Re: [Idr] Early Code Point Allocation for draft-ietf-idr-segment-routing-te-policy [4/30 to 5/14/2019]
"Kausik Majumdar (kmajumda)" <kmajumda@cisco.com> Tue, 30 April 2019 16:27 UTC
Return-Path: <kmajumda@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 5A9771202DF; Tue, 30 Apr 2019 09:27:13 -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=CbEOyAzi; dkim=pass (1024-bit key) header.d=cisco.onmicrosoft.com header.b=eK6wsaqw
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 XQzk_3KWWkT6; Tue, 30 Apr 2019 09:27:11 -0700 (PDT)
Received: from alln-iport-5.cisco.com (alln-iport-5.cisco.com [173.37.142.92]) (using TLSv1.2 with cipher DHE-RSA-SEED-SHA (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id AF0A112008D; Tue, 30 Apr 2019 09:27:10 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=cisco.com; i=@cisco.com; l=10161; q=dns/txt; s=iport; t=1556641630; x=1557851230; h=from:to:cc:subject:date:message-id:references: in-reply-to:mime-version; bh=pBn1uqlLYsDdD6ydAk8iHwDLTexduKIC8rR69Mb5Sp8=; b=CbEOyAzi4FNPLMC4fPLsGFahdJ4kr6lDiGkZRSB0YxBNN7RMtTzwLAPl Z5uApQ6e54qFL31SHo0zryzNN4RLNw+j58FdmyVAEDr8wyn40Ej9c5X7B Jt/LJqt+VIXGPJ3/Mw+9SqcDXtxkC29Jg85Ap1mvnTEBeL4pDZMe00I30 4=;
IronPort-PHdr: 9a23:RHprDxyDs4O5H9PXCy+N+z0EezQntrPoPwUc9psgjfdUf7+++4j5YhWN/u1j2VnOW4iTq+lJjebbqejBYSQB+t7A1RJKa5lQT1kAgMQSkRYnBZuGDET5MfvmZgQxHd9JUxlu+HToeUU=
X-IronPort-Anti-Spam-Filtered: true
X-IronPort-Anti-Spam-Result: A0AGAAA4dshc/51dJa1mGQEBAQEBAQEBAQEBAQcBAQEBAQGBUQQBAQEBAQsBgQ4vKScDaVUgBAsohW+BaAOEUoo9gld+kViETIEuFIEQA1QOAQElCIMJgTcChjEjNAkOAQMBAQQBAQIBAm0cDIVKAQEBBBILEBMBATcBDwIBCBEEAQEkBAcyFAkIAQEEAQ0FCBqDAYEdTQMdAQIMo2wCgTWIX4IggnkBAQWBRkGCfhiCDgMGgTIBi0kXgUA/gRFGghcHLj6BBIFdAgMBgSoBEgEhKwmDBoImkggglGAJAoIJhhWELYgTgg2GN4xrjA6GQ44OAgQCBAUCDgEBBYFPODUwcXAVO4JsgWskN20BB4JDhRSFP3KBKZBLgkMBAQ
X-IronPort-AV: E=Sophos;i="5.60,414,1549929600"; d="scan'208,217";a="266808842"
Received: from rcdn-core-6.cisco.com ([173.37.93.157]) by alln-iport-5.cisco.com with ESMTP/TLS/DHE-RSA-SEED-SHA; 30 Apr 2019 16:27:09 +0000
Received: from XCH-RCD-007.cisco.com (xch-rcd-007.cisco.com [173.37.102.17]) by rcdn-core-6.cisco.com (8.15.2/8.15.2) with ESMTPS id x3UGR92E009574 (version=TLSv1.2 cipher=AES256-SHA bits=256 verify=FAIL); Tue, 30 Apr 2019 16:27:09 GMT
Received: from xhs-rtp-001.cisco.com (64.101.210.228) by XCH-RCD-007.cisco.com (173.37.102.17) with Microsoft SMTP Server (TLS) id 15.0.1473.3; Tue, 30 Apr 2019 11:27:08 -0500
Received: from xhs-rcd-003.cisco.com (173.37.227.248) by xhs-rtp-001.cisco.com (64.101.210.228) with Microsoft SMTP Server (TLS) id 15.0.1473.3; Tue, 30 Apr 2019 12:27:07 -0400
Received: from NAM01-SN1-obe.outbound.protection.outlook.com (72.163.14.9) by xhs-rcd-003.cisco.com (173.37.227.248) with Microsoft SMTP Server (TLS) id 15.0.1473.3 via Frontend Transport; Tue, 30 Apr 2019 11:27:07 -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=G8hVkREBRAD2zWzgm2Oyt2X+LS3NVBjmbJgdf04VXxo=; b=eK6wsaqwgjDzYtKZ0AKg5Q0i/BtynYYYE8KHhEQo3yJ72u87OZVfsNmtHitEuNBb0rMWYgcat6qol2ZceHyH0M0dNXR4MukMw89UWko8RdUIu4OzoKccW0xorp0KtAFsWKl41bL8IOqwlxygCwyWtHfs9Uc6Eqo7yztSvZd9Iqw=
Received: from BYAPR11MB3544.namprd11.prod.outlook.com (20.178.206.17) by BYAPR11MB2870.namprd11.prod.outlook.com (52.135.228.144) with Microsoft SMTP Server (version=TLS1_2, cipher=TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384) id 15.20.1835.15; Tue, 30 Apr 2019 16:27:02 +0000
Received: from BYAPR11MB3544.namprd11.prod.outlook.com ([fe80::842e:6b7:baa6:1047]) by BYAPR11MB3544.namprd11.prod.outlook.com ([fe80::842e:6b7:baa6:1047%3]) with mapi id 15.20.1835.015; Tue, 30 Apr 2019 16:27:02 +0000
From: "Kausik Majumdar (kmajumda)" <kmajumda@cisco.com>
To: "Ketan Talaulikar (ketant)" <ketant@cisco.com>, Susan Hares <shares@ndzh.com>, "idr@ietf.org" <idr@ietf.org>
CC: "draft-ietf-idr-segment-routing-te-policy@ietf.org" <draft-ietf-idr-segment-routing-te-policy@ietf.org>, Przemyslaw Krol <pkrol@google.com>
Thread-Topic: [Idr] Early Code Point Allocation for draft-ietf-idr-segment-routing-te-policy [4/30 to 5/14/2019]
Thread-Index: AdT/U+X6vdEwlS9uQBGKy//tUsGZZgACW/bgAATA/FA=
Date: Tue, 30 Apr 2019 16:27:02 +0000
Message-ID: <BYAPR11MB3544B2488D14307537E09774D03A0@BYAPR11MB3544.namprd11.prod.outlook.com>
References: <001b01d4ff54$31784b90$9468e2b0$@ndzh.com> <SN6PR11MB2845D4E5433A9C30C04D6592C13A0@SN6PR11MB2845.namprd11.prod.outlook.com>
In-Reply-To: <SN6PR11MB2845D4E5433A9C30C04D6592C13A0@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=kmajumda@cisco.com;
x-originating-ip: [2001:420:c0c8:1003::65e]
x-ms-publictraffictype: Email
x-ms-office365-filtering-correlation-id: 8a282291-35f3-4c65-547a-08d6cd88ad49
x-microsoft-antispam: BCL:0; PCL:0; RULEID:(2390118)(7020095)(4652040)(8989299)(4534185)(4627221)(201703031133081)(201702281549075)(8990200)(5600141)(711020)(4605104)(2017052603328)(7193020); SRVR:BYAPR11MB2870;
x-ms-traffictypediagnostic: BYAPR11MB2870:
x-ms-exchange-purlcount: 3
x-microsoft-antispam-prvs: <BYAPR11MB2870670C813249F5C9BF6202D03A0@BYAPR11MB2870.namprd11.prod.outlook.com>
x-ms-oob-tlc-oobclassifiers: OLM:8273;
x-forefront-prvs: 00235A1EEF
x-forefront-antispam-report: SFV:NSPM; SFS:(10009020)(376002)(396003)(39860400002)(366004)(136003)(346002)(199004)(189003)(486006)(6436002)(86362001)(2501003)(478600001)(81156014)(99286004)(476003)(186003)(52536014)(14444005)(25786009)(256004)(11346002)(4326008)(966005)(102836004)(14454004)(8936002)(110136005)(6246003)(53936002)(54906003)(446003)(6506007)(53546011)(229853002)(606006)(55016002)(6306002)(236005)(54896002)(9686003)(81166006)(76176011)(66476007)(66556008)(790700001)(7696005)(64756008)(66446008)(46003)(6116002)(33656002)(2906002)(66946007)(73956011)(76116006)(68736007)(97736004)(7736002)(316002)(8676002)(74316002)(71190400001)(71200400001)(5660300002); DIR:OUT; SFP:1101; SCL:1; SRVR:BYAPR11MB2870; H:BYAPR11MB3544.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: ysPGbWOBKa/gPLdZbA65ZeBwBvY8UvGMnvT6zTSpsHKc0afNTYGrQlaBYVRG9DUcmIAjWXU/B9aJQh8dvL/swhiZ5V13lt04MHynaJyVPyo7Hrm8bt1XzoSjYahk/i3MgCZycDHpoqi47dHlfqsY6lDdB46X4L91P0NlmmwVLeWcUeaiIfNwoKVuLceYNqTe3ud/i51X/RYOh/fz4Jae4mLRTuCJKICZV/WpU3MKB6Z1JhYVVXWfy7qnXhSc0ta9I9/iolOs4/IJuhsxwxUYTwTdCd3vb5/ggtKWYy/opngglC8ngHLqEIlrx3ZkZafJiWYtOupoKJpn/xAU4NCIQU7rSPa+xHvH8dr8IfhcDukX2jUTP/H4vg1yvDRJKd7ClF8RSllimOczUBuTTGVJAQ19nsC+dLlIIcoOa3i7KhA=
Content-Type: multipart/alternative; boundary="_000_BYAPR11MB3544B2488D14307537E09774D03A0BYAPR11MB3544namp_"
MIME-Version: 1.0
X-MS-Exchange-CrossTenant-Network-Message-Id: 8a282291-35f3-4c65-547a-08d6cd88ad49
X-MS-Exchange-CrossTenant-originalarrivaltime: 30 Apr 2019 16:27:02.4873 (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: BYAPR11MB2870
X-OriginatorOrg: cisco.com
X-Outbound-SMTP-Client: 173.37.102.17, xch-rcd-007.cisco.com
X-Outbound-Node: rcdn-core-6.cisco.com
Archived-At: <https://mailarchive.ietf.org/arch/msg/idr/4dCI7EBqM8QsYmerHMg_fteR-_E>
Subject: Re: [Idr] Early Code Point Allocation for draft-ietf-idr-segment-routing-te-policy [4/30 to 5/14/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: Tue, 30 Apr 2019 16:27:13 -0000
Hi Sue et all, I support the early allocation of BGP Tunnel Allocation Sub-TLVs defined in section 8.3 : TBD1 ENLP sub-TLV This document TBD2 Priority sub-TLV This document TBD3 Policy Name sub-TLV This document This would be needed for implementation. Thanks, Kausik From: Idr <idr-bounces@ietf.org> On Behalf Of Ketan Talaulikar (ketant) Sent: Tuesday, April 30, 2019 7:04 AM To: Susan Hares <shares@ndzh.com>; idr@ietf.org Cc: draft-ietf-idr-segment-routing-te-policy@ietf.org; Przemyslaw Krol <pkrol@google.com> Subject: Re: [Idr] Early Code Point Allocation for draft-ietf-idr-segment-routing-te-policy [4/30 to 5/14/2019] Hi Sue/All, I support the early allocation for code-points for the remaining TLVs defined in this WG document. We need the same for implementation. Thanks, Ketan From: Idr <idr-bounces@ietf.org<mailto:idr-bounces@ietf.org>> On Behalf Of Susan Hares Sent: 30 April 2019 18:27 To: idr@ietf.org<mailto:idr@ietf.org> Cc: draft-ietf-idr-segment-routing-te-policy@ietf.org<mailto:draft-ietf-idr-segment-routing-te-policy@ietf.org> Subject: [Idr] Early Code Point Allocation for draft-ietf-idr-segment-routing-te-policy [4/30 to 5/14/2019] This begins a 2 week call for early allocation for draft-ietf-idr-segment-routing-te-policy-05.txt . https://datatracker..ietf.org/doc/draft-ietf-idr-segment-routing-te-policy/<https://datatracker.ietf.org/doc/draft-ietf-idr-segment-routing-te-policy/> Please note that in this draft in section 8.1-8.3 to some values with existing early allocation, but in sections 8.3 there are 3 values: (ENLP sub-TLV, Priority sub-TLV, and Policy Name sub-TLV) that need early assignment. Section 8.4, 8.5 and 8.6 define new registries which do not need early allocation. Please comment early and often on early allocation. The authors have indicated their preference for values on this email list. The authors have indicated that they have 3+ implementations which need these values in order to complete the IDR implementation requirements. Cheerily, Susan Hares
- [Idr] Early Code Point Allocation for draft-ietf-… Susan Hares
- Re: [Idr] Early Code Point Allocation for draft-i… Ketan Talaulikar (ketant)
- Re: [Idr] Early Code Point Allocation for draft-i… Kausik Majumdar (kmajumda)
- Re: [Idr] Early Code Point Allocation for draft-i… Paul Mattes
- Re: [Idr] Early Code Point Allocation for draft-i… Dhanendra Jain
- Re: [Idr] Early Code Point Allocation for draft-i… Nandan Saha
- Re: [Idr] Early Code Point Allocation for draft-i… stefano previdi
- Re: [Idr] Early Code Point Allocation for draft-i… Zafar Ali (zali)
- Re: [Idr] Early Code Point Allocation for draft-i… Gaurav Dawra
- Re: [Idr] Early Code Point Allocation for draft-i… Zhuangshunwan
- Re: [Idr] Early Code Point Allocation for draft-i… Lizhenbin
- Re: [Idr] Early Code Point Allocation for draft-i… Przemyslaw Krol
- Re: [Idr] Early Code Point Allocation for draft-i… Ketan Talaulikar (ketant)
- Re: [Idr] Early Code Point Allocation for draft-i… Dhanendra Jain