IETF Logo Mail Archive

[quicwg/base-drafts] Does any portion of the QUIC framing require 4 byte alignment? (#292)

ianswett <notifications@github.com> Sun, 12 February 2017 17:17 UTC

Return-Path: <bounces+848413-a050-quic-issues=ietf.org@sgmail.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 881A7129994 for <quic-issues@ietfa.amsl.com>; Sun, 12 Feb 2017 09:17:50 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -0.403
X-Spam-Level:
X-Spam-Status: No, score=-0.403 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, RCVD_IN_DNSWL_NONE=-0.0001, RCVD_IN_MSPIKE_H4=-0.01, RCVD_IN_MSPIKE_WL=-0.01, RP_MATCHES_RCVD=-0.001, SPF_PASS=-0.001] autolearn=no 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 0FtzZRphq5Lx for <quic-issues@ietfa.amsl.com>; Sun, 12 Feb 2017 09:17:48 -0800 (PST)
Received: from o7.sgmail.github.com (o7.sgmail.github.com [167.89.101.198]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 6A743129953 for <quic-issues@ietf.org>; Sun, 12 Feb 2017 09:17:48 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha1; c=relaxed/relaxed; d=github.com; h=from:reply-to:to:cc:subject:mime-version:content-type:content-transfer-encoding:list-id:list-archive:list-post:list-unsubscribe; s=s20150108; bh=fkPMjKzvp/WrnpEOsX7C2rVbR8E=; b=mGRBilWUE5U/prtr +U83XuEhS74hAO7atPFE7rrQLO/RhstL2zriU0NOZG8nQdw98obENulQpbv4Ndn2 duG9gIBReMJfKBrSnRSELGPN2J5nmr72Y8DghBeiNUZJZ5yf2rCq/JhdE8frfV2z AHL6XRBMYTkJQS/j4gK+G+653k4=
Received: by filter0650p1mdw1.sendgrid.net with SMTP id filter0650p1mdw1-26472-58A098BA-19 2017-02-12 17:17:46.302403591 +0000 UTC
Received: from github-smtp2a-ext-cp1-prd.iad.github.net (github-smtp2a-ext-cp1-prd.iad.github.net [192.30.253.16]) by ismtpd0004p1iad1.sendgrid.net (SG) with ESMTP id NZ83Yh8GSWym-xDVciEV8A for <quic-issues@ietf.org>; Sun, 12 Feb 2017 17:17:46.242 +0000 (UTC)
Date: Sun, 12 Feb 2017 09:17:46 -0800
From: ianswett <notifications@github.com>
To: quicwg/base-drafts <base-drafts@noreply.github.com>
Message-ID: <quicwg/base-drafts/issues/292@github.com>
Subject: [quicwg/base-drafts] Does any portion of the QUIC framing require 4 byte alignment? (#292)
Mime-Version: 1.0
Content-Type: multipart/alternative; boundary="--==_mimepart_58a098ba26ddd_12083f9525a0114018339a"; 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
X-SG-EID: l64QuQ2uJCcEyUykJbxN122A6QRmEpucztpreh3Pak0PMY37p8NU9EHRib9Yol2ClZoESgIDI6Qfeq HxF2tmT3L0SJ4rkZOLkZ67xJkC+wzTB0Bk/o3xMdUIjIKqPxpGJdEs4Vq1MgmcCqbdw/LMqltpp6WB BydhsmUKWT6dEBi8s/mRJZ5M1AGIuPQvuc9kdddkr34SdkPQo2WNYjXpWLR3kR1jsmwhEg7s/+gGN9 U=
Archived-At: <https://mailarchive.ietf.org/arch/msg/quic-issues/D8IJabnBSPowA8Ttl9PA8KuDQ1M>
Cc: Subscribed <subscribed@noreply.github.com>
X-BeenThere: quic-issues@ietf.org
X-Mailman-Version: 2.1.17
Reply-To: quic@ietf.org
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: Sun, 12 Feb 2017 17:17:50 -0000

@martinthomson Wrote up a public header proposal that implies 4 byte alignment is an important goal of the public header.

Is it necessary, as it does constrain the design space substantially?  And if there are environments it's necessary, is it only a requirement for non-endpoint devices(aka middleboxes), so only applies to the non-protected portion of the packet.

-- 
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/292

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