RFC 9299 on An Architectural Introduction to the Locator/ID Separation Protocol (LISP)
rfc-editor@rfc-editor.org Thu, 20 October 2022 21:06 UTC
Return-Path: <wwwrun@rfcpa.amsl.com>
X-Original-To: ietf-announce@ietfa.amsl.com
Delivered-To: ietf-announce@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id C3255C14CE3C for <ietf-announce@ietfa.amsl.com>; Thu, 20 Oct 2022 14:06:09 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -3.959
X-Spam-Level:
X-Spam-Status: No, score=-3.959 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, HEADER_FROM_DIFFERENT_DOMAINS=0.249, RCVD_IN_DNSWL_MED=-2.3, RCVD_IN_ZEN_BLOCKED_OPENDNS=0.001, SPF_PASS=-0.001, T_SCC_BODY_TEXT_LINE=-0.01, URIBL_DBL_BLOCKED_OPENDNS=0.001, URIBL_ZEN_BLOCKED_OPENDNS=0.001] autolearn=unavailable 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 C9oYe8ZguCib for <ietf-announce@ietfa.amsl.com>; Thu, 20 Oct 2022 14:06:04 -0700 (PDT)
Received: from rfcpa.amsl.com (rfc-editor.org [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 7A19CC14CE28 for <ietf-announce@ietf.org>; Thu, 20 Oct 2022 14:06:04 -0700 (PDT)
Received: by rfcpa.amsl.com (Postfix, from userid 499) id 5EA3215D30D; Thu, 20 Oct 2022 14:06:04 -0700 (PDT)
To: ietf-announce@ietf.org, rfc-dist@rfc-editor.org
Subject: RFC 9299 on An Architectural Introduction to the Locator/ID Separation Protocol (LISP)
From: rfc-editor@rfc-editor.org
Cc: rfc-editor@rfc-editor.org, drafts-update-ref@iana.org
Content-type: text/plain; charset="UTF-8"
Message-Id: <20221020210604.5EA3215D30D@rfcpa.amsl.com>
Date: Thu, 20 Oct 2022 14:06:04 -0700
Archived-At: <https://mailarchive.ietf.org/arch/msg/ietf-announce/xABLbYXS_VJau0HxZCXIJHLEI-I>
X-BeenThere: ietf-announce@ietf.org
X-Mailman-Version: 2.1.39
Precedence: list
List-Id: "IETF announcement list. No discussions." <ietf-announce.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf-announce>, <mailto:ietf-announce-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/ietf-announce/>
List-Post: <mailto:ietf-announce@ietf.org>
List-Help: <mailto:ietf-announce-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf-announce>, <mailto:ietf-announce-request@ietf.org?subject=subscribe>
X-List-Received-Date: Thu, 20 Oct 2022 21:06:09 -0000
A new Request for Comments is now available in online RFC libraries.
RFC 9299
Title: An Architectural Introduction to the
Locator/ID Separation Protocol (LISP)
Author: A. Cabellos,
D. Saucez, Ed.
Status: Informational
Stream: IETF
Date: October 2022
Mailbox: acabello@ac.upc.edu,
damien.saucez@inria.fr
Pages: 24
Updates/Obsoletes/SeeAlso: None
I-D Tag: draft-ietf-lisp-introduction-15.txt
URL: https://www.rfc-editor.org/info/rfc9299
DOI: 10.17487/RFC9299
This document describes the architecture of the Locator/ID Separation
Protocol (LISP), making it easier to read the rest of the LISP
specifications and providing a basis for discussion about the details
of the LISP protocols. This document is used for introductory
purposes; more details can be found in the protocol specifications,
RFCs 9300 and 9301.
This document is a product of the Locator/ID Separation Protocol Working Group of the IETF.
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 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
Association Management Solutions, LLC