RE: IETF tree URL registration procedure incomplete

In particular, it has been argued that the IETF process
for publication of Informational RFCs does not require
technical review. In 

http://www.ietf.org/mail-archive/ietf/Current/msg05318.html

Michael Dolan argued, in regard to draft-zigmond-tv-url-02.txt:

"The continued insistence that this draft obtain technical review 
and approval either in or out of IETF is not required under the 
Informational process.  So, there simply is no requirement to change 
the draft technically based on comments here or in W3C or anywhere 
else.  Continued references to current and past mail threads on the 
(lack of) technical merits are just not relevant unless someone can 
explain why this draft requires a special review process."

I think we might want to make sure that 
draft-ietf-urlreg-procedure-07.txt says that the URL review process
is an ongoing activity of the IETF, and any Informational
RFC which purports to register an IETF tree URL is subject
to technical review. It would be useful if the resulting BCP
were listed as "Updates RFC 2026", so that there's no question
about the applicable process.