Expectations of Implementers of IETF Protocols
draft-housley-implementer-obligations-02
Document | Type |
Expired Internet-Draft
(individual in gen area)
Expired & archived
|
|
---|---|---|---|
Author | Russ Housley | ||
Last updated | 2015-10-14 (Latest revision 2014-05-10) | ||
RFC stream | Internet Engineering Task Force (IETF) | ||
Intended RFC status | Informational | ||
Formats | |||
Reviews | |||
Stream | WG state | (None) | |
Document shepherd | (None) | ||
IESG | IESG state | Expired (IESG: Dead) | |
Action Holders |
(None)
|
||
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 is available in these formats:
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.)