Re: [core] 🔔 WGLC of draft-ietf-core-too-many-reqs-02
Jim Schaad <ietf@augustcellars.com> Thu, 05 July 2018 16:48 UTC
Return-Path: <ietf@augustcellars.com>
X-Original-To: core@ietfa.amsl.com
Delivered-To: core@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 0D231130E19 for <core@ietfa.amsl.com>; Thu, 5 Jul 2018 09:48:49 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.901
X-Spam-Level:
X-Spam-Status: No, score=-1.901 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RCVD_IN_DNSWL_NONE=-0.0001, SPF_PASS=-0.001] autolearn=ham autolearn_force=no
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 1mT0kKPbeGvA for <core@ietfa.amsl.com>; Thu, 5 Jul 2018 09:48:47 -0700 (PDT)
Received: from mail2.augustcellars.com (augustcellars.com [50.45.239.150]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-SHA384 (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id B7C69130E6C for <core@ietf.org>; Thu, 5 Jul 2018 09:48:46 -0700 (PDT)
Received: from Jude (73.180.8.170) by mail2.augustcellars.com (192.168.0.56) with Microsoft SMTP Server (TLS) id 15.0.1347.2; Thu, 5 Jul 2018 09:45:32 -0700
From: Jim Schaad <ietf@augustcellars.com>
To: 'Carsten Bormann' <cabo@tzi.org>
CC: 'Core' <core@ietf.org>
References: <8EEE411B-6268-4103-9F5F-681D21E1AD48@tzi.org> <008c01d41462$44c26c90$ce4745b0$@augustcellars.com> <573D4219-72C7-425F-A9FA-D2A8A4093310@tzi.org>
In-Reply-To: <573D4219-72C7-425F-A9FA-D2A8A4093310@tzi.org>
Date: Thu, 05 Jul 2018 09:48:38 -0700
Message-ID: <00a601d41480$074aa990$15dffcb0$@augustcellars.com>
MIME-Version: 1.0
Content-Type: text/plain; charset="utf-8"
Content-Transfer-Encoding: quoted-printable
X-Mailer: Microsoft Outlook 16.0
Content-Language: en-us
Thread-Index: AQJt7qfOLfP6zXhio7jvHWj1sBbapgGLD0UXAccAZY+jMpIJUA==
X-Originating-IP: [73.180.8.170]
Archived-At: <https://mailarchive.ietf.org/arch/msg/core/W_F9xvsaG2AUNIQpsQrGlxAPg5g>
Subject: Re: [core] 🔔 WGLC of draft-ietf-core-too-many-reqs-02
X-BeenThere: core@ietf.org
X-Mailman-Version: 2.1.26
Precedence: list
List-Id: "Constrained RESTful Environments \(CoRE\) Working Group list" <core.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/core>, <mailto:core-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/core/>
List-Post: <mailto:core@ietf.org>
List-Help: <mailto:core-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/core>, <mailto:core-request@ietf.org?subject=subscribe>
X-List-Received-Date: Thu, 05 Jul 2018 16:48:49 -0000
> -----Original Message----- > From: Carsten Bormann <cabo@tzi.org> > Sent: Thursday, July 5, 2018 9:39 AM > To: Jim Schaad <ietf@augustcellars.com> > Cc: Core <core@ietf.org> > Subject: Re: [core] 🔔 WGLC of draft-ietf-core-too-many-reqs-02 > > On Jul 5, 2018, at 15:15, Jim Schaad <ietf@augustcellars.com> wrote: > > > > Note that a client could get this as a response even on its first request if the > path to the server goes through a proxy agent. > > Which strikes me as moderately appropriate — after all, the client is “part of > the problem”. I understand this, however it means that a client might get this response even though it had never sent a message to the server before. This might be considered to be unexpected behavior. Jim > > Grüße, Carsten
- Re: [core] 🔔 WGLC of draft-ietf-core-too-many-req… Ari Keränen
- Re: [core] 🔔 WGLC of draft-ietf-core-too-many-req… Michael Koster
- Re: [core] 🔔 WGLC of draft-ietf-core-too-many-req… Klaus Hartke
- [core] 🔔 WGLC of draft-ietf-core-too-many-reqs-02 Carsten Bormann
- Re: [core] 🔔 WGLC of draft-ietf-core-too-many-req… Jim Schaad
- Re: [core] 🔔 WGLC of draft-ietf-core-too-many-req… Jim Schaad
- Re: [core] 🔔 WGLC of draft-ietf-core-too-many-req… Carsten Bormann