IETF Logo Mail Archive

[Pce] Re: Where the Controlled ID info shuold be carried/encoded?

julien.meuric@orange.com Wed, 31 July 2024 07:51 UTC

Return-Path: <julien.meuric@orange.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 334FBC14F736 for <pce@ietfa.amsl.com>; Wed, 31 Jul 2024 00:51:19 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.805
X-Spam-Level:
X-Spam-Status: No, score=-2.805 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_LOW=-0.7, RCVD_IN_MSPIKE_H4=0.001, RCVD_IN_MSPIKE_WL=0.001, RCVD_IN_ZEN_BLOCKED_OPENDNS=0.001, SPF_PASS=-0.001, T_SCC_BODY_TEXT_LINE=-0.01, UNPARSEABLE_RELAY=0.001, URIBL_DBL_BLOCKED_OPENDNS=0.001, URIBL_ZEN_BLOCKED_OPENDNS=0.001] autolearn=unavailable autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (2048-bit key) header.d=orange.com
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 DgECCR9U-ZnQ for <pce@ietfa.amsl.com>; Wed, 31 Jul 2024 00:51:15 -0700 (PDT)
Received: from smtp-out.orange.com (smtp-out.orange.com [80.12.126.238]) (using TLSv1.2 with cipher ECDHE-ECDSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id D8AB0C151062 for <pce@ietf.org>; Wed, 31 Jul 2024 00:51:14 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=orange.com; i=@orange.com; q=dns/txt; s=orange002; t=1722412275; x=1753948275; h=message-id:date:mime-version:subject:to:cc:references: in-reply-to:from; bh=xwebsPgPofANp4ynbDDasWsQb0iX79d+ICgZwR0Yk84=; b=jb00q4hw372FfxlKd/spN0VqAVXTRQbSoFtDAQv21Yzvo7TArJ2bpcrR EQ65ijIRqfcxRQ8MUOcBdGMPYbpJLtvgSOrWMzc4WeWYr0oho6EP9MZnt tCgcaslCqbyvUWkixqR3xiYesUZ6lhK0cIcnME1sujvriL/GU+t4ZjY0Z NNZi+NlvEhs0iDvHhPiOtR2ZL2moctFiUD4jfLSMqnLE9zXbwcIVIsbHg sh8mz7Ys5ST2vkrlDiEWD0HK1bulREgrtgz//GfE9QReDYIbC+/EHYAxZ 3J8ywyNl2gq6whSvNlY33DoqKEj7aImTH98F82YPCwkUdHOVHjhvRdevX w==;
Received: from unknown (HELO opfedv1rlp0f.nor.fr.ftgroup) ([x.x.x.x]) by smtp-out.orange.com with ESMTP/TLS/ECDHE-RSA-AES256-GCM-SHA384; 31 Jul 2024 09:51:13 +0200
Received: from unknown (HELO OPE16NORMBX407.corporate.adroot.infra.ftgroup) ([x.x.x.x]) by opfedv1rlp0f.nor.fr.ftgroup with ESMTP/TLS/ECDHE-RSA-AES128-GCM-SHA256; 31 Jul 2024 09:51:13 +0200
Received: from [x.x.x.x] [x.x.x.x] by OPE16NORMBX407.corporate.adroot.infra.ftgroup [x.x.x.x] with Microsoft SMTP Server (version=TLS1_2, cipher=TLS_ECDHE_RSA_WITH_AES_128_GCM_SHA256) id 15.1.2507.39; Wed, 31 Jul 2024 09:51:12 +0200
From: julien.meuric@orange.com
X-IronPort-AV: E=Sophos;i="6.09,250,1716242400"; d="p7s'346?scan'346,208,346";a="174133631"
Message-ID: <45d7e8b6-30f5-48e2-8761-120907de06f1@orange.com>
Date: Wed, 31 Jul 2024 09:51:04 +0200
MIME-Version: 1.0
User-Agent: Mozilla Thunderbird
To: "Samuel Sidor (ssidor)" <ssidor@cisco.com>
References: <c7083e8f89e74d4fa9985842b4c0e8b5@huawei.com> <CAP7zK5ZApRFNvtqZoLjVX=-w3eRUvy77mJAeoUvTTo26_V8RNA@mail.gmail.com> <CAP7zK5aRrv1OFt1e5mGvOcbgEAb2kibr2c81oO_6+Jerk+_rYg@mail.gmail.com> <09acf5face1d472a9267a5d92568dd64@huawei.com> <CH0PR08MB73536B5001F740343F5F70F491DB2@CH0PR08MB7353.namprd08.prod.outlook.com> <CAP7zK5ZuFC6dD5av-6S6Ade0hY5_Yg1uLoFTJfqtUfckntE7pA@mail.gmail.com> <IA0PR11MB77923AE70002504379499526D0B12@IA0PR11MB7792.namprd11.prod.outlook.com>
Content-Language: en-US, fr
Organization: Orange
In-Reply-To: <IA0PR11MB77923AE70002504379499526D0B12@IA0PR11MB7792.namprd11.prod.outlook.com>
Content-Type: multipart/signed; protocol="application/pkcs7-signature"; micalg="sha-256"; boundary="------------ms080403040402040509090207"
X-Originating-IP: [10.115.26.53]
X-ClientProxiedBy: OPE16NORMBX202.corporate.adroot.infra.ftgroup (10.115.26.7) To OPE16NORMBX407.corporate.adroot.infra.ftgroup (10.115.27.16)
Message-ID-Hash: 37NM3TISSWH32QAMZCAQPDDBMJXFCOJL
X-Message-ID-Hash: 37NM3TISSWH32QAMZCAQPDDBMJXFCOJL
X-MailFrom: julien.meuric@orange.com
X-Mailman-Rule-Misses: dmarc-mitigation; no-senders; approved; emergency; loop; banned-address; member-moderation; header-match-pce.ietf.org-0; nonmember-moderation; administrivia; implicit-dest; max-recipients; max-size; news-moderation; no-subject; digests; suspicious-header
CC: Cheng Li <c.l=40huawei.com@dmarc.ietf.org>, "pce@ietf.org" <pce@ietf.org>
X-Mailman-Version: 3.3.9rc4
Precedence: list
Subject: [Pce] Re: Where the Controlled ID info shuold be carried/encoded?
List-Id: Path Computation Element <pce.ietf.org>
Archived-At: <https://mailarchive.ietf.org/arch/msg/pce/a-ZAOU6VdIUzk1wKl_qAYCvw5uY>
List-Archive: <https://mailarchive.ietf.org/arch/browse/pce>
List-Help: <mailto:pce-request@ietf.org?subject=help>
List-Owner: <mailto:pce-owner@ietf.org>
List-Post: <mailto:pce@ietf.org>
List-Subscribe: <mailto:pce-join@ietf.org>
List-Unsubscribe: <mailto:pce-leave@ietf.org>

Hi Samuel.

Assuming we get consensus on option 1, I believe it does make sense to 
add a sentence in the I-D leaving explicitly the door open for a further 
extension.

Thanks,

Julien


On 31/07/2024 09:41, Samuel Sidor (ssidor) wrote:
> Does it make sense to explicitly mentioned in the draft that updating 
> ranges dynamically was considered, but is considered out of scope and 
> can be introduced later as separate draft if frequent range updates 
> are needed?

v2.46.0 | Report a Bug | By Email | System Status