Error reporting on handshake
Jānis Čoders <janis.coders@gmail.com> Wed, 13 September 2017 13:26 UTC
Return-Path: <janis.coders@gmail.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 68D76133030 for <quic@ietfa.amsl.com>; Wed, 13 Sep 2017 06:26:18 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.7
X-Spam-Level:
X-Spam-Status: No, score=-2.7 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, FREEMAIL_FROM=0.001, RCVD_IN_DNSWL_LOW=-0.7, SPF_PASS=-0.001] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (2048-bit key) header.d=gmail.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 uKjaiUDo6PwS for <quic@ietfa.amsl.com>; Wed, 13 Sep 2017 06:26:17 -0700 (PDT)
Received: from mail-it0-x230.google.com (mail-it0-x230.google.com [IPv6:2607:f8b0:4001:c0b::230]) (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 5197A13303A for <quic@ietf.org>; Wed, 13 Sep 2017 06:26:17 -0700 (PDT)
Received: by mail-it0-x230.google.com with SMTP id v19so2231040ite.0 for <quic@ietf.org>; Wed, 13 Sep 2017 06:26:17 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20161025; h=mime-version:from:date:message-id:subject:to :content-transfer-encoding; bh=c6Vb7JCH1cUyyNJl2HkvQCaBcyZ4ovqkij37JVD5Luo=; b=DOwBDLA7WlF3iiNfIBDzENKDZz7vGRHnySmr3bbmDSJwpYIDWEv+Z1g3dcUKFQBAL+ 9ePjRQfk2EI9H4zCFfdLH3Gtqk4ADERCFGoHiGXZJDGGVTLpvkagrBDISXS5/m32JpVf m5RaEJZC12V4pTwt4GL1wWNNEHim6Qeb5h5w+ppm1bx1UgMM/7aT0gcmQ1SVK5WlPkNf Jtd4Gj1BDCGurYqcMRTSrzwNLIPqcLPc4n+DDcS4peYlWapBlO/F4ZmaYR5U7LP2Wmks IcNUL8DfvjIQO3KjmhFdpK/uhA0jrAlLi9536J+gw1vEOjLx/dRvaN1iwbjjn8Uu16bn PncA==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:mime-version:from:date:message-id:subject:to :content-transfer-encoding; bh=c6Vb7JCH1cUyyNJl2HkvQCaBcyZ4ovqkij37JVD5Luo=; b=Qo3DXktBgM0deokOwuq9wiLixuPWY4OTXtwbz0+FPL2jsQBaJA114eqxtLjnugEWiM GQVO52Axnb4G07MuvNBQuoS08/33pzBtbZKmbOh/eY7UigvUi/UrWD+AX9Cfq5kyEtJC v+N+pkOriiNdOrBMMVLXDP/KgraqY1HFS0ZH6Nn+oPUKRnWYOxd2abgs6Z1TxGeVdoiM hmQbzodPB+Lx5uCNREa1eGw9OJNBkoguFrrw9JQH9TuY5veyk4LPJ8zB2bC49dw0GaXf /e5ec1GvHDQdOcjwOokOH19XdRFNCU/f586+/rJDFrfnHyeLhDcy6plMe+vFG179C7eZ dwqg==
X-Gm-Message-State: AHPjjUg3bNIPnvD8Armw3Xq8UbFDd57DzlnzuJayU4b41FDZoZ+5jTOd WE+nG3ybCaFuzZTXqDlsqEwiPGcn/8u3XDLma+s=
X-Google-Smtp-Source: AOwi7QClEKQpnvHTxvxiZPBCUX3iaXe3ul4c9xXR1zSDBbveu7n2Ch2vNSASfy+vcwUzXxUek+CXi+vnRppIb56fJ90=
X-Received: by 10.36.86.18 with SMTP id o18mr3769287itb.32.1505309176439; Wed, 13 Sep 2017 06:26:16 -0700 (PDT)
MIME-Version: 1.0
Received: by 10.79.124.148 with HTTP; Wed, 13 Sep 2017 06:26:16 -0700 (PDT)
From: Jānis Čoders <janis.coders@gmail.com>
Date: Wed, 13 Sep 2017 16:26:16 +0300
Message-ID: <CA+tEvRS1cC8tk2QBUnq6dUK14eV3heG3CSpRtdYeA2TtNHMTXA@mail.gmail.com>
Subject: Error reporting on handshake
To: QUIC WG <quic@ietf.org>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
Archived-At: <https://mailarchive.ietf.org/arch/msg/quic/qkNQmcO2iObskzfEfKrUfA6FIMg>
X-BeenThere: quic@ietf.org
X-Mailman-Version: 2.1.22
Precedence: list
List-Id: Main mailing list of the IETF QUIC working group <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: Wed, 13 Sep 2017 13:26:18 -0000
Hi, how should QUIC server respond while performing TLS handshake and there is a server internal error - too many parallel authentications, no memory or other? Should it respond with ConnectionClose Frame encapsulated into LongHeader-ServerCleartext or some other? Thank you -- Ar cieņu, Jānis Čoders
- Error reporting on handshake Jānis Čoders
- Re: Error reporting on handshake Jana Iyengar
- Re: Error reporting on handshake Patrick McManus
- Re: Error reporting on handshake Jānis Čoders