RFC 5795 on The RObust Header Compression (ROHC) Framework
rfc-editor@rfc-editor.org Fri, 19 March 2010 02:18 UTC
Return-Path: <wwwrun@rfc-editor.org>
X-Original-To: ietf-announce@core3.amsl.com
Delivered-To: ietf-announce@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id 28BB13A6CB1; Thu, 18 Mar 2010 19:18:41 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.194
X-Spam-Level:
X-Spam-Status: No, score=-1.194 tagged_above=-999 required=5 tests=[AWL=-0.936, BAYES_00=-2.599, DNS_FROM_OPENWHOIS=1.13, HELO_MISMATCH_ORG=0.611, J_CHICKENPOX_93=0.6]
Received: from mail.ietf.org ([64.170.98.32]) by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id EorTME6r++Te; Thu, 18 Mar 2010 19:18:40 -0700 (PDT)
Received: from rfc-editor.org (rfcpa [64.170.98.47]) by core3.amsl.com (Postfix) with ESMTP id B4A913A6CAF; Thu, 18 Mar 2010 19:18:39 -0700 (PDT)
Received: by rfc-editor.org (Postfix, from userid 30) id 4A59CE0778; Thu, 18 Mar 2010 19:18:52 -0700 (PDT)
To: ietf-announce@ietf.org, rfc-dist@rfc-editor.org
Subject: RFC 5795 on The RObust Header Compression (ROHC) Framework
From: rfc-editor@rfc-editor.org
Message-Id: <20100319021852.4A59CE0778@rfc-editor.org>
Date: Thu, 18 Mar 2010 19:18:52 -0700
Cc: rohc@ietf.org, rfc-editor@rfc-editor.org
X-BeenThere: ietf-announce@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: "IETF announcement list. No discussions." <ietf-announce.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/ietf-announce>, <mailto:ietf-announce-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf-announce>
List-Post: <mailto:ietf-announce@ietf.org>
List-Help: <mailto:ietf-announce-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf-announce>, <mailto:ietf-announce-request@ietf.org?subject=subscribe>
X-List-Received-Date: Fri, 19 Mar 2010 02:18:41 -0000
A new Request for Comments is now available in online RFC libraries.
RFC 5795
Title: The RObust Header Compression (ROHC)
Framework
Author: K. Sandlund, G. Pelletier,
L-E. Jonsson
Status: Standards Track
Date: March 2010
Mailbox: kristofer.sandlund@ericsson.com,
ghyslain.pelletier@ericsson.com,
lars-erik@lejonsson.com
Pages: 41
Characters: 89850
Obsoletes: RFC4995
I-D Tag: draft-ietf-rohc-rfc4995bis-03.txt
URL: http://www.rfc-editor.org/rfc/rfc5795.txt
The Robust Header Compression (ROHC) protocol provides an efficient,
flexible, and future-proof header compression concept. It is
designed to operate efficiently and robustly over various link
technologies with different characteristics.
The ROHC framework, along with a set of compression profiles, was
initially defined in RFC 3095. To improve and simplify the ROHC
specifications, this document explicitly defines the ROHC framework
and the profile for uncompressed separately. More specifically, the
definition of the framework does not modify or update the definition
of the framework specified by RFC 3095.
This specification obsoletes RFC 4995. It fixes one interoperability
issue that was erroneously introduced in RFC 4995, and adds some
minor clarifications. [STANDARDS TRACK]
This document is a product of the Robust Header Compression Working Group of the IETF.
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-Announce and rfc-dist lists.
To subscribe or unsubscribe, see
http://www.ietf.org/mailman/listinfo/ietf-announce
http://mailman.rfc-editor.org/mailman/listinfo/rfc-dist
For searching the RFC series, see http://www.rfc-editor.org/rfcsearch.html.
For downloading RFCs, see http://www.rfc-editor.org/rfc.html.
Requests for special distribution should be addressed to either the
author of the RFC in question, or to rfc-editor@rfc-editor.org. Unless
specifically noted otherwise on the RFC itself, all RFCs are for
unlimited distribution.
The RFC Editor Team
Association Management Solutions, LLC