Re: [Ace] [core] Early media-type registration for EST over CoAP

Since the registry that we are registering into does not fulfill the preconditions of RFC 7120 Section 2 point (a), I think the next step is to send the registration to IANA using the protocol parameters form [1].  The application should reference the I-D as well as the message from the DE [2] — there will be another interaction between IANA and DE and then we should be done.  To do so without further friction, the I-D probably should have been updated to align with [2].

[1]: https://www.iana.org/form/protocol-assignment
[2]: https://www.ietf.org/mail-archive/web/core-parameters/current/msg00024.html

Grüße, Carsten

> On Jun 19, 2018, at 11:40, Hannes Tschofenig <Hannes.Tschofenig@arm.com> wrote:
> 
> Peter,
> 
> Did this registration attempt got concluded?
> 
> Ciao
> Hannes
> 
> -----Original Message-----
> From: peter van der Stok [mailto:stokcons@xs4all.nl]
> Sent: 24 May 2018 15:55
> To: Carsten Bormann
> Cc: Hannes Tschofenig; core; ace@ietf.org
> Subject: Re: [core] [Ace] Early media-type registration for EST over CoAP
> 
> Ok, I will raise the experts to-morrow.
> 
> Peter
> 
> Carsten Bormann schreef op 2018-05-24 16:37:
>> On May 24, 2018, at 16:15, Hannes Tschofenig
>> <Hannes.Tschofenig@arm.com> wrote:
>>> 
>>> Hi all,
>>> 
>>> Trying to finalize this discussion: Could we do an early registry of
>>> the Content-Format numbers?
>> 
>> Yes.
>> 
>>> From the discussion so far I believe we concluded that the charset is
>>> utf-8
>> 
>> What charset?  I thought we don’t have parameters (see below).
>> 
>>> and that there are no parameters. Is that correct?
>> 
>> That is my understanding so far, but the point of me asking the
>> question was to ask the actual experts about these media types.  Did
>> we get that input?
>> 
>> Next step: make a proposal and raise this on core-parameters@ietf.org
>> so we get the needed input from the designated expert.
>> 
>> Grüße, Carsten
>> 
>> 
>>> 
>>> Ciao
>>> Hannes
>>> 
>>> From: Carsten Bormann [mailto:cabo@tzi.org]
>>> Sent: 16 May 2018 12:30
>>> To: Hannes Tschofenig
>>> Cc: ace@ietf.org; core
>>> Subject: Re: [Ace] Early media-type registration for EST over CoAP
>>> 
>>> Forgot to add another example: the content-format numbers for COSE
>>> have parameters.
>>> 
>>> Sent from mobile
>>> 
>>> On 16. May 2018, at 12:26, Carsten Bormann <cabo@tzi.org> wrote:
>>> 
>>> I was thinking about media type parameters such as charset="utf-8".
>>> The RT value need to be registered separately, but we can be a bit
>>> lazy about that.
>>> 
>>> Sent from mobile
>>> 
>>> On 16. May 2018, at 12:15, Hannes Tschofenig
>>> <Hannes.Tschofenig@arm.com> wrote:
>>> 
>>> Hi Carsten,
>>> 
>>> Yes, I am talking about the Content-Format numbers for them.
>>> Would rt="ace.est" be the parameter you are talking about?
>>> 
>>> Ciao
>>> Hannes
>>> 
>>> -----Original Message-----
>>> From: Carsten Bormann [mailto:cabo@tzi.org]
>>> Sent: 15 May 2018 11:45
>>> To: Hannes Tschofenig
>>> Cc: ace@ietf.org; core
>>> Subject: Re: [Ace] Early media-type registration for EST over CoAP
>>> 
>>> On May 15, 2018, at 10:56, Hannes Tschofenig
>>> <Hannes.Tschofenig@arm.com> wrote:
>>> 
>>> 
>>> I am curious whether it would be possible to ask for early media-type
>>> registration of at least these two types:
>>> - application/pkcs7-mime
>>> - application/pkcs10
>>> 
>>> There already are registered.
>>> 
>>> I think you are talking about getting Content-Format numbers for
>>> these?
>>> Do we need any parameters or content-codings with that?
>>> 
>>> Grüße, Carsten
>>> 
>>> IMPORTANT NOTICE: The contents of this email and any attachments are
>>> confidential and may also be privileged. If you are not the intended
>>> recipient, please notify the sender immediately and do not disclose
>>> the contents to any other person, use it for any purpose, or store or
>>> copy the information in any medium. Thank you.
>>> 
>>> 
>>> IMPORTANT NOTICE: The contents of this email and any attachments are
>>> confidential and may also be privileged. If you are not the intended
>>> recipient, please notify the sender immediately and do not disclose
>>> the contents to any other person, use it for any purpose, or store or
>>> copy the information in any medium. Thank you.
>>> _______________________________________________
>>> Ace mailing list
>>> Ace@ietf.org
>>> https://www.ietf.org/mailman/listinfo/ace
>> 
>> _______________________________________________
>> core mailing list
>> core@ietf.org
>> https://www.ietf.org/mailman/listinfo/core
> IMPORTANT NOTICE: The contents of this email and any attachments are confidential and may also be privileged. If you are not the intended recipient, please notify the sender immediately and do not disclose the contents to any other person, use it for any purpose, or store or copy the information in any medium. Thank you.
> _______________________________________________
> Ace mailing list
> Ace@ietf.org
> https://www.ietf.org/mailman/listinfo/ace