ITU-T Y 1313-2004 Layer 1 Virtual Private Network service and network architectures SERIES Y GLOBAL INFORMATION INFRASTRUCTURE INTERNET PROTOCOL ASPECTS AND NEXT GENERATION NETWORK.pdf

《ITU-T Y 1313-2004 Layer 1 Virtual Private Network service and network architectures SERIES Y GLOBAL INFORMATION INFRASTRUCTURE INTERNET PROTOCOL ASPECTS AND NEXT GENERATION NETWORK.pdf》由会员分享，可在线阅读，更多相关《ITU-T Y 1313-2004 Layer 1 Virtual Private Network service and network architectures SERIES Y GLOBAL INFORMATION INFRASTRUCTURE INTERNET PROTOCOL ASPECTS AND NEXT GENERATION NETWORK.pdf（52页珍藏版）》请在麦多课文档分享上搜索。

1、 INTERNATIONAL TELECOMMUNICATION UNION ITU-T Y.1313TELECOMMUNICATION STANDARDIZATION SECTOR OF ITU (07/2004) SERIES Y: GLOBAL INFORMATION INFRASTRUCTURE, INTERNET PROTOCOL ASPECTS AND NEXT GENERATION NETWORKS Internet protocol aspects Transport Layer 1 Virtual Private Network service and network arc

2、hitectures ITU-T Recommendation Y.1313 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

3、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, network capabilities and r

4、esource 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 functional architectur

5、e 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 Network management Y.2400Y.24

6、99 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. ITU-T Rec. Y.1313 (07/2004) i ITU-T Recommendation Y.1313 Layer 1 Virtual Private Network service and network ar

7、chitectures Summary This Recommendation specifies functions and architectures to support Layer 1 VPN services described in ITU-T Rec. Y.1312, along with examples of detailed architectures. Source ITU-T Recommendation Y.1313 was approved on 22 July 2004 by ITU-T Study Group 13 (2001-2004) under the I

8、TU-T Recommendation A.8 procedure. Keywords Architecture, Function, Layer 1 VPN, Layer 1, Virtual Private Network, VPN. ii ITU-T Rec. Y.1313 (07/2004) FOREWORD The International Telecommunication Union (ITU) is the United Nations specialized agency in the field of telecommunications. The ITU Telecom

9、munication 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 Telecommunication Standardization Ass

