RADIUS Attributes for Softwire Mechanisms Based on Address plus Port (A+P)
Draft of message to be sent after approval:
From: The IESG <email@example.com> To: IETF-Announce <firstname.lastname@example.org> Cc: The IESG <email@example.com>, firstname.lastname@example.org, Ian Farrer <email@example.com>, firstname.lastname@example.org, email@example.com, Yong Cui <firstname.lastname@example.org>, email@example.com, firstname.lastname@example.org, email@example.com Subject: Protocol Action: 'RADIUS Attributes for Address plus Port (A+P) based Softwire Mechanisms' to Proposed Standard (draft-ietf-softwire-map-radius-26.txt) The IESG has approved the following document: - 'RADIUS Attributes for Address plus Port (A+P) based Softwire Mechanisms' (draft-ietf-softwire-map-radius-26.txt) as Proposed Standard This document is the product of the Softwires Working Group. The IESG contact persons are Éric Vyncke and Suresh Krishnan. A URL of this Internet Draft is: https://datatracker.ietf.org/doc/draft-ietf-softwire-map-radius/
== Technical Summary == IPv4-over-IPv6 transition mechanisms provide IPv4 connectivity services over IPv6 native networks during the IPv4/IPv6 co-existence period. DHCPv6 options have been defined for configuring clients for Lightweight 4over6, Mapping of Address and Port with Encapsulation (MAP-E) and Mapping of Address and Port using Translation (MAP-T) unicast softwire mechanisms, and also multicast softwires. However, in many networks, configuration information is stored in an Authentication, Authorization, and Accounting server which utilizes the RADIUS protocol to provide centralized management for users. When a new transition mechanism is developed, new RADIUS attributes need to be defined correspondingly. This document defines new RADIUS attributes to carry Address plus Port based softwire configuration parameters from an Authentication, Authorization, and Accounting server to a Broadband Network Gateway. Both unicast and multicast attributes are covered. == Working Group Summary == No points or controversy has been raised during the authoring or review process. The author's original scope was just to define RADIUS attributes for MAP-E & MAP-T based softwire configuration, but by agreement of the WG, the document scope was extended to cover all standards track softwire mechanisms (unicast and multicast) that do not currently have RADIUS configuration defined. == Document Quality == The draft has been reviewed by Alan DeKok (RADEXT) who suggested substantial changes to make the document more readable and in line with recent RADIUS document conventions. Chongfeng Xie from China Telecom made the following statement regarding an implementation: "We have done some implementations when we carried out Lightweight4over6 trial in some provinces of China." Per AD request, there were more reviews from: - opsdir (Al Morton): ready - genart (Joel Halpern): almost ready - intdir (Bernie Volz): ready with issues - secdir (Donald Eastlake): almost ready (note: this review is not reflected yet in the data tracker but authors have issued a revised I-D addressing the review) The main editor of the document was prompt to reply, explain and revise the I-D. == Personnel == Ian Farrer (Softwire co-chair), is the Document Shepherd. Eric Vyncke is the Responsible AD. == IANA Note == IANA is requested to assign the Attribute Types defined in this document from the RADIUS namespace. IANA is requested to create a new registry called "RADIUS Softwire46 Configuration and Multicast Attributes". IANA is requested to create and maintain a new registry entitled "Option Codes Permitted in the Softwire46-Priority Attribute". Revision -24 addresses all issues raised by IANA about -23.