IETF Logo Mail Archive

[rohc] Liaison request from 3GPP2

Thomas Narten <narten@us.ibm.com> Fri, 26 May 2006 18:46 UTC

Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com) by megatron.ietf.org with esmtp (Exim 4.43) id 1FjhJy-0004e1-AI; Fri, 26 May 2006 14:46:02 -0400
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org) by megatron.ietf.org with esmtp (Exim 4.43) id 1FjhJw-0004dg-Mh for rohc@ietf.org; Fri, 26 May 2006 14:46:00 -0400
Received: from e36.co.us.ibm.com ([32.97.110.154]) by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1FjhJv-0004HP-DK for rohc@ietf.org; Fri, 26 May 2006 14:46:00 -0400
Received: from westrelay02.boulder.ibm.com (westrelay02.boulder.ibm.com [9.17.195.11]) by e36.co.us.ibm.com (8.12.11.20060308/8.12.11) with ESMTP id k4QIjwPr013860 for <rohc@ietf.org>; Fri, 26 May 2006 14:45:58 -0400
Received: from d03av03.boulder.ibm.com (d03av03.boulder.ibm.com [9.17.195.169]) by westrelay02.boulder.ibm.com (8.12.10/NCO/VER6.8) with ESMTP id k4QIjwl6271154 for <rohc@ietf.org>; Fri, 26 May 2006 12:45:58 -0600
Received: from d03av03.boulder.ibm.com (loopback [127.0.0.1]) by d03av03.boulder.ibm.com (8.12.11.20060308/8.13.3) with ESMTP id k4QIjwtg023802 for <rohc@ietf.org>; Fri, 26 May 2006 12:45:58 -0600
Received: from rotala.raleigh.ibm.com (rotala.raleigh.ibm.com [9.27.151.17]) by d03av03.boulder.ibm.com (8.12.11.20060308/8.12.11) with ESMTP id k4QIjwtn023772; Fri, 26 May 2006 12:45:58 -0600
Received: from rotala.raleigh.ibm.com (rotala.raleigh.ibm.com [127.0.0.1]) by rotala.raleigh.ibm.com (8.13.1/8.12.5) with ESMTP id k4QIjvcN023278; Fri, 26 May 2006 14:45:57 -0400
Message-Id: <200605261845.k4QIjvcN023278@rotala.raleigh.ibm.com>
To: rohc@ietf.org
Date: Fri, 26 May 2006 14:45:57 -0400
From: Thomas Narten <narten@us.ibm.com>
X-Spam-Score: 0.0 (/)
X-Scan-Signature: 8abaac9e10c826e8252866cbe6766464
Cc: AC Mahendran <mahendra@qualcomm.com>
Subject: [rohc] Liaison request from 3GPP2
X-BeenThere: rohc@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: Robust Header Compression <rohc.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/rohc>, <mailto:rohc-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:rohc@ietf.org>
List-Help: <mailto:rohc-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/rohc>, <mailto:rohc-request@ietf.org?subject=subscribe>
Errors-To: rohc-bounces@ietf.org

ROHC WG:

3GPP2 has sent the following request to the ROHC WG.

> The RoHC WG is currently working on revising the IP/UDP/RTP profiles
> defined in RFC 3095 to add support for reordering among other
> things. Reordering support in RoHC is extremely important for 3GPP2,
> since packets can arrive out-of-order due to handoffs as well as ARQ
> techniques at the physical and higher layers. Based on the RoHC WG
> charter, the WG is expected to produce a couple of related documents ­
> RoHC framework draft and Revised IP/UDP/RTP profiles draft.

> Both these documents are essential for 3GPP2. We would greatly
> appreciate it if you could provide us the target completion dates of
> the above drafts. Also, we request that the work on these documents
> be completed as soon as possible.

(It doesn't appear the WG has discussed these, as I find no record in
the WG archives. Also, I can't tell of ROHC met in Dallas. There was a
slot for ROHC on the published agenda, but the proceedings say the WG
didn't meet.)

Can someone please report on the status of the following two
documents:

 - draft-ietf-rohc-rfc3095bis-framework
 - draft-ietf-rohc-rfc3095bis-improvements

Are they close to being finished? Are there known outstanding issues
that need to be addressed? 
 
Thomas

_______________________________________________
Rohc mailing list
Rohc@ietf.org
https://www1.ietf.org/mailman/listinfo/rohc

v2.23.0 | Report a Bug | By Email