[rfc-dist] Moved to Historic: RFC 7955 on Management Guidelines for the Locator/ID Separation Protocol (LISP) Endpoint Identifier (EID) Block
rfc-editor@rfc-editor.org Fri, 01 December 2023 01:15 UTC
Return-Path: <wwwrun@rfcpa.amsl.com>
X-Original-To: rfc-dist@ietfa.amsl.com
Delivered-To: rfc-dist@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id A4E1AC151997; Thu, 30 Nov 2023 17:15:45 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -6.659
X-Spam-Level:
X-Spam-Status: No, score=-6.659 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, HEADER_FROM_DIFFERENT_DOMAINS=0.249, RCVD_IN_DNSWL_HI=-5, 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 m95Qv1yLy3Gf; Thu, 30 Nov 2023 17:15:41 -0800 (PST)
Received: from rfcpa.amsl.com (rfcpa.amsl.com [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 2895DC14CE39; Thu, 30 Nov 2023 17:15:41 -0800 (PST)
Received: by rfcpa.amsl.com (Postfix, from userid 499) id 20A5F139096A; Thu, 30 Nov 2023 17:15:41 -0800 (PST)
To: ietf-announce@ietf.org, rfc-dist@rfc-editor.org
From: rfc-editor@rfc-editor.org
Cc: rfc-editor@rfc-editor.org
Content-type: text/plain; charset="UTF-8"
Message-Id: <20231201011541.20A5F139096A@rfcpa.amsl.com>
Date: Thu, 30 Nov 2023 17:15:41 -0800
Archived-At: <https://mailarchive.ietf.org/arch/msg/rfc-dist/vYAxY0aRZHY1tpA7wNIYw4XzIdw>
Subject: [rfc-dist] Moved to Historic: RFC 7955 on Management Guidelines for the Locator/ID Separation Protocol (LISP) Endpoint Identifier (EID) Block
X-BeenThere: rfc-dist@rfc-editor.org
X-Mailman-Version: 2.1.39
Precedence: list
List-Id: RFC Announcements <rfc-dist.rfc-editor.org>
List-Unsubscribe: <https://mailman.rfc-editor.org/mailman/options/rfc-dist>, <mailto:rfc-dist-request@rfc-editor.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/rfc-dist/>
List-Post: <mailto:rfc-dist@rfc-editor.org>
List-Help: <mailto:rfc-dist-request@rfc-editor.org?subject=help>
List-Subscribe: <https://mailman.rfc-editor.org/mailman/listinfo/rfc-dist>, <mailto:rfc-dist-request@rfc-editor.org?subject=subscribe>
X-List-Received-Date: Fri, 01 Dec 2023 01:15:45 -0000
RFC 7955 has been reclassified as Historic.
RFC 7955
Title: Management Guidelines for the Locator/ID
Separation Protocol (LISP) Endpoint Identifier (EID)
Block
Author: L. Iannone,
R. Jorgensen,
D. Conrad,
G. Huston
Status: Historic
Stream: IETF
Date: September 2016
Pages: 10
Updates/Obsoletes/SeeAlso: None
I-D Tag: draft-ietf-lisp-eid-block-mgmnt-07.txt
URL: https://www.rfc-editor.org/info/rfc7955
DOI: 10.17487/RFC7955
This document proposes a framework for the management of the Locator/
ID Separation Protocol (LISP) Endpoint Identifier (EID) address
block. The framework described relies on hierarchical distribution
of the address space, granting temporary usage of prefixes of such
space to requesting organizations.
This document is a product of the Locator/ID Separation Protocol Working Group of the IETF.
The status change is documented at:
https://datatracker.ietf.org/doc/status-change-lisp-eid-block-to-historic/
HISTORIC: This memo defines a Historic Document 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