Re: [apps-discuss] Scope of RFC3986 and successor - what is a URI?

[Larry Masinter <[e-mail]>]

+1 BOF at next IETF, whether or not it leads to a working group.  

Proposed Agenda: walk through draft-ruby-url-problem (I volunteer)
                                    based on that, discuss next steps.

If a working group is wanted, proposed charter milestone:
 
* finish draft-ruby-url-problem (problem statement agreed or controversies identified, proposed plans concrete or have concrete options), publish as RFC.
* Then recharter or close (within 4 months)

If you agree, it would help focus the discussion if comments were couched in terms of changes to draft-ruby-url-problem.
For example, https://tools.ietf.org/html/draft-ruby-url-problem-01#section-5.2  does note some kinds of things an update to 3986 might accomplish, but doesn't suggest changing fragment identifier repertoire, as Sam suggested in email.

If you want a mailing list other than appswg, either a new one or an old one; of the existing mailing lists, I suggest [e-mail] is the closest in scope.

I'm in favor of chartering and managing the work in IETF and not in W3C based on where the specs would get adequate review.
* URIs/URLs, although invented for the web, are now woven into many other IETF protocols and data structures than the web, and those are mainly out of scope for W3C/WHATWG priorities.
* it seems easier to get broader review in IETF.  I say this despite the past failure to get W3C/WHATWG participation in the IRI working group, because we now have real data about browser behavior  and the new possibility of getting browser participation in the discussion. 

Commitments of participation (from W3C management, URL implementors) would help.