Re: [quicwg/base-drafts] Consistent presenting Connection ID in packet or frame (#1336)

ianswett <notifications@github.com> Fri, 04 May 2018 14:29 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 85935127876 for <quic-issues@ietfa.amsl.com>; Fri, 4 May 2018 07:29:47 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -6.392
X-Spam-Level:
X-Spam-Status: No, score=-6.392 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, HTML_IMAGE_ONLY_24=1.618, HTML_MESSAGE=0.001, MAILING_LIST_MULTI=-1, RCVD_IN_DNSWL_HI=-5, SPF_PASS=-0.001, T_DKIMWL_WL_HIGH=-0.01] 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 wgt8HjfkaUIC for <quic-issues@ietfa.amsl.com>; Fri, 4 May 2018 07:29:46 -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 C20BD12426E for <quic-issues@ietf.org>; Fri, 4 May 2018 07:29:45 -0700 (PDT)
Date: Fri, 04 May 2018 07:29:44 -0700
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=github.com; s=pf2014; t=1525444184; bh=uISG4ou05+e46ogg62YW29VpTAOw8s/flSeU9RmGPxY=; h=Date:From:Reply-To:To:Cc:In-Reply-To:References:Subject:List-ID: List-Archive:List-Post:List-Unsubscribe:From; b=R5T6/a0p2HnM4UsZaoJoo6MAp/MYQkbiHFPaaa66LCGLDTbFmq1LbBIKvkW9/xqtz M/bohFlTZ0Z7bXOpq96tiI9u0bMUxpbWrc5IVYf46U7Gs1L8FTCNVtyZ6g5jz7G3Rr DHo8CU0d26iIJDNe5FA1pAJ8NLOKfvXMEK11OWSY=
From: ianswett <notifications@github.com>
Reply-To: quicwg/base-drafts <reply+0166e4abf56dc0a995e2a1147505148e61d93fa9ab164b6d92cf000000011704305892a169ce131475f5@reply.github.com>
To: quicwg/base-drafts <base-drafts@noreply.github.com>
Cc: Subscribed <subscribed@noreply.github.com>
Message-ID: <quicwg/base-drafts/issues/1336/386619380@github.com>
In-Reply-To: <quicwg/base-drafts/issues/1336@github.com>
References: <quicwg/base-drafts/issues/1336@github.com>
Subject: Re: [quicwg/base-drafts] Consistent presenting Connection ID in packet or frame (#1336)
Mime-Version: 1.0
Content-Type: multipart/alternative; boundary="--==_mimepart_5aec6e58e80a6_30922b11de5fef5498093"; charset="UTF-8"
Content-Transfer-Encoding: 7bit
Precedence: list
X-GitHub-Sender: ianswett
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/GvBzTeZUQbHQrwpS70JumG71AZs>
X-BeenThere: quic-issues@ietf.org
X-Mailman-Version: 2.1.22
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: Fri, 04 May 2018 14:29:47 -0000

Not using a connection ID on the server side in that case seems pretty brittle.  The QUIC design includes CIDs partially for NAT rebinds, so the server would be implicitly deciding it didn't care about NAT rebinds.  If it decided it'd rather reset connections than deal with NAT rebinds, that's certainly a choice it can make.

-- 
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/1336#issuecomment-386619380