Expectations of Implementers of IETF Protocols
draft-housley-implementer-obligations-02
| Document | Type | Expired Internet-Draft (individual in gen area) | |
|---|---|---|---|
| Author | Russ Housley | ||
| Last updated | 2015-10-14 (Latest revision 2014-05-10) | ||
| Stream | Internet Engineering Task Force (IETF) | ||
| Formats |
Expired & archived
plain text
htmlized
pdfized
bibtex
|
||
| Reviews |
SECDIR Last Call review
Ready
GENART Last Call review
Ready
|
||
| Stream | WG state | (None) | |
| Document shepherd | (None) | ||
| IESG | IESG state | Expired (IESG: Dead) | |
| Consensus boilerplate | Unknown | ||
| Telechat date | (None) | ||
| Responsible AD | Jari Arkko | ||
| Send notices to | (None) | ||
| IANA | IANA review state | IANA OK - No Actions Needed |
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-housley-implementer-obligations-02.txt
https://www.ietf.org/archive/id/draft-housley-implementer-obligations-02.txt
Abstract
By choosing to implement an IETF protocol, one is expected to follow the specification, associated best current practices, and IANA registry practices.
Authors
(Note: The e-mail addresses provided for the authors of this Internet-Draft may no longer be valid.)