Hi, I've read the draft and I think it addresses an important problem. So, I support adoption of the draft as a starting point ( I think the draft has some issues that can be addressed in WG).
Regards, Valery. > -----Original Message----- > From: IPsec <[email protected]> On Behalf Of Tero Kivinen > Sent: Saturday, October 26, 2019 6:17 PM > To: [email protected] > Subject: [IPsec] Adoption call for draft-hopps-ipsecme-iptfs > > So this is fast (one week) adoption call for the draft-hopps-ipsecme-iptfs draft > to be accepted to the WG document. We did have quite positive feedback in > last IETF meeting and the charter item is being worked on in parallel to this call. > > If you support adopting this document as WG document and as a starting place > for the charter item proposed for the WG, then send email indicating your > support to the [email protected] mailing-list. If you have any comments or > reservations send them to list too. > > This adoption call finishes at 2019-11-04. > > ---------------------------------------------------------------------- > The demand for Traffic Flow Confidentiality has been increasing in the user > community; however, the current method defined in RFC4303 (i.e., add null > padding to each ESP payload) is very inefficient in it's use of network > resources. The working group will develop an alternative TFC solution that > provides for efficient use of network resources. > -- > [email protected] > > _______________________________________________ > IPsec mailing list > [email protected] > https://www.ietf.org/mailman/listinfo/ipsec _______________________________________________ IPsec mailing list [email protected] https://www.ietf.org/mailman/listinfo/ipsec
