Subject: [Ace] FW: New Version Notification for draft-somaraju-ace-multicast-01.txt

From: Somaraju Abhinav <[email-masked]>
Date: Fri, 15 Jan 2016 14:33:21 +0000

Dear All,
we posted a new version of the "Security for Low-Latency Group Communication" draft.

Description of changes from previous version:
- Reorganised text/content for clarity
- Focussed on using Object Security instead of multicast DTLS
- Removed references to LWM2M
- More detailed information on content of access tokens and group messages

Regards,
Abhinav

-----Original Message-----
From: [email-masked] [mailto:[email-masked]]
Sent: Freitag, 15. Jänner 2016 14:48
To: Somaraju Abhinav <[email-masked]>; Hannes Tschofenig <[email-masked]>; Sandeep S. Kumar <[email-masked]>; Hannes Tschofenig <[email-masked]>; Walter Werner <[email-masked]>
Subject: New Version Notification for draft-somaraju-ace-multicast-01.txt

A new version of I-D, draft-somaraju-ace-multicast-01.txt
has been successfully submitted by Hannes Tschofenig and posted to the IETF repository.

Name:           draft-somaraju-ace-multicast
Revision:       01
Title:          Security for Low-Latency Group Communication
Document date:  2016-01-15
Group:          Individual Submission
Pages:          19
URL:            https://www.ietf.org/internet-drafts/draft-somaraju-ace-multicast-01.txt
Status:         https://datatracker.ietf.org/doc/draft-somaraju-ace-multicast/
Htmlized:       https://tools.ietf.org/html/draft-somaraju-ace-multicast-01
Diff:           https://www.ietf.org/rfcdiff?url2=draft-somaraju-ace-multicast-01

Abstract:
   Some Internet of Things application domains, such as lighting, have
   strict requirements on latency for group communication.  From a user
   experience point of view latency less than 200 ms is necessary from
   an action triggered by a user to the visible effects.  This draft
   describes procedures for authorization, key management, and securing
   group messages within a low latency application domain with a special
   emphasis on lighting systems.  We specify the usage of object
   security at the application layer for group communication and assume
   that CoAP is used as the application layer protocol.

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

________________________________________________________ The contents of this e-mail and any attachments are confidential to the intended recipient. They may not be disclosed to or used by or copied in any way by anyone other than the intended recipient. If this e-mail is received in error, please immediately notify the sender and delete the e-mail and attached documents. Please note that neither the sender nor the sender's company accept any responsibility for viruses and it is your responsibility to scan or otherwise check this e-mail and any attachments.