[prev in list] [next in list] [prev in thread] [next in thread] 

List:       ipsec
Subject:    [Ipsec] RFC 3947 on Negotiation of NAT-Traversal in the IKE
From:       rfc-editor () rfc-editor ! org
Date:       2005-01-06 1:54:53
Message-ID: p06200773be024ad47548 () [10 ! 20 ! 30 ! 249]
[Download RAW message or body]

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@safenet-inc.com,
                     Ari.Huttunen@F-Secure.com, briansw@microsoft.com,
                     vvolpe@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@IETF.ORG.  Requests to be
added to or deleted from the RFC-DIST distribution list should
be sent to RFC-DIST-REQUEST@RFC-EDITOR.ORG.

Details on obtaining RFCs via FTP or EMAIL may be obtained by sending
an EMAIL message to rfc-info@RFC-EDITOR.ORG with the message body
help: ways_to_get_rfcs.  For example:

         To: rfc-info@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@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@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.


[The following attachment must be fetched by mail. Command-click the 
URL below and send the resulting message to get the attachment.]
<mailto:RFC-INFO@RFC-EDITOR.ORG?body=RETRIEVE:%20rfc%0D%0ADOC-ID:%20rfc3947>
[The following attachment must be fetched by ftp.  Command-click the 
URL below to ask your ftp client to fetch it.]
<ftp://ftp.isi.edu/in-notes/rfc3947.txt>
_______________________________________________
IETF-Announce mailing list
IETF-Announce@ietf.org
https://www1.ietf.org/mailman/listinfo/ietf-announce

_______________________________________________
Ipsec mailing list
Ipsec@ietf.org
https://www1.ietf.org/mailman/listinfo/ipsec
[prev in list] [next in list] [prev in thread] [next in thread]