Re: [MEDIACTRL] ISSUE 11 - 5. Handling of the 'Seq' header is not clearly specified

Eric Burger <eburger@standardstrack.com> Mon, 19 July 2010 21:15 UTC

Return-Path: <eburger@standardstrack.com>
X-Original-To: mediactrl@core3.amsl.com
Delivered-To: mediactrl@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id 71A7E3A695E for <mediactrl@core3.amsl.com>; Mon, 19 Jul 2010 14:15:50 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.08
X-Spam-Level:
X-Spam-Status: No, score=-2.08 tagged_above=-999 required=5 tests=[AWL=0.519, BAYES_00=-2.599]
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 Gs20lv9gIlLO for <mediactrl@core3.amsl.com>; Mon, 19 Jul 2010 14:15:49 -0700 (PDT)
Received: from gs19.inmotionhosting.com (gs19.inmotionhosting.com [66.117.3.189]) by core3.amsl.com (Postfix) with ESMTP id 9A9763A68D5 for <mediactrl@ietf.org>; Mon, 19 Jul 2010 14:15:49 -0700 (PDT)
Received: from ip68-100-199-8.dc.dc.cox.net ([68.100.199.8] helo=[192.168.15.185]) by gs19.inmotionhosting.com with esmtpsa (TLSv1:AES128-SHA:128) (Exim 4.69) (envelope-from <eburger@standardstrack.com>) id 1Oaxfy-0003QN-Nc; Mon, 19 Jul 2010 14:15:03 -0700
Mime-Version: 1.0 (Apple Message framework v1081)
Content-Type: text/plain; charset="us-ascii"
From: Eric Burger <eburger@standardstrack.com>
In-Reply-To: <4C34D800.1020507@ns-technologies.com>
Date: Mon, 19 Jul 2010 17:16:02 -0400
Content-Transfer-Encoding: quoted-printable
Message-Id: <FB9BE9D3-6362-450F-BB6B-1AC0C2CE1EFF@standardstrack.com>
References: <4C34D800.1020507@ns-technologies.com>
To: Chris Boulton <chris@ns-technologies.com>
X-Mailer: Apple Mail (2.1081)
X-AntiAbuse: This header was added to track abuse, please include it with any abuse report
X-AntiAbuse: Primary Hostname - gs19.inmotionhosting.com
X-AntiAbuse: Original Domain - ietf.org
X-AntiAbuse: Originator/Caller UID/GID - [47 12] / [47 12]
X-AntiAbuse: Sender Address Domain - standardstrack.com
X-Source:
X-Source-Args:
X-Source-Dir:
Cc: Saint-Andre Peter <stpeter@stpeter.im>, mediactrl@ietf.org
Subject: Re: [MEDIACTRL] ISSUE 11 - 5. Handling of the 'Seq' header is not clearly specified
X-BeenThere: mediactrl@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: Media Control WG Discussion List <mediactrl.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/mediactrl>, <mailto:mediactrl-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/mediactrl>
List-Post: <mailto:mediactrl@ietf.org>
List-Help: <mailto:mediactrl-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/mediactrl>, <mailto:mediactrl-request@ietf.org?subject=subscribe>
X-List-Received-Date: Mon, 19 Jul 2010 21:15:50 -0000

I vote BARF.

The only other option is to ignore.  That does not sound like a protocol to me.

On Jul 7, 2010, at 3:39 PM, Chris Boulton wrote:

> Hi All,
> 
> As part of our IESG review the following has been identified:
> 
> The text in
> Section 6.3.2 states that the 'Seq' header MUST be incremented by 1, but
> does not state whether an entity receiving a message with a 'Seq' header
> that is more than 1 larger than the previous header value needs to
> return an error.
> 
> 
> Group input is required on what to do in this situation.  One proposal would be to return an error and consider the extended transaction terminated.
> 
> Chris.
> 
> -- 
> Chris Boulton
> CTO & Co-founder
> NS-Technologies
> m: +44.7876.476681
> _______________________________________________
> MEDIACTRL mailing list
> MEDIACTRL@ietf.org
> https://www.ietf.org/mailman/listinfo/mediactrl
> Supplemental Web Site:
> http://www.standardstrack.com/ietf/mediactrl