
From nobody Tue Oct 13 02:27:17 2015
Return-Path: <y.oiwa@aist.go.jp>
X-Original-To: http-auth@ietfa.amsl.com
Delivered-To: http-auth@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 1261E1A701D for <http-auth@ietfa.amsl.com>; Tue, 13 Oct 2015 02:27:15 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: 3.198
X-Spam-Level: ***
X-Spam-Status: No, score=3.198 tagged_above=-999 required=5 tests=[BAYES_40=-0.001, CHARSET_FARAWAY_HEADER=3.2, RCVD_IN_DNSWL_NONE=-0.0001, SPF_PASS=-0.001] 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 G_j_NLtCvs9V for <http-auth@ietfa.amsl.com>; Tue, 13 Oct 2015 02:27:12 -0700 (PDT)
Received: from APC01-PU1-obe.outbound.protection.outlook.com (mail-pu1apc01on0055.outbound.protection.outlook.com [104.47.126.55]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-SHA384 (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 4CEC61A7015 for <http-auth@ietf.org>; Tue, 13 Oct 2015 02:27:12 -0700 (PDT)
Received: from OS1PR01MB0200.jpnprd01.prod.outlook.com (10.161.230.139) by OS1PR01MB0199.jpnprd01.prod.outlook.com (10.161.229.19) with Microsoft SMTP Server (TLS) id 15.1.293.16; Tue, 13 Oct 2015 09:27:08 +0000
Received: from OS1PR01MB0200.jpnprd01.prod.outlook.com ([10.161.230.139]) by OS1PR01MB0200.jpnprd01.prod.outlook.com ([10.161.230.139]) with mapi id 15.01.0293.007; Tue, 13 Oct 2015 09:27:09 +0000
From: =?iso-2022-jp?B?GyRCQmc0ZDQyGyhC?= <y.oiwa@aist.go.jp>
To: "http-auth@ietf.org" <http-auth@ietf.org>
Thread-Topic: (due Oct 26) Mutual-auth issues (part 4)
Thread-Index: AdEFmSW6Y4b8yLXgTGmE1i5THFADlQ==
Date: Tue, 13 Oct 2015 09:27:08 +0000
Message-ID: <OS1PR01MB02005C98D3788549349C429BA0300@OS1PR01MB0200.jpnprd01.prod.outlook.com>
Accept-Language: ja-JP, en-US
Content-Language: ja-JP
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
authentication-results: spf=none (sender IP is ) smtp.mailfrom=y.oiwa@aist.go.jp; 
x-originating-ip: [150.29.149.52]
x-microsoft-exchange-diagnostics: 1; OS1PR01MB0199; 5:EDNVNbdsm45dj0iJz3vRgp9AK4AjPbomBRhHw6YkKc0xtLfnOvaTYDiZJCtBNZOPrWILmi/HFJMV2NmNpJSdOLYUSZtNtRVZ2N5Fh6FP/o506okXxr/Vh7lA6BbJW0IEvzA9q62Cxo9A5SsI/Hzqsg==; 24:T/Eun3ZQB2r2jqkt8jCUvVZlT+M5SZje76zVUyW+v6izCh8JNJgmmN9aiHNOE8lq3M2wtZ+4OQsgm3pmNp6G3wEwE8yJE0bR+rtTEhrVgzU=; 20:+Chs0LWUgiRnAZ5GsLHMczmGd+gZiGJdtNT27yXRa6k+sljSyikywF23neEJgb6XVd/W1u1dkOcVJe7ApG0d0Q==
x-microsoft-antispam: UriScan:;BCL:0;PCL:0;RULEID:;SRVR:OS1PR01MB0199;
x-microsoft-antispam-prvs: <OS1PR01MB019939A8A8A86B3E4F3E947DA0300@OS1PR01MB0199.jpnprd01.prod.outlook.com>
x-exchange-antispam-report-test: UriScan:(58186630543729);
x-exchange-antispam-report-cfa-test: BCL:0; PCL:0; RULEID:(2401047)(5005006)(520078)(8121501046)(3002001); SRVR:OS1PR01MB0199; BCL:0; PCL:0; RULEID:; SRVR:OS1PR01MB0199; 
x-forefront-prvs: 07283408BE
x-forefront-antispam-report: SFV:NSPM; SFS:(10009020)(6009001)(189002)(199003)(504964003)(5001960100002)(101416001)(189998001)(76576001)(2900100001)(2501003)(92566002)(5004730100002)(19580405001)(19580395003)(54356999)(110136002)(50986999)(15975445007)(5002640100001)(77096005)(450100001)(5003600100002)(46102003)(85182001)(74482002)(40100003)(102836002)(33656002)(107886002)(5008740100001)(105586002)(229853001)(64706001)(122556002)(106356001)(2351001)(81156007)(10400500002)(97736004)(66066001)(86362001)(87936001)(5007970100001)(74316001); DIR:OUT; SFP:1101; SCL:1; SRVR:OS1PR01MB0199; H:OS1PR01MB0200.jpnprd01.prod.outlook.com; FPR:; SPF:None; PTR:InfoNoRecords;  MX:1; A:1; LANG:en; 
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-OriginatorOrg: aist.go.jp
X-MS-Exchange-CrossTenant-originalarrivaltime: 13 Oct 2015 09:27:08.8190 (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/iLyxFy7burpX_b5xtYfMvR4YchA>
Subject: [http-auth] (due Oct 26) Mutual-auth issues (part 4)
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: Tue, 13 Oct 2015 09:27:15 -0000

Dear all HTTPAUTH WG members,

I'd like to have your comments on the following four issues.
Please make your initial response *before October 26*,
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 l=
ist.
 (Please be understood that your comments on the private email may be inclu=
ded in the summary and published.)

=3D=3D=3D=3D draft-ietf-httpauth-mutual =3D=3D=3D=3D=20

(p11): Section 10
Two forms of descriptions are given for client state-machines,
requested by feedback comments.
We tried to clarify the normative description in the latest draft.
Is this satisfactory?
https://github.com/yoiwa/httpauth-mutual/issues/11

(p12): Section 12.1: Data Syntax
We defined non-ambiguous encoding of multiple string sets in Section 12.1.
Are definitions of VI(), VS() satisfactory?
https://github.com/yoiwa/httpauth-mutual/issues/12

(p13): Section 16: IANA Considerations
Choice of Requirement specification levels for new algorithms.
Discussions in IETF 92 proposed "Expert review" level.  Is it OK?
https://github.com/yoiwa/httpauth-mutual/issues/13

=3D=3D=3D=3D draft-ietf-httpauth-mutual-algo =3D=3D=3D=3D

(p14)
Iteration counts for "PBKDF2" construction is set to 16384.
Is this value reasonable?
https://github.com/yoiwa/httpauth-mutual/issues/14


Thank you in advance for your cooperation.


--=20
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=
]


From nobody Tue Oct 13 02:29:27 2015
Return-Path: <y.oiwa@aist.go.jp>
X-Original-To: http-auth@ietfa.amsl.com
Delivered-To: http-auth@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id A93A51A8033 for <http-auth@ietfa.amsl.com>; Tue, 13 Oct 2015 02:29:26 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: 1.299
X-Spam-Level: *
X-Spam-Status: No, score=1.299 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, CHARSET_FARAWAY_HEADER=3.2, RCVD_IN_DNSWL_NONE=-0.0001, SPF_PASS=-0.001] 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 qKBF7x_I8WNr for <http-auth@ietfa.amsl.com>; Tue, 13 Oct 2015 02:29:24 -0700 (PDT)
Received: from APC01-PU1-obe.outbound.protection.outlook.com (mail-pu1apc01on0058.outbound.protection.outlook.com [104.47.126.58]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-SHA384 (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id CFB831A038E for <http-auth@ietf.org>; Tue, 13 Oct 2015 02:29:23 -0700 (PDT)
Received: from OS1PR01MB0200.jpnprd01.prod.outlook.com (10.161.230.139) by OS1PR01MB0199.jpnprd01.prod.outlook.com (10.161.229.19) with Microsoft SMTP Server (TLS) id 15.1.293.16; Tue, 13 Oct 2015 09:29:21 +0000
Received: from OS1PR01MB0200.jpnprd01.prod.outlook.com ([10.161.230.139]) by OS1PR01MB0200.jpnprd01.prod.outlook.com ([10.161.230.139]) with mapi id 15.01.0293.007; Tue, 13 Oct 2015 09:29:21 +0000
From: =?iso-2022-jp?B?GyRCQmc0ZDQyGyhC?= <y.oiwa@aist.go.jp>
To: =?iso-2022-jp?B?GyRCQmc0ZDQyGyhC?= <y.oiwa@aist.go.jp>, "http-auth@ietf.org" <http-auth@ietf.org>
Thread-Topic: (due Sep 20) Mutual-auth issues (part 2)
Thread-Index: AdDqyXHlkUl3afdjS42jzuCm/pYJ1ga0Ap/Q
Date: Tue, 13 Oct 2015 09:29:20 +0000
Message-ID: <OS1PR01MB0200F8026EE99E8BB9774929A0300@OS1PR01MB0200.jpnprd01.prod.outlook.com>
References: <OS1PR01MB02003822745C024DCFD78C2CA0520@OS1PR01MB0200.jpnprd01.prod.outlook.com>
In-Reply-To: <OS1PR01MB02003822745C024DCFD78C2CA0520@OS1PR01MB0200.jpnprd01.prod.outlook.com>
Accept-Language: ja-JP, en-US
Content-Language: ja-JP
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
authentication-results: spf=none (sender IP is ) smtp.mailfrom=y.oiwa@aist.go.jp; 
x-originating-ip: [150.29.149.52]
x-microsoft-exchange-diagnostics: 1; OS1PR01MB0199; 5:n0r8VJyPMS5ZEbjYYQCcBqz4iTQiMUZyz4m78aQ3ioGAvPO1mG5jyTq8toTr+bYk9fcSXbhWOGbLwQrKkzL6j4e0ZyCEpJFTnyMMIEsPS/DS1rv7i/4aG9f+nXNOMzcQ6PjH9UqoEr6hOTrXiVVO9g==; 24:2HnffTkXN9jT0vuJZIDN7rgBrlX9Ras3B9Uj7KuoyxdJp4pFj1wt/iS+mg7J2IKE/24pqxOJmBzMcgRnwSrIOdQP/DknAkEs+/dVB/ncduE=; 20:P6Dxil/gW0JYofXS68rSnt96z+UhL5eU/jdL/vaHCxOW6c3ckw0bJ76pYn1+wdSV+BcslSHVnDftosK3KvruJg==
x-microsoft-antispam: UriScan:;BCL:0;PCL:0;RULEID:;SRVR:OS1PR01MB0199;
x-microsoft-antispam-prvs: <OS1PR01MB0199DF997E4527D700DC633CA0300@OS1PR01MB0199.jpnprd01.prod.outlook.com>
x-exchange-antispam-report-test: UriScan:(58186630543729);
x-exchange-antispam-report-cfa-test: BCL:0; PCL:0; RULEID:(2401047)(5005006)(520078)(8121501046)(3002001); SRVR:OS1PR01MB0199; BCL:0; PCL:0; RULEID:; SRVR:OS1PR01MB0199; 
x-forefront-prvs: 07283408BE
x-forefront-antispam-report: SFV:NSPM; SFS:(10009020)(6009001)(377454003)(189002)(199003)(13464003)(5001960100002)(101416001)(11100500001)(189998001)(76176999)(76576001)(2900100001)(2501003)(92566002)(5004730100002)(19580405001)(19580395003)(54356999)(50986999)(15975445007)(5002640100001)(77096005)(450100001)(5003600100002)(46102003)(85182001)(74482002)(40100003)(102836002)(33656002)(107886002)(5008740100001)(105586002)(64706001)(122556002)(2950100001)(106356001)(81156007)(5001770100001)(10400500002)(97736004)(66066001)(86362001)(87936001)(5007970100001)(74316001); DIR:OUT; SFP:1101; SCL:1; SRVR:OS1PR01MB0199; H:OS1PR01MB0200.jpnprd01.prod.outlook.com; FPR:; SPF:None; PTR:InfoNoRecords;  MX:1; A:1; LANG:en; 
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-OriginatorOrg: aist.go.jp
X-MS-Exchange-CrossTenant-originalarrivaltime: 13 Oct 2015 09:29:21.0239 (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/4EbqL_IGVoHWPH2cgirfukSKsXk>
Subject: Re: [http-auth] (due Sep 20) Mutual-auth issues (part 2)
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: Tue, 13 Oct 2015 09:29:26 -0000

Dear HTTPAUTH WG members,

We'll go forward with the current specification regarding the following iss=
ues.
Thank you.

--=20
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=
]

> -----Original Message-----
> From: Yutaka OIWA
> Sent: Wednesday, September 9, 2015 3:42 PM
> To: http-auth@ietf.org
> Subject: [http-auth] (due Sep 20) Mutual-auth issues (part 2)
>=20
> Dear all HTTPAUTH WG members,
>=20
> I'd like to have your comments on the following four issues.
> Please make your initial response *before September 20*, or the WG will c=
onsider
> these issues as successfully resolved (as the WG Chair said in the Prague
> meeting.)
>=20
> 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 incl=
uded
> in the summary and published.)
>=20
>=20
> =3D=3D=3D=3D draft-ietf-httpauth-mutual =3D=3D=3D=3D
>=20
> =3D Section 4.1: 401-INIT =3D
>=20
> [P4] The set of pwd-hash parameters for user-DB migrations:
>      none, md5, digest-md5, sha1 makes sense?
>   https://github.com/yoiwa/httpauth-mutual/issues/4
>=20
> [P5] reason parameter:
>      Are the listed reasons good and complete?
>   https://github.com/yoiwa/httpauth-mutual/issues/5
>=20
> =3D Section 4.3 401-KEX-S1 =3D
>=20
> [P6] Minimum parameter ranges:
>   * 80+ bits for session id (sid)
>   * 128+ slots for active nonces: nc-max, nc-window
>   * 60+ seconds for session key retention
>   https://github.com/yoiwa/httpauth-mutual/issues/6
>=20
> =3D Section 5: Authentication Realms =3D
>=20
> [P7] Current choices for authentication scopes are single-port, single-ho=
st,
> and wildcard-domain.
> Are these choices complete?
>   https://github.com/yoiwa/httpauth-mutual/issues/7
>=20
>=20
> Thank you for your cooperation.
>=20
> --
> Yutaka OIWA, Ph.D.               Cyber Physical Architecture Research Gro=
up
>                                   Information Technology Research Institu=
te
>     National Institute of Advanced Industrial Science and Technology (AIS=
T)
>                       Mail addresses: <y.oiwa@aist.go.jp>, <yutaka@oiwa.j=
p>
> OpenPGP: id[440546B5] fp[7C9F 723A 7559 3246 229D  3139 8677 9BD2 4405 46=
B5]
>=20
>=20
> _______________________________________________
> http-auth mailing list
> http-auth@ietf.org
> https://www.ietf.org/mailman/listinfo/http-auth


From nobody Tue Oct 13 02:30:38 2015
Return-Path: <y.oiwa@aist.go.jp>
X-Original-To: http-auth@ietfa.amsl.com
Delivered-To: http-auth@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 755FA1A8714 for <http-auth@ietfa.amsl.com>; Tue, 13 Oct 2015 02:30:37 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: 1.299
X-Spam-Level: *
X-Spam-Status: No, score=1.299 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, CHARSET_FARAWAY_HEADER=3.2, RCVD_IN_DNSWL_NONE=-0.0001, SPF_PASS=-0.001] 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 99KZh8tZIvsn for <http-auth@ietfa.amsl.com>; Tue, 13 Oct 2015 02:30:30 -0700 (PDT)
Received: from APC01-PU1-obe.outbound.protection.outlook.com (mail-pu1apc01on0075.outbound.protection.outlook.com [104.47.126.75]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-SHA384 (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 71B791A8033 for <http-auth@ietf.org>; Tue, 13 Oct 2015 02:30:29 -0700 (PDT)
Received: from OS1PR01MB0200.jpnprd01.prod.outlook.com (10.161.230.139) by OS1PR01MB0199.jpnprd01.prod.outlook.com (10.161.229.19) with Microsoft SMTP Server (TLS) id 15.1.293.16; Tue, 13 Oct 2015 09:30:26 +0000
Received: from OS1PR01MB0200.jpnprd01.prod.outlook.com ([10.161.230.139]) by OS1PR01MB0200.jpnprd01.prod.outlook.com ([10.161.230.139]) with mapi id 15.01.0293.007; Tue, 13 Oct 2015 09:30:26 +0000
From: =?iso-2022-jp?B?GyRCQmc0ZDQyGyhC?= <y.oiwa@aist.go.jp>
To: "http-auth@ietf.org" <http-auth@ietf.org>
Thread-Topic: (due Oct 04) Mutual-auth issues (part 3)
Thread-Index: AdD2C0A8YXdwq6b8Q9+w1xwKGLCSuQPjnxhg
Date: Tue, 13 Oct 2015 09:30:26 +0000
Message-ID: <OS1PR01MB02003E06FAF56387CAA17A65A0300@OS1PR01MB0200.jpnprd01.prod.outlook.com>
Accept-Language: ja-JP, en-US
Content-Language: ja-JP
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
authentication-results: spf=none (sender IP is ) smtp.mailfrom=y.oiwa@aist.go.jp; 
x-originating-ip: [150.29.149.52]
x-microsoft-exchange-diagnostics: 1; OS1PR01MB0199; 5:SJskfWbTET67tGDmYGz59Ip6YJh+xwFSPbnlpLUt1RDlW4waLiYRPso0/o6CyyoyBQ8j2/PjdDYA2MHnVw02oN6D01qM08pZ1tVAS76ND33PyLYIBJuVU7l6Jzd6CJI+OEJWKJEog69Kj7bh9A1v0Q==; 24:UBPHZl/kann6FqMtfd09eAZRHu/UQgiGLHMuJuk2IXKlBxoMoBAhjxUdG8F0YjfrZmlTyuaxoN83+y6uuxIUkVC+rxB9EipL3K20zrZ6sm0=; 20:4zj3qEM7g+iSEL2PnPTzi4GKxF+uyziQBA24s9MrqwXImbHCHSf6dDKljb/Z3/ZCfPoAdn24V5TH5fChnksLGw==
x-microsoft-antispam: UriScan:;BCL:0;PCL:0;RULEID:;SRVR:OS1PR01MB0199;
x-microsoft-antispam-prvs: <OS1PR01MB01990072B4CBBA31E9957EF4A0300@OS1PR01MB0199.jpnprd01.prod.outlook.com>
x-exchange-antispam-report-test: UriScan:(58186630543729);
x-exchange-antispam-report-cfa-test: BCL:0; PCL:0; RULEID:(2401047)(5005006)(520078)(8121501046)(3002001); SRVR:OS1PR01MB0199; BCL:0; PCL:0; RULEID:; SRVR:OS1PR01MB0199; 
x-forefront-prvs: 07283408BE
x-forefront-antispam-report: SFV:NSPM; SFS:(10009020)(6009001)(377454003)(189002)(199003)(504964003)(13464003)(5001960100002)(101416001)(11100500001)(189998001)(76576001)(2900100001)(2501003)(92566002)(5004730100002)(19580405001)(19580395003)(54356999)(110136002)(50986999)(15975445007)(5002640100001)(77096005)(450100001)(5003600100002)(46102003)(85182001)(74482002)(40100003)(102836002)(33656002)(107886002)(5008740100001)(105586002)(64706001)(122556002)(106356001)(2351001)(81156007)(10400500002)(97736004)(66066001)(86362001)(87936001)(5007970100001)(74316001); DIR:OUT; SFP:1101; SCL:1; SRVR:OS1PR01MB0199; H:OS1PR01MB0200.jpnprd01.prod.outlook.com; FPR:; SPF:None; PTR:InfoNoRecords;  MX:1; A:1; LANG:en; 
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-OriginatorOrg: aist.go.jp
X-MS-Exchange-CrossTenant-originalarrivaltime: 13 Oct 2015 09:30:26.5102 (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/03GNlZVcot98F-e1ZaIIUtsVhok>
Subject: Re: [http-auth] (due Oct 04) Mutual-auth issues (part 3)
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: Tue, 13 Oct 2015 09:30:37 -0000

Dear HTTPAUTH WG members,

We'll go forward with the current specification regarding the following iss=
ues.
Thank you.

--=20
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=
]

> -----Original Message-----
> From: Yutaka OIWA
> Sent: Wednesday, September 23, 2015 11:27 PM
> To: 'http-auth@ietf.org' <http-auth@ietf.org>
> Subject: (due Oct 04) Mutual-auth issues (part 3)
>=20
> Dear all HTTPAUTH WG members,
>=20
> I'd like to have your comments on the following four issues.
> Please make your initial response *before October 04*, or the WG will con=
sider
> these issues as successfully resolved (as the WG Chair said in the Prague
> meeting.)
>=20
> 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 incl=
uded
> in the summary and published.)
>=20
> This time, all of issues are related with TLS channel bindings.
> Related part is Section 7 of the draft-ietf-httpauth-mutual.
>=20
> (P8)
> Is it reasonable to use RFC 5929 "TLS channel binding"?
>=20
> We guess general consensus is "yes", with some care for known vulnerabili=
ties.
> These comments are already reflected in the latest draft.
> Additional comments are welcome.
> https://github.com/yoiwa/httpauth-mutual/issues/8
>=20
>=20
> (P9)
> tls-unique binding is somewhat tricky with HTTPS authentication, as keys =
might
> be different among multi-trip exchange requests, especially when anonymou=
s TLS
> ciphersuite is used.
> Current definition "will work", at least.
> Do you think the current text is satisfactory?
> Are more cautionary texts needed?
> https://github.com/yoiwa/httpauth-mutual/issues/9
>=20
>=20
> (P10)
> If 512-bit-worth user authentication is performed on TLS channels with
> 256-bit-worth server authentication (RSA certificate with SHA-256 hash), =
is
> it satisfactory to use 256-bit channel binding datum?
> Use of RFC 5929 implies this, because binding datum size is determined on=
ly
> by TLS certificate hash algorithm.
> https://github.com/yoiwa/httpauth-mutual/issues/10
>=20
>=20
>=20
> Thank you in advance for your cooperation.
>=20
> --
> Yutaka OIWA, Ph.D.               Cyber Physical Architecture Research Gro=
up
>                                   Information Technology Research Institu=
te
>     National Institute of Advanced Industrial Science and Technology (AIS=
T)
>                       Mail addresses: <y.oiwa@aist.go.jp>, <yutaka@oiwa.j=
p>
> OpenPGP: id[440546B5] fp[7C9F 723A 7559 3246 229D  3139 8677 9BD2 4405 46=
B5]


From nobody Sun Oct 18 04:43:54 2015
Return-Path: <internet-drafts@ietf.org>
X-Original-To: http-auth@ietfa.amsl.com
Delivered-To: http-auth@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 45B301A1A48; Sun, 18 Oct 2015 04:43:52 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.9
X-Spam-Level: 
X-Spam-Status: No, score=-1.9 tagged_above=-999 required=5 tests=[BAYES_00=-1.9] 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 FOwHkcQ6aEak; Sun, 18 Oct 2015 04:43:50 -0700 (PDT)
Received: from ietfa.amsl.com (localhost [IPv6:::1]) by ietfa.amsl.com (Postfix) with ESMTP id 98E0B1A1A45; Sun, 18 Oct 2015 04:43:50 -0700 (PDT)
MIME-Version: 1.0
Content-Type: text/plain; charset="utf-8"
Content-Transfer-Encoding: 7bit
From: internet-drafts@ietf.org
To: <i-d-announce@ietf.org>
X-Test-IDTracker: no
X-IETF-IDTracker: 6.6.0
Auto-Submitted: auto-generated
Precedence: bulk
Message-ID: <20151018114350.19020.40343.idtracker@ietfa.amsl.com>
Date: Sun, 18 Oct 2015 04:43:50 -0700
Archived-At: <http://mailarchive.ietf.org/arch/msg/http-auth/pylteCwgmSFuAkT39JWpiQX_GxY>
Cc: http-auth@ietf.org
Subject: [http-auth] I-D Action: draft-ietf-httpauth-scram-auth-08.txt
X-BeenThere: http-auth@ietf.org
X-Mailman-Version: 2.1.15
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: Sun, 18 Oct 2015 11:43:52 -0000

A New Internet-Draft is available from the on-line Internet-Drafts directories.
 This draft is a work item of the Hypertext Transfer Protocol Authentication Working Group of the IETF.

        Title           : Salted Challenge Response (SCRAM) HTTP Authentication Mechanism
        Author          : Alexey Melnikov
	Filename        : draft-ietf-httpauth-scram-auth-08.txt
	Pages           : 18
	Date            : 2015-10-18

Abstract:
   The secure authentication mechanism most widely deployed and used by
   Internet application protocols is the transmission of clear-text
   passwords over a channel protected by Transport Layer Security (TLS).
   There are some significant security concerns with that mechanism,
   which could be addressed by the use of a challenge response
   authentication mechanism protected by TLS.  Unfortunately, the HTTP
   Digest challenge response mechanism presently on the standards track
   failed widespread deployment, and have had success only in limited
   use.

   This specification describes a family of HTTP authentication
   mechanisms called the Salted Challenge Response Authentication
   Mechanism (SCRAM), which addresses security concerns with HTTP Digest
   and meets the deployability requirements.  When used in combination
   with TLS or an equivalent security layer, a mechanism from this
   family could improve the status-quo for HTTP authentication.


The IETF datatracker status page for this draft is:
https://datatracker.ietf.org/doc/draft-ietf-httpauth-scram-auth/

There's also a htmlized version available at:
https://tools.ietf.org/html/draft-ietf-httpauth-scram-auth-08

A diff from the previous version is available at:
https://www.ietf.org/rfcdiff?url2=draft-ietf-httpauth-scram-auth-08


Please note that it may take a couple of minutes from the time of submission
until the htmlized version and diff are available at tools.ietf.org.

Internet-Drafts are also available by anonymous FTP at:
ftp://ftp.ietf.org/internet-drafts/


From nobody Sun Oct 18 12:34:38 2015
Return-Path: <tony@att.com>
X-Original-To: http-auth@ietfa.amsl.com
Delivered-To: http-auth@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id B76421ACEBD for <http-auth@ietfa.amsl.com>; Sun, 18 Oct 2015 12:34:36 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.245
X-Spam-Level: 
X-Spam-Status: No, score=-1.245 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, IP_NOT_FRIENDLY=0.334, MISSING_HEADERS=1.021, RCVD_IN_DNSWL_LOW=-0.7] 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 w3g6rWENFBOS for <http-auth@ietfa.amsl.com>; Sun, 18 Oct 2015 12:34:35 -0700 (PDT)
Received: from mx0b-00191d01.pphosted.com (mx0b-00191d01.pphosted.com [67.231.157.136]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id B41411ACEB7 for <http-auth@ietf.org>; Sun, 18 Oct 2015 12:34:35 -0700 (PDT)
Received: from pps.filterd (m0049463.ppops.net [127.0.0.1]) by m0049463.ppops.net-00191d01. (8.15.0.59/8.15.0.59) with SMTP id t9IJY82e009414 for <http-auth@ietf.org>; Sun, 18 Oct 2015 15:34:34 -0400
Received: from alpi154.enaf.aldc.att.com (sbcsmtp6.sbc.com [144.160.229.23]) by m0049463.ppops.net-00191d01. with ESMTP id 1xkjq6ew1x-1 (version=TLSv1/SSLv3 cipher=ECDHE-RSA-AES256-GCM-SHA384 bits=256 verify=NOT) for <http-auth@ietf.org>; Sun, 18 Oct 2015 15:34:34 -0400
Received: from enaf.aldc.att.com (localhost [127.0.0.1]) by alpi154.enaf.aldc.att.com (8.14.5/8.14.5) with ESMTP id t9IJYY5m019709 for <http-auth@ietf.org>; Sun, 18 Oct 2015 15:34:34 -0400
Received: from alpi133.aldc.att.com (alpi133.aldc.att.com [130.8.217.3]) by alpi154.enaf.aldc.att.com (8.14.5/8.14.5) with ESMTP id t9IJYR5K019666 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-GCM-SHA384 bits=256 verify=NO) for <http-auth@ietf.org>; Sun, 18 Oct 2015 15:34:31 -0400
Received: from alpi153.aldc.att.com (alpi153.aldc.att.com [130.8.42.31]) by alpi133.aldc.att.com (RSA Interceptor) for <http-auth@ietf.org>; Sun, 18 Oct 2015 19:34:23 GMT
Received: from aldc.att.com (localhost [127.0.0.1]) by alpi153.aldc.att.com (8.14.5/8.14.5) with ESMTP id t9IJYNg1023615 for <http-auth@ietf.org>; Sun, 18 Oct 2015 15:34:23 -0400
Received: from mailgw1.maillennium.att.com (maillennium.att.com [135.25.114.99]) by alpi153.aldc.att.com (8.14.5/8.14.5) with ESMTP id t9IJYJjk023536 for <http-auth@ietf.org>; Sun, 18 Oct 2015 15:34:20 -0400
Received: from tonys-macbook-pro.local (unknown[135.110.240.3](untrusted sender)) by maillennium.att.com (mailgw1) with ESMTP id <20151018193418gw100dvb6le>; Sun, 18 Oct 2015 19:34:19 +0000
X-Originating-IP: [135.110.240.3]
References: <20151018114350.19020.40343.idtracker@ietfa.amsl.com>
Cc: http-auth@ietf.org
From: Tony Hansen <tony@att.com>
Message-ID: <5623F439.9080105@att.com>
Date: Sun, 18 Oct 2015 15:34:17 -0400
User-Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.10; rv:38.0) Gecko/20100101 Thunderbird/38.3.0
MIME-Version: 1.0
In-Reply-To: <20151018114350.19020.40343.idtracker@ietfa.amsl.com>
Content-Type: text/plain; charset=windows-1252
Content-Transfer-Encoding: 7bit
X-RSA-Inspected: yes
X-RSA-Classifications: public
X-Proofpoint-Virus-Version: vendor=fsecure engine=2.50.10432:, , definitions=2015-10-18_16:, , signatures=0
X-Proofpoint-Spam-Details: rule=outbound_policy_notspam policy=outbound_policy score=0 spamscore=0 suspectscore=0 malwarescore=0 phishscore=0 adultscore=0 bulkscore=0 classifier=spam adjust=0 reason=mlx scancount=1 engine=8.0.1-1507310000 definitions=main-1510180367
Archived-At: <http://mailarchive.ietf.org/arch/msg/http-auth/kTjyE9Ayj4Moky4JVviliWWr1nI>
Subject: Re: [http-auth] I-D Action: draft-ietf-httpauth-scram-auth-08.txt
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: Sun, 18 Oct 2015 19:34:36 -0000

