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

"Carlos Pignataro (cpignata)" <cpignata@cisco.com> Fri, 20 October 2017 12:54 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 676E1133011; Fri, 20 Oct 2017 05:54:27 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -14.519
X-Spam-Level:
X-Spam-Status: No, score=-14.519 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, 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 obAmkEbWgzp4; Fri, 20 Oct 2017 05:54:25 -0700 (PDT)
Received: from alln-iport-2.cisco.com (alln-iport-2.cisco.com [173.37.142.89]) (using TLSv1.2 with cipher DHE-RSA-SEED-SHA (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 9C7F5124B18; Fri, 20 Oct 2017 05:54:25 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=cisco.com; i=@cisco.com; l=12480; q=dns/txt; s=iport; t=1508504065; x=1509713665; h=from:to:cc:subject:date:message-id:references: in-reply-to:mime-version; bh=fVCFmTn4M0DdWysfVVM8HlReX7jXV3mSJ7Bzy7flAIE=; b=AwWjMm8GcPcuWyh+CbmrgEMhTlPSOB/zENjo3Tb5KL4mMMYPS8lRpN6M epXbYbnRFaIsUXH+KbOR91xkYGk16UUAgdqwz0AHAXBQE7lspXiAt3Jx6 Y5nXqIsr06GgYf8o1Cxx2Xfohw2v8ePiiL9C+L7M4N8OS+T0PdsYtj7G6 I=;
X-IronPort-Anti-Spam-Filtered: true
X-IronPort-Anti-Spam-Result: =?us-ascii?q?A0ChAAA78elZ/4YNJK1cGQEBAQEBAQEBA?= =?us-ascii?q?QEBBwEBAQEBg19kbicHg3OKH48/gXqISogshT8QggEKGAEMhRYCGoQfPxgBAgE?= =?us-ascii?q?BAQEBAQFrKIUdAQEBBAEBIUsJAhACAQgRAwECKAMCAgIfBgsUCQgCBA4FiTxMA?= =?us-ascii?q?xUQqXCCJ4c6DYNZAQEBAQEBAQEBAQEBAQEBAQEBAQEBHYMuggeBUIFpKYMBgl6?= =?us-ascii?q?Bb1gWCIJWL4IyBYochzKPUjwCh2GIFYR5ghVdhRuLD40IiEECERkBgTgBDxA4g?= =?us-ascii?q?Vt6FR8qLQGCNgmCGm6BTnYBiUaBEQEBAQ?=
X-IronPort-AV: E=Sophos; i="5.43,405,1503360000"; d="scan'208,217"; a="19696982"
Received: from alln-core-12.cisco.com ([173.36.13.134]) by alln-iport-2.cisco.com with ESMTP/TLS/DHE-RSA-AES256-SHA; 20 Oct 2017 12:54:24 +0000
Received: from XCH-RTP-016.cisco.com (xch-rtp-016.cisco.com [64.101.220.156]) by alln-core-12.cisco.com (8.14.5/8.14.5) with ESMTP id v9KCsOI8027424 (version=TLSv1/SSLv3 cipher=AES256-SHA bits=256 verify=FAIL); Fri, 20 Oct 2017 12:54:24 GMT
Received: from xch-rtp-020.cisco.com (64.101.220.160) by XCH-RTP-016.cisco.com (64.101.220.156) with Microsoft SMTP Server (TLS) id 15.0.1320.4; Fri, 20 Oct 2017 08:54:23 -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.1320.000; Fri, 20 Oct 2017 08:54:23 -0400
From: "Carlos Pignataro (cpignata)" <cpignata@cisco.com>
To: Greg Mirsky <gregimirsky@gmail.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
Thread-Topic: [mpls] New Version Notification for draft-mirsky-mpls-bfd-bootstrap-clarify-00.txt
Thread-Index: AQHTSaKNQv/vxpuNgkGxEXSkWX93Sg==
Date: Fri, 20 Oct 2017 12:54:23 +0000
Message-ID: <D0AA7372-C4D2-416B-AAA3-3A0229E639AB@cisco.com>
References: <150833078446.12462.3050923622769989740.idtracker@ietfa.amsl.com> <CA+RyBmUnB6jaMMytXtiUZf98RnLG8f6LusmDdAXHYkb2y1AE5A@mail.gmail.com>
In-Reply-To: <CA+RyBmUnB6jaMMytXtiUZf98RnLG8f6LusmDdAXHYkb2y1AE5A@mail.gmail.com>
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.133]
Content-Type: multipart/alternative; boundary="_000_D0AA7372C4D2416BAAA33A0229E639ABciscocom_"
MIME-Version: 1.0
Archived-At: <https://mailarchive.ietf.org/arch/msg/rtg-bfd/NdflUivzCaTYfumMtgkfCBIBFnI>
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 12:54:27 -0000

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.

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.

Also I wonder if this should be bfd-mpls instead of mpls-bfd, given where RFC 5884 was advanced.

Thanks,

—
Carlos Pignataro, carlos@cisco.com<mailto: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<mailto: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<mailto: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<mailto:gregimirsky@gmail.com>>, Yanhua Zhao <zhao.yanhua3@zte.com.cn<mailto: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<http://tools.ietf.org/>;.

The IETF Secretariat


_______________________________________________
mpls mailing list
mpls@ietf.org<mailto:mpls@ietf.org>
https://www.ietf.org/mailman/listinfo/mpls