Recommendation ITU-T G.7712/Y.1703 (2019) - Amd.1 (02/2022) Architecture and specification of data communication network
Summary
History
FOREWORD
Table of Contents
Amendment 1
1 Scope
2 References
3 Terms and definitions
     3.1 Terms defined elsewhere
3.1.3 Terms defined in [ITU-T G.8080] and [ITU-T G.8081]:
     3.2 Terms defined in this Recommendation
4 Abbreviations and acronyms
5 Conventions
6 DCN applications
     6.1 TMN application
          6.1.1 X management subnetwork architecture
               6.1.1.1 Topology for management subnetwork
          6.1.2 Reliability of MCN
          6.1.3 Security of MCN
          6.1.4 MCN s
     6.2 ASON application
          6.2.1 Topology of CCNSCN
          6.2.2 Reliability of SCNCCN
          6.2.3 Security of CCNSCN
          6.2.4 CCN SCN data communication functions
     6.3 SDN application
          6.3.1 Supported SDN interfaces
          6.3.2 Topology of SDN communications
          6.3.3 Reliability of SDN communications
          6.3.4 Security of SDN communications
     6.4 Other applications requiring communication networks
          6.4.1 OTSiG|OCh non-associated overhead communication application
     6.5 Separation of various applications
7 DCN functional architecture
8 Data communication function requirements
     8.1 L1 Physical layer requirements
     8.2 L2 Data link layer requirement
          8.2.1 SDH ECC (DCC)
               8.2.1.1 Mapping the data-link layer frame into the SDH ECC
               8.2.1.2 SDH ECC data-link layer protocol specification
                    8.2.1.2.1 IP-only interface
                    8.2.1.2.2 OSI-only interface
                    8.2.1.2.3 Dual interface (IP+OSI)
          8.2.2 OTN ECC (GCC)
               8.2.2.1 Mapping the data-link layer frame into the OTN GCC (OTN COMMS channel)
               8.2.2.2 OTN ECC data-link layer protocol specification
                    8.2.2.2.1 IP-only interface
                    8.2.2.2.2 OSI-only interface
                    8.2.2.2.3 Dual interface (IP+OSI)
          8.2.3 MPLS-TP ECC
               8.2.3.1 MPLS-TP SCN
                    8.2.3.1.1 SCN link sharing server layer trail with MPLS-TP user traffic
                    8.2.3.1.2 SCN MPLS-TP SCC as per [IETF RFC 5718]
                    8.2.3.1.3 SCN link utilizing a dedicated MPLS-TP LSP
                    8.2.3.1.4 Separate and independent SCN links
                    8.2.3.1.5 MPLS-TP SCC data-link layer termination function
                         8.2.3.1.5.1 Non-MPLS-TP server layer trail providing an SCN link (SCN link sharing a server layer trail with MPLS-TP user traffic)
                         8.2.3.1.5.2 SCN link utilizing the MPLS-TP SCC as per [IETF RFC 5718]
                         8.2.3.1.5.3 SCN link utilizing a dedicated MPLS-TP LSP
               8.2.3.2 MPLS-TP MCN
                    8.2.3.2.1 Non-MPLS-TP server layer trail providing an MCN link (MCN link sharing a server layer trail with MPLS-TP user traffic)
                    8.2.3.2.2 MCN link utilizing the MPLS-TP MCC as per [IETF RFC 5718]
                    8.2.3.2.3 MCN link utilizing a dedicated MPLS-TP LSP
          8.2.4 EoT ECC
          8.2.5 MTN ECC
               8.2.5.1 CCN link utilizing the MTNS MCC (MTN COMMS channel)
                    8.2.5.1.1 Mapping the data-link layer frame into the MTN ECC
                    8.2.5.1.2 MTN ECC data-link layer protocol specification
               8.2.5.2 CCN link sharing MTNP trail with MTN user traffic
               8.2.5.3 Separate and independent CCN links
     8.3 L3 Network layer requirements
          8.3.1 L3 into L2 encapsulation function
               8.3.1.1 L3 into SDH ECC data-link frame encapsulation function
                    8.3.1.1.1 IP-only interface
                    8.3.1.1.2 OSI-only interface
                    8.3.1.1.3 Dual (IP+OSI) interface
               8.3.1.2 L3 into MPLS-TP SCC data-link frame encapsulation function
               8.3.1.3 L3 into MPLS-TP MCC data-link frame encapsulation function
               8.3.1.4 L3 into EoT MCC data-link frame encapsulation function
               8.3.1.5 L3 into Ethernet frame encapsulation function
          8.3.2 L3 forwarding function
          8.3.3 L3 interworking function
          8.3.4 L3 to L3 encapsulation function
          8.3.5 L3 tunnelling function
          8.3.6 L3 routing function
               8.3.6.1 Integrated IS-IS requirements
                    8.3.6.1.1 Network-layer protocol aware adjacency creation
                    8.3.6.1.2 IS-IS domain-wide IP prefix distribution
                         8.3.6.1.2.1 Configuration prefixes
                         8.3.6.1.2.2 Tagging of propagated prefixes
                              8.3.6.1.2.2.1 Transmission of LS-PDUs with IP reachability TLVs and IP external reachability TLVs
                              8.3.6.1.2.2.2 Reception of LS-PDUs with IP reachability TLVs and IP external reachability TLVs
                              8.3.6.1.2.2.3 Use the up/down bit in Level-2 LS-PDUs
                         8.3.6.1.2.3 Route preference
          8.3.7 L3 IP routing interworking function
          8.3.8 Applications to L3 mapping function
     8.4 Other requirements
          8.4.1 Provisioning requirements
          8.4.2 Security requirements
