OASIS Mailing List ArchivesView the OASIS mailing list archive below
or browse/search using MarkMail.

 


Help: OASIS Mailing Lists Help | MarkMail Help

xri message

[Date Prev] | [Thread Prev] | [Thread Next] | [Date Next] -- [Date Index] | [Thread Index] | [List Home]


Subject: Re: [xri] XriAsRelativeUri - Question of Bindings


The reason would be to know it is abstract without having to do a get on it.

Knowing also lets you skip a step if you want the meta data you can just retrieve it directly.

It also lets you choose a more appropriate proxy.   Perhaps I have my own XRI resolver and prefer to do SAML resolution I can just bypass the http proxy for http://xri.example.com.xri.net/=jbradley and resolve =jbradley directly with my own resolver.

But you may be correct that everyone will just treat it as a URI until they get a link header telling them they can directly resolve the relative XRI if they need to.

=jbradley
On 8-Nov-08, at 7:36 PM, Chasen, Les wrote:

Taking a step back ... I have never found compelling reasons for being able to look at a http uri and knowing it was an xri.  The arguement for it in the past was for potential pre-processors. 

--------------------------
http://xri.net/=les.chasen


----- Original Message -----
From: John Bradley <jbradley@mac.com>
To: Chasen, Les
Cc: Nika Jones <njones@ouno.com>; OASIS XRI TC <xri@lists.oasis-open.org>
Sent: Sat Nov 08 21:57:08 2008
Subject: Re: [xri] XriAsRelativeUri - Question of Bindings

Yes a CNAME would work.  If we are talking about tens of organizations wanting to run proxy servers in the XRI sub-scheme space then it probably isn't a big deal.

Perhaps some automated form to add a CNAME for a given domain.  ie if I want to add an entry for xri.example.com it would add a cname for xri.example.com.xri.net pointing to xri.example.com.

Something that gets a A request for xri.example.com.cri.net and automaticly returns a CNAME for xri.example.com will have to be custom but I am certain that Peter can whip it up in a day or two hacking BIND.

What it needs to do is dead simple.

=jbradley

On 8-Nov-08, at 6:24 PM, Chasen, Les wrote:


                
        We could do it by configuration.  People telling us to add them.  That seems sub optimal.
        [Chasen, Les] I guess I am not very creative.  This is the only option I can think of.  The request would be for a cname I think.
        
        We could modify the Zone server to do some sort of proxy operation to return the A record directly.
        [Chasen, Les] Some sort of proxy operation … I am not aware of anything in DNS that does that for you in a standard fashion.  A special proxy server could be created but that would be … well … special.
        
        Or we could tell everyone to forget about using there own proxy in there HXRI and use xri.net for everything.
        
        I don't know that the how you get a name in *.xri.net needs to be a part of the spec.
        [Chasen, Les] Probably not.
        
        We will probably also define dome other mechanism to indicate a sub scheme that is not dependent on DNS.
        
        That method is also required for XRDS-Simple/XRD as I under stand it.
        
        =jbradley
        
        On 7-Nov-08, at 10:10 AM, Chasen, Les wrote:


        How do the sub-delegations of xri.net get in the zone of xri.net?
        
        From: John Bradley [mailto:jbradley@mac.com]
        Sent: Friday, November 07, 2008 11:58 AM
        To: Nika Jones
        Cc: OASIS XRI TC
        Subject: Re: [xri] XriAsRelativeUri - Question of Bindings
        
        *.xri.net is just a way to determine by inspection that the http(s) URI adheres to the XRI subjcheme for http:
        
        It has to do with the chain of authority.  We proposed in 2.0 that we use xri.* as the pattern for proxy servers.
        
        The TAG said no you cant do that it violates AWWW in that we would be steeling a host name out of everyones namespace.
        
        The principle is that you can only define policy for hosts under your domain. 
        
        So they have this as a principle but no mechanism to accomplish this.
        
        An idea that we had to accommodate there principle but still allow for people to have there own proxy servers is to set up the DNS for xri.net in such a way that if you request an A record for xri.boeing.com.xri.net it would return the A record for xri.boeing.com.  This lets boeing run there own proxy at xri.boeing.com and produce HXRI like https://xri.boeing.com.xri.net/@boeing*marty that use there own proxy server,  but are still XRI by inspection.
        
        They could get tricky and have two proxy servers one inside there firewall and one outside using dns split horizon.
        
        As the HXRI that they produce are resolvable as URI from there proxy but by inspection a partner like Lockheed could resolve them via its own resolver or at https://xri.net as it sees fit for the application.
        
        So to your question http://employees.example.com.xri.net/=nika.jones should resolve to the same meta data as http://parts.example.com.xri.net/=nika.jones  they are just separate proxies for load balancing and performance reasons.
        
        This is not requiring anyone to set up there own proxy.  However it makes it easier for people to do that if they require it.
        
        John Bradley
        =jbradley
        
        
        On 7-Nov-08, at 1:03 AM, Nika Jones wrote:
       
       
       
       
        In section 6 - "Proposed HTTP and HTTPS Bindings"
       
        http://wiki.oasis-open.org/xri/XriAsRelativeUri#head-66cc964a3fdc2ada8ed087e2bd95bca22944b7c9
       
        What exactly does *.xri.net do?
       
        If the "*" means I can put anything there, does that mean all of the resolution happens on the "*" server?
       
        Also if I designate a server (or group) with sub-domains to do resolution work... ie. employees.example.com and parts.example.com ... under the "same domain" proposal can I split that work up? And would it become something like  http://employees.example.com.xri.net/=nika.jones right?
        Wow.
       
        Nika
       
        ---------------------------------------------------------------------
        To unsubscribe from this mail list, you must leave the OASIS TC that
        generates this mail.  Follow this link to all your TCs in OASIS at:
        https://www.oasis-open.org/apps/org/workgroup/portal/my_workgroups.php
        
        
       




[Date Prev] | [Thread Prev] | [Thread Next] | [Date Next] -- [Date Index] | [Thread Index] | [List Home]