Re: Withdrawing sponsorship of draft-housley-tls-authz-extns

Brian E Carpenter <brian.e.carpenter@gmail.com> Fri, 15 June 2007 11:33 UTC

Return-path: <ietf-bounces@ietf.org>
Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com) by megatron.ietf.org with esmtp (Exim 4.43) id 1HzA3W-0002LO-Dk; Fri, 15 Jun 2007 07:33:30 -0400
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org) by megatron.ietf.org with esmtp (Exim 4.43) id 1HzA3V-0002LJ-2z for ietf@ietf.org; Fri, 15 Jun 2007 07:33:29 -0400
Received: from ug-out-1314.google.com ([66.249.92.172]) by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1HzA3T-0000UW-LU for ietf@ietf.org; Fri, 15 Jun 2007 07:33:29 -0400
Received: by ug-out-1314.google.com with SMTP id k3so70524ugf for <ietf@ietf.org>; Fri, 15 Jun 2007 04:33:26 -0700 (PDT)
DKIM-Signature: a=rsa-sha1; c=relaxed/relaxed; d=gmail.com; s=beta; h=domainkey-signature:received:received:message-id:date:from:user-agent:mime-version:to:cc:subject:references:in-reply-to:content-type:content-transfer-encoding; b=i425JxayzNOtx+m0PtPaiHpEFoXN217mWWqBcKYQMooA7Wxgpw8kZS5PE4y4s5CIPpWhO24zdydp3dMq9tzUwmIdmpdwIdrQpbUbHjpXgVMsw4oMPiSG//WPkpSbAh3qNlA8tQtUezIsDulaXD16Ln/2Qh78UcgFEHHU6Vskaks=
DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=beta; h=received:message-id:date:from:user-agent:mime-version:to:cc:subject:references:in-reply-to:content-type:content-transfer-encoding; b=YbNaBSxMlPctGWoE/9fm8STHNtQEnPBxZhD+/a2hSeBBucno4JJzGQu2RizMnN5zyF5NVsu1mhTH/GsQd0xIzQJI99FDT0TqSEnBRtz8rdRP+Xk4F+TRk7Fckgjdv/ue6RYxMMCgNjHFN5GqPySovqzJ9VpI+w9w0sJKOGvLraI=
Received: by 10.82.152.16 with SMTP id z16mr5498360bud.1181907206553; Fri, 15 Jun 2007 04:33:26 -0700 (PDT)
Received: from ?10.10.50.1? ( [213.3.13.1]) by mx.google.com with ESMTP id z37sm6997815ikz.2007.06.15.04.33.25 (version=SSLv3 cipher=RC4-MD5); Fri, 15 Jun 2007 04:33:26 -0700 (PDT)
Message-ID: <46727903.20305@gmail.com>
Date: Fri, 15 Jun 2007 13:33:23 +0200
From: Brian E Carpenter <brian.e.carpenter@gmail.com>
User-Agent: Thunderbird 1.5.0.12 (Windows/20070509)
MIME-Version: 1.0
To: Pasi.Eronen@nokia.com
References: <tslveduxfp2.fsf@mit.edu><B356D8F434D20B40A8CEDAEC305A1F24043F6B4D@esebe105.NOE.Nokia.com><466E959D.80601@cisco.com> <466EA98D.9010401@dcrocker.net><D2C66431AE5E7F688AB7DA5C@[192.168.0.3]> <200706150008.l5F08EXt014583@cichlid.raleigh.ibm.com> <B356D8F434D20B40A8CEDAEC305A1F240442B881@esebe105.NOE.Nokia.com>
In-Reply-To: <B356D8F434D20B40A8CEDAEC305A1F240442B881@esebe105.NOE.Nokia.com>
Content-Type: text/plain; charset="UTF-8"; format="flowed"
Content-Transfer-Encoding: 7bit
X-Spam-Score: 0.0 (/)
X-Scan-Signature: bb8f917bb6b8da28fc948aeffb74aa17
Cc: narten@us.ibm.com, ietf@ietf.org
Subject: Re: Withdrawing sponsorship of draft-housley-tls-authz-extns
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

On 2007-06-15 10:25, Pasi.Eronen@nokia.com wrote:
> Thomas Narten wrote:
> 
>> If the above text were in effect today, would it be sufficient to
>> cover the situation at issue here? (Now would be an excellent time
>> to consider updates/clarifications to the above text.)
> 
> I don't think so. The text allows IESG to override the allocation
> procedures when they judge there is "strong IETF consensus" to do 
> so.
> 
> In the situation at issue here: IMHO the main question is whether 
> we have rough consensus that this particular draft should be 
> published as non-Standards Track RFC.
> 
> If the IESG thinks we have this consensus, they would just approve 
> the document, and the override procedure would not be needed. 

Yes it would, if registration normally requires Standards Action.

> If 
> the IESG thinks there is no consensus (or it's too rough), the 
> override rule wouldn't apply.
> 
> So while I think the override rule might be valuable in some
> cases, it doesn't seem to help here. 

I think another aspect is whether the IETF chooses to give IANA
some discretion to document usage which is widespread, but not
covered by any IETF document or procedure. It may not be appropriate
to expect the IESG to spend time on every case, or even to look for
consensus when what is being documented is simply a fact of life.
As a friend of mine used to say, you can't vote on facts.

   Brian

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