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

"Fred Baker (fred)" <fred@cisco.com> Wed, 26 June 2013 15:46 UTC

Return-Path: <fred@cisco.com>
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 967CF11E8116 for <ipv6@ietfa.amsl.com>; Wed, 26 Jun 2013 08:46:44 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -110.599
X-Spam-Level:
X-Spam-Status: No, score=-110.599 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, RCVD_IN_DNSWL_HI=-8, USER_IN_WHITELIST=-100]
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 NcNYpzejBr9k for <ipv6@ietfa.amsl.com>; Wed, 26 Jun 2013 08:46:27 -0700 (PDT)
Received: from rcdn-iport-5.cisco.com (rcdn-iport-5.cisco.com [173.37.86.76]) by ietfa.amsl.com (Postfix) with ESMTP id 0EB0C21F842E for <ipv6@ietf.org>; Wed, 26 Jun 2013 08:46:27 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=cisco.com; i=@cisco.com; l=2613; q=dns/txt; s=iport; t=1372261587; x=1373471187; h=from:to:cc:subject:date:message-id:references: in-reply-to:content-id:content-transfer-encoding: mime-version; bh=h1dIl8coZ5t4hONp9LYrqiYv/GOG5tiqWXYIcQF3XbI=; b=a14hgfn4e5K0IkHHgq9/JjflYMdSuMxzpoSVVQn9WRper/WUzRGaFq4B nINhg54tNsVYq6mRpUPA2mmefLqoYZP5tcp6mEdXUQnU/i64SAmrlJK9x T4cFxX3ukq2MQx5AiqJrFXi5yDcOQbnsyIeGf9xk2CxczKZ+HyTrT52yj g=;
X-IronPort-Anti-Spam-Filtered: true
X-IronPort-Anti-Spam-Result: AgQFAKALy1GtJXHA/2dsb2JhbABagwkxSb59gQEWdIIjAQEBAwF3AgUHBAIBCBEEAQEBCiQyFwEFCAIEDgUIh3QDCQYMujSMY4ExgQQCMQcGgnxhA4hqjHiDDIp3hSWDEYFpPw
X-IronPort-AV: E=Sophos;i="4.87,945,1363132800"; d="scan'208";a="227714273"
Received: from rcdn-core2-5.cisco.com ([173.37.113.192]) by rcdn-iport-5.cisco.com with ESMTP; 26 Jun 2013 15:46:26 +0000
Received: from xhc-aln-x06.cisco.com (xhc-aln-x06.cisco.com [173.36.12.80]) by rcdn-core2-5.cisco.com (8.14.5/8.14.5) with ESMTP id r5QFkQeH028611 (version=TLSv1/SSLv3 cipher=AES128-SHA bits=128 verify=FAIL); Wed, 26 Jun 2013 15:46:26 GMT
Received: from xmb-rcd-x09.cisco.com ([169.254.9.220]) by xhc-aln-x06.cisco.com ([173.36.12.80]) with mapi id 14.02.0318.004; Wed, 26 Jun 2013 10:46:26 -0500
From: "Fred Baker (fred)" <fred@cisco.com>
To: Mark ZZZ Smith <markzzzsmith@yahoo.com.au>
Subject: Re: New Version Notification for draft-bonica-6man-frag-deprecate-00.txt
Thread-Topic: New Version Notification for draft-bonica-6man-frag-deprecate-00.txt
Thread-Index: AQHOcdXNVc9Jzi6cikCUApHj4sRJiJlHKFIAgACCt4CAAHzRgIAAUOqA
Date: Wed, 26 Jun 2013 15:46:25 +0000
Message-ID: <8C48B86A895913448548E6D15DA7553B9273E2@xmb-rcd-x09.cisco.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> <8C48B86A895913448548E6D15DA7553B9268E3@xmb-rcd-x09.cisco.com> <1372244207.93298.YahooMailNeo@web142505.mail.bf1.yahoo.com>
In-Reply-To: <1372244207.93298.YahooMailNeo@web142505.mail.bf1.yahoo.com>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach:
X-MS-TNEF-Correlator:
x-originating-ip: [10.19.64.125]
Content-Type: text/plain; charset="iso-8859-1"
Content-ID: <6C8E6DAAC17C3443846242A457F382CD@emea.cisco.com>
Content-Transfer-Encoding: quoted-printable
MIME-Version: 1.0
Cc: IPv6 Deployment Prevention <ipv6@ietf.org>
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: Wed, 26 Jun 2013 15:46:44 -0000

On Jun 26, 2013, at 3:56 AM, Mark ZZZ Smith <markzzzsmith@yahoo.com.au> wrote:
> ----- Original Message -----
>> From: Fred Baker (fred) <fred@cisco.com>
>> To: Randy Bush <randy@psg.com>
>> Cc: IPv6 Deployment Prevention <ipv6@ietf.org>
>> Sent: Wednesday, 26 June 2013 1:30 PM
>> Subject: Re: New Version Notification for draft-bonica-6man-frag-deprecate-00.txt
>> 
>> On Jun 25, 2013, at 12:42 PM, Randy Bush <randy@psg.com> wrote:
>>> in reality, you can not count on pmtud working
>> 
>> One of these days, I'll understand why Linux/FreeBSD/Windows/Apple don't implement RFC 4821. 
> 
> Actually, Linux does, it just needs to be switched on in /proc/sys/net/ipv4/
> tcp_mtu_probing - INTEGER Controls TCP Packetization-Layer Path MTU Discovery.  Takes three values: 0 - Disabled 1 - Disabled by default, enabled when an ICMP black hole detected 2 - Always enabled, use initial MSS of tcp_base_mss.

In other words, it's not on. There is some dead code there, but unless you are the writer of the application or a Linux techie, it doesn't work for you.

> I think Windows also implements something similar:
> "
> Troubleshooting PMTU Black Hole Routers"
> http://technet.microsoft.com/en-us/library/cc958871.aspx

"To respond effectively to black hole routers, you must enable the Path MTUBH Detect feature of TCP/IP."

In other words, it's not on. There is some dead code there, but unless you are the writer of the application or a Windows techie, it doesn't work for you.

My question isn't whether there is some experimental code somewhere that could possibly implement it if someone rewrote the application or did some surgery in the system's configuration files. If my daughter bought a standard system and started using it, would it work for her? My question is why folks aren't implementing it in the normal case. Experimental code is kind of pointless in the general case.

> One of the issues with conventional ICMP PTB based PMTUD is the default rate limits on ICMP messages on broadband routers with PPPoE subscribers i.e. dumbell [1500][1492][1500] MTUs, slowing down PMTUD. Upping the limit on ICMP PTBs is an obscure parameter to have to remember to change, and it isn't clear exactly what to change it to - IIRC, the value I've used in the past is 1000/s up from 10/s. RFC4821 would be nice because it would avoid control plane processing that ICMP based PMTUD causes.
> 
> Regards,
> Mark.

If at first the idea is not absurd, then there is no hope for it.  
Albert Einstein