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

Jeffrey Haas <jhaas@pfrc.org> Wed, 05 July 2017 16:17 UTC

Return-Path: <jhaas@slice.pfrc.org>
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 43886131D48 for <rtg-bfd@ietfa.amsl.com>; Wed, 5 Jul 2017 09:17:30 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.902
X-Spam-Level:
X-Spam-Status: No, score=-1.902 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RP_MATCHES_RCVD=-0.001, SPF_HELO_PASS=-0.001, SPF_PASS=-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 seT6hMa1M29W for <rtg-bfd@ietfa.amsl.com>; Wed, 5 Jul 2017 09:17:28 -0700 (PDT)
Received: from slice.pfrc.org (slice.pfrc.org [67.207.130.108]) by ietfa.amsl.com (Postfix) with ESMTP id 3442D131BBF for <rtg-bfd@ietf.org>; Wed, 5 Jul 2017 09:17:28 -0700 (PDT)
Received: by slice.pfrc.org (Postfix, from userid 1001) id 654C41E34A; Wed, 5 Jul 2017 12:26:43 -0400 (EDT)
Date: Wed, 5 Jul 2017 12:26:43 -0400
From: Jeffrey Haas <jhaas@pfrc.org>
To: Greg Mirsky <gregimirsky@gmail.com>
Cc: "rtg-bfd@ietf.org" <rtg-bfd@ietf.org>
Subject: Re: WGLC for BFD Multipoint documents (ending July 14, 2017)
Message-ID: <20170705162643.GS2289@pfrc.org>
References: <20170619193929.GE22146@pfrc.org> <CA+RyBmUfOe-1u7_MVwNt394B181XavLmTg4gA16v-4Mf1XWhGA@mail.gmail.com>
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
In-Reply-To: <CA+RyBmUfOe-1u7_MVwNt394B181XavLmTg4gA16v-4Mf1XWhGA@mail.gmail.com>
User-Agent: Mutt/1.5.21 (2010-09-15)
Archived-At: <https://mailarchive.ietf.org/arch/msg/rtg-bfd/bhpB1TgCmb59X0HrdK8qSIu37iU>
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: Wed, 05 Jul 2017 16:17:30 -0000

Greg,

Thanks for your detailed feedback.

A portion of your feedback seems to be mostly minor editorial changes.  A
few of these items are discussion points that probably need to be resolved
with some amount of WG discussion.

What's your opinion about the ability to advance these documents once these
issues have been addressed?

-- Jeff

On Mon, Jul 03, 2017 at 12:32:44PM -0700, 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;
>    - 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.
>    - 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/
>    - 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:
> 
> OLD:
> 
> For multipoint LSP, MultipointTail MUST use destination UDP port
> "3784" and IP "127.0.0.0/8" range.
> 
> 
> NEW
> 
> If IP/UDP encapsulation used by MultipointHead for multipoint LSP,
> MultipointTail MUST use IP/UDP encapsulation of BFD destination UDP
> port "3784" and IP "127.0.0.0/8" range.
> 
> 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?
>    - 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.
> 
> 
> Regards,
> 
> Greg
> 
> 
> 
> On Mon, Jun 19, 2017 at 12:39 PM, Jeffrey Haas <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
> >
> >