Policy for Registering SRTP Transforms
draft-ietf-avt-register-srtp-02
| Document | Type |
Expired Internet-Draft
(avt WG)
Expired & archived
|
|
|---|---|---|---|
| Author | Dan Wing | ||
| Last updated | 2015-10-14 (Latest revision 2010-04-20) | ||
| Replaces | draft-wing-avt-register-srtp | ||
| RFC stream | Internet Engineering Task Force (IETF) | ||
| Intended RFC status | Proposed Standard | ||
| Formats | |||
| Reviews | |||
| Additional resources | Mailing list discussion | ||
| Stream | WG state | WG Document | |
| Document shepherd | (None) | ||
| IESG | IESG state | Expired (IESG: Dead) | |
| Action Holders |
(None)
|
||
| Consensus boilerplate | Unknown | ||
| Telechat date | (None) | ||
| Responsible AD | Robert Sparks | ||
| IESG note | ** No value found for 'doc.notedoc.note' ** | ||
| Send notices to | (None) |
This Internet-Draft is no longer active. A copy of the expired Internet-Draft is available in these formats:
Abstract
IETF procedure requires country-specific cryptographic transforms to be Informational RFCs. This document allows such Informational RFCs to be used by SRTP and SRTP Security Descriptions.
Authors
(Note: The e-mail addresses provided for the authors of this Internet-Draft may no longer be valid.)