Hi Panos, On Mon, Jan 6, 2020, at 5:32 PM, Panos Kampanakis (pkampana) wrote: > Hi Alexey, > > > Just to clarify: the original EST URIs are prohibited in COAP-EST? > > No we don't forbid them in the draft. We do not make them MTI either though. > The long URIs can be supported and they would be a non-default EST-coaps > resource that a server could support and a client could do resource > discovery for. So we did not add text to say "MUST NOT implement the long > URIs". The mandatory to implement/support EST-coaps URIs are the short URIs > for EST-coaps though.
After the followup discussion, I was thinking more about adding something along the lines of "MAY implement the long URIs". But this comment is non blocking and I am sure you will do the right thing. Best Regards, Alexey > Panos > > > -----Original Message----- > From: Ace <[email protected]> On Behalf Of Alexey Melnikov via > Datatracker > Sent: Monday, January 06, 2020 12:21 PM > To: The IESG <[email protected]> > Cc: [email protected]; [email protected]; > [email protected]; [email protected] > Subject: [Ace] Alexey Melnikov's No Objection on draft-ietf-ace-coap-est-17: > (with COMMENT) > > Alexey Melnikov has entered the following ballot position for > draft-ietf-ace-coap-est-17: No Objection > > When responding, please keep the subject line intact and reply to all email > addresses included in the To and CC lines. (Feel free to cut this > introductory paragraph, however.) > > > Please refer to https://www.ietf.org/iesg/statement/discuss-criteria.html > for more information about IESG DISCUSS and COMMENT positions. > > > The document, along with other ballot positions, can be found here: > https://datatracker.ietf.org/doc/draft-ietf-ace-coap-est/ > > > > ---------------------------------------------------------------------- > COMMENT: > ---------------------------------------------------------------------- > > Thank you for this well written document. And thank you for addressing my > points in github. > > A remaining comment (which might or might not have been resolved): > > 5.1. Discovery and URIs > > Clients and servers MUST support the short resource EST-coaps URIs. > > Just to clarify: the original EST URIs are prohibited in COAP-EST? > > > _______________________________________________ > Ace mailing list > [email protected] > https://www.ietf.org/mailman/listinfo/ace > > Attachments: > * smime.p7s _______________________________________________ Ace mailing list [email protected] https://www.ietf.org/mailman/listinfo/ace
