Re: [quicwg/base-drafts] PMTUD (#64)

Patrick McManus <notifications@github.com> Tue, 03 January 2017 19:17 UTC

Return-Path: <noreply@github.com>
X-Original-To: quic-issues@ietfa.amsl.com
Delivered-To: quic-issues@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 2410F129AE5 for <quic-issues@ietfa.amsl.com>; Tue, 3 Jan 2017 11:17:15 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -7.001
X-Spam-Level:
X-Spam-Status: No, score=-7.001 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_HI=-5, RCVD_IN_MSPIKE_H2=-0.001, SPF_PASS=-0.001] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (1024-bit key) header.d=github.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 KyMT344wnkER for <quic-issues@ietfa.amsl.com>; Tue, 3 Jan 2017 11:17:13 -0800 (PST)
Received: from github-smtp2b-ext-cp1-prd.iad.github.net (github-smtp2-ext3.iad.github.net [192.30.252.194]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 4B9C8129AB4 for <quic-issues@ietf.org>; Tue, 3 Jan 2017 11:17:13 -0800 (PST)
Date: Tue, 03 Jan 2017 11:17:12 -0800
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=github.com; s=pf2014; t=1483471032; bh=Hz7Vhelm5XDM58er9UraPe9WHvLh5HtYIHezQyYXs9E=; h=From:Reply-To:To:Cc:In-Reply-To:References:Subject:List-ID: List-Archive:List-Post:List-Unsubscribe:From; b=bbm10lRilsYIppaiUODvYrKqjq5krbhyyjJeFl0OzF6xLZRnXGM9RPlTrNi6GJFKy NBlcq6EYiZYfMmBi7zTDb2/561OiY9wTwKuRD6xW6809CnaR7Bm/D7QIVy1rbgE1s6 Ir2qKJtzqwd5HJVNb4K70bLLFIdvHTe8YvzBYx8A=
From: Patrick McManus <notifications@github.com>
To: quicwg/base-drafts <base-drafts@noreply.github.com>
Message-ID: <quicwg/base-drafts/issues/64/270198226@github.com>
In-Reply-To: <quicwg/base-drafts/issues/64@github.com>
References: <quicwg/base-drafts/issues/64@github.com>
Subject: Re: [quicwg/base-drafts] PMTUD (#64)
Mime-Version: 1.0
Content-Type: multipart/alternative; boundary="--==_mimepart_586bf8b888e93_33b3fc60b3371401972f8"; charset="UTF-8"
Content-Transfer-Encoding: 7bit
Precedence: list
X-GitHub-Sender: mcmanus
X-GitHub-Recipient: quic-issues
X-GitHub-Reason: subscribed
X-Auto-Response-Suppress: All
X-GitHub-Recipient-Address: quic-issues@ietf.org
Archived-At: <https://mailarchive.ietf.org/arch/msg/quic-issues/Y0SMv9FJp-RcV4YmycfHySykI9o>
Cc: Subscribed <subscribed@noreply.github.com>
X-BeenThere: quic-issues@ietf.org
X-Mailman-Version: 2.1.17
Reply-To: quic@ietf.org
List-Id: Notification list for GitHub issues related to the QUIC WG <quic-issues.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/quic-issues>, <mailto:quic-issues-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/quic-issues/>
List-Post: <mailto:quic-issues@ietf.org>
List-Help: <mailto:quic-issues-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/quic-issues>, <mailto:quic-issues-request@ietf.org?subject=subscribe>
X-List-Received-Date: Tue, 03 Jan 2017 19:17:15 -0000

I should have been more clear that I was making 2 different (but related)
comments

1] PMTUD overall ought to remain a MAY

2] in describing PMTUD we could choose to detail a loss based in band
approach or an ICMP approach (or a hybrid etc..).  I meant to advocate for
the in band approach because of concerns over the complexity of ICMP given
its rather small impact here.

* part of the complexity is simply ICMP is a whole different protocol stack
- often with different same host consumers than the QUIC stack (as has been
mentioned).

* a bigger part of the complexity imo is that ICMP introduces
unauthenticated and unencrypted inputs into the system. So you have to at
least add the complexity of verifying them independently which undermines a
lot of their original advantages over a loss based approach anyhow (e.g
partially the argument about search space, the argument about faster) and
who knows if this also enables meaningful traffic analysis such as
identifying reliable vs non reliable streams, etc.. Much better in my
opinion to keep all quic inputs authenticated as much as possible - and
this is a place where it seems possible.

I'm not actually a big fan of the variable-length header fields, but your
argument isn't really apples to apples. Variable-Length-Encoded bytes are
truly saved bandwidth, while the 150 byte MTU shortcoming relates to packet
overhead ratios.. adding 150 bytes of data to each packet has about the
same bandwidth impact as saving 6 or 7 actual bytes if my arithmetic worked
out.






On Tue, Jan 3, 2017 at 1:11 PM, martinduke <notifications@github.com> wrote:

> given ian's experience of 90% effectiveness in comment in #64
> <https://github.com/quicwg/base-drafts/issues/64> (comment) I would be
> wary of introducing ICMP into this at all.
>
> '90% effectiveness' means we're leaving about 150 bytes per datagram on
> the table. It would be fine to have a protocol that didn't packetize data
> all that efficiently in the name of simplicity, but if that is the goal
> then we should absolutely get rid of the many variable-length header
> fields, which introduce a ton of complexity for less than 100 bytes of
> savings in most cases.
>
> —
> You are receiving this because you commented.
> Reply to this email directly, view it on GitHub
> <https://github.com/quicwg/base-drafts/issues/64#issuecomment-270181742>,
> or mute the thread
> <https://github.com/notifications/unsubscribe-auth/AAP5sxEbWTvUmKtgbh7rwymjzSWrReJbks5rOo9NgaJpZM4LCCRR>
> .
>


-- 
You are receiving this because you are subscribed to this thread.
Reply to this email directly or view it on GitHub:
https://github.com/quicwg/base-drafts/issues/64#issuecomment-270198226