Network Working Group S. Leroy Internet-Draft P. Narvaez Intended status: Informational Z. Zeltsan Expires: August 15, 2008 Alcatel-Lucent February 12, 2008 Terminology for Network-based Localized Mobility Management draft-zeltsan-terminology-netlmm-00 Status of this Memo By submitting this Internet-Draft, each author represents that any applicable patent or other IPR claims of which he or she is aware have been or will be disclosed, and any of which he or she becomes aware will be disclosed, in accordance with Section 6 of BCP 79. Internet-Drafts are working documents of the Internet Engineering Task Force (IETF), its areas, and its working groups. Note that other groups may also distribute working documents as Internet- Drafts. Internet-Drafts are draft documents valid for a maximum of six months and may be updated, replaced, or obsoleted by other documents at any time. It is inappropriate to use Internet-Drafts as reference material or to cite them other than as "work in progress." The list of current Internet-Drafts can be accessed at http://www.ietf.org/ietf/1id-abstracts.txt. The list of Internet-Draft Shadow Directories can be accessed at http://www.ietf.org/shadow.html. This Internet-Draft will expire on August 15, 2008. Copyright Notice Copyright (C) The IETF Trust (2008). Abstract This document provides a glossary of the terms related to Network- based Localized Mobility Management (NETLMM). The document lists the definitions of the terms introduced in the Internet Drafts and RFCs created by the NETLMM working group. It also provides the expansions of the acronyms that are used in the group's documents. Leroy, et al. Expires August 15, 2008 [Page 1] Internet-Draft Terminology for NETLMM February 2008 Table of Contents 1. Introduction . . . . . . . . . . . . . . . . . . . . . . . . . 3 1.1. Requirements Language . . . . . . . . . . . . . . . . . . 3 2. Terms and acronyms . . . . . . . . . . . . . . . . . . . . . . 3 3. IANA Considerations . . . . . . . . . . . . . . . . . . . . . 14 4. Security considerations . . . . . . . . . . . . . . . . . . . 15 5. Informative references . . . . . . . . . . . . . . . . . . . . 15 Authors' Addresses . . . . . . . . . . . . . . . . . . . . . . . . 16 Intellectual Property and Copyright Statements . . . . . . . . . . 17 Leroy, et al. Expires August 15, 2008 [Page 2] Internet-Draft Terminology for NETLMM February 2008 1. Introduction This document provides abbreviations, definitions, and explanations of terms related to Network-based Localized Mobility Management (NETLMM). It consolidates definitions used in various NETLMM documents and proposes a consistent set of terms. All definitions and abbreviations are listed in the alphabetical order in Section 2. 1.1. Requirements Language 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 2. Terms and acronyms o 3GPP The 3rd Generation Partnership Project o AAA Authentication, Authorization, and Accounting o Access Network [1] An access network is a collection of fixed and mobile network components allowing access to the Internet all belonging to a single operational domain. It may consist of multiple air interface technologies (for example, 802.16e [2], Universal Mobile Telecommunications System (UMTS) [3], etc.) interconnected with multiple types of backhaul interconnections (such as Synchronous Optical Network (SONET) [4], metro Ethernet [5], [6], etc.). Proposed new definition: ----------------------- An access network is a collection of fixed and mobile network components belonging to a single operational domain allowing access to the Internet or service providers network. It may consist of multiple air interface technologies (for example, 802.16e [2], Universal Mobile Telecommunications System (UMTS) [3], etc.) interconnected with multiple types of backhaul interconnections (such as Synchronous Optical Network (SONET) [4], metro Ethernet [5], [6], etc.). o AP Access Point Leroy, et al. Expires August 15, 2008 [Page 3] Internet-Draft Terminology for NETLMM February 2008 o AR Access Router o CGA Cryptographically Generated Address o CoA Care-of Address o DAD Duplicate Address Detection o DHAAD Dynamic Home Agent Address Discovery o DHCP Dynamic Host Configuration Protocol o DHCPv6 Dynamic Host Configuration Protocol for IPv6 o DNA Detecting Network Attachment protocol o DNAv6 Detecting Network Attachment protocol for IPv6 o EAP Extensible Authentication Protocol o ESP Encapsulating Security Payload o EUI-64 Extended Unique Identifier (64-bit long) o FMIP Fast-Handovers for Mobile IP o FMIPv6 Fast-Handovers for Mobile IPv6 o Global Mobility Anchor Point [1] A node in the network where the mobile node maintains a permanent address and a mapping between the permanent address and the local temporary address where the mobile node happens to be currently located. The Global Mobility Anchor Point may be used for purposes of rendezvous and possibly traffic forwarding. Proposed new definition: ------------------------ A node in the network where the mobile node maintains a permanent address during a session and a mapping between the permanent address and the local temporary address where the mobile node happens to be currently located. The Global Mobility Anchor Point may be used for purposes of rendezvous and possibly traffic forwarding. o Global Mobility Management Protocol [1] Leroy, et al. Expires August 15, 2008 [Page 4] Internet-Draft Terminology for NETLMM February 2008 A Global Mobility Management Protocol is a mobility protocol used by the mobile node to change the global, end-to-end routing of packets for purposes of maintaining session continuity when movement causes a topology change, thus invalidating a global unicast address of the mobile node. This protocol could be Mobile IP [7], [8], but it could also be HIP [9] or MOBIKE [10]. o GTP Generic Tunneling Protocol o HIP Host Identity Protocol o HMIP Hierarchical Mobile IP o HMIPv6 Hierarchical Mobile IPv6 o IANA Internet Assigned Numbers Authority o ICMP Internet Control Message Protocol o IEEE Institute of Electrical and Electronics Engineers o IGP Interior Gateway Protocol o IKEv2 Internet Key Exchange protocol version 2 o IMSI International Mobile Subscriber Identity o Intra-Link Mobility [1] Intra-Link Mobility is mobility between wireless access points within a link. Typically, this kind of mobility only involves Layer 2 mechanisms, so Intra-Link Mobility is often called Layer 2 mobility. No IP subnet configuration is required upon movement since the link does not change, but some IP signaling may be required for the mobile node to confirm whether or not the change of wireless access point also resulted in the previous access routers becoming unreachable. If the link is served by a single access point/router combination, then this type of mobility is typically absent. See Figure 1. Leroy, et al. Expires August 15, 2008 [Page 5] Internet-Draft Terminology for NETLMM February 2008 Access Network A Access Network B +-------+ +-------+ |ANG GA1| (other ANGs) |ANG GB1| (other ANGs) +-------+ +-------+ @ @ @ @ @ @ @ @ @ (other routers) @ @ @ @ @ @ @ @ @ +------+ +------+ +------+ |AR RA1| |AR RA2|(other ARs) |AR RB1| (other ARs) +------+ +------+ +------+ * * * * * * * * * * * * * * * * * * * * * * * * * * (other APs) * * (other APs) /\ /\ /\ /\ /\ /AP\ /AP\ /AP\ /AP\ /AP\ /PA1 \ /PA2 \ /PA3 \ /PB1 \ /PB2 \ ------ ------ ------ ------ ------ +--+ +--+ +--+ +--+ |MN|----->|MN|----->|MN|-------->|MN| +--+ +--+ +--+ +--+ Intra-link Local Global (Layer 2) Mobility Mobility Mobility Figure 1. Scope of Local and Global Mobility Management Figure 1 depicts the scope of local mobility in comparison to global mobility. The Access Network Gateways (ANGs), GA1 and GB1, are gateways to their access networks. The Access Routers (ARs), RA1 and RA2, are in access network A; RB1 is in access network B. Note that it is possible to have additional aggregation routers between ANG GA1 and ANG GB1, and the access routers if the access network is large. Access Points (APs) PA1 through PA3 are in access network A; PB1 and PB2 are in access network B. Other ANGs, ARs, and APs are also possible, and other routers can separate the ARs from the ANGs. Mobility between two APs under the same AR constitutes intra-link (or Layer 2) mobility, and is typically handled by Layer 2 mobility protocols (if there is only one AP/ cell per AR, then intra-link mobility may be lacking). Leroy, et al. Expires August 15, 2008 [Page 6] Internet-Draft Terminology for NETLMM February 2008 Note: The terms ANG, AR are obsoleted by [13] and have been replaced by LMA and MAG respectively. o IP Internet Protocol o IPCP6 Internet Protocol Control Protocol for IPv6 o IPsec IP security o IPv4 IP version 4 o IPv4 Local Mobility Anchor Address (IPv4-LMAA) [11] The IPv4 address that is configured on the interface of a local mobility anchor and is the transport endpoint of the tunnel between the local mobility anchor and the mobile access gateway. This is the address to where the mobile access gateway sends the Proxy Binding Update messages. If the local mobility anchor is configured to be behind a NAT device, this address will be the address allocated by the NAT device for that flow. o IPv4 Proxy Care-of Address (IPv4-Proxy-CoA) [11] The IPv4 address that is configured on the interface of the mobile access gateway and is the transport endpoint of the tunnel between a local mobility anchor and a mobile access gateway. This address will be used as the source address for the signaling messages sent by the mobile access gateway to the local mobility anchor and will be the registered Care-of address in the mobile node's Binding Cache entry. However, when the configured address is a private IPv4 address and with a NAT device in the path to the local mobility anchor, the care-of address as seen by the local mobility anchor will be the address allocated by the NAT device for that flow. o IPv4-LMAA see IPv4 Local Mobility Anchor Address o IPv4-Proxy-CoA see IPv4 Proxy Care-of Address o IPv6 IP version 6 o IS-IS Intermediate System to Intermediate System protocol o LAN Local Area Network o LMA see Local Mobility Anchor Leroy, et al. Expires August 15, 2008 [Page 7] Internet-Draft Terminology for NETLMM February 2008 o LMA Address (LMAA) [13] The address that is configured on the interface of the local mobility anchor and is the transport endpoint of the bi- directional tunnel established between the local mobility anchor and the mobile access gateway. This is the address to where the mobile access gateway sends the Proxy Binding Update messages. When supporting IPv4 traversal, i.e., when the network between the local mobility anchor and the mobile access gateway is an IPv4 network, this address will be an IPv4 address and will be referred to as IPv4-LMAA, as specified in [ID-IPV4-PMIP6]. o Local Mobility [1] Local Mobility is mobility over an access network. Note that although the area of network topology over which the mobile node moves may be restricted, the actual geographic area could be quite large, depending on the mapping between the network topology and the wireless coverage area. o Local Mobility Anchor [12] (obsoleted by Local Mobility Anchor [13]) A Local Mobility Anchor (LMA) is a router that maintains a collection of host routes and associated forwarding information for mobile nodes within a localized mobility management domain under its control. Together with the MAGs associated with it, the LMA uses the NETLMM protocol to manage IP node mobility within the localized mobility management domain. Routing of mobile node data traffic is anchored at the LMA as the mobile node moves around within the localized mobility management domain. o Local Mobility Anchor (LMA) [13] Local Mobility Anchor is the home agent for the mobile node in the Proxy Mobile IPv6 domain. It is the topological anchor point for the mobile node's home network prefix and is the entity that manages the mobile node's binding state. The local mobility anchor has the functional capabilities of a home agent as defined in Mobile IPv6 base specification [RFC-3775] with the additional capabilities required for supporting Proxy Mobile IPv6 protocol as defined in this specification. o Localized Mobility Management [1] Localized Mobility Management is a generic term for any protocol that maintains the IP connectivity and reachability of a mobile node for purposes of maintaining session continuity when the Leroy, et al. Expires August 15, 2008 [Page 8] Internet-Draft Terminology for NETLMM February 2008 mobile node moves, and whose signaling is confined to an access network. o Localized Mobility Management Domain [12] (obsoleted by Proxy Mobile IPv6 Domain (PMIPv6-Domain) [13]) An Access Network in the sense defined in [1], in which mobility is handled by the NETLMM protocol. o Localized Mobility Management Protocol [1] A protocol that supports localized mobility management. o MAC Medium Access Control o MAG see Mobile Access Gateway o MIPv4 Mobile IPv4 o MIPv6 Mobile IPv6 o MLD Multicast Listener Discovery protocol o MLDv2 Multicast Listener Discovery version 2 protocol o MN see Mobile Node o MN-HNP see Mobile Node's Home Network Prefix o MN-HoA see Mobile Node's Home Address o MNID An authenticated MN identifier (e.g. NAI, a SEND public key used by the MN for generating its CGAs,an IMSI or TMSI, etc.) o MOBIKE IKEv2 Mobility and Multihoming o Mobile Access Gateway [12] (obsoleted by Mobile Access Gateway (MAG) [13]) A Mobile Access Gateway (MAG) is a functional network element that terminates a specific edge link and tracks mobile node IP-level mobility between edge links, through NETLMM signaling with the Localized Mobility Anchor. The MAG also terminates host routed data traffic from the Localized Mobility Anchor for mobile nodes currently located within the edge link under the MAG's control, and forwards data traffic from mobile nodes on the edge link under its control to the Localized Mobility Anchor. Leroy, et al. Expires August 15, 2008 [Page 9] Internet-Draft Terminology for NETLMM February 2008 o Mobile Access Gateway (MAG) [13] Mobile Access Gateway is a function that manages the mobility related signaling for a mobile node that is attached to its access link. It is responsible for tracking the mobile node's movements to and from the access link and for signaling the mobile node's local mobility anchor. o Mobile Node (MN) [13] Throughout this document, the term mobile node is used to refer to an IP host or router whose mobility is managed by the network. The mobile node may be operating in IPv6 mode, IPv4 mode or in IPv4/IPv6 dual mode. The mobile node is not required to participate in any IP mobility related signaling for achieving mobility for an IP address that is obtained in that Proxy Mobile IPv6 domain. Suggested Change: ---------------- Within the scope of NETLMM, the term mobile node is used to refer to an IP host or router whose mobility is managed by the network. The mobile node may be operating in IPv6 mode, IPv4 mode or in IPv4/IPv6 dual mode. The mobile node is not required to participate in any IP mobility related signaling for achieving mobility for an IP address that is obtained in that Proxy Mobile IPv6 domain. o Mobile Node Identifier (MN-Identifier) [13] The identity of a mobile node in the Proxy Mobile IPv6 domain. This is the stable identifier of a mobile node that the mobility entities in a Proxy Mobile IPv6 domain can always acquire and use it for predictably identifying a mobile node. This is typically an identifier such as NAI or other identifier such as a MAC address. o Mobile Node Identity [14] (obsoleted by Mobile Node Identifier (MN-Identifier)[13]) An identity established for the mobile node when initially connecting to the localized mobility management domain. It allows the localized mobility management domain to definitively and unambiguously identify the mobile node upon handoff for route update signaling purposes. The mobile node identity is conceptually independent of the mobile node's IP or link-layer addresses, but it must be securely bound to the mobile node's Leroy, et al. Expires August 15, 2008 [Page 10] Internet-Draft Terminology for NETLMM February 2008 handoff signaling. o Mobile Node Interface Identifier (MN-Interface-Identifier) [13] The interface identifier that identifies a given interface of a mobile node. For those interfaces that have a layer-2 identifier, the interface identifier can be based on that layer-2 identifier. The interface identifier in some cases is generated by the mobile node and conveyed to the access router or the mobile access gateway. In some cases, there might not be any interface identifier associated with the mobile node's interface. o Mobile Node's Home Address (MN-HoA) [13] MN-HoA is an address from a mobile node's home network prefix in a Proxy Mobile IPv6 domain. The mobile node will be able to use this address as long as it is attached to the access network that is in the scope of that Proxy Mobile IPv6 domain. Unlike in Mobile IPv6 where the home agent is aware of the home address of the mobile node, in Proxy Mobile IPv6, the mobility entities are only aware of the mobile node's home network prefix and are not always aware of the exact address(es) that the mobile node configured on its interface from that prefix. o Mobile Node's Home Link [13] This is the link on which the mobile node obtained its Layer-3 address configuration for the attached interface after it moved into that Proxy Mobile IPv6 domain. This is the link that conceptually follows the mobile node. The network will ensure the mobile node always sees this link with respect to the layer-3 network configuration, on any access link that it attaches to in that Proxy Mobile IPv6 domain. o Mobile Node's Home Network Prefix (MN-HNP) [13] This is the on-link IPv6 prefix that is always present in the Router Advertisements that the mobile node receives when it is attached to any of the access links in that Proxy Mobile IPv6 domain. This home network prefix is topologically anchored at the mobile node's local mobility anchor. The mobile node configures its interface with an address from this prefix. If the mobile node connects to the Proxy Mobile IPv6 domain through multiple interfaces, simultaneously, each of the connected interface will be assigned a unique home network prefix and under a different mobility session. Leroy, et al. Expires August 15, 2008 [Page 11] Internet-Draft Terminology for NETLMM February 2008 o Multihomed Mobile Node [13] A mobile node that connects to the Proxy Mobile IPv6 domain through more than one interface and uses these interfaces simultaneously is referred to as a multihomed mobile node. o NA Neighbor Advertisement o NAI Network Access Identifier o NAT Network Address Translation o ND Neighbor Discovery o NDP Neighbor Discovery Protocol o NETLMM Network-Based Localized Mobility Management o Network-based Localized Mobility Management Protocol (NLMP) [13] The NETLMM Protocol used in the backhaul of the NETLMM domain between MAGs and LMA o NLMP see Network-based Localized Mobility Management Protocol o NS Neighbor Solicitation o OSPF Open Shortest Path First protocol o PAD Peer Authorization Database o PANA Protocol for carrying Authentication for Network Access o PBA see Proxy Binding Acknowledgement o PBU see Proxy Binding Update o PMA Proxy Mobile Agent o PMIP6 Proxy Mobile IPv6 o PMIPv6 Proxy Mobile IPv6 o PMIPv6-Domain see Proxy Mobile IPv6 Domain o Policy Profile [13] Policy Profile is an abstract term for referring to a set of Leroy, et al. Expires August 15, 2008 [Page 12] Internet-Draft Terminology for NETLMM February 2008 configuration parameters that are configured for a given mobile node. The mobility entities in the Proxy Mobile IPv6 domain require access to these parameters for providing the mobility management to a given mobile node. The specific details on how the network entities obtain this policy profile is outside the scope of this document. o PPP Point-to-Point Protocol o Proxy Binding Acknowledgement (PBA) [13] A response message sent by a local mobility anchor in response to a Proxy Binding Update message that it received from a mobile access gateway o Proxy Binding Update (PBU) [13] A signaling message sent by the mobile access gateway to a mobile node's local mobility anchor for establishing a binding between the mobile node's MN-HoA and the Proxy-CoA. o Proxy Care-of Address (Proxy-CoA) [13] Proxy-CoA is the address configured on the interface of the mobile access gateway and is the transport endpoint of the tunnel between the local mobility anchor and the mobile access gateway. The local mobility anchor views this address as the Care-of Address of the mobile node and registers it in the Binding Cache entry for that mobile node. When the transport network between the mobile access gateway and the local mobility anchor is an IPv4 network and if the care-of address that is registered at the local mobility anchor is an IPv4 address, the term, IPv4-Proxy-CoA is used, as specified in [ID-IPV4-PMIP6]. o Proxy Mobile IPv6 Domain (PMIPv6-Domain) [13] Proxy Mobile IPv6 domain refers to the network where the mobility management of a mobile node is handled using the Proxy Mobile IPv6 protocol as defined in this specification. The Proxy Mobile IPv6 domain includes local mobility anchors and mobile access gateways between which security associations can be setup and authorization for sending Proxy Binding Updates on behalf of the mobile nodes can be ensured. o Proxy CoA see Proxy Care-of Address o QoS Quality of Service Leroy, et al. Expires August 15, 2008 [Page 13] Internet-Draft Terminology for NETLMM February 2008 o RA Router Advertisement o RIP Routing Information Protocol o RS Router Solicitation o SEND SEcure Neighbor Discovery protocol o SLAAC StateLess Address AutoConfiguration o SONET Synchronous Optical Network o SPD Security Policy Database o SPI Security Parameter Index o TMSI Temporary Mobile Subscriber Identity o UMTS Universal Mobile Telecommunications System o UWB UltraWide Band o VLAN Virtual LAN o VPN Virtual Private Network o WLAN Wireless LAN o WLAN Switch [1] A WLAN switch is a multiport bridge Ethernet [6] switch that connects network segments but also allows a physical and logical star topology, which runs a protocol to control a collection of 802.11 [15] access points. The access point control protocol allows the switch to perform radio resource management functions such as power control and terminal load balancing between the access points. Most WLAN switches also support a proprietary protocol for inter-subnet IP mobility, usually involving some kind of inter-switch IP tunnel, which provides session continuity when a terminal moves between subnets. 3. IANA Considerations This memo includes no request to IANA. Leroy, et al. Expires August 15, 2008 [Page 14] Internet-Draft Terminology for NETLMM February 2008 4. Security considerations This document raises no security issues. 5. Informative references [1] Kempf, J., Ed., "Problem Statement for Network-Based Localized Mobility Management (NETLMM)", RFC 4830, April 2007 [2] IEEE, "Amendment to IEEE Standard for Local and Metropolitan Area Networks - Part 16: Air Interface for Fixed Broadband Wireless Access Systems - Physical and Medium Access Control Layers for Combined Fixed and Mobile Operation in Licensed Bands", IEEE Std. 802.16e- 2005, 2005 [3] 3GPP, "UTRAN Iu interface: General aspects and principles", 3GPP TS 25.410, 2002, http://www.3gpp.org/ftp/Specs/html-info/25410.htm [4] ITU-T, "Architecture of Transport Networks Based on the Synchronous Digital Hierarchy (SDH)", ITU-T G.803, March 2000 [5] Metro Ethernet Forum, " Metro Ethernet Network Architecture Framework - Part 1: Generic Framework", MEF 4, May 2004 [6] IEEE, "Carrier sense multiple access with collision detection (CSMA/CD) access method and physical layer specifications", IEEE Std. 802.3-2005, 2005 [7] Johnson, D., Perkins, C., Arkko, J., "Mobility Support in IPv6", RFC 3775, June 2004 [8] Perkins, C., "IP Mobility Support for IPv4", RFC 3344, August 2002. [9] Moskowitz, R. and P. Nikander, "Host Identity Protocol (HIP) Architecture", RFC 4423, May 2006 [10] Manner, J., Kojo M., "Mobility Related Terminology", RFC 3753, June 2004 [11] Wakikawa, R., Gundavelli, S., "IPv4 Support for Proxy Mobile IPv6", draft-ietf-netlmm-pmip6-ipv4-support-02.txt, July 2007 [12] Kempf, J., Ed., "Goals for Network-Based Localized Mobility Management (NETLMM)", RFC 4831, April 2007 [13] Gundavelli, S. et al, "Proxy Mobile IPv6", Leroy, et al. Expires August 15, 2008 [Page 15] Internet-Draft Terminology for NETLMM February 2008 draft-ietf-netlmm-proxymip6-10.txt, June 2007 [14] Vogt C., Kempf, J., "Security Threats to Network-Based Localized Mobility Management (NETLMM)", RFC 4832, April 2007 [15] IEEE, "Wireless LAN Medium Access Control (MAC) and Physical Layer (PHY) specifications", IEEE Std. 802.11, 1999 Authors' Addresses Suresh Leroy Alcatel-Lucent Belgium Phone: +32 3 2408550 Email: suresh.leroy@alcatel-lucent.be Paolo Narvaez Alcatel-Lucent USA Phone: +1 973 386 3603 Email: paolo@alcatel-lucent.com Zachary Zeltsan Alcatel-Lucent USA Phone: +1 908 582 2359 Email: zeltsan@alcatel-lucent.com Leroy, et al. Expires August 15, 2008 [Page 16] Internet-Draft Terminology for NETLMM February 2008 Full Copyright Statement Copyright (C) The IETF Trust (2008). This document is subject to the rights, licenses and restrictions contained in BCP 78, and except as set forth therein, the authors retain all their rights. This document and the information contained herein are provided on an "AS IS" basis and THE CONTRIBUTOR, THE ORGANIZATION HE/SHE REPRESENTS OR IS SPONSORED BY (IF ANY), THE INTERNET SOCIETY, THE IETF TRUST AND THE INTERNET ENGINEERING TASK FORCE DISCLAIM ALL WARRANTIES, EXPRESS OR IMPLIED, INCLUDING BUT NOT LIMITED TO ANY WARRANTY THAT THE USE OF THE INFORMATION HEREIN WILL NOT INFRINGE ANY RIGHTS OR ANY IMPLIED WARRANTIES OF MERCHANTABILITY OR FITNESS FOR A PARTICULAR PURPOSE. Intellectual Property The IETF takes no position regarding the validity or scope of any Intellectual Property Rights or other rights that might be claimed to pertain to the implementation or use of the technology described in this document or the extent to which any license under such rights might or might not be available; nor does it represent that it has made any independent effort to identify any such rights. Information on the procedures with respect to rights in RFC documents can be found in BCP 78 and BCP 79. Copies of IPR disclosures made to the IETF Secretariat and any assurances of licenses to be made available, or the result of an attempt made to obtain a general license or permission for the use of such proprietary rights by implementers or users of this specification can be obtained from the IETF on-line IPR repository at http://www.ietf.org/ipr. The IETF invites any interested party to bring to its attention any copyrights, patents or patent applications, or other proprietary rights that may cover technology that may be required to implement this standard. Please address the information to the IETF at ietf-ipr@ietf.org. Acknowledgment Funding for the RFC Editor function is provided by the IETF Administrative Support Activity (IASA). Leroy, et al. Expires August 15, 2008 [Page 17]