IETF Logo Mail Archive

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

"Hollenbeck, Scott" <shollenbeck@verisign.com> Wed, 06 April 2016 19:41 UTC

Return-Path: <shollenbeck@verisign.com>
X-Original-To: oauth@ietfa.amsl.com
Delivered-To: oauth@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 6327012D791 for <oauth@ietfa.amsl.com>; Wed, 6 Apr 2016 12:41:37 -0700 (PDT)
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 autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (2048-bit key) header.d=verisign-com.20150623.gappssmtp.com
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 zozPuu-BDLNW for <oauth@ietfa.amsl.com>; Wed, 6 Apr 2016 12:41:35 -0700 (PDT)
Received: from mail-oi0-x264.google.com (mail-oi0-x264.google.com [IPv6:2607:f8b0:4003:c06::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 57C7212D769 for <OAuth@ietf.org>; Wed, 6 Apr 2016 12:41:35 -0700 (PDT)
Received: by mail-oi0-x264.google.com with SMTP id c134so3531847oig.0 for <OAuth@ietf.org>; Wed, 06 Apr 2016 12:41:35 -0700 (PDT)
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 :references:in-reply-to:accept-language:content-language :content-transfer-encoding:mime-version; bh=iTEEEk3cGxDjjlEXs8ohtBRRUc4/T8WYAoTx63BdX3g=; b=QIT3PGxnMacBd00AgrJh/Q0Di+wbMK8ZjdB7YJvYv1w9gtFcV8Cw30siYi7th7xNRS KyL2Aa2nJ4E9CZ28ypsB456oHFhmWgz2khCX+smzZ1x+qWCNYOJ6Hvw/P8TwBt6Kx20j cyPpQ6bboh3BYgwF8ozqdw7TjhUbY2EtjdwvZPLluV9a4B9Q+aSsTTnJQf5dnc41xySz JlrhKv9CWFaPNrofNAPjhqSX0lsHlms4bq3EkkOFrm62jT6PvB3sd3XL1A/M/pOqy7pL nAa5u2w68u/kv+PTTYjmVeg0akmt++YOfguwXi+JQ5R/f8lEjGhKDBZXdHRVqbdlWGDp ueeQ==
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:references:in-reply-to:accept-language:content-language :content-transfer-encoding:mime-version; bh=iTEEEk3cGxDjjlEXs8ohtBRRUc4/T8WYAoTx63BdX3g=; b=fHXFDwGiJOx88IQqnzkAGlhNWuUJF/im1dnsRVC2SXKkGfRdA7NN2lWuEB4qnDadnT WVQdST5Bqx7qWMXS30MQieriji5uvCJnnMXT1o+XP+jjIs05n3ExkUFgFWFFVYmqg62Q SsHPmJHQWIwXJ4y3UduePcQfaNJh/HJHoi6lWCLxCqFIXtx0oS+2RoiHQf3tc+makN7N 1Oq39R/n00X2Vk3mtemIbgCWKD25ML8zE3MOAMzyg2xcIljr71OHxJLrBr8j046zbbyY grDcn5KcNAiTPEt2ayJaKM3S7XZbd+Je2vBWex7X9zpFS9Q8V4AUJuMaiHR4TgIjTByF hZaQ==
X-Gm-Message-State: AD7BkJIvyO3kk4nd2puZLvCUK6T4x26p8crCzMubnZ8x6GPxUWwRbQdzjllFb4s/8o5Fz2vqObgSBEncGLjx2TaP8QKV4sOx
X-Received: by 10.140.160.214 with SMTP id g205mr7833143qhg.88.1459971694693; Wed, 06 Apr 2016 12:41:34 -0700 (PDT)
Received: from brn1lxmailout01.verisign.com (brn1lxmailout01.verisign.com. [72.13.63.41]) by smtp-relay.gmail.com with ESMTPS id x77sm630695qka.5.2016.04.06.12.41.34 for <OAuth@ietf.org> (version=TLS1 cipher=AES128-SHA bits=128/128); Wed, 06 Apr 2016 12:41:34 -0700 (PDT)
X-Relaying-Domain: verisign.com
Received: from BRN1WNEXCHM01.vcorp.ad.vrsn.com (brn1wnexchm01 [10.173.152.255]) by brn1lxmailout01.verisign.com (8.13.8/8.13.8) with ESMTP id u36JfYpe021445 (version=TLSv1/SSLv3 cipher=AES256-SHA bits=256 verify=FAIL) for <OAuth@ietf.org>; Wed, 6 Apr 2016 15:41:34 -0400
Received: from BRN1WNEXMBX01.vcorp.ad.vrsn.com ([::1]) by BRN1WNEXCHM01.vcorp.ad.vrsn.com ([::1]) with mapi id 14.03.0174.001; Wed, 6 Apr 2016 15:41:33 -0400
From: "Hollenbeck, Scott" <shollenbeck@verisign.com>
To: "'OAuth@ietf.org'" <OAuth@ietf.org>
Thread-Topic: Cross-Area Review Request for RDAP Authentication
Thread-Index: AdFMdFIjlomRE03AR0yFxWcnxij5bwGUrPpQD105X8A=
Date: Wed, 06 Apr 2016 19:41:32 +0000
Message-ID: <831693C2CDA2E849A7D7A712B24E257F4A3B5A7D@BRN1WNEXMBX01.vcorp.ad.vrsn.com>
References: <831693C2CDA2E849A7D7A712B24E257F4A129732@BRN1WNEXMBX01.vcorp.ad.vrsn.com> <831693C2CDA2E849A7D7A712B24E257F4A130B17@BRN1WNEXMBX01.vcorp.ad.vrsn.com>
In-Reply-To: <831693C2CDA2E849A7D7A712B24E257F4A130B17@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/GPBWIgDbxcU_lny2T3cjktSNTcY>
Subject: Re: [OAUTH-WG] Cross-Area Review Request for RDAP Authentication
X-BeenThere: oauth@ietf.org
X-Mailman-Version: 2.1.17
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: Wed, 06 Apr 2016 19:41:37 -0000

Folks, this is the sequence of list messages that I mentioned at the end of today's meeting. Nat did reply on January 20th with "It is on my todo list but ...". I really could use affirmation or correction from clueful people...

Scott

> -----Original Message-----
> From: OAuth [mailto:oauth-bounces@ietf.org] On Behalf Of Hollenbeck,
> Scott
> Sent: Tuesday, January 19, 2016 9:40 AM
> To: 'OAuth@ietf.org'
> Subject: Re: [OAUTH-WG] Cross-Area Review Request for RDAP
> Authentication
> 
> > -----Original Message-----
> > From: Hollenbeck, Scott
> > Sent: Monday, January 11, 2016 8:31 AM
> > To: OAuth@ietf.org
> > Subject: Cross-Area Review Request for RDAP Authentication
> >
> > 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.
> 
> Can anyone help with this?
> 
> Scott
> 
> _______________________________________________
> OAuth mailing list
> OAuth@ietf.org
> https://www.ietf.org/mailman/listinfo/oauth

v2.23.0 | Report a Bug | By Email