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

"Carlos Pignataro (cpignata)" <> Sun, 09 July 2017 21:30 UTC

Return-Path: <>
Received: from localhost (localhost []) by (Postfix) with ESMTP id 0A20A126C7A for <>; Sun, 9 Jul 2017 14:30:35 -0700 (PDT)
X-Virus-Scanned: amavisd-new at
X-Spam-Flag: NO
X-Spam-Score: -14.521
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: (amavisd-new); dkim=pass (1024-bit key)
Received: from ([]) by localhost ( []) (amavisd-new, port 10024) with ESMTP id P5A1sw0SgFPs for <>; Sun, 9 Jul 2017 14:30:32 -0700 (PDT)
Received: from ( []) (using TLSv1.2 with cipher DHE-RSA-SEED-SHA (128/128 bits)) (No client certificate requested) by (Postfix) with ESMTPS id 1B6BA1242F5 for <>; Sun, 9 Jul 2017 14:30:32 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple;;; l=25092; q=dns/txt; s=iport; t=1499635831; x=1500845431; h=from:to:cc:subject:date:message-id:references: in-reply-to:mime-version; bh=gNiH+UI5jhvmF6KVwS6Fjk3YrO2msYysG5HnwQfaRSQ=; b=K3myAACVKferB2slWOYhvZtgXDsQ4GTXiog2AH1Jq8rdztdB8+olsE9W 7PcDvXYfFaLur/tpLpBXk7LCAOd1BNQRJl3nTCVPL4lWIJpzWZY+mNrs+ lKKCa11W2bnsrlpIVq9xxMcseAAUmv8kgZVc16FQUijnIqQjfpwRX0VZg U=;
X-IronPort-Anti-Spam-Filtered: true
X-IronPort-Anti-Spam-Result: =?us-ascii?q?A0DJAACWn2JZ/4kNJK1cGgEBAQECAQEBA?= =?us-ascii?q?QgBAQEBgm8+LWSBFI4JlEuFTY1VghEshXACg0k/GAECAQEBAQEBAWsohRkGTC0?= =?us-ascii?q?QAgEIEyUHByEEDRQRAgQOBYlLTAMQBRCseoQOgx4NhAABAQEBAQEBAQEBAQEBA?= =?us-ascii?q?QEBAQEBAQEdgyiDTIFhK4J5gTyBG4IPg0eCEh8FnmM7AodGg0WED4RuggyFS4p?= =?us-ascii?q?Li3kxCYkMAQ8QOIEKdRVJEgGER0WBdgF2AYh6AQEB?=
X-IronPort-AV: E=Sophos;i="5.40,336,1496102400"; d="scan'208,217";a="270801914"
Received: from ([]) by with ESMTP/TLS/DHE-RSA-AES256-SHA; 09 Jul 2017 21:30:30 +0000
Received: from ( []) by (8.14.5/8.14.5) with ESMTP id v69LUUgN015244 (version=TLSv1/SSLv3 cipher=AES256-SHA bits=256 verify=FAIL); Sun, 9 Jul 2017 21:30:30 GMT
Received: from ( by ( with Microsoft SMTP Server (TLS) id 15.0.1210.3; Sun, 9 Jul 2017 17:30:29 -0400
Received: from ([]) by ([]) with mapi id 15.00.1210.000; Sun, 9 Jul 2017 17:30:29 -0400
From: "Carlos Pignataro (cpignata)" <>
To: Greg Mirsky <>
CC: Santosh P K <>, "" <>
Subject: Re: WGLC for BFD Multipoint documents (ending July 14, 2017)
Thread-Topic: WGLC for BFD Multipoint documents (ending July 14, 2017)
Date: Sun, 9 Jul 2017 21:30:29 +0000
Message-ID: <>
References: <> <> <> <>, <>
In-Reply-To: <>
Accept-Language: en-US
Content-Language: en-US
x-ms-exchange-transport-fromentityheader: Hosted
Content-Type: multipart/alternative; boundary="_000_A141706561ED4B319A96C6D0D0F16508ciscocom_"
MIME-Version: 1.0
Archived-At: <>
X-Mailman-Version: 2.1.22
Precedence: list
List-Id: "RTG Area: Bidirectional Forwarding Detection DT" <>
List-Unsubscribe: <>, <>
List-Archive: <>
List-Post: <>
List-Help: <>
List-Subscribe: <>, <>
X-List-Received-Date: Sun, 09 Jul 2017 21:30:35 -0000


How would that help interoperability? Seems like it would not matter, hence not mention is appropriate...

Sent from my iPad

On Jul 7, 2017, at 9:17 PM, Greg Mirsky <<>> wrote:

Hi Santosh, et. al,
another note, question on IP/UDP encapsulation of BFD for multipoint networks. The document says nothing about values that may be used for Source UDP port number. Even though MultipointHead will not receive BFD packets from MultipointTail on the UDP port listed, should we recommend to use numbers from dynamic range, i.e. 49152 to 65535? I think that the multipoint document should state, as in RFC 5881:

The source port MUST be in the range 49152 through 65535.

What do you think?


On Thu, Jul 6, 2017 at 11:00 AM, Greg Mirsky <<>> wrote:
Hi Santosh,
many thanks for your thoughtful consideration of my comments. Please find my answers and couple more notes in-line and tagged GIM>>.


On Thu, Jul 6, 2017 at 10:27 AM, Santosh P K <<>> wrote:
Hello Greg,
   Thanks for your comments. Please see my reply inline tagged[ SPK].

Santosh P K

On Tue, Jul 4, 2017 at 1:02 AM, Greg Mirsky <<>> wrote:
Dear Authors, WG chairs, et. al,
please kindly consider my comments to the latest version of the draft as part of WGLC:

  *   Very general
     *   I suggest to add note clarifying that all terms that include "connectivity" in the document are being used as alternative to "continuity", i.e. existence of a path between the sender and the receiver, and should not be interpreted as "connectivity verification in terms of transport network".
  *   Introduction
     *   I find that characterization of BFD and unidirectional continuity verification as "natural fit" bit of stretching. Perhaps "capable of supporting this use case" is acceptable;

[SPK] Will take care.
GIM>> Thanks

  *   Goals
     *   the last statement of non-goal seems little unclear. In fact, if there's only one tail, the BFD for multipoint network does verify connectivity, though unidirectional, between the head and the tail. I think that the intention is to stress that p2p bi-directional connectivity verification is not supported by this document.

[SPK] It only says that this document does not support verification of unicast path between head and tail. I can clarify a bit on this. Please let me know if you have a suggestion for this.
GIM>> I'd suggest to use unicast in place of point-to-point. Using my earlier example, in case when there's only one tail multipoint becomes point-to-point.

  *   Section 4.7
     *   the last paragraph notes that the discriminator value MUST NOT be changed. Since Your Discriminator MUST be set to 0 this refers to My Discriminator only. I think that explicit reference will make the statement more clear. Thus suggest s/the discriminator values/the My Discriminator value/

[SPK] Will take care of this.
GIM>> Thanks.

  *   Section 4.8
     *   I believe that requiring use of IP/UDP encapsulation for BFD in multipoint networks over MPSL LSP is too restrictive. I suggest changing text as following:


For multipoint LSP, MultipointTail MUST use destination UDP port "3784" and IP "<>" range.


If IP/UDP encapsulation used by MultipointHead for multipoint LSP, MultipointTail MUST use IP/UDP encapsulation of BFD destination UDP port "3784" and IP "<>" range.

Use of other types of encapsulation for multipoint LSP is outside the scope of this document.

[SPK] Thanks. I think this make sense for non MPLS tunnels.
GIM>> Thanks. As I've looked at the text, I've realized that it misses IPv6 case. Please consider the following as my new proposed change (not sure but I think that quote marks are not required):
If IP/UDP encapsulation used by MultipointHead for multipoint LSP, MultipointTail MUST use IP/UDP encapsulation of BFD destination UDP port 3784, and the 127/8 range for IPv4, and the 0:0:0:0:0:FFFF:7F00/104 range for IPv6.
Use of other types of encapsulation for multipoint LSP is outside the scope of this document.

  *   Section 4.10
     *   I cannot say what bfd.DetectMult packet is. It has not been defined in RFC 5880, nor in this document. What is the scenario described in the second paragraph? Is it when MultipointHead reduces Desired Min TX  Interval thus making defect detection more aggressive?

[SPK] This section talks about how to handle Poll sequence. In case of Multipoint head we cant afford to send POLL and expect all tail to reply with F bit set. Keeping track and building state at headend will be costly.
GIM>> Perhaps I wasn't clear in my question.  It was to the opening of this sentence:

   The MultipointHead MUST send bfd.DetectMult packets with P bit set at
   the old transmit interval before using the higher value in order to
   avoid false detection timeouts at the tails.

I couldn't find reference to "bfd.DetectMult packet" in any document related to BFD.

  *   Section 7
     *   I think it should be plural in the first paragraph, i.e. s/MultipointTail session/MultipointTail sessions/
     *   I think that we can add another consideration to improve, strengthen security of BFD for multipoint network by suggesting that MultipointTail sessions created only for known combination of MultipointHead and My Discriminator. Such information MAY be learned from out-of-band and mechanisms are outside the scope of this document.



On Mon, Jun 19, 2017 at 12:39 PM, Jeffrey Haas <<>> wrote:
Working Group,

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