As far as I know, this is the last TRILL RFC. It was stuck for years
waiting on another document but has now popped through.

Thanks,
Donald
===============================
 Donald E. Eastlake 3rd   +1-508-333-2270 (cell)
 2386 Panoramic Circle, Apopka, FL 32703 USA
 [email protected]

On Fri, Aug 30, 2024 at 11:51 PM <[email protected]> wrote:

> A new Request for Comments is now available in online RFC libraries.
>
>
>         RFC 9600
>
>         Title:      TRansparent Interconnection of Lots of Links (TRILL):
>                     Explicit Congestion Notification (ECN) Support
>         Author:     D. Eastlake 3rd,
>                     B. Briscoe
>         Status:     Standards Track
>         Stream:     IETF
>         Date:       August 2024
>         Mailbox:    [email protected],
>                     [email protected]
>         Pages:      13
>         Updates/Obsoletes/SeeAlso:   None
>
>         I-D Tag:    draft-ietf-trill-ecn-support-07.txt
>
>         URL:        https://www.rfc-editor.org/info/rfc9600
>
>         DOI:        10.17487/RFC9600
>
> Explicit Congestion Notification (ECN) allows a forwarding element to
> notify downstream devices, including the destination, of the onset of
> congestion without having to drop packets. This can improve network
> efficiency through better congestion control without packet drops.
> This document extends ECN to TRansparent Interconnection of Lots of
> Links (TRILL) switches, including integration with IP ECN, and
> provides for ECN marking in the TRILL header extension flags word
> (RFC 7179).
>
> This document is a product of the Transparent Interconnection of Lots of
> Links Working Group of the IETF.
>
> This is now a Proposed Standard.
>
> STANDARDS TRACK: This document specifies an Internet Standards Track
> protocol for the Internet community, and requests discussion and
> suggestions
> for improvements.  Please refer to the current edition of the Official
> Internet Protocol Standards (https://www.rfc-editor.org/standards) for
> the
> standardization state and status of this protocol.  Distribution of this
> memo is unlimited.
>
> This announcement is sent to the IETF-Announce and rfc-dist lists.
> To subscribe or unsubscribe, see
>   https://www.ietf.org/mailman/listinfo/ietf-announce
>   https://mailman.rfc-editor.org/mailman/listinfo/rfc-dist
>
> For searching the RFC series, see https://www.rfc-editor.org/search
> For downloading RFCs, see https://www.rfc-editor.org/retrieve/bulk
>
> Requests for special distribution should be addressed to either the
> author of the RFC in question, or to [email protected].  Unless
> specifically noted otherwise on the RFC itself, all RFCs are for
> unlimited distribution.
>
>
> The RFC Editor Team
> Association Management Solutions, LLC
>
_______________________________________________
trill mailing list -- [email protected]
To unsubscribe send an email to [email protected]

Reply via email to