Re: [mpls] New Version Notification for draft-mirsky-mpls-bfd-bootstrap-clarify-00.txt
Greg Mirsky <gregimirsky@gmail.com> Thu, 22 March 2018 21:15 UTC
Return-Path: <gregimirsky@gmail.com>
X-Original-To: mpls@ietfa.amsl.com
Delivered-To: mpls@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id EFB4812025C; Thu, 22 Mar 2018 14:15:02 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.699
X-Spam-Level:
X-Spam-Status: No, score=-2.699 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] 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 c-uytsQKlxBh; Thu, 22 Mar 2018 14:14:54 -0700 (PDT)
Received: from mail-lf0-x233.google.com (mail-lf0-x233.google.com [IPv6:2a00:1450:4010:c07::233]) (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 7C95012426E; Thu, 22 Mar 2018 14:14:53 -0700 (PDT)
Received: by mail-lf0-x233.google.com with SMTP id x205-v6so15303532lfa.0; Thu, 22 Mar 2018 14:14:53 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20161025; h=mime-version:references:in-reply-to:from:date:message-id:subject:to :cc; bh=GXtpl/wRrP8RFRB7+X4JXiwKBJwQzWHKQ/m92h/jV4s=; b=CWpfKeoM430NrFF9C7as6ESvri3PKez6ZYgsqSEqDs39h1xGby72z/FpOjZFHgeHHd N6p23v57SQBW0D0HO3NN4Pux02NLTNGE0VMKfCIhhuN/2/1JjggYfF+uH4Cx+bGP60qR pK2uAu6+l2FN1YKp6VDV2o6VNTxDXQ4NCYFJe259Fsck4uwelZRsO8jVVLjHNCt8rZdb OBs4FCRR7CaD6umJ0Gv7WHMX4TqykSkrCpX07nZ2VZapV0yAO0DVDYpKVs8GgH3faE1J x/X62GO2q+xodqcd5GHrwoa0ln2vQbfmV6FBfxs1/NisVgNDOLSti2s58rR5D8p4NyWH cD9A==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:mime-version:references:in-reply-to:from:date :message-id:subject:to:cc; bh=GXtpl/wRrP8RFRB7+X4JXiwKBJwQzWHKQ/m92h/jV4s=; b=e22iTpubqAbCXwEyT7wa4AgEMFdudlyU/MNL0V/qfqwxMd7sBzWHWauO59ooc2mdcP dp6vup1bDu9AUotqorZfAeOmE4+nc9hBY8oyd1YaX3z85iKOJb991GpckMIPw97WRzwz nK7Pib2Co9X6+EFORoZMm/HsIOBPAN2NJXBAjhSNryAqrR8/swjbNXC8fPDgUFEtDZtC 4Oes8kv/uGcQBKjd8becZolEmPbLmlT50wRpmPFDKnF/gLSv2G4S4Q3SQQpTcVXcclK9 2ymdDzGwiC6E4KE7BIVRtDfdRNDmHVF20TpzNqPRg1JrAoYZqDajJ+jjwu0/CIyO1uya b5pg==
X-Gm-Message-State: AElRT7ERlwPxgkAeHcaluMH+MohT1IgN1skIUQU3W9IKiXX56PTWTWTu TAyytw97rypoys/QSlkL7UA/1QinQnAeP4jn4Ys9/Q==
X-Google-Smtp-Source: AG47ELuYXqrFjzWgUeSFF+hssIcBVtqBNYOJ0Xuz5kGhYIul89DFNXH0BFSOn6g6gp0Z/jUypUUEYaX9thqQJ+BB+mM=
X-Received: by 10.46.129.153 with SMTP id e25mr14406533ljg.69.1521753291635; Thu, 22 Mar 2018 14:14:51 -0700 (PDT)
MIME-Version: 1.0
References: <150833078446.12462.3050923622769989740.idtracker@ietfa.amsl.com> <CA+RyBmUnB6jaMMytXtiUZf98RnLG8f6LusmDdAXHYkb2y1AE5A@mail.gmail.com> <D0AA7372-C4D2-416B-AAA3-3A0229E639AB@cisco.com> <CA+RyBmV85xh_Et5VQVkyVN_eOEjSKiAmmaTHjVSDreOOcFpaWA@mail.gmail.com> <5F91613C-194E-4C0C-ABC0-2C27E9AFAB4B@cisco.com> <15EBD5DA-382A-448C-945D-8C3B1ACFAA88@cisco.com> <CA+RyBmWz-oKXJuPTxDLyfRUXjAQ6OvT68MPaMRKXDMobbGDFGw@mail.gmail.com> <06E104E8-DC84-4BD8-87D9-DFE96938E70E@cisco.com>
In-Reply-To: <06E104E8-DC84-4BD8-87D9-DFE96938E70E@cisco.com>
From: Greg Mirsky <gregimirsky@gmail.com>
Date: Thu, 22 Mar 2018 21:14:40 +0000
Message-ID: <CA+RyBmUBCFo=hJWa=ozORP01U0jDo9ogBQZMR5qY8964CHNzbg@mail.gmail.com>
To: "Carlos Pignataro (cpignata)" <cpignata@cisco.com>
Cc: "Reshad Rahman (rrahman)" <rrahman@cisco.com>, mpls@ietf.org, "rtg-bfd@ietf.org" <rtg-bfd@ietf.org>
Content-Type: multipart/alternative; boundary="f4f5e80c7dec623f63056806ccf4"
Archived-At: <https://mailarchive.ietf.org/arch/msg/mpls/1zw09MPFtP57mAdXN8MOGHiJ6RU>
Subject: Re: [mpls] New Version Notification for draft-mirsky-mpls-bfd-bootstrap-clarify-00.txt
X-BeenThere: mpls@ietf.org
X-Mailman-Version: 2.1.22
Precedence: list
List-Id: Multi-Protocol Label Switching WG <mpls.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/mpls>, <mailto:mpls-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/mpls/>
List-Post: <mailto:mpls@ietf.org>
List-Help: <mailto:mpls-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/mpls>, <mailto:mpls-request@ietf.org?subject=subscribe>
X-List-Received-Date: Thu, 22 Mar 2018 21:15:03 -0000
Hi Carlos, if the group agrees that I'm overparanoid I'll accept that and forever hold my peace. Regards, Greg On Thu, Mar 22, 2018, 7:00 PM Carlos Pignataro (cpignata) < cpignata@cisco.com> wrote: > Hi, Greg, > > > > That, to me, reads like over-specifying. Are you aware of any > implementation attempting to do that? > > > > There’s no text for that comparison – why would an implementation do that? > > > > Thanks, > > > > Carlos. > > > > *From: *Greg Mirsky <gregimirsky@gmail.com> > *Date: *Thursday, March 22, 2018 at 12:18 PM > *To: *"Reshad Rahman (rrahman)" <rrahman@cisco.com> > *Cc: *Carlos Pignataro <cpignata@cisco.com>, "mpls@ietf.org" < > mpls@ietf.org>, "rtg-bfd@ietf.org" <rtg-bfd@ietf.org> > *Subject: *Re: [mpls] New Version Notification for > draft-mirsky-mpls-bfd-bootstrap-clarify-00.txt > > > > Hi Reshad, > > your analysis of the text is absolutely correct. My concern is the > possible analysis of the Discriminator by ingress LER and it comparing to > My Discriminator of the received BFD control packets. According to the RFC > 5884 both must match but because LSP Echo reply does not provide sufficient > information the most likely outcome will be - no matching BFD session found > and thus the text fails. (Yes, it would be rather naive implementation but > ...). Thus I propose to add explicit statement for ingress LER not to use > information if received Discriminator TLV in Echo reply. > > > > Regards, > > Greg > > > > On Thu, Mar 22, 2018 at 3:39 PM, Reshad Rahman (rrahman) < > rrahman@cisco.com> wrote: > > Hi, > > > > In the BFD meeting yesterday there was discussion about lack of clarity on > what the spec says wrt to the discriminator TLV being sent by the egress > node in the echo reply and that this causes interop issues. From RFC 5884: > > > > The egress LSR MAY respond with an LSP Ping Echo > > reply message that carries the local discriminator assigned by it for > > the BFD session. > > > > In the errata: > > The LSP Ping > > Echo reply message generated by the egress LSR MAY carry the local > > discriminator assigned by it for the BFD session, as specified in > > section 6.1. > > So I think it’s clear that this cannot be the discriminator of the ingress > node. I agree that this information is useless but still don’t see how it > can cause any harm, and any implementation which interprets the > discriminator in the echo reply differently is buggy IMHO. > > > > Regards, > > Reshad (hat off). > > > > *From: *Rtg-bfd <rtg-bfd-bounces@ietf.org> on behalf of "Reshad Rahman > (rrahman)" <rrahman@cisco.com> > *Date: *Tuesday, March 20, 2018 at 5:49 PM > *To: *Greg Mirsky <gregimirsky@gmail.com>, "Carlos Pignataro (cpignata)" < > cpignata@cisco.com> > > > *Cc: *"mpls@ietf.org" <mpls@ietf.org>, "rtg-bfd@ietf.org" < > rtg-bfd@ietf.org> > *Subject: *Re: [mpls] New Version Notification for > draft-mirsky-mpls-bfd-bootstrap-clarify-00.txt > > > > Hi, > > > > While I agree that the echo reply is not needed to bootstrap BFD, and that > the BFD Disc TLV is not needed in the reply, doing this doesn’t break > anything. So I don’t see the proposed changes as being necessary. > > > > Does anyone remember why RFC5884 has the echo reply, was it to > potentially save an echo request from egress for bidirectional case? > > > > Also, if we do go ahead with the proposed changes in this draft, we’ll > have to fix this errata <https://www.rfc-editor.org/errata/eid5085>. > > > > Regards, > > Reshad (speaking as individual contributor). > > > > *From: *Rtg-bfd <rtg-bfd-bounces@ietf.org> on behalf of Greg Mirsky < > gregimirsky@gmail.com> > *Date: *Friday, October 20, 2017 at 4:19 PM > *To: *"Carlos Pignataro (cpignata)" <cpignata@cisco.com> > *Cc: *"mpls@ietf.org" <mpls@ietf.org>, "rtg-bfd@ietf.org" < > rtg-bfd@ietf.org> > *Subject: *Re: [mpls] New Version Notification for > draft-mirsky-mpls-bfd-bootstrap-clarify-00.txt > > > > 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/draft-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 > > > > > > >
- [mpls] Fwd: New Version Notification for draft-mi… Greg Mirsky
- Re: [mpls] New Version Notification for draft-mir… Carlos Pignataro (cpignata)
- Re: [mpls] New Version Notification for draft-mir… Greg Mirsky
- Re: [mpls] New Version Notification for draft-mir… Reshad Rahman (rrahman)
- Re: [mpls] New Version Notification for draft-mir… Reshad Rahman (rrahman)
- Re: [mpls] New Version Notification for draft-mir… Greg Mirsky
- Re: [mpls] New Version Notification for draft-mir… Carlos Pignataro (cpignata)
- Re: [mpls] New Version Notification for draft-mir… Greg Mirsky