Cryptographic Agility for the RSVP INTEGRITY Object
draft-turner-rsvp-auth-update-01
| Document | Type | Expired Internet-Draft (individual) | |
|---|---|---|---|
| Last updated | 2013-10-20 (latest revision 2013-04-18) | ||
| 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) | ||
https://www.ietf.org/archive/id/draft-turner-rsvp-auth-update-01.txt
Abstract
This document modifies the RSVP INTEGRITY object to support algorithm agility by explicitly indicating the algorithm used. It also provides rationale for the design choices. Finally, it updates the mandatory to implement algorithm.
Authors
Sean Turner
(turners@ieca.com)
Lou Berger
(lberger@labn.net)
Mahesh Jethanandani
(mjethanandani@gmail.com)
Keyur Patel
(keyupate@cisco.com)
Dacheng Zhang
(zhangdacheng@huawei.com)
(Note: The e-mail addresses provided for the authors of this Internet-Draft may no longer be valid.)