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

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

Re: [OPSAWG] Eric Rescorla's Discuss on draft-mm-wg-effect-encrypt-17: (with DISCUSS and COMMENT)

Hi Eric, Thanks for your feedback, responses are inline. FYI - I posted another version, but expect at least one more iteration after this version with additional comments and the ones we haven't gotten to yet. On Thu, Feb 8, 2018 at 12:04 AM, Eric Rescorla wrote: > Eric

Re: [OPSAWG] draft-ietf-opsawg-mud

Yes, but they're not quite ready for release (I know of at least two).  I think they're waiting for this doc to get finished. On 19.02.18 19:07, Marco Davids (SIDN) wrote: > Op 19-02-18 om 17:38 schreef Eliot Lear: > >>> I know of some >>> people working to implement this.  I don't think they

Re: [OPSAWG] draft-ietf-opsawg-mud

Op 19-02-18 om 17:38 schreef Eliot Lear: I know of some people working to implement this.  I don't think they are all on this list.  Have you run this by them to see if this limits any use cases out of the box? I have.  I think they're okay with it. Anyone knows if these

[OPSAWG] I-D Action: draft-ietf-opsawg-tacacs-08.txt

A New Internet-Draft is available from the on-line Internet-Drafts directories. This draft is a work item of the Operations and Management Area Working Group WG of the IETF. Title : The TACACS+ Protocol Authors : Thorsten Dahm Andrej

Re: [OPSAWG] draft-ietf-opsawg-mud

-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Speaking as a contributor... On 2/19/18 05:03, Eliot Lear wrote: > All, > > Mark Nottingham and I had some extensive conversations about how > to handle the MUD URL. The issue is was that Mark identified a > potential violation of a best practice

[OPSAWG] draft-ietf-opsawg-mud

All, Mark Nottingham and I had some extensive conversations about how to handle the MUD URL.  The issue is was that Mark identified a potential violation of a best practice in the way the URL was structured.  The principles I seek to maintain are these: * The base MUD URL is formed solely by