Internet-Draft icmpext-xlat-source July 2024
Lamparter & Linkova Expires 8 January 2025 [Page]
Workgroup:
Internet Area
Internet-Draft:
draft-equinox-intarea-icmpext-xlat-source-01
Updates:
7915 (if approved)
Published:
Intended Status:
Standards Track
Expires:
Authors:
D. Lamparter
NetDEF, Inc.
J. Linkova
Google

ICMP Extensions for IP/ICMP translators (XLATs)

Abstract

This document proposes allocating a dedicated IPv4 address for translating arbitrary (non-IPv4-translatable) IPv6 addresses and suggests the creation of an ICMP Multi-part Extension to carry the original IPv6 source address of ICMPv6 messages translated to ICMP by stateless (RFC7915) or stateful (RFC 6146) protocol translators.

About This Document

This note is to be removed before publishing as an RFC.

Source, version control history, and issue tracker for this draft can be found at https://github.com/eqvinox/icmpext-clat-source.

(Note the draft was renamed (clat → xlat) prior to submission but changing the repository name on github breaks too many things to be worth the effort.)

Status of This Memo

This Internet-Draft is submitted in full conformance with the provisions of BCP 78 and BCP 79.

Internet-Drafts are working documents of the Internet Engineering Task Force (IETF). Note that other groups may also distribute working documents as Internet-Drafts. The list of current Internet-Drafts is at https://datatracker.ietf.org/drafts/current/.

Internet-Drafts are draft documents valid for a maximum of six months and may be updated, replaced, or obsoleted by other documents at any time. It is inappropriate to use Internet-Drafts as reference material or to cite them other than as "work in progress."

This Internet-Draft will expire on 8 January 2025.

▲

Table of Contents

1. Introduction

To allow communication between IPv6-only and IPv4-only devices, IPv4/IPv6 translators translate IPv6 and IPv4 packet headers according to the IP/ICMP Translation Algorithm defined in [RFC7915]. For example, 464XLAT ([RFC6877]) defines an architecture for providing IPv4 connectivity across an IPv6-only network. The solution contains two key elements: provider-side translator (PLAT) and customer-side translator (CLAT). CLAT implementations translate private IPv4 addresses to global IPv6 addresses, and vice versa, as defined in [RFC7915].

To map IPv4 addresses to IPv6 ones the translators use the translation prefix (either a well-known or a network-specific one, see [RFC6052]). The resulting IPv6 addresses can be statelessly translated back to IPv4. However it's not the case for an arbitrary global IPv6 addresses. Those addresses can only be translated to IPv4 by a stateful translators.

One of scenarios when it might be required but not currently possible is translating ICMPv6 error messages send by intermediate nodes to the CLAT address in the 464XLAT envinronment. The most typical example is a diagnistic tool like traceroute sending packets to an IPv4 destination from an IPv6-only host. Received ICMPv6 Time Exceeded are translated to ICMP Time Exceeded. If those packets were originated from an IPv4 address and translated to ICMPv6 by the PLAT (NAT64) device, then the source address of such packet can be mapped back to IPv4 by removing the translation prefix. However ICMPv6 error messages sent by devices located between the IPv6-only host and the NAT64 device have "native" IPv6 source addresses, which can not be mapped back to IPv4. Those packets are usually dropped and tools like traceroute can not represent IPv6 intermediate hops in any meaningful way. Such behaviour complicates troubleshooting. It's also confusing for users and increases operational costs, as users report packet loss in the network based on traceroute output.

Some CLAT implementations are known to workaround this issue by representing IPv6 addresses in IPv4 traceroute by using a reserved IPv4 address space and using the hop limit as the last octet, so an IPv6 device 5 hops away is shown as 225.0.0.5 etc.

It should be noted that the similar issue occurs in IPv6 Data Center Environments when an ICMPv6 error message needs to be sent to an IPv4-only client. As per Section 4.8 of [RFC7755], ICMPv6 error packets are usually dropped by the translator.

This document introduces a dedicated IPv4 address to translate arbitrary global IPv6 addresses in ICMPv6 error messages, and proposes an ICMP extension so original IPv6 address of an ICMPv6 error message can be included into IMCP message and therefore passed to an application.

2. Requirements Language

The key words "MUST", "MUST NOT", "REQUIRED", "SHALL", "SHALL NOT", "SHOULD", "SHOULD NOT", "RECOMMENDED", "NOT RECOMMENDED", "MAY", and "OPTIONAL" in this document are to be interpreted as described in BCP 14 [RFC2119] [RFC8174] when, and only when, they appear in all capitals, as shown here.

3. Translation Behavior Overview

Whenever a translator translates an ICMPv4 ([RFC0792]) packet from an ICMPv6 ([RFC4443]) one, and the IPv6 source address in the outermost IPv6 header does not match the NAT64 prefix (and is therefore not mappable to an IPv4 address), the translator SHOULD:

