rfc9801v1.txt   rfc9801.txt 
Internet Engineering Task Force (IETF) S. Gringeri Internet Engineering Task Force (IETF) S. Gringeri
Request for Comments: 9801 J. Whittaker Request for Comments: 9801 J. Whittaker
Category: Standards Track Verizon Category: Standards Track Verizon
ISSN: 2070-1721 N. Leymann ISSN: 2070-1721 N. Leymann
Deutsche Telekom Deutsche Telekom
C. Schmutzer, Ed. C. Schmutzer, Ed.
Cisco Systems, Inc. Cisco Systems, Inc.
C. Brown C. Brown
Ciena Corporation Ciena Corporation
June 2025 July 2025
Private Line Emulation over Packet Switched Networks Private Line Emulation over Packet Switched Networks
Abstract Abstract
This document expands the applicability of Virtual Private Wire This document expands the applicability of Virtual Private Wire
Service (VPWS) bit-stream payloads beyond Time Division Multiplexing Service (VPWS) bit-stream payloads beyond Time Division Multiplexing
(TDM) signals and provides pseudowire transport with complete signal (TDM) signals and provides pseudowire transport with complete signal
transparency over Packet Switched Networks (PSNs). transparency over Packet Switched Networks (PSNs).
skipping to change at line 56 skipping to change at line 56
to this document. Code Components extracted from this document must to this document. Code Components extracted from this document must
include Revised BSD License text as described in Section 4.e of the include Revised BSD License text as described in Section 4.e of the
Trust Legal Provisions and are provided without warranty as described Trust Legal Provisions and are provided without warranty as described
in the Revised BSD License. in the Revised BSD License.
Table of Contents Table of Contents
1. Introduction and Motivation 1. Introduction and Motivation
2. Requirements Notation 2. Requirements Notation
3. Terminology and Reference Models 3. Terminology and Reference Models
3.1. Terminology 3.1. Abbreviations
3.2. Reference Models 3.2. Reference Models
4. Emulated Services 4. Emulated Services
4.1. Generic PLE Service 4.1. Generic PLE Service
4.2. Ethernet Services 4.2. Ethernet Services
4.2.1. 1000BASE-X 4.2.1. 1000BASE-X
4.2.2. 10GBASE-R and 25GBASE-R 4.2.2. 10GBASE-R and 25GBASE-R
4.2.3. 40GBASE-R, 50GBASE-R, and 100GBASE-R 4.2.3. 40GBASE-R, 50GBASE-R, and 100GBASE-R
4.2.4. 200GBASE-R and 400GBASE-R 4.2.4. 200GBASE-R and 400GBASE-R
4.2.5. Energy Efficient Ethernet (EEE) 4.2.5. Energy Efficient Ethernet (EEE)
4.3. SONET/SDH Services 4.3. SONET/SDH Services
skipping to change at line 143 skipping to change at line 143
or SDH Virtual Container (VC). In other words, PLE provides an or SDH Virtual Container (VC). In other words, PLE provides an
independent layer network underneath the SONET/SDH layer network, independent layer network underneath the SONET/SDH layer network,
whereas CEP operates at the same level and peer with the SONET/SDH whereas CEP operates at the same level and peer with the SONET/SDH
layer network. layer network.
The mechanisms described in this document follow principles similar The mechanisms described in this document follow principles similar
to Structure-Agnostic TDM over Packet (SAToP) (defined in [RFC4553]). to Structure-Agnostic TDM over Packet (SAToP) (defined in [RFC4553]).
The applicability is expanded beyond the narrow set of Plesiochronous The applicability is expanded beyond the narrow set of Plesiochronous
Digital Hierarchy (PDH) interfaces (T1, E1, T3, and E3) to allow the Digital Hierarchy (PDH) interfaces (T1, E1, T3, and E3) to allow the
transport of signals from many different technologies such as transport of signals from many different technologies such as
Ethernet, Fibre Channel, SONET/SDH ([GR253] / [G.707]), and OTN Ethernet, Fibre Channel, SONET/SDH ([GR253] / [G.707]), and Optical
[G.709] at gigabit speeds. The signals are treated as bit-stream Transport Network (OTN) [G.709] at gigabit speeds. The signals are
payload, which was defined in the Pseudo Wire Emulation Edge-to-Edge treated as bit-stream payload, which was defined in the Pseudo Wire
(PWE3) architecture in Sections 3.3.3 and 3.3.4 of [RFC3985]. Emulation Edge-to-Edge (PWE3) architecture in Sections 3.3.3 and
3.3.4 of [RFC3985].
2. Requirements Notation 2. Requirements Notation
The key words "MUST", "MUST NOT", "REQUIRED", "SHALL", "SHALL NOT", The key words "MUST", "MUST NOT", "REQUIRED", "SHALL", "SHALL NOT",
"SHOULD", "SHOULD NOT", "RECOMMENDED", "NOT RECOMMENDED", "MAY", and "SHOULD", "SHOULD NOT", "RECOMMENDED", "NOT RECOMMENDED", "MAY", and
"OPTIONAL" in this document are to be interpreted as described in BCP "OPTIONAL" in this document are to be interpreted as described in BCP
14 [RFC2119] [RFC8174] when, and only when, they appear in all 14 [RFC2119] [RFC8174] when, and only when, they appear in all
capitals, as shown here. capitals, as shown here.
3. Terminology and Reference Models 3. Terminology and Reference Models
3.1. Terminology 3.1. Abbreviations
ACH: Associated Channel Header [RFC7212] ACH: Associated Channel Header [RFC7212]
AIS: Alarm Indication Signal AIS: Alarm Indication Signal
AIS-L: Line AIS AIS-L: Line AIS
MS-AIS: Multiplex Section AIS MS-AIS: Multiplex Section AIS
BITS: Building Integrated Timing Supply [ATIS-0900105.09.2013] BITS: Building Integrated Timing Supply [ATIS-0900105.09.2013]
skipping to change at line 216 skipping to change at line 217
MEF: MEF Forum MEF: MEF Forum
MPLS: Multiprotocol Label Switching [RFC3031] MPLS: Multiprotocol Label Switching [RFC3031]
NOS: Not Operational NOS: Not Operational
NSP: Native Service Processing [RFC3985] NSP: Native Service Processing [RFC3985]
ODUk: Optical Data Unit k ODUk: Optical Data Unit k
OOF: Out Of Frame
OTN: Optical Transport Network OTN: Optical Transport Network
OTUk: Optical Transport Unit k OTUk: Optical Transport Unit k
PCS: Physical Coding Sublayer PCS: Physical Coding Sublayer
PDV: Packet Delay Variation PDV: Packet Delay Variation
PE: Provider Edge PE: Provider Edge
skipping to change at line 240 skipping to change at line 243
PLR: Packet Loss Rate PLR: Packet Loss Rate
PMA: Physical Medium Attachment PMA: Physical Medium Attachment
PMD: Physical Medium Dependent PMD: Physical Medium Dependent
PSN: Packet Switched Network PSN: Packet Switched Network
PTP: Precision Time Protocol PTP: Precision Time Protocol
PW: Pseudowire [RFC3985] PW: Pseudowire [RFC4664]
PWE3: Pseudo Wire Emulation Edge-to-Edge [RFC3985] PWE3: Pseudo Wire Emulation Edge-to-Edge [RFC3985]
RDI: Remote Defect Indication RDI: Remote Defect Indication
RSVP-TE: Resource Reservation Protocol Traffic Engineering [RFC4875] RSVP-TE: Resource Reservation Protocol Traffic Engineering [RFC4875]
RTCP: RTP Control Protocol [RFC3550] RTCP: RTP Control Protocol [RFC3550]
RTP: Real-time Transport Protocol [RFC3550] RTP: Real-time Transport Protocol [RFC3550]
skipping to change at line 282 skipping to change at line 285
TCP: Transmission Control Protocol [RFC9293] TCP: Transmission Control Protocol [RFC9293]
TDM: Time Division Multiplexing TDM: Time Division Multiplexing
TTS: Transmitter Training Signal TTS: Transmitter Training Signal
UAS: Unavailable Seconds UAS: Unavailable Seconds
VPWS: Virtual Private Wire Service [RFC3985] VPWS: Virtual Private Wire Service [RFC3985]
Note: The term Interworking Function (IWF) is used to describe the | Note: The term Interworking Function (IWF) is used to describe
functional block that encapsulates bit streams into PLE packets and | the functional block that encapsulates bit-streams into PLE
in the reverse direction decapsulates PLE packets and reconstructs | packets and in the reverse direction decapsulates PLE packets
bit streams. | and reconstructs bit-streams.
3.2. Reference Models 3.2. Reference Models
The reference model for PLE is illustrated in Figure 1 and is inline The reference model for PLE is illustrated in Figure 1 and is inline
with the reference model defined in Section 4.1 of [RFC3985]. PLE with the reference model defined in Section 4.1 of [RFC3985]. PLE
relies on PWE3 preprocessing, in particular the concept of a Native relies on PWE3 preprocessing, in particular the concept of an NSP
Service Processing (NSP) function defined in Section 4.2.2 of function defined in Section 4.2.2 of [RFC3985].
[RFC3985].
|<--- p2p L2VPN service -->| |<--- p2p L2VPN service -->|
| | | |
| |<-PSN tunnel->| | | |<-PSN tunnel->| |
v v v v v v v v
+---------+ +---------+ +---------+ +---------+
| PE1 |==============| PE2 | | PE1 |==============| PE2 |
+---+-----+ +-----+---+ +---+-----+ +-----+---+
+-----+ | N | | | | N | +-----+ +-----+ | N | | | | N | +-----+
| CE1 |-----| S | IWF |.....VPWS.....| IWF | S |-----| CE2 | | CE1 |-----| S | IWF |.....VPWS.....| IWF | S |-----| CE2 |
skipping to change at line 316 skipping to change at line 318
CE1 physical ^ ^ CE2 physical CE1 physical ^ ^ CE2 physical
interface | | interface interface | | interface
|<--- emulated service --->| |<--- emulated service --->|
| | | |
attachment attachment attachment attachment
circuit circuit circuit circuit
Figure 1: PLE Reference Model Figure 1: PLE Reference Model
PLE embraces the minimum intervention principle outlined in PLE embraces the minimum intervention principle outlined in
Section 3.3.5 of [RFC3985] whereas the data is flowing through the Section 3.3.5 of [RFC3985], which means the data is flowing through
PLE encapsulation layer as received without modifications. the PLE encapsulation layer as received without modifications.
For some service types, the NSP function is responsible for For some service types, the NSP function is responsible for
performing operations on the native data received from the CE. performing operations on the data received from the CE. Examples are
Examples are terminating Forward Error Correction (FEC), terminating terminating FEC, terminating the OTUk layer for OTN, or dealing with
the OTUk layer for OTN, or dealing with multi-lane processing. After multi-lane processing. After the NSP, the IWF is generating the
the NSP, the IWF is generating the payload of the VPWS, which is payload of the VPWS, which is carried via a PSN tunnel.
carried via a PSN tunnel.
To allow the clock of the transported signal to be carried across the To allow the clock of the transported signal to be carried across the
PLE domain in a transparent way, the relative network synchronization PLE domain in a transparent way, the relative network synchronization
reference model and deployment scenario outlined in Section 4.3.2 of reference model and deployment scenario outlined in Section 4.3.2 of
[RFC4197] are applicable and are shown in Figure 2. [RFC4197] are applicable and are shown in Figure 2.
J J
| G | G
| | | |
| +-----+ +-----+ v | +-----+ +-----+ v
skipping to change at line 361 skipping to change at line 362
The local oscillators C of PE1 and D of PE2 are locked to a common The local oscillators C of PE1 and D of PE2 are locked to a common
clock I. clock I.
The attachment circuit clock E is generated by PE2 via a differential The attachment circuit clock E is generated by PE2 via a differential
clock recovery method in reference to the common clock I. For this clock recovery method in reference to the common clock I. For this
to work, the difference between clock A and clock C (locked to I) to work, the difference between clock A and clock C (locked to I)
MUST be explicitly transferred from PE1 to PE2 using the timestamp MUST be explicitly transferred from PE1 to PE2 using the timestamp
inside the RTP header. inside the RTP header.
For the reverse direction, PE1 generates the attachment circuit clock For the reverse direction, PE1 generates the attachment circuit clock
J and the clock difference between G and D (locked to I) transferred J and the clock difference between G and D (locked to I) is
from PE2 to PE1. transferred from PE2 to PE1.
The method used to lock clocks C and D to the common clock I is out The method used to lock clocks C and D to the common clock I is out
of scope of this document; however, there are already several well- of scope of this document; however, there are already several well-
established concepts for achieving clock synchronization (commonly established concepts for achieving clock synchronization (commonly
also referred to as "frequency synchronization") available. also referred to as "frequency synchronization") available.
While using external timing inputs (aka BITS [ATIS-0900105.09.2013]) While using external timing inputs (aka BITS [ATIS-0900105.09.2013])
or synchronous Ethernet (as defined in [G.8261]), the characteristics or synchronous Ethernet (as defined in [G.8261]), the characteristics
and limits defined in [G.8262] have to be considered. and limits defined in [G.8262] have to be considered.
While relying on precision time protocol (PTP) (as defined in While relying on PTP (as defined in [G.8265.1]), the network limits
[G.8265.1]), the network limits defined in [G.8261.1] have to be defined in [G.8261.1] have to be considered.
considered.
4. Emulated Services 4. Emulated Services
This specification describes the emulation of services from a wide This specification describes the emulation of services from a wide
range of technologies, such as TDM, Ethernet, Fibre Channel, or OTN, range of technologies, such as TDM, Ethernet, Fibre Channel, or OTN,
as bit streams or structured bit streams, as defined in Sections as bit-streams or structured bit-streams, as defined in Sections
3.3.3 and 3.3.4 of [RFC3985]. 3.3.3 and 3.3.4 of [RFC3985].
4.1. Generic PLE Service 4.1. Generic PLE Service
The generic PLE service is an example of the bit stream defined in The generic PLE service is an example of the bit-stream defined in
Section 3.3.3 of [RFC3985]. Section 3.3.3 of [RFC3985].
Under the assumption that the CE-bound IWF is not responsible for any Under the assumption that the CE-bound IWF is not responsible for any
service-specific operation, a bit stream of any rate can be carried service-specific operation, a bit-stream of any rate can be carried
using the generic PLE payload. using the generic PLE payload.
There is no NSP function present for this service. There is no NSP function present for this service.
4.2. Ethernet Services 4.2. Ethernet Services
Ethernet services are special cases of the structured bit stream Ethernet services are special cases of the structured bit-stream
defined in Section 3.3.4 of [RFC3985]. defined in Section 3.3.4 of [RFC3985].
The IEEE has defined several layers for Ethernet in [IEEE802.3]. The IEEE has defined several layers for Ethernet in [IEEE802.3].
Emulation is operating at the physical (PHY) layer, more precisely at Emulation is operating at the physical (PHY) layer, more precisely at
the Physical Coding Sublayer (PCS). the PCS.
Over time, many different Ethernet interface types have been Over time, many different Ethernet interface types have been
specified in [IEEE802.3] with a varying set of characteristics, such specified in [IEEE802.3] with a varying set of characteristics, such
as optional versus mandatory FEC and single-lane versus multi-lane as optional versus mandatory FEC and single-lane versus multi-lane
transmission. transmission.
Ethernet interface types with backplane physical media dependent Ethernet interface types with backplane PMD variants and Ethernet
(PMD) variants and Ethernet interface types mandating auto- interface types mandating auto-negotiation (except 1000Base-X) are
negotiation (except 1000Base-X) are out of scope for this document. out of scope for this document.
All Ethernet services are leveraging the basic PLE payload and All Ethernet services are leveraging the basic PLE payload and
interface-specific mechanisms are confined to the respective service interface-specific mechanisms are confined to the respective service
specific NSP functions. specific NSP functions.
4.2.1. 1000BASE-X 4.2.1. 1000BASE-X
The PCS layer of 1000BASE-X (defined in Section 36 of [IEEE802.3]) is The PCS layer of 1000BASE-X (defined in Section 36 of [IEEE802.3]) is
based on 8B/10B code. based on 8B/10B code.
skipping to change at line 450 skipping to change at line 450
The PSN-bound NSP function is also responsible for detecting The PSN-bound NSP function is also responsible for detecting
attachment circuit faults specific to 10GBASE-R and 25GBASE-R such as attachment circuit faults specific to 10GBASE-R and 25GBASE-R such as
LOS and sync loss. LOS and sync loss.
The PSN-bound IWF maps the scrambled 64B/66B code stream into the The PSN-bound IWF maps the scrambled 64B/66B code stream into the
basic PLE payload. basic PLE payload.
The CE-bound NSP function MUST perform: The CE-bound NSP function MUST perform:
* PCS code sync (Section 49.2.9 of [IEEE802.3]) * PCS code sync (Section 49.2.9 of [IEEE802.3]) and
* descrambling (Section 49.2.10 of [IEEE802.3]) * descrambling (Section 49.2.10 of [IEEE802.3])
in order to properly: in order to properly:
* transform invalid 66B code blocks into proper error control * transform invalid 66B code blocks into proper error control
characters /E/ (Section 49.2.4.11 of [IEEE802.3]) characters /E/ (Section 49.2.4.11 of [IEEE802.3]) and
* insert Local Fault (LF) ordered sets (Section 46.3.4 of * insert LF ordered sets (Section 46.3.4 of [IEEE802.3]) when the
[IEEE802.3]) when the CE-bound IWF is in PLOS state or when PLE CE-bound IWF is in PLOS state or when PLE packets are received
packets are received with the L bit set. with the L bit set.
Note: Invalid 66B code blocks typically are a consequence of the CE- | Note: Invalid 66B code blocks typically are a consequence of
bound IWF inserting replacement data in case of lost PLE packets or | the CE-bound IWF inserting replacement data in case of lost PLE
the far-end PSN-bound NSP function setting sync headers to 11 due to | packets or the far-end PSN-bound NSP function setting sync
uncorrectable FEC errors. | headers to 11 due to uncorrectable FEC errors.
Before sending the bit stream to the CE, the CE-bound NSP function Before sending the bit-stream to the CE, the CE-bound NSP function
MUST also scramble the 64B/66B code stream (Section 49.2.6 MUST also scramble the 64B/66B code stream (Section 49.2.6
[IEEE802.3]). [IEEE802.3]).
4.2.3. 40GBASE-R, 50GBASE-R, and 100GBASE-R 4.2.3. 40GBASE-R, 50GBASE-R, and 100GBASE-R
The PCS layers of 40GBASE-R and 100GBASE-R (defined in Section 82 of The PCS layers of 40GBASE-R and 100GBASE-R (defined in Section 82 of
[IEEE802.3]) and of 50GBASE-R (defined in Section 133 of [IEEE802.3]) [IEEE802.3]) and of 50GBASE-R (defined in Section 133 of [IEEE802.3])
are based on a 64B/66B code transmitted over multiple lanes. are based on a 64B/66B code transmitted over multiple lanes.
Sections 74 and 91 of [IEEE802.3] define an optional FEC layer; if Sections 74 and 91 of [IEEE802.3] define an optional FEC layer; if
present, the PSN-bound NSP function MUST terminate the FEC and the present, the PSN-bound NSP function MUST terminate the FEC and the
CE-bound NSP function MUST generate the FEC. CE-bound NSP function MUST generate the FEC.
To gain access to the scrambled 64B/66B code stream, the PSN-bound To gain access to the scrambled 64B/66B code stream, the PSN-bound
NSP further MUST perform: NSP further MUST perform:
* block synchronization (Section 82.2.12 of [IEEE802.3]) * block synchronization (Section 82.2.12 of [IEEE802.3]),
* PCS lane de-skew (Section 82.2.13 of [IEEE802.3]) * PCS lane de-skew (Section 82.2.13 of [IEEE802.3]), and
* PCS lane reordering (Section 82.2.14 of [IEEE802.3]) * PCS lane reordering (Section 82.2.14 of [IEEE802.3]).
The PSN-bound NSP function is also responsible for detecting The PSN-bound NSP function is also responsible for detecting
attachment circuit faults specific to 40GBASE-R, 50GBASE-R, and attachment circuit faults specific to 40GBASE-R, 50GBASE-R, and
100GBASE-R such as LOS and loss of alignment. 100GBASE-R such as LOS and loss of alignment.
The PSN-bound IWF maps the serialized and scrambled 64B/66B code The PSN-bound IWF maps the serialized and scrambled 64B/66B code
stream including the alignment markers into the basic PLE payload. stream including the alignment markers into the basic PLE payload.
The CE-bound NSP function MUST perform: The CE-bound NSP function MUST perform:
* PCS code sync (Section 82.2.12 of [IEEE802.3]) * PCS code sync (Section 82.2.12 of [IEEE802.3]),
* alignment-marker removal (Section 82.2.15 of [IEEE802.3]) * alignment-marker removal (Section 82.2.15 of [IEEE802.3]), and
* descrambling (Section 49.2.10 of [IEEE802.3]) * descrambling (Section 49.2.10 of [IEEE802.3])
in order to properly: in order to properly:
* transform invalid 66B code blocks into proper error control * transform invalid 66B code blocks into proper error control
characters /E/ (Section 82.2.3.10 of [IEEE802.3]) characters /E/ (Section 82.2.3.10 of [IEEE802.3]) and
* insert Local Fault (LF) ordered sets (Section 81.3.4 of * insert LF ordered sets (Section 81.3.4 of [IEEE802.3]) when the
[IEEE802.3]) when the CE-bound IWF is in PLOS state or when PLE CE-bound IWF is in PLOS state or when PLE packets are received
packets are received with the L bit set with the L bit set.
Note: Invalid 66B code blocks typically are a consequence of the CE- | Note: Invalid 66B code blocks typically are a consequence of
bound IWF inserting replacement data in case of lost PLE packets or | the CE-bound IWF inserting replacement data in case of lost PLE
the far-end PSN-bound NSP function not setting sync headers to 11 due | packets or the far-end PSN-bound NSP function not setting sync
to uncorrectable FEC errors. | headers to 11 due to uncorrectable FEC errors.
When sending the bit stream to the CE, the CE-bound NSP function MUST When sending the bit-stream to the CE, the CE-bound NSP function MUST
also perform: also perform:
* scrambling of the 64B/66B code (Section 49.2.6 of [IEEE802.3]) * scrambling of the 64B/66B code (Section 49.2.6 of [IEEE802.3]),
* block distribution (Section 82.2.6 of [IEEE802.3]) * block distribution (Section 82.2.6 of [IEEE802.3]), and
* alignment-marker insertion (Sections 82.2.7 and 133.2.2 of * alignment-marker insertion (Sections 82.2.7 and 133.2.2 of
[IEEE802.3]) [IEEE802.3]).
4.2.4. 200GBASE-R and 400GBASE-R 4.2.4. 200GBASE-R and 400GBASE-R
The PCS layers of 200GBASE-R and 400GBASE-R (defined in Section 119 The PCS layers of 200GBASE-R and 400GBASE-R (defined in Section 119
of [IEEE802.3]) are based on a 64B/66B code transcoded to a 256B/257B of [IEEE802.3]) are based on a 64B/66B code transcoded to a 256B/257B
code to reduce the overhead and make room for a mandatory FEC. code to reduce the overhead and make room for a mandatory FEC.
To gain access to the 64B/66B code stream, the PSN-bound NSP further To gain access to the 64B/66B code stream, the PSN-bound NSP further
MUST perform: MUST perform:
* alignment lock and de-skew (Section 119.2.5.1 of [IEEE802.3]) * alignment lock and de-skew (Section 119.2.5.1 of [IEEE802.3]),
* PCS Lane reordering and de-interleaving (Section 119.2.5.2 of * PCS lane reordering and de-interleaving (Section 119.2.5.2 of
[IEEE802.3]) [IEEE802.3]),
* FEC decoding (Section 119.2.5.3 of [IEEE802.3]) * FEC decoding (Section 119.2.5.3 of [IEEE802.3]),
* post-FEC interleaving (Section 119.2.5.4 of [IEEE802.3]) * post-FEC interleaving (Section 119.2.5.4 of [IEEE802.3]),
* alignment-marker removal (Section 119.2.5.5 of [IEEE802.3]) * alignment-marker removal (Section 119.2.5.5 of [IEEE802.3]),
* descrambling (Section 119.2.5.6 of [IEEE802.3]) * descrambling (Section 119.2.5.6 of [IEEE802.3]), and
* reverse transcoding from 256B/257B to 64B/66B (Section 119.2.5.7 * reverse transcoding from 256B/257B to 64B/66B (Section 119.2.5.7
of [IEEE802.3]) of [IEEE802.3]).
Further, the PSN-bound NSP MUST perform rate compensation and Further, the PSN-bound NSP MUST perform rate compensation and
scrambling (Section 49.2.6 of [IEEE802.3]) before the PSN-bound IWF scrambling (Section 49.2.6 of [IEEE802.3]) before the PSN-bound IWF
maps the same into the basic PLE payload. maps the same into the basic PLE payload.
Rate compensation is applied so that the rate of the 66B encoded bit Rate compensation is applied so that the rate of the 66B encoded bit-
stream carried by PLE is 528/544 times the nominal bitrate of the stream carried by PLE is 528/544 times the nominal bitrate of the
200GBASE-R or 400GBASE-R at the PMA service interface. X number of 200GBASE-R or 400GBASE-R at the PMA service interface. X number of
66-byte-long rate compensation blocks are inserted every X*20479 66-byte-long rate compensation blocks are inserted every X*20479
number of 66B client blocks. For 200GBASE-R, the value of X is 16; number of 66B client blocks. For 200GBASE-R, the value of X is 16;
for 400GBASE-R, the value of X is 32. Rate compensation blocks are for 400GBASE-R, the value of X is 32. Rate compensation blocks are
special 66B control characters of type 0x00 that can easily be special 66B control characters of type 0x00 that can easily be
searched for by the CE-bound IWF in order to remove them. searched for by the CE-bound IWF in order to remove them.
The PSN-bound NSP function is also responsible for detecting The PSN-bound NSP function is also responsible for detecting
attachment circuit faults specific to 200GBASE-R and 400GBASE-R such attachment circuit faults specific to 200GBASE-R and 400GBASE-R such
as LOS and loss of alignment. as LOS and loss of alignment.
The CE-bound NSP function MUST perform: The CE-bound NSP function MUST perform:
* PCS code sync (Section 49.2.13 of [IEEE802.3]) * PCS code sync (Section 49.2.13 of [IEEE802.3]),
* descrambling (Section 49.2.10 of [IEEE802.3]) * descrambling (Section 49.2.10 of [IEEE802.3]), and
* rate compensation block removal * rate compensation block removal
in order to properly: in order to properly:
* transform invalid 66B code blocks into proper error control * transform invalid 66B code blocks into proper error control
characters /E/ (Section 119.2.3.9 of [IEEE802.3]) characters /E/ (Section 119.2.3.9 of [IEEE802.3]) and
* insert Local Fault (LF) ordered sets (Section 81.3.4 of * insert LF ordered sets (Section 81.3.4 of [IEEE802.3]) when the
[IEEE802.3]) when the CE-bound IWF is in PLOS state or when PLE CE-bound IWF is in PLOS state or when PLE packets are received
packets are received with the L bit set with the L bit set.
Note: Invalid 66B code blocks typically are a consequence of the CE- | Note: Invalid 66B code blocks typically are a consequence of
bound IWF inserting replacement data in case of lost PLE packets or | the CE-bound IWF inserting replacement data in case of lost PLE
the far-end PSN-bound NSP function not setting sync headers to 11 due | packets or the far-end PSN-bound NSP function not setting sync
to uncorrectable FEC errors. | headers to 11 due to uncorrectable FEC errors.
When sending the bit stream to the CE, the CE-bound NSP function MUST When sending the bit-stream to the CE, the CE-bound NSP function MUST
also perform: also perform:
* transcoding from 64B/66B to 256B/257B (Section 119.2.4.2 of * transcoding from 64B/66B to 256B/257B (Section 119.2.4.2 of
[IEEE802.3]) [IEEE802.3]),
* scrambling (Section 119.2.4.3 of [IEEE802.3]) * scrambling (Section 119.2.4.3 of [IEEE802.3]),
* alignment-marker insertion (Section 119.2.4.4 of [IEEE802.3]) * alignment-marker insertion (Section 119.2.4.4 of [IEEE802.3]),
* pre-FEC distribution (Section 119.2.4.5 of [IEEE802.3]) * pre-FEC distribution (Section 119.2.4.5 of [IEEE802.3]),
* FEC encoding (Section 119.2.4.6 of [IEEE802.3]) * FEC encoding (Section 119.2.4.6 of [IEEE802.3]), and
* PCS Lane distribution (Section 119.2.4.8 of [IEEE802.3]) * PCS lane distribution (Section 119.2.4.8 of [IEEE802.3]).
4.2.5. Energy Efficient Ethernet (EEE) 4.2.5. Energy Efficient Ethernet (EEE)
Section 78 of [IEEE802.3] defines the optional Low Power Idle (LPI) Section 78 of [IEEE802.3] defines the optional LPI capability for
capability for Ethernet. Two modes are defined: Ethernet. Two modes are defined:
* deep sleep * deep sleep
* fast wake * fast wake
Deep sleep mode is not compatible with PLE due to the CE ceasing Deep sleep mode is not compatible with PLE due to the CE ceasing
transmission. Hence, there is no support for LPI for 10GBASE-R transmission. Hence, there is no support for LPI for 10GBASE-R
services across PLE. services across PLE.
In fast wake mode, the CE transmits /LI/ control code blocks instead In fast wake mode, the CE transmits /LI/ control code blocks instead
of /I/ control code blocks and, therefore, PLE is agnostic to it. of /I/ control code blocks and, therefore, PLE is agnostic to it.
For 25GBASE-R and higher services across PLE, LPI is supported as For 25GBASE-R and higher services across PLE, LPI is supported as
only fast wake mode is applicable. only fast wake mode is applicable.
4.3. SONET/SDH Services 4.3. SONET/SDH Services
SONET/SDH services are special cases of the structured bit stream SONET/SDH services are special cases of the structured bit-stream
defined in Section 3.3.4 of [RFC3985]. defined in Section 3.3.4 of [RFC3985].
SDH interfaces are defined in [G.707]; SONET interfaces are defined SDH interfaces are defined in [G.707]; SONET interfaces are defined
in [GR253]. in [GR253].
The PSN-bound NSP function does not modify the received data but is The PSN-bound NSP function does not modify the received data but is
responsible for detecting attachment circuit faults specific to responsible for detecting attachment circuit faults specific to
SONET/SDH such as LOS, LOF, and OOF. SONET/SDH such as LOS, LOF, and OOF.
Data received by the PSN-bound IWF is mapped into the basic PLE Data received by the PSN-bound IWF is mapped into the basic PLE
payload without any awareness of SONET/SDH frames. payload without any awareness of SONET/SDH frames.
When the CE-bound IWF is in PLOS state or when PLE packets are When the CE-bound IWF is in PLOS state or when PLE packets are
received with the L bit set, the CE-bound NSP function is responsible received with the L bit set, the CE-bound NSP function is responsible
for generating the: for generating the:
* MS-AIS maintenance signal (defined in Section 6.2.4.1.1 of * MS-AIS maintenance signal (defined in Section 6.2.4.1.1 of
[G.707]) for SDH services [G.707]) for SDH services and
* AIS-L maintenance signal (defined in Section 6.2.1.2 of [GR253]) * AIS-L maintenance signal (defined in Section 6.2.1.2 of [GR253])
for SONET services for SONET services
at client-frame boundaries. at client-frame boundaries.
4.4. Fibre Channel Services 4.4. Fibre Channel Services
Fibre Channel services are special cases of the structured bit stream Fibre Channel services are special cases of the structured bit-stream
defined in Section 3.3.4 of [RFC3985]. defined in Section 3.3.4 of [RFC3985].
The T11 technical committee of INCITS has defined several layers for The T11 technical committee of INCITS has defined several layers for
Fibre Channel. PLE operates at the FC-1 layer that leverages Fibre Channel. PLE operates at the FC-1 layer that leverages
mechanisms defined by [IEEE802.3]. mechanisms defined by [IEEE802.3].
Over time, many different Fibre Channel interface types have been Over time, many different Fibre Channel interface types have been
specified with a varying set of characteristics such as optional specified with a varying set of characteristics such as optional
versus mandatory FEC and single-lane versus multi-lane transmission. versus mandatory FEC and single-lane versus multi-lane transmission.
skipping to change at line 690 skipping to change at line 690
circuit faults specific to the Fibre Channel such as LOS and sync circuit faults specific to the Fibre Channel such as LOS and sync
loss. loss.
The PSN-bound IWF maps the received 8B/10B code stream as is directly The PSN-bound IWF maps the received 8B/10B code stream as is directly
into the basic PLE payload. into the basic PLE payload.
The CE-bound NSP function MUST perform transmission word sync in The CE-bound NSP function MUST perform transmission word sync in
order to properly: order to properly:
* replace invalid transmission words with the special character * replace invalid transmission words with the special character
K30.7 K30.7 and
* insert Not Operational (NOS) ordered sets when the CE-bound IWF is * insert NOS ordered sets when the CE-bound IWF is in PLOS state or
in PLOS state or when PLE packets are received with the L bit set when PLE packets are received with the L bit set.
Note: Invalid transmission words typically are a consequence of the | Note: Invalid transmission words typically are a consequence of
CE-bound IWF inserting replacement data in case of lost PLE packets. | the CE-bound IWF inserting replacement data in case of lost PLE
| packets.
[FC-PI-5am1] defines the use of scrambling for 8GFC; in this case, [FC-PI-5am1] defines the use of scrambling for 8GFC; in this case,
the CE-bound NSP MUST also perform descrambling before replacing the CE-bound NSP MUST also perform descrambling before replacing
invalid transmission words or inserting NOS ordered sets. Before invalid transmission words or inserting NOS ordered sets. Before
sending the bit stream to the CE, the CE-bound NSP function MUST sending the bit-stream to the CE, the CE-bound NSP function MUST
scramble the 8B/10B code stream. scramble the 8B/10B code stream.
4.4.2. 16GFC 4.4.2. 16GFC
[FC-PI-5] and [FC-PI-5am1] specify 16GFC and define an optional FEC [FC-PI-5] and [FC-PI-5am1] specify 16GFC and define an optional FEC
layer. layer.
If FEC is present, it must be indicated via transmitter training If FEC is present, it must be indicated via TTS when the attachment
signal (TTS) when the attachment circuit is brought up. Further, the circuit is brought up. Further, the PSN-bound NSP function MUST
PSN-bound NSP function MUST terminate the FEC and the CE-bound NSP terminate the FEC and the CE-bound NSP function must generate the
function must generate the FEC. FEC.
The PSN-bound NSP function is responsible for detecting attachment The PSN-bound NSP function is responsible for detecting attachment
circuit faults specific to the Fibre Channel such as LOS and sync circuit faults specific to the Fibre Channel such as LOS and sync
loss. loss.
The PSN-bound IWF maps the received scrambled 64B/66B code stream as The PSN-bound IWF maps the received scrambled 64B/66B code stream as
is into the basic PLE payload. is into the basic PLE payload.
The CE-bound NSP function MUST perform: The CE-bound NSP function MUST perform:
* transmission word sync (Section 49.2.13 of [IEEE802.3]) * transmission word sync (Section 49.2.13 of [IEEE802.3]) and
* descrambling (Section 49.2.10 of [IEEE802.3]) * descrambling (Section 49.2.10 of [IEEE802.3])
in order to properly: in order to properly:
* replace invalid transmission words with the error transmission * replace invalid transmission words with the error transmission
word 1Eh word 1Eh and
* insert Not Operational (NOS) ordered sets when the CE-bound IWF is * insert NOS ordered sets when the CE-bound IWF is in PLOS state or
in PLOS state or when PLE packets are received with the L bit set when PLE packets are received with the L bit set.
Note: Invalid transmission words typically are a consequence of the | Note: Invalid transmission words typically are a consequence of
CE-bound IWF inserting replacement data in case of lost PLE packets | the CE-bound IWF inserting replacement data in case of lost PLE
or the far-end PSN-bound NSP function not setting sync headers to 11 | packets or the far-end PSN-bound NSP function not setting sync
due to uncorrectable FEC errors. | headers to 11 due to uncorrectable FEC errors.
Before sending the bit stream to the CE, the CE-bound NSP function Before sending the bit-stream to the CE, the CE-bound NSP function
MUST also scramble the 64B/66B code stream (Section 49.2.6 of MUST also scramble the 64B/66B code stream (Section 49.2.6 of
[IEEE802.3]). [IEEE802.3]).
4.4.3. 32GFC and 4-Lane 128GFC 4.4.3. 32GFC and 4-Lane 128GFC
[FC-PI-6] specifies 32GFC and [FC-PI-6P] specifies 4-lane 128GFC, [FC-PI-6] specifies 32GFC and [FC-PI-6P] specifies 4-lane 128GFC,
both with FEC layer and TTS support being mandatory. both with FEC layer and TTS support being mandatory.
To gain access to the 64B/66B code stream the PSN-bound NSP further To gain access to the 64B/66B code stream the PSN-bound NSP further
MUST perform: MUST perform:
* descrambling (Section of 49.2.10 of [IEEE802.3]) * descrambling (Section of 49.2.10 of [IEEE802.3]),
* FEC decoding (Section 91.5.3.3 of [IEEE802.3]) * FEC decoding (Section 91.5.3.3 of [IEEE802.3]), and
* reverse transcoding from 256B/257B to 64B/66B (Section 119.2.5.7 * reverse transcoding from 256B/257B to 64B/66B (Section 119.2.5.7
of [IEEE802.3]) of [IEEE802.3]).
Further, the PSN-bound NSP MUST perform scrambling (Section 49.2.6 of Further, the PSN-bound NSP MUST perform scrambling (Section 49.2.6 of
[IEEE802.3]) before the PSN-bound IWF maps the same into the basic [IEEE802.3]) before the PSN-bound IWF maps the same into the basic
PLE payload. PLE payload.
The PSN-bound NSP function is also responsible for detecting The PSN-bound NSP function is also responsible for detecting
attachment circuit faults specific to the Fibre Channel such as LOS attachment circuit faults specific to the Fibre Channel such as LOS
and sync loss. and sync loss.
The CE-bound NSP function MUST perform: The CE-bound NSP function MUST perform:
* transmission word sync (Section 119.2.6.3 of [IEEE802.3]) * transmission word sync (Section 119.2.6.3 of [IEEE802.3]) and
* descrambling (Section 49.2.10 of [IEEE802.3]) * descrambling (Section 49.2.10 of [IEEE802.3])
in order to properly: in order to properly:
* replace invalid transmission words with the error transmission * replace invalid transmission words with the error transmission
word 1Eh word 1Eh and
* insert Not Operational (NOS) ordered sets when the CE-bound IWF is * insert NOS ordered sets when the CE-bound IWF is in PLOS state or
in PLOS state or when PLE packets are received with the L bit set when PLE packets are received with the L bit set.
Note: Invalid transmission words typically are a consequence of the | Note: Invalid transmission words typically are a consequence of
CE-bound IWF inserting replacement data in case of lost PLE packets | the CE-bound IWF inserting replacement data in case of lost PLE
or the far-end PSN-bound NSP function not setting sync headers to 11 | packets or the far-end PSN-bound NSP function not setting sync
due to uncorrectable FEC errors. | headers to 11 due to uncorrectable FEC errors.
When sending the bit stream to the CE, the CE-bound NSP function MUST When sending the bit-stream to the CE, the CE-bound NSP function MUST
also perform: also perform:
* transcoding from 64B/66B to 256B/257B (Section 119.2.4.2 of * transcoding from 64B/66B to 256B/257B (Section 119.2.4.2 of
[IEEE802.3]) [IEEE802.3]),
* FEC encoding (Section 91.5.2.7 of [IEEE802.3]) * FEC encoding (Section 91.5.2.7 of [IEEE802.3]), and
* scrambling (Section 49.2.6 of [IEEE802.3]) * scrambling (Section 49.2.6 of [IEEE802.3]).
4.4.4. 64GFC 4.4.4. 64GFC
[FC-PI-7] specifies 64GFC with a mandatory FEC layer. [FC-PI-7] specifies 64GFC with a mandatory FEC layer.
To gain access to the 64B/66B code stream, the PSN-bound NSP further To gain access to the 64B/66B code stream, the PSN-bound NSP further
MUST perform: MUST perform:
* alignment lock (Section 134.5.4 of [IEEE802.3] modified to single * alignment lock (Section 134.5.4 of [IEEE802.3] modified to single
FEC lane operation) FEC lane operation),
* FEC decoding (Section 134.5.3.3 of [IEEE802.3]) * FEC decoding (Section 134.5.3.3 of [IEEE802.3]),
* alignment-marker removal (Section 134.5.3.4 of [IEEE802.3]) * alignment-marker removal (Section 134.5.3.4 of [IEEE802.3]), and
* reverse transcoding from 256B/257B to 64B/66B (Section 91.5.3.5 of * reverse transcoding from 256B/257B to 64B/66B (Section 91.5.3.5 of
[IEEE802.3]) [IEEE802.3]).
Further, the PSN-bound NSP MUST perform scrambling (Section 49.2.6 of Further, the PSN-bound NSP MUST perform scrambling (Section 49.2.6 of
[IEEE802.3]) before the PSN-bound IWF maps the same into the basic [IEEE802.3]) before the PSN-bound IWF maps the same into the basic
PLE payload. PLE payload.
The PSN-bound NSP function is also responsible for detecting The PSN-bound NSP function is also responsible for detecting
attachment circuit faults specific to the Fibre Channel such as LOS attachment circuit faults specific to the Fibre Channel such as LOS
and sync loss. and sync loss.
The CE-bound NSP function MUST perform: The CE-bound NSP function MUST perform:
* transmission word sync (Section 49.2.13 of [IEEE802.3]) * transmission word sync (Section 49.2.13 of [IEEE802.3]) and
* descrambling (Section 49.2.10 of [IEEE802.3]) * descrambling (Section 49.2.10 of [IEEE802.3])
in order to properly: in order to properly:
* replace invalid transmission words with the error transmission * replace invalid transmission words with the error transmission
word 1Eh word 1Eh and
* insert Not Operational (NOS) ordered sets when the CE-bound IWF is * insert NOS ordered sets when the CE-bound IWF is in PLOS state or
in PLOS state or when PLE packets are received with the L bit set when PLE packets are received with the L bit set.
Note: Invalid transmission words typically are a consequence of the | Note: Invalid transmission words typically are a consequence of
CE-bound IWF inserting replacement data in case of lost PLE packets | the CE-bound IWF inserting replacement data in case of lost PLE
or the far-end PSN-bound NSP function not setting sync headers to 11 | packets or the far-end PSN-bound NSP function not setting sync
due to uncorrectable FEC errors. | headers to 11 due to uncorrectable FEC errors.
When sending the bit stream to the CE, the CE-bound NSP function MUST When sending the bit-stream to the CE, the CE-bound NSP function MUST
also perform: also perform:
* transcoding from 64B/66B to 256B/257B (Section 91.5.2.5 of * transcoding from 64B/66B to 256B/257B (Section 91.5.2.5 of
[IEEE802.3]) [IEEE802.3]),
* alignment-marker insertion (Section 134.5.2.6 of [IEEE802.3]) * alignment-marker insertion (Section 134.5.2.6 of [IEEE802.3]), and
* FEC encoding (Section 134.5.2.7 of [IEEE802.3]) * FEC encoding (Section 134.5.2.7 of [IEEE802.3]).
4.5. OTN Services 4.5. OTN Services
OTN services are special cases of the structured bit stream defined OTN services are special cases of the structured bit-stream defined
in Section 3.3.4 of [RFC3985]. in Section 3.3.4 of [RFC3985].
OTN interfaces are defined in [G.709]. OTN interfaces are defined in [G.709].
The PSN-bound NSP function MUST terminate the FEC and replace the The PSN-bound NSP function MUST terminate the FEC and replace the
OTUk overhead in row 1, columns 8-14 with an all-zeros pattern; this OTUk overhead in row 1, columns 8-14 with an all-zeros pattern; this
results in an extended ODUk frame as illustrated in Figure 3. The results in an extended ODUk frame as illustrated in Figure 3. The
frame alignment overhead (FA OH) in row 1, columns 1-7 is kept as it frame alignment overhead (FA OH) in row 1, columns 1-7 is kept as it
is. is.
skipping to change at line 906 skipping to change at line 907
+-------------------------------+ -+ +-------------------------------+ -+
| PSN and VPWS Demux | \ | PSN and VPWS Demux | \
| (MPLS/SRv6) | > PSN and VPWS | (MPLS/SRv6) | > PSN and VPWS
| | / Demux Headers | | / Demux Headers
+-------------------------------+ -+ +-------------------------------+ -+
| PLE Control Word | \ | PLE Control Word | \
+-------------------------------+ > PLE Header +-------------------------------+ > PLE Header
| RTP Header | / | RTP Header | /
+-------------------------------+ --+ +-------------------------------+ --+
| Bit Stream | \ | Bit-Stream | \
| Payload | > Payload | Payload | > Payload
| | / | | /
+-------------------------------+ --+ +-------------------------------+ --+
Figure 4: PLE Encapsulation Layer Figure 4: PLE Encapsulation Layer
5.1. PSN and VPWS Demultiplexing Headers 5.1. PSN and VPWS Demultiplexing Headers
This document does not suggest any specific technology be used for This document does not suggest any specific technology be used for
implementing the VPWS demultiplexing and PSN layers. implementing the VPWS demultiplexing and PSN layers.
The total size of a PLE packet for a specific PW MUST NOT exceed the The total size of a PLE packet for a specific PW MUST NOT exceed the
path MTU between the pair of PEs terminating this PW. path MTU between the pair of PEs terminating this PW.
When an MPLS PSN layer is used, a VPWS label provides the When an MPLS PSN layer is used, a VPWS label provides the
demultiplexing mechanism (as described in Section 5.4.2 of demultiplexing mechanism (as described in Section 5.4.2 of
[RFC3985]). The PSN tunnel can be a simple best-path Label Switched [RFC3985]). The PSN tunnel can be a simple best-path LSP established
Path (LSP) established using LDP (see [RFC5036]) or Segment Routing using LDP (see [RFC5036]) or Segment Routing (SR) (see [RFC8402]); or
(SR) (see [RFC8402]); or it can be a traffic-engineered LSP it can be a traffic-engineered LSP established using RSVP-TE (see
established using RSVP-TE (see [RFC3209]) or SR policies (see [RFC3209]) or SR policies (see [RFC9256]).
[RFC9256]).
When an SRv6 PSN layer is used, an SRv6 service Segment Identifier When an SRv6 PSN layer is used, an SRv6 service SID (as defined in
(SID) (as defined in [RFC8402]) provides the demultiplexing mechanism [RFC8402]) provides the demultiplexing mechanism and definitions of
and definitions of Section 6 of [RFC9252] apply. Both SRv6 service Section 6 of [RFC9252] apply. Both SRv6 service SIDs with the full
SIDs with the full IPv6 address format defined in [RFC8986] and IPv6 address format defined in [RFC8986] and compressed SIDs (C-SIDs)
compressed SIDs (C-SIDs) with the format defined in [RFC9800] can be with the format defined in [RFC9800] can be used.
used.
5.1.1. New SRv6 Behaviors 5.1.1. New SRv6 Behaviors
Two new encapsulation behaviors, H.Encaps.L1 and H.Encaps.L1.Red, are Two new encapsulation behaviors, H.Encaps.L1 and H.Encaps.L1.Red, are
defined in this document. The behavior procedures are applicable to defined in this document. The behavior procedures are applicable to
both SIDs and C-SIDs. both SIDs and C-SIDs.
The H.Encaps.L1 behavior encapsulates a frame received from an IWF in The H.Encaps.L1 behavior encapsulates a frame received from an IWF in
an IPv6 packet with a segment routing header (SRH). The received an IPv6 packet with a segment routing header (SRH). The received
frame becomes the payload of the new IPv6 packet. frame becomes the payload of the new IPv6 packet.
skipping to change at line 958 skipping to change at line 957
* The insertion of the SRH MAY be omitted per [RFC8986] when the * The insertion of the SRH MAY be omitted per [RFC8986] when the
SRv6 policy only contains one segment and there is no need to use SRv6 policy only contains one segment and there is no need to use
any flag, tag, or TLV. any flag, tag, or TLV.
The H.Encaps.L1.Red behavior is an optimization of the H.Encaps.L1 The H.Encaps.L1.Red behavior is an optimization of the H.Encaps.L1
behavior. behavior.
* H.Encaps.L1.Red reduces the length of the SRH by excluding the * H.Encaps.L1.Red reduces the length of the SRH by excluding the
first SID in the SRH. The first SID is only placed in the first SID in the SRH. The first SID is only placed in the
destination IPv6 address field. Destination Address field of the IPv6 header.
* The insertion of the SRH MAY be omitted per [RFC8986] when the * The insertion of the SRH MAY be omitted per [RFC8986] when the
SRv6 policy only contains one segment and there is no need to use SRv6 policy only contains one segment and there is no need to use
any flag, tag, or TLV. any flag, tag, or TLV.
Three new "Endpoint with decapsulation and bit-stream cross-connect" Three new "Endpoint with decapsulation and bit-stream cross-connect"
behaviors called "End.DX1", "End.DX1 with NEXT-CSID", and "End.DX1 behaviors called "End.DX1", "End.DX1 with NEXT-CSID", and "End.DX1
with REPLACE-CSID" are defined in this document. These new behaviors with REPLACE-CSID" are defined in this document. These new behaviors
are variants of End.DX2 defined in [RFC8986], and they all have the are variants of End.DX2 defined in [RFC8986], and they all have the
following procedures in common: following procedures in common:
skipping to change at line 1015 skipping to change at line 1014
0 1 2 3 0 1 2 3
0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1 0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
|0 0 0 0|L|R|RSV|FRG| LEN | Sequence number | |0 0 0 0|L|R|RSV|FRG| LEN | Sequence number |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
Figure 5: PLE Control Word Figure 5: PLE Control Word
The bits 0..3 of the first nibble are set to 0 to differentiate a The bits 0..3 of the first nibble are set to 0 to differentiate a
control word or Associated Channel Header (ACH) from an IP packet or control word or ACH from an IP packet or Ethernet frame. The first
Ethernet frame. The first nibble MUST be set to 0000b to indicate nibble MUST be set to 0000b to indicate that this header is a control
that this header is a control word as defined in Section 3 of word as defined in Section 3 of [RFC4385].
[RFC4385].
The other fields in the control word are used as defined below: The other fields in the control word are used as defined below:
L L:
Set by the PE to indicate that data carried in the payload is Set by the PE to indicate that data carried in the payload is
invalid due to an attachment circuit fault. The downstream PE invalid due to an attachment circuit fault. The downstream PE
MUST send appropriate replacement data. The NSP MAY inject an MUST send appropriate replacement data. The NSP MAY inject an
appropriate native fault propagation signal. appropriate specific fault propagation signal.
R R:
Set by the downstream PE to indicate that the IWF experiences Set by the downstream PE to indicate that the IWF experiences
packet loss from the PSN or a server layer backward fault packet loss from the PSN or a server layer backward fault
indication is present in the NSP. The R bit MUST be cleared by indication is present in the NSP. The R bit MUST be cleared by
the PE once the packet loss state or fault indication has cleared. the PE once the packet loss state or fault indication has cleared.
RSV RSV:
These bits are reserved for future use. This field MUST be set to These bits are reserved for future use. This field MUST be set to
zero by the sender and ignored by the receiver. zero by the sender and ignored by the receiver.
FRG FRG:
These bits MUST be set to zero by the sender and ignored by the These bits MUST be set to zero by the sender and ignored by the
receiver as PLE does not use payload fragmentation. receiver as PLE does not use payload fragmentation.
LEN LEN:
In accordance with Section 3 of [RFC4385], the length field MUST In accordance with Section 3 of [RFC4385], the length field MUST
always be set to zero as there is no padding added to the PLE always be set to zero as there is no padding added to the PLE
packet. To detect malformed packets the default, preconfigured or packet. The preconfigured size of the PLE payload MUST be assumed
signaled payload size MUST be assumed. to be as described in Section 5.2; if the actual packet size is
inconsistent with this length, the packet MUST be considered
malformed. To detect malformed packets the default, preconfigured
or signaled payload size MUST be assumed.
Sequence number Sequence number:
The sequence number field is used to provide a common PW The sequence number field is used to provide a common PW
sequencing function as well as detection of lost packets. It MUST sequencing function as well as detection of lost packets. It MUST
be generated in accordance with the rules defined in Section 5.1 be generated in accordance with the rules defined in Section 5.1
of [RFC3550] and MUST be incremented with every PLE packet being of [RFC3550] and MUST be incremented with every PLE packet being
sent. sent.
5.2.2. RTP Header 5.2.2. RTP Header
The RTP header MUST be included to explicitly convey timing The RTP header MUST be included to explicitly convey timing
information. information.
The RTP header (as defined in [RFC3550]) is reused to align with The RTP header (as defined in [RFC3550]) is reused to align with
other bit-stream emulation pseudowires defined by [RFC4553], other bit-stream emulation pseudowires defined by [RFC4553],
[RFC5086], and [RFC4842] and to allow PLE implementations to reuse [RFC5086], and [RFC4842] and to allow PLE implementations to reuse
preexisting work. preexisting work.
There is no intention to support full RTP topologies and protocol There is no intention to support full RTP topologies and protocol
mechanisms, such as header extensions, contributing source (CSRC) mechanisms, such as header extensions, contributing source (CSRC)
list, padding, RTP Control Protocol (RTCP), RTP header compression, list, padding, RTCP, RTP header compression, SRTP, etc., as these are
Secure Real-time Transport Protocol (SRTP), etc., as these are not not applicable to PLE VPWS.
applicable to PLE VPWS.
The format of the RTP header is as shown in Figure 6. The format of the RTP header is as shown in Figure 6.
0 1 2 3 0 1 2 3
0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1 0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
|V=2|P|X| CC |M| PT | Sequence Number | |V=2|P|X| CC |M| PT | Sequence Number |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| Timestamp | | Timestamp |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
skipping to change at line 1118 skipping to change at line 1118
Marker Marker
The M bit MUST be set to zero by the sender and ignored by the The M bit MUST be set to zero by the sender and ignored by the
receiver. receiver.
PT: PT:
Payload type Payload type
A PT value MUST be allocated from the range of dynamic values A PT value MUST be allocated from the range of dynamic values
defined in Section 6 of [RFC3551] for each direction of the VPWS. defined in Section 6 of [RFC3551] for each direction of the VPWS.
The same PT value MAY be reused both for direction and between The same PT value MAY be reused for both for directions and
different PLE VPWS. between different PLE VPWSs.
The PT field MAY be used for detection of misconnections. The PT field MAY be used for detection of misconnections.
Sequence number Sequence number:
When using a 16-bit sequence number space, the sequence number in When using a 16-bit sequence number space, the sequence number in
the RTP header MUST be equal to the sequence number in the PLE the RTP header MUST be equal to the sequence number in the PLE
control word. When using a sequence number space of 32 bits, the control word. When using a sequence number space of 32 bits, the
initial value of the RTP sequence number MUST be 0 and incremented initial value of the RTP sequence number MUST be 0 and incremented
whenever the PLE control word sequence number cycles through from whenever the PLE control word sequence number cycles through from
0xFFFF to 0x0000. 0xFFFF to 0x0000.
Timestamp Timestamp:
Timestamp values are used in accordance with the rules established Timestamp values are used in accordance with the rules established
in [RFC3550]. For bit-streams up to 200 Gbps, the frequency of in [RFC3550]. For bit-streams up to 200 Gbps, the frequency of
the clock used for generating timestamps MUST be 125 MHz based on the clock used for generating timestamps MUST be 125 MHz based on
a the common clock I. For bit-streams above 200 Gbps, the a the common clock I. For bit-streams above 200 Gbps, the
frequency MUST be 250 MHz. frequency MUST be 250 MHz.
SSRC: SSRC:
Synchronization source Synchronization source
The SSRC field MAY be used for detection of misconnections. The SSRC field MAY be used for detection of misconnections.
skipping to change at line 1197 skipping to change at line 1197
[LDP-PLE]. [LDP-PLE].
7.2. PLE IWF Operation 7.2. PLE IWF Operation
7.2.1. PSN-Bound Encapsulation Behavior 7.2.1. PSN-Bound Encapsulation Behavior
After the VPWS is set up, the PSN-bound IWF performs the following After the VPWS is set up, the PSN-bound IWF performs the following
steps: steps:
* Packetize the data received from the CE into PLE payloads, all of * Packetize the data received from the CE into PLE payloads, all of
the same configured size the same configured size,
* Add PLE control word and RTP header with sequence numbers, flags, * Add PLE control word and RTP header with sequence numbers, flags,
and timestamps properly set and timestamps properly set,
* Add the VPWS demultiplexer and PSN headers * Add the VPWS demultiplexer and PSN headers,
* Transmit the resulting packets over the PSN * Transmit the resulting packets over the PSN,
* Set the L bit in the PLE control word whenever the attachment * Set the L bit in the PLE control word whenever the attachment
circuit detects a fault circuit detects a fault, and
* Set the R bit in the PLE control word whenever the local CE-bound * Set the R bit in the PLE control word whenever the local CE-bound
IWF is in packet loss state IWF is in packet loss state.
7.2.2. CE-Bound Decapsulation Behavior 7.2.2. CE-Bound Decapsulation Behavior
The CE-bound IWF is responsible for removing the PSN and VPWS The CE-bound IWF is responsible for removing the PSN and VPWS
demultiplexing headers, PLE control word, and RTP header from the demultiplexing headers, PLE control word, and RTP header from the
received packet stream and sending the bit-stream out via the local received packet stream and sending the bit-stream out via the local
attachment circuit. attachment circuit.
A de-jitter buffer MUST be implemented where the PLE packets are A de-jitter buffer MUST be implemented where the PLE packets are
stored upon arrival. The size of this buffer SHOULD be locally stored upon arrival. The size of this buffer SHOULD be locally
configurable to allow accommodation of specific PSN packet delay configurable to allow accommodation of specific PSN PDV expected.
variation (PDV) expected.
The CE-bound IWF SHOULD use the sequence number in the control word The CE-bound IWF SHOULD use the sequence number in the control word
to detect lost and misordered packets. It MAY use the sequence to detect lost and misordered packets. It MAY use the sequence
number in the RTP header for the same purpose. The CE-bound IWF MAY number in the RTP header for the same purpose. The CE-bound IWF MAY
support reordering of packets received out of order. If the CE-bound support reordering of packets received out of order. If the CE-bound
IWF does not support reordering, it MUST drop the misordered packets. IWF does not support reordering, it MUST drop the misordered packets.
The payload of a lost or dropped packet MUST be replaced with an The payload of a lost or dropped packet MUST be replaced with an
equivalent amount of replacement data. The contents of the equivalent amount of replacement data. The contents of the
replacement data MAY be locally configurable. By default, all PLE replacement data MAY be locally configurable. By default, all PLE
implementations MUST support generation of "0xAA" as replacement implementations MUST support generation of "0xAA" as replacement
data. The alternating sequence of 0s and 1s of the "0xAA" pattern data. The alternating sequence of 0s and 1s of the "0xAA" pattern
ensures clock synchronization is maintained and, for 64B/66B code- ensures clock synchronization is maintained and, for 64B/66B code-
based services, ensures no invalid sync headers are generated. While based services, ensures no invalid sync headers are generated. While
sending out the replacement data, the IWF will apply a holdover sending out the replacement data, the IWF will apply a holdover
mechanism to maintain the clock. mechanism to maintain the clock.
Whenever the VPWS is not operationally up, the CE-bound NSP function Whenever the VPWS is not operationally up, the CE-bound NSP function
MUST inject the appropriate native downstream fault-indication MUST inject the appropriate specific downstream fault-indication
signal. signal.
Whenever a VPWS comes up, the CE-bound IWF will enter the Whenever a VPWS comes up, the CE-bound IWF will enter the
intermediate state, will start receiving PLE packets, and will store intermediate state, will start receiving PLE packets, and will store
them in the jitter buffer. The CE-bound NSP function will continue them in the jitter buffer. The CE-bound NSP function will continue
to inject the appropriate native downstream fault-indication signal to inject the appropriate specific downstream fault-indication signal
until a preconfigured number of payload s stored in the jitter until a preconfigured number of payload s stored in the jitter
buffer. buffer.
After the preconfigured amount of payload is present in the jitter After the preconfigured amount of payload is present in the jitter
buffer, the CE-bound IWF transitions to the normal operation state, buffer, the CE-bound IWF transitions to the normal operation state,
and the content of the jitter buffer is streamed out to the CE in and the content of the jitter buffer is streamed out to the CE in
accordance with the required clock. In this state, the CE-bound IWF accordance with the required clock. In this state, the CE-bound IWF
MUST perform egress clock recovery. MUST perform egress clock recovery.
Considerations for choosing the preconfigured amount of payload Considerations for choosing the preconfigured amount of payload
skipping to change at line 1280 skipping to change at line 1279
* [G.825], [G.783], and [G.823] for SDH * [G.825], [G.783], and [G.823] for SDH
* [GR253] and [GR499] for SONET * [GR253] and [GR499] for SONET
* [G.8261] for synchronous Ethernet * [G.8261] for synchronous Ethernet
* [G.8251] for OTN * [G.8251] for OTN
Whenever the L bit is set in the PLE control word of a received PLE Whenever the L bit is set in the PLE control word of a received PLE
packet, the CE-bound NSP function SHOULD inject the appropriate packet, the CE-bound NSP function SHOULD inject the appropriate
native downstream fault-indication signal instead of streaming out specific downstream fault-indication signal instead of streaming out
the payload. the payload.
If the CE-bound IWF detects loss of consecutive packets for a If the CE-bound IWF detects loss of consecutive packets for a
preconfigured amount of time (default is 1 millisecond), it enters preconfigured amount of time (default is 1 millisecond), it enters
packet loss (PLOS) state and a corresponding defect is declared. PLOS state and a corresponding defect is declared.
If the CE-bound IWF detects a packet loss ratio (PLR) above a If the CE-bound IWF detects a PLR above a configurable SD threshold
configurable signal-degrade (SD) threshold for a configurable amount for a configurable amount of consecutive 1-second intervals, it
of consecutive 1-second intervals, it enters the degradation (DEG) enters the DEG state and a corresponding defect is declared. The SD-
state and a corresponding defect is declared. The SD-PLR threshold PLR threshold can be defined as a percentage with the default being
can be defined as a percentage with the default being 15% or absolute 15% or absolute packet count for finer granularity for higher rate
packet count for finer granularity for higher rate interfaces. interfaces. Possible values for consecutive intervals are 2..10 with
Possible values for consecutive intervals are 2..10 with the default the default 7.
7.
While the PLOS defect is declared, the CE-bound NSP function MUST While the PLOS defect is declared, the CE-bound NSP function MUST
inject the appropriate native downstream fault-indication signal. If inject the appropriate specific downstream fault-indication signal.
the emulated service does not have an appropriate maintenance signal If the emulated service does not have an appropriate maintenance
defined, the CE-bound NSP function MAY disable its transmitter signal defined, the CE-bound NSP function MAY disable its transmitter
instead. Also, the PSN-bound IWF SHOULD set the R bit in the PLE instead. Also, the PSN-bound IWF SHOULD set the R bit in the PLE
control word of every packet transmitted. control word of every packet transmitted.
The CE-bound IWF changes from the PLOS to normal state after the The CE-bound IWF changes from the PLOS to normal state after the
preconfigured amount of payload has been received similar to the preconfigured amount of payload has been received similar to the
transition from intermediate to normal state. transition from intermediate to normal state.
Whenever the R bit is set in the PLE control word of a received PLE Whenever the R bit is set in the PLE control word of a received PLE
packet, the PLE performance monitoring statistics SHOULD get updated. packet, the PLE performance monitoring statistics SHOULD get updated.
skipping to change at line 1328 skipping to change at line 1326
operators. operators.
The near-end performance monitors defined for PLE are as follows: The near-end performance monitors defined for PLE are as follows:
* ES-PLE : PLE Errored Seconds * ES-PLE : PLE Errored Seconds
* SES-PLE : PLE Severely Errored Seconds * SES-PLE : PLE Severely Errored Seconds
* UAS-PLE : PLE Unavailable Seconds * UAS-PLE : PLE Unavailable Seconds
Each second with at least one packet lost or a PLOS/DEG defect SHALL Each second with at least one packet lost or a PLOS or DEG defect
be counted as an ES-PLE. Each second with a PLR greater than 15% or SHALL be counted as an ES-PLE. Each second with a PLR greater than
a PLOS/DEG defect SHALL be counted as an SES-PLE. 15% or a PLOS or DEG defect SHALL be counted as an SES-PLE.
UAS-PLE SHALL be counted after a configurable number of consecutive UAS-PLE SHALL be counted after a configurable number of consecutive
SES-PLEs have been observed, and no longer counted after a SES-PLEs have been observed, and no longer counted after a
configurable number of consecutive seconds without an SES-PLE have configurable number of consecutive seconds without an SES-PLE have
been observed. The default value for each is 10 seconds. been observed. The default value for each is 10 seconds.
Once unavailability is detected, ES and SES counts SHALL be inhibited Once unavailability is detected, ES-PLE and SES-PLE counts SHALL be
up to the point where the unavailability was started. Once inhibited up to the point where the unavailability was started. Once
unavailability is removed, ES and SES that occurred along the unavailability is removed, ES-PLE and SES-PLE that occurred along the
clearing period SHALL be added to the ES and SES counts. clearing period SHALL be added to the ES-PLE and SES-PLE counts.
A PLE far-end performance monitor provides insight into the CE-bound A PLE far-end performance monitor provides insight into the CE-bound
IWF at the far end of the PSN. The statistics are based on the PLE- IWF at the far end of the PSN. The statistics are based on the PLE-
RDI indication carried in the PLE control word via the R bit. RDI indication carried in the PLE control word via the R bit.
The PLE VPWS performance monitors are derived from the definitions in The PLE VPWS performance monitors are derived from the definitions in
accordance with [G.826]. accordance with [G.826].
Performance monitoring data MUST be provided by the management Performance monitoring data MUST be provided by the management
interface and SHOULD be provided by a YANG data model. The YANG data interface and SHOULD be provided by a YANG data model. The YANG data
skipping to change at line 1370 skipping to change at line 1368
Faults MUST be timestamped as they are declared and cleared; fault- Faults MUST be timestamped as they are declared and cleared; fault-
related information MUST be provided by the management interface and related information MUST be provided by the management interface and
SHOULD be provided by a YANG data model. The YANG data model SHOULD be provided by a YANG data model. The YANG data model
specification is out of scope for this document. specification is out of scope for this document.
8. QoS and Congestion Control 8. QoS and Congestion Control
The PSN carrying PLE VPWS may be subject to congestion. Congestion The PSN carrying PLE VPWS may be subject to congestion. Congestion
considerations for PWs are described in Section 6.5 of [RFC3985]. considerations for PWs are described in Section 6.5 of [RFC3985].
PLE VPWS represent inelastic constant bit-rate (CBR) flows that PLE VPWS represent inelastic CBR flows that cannot respond to
cannot respond to congestion in a TCP-friendly manner (as described congestion in a TCP-friendly manner (as described in [RFC2914]) and
in [RFC2914]) and are sensitive to jitter, packet loss, and packets are sensitive to jitter, packet loss, and packets received out of
received out of order. order.
The PSN providing connectivity between PE devices of a PLE VPWS has The PSN providing connectivity between PE devices of a PLE VPWS has
to ensure low jitter and low loss. The exact mechanisms used are to ensure low jitter and low loss. The exact mechanisms used are
beyond the scope of this document and may evolve over time. Possible beyond the scope of this document and may evolve over time. Possible
options, but not exhaustively, are as follows options, but not exhaustively, are as follows:
* a Diffserv-enabled [RFC2475] PSN with a per-domain behavior (see * a Diffserv-enabled [RFC2475] PSN with a per-domain behavior (see
[RFC3086]) supporting Expedited Forwarding (see [RFC3246]), [RFC3086]) supporting Expedited Forwarding (see [RFC3246]),
* traffic-engineered paths through the PSN with bandwidth * traffic-engineered paths through the PSN with bandwidth
reservation and admission control applied, or reservation and admission control applied, or
* capacity over-provisioning. * capacity over-provisioning.
9. Security Considerations 9. Security Considerations
skipping to change at line 1422 skipping to change at line 1420
Misconnection detection using the SSRC and/or PT field of the RTP Misconnection detection using the SSRC and/or PT field of the RTP
header can increase the resilience to misconfiguration and some types header can increase the resilience to misconfiguration and some types
of denial-of-service (DoS) attacks. Randomly chosen expected values of denial-of-service (DoS) attacks. Randomly chosen expected values
decrease the chance of a spoofing attack being successful. decrease the chance of a spoofing attack being successful.
A data plane attack may force PLE packets to be dropped, reordered, A data plane attack may force PLE packets to be dropped, reordered,
or delayed beyond the limit of the CE-bound IWF's dejitter buffer or delayed beyond the limit of the CE-bound IWF's dejitter buffer
leading to either degradation or service disruption. Considerations leading to either degradation or service disruption. Considerations
outlined in [RFC9055] are a good reference. outlined in [RFC9055] are a good reference.
Clock synchronization leveraging PTP is sensitive to Packet Delay Clock synchronization leveraging PTP is sensitive to PDV and
Variation (PDV) and vulnerable to various threads and attack vectors. vulnerable to various threats and attack vectors. Considerations
Considerations outlined in [RFC7384] should be taken into account. outlined in [RFC7384] should be taken into account.
10. IANA Considerations 10. IANA Considerations
10.1. Bit-Stream Next Header Type 10.1. Bit-Stream Next Header Type
This document introduces a new value to be used in the next header This document introduces a new value to be used in the next header
field of an IPv6 header or any extension header indicating that the field of an IPv6 header or any extension header indicating that the
payload is an emulated bit-stream. IANA has assigned the following payload is an emulated bit-stream. IANA has assigned the following
from the "Assigned Internet Protocol Numbers" registry [IANA-Proto]. from the "Assigned Internet Protocol Numbers" registry [IANA-Proto].
skipping to change at line 1485 skipping to change at line 1483
[G.783] ITU-T, "Characteristics of synchronous digital hierarchy [G.783] ITU-T, "Characteristics of synchronous digital hierarchy
(SDH) equipment functional blocks", ITU-T (SDH) equipment functional blocks", ITU-T
Recommendation G.783, March 2006, Recommendation G.783, March 2006,
<https://www.itu.int/rec/T-REC-G.783>. <https://www.itu.int/rec/T-REC-G.783>.
[G.823] ITU-T, "The control of jitter and wander within digital [G.823] ITU-T, "The control of jitter and wander within digital
networks which are based on the 2048 kbit/s hierarchy", networks which are based on the 2048 kbit/s hierarchy",
ITU-T Recommendation G.823, March 2000, ITU-T Recommendation G.823, March 2000,
<https://www.itu.int/rec/T-REC-G.823>. <https://www.itu.int/rec/T-REC-G.823>.
[G.824] ITU-T, "The control of jitter and wander within digital
networks which are based on the 1544 kbits hierarchy",
ITU-T Recommendation G.824, March 2000,
<https://www.itu.int/rec/T-REC-G.824>.
[G.825] ITU-T, "The control of jitter and wander within digital [G.825] ITU-T, "The control of jitter and wander within digital
networks which are based on the synchronous digital networks which are based on the synchronous digital
hierarchy (SDH)", ITU-T Recommendation G.825, March 2000, hierarchy (SDH)", ITU-T Recommendation G.825, March 2000,
<https://www.itu.int/rec/T-REC-G.825>. <https://www.itu.int/rec/T-REC-G.825>.
[G.8251] ITU-T, "The control of jitter and wander within the [G.8251] ITU-T, "The control of jitter and wander within the
optical transport network (OTN)", ITU-T optical transport network (OTN)", ITU-T
Recommendation G.8251, November 2022, Recommendation G.8251, November 2022,
<https://www.itu.int/rec/T-REC-G.8251>. <https://www.itu.int/rec/T-REC-G.8251>.
skipping to change at line 1610 skipping to change at line 1603
signalling-02, 18 October 2024, signalling-02, 18 October 2024,
<https://datatracker.ietf.org/doc/html/draft-schmutzer- <https://datatracker.ietf.org/doc/html/draft-schmutzer-
bess-bitstream-vpws-signalling-02>. bess-bitstream-vpws-signalling-02>.
[FC-PI-2] INCITS, "Information Technology - Fibre Channel Physical [FC-PI-2] INCITS, "Information Technology - Fibre Channel Physical
Interfaces - 2 (FC-PI-2)", INCITS 404-2006 (S2016), 2016, Interfaces - 2 (FC-PI-2)", INCITS 404-2006 (S2016), 2016,
<https://webstore.ansi.org/standards/incits/ <https://webstore.ansi.org/standards/incits/
incits4042006s2016>. incits4042006s2016>.
[FC-PI-5] INCITS, "Information Technology - Fibre Channel - Physical [FC-PI-5] INCITS, "Information Technology - Fibre Channel - Physical
Interface-5 (FC-PI-5)", INCITS 479-2011, 2011, Interface-5 (FC-PI-5)", INCITS 479-2011 (S2021), 2021,
<https://webstore.ansi.org/standards/incits/ <https://webstore.ansi.org/standards/incits/
incits4792011>. incits4792011s2021>.
[FC-PI-5am1] [FC-PI-5am1]
INCITS, "Information Technology - Fibre Channel - Physical INCITS, "Information Technology - Fibre Channel - Physical
Interface - 5/Amendment 1 (FC-PI-5/AM1)", Interface - 5/Amendment 1 (FC-PI-5/AM1)",
INCITS 479-2011/AM1-2016, 2016, INCITS 479-2011/AM1-2016 (R2021), 2021,
<https://webstore.ansi.org/standards/incits/ <https://webstore.ansi.org/standards/incits/
incits4792011am12016>. incits4792011am2016r2021>.
[FC-PI-6] INCITS, "Information Technology - Fibre Channel - Physical [FC-PI-6] INCITS, "Information Technology - Fibre Channel - Physical
Interface - 6 (FC-PI-6)", INCITS 512-2015, 2015, Interface - 6 (FC-PI-6)", INCITS 512-2015 (R2020), 2020,
<https://webstore.ansi.org/standards/incits/ <https://webstore.ansi.org/standards/incits/
incits5122015>. incits5122015r2020>.
[FC-PI-6P] INCITS, "Information Technology - Fibre Channel - Physical [FC-PI-6P] INCITS, "Information Technology - Fibre Channel - Physical
Interface - 6P (FC-PI-6P)", INCITS 533-2016, 2016, Interface - 6P (FC-PI-6P)", INCITS 533-2016 (R2021), 2021,
<https://webstore.ansi.org/standards/incits/ <https://webstore.ansi.org/standards/incits/
incits5332016>. incits5332016r2021>.
[FC-PI-7] ISO/IEC, "Information technology – Fibre channel - Part [FC-PI-7] ISO/IEC, "Information technology – Fibre channel - Part
147: Physical interfaces - 7 (FC-PI-7)", ISO/ 147: Physical interfaces - 7 (FC-PI-7)", ISO/
IEC 14165-147:2021, 2021, IEC 14165-147:2021, 2021,
<https://www.iso.org/standard/80933.html>. <https://www.iso.org/standard/80933.html>.
[G.826] ITU-T, "End-to-end error performance parameters and [G.826] ITU-T, "End-to-end error performance parameters and
objectives for international, constant bit-rate digital objectives for international, constant bit-rate digital
paths and connections", ITU-T Recommendation G.826, paths and connections", ITU-T Recommendation G.826,
December 2002, <https://www.itu.int/rec/T-REC-G.826>. December 2002, <https://www.itu.int/rec/T-REC-G.826>.
skipping to change at line 1713 skipping to change at line 1706
[RFC4448] Martini, L., Ed., Rosen, E., El-Aawar, N., and G. Heron, [RFC4448] Martini, L., Ed., Rosen, E., El-Aawar, N., and G. Heron,
"Encapsulation Methods for Transport of Ethernet over MPLS "Encapsulation Methods for Transport of Ethernet over MPLS
Networks", RFC 4448, DOI 10.17487/RFC4448, April 2006, Networks", RFC 4448, DOI 10.17487/RFC4448, April 2006,
<https://www.rfc-editor.org/info/rfc4448>. <https://www.rfc-editor.org/info/rfc4448>.
[RFC4553] Vainshtein, A., Ed. and YJ. Stein, Ed., "Structure- [RFC4553] Vainshtein, A., Ed. and YJ. Stein, Ed., "Structure-
Agnostic Time Division Multiplexing (TDM) over Packet Agnostic Time Division Multiplexing (TDM) over Packet
(SAToP)", RFC 4553, DOI 10.17487/RFC4553, June 2006, (SAToP)", RFC 4553, DOI 10.17487/RFC4553, June 2006,
<https://www.rfc-editor.org/info/rfc4553>. <https://www.rfc-editor.org/info/rfc4553>.
[RFC4664] Andersson, L., Ed. and E. Rosen, Ed., "Framework for Layer
2 Virtual Private Networks (L2VPNs)", RFC 4664,
DOI 10.17487/RFC4664, September 2006,
<https://www.rfc-editor.org/info/rfc4664>.
[RFC4842] Malis, A., Pate, P., Cohen, R., Ed., and D. Zelig, [RFC4842] Malis, A., Pate, P., Cohen, R., Ed., and D. Zelig,
"Synchronous Optical Network/Synchronous Digital Hierarchy "Synchronous Optical Network/Synchronous Digital Hierarchy
(SONET/SDH) Circuit Emulation over Packet (CEP)", (SONET/SDH) Circuit Emulation over Packet (CEP)",
RFC 4842, DOI 10.17487/RFC4842, April 2007, RFC 4842, DOI 10.17487/RFC4842, April 2007,
<https://www.rfc-editor.org/info/rfc4842>. <https://www.rfc-editor.org/info/rfc4842>.
[RFC4875] Aggarwal, R., Ed., Papadimitriou, D., Ed., and S. [RFC4875] Aggarwal, R., Ed., Papadimitriou, D., Ed., and S.
Yasukawa, Ed., "Extensions to Resource Reservation Yasukawa, Ed., "Extensions to Resource Reservation
Protocol - Traffic Engineering (RSVP-TE) for Point-to- Protocol - Traffic Engineering (RSVP-TE) for Point-to-
Multipoint TE Label Switched Paths (LSPs)", RFC 4875, Multipoint TE Label Switched Paths (LSPs)", RFC 4875,
 End of changes. 138 change blocks. 
228 lines changed or deleted 226 lines changed or added

This html diff was produced by rfcdiff 1.48.