IETF Logo Mail Archive

[OAUTH-WG] Cross-Area Review Request for RDAP Authentication

"Hollenbeck, Scott" <shollenbeck@verisign.com> Mon, 11 January 2016 13:31 UTC

Return-Path: <shollenbeck@verisign.com>
X-Original-To: oauth@ietfa.amsl.com
Delivered-To: oauth@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id C77A51A8A60 for <oauth@ietfa.amsl.com>; Mon, 11 Jan 2016 05:31:13 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.9
X-Spam-Level:
X-Spam-Status: No, score=-1.9 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1] autolearn=ham
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id BjJLb2icrE5D for <oauth@ietfa.amsl.com>; Mon, 11 Jan 2016 05:31:10 -0800 (PST)
Received: from mail-qg0-x264.google.com (mail-qg0-x264.google.com [IPv6:2607:f8b0:400d:c04::264]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id A0C4C1A8A57 for <OAuth@ietf.org>; Mon, 11 Jan 2016 05:31:07 -0800 (PST)
Received: by mail-qg0-x264.google.com with SMTP id o11so44796538qge.3 for <OAuth@ietf.org>; Mon, 11 Jan 2016 05:31:07 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=verisign-com.20150623.gappssmtp.com; s=20150623; h=from:to:subject:thread-topic:thread-index:date:message-id :accept-language:content-language:content-type :content-transfer-encoding:mime-version; bh=kMrODY3/iVH85jQ8Rnj2M+yoGAkuNZUdnnqPrj9r8aw=; b=K2DYAHTuRyydfTBLmmz4O2wziJgqkRCYBRjN+VUeUuxN82uqwVLdXsF7glG8fq4AIs FLnpJEKIwto+DYMfZeq3NtIkrb1T5EjXJx//Vzg8DyRnEj+WU7gEYFPJ4zANPXmVxwkX YaA1PnK2H28TGQQCIjidohcxXBbHyaqxzwG9ijKmaYRz+NGMdnUDrMRYQgGyMLJrKHd9 vY+1p0dMXPqj5wXXUgIxEkzcJmSbRz4FEtc0eh7sjMLcouqNspLBdR56b1Kt0sY6uLYE MnIskuGcrSmu361BPQ0JshdyVyDBesrrHReH31icS6RfIxhozXAC5uCUgFfJgCWQ8aQd rAqg==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20130820; h=x-gm-message-state:from:to:subject:thread-topic:thread-index:date :message-id:accept-language:content-language:content-type :content-transfer-encoding:mime-version; bh=kMrODY3/iVH85jQ8Rnj2M+yoGAkuNZUdnnqPrj9r8aw=; b=GPkmtcJfJ3zDvztlAOy7YK4dY3hNyVo2KkoSHCCcNRlhNNKjJP+prQgwV1OsIk8nAs x7TKBLJOp+KIs3jIoOrRSlvGmzCrghKNPymgdf1SUxVdpZEMETWhwCMfbi39+u99h9xd QD5InEoWPbNF7TYF1Q/kn/rI2L1/PeUP4UQR+GnAgv9nN0dvq7zofNK7KXTDvHyBKnVH D0zkRSMw64GVCaDqwPgMMVLwSs56TEMXlTNfwwqk915S0nLEUr+s4jykvge+SUfR1qiV 9BEy1Obx4H38bKXGQqF3kyaOadPdKIDcNImLxO1vzn5Bn86RRZWNNuoPCjj+SAN5kbsW XBEw==
X-Gm-Message-State: ALoCoQk93G/0pBahxddR6bHBtKEbLODmVmu0XgSmsi1ht6naJrHknut3OY3R7hPRdRZjlZ2csie9fBecE9ExEZoXTPwmuQCqLAiUVPy6nEkvs+ctLiNj3IU=
X-Received: by 10.55.40.160 with SMTP id o32mr9579112qko.93.1452519066635; Mon, 11 Jan 2016 05:31:06 -0800 (PST)
Received: from brn1lxmailout01.verisign.com (brn1lxmailout01.verisign.com. [72.13.63.41]) by smtp-relay.gmail.com with ESMTPS id y16sm2656273qka.6.2016.01.11.05.31.06 for <OAuth@ietf.org> (version=TLS1 cipher=AES128-SHA bits=128/128); Mon, 11 Jan 2016 05:31:06 -0800 (PST)
X-Relaying-Domain: verisign.com
Received: from brn1wnexcas01.vcorp.ad.vrsn.com (brn1wnexcas01 [10.173.152.205]) by brn1lxmailout01.verisign.com (8.13.8/8.13.8) with ESMTP id u0BDV6f6022192 (version=TLSv1/SSLv3 cipher=AES256-SHA bits=256 verify=FAIL) for <OAuth@ietf.org>; Mon, 11 Jan 2016 08:31:06 -0500
Received: from BRN1WNEXMBX01.vcorp.ad.vrsn.com ([::1]) by brn1wnexcas01.vcorp.ad.vrsn.com ([::1]) with mapi id 14.03.0174.001; Mon, 11 Jan 2016 08:31:04 -0500
From: "Hollenbeck, Scott" <shollenbeck@verisign.com>
To: "OAuth@ietf.org" <OAuth@ietf.org>
Thread-Topic: Cross-Area Review Request for RDAP Authentication
Thread-Index: AdFMdFIjlomRE03AR0yFxWcnxij5bw==
Date: Mon, 11 Jan 2016 13:31:05 +0000
Message-ID: <831693C2CDA2E849A7D7A712B24E257F4A129732@BRN1WNEXMBX01.vcorp.ad.vrsn.com>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach:
X-MS-TNEF-Correlator:
x-originating-ip: [10.173.152.4]
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: quoted-printable
MIME-Version: 1.0
Archived-At: <http://mailarchive.ietf.org/arch/msg/oauth/ir4Yu1U8_oM3l52j-difKKn3u8A>
Subject: [OAUTH-WG] Cross-Area Review Request for RDAP Authentication
X-BeenThere: oauth@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: OAUTH WG <oauth.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/oauth>, <mailto:oauth-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/oauth/>
List-Post: <mailto:oauth@ietf.org>
List-Help: <mailto:oauth-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/oauth>, <mailto:oauth-request@ietf.org?subject=subscribe>
X-List-Received-Date: Mon, 11 Jan 2016 13:31:13 -0000

I'd like to ask folks who are more familiar with OAuth than I am to please review an I-D I've written that describes an approach to using OpenID Connect with the Registration Data Access Protocol (RDAP, a product of the WEIRDS WG). Those of you who are familiar with WHOIS will understand the motivation behind the development of RDAP and the benefits of being able to authenticate clients.

The I-D can be found here:

https://datatracker.ietf.org/doc/draft-hollenbeck-weirds-rdap-openid/

Note that RDAP does not depend on clients using web browsers. I have some text in the document that describes how to use OpenID Connect with non-browser clients and I'd like to ensure that it all makes sense.

Thank you,
Scott

v2.23.0 | Report a Bug | By Email