IETF Logo Mail Archive

Re: [rohc] New ROHC Milesstones.

"Ghyslain Pelletier" <ghyslain.pelletier@ericsson.com> Thu, 10 September 2009 10:02 UTC

Return-Path: <ghyslain.pelletier@ericsson.com>
X-Original-To: rohc@core3.amsl.com
Delivered-To: rohc@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id 5EB623A69F2 for <rohc@core3.amsl.com>; Thu, 10 Sep 2009 03:02:13 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -4.249
X-Spam-Level:
X-Spam-Status: No, score=-4.249 tagged_above=-999 required=5 tests=[AWL=-2.000, BAYES_00=-2.599, HELO_EQ_SE=0.35]
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 U9dg77zr1X+d for <rohc@core3.amsl.com>; Thu, 10 Sep 2009 03:02:12 -0700 (PDT)
Received: from mailgw5.ericsson.se (mailgw5.ericsson.se [193.180.251.36]) by core3.amsl.com (Postfix) with ESMTP id 3CD9A3A68F7 for <rohc@ietf.org>; Thu, 10 Sep 2009 03:02:12 -0700 (PDT)
X-AuditID: c1b4fb24-b7c01ae00000498b-09-4aa8cb233c68
Received: from esealmw128.eemea.ericsson.se (Unknown_Domain [153.88.253.125]) by mailgw5.ericsson.se (Symantec Brightmail Gateway) with SMTP id 07.61.18827.32BC8AA4; Thu, 10 Sep 2009 11:47:15 +0200 (CEST)
Received: from esealmw109.eemea.ericsson.se ([153.88.200.2]) by esealmw128.eemea.ericsson.se with Microsoft SMTPSVC(6.0.3790.3959); Thu, 10 Sep 2009 11:45:50 +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
Date: Thu, 10 Sep 2009 11:45:49 +0200
Message-ID: <130EBB38279E9847BAAAE0B8F9905F8C01CC832F@esealmw109.eemea.ericsson.se>
In-Reply-To: <FA75D17D-8CDE-4F20-9EBB-1BF884260737@tzi.org>
X-MS-Has-Attach:
X-MS-TNEF-Correlator:
Thread-Topic: [rohc] New ROHC Milesstones.
Thread-Index: Acox9haNo0UP7SiIReKAkr70hQvGGgABGQww
References: <4AA8BA43.9030405@effnet.com> <FA75D17D-8CDE-4F20-9EBB-1BF884260737@tzi.org>
From: Ghyslain Pelletier <ghyslain.pelletier@ericsson.com>
To: Carsten Bormann <cabo@tzi.org>, Carl Knutsson <carl.knutsson@effnet.com>
X-OriginalArrivalTime: 10 Sep 2009 09:45:51.0023 (UTC) FILETIME=[7B64B3F0:01CA31FB]
X-Brightmail-Tracker: AAAAAA==
Cc: rohc@ietf.org
Subject: Re: [rohc] New ROHC Milesstones.
X-BeenThere: rohc@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: Robust Header Compression <rohc.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/rohc>, <mailto:rohc-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/rohc>
List-Post: <mailto:rohc@ietf.org>
List-Help: <mailto:rohc-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/rohc>, <mailto:rohc-request@ietf.org?subject=subscribe>
X-List-Received-Date: Thu, 10 Sep 2009 10:02:13 -0000

Hello Carsten, others,

Given earlier discussions on this topic, my recollection is that there
was no agreement to move this as a working group draft. The reasons for
this was the lack of motivations, requirements or interest in pursuing
this work. Furthermore, this would introduce additional complexity to
our protocol, and the proposed solution has not been reviewed
technically. 

> There are no new problems being solved, so much is true.
> But they are solved in a different way

Given the admitted lack of a real problem to address, new solutions
appear unnecessary and not worth-while the effort. Further, I do not
believe that getting around some suspected IPRs (to possibly fall into
other IPRs) is a typical motivation for specifying new profiles.

Cheers,

///Ghyslain



-----Original Message-----
From: rohc-bounces@ietf.org [mailto:rohc-bounces@ietf.org] On Behalf Of
Carsten Bormann
Sent: den 10 september 2009 11:03
To: Carl Knutsson
Cc: rohc@ietf.org
Subject: Re: [rohc] New ROHC Milesstones.


On Sep 10, 2009, at 10:35, Carl Knutsson wrote:

> Feb 2007 - ROHC encapsulation profile(s) for IPHC/CRTP/eCRTP submitted
>           to IESG for publication as Proposed Standard

I wrote a draft for that,

http://tools.ietf.org/html/draft-bormann-rohc-avt-crtp-profile-00

As far as I know, this is technically complete and could be submitted to
WGLC.

> =This was added before I started as a chair and it is not completely 
> clear to me what the consensus is for this item. I can't really see 
> what these new legacy profiles solve that can't be solved by existing 
> profiles.

There are no new problems being solved, so much is true.
But they are solved in a different way, and possibly with different IPR
considerations, based on existing IETF standards documents.
I can't speak to the IPR considerations (and I would not want to discuss
them on the WG list), but I've heard that some people are interested in
them in the hallway.

Gruesse, Carsten

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

v2.23.0 | Report a Bug | By Email