[Ipsec] RFC 3948 on UDP Encapsulation of IPsec ESP Packets

[[e-mail]]

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


         RFC 3948

         Title:      UDP Encapsulation of IPsec ESP Packets
         Author(s):  A. Huttunen, B. Swander, V. Volpe, L. DiBurro,
                     M. Stenberg
         Status:     Standards Track
         Date:       January 2005
         Mailbox:    [e-mail], [e-mail],
                     [e-mail], [e-mail],
                     [e-mail]
         Pages:      15
         Characters: 30366
         Updates/Obsoletes/SeeAlso:    None

         I-D Tag:    draft-ietf-ipsec-udp-encaps-09.txt

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


This protocol specification defines methods to encapsulate and
decapsulate IP Encapsulating Security Payload (ESP) packets inside
UDP packets for traversing Network Address
Translators.  ESP encapsulation, as defined in this document,
can be used in both IPv4 and IPv6 scenarios.  Whenever negotiated,
encapsulation is used with Internet Key Exchange (IKE).

This document is a product of the 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 [e-mail].  Requests to be
added to or deleted from the RFC-DIST distribution list should
be sent to [e-mail].

Details on obtaining RFCs via FTP or EMAIL may be obtained by sending
an EMAIL message to [e-mail] with the message body
help: ways_to_get_rfcs.  For example:

         To: [e-mail]
         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 [e-mail].  Unless
specifically noted otherwise on the RFC itself, all RFCs are for
unlimited distribution.

Submissions for Requests for Comments should be sent to
[e-mail].  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:[e-mail]?body=RETRIEVE:%20rfc%0D%0ADOC-ID:%20rfc3948>
[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/rfc3948.txt>
_______________________________________________
IETF-Announce mailing list
[e-mail]
https://www1.ietf.org/mailman/listinfo/ietf-announce

_______________________________________________
Ipsec mailing list
[e-mail]
https://www1.ietf.org/mailman/listinfo/ipsec