The Application Specific Link Attribute (ASLA) Any Application Bit
draft-hegde-lsr-asla-any-app-02
Document | Type |
Expired Internet-Draft
(individual)
Expired & archived
|
|
---|---|---|---|
Authors | Shraddha Hegde , Ron Bonica , Chris Bowers , Robert Raszuk , Zhenbin Li , Daniel Voyer | ||
Last updated | 2023-01-12 (Latest revision 2022-07-11) | ||
RFC stream | (None) | ||
Intended RFC status | (None) | ||
Formats | |||
Stream | Stream state | (No stream defined) | |
Consensus boilerplate | Unknown | ||
RFC Editor Note | (None) | ||
IESG | IESG state | Expired | |
Telechat date | (None) | ||
Responsible AD | (None) | ||
Send notices to | (None) |
This Internet-Draft is no longer active. A copy of the expired Internet-Draft is available in these formats:
Abstract
RFC 8919 and RFC 8920 define Application Specific Link Attributes (ASLA). Each ASLA includes an Application Identifier Bit Mask. The Application Identifier Bit Mask includes a Standard Application Bit Mask (SABM) and a User Defined Application Bit Mask (UDABM). The SABM and UDABM determine which applications can use the ASLA as an input. This document introduces a new bit to the Standard Application Identifier Bit Mask. This bit is called the Any Application Bit (i.e., the A-bit). If the A-bit is set, the link attribute can be used by any application. This includes currently defined applications as well as applications to be defined in the future.
Authors
Shraddha Hegde
Ron Bonica
Chris Bowers
Robert Raszuk
Zhenbin Li
Daniel Voyer
(Note: The e-mail addresses provided for the authors of this Internet-Draft may no longer be valid.)