Re: A problem with RFC 6465's Uniform Format for Extension Headers
Mark ZZZ Smith <markzzzsmith@yahoo.com.au> Sat, 08 February 2014 00:06 UTC
Return-Path: <markzzzsmith@yahoo.com.au>
X-Original-To: ipv6@ietfa.amsl.com
Delivered-To: ipv6@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id EE51E1AD7C1 for <ipv6@ietfa.amsl.com>; Fri, 7 Feb 2014 16:06:31 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: 1.347
X-Spam-Level: *
X-Spam-Status: No, score=1.347 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, FH_RANDOM_SURE=0.499, FREEMAIL_FROM=0.001, FROM_LOCAL_NOVOWEL=0.5, HK_RANDOM_ENVFROM=0.001, HK_RANDOM_FROM=0.999, RCVD_IN_BL_SPAMCOP_NET=1.347, RCVD_IN_DNSWL_NONE=-0.0001] autolearn=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 dgKcOV8NpsNa for <ipv6@ietfa.amsl.com>; Fri, 7 Feb 2014 16:06:30 -0800 (PST)
Received: from nm9-vm0.bullet.mail.bf1.yahoo.com (nm9-vm0.bullet.mail.bf1.yahoo.com [98.139.213.154]) by ietfa.amsl.com (Postfix) with ESMTP id AAB9C1AD79D for <6man@ietf.org>; Fri, 7 Feb 2014 16:06:30 -0800 (PST)
Received: from [66.196.81.170] by nm9.bullet.mail.bf1.yahoo.com with NNFMP; 08 Feb 2014 00:06:30 -0000
Received: from [98.139.212.248] by tm16.bullet.mail.bf1.yahoo.com with NNFMP; 08 Feb 2014 00:06:30 -0000
Received: from [127.0.0.1] by omp1057.mail.bf1.yahoo.com with NNFMP; 08 Feb 2014 00:06:30 -0000
X-Yahoo-Newman-Property: ymail-3
X-Yahoo-Newman-Id: 404329.87187.bm@omp1057.mail.bf1.yahoo.com
Received: (qmail 87982 invoked by uid 60001); 8 Feb 2014 00:06:30 -0000
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=yahoo.com.au; s=s1024; t=1391817990; bh=3Y80cbn6RHuA9k8Gx2kue6LyyJKWoKe+2R4rAJHNgFM=; h=X-YMail-OSG:Received:X-Rocket-MIMEInfo:X-Mailer:References:Message-ID:Date:From:Reply-To:Subject:To:Cc:In-Reply-To:MIME-Version:Content-Type:Content-Transfer-Encoding; b=s2FiMGfawj3Ta7btaUbyN9WbJiFVzMPiNHnOGH5CtCZie6krZlcZBlNJXhe9O0pTX0vlhwAUErEASh0kQBfALJtF4zKAw2CZR0/YJanI6ur7FeJs5qgegY49HJ0yOFCZG5zSdntpVYOINyLn0Zg4OpnEMjXDdtwPo2V2n03pLXk=
DomainKey-Signature: a=rsa-sha1; q=dns; c=nofws; s=s1024; d=yahoo.com.au; h=X-YMail-OSG:Received:X-Rocket-MIMEInfo:X-Mailer:References:Message-ID:Date:From:Reply-To:Subject:To:Cc:In-Reply-To:MIME-Version:Content-Type:Content-Transfer-Encoding; b=0Vjx222bQ3P9Rn4V+XH97THWyLmjKkWRPte7p+00MU4jx3nCRgY7r4BAstcRlWUGVwq4cxlCVJ/ZVMw5uBHtuHa6xHJ7EH2u1LTuZh/Mx2uAFK7BFnEHAfJxzAPqPk42HHMNGjNv7a5w+XoV4rBVZ1o7yIQcCwbnEIHvS7cEpNI=;
X-YMail-OSG: wCWeEAIVM1mQzj4JxSF1DzSRaF.l0MBchQgcuerj4FfT51D ud6gHdXApFfKtHjyAGrGH3N_vTQUk2fKr42XvVTtpb4gmNjXq_tly.ddTleb NZVNauOj9umR4a4Z.dTJb4F7Rmn__BnkC.d5PYi8wZpUYW0h3jf8Y_p.mUTm chQ3byll5oDJVUjysJo8_Rjq5TD6tq3ctl2dBdP8AnkyYCLspdSNqtdUL66J rf48ohd47DGkOgygWzGl0rb2oFseRcXgMSkilhNfSS27WLPTTgvUN4oz97B7 xPT9OyxX0sgvh9NrTS7TuSb_Z9veQPWMftsgHtOBfBkCHli07zyzsOG1s0CR AkAJagX32fjBWTsGiOY6FEWCFdzWzVsTOyFS3TffgzzHccEkDoytmvXePtae fZ26croTJbH1rjoMgzqqxGUW5_edzCunYHW6sDn_keHE00FO_uVqTpmlewVJ PSefLHBMfeyGHm59nom7ubmY45U3o25o90KM_HStJE.hDCp7EI5YgwwWwjRp nuPEb_RPN9MToy8D_5Si6EKDdbHJsCbnbL07v6gkgjCONMWFOqAcrI9UBEWR UqpwTSlEoGa.zeyDBunUS9Ro7SorZlE9SXFvbdbQh29NK8weB_l7arV5hx6D yaGtJpesfRkCbkLb.T0x1ip04qxxfETXU3lBiT4YBjmGPwXJKYw4mrXwNtgJ g1AYcJOQ.eUsWbpmsgtAXF1ffCWHtdSmcK7z1x3lRTQ--
Received: from [150.101.221.237] by web162204.mail.bf1.yahoo.com via HTTP; Fri, 07 Feb 2014 16:06:29 PST
X-Rocket-MIMEInfo: 002.001, CgoKCi0tLS0tIE9yaWdpbmFsIE1lc3NhZ2UgLS0tLS0KPiBGcm9tOiBGZXJuYW5kbyBHb250IDxmZ29udEBzaTZuZXR3b3Jrcy5jb20.Cj4gVG86IE9sZSBUcm9hbiA8b3Ryb2FuQGVtcGxveWVlcy5vcmc.Cj4gQ2M6IFRob21hcyBOYXJ0ZW4gPG5hcnRlbkB1cy5pYm0uY29tPjsgIjZtYW5AaWV0Zi5vcmciIDw2bWFuQGlldGYub3JnPjsgQy4gTS4gSGVhcmQgPGhlYXJkQHBvYm94LmNvbT47IFN1cmVzaCBLcmlzaG5hbiA8c3VyZXNoLmtyaXNobmFuQGVyaWNzc29uLmNvbT47IFRpbSBDaG93biA8dGpjQGVjcy4BMAEBAQE-
X-Mailer: YahooMailWebService/0.8.175.632
References: <20140130230740.25350.9524.idtracker@ietfa.amsl.com> <52EAF63A.7050108@si6networks.com> <52F1B8CE.4070803@ericsson.com> <52F1BD1F.2080007@si6networks.com> <m3k3d82zz6.wl%narten@us.ibm.com> <52F383A0.7030002@si6networks.com> <m28utnbwj9.wl%randy@psg.com> <52F44A73.3000609@si6networks.com> <86BA587E-A7F8-47B9-AC74-98D3DB9A7E46@employees.org> <52F4DDC7.8070606@si6networks.com>
Message-ID: <1391817989.71306.YahooMailNeo@web162204.mail.bf1.yahoo.com>
Date: Fri, 07 Feb 2014 16:06:29 -0800
From: Mark ZZZ Smith <markzzzsmith@yahoo.com.au>
Subject: Re: A problem with RFC 6465's Uniform Format for Extension Headers
To: Fernando Gont <fgont@si6networks.com>, Ole Troan <otroan@employees.org>
In-Reply-To: <52F4DDC7.8070606@si6networks.com>
MIME-Version: 1.0
Content-Type: text/plain; charset="iso-8859-1"
Content-Transfer-Encoding: quoted-printable
Cc: Thomas Narten <narten@us.ibm.com>, "C. M. Heard" <heard@pobox.com>, Tim Chown <tjc@ecs.soton.ac.uk>, "6man@ietf.org" <6man@ietf.org>, Suresh Krishnan <suresh.krishnan@ericsson.com>
X-BeenThere: ipv6@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
Reply-To: Mark ZZZ Smith <markzzzsmith@yahoo.com.au>
List-Id: "IPv6 Maintenance Working Group \(6man\)" <ipv6.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ipv6>, <mailto:ipv6-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ipv6/>
List-Post: <mailto:ipv6@ietf.org>
List-Help: <mailto:ipv6-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ipv6>, <mailto:ipv6-request@ietf.org?subject=subscribe>
X-List-Received-Date: Sat, 08 Feb 2014 00:06:32 -0000
----- Original Message ----- > From: Fernando Gont <fgont@si6networks.com> > To: Ole Troan <otroan@employees.org> > Cc: Thomas Narten <narten@us.ibm.com>; "6man@ietf.org" <6man@ietf.org>; C. M. Heard <heard@pobox.com>; Suresh Krishnan <suresh.krishnan@ericsson.com>; Tim Chown <tjc@ecs.soton.ac.uk> > Sent: Saturday, 8 February 2014 12:21 AM > Subject: Re: A problem with RFC 6465's Uniform Format for Extension Headers > > Hi, Ole, > > On 02/07/2014 06:05 AM, Ole Troan wrote: >> >>> But to keep hearing that e.g. extensions are expected to work >>> when I'm measuring over 40% of breakage, It seems to boil down to >>> "you, heretic! don't filter these packets!" on one side > and "shut >>> up! you don't know how to run a network" on another. *That* >>> doesn't seem to be the more sane approach to this issue. >> >> I think we have to be careful throwing these numbers about without >> qualifying them. >> >> aren't you in many cases detecting filtering in front of services, >> where the operator has very good control of how their traffic >> should look like? > > Probably, I guess -- I'm in the process of finding out where these > packets are being filtered. > > But widespread filtering of stuff that is supposed to be "ignored if > unsupported" eventually leads to "It's not usable, because if you > try > to, your packets get dropped". > > If, say, tomorrow you come up with this shiny cool new Dst Opt-based > extension for clients, then, from starters, you would have to think of > a back-up plan, because in more than 40% cases your packets would get > dropped just because of that extension. -- that's where we are right now. > End-to-end crypto might the backup plan. I think it might be worth remembering that as per the IETF88 Plenary, end-to-end encryption is the general direction, and that middle boxes less effective/in-effective because of it. So putting a lot of time and effort into facilitating them might be wasted effort. I also think multipathing, to take advantage of smartphone/tablet's multi-homing to the network will also mean middle boxes become less effective/in-effective. IOS 7 is already using MPTCP for Siri for example+. <snip> Regards, Mark. + - http://perso.uclouvain.be/olivier.bonaventure/blog/html/2013/09/18/mptcp.html
- A problem with RFC 6465's Uniform Format for Exte… Fernando Gont
- Re: A problem with RFC 6465's Uniform Format for … Hagen Paul Pfeifer
- Re: A problem with RFC 6465's Uniform Format for … Brian E Carpenter
- Re: A problem with RFC 6465's Uniform Format for … Hagen Paul Pfeifer
- Re: A problem with RFC 6465's Uniform Format for … Brian E Carpenter
- Re: A problem with RFC 6465's Uniform Format for … Jen Linkova
- Re: A problem with RFC 6465's Uniform Format for … Fernando Gont
- Re: A problem with RFC 6465's Uniform Format for … Suresh Krishnan
- Re: A problem with RFC 6465's Uniform Format for … Fernando Gont
- Re: A problem with RFC 6465's Uniform Format for … Thomas Narten
- Re: A problem with RFC 6465's Uniform Format for … Fernando Gont
- Re: A problem with RFC 6465's Uniform Format for … brianjusa
- Re: A problem with RFC 6465's Uniform Format for … Brian E Carpenter
- Re: A problem with RFC 6465's Uniform Format for … Randy Bush
- Re: A problem with RFC 6465's Uniform Format for … Fernando Gont
- Re: A problem with RFC 6465's Uniform Format for … Randy Bush
- Re: A problem with RFC 6465's Uniform Format for … Fernando Gont
- Re: A problem with RFC 6465's Uniform Format for … Karsten Thomann
- Re: A problem with RFC 6465's Uniform Format for … Hagen Paul Pfeifer
- Re: A problem with RFC 6465's Uniform Format for … Brian E Carpenter
- Re: A problem with RFC 6465's Uniform Format for … Mark ZZZ Smith
- Re: A problem with RFC 6465's Uniform Format for … C. M. Heard
- Re: A problem with RFC 6465's Uniform Format for … Brian E Carpenter
- Re: A problem with RFC 6465's Uniform Format for … Fernando Gont
- Re: A problem with RFC 6465's Uniform Format for … RJ Atkinson
- Re: A problem with RFC 6465's Uniform Format for … Fernando Gont
- Re: A problem with RFC 6465's Uniform Format for … Brian E Carpenter
- Re: A problem with RFC 6465's Uniform Format for … Fernando Gont
- Re: A problem with RFC 6465's Uniform Format for … RJ Atkinson
- Re: A problem with RFC 6465's Uniform Format for … Fernando Gont
- Re: Re: A problem with RFC 6465's Uniform Format … Ray Hunter
- Re: A problem with RFC 6465's Uniform Format for … C. M. Heard
- Re: A problem with RFC 6465's Uniform Format for … Mark ZZZ Smith
- Re: A problem with RFC 6465's Uniform Format for … Fernando Gont
- Re: A problem with RFC 6465's Uniform Format for … Dan Lüdtke
- Re: A problem with RFC 6465's Uniform Format for … Mark ZZZ Smith
- Re: A problem with RFC 6465's Uniform Format for … Brian E Carpenter
- Re: A problem with RFC 6465's Uniform Format for … Fernando Gont