WD11 Issue #18 - Root Authority XRDs

["Drummond Reed" <drummond.reed@cordance.net>]

This email is for closure of issue #18 from the XRI Resolution 2.0 Working Draft 11 Issues List wiki page at:

 

            http://wiki.oasis-open.org/xri/Xri2Cd02/ResWorkingDraft11

 

Please review the following text from this page and, if you don’t agree with the proposed solution, please reply to the list. SILENCE WILL BE INTERPRETED AS CLOSURE.

 

 

=== #18 – Section 7 - Returning Root Authority XRD (Gabe Wachob) ===

 

Should an XRI resolution response from a resolver always include an XRD describing the root authority the resolver?

 

BACKGROUND EMAIL THREAD

 

      http://lists.oasis-open.org/archives/xri/200608/msg00002.html

 

DISCUSSION ON 2006-8-17 TELECON

 

 * There is a need to be able to get the XRD for a root authority.

 * It is inefficient to have it returned in every reponse from a local or proxy resolver.

 * But it should not require special behaviour to serve as a root – all all authorities should be able to be self-describing.

 

PROPOSED SOLUTION (FROM 2006-8-17 TELECON) FOR WD 11

 

 * Specify that when an XRI authority is asked for anything EXCEPT it’s own self-describing XRD, the authority MUST NOT include a self-describing XRD in the response. (This is consistent with WD10 and current practice.)

 * Specify that any XRI authority that wants to function as a root authority SHOULD publish its own self-describing XRD.

 * Specify that to request a self-describing XRD for an XRI authority, a resolver can ask for it by: a) querying the authority directly at its well-known http or https address with a null query string, or b) querying a proxy resolver (or any other XRI authority) for the well-known name of the root authority (i.e., either a GCS character or a cross-reference).