I n t e r n a t i o n a l T e l e c o m m u n i c a t i o n U n i o n ITU-T TELECOMMUNICATION STANDARDIZATION SECTOR OF ITU G.7712/Y.1703 Amendment 2 (02/2016) SERIES G: TRANSMISSION SYSTEMS AND MEDIA, DIGITAL SYSTEMS AND NETWORKS Data over Transport Generic aspects Transport network control aspects SERIES Y: GLOBAL INFORMATION INFRASTRUCTURE, INTERNET PROTOCOL ASPECTS AND NEXT-GENERATION NETWORKS, INTERNET OF THINGS AND SMART CITIES Internet protocol aspects Architecture and specification of data communication network Amendment 2 Operation, administration and Recommendation ITU-T G.7712/Y.1703 (2010) Amendment 2
ITU-T G-SERIES RECOMMENDATIONS TRANSMISSION SYSTEMS AND MEDIA, DIGITAL SYSTEMS AND NETWORKS INTERNATIONAL TELEPHONE CONNECTIONS AND CIRCUITS GENERAL CHARACTERISTICS COMMON TO ALL ANALOGUE CARRIER- TRANSMISSION SYSTEMS INDIVIDUAL CHARACTERISTICS OF INTERNATIONAL CARRIER TELEPHONE SYSTEMS ON METALLIC LINES GENERAL CHARACTERISTICS OF INTERNATIONAL CARRIER TELEPHONE SYSTEMS ON RADIO-RELAY OR SATELLITE LINKS AND INTERCONNECTION WITH METALLIC LINES COORDINATION OF RADIOTELEPHONY AND LINE TELEPHONY TRANSMISSION MEDIA AND OPTICAL SYSTEMS CHARACTERISTICS DIGITAL TERMINAL EQUIPMENTS DIGITAL NETWORKS DIGITAL SECTIONS AND DIGITAL LINE SYSTEM MULTIMEDIA QUALITY OF SERVICE AND PERFORMANCE GENERIC AND USER- RELATED ASPECTS TRANSMISSION MEDIA CHARACTERISTICS DATA OVER TRANSPORT GENERIC ASPECTS General Transport network control aspects PACKET OVER TRANSPORT ASPECTS ACCESS NETWORKS G.100 G.199 G.200 G.299 G.300 G.399 G.400 G.449 G.450 G.499 G.600 G.699 G.700 G.799 G.800 G.899 G.900 G.999 G.1000 G.1999 G.6000 G.6999 G.7000 G.7999 G.7000 G.7099 G.7700 G.7799 G.8000 G.8999 G.9000 G.9999 For further details, please refer to the list of ITU-T Recommendations.
Recommendation ITU-T G.7712/Y.1703 Architecture and specification of data communication network Amendment 2 Summary Amendment 2 to Recommendation ITU-T G.7712/Y.1703 contains the updates to Recommendation ITU-T G.7712/Y.1703 (2010) to provide the specification of the out-of-band (OOB) OCh overhead (OCh-O) status report protocol (SRP). History Edition Recommendation Approval Study Group Unique ID * 1.0 ITU-T G.7712/Y.1703 2001-11-29 15 11.1002/1000/5637 2.0 ITU-T G.7712/Y.1703 2003-03-16 15 11.1002/1000/6287 3.0 ITU-T G.7712/Y.1703 2008-06-22 15 11.1002/1000/9390 4.0 ITU-T G.7712/Y.1703 2010-09-06 15 11.1002/1000/10895 4.1 ITU-T G.7712/Y.1703 (2010) Amd. 1 2013-10-07 15 11.1002/1000/12000 4.2 ITU-T G.7712/Y.1703 (2010) Amd. 2 2016-02-26 15 11.1002/1000/12553 * To access the Recommendation, type the URL http://handle.itu.int/ in the address field of your web browser, followed by the Recommendation's unique ID. For example, http://handle.itu.int/11.1002/1000/11 830-en. Rec. ITU-T G.7712/Y.1703 (2010)/Amd.2 (02/2016) i
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-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 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 which fall within ITU-T's 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 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 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 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 development process. As of the date of approval of this Recommendation, ITU had 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 strongly urged to consult the TSB patent database at http://www.itu.int/itu-t/ipr/. ITU 2016 All rights reserved. No part of this publication may be reproduced, by any means whatsoever, without the prior written permission of ITU. ii Rec. ITU-T G.7712/Y.1703 (2010)/Amd.2 (02/2016)
Table of Contents Page 1) Scope... 1 2) Updates to Recommendation ITU-T G.7712/Y.1703... 1 2.1) Clause 2, References... 1 2.2) Clause 4, Abbreviations... 1 2.3) Clause 6.3.1... 1 2.4) Add a new Annex D... 1 Annex D OOB OCh-O protocol specification... 1 D.1 Overview... 1 D.2 PDU format... 2 D.3 OCh_O communication channel adaptation function (OCC/OCh-O_A)... 6 D.4 OCh_O communication channel termination function (OCC_TT)... 6 Rec. ITU-T G.7712/Y.1703 (2010)/Amd.2 (02/2016) iii
Recommendation ITU-T G.7712/Y.1703 Architecture and specification of data communication network Amendment 2 1) Scope This amendment contains the updates to Recommendation ITU-T G.7712/Y.1703 (2010) to provide the specification of the out-of-band (OOB) OCh overhead (OCh-O) status report protocol (SRP). 2) Updates to Recommendation ITU-T G.7712/Y.1703 2.1) Clause 2, References Add the following reference to clause 2: [IETF RFC 4204] 2.2) Clause 4, Abbreviations IETF RFC 4204 (2005), Link Management Protocol (LMP). Add the following abbreviations, inserted alphabetically, to clause 4: LMP OOB OPS UDP Link Management Protocol Out-Of-Band Optical Physical Section User Datagram Protocol 2.3) Clause 6.3.1 Update to clause 6.3.1, "OCh overhead communication application" Replace the note: NOTE The specification for how the primitive and information elements described in Amendment 2 of [ITU-T G.709] are carried across an OCN is for further study. with the following text: The protocol used for OCh overhead communication is defined in Annex D. 2.4) Add a new Annex D Insert the following text as a new Annex D: D.1 Overview Annex D OOB OCh-O protocol specification (This annex forms an integral part of this Recommendation.) The OOB OCh-O protocol supports an OCC carrying the status of OCh connections and signals over an OCN to systems that do not have direct access to the OSC. For deployment flexibility, the OCh-O Rec. ITU-T G.7712/Y.1703 (2010)/Amd.2 (02/2016) 1
protocol is defined independent of the specific DCN protocol in use (e.g., IPv4, IPv6). The details of how to adapt the characteristic information (CI) of this protocol to an IPv4-based DCN are provided at the end of the protocol definition. The OOB OCh-O protocol requires configuration of a protocol adjacency between two OCh-O connection points (OCh-O CP) located on the associated network equipment being connected by one or more optical physical section (OPS). Prior to both ends being configured, the status reporting behaviours driven by the protocol will not be operational. The adjacency is identified by using OPS as well as OCh identifiers and is carried by the DCN network. The status messages carried by the OOB OCh-O protocol provide unidirectional state information for one or more OCh connections and signals. The messages include identifiers of the OPS trail and one or more OCh-P link connections carried by that trail that identify the OCh-P link connections for which status is being reported. The receiving NE correlates the received status message with a local OCh-P CP utilizing the configured OPS adjacency. D.2 PDU format The OOB OCh-O protocol is derived from the IETF's link management protocol (LMP) [IETF RFC 4204]. LMP uses a common format for the PDUs of all protocol messages as shown in Figure D.1. Vers (Reserved) Flags Msg Type Msg Length (Reserved) : Payload TLVs : Figure D.1 OOB OCh-O protocol message PDU format Sub-protocols are used in the design of the OOB OCh-O protocol. The value in the Msg Type field indicates which of the sub-protocols a PDU belongs to. TLV structure is used for the base PDU and payload TLV structures; in all cases the units of length are octets. The Msg Length provides the overall length of the PDU. Payload TLVs follow the format shown in Figure D.2. C-Type Class Length : Value : Figure D.2 OOB OCh-O protocol payload TLV format The C-Type and Class fields are defined by each sub-protocol. The Length field provides the overall length of the TLV inclusive of the C-Type, Class and Length fields. The OOB OCh-O protocol shall exchange Hello PDUs and Status Reporting PDUs. 2 Rec. ITU-T G.7712/Y.1703 (2010)/Amd.2 (02/2016)
D.2.1 Hello sub-protocol The Hello sub-protocol uses a message type of 4. Inside the message are Hello sequence and validity TLVs. The format of these TLVs is as follows: D.2.1.1 Hello sequence TLV The C-type is 7, Class is 1 and Length is 12. The Value field is formatted as shown in Figure D.3. TxSeqNum RcvSeqNum Figure D.3 OOB OCh-O protocol Hello sequence format The TxSeqNum is the sequence number of the Status Reporting message last transmitted by this adjacency endpoint. The RcvSeqNum is the sequence number of the Status Reporting message last received by this adjacency endpoint. Initially the RcvSeqNum=0 and the TxSeqNum=1. The RcvSeqNum will be replaced with the TxSeqNum received from the peer when the first Hello message is received. If a Hello message is received with a Hello sequence TLV containing a RcvSeqNum equal to 0, it is an indication that the peer endpoint has restarted and requires state information be sent for all OCh associated with this adjacency. The TxSeqNum may eventually exceed 2^32. When this occurs, the TxSeqNum will wrap to the value of 1. D.2.1.2 Hello validity TLV The C-type is 240, Class is 1 and Length is 8. The value is formatted as shown in Figure D.4. Validity Period Figure D.4 OOB OCh-O protocol Hello validity format The Validity Period field describes the amount of time (in ms) before another Hello must be received for the adjacency to be considered up. A transmitter should send subsequent Hello messages prior to the expiration of the validity period. The receiver of the Hello must update the expiration of the adjacency health timer upon receipt of a Hello PDU. If the validity period expires, the adjacency shall raise an alarm to the EMF. This alarm clears when the Hello protocol receives a Hello message from the peer starting a new validity period. D.2.2 Status Reporting sub-protocol Status Reporting PDUs are issued for one or more OCh connections and signals as state changes occur or initial state requests are received. These PDUs use message type 17. The PDUs each contain a Message ID TLV, an OPS Trail Identification TLV, along with one or more identifiers for one or more OCh-P Link Connections and one OCh Status TLVs. It is possible for multiple OCh-P link connections that change state at the same time to be reported in a single Status Reporting PDU. In this case, all OCh-Ps identified in the PDU will have the same status. Rec. ITU-T G.7712/Y.1703 (2010)/Amd.2 (02/2016) 3
The format of these TLVs is as follows: D.2.2.1 Message ID TLV The Message ID TLV contains the TxSeqNum for this specific Status Reporting PDU. The Class number is 5 and the C-Type 1. The TLV Length is 8. The format is shown in Figure D.5. Message_ID D.2.2.2 Figure D.5 OOB OCh status reporting Message ID format OPS Trail Identification TLV The namespace used for OPS Trail Identification is the TCP_ID namespace used by ITU-T G.7714 neighbour discovery. Control plane names are not used as it is not guaranteed that a control plane is active on this link. An OPS Trail Identification TLV has a C-type of 241 and Length of 16. The class uses the Format ID defined for each TCP-ID format in [ITU-T G.7714.1]. The Value field is formatted as shown in Figure D.6, Figure D.7 and Figure D.8 for TCP-ID Name, DCN Address format and DCN Name formats respectively. (Reserved) TCP Name.. TCP Name.. TCP Name Figure D.6 OOB OPS Trail and OCh-P Link Connection ID TCP-ID Name format (Class=1) (Reserved) DCN Context ID DCN Address Local TCP-ID Figure D.7 OOB OPS Trail and OCh-P Link Connection ID DCN Address format (Class=2) 4 Rec. ITU-T G.7712/Y.1703 (2010)/Amd.2 (02/2016)
(Reserved) DCN Name.. DCN Name Local TCP-ID Name D.2.2.3 Figure D.8 OOB OPS Trail and OCh-P Link Connection ID DCN Name format (Class=3) OCh-P Link Connection ID TLV The OCh-P Link Connection ID TLV identifies an OCh-P instance carried by the OPS trail. The namespace used for the OCh-P Link Connection ID is the TCP-ID namespace used by ITU-T G.7714.1 neighbour discovery. Control plane names are not used as it is not guaranteed that a control plane is active on this link. The format for the OCh-P Link Connection ID TLV is the same as the format for the OPS Trail Identification TLV. An OCh-P Link Connection ID TLV has a C-type of 244 and Length of 16. The class uses the Format ID defined for each TCP-ID format in [ITU-T G.7714.1]. The Value field for the OCh-P Link Connection ID TLV is formatted as shown in Figure D.6, Figure D.7 and Figure D.8 for TCP-ID Name, DCN Address and DCN Name format respectively. Multiple Link Connection ID TLVs may be carried in the same status update message. In this case, all OCh-P link connections in the message will have the same status. D.2.2.4 OCh Status TLV The OCh Status TLV is a bit vector providing status indication for one or more OCh-P link connections identified in the Status Reporting PDU. The Class number is 242 and the C-Type is 1. The TLV Length is 8. The format is shown in Figure D.9. Channel Status Flags Figure D-9 OCh Status TLV format The flags in the Channel Status Flags field are defined as follows: 0x0000.0001: FDI-P 0x0000.0002: FDI-O 0x0000.0004: OCI All remaining flags are reserved. Reserved flags are transmitted as zero (0) and ignored on reception. D.2.3 Protocol adaptation to IPv4 DCN The OOB OCh-O protocol is carried over IPv4 networks using unicast user datagram protocol (UDP) messages. The OOB OCh-O PDUs are carried as payload within adaptation frames with one PDU in each frame. The adaptation uses the format in Figure D.10. Rec. ITU-T G.7712/Y.1703 (2010)/Amd.2 (02/2016) 5
ITU-T Enterprise Identifier (xxxx) ITU-T Protocol Number (yyyy) : Payload : Figure D.10 OOB OCh-O protocol UDP/IPv4 frame format While the OOB OCh-O protocol does not have a byte-count limit on a PDU, they are to be carried within a single IPv4 PDU to the destination to avoid problems with complete message loss due to message fragmentation and loss of fragments. For this reason, the IPv4 DoNotFragment bit should be set and PDUs should be less than 1500 bytes (inclusive of IPv4, UDP and frame header overheads). D.3 OCh_O communication channel adaptation function (OCC/OCh-O_A) The OCC/OCh-O_A function aggregates/de-aggregates OCh_CI_OH. The specification of this function is for further study. D.4 OCh_O communication channel termination function (OCC_TT) The OCC_TT function is responsible for the end-to-end supervision of the OCC trail. The specification of this function is for further study. 6 Rec. ITU-T G.7712/Y.1703 (2010)/Amd.2 (02/2016)
ITU-T Y-SERIES RECOMMENDATIONS GLOBAL INFORMATION INFRASTRUCTURE, INTERNET PROTOCOL ASPECTS AND NEXT- GENERATION NETWORKS, INTERNET OF THINGS AND SMART CITIES GLOBAL INFORMATION INFRASTRUCTURE General Services, applications and middleware Network aspects Interfaces and protocols Numbering, addressing and naming Operation, administration and maintenance Security Performances INTERNET PROTOCOL ASPECTS General Services and applications Architecture, access, network capabilities and resource management Transport Interworking Quality of service and network performance Signalling Operation, administration and maintenance Charging IPTV over NGN NEXT GENERATION NETWORKS Frameworks and functional architecture models Quality of Service and performance Service aspects: Service capabilities and service architecture Service aspects: Interoperability of services and networks in NGN Enhancements to NGN Network management Network control architectures and protocols Packet-based Networks Security Generalized mobility Carrier grade open environment FUTURE NETWORKS CLOUD COMPUTING INTERNET OF THINGS AND SMART CITIES AND COMMUNITIES General Definitions and terminologies Requirements and use cases Infrastructure, connectivity and networks Frameworks, architectures and protocols Services, applications, computation and data processing Management, control and performance Identification and security Y.100 Y.199 Y.200 Y.299 Y.300 Y.399 Y.400 Y.499 Y.500 Y.599 Y.600 Y.699 Y.700 Y.799 Y.800 Y.899 Y.1000 Y.1099 Y.1100 Y.1199 Y.1200 Y.1299 Y.1300 Y.1399 Y.1400 Y.1499 Y.1500 Y.1599 Y.1600 Y.1699 Y.1700 Y.1799 Y.1800 Y.1899 Y.1900 Y.1999 Y.2000 Y.2099 Y.2100 Y.2199 Y.2200 Y.2249 Y.2250 Y.2299 Y.2300 Y.2399 Y.2400 Y.2499 Y.2500 Y.2599 Y.2600 Y.2699 Y.2700 Y.2799 Y.2800 Y.2899 Y.2900 Y.2999 Y.3000 Y.3499 Y.3500 Y.3999 Y.4000 Y.4049 Y.4050 Y.4099 Y.4100 Y.4249 Y.4250 Y.4399 Y.4400 Y.4549 Y.4550 Y.4699 Y.4700 Y.4799 Y.4800 Y.4899 For further details, please refer to the list of ITU-T Recommendations.
SERIES OF ITU-T RECOMMENDATIONS Series A Series D Series E Series F Series G Series H Series I Series J Series K Series L Series M Series N Series O Series P Series Q Series R Series S Series T Series U Series V Series X Series Y Series Z Organization of the work of ITU-T General tariff principles Overall network operation, telephone service, service operation and human factors Non-telephone telecommunication services Transmission systems and media, digital systems and networks Audiovisual and multimedia systems Integrated services digital network Cable networks and transmission of television, sound programme and other multimedia signals Protection against interference Environment and ICTs, climate change, e-waste, energy efficiency; construction, installation and protection of cables and other elements of outside plant Telecommunication management, including TMN and network maintenance Maintenance: international sound programme and television transmission circuits Specifications of measuring equipment Terminals and subjective and objective assessment methods Switching and signalling Telegraph transmission Telegraph services terminal equipment Terminals for telematic services Telegraph switching Data communication over the telephone network Data networks, open system communications and security Global information infrastructure, Internet protocol aspects, next-generation networks, Internet of Things and smart cities Languages and general software aspects for telecommunication systems Printed in Switzerland Geneva, 2016