Re: [OPSAWG] WG LC for draft-ietf-opsawg-mud-05

2017-04-17 Thread Eliot Lear
Hi Brian, Apologies for the late response. On 3/31/17 6:40 AM, Brian Weis (bew) wrote: > I support advancing this document, and have the following minor comments. > > (1) Section 1.3. LLDP should be referenced at first use. The wording > at the beginning of Section 11 is nice: "IEEE802.1AB Link L

Re: [OPSAWG] WG LC for draft-ietf-opsawg-mud-05

2017-04-07 Thread Eliot Lear
Hi Kent, Thanks very much for taking the time to review the draft. Based on your review, unless the WG objects, I'll include some changes as discussed below. On 4/7/17 3:37 AM, Kent Watsen wrote: > > Hi, > > > > First off, I think that this is an interesting and useful idea. > However, I hav

Re: [OPSAWG] WG LC for draft-ietf-opsawg-mud-05

2017-04-06 Thread Kent Watsen
Hi, First off, I think that this is an interesting and useful idea. However, I have found some issues that I'd like to discuss. First, I think that this draft unnecessarily conflates the MUD file itself with mechanisms for how a device might identify its model type and/or where its MUD file can

Re: [OPSAWG] WG LC for draft-ietf-opsawg-mud-05

2017-03-30 Thread Brian Weis (bew)
I support advancing this document, and have the following minor comments. (1) Section 1.3. LLDP should be referenced at first use. The wording at the beginning of Section 11 is nice: "IEEE802.1AB Link Layer Discovery Protocol (LLDP) [IEEE8021AB]”. (2) Section 1.4. An interesting policy example

Re: [OPSAWG] WG LC for draft-ietf-opsawg-mud-05

2017-03-28 Thread Thorsten Dahm
I support the document. Regards, Thorsten On 17 March 2017 at 03:17, Tianran Zhou wrote: > Dear OPSAWG, > > This is a notice to start a two-week OPSAWG WG last call for the document: > > Manufacturer Usage Description Specification > https://datatracker.ietf.org/doc/draft-ietf-opsawg-mud/ > > P

Re: [OPSAWG] WG LC for draft-ietf-opsawg-mud-05

2017-03-23 Thread Max Pritikin (pritikin)
Folks, I support this document. I have the following concerns, 1) A MUD file attribute indicating the expected MUD URL emission method is of security value. Discussion: Section 1.3 indicates "three means are defined to emit the MUD URL” which including unsecured modes. This introduces the po

[OPSAWG] WG LC for draft-ietf-opsawg-mud-05

2017-03-17 Thread Tianran Zhou
Dear OPSAWG, This is a notice to start a two-week OPSAWG WG last call for the document: Manufacturer Usage Description Specification https://datatracker.ietf.org/doc/draft-ietf-opsawg-mud/ Please read the above draft and send any issues, comments, or corrections to this mailing list. Please ind