[rfc-dist] RFC 5201 on Host Identity Protocol

rfc-editor@rfc-editor.org rfc-editor at rfc-editor.org
Fri Apr 18 16:03:14 PDT 2008


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

        
        RFC 5201

        Title:      Host Identity Protocol 
        Author:     R. Moskowitz, P. Nikander,
                    P. Jokela, Ed., T. Henderson
        Status:     Experimental
        Date:       April 2008
        Mailbox:    rgm at icsalabs.com, 
                    pekka.nikander at nomadiclab.com, 
                    petri.jokela at nomadiclab.com,
                    thomas.r.henderson at boeing.com
        Pages:      104
        Characters: 240492
        Updates/Obsoletes/SeeAlso:   None

        I-D Tag:    draft-ietf-hip-base-10.txt

        URL:        http://www.rfc-editor.org/rfc/rfc5201.txt

This memo 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 Sigma-compliant 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 memo defines an Experimental 
Protocol for the Internet community.

This document is a product of the Host Identity 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 list and the RFC-DIST list.
Requests to be added to or deleted from the IETF distribution list
should be sent to IETF-REQUEST at IETF.ORG.  Requests to be
added to or deleted from the RFC-DIST distribution list should
be sent to RFC-DIST-REQUEST at RFC-EDITOR.ORG.

Details on obtaining RFCs via FTP or EMAIL may be obtained by sending
an EMAIL message to rfc-info at RFC-EDITOR.ORG with the message body 

help: ways_to_get_rfcs. For example:

        To: rfc-info at RFC-EDITOR.ORG
        Subject: getting rfcs

        help: ways_to_get_rfcs

Requests for special distribution should be addressed to either the
author of the RFC in question, or to RFC-Manager at RFC-EDITOR.ORG.  Unless
specifically noted otherwise on the RFC itself, all RFCs are for
unlimited distribution.

Submissions for Requests for Comments should be sent to
RFC-EDITOR at RFC-EDITOR.ORG.  Please consult RFC 2223, Instructions to RFC
Authors, for further information.


The RFC Editor Team
USC/Information Sciences Institute

...




More information about the rfc-dist mailing list