Re: [quicwg/base-drafts] Clarify simultaneous path validation (#3932)
Mike Bishop <notifications@github.com> Mon, 10 August 2020 18:59 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 258523A0B3A for <quic-issues@ietfa.amsl.com>; Mon, 10 Aug 2020 11:59:14 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.009
X-Spam-Level:
X-Spam-Status: No, score=-2.009 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIMWL_WL_HIGH=-0.001, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, DKIM_VALID_EF=-0.1, HTML_IMAGE_ONLY_16=1.092, HTML_MESSAGE=0.001, MAILING_LIST_MULTI=-1, RCVD_IN_MSPIKE_H2=-0.001, SPF_HELO_NONE=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 sFdUNsu4ky8U for <quic-issues@ietfa.amsl.com>; Mon, 10 Aug 2020 11:59:13 -0700 (PDT)
Received: from out-26.smtp.github.com (out-26.smtp.github.com [192.30.252.209]) (using TLSv1.2 with cipher ADH-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 014483A0B39 for <quic-issues@ietf.org>; Mon, 10 Aug 2020 11:59:12 -0700 (PDT)
Received: from github-lowworker-1b8c660.ash1-iad.github.net (github-lowworker-1b8c660.ash1-iad.github.net [10.56.18.59]) by smtp.github.com (Postfix) with ESMTP id 97E775E0ECB for <quic-issues@ietf.org>; Mon, 10 Aug 2020 11:59:11 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=github.com; s=pf2014; t=1597085951; bh=FOYKSbCJckTpubDNuvooVO97aqKYQa1Mz3RLpoluD0U=; h=Date:From:Reply-To:To:Cc:In-Reply-To:References:Subject:List-ID: List-Archive:List-Post:List-Unsubscribe:From; b=RltZaaxAJyox+Lfey65oKCGHK1tfX0E5KV4OFEYt4nGgDDJUbcHqRW00ZiOj4m3Nq DPeFqt6Xi1lzwak9kSiaD8CjhvQkQPd4Qqkata+XZDB95gkFW/W0NfCq36VSW8rmt3 e/iK9vkUs9giy6HLCEXI7e4nTRnBT13xLu1Kmf9U=
Date: Mon, 10 Aug 2020 11:59:11 -0700
From: Mike Bishop <notifications@github.com>
Reply-To: quicwg/base-drafts <reply+AFTOJK2PMRLJS3EXHWYQNVF5HV477EVBNHHCPCRAZE@reply.github.com>
To: quicwg/base-drafts <base-drafts@noreply.github.com>
Cc: Subscribed <subscribed@noreply.github.com>
Message-ID: <quicwg/base-drafts/issues/3932/671530292@github.com>
In-Reply-To: <quicwg/base-drafts/issues/3932@github.com>
References: <quicwg/base-drafts/issues/3932@github.com>
Subject: Re: [quicwg/base-drafts] Clarify simultaneous path validation (#3932)
Mime-Version: 1.0
Content-Type: multipart/alternative; boundary="--==_mimepart_5f3198ff8735a_34ba16f81944d3"; charset="UTF-8"
Content-Transfer-Encoding: 7bit
Precedence: list
X-GitHub-Sender: MikeBishop
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/ZlmHcmbVdMk_lEoft8oi4geZWcs>
X-BeenThere: quic-issues@ietf.org
X-Mailman-Version: 2.1.29
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: Mon, 10 Aug 2020 18:59:14 -0000
Note that while the server needs to respond to the probes (so the client can validate the paths), I don't think there's any requirement that the server continue to regard all those paths as validated. When the client actually migrates, if the server wants to treat the migration as an unvalidated path and initiate validation again, that seems fine. -- 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/3932#issuecomment-671530292
- [quicwg/base-drafts] Servers are not expected to … ianswett
- Re: [quicwg/base-drafts] Servers are not expected… Marten Seemann
- Re: [quicwg/base-drafts] Servers are not expected… Kazuho Oku
- Re: [quicwg/base-drafts] Servers are not expected… Eric Kinnear
- Re: [quicwg/base-drafts] Servers are not expected… ianswett
- Re: [quicwg/base-drafts] Servers are not expected… ianswett
- Re: [quicwg/base-drafts] Servers are not expected… Eric Kinnear
- Re: [quicwg/base-drafts] Servers are not expected… Kazuho Oku
- Re: [quicwg/base-drafts] Clarify simultaneous pat… David Schinazi
- Re: [quicwg/base-drafts] Clarify simultaneous pat… Mike Bishop
- Re: [quicwg/base-drafts] Clarify simultaneous pat… Martin Thomson
- Re: [quicwg/base-drafts] Clarify simultaneous pat… Martin Thomson
- Re: [quicwg/base-drafts] Clarify simultaneous pat… ianswett
- Re: [quicwg/base-drafts] Clarify simultaneous pat… Lars Eggert
- Re: [quicwg/base-drafts] Clarify simultaneous pat… ianswett
- Re: [quicwg/base-drafts] Clarify simultaneous pat… Christian Huitema
- Re: [quicwg/base-drafts] Clarify simultaneous pat… Lars Eggert
- Re: [quicwg/base-drafts] Clarify simultaneous pat… ianswett