Re: [rohc] Empty CSRC list issue in IR packet.

Ghyslain Pelletier <Ghyslain.Pelletier@ericsson.com> Fri, 29 August 2003 11:30 UTC

Received: from optimus.ietf.org (ietf.org [132.151.1.19] (may be forged)) by ietf.org (8.9.1a/8.9.1a) with ESMTP id HAA12987 for <rohc-archive@odin.ietf.org>; Fri, 29 Aug 2003 07:30:10 -0400 (EDT)
Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org) by optimus.ietf.org with esmtp (Exim 4.20) id 19sfxm-00051w-Ug for rohc-archive@odin.ietf.org; Fri, 29 Aug 2003 05:54:39 -0400
Received: (from exim@localhost) by www1.ietf.org (8.12.8/8.12.8/Submit) id h7T9sc6i019327 for rohc-archive@odin.ietf.org; Fri, 29 Aug 2003 05:54:38 -0400
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org) by optimus.ietf.org with esmtp (Exim 4.20) id 19sfa8-0003V4-Jg for rohc-web-archive@optimus.ietf.org; Fri, 29 Aug 2003 05:30:12 -0400
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id FAA02915 for <rohc-web-archive@ietf.org>; Fri, 29 Aug 2003 05:30:04 -0400 (EDT)
Received: from ietf-mx ([132.151.6.1]) by ietf-mx with esmtp (Exim 4.12) id 19sfa4-00067f-00 for rohc-web-archive@ietf.org; Fri, 29 Aug 2003 05:30:08 -0400
Received: from ietf.org ([132.151.1.19] helo=optimus.ietf.org) by ietf-mx with esmtp (Exim 4.12) id 19sfa4-00067c-00 for rohc-web-archive@ietf.org; Fri, 29 Aug 2003 05:30:08 -0400
Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org) by optimus.ietf.org with esmtp (Exim 4.20) id 19sfPI-0002z5-RS; Fri, 29 Aug 2003 05:19:00 -0400
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org) by optimus.ietf.org with esmtp (Exim 4.20) id 19s0u0-0004gg-8C for rohc@optimus.ietf.org; Wed, 27 Aug 2003 10:04:00 -0400
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id KAA28484 for <rohc@ietf.org>; Wed, 27 Aug 2003 10:03:54 -0400 (EDT)
Received: from ietf-mx ([132.151.6.1]) by ietf-mx with esmtp (Exim 4.12) id 19s0tx-0006KH-00 for rohc@ietf.org; Wed, 27 Aug 2003 10:03:58 -0400
Received: from penguin-ext.wise.edt.ericsson.se ([193.180.251.47]) by ietf-mx with esmtp (Exim 4.12) id 19s0tx-0006KE-00 for rohc@ietf.org; Wed, 27 Aug 2003 10:03:57 -0400
Received: from esealnt613.al.sw.ericsson.se ([153.88.254.125]) by penguin-ext.wise.edt.ericsson.se (8.12.9/8.12.9/WIREfire-1.7) with ESMTP id h7RE3s31020659; Wed, 27 Aug 2003 16:03:55 +0200 (MEST)
Received: from lms001.lu.erisoft.se ([150.132.144.19]) by esealnt613.al.sw.ericsson.se with SMTP (Microsoft Exchange Internet Mail Service Version 5.5.2655.55) id Q9L3DB48; Wed, 27 Aug 2003 16:03:54 +0200
Received: by lms001.lu.erisoft.se id QAA08685; Wed, 27 Aug 2003 16:03:55 +0200 (MET DST)
Message-ID: <3F4CBAC0.443A0D0B@ericsson.com>
Date: Wed, 27 Aug 2003 16:05:52 +0200
X-Sybari-Space: 00000000 00000000 00000000 00000000
From: Ghyslain Pelletier <Ghyslain.Pelletier@ericsson.com>
Organization: Ericsson Erisoft AB, Ericsson Research Corporate Unit
X-Mailer: Mozilla 4.79 [en] (Windows NT 5.0; U)
X-Accept-Language: en
MIME-Version: 1.0
To: Remi Pelland <remi.pelland@octasic.com>
CC: "'rohc@ietf.org'" <rohc@ietf.org>
Subject: Re: [rohc] Empty CSRC list issue in IR packet.
References: <F54085DA4E90D511B80B00B0D0D007D26BA79F@EXCHSVR>
Content-Type: text/plain; charset="iso-8859-1"
Content-Transfer-Encoding: quoted-printable
X-MIME-Autoconverted: from 8bit to quoted-printable by penguin-ext.wise.edt.ericsson.se id h7RE3s31020659
Content-Transfer-Encoding: quoted-printable
Sender: rohc-admin@ietf.org
Errors-To: rohc-admin@ietf.org
X-BeenThere: rohc@ietf.org
X-Mailman-Version: 2.0.12
Precedence: bulk
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/rohc>, <mailto:rohc-request@ietf.org?subject=unsubscribe>
List-Id: Robust Header Compression <rohc.ietf.org>
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>
Content-Transfer-Encoding: quoted-printable
Content-Transfer-Encoding: quoted-printable