The translator SHOULD NOT use 192.0.0.11/32 to translate the source IPv6 address and SHOULD NOT add the extension if the packet IPv6 source address is an IPv4 address mapped to an IPv6 address using the translation prefix known to the translator, of if the translator has a stateful entry for the given IPv6 address mapped to another IPv4 address.

4. Dedicated IPv4 Address for Stateful Translation of Global IPv6 Addresses

This document proposed allocating a dedicated IPv4 192.0.0.11/32 to use for statefully translating global IPv6 addresses in ICMPv6 error messages in scenarious, when the transator doesn't have any existing entry to use for translating such an address.

5. IPv6 Original Source Extension Object Format

The suggested encoding to be appended[RFC4884] to ICMP messages is as follows:

 0                   1                   2                   3
 0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
|          Length = 20          |   Class TBD1  |  C-Type = 0   |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
|                                                               |
+                                                               +
|                  original IPv6 source address                 |
+                          16 octets                            +
|                                                               |
+                                                               +
|                                                               |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
Figure 1

The Length, Class and C-Type fields are as defined in [RFC4884] and filled in accordingly. This document describes only one encoding and uses C-Type 0 for it. C-Type MUST be set to 0 when appending this extension. On receipt, this extension MUST be ignored if C-Type is not 0 or if Length is not 20.

The original IPv6 source address field is always 16 octets in length and filled as described in this document. It may contain any source address possibly seen in an ICMPv6 packet. This notably includes link-local addresses, the IPv6 loopback address, and mapped IPv4 addresses. Receivers MUST NOT reject addresses solely due to the address not being a globally scoped IPv6 addresses.

6. Translation Behavior

6.1. Adding IPv6 Original Source Extension Object

IPv6 Original Source Extension Object SHOULD be added when translating"

  • ICMPv6 Destination Unreachable to ICMPv4 Destination Unreachable

  • ICMPv6 Time Exceeded to ICMPv4 Time Exceeded.

and the IPv6 source address in the outermost IPv6 header does not match the NAT64 prefix.

IPv6 Original Source Extension Object MUST NOT be added in any other cases.

6.1.1. Adding New ICMP Extension Structure

If the original ICMPv6 message does not contain an ICMP Extension Structure (as defined in Section 7 of [RFC4884]), the translator SHOULD append a new ICMP Extension Structure to the resulting ICMPv4 message. When adding the new Extension Structure, the translator MUST:

  • Create a new ICMP Extension Structure, containing one Extension Header and one IPv6 Original Source Extension object.

  • Append that Extension Structure to the original ICMPv6 message.

  • If the resulting packet size exceeds the minimum IPv6 MTU: truncate the embedded invoking packet by removing the trailing 24 octets (to accomodate for 4 octets of the extension header and 20 octets of the extension object).

  • Set the length field of the ICMPv6 message to the length of the padded "original datagram" field, measured in 32-bit words.

  • Translate the resulting ICMPv6 message to IPv6 as per [RFC7915].

6.1.2. Adding IPv6 Original Source Extension Object to Existing ICMP Extension Structure

If the original ICMPv6 message already contains an ICMP Extension Structure, the translator SHOULD append an IPv6 Original Source Extension object to that structure. When appending the object, the translator MUST:

  • Append an IPv6 Original Source Extension object to the Extension Structure.

  • Update the checksum field of the Extension Header accordingly.

  • If the resulting packet size exceeds the minimum IPv6 MTU: truncate the embedded invoking packet by removing the trailing 20 octets (to accomodate for 20 octets of the extension object) and update the length field of the ICMPv6 message

  • Translate the resulting ICMPv6 message to IPv6 as per [RFC7915].

6.2. Translating Arbitrary IPv6 Source Addresses Using the Dedicated IPv4 Address

The translator SHOULD use the dedicated IPv4 192.0.0.11/32 for translating IPv6 source addresses if all of the following conditions are met:

  • The packet being translated is one of the following:

    • ICMPv6 Destination Unreachable

    • ICMPv6 Time Exceeded

    • ICMPv6 Packet Too Big

  • the IPv6 source address in the outermost IPv6 header does not match the NAT64 prefix (and is therefore not mappable to an IPv4 address).

  • The translator does not have an explicit address mapping ([RFC7757]) configured for the given global IPv6 address to an IPv4 address .

it should be noted that the IPv6 Original Source Extension Object can not be added to ICMPv6 Packet Too Big messages (see Section 4.6 of [RFC4884]). At the same time it's highly desirable to ensure that translators translate those messages even if the IPv6 source address in the outermost IPv6 header does not match the NAT64 prefix (and is therefore not mappable to an IPv4 address), as those messages are crucial for Path MTU Discovery.

7. Updates to RFC7915

