Re: [Idr] WG LC on draft-ietf-idr-bgp-ls-segment-routing-msd-05.txt - WG consensus pending

"Ketan Talaulikar (ketant)" <ketant@cisco.com> Tue, 10 September 2019 17:13 UTC

Return-Path: <ketant@cisco.com>
X-Original-To: idr@ietfa.amsl.com
Delivered-To: idr@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id D4FDB120058; Tue, 10 Sep 2019 10:13:52 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -14.499
X-Spam-Level:
X-Spam-Status: No, score=-14.499 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, 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 header.b=gCpeEFA0; dkim=pass (1024-bit key) header.d=cisco.onmicrosoft.com header.b=d5WFNCyc
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 g5u9vGXy4RjF; Tue, 10 Sep 2019 10:13:50 -0700 (PDT)
Received: from alln-iport-7.cisco.com (alln-iport-7.cisco.com [173.37.142.94]) (using TLSv1.2 with cipher DHE-RSA-SEED-SHA (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 420F8120041; Tue, 10 Sep 2019 10:13:50 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=cisco.com; i=@cisco.com; l=25643; q=dns/txt; s=iport; t=1568135630; x=1569345230; h=from:to:cc:subject:date:message-id:references: in-reply-to:mime-version; bh=eranaPLNuzk98O9rQ/Zc4mHxKuBz12BicZiaFjKtihQ=; b=gCpeEFA00XVWASf3tw8NHbK+cY3eYBddYLtx8RSPSSBgf7/pbhwPb0ar iR4jZtYi5pMh9ab1BvJ7KDTqAQExcbTHx2NxMab5wfOZtd+yUzau2c5Uf WpJRAhocJ2PtIzShTBS0iIsgsuD2z2MaL55FUM5cu7M3RHByx3WzwRJ+K E=;
IronPort-PHdr: =?us-ascii?q?9a23=3Ap/QzNROhfN8wdrLXDQkl6mtXPHoupqn0MwgJ65?= =?us-ascii?q?Eul7NJdOG58o//OFDEuKQ/l0fHCIPc7f8My/HbtaztQyQh2d6AqzhDFf4ETB?= =?us-ascii?q?oZkYMTlg0kDtSCDBj4IeLjaTASF8VZX1gj9Ha+YgBY?=
X-IronPort-Anti-Spam-Filtered: true
X-IronPort-Anti-Spam-Result: =?us-ascii?q?A0B/AABf2Xdd/5JdJa1kGQEBAQEBAQE?= =?us-ascii?q?BAQEBAQcBAQEBAQGBZ4EWL1ADbVYgBAsqh2gDinuCXH6WcoJSA1QJAQEBDAE?= =?us-ascii?q?BJQgCAQGEPwKCSSM4EwIDCQEBBAEBAQIBBgRthS4MhUoBAQEBAxIbEwEBNwE?= =?us-ascii?q?PAgEIDgMEAQEhBwcyFAkIAQEEAQ0FCBqDAYEdTQMdAQ6dIwKBOIhhgiWCfQE?= =?us-ascii?q?BBYUGGIIWAwaBNIt4GIFAP4ERRoIXNT6BBAGBXAICgWErCYMHgiaMThIwAod?= =?us-ascii?q?Pl2oKgiGHAY4RgjSHQI8WJI1bgTiGTJBqAgQCBAUCDgEBBYFpIYFYcBU7gmy?= =?us-ascii?q?CQjiDOoUUhT9zgSmOfwEB?=
X-IronPort-AV: E=Sophos;i="5.64,490,1559520000"; d="scan'208,217";a="323499762"
Received: from rcdn-core-10.cisco.com ([173.37.93.146]) by alln-iport-7.cisco.com with ESMTP/TLS/DHE-RSA-SEED-SHA; 10 Sep 2019 17:13:49 +0000
Received: from XCH-RCD-020.cisco.com (xch-rcd-020.cisco.com [173.37.102.30]) by rcdn-core-10.cisco.com (8.15.2/8.15.2) with ESMTPS id x8AHDmOf004388 (version=TLSv1.2 cipher=AES256-SHA bits=256 verify=FAIL); Tue, 10 Sep 2019 17:13:49 GMT
Received: from xhs-aln-002.cisco.com (173.37.135.119) by XCH-RCD-020.cisco.com (173.37.102.30) with Microsoft SMTP Server (TLS) id 15.0.1473.3; Tue, 10 Sep 2019 12:13:48 -0500
Received: from xhs-rtp-002.cisco.com (64.101.210.229) by xhs-aln-002.cisco.com (173.37.135.119) with Microsoft SMTP Server (TLS) id 15.0.1473.3; Tue, 10 Sep 2019 12:13:47 -0500
Received: from NAM01-SN1-obe.outbound.protection.outlook.com (64.101.32.56) by xhs-rtp-002.cisco.com (64.101.210.229) with Microsoft SMTP Server (TLS) id 15.0.1473.3 via Frontend Transport; Tue, 10 Sep 2019 13:13:46 -0400
ARC-Seal: i=1; a=rsa-sha256; s=arcselector9901; d=microsoft.com; cv=none; b=ZRGo8wwIjjC9TTRdJ/hAo067/vgGzfY1RPj1Txhc566lLe/snqH5sIsTad9wuYTLktOslJ7t/nZITWzGuaem4Co0rPZGdlOEyaAaoRJUIeJabUBe2ONbzpHnehCoHhXRHnikrb3W0o46rli19OBAgTs7dAc1M0HmUshXCcjW+Ip8rONxNCU2f7KqEPGpcM5t2oQzhUWJPVnQ4m4L+PJEaaYzxSryPsyw5SE5ni0Bczy/X/cQ76twfgljrvmSzgK5+D/RtvEWSEUBsqv3k+Sf3HoHfctXSGRPr8vruccEZKbn9NLqAINGl3UwzHEArWu0KrYfIMrNJUNbmUSfDKPNLQ==
ARC-Message-Signature: i=1; a=rsa-sha256; c=relaxed/relaxed; d=microsoft.com; s=arcselector9901; h=From:Date:Subject:Message-ID:Content-Type:MIME-Version:X-MS-Exchange-SenderADCheck; bh=OJ5BevZFmSLQzufVVwns831yqOY0fR3ez4D0dY3yP6A=; b=TcyddUTPiN4crbnEuyWBQF8yP2EPtylmUKEN/MzQM32Gs4b6KF6NOrpIZyFlsOv3Tf2uw5aSTVWira+G9GWxgXWj00SA/SNjcmG33aztQGPLwgjT7mBZ9TtznKuWk03n7zo6AxEVemm+CjxXpPmSB0d0s0YmCjnwLAhl4JDZ/soBqDj32MCXDRFIeNhSJPJQ590oNEvEFY8GxWiHykp25y5828CcDvPbbC/mCqUj1w64ZOl5m/pyJVys1y1GlSaoUDjXprOsPUcEdVwf89nR/YKdsD+J8BNKE4L0dkOrOdtuvF09Xh2GUgoE+FxsyImkvz15GLYMVxzSUmec8TkH2A==
ARC-Authentication-Results: i=1; mx.microsoft.com 1; spf=pass smtp.mailfrom=cisco.com; dmarc=pass action=none header.from=cisco.com; dkim=pass header.d=cisco.com; arc=none
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=OJ5BevZFmSLQzufVVwns831yqOY0fR3ez4D0dY3yP6A=; b=d5WFNCycGYmhHKuXBZ0OwHJ8yGi/4TJtkuTynQ4HKFgsAbisfVKC8dYcbQ0YWl6EGhQ1IBVmYW1DJNAY+Xqr5Io42h+qobLBhSh1ZfZfc/MYC7k7dQeWQ7R4FAM18wruCLxfirneO8LT3zZiKgQWag0s/m5zDznRoMljZqEd3fk=
Received: from CY4PR11MB1541.namprd11.prod.outlook.com (10.172.68.150) by CY4PR11MB1925.namprd11.prod.outlook.com (10.175.82.14) with Microsoft SMTP Server (version=TLS1_2, cipher=TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384) id 15.20.2241.20; Tue, 10 Sep 2019 17:13:45 +0000
Received: from CY4PR11MB1541.namprd11.prod.outlook.com ([fe80::297e:b901:3eca:88af]) by CY4PR11MB1541.namprd11.prod.outlook.com ([fe80::297e:b901:3eca:88af%12]) with mapi id 15.20.2241.018; Tue, 10 Sep 2019 17:13:45 +0000
From: "Ketan Talaulikar (ketant)" <ketant@cisco.com>
To: Susan Hares <shares@ndzh.com>, "idr@ietf.org" <idr@ietf.org>
CC: "draft-ietf-idr-bgp-ls-segment-routing-msd@ietf.org" <draft-ietf-idr-bgp-ls-segment-routing-msd@ietf.org>
Thread-Topic: [Idr] WG LC on draft-ietf-idr-bgp-ls-segment-routing-msd-05.txt - WG consensus pending
Thread-Index: AdVNQg8h1R/9RzbbQNWIOPyzclLjdQAlreHAADsvrIABLbIQAAUfnJ2g
Date: Tue, 10 Sep 2019 17:13:45 +0000
Message-ID: <CY4PR11MB154103D58B871688531D0BF9C1B60@CY4PR11MB1541.namprd11.prod.outlook.com>
References: <01d601d54d44$da468ff0$8ed3afd0$@ndzh.com> <BYAPR11MB3558E18E1E92C8E6254C8C75C1D70@BYAPR11MB3558.namprd11.prod.outlook.com> <01dd01d54ec5$85daa3c0$918feb40$@ndzh.com> <01d101d5537c$4df1ccc0$e9d56640$@ndzh.com>
In-Reply-To: <01d101d5537c$4df1ccc0$e9d56640$@ndzh.com>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach:
X-MS-TNEF-Correlator:
authentication-results: spf=none (sender IP is ) smtp.mailfrom=ketant@cisco.com;
x-originating-ip: [2001:420:c0e0:1007::246]
x-ms-publictraffictype: Email
x-ms-office365-filtering-correlation-id: fe0defe2-9645-462e-ac61-08d736123cf9
x-microsoft-antispam: BCL:0; PCL:0; RULEID:(2390118)(7020095)(4652040)(8989299)(4534185)(4627221)(201703031133081)(201702281549075)(8990200)(5600166)(711020)(4605104)(1401327)(2017052603328)(7193020); SRVR:CY4PR11MB1925;
x-ms-traffictypediagnostic: CY4PR11MB1925:
x-ms-exchange-purlcount: 3
x-microsoft-antispam-prvs: <CY4PR11MB1925CCA870E3F5F907AE46D0C1B60@CY4PR11MB1925.namprd11.prod.outlook.com>
x-ms-oob-tlc-oobclassifiers: OLM:10000;
x-forefront-prvs: 01565FED4C
x-forefront-antispam-report: SFV:NSPM; SFS:(10009020)(4636009)(396003)(39860400002)(136003)(366004)(376002)(346002)(199004)(189003)(446003)(9326002)(71200400001)(11346002)(81166006)(14454004)(25786009)(478600001)(52536014)(5660300002)(53936002)(33656002)(486006)(53546011)(6506007)(102836004)(6306002)(54896002)(236005)(14444005)(316002)(256004)(110136005)(790700001)(46003)(6116002)(2906002)(71190400001)(4326008)(966005)(55016002)(476003)(99286004)(2501003)(8936002)(76176011)(74316002)(76116006)(9686003)(8676002)(81156014)(7696005)(6436002)(66946007)(6246003)(66446008)(64756008)(66556008)(66476007)(229853002)(86362001)(7736002)(606006)(186003); DIR:OUT; SFP:1101; SCL:1; SRVR:CY4PR11MB1925; H:CY4PR11MB1541.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: Lcsp2ugOMQpLtvqUNDv0YvtaFNMDE/HNQQKJfRdrCtohcjmoCLR4pHFgK5JphyM9w5ixGVPJfs4xw9oroUgKEwKW+C4nk28dNrAluVGRTxMBF9Z/dINzWVGVvDILdtwiyACKQy3Y8K0EzJAVVRxXJMhOD+1IrUrX1MQ95MR7Mc9hCjndAnsc5Qzhfzn8aL3MEOf9qwhMP+u7jxss1xk/VVHVsf+iUt/V5UPNxEK4Rr00M3L43lDUO5D1ULhjzwmg9cmMJVdYSstl436w9zT1eD4ysqufKLKnbtlztkx+2UXYpjUJdxV2zhAGzii0EJPg5640nX+zWwW29kE0YtaIAdYmW/JbtRRvzm7SaHcfM55zIFjjJizNSi/n3dI7mPkcD0pxZTKKML5394mk5YMCFLLdoT3NqOzhkQDeF2grghI=
x-ms-exchange-transport-forked: True
Content-Type: multipart/alternative; boundary="_000_CY4PR11MB154103D58B871688531D0BF9C1B60CY4PR11MB1541namp_"
MIME-Version: 1.0
X-MS-Exchange-CrossTenant-Network-Message-Id: fe0defe2-9645-462e-ac61-08d736123cf9
X-MS-Exchange-CrossTenant-originalarrivaltime: 10 Sep 2019 17:13:45.5081 (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: xTOCjTB7rNKe6x/jeQxFhVS4Sh4ta8hjmsPSzr0WhIWndxX5AdOlprHJyCaFDli7WaA5kJCBNAnatOB7F1EEkQ==
X-MS-Exchange-Transport-CrossTenantHeadersStamped: CY4PR11MB1925
X-OriginatorOrg: cisco.com
X-Outbound-SMTP-Client: 173.37.102.30, xch-rcd-020.cisco.com
X-Outbound-Node: rcdn-core-10.cisco.com
Archived-At: <https://mailarchive.ietf.org/arch/msg/idr/ceTUM4fa4MFCcyFDluoqZudqwkE>
Subject: Re: [Idr] WG LC on draft-ietf-idr-bgp-ls-segment-routing-msd-05.txt - WG consensus pending
X-BeenThere: idr@ietf.org
X-Mailman-Version: 2.1.29
Precedence: list
List-Id: Inter-Domain Routing <idr.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/idr>, <mailto:idr-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/idr/>
List-Post: <mailto:idr@ietf.org>
List-Help: <mailto:idr-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/idr>, <mailto:idr-request@ietf.org?subject=subscribe>
X-List-Received-Date: Tue, 10 Sep 2019 17:13:53 -0000

Hi Sue,

We have published the v06 last week. There have been no further implementation report updates (besides the two that were done previously).

Could you please review the draft and implementation report updates for the draft progression?

Thanks,
Ketan

From: Susan Hares <shares@ndzh.com>
Sent: 15 August 2019 20:46
To: idr@ietf.org
Cc: draft-ietf-idr-bgp-ls-segment-routing-msd@ietf.org
Subject: RE: [Idr] WG LC on draft-ietf-idr-bgp-ls-segment-routing-msd-05.txt - WG consensus pending

The WG LC on draft-ietf-idr-bgp-ls-segment-routing-msd-05.txt has completed.

The authors should

  1.  Submit draft-ietf-idr-bgp-ls-segment-routing-msd-06.txt
  2.  Complete the Wiki page on the implementations.

At that point, the Shepherd report can be completed, and the draft sent to Alvaro for review.

Cheerily, Sue
From: Idr [mailto:idr-bounces@ietf.org] On Behalf Of Susan Hares
Sent: Friday, August 9, 2019 11:17 AM
To: idr@ietf.org<mailto:idr@ietf.org>
Subject: Re: [Idr] WG LC on draft-ietf-idr-bgp-ls-segment-routing-msd-05.txt - WG consensus pending

Ketan:

Thank you for this response.   Please send me a note when you begin you have completed -06.txt,
and any updates.

I encourage other implementers to either update the web page
https://trac.ietf.org/trac/idr/wiki/draft-ietf-idr-bgp-ls-segment-routing-msd%20implementations

or to send information to the WG chairs.

Cheerily, Susan Hares


From: Ketan Talaulikar (ketant) [mailto:ketant@cisco.com]
Sent: Thursday, August 8, 2019 7:07 AM
To: Susan Hares; 'IDR'
Cc: draft-ietf-idr-bgp-ls-segment-routing-msd@ietf.org<mailto:draft-ietf-idr-bgp-ls-segment-routing-msd@ietf.org>
Subject: RE: WG LC on draft-ietf-idr-bgp-ls-segment-routing-msd-05.txt - WG consensus pending

Hi Sue/All,

The authors are working on the update and we'll post it once done/ready.

I've updated the implementation report with most of the items that you have suggested for the implementations that I am aware of. For the error handling part, since that text would get added in v06, we can look at that aspect after the posting is done.

I believe there are other implementations and would request WG members to update the same at https://trac.ietf.org/trac/idr/wiki/draft-ietf-idr-bgp-ls-segment-routing-msd%20implementations

Thanks,
Ketan

From: Susan Hares <shares@ndzh.com<mailto:shares@ndzh.com>>
Sent: 07 August 2019 22:54
To: 'IDR' <idr@ietf.org<mailto:idr@ietf.org>>
Cc: draft-ietf-idr-bgp-ls-segment-routing-msd@ietf.org<mailto:draft-ietf-idr-bgp-ls-segment-routing-msd@ietf.org>
Subject: WG LC on draft-ietf-idr-bgp-ls-segment-routing-msd-05.txt - WG consensus pending

The WG LC on draft-ietf-idr-bgp-ls-segment-routing-msd-05.txt concludes on 8/8/2019.

At this point, we have about 12 people who have participated in this last call by making comments.   All comments regarding publication appear to be positive.   If you wish to make additional comments, please make your comments by 8/8/2019.

The implementations come from a single vendor (cisco).  A 1 week query will be made (starting on 8/8/2019)  to determine if the WG will accept 2 implementations from the same vendor to meet IDR requirement for 2 implementations.

The authors of this draft (Jeff,  Uma, Ketan, Greg, Nikos) need to do the following:

  1.  Post an -06.txt  revision that addresses any comments received at IETF 105 or on the WG list,
  2.  Upgrade the interoperability report at
  https://trac.ietf.org/trac/idr/wiki/draft-ietf-idr-bgp-ls-segment-routing-msd%20implementations

With details on the following MUST Clause support

Reference are:  section 3

      *  MSD-Value : a number in the range of 0-255.  For all MSD-Types,
         0 represents the lack of ability to impose an MSD stack of any
         depth; any other value represents that of the node.  This value
         MUST represent the lowest value supported by any link
         configured for use by the advertising protocol instance.]
Reference in section 4: - a similar definition

      *  MSD-Value : a number in the range of 0-255.  For all MSD-Types,

         0 represents the lack of ability to impose an MSD stack of any

         depth; any other value represents that of the link when used as

         an outgoing interface.]


Expected addition to Wiki document is the following information
------------------------------------------------------------------------------
Support for zero MSD-value:
    Node MSD TLV:  yes/no
    Link MSD TLV: yes/no

Mechanism for reporting zero-value:

Error handling of MSD TLV  (according to RFC7752):
  Node MSD TLV:  yes/no
  Link MSD TLV :    yes /no


Mechanism for reporting errors on MSD TLV:  (log error in log file)