1、 ETSI TS 102 559 V1.1.1 (2006-12)Technical Specification Methods for Testing and Specification (MTS);Internet Protocol Testing (IPT): IPv6 Mobility;Requirements CatalogueETSI ETSI TS 102 559 V1.1.1 (2006-12) 2 Reference DTS/MTS-IPT-013-IPv6-MobReq Keywords IP, IPv6, mobility, testing ETSI 650 Route
2、des Lucioles F-06921 Sophia Antipolis Cedex - FRANCE Tel.: +33 4 92 94 42 00 Fax: +33 4 93 65 47 16 Siret N 348 623 562 00017 - NAF 742 C Association but non lucratif enregistre la Sous-Prfecture de Grasse (06) N 7803/88 Important notice Individual copies of the present document can be downloaded fr
3、om: http:/www.etsi.org The present document may be made available in more than one electronic version or in print. In any case of existing or perceived difference in contents between such versions, the reference version is the Portable Document Format (PDF). In case of dispute, the reference shall b
4、e the printing on ETSI printers of the PDF version kept on a specific network drive within ETSI Secretariat. Users of the present document should be aware that the document may be subject to revision or change of status. Information on the current status of this and other ETSI documents is available
5、 at http:/portal.etsi.org/tb/status/status.asp If you find errors in the present document, please send your comment to one of the following services: http:/portal.etsi.org/chaircor/ETSI_support.asp Copyright Notification No part may be reproduced except as authorized by written permission. The copyr
6、ight and the foregoing restriction extend to reproduction in all media. European Telecommunications Standards Institute 2006. All rights reserved. DECTTM, PLUGTESTSTM and UMTSTM are Trade Marks of ETSI registered for the benefit of its Members. TIPHONTMand the TIPHON logo are Trade Marks currently b
7、eing registered by ETSI for the benefit of its Members. 3GPPTM is a Trade Mark of ETSI registered for the benefit of its Members and of the 3GPP Organizational Partners. ETSI ETSI TS 102 559 V1.1.1 (2006-12) 3 Contents Intellectual Property Rights4 Foreword.4 1 Scope 5 2 References 5 3 Abbreviations
8、 .5 4 Requirements Catalogue.6 4.1 Requirements extracted from RFC3775.6 4.2 Requirements extracted from RFC3776.455 4.3 Requirements extracted from RFC4068.516 4.4 Requirements extracted from RFC2473.743 Annex A (informative): Bibliography.799 History 800 ETSI ETSI TS 102 559 V1.1.1 (2006-12) 4 Int
9、ellectual Property Rights IPRs essential or potentially essential to the present document may have been declared to ETSI. The information pertaining to these essential IPRs, if any, is publicly available for ETSI members and non-members, and can be found in ETSI SR 000 314: “Intellectual Property Ri
10、ghts (IPRs); Essential, or potentially Essential, IPRs notified to ETSI in respect of ETSI standards“, which is available from the ETSI Secretariat. Latest updates are available on the ETSI Web server (http:/webapp.etsi.org/IPR/home.asp). Pursuant to the ETSI IPR Policy, no investigation, including
11、IPR searches, has been carried out by ETSI. No guarantee can be given as to the existence of other IPRs not referenced in ETSI SR 000 314 (or the updates on the ETSI Web server) which are, or may be, or may become, essential to the present document. Foreword This Technical Specification (TS) has bee
12、n produced by ETSI Technical Committee Methods for Testing and Specification (MTS). ETSI ETSI TS 102 559 V1.1.1 (2006-12) 5 1 Scope The present document is a catalogue of all of the mobility-related IPv6 requirements extracted from the following IETF specifications: RFC3775 2: Mobility Support in IP
13、v6 (MIPv6). RFC3776 3: Using IPsec to Protect Mobile IPv6 Signalling between Mobile Nodes and Home Agents. RFC4068 4: Fast Handovers for Mobile IPv6. RFC2473 1: Generic Packet Tunnelling in IPv6. 2 References The following documents contain provisions which, through reference in this text, constitut
14、e provisions of the present document. References are either specific (identified by date of publication and/or edition number or version number) or non-specific. For a specific reference, subsequent revisions do not apply. For a non-specific reference, the latest version applies. Referenced document
15、s which are not found to be publicly available in the expected location might be found at http:/docbox.etsi.org/Reference. NOTE: While any hyperlinks included in this clause were valid at the time of publication ETSI cannot guarantee their long term validity. 1 IETF RFC2473: “Generic Packet Tunnelin
16、g in IPv6 Specification“. 2 IETF RFC3775: “Mobility Support in IPv6“. 3 IETF RFC3776: “Using IPsec to Protect Mobile IPv6 Signaling Between Mobile Nodes and Home Agents“. 4 IETF RFC4068: “Fast Handovers for Mobile IPv6“. 3 Abbreviations For the purposes of the present document, the following abbrevi
17、ations apply: AH Authentication Header DES Data Encryption Standard ESP Encapsulated Security Payload IANA Internet Assigned Number Association ICMP Internet Control Message Protocol IETF Internet Engineering Task Force IP Internet Protocol IPsec IP securityIPv4 Internet Protocol version 4 IPv6 Inte
18、rnet Protocol version 6 MAC Message Authentication Code MIPv6 Mobile IPv6 NAR New Address Router PAR Previous Access Router RFC Request For Comments (IETF terminology for a draft standard) ETSI ETSI TS 102 559 V1.1.1 (2006-12) 6 SA Security Association TCP Transport Control Protocol UDP User Datagra
19、m Protocol 4 Requirements Catalogue The mobility requirements related to Internet Protocol version 6 (IPv6) are specified in a number of IETF documents. These documents include requirements for the overall IPv6 mobility architecture 2, the use of the IP Security (IPsec) 3, tunnelling MIPv6 packets 1
20、 and fast handover 4. The present document is a catalogue of all of the normative requirements from these mobility specifications. Each requirement is given a unique identifier (for example, RQ_001_1234) and the following information is included with each: the clause number in the RFC from which the
21、 requirement has been extracted; the type of requirement (Mandatory, Optional or Recommended); the type of device to which the requirement applies (for example, Mobile Node or Home Agent); the actual text from which the requirement was extracted. 4.1 Requirements extracted from RFC3775 Identifier: R
22、Q_001_1001 RFC Clause: 1 Type: Mandatory Applies to: Mobile_Node Requirement: Mobile IPv6 SHALL enable a mobile node to move from one link to another without changing the mobile nodes “home address“. RFC Text: The protocol defined in this document, known as Mobile IPv6,allows a mobile node to move f
23、rom one link to another without changing the mobile nodes “home address“. Packets may be routed to the mobile node using this address regardless of the mobile nodes current point of attachment to the Internet. The mobile node may also continue to communicate with other nodes (stationary or mobile) a
24、fter moving to a new link. Identifier: RQ_001_1002 RFC Clause: 1 Type: Optional Applies to: Mobile_Node Requirement: Packets may be routed to the mobile node using its home address regardless of the mobile nodes current point of attachment to the Internet. RFC Text: The protocol defined in this docu
25、ment, known as Mobile IPv6, allows a mobile node to move from one link to another without changing the mobile nodes “home address“. Packets may be routed to the mobile node using this address regardless of the mobile nodes current point of attachment to the Internet. The mobile node may also continu
26、e to communicate with other nodes (stationary or mobile) after moving to a new link. ETSI ETSI TS 102 559 V1.1.1 (2006-12) 7 Identifier: RQ_001_1003 RFC Clause: 1 Type: Optional Applies to: Mobile_Node Requirement: The mobile node CAN also continue to communicate with other nodes (stationary or mobi
27、le) after moving to a new link RFC Text: The protocol defined in this document, known as Mobile IPv6, allows a mobile node to move from one link to another without changing the mobile nodes “home address“. Packets may be routed to the mobile node using this address regardless of the mobile nodes cur
28、rent point of attachment to the Internet. The mobile node may also continue to communicate with other nodes (stationary or mobile) after moving to a new link. Identifier: RQ_001_1004 RFC Clause: 4 Type: Mandatory Applies to: Mobile_Node Requirement: A mobile node is addressable at its home address,
29、whether it is currently attached to its home link or is away from home RFC Text: A mobile node is always expected to be addressable at its home address, whether it is currently attached to its home link or is away from home. The “home address“ is an IP address assigned to the mobile node within its
30、home subnet prefix on its home link. While a mobile node is at home, packets addressed to its home address are routed to the mobile nodes home link, using conventional Internet routing mechanisms. Identifier: RQ_001_1005 RFC Clause: 4.1 Type: Mandatory Applies to: Mobile_Node Requirement: While a mo
31、bile node is attached to some foreign link away from home, it is also addressable at one or more care-of addresses RFC Text: While a mobile node is attached to some foreign link away from home, it is also addressable at one or more care-of addresses. A care-of address is an IP address associated wit
32、h a mobile node that has the subnet prefix of a particular foreign link. The mobile node can acquire its care-of address through conventional IPv6 mechanisms, such as stateless or stateful auto-configuration. As long as the mobile node stays in this location, packets addressed to this care-of addres
33、s will be routed to the mobile node. The mobile node may also accept packets from several care-of addresses, such as when it is moving but still reachable at the previous link. ETSI ETSI TS 102 559 V1.1.1 (2006-12) 8 Identifier: RQ_001_1006 RFC Clause: 4.1 Type: Optional Applies to: Home_Agent Requi
34、rement: Support bidirectional tunneling using IPv6 encapsulation between the Home Agent and the mobile node RFC Text: There are two possible modes for communications between the mobile node and a correspondent node. The first mode, bidirectional tunneling, does not require Mobile IPv6 support from t
35、he correspondent node and is available even if the mobile node has not registered its current binding with the correspondent node. Packets from the correspondent node are routed to the home agent and then tunneled to the mobile node. Packets to the correspondent node are tunneled from the mobile nod
36、e to the home agent (“reverse tunneled“) and then routed normally from the home network to the correspondent node. In this mode, the home agent uses proxy Neighbor Discovery to intercept any IPv6 packets addressed to the mobile nodes home address (or home addresses) on the home link. Each intercepte
37、d packet is tunneled to the mobile nodes primary care-of address. This tunneling is performed using IPv6 encapsulation 15. Identifier: RQ_001_1006 RFC Clause: 4.1 Type: Optional Applies to: Mobile_Node Requirement: Support bidirectional tunneling using IPv6 encapsulation between the Home Agent and t
38、he mobile node RFC Text: There are two possible modes for communications between the mobile node and a correspondent node. The first mode, bidirectional tunneling, does not require Mobile IPv6 support from the correspondent node and is available even if the mobile node has not registered its current
39、 binding with the correspondent node. Packets from the correspondent node are routed to the home agent and then tunneled to the mobile node. Packets to the correspondent node are tunneled from the mobile node to the home agent (“reverse tunneled“) and then routed normally from the home network to th
40、e correspondent node. In this mode, the home agent uses proxy Neighbor Discovery to intercept any IPv6 packets addressed to the mobile nodes home address (or home addresses) on the home link. Each intercepted packet is tunneled to the mobile nodes primary care-of address. This tunneling is performed
41、 using IPv6 encapsulation 15. Identifier: RQ_001_1007 RFC Clause: 4.1 Type: Optional Applies to: Mobile_Node Requirement: the mobile node MAY register its current binding at the correspondent node RFC Text: The second mode, “route optimization“, requires the mobile node to register its current bindi
42、ng at the correspondent node. Packets from the correspondent node can be routed directly to the care-of address of the mobile node. When sending a packet to any IPv6 destination, the correspondent node checks its cached bindings for an entry for the packets destination address. If a cached binding f
43、or this destination address is found, the node uses a new type of IPv6 routing header 11 (see Section 6.4) to route the packet to the mobile node by way of the care-of address indicated in this binding. ETSI ETSI TS 102 559 V1.1.1 (2006-12) 9 Identifier: RQ_001_1008 RFC Clause: 4.1 Type: Mandatory A
44、pplies to: Mobile_Node Requirement: Mobile Nodes shall support “dynamic home agent address discovery“ RFC Text: Mobile IPv6 also provides support for multiple home agents, and a limited support for the reconfiguration of the home network. In these cases, the mobile node may not know the IP address o
45、f its own home agent, and even the home subnet prefixes may change over time. A mechanism, known as “dynamic home agent address discovery“ allows a mobile node to dynamically discover the IP address of a home agent on its home link, even when the mobile node is away from home. Mobile nodes can also
46、learn new information about home subnet prefixes through the “mobile prefix discovery“ mechanism. These mechanisms are described starting from Section 6.5. Identifier: RQ_001_1009 RFC Clause: 4.1 Type: Optional Applies to: Mobile_Node Requirement: Mobile nodes MAY learn new information about home su
47、bnet prefixes through the “mobile prefix discovery“ mechanism RFC Text: Mobile IPv6 also provides support for multiple home agents, and a limited support for the reconfiguration of the home network. In these cases, the mobile node may not know the IP address of its own home agent, and even the home
48、subnet prefixes may change over time. A mechanism, known as “dynamic home agent address discovery“ allows a mobile node to dynamically discover the IP address of a home agent on its home link, even when the mobile node is away from home. Mobile nodes can also learn new information about home subnet
49、prefixes through the “mobile prefix discovery“ mechanism. These mechanisms are described starting from Section 6.5. Identifier: RQ_001_1010 RFC Clause: 4.6 Type: Mandatory Applies to: Mobile_Node Requirement: home addresses MUST be unicast routable addresses RFC Text: This specification requires that home and care-of addresses MUST be unicast routable addresses. Site-local addresses may be usable on networks that are not connected to the Internet, but this specification does not define when such usage is safe and when i
