IETF Logo Mail Archive

Re: [v6ops] new draft: draft-taylor-v6ops-fragdrop

Mark Smith <markzzzsmith@yahoo.com.au> Thu, 25 October 2012 08:41 UTC

Return-Path: <markzzzsmith@yahoo.com.au>
X-Original-To: v6ops@ietfa.amsl.com
Delivered-To: v6ops@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 5038321F88E2 for <v6ops@ietfa.amsl.com>; Thu, 25 Oct 2012 01:41:35 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.599
X-Spam-Level:
X-Spam-Status: No, score=-1.599 tagged_above=-999 required=5 tests=[AWL=-0.100, BAYES_00=-2.599, FROM_LOCAL_NOVOWEL=0.5, J_CHICKENPOX_13=0.6]
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 k0qLXeB3Fe2y for <v6ops@ietfa.amsl.com>; Thu, 25 Oct 2012 01:41:34 -0700 (PDT)
Received: from nm33-vm1.bullet.mail.ne1.yahoo.com (nm33-vm1.bullet.mail.ne1.yahoo.com [98.138.229.65]) by ietfa.amsl.com (Postfix) with ESMTP id 7869521F8869 for <v6ops@ietf.org>; Thu, 25 Oct 2012 01:41:34 -0700 (PDT)
Received: from [98.138.226.177] by nm33.bullet.mail.ne1.yahoo.com with NNFMP; 25 Oct 2012 08:41:28 -0000
Received: from [98.138.88.234] by tm12.bullet.mail.ne1.yahoo.com with NNFMP; 25 Oct 2012 08:41:28 -0000
Received: from [127.0.0.1] by omp1034.mail.ne1.yahoo.com with NNFMP; 25 Oct 2012 08:41:28 -0000
X-Yahoo-Newman-Property: ymail-3
X-Yahoo-Newman-Id: 969584.71113.bm@omp1034.mail.ne1.yahoo.com
Received: (qmail 88731 invoked by uid 60001); 25 Oct 2012 08:41:28 -0000
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=yahoo.com.au; s=s1024; t=1351154488; bh=t1ZUvUA4dDFaFLT+9hAvocThDvBbOCuG7TlNuDFRbtE=; 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=FhvPDIK/oS9W636gcjLdlg4SiP6w5spYNJLM+IAOUBEE/qoYY3xcLLh/9+kMIHLUqB9YoWSytVGtIL6ZyMbePIQcLuTnbNLBxkYUaWEEsG4ajxW20+tUzPsyKc+gYl726mpQFPJTm+73xWnET1wqGiSnPR6MWquy/n+M6F46Cxs=
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=RDUP7OMtoSoZjlslxYtiM30CLRPXSg6Q8gliiA6/5bGWehQ8kGW/EnUo1Rc2ALlPJnjFiQxwNBT8x3wtqhqEVqXKwyjHMj/FRjEYPsG7b1Q5MfbNpDAEzn3CSQc2+9Ws7CXHLAJzazBVZlzqrF/Uvs9TEt6nDa+UK+l8GvTs16c=;
X-YMail-OSG: y1BPs2gVM1kPC.V36gcovbW4_eTRfoAb35L7HsBAAQyRWwM .QoFWl6iEuuHGYc6WmS04EM6K9Xbsr6M5JD4nduDZoTrWsNatXc8fgnlOj8J W2vjhpdO_NYXcQ29wTx1yRvPs2q99M821VJujOHsOz_eNOmH4W0bAP0SVReX J.GaURfO.zZYKPUf3_QVGtlAL3CB.1K5v14.xotq6brUPkXFCbn14I.8lQYs wM3fDzhNPUtywZO0dUGrKo5DYN21bm3_KBsMk2Y5WPhr0P9ECSk3Y6ebRBQ6 eVJs0yVRMv9oU4tvWmeiUVFzChLwGQ7GwitRxYQnPCZP7gll5yrK_..Xb1hd StGUAWO_67DGryna37Gl1rY6HBDDcRtnOysg5Lbddvbd2iAdRNqWnoI9rBJ0 o4oOM8uLMFiWr0LYLIxDBOvk6v2337qDJP6PKQYa0rJodLPyzGr4ps6oItP9 _XRZqVl4Ekndt5D_wxDRjgr4U8Po3fkRYt2aap.RBRfgIlkJJi22QVHKoBOs r3QhIflNH1NDH7Q--
Received: from [150.101.221.237] by web32504.mail.mud.yahoo.com via HTTP; Thu, 25 Oct 2012 01:41:27 PDT
X-Rocket-MIMEInfo: 001.001, SGksCgoKCi0tLS0tIE9yaWdpbmFsIE1lc3NhZ2UgLS0tLS0KPiBGcm9tOiBNZXJpa2UgS2FlbyA8a2Flb0BtZXJpa2UuY29tPgo.IFRvOiBMb3JlbnpvIENvbGl0dGkgPGxvcmVuem9AZ29vZ2xlLmNvbT4KPiBDYzogVjYgT3BzIDx2Nm9wc0BpZXRmLm9yZz4KPiBTZW50OiBUaHVyc2RheSwgMjUgT2N0b2JlciAyMDEyIDc6NDkgQU0KPiBTdWJqZWN0OiBSZTogW3Y2b3BzXSBuZXcgZHJhZnQ6IGRyYWZ0LXRheWxvci12Nm9wcy1mcmFnZHJvcAo.IAo.IAo.IE9uIE9jdCAyMywgMjAxMiwgYXQgMTozOSBBTSwgTG8BMAEBAQE-
X-Mailer: YahooMailWebService/0.8.123.450
References: <201210161245.q9GCj0i26478@ftpeng-update.cisco.com> <E1829B60731D1740BB7A0626B4FAF0A65E0DEDF3A2@XCH-NW-01V.nw.nos.boeing.com> <507DA6A3.20807@inex.ie> <E1829B60731D1740BB7A0626B4FAF0A65E0DEDF3C3@XCH-NW-01V.nw.nos.boeing.com> <507DAB13.2010704@inex.ie> <E1829B60731D1740BB7A0626B4FAF0A65E0DEDF3CE@XCH-NW-01V.nw.nos.boeing.com> <507DDF8A.9010607@inex.ie> <E1829B60731D1740BB7A0626B4FAF0A65E0DEDF5AB@XCH-NW-01V.nw.nos.boeing.com> <BB219517-B488-4777-AE9C-35C57BE91263@kumari.net> <Pine.LNX.4.64.1210171337470.7337@shell4.bayarea.net> <AC530E99-4054-4B0A-9B5C-30F9EF4A530C@kumari.net> <20121018223121.28B2C2A0041D@drugs.dv.isc.org> <50812F87.5000107@inex.ie> <E1829B60731D1740BB7A0626B4FAF0A65E0DF5C66F@XCH-NW-01V.nw.nos.boeing.com> <5085319B.60707@inex.ie> <CAKD1Yr2qDsM6cCPapRmKuWw7SG-cuMd9PuiBD7ineqj7Bp4+Xw@mail.gmail.com> <8C4093E0-4031-4057-9B96-3738A5A48D2D@merike.com>
Message-ID: <1351154487.78754.YahooMailNeo@web32504.mail.mud.yahoo.com>
Date: Thu, 25 Oct 2012 01:41:27 -0700
From: Mark Smith <markzzzsmith@yahoo.com.au>
To: Merike Kaeo <kaeo@merike.com>, Lorenzo Colitti <lorenzo@google.com>
In-Reply-To: <8C4093E0-4031-4057-9B96-3738A5A48D2D@merike.com>
MIME-Version: 1.0
Content-Type: text/plain; charset="iso-8859-1"
Content-Transfer-Encoding: quoted-printable
Cc: V6 Ops <v6ops@ietf.org>
Subject: Re: [v6ops] new draft: draft-taylor-v6ops-fragdrop
X-BeenThere: v6ops@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
Reply-To: Mark Smith <markzzzsmith@yahoo.com.au>
List-Id: v6ops discussion list <v6ops.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/v6ops>, <mailto:v6ops-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/v6ops>
List-Post: <mailto:v6ops@ietf.org>
List-Help: <mailto:v6ops-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/v6ops>, <mailto:v6ops-request@ietf.org?subject=subscribe>
X-List-Received-Date: Thu, 25 Oct 2012 08:41:35 -0000