10、embly (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 of information technology wh

11、ich 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 operating agency. Compliance with

12、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 some other obligatory lang

13、uage 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 or implementation of this

14、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 development process. As of the date o

15、f approval of this Recommendation, ITU had not received notice of intellectual property, protected by patents, which may be required to implement this Recommendation. However, implementors are cautioned that this may not represent the latest information and are therefore strongly urged to consult th

16、e TSB patent database. ITU 2004 All rights reserved. No part of this publication may be reproduced, by any means whatsoever, without the prior written permission of ITU. ITU-T Rec. Y.1313 (07/2004) iii CONTENTS Page 1 Scope 1 2 References. 1 2.1 Normative references 1 2.2 Informative references 2 3

17、Definitions 2 4 Abbreviations 3 5 Classification of functions 4 6 Service scenarios, service features and required functions 8 6.1 Description of functions with service features . 8 6.2 Examples of service scenarios and required functions. 9 7 Architecture classification 11 7.1 Provider network arch

18、itecture 11 7.2 Customer network architecture. 16 7.3 Management architecture . 17 8 Layer 1 VPN functional architecture concepts. 19 8.1 Architecture constructs. 19 8.2 Resource allocation schemes 20 8.3 Private addressing. 23 9 Layer 1 VPN functional entities architecture . 24 9.1 Membership infor

19、mation maintenance and connectivity policy management 24 9.2 Routing information maintenance and route computation . 25 9.3 Connection control . 26 9.4 Management . 26 10 Examples of functional architecture . 26 10.1 Distributed provider network architecture 26 10.2 Hybrid provider network architect

20、ure 29 10.3 Centralized provider network architecture . 32 11 Implementation examples of functional architecture . 33 11.1 Overview 33 11.2 Distributed provider network architecture 34 11.3 Hybrid provider network architecture 38 11.4 Centralized provider network architecture . 39 12 Security aspect

21、s 39 iv ITU-T Rec. Y.1313 (07/2004) Page Annex A Detailed description of CE and PE 40 A.1 Architecture of CE participating in multiple Layer 1 VPNs (constructs from ITU-T Recs G.805 and G.8080/Y.1304) . 40 A.2 Architecture of PE participating in multiple Layer 1 VPNs (constructs from ITU-T Recs G.80

22、5 and G.8080/Y.1304) . 41 A.3 Architecture of CE and PE in relation with management systems. 41 Appendix I Implementation examples of existing mechanisms for Layer 1 VPN . 42 BIBLIOGRAPHY 43 ITU-T Rec. Y.1313 (07/2004) 1 ITU-T Recommendation Y.1313 Layer 1 Virtual Private Network service and network

23、 architectures 1 Scope This Recommendation describes the functions and architectures required to support the Layer 1 VPN services defined in ITU-T Rec. Y.1312. It provides some of the architecture examples related to the use of dedicated and shared C-Plane and U-Plane resources. The architecture als

24、o provides examples of networks where the functions are distributed or centralized. 2 References The following ITU-T Recommendations and other references contain provisions which, through reference in this text, constitute provisions of this Recommendation. At the time of publication, the editions i

25、ndicated were valid. All Recommendations and other references are subject to revision; users of this Recommendation are therefore encouraged 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-

26、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. 2.1 Normative references ITU-T G.805 ITU-T Recommendation G.805 (2000), Generic functional architecture of transport networks.

27、 ITU-T G.807 ITU-T Recommendation G.807/Y.1302 (2001), Requirements for Automatic Switched Transport Networks (ASTN). ITU-T G.7713.1 ITU-T Recommendation G.7713.1/Y.1704.1 (2003), Distributed Call and Connection Management (DCM) based on PNNI. ITU-T G.7713.2 ITU-T Recommendation G.7713.2/Y.1704.2 (2

28、003), Distributed Call and Connection Management: Signalling mechanism using GMPLS RSVP-TE. ITU-T G.7713.3 ITU-T Recommendation G.7713.3/Y.1704.3 (2003), Distributed Call and Connection Management: Signalling mechanism using GMPLS CR-LDP. ITU-T G.7714.1 ITU-T Recommendation G.7714.1/Y.1705.1 (2003),

29、 Protocol for automatic discovery in SDH and OTN networks. ITU-T G.8080 ITU-T Recommendation G.8080/Y.1304 (2001), Architecture for the Automatically Switched Optical Network (ASON). ITU-T Y.1311 ITU-T Recommendation Y.1311 (2002), Network-based VPNs Generic architecture and service requirements. IT

30、U-T Y.1312 ITU-T Recommendation Y.1312 (2003), Layer 1 Virtual Private Network generic requirements and architecture elements. IETF RFC 1771 IETF RFC 1771 (1995), A Border Gateway Protocol 4 (BGP-4). IETF RFC 2328 IETF RFC 2328 (1998), OSPF version 2. IETF RFC 2748 IETF RFC 2748 (2000), The COPS (Co

31、mmon Open Policy Service) Protocol. 2 ITU-T Rec. Y.1313 (07/2004) IETF RFC 3472 IETF RFC 3472 (2003), Generalized Multi-Protocol Label Switching (GMPLS) Signaling Constraint-based Routed Label Distribution Protocol (CR-LDP) Extensions. IETF RFC 3473 IETF RFC 3473 (2003), Generalized Multi-Protocol L

32、abel Switching (GMPLS) Signaling Resource ReserVation Protocol-Traffic Engineering (RSVP-TE) Extensions. OIF UNI 1.0 OIF Implementation Agreement OIF-UNI01.0 (2001), User Network Interface (UNI) 1.0 Signaling Specification. OIF Signaling E-NNI 1.0 OIF Implementation Agreement OIF-E-NNI-Sig-01.0 (200

33、4), Intra-Carrier E-NNI Signaling Specification. 2.2 Informative references IETF RFC 3474 IETF RFC 3474 (2003), Documentation of IANA assignments for Generalized MultiProtocol Label Switching (GMPLS) Resource Reservation Protocol Traffic Engineering (RSVP-TE) Usage and Extensions for Automatically S

34、witched Optical Network (ASON). IETF RFC 3475 IETF RFC 3475 (2003), Documentation of IANA assignments for Constraint-Based LSP setup using LDP (CR-LDP) Extensions for Automatic Switched Optical Network (ASON). IETF RFC 3476 IETF RFC 3476 (2003), Documentation of IANA Assignments for Label Distributi

35、on Protocol (LDP), Resource ReSerVation Protocol (RSVP), and Resource ReSerVation Protocol-Traffic Engineering (RSVP-TE) Extensions for Optical UNI Signaling. 3 Definitions 3.1 This Recommendation makes use of the following terms defined in the following ITU-T Recommendations: a) L1 VPN (Layer 1 VPN

36、): Refer to ITU-T Rec. Y.1312. b) CE: Refer to ITU-T Rec. Y.1312. c) PE: Refer to ITU-T Rec. Y.1312. d) P: Refer to ITU-T Rec. Y.1312. e) Customer: Refer to ITU-T Rec. Y.1312 f) shared U-plane: Refer to ITU-T Rec. Y.1312. g) dedicated U-plane: Refer to ITU-T Rec. Y.1312. h) shared C-plane: Refer to

