Re: [TLS] Document Action: 'TLS Elliptic Curve Cipher Suites with SHA-256/384 and AES Galois Counter Mode' to Informational RFC

[Dean Anderson <dean at av8.com>]

On Fri, 27 Jun 2008, Russ Housley wrote:

> >Indeed, it appears to be the case that I was correct on the principle
> >issue:  That the general public is not licenced to use these patents on
> >implementing this draft.
> 
> Right.  This is the reason the document is a candidate for the 
> standards track.  

So, you (Russ--chair of IETF) knew of the patent encumbrances, but
failed to report those facts in an IETF 'IPR' (patent) disclosure?  And
the WG failed to discuss non-patent alternatives in the working group as
required by RFC3979?  This seems to be almost the same issues as with
TLS-Authz.  It is too bad that Sam Hartman is no longer on the IESG,
this time.


> The idea of the informational specification is so that anyone that
> chooses to use this technology can do so in an interoperable way.

The above reason does not seem to be a proper use of the Informational
category.

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.


Particularly, Section 4.2.3 states

   To ensure that the non-standards track Experimental and Informational
   designations are not misused to circumvent the Internet Standards
   Process, the IESG and the RFC Editor have agreed that the RFC Editor
   will refer to the IESG any document submitted for Experimental or
   Informational publication which, in the opinion of the RFC Editor,
   may be related to work being done, or expected to be done, within the
   IETF community.  The IESG shall review such a referred document
   within a reasonable period of time, and recommend either that it be
   published as originally submitted or referred to the IETF as a
   contribution to the Internet Standards Process.

This document is related to work that has been done within the IETF 
community.

		--Dean

-- 
Av8 Internet   Prepared to pay a premium for better service?
www.av8.net         faster, more reliable, better service
617 344 9000   



_______________________________________________
TLS mailing list
TLS at ietf.org
https://www.ietf.org/mailman/listinfo/tls