IETF Logo Mail Archive

Re: [Idr] Need information on planned implementations of draft-ietf-idr-bgp-ls-segment-routing-msd-07

"Ketan Talaulikar (ketant)" <ketant@cisco.com> Thu, 12 September 2019 07:50 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 EE25712082E for <idr@ietfa.amsl.com>; Thu, 12 Sep 2019 00:50:07 -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=AL0sIv1S; dkim=pass (1024-bit key) header.d=cisco.onmicrosoft.com header.b=kbH6ea+r
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 76ABSwPd4-mf for <idr@ietfa.amsl.com>; Thu, 12 Sep 2019 00:50:05 -0700 (PDT)
Received: from rcdn-iport-5.cisco.com (rcdn-iport-5.cisco.com [173.37.86.76]) (using TLSv1.2 with cipher DHE-RSA-SEED-SHA (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 3AA2D12080C for <idr@ietf.org>; Thu, 12 Sep 2019 00:50:05 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=cisco.com; i=@cisco.com; l=16652; q=dns/txt; s=iport; t=1568274605; x=1569484205; h=from:to:subject:date:message-id:references:in-reply-to: mime-version; bh=UFkpZHfSKYd8BvKv83R5Ix5k78yefc+7iZeGX6xgdw0=; b=AL0sIv1SngYn1shyE2W0butYJsqQ4e2qbfq+zRgwS9uOtuiyjYKmIJLA JiCXsgf3Y6TQZGsqSkhd8Lh+Pq4DnYiitlyaWKye4ucvvSv4eVjdBaMAf 7cP0gWuobEAZZDevr8jpLOtZ4oLiCTjFZEo8OzJFgNFpzTn7r0EZ5R3pL w=;
IronPort-PHdr: 9a23:tkg8Px3J2GCxHrvksmDT+zVfbzU7u7jyIg8e44YmjLQLaKm44pD+JxGOt+51ggrPWoPWo7JfhuzavrqoeFRI4I3J8RVgOIdJSwdDjMwXmwI6B8vQCkDnJfj2Ryc7B89FElRi+iLzPA==
X-IronPort-Anti-Spam-Filtered: true
X-IronPort-Anti-Spam-Result: A0D9AQD193ld/4YNJK1mGwEBAQEDAQEBBwMBAQGBZ4EWL1ADbVYgBAsqhCGDRwOKZk2CD5MUhFyCUgNUCQEBAQwBASUIAgEBhD8CF4JAIzgTAgMJAQEEAQEBAgEGBG2FLgyFSgEBAQEDEhEKEwEBOA8CAQYCDgMEAQEkBAMCAgIwFAkIAQEEARIIGoMBgR1NAx0BDo5/kGECgTiIYXOBMoJ9AQEFhQwYgXwaAwaBNIt4GIFAP4FXghc1PoJhAgKBYSsJglUygiaPQIUhiRiOUgqCIYcBh1+GMoI0h0CPFoo+g0GIBJBqAgQCBAUCDgEBBYFpIYFYcBU7gmyCQjiDOoUUhT9zgSmOfwEB
X-IronPort-AV: E=Sophos;i="5.64,495,1559520000"; d="scan'208,217";a="409337706"
Received: from alln-core-12.cisco.com ([173.36.13.134]) by rcdn-iport-5.cisco.com with ESMTP/TLS/DHE-RSA-SEED-SHA; 12 Sep 2019 07:50:04 +0000
Received: from XCH-ALN-015.cisco.com (xch-aln-015.cisco.com [173.36.7.25]) by alln-core-12.cisco.com (8.15.2/8.15.2) with ESMTPS id x8C7o3Kg029128 (version=TLSv1.2 cipher=AES256-SHA bits=256 verify=FAIL); Thu, 12 Sep 2019 07:50:04 GMT
Received: from xhs-rcd-003.cisco.com (173.37.227.248) by XCH-ALN-015.cisco.com (173.36.7.25) with Microsoft SMTP Server (TLS) id 15.0.1473.3; Thu, 12 Sep 2019 02:50:03 -0500
Received: from xhs-aln-002.cisco.com (173.37.135.119) by xhs-rcd-003.cisco.com (173.37.227.248) with Microsoft SMTP Server (TLS) id 15.0.1473.3; Thu, 12 Sep 2019 02:50:02 -0500
Received: from NAM01-BN3-obe.outbound.protection.outlook.com (173.37.151.57) by xhs-aln-002.cisco.com (173.37.135.119) with Microsoft SMTP Server (TLS) id 15.0.1473.3 via Frontend Transport; Thu, 12 Sep 2019 02:50:02 -0500
ARC-Seal: i=1; a=rsa-sha256; s=arcselector9901; d=microsoft.com; cv=none; b=V1WUUStUNXGDMZH4G0SguZhpVFlvyggQnc/k8bYMFF+tsxrLNSQwB0wHOkXwv67xYj0U4/BVZ+gLF2FsrQ9T57v++4z4H92TMGKkvFU070FV8fUqVXuVPxc38PJKMFdtuWqINJ1mMC0YjOQhjSKwMAylA4jWWP7QykQN/KwJjkJV57KgU7C1Ini7CKpTQyuElowHgltL49DsWQMLZFnIGZzcgZlM08F4rcGcRv+8WvNEpZ6zYu3FeHjUqiKSspangeLWRZnCtoTJ990Fz+eQk5xwOY8iSWLw+Bn80azDZK6JnN4AruyGl/Uq7PbrL08KfQXSfrderrzdQariIdPgNg==
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=UFkpZHfSKYd8BvKv83R5Ix5k78yefc+7iZeGX6xgdw0=; b=Yb0nPifOniQO5ZH+Bi2vMCYeGiqHnnw573wc/CXM7qsMn87FKZzMutFMsKC5ffbdwKnFZKhy5z4BpzWU+bsdk0wBOrOZnaRBNow3HSBnrE4/h4bN/z6ClydYJhMKCJJFfngQ+1q5tzBh7/qrUUNJ2O5zW/kH3Sgca3qt/9LWpWAPiJUSeVeEUiLr7ELdVbX77ZTZ5xVe/uZZUXWAV3XFeuYwOZWsUHFGd72evpItQl9+7hitZsriwo50OoWdQaptrzyeVQ2UHnAiB+RWAp/yS/YGxBizCppt+jfkSB4J0SsOKhUonyfysRIvcYT+KFipin5DebrK6VnZhLVIJfbEdg==
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=UFkpZHfSKYd8BvKv83R5Ix5k78yefc+7iZeGX6xgdw0=; b=kbH6ea+rBStXI5bCrm6DbOxlPaRe0GpWMFuMrBlUtJ6HfJBTEsFPf5IIaLpJj2nTU9cxWjZQLv+08zlRMaGfOsAmkUIJ6L66x6jVkeW8JqZMxdHRC00wBdhHdi0WANQNzvXud7RJ57ylMUwbz8XWBHNwqfg2H0EktTeSy21II3s=
Received: from CY4PR11MB1541.namprd11.prod.outlook.com (10.172.68.150) by CY4PR11MB2024.namprd11.prod.outlook.com (10.169.254.16) with Microsoft SMTP Server (version=TLS1_2, cipher=TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384) id 15.20.2263.13; Thu, 12 Sep 2019 07:50:01 +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.022; Thu, 12 Sep 2019 07:50:01 +0000
From: "Ketan Talaulikar (ketant)" <ketant@cisco.com>
To: Susan Hares <shares@ndzh.com>, "idr@ietf.org" <idr@ietf.org>
Thread-Topic: [Idr] Need information on planned implementations of draft-ietf-idr-bgp-ls-segment-routing-msd-07
Thread-Index: AdVpL7UeN6a8vL6RTdKZ+TJgoqO4EwACL9EgAAFSRYAAACkd4A==
Date: Thu, 12 Sep 2019 07:50:01 +0000
Message-ID: <CY4PR11MB1541E2EE5C87942ECB65346DC1B00@CY4PR11MB1541.namprd11.prod.outlook.com>
References: <001e01d56931$54a633b0$fdf29b10$@ndzh.com> <CY4PR11MB1541212B93FAE0BD59A97ABAC1B00@CY4PR11MB1541.namprd11.prod.outlook.com> <018801d5693d$be220600$3a661200$@ndzh.com>
In-Reply-To: <018801d5693d$be220600$3a661200$@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: 0e8028fa-312f-4ac5-7cd7-08d73755d107
x-microsoft-antispam: BCL:0; PCL:0; RULEID:(2390118)(7020095)(4652040)(8989299)(4534185)(4627221)(201703031133081)(201702281549075)(8990200)(5600166)(711020)(4605104)(1401327)(2017052603328)(7193020); SRVR:CY4PR11MB2024;
x-ms-traffictypediagnostic: CY4PR11MB2024:
x-ms-exchange-purlcount: 3
x-microsoft-antispam-prvs: <CY4PR11MB20248C5BCFE27B83640CA128C1B00@CY4PR11MB2024.namprd11.prod.outlook.com>
x-ms-oob-tlc-oobclassifiers: OLM:9508;
x-forefront-prvs: 01583E185C
x-forefront-antispam-report: SFV:NSPM; SFS:(10009020)(979002)(4636009)(346002)(366004)(39860400002)(136003)(376002)(396003)(199004)(189003)(53546011)(8676002)(6506007)(86362001)(71200400001)(71190400001)(6246003)(5660300002)(186003)(52536014)(102836004)(54896002)(76116006)(316002)(7736002)(74316002)(33656002)(110136005)(46003)(8936002)(81166006)(81156014)(66946007)(11346002)(229853002)(446003)(486006)(476003)(966005)(55016002)(2501003)(6436002)(66556008)(64756008)(99286004)(790700001)(6116002)(66476007)(236005)(478600001)(6306002)(256004)(14444005)(25786009)(606006)(9686003)(7696005)(14454004)(2906002)(76176011)(53936002)(66446008)(969003)(989001)(999001)(1009001)(1019001); DIR:OUT; SFP:1101; SCL:1; SRVR:CY4PR11MB2024; 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: R5kyVzeYE8hHJmSKgYsxK0KRKVQLSarTrmsHDllHsq4cuZcP1dz/MnqGA5F+ystanIdys67Rs5CCHXc8ZIoZFxgWSAYtBacWywmUS7UOcdsvwK8pelGXivxCF+yGwZAp6RmBS2j/AR+m5PmnWve5sHEzNbQGGQ1ZZGDY4m9V+QdczYpDGim9mF3mVFTvybi0kZ3Etd7ZlShFk1/XvohSb9RlOcAZ0qNg6tEe22WYxk2ZT2iwVaMXGsPP1WcjAtlOkdUdMrZ7CHzGT+FulYJ7/lhznW+WgxZyqEfO2Q0j9OHDJiccj4keFhN+TxglsJBx4wt8+ZIuPy59ASzE2XJ9/iJty9U17FduA57tVO9mLxvQvjJLvREIsnEvI63WvzsXnmJ3L4jaOhI4B9+JtVRIklKyFdUIMBth35x4oUM6ehc=
x-ms-exchange-transport-forked: True
Content-Type: multipart/alternative; boundary="_000_CY4PR11MB1541E2EE5C87942ECB65346DC1B00CY4PR11MB1541namp_"
MIME-Version: 1.0
X-MS-Exchange-CrossTenant-Network-Message-Id: 0e8028fa-312f-4ac5-7cd7-08d73755d107
X-MS-Exchange-CrossTenant-originalarrivaltime: 12 Sep 2019 07:50:01.3621 (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: //DxZNaBwQp0+BzTm8B3PzzN/clTg9+eWznv6EnEe7rB/n64aIJFHrnXSgHEgmneW0zD83nl3+7mv1CHCh1KNw==
X-MS-Exchange-Transport-CrossTenantHeadersStamped: CY4PR11MB2024
X-OriginatorOrg: cisco.com
X-Outbound-SMTP-Client: 173.36.7.25, xch-aln-015.cisco.com
X-Outbound-Node: alln-core-12.cisco.com
Archived-At: <https://mailarchive.ietf.org/arch/msg/idr/jAIrc_TQSTrfMdjvDtKtNf6KxXM>
Subject: Re: [Idr] Need information on planned implementations of draft-ietf-idr-bgp-ls-segment-routing-msd-07
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: Thu, 12 Sep 2019 07:50:08 -0000

Agree Sue and I understand.

I just wanted to pass a handy link at which other implementations may be updated 😊

Thanks,
Ketan

From: Susan Hares <shares@ndzh.com>
Sent: 12 September 2019 13:13
To: Ketan Talaulikar (ketant) <ketant@cisco.com>; idr@ietf.org
Subject: RE: [Idr] Need information on planned implementations of draft-ietf-idr-bgp-ls-segment-routing-msd-07

Ketan:

The information on the two cisco implementations
is accurate and complete.   Thank you for your careful work.
These two implementation reports are sufficient for
IDR requirement for 2 implementations.

This request is asking for anyone who plans an
implementation of this draft but has not implemented the draft.
This request is simply an information gathering request.

This request will not delay the publication request.
The only thing I’m waiting on is the Early QA reviews
(due by 9/14).   If these are positive, then I can request publication.

Please watch for the RTG-DIR and OPS-DIR reviews.
I’m hoping these will be in by 9/14.

Cheers, Sue

From: Ketan Talaulikar (ketant) [mailto:ketant@cisco.com]
Sent: Thursday, September 12, 2019 3:06 AM
To: Susan Hares; idr@ietf.org<mailto:idr@ietf.org>
Subject: RE: [Idr] Need information on planned implementations of draft-ietf-idr-bgp-ls-segment-routing-msd-07

FYI the implementation report is available for updates at https://trac.ietf.org/trac/idr/wiki/draft-ietf-idr-bgp-ls-segment-routing-msd%20implementations

From: Idr <idr-bounces@ietf.org<mailto:idr-bounces@ietf.org>> On Behalf Of Susan Hares
Sent: 12 September 2019 11:44
To: idr@ietf.org<mailto:idr@ietf.org>
Subject: [Idr] Need information on planned implementations of draft-ietf-idr-bgp-ls-segment-routing-msd-07

Greetings:

Would anyone who plans to implement or deploy
draft-ietf-idr-bgp-ls-segment-routing-msd-07.txt
please contact me?

It can be either on-list or off-list?
I just need a general idea of the number planned
implementation status for the
shepherd’s report for this draft.

I’ll send the shepherd report by 9/15/2019.

Cheerily, Susan Hares

v2.23.0 | Report a Bug | By Email