[IRTF-Announce] RFC 9414 on Unfortunate History of Transient Numeric Identifiers
rfc-editor@rfc-editor.org Sat, 22 July 2023 01:31 UTC
Return-Path: <wwwrun@rfcpa.amsl.com>
X-Original-To: irtf-announce@ietfa.amsl.com
Delivered-To: irtf-announce@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id D20DFC151534; Fri, 21 Jul 2023 18:31:28 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -0.854
X-Spam-Level:
X-Spam-Status: No, score=-0.854 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, HEADER_FROM_DIFFERENT_DOMAINS=0.25, RCVD_IN_ZEN_BLOCKED_OPENDNS=0.001, RDNS_NONE=0.793, SPF_PASS=-0.001, URIBL_BLOCKED=0.001, URIBL_DBL_BLOCKED_OPENDNS=0.001, URIBL_ZEN_BLOCKED_OPENDNS=0.001] autolearn=no autolearn_force=no
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 zM7M6QCdFN4P; Fri, 21 Jul 2023 18:31:23 -0700 (PDT)
Received: from rfcpa.amsl.com (unknown [50.223.129.200]) (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 B105BC15153D; Fri, 21 Jul 2023 18:31:23 -0700 (PDT)
Received: by rfcpa.amsl.com (Postfix, from userid 499) id 9193F56692; Fri, 21 Jul 2023 18:31:23 -0700 (PDT)
To: ietf-announce@ietf.org, rfc-dist@rfc-editor.org, irtf-announce@irtf.org
From: rfc-editor@rfc-editor.org
Cc: rfc-editor@rfc-editor.org, drafts-update-ref@iana.org, pearg@irtf.org
Content-type: text/plain; charset="UTF-8"
Message-Id: <20230722013123.9193F56692@rfcpa.amsl.com>
Date: Fri, 21 Jul 2023 18:31:23 -0700
Archived-At: <https://mailarchive.ietf.org/arch/msg/irtf-announce/Rn6mP1ncP6xOYkO3LKIQ2NzvSAE>
Subject: [IRTF-Announce] RFC 9414 on Unfortunate History of Transient Numeric Identifiers
X-BeenThere: irtf-announce@irtf.org
X-Mailman-Version: 2.1.39
Precedence: list
List-Id: IRTF-Announce <irtf-announce.irtf.org>
List-Unsubscribe: <https://www.irtf.org/mailman/options/irtf-announce>, <mailto:irtf-announce-request@irtf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/irtf-announce/>
List-Post: <mailto:irtf-announce@irtf.org>
List-Help: <mailto:irtf-announce-request@irtf.org?subject=help>
List-Subscribe: <https://www.irtf.org/mailman/listinfo/irtf-announce>, <mailto:irtf-announce-request@irtf.org?subject=subscribe>
X-List-Received-Date: Sat, 22 Jul 2023 01:31:28 -0000
A new Request for Comments is now available in online RFC libraries.
RFC 9414
Title: Unfortunate History of Transient Numeric Identifiers
Author: F. Gont,
I. Arce
Status: Informational
Stream: IRTF
Date: July 2023
Mailbox: fgont@si6networks.com,
iarce@quarkslab.com
Pages: 27
Updates/Obsoletes/SeeAlso: None
I-D Tag: draft-irtf-pearg-numeric-ids-history-11.txt
URL: https://www.rfc-editor.org/info/rfc9414
DOI: 10.17487/RFC9414
This document analyzes the timeline of the specification and
implementation of different types of "transient numeric identifiers"
used in IETF protocols and how the security and privacy properties of
such protocols have been affected as a result of it. It provides
empirical evidence that advice in this area is warranted. This
document is a product of the Privacy Enhancements and Assessments
Research Group (PEARG) in the IRTF.
This document is a product of the Privacy Enhancements and Assessments Research Group of the IRTF.
INFORMATIONAL: This memo provides information for the Internet community.
It does not specify an Internet standard of any kind. Distribution of
this memo is unlimited.
This announcement is sent to the IETF-Announce, rfc-dist and IRTF-Announce lists.To subscribe or unsubscribe, see
https://www.ietf.org/mailman/listinfo/ietf-announce
https://mailman.rfc-editor.org/mailman/listinfo/rfc-dist
https://www.irtf.org/mailman/listinfo/irtf-announce
For searching the RFC series, see https://www.rfc-editor.org/search
For downloading RFCs, see https://www.rfc-editor.org/retrieve/bulk
Requests for special distribution should be addressed to either the
author of the RFC in question, or to rfc-editor@rfc-editor.org. Unless
specifically noted otherwise on the RFC itself, all RFCs are for
unlimited distribution.
The RFC Editor Team
Association Management Solutions, LLC