RFC Errata
Found 3 records.
Status: Verified (3)
RFC 8466, "A YANG Data Model for Layer 2 Virtual Private Network (L2VPN) Service Delivery", October 2018
Source of RFC: l2sm (ops)
Errata ID: 5615
Status: Verified
Type: Technical
Publication Format(s) : TEXT
Reported By: Nikolai Malykh
Date Reported: 2019-01-28
Verifier Name: Ignas Bagdonas
Date Verified: 2019-07-09
Section 5.10.1 says:
The svc-bandwidth parameter must include a "cos-id" parameter if the "type" is set to "bw-per-cos". The cos-id can be assigned based on either (1) the IEEE 802.1p value [IEEE-802-1D] in the C-tag or (2) the Differentiated Services Code Point (DSCP) in the Ethernet frame header. Service frames are metered against the bandwidth profile based on the cos-id.
It should say:
The svc-bandwidth parameter must include a "cos-id" parameter if the "type" is set to "bw-per-cos". The cos-id can be assigned based on either (1) the IEEE 802.1p value [IEEE-802-1D] in the C-tag or (2) the Differentiated Services Code Point (DSCP) in the IP header. Service frames are metered against the bandwidth profile based on the cos-id.
Notes:
The DSCP field is part of the IP packet header, not the Ethernet frame руфвук.
Errata ID: 6922
Status: Verified
Type: Technical
Publication Format(s) : TEXT
Reported By: Mohamed Boucadair
Date Reported: 2022-04-05
Verifier Name: Rob Wilton
Date Verified: 2023-10-02
Section 5.5.2.1 says:
... <network-access-id>LA1</network-access-id> <service> <svc-bandwidth> <bandwidth> <direction>input-bw</direction> <type>bw-per-cos</type> <cir>450000000</cir> <cbs>20000000</cbs> <eir>1000000000</eir> <ebs>200000000</ebs> </bandwidth> </svc-bandwidth> ... <network-access-id>LA2</network-access-id> <service> <svc-bandwidth> <bandwidth> <direction>input-bw</direction> <type>bw-per-cos</type> <cir>450000000</cir> <cbs>20000000</cbs> <eir>1000000000</eir> <ebs>200000000</ebs>
It should say:
... <network-access-id>LA1</network-access-id> <service> <svc-bandwidth> <bandwidth> <direction>input-bw</direction> <type>bw-per-cos</type> <cos-id>10</cos-id> <cir>450000000</cir> <cbs>20000000</cbs> <eir>1000000000</eir> <ebs>200000000</ebs> </bandwidth> </svc-bandwidth> ... <network-access-id>LA2</network-access-id> <service> <svc-bandwidth> <bandwidth> <direction>input-bw</direction> <type>bw-per-cos</type> <cos-id>10</cos-id> <cir>450000000</cir> <cbs>20000000</cbs> <eir>1000000000</eir> <ebs>200000000</ebs>
Notes:
The cos-id must be included when the bandwidth type is set to "bw-per-cos".
Errata ID: 6683
Status: Verified
Type: Editorial
Publication Format(s) : TEXT
Reported By: Mohamed Boucadair
Date Reported: 2021-09-14
Verifier Name: Robert Wilton
Date Verified: 2024-01-12
Section 5.10.2.1 says:
QoS classification rules are handled by "qos-classification-policy". qos-classification-policy is an ordered list of rules that match a flow or application and set the appropriate target CoS (target-class-id). The user can define the match using a more specific flow definition (based on Layer 2 source and destination MAC addresses, cos, dscp, cos-id, color-id, etc.). A "color-id" will be assigned to a service frame to identify its QoS profile conformance. A service frame is "green" if it is conformant with the "committed" rate of the bandwidth profile. A service frame is "yellow" if it exceeds the "committed" rate but is conformant with the "excess" rate of the bandwidth profile. Finally, a service frame is "red" if it is conformant with neither the "committed" rate nor the "excess" rate of the bandwidth profile.
It should say:
QoS classification rules are handled by "qos-classification-policy". qos-classification-policy is an ordered list of rules that match a flow or application and set the appropriate target CoS (target-class-id). The user can define the match using a more specific flow definition (based on Layer 2 source and destination MAC addresses, dscp, color-type, etc.). A "color-type" will be assigned to a service frame to identify its QoS profile conformance. A service frame is "green" if it is conformant with the "committed" rate of the bandwidth profile. A service frame is "yellow" if it exceeds the "committed" rate but is conformant with the "excess" rate of the bandwidth profile. Finally, a service frame is "red" if it is conformant with neither the "committed" rate nor the "excess" rate of the bandwidth profile.
Notes:
There is no "color-id" under "qos-classification-policy". The text should refer to "color-type" given that the "qos-classification-policy" substree is as follows:
+--rw service
| +--rw qos {qos}?
| | +--rw qos-classification-policy
| | | +--rw rule* [id]
| | | +--rw id string
| | | +--rw (match-type)?
| | | | +--:(match-flow)
| | | | | +--rw match-flow
| | | | | +--rw dscp? inet:dscp
| | | | | +--rw dot1q? uint16
| | | | | +--rw pcp? uint8
| | | | | +--rw src-mac? yang:mac-address
| | | | | +--rw dst-mac? yang:mac-address
| | | | | +--rw color-type? identityref
| | | | | +--rw target-sites*
| | | | | | svc-id {target-sites}?
| | | | | +--rw any? empty
| | | | | +--rw vpn-id? svc-id
| | | | +--:(match-application)
| | | | +--rw match-application? identityref
| | | +--rw target-class-id? string
The same applies for "cos" and "cos-id".
The corrected text uses "color-type" instead of "color-id" and removes "cos" and "cos-id" from the flow definition examples.