[rfc-dist] RFC 3947 on Negotiation of NAT-Traversal in the IKE

rfc-editor at rfc-editor.org rfc-editor at rfc-editor.org
Wed Jan 5 17:04:55 PST 2005

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

        RFC 3947

        Title:      Negotiation of NAT-Traversal in the IKE
        Author(s):  T. Kivinen, B. Swander, A. Huttunen, V. Volpe
        Status:     Standards Track
        Date:       January 2005
        Mailbox:    kivinen at safenet-inc.com,
                    Ari.Huttunen at F-Secure.com, briansw at microsoft.com,
                    vvolpe at cisco.com
        Pages:      16
        Characters: 34759
        Updates/Obsoletes/SeeAlso:    None

        I-D Tag:    draft-ietf-ipsec-nat-t-ike-08.txt

        URL:        ftp://ftp.rfc-editor.org/in-notes/rfc3947.txt

This document describes how to detect one or more network address
translation devices (NATs) between IPsec hosts, and how to negotiate
the use of UDP encapsulation of IPsec packets through NAT boxes in
Internet Key Exchange (IKE).

This document is a product of IP Security Protocol Working Group of
the IETF.

This is now a Proposed Standard Protocol.

This document specifies an Internet standards track protocol for
the Internet community, and requests discussion and suggestions
for improvements.  Please refer to the current edition of the
"Internet Official Protocol Standards" (STD 1) for the
standardization state and status of this protocol.  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

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.

Joyce K. Reynolds and Sandy Ginoza
USC/Information Sciences Institute


Below is the data which will enable a MIME compliant Mail Reader 
implementation to automatically retrieve the ASCII version
of the RFCs.
-------------- next part --------------
Skipped content of type multipart/alternative

More information about the rfc-dist mailing list