Revision to Registration Procedures for IS-IS Neighbor Link-Attribute Bit Values

Status of This Memo

This Internet-Draft is submitted in full conformance with the provisions of BCP 78 and BCP 79.¶

Internet-Drafts are working documents of the Internet Engineering Task Force (IETF). Note that other groups may also distribute working documents as Internet-Drafts. The list of current Internet-Drafts is at https://datatracker.ietf.org/drafts/current/.¶

Internet-Drafts are draft documents valid for a maximum of six months and may be updated, replaced, or obsoleted by other documents at any time. It is inappropriate to use Internet-Drafts as reference material or to cite them other than as "work in progress."¶

This Internet-Draft will expire on 25 October 2024.¶

Copyright Notice

Copyright (c) 2024 IETF Trust and the persons identified as the document authors. All rights reserved.¶

This document is subject to BCP 78 and the IETF Trust's Legal Provisions Relating to IETF Documents (https://trustee.ietf.org/license-info) in effect on the date of publication of this document. Please review these documents carefully, as they describe your rights and restrictions with respect to this document. Code Components extracted from this document must include Revised BSD License text as described in Section 4.e of the Trust Legal Provisions and are provided without warranty as described in the Revised BSD License.¶

Table of Contents

1. Introduction

[RFC5029] defines the "IS-IS Neighbor Link-Attribute Bit Values" registry and specifies a registration procedure of "Standards Action". In practice, this registration procedure is unnecessarily restrictive, as it prevents allocation of bits to experimental protocols, which in turn increases the risk of conflicts introduced by use of unregistered code points (so-called "code point squatting").¶

Accordingly, this document changes the registration procedure for the registry, as described in Section 2.¶

2. IANA Considerations

The registration procedure for the "IS-IS Neighbor Link-Attribute Bit Values" registry is changed to be "Expert Review".¶

3. Security Considerations

This document does not affect the security issues discussed in RFC 5029.¶

4. Acknowledgements

The author would like to thank John Scudder for his contributions.¶

Author's Address