[Hipsec] I-D Action: draft-ietf-hip-rfc5201-bis-17.txt
internet-drafts@ietf.org Fri, 05 September 2014 18:26 UTC
Return-Path: <internet-drafts@ietf.org>
X-Original-To: hipsec@ietfa.amsl.com
Delivered-To: hipsec@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 301651A6EF2; Fri, 5 Sep 2014 11:26:00 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.9
X-Spam-Level:
X-Spam-Status: No, score=-1.9 tagged_above=-999 required=5 tests=[BAYES_00=-1.9] autolearn=ham
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 73AbKBuWtAcn; Fri, 5 Sep 2014 11:25:58 -0700 (PDT)
Received: from ietfa.amsl.com (localhost [IPv6:::1]) by ietfa.amsl.com (Postfix) with ESMTP id CFCA31A03F4; Fri, 5 Sep 2014 11:25:58 -0700 (PDT)
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
X-Test-IDTracker: no
X-IETF-IDTracker: 5.6.2.p6
Auto-Submitted: auto-generated
Precedence: bulk
Message-ID: <20140905182558.7340.5516.idtracker@ietfa.amsl.com>
Date: Fri, 05 Sep 2014 11:25:58 -0700
Archived-At: http://mailarchive.ietf.org/arch/msg/hipsec/mRucBpT6fuOwguFOScSmypeJh3U
Cc: hipsec@ietf.org
Subject: [Hipsec] I-D Action: draft-ietf-hip-rfc5201-bis-17.txt
X-BeenThere: hipsec@ietf.org
X-Mailman-Version: 2.1.15
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: Fri, 05 Sep 2014 18:26:00 -0000
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-17.txt Pages : 128 Date : 2014-09-05 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-17 A diff from the previous version is available at: http://www.ietf.org/rfcdiff?url2=draft-ietf-hip-rfc5201-bis-17 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
- [Hipsec] RFC5201-bis and RFC5202-bis status Tom Henderson
- Re: [Hipsec] RFC5201-bis and RFC5202-bis status Ted Lemon
- Re: [Hipsec] RFC5201-bis and RFC5202-bis status Tom Henderson
- Re: [Hipsec] RFC5201-bis and RFC5202-bis status Tom Taylor
- Re: [Hipsec] RFC5201-bis and RFC5202-bis status Gonzalo Camarillo
- Re: [Hipsec] RFC5201-bis and RFC5202-bis status Tom Henderson
- Re: [Hipsec] RFC5201-bis and RFC5202-bis status Jari Arkko
- Re: [Hipsec] RFC5201-bis and RFC5202-bis status Jari Arkko
- Re: [Hipsec] RFC5201-bis and RFC5202-bis status Miika Komu
- Re: [Hipsec] RFC5201-bis and RFC5202-bis status Tom Henderson
- Re: [Hipsec] RFC5201-bis and RFC5202-bis status Ted Lemon
- Re: [Hipsec] RFC5201-bis and RFC5202-bis status Gonzalo Camarillo