Re: [OAUTH-WG] [Technical Errata Reported] RFC6749 (3904)
Kawasaki Takahiko <takahiko.kawasaki@neovisionaries.com> Mon, 03 March 2014 17:20 UTC
Return-Path: <takahiko.kawasaki@neovisionaries.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 A36AC1A0260 for <oauth@ietfa.amsl.com>; Mon, 3 Mar 2014 09:20:15 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.977
X-Spam-Level:
X-Spam-Status: No, score=-1.977 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, FM_FORGED_GMAIL=0.622, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_LOW=-0.7] 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 XgHvx-OUHy2h for <oauth@ietfa.amsl.com>; Mon, 3 Mar 2014 09:20:13 -0800 (PST)
Received: from mail-vc0-f176.google.com (mail-vc0-f176.google.com [209.85.220.176]) by ietfa.amsl.com (Postfix) with ESMTP id 39E8C1A0258 for <oauth@ietf.org>; Mon, 3 Mar 2014 09:20:13 -0800 (PST)
Received: by mail-vc0-f176.google.com with SMTP id la4so3840175vcb.21 for <oauth@ietf.org>; Mon, 03 Mar 2014 09:20:10 -0800 (PST)
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20130820; h=x-gm-message-state:mime-version:in-reply-to:references:date :message-id:subject:from:to:cc:content-type; bh=pM94xl0w/Bi+aFPI4m4A+9lHKQiaVcAhU6kavfTpMgk=; b=A1oidFLFvYtONXx8sqb9qjec2uvmWGxppgz/qEiqM8HwAKJ5WVK1iLa8e8Us3+JV61 53cXnFwjag7McE0cyeSNYIT3cXf0oe4qldm8FkPxHjT6i8ipdw4N9WG1as5mU3ndH09w fdCOpYCZxV5RVI6okK1ILkG9cJ86C3v+04ok1HcxwJi/jdj3TZDVTOPo2Rd5nNhxuZUX 5KIgswAjbcYDjIB0hL3sCJ/yjUUCMQ+9xzaVHu4fnN9NkI+RPHcLf9uUOlvTIdzgiGQS RQ579zaJ1AGFmxCb6UZZAmdLi7WHRasdTg7LArx3wxugmijuAfP4c4Fw/1zaqwWA29nq 00sQ==
X-Gm-Message-State: ALoCoQkS3Y3ctaQWoYo+YAWk4JLrjiytR9TMrdjj333IJCcauscdkMxiKNlQVblDVd3BcZaHCUMd
MIME-Version: 1.0
X-Received: by 10.58.238.35 with SMTP id vh3mr13013394vec.16.1393867209900; Mon, 03 Mar 2014 09:20:09 -0800 (PST)
Received: by 10.220.92.137 with HTTP; Mon, 3 Mar 2014 09:20:09 -0800 (PST)
X-Originating-IP: [58.87.202.217]
In-Reply-To: <20140301141431.C1F887FC396@rfc-editor.org>
References: <20140301141431.C1F887FC396@rfc-editor.org>
Date: Tue, 04 Mar 2014 02:20:09 +0900
Message-ID: <CACYGi5+LWYOaX_QbRo44xya+nYP99nByOwTbaXdv5U8Zyr=rAw@mail.gmail.com>
From: Kawasaki Takahiko <takahiko.kawasaki@neovisionaries.com>
To: RFC Errata System <rfc-editor@rfc-editor.org>
Content-Type: multipart/alternative; boundary="047d7bb04396e921b404f3b6ff69"
Archived-At: http://mailarchive.ietf.org/arch/msg/oauth/H3vAlO0pTGAhuvlRKpLK5bKsuhw
X-Mailman-Approved-At: Mon, 10 Mar 2014 00:41:29 -0700
Cc: turners@ieca.com, derek@ihtfp.com, oauth@ietf.org
Subject: Re: [OAUTH-WG] [Technical Errata Reported] RFC6749 (3904)
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: Mon, 03 Mar 2014 17:28:07 -0000
Hello, I made an errata report for RFC 6749 (The OAuth 2.0 Authorization Framework). http://www.rfc-editor.org/errata_search.php?rfc=6749&eid=3904 Is there any next action I should take? Is the errata reviewed without my further action? Best Regards, Takahiko Kawasaki 2014-03-01 23:14 GMT+09:00 RFC Errata System <rfc-editor@rfc-editor.org>: > The following errata report has been submitted for RFC6749, > "The OAuth 2.0 Authorization Framework". > > -------------------------------------- > You may review the report below and at: > http://www.rfc-editor.org/errata_search.php?rfc=6749&eid=3904 > > -------------------------------------- > Type: Technical > Reported by: Takahiko Kawasaki <takahiko.kawasaki@neovisionaries.com> > > Section: 11.2.2. > > Original Text > ------------- > > > Corrected Text > -------------- > o Parameter name: error > o Parameter usage location: authorization response, token response > o Change controller: IETF > o Specification document(s): RFC 6749 > > > Notes > ----- > "error" is missing and should be added to the list of Initial Registry > Contents of OAuth Parameters Registry. > > Instructions: > ------------- > This errata is currently posted as "Reported". If necessary, please > use "Reply All" to discuss whether it should be verified or > rejected. When a decision is reached, the verifying party (IESG) > can log in to change the status and edit the report, if necessary. > > -------------------------------------- > RFC6749 (draft-ietf-oauth-v2-31) > -------------------------------------- > Title : The OAuth 2.0 Authorization Framework > Publication Date : October 2012 > Author(s) : D. Hardt, Ed. > Category : PROPOSED STANDARD > Source : Web Authorization Protocol > Area : Security > Stream : IETF > Verifying Party : IESG >
- [OAUTH-WG] [Technical Errata Reported] RFC6749 (3… RFC Errata System
- Re: [OAUTH-WG] [Technical Errata Reported] RFC674… Kawasaki Takahiko
- [OAUTH-WG] [Errata Verified] RFC6749 (3904) RFC Errata System
- Re: [OAUTH-WG] [Errata Verified] RFC6749 (3904) Mike Jones
- Re: [OAUTH-WG] [Errata Verified] RFC6749 (3904) Kathleen Moriarty