Re: [Idr] draft-ietf-idr-bgpls-srv6-ext - 2 week Early Allocation Call [6/2 - 6/16/2019]

"Acee Lindem (acee)" <acee@cisco.com> Mon, 03 June 2019 11:42 UTC

Return-Path: <acee@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 E462B1200C1; Mon, 3 Jun 2019 04:42:21 -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=XgLqjMYb; dkim=pass (1024-bit key) header.d=cisco.onmicrosoft.com header.b=ibwUHFIx
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 xH1q8oAduoeH; Mon, 3 Jun 2019 04:42:19 -0700 (PDT)
Received: from alln-iport-3.cisco.com (alln-iport-3.cisco.com [173.37.142.90]) (using TLSv1.2 with cipher DHE-RSA-SEED-SHA (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 19CF8120203; Mon, 3 Jun 2019 04:42:19 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=cisco.com; i=@cisco.com; l=27765; q=dns/txt; s=iport; t=1559562139; x=1560771739; h=from:to:cc:subject:date:message-id:mime-version; bh=evGsdnKmYWYlnM8HDywexEL+xrf92BKo9D+oIfBr5m4=; b=XgLqjMYbhv8c0DWBg/NHLIoqGn+8EkHFvzGEuExOS/GgHsdbjBzg+luQ +XXeXIKGH3h5UKcaRIms7Oa+sOXeA8YMnKhK0FA9VaoWjLtkmETtxBWU3 YHaOf2YwLfsB69t8OxE0Zt3tbREM8EWUDxt+u1jQrXzT68bqqYR1LWFQo Y=;
IronPort-PHdr: =?us-ascii?q?9a23=3Askr6XhbNwJ4GDFSDOCYdIHb/LSx94ef9IxIV55?= =?us-ascii?q?w7irlHbqWk+dH4MVfC4el20QKbRp3VvvRDjeee87vtX2AN+96giDgDa9QNHw?= =?us-ascii?q?QAld1QmgUhBMCfDkiuJfXnYgQxHd9JUxlu+HToeUU=3D?=
X-IronPort-Anti-Spam-Filtered: true
X-IronPort-Anti-Spam-Result: =?us-ascii?q?A0A1AAAJB/Vc/5BdJa1mGwEBAQEDAQE?= =?us-ascii?q?BBwMBAQGBUwQBAQELAYEOLyQsA2pVIAQLKAqECoNHA45ygld+ljGBLhSBEAN?= =?us-ascii?q?UCQEBAQwBASMKAgEBhEAZgngjNgcOAQMBAQQBAQIBBG0cDIVKAQEBAQMSCwY?= =?us-ascii?q?dAQE3AREBCBEDAQEBIQoCBDAdCgQBDQUbB4MAAYEdTQMdAQIMnh0CgTiIX3G?= =?us-ascii?q?BMYJ5AQEFgTYCDkGCcxiCDwMGgTQBi1kXgX+BEAEnH4IXNT6BBIFdAQECAQG?= =?us-ascii?q?BKgESAT8GB4JdMoImi1GCSYRolXsJAoINhj+McxuCIoZxjVuEBIh8hwuPEwI?= =?us-ascii?q?EAgQFAg4BAQWBVgIvZ3FwFTsqAYJBgg8MDAsUgzmFFIU/coEpjWmBIgGBIAE?= =?us-ascii?q?B?=
X-IronPort-AV: E=Sophos;i="5.60,546,1549929600"; d="scan'208,217";a="285798296"
Received: from rcdn-core-8.cisco.com ([173.37.93.144]) by alln-iport-3.cisco.com with ESMTP/TLS/DHE-RSA-SEED-SHA; 03 Jun 2019 11:42:17 +0000
Received: from XCH-RCD-007.cisco.com (xch-rcd-007.cisco.com [173.37.102.17]) by rcdn-core-8.cisco.com (8.15.2/8.15.2) with ESMTPS id x53BgHmT023731 (version=TLSv1.2 cipher=AES256-SHA bits=256 verify=FAIL); Mon, 3 Jun 2019 11:42:17 GMT
Received: from xhs-rcd-003.cisco.com (173.37.227.248) by XCH-RCD-007.cisco.com (173.37.102.17) with Microsoft SMTP Server (TLS) id 15.0.1473.3; Mon, 3 Jun 2019 06:42:17 -0500
Received: from xhs-aln-001.cisco.com (173.37.135.118) by xhs-rcd-003.cisco.com (173.37.227.248) with Microsoft SMTP Server (TLS) id 15.0.1473.3; Mon, 3 Jun 2019 06:42:16 -0500
Received: from NAM01-BN3-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; Mon, 3 Jun 2019 06:42:16 -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=evGsdnKmYWYlnM8HDywexEL+xrf92BKo9D+oIfBr5m4=; b=ibwUHFIxFxaGYJy9x4QJXVWwsVh/dRkLrnTFeFf27mrbZKYdi4Pc1jhcFAjiQ4m5RS31hRHb9+4lzyu1se2Ycfzq8RXZnK8AS8rKz2yfUI1IpsclFW+2owHQLQbv7VXlZQ+1k6P3qfGoKwReR4uvGBfJGKWah63B+rJmlXAyiBw=
Received: from SN6PR11MB2845.namprd11.prod.outlook.com (52.135.93.24) by SN6PR11MB2912.namprd11.prod.outlook.com (52.135.123.214) with Microsoft SMTP Server (version=TLS1_2, cipher=TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384) id 15.20.1943.18; Mon, 3 Jun 2019 11:42:14 +0000
Received: from SN6PR11MB2845.namprd11.prod.outlook.com ([fe80::3006:a080:19fa:623e]) by SN6PR11MB2845.namprd11.prod.outlook.com ([fe80::3006:a080:19fa:623e%6]) with mapi id 15.20.1943.018; Mon, 3 Jun 2019 11:42:14 +0000
From: "Acee Lindem (acee)" <acee@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] draft-ietf-idr-bgpls-srv6-ext - 2 week Early Allocation Call [6/2 - 6/16/2019]
Thread-Index: AQHVGgFjcbGerNt/9UydJHk80eOoUA==
Date: Mon, 3 Jun 2019 11:42:14 +0000
Message-ID: <B847CCCB-34DD-42E2-83B1-83B4AECDF1F6@cisco.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=acee@cisco.com;
x-originating-ip: [173.38.117.70]
x-ms-publictraffictype: Email
x-ms-office365-filtering-correlation-id: 90281a44-f398-46fc-541a-08d6e8188637
x-microsoft-antispam: BCL:0; PCL:0; RULEID:(2390118)(7020095)(4652040)(8989299)(4534185)(4627221)(201703031133081)(201702281549075)(8990200)(5600148)(711020)(4605104)(1401327)(2017052603328)(7193020); SRVR:SN6PR11MB2912;
x-ms-traffictypediagnostic: SN6PR11MB2912:
x-ms-exchange-purlcount: 3
x-microsoft-antispam-prvs: <SN6PR11MB2912F659ABF54B00A82C4786C2140@SN6PR11MB2912.namprd11.prod.outlook.com>
x-ms-oob-tlc-oobclassifiers: OLM:10000;
x-forefront-prvs: 0057EE387C
x-forefront-antispam-report: SFV:NSPM; SFS:(10009020)(136003)(346002)(376002)(39860400002)(396003)(366004)(189003)(199004)(3846002)(6116002)(102836004)(53546011)(6506007)(66066001)(6246003)(71200400001)(8676002)(36756003)(71190400001)(110136005)(54896002)(476003)(2616005)(6306002)(82746002)(53936002)(6512007)(236005)(486006)(6436002)(26005)(966005)(478600001)(64756008)(66446008)(606006)(68736007)(8936002)(81166006)(83716004)(4326008)(76116006)(2501003)(316002)(86362001)(91956017)(81156014)(6486002)(25786009)(229853002)(5660300002)(33656002)(99286004)(2906002)(256004)(66476007)(14454004)(7736002)(66946007)(66556008)(73956011)(186003); DIR:OUT; SFP:1101; SCL:1; SRVR:SN6PR11MB2912; H:SN6PR11MB2845.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: pVLKybq3rm6Gw8yPGHvCZmXKMlMo4YEpJebVndIsmMgQc5PIVRggmXgavgGoT2ZKOQFyStQiR4eqSl9A9a+6LChiCwUAcTKetRMJwCHQ8dqAkvTX+tco4F50bNv9MrZzrYn9k5fNdQe2wvs7M9ThkmdE3TFzyd1bAhg2bHw4E/3mcl1TrwqScowIBEW5bdn2YbGrHakmlPJSbkxW5hRAsLYvG4TQG8CQWBrtMvWJEzlk0+FfT5oKkzowyuWIGridkuTTV3n1L9poPOLJmJRc7khEaS3+fNyNNUufOuwAQeOOFbTyzzHkPrNnMMEy8okazu0o46E3KQt58nVYT4dDbpJPyp0FH4ojDRgYtDdG4Q2dHCSOLQWnPwKqCKWwDF/M3JdNJkCXV6AEuu5fipZuiV0lLrYIfHbyowMdANUL0ME=
Content-Type: multipart/alternative; boundary="_000_B847CCCB34DD42E283B183B4AECDF1F6ciscocom_"
MIME-Version: 1.0
X-MS-Exchange-CrossTenant-Network-Message-Id: 90281a44-f398-46fc-541a-08d6e8188637
X-MS-Exchange-CrossTenant-originalarrivaltime: 03 Jun 2019 11:42:14.6376 (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: acee@cisco.com
X-MS-Exchange-Transport-CrossTenantHeadersStamped: SN6PR11MB2912
X-OriginatorOrg: cisco.com
X-Outbound-SMTP-Client: 173.37.102.17, xch-rcd-007.cisco.com
X-Outbound-Node: rcdn-core-8.cisco.com
Archived-At: <https://mailarchive.ietf.org/arch/msg/idr/tFdIRXuBHw74oA3yTvdlrAK0lBE>
Subject: Re: [Idr] draft-ietf-idr-bgpls-srv6-ext - 2 week Early Allocation Call [6/2 - 6/16/2019]
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, 03 Jun 2019 11:42:22 -0000

I support as well. However, I wondering why the IDR WG goes through the formality of additional code point allocation call given that the document is already a WG document and has gone through an adoption call. It would seem very strange to me to accept a document as a WG document and yet deny early code point allocation.
Thanks,
Acee

From: Idr <idr-bounces@ietf.org> on behalf of "Ketan Talaulikar (ketant)" <ketant@cisco.com>
Date: Monday, June 3, 2019 at 2:05 AM
To: Susan Hares <shares@ndzh.com>, IDR List <idr@ietf.org>
Cc: "draft-dawra-idr-bgpls-srv6-ext@ietf.org" <draft-dawra-idr-bgpls-srv6-ext@ietf.org>
Subject: Re: [Idr] draft-ietf-idr-bgpls-srv6-ext - 2 week Early Allocation Call [6/2 - 6/16/2019]

Hi Sue/All,

Support as a co-author to enable implementation of this draft to support SRv6 use-cases.

Thanks,
Ketan

From: Susan Hares <shares@ndzh.com>
Sent: 03 June 2019 07:57
To: Ketan Talaulikar (ketant) <ketant@cisco.com>; idr@ietf.org
Cc: draft-dawra-idr-bgpls-srv6-ext@ietf.org
Subject: draft-ietf-idr-bgpls-srv6-ext - 2 week Early Allocation Call [6/2 - 6/16/2019]

This begins a 2 week Early Allocation call for parameters from:


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

The authors are requesting for early code point allocation from
IANA to enable implementations with suggested code points as indicated below.

The criteria for early allocation includes:  stable working group document,
clear technical solution and implementation interest.   The IDR chairs
believe this document meets these criteria. Please let us know if you
think this draft meets these criteria.

If you support early adoption,  please include “support” in your along
with any comments about the draft’s technical solution.  Since the
authors are heading into testing implementations, any comments about
error or improvements will be helpful to the authors.

If you do not support early allocation, please include
include “no support in your email” and indicate why.

Cheerily, Sue Hares

----------------------

   The following codepoints is suggested (to be assigned by IANA) from
   within the sub-registry called "BGP-LS NLRI-Types":

    +------+----------------------------+---------------+
    | Type | NLRI Type                  |   Reference   |
    +------+----------------------------+---------------+
    |  6   | SRv6 SID                   | this document |
    +------+----------------------------+---------------+

   The following TLV codepoints are suggested (to be assigned by IANA)
   from within the sub-registry called "BGP-LS Node Descriptor, Link
   Descriptor, Prefix Descriptor, and Attribute TLVs":

   +----------+----------------------------------------+---------------+
   | TLV Code |             Description                | Value defined |
   |  Point   |                                        |       in      |
   +----------+----------------------------------------+---------------+
   |  1038    |   SRv6 Capabilities TLV                | this document |
   |  1106    |   SRv6 End.X SID TLV                   | this document |
   |  1107    |   IS-IS SRv6 LAN End.X SID TLV         | this document |
  |  1108    |   OSPFv3 SRv6 LAN End.X SID TLV        | this document |
   |  1162    |   SRv6 Locator TLV                     | this document |
   |   518    |   SRv6 SID Information TLV             | this document |
   |  1250    |   SRv6 Endpoint Function TLV           | this document |
   |  1251    |   SRv6 BGP Peer Node SID TLV           | this document |
   +----------+----------------------------------------+---------------+