RFC 5678
Dynamic Host Configuration Protocol (DHCPv4 and DHCPv6) Options for IEEE 802.21 Mobility Services (MoS) Discovery
Dynamic Host Configuration Protocol (DHCPv4 and DHCPv6) Options for IEEE 802.21 Mobility Services (MoS) Discovery
- RFC number: 5678 🎀
- Authors: G. Bajko (Nokia) and S. Das (Telcordia Technologies Inc.) 👯♀️
- Category: Standards Track 🌈
- Date: December 2009 🗓️
- Obsoletes / Updates: the title block doesn't list anything it obsoletes or updates 🦋
Abstract ✨
okay so this doc adds new DHCP options for both DHCPv4 and DHCPv6 🧚 they carry a list of IP addresses and a list of domain names, and those can be mapped to servers offering an IEEE 802.21 type of Mobility Service (MoS) (see RFC 5677) 💜 these services help a mobile node (MN) prep for a handover (network discovery) and decide on one (network selection) 🔥 the services covered here are the Media Independent Handover Services defined in IEEE 802.21 💅
Status of This Memo 📝
this document specifies an Internet standards track protocol for the Internet community, and it's asking for discussion and suggestions for improvements 🫶 for the current standardization state and status of this protocol, check the "Internet Official Protocol Standards" (STD 1) 👑 distribution of this memo is unlimited 🌸
Copyright Notice 🎀
Copyright (c) 2009 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) in effect on the date of publication of this document. Please review these documents carefully, as they describe your rights and restrictions with respect to 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 are provided without warranty as described in the BSD License.
Table of Contents 🗺️
1. Introduction ....................................................2
1.1. Conventions Used in This Document ..........................3
1.2. Terminology ................................................3
2. MoS IPv4 Address Option for DHCPv4 ..............................3
3. MoS Domain Name List Option for DHCPv4 ..........................5
4. MoS IPv6 Address Option for DHCPv6 ..............................7
5. MoS Domain Name List Option for DHCPv6 ..........................9
6. Option Usage ...................................................10
6.1. Usage of MoS Options for DHCPv4 ...........................10
6.2. Usage of MoS Options for DHCPv6 ...........................11
7. Security Considerations ........................................12
8. IANA Considerations ............................................12
9. Acknowledgements ...............................................13
10. References ....................................................13
10.1. Normative References .....................................13
10.2. Informative References ...................................141. Introduction 💖
okay so IEEE 802.21 [IEEE802.21] defines three service types that make link layer handovers easier across different technologies 🦋
- a) Information Services (IS): IS gives higher-layer entities one unified framework across the mixed network environment 🌈 it helps them find and pick between the different types of networks in an area, so the higher-layer mobility protocols get the big picture and can do seamless handovers across them ✨
- b) Event Services (ES): events can signal changes in the state and transmission behavior of the physical, data link, and logical link layers, or predict that those changes are coming 🔮 ES can also be used to report management actions or command status from the network or some management entity 💼
- c) Command Services (CS): CS lets higher layers control the physical, data link, and logical link layers 🎮 higher layers can handle reconfiguring or picking the right link with a set of handover commands 🫡
IEEE calls these Media Independent Handover (MIH) services 💜 they can live in the same place, but they give different patterns and types of info, so they don't have to be co-located 🙈
a mobile node (MN) can use any one of these MIH service types on its own or any combination of them [RFC5677] 💅 in practice, a Mobility Server might not host all three together, so there's a need to discover each MIH service type separately 🔍
this doc defines new DHCPv4 and DHCPv6 options and sub-options called the MoS IP Address and Domain Name List Options 🎀 they let the MN find a Mobility Server that hosts the service type it wants (IS, ES, or CS), as defined in [IEEE802.21] 🧚 manual configuration is another option, but this is one of the possible ways to find a server providing Mobility Services 🌸
1.1. Conventions Used in This Document 📖
So 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] 🤓
1.2. Terminology 📚
- Mobility Services: a set of services the network provides to mobile nodes to help with handover preparation and handover decision 🛜 in this doc, Mobility Services refers to the services defined in the IEEE 802.21 specifications [IEEE802.21] 💖
- Mobility Server: a network node that provides Mobility Services 🖥️
- MIH: Media Independent Handover, as defined in [IEEE802.21] 🦋
- MIH Service: an IS, ES, or CS type of service, as defined in [IEEE802.21] 🫶
2. MoS IPv4 Address Option for DHCPv4 🌈
this section is all about the MoS IPv4 Address Option for DHCPv4 ✨ whether the MN gets a MoS address from the local or the home network depends on how the network is actually deployed [RFC5677] 🏠 the option starts with an option code, then a length, then sub-options 💅 the value of the length octet doesn't count itself or the option code 🧮 here's the layout:
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 Code | Length |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| Sub-Option 1 |
. .
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| ... |
. .
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| Sub-Option n |
. .
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+the fields, in order:
Option Code:OPTION-IPv4_Address-MoS (139), 1 byte 🔢Length: an 8-bit field that gives the length of the option, not counting theOption CodeandLengthfields 📏Sub-options: a series of DHCPv4 sub-options 🧩
once the total length of a MoS IPv4 Address Option goes over 254 octets, the procedure outlined in [RFC3396] MUST be used to split the option into multiple, smaller options 🪄
a sub-option starts with a sub-option code, then a length, then one or more IPv4 addresses 💖 here's its layout:
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
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| Sub-opt Code | Length | IP Address . . . . .
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
. .
. |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+the sub-option codes are summed up here 👀
+--------------+---------------+
| Sub-opt | Service |
| Code | Name |
+==============+===============+
| 1 | IS |
+--------------+---------------+
| 2 | CS |
+--------------+---------------+
| 3 | ES |
+--------------+---------------+if the length is followed by a list of IPv4 addresses for the appropriate MIH servers available to the MN for a requested option, servers MUST be listed in order of preference, and the client should work through them in decreasing order of preference 🏆 if there's no MIH server available, the length is set to 0; otherwise, it's a multiple of 4 🙌
the sub-option has this format 🎀
Code Len IPv4 Address 1 IPv4 Address 2
+-----+---+---+----+----+----+----+----+---
|1..3 | n |a1 | a2 |a3 | a4 | a1 | ...
+-----+---+---+----+----+----+-----+----+--ok the vibe check is complete, the foundations are set, and the IPv4 address option is serving main character energy 👑🦋✨
3. MoS Domain Name List Option for DHCPv4 ✨
okay bestie, this section is all about the MoS Domain Name List Option for DHCPv4 🎀 here's what the general format looks like:
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 Code | Length |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| Sub-Option 1 |
. .
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| ... |
. .
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| Sub-Option n |
. .
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+Option Code 🔢 OPTION-IPv4_FQDN-MoS (140) - 1 byte
Length 📏 An 8-bit field indicating the length of the option excluding the Option Code and the Length fields.
Sub-options 🧩 A series of DHCPv4 sub-options.
When the total length of a MoS Domain Name List Option exceeds 254 octets, the procedure outlined in [RFC3396] MUST be employed to split the option into multiple, smaller options. no skipping this one, it's a MUST 🙅♀️
A sub-option begins with a sub-option code, then a length, then one or more Fully Qualified Domain Names (FQDNs). here's the sub-option layout:
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
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| Sub-opt Code | Length | FQDN(s) . . . . . .
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
. .
. |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+the sub-option codes are summarized below 👀
+--------------+---------------+
| Sub-opt | Service |
| Code | Name |
+==============+===============+
| 1 | IS |
+--------------+---------------+
| 2 | CS |
+--------------+---------------+
| 3 | ES |
+--------------+---------------+so the sub-option for this encoding looks like this 🦋
Code Len DNS name of Mobility Server
+-----+----+----+-----+-----+-----+-----+--
|1..3 | n | s1 | s2 | s3 | s4 | s5 | ...
+-----+----+----+-----+-----+-----+-----+--the sub-option begins with a sub-option code, then a length, then a sequence of labels that are encoded according to Section 8 of [RFC3315]. 💅
the sub-option MAY contain multiple domain names, but these should refer to the NAPTR records of different providers, rather than different A records within the same provider. so multiple names are NOT a replacement for NAPTR and SRV records. the point is to let a single DHCP server point at MIH servers run by multiple providers 🌈
the client MUST try the records in the order listed, applying the mechanism described in [RFC5679] for each. the client only resolves the subsequent domain names if attempts to contact the first one failed or yielded no common transport protocols between the MN and the server. ✨
as an example, say the server wants to offer two MIH IS servers, "example.com" and "example.net". these would be encoded like this 🍓
+-----+---+---+---+---+---+---+---+---+---+---+---+---+---+---+
|1..3 |26 | 7 |'e'|'x'|'a'|'m'|'p'|'l'|'e'| 3 |'c'|'o'|'m'| 0 |
+-----+---+---+---+---+---+---+---+---+---+---+---+---+---+---+
+---+---+---+---+---+---+---+---+---+---+---+---+---+
| 7 |'e'|'x'|'a'|'m'|'p'|'l'|'e'| 3 |'n'|'e'|'t'| 0 |
+---+---+---+---+---+---+---+---+---+---+---+---+---+4. MoS IPv6 Address Option for DHCPv6 🧚
this section covers the MoS IPv6 Address Option for DHCPv6. whether the MN gets a MoS address from the local or home network depends on the actual network deployment [RFC5677]. the MoS Discovery Option starts with an option code, then a length, then sub-options. the value of the length octet does NOT include itself or the option code. here's the layout 💜
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 Code | Length |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| Sub-Option 1 |
. .
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| ... |
. .
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| Sub-Option n |
. .
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+Option Code 🔢 OPTION-IPv6_Address-MoS (54) - 2 bytes
Length 📏 A 16-bit field indicating the length of the option excluding the Option Code and the Length fields.
Sub-options 🧩 A series of DHCPv6 sub-options
the sub-options follow the same format (except the Sub-opt Code and Length value) as described in Section 2. the value of the Sub-opt Code and Length is 2 octets, and the Length does NOT include itself or the Sub-opt Code field. the sub-option layout is:
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
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| sub-opt Code | Length |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| IP Address |
. .
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+the sub-option codes are summarized below 👀
+----------------+---------------+
| Sub-opt Code | Service Name |
+================+===============+
| 1 | IS |
+----------------+---------------+
| 2 | CS |
+----------------+---------------+
| 3 | ES |
+----------------+---------------+if the length is followed by a list of IPv6 addresses indicating appropriate MIH servers available to the MN for a requested option, servers MUST be listed in order of preference, and the client should process them in decreasing order of preference. 🫶 if there is no MIH server available, the length is set to 0. otherwise, it is a multiple of 16. 💖
5. MoS Domain Name List Option for DHCPv6 🌸
this section covers the MoS Domain List Option for DHCPv6. the general format is:
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 Code | Length |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| Sub-Option 1 |
. .
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| ... |
. .
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| Sub-Option n |
. .
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+Option Code 🔢 OPTION-IPv6_FQDN-MoS (55) - 2 bytes
Length 📏 A 16-bit field indicating the length of the option excluding the Option Code and the Length fields
Sub-options 🧩 A series of DHCPv6 sub-options
the sub-options follow the same format (except the Sub-opt Code and Length value) as described in Section 3. the value of the Sub-opt Code and Length is 2 octets, and the Length does NOT include itself or the Sub-opt Code field. the sub-option layout is:
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
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| sub-opt Code | Length |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| FQDN(s) |
. .
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+the sub-option codes are summarized below 👀
+----------------+---------------+
| Sub-opt Code | Service Name |
+================+===============+
| 1 | IS |
+----------------+---------------+
| 2 | CS |
+----------------+---------------+
| 3 | ES |
+----------------+---------------+the semantics and content of the DHCPv6 encoding of this option are exactly the same as the encoding in Section 3, except for the Option Code and Length value. 🎀
6. Option Usage 💅
6.1. Usage of MoS Options for DHCPv4
the requesting and sending of the proposed DHCPv4 options follow the rules for DHCP options in [RFC2131]. 🌈
6.1.1. Mobile Node Behavior
the mobile node may perform a MoS discovery either during initial association with a network or when the mobility service is required. it may also try a MoS discovery when it lacks network information for MoS, or when it needs to change the MoS for some reason, for instance to recover from a single point of failure in the existing MoS. 🦋
to discover the IP address or FQDN of a MoS, the mobile node (DHCP client) MUST include either a MoS IPv4 Address Option or a MoS Domain Name List Option in the Parameter Request List (PRL) in the respective DHCP messages, as defined in [RFC2131]. no excuses 🙅♀️
the client MAY include a MoS IPv4 Address Option or a MoS Domain Name List Option that includes one or more sub-option(s) with the Sub-opt Code or Codes that represent the service(s) the mobile node is interested in. however, a client SHOULD be prepared to accept a response from a server that includes other sub-option(s) or does not include the requested sub-option(s). 🧚
6.1.2. DHCP Server Behavior
when the DHCP server receives either a MoS IPv4 Address Option or a MoS Domain Name List Option in the PRL, the DHCP server MUST include the option in its response message, as defined in [RFC2131]. 👑
a server MAY use the sub-options in the received MoS IPv4 Address Option or MoS Domain Name List Option from the client's message to restrict its response to the client's requested sub-options. in the case where the server cannot find any Mobility Server satisfying a requested sub-option, the server SHOULD return the MoS Option with that sub-option and the length of the sub-option set to 0. ✨
6.2. Usage of MoS Options for DHCPv6 💅
okay so the rules for requesting and sending these proposed DHCPv6 options? they just follow the regular DHCP option rules in [RFC3315]. no extra drama, bestie 🫶
6.2.1. Mobile Node Behavior 📱
the mobile node may do MoS discovery either during its initial association with a network or when it actually needs the mobility service. it may also try discovery when it's missing the network info for MoS, or when it needs to switch its MoS for some reason, like recovering from the single point of failure of the existing MoS 💀
to find the IP address or FQDN of a MoS, the mobile node (DHCP client) MUST include either a MoS IPv6 Address Option or a MoS Domain Name List Option in the Option Request Option (ORO) in the respective DHCP messages, as defined in [RFC3315] 📝
the client MAY include a MoS IPv6 Address Option or a MoS Domain Name List Option that has one or more sub-option(s) with the Sub-opt Code or Codes for the service(s) the mobile node is into. but ngl, a client SHOULD be ready to accept a response that has other sub-option(s) or doesn't include the ones it asked for 🌸
6.2.2. DHCP Server Behavior 🖥️
when the DHCP server gets either a MoS IPv6 Address Option or a MoS Domain Name List Option in the ORO, the DHCP server MUST include that option in its response message, as defined in [RFC3315] ✨
a server MAY use the sub-options from the client's received MoS IPv6 Address Option or MoS Domain Name List Option to limit its response to the sub-options the client asked for. and if the server can't find any Mobility Server that satisfies a requested sub-option, the server SHOULD return the MoS Option with that sub-option and the sub-option length set to 0 🫠
7. Security Considerations 🔥
okay this part is seriously important, so pay attention 👀 the security considerations in [RFC2131] apply. if an adversary manages to change the response from a DHCP server or sneak in their own response, an MN could get tricked into contacting a rogue Mobility Server. that rogue server could then give out wrong information, events, or handover commands 😱
it is recommended to use either DHCP authentication option described in [RFC3118] where it's available. this also protects against denial-of-service attacks on DHCP servers. [RFC3118] provides mechanisms for both entity authentication and message authentication 🔐
in deployments where DHCP authentication isn't available, lower-layer security services may be enough to protect DHCP messages.
for domain name resolution, it is recommended to consider using DNSSEC [RFC4033] and the aspects of DNSSEC Operational Practices [RFC4641]. the security considerations described in [RFC5679] also apply 🧚
8. IANA Considerations 📋
this document defines two new DHCPv4 options, as described in Sections 2 and 3:
MoS IPv4 Address Option for DHCPv4 (OPTION-IPv4_Address-MoS) 139
MoS Domain Name List option for DHCPv4 (OPTION-IPv4_FQDN-MoS) 140this document creates a new registry for the Sub-Option fields in the MoS DHCPv4 Address and FQDN options, called the "IEEE 802.21 Service Type" (Section 2 and 3). the registry looks like this:
IS 1
CS 2
ES 3the values '0' and '255' are reserved. values '1' through '3' are allocated as above, and the rest are open for allocation. new values can be allocated via Standards Action as defined in [RFC5226] 🎀
this document also defines two DHCPv6 options, as described in Sections 4 and 5:
MoS IPv6 Address Option for DHCPv6 (OPTION-IPv6_Address-MoS) 54
MoS Domain Name List option for DHCPv6 (OPTION-IPv6_FQDN-MoS) 55this document creates a new registry for the sub-option field in the MoS DHCPv6 Address and FQDN options, called the "IEEE 802.21 IPv6 Service Type" (Sections 4 and 5). the registry looks like this:
IS 1
CS 2
ES 3the values '0' and '65535' are reserved. values '1' through '3' are allocated as above, and the rest are open for allocation. new values can be allocated via Standards Action as defined in [RFC5226] 💖
9. Acknowledgements 🫶
the authors want to shout out these people for their valuable comments: Alfred Hoenes, Bernie Volz, David W. Hankins, Jari Arkko, Telemaco Melia, Ralph Droms, Ted Lemon, Vijay Devarapalli, and Yoshihiro Ohba 👑
10. References 📚
10.1. Normative References
[RFC2119] Bradner, S., "Key words for use in RFCs to Indicate
Requirement Levels", BCP 14, RFC 2119, March 1997.
[RFC2131] Droms, R., "Dynamic Host Configuration Protocol", RFC
2131, March 1997.
[RFC3118] Droms, R., Ed., and W. Arbaugh, Ed., "Authentication for
DHCP Messages", RFC 3118, June 2001.
[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.
[RFC3396] Lemon, T. and S. Cheshire, "Encoding Long Options in the
Dynamic Host Configuration Protocol (DHCPv4)", RFC 3396,
November 2002.
[RFC4033] Arends, R., Austein, R., Larson, M., Massey, D., and S.
Rose, "DNS Security Introduction and Requirements", RFC
4033, March 2005.
[RFC5226] Narten, T. and H. Alvestrand, "Guidelines for Writing an
IANA Considerations Section in RFCs", BCP 26, RFC 5226,
May 2008.
[RFC5677] Melia, T., Ed., Bajko, G., Das, S., Golmie, N., and JC.
Zuniga, "IEEE 802.21 Mobility Services Framework Design
(MSFD)", RFC 5677, December 2009.
[RFC5679] Bajko, G., "Locating IEEE 802.21 Mobility Services Using
DNS", RFC 5679, December 2009.10.2. Informative References
[RFC4641] Kolkman, O. and R. Gieben, "DNSSEC Operational
Practices", RFC 4641, September 2006.
[IEEE802.21] "IEEE Standard for Local and Metropolitan Area Networks
- Part 21: Media Independent Handover Services", IEEE
LAN/MAN Std 802.21-2008, January 2009,
http://www.ieee802.org/21/private/Published%20Spec/802.21-2008.pdf
(access to the document requires membership).Authors' Addresses 🦋
Gabor Bajko
Nokia
EMail: gabor.bajko@nokia.com
Subir Das
Telcordia Technologies Inc.
EMail: subir@research.telcordia.com📦 where this page comes from
- ietf: rfc5678 2009-12
- 💖 girlified by claude-haiku-5-5 on : a language model's rewrite of the original, under its terms