Ole, On May 29, 2013, at 3:40 PM, Ole Troan <[email protected]> wrote: > ... > now the question becomes, what do you do with the embedded URIs containing > link-local addresses?
For a web page, the user would click on links/buttons that open other pages on the printer. For an IPP response, the client would fetch localization data, ICC profiles, etc. or open web pages in a browser (printer administration and supply pages). > the referral clearly has no value outside of the given link-local zone. Agreed. > could you not infer the link-local zone of the referral from the transport > session? > given a link-local transport connection using a link-local zone, would it > ever make > sense that the referrals using link-locals would belong to a different zone? No. The issue is one of preserving that context, in every application or in every data store. If the context (zoneid) is part of the URIs, then the URIs will continue to work as long as the two devices remain in the same link-local zone, without changes to the software. If the context is not included in the URIs, then *every* client application has to be updated to add that context back to the URIs for every kind of content that might be returned. *Or* every operating system needs to be updated to support handling link-local addresses without a zoneid so that applications do not require changes. > if not, then the client can just ensure to use the same zone for referrals > that it does the transport it received the HTML over. That implies adding extra code to every network application that wants to support link-local addressing, which is what I want to avoid (makes for a bad user experience when some things work and others do not because software hasn't been updated...) _________________________________________________________ Michael Sweet, Senior Printing System Engineer, PWG Chair -------------------------------------------------------------------- IETF IPv6 working group mailing list [email protected] Administrative Requests: https://www.ietf.org/mailman/listinfo/ipv6 --------------------------------------------------------------------
