[rfc-dist] RFC 4347 on Datagram Transport Layer Security

rfc-editor@rfc-editor.org rfc-editor at rfc-editor.org
Wed Apr 26 15:13:54 PDT 2006


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

        
        RFC 4347

        Title:      Datagram Transport Layer Security 
        Author:     E. Rescorla, N. Modadugu
        Status:     Standards Track
        Date:       April 2006
        Mailbox:    ekr at rtfm.com, 
                    nagendra at cs.stanford.edu
        Pages:      25
        Characters: 56014
        Updates/Obsoletes/SeeAlso:   None

        I-D Tag:    draft-rescorla-dtls-05.txt

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

This document specifies Version 1.0 of the Datagram Transport Layer
Security (DTLS) protocol.  The DTLS protocol provides communications
privacy for datagram protocols.  The protocol allows client/server
applications to communicate in a way that is designed to prevent
eavesdropping, tampering, or message forgery.  The DTLS protocol is
based on the Transport Layer Security (TLS) protocol and provides
equivalent security guarantees.  Datagram semantics of the underlying
transport are preserved by the DTLS protocol.  [STANDARDS TRACK]

This is now a Proposed Standard Protocol.

STANDARDS TRACK: 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
be sent to RFC-DIST-REQUEST at RFC-EDITOR.ORG.

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

...




More information about the rfc-dist mailing list