Add bLIP 50: LSP Spec Transport Layer (LSPS0) #52
Conversation
tnull
force-pushed
the
2024-12-add-lsps0
branch
5 times, most recently
from
bcb9139 to
d905a83
Compare
tnull
force-pushed
the
2024-12-add-lsps0
branch
from
d905a83 to
24973c2
Compare
| > might not be directly contactable) was deemed unnecessary for | ||
| > most client-LSP communication needs. | ||
|
|
||
| All LSPS messages MUST use the [BOLT8][] message ID 37913 |
There was a problem hiding this comment.
This message ID must be reserved in bLIP 2.
There was a problem hiding this comment.
It is though? Is there anything else to be done besides adding it to the Messages table?
There was a problem hiding this comment.
No that's it, it looks like this is the only message you're using, and you've already registered the feature bit.
|
It would be useful to include a list of known implementations with a link to the code. |
Ah, cool, excuse the oversight!,I had overlooked that rule and simply looked for an empty namespace, while aligning the last number with the 'original' LSPS number to make it easier to remember. Thanks!
Will do! Note that |
Sounds good, let's merge with the new location right now then. |
I'll squash the fixup right now! |
The LSPS0 specification defines a protocol that is used for communcations between LSP nodes and their clients. To this end it utilizes a JSON-RPC format spoken over BOLT8 peer-to-peer messages. The given protocol has been previously stabilized by the LSP Spec group and is live in production with several LSP and client implementations today. As previously discussed on multiple occasions, the LSP Spec group is however moving to a bLIP-centric process, which is why we 'upstream' these previously-stabilized specifications here.
tnull
force-pushed
the
2024-12-add-lsps0
branch
from
8497273 to
4daf56a
Compare
The LSPS0 specification defines a protocol that is used for communcations between LSP nodes and their clients. To this end it utilizes a JSON-RPC format spoken over BOLT8 peer-to-peer messages.
The given protocol has been previously stabilized by the LSP Spec group and is live in production with several LSP and client implementations today.
As previously discussed on multiple occasions, the LSP Spec group is however moving to a bLIP-centric process, which is why we 'upstream' these previously-stabilized specifications here.
(cc the original author @ZmnSCPxj-jr)