[core] #367 (block): Reaction for Content-Format mismatch
"core issue tracker" <trac+core@trac.tools.ietf.org> Sat, 08 March 2014 18:52 UTC
Return-Path: <trac+core@trac.tools.ietf.org>
X-Original-To: core@ietfa.amsl.com
Delivered-To: core@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 2A76D1A022C for <core@ietfa.amsl.com>; Sat, 8 Mar 2014 10:52:44 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.447
X-Spam-Level:
X-Spam-Status: No, score=-2.447 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RP_MATCHES_RCVD=-0.547] autolearn=ham
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 JWaeGvmf_gQ0 for <core@ietfa.amsl.com>; Sat, 8 Mar 2014 10:52:42 -0800 (PST)
Received: from grenache.tools.ietf.org (grenache.tools.ietf.org [IPv6:2a01:3f0:1:2::30]) by ietfa.amsl.com (Postfix) with ESMTP id 6FD661A0142 for <core@ietf.org>; Sat, 8 Mar 2014 10:52:42 -0800 (PST)
Received: from localhost ([127.0.0.1]:33952 helo=grenache.tools.ietf.org ident=www-data) by grenache.tools.ietf.org with esmtp (Exim 4.80) (envelope-from <trac+core@trac.tools.ietf.org>) id 1WMMMG-0006Ci-PM; Sat, 08 Mar 2014 19:52:28 +0100
MIME-Version: 1.0
Content-Type: text/plain; charset="utf-8"
Content-Transfer-Encoding: 7bit
From: core issue tracker <trac+core@trac.tools.ietf.org>
X-Trac-Version: 0.12.3
Precedence: bulk
Auto-Submitted: auto-generated
X-Mailer: Trac 0.12.3, by Edgewall Software
To: draft-ietf-core-block@tools.ietf.org, kovatsch@inf.ethz.ch
X-Trac-Project: core
Date: Sat, 08 Mar 2014 18:52:28 -0000
X-URL: http://tools.ietf.org/core/
X-Trac-Ticket-URL: http://tools.ietf.org/wg/core/trac/ticket/367
Message-ID: <059.c382556ea7a7abaeb2001d71014e58e2@trac.tools.ietf.org>
X-Trac-Ticket-ID: 367
X-SA-Exim-Connect-IP: 127.0.0.1
X-SA-Exim-Rcpt-To: draft-ietf-core-block@tools.ietf.org, kovatsch@inf.ethz.ch, core@ietf.org
X-SA-Exim-Mail-From: trac+core@trac.tools.ietf.org
X-SA-Exim-Scanned: No (on grenache.tools.ietf.org); SAEximRunCond expanded to false
Resent-To: cabo@tzi.org, zach@sensinode.com
Archived-At: http://mailarchive.ietf.org/arch/msg/core/46w8Mb-Z7yELT0K479H2yOBFh3g
Cc: core@ietf.org
Subject: [core] #367 (block): Reaction for Content-Format mismatch
X-BeenThere: core@ietf.org
X-Mailman-Version: 2.1.15
Reply-To: trac+core@trac.tools.ietf.org
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: <http://www.ietf.org/mail-archive/web/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: Sat, 08 Mar 2014 18:52:44 -0000
#367: Reaction for Content-Format mismatch The Content-Format option applies to the body, not to the payload. What if the Content-Format of a block is different from the rest? Even if non-atomic transfers are allowed, a different Content-Format cannot be patched into a representation body. A server should (aiming for a MUST) not process such Block1 requests and return an error, e.g., 4.08 Request Entity Incomplete. For Block2, it should be up to the client to interpret non-atomic blocks correctly. Atomic transfers should (aiming for a MUST) be aborted when the Content- Format changes during the transfer. This might apply to more options. Servers probably should return the same error as for the non-atomic case. -- -------------------------+------------------------------------------------- Reporter: | Owner: draft-ietf-core- kovatsch@inf.ethz.ch | block@tools.ietf.org Type: protocol | Status: new defect | Milestone: Priority: minor | Version: block-14 Component: block | Keywords: Severity: Active WG | Document | -------------------------+------------------------------------------------- Ticket URL: <http://tools.ietf.org/wg/core/trac/ticket/367> core <http://tools.ietf.org/core/>
- [core] #367 (block): Reaction for Content-Format … core issue tracker
- Re: [core] #367 (block): Reaction for Content-For… core issue tracker