Thanks Dhruv!

On Thu, Mar 27, 2025 at 1:56 PM Dhruv Dhody <dhruv.i...@gmail.com> wrote:

> Hi,
>
> The erratum is correct and should be verified. Thanks Mrinmoy.
>
> Regards,
> Dhruv
>
> On Thu, Mar 27, 2025 at 12:37 PM RFC Errata System <
> rfc-edi...@rfc-editor.org> wrote:
>
>> The following errata report has been submitted for RFC5440,
>> "Path Computation Element (PCE) Communication Protocol (PCEP)".
>>
>> --------------------------------------
>> You may review the report below and at:
>> https://www.rfc-editor.org/errata/eid8349
>>
>> --------------------------------------
>> Type: Editorial
>> Reported by: Mrinmoy Das <mrinmoy.i...@gmail.com>
>>
>> Section: 7.14
>>
>> Original Text
>> -------------
>>          The OVERLOADED-DURATION TLV is compliant with the PCEP TLV
>>          format defined in Section 7.1 and is comprised of 2 bytes for
>>          the type, 2 bytes specifying the TLV length (length of the
>>          value portion in bytes), followed by a fixed-length value field
>>          of a 32-bit flags field.
>>
>>          Type:   2
>>          Length: 4 bytes
>>          Value:  32-bit flags field indicates the estimated PCE
>>                  congestion duration in seconds.
>>
>> Corrected Text
>> --------------
>>          The OVERLOADED-DURATION TLV is compliant with the PCEP TLV
>>          format defined in Section 7.1 and is comprised of 2 bytes for
>>          the type, 2 bytes specifying the TLV length (length of the
>>          value portion in bytes), followed by a fixed-length value field
>>          of 4 bytes.
>>
>>          Type:   2
>>          Length: 4 bytes
>>          Value:  4 bytes field indicates the estimated PCE
>>                  congestion duration in seconds.
>>
>> Notes
>> -----
>> TLV value field marked as 32-bit flags field which needs to be corrected
>> to 4 bytes field.
>>
>> Instructions:
>> -------------
>> This erratum is currently posted as "Reported". (If it is spam, it
>> will be removed shortly by the RFC Production Center.) Please
>> use "Reply All" to discuss whether it should be verified or
>> rejected. When a decision is reached, the verifying party
>> will log in to change the status and edit the report, if necessary.
>>
>> --------------------------------------
>> RFC5440 (draft-ietf-pce-pcep-19)
>> --------------------------------------
>> Title               : Path Computation Element (PCE) Communication
>> Protocol (PCEP)
>> Publication Date    : March 2009
>> Author(s)           : JP. Vasseur, Ed., JL. Le Roux, Ed.
>> Category            : PROPOSED STANDARD
>> Source              : Path Computation Element
>> Stream              : IETF
>> Verifying Party     : IESG
>>
>> _______________________________________________
>> Pce mailing list -- pce@ietf.org
>> To unsubscribe send an email to pce-le...@ietf.org
>>
>
_______________________________________________
Pce mailing list -- pce@ietf.org
To unsubscribe send an email to pce-le...@ietf.org

Reply via email to