[Pce] New I-D on Experimental PCEP Error codes

Adrian Farrel <adrian@olddog.co.uk> Wed, 03 April 2024 09:34 UTC

Return-Path: <adrian@olddog.co.uk>
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 2DCBAC15152C for <pce@ietfa.amsl.com>; Wed, 3 Apr 2024 02:34:05 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.093
X-Spam-Level:
X-Spam-Status: No, score=-2.093 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, RCVD_IN_DNSWL_BLOCKED=0.001, RCVD_IN_MSPIKE_H3=0.001, RCVD_IN_MSPIKE_WL=0.001, RCVD_IN_ZEN_BLOCKED_OPENDNS=0.001, SPF_HELO_NONE=0.001, SPF_PASS=-0.001, URIBL_BLOCKED=0.001, URIBL_DBL_BLOCKED_OPENDNS=0.001, URIBL_ZEN_BLOCKED_OPENDNS=0.001] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (2048-bit key) header.d=olddog.co.uk
Received: from mail.ietf.org ([50.223.129.194]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id UXCcDry38kUm for <pce@ietfa.amsl.com>; Wed, 3 Apr 2024 02:34:00 -0700 (PDT)
Received: from mta6.iomartmail.com (mta6.iomartmail.com [62.128.193.156]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 3517FC151522 for <pce@ietf.org>; Wed, 3 Apr 2024 02:33:58 -0700 (PDT)
Received: from vs4.iomartmail.com (vs4.iomartmail.com [10.12.10.122]) by mta6.iomartmail.com (8.14.7/8.14.7) with ESMTP id 4339XuKC020450 for <pce@ietf.org>; Wed, 3 Apr 2024 10:33:56 +0100
Received: from vs4.iomartmail.com (unknown [127.0.0.1]) by IMSVA (Postfix) with ESMTP id A40854604F for <pce@ietf.org>; Wed, 3 Apr 2024 10:33:56 +0100 (BST)
Received: from vs4.iomartmail.com (unknown [127.0.0.1]) by IMSVA (Postfix) with ESMTP id 98C194604D for <pce@ietf.org>; Wed, 3 Apr 2024 10:33:56 +0100 (BST)
Received: from asmtp1.iomartmail.com (unknown [10.12.10.248]) by vs4.iomartmail.com (Postfix) with ESMTPS for <pce@ietf.org>; Wed, 3 Apr 2024 10:33:56 +0100 (BST)
Received: from LAPTOPK7AS653V ([148.252.140.47]) (authenticated bits=0) by asmtp1.iomartmail.com (8.14.7/8.14.7) with ESMTP id 4339Xt7k004981 (version=TLSv1/SSLv3 cipher=ECDHE-RSA-AES256-GCM-SHA384 bits=256 verify=NO) for <pce@ietf.org>; Wed, 3 Apr 2024 10:33:56 +0100
Reply-To: adrian@olddog.co.uk
From: Adrian Farrel <adrian@olddog.co.uk>
To: pce@ietf.org
References: <171213611424.47781.8304454499695402364@ietfa.amsl.com>
In-Reply-To: <171213611424.47781.8304454499695402364@ietfa.amsl.com>
Date: Wed, 03 Apr 2024 10:33:53 +0100
Organization: Old Dog Consulting
Message-ID: <007201da85aa$0bd42d00$237c8700$@olddog.co.uk>
MIME-Version: 1.0
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: 7bit
X-Mailer: Microsoft Outlook 16.0
Content-Language: en-gb
Thread-Index: AdqFqfb+aSt9C3qoR1SWcCIJHQCHLA==
X-Originating-IP: 148.252.140.47
X-Thinkmail-Auth: adrian@olddog.co.uk
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed; d=olddog.co.uk; h=reply-to :from:to:references:in-reply-to:subject:date:message-id :mime-version:content-type:content-transfer-encoding; s= 20221128; bh=78TXRC/hVB0qCbqY78Ss7ZBqSwYVCDI3hTpscd+aG3k=; b=Nh5 6TXkcXP9c75fclnCrKDjIbJjRMVktZcODrYvI9dPkpKzYhGjV2TxfFzPnU/CATyC na7e35MQnazVERnGCRrMcCRNtYyJbYAoEXx7J4xFC5Bs7o3Mycb9mhkkoF08adfV C7mLHFyoqmsV+gK2oG1Uj7hAJIKhH/c6adLyzzcLtp8uhb2yZRFUeKJYJ/BbeuF8 ZiW8F/qqxm3wWCegMdswHRnp7+lHBt9+sP7nWy3vcAQlB+8jKjwGZNt8UxoeZEwG UENTx4BG/omTZ866Q2LP/hHjlnpEs21EaTnP4TL0pPupuJsV+GWzo3DpOQUkaewO VdBEDthhQfIBm2KWkVg==
X-TM-AS-GCONF: 00
X-TM-AS-Product-Ver: IMSVA-9.1.0.2090-9.0.0.1002-28294.006
X-TM-AS-Result: No--8.757-10.0-31-10
X-imss-scan-details: No--8.757-10.0-31-10
X-TMASE-Version: IMSVA-9.1.0.2090-9.0.1002-28294.006
X-TMASE-Result: 10--8.757400-10.000000
X-TMASE-MatchedRID: RTC/st8+7P/kht9v6t8rY65i3jK3KDOox287VGn6yCa4mfZGgSa8sorq nYTxkVFKh1wqj9tj1RCVIQAmwcXc40OlCbDfmPVyBe3KRVyu+k0QOcMSo0926mz3xnx8b/qRZ+x r/gPMvBUTTObItRqm1Oz5F5v67Oj31+eFZnMe0WB85pjA/x1xfgO3/A5KGHP/yzeZ0EF2JhJCIy KeBKUqgof3DLCrT4qlkZOl7WKIImq0P2qkGU0XynAruZnjhopui2QFaYS1v20qtq5d3cxkNUjsy SyHk2QGM7qFGE4FOHKY9G4lJJlmSAOcQnVulih6Po7A7ZreGbw=
X-TMASE-SNAP-Result: 1.821001.0001-0-1-22:0,33:0,34:0-0
Archived-At: <https://mailarchive.ietf.org/arch/msg/pce/Z5UUaLDADzmK0wK7vS9NtMlBB7A>
Subject: [Pce] New I-D on Experimental PCEP Error codes
X-BeenThere: pce@ietf.org
X-Mailman-Version: 2.1.39
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, 03 Apr 2024 09:34:05 -0000

Hi PCE,

After some discussions with Dhruv about how and why we wrote RFC 8356,
Haomian and I have posted a new draft to allow Experimental error codes in
PCEP.

In summary, 8356 created space for Experimental PCEP messages, objects,
TLVs.
The assumption (see Appendix A) was that you could do anything experimental
using these three elements, and nothing further was needed.
This was true to some extent, but we have been concerned about the case of
carrying Error-Types and Error-values in experiments.
It could be possible for the experiment to define its own new object (say
the "Experimental-PCEP-Error Object") and use that to carry experimental
errors.
However, we felt that that would make it harder to migrate an experiment to
the standards track in the fullness of time.
So this I-D creates space for Experimental Error-Types to be carried in the
PCEP-Error Object.
Note that it does not create space for Experimental Error-values within the
existing Error-Types - we think that is unnecessary and would make the
registry messy.

The IETF datatracker status page for this Internet-Draft is:
https://datatracker.ietf.org/doc/draft-farrel-pce-experimental-errors/ 

There is also an HTMLized version available at:
https://datatracker.ietf.org/doc/html/draft-farrel-pce-experimental-errors-0
0 

Please have a look and tell us if you think this is a good idea or a waste
of time.
FWIW, we believe we would use it in completing the work to move the PCEP-LS
draft to be fully Experimental.

Cheers,
Adrian (and Haomian)