Re: WGLC for BFD Multipoint documents (ending July 14, 2017)

"Carlos Pignataro (cpignata)" <cpignata@cisco.com> Tue, 27 June 2017 14:56 UTC

Return-Path: <cpignata@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 3B92E129B41 for <rtg-bfd@ietfa.amsl.com>; Tue, 27 Jun 2017 07:56:27 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -14.521
X-Spam-Level:
X-Spam-Status: No, score=-14.521 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, RCVD_IN_MSPIKE_H3=-0.01, RCVD_IN_MSPIKE_WL=-0.01, RP_MATCHES_RCVD=-0.001, SPF_HELO_PASS=-0.001, SPF_PASS=-0.001, URIBL_BLOCKED=0.001, USER_IN_DEF_DKIM_WL=-7.5] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (1024-bit key) header.d=cisco.com
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 R2ZFaczZieEy for <rtg-bfd@ietfa.amsl.com>; Tue, 27 Jun 2017 07:56:24 -0700 (PDT)
Received: from alln-iport-5.cisco.com (alln-iport-5.cisco.com [173.37.142.92]) (using TLSv1.2 with cipher DHE-RSA-SEED-SHA (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id A9DD8129B1A for <rtg-bfd@ietf.org>; Tue, 27 Jun 2017 07:56:24 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=cisco.com; i=@cisco.com; l=11864; q=dns/txt; s=iport; t=1498575384; x=1499784984; h=from:to:cc:subject:date:message-id:references: in-reply-to:mime-version; bh=WHkmVs3EzvUcwZ6sdvDA7FblZ3MuRvjar7U9cGxQ49g=; b=Smp8pV9xjNNX3cHS4Yet+d3Qf0MJbYnu+Fhv/Xj/jzhec7MlJWTf1mp7 PgZtYuqKLLpGthOolxxrKqzW4PO79fbR+1GgN1mIXzemKCcqkuDzMi4Cc Y9iShAbKPpg/gf0KNhm9ry6yfVSTiFdb8zLIftL0QNyJmx7q/1ty9yNwT k=;
X-IronPort-Anti-Spam-Filtered: true
X-IronPort-Anti-Spam-Result: =?us-ascii?q?A0BbAQBocVJZ/5hdJa1cGQEBAQEBAQEBA?= =?us-ascii?q?QEBBwEBAQEBgystY4EOB4NlihmRQ5B0hSuCES6FewIagmI/GAECAQEBAQEBAWs?= =?us-ascii?q?ohRkGI1YQAgEIDjEDAgICMBQRAgQOBYlMZBCwOoImi1gBAQEBAQEBAQEBAQEBA?= =?us-ascii?q?QEBAQEBAQEYBYMng0yBYAErC4JugTyGQTCCEh8FlyGHTgKHNIw1khSVIwEfOIE?= =?us-ascii?q?KdBVJEgGFCoF2dgEBiA2BDQEBAQ?=
X-IronPort-AV: E=Sophos;i="5.39,401,1493683200"; d="scan'208,217";a="444742279"
Received: from rcdn-core-1.cisco.com ([173.37.93.152]) by alln-iport-5.cisco.com with ESMTP/TLS/DHE-RSA-AES256-GCM-SHA384; 27 Jun 2017 14:56:23 +0000
Received: from XCH-RTP-017.cisco.com (xch-rtp-017.cisco.com [64.101.220.157]) by rcdn-core-1.cisco.com (8.14.5/8.14.5) with ESMTP id v5REuNYx030334 (version=TLSv1/SSLv3 cipher=AES256-SHA bits=256 verify=FAIL); Tue, 27 Jun 2017 14:56:23 GMT
Received: from xch-rtp-020.cisco.com (64.101.220.160) by XCH-RTP-017.cisco.com (64.101.220.157) with Microsoft SMTP Server (TLS) id 15.0.1210.3; Tue, 27 Jun 2017 10:56:22 -0400
Received: from xch-rtp-020.cisco.com ([64.101.220.160]) by XCH-RTP-020.cisco.com ([64.101.220.160]) with mapi id 15.00.1210.000; Tue, 27 Jun 2017 10:56:22 -0400
From: "Carlos Pignataro (cpignata)" <cpignata@cisco.com>
To: Jeff Haas <jhaas@pfrc.org>
CC: "rtg-bfd@ietf.org" <rtg-bfd@ietf.org>
Subject: Re: WGLC for BFD Multipoint documents (ending July 14, 2017)
Thread-Topic: WGLC for BFD Multipoint documents (ending July 14, 2017)
Thread-Index: AQHS6TKRH3+h+CPmGE2vggvMdQNmVaI5G70A
Date: Tue, 27 Jun 2017 14:56:22 +0000
Message-ID: <0B1CE01B-4FA3-4536-AF41-5DDC6F510C0D@cisco.com>
References: <20170619193929.GE22146@pfrc.org>
In-Reply-To: <20170619193929.GE22146@pfrc.org>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach:
X-MS-TNEF-Correlator:
x-ms-exchange-messagesentrepresentingtype: 1
x-ms-exchange-transport-fromentityheader: Hosted
x-originating-ip: [10.118.116.131]
Content-Type: multipart/alternative; boundary="_000_0B1CE01B4FA34536AF415DDC6F510C0Dciscocom_"
MIME-Version: 1.0
Archived-At: <https://mailarchive.ietf.org/arch/msg/rtg-bfd/UuDJNywQils2fo4kcX4LP5bWsxk>
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: Tue, 27 Jun 2017 14:56:27 -0000

Just one comment on these two documents, in regards to the state variables:

https://tools.ietf.org/html/draft-ietf-bfd-multipoint-10#section-4.4.1

4.4.1.  New State Variables

   A number of state variables are added to the base specification in
   support of Multipoint BFD.

      bfd.SessionType

         The type of this session.  Allowable values are:

CMP: However, this state (bfd.SessionType) variable is already defined in SBFD RFC 7880:

https://tools.ietf.org/html/rfc7880#section-6.1

6.1.  New State Variables

   A new state variable is added to the base specification in support
   of S-BFD.

   o  bfd.SessionType: This is a new state variable that describes
      the type of a particular session.


CMP: So, for draft-ietf-bfd-multipoint, I suggest a pointer to RFC 7880 where bfd.SessionType is defined in the addition of new values to the existing variable.

CMP: Similarly:

https://tools.ietf.org/html/draft-ietf-bfd-multipoint-active-tail-04#section-3.3.1

      bfd.SessionType

         The type of this session as defined in
         [I-D.ietf-bfd-multipoint].  A new value introduced is:

CMP: The pointer above should be to RFC 7880 also, and:

      bfd.SilentTail

CMP: But this is defined in draft-ietf-bfd-multipoint

https://tools.ietf.org/html/draft-ietf-bfd-multipoint-10#section-4.4.1

      bfd.SilentTail

Thanks!

— Carlos.


On Jun 19, 2017, at 3:39 PM, Jeffrey Haas <jhaas@pfrc.org<mailto:jhaas@pfrc.org>> wrote:

Working Group,

https://tools.ietf.org/html/draft-ietf-bfd-multipoint-10
https://tools.ietf.org/html/draft-ietf-bfd-multipoint-active-tail-04


The BFD Multipoint documents have been stable for some time.  Prior
discussion at meetings has suggested we have an implementation for the main
protocol component.  Also per prior discussions, we split the active-tail
component of the original multipoint document to permit implementors to not
have to worry about implementing active-tail procedures if they weren't
interested in that feature.

We are starting an extended last call on these documents.  The WGLC will
conclude on July 14.  This provides ample time for list discussion.  If
necessary, the IETF-99 meeting may provide for opportunities to close any
contentious technical points.  (BFD is not currently scheduled to meet.)

One item I would like to kick off is the document status of the active-tail
mechanism.  At this time, no one has implemented it that I am aware of.
Discussion with our AD suggests that publishing the document with
Experimental status may be reasonable to preserve the work that went into
the proposal.

-- Jeff