Re: [core] Last Call: <draft-ietf-core-block-18.txt> (Block-wise transfers in CoAP) to Proposed Standard

Göran Selander <goran.selander@ericsson.com> Thu, 26 November 2015 08:43 UTC

From: Göran Selander <goran.selander@ericsson.com>
To: Carsten Bormann <cabo@tzi.org>
Thread-Topic: Last Call: <draft-ietf-core-block-18.txt> (Block-wise transfers in CoAP) to Proposed Standard
Thread-Index: AQHRI9sb/ga71FS+3UKAe+rFI8Rp+56t6kEAgAAAkICAABp4gA==
Date: Thu, 26 Nov 2015 08:43:20 +0000
Message-ID: <D27C7DBC.3F244%goran.selander@ericsson.com>
References: <20151120213250.32473.53283.idtracker@ietfa.amsl.com> <D27C68A8.3F21C%goran.selander@ericsson.com> <5656BE03.3090604@tzi.org>
In-Reply-To: <5656BE03.3090604@tzi.org>
Accept-Language: en-US
Content-Language: en-US
user-agent: Microsoft-MacOutlook/14.4.7.141117
Content-Type: text/plain; charset="utf-8"
Content-ID: <1530EF0D3BF7EC45A56C1628088A91F4@ericsson.com>
Content-Transfer-Encoding: base64
MIME-Version: 1.0
Archived-At: <http://mailarchive.ietf.org/arch/msg/core/L1C4oeT9HG0CpQEzwbGnTJnM7s8>
Cc: "core-chairs@ietf.org" <core-chairs@ietf.org>, "ietf@ietf.org" <ietf@ietf.org>, "core@ietf.org" <core@ietf.org>, "barryleiba@gmail.com" <barryleiba@gmail.com>, "draft-ietf-core-block@ietf.org" <draft-ietf-core-block@ietf.org>
Subject: Re: [core] Last Call: <draft-ietf-core-block-18.txt> (Block-wise transfers in CoAP) to Proposed Standard
Precedence: list

On 2015-11-26 09:08, "Carsten Bormann" <cabo@tzi.org> wrote:

>Göran Selander wrote:
>> we should
>> not ignore these security issues in new standards.
>
>Definitely, we shouldn't ignore these security issues when defining new
>standards.
>
>Now why is this a comment on the IETF last-call for an existing
>specification? 

I’m sorry if you find this comment coming a bit late. Let me expand on the
history. 

As mentioned the object security work has been going on since a year
starting with CoAP. When turning to the other drafts in the CoAP suite, we
couldn't understand how blockwise works with proxies from the draft and
asked the question to the CORE list (June). The only answer we got was
actually wrong, in the sense that it gave the impression that this is not
a proxy operation that would be of any use - an indication that  blockwise
proxy operations, although not invented yesterday, has not been well
understood.

It was not until the social event in Prague (July) where we learnt (in
private conversation) that this is not a corner case. In the mail
discussion that follow on the CoRE list I formulate this problem as a
question to you but I don’t get any answer (Sept. 2). In the CORE WG f2f
meeting in Yokohama I raised the issue with blockwise and proposed
solution in my presentation (Nov. 5), but there is no comment.

That is why this is a comment on the IETF last-call.

Göran

[core] Last Call: <draft-ietf-core-block-18.txt> … The IESG
Re: [core] Last Call: <draft-ietf-core-block-18.t… Göran Selander
Re: [core] Last Call: <draft-ietf-core-block-18.t… Carsten Bormann
Re: [core] Last Call: <draft-ietf-core-block-18.t… Göran Selander
Re: [core] Last Call: <draft-ietf-core-block-18.t… Jim Schaad
Re: [core] Last Call: <draft-ietf-core-block-18.t… Carsten Bormann
Re: [core] Last Call: <draft-ietf-core-block-18.t… Jim Schaad
Re: [core] Last Call: <draft-ietf-core-block-18.t… Göran Selander
Re: [core] Last Call: <draft-ietf-core-block-18.t… Jim Schaad
Re: [core] Last Call: <draft-ietf-core-block-18.t… Göran Selander
Re: [core] Last Call: <draft-ietf-core-block-18.t… Jim Schaad
Re: [core] Last Call: <draft-ietf-core-block-18.t… Carsten Bormann
Re: [core] Last Call: <draft-ietf-core-block-18.t… Ludwig Seitz
Re: [core] Last Call: <draft-ietf-core-block-18.t… Göran Selander