IETF Logo Mail Archive

[webfinger] feedback for multiple "rel"

nov matake <matake@gmail.com> Sat, 22 December 2012 04:48 UTC

Return-Path: <matake@gmail.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 2D12021F84D9 for <webfinger@ietfa.amsl.com>; Fri, 21 Dec 2012 20:48:40 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -3.599
X-Spam-Level:
X-Spam-Status: No, score=-3.599 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, RCVD_IN_DNSWL_LOW=-1]
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 p5gLEH7A0lot for <webfinger@ietfa.amsl.com>; Fri, 21 Dec 2012 20:48:40 -0800 (PST)
Received: from mail-da0-f50.google.com (mail-da0-f50.google.com [209.85.210.50]) by ietfa.amsl.com (Postfix) with ESMTP id 05BEE21F845F for <webfinger@ietf.org>; Fri, 21 Dec 2012 20:48:39 -0800 (PST)
Received: by mail-da0-f50.google.com with SMTP id h15so2399167dan.23 for <webfinger@ietf.org>; Fri, 21 Dec 2012 20:48:39 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=x-received:from:content-type:content-transfer-encoding:subject :message-id:date:to:mime-version:x-mailer; bh=R0lAtRtXI3x/Uz48wTpTpNAhFi8bs0586MHWZjUmtdM=; b=p4c2dwuuFlz5L9u4INJIMIrv7BScQpFqqWcoNPoC1mfMfSKBxlXctK5qALZplQVUR0 DztiHfWtKbHS+wDi3PUHhbkUWXeUGXNEVaHWJ2CmarpWXnuxgP9EoOoyw7XgR35qQXNo LVq32244WbenRDcuBdcfnTDfDz3g0kRnzX/0aznhaTTt+HSLRelGtNwfFon9q19Qi1RL u65EKWrtSlfAO5qmLtnPdFgbo89W2zEqrMmA1NahwciWT3XikytL0S2HYRG3uD/hKAt8 UX50rKRR0vQJGgwA7kMp9dEkbS0U0ukJ2dyPNcRyquq76odxlV22ZXzpMG/f6eNRxz7k fd4g==
X-Received: by 10.68.204.103 with SMTP id kx7mr46276932pbc.33.1356151719770; Fri, 21 Dec 2012 20:48:39 -0800 (PST)
Received: from [192.168.1.6] (z195031.dynamic.ppp.asahi-net.or.jp. [110.4.195.31]) by mx.google.com with ESMTPS id uk9sm8146792pbc.63.2012.12.21.20.48.37 (version=TLSv1/SSLv3 cipher=OTHER); Fri, 21 Dec 2012 20:48:38 -0800 (PST)
From: nov matake <matake@gmail.com>
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: quoted-printable
Message-Id: <58036BAD-2161-4420-A724-343883F627B7@gmail.com>
Date: Sat, 22 Dec 2012 13:48:37 +0900
To: "webfinger@ietf.org" <webfinger@ietf.org>
Mime-Version: 1.0 (Mac OS X Mail 6.2 \(1499\))
X-Mailer: Apple Mail (2.1499)
Subject: [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 04:48:40 -0000

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

v2.23.0 | Report a Bug | By Email