Re: [dispatch] Tiny update to RFC 3405

I read Robert’s email to be an objection to the fact that our existing charter allows us to adopt certain documents at all, not an objection that this draft does not fit under the charter. If that’s not the case, please correct me.

Ben.

> On Jun 23, 2020, at 11:29 AM, Mary Barnes <mary.ietf.barnes@gmail.com> wrote:
> 
> I totally agree with Robert. 
> 
> 
> 
> On Tue, Jun 23, 2020 at 9:12 AM Robert Sparks <rjsparks@nostrum.com <mailto:rjsparks@nostrum.com>> wrote:
> I can live with either path, but I still think allowing Dispatch to adopt work was a step onto the slippery slope mistake.
> 
> On 6/22/20 5:51 PM, Ben Campbell wrote:
>> Hi Everyone,
>> 
>> The ART ADs have reminded the chairs that our charter allows us to adopt “simple administrative” work such as IANA registration documents. This draft seems to fit squarely in that category. Does anyone see a reason we shouldn’t just adopt it, with the expectation of going immediately to WGLC? (The last-call timeline is the same either way, either 2 weeks WGLC and 2 weeks IETF LC for a working group draft, or 4 weeks IETF LC for an AD sponsored draft.)
>> 
>> Thanks!
>> 
>> Ben (as co-chair)
>> 
>>> On Jun 3, 2020, at 6:13 PM, Ted Hardie <ted.ietf@gmail.com <mailto:ted.ietf@gmail.com>> wrote:
>>> 
>>> Howdy,
>>> 
>>> This is one the shortest drafts I've ever written:  https://datatracker.ietf.org/doc/draft-hardie-dispatch-rfc3405-update/ <https://datatracker.ietf..org/doc/draft-hardie-dispatch-rfc3405-update/> .   Basically, RFC 3405 used to require that registrations in URI.ARPA be from the "IETF Tree".  That tree was deprecated after the document was published.  As it happens, there are very few registrations in URI.ARPA, so we did not catch it and fix it before now.  
>>> 
>>> This draft updates RFC 3405 to require "permanent" scheme registrations.  The salient bit is this:
>>> 
>>> All registrations in URI.ARPA MUST be for schemes which are permanent
>>>    registrations, as they are described in BCP 35.
>>> 
>>> I'm hoping for a quick dispatch of this, but happy to discuss.
>>> 
>>> regards,
>>> 
>>> Ted Hardie
>>> _______________________________________________
>>> dispatch mailing list
>>> dispatch@ietf.org <mailto:dispatch@ietf.org>
>>> https://www.ietf.org/mailman/listinfo/dispatch <https://www.ietf.org/mailman/listinfo/dispatch>
>> 
>> 
>> 
>> _______________________________________________
>> dispatch mailing list
>> dispatch@ietf.org <mailto:dispatch@ietf.org>
>> https://www.ietf.org/mailman/listinfo/dispatch <https://www.ietf.org/mailman/listinfo/dispatch>
> _______________________________________________
> dispatch mailing list
> dispatch@ietf.org <mailto:dispatch@ietf.org>
> https://www.ietf.org/mailman/listinfo/dispatch <https://www.ietf.org/mailman/listinfo/dispatch>
> _______________________________________________
> dispatch mailing list
> dispatch@ietf.org
> https://www.ietf.org/mailman/listinfo/dispatch