Use of Fingerprints for Identifying Certificates in the Session Description Protocol (SDP)
draft-thomson-mmusic-fingerprint-00
| Document | Type | Expired Internet-Draft (individual) | |
|---|---|---|---|
| Author | Martin Thomson | ||
| Last updated | 2014-04-24 (latest revision 2013-10-21) | ||
| Stream | (None) | ||
| Intended RFC status | (None) | ||
| Formats |
Expired & archived
pdf
htmlized (tools)
htmlized
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-thomson-mmusic-fingerprint-00.txt
https://www.ietf.org/archive/id/draft-thomson-mmusic-fingerprint-00.txt
Abstract
The Session Description Protocol (SDP) fingerprint attribute binds a session description to an X.509 certificate. This document describes how hash agility is achieved without backwards compatibility issues. This document also describes how the fingerprint attribute can be used to identify a set of valid certificates. This document updates RFC4572.
Authors
Martin Thomson (martin.thomson@skype.net)
(Note: The e-mail addresses provided for the authors of this Internet-Draft may no longer be valid.)