[OAUTH-WG] OAuth POP query

Security Developer <security.developer22@gmail.com> Sat, 14 February 2015 11:40 UTC

Return-Path: <security.developer22@gmail.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 2CA611A1BDD for <oauth@ietfa.amsl.com>; Sat, 14 Feb 2015 03:40:19 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.749
X-Spam-Level:
X-Spam-Status: No, score=-1.749 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, FREEMAIL_ENVFROM_END_DIGIT=0.25, FREEMAIL_FROM=0.001, HTML_MESSAGE=0.001, SPF_PASS=-0.001] autolearn=no
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 nrXj8r8ObgdS for <oauth@ietfa.amsl.com>; Sat, 14 Feb 2015 03:40:18 -0800 (PST)
Received: from mail-ob0-x235.google.com (mail-ob0-x235.google.com [IPv6:2607:f8b0:4003:c01::235]) (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 D27B81A1B6A for <oauth@ietf.org>; Sat, 14 Feb 2015 03:40:17 -0800 (PST)
Received: by mail-ob0-f181.google.com with SMTP id vb8so28686144obc.12 for <oauth@ietf.org>; Sat, 14 Feb 2015 03:40:17 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:date:message-id:subject:from:to:content-type; bh=E8ozAhzzh0Rrz+QUvTqoeLHnJGq52q+4XYjriL39r40=; b=m9OwOtJH4lNNBu3A3xcvsbnXMB8FRmGOZn1Sw9YZk0Ri1aXNY9+Xn0XVYAkVuFUnyG b0cP+zDhcnxp9FkHZvQqpE1MBOzBf527RV1VUhOw6e8fr+9pzc8aFdyKGuVaWQcUkgpD 1p1vWmmnpP3zMM/tC9O6gD3hD/8KA0ridUqvvnCVYlW+UBO7L2auGBy9+d3fNF08qh6j 7yN3mw+FXeim6zuCLlit6xiN1izCX0T8JQsnXAGyour84aAmpF5KpGG9t769O+EHFwAS y1RiFmMudbKl/YzMP4pPWhaIUpnU5nDo8TGIbsaOE1M8mP/cSUN7PzaBIGB7PxSOIsFW ML2A==
MIME-Version: 1.0
X-Received: by 10.60.133.20 with SMTP id oy20mr9286852oeb.55.1423914016970; Sat, 14 Feb 2015 03:40:16 -0800 (PST)
Received: by 10.202.168.143 with HTTP; Sat, 14 Feb 2015 03:40:16 -0800 (PST)
Date: Sat, 14 Feb 2015 16:40:16 +0500
Message-ID: <CAD-drXsWwk_-SH9wsVW7spNWmTzGjja-uhEk8ZYWBZc7Xw7bcw@mail.gmail.com>
From: Security Developer <security.developer22@gmail.com>
To: oauth@ietf.org, ve7jtb@ve7jtb.com
Content-Type: multipart/alternative; boundary=047d7b47204e2c1ec1050f0ad19e
Archived-At: <http://mailarchive.ietf.org/arch/msg/oauth/dQ1Za_1YuvX014LX212S_OIdzYk>
Subject: [OAUTH-WG] OAuth POP query
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: <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: Sat, 14 Feb 2015 11:40:19 -0000

Hi,

I have a couple of questions.

1- What is the status of these documents as I am interested in implementing
POP

draft-ietf-oauth-pop-architecture-00.pdf
draft-ietf-oauth-pop-key-distribution-00.pdf
draft-ietf-oauth-proof-of-possession-00.pdf
draft-ietf-oauth-signed-http-request-00.pdf

2- Should Authorization server restrict the number of authorization codes
issued to a single user after successful authentication and authorization
in OAuth? also What is the good practice in this case?

Thanks for your time.