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

"Carlos Pignataro (cpignata)" <cpignata@cisco.com> Tue, 09 May 2017 16:07 UTC

Return-Path: <cpignata@cisco.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 47FCC1294AC; Tue, 9 May 2017 09:07:27 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -14.522
X-Spam-Level:
X-Spam-Status: No, score=-14.522 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, 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 YFdLccWn6s2N; Tue, 9 May 2017 09:07:25 -0700 (PDT)
Received: from rcdn-iport-3.cisco.com (rcdn-iport-3.cisco.com [173.37.86.74]) (using TLSv1.2 with cipher DHE-RSA-SEED-SHA (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 2E92212420B; Tue, 9 May 2017 09:07:25 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=cisco.com; i=@cisco.com; l=15804; q=dns/txt; s=iport; t=1494346045; x=1495555645; h=from:to:cc:subject:date:message-id:references: in-reply-to:mime-version; bh=z4kC/A4y1mfoT95b1XbYLX+H3rYIWFJpJ288HrXZ1QM=; b=gblv3Wg+qL95b0gVGi6OEQ2k2q6WmNFQyK9rW5+z3OXx23MYo4KWKg4I ZZorJmebo6pIqqqUFHMFA5ZFvjmxzfeK/igdCIgmNyJGPX4MYo9bb9V4b nBQgYXGyH3GG+Ks5pm5AzR0ep1x4RevNHS+WSUmarwAxZ1KAsq4Ua2Dx3 g=;
X-IronPort-Anti-Spam-Filtered: true
X-IronPort-Anti-Spam-Result: =?us-ascii?q?A0D4AACA6BFZ/4cNJK1dGQEBAQEBAQEBA?= =?us-ascii?q?QEBBwEBAQEBg1VigQwHg2KKGJFWiCOIF4U4gg8hAQqFeAIahFI/GAECAQEBAQE?= =?us-ascii?q?BAWsohRUBAQEBAwEBIUsJAhACAQgRAQIBAigDAgICHwYLFAMGCAIEDgUbiW4DF?= =?us-ascii?q?Q6yVoImhy4NgzgBAQEBAQEBAQEBAQEBAQEBAQEBAQEdhl+BXiuCcIJUTYElAQE?= =?us-ascii?q?7FgiCTC6CMQWJRIZehkuGXTsBhxuHKoRTggRVhGaKLIsqhHcog3YBDxA4gQpwF?= =?us-ascii?q?RwqEgGEKDkcgWN2AYZFgSGBDQEBAQ?=
X-IronPort-AV: E=Sophos;i="5.38,315,1491264000"; d="scan'208,217";a="232756573"
Received: from alln-core-2.cisco.com ([173.36.13.135]) by rcdn-iport-3.cisco.com with ESMTP/TLS/DHE-RSA-AES256-SHA; 09 May 2017 16:07:23 +0000
Received: from XCH-RTP-016.cisco.com (xch-rtp-016.cisco.com [64.101.220.156]) by alln-core-2.cisco.com (8.14.5/8.14.5) with ESMTP id v49G7NWB019458 (version=TLSv1/SSLv3 cipher=AES256-SHA bits=256 verify=FAIL); Tue, 9 May 2017 16:07:23 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.1210.3; Tue, 9 May 2017 12:07:22 -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.1210.000; Tue, 9 May 2017 12:07:22 -0400
From: "Carlos Pignataro (cpignata)" <cpignata@cisco.com>
To: Greg Mirsky <gregimirsky@gmail.com>
CC: "spring@ietf.org" <spring@ietf.org>, "rtg-bfd@ietf.org" <rtg-bfd@ietf.org>, "mpls@ietf.org" <mpls@ietf.org>
Thread-Topic: [mpls] New Version Notification for draft-mirsky-spring-bfd-00.txt
Thread-Index: AQHSyNwl4f82jzKO5Eq8Ccd1kzJOwKHsbA8AgAAB9QA=
Date: Tue, 9 May 2017 16:07:22 +0000
Message-ID: <F3C093E0-FE4E-41C0-B9EB-0CA1CB52DBE7@cisco.com>
References: <149430058880.24107.8628199428997673992.idtracker@ietfa.amsl.com> <CA+RyBmVA3G8eucX2Q0=bHGdr+awmiXAd44BOMkdOmTQkeA6aYQ@mail.gmail.com> <1C12E162-6B5C-4EF2-A3CB-3621C72BCFE9@cisco.com> <CA+RyBmXgfmL7+Bx-KxFcm=3tTtsCALmRhrhyX=uqF8kuDFw2nw@mail.gmail.com>
In-Reply-To: <CA+RyBmXgfmL7+Bx-KxFcm=3tTtsCALmRhrhyX=uqF8kuDFw2nw@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.117.115.52]
Content-Type: multipart/alternative; boundary="_000_F3C093E0FE4E41C0B9EB0CA1CB52DBE7ciscocom_"
MIME-Version: 1.0
Archived-At: <https://mailarchive.ietf.org/arch/msg/mpls/qdGFxgfnmdBZoSlymuXm7qBcaCc>
Subject: Re: [mpls] New Version Notification for draft-mirsky-spring-bfd-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: Tue, 09 May 2017 16:07:27 -0000

Thank you Greg!

Since https://tools.ietf.org/html/draft-mirsky-spring-bfd-00 seems quite similar to the text removed at https://tools.ietf.org/rfcdiff?url2=draft-ietf-mpls-bfd-directed-05.txt, then the complete set of outstanding technical comments that triggered the removal of that text from draft-ietf-mpls-bfd-directed-05.txt might peek your interest :-)

One that I recall is: why use label values when every other return-path sub-TLV for BFD and for LSP-Ping, including draft-ietf-mpls-bfd-directed, uses TFSs?

Best,

— Carlos.

On May 9, 2017, at 12:00 PM, Greg Mirsky <gregimirsky@gmail.com<mailto:gregimirsky@gmail.com>> wrote:

Dear Carlos,
I've decided to re-start the discussion and am interested to hear technical comments to the proposed solution.

Regards,
Greg

On Tue, May 9, 2017 at 8:51 AM, Carlos Pignataro (cpignata) <cpignata@cisco.com<mailto:cpignata@cisco.com>> wrote:
Dear Greg,

Cursorily scanning through this, it seems that most concerns raised and comments made about the SR sections of draft-ietf-mpls-bfd-directed-0N (with N < 5) apply to your new draft.

This is one of those: https://www.ietf.org/mail-archive/web/mpls/current/msg15860.html — the list archive shows a few more. The copy/paste did not address the comments.

Best,

— Carlos.

On May 8, 2017, at 11:33 PM, Greg Mirsky <gregimirsky@gmail.com<mailto:gregimirsky@gmail.com>> wrote:

Dear All,
perhaps this new draft may is of interest to you.
Your comments, suggestions are most welcome and greatly appreciated.

Regards,
Greg

---------- Forwarded message ----------
From: <internet-drafts@ietf.org<mailto:internet-drafts@ietf.org>>
Date: Mon, May 8, 2017 at 8:29 PM
Subject: New Version Notification for draft-mirsky-spring-bfd-00.txt
To: Gregory Mirsky <gregimirsky@gmail.com<mailto:gregimirsky@gmail.com>>



A new version of I-D, draft-mirsky-spring-bfd-00.txt
has been successfully submitted by Greg Mirsky and posted to the
IETF repository.

Name:           draft-mirsky-spring-bfd
Revision:       00
Title:          Bidirectional Forwarding Detection (BFD) in Segment Routing Networks Using MPLS Dataplane
Document date:  2017-05-08
Group:          Individual Submission
Pages:          7
URL:            https://www.ietf.org/internet-drafts/draft-mirsky-spring-bfd-00.txt
Status:         https://datatracker.ietf.org/doc/draft-mirsky-spring-bfd/
Htmlized:       https://tools.ietf.org/html/draft-mirsky-spring-bfd-00
Htmlized:       https://datatracker.ietf.org/doc/html/draft-mirsky-spring-bfd-00


Abstract:
   Segment Routing architecture leverages the paradigm of source
   routing.  It can be realized in the Multiprotocol Label Switching
   (MPLS) network without any change to the data plane.  A segment is
   encoded as an MPLS label and an ordered list of segments is encoded
   as a stack of labels.  Bidirectional Forwarding Detection (BFD) is
   expected to monitor any kind of paths between systems.  This document
   defines how to use Label Switched Path Ping to bootstrap and control
   path in reverse direction of a BFD session on the Segment Routing
   network over MPLS dataplane.




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