Secure Credential Transfer
draft-secure-credential-transfer-04
| Document | Type |
Expired Internet-Draft
(individual)
Expired & archived
|
|
|---|---|---|---|
| Authors | Dmitry Vinokurov , Matt Byington , Matthias Lerch , Alex Pelletier , Nick Sha | ||
| Last updated | 2023-01-09 (Latest revision 2022-07-08) | ||
| 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
This document describes a mechanism to transfer digital credentials securely between two devices. Secure credentials may represent a digital key to a hotel room, a digital key to a door lock in a house or a digital key to a car. Devices that share credentials may belong to the same or two different platforms (e.g. iOS and Android). Secure transfer may include one or more write and read operations. Credential transfer needs to be performed securely due to the sensitive nature of the information.
Authors
Dmitry Vinokurov
Matt Byington
Matthias Lerch
Alex Pelletier
Nick Sha
(Note: The e-mail addresses provided for the authors of this Internet-Draft may no longer be valid.)