Re: [apps-discuss] Revised webfinger draft (-02)

[Eran Hammer <[e-mail]>]

It would be appropriate for APPSAWG if the scope is narrowly defined as adding a few enhancements to RFC 6415 (which *is* what the current draft attempts to do, even though its prose might sounds grander). But in the context of the recent OAuth WG meeting discussing a competing foundation (SWD), a new WG seems to be in order.

My concern is that we are reaching a point (or maybe pass it) where progressing a work to standards track RFC status no longer translate into requiring new work to explain why it cannot build on top of the published standard. If this body throws away work as recent as October 2011 just because it's more convenient for some to start from scratch, I don't see why anyone would bother go through the significant cost and effort of getting it published here in the first place.

EH




From: [e-mail] [mailto:[e-mail]] On Behalf Of Murray S. Kucherawy
Sent: Thursday, March 29, 2012 9:18 AM
To: [e-mail]
Subject: Re: [apps-discuss] Revised webfinger draft (-02)

That sounds like a mighty strong statement that, in any case, it's not appropriate for APPSAWG.

Perhaps the proponents should request a non-WG list to talk about it for a while to let the problem definition congeal for a while, and then request a working group when a charter falls out of that.

-MSK

From: Eran Hammer [mailto:[e-mail]]<mailto:[mailto:[e-mail]]>
Sent: Thursday, March 29, 2012 9:03 AM
To: Murray S. Kucherawy; [e-mail]<mailto:[e-mail]>
Subject: RE: [apps-discuss] Revised webfinger draft (-02)

This clearly does not belong in the Security area or the OAuth working group.

I would strongly warn that moving this effort into any WG requires very careful work on the charter as historically there has been very little consensus and success in agreeing on what problems we are trying to solve. RFC 6415 was the end of a 5+ years process across multiple standard bodies including the IETF, W3C, OASIS, and the OpenID Foundation. This has proved a really hard problem to *define*.

EH

From: [e-mail]<mailto:[e-mail]> [mailto:[e-mail]] On Behalf Of Murray S. Kucherawy
Sent: Thursday, March 29, 2012 6:57 AM
To: [e-mail]<mailto:[e-mail]>
Subject: Re: [apps-discuss] Revised webfinger draft (-02)

Having talked with Barry now, an amended question:

Would this work better fit in another working group like OAuth (which has its own interest and concerns in webfinger), or perhaps in its own working group?  It may well be that it's too big to fit in APPSAWG's charter for smaller work items.

-MSK

From: [e-mail]<mailto:[e-mail]> [mailto:[e-mail]]<mailto:[mailto:[e-mail]]> On Behalf Of Murray S. Kucherawy
Sent: Thursday, March 29, 2012 4:35 AM
To: [e-mail]<mailto:[e-mail]>
Subject: Re: [apps-discuss] Revised webfinger draft (-02)

To the working group,

This has been hovering outside APPSAWG for two meetings now.  Is APPSAWG the right place to process it?  That is, should we bring it in as a working group document?  Or would it be better done through the ISE, or perhaps in some other working group?

-MSK

From: [e-mail]<mailto:[e-mail]> [mailto:[e-mail]] On Behalf Of Paul E. Jones
Sent: Wednesday, March 28, 2012 6:50 PM
To: [e-mail]<mailto:[e-mail]>
Subject: [apps-discuss] Revised webfinger draft (-02)

Folks,

I published a revised version of the Webfinger specification based on feedback I've received so far that seems to  have general agreement.  As requested, I added a change log at the end of the document that I hope will help.  The draft is here:
http://tools.ietf.org/html/draft-jones-appsawg-webfinger-02

The "diff" tool on that page allows you to quickly see exactly what changed.

Paul