[QUIC] New set of QUIC drafts
Jana Iyengar <jri@google.com> Fri, 08 July 2016 22:53 UTC
Return-Path: <jri@google.com>
X-Original-To: quic@ietfa.amsl.com
Delivered-To: quic@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 891F912D1D5 for <quic@ietfa.amsl.com>; Fri, 8 Jul 2016 15:53:32 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -4.126
X-Spam-Level:
X-Spam-Status: No, score=-4.126 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, RCVD_IN_DNSWL_LOW=-0.7, RP_MATCHES_RCVD=-1.426, SPF_PASS=-0.001] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (2048-bit key) header.d=google.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 JmRtPTAS04CO for <quic@ietfa.amsl.com>; Fri, 8 Jul 2016 15:53:30 -0700 (PDT)
Received: from mail-yw0-x22f.google.com (mail-yw0-x22f.google.com [IPv6:2607:f8b0:4002:c05::22f]) (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 8E77712B050 for <quic@ietf.org>; Fri, 8 Jul 2016 15:53:30 -0700 (PDT)
Received: by mail-yw0-x22f.google.com with SMTP id j17so49190392ywg.0 for <quic@ietf.org>; Fri, 08 Jul 2016 15:53:30 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=google.com; s=20120113; h=mime-version:from:date:message-id:subject:to; bh=j27an4Ww4Xu/dLhlBm7ybsUAGD2FEu99ekyvibKoWlo=; b=fxo41AEX2KeSKUp4Dc/jNcd9GJEnoB+wIdytGp2C2VOKU1jTEAcwhWWBso1s/pAdqX 26IVCugaQmGQRLEdy1JtvRRaX0LTDlOzm8nvaXQeqCk36iAvlTYfi6y57vYartQWvKqW AH4RNBiECatpU3R0O7VJtMh1zNUA0Azktq2mh0tPFLlf+yFOydxNii+TyQxDt/X6iA/R mxv0CyBM+TE7Elcl23NZuOMtoI+adqdwXPcx12VzMJmkzUQAsSYZJog36g6qnMhmJgOA BVjFJGIsG/HbEbJkxPRHorNUlBlZaSAJ9YXf5OUcWF2YQvb0+ZwOyrG+1MyUkyPeJf55 uETA==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20130820; h=x-gm-message-state:mime-version:from:date:message-id:subject:to; bh=j27an4Ww4Xu/dLhlBm7ybsUAGD2FEu99ekyvibKoWlo=; b=P+LQrHeF/ur5ID9+kp7xW4Avq1g75syzpRlNgSusFeJnq7XHcYQlkWt0dcEq6d7Jr4 ke8xplHo5I7lKCaxfrZreZsoQP+XBUazVL+L/Dltmv0xOM5wZcoGiZjxTHur5JkxB922 fb2iZkUd4NViKYhkGyhvniM/htp7ZXcmufN4zW76tAvIskEya3YKaFSbHs1S7BEza49p m9dMmDkS7QOoE2MVr7q2GKLcdrOsYw0arFLX+25B3H8FyLk7BdrjrA8l8vtRabBs4eGt 1q5pPfPKONY9+o89OFeRrNvTQ7THWO3lwq/Y3Tmat4NP4ePcS5icRFMrp/WvGopMYyTf EWWg==
X-Gm-Message-State: ALyK8tI0pEW8AiPdMIF0nAFKOpHOoUky6RKHsykQskYmxWuQcACCXfkUWijJySiszXZ+GdL4UgQTymkxY0qgdaXV
X-Received: by 10.129.161.86 with SMTP id y83mr6145577ywg.190.1468018409602; Fri, 08 Jul 2016 15:53:29 -0700 (PDT)
MIME-Version: 1.0
Received: by 10.37.211.65 with HTTP; Fri, 8 Jul 2016 15:53:29 -0700 (PDT)
From: Jana Iyengar <jri@google.com>
Date: Fri, 08 Jul 2016 15:53:29 -0700
Message-ID: <CAGD1bZYWgZDkXhsdSVz9k47DiPjiW+TJomfZ9A1yeA6mAEzZ1g@mail.gmail.com>
To: quic@ietf.org
Content-Type: multipart/alternative; boundary="001a114f8d26d47c56053727abd1"
Archived-At: <https://mailarchive.ietf.org/arch/msg/quic/4fE0i5Yq22PQ4Bw9nuwb0fLa-E0>
Subject: [QUIC] New set of QUIC drafts
X-BeenThere: quic@ietf.org
X-Mailman-Version: 2.1.17
Precedence: list
List-Id: Mailing list to discuss QUIC standardization <quic.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/quic>, <mailto:quic-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/quic/>
List-Post: <mailto:quic@ietf.org>
List-Help: <mailto:quic-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/quic>, <mailto:quic-request@ietf.org?subject=subscribe>
X-List-Received-Date: Fri, 08 Jul 2016 22:53:32 -0000
Dear all, We have a new set of drafts that describes the various constituent parts of QUIC: QUIC transport protocol draft: https://datatracker.ietf.org/doc/draft-hamilton-quic-transport-protocol/ QUIC congestion control and loss recovery draft: https://datatracker.ietf.org/doc/draft-iyengar-quic-loss-recovery/ The use of QUIC as a transport for HTTP/2 is described in: https://datatracker.ietf.org/doc/draft-shade-quic-http2-mapping/ In addition, the use of TLS1.3 for QUIC's crypto handshake is described in: https://datatracker.ietf.org/doc/draft-thomson-quic-tls - jana (The earlier monolithic QUIC draft has been renamed, and is here: https://datatracker.ietf.org/doc/draft-hamilton-early-deployment-quic/)
- [QUIC] New set of QUIC drafts Jana Iyengar
- Re: [QUIC] draft-shade-quic-http2-mapping comments Martin Thomson
- Re: [QUIC] draft-shade-quic-http2-mapping comments Mark Nottingham
- [QUIC] draft-shade-quic-http2-mapping comments Julian Reschke