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

added IANA considerations, and incloude CMP in the example #46

Open
wants to merge 1 commit into
base: main
Choose a base branch
from

Conversation

mcr
Copy link
Member

@mcr mcr commented Aug 11, 2023

Added IANA considerations for objective values.

@mcr mcr requested review from EskoDijk and becarpenter August 11, 2023 21:04
@becarpenter
Copy link
Member

It looks OK but I am confused. Where are the "BRSKI AN_Proxy Objective Value" and "BRSKI AN_join_registrar Objective Value" registries defined? They don't seem to be in the posted version of draft-ietf-anima-constrained-voucher. Would they be added in the BRSKI section at https://www.iana.org/assignments/brski-parameters/brski-parameters.xhtml? If so there would need to be a cross-reference from https://www.iana.org/assignments/grasp-parameters/grasp-parameters.xhtml#objective-names

@mcr
Copy link
Member Author

mcr commented Aug 13, 2023

It looks OK but I am confused. Where are the "BRSKI AN_Proxy Objective Value" and "BRSKI AN_join_registrar Objective Value" registries defined? They don't seem to be in the posted version of draft-ietf-anima-constrained-voucher. Would they be added in the BRSKI section at https://www.iana.org/assignments/brski-parameters/brski-parameters.xhtml? If so there would need to be a cross-reference from https://www.iana.org/assignments/grasp-parameters/grasp-parameters.xhtml#objective-names

https://github.com/anima-wg/constrained-voucher/pull/272/files

@becarpenter
Copy link
Member

OK, that seems right. Thanks!

@EskoDijk
Copy link
Collaborator

Update: per the IETF 118 discussion, the GRASP related content was moved out from cBRSKI (= constrained-voucher) and I think this was equally proposed for constrained-join-proxy. So that would imply this PR needs to be updated/changed to reflect that.

@EskoDijk EskoDijk added the future Any topic that is postponed to a new draft/document or a future version label Jan 10, 2025
@EskoDijk
Copy link
Collaborator

Added label 'future' now, since the plan is to focus on a bare minimum of CoAP discovery as a solution and do the rest in BRSKI-discovery. Which could include GRASP as a method, in case cBRSKI is used in ANI context.

The latter is still a question though, whether cBRSKI is suitable for ANI context and whether anyone will be interested in using it there given that BRSKI was made for that use case. cBRSKI is more fitting to IoT networks for home/commercial where there's no separate network for ANI bootstrap, but the medium is shared control-traffic / application-traffic.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
future Any topic that is postponed to a new draft/document or a future version
Projects
None yet
Development

Successfully merging this pull request may close these issues.

3 participants