IPICMP Translation Algorithm rfc 6145 bis02 https datatracker

IP/ICMP Translation Algorithm (rfc 6145 bis-02) https: //datatracker. ietf. org/doc/draft-bao-v 6 opsrfc 6145 bis/ IETF 94 2015 -11 -02

Outline • RFC 6145 bis • Next step 2

RFC 6145 • IP/ICMP Translation Algorithm – https: //datatracker. ietf. org/doc/rfc 6145/referencedby/ • The Building block of – – rfc 6146 (NAT 64, stateful) rfc 6219 (IVI, stateless NAT 64) rfc 6877 (464 XLAT, stateful double translation) rfc 7599 (MAP-T, stateless double translation) • Referenced by – 31 rfcs (rfc 6127, rfc 6144, rfc 6146, rfc 6156, rfc 6180, rfc 6219, rfc 6264, rfc 6269, rfc 6272, rfc 6296, rfc 6316, rfc 6342, rfc 6384, rfc 6535, rfc 6586, rfc 6724, rfc 6736, rfc 6751, rfc 6791, rfc 6864, rfc 6877, rfc 6889, rfc 6992, rfc 7059, rfc 7269, rfc 7368, rfc 7381, rfc 7598, rfc 7599, rfc 7600) – 23 active drafts 3

RFC 6145 bis • Erratum • Atomic Fragments • Address mapping algorithm update 4

Erratum From http: //www. rfc-editor. org/errata_search. php? rfc=6145 etc 5

Atomic Fragments From 6 man's document concerning "Deprecating the Generation of IPv 6 Atomic Fragments" https: //datatracker. ietf. org/doc/draft-ietf-6 man-deprecateatomfrag-generation/ RFC 6145 already has this mechanism, but it is just an option. The rfc 6145 bis makes this mechanism the default and the only one. 6

http: //www. ietf. org/proceedings/76/slides/behave-6. htm 7

Address mapping algorithm update • Mapping of IP Addresses – SHOULD • rfc 6052 default • http: //datatracker. ietf. org/doc/draft-ietf-v 6 ops-siiteam/ (EAM) • rfc 6791 (Stateless Source Address Mapping for ICMPv 6 Packets) – MAY • rfc 6146 (NAT 64) • rfc 6799 (MAP-T) 8

Next step • Start a 30 day IETF LC and take this as an AD-sponsored draft 9