RFC 8113 on Locator/ID Separation Protocol (LISP): Shared Extension Message & IANA Registry for Packet Type Allocations
rfc-editor@rfc-editor.org Fri, 10 March 2017 02:36 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 52B851294CA for <ietf-announce@ietfa.amsl.com>; Thu, 9 Mar 2017 18:36:37 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -4.203
X-Spam-Level:
X-Spam-Status: No, score=-4.203 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RCVD_IN_DNSWL_MED=-2.3, RP_MATCHES_RCVD=-0.001, SPF_HELO_PASS=-0.001, SPF_PASS=-0.001] 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 2WGRqgPI4okv for <ietf-announce@ietfa.amsl.com>; Thu, 9 Mar 2017 18:36:36 -0800 (PST)
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 EB3901294C3 for <ietf-announce@ietf.org>; Thu, 9 Mar 2017 18:36:32 -0800 (PST)
Received: by rfc-editor.org (Postfix, from userid 30) id D83B6B801A3; Thu, 9 Mar 2017 18:07:20 -0800 (PST)
To: ietf-announce@ietf.org, rfc-dist@rfc-editor.org
Subject: RFC 8113 on Locator/ID Separation Protocol (LISP): Shared Extension Message & IANA Registry for Packet Type Allocations
X-PHP-Originating-Script: 1005:ams_util_lib.php
From: rfc-editor@rfc-editor.org
Message-Id: <20170310020720.D83B6B801A3@rfc-editor.org>
Date: Thu, 09 Mar 2017 18:07:20 -0800
Archived-At: <https://mailarchive.ietf.org/arch/msg/ietf-announce/RPY9dedSRDjIgWPoFdyKhu8rhUY>
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: Fri, 10 Mar 2017 02:36:37 -0000
A new Request for Comments is now available in online RFC libraries.
RFC 8113
Title: Locator/ID Separation Protocol (LISP): Shared
Extension Message & IANA Registry for
Packet Type Allocations
Author: M. Boucadair, C. Jacquenet
Status: Experimental
Stream: IETF
Date: March 2017
Mailbox: mohamed.boucadair@orange.com,
christian.jacquenet@orange.com
Pages: 6
Characters: 10608
Updates: RFC 6830
I-D Tag: draft-ietf-lisp-type-iana-06.txt
URL: https://www.rfc-editor.org/info/rfc8113
DOI: 10.17487/RFC8113
This document specifies a Locator/ID Separation Protocol (LISP)
shared message type for defining future extensions and conducting
experiments without consuming a LISP packet type codepoint for each
extension. It also defines a registry for LISP Packet Type
allocations, thus updating RFC 6830.
This document is a product of the Locator/ID Separation Protocol Working Group of the IETF.
EXPERIMENTAL: This memo defines an Experimental Protocol for the
Internet community. It does not specify an Internet standard of any
kind. Discussion and suggestions for improvement are requested.
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