37、ITU-T Rec. Y.1312. i) dedicated C-plane: Refer to ITU-T Rec. Y.1312. j) connection: Refer to ITU-T Rec. Y.1312. k) Connection Point (CP): Refer to ITU-T Rec. G.805. l) link: Refer to ITU-T Recs G.805 and Y.1312. m) link connection: Refer to ITU-T Rec. G.805. n) subnetwork: Refer to ITU-T Rec. G.805.

38、 o) trail: Refer to ITU-T Rec. G.805. p) SNP: Refer to ITU-T Rec. G.8080/Y.1304. ITU-T Rec. Y.1313 (07/2004) 3 q) SNPP: Refer to ITU-T Rec. G.8080/Y.1304. r) SNP link connection: Refer to ITU-T Rec. G.8080/Y.1304. s) SNPP link: Refer to ITU-T Rec. G.8080/Y.1304. 3.2 This Recommendation defines the f

39、ollowing terms: 3.2.1 Provider Centralized Controller (PCC): The centralized entity which performs some L1 VPN functions for the provider network. 3.2.2 Customer Centralized Controller (CCC): The centralized entity which performs some L1 VPN functions for the customer network. 3.2.3 provider entity:

40、 The entity which performs some L1 VPN functions for the provider network. The provider entity may be PE/P or PCC, depending on implementation of functions. 3.2.4 customer entity: The entity which performs some L1 VPN functions for the customer network. The customer entity may be CE or CCC, dependin

41、g on implementation of functions. 4 Abbreviations This Recommendation uses the following abbreviations: AAA Authentication, Authorization and Accounting BGP Border Gateway Protocol CCC Customer Centralized Controller CE Customer Edge CNM Customer Network Management COPS Common Open Policy Service CO

42、RBA Common Object Request Broker Architecture CP Connection Point CUG Closed User Group DCN Data Communications Network E-NNI External Network-to-Network Interface EPL Ethernet Private Line FTP File Transfer Protocol GMPLS Generalized Multi-Protocol Label Switching I-NNI Internal Network-to-Network

43、Interface LRM Link Resource Manager NNI Network-Network Interface OAM Operation, Administration and Maintenance OSPF Open Shortest Path First OTN Optical Transport Network P Provider PCC Provider Centralized Controller PDP Policy Decision Point 4 ITU-T Rec. Y.1313 (07/2004) PE Provider Edge PEP Poli

44、cy Enforcement Point SNMP Simple Network Management Protocol SNP Subnetwork Point SNPP Subnetwork Point Pool SPC Soft Permanent Connection TCA Threshold Crossing Alert TL1 Transaction Language 1 TMF TeleManagement Forum UNI User Network Interface VPN Virtual Private Network XML eXtensible Markup Lan

45、guage 5 Classification of functions In order to support service functions, the L1 VPN providing network must perform the following functions, as described in ITU-T Rec. Y.1312. Some of the functions can be optional. ITU-T Rec. Y.1313 (07/2004) 5 Functional Entities in the networkInformation flowFunc

46、tional Entities in the network (not directlycommunicating to customers)CE PE PEPCE Explicit link selection Selection of L1 class of service Per-CE policy and its management Transfer of fault information Transfer of performance information Notification of connection rejection Authentication Dynamic c

47、ontrol of Layer 1 connection Transfer of connectivity information Transfer of resource information Transparent transfer of controlinformation between customer entities Network participation in customer domain routing Distribution of membership availability information Distribution of membership info

48、rmation Basic L1 service features Per-VPN Policy Authorization Accounting Connectivity restrictions Per-CE policy and its management Transfer of fault information Transfer of performance information Notification of connection rejection Authentication Dynamic control of Layer 1 connection Transfer of

49、 connectivity information Transfer of resource information Transparent transfer of control information between customer entities Network participation in customer domain routing Distribution of membership availability information Distribution of membership information Basic L1 service features Membership maintenance Customer domain routing information maintenance Network topology information maintenance Connectivity information maintenance Mapping of class of service to surviva