IETF Logo Mail Archive

Re: [mpls] MPLS-RT review of draft-mirsky-mpls-bfd-directed-03

Markus Jork <mjork@juniper.net> Thu, 09 July 2015 21:23 UTC

Return-Path: <mjork@juniper.net>
X-Original-To: mpls@ietfa.amsl.com
Delivered-To: mpls@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 74AB31A0396; Thu, 9 Jul 2015 14:23:53 -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, RCVD_IN_DNSWL_NONE=-0.0001, SPF_HELO_PASS=-0.001, SPF_PASS=-0.001] autolearn=ham
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 98TKqFVsl9MM; Thu, 9 Jul 2015 14:23:52 -0700 (PDT)
Received: from na01-bl2-obe.outbound.protection.outlook.com (mail-bl2on0104.outbound.protection.outlook.com [65.55.169.104]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-SHA384 (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id E4D281A036A; Thu, 9 Jul 2015 14:23:51 -0700 (PDT)
Received: from CO2PR0501MB919.namprd05.prod.outlook.com (10.141.247.22) by CO2PR0501MB918.namprd05.prod.outlook.com (10.141.247.21) with Microsoft SMTP Server (TLS) id 15.1.207.19; Thu, 9 Jul 2015 21:23:50 +0000
Received: from CO2PR0501MB919.namprd05.prod.outlook.com ([10.141.247.22]) by CO2PR0501MB919.namprd05.prod.outlook.com ([10.141.247.22]) with mapi id 15.01.0207.004; Thu, 9 Jul 2015 21:23:49 +0000
From: Markus Jork <mjork@juniper.net>
To: "mpls-chairs@ietf.org" <mpls-chairs@ietf.org>, Gregory Mirsky <gregory.mirsky@ericsson.com>, Jeff Tantsura <jeff.tantsura@ericsson.com>, Mach Chen <mach.chen@huawei.com>, "Ilya@nobulus.com" <Ilya@nobulus.com>
Thread-Topic: MPLS-RT review of draft-mirsky-mpls-bfd-directed-03
Thread-Index: AQHQrp6jgU6mEKrEDEixCriNRyOIhJ3TtJgQ
Date: Thu, 09 Jul 2015 21:23:49 +0000
Message-ID: <CO2PR0501MB919738C04D7063D7CBC0B56A5900@CO2PR0501MB919.namprd05.prod.outlook.com>
References: <BY1PR0501MB14307CC8225AFFA12887B0C0A5AF0@BY1PR0501MB1430.namprd05.prod.outlook.com>
In-Reply-To: <BY1PR0501MB14307CC8225AFFA12887B0C0A5AF0@BY1PR0501MB1430.namprd05.prod.outlook.com>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach:
X-MS-TNEF-Correlator:
authentication-results: ietf.org; dkim=none (message not signed) header.d=none;
x-originating-ip: [66.129.241.12]
x-microsoft-exchange-diagnostics: 1; CO2PR0501MB918; 5:5i/ewocYQ1BLx0+AqGAVWyTIEjUI1AEHJ/gbdlrQokdqFG3pjUm3qo0fdHE7RzNsVSiZ5zrvhUC8mFv7557h8XRn2bjmVg3sVNH7SmFkO/zbWF+ZaTrgummzct8ghL/jy1ItGsD2/2ofgVLZ5T7lSA==; 24:h6LS0dVbxKsMOzDCbMeehmN6f/8w8GI4PAEDqliGh6wtIwZyLAlVR8xN7wkpjljA8nQtTmzzP2FMy3oLrxyY8NhzaVUSg7NDfYQvqVt3izE=; 20:deM3N+RIbxCf4nhmcjAhmKPNsrNxSXMI13MsmDBlMLUfpzGwvpNk3YuSvfjodGDjm6Qiw3KS4DvQ3VWgw2IFww==
x-microsoft-antispam: UriScan:;BCL:0;PCL:0;RULEID:;SRVR:CO2PR0501MB918;
x-microsoft-antispam-prvs: <CO2PR0501MB918722AF559C572DDD4A5B3A5900@CO2PR0501MB918.namprd05.prod.outlook.com>
x-exchange-antispam-report-test: UriScan:;
x-exchange-antispam-report-cfa-test: BCL:0; PCL:0; RULEID:(601004)(5005006)(3002001); SRVR:CO2PR0501MB918; BCL:0; PCL:0; RULEID:; SRVR:CO2PR0501MB918;
x-forefront-prvs: 0632519F33
x-forefront-antispam-report: SFV:NSPM; SFS:(10019020)(6009001)(5001920100001)(66066001)(5002640100001)(5001770100001)(62966003)(33656002)(99286002)(86362001)(77156002)(46102003)(106116001)(5003600100002)(2656002)(230783001)(92566002)(102836002)(2501003)(76576001)(2900100001)(2950100001)(54356999)(5001960100002)(189998001)(76176999)(50986999)(74316001)(87936001)(122556002)(40100003)(77096005); DIR:OUT; SFP:1102; SCL:1; SRVR:CO2PR0501MB918; H:CO2PR0501MB919.namprd05.prod.outlook.com; FPR:; SPF:None; MLV:sfv; LANG:en;
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: quoted-printable
MIME-Version: 1.0
X-OriginatorOrg: juniper.net
X-MS-Exchange-CrossTenant-originalarrivaltime: 09 Jul 2015 21:23:49.5889 (UTC)
X-MS-Exchange-CrossTenant-fromentityheader: Hosted
X-MS-Exchange-CrossTenant-id: bea78b3c-4cdb-4130-854a-1d193232e5f4
X-MS-Exchange-Transport-CrossTenantHeadersStamped: CO2PR0501MB918
Archived-At: <http://mailarchive.ietf.org/arch/msg/mpls/4ThbXk5uR883ecesRHc8FgXCmBk>
Cc: "mpls@ietf.org" <mpls@ietf.org>
Subject: Re: [mpls] MPLS-RT review of draft-mirsky-mpls-bfd-directed-03
X-BeenThere: mpls@ietf.org
X-Mailman-Version: 2.1.15
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, 09 Jul 2015 21:23:53 -0000

I have looked at draft-mirsky-mpls-bfd-directed-03 as one of the MPLS-RT reviewers.

The document clearly explains the desire to have a matching return path for a BFD session and proposes a straight forward mechanism for that. As such it is coherent.

The mechanism is based on the initiator of the BFD session picking and specifying the return path. I can imagine use cases where that is the preferable approach. Though one could also go about this from the other direction: let the other end pick a return path that matches the forward path. That would not require protocol extensions. Nevertheless, there are probably enough cases where the mechanism in this document is appropriate and so I think it will be useful.

The document seems technically sound to me and is ready to be considered for WG adoption.

-Markus

v2.23.0 | Report a Bug | By Email