Re: [Int-area] Int-area Digest, Vol 170, Issue 14

Joe Touch <touch@strayalpha.com> Sat, 02 November 2019 02:53 UTC

Return-Path: <touch@strayalpha.com>
X-Original-To: int-area@ietfa.amsl.com
Delivered-To: int-area@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id CA1F01209E2 for <int-area@ietfa.amsl.com>; Fri, 1 Nov 2019 19:53:23 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.219
X-Spam-Level:
X-Spam-Status: No, score=-1.219 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, RCVD_IN_DNSWL_NONE=-0.0001, SPF_HELO_NONE=0.001, SPF_NEUTRAL=0.779, URIBL_BLOCKED=0.001] autolearn=no autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (2048-bit key) header.d=strayalpha.com
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 wSosPwyRF61C for <int-area@ietfa.amsl.com>; Fri, 1 Nov 2019 19:53:21 -0700 (PDT)
Received: from server217-3.web-hosting.com (server217-3.web-hosting.com [198.54.115.226]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id B85381209A6 for <int-area@ietf.org>; Fri, 1 Nov 2019 19:53:21 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; q=dns/txt; c=relaxed/relaxed; d=strayalpha.com; s=default; h=To:References:Message-Id:Cc:Date:In-Reply-To: From:Subject:Mime-Version:Content-Transfer-Encoding:Content-Type:Sender: Reply-To:Content-ID:Content-Description:Resent-Date:Resent-From:Resent-Sender :Resent-To:Resent-Cc:Resent-Message-ID:List-Id:List-Help:List-Unsubscribe: List-Subscribe:List-Post:List-Owner:List-Archive; bh=oIC2Rzl0+P2d1MQHNq4Hv7BnoFHdSUISOBrTwD2oDoI=; b=RL/esDlObH2aMwyXT/PILs7HzN RNKn7JwYpnAzixdXBFJ8wh8f3dDcA3c/zyqXbw69OK45DqYkx8o2v5tLa/feUGQgB0F1aC/Dve0UO 9rN+njOC59mYzBhfRZyb1KfPN1UJWWt4ezkMx26yiyXpOl3pSKkC0kip0UJm+t4aRJTUEzsETbViP THWQU4hZRbI8X1JRI907nyEtUOHjmdDWPxSkMKCnUEzR8zh4IZNNiGTT4Ox/4QPJ1At1ZcnT/JUyM Kbh1NCpLBUrrODnpQlqi71N0GFZO7c4mvroz3TyGCY/CuhOqp//AJadh+zMQA8E3m3MUr1WUP+Zs0 eeMEfWUw==;
Received: from cpe-172-250-225-198.socal.res.rr.com ([172.250.225.198]:63040 helo=[192.168.1.5]) by server217.web-hosting.com with esmtpsa (TLSv1.2:ECDHE-RSA-AES256-GCM-SHA384:256) (Exim 4.92) (envelope-from <touch@strayalpha.com>) id 1iQjXQ-000nXa-EZ; Fri, 01 Nov 2019 22:53:21 -0400
Content-Type: text/plain; charset="utf-8"
Content-Transfer-Encoding: quoted-printable
Mime-Version: 1.0 (1.0)
From: Joe Touch <touch@strayalpha.com>
In-Reply-To: <51C08012-8D12-471C-B867-EDC700D33893@juniper.net>
Date: Fri, 01 Nov 2019 19:53:15 -0700
Cc: "int-area@ietf.org" <int-area@ietf.org>
Message-Id: <B02379AC-C0CC-4404-BDC8-32E443AAFD7F@strayalpha.com>
References: <51C08012-8D12-471C-B867-EDC700D33893@juniper.net>
To: Manoj Nayak <manojnayak@juniper.net>
X-Mailer: iPhone Mail (17B84)
X-OutGoing-Spam-Status: No, score=0.3
X-AntiAbuse: This header was added to track abuse, please include it with any abuse report
X-AntiAbuse: Primary Hostname - server217.web-hosting.com
X-AntiAbuse: Original Domain - ietf.org
X-AntiAbuse: Originator/Caller UID/GID - [47 12] / [47 12]
X-AntiAbuse: Sender Address Domain - strayalpha.com
X-Get-Message-Sender-Via: server217.web-hosting.com: authenticated_id: touch@strayalpha.com
X-Authenticated-Sender: server217.web-hosting.com: touch@strayalpha.com
X-Source:
X-Source-Args:
X-Source-Dir:
X-From-Rewrite: unmodified, already matched
Archived-At: <https://mailarchive.ietf.org/arch/msg/int-area/7p9Q5q_1ioPf9qTLUwwnbozMTEc>
Subject: Re: [Int-area] Int-area Digest, Vol 170, Issue 14
X-BeenThere: int-area@ietf.org
X-Mailman-Version: 2.1.29
Precedence: list
List-Id: IETF Internet Area Mailing List <int-area.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/int-area>, <mailto:int-area-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/int-area/>
List-Post: <mailto:int-area@ietf.org>
List-Help: <mailto:int-area-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/int-area>, <mailto:int-area-request@ietf.org?subject=subscribe>
X-List-Received-Date: Sat, 02 Nov 2019 02:53:24 -0000


> On Nov 1, 2019, at 7:32 PM, Manoj Nayak <manojnayak@juniper.net> wrote:
> 
> Hello Joe,
> 
> I was reading the  following comment. Even when router takes care of generating equal sized fragments, the last fragment is 
> most likely to be less than rest of the fragments.

See RFC 1812. Not all fragmentation algs have unequal sizes or the smallest chunk last. There are no requirements on this. 

> 
> "why would this approach find the largest fragment through a system?
> rfc1812 talks about various strategies, one of which is ?equal sized?, which might never find the max the way you propose"
> 
> 
> Regards
> Manoj Nayak
> 
>    -----Original Message-----
>    From: Joe Touch <touch@strayalpha.com> 
>    Sent: Wednesday, October 30, 2019 12:44 AM
>    To: Ron Bonica <rbonica@juniper.net>
>    Cc: int-area@ietf.org
>    Subject: Re: [Int-area] New Version Notification for draft-bonica-intarea-lossless-pmtud-00.txt
> 
>    Hi, Ron,
> 
>    A few things come to mind. The first one, IMO, renders the rest somewhat less important.
> 
>    Joe
> 
>    -------------
> 
>    - this approach applies only to IPv4; not sure it?s worth trying to optimize for only that case
>        (it requires on-path fragmentation permitted)
> 
>    - this approach relies on ICMPs, so it?s as robust (or, more to the point, not) as PMTUD
>        if ICMPs can find the reverse path from the dest, why wouldn?t the routers?
>        i.e., isn?t the problem with ICMPs not just routers not sending them but firewalls BLOCKING them?
>        (i.e., if ICMPs would work here, PMTU would have worked, rendering this unnecessary)
> 
>    - why does this doc assume the max ICMP is 576?
>        we?re still talking IPv4 here; it?s still 68 (that?s why only 64 bits of the orig payload are guaranteed)
>        (yes, your note in the end of sec 1 is relevant, but given v4-in-v4 tunneling, it?s possible that paths might be smaller than the 576 assumption)
> 
>    - why would this approach find the largest fragment through a system?
>        rfc1812 talks about various strategies, one of which is ?equal sized?, which might never find the max the way you propose 
> 
> 
>> On Oct 29, 2019, at 9:53 AM, Ron Bonica <rbonica=40juniper.net@dmarc.ietf.org> wrote:
>> 
>> Folks,
>> 
>> Please review and comment.
>> 
>>                       Ron
>> 
>> 
>> 
>> Juniper Business Use Only
>> 
>> -----Original Message-----
>> From: internet-drafts@ietf.org <internet-drafts@ietf.org> 
>> Sent: Tuesday, October 29, 2019 11:48 AM
>> To: Ron Bonica <rbonica@juniper.net>; Hakan Alpan <halpan@hnc.edu>; Radon Rosborough <rrosborough@hmc.edu>; Bradely Newton <bnewton@hmc.edu>; Miles President <mpresident@hmc.edu>; Manoj Nayak <manojnayak@juniper.net>
>> Subject: New Version Notification for draft-bonica-intarea-lossless-pmtud-00.txt
>> 
>> 
>> A new version of I-D, draft-bonica-intarea-lossless-pmtud-00.txt
>> has been successfully submitted by Ron Bonica and posted to the IETF repository.
>> 
>> Name:        draft-bonica-intarea-lossless-pmtud
>> Revision:    00
>> Title:        Lossless Path MTU Discovery (PMTUD)
>> Document date:    2019-10-29
>> Group:        Individual Submission
>> Pages:        8
>> URL:            https://urldefense.com/v3/__https://tools.ietf.org/html/draft-bonica-intarea-lossless-pmtud-00__;!8WoA6RjC81c!SaG54qXv3mOmFFinOp93hDtn-j4u5ZzUbomMfaHAujluBDj7pJq_RtQMALmTf6K4$ 
>> 
>> 
>> 
>> Abstract:
>>  This document describes alternative IPv4 PMTUD procedures that do not
>>  prevent IP fragmentation and do no rely on the network's ability to
>>  deliver ICMP Destination Unreachable messages to the source node.
>>  This document also defines a new ICMP message.  IPv4 nodes emit this
>>  new message when they reassemble a fragmented packet.
>> 
>> 
>> 
>> 
>> Please note that it may take a couple of minutes from the time of submission until the htmlized version and diff are available at tools.ietf.org.
>> 
>> The IETF Secretariat
>> _______________________________________________
>> Int-area mailing list
>> Int-area@ietf.org
>> https://urldefense.com/v3/__https://www.ietf.org/mailman/listinfo/int-area__;!8WoA6RjC81c!SaG54qXv3mOmFFinOp93hDtn-j4u5ZzUbomMfaHAujluBDj7pJq_RtQMAGjVmADJ$ 
> 
>    ------------------------------
> 
>    Message: 2
>    Date: Thu, 31 Oct 2019 19:16:38 +0000
>    From: Ron Bonica <rbonica@juniper.net>
>    To: "int-area@ietf.org" <int-area@ietf.org>
>    Subject: [Int-area] FW: New Version Notification for
>        draft-bonica-intarea-lossless-pmtud-01.txt
>    Message-ID:
>        <BN7PR05MB5699A257D6A46B016FBCD539AE630@BN7PR05MB5699.namprd05.prod.outlook.com>
>        
>    Content-Type: text/plain; charset="utf-8"
> 
> 
>    Updated draft
> 
> 
>    Juniper Business Use Only
> 
>    -----Original Message-----
>    From: internet-drafts@ietf.org <internet-drafts@ietf.org> 
>    Sent: Thursday, October 31, 2019 3:15 PM
>    To: Ron Bonica <rbonica@juniper.net>; Hakan Alpan <halpan@hnc.edu>; Radon Rosborough <rrosborough@hmc.edu>; Bradely Newton <bnewton@hmc.edu>; Bradley Newton <bnewton@hmc.edu>; Miles President <mpresident@hmc.edu>; Manoj Nayak <manojnayak@juniper.net>
>    Subject: New Version Notification for draft-bonica-intarea-lossless-pmtud-01.txt
> 
> 
>    A new version of I-D, draft-bonica-intarea-lossless-pmtud-01.txt
>    has been successfully submitted by Ron Bonica and posted to the IETF repository.
> 
>    Name:        draft-bonica-intarea-lossless-pmtud
>    Revision:    01
>    Title:        Lossless Path MTU Discovery (PMTUD)
>    Document date:    2019-10-31
>    Group:        Individual Submission
>    Pages:        7
>    URL                     https://urldefense.com/v3/__https://tools.ietf.org/html/draft-bonica-intarea-lossless-pmtud-01__;!8WoA6RjC81c!XLNEZ-1XcW1SCcQkdY1e72UP_43UD2slIH4JB_BJ-gO_XISUMzEDSldcRkqU5JMOvqw$ 
>    Abstract:
>       This document describes alternative IPv4 PMTUD procedures that do not
>       prevent IP fragmentation and do no rely on the network's ability to
>       deliver ICMP Destination Unreachable messages to the source node.
>       This document also defines a new ICMP message.  IPv4 nodes emit this
>       new message when they reassemble a fragmented packet.
> 
> 
> 
> 
>    Please note that it may take a couple of minutes from the time of submission until the htmlized version and diff are available at tools.ietf.org.
> 
>    The IETF Secretariat
> 
>    ------------------------------
> 
>    Message: 3
>    Date: Thu, 31 Oct 2019 16:51:10 -0700
>    From: Bob Hinden <bob.hinden@gmail.com>
>    To: Ron Bonica <rbonica=40juniper.net@dmarc.ietf.org>
>    Cc: Bob Hinden <bob.hinden@gmail.com>, "int-area@ietf.org"
>        <int-area@ietf.org>
>    Subject: Re: [Int-area] New Version Notification for
>        draft-bonica-intarea-lossless-pmtud-01.txt
>    Message-ID: <702307FF-E65E-4800-BAC8-CEE16EAFA0BD@gmail.com>
>    Content-Type: text/plain; charset="utf-8"
> 
>    Ron,
> 
>    A few comments on your draft.
> 
>    Naming the draft "Lossless Path MTU Discovery (PMTUD)? seems to be very aspirational, and is an oxymoron.  ICMP message can be rate limited and dropped in the network.   Hardly ?lossless?.  A different title might be better.
> 
>    I do like the idea of the destination sending feedback, we have worked on some other drafts with that property.
> 
>    The document says:
> 
>       This document describes alternative PMTUD procedures that do no rely
>       on the network's ability to deliver ICMP Destination Unreachable
>       messages to the source node.  In these procedures, the source node
>       produces an initial PMTU estimate.  This initial estimate is equal to
>       the MTU of the first link along the path to the destination node.  It
>       can be greater than the actual PMTU.
> 
>    This is not really correct, your are still dependent on the networks ability to deliver ICMP messages to the source node.  Just not ICMP Destination Unreachable messages.   A new ICMP message isn?t going to be better, perhaps worse.
> 
>    I didn?t understand the purpose of the Code field, that can indicate reassembly error.  What is the purpose of this?   This seems to be in conflict with this message that is sent when the destination node successfully reassemblies a set of fragments.  With the code indicating reassembly error, it is saying that the fragments were not reassembled.
> 
>    It may be folly to try to modify IPv4 implementations at this point.   I have no objections if you wish to try pushing this big rock up hill, but I doubt you will be successful.
> 
>    I see you have several co-authors from Harvey Mudd College.
> 
>    Bob
> 
> 
>> On Oct 31, 2019, at 12:16 PM, Ron Bonica <rbonica=40juniper.net@dmarc.ietf.org> wrote:
>> 
>> 
>> Updated draft
>> 
>> 
>> Juniper Business Use Only
>> 
>> -----Original Message-----
>> From: internet-drafts@ietf.org <internet-drafts@ietf.org>
>> Sent: Thursday, October 31, 2019 3:15 PM
>> To: Ron Bonica <rbonica@juniper.net>; Hakan Alpan <halpan@hnc.edu>; Radon Rosborough <rrosborough@hmc.edu>; Bradely Newton <bnewton@hmc.edu>; Bradley Newton <bnewton@hmc.edu>; Miles President <mpresident@hmc.edu>; Manoj Nayak <manojnayak@juniper.net>
>> Subject: New Version Notification for draft-bonica-intarea-lossless-pmtud-01.txt
>> 
>> 
>> A new version of I-D, draft-bonica-intarea-lossless-pmtud-01.txt
>> has been successfully submitted by Ron Bonica and posted to the IETF repository.
>> 
>> Name:        draft-bonica-intarea-lossless-pmtud
>> Revision:    01
>> Title:        Lossless Path MTU Discovery (PMTUD)
>> Document date:    2019-10-31
>> Group:        Individual Submission
>> Pages:        7
>> URL                     https://urldefense.com/v3/__https://tools.ietf.org/html/draft-bonica-intarea-lossless-pmtud-01__;!8WoA6RjC81c!XLNEZ-1XcW1SCcQkdY1e72UP_43UD2slIH4JB_BJ-gO_XISUMzEDSldcRkqU5JMOvqw$ 
>> Abstract:
>>  This document describes alternative IPv4 PMTUD procedures that do not
>>  prevent IP fragmentation and do no rely on the network's ability to
>>  deliver ICMP Destination Unreachable messages to the source node.
>>  This document also defines a new ICMP message.  IPv4 nodes emit this
>>  new message when they reassemble a fragmented packet.
>> 
>> 
>> 
>> 
>> Please note that it may take a couple of minutes from the time of submission until the htmlized version and diff are available at tools.ietf.org.
>> 
>> The IETF Secretariat
>> _______________________________________________
>> Int-area mailing list
>> Int-area@ietf.org
>> https://urldefense.com/v3/__https://www.ietf.org/mailman/listinfo/int-area__;!8WoA6RjC81c!XLNEZ-1XcW1SCcQkdY1e72UP_43UD2slIH4JB_BJ-gO_XISUMzEDSldcRkqUNjQlVhU$ 
> 
>    -------------- next part --------------
>    A non-text attachment was scrubbed...
>    Name: signature.asc
>    Type: application/pgp-signature
>    Size: 488 bytes
>    Desc: Message signed with OpenPGP
>    URL: <https://urldefense.com/v3/__https://mailarchive.ietf.org/arch/browse/int-area/attachments/20191031/999da00d/attachment.asc__;!8WoA6RjC81c!XLNEZ-1XcW1SCcQkdY1e72UP_43UD2slIH4JB_BJ-gO_XISUMzEDSldcRkqUrBUvJx8$ >
> 
>    ------------------------------
> 
>    Subject: Digest Footer
> 
>    _______________________________________________
>    Int-area mailing list
>    Int-area@ietf.org
>    https://urldefense.com/v3/__https://www.ietf.org/mailman/listinfo/int-area__;!8WoA6RjC81c!XLNEZ-1XcW1SCcQkdY1e72UP_43UD2slIH4JB_BJ-gO_XISUMzEDSldcRkqUNjQlVhU$ 
> 
> 
>    ------------------------------
> 
>    End of Int-area Digest, Vol 170, Issue 14
>    *****************************************
> 
>