Re: IONs & discuss criteria
[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
Re: IONs & discuss criteria
- To: Brian E Carpenter <brian.e.carpenter at gmail.com>
- Subject: Re: IONs & discuss criteria
- From: Lakshminath Dondeti <ldondeti at qualcomm.com>
- Date: Thu, 06 Mar 2008 17:06:54 -0800
- Cc: "chair at ietf.org" <chair at ietf.org>, Sam Hartman <hartmans-ietf at mit.edu>, "ietf at ietf.org" <ietf at ietf.org>, "iesg at ietf.org" <iesg at ietf.org>
- Delivered-to: ietfarch-ietf-web-archive at core3.amsl.com
- Delivered-to: ietf at core3.amsl.com
- Dkim-signature: v=1; a=rsa-sha256; c=simple/simple; d=qualcomm.com; i=ldondeti at qualcomm.com; q=dns/txt; s=qcdkim; t=1204852008; x=1236388008; h=message-id:date:from:user-agent:mime-version:to:cc: subject:references:in-reply-to:content-type: content-transfer-encoding:x-ironport-av; z=Message-ID:=20<47D0952E.7010308 at qualcomm.com>|Date:=20Th u,=2006=20Mar=202008=2017:06:54=20-0800|From:=20Lakshmina th=20Dondeti=20<ldondeti at qualcomm.com>|User-Agent:=20Thun derbird=202.0.0.12=20(Windows/20080213)|MIME-Version:=201 .0|To:=20Brian=20E=20Carpenter=20<brian.e.carpenter at gmail .com>|CC:=20Dave=20Crocker=20<dhc2 at dcrocker.net>,=20"chai r at ietf.org"=20<chair at ietf.org>,=0D=0A=20=20=20=20=20=20 =20=20Sam=20Hartman=20<hartmans-ietf at mit.edu>,=20"ietf at ie tf.org"=20<ietf at ietf.org>,=0D=0A=20=20=20=20=20=20=20=20" iesg at ietf.org"=20<iesg at ietf.org>|Subject:=20Re:=20IONs=20 &=20discuss=20criteria|References:=20<p06240606c3f5fb872a e5 at [24.4.239.115]>=09<20080306211148.28D4D28C834 at core3.am sl.com>=09<p06240609c3f6109f1c58 at [24.4.239.115]>=09<tslve 3zil4y.fsf at mit.edu>=09<p0624060dc3f6272c6553 at [24.4.239.11 5]>=09<tsl8x0vh2pc.fsf at mit.edu>=09<47D07F6A.2090102 at dcroc ker.net>=20<47D087FB.7000606 at gmail.com>|In-Reply-To:=20<4 7D087FB.7000606 at gmail.com>|Content-Type:=20text/plain=3B =20charset=3DISO-8859-15=3B=20format=3Dflowed |Content-Transfer-Encoding:=207bit|X-IronPort-AV:=20E=3DM cAfee=3Bi=3D"5200,2160,5246"=3B=20a=3D"969020"; bh=SpFJaXnAYukMVcHsIRzp/VVHn2JgwnMteQePuKTjlDA=; b=gA85tKG5Y7uv5fyWTRfaH0s6ZiZC/xyNwwEL/9ub2/XpfCPXdLYp7nCv 39+lgvFlwRljqcjo6tpEFvG8/rZWgb1L78jifbPrm5b4ihCLVcqKewzgT JuaTPwQ7VEw+fewcKEjcIBNVEA9SSCggX/JjV/xiywxjeyWq4IolCBjg2 Q=;
- In-reply-to: <47D087FB.7000606 at gmail.com>
- List-help: <mailto:ietf-request@ietf.org?subject=help>
- List-id: IETF Discussion <ietf.ietf.org>
- List-post: <mailto:ietf@ietf.org>
- List-subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
- List-unsubscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
- References: <p06240606c3f5fb872ae5 at [24.4.239.115]> <20080306211148.28D4D28C834 at core3.amsl.com> <p06240609c3f6109f1c58 at [24.4.239.115]> <tslve3zil4y.fsf at mit.edu> <p0624060dc3f6272c6553 at [24.4.239.115]> <tsl8x0vh2pc.fsf at mit.edu> <47D07F6A.2090102 at dcrocker.net> <47D087FB.7000606 at gmail.com>
- Sender: ietf-bounces at ietf.org
- User-agent: Thunderbird 2.0.0.12 (Windows/20080213)
Brian,
A small clarification below on the reference to the interpretation
problems related to 3777:
On 3/6/2008 4:10 PM, Brian E Carpenter wrote:
> Dave,
>
> On 2008-03-07 12:34, Dave Crocker wrote:
>> Sam Hartman wrote:
>>> Making it a BCP will make the interpretation problem worse not better.
>>
>> How?
>
> To some extent that depends on how carefully the putative BCP
> is crafted, with "should" and when to disregard "should" being
> very precise. What I think we've seen, with 2026 over the years,
> and apparently this year with 3777, is that it's virtually
I am not sure whether you have made it to the appendix in my report, but
the disagreements in interpretation of 3777 have a history (see Page
37). The only thing special about the current nomcom is that we chose
to bring it to the community's attention. In Ralph's case, he brought
it to the IESG and IAB's attention in March 2006.
thanks,
Lakshminath
Nomcom 2007-8 Chair
> impossible to write precise procedural text that deals with
> completely unexpected circumstances. Yet if the text has the
> force of a BCP, it becomes very hard to interpret it flexibly
> when flexibility is clearly needed. I don't know if that
> is Sam's point, of course.
>
> Brian
> _______________________________________________
> IETF mailing list
> IETF at ietf.org
> https://www.ietf.org/mailman/listinfo/ietf
>
_______________________________________________
IETF mailing list
IETF at ietf.org
https://www.ietf.org/mailman/listinfo/ietf
Note Well: Messages sent to this mailing list are the opinions
of the senders and do not imply endorsement by the IETF.
Note: Messages sent to this list are the opinions of the senders and do not imply endorsement by the IETF.