IETF Logo Mail Archive

RE: I-D Action: draft-ietf-bfd-on-lags-00.txt

Gregory Mirsky <gregory.mirsky@ericsson.com> Mon, 20 May 2013 21:29 UTC

Return-Path: <gregory.mirsky@ericsson.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 8825921F9647 for <rtg-bfd@ietfa.amsl.com>; Mon, 20 May 2013 14:29:14 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.598
X-Spam-Level:
X-Spam-Status: No, score=-2.598 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, HTML_MESSAGE=0.001]
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 MsfAdhrOtA3Z for <rtg-bfd@ietfa.amsl.com>; Mon, 20 May 2013 14:29:07 -0700 (PDT)
Received: from usevmg21.ericsson.net (usevmg21.ericsson.net [198.24.6.65]) by ietfa.amsl.com (Postfix) with ESMTP id 6929E21F95F3 for <rtg-bfd@ietf.org>; Mon, 20 May 2013 14:29:07 -0700 (PDT)
X-AuditID: c6180641-b7f7b6d000001a44-f5-519a95a24b84
Received: from EUSAAHC006.ericsson.se (Unknown_Domain [147.117.188.90]) by usevmg21.ericsson.net (Symantec Mail Security) with SMTP id 3C.80.06724.2A59A915; Mon, 20 May 2013 23:29:06 +0200 (CEST)
Received: from EUSAAMB103.ericsson.se ([147.117.188.120]) by EUSAAHC006.ericsson.se ([147.117.188.90]) with mapi id 14.02.0328.009; Mon, 20 May 2013 17:29:05 -0400
From: Gregory Mirsky <gregory.mirsky@ericsson.com>
To: "rtg-bfd@ietf.org" <rtg-bfd@ietf.org>
Subject: RE: I-D Action: draft-ietf-bfd-on-lags-00.txt
Thread-Topic: I-D Action: draft-ietf-bfd-on-lags-00.txt
Thread-Index: AQHOTcu+41wx13zJGki3ilKRtslFy5kOnrBw
Date: Mon, 20 May 2013 21:29:04 +0000
Message-ID: <7347100B5761DC41A166AC17F22DF1121B49CFFD@eusaamb103.ericsson.se>
References: <20130510221344.9328.58926.idtracker@ietfa.amsl.com>
In-Reply-To: <20130510221344.9328.58926.idtracker@ietfa.amsl.com>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach:
X-MS-TNEF-Correlator:
x-originating-ip: [147.117.188.134]
Content-Type: multipart/alternative; boundary="_000_7347100B5761DC41A166AC17F22DF1121B49CFFDeusaamb103erics_"
MIME-Version: 1.0
X-Brightmail-Tracker: H4sIAAAAAAAAA+NgFjrLLMWRmVeSWpSXmKPExsUyuXRPlO6iqbMCDVoPmlh8/rON0YHRY8mS n0wBjFFcNimpOZllqUX6dglcGbP/7mQvOGhXcfjFddYGxkWmXYwcHBICJhLXv9p1MXICmWIS F+6tZ+ti5OIQEjjKKHFv9gtGCGc5o8T+Q53sIFVsAkYSLzb2gNkiApoSa+dsZwWxhQXMJCY+ 2sIMETeX2LH8GxOEbSTxbdl2FhCbRUBVYtP3dWD1vAK+ElefrQSrERJwkPi0/gSYzSngKDHx 3hawGkagi76fWgMWZxYQl7j1ZD4TxKUCEkv2nGeGsEUlXj7+xwphK0ssebKfBeQxZoF8iTWv EyFWCUqcnPmEZQKjyCwkk2YhVM1CUgVRoiOxYPcnNghbW2LZwtfMMPaZA4+ZkMUXMLKvYuQo LU4ty003MtzECIySYxJsjjsYF3yyPMQozcGiJM7brT01UEggPbEkNTs1tSC1KL6oNCe1+BAj EwenVAOj15bDOqYPVAV4dBxu1t2T0WOeaC26OWbdC00GmRZP7WrWW5r69U/vFjv58aZerdZa 1rrs8Re16kucp5fJf3uwy1ksW7Mu9ehrxWyRNeo8UWkua55xhLqzZq+9eVBy1oxov5z5pS83 O0/IYbF/KGhnfUXlqttJtd6G9gv2xx8Vbed8Hmr9+pASS3FGoqEWc1FxIgAhQyB0YAIAAA==
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, 20 May 2013 21:29:14 -0000

Dear Authors, et al.,
I agree with everything in the latest version of the document but inclusion of Section 3. I think that what is discussed in the section and use of normative language are outside of the scope of BFD WG charter:
Provide one or more mechanisms to run BFD over Link Aggregation Group Interfaces.

Content of the section seems more suitable as Informational or BCP with appropriate changes in use and interpretation of RFC 2119 language.

        Regards,
                Greg

-----Original Message-----
From: rtg-bfd-bounces@ietf.org [mailto:rtg-bfd-bounces@ietf.org] On Behalf Of internet-drafts@ietf.org
Sent: Friday, May 10, 2013 3:14 PM
To: i-d-announce@ietf.org
Cc: rtg-bfd@ietf.org
Subject: I-D Action: draft-ietf-bfd-on-lags-00.txt


A New Internet-Draft is available from the on-line Internet-Drafts directories.
 This draft is a work item of the Bidirectional Forwarding Detection Working Group of the IETF.

        Title           : Bidirectional Forwarding Detection (BFD) on Link Aggregation Group (LAG) Interfaces
        Author(s)       : Manav Bhatia
                          Mach(Guoyi) Chen
                          Sami Boutros
                          Marc Binderberger
                          Jeffrey Haas
        Filename        : draft-ietf-bfd-on-lags-00.txt
        Pages           : 11
        Date            : 2013-05-10

Abstract:
   This document proposes a mechanism to run BFD on Link Aggregation
   Group (LAG) interfaces.  It does so by running an independent
   Asynchronous mode BFD session on every LAG member link.

   This mechanism allows the verification of member link continuity,
   either in combination with, or in absence of, LACP.  It provides a
   shorter detection time than what LACP offers.  The continuity check
   can also cover elements of layer 3 bidirectional forwarding.

   This mechanism utilizes a well-known UDP port distinct from that of
   single-hop BFD over IP.  This new UDP port removes the ambiguity of
   BFD over LAG packets from BFD over single-hop IP.



The IETF datatracker status page for this draft is:
https://datatracker.ietf.org/doc/draft-ietf-bfd-on-lags

There's also a htmlized version available at:
http://tools.ietf.org/html/draft-ietf-bfd-on-lags-00


Internet-Drafts are also available by anonymous FTP at:
ftp://ftp.ietf.org/internet-drafts/

v2.23.0 | Report a Bug | By Email