IETF Logo Mail Archive

RE: Treatment of ICMP for PMTU

Lucas Pardue <Lucas.Pardue@bbc.co.uk> Thu, 28 June 2018 09:10 UTC

Return-Path: <Lucas.Pardue@bbc.co.uk>
X-Original-To: quic@ietfa.amsl.com
Delivered-To: quic@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 9628B130F1F for <quic@ietfa.amsl.com>; Thu, 28 Jun 2018 02:10:13 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -4.199
X-Spam-Level:
X-Spam-Status: No, score=-4.199 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_MED=-2.3, SPF_PASS=-0.001, URIBL_BLOCKED=0.001] autolearn=ham autolearn_force=no
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 RibjGI3brjuM for <quic@ietfa.amsl.com>; Thu, 28 Jun 2018 02:10:11 -0700 (PDT)
Received: from mailout0.telhc.bbc.co.uk (mailout0.telhc.bbc.co.uk [132.185.161.179]) (using TLSv1.2 with cipher DHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 2BF83130F0B for <quic@ietf.org>; Thu, 28 Jun 2018 02:10:11 -0700 (PDT)
Received: from BGB01XI1010.national.core.bbc.co.uk (bgb01xi1010.national.core.bbc.co.uk [10.161.14.14]) by mailout0.telhc.bbc.co.uk (8.15.2/8.15.2) with ESMTP id w5S9A6nU026262; Thu, 28 Jun 2018 10:10:06 +0100 (BST)
Received: from BGB01XUD1012.national.core.bbc.co.uk ([10.161.14.10]) by BGB01XI1010.national.core.bbc.co.uk ([10.161.14.14]) with mapi id 14.03.0389.001; Thu, 28 Jun 2018 10:10:06 +0100
From: Lucas Pardue <Lucas.Pardue@bbc.co.uk>
To: Mikkel Fahnøe Jørgensen <mikkelfj@gmail.com>, IETF QUIC WG <quic@ietf.org>, Martin Duke <martin.h.duke@gmail.com>, "Lubashev, Igor" <ilubashe@akamai.com>
Subject: RE: Treatment of ICMP for PMTU
Thread-Topic: Treatment of ICMP for PMTU
Thread-Index: AdQOVlbAt8rn27zdQrag9H62mpvY5wABihw5AANGU0AABKuwsgAHCjoAAAm8dnA=
Date: Thu, 28 Jun 2018 09:10:06 +0000
Message-ID: <7CF7F94CB496BF4FAB1676F375F9666A3BB5BA81@bgb01xud1012>
References: <924fbd75dbcf4d62a9062570b0d2ba5a@ustx2ex-dag1mb5.msg.corp.akamai.com> <7CF7F94CB496BF4FAB1676F375F9666A3BB5B9DC@bgb01xud1012> <2f0e251a9b274272968a8b3053d3a3a5@ustx2ex-dag1mb5.msg.corp.akamai.com> <7CF7F94CB496BF4FAB1676F375F9666A3BB5BA29@bgb01xud1012> <CAN1APdf-AbpoMZ+FYZpa6H=DCv16Ef0ijkPa6fNSa2tA+obV7g@mail.gmail.com>
In-Reply-To: <CAN1APdf-AbpoMZ+FYZpa6H=DCv16Ef0ijkPa6fNSa2tA+obV7g@mail.gmail.com>
Accept-Language: en-GB, en-US
Content-Language: en-US
X-MS-Has-Attach:
X-MS-TNEF-Correlator:
x-originating-ip: [172.19.161.213]
x-exclaimer-md-config: c91d45b2-6e10-4209-9543-d9970fac71b7
x-tm-as-product-ver: SMEX-12.5.0.1300-8.2.1013-23934.005
x-tm-as-result: No-17.796600-8.000000-10
x-tmase-matchedrid: X4bcv0S75KlEXwnTCGfm3f0peXGEEBlvmHAp2UJ8+TxXG3yI9k2vbCWe OHilL0WHP5mpBtPr/e4BZOsOGHKpoUjlo2JU8qCxmHJeAYKlcpNxtWYlDuRQpY9osn8JrdJPaOL TgTM6NjgX8KBmsUzf6qdCIx24gQ82oXHg+KoW2UYiPTMUjkOgki1RIwMdx4yupOwTxn+Ouv6nvg 2KCDOgGHy4Qb9B9i9z7YaSfIt4lQJ5DFcHFDIB+y/YTQ49mwcHOyAvntOeAd6Rl9Ydphffeu/bF 9CSQF3djaOMlOGY7eHdiQFYcUCYxzRn2xdwrsXpHcQQBuf4ZFu+F//Mn3a2w0S/boWSGMtd0XkQ QQE/sODCEqUCZFLXWv2+R30vCSgA6t1guSoQ4UOeAiCmPx4NwFkMvWAuahr8LzP5snaeb1TTlOj yZSxJ4m4RojVxFH9b57CCZXpr4JBycZ7hsClWWBCVr5v48c4t54yn0DmLPJ0=
x-tm-as-user-approved-sender: Yes
x-tm-as-user-blocked-sender: No
x-tmase-result: 10--17.796600-8.000000
x-tmase-version: SMEX-12.5.0.1300-8.2.1013-23934.005
Content-Type: multipart/alternative; boundary="_000_7CF7F94CB496BF4FAB1676F375F9666A3BB5BA81bgb01xud1012_"
MIME-Version: 1.0
Archived-At: <https://mailarchive.ietf.org/arch/msg/quic/evikgfjRZTkqu-gBTGBkbBmC4mA>
X-BeenThere: quic@ietf.org
X-Mailman-Version: 2.1.26
Precedence: list
List-Id: Main mailing list of the IETF QUIC working group <quic.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/quic>, <mailto:quic-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/quic/>
List-Post: <mailto:quic@ietf.org>
List-Help: <mailto:quic-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/quic>, <mailto:quic-request@ietf.org?subject=subscribe>
X-List-Received-Date: Thu, 28 Jun 2018 09:10:14 -0000

Hi Mikkel,

Thanks for highlighting that issue, I’d lost sight of it.

I’ll respond to the HOL blocking on Igor’s thread.

Lucas

From: Mikkel Fahnøe Jørgensen [mailto:mikkelfj@gmail.com]
Sent: 28 June 2018 06:28
To: Lucas Pardue <Lucas.Pardue@bbc.co.uk>; IETF QUIC WG <quic@ietf.org>; Martin Duke <martin.h.duke@gmail.com>; Lubashev, Igor <ilubashe@akamai.com>
Subject: RE: Treatment of ICMP for PMTU

Wrt tunnelling, see also

https://github.com/quicwg/base-drafts/issues/1209

which was unceremoniously shut down on the argument that a path below 1280 is not a QUIC path.

I see a concrete use case for smaller PMTU’s: a high performance coordination node forwards packets to peer nodes for consensus. The consensus requires adding a signature on forwarding, but repackaging the packet is too slow and might go against the proof being made. Here PNE is also annoying.

On tunneling QUIC in QUIC in QUIC streams: that would add HOL, enough to not make it QUIC.

Mikkel

v2.27.8 | Report a Bug | By Email | System Status