Hi Henk and thanks very much for your review.
Please see below.
On 8/29/17 11:40 PM, Henk Birkholz wrote:
>
>
> # IoT-DIR Early Review of I-D.ietf-opsawg-mud-08
>
> ## Draft Summary
>
> This draft defines a canonical way to compose an URI that points to a
> specific resource called a MUD file. A
Hello Eliot,
thank you for your fast feedback! I still have some comments and
questions for another round, though. I hope that is okay - please see
comments in-line.
Viele Grüße,
Henk
On 08/30/2017 09:56 AM, Eliot Lear wrote:
Hi Henk and thanks very much for your review.
Please see below
Reviewer: Robert Sparks
Review result: Almost Ready
This is an exciting concept, and the draft overall is approachable. I
have identified a few areas I think need more detail, and have a
longish list of nits (please don't take that to be negative).
==Issues==
I find the structure of the introdu
On Wed, Aug 30, 2017 at 1:21 PM, Robert Sparks wrote:
>
>
> Right now, you leave the DHCP server (when it's used) responsible for
> clearing state in the MUD controller. Please discuss what happens when
> those are distinct elements (as you have in the end of section 9.2) and
> the DHCP server re
On Wed, Aug 30, 2017 at 6:00 PM, M. Ranganathan wrote:
>
>
> On Wed, Aug 30, 2017 at 1:21 PM, Robert Sparks
> wrote:
>
>>
>>
>> Right now, you leave the DHCP server (when it's used) responsible for
>> clearing state in the MUD controller. Please discuss what happens when
>> those are distinct el
This draft raises some fascinating questions. One is "How do we ensure
that the manufacturer cannot proscribe the uses of a device that it is
capable of and that its purchaser desires?" Another is "How do we
ensure that the manufacturer cannot reduce the permitted uses of the
device after its pur
