RE: [rohc] Liaison request from 3GPP2

"Ghyslain Pelletier \(LU/EAB\)" <ghyslain.pelletier@ericsson.com> Wed, 31 May 2006 14:32 UTC

Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com) by megatron.ietf.org with esmtp (Exim 4.43) id 1FlRk2-0000oB-7y; Wed, 31 May 2006 10:32:10 -0400
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org) by megatron.ietf.org with esmtp (Exim 4.43) id 1FlRk0-0000o1-7n for rohc@ietf.org; Wed, 31 May 2006 10:32:08 -0400
Received: from mailgw3.ericsson.se ([193.180.251.60]) by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1FlRjy-0000P6-Nj for rohc@ietf.org; Wed, 31 May 2006 10:32:08 -0400
Received: from esealmw128.eemea.ericsson.se (unknown [153.88.254.121]) by mailgw3.ericsson.se (Symantec Mail Security) with ESMTP id 94EA64F007F; Wed, 31 May 2006 16:31:55 +0200 (CEST)
Received: from esealmw128.eemea.ericsson.se ([153.88.254.176]) by esealmw128.eemea.ericsson.se with Microsoft SMTPSVC(6.0.3790.1830); Wed, 31 May 2006 16:31:55 +0200
Received: from esealmw109.eemea.ericsson.se ([153.88.200.2]) by esealmw128.eemea.ericsson.se with Microsoft SMTPSVC(6.0.3790.1830); Wed, 31 May 2006 16:31:55 +0200
X-MimeOLE: Produced By Microsoft Exchange V6.5
Content-class: urn:content-classes:message
MIME-Version: 1.0
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: quoted-printable
Subject: RE: [rohc] Liaison request from 3GPP2
Date: Wed, 31 May 2006 16:31:54 +0200
Message-ID: <026F8EEDAD2C4342A993203088C1FC0502F59B57@esealmw109.eemea.ericsson.se>
X-MS-Has-Attach:
X-MS-TNEF-Correlator:
Thread-Topic: [rohc] Liaison request from 3GPP2
Thread-Index: AcaA9M5fRsFf6trwSmmGcR5zhnb5KQAA+AoAAPDxpPAAAHJkMA==
From: "Ghyslain Pelletier (LU/EAB)" <ghyslain.pelletier@ericsson.com>
To: "Lars-Erik Jonsson (LU/EAB)" <lars-erik.jonsson@ericsson.com>, Thomas Narten <narten@us.ibm.com>, rohc@ietf.org
X-OriginalArrivalTime: 31 May 2006 14:31:55.0024 (UTC) FILETIME=[F70EE900:01C684BE]
X-Brightmail-Tracker: AAAAAA==
X-Spam-Score: 0.0 (/)
X-Scan-Signature: e1b0e72ff1bbd457ceef31828f216a86
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

Lars-Erik,

> Ghyslain, for alignment with the WG draft name, which will be:
>    draft-ietf-rohc-rfc3095bis-profiles-00.txt,
> please name the upcoming initial individual draft similarily:
>    draft-pelletier-rohc-rfc3095bis-profiles-00.txt

I don't really agree with this, as the RoHCv2 profiles are not meant to
replace the already existing profiles, but rather to create an updated
variants without replacing the current profiles. In other words, new
profile numbers should be issued by IANA. So I don't see the RoHCv2
profiles draft having the "bis" in its name.

For the framework draft, it is already borderline but less of an issue
as it is compatible with RFC3095, but I am not sure it is really a "bis"
either, unless a bis can update and replace only a part of an existing
specification.

/Ghyslain

Lars-Erik Jonsson (LU/EAB) wrote:
> Thomas, Ghyslain, others,
> 
> (filling in some details in the excellent summary from Ghyslain)
> 
>> 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.
> 
> That is excellent, I hope we can then get discussions going
> on this draft, and the intent would then be to turn this
> document into the envisioned WG draft.
> 
> Ghyslain, for alignment with the WG draft name, which will be:
>    draft-ietf-rohc-rfc3095bis-profiles-00.txt,
> please name the upcoming initial individual draft similarily:
>    draft-pelletier-rohc-rfc3095bis-profiles-00.txt
> 
> 
>> 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.
> 
> Well, the improvements draft has been discussed
> point-by-point before it even became a separate draft
> (discussions were carried out while it was part of
> draft-ietf-rohc-rtp-impl-guide), establishing consensus for
> all items. However, I believe it is reasonable to believe
> some people may have additional ideas to bring for v2, and
> such ideas should then be brought to the mail list. If not,
> the improvements  draft as it currently looks is what
> consitutes the technical direction for the profiles draft.
> 
>> Should we push the chairman to request a meeting slot in Montreal?
>> Any opinions?
> 
> A meeting slot will be requested!
> 
> /L-E


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