Bill Silverajan
2018-03-07 08:49:59 UTC
Hello CoRE,
We submitted version -08 of CoAP Protocol Negotiation on Monday. The
version adds to the feedback previously received, and now incorporated
good suggestions and feedback from Jaime's and Christian's reviews of
-07. More detailed responses to both reviews would follow shortly.
Best regards,
Bill
-------- Forwarded Message --------
Subject: New Version Notification for
draft-silverajan-core-coap-protocol-negotiation-08.txt
Date: Mon, 5 Mar 2018 12:59:02 -0800
From: internet-***@ietf.org
To: Mert Ocak <***@ericsson.com>, Bill Silverajan
<***@tut.fi>
A new version of I-D, draft-silverajan-core-coap-protocol-negotiation-08.txt
has been successfully submitted by Bilhanan Silverajan and posted to the
IETF repository.
Name: draft-silverajan-core-coap-protocol-negotiation
Revision: 08
Title: CoAP Protocol Negotiation
Document date: 2018-03-05
Group: Individual Submission
Pages: 18
URL: https://www.ietf.org/internet-drafts/draft-silverajan-core-coap-protocol-negotiation-08.txt
Status: https://datatracker.ietf.org/doc/draft-silverajan-core-coap-protocol-negotiation/
Htmlized: https://tools.ietf.org/html/draft-silverajan-core-coap-protocol-negotiation-08
Htmlized: https://datatracker.ietf.org/doc/html/draft-silverajan-core-coap-protocol-negotiation-08
Diff: https://www.ietf.org/rfcdiff?url2=draft-silverajan-core-coap-protocol-negotiation-08
Abstract:
CoAP has been standardised as an application-level REST-based
protocol. When multiple transport protocols exist for exchanging
CoAP resource representations, this document introduces a way forward
for CoAP endpoints as well as intermediaries to agree upon alternate
transport and protocol configurations as well as URIs for CoAP
messaging. Several mechanisms are proposed: Extending the CoRE
Resource Directory with new parameter types, introducing a new CoAP
Option with which clients can interact directly with servers without
needing the Resource Directory, and finally a new CoRE Link Attribute
allowing exposing alternate locations on a per-resource basis.
Please note that it may take a couple of minutes from the time of submission
until the htmlized version and diff are available at tools.ietf.org.
The IETF Secretariat
We submitted version -08 of CoAP Protocol Negotiation on Monday. The
version adds to the feedback previously received, and now incorporated
good suggestions and feedback from Jaime's and Christian's reviews of
-07. More detailed responses to both reviews would follow shortly.
Best regards,
Bill
-------- Forwarded Message --------
Subject: New Version Notification for
draft-silverajan-core-coap-protocol-negotiation-08.txt
Date: Mon, 5 Mar 2018 12:59:02 -0800
From: internet-***@ietf.org
To: Mert Ocak <***@ericsson.com>, Bill Silverajan
<***@tut.fi>
A new version of I-D, draft-silverajan-core-coap-protocol-negotiation-08.txt
has been successfully submitted by Bilhanan Silverajan and posted to the
IETF repository.
Name: draft-silverajan-core-coap-protocol-negotiation
Revision: 08
Title: CoAP Protocol Negotiation
Document date: 2018-03-05
Group: Individual Submission
Pages: 18
URL: https://www.ietf.org/internet-drafts/draft-silverajan-core-coap-protocol-negotiation-08.txt
Status: https://datatracker.ietf.org/doc/draft-silverajan-core-coap-protocol-negotiation/
Htmlized: https://tools.ietf.org/html/draft-silverajan-core-coap-protocol-negotiation-08
Htmlized: https://datatracker.ietf.org/doc/html/draft-silverajan-core-coap-protocol-negotiation-08
Diff: https://www.ietf.org/rfcdiff?url2=draft-silverajan-core-coap-protocol-negotiation-08
Abstract:
CoAP has been standardised as an application-level REST-based
protocol. When multiple transport protocols exist for exchanging
CoAP resource representations, this document introduces a way forward
for CoAP endpoints as well as intermediaries to agree upon alternate
transport and protocol configurations as well as URIs for CoAP
messaging. Several mechanisms are proposed: Extending the CoRE
Resource Directory with new parameter types, introducing a new CoAP
Option with which clients can interact directly with servers without
needing the Resource Directory, and finally a new CoRE Link Attribute
allowing exposing alternate locations on a per-resource basis.
Please note that it may take a couple of minutes from the time of submission
until the htmlized version and diff are available at tools.ietf.org.
The IETF Secretariat