Closing ACTION-149: Check expectations regarding cts from ietf

The requirements for Standards-Track RFCs are defined in RFC RFC 2026
https://tools.ietf.org/html/rfc2026
as updated by RFC 6410
https://tools.ietf.org/html/rfc6410

RFC 2026 required testing for Proposed Standard; in section 1.2

  These procedures are explicitly aimed at recognizing and adopting
  generally-accepted practices. Thus, a candidate specification must
  be implemented and tested for correct operation and interoperability
  by multiple independent parties and utilized in increasingly
  demanding environments, before it can be adopted as an Internet
  Standard.

RFC 6410 merged Draft Standard and Standard into IETF Standard. It
also relaxed the testing requirements, in section 3.2.

Requirement for Interoperability Testing Reporting

   Testing for interoperability is a long tradition in the development
   of Internet protocols and remains important for reliable deployment
   of services.  The IETF Standards Process no longer requires a formal
   interoperability report, recognizing that deployment and use is
   sufficient to show interoperability.

Neither RFC requires any testing for Informational RFC. In RFC 2026,
section 4.2.2

Informational

   An "Informational" specification is published for the general
   information of the Internet community, and does not represent an
   Internet community consensus or recommendation.  The Informational
   designation is intended to provide for the timely publication of a
   very broad range of responsible informational documents from many
   sources, subject only to editorial considerations and to verification
   that there has been adequate coordination with the standards process
   (see section 4.2.3).

   Specifications that have been prepared outside of the Internet
   community and are not incorporated into the Internet Standards
   Process by any of the provisions of section 10 may be published as
   Informational RFCs, with the permission of the owner and the
   concurrence of the RFC Editor.

The procedure is expanded in more detail in 4.2.3 Procedures for
Experimental and Informational RFCs which is a bit long to quote here.

  https://tools.ietf.org/html/rfc2026#section-4.2.3


  

-- 
Best regards,
 Chris Lilley, Technical Director, W3C Interaction Domain

Received on Wednesday, 3 December 2014 21:36:53 UTC