Hi all,

Does the following summarizes accurately the consensus that Remi is
looking after?

1) Section 4.3.1 and 4.3.2 of the implementer's guide clarifies
   rfc3095, and they should remain as they are.
   
   The text is clear, bring a clarification inline with the
   standard, and this has been interop tested. These two sections
   therefore do not need to be modified. In summary, when an empty
   CSRC list is present, an empty generic list (1-2 octets) must be
   inserted.

   Tommy's mail would then represent the consensus on this:
  
http://www1.ietf.org/mail-archive/working-groups/rohc/current/msg01654.html

2) Section 4.3.3 of the implementer's guide should be removed.

   Section 4.3.3 of the implementer's guide is a "deviation" from the
   standard that proposes an improvement that would remove the need to
   send an empty generic list (1-2 octets) in the presence of an empty
   CSRC list. It is a deviation in the sense that the generic CSRC list
   in rfc3095 is of variable lenght but is not optional (must be
   present), while the text in 4.3.3 is keeping it of variable length
   but makes it optional.

   Section 4.3.3 should thus be removed from the implementer's guide,
   but could later be considered as a proposed improvement when
   bringing rfc3095 to draft standard if the profile gets updated at
   the same time.

   Abigail's mail would then represent the consensus on this:
  
http://www1.ietf.org/mail-archive/working-groups/rohc/current/msg01655.html

Is my understanding of the conclusions/consensus correct?
If so, then we will update the Implementer's guide accordingly.

/Ghyslain

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

Ericsson AB, Laboratoriegränd 11
Box 920, S-97128 Luleå, SWEDEN
Phone : +46 (0) 920 20 24 32 
Mobile: +46 (0) 706 09 27 73
Ghyslain.Pelletier@ericsson.com
http://www.ericsson.com

I have a new mail address: Ghyslain.Pelletier@ericsson.com
My old e-mail address will function until 2004-06-01.
Please change my address in your personal address book.

Remi Pelland wrote:
> 
> Hi,
> 
> A couple of weeks ago, there was a discussion about a section in the latest
> implementer's guide that corrects RFC 3095 with regards to the handling of
> empty CSRC lists: section 5.7.7.6 of the RFC says that an empty generic list
> is inserted, while section 4.3.3. of the implementer's guide modifies the
> RFC by saying that no generic list should be present.
> 
> There seemed to be a concensus among those involved in the discussion to
> follow the RFC since this is how interoperability was tested.  That's fine
> and I do not want to restart the discussion on this.
> 
> Now, it has been a couple of weeks and there hasn't been any final
> conclusion on this issue (i.e. officially stating that the RFC method should
> be used, anouncing the associated correction to the implementer's guide,
> etc...).
> 
> Based on the concensus that existed, I don't think there's a problem for
> those who currently receive mailing list messages.  However, it seems to me
> like there's a risk that future implementations may use either methods,
> leading to interoperability problems.
> 
> Thanks,
> Remi.
> 
> _______________________________________________
> 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