[Hipsec] RFC 7401 on Host Identity Protocol Version 2 (HIPv2)

rfc-editor@rfc-editor.org Thu, 09 April 2015 20:45 UTC

Return-Path: <wwwrun@rfc-editor.org>
X-Original-To: hipsec@ietfa.amsl.com
Delivered-To: hipsec@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com []) by ietfa.amsl.com (Postfix) with ESMTP id 7C5551B3232; Thu, 9 Apr 2015 13:45:52 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -101.912
X-Spam-Status: No, score=-101.912 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, SPF_HELO_PASS=-0.001, SPF_PASS=-0.001, T_RP_MATCHES_RCVD=-0.01, USER_IN_WHITELIST=-100] autolearn=ham
Received: from mail.ietf.org ([]) by localhost (ietfa.amsl.com []) (amavisd-new, port 10024) with ESMTP id sQMv5gMnxGD0; Thu, 9 Apr 2015 13:45:47 -0700 (PDT)
Received: from rfc-editor.org (rfc-editor.org [IPv6:2001:1900:3001:11::31]) by ietfa.amsl.com (Postfix) with ESMTP id 55DC01B3238; Thu, 9 Apr 2015 13:44:36 -0700 (PDT)
Received: by rfc-editor.org (Postfix, from userid 30) id 4776418046C; Thu, 9 Apr 2015 13:43:58 -0700 (PDT)
To: ietf-announce@ietf.org, rfc-dist@rfc-editor.org
X-PHP-Originating-Script: 6000:ams_util_lib.php
From: rfc-editor@rfc-editor.org
Message-Id: <20150409204358.4776418046C@rfc-editor.org>
Date: Thu, 9 Apr 2015 13:43:58 -0700 (PDT)
Archived-At: <http://mailarchive.ietf.org/arch/msg/hipsec/t733d_TteOA2GwzCUuDbvpltKsQ>
Cc: drafts-update-ref@iana.org, hipsec@ietf.org, rfc-editor@rfc-editor.org
Subject: [Hipsec] RFC 7401 on Host Identity Protocol Version 2 (HIPv2)
X-BeenThere: hipsec@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: "This is the official IETF Mailing List for the HIP Working Group." <hipsec.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/hipsec>, <mailto:hipsec-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/hipsec/>
List-Post: <mailto:hipsec@ietf.org>
List-Help: <mailto:hipsec-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/hipsec>, <mailto:hipsec-request@ietf.org?subject=subscribe>
X-List-Received-Date: Thu, 09 Apr 2015 20:45:52 -0000

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

        RFC 7401

        Title:      Host Identity Protocol Version 2 (HIPv2) 
        Author:     R. Moskowitz, Ed.,
                    T. Heer,
                    P. Jokela,
                    T. Henderson
        Status:     Standards Track
        Stream:     IETF
        Date:       April 2015
        Mailbox:    rgm@labs.htt-consult.com, 
        Pages:      128
        Characters: 309319
        Obsoletes:  RFC 5201

        I-D Tag:    draft-ietf-hip-rfc5201-bis-20.txt

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

This document specifies the details of the Host Identity Protocol
(HIP).  HIP allows consenting hosts to securely establish and
maintain shared IP-layer state, allowing separation of the identifier
and locator roles of IP addresses, thereby enabling continuity of
communications across IP address changes.  HIP is based on a
Diffie-Hellman key exchange, using public key identifiers from a new
Host Identity namespace for mutual peer authentication.  The protocol
is designed to be resistant to denial-of-service (DoS) and
man-in-the-middle (MitM) attacks.  When used together with another
suitable security protocol, such as the Encapsulating Security
Payload (ESP), it provides integrity protection and optional
encryption for upper-layer protocols, such as TCP and UDP.

This document obsoletes RFC 5201 and addresses the concerns raised by
the IESG, particularly that of crypto agility.  It also incorporates
lessons learned from the implementations of RFC 5201.

This document is a product of the Host Identity Protocol Working Group of the IETF.

This is now a Proposed Standard.

STANDARDS TRACK: This document specifies an Internet Standards Track
protocol for the Internet community, and requests discussion and suggestions
for improvements.  Please refer to the current edition of the Official
Internet Protocol Standards (https://www.rfc-editor.org/standards) for the 
standardization state and status of this protocol.  Distribution of this 
memo is unlimited.

This announcement is sent to the IETF-Announce and rfc-dist lists.
To subscribe or unsubscribe, see

For searching the RFC series, see https://www.rfc-editor.org/search
For downloading RFCs, see https://www.rfc-editor.org/rfc.html

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