[apps-discuss] RFC6454 "the web origin concept" obsoleted?

[[e-mail]]

[This is more-or-less a heads-up public service announcement/query wrt  
process...]

In the below relatively recent exchange on the HTTP WG's list ietf-http-wg@..

https://lists.w3.org/Archives/Public/ietf-http-wg/2016JanMar/0323.html
> On 3/3/16, 3:10 AM, "Anne van Kesteren" <[e-mail]> wrote:
>> On Mon, Feb 22, 2016 at 1:45 PM, Mike West <[e-mail]> wrote:
>> > I think we need precision somewhere. I'm fairly agnostic about where that
>> > somewhere might be. Adding Anne, who might be interested in defining terms
>> > like these in Fetch?
>
> Seems fine. (Though note that the Origin RFC comparison does not quite
> fly, it's made obsolete by the combination of HTML, Fetch, and URL
> Standards.)

..Anne notes that (in the WhatWG's (and others?) view), RFC6454 "The  
Web Origin Concept" is obsoleted by the combination of (the present,  
and intended on-going state of) [HTML], [FETCH], and [URL].

This seems to beg some questions for the HTTP WG and the IETF at large  
(and perhaps the WhatWG, as well as the W3C), since [HTML] and [FETCH]  
are implemented by browsers and browser-like HTTP clients (e.g.,  
crawlers/spiders), but not necessarily other types of HTTP clients,  
[URL] is intended (by its author(s)) to obsolete RFC3986 & RFC3987  
[URLgoals], and RFC6454 is referenced by nine RFCs [0] and several  
I-Ds [1]:

* Should some I-D appear that is intended to obsolete RFC6454 and  
points to [HTML], [FETCH], and [URL] as the present specs addressing  
the Web Origin Concept?

* Or should some I-D appear stating that for browsers and browser-like  
HTTP clients, see [HTML][FETCH][URL] for the Web Origin Concept, and  
for other HTTP clients, see RFC6454?

* Plus, should the change(s) to the functionality & definitions in  
RFC6454 be back-ported to a rfc6454bis ?

* Are the changes to RFC3986 & RFC3987 evidenced in [URL] widely  
applicable to all URL-utilizing specs and if so, do we obsolete them  
and point to [URL], or backport the changes to RFC3986bis &  
RFC3987bis? Or do something else, or do nothing?

The above questions and the issues they beg are just off the top of my  
head, need refinement, etc.

Perhaps the duplication between "orgs" doesn't matter and everyone can  
figure out what specs to pay attention to given their context? I don't  
know the answers but thought I'd toss out the questions...

HTH,

=JeffH

ps: note also that [HTML] and [FETCH] are referenced by  
draft-ietf-httpbis-cookie-same-site:
https://lists.w3.org/Archives/Public/ietf-http-wg/2016AprJun/0432.html


[FETCH] https://fetch.spec.whatwg.org/

[HTML] https://html.spec.whatwg.org/

[URL] https://url.spec.whatwg.org/

[URLgoals] https://url.spec.whatwg.org/#goals

[0] RFC6454 is ref'd By 6555, 6690, 6787, 6797, 6920, 7030, 7034, 7395, 7486

[1]  (some of the below may be expired, I didn't check)
> grep -li rfc6454 *txt
draft-dejong-remotestorage-07.txt
draft-ietf-appsawg-file-scheme-11.txt
draft-ietf-core-coap-tcp-tls-03.txt
draft-ietf-httpauth-mutual-08.txt
draft-ietf-httpbis-alt-svc-14.txt
draft-ietf-httpbis-cache-digest-00.txt
draft-ietf-httpbis-cookie-same-site-00.txt
draft-ietf-httpbis-http2-encryption-06.txt
draft-ietf-httpbis-origin-frame-00.txt
draft-ietf-rtcweb-security-08.txt
draft-ietf-rtcweb-security-arch-12.txt
draft-ietf-tram-stun-origin-06.txt
draft-ietf-webpush-protocol-07.txt
draft-ietf-webpush-vapid-01.txt
draft-kazuho-h2-cache-digest-01.txt
draft-nottingham-httpbis-origin-frame-01.txt
draft-pd-dispatch-msrp-websocket-12.txt
draft-reschke-http-oob-encoding-07.txt
draft-savolainen-core-coap-websockets-07.txt
draft-sheffer-tls-pinning-ticket-02.txt
draft-thomson-http-scd-01.txt
draft-thomson-webpush-vapid-02.txt