This document makes the following changes to Section 5.1 of [RFC7915]:

The text in RFC7915 is as follows:

Source Address: Mapped to an IPv4 address based on the algorithms presented in Section 6.

This document updates the text as follows:

Source Address: Mapped to an IPv4 address based on the algorithms presented in Section 6. When translating ICMPv4 error messages to ICMPv6 error messages and the valid IPv6 source address in the outermost IPv6 header does not match the prefix used in algorithmic mapping, the translator SHOULD follow the recommendations in draft-equinox-intarea-icmpext-xlat-source.

This document also adds the following paragraph before the very last paragraph of Section 5.2 of [RFC7915] (before "Error payload:"):

If valid IPv6 source address in the outermost IPv6 header of the ICMPv6 messages does not match the prefix used in algorithmic mapping, the translator SHOULD follow the recommendations in draft-equinox-intarea-icmpext-xlat-source.

8. Security Considerations

TBD. Should probably be local-only.

9. Privacy Considerations

TBD

10. IANA Considerations

This document requests that IANA allocates a "Class Value" from the "ICMP Extension Object Classes and Class Sub-types" registry created by [RFC4884] for use as described above. The following entry should be appended:

Table 1
Class Value Class Name Reference
TBD1 Original IPv6 Source Address [THIS DOCUMENT]

This document also requests that IANA allocates an IPv4 address 192.0.0.11/32) and updates the IPv4 Special-Purpose Address Registry available at (http://www.iana.org/assignments/iana-ipv4-special-registry/) with the following:

Address Block: 192.0.0.11/32

Name: [TBA IN THE NEXT VERSION OF THE DRAFT]

RFC: [THIS DOCUMENT]

Allocation Date: TBD3

Termination Date: N/A

Source: True

Destination: False

Forwardable: False

Global: False

Reserved-by-Protocol: False

11. References

11.1. Normative References

[RFC0792]
Postel, J., "Internet Control Message Protocol", STD 5, RFC 792, DOI 10.17487/RFC0792, , <https://www.rfc-editor.org/info/rfc792>.
[RFC2119]
Bradner, S., "Key words for use in RFCs to Indicate Requirement Levels", BCP 14, RFC 2119, DOI 10.17487/RFC2119, , <https://www.rfc-editor.org/info/rfc2119>.
[RFC4443]
Conta, A., Deering, S., and M. Gupta, Ed., "Internet Control Message Protocol (ICMPv6) for the Internet Protocol Version 6 (IPv6) Specification", STD 89, RFC 4443, DOI 10.17487/RFC4443, , <https://www.rfc-editor.org/info/rfc4443>.
[RFC4884]
Bonica, R., Gan, D., Tappan, D., and C. Pignataro, "Extended ICMP to Support Multi-Part Messages", RFC 4884, DOI 10.17487/RFC4884, , <https://www.rfc-editor.org/info/rfc4884>.
[RFC6052]
Bao, C., Huitema, C., Bagnulo, M., Boucadair, M., and X. Li, "IPv6 Addressing of IPv4/IPv6 Translators", RFC 6052, DOI 10.17487/RFC6052, , <https://www.rfc-editor.org/info/rfc6052>.
[RFC7915]
Bao, C., Li, X., Baker, F., Anderson, T., and F. Gont, "IP/ICMP Translation Algorithm", RFC 7915, DOI 10.17487/RFC7915, , <https://www.rfc-editor.org/info/rfc7915>.
[RFC6877]
Mawatari, M., Kawashima, M., and C. Byrne, "464XLAT: Combination of Stateful and Stateless Translation", RFC 6877, DOI 10.17487/RFC6877, , <https://www.rfc-editor.org/info/rfc6877>.
[RFC7757]
Anderson, T. and A. Leiva Popper, "Explicit Address Mappings for Stateless IP/ICMP Translation", RFC 7757, DOI 10.17487/RFC7757, , <https://www.rfc-editor.org/info/rfc7757>.
[RFC8174]
Leiba, B., "Ambiguity of Uppercase vs Lowercase in RFC 2119 Key Words", BCP 14, RFC 8174, DOI 10.17487/RFC8174, , <https://www.rfc-editor.org/info/rfc8174>.

11.2. Informative References

[RFC7755]
Anderson, T., "SIIT-DC: Stateless IP/ICMP Translation for IPv6 Data Center Environments", RFC 7755, DOI 10.17487/RFC7755, , <https://www.rfc-editor.org/info/rfc7755>.

Acknowledgements

This document is the result of discussions with Thomas Jensen. The authors would like to thank Darren Dukes, Bill Fenner for their feedback, comments and guidance.

Authors' Addresses

David 'equinox' Lamparter
NetDEF, Inc.
San Jose,
United States of America
Jen Linkova
Google
1 Darling Island Rd
Pyrmont NSW 2009
Australia