Re: [OAUTH-WG] I-D Action: draft-ietf-oauth-urn-sub-ns-03.txt

Brian Campbell <bcampbell@pingidentity.com> Thu, 21 June 2012 19:55 UTC

Return-Path: <bcampbell@pingidentity.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 3F1CA21F85FC for <oauth@ietfa.amsl.com>; Thu, 21 Jun 2012 12:55:46 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -5.91
X-Spam-Level:
X-Spam-Status: No, score=-5.91 tagged_above=-999 required=5 tests=[AWL=0.067, BAYES_00=-2.599, FM_FORGED_GMAIL=0.622, RCVD_IN_DNSWL_MED=-4]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id O1+0I-d3LnBV for <oauth@ietfa.amsl.com>; Thu, 21 Jun 2012 12:55:44 -0700 (PDT)
Received: from na3sys009aog122.obsmtp.com (na3sys009aog122.obsmtp.com [74.125.149.147]) by ietfa.amsl.com (Postfix) with ESMTP id 91E3121F85D4 for <oauth@ietf.org>; Thu, 21 Jun 2012 12:55:44 -0700 (PDT)
Received: from mail-qa0-f49.google.com ([209.85.216.49]) (using TLSv1) by na3sys009aob122.postini.com ([74.125.148.12]) with SMTP ID DSNKT+N8QISt5TnWJAamsuonfeZdlPO1Kvth@postini.com; Thu, 21 Jun 2012 12:55:44 PDT
Received: by qabj40 with SMTP id j40so1800327qab.15 for <oauth@ietf.org>; Thu, 21 Jun 2012 12:55:43 -0700 (PDT)
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=google.com; s=20120113; h=mime-version:in-reply-to:references:from:date:message-id:subject:to :cc:content-type:content-transfer-encoding:x-gm-message-state; bh=zcbJKPBu/VHf6ZFoE77ANv30ielQN2TMWt1MNX5ayAM=; b=B3qujLN10uqVxSVvCxmje7P5rYBsgkVhrjJis4HlO1af5ciZj3++wfDDfABIwBqrnD ZXanjELGksQYmDcenL9ljbOFJQtTBnYpEFhJtsBv0K/J5C3PTxMMNOfKM8tgxR2Kcc25 +WYU7Zfr8gKEf5k+QnbTZqSDKuJzy7sLEKL/B7JkZhnIFKUBE0vWZYBISWDl0TyxrOlD QGo0nrmq+b3lRbjTJ/cRNywqcIeLyGOTXacWqkn1Oz/MAZSmKmUjwCQc8nvoHbnTreEv Sqf+LYLvLT59qSrJmiH/+hhg9SLfLKi8TaT8rWHCjX+JK4l5UGq0Otr+0owCby0AcrSG v1gw==
Received: by 10.224.201.136 with SMTP id fa8mr1712834qab.20.1340308543373; Thu, 21 Jun 2012 12:55:43 -0700 (PDT)
MIME-Version: 1.0
Received: by 10.229.87.142 with HTTP; Thu, 21 Jun 2012 12:55:13 -0700 (PDT)
In-Reply-To: <CAC4RtVAcnGwv7yp=zwwAM--w-DubHfFpHFrKyHRzfe8Fjfg0Rg@mail.gmail.com>
References: <20120621175317.32545.76545.idtracker@ietfa.amsl.com> <CAC4RtVAcnGwv7yp=zwwAM--w-DubHfFpHFrKyHRzfe8Fjfg0Rg@mail.gmail.com>
From: Brian Campbell <bcampbell@pingidentity.com>
Date: Thu, 21 Jun 2012 13:55:13 -0600
Message-ID: <CA+k3eCS0DYEqk4SDNpWJKJvWZgTqHAkojQVTPuZKmySHPxBR1A@mail.gmail.com>
To: Barry Leiba <barryleiba@computer.org>
Content-Type: text/plain; charset="ISO-8859-1"
Content-Transfer-Encoding: quoted-printable
X-Gm-Message-State: ALoCoQkLEqUJq4bnLUCp7IXys8fA+K6L+Rsj+c3AhsjzjbiZ28gBJTZ4xJKbPrxouJYPITCcldBR
Cc: OAuth WG <oauth@ietf.org>
Subject: Re: [OAUTH-WG] I-D Action: draft-ietf-oauth-urn-sub-ns-03.txt
X-BeenThere: oauth@ietf.org
X-Mailman-Version: 2.1.12
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: <http://www.ietf.org/mail-archive/web/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: Thu, 21 Jun 2012 19:55:46 -0000

I honestly don't understand the push to have additional registries
under urn:ietf:params:oauth?

On Thu, Jun 21, 2012 at 1:28 PM, Barry Leiba <barryleiba@computer.org> wrote:
> This one's mostly there.  As Mike and Hannes are discussing, the WG
> needs to sort out exactly what goes under "oauth" here.
>
> Here's a suggestion:
> Have Section 3 specify that what comes after "oauth" are one or more
> tokens, delimited by ":".
> Have Section 3 create the registry for the first-level token, "class".
>  In your example, that's "grant-type".
> Have Section 3 specify that the definition of each "class" token
> specifies what comes after it -- how many tokens, and the meaning(s).
> Have Section 3 note that certain classes might create new
> sub-registries for what goes under them, if necessary.
> Have Section 3 note that certain classes might have *no* further
> tokens under them.
>
> I realize that there might not be any use cases envisioned right now
> for that last one, but it might be a bad idea to forbid it.
>
> Section 5:
>
>   o  Repository: [[not sure about this? this document or
>      http://www.iana.org/assignments/oauth]]
>
> Yeh, I've never been sure about that either.  I think what you want
> here is "[[The registry created in Section 3.]]".
> See RFC 6134 for how I did this with the "sieve" namespace.
>
> Barry
> _______________________________________________
> OAuth mailing list
> OAuth@ietf.org
> https://www.ietf.org/mailman/listinfo/oauth