Stateless IPv4 over IPv6 report dra1- janog- so1wire- report- 01

Transcription

1 Stateless IPv4 over IPv6 report dra1- janog- so1wire- report- 01 Shishio Tsuchiya Shuichi Ohkubo Yuya Kawakami

2 What is JANOG? JApan Network Operator s Group 2 Major AcFviFes Mailing list janog@janog.gr.jp subscribers 2 MeeFngs per year Working Group focus special technology JANOG established Working group to focus the stateles IPv4 over IPv6. WG had held MAP- E interop events at Nagaoka. 7 vendors and 9 implementafons atended to the interop events

3 The documents ImplementaFon Report IPv4 funcfonality over IPv6 ICMP,FTP,IPSec VPN,SSL VPN,PPTP,L2TP Instant Messaging and VoIP [RFC6586] STUN, NAT- Analyzer BR redundancy Interoperability

4 The interop event network topology IPv4 internet IPv6 internet NSCS BR CE

5 BR ParFcipant list Vendor IP Infusion Furukawa Network SoluFon Corp. ASAMAP Internet IniFaFve Japan Inc. Cisco Systems OS/Equipement Linux NetBSD FX5000 VyaTa SEIL/X1 IOS- XR/ASR vendors, 6 implementafons

6 CE ParFcipant list Vendor IP Infusion Furukawa Network SoluFon Corp. ASAMAP Internet IniFaFve Japan Inc. CERNET Yamaha CorporaFon OS/Equipement Linux NetBSD F60W VyaTa SEIL/X1 OpenWRT RTX vendors, 7 implementafons Total 7 vendors, 9 implementafons

7 ImplementaFon Report cont d Security mechanism ask consistency checks between IPv4 and IPv6 src on BR/CE SecFon 13 of [I- D.ieh- soiwire- map]. Provisioning method all of atendee only support manual configurafon. There is difference configurafon type for Length of EA bits Reachability to BR address 3BR can confirm reachability of BR address 2BR can not confirm reachability of BR address but can confirm reachability of BR s interface address.

8 Difference configurafon type for Length of EA bits Rule IPv6 prefix: Rule IPv4 prefix: EA bits: Port-Set ID: PSID offset: BR IPv6 address: 2403:9200::/ /28 16bit(48-32) 12bit :9200:fff0:0::2 # set interfaces map map0 role br # set interfaces map map0 br- address 2001:db8::1/64 # set interfaces map map0 default- forwarding- mode translafon # set interfaces map map0 default- forwarding- rule true # set interfaces map map0 rule 1 ipv6- prefix 2001:db8:89ab::/48 # set interfaces map map0 rule 1 ipv4- prefix /24 # set interfaces map map0 rule 1 ea- length 16 useful for operafon and trouble shoofng service cgn JANOG service- locafon preferred- acfve 0/0/CPU0 service- type map- e Soiwire cpe- domain ipv4 prefix /28 cpe- domain ipv6 prefix 2403:9200::/32 sharing- raeo 12 air- endpoint- address 2403:9200:fff0::2 confguous- ports 0 easy to understand design Appendix 2 all of configurafon

9 Parameter Rule IPv6 prefix Rule IPv4 prefix End- user IPv6 prefix EA bits Port- Set ID PSID offset BR IPv6 address Topology Test Parameter MAP- E Value 2403:9200::/ / :9200:fff1::/ :9200:fff7::/48 16bit(48-32) 12bit :9200:fff0:0::2 Mesh Only 15 Port for CE, Sharing raeo 1:4096

10 Test Parameter MTU Parameter IPv6 MTU TCP MSS clamp Tunnel IF IPv4 MTU Value 1500byte Enable 1460byte Not 1280 byte

11 IPv4 funcfonality over IPv6 ICMP echo request echo request echo reply TTL exipre Too big host unreach With IdenFfier message for CE/BR Null IdenFfier message for BR

12 IPv4 funcfonality over IPv6 VPN(IPSec VPN,SSL VPN,PPTP,L2TP),FTP(Port/PASV) Instant Messaging,VoIP and Video NAT VerificaFon tool KONAMI [RFC4787] verificafon tool NAT- Analyzer(TUM)

13 Issue of IPv4 funcfonality Even DNS query occupy NAT table(only 15) UDP/DNS Fmeout immediately DNS transport proxy,secfon- 3 of [I- D.drai- dec- stateless- 4v6] Implicit IPv6 MTU limitafon(1280byte) could not browse, could not video chat should well- managed, secfon 10.1 of [I- D.ieh- soiwire- map] All of vendor support NAT Traversal Most of modern message tools are succeed NAT- verificafon tool and FTP(ACTV) result depends on implementafon of NAT.

14 BR redundancy IPv6 Confirmed BR redundancy by roufng convergence Skype session kept, could communicate aier converged

15 Interoperability The IPv6 Interface IdenEfier Wrong :2403:9200:fff6:0:cb:56e1:fff:6000 Correct: 2403:9200:fff6:0:cb:56e1:f0f:f600 mis- understanding lei- padding and right- padding If it could add example to explain format in SecFon6, then it would be more understandable.

16 Conclusion Many vendors already supported MAP- E. No crifcal interoperability issue between mulfvendor CE and CE,CE and BR,BR and BR. DNS transport proxy and MTU issue already discussed on IETF and drai. MAP- E is mature