With huge apologies to everyone involved, I'm going to extend this call for adoption for 2 days (till the 27th).
After Tom found https://datatracker.ietf.org/doc/draft-hartman-snmp-sha2/ and made us aware, Scott and I chatted. We decided that we should make the authors of draft-hartman-snmp-sha2 aware of this CfA so that they could chime in, and I took it on as an action item to inform them -- and then I went off to USENIX Security / WOOT and completely forgot (it was a good conference!). So, in order to give draft-hartman-snmp-sha2 time to respond, I'm extending htis. Apologies to everyone involved. W On Mon, Aug 11, 2014 at 2:28 PM, Warren Kumari <[email protected]> wrote: > Dear OpsAWG WG, > > This starts a Call for Adoption for draft-hmac-sha-2-usm-snmp. > > The draft is available here: > https://datatracker.ietf.org/doc/draft-hmac-sha-2-usm-snmp/ > > Please review this draft to see if you think it is suitable for > adoption by OpsAWG, > and comments to the list, clearly stating your view. > > Please also indicate if you are willing to contribute text, review, etc. > > This call for adoption ends Mon 25-Aug-2014. > > In addition, to satisfy RFC 6702 ("Promoting Compliance with > Intellectual Property Rights (IPR)"): > If you are personally aware of any IPR that applies to > draft-hmac-sha-2-usm-snmp, has this IPR been disclosed in compliance > with IETF IPR rules? (See RFCs 3979, 4879, 3669, and 5378 for more > details.) > > > > Thanks, > Warren Kumari > (as OpsAWG WG co-chair) -- I don't think the execution is relevant when it was obviously a bad idea in the first place. This is like putting rabid weasels in your pants, and later expressing regret at having chosen those particular rabid weasels and that pair of pants. ---maf _______________________________________________ OPSAWG mailing list [email protected] https://www.ietf.org/mailman/listinfo/opsawg
