Re: New Version Notification for draft-bonica-6man-frag-deprecate-00.txt

George Michaelson <ggm@algebras.org> Tue, 25 June 2013 23:53 UTC

Return-Path: <ggm@algebras.org>
X-Original-To: ipv6@ietfa.amsl.com
Delivered-To: ipv6@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 71CDF11E816B for <ipv6@ietfa.amsl.com>; Tue, 25 Jun 2013 16:53:07 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.977
X-Spam-Level:
X-Spam-Status: No, score=-1.977 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, FM_FORGED_GMAIL=0.622, HTML_MESSAGE=0.001, NO_RELAYS=-0.001]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id TkssMZpvlj6e for <ipv6@ietfa.amsl.com>; Tue, 25 Jun 2013 16:53:06 -0700 (PDT)
Received: from mail-pb0-x234.google.com (mail-pb0-x234.google.com [IPv6:2607:f8b0:400e:c01::234]) by ietfa.amsl.com (Postfix) with ESMTP id C87AD11E8162 for <ipv6@ietf.org>; Tue, 25 Jun 2013 16:53:06 -0700 (PDT)
Received: by mail-pb0-f52.google.com with SMTP id xa12so13248997pbc.25 for <ipv6@ietf.org>; Tue, 25 Jun 2013 16:53:06 -0700 (PDT)
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=google.com; s=20120113; h=mime-version:x-originating-ip:in-reply-to:references:date :message-id:subject:from:to:content-type:x-gm-message-state; bh=N1PuUnXDfVdlv2Xe+i4S43IdLDHCTa+aB9PPyIeoWnY=; b=FHlclcTY39lRFQL+NmG6W3MhJfS0lF+UP6tbOvTjCubI74xzWC8nz72NeBhAguhJjL yCHcgaWTp0xw661YxRiUOvpEIGznu2f0cZ5AyMA1Mg98N074HajxMlfmTHQ+Cyn+gwTU ljZXThnX5LB88RnNjNpB+OR2SyauOpDKwhM6uPSnbTg6AJKonfB/QLULQv3eqanP4tTL iNsTgbU8ZOnOyYSrvovYarEwHSxkiOiDf5HpQxTAKW1LAB+nY1hY7bHT0lJYCxdapIUu vu2xtowDHy7+4Vo84DOnh+UBvbFbqPEVp4bTCPH8S3sQwLS+CRy/knEmbeeu/Z99BKT2 8vdg==
MIME-Version: 1.0
X-Received: by 10.66.169.172 with SMTP id af12mr2036997pac.216.1372204386450; Tue, 25 Jun 2013 16:53:06 -0700 (PDT)
Received: by 10.70.25.195 with HTTP; Tue, 25 Jun 2013 16:53:06 -0700 (PDT)
X-Originating-IP: [2001:dc0:a000:4:5cfa:3a7d:cf29:3a21]
In-Reply-To: <m2zjudixlt.wl%randy@psg.com>
References: <2CF4CB03E2AA464BA0982EC92A02CE2509F85151@BY2PRD0512MB653.namprd05.prod.outlook.com> <51C32FA9.1090207@gmail.com> <2CF4CB03E2AA464BA0982EC92A02CE2509F85F38@BY2PRD0512MB653.namprd05.prod.outlook.com> <20130624204008.GB3647@virgo.local> <20130624205226.GC3647@virgo.local> <2CF4CB03E2AA464BA0982EC92A02CE2509F8761C@BY2PRD0512MB653.namprd05.prod.outlook.com> <51C902DC.9000408@gmail.com> <m24ncmaozs.wl%randy@psg.com> <2EA20F89-02F5-4D06-90EE-A7D2974045A3@employees.org> <m2li5yj7u3.wl%randy@psg.com> <3B0D9447-D39F-4165-9B43-019C3513101A@employees.org> <m2ip12j6d9.wl%randy@psg.com> <A0662700-628E-4032-89ED-6621B0867820@apple.com> <m2zjudixlt.wl%randy@psg.com>
Date: Wed, 26 Jun 2013 09:53:06 +1000
Message-ID: <CAKr6gn1xdugTqEFM1HKODL=S-niDSX5WfkatfaO+-FZVK7cqxA@mail.gmail.com>
Subject: Re: New Version Notification for draft-bonica-6man-frag-deprecate-00.txt
From: George Michaelson <ggm@algebras.org>
To: IPv6 Deployment Prevention <ipv6@ietf.org>
Content-Type: multipart/alternative; boundary="047d7bea3b1403929904e0033b2d"
X-Gm-Message-State: ALoCoQk07j5tpHVnMxmUbV9jCjo7XDypqW6YtS4+7eSc0xGsulmV+JEgl9w32UbXBO9JwFrEeDsg
X-BeenThere: ipv6@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
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: Tue, 25 Jun 2013 23:53:07 -0000

If the recommended MTU was dropped, the frag changes probably wouldn't be
needed.

If the recommended MTU was dropped, could we raise the recommended MTU
again later, on some evidence based process to confirm how its working?

If this was only a recommendation, would it be enough? No code changes
required: totally in the hands of operators and host configuration. Can be
done on BSD and Linux systems trivially.

APNIC has been running some of its web services on a dropped MTU for some
time. It definitely reduced the incidence of pMTU related fail-to-fetch
over V6 which we were seeing. (a bunch of people in Europe were seeing this
facing us. We have seen this facing sites like ISOC and the IETF, in times
past, as a result of dual-stacking)


On Wed, Jun 26, 2013 at 9:23 AM, Randy Bush <randy@psg.com> wrote:

> > while the practical global MTU for IPv4 remains larger, then I would
> > say that pretty much serves as a guarantee that the transition from
> > IPv4 to IPv6 cannot ever be successful.
>
> i had a semi-discussion with olaf kolkman, who was saying dnssec and
> ipv6 were slow and steady transitions.  i pointed out that dnssec, with
> all its warts, was forward compatible and there was no visible
> alternative.  ipv6, otoh, is incompatible on the wire and to the user,
> and there are viable, though disgusting, alternatives, nat.
>
> i am not optimistic.  in our second system syndrome religious ferver, we
> have left the customer behind.  if we have any last chance, it is to
> make it as absolutely easy as possible for folk running ipv4 to add
> ipv6, no excuses, no self-righteous crap, no ivory tower.  all speed
> bumps must br removed.
>
> st00pid terribly trivial example.  why do i have to install a second
> dhcp server for v6?  why does the default one not do both?  so building,
> testing, installing, dhcpv6 goes on the enterprise's mess of a ipv6
> transition pert chart and the perceived cost goes up.  and no, dhcp-
> based enterprises are not gonna transition to stateless, i said no
> religion.
>
> ron is actually deploying ipv6 in enterprises to see what his customers
> are seeing, eating his own dogfood.  he did not field this draft for his
> amusement or to get his name on an rfc.
>
> randy
> --------------------------------------------------------------------
> IETF IPv6 working group mailing list
> ipv6@ietf.org
> Administrative Requests: https://www.ietf.org/mailman/listinfo/ipv6
> --------------------------------------------------------------------
>