This amendment specifies protocols, procedures, and managed objects for a Resource Allocation Protocol (RAP) that uses the Link-local Registration Protocol (LRP) and supports and provides backwards compatibility with the stream reservation and quality of service capabilities, controls and protocols specified in IEEE Std 802.1Q. RAP provides support for accurate latency calculation and reporting, can use redundant paths established by other protocols, and is not limited to bridged networks.
A signaling protocol that performs distributed and dynamic resource management and admission control is an essential component for automatic configuration in bridged LANs requiring latency and bandwidth guarantees. Current IEEE 802.1Q Multiple Stream Reservation Protocol (MSRP) is constrained by the capability of its underlying IEEE 802.1Q Multiple Registration Protocol (MRP) and does not efficiently support a large reservation database. For use in distributed stream reservation, IEEE 802.1Q MSRP does not make use of all available Quality of Service provisions and does not support reservation for the streams in need of high availability by use of the technologies specified in IEEE Std 802.1CB. The proposed amendment will address these issues.
|Status||2nd TG ballot|
|Current Draft||D0.2 (19 May 2020)|
|PAR & CSD||Full title: Standard for Local and Metropolitan Area Networks — Bridges and Bridged Networks — Amendment: Resource Allocation Protocol
PAR approved 27 Sep 2018;
|24 June 2020||802.1Qdd, Draft 0.2 final comment disposition|
|19 May 2020||802.1Qdd, Draft 0.2|
|3 Dec 2019||802.1Qdd, Draft 0.1 final comment disposition|
|21 Oct 2019||802.1Qdd, Draft 0.1|
|16 July 2019||802.1Qdd, Draft 0.0|
The above list includes only the latest version of (proposed) dispositions. See the project folder for a complete list). The dates listed are the website file dates; they may differ from the creation dates in the documents.
Contributions leading to RAP (and LRP)
The above list includes only the latest version of updated documents and omits those superseded by subsequent discussion or inclusion in the current draft (see filenames beginning “dd-” in the 2018 and 2019 public directories for a complete list). The dates listed are the website file dates; they may differ from the creation dates in the documents.
Please contact the Editor if you have comments to this page.