IETF Logo Mail Archive

Re: [quicwg/base-drafts] Coalescing different CIDs for same connection (#3800)

Tatsuhiro Tsujikawa <notifications@github.com> Wed, 15 July 2020 15:39 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 077983A03ED for <quic-issues@ietfa.amsl.com>; Wed, 15 Jul 2020 08:39:48 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.574
X-Spam-Level:
X-Spam-Status: No, score=-1.574 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_20=1.546, HTML_MESSAGE=0.001, MAILING_LIST_MULTI=-1, RCVD_IN_MSPIKE_H3=-0.01, RCVD_IN_MSPIKE_WL=-0.01, 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 iUqRx67CrGeN for <quic-issues@ietfa.amsl.com>; Wed, 15 Jul 2020 08:39:46 -0700 (PDT)
Received: from out-11.smtp.github.com (out-11.smtp.github.com [192.30.254.194]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id A01F23A02C1 for <quic-issues@ietf.org>; Wed, 15 Jul 2020 08:39:46 -0700 (PDT)
Received: from github-lowworker-f144ac1.va3-iad.github.net (github-lowworker-f144ac1.va3-iad.github.net [10.48.16.59]) by smtp.github.com (Postfix) with ESMTP id 15219260197 for <quic-issues@ietf.org>; Wed, 15 Jul 2020 08:39:46 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=github.com; s=pf2014; t=1594827586; bh=wp0lt7scCJnLl5xawMke2fWPgqnIrvfL8l01COsY8co=; h=Date:From:Reply-To:To:Cc:In-Reply-To:References:Subject:List-ID: List-Archive:List-Post:List-Unsubscribe:From; b=XaqenDean8Hu0fChQWmNTr5eomvHn3S8Fsu95pftaXxXaSfa4BDHIrFgzv7+hEWlm titQki6cH72arH4/0zWwe4eTfUVSoQbHuq6RS5nnn5GQ3A3nfxzVa/TLL+njdCPVGk EHJotUCRw+kUvbDQ46hDvZ6dkQMwLh5RTCCTkEY4=
Date: Wed, 15 Jul 2020 08:39:45 -0700
From: Tatsuhiro Tsujikawa <notifications@github.com>
Reply-To: quicwg/base-drafts <reply+AFTOJK2ZVXD2SC5DRSD2R5F5DMCEDEVBNHHCNJ65QE@reply.github.com>
To: quicwg/base-drafts <base-drafts@noreply.github.com>
Cc: Subscribed <subscribed@noreply.github.com>
Message-ID: <quicwg/base-drafts/issues/3800/658836551@github.com>
In-Reply-To: <quicwg/base-drafts/issues/3800@github.com>
References: <quicwg/base-drafts/issues/3800@github.com>
Subject: Re: [quicwg/base-drafts] Coalescing different CIDs for same connection (#3800)
Mime-Version: 1.0
Content-Type: multipart/alternative; boundary="--==_mimepart_5f0f2341c36a5_1bfe3fa0ff6cd95c8105"; charset="UTF-8"
Content-Transfer-Encoding: 7bit
Precedence: list
X-GitHub-Sender: tatsuhiro-t
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/GZSMQohx6FHI8JUbDee5y_CY5IE>
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: Wed, 15 Jul 2020 15:39:48 -0000

In my implementation, ngtcp2, it processes packet in the way that PR #3870 proposes; which means I just over looked existing text, but anyway, I think that processing a packet atomically is cleaner approach in implementation wise rather than passing a some kind of pointer to the very first packet header.

-- 
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/3800#issuecomment-658836551

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