Re: [dd] [Ext] starting charter text for the DELEG BOF discussion

[Paul Hoffman <[e-mail]>]

On Mar 5, 2024, at 11:52, Ben Schwartz <bemasc=[e-mail]> wrote:
> 
> This charter text doesn't mention encryption, TLS, or QUIC.

Correct. It doesn't mention anything from <https://mailarchive.ietf.org/arch/msg/dd/H2p3Mzgc02ineG9-ccIHuNKbS3w> other than aliaasing.

> It seems to me that enabling encrypted transport upgrade is a key motivating factor that drives many aspects of the DELEG design.

It was a key motivating factor, but then was not developed to the extent that aliasing was.

>   Encryption should at least be mentioned in the charter, and the group's intention should be spelled out here to avoid confusion about the division of responsibility between DELEG and DPRIVE.

If there's a lot of interest on this list for that use case, it could certainly be added to this proposed charter. Please propose text.

According to the DPRIVE chairs, DPRIVE is going dormant, so it seems unlikely to recharter to take on a new work item that could be covered in a different working group. Having said that, if the working group that comes out of this BoF does cover identifying encrypted transports during delegation, the chairs of that WG should certainly reach out to the DPRIVE mailing list even if the WG has shut down.

--Paul Hoffman