RFC 7834 on Locator/ID Separation Protocol (LISP) Impact

rfc-editor@rfc-editor.org Sat, 30 April 2016 02:45 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 4612512B042 for <ietf-announce@ietfa.amsl.com>; Fri, 29 Apr 2016 19:45:37 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -107.898
X-Spam-Level:
X-Spam-Status: No, score=-107.898 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RCVD_IN_DNSWL_HI=-5, RP_MATCHES_RCVD=-0.996, 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 A8XvQJX2VQZf for <ietf-announce@ietfa.amsl.com>; Fri, 29 Apr 2016 19:45:35 -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 70B7E12B035 for <ietf-announce@ietf.org>; Fri, 29 Apr 2016 19:45:35 -0700 (PDT)
Received: by rfc-editor.org (Postfix, from userid 30) id 1500B180003; Fri, 29 Apr 2016 19:45:15 -0700 (PDT)
To: ietf-announce@ietf.org, rfc-dist@rfc-editor.org
Subject: RFC 7834 on Locator/ID Separation Protocol (LISP) Impact
X-PHP-Originating-Script: 1005:ams_util_lib.php
From: rfc-editor@rfc-editor.org
Message-Id: <20160430024515.1500B180003@rfc-editor.org>
Date: Fri, 29 Apr 2016 19:45:15 -0700
Archived-At: <http://mailarchive.ietf.org/arch/msg/ietf-announce/wQx76rAecVekTBDN4dZReBSZ-OE>
Cc: rfc-editor@rfc-editor.org
X-BeenThere: ietf-announce@ietf.org
X-Mailman-Version: 2.1.17
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: Sat, 30 Apr 2016 02:45:37 -0000

A new Request for Comments is now available in online RFC libraries.

        
        RFC 7834

        Title:      Locator/ID Separation Protocol (LISP) Impact 
        Author:     D. Saucez, L. Iannone,
                    A. Cabellos, F. Coras
        Status:     Informational
        Stream:     IETF
        Date:       April 2016
        Mailbox:    damien.saucez@inria.fr, 
                    ggx@gigix.net, 
                    acabello@ac.upc.edu,   
                    fcoras@ac.upc.edu
        Pages:      18
        Characters: 43168
        Updates/Obsoletes/SeeAlso:   None

        I-D Tag:    draft-ietf-lisp-impact-05.txt

        URL:        https://www.rfc-editor.org/info/rfc7834

        DOI:        http://dx.doi.org/10.17487/RFC7834

The Locator/ID Separation Protocol (LISP) aims to improve the
Internet routing scalability properties by leveraging three
principles: address role separation, encapsulation, and mapping.  In
this document, based on implementation work, deployment experiences,
and theoretical studies, we discuss the impact that the deployment of
LISP can have on both the routing infrastructure and the end user.

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