RFC 9735 on Locator/ID Separation Protocol (LISP) Distinguished Name Encoding
rfc-editor@rfc-editor.org Wed, 05 February 2025 23:35 UTC
Return-Path: <wwwrun@rfcpa.rfc-editor.org>
X-Original-To: ietf-announce@ietfa.amsl.com
Delivered-To: ietf-announce@ietfa.amsl.com
Received: from mail.ietf.org (ietfa.amsl.com [50.223.129.194]) (using TLSv1.3 with cipher TLS_AES_256_GCM_SHA384 (256/256 bits) key-exchange X25519 server-signature ECDSA (P-256) server-digest SHA256) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPSA id 93C9DC1D6211; Wed, 5 Feb 2025 15:35:59 -0800 (PST)
Received: from rfcpa.rfc-editor.org (unknown [167.172.21.234]) (using TLSv1.3 with cipher TLS_AES_256_GCM_SHA384 (256/256 bits) key-exchange X25519 server-signature ECDSA (P-256) server-digest SHA256) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 80BBBC1D3DE2; Wed, 5 Feb 2025 15:35:59 -0800 (PST)
Received: by rfcpa.rfc-editor.org (Postfix, from userid 461) id DF1D81DF154; Wed, 5 Feb 2025 15:35:58 -0800 (PST)
To: ietf-announce@ietf.org, rfc-dist@rfc-editor.org
Subject: RFC 9735 on Locator/ID Separation Protocol (LISP) Distinguished Name Encoding
From: rfc-editor@rfc-editor.org
Content-type: text/plain; charset="UTF-8"
Message-Id: <20250205233558.DF1D81DF154@rfcpa.rfc-editor.org>
Date: Wed, 05 Feb 2025 15:35:58 -0800
Message-ID-Hash: U6RJMPBXFIQSBUHC5XEYXV2RFESZKJ7K
X-Message-ID-Hash: U6RJMPBXFIQSBUHC5XEYXV2RFESZKJ7K
X-MailFrom: wwwrun@rfcpa.rfc-editor.org
X-Mailman-Rule-Misses: dmarc-mitigation; no-senders; approved; emergency; loop; banned-address; member-moderation; header-match-ietf-announce.ietf.org-0; nonmember-moderation; administrivia; implicit-dest; max-recipients; max-size; news-moderation; no-subject; digests; suspicious-header
CC: rfc-editor@rfc-editor.org, drafts-update-ref@iana.org
X-Mailman-Version: 3.3.9rc6
Precedence: list
List-Id: "IETF announcement list. No discussions." <ietf-announce.ietf.org>
Archived-At: <https://mailarchive.ietf.org/arch/msg/ietf-announce/1Md0EtDJ_xcAnKIi62oV6nuye4U>
List-Archive: <https://mailarchive.ietf.org/arch/browse/ietf-announce>
List-Help: <mailto:ietf-announce-request@ietf.org?subject=help>
List-Owner: <mailto:ietf-announce-owner@ietf.org>
List-Post: <mailto:ietf-announce@ietf.org>
List-Subscribe: <mailto:ietf-announce-join@ietf.org>
List-Unsubscribe: <mailto:ietf-announce-leave@ietf.org>
A new Request for Comments is now available in online RFC libraries.
RFC 9735
Title: Locator/ID Separation Protocol (LISP) Distinguished
Name Encoding
Author: D. Farinacci,
L. Iannone, Ed.
Status: Standards Track
Stream: IETF
Date: February 2025
Mailbox: farinacci@gmail.com,
luigi.iannone@huawei.com
Pages: 9
Updates/Obsoletes/SeeAlso: None
I-D Tag: draft-ietf-lisp-name-encoding-17.txt
URL: https://www.rfc-editor.org/info/rfc9735
DOI: 10.17487/RFC9735
This document defines how to use the Address Family Identifier (AFI)
17 "Distinguished Name" in the Locator/ID Separation Protocol (LISP).
LISP introduces two new numbering spaces: Endpoint Identifiers
(EIDs) and Routing Locators (RLOCs). Distinguished Names (DNs) can be
used in either EID-Records or RLOC-Records in LISP control messages
to convey additional information.
This document is a product of the Locator/ID Separation Protocol Working Group of the IETF.
This is now a Proposed Standard.
STANDARDS TRACK: This document specifies an Internet Standards Track
protocol for the Internet community, and requests discussion and suggestions
for improvements. Please refer to the current edition of the Official
Internet Protocol Standards (https://www.rfc-editor.org/standards) for the
standardization state and status of this protocol. Distribution of this
memo is unlimited.
This announcement is sent to the IETF-Announce and rfc-dist lists.
To subscribe or unsubscribe, see
https://www.ietf.org/mailman/listinfo/ietf-announce
https://mailman.rfc-editor.org/mailman/listinfo/rfc-dist
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