Subject: RFC 9650 on Revision to Registration Procedures for IS-IS Neighbor Link-Attribute Bit Values
From: [email-masked]
To: [email-masked], [email-masked]
Cc: [email-masked], [email-masked], [email-masked]
Date: Mon, 26 Aug 2024 23:12:05 -0700 (PDT)
List-Id: "IETF announcement list. No discussions." <ietf-announce.ietf.org>

A new Request for Comments is now available in online RFC libraries.

        RFC 9650

        Title:      Revision to Registration Procedures for 
                    IS-IS Neighbor Link-Attribute Bit Values 
        Author:     T. Li
        Status:     Standards Track
        Stream:     IETF
        Date:       August 2024
        Mailbox:    [email-masked]
        Pages:      3
        Updates:    RFC 5029

        I-D Tag:    draft-ietf-lsr-labv-registration-03.txt

        URL:        https://www.rfc-editor.org/info/rfc9650

        DOI:        10.17487/RFC9650

RFC 5029, "Definition of an IS-IS Link Attribute Sub-TLV", defines an
IANA registry called "IS-IS Neighbor Link-Attribute Bit Values". This
document changes the registration procedure for that registry from
"Standards Action" to "Expert Review". This document updates RFC
5029.

This document is a product of the Link State Routing 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-masked].  Unless
specifically noted otherwise on the RFC itself, all RFCs are for
unlimited distribution.

The RFC Editor Team
Association Management Solutions, LLC