RFC 8061 on Locator/ID Separation Protocol (LISP) Data-Plane Confidentiality

rfc-editor@rfc-editor.org Thu, 02 February 2017 22:31 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 7A3911296C8 for <ietf-announce@ietfa.amsl.com>; Thu, 2 Feb 2017 14:31:59 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -7.401
X-Spam-Level:
X-Spam-Status: No, score=-7.401 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RCVD_IN_DNSWL_MED=-2.3, RP_MATCHES_RCVD=-3.199, 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 jQVYdEFxOjrv for <ietf-announce@ietfa.amsl.com>; Thu, 2 Feb 2017 14:31:56 -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 ACCEC1295FC for <ietf-announce@ietf.org>; Thu, 2 Feb 2017 14:31:56 -0800 (PST)
Received: by rfc-editor.org (Postfix, from userid 30) id 9420AB81A06; Thu, 2 Feb 2017 14:31:56 -0800 (PST)
To: ietf-announce@ietf.org, rfc-dist@rfc-editor.org
Subject: RFC 8061 on Locator/ID Separation Protocol (LISP) Data-Plane Confidentiality
X-PHP-Originating-Script: 1005:ams_util_lib.php
From: rfc-editor@rfc-editor.org
Message-Id: <20170202223156.9420AB81A06@rfc-editor.org>
Date: Thu, 2 Feb 2017 14:31:56 -0800 (PST)
Archived-At: <https://mailarchive.ietf.org/arch/msg/ietf-announce/KuRSz6n1KFchYj73VBoD37C4j44>
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: Thu, 02 Feb 2017 22:31:59 -0000

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

        
        RFC 8061

        Title:      Locator/ID Separation Protocol (LISP) Data-Plane 
                    Confidentiality 
        Author:     D. Farinacci, B. Weis
        Status:     Experimental
        Stream:     IETF
        Date:       February 2017
        Mailbox:    farinacci@gmail.com, 
                    bew@cisco.com
        Pages:      18
        Characters: 39345
        Updates/Obsoletes/SeeAlso:   None

        I-D Tag:    draft-ietf-lisp-crypto-10.txt

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

        DOI:        10.17487/RFC8061

This document describes a mechanism for encrypting traffic
encapsulated using the Locator/ID Separation Protocol (LISP).  The
design describes how key exchange is achieved using existing LISP
control-plane mechanisms as well as how to secure the LISP data plane
from third-party surveillance attacks.

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