9 Specific DCN L3|L2|L1 technology requirements
     9.1 Ethernet LAN as L1&L2
     9.2 Ethernet WAN as L1&L2
     9.3 Native MPLS as L3
          9.3.1 MPLS PDU into L2 encapsulation function
               9.3.1.1 "MPLS PDU into Ethernet frame" encapsulation function
          9.3.2 MPLS LSP signalling function
          9.3.3 MPLS LSP forwarding function
          9.3.4 MPLS LSP path computation function
          9.3.5 "Network layer packet into MPLS" encapsulation function
          9.3.6 MPLS packet 1+1 protection function
               9.3.6.1 Associating two LSPs
               9.3.6.2 Sequence identifier format
Annex A  Requirements for three-way handshaking
     A.1 Point-to-point three-way adjacency TLV
     A.2 Adjacency three-way state
Annex B  Requirements for automatic encapsulation
     B.1 Introduction
     B.2 Scope
     B.3 Description of the AE-DCF
          B.3.1 Introduction
          B.3.2 Basic concept
     B.4 Requirements and limitations
          B.4.1 Requirements for OSI-only nodes
          B.4.2 Requirements for IP-capable nodes
          B.4.3 Requirements for automatically encapsulating dual or multilingual nodes
               B.4.3.1 Encapsulation capability TLV
               B.4.3.2 Forwarding process
               B.4.3.3 Receipt process
               B.4.3.4 MTU size and fragmentation requirements
               B.4.3.5 Requirements for AE-DCF with broadcast (LAN) interfaces
                    B.4.3.5.1 Pseudo-node election process
                    B.4.3.5.2 LS-PDU update process
                    B.4.3.5.3 Redirects
                    B.4.3.5.4 Mixing of dual [IETF RFC 1195] only and automatically encapsulating nodes on a LAN
          B.4.4 Requirements for automatically encapsulating split stack nodes
          B.4.5 Use of IP nodes that do not conform to clause 8.3.6.1.1 with the AE-DCF
          B.4.6 Use of dual nodes with no AE-DCF and dual nodes with AE-DCF in the same IS-IS area
          B.4.7 Requirements for Level-1 and Level-2 nodes
          B.4.8 Requirements for the Level-2 subdomain
Annex C
Annex D  OOB OCh-O and OTSiG-O protocol specification
     D.1 Overview
     D.2 PDU format
          D.2.1 Hello sub-Protocol
               D.2.1.1 Hello sequence TLV
               D.2.1.2 Hello validity TLV
          D.2.2 Status Reporting sub-protocol
               D.2.2.1 Message ID TLV
               D.2.2.2 OPS Trail Identification TLV
               D.2.2.3 OCh-P and OTSiG Link Connection ID TLV
               D.2.2.4 OCh and OTSiG Status TLV
          D.2.3 Protocol adaptation to IPv4 DCN
          D.2.4 OTSiG-O TTI TLV
          D.2.5 OTSiG-O BDI TLV
          D.2.6 OTSi TSI TLV
     D.3 OCh_O and OTSiG-O communication channel adaptation function
          D.3.1 OCh_O communication channel adaptation function (OCC/OCh-O_A)
          D.3.2 OCh_O and OTSiG-O communication channel adaptation function (OCC/OCh|OTSiG-O_A)
     D.4 OCh_O [and OTSiG-O] communication channel termination function (OCC_TT)
Appendix I  Constraints of the interworking functions in DCN
     I.1 General assumptions
     I.2 Common to all scenarios
          I.2.1 Scenario 1: OSI-based management system connected to node A
          I.2.2 Scenario 2: IP-based management systems connected to node B
          I.2.3 Scenario 3: OSI-based management systems connected to node C
          I.2.4 Scenario 4: IP-based management systems connected to node E
          I.2.5 Scenario 5: OSI-based management systems connected to node F
          I.2.6 Scenario 6: IP-based management systems connected to node G
Appendix II  Example implementation of automatic encapsulation
     II.1 Introduction
     II.2 Updates to Dijkstra's algorithm
          II.2.1 Changes to database
          II.2.2 Changes to algorithm
Appendix III  Commissioning guide for SDH NEs in dual [IETF RFC 1195] environment and impact of automatic encapsulation option
     III.1 Introduction
     III.2 Integrated IS-IS without automatic encapsulation
          III.2.1 Introduction and rules of [IETF RFC 1195]
          III.2.2 Level-2 subdomain
          III.2.3 Level-2 subdomain with external routers running integrated IS-IS
          III.2.4 External routers running OSPF or other IP routing protocols
     III.3 Integrated IS-IS with automatic encapsulation
          III.3.1 Introduction and effect on topological restrictions
          III.3.2 Getting IP traffic in and out of the SDH embedded network
               III.3.2.1 IP capable gateway NE
               III.3.2.2 OSI-only gateway NE
Appendix IV  Example illustration of packet 1+1 protection
     IV.1 Packet 1+1 protection overview
     IV.2 Packet 1+1 protection illustration
     IV.3 Operation of selector algorithm under various failure scenarios
Appendix V  Mapping version 4 and version 5 clause numbers
Bibliography
<\pre>