Re: [OPSAWG] Start of 2nd WGLC for draft-ietf-opsawg-capwap-alt-tunnel

2016-08-03 Thread Warren Kumari
Dear OpsAWG WG, We believe that there is sufficient support (taking into account comments reveived during both this, and the previous WGLC) for progressing this document, and so will be submitting it to the IESG for publication. Thank you for your review and feedback, W and T. On Wed, Jun 15,

Re: [OPSAWG] Adoption poll for draft-lear-ietf-netmod-mud-04

2016-08-03 Thread Paul Duffy
I support adoption of this work. On 8/3/2016 3:14 AM, Zhoutianran wrote: Dear OPSAWG, The chairs would like to know if the WG participants agree that the following document should be adopted as a WG document in OPSAWG. Manufacturer Usage Description Specification:

Re: [OPSAWG] Plans for advancing RFC7860 to full standard?

2016-08-03 Thread Johannes Merkle
Hi Matjaz, others on this list have more insight in the availability and interoperability of implementations, and Robert has already provided some information. If and when the WG decides that it is time to proceed the RFC to maturity level Internet Standard we would be happy to cooperate. Best

Re: [OPSAWG] Adoption poll for draft-lear-ietf-netmod-mud-04

2016-08-03 Thread Eliot Lear
Hi Bert, On 8/3/16 12:54 PM, Bert Wijnen (IETF) wrote: > M > > - first I wonder why this document has "netmod" in the draftname". > it is targeted at opsawg, and besides, it not only has a YANG > datamodel, but also talks bout DHCP, x509 and LLDP. > So people should be aware that this

Re: [OPSAWG] Adoption poll for draft-lear-ietf-netmod-mud-04

2016-08-03 Thread Bert Wijnen (IETF)
M - first I wonder why this document has "netmod" in the draftname". it is targeted at opsawg, and besides, it not only has a YANG datamodel, but also talks bout DHCP, x509 and LLDP. So people should be aware that this is more than just YANG data model. - the document also refers to