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

"Ketan Talaulikar (ketant)" <ketant@cisco.com> Thu, 02 May 2019 14:57 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 31017120406; Thu, 2 May 2019 07:57:38 -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=AHlTj1hd; dkim=pass (1024-bit key) header.d=cisco.onmicrosoft.com header.b=e32Cf8Xa
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 1VwrgNPdWxWo; Thu, 2 May 2019 07:57:36 -0700 (PDT)
Received: from rcdn-iport-2.cisco.com (rcdn-iport-2.cisco.com [173.37.86.73]) (using TLSv1.2 with cipher DHE-RSA-SEED-SHA (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 1722412038A; Thu, 2 May 2019 07:57:28 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=cisco.com; i=@cisco.com; l=13665; q=dns/txt; s=iport; t=1556809049; x=1558018649; h=from:to:cc:subject:date:message-id:references: in-reply-to:mime-version; bh=ktJHC7QeCCz+noRxQUHriDDOS8bdmM+qZFNuVfVMlfM=; b=AHlTj1hdLZvDsk5HmH8QomZFmReJvTMGmBaZk4Hceylnnq1p0rx48DKB 0pUnIjQynjXlohv+sv+6ntq3v1ZoVBifT5NRUAZC2OxUoyuN05wOx3diV xAVHzIjkR1/+j+uDy/D3SoMA/ZJ3ihOZwpVE2nJXg+IJVgd0hAeVuojjM s=;
IronPort-PHdr: =?us-ascii?q?9a23=3AzFV3pBBLixcs61yIipglUyQJPHJ1sqjoPgMT9p?= =?us-ascii?q?ssgq5PdaLm5Zn5IUjD/qg83kTRU9Dd7PRJw6rNvqbsVHZIwK7JsWtKMfkuHw?= =?us-ascii?q?QAld1QmgUhBMCfDkiuL/P2ZiomNM9DT1RiuXq8NBsdFQ=3D=3D?=
X-IronPort-Anti-Spam-Filtered: true
X-IronPort-Anti-Spam-Result: =?us-ascii?q?A0AIAAD4BMtc/4MNJK1lGgEBAQEBAgE?= =?us-ascii?q?BAQEHAgEBAQGBUQUBAQEBCwGBDi9QA2lVIAQLKIdXA4RSijCCV36RWIRMgS6?= =?us-ascii?q?BJANUDgEBIwqEQAKGMyM0CQ4BAwEBBAEBAgECbRwMhUoBAQEEEgsQEwEBNwE?= =?us-ascii?q?PAgEIDgMEAQEvMh0IAQEEAQ0FCBMHgwGBHU0DHQECDKJoAoE1iF+CIIJ5AQE?= =?us-ascii?q?FgUZBgngYgg4DBoEyAYtLF4FAP4ERRoIXNT6BBIFdAgMBgV8rgw+CJpIYlRA?= =?us-ascii?q?JAoIJhhiMQ4IOhjyMd4wWhkuOGAIEAgQFAg4BAQWBTziBVnAVgyeCDxESg0y?= =?us-ascii?q?FFIU/coEpkzQBAQ?=
X-IronPort-AV: E=Sophos;i="5.60,422,1549929600"; d="scan'208,217";a="557410854"
Received: from alln-core-1.cisco.com ([173.36.13.131]) by rcdn-iport-2.cisco.com with ESMTP/TLS/DHE-RSA-SEED-SHA; 02 May 2019 14:57:27 +0000
Received: from XCH-RCD-008.cisco.com (xch-rcd-008.cisco.com [173.37.102.18]) by alln-core-1.cisco.com (8.15.2/8.15.2) with ESMTPS id x42EvRvP001643 (version=TLSv1.2 cipher=AES256-SHA bits=256 verify=FAIL); Thu, 2 May 2019 14:57:27 GMT
Received: from xhs-rcd-001.cisco.com (173.37.227.246) by XCH-RCD-008.cisco.com (173.37.102.18) with Microsoft SMTP Server (TLS) id 15.0.1473.3; Thu, 2 May 2019 09:57:27 -0500
Received: from xhs-aln-001.cisco.com (173.37.135.118) by xhs-rcd-001.cisco.com (173.37.227.246) with Microsoft SMTP Server (TLS) id 15.0.1473.3; Thu, 2 May 2019 09:57:26 -0500
Received: from NAM04-SN1-obe.outbound.protection.outlook.com (173.37.151.57) by xhs-aln-001.cisco.com (173.37.135.118) with Microsoft SMTP Server (TLS) id 15.0.1473.3 via Frontend Transport; Thu, 2 May 2019 09:57:26 -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=4ymJwiU6A98WMeqkbOy3NJREgdtdHBeGc1ks16PY5Iw=; b=e32Cf8Xaf9q7rbJd72tLYUuesqJ66JH8r5lms6Bi7lIcRmW9hq0KVQDQrVLRkO4XZZDAyQdcoH0McWP+aGovNoWAaHx5S4guZ1X8SfhT7Vs2DyygbDH7QPFZDFnCQyQvw5UEN8wO4riI2e+if3DTFM5TZcVWWGDX0WdS4o61UVI=
Received: from SN6PR11MB2845.namprd11.prod.outlook.com (52.135.93.24) by SN6PR11MB2607.namprd11.prod.outlook.com (52.135.91.28) with Microsoft SMTP Server (version=TLS1_2, cipher=TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384) id 15.20.1856.11; Thu, 2 May 2019 14:57:24 +0000
Received: from SN6PR11MB2845.namprd11.prod.outlook.com ([fe80::5c42:5f15:d194:98f]) by SN6PR11MB2845.namprd11.prod.outlook.com ([fe80::5c42:5f15:d194:98f%5]) with mapi id 15.20.1835.018; Thu, 2 May 2019 14:57:24 +0000
From: "Ketan Talaulikar (ketant)" <ketant@cisco.com>
To: 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: Adoption call for draft-dawra-idr-bgpls-srv6-ext [5/2 - 5/16/2018]
Thread-Index: AdUA6N2Rf+SOd1UySuqIw1eSDjH8ZQADTF1Q
Date: Thu, 2 May 2019 14:57:24 +0000
Message-ID: <SN6PR11MB28453B5F90F22039CD2F4CAAC1340@SN6PR11MB2845.namprd11.prod.outlook.com>
References: <00c901d500e8$de7722e0$9b6568a0$@ndzh.com>
In-Reply-To: <00c901d500e8$de7722e0$9b6568a0$@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:1002::364]
x-ms-publictraffictype: Email
x-ms-office365-filtering-correlation-id: b8fd43f5-f90a-4759-8def-08d6cf0e7ca7
x-microsoft-antispam: BCL:0; PCL:0; RULEID:(2390118)(7020095)(4652040)(8989299)(4534185)(4627221)(201703031133081)(201702281549075)(8990200)(5600141)(711020)(4605104)(2017052603328)(7193020); SRVR:SN6PR11MB2607;
x-ms-traffictypediagnostic: SN6PR11MB2607:
x-ms-exchange-purlcount: 3
x-microsoft-antispam-prvs: <SN6PR11MB260790EEDF7E2506C388B59CC1340@SN6PR11MB2607.namprd11.prod.outlook.com>
x-ms-oob-tlc-oobclassifiers: OLM:10000;
x-forefront-prvs: 0025434D2D
x-forefront-antispam-report: SFV:NSPM; SFS:(10009020)(136003)(39860400002)(366004)(346002)(396003)(376002)(199004)(189003)(256004)(73956011)(53546011)(66946007)(66446008)(4326008)(6506007)(66556008)(66476007)(64756008)(8936002)(486006)(102836004)(8676002)(76176011)(55016002)(6306002)(54896002)(53936002)(76116006)(14444005)(81156014)(86362001)(186003)(9686003)(236005)(6246003)(81166006)(2906002)(25786009)(99286004)(68736007)(7696005)(790700001)(6116002)(52536014)(606006)(33656002)(71200400001)(71190400001)(6436002)(14454004)(5660300002)(478600001)(446003)(966005)(2501003)(11346002)(110136005)(7736002)(476003)(74316002)(229853002)(46003)(316002)(4743002); DIR:OUT; SFP:1101; SCL:1; SRVR:SN6PR11MB2607; H:SN6PR11MB2845.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: KwMdelKomh3j7lwUswbzsvHLnKDhZffpMRkFffg6KkXMfw0lWR9WUdPB3UrglZZ08PQH13QoEIkFpbZyaK92p1PIqoXbIRPILaNIfeD2XdEpUQM+HcbTJBm6yM/w2ZnHBAOXqvpFnNW0dwL5NpODa0NMJoyAT1JArWvdeS1IVHLS6frQz9A4FMdq7cjL1AG5diExYQmnviqDUnNvmHC//hNgYZjDwaFhZfAIERw0Gm4ZE3fRdbj3WXIZbUJX4jqWj4mUa47RQaA1b4Kwi4pWTFKfoXgbzVNYqWR20oMe/WZebtThPIJjgsny+8q5n8uX2g/KRmTkWrQfcuHh+3j67ONDrfQ+SAPV9sOvY91OPJ9lRCKo8fGLaa4T/ybYcxVnlhiunlV0mYkn1/tb1qAPGRy9xKjoiacf6uAxg0+esP0=
Content-Type: multipart/alternative; boundary="_000_SN6PR11MB28453B5F90F22039CD2F4CAAC1340SN6PR11MB2845namp_"
MIME-Version: 1.0
X-MS-Exchange-CrossTenant-Network-Message-Id: b8fd43f5-f90a-4759-8def-08d6cf0e7ca7
X-MS-Exchange-CrossTenant-originalarrivaltime: 02 May 2019 14:57:24.5850 (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: SN6PR11MB2607
X-OriginatorOrg: cisco.com
X-Outbound-SMTP-Client: 173.37.102.18, xch-rcd-008.cisco.com
X-Outbound-Node: alln-core-1.cisco.com
Archived-At: <https://mailarchive.ietf.org/arch/msg/idr/YJ4-QIyws_Kdlzti0Qh-tFgVKVo>
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: Thu, 02 May 2019 14:57:44 -0000

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.


  1.  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).


  1.  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.



  1.  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>
Sent: 02 May 2019 18:44
To: idr@ietf.org
Cc: 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?



  1.  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