IETF Logo Mail Archive

Re: [OPSAWG] Research on additional registry work

mohamed.boucadair@orange.com Tue, 29 November 2022 14:27 UTC

Return-Path: <mohamed.boucadair@orange.com>
X-Original-To: opsawg@ietfa.amsl.com
Delivered-To: opsawg@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id B7C0CC14CE38 for <opsawg@ietfa.amsl.com>; Tue, 29 Nov 2022 06:27:39 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.094
X-Spam-Level:
X-Spam-Status: No, score=-2.094 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, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_BLOCKED=0.001, RCVD_IN_MSPIKE_H2=-0.001, RCVD_IN_ZEN_BLOCKED_OPENDNS=0.001, SPF_HELO_NONE=0.001, SPF_PASS=-0.001, UNPARSEABLE_RELAY=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=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 7K8b2cSw-82W for <opsawg@ietfa.amsl.com>; Tue, 29 Nov 2022 06:27:35 -0800 (PST)
Received: from relais-inet.orange.com (relais-inet.orange.com [80.12.70.34]) (using TLSv1.3 with cipher TLS_AES_256_GCM_SHA384 (256/256 bits) key-exchange X25519 server-signature RSA-PSS (2048 bits) server-digest SHA256) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 7FF11C14CF09 for <opsawg@ietf.org>; Tue, 29 Nov 2022 06:27:35 -0800 (PST)
Received: from opfednr04.francetelecom.fr (unknown [xx.xx.xx.68]) (using TLSv1.3 with cipher TLS_AES_256_GCM_SHA384 (256/256 bits) key-exchange X25519 server-signature RSA-PSS (2048 bits)) (No client certificate requested) by opfednr26.francetelecom.fr (ESMTP service) with ESMTPS id 4NM4Rn38xDz1052; Tue, 29 Nov 2022 15:27:33 +0100 (CET)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=orange.com; s=ORANGE001; t=1669732053; bh=L+IqgeAhpC/mBMdf1d4YsZWodRmXXWIgdcUeN+Ab6mM=; h=From:To:Subject:Date:Message-ID:Content-Type:MIME-Version; b=dFOeGKhenMMqxdbzOJjyttWEdtqQ9YnpXvYZId+UOdMUELshyGRoquyEa6Gzd6Ngx 18LjARnBbXnTvaonh3hNBvqj1Lq8DH8j2aezAGv0eV5nwc6Qdd9SAG+eiFFRfccTjF tSRfmp5ZD4+OuZEj+OMcDs9ssM0ZM3J26Cja4LcOse2QQ4BfqgGLUT5Zj2Ty0TSw3m UJ691Wd7A5ScI0JhQe4S9gcsfQ+ONmQgnpMOCB/q/67NYbEeQFsp+kfNdEabDd4Y5X q0b2YPhBibe09N+jI6KMR2dgPO4hcFFLhaaYGRqUXiB8wdgGm4/Tw9faFTyvgM47ft iye5NvRuYe8wQ==
From: mohamed.boucadair@orange.com
To: "Joe Clarke (jclarke)" <jclarke@cisco.com>, "opsawg@ietf.org" <opsawg@ietf.org>
Thread-Topic: Research on additional registry work
Thread-Index: AQHZA14QwUL84GlqQE6OqLdX1br9RK5V30Gg
Content-Class:
Date: Tue, 29 Nov 2022 14:27:32 +0000
Message-ID: <13385_1669732053_638616D5_13385_48_1_e622f187387144a58f791b7a6442f1a4@orange.com>
References: <BN9PR11MB5371EAE85F6CD671ED7D504CB8139@BN9PR11MB5371.namprd11.prod.outlook.com>
In-Reply-To: <BN9PR11MB5371EAE85F6CD671ED7D504CB8139@BN9PR11MB5371.namprd11.prod.outlook.com>
Accept-Language: fr-FR, en-US
Content-Language: fr-FR
X-MS-Has-Attach:
X-MS-TNEF-Correlator:
msip_labels: MSIP_Label_07222825-62ea-40f3-96b5-5375c07996e2_Enabled=true; MSIP_Label_07222825-62ea-40f3-96b5-5375c07996e2_SetDate=2022-11-29T13:03:50Z; MSIP_Label_07222825-62ea-40f3-96b5-5375c07996e2_Method=Privileged; MSIP_Label_07222825-62ea-40f3-96b5-5375c07996e2_Name=unrestricted_parent.2; MSIP_Label_07222825-62ea-40f3-96b5-5375c07996e2_SiteId=90c7a20a-f34b-40bf-bc48-b9253b6f5d20; MSIP_Label_07222825-62ea-40f3-96b5-5375c07996e2_ActionId=9f3039d4-0253-4ba2-9dc7-abbe51fb0519; MSIP_Label_07222825-62ea-40f3-96b5-5375c07996e2_ContentBits=0
x-originating-ip: [10.115.27.51]
Content-Type: multipart/alternative; boundary="_000_e622f187387144a58f791b7a6442f1a4orangecom_"
MIME-Version: 1.0
Archived-At: <https://mailarchive.ietf.org/arch/msg/opsawg/zeCCjXXa28LzgWt0tiEcEkDVmP0>
Subject: Re: [OPSAWG] Research on additional registry work
X-BeenThere: opsawg@ietf.org
X-Mailman-Version: 2.1.39
Precedence: list
List-Id: OPSA Working Group Mail List <opsawg.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/opsawg>, <mailto:opsawg-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/opsawg/>
List-Post: <mailto:opsawg@ietf.org>
List-Help: <mailto:opsawg-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/opsawg>, <mailto:opsawg-request@ietf.org?subject=subscribe>
X-List-Received-Date: Tue, 29 Nov 2022 14:27:39 -0000

