[core-parameters] [IANA #1229125] expert review for draft-ietf-anima-constrained-join-proxy (core-parameters)

[Amanda Baber via RT <[e-mail]>]

Hi Carsten, Jaime (cc: anima),

Can you approve the Resource Type (rt=) Link Target Attribute Values registrations in version -11 of this document?

https://datatracker.ietf.org/doc/html/draft-ietf-anima-constrained-join-proxy

thanks,
Amanda

On Thu Apr 07 21:44:01 2022, sabrina.tanamal wrote:
> Hi Carsten,
> 
> We have a response from the author:
> 
> Thanks for your reaction.
> Suggestion for new readable titles are below. I will insert them in
> the coming version 10 of the draft.
> 
> __________________________________________________________________
> OLD
>    Attribute Value: brski.jp
>    Description: This BRSKI resource type is used to query and return
> the
>                 supported BRSKI (CoAP over DTLS) port of the
> constrained
>                 Join Proxy.
>    Reference: [this document]
> 
> Attribute Value: brski.rjp
> Description: This BRSKI resource type is used to query and return the
>              supported BRSKI JPY protocol port of the Registrar.
> Reference: [this document]
> 
> NEW
> 
> Attribute Value: brski.jp
> Description: This BRSKI resource type is used to query and return the
>              supported BRSKI resources of the constrained Join Proxy.
> Reference: [this document]
> 
> Attribute Value: brski.rjp
> Description: This BRSKI resource type is used for the constrained Join
> Proxy
>              to query and return Join Proxy specific BRSKI resources
> of a Registrar.
> Reference: [this document]
> 
> ___________________________________________________________
> Hope this is understandable enough,
> 
> ====
> 
> Best regards,
> 
> Sabrina Tanamal
> Lead IANA Services Specialist
> 
> On Tue Apr 05 20:30:05 2022, [e-mail] wrote:
> > Hi Sabrina,
> >
> > I looked at the registration requests in the draft.
> > They use somewhat unusual language about discovering ports - resource
> > discovery is understood to discover resources.  For brski.jp, this
> > appears to be about discovering a CoAP or CoAPs entry point (without
> > describing how exactly that is then used, e.g., what happens if that
> > has a different IP address in the authority than the request
> > address).
> > For brski.rjp, this appears to be about discovering an entry point
> > for
> > a protocol that I don’t seem to fully understand the description for.
> >
> > I didn’t try to obtain a deep understanding of the protocol before
> > writing this, but I would prefer if the language used for the
> > description were understandable for other registrants in this
> > registry, i.e., discussing resources, not ports (port numbers?).
> >
> > All the other criteria for a registration appear to be fulfilled.
> >
> > I don’t think we need to reach a consensus between the designated
> > experts before proceeding.
> >
> > Grüße, Carsten
> >
> >
> > > On 2022-04-05, at 18:43, Sabrina Tanamal via RT <drafts-expert-
> > > [e-mail]> wrote:
> > >
> > > Carsten and Jaime (cc: anima WG),
> > >
> > > As the designated experts for the Resource Type (rt=) Link Target
> > > Attribute Values registry, can you review the proposed
> > > registrations
> > > in draft-ietf-anima-constrained-join-proxy for us? Please see
> > >
> > > https://datatracker.ietf.org/doc/draft-ietf-anima-constrained-join-
> > > proxy/
> > >
> > > If this is OK, when the IESG approves the document for publication,
> > > we'll make the registration at
> > >
> > > https://www.iana.org/assignments/core-parameters
> > >
> > > If you're the first expert to submit a review, please let us know
> > > whether you want us to wait for both reviewers to respond before we
> > > mark the document "IANA OK" (or send your comments to the authors,
> > > if
> > > the registrations aren't OK).
> > >
> > > The IESG has asked us to set a two-week deadline for registration
> > > reviews. The due date for this request is 19 April 2022.
> > >
> > > thanks,
> > >
> > > Sabrina Tanamal
> > > Lead IANA Services Specialist
> > >