Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Conflicts with draft-ietf-dots-signal-channel #32

Open
OlliV opened this issue Mar 24, 2019 · 0 comments
Open

Conflicts with draft-ietf-dots-signal-channel #32

OlliV opened this issue Mar 24, 2019 · 0 comments

Comments

@OlliV
Copy link
Contributor

OlliV commented Mar 24, 2019

DOTS_protocol_specification_cheat_sheet.md refers to Content-Type option for CoAP while it should be called Content-Format. The content format is specified as application/cbor in the doc as well as in the source code but draft-ietf-dots-signal-channel specifies application/dots+cbor.

The URI-Path seems to be incorrect at least the cheat sheet as it specifies /.well-known/dots/v1/mitigate while the draft specifies /.well-known/dots/mitigate. The client code seems to be using the proper format but the server doesn't exactly verify it. By a quick look, it seems the server just looks if mitigate is defined in the URI, which isn't probably wrong as the draft mandates a certain order of options. To me it would sound reasonable to have versioned paths, too bad it's not currently allowed in the draft.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

1 participant