RFC 7955 on Management Guidelines for the Locator/ID Separation Protocol (LISP) Endpoint Identifier (EID) Block
rfc-editor@rfc-editor.org Wed, 21 September 2016 23:17 UTC
Return-Path: <wwwrun@rfc-editor.org>
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 3754412D16C for <ietf-announce@ietfa.amsl.com>; Wed, 21 Sep 2016 16:17:04 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -104.918
X-Spam-Level:
X-Spam-Status: No, score=-104.918 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RCVD_IN_DNSWL_LOW=-0.7, RP_MATCHES_RCVD=-2.316, SPF_HELO_PASS=-0.001, SPF_PASS=-0.001, USER_IN_WHITELIST=-100] autolearn=ham autolearn_force=no
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id xRzX3M9qzME4 for <ietf-announce@ietfa.amsl.com>; Wed, 21 Sep 2016 16:17:01 -0700 (PDT)
Received: from rfc-editor.org (rfc-editor.org [4.31.198.49]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 2868312BF4C for <ietf-announce@ietf.org>; Wed, 21 Sep 2016 16:16:48 -0700 (PDT)
Received: by rfc-editor.org (Postfix, from userid 30) id 23432B80FCF; Wed, 21 Sep 2016 16:16:48 -0700 (PDT)
To: ietf-announce@ietf.org, rfc-dist@rfc-editor.org
Subject: RFC 7955 on Management Guidelines for the Locator/ID Separation Protocol (LISP) Endpoint Identifier (EID) Block
X-PHP-Originating-Script: 1005:ams_util_lib.php
From: rfc-editor@rfc-editor.org
Message-Id: <20160921231648.23432B80FCF@rfc-editor.org>
Date: Wed, 21 Sep 2016 16:16:48 -0700
Archived-At: <https://mailarchive.ietf.org/arch/msg/ietf-announce/dd8phfLEaY43cz0GBDAFF8FXqyY>
Cc: drafts-update-ref@iana.org, rfc-editor@rfc-editor.org
X-BeenThere: ietf-announce@ietf.org
X-Mailman-Version: 2.1.17
Precedence: list
Reply-To: ietf@ietf.org
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: Wed, 21 Sep 2016 23:17:04 -0000
A new Request for Comments is now available in online RFC libraries.
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: Informational
Stream: IETF
Date: September 2016
Mailbox: ggx@gigix.net,
rogerj@gmail.com,
drc@virtualized.org,
gih@apnic.net
Pages: 10
Characters: 19607
Updates/Obsoletes/SeeAlso: None
I-D Tag: draft-ietf-lisp-eid-block-mgmnt-07.txt
URL: https://www.rfc-editor.org/info/rfc7955
DOI: http://dx.doi.org/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.
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