rfc9801v2.txt | rfc9801.txt | |||
---|---|---|---|---|
skipping to change at line 177 ¶ | skipping to change at line 177 ¶ | |||
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] | |||
CBR: Constant Bit Rate | CBR: Constant Bit Rate | |||
CE: Customer Edge | CE: Customer Edge | |||
CEP: Circuit Emulation over Packet [RFC4842] | CEP: Circuit Emulation over Packet [RFC4842] | |||
CSID: Compressed SID | ||||
CSRC: Contributing Source [RFC3550] | CSRC: Contributing Source [RFC3550] | |||
DEG: Degradation | DEG: Degradation | |||
ES: Errored Second | ES: Errored Second | |||
FEC: Forward Error Correction | FEC: Forward Error Correction | |||
ICMP: Internet Control Message Protocol [RFC4443] | ICMP: Internet Control Message Protocol [RFC4443] | |||
skipping to change at line 932 ¶ | skipping to change at line 934 ¶ | |||
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 LSP established | [RFC3985]). The PSN tunnel can be a simple best-path LSP established | |||
using LDP (see [RFC5036]) or Segment Routing (SR) (see [RFC8402]); or | using LDP (see [RFC5036]) or Segment Routing (SR) (see [RFC8402]); or | |||
it can be a traffic-engineered LSP established using RSVP-TE (see | it can be a traffic-engineered LSP established using RSVP-TE (see | |||
[RFC3209]) or SR policies (see [RFC9256]). | [RFC3209]) or SR policies (see [RFC9256]). | |||
When an SRv6 PSN layer is used, an SRv6 service SID (as defined in | When an SRv6 PSN layer is used, an SRv6 service SID (as defined in | |||
[RFC8402]) provides the demultiplexing mechanism and definitions of | [RFC8402]) provides the demultiplexing mechanism and definitions of | |||
Section 6 of [RFC9252] apply. Both SRv6 service SIDs with the full | Section 6 of [RFC9252] apply. Both SRv6 service SIDs with the full | |||
IPv6 address format defined in [RFC8986] and compressed SIDs (C-SIDs) | IPv6 address format defined in [RFC8986] and CSIDs with the format | |||
with the format defined in [RFC9800] can be used. | defined in [RFC9800] can be 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 CSIDs. | |||
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. | |||
* The next header field of the SRH or the last extension header | * The next header field of the SRH or the last extension header | |||
present MUST be set to 147. | present MUST be set to 147. | |||
* 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 | |||
skipping to change at line 1024 ¶ | skipping to change at line 1026 ¶ | |||
control word or ACH from an IP packet or Ethernet frame. The first | control word or ACH from an IP packet or Ethernet frame. The first | |||
nibble MUST be set to 0000b to indicate that this header is a control | nibble MUST be set to 0000b to indicate that this header is a control | |||
word as defined in Section 3 of [RFC4385]. | word as defined in Section 3 of [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 specific fault propagation signal. | appropriate fault-indication 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. The preconfigured size of the PLE payload MUST be assumed | packet. The size of the PLE payload MUST be assumed to be as | |||
to be as described in Section 5.2; if the actual packet size is | described in Section 6; if the actual packet size is inconsistent | |||
inconsistent with this length, the packet MUST be considered | with this, the packet MUST be considered malformed. | |||
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 | |||
skipping to change at line 1240 ¶ | skipping to change at line 1240 ¶ | |||
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 specific downstream fault-indication | MUST inject the appropriate 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 specific downstream fault-indication signal | to inject the appropriate downstream fault-indication signal until a | |||
until a preconfigured number of payload s stored in the jitter | 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 | |||
required to be present for transitioning into the normal state: | required to be present for transitioning into the normal state: | |||
skipping to change at line 1279 ¶ | skipping to change at line 1277 ¶ | |||
* [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 | |||
specific downstream fault-indication signal instead of streaming out | downstream fault-indication signal instead of streaming out the | |||
the payload. | 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 | |||
PLOS state and a corresponding defect is declared. | PLOS state and a corresponding defect is declared. | |||
If the CE-bound IWF detects a PLR above a configurable SD threshold | If the CE-bound IWF detects a PLR above a configurable SD threshold | |||
for a configurable amount of consecutive 1-second intervals, it | for a configurable amount of consecutive 1-second intervals, it | |||
enters the DEG state and a corresponding defect is declared. The SD- | enters the DEG state and a corresponding defect is declared. The SD- | |||
PLR threshold can be defined as a percentage with the default being | PLR threshold can be defined as a percentage with the default being | |||
15% or absolute packet count for finer granularity for higher rate | 15% or absolute packet count for finer granularity for higher rate | |||
interfaces. Possible values for consecutive intervals are 2..10 with | interfaces. Possible values for consecutive intervals are 2..10 with | |||
the default 7. | the default 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 specific downstream fault-indication signal. | inject the appropriate downstream fault-indication signal. If the | |||
If the emulated service does not have an appropriate maintenance | emulated service does not have an appropriate maintenance signal | |||
signal defined, the CE-bound NSP function MAY disable its transmitter | 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. | |||
End of changes. 9 change blocks. | ||||
19 lines changed or deleted | 17 lines changed or added | |||
This html diff was produced by rfcdiff 1.48. |