RFC 3243 on Reqs and Assumptions for 0-byte ROHC RTP
RFC Editor <rfc-ed@ISI.EDU> Wed, 01 May 2002 23:00 UTC
Received: from loki.ietf.org (loki [10.27.2.29]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id TAA16647; Wed, 1 May 2002 19:00:47 -0400 (EDT)
Received: (from adm@localhost) by loki.ietf.org (8.9.1b+Sun/8.9.1) id SAA03052 for ietf-123-outbound.10@ietf.org; Wed, 1 May 2002 18:55:01 -0400 (EDT)
Received: from ietf.org (odin.ietf.org [10.27.2.28]) by loki.ietf.org (8.9.1b+Sun/8.9.1) with ESMTP id SAA02893 for <all-ietf@loki.ietf.org>; Wed, 1 May 2002 18:35:57 -0400 (EDT)
Received: from gamma.isi.edu (gamma.isi.edu [128.9.144.145]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id SAA13036 for <all-ietf@ietf.org>; Wed, 1 May 2002 18:35:49 -0400 (EDT)
Received: from ISI.EDU (jet.isi.edu [128.9.160.87]) by gamma.isi.edu (8.11.6/8.11.2) with ESMTP id g41MZpm13956; Wed, 1 May 2002 15:35:51 -0700 (PDT)
Message-Id: <200205012235.g41MZpm13956@gamma.isi.edu>
To: IETF-Announce:;
Subject: RFC 3243 on Reqs and Assumptions for 0-byte ROHC RTP
Cc: rfc-editor@rfc-editor.org, rohc@CDT.LUTH.SE
Mime-Version: 1.0
Content-Type: Multipart/Mixed; Boundary="NextPart"
Date: Wed, 01 May 2002 15:35:51 -0700
From: RFC Editor <rfc-ed@ISI.EDU>
A new Request for Comments is now available in online RFC libraries. RFC 3243 Title: RObust Header Compression (ROHC): Requirements and Assumptions for 0-byte IP/UDP/RTP Compression Author(s): L-E. Jonsson Status: Informational Date: April 2002 Mailbox: lars-erik.jonsson@ericsson.com Pages: 6 Characters: 12451 Updates/Obsoletes/SeeAlso: None I-D Tag: draft-ietf-rohc-rtp-0-byte-requirements-02.txt URL: ftp://ftp.rfc-editor.org/in-notes/rfc3243.txt This document contains requirements for the 0-byte IP/UDP/RTP (Internet Protocol/User Datagram Protocol/Real-Time Transport Protocol) header compression scheme to be developed by the Robust Header Compression (ROHC) Working Group. It also includes the basic assumptions for the typical link layers over which 0-byte compression may be implemented, and assumptions about its usage in general. This document is a product of the Robust Header Compression Working Group of the IETF. This memo provides information for the Internet community. It does not specify an Internet standard of any kind. 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.