DTLS Multicast
draft-lucas-dtls-multicast-00

Document Type Active Internet-Draft (individual)
Last updated 2017-09-13
Stream (None)
Intended RFC status (None)
Formats plain text pdf html bibtex
Stream Stream state (No stream defined)
Consensus Boilerplate Unknown
RFC Editor Note (None)
IESG IESG state I-D Exists
Telechat date
Responsible AD (None)
Send notices to (None)
tls                                                           R. Lucas 
Internet Draft                              Cisco International Limited 
Intended status: Standards Track                     September 13, 2017 
Expires: March 17, 2018 
 
                             DTLS Multicast 
                  draft-lucas-dtls-multicast-00.txt 
Abstract 
 
  This proposal to provide a secure multicast 1-to-N or M-to-N device 
  capability, with the same level of reliability as the underlying 
  multicast network, also aims to be light-weight and supported  
  by a very constrained device. Guaranteed reliability would be 
  provided by an additional protocol working in co-operation with it. 
   
  The aim is to support end to end secure communications in the edge 
  device world of IoT where the transport methods will vary or at 
  least change once the IP realm is left. Hence there is no 
  dependence on Ipv6 or IP or CoAP and no restrictions that might be 
  introduced if too specific an end node application was implied. It 
  is network independent, it just must be possible to transmit and 
  receive frames in multicast. 
   
  This can be achieved with simply a minimal change to the DTLS 
  behavior and using current DTLS libraries. DTLS headers are not 
  changed, additional headers are used in the packets before the DTLS 
  traffic.  
   
  DTLS Multicast keeps the layer concept pure and independent, hence 
  it can be used for routing something that is not CoAP. 
 
Status of This Memo 
 
   This Internet-Draft is submitted in full conformance with the 
   provisions of BCP 78 and BCP 79. 
 
   Internet-Drafts are working documents of the Internet Engineering 
   Task Force (IETF).  Note that other groups may also distribute 
   working documents as Internet-Drafts.  The list of current Internet- 
   Drafts is at http://datatracker.ietf.org/drafts/current/. 
 
   Internet-Drafts are draft documents valid for a maximum of six 
   months and may be updated, replaced, or obsoleted by other documents 
   at any time. It is inappropriate to use Internet-Drafts as reference 
   material or to cite them other than as "work in progress." 
 
   This Internet-Draft will expire on March 17, 2018. 
 
Copyright Notice 
 
   Copyright (c) 2017 IETF Trust and the persons identified as the 
   document authors. All rights reserved. 
Lucas                   Expires March 17, 2018                [Page 1] 

Internet-Draft               DTLS Multicast              September 2017 
 
   This document is subject to BCP 78 and the IETF Trust's Legal 
   Provisions Relating to IETF Documents 
   (http://trustee.ietf.org/license-info) in effect on the date of 
   publication of this document.  Please review these documents 
   carefully, as they describe your rights and restrictions with 
   respect to this document. 
 
   Code Components extracted from this document must include Simplified 
   BSD License text as described in Section 4.e of the Trust Legal 
   Provisions and are provided without warranty as described in the 
   Simplified BSD License. 
 
 
 

Contents 
1.  Introduction                                                     3 
2.  Background                                                       4 
3.  Restrictions / Assumptions                                       4 
4.  Terminology                                                      4 
5.  DTLS Multicast Proposal                                          5 
6. Significant differences between DTLS Multicast and DTLS Unicast    7 
7.  Logical Traffic Types become Channels                             7 
7.1  CLIENT channel format                                           8 
7.2  ELECTION channel format                                         8 
7.3  CONTROL channel format                                          8 
7.4  SUBGROUP channel format                                         9 
7.5  SENDER channel format                                           9 
8.  Message definitions                                              9 
9.  How to use the DTLSMulticast structures                          12 
9.1  DTLSMulticastRADIUS                                            12 
9.2  DTLSMulticastJoin                                              13 
   9.2.1  sender_channel                                            13 
   9.2.2  max_subgroups                                             13 
   9.2.3  Group controller election flags NE and EL                  14 
   9.2.4  Member send ability flags TX and RX.                      14 
9.3  DTLSMulticastAddSA                                             14 
9.4  DTLSMulticastDropSA                                            15 
9.5  DTLSMulticastReconnect                                         15 
10.  Joining a DTLS multicast group                                  16 
11.  Notes on cipher suites                                         17 
12.  Receiving DTLS multicast data                                  17 
13.  Sending DTLS multicast data                                    19 
Show full document text