[core] Suresh Krishnan's No Objection on draft-ietf-core-block-19: (with COMMENT)
"Suresh Krishnan" <suresh.krishnan@ericsson.com> Wed, 20 April 2016 03:55 UTC
Return-Path: <suresh.krishnan@ericsson.com>
X-Original-To: core@ietf.org
Delivered-To: core@ietfa.amsl.com
Received: from ietfa.amsl.com (localhost [IPv6:::1]) by ietfa.amsl.com (Postfix) with ESMTP id BB03A12E177; Tue, 19 Apr 2016 20:55:47 -0700 (PDT)
MIME-Version: 1.0
Content-Type: text/plain; charset="utf-8"
Content-Transfer-Encoding: 7bit
From: Suresh Krishnan <suresh.krishnan@ericsson.com>
To: The IESG <iesg@ietf.org>
X-Test-IDTracker: no
X-IETF-IDTracker: 6.19.0
Auto-Submitted: auto-generated
Precedence: bulk
Message-ID: <20160420035547.31549.85944.idtracker@ietfa.amsl.com>
Date: Tue, 19 Apr 2016 20:55:47 -0700
Archived-At: <http://mailarchive.ietf.org/arch/msg/core/x-5LfkN7SS22Vf10elzFgru1xXo>
Cc: draft-ietf-core-block@ietf.org, core-chairs@ietf.org, core@ietf.org
Subject: [core] Suresh Krishnan's No Objection on draft-ietf-core-block-19: (with COMMENT)
X-BeenThere: core@ietf.org
X-Mailman-Version: 2.1.17
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: Wed, 20 Apr 2016 03:55:48 -0000
Suresh Krishnan has entered the following ballot position for draft-ietf-core-block-19: No Objection When responding, please keep the subject line intact and reply to all email addresses included in the To and CC lines. (Feel free to cut this introductory paragraph, however.) Please refer to https://www.ietf.org/iesg/statement/discuss-criteria.html for more information about IESG DISCUSS and COMMENT positions. The document, along with other ballot positions, can be found here: https://datatracker.ietf.org/doc/draft-ietf-core-block/ ---------------------------------------------------------------------- COMMENT: ---------------------------------------------------------------------- Is there a specific reason that the 4.08 response code is overloaded for use for two different kinds of issues? a) Mismatching Content-Format options in different blocks b) not all previous blocks are available at the server at the time of processing the final block of an atomic operation Section 7.1: Have you thought about how this text can be made actionable, especially in the case of atomic PUT or POST requests without maintaining state? If so, it would be good to elaborate here. "Wherever possible, servers should therefore minimize the opportunities to create state for untrusted sources, e.g. by using stateless approaches."
- [core] Suresh Krishnan's No Objection on draft-ie… Suresh Krishnan
- Re: [core] Suresh Krishnan's No Objection on draf… Carsten Bormann