Re: [rohc] RFC4996bis

Wesley Eddy <wes@mti-systems.com> Tue, 04 September 2012 04:03 UTC

Return-Path: <wes@mti-systems.com>
X-Original-To: rohc@ietfa.amsl.com
Delivered-To: rohc@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id A6BBF21F85F0 for <rohc@ietfa.amsl.com>; Mon, 3 Sep 2012 21:03:42 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.299
X-Spam-Level:
X-Spam-Status: No, score=-1.299 tagged_above=-999 required=5 tests=[AWL=1.300, BAYES_00=-2.599]
Received: from mail.ietf.org ([64.170.98.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id jfBJFwb7KLcY for <rohc@ietfa.amsl.com>; Mon, 3 Sep 2012 21:03:40 -0700 (PDT)
Received: from omr3.networksolutionsemail.com (omr3.networksolutionsemail.com [205.178.146.53]) by ietfa.amsl.com (Postfix) with ESMTP id 1862721F85E6 for <rohc@ietf.org>; Mon, 3 Sep 2012 21:03:40 -0700 (PDT)
Received: from cm-omr10 (mail.networksolutionsemail.com [205.178.146.50]) by omr3.networksolutionsemail.com (8.14.4/8.14.4) with ESMTP id q8443dNf026375 for <rohc@ietf.org>; Tue, 4 Sep 2012 00:03:39 -0400
Authentication-Results: cm-omr10 smtp.user=wes@mti-systems.com; auth=pass (PLAIN)
X-Authenticated-UID: wes@mti-systems.com
Received: from [69.81.143.209] ([69.81.143.209:12448] helo=[192.168.1.115]) by cm-omr10 (envelope-from <wes@mti-systems.com>) (ecelerity 2.2.2.41 r(31179/31189)) with ESMTPA id ED/1E-08814-B9D75405; Tue, 04 Sep 2012 00:03:39 -0400
Message-ID: <50457D91.80907@mti-systems.com>
Date: Tue, 04 Sep 2012 00:03:29 -0400
From: Wesley Eddy <wes@mti-systems.com>
Organization: MTI Systems
User-Agent: Mozilla/5.0 (Windows NT 6.1; WOW64; rv:15.0) Gecko/20120824 Thunderbird/15.0
MIME-Version: 1.0
To: rohc@ietf.org
References: <50305E66.5000307@mti-systems.com>
In-Reply-To: <50305E66.5000307@mti-systems.com>
Content-Type: text/plain; charset="ISO-8859-1"
Content-Transfer-Encoding: 7bit
Cc: Russ Housley <housley@vigilsec.com>
Subject: Re: [rohc] RFC4996bis
X-BeenThere: rohc@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: Robust Header Compression <rohc.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/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: Tue, 04 Sep 2012 04:03:42 -0000

We haven't seen any responses to this query.  This is a reminder nudge
in case people have been on vacation, or otherwise slow to respond.
Currently, this question is the only thing holding the 4996bis document
up, so feedback would be appreciated!


On 8/18/2012 11:32 PM, Wesley Eddy wrote:
> As you may be aware, the authors of RFC 4996 have been working
> on an update that's currently held up in the IESG Review based
> on the following DISCUSS comment from Russ:
> 
> """
>   The issue below is the same as the one raised in the Gen-ART Review
>   by Joel Halpern on 16-July-2012.
> 
>   Section 5.2.2.2 on negative acknowledgments includes the following:
>   >
>   > ... unless it has confidence that information sent after the packet
>   > being acknowledged already provides a suitable response ...
>   >
>   This deals with a specific response to the NACK, it is unclear what
>   constitutes confidence.  Other places in this document that refer to
>   gaining confidence provide specific descriptions of how it is gained.
>   The primary methods for gaining confidence are receiving acks or
>   sufficient transmissions.  If all that is meant here is sufficient
>   transmissions, please say so.
> """
> 
> There seems to be disagreement about whether additional text
> would be useful in this regard.
> 
> We'd like to hear from people on this ROHC mailing list who
> either have implemented or might implement this specification
> as to whether or not more clarity is needed here, or if it's
> really not useful or a good idea to add such text.
> 


-- 
Wes Eddy
MTI Systems