Dear CoRE, COSE and ACE members,

We have submitted an update to the OSCOAP draft:
https://tools.ietf.org/html/draft-selander-ace-object-security-05

For those who don’t know, OSCOAP is an application layer security protocol for 
CoAP, based on wrapping request and response messages in COSE objects which are 
sent in a CoAP message exchange.

With this version, we aimed for improved readability and we added the blockwise 
functionality, as discussed during last f2f meeting.

We are now looking for reviews. Any comment or feedback would be greatly 
appreciated!

Best regards,
Francesca

-----Original Message-----
From: internet-dra...@ietf.org [mailto:internet-dra...@ietf.org] 
Sent: den 7 juli 2016 18:37
To: Göran Selander <goran.selan...@ericsson.com>; Ludwig Seitz 
<lud...@sics.se>; John Mattsson <john.matts...@ericsson.com>; Göran Selander 
<goran.selan...@ericsson.com>; Francesca Palombini 
<francesca.palomb...@ericsson.com>
Subject: New Version Notification for draft-selander-ace-object-security-05.txt


A new version of I-D, draft-selander-ace-object-security-05.txt
has been successfully submitted by Francesca Palombini and posted to the IETF 
repository.

Name:           draft-selander-ace-object-security
Revision:       05
Title:          Object Security of CoAP (OSCOAP)
Document date:  2016-07-07
Group:          Individual Submission
Pages:          36
URL:            
https://www.ietf.org/internet-drafts/draft-selander-ace-object-security-05.txt
Status:         
https://datatracker.ietf.org/doc/draft-selander-ace-object-security/
Htmlized:       
https://tools.ietf.org/html/draft-selander-ace-object-security-05
Diff:           
https://www.ietf.org/rfcdiff?url2=draft-selander-ace-object-security-05

Abstract:
   This memo defines Object Security of CoAP (OSCOAP), a method for
   application layer protection of message exchanges with the
   Constrained Application Protocol (CoAP), using the CBOR Object
   Signing and Encryption (COSE) format.  OSCOAP provides end-to-end
   encryption, integrity and replay protection to CoAP payload, options,
   and header fields, as well as a secure binding between CoAP request
   and response messages.  The use of OSCOAP is signaled with the CoAP
   option Object-Security, also defined in this memo.

                                                                                
  


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

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

Reply via email to