RE: [rohc] Liaison request from 3GPP2

"Ghyslain Pelletier \(LU/EAB\)" <ghyslain.pelletier@ericsson.com> Fri, 26 May 2006 19:30 UTC

Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com) by megatron.ietf.org with esmtp (Exim 4.43) id 1Fji0u-0000fv-7X; Fri, 26 May 2006 15:30:24 -0400
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org) by megatron.ietf.org with esmtp (Exim 4.43) id 1Fji0s-0000fp-UW for rohc@ietf.org; Fri, 26 May 2006 15:30:22 -0400
Received: from mailgw3.ericsson.se ([193.180.251.60]) by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1Fji0j-0001SN-7U for rohc@ietf.org; Fri, 26 May 2006 15:30:22 -0400
Received: from esealmw129.eemea.ericsson.se (unknown [153.88.254.120]) by mailgw3.ericsson.se (Symantec Mail Security) with ESMTP id 057CB4F0003; Fri, 26 May 2006 21:29:38 +0200 (CEST)
Received: from esealmw127.eemea.ericsson.se ([153.88.254.171]) by esealmw129.eemea.ericsson.se with Microsoft SMTPSVC(6.0.3790.1830); Fri, 26 May 2006 21:29:37 +0200
Received: from esealmw109.eemea.ericsson.se ([153.88.200.2]) by esealmw127.eemea.ericsson.se with Microsoft SMTPSVC(6.0.3790.1830); Fri, 26 May 2006 21:29:37 +0200
X-MimeOLE: Produced By Microsoft Exchange V6.5
Content-class: urn:content-classes:message
MIME-Version: 1.0
Content-Type: text/plain; charset="iso-8859-1"
Content-Transfer-Encoding: quoted-printable
Subject: RE: [rohc] Liaison request from 3GPP2
Date: Fri, 26 May 2006 21:29:32 +0200
Message-ID: <026F8EEDAD2C4342A993203088C1FC0502EC0AF5@esealmw109.eemea.ericsson.se>
X-MS-Has-Attach:
X-MS-TNEF-Correlator:
Thread-Topic: [rohc] Liaison request from 3GPP2
Thread-Index: AcaA9M5fRsFf6trwSmmGcR5zhnb5KQAA+AoA
From: "Ghyslain Pelletier (LU/EAB)" <ghyslain.pelletier@ericsson.com>
To: Thomas Narten <narten@us.ibm.com>, rohc@ietf.org
X-OriginalArrivalTime: 26 May 2006 19:29:37.0171 (UTC) FILETIME=[B9A97E30:01C680FA]
X-Brightmail-Tracker: AAAAAA==
X-Spam-Score: 0.0 (/)
X-Scan-Signature: 2857c5c041d6c02d7181d602c22822c8
Cc: AC Mahendran <mahendra@qualcomm.com>
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

Thomas, RoHCers,

The output that 3GPP2 expect from this WG in the liaison is actually three documents:

  - draft-ietf-rohc-rfc3095bis-improvements (to be published as Informational)
  - draft-ietf-rohc-rfc3095bis-framework (to be published as PS)
  - RoHCv2 profiles (to be published as PS, does not exist publicly yet)

So, there is a whole draft missing here as you can see. I've already notified Rohit Kapoor (which I believe is involved in 3GPP2 std?) that I will submit a draft describing the updated RoHC profiles (RoHCv2 profiles) by the cut-off date for initial submissions. I have already notified the WG chair of the upcoming draft as well. Look for draft-pelletier-rohcv2-profiles-00.txt by mid-June. I've already updating my priority list with this one on top.

Status:
 
>  - draft-ietf-rohc-rfc3095bis-framework

This draft specifies the RoHC framework. It does not include any update to profiles. In my opinion, it is already ready for a wglc, however there is no point in having a wglc until its companion draft describing the updated profiles (RoHCv2 profiles) is also ready for wlgc. Currently as I wrote above, this draft only exists on my computer, i.e. it is yet to be available as a draft individual submission, but I'm a couple of week for making it available.

>  - draft-ietf-rohc-rfc3095bis-improvements

This draft is meant to be published as informational. It contains suggested improvement for the updated RoHC profiles (RoHCv2 profiles) as agreed on the mailing list. However, it is of not really of any help to 3GPP2 as it only describes what should be done for the RoHCv2 profiles. It is some kind of "requirements" document
 
> Are they close to being finished? Are there known outstanding
> issues that need to be addressed?

I think there has been only limited discussions of the framework and the improvements draft on the mailing list, nothing at a physical meeting. The RoHC WG hasn't met at last IETF. I am not sure yet if there will be a WG meeting in Montreal, but I think it may be good to have one to discuss how to move forward on this issue. Should we push the chairman to request a meeting slot in Montreal? Any opinions? Anyone interested in meeting physically to discuss how to move this work forward once I've sent in the base draft for the updated profiles?

Regards,

/Ghyslain

--
 Ghyslain Pelletier, Dipl. Ing.
 Wireless IP Optimizations
 Ericsson Research, Corporate Unit

 Ericsson AB, Laboratoriegränd 11
 Box 920, S-97128 Luleå, SWEDEN
 Phone : +46 (0)  8 404 29 43
 Mobile: +46 (0) 70 264 83 14
 Ghyslain.Pelletier at ericsson.com
 http://www.ericsson.com

-----------------------------------
 The opinions expressed in this
 message are my personal opinions.
 These opinions are not
 necessarily those of my employer,
 unless stated otherwise.
-----------------------------------


Thomas Narten wrote:
> 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


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