https://github.com/anima-wg/constrained-voucher/pull/272/files
Hi, we had some discussion on the list a few weeks ago about the lack of a
IANA registry for the GRASP AN_PROXY and AN_join_registrar objective's
objective-value.
RFC8994 defines AN_PROXY, and RFC8995 (section 4.4.1) uses it like:
[M_FLOOD, 12340815, h'fe800000000000000000000000000001', 180000,
[["AN_Proxy", 4, 1, ""<-OBJECTIVEVALUE],
[O_IPv6_LOCATOR,
h'fe800000000000000000000000000001', IPPROTO_TCP, 4443]]]
with:
objective-value = any ; none
and we were a bit imprecise that "none" meant empty string, rather than CBOR
null!
constrained-voucher (cBRSKI) needs to extend this value to include: "DTLS-EST"
while constrained-join-proxy uses it.
RFC8995 defines AN_join_registrar (section 4.3) as:
[M_FLOOD, 51804321, h'fda379a6f6ee00000200000064000001', 180000,
[["AN_join_registrar", 4, 255, "EST-TLS"],
[O_IPv6_LOCATOR,
h'fda379a6f6ee00000200000064000001', IPPROTO_TCP, 8443]]]
objective-value = text ; name of the supported protocol.
; e.g., "EST-TLS" for RFC 7030.
(after https://www.rfc-editor.org/errata/eid7576 is applied)
constrained-voucher (cBRSKI) needs to extend this value to include: "BRSKI_JP"
while constrained-join-proxy then extends this to include "BRSKI_RJP"
(see: https://github.com/anima-wg/constrained-join-proxy/pull/46 )
we also seem to have "CMP" as a value, which I think that brski-ae will need
to register, but which I don't think we do yet.
One thing that I'm unsure about is whether there should be additional
columns in the Registry. Specifically, we have changes in the $transport-proto
for both, which can vary from IPPROTO_TCP in RFC8995, to IPPROTO_UDP for the
coap methods. Should that be in the table too?
--
Michael Richardson <[email protected]> . o O ( IPv6 IøT consulting )
Sandelman Software Works Inc, Ottawa and Worldwide
signature.asc
Description: PGP signature
_______________________________________________ Anima mailing list [email protected] https://www.ietf.org/mailman/listinfo/anima
