As author, I know of no IPR that applies to this draft, and support its adoption by the WG.
Thanks, Chris. > On Oct 26, 2019, at 11:17 AM, Tero Kivinen <kivi...@iki.fi> wrote: > > 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 ipsec@ietf.org 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. > -- > kivi...@iki.fi > > _______________________________________________ > IPsec mailing list > IPsec@ietf.org > https://www.ietf.org/mailman/listinfo/ipsec > _______________________________________________ IPsec mailing list IPsec@ietf.org https://www.ietf.org/mailman/listinfo/ipsec