rfc-7678

Attribute-Value Pairs for Provisioning Customer Equipment Supporting IPv4-Over-IPv6 Transitional Solutions

C. Zhou, T. Taylor, Q. Sun, M. Boucadair
date2015-10 streamIETF areaops wgdime statusPROPOSED STANDARD pages23 canonicalhttps://www.rfc-editor.org/rfc/rfc7678 doi10.17487/RFC7678
During the transition from IPv4 to IPv6, customer equipment may have to support one of the various transition methods that have been defined for carrying IPv4 packets over IPv6. This document enumerates the information that needs to be provisioned on a customer edge router to support a list of transition techniques based on tunneling IPv4 in IPv6, with a view to defining reusable components for a reasonable transition path between these techniques. To the extent that the provisioning is done dynamically, Authentication, Authorization, and Accounting (AAA) support is needed to provide the information to the network server responsible for passing the information to the customer equipment. This document specifies Diameter (RFC 6733) Attribute-Value Pairs (AVPs) to be used for that purpose.

Extracted elements (29)

design-rationale §2

A Grouped AVP wrapper is unnecessary for DS-Lite because AAA only needs to supply the AFTR's FQDN; the absence of lw4o6 or MAP-E Grouped AVPs with only the AFTR FQDN present implicitly signals DS-Lite as the selected transition method.

v6ops, diameter

design-rationale §3.2

Border routers are identified by FQDN rather than IP address, following the precedent of RFC 6334 and RFC 6519 for DS-Lite. The FQDN can be dereferenced to one or more IP addresses by the provisioning system or passed as-is to the customer equipment, providing flexibility.

diameter, v6ops

design-rationale §3.4

The Tunnel-Source-Pref-Or-Addr AVP is defined separately from Lw4o6-Binding to allow flexibility: the provisioning system can deliver just the tunnel source address to AAA independently, while still supporting delivery of the complete binding to the lw4o6 border router.

v6ops, diameter

interoperability-note §2.2

For lw4o6, per-subscriber configuration at the CPE (IPv4 address, port set, tunnel source address) must be synchronized with corresponding configuration at the border router. The border router requires the same public IPv4 address and port set parameters bound to the full /128 tunnel source IPv6 address.

v6ops

interoperability-note §2.1

The B4 interface IPv4 address for DS-Lite (valid range 192.0.0.2–192.0.0.7, default 192.0.0.2) is not provisioned via AAA in this framework because it is problematic when multiple B4 instances share a device; it is determined by implementation-dependent or static means.

v6ops, diameter

normative-requirement §4 MUST NOT

All AVPs defined in this document have the V-flag in the MUST NOT column, meaning the Vendor-ID flag must not be set. The M-bit usage for these AVPs in a given command may be defined by the application per RFC 6733.

diameter, v6ops

normative-requirement §3.3 MUST

The 64-Multicast-Attributes AVP MUST include at least one of ASM-mPrefix64 or SSM-mPrefix64, and MAY include both. When SSM-mPrefix64 is present, the Delegated-IPv6-Prefix AVP MUST also be present.

diameter, v6ops, multicast

normative-requirement §3.6.1 MUST

The Lw4o6-External-IPv4-Addr AVP (code 641) AddressType field MUST be set to 1 (IPv4) and the total length of the AVP MUST be 14 octets.

diameter, v6ops

normative-requirement §3.4.2 MUST

The Tunnel-Source-IPv6-Address AVP (code 638) is of type Address and its AddressType field MUST be set to 2 (IPv6); it conveys the CPE's local tunnel endpoint address for an lw4o6 tunnel.

diameter, v6ops

normative-requirement §3.4 MUST

The Tunnel-Source-Pref-Or-Addr AVP MUST contain either the Delegated-IPv6-Prefix AVP or the Tunnel-Source-IPv6-Address AVP, but not both.

diameter, v6ops

normative-requirement §3.3.1 MUST

Within ASM-mPrefix64 and SSM-mPrefix64 AVPs, the AddressType field of IP-Address MUST have value 2 (IPv6), the conveyed prefix MUST belong to the correct multicast range, and unused bits beyond the prefix MUST be set to zeroes by the sender.

diameter, v6ops, multicast

normative-requirement §3.7 MUST

Within MAP-E-Attributes, at least one Border-Router-Name AVP MUST be present and at least one MAP-Mapping-Rule AVP MUST be present. In Hub-and-Spoke mode, additional MAP-Mapping-Rule instances MUST NOT be present.

diameter, v6ops

normative-requirement §3.9 MUST

Within MAP-Mapping-Rule, the Rule-IPv4-Addr-Or-Prefix, Rule-IPv6-Prefix, EA-Field-Length, and Port-Set-Identifier AVPs MUST all be present.

diameter, v6ops

normative-requirement §3.3.3 MUST

Within the 64-Multicast-Attributes AVP, the Delegated-IPv6-Prefix AVP used as uPrefix64 MUST have a Prefix-Length value of one of 32, 48, 56, 64, or 96, per RFC 6052 address mapping guidelines.

diameter, v6ops, multicast

privacy-consideration §6.2 MUST

