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

[Klaus Hartke]

Carsten Bormann wrote:
> Next step: make a proposal and raise this on core-paramet...@ietf.org so
we get the needed input from the designated expert.

Done.
https://www.ietf.org/mail-archive/web/core-parameters/current/msg00024.html

Klaus
___
Ace mailing list
Ace@ietf.org
https://www.ietf.org/mailman/listinfo/ace

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

[Carsten Bormann]

On May 24, 2018, at 16:15, Hannes Tschofenig <hannes.tschofe...@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-paramet...@ietf.org so we get 
the needed input from the designated expert.

Grüße, Carsten


>  
> Ciao
> Hannes
>  
> From: Carsten Bormann [mailto:c...@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 <c...@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.tschofe...@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:c...@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.tschofe...@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

___
Ace mailing list
Ace@ietf.org
https://www.ietf.org/mailman/listinfo/ace

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

[Hannes Tschofenig]

Hi all,

Trying to finalize this discussion: Could we do an early registry of the 
Content-Format numbers?

From the discussion so far I believe we concluded that the charset is utf-8 and 
that there are no parameters. Is that correct?

Ciao
Hannes

From: Carsten Bormann [mailto:c...@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 <c...@tzi.org<mailto:c...@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.tschofe...@arm.com<mailto:hannes.tschofe...@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:c...@tzi.org]
Sent: 15 May 2018 11:45
To: Hannes Tschofenig
Cc: ace@ietf.org<mailto: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.tschofe...@arm.com<mailto:hannes.tschofe...@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

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

[Michael Richardson]

Hannes Tschofenig  wrote:
> I don't have a strong opinion about option #2 appears to be slightly
> better.

Oh, I misread your options before.

Hannes Tschofenig  wrote:
>> (RTT for the lookup vs extra bytes in the URL)
>> Are you asking me about these two options:
>> Option #1 - going through /.well-known/core
>> REQ: GET /.well-known/core?rt=ace.est
>> RES: 2.05 Content ; rt="ace.est"


>> Option #2 - using a /.well-known/est URL
>> REQ: GET /.well-known/est
>> RES: 2.05 Content ; rt="ace.est"

Option 2 is not substituting /.well-known/core for /.well-known/est
(and doing resource discovery and then learn one uses /est-root/rv, etc.)
but rather not doing resource discovery, just go directly
to /.well-known/est/rv, which is what we do in RFC7030.

--
Michael Richardson , Sandelman Software Works
 -= IPv6 IoT consulting =-





signature.asc
Description: PGP signature
___
Ace mailing list
Ace@ietf.org
https://www.ietf.org/mailman/listinfo/ace

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

[Hannes Tschofenig]

I don't have a strong opinion about option #2 appears to be slightly better.

I guess hard-cording URLs will not work

-Original Message-
From: Michael Richardson [mailto:mcr+i...@sandelman.ca]
Sent: 16 May 2018 14:16
To: Hannes Tschofenig
Cc: ace@ietf.org
Subject: Re: [Ace] Early media-type registration for EST over CoAP


Hannes Tschofenig <hannes.tschofe...@arm.com> wrote:
>> Hannes: do you have any opinion about the necessity of going through
>> /.well-known/core to get the short URL, vs just using a
>> /.well-known/est URL?

Yes, exactly.  Is option #1 useful enough to justify the code to parse links?  
Os is the code impact already paid for in your view?

> (RTT for the lookup vs extra bytes in the URL)
> Are you asking me about these two options:
> Option #1 - going through /.well-known/core
>  REQ: GET /.well-known/core?rt=ace.est
>  RES: 2.05 Content ; rt="ace.est"


> Option #2 - using a /.well-known/est URL
>  REQ: GET /.well-known/est
>  RES: 2.05 Content ; rt="ace.est"

--
]   Never tell me the odds! | ipv6 mesh networks [
]   Michael Richardson, Sandelman Software Works| network architect  [
] m...@sandelman.ca  http://www.sandelman.ca/|   ruby on rails[


--
Michael Richardson <mcr+i...@sandelman.ca>, Sandelman Software Works  -= IPv6 
IoT consulting =-



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

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

[Hannes Tschofenig]

> Hannes: do you have any opinion about the necessity of going through 
> /.well-known/core to get the short URL, vs just using a /.well-known/est URL?
(RTT for the lookup vs extra bytes in the URL)

Are you asking me about these two options:

Option #1 - going through /.well-known/core

 REQ: GET /.well-known/core?rt=ace.est

 RES: 2.05 Content
   ; rt="ace.est"



Option #2 - using a /.well-known/est URL

 REQ: GET /.well-known/est

 RES: 2.05 Content
   ; rt="ace.est"



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

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

[Carsten Bormann]

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.tschofe...@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:c...@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.tschofe...@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.
> 
> 
___
Ace mailing list
Ace@ietf.org
https://www.ietf.org/mailman/listinfo/ace

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

[Hannes Tschofenig]

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:c...@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.tschofe...@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.
___
Ace mailing list
Ace@ietf.org
https://www.ietf.org/mailman/listinfo/ace

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

[Carsten Bormann]

On May 15, 2018, at 10:56, Hannes Tschofenig  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

___
Ace mailing list
Ace@ietf.org
https://www.ietf.org/mailman/listinfo/ace

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

[Hannes Tschofenig]

I get the impression that the EST over CoAP spec will not completed as soon as 
I had hoped.

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

Ciao
Hannes

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