[http-auth] (Due Dec 15) Mutual-auth issues (part 5)

大岩寛 <y.oiwa@aist.go.jp> Wed, 02 December 2015 05:30 UTC

From: 大岩寛 <y.oiwa@aist.go.jp>
To: "http-auth@ietf.org" <http-auth@ietf.org>
Thread-Topic: (Due Dec 15) Mutual-auth issues (part 5)
Thread-Index: AdEswaG5yrdRgFV1To+xlwTRHoRcAg==
Date: Wed, 02 Dec 2015 05:30:47 +0000
Message-ID: <OS1PR01MB0200B147494C1C69D780C9CBA00E0@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="iso-2022-jp"
Content-Transfer-Encoding: quoted-printable
MIME-Version: 1.0
X-MS-Exchange-CrossTenant-originalarrivaltime: 02 Dec 2015 05:30:47.9972 (UTC)
X-MS-Exchange-CrossTenant-fromentityheader: Hosted
X-MS-Exchange-CrossTenant-id: 18a7fec8-652f-409b-8369-272d9ce80620
X-MS-Exchange-Transport-CrossTenantHeadersStamped: OS1PR01MB0199
Archived-At: <http://mailarchive.ietf.org/arch/msg/http-auth/vSJp64wJK_b-5PpbhvqPRIBxDPQ>
Subject: [http-auth] (Due Dec 15) Mutual-auth issues (part 5)
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: Wed, 02 Dec 2015 05:30:55 -0000

Dear all HTTPAUTH WG members,

I'd like to have your comments on the following four issues.
Please make your initial response *before December 15*, 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-extension ====

= Section 3: Optional authentication =

[P15] We use new header for optional possibility of authentications, OK?
      WG discussion have mentioned that the current choice is more
      friendly for existing proxies and other implementations.
      Also it will co-exist with Cookie-based authentication.
https://github.com/yoiwa/httpauth-mutual/issues/15

= Section 4: General issues =

[P16] Length of parameter names:
      Some requests are there, that we should shorten
      name of parameters: how far we should go?
https://github.com/yoiwa/httpauth-mutual/issues/16

= Section 4.6 =

[P17] Is it reasonable to use logout-timeout=0 for logout request?
      Or, something more explicit like "request-logout=true" is preferred?
https://github.com/yoiwa/httpauth-mutual/issues/17

= Section 7: IANA registration =

[P18] Choice of Requirement specification levels for 
      new parameters:
      Both our choice and the WG's discussion result in Dallas
      are "Specification Required".
      Is it OK? (See RFC 5226 for other choices, again.)
https://github.com/yoiwa/httpauth-mutual/issues/18

-- 
Yutaka OIWA, Ph.D.       Leader, 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] (Due Dec 15) Mutual-auth issues (part… 大岩寛