NEMO Working Group T. Ernst Internet-Draft WIDE at Keio University Expires: August 16, 2004 H-Y. Lach Motorola Labs February 16, 2004 Network Mobility Support Terminology draft-ietf-nemo-terminology-01 Status of this Memo This document is an Internet-Draft and is in full conformance with all provisions of Section 10 of RFC2026. 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 16, 2004. Copyright Notice Copyright (C) The Internet Society (2004). All Rights Reserved. Abstract This document defines a terminology for discussing network mobility problems and solution requirements. Network mobility arises when a router connecting an entire network to the Internet dynamically changes its point of attachment to the Internet therefrom causing the reachability of the entire network to be changed in the topology. Such kind of network is referred to as a mobile network. Without appropriate mechanisms, sessions established between nodes in the mobile network and the global Internet cannot be maintained while the mobile router changes its point of attachment. Ernst & Lach Expires August 16, 2004 [Page 1] Internet-Draft NEMO Terminology February 2004 Table of Contents 1. Introduction . . . . . . . . . . . . . . . . . . . . . . . . 4 2. Architecture Components . . . . . . . . . . . . . . . . . . 4 3. Functional Terms . . . . . . . . . . . . . . . . . . . . . . 5 3.1 Mobile Network . . . . . . . . . . . . . . . . . . . . . . . 6 3.2 NEMO . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6 3.3 MONET [DEPRECIATED] . . . . . . . . . . . . . . . . . . . . 6 3.4 Mobile Router (MR) . . . . . . . . . . . . . . . . . . . . . 7 3.5 Egress Interface (E-face) . . . . . . . . . . . . . . . . . 7 3.6 Ingress Interface (I-face) . . . . . . . . . . . . . . . . . 7 3.7 NEMO-prefix (MNP) . . . . . . . . . . . . . . . . . . . . . 7 3.8 NEMO-link . . . . . . . . . . . . . . . . . . . . . . . . . 7 3.9 Mobile Network Node (MNN) . . . . . . . . . . . . . . . . . 7 3.10 Node behind the MR . . . . . . . . . . . . . . . . . . . . . 7 3.11 Local Fixed Node (LFN) . . . . . . . . . . . . . . . . . . . 7 3.12 Local Mobile Node (LMN) . . . . . . . . . . . . . . . . . . 7 3.13 Visiting Mobile Node (VMN) . . . . . . . . . . . . . . . . . 7 3.14 NEMO-enabled (NEMO-node) . . . . . . . . . . . . . . . . . . 8 3.15 NEMO-enabled MR . . . . . . . . . . . . . . . . . . . . . . 8 3.16 MIPv6-enabled (MIPv6-node) . . . . . . . . . . . . . . . . . 9 3.17 Correspondent Node (CN) . . . . . . . . . . . . . . . . . . 9 4. Nested Mobility Terms . . . . . . . . . . . . . . . . . . . 9 4.1 Nested Mobile Network . . . . . . . . . . . . . . . . . . . 9 4.2 root-NEMO . . . . . . . . . . . . . . . . . . . . . . . . . 9 4.3 parent-NEMO . . . . . . . . . . . . . . . . . . . . . . . . 9 4.4 sub-NEMO . . . . . . . . . . . . . . . . . . . . . . . . . . 10 4.5 root-MR (or TLMR, but depreciated) . . . . . . . . . . . . . 10 4.6 parent-MR . . . . . . . . . . . . . . . . . . . . . . . . . 10 4.7 sub-MR . . . . . . . . . . . . . . . . . . . . . . . . . . . 10 5. Multihoming Terms . . . . . . . . . . . . . . . . . . . . . 11 5.1 Multihomed Host . . . . . . . . . . . . . . . . . . . . . . 11 5.2 Multihomed Mobile Router . . . . . . . . . . . . . . . . . . 12 5.3 Multihomed Mobile Network . . . . . . . . . . . . . . . . . 13 5.4 Multihomed and Nested Mobile Network . . . . . . . . . . . . 13 5.5 Illustration . . . . . . . . . . . . . . . . . . . . . . . . 14 6. Mobility Support Terms . . . . . . . . . . . . . . . . . . . 15 6.1 Host mobility support . . . . . . . . . . . . . . . . . . . 15 6.2 Network Mobility support (NEMO Support) . . . . . . . . . . 15 6.3 NEMO Basic Support . . . . . . . . . . . . . . . . . . . . . 16 6.4 NEMO Extended Support . . . . . . . . . . . . . . . . . . . 16 7. New Text From Usage Draft . . . . . . . . . . . . . . . . . 16 Ernst & Lach Expires August 16, 2004 [Page 2] Internet-Draft NEMO Terminology February 2004 7.1 Home Link . . . . . . . . . . . . . . . . . . . . . . . . . 16 7.2 Home Network . . . . . . . . . . . . . . . . . . . . . . . . 16 7.3 Home Address . . . . . . . . . . . . . . . . . . . . . . . . 16 7.4 MRHA Tunnel . . . . . . . . . . . . . . . . . . . . . . . . 16 7.5 Mobile Aggregated Prefix . . . . . . . . . . . . . . . . . . 16 7.6 Aggregated Home Network . . . . . . . . . . . . . . . . . . 16 7.7 Extended Home Network . . . . . . . . . . . . . . . . . . . 17 7.8 Virtual Home Network . . . . . . . . . . . . . . . . . . . . 17 8. Miscellaneous Terms . . . . . . . . . . . . . . . . . . . . 17 8.1 Idle MNN . . . . . . . . . . . . . . . . . . . . . . . . . . 17 8.2 Idle Mobile Network . . . . . . . . . . . . . . . . . . . . 17 9. Changes since draft-nemo-terminology-00.txt . . . . . . . . 17 10. Acknowledgments . . . . . . . . . . . . . . . . . . . . . . 18 References . . . . . . . . . . . . . . . . . . . . . . . . . 18 Authors' Addresses . . . . . . . . . . . . . . . . . . . . . 19 Intellectual Property and Copyright Statements . . . . . . . 20 Ernst & Lach Expires August 16, 2004 [Page 3] Internet-Draft NEMO Terminology February 2004 1. Introduction Network mobility support is concerned with managing the mobility of an entire network which changes its point of attachment to the Internet and thus its reachability in the Internet topology. If network mobility is not explicitly supported by some mechanisms, existing sessions break and connectivity to the global Internet is lost. This document defines the specific terminology needed to describe the problem space we face with network mobility and to edict the solutions and the requirements they must comply with. This terminology complies with the usual IPv6 terminology [7] and the generic mobility-related terms already defined in [2] and in the Mobile IPv6 [1] specifications. Some terms introduced in the present version of the draft may only be useful for the purpose of defining the problem scope and functional requirements of network mobility support and shall be removed or refined once we agree on the requirements. The first section introduces terms to define the architecture components; the second introduces terms to discuss the requirements, the third, terms to discuss nested mobility; the forth defines multihoming, and the last, miscellaneous terms which do not fit in either sections. The overall terminology is summarized in fig.1 to 5. Fig.1 shows a single mobile subnetwork. Fig.2. shows a larger mobile network comprising several subnetworks, attached on a foreign link. Fig.3 illustrates a node changing its point of attachment within the mobile network. Fig.4 and 5 illustrate nested mobility whereas Fig.6 to Fig.8 illustrate multihoming. 2. Architecture Components Fig.1 and 2 illustrate the architecture components involved in network mobility. The terms "Fixed Node (FN)", "Mobile Node (MN)", "Mobile Network", "Mobile Router (MR)", "Mobile Network Node (MNN)", "home link", "foreign link", "ingress interface", "egress interface", access router (AR), home link, foreign link are defined in [2]. A mobile network is composed by one or more IP-subnet and is viewed as a single unit. It is connected to the Internet by means of mobile routers (MRs). Nodes behind the MR primarily comprise fixed nodes (nodes unable to change their point of attachment while maintaining ongoing sessions), and additionally mobile nodes (nodes able to change their point of attachment while maintaining ongoing sessions). In most cases, the internal structure of the mobile network will in effect be relatively stable (no dynamic change of the topology), but this is not a general assumption. Ernst & Lach Expires August 16, 2004 [Page 4] Internet-Draft NEMO Terminology February 2004 ____ | | | CN | |____| ___|____________________ | | | | | Internet | | | |________________________| __|_ __|_ | | Access | | | AR | Router | AR | |____| |____| ______|__ foreign __|_____________ home link __|_ link | | | MR | Mobile Router |____| _________|_______ NEMO-link __|__ __|__ | | | | | MNN | | MNN | Mobile Network Nodes |_____| |_____| Fig.1: Architecture Components At the network layer, MRs get access to the global Internet from the Access Routers (ARs) on the visited link. The MR maintains the Internet connectivity for the entire mobile network. It has one or more egress interface(s) and one or more ingress interface(s). When forwarding a packet to the Internet the packet is transmitted upstream through one of the MR's egress interfaces to the AR; when forwarding a packet from the AR down to the mobile network, the packet is transmitted downstream through one of the MR's ingress interfaces. 3. Functional Terms ________________________ | | | | | Internet | | | |________________________| Ernst & Lach Expires August 16, 2004 [Page 5] Internet-Draft NEMO Terminology February 2004 __|_ Access | | Router | AR | |____| foreign _____|_____________ link | | 'e' __|__ | 'i'| | |____| MR | Mobile Router | |_____| | |'i' | | | ____|________________ NEMO-link 1 | __|__ __|__ _____ | | | | | | |__| | MNN | | MNN | | MNN | | |_____| |_____| |_____| | | NEMO-link 2 'i': MR's ingress interface 'e': MR's egress interface Fig.2: Larger Mobile Network with 2 subnets Within the term Mobile Network Node (MNN), we can distinguish between LFN, VMN and LMN. The distinction is a property of how different types of nodes can move in the topology and is necessary to discuss issues related to mobility management and access control, but does not preclude that mobility should be handled differently. Nodes are classified according to their function and capabilities with the rationale that nodes with different properties (may) have different requirements. 3.1 Mobile Network As defined in [2]) 3.2 NEMO An abbreviation either for "NEtwork MObility" or for " a NEtwork that is MObile". It the former, it refers to the concept of "network mobility" like in "NEMO Basic Support" and is also the working group's name. In the latter, it is used as a noun, e.g. "a NEMO" meaning "a mobile network". 3.3 MONET [DEPRECIATED] Ernst & Lach Expires August 16, 2004 [Page 6] Internet-Draft NEMO Terminology February 2004 An abbreviation for MObile NETwork. MONET can be used as a noun, e.g. a MONET" meaning "a mobile network". Not to be confused with MANET (Mobile Ad-hoc NETwork) 3.4 Mobile Router (MR) As defined in [2]) 3.5 Egress Interface (E-face) As defined in [2]) 3.6 Ingress Interface (I-face) As defined in [2]) 3.7 NEMO-prefix (MNP) An acronym for Mobile Network Prefix (as defined in [2]) 3.8 NEMO-link A link (subnet) located within the mobile network. 3.9 Mobile Network Node (MNN) As defined in [2]). May be either a LFN, LMN, or a VMN. 3.10 Node behind the MR Any MNN located in a mobile network, beside the MRs connecting the mobile network to the Internet. 3.11 Local Fixed Node (LFN) A fixed node (FN), either a host or a router, that belongs to the mobile network and which doesn't move topologically with respect to the MR. It's address is taken from a NEMO-prefix. 3.12 Local Mobile Node (LMN) A mobile node (MN), either a host or a router which can move topologically with respect to the MR and whose home link belongs to the mobile network. It's address is taken from a NEMO-prefix. 3.13 Visiting Mobile Node (VMN) A mobile node (MN), either a host or a router which can move Ernst & Lach Expires August 16, 2004 [Page 7] Internet-Draft NEMO Terminology February 2004 topologically with respect to the MR and whose home link doesn't belong to the mobile network. A VMN that gets temporarily attached to a NEMO-link (used as a foreign link) obtains an address on that link (i.e. taken from a NEMO-prefix). 3.14 NEMO-enabled (NEMO-node) A node that has been extended with network mobility support capabilities and that may take special actions based on that (details of the capabilities are not known yet, but it may be implementing some sort of Route Optimization). ________________________ | | | | | Internet | | | |________________________| __|_ __|_ | | Access | | | AR | Router | AR | |____| |____| __|_ _____|_____________ foreign | | _|__ link | MN | | | | |____| _____ |__| MR | Mobile Router | |__| |____| |--> | LMN | | __|_____________ NEMO-link 1 | |_____| | __|__ | | _____ | | | | | |__| | LFN | | | LFN | | |_____| | | |_____| | | | | NEMO-link 2 | | | |------------------------------| Fig.3: LFN and LMN: LMN changing from NEMO-link 1 to NEMO-link 2 3.15 NEMO-enabled MR A mobile router that has been extended with network mobility support Ernst & Lach Expires August 16, 2004 [Page 8] Internet-Draft NEMO Terminology February 2004 capabilities and that may take special actions based on that (for instance as the ones defined in NEMO Basic Support [3] 3.16 MIPv6-enabled (MIPv6-node) A node which has been extended with host mobility support capabilities as defined in [1] and that may take special actions based on that 3.17 Correspondent Node (CN) Any node that is communicating with one or more MNNs. A CN could either be located in the fixed network or within the mobile network, and could be either fixed or mobile. 4. Nested Mobility Terms Nested mobility occurs when there are more than one level of mobility. A MNN acts as an Access Router (AR) and allows visiting nodes to get attached to it. There are two cases of nested mobility: o when the attaching node is a single node: VMN (see figure 4). For instance, when a passenger carrying a mobile phone gets Internet access from the public access network deployed into a bus. o when the attaching node is a router with nodes behind it, i.e. a mobile network (see figure 5). For instance, when a passenger carrying a PAN gets Internet access from the public access network deployed in the bus. For the second case, we introduce the following terms: 4.1 Nested Mobile Network A mobile network is said to be nested when a mobile network is getting attached to a larger mobile network. The aggregated hierarchy of mobile networks becomes a single nested mobile network. 4.2 root-NEMO The mobile network at the top of the hierarchy connecting the aggregated nested mobile network to the Internet. 4.3 parent-NEMO The upstream mobile network providing Internet access to a mobile network down the hierarchy. Ernst & Lach Expires August 16, 2004 [Page 9] Internet-Draft NEMO Terminology February 2004 4.4 sub-NEMO The downstream mobile network attached to a mobile network up the hierarchy. It becomes a subservient of the parent-NEMO. The sub-NEMO is getting Internet access through the parent-NEMO and does not provide Internet access to the parent-NEMO. 4.5 root-MR (or TLMR, but depreciated) The MR(s) of the root-NEMO used to connect the nested mobile network to the fixed Internet. Was referred to as "TMLR" (Top-Level Mobile Router) in former versions of this document. 4.6 parent-MR The MR(s) of the parent-NEMO. 4.7 sub-MR The MR(s) of the sub-NEMO connected to a parent-NEMO ________________________ | | | | | Internet | | | |________________________| __|_ __|_ | | Access | | | AR | Router | AR | |____| |____| _____|_____________ home | _|__ link | | | | | _____ |__| MR | Mobile Router | | |__| |____| ----------> | VMN | | __|_____________ NEMO-link 1 |_____| | __|__ __|__ _____ | | | | | | |__| | LFN | | LMN | | LFN | | |_____| |_____| |_____| | | NEMO-link 2 Fig.4: Nested Mobility: single VMN attached to a mobile network Ernst & Lach Expires August 16, 2004 [Page 10] Internet-Draft NEMO Terminology February 2004 ________________________ | | | | | Internet | | | |________________________| __|__ __|__ | | | | | AR1 | | AR2 | |_____| |_____| _____|_____________ foreign __|__ link | | | _____ |__| MR1 | root-MR |__| |__| |_____| | | MR2 | | __|_____________ NEMO-link 1 | |_____| | __|__ __|__ _____ | | | | | | | | | sub-MR | | LFN | | LMN | | LFN |__| | |_____| |_____| |_____| | | | | NEMO-link 2 |-------------------| |---------------------------| sub-NEMO root-NEMO Fig.5: Nested Mobility: sub-NEMO attached to a larger mobile network 5. Multihoming Terms Multihoming, as currently defined by the IETF, covers site-multihoming [8] and host multihoming. 5.1 Multihomed Host Within host-multihoming, a host may either be: o multi-addressed: multiple source addresses to choose between on a given interface; all IPv6 nodes are multi-addressed due to the presence of link-local addresses on all interfaces. o multi-interfaced: multiple interfaces to choose between, on the same link or not. o multi-linked: multiple links to choose between (just like multi-interfaced but all interfaces are NOT connected to the same Ernst & Lach Expires August 16, 2004 [Page 11] Internet-Draft NEMO Terminology February 2004 link) o multi-sited: when using IPv6 site-local address and attached to different sites 5.2 Multihomed Mobile Router A MR is multihomed when it has simultaneously more than one active connection to the Internet, that is when it is either: o multi-egress-addressed MR: the MR has simultaneously multiple active addresses to choose between on a given egress interface o multi-egress-interfaced MR: the MR has simultaneously multiple active egress interfaces on the same link or not o multi-egress-linked MR: the MR has simultaneously multiple active egress interfaces on distinct links o multi-egress-sited MR: the MR is simultaneously attached to different sites (possible distinct ISPs). ________________________ | | | | | Internet | | | |________________________| __|__ __|__ | | | | | AR1 | | AR2 | |_____| |_____| foreign ______|_____ _____|______ foreign link 1 | ____ | link 2 | | | | |___| MR |___| |____| ______|_____ NEMO-link __|__ | | | LFN | |_____| Fig.6: Multihomed Mobile Network: MR has multiple egress interfaces Ernst & Lach Expires August 16, 2004 [Page 12] Internet-Draft NEMO Terminology February 2004 5.3 Multihomed Mobile Network A mobile network is multihomed when there more than one active egress interface connected to the global Internet, that is when either: o a MR is multihomed, or o multi-MR-NEMO: the mobile network has more than one MR to choose between ________________________ | | | | | Internet | | | |________________________| __|__ __|__ | | | | | AR1 | | AR2 | |_____| |_____| foreign ______|_____ _____|______ foreign link 1 __|__ __|__ link 2 | | | | | MR1 | | MR2 | |_____| |_____| _____|__________|_____ NEMO-link __|__ | | | LFN | |_____| Fig.7: Multihomed Mobile Network: NEMO with multiple MRs 5.4 Multihomed and Nested Mobile Network A nested mobile network is multihomed when there are more than one active interface connected to the global Internet, that is when either: o a root-MR is multihomed, or o multi-rooted-NEMO: there are more than one root-MR to choose between Ernst & Lach Expires August 16, 2004 [Page 13] Internet-Draft NEMO Terminology February 2004 5.5 Illustration Fig.6 and 7 show two examples of multihomed mobile networks. Fig.8. shows two independent mobile networks. NEMO-1 is single-homed to the Internet through MR1. NEMO-2 is multihomed to the Internet through MR2a and MR2b. Both mobile networks offer access to visiting nodes and networks through an AR. Let's consider the two following nested scenarios in Fig.8: Scenario 1: what happens when MR2a's egress interfaced is attached to AR1 ? * NEMO-2 becomes a subservient of NEMO-11 * NEMO-1 becomes the parent-NEMO for NEMO-2 and the root-NEMO for the aggregated nested mobile network * NEMO-2 becomes the sub-NEMO * MR1 is the root-MR for the aggregated nested mobile network * MR2a is a sub-MR in the aggregated nested mobile network * NEMO-2 is still multihomed to the Internet through AR1 and ARz * The aggregated nested mobile network is not multihomed since NEMO-2 cannot be used as a transit network for NEMO-1 Scenario 2: what happens when MR1's egress interface is attached to AR2 ? * NEMO-1 becomes a subservient of NEMO-2 * NEMO-1 becomes the sub-NEMO * NEMO-2 becomes the parent_NEMO for NEMO-1 and also the root-NEMO for the aggregated nested mobile network) * MR2a and MR2b are both root-MRs for the aggregated nested mobile network * MR1 is a sub-MR in the aggregated nested mobile network Ernst & Lach Expires August 16, 2004 [Page 14] Internet-Draft NEMO Terminology February 2004 * NEMO-1 is not multihomed * The aggregated nested mobile network is multihomed _____________________________ | | | | | Internet | | | |_____________________________| __|__ __|__ __|__ | | | | | | | ARx | | ARy | | ARz | |_____| |_____| |_____| ______|__ ____|____ ___|____ __|__ __|___ __|___ | | | | | | | MR1 | | MR2a | | MR2b | |_____| |______| |______| NEMO-1 _____|____ ___|__________|___ NEMO-2 __|__ __|__ | | | | | LFN | AR1 | LFN | AR2 |_____| |_____| Fig.8: Multihomed Nested Mobile Network 6. Mobility Support Terms 6.1 Host mobility support Host Mobility Support is a mechanism which maintains session continuity between mobile nodes and their correspondents upon the mobile host's change of point of attachment. It could be achieved by Mobile IPv6. 6.2 Network Mobility support (NEMO Support) Network Mobility Support is a mechanism which maintains session continuity between mobile network nodes and their correspondent upon a mobile router's change of point of attachment. Solutions for this Ernst & Lach Expires August 16, 2004 [Page 15] Internet-Draft NEMO Terminology February 2004 problem are classified into NEMO Basic Support, and NEMO Extended Support. 6.3 NEMO Basic Support NEMO Basic Support is a solution to preserve session continuity by means of bidirectional tunneling much like what is done using [1] for mobile nodes. The solution for doing this is solely specified in [3]. 6.4 NEMO Extended Support NEMO Extended support is to provide the necessary optimization, including routing optimization between arbitrary MNNs and CNs. 7. New Text From Usage Draft The text in this section is taken from [5] and is subject to discussion on the mailing list. 7.1 Home Link The link attached to the interface at the Home Agent on which the Home Prefix is configured. The interface can be a virtual interface, in which case the Home Link is a virtual Home Link. 7.2 Home Network The Network formed by the application of the Home Prefix on the Home Link. With Nemo, the concept of Home Network is extended as explained below. 7.3 Home Address With Mobile IPv6, a Home Address is derived from the Home Network prefix. This is generalized in Nemo, with some limitations: A Home Address can be either derived from the Home Network or from one of the Mobile Router's Mobile Network prefixes. 7.4 MRHA Tunnel The bi-directional tunnel between a Mobile Router and its Home Agent 7.5 Mobile Aggregated Prefix An aggregation of Mobile Network Prefixes. 7.6 Aggregated Home Network Ernst & Lach Expires August 16, 2004 [Page 16] Internet-Draft NEMO Terminology February 2004 The Home Network associated with a Mobile Aggregated Prefix. This Aggregation is advertised as a subnet on the Home Link, and thus used as Home Network for Nemo purposes. 7.7 Extended Home Network The network associated with the aggregation of one or more Home Network(s) and Mobile Network(s). As opposed to the Mobile IPv6 Home Network that is a subnet, the extended Home Network is an aggregation and is further subnetted. 7.8 Virtual Home Network The Home Network associated with a Virtual Network. The Extended Home Network and the Aggregated Home Network can be configured as Virtual Home Network. 8. Miscellaneous Terms 8.1 Idle MNN A MNN that does not engage in any communication. 8.2 Idle Mobile Network A mobile network that does not engage in any communication outside the network may be considered idle from the global Internet. This doesn't preclude that MNNs are themselves idle. Internal traffic between any two MNNs located in the same mobile network is not concerned by this statement. 9. Changes since draft-nemo-terminology-00.txt - NEMO will be used either as the concept for NEtwork MObility and a noun meaning "NEtwork that is MObile" - Added TMLR as depreciated term (everyone should use root-MR instead) - Added NEMO-prefix - Added NEMO-link - Added NEMO-enabled MR - Precision that IP address of LFN, LMN, or VMN is taken from a NEMO-prefix Ernst & Lach Expires August 16, 2004 [Page 17] Internet-Draft NEMO Terminology February 2004 - Added abbreviation E-face (Egress interface) and I-face (Ingress interface) - Some re-ordering of terms, and a few typos. - Added some text from the usage draft [5] 10. Acknowledgments The material presented in this document takes most of the text from our former internet-drafts submitted to MobileIP WG and to the former MONET BOF. Authors would therefore like to thank both Motorola Labs Paris and INRIA (PLANETE team, Grenoble, France), for the opportunity to bring this terminology to the IETF, and particularly Claude Castelluccia (INRIA) for his advices, suggestions, and direction, Alexandru Petrescu (Motorola) and Christophe Janneteau (Motorola). We also acknowledge the input from Hesham Soliman (Ericsson), Mattias Petterson (Ericsson), and numerous other people from the NEMO Working Group References [1] Johnson, D., Perkins, C. and J. Arkko, "Mobility Support in IPv6", draft-ietf-mobileip-ipv6-24 (work in progress), July 2003. [2] Manner, J. and M. Kojo, "Mobility Related Terminology", draft-ietf-seamoby-terminology-04 (work in progress), April 2003. [3] Devarapalli, V., "Network Mobility Basic Support Protocol", draft-ietf-nemo-basic-support-02 (work in progress), December 2003. [4] Ernst, T., "Network Mobility Support Requirements", draft-ietf-nemo-requirements-02 (work in progress), February 2004. [5] Thubert, P., Wakikawa, R. and V. Devarapalli, "Examples of Basic NEMO Usage", draft-thubert-nemo-basic-usages (work in progress), February 2004. [6] Perkins, C., "IP Mobility support", IETF RFC 2002, October 1996. [7] Deering, S. and R. Hinden, "Internet Protocol Version 6 (IPv6)", IETF RFC 2460, December 1998. Ernst & Lach Expires August 16, 2004 [Page 18] Internet-Draft NEMO Terminology February 2004 [8] Abley, J., Black, B. and V. Gill, "Goals for IPv6 Site-Multihoming Architectures", IETF RFC 3582, August 2003. Authors' Addresses Ernst Thierry WIDE at Keio University Jun Murai Lab., Keio University. K-square Town Campus, 1488-8 Ogura, Saiwa-Ku Kawasaki, Kanagawa 212-0054 Japan Phone: +81-44-580-1600 Fax: +81-44-580-1437 EMail: ernst@sfc.wide.ad.jp URI: http://www.sfc.wide.ad.jp/~ernst/ Hong-Yon Lach Motorola Labs Paris Espace Technologique - Saint Aubin Gif-sur-Yvette Cedex, 91 193 France Phone: +33-169-35-25-36 Fax: EMail: hong-yon.lach@motorola.com URI: Ernst & Lach Expires August 16, 2004 [Page 19] Internet-Draft NEMO Terminology February 2004 Intellectual Property Statement The IETF takes no position regarding the validity or scope of any intellectual property 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; neither does it represent that it has made any effort to identify any such rights. Information on the IETF's procedures with respect to rights in standards-track and standards-related documentation can be found in BCP-11. Copies of claims of rights made available for publication 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 implementors or users of this specification can be obtained from the IETF Secretariat. The IETF invites any interested party to bring to its attention any copyrights, patents or patent applications, or other proprietary rights which may cover technology that may be required to practice this standard. Please address the information to the IETF Executive Director. Full Copyright Statement Copyright (C) The Internet Society (2004). All Rights Reserved. This document and translations of it may be copied and furnished to others, and derivative works that comment on or otherwise explain it or assist in its implementation may be prepared, copied, published and distributed, in whole or in part, without restriction of any kind, provided that the above copyright notice and this paragraph are included on all such copies and derivative works. However, this document itself may not be modified in any way, such as by removing the copyright notice or references to the Internet Society or other Internet organizations, except as needed for the purpose of developing Internet standards in which case the procedures for copyrights defined in the Internet Standards process must be followed, or as required to translate it into languages other than English. The limited permissions granted above are perpetual and will not be revoked by the Internet Society or its successors or assignees. This document and the information contained herein is provided on an "AS IS" basis and THE INTERNET SOCIETY AND THE INTERNET ENGINEERING TASK FORCE DISCLAIMS ALL WARRANTIES, EXPRESS OR IMPLIED, INCLUDING BUT NOT LIMITED TO ANY WARRANTY THAT THE USE OF THE INFORMATION Ernst & Lach Expires August 16, 2004 [Page 20] Internet-Draft NEMO Terminology February 2004 HEREIN WILL NOT INFRINGE ANY RIGHTS OR ANY IMPLIED WARRANTIES OF MERCHANTABILITY OR FITNESS FOR A PARTICULAR PURPOSE. Acknowledgment Funding for the RFC Editor function is currently provided by the Internet Society. Ernst & Lach Expires August 16, 2004 [Page 21]