draft-ietf-softwire-hs-framework-l2tpv2-12.txt   draft-ietf-softwire-hs-framework-l2tpv2-13.txt 
Softwires Working Group B. Storer Softwires Working Group B. Storer
Internet-Draft C. Pignataro, Ed. Internet-Draft C. Pignataro, Ed.
Intended status: Standards Track M. Dos Santos Intended status: Standards Track M. Dos Santos
Expires: September 7, 2009 Cisco Systems Expires: October 15, 2009 Cisco Systems
B. Stevant, Ed. B. Stevant, Ed.
TELECOM Bretagne TELECOM Bretagne
J. Tremblay J. Tremblay
Videotron Ltd. Videotron Ltd.
March 6, 2009 April 13, 2009
Softwire Hub & Spoke Deployment Framework with L2TPv2 Softwire Hub & Spoke Deployment Framework with L2TPv2
draft-ietf-softwire-hs-framework-l2tpv2-12 draft-ietf-softwire-hs-framework-l2tpv2-13
Status of this Memo Status of this Memo
This Internet-Draft is submitted to IETF in full conformance with the This Internet-Draft is submitted to IETF in full conformance with the
provisions of BCP 78 and BCP 79. This document may contain material provisions of BCP 78 and BCP 79. This document may contain material
from IETF Documents or IETF Contributions published or made publicly from IETF Documents or IETF Contributions published or made publicly
available before November 10, 2008. The person(s) controlling the available before November 10, 2008. The person(s) controlling the
copyright in some of this material may not have granted the IETF copyright in some of this material may not have granted the IETF
Trust the right to allow modifications of such material outside the Trust the right to allow modifications of such material outside the
IETF Standards Process. Without obtaining an adequate license from IETF Standards Process. Without obtaining an adequate license from
skipping to change at page 1, line 47 skipping to change at page 1, line 47
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."
The list of current Internet-Drafts can be accessed at The list of current Internet-Drafts can be accessed at
http://www.ietf.org/ietf/1id-abstracts.txt. http://www.ietf.org/ietf/1id-abstracts.txt.
The list of Internet-Draft Shadow Directories can be accessed at The list of Internet-Draft Shadow Directories can be accessed at
http://www.ietf.org/shadow.html. http://www.ietf.org/shadow.html.
This Internet-Draft will expire on September 7, 2009. This Internet-Draft will expire on October 15, 2009.
Copyright Notice Copyright Notice
Copyright (c) 2009 IETF Trust and the persons identified as the Copyright (c) 2009 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 in effect on the date of Provisions Relating to IETF Documents in effect on the date of
publication of this document (http://trustee.ietf.org/license-info). publication of this document (http://trustee.ietf.org/license-info).
Please review these documents carefully, as they describe your rights Please review these documents carefully, as they describe your rights
and restrictions with respect to this document. and restrictions with respect to this document.
skipping to change at page 3, line 50 skipping to change at page 3, line 50
6.3. Possible Address Provisioning Scenarios . . . . . . . . . 32 6.3. Possible Address Provisioning Scenarios . . . . . . . . . 32
6.3.1. Scenarios for IPv6 . . . . . . . . . . . . . . . . . . 32 6.3.1. Scenarios for IPv6 . . . . . . . . . . . . . . . . . . 32
6.3.2. Scenarios for IPv4 . . . . . . . . . . . . . . . . . . 33 6.3.2. Scenarios for IPv4 . . . . . . . . . . . . . . . . . . 33
7. Considerations about Address Stability . . . . . . . . . . . . 33 7. Considerations about Address Stability . . . . . . . . . . . . 33
8. Considerations about RADIUS Integration . . . . . . . . . . . 34 8. Considerations about RADIUS Integration . . . . . . . . . . . 34
8.1. Softwire Endpoints . . . . . . . . . . . . . . . . . . . . 34 8.1. Softwire Endpoints . . . . . . . . . . . . . . . . . . . . 34
8.1.1. IPv6 Softwires . . . . . . . . . . . . . . . . . . . . 34 8.1.1. IPv6 Softwires . . . . . . . . . . . . . . . . . . . . 34
8.1.2. IPv4 Softwires . . . . . . . . . . . . . . . . . . . . 34 8.1.2. IPv4 Softwires . . . . . . . . . . . . . . . . . . . . 34
8.2. Delegated Prefixes . . . . . . . . . . . . . . . . . . . . 35 8.2. Delegated Prefixes . . . . . . . . . . . . . . . . . . . . 34
8.2.1. IPv6 Prefixes . . . . . . . . . . . . . . . . . . . . 35 8.2.1. IPv6 Prefixes . . . . . . . . . . . . . . . . . . . . 34
8.2.2. IPv4 Prefixes . . . . . . . . . . . . . . . . . . . . 35 8.2.2. IPv4 Prefixes . . . . . . . . . . . . . . . . . . . . 35
9. Considerations for Maintenance and Statistics . . . . . . . . 35 9. Considerations for Maintenance and Statistics . . . . . . . . 35
9.1. RADIUS Accounting . . . . . . . . . . . . . . . . . . . . 35 9.1. RADIUS Accounting . . . . . . . . . . . . . . . . . . . . 35
9.2. MIBs . . . . . . . . . . . . . . . . . . . . . . . . . . . 36 9.2. MIBs . . . . . . . . . . . . . . . . . . . . . . . . . . . 36
10. Security Considerations . . . . . . . . . . . . . . . . . . . 36 10. Security Considerations . . . . . . . . . . . . . . . . . . . 36
11. IANA Considerations . . . . . . . . . . . . . . . . . . . . . 37 11. IANA Considerations . . . . . . . . . . . . . . . . . . . . . 37
skipping to change at page 34, line 34 skipping to change at page 34, line 34
If the RADIUS server includes a Framed-Interface-Id attribute If the RADIUS server includes a Framed-Interface-Id attribute
[RFC3162], the Softwire Concentrator must send it to the Softwire [RFC3162], the Softwire Concentrator must send it to the Softwire
Initiator in the Interface-Identifier field of its IPV6CP Initiator in the Interface-Identifier field of its IPV6CP
Configuration Request message. Configuration Request message.
If the Framed-IPv6-Prefix attribute [RFC3162] is included, that If the Framed-IPv6-Prefix attribute [RFC3162] is included, that
prefix must be used in the router advertisements sent to the SI. If prefix must be used in the router advertisements sent to the SI. If
Framed-IPv6-Prefix is not present but Framed-IPv6-Pool is, the SC Framed-IPv6-Prefix is not present but Framed-IPv6-Pool is, the SC
must choose a prefix from that pool to send RAs. must choose a prefix from that pool to send RAs.
If none of the attributes above are included but the AAA server
returns the Tunnel-Client-Endpoint and Tunnel-Server-Endpoint
attributes [RFC2868] with the correct address family, these must be
used in the IPV6CP Interface-Identifier and for the Router
Advertisements.
8.1.2. IPv4 Softwires 8.1.2. IPv4 Softwires
If the Framed-IP-Address attribute [RFC2865] is present, the Softwire If the Framed-IP-Address attribute [RFC2865] is present, the Softwire
Concentrator must provide that address to the Softwire Initiator Concentrator must provide that address to the Softwire Initiator
during IPCP address negotiation. That is, when the Softwire during IPCP address negotiation. That is, when the Softwire
Initiator requests an IP address from the Softwire Concentrator, the Initiator requests an IP address from the Softwire Concentrator, the
address provided should be the Framed-IP-Address. address provided should be the Framed-IP-Address.
If the Framed-IP-Address attribute is not present and the Tunnel-
Client-Endpoint and Tunnel-Server-Endpoint attributes [RFC2868] are
present and of the correct address family, these should be used in
the IPCP IP-Address configuration option.
8.2. Delegated Prefixes 8.2. Delegated Prefixes
8.2.1. IPv6 Prefixes 8.2.1. IPv6 Prefixes
If the attribute Delegated-IPv6-Prefix [RFC4818] is present in the If the attribute Delegated-IPv6-Prefix [RFC4818] is present in the
RADIUS Access-Accept message, it must be used by the Softwire RADIUS Access-Accept message, it must be used by the Softwire
Concentrator for the delegation of the IPv6 prefix. Since the prefix Concentrator for the delegation of the IPv6 prefix. Since the prefix
delegation is performed by DHCPv6 and the attribute is linked to a delegation is performed by DHCPv6 and the attribute is linked to a
username, the SC must associate the DHCP Unique Identifier (DUID) of username, the SC must associate the DHCP Unique Identifier (DUID) of
a DHCPv6 request to the tunnel it came from and its user. a DHCPv6 request to the tunnel it came from and its user.
skipping to change at page 35, line 28 skipping to change at page 35, line 17
mechanism proposed in [I-D.ietf-dhc-v6-relay-radius]. In this case, mechanism proposed in [I-D.ietf-dhc-v6-relay-radius]. In this case,
during the Softwire authentication phase, PPP collects the RADIUS during the Softwire authentication phase, PPP collects the RADIUS
attributes for the user such as Delegated-IPv6-Prefix. A specific attributes for the user such as Delegated-IPv6-Prefix. A specific
DHCPv6 relay is assigned to the Softwire. The DHCPv6 relay fills in DHCPv6 relay is assigned to the Softwire. The DHCPv6 relay fills in
these attributes in the Relay agent RADIUS Attribute Option (RRAO) these attributes in the Relay agent RADIUS Attribute Option (RRAO)
DHCPv6 option, before forwarding the DHCPv6 requests to the DHCPv6 DHCPv6 option, before forwarding the DHCPv6 requests to the DHCPv6
server. server.
8.2.2. IPv4 Prefixes 8.2.2. IPv4 Prefixes
The combination of the Framed-IP-Address and Framed-IP-Netmask RADIUS does not define an attribute for the delegated IPv4 Prefix.
attributes [RFC2865] may be used by the Softwire Concentrator to Attributes indicating an IPv4 prefix and its length (for instance the
delegate an IPv4 prefix to the Softwire Initiator. combination of the Framed-IP-Address and Framed-IP-Netmask attributes
[RFC2865]) may be used by the Softwire Concentrator to delegate an
IPv4 prefix to the Softwire Initiator. The Softwire Concentrator
must add a corresponding route with the Softwire Initiator as next-
hop.
As this practice had been used, the inclusion of the Framed-IP-
Netmask attribute along with the Framed-IP-Address attribute tells
the Softwire Concentrator to delegate an IPv4 prefix to the Softwire
Initiator (e.g., in the IPv4 over IPv6 scenarios where the Softwire
Initiator is a router, see Section 3.2.2 and Section 3.2.4), as the
SC should forward packets destined to any IPv4 address in the prefix
to the SI.
9. Considerations for Maintenance and Statistics 9. Considerations for Maintenance and Statistics
Existing protocol mechanics for conveying adjunct or accessory Existing protocol mechanics for conveying adjunct or accessory
information for logging purposes, including L2TPv2 and RADIUS information for logging purposes, including L2TPv2 and RADIUS
methods, can include informational text that the behavior is methods, can include informational text that the behavior is
according to the Softwire "Hub and Spoke" framework (following the according to the Softwire "Hub and Spoke" framework (following the
implementation details specified in this document). implementation details specified in this document).
9.1. RADIUS Accounting 9.1. RADIUS Accounting
skipping to change at page 39, line 5 skipping to change at page 39, line 5
[RFC3948] Huttunen, A., Swander, B., Volpe, V., DiBurro, L., and M. [RFC3948] Huttunen, A., Swander, B., Volpe, V., DiBurro, L., and M.
Stenberg, "UDP Encapsulation of IPsec ESP Packets", Stenberg, "UDP Encapsulation of IPsec ESP Packets",
RFC 3948, January 2005. RFC 3948, January 2005.
[RFC4818] Salowey, J. and R. Droms, "RADIUS Delegated-IPv6-Prefix [RFC4818] Salowey, J. and R. Droms, "RADIUS Delegated-IPv6-Prefix
Attribute", RFC 4818, April 2007. Attribute", RFC 4818, April 2007.
[RFC4862] Thomson, S., Narten, T., and T. Jinmei, "IPv6 Stateless [RFC4862] Thomson, S., Narten, T., and T. Jinmei, "IPv6 Stateless
Address Autoconfiguration", RFC 4862, September 2007. Address Autoconfiguration", RFC 4862, September 2007.
[RFC5072] S.Varada, Haskin, D., and E. Allen, "IP Version 6 over [RFC5072] S.Varada, Haskins, D., and E. Allen, "IP Version 6 over
PPP", RFC 5072, September 2007. PPP", RFC 5072, September 2007.
13.2. Informative References 13.2. Informative References
[I-D.ietf-dhc-subnet-alloc] [I-D.ietf-dhc-subnet-alloc]
Johnson, R., "Subnet Allocation Option", Johnson, R., Kumarasamy, J., Kinnear, K., and M. Stapp,
draft-ietf-dhc-subnet-alloc-07 (work in progress), "Subnet Allocation Option", draft-ietf-dhc-subnet-alloc-09
July 2008. (work in progress), March 2009.
[I-D.ietf-dhc-v6-relay-radius] [I-D.ietf-dhc-v6-relay-radius]
Lau, W., "DHCPv6 Relay agent RADIUS Attribute Option", Lau, W., "DHCPv6 Relay agent RADIUS Attribute Option",
draft-ietf-dhc-v6-relay-radius-02 (work in progress), draft-ietf-dhc-v6-relay-radius-02 (work in progress),
February 2006. February 2006.
[I-D.ietf-softwire-security-requirements] [I-D.ietf-softwire-security-requirements]
Yamamoto, S., Williams, C., Parent, F., and H. Yokota, Yamamoto, S., Williams, C., Parent, F., and H. Yokota,
"Softwire Security Analysis and Requirements", "Softwire Security Analysis and Requirements",
draft-ietf-softwire-security-requirements-06 (work in draft-ietf-softwire-security-requirements-07 (work in
progress), October 2008. progress), March 2009.
[I-D.stevant-softwire-accounting] [I-D.stevant-softwire-accounting]
Stevant, B., "Accounting on Softwires", Stevant, B., "Accounting on Softwires",
draft-stevant-softwire-accounting-01 (work in progress), draft-stevant-softwire-accounting-01 (work in progress),
October 2006. October 2006.
[RFC1471] Kastenholz, F., "The Definitions of Managed Objects for [RFC1471] Kastenholz, F., "The Definitions of Managed Objects for
the Link Control Protocol of the Point-to-Point Protocol", the Link Control Protocol of the Point-to-Point Protocol",
RFC 1471, June 1993. RFC 1471, June 1993.
 End of changes. 11 change blocks. 
26 lines changed or deleted 27 lines changed or added

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