Strong Identities for DOTS Agents
draft-moskowitz-dots-identities-00

Document Type Expired Internet-Draft (individual)
Last updated 2017-05-03 (latest revision 2016-10-30)
Stream (None)
Intended RFC status (None)
Formats
Expired & archived
plain text pdf html bibtex
Stream Stream state (No stream defined)
Consensus Boilerplate Unknown
RFC Editor Note (None)
IESG IESG state Expired
Telechat date
Responsible AD (None)
Send notices to (None)

This Internet-Draft is no longer active. A copy of the expired Internet-Draft can be found at
https://www.ietf.org/archive/id/draft-moskowitz-dots-identities-00.txt

Abstract

DOTS communications are machine-to-machine oriented communications. In addition DOTS agents are expected to end up in a large number of entities. As a result, in addition to secure, the naming scheme to identify all DOTS agents must be scalable. For these reasons this document recommends the use of cryptographic identifiers or strong Identities as opposed to human readable identifiers for example. This document proposes two forms of strong Identities for the registration and operation of DOTS Agents. One is 802.1AR LDevID [Std-802.1AR-2009] X.509 certificates. The other is raw public keys as in HIP [RFC7401] or TLS/DTLS Raw Public Keys [RFC7250].

Authors

Robert Moskowitz (rgm@labs.htt-consult.com)
Liang Xia (frank.xialiang@huawei.com)
Daniel Migault (daniel.migault@ericsson.com)
Andrew Mortensen (amortensen@arbor.net)

(Note: The e-mail addresses provided for the authors of this Internet-Draft may no longer be valid.)