Re: Last Call: 'TLS User Mapping Extension' to Proposed Standard

"Steven M. Bellovin" <smb@cs.columbia.edu> Sun, 19 February 2006 03:32 UTC

Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com) by megatron.ietf.org with esmtp (Exim 4.43) id 1FAfJ7-0003uY-9n; Sat, 18 Feb 2006 22:32:21 -0500
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org) by megatron.ietf.org with esmtp (Exim 4.43) id 1FAfJ5-0003u3-5q; Sat, 18 Feb 2006 22:32:19 -0500
Received: from machshav.com ([147.28.0.16]) by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1FAfJ1-0005pQ-St; Sat, 18 Feb 2006 22:32:19 -0500
Received: from berkshire.machshav.com (localhost [127.0.0.1]) by machshav.com (Postfix) with ESMTP id CF927FB28D; Sat, 18 Feb 2006 22:32:14 -0500 (EST)
Received: from cs.columbia.edu (localhost [127.0.0.1]) by berkshire.machshav.com (Postfix) with ESMTP id 85B213C028D; Sat, 18 Feb 2006 22:32:13 -0500 (EST)
X-Mailer: exmh version 2.6.3 04/04/2003 with nmh-1.0.4
From: "Steven M. Bellovin" <smb@cs.columbia.edu>
To: Eric Rescorla <ekr@networkresonance.com>
In-Reply-To: (Your message of "Sat, 18 Feb 2006 17:31:13 PST.") <20060219013238.779CC22241D@laser.networkresonance.com>
Mime-Version: 1.0
Content-Type: text/plain; charset="us-ascii"
Date: Sat, 18 Feb 2006 22:32:13 -0500
Message-Id: <20060219033213.85B213C028D@berkshire.machshav.com>
X-Spam-Score: 0.0 (/)
X-Scan-Signature: cf4fa59384e76e63313391b70cd0dd25
Cc: iesg@ietf.org, ietf@ietf.org, tls@ietf.org
Subject: Re: Last Call: 'TLS User Mapping Extension' to Proposed Standard
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
Errors-To: ietf-bounces@ietf.org

In message <20060219013238.779CC22241D@laser.networkresonance.com>, Eric Rescor
la writes:

>
>Since the IETF would not have change control, this is an inappropriate
>work item for the TLS WG and therefore the authors appear to have
>decided on an Individual Submission. The reason for the intended status
>of Proposed Standard 

Do we have a process issue here?  Can we have a Proposed Standard
without the IETF having change control?  (2026 speaks of change control 
only in the context of a WG.)

		--Steven M. Bellovin, http://www.cs.columbia.edu/~smb



_______________________________________________
Ietf mailing list
Ietf@ietf.org
https://www1.ietf.org/mailman/listinfo/ietf