RE: WGLC for BFD over Link Aggregate Group Interfaces - ends November 8

"Nobo Akiya (nobo)" <nobo@cisco.com> Mon, 11 November 2013 15:21 UTC

Return-Path: <nobo@cisco.com>
X-Original-To: rtg-bfd@ietfa.amsl.com
Delivered-To: rtg-bfd@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 68CF421F9EDA for <rtg-bfd@ietfa.amsl.com>; Mon, 11 Nov 2013 07:21:10 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -10.549
X-Spam-Level:
X-Spam-Status: No, score=-10.549 tagged_above=-999 required=5 tests=[AWL=0.050, BAYES_00=-2.599, RCVD_IN_DNSWL_HI=-8]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id ikuBhywt6zZU for <rtg-bfd@ietfa.amsl.com>; Mon, 11 Nov 2013 07:21:05 -0800 (PST)
Received: from rcdn-iport-9.cisco.com (rcdn-iport-9.cisco.com [173.37.86.80]) by ietfa.amsl.com (Postfix) with ESMTP id 2FBFB11E817E for <rtg-bfd@ietf.org>; Mon, 11 Nov 2013 07:21:05 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=cisco.com; i=@cisco.com; l=2793; q=dns/txt; s=iport; t=1384183265; x=1385392865; h=from:to:cc:subject:date:message-id:references: in-reply-to:content-transfer-encoding:mime-version; bh=u8y2ftkp1AMcBJdsixuP3aBE6/Gii4LcLrTSUFvrWXo=; b=awjwh6qMkRVL1a0KgTso5ozx6yVpIJ/DmsoCFRjNZXk0hUCCYK9O2X2L uDWY31r25YNkb1CX6aJ5lYn2ZTXodVits5lnUE6kNntfjQSvxRxLgwNHW sLS/3Rq06y000OSd4hnrriYTqeJdDZS021fMidKJAC5QpLuO6sFjFJGVC c=;
X-IronPort-Anti-Spam-Filtered: true
X-IronPort-Anti-Spam-Result: AhoFALX0gFKtJV2c/2dsb2JhbABZgmYhOFO/F4E6FnSCJQEBAQQ6NAsMBAIBCBEEAQEBChQJBzIUCQgCBAENBQiHeQEMvXuOHoEYMQcGgxqBEAOULoUQkFuDJoFxOQ
X-IronPort-AV: E=Sophos;i="4.93,678,1378857600"; d="scan'208";a="280294744"
Received: from rcdn-core-5.cisco.com ([173.37.93.156]) by rcdn-iport-9.cisco.com with ESMTP; 11 Nov 2013 15:21:04 +0000
Received: from xhc-aln-x02.cisco.com (xhc-aln-x02.cisco.com [173.36.12.76]) by rcdn-core-5.cisco.com (8.14.5/8.14.5) with ESMTP id rABFL4Us027355 (version=TLSv1/SSLv3 cipher=AES128-SHA bits=128 verify=FAIL); Mon, 11 Nov 2013 15:21:04 GMT
Received: from xmb-aln-x01.cisco.com ([fe80::747b:83e1:9755:d453]) by xhc-aln-x02.cisco.com ([173.36.12.76]) with mapi id 14.03.0123.003; Mon, 11 Nov 2013 09:21:04 -0600
From: "Nobo Akiya (nobo)" <nobo@cisco.com>
To: "Carlos Pignataro (cpignata)" <cpignata@cisco.com>, Jeffrey Haas <jhaas@pfrc.org>
Subject: RE: WGLC for BFD over Link Aggregate Group Interfaces - ends November 8
Thread-Topic: WGLC for BFD over Link Aggregate Group Interfaces - ends November 8
Thread-Index: AQHO3mRiUajq3tTg6U2yq9mkMQcIrZogJDog
Date: Mon, 11 Nov 2013 15:21:03 +0000
Message-ID: <CECE764681BE964CBE1DFF78F3CDD3941DEE0BDE@xmb-aln-x01.cisco.com>
References: <20131024191431.GO17538@pfrc> <6C38E01D-2C15-4F18-9A19-06486DC48C50@cisco.com>
In-Reply-To: <6C38E01D-2C15-4F18-9A19-06486DC48C50@cisco.com>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach:
X-MS-TNEF-Correlator:
x-originating-ip: [161.44.213.104]
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: quoted-printable
MIME-Version: 1.0
Cc: "rtg-bfd@ietf.org" <rtg-bfd@ietf.org>
X-BeenThere: rtg-bfd@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: "RTG Area: Bidirectional Forwarding Detection DT" <rtg-bfd.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/rtg-bfd>, <mailto:rtg-bfd-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/rtg-bfd>
List-Post: <mailto:rtg-bfd@ietf.org>
List-Help: <mailto:rtg-bfd-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/rtg-bfd>, <mailto:rtg-bfd-request@ietf.org?subject=subscribe>
X-List-Received-Date: Mon, 11 Nov 2013 15:21:10 -0000

