Return-Path: 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 0FF1F130EF0 for ; Sat, 30 Jun 2018 01:10:32 -0700 (PDT) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -8.009 X-Spam-Level: X-Spam-Status: No, score=-8.009 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, MAILING_LIST_MULTI=-1, RCVD_IN_DNSWL_HI=-5, SPF_PASS=-0.001, T_DKIMWL_WL_HIGH=-0.01, URIBL_BLOCKED=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 wkPtOZ1mVrWl for ; Sat, 30 Jun 2018 01:10:30 -0700 (PDT) Received: from out-4.smtp.github.com (out-4.smtp.github.com [192.30.252.195]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 52A9D130EE3 for ; Sat, 30 Jun 2018 01:10:30 -0700 (PDT) Date: Sat, 30 Jun 2018 01:10:28 -0700 DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=github.com; s=pf2014; t=1530346228; bh=Wqi632bXzRKcrCiDfJT5YzuhXHhNFWl2y+rSN5tKpSg=; h=Date:From:Reply-To:To:Cc:In-Reply-To:References:Subject:List-ID: List-Archive:List-Post:List-Unsubscribe:From; b=tCrXZLa8opJPMj2Bv7nozlNMOJuMbuMjglQ4vtggvE5Ghde2pz8PtjaEcZbK1j78D l5FAzR/kEQR+BMnoywQUTnZdwOPI0ZjfLhPe6bsF+SAppcgS/bcOCDOKyfi6RCW4jd tGoS1zsNoCLOpO2ewOqPvgo+pT4H2HehXlrI/FU8= From: Gorry Fairhurst Reply-To: quicwg/base-drafts To: quicwg/base-drafts Cc: Subscribed Message-ID: In-Reply-To: References: Subject: Re: [quicwg/base-drafts] ICMP and ICMPv6 PMTUD with asymmetric connection-ids (#1243) Mime-Version: 1.0 Content-Type: multipart/alternative; boundary="--==_mimepart_5b373af46a43c_241e3faaa7a4af8811432"; charset=UTF-8 Content-Transfer-Encoding: 7bit Precedence: list X-GitHub-Sender: gorryfair X-GitHub-Recipient: quic-issues X-GitHub-Reason: subscribed X-Auto-Response-Suppress: All X-GitHub-Recipient-Address: quic-issues@ietf.org Archived-At: X-BeenThere: quic-issues@ietf.org X-Mailman-Version: 2.1.26 List-Id: Notification list for GitHub issues related to the QUIC WG List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sat, 30 Jun 2018 08:10:32 -0000 ----==_mimepart_5b373af46a43c_241e3faaa7a4af8811432 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: quoted-printable Just to be sure myself .. how does that help a QUIC sender to process a = PTB ICMP message? Gorry = > On 29 Jun 2018, at 21:15, Igor Lubashev wrot= e: > = > ICMP and Load Balancers is a generic problem, but QUIC has some protoco= l elements specifically designed to help load balancers (Server CID). It = stands to reason that enable those protocol elements to help with ICMP pr= ocessing in QUIC context. > = > @martinduke, which workarounds do you have in mind (unless it is PLPMTU= D)? PLPMTUD, for example, specifically states that it works most efficien= tly with ICMP. So this issue is about enabling ICMP to for for PMTU in th= e presence of load balancers. > = > =E2=80=94 > You are receiving this because you were mentioned. > Reply to this email directly, view it on GitHub, or mute the thread. -- = 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/1243#issuecomment-401525861= ----==_mimepart_5b373af46a43c_241e3faaa7a4af8811432 Content-Type: text/html; charset=UTF-8 Content-Transfer-Encoding: quoted-printable Just to be sure myself .. how does that help a QUIC sender to process a = PTB ICMP message?

Gorry

> On 29 Jun 2018, at 21:15, Igor Lubashev <notifications@github.com= > wrote:
>
> ICMP and Load Balancers is a generic problem, but QUIC has some prot= ocol elements specifically designed to help load balancers (Server CID). = It stands to reason that enable those protocol elements to help with ICMP= processing in QUIC context.
>
> @martinduke, which workarounds do you have in mind (unless it is PLP= MTUD)? PLPMTUD, for example, specifically states that it works most effic= iently with ICMP. So this issue is about enabling ICMP to for for PMTU in= the presence of load balancers.
>
> =E2=80=94
> You are receiving this because you were mentioned.
> Reply to this email directly, view it on GitHub, or mute the thread.=

&m= dash;
You are receiving this because you are subscribed to this thre= ad.
Reply to this email directly, view it on GitHub,= or mute the thread.3D""

= ----==_mimepart_5b373af46a43c_241e3faaa7a4af8811432--