IETF Logo Mail Archive

Re: [Idr] Adoption call for draft-dawra-idr-bgpls-srv6-ext [5/2 - 5/16/2018]

"Les Ginsberg (ginsberg)" <ginsberg@cisco.com> Mon, 06 May 2019 16:58 UTC

Return-Path: <ginsberg@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 4944F120071; Mon, 6 May 2019 09:58:20 -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=X2vj4C53; dkim=pass (1024-bit key) header.d=cisco.onmicrosoft.com header.b=C3+9JesN
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 dnOPs0LpuusX; Mon, 6 May 2019 09:58:18 -0700 (PDT)
Received: from rcdn-iport-4.cisco.com (rcdn-iport-4.cisco.com [173.37.86.75]) (using TLSv1.2 with cipher DHE-RSA-SEED-SHA (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id C62AB120188; Mon, 6 May 2019 09:58:17 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=cisco.com; i=@cisco.com; l=16557; q=dns/txt; s=iport; t=1557161897; x=1558371497; h=from:to:cc:subject:date:message-id:references: in-reply-to:mime-version; bh=IXG/DeQGGOxEedSSum4bepNctcs3QQyuRhu2DPCvfG4=; b=X2vj4C53ifS7VLwZ0RP8oGNzkkgJADc5TjW3GCbsJB37lJiJ0FJyBeu1 ZC8zOO31cvHPqH0Y6FPXeTHnAl4Vpc3knoGRIIGZGJEmYSnszdY3wXD5s IXX3BeoXsGUYx8AAaRkW9j0w3MJsdHVJJ+8RFHZWpuIft4h8Zt52XMKHE E=;
IronPort-PHdr: 9a23:J56+xxGMLuWUmd2kL0PbRJ1GYnJ96bzpIg4Y7IYmgLtSc6Oluo7vJ1Hb+e4z1Q3SRYuO7fVChqKWqK3mVWEaqbe5+HEZON0pNVcejNkO2QkpAcqLE0r+efHraTcwEd5NfFRk5Hq8d0NSHZW2ag==
X-IronPort-Anti-Spam-Filtered: true
X-IronPort-Anti-Spam-Result: A0AIAABLZ9Bc/51dJa1lGgEBAQEBAgEBAQEHAgEBAQGBUQUBAQEBCwGBDi9QA2lVIAQLKIdXA4RSijCCV36WJoEugSQDVA4BASMKhEACghMjNAkOAQMBAQQBAQIBAm0cDIVKAQEBAQMSCxATAQE3AQ8CAQgRBAEBKAcyFAkIAQEEAQ0FCBMHgwGBHU0DHQECDKEGAoE1iF+CIIJ5AQEFgUZBgnYYgg4DBoEyAYtNF4FAP4ERRoIXNT6BBIFdAgMBgV8rCYMGgiaSIZUVCQKCCYYYjEiCDoY/jHuMG4ZMjh0CBAIEBQIOAQEFgU84gVZwFYMngg8REoNMhRSFP3KBKZAWAQE
X-IronPort-AV: E=Sophos;i="5.60,438,1549929600"; d="scan'208,217";a="555591976"
Received: from rcdn-core-6.cisco.com ([173.37.93.157]) by rcdn-iport-4.cisco.com with ESMTP/TLS/DHE-RSA-SEED-SHA; 06 May 2019 16:58:16 +0000
Received: from XCH-ALN-015.cisco.com (xch-aln-015.cisco.com [173.36.7.25]) by rcdn-core-6.cisco.com (8.15.2/8.15.2) with ESMTPS id x46GwGFG011215 (version=TLSv1.2 cipher=AES256-SHA bits=256 verify=FAIL); Mon, 6 May 2019 16:58:16 GMT
Received: from xhs-rtp-001.cisco.com (64.101.210.228) by XCH-ALN-015.cisco.com (173.36.7.25) with Microsoft SMTP Server (TLS) id 15.0.1473.3; Mon, 6 May 2019 11:58:15 -0500
Received: from xhs-rcd-001.cisco.com (173.37.227.246) by xhs-rtp-001.cisco.com (64.101.210.228) with Microsoft SMTP Server (TLS) id 15.0.1473.3; Mon, 6 May 2019 12:58:14 -0400
Received: from NAM05-BY2-obe.outbound.protection.outlook.com (72.163.14.9) by xhs-rcd-001.cisco.com (173.37.227.246) with Microsoft SMTP Server (TLS) id 15.0.1473.3 via Frontend Transport; Mon, 6 May 2019 11:58:14 -0500
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=cisco.onmicrosoft.com; s=selector1-cisco-com; h=From:Date:Subject:Message-ID:Content-Type:MIME-Version:X-MS-Exchange-SenderADCheck; bh=gRdXAxwVTLF9E/Z14bzVCeE9Z2o3QV7FGGybzjini4Y=; b=C3+9JesNxzXH3ksj717wqZQXilyK/DlR8T9fysehNKHagaMngl/Az3ijbsJhlVewAxgaDIA/aLfW4O03S/SHyMrYZlVEA3wWldwPRiwLMihZ9l1I47zMwuXTXW3L44jzxz07cfCGap5jHYg5q3VS1isy/EWGKG4d+K+VddGlYSg=
Received: from BYAPR11MB3638.namprd11.prod.outlook.com (20.178.237.19) by BYAPR11MB3045.namprd11.prod.outlook.com (20.177.225.161) with Microsoft SMTP Server (version=TLS1_2, cipher=TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384) id 15.20.1856.12; Mon, 6 May 2019 16:58:13 +0000
Received: from BYAPR11MB3638.namprd11.prod.outlook.com ([fe80::d801:cf9d:b255:2b07]) by BYAPR11MB3638.namprd11.prod.outlook.com ([fe80::d801:cf9d:b255:2b07%6]) with mapi id 15.20.1856.012; Mon, 6 May 2019 16:58:13 +0000
From: "Les Ginsberg (ginsberg)" <ginsberg@cisco.com>
To: "Ketan Talaulikar (ketant)" <ketant@cisco.com>, Susan Hares <shares@ndzh.com>, "idr@ietf.org" <idr@ietf.org>
CC: "draft-dawra-idr-bgpls-srv6-ext@ietf.org" <draft-dawra-idr-bgpls-srv6-ext@ietf.org>
Thread-Topic: [Idr] Adoption call for draft-dawra-idr-bgpls-srv6-ext [5/2 - 5/16/2018]
Thread-Index: AdUA6N2Rf+SOd1UySuqIw1eSDjH8ZQADTF1QAM2vyyA=
Date: Mon, 06 May 2019 16:58:13 +0000
Message-ID: <BYAPR11MB363848C2C5E2A4B0B9B6ACA7C1300@BYAPR11MB3638.namprd11.prod.outlook.com>
References: <00c901d500e8$de7722e0$9b6568a0$@ndzh.com> <SN6PR11MB28453B5F90F22039CD2F4CAAC1340@SN6PR11MB2845.namprd11.prod.outlook.com>
In-Reply-To: <SN6PR11MB28453B5F90F22039CD2F4CAAC1340@SN6PR11MB2845.namprd11.prod.outlook.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=ginsberg@cisco.com;
x-originating-ip: [2001:420:c0c8:1005::51a]
x-ms-publictraffictype: Email
x-ms-office365-filtering-correlation-id: add04aa4-0afc-4802-1728-08d6d24406d3
x-microsoft-antispam: BCL:0; PCL:0; RULEID:(2390118)(7020095)(4652040)(8989299)(4534185)(4627221)(201703031133081)(201702281549075)(8990200)(5600141)(711020)(4605104)(2017052603328)(7193020); SRVR:BYAPR11MB3045;
x-ms-traffictypediagnostic: BYAPR11MB3045:
x-ms-exchange-purlcount: 3
x-microsoft-antispam-prvs: <BYAPR11MB304569EB2885F14DBDA49E15C1300@BYAPR11MB3045.namprd11.prod.outlook.com>
x-ms-oob-tlc-oobclassifiers: OLM:8882;
x-forefront-prvs: 0029F17A3F
x-forefront-antispam-report: SFV:NSPM; SFS:(10009020)(366004)(376002)(136003)(39860400002)(396003)(346002)(189003)(199004)(5660300002)(6246003)(74316002)(256004)(966005)(186003)(102836004)(110136005)(81156014)(2501003)(7696005)(76176011)(86362001)(446003)(11346002)(6506007)(53546011)(46003)(66946007)(66476007)(6436002)(25786009)(68736007)(236005)(55016002)(81166006)(9686003)(8676002)(6306002)(6116002)(790700001)(14454004)(8936002)(71200400001)(71190400001)(2906002)(54896002)(229853002)(486006)(99286004)(53936002)(4326008)(476003)(52536014)(478600001)(14444005)(66446008)(64756008)(7736002)(33656002)(316002)(606006)(76116006)(73956011)(66556008); DIR:OUT; SFP:1101; SCL:1; SRVR:BYAPR11MB3045; H:BYAPR11MB3638.namprd11.prod.outlook.com; FPR:; SPF:None; LANG:en; PTR:InfoNoRecords; MX:1; A: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: Ub0YkLLIlj7wW5oF6Md2YUWcvGh135dRXp2xs7qp8OXtt6KzH7XC9eVsNuXdrvgObZhI2JeXpD7c7+LrH759g6JkjpdkhrEJKl0bwg23E28i6hTv3ZckssPVI7z2ZWlmPBK1aIyDRvRAK5+eSW6Jkn4KnXTuIwHZvbxQQgjpM0p22d2ihAnzeI/iOeccH1ByMbimoLLfGp10Ey1ofhvgJLUwa9B7BbBkLFqy4Z3slIzv1r/043iBpaOU7TnxLJJ9Ex25r5cvPLGdId4/EFvjo1d1/CbGPjKy6DiMzkjlVe9/r5V/ZIP7nYc3k8CbeerbHRETnMgCtm48pEoqQ/hBGp57QHVUSTy38w/4VRocQqpk6AYtd9ny3fi277nYAMadboO7aqz2E+2+azrwOfnXwTvCYDcRoyFfd6yHPsuKcRU=
Content-Type: multipart/alternative; boundary="_000_BYAPR11MB363848C2C5E2A4B0B9B6ACA7C1300BYAPR11MB3638namp_"
MIME-Version: 1.0
X-MS-Exchange-CrossTenant-Network-Message-Id: add04aa4-0afc-4802-1728-08d6d24406d3
X-MS-Exchange-CrossTenant-originalarrivaltime: 06 May 2019 16:58:13.2449 (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-Transport-CrossTenantHeadersStamped: BYAPR11MB3045
X-OriginatorOrg: cisco.com
X-Outbound-SMTP-Client: 173.36.7.25, xch-aln-015.cisco.com
X-Outbound-Node: rcdn-core-6.cisco.com
Archived-At: <https://mailarchive.ietf.org/arch/msg/idr/BEeXPfsWXBqoBd8Xs1cTZXlEUVg>
Subject: Re: [Idr] Adoption call for draft-dawra-idr-bgpls-srv6-ext [5/2 - 5/16/2018]
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: Mon, 06 May 2019 16:58:20 -0000

I support WG adoption of the draft - and agree with all the points Ketan has made below.

   Les


From: Idr <idr-bounces@ietf.org> On Behalf Of Ketan Talaulikar (ketant)
Sent: Thursday, May 02, 2019 7:57 AM
To: Susan Hares <shares@ndzh.com>; idr@ietf.org
Cc: draft-dawra-idr-bgpls-srv6-ext@ietf.org
Subject: Re: [Idr] Adoption call for draft-dawra-idr-bgpls-srv6-ext [5/2 - 5/16/2018]

Hi Sue/All,

Support as co-author.


1)      Does this draft needed support for the SRV6?
Yes. This enables the reporting of SRv6 information from multi-domain IGP topologies via BGP-LS to centralized applications/consumers that can leverage this information for use-cases like TE.

2)      Is this draft a good starting point for the BGP support for SRv6?
It is actually for BGP-LS support for SRv6. There is a separate draft-dawra-bess-srv6-services which was presented in BESS that covers the BGP services (Global, VPN, EVPN).

3)      Do you know of any technical issues regarding this draft?

