IETF Logo Mail Archive

RE: Adoption request for draft-tanmir-rtgwg-bfd-mc-lag

John Messenger <jmessenger@advaoptical.com> Thu, 23 March 2017 19:45 UTC

Return-Path: <jmessenger@advaoptical.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 492E813164E for <rtg-bfd@ietfa.amsl.com>; Thu, 23 Mar 2017 12:45:49 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.919
X-Spam-Level:
X-Spam-Status: No, score=-1.919 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_NONE=-0.0001, RCVD_IN_MSPIKE_H3=-0.01, RCVD_IN_MSPIKE_WL=-0.01, RP_MATCHES_RCVD=-0.001, URIBL_BLOCKED=0.001] autolearn=ham autolearn_force=no
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 UENy72SJlcot for <rtg-bfd@ietfa.amsl.com>; Thu, 23 Mar 2017 12:45:46 -0700 (PDT)
Received: from mail.advaoptical.com (mail.advaoptical.com [91.217.199.15]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 708CD1294A3 for <rtg-bfd@ietf.org>; Thu, 23 Mar 2017 12:45:46 -0700 (PDT)
Received: from MUC-S-EX16B.advaoptical.com ([172.20.1.15]) by muc-vsrv-fsmail.advaoptical.com (8.16.0.17/8.16.0.17) with ESMTPS id v2NJjecW011102 (version=TLSv1.2 cipher=ECDHE-RSA-AES256-SHA384 bits=256 verify=FAIL); Thu, 23 Mar 2017 20:45:40 +0100
Received: from MUC-S-EX16A.advaoptical.com (172.20.1.18) by MUC-S-EX16B.advaoptical.com (172.20.1.15) with Microsoft SMTP Server (version=TLS1_2, cipher=TLS_ECDHE_RSA_WITH_AES_256_CBC_SHA384_P256) id 15.1.845.32; Thu, 23 Mar 2017 20:45:40 +0100
Received: from MUC-S-EX16A.advaoptical.com ([fe80::3124:862:90cb:59f4]) by MUC-S-EX16A.advaoptical.com ([fe80::3124:862:90cb:59f4%12]) with mapi id 15.01.0845.032; Thu, 23 Mar 2017 20:45:40 +0100
From: John Messenger <jmessenger@advaoptical.com>
To: Greg Mirsky <gregimirsky@gmail.com>, Jeffrey Haas <jhaas@pfrc.org>, Stephen Haddock <shaddock@stanfordalumni.org>, Norman Finn <norman.finn@MAIL01.HUAWEI.COM>, "Glenn Parsons (glenn.parsons@ericsson.com)" <glenn.parsons@ericsson.com>
CC: "rtg-bfd@ietf.org" <rtg-bfd@ietf.org>
Subject: RE: Adoption request for draft-tanmir-rtgwg-bfd-mc-lag
Thread-Topic: Adoption request for draft-tanmir-rtgwg-bfd-mc-lag
Thread-Index: AQHSpArwkWgz+0by/Uie6f8Qv0VyS6Gi01Iw
Date: Thu, 23 Mar 2017 19:45:40 +0000
Message-ID: <243e5d4a5b59466eaae06461cf54ef18@advaoptical.com>
References: <20170323153057.GK27015@pfrc.org> <CA+RyBmXthAjdVzfBAaD3OX8EXTHCm3e7_dF=j7XiymX-Ssh9sw@mail.gmail.com>
In-Reply-To: <CA+RyBmXthAjdVzfBAaD3OX8EXTHCm3e7_dF=j7XiymX-Ssh9sw@mail.gmail.com>
Accept-Language: en-GB, de-DE, en-US
Content-Language: en-US
X-MS-Has-Attach:
X-MS-TNEF-Correlator:
x-originating-ip: [172.20.1.232]
Content-Type: multipart/alternative; boundary="_000_243e5d4a5b59466eaae06461cf54ef18advaopticalcom_"
MIME-Version: 1.0
X-Proofpoint-Virus-Version: vendor=fsecure engine=2.50.10432:, , definitions=2017-03-23_19:, , signatures=0
Archived-At: <https://mailarchive.ietf.org/arch/msg/rtg-bfd/7Jw0l_qShkHVuX7qy8x-Q6jqkLs>
X-BeenThere: rtg-bfd@ietf.org
X-Mailman-Version: 2.1.22
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: <https://mailarchive.ietf.org/arch/browse/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: Thu, 23 Mar 2017 19:45:49 -0000

Adding some DRNI experts…

From: Greg Mirsky [mailto:gregimirsky@gmail.com]
Sent: 23 March 2017 15:23
To: Jeffrey Haas <jhaas@pfrc.org>; John Messenger <jmessenger@advaoptical.com>
Cc: rtg-bfd@ietf.org
Subject: Re: Adoption request for draft-tanmir-rtgwg-bfd-mc-lag

Hi Jeff, Reshad, John, et. al,
at our discussion in     Berlin<https://www.ietf.org/proceedings/96/minutes/minutes-96-bfd> John pointed to recent extension of IEEE 802.1AX, Distributed Resilient Network Interface (DRNI). I've reviewed, to the best of my understanding, Section 9 in IEEE 802.1AX-2014 (I can send copy if anyone is interested) and I agree with John that MC-LAG can be viewed as special case of DRNI. But I'm not sure that trying to address monitoring of DRNI with BFD would be appropriate. I think that using CFM/G.8013, a.k.a. Y.1731 mechanisms to monitor Layer 2 entity, which DRNI is, seems more appropriate. If there are cases of DRNI, other then MC-LAG, that are of interest to IETF community, I'd certainly would like to discuss these and see how we can apply BFD to monitor them as unified entity as well as its individual interfaces, similar to RFC 7130.

Regards,
Greg


On Thu, Mar 23, 2017 at 10:30 AM, Jeffrey Haas <jhaas@pfrc.org<mailto:jhaas@pfrc.org>> wrote:
We had presentations on draft-tanmir-rtgwg-bfd-mc-lag-(mpls|ip) during IETF 96.
This work covers multi-chassis forms of BFD-on-LAG, similar to RFC 7130.

After that presentation, the sense of the room was that this work was
something the WG would like to adopt.

This e-mail begins a formal adoption poll for one or both of these drafts.
This poll ends on April 16.  The timing of this poll is to give WG members a
chance to read the draft for comment during the WG session in Chicago on
Monday and also to set the date for two weeks after IETF 98 ends.

Please respond to this mail to indicate your support or lack of support for
this adoption.  Unless otherwise noted, support will be interpreted as
support for *both* documents.

The chairs wish to remind the Working Group that these documents have IPR
asserted against the mechanisms contained in these drafts.

-- Jeff and Reshad

v2.23.0 | Report a Bug | By Email