Next in thread → Next in month →

Re: [xri] Minutes: XRI TC Telecon 2-3PM PT Thursday 2010-03-25

From
Erummond Qeed
Date
2010-03-26T07:32:51+00:00
ID
Thread
Re: [xri] Minutes: XRI TC Telecon 2-3PM PT Thursday 2010-03-25
No problem, Breno - we scheduled you and Will to talk about the X.500 trust profile next week.

=Drummond 

On Thu, Mar 25, 2010 at 11:59 PM, Breno de Medeiros <> wrote:

Sorry for not being able to attend. I was OOO (and out of country) on

a business trip.

On Fri, Mar 26, 2010 at 08:07, Drummond Reed <> wrote:

> Following are the minutes of the unofficial telecon of the XRI TC at:

>

> Date:  Thursday, 25 March 2010 USA

> Time:  2:00PM - 3:00PM Pacific Time (21:00-22:00 UTC)

>

> ATTENDING

>

> John Bradley

>

> Markus Sabadello

>

> Drummond Reed

>

> Eran Hammer-Lahav

>

> Will Norris

>

> REGRETS

>

> Breno de Medeiros

>

>

>

> GUESTS

>

> Joe Boyle

>

>

>

> 1) XRD 1.0 CD02 SCHEDULE

>

>

>

> Will sent an updated CD02 package to Mary McRae with current OASIS

> boilerplate.

>

>

>

> In terms of overall timing, Eran said we still need to wait for the Web

> Linking specs to be approved by IESG before XRD 1.0 can go to Committee

> Specification. After IESG approves it, it can take from 2-6 months before it

> will be an RFC.

>

>

>

> So the consensus was that we will wait until the CD public review is

> complete, then check with OASIS about what the actual dependencies on IETF

> references are for us to move to Committee Specification and then to OASIS

> Standard.

>

>

>

>

>

> 2) XRD LINKING/DELEGATION/INCLUSION

>

>

>

> Will brought up that Google still has the use case of needing one use case

> that needs to link/delegate/include another XRD, and what the trust

> characteristics are. He has the action item to bring that to the TC once

> Google is ready.

>

>

>

>

>

> 3) PROPOSAL FOR AN X.509-BASED XRI TRUST PROFILE

>

>

>

>             http://lists.oasis-open.org/archives/xri/201001/msg00083.html

>

>

>

> Breno was not able to attend the call, so this was postponed to next week.

> Will said he was also working with Breno on this, and that he'd try to have

> the two of them ready by then.

>

>

>

> 4) XRI 3.0 SYNTAX AND RESOLUTION

>

>

> http://www.oasis-open.org/committees/download.php/35972/xri-syntax-3.0-wd03.pdf

>

>

>

> Drummond explained that the next step is for additional read-throughs of the

> spec. The only feedback so far is Paul Trevithick who suggested it needed

> more examples (it has almost none at present).

>

>

>

> Joe volunteered to review the spec with fresh eyes and send any feedback to

> Drummond.

>

>

>

> We discussed the best overall direction for XRI resolution. John noted that

> what's becoming popular is WebFinger and acct: identifiers.

>

>

>

> We discussed acct: URIs. Eran said that at the last IETF meeting there was

> general consensus that they are needed, and the only discussion was about

> the syntax.

>

>

>

> Essentially WebFinger is doing LRDD discovery on an acct: URI. Eran said

> that there will be a spec for acct: URIs, and it will probably include a

> brief reference to using LRDD for discovery of an acct: URI. It is unclear

> whether that spec will be called WebFinger.

>

>

>

> John pointed out that from an XRI standpoint, every acct: URI would be

> considered an XRI  root authority. Every acct: URI is a one-segment XRI

> resolved through LRDD. One question: can acct: URIs contain relative URIs,

> or do we need to treat them separately?

>

>

>

> In any case, XRI Resolution 3.0 could just be a combination of LRDD

> discovery and XRI authority service relations. There was agreement this was

> the approach that made sense, which means we will have some dependencies on

> those specs.

>

> 5) NEXT CALL

>

>

>

> The next call is next week at the regular time. However there will NOT be a

> call the following week (April 8) due to spring break and travel.

>

>

--

--Breno

+1 (650) 214-1007 desk

+1 (408) 212-0135 (Grand Central)

MTV-41-3 : 383-A

PST (GMT-8) / PDT(GMT-7)
Next in thread → Next in month →