If so, do these technical issues present any major problems to the technical solution?
No.


4)      Do you know of any existing implementations or any plans for implementation?
Yes. We have implementation and deployment plans. Would like to request early allocation of code-points post adoption.

Thanks,
Ketan

From: Susan Hares <shares@ndzh.com<mailto:shares@ndzh.com>>
Sent: 02 May 2019 18:44
To: idr@ietf.org<mailto:idr@ietf.org>
Cc: draft-dawra-idr-bgpls-srv6-ext@ietf.org<mailto:draft-dawra-idr-bgpls-srv6-ext@ietf.org>
Subject: Adoption call for draft-dawra-idr-bgpls-srv6-ext [5/2 - 5/16/2018]

This begins a 2 week WG Adoption call for draft-dawra-idr-bgpls-srv6

https://datatracker.ietf.org/doc/draft-dawra-idr-bgpls-srv6-ext/

Please consider the following questions in commenting on the

1)      Does this draft needed support for the SRV6?
2)      Is this draft a good starting point for the BGP support for SRv6?
3)      Do you know of any technical issues regarding this draft?

If so, do these technical issues present any major problems to the technical solution?


4)      Do you know of any existing implementations or any plans for implementation?

One special note, if you mentioning technical issues regarding a draft it can be helpful to the WG.  Our goal is to provide good BGP support of the Spring BGP-LS work in a timely fashion.  The SRv6 support is key to the Spring effort - so it would be helpful to mention and get resolved any issues with this draft.

Cheerily, Sue Hares

v2.28.0 | Report a Bug | By Email | System Status