Re: [tcpm] draft-ietf-tcpm-urgent-data-06

Jari Arkko <jari.arkko@piuha.net> Tue, 19 October 2010 22:13 UTC

Return-Path: <jari.arkko@piuha.net>
X-Original-To: tcpm@core3.amsl.com
Delivered-To: tcpm@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id DAB8D3A6953 for <tcpm@core3.amsl.com>; Tue, 19 Oct 2010 15:13:16 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -102.449
X-Spam-Level:
X-Spam-Status: No, score=-102.449 tagged_above=-999 required=5 tests=[AWL=0.150, BAYES_00=-2.599, USER_IN_WHITELIST=-100]
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 lP6PoQDqpn3Z for <tcpm@core3.amsl.com>; Tue, 19 Oct 2010 15:13:14 -0700 (PDT)
Received: from p130.piuha.net (p130.piuha.net [IPv6:2001:14b8:400::130]) by core3.amsl.com (Postfix) with ESMTP id C217D3A68E3 for <tcpm@ietf.org>; Tue, 19 Oct 2010 15:13:13 -0700 (PDT)
Received: from localhost (localhost [127.0.0.1]) by p130.piuha.net (Postfix) with ESMTP id BEBBB2CC31; Wed, 20 Oct 2010 01:14:44 +0300 (EEST)
X-Virus-Scanned: amavisd-new at piuha.net
Received: from p130.piuha.net ([127.0.0.1]) by localhost (p130.piuha.net [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id ugrUoTX6KItS; Wed, 20 Oct 2010 01:14:44 +0300 (EEST)
Received: from [IPv6:::1] (unknown [IPv6:2001:14b8:400::130]) by p130.piuha.net (Postfix) with ESMTP id B0C9E2CC2F; Wed, 20 Oct 2010 01:14:43 +0300 (EEST)
Message-ID: <4CBE1853.9020502@piuha.net>
Date: Wed, 20 Oct 2010 01:14:43 +0300
From: Jari Arkko <jari.arkko@piuha.net>
User-Agent: Thunderbird 2.0.0.24 (X11/20100411)
MIME-Version: 1.0
To: Joe Touch <touch@isi.edu>
References: <201009301549.RAA14282@TR-Sys.de> <13205C286662DE4387D9AF3AC30EF456B01839E20B@EMBX01-WF.jnpr.net> <31679F6B-0ACA-421F-8131-DA05B764A4A9@nokia.com> <13205C286662DE4387D9AF3AC30EF456B0201C2D1C@EMBX01-WF.jnpr.net> <FCF0200B-A1AF-4902-A110-D7EC08C39FEC@nokia.com> <4CB31ECF.6040307@gont.com.ar>, <1D4E3C6E-B0BF-4CAC-A01E-EC9CDAC14EE0@nokia.com> <C304DB494AC0C04C87C6A6E2FF5603DB481FB1C732@NDJSSCC01.ndc.nasa.gov> <4CB3CCBB.1030400@isi.edu> <675AC39A-0E6D-4014-850B-2A05389577C4@windriver.com> <4CB488F2.1070800@isi.edu> <4CB48DCE.7010606@isi.edu> <4CB8C1CF.1020106@piuha.net> <30410F46-8F64-4988-B6ED-73ECFB7F59E9@windriver.com> <4CB8CC43.8080305@isi.edu> <4CB8CEE1.8070408@piuha.net> <4CBE1739.6040203@isi.edu>
In-Reply-To: <4CBE1739.6040203@isi.edu>
Content-Type: text/plain; charset="ISO-8859-1"; format="flowed"
Content-Transfer-Encoding: 7bit
Cc: "tcpm@ietf.org Extensions" <tcpm@ietf.org>, David Borman <david.borman@windriver.com>, Fernando Gont <fernando@gont.com.ar>
Subject: Re: [tcpm] draft-ietf-tcpm-urgent-data-06
X-BeenThere: tcpm@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: TCP Maintenance and Minor Extensions Working Group <tcpm.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/tcpm>, <mailto:tcpm-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/tcpm>
List-Post: <mailto:tcpm@ietf.org>
List-Help: <mailto:tcpm-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/tcpm>, <mailto:tcpm-request@ietf.org?subject=subscribe>
X-List-Received-Date: Tue, 19 Oct 2010 22:13:17 -0000

Joe, I think I agree with you. I was not planning on holding on to a 
Discuss for that part, however.

Jari

Joe Touch kirjoitti:
>
>
> On 10/15/2010 3:00 PM, Jari Arkko wrote:
>> Joe,
>>
>> Just a quick response on one point:
>>
>>> - based on the note from Jari, I can't tell whether the
>>> doc is recommending SHOULD NOT for new apps or not
>>
>> My text did not change that aspect in any way. The new text is in the
>> introduction and has no keywords. The formal requirement is later in the
>> document. IIRC the current text there says SHOULD NOT for new apps.
>
> Correct. In that case, the note was not responsive to the thread I 
> raised discussing the point that this is a new and substantial change, 
> one that I feel suggests that the title, abstract, and overall 
> structure should be inverted to focus on SHOULD NOT as the key point.
>
> It's hard to understand a doc that basically focuses on a change to 
> the spec, and includes the SHOULD NOT almost parenthetically.
>
> Joe
>