Re: [CHANNEL-BINDING] [TLS] RESOLVED (Re: [sasl] lasgt call comments (st Call: draft-altman-tls-channel-bindings (Channel Bindings for TLS) to Proposed Standard))
Nicolas Williams <Nicolas.Williams@sun.com> Wed, 04 November 2009 18:38 UTC
Return-Path: <Nicolas.Williams@sun.com>
X-Original-To: channel-binding@core3.amsl.com
Delivered-To: channel-binding@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id ABBFF3A68CB; Wed, 4 Nov 2009 10:38:18 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -6.045
X-Spam-Level:
X-Spam-Status: No, score=-6.045 tagged_above=-999 required=5 tests=[AWL=0.001, BAYES_00=-2.599, HELO_MISMATCH_COM=0.553, RCVD_IN_DNSWL_MED=-4]
Received: from mail.ietf.org ([64.170.98.32]) by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id F7V1T7EvW6gp; Wed, 4 Nov 2009 10:38:18 -0800 (PST)
Received: from sca-ea-mail-2.sun.com (sca-ea-mail-2.Sun.COM [192.18.43.25]) by core3.amsl.com (Postfix) with ESMTP id 355453A67AF; Wed, 4 Nov 2009 10:38:12 -0800 (PST)
Received: from dm-central-01.central.sun.com ([129.147.62.4]) by sca-ea-mail-2.sun.com (8.13.7+Sun/8.12.9) with ESMTP id nA4IcXEo015656; Wed, 4 Nov 2009 18:38:34 GMT
Received: from binky.Central.Sun.COM (binky.Central.Sun.COM [129.153.128.104]) by dm-central-01.central.sun.com (8.13.8+Sun/8.13.8/ENSMAIL,v2.2) with ESMTP id nA4IcXeM009722; Wed, 4 Nov 2009 11:38:33 -0700 (MST)
Received: from binky.Central.Sun.COM (localhost [127.0.0.1]) by binky.Central.Sun.COM (8.14.3+Sun/8.14.3) with ESMTP id nA4IR4jc008279; Wed, 4 Nov 2009 12:27:04 -0600 (CST)
Received: (from nw141292@localhost) by binky.Central.Sun.COM (8.14.3+Sun/8.14.3/Submit) id nA4IR4if008278; Wed, 4 Nov 2009 12:27:04 -0600 (CST)
X-Authentication-Warning: binky.Central.Sun.COM: nw141292 set sender to Nicolas.Williams@sun.com using -f
Date: Wed, 04 Nov 2009 12:27:04 -0600
From: Nicolas Williams <Nicolas.Williams@sun.com>
To: Michael D'Errico <mike-list@pobox.com>
Message-ID: <20091104182704.GA1105@Sun.COM>
References: <20091005162704.8C1B43A6873@core3.amsl.com> <D3DC9D45B39CFC4CB312B2DD279B354C29BADFF7@TK5EX14MBXW653.wingroup.windeploy.ntdev.microsoft.com> <20091030223647.GO1105@Sun.COM> <808FD6E27AD4884E94820BC333B2DB774E7F7C562A@NOK-EUMSG-01.mgdnok.nokia.com> <4AF1C6DD.7030502@pobox.com>
Mime-Version: 1.0
Content-Type: text/plain; charset="us-ascii"
Content-Disposition: inline
In-Reply-To: <4AF1C6DD.7030502@pobox.com>
User-Agent: Mutt/1.5.7i
Cc: channel-binding@ietf.org, tls@ietf.org, sasl@ietf.org
Subject: Re: [CHANNEL-BINDING] [TLS] RESOLVED (Re: [sasl] lasgt call comments (st Call: draft-altman-tls-channel-bindings (Channel Bindings for TLS) to Proposed Standard))
X-BeenThere: channel-binding@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: Discussion of channel binding IANA registry requests and specifications <channel-binding.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/channel-binding>, <mailto:channel-binding-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/channel-binding>
List-Post: <mailto:channel-binding@ietf.org>
List-Help: <mailto:channel-binding-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/channel-binding>, <mailto:channel-binding-request@ietf.org?subject=subscribe>
X-List-Received-Date: Wed, 04 Nov 2009 18:38:18 -0000
On Wed, Nov 04, 2009 at 10:24:29AM -0800, Michael D'Errico wrote: > I don't pretend to know exactly what this feature is supposed to do, > but I think using the word "connection" would be a mistake given its > widespread use meaning TCP connections, etc. At least the word 'connection' is used in RFC5246 _some_ times to mean what we were using it to mean here. > Perhaps using a different word such as "link" would portray the > meaning you want without causing confusion? 'Link' is even worse. We'll probably have to include our own definition in the I-D. The fact that certain words are overloaded does not mean that they cannot be used. This is a fact of life in Internet standards, that terminology varies significantly, and often overlaps, between areas, and even within areas. One way to avoid confusion is to indicate, in each context, the source of one's terminology, and to clarify whenever one must refer to multiple documents with conflicting terminologies. Another way is to invent new terminology whenever conflicts arise. The latter is very difficult to do and to popularize. The former requires discipline. I prefer the former.
- Re: [CHANNEL-BINDING] RESOLVED (Re: [sasl] lasgt … Nicolas Williams
- [CHANNEL-BINDING] Last Call: draft-altman-tls-cha… The IESG
- Re: [CHANNEL-BINDING] Last Call: draft-altman-tls… Simon Josefsson
- Re: [CHANNEL-BINDING] Last Call: draft-altman-tls… Nicolas Williams
- [CHANNEL-BINDING] Unrelated (Re: [TLS] RESOLVED (… Nicolas Williams
- Re: [CHANNEL-BINDING] [sasl] lasgt call comments … Pasi.Eronen
- Re: [CHANNEL-BINDING] lasgt call comments (st Cal… Simon Josefsson
- Re: [CHANNEL-BINDING] lasgt call comments (st Cal… Simon Josefsson
- Re: [CHANNEL-BINDING] [sasl] lasgt call comments … Nicolas Williams
- [CHANNEL-BINDING] lasgt call comments (st Call: d… Larry Zhu
- Re: [CHANNEL-BINDING] lasgt call comments (st Cal… Larry Zhu
- Re: [CHANNEL-BINDING] [TLS] [sasl] lasgt call com… Nicolas Williams
- Re: [CHANNEL-BINDING] [TLS] [sasl] lasgt call com… Larry Zhu
- Re: [CHANNEL-BINDING] [TLS] [sasl] lasgt call com… Nicolas Williams
- Re: [CHANNEL-BINDING] [TLS] RESOLVED (Re: [sasl] … Nicolas Williams
- Re: [CHANNEL-BINDING] [sasl] lasgt call comments … Larry Zhu
- Re: [CHANNEL-BINDING] [TLS] [sasl] lasgt call com… Nicolas Williams
- Re: [CHANNEL-BINDING] [TLS] [sasl] lasgt call com… Martin Rex
- [CHANNEL-BINDING] RESOLVED (Re: [sasl] lasgt call… Nicolas Williams
- Re: [CHANNEL-BINDING] [TLS] RESOLVED (Re: [sasl] … Martin Rex
- Re: [CHANNEL-BINDING] RESOLVED (Re: [sasl] lasgt … Simon Josefsson
- Re: [CHANNEL-BINDING] RESOLVED (Re: [sasl] lasgt … Martin Rex
- Re: [CHANNEL-BINDING] [TLS] RESOLVED (Re: [sasl] … Martin Rex
- Re: [CHANNEL-BINDING] [TLS] RESOLVED (Re: [sasl] … Martin Rex
- Re: [CHANNEL-BINDING] [TLS] RESOLVED (Re: [sasl] … Peter Gutmann
- Re: [CHANNEL-BINDING] [TLS] RESOLVED (Re: [sasl] … Nicolas Williams
- Re: [CHANNEL-BINDING] Unrelated (Re: [TLS] RESOLV… Martin Rex
- Re: [CHANNEL-BINDING] Unrelated (Re: [TLS] RESOLV… Nicolas Williams
- Re: [CHANNEL-BINDING] [TLS] RESOLVED (Re: [sasl] … Martin Rex
- Re: [CHANNEL-BINDING] [TLS] RESOLVED (Re: [sasl] … Pasi.Eronen
- Re: [CHANNEL-BINDING] [TLS] RESOLVED (Re: [sasl] … Pasi.Eronen
- Re: [CHANNEL-BINDING] [TLS] lasgt call comments (… Pasi.Eronen
- Re: [CHANNEL-BINDING] [TLS] lasgt call comments (… Simon Josefsson
- Re: [CHANNEL-BINDING] [TLS] RESOLVED (Re: [sasl] … Nicolas Williams
- Re: [CHANNEL-BINDING] [sasl] [TLS] lasgt call com… Nicolas Williams
- Re: [CHANNEL-BINDING] [TLS] RESOLVED (Re: [sasl] … Jeffrey Hutzelman
- Re: [CHANNEL-BINDING] [sasl] [TLS] lasgt call com… Nicolas Williams
- Re: [CHANNEL-BINDING] [TLS] RESOLVED (Re: [sasl] … Michael D'Errico
- Re: [CHANNEL-BINDING] [TLS] RESOLVED (Re: [sasl] … Nicolas Williams
- Re: [CHANNEL-BINDING] [TLS] RESOLVED (Re: [sasl] … Sam Hartman
- Re: [CHANNEL-BINDING] [TLS] RESOLVED (Re: [sasl] … Nicolas Williams
- Re: [CHANNEL-BINDING] [TLS] lasgt call comments (… Simon Josefsson
- Re: [CHANNEL-BINDING] [TLS] lasgt call comments (… Nicolas Williams
- Re: [CHANNEL-BINDING] [TLS] RESOLVED (Re: [sasl] … Larry Zhu
- [CHANNEL-BINDING] New Problem (Was: Last Call: dr… Nicolas Williams
- Re: [CHANNEL-BINDING] [TLS] New Problem (Was: Las… Larry Zhu
- Re: [CHANNEL-BINDING] [TLS] New Problem (Was: Las… Nicolas Williams