draft-ietf-6man-lineid-00.txt   draft-ietf-6man-lineid-01.txt 
6man Working Group S. Krishnan 6man Working Group S. Krishnan
Internet-Draft A. Kavanagh Internet-Draft A. Kavanagh
Intended status: Standards Track B. Varga Intended status: Standards Track B. Varga
Expires: June 20, 2011 Ericsson Expires: September 15, 2011 Ericsson
S. Ooghe S. Ooghe
Alcatel-Lucent Alcatel-Lucent
E. Nordmark E. Nordmark
Oracle Cisco
December 17, 2010 March 14, 2011
The Line Identification Destination Option The Line Identification Destination Option
draft-ietf-6man-lineid-00 draft-ietf-6man-lineid-01
Abstract Abstract
In Ethernet based aggregation networks, several subscriber premises In Ethernet based aggregation networks, several subscriber premises
may be logically connected to the same interface of an edge router. may be logically connected to the same interface of an edge router.
This document proposes a method for the edge router to identify the This document proposes a method for the edge router to identify the
subscriber premises using the contents of the received Router subscriber premises using the contents of the received Router
Solicitation messages. The applicability is limited to the N:1 VLAN Solicitation messages. The applicability is limited to broadband
allocation model. network deployment scenarios where multiple user ports are mapped to
the same virtual interface on the Edge Router.
Status of this Memo Status of this Memo
This Internet-Draft is submitted in full conformance with the This Internet-Draft is submitted in full conformance with the
provisions of BCP 78 and BCP 79. provisions of BCP 78 and BCP 79.
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 June 20, 2011. This Internet-Draft will expire on September 15, 2011.
Copyright Notice Copyright Notice
Copyright (c) 2010 IETF Trust and the persons identified as the Copyright (c) 2011 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
carefully, as they describe your rights and restrictions with respect carefully, as they describe your rights and restrictions with respect
to this document. Code Components extracted from this document must to this document. Code Components extracted from this document must
include Simplified BSD License text as described in Section 4.e of include Simplified BSD License text as described in Section 4.e of
the Trust Legal Provisions and are provided without warranty as the Trust Legal Provisions and are provided without warranty as
skipping to change at page 2, line 31 skipping to change at page 2, line 32
5.2. On receiving a Router Advertisement from the Edge 5.2. On receiving a Router Advertisement from the Edge
Router . . . . . . . . . . . . . . . . . . . . . . . . . . 7 Router . . . . . . . . . . . . . . . . . . . . . . . . . . 7
5.2.1. Identifying tunneled Router Advertisements . . . . . . 7 5.2.1. Identifying tunneled Router Advertisements . . . . . . 7
5.3. On detecting a subscriber circuit coming up . . . . . . . 7 5.3. On detecting a subscriber circuit coming up . . . . . . . 7
6. Edge Router Behavior . . . . . . . . . . . . . . . . . . . . . 8 6. Edge Router Behavior . . . . . . . . . . . . . . . . . . . . . 8
6.1. On receiving a Tunneled Router Solicitation from the 6.1. On receiving a Tunneled Router Solicitation from the
Access Node . . . . . . . . . . . . . . . . . . . . . . . 8 Access Node . . . . . . . . . . . . . . . . . . . . . . . 8
6.2. On sending a Router Advertisement towards the 6.2. On sending a Router Advertisement towards the
end-device . . . . . . . . . . . . . . . . . . . . . . . . 8 end-device . . . . . . . . . . . . . . . . . . . . . . . . 8
6.3. Sending periodic unsolicited Router Advertisements 6.3. Sending periodic unsolicited Router Advertisements
towards the end-device . . . . . . . . . . . . . . . . . . 8 towards the end-device . . . . . . . . . . . . . . . . . . 9
7. Line Identification Destination Option (LIO) . . . . . . . . . 9 7. Line Identification Destination Option (LIO) . . . . . . . . . 9
8. Interactions with Secure Neighbor Discovery . . . . . . . . . 10 8. Interactions with Secure Neighbor Discovery . . . . . . . . . 10
9. Acknowledgements . . . . . . . . . . . . . . . . . . . . . . . 10 9. Acknowledgements . . . . . . . . . . . . . . . . . . . . . . . 10
10. Security Considerations . . . . . . . . . . . . . . . . . . . 10 10. Security Considerations . . . . . . . . . . . . . . . . . . . 10
11. IANA Considerations . . . . . . . . . . . . . . . . . . . . . 11 11. IANA Considerations . . . . . . . . . . . . . . . . . . . . . 11
12. Normative References . . . . . . . . . . . . . . . . . . . . . 11 12. Normative References . . . . . . . . . . . . . . . . . . . . . 11
Authors' Addresses . . . . . . . . . . . . . . . . . . . . . . . . 11 Authors' Addresses . . . . . . . . . . . . . . . . . . . . . . . . 12
1. Introduction 1. Introduction
DSL is a widely deployed access technology for Broadband Access for Digital Subscriber Line (DSL) is a widely deployed access technology
Next Generation Networks. While traditionally DSL access networks for Broadband Access for Next Generation Networks. While
were PPP based some networks are migrating from the traditional PPP traditionally DSL access networks were Point-to-Point Protocol (PPP)
[RFC1661] based some networks are migrating from the traditional PPP
access model into a pure IP-based Ethernet aggregated access access model into a pure IP-based Ethernet aggregated access
environment. Architectural and topological models of an Ethernet environment. Architectural and topological models of an Ethernet
aggregation network in context of DSL aggregation are described in aggregation network in context of DSL aggregation are described in
[TR101]. [TR101].
+----+ +----+ +----------+ +----+ +----+ +----------+
|Host|---| RG |----| | |Host|---| RG |----| |
+----+ +----+ | | +----+ +----+ | |
| AN |\ | AN |\
+----+ +----+ | | \ +----+ +----+ | | \
skipping to change at page 3, line 40 skipping to change at page 3, line 41
+----+ +----+ | | / +----+ +----+ | | /
|Host|---| RG |----| AN |/ |Host|---| RG |----| AN |/
+----+ +----+ | | +----+ +----+ | |
| | | |
+----------+ +----------+
Figure 1: Broadband Forum Network Architecture Figure 1: Broadband Forum Network Architecture
One of the Ethernet and GPON aggregation models specified in this One of the Ethernet and GPON aggregation models specified in this
document bridges sessions from multiple user ports behind a DSL document bridges sessions from multiple user ports behind a DSL
Access Node (AN), also referred to as a DSLAM, into a single VLAN in Access Node (AN), also referred to as a Digital subscriber line
the aggregation network. This is called the N:1 VLAN allocation access multiplexer (DSLAM), into a single VLAN in the aggregation
model. network. This is called the N:1 VLAN allocation model.
+----------+ +----------+
| | | |
| | | |
| AN |\ | AN |\
| | \ | | \
| | \ VLANx | | \ VLANx
+----------+ \ +----------+ +----------+ \ +----------+
\ | | \ | |
+-------------+ | | +-------------+ | |
skipping to change at page 4, line 41 skipping to change at page 4, line 41
scenario where each user port is mapped to scenario where each user port is mapped to
a different VLAN on the Edge Router. The a different VLAN on the Edge Router. The
uniqueness of the mapping is maintained in uniqueness of the mapping is maintained in
the Access Node and across the Aggregation the Access Node and across the Aggregation
Network. Network.
N:1 VLAN It is a broadband network deployment N:1 VLAN It is a broadband network deployment
scenario where multiple user ports are scenario where multiple user ports are
mapped to the same VLAN on the Edge Router. mapped to the same VLAN on the Edge Router.
The user ports may be located in the same The user ports may be located in the same
or different Access Nodes. or different Access Nodes.
AN A DSL or GPON Access Node. The Access Node AN A DSL or a Gigabit Passive Optical Network
terminates the phyiscal layer (e.g. DSL (GPON) Access Node. The Access Node
terminates the physical layer (e.g. DSL
termination function or GPON termination termination function or GPON termination
function), may physically aggregate other function), may physically aggregate other
nodes implementing such functionality, or nodes implementing such functionality, or
may perform both functions at the same may perform both functions at the same
time. This node contains at least one time. This node contains at least one
standard Ethernet interface that serves as standard Ethernet interface that serves as
its "northbound" interface into which it its "northbound" interface into which it
aggregates traffic from several user ports aggregates traffic from several user ports
or Ethernet-based "southbound" interfaces. or Ethernet-based "southbound" interfaces.
It does not implement an IPv6 stack but It does not implement an IPv6 stack but
performs some limited inspection/ performs some limited inspection/
modification of IPv6 packets. modification of IPv6 packets. The IPv6
functions required on the Access Node are
described in Section 5 of [TR177].
Aggregation Network The part of the network stretching from the Aggregation Network The part of the network stretching from the
Access Nodes to the Edge Router. In the Access Nodes to the Edge Router. In the
context of this document the aggregation context of this document the aggregation
network is considered to be Ethernet based, network is considered to be Ethernet based,
providing standard Ethernet interfaces at providing standard Ethernet interfaces at
the edges, for connecting the Access Nodes the edges, for connecting the Access Nodes
and Broadband Network. It is comprised of and Broadband Network. It is comprised of
ethernet switches that provide very limited ethernet switches that provide very limited
IP functionality (e.g. IGMP snooping, MLD IP functionality (e.g. IGMP snooping, MLD
snooping etc.). snooping etc.).
skipping to change at page 6, line 49 skipping to change at page 6, line 49
unmodified inside the encapsulating IPv6 packet. In particular, the unmodified inside the encapsulating IPv6 packet. In particular, the
Hop Limit field of the ND message is not decremented when the packet Hop Limit field of the ND message is not decremented when the packet
is being tunneled. This is because ND messages whose Hop Limit is is being tunneled. This is because ND messages whose Hop Limit is
not 255 will be discarded by the receiver of such messages. not 255 will be discarded by the receiver of such messages.
5. Access Node Behavior 5. Access Node Behavior
5.1. On receiving a Router Solicitation from the end-device 5.1. On receiving a Router Solicitation from the end-device
When an end-device sends out a Router Solicitation, it is received by When an end-device sends out a Router Solicitation, it is received by
the access node. The AN then tunnels the received Router the access node. The AN identifies these messages by looking for
Solicitation in a newly created IPv6 datagram with the Line ICMPv6 messages (IPv6 Next Header value of 58) with ICMPv6 type 133.
Identification Option (LIO). The AN forms a new IPv6 datagram whose The AN intercepts and then tunnels the received Router Solicitation
payload is the received Router Solicitation message as described in in a newly created IPv6 datagram with the Line Identification Option
[RFC2473] except that the Hop Limit field of the Router Solicitation (LIO). The AN forms a new IPv6 datagram whose payload is the
message MUST NOT be decremented. If the AN has an IPv6 address, it received Router Solicitation message as described in [RFC2473] except
SHOULD use this address in the Source Address field of the outer IPv6 that the Hop Limit field of the Router Solicitation message MUST NOT
datagram. Otherwise it MUST use the unspecified address as the be decremented. If the AN has an IPv6 address, it SHOULD use this
Source Address of the outer IPv6 datagram. The destination address address in the Source Address field of the outer IPv6 datagram.
of the outer IPv6 datagram MUST be copied from the destination Otherwise it MUST use the unspecified address as the Source Address
address of the tunneled RS. The AN MUST insert a destination options of the outer IPv6 datagram. The destination address of the outer
header between the outer IPv6 header and the payload. It MUST insert IPv6 datagram MUST be copied from the destination address of the
a LIO destination option and set the line identification field of the tunneled RS. The AN MUST insert a destination options header between
the outer IPv6 header and the payload. It MUST insert a LIO
destination option and set the line identification field of the
option to contain the circuit identifier corresponding to the logical option to contain the circuit identifier corresponding to the logical
access loop port of the Access Node from which the RS was initiated. access loop port of the Access Node from which the RS was initiated.
5.2. On receiving a Router Advertisement from the Edge Router 5.2. On receiving a Router Advertisement from the Edge Router
When the edge router sends out a tunneled router advertisement in When the edge router sends out a tunneled router advertisement in
response to the RS, it is received by the access node. If there is response to the RS, it is received by the access node. If there is
an LIO option present, the AN MUST use the line identification data an LIO option present, the AN MUST use the line identification data
of the LIO option to identify the subscriber agent circuit of the of the LIO option to identify the subscriber agent circuit of the
Access Node on which the RA should be sent. The AN MUST then remove Access Node on which the RA should be sent. The AN MUST then remove
the outer IPv6 header of this tunneled RA and multicast the inner the outer IPv6 header of this tunneled RA and multicast the inner
packet (the original RA) on this specific subscriber circuit. packet (the original RA) on this specific subscriber circuit.
5.2.1. Identifying tunneled Router Advertisements 5.2.1. Identifying tunneled Router Advertisements
The Access Node can identify tunneled RAs by installing filters based The Access Node can identify tunneled RAs by installing filters based
on the destination address of the outer packets, and the presence of on the destination address (All BBF Access Nodes) of the outer
a destination option header with an LIO destination option. packets, and the presence of a destination option header with an LIO
destination option.
5.3. On detecting a subscriber circuit coming up 5.3. On detecting a subscriber circuit coming up
RSs initiated by end-devices as described in Section 5.1 may be lost RSs initiated by end-devices as described in Section 5.1 may be lost
due to lack of connectivity between the access node and the end- due to lack of connectivity between the access node and the end-
device. To ensure that the end-device will receive an RA, the AN device. To ensure that the end-device will receive an RA, the AN
needs to trigger the sending of periodic RAs on the edge router. For needs to trigger the sending of periodic RAs on the edge router. For
this purpose, the AN needs to inform the edge router that a this purpose, the AN needs to inform the edge router that a
subscriber circuit has come up. When the access node detects that a subscriber circuit has come up. When the access node detects that a
subscriber circuit has come up, it MUST create a Router Solicitation subscriber circuit has come up, it MUST create a Router Solicitation
skipping to change at page 8, line 36 skipping to change at page 8, line 39
Identification Option (LIO). The edge router creates the Router Identification Option (LIO). The edge router creates the Router
Advertisement message as described in Section 6.2.3 of [RFC4861]. Advertisement message as described in Section 6.2.3 of [RFC4861].
The edge router may use the contents of the LIO in the received The edge router may use the contents of the LIO in the received
router solicitation to determine the contents of this router router solicitation to determine the contents of this router
advertisement(es. The Edge Router then forms a new IPv6 datagram, advertisement(es. The Edge Router then forms a new IPv6 datagram,
whose payload is the Router Advertisement message, as described in whose payload is the Router Advertisement message, as described in
[RFC2473] except that the Hop Limit field of the Router Advertisement [RFC2473] except that the Hop Limit field of the Router Advertisement
message MUST NOT be decremented. The Edge router MUST use a link- message MUST NOT be decremented. The Edge router MUST use a link-
local IPv6 address on the outgoing interface in the Source Address local IPv6 address on the outgoing interface in the Source Address
field of the outer IPv6 datagram. The destination address of the field of the outer IPv6 datagram. The destination address of the
outer IPv6 datagram MUST be set to [KNOWN_VALUE_X, say fe80::0] . outer IPv6 datagram MUST be set to the well-known link-local scope
The edge router MUST insert a destination options header between the All BBF Access Nodes multicast address [to be allocated]. The edge
outer IPv6 header and the payload. It MUST insert a LIO destination router MUST insert a destination options header between the outer
option and set the line identification field of the option to contain IPv6 header and the payload. It MUST insert a LIO destination option
the circuit identifier corresponding to the logical access loop port and set the line identification field of the option to contain the
of the Access Node to which the RA MUST be sent. The IPv6 circuit identifier corresponding to the logical access loop port of
destination address of the inner RA MUST be set to the all-nodes the Access Node to which the RA MUST be sent. The IPv6 destination
multicast address. The link-layer destination address of the address of the inner RA MUST be set to the all-nodes multicast
tunneled RA MUST be set to the unicast link-layer address of the address. The link-layer destination address of the tunneled RA MUST
Access Node that sent the tunneled Router Solicitation which is being be set to the unicast link-layer address of the Access Node that sent
responded to. the tunneled Router Solicitation which is being responded to.
6.3. Sending periodic unsolicited Router Advertisements towards the 6.3. Sending periodic unsolicited Router Advertisements towards the
end-device end-device
After sending a tunneled Router Advertisement as specified in After sending a tunneled Router Advertisement as specified in
Section 6.2 in response to a received RS, the edge router MUST store Section 6.2 in response to a received RS, the edge router MUST store
the mapping between the LIO and the prefixes contained in the Router the mapping between the LIO and the prefixes contained in the Router
Advertisement. It should then initiate periodic sending of Advertisement. It should then initiate periodic sending of
unsolicited Router Advertisements as described in Section 6.2.3. of unsolicited Router Advertisements as described in Section 6.2.3. of
[RFC4861] . The Router Advertisements MUST be created and tunneled [RFC4861] . The Router Advertisements MUST be created and tunneled
skipping to change at page 11, line 13 skipping to change at page 11, line 13
trusted. trusted.
11. IANA Considerations 11. IANA Considerations
This document defines a new IPv6 destination option for carrying line This document defines a new IPv6 destination option for carrying line
identification. IANA is requested to assign a new destination option identification. IANA is requested to assign a new destination option
type in the Destination Options registry maintained at type in the Destination Options registry maintained at
http://www.iana.org/assignments/ipv6-parameters http://www.iana.org/assignments/ipv6-parameters
<TBA> Line Identification Option [RFCXXXX] <TBA1> Line Identification Option [RFCXXXX]
The act bits for this option need to be 10 and the chg bit needs to The act bits for this option need to be 10 and the chg bit needs to
be 0. be 0.
This document also requires the allocation of a well-known link-local
scope multicast address from the IPv6 Multicast Address Space
Registry located at
http://www.iana.org/assignments/ipv6-multicast-addresses/
ipv6-multicast-addresses.xml
<TBA2> All BBF Access Nodes [RFCXXXX]
12. Normative References 12. Normative References
[RFC1661] Simpson, W., "The Point-to-Point Protocol (PPP)", STD 51,
RFC 1661, July 1994.
[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, March 1997.
[RFC2473] Conta, A. and S. Deering, "Generic Packet Tunneling in [RFC2473] Conta, A. and S. Deering, "Generic Packet Tunneling in
IPv6 Specification", RFC 2473, December 1998. IPv6 Specification", RFC 2473, December 1998.
[RFC3971] Arkko, J., Kempf, J., Zill, B., and P. Nikander, "SEcure [RFC3971] Arkko, J., Kempf, J., Zill, B., and P. Nikander, "SEcure
Neighbor Discovery (SEND)", RFC 3971, March 2005. Neighbor Discovery (SEND)", RFC 3971, March 2005.
[RFC4861] Narten, T., Nordmark, E., Simpson, W., and H. Soliman, [RFC4861] Narten, T., Nordmark, E., Simpson, W., and H. Soliman,
skipping to change at page 12, line 5 skipping to change at page 12, line 10
[TR124] Broadband Forum, "Functional Requirements for Broadband [TR124] Broadband Forum, "Functional Requirements for Broadband
Residential Gateway Devices", <http:// Residential Gateway Devices", <http://
www.broadband-forum.org/technical/download/ www.broadband-forum.org/technical/download/
TR-124_Issue-2.pdf>. TR-124_Issue-2.pdf>.
[TR156] Broadband Forum, "Using GPON Access in the context of TR- [TR156] Broadband Forum, "Using GPON Access in the context of TR-
101", <http://www.broadband-forum.org/technical/download/ 101", <http://www.broadband-forum.org/technical/download/
TR-156.pdf>. TR-156.pdf>.
[TR177] Broadband Forum, "IPv6 in the context of TR-101",
<www.broadband-forum.org/technical/download/TR-177.pdf>.
Authors' Addresses Authors' Addresses
Suresh Krishnan Suresh Krishnan
Ericsson Ericsson
8400 Blvd Decarie 8400 Blvd Decarie
Town of Mount Royal, Quebec Town of Mount Royal, Quebec
Canada Canada
Email: suresh.krishnan@ericsson.com Email: suresh.krishnan@ericsson.com
skipping to change at page 12, line 36 skipping to change at page 13, line 4
Email: balazs.a.varga@ericsson.com Email: balazs.a.varga@ericsson.com
Sven Ooghe Sven Ooghe
Alcatel-Lucent Alcatel-Lucent
Copernicuslaan 50 Copernicuslaan 50
2018 Antwerp, 2018 Antwerp,
Belgium Belgium
Phone: Phone:
Email: sven.ooghe@alcatel-lucent.com Email: sven.ooghe@alcatel-lucent.com
Erik Nordmark Erik Nordmark
Oracle Cisco
17 Network Circle
Menlo Park, CA 94025
USA
Email: erik.nordmark@oracle.com Email: nordmark@acm.org
 End of changes. 23 change blocks. 
51 lines changed or deleted 71 lines changed or added

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