1、 International Telecommunication Union ITU-T Y.2902TELECOMMUNICATION STANDARDIZATION SECTOR OF ITU (11/2008) SERIES Y: GLOBAL INFORMATION INFRASTRUCTURE, INTERNET PROTOCOL ASPECTS AND NEXT-GENERATION NETWORKS Next Generation Networks Carrier grade open environment Carrier grade open environment comp
2、onents Recommendation ITU-T Y.2902 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 Y.300Y.399 Interfaces and
3、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, network capabilities and resou
4、rce 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 IPTV over NGN Y.1900Y.1999 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 Future networks Y.2600Y.2699 Security Y.2700Y.2799 Generalized mobility Y.2800Y.2899 Carrier grade open environment Y.2900Y.2999 For further details, please refer to the list of ITU-T Recommendations. Rec. ITU-T Y.290
7、2 (11/2008) i Recommendation ITU-T Y.2902 Carrier grade open environment components Summary Recommendation ITU-T Y.2902 describes carrier grade open environment (CGOE) components, assigned to specific categories of the CGOE reference model, which may be used in commercial off-the-shelf components, s
8、uitable for implementation in next generation networks (NGNs). The characteristics of each individual CGOE component are presented in the following new annexes: Annex A: The Diameter client CGOE component. Annex B: The Diameter server CGOE component. Annex C: The FTP client CGOE component. Annex D:
9、The FTP server CGOE component. Source This edition of Recommendation ITU-T Y.2902 includes the amendments approved on 29 June 2008 by ITU-T Study Group 13 (2005-2008) and the amendments approved on 13 November 2008 by ITU-T Study Group 13 (2009-2012) under Recommendation ITU-T A.8 procedures. ii Rec
10、. ITU-T Y.2902 (11/2008) FOREWORD The International Telecommunication Union (ITU) is the United Nations specialized agency in the field of telecommunications, information and communication technologies (ICTs). The ITU Telecommunication Standardization Sector (ITU-T) is a permanent organ of ITU. ITU-
11、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 Telecommunication Standardization Assembly (WTSA), which meets every four years, establishes the topics for stud
12、y 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 of information technology which fall within ITU-Ts purview, the necessary standards are prepared on a c
13、ollaborative 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 operating agency. Compliance with this Recommendation is voluntary. However, the Recommendation may contain c
14、ertain 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 some other obligatory language such as “must“ and the negative equivalents are used to express requir
15、ements. 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 or implementation of this Recommendation may involve the use of a claimed Intellectual Property Right
16、. 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 development process. As of the date of approval of this Recommendation, ITU had received notice of intellectual
17、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 strongly urged to consult the TSB patent database at http:/www.itu.int/ITU-T/ipr/. ITU 2009 All rights rese
18、rved. No part of this publication may be reproduced, by any means whatsoever, without the prior written permission of ITU. Rec. ITU-T Y.2902 (11/2008) iii CONTENTS Page 1 Scope 1 2 References. 1 3 Definitions 2 3.1 Terms defined elsewhere 2 3.2 Terms defined in this Recommendation. 3 4 Abbreviations
19、 and acronyms 4 5 Conventions 4 5.1 Terms 4 5.2 CGOE component diagrams. 5 6 CGOE components . 7 7 CGOE framework. 8 8 Security considerations. 10 Annex A The Diameter client CGOE component 11 A.1 Scope 11 A.2 References 11 A.3 Definitions 11 A.4 Abbreviations and acronyms 11 A.5 Conventions 11 A.6
20、The Diameter client CGOE component . 11 A.7 Security. 15 Annex B The Diameter server CGOE component 16 B.1 Scope 16 B.2 References 16 B.3 Definitions 16 B.4 Abbreviations and acronyms 16 B.5 Conventions 16 B.6 The Diameter server CGOE component. 16 B.7 Security. 20 Annex C The FTP client CGOE compon
21、ent. 21 C.1 Scope 21 C.2 References 21 C.3 Definitions 21 C.4 Abbreviations . 21 C.5 Conventions 21 C.6 The FTP client CGOE component . 21 C.7 Security. 24 iv Rec. ITU-T Y.2902 (11/2008) Page Annex D The FTP server CGOE component . 25 D.1 Scope 25 D.2 References 25 D.3 Definitions 25 D.4 Abbreviatio
22、ns . 25 D.5 Conventions 25 D.6 The FTP server CGOE component. 25 D.7 Security. 28 Bibliography. 29 Rec. ITU-T Y.2902 (11/2008) 1 Recommendation ITU-T Y.2902 Carrier grade open environment components 1 Scope This Recommendation provides a set of carrier grade open environment (CGOE) components, each
23、of which can be related to a CGOE category identified in the CGOE model that is defined in ITU-T Y.2901. These CGOE components are intended for use by vendors to assist them in developing commercial off-the-shelf (COTS) components. It is recognized that CGOE components will continue to be identified
24、 on a going forward basis and annexes will be added to capture these additions. Additionally, to ensure that a consistent approach is used in the generation of future annexes, a framework for the specification of new CGOE components is provided. 2 References The following ITU-T Recommendations and o
25、ther references contain provisions which, through 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 encourag
26、ed to investigate the possibility of applying 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 docume
27、nt, the status of a Recommendation. ITU-T Y.2901 Recommendation ITU-T Y.2901 (2006), The carrier grade open environment reference model. IETF RFC 854 IETF RFC 854 (1983), Telnet Protocol Specification. IETF RFC 855 IETF RFC 855 (1983), Telnet Option Specifications. IETF RFC 959 IETF RFC 959 (1985),
28、File Transfer Protocol (FTP). IETF RFC 2228 IETF RFC 2228 (1997), FTP Security Extensions. IETF RFC 2246 IETF RFC 2246 (1999), The TLS Protocol Version 1.0. IETF RFC 2401 IETF RFC 2401 (1998), Security Architecture for the Internet Protocol. IETF RFC 2640 IETF RFC 2640 (1999), Internationalization o
29、f the File Transfer Protocol. IETF RFC 2773 IETF RFC 2773 (2000), Encryption using KEA and SKIPJACK. IETF RFC 3659 IETF RFC 3659 (2007), Extensions to FTP. IETF RFC 3588 IETF RFC 3588 (2003), Diameter Base Protocol. 2 Rec. ITU-T Y.2902 (11/2008) IETF RFC 4301 IETF RFC 4301 (2005), Security Architect
30、ure for the Internet Protocol. IETF RFC 4346 IETF RFC 4346 (2006), The Transport Layer Security (TLS) Protocol Version 1.1. IETF RFC 4960 IETF RFC 4960 (2007), Stream Control Transmission Protocol. 3 Definitions 3.1 Terms defined elsewhere This Recommendation uses the following terms defined elsewhe
31、re: 3.1.1 agent b-ITU-T Q.1290: An entity acting on behalf of another. NOTE In client server systems, an agent is the part of the system that performs information preparation and exchange on behalf of a client or server application 3.1.2 application ITU-T Y.2901: An application is a piece of softwar
32、e answering a set of users requirements using telecommunication network services via an IT system. 3.1.3 carrier grade ITU-T Y.2901: Colloquially, a “carrier grade“ implementation of a solution, building block, or a COTS component exhibits particular qualities beyond regular information technology (
33、IT) reliability, availability, serviceability and manageability (RASM) features enabling its mission-critical use in a service providers offering. NOTE COTS component can be called “carrier grade“ with respect to a particular building block if it meets all of the necessary and sufficient non-fuction
34、al requirements of a COTS category for such a building block. 3.1.4 CGOE category ITU-T Y.2901: A unit of description of the CGOE reference model. It comprises one or more CGOE components. NOTE This method of abstraction keeps the size of the framework manageable and understandable. It avoids being
35、too specific or leaning towards the needs of a certain building block. For example, the alarm management category consists of several components, e.g., alarm generation and alarm clearance. 3.1.5 CGOE component ITU-T Y.2901: A CGOE component is an abstract description of technical tasks, interfaces
36、and properties. 3.1.6 CGOE reference model ITU-T Y.2901: A model that organizes the CGOE categories. NOTE 1 Each category is intended to be independent in the sense that it does not require the existence of the categories above it; however, to produce carrier grade functionality, functions may be ne
37、eded from more than one category. NOTE 2 Multiple categories are logically grouped and referred to as the server hardware and the operating platform. 3.1.7 COTS component ITU-T Y.2901: A hardware or a software component instantiation of one or more CGOE components. NOTE 1 Existing or new components
38、may instantiate CGOE components. NOTE 2 The following are examples of components: database system, operating system and management middleware. 3.1.8 component instance ITU-T Y.2901: A component instance is a specific representation of a component, which satisfies the specific needs of building a spe
39、cific building block. NOTE Technology providers develop component instances. During the engineering process within the solution providers, instances are chosen according to the requirements and integrated to eventually stage the entire building block. Examples of component instances: Linux, manageme
40、nt middleware for Q3-access. Rec. ITU-T Y.2902 (11/2008) 3 3.1.9 Diameter ITU-T Y.2901: An IETF protocol that may be used to provide an authentication, authorization and accounting (AAA) framework for applications. 3.1.10 framework ITU-T Y.2901: A framework is an environment that provides a partial
41、solution, usually automating a particularly tedious or difficult part of an application project. 3.1.11 functional requirements ITU-T Y.2901: The set of interfaces, capabilities and features, developed with respect to a service architecture associated with a building block. 3.1.12 middleware ITU-T Y
42、.2901: The mediating entity between two information elements. Such an element can be, for example, an application, infrastructure component or another mediating entity. 3.1.13 non-functional requirements ITU-T Y.2901: A list of features that a building block must provide in order to ensure certain b
43、ehaviour within the service architecture. NOTE This list mostly represents requirements to allow for smooth operations and lifecycle management. 3.2 Terms defined in this Recommendation This Recommendation defines the following terms: 3.2.1 Diameter agent: A Diameter agent is a Diameter component th
44、at provides either relay, proxy, redirect or translation services. 3.2.2 Diameter client: A Diameter client is a device at the edge of the network that performs access control. 3.2.3 Diameter peer: A Diameter peer is a Diameter component to which a given Diameter component has a direct transport con
45、nection. 3.2.4 Diameter server: A Diameter server handles authentication, authorization and accounting requests. NOTE A Diameter server shall support Diameter applications in addition to the base protocol. 3.2.5 non-functional property: A property that does not relate to the function performed by a
46、device or component, e.g., scalability and availability. 3.2.6 proxy: A system authorized to work on behalf of another system including responding to protocol requests. 3.2.7 proxy agent: An agent that acts as a proxy. NOTE In addition to forwarding requests and responses, proxy agents may make poli
47、cy decisions relating to resource usage and provisioning. This would typically be accomplished by tracking the state of network access server devices. While proxies typically do not respond to client requests prior to receiving a response from the server, they may originate reject messages in cases
48、where policies are violated. As a result, proxies need to understand the semantics of the messages passing through them, and may not support all Diameter applications. 3.2.8 relay agent: An agent that performs a relay function. NOTE Relay agents forward requests and responses based on routing-relate
49、d attribute value pairs (AVPs) and realm routing table entries. Relays do not make policy decisions and thus, they do not examine or alter non-routing AVPs. Consequently relay agents never originate messages, do not need to understand the semantics of messages or non-routing AVPs, and are expected to be capable of handling all Diameter application or message types. As relays make decisions based solely on information in routing AVPs and realm forwarding tables, t