Carlos, thank you for gauging the WGLC consensus on draft-ietf-bfd-on-lags document.

Authors, please address only the idnits and post a new ID.

-Nobo
(as draft-ietf-bfd-on-lags shepherd)

> -----Original Message-----
> From: rtg-bfd-bounces@ietf.org [mailto:rtg-bfd-bounces@ietf.org] On
> Behalf Of Carlos Pignataro (cpignata)
> Sent: Sunday, November 10, 2013 5:30 PM
> To: Jeffrey Haas
> Cc: rtg-bfd@ietf.org
> Subject: Re: WGLC for BFD over Link Aggregate Group Interfaces - ends
> November 8
> 
> WG:
> 
> Hi,
> 
> The BFD co-chairs asked me to gauge consensus on the WGLC for draft-ietf-
> bfd-on-lags-01, which ended November 8th.
> 
> There is clearly good support for this document, and I see strong consensus
> to move forward including the mention of interoperable implementations.
> There was also a good discussion (and conclusion) on the list about interface
> identification.
> 
> I captured the following notes:
> 1. Please fix idnits warnings
> 
> Thanks,
> 
> - Carlos.
> 
> On Oct 24, 2013, at 3:14 PM, Jeffrey Haas <jhaas@pfrc.org> wrote:
> 
> > This email is to initiate working group last call on the BFD on Link
> > Aggregate Group Interfaces document:
> >
> > http://tools.ietf.org/html/draft-ietf-bfd-on-lags-01
> >
> > The last call will complete on November 8, the end of IETF week.  Time
> > will be available during the Vancouver IETF BFD session to discuss
> > last call comments.
> >
> > Nobo Akiya will be serving as document shepherd (RFC 4858) for this
> WGLC.
> >
> > Due to the small nature of the BFD working group and the fact that
> > both working group chairs have contributed to this document, we have
> > gotten Carlos Pignataro (cpignata@cisco.com) to volunteer to serve as
> > an independent party to gauge working group consensus.
> >
> > In order to facilitate the transparency of this WGLC, please remember
> > to send all comments to the working group mailing list.
> >
> > IPR declarations have been filed against this draft and the document
> > authors and contributors have been polled for any further IPR.
> > Current IPR declarations may be seen at the following link:
> >
> > http://datatracker.ietf.org/ipr/search/?option=document_search&id=draf
> > t-ietf-bfd-on-lags
> >
> > If you are aware of additional IPR against this document please
> > declare so, per the IETF Note Well.
> >
> > Finally, the IEEE has expressed interest in the disposition of this draft.
> > They will likely provide additional commentary, if any, via the IETF
> > liaison process.  This process will likely happen after WGLC
> > concludes.  Depending on their feedback, WGLC may re-open to address
> their concerns.
> >
> > -- Jeff (for the chairs)