1、 International Telecommunication Union ITU-T Y.2015TELECOMMUNICATION STANDARDIZATION SECTOR OF ITU (01/2009) SERIES Y: GLOBAL INFORMATION INFRASTRUCTURE, INTERNET PROTOCOL ASPECTS AND NEXT-GENERATION NETWORKS Next Generation Networks Frameworks and functional architecture models General requirements
2、 for ID/locator separation in NGN Recommendation ITU-T Y.2015 ITU-T Y-SERIES RECOMMENDATIONS GLOBAL INFORMATION INFRASTRUCTURE, INTERNET PROTOCOL ASPECTS AND NEXT-GENERATION NETWORKS GLOBAL INFORMATION INFRASTRUCTURE General Y.100Y.199 Services, applications and middleware Y.200Y.299 Network aspects
3、 Y.300Y.399 Interfaces and protocols Y.400Y.499 Numbering, addressing and naming Y.500Y.599 Operation, administration and maintenance Y.600Y.699 Security Y.700Y.799 Performances Y.800Y.899 INTERNET PROTOCOL ASPECTS General Y.1000Y.1099 Services and applications Y.1100Y.1199 Architecture, access, net
4、work capabilities and resource management Y.1200Y.1299 Transport Y.1300Y.1399 Interworking Y.1400Y.1499 Quality of service and network performance Y.1500Y.1599 Signalling Y.1600Y.1699 Operation, administration and maintenance Y.1700Y.1799 Charging Y.1800Y.1899 NEXT GENERATION NETWORKS Frameworks and
5、 functional architecture models Y.2000Y.2099 Quality of Service and performance Y.2100Y.2199 Service aspects: Service capabilities and service architecture Y.2200Y.2249 Service aspects: Interoperability of services and networks in NGN Y.2250Y.2299 Numbering, naming and addressing Y.2300Y.2399 Networ
6、k management Y.2400Y.2499 Network control architectures and protocols Y.2500Y.2599 Security Y.2700Y.2799 Generalized mobility Y.2800Y.2899 For further details, please refer to the list of ITU-T Recommendations. Rec. ITU-T Y.2015 (01/2009) i Recommendation ITU-T Y.2015 General requirements for ID/loc
7、ator separation in NGN Summary Recommendation ITU-T Y.2015 begins with showing the limitations of the conventional IP architecture, which uses IP addresses as both node identifiers (IDs) and locators, on supporting mobility, multi-homing, fast endpoint renumbering, traffic engineering, and scalable
8、routing. It then shows that ID/locator separation, i.e., the use of distinct sets of values as node IDs and locators, helps to overcome these limitations. This Recommendation provides general requirements for introducing ID/locator separation in NGN. Source Recommendation ITU-T Y.2015 was approved o
9、n 23 January 2009 by ITU-T Study Group 13 (2009-2012) under Recommendation ITU-T A.8 procedure. ii Rec. ITU-T Y.2015 (01/2009) FOREWORD The International Telecommunication Union (ITU) is the United Nations specialized agency in the field of telecommunications, information and communication technolog
10、ies (ICTs). The ITU Telecommunication Standardization Sector (ITU-T) is a permanent organ of ITU. ITU-T is responsible for studying technical, operating and tariff questions and issuing Recommendations on them with a view to standardizing telecommunications on a worldwide basis. The World Telecommun
11、ication Standardization Assembly (WTSA), which meets every four years, establishes the topics for study by the ITU-T study groups which, in turn, produce Recommendations on these topics. The approval of ITU-T Recommendations is covered by the procedure laid down in WTSA Resolution 1. In some areas o
12、f information technology which fall within ITU-Ts purview, the necessary standards are prepared on a collaborative basis with ISO and IEC. NOTE In this Recommendation, the expression “Administration“ is used for conciseness to indicate both a telecommunication administration and a recognized operati
13、ng agency. Compliance with this Recommendation is voluntary. However, the Recommendation may contain certain mandatory provisions (to ensure e.g. interoperability or applicability) and compliance with the Recommendation is achieved when all of these mandatory provisions are met. The words “shall“ or
14、 some other obligatory language such as “must“ and the negative equivalents are used to express requirements. The use of such words does not suggest that compliance with the Recommendation is required of any party. INTELLECTUAL PROPERTY RIGHTS ITU draws attention to the possibility that the practice
15、 or implementation of this Recommendation may involve the use of a claimed Intellectual Property Right. ITU takes no position concerning the evidence, validity or applicability of claimed Intellectual Property Rights, whether asserted by ITU members or others outside of the Recommendation developmen
16、t process. As of the date of approval of this Recommendation, ITU had not received notice of intellectual property, protected by patents, which may be required to implement this Recommendation. However, implementers are cautioned that this may not represent the latest information and are therefore s
17、trongly urged to consult the TSB patent database at http:/www.itu.int/ITU-T/ipr/. ITU 2009 All rights reserved. No part of this publication may be reproduced, by any means whatsoever, without the prior written permission of ITU. Rec. ITU-T Y.2015 (01/2009) iii CONTENTS Page 1 Scope 1 2 References. 1
18、 3 Definitions 2 3.1 Terms defined elsewhere 2 3.2 Terms defined in this Recommendation. 2 4 Abbreviations and acronyms 3 5 General overview of ID and LOC separation. 4 5.1 General environment under IP based network . 4 5.2 General concept of ID/LOC separation 5 6 General requirements for ID/LOC sep
19、aration 7 6.1 Requirements for survivability. 7 6.2 Requirements for node ID persistency . 7 6.3 Requirements for multi-homing . 7 6.4 Requirements for mobility 8 6.5 Requirements for locator renumbering. 8 6.6 Requirements for traffic engineering 8 7 Functional requirements for ID/LOC separation 9
20、7.1 Requirements for node ID 9 7.2 Requirements for LOC . 10 7.3 Basic functionalities . 10 8 General architecture for ID/LOC separation in NGN. 11 8.1 General considerations of ID/LOC separation . 11 8.2 Architectural components. 12 8.3 Architectural requirements . 12 9 Capability from ID/LOC separ
21、ation . 13 10 Security consideration 14 Bibliography. 15 Rec. ITU-T Y.2015 (01/2009) 1 Recommendation ITU-T Y.2015 General requirements for ID/locator separation in NGN 1 Scope This Recommendation begins by showing the limitations of the conventional IP architecture, which uses IP addresses as both
22、node identifiers (IDs) and node locators, for supporting mobility and multi-homing and states how such limitations would be overcome by ID/locator separation, i.e., by using distinct sets of values for node IDs and locators. It then defines general requirements for ID/locator separation to efficient
23、ly support mobility, multi-homing and host renumbering in NGN. Through the ID/locator separation, it is recommended to have network topology-independent node IDs and topology-dependent locators, and maintain a mapping between NGN identifiers, node IDs and locators. It outlines a general architecture
24、 of ID/locator separation in NGN and provides general requirements of the architectural components. It also outlines security requirements of the architecture that are specific to ID/locator separation. 2 References The following ITU-T Recommendations and other references contain provisions which, t
25、hrough reference in this text, constitute provisions of this Recommendation. At the time of publication, the editions indicated were valid. All Recommendations and other references are subject to revision; users of this Recommendation are therefore encouraged to investigate the possibility of applyi
26、ng the most recent edition of the Recommendations and other references listed below. A list of the currently valid ITU-T Recommendations is regularly published. The reference to a document within this Recommendation does not give it, as a stand-alone document, the status of a Recommendation. ITU-T E
27、.164 Recommendation ITU-T E.164 (1997), The international public telecommunication numbering plan. ITU-T H.323 Recommendation ITU-T H.323 (2003), Packet-based multimedia communications systems. ITU-T Q.1706 Recommendation ITU-T Q.1706/Y.2801 (2006), Mobility management requirements for NGN. ITU-T Y.
28、1241 Recommendation ITU-T Y.1241 (2001), Support of IP-based services using IP transfer capabilities. ITU-T Y.2001 Recommendation ITU-T Y.2001 (2004), General overview of NGN. ITU-T Y.2011 Recommendation ITU-T Y.2011 (2004), General principles and general reference model for next generation networks
29、. ITU-T Y.2012 Recommendation ITU-T Y.2012 (2006), Functional requirements and architecture of the NGN release 1. ITU-T Y.2052 Recommendation ITU-T Y.2052 (2008), Framework of multi-homing in IPv6-based NGN. ITU-T Y.2201 Recommendation ITU-T Y.2201 (2007), NGN release 1 requirements. IETF RFC 3261 I
30、ETF RFC 3261 (2002), SIP: Session Initiation Protocol. 2 Rec. ITU-T Y.2015 (01/2009) 3 Definitions 3.1 Terms defined elsewhere This Recommendation uses the following terms defined elsewhere: 3.1.1 access border gateway b-ITU-T Y.2091: A packet gateway between an access network and a core network. 3.
31、1.2 address b-ITU-T Y.2091: An address is the identifier for a specific termination point and is used for routing to this termination point. NOTE This Recommendation only uses the term “address“ in the case where it does not specifically refer to a locator or an identifier. 3.1.3 identifier b-ITU-T
32、Y.2091: An identifier is a series of digits, characters and symbols or any other form of data used to identify subscriber(s), user(s), network element(s), function(s), network entity(ies) providing services/applications, or other entities (e.g., physical or logical objects). Identifiers can be used
33、for registration or authorization. They can be either public to all networks, shared between a limited number of networks or private to a specific network (private IDs are normally not disclosed to third parties). NOTE In this Recommendation, this identifier is referred to as “NGN identifier“. We de
34、fine a new term “Node ID“ that would be used in transport and upper layers in the ID/locator separation architecture. 3.1.4 seamless service ITU-T Q.1706: A service that is implemented such that it will ensure that users will not experience any service disruptions while changing the point of attachm
35、ent. 3.1.5 service continuity ITU-T Q.1706: The ability for a moving object to maintain ongoing service over including current states, such as users network environment and session for a service. 3.1.6 session b-ITU-T Y.2091: A temporary telecommunications relationship among a group of objects in th
36、e service stratum that are assigned to collectively fulfil a task for a period of time. A session has a state that may change during its lifetime. Session-based telecommunications may, but need not be, assisted by intermediaries (see mediated services). Session-based telecommunications can be one-to
37、-one, one-to-many, many-to-one, or many-to-many. 3.2 Terms defined in this Recommendation This Recommendation defines the following terms: 3.2.1 ID/LOC mapping: ID/LOC mapping is an association between a node ID and one or more LOCs. NOTE 1 A single node ID or several node IDs can be associated with
38、 many LOCs associated with a single terminal. The node ID to LOC mapping can have the one-to-one, one-to-many, or many-to-one relationship. NOTE 2 ID/LOC mapping is also called ID/LOC binding. 3.2.2 ID/LOC mapping function: An ID/LOC mapping function gets mapping information from an ID/LOC mapping s
39、torage function and uses the corresponding node ID and/or LOC in packet headers. The ID/LOC mapping function works in a close correlation with the transport user profile associated with the transport control function. NOTE ID/LOC mapping functions can be physically located in an NGN terminal, an acc
40、ess border gateway, or any other NGN components. 3.2.3 ID/LOC mapping storage function: An ID/LOC mapping storage function stores the mapping of NGN identifiers, node IDs and LOCs. This function also updates mapping information, as well as provides mapping information to other functions on request.
41、The mapping storage function can be physically located in an NGN terminal or with other NGN components. 3.2.4 ID/LOC separation: ID/LOC separation is decoupling the semantic of IP address into the semantics of node IDs and LOCs. Distinct namespaces are used for node IDs and LOCs so that they Rec. IT
42、U-T Y.2015 (01/2009) 3 can evolve independently. LOCs are associated with the IP layer whereas node IDs are associated with upper layers in such a way that ongoing communication sessions or services shall not be broken by changing LOCs due to mobility and multi-homing. NOTE In the context of this Re
43、commendation, a completely new namespace for node IDs can optionally be created that would leave the IP address space more or less intact for LOCs, allowing routing technologies to be developed independently of end-host mobility and end-host multi-homing implications. 3.2.5 locator (LOC): A locator
44、is the network layer topological name for an interface or a set of interfaces. LOCs are carried in the IP address fields as packets traverse the network. NOTE IP addresses can gradually become pure LOCs. However, on the contrary, it cannot be said that a LOC is an IP address. An IP address may assoc
45、iate with the IP layer as well as upper layer protocols (such as TCP and HTTP), whereas a LOC will associate with only the IP layer and be used in IP address fields. 3.2.6 node: A node is defined as a connection point that may be a network device, a user terminal or a process where data can be trans
46、mitted, received or forwarded. In general, a node is identified by its NGN identifier by the user, and by its node ID by the protocol stack. 3.2.7 node ID: A node ID is an identifier used at the transport and higher layers to identify the node as well as the endpoint of a communication session. A no
47、de ID is independent of the node location as well as the network to which the node is attached so that the node ID is not required to change even when the node changes its network connectivity by physically moving or simply activating another interface. The node IDs should be used at the transport a
48、nd higher layers for replacing the conventional use of IP addresses at these layers. A node may have more than one node ID in use. NOTE Unless otherwise specified, the term “ID“ used in this Recommendation represents a node ID, not an NGN identifier specified in this or any other Recommendations. 4
49、Abbreviations and acronyms This Recommendation uses the following abbreviations and acronyms: API Application Programming Interface CPN Customer Premises Network DNS Domain Name System FE Functional Entity GERAN GSM EDGE Radio Access Network ID Identifier IP Internet Protocol ISP Internet Service Provider LAN Local Area Network LOC Locator NGN Next Generation Network POA Point of Attachment SIP Session Initiation Protocol TCP Transmission Control Protocol URI Uniform Resource Identifier URL Uniform Resource Locato
