This standard specifies protocols, procedures, and managed objects for a Link-local Registration Protocol (LRP) to replicate a registration database from one end to the other of a point-to-point link and to replicate changes to parts of that database. A facility is provided to purge the replicated database if the source becomes unresponsive. LRP is optimized for databases on the order of 1 Mbyte.
Link-local Registration Protocol is designed to facilitate the creation of application protocols that distribute information through all or part of a network.
Current “802.1Q Multiple Registration Protocol (MRP)” is optimized for databases up to 1500 bytes, and slows significantly when used for larger databases. There is a need to overcome this limitation in an efficient manner.
|Current Draft||D1.2 (December 2017)|
|PAR & CSD||Full title: Standard for Local and Metropolitan Area Networks — Link-local Registration Protocol
PAR approved 17 Feb 2017
|15 May 2017||802.1CS, Draft 0.0|
|12 Jul 2017||802.1CS, Draft 0.1|
|29 Jul 2017||802.1CS, Draft 1.0|
|06 Sep 2017||802.1CS, Draft 1.0 proposed comment dispositions v01|
|06 Sep 2017||802.1CS, Draft 1.0 proposed comment dispositions v02|
|11 Dec 2017||802.1CS. Draft 1.0 final comment disposition|
|06 Nov 2017||802.1CS. Draft 1.1|
|08 Dec 2017||802.1CS Draft 1.2|
|17 Jan 2017||Link-local Registration Protocol – Architecture and Transport Mechanism — Feng Chen|
|14 Mar 2017||Link Registry Protocol Options v1 — Norman Finn|
|14 Mar 2017||Link-local Registration Protocol – Database and Synchronization — Feng Chen|
|15 Mar 2017||Link Registry Protocol Options v2 — Norman Finn|
|16 May 2017||Link-local Registration Protocol – Thoughts on Options — Jürgen Schmitt|
|17 May 2017||LRP Draft 0 — Norman Finn|
|05 Sep 2017||Edge Control Transport for LRP v1 — Paul Bottorff|
|05 Sep 2017||Edge Control Transport for LRP v2 — Paul Bottorff|