Re: [tcpm] urgent data draft (draft-gont-tcpm-urgent-data-01.txt)

Joe Touch <touch@ISI.EDU> Tue, 23 June 2009 03:24 UTC

Return-Path: <touch@ISI.EDU>
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 128B63A6B5C for <tcpm@core3.amsl.com>; Mon, 22 Jun 2009 20:24:07 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.599
X-Spam-Level:
X-Spam-Status: No, score=-2.599 tagged_above=-999 required=5 tests=[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 F-m3inbXLRyh for <tcpm@core3.amsl.com>; Mon, 22 Jun 2009 20:24:06 -0700 (PDT)
Received: from vapor.isi.edu (vapor.isi.edu [128.9.64.64]) by core3.amsl.com (Postfix) with ESMTP id 0042B3A69BA for <tcpm@ietf.org>; Mon, 22 Jun 2009 20:23:45 -0700 (PDT)
Received: from [75.222.253.162] (162.sub-75-222-253.myvzw.com [75.222.253.162]) by vapor.isi.edu (8.13.8/8.13.8) with ESMTP id n5N3MrTb008163; Mon, 22 Jun 2009 20:22:55 -0700 (PDT)
Message-ID: <4A404A83.8030100@isi.edu>
Date: Mon, 22 Jun 2009 20:22:43 -0700
From: Joe Touch <touch@ISI.EDU>
User-Agent: Thunderbird 2.0.0.21 (Windows/20090302)
MIME-Version: 1.0
To: Fernando Gont <fernando.gont.laptop.win@gmail.com>
References: <4A12C9C9.9060404@gont.com.ar> <FB06CDDD-8388-448B-8092-151E5533705F@weston.borman.com> <4A30E355.1040704@erg.abdn.ac.uk> <4A3FC1C2.7060407@isi.edu> <4A4020D5.30104@gont.com.ar>
In-Reply-To: <4A4020D5.30104@gont.com.ar>
X-Enigmail-Version: 0.95.7
Content-Type: text/plain; charset=ISO-8859-1
Content-Transfer-Encoding: 7bit
X-ISI-4-43-8-MailScanner: Found to be clean
X-MailScanner-From: touch@isi.edu
Cc: tcpm-chairs@tools.ietf.org, David Borman <dab@weston.borman.com>, tcpm@ietf.org
Subject: Re: [tcpm] urgent data draft (draft-gont-tcpm-urgent-data-01.txt)
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, 23 Jun 2009 03:24:07 -0000

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1



Fernando Gont wrote:
> Joe Touch wrote:
> 
>> I'm wondering about #2. It's worth noting that implementations don't
>> follow the specs, but I'm getting increasingly concerned about
>> continuing to publish docs that say "implementations don't follow spec"
>> without actually either saying "and the spec is hereby changed" or "and
>> implementations are noncompliant and should be fixed".
> 
> Joe, you had agreed with #2 at the meeting we had in Minneapolis. What
> changed since then?
>
> P.S.: As there is no practical difference between "points to the last
> byte of urgent data" vs. "points to the byte following the last byte of
> urgent data", and since all implementations do the later, it does make
> sense to change the specs. You had agreed with this reasoning at MPLS.
> -- I'm now puzzled.

I didn't see in Gorry's note anything about saying we were changing the
specs. As I said, I don't really care whether we change the specs or
declare the implementation incorrect in general. If we've already agreed
that this will be a standards track update to 1122, that's fine (I just
didn't see it mentioned in Gorry's note).

In general, we should always *try* to take a stand when implementations
differ from the standard. This looks like a case where that's possible,
so I was just noting that we should do so.

Joe
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.9 (MingW32)
Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org

iEYEARECAAYFAkpASoMACgkQE5f5cImnZrt3UwCgvnSomiCSCXERCtF5BavhcDEG
KIMAnRzVnyNIK6o6XmBtqRQGsfDyrX3x
=mFkN
-----END PGP SIGNATURE-----