Re: [dns-privacy] [Ext] WGLC : draft-ietf-dprive-unilateral-probing

["Hollenbeck, Scott" <[e-mail]>]

> -----Original Message-----
> From: dns-privacy <[e-mail]> On Behalf Of Paul Hoffman
> Sent: Tuesday, June 6, 2023 9:44 AM
> To: [e-mail]
> Subject: [EXTERNAL] Re: [dns-privacy] [Ext] WGLC : 
> draft-ietf-dprive-unilateral-
> probing
>
> Caution: This email originated from outside the organization. Do not click 
> links
> or open attachments unless you recognize the sender and know the content is
> safe.
>
> On Jun 5, 2023, at 8:12 PM, Brian Haberman <[e-mail]>
> wrote:
> >
> > Tim & I checked in with our AD on this. Given that the charter text calls 
> > out
> Experimental, that is a binding agreement with the IESG.
> >
> > Our choices are simple:
> >
> > 1) publish as Experimental
> > 2) re-charter
> >
> > If the intended status had just been in the milestones, we would have more
> flexibility.
> >
> > Let’s constructively discuss the above options.
>
> One large problem with publishing a protocol as "experimental" is there is 
> not
> objective way to exit that status. There are no criteria that say "this 
> experiment
> succeeded" or "this experiment failed".
>
> It will take much less IETF effort to fix the charter now than it will to 
> move the
> already-deployed protocol to standards track. We might as well bit the
> bureaucratic bullet now and just fix the charter. If most folks agree, I can 
> do
> that work.

[SAH] The criteria to conduct the experiment and measure the outcome could be 
documented in the current draft. From there:

Publish experimental RFC.
Conduct experiment.
Publish RFCbis I-D to document the results of the experiment with 
informational status for failure or standards track for success.
Assuming success, recharter to publish RFCbis I-D on the standards track.
Adopt RFCbis I-D as a working group document.
Working group works to publish RFCbis on the standards track.

Paul is correct in noting that there's more IETF effort associated with the 
above. It's worth making that effort to ensure that the risks to critical 
internet infrastructure are minimized.

Scott