Hi all We have updated the 04 version of map radius draft. The main changes are as follow:
1) In the section 3, we change the sentence "When BNG receives the SOLICIT, it SHOULD initiates radius Access-Request message, in which the User-Name attribute SHOULD be filled by the MAP CE MAC address, to the RADIUS server" to "When BNG receives the SOLICIT, it SHOULD initiates radius Access-Request message, in which the User-Name attribute SHOULD be filled by the MAP CE MAC address or interface-id or both, to the RADIUS server." It is based on the comments proposed by Ross Chandler on the mailing list that the User-name attribute can be filled by MAC address or interface-id or both depends on the operational implementation by different vendor. 2) In section 4.2, we have deleted the definition of Default Mapping Rule in the MAP Rule Option because this rule is defined for the MAP-T mode. But the MAP RADIUS attributes designed in this document are especially for the MAP encapsulation mode. Comments are welcome Best Regards Yu -----Original Message----- From: [email protected] [mailto:[email protected]] On Behalf Of [email protected] Sent: Tuesday, June 23, 2015 9:55 AM To: [email protected] Cc: [email protected] Subject: [Softwires] I-D Action: draft-ietf-softwire-map-radius-04.txt A New Internet-Draft is available from the on-line Internet-Drafts directories. This draft is a work item of the Softwires Working Group of the IETF. Title : RADIUS Attribute for MAP Authors : Sheng Jiang Yu Fu Bing Liu Peter Deacon Filename : draft-ietf-softwire-map-radius-04.txt Pages : 15 Date : 2015-06-22 Abstract: Mapping of Address and Port (MAP) is a stateless mechanism for running IPv4 over IPv6-only infrastructure. It provides both IPv4 and IPv6 connectivity services simultaneously during the IPv4/IPv6 co-existing period. The Dynamic Host Configuration Protocol for IPv6 (DHCPv6) MAP options has been defined to configure MAP Customer Edge (CE). However, in many networks, the configuration information may be stored in Authentication Authorization and Accounting (AAA) servers while user configuration is mainly from Broadband Network Gateway (BNG) through DHCPv6 protocol. This document defines a Remote Authentication Dial In User Service (RADIUS) attribute that carries MAP configuration information from AAA server to BNG. The MAP RADIUS attribute are designed following the simplify principle. It provides just enough information to form the correspondent DHCPv6 MAP option. The IETF datatracker status page for this draft is: https://datatracker.ietf.org/doc/draft-ietf-softwire-map-radius/ There's also a htmlized version available at: https://tools.ietf.org/html/draft-ietf-softwire-map-radius-04 A diff from the previous version is available at: https://www.ietf.org/rfcdiff?url2=draft-ietf-softwire-map-radius-04 Please note that it may take a couple of minutes from the time of submission until the htmlized version and diff are available at tools.ietf.org. Internet-Drafts are also available by anonymous FTP at: ftp://ftp.ietf.org/internet-drafts/ _______________________________________________ Softwires mailing list [email protected] https://www.ietf.org/mailman/listinfo/softwires _______________________________________________ Softwires mailing list [email protected] https://www.ietf.org/mailman/listinfo/softwires
