%% You should probably cite rfc8658 instead of this I-D. @techreport{ietf-softwire-map-radius-15, number = {draft-ietf-softwire-map-radius-15}, type = {Internet-Draft}, institution = {Internet Engineering Task Force}, publisher = {Internet Engineering Task Force}, note = {Work in Progress}, url = {https://datatracker.ietf.org/doc/draft-ietf-softwire-map-radius/15/}, author = {Sheng Jiang and Yu Fu and Bing Liu and Peter Deacon and Chongfeng Xie and Tianxiang Li and Mohamed Boucadair}, title = {{RADIUS Attribute for Softwire Address plus Port based Mechanisms}}, pagetotal = 32, year = 2018, month = mar, day = 21, abstract = {IPv4-over-IPv6 transition mechanisms provide both IPv4 and IPv6 connectivity services simultaneously during the IPv4/IPv6 co-existing period. The Dynamic Host Configuration Protocol for IPv6 (DHCPv6) options have been defined to configure Customer Edge (CE) in MAP-E, MAP-T, Lightweight 4over6 and PREFIX64 option for Multicast Basic Bridging BroadBand (mB4) in multicast scenarios. However, in many networks, the configuration information may be stored in an Authentication Authorization and Accounting (AAA) server, while user configuration information is mainly provided by the Broadband Network Gateway (BNG) through the DHCPv6 protocol. This document defines two new Remote Authentication Dial In User Service (RADIUS) attributes that carry CE or mB4 configuration information from an AAA server to BNG.}, }