Re: [webfinger] FW: [apps-discuss] I-D Action: draft-ietf-appsawg-webfinger-08.txt

"Paul E. Jones" <paulej@packetizer.com> Sun, 23 December 2012 00:01 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 7EFE921F894C for <webfinger@ietfa.amsl.com>; Sat, 22 Dec 2012 16:01:14 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.549
X-Spam-Level:
X-Spam-Status: No, score=-2.549 tagged_above=-999 required=5 tests=[AWL=0.049, BAYES_00=-2.599, HTML_MESSAGE=0.001]
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 cSd5ZIT0s0TD for <webfinger@ietfa.amsl.com>; Sat, 22 Dec 2012 16:01:13 -0800 (PST)
Received: from dublin.packetizer.com (dublin.packetizer.com [75.101.130.125]) by ietfa.amsl.com (Postfix) with ESMTP id 621A421F856C for <webfinger@ietf.org>; Sat, 22 Dec 2012 16:01:13 -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 qBN01BAW021616 (version=TLSv1/SSLv3 cipher=AES128-SHA bits=128 verify=NO); Sat, 22 Dec 2012 19:01:11 -0500
DKIM-Signature: v=1; a=rsa-sha256; c=simple/simple; d=packetizer.com; s=dublin; t=1356220872; bh=r08+gycZE56/zy/TK3agZ6hLOBJ84jPB8GTQ+isG7Sc=; h=From:To:Cc:References:In-Reply-To:Subject:Date:Message-ID: MIME-Version:Content-Type; b=RZ+zUIVQD8jGPTvjvgVGD8GcHgq9mZuqIrqAq5sYQtitravizfEbrqBXyKgQmVc0u FEvNObaIXtWNQ+K6OrMcGW4AWNPv4nJv6gSkUMhy9Jfr8WhAPTv3nNSxN4zv1RubqL PTTyDdYfrKCm4pOevZ9CXgRrDpN/uQdIKiTn/fEU=
From: "Paul E. Jones" <paulej@packetizer.com>
To: 'Melvin Carvalho' <melvincarvalho@gmail.com>, webfinger@googlegroups.com
References: <20121221172032.28253.90788.idtracker@ietfa.amsl.com> <065701cddfa1$fa73bc70$ef5b3550$@packetizer.com> <CAKaEYh+E6WBkw=HBVOb7H-kHNYTabY-GS3pmdRyMAJkeSOv1hg@mail.gmail.com>
In-Reply-To: <CAKaEYh+E6WBkw=HBVOb7H-kHNYTabY-GS3pmdRyMAJkeSOv1hg@mail.gmail.com>
Date: Sat, 22 Dec 2012 19:01:16 -0500
Message-ID: <001e01cde0a0$a1bbc8c0$e5335a40$@packetizer.com>
MIME-Version: 1.0
Content-Type: multipart/alternative; boundary="----=_NextPart_000_001F_01CDE076.B8E5C0C0"
X-Mailer: Microsoft Outlook 14.0
Thread-Index: AQMz7gWtxLgac+I1n0R+LgHWh9rv+QCHcUCtAYIzeSmVSRQMAA==
Content-Language: en-us
Cc: webfinger@ietf.org
Subject: Re: [webfinger] FW: [apps-discuss] I-D Action: draft-ietf-appsawg-webfinger-08.txt
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: Sun, 23 Dec 2012 00:01:14 -0000

Melvin,

 

 

This actually looks pretty good!



PEJ: Great!


Re:

The media type used for the JSON Resource Descriptor (JRD) is
"application/json"

Doesnt JRD have it's own content type?

See Eran's comment:

http://hueniverse.com/2010/05/jrd-the-other-resource-descriptor/#comment-812
2

"For now I'm using application/json, but application/xrd+json is also
possible."

Maybe something like application/jrd+json would be best?

 

PEJ: Nothing has ever been defined and RFC 6415 says JRD is
"application/json".  Should somebody (note "somebody") define something
specific for JRD?  I didn't see any other +json definitions and I know
people expressed concern with that previously (not related to WF).  If we
defined such a thing, it should either be application/jrd or
application/jrd+json.

 

Paul