IETF Logo Mail Archive

[Pce] Early code point allocation for draft-ietf-pce-association-policy

Dhruv Dhody <dhruv.ietf@gmail.com> Wed, 22 April 2020 17:08 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 A61363A0D63; Wed, 22 Apr 2020 10:08:19 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.099
X-Spam-Level:
X-Spam-Status: No, score=-2.099 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, SPF_HELO_NONE=0.001, SPF_PASS=-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 P7i69LB0BvOI; Wed, 22 Apr 2020 10:08:18 -0700 (PDT)
Received: from mail-io1-xd33.google.com (mail-io1-xd33.google.com [IPv6:2607:f8b0:4864:20::d33]) (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 580113A078A; Wed, 22 Apr 2020 10:08:18 -0700 (PDT)
Received: by mail-io1-xd33.google.com with SMTP id 19so3171655ioz.10; Wed, 22 Apr 2020 10:08:18 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20161025; h=mime-version:from:date:message-id:subject:to:cc; bh=kkSRo/T5Pe45L7O4epargVfMeEe7Pn6KKTk9jF/XC54=; b=J4hIG+V8MZD3k37hKxX5ufKX0ZI7SXPW+Hc+9SDolfx0THwPhmk8Et/rBY/ECA0xSO 1QJMC3xgNALQfIyImcWGW1h+pQM17PwUHRl5gOww8sNTXMRTjYL/Jjp7CA/nTSR6K3Zf Ayh9kgbVIYjlRmSQWs4rn02aemyx/ZI9VrjfnDYFv3rIKhhxQvwHtIIxJT6Zxqal0AWZ 8awKgSb65rV+wbF4/Y0+ZO/1LM8JzpB3nfs43TL2qIXSVBLkDPvrQgK025gxbsS5oOEB SKKRXJUDSWE9HadFSgLOIk9XWQ3iQMvdz+9ftvyxJPR2x0U9JwO5+gA9+AcuXiA/L8v9 RXGg==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:mime-version:from:date:message-id:subject:to:cc; bh=kkSRo/T5Pe45L7O4epargVfMeEe7Pn6KKTk9jF/XC54=; b=uQdniKPgLRSh6sFOG3XJoOnS2qTuNTY1gwZ7W8o0/XpdowOfJeXF69Vif5J97GmAc2 I4rAoolcGdFis7CliSwmE5kwJMpIxdJrP/wG59JcrQSikQaYHpZY8gCCLYLWe9neeNOS djgriK6TeMi7lGwGtlweB+BfYeeyocjjhljPMlPhsCj8LFow9Ocq4ZJ3TNxR1lN6h8Qk b6QF0DCvyc4VLqBdq1Xc5MWQnryO3i8oa7D16NqsXQUxFO6SDlMUhTYMqfOomvUEc1hw i7mdc9AGacXHbVKBavEfHjtSQwjfhK7VrkP1P/DEqKuVY8V3QpQH4gvBBsoDqzeUkm0i g7Rg==
X-Gm-Message-State: AGi0PuZ2uSn1iPsiYHzQIa12p0FzOthIFQYu70mhZP4rB/0eyE7r++5u B6DXIE4d5Ae8Z6P46JTQSJIIBxyGFx/NiTWRtd530IAyH7I=
X-Google-Smtp-Source: APiQypJWJnMap9SECxF2V+kgo3GvXQl7pQGSNvrnefqXfQUmQ0Hpul3XCYPWgPC77qu0njKrpHRJ1oQ950YKFUYCU0U=
X-Received: by 2002:a6b:8b05:: with SMTP id n5mr26728478iod.68.1587575297033; Wed, 22 Apr 2020 10:08:17 -0700 (PDT)
MIME-Version: 1.0
From: Dhruv Dhody <dhruv.ietf@gmail.com>
Date: Wed, 22 Apr 2020 22:37:41 +0530
Message-ID: <CAB75xn6kVzAf8f95q1gtBvGV6qbw_7vbiYz+XUJjKxX20QU4Uw@mail.gmail.com>
To: pce@ietf.org
Cc: pce-chairs <pce-chairs@ietf.org>
Content-Type: text/plain; charset="UTF-8"
Archived-At: <https://mailarchive.ietf.org/arch/msg/pce/8M5rvyarF5ftx307oI4tQWD0YUI>
Subject: [Pce] Early code point allocation for draft-ietf-pce-association-policy
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: Wed, 22 Apr 2020 17:08:20 -0000

Hi WG,

We have received a request from the authors of
draft-ietf-pce-association-policy for an early code point allocation.

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 the
reasons.  If the chairs hear no objections by next Friday, May 1st, we
will kick off the early allocation request.

Best regards and stay safe,

Dhruv & Julien

v2.23.0 | Report a Bug | By Email