RFC 3828 on The Lightweight User Datagram Protocol (UDP-Lite)

rfc-editor@rfc-editor.org Wed, 14 July 2004 04:17 UTC

Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id AAA11773 for <ietf-announce-archive@ietf.org>; Wed, 14 Jul 2004 00:17:28 -0400 (EDT)
Received: from ietf-mx.ietf.org ([132.151.6.1] helo=ietf-mx) by ietf-mx with esmtp (Exim 4.32) id 1BkbCz-0003po-S4 for ietf-announce-archive@ietf.org; Wed, 14 Jul 2004 00:17:29 -0400
Received: from exim by ietf-mx with spam-scanned (Exim 4.12) id 1BkabS-0005Am-00 for ietf-announce-archive@ietf.org; Tue, 13 Jul 2004 23:38:43 -0400
Received: from megatron.ietf.org ([132.151.6.71]) by ietf-mx with esmtp (Exim 4.12) id 1Bka4t-0007hX-00; Tue, 13 Jul 2004 23:05:03 -0400
Received: from localhost.localdomain ([127.0.0.1] helo=megatron.ietf.org) by megatron.ietf.org with esmtp (Exim 4.32) id 1BkVd9-0004Bo-Jw; Tue, 13 Jul 2004 18:20:07 -0400
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org) by megatron.ietf.org with esmtp (Exim 4.32) id 1BkUPn-0002NC-UF for ietf-announce@megatron.ietf.org; Tue, 13 Jul 2004 17:02:16 -0400
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id RAA17567 for <ietf-announce@ietf.org>; Tue, 13 Jul 2004 17:02:13 -0400 (EDT)
Received: from ietf-mx.ietf.org ([132.151.6.1] helo=ietf-mx) by ietf-mx with esmtp (Exim 4.32) id 1BkUPm-00065e-Di for ietf-announce@ietf.org; Tue, 13 Jul 2004 17:02:14 -0400
Received: from exim by ietf-mx with spam-scanned (Exim 4.12) id 1BkUKB-0004ev-00 for ietf-announce@ietf.org; Tue, 13 Jul 2004 16:56:28 -0400
Received: from boreas.isi.edu ([128.9.160.161]) by ietf-mx with esmtp (Exim 4.12) id 1BkUEK-00031C-00; Tue, 13 Jul 2004 16:50:24 -0400
Received: from ISI.EDU (adma.isi.edu [128.9.160.239]) by boreas.isi.edu (8.11.6p2+0917/8.11.2) with ESMTP id i6DKmrJ23284; Tue, 13 Jul 2004 13:48:53 -0700 (PDT)
Message-Id: <200407132048.i6DKmrJ23284@boreas.isi.edu>
To: ietf-announce@ietf.org
From: rfc-editor@rfc-editor.org
Mime-Version: 1.0
Content-Type: Multipart/Mixed; Boundary="NextPart"
Date: Tue, 13 Jul 2004 13:48:53 -0700
X-ISI-4-30-3-MailScanner: Found to be clean
X-MailScanner-From: rfc-ed@isi.edu
Cc: tsvwg@ietf.org, rfc-editor@rfc-editor.org
Subject: RFC 3828 on The Lightweight User Datagram Protocol (UDP-Lite)
X-BeenThere: ietf-announce@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: ietf-announce.ietf.org
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/ietf-announce>, <mailto:ietf-announce-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:ietf-announce@ietf.org>
List-Help: <mailto:ietf-announce-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/ietf-announce>, <mailto:ietf-announce-request@ietf.org?subject=subscribe>
Sender: ietf-announce-bounces@ietf.org
Errors-To: ietf-announce-bounces@ietf.org
X-Spam-Checker-Version: SpamAssassin 2.60 (1.212-2003-09-23-exp) on ietf-mx.ietf.org
X-Spam-Status: No, hits=-1.4 required=5.0 tests=AWL,MIME_BOUND_NEXTPART, NO_REAL_NAME autolearn=no version=2.60

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


        RFC 3828

        Title:      The Lightweight User Datagram Protocol (UDP-Lite)
        Author(s):  L-A. Larzon, M. Degermark, S. Pink,
                    L-E. Jonsson, Ed., G. Fairhurst, Ed.
        Status:     Standards Track
        Date:       July 2004
        Mailbox:    lln@csee.ltu.se, micke@cs.arizona.edu,
                    steve@cs.arizona.edu,
                    lars-erik.jonsson@ericsson.com,
                    gorry@erg.abdn.ac.uk
        Pages:      12
        Characters: 27193
        Updates/Obsoletes/SeeAlso:    None

        I-D Tag:    draft-ietf-tsvwg-udp-lite-02.txt

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


This document describes the Lightweight User Datagram Protocol
(UDP-Lite), which is similar to the User Datagram Protocol (UDP) (RFC
768), but can also serve applications in error-prone network
environments that prefer to have partially damaged payloads delivered
rather than discarded.  If this feature is not used, UDP-Lite is
semantically identical to UDP.

This document is a product of the Transport Area 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.echo 
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.
ftp://ftp.isi.edu/in-notes/rfc3828.txt"><ftp://ftp.isi.edu/in-notes/rfc3828.txt>
_______________________________________________
IETF-Announce mailing list
IETF-Announce@ietf.org
https://www1.ietf.org/mailman/listinfo/ietf-announce