[email protected] writes: > Could you respond on the timeline and if you think it's reasonable > and why or if it should be changed.
Sure. Out of the nine documents to be published, there is two which are already going out from the WG, i.e., which are already submitted for publication (DDoS and curve25519). Two more are almost ready (4307bis and 7321bis), and those are updating the MTI requirements, thus there is not that much of protocol work, we just need to agree what is suitable level for each algorithm. This means that four of the documents should be out from the WG hands before the next IETF, and hopefully published as RFC on first half of 2017... Then there is EdDSA which is mostly waiting for the curdle-pkix to agree on the OIDS to be used for the EdDSA, and then it should be ready soon after that is done (it is 2 page document just saying we do what draft-irtf-cfrg-eddsa and draft-ietf-curdle-pkix do). For the rest of the items, we have quite stable drafts for three of them (tcp-encp, split-dns, and implicit IV), so after we get those first drafts out, we should get them done during the winter. Only thing that still requires more work is the quantum resistant version of the IKEv2, and even for that, I think we already have the idea how it will be done, and it should not take too long. Also I would assume that during 2017 we most likely will get some new work items that will start working on, thus we will most likely want to do recharter by the end of 2017 anyways. And if there is nothing new to be done, and we have only 1-2 items left, we can continue working them without WG if needed. Year ago (IETF 93, July 2015) we had started charter dicussion last time, i.e., during the meeting we discussed whether we should close down the WG, or recharter and continue. Then we decided to keep the WG, and recharter, but the recharter discussion took some time, and as we did not meet in Yokohama IETF 94, the discussion on charter started on the IETF 95 in Buenos Aires, and finalized during the IETF 96 in Berlin. -- [email protected] _______________________________________________ IPsec mailing list [email protected] https://www.ietf.org/mailman/listinfo/ipsec
