[Hipsec] I-D Action: draft-ietf-hip-rfc5201-bis-15.txt

internet-drafts@ietf.org Mon, 28 July 2014 11:15 UTC

MIME-Version: 1.0
Content-Type: text/plain; charset="utf-8"
Content-Transfer-Encoding: 7bit
From: internet-drafts@ietf.org
To: i-d-announce@ietf.org
Auto-Submitted: auto-generated
Precedence: bulk
Message-ID: <20140728111521.20762.32404.idtracker@ietfa.amsl.com>
Date: Mon, 28 Jul 2014 04:15:21 -0700
Archived-At: http://mailarchive.ietf.org/arch/msg/hipsec/Gly4Hy5qP0vvY0yW7Fs7d2_dFxE
Cc: hipsec@ietf.org
Subject: [Hipsec] I-D Action: draft-ietf-hip-rfc5201-bis-15.txt

A New Internet-Draft is available from the on-line Internet-Drafts directories.
 This draft is a work item of the Host Identity Protocol Working Group of the IETF.

        Title           : Host Identity Protocol Version 2 (HIPv2)
        Authors         : Robert Moskowitz
                          Tobias Heer
                          Petri Jokela
                          Thomas R. Henderson
	Filename        : draft-ietf-hip-rfc5201-bis-15.txt
	Pages           : 127
	Date            : 2014-07-23

Abstract:
   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 Encapsulated 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.


The IETF datatracker status page for this draft is:
https://datatracker.ietf.org/doc/draft-ietf-hip-rfc5201-bis/

There's also a htmlized version available at:
http://tools.ietf.org/html/draft-ietf-hip-rfc5201-bis-15

A diff from the previous version is available at:
http://www.ietf.org/rfcdiff?url2=draft-ietf-hip-rfc5201-bis-15


Please note that it may take a couple of minutes from the time of submission
until the htmlized version and diff are available at tools.ietf.org.

Internet-Drafts are also available by anonymous FTP at:
ftp://ftp.ietf.org/internet-drafts/

[Hipsec] I-D Action: draft-ietf-hip-rfc5201-bis-1… internet-drafts