Re: [Pce] Early code point allocation for draft-ietf-pce-segment-routing-policy-cp

Dhruv Dhody <dhruv.ietf@gmail.com> Sun, 07 February 2021 04:36 UTC

Return-Path: <dhruv.ietf@gmail.com>
X-Original-To: pce@ietfa.amsl.com
Delivered-To: pce@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 1AFED3A2F86 for <pce@ietfa.amsl.com>; Sat, 6 Feb 2021 20:36:50 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.098
X-Spam-Level:
X-Spam-Status: No, score=-2.098 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, DKIM_VALID_EF=-0.1, FREEMAIL_FROM=0.001, RCVD_IN_DNSWL_NONE=-0.0001, SPF_HELO_NONE=0.001, SPF_PASS=-0.001, URIBL_BLOCKED=0.001] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (2048-bit key) header.d=gmail.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 Kn_RhKf3E0gg for <pce@ietfa.amsl.com>; Sat, 6 Feb 2021 20:36:48 -0800 (PST)
Received: from mail-il1-x130.google.com (mail-il1-x130.google.com [IPv6:2607:f8b0:4864:20::130]) (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 45AB83A2F85 for <pce@ietf.org>; Sat, 6 Feb 2021 20:36:48 -0800 (PST)
Received: by mail-il1-x130.google.com with SMTP id e1so9799613ilu.0 for <pce@ietf.org>; Sat, 06 Feb 2021 20:36:48 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20161025; h=mime-version:references:in-reply-to:from:date:message-id:subject:to :cc; bh=QyZ/wpgIu2wcueLhmPDj56qiTwy7w85IEJckADWeoJE=; b=Zo5InmkjFDoSZ3NTH7bD8tJ7YNw2s/B/A2TGn0n/CqVYM5aPQvc+R2ize/uQH7u/ic 73OTkbRkskU3P8MeIizFRCPnDYDGEdp69pV8c6YtZAiTlzEqLawdxGiInv52qZlObxam jB1R2nf7QMrYUbAztB/gUOglR85GhAlUHcbhDJRiq9nMQ2QVJAjZ4WzxFg5Ehso9qHlZ v2pcUBIyt/PjaTxUEoROghfdGk6Hr0ZuXCiposlzwc/5PCU4zEobaCqdPCS+AYe7RCJW AmZtKRozqpq1IRn6Abn2SioqMl5j2LUtCNgzfDvriFQKwAXeWI/hKMsBpRs8Uct6HTQ3 d1Rg==
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=QyZ/wpgIu2wcueLhmPDj56qiTwy7w85IEJckADWeoJE=; b=UjU47zzsS7QW2kqFC/1Kav4xuSTbZj44t/SwZnQ4Lqaoyugh8ByCtEBdXYrtWVCjDV EzeBL4q///yRD6vVFeJEh6zJreBdTllvC01v8G1Ut1dNjm0nKBqBk6x2cfHmiQi1w7vh cjpSuxsVRCZ27ED7vrQ0evcS78v+8vR1fKGeZD2d04oV3Cxynf4XRCTEpa6LzVDzOz7O VUQfwpV0rlLwWPy0DVs5HfeQgPC2BA9mRnUOmeK3eUBJvJLs9av+jFNTGaqM0Vfs3FV4 rb88AQKtgjJrWQF4hlapjalQGp/7oFzMWhFBHDVa7Oax+vZK0rwo/X5KeeCwTcgE9ga7 LpOw==
X-Gm-Message-State: AOAM530Cophn0SEz1paYEQCkyA96ZXAlC8OEDgW8fLCq+nPnX/qcG7cg dT1EMedfF/i5WhTRSUCBAslPqIxvz5Wsx0fjURY=
X-Google-Smtp-Source: ABdhPJwMkaymbfobh5GkHNFv0DTo4uIgI8oRDWFTJD9M5I75cnJxE5fPk9+Xk2PT5bzAwgnR3183VLufyjZZynUfmQ8=
X-Received: by 2002:a92:5b08:: with SMTP id p8mr10328735ilb.124.1612672607055; Sat, 06 Feb 2021 20:36:47 -0800 (PST)
MIME-Version: 1.0
References: <557499ee-62df-102e-3da4-7fd386b7ff98@orange.com> <AM7PR07MB6248748F50E97F6EBBDC5623A0B19@AM7PR07MB6248.eurprd07.prod.outlook.com>
In-Reply-To: <AM7PR07MB6248748F50E97F6EBBDC5623A0B19@AM7PR07MB6248.eurprd07.prod.outlook.com>
From: Dhruv Dhody <dhruv.ietf@gmail.com>
Date: Sun, 07 Feb 2021 10:06:10 +0530
Message-ID: <CAB75xn4-CVSiciw22MRMzW7QrBd2B-_w9q+NqROi=JXDCqHr2Q@mail.gmail.com>
To: tom petch <ietfc@btconnect.com>
Cc: "julien.meuric@orange.com" <julien.meuric@orange.com>, "pce@ietf.org" <pce@ietf.org>
Content-Type: text/plain; charset="UTF-8"
Archived-At: <https://mailarchive.ietf.org/arch/msg/pce/ErOIkVqQz1JFkm9tnbMYmZx0zCk>
Subject: Re: [Pce] Early code point allocation for draft-ietf-pce-segment-routing-policy-cp
X-BeenThere: pce@ietf.org
X-Mailman-Version: 2.1.29
Precedence: list
List-Id: Path Computation Element <pce.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/pce>, <mailto:pce-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/pce/>
List-Post: <mailto:pce@ietf.org>
List-Help: <mailto:pce-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/pce>, <mailto:pce-request@ietf.org?subject=subscribe>
X-List-Received-Date: Sun, 07 Feb 2021 04:36:50 -0000

Hi Tom, WG,

On Sat, Feb 6, 2021 at 5:36 PM tom petch <ietfc@btconnect.com> wrote:
>
> From: Pce <pce-bounces@ietf.org> on behalf of julien.meuric@orange.com <julien.meuric@orange.com>
> Sent: 01 February 2021 10:54
>
> Hi WG,
>
> We have received a request from the authors of
> draft-ietf-pce-segment-routing-policy-cp for an early code point allocation.
>
> <tp>
>
> Which code point or code points?
>
> This I-D asks IANA to allocate eleven values; to which of these does the early allocation request apply?
>

All of them.

This I-D is asking for allocations from 3 existing sub-registries:

ASSOCIATION Type Field
(https://datatracker.ietf.org/doc/html/draft-ietf-pce-segment-routing-policy-cp-02#section-7.1)
https://www.iana.org/assignments/pcep/pcep.xhtml#association-type-field

PCEP-ERROR Object Error Types and Values
(https://datatracker.ietf.org/doc/html/draft-ietf-pce-segment-routing-policy-cp-02#section-7.2)
https://www.iana.org/assignments/pcep/pcep.xhtml#pcep-error-object

PCEP TLV Type Indicators
(https://datatracker.ietf.org/doc/html/draft-ietf-pce-segment-routing-policy-cp-02#section-7.3)
https://www.iana.org/assignments/pcep/pcep.xhtml#pcep-tlv-type-indicators

Please feedback to the list if you feel the RFC 7120 criteria listed
in the original email does not meet any (or all) of the codepoints
allocation requests.

Thanks!
Dhruv & Julien

> Tom Petch
>
> RFC 7120 requires to meet the following criteria to proceed:
>
> b. The format, semantics, processing, and other rules related to
> handling the protocol entities defined by the code points
> (henceforth called "specifications") must be adequately described
> in an Internet-Draft.
> c. The specifications of these code points must be stable; i.e., if
> there is a change, implementations based on the earlier and later
> specifications must be seamlessly interoperable.
>
> If anyone believes that the draft does not meet these criteria, or
> believes that early allocation is not appropriate for any other
> reason, please send an email to the PCE mailing list explaining why. If
> the chairs hear no objections by Monday, February 15th, we will kick off
> the early allocation request.
>
> Thanks!
>
> Dhruv & Julien
>
>
>
> _______________________________________________
> Pce mailing list
> Pce@ietf.org
> https://www.ietf.org/mailman/listinfo/pce