RFC 6788
The Line-Identification Option
RFC 6788: The Line-Identification Option ✨
Part 1 of 4 🧚
Title block 🎀
- Number: RFC 6788
- Title: The Line-Identification Option
- Authors: S. Krishnan (Ericsson), A. Kavanagh (Ericsson), B. Varga (Ericsson), S. Ooghe (Alcatel-Lucent), E. Nordmark (Cisco)
- Category: Standards Track
- Date: November 2012
- ISSN: 2070-1721
- Obsoletes / Updates: the header doesn't list anything this one obsoletes or updates 🙈
Abstract
Okay so picture Ethernet aggregation networks 🌸 where a bunch of subscriber premises can all be logically hooked up to the same interface of an Edge Router. This doc proposes a way for the Edge Router to figure out which subscriber premises is which, just by looking at what's inside the Router Solicitation messages it gets. It's only meant for broadband setups where lots of user ports get mapped onto the same virtual interface on the Edge Router. Very specific, very iconic 💅
Status of This Memo
This is an Internet Standards Track document. 🦋
This document is a product of the Internet Engineering Task Force (IETF). It represents the consensus of the IETF community. It has received public review and has been approved for publication by the Internet Engineering Steering Group (IESG). If you want more on Internet Standards, check out Section 2 of RFC 5741 📚
Info about the current status of this document, any errata, and how to give feedback on it lives at http://www.rfc-editor.org/info/rfc6788. Go take a peek 👀
Copyright Notice
Copyright (c) 2012 IETF Trust and the persons identified as the document authors. All rights reserved. ✨
This document is subject to BCP 78 and the IETF Trust's Legal Provisions Relating to IETF Documents (http://trustee.ietf.org/license-info) as in effect on the date of publication of this document. Please read these carefully, bestie, because they spell out your rights and restrictions for this document. Code Components pulled out of this document must include Simplified BSD License text as described in Section 4.e of the Trust Legal Provisions, and they come without warranty as described in the Simplified BSD License. 🫶
Table of Contents
1. Introduction ....................................................3
1.1. Terminology ................................................4
1.2. Conventions Used in This Document ..........................6
2. Applicability Statement .........................................6
3. Issues with Identifying the Subscriber Premises in an
N:1 VLAN Model ..................................................7
4. Basic Operation .................................................7
5. AN Behavior .....................................................8
5.1. On Initialization ..........................................8
5.2. On Receiving a Router Solicitation from the End-Device .....8
5.3. On Receiving a Router Advertisement from the Edge Router ...9
5.3.1. Identifying Tunneled Router Advertisements ..........9
5.4. On Detecting a Subscriber Circuit Coming Up ................9
5.5. On Detecting Edge Router Failure ..........................10
5.6. RS Retransmission Algorithm ...............................10
6. Edge Router Behavior ...........................................10
6.1. On Receiving a Tunneled Router Solicitation from the AN ...10
6.2. On Sending a Router Advertisement Towards the End-Device ..10
6.3. Sending Periodic Unsolicited Router Advertisements
Towards the End-Device ....................................11
7. Line-Identification Option (LIO) ...............................12
7.1. Encoding of Line ID .......................................13
8. Garbage Collection of Unused Prefixes ..........................14
9. Interactions with Secure Neighbor Discovery ....................14
10. Acknowledgements ..............................................14
11. Security Considerations .......................................14
12. IANA Considerations ...........................................14
13. References ....................................................15
13.1. Normative References .....................................15
13.2. Informative References ...................................161. Introduction ✨
Digital Subscriber Line (DSL) is a super popular access tech for Broadband Access for Next Generation Networks 📡. Traditional DSL access networks were built on Point-to-Point Protocol (PPP) [RFC1661], but some networks are moving away from that old PPP model and into a pure IP-based Ethernet aggregated access environment. The architecture and topology models for an Ethernet aggregation network in a DSL aggregation context are described in [TR101]. Obsessed with the diagram below 😭
+----+ +----+ +----------+
|Host|---| RG |----| |
+----+ +----+ | |
| AN |\
+----+ +----+ | | \
|Host|---| RG |----| | \
+----+ +----+ +----------+ \ +----------+
\ | |
+-------------+ | |
| Aggregation | | Edge |
| Network |-------| Router |
+-------------+ | |
/ | |
+----------+ / +----------+
| | /
+----+ +----+ | | /
|Host|---| RG |----| AN |/
+----+ +----+ | |
| |
+----------+
Figure 1: Broadband Forum Network ArchitectureOne of the Ethernet and Gigabit-capable Passive Optical Network (GPON) aggregation models specified in this document is giving bridging energy 💜. It bridges sessions from multiple user ports behind a DSL Access Node (AN), also called a Digital Subscriber Line Access Multiplexer (DSLAM), into a single VLAN in the aggregation network. This is called the N:1 VLAN allocation model 🎀
+----------+
| |
| |
| AN |\
| | \
| | \ VLANx
+----------+ \ +----------+
\ | |
+-------------+ | |
| Aggregation | VLANx | Edge |
| Network |-------| Router |
+-------------+ | |
/ | |
+----------+ / +----------+
| | / VLANx
| | /
| AN |/
| |
| |
+----------+
Figure 2: n:1 VLAN model1.1. Terminology
Here's the glossary, bestie 📖 Every term is in the table below, exactly as the spec has it.
1:1 VLAN A broadband network deployment scenario in
which each user port is mapped to a different
VLAN on the Edge Router. The uniqueness of
the mapping is maintained in the Access Node
and across the aggregation network.
N:1 VLAN A broadband network deployment scenario in
which multiple user ports are mapped to the
same VLAN on the Edge Router. The user ports
may be located in the same or different Access
Nodes.
GPON Gigabit-capable Passive Optical Network is an
optical access network that has been
introduced into the Broadband Forum
architecture in [TR156].
AN A DSL or a GPON Access Node. The Access Node
terminates the physical layer (e.g., DSL
termination function or GPON termination
function), may physically aggregate other
nodes implementing such functionality, or may
perform both functions at the same time. This
node contains at least one standard Ethernet
interface that serves as its "northbound"
interface into which it aggregates traffic
from several user ports or Ethernet-based
"southbound" interfaces. It does not
implement an IPv6 stack but performs some
limited inspection/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
Access Nodes to the Edge Router. In the
context of this document, the aggregation
network is considered to be Ethernet based,
providing standard Ethernet interfaces at the
edges, for connecting the Access Nodes and the
broadband network. It is comprised of
Ethernet switches that provide very limited IP
functionality (e.g., IGMP snooping, Multicast
Listener Discovery (MLD) snooping, etc.).
RG A residential gateway device. It can be a
Layer-3 (routed) device or a Layer-2 (bridged)
device. The residential gateway for Broadband
Forum networks is defined in [TR124].
Edge Router The Edge Router, also known as the Broadband
Network Gateway (BNG), is the first IPv6 hop
for the user. In cases where the RG is
bridged, the BNG acts as the default router
for the hosts behind the RG. In cases where
the RG is routed, the BNG acts as the default
router for the RG itself. This node
implements IPv6 router functionality.
Host A node that implements IPv6 host
functionality.
End-Device A node that sends Router Solicitations and
processes received Router Advertisements.
When a Layer-3 (L3) RG is used, it is
considered an end-device in the context of
this document. When a Layer-2 (L2) RG is
used, the host behind the RG is considered to
be an end-device in the context of this
document.1.2. Conventions Used in This Document
Okay, the key words are the official BCP 14 ones, and this is where the spec tells you how to read them 🤓. The key words "MUST", "MUST NOT", "REQUIRED", "SHALL","SHALL NOT", "SHOULD", "SHOULD NOT", "RECOMMENDED", "MAY", and "OPTIONAL" in this document are to be interpreted as described in [RFC2119]. No cap, that's the whole thing 💅
2. Applicability Statement ✨
okay bestie, let's talk about where this thing actually belongs 🎀 The Line-Identification Option (LIO) is meant to be used only for the N:1 VLAN deployment model 💅 For the other VLAN deployment models, line identification can be done differently. This mechanism lets hosts that only support IPv6 stateless address auto-configuration hook up to networks using the N:1 VLAN deployment model 🦋
When the Dynamic Host Configuration Protocol (DHCP) [RFC3315] is used for IPv6 address assignment, it comes with a side-effect that's kind of iconic: end-device-initiated reliability and inactivity detection 🌸 The reliability comes from the end-device continuing to retransmit DHCP messages until it receives a response), and inactivity is detected when the end-device stops renewing its DHCP lease. The "IPv6 Stateless Address Autoconfiguration" protocol [RFC4862] was not designed to satisfy those requirements [RSDA]. This option does improve reliability in deployments that use Router Solicitations instead of DHCP, but there are some limitations, as specified below ⚠️
The mechanism in this document deals with the loss of subscriber-originated Router Solicitations (RSes) by starting RSes at the AN 💖 That's more robust than just relying on the end-device's few initial retransmissions of RSes, so it's a real glow-up 🌈
BUT (and it's a big but 😭) the AN retransmissions mean that some information, like the subscriber's MAC address, that the Edge Router used to get from subscriber-originated RSes might not be available anymore. For example, since no L2 frame comes in from the subscriber when an AN sends an RS, the L2-address information of the end-device can't be determined. One piece of L2-address information that some broadband networks currently use is the MAC address. So for networks that need the endpoint's MAC address for identification, the solution in this document is NOT RECOMMENDED 🙈
There's also no indication when a subscriber is no longer active. That means this protocol can't automatically reclaim resources, such as prefixes, that are tied to an active subscriber. See Section 8. So, this protocol is NOT RECOMMENDED for networks that need automatic notification when a subscriber is no longer active 💀
This mechanism on its own gives no protection against the loss of RS-induced state in access routers, which could lead to loss of IPv6 connectivity for end-devices. Regular IPv6 hosts don't have RS retransmission behavior that would let them automatically recover from that kind of failure, so this mechanism SHOULD only be used in deployments employing N:1 VLANs 🫶
3. Issues with Identifying the Subscriber Premises in an N:1 VLAN Model 🧚
In a DSL- or GPON-based fixed broadband network, IPv6 end-devices are connected to an AN 🍓 Right now, these end-devices typically send a Router Solicitation message to the Edge Router, and the Edge Router replies with a Router Advertisement message. The Router Advertisement usually contains a prefix that the end-devices use to automatically configure an IPv6 address ✨ When the node connecting the end-device on the access circuit (typically an AN) sends the RS, it forwards it to the Edge Router upstream over a switched network 🦋
In these Ethernet-based aggregation networks, several subscriber premises may be connected to the same interface of an Edge Router (for example, on the same VLAN) 🌸 But the Edge Router needs some information to identify the end-device on the circuit. So the AN needs to add line-identification information to the Router Solicitation message and forward it to the Edge Router 💅 This is analogous to the DHCP case, where the line-identification information is inserted by a DHCP relay agent [RFC3315]. This document proposes a method for the Edge Router to identify the subscriber premises using the contents of the received Router Solicitation messages 👑 Note that there might be several end-devices located on the same subscriber premises 🫶
4. Basic Operation 🌈
This document uses a mechanism that tunnels Neighbor Discovery (ND) packets inside another IPv6 packet. That outer packet uses a destination option (Line-ID option) to carry the line-identification information, as shown in Figure 3 🎀 The Line-ID option is not defined by this document for use in any other IPv6 datagrams, including untunneled RS and RA messages 🙅♀️ The ND packets stay unmodified inside the encapsulating IPv6 packet. In particular, the Hop Limit field of the ND message is not decremented when the packet is tunneled. That's because an ND message whose Hop Limit is not 255 will be discarded by the receiver of such messages, as described in Sections 6.1.1 and 6.1.2 of [RFC4861] 💀
+----+ +----+ +-----------+
|Host| | AN | |Edge Router|
+----+ +----+ +-----------+
| RS | |
|---------->| |
| | |
| |Tunneled RS(LIO)|
| |--------------->|
| | |
| |Tunneled RA(LIO)|
| |<---------------|
| RA | |
|<----------| |
| | |Figure 3: Basic Message Flow
5. AN Behavior 🔥
5.1. On Initialization 🌸
On initialization, the AN MUST join the All-BBF-Access-Nodes multicast group on all of its upstream interfaces towards the Edge Router 🦋
5.2. On Receiving a Router Solicitation from the End-Device 💖
When an end-device sends out a Router Solicitation, the AN receives it 👀 The AN spots these messages by looking for ICMPv6 messages (IPv6 Next Header value of 58) with ICMPv6 type 133. The AN intercepts the received Router Solicitation and tunnels it in a newly created IPv6 datagram with the Line-Identification Option (LIO) ✨ The AN forms the new IPv6 datagram with the received Router Solicitation message as its payload, as described in [RFC2473], except that the Hop Limit field of the Router Solicitation message MUST NOT be decremented 🙅♀️ If the AN has an IPv6 address, it MUST use that address in the Source Address field of the outer IPv6 datagram. Otherwise, the AN MUST copy the source address from the received Router Solicitation into the Source Address field of the outer IPv6 datagram. The destination address of the outer IPv6 datagram MUST be copied from the destination address of the tunneled RS. The AN MUST include a destination options header between the outer IPv6 header and the payload. It MUST insert an LIO destination option and set the Line ID field of the option to contain the circuit identifier for the logical access loop port of the AN where the RS was initiated 🎀
5.3. On Receiving a Router Advertisement from the Edge Router 🦋
When the Edge Router sends out a tunneled Router Advertisement in response to the RS, the AN receives it 📬 If there is an LIO present, the AN MUST use the line-identification data in the LIO to identify the subscriber agent circuit of the AN on which the RA should be sent. Then the AN MUST remove the outer IPv6 header of this tunneled RA and multicast the inner packet (the original RA) on this specific subscriber circuit 💜
5.3.1. Identifying Tunneled Router Advertisements 🔍
The AN can identify tunneled RAs by installing filters based on two things: the destination address of the outer packets (All-BBF-Access-Nodes, which is a reserved link-local scoped multicast address), and the presence of a destination option header with an LIO destination option 🧚
5.4. On Detecting a Subscriber Circuit Coming Up 🌟
RSes initiated by end-devices as described in Section 5.2 may be lost due to lack of connectivity between the AN and the end-device 😭 To make sure the end-device gets an RA, the AN needs to trigger periodic RAs on the Edge Router. For that, the AN needs to tell the Edge Router that a subscriber circuit has come up ✨ Each time the AN detects that a subscriber circuit has come up, it MUST create a Router Solicitation message as described in Section 6.3.7 of [RFC4861]. It MUST use the unspecified address as the source address of this RS. Then it MUST tunnel this RS towards the Edge Router as described in Section 5.2 🫶
If there are connectivity issues between the AN and the Edge Router, the RSes initiated by the AN can get lost too. In that case, the AN SHOULD keep retransmitting the Router Solicitations following the algorithm in Section 5.6 for a given LIO until it receives an RA for that specific LIO 🔁
5.5. On Detecting Edge Router Failure 💀
When the Edge Router reboots and loses state, or gets replaced by a new Edge Router, the AN will detect it using connectivity check mechanisms that are already in place in broadband networks (for example, Bidirectional Forwarding Detection). When that Edge Router failure is detected, the AN needs to start transmitting RSes for each of its subscriber circuits that have come up, as described in Section 5.4 🚨
5.6. RS Retransmission Algorithm 🎀
The AN SHOULD use the exponential backoff algorithm for retransmits described in Section 14 of [RFC3315], so it can keep retransmitting the Router Solicitations for a given LIO until a response is received for that specific LIO 🌸 The AN SHOULD use the following variables as input to the retransmission algorithm:
Initial retransmission time (IRT) 1 Second
Maximum retransmission time (MRT) 30 Seconds
Maximum retransmission count (MRC) 0
Maximum retransmission duration (MRD) 06. Edge Router Behavior 👑
6.1. On Receiving a Tunneled Router Solicitation from the AN 🧚
When the Edge Router receives a tunneled Router Solicitation forwarded by the AN, it needs to check whether there is an LIO destination option in the outer datagram 🔍 The Edge Router can use the contents of the Line ID field to look up the addressing information and policy to apply to the line the Router Solicitation came from 💅 The Edge Router MUST then process the inner RS message as specified in [RFC4861] 🌈
6.2. On Sending a Router Advertisement Towards the End-Device ✨
Okay bestie, so when the Edge Router sends out an RA in response to a tunneled RS that had an LIO, it MUST tunnel that RA inside a brand new IPv6 datagram with the LIO attached 💌. First, the Edge Router builds the RA message the way Section 6.2.3 of [RFC4861] describes. Then it MUST include a Prefix Information option in that RA with the prefix that matches the received LIO. (The LIO from the tunneled RS usually gets passed to some kind of provisioning system, which sends back the prefix for the RA. It could, e,g., be based on RADIUS 🙈.)
Next, the Edge Router wraps the RA in a new IPv6 datagram, as described in [RFC2473], with one twist: the Hop Limit field of the RA MUST NOT be decremented 🦋. The Edge router MUST use a link-local IPv6 address on the outgoing interface for the Source Address of the outer datagram. The Edge Router MUST include a destination options header between the outer IPv6 header and the payload. It MUST insert an LIO and set its Line ID field to the same value as the Line-ID option in the received RS. The IPv6 destination address of the inner RA MUST be set to the all-nodes multicast address 🌈.
If the Source Address of the received IPv6 datagram was not the unspecified address, the Edge Router MUST copy that address into the Destination Address of the outer IPv6 datagram sent back towards the AN. The link-layer destination address of that outer datagram MUST be resolved using regular Neighbor Discovery procedures 💜.
If the Source Address of the received IPv6 datagram was the unspecified address, the destination address of the outer IPv6 datagram MUST be set to the well-known link-local scope All-BBF-Access-Nodes multicast address (ff02::10). The link-layer destination address of the tunneled RA MUST be set to the unicast link-layer address of the AN that sent the tunneled Router Solicitation being responded to 🫶.
The Edge Router MUST ensure that it does not transmit tunneled RAs larger than the MTU of the link between the Edge Router and the AN, because that would force the outer IPv6 datagram to be fragmented 😭. This limit exists because the AN may not be capable of reassembling fragmented datagrams like that, so bestie, keep them small.
6.3. Sending Periodic Unsolicited Router Advertisements Towards the End-Device
After the Edge Router sends a tunneled RA as Section 6.2 specifies, in response to a received RS, it MUST store the mapping between the LIO and the prefixes contained in that RA 🧚. It should then start sending unsolicited RAs periodically, as described in Section 6.2.3. of [RFC4861] . Those RAs MUST be created and tunneled as described in Section 6.2 🎀.
The Edge Router MAY stop sending RAs if it gets a notification from the AN that the subscriber circuit has gone down. That notification can arrive out-of-band through a mechanism such as the Access Node Control Protocol (ANCP) 🌸. Please consult Section 8 for more details.
7. Line-Identification Option (LIO) 🍓
The Line-Identification Option (LIO) is a destination option that can be included in IPv6 datagrams that tunnel Router Solicitation and Router Advertisement messages 💖. The Line-ID option is not defined by this document for use in any other IPv6 datagrams. Multiple Line-ID destination options MUST NOT be present in the same IPv6 datagram, no exceptions 💅. The LIO has no alignment requirement.
0 1 2 3
0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| Option Type | Option Length |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| LineIDLen | Line ID...
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+Figure 4: Line-Identification Option Layout
Here's the breakdown, bestie 🧠:
Option Type: an 8-bit identifier of the type of option. The option identifier for the Line-Identification Option (0x8C) has been allocated by the IANA 👑.
Option Length: an 8-bit unsigned integer that gives the length of the option, not counting the Option Type and Option Length fields. The value MUST be greater than 0 ✨.
LineIDLen: an 8-bit unsigned integer that gives the length of the Line ID field in number of octets 📏.
Line ID: variable-length data inserted by the AN, describing the subscriber-agent circuit identifier that matches the logical access loop port of the AN the RS came from. The line identification MUST be unique across all the ANs that share a link to the Edge Router. One such line-identification scheme is described in Section 3.9 of [TR101] 🦋. The line identification should be encoded as specified in Section 7.1.
7.1. Encoding of the Line ID Field Content 🌷
This IPv6 Destination option is derived from a widely deployed DHCPv6 option [RFC4649], which in turn is derived from a widely deployed DHCPv4 option [RFC3046]. These options derive from and cite the basic DHCP options specification [RFC2132]. The widely deployed DHCP options use the Network Virtual Terminal (NVT) character set [RFC2132] [RFC0020]. Since the provisioning systems use the data in the Line-ID option the same way they use DHCP options, it's super beneficial for it to keep the same encoding 🤝.
The IPv6 Line ID option describes the line using only character positions (decimal 32 to decimal 126, inclusive) of the US-ASCII character set [X3.4] [RFC0020]. Consistent with [RFC2132], [RFC3046], and [RFC4649], the Line ID field SHOULD NOT contain the US-ASCII NUL character (decimal 0). However, implementations receiving this option MUST NOT fail merely because an ASCII NUL character is (erroneously) present in the Line ID field 🙈.
Some existing, widely deployed Edge Routers and ANs that support the DHCP option mentioned above only support US-ASCII and strip the high-order bit from any 8-bit characters the device operator types in. The DHCP options mentioned above don't support 8-bit character sets either 💀. So, for compatibility with the installed base and to maximize interoperability, the high-order bit of each octet in this field MUST be set to zero by any device inserting this option into an IPv6 packet 🫶.
Consistent with [RFC3046] and [RFC4649], this option always uses binary comparison. That means two Line IDs MUST be equal when they match byte-by-byte. Line-ID A and Line-ID B match byte-by-byte when (1) A and B have the same number of bytes, and (2) for all byte indexes P in A, the value of A at index P has the same binary value as the value of B at index P 🔥.
Two Line IDs MUST NOT be equal if they do not match byte-by-byte. For example, an IPv6 Line-ID option containing "f123" is not equal to a Line-ID option "F123". Yep, capital letters matter, iykyk 💅.
Intermediate systems MUST NOT alter the contents of the Line ID 🔒.
8. Garbage Collection of Unused Prefixes 🗑️
Following the mechanism described in this document, the broadband network associates a prefix with a subscriber line based on the LIO. Even when the subscriber line goes down temporarily, this prefix stays allocated to that specific subscriber line, so the prefix is not returned to the unused pool 🌈. When a subscriber line no longer needs a prefix, the prefix can be reclaimed by manual action that dissociates it from the LIO in the backend systems 🧹.
9. Interactions with Secure Neighbor Discovery 🔐
Since the RS/RA packets protected by "SEcure Neighbor Discovery (SEND)" [RFC3971] are not modified in any way by the mechanism described in this document, there are no issues with SEND verification ✅.
10. Acknowledgements 🎉
The authors would like to thank Margaret Wasserman, Mark Townsley, David Miles, John Kaippallimalil, Eric Levy-Abegnoli, Thomas Narten, Olaf Bonness, Thomas Haag, Wojciech Dec, Brian Haberman, Ole Troan, Hemant Singh, Jari Arkko, Joel Halpern, Bob Hinden, Ran Atkinson, Glen Turner, Kathleen Moriarty, David Sinicrope, Dan Harkins, Stephen Farrell, Barry Leiba, Sean Turner, Ralph Droms, and Mohammed Boucadair for reviewing this document and suggesting changes. Iconic squad 👑💖.
11. Security Considerations 🚨
The line identification information inserted by the AN or the Edge Router is not protected. This means that this option may be modified, inserted, or deleted without being detected. In order to ensure validity of the contents of the Line ID field, the network between the AN and the Edge Router needs to be trusted. Bestie, this is serious, so trust the network or the whole thing is cooked 💀🔥.
12. IANA Considerations 📋
This document defines a new IPv6 destination option for carrying line identification. IANA has assigned the following new destination option type in the "Destination Options and Hop-by-Hop Options" registry maintained at <http://www.iana.org/assignments/ipv6-parameters>:
0x8C Line-Identification Option [RFC6788]The act bits for this option are 10 and the chg bit is 0.
Per this document, IANA has also allocated the following well-known link-local scope multicast address from the "IPv6 Multicast Address Space Registry" located at <http://www.iana.org/assignments/ipv6-multicast-addresses/>:
FF02:0:0:0:0:0:0:10 All-BBF-Access-Nodes [RFC6788]13. References ✨
13.1. Normative References 📚✨
okay bestie, these are the must-read buddies 💅 the stuff this doc leans on super hard, so you gotta know them to get the full vibe:
[RFC1661]Simpson, W., Ed., "The Point-to-Point Protocol (PPP)", STD 51, RFC 1661, July 1994. 🦋[RFC2119]Bradner, S., "Key words for use in RFCs to Indicate Requirement Levels", BCP 14, RFC 2119, March 1997. 👑[RFC2473]Conta, A. and S. Deering, "Generic Packet Tunneling in IPv6 Specification", RFC 2473, December 1998. 🌈[RFC3315]Droms, R., Ed., Bound, J., Volz, B., Lemon, T., Perkins, C., and M. Carney, "Dynamic Host Configuration Protocol for IPv6 (DHCPv6)", RFC 3315, July 2003. 🎀[RFC3971]Arkko, J., Ed., Kempf, J., Zill, B., and P. Nikander, "SEcure Neighbor Discovery (SEND)", RFC 3971, March 2005. 🔐[RFC4861]Narten, T., Nordmark, E., Simpson, W., and H. Soliman, "Neighbor Discovery for IP version 6 (IPv6)", RFC 4861, September 2007. 🌸[RFC4862]Thomson, S., Narten, T., and T. Jinmei, "IPv6 Stateless Address Autoconfiguration", RFC 4862, September 2007. ✨[TR101]Broadband Forum, "Migration to Ethernet-based DSL aggregation",<http://www.broadband-forum.org/technical/download/TR-101.pdf>. 🍓[TR124]Broadband Forum, "Functional Requirements for Broadband Residential Gateway Devices",<http://www.broadband-forum.org/technical/download/TR-124_Issue-2.pdf>. 🏠[TR156]Broadband Forum, "Using GPON Access in the context of TR-101",<http://www.broadband-forum.org/technical/download/TR-156.pdf>. 🧚[TR177]Broadband Forum, "IPv6 in the context of TR-101",<www.broadband-forum.org/technical/download/TR-177.pdf>. 💜[X3.4]American National Standards Institute, "American Standard Code for Information Interchange (ASCII)", Standard X3.4, 1968. 🔤
13.2. Informative References 💭
these ones are the extra reading 🫶 not required to get the core ideas, but SO worth a look if you're curious (and let's be real, you will be):
[RFC0020]Cerf, V., "ASCII format for network interchange", RFC 20, October 1969. 💻[RFC2132]Alexander, S. and R. Droms, "DHCP Options and BOOTP Vendor Extensions", RFC 2132, March 1997. 🌷[RFC3046]Patrick, M., "DHCP Relay Agent Information Option", RFC 3046, January 2001. 🔍[RFC4649]Volz, B., "Dynamic Host Configuration Protocol for IPv6 (DHCPv6) Relay Agent Remote-ID Option", RFC 4649, August 2006. 🪄[RSDA]Dec, W., "IPv6 Router Solicitation Driven Access Considered Harmful", Work in Progress, June 2011. 🙈
Authors' Addresses 🎀
meet the squad who wrote this 🫶 here's where you can find them:
Suresh Krishnan
Ericsson
8400 Blvd Decarie
Town of Mount Royal, Quebec
Canada
EMail: suresh.krishnan@ericsson.com
Alan Kavanagh
Ericsson
8400 Blvd Decarie
Town of Mount Royal, Quebec
Canada
EMail: alan.kavanagh@ericsson.com
Balazs Varga
Ericsson
Konyves Kalman krt. 11. B.
1097 Budapest
Hungary
EMail: balazs.a.varga@ericsson.com
Sven Ooghe
Alcatel-Lucent
Copernicuslaan 50
2018 Antwerp,
Belgium
Phone:
EMail: sven.ooghe@alcatel-lucent.com
Erik Nordmark
Cisco
510 McCarthy Blvd.
Milpitas, CA, 95035
USA
Phone: +1 408 527 6625
EMail: nordmark@cisco.com📦 where this page comes from
- ietf: rfc6788 2012-11
- 💖 girlified by claude-haiku-5-5 on : a language model's rewrite of the original, under its terms