Dynamic Prefix Configuration of MAP-T and MAP-E Parameters via BGP

Dynamic Prefix Configuration of MAP-T and MAP-E Parameters via BGP Juniper Networks

18 Buckingham Dr Manalapan 07726 NJ US mnayman@juniper.net

AT&T

12186 Diamond Creek Dr Frisco 75035 TX US ar977m@example.com

This document proposes an extension to the current MAP-T (Mapping of Address and Port using Translation) and MAP-E (Mapping of Address and Port with Encapsulation) configuration mechanisms. It allows for dynamically learned and programmed MAP-T or MAP-E prefix value parameters via BGP-learned prefixes marked with extended community attributes, enabling a more flexible and scalable approach compared to static configuration.

MAP-T and MAP-E are mechanisms that enable the transition from IPv4 to IPv6 by mapping IPv4 addresses and ports to IPv6 addresses (RFC 7599 and RFC 7597 respectively). The current standard requires static configuration of MAP-T and MAP-E parameters, which can be cumbersome and inflexible in large-scale networks. This document proposes a method to dynamically configure MAP-T and MAP-E parameters using BGP-learned prefixes with extended community attributes, enhancing the efficiency and adaptability of network configurations.

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 when, and only when, they appear in all capitals, as shown here.

The proposed solution introduces dynamic MAP-T and MAP-E parameter configuration using BGP-learned prefixes. This approach allows for the dynamic assignment of MAP-T and MAP-E domain-specific parameters, such as the DMR prefix, IPv4 prefix, and MAP-T/MAP-E prefix, based on BGP updates. To facilitate this dynamic configuration, new BGP extended communities will be defined. These communities will be associated with specific softwire concentrators and prefixes:

dmr:{number}:{prefix}
ipv4:{number}:{prefix}
map:{number}:{prefix}

This initiative leverages the framework established in RFC 7153 for defining new BGP communities. The new BGP communities are required to indicate where the prefix will be imported and dynamically configured. By associating these communities with specific MAP-T and MAP-E parameters, the BGP updates can precisely control the importation and configuration of these prefixes within the network. This ensures that the dynamic parameters are applied accurately and efficiently, allowing for real-time adaptability to network changes. The community attribute dmr refers to the DMR prefix (Softwire DMR IPv6 Address). The community attribute ipv4 refers to the MAP-T/MAP-E domain's rule IPv4 prefix/length. The community attribute map refers to the MAP-T/MAP-E domain's rule IPv6 prefix/length. The {number} refers to the name or number or term of the MAP-T/MAP-E softwire concentrator. Since a MAP-T BR can have multiple MAP-T domains with different prefixes, this helps identify where the prefix will be associated. The {prefix} refers to the actual MAP-T or MAP-E prefix. These extended community attributes are associated with the following Address Family Identifier (AFI) and Subsequent Address Family Identifier (SAFI) combinations as specified in IANA and descbied in and . This initiative is OPTIONAL for MAP-T and MAP-E; it is not necessary for them to function. It provides an optional mechanism to enhance the configuration process. Users can take advantage of BGP-advertised MAP-T and MAP-E parameters by leveraging the newly defined BGP extended communities to dynamically update their configurations. When a BGP route containing one of the specified extended communities (e.g., dmr:{number}:{prefix}, ipv4:{number}:{prefix}, or map:{number}:{prefix}) is received, the router can automatically parse these communities and update the MAP-T/MAP-E configuration accordingly. This approach ensures that the configuration is always up-to-date with the latest network changes, reduces administrative overhead, and enhances scalability by allowing centralized management of MAP-T and MAP-E parameters through BGP. The extended community attributes defined in this document are **Transitive Extended Communities**. This designation is essential because MAP-T and MAP-E parameters need to be propagated across different BGP sessions, ensuring that routers throughout the network can dynamically configure themselves based on these attributes, thus maintaining consistency and efficiency in the network configuration.

dmr:{number}:{prefix}
ipv4:{number}:{prefix}
map:{number}:{prefix}

This initiative leverages the framework established in for defining new BGP communities. The new BGP communities are required to indicate where the prefix will be imported and dynamically configured. By associating these communities with specific MAP-T and MAP-E parameters, the BGP updates can precisely control the importation and configuration of these prefixes within the network. This ensures that the dynamic parameters are applied accurately and efficiently, allowing for real-time adaptability to network changes. The community attribute dmr refers to the DMR prefix (Softwire DMR IPv6 Address). The community attribute ipv4 refers to the MAP-T/MAP-E domain's rule IPv4 prefix/length. The community attribute map refers to the MAP-T/MAP-E domain's rule IPv6 prefix/length. The {number} refers to the name or number or term of the MAP-T/MAP-E softwire concentrator. Since a MAP-T BR can have multiple MAP-T domains with different prefixes, this helps identify where the prefix will be associated. The {prefix} refers to the actual MAP-T or MAP-E prefix. These extended community attributes are associated with the following Address Family Identifier (AFI) and Subsequent Address Family Identifier (SAFI) combinations as specified in IANA:

IPv4 Unicast (AFI: 1, SAFI: 1)
IPv6 Unicast (AFI: 2, SAFI: 1)
VPNv4 Unicast (AFI: 1, SAFI: 128)
VPNv6 Unicast (AFI: 2, SAFI: 128)

This initiative is OPTIONAL for MAP-T and MAP-E; it is not necessary for them to function. It provides an optional mechanism to enhance the configuration process. Users can take advantage of BGP-advertised MAP-T and MAP-E parameters by leveraging the newly defined BGP extended communities to dynamically update their configurations. When a BGP route containing one of the specified extended communities (e.g., dmr:{number}:{prefix}, ipv4:{number}:{prefix}, or map:{number}:{prefix}) is received, the router can automatically parse these communities and update the MAP-T/MAP-E configuration accordingly. This approach ensures that the configuration is always up-to-date with the latest network changes, reduces administrative overhead, and enhances scalability by allowing centralized management of MAP-T and MAP-E parameters through BGP. The extended community attributes defined in this document are **Transitive Extended Communities**. This designation is essential because MAP-T and MAP-E parameters need to be propagated across different BGP sessions, ensuring that routers throughout the network can dynamically configure themselves based on these attributes, thus maintaining consistency and efficiency in the network configuration.

AFI: Address Family Identifier BGP: Border Gateway Protocol IP: Internet Protocol IPv4: Internet Protocol version 4 IPv6: Internet Protocol version 6 MAP-T: Mapping of Address and Port using Translation MAP-E: Mapping of Address and Port with Encapsulation NLRI: Network Layer Reachability Information VPN: Virtual Private Network SAFI: Subsequent Address Family Identifier

Acknowledgements To be added later

Contributors To be added later