Hi,



----- Original Message -----
> From: Merike Kaeo <kaeo@merike.com>
> To: Lorenzo Colitti <lorenzo@google.com>
> Cc: V6 Ops <v6ops@ietf.org>
> Sent: Thursday, 25 October 2012 7:49 AM
> Subject: Re: [v6ops] new draft: draft-taylor-v6ops-fragdrop
> 
> 
> On Oct 23, 2012, at 1:39 AM, Lorenzo Colitti wrote:
> 
>>  On Mon, Oct 22, 2012 at 8:44 PM, Nick Hilliard <nick@inex.ie> wrote:
>>  So, what do we do?  Do we:
>> 
>>  - ignore the problem
>>  - issue generic advice
>>  - name and shame
>>  - other
>> 
>>  Other. Document that some networks drop fragments, the reasons why they do 
> so, and the impact on applications, but provide no advice.
> 
> +1
> 

I think there should be advice. If the IETF has seen fit to make

fragmentation a capability of IPv6, then I think that is inherently saying
that the IETF strongly suggests if not requires forwarding rather than
dropping of fragments for successful IPv6 operation. This seems to me to
be an RFC2775 Internet Transparency issue.

Alternatively, if fragments are more trouble than they're worth,
they should be deprecated. 

>>  It's unlikely that this group, let alone the IETF, would agree on what 

> advice to give (at least this decade), but I think it is the responsibility of 
> an operations group to document real operational issues, so the rest of the 
> community, including application developers and protocol developers, can be made 
> aware of it.
> 

It seems to me that developing an application that may be used over the

Internet involves developing for the worst case, not the best. If a small
but significant enough portion of sites on the Internet drop fragments, then
applications will be developed to avoid using fragments. Once applications
avoid using fragments to suit some sites on the Internet, then all sites
on the Internet may as well drop them, because they've been rendered useless.

> +1 on documenting known issues to make others aware
> 
> - merike
> _______________________________________________
> v6ops mailing list
> v6ops@ietf.org
> https://www.ietf.org/mailman/listinfo/v6ops
>

v2.23.0 | Report a Bug | By Email