1 / 6

4rd Implementation Report

4rd Implementation Report. Bing Liu(speaker), Sheng Jiang, Yu Fu @ softwire -IETF 84-Vancouver Aug-2 2012. 4rd logical functions (CPE). 6->4 translation. CPE. CPE. 端口 限制. NAT44. 4o6 报文 解 / 封装. NAT44 翻译. Fragmt Hdr. Port restrict. IPv4 Forwarding. 4->6 translation. IPv4

gayle
Download Presentation

4rd Implementation Report

An Image/Link below is provided (as is) to download presentation Download Policy: Content on the Website is provided to you AS IS for your information and personal use and may not be sold / licensed / shared on other websites without getting consent from its author. Content is provided to you AS IS for your information and personal use only. Download presentation by click this link. While downloading, if for some reason you are not able to download a presentation, the publisher may have deleted the file from their server. During download, if you can't get a presentation, the file might be deleted by the publisher.

E N D

Presentation Transcript

  1. 4rd Implementation Report Bing Liu(speaker), Sheng Jiang, Yu Fu @softwire-IETF 84-Vancouver Aug-2 2012

  2. 4rd logical functions (CPE) 6->4 translation CPE CPE 端口限制 NAT44 4o6报文解/封装 NAT44翻译 FragmtHdr Port restrict IPv4 Forwarding 4->6 translation IPv4 Fragmt Identifying 4rd packets IPv4host IPv4/IPv6判断模块 IPv6 only FragmtHdr IPv4转发模块 Addr Calculation Mapping rule table 4rd BR IPv6转发模块 IPv6 forwarding IPv6host

  3. 4rd logical functions (BR) 6->4 IPv4 FWD FragHdr IPv4Internet Mapping rule table Addr Calculation 4->6 IPv4 Fragmt FragHdr Identififying 4rd packets IPv6 only CPE IPv6FWD IPv6Internet

  4. Implementation in Linux Linux Kernel TCP/IP Stack Linux Kernel Netfilter 4RD Translator 4RD Virtual Interface CPE LAN Interface CPE WAN Interface 4rd module

  5. Preliminary Conclusions • 4rd doesn’t change any IP protocol standards at the routing plane. • At the routing plane, 4rd packet is identical to normal IPv6 packet. Since we only used standard interfaces to input/output packets to/from the 4rd module, the TCP/IP stack itself doesn’t need to do 4rd-specific extension. • The 4rd fragment header remains the same data structure of IPv6 standard, the utilization of fragment-header doesn’t bother the TCP/IP stack and routers, unless fraghdr-specific-rules DPI is deployed. • 4rd packet translation is lightweight • No need to deal with the checksum adjustment(benefit from CNP) • No need to process each protocol (TCP/UDP/ICMP) respectively • More likely an “encapuslation” rather than “translation” • Our implementation and analysis haven’t identified any ambiguity or flaw.

  6. Thank you!leo.liubing@huawei.comjiangsheng@huawei.com eleven.fuyu@huawei.comAug 2, @Vancouver

More Related