Re: [mpls] New Version Notification for draft-mirsky-mpls-bfd-bootstrap-clarify-00.txt

Greg Mirsky <gregimirsky@gmail.com> Fri, 20 October 2017 15:18 UTC

Return-Path: <gregimirsky@gmail.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 C219B134210; Fri, 20 Oct 2017 08:18:52 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.698
X-Spam-Level:
X-Spam-Status: No, score=-2.698 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, FREEMAIL_FROM=0.001, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_LOW=-0.7, SPF_PASS=-0.001, URIBL_BLOCKED=0.001] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (2048-bit key) header.d=gmail.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 0HNGwC1wFAqQ; Fri, 20 Oct 2017 08:18:49 -0700 (PDT)
Received: from mail-lf0-x236.google.com (mail-lf0-x236.google.com [IPv6:2a00:1450:4010:c07::236]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id C2FAD126D0C; Fri, 20 Oct 2017 08:18:48 -0700 (PDT)
Received: by mail-lf0-x236.google.com with SMTP id 75so13580597lfx.1; Fri, 20 Oct 2017 08:18:48 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20161025; h=mime-version:in-reply-to:references:from:date:message-id:subject:to :cc; bh=h4ujeyTGXHQ/3IyUXW9ya0+8U8WA4EUm8PPjhmj4CDQ=; b=Ni4hHzvr7WpBQ6+euBvOQnuds5poH36heR3E8DQH+YxWx2iJyjp67l/d+y9DbZbIB4 hHtum7PlCD/VKpDOwtmiulEjEfN5Ws4GejFSSl/nqWCJwUfoYSheMVUIBHfi2bma/2pr NpykPxhaVKwDUAqF/8dl08qBF1JpfU5BGzX6NPp8Rbdpgd8Ms0H+8Lsu9iIaRUY12geS hA+k7G6x4TQOqjx5YS+g/i2aui2dJ6Y/GMWuTiaegGskYWylPvOp7iIIuE+tV4TFxISu lW/gSRO1U56lZz0kq9ywLbjKlOt1GJJA75JuvvqyaV6DzqqlLSHQUdjKRVGHlBQt+/sN nbbw==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:mime-version:in-reply-to:references:from:date :message-id:subject:to:cc; bh=h4ujeyTGXHQ/3IyUXW9ya0+8U8WA4EUm8PPjhmj4CDQ=; b=mylJSG687id8sNUKKtnidQNwPGXZdIEmCYZZnG9okFrOsHENzrk0geyXjue3wWNFFm pXxG+D1jT6+zluWfqemDhonX9S7C+7keg2bGYkHOrk8jyFswoQv1cIcwB0Z3piT6nOoe CirJBZMH6rzKZ62TW8U0cf+0cQKTgF7PdsiGLvsta+XbbFBlhNOA+6M29vZB9exG6gMa jguCjxu0Kl2eiqfFKAR5pCxuP/+p5pvIvABnmaWZdA7J37o8ophxBgThUERJWORjDoWN 3NG/lvLJ/tSH9SpfTZlTfpS7mIejdQ7rEonbDWIdHZi+nFcwyqfvrS5LMaEWnHzHe3/n H+Bw==
X-Gm-Message-State: AMCzsaX4UeF7mAflYBXfuXmJFx+ItX0cn1gKBnXzoJWFM6jybaQDMs13 v+KoL9+bd6bT6aZ4wtXHg3+hpkFRnSY37xM6ahI=
X-Google-Smtp-Source: ABhQp+RWMjYdWVWKBD377ckxxfP793/lyFv/FCohXlBF7uv2vVJRdM1dRYos11LWnZCJgwmU+cdguyInbpkp47uJj3A=
X-Received: by 10.25.18.35 with SMTP id h35mr1947612lfi.73.1508512726819; Fri, 20 Oct 2017 08:18:46 -0700 (PDT)
MIME-Version: 1.0
Received: by 10.46.32.147 with HTTP; Fri, 20 Oct 2017 08:18:46 -0700 (PDT)
In-Reply-To: <D0AA7372-C4D2-416B-AAA3-3A0229E639AB@cisco.com>
References: <150833078446.12462.3050923622769989740.idtracker@ietfa.amsl.com> <CA+RyBmUnB6jaMMytXtiUZf98RnLG8f6LusmDdAXHYkb2y1AE5A@mail.gmail.com> <D0AA7372-C4D2-416B-AAA3-3A0229E639AB@cisco.com>
From: Greg Mirsky <gregimirsky@gmail.com>
Date: Fri, 20 Oct 2017 08:18:46 -0700
Message-ID: <CA+RyBmV85xh_Et5VQVkyVN_eOEjSKiAmmaTHjVSDreOOcFpaWA@mail.gmail.com>
Subject: Re: [mpls] New Version Notification for draft-mirsky-mpls-bfd-bootstrap-clarify-00.txt
To: "Carlos Pignataro (cpignata)" <cpignata@cisco.com>
Cc: "mpls@ietf.org" <mpls@ietf.org>, "rtg-bfd@ietf.org" <rtg-bfd@ietf.org>
Content-Type: multipart/alternative; boundary="001a113fbed238a96b055bfbfded"
Archived-At: <https://mailarchive.ietf.org/arch/msg/rtg-bfd/DE_b7478XsaoJp_pt3xCYadyBr8>
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: Fri, 20 Oct 2017 15:18:53 -0000

Hi Carlos,
thank you for taking interest in the proposal, much appreciated. Please
find my notes in-line and tagged GIM>>.

Regards,
Greg

On Fri, Oct 20, 2017 at 5:54 AM, Carlos Pignataro (cpignata) <
cpignata@cisco.com>; wrote:

> Greg,
>
> This document seems to say “use “Do not Reply” reply mode, and even if you
> reply do not use the BFD Disc TLV, because it is not used.
>
GIM>> To be precise it says "SHOULD use "Do not Reply" thus preserving
compliance of implementations that do otherwise.

>
> Wouldn’t it be simpler to say “follow RFC 8029, and the ingress does not
> care about the BFD Disc TLV in the reply”? This would not suddenly make
> uncompliant existing implementations, potentially.
>
GIM>> I agree that normative language on handling echo reply is bit
restrictive. My goal is to have good discussion and see what others think.

>
> Also I wonder if this should be bfd-mpls instead of mpls-bfd, given where
> RFC 5884 was advanced.
>
GIM>> Probably it should be the way you've suggested. Hope it is not a big
problem for individual draft.

>
> Thanks,
>
> —
> Carlos Pignataro, carlos@cisco.com
>
> *“Sometimes I use big words that I do not fully understand, to make myself
> sound more photosynthesis."*
>
> On Oct 18, 2017, at 8:50 AM, Greg Mirsky <gregimirsky@gmail.com>; wrote:
>
> Dear All,
> this new document proposes clarification of two questions brought up in
> course of recent discussion of RFC 5884:
>
>    - use of Return mode values in bootstrapping BFD session echo request;
>    - inclusion of BFD Discriminator TLV in echo response to the
>    bootstrapping echo request.
>
> Your comments, questions are always welcome and greatly appreciated.
>
> Regards,
> Greg
>
> ---------- Forwarded message ----------
> From: <internet-drafts@ietf.org>;
> Date: Wed, Oct 18, 2017 at 5:46 AM
> Subject: New Version Notification for draft-mirsky-mpls-bfd-
> bootstrap-clarify-00.txt
> To: Gregory Mirsky <gregimirsky@gmail.com>;, Yanhua Zhao <
> zhao.yanhua3@zte.com.cn>;
>
>
>
> A new version of I-D, draft-mirsky-mpls-bfd-bootstrap-clarify-00.txt
> has been successfully submitted by Greg Mirsky and posted to the
> IETF repository.
>
> Name:           draft-mirsky-mpls-bfd-bootstrap-clarify
> Revision:       00
> Title:          Clarifying Use of LSP Ping to Bootstrap BFD over MPLS LSP
> Document date:  2017-10-18
> Group:          Individual Submission
> Pages:          4
> URL:            https://www.ietf.org/internet-
> drafts/draft-mirsky-mpls-bfd-bootstrap-clarify-00.txt
> Status:         https://datatracker.ietf.org/
> doc/draft-mirsky-mpls-bfd-bootstrap-clarify/
> Htmlized:       https://tools.ietf.org/html/d
> raft-mirsky-mpls-bfd-bootstrap-clarify-00
> Htmlized:       https://datatracker.ietf.org/
> doc/html/draft-mirsky-mpls-bfd-bootstrap-clarify-00
>
>
> Abstract:
>    This document, if approved, updates RFC 5884 by clarifying procedures
>    for using MPLS LSP ping to bootstrap Bidirectional Forwarding
>    Detection (BFD) over MPLS Label Switch Path.
>
>
>
>
> Please note that it may take a couple of minutes from the time of
> submission
> until the htmlized version and diff are available at tools.ietf.org.
>
> The IETF Secretariat
>
>
> _______________________________________________
> mpls mailing list
> mpls@ietf.org
> https://www.ietf.org/mailman/listinfo/mpls
>
>
>