RFC 6911
RADIUS Attributes for IPv6 Access Networks
RFC 6911: RADIUS Attributes for IPv6 Access Networks 🎀
okay bestie, this is the RFC that gives RADIUS new IPv6 Attributes for residential broadband setups 🏠✨ here's the tea on its title block:
- Publisher: Internet Engineering Task Force (IETF) 🌸
- Authors: W. Dec, Ed. (Cisco Systems, Inc.), B. Sarikaya (Huawei USA), G. Zorn, Ed. (Network Zen), D. Miles (Google), and B. Lourdelet (Juniper Networks) 💖
- Category: Standards Track 🦋
- ISSN: 2070-1721
- Date: April 2013 📅
- Obsoletes or updates: the title block doesn't list anything it obsoletes or updates 🙈
Abstract ✨
okay so this doc adds more IPv6 RADIUS Attributes that are useful in residential broadband networks 🏡 the Attributes are used for authorization and accounting, and they let you do a bunch of cute stuff: hand a host its IPv6 address and an IPv6 DNS server address through DHCPv6 💅, assign an IPv6 route that gets announced through router advertisement 📡, assign a named IPv6 delegated prefix pool 🎀, and assign a named IPv6 pool for host DHCPv6 addressing 🧚
Status of This Memo
this is an Internet Standards Track document 🌈
this document is a product of the Internet Engineering Task Force (IETF). it reflects the consensus of the IETF community, got public review, and was approved for publication by the Internet Engineering Steering Group (IESG). more info on Internet Standards is in Section 2 of RFC 5741 📚
for the current status, any errata, and how to give feedback, check http://www.rfc-editor.org/info/rfc6911 💜
Copyright Notice
Copyright (c) 2013 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. please read these carefully, because they explain your rights and restrictions for this document 🫶 code components extracted from 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. Requirements Language . . . . . . . . . . . . . . . . . . 3
2. Deployment Scenarios . . . . . . . . . . . . . . . . . . . . 3
2.1. IPv6 Address Assignment . . . . . . . . . . . . . . . . . 4
2.2. DNS Servers . . . . . . . . . . . . . . . . . . . . . . . 5
2.3. IPv6 Route Information . . . . . . . . . . . . . . . . . 5
2.4. Delegated IPv6 Prefix Pool . . . . . . . . . . . . . . . 6
2.5. Stateful IPv6 Address Pool . . . . . . . . . . . . . . . 6
3. Attributes . . . . . . . . . . . . . . . . . . . . . . . . . 6
3.1. Framed-IPv6-Address . . . . . . . . . . . . . . . . . . . 6
3.2. DNS-Server-IPv6-Address . . . . . . . . . . . . . . . . . 8
3.3. Route-IPv6-Information . . . . . . . . . . . . . . . . . 9
3.4. Delegated-IPv6-Prefix-Pool . . . . . . . . . . . . . . . 10
3.5. Stateful-IPv6-Address-Pool . . . . . . . . . . . . . . . 11
3.6. Table of Attributes . . . . . . . . . . . . . . . . . . . 11
4. Diameter Considerations . . . . . . . . . . . . . . . . . . . 12
5. Security Considerations . . . . . . . . . . . . . . . . . . . 12
6. IANA Considerations . . . . . . . . . . . . . . . . . . . . . 12
7. Acknowledgments . . . . . . . . . . . . . . . . . . . . . . . 13
8. References . . . . . . . . . . . . . . . . . . . . . . . . . 13
8.1. Normative References . . . . . . . . . . . . . . . . . . 13
8.2. Informative References . . . . . . . . . . . . . . . . . 131. Introduction 🦋
okay so this doc specifies extra RADIUS Attributes that help configure DHCPv6 and/or ICMPv6 Router Advertisement (RA) parameters on a per-user basis 💖 these Attributes complement the ones in [RFC3162] and [RFC4818], and they support the following:
- the assignment of specific IPv6 addresses to hosts via DHCPv6 🏠
- the assignment of an IPv6 DNS server address, via DHCPv6 or Router Advertisement [RFC6106] 🌐
- the configuration of more specific routes to be announced to the user via the Route Information Option defined in [RFC4191], Section 2.3 🛣️
- the assignment of a named delegated prefix pool for use with "IPv6 Prefix Options for Dynamic Host Configuration Protocol (DHCP) version 6" [RFC3633] 🎀
- the assignment of a named stateful address pool for use with DHCPv6 stateful address assignment [RFC3315] 🧚
1.1. Requirements Language
quick heads up 🫶 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 RFC 2119 [RFC2119] 📖
2. Deployment Scenarios 🌸
the extensions here are meant to work across a whole bunch of network access setups where RADIUS is involved 🌍 one typical example is in Figure 1. it's made of an IP Routing Residential Gateway (RG) or host, a Layer 2 Access Node (AN) (e.g., a Digital Subscriber Line Access Multiplexer (DSLAM)), an IP Network Access Server (NAS) (which includes an Authentication, Authorization, and Accounting (AAA) client), and an AAA server 🖥️
+-----+
| AAA |
| |
+--+--+
^
.
.(RADIUS)
.
v
+------+ +---+---+
+------+ | | | |
| RG/ +-------| AN +-----------+----------+ NAS |
| host | | | | |
+------+ (DSL) +------+ (Ethernet) +-------+
Figure 1in this setup, the NAS may use an IP address configuration protocol (e.g., DHCPv6) to handle address assignment to RGs/hosts 🎯 the RADIUS server authenticates each RG/host and sends back the Attributes used for authorization and accounting ✨ those Attributes can include a host's IPv6 address, a DNS server address, and a set of IPv6 routes to be advertised via any suitable protocol (e.g., ICMPv6 (Neighbor Discovery)) 📡 the name of a prefix pool for DHCPv6 Prefix Delegation, or the name of an address pool for DHCPv6 address assignment, can also be Attributes the RADIUS AAA server gives to the NAS 🧁
the following subsections go deeper into how these Attributes get used 💅
2.1. IPv6 Address Assignment
DHCPv6 [RFC3315] gives you a way to assign one or more non-temporary IPv6 addresses to hosts 🏷️ so a DHCPv6 server living on a NAS can get one or more IPv6 addresses to hand out, this document specifies the Framed-IPv6-Address Attribute (Section 3.1) 🦋
while [RFC3162] lets you specify an IPv6 address by combining the Framed-Interface-Id and Framed-IPv6-Prefix Attributes, that split is more natural for PPP's IPv6 Control Protocol than for DHCPv6 🙃 using one single IPv6 address Attribute makes accounting records way easier to process 📊
okay here's the plot twist 😭 DHCPv6 can live on the same network as ICMPv6 stateless address autoconfiguration (SLAAC) [RFC4862], so the NAS might need both stateful and stateless config info 🌀 that means the Framed-IPv6-Address, Framed-IPv6-Prefix, and Framed-Interface-Id Attributes [RFC3162] could all show up in the same packet 🎀 to avoid any confusion, the Framed-IPv6-Address Attribute is meant for authorization and accounting of DHCPv6-assigned addresses, while the Framed-IPv6-Prefix and Framed-Interface-Id Attributes are used for authorization and accounting of addresses assigned via SLAAC ✨
2.2. DNS Servers
DHCPv6 has an option for giving a host the IPv6 address of a DNS server 🌐 the IPv6 address of a DNS server can also be passed to the host using ICMPv6 with Router Advertisements, through the Recursive DNS Server Option [RFC6106] 📮 to give the NAS the IPv6 address of one or more DNS servers, this document specifies the DNS-Server-IPv6-Address Attribute (Section 3.2) 💜
2.3. IPv6 Route Information
the IPv6 Route Information Option [RFC4191], is meant to tell a host connected to the NAS that a specific route can be reached through any given NAS 🛤️
this document specifies the Route-IPv6-Information Attribute (Section 3.3), which lets the AAA server set up the NAS announcing a specific Route Information Option to an accessing host 📢 the NAS may advertise this route using the method defined in RFC 4191 or another equivalent method 🌷 any other info, like preference or lifetime values, that goes into the actual announcement with a given method is assumed to be decided by the NAS using means this document doesn't specify (e.g., local configuration on the NAS) 🧠
⚠️ the Framed-IPv6-Prefix Attribute ([RFC3162], Section 2.3) lets the route be advertised in an RA, but it can't be used to configure more specific routes 🙈 the Framed-IPv6-Route Attribute ([RFC3162], Section 2.5) does get the route configured on the NAS and maybe announced via an IP routing protocol (depending on the value of Framed-Routing), but it doesn't result in the route being announced in an RA 💀
2.4. Delegated IPv6 Prefix Pool
DHCPv6 Prefix Delegation (DHCPv6-PD) [RFC3633] is when a delegating router picks a prefix and hands it out on a temporary basis to a requesting router 🎁 the delegating router may use a bunch of strategies to choose which prefix gets delegated to a requesting router, and one of them is using a local named prefix pool 🧁 the Delegated-IPv6-Prefix-Pool Attribute (Section 3.4) lets the RADIUS server send a prefix pool name to a NAS that's hosting a DHCPv6-PD server and acting as a delegating router 👑
because DHCPv6 Prefix Delegation can run alongside SLAAC on the same network, the Delegated-IPv6-Prefix-Pool and Framed-IPv6-Pool Attributes could end up in the same packet 😭 to keep things clear, the Delegated-IPv6-Prefix-Pool Attribute should be limited to authorization and accounting of prefix pools used in DHCPv6 Prefix Delegation, and the Framed-IPv6-Pool Attribute should be used for authorization and accounting of prefix pools used in SLAAC 💅✨
2.5. Stateful IPv6 Address Pool 💖
okay so DHCPv6 [RFC3315] is the thing that hands hosts one or more non-temporary IPv6 addresses 🫶 Section 3.1 brings in the Framed-IPv6-Address Attribute so a DHCPv6 server sitting on a NAS can be given IPv6 addresses to pass out to clients. But there's a second way to get a similar result: the NAS just picks the address from an address pool that's been set up on the NAS for exactly that purpose 🌸 This document adds the Stateful-IPv6-Address-Pool Attribute (Section 3.5) so the RADIUS server can send over a pool name. That name tells the NAS which pool to use for this kind of stateful DHCPv6-based addressing, and for any accounting that comes after 📊✨
3. Attributes 🎀
The fields shown in the diagrams below are transmitted from left to right. 🦋
3.1. Framed-IPv6-Address 🌈
okay bestie, the Framed-IPv6-Address Attribute says which IPv6 address is assigned to the NAS-facing interface of the RG/host 💅 It MAY show up in Access-Accept packets, and it MAY appear more than once 🍓 It MAY also be sent in an Access-Request packet as a hint from the NAS to the RADIUS server, saying "hey, I'd prefer this address." The RADIUS server isn't required to honor that hint, though 🙈 And because the NAS is assumed to add a route for the address, the RADIUS server doesn't also need to send a host Framed-IPv6-Route Attribute for that same address. Literally less work, iykyk 💀
This Attribute can be used by a DHCPv6 process on the NAS to give the RG/host a unique IPv6 address 🧚
Here's a quick look at the Framed-IPv6-Address Attribute format. The Address field is identical to the matching field in the NAS-IPv6-Address Attribute [RFC3162] ✨
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
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| Type | Length | Address
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
Address (cont)
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
Address (cont)
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
Address (cont)
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
Address (cont) |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+Type
168 for Framed-IPv6-Address 🔥
Length
18 💖
Address
A 128-bit IPv6 address. 🫧
3.2. DNS-Server-IPv6-Address 🌷
The DNS-Server-IPv6-Address Attribute carries the IPv6 address of a DNS server 🧁 It MAY be included multiple times in Access-Accept packets, which is the move when the NAS wants to announce more than one DNS server address to an RG/host 💜 It MAY also be used in an Access-Request packet as a hint from the NAS to the RADIUS server about the DNS IPv6 address, but the RADIUS server isn't required to honor that hint 🙈
The content of this Attribute can be copied into an instance of the DHCPv6 DNS Recursive Name Server Option [RFC3646], or into an IPv6 Router Advertisement Recursive DNS Server Option [RFC6106]. If more than one DNS-Server-IPv6-Address Attribute shows up in the Access-Accept packet, the addresses from those Attributes SHOULD be copied in the same order they were received 🍓
Here's the DNS-Server-IPv6-Address Attribute format. Its Address field is the same as the corresponding field in the NAS-IPv6-Address Attribute [RFC3162] 🦋
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
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| Type | Length | Address
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
Address (cont)
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
Address (cont)
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
Address (cont)
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
Address (cont) |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+Type
169 for DNS-Server-IPv6-Address ✨
Length
18 🌸
Address
The 128-bit IPv6 address of a DNS server. 💅
3.3. Route-IPv6-Information 🛣️
The Route-IPv6-Information Attribute specifies a prefix (and its matching route) for the user on the NAS. That prefix gets announced using the Route Information Option from "Default Router Preferences and More Specific Routes" [RFC4191], Section 2.3 🧚 It's used in the Access-Accept packet and can appear multiple times 🌈 It MAY also be used in an Access-Request packet as a hint from the NAS to the RADIUS server, but the RADIUS server isn't required to honor it. The Route-IPv6-Information Attribute format is drawn below, and the prefix follows the format given in [RFC3162] 💖
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
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| Type | Length | Reserved | Prefix-Length |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| |
. Prefix (variable) .
. .
| |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+Type
170 for Route-IPv6-Information 🍓
Length
Length, in bytes. At least 4 and no larger than 20; typically, 12 or less. 🫶
Prefix Length
8-bit unsigned integer. The number of leading bits in the prefix that are valid. The value can range from 0 to 128. The prefix field is 0, 8, or 16 octets depending on Length. 🔢
Prefix
Variable-length field containing an IP prefix. The prefix length field contains the number of valid leading bits in the prefix. The bits in the prefix after the prefix length, if any, are reserved and MUST be initialized to zero. ⚠️ That zeroing part is non-negotiable, bestie 💅
3.4. Delegated-IPv6-Prefix-Pool 🌊
The Delegated-IPv6-Prefix-Pool Attribute contains the name of an assigned pool that SHOULD be used to pick an IPv6 delegated prefix for the user on the NAS 🌺 If a NAS doesn't support prefix pools, the NAS MUST ignore this Attribute 🙅♀️ It MAY be used in an Access-Request packet as a hint from the NAS to the RADIUS server about the pool, but the RADIUS server isn't required to honor the hint 🍓
Here's the Delegated-IPv6-Prefix-Pool Attribute format 🦋
0 1 2
0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1 2 3
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| Type | Length | String...
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+Type
171 for Delegated-IPv6-Prefix-Pool 💜
Length
Length, in bytes. At least 3. 🔢
String
The string field contains the name of an assigned IPv6 prefix pool configured on the NAS. The field is not NULL (hexadecimal 00) terminated. 🎀
Note: The string data type is as documented in [RFC6158] and carries binary data that is external to the RADIUS protocol, e.g., the name of a pool of prefixes configured on the NAS. 🧠
3.5. Stateful-IPv6-Address-Pool 🌟
The Stateful-IPv6-Address-Pool Attribute contains the name of an assigned pool that SHOULD be used to pick an IPv6 address for the user on the NAS 🌸 If a NAS doesn't support address pools, the NAS MUST ignore this Attribute 🙅♀️ Here's the format 👇 It MAY be used in an Access-Request packet as a hint from the NAS to the RADIUS server about the pool, but the RADIUS server isn't required to honor the hint 💖
0 1 2
0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1 2 3
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| Type | Length | String...
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+Type
172 for Stateful-IPv6-Address-Pool 🫧
Length
Length, in bytes. At least 3. 🔢
String
The string field contains the name of an assigned IPv6 stateful address pool configured on the NAS. The field is not NULL (hexadecimal 00) terminated. 🎀
Note: The string data type is as documented in [RFC6158] and carries binary data that is external to the RADIUS protocol, e.g., the name of a pool of addresses configured on the NAS. 🧠
3.6. Table of Attributes 📋
This table is your cheat sheet for which Attributes can show up in which kinds of packets, and how many of each 🍭 The optional stuff in Access Request messages is there so a NAS can give the RADIUS server a hint about Attributes before user authentication happens. That's handy when a user reconnects or has a static address 🫶 The server has no obligation to honor those hints, so don't count on it 🙈
Request Accept Reject Challenge Accounting # Attribute
Request
0+ 0+ 0 0 0+ 168 Framed-IPv6-Address
0+ 0+ 0 0 0+ 169 DNS-Server-IPv6-Address
0+ 0+ 0 0 0+ 170 Route-IPv6-Information
0+ 0+ 0 0 0+ 171 Delegated-IPv6-Prefix-Pool
0+ 0+ 0 0 0+ 172 Stateful-IPv6-Address-Pool4. Diameter Considerations 🌈
Since the Attributes defined in this document are allocated from the standard RADIUS type space (see Section 6), Diameter entities don't need any special handling 💅
5. Security Considerations 🚨
Okay, this part is serious, so listen up 🫢 This document specifies additional IPv6 RADIUS Attributes that are useful in residential broadband network deployments. In those networks, the RADIUS protocol may run over IPv4 or over IPv6, and known security vulnerabilities of the RADIUS protocol, e.g., [SECI], apply to the Attributes defined in this document 💀 A trust relationship between a NAS and RADIUS server is expected to be in place, and the communication can optionally be secured by IPsec or Transport Layer Security (TLS) [RFC6614] 🔐 Don't skip this bit, periodt 😭
6. IANA Considerations 🗂️
IANA has assigned five new RADIUS Attribute types in the "Radius Attribute Types" registry (currently located at http://www.iana.org/assignments/radius-types) for the following Attributes: 🦋
Framed-IPv6-Address💖DNS-Server-IPv6-Address🌸Route-IPv6-Information🧚Delegated-IPv6-Prefix-Pool🍓Stateful-IPv6-Address-Pool👑
7. Acknowledgments 🫶
The authors would like to thank Bernard Aboba, Benoit Claise, Peter Deacon, Alan DeKok, Ralph Droms, Brian Haberman, Alfred Hines, Stephen Farrell, Jouni Korhonen, Roberta Maglione, Pete Resnick, Mark Smith, and Leaf Yeh for their help and comments in reviewing this document 💜✨
8. References 📚
8.1. Normative References 🌷
[RFC2119] Bradner, S., "Key words for use in RFCs to Indicate
Requirement Levels", BCP 14, RFC 2119, March 1997.
[RFC4862] Thomson, S., Narten, T., and T. Jinmei, "IPv6 Stateless
Address Autoconfiguration", RFC 4862, September 2007.8.2. Informative References ✨
okay so these are the informative ones, bestie 📚🫶 they're not required reading to implement the spec, but they give the backstory on RADIUS, IPv6, and DHCPv6 that makes everything click 💅
- [RFC3162] Aboba, B., Zorn, G., and D. Mitton, "RADIUS and IPv6", RFC 3162, August 2001. 🧚
- [RFC3315] Droms, R., Bound, J., Volz, B., Lemon, T., Perkins, C., and M. Carney, "Dynamic Host Configuration Protocol for IPv6 (DHCPv6)", RFC 3315, July 2003. 🌈
- [RFC3633] Troan, O. and R. Droms, "IPv6 Prefix Options for Dynamic Host Configuration Protocol (DHCP) version 6", RFC 3633, December 2003. 🎀
- [RFC3646] Droms, R., "DNS Configuration options for Dynamic Host Configuration Protocol for IPv6 (DHCPv6)", RFC 3646, December 2003. 🌸
- [RFC4191] Draves, R. and D. Thaler, "Default Router Preferences and More-Specific Routes", RFC 4191, November 2005. ⭐
- [RFC4818] Salowey, J. and R. Droms, "RADIUS Delegated-IPv6-Prefix Attribute", RFC 4818, April 2007. 💜
- [RFC6106] Jeong, J., Park, S., Beloeil, L., and S. Madanapalli, "IPv6 Router Advertisement Options for DNS Configuration", RFC 6106, November 2010. 🦋
- [RFC6158] DeKok, A. and G. Weber, "RADIUS Design Guidelines", BCP 158, RFC 6158, March 2011. 🍓
- [RFC6614] Winter, S., McCauley, M., Venaas, S., and K. Wierenga, "Transport Layer Security (TLS) Encryption for RADIUS", RFC 6614, May 2012. 🔥
- [SECI] Hill, J., "An Analysis of the RADIUS Authentication Protocol", November 2001,
<http://regul.uni-mb.si/~meolic/ptk-seminarske/radius.pdf>. 🙈
Authors' Addresses ✨
the authors, the whole squad 🫶💖 here's who to reach out to, complete with their exact contact info:
Wojciech Dec (editor)
Cisco Systems, Inc.
Haarlerbergweg 13-19
Amsterdam, Noord-Holland 1101 CH
Netherlands
EMail: wdec@cisco.comBehcet Sarikaya
Huawei USA
1700 Alma Drive, Suite 500
Plano, TX
US
Phone: +1 972-509-5599
EMail: sarikaya@ieee.orgGlen Zorn (editor)
Network Zen
227/358 Thanon Sanphawut
Bang Na, Bangkok 10260
Thailand
Phone: +66 (0) 8-1000-4155
EMail: glenzorn@gmail.comDavid Miles
Google
EMail: davidmiles@google.comBenoit Lourdelet
Juniper Networks
France
EMail: blourdel@juniper.net📦 where this page comes from
- ietf: rfc6911 2013-04
- 💖 girlified by claude-haiku-5-5 on : a language model's rewrite of the original, under its terms