The AVPs defined in this document reveal privacy-sensitive information such as subscriber addresses that can be used for tracking. All these AVPs are considered security-sensitive, and the security considerations of RFC 6733 Section 13.3 MUST be followed for Diameter messages containing them.

privacy, security, diameter, v6ops

protocol-element §3.3

The 64-Multicast-Attributes AVP (code 634) is a Grouped AVP carrying IPv6 multicast prefixes for IPv4-over-IPv6 multicast delivery (DS-Lite, MAP-E, lw4o6). It contains optional ASM-mPrefix64, SSM-mPrefix64, and Delegated-IPv6-Prefix (as uPrefix64) sub-AVPs.

diameter, v6ops, multicast

protocol-element §3.3.1

The ASM-mPrefix64 AVP (code 635) is a Grouped AVP containing an IP-Address (AddressType MUST be 2/IPv6, MUST belong to ASM range) and IP-Prefix-Length (valid range 24–96) for synthesizing IPv4-embedded IPv6 multicast group addresses in ASM mode.

diameter, v6ops, multicast

protocol-element §3.2

The Border-Router-Name AVP (code 633) is of type OctetString and carries the FQDN of a DS-Lite AFTR, lw4o6 border router, or MAP-E border relay. FQDN encoding MUST follow RFC 1035/1123/2181 syntax in ASCII; A-labels (RFC 5891) must be used for internationalized domain names.

diameter, v6ops

protocol-element §3.9.3

The EA-Field-Length AVP (code 647) is of type Unsigned32 with valid values 0–48, encoding the number of Embedded Address bits in the MAP-E end-user IPv6 prefix used to derive IPv4 address and port number configuration per RFC 7597 Section 5.2.

diameter, v6ops

protocol-element §3.1

The IP-Prefix-Length AVP (code 632) is of type Unsigned32 and provides the length of an IPv4 or IPv6 prefix; valid values are 0–32 for IPv4 and 0–128 for IPv6. It is only meaningful when associated with an IP-Address AVP inside a Grouped AVP.

diameter, v6ops

protocol-element §3.6

The Lw4o6-Binding AVP (code 640) is a Grouped AVP binding an lw4o6 tunnel to IPv4 packets; it contains mandatory Tunnel-Source-Pref-Or-Addr and Lw4o6-External-IPv4-Addr sub-AVPs, and an optional Port-Set-Identifier when the IPv4 address is shared.

diameter, v6ops

protocol-element §3.7

The MAP-E-Attributes AVP (code 642) is a Grouped AVP carrying all MAP-E configuration for a single MAP domain: one or more Border-Router-Name AVPs, one or more MAP-Mapping-Rule AVPs, an optional MAP-Mesh-Mode AVP, and an optional Delegated-IPv6-Prefix for the end-user IPv6 prefix.

diameter, v6ops

protocol-element §3.9

The MAP-Mapping-Rule AVP (code 644) is a Grouped AVP requiring all four sub-AVPs: Rule-IPv4-Addr-Or-Prefix, Rule-IPv6-Prefix, EA-Field-Length, and Port-Set-Identifier. It encodes a MAP-E Basic or Forwarding Mapping Rule.

diameter, v6ops

protocol-element §3.8

The MAP-Mesh-Mode AVP (code 643) is of type Enumerated with values 0 (MESH) and 1 (HUB_AND_SPOKE). The absence of this AVP indicates Hub-and-Spoke mode is required.

diameter, v6ops

protocol-element §3.3.2

The SSM-mPrefix64 AVP (code 636) is a Grouped AVP containing an IP-Address (IPv6, SSM range) and IP-Prefix-Length for synthesizing IPv4-embedded IPv6 multicast group addresses in Source-Specific Multicast mode.

diameter, v6ops, multicast

protocol-element §3.4

The Tunnel-Source-Pref-Or-Addr AVP (code 637) is a Grouped AVP that carries either the IPv6 Binding Prefix (Delegated-IPv6-Prefix) or the full tunnel source IPv6 address (Tunnel-Source-IPv6-Address) for lw4o6 CPE configuration; it MUST contain exactly one of the two, not both.

diameter, v6ops

registry §5

IANA registered 16 new Diameter AVP codes (632–647) in the 'AVP Codes' registry for IPv4-over-IPv6 transitional provisioning, covering IP-Prefix-Length, Border-Router-Name, multicast attributes, tunnel source, port set, lw4o6 binding, and MAP-E attributes.

registry, diameter, v6ops

security-consideration §6.1

MITM attacks on the Diameter delivery path can cause denial-of-service via misconfiguration (invalid addresses leading to connectivity failure or traffic interception via a fake border node). Diameter security is currently hop-by-hop only (RFC 6733 Section 2.2) with no end-to-end security solution, leaving intermediate Diameter peers able to tamper with AVP contents.

security, diameter, v6ops

wire-format §3.5

The Port-Set-Identifier AVP (code 639) is a structured OctetString of exactly 4 octets (total AVP length 12): Offset (8-bit unsigned, values 0–15), PSIDLength (8-bit unsigned, values 0 to 16-a), and PSIDValue (16-bit, PSID right-justified in low-order k bits). A PSIDLength of 0 means no PSID.

diameter, v6ops