> -Original Message-
> From: Michael Richardson
> Sent: Friday, February 22, 2019 8:46 AM
> To: Carsten Bormann
> Cc: Jim Schaad ; Panos Kampanakis (pkampana)
> ; ace ; Klaus Hartke
> ; draft-ietf-ace-coap-...@ietf.org
> Subject: Re: [Ace] Embedded Conte
Carsten Bormann wrote:
>> I am thinking of two different URLs, that is not do the difference by
>> a query parameter but by changing the URI.
> Note that the query parameters are part of the URI, so fundamentally
> there is no difference between putting the info there or in the p
rsten Bormann'
Cc: 'ace' ; 'Klaus Hartke'
Subject: RE: [Ace] Embedded Content Types
Panos,
Someplace you are not understanding what I am saying.
> -Original Message-
> From: Panos Kampanakis (pkampana)
> Sent: Thursday, February 21, 2019 7:21 PM
> T
Panos,
Someplace you are not understanding what I am saying.
> -Original Message-
> From: Panos Kampanakis (pkampana)
> Sent: Thursday, February 21, 2019 7:21 PM
> To: Jim Schaad ; 'Carsten Bormann'
> Cc: 'ace' ; 'Klaus Hartke'
akis (pkampana) ; 'ace' ;
'Klaus Hartke' ; draft-ietf-ace-coap-...@ietf.org
Subject: RE: [Ace] Embedded Content Types
It is true that the query parameters are part of the type. However, the use of
two different URIs allows for the discovery to figure out if both versions are
because it is not looked for.
Jim
> -Original Message-
> From: Carsten Bormann
> Sent: Thursday, February 21, 2019 2:52 PM
> To: Jim Schaad
> Cc: Panos Kampanakis (pkampana) ; ace
> ; Klaus Hartke ; draft-ietf-ace-coap-
> e...@ietf.org
> Subject: Re: [Ace] Embedded C
On Feb 21, 2019, at 23:31, Jim Schaad wrote:
>
> I am thinking of two different URLs, that is not do the difference by a query
> parameter but by changing the URI.
Note that the query parameters are part of the URI, so fundamentally there is
no difference between putting the info there or in t
d ; 'Carsten Bormann'
> Cc: ace@ietf.org; 'Klaus Hartke' ; draft-ietf-ace-
> coap-...@ietf.org
> Subject: RE: [Ace] Embedded Content Types
>
> > This is why I would prefer doing something like "/est/skg" and
> "/est/skg/yyy".
>
> Not
s (pkampana) ; 'Carsten Bormann'
Cc: ace@ietf.org; 'Klaus Hartke' ;
draft-ietf-ace-coap-...@ietf.org
Subject: RE: [Ace] Embedded Content Types
> -Original Message-
> From: Panos Kampanakis (pkampana)
> Sent: Thursday, February 21, 2019 1:32 PM
> To:
> -Original Message-
> From: Panos Kampanakis (pkampana)
> Sent: Thursday, February 21, 2019 1:32 PM
> To: Carsten Bormann
> Cc: Jim Schaad ; ace@ietf.org; Klaus Hartke
> ; draft-ietf-ace-coap-...@ietf.org
> Subject: RE: [Ace] Embedded Content Types
>
> Tha
returned attribute values are the accepted values by the server in the "Accept"
option.
-Original Message-
From: Carsten Bormann
Sent: Wednesday, February 20, 2019 8:11 PM
To: Panos Kampanakis (pkampana)
Cc: Jim Schaad ; ace@ietf.org; Klaus Hartke
; draft-ietf-ace-coap-
Carsten Bormann wrote:
> I think this is just a misunderstanding — the idea wasn’t to supply the
> parts under different URIs, but to make up different URIs for
> retrieving the different combinations coming in one multipart-core, in
> one transaction.
> or, say
> /skg/2
Hi,
For me the est-coaps solution with different URIs is a good one.
as suggested by Carsten, /skg/ctnumbers seems straightforward.
In the return of /.well-known/core, the CT hints will help. No need to
define multiple content-format combinations.
Peter
Jim Schaad schreef op 2019-02-20 18:58:
>
On Feb 20, 2019, at 22:33, Panos Kampanakis (pkampana)
wrote:
>
> If we broke the requests to different URIs, it means that a client needs to
> keep track of his transactions and on top of it he needs to correlate the key
> and the cert he receives at a later time.
I think this is just a misu
> -Original Message-
> From: Panos Kampanakis (pkampana)
> Sent: Wednesday, February 20, 2019 1:34 PM
> To: Jim Schaad ; ace@ietf.org; Klaus Hartke
>
> Cc: draft-ietf-ace-coap-...@ietf.org
> Subject: RE: [Ace] Embedded Content Types
>
> Hi Jim,
>
>
it in this context.
Any strong objections?
Rgs,
Panos
-Original Message-
From: Ace On Behalf Of Jim Schaad
Sent: Wednesday, February 20, 2019 12:59 PM
To: ace@ietf.org
Cc: draft-ietf-ace-coap-...@ietf.org
Subject: [Ace] Embedded Content Types
The CoRE working had an interesting vi
The CoRE working had an interesting virtual meeting this morning (my time)
where the main topic of discussion was how to deal with embedded content
types. This is a current problem that needs to be addressed with the EST
document which is currently trying to deal with last call comments. The log
17 matches
Mail list logo