Hi Joe, all,

Yes, I had a discussion with Benoît during the IETF meeting to see how to handle this. We agreed to proceed with at least two documents:

  *   draft-boucadair-opsawg-rfc7125-update to update the TCP IPFIX RFC.
  *   Edit a second draft to "clean" other entries in registry. This document is intended to include only simple fixes and which do not require updating existing RFCs. The candidate list of these proposed fixes can be seen at https://boucadair.github.io/simple-ipfix-fixes/draft-boucla-opsawg-ipfix-fixes.html. New IEs, if needed, will be moved to a separate document. simple-ipfix-fixes may or may not be published as an RFC.


Cheers,
Med

De : Joe Clarke (jclarke) <jclarke@cisco.com>
Envoyé : lundi 28 novembre 2022 20:23
À : opsawg@ietf.org
Cc : BOUCADAIR Mohamed INNOV/NET <mohamed.boucadair@orange.com>
Objet : Research on additional registry work

Hello, Med.  I was curious if you had a chance to dig into the IANA registries to see where else there might be a need for updates.  What we had said at 115 was that you would take a look and see what the scope of work might be.  That might turn into more docs to track those various registry changes.

Thanks.

Joe

_________________________________________________________________________________________________________________________

Ce message et ses pieces jointes peuvent contenir des informations confidentielles ou privilegiees et ne doivent donc
pas etre diffuses, exploites ou copies sans autorisation. Si vous avez recu ce message par erreur, veuillez le signaler
a l'expediteur et le detruire ainsi que les pieces jointes. Les messages electroniques etant susceptibles d'alteration,
Orange decline toute responsabilite si ce message a ete altere, deforme ou falsifie. Merci.

This message and its attachments may contain confidential or privileged information that may be protected by law;
they should not be distributed, used or copied without authorisation.
If you have received this email in error, please notify the sender and delete this message and its attachments.
As emails may be altered, Orange is not liable for messages that have been modified, changed or falsified.
Thank you.

v2.23.0 | Report a Bug | By Email