Re: [IPsec] Possible new charter text to cover iptfs.

I think we've got a couple potential recharter topics in flight, so I'd
like to have the chairs assemble a consolidated version with all the
updates in it, so that I can start the formal rechartering process.

-Ben

On Sun, Oct 13, 2019 at 03:10:36AM -0400, Christian Hopps wrote:
> Hi ipsecme and charis,
> 
> It seems like we've had a good amount of soak time on this. :)
> 
> What are the next steps?
> 
> Thanks,
> Chris.
> 
> > On Aug 7, 2019, at 7:04 PM, Paul Wouters <paul@nohats.ca> wrote:
> > 
> > Seems broad enough - works for me
> > 
> > Sent from mobile device
> > 
> >> On Aug 7, 2019, at 06:38, Christian Hopps <chopps@chopps.org> wrote:
> >> 
> >> Hi ipsecme and chairs,
> >> 
> >> As discussed @IETF105 we need to update the charter in order to adopt the IPTFS draft, how does this look for addition to the charter?
> >> 
> >> "
> >> 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.
> >> "
> >> 
> >> Thanks,
> >> Chris.
> >> _______________________________________________
> >> 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