[OPSAWG] MUD: Why reserve names for "well-known" controllers

2017-10-18 Thread M. Ranganathan
Hello MUD authors, DNS and NTP have reserved URI names. However, it appears you need to specify a full ACL for both of these. In that case, why reserve the name? Is it just for clarity? Thanks -- M. Ranganathan ___ OPSAWG mailing list OPSAWG@ietf.org

Re: [OPSAWG] MUD: Why reserve names for "well-known" controllers

2017-10-19 Thread M. Ranganathan
Hello, On Wed, Oct 18, 2017 at 6:19 PM, M. Ranganathan wrote: > Hello MUD authors, > > DNS and NTP have reserved URI names. However, it appears you need to > specify a full ACL for both of these. In that case, why reserve the name? > Is it just for clarity? > > Thanks > > -- > M. Ranganathan >

Re: [OPSAWG] MUD: Why reserve names for "well-known" controllers

2017-10-19 Thread Eliot Lear
Hi Ranga, Sorry I've been quiet for a few days.  I'll have more to say later.  Please see below. On 10/19/17 4:28 PM, M. Ranganathan wrote: > > I am not clear in my mind about why this should be the case for NTP server > i.e. why do we reserve a special URN for NTP server? Why is it not just a >

Re: [OPSAWG] MUD: Why reserve names for "well-known" controllers

2017-10-19 Thread M. Ranganathan
Hi Eliot, On Thu, Oct 19, 2017 at 4:44 PM, Eliot Lear wrote: > Hi Ranga, > > Sorry I've been quiet for a few days. I'll have more to say later. > Please see below. > > > On 10/19/17 4:28 PM, M. Ranganathan wrote: > > > > I am not clear in my mind about why this should be the case for NTP > serv

Re: [OPSAWG] MUD: Why reserve names for "well-known" controllers

2017-10-19 Thread Eliot Lear
On 10/20/17 2:47 AM, M. Ranganathan wrote: > > Scenario: Perhaps the manufacturer would like the IOT devices to use HIS > name server - not necessarily what is returned by dhcp when the IOT device > goes to get it's IP address assigned. That is the device gets a server > address of the desired n