Summary
This document is an Implementers' Guide for Recommendation ITU-T G.8001/Y.1354 (2016-04).
This version contains all updates submitted up to and including those at Study Group 15 meeting in January/February 2020.
This document was approved by ITU-T Study Group 15 on 7 February 2020
Change log
| 19 October 2018 | First version. |
| 07 February 2020 | Second version |
| Editors: | Jessy Rouyer Nokia | E-mail: jessy.rouyer@nokia.com |
|---|---|---|
| Yuji Tochio Fujitsu | E-mail: tochio@fujitsu.com |
Implementers’ Guide ITU-T G.8001/Y.1354 Implementers' Guide
Implementers' guide for Recommendation ITU-T G.8001/Y.1354
1. Scope
This guide provides a list of the definitions that were deleted from Recommendation ITU-T G.8001/Y.1354 when moved to their source Recommendations.
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 indicated 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-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 G.8001/Y.1354 (04/2016)] | Recommendation ITU-T G.8001/Y.1354 (04/2016), ITU-T Recommendation G.8001/Y.1354 (2016-04), Terms and definitions for Ethernet frames over transport.. |
3. Technical and editorial corrections to Recommendation ITU-T G.8001
3.1. Section 3.2
This Recommendation defines the following terms:
3.1.1. backbone Ethernet connection:An Ethernet connection of which the traffic units are encapsulated with a backbone VLAN tag (B-Tag) when they are transported through an Ethernet link. Outside an Ethernet link, the traffic units are without a backbone VLAN tag; the information transported in the backbone VLAN tag is presented as a set of parameters: priority, drop eligible and EC identifier. The link end performs the mapping of those parameters into the backbone VLAN tag and the demapping of these parameters from the backbone VLAN tag.
NOTE – Backbone Ethernet connection is referred to in [ITU-T G.8012.1].
3.1.2. backbone service Ethernet connection:An Ethernet connection of which the traffic units are encapsulated with the first 48 bits of a backbone service instance tag (I-Tag) when they are transported through an Ethernet link. Outside an Ethernet link, the traffic units are without a backbone service instance tag; the information transported in the backbone service instance tag is presented as a set of parameters: priority, drop eligible and EC identifier. The link end performs the mapping of those parameters into the backbone service instance tag and the demapping of these parameters from the backbone service instance tag.
NOTE – Backbone service Ethernet connection is referred to in [ITU-T G.8012.1].
3.1.3. customer: The entity that has ownership authority over a set of flow points. The customer may have one or more service instances.
NOTE – Customer is referred to in [ITU-T G.8011].
3.1.4. customer Ethernet connection:An Ethernet connection (EC) of which the traffic units are encapsulated with a customer VLAN tag (C-Tag) when they are transported through an Ethernet link. Outside an Ethernet link, the traffic units are without a customer VLAN tag; the information transported in the customer VLAN tag is presented as a set of parameters: priority, drop eligible and EC identifier. The link end performs the mapping of those parameters into the customer VLAN tag and the demapping of these parameters from the customer VLAN tag.
NOTE – Customer Ethernet connection is referred to in [ITU-T G.8012.1].
3.1.5. dual-ended: A type of protocol messaging whereby an initiating MEP sends a request PDU to a receiving peer MEP, which does not send any response. In performance monitoring, the receiving MEP performs measurement calculations.
NOTE – Dual-ended is referred to in [ITU-T G.8013].
3.1.6. EoT-NNI:An NNI for the transfer of ETH_CI traffic units over a transport layer network.
NOTE – EoT-NNI is referred to in [ITU-T G.8012].
3.1.7. ERP instance: An entity that is responsible for the protection of a subset of the VLANs that transport traffic over the physical Ethernet ring. Each ERP instance is independent of other ERP instances that may be configured on the physical Ethernet ring.
NOTE – ERP instance is referred to in [ITU-T G.8032].
3.1.8. Ethernet management communication channel (ET.MCC):A function providing a management communication channel between a pair of maintenance entity group (MEG) end points (MEP). The MCC can be used to perform remote management. The specific use of MCC is outside the scope of this Recommendation. An MEP can send a frame with ETH-MCC information to its peer MEP with a remote maintenance request, remote maintenance reply, notification, etc. Configuration information needs to be provisioned to the MEP to support MCC functions. See [ITU-T G.8013] for detailed information and the protocol data unit (PDU) structure of the MCC.
NOTE – ET.MCC is defined in [ITU-T G.8051 (08/2024)] as EoT MCC.
3.1.9. ETH_CI group:A group of ETH_CI signals that is monitored as a single MEG. For this purpose, ETH OAM is added to one of the ETH_CI signals in the group.
NOTE – ETH_CI group is referred to in [ITU-T G.8010].
3.1.10. ETH_CI traffic unit:The following set of signals defined in [ITU-T G.8010]: ETH_CI Data (D), ETH_CI priority (P), ETH_CI drop eligibility (DE), ETH_CI server signal fail (SSF) and optionally ETH_CI automatic protection switching (APS). The ETH_CI_D signal carries the traffic unit that consists of the following fields: destination address (DA), source address (SA) and MAC service data unit (M_SDU).
NOTE – ETH_CI traffic unit is defined in clause 6.3.1 of [ITU-T G.8010] and referred to in [ITU-T G.8012].
3.1.11. Ethernet flow replication point (ETHF_PP):Connection point between <Srv>/ETH adaptation source and sink. ETH_CI from source Ethernet flow point (ETH_FP) is replicated and delivered across ETHF_PP to sink Ethernet termination flow point (ETH_TFP).
NOTE – ETHF_PP is referred to in [ITU-T G.8021].
3.1.12. Ethernet replicated information (ETH_PI):Replicated ETH_CI delivered across ETHTF_PP or ETHF_PP.
NOTE – ETH_PI is referred to in [ITU-T G.8021].
3.1.13. Ethernet ring: A collection of Ethernet ring nodes forming a closed physical loop whereby each Ethernet ring node is connected to two adjacent Ethernet ring nodes via a duplex communications facility.
NOTE – Ethernet ring is referred to in [ITU-T G.8032].
3.1.14. Ethernet ring node: A network element that implements at least the following functionality.
One Ethernet connection function (ETH_C) with a dedicated Ethernet flow forwarding function (ETH_FF) for forwarding ring automatic protection switching (R-APS) control traffic.Two ring ports, including ETHDi/ETH adaptation function at the ring maintenance entity group level (MEL).Ethernet ring protection (ERP) control process controlling the blocking and unblocking of traffic over the ring ports.
NOTE – Ethernet ring node is referred to in [ITU-T G.8032].
3.1.15. Ethernet service: An Ethernet service supports an Ethernet flow (as specified in [ITU-T G.8010]). It is determined by the topology of the Ethernet network and a corresponding set of attributes associated with the Ethernet connection (EC), the UNI ports and NNI ports.
NOTE – Ethernet service is referred to in [ITU-T G.8011].
3.1.16. Ethernet termination flow replication point (ETHTF_PP):Connection point between <Srv>/ETH adaptation source and sink. ETH_CI from source Ethernet termination flow point (ETH_TFP) is replicated and delivered across ETHTF_PP to sink filter process.
NOTE – ETHTF_PP is referred to in [ITU-T G.8021].
3.1.17. Ethernet virtual connection (EVC):
NOTE – EVC is defined in [MEF 10.3].
3.1.18. ETH path:The highest ETH MEG level in a set of eight MEG levels.
NOTE – ETH path is referred to in [ITU-T G.8010].
3.1.19. ETH section:The lowest ETH MEG level in a set of eight MEG levels.
NOTE – ETH section is referred to in [ITU-T G.8010].
3.1.20. ETH tandem connection:An intermediate ETH MEG level in a set of eight MEG levels.
NOTE – ETH tandem connection is referred to in [ITU-T G.8010].
3.1.21. ET management network (ET.MN):A subset of a TMN that is responsible for managing those parts of a network element that contain ET layer network entities. An ET.MN may be subdivided into a set of ET management subnetworks.
NOTE – ET.MN is referred to in [ITU-T G.8051 (08/2024)].
3.1.22. ET management subnetwork (ET.MSN):Subnetwork consisting of a set of separate embedded communication channels (ECCs) and associated intra-site data communication links which are interconnected to form a data communication network (DCN) within any given ET topology. For ET, the physical channel supporting the ECC is the Ethernet management communication channel (MCC) as defined in [ITU-T G.8013]. An ET.MSN represents an ET specific local communications network (LCN) portion of a network operator's overall data communication network or TMN.
NOTE – ET.MSN is referred to in [ITU-T G.8051 (08/2024)].
3.1.23. ET network element (ET.NE):Element containing entities from one or more ET layer networks. An ET.NE may therefore be a stand-alone physical entity or a subset of a network element. It supports at least network element functions (NEFs) and may also support an operations system function (OSF). It contains managed objects (MOs), a message communication function (MCF) and a management application function (MAF). The functions of an ET.NE may be contained within an NE that also supports other layer networks. These layer network entities are considered to be managed separately from ET entities. As such, they are not part of the ET.MN or ET.MSN.
NOTE – ET.NE is referred to in [ITU-T G.8051 (08/2024)].
3.1.24. Ety-NNI:An NNI for the transfer of ETH_CI traffic units over a physical Ethernet interface.
NOTE – Ety-NNI is referred to in [ITU-T G.8012].
3.1.25. Ety-UNI:A UNI for the transfer of ETH_CI traffic units over a physical Ethernet interface.
NOTE – Ety-UNI is referred to in [ITU-T G.8012].
3.1.26. external NNI (ENNI):
NOTE – ENNI is defined by [MEF 26.1].
3.1.27. far-end: In single-ended or dual-ended messaging, the direction and information relating to a one-way measurement from an initiating MEP) to a receiving or responding peer MEP.
NOTE – Far-end is referred to in [ITU-T G.8013].
3.1.28. initiating MEP: An initiating MEP initiates measurements by sending request PDUs, and in the case of single-ended messaging, receiving response PDUs.
NOTE – Initiating MEP is referred to in [ITU-T G.8013].
3.1.29. interconnection node: An Ethernet ring node that is common to two or more Ethernet rings or to a sub-ring and an interconnected network. At each interconnection node, there may be one or more Ethernet rings that can be accessed through a single ring port and not more than one Ethernet ring that is accessed by two ring ports. The former set of Ethernet rings is comprised of sub-rings, whereas the latter Ethernet ring is considered a major ring, relative to this interconnection node. If the interconnection node is used to connect a (set of) sub-ring(s) to another network, then there is no Ethernet ring accessed by two ring ports.
NOTE – Interconnection node is referred to in [ITU-T G.8032].
3.1.30. in-profile: For frames that belong to the same instance of an Ethernet service and priority, in-profile frames are defined as frames for which priority corresponds to a common value <X> and the network has determined that drop-eligibility corresponds to <false>. Procedures to determine drop-eligibility for a frame and procedures to convey priority and drop-eligibility on a frame are network and service specific.
NOTE – In-profile is referred to in [ITU-T G.8013].
3.1.31. in-service OAM: OAM actions that are carried out while the data traffic is not interrupted, with an expectation that data traffic remains transparent to OAM actions.
NOTE – In-service OAM is referred to in [ITU-T G.8013].
3.1.32. leaf group:A group representing two or more leaf ports within an RMP EC which can transmit to and receive from other leafs in the leaf group. Leaf ports within a leaf group cannot transmit to or receive from leafs outside the group.
NOTE – Leaf group is referred to in [ITU-T G.8012.1].
3.1.33. link Ethernet connection:An Ethernet connection of which the traffic units are either not encapsulated or encapsulated with a priority tag.
NOTE – Link Ethernet connection is referred to in [ITU-T G.8012.1].
3.1.34. maintenance entity:The entity between two of the flow/connection points in a maintenance entity group.
NOTE – Maintenance entity is referred to in [ITU-T G.8010].
3.1.35. maintenance entity group (MEG):A group defined, for the purpose of fragment or connection monitoring, between a set of flow or connection points within a fragment/connection. This set of flow or connection points may be located at the boundary of one administrative domain or a protection domain, or at the boundaries of two adjacent administrative domains. The maintenance entity group consists of one or more maintenance entities.
NOTE – MEG is referred to in [ITU-T G.8010].
3.1.36. maintenance entity group end point compound sink function:A compound transport processing function that accepts the characteristic information of the layer network at its input, extracts and processes the OAM information related to the monitoring of the maintenance entity group, filters the OAM information from within to the maintenance entity group, adapts the information and presents it as the characteristic information of the layer or a client layer at its output, potentially as a (client) layer maintenance signal (e.g., AIS).
NOTE – MEP compound sink function is referred to in [ITU-T G.8010].
3.1.37. maintenance entity group end point compound source function:A compound transport processing function that accepts the characteristic information of the layer or a client layer network at its input, adapts that information, filters it for OAM information interfering with its own OAM information, adds OAM information to allow the maintenance entity group to be monitored and presents the resulting information at its output.
NOTE – MEP compound source function is referred to in [ITU-T G.8010].
3.1.38. maintenance entity group intermediate point compound function:A compound transport processing function that accepts the characteristic information of the layer network at its input, reacts to OAM information related to on-demand monitoring of a maintenance entity group and presents the characteristic information without the OAM to which it reacted at its output.
NOTE – MIP compound function is referred to in [ITU-T G.8010].
3.1.39. major ring: An Ethernet ring that is connected on two ports to an interconnection node.
NOTE – Major ring is referred to in [ITU-T G.8032].
3.1.40. MEG end point (MEP): A point marking the end of an ETH MEG that is capable of initiating and terminating OAM frames for fault management and performance monitoring. A MEP does not add a new forwarding identifier to the transit ETH flows. A MEP does not terminate the transit ETH flows, though it can observe these flows (e.g., count frames).
NOTE – MEP is referred to in [ITU-T G.8013].
3.1.41. MEG intermediate point (MIP): An intermediate point in a MEG that is capable of reacting to some OAM frames. A MIP does not initiate OAM frames. A MIP takes no action on the transit ETH flows.
NOTE – MIP is referred to in [ITU-T G.8013].
3.1.42. near-end: In single-ended messaging, the direction and information relating to a one-way measurement from a responding peer MEP to an initiating MEP.
NOTE – Near-end is referred to in [ITU-T G.8013].
3.1.43. network termination:The network element in the transport network that is connected to the customer edge equipment.
NOTE – Network termination is referred to in [ITU-T G.8012].
3.1.44. network-to-network interface (NNI):An interface that is used for the interconnection of network elements within a transport network.
NOTE – NNI is referred to in [ITU-T G.8012].
3.1.45. on-demand measurement: A measurement (e.g., performance monitoring such as delay measurement, loss measurement) that is running at a specific request. An on-demand measurement has a defined start and end time or date.
NOTE – On-demand measurement is referred to in [ITU-T G.8052 (01/2024)].
3.1.46. on-demand monitoring:A method to infer a specific status or performance characteristic of a maintenance entity or a set of maintenance entities within a maintenance entity group at a specific time with the purpose of obtaining a snapshot of the performance or to diagnose an identified fault condition or performance degradation.
NOTE – On-demand monitoring is referred to in [ITU-T G.8010].
3.1.47. on-demand OAM: OAM actions that are initiated via manual intervention for a limited time to carry out diagnostics. On-demand OAM can result in singular or periodic OAM actions during the diagnostics time interval.
NOTE – On-demand OAM is referred to in [ITU-T G.8013].
3.1.48. one-way: A measurement of the performance of frames that is achieved in one direction from an initiating MEP to a peer MEP, or vice versa; i.e., a unidirectional measurement.
NOTE – One-way is referred to in [ITU-T G.8013].
3.1.49. out-of-service OAM: OAM actions that are carried out while the data traffic is interrupted.
NOTE – Out-of-service OAM is referred to in [ITU-T G.8013].
3.1.50. operator virtual connection (OVC):
NOTE – OVC is defined by [MEF 26.1].
3.1.51. peer MEP: In a given MEP, all of the other MEPs in the same MEG.
NOTE – Peer MEP is referred to in [ITU-T G.8013].
3.1.52. proactive measurement: A measurement (e.g., performance monitoring such as delay measurement, loss measurement.) that is running continuously after it has been established. Proactive measurements can only be temporarily disabled.
NOTE: Proactive measurement is referred to in [ITU-T G.8052 (01/2024)].
3.1.53. proactive monitoring:A method to continuously infer the status and performance of a maintenance entity group with the purpose of detecting disturbances, faults and degradations immediately after their occurrence in order to verify the service level agreement or initiate recovery actions to restore the service to the guaranteed level.
NOTE – Proactive monitoring is referred to in [ITU-T G.8010].
3.1.54. proactive OAM: OAM actions that are carried out continuously to permit proactive reporting of fault or performance results.
NOTE – Proactive OAM is referred to in [ITU-T G.8013].
3.1.55. R-APS virtual channel: The R-APS channel connection between two interconnection nodes of a sub-ring in (an)other Ethernet ring(s) or network(s). Its connection characteristics (e.g., path, performance) are influenced by the characteristics of the network (e.g., Ethernet ring) providing connectivity between the interconnection nodes.
NOTE – R-APS virtual channel is referred to in [ITU-T G.8032].
3.1.56. responding MEP: In single-ended messaging, an MEP that receives request PDUs from an initiating MEP and transmits corresponding response PDUs.
NOTE – Responding MEP is referred to in [ITU-T G.8013].
3.1.57. receiving MEP: In dual-ended messaging, an MEP that receives request PDUs from an initiating MEP, and does not respond to them.
NOTE – Receiving MEP is referred to in [ITU-T G.8013].
3.1.58. ring MEL: The maintenance entity group (MEG) level providing a communication channel for ring automatic protection switching (R-APS) information.
NOTE – Ring MEL is referred to in [ITU-T G.8032].
3.1.59. ring protection link (RPL): The ring link that under normal conditions, i.e., without any failure or request, is blocked (at one or both ends) to traffic channels, to prevent the formation of loops.
NOTE – Ring protection link is referred to in [ITU-T G.8032].
3.1.60. RPL neighbour node: When configured, an Ethernet ring node adjacent to the RPL that is responsible for blocking its end of the RPL under normal conditions (i.e., the ring is established and no requests are present in the ring) in addition to the block by the RPL owner node. However, it is not responsible for activating the reversion behaviour.
NOTE – RPL neighbour node is referred to in [ITU-T G.8032].
3.1.61. RPL owner node: An Ethernet ring node adjacent to the RPL that is responsible for blocking its end of the RPL under normal conditions (i.e., the ring is established and no requests are present in the ring). Furthermore, it is responsible for activating reversion behaviour from protected or manual switch/forced switch (MS/FS) conditions.
NOTE – RPL owner node is referred to in [ITU-T G.8032].
3.1.62. server MEP: A server MEP represents the compound function of the server layer termination function and server/ETH adaptation function, which is used to notify the ETH layer MEPs of conditions of the server layer that may be relevant to these ETH MEPs (e.g., failure or degradation detection by the server layer termination function or server/ETH adaptation function), where the server layer termination function is expected to run OAM mechanisms specific to that server layer.
NOTE – Server MEP is referred to in [ITU-T G.8013].
3.1.63. service Ethernet connection:An Ethernet connection of which the traffic units are encapsulated with a service VLAN tag (S-Tag) when they are transported through an Ethernet link. Outside an Ethernet link1 the traffic units are without service VLAN tag; the information transported in the service VLAN tag is presented as a set of parameters: priority, drop eligible and EC identifier. The link end performs the mapping of those parameters into the service VLAN tag and the demapping of these parameters from the service VLAN tag.
NOTE – Service Ethernet connection is referred to in [ITU-T G.8012.1].
3.1.64. service frame:
NOTE – Service frame is defined in [MEF 10.3].
3.1.65. single-ended: A type of protocol messaging whereby an initiating MEP sends a request PDU to a responding peer MEP, and the peer MEP responds by sending a response PDU that contains the original request data plus any additional data added by the responder. In performance monitoring, the initiating MEP performs measurement calculations.
NOTE – Single-ended is referred to in [ITU-T G.8013].
3.1.66. sub-ring: An Ethernet ring that is connected to (an)other Ethernet ring(s) or network(s) through the use of a pair of interconnection nodes. On their own, the sub-ring links do not form a closed loop. A closed connection of traffic may be formed by the sub-ring links and one or more links, which are controlled by (an)other Ethernet ring(s) or network(s), between interconnection nodes.
NOTE – Sub-ring is referred to in [ITU-T G.8032].
3.1.67. sub-ring link: A span (e.g., link/port) connecting adjacent sub-ring nodes that are under the control of the Ethernet ring protection control process (ERP control process) of the sub-ring.
NOTE – Sub-ring link is referred to in [ITU-T G.8032].
3.1.68. two-way: A measurement of the performance of frames that is achieved from an initiating MEP to responding peer MEP, and back to the initiating MEP; i.e., a bidirectional or round-trip measurement.
NOTE – Two-way is referred to in [ITU-T G.8013].
3.1.69. traffic-conditioning function:A transport processing function that accepts the characteristic information of the layer network at its input, classifies the traffic units according to configured rules, meters each traffic unit within its class to determine its eligibility, polices non-conformant traffic units and presents the remaining traffic units at its output as characteristic information of the layer network.
NOTE – Traffic-conditioning function is referred to in [ITU-T G.8010].
3.1.70. traffic-shaping function:A transport processing function that accepts the characteristic information of the layer network at its input, classifies the traffic units according to configured rules, meters each traffic unit within its class to determine its eligibility, controls non-conformant traffic units by buffering and scheduling them alternately with conformant traffic units for presentation at its output as characteristic information of the layer network.
NOTE – Traffic-shaping function is referred to in [ITU-T G.8021].
3.1.71. user network interface (UNI):
NOTE – User network interface is referred to in [MEF 10.3].
3.1.72. user-to-network interface (UNI):An interface that is used for the interconnection of customer equipment with a network element of the transport network.
NOTE – User-to-network interface is referred to in [ITU-T G.8012].
3.1.73. wait to block timer: A timer that is employed by the RPL owner to delay reversion after a forced switch or manual switch has been cleared.
NOTE – Wait to block timer is referred to in [ITU-T G.8032].
3.2. Appendix I
Table 1 — Source Recommendations
| ITU-T Recommendation | Latest version |
|---|---|
| ITU-T G.8010/Y.1306 | 02/2004 with Amd. 1 (2006), Err. 1 (2007), Err. 2 (2007) and Amd. 2 (2010). |
| ITU-T G.8012/Y.1308 | 08/2004 with Amd.1 (2006) |
| ITU-T G.8012.1/Y.1308.1 | 12/2012 |
| ITU-T G.8021/Y.1341 | 04/2015 with Cor. 1 (2015) |
| ITU-T G.8051/Y.1345 | 08/2015 |
3.3. Bibliography
| [ITU‑T G.7710 (11/2025)] | Recommendation ITU-T G.7710 (11/2025), Recommendation ITU-T G.7710/Y.1701 (2012), Common equipment management function requirements.. |
| [ITU‑T G.800 (04/2016)] | Recommendation ITU-T G.800 (04/2016), Recommendation ITU-T G.800 (2012), Unified functional architecture of transport networks.. |
| [ITU‑T G.805 (03/2000)] | Recommendation ITU-T G.805 (03/2000), Recommendation ITU-T G.805 (2000), Generic functional architecture of transport networks.. |
| [ITU‑T G.8051 (08/2024)] | Recommendation ITU-T G.8051 (08/2024), Recommendation ITU-T G.8051/Y.1345 (2015). Management aspects of the Ethernet transport (ET) capable network element.. |
| [ITU‑T G.8052 (01/2024)] | Recommendation ITU-T G.8052 (01/2024), |
| [ITU‑T G.808.1 (05/2014)] | Recommendation ITU-T G.808.1 (05/2014), Recommendation ITU-T G.808.1 (2014), Generic protection switching – Linear trail and subnetwork protection.. |
| [ITU‑T G.809 (03/2003)] | Recommendation ITU-T G.809 (03/2003), Recommendation ITU-T G.809 (2003), Functional architecture of connectionless layer networks.. |
| [ITU‑T M.3010 (10/1992)] | Recommendation ITU-T M.3010 (10/1992), Recommendation ITU-T M.3010 (2000), Principles for a telecommunications management network; Amendment 2 (2005).. |
| [ITU‑T M.3013 (02/2000)] | Recommendation ITU-T M.3013 (02/2000), Recommendation ITU-T M.3013 (2000), Considerations for a telecommunications management network.. |
| [ITU‑T M.3100 (10/1992)] | Recommendation ITU-T M.3100 (10/1992), Recommendation ITU-T M.3100 (2005), Generic network information model.. |
| [ITU‑T X.700 (09/1992)] | Recommendation ITU-T X.700 (09/1992) | ISO/IEC 7498-4, Recommendation ITU-T X.700 (1992), Management framework for Open Systems Interconnection (OSI) for CCITT applications.. |
| [ITU‑T X.701 (01/1992)] | Recommendation ITU-T X.701 (01/1992) | ISO/IEC 10040, Recommendation ITU-T X.701 (1997. ISO/IEC 10040:1998, Information technology – Open Systems Interconnection – Systems management overview.. |
| [ITU‑T G.7712] | Recommendation ITU-T G.7712, Recommendation ITU-T G.7712/Y.1703 (2010), Architecture and specification of data communication network. |
| [ITU‑T G.8010] | Recommendation ITU-T G.8010, Recommendation ITU-T G.8010/Y.1306 (2004), Architecture of Ethernet layer networks. |
| [ITU‑T G.8011] | Recommendation ITU-T G.8011,
|
| [ITU‑T G.8012] | Recommendation ITU-T G.8012, Recommendation ITU-T G.8012/Y.1308 (2004), Ethernet UNI and Ethernet NNI. |
| [ITU‑T G.8012.1] | Recommendation ITU-T G.8012.1, Recommendation ITU-T G.8012.1/Y.1308.1 (2012), Interfaces for the Ethernet transport network. |
| [ITU‑T G.8013] | Recommendation ITU-T G.8013,
|
| [ITU‑T G.8021] | Recommendation ITU-T G.8021, Recommendation ITU-T G.8021/Y.1341 (2015), Characteristics of Ethernet transport network equipment functional blocks. |
| [ITU‑T G.8031] | Recommendation ITU-T G.8031,
|
| [ITU‑T G.8032] | Recommendation ITU-T G.8032,
|
| [ITU‑T G.870] | Recommendation ITU-T G.870, Recommendation ITU-T G.870/Y.1352 (2012), Terms and definitions for optical transport networks. |
| [ITU‑T G.Sup52] | Recommendation ITU-T G.Sup52, ITU-T G-series Recommendations – Supplement 52 (2012), Ethernet ring protection switching. |
| [MEF 10.3] | MEF 10.3,
|
| [MEF 12.1] | MEF 12.1,
|
| [MEF 26.1] | MEF 26.1,
|
4. Introduction
This implementers' guide is a compilation of reported defects for all versions of Recommendation ITU-T G.8001. In this edition of the guide, reported defects identified as of 2018-10 are given for:
Recommendation ITU-T G.8001/Y.1354 (2016-04)
The guide must be read in conjunction with Recommendation ITU-T G.8001/Y.1354 (2016-04) to serve as an additional source of information for implementers. The changes, clarifications and corrections defined herein are expected to be included in future versions of the affected Recommendations.
5. Defect resolution procedure
Upon discovering technical defects with any components of the texts covered by this implementers' guide, please provide a written description directly to the editors of the affected Recommendation(s) with a copy to the respective Rapporteur (See contacts above). The template for a defect report is located at the end of this guide. Return contact information should also be supplied so a dialogue can be established to resolve the matter and an appropriate reply to the defect report can be conveyed. This defect resolution process is open to any interested party. Formal membership in the ITU is not required to participate in this process.
6. Nomenclature
In addition to traditional revision marks, the following marks and symbols are used to indicate to the reader how changes to the text of a Recommendation should be applied:
| Symbol | Description |
|---|---|
| [Begin Correction] | Identifies the start of revision marked text based on extractions from the published Recommendations affected by the correction being described. |
| [End Correction] | Identifies the end of revision marked text based on extractions from the published Recommendations affected by the correction being described. |
| … | Indicates that the portion of the Recommendation between the text appearing before and after this symbol has remained unaffected by the correction being described and has been omitted for brevity. |
| --- SPECIAL INSTRUCTIONS --- {instructions} | Indicates a set of special editing instructions to be followed. |
Annex A
Recommendation ITU-T G.8001/Y.1354 Defect Report Form
(This annex forms an integral part of this Implementers’ Guide.)
| DATE: | |
CONTACT INFORMATION | |
| AFFECTED RECOMMENDATIONS: | |
| DESCRIPTION OF PROBLEM: | |
| SUGGESTIONS FOR RESOLUTION: | |
NOTE – Attach additional pages if more space is required than is provided above. | |