Re: [Idr] Early Code Point Allocation for draft-ietf-idr-segment-routing-te-policy [4/30 to 5/14/2019]

Przemyslaw Krol <pkrol@google.com> Thu, 23 May 2019 15:41 UTC

Return-Path: <pkrol@google.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 321C5120123 for <idr@ietfa.amsl.com>; Thu, 23 May 2019 08:41:05 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -17.51
X-Spam-Level:
X-Spam-Status: No, score=-17.51 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, ENV_AND_HDR_SPF_MATCH=-0.5, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_NONE=-0.0001, SPF_PASS=-0.001, T_DKIMWL_WL_MED=-0.01, USER_IN_DEF_DKIM_WL=-7.5, USER_IN_DEF_SPF_WL=-7.5] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (2048-bit key) header.d=google.com
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 4V87vlnRxHxv for <idr@ietfa.amsl.com>; Thu, 23 May 2019 08:41:02 -0700 (PDT)
Received: from mail-wr1-x436.google.com (mail-wr1-x436.google.com [IPv6:2a00:1450:4864:20::436]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 9D63412011F for <idr@ietf.org>; Thu, 23 May 2019 08:41:01 -0700 (PDT)
Received: by mail-wr1-x436.google.com with SMTP id l2so6804511wrb.9 for <idr@ietf.org>; Thu, 23 May 2019 08:41:01 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=google.com; s=20161025; h=mime-version:references:in-reply-to:from:date:message-id:subject:to :cc; bh=t7yPL3g0uYiuqHKx70anCfv1DsIq7Q9rLmmKmqn2xfE=; b=YrkalPFXomlUMkiITInE6xVCARPQ2dbE3fHTXa6SPMGBnp8z7Xct5MFfiwfxGWVwGO y381YD+PrGc577OyBFziyUikXO6qmUyPCMaVf4Hdt74VpM9tyY9fFM2sTHDUH8s+2eAJ 3dA9EXijWj/RhLDV/R2tq3qhKXEN9WQYW5jEwNl57X8zZsKpV+NsBYW153lcaKw6kqsw QTEEgbASEKghyGC5MhhRI68lV7H2tzjnH28NFx8Tgt6DKb9fAusPaWoqbmSj9BoVhvvL bcyrgN+laES+UoSosfBXY19HmPR8uxvqDcaNjOx0DSi7BKTcmkDx0LqNl6be3fKpLFFj aoHg==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:mime-version:references:in-reply-to:from:date :message-id:subject:to:cc; bh=t7yPL3g0uYiuqHKx70anCfv1DsIq7Q9rLmmKmqn2xfE=; b=X+/lOJaL0obH22dBOj399vwnuHamygzSFSYPf/Fk8NOAPlW5jJLyTG5267iUje0lDs RFp3Nbtn8o8uUTW3WFtRjNYq/cHKdYISYyoYFthbGFn8i15Rvi3fjoNsAO4LxEFRQNNq A6gn4bbmLPtfIc9Z7ryX20k1pDXHt/9vhvRX0Iogs0TycMb47TOW00RxTbLE4B1gB8VE eclO7CpWZ05y+gn9ZDOVoK9/rRdiN/rVL4tId4OFX7a1kMzC0/sZo52u6rm9uduEdmdF crMI6e2okYyZKySjxBvxk9qXhk/9ksQfpHH4f2dDwHHJCvXVzUcFlIQal8Bu5QqtojPD PV/A==
X-Gm-Message-State: APjAAAX429A7Tr8UNS1KeSStb8DD0qZ/DGYqqxhSVmiIuEwy2NOcxzxI uxUsR7d9SxLPWqv/xZT3FdpG/SreKoo9r5h9ujlV1w==
X-Google-Smtp-Source: APXvYqyKm5eetMJEV8pBVm2hDpzL9x4esU1CDy1o/KHuy76eUKbKblUK2CaFeHlaPiISKxvXSiKxq0g9GwpmRWyT3wM=
X-Received: by 2002:adf:81a2:: with SMTP id 31mr58473046wra.165.1558626059510; Thu, 23 May 2019 08:40:59 -0700 (PDT)
MIME-Version: 1.0
References: <001b01d4ff54$31784b90$9468e2b0$@ndzh.com> <SN6PR11MB2845D4E5433A9C30C04D6592C13A0@SN6PR11MB2845.namprd11.prod.outlook.com> <BYAPR11MB3544B2488D14307537E09774D03A0@BYAPR11MB3544.namprd11.prod.outlook.com>
In-Reply-To: <BYAPR11MB3544B2488D14307537E09774D03A0@BYAPR11MB3544.namprd11.prod.outlook.com>
From: Przemyslaw Krol <pkrol@google.com>
Date: Thu, 23 May 2019 08:40:23 -0700
Message-ID: <CACH2EkUmr1WE3tCjCj4iTkadDuB7ZpAp=hBtNEYRWoe3YMNXaA@mail.gmail.com>
To: "Kausik Majumdar (kmajumda)" <kmajumda@cisco.com>
Cc: "Ketan Talaulikar (ketant)" <ketant@cisco.com>, Susan Hares <shares@ndzh.com>, "idr@ietf.org" <idr@ietf.org>, "draft-ietf-idr-segment-routing-te-policy@ietf.org" <draft-ietf-idr-segment-routing-te-policy@ietf.org>
Content-Type: multipart/alternative; boundary="0000000000009ddce105898fe8c3"
Archived-At: <https://mailarchive.ietf.org/arch/msg/idr/D4lXiM1LW9vDm0Na7AsMhC80hww>
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: Thu, 23 May 2019 15:41:05 -0000

Greetings,

How long does this process usually take?

thanks,
pk

On Tue, Apr 30, 2019 at 9:27 AM Kausik Majumdar (kmajumda) <
kmajumda@cisco.com> wrote:

>
>
> 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> *On Behalf Of *Susan Hares
> *Sent:* 30 April 2019 18:27
> *To:* idr@ietf.org
> *Cc:* 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
>
>
>


-- 
Przemyslaw "PK" Krol |  Strategic Network Engineer ing | pkrol@google.com