Re: [mpls] New Version Notification for draft-mirsky-mpls-p2mp-bfd-07.txt

"Carlos Pignataro (cpignata)" <cpignata@cisco.com> Mon, 10 June 2019 05:10 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 1C1CC120130; Sun, 9 Jun 2019 22:10:16 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -14.5
X-Spam-Level:
X-Spam-Status: No, score=-14.5 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, 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 header.b=QpOSaC+d; dkim=pass (1024-bit key) header.d=cisco.onmicrosoft.com header.b=m5Ch6XR8
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 5DA7PzgYPMRo; Sun, 9 Jun 2019 22:10:13 -0700 (PDT)
Received: from alln-iport-4.cisco.com (alln-iport-4.cisco.com [173.37.142.91]) (using TLSv1.2 with cipher DHE-RSA-SEED-SHA (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 3348712006F; Sun, 9 Jun 2019 22:10:13 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=cisco.com; i=@cisco.com; l=13143; q=dns/txt; s=iport; t=1560143413; x=1561353013; h=from:to:cc:subject:date:message-id:references: in-reply-to:mime-version; bh=inUynAimykBKvdJupqHMoZUs10KweIt+gndnQ2+uRGQ=; b=QpOSaC+diNdG/GX7w4gEQQ78J66MByodUqf8gniRcJG/+e1yma/iZlly iwpLxB1WlgZVvMG2ulzOmSm5adh6RdXU4GpUX7ppm7LlmlX89Skk5kpSU 7cJuxd0AJeBVZupVuh37G60TamfUPd1a9041exNdharX9w9cvKvIfzDRZ A=;
IronPort-PHdr: 9a23:jN81ABRo1WHOmcPsfUQRgxCFFdpsv++ubAcI9poqja5Pea2//pPkeVbS/uhpkESXBNfA8/wRje3QvuigQmEG7Zub+FE6OJ1XH15g640NmhA4RsuMCEn1NvnvOiciHctEXUNs13q6KkNSXs35Yg6arw==
X-IronPort-Anti-Spam-Filtered: true
X-IronPort-Anti-Spam-Result: A0ByAAA95f1c/5JdJa1lHAEBAQQBAQcEAQGBUgYBAQsBgT0kLANqVSAECyiEFYNHA45dgjIliUOJHYRSgS4UgRADVAkBAQEMAQEYAQoKAgEBhEACF4JUIzUIDgEDAQEEAQECAQRtHAyFSgEBAQQBARARHQEBLAkCAQ8CAQgRAwECKAMCAgIfBgsUCQgCBA4FGweDAAGBHU0DHQECDJs1AoE4iF9xgTGCeQEBBYE2Ag5BQIIyDQuCDwmBNAGEb4ZtF4FAP4EQAScME4JMPoIaRwEBAgEBFoEPBQESAR4hBgcRgkwygiaLXgmCQYRsIogcjRs+CQKCD4VpW4ZYgjuDaxuCJWmGE416lCaBY4o9gwcCBAIEBQIOAQEFgT0TATZncXAVGiEqAYJBCTWBUYNwhRSFP3IBgSiNAYJDAQE
X-IronPort-AV: E=Sophos;i="5.63,573,1557187200"; d="scan'208,217";a="282388878"
Received: from rcdn-core-10.cisco.com ([173.37.93.146]) by alln-iport-4.cisco.com with ESMTP/TLS/DHE-RSA-SEED-SHA; 10 Jun 2019 05:10:12 +0000
Received: from XCH-ALN-020.cisco.com (xch-aln-020.cisco.com [173.36.7.30]) by rcdn-core-10.cisco.com (8.15.2/8.15.2) with ESMTPS id x5A5AB4Q015277 (version=TLSv1.2 cipher=AES256-SHA bits=256 verify=FAIL); Mon, 10 Jun 2019 05:10:11 GMT
Received: from xhs-rtp-002.cisco.com (64.101.210.229) by XCH-ALN-020.cisco.com (173.36.7.30) with Microsoft SMTP Server (TLS) id 15.0.1473.3; Mon, 10 Jun 2019 00:10:11 -0500
Received: from xhs-aln-003.cisco.com (173.37.135.120) by xhs-rtp-002.cisco.com (64.101.210.229) with Microsoft SMTP Server (TLS) id 15.0.1473.3; Mon, 10 Jun 2019 01:10:09 -0400
Received: from NAM05-DM3-obe.outbound.protection.outlook.com (173.37.151.57) by xhs-aln-003.cisco.com (173.37.135.120) with Microsoft SMTP Server (TLS) id 15.0.1473.3 via Frontend Transport; Mon, 10 Jun 2019 00:10:09 -0500
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=cisco.onmicrosoft.com; s=selector2-cisco-onmicrosoft-com; h=From:Date:Subject:Message-ID:Content-Type:MIME-Version:X-MS-Exchange-SenderADCheck; bh=inUynAimykBKvdJupqHMoZUs10KweIt+gndnQ2+uRGQ=; b=m5Ch6XR877Avs2BXvxyZ5im9TWJbV5bHvduG3MwMgUrCD1u+SLF3E3AD0S6dJCbfqG1yBpGCOrKfRzinLTDuI3/U6V+NbUqbirNxgkSrHup3IraTnoQc69C+tAiueG7h+4/1IAZ4DtpBHUQUD3aM25pxB3yWJSK6iAsmyv5q1v8=
Received: from BL0PR11MB3028.namprd11.prod.outlook.com (20.177.204.138) by BL0PR11MB3137.namprd11.prod.outlook.com (20.177.206.27) with Microsoft SMTP Server (version=TLS1_2, cipher=TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384) id 15.20.1965.17; Mon, 10 Jun 2019 05:10:08 +0000
Received: from BL0PR11MB3028.namprd11.prod.outlook.com ([fe80::ec33:f4c1:227a:fcb3]) by BL0PR11MB3028.namprd11.prod.outlook.com ([fe80::ec33:f4c1:227a:fcb3%5]) with mapi id 15.20.1965.017; Mon, 10 Jun 2019 05:10:08 +0000
From: "Carlos Pignataro (cpignata)" <cpignata@cisco.com>
To: Greg Mirsky <gregimirsky@gmail.com>
CC: mpls <mpls@ietf.org>, "mpls-chairs@ietf.org" <mpls-chairs@ietf.org>
Thread-Topic: [mpls] New Version Notification for draft-mirsky-mpls-p2mp-bfd-07.txt
Thread-Index: AQHVH0rFdtBQRa0oc0WkjdOAQdNk5Q==
Date: Mon, 10 Jun 2019 05:10:08 +0000
Message-ID: <4ED514BF-A8AD-4233-BCEE-E4D7745C5733@cisco.com>
References: <155969758794.27970.7072691559400071749.idtracker@ietfa.amsl.com> <CA+RyBmXOfyThOUTN0k1qu=ZRhXddjL-vZbX0CUjTpvkksSZx1w@mail.gmail.com>
In-Reply-To: <CA+RyBmXOfyThOUTN0k1qu=ZRhXddjL-vZbX0CUjTpvkksSZx1w@mail.gmail.com>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach:
X-MS-TNEF-Correlator:
x-mailer: Apple Mail (2.3445.104.11)
authentication-results: spf=none (sender IP is ) smtp.mailfrom=cpignata@cisco.com;
x-originating-ip: [2001:420:c0c8:1001::506]
x-ms-publictraffictype: Email
x-ms-office365-filtering-correlation-id: 8d5e38c5-74de-4ee5-6de3-08d6ed61e867
x-microsoft-antispam: BCL:0; PCL:0; RULEID:(2390118)(7020095)(4652040)(8989299)(4534185)(4627221)(201703031133081)(201702281549075)(8990200)(5600148)(711020)(4605104)(1401327)(2017052603328)(7193020); SRVR:BL0PR11MB3137;
x-ms-traffictypediagnostic: BL0PR11MB3137:
x-ms-exchange-purlcount: 7
x-microsoft-antispam-prvs: <BL0PR11MB3137407937D1549A89D98627C7130@BL0PR11MB3137.namprd11.prod.outlook.com>
x-ms-oob-tlc-oobclassifiers: OLM:9508;
x-forefront-prvs: 0064B3273C
x-forefront-antispam-report: SFV:NSPM; SFS:(10009020)(136003)(346002)(39860400002)(366004)(396003)(376002)(199004)(22974007)(189003)(14454004)(57306001)(446003)(2616005)(6246003)(1411001)(486006)(476003)(256004)(14444005)(11346002)(7736002)(86362001)(68736007)(6116002)(53936002)(5660300002)(81166006)(81156014)(83716004)(2420400007)(15650500001)(82746002)(8936002)(8676002)(50226002)(66446008)(64756008)(76116006)(73956011)(66946007)(66476007)(66556008)(91956017)(71190400001)(71200400001)(6436002)(46003)(606006)(54906003)(6916009)(6486002)(229853002)(76176011)(99286004)(316002)(6306002)(25786009)(54896002)(53546011)(7110500001)(236005)(478600001)(6512007)(33656002)(4326008)(186003)(6506007)(66574012)(102836004)(2906002)(966005)(36756003); DIR:OUT; SFP:1101; SCL:1; SRVR:BL0PR11MB3137; H:BL0PR11MB3028.namprd11.prod.outlook.com; FPR:; SPF:None; LANG:en; PTR:InfoNoRecords; A:1; MX:1;
received-spf: None (protection.outlook.com: cisco.com does not designate permitted sender hosts)
x-ms-exchange-senderadcheck: 1
x-microsoft-antispam-message-info: /9vWR7HoEmAJm6M6uy9a06DuLw8ZFSaAiFCAKN/SL0esB4BYx7h+9oCGN+FS+AveL7rS6n26OU8mkAsEzMndFhk7Oz/Rx+p3OC7bvIQShrrRSs6F9pPA+yEexy931YfNIvWZAIjdvyvElIr7A6nhj8W20Crc6vRC1iflngKNa1mpriMobmaYlX8wNXdXc1gdhLHlaGj0uiFSJdUP0RfE+bl8iQug1ywPLLKqbbEeOMpHfOJMX5b6Ol8vs4rSV4+tTjjoUu5bn1BUuYL9Qz8Oi3AtsAXrs5fvbugo60yM7OGD0cVyHR7I/j/CyvBjETaG8LGS4gfQhyEA2zAec0KuTPZ/EuJq233C9bWSMNVmjugYJVYTDXzfKTzqeh+YSAIPpABpQH6JyN2clb05aXAhkq8qdvYA6U+mZDWSuWViNr4=
Content-Type: multipart/alternative; boundary="_000_4ED514BFA8AD4233BCEEE4D7745C5733ciscocom_"
MIME-Version: 1.0
X-MS-Exchange-CrossTenant-Network-Message-Id: 8d5e38c5-74de-4ee5-6de3-08d6ed61e867
X-MS-Exchange-CrossTenant-originalarrivaltime: 10 Jun 2019 05:10:08.4557 (UTC)
X-MS-Exchange-CrossTenant-fromentityheader: Hosted
X-MS-Exchange-CrossTenant-id: 5ae1af62-9505-4097-a69a-c1553ef7840e
X-MS-Exchange-CrossTenant-mailboxtype: HOSTED
X-MS-Exchange-CrossTenant-userprincipalname: cpignata@cisco.com
X-MS-Exchange-Transport-CrossTenantHeadersStamped: BL0PR11MB3137
X-OriginatorOrg: cisco.com
X-Outbound-SMTP-Client: 173.36.7.30, xch-aln-020.cisco.com
X-Outbound-Node: rcdn-core-10.cisco.com
Archived-At: <https://mailarchive.ietf.org/arch/msg/mpls/h7huh6zEPPbIOpVl99ojaXaj358>
Subject: Re: [mpls] New Version Notification for draft-mirsky-mpls-p2mp-bfd-07.txt
X-BeenThere: mpls@ietf.org
X-Mailman-Version: 2.1.29
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: Mon, 10 Jun 2019 05:10:18 -0000

Hello,

I’ve not looked at this whole document, but this email triggered me to check the encapsulation of BFD. So, while not commenting on the value of this document, I do have two questions: one on the encapsulation, one on the proposed new TLV.

The IP BFD encapsulation described here is the same for p2p and for multipoint, based on RFC 8562 and Section 3.1 of this doc, using destination UDP port 3784.

However, Section 3.2 requests a new G-ACh Channel Type (see Section 3.1) for “Multipoint BFD Session”, different than BFD over G-ACh as per RFC 5885.

Why this difference? What is the reason to have to differentiate with a new Channel Type?

Also, the “CC/CV MEP-ID TLV” is specified in RFC 6428, which is scoped to MPLS-TP. See also the scope in RFC 7276, defining usage of BFD in MPLS-TP. How is that proposed to be used for MPLS?

Best,

Carlos.

On Jun 5, 2019, at 4:40 PM, Greg Mirsky <gregimirsky@gmail.com<mailto:gregimirsky@gmail.com>> wrote:

Dear All,
the new version includes updates:

  *   request for the allocation of a new G-ACh type "Multipoint BFD Session"
  *   an extended explanation for the use of non-IP encapsulation of BFD control packet in multipoint BFD session over MPLS LSP
  *   updated references to RFC 8562 BFD for Multipoint Networks

Hope it helps to get WG AP decision.

Regards,
Greg

---------- Forwarded message ---------
From: <internet-drafts@ietf.org<mailto:internet-drafts@ietf.org>>
Date: Tue, Jun 4, 2019 at 6:19 PM
Subject: New Version Notification for draft-mirsky-mpls-p2mp-bfd-07.txt
To: Gregory Mirsky <gregimirsky@gmail.com<mailto:gregimirsky@gmail.com>>



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

Name:           draft-mirsky-mpls-p2mp-bfd
Revision:       07
Title:          BFD for Multipoint Networks over Point-to-Multi-Point MPLS LSP
Document date:  2019-06-04
Group:          mpls
Pages:          8
URL:            https://www.ietf.org/internet-drafts/draft-mirsky-mpls-p2mp-bfd-07.txt
Status:         https://datatracker.ietf.org/doc/draft-mirsky-mpls-p2mp-bfd/
Htmlized:       https://tools.ietf.org/html/draft-mirsky-mpls-p2mp-bfd-07
Htmlized:       https://datatracker.ietf.org/doc/html/draft-mirsky-mpls-p2mp-bfd
Diff:           https://www.ietf.org/rfcdiff?url2=draft-mirsky-mpls-p2mp-bfd-07

Abstract:
   This document describes procedures for using Bidirectional Forwarding
   Detection (BFD) for multipoint networks to detect data plane failures
   in Multiprotocol Label Switching (MPLS) point-to-multipoint (p2mp)
   Label Switched Paths (LSPs).  It also describes the applicability of
   LSP Ping, as in-band, and the control plane, as out-band, solutions
   to bootstrap a BFD session in this environment.




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