Re: [webfinger] feedback for multiple "rel"

"Paul E. Jones" <paulej@packetizer.com> Sat, 22 December 2012 05:44 UTC

Return-Path: <paulej@packetizer.com>
X-Original-To: webfinger@ietfa.amsl.com
Delivered-To: webfinger@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id D3BA721E8037 for <webfinger@ietfa.amsl.com>; Fri, 21 Dec 2012 21:44:09 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.482
X-Spam-Level:
X-Spam-Status: No, score=-2.482 tagged_above=-999 required=5 tests=[AWL=-0.017, BAYES_00=-2.599, HTTP_ESCAPED_HOST=0.134]
Received: from mail.ietf.org ([64.170.98.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id gNQJI77cVVfP for <webfinger@ietfa.amsl.com>; Fri, 21 Dec 2012 21:44:09 -0800 (PST)
Received: from dublin.packetizer.com (dublin.packetizer.com [75.101.130.125]) by ietfa.amsl.com (Postfix) with ESMTP id EA70021F843E for <webfinger@ietf.org>; Fri, 21 Dec 2012 21:44:08 -0800 (PST)
Received: from sydney (rrcs-98-101-148-48.midsouth.biz.rr.com [98.101.148.48]) (authenticated bits=0) by dublin.packetizer.com (8.14.5/8.14.5) with ESMTP id qBM5i69x005013 (version=TLSv1/SSLv3 cipher=AES128-SHA bits=128 verify=NO); Sat, 22 Dec 2012 00:44:07 -0500
DKIM-Signature: v=1; a=rsa-sha256; c=simple/simple; d=packetizer.com; s=dublin; t=1356155047; bh=B33c36bGzYUF3WS1p0ni1CAkFb1zZ0hECptlxDijqZE=; h=From:To:Cc:References:In-Reply-To:Subject:Date:Message-ID: MIME-Version:Content-Type:Content-Transfer-Encoding; b=BTcFqjI8RK5aPi4LcbQOb+3kWpDbJGIhqcGWvKl202LXse7e9N7yG/5/zXo86tkFa Y86PZ0ImFo/U7sPImoSEP96SHOE5CgyW106FON9yKiPl2SeWrq8VU570N//DVCSPkw TGeCK8a4goVvwyTKsOtkMrvVSy7MUStQe1Tud/zw=
From: "Paul E. Jones" <paulej@packetizer.com>
To: 'nov matake' <matake@gmail.com>, 'Brad Fitzpatrick' <bradfitz@google.com>
References: <58036BAD-2161-4420-A724-343883F627B7@gmail.com> <077401cde003$bc74fe40$355efac0$@packetizer.com> <3B2DA5C2-0868-4738-ABB0-5D33D920EB37@gmail.com>
In-Reply-To: <3B2DA5C2-0868-4738-ABB0-5D33D920EB37@gmail.com>
Date: Sat, 22 Dec 2012 00:44:09 -0500
Message-ID: <079f01cde007$5d817310$18845930$@packetizer.com>
MIME-Version: 1.0
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: 7bit
X-Mailer: Microsoft Outlook 14.0
Thread-Index: AQHn/3n6mr+8L0+iRGJmLFJlw0GLowIzcdlqAlXgG7KXy8ThMA==
Content-Language: en-us
Cc: webfinger@ietf.org
Subject: Re: [webfinger] feedback for multiple "rel"
X-BeenThere: webfinger@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: Discussion of the Webfinger protocol proposal in the Applications Area <webfinger.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/webfinger>, <mailto:webfinger-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/webfinger>
List-Post: <mailto:webfinger@ietf.org>
List-Help: <mailto:webfinger-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/webfinger>, <mailto:webfinger-request@ietf.org?subject=subscribe>
X-List-Received-Date: Sat, 22 Dec 2012 05:44:10 -0000

Not if you shout loudly. :)  We could change it back.

I think Brad was the main proponent for this change.

Brad, what is your take?

Paul

> -----Original Message-----
> From: nov matake [mailto:matake@gmail.com]
> Sent: Saturday, December 22, 2012 12:36 AM
> To: Paul E. Jones
> Cc: webfinger@ietf.org
> Subject: Re: [webfinger] feedback for multiple "rel"
> 
> Understood.
> I saw the same debate in OAuth2 ML and saw opposite result :p
> 
> I, as a ruby library developer, prefer single "rel" because parsing
> double encoded values in library is easier than modifying developer's
> application framework.
> But at same time, as OpenID Connect library developer, it's probably too
> late to change webfinger spec ... :(
> 
> On 2012/12/22, at 14:18, Paul E. Jones <paulej@packetizer.com> wrote:
> 
> > Nov,
> >
> > It used to base space-delimited in the -02 draft:
> > http://tools.ietf.org/html/draft-ietf-appsawg-webfinger-02#section-5.3
> >
> > We had a debate over this and, as usual, I lost. :-)
> >
> > Some people expressed concerns that there might be spaces in the URL,
> > so taking two URLs like this:
> >
> > http://example.com/this one
> > http://example.com/that one
> >
> > And then putting them into the "rel" parameter like this:
> >
> > http%3A%2F%2Fexample.com%2Fthis%20one%20http%3A%2F%2Fexample.com%2Ftha
> > t%20on
> > e
> >                               ^^^   ^^^
> >
> > The ^^^ denotes the problem.
> >
> > Unescaping and splitting on spaces would give you 4 values.
> >
> > So, one has to do this:
> > encodeURIComponent(
> >   encodeURIComponent ("http://example.com/this one") + " " +
> >   encodeURIComponent ("http://example.com/that one") )
> >
> > And put that into the "rel" parameter.
> >
> > That can get a bit ugly.  I personally preferred the single rel
> > parameter, though.  I was overruled.
> >
> > Perhaps you might be more persuasive than I was.
> >
> > Paul
> >
> >> -----Original Message-----
> >> From: webfinger-bounces@ietf.org [mailto:webfinger-bounces@ietf.org]
> >> On Behalf Of nov matake
> >> Sent: Friday, December 21, 2012 11:49 PM
> >> To: webfinger@ietf.org
> >> Subject: [webfinger] feedback for multiple "rel"
> >>
> >> Hi,
> >>
> >> I have a comment for they way to specify multiple "rel" values.
> >>
> >> As a ruby library developer, my main target is rails developers.
> >> Since rails can't handle multiple same query keys, developers will
> >> need to hack query params parser in rails middleware layer.
> >> I can easily imagine it'll be an annoying part to support webfinger
> >> in rails.
> >>
> >> Is the multiple "rel" case can be a space-delimitered (or some other
> >> character) strings like multiple redirect_uri in OAuth2?
> >> Or any reason for putting multiple same keys in query parameters?
> >>
> >> Cheers,
> >>
> >> Nov Matake
> >> _______________________________________________
> >> webfinger mailing list
> >> webfinger@ietf.org
> >> https://www.ietf.org/mailman/listinfo/webfinger
> >