Re: [Isis-wg] More support? Re: WG Last Call for draft-ietf-isis-sbfd-discriminator-02

"Les Ginsberg (ginsberg)" <ginsberg@cisco.com> Fri, 02 October 2015 00:31 UTC

Return-Path: <ginsberg@cisco.com>
X-Original-To: isis-wg@ietfa.amsl.com
Delivered-To: isis-wg@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 51C561A90F4 for <isis-wg@ietfa.amsl.com>; Thu, 1 Oct 2015 17:31:11 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -14.51
X-Spam-Level:
X-Spam-Status: No, score=-14.51 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_HI=-5, SPF_PASS=-0.001, T_RP_MATCHES_RCVD=-0.01, USER_IN_DEF_DKIM_WL=-7.5] autolearn=ham
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id zlwz51MaILXt for <isis-wg@ietfa.amsl.com>; Thu, 1 Oct 2015 17:31:06 -0700 (PDT)
Received: from rcdn-iport-4.cisco.com (rcdn-iport-4.cisco.com [173.37.86.75]) (using TLSv1 with cipher RC4-SHA (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 9D8111A90EF for <isis-wg@ietf.org>; Thu, 1 Oct 2015 17:31:06 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=cisco.com; i=@cisco.com; l=25850; q=dns/txt; s=iport; t=1443745866; x=1444955466; h=from:to:cc:subject:date:message-id:references: in-reply-to:mime-version; bh=R2/yRgaLFZbv38OQM0ZGBcIyoWeDtGxoDdPakUzsaUk=; b=QrhY6nLTzHel64A3Bjv+IQEGSiICPha0fxqcqoT63/G++DQ8hl/9ttp9 0a7ORAxno8VGtjJ6bRUvY9PyEaPAUUrX6VwgYL8oAAQQHWL/fwtPWsCgp MHAlP8iIUKq2+mDPIsrgA476eFSNjF6ZzEStOvZnQi9X+50r3anJ/sCXH g=;
X-IronPort-Anti-Spam-Filtered: true
X-IronPort-Anti-Spam-Result: A0DyAQBVzw1W/4cNJK1eglpNVG4GvWwBDYFxAQmFeQIcgRw4FAEBAQEBAQGBCoQkAQEBBAEBARoGCkELDAQCAQgOAwQBASgDAgICHwYLFAkIAgQOBQiIEQMSDbcRjzYNhQ0BAQEBAQEBAQEBAQEBAQEBAQEBAQETBIZzhH6CUII5BAYBBoJjgUMFkkaDMwGFFYYNgWyBVYdZimKHRwEfAQFCghEdFoE+cYhygQYBAQE
X-IronPort-AV: E=Sophos; i="5.17,620,1437436800"; d="scan'208,217"; a="33808910"
Received: from alln-core-2.cisco.com ([173.36.13.135]) by rcdn-iport-4.cisco.com with ESMTP; 02 Oct 2015 00:31:05 +0000
Received: from XCH-ALN-004.cisco.com (xch-aln-004.cisco.com [173.36.7.14]) by alln-core-2.cisco.com (8.14.5/8.14.5) with ESMTP id t920V53t012167 (version=TLSv1/SSLv3 cipher=AES256-SHA bits=256 verify=FAIL); Fri, 2 Oct 2015 00:31:05 GMT
Received: from xch-aln-001.cisco.com (173.36.7.11) by XCH-ALN-004.cisco.com (173.36.7.14) with Microsoft SMTP Server (TLS) id 15.0.1104.5; Thu, 1 Oct 2015 19:31:04 -0500
Received: from xch-aln-001.cisco.com ([173.36.7.11]) by XCH-ALN-001.cisco.com ([173.36.7.11]) with mapi id 15.00.1104.000; Thu, 1 Oct 2015 19:31:04 -0500
From: "Les Ginsberg (ginsberg)" <ginsberg@cisco.com>
To: Alia Atlas <akatlas@gmail.com>
Thread-Topic: [Isis-wg] More support? Re: WG Last Call for draft-ietf-isis-sbfd-discriminator-02
Thread-Index: AQHQ/DRkU8/CZEbj+0Otnu0Oul1qZ55WuO5wgAA8u6CAAHmLgP//6PiA
Date: Fri, 02 Oct 2015 00:31:04 +0000
Message-ID: <8f09b23610e94fa6a2209062f2b8ef87@XCH-ALN-001.cisco.com>
References: <104E712C-0351-4ABD-9D5E-7A6E5194E74E@chopps.org> <87oagikhhv.fsf@chopps.org> <8df71da368534e33b1f9c82ee67ecf48@XCH-ALN-001.cisco.com> <ef44e1da733c416c852754eb9f60882c@XCH-ALN-001.cisco.com> <CAG4d1rf=e2T_wt3yEYytLoXZn2=ari-qarRYASVqfy8pcYC7WQ@mail.gmail.com>
In-Reply-To: <CAG4d1rf=e2T_wt3yEYytLoXZn2=ari-qarRYASVqfy8pcYC7WQ@mail.gmail.com>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach:
X-MS-TNEF-Correlator:
x-ms-exchange-transport-fromentityheader: Hosted
x-originating-ip: [10.154.208.14]
Content-Type: multipart/alternative; boundary="_000_8f09b23610e94fa6a2209062f2b8ef87XCHALN001ciscocom_"
MIME-Version: 1.0
Archived-At: <http://mailarchive.ietf.org/arch/msg/isis-wg/UI0BTSZLRW1xnw8KNt4PcM-HivQ>
Cc: Christian Hopps <chopps@chopps.org>, ISIS-WG <isis-wg@ietf.org>
Subject: Re: [Isis-wg] More support? Re: WG Last Call for draft-ietf-isis-sbfd-discriminator-02
X-BeenThere: isis-wg@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: IETF IS-IS working group <isis-wg.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/isis-wg>, <mailto:isis-wg-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/isis-wg/>
List-Post: <mailto:isis-wg@ietf.org>
List-Help: <mailto:isis-wg-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/isis-wg>, <mailto:isis-wg-request@ietf.org?subject=subscribe>
X-List-Received-Date: Fri, 02 Oct 2015 00:31:11 -0000

Alia –

It is not that I strongly object to the new behavior – it just seems a bit odd.

The document gets adopted by the WG – that clearly requires some level of support.
The document then gets presented – often multiple times – and undergoes multiple revisions – each of which is based on feedback received.
Once the authors/chairs believe the document is mature last call is requested.

For all the folks who have participated in the review of the document the work is done and clearly there has been interest in the work – an inspection of the WG archives reveals that.

I don’t know of any document that goes to last call w/o any comment whatsoever during the time it is a WG doc. If that is the case I would think the chairs are justified in saying there is no reason to go to last call because no work has been done on the document post becoming a WG item.
If you want evidence of review it should be found in the WG archives – not in a statement in response to last call.

I have always interpreted last call as an opportunity for folks who believe the document is not yet mature to say so – but instead it seems  to be used as a way of verifying that there is actually interest in the document – which is too late and too perfunctory for my tastes.

   Les


From: Alia Atlas [mailto:akatlas@gmail.com]
Sent: Thursday, October 01, 2015 1:44 PM
To: Les Ginsberg (ginsberg)
Cc: Christian Hopps; ISIS-WG
Subject: Re: [Isis-wg] More support? Re: WG Last Call for draft-ietf-isis-sbfd-discriminator-02

Les,

It's all too common for interest in a draft to peak at WG adoption.
Particularly if there hasn't been much active discussion, it is very useful to
know that a draft has gotten significant review, is still needed, and is
ready to be published.

Having clear evidence of WG consensus at WGLC assures that the work is
still needed and ready.

There are some drafts where publication is requested and one wonders if anyone
has fully read the draft or just looked at diffs.

Hope that helps,
Alia

On Thu, Oct 1, 2015 at 2:31 PM, Les Ginsberg (ginsberg) <ginsberg@cisco.com<mailto:ginsberg@cisco.com>> wrote:
Some additional context here...

My remarks regarding expectations of support during last call are not specifically aimed at the SBFD draft nor the IS-IS WG. I see this change of behavior across multiple WGs and I am wondering why?
Some enlightenment from the ADs would be appreciated.

   Les


> -----Original Message-----
> From: Isis-wg [mailto:isis-wg-bounces@ietf.org<mailto:isis-wg-bounces@ietf.org>] On Behalf Of Les Ginsberg
> (ginsberg)
> Sent: Thursday, October 01, 2015 7:57 AM
> To: Christian Hopps; ISIS-WG
> Subject: Re: [Isis-wg] More support? Re: WG Last Call for draft-ietf-isis-sbfd-
> discriminator-02
>
> FWIW...
>
> I support this as co-author.
>
> But, it also seems relevant to comment on what seems to be a "behavior
> change".
>
> In the past, expressions of support were expected when asking if a
> document should be made a WG item. However, once that happened, when
> a last call was issued it was only expected that folks should express
> reservations if they had any. Expressions of support for last call were not
> expected because it was assumed that since the WG had already been
> actively working on the document since it became a WG item support was
> implicit.
>
> Now however it seems that there is an expectation that despite all of the
> history of the document post WG acceptance folks are supposed to once
> again say "Yes I support this".
> When did this behavior change and could the chairs and/or the ADs explain
> why the change was made?
>
> Thanx.
>
>    Les
>
>
> > -----Original Message-----
> > From: Isis-wg [mailto:isis-wg-bounces@ietf.org<mailto:isis-wg-bounces@ietf.org>] On Behalf Of Christian
> > Hopps
> > Sent: Thursday, October 01, 2015 3:31 AM
> > To: ISIS-WG
> > Cc: chopps@chopps.org<mailto:chopps@chopps.org>
> > Subject: [Isis-wg] More support? Re: WG Last Call for
> > draft-ietf-isis-sbfd-
> > discriminator-02
> >
> >
> > Hi Folks,
> >
> > far there's not been much public indication of support for this draft.
> > It did clear WG last call and we can move it forward on the belief
> > that everyone is quietly accepting it; however, I would prefer it if a
> > few more people could be vocal in their support of the document.
> >
> > Thanks,
> > Chris.
> >
> > Christian Hopps <chopps@chopps.org<mailto:chopps@chopps.org>> writes:
> >
> > > Hi Folks,
> > >
> > > We are starting a WG Last Call on the following draft.
> > >
> > > “Advertising S-BFD Discriminators in IS-IS”
> > > https://datatracker.ietf.org/doc/draft-ietf-isis-sbfd-discriminator/
> > >
> > > The LC is set to expire 3 weeks from now (allowing for common
> > > vacation
> > > time) on Friday, September 4th, 2015.
> > >
> > > Thanks,
> > > Chris & Hannes.
> > >
> > > _______________________________________________
> > > Isis-wg mailing list
> > > Isis-wg@ietf.org<mailto:Isis-wg@ietf.org>
> > > https://www.ietf.org/mailman/listinfo/isis-wg
> >
> > _______________________________________________
> > Isis-wg mailing list
> > Isis-wg@ietf.org<mailto:Isis-wg@ietf.org>
> > https://www.ietf.org/mailman/listinfo/isis-wg
> _______________________________________________
> Isis-wg mailing list
> Isis-wg@ietf.org<mailto:Isis-wg@ietf.org>
> https://www.ietf.org/mailman/listinfo/isis-wg
_______________________________________________
Isis-wg mailing list
Isis-wg@ietf.org<mailto:Isis-wg@ietf.org>
https://www.ietf.org/mailman/listinfo/isis-wg