Re: [IPsec] [Editorial Errata Reported] RFC7296 (4930)

This is factually true, and it dates back to RFC 5996 (but not 4306). It obviously doesn’t confuse anyone, so I guess it should be either “held for document update” Yoav > On 8 Feb 2017, at 17:55, RFC Errata System wrote: > > The following errata report has been

Re: [IPsec] Working group last call for the draft-nir-ipsecme-eddsa-00

Tero, I've reviewed this draft. I support it and believe it is ready to move forward towards becoming a standards-track RFC. Also, would it make sense to ask IANA for early assignment of the code point? Using 0 sounds reasonable to me. Minor typo in the introduction: "we define a new value

[IPsec] [Editorial Errata Reported] RFC7296 (4930)

The following errata report has been submitted for RFC7296, "Internet Key Exchange Protocol Version 2 (IKEv2)". -- You may review the report below and at: http://www.rfc-editor.org/errata_search.php?rfc=7296=4930 -- Type:

[IPsec] Meeting in the Chicago IETF 98 and agenda items

I think we have still enough drafts going forward and work to do that is useful for us to meet in the Chicago. I am planning to put in a request for one 1.5 hour session, but if someone has some other agenda items which are not in our current items to be worked on (rfc4307bis, rfc7321bis, eddsa,

[IPsec] Working group last call for the draft-nir-ipsecme-eddsa-00

This message will start two week working group last call for the draft-nir-ipsecme-eddsa-00 [1] draft. Please send your comments, questions etc to WG mailing list before 2017-02-24. If you belive that the document is ready to be submitted to the IESG for consideration as a standard track RFC