This document is based on draft-akira-v6ops-mape-experience-00

1. 240b::1240b::1
APRICOT
Operational Experience of MAP-‐‑‒E
⽇日本ネットワークイネイブラー株式会社
(JPNE)
中川あきら
Jul.24.2015
Japan Network Enabler (JPNE)
Akira Nakagawa

2. 240b::2240b::2
Beginning
Overview of “MAP-‐‑‒E of JPNE”
was presented at IETF92 v6ops @ Dallas :
https://www.ietf.org/proceedings/92/
slides/slides-‐‑‒92-‐‑‒v6ops-‐‑‒2.pdf

3. 240b::3240b::3
464XLAT
DS-‐‑‒Lite
JPIX
IoT
MAP-‐‑‒E in JPNE
IPv4
Internet
IPv6
Internet
BR
BR : Border Relay
SPI : Stateful Packet Inspection
IPv4 over IPv6
Home Router
(v4NAT/v6SPI)
IPv6
IPv6
DNS cache
IPv6
Home Router
(v4NAT/v6SPI)
Stateless,
(not CGN)
IPv6
IPv4 over IPv6

4. 240b::4240b::4
Final Goal
v4 Sunsetv6
Internet
v4
Internet
JPNE)
IPv4
over
IPv6
offloading IPv6
Final Goal
Steps
1. Overlaying IPv4
on IPv6.
2. Offloading traffic
to simple IPv6.
3. Removing
overplayed IPv4.
Now

5. 240b::5240b::5
464XLAT
DS-‐‑‒Lite
JPIX
IoT
Off-‐‑‒loading
IPv4
Internet
IPv6
Internet
BR
IPv4 over IPv6
IPv4 over IPv6
IPv6
IPv6
DNS cache
IPv6
IPv6
※
※
※
※Trying to reduce load
of BR and backbone.

6. 240b::6240b::6
Motivation to choose MAPE (1/2)
1. Suitable to go to final goal “IPv6-‐‑‒only”.
2. No setup operation by users.
3. No daily provisioning operation by
network providers.
4. No logging function no storage.
The upper, the most important
for JPNE.

7. 240b::7240b::7
Motivation to choose MAPE (2/2)
6. Border Relays scales according to only
traffic, not number of user, not number
of session. network.
7. No session management.
8. Packets between MAP-‐‑‒E users donʼ’t
detour Border Relay. It reduces
l Load of Border Relay
l Traffic of backbone network.

8. 240b::8240b::8
Motivation to move Traffic to IPv6
IPv4
Plural device makers told me
• Cost of testing and after-‐‑‒support of variety of
protocols is high.
• One type is ideal, less types is better.
NAT444 MAP-‐‑‒E MAP-‐‑‒T DS-‐‑‒Lite 464XLAT
IPv6
ISP3 ISP4 ISP5
IPv6 ISP6 ISP7 ISP8 ISP9 ISP10
ISP11 ISP12 ISP13 ISP14 ISP15
tuneup
1
tuneup
2
tuneup
n
ISP1 ISP2
IPv6 has been
additional
IPv4s are additional

9. 240b::9240b::9
NW Design of MAP-‐‑‒E (Redundant)
BR BR BR
Router Router
Backbone Network
• Same MAP Rule on
all BRs
• Traffic balances
equally by ECMP
Anycast Address
Router Router
IPv4
Over IPv6
IPv4
Normal :
• Keeping traffic less
than capacity.
When a BR fails :
• Other BRs undertake
traffic equally.

10. 240b::10240b::10
NW Design of MAP-‐‑‒E (Scaling)
BR BR BR
Router Router
Backbone Network
Anycast Address
Router Router
IPv4
Over IPv6
IPv4
Just adding
BRs.
BR
Scales
• Same MAP Rule on
all BRs
• Traffic balances
equally by ECMP

11. 240b::11240b::11
Protocols supported by MAP-‐‑‒E
l Protocols without port number doesnʼ’t
function. (PPTP/SCTP/IPsec)
l Example of workaround
l IPSec doesnʼ’t have port number.
l It works if client is NAT traversal mode
l FTP has different issue.
l Client is passive mode, FTP works.
l Client is active mode, ALG is required on MAP
CE.

12. 240b::12240b::12
ping
Good enough from
userʼ’s view, so far.
l Users can ping to
Internet.
l Operator can ping
to users.
IPv4
◯
MAP
CE
✕
✕
✕
Tester
BR
◯
IPv4
IPv4 over IPv6
to:
IPv4 Add + ICMP ID
MAP
CE
(Operator)

13. 240b::13240b::13
Effects on Users by “Address Sharing”
l Users may not be affected practically, so far.
l A very few OLD games do not function.
l IP conference system that uses H.323 did
not function.
Address
Sharing
IP 192.0.2.1
Port 1720 (waiting)
Dest:
IP 192.0.2.1
Port 1720(fixed) ✕
Conference Conference

14. 240b::14240b::14
Timer Management
l NAT Mapping Timer at MAP CE
l Shorter -‐‑‒-‐‑‒-‐‑‒> Consuming less ports
l Longer -‐‑‒-‐‑‒-‐‑‒> Consuming more ports
l Timer Management
l Keepalive of Application > Timer
• -‐‑‒-‐‑‒-‐‑‒> Application doesnʼ’t function
l Keepalive of Application < Timer
• -‐‑‒-‐‑‒-‐‑‒> Application function
l Needed to tune.

15. 240b::15240b::15
Effects on People by “Address Sharing”
Becoming complicated.
l Abuse issue
l Solving criminal cases
l Solving civil litigation
Content / Server
ISP
IPv4
Address
Sharing
Same IP
F/W・L/B etc.
Important :
Taking Log of port
number at Server,
Firewall, etc.

16. 240b::16240b::16
Effects on Internal Staff
l Comparing to single stack IPv4
l Architecture of MAP-‐‑‒E is IPv6 based and
simple.
l But operators have to handle two protocols.
l Even experts cannot convert IPv4 address to
IPv6.
By introducing tools, operation becomes simple
for all staff.
(e.g.) IPv4/IPv6 Ping Trouble Shooting tool.
http://kiriwake.jpne.co.jp/

17. 240b::17240b::17
Comments ?