Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com)
 by megatron.ietf.org with esmtp (Exim 4.43)
 id 1GwJRF-0000tE-SM; Mon, 18 Dec 2006 09:25:57 -0500
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org)
 by megatron.ietf.org with esmtp (Exim 4.43) id 1GwJRE-0000t8-SJ
 for tls@ietf.org; Mon, 18 Dec 2006 09:25:56 -0500
Received: from nz-out-0506.google.com ([64.233.162.230])
 by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1GwJRC-00069s-LP
 for tls@ietf.org; Mon, 18 Dec 2006 09:25:56 -0500
Received: by nz-out-0506.google.com with SMTP id z6so632476nzd
 for <tls@ietf.org>; Mon, 18 Dec 2006 06:25:54 -0800 (PST)
DomainKey-Signature: a=rsa-sha1; q=dns; c=nofws; s=beta; d=gmail.com;
 h=received:message-id:date:from:to:subject:mime-version:content-type;
 b=Hn2ZisoqIv22nDu34mR44fXV6erEgYneuQPkVdRlbDRbZ1VpK8JpTLTuFu0vkxbSsPjyAFV9MACMsjHB/jXjK1/yc9q7lkagjk+c0+Nv8qsSQn2AcZXuuOtV/P7wu4tLCdSpTJJwHIUgwmMEYLFKtz+huz8nMJRHKmWw68CAtjk=
Received: by 10.78.201.15 with SMTP id y15mr3169181huf.1166451953178;
 Mon, 18 Dec 2006 06:25:53 -0800 (PST)
Received: by 10.78.182.7 with HTTP; Mon, 18 Dec 2006 06:25:52 -0800 (PST)
Message-ID: <7d7b76890612180625m4a3b5071we41f1eabdaba5d3f@mail.gmail.com>
Date: Mon, 18 Dec 2006 15:25:52 +0100
From: "Georges Le grand" <georgeslegr@gmail.com>
To: tls@ietf.org
MIME-Version: 1.0
X-Spam-Score: 0.3 (/)
X-Scan-Signature: 97adf591118a232206bdb5a27b217034
Cc: 
Subject: [TLS] Implementations for RFC4279, RFC4492, RFC4366 and RFC4347
X-BeenThere: tls@lists.ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: "This is the mailing list for the Transport Layer Security working
 group of the IETF." <tls.lists.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/tls>,
 <mailto:tls-request@lists.ietf.org?subject=unsubscribe>
List-Archive: <http://www1.ietf.org/pipermail/tls>
List-Post: <mailto:tls@lists.ietf.org>
List-Help: <mailto:tls-request@lists.ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/tls>,
 <mailto:tls-request@lists.ietf.org?subject=subscribe>
Content-Type: multipart/mixed; boundary="===============1249955443=="
Errors-To: tls-bounces@lists.ietf.org

--===============1249955443==
Content-Type: multipart/alternative; 
 boundary="----=_Part_14300_7306547.1166451952871"

------=_Part_14300_7306547.1166451952871
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit
Content-Disposition: inline

RFC2026 says:

... 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.

I'd like to be informed if the above text has been applied to RFC4279,
RFC4492, RFC4366 and RFC4347. Is there at least, for each RFC,
two interoperable implementations have been developed

Sincerely,
Georges

------=_Part_14300_7306547.1166451952871
Content-Type: text/html; charset=ISO-8859-1
Content-Transfer-Encoding: 7bit
Content-Disposition: inline

<div>RFC2026 says:</div>
<div>&nbsp;</div>
<div>... a candidate specification must be implemented and tested for correct operation and&nbsp;interoperability by multiple independent parties and utilized in increasingly demanding environments, before it can be adopted as an Internet Standard.
<br>&nbsp;</div>
<div>I'd like to be informed if the above text has been applied to&nbsp;RFC4279, RFC4492, RFC4366 and RFC4347. Is there at least, for each RFC, two&nbsp;interoperable implementations have been developed</div>
<div>&nbsp;</div>
<div>Sincerely,</div>
<div>Georges</div>

------=_Part_14300_7306547.1166451952871--


--===============1249955443==
Content-Type: text/plain; charset="us-ascii"
MIME-Version: 1.0
Content-Transfer-Encoding: 7bit
Content-Disposition: inline

_______________________________________________
TLS mailing list
TLS@lists.ietf.org
https://www1.ietf.org/mailman/listinfo/tls

--===============1249955443==--