Re: IONs & discuss criteria
[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
Re: IONs & discuss criteria
- To: Russ Housley <housley at vigilsec.com>, "Dondeti, Lakshminath" <ldondeti at qualcomm.com>
- Subject: Re: IONs & discuss criteria
- From: Ted Hardie <hardie at qualcomm.com>
- Date: Mon, 10 Mar 2008 10:13:53 -0400
- Cc: "chair at ietf.org" <chair at ietf.org>, "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=hardie at qualcomm.com; q=dns/txt; s=qcdkim; t=1205158439; x=1236694439; h=mime-version:message-id:in-reply-to:references:date:to: from:subject:cc:content-type:x-ironport-av; z=Mime-Version:=201.0|Message-Id:=20<p06240601c3faf100b405 @[130.129.17.237]>|In-Reply-To:=20<200803100418.m2A4IH7c0 12813 at hobbiton.qualcomm.com>|References:=20<p06240606c3f5 fb872ae5 at [24.4.239.115]>=0D=0A=20<94D79D1D-9087-4776-8117 -DC3E5FB2B666 at cisco.com>=0D=0A=20<47D06388.3070008 at qualco mm.com>=20<tslmypbiks0.fsf at mit.edu>=0D=0A=20<47D06E7A.304 0904 at qualcomm.com>=0D=0A=20<200803070018.m270GZNt025723 at m oria.qualcomm.com>=0D=0A=20<47D09379.9090300 at qualcomm.com >=0D=0A=20<200803071857.m27Iuqnw018022 at moria.qualcomm.com >=0D=0A=20<47D245B6.3010207 at qualcomm.com>=0D=0A=20<200803 09154525.1EB7A28C298 at core3.amsl.com>=0D=0A=20<p06240602c3 fa516c2c5b at [10.150.134.15]>=0D=0A=20<200803100418.m2A4IH7 c012813 at hobbiton.qualcomm.com>|Date:=20Mon,=2010=20Mar=20 2008=2010:13:53=20-0400|To:=20Russ=20Housley=20<housley at v igilsec.com>,=0D=0A=20=20=20=20=20=20=20=20"Dondeti,=20La kshminath"=09<ldondeti at qualcomm.com>|From:=20Ted=20Hardie =20<hardie at qualcomm.com>|Subject:=20Re:=20IONs=20&=20disc uss=20criteria|Cc:=20"chair at ietf.org"=20<chair at ietf.org>, =20"ietf at ietf.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> |Content-Type:=20text/plain=3B=20charset=3D"us-ascii" |X-IronPort-AV:=20E=3DMcAfee=3Bi=3D"5200,2160,5247"=3B=20 a=3D"1005838"; bh=6K9lYgHLMSpVNSsxmU7+ZvofzcQG2bUKFC6z7tlaQ+Y=; b=GEPV42UU8qYsDnPp/CELzt9McnN/50lP7kGlgQfz0RR3qNOEQ0MAocix 5yX/yeBinDLe/XfoVdWYdoRcNmezyaRPlnFg1GBrztYDH4OsHUZ6atR5l Ss19/585SR32Lzw2JKjF55ljBsPWJwU/ErlIVEcUp1o3x0tjC/nzZOtZk g=;
- In-reply-to: <200803100418.m2A4IH7c012813 at hobbiton.qualcomm.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]> <94D79D1D-9087-4776-8117-DC3E5FB2B666 at cisco.com> <47D06388.3070008 at qualcomm.com> <tslmypbiks0.fsf at mit.edu> <47D06E7A.3040904 at qualcomm.com> <200803070018.m270GZNt025723 at moria.qualcomm.com> <47D09379.9090300 at qualcomm.com> <200803071857.m27Iuqnw018022 at moria.qualcomm.com> <47D245B6.3010207 at qualcomm.com> <20080309154525.1EB7A28C298 at core3.amsl.com> <p06240602c3fa516c2c5b at [10.150.134.15]> <200803100418.m2A4IH7c012813 at hobbiton.qualcomm.com>
- Sender: ietf-bounces at ietf.org
At 9:18 PM -0700 3/9/08, Russ Housley wrote:
>
>I really disagree. Gen-ART Reviews begin this way:
>
> I have been selected as the General Area Review Team (Gen-ART)
> reviewer for this draft (for background on Gen-ART, please see
> _http://www.alvestrand.no/ietf/gen/art/gen-art-FAQ.html_).
>
> Please resolve these comments along with any other Last Call comments
> you may receive.
>
>This tells the recipients that the review fits exactly the role you
>describe above.
But your behavior does not tell the recipient that. If they were
being treated as general Last Call comments, it would be up to
the shepherd and sponsoring AD to resolve them, not up to
the General Area AD. That leaves one set of people on the hook
for making sure they are done and deciding when they are,
and it is the same set no matter how the Last Call comment
is generated. Your mechanism privileges one set
over others (in that they are more likely to be held as blocking
until resolved), is likely to be slower (since yet another busy person
must be informed that something is resolved, and may miss it
when it was), and does not encourage things to push earlier than
Last Call (which is the opportunity I think you're missing).
Ted Hardie
_______________________________________________
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.