+1 Specifically agree on this point as a co-author.
The motivation of this draft was based on the Gang said common deployment schema in real production networks, in which user configuration information is usually managed by AAA. For example, in fixed broadband networks, the MAP configuration information might most probably stored in AAA servers. And the MAP DHCP configuration provisioning are most probably through BNG. So the MAP radius attributes are needed to propagate the information from AAA servers to BNGs, so that the BNG could form correspondent MAP DHCP options to the CEs. B.R. Bing > -----Original Message----- > From: [email protected] [mailto:[email protected]] On > Behalf Of GangChen > Sent: Friday, May 31, 2013 12:53 AM > To: Suresh Krishnan > Cc: Softwires WG; Yong Cui > Subject: Re: [Softwires] Call for adoption of > draft-jiang-softwire-map-radius-04 as wg draft > > Support > This interactive radius support for MAP is useful when it comes to > real deployment. ISPs are likely use radius to authorize and manage > MAP subscribers. > > BRs > > Gang > > 2013/5/24, Suresh Krishnan <[email protected]>: > > Hi all, > > This call is being initiated to determine whether there is WG > > consensus towards adoption of draft-jiang-softwire-map-radius-04 as a > > softwire WG draft. Please state whether or not you're in favor of the > > adoption by replying to this email. If you are not in favor, please also > > state your objections in your response. The call will complete at > > midnight PDT on 2013-06-02. > > > > Regards > > Suresh & Yong > > > > > > > > _______________________________________________ > > Softwires mailing list > > [email protected] > > https://www.ietf.org/mailman/listinfo/softwires > > > _______________________________________________ > Softwires mailing list > [email protected] > https://www.ietf.org/mailman/listinfo/softwires _______________________________________________ Softwires mailing list [email protected] https://www.ietf.org/mailman/listinfo/softwires
