TLS/DTLS Omit AEAD Explicit Nonce from Record Extension
draft-jay-tls-omit-aead-explicit-nonce-extension-00
| Document | Type |
Expired Internet-Draft
(individual)
Expired & archived
|
|
|---|---|---|---|
| Authors | Jayaraghavendran K, Raja Ashok V K | ||
| Last updated | 2016-04-04 (Latest revision 2015-09-29) | ||
| RFC stream | (None) | ||
| Intended RFC status | (None) | ||
| Formats | |||
| Stream | Stream state | (No stream defined) | |
| Consensus boilerplate | Unknown | ||
| RFC Editor Note | (None) | ||
| IESG | IESG state | Expired | |
| Telechat date | (None) | ||
| Responsible AD | (None) | ||
| Send notices to | (None) |
This Internet-Draft is no longer active. A copy of the expired Internet-Draft is available in these formats:
Abstract
With emergence of Internet of Things(IoT), DTLS is being widely considered as a protocol of choice for communication security in IoT applications. Further, AES_CCM has emerged as the cipher of choice in constrained environments. Constrained Application Protocol (CoAP), which is the application layer protocol for resource constrained environments, mandates DTLS as underlying security protocol and proposes AES_CCM based ciphers to be used with different key exchange methods. AEAD ciphers requires an explicit nonce of 8 bytes must be carried in each transmitted record.This document defines a TLS (and DTLS) extension, which will allow clients and servers to omit the explicit nonce sent in TLS/DTLS records. This document can be considered as an extended version of "Transport Layer Security (TLS) Extensions : Extension Definitions". The extension defined in this document apply equally to both DTLS and TLS protocols.
Authors
Jayaraghavendran K
Raja Ashok V K
(Note: The e-mail addresses provided for the authors of this Internet-Draft may no longer be valid.)