IETF Logo Mail Archive

Re: Unidirectional streams PR

Martin Thomson <martin.thomson@gmail.com> Fri, 07 July 2017 01:05 UTC

Return-Path: <martin.thomson@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 38D60131545 for <quic@ietfa.amsl.com>; Thu, 6 Jul 2017 18:05:46 -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 bOR2_bRM6atz for <quic@ietfa.amsl.com>; Thu, 6 Jul 2017 18:05:42 -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 890B0131559 for <quic@ietf.org>; Thu, 6 Jul 2017 18:05:42 -0700 (PDT)
Received: by mail-it0-x230.google.com with SMTP id m68so18628473ith.1 for <quic@ietf.org>; Thu, 06 Jul 2017 18:05:42 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20161025; h=mime-version:in-reply-to:references:from:date:message-id:subject:to :cc; bh=l2NuHp5HQtmOnLMMr7pWfxyQU/hi6a6VmXCYmZVt7JY=; b=kQXqU9Z9I4u7qszKod353KY333wfZrYs5p3bqYaGraVaalHiCJv3I35lFKYVkhCIet 27sy3nIdHYmob2LOi1ae2gMeKBU0jEedLAoevq+3qY9EcrhJ75Nd9sfDv4XSss4+v67L iYo3pW7gPkS521cXDX2hkLeDmWFO5Dq/mW/nIrz5gNLVWY60Kj1tgdAvPtjTYG2qlEoQ 9JGkjqjiRnx+nFhFlEhtmz1CNAr3uUjFea8FAC4Fe5k2yq8Wl1fJD1DU4+gbEJ+J26AK VYErUB85QZnctDzGIC1v8D9N9alb/Hqwzmt7AY4ZcTEhXHanZODufjFwYnLDxH/2Qcjf sLeg==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:mime-version:in-reply-to:references:from:date :message-id:subject:to:cc; bh=l2NuHp5HQtmOnLMMr7pWfxyQU/hi6a6VmXCYmZVt7JY=; b=Wuvzf0LEWRk27LzKq+0KIkkCN1V4rbgKJ4D2wV/wwv3XoEHYmjvEsuQotOmGGpDMEA J1dMOQYagPbdIqY3+yOp88x3WG4juToLIYa37hyF1AKlikFud33ieSWOtuu+PYcEdmd9 Eqma00Is5EaQ9GH96TUGP2+v7YV8IkH0Ax3wBwAdlLH03pbej+0qcmC+dKqhFC/hm8Va 1ZnqxcvkQ96ufqcRhA4E/O4yd/HDOonSko8bmt62QlAiPMhDy/Lw7p+N3cspkBi7Pf8B sOzTlwVYeHNfRH7rj62eoo52OSgN1W4y8vUXab8nyyc5lAZN2/ZUeJIAgK2yetsL4rtp uCKA==
X-Gm-Message-State: AIVw110f2U3ol+1+qg/H0CVKBDDt5n43r7hrYOGeLT2WqsXPxSmZ/tlc /xgyyB6WWioBK5L4VP1e9TI+wCADig==
X-Received: by 10.36.236.4 with SMTP id g4mr744911ith.60.1499389541981; Thu, 06 Jul 2017 18:05:41 -0700 (PDT)
MIME-Version: 1.0
Received: by 10.107.129.162 with HTTP; Thu, 6 Jul 2017 18:05:41 -0700 (PDT)
In-Reply-To: <CANatvzzN6sQ2Pqb4jkQyZAY-KUYDb_J2sbW=K0zrQ0LCTJ2NVw@mail.gmail.com>
References: <CABkgnnW+veDVq27v+wTz0cA=eGPRTLQ1A90A0ynHLPU88Pg77Q@mail.gmail.com> <CANatvzzN6sQ2Pqb4jkQyZAY-KUYDb_J2sbW=K0zrQ0LCTJ2NVw@mail.gmail.com>
From: Martin Thomson <martin.thomson@gmail.com>
Date: Fri, 07 Jul 2017 11:05:41 +1000
Message-ID: <CABkgnnV9JzZG6HY_y_pxSRSUwX3ocxv7L0UCaiuaJs1sMfPWcg@mail.gmail.com>
Subject: Re: Unidirectional streams PR
To: Kazuho Oku <kazuhooku@gmail.com>
Cc: QUIC WG <quic@ietf.org>
Content-Type: text/plain; charset="UTF-8"
Archived-At: <https://mailarchive.ietf.org/arch/msg/quic/g9yWyVnj0RZ721RXjlC2L4GUHlU>
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: Fri, 07 Jul 2017 01:05:46 -0000

On 7 July 2017 at 10:57, Kazuho Oku <kazuhooku@gmail.com> wrote:
> Could somebody clarify what a server is expected to do when there are
> no more streams than can be used to send a response (i.e. when a
> server has used all the Stream IDs up to 2^32-2 and then receives a
> request)?

I think that the only sensible approach is to give up on the
connection before this point is reached.

A client can't know exactly how many streams a server has open, so I
think that the only sensible course of action is to initiate graceful
shutdown whenever the endpoint might be inclined to MAX_STREAM_ID that
is 2^32-1 or greater.

(In the PR, the limit is 2^32-1.)

v2.23.0 | Report a Bug | By Email