One document matched: draft-ietf-avt-crtp-05.txt

Differences from draft-ietf-avt-crtp-04.txt

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


        RFC 2508: 

        Title:	    Compressing IP/UDP/RTP Headers for Low-Speed
		    Serial Links
	Author(s):  S. Casner, V. Jacobson
	Status:     Proposed Standard
	Date:       February 1999
        Mailbox:    casner@cisco.com, van@cisco.com
	Pages:      24
        Characters: 60474
        Updates/Obsoletes/See Also: None    
        I-D Tag:    draft-ietf-avt-crtp-05.txt

        URL:        ftp://ftp.isi.edu/in-notes/rfc2508.txt


This document describes a method for compressing the headers of
IP/UDP/RTP datagrams to reduce overhead on low-speed serial links.  In
many cases, all three headers can be compressed to 2-4 bytes.

This document is a product of the Audio/Video Transport 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 Alegre Ramos
USC/Information Sciences Institute