Re: [TLS] RFC 2817 proposed standard status revocation?
Eric Rescorla <ekr@networkresonance.com> Mon, 11 December 2006 00:09 UTC
Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com) by megatron.ietf.org with esmtp (Exim 4.43) id 1GtYjb-0003lm-Oe; Sun, 10 Dec 2006 19:09:31 -0500
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org) by megatron.ietf.org with esmtp (Exim 4.43) id 1GtYjb-0003lh-Ch for tls@lists.ietf.org; Sun, 10 Dec 2006 19:09:31 -0500
Received: from laser.networkresonance.com ([198.144.196.2]) by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1GtYja-0000sx-1f for tls@lists.ietf.org; Sun, 10 Dec 2006 19:09:31 -0500
Received: from networkresonance.com (raman.networkresonance.com [198.144.196.3]) by laser.networkresonance.com (Postfix) with ESMTP id CAA895C01E; Sun, 10 Dec 2006 16:12:36 -0800 (PST)
To: Peter Williams <home_pw@msn.com>
Subject: Re: [TLS] RFC 2817 proposed standard status revocation?
In-reply-to: Your message of "Sun, 10 Dec 2006 10:35:24 PST." <BAY103-W3D8FE918D057A244F576492D10@phx.gbl>
X-Mailer: MH-E 7.4.3; nmh 1.2; XEmacs 21.4 (patch 19)
Date: Sun, 10 Dec 2006 16:09:27 -0800
From: Eric Rescorla <ekr@networkresonance.com>
Message-Id: <20061211001236.CAA895C01E@laser.networkresonance.com>
X-Spam-Score: 0.0 (/)
X-Scan-Signature: 9466e0365fc95844abaf7c3f15a05c7d
Cc: tls@lists.ietf.org
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>
Errors-To: tls-bounces@lists.ietf.org
Peter Williams <home_pw@msn.com> wrote: > I assume this WG is, or would be, responsible for handling RFC2817 > standards track issues?http://tools.ietf.org/html/rfc2817. > > I record my recommendation that the cited document have its PROPOSED > STANDARD status revoked. Period. Its bad (SSL) theory, and even worse > practice. I more or less agree with you that the HTTP Upgrade part of RFC 2817 is a bad idea, but I hardly think it's worth the trouble to have it moved to Historical, esp. since 2817 also standardizes the CONNECT method, which is quite widely used. > Never ever forget, SSL was intended as an IPSEC stopgap. In IETF, dont > force TLS into a long term position in the internet security > architecture that it doesn't deserve (e.g. RFC2817). It is SUPPOSED to > go away, at some point. Regardless of what the intentions of the SSL designers were, it's now quite clear that TLS is generally applicable. I don't agree that if IPsec suddenly became widely available people would suddenly stop being interested in TLS. While it may be true that TLS will go away at some point, that's not something the IETF is planning for. -Ekr _______________________________________________ TLS mailing list TLS@lists.ietf.org https://www1.ietf.org/mailman/listinfo/tls
- [TLS] RFC 2817 proposed standard status revocatio… Peter Williams
- RE: [TLS] RFC 2817 proposed standard status revoc… Peter Williams
- Re: [TLS] RFC 2817 proposed standard status revoc… Eric Rescorla
- Re: [TLS] RFC 2817 proposed standard status revoc… Eric Rescorla