draft-ietf-softwire-map-radius-04.txt   draft-ietf-softwire-map-radius-05.txt 
Softwire S. Jiang Softwire S. Jiang
Internet-Draft Huawei Technologies Co., Ltd Internet-Draft Huawei Technologies Co., Ltd
Intended status: Standards Track Y. Fu Intended status: Standards Track Y. Fu
Expires: December 24, 2015 CNNIC Expires: June 25, 2016 CNNIC
B. Liu B. Liu
Huawei Technologies Co., Ltd Huawei Technologies Co., Ltd
P. Deacon P. Deacon
IEA Software, Inc. IEA Software, Inc.
June 22, 2015 December 23, 2015
RADIUS Attribute for MAP RADIUS Attribute for MAP
draft-ietf-softwire-map-radius-04 draft-ietf-softwire-map-radius-05
Abstract Abstract
Mapping of Address and Port (MAP) is a stateless mechanism for Mapping of Address and Port (MAP) is a stateless mechanism for
running IPv4 over IPv6-only infrastructure. It provides both IPv4 running IPv4 over IPv6-only infrastructure. It provides both IPv4
and IPv6 connectivity services simultaneously during the IPv4/IPv6 and IPv6 connectivity services simultaneously during the IPv4/IPv6
co-existing period. The Dynamic Host Configuration Protocol for IPv6 co-existing period. The Dynamic Host Configuration Protocol for IPv6
(DHCPv6) MAP options has been defined to configure MAP Customer Edge (DHCPv6) MAP options has been defined to configure MAP Customer Edge
(CE). However, in many networks, the configuration information may (CE). However, in many networks, the configuration information may
be stored in Authentication Authorization and Accounting (AAA) be stored in Authentication Authorization and Accounting (AAA)
skipping to change at page 1, line 48 skipping to change at page 1, line 48
Internet-Drafts are working documents of the Internet Engineering Internet-Drafts are working documents of the Internet Engineering
Task Force (IETF). Note that other groups may also distribute Task Force (IETF). Note that other groups may also distribute
working documents as Internet-Drafts. The list of current Internet- working documents as Internet-Drafts. The list of current Internet-
Drafts is at http://datatracker.ietf.org/drafts/current/. Drafts is at http://datatracker.ietf.org/drafts/current/.
Internet-Drafts are draft documents valid for a maximum of six months Internet-Drafts are draft documents valid for a maximum of six months
and may be updated, replaced, or obsoleted by other documents at any and may be updated, replaced, or obsoleted by other documents at any
time. It is inappropriate to use Internet-Drafts as reference time. It is inappropriate to use Internet-Drafts as reference
material or to cite them other than as "work in progress." material or to cite them other than as "work in progress."
This Internet-Draft will expire on December 24, 2015. This Internet-Draft will expire on June 25, 2016.
Copyright Notice Copyright Notice
Copyright (c) 2015 IETF Trust and the persons identified as the Copyright (c) 2015 IETF Trust and the persons identified as the
document authors. All rights reserved. document authors. All rights reserved.
This document is subject to BCP 78 and the IETF Trust's Legal This document is subject to BCP 78 and the IETF Trust's Legal
Provisions Relating to IETF Documents Provisions Relating to IETF Documents
(http://trustee.ietf.org/license-info) in effect on the date of (http://trustee.ietf.org/license-info) in effect on the date of
publication of this document. Please review these documents publication of this document. Please review these documents
skipping to change at page 3, line 4 skipping to change at page 3, line 4
4.3.3. EA Length Sub Option . . . . . . . . . . . . . . . . 9 4.3.3. EA Length Sub Option . . . . . . . . . . . . . . . . 9
4.3.4. BR-IPv6-Address Sub Option . . . . . . . . . . . . . 9 4.3.4. BR-IPv6-Address Sub Option . . . . . . . . . . . . . 9
4.3.5. PSID Sub Option . . . . . . . . . . . . . . . . . . . 9 4.3.5. PSID Sub Option . . . . . . . . . . . . . . . . . . . 9
4.3.6. PSID Length Sub Option . . . . . . . . . . . . . . . 10 4.3.6. PSID Length Sub Option . . . . . . . . . . . . . . . 10
4.3.7. PSID Offset Sub Option . . . . . . . . . . . . . . . 10 4.3.7. PSID Offset Sub Option . . . . . . . . . . . . . . . 10
4.4. Table of attributes . . . . . . . . . . . . . . . . . . . 11 4.4. Table of attributes . . . . . . . . . . . . . . . . . . . 11
5. Diameter Considerations . . . . . . . . . . . . . . . . . . . 11 5. Diameter Considerations . . . . . . . . . . . . . . . . . . . 11
6. IANA Considerations . . . . . . . . . . . . . . . . . . . . . 12 6. IANA Considerations . . . . . . . . . . . . . . . . . . . . . 12
7. Security Considerations . . . . . . . . . . . . . . . . . . . 12 7. Security Considerations . . . . . . . . . . . . . . . . . . . 12
8. Acknowledgements . . . . . . . . . . . . . . . . . . . . . . 12 8. Acknowledgements . . . . . . . . . . . . . . . . . . . . . . 12
9. References . . . . . . . . . . . . . . . . . . . . . . . . . 12 9. References . . . . . . . . . . . . . . . . . . . . . . . . . 13
9.1. Normative References . . . . . . . . . . . . . . . . . . 13 9.1. Normative References . . . . . . . . . . . . . . . . . . 13
9.2. Informative References . . . . . . . . . . . . . . . . . 13 9.2. Informative References . . . . . . . . . . . . . . . . . 13
Authors' Addresses . . . . . . . . . . . . . . . . . . . . . . . 14 Authors' Addresses . . . . . . . . . . . . . . . . . . . . . . . 14
1. Introduction 1. Introduction
Recently providers start to deploy IPv6 and consider how to transit Recently providers start to deploy IPv6 and consider how to transit
to IPv6. Mapping of Address and Port (MAP)[I-D.ietf-softwire-map] is to IPv6. Mapping of Address and Port (MAP)[I-D.ietf-softwire-map] is
a stateless mechanism for running IPv4 over IPv6-only infrastructure. a stateless mechanism for running IPv4 over IPv6-only infrastructure.
It provides both IPv4 and IPv6 connectivity services simultaneously It provides both IPv4 and IPv6 connectivity services simultaneously
skipping to change at page 12, line 44 skipping to change at page 12, line 44
discussed in [I-D.ietf-softwire-map]. Furthermore, generic DHCPv6 discussed in [I-D.ietf-softwire-map]. Furthermore, generic DHCPv6
security mechanisms can be applied DHCPv6 intercommunication between security mechanisms can be applied DHCPv6 intercommunication between
MAP CE and BNG. MAP CE and BNG.
Security considerations for the Diameter protocol are discussed in Security considerations for the Diameter protocol are discussed in
[RFC6733]. [RFC6733].
8. Acknowledgements 8. Acknowledgements
The authors would like to thank the valuable comments made by Peter The authors would like to thank the valuable comments made by Peter
Lothberg, Wojciech Dec, and Suresh Krishnan for this document. Lothberg, Wojciech Dec, Suresh Krishnan and Ross Chandler for this
document.
This document was produced using the xml2rfc tool [RFC2629]. This document was produced using the xml2rfc tool [RFC2629].
9. References 9. References
9.1. Normative References 9.1. Normative References
[RFC2119] Bradner, S., "Key words for use in RFCs to Indicate [RFC2119] Bradner, S., "Key words for use in RFCs to Indicate
Requirement Levels", BCP 14, RFC 2119, March 1997. Requirement Levels", BCP 14, RFC 2119,
DOI 10.17487/RFC2119, March 1997,
<http://www.rfc-editor.org/info/rfc2119>.
[RFC2865] Rigney, C., Willens, S., Rubens, A., and W. Simpson, [RFC2865] Rigney, C., Willens, S., Rubens, A., and W. Simpson,
"Remote Authentication Dial In User Service (RADIUS)", RFC "Remote Authentication Dial In User Service (RADIUS)",
2865, June 2000. RFC 2865, DOI 10.17487/RFC2865, June 2000,
<http://www.rfc-editor.org/info/rfc2865>.
[RFC3162] Aboba, B., Zorn, G., and D. Mitton, "RADIUS and IPv6", RFC [RFC3162] Aboba, B., Zorn, G., and D. Mitton, "RADIUS and IPv6",
3162, August 2001. RFC 3162, DOI 10.17487/RFC3162, August 2001,
<http://www.rfc-editor.org/info/rfc3162>.
[RFC3315] Droms, R., Bound, J., Volz, B., Lemon, T., Perkins, C., [RFC3315] Droms, R., Ed., Bound, J., Volz, B., Lemon, T., Perkins,
and M. Carney, "Dynamic Host Configuration Protocol for C., and M. Carney, "Dynamic Host Configuration Protocol
IPv6 (DHCPv6)", RFC 3315, July 2003. for IPv6 (DHCPv6)", RFC 3315, DOI 10.17487/RFC3315, July
2003, <http://www.rfc-editor.org/info/rfc3315>.
[RFC3580] Congdon, P., Aboba, B., Smith, A., Zorn, G., and J. Roese, [RFC3580] Congdon, P., Aboba, B., Smith, A., Zorn, G., and J. Roese,
"IEEE 802.1X Remote Authentication Dial In User Service "IEEE 802.1X Remote Authentication Dial In User Service
(RADIUS) Usage Guidelines", RFC 3580, September 2003. (RADIUS) Usage Guidelines", RFC 3580,
DOI 10.17487/RFC3580, September 2003,
<http://www.rfc-editor.org/info/rfc3580>.
[RFC5080] Nelson, D. and A. DeKok, "Common Remote Authentication [RFC5080] Nelson, D. and A. DeKok, "Common Remote Authentication
Dial In User Service (RADIUS) Implementation Issues and Dial In User Service (RADIUS) Implementation Issues and
Suggested Fixes", RFC 5080, December 2007. Suggested Fixes", RFC 5080, DOI 10.17487/RFC5080, December
2007, <http://www.rfc-editor.org/info/rfc5080>.
[RFC6158] DeKok, A. and G. Weber, "RADIUS Design Guidelines", BCP [RFC6158] DeKok, A., Ed. and G. Weber, "RADIUS Design Guidelines",
158, RFC 6158, March 2011. BCP 158, RFC 6158, DOI 10.17487/RFC6158, March 2011,
<http://www.rfc-editor.org/info/rfc6158>.
[RFC6929] DeKok, A. and A. Lior, "Remote Authentication Dial In User [RFC6929] DeKok, A. and A. Lior, "Remote Authentication Dial In User
Service (RADIUS) Protocol Extensions", RFC 6929, April Service (RADIUS) Protocol Extensions", RFC 6929,
2013. DOI 10.17487/RFC6929, April 2013,
<http://www.rfc-editor.org/info/rfc6929>.
9.2. Informative References 9.2. Informative References
[I-D.ietf-softwire-map] [I-D.ietf-softwire-map]
Troan, O., Dec, W., Li, X., Bao, C., Matsushima, S., Troan, O., Dec, W., Li, X., Bao, C., Matsushima, S.,
Murakami, T., and T. Taylor, "Mapping of Address and Port Murakami, T., and T. Taylor, "Mapping of Address and Port
with Encapsulation (MAP)", draft-ietf-softwire-map-13 with Encapsulation (MAP)", draft-ietf-softwire-map-13
(work in progress), March 2015. (work in progress), March 2015.
[I-D.ietf-softwire-map-dhcp] [I-D.ietf-softwire-map-dhcp]
Mrugalski, T., Troan, O., Farrer, I., Perreault, S., Dec, Mrugalski, T., Troan, O., Farrer, I., Perreault, S., Dec,
W., Bao, C., Yeh, L., and X. Deng, "DHCPv6 Options for W., Bao, C., Yeh, L., and X. Deng, "DHCPv6 Options for
configuration of Softwire Address and Port Mapped configuration of Softwire Address and Port Mapped
Clients", draft-ietf-softwire-map-dhcp-12 (work in Clients", draft-ietf-softwire-map-dhcp-12 (work in
progress), March 2015. progress), March 2015.
[RFC2607] Aboba, B. and J. Vollbrecht, "Proxy Chaining and Policy [RFC2607] Aboba, B. and J. Vollbrecht, "Proxy Chaining and Policy
Implementation in Roaming", RFC 2607, June 1999. Implementation in Roaming", RFC 2607,
DOI 10.17487/RFC2607, June 1999,
<http://www.rfc-editor.org/info/rfc2607>.
[RFC2629] Rose, M., "Writing I-Ds and RFCs using XML", RFC 2629, [RFC2629] Rose, M., "Writing I-Ds and RFCs using XML", RFC 2629,
June 1999. DOI 10.17487/RFC2629, June 1999,
<http://www.rfc-editor.org/info/rfc2629>.
[RFC2869] Rigney, C., Willats, W., and P. Calhoun, "RADIUS [RFC2869] Rigney, C., Willats, W., and P. Calhoun, "RADIUS
Extensions", RFC 2869, June 2000. Extensions", RFC 2869, DOI 10.17487/RFC2869, June 2000,
<http://www.rfc-editor.org/info/rfc2869>.
[RFC4301] Kent, S. and K. Seo, "Security Architecture for the [RFC4301] Kent, S. and K. Seo, "Security Architecture for the
Internet Protocol", RFC 4301, December 2005. Internet Protocol", RFC 4301, DOI 10.17487/RFC4301,
December 2005, <http://www.rfc-editor.org/info/rfc4301>.
[RFC5226] Narten, T. and H. Alvestrand, "Guidelines for Writing an [RFC5226] Narten, T. and H. Alvestrand, "Guidelines for Writing an
IANA Considerations Section in RFCs", BCP 26, RFC 5226, IANA Considerations Section in RFCs", BCP 26, RFC 5226,
May 2008. DOI 10.17487/RFC5226, May 2008,
<http://www.rfc-editor.org/info/rfc5226>.
[RFC6733] Fajardo, V., Arkko, J., Loughney, J., and G. Zorn, [RFC6733] Fajardo, V., Ed., Arkko, J., Loughney, J., and G. Zorn,
"Diameter Base Protocol", RFC 6733, October 2012. Ed., "Diameter Base Protocol", RFC 6733,
DOI 10.17487/RFC6733, October 2012,
<http://www.rfc-editor.org/info/rfc6733>.
Authors' Addresses Authors' Addresses
Sheng Jiang Sheng Jiang
Huawei Technologies Co., Ltd Huawei Technologies Co., Ltd
Q14, Huawei Campus, No.156 Beiqing Road Q14, Huawei Campus, No.156 Beiqing Road
Hai-Dian District, Beijing, 100095 Hai-Dian District, Beijing, 100095
P.R. China P.R. China
Email: jiangsheng@huawei.com Email: jiangsheng@huawei.com
Yu Fu Yu Fu
CNNIC CNNIC
 End of changes. 22 change blocks. 
28 lines changed or deleted 47 lines changed or added

This html diff was produced by rfcdiff 1.42. The latest version is available from http://tools.ietf.org/tools/rfcdiff/