rewrite to remove JPY, changing encapsulation to straight CoAP #42
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
* bump version * make RFC6690 normative * remove installation terminology, as never used * make Registrar implement both, and Join Proxy prefer stateless * fix case of Join Proxy * fixed RFC9148 reference * fix! fix case of Join Proxy * remove comment about layer-2 security making encryption of token unnecessary * transform table into markdown table * mark examples as old * fix capitalizatin of Pledge * fix capitalizatin of CoAP * title of example to three servis * make RFC9032 informative * added text from TTE about ICMP errors and DoS protection * added root BRSKI response as suggested by Esko
|
Closing this for now - we keep the And in rev -14 and -15 the CoAP header idea was already dropped again. If needed we can always start up a new discussion if we want to make this change. |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
This commit reflects the discussion at the Oct 12 IoTOPS/CORE meeting about how to deal with the problems with how the JPY message discovery works.
A question was: why can't it just be CoAP, and no good answer returned, so this rewrite uses CoAP, exactly as RFC9031 does, but adds a second layer of CoAP header.