Re: [OPSAWG] I-D Action: draft-ietf-opsawg-mud-14.txt

2018-01-31 Thread Marco Davids (SIDN)
Op 26-01-18 om 20:17 schreef Saswat Praharaj (saspraha): Adding device information (manufacture/device-type etc.) in MUD file provides visibility in network, in addition to policy. Also, besides ACL's, I believe it would also make sense to convey bandwidth limitation information via MUD's (m

Re: [OPSAWG] I-D Action: draft-ietf-opsawg-mud-14.txt

2018-01-31 Thread Eliot Lear
Hi Marco, I think this is an example opportunity for an extension.  Let's put that together separately.  happy to work with you on it. Eliot On 31.01.18 10:07, Marco Davids (SIDN) wrote: > Op 26-01-18 om 20:17 schreef Saswat Praharaj (saspraha): > >> Adding device information (manufacture/devi

[OPSAWG] New Version Notification - draft-mm-wg-effect-encrypt-16.txt

2018-01-31 Thread internet-drafts
A new version (-16) has been submitted for draft-mm-wg-effect-encrypt: https://www.ietf.org/internet-drafts/draft-mm-wg-effect-encrypt-16.txt The IETF datatracker page for this Internet-Draft is: https://datatracker.ietf.org/doc/draft-mm-wg-effect-encrypt/ Diff from previous version: https://ww

[OPSAWG] draft-ietf-opsawg-mud-15 ACL operators

2018-01-31 Thread M. Ranganathan
The ACL draft has various operators for ports, including eq, lte, gte Does a compliant MUD implementation have to support all of these operators? If ONLY eq is required to be supported (I hope ) , can this be stated in the draft. Given that port ranges can be specified I wonder why the other comp

[OPSAWG] request slot for 10 minutes

2018-01-31 Thread Eliot Lear
Dear OPSAWG chairs, Can I please have 10 minutes to talk about- AfterMUD, or those next MUDdy steps, or the like? Abstract as follows: We anticipate the IETF LC to have completed on the base MUD draft.  We have other work that we may wish to look to, in terms of next steps.  As we have seen duri

Re: [OPSAWG] draft-ietf-opsawg-mud-15 ACL operators

2018-01-31 Thread Eliot Lear
On 31.01.18 21:35, M. Ranganathan wrote: > The ACL draft has various operators for ports, including eq, lte, gte > > Does a compliant MUD implementation have to support all of these > operators? If ONLY eq is required to be supported (I hope ) , can this > be stated in the draft. All.  The MUD f

[OPSAWG] New Version Notification - draft-mm-wg-effect-encrypt-17.txt

2018-01-31 Thread internet-drafts
A new version (-17) has been submitted for draft-mm-wg-effect-encrypt: https://www.ietf.org/internet-drafts/draft-mm-wg-effect-encrypt-17.txt The IETF datatracker page for this Internet-Draft is: https://datatracker.ietf.org/doc/draft-mm-wg-effect-encrypt/ Diff from previous version: https://ww

[OPSAWG] opsawg - New Meeting Session Request for IETF 101

2018-01-31 Thread IETF Meeting Session Request Tool
A new meeting session request has just been submitted by Tianran Zhou, a Chair of the opsawg working group. - Working Group Name: Operations and Management Area Working Group Area Name: Operations and Management Area Session Requester: Ti

Re: [OPSAWG] Christian's review of draft-mm-wg-effect-encrypt-13

2018-01-31 Thread Christian Huitema
I am using the side by side feature to review the differences between draft-13 and draft-15. I am commenting here on Kathleen's message, to check whether various points are addressed. On 1/5/2018 6:07 AM, Kathleen Moriarty wrote: > Christian, > > Thanks for your review. I'll respond inline to m