[http-auth] [Mutual] (due Aug 28) Mutual auth issues (part 1)

Yutaka OIWA <y.oiwa@aist.go.jp> Thu, 13 August 2015 02:17 UTC

From: Yutaka OIWA <y.oiwa@aist.go.jp>
To: "http-auth@ietf.org" <http-auth@ietf.org>
Thread-Topic: [Mutual] (due Aug 28) Mutual auth issues (part 1)
Thread-Index: AdDVbU8S0YCBqDw+RAOYwINxg2v0vg==
Date: Thu, 13 Aug 2015 02:17:22 +0000
Message-ID: <OS1PR01MB0200719F947ACCD628FF3D7DA07D0@OS1PR01MB0200.jpnprd01.prod.outlook.com>
Accept-Language: ja-JP, en-US
Content-Language: ja-JP
received-spf: None (protection.outlook.com: aist.go.jp does not designate permitted sender hosts)
spamdiagnosticoutput: 1:23
spamdiagnosticmetadata: NSPM
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: quoted-printable
MIME-Version: 1.0
X-MS-Exchange-CrossTenant-originalarrivaltime: 13 Aug 2015 02:17:22.7527 (UTC)
X-MS-Exchange-CrossTenant-fromentityheader: Hosted
X-MS-Exchange-CrossTenant-id: 18a7fec8-652f-409b-8369-272d9ce80620
X-MS-Exchange-Transport-CrossTenantHeadersStamped: OS1PR01MB0200
Archived-At: <http://mailarchive.ietf.org/arch/msg/http-auth/WNLMw3l4zEjKGH5HR6Y-F-7Krck>
Cc: Mutual auth contact <mutual-auth-contact-ml@aist.go.jp>
Subject: [http-auth] [Mutual] (due Aug 28) Mutual auth issues (part 1)
X-BeenThere: http-auth@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: HTTP authentication methods <http-auth.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/http-auth>, <mailto:http-auth-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/http-auth/>
List-Post: <mailto:http-auth@ietf.org>
List-Help: <mailto:http-auth-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/http-auth>, <mailto:http-auth-request@ietf.org?subject=subscribe>
X-List-Received-Date: Thu, 13 Aug 2015 02:17:28 -0000

Dear all HTTPAUTH WG members,

I'd like to have your comments on the following three issues.
Please make your initial response *before August 28*, or the
WG will consider these issues as successfully resolved
(as the WG Chair said in the Prague meeting.)

We appreciate your responses in any of the following form:
  * on the github issue tracking system (comments, pull-request etc.)
  * on this mailing list
  * on the private email
We'll summarize comments on the medium above, and send it to this
mailing list.  (Please be understood that your comments on the
private email may be included in the summary and published.)


==== draft-ietf-httpauth-mutual ====

= Section 3.1 =

[P1] Is adoption of RFC5987 OK?
https://github.com/yoiwa/httpauth-mutual/issues/1

[P2] The encoding is fixed to UTF-8, without any language.
     (justification: it is not an on-line negotiable parameter,
      and the new protocol does not need to consider older
      clients.)
https://github.com/yoiwa/httpauth-mutual/issues/2

= Section 4: Messages =

[P3] Are the reserved parameter names making sense?
https://github.com/yoiwa/httpauth-mutual/issues/3


Thank you for your cooperation.

-- 
Yutaka OIWA, Ph.D.               Cyber Physical Architecture Research Group
                                  Information Technology Research Institute
    National Institute of Advanced Industrial Science and Technology (AIST)
                      Mail addresses: <y.oiwa@aist.go.jp>, <yutaka@oiwa.jp>
OpenPGP: id[440546B5] fp[7C9F 723A 7559 3246 229D  3139 8677 9BD2 4405 46B5]

[http-auth] [Mutual] (due Aug 28) Mutual auth iss… Yutaka OIWA
Re: [http-auth] [Mutual] (due Aug 28) Mutual auth… Sophie Bremer
Re: [http-auth] [Mutual] (due Aug 28) Mutual auth… Alexey Melnikov
Re: [http-auth] [Mutual] (due Aug 28) Mutual auth… Yutaka OIWA