Implementation reports

This page provides implementation reports of a protocol specifications that have been considered for advancement to an Internet Standard.

Key Info

The IETF Standards Process (RFC 2026, updated by RFC 6410) requires at least two independent and inter-operable implementations for advancing a protocol specification to Internet Standard. Following the Montreal IETF meeting June, 1996, the IAB recommended that:

"The IETF Secretariat should be responsible for making this material available to the community." 

This page provides implementation reports as received by the IESG in its deliberations. Note that this is NOT a list of endorsements. Nor should it be assumed that the list is all inclusive. Indeed, there may be many more implementations. 

The IETF Secretariat provides the following reports for information only, and in no way endorses their accuracy. This disclaimer must be quoted in full whenever the information from the reports is quoted.

Bibliography

  • [1] RFC 2026
    The Internet Standards Process -- Revision 3

    This memo documents the process used by the Internet community for the standardization of protocols and procedures. It defines the stages in the standardization process, the requirements for moving a document between stages and the types of documents used during this process. This document spec...

  • [2] RFC 6410
    Reducing the Standards Track to Two Maturity Levels

    This document updates the Internet Engineering Task Force (IETF) Standards Process defined in RFC 2026. Primarily, it reduces the Standards Process from three Standards Track maturity levels to two. This memo documents an Internet Best Current Practice.

    Dave Crocker, Eric Burger, Russ Housley