Hi, Med

A new version has been updated based on your comments as below:
>Further, I invite the authors to double check
>Also, you may follow the template defined in

The main changes are as below:
1.We have double checked with the section3.4 of RFC 6158. 
In the scenario of our draft and as described in the RFC 8026, a service
provider's network may have more than one S46 mechanism. 
For example, a ISP's network is configured with MAP and Lightweight 4over6. 
So the radius attribute format defined in section 4.1 is not a fixed data
format based on the scenario as described above.

2.We have changed the format of IPv6 prefix in 4.3.3 to include the reserved
field according to the section 3.10 of RFC8044.

3. We have changed the format of 4.3.4 and 4.3.5 using the sub option/TLV
scheme from RFC6929 and RFC8044 to break out
IPv4 address, IPv6 prefix and other PSID parameters while maintaining the
grouped relationship. And updated the figure of 4.2 accordingly.

Thanks for your comments


-----Original Message-----
From: softwires-boun...@ietf.org [mailto:softwires-boun...@ietf.org] On
Behalf Of internet-dra...@ietf.org
Sent: Monday, August 07, 2017 3:58 PM
To: i-d-annou...@ietf.org
Cc: softwires@ietf.org
Subject: [Softwires] I-D Action: draft-ietf-softwire-map-radius-13.txt

A New Internet-Draft is available from the on-line Internet-Drafts
This draft is a work item of the Softwires WG of the IETF.

        Title           : RADIUS Attribute for Softwire Address plus Port
based Mechanisms
        Authors         : Sheng Jiang
                          Yu Fu
                          Bing Liu
                          Peter Deacon
                          Chongfeng Xie
                          Tianxiang Li
        Filename        : draft-ietf-softwire-map-radius-13.txt
        Pages           : 25
        Date            : 2017-08-07

   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, and Lightweight 4over6.  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
   configuration information from an AAA server to BNG.

The IETF datatracker status page for this draft is:

There are also htmlized versions available at:

A diff from the previous version is available at:

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:

Softwires mailing list

Softwires mailing list

Reply via email to