On 10/18/15 7:43 AM, internet-drafts@ietf.org wrote:
> A New Internet-Draft is available from the on-line Internet-Drafts directories.
>  This draft is a work item of the Hypertext Transfer Protocol Authentication Working Group of the IETF.
>
>         Title           : Salted Challenge Response (SCRAM) HTTP Authentication Mechanism
>         Author          : Alexey Melnikov
> 	Filename        : draft-ietf-httpauth-scram-auth-08.txt
> 	Pages           : 18
> 	Date            : 2015-10-18

I read through this draft. I spotted one nit that I sent directly to
Alexey. Other than that, I did not see anything wrong.

Regarding the open issue "Should "sid" directive be an attribute or a
new HTTP header field shared with other HTTP authentication
mechanisms?", I think the way it is specified in this document as part
of the WWW-Authenticate header is just fine.

After information from Precis is incorporated, this document looks ready
for WGLC.

    Tony Hansen


From nobody Wed Oct 21 05:24:20 2015
Return-Path: <rifaat.ietf@gmail.com>
X-Original-To: http-auth@ietfa.amsl.com
Delivered-To: http-auth@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id D1A1C1A1B20 for <http-auth@ietfa.amsl.com>; Wed, 21 Oct 2015 05:24:17 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.999
X-Spam-Level: 
X-Spam-Status: No, score=-1.999 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, FREEMAIL_FROM=0.001, HTML_MESSAGE=0.001, SPF_PASS=-0.001] 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 5X5QhtxDSAN3 for <http-auth@ietfa.amsl.com>; Wed, 21 Oct 2015 05:24:16 -0700 (PDT)
Received: from mail-ig0-x229.google.com (mail-ig0-x229.google.com [IPv6:2607:f8b0:4001:c05::229]) (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 050D21A034C for <http-auth@ietf.org>; Wed, 21 Oct 2015 05:24:15 -0700 (PDT)
Received: by igbni9 with SMTP id ni9so92475665igb.1 for <http-auth@ietf.org>; Wed, 21 Oct 2015 05:24:15 -0700 (PDT)
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=jSyBmKMhR6XiBlC++DSlZxIbswxc7eIzIzXo3LiQ3z4=; b=aRDxPi6soNy13jWey1ivnb3f4VwkYP7WvaBMR05SU93LITYLAyX0jVecDTx283rmHy jSw7yAotQmQJ6zg1kMQJJ8j8MtXJQLY/53h/29Oxs/vl7Knyoa2QJMyZQ5CaaLsZB9W5 FztNSAXFhjd4fqxMGPTfPAEj/sYH9jN2T0x+u3AXTgJhWDr1uZUzy+wOSbzTwvxZvEOV Fwc0T31BGLXkPHl1zq6yA+UTQMNHQPjXMDGmNRp8irxU5cQH3I8EXMK7MpDmAhC/bicQ Wj0ODe6/dRzxd4QOE+fGmrG54seTmh4qRwc3WD6rjpXVc/ocFAQMN25nZReRq2GdtSQ+ A5vw==
MIME-Version: 1.0
X-Received: by 10.50.111.231 with SMTP id il7mr10395492igb.34.1445430255321; Wed, 21 Oct 2015 05:24:15 -0700 (PDT)
Received: by 10.107.26.208 with HTTP; Wed, 21 Oct 2015 05:24:15 -0700 (PDT)
Date: Wed, 21 Oct 2015 08:24:15 -0400
Message-ID: <CAGL6epJxdnEqYfutqvMZUA=0c2pW1Z3xTwdTVMF2sEYRVE2RVQ@mail.gmail.com>
From: Rifaat Shekh-Yusef <rifaat.ietf@gmail.com>
To: "http-auth@ietf.org" <http-auth@ietf.org>
Content-Type: multipart/alternative; boundary=047d7b4142c8ea8b0d05229c74d7
Archived-At: <http://mailarchive.ietf.org/arch/msg/http-auth/n3XXIFeFBvgGw92xwtRhfkOoi4A>
Subject: [http-auth] WGLC for draft-ietf-httpauth-scram-auth-08
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, 21 Oct 2015 12:24:18 -0000

--047d7b4142c8ea8b0d05229c74d7
Content-Type: text/plain; charset=UTF-8

HTTPAuth WG,

We are starting a Work Group Last Call (WGLC) for the
draft-ietf-httpauth-scram-auth-08 document:
https://tools.ietf.org/html/draft-ietf-httpauth-scram-auth-08

This will be a 3 week WGLC, because of the IETF week.

Please, review the document and provide your feedback, on the HTTPAuth
mailing list, by November 11, 2015.

Regards,
 Rifaat & Yoav

--047d7b4142c8ea8b0d05229c74d7
Content-Type: text/html; charset=UTF-8
Content-Transfer-Encoding: quoted-printable

<div dir=3D"ltr"><div>HTTPAuth WG,</div><div><br></div><div>We are starting=
 a Work Group Last Call (WGLC) for the draft-ietf-httpauth-scram-auth-08 do=
cument:</div><div><a href=3D"https://tools.ietf.org/html/draft-ietf-httpaut=
h-scram-auth-08">https://tools.ietf.org/html/draft-ietf-httpauth-scram-auth=
-08</a></div><div><br></div><div>This will be a 3 week WGLC, because of the=
 IETF week.</div><div><br></div><div>Please, review the document and provid=
e your feedback, on the HTTPAuth mailing list, by November 11, 2015.</div><=
div><br></div><div>Regards,</div><div>=C2=A0Rifaat &amp; Yoav</div><div><br=
></div></div>

--047d7b4142c8ea8b0d05229c74d7--


From nobody Mon Oct 26 07:06:45 2015
Return-Path: <simon@josefsson.org>
X-Original-To: http-auth@ietfa.amsl.com
Delivered-To: http-auth@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id C169F1B40CE for <http-auth@ietfa.amsl.com>; Mon, 26 Oct 2015 07:06:44 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.551
X-Spam-Level: 
X-Spam-Status: No, score=-1.551 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, HELO_EQ_SE=0.35, 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 053dLL4t6k0D for <http-auth@ietfa.amsl.com>; Mon, 26 Oct 2015 07:06:43 -0700 (PDT)
Received: from duva.sjd.se (duva.sjd.se [IPv6:2001:9b0:1:1702::100]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id AD2481B40D8 for <http-auth@ietf.org>; Mon, 26 Oct 2015 07:06:42 -0700 (PDT)
Received: from latte.josefsson.org ([155.4.17.2]) (authenticated bits=0) by duva.sjd.se (8.14.4/8.14.4/Debian-4) with ESMTP id t9QE6a43013954 (version=TLSv1/SSLv3 cipher=AES128-GCM-SHA256 bits=128 verify=NOT); Mon, 26 Oct 2015 15:06:38 +0100
From: Simon Josefsson <simon@josefsson.org>
To: Rifaat Shekh-Yusef <rifaat.ietf@gmail.com>
References: <CAGL6epJxdnEqYfutqvMZUA=0c2pW1Z3xTwdTVMF2sEYRVE2RVQ@mail.gmail.com>
OpenPGP: id=54265E8C; url=http://josefsson.org/54265e8c.txt
X-Hashcash: 1:22:151026:http-auth@ietf.org::8iR7pUH/KQqKUsFO:7FMG
X-Hashcash: 1:22:151026:rifaat.ietf@gmail.com::I6id3znww+ZGkAPZ:XvmM
Date: Mon, 26 Oct 2015 15:06:35 +0100
In-Reply-To: <CAGL6epJxdnEqYfutqvMZUA=0c2pW1Z3xTwdTVMF2sEYRVE2RVQ@mail.gmail.com> (Rifaat Shekh-Yusef's message of "Wed, 21 Oct 2015 08:24:15 -0400")
Message-ID: <87lhapsp04.fsf@latte.josefsson.org>
User-Agent: Gnus/5.130014 (Ma Gnus v0.14) Emacs/24.4 (gnu/linux)
MIME-Version: 1.0
Content-Type: multipart/signed; boundary="=-=-="; micalg=pgp-sha256; protocol="application/pgp-signature"
X-Virus-Scanned: clamav-milter 0.98.7 at duva.sjd.se
X-Virus-Status: Clean
Archived-At: <http://mailarchive.ietf.org/arch/msg/http-auth/D9B2wNqITd_IXfP-BW38qZRN3Do>
Cc: "http-auth@ietf.org" <http-auth@ietf.org>
Subject: Re: [http-auth] WGLC for draft-ietf-httpauth-scram-auth-08
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: Mon, 26 Oct 2015 14:06:44 -0000

--=-=-=
Content-Type: text/plain

Rifaat Shekh-Yusef <rifaat.ietf@gmail.com> writes:

> HTTPAuth WG,
>
> We are starting a Work Group Last Call (WGLC) for the
> draft-ietf-httpauth-scram-auth-08 document:
> https://tools.ietf.org/html/draft-ietf-httpauth-scram-auth-08

There appears to be some traces of channel binding support, for example
the security consideration talks about how to the SCRAM channel binding
mechanism can be used to twart some attacks, and there is a reference to
the tls-server-end-point document.  Further, section 5 says that the
channel binding flag is 'n', 'y' or 'p', which is unhelpful as this
document only supports 'n' so it should say that instead.

I believe it would be useful to have support for channel bindings when
used over HTTPS to have better security properties.  Given the status of
SCRAM-PLUS (with having to require tls-session-hash to have tls-unique
be secure) I think it is acceptable to publish this document without it.
Someone can specify a SCRAM-SHA256-PLUS HTTP Authentication Mechanism in
the future should the need arise.

I suggest dropping SCRAM-SHA-1 and focusing solely on SCRAM-SHA-256.
Specifying both seems like a recipie for poor interop, and I don't see a
significant use-case for having both.

I'm also curious, has anyone implemented this?  Does any HTTP clients,
especially browsers, plan to implement this?

Thanks,
/Simon

--=-=-=
Content-Type: application/pgp-signature; name="signature.asc"

-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1

iQEcBAEBCAAGBQJWLjNrAAoJEIYLf7sy+BGddMkH/R2/2r7BCnHAR49CnnAFUDiM
TfvCLSMzDJOgEwAkD7iQIGqdTysDL6ZTshDSOtnGLt8bXRWkQJMNXWsf8QAETwGu
tizzjgSorFVIC/BQRaFETNyfUxuxhAm7c45XC7rONAdIX4Vu3D2qOqVk82FoCtSd
3PUQLLzjBHI3Hno5JPm/1w1eTmuLnUpxhwMoTaJBjLY8DbH9n0dU76EMqnymCF28
XZIQ4qXdGNaI+r6nsLEaeOG/3hpbiR44ZbDHXimi/hZkWip5pKWQ+UshS5KcEysj
EwrgJw1l/qp4eXeLxeyJxe/jPMXjpPp8/CUs6PBT2APZLa65F+uz9zfjUdRYA/4=
=N99v
-----END PGP SIGNATURE-----
--=-=-=--

