Re: [Spud] Fwd: New Version Notification for draft-herbert-transports-over-udp-00.txt

Joe Touch <touch@isi.edu> Thu, 19 May 2016 23:30 UTC

Return-Path: <touch@isi.edu>
X-Original-To: spud@ietfa.amsl.com
Delivered-To: spud@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 1475712D0F5 for <spud@ietfa.amsl.com>; Thu, 19 May 2016 16:30:44 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -8.326
X-Spam-Level:
X-Spam-Status: No, score=-8.326 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RCVD_IN_DNSWL_HI=-5, RP_MATCHES_RCVD=-1.426] autolearn=ham autolearn_force=no
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id vmNVWo82Z3r2 for <spud@ietfa.amsl.com>; Thu, 19 May 2016 16:30:43 -0700 (PDT)
Received: from boreas.isi.edu (boreas.isi.edu [128.9.160.161]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 1755012B05C for <spud@ietf.org>; Thu, 19 May 2016 16:30:43 -0700 (PDT)
Received: from [128.9.184.125] ([128.9.184.125]) (authenticated bits=0) by boreas.isi.edu (8.13.8/8.13.8) with ESMTP id u4JNUItx021325 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES128-SHA bits=128 verify=NOT); Thu, 19 May 2016 16:30:19 -0700 (PDT)
To: Tom Herbert <tom@herbertland.com>
References: <20160519175701.17290.47241.idtracker@ietfa.amsl.com> <CALx6S377qRfq7ufRVUx6Yn7ec4=EmK_=FL14PWT_qf4g840mbQ@mail.gmail.com> <20160519185943.GM12994@cisco.com> <CALx6S37qPpKpCT6ZpVQwRWf1XFKESYasOBcz26To9zw0GRyz5Q@mail.gmail.com> <573E31E1.807@isi.edu> <CALx6S35k35rs7f9owPW2zDdcx3tHLL_QE8-nQ6OSDR9=_-m+Gg@mail.gmail.com> <573E3C9F.202@isi.edu> <20160519225859.GV12994@cisco.com> <573E4636.70001@isi.edu> <CALx6S35RxOgrQiQRjkgQrVEA7ZYYRVP0CveHg8-gujbGn-Xjog@mail.gmail.com>
From: Joe Touch <touch@isi.edu>
Message-ID: <573E4C8A.9080902@isi.edu>
Date: Thu, 19 May 2016 16:30:18 -0700
User-Agent: Mozilla/5.0 (Windows NT 6.3; WOW64; rv:38.0) Gecko/20100101 Thunderbird/38.7.2
MIME-Version: 1.0
In-Reply-To: <CALx6S35RxOgrQiQRjkgQrVEA7ZYYRVP0CveHg8-gujbGn-Xjog@mail.gmail.com>
Content-Type: text/plain; charset="windows-1252"
Content-Transfer-Encoding: 7bit
X-ISI-4-43-8-MailScanner: Found to be clean
X-MailScanner-From: touch@isi.edu
Archived-At: <http://mailarchive.ietf.org/arch/msg/spud/FZ7JtxvhDjcaNcHQZ9aoX1ZmE4A>
Cc: Toerless Eckert <eckert@cisco.com>, spud <spud@ietf.org>
Subject: Re: [Spud] Fwd: New Version Notification for draft-herbert-transports-over-udp-00.txt
X-BeenThere: spud@ietf.org
X-Mailman-Version: 2.1.17
Precedence: list
List-Id: Session Protocol Underneath Datagrams <spud.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/spud>, <mailto:spud-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/spud/>
List-Post: <mailto:spud@ietf.org>
List-Help: <mailto:spud-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/spud>, <mailto:spud-request@ietf.org?subject=subscribe>
X-List-Received-Date: Thu, 19 May 2016 23:30:44 -0000


On 5/19/2016 4:23 PM, Tom Herbert wrote:
> ...
>> And there is nothing in the Internet architecture that constrains any of
>> this.
>>
>> Your issue is with the OS, not the Internet.
>>
> But there is the issue issue with Internet. Middleboxes will drop
> packets they don't like for arbitrary reasons. RFC2460 clearly states
> that intermediate devices should not inspect EH and yet they do and
> often drop these packets. As I pointed out we've seen middleboxes that
> drop TCP packets that contain options unknown to it, ones that drop
> SYN packets that contain data (problem with deploying TFO),
> middleboxes that take it upon themselves to rewrite parts of the TCP
> header as they see fit. Heck, before we were using TLS we had
> middleboxes parsing TCP payloads and doing strange things to it like
> inserting their own ads into http (see accord BOF).

Now your issue is with the ISOC for not enforcing compliance, or at
least requiring validation before using terms like "supports Internet
protocols and standards".

However, like problems with OS implementation, these issues cannot be
corrected with technology. All you will accomplish is to "move the
goalposts" and escalate the problems you're already experiencing.

Joe