Skip to content

Objective BRSKI_JP not formally defined and name is confusing #60

@EskoDijk

Description

@EskoDijk

Problem with BRSKI_JP: it's used in an example as GRASP objective, but not formally introduced.

Also the name is a problem: it sounds like a Join Proxy advertising itself as a Join Proxy to Pledges. But that's not the case: the document says it's used by a Registrar to advertise its CoAPS (CoAP-over-DTLS) service. So to stay consistent with earlier and other work we should use e.g.

BRSKI_REG (given that BRSKI_REGISTRAR would be quite long)

Also this fits with the name

BRSKI_RJP

which can be interpreted as "BRSKI Registrar Join Proxy protocol". This is the special access protocol that uses a CBOR element.

Metadata

Metadata

Assignees

No one assigned

    Labels

    futureAny topic that is postponed to a new draft/document or a future version

    Type

    No type

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions