[Hipsec] RFC 5770 on Basic Host Identity Protocol (HIP) Extensions for Traversal of Network Address Translators
rfc-editor@rfc-editor.org Sat, 01 May 2010 00:00 UTC
Return-Path: <wwwrun@rfc-editor.org>
X-Original-To: hipsec@core3.amsl.com
Delivered-To: hipsec@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id DE0A33A693D; Fri, 30 Apr 2010 17:00:40 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.26
X-Spam-Level:
X-Spam-Status: No, score=-2.26 tagged_above=-999 required=5 tests=[AWL=0.340, BAYES_00=-2.599, NO_RELAYS=-0.001]
Received: from mail.ietf.org ([64.170.98.32]) by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id P+aZ7jNu8xeg; Fri, 30 Apr 2010 17:00:40 -0700 (PDT)
Received: from rfc-editor.org (rfc-editor.org [IPv6:2001:1890:1112:1::2f]) by core3.amsl.com (Postfix) with ESMTP id 1C51A3A6A1F; Fri, 30 Apr 2010 17:00:40 -0700 (PDT)
Received: by rfc-editor.org (Postfix, from userid 30) id 9DB35130001; Fri, 30 Apr 2010 17:00:26 -0700 (PDT)
To: ietf-announce@ietf.org, rfc-dist@rfc-editor.org
From: rfc-editor@rfc-editor.org
Message-Id: <20100501000026.9DB35130001@rfc-editor.org>
Date: Fri, 30 Apr 2010 17:00:26 -0700
Cc: hipsec@ietf.org, rfc-editor@rfc-editor.org
Subject: [Hipsec] RFC 5770 on Basic Host Identity Protocol (HIP) Extensions for Traversal of Network Address Translators
X-BeenThere: hipsec@ietf.org
X-Mailman-Version: 2.1.9
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/listinfo/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: Sat, 01 May 2010 00:00:41 -0000
A new Request for Comments is now available in online RFC libraries.
RFC 5770
Title: Basic Host Identity Protocol (HIP)
Extensions for Traversal of Network Address
Translators
Author: M. Komu, T. Henderson,
H. Tschofenig, J. Melen,
A. Keranen, Ed.
Status: Experimental
Stream: IETF
Date: April 2010
Mailbox: miika@iki.fi,
thomas.r.henderson@boeing.com,
Hannes.Tschofenig@gmx.net, jan.melen@ericsson.com,
ari.keranen@ericsson.com
Pages: 34
Characters: 79767
Updates/Obsoletes/SeeAlso: None
I-D Tag: draft-ietf-hip-nat-traversal-09.txt
URL: http://www.rfc-editor.org/rfc/rfc5770.txt
This document specifies extensions to the Host Identity Protocol
(HIP) to facilitate Network Address Translator (NAT) traversal. The
extensions are based on the use of the Interactive Connectivity
Establishment (ICE) methodology to discover a working path between
two end-hosts, and on standard techniques for encapsulating
Encapsulating Security Payload (ESP) packets within the User Datagram
Protocol (UDP). This document also defines elements of a procedure
for NAT traversal, including the optional use of a HIP relay server.
With these extensions HIP is able to work in environments that have
NATs and provides a generic NAT traversal solution to higher-layer
networking applications. 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 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