Subject: [Hipsec] RFC 6028 on Host Identity Protocol (HIP) Multi-Hop Routing Extension

From: [email-masked]
Date: Tue, 19 Oct 2010 07:55:36 -0700 (PDT)

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

        RFC 6028

        Title:      Host Identity Protocol (HIP) Multi-Hop 
                    Routing Extension 
        Author:     G. Camarillo, A. Keranen
        Status:     Experimental
        Stream:     IETF
        Date:       October 2010
        Mailbox:    [email-masked], 
                    [email-masked]
        Pages:      10
        Characters: 21571
        Updates/Obsoletes/SeeAlso:   None

        I-D Tag:    draft-ietf-hip-via-03.txt

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

This document specifies two extensions to the Host Identity Protocol
(HIP) to implement multi-hop routing.  The first extension allows 
implementing source routing in HIP.  That is, a node sending a HIP packet 
can define a set of nodes that the HIP packet should traverse.  The second 
extension allows a HIP packet to carry and record the list of nodes that 
forwarded it.  This document 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-Announce and rfc-dist lists.
To subscribe or unsubscribe, see
  http://www.ietf.org/mailman/listinfo/ietf-announce
  http://mailman.rfc-editor.org/mailman/listinfo/rfc-dist

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

Requests for special distribution should be addressed to either the
author of the RFC in question, or to [email-masked].  Unless
specifically noted otherwise on the RFC itself, all RFCs are for
unlimited distribution.

The RFC Editor Team
Association Management Solutions, LLC