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 489561271FF for ; Tue, 3 Jul 2018 21:11:55 -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 MP17Gg9roMcv for ; Tue, 3 Jul 2018 21:11:53 -0700 (PDT) Received: from out-1.smtp.github.com (out-1.smtp.github.com [192.30.252.192]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 53159130934 for ; Tue, 3 Jul 2018 21:11:53 -0700 (PDT) Date: Tue, 03 Jul 2018 21:11:52 -0700 DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=github.com; s=pf2014; t=1530677512; bh=gskFYEwtMijAjYe74dDdxayXQ4vZKS/nVmVdTZEwhiM=; h=Date:From:Reply-To:To:Cc:In-Reply-To:References:Subject:List-ID: List-Archive:List-Post:List-Unsubscribe:From; b=iRHXsBwwMyr1a3npBGXLqPY12voW4kvxVbn7xkB0kBk6vqVyN8Nu34ka7VzM/YmOf gdkSsYl69zKgOES8PRcDZR41OZoQJoIld52aIocuQS9p3mheReZwreVZ36shmWLEq9 pK2nE9NgtiNo8sp3TuzWLSjyDiGDMeeZ1vdJxQ+g= From: Christian Huitema Reply-To: quicwg/base-drafts To: quicwg/base-drafts Cc: Subscribed Message-ID: In-Reply-To: References: Subject: Re: [quicwg/base-drafts] Make EOED transmission optional in QUIC, please (#1518) Mime-Version: 1.0 Content-Type: multipart/alternative; boundary="--==_mimepart_5b3c490855bb5_71172b1712580f58522472"; charset=UTF-8 Content-Transfer-Encoding: 7bit Precedence: list X-GitHub-Sender: huitema 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: Wed, 04 Jul 2018 04:11:56 -0000 ----==_mimepart_5b3c490855bb5_71172b1712580f58522472 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 7bit It really depends how you deal with retransmissions. In my code it is a huge pain. Of course I can find some contorted way to deal with it. But I hate that kind of stuff. As for the TLS 1.3 state machine, what does the EOED actually achieve? You cannot clear the 0-RTT encryption context until you are sure that all 0-RTT datagrams have been received. Do you just want to prove that the client could exercise the 0-RTT key? -- 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/1518#issuecomment-402357765 ----==_mimepart_5b3c490855bb5_71172b1712580f58522472 Content-Type: text/html; charset=UTF-8 Content-Transfer-Encoding: quoted-printable

It really depends how you deal with retransmissions. In my code it is = a huge pain. Of course I can find some contorted way to deal with it. But= I hate that kind of stuff.

As for the TLS 1.3 state machine, what does the EOED actually achieve?= You cannot clear the 0-RTT encryption context until you are sure that al= l 0-RTT datagrams have been received. Do you just want to prove that the = client could exercise the 0-RTT key?

&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_5b3c490855bb5_71172b1712580f58522472--