> In such a case, resolvers following
> this protocol will look for authoritative answers to ports 53 and
> 853 on that system, and the system would need to be able to
> differentiate queries for recursive answers from queries for
> authoritative answers.
For lack of a better term, I use the word
In your letter dated Wed, 7 Jun 2023 23:12:21 + you wrote:
>> The experiment could just be to gain operational experience. We can be up=
>front
>> that we don't know what will happen, and encourage people to be careful.
>
>That's true with every new protocol from the IETF. It would be good to
> We still have time to add those known operational considerations.
> In fact, we should be listing those even if this is an experimental
> RFC.
The experiment could just be to gain operational experience. We can be upfront
that we don't know what will happen, and encourage people to be careful.
> 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