
From nobody Wed Oct 14 10:41:30 2020
Return-Path: <internet-drafts@ietf.org>
X-Original-To: emu@ietf.org
Delivered-To: emu@ietfa.amsl.com
Received: from ietfa.amsl.com (localhost [IPv6:::1]) by ietfa.amsl.com (Postfix) with ESMTP id 2B2CF3A0A13; Wed, 14 Oct 2020 10:41:29 -0700 (PDT)
MIME-Version: 1.0
Content-Type: text/plain; charset="utf-8"
Content-Transfer-Encoding: 8bit
From: internet-drafts@ietf.org
To: <i-d-announce@ietf.org>
Cc: emu@ietf.org
X-Test-IDTracker: no
X-IETF-IDTracker: 7.20.0
Auto-Submitted: auto-generated
Precedence: bulk
Reply-To: emu@ietf.org
Message-ID: <160269728910.12450.1037477820698723012@ietfa.amsl.com>
Date: Wed, 14 Oct 2020 10:41:29 -0700
Archived-At: <https://mailarchive.ietf.org/arch/msg/emu/07Uvjk0LRkcHKqbDTtQMR9TInEE>
Subject: [Emu] I-D Action: draft-ietf-emu-eap-tls13-11.txt
X-BeenThere: emu@ietf.org
X-Mailman-Version: 2.1.29
List-Id: "EAP Methods Update \(EMU\)" <emu.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/emu>, <mailto:emu-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/emu/>
List-Post: <mailto:emu@ietf.org>
List-Help: <mailto:emu-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/emu>, <mailto:emu-request@ietf.org?subject=subscribe>
X-List-Received-Date: Wed, 14 Oct 2020 17:41:29 -0000

A New Internet-Draft is available from the on-line Internet-Drafts directories.
This draft is a work item of the EAP Method Update WG of the IETF.

        Title           : Using EAP-TLS with TLS 1.3
        Authors         : John PreuĂ Mattsson
                          Mohit Sethi
	Filename        : draft-ietf-emu-eap-tls13-11.txt
	Pages           : 30
	Date            : 2020-10-14

Abstract:
   This document specifies the use of EAP-TLS with TLS 1.3 while
   remaining backwards compatible with existing implementations of EAP-
   TLS.  TLS 1.3 provides significantly improved security, privacy, and
   reduced latency when compared to earlier versions of TLS.  EAP-TLS
   with TLS 1.3 further improves security and privacy by mandating use
   of privacy and revocation checking.  This document also provides
   guidance on authorization and resumption for EAP-TLS in general
   (regardless of the underlying TLS version used).  This document
   updates RFC 5216.


The IETF datatracker status page for this draft is:
https://datatracker.ietf.org/doc/draft-ietf-emu-eap-tls13/

There are also htmlized versions available at:
https://tools.ietf.org/html/draft-ietf-emu-eap-tls13-11
https://datatracker.ietf.org/doc/html/draft-ietf-emu-eap-tls13-11

A diff from the previous version is available at:
https://www.ietf.org/rfcdiff?url2=draft-ietf-emu-eap-tls13-11


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 Wed Oct 14 11:01:14 2020
Return-Path: <mohit.m.sethi@ericsson.com>
X-Original-To: emu@ietfa.amsl.com
Delivered-To: emu@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 062B03A0FA8 for <emu@ietfa.amsl.com>; Wed, 14 Oct 2020 11:01:13 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -3.514
X-Spam-Level: 
X-Spam-Status: No, score=-3.514 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIMWL_WL_HIGH=-1.2, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, DKIM_VALID_EF=-0.1, NICE_REPLY_A=-0.213, RCVD_IN_MSPIKE_H2=-0.001, SPF_PASS=-0.001, URIBL_BLOCKED=0.001] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (1024-bit key) header.d=ericsson.com
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 lLkBcmESmas8 for <emu@ietfa.amsl.com>; Wed, 14 Oct 2020 11:01:11 -0700 (PDT)
Received: from EUR03-VE1-obe.outbound.protection.outlook.com (mail-eopbgr50067.outbound.protection.outlook.com [40.107.5.67]) (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 DD3393A0D40 for <emu@ietf.org>; Wed, 14 Oct 2020 11:01:10 -0700 (PDT)
ARC-Seal: i=1; a=rsa-sha256; s=arcselector9901; d=microsoft.com; cv=none; b=R7E3iaDUjFRqndnLh9MorXupd9Jiuf1ApPi3eBOYV8umi5ufmBD5uYpbzvDfp0n10ryoCtL2Hz84OuPang7wEXjmzgeAyCCZKyUjxEC/bPP97LCCSbFGLxtx3rFRqLJSs6YwPFz7xZXIYoCPcGbFyCNGDxDNOCIUlSVkcO9WbOXInabk100vmXDpR7lwpWH+GtnXkcmKEj1r+wPgbfqSAYRqerCDJxUN5B85OMXuWmQ+t3Y9PVt/NeUC+gNtek1E7UNa4/B7wnzMv+3C59dZw3tzv88/NWg8TfItUTtGvVZ0END8riDfV74XT+z4B0F1aoODHMMo1ifCMY3AXfqS9A==
ARC-Message-Signature: i=1; a=rsa-sha256; c=relaxed/relaxed; d=microsoft.com;  s=arcselector9901; h=From:Date:Subject:Message-ID:Content-Type:MIME-Version:X-MS-Exchange-SenderADCheck; bh=ImyDMORS3dxKUOZzYsuLT5XcCs9Ua2X3QJvuUDYV7tk=; b=Teu94OcN0iyFrEfljzVzsPJMW5OXH7keUUXjwzv0fkjZuClWlJyHvuTtcFfu8dhvj/ATIcDj279CUunNeUj+C1g3ieTsuMf/MFuXftladDoUMJbdt9xz0Mi1pVF6IyftnvZ66ysolrvJaSA8/DmNXxx9hgvwD1YufCBLL55vdJS+QhV6MU289MXtPhursS42FlEfZQHGAoe8PEyD1q2DBbsNxw/pzAvcYW7XxY1W63nlql6edJhLtfDU/CNZB4AOrcc3ikLIzN8AsFjfNKjZH0K67Hafkz4EFdi0VSAv0Gto6kAYO8oIcMsOj2JS2wWFI0hR57no55Cv/OMEDXyX9w==
ARC-Authentication-Results: i=1; mx.microsoft.com 1; spf=pass smtp.mailfrom=ericsson.com; dmarc=pass action=none header.from=ericsson.com; dkim=pass header.d=ericsson.com; arc=none
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=ericsson.com; s=selector1; h=From:Date:Subject:Message-ID:Content-Type:MIME-Version:X-MS-Exchange-SenderADCheck; bh=ImyDMORS3dxKUOZzYsuLT5XcCs9Ua2X3QJvuUDYV7tk=; b=BKK2iG/xS3Ad6nyo+mt9vjl07J3yhFKpiuarQCRxCmIhejXMKRZza0P1NVl2Y0obQDd9QQ95NLaJDIvoccUY+InO5VHlzuf0aylVkK0agedpk5JgaS1zp2aw59FKGE/Q+hzwFxkinMuD5oL5S1QC71nODbl+3hAiAjYSsZtWMT4=
Received: from HE1PR07MB3209.eurprd07.prod.outlook.com (2603:10a6:7:32::14) by HE1PR0701MB2090.eurprd07.prod.outlook.com (2603:10a6:3:2b::22) with Microsoft SMTP Server (version=TLS1_2, cipher=TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384) id 15.20.3477.11; Wed, 14 Oct 2020 18:01:08 +0000
Received: from HE1PR07MB3209.eurprd07.prod.outlook.com ([fe80::1550:2d88:a5be:95ca]) by HE1PR07MB3209.eurprd07.prod.outlook.com ([fe80::1550:2d88:a5be:95ca%6]) with mapi id 15.20.3477.020; Wed, 14 Oct 2020 18:01:08 +0000
From: Mohit Sethi M <mohit.m.sethi@ericsson.com>
To: "emu@ietf.org" <emu@ietf.org>
Thread-Topic: [Emu] I-D Action: draft-ietf-emu-eap-tls13-11.txt
Thread-Index: AQHWolP9NXXhHncCU0GTakdqjKveNQ==
Date: Wed, 14 Oct 2020 18:01:08 +0000
Message-ID: <55be6146-248f-e139-e9c1-77317c473e5c@ericsson.com>
References: <160269728910.12450.1037477820698723012@ietfa.amsl.com>
In-Reply-To: <160269728910.12450.1037477820698723012@ietfa.amsl.com>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
user-agent: Mozilla/5.0 (X11; Linux x86_64; rv:68.0) Gecko/20100101 Thunderbird/68.10.0
authentication-results: ietf.org; dkim=none (message not signed) header.d=none;ietf.org; dmarc=none action=none header.from=ericsson.com;
x-originating-ip: [87.93.142.12]
x-ms-publictraffictype: Email
x-ms-office365-filtering-correlation-id: 6fac3d27-0d05-443f-d5ba-08d8706b20a8
x-ms-traffictypediagnostic: HE1PR0701MB2090:
x-microsoft-antispam-prvs: <HE1PR0701MB2090F583A6E5E81217EFE483D0050@HE1PR0701MB2090.eurprd07.prod.outlook.com>
x-ms-oob-tlc-oobclassifiers: OLM:8273;
x-ms-exchange-senderadcheck: 1
x-microsoft-antispam: BCL:0;
x-microsoft-antispam-message-info: IQaKAJ7JgBp7XiCZoB+cZux56BBHExSruNXINluWqEzjEVm8jH3fS6FuhXorrKC3khAkAUME6XJPS0UYYKaH4JGszAANdar+46Gc+E6SawDfs7pQ8agKJSFHMzXZ9oavPNoays4oP651585be8EJLVNdnfJoqz32Q8m3W/3kH4wrzBbSkL0cWAnLe9GJNrVRiEBspEFPyI3DJjyeuvRVlgmuBk1yC7cw47JU5FvxK1j5lT4UvdNElBFrqp1NqspJsOCERS6IxCNnYnFHeJFqhO9XmrDPeAnQ7W3ecSW+QaUiR1mwAH0jg3hPTmzYMmYBjRdkGwNxaNj5SEFklrDDlYf2QgxPKrrzofzg+FHdA6fh7KQTOPBCNjPhftwQjX4LypR7+pLV+o9pu164sB/5irAj11gy5brRrJD9vTvSOYIkDJcw6tQb70zC4BvRZwDm4VfrzM1BLF5xib57dUc0Rw==
x-forefront-antispam-report: CIP:255.255.255.255; CTRY:; LANG:en; SCL:1; SRV:;  IPV:NLI; SFV:NSPM; H:HE1PR07MB3209.eurprd07.prod.outlook.com; PTR:; CAT:NONE;  SFS:(4636009)(396003)(346002)(39860400002)(376002)(366004)(136003)(53546011)(966005)(64756008)(66446008)(36756003)(66574015)(83080400001)(6486002)(31686004)(4001150100001)(26005)(83380400001)(478600001)(2906002)(86362001)(2616005)(66556008)(6512007)(76116006)(316002)(66476007)(66946007)(186003)(8936002)(6506007)(31696002)(71200400001)(8676002)(6916009)(5660300002)(43740500002); DIR:OUT; SFP:1101; 
x-ms-exchange-antispam-messagedata: ZduA0jWDcH96RBkz+RtDKoEb2dWeIAUeTieE5BC1HvkFIfp5I/Rd1o0vLTCxJnS7thbDVtDSbnMaKl6qJE801bJaDmVd2mmuoqd3UrW5PSwdClgrQJE8yUQWoSmnBg6abjOEv6FBugROB5Y7TlTpjO5VHp5vlW6BwL7zMhyZLe4qZMyX/vxDCZ0MkQQxXrghd0hxJ18IYHBalGrft4LaN/6JKoQDGYWEdqW28xUsKnUVaQzD76AkNfcB9kFRBGiAK5YV8vO7TPXh0OT0Ia5hn2NDJTqZxXjfv10WQDEri4NxE6lW4xMABlkGoLct7K0yGL6WtH3fz/lcDfESr+60nNnae2BkxWZj9sI9KbL5AuNW95ND038gqUIfPUHqGkPdmwikOR+huCkcZjTZ4QsCecPAt357tVc8doIoYJvJXWN2Ar1JuCqMNbWaEkkjKy47wfOtfarb4K/zM7R0ZPMGcCeeAIOSxSRV50yUgEhfqE4eWvmmEisnAV37rP6xfQTDVIzW3wFPhhRV8260uG69xOXq5aRmrRH2ycqwA0dmkYA8VcGAPeeRfEBZkz7aslhGe2Q1KYcZpEz9M75wmRRrZVA9p70gIzsqYItuQWUAw6kKbrF3bEuqXyC9DOGUxfcz3WzdAA5Iv2TypXUFUi99mQ==
x-ms-exchange-transport-forked: True
Content-Type: text/plain; charset="utf-8"
Content-ID: <A5268DE3697EE244BE49CA8AF43DAB56@eurprd07.prod.outlook.com>
Content-Transfer-Encoding: base64
MIME-Version: 1.0
X-OriginatorOrg: ericsson.com
X-MS-Exchange-CrossTenant-AuthAs: Internal
X-MS-Exchange-CrossTenant-AuthSource: HE1PR07MB3209.eurprd07.prod.outlook.com
X-MS-Exchange-CrossTenant-Network-Message-Id: 6fac3d27-0d05-443f-d5ba-08d8706b20a8
X-MS-Exchange-CrossTenant-originalarrivaltime: 14 Oct 2020 18:01:08.3013 (UTC)
X-MS-Exchange-CrossTenant-fromentityheader: Hosted
X-MS-Exchange-CrossTenant-id: 92e84ceb-fbfd-47ab-be52-080c6b87953f
X-MS-Exchange-CrossTenant-mailboxtype: HOSTED
X-MS-Exchange-CrossTenant-userprincipalname: HxqTgzySXqY1r8lp2fatiPCwktJM6+/kqfrvw1P/9JQzrfaLH4kmyGCLNnx9cuw5UstBSMOoIco/KCpyCRG+U/8WEvBzmazQuJTFkdTOqTU=
X-MS-Exchange-Transport-CrossTenantHeadersStamped: HE1PR0701MB2090
Archived-At: <https://mailarchive.ietf.org/arch/msg/emu/81_cyCWBvMoI-0867guBl0cu_ZA>
Subject: Re: [Emu] I-D Action: draft-ietf-emu-eap-tls13-11.txt
X-BeenThere: emu@ietf.org
X-Mailman-Version: 2.1.29
Precedence: list
List-Id: "EAP Methods Update \(EMU\)" <emu.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/emu>, <mailto:emu-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/emu/>
List-Post: <mailto:emu@ietf.org>
List-Help: <mailto:emu-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/emu>, <mailto:emu-request@ietf.org?subject=subscribe>
X-List-Received-Date: Wed, 14 Oct 2020 18:01:13 -0000

RGVhciBhbGwsDQoNClRoaXMgdmVyc2lvbiBpbmNsdWRlcyBhZGRpdGlvbmFsIGNsYXJpZmljYXRp
b25zIG9uIHJlc3VtcHRpb24gc3VnZ2VzdGVkIA0KYnkgVGVycnkgQnVydG9uLiBCYXNlZCBvbiB0
aGUgbWFpbGluZyBsaXN0IGRpc2N1c3Npb24sIHdlIHN0aWxsIHVzZSANCjEtYnl0ZSBvZiBlbmNy
eXB0ZWQgYXBwbGljYXRpb24gZGF0YSBhcyB0aGUgY29tbWl0bWVudCBtZXNzYWdlOiANCmh0dHBz
Oi8vbWFpbGFyY2hpdmUuaWV0Zi5vcmcvYXJjaC9tc2cvZW11LzZmMzZVVFN5c0pfeHpHZGtPdEM0
VEROVFpiSS8uDQoNCi0tTW9oaXQNCg0KT24gMTAvMTQvMjAgODo0MSBQTSwgaW50ZXJuZXQtZHJh
ZnRzQGlldGYub3JnIHdyb3RlOg0KPiBBIE5ldyBJbnRlcm5ldC1EcmFmdCBpcyBhdmFpbGFibGUg
ZnJvbSB0aGUgb24tbGluZSBJbnRlcm5ldC1EcmFmdHMgZGlyZWN0b3JpZXMuDQo+IFRoaXMgZHJh
ZnQgaXMgYSB3b3JrIGl0ZW0gb2YgdGhlIEVBUCBNZXRob2QgVXBkYXRlIFdHIG9mIHRoZSBJRVRG
Lg0KPg0KPiAgICAgICAgICBUaXRsZSAgICAgICAgICAgOiBVc2luZyBFQVAtVExTIHdpdGggVExT
IDEuMw0KPiAgICAgICAgICBBdXRob3JzICAgICAgICAgOiBKb2huIFByZXXDnyBNYXR0c3Nvbg0K
PiAgICAgICAgICAgICAgICAgICAgICAgICAgICBNb2hpdCBTZXRoaQ0KPiAJRmlsZW5hbWUgICAg
ICAgIDogZHJhZnQtaWV0Zi1lbXUtZWFwLXRsczEzLTExLnR4dA0KPiAJUGFnZXMgICAgICAgICAg
IDogMzANCj4gCURhdGUgICAgICAgICAgICA6IDIwMjAtMTAtMTQNCj4NCj4gQWJzdHJhY3Q6DQo+
ICAgICBUaGlzIGRvY3VtZW50IHNwZWNpZmllcyB0aGUgdXNlIG9mIEVBUC1UTFMgd2l0aCBUTFMg
MS4zIHdoaWxlDQo+ICAgICByZW1haW5pbmcgYmFja3dhcmRzIGNvbXBhdGlibGUgd2l0aCBleGlz
dGluZyBpbXBsZW1lbnRhdGlvbnMgb2YgRUFQLQ0KPiAgICAgVExTLiAgVExTIDEuMyBwcm92aWRl
cyBzaWduaWZpY2FudGx5IGltcHJvdmVkIHNlY3VyaXR5LCBwcml2YWN5LCBhbmQNCj4gICAgIHJl
ZHVjZWQgbGF0ZW5jeSB3aGVuIGNvbXBhcmVkIHRvIGVhcmxpZXIgdmVyc2lvbnMgb2YgVExTLiAg
RUFQLVRMUw0KPiAgICAgd2l0aCBUTFMgMS4zIGZ1cnRoZXIgaW1wcm92ZXMgc2VjdXJpdHkgYW5k
IHByaXZhY3kgYnkgbWFuZGF0aW5nIHVzZQ0KPiAgICAgb2YgcHJpdmFjeSBhbmQgcmV2b2NhdGlv
biBjaGVja2luZy4gIFRoaXMgZG9jdW1lbnQgYWxzbyBwcm92aWRlcw0KPiAgICAgZ3VpZGFuY2Ug
b24gYXV0aG9yaXphdGlvbiBhbmQgcmVzdW1wdGlvbiBmb3IgRUFQLVRMUyBpbiBnZW5lcmFsDQo+
ICAgICAocmVnYXJkbGVzcyBvZiB0aGUgdW5kZXJseWluZyBUTFMgdmVyc2lvbiB1c2VkKS4gIFRo
aXMgZG9jdW1lbnQNCj4gICAgIHVwZGF0ZXMgUkZDIDUyMTYuDQo+DQo+DQo+IFRoZSBJRVRGIGRh
dGF0cmFja2VyIHN0YXR1cyBwYWdlIGZvciB0aGlzIGRyYWZ0IGlzOg0KPiBodHRwczovL2RhdGF0
cmFja2VyLmlldGYub3JnL2RvYy9kcmFmdC1pZXRmLWVtdS1lYXAtdGxzMTMvDQo+DQo+IFRoZXJl
IGFyZSBhbHNvIGh0bWxpemVkIHZlcnNpb25zIGF2YWlsYWJsZSBhdDoNCj4gaHR0cHM6Ly90b29s
cy5pZXRmLm9yZy9odG1sL2RyYWZ0LWlldGYtZW11LWVhcC10bHMxMy0xMQ0KPiBodHRwczovL2Rh
dGF0cmFja2VyLmlldGYub3JnL2RvYy9odG1sL2RyYWZ0LWlldGYtZW11LWVhcC10bHMxMy0xMQ0K
Pg0KPiBBIGRpZmYgZnJvbSB0aGUgcHJldmlvdXMgdmVyc2lvbiBpcyBhdmFpbGFibGUgYXQ6DQo+
IGh0dHBzOi8vd3d3LmlldGYub3JnL3JmY2RpZmY/dXJsMj1kcmFmdC1pZXRmLWVtdS1lYXAtdGxz
MTMtMTENCj4NCj4NCj4gUGxlYXNlIG5vdGUgdGhhdCBpdCBtYXkgdGFrZSBhIGNvdXBsZSBvZiBt
aW51dGVzIGZyb20gdGhlIHRpbWUgb2Ygc3VibWlzc2lvbg0KPiB1bnRpbCB0aGUgaHRtbGl6ZWQg
dmVyc2lvbiBhbmQgZGlmZiBhcmUgYXZhaWxhYmxlIGF0IHRvb2xzLmlldGYub3JnLg0KPg0KPiBJ
bnRlcm5ldC1EcmFmdHMgYXJlIGFsc28gYXZhaWxhYmxlIGJ5IGFub255bW91cyBGVFAgYXQ6DQo+
IGZ0cDovL2Z0cC5pZXRmLm9yZy9pbnRlcm5ldC1kcmFmdHMvDQo+DQo+DQo+IF9fX19fX19fX19f
X19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fDQo+IEVtdSBtYWlsaW5nIGxpc3QN
Cj4gRW11QGlldGYub3JnDQo+IGh0dHBzOi8vd3d3LmlldGYub3JnL21haWxtYW4vbGlzdGluZm8v
ZW11DQo=


From nobody Wed Oct 14 12:30:57 2020
Return-Path: <rdd@cert.org>
X-Original-To: emu@ietfa.amsl.com
Delivered-To: emu@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id C1F343A0FF2 for <emu@ietfa.amsl.com>; Wed, 14 Oct 2020 12:30:55 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.099
X-Spam-Level: 
X-Spam-Status: No, score=-2.099 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, DKIM_VALID_EF=-0.1, SPF_HELO_NONE=0.001, SPF_PASS=-0.001, URIBL_BLOCKED=0.001] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (1024-bit key) header.d=cert.org
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 AYhyIQY-GFtM for <emu@ietfa.amsl.com>; Wed, 14 Oct 2020 12:30:54 -0700 (PDT)
Received: from taper.sei.cmu.edu (taper.sei.cmu.edu [147.72.252.16]) (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 78BF93A0FEB for <emu@ietf.org>; Wed, 14 Oct 2020 12:30:54 -0700 (PDT)
Received: from korb.sei.cmu.edu (korb.sei.cmu.edu [10.64.21.30]) by taper.sei.cmu.edu (8.14.7/8.14.7) with ESMTP id 09EJUrUV031665 for <emu@ietf.org>; Wed, 14 Oct 2020 15:30:53 -0400
DKIM-Filter: OpenDKIM Filter v2.11.0 taper.sei.cmu.edu 09EJUrUV031665
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=cert.org; s=yc2bmwvrj62m; t=1602703853; bh=vg5k4OLjupcVS5gI0/xKtOZZCgDgkrIJ7zTVRYmR3Ck=; h=From:To:Subject:Date:From; b=IGEoCWqerbS6wV7QX2/MkURqhQk1ZN2BhEmGkin1AxXe7L91VwVKCEuBhBaLAOklK JPP0Sd1Ikf4MFo+cq9CURM2El6Q4+Lh86pu3oVABo6RcA84T6rsIbdGatCpxkoZAXm K39UP/dxyXyw8C7IDbSYOmK8ucHgTLYrfVZ6Y77k=
Received: from MURIEL.ad.sei.cmu.edu (muriel.ad.sei.cmu.edu [147.72.252.47]) by korb.sei.cmu.edu (8.14.7/8.14.7) with ESMTP id 09EJUpVs009630 for <emu@ietf.org>; Wed, 14 Oct 2020 15:30:51 -0400
Received: from MORRIS.ad.sei.cmu.edu (147.72.252.46) by MURIEL.ad.sei.cmu.edu (147.72.252.47) with Microsoft SMTP Server (version=TLS1_2, cipher=TLS_ECDHE_RSA_WITH_AES_128_GCM_SHA256) id 15.1.1979.3; Wed, 14 Oct 2020 15:30:51 -0400
Received: from MORRIS.ad.sei.cmu.edu ([fe80::555b:9498:552e:d1bb]) by MORRIS.ad.sei.cmu.edu ([fe80::555b:9498:552e:d1bb%13]) with mapi id 15.01.1979.003; Wed, 14 Oct 2020 15:30:51 -0400
From: Roman Danyliw <rdd@cert.org>
To: "emu@ietf.org" <emu@ietf.org>
Thread-Topic: AD Review of draft-ietf-emu-eaptlscert-05
Thread-Index: AdaiYCbKlD7KN0eKSBqq6vltBDWi5w==
Date: Wed, 14 Oct 2020 19:30:50 +0000
Message-ID: <3ea21ac7a0134aed95b56e64b6e104be@cert.org>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
x-originating-ip: [10.64.203.52]
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: quoted-printable
MIME-Version: 1.0
Archived-At: <https://mailarchive.ietf.org/arch/msg/emu/ABvCFmTeDioJrHy8g-OORJyIIEw>
Subject: [Emu] AD Review of draft-ietf-emu-eaptlscert-05
X-BeenThere: emu@ietf.org
X-Mailman-Version: 2.1.29
Precedence: list
List-Id: "EAP Methods Update \(EMU\)" <emu.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/emu>, <mailto:emu-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/emu/>
List-Post: <mailto:emu@ietf.org>
List-Help: <mailto:emu-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/emu>, <mailto:emu-request@ietf.org?subject=subscribe>
X-List-Received-Date: Wed, 14 Oct 2020 19:30:56 -0000

Hello!

I performed an AD review of draft-ietf-emu-eaptlscert-05.  This document is=
 in good shape.  Thanks for writing this practical guidance for operators a=
nd implementers.  I have minor feedback below that can be addressed concurr=
ently with IETF LC.

Section 3.  Editorial.  s/A certificate chain .... can have 2 - 6 intermedi=
ate certificates/A certificate chain ... can commonly have 2 - 6 intermedia=
te certificates/

Section 4.1.1.  Editorial. s/1st/first/

Section 4.2.2.  s/more strict/stricter/

Section 4.3.  Editorial. s/Another second reason/Another reason/

Section 4.3.  Per "unlimited communication from an unauthenticated device a=
s EAP could otherwise be use for bulk data transfer" doesn't parse - ("... =
devices as EAP ...", also, is it that an unauthenticated devices can use re=
sources?)

Section 4.3.  Would 100 round trips ensure that certificates chains as ther=
e are currently deployed (in size) do not get dropped?  I'm inquiring about=
 the basis of the 100 round-trip threshold.

Regards,
Roman


From nobody Wed Oct 14 12:39:19 2020
Return-Path: <iesg-secretary@ietf.org>
X-Original-To: emu@ietf.org
Delivered-To: emu@ietfa.amsl.com
Received: from ietfa.amsl.com (localhost [IPv6:::1]) by ietfa.amsl.com (Postfix) with ESMTP id 2457F3A0FF5; Wed, 14 Oct 2020 12:39:18 -0700 (PDT)
MIME-Version: 1.0
Content-Type: text/plain; charset="utf-8"
Content-Transfer-Encoding: 7bit
From: The IESG <iesg-secretary@ietf.org>
To: "IETF-Announce" <ietf-announce@ietf.org>
X-Test-IDTracker: no
X-IETF-IDTracker: 7.20.0
Auto-Submitted: auto-generated
Precedence: bulk
CC: draft-ietf-emu-eaptlscert@ietf.org, joe@salowey.net, rdd@cert.org, Joseph Salowey <joe@salowey.net>, emu-chairs@ietf.org, emu@ietf.org
Reply-To: last-call@ietf.org
Sender: <iesg-secretary@ietf.org>
MIME-Version: 1.0
Content-Type: text/plain; charset="utf-8"
Content-Transfer-Encoding: 7bit
Message-ID: <160270435768.16197.8909056833783118201@ietfa.amsl.com>
Date: Wed, 14 Oct 2020 12:39:18 -0700
Archived-At: <https://mailarchive.ietf.org/arch/msg/emu/1VHNM2ZpXx15sz03Yqd6UIlzXps>
Subject: [Emu] Last Call: <draft-ietf-emu-eaptlscert-05.txt> (Handling Large Certificates and Long Certificate Chains in TLS-based EAP Methods) to Informational RFC
X-BeenThere: emu@ietf.org
X-Mailman-Version: 2.1.29
List-Id: "EAP Methods Update \(EMU\)" <emu.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/emu>, <mailto:emu-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/emu/>
List-Post: <mailto:emu@ietf.org>
List-Help: <mailto:emu-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/emu>, <mailto:emu-request@ietf.org?subject=subscribe>
X-List-Received-Date: Wed, 14 Oct 2020 19:39:18 -0000

The IESG has received a request from the EAP Method Update WG (emu) to
consider the following document: - 'Handling Large Certificates and Long
Certificate Chains in TLS-based
   EAP Methods'
  <draft-ietf-emu-eaptlscert-05.txt> as Informational RFC

The IESG plans to make a decision in the next few weeks, and solicits final
comments on this action. Please send substantive comments to the
last-call@ietf.org mailing lists by 2020-10-28. Exceptionally, comments may
be sent to iesg@ietf.org instead. In either case, please retain the beginning
of the Subject line to allow automated sorting.

Abstract


   EAP-TLS and other TLS-based EAP methods are widely deployed and used
   for network access authentication.  Large certificates and long
   certificate chains combined with authenticators that drop an EAP
   session after only 40 - 50 round-trips is a major deployment problem.
   This document looks at the this problem in detail and describes the
   potential solutions available.




The file can be obtained via
https://datatracker.ietf.org/doc/draft-ietf-emu-eaptlscert/



No IPR declarations have been submitted directly on this I-D.






From nobody Thu Oct 15 06:51:42 2020
Return-Path: <iesg-secretary@ietf.org>
X-Original-To: emu@ietf.org
Delivered-To: emu@ietfa.amsl.com
Received: from ietfa.amsl.com (localhost [IPv6:::1]) by ietfa.amsl.com (Postfix) with ESMTP id AAC3B3A0AB0; Thu, 15 Oct 2020 06:51:40 -0700 (PDT)
MIME-Version: 1.0
Content-Type: text/plain; charset="utf-8"
Content-Transfer-Encoding: 7bit
From: The IESG <iesg-secretary@ietf.org>
To: "IETF-Announce" <ietf-announce@ietf.org>
X-Test-IDTracker: no
X-IETF-IDTracker: 7.20.0
Auto-Submitted: auto-generated
Precedence: bulk
CC: emu@ietf.org, joe@salowey.net, draft-ietf-emu-eap-tls13@ietf.org, emu-chairs@ietf.org, rdd@cert.org, Joseph Salowey <joe@salowey.net>
Reply-To: last-call@ietf.org
Sender: <iesg-secretary@ietf.org>
MIME-Version: 1.0
Content-Type: text/plain; charset="utf-8"
Content-Transfer-Encoding: 7bit
Message-ID: <160276990012.10807.6524962005496387710@ietfa.amsl.com>
Date: Thu, 15 Oct 2020 06:51:40 -0700
Archived-At: <https://mailarchive.ietf.org/arch/msg/emu/bvxzQcKz_VUQkTwfojcR7nIR5AI>
Subject: [Emu] Last Call: <draft-ietf-emu-eap-tls13-11.txt> (Using EAP-TLS with TLS 1.3) to Proposed Standard
X-BeenThere: emu@ietf.org
X-Mailman-Version: 2.1.29
List-Id: "EAP Methods Update \(EMU\)" <emu.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/emu>, <mailto:emu-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/emu/>
List-Post: <mailto:emu@ietf.org>
List-Help: <mailto:emu-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/emu>, <mailto:emu-request@ietf.org?subject=subscribe>
X-List-Received-Date: Thu, 15 Oct 2020 13:51:41 -0000

The IESG has received a request from the EAP Method Update WG (emu) to
consider the following document: - 'Using EAP-TLS with TLS 1.3'
  <draft-ietf-emu-eap-tls13-11.txt> as Proposed Standard

The IESG plans to make a decision in the next few weeks, and solicits final
comments on this action. Please send substantive comments to the
last-call@ietf.org mailing lists by 2020-10-29. Exceptionally, comments may
be sent to iesg@ietf.org instead. In either case, please retain the beginning
of the Subject line to allow automated sorting.

Abstract


   This document specifies the use of EAP-TLS with TLS 1.3 while
   remaining backwards compatible with existing implementations of EAP-
   TLS.  TLS 1.3 provides significantly improved security, privacy, and
   reduced latency when compared to earlier versions of TLS.  EAP-TLS
   with TLS 1.3 further improves security and privacy by mandating use
   of privacy and revocation checking.  This document also provides
   guidance on authorization and resumption for EAP-TLS in general
   (regardless of the underlying TLS version used).  This document
   updates RFC 5216.




The file can be obtained via
https://datatracker.ietf.org/doc/draft-ietf-emu-eap-tls13/



No IPR declarations have been submitted directly on this I-D.






From nobody Wed Oct 21 01:55:28 2020
Return-Path: <Hannes.Tschofenig@arm.com>
X-Original-To: emu@ietfa.amsl.com
Delivered-To: emu@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id BB0273A13C5 for <emu@ietfa.amsl.com>; Wed, 21 Oct 2020 01:55:25 -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, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, HTML_MESSAGE=0.001, RCVD_IN_MSPIKE_H2=-0.001, SPF_PASS=-0.001, UNPARSEABLE_RELAY=0.001] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (1024-bit key) header.d=armh.onmicrosoft.com header.b=uDGIlmT8; dkim=pass (1024-bit key) header.d=armh.onmicrosoft.com header.b=uDGIlmT8
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 lLO0SPi5CtXm for <emu@ietfa.amsl.com>; Wed, 21 Oct 2020 01:55:23 -0700 (PDT)
Received: from EUR05-DB8-obe.outbound.protection.outlook.com (mail-db8eur05on2054.outbound.protection.outlook.com [40.107.20.54]) (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 74AD53A13C6 for <emu@ietf.org>; Wed, 21 Oct 2020 01:55:23 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=armh.onmicrosoft.com;  s=selector2-armh-onmicrosoft-com; h=From:Date:Subject:Message-ID:Content-Type:MIME-Version:X-MS-Exchange-SenderADCheck; bh=ssz/FuEx6uCplTtmS76Iq5FfuFXDzuziAhw8lvBHk0k=; b=uDGIlmT80xiVcRhzBVh2w9xf7aSzuHBpVNt1CJLhM6YiD5nt3KQff7AUeKJ7e5npdIsWFXj+pHzl9kKc6xm2L85c+h1OAJbDslMHp6M7PA8gA7IeaiRvczXMIQf/Gwplw6j+uGKrz4wn7mPczPFUGAbK9WCZHDpmBYVnpppPjs0=
Received: from AM6PR08CA0029.eurprd08.prod.outlook.com (2603:10a6:20b:c0::17) by AM0PR08MB3890.eurprd08.prod.outlook.com (2603:10a6:208:10a::31) with Microsoft SMTP Server (version=TLS1_2, cipher=TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384) id 15.20.3477.21; Wed, 21 Oct 2020 08:55:20 +0000
Received: from AM5EUR03FT035.eop-EUR03.prod.protection.outlook.com (2603:10a6:20b:c0:cafe::87) by AM6PR08CA0029.outlook.office365.com (2603:10a6:20b:c0::17) with Microsoft SMTP Server (version=TLS1_2, cipher=TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384) id 15.20.3477.22 via Frontend Transport; Wed, 21 Oct 2020 08:55:20 +0000
X-MS-Exchange-Authentication-Results: spf=pass (sender IP is 63.35.35.123) smtp.mailfrom=arm.com; ietf.org; dkim=pass (signature was verified) header.d=armh.onmicrosoft.com;ietf.org; dmarc=pass action=none header.from=arm.com;
Received-SPF: Pass (protection.outlook.com: domain of arm.com designates 63.35.35.123 as permitted sender) receiver=protection.outlook.com; client-ip=63.35.35.123; helo=64aa7808-outbound-1.mta.getcheckrecipient.com;
Received: from 64aa7808-outbound-1.mta.getcheckrecipient.com (63.35.35.123) by AM5EUR03FT035.mail.protection.outlook.com (10.152.16.119) with Microsoft SMTP Server (version=TLS1_2, cipher=TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384) id 15.20.3499.18 via Frontend Transport; Wed, 21 Oct 2020 08:55:20 +0000
Received: ("Tessian outbound c579d876a324:v64"); Wed, 21 Oct 2020 08:55:20 +0000
X-CR-MTA-TID: 64aa7808
Received: from 32a186c04972.1 by 64aa7808-outbound-1.mta.getcheckrecipient.com id F10DE5A6-80B9-431D-938F-987B02D4C7FE.1;  Wed, 21 Oct 2020 08:55:15 +0000
Received: from EUR05-VI1-obe.outbound.protection.outlook.com by 64aa7808-outbound-1.mta.getcheckrecipient.com with ESMTPS id 32a186c04972.1 (version=TLSv1.2 cipher=ECDHE-RSA-AES256-GCM-SHA384); Wed, 21 Oct 2020 08:55:15 +0000
ARC-Seal: i=1; a=rsa-sha256; s=arcselector9901; d=microsoft.com; cv=none; b=I5V/BgkBQ4g+d1XAD7+ZezsKx1V2/cAeH8SI1szz7HqrfqBJ8iq1gLyJZzNpXwqBYtyytKymVO4aU+2T0jqXjNQQNb6WEQWA7StIeYgNJccyu/ly6wbX8jgPQmSf7xc3+baDaFIhxGPG0z8Ao/7XCF698NiDYacD5VcQaig0XXt2KmcdsU2fw3ywItFlCYi9gW8AaB2EKHsHBp7Q7F7xQMAz8ubrKXwjACUys5Czfrr2FOTPj4HjCEkOqjpLag8LvxIdZlVN09z5QC2T2FUfILUoLFZYT6fJmaXlRnsxDTvWmDeDQrFHR4Grzydck+nYiGbhpC/yTVSc/idSQyP8/g==
ARC-Message-Signature: i=1; a=rsa-sha256; c=relaxed/relaxed; d=microsoft.com;  s=arcselector9901; h=From:Date:Subject:Message-ID:Content-Type:MIME-Version:X-MS-Exchange-SenderADCheck; bh=ssz/FuEx6uCplTtmS76Iq5FfuFXDzuziAhw8lvBHk0k=; b=KOSH0lZhG28BQrRY/J3n+L8LLsVDyvjmGatrGC1jAMmy6OnXDXoCQ/bwdjgGFScH8+NRPDqeAbuGjK6tjB7xavZwB0jiQ2T9ycm1MBKK648+U9GdZl7nBG8LWo9H9AvlTQIxbeJDXkhxbz6i2LguoLwxHcKsdshV2Lg3PXpvPhakFQt0xO/qyOdds7u3wVRcP7J7r2kHG8z/PsvuiVljSK5vbP5ubxVw/v9RyOCQlXZB2/f1ax5J+mGuxZPB14x8vXI2ni9KB+zh02ogYiFuJFzubihRBHPCEFHfb6WULOPC3xjYRi4x+cTwJL0BhWpUjyfvTd51QocZO3N5EcvyIA==
ARC-Authentication-Results: i=1; mx.microsoft.com 1; spf=pass smtp.mailfrom=arm.com; dmarc=pass action=none header.from=arm.com; dkim=pass header.d=arm.com; arc=none
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=armh.onmicrosoft.com;  s=selector2-armh-onmicrosoft-com; h=From:Date:Subject:Message-ID:Content-Type:MIME-Version:X-MS-Exchange-SenderADCheck; bh=ssz/FuEx6uCplTtmS76Iq5FfuFXDzuziAhw8lvBHk0k=; b=uDGIlmT80xiVcRhzBVh2w9xf7aSzuHBpVNt1CJLhM6YiD5nt3KQff7AUeKJ7e5npdIsWFXj+pHzl9kKc6xm2L85c+h1OAJbDslMHp6M7PA8gA7IeaiRvczXMIQf/Gwplw6j+uGKrz4wn7mPczPFUGAbK9WCZHDpmBYVnpppPjs0=
Received: from AM0PR08MB3716.eurprd08.prod.outlook.com (2603:10a6:208:106::13) by AM8PR08MB5620.eurprd08.prod.outlook.com (2603:10a6:20b:1c6::23) with Microsoft SMTP Server (version=TLS1_2, cipher=TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384) id 15.20.3477.20; Wed, 21 Oct 2020 08:55:14 +0000
Received: from AM0PR08MB3716.eurprd08.prod.outlook.com ([fe80::900e:c64d:a006:4860]) by AM0PR08MB3716.eurprd08.prod.outlook.com ([fe80::900e:c64d:a006:4860%6]) with mapi id 15.20.3455.037; Wed, 21 Oct 2020 08:55:13 +0000
From: Hannes Tschofenig <Hannes.Tschofenig@arm.com>
To: "emu@ietf.org" <emu@ietf.org>
Thread-Topic: draft-ietf-emu-eap-tls13-11
Thread-Index: AdancnFR+BWuksi7Q+KHMh6fjbEB0w==
Date: Wed, 21 Oct 2020 08:55:13 +0000
Message-ID: <AM0PR08MB3716D1CAAC616D85118DEAD7FA1C0@AM0PR08MB3716.eurprd08.prod.outlook.com>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
x-ts-tracking-id: 4F90308E39C51449A142422AB72D9DFF.0
x-checkrecipientchecked: true
Authentication-Results-Original: ietf.org; dkim=none (message not signed) header.d=none;ietf.org; dmarc=none action=none header.from=arm.com;
x-originating-ip: [156.67.196.116]
x-ms-publictraffictype: Email
X-MS-Office365-Filtering-HT: Tenant
X-MS-Office365-Filtering-Correlation-Id: 265ac612-517f-41fa-44e3-08d8759f0a6f
x-ms-traffictypediagnostic: AM8PR08MB5620:|AM0PR08MB3890:
X-Microsoft-Antispam-PRVS: <AM0PR08MB38905FF1B9E63AE56D172F60FA1C0@AM0PR08MB3890.eurprd08.prod.outlook.com>
x-checkrecipientrouted: true
nodisclaimer: true
x-ms-oob-tlc-oobclassifiers: OLM:5516;OLM:10000;
X-MS-Exchange-SenderADCheck: 1
X-Microsoft-Antispam-Untrusted: BCL:0;
X-Microsoft-Antispam-Message-Info-Original: USlTUdNzZcCjycYJy8G7PnIvEUvoglK1d24tdSdgIIacQUKW5ozG06aD4ue2t5sTSMWEmgIHEVKzKEcpREiFPTt5srNsuQfZksF+td2ob/02pXvtIJ5mHLYT0l8fGfzM4zzyVxnTywJonELjY/AQ6PZprHNJQCIglKBV7yLQ4nhnQnt5Svj3yFuRXNbxWETfZGly1LtAGYipUvWKr75k3hDfSosj/CavMIVEdxeL4EagfAbFtXqm+qyCLpJd+4RwmlhVRxyq2+HWmdf+wRUtxOamRBlXsw5DddlrcTi1Q/6sDGnaK9oHWEbUXnwyXD7w8rZBKhk/bhlDzgHzCKrkhA==
X-Forefront-Antispam-Report-Untrusted: CIP:255.255.255.255; CTRY:; LANG:en; SCL:1; SRV:; IPV:NLI; SFV:NSPM; H:AM0PR08MB3716.eurprd08.prod.outlook.com; PTR:; CAT:NONE; SFS:(4636009)(346002)(39860400002)(366004)(396003)(136003)(376002)(66476007)(478600001)(66556008)(71200400001)(316002)(5660300002)(86362001)(8936002)(76116006)(7696005)(9686003)(55016002)(6506007)(66446008)(2906002)(26005)(33656002)(6916009)(52536014)(186003)(64756008)(66946007)(83380400001)(8676002)(4744005); DIR:OUT; SFP:1101; 
x-ms-exchange-antispam-messagedata: 28+EFmrDRnVUkBWup9hgH7eGw2XgDesz0RjYR58z9qjnNoGBO8BHqQ9Bh2Fu7couaOPdTJy3l/1Ccz/sWzw72zMJiwWDitgD83cCBhACjeNYvdbEWFxxI3HMqo0rTiOWBxv+W94NxU93RHlaM4PBL09NmtqIou4bQkl7wRm7VmTiTG05NsQp63STyT0WO1jQbFzYoGHXktILGHNgrYrPnspIiHtt1ylVrtvxpu+cOArvPJyWZE23TNplGevxXl1kYwMi7LI3sr0HXU1MrEIWUXXdvk/Re8A+S/k0hRnDfeEeyExlkOjThYNJGDW7LARRYoavtj3Bqij9upp75QfxGRO5RSYvYhZmmCZBBH3HgqmRnxKUI76VS7MZU9Y+CoWlhhi54S2l7sRihoyhEGfpnkDAe2LDbdd1JtWc07b/fBjEHoqCM8OjINiJVzfo5+leAlVYCNUFjtJj+i7PX1JV0ntd33neBpdiA9jWvGzYiiUI5UeZSD5earMxIan9AyHPsTruRATEpX5Qeaz5ONwxSunDIF87GXZbhdVPfJIXN3kY1uSrvQdM7fMJcWLyFeWH1ZskZVPw/73AmoMwZXYCGc73n144KbqQsuF2qt9NkCyBQ2o+staJAoRomUQxQ3mRPCZeeW75YKWgPIRqPN5DeQ==
x-ms-exchange-transport-forked: True
Content-Type: multipart/alternative; boundary="_000_AM0PR08MB3716D1CAAC616D85118DEAD7FA1C0AM0PR08MB3716eurp_"
MIME-Version: 1.0
X-MS-Exchange-Transport-CrossTenantHeadersStamped: AM8PR08MB5620
Original-Authentication-Results: ietf.org; dkim=none (message not signed) header.d=none;ietf.org; dmarc=none action=none header.from=arm.com;
X-EOPAttributedMessage: 0
X-MS-Exchange-Transport-CrossTenantHeadersStripped: AM5EUR03FT035.eop-EUR03.prod.protection.outlook.com
X-MS-Office365-Filtering-Correlation-Id-Prvs: 8ef69a5a-693a-40ab-857a-08d8759f0653
X-Microsoft-Antispam: BCL:0;
X-Microsoft-Antispam-Message-Info: PIcjIU600kaYz2fHXpXQvKZEEeGfYF7RUv8fXx+Jntl6VzPPGut5uLhpFCVdMT98wYt52U0hzF+R04yJrHt0u0o24Mt6y1G17Xbw97EHygP4+jhrk7nPLLq07XSk3vR4Lz7MLolN+3KsyAL6N3oE7XDBz4NEGjG/PakNYns/v4WsqfXgjlZIht+WAep0u4qLWFymzu7/h/2XxTBRJnbcUD5JVHthT9vQVsh/g9yvr65nXg+dIbr0uzYfFELz/tmeY5ctDNtiTf0iW+KErqsJTZbHuxEHo08Em36h1TthxcDMmy03Mqa4lL/nP4RAxdhrkRhZwd36IyW5fg+G+LaU8jA4r806RVCu2/fd6Z6a0ShF+cQ9OqnyOlsjX47bSnB8aPtciUOm8Dj1l9oc6sRUAQ==
X-Forefront-Antispam-Report: CIP:63.35.35.123; CTRY:IE; LANG:en; SCL:1; SRV:;  IPV:CAL; SFV:NSPM; H:64aa7808-outbound-1.mta.getcheckrecipient.com;  PTR:ec2-63-35-35-123.eu-west-1.compute.amazonaws.com; CAT:NONE; SFS:(4636009)(396003)(376002)(39860400002)(136003)(346002)(46966005)(86362001)(33656002)(316002)(82310400003)(6916009)(186003)(336012)(26005)(5660300002)(36906005)(2906002)(52536014)(70206006)(7696005)(70586007)(83380400001)(82740400003)(47076004)(55016002)(478600001)(9686003)(81166007)(356005)(6506007)(8676002)(8936002); DIR:OUT; SFP:1101; 
X-OriginatorOrg: arm.com
X-MS-Exchange-CrossTenant-OriginalArrivalTime: 21 Oct 2020 08:55:20.7589 (UTC)
X-MS-Exchange-CrossTenant-Network-Message-Id: 265ac612-517f-41fa-44e3-08d8759f0a6f
X-MS-Exchange-CrossTenant-Id: f34e5979-57d9-4aaa-ad4d-b122a662184d
X-MS-Exchange-CrossTenant-OriginalAttributedTenantConnectingIp: TenantId=f34e5979-57d9-4aaa-ad4d-b122a662184d; Ip=[63.35.35.123];  Helo=[64aa7808-outbound-1.mta.getcheckrecipient.com]
X-MS-Exchange-CrossTenant-AuthSource: AM5EUR03FT035.eop-EUR03.prod.protection.outlook.com
X-MS-Exchange-CrossTenant-AuthAs: Anonymous
X-MS-Exchange-CrossTenant-FromEntityHeader: HybridOnPrem
X-MS-Exchange-Transport-CrossTenantHeadersStamped: AM0PR08MB3890
Archived-At: <https://mailarchive.ietf.org/arch/msg/emu/I9f8PAgNW2KjbYUpaFGDLJhrMxM>
Subject: [Emu] draft-ietf-emu-eap-tls13-11
X-BeenThere: emu@ietf.org
X-Mailman-Version: 2.1.29
Precedence: list
List-Id: "EAP Methods Update \(EMU\)" <emu.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/emu>, <mailto:emu-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/emu/>
List-Post: <mailto:emu@ietf.org>
List-Help: <mailto:emu-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/emu>, <mailto:emu-request@ietf.org?subject=subscribe>
X-List-Received-Date: Wed, 21 Oct 2020 08:55:26 -0000

--_000_AM0PR08MB3716D1CAAC616D85118DEAD7FA1C0AM0PR08MB3716eurp_
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: quoted-printable

Hi all,

Roman asked me to look at draft-ietf-emu-eap-tls13-11.

I have carefully read through the document and I will post my reviews in se=
parate emails.
There are still lots of room for improvement.

Ciao
Hannes

IMPORTANT NOTICE: The contents of this email and any attachments are confid=
ential and may also be privileged. If you are not the intended recipient, p=
lease notify the sender immediately and do not disclose the contents to any=
 other person, use it for any purpose, or store or copy the information in =
any medium. Thank you.

--_000_AM0PR08MB3716D1CAAC616D85118DEAD7FA1C0AM0PR08MB3716eurp_
Content-Type: text/html; charset="us-ascii"
Content-Transfer-Encoding: quoted-printable

<html xmlns:v=3D"urn:schemas-microsoft-com:vml" xmlns:o=3D"urn:schemas-micr=
osoft-com:office:office" xmlns:w=3D"urn:schemas-microsoft-com:office:word" =
xmlns:m=3D"http://schemas.microsoft.com/office/2004/12/omml" xmlns=3D"http:=
//www.w3.org/TR/REC-html40">
<head>
<meta http-equiv=3D"Content-Type" content=3D"text/html; charset=3Dus-ascii"=
>
<meta name=3D"Generator" content=3D"Microsoft Word 15 (filtered medium)">
<style><!--
/* Font Definitions */
@font-face
	{font-family:"Cambria Math";
	panose-1:2 4 5 3 5 4 6 3 2 4;}
@font-face
	{font-family:DengXian;
	panose-1:2 1 6 0 3 1 1 1 1 1;}
@font-face
	{font-family:Calibri;
	panose-1:2 15 5 2 2 2 4 3 2 4;}
@font-face
	{font-family:"\@DengXian";
	panose-1:2 1 6 0 3 1 1 1 1 1;}
/* Style Definitions */
p.MsoNormal, li.MsoNormal, div.MsoNormal
	{margin:0in;
	font-size:11.0pt;
	font-family:"Calibri",sans-serif;}
span.EmailStyle17
	{mso-style-type:personal-compose;
	font-family:"Calibri",sans-serif;
	color:windowtext;}
.MsoChpDefault
	{mso-style-type:export-only;
	font-family:"Calibri",sans-serif;}
@page WordSection1
	{size:8.5in 11.0in;
	margin:1.0in 1.0in 1.0in 1.0in;}
div.WordSection1
	{page:WordSection1;}
--></style><!--[if gte mso 9]><xml>
<o:shapedefaults v:ext=3D"edit" spidmax=3D"1026" />
</xml><![endif]--><!--[if gte mso 9]><xml>
<o:shapelayout v:ext=3D"edit">
<o:idmap v:ext=3D"edit" data=3D"1" />
</o:shapelayout></xml><![endif]-->
</head>
<body lang=3D"EN-US" link=3D"#0563C1" vlink=3D"#954F72">
<div class=3D"WordSection1">
<p class=3D"MsoNormal">Hi all, <o:p></o:p></p>
<p class=3D"MsoNormal"><o:p>&nbsp;</o:p></p>
<p class=3D"MsoNormal">Roman asked me to look at draft-ietf-emu-eap-tls13-1=
1. <o:p>
</o:p></p>
<p class=3D"MsoNormal"><o:p>&nbsp;</o:p></p>
<p class=3D"MsoNormal">I have carefully read through the document and I wil=
l post my reviews in separate emails.
<o:p></o:p></p>
<p class=3D"MsoNormal">There are still lots of room for improvement. <o:p><=
/o:p></p>
<p class=3D"MsoNormal"><o:p>&nbsp;</o:p></p>
<p class=3D"MsoNormal">Ciao<o:p></o:p></p>
<p class=3D"MsoNormal">Hannes<o:p></o:p></p>
<p class=3D"MsoNormal"><o:p>&nbsp;</o:p></p>
</div>
IMPORTANT NOTICE: The contents of this email and any attachments are confid=
ential and may also be privileged. If you are not the intended recipient, p=
lease notify the sender immediately and do not disclose the contents to any=
 other person, use it for any purpose,
 or store or copy the information in any medium. Thank you.
</body>
</html>

--_000_AM0PR08MB3716D1CAAC616D85118DEAD7FA1C0AM0PR08MB3716eurp_--


From nobody Wed Oct 21 01:56:12 2020
Return-Path: <Hannes.Tschofenig@arm.com>
X-Original-To: emu@ietfa.amsl.com
Delivered-To: emu@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 931D93A13CB for <emu@ietfa.amsl.com>; Wed, 21 Oct 2020 01:56:10 -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, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, HTML_MESSAGE=0.001, RCVD_IN_MSPIKE_H2=-0.001, SPF_PASS=-0.001, UNPARSEABLE_RELAY=0.001] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (1024-bit key) header.d=armh.onmicrosoft.com header.b=HgnVkUTH; dkim=pass (1024-bit key) header.d=armh.onmicrosoft.com header.b=HgnVkUTH
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 Yf0uN3nwVOS7 for <emu@ietfa.amsl.com>; Wed, 21 Oct 2020 01:56:08 -0700 (PDT)
Received: from EUR05-AM6-obe.outbound.protection.outlook.com (mail-am6eur05on2068.outbound.protection.outlook.com [40.107.22.68]) (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 371C63A13C7 for <emu@ietf.org>; Wed, 21 Oct 2020 01:56:08 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=armh.onmicrosoft.com;  s=selector2-armh-onmicrosoft-com; h=From:Date:Subject:Message-ID:Content-Type:MIME-Version:X-MS-Exchange-SenderADCheck; bh=Xzpc4LW5sp7pvKLnT7S2NcexbRjW2qPZKplQaufRjK4=; b=HgnVkUTHrrjiLlLqYWkxQiUw6U6OunD0qoWTfBWsGtcH0o+dLQfFf2JaMwWZdcf/Ix3uScqxJ4+lkoqjEy7nnhfWHw1DQ0EbAE1BEsC0/sM9YqY9uzX0SrVCGmHMfz6UT/yoHQk0zI9iu0VZW3zBPbprGvS9dyxAlv0brTKdRW8=
Received: from DB6PR0301CA0007.eurprd03.prod.outlook.com (2603:10a6:4:3e::17) by DBBPR08MB6186.eurprd08.prod.outlook.com (2603:10a6:10:204::5) with Microsoft SMTP Server (version=TLS1_2, cipher=TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384) id 15.20.3499.18; Wed, 21 Oct 2020 08:56:05 +0000
Received: from DB5EUR03FT049.eop-EUR03.prod.protection.outlook.com (2603:10a6:4:3e:cafe::d5) by DB6PR0301CA0007.outlook.office365.com (2603:10a6:4:3e::17) with Microsoft SMTP Server (version=TLS1_2, cipher=TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384) id 15.20.3477.23 via Frontend Transport; Wed, 21 Oct 2020 08:56:05 +0000
X-MS-Exchange-Authentication-Results: spf=pass (sender IP is 63.35.35.123) smtp.mailfrom=arm.com; ietf.org; dkim=pass (signature was verified) header.d=armh.onmicrosoft.com;ietf.org; dmarc=pass action=none header.from=arm.com;
Received-SPF: Pass (protection.outlook.com: domain of arm.com designates 63.35.35.123 as permitted sender) receiver=protection.outlook.com; client-ip=63.35.35.123; helo=64aa7808-outbound-1.mta.getcheckrecipient.com;
Received: from 64aa7808-outbound-1.mta.getcheckrecipient.com (63.35.35.123) by DB5EUR03FT049.mail.protection.outlook.com (10.152.20.191) with Microsoft SMTP Server (version=TLS1_2, cipher=TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384) id 15.20.3499.18 via Frontend Transport; Wed, 21 Oct 2020 08:56:05 +0000
Received: ("Tessian outbound a64c3afb6fc9:v64"); Wed, 21 Oct 2020 08:56:05 +0000
X-CR-MTA-TID: 64aa7808
Received: from c374e79fe4e6.1 by 64aa7808-outbound-1.mta.getcheckrecipient.com id E0E1BF3A-9C33-4CE9-A326-2EF35D179B8F.1;  Wed, 21 Oct 2020 08:56:00 +0000
Received: from EUR04-DB3-obe.outbound.protection.outlook.com by 64aa7808-outbound-1.mta.getcheckrecipient.com with ESMTPS id c374e79fe4e6.1 (version=TLSv1.2 cipher=ECDHE-RSA-AES256-GCM-SHA384); Wed, 21 Oct 2020 08:56:00 +0000
ARC-Seal: i=1; a=rsa-sha256; s=arcselector9901; d=microsoft.com; cv=none; b=a7ucfUSXm47UChMg8jE/gYZ/gzbNABRkML1BYZ1KB5b0pgYhZXueK6/QQv0NFVDyxq9kBfKSbNWbv4eYA+qK476IVFvC12pGi45MvxcIN9f4QUuXb3l4g4ZZNTWqt+KUdsqw/oO10NQPt8HF92kNFk9YQa8efNe8PIyauEeLO0K9nMoImDROJ6Fwphh4r+vpogi8mx8wZ3pJo3EUnMFjIQ65A/5pihG1SZLMqHhaEJlKCfXUuJlJCQM5uDiNUGjK0mJYK55HcNVyH1BtruHFAggjeQ38HRO8zS2hyr6TWl+kD68BSTTzcKFD3uS4NwUL8Du3xzOf1pmqGBuqdKVuhg==
ARC-Message-Signature: i=1; a=rsa-sha256; c=relaxed/relaxed; d=microsoft.com;  s=arcselector9901; h=From:Date:Subject:Message-ID:Content-Type:MIME-Version:X-MS-Exchange-SenderADCheck; bh=Xzpc4LW5sp7pvKLnT7S2NcexbRjW2qPZKplQaufRjK4=; b=Yy1A6G+QwinyI+mEnNAjAvKVRjRh3SHB15zN/d3K4sTZqGI8mGKfA66P+6pBycIR2hp3NEUkpTHow9sD5U1kYNyFRntkDYkART3JMUykh0GSyqsyJNYrEAE5lZDJQYs5IpgzIm3GX4BgGOe9SR2TBqroH4gYUdGMfe0rTXmg8c1UUYSgu5c5pIVo+uOCkhJ1UtE+F4D/TZePyx/6pAcfeY0yQBebWB2wVnI616PhQL2mlrZNNz47hdhg8GexaNooz6pOJCvXtvoUiQ7h0qnHrSUokOt8/oHCT/np2URtoQzuWEWRelIX5Dt43loF1xi8DhmffABuHGKhYvkxKCkREA==
ARC-Authentication-Results: i=1; mx.microsoft.com 1; spf=pass smtp.mailfrom=arm.com; dmarc=pass action=none header.from=arm.com; dkim=pass header.d=arm.com; arc=none
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=armh.onmicrosoft.com;  s=selector2-armh-onmicrosoft-com; h=From:Date:Subject:Message-ID:Content-Type:MIME-Version:X-MS-Exchange-SenderADCheck; bh=Xzpc4LW5sp7pvKLnT7S2NcexbRjW2qPZKplQaufRjK4=; b=HgnVkUTHrrjiLlLqYWkxQiUw6U6OunD0qoWTfBWsGtcH0o+dLQfFf2JaMwWZdcf/Ix3uScqxJ4+lkoqjEy7nnhfWHw1DQ0EbAE1BEsC0/sM9YqY9uzX0SrVCGmHMfz6UT/yoHQk0zI9iu0VZW3zBPbprGvS9dyxAlv0brTKdRW8=
Received: from AM0PR08MB3716.eurprd08.prod.outlook.com (2603:10a6:208:106::13) by AM0PR08MB5332.eurprd08.prod.outlook.com (2603:10a6:208:17e::8) with Microsoft SMTP Server (version=TLS1_2, cipher=TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384) id 15.20.3499.18; Wed, 21 Oct 2020 08:55:59 +0000
Received: from AM0PR08MB3716.eurprd08.prod.outlook.com ([fe80::900e:c64d:a006:4860]) by AM0PR08MB3716.eurprd08.prod.outlook.com ([fe80::900e:c64d:a006:4860%6]) with mapi id 15.20.3455.037; Wed, 21 Oct 2020 08:55:59 +0000
From: Hannes Tschofenig <Hannes.Tschofenig@arm.com>
To: "emu@ietf.org" <emu@ietf.org>
Thread-Topic: draft-ietf-emu-eap-tls13-11: Commitment Message
Thread-Index: AdanctIIdvWytKycRwySpguVsiPTSg==
Date: Wed, 21 Oct 2020 08:55:59 +0000
Message-ID: <AM0PR08MB3716DDE49C414EBCCCF79D08FA1C0@AM0PR08MB3716.eurprd08.prod.outlook.com>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
x-ts-tracking-id: 6134AF958F11FA459A5117E319C17016.0
x-checkrecipientchecked: true
Authentication-Results-Original: ietf.org; dkim=none (message not signed) header.d=none;ietf.org; dmarc=none action=none header.from=arm.com;
x-originating-ip: [156.67.196.116]
x-ms-publictraffictype: Email
X-MS-Office365-Filtering-HT: Tenant
X-MS-Office365-Filtering-Correlation-Id: d06b4519-f50a-4856-0a94-08d8759f2528
x-ms-traffictypediagnostic: AM0PR08MB5332:|DBBPR08MB6186:
X-Microsoft-Antispam-PRVS: <DBBPR08MB61869F1FF56FA88EBC69A75EFA1C0@DBBPR08MB6186.eurprd08.prod.outlook.com>
x-checkrecipientrouted: true
nodisclaimer: true
x-ms-oob-tlc-oobclassifiers: OLM:10000;OLM:10000;
X-MS-Exchange-SenderADCheck: 1
X-Microsoft-Antispam-Untrusted: BCL:0;
X-Microsoft-Antispam-Message-Info-Original: ECEI4OPsqPRxwraPbMY5Mg07n6yEilmXY4WixmpvnxVFH6vK9J/gRgEkibZa0R4tuZ49odIEjv2Ao01tzkbSiFIvK8na6nKPMWUNY/2x4Fd6+pmiIx80+xz1fC03caFCdwHJWtV8XeOqwDWMIHIcgP1Wt+J69KLFhwePOAHCiuU1Fz0XYB5JPh87k3+wc2+W3LbD/Lngf4dvb1Dnk3M13TBRnDV32wyx7P/MlDOk3dnRNs0vKRis8vYFvWqq4ecrH32EDa4HUBIVekwOLArQgq2ISC8/SQ4EnPa70MpN5w8bt5d9eiw1wZmfs7UiJdpexNrDQdIjOAnypnNqY6SVkw==
X-Forefront-Antispam-Report-Untrusted: CIP:255.255.255.255; CTRY:; LANG:en; SCL:1; SRV:; IPV:NLI; SFV:NSPM; H:AM0PR08MB3716.eurprd08.prod.outlook.com; PTR:; CAT:NONE; SFS:(4636009)(376002)(136003)(366004)(346002)(396003)(39860400002)(86362001)(55016002)(26005)(9686003)(5660300002)(71200400001)(6916009)(478600001)(8936002)(2906002)(316002)(6506007)(33656002)(66946007)(66556008)(66446008)(64756008)(66476007)(186003)(52536014)(8676002)(76116006)(15650500001)(7696005)(83380400001); DIR:OUT; SFP:1101; 
x-ms-exchange-antispam-messagedata: 5gThKYFRBpcOz1Wa5vvZvSKE6NRYUeypVqR7SFqMhamEQ7YBCEx+SD+qJLYkmj4ub5BlLr4fFJNHqsRtWX5PH5Lg6dAgk3CGBRdnY3Wqwxfpsp8haaQlkxcQhyM1vt6k5yI4RYZVY/uc9+gkTmwIdpRWdgXwvQ14Xgk5vXDMCgmo24wuqLWLnfI5MDJ4+r5ui9+bev/8q6L/5WiupMeDyzmMEI9/Emowl52+lyjJYiPOMnGCcioYADx6PeSXriiZ8tQC4W4sJWLInfIAR1sNQ6tDTyJqKaiMLj0J8eIwWUabCb/UG5qnE9KAvOa6yGwl0i+xJDmYUMe4rSgnCaWAwG/w3SBYtEiHWmwHRWKvNrBC46IB36gRsvcVQovlgbZbXXs4wfBWcr4RxF6WCoyrn+BauT2abbBFLdGJpAMiYleCNIruyJdJqFcTf+hlrvGYmqtP7DmjjK7oy/DbBQSKg+LraeRL9IhNeBszFI2hnwdYUdcWC7BIBkm6aCDZj6uSn2IB+NmsZijEHYkjHVo2Lt4j/CiAYvdiNfkoeJIpEn/t7ibGuGVGy4gPDyhDch8P9yDcYUEQ02V3X/8yKEKdLxuMGi25D0H6Bs6Cs+dptNyXpIDYjFAe8KJTwe3wslEJu0FN68NntG8sOlkEmdQMKQ==
x-ms-exchange-transport-forked: True
Content-Type: multipart/alternative; boundary="_000_AM0PR08MB3716DDE49C414EBCCCF79D08FA1C0AM0PR08MB3716eurp_"
MIME-Version: 1.0
X-MS-Exchange-Transport-CrossTenantHeadersStamped: AM0PR08MB5332
Original-Authentication-Results: ietf.org; dkim=none (message not signed) header.d=none;ietf.org; dmarc=none action=none header.from=arm.com;
X-EOPAttributedMessage: 0
X-MS-Exchange-Transport-CrossTenantHeadersStripped: DB5EUR03FT049.eop-EUR03.prod.protection.outlook.com
X-MS-Office365-Filtering-Correlation-Id-Prvs: 6c695921-a723-4af7-3c68-08d8759f216d
X-Microsoft-Antispam: BCL:0;
X-Microsoft-Antispam-Message-Info: hu9zwF17PkIQm7wjls3dNx+tsCrwCDMkdqWpn4rTw7nKNweKRQHw9Pb93GR9UOu0EtobolsPkuH+qjneJjQw9Sh069+SsHoPkm7c9ZxuTaXf9N/n1vcN+3y5IP69vYu12aUwufqX1qep4B22o6j/xlrew0uKErAaQJc/YmhdaGzS/L1rB8TcqGcA2ZM4XcFO2VxStMqmFgV1M8DCWwwC8T3j7EZmrMlqCQ+DMBV8EjvXQtcsUn5RnA2cYjw9K4RMJXpuBQgvtWMeHTQ56MmzCyA4uo3eoiHhq6i9BS1EtN+hau3H8bXmY9/b9ZocSkKfGhyP3P5oJGSXoqGg04flPFDfj6wvyLK+6yWBNh7FNlQkOFJzVk42Tpv983JWlWrfCAeHoT0cvs1EpjEbP5UFpA==
X-Forefront-Antispam-Report: CIP:63.35.35.123; CTRY:IE; LANG:en; SCL:1; SRV:;  IPV:CAL; SFV:NSPM; H:64aa7808-outbound-1.mta.getcheckrecipient.com;  PTR:ec2-63-35-35-123.eu-west-1.compute.amazonaws.com; CAT:NONE; SFS:(4636009)(376002)(346002)(396003)(136003)(39860400002)(46966005)(47076004)(55016002)(316002)(336012)(186003)(6506007)(26005)(478600001)(7696005)(33656002)(86362001)(8936002)(2906002)(9686003)(52536014)(6916009)(8676002)(15650500001)(81166007)(356005)(5660300002)(70206006)(82310400003)(70586007)(82740400003)(83380400001); DIR:OUT; SFP:1101; 
X-OriginatorOrg: arm.com
X-MS-Exchange-CrossTenant-OriginalArrivalTime: 21 Oct 2020 08:56:05.6476 (UTC)
X-MS-Exchange-CrossTenant-Network-Message-Id: d06b4519-f50a-4856-0a94-08d8759f2528
X-MS-Exchange-CrossTenant-Id: f34e5979-57d9-4aaa-ad4d-b122a662184d
X-MS-Exchange-CrossTenant-OriginalAttributedTenantConnectingIp: TenantId=f34e5979-57d9-4aaa-ad4d-b122a662184d; Ip=[63.35.35.123];  Helo=[64aa7808-outbound-1.mta.getcheckrecipient.com]
X-MS-Exchange-CrossTenant-AuthSource: DB5EUR03FT049.eop-EUR03.prod.protection.outlook.com
X-MS-Exchange-CrossTenant-AuthAs: Anonymous
X-MS-Exchange-CrossTenant-FromEntityHeader: HybridOnPrem
X-MS-Exchange-Transport-CrossTenantHeadersStamped: DBBPR08MB6186
Archived-At: <https://mailarchive.ietf.org/arch/msg/emu/O4tqbA0lqcTwCvWt_q9T5TlMBTc>
Subject: [Emu] draft-ietf-emu-eap-tls13-11: Commitment Message
X-BeenThere: emu@ietf.org
X-Mailman-Version: 2.1.29
Precedence: list
List-Id: "EAP Methods Update \(EMU\)" <emu.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/emu>, <mailto:emu-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/emu/>
List-Post: <mailto:emu@ietf.org>
List-Help: <mailto:emu-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/emu>, <mailto:emu-request@ietf.org?subject=subscribe>
X-List-Received-Date: Wed, 21 Oct 2020 08:56:11 -0000

--_000_AM0PR08MB3716DDE49C414EBCCCF79D08FA1C0AM0PR08MB3716eurp_
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: quoted-printable

Hi all,



in an earlier email on this topic John wrote "I don't see why anybody would=
 get the impressions that the application data would be unencrypted, all ap=
plication data in TLS 1.3 is encrypted."



Even in the latest version of the draft (version -11) I can still find text=
 that says the contrary.



Section 2.4:



"

   While EAP-TLS does not protect any application data, the negotiated

   cipher suites and algorithms MAY be used to secure data as done in

   other TLS-based EAP methods.

"



Section 2.1.1:



"

   After the TLS handshake has completed

   and all Post-Handshake messages have been sent, the EAP server sends

   EAP-Success.

"



Even the figure that follows this statement shows that this is not true bec=
ause there is still the Commitment Message.



Can you see how this is confusing?



I had suggested to add a note to the introduction to make it clear that the=
 Commitment Message is one of the two things that changed with this draft. =
(The other aspect is the changed key exporting.)



Currently, the important information on how the Commitment Message works is=
 buried in a section called EAP State Machines when nothing in the draft ca=
n possibly change the EAP state machine.



Ciao

Hannes



IMPORTANT NOTICE: The contents of this email and any attachments are confid=
ential and may also be privileged. If you are not the intended recipient, p=
lease notify the sender immediately and do not disclose the contents to any=
 other person, use it for any purpose, or store or copy the information in =
any medium. Thank you.

--_000_AM0PR08MB3716DDE49C414EBCCCF79D08FA1C0AM0PR08MB3716eurp_
Content-Type: text/html; charset="us-ascii"
Content-Transfer-Encoding: quoted-printable

<html xmlns:v=3D"urn:schemas-microsoft-com:vml" xmlns:o=3D"urn:schemas-micr=
osoft-com:office:office" xmlns:w=3D"urn:schemas-microsoft-com:office:word" =
xmlns:m=3D"http://schemas.microsoft.com/office/2004/12/omml" xmlns=3D"http:=
//www.w3.org/TR/REC-html40">
<head>
<meta http-equiv=3D"Content-Type" content=3D"text/html; charset=3Dus-ascii"=
>
<meta name=3D"Generator" content=3D"Microsoft Word 15 (filtered medium)">
<style><!--
/* Font Definitions */
@font-face
	{font-family:"Cambria Math";
	panose-1:2 4 5 3 5 4 6 3 2 4;}
@font-face
	{font-family:DengXian;
	panose-1:2 1 6 0 3 1 1 1 1 1;}
@font-face
	{font-family:Calibri;
	panose-1:2 15 5 2 2 2 4 3 2 4;}
@font-face
	{font-family:"\@DengXian";
	panose-1:2 1 6 0 3 1 1 1 1 1;}
/* Style Definitions */
p.MsoNormal, li.MsoNormal, div.MsoNormal
	{margin:0in;
	font-size:11.0pt;
	font-family:"Calibri",sans-serif;}
p.MsoPlainText, li.MsoPlainText, div.MsoPlainText
	{mso-style-priority:99;
	mso-style-link:"Plain Text Char";
	margin:0in;
	font-size:11.0pt;
	font-family:"Calibri",sans-serif;}
span.EmailStyle17
	{mso-style-type:personal-compose;
	font-family:"Calibri",sans-serif;
	color:windowtext;}
span.PlainTextChar
	{mso-style-name:"Plain Text Char";
	mso-style-priority:99;
	mso-style-link:"Plain Text";
	font-family:"Calibri",sans-serif;}
.MsoChpDefault
	{mso-style-type:export-only;
	font-family:"Calibri",sans-serif;}
@page WordSection1
	{size:8.5in 11.0in;
	margin:1.0in 1.0in 1.0in 1.0in;}
div.WordSection1
	{page:WordSection1;}
--></style><!--[if gte mso 9]><xml>
<o:shapedefaults v:ext=3D"edit" spidmax=3D"1026" />
</xml><![endif]--><!--[if gte mso 9]><xml>
<o:shapelayout v:ext=3D"edit">
<o:idmap v:ext=3D"edit" data=3D"1" />
</o:shapelayout></xml><![endif]-->
</head>
<body lang=3D"EN-US" link=3D"#0563C1" vlink=3D"#954F72">
<div class=3D"WordSection1">
<p class=3D"MsoPlainText">Hi all, <o:p></o:p></p>
<p class=3D"MsoPlainText"><o:p>&nbsp;</o:p></p>
<p class=3D"MsoPlainText">in an earlier email on this topic John wrote &#82=
20;I don't see why anybody would get the impressions that the application d=
ata would be unencrypted, all application data in TLS 1.3 is encrypted.&#82=
21;<o:p></o:p></p>
<p class=3D"MsoPlainText"><o:p>&nbsp;</o:p></p>
<p class=3D"MsoPlainText">Even in the latest version of the draft (version =
-11) I can still find text that says the contrary.
<o:p></o:p></p>
<p class=3D"MsoPlainText"><o:p>&nbsp;</o:p></p>
<p class=3D"MsoPlainText">Section 2.4: <o:p></o:p></p>
<p class=3D"MsoPlainText"><o:p>&nbsp;</o:p></p>
<p class=3D"MsoPlainText">&quot;<o:p></o:p></p>
<p class=3D"MsoPlainText">&nbsp;&nbsp; While EAP-TLS does not protect any a=
pplication data, the negotiated<o:p></o:p></p>
<p class=3D"MsoPlainText">&nbsp;&nbsp; cipher suites and algorithms MAY be =
used to secure data as done in<o:p></o:p></p>
<p class=3D"MsoPlainText">&nbsp;&nbsp; other TLS-based EAP methods.<o:p></o=
:p></p>
<p class=3D"MsoPlainText">&quot;<o:p></o:p></p>
<p class=3D"MsoPlainText"><o:p>&nbsp;</o:p></p>
<p class=3D"MsoPlainText">Section 2.1.1:<o:p></o:p></p>
<p class=3D"MsoPlainText"><o:p>&nbsp;</o:p></p>
<p class=3D"MsoPlainText">&quot;<o:p></o:p></p>
<p class=3D"MsoPlainText">&nbsp;&nbsp; After the TLS handshake has complete=
d<o:p></o:p></p>
<p class=3D"MsoPlainText">&nbsp;&nbsp; and all Post-Handshake messages have=
 been sent, the EAP server sends<o:p></o:p></p>
<p class=3D"MsoPlainText">&nbsp;&nbsp; EAP-Success.<o:p></o:p></p>
<p class=3D"MsoPlainText">&quot;<o:p></o:p></p>
<p class=3D"MsoPlainText"><o:p>&nbsp;</o:p></p>
<p class=3D"MsoPlainText">Even the figure that follows this statement shows=
 that this is not true because there is still the Commitment Message.
<o:p></o:p></p>
<p class=3D"MsoPlainText"><o:p>&nbsp;</o:p></p>
<p class=3D"MsoPlainText">Can you see how this is confusing?<o:p></o:p></p>
<p class=3D"MsoPlainText"><o:p>&nbsp;</o:p></p>
<p class=3D"MsoPlainText">I had suggested to add a note to the introduction=
 to make it clear that the Commitment Message is one of the two things that=
 changed with this draft. (The other aspect is the changed key exporting.)
<o:p></o:p></p>
<p class=3D"MsoPlainText"><o:p>&nbsp;</o:p></p>
<p class=3D"MsoPlainText">Currently, the important information on how the C=
ommitment Message works is buried in a section called EAP State Machines wh=
en nothing in the draft can possibly change the EAP state machine.
<o:p></o:p></p>
<p class=3D"MsoPlainText"><o:p>&nbsp;</o:p></p>
<p class=3D"MsoPlainText">Ciao<o:p></o:p></p>
<p class=3D"MsoPlainText">Hannes<o:p></o:p></p>
<p class=3D"MsoPlainText"><o:p>&nbsp;</o:p></p>
<p class=3D"MsoNormal"><o:p>&nbsp;</o:p></p>
</div>
IMPORTANT NOTICE: The contents of this email and any attachments are confid=
ential and may also be privileged. If you are not the intended recipient, p=
lease notify the sender immediately and do not disclose the contents to any=
 other person, use it for any purpose,
 or store or copy the information in any medium. Thank you.
</body>
</html>

--_000_AM0PR08MB3716DDE49C414EBCCCF79D08FA1C0AM0PR08MB3716eurp_--


From nobody Wed Oct 21 02:01:19 2020
Return-Path: <Hannes.Tschofenig@arm.com>
X-Original-To: emu@ietfa.amsl.com
Delivered-To: emu@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 20F123A13D3 for <emu@ietfa.amsl.com>; Wed, 21 Oct 2020 02:01:18 -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, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, HTML_MESSAGE=0.001, RCVD_IN_MSPIKE_H2=-0.001, SPF_PASS=-0.001, UNPARSEABLE_RELAY=0.001] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (1024-bit key) header.d=armh.onmicrosoft.com header.b=3Twb0LV9; dkim=pass (1024-bit key) header.d=armh.onmicrosoft.com header.b=3Twb0LV9
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 0_jbXAZtjiUh for <emu@ietfa.amsl.com>; Wed, 21 Oct 2020 02:01:15 -0700 (PDT)
Received: from EUR05-VI1-obe.outbound.protection.outlook.com (mail-vi1eur05on2089.outbound.protection.outlook.com [40.107.21.89]) (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 347BE3A13CC for <emu@ietf.org>; Wed, 21 Oct 2020 02:01:09 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=armh.onmicrosoft.com;  s=selector2-armh-onmicrosoft-com; h=From:Date:Subject:Message-ID:Content-Type:MIME-Version:X-MS-Exchange-SenderADCheck; bh=EuqKVad+zm2RgQyJnSIJS4ybwCQV/ZYv4Fd7+Hwhx9g=; b=3Twb0LV9rmIHEgIuvTTdiXozbD/KJgUcXGUXVD6ztUqwaLYF6+eCo4SR9hyVXStdENX3MPfH9BcLfsqxcZJnGCwn+tXxV/z3Is2FNMEohkiEWELhnVT2f/Nm1D2u0jBH339RTO+bGOmLRqfPxC2oQTrn/V0bZCdWXa58X3TsGnI=
Received: from AM5PR0502CA0010.eurprd05.prod.outlook.com (2603:10a6:203:91::20) by DB8PR08MB5385.eurprd08.prod.outlook.com (2603:10a6:10:119::11) with Microsoft SMTP Server (version=TLS1_2, cipher=TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384) id 15.20.3455.23; Wed, 21 Oct 2020 09:01:07 +0000
Received: from AM5EUR03FT047.eop-EUR03.prod.protection.outlook.com (2603:10a6:203:91:cafe::93) by AM5PR0502CA0010.outlook.office365.com (2603:10a6:203:91::20) with Microsoft SMTP Server (version=TLS1_2, cipher=TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384) id 15.20.3499.18 via Frontend Transport; Wed, 21 Oct 2020 09:01:07 +0000
X-MS-Exchange-Authentication-Results: spf=pass (sender IP is 63.35.35.123) smtp.mailfrom=arm.com; ietf.org; dkim=pass (signature was verified) header.d=armh.onmicrosoft.com;ietf.org; dmarc=pass action=none header.from=arm.com;
Received-SPF: Pass (protection.outlook.com: domain of arm.com designates 63.35.35.123 as permitted sender) receiver=protection.outlook.com; client-ip=63.35.35.123; helo=64aa7808-outbound-1.mta.getcheckrecipient.com;
Received: from 64aa7808-outbound-1.mta.getcheckrecipient.com (63.35.35.123) by AM5EUR03FT047.mail.protection.outlook.com (10.152.16.197) with Microsoft SMTP Server (version=TLS1_2, cipher=TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384) id 15.20.3499.18 via Frontend Transport; Wed, 21 Oct 2020 09:01:07 +0000
Received: ("Tessian outbound c189680f801b:v64"); Wed, 21 Oct 2020 09:01:07 +0000
X-CR-MTA-TID: 64aa7808
Received: from f3516be55a0a.1 by 64aa7808-outbound-1.mta.getcheckrecipient.com id A22F1A85-554F-4FD1-AF57-63D8B95F7611.1;  Wed, 21 Oct 2020 09:01:02 +0000
Received: from EUR03-VE1-obe.outbound.protection.outlook.com by 64aa7808-outbound-1.mta.getcheckrecipient.com with ESMTPS id f3516be55a0a.1 (version=TLSv1.2 cipher=ECDHE-RSA-AES256-GCM-SHA384); Wed, 21 Oct 2020 09:01:02 +0000
ARC-Seal: i=1; a=rsa-sha256; s=arcselector9901; d=microsoft.com; cv=none; b=ONKyyDUzresIxfK35qJrlqusNfNrSwtkTl2raW3fmTqPDcy3LeKmqZSL3WOvIkOUWbc6wNbExddKIRCt3navTLYgkfXCs68aRr8wat0oxrDbCpWAlEi9BLszSTqO0Td4B4GjPCp/vybrqR+MfEYh/p9doO/u9breVuOkmL5Vtie16iwZFdSu0idlFMCD6ErGELyuYvaFJYWfaguCkeik4Fff5f0Xob0KRfyq6BYOWGK3pzXMgG+nQQ7Hot84FLghS+svhpCyluneltJoV3BtHlN5J4qbL+WHgrr3ZRX7jeQ3LdNulfWyd9m8MD7g0JorhvWFDe8YSZFq8g9TASq4rQ==
ARC-Message-Signature: i=1; a=rsa-sha256; c=relaxed/relaxed; d=microsoft.com;  s=arcselector9901; h=From:Date:Subject:Message-ID:Content-Type:MIME-Version:X-MS-Exchange-SenderADCheck; bh=EuqKVad+zm2RgQyJnSIJS4ybwCQV/ZYv4Fd7+Hwhx9g=; b=RBS/UZRbozLs1NrFiXjL7/PeXNG/XZ4z943QbMuVWJGgoBZgPyPyfeosPPlSjSoW09j9MWadqG8SUfasiXIAFwFYHSf+CTydPjpjc4F4aZzcsV5cMucNbotv9t/k96J2DSShABqtNrhFRis53TrBhLBTO9OVDmdbt88jq5MYQLDH93X+HPP3GKNZaJPcm3U/tBrXx/xW+UAknFXzvZ5WPLQ5A481tL3SQitXPJeWqUeCMr68ydNvNNlU12MyvlT4FZJ21hkgJRx/DOQyWUOg2ukd+KHkGAqnqI0m1sPzD3vE+6rGZiXXTOQEC1sWnsXcjLk6AYL5RZijGbFinKuMSA==
ARC-Authentication-Results: i=1; mx.microsoft.com 1; spf=pass smtp.mailfrom=arm.com; dmarc=pass action=none header.from=arm.com; dkim=pass header.d=arm.com; arc=none
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=armh.onmicrosoft.com;  s=selector2-armh-onmicrosoft-com; h=From:Date:Subject:Message-ID:Content-Type:MIME-Version:X-MS-Exchange-SenderADCheck; bh=EuqKVad+zm2RgQyJnSIJS4ybwCQV/ZYv4Fd7+Hwhx9g=; b=3Twb0LV9rmIHEgIuvTTdiXozbD/KJgUcXGUXVD6ztUqwaLYF6+eCo4SR9hyVXStdENX3MPfH9BcLfsqxcZJnGCwn+tXxV/z3Is2FNMEohkiEWELhnVT2f/Nm1D2u0jBH339RTO+bGOmLRqfPxC2oQTrn/V0bZCdWXa58X3TsGnI=
Received: from AM0PR08MB3716.eurprd08.prod.outlook.com (2603:10a6:208:106::13) by AM0PR08MB3796.eurprd08.prod.outlook.com (2603:10a6:208:100::13) with Microsoft SMTP Server (version=TLS1_2, cipher=TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384) id 15.20.3499.18; Wed, 21 Oct 2020 09:00:49 +0000
Received: from AM0PR08MB3716.eurprd08.prod.outlook.com ([fe80::900e:c64d:a006:4860]) by AM0PR08MB3716.eurprd08.prod.outlook.com ([fe80::900e:c64d:a006:4860%6]) with mapi id 15.20.3455.037; Wed, 21 Oct 2020 09:00:49 +0000
From: Hannes Tschofenig <Hannes.Tschofenig@arm.com>
To: "emu@ietf.org" <emu@ietf.org>
Thread-Topic: draft-ietf-emu-eap-tls13-11: Updates RFC 5216
Thread-Index: AdaniA3c0x5tKPKkRly4vRg4IrXi2w==
Date: Wed, 21 Oct 2020 09:00:49 +0000
Message-ID: <AM0PR08MB3716A5224BA1C5D36BC150A0FA1C0@AM0PR08MB3716.eurprd08.prod.outlook.com>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
x-ts-tracking-id: 9F715C8425535945866F43C13A32502F.0
x-checkrecipientchecked: true
Authentication-Results-Original: ietf.org; dkim=none (message not signed) header.d=none;ietf.org; dmarc=none action=none header.from=arm.com;
x-originating-ip: [156.67.196.116]
x-ms-publictraffictype: Email
X-MS-Office365-Filtering-HT: Tenant
X-MS-Office365-Filtering-Correlation-Id: f8ac7d4d-0c37-47d6-7ddb-08d8759fd8f8
x-ms-traffictypediagnostic: AM0PR08MB3796:|DB8PR08MB5385:
X-Microsoft-Antispam-PRVS: <DB8PR08MB53859C57AAF1AAE74E692AD4FA1C0@DB8PR08MB5385.eurprd08.prod.outlook.com>
x-checkrecipientrouted: true
nodisclaimer: true
x-ms-oob-tlc-oobclassifiers: OLM:10000;OLM:10000;
X-MS-Exchange-SenderADCheck: 1
X-Microsoft-Antispam-Untrusted: BCL:0;
X-Microsoft-Antispam-Message-Info-Original: +UFO3NoFORIHCXnKWzVju2/QocLhRSWHNN1lvSWMg8m5vSMB5rXvcqKTdB31vxds8FZt8F0aBaC/sFkAWMAeazitUHZs7P51uI0PB8kHQT8jSZ805q3iDP6AqE6fnBdAKwEeLAjFG4HUqRAuQ688H2PXyXMNrcRaUJeytBBIUGde5CnvUUJ5ZzOgm2mJdiRcWYWI95DT1K5L1iu4OHxxLTCYPsc8eRVu0j5wSHBtSPz5AVJWt2/+xqU0j3Gz5dkNrqQXT6SsUp1kEf7rwtIFdVHb6sUFfHP3i72c8Lx4nhjLm8muxgAWeVkerdC5z6Zwm8UPxY0Wp82z2wn3lXTBXg==
X-Forefront-Antispam-Report-Untrusted: CIP:255.255.255.255; CTRY:; LANG:en; SCL:1; SRV:; IPV:NLI; SFV:NSPM; H:AM0PR08MB3716.eurprd08.prod.outlook.com; PTR:; CAT:NONE; SFS:(4636009)(376002)(346002)(366004)(396003)(136003)(39860400002)(55016002)(316002)(186003)(6506007)(26005)(478600001)(7696005)(33656002)(86362001)(8936002)(2906002)(76116006)(71200400001)(6916009)(8676002)(15650500001)(66446008)(64756008)(66556008)(66946007)(5660300002)(9686003)(52536014)(66476007)(83380400001); DIR:OUT; SFP:1101; 
x-ms-exchange-antispam-messagedata: HPX3MmJaCzt3D4qNdInW5l1vPMy/yd6HVVCKF7vCwwsevDYWLpW6PN099bzRVSx+dQR2UwtjjUleDuqW+H2xtjEFVZr4weuxTkCBOTdIQ0NIgyk7bgR1ePr07z4bjzsy8534Dh7PBrPLbqLmA/sj+KRynDcFgIm+7W3/3/1Z1nfK/meh5k+WAFXYdrPyt6xpNfjDOpEg+BYt2dX8/TOkBWTRLQEDJinjvDBdPc26QfKatsjEFkE5DJvmXBR3py+ZK15/xK29pwo9/tYMhpDVShRnMH6mj8DyWwErNgPiOIcTNBovpklVEYgOLWUkMkwWg+xhFHLBX785e0XaTk+WetWhp2TfCgTunL8b60xWhowvpVzNph41DjKrNhv9J53695lP6Etpv0ljaCCSbGuFSpALPA+o9Wt9s0BHOPK6wXRELONvC/BKYJ+2Nf2UELrVv5v2aCQJ6239HUEa/NmyXIUtErFum+oaMSmLIA/+c5+IOdhKcW2sZ7PevPcNyXoJTvWQNOBA7e94JFYjkRQ1O+QwhS8wNvW51/TM9WBCXN2k6F64yyv5+L8JgiCaRRqH9MbGCKFXUPjjvbPb7AxTdW+GrQwlI/Xs9yWvEPRiU3L7STzZB2rLEQQAqNvBd63SA3MTC6ZtoDRL90Rzn9k0xA==
x-ms-exchange-transport-forked: True
Content-Type: multipart/alternative; boundary="_000_AM0PR08MB3716A5224BA1C5D36BC150A0FA1C0AM0PR08MB3716eurp_"
MIME-Version: 1.0
X-MS-Exchange-Transport-CrossTenantHeadersStamped: AM0PR08MB3796
Original-Authentication-Results: ietf.org; dkim=none (message not signed) header.d=none;ietf.org; dmarc=none action=none header.from=arm.com;
X-EOPAttributedMessage: 0
X-MS-Exchange-Transport-CrossTenantHeadersStripped: AM5EUR03FT047.eop-EUR03.prod.protection.outlook.com
X-MS-Office365-Filtering-Correlation-Id-Prvs: 75f77ed1-b4d8-4d66-a15a-08d8759fce86
X-Microsoft-Antispam: BCL:0;
X-Microsoft-Antispam-Message-Info: lS7Ef1VTpWO1fDQC1x4kQ6i3oMTMJlRTtpCFGrJ/c3u0FtLLaHwczUWf6uAznPJoHQuK6yEhJ8QshvdgkKCebXCeOl8isLZSqqZXhPNtLLk9j+osAYruAq6vrwkaFKr/NBAtN3VEUtJM+SRtRpougvfiP+2cTy/tkt7B/K4Jf6oQJokGIF8q0FJ492fJjXCj20iApk+HoFqLD+Wf2YMFSWkwNyIPjxO2PHhVV+AQfiTZarAwPgZHihsk9/oqZTBhUwW37/63ofMLhaf5TZ6L7e8MS64iSOndBAlFd1zKp6JYaQnq+dPOvP9Kj1BNYNZll0pEGeadUIrLyAgT8mxA/bLB5k9qwdosZ/aMZxiLEe495rMDbl/jBuVmbr+0Ymve1k9m4Tj+y1C4OF+2FJqJQQ==
X-Forefront-Antispam-Report: CIP:63.35.35.123; CTRY:IE; LANG:en; SCL:1; SRV:;  IPV:CAL; SFV:NSPM; H:64aa7808-outbound-1.mta.getcheckrecipient.com;  PTR:ec2-63-35-35-123.eu-west-1.compute.amazonaws.com; CAT:NONE; SFS:(4636009)(39860400002)(396003)(136003)(376002)(346002)(46966005)(70206006)(2906002)(52536014)(8936002)(8676002)(478600001)(83380400001)(33656002)(15650500001)(81166007)(356005)(70586007)(9686003)(6916009)(5660300002)(6506007)(26005)(82740400003)(82310400003)(47076004)(36906005)(316002)(86362001)(336012)(55016002)(186003)(7696005); DIR:OUT; SFP:1101; 
X-OriginatorOrg: arm.com
X-MS-Exchange-CrossTenant-OriginalArrivalTime: 21 Oct 2020 09:01:07.2559 (UTC)
X-MS-Exchange-CrossTenant-Network-Message-Id: f8ac7d4d-0c37-47d6-7ddb-08d8759fd8f8
X-MS-Exchange-CrossTenant-Id: f34e5979-57d9-4aaa-ad4d-b122a662184d
X-MS-Exchange-CrossTenant-OriginalAttributedTenantConnectingIp: TenantId=f34e5979-57d9-4aaa-ad4d-b122a662184d; Ip=[63.35.35.123];  Helo=[64aa7808-outbound-1.mta.getcheckrecipient.com]
X-MS-Exchange-CrossTenant-AuthSource: AM5EUR03FT047.eop-EUR03.prod.protection.outlook.com
X-MS-Exchange-CrossTenant-AuthAs: Anonymous
X-MS-Exchange-CrossTenant-FromEntityHeader: HybridOnPrem
X-MS-Exchange-Transport-CrossTenantHeadersStamped: DB8PR08MB5385
Archived-At: <https://mailarchive.ietf.org/arch/msg/emu/shJ70BmJq_OqVMLQEAcE4kNhogA>
Subject: [Emu] draft-ietf-emu-eap-tls13-11: Updates RFC 5216
X-BeenThere: emu@ietf.org
X-Mailman-Version: 2.1.29
Precedence: list
List-Id: "EAP Methods Update \(EMU\)" <emu.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/emu>, <mailto:emu-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/emu/>
List-Post: <mailto:emu@ietf.org>
List-Help: <mailto:emu-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/emu>, <mailto:emu-request@ietf.org?subject=subscribe>
X-List-Received-Date: Wed, 21 Oct 2020 09:01:18 -0000

--_000_AM0PR08MB3716A5224BA1C5D36BC150A0FA1C0AM0PR08MB3716eurp_
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: quoted-printable

Hi all,

the draft says it updates the earlier EAP-TLS version and claims that the u=
pdates are related to

* Section 5.6 Authorization
* Section 5.7 Resumption

The content of Section 5.6 actually does not relate to EAP-TLS but is gener=
ic to all EAP methods. I don't think it even belongs in an EAP method docum=
ent.

The content of Section 5.7 claims that there are aspects of resumptions tha=
t are not described in the earlier version of EAP-TLS. The focus is then on=
 the way how the cached data is stored, an implementation-specific aspect, =
that is not specific to EAP-TLS because the concept of caching is used by o=
ther EAP methods too. Then, there is a threat presented whereby the authori=
zation information changes between the full handshake and the resumption ha=
ndshake. I believe that this is not a threat that is unique to EAP-TLS beca=
use this can happen even when there is no resumption. Nothing prevents you =
from checking authorization again when you do resumption though and even du=
ring an ongoing session. I would argue that there is a lot of text in there=
 that has nothing to do with EAP-TLS but rather concerns the whole system i=
n which EAP is used. If this is indeed a problem, I believe it should be co=
vered in a separate document. I don't think it is a problem because extensi=
ons for RADIUS and Diameter have been developed to address this issue to re=
voke authorization during the lifetime of a session.

Here is where it gets confusing. The introduction says "This document defin=
es how to use EAP-TLS with TLS 1.3 (or higher) and does not change how EAP-=
TLS is used with older versions of TLS." To me, this does not sound like an=
 update.

Reading more carefully one can notice that the actual update to EAP-TLS is =
hidden in Section 5.8 "Privacy Considerations" and Section 5.10 "Discovered=
 Vulnerabilities".

Section 5.8 says:
"
   it is RECOMMENDED for EAP peers to not use EAP-TLS with
   TLS 1.2 and static RSA based cipher suites without privacy.  This
   implies that an EAP peer SHOULD NOT continue the handshake if a TLS
   1.2 EAP server responds to an empty certificate message with a TLS
   alert message.
"

Section 5.10 says:
"
EAP-TLS implementations
   SHOULD mitigate known attacks and follow the recommendations in
   [RFC7525] and [I-D.ietf-tls-oldversions-deprecate].
"

Interestingly, RFC 7525 does not talk about EAP (and instead focuses on app=
lications like  HTTP, SMTP, IMAP, POP, SIP, and XMPP, as noted in the abstr=
act). RFC 7525, for example, does not mandate OCSP. It also recommends RSA,=
 which draft-ietf-emu-eaptlscert and this draft does not do. There seems to=
 be contradiction here.

At a minimum, I would clarify in the introduction what the updates to RFC 5=
216 are. This will help those implementers that focus on a variant of EAP-T=
LS that uses version 1.2. As mentioned above, I don't believe Sections 5.6 =
and 5.7 belong to this document. Leave it in there if someone in the group =
gets paid by the number of published pages.

Ciao
Hannes
IMPORTANT NOTICE: The contents of this email and any attachments are confid=
ential and may also be privileged. If you are not the intended recipient, p=
lease notify the sender immediately and do not disclose the contents to any=
 other person, use it for any purpose, or store or copy the information in =
any medium. Thank you.

--_000_AM0PR08MB3716A5224BA1C5D36BC150A0FA1C0AM0PR08MB3716eurp_
Content-Type: text/html; charset="us-ascii"
Content-Transfer-Encoding: quoted-printable

<html xmlns:v=3D"urn:schemas-microsoft-com:vml" xmlns:o=3D"urn:schemas-micr=
osoft-com:office:office" xmlns:w=3D"urn:schemas-microsoft-com:office:word" =
xmlns:m=3D"http://schemas.microsoft.com/office/2004/12/omml" xmlns=3D"http:=
//www.w3.org/TR/REC-html40">
<head>
<meta http-equiv=3D"Content-Type" content=3D"text/html; charset=3Dus-ascii"=
>
<meta name=3D"Generator" content=3D"Microsoft Word 15 (filtered medium)">
<style><!--
/* Font Definitions */
@font-face
	{font-family:"Cambria Math";
	panose-1:2 4 5 3 5 4 6 3 2 4;}
@font-face
	{font-family:DengXian;
	panose-1:2 1 6 0 3 1 1 1 1 1;}
@font-face
	{font-family:Calibri;
	panose-1:2 15 5 2 2 2 4 3 2 4;}
@font-face
	{font-family:"\@DengXian";
	panose-1:2 1 6 0 3 1 1 1 1 1;}
/* Style Definitions */
p.MsoNormal, li.MsoNormal, div.MsoNormal
	{margin:0in;
	font-size:11.0pt;
	font-family:"Calibri",sans-serif;}
span.EmailStyle17
	{mso-style-type:personal-compose;
	font-family:"Calibri",sans-serif;
	color:windowtext;}
.MsoChpDefault
	{mso-style-type:export-only;
	font-family:"Calibri",sans-serif;}
@page WordSection1
	{size:8.5in 11.0in;
	margin:1.0in 1.0in 1.0in 1.0in;}
div.WordSection1
	{page:WordSection1;}
--></style><!--[if gte mso 9]><xml>
<o:shapedefaults v:ext=3D"edit" spidmax=3D"1026" />
</xml><![endif]--><!--[if gte mso 9]><xml>
<o:shapelayout v:ext=3D"edit">
<o:idmap v:ext=3D"edit" data=3D"1" />
</o:shapelayout></xml><![endif]-->
</head>
<body lang=3D"EN-US" link=3D"#0563C1" vlink=3D"#954F72">
<div class=3D"WordSection1">
<p class=3D"MsoNormal">Hi all, <o:p></o:p></p>
<p class=3D"MsoNormal"><o:p>&nbsp;</o:p></p>
<p class=3D"MsoNormal">the draft says it updates the earlier EAP-TLS versio=
n and claims that the updates are related to
<o:p></o:p></p>
<p class=3D"MsoNormal"><o:p>&nbsp;</o:p></p>
<p class=3D"MsoNormal">* Section 5.6 Authorization<o:p></o:p></p>
<p class=3D"MsoNormal">* Section 5.7 Resumption<o:p></o:p></p>
<p class=3D"MsoNormal"><o:p>&nbsp;</o:p></p>
<p class=3D"MsoNormal">The content of Section 5.6 actually does not relate =
to EAP-TLS but is generic to all EAP methods. I don't think it even belongs=
 in an EAP method document.
<o:p></o:p></p>
<p class=3D"MsoNormal"><o:p>&nbsp;</o:p></p>
<p class=3D"MsoNormal">The content of Section 5.7 claims that there are asp=
ects of resumptions that are not described in the earlier version of EAP-TL=
S. The focus is then on the way how the cached data is stored, an implement=
ation-specific aspect, that is not
 specific to EAP-TLS because the concept of caching is used by other EAP me=
thods too. Then, there is a threat presented whereby the authorization info=
rmation changes between the full handshake and the resumption handshake. I =
believe that this is not a threat
 that is unique to EAP-TLS because this can happen even when there is no re=
sumption. Nothing prevents you from checking authorization again when you d=
o resumption though and even during an ongoing session. I would argue that =
there is a lot of text in there
 that has nothing to do with EAP-TLS but rather concerns the whole system i=
n which EAP is used. If this is indeed a problem, I believe it should be co=
vered in a separate document. I don&#8217;t think it is a problem because e=
xtensions for RADIUS and Diameter have
 been developed to address this issue to revoke authorization during the li=
fetime of a session.<o:p></o:p></p>
<p class=3D"MsoNormal"><o:p>&nbsp;</o:p></p>
<p class=3D"MsoNormal">Here is where it gets confusing. The introduction sa=
ys &quot;This document defines how to use EAP-TLS with TLS 1.3 (or higher) =
and does not change how EAP-TLS is used with older versions of TLS.&quot; T=
o me, this does not sound like an update.
<o:p></o:p></p>
<p class=3D"MsoNormal"><o:p>&nbsp;</o:p></p>
<p class=3D"MsoNormal">Reading more carefully one can notice that the actua=
l update to EAP-TLS is hidden in Section 5.8 &quot;Privacy Considerations&q=
uot; and Section 5.10 &quot;Discovered Vulnerabilities&quot;.
<o:p></o:p></p>
<p class=3D"MsoNormal"><o:p>&nbsp;</o:p></p>
<p class=3D"MsoNormal">Section 5.8 says:<o:p></o:p></p>
<p class=3D"MsoNormal">&quot;<o:p></o:p></p>
<p class=3D"MsoNormal">&nbsp;&nbsp; it is RECOMMENDED for EAP peers to not =
use EAP-TLS with<o:p></o:p></p>
<p class=3D"MsoNormal">&nbsp;&nbsp; TLS 1.2 and static RSA based cipher sui=
tes without privacy.&nbsp; This<o:p></o:p></p>
<p class=3D"MsoNormal">&nbsp;&nbsp; implies that an EAP peer SHOULD NOT con=
tinue the handshake if a TLS<o:p></o:p></p>
<p class=3D"MsoNormal">&nbsp;&nbsp; 1.2 EAP server responds to an empty cer=
tificate message with a TLS<o:p></o:p></p>
<p class=3D"MsoNormal">&nbsp;&nbsp; alert message.<o:p></o:p></p>
<p class=3D"MsoNormal">&quot;<o:p></o:p></p>
<p class=3D"MsoNormal"><o:p>&nbsp;</o:p></p>
<p class=3D"MsoNormal">Section 5.10 says:<o:p></o:p></p>
<p class=3D"MsoNormal">&quot;<o:p></o:p></p>
<p class=3D"MsoNormal">EAP-TLS implementations<o:p></o:p></p>
<p class=3D"MsoNormal">&nbsp;&nbsp; SHOULD mitigate known attacks and follo=
w the recommendations in<o:p></o:p></p>
<p class=3D"MsoNormal">&nbsp;&nbsp; [RFC7525] and [I-D.ietf-tls-oldversions=
-deprecate].<o:p></o:p></p>
<p class=3D"MsoNormal">&quot;<o:p></o:p></p>
<p class=3D"MsoNormal"><o:p>&nbsp;</o:p></p>
<p class=3D"MsoNormal">Interestingly, RFC 7525 does not talk about EAP (and=
 instead focuses on applications like&nbsp; HTTP, SMTP, IMAP, POP, SIP, and=
 XMPP, as noted in the abstract). RFC 7525, for example, does not mandate O=
CSP. It also recommends RSA, which draft-ietf-emu-eaptlscert
 and this draft does not do. There seems to be contradiction here. <o:p></o=
:p></p>
<p class=3D"MsoNormal"><o:p>&nbsp;</o:p></p>
<p class=3D"MsoNormal">At a minimum, I would clarify in the introduction wh=
at the updates to RFC 5216 are. This will help those implementers that focu=
s on a variant of EAP-TLS that uses version 1.2. As mentioned above, I don'=
t believe Sections 5.6 and 5.7 belong
 to this document. Leave it in there if someone in the group gets paid by t=
he number of published pages.
<o:p></o:p></p>
<p class=3D"MsoNormal"><o:p>&nbsp;</o:p></p>
<p class=3D"MsoNormal">Ciao<o:p></o:p></p>
<p class=3D"MsoNormal">Hannes<o:p></o:p></p>
</div>
IMPORTANT NOTICE: The contents of this email and any attachments are confid=
ential and may also be privileged. If you are not the intended recipient, p=
lease notify the sender immediately and do not disclose the contents to any=
 other person, use it for any purpose,
 or store or copy the information in any medium. Thank you.
</body>
</html>

--_000_AM0PR08MB3716A5224BA1C5D36BC150A0FA1C0AM0PR08MB3716eurp_--


From nobody Wed Oct 21 02:03:11 2020
Return-Path: <Hannes.Tschofenig@arm.com>
X-Original-To: emu@ietfa.amsl.com
Delivered-To: emu@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 2794E3A0B21 for <emu@ietfa.amsl.com>; Wed, 21 Oct 2020 02:03:10 -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, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, HTML_MESSAGE=0.001, RCVD_IN_MSPIKE_H2=-0.001, SPF_PASS=-0.001, UNPARSEABLE_RELAY=0.001] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (1024-bit key) header.d=armh.onmicrosoft.com header.b=MQkYLASp; dkim=pass (1024-bit key) header.d=armh.onmicrosoft.com header.b=MQkYLASp
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 AEvq4ffJ1jlt for <emu@ietfa.amsl.com>; Wed, 21 Oct 2020 02:03:07 -0700 (PDT)
Received: from EUR02-AM5-obe.outbound.protection.outlook.com (mail-eopbgr00055.outbound.protection.outlook.com [40.107.0.55]) (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 8BD793A13BF for <emu@ietf.org>; Wed, 21 Oct 2020 02:03:07 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=armh.onmicrosoft.com;  s=selector2-armh-onmicrosoft-com; h=From:Date:Subject:Message-ID:Content-Type:MIME-Version:X-MS-Exchange-SenderADCheck; bh=xyzGo4UstawCVSSc+8zHK6xOTWIpnrt0ZfQv0wwyrF0=; b=MQkYLASpH+Rnp2aqP5aTk8xQ0tUZacIte1YI7t3x7m/0RSdYRDYcmJtgK2bLWWaUq9z7mBWIOEYMGsucEjml5W0hPU57xVKmGA+2WMTH2SLVE3xE3xQZluF56wGe5Kc/bBm8rZsq+cvxkr+FceJ1dUjgTStIG3kvJnJDZtxQPs8=
Received: from AM4PR0302CA0019.eurprd03.prod.outlook.com (2603:10a6:205:2::32) by VE1PR08MB5615.eurprd08.prod.outlook.com (2603:10a6:800:1b3::23) with Microsoft SMTP Server (version=TLS1_2, cipher=TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384) id 15.20.3477.20; Wed, 21 Oct 2020 09:03:05 +0000
Received: from AM5EUR03FT055.eop-EUR03.prod.protection.outlook.com (2603:10a6:205:2:cafe::44) by AM4PR0302CA0019.outlook.office365.com (2603:10a6:205:2::32) with Microsoft SMTP Server (version=TLS1_2, cipher=TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384) id 15.20.3499.18 via Frontend Transport; Wed, 21 Oct 2020 09:03:04 +0000
X-MS-Exchange-Authentication-Results: spf=pass (sender IP is 63.35.35.123) smtp.mailfrom=arm.com; ietf.org; dkim=pass (signature was verified) header.d=armh.onmicrosoft.com;ietf.org; dmarc=pass action=none header.from=arm.com;
Received-SPF: Pass (protection.outlook.com: domain of arm.com designates 63.35.35.123 as permitted sender) receiver=protection.outlook.com; client-ip=63.35.35.123; helo=64aa7808-outbound-1.mta.getcheckrecipient.com;
Received: from 64aa7808-outbound-1.mta.getcheckrecipient.com (63.35.35.123) by AM5EUR03FT055.mail.protection.outlook.com (10.152.17.214) with Microsoft SMTP Server (version=TLS1_2, cipher=TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384) id 15.20.3499.18 via Frontend Transport; Wed, 21 Oct 2020 09:03:04 +0000
Received: ("Tessian outbound 68da730eaaba:v64"); Wed, 21 Oct 2020 09:03:04 +0000
X-CR-MTA-TID: 64aa7808
Received: from f027c25dc247.1 by 64aa7808-outbound-1.mta.getcheckrecipient.com id 8F25F932-1028-4710-A308-F68C03F4C007.1;  Wed, 21 Oct 2020 09:02:59 +0000
Received: from EUR03-VE1-obe.outbound.protection.outlook.com by 64aa7808-outbound-1.mta.getcheckrecipient.com with ESMTPS id f027c25dc247.1 (version=TLSv1.2 cipher=ECDHE-RSA-AES256-GCM-SHA384); Wed, 21 Oct 2020 09:02:59 +0000
ARC-Seal: i=1; a=rsa-sha256; s=arcselector9901; d=microsoft.com; cv=none; b=h+64qQd4hiGjm3D3tcDjnoneWG7ICkOB0hxJDIZd1ilqwHf7GzR7vyufmI9371H73tGFBt+0OeC5XqhMvDK3BZGbYhiOlG5ldWu8OEc88TagJy5n+hxxYbwOZ6OpJhuhZlQMGyGEJOhON1sNLar84N2TQ17NFe37snzun/IdV1oQ/BOoym85L/tCulcsawbWZ70VI+2HaKi1h11RRQHxyU22E0UL23ZGdV7QyASVoAAdwE2Lqkx6Z8JNKn6TGxEh2G4YB36i4raYZZ3K/ePOMEBNFp77BlyjwENMxtd9cxTl7FtKYZV+NNW0yH5FrXAGymgIdRVjzYBz4Qi1I2msbQ==
ARC-Message-Signature: i=1; a=rsa-sha256; c=relaxed/relaxed; d=microsoft.com;  s=arcselector9901; h=From:Date:Subject:Message-ID:Content-Type:MIME-Version:X-MS-Exchange-SenderADCheck; bh=xyzGo4UstawCVSSc+8zHK6xOTWIpnrt0ZfQv0wwyrF0=; b=VOo9kdgGFgIg+dlVPQJP2c1+mZWKivpYwa9o59jLB81VXnV/WJ/l9KzOq7EwzzMr4MswPMaGaTGAAes18CsEMoyikO8e3EEudcMnig1sYTnr4zQt6PZ3mKcbIhwQZwgVdVlWrwAWqC+Ip3SQo5WhvI3ApsGXmEUSJ847fLyonvGgiF4VTJftLO3lSrqedyBPcPKG5v0TduznQFRL2/jFPKrS6C2nBmlhRIuHTAJMA09tiFkDYMcu1x/Go4E/G9f5wYxW4bfvUYXv5ThB+pkYER7u4pBZhl54eS/NPuIN0d2fmF/sHhOej5tAt1KT1n0rkeSY62UGeqtYna3xWaX5Zg==
ARC-Authentication-Results: i=1; mx.microsoft.com 1; spf=pass smtp.mailfrom=arm.com; dmarc=pass action=none header.from=arm.com; dkim=pass header.d=arm.com; arc=none
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=armh.onmicrosoft.com;  s=selector2-armh-onmicrosoft-com; h=From:Date:Subject:Message-ID:Content-Type:MIME-Version:X-MS-Exchange-SenderADCheck; bh=xyzGo4UstawCVSSc+8zHK6xOTWIpnrt0ZfQv0wwyrF0=; b=MQkYLASpH+Rnp2aqP5aTk8xQ0tUZacIte1YI7t3x7m/0RSdYRDYcmJtgK2bLWWaUq9z7mBWIOEYMGsucEjml5W0hPU57xVKmGA+2WMTH2SLVE3xE3xQZluF56wGe5Kc/bBm8rZsq+cvxkr+FceJ1dUjgTStIG3kvJnJDZtxQPs8=
Received: from AM0PR08MB3716.eurprd08.prod.outlook.com (2603:10a6:208:106::13) by AM0PR08MB3796.eurprd08.prod.outlook.com (2603:10a6:208:100::13) with Microsoft SMTP Server (version=TLS1_2, cipher=TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384) id 15.20.3499.18; Wed, 21 Oct 2020 09:02:55 +0000
Received: from AM0PR08MB3716.eurprd08.prod.outlook.com ([fe80::900e:c64d:a006:4860]) by AM0PR08MB3716.eurprd08.prod.outlook.com ([fe80::900e:c64d:a006:4860%6]) with mapi id 15.20.3455.037; Wed, 21 Oct 2020 09:02:55 +0000
From: Hannes Tschofenig <Hannes.Tschofenig@arm.com>
To: "emu@ietf.org" <emu@ietf.org>
Thread-Topic: draft-ietf-emu-eap-tls13-11: OCSP Stapling
Thread-Index: AdaniLvyfaHHD0ANRluj1nshuTAidQ==
Date: Wed, 21 Oct 2020 09:02:55 +0000
Message-ID: <AM0PR08MB371647618F993B8C5BA6EB5FFA1C0@AM0PR08MB3716.eurprd08.prod.outlook.com>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
x-ts-tracking-id: 43ADE978393C1F488F6B2BADF6A6FE9F.0
x-checkrecipientchecked: true
Authentication-Results-Original: ietf.org; dkim=none (message not signed) header.d=none;ietf.org; dmarc=none action=none header.from=arm.com;
x-originating-ip: [156.67.196.116]
x-ms-publictraffictype: Email
X-MS-Office365-Filtering-HT: Tenant
X-MS-Office365-Filtering-Correlation-Id: 6bacdd74-d0e1-49f9-5b9c-08d875a01f08
x-ms-traffictypediagnostic: AM0PR08MB3796:|VE1PR08MB5615:
X-Microsoft-Antispam-PRVS: <VE1PR08MB5615C8F98B5C22474F20E829FA1C0@VE1PR08MB5615.eurprd08.prod.outlook.com>
x-checkrecipientrouted: true
nodisclaimer: true
x-ms-oob-tlc-oobclassifiers: OLM:6108;OLM:9508;
X-MS-Exchange-SenderADCheck: 1
X-Microsoft-Antispam-Untrusted: BCL:0;
X-Microsoft-Antispam-Message-Info-Original: nib0hmxLqN3NG3bxhr56t6GeXOr/FkGmmb5/eokKd9Q8rQvl04a9ADQIj1SlPep7I6PF3YisA2mJKt0uNqnkCW5Q7eoCGH5SiebMQq8MEl6sFNnXdUxTeD8lFhPywSXu/8N7cd7+sB2KK6ILnZm+zpv+Er/jrrkQ7ZvTvTa92ekIkaoBsEAFHiHqSgXPp+x3Mz64Jc8onaq6u/qO/V2vAtRxqPp66mwL5XTgMz5q6gol5SECO9yIal7uurIi0lShU9Qw4xfCTxLrDHhAxlklVK3sU8zrc6HELEMt11xwFPgyqpy+AztO/TvZG9eUV41B1idJ0Az2bGhGVIGj4mrmcw==
X-Forefront-Antispam-Report-Untrusted: CIP:255.255.255.255; CTRY:; LANG:en; SCL:1; SRV:; IPV:NLI; SFV:NSPM; H:AM0PR08MB3716.eurprd08.prod.outlook.com; PTR:; CAT:NONE; SFS:(4636009)(376002)(346002)(366004)(396003)(136003)(39860400002)(55016002)(316002)(186003)(6506007)(26005)(478600001)(7696005)(33656002)(86362001)(8936002)(2906002)(76116006)(71200400001)(6916009)(8676002)(66446008)(64756008)(66556008)(66946007)(5660300002)(9686003)(52536014)(66476007)(83380400001); DIR:OUT; SFP:1101; 
x-ms-exchange-antispam-messagedata: 6ouE7E24YlA0UVG/0uBbZvYUuhoS7s2Pdur0Hy7pIn4B2/WRJD82wwFa7I2lyqm7ZBh8YcPrIOh5p1LPl1C2TUA8VuBUYcPPWy9sLa/hPHSftS6kW+q/xk3nB8PdLAwc0CtegVxD8ooQv37hwahW5P3SWG6EzjZOptg1vbbc3/Rc7dHzShbWbPZRiD9dxFCqcROvvSwaRaWdDeF6PL15s7yCC9Y6GSblq7nZ6XtHejWW7d/JGMsLZ0YvD+yacaV+ygaiLMCpRxDO+wylJOd9JZjHGf6L1LTjoISksjGDqp8XG+TZH8Qs5BFikjTj1+NsJjHfMecN7CALSC52bJZ6HXO7BcB9vebz5HcjuCXkIS9t7+JrE9CxFt5itjtI/ysOozgwK7FvbBpWuwOR/VDqK3405Fgvx2d0ZO4zX8sv4iefugvrJVy4hsyPlwo9ka6eyIyo3vtsLAQD5qA5tyaOTKukgS2gAJ3kWVriU4ckRaKhhkyhoOl6qaENHsJpw+VpOsqQoWSu3hrXSbW3gEO8B97eQSPkyNYPtOgI5EtPNAki4/pcP588ZvB1wZOVAQ+yPZVPDPl4YlrWUIID8eyIZv1Hd9XHmUa78A+71NPNePqb0IuB0tRbHK/Z8dvmm4ASk4btvrCVGMlVL3hWj/mlgA==
x-ms-exchange-transport-forked: True
Content-Type: multipart/alternative; boundary="_000_AM0PR08MB371647618F993B8C5BA6EB5FFA1C0AM0PR08MB3716eurp_"
MIME-Version: 1.0
X-MS-Exchange-Transport-CrossTenantHeadersStamped: AM0PR08MB3796
Original-Authentication-Results: ietf.org; dkim=none (message not signed) header.d=none;ietf.org; dmarc=none action=none header.from=arm.com;
X-EOPAttributedMessage: 0
X-MS-Exchange-Transport-CrossTenantHeadersStripped: AM5EUR03FT055.eop-EUR03.prod.protection.outlook.com
X-MS-Office365-Filtering-Correlation-Id-Prvs: 286aa278-4f1a-4eb9-2771-08d875a0199c
X-Microsoft-Antispam: BCL:0;
X-Microsoft-Antispam-Message-Info: X8NWDMTmERQkspJy8IHMu9Ly/7NaQa73QOqyJn0AqVs/nH3/p3Ia3CyVyTs1XzoYNpDe+IlbPp5xBsweaSY+nOl5rrNQUmgYIfYPoEkCR5Di0BHFdY1oeryHlFUi0SZeWh2rGURje4m/SZch+6ZNKLGw232VHDxNZ6gThKp5xjBQHOQeVLDpf1rb8dd7bJEjmr8I7D+OoP2v5auDWvszMbeWvUw+LB/UzVsFSoXOvIH+IpFHwOyo0dJXBGnNc70McHGPJ41JSq+NUBkMDORQQrBuuw5l88HVHfCYuw3JD/6XGAr89KTJMC+RFw7BFgfUqw1w5+itMiC65UQzTMr2zlzM3fv6hE0a/zI5tAvYOLtWFRYpxoTZ/hcmimGxZu/JIN6H892rCqoSwcd3uXJJsw==
X-Forefront-Antispam-Report: CIP:63.35.35.123; CTRY:IE; LANG:en; SCL:1; SRV:;  IPV:CAL; SFV:NSPM; H:64aa7808-outbound-1.mta.getcheckrecipient.com;  PTR:ec2-63-35-35-123.eu-west-1.compute.amazonaws.com; CAT:NONE; SFS:(4636009)(136003)(376002)(346002)(396003)(39860400002)(46966005)(6916009)(7696005)(47076004)(9686003)(8676002)(5660300002)(8936002)(2906002)(70206006)(70586007)(52536014)(336012)(26005)(6506007)(83380400001)(356005)(55016002)(186003)(36906005)(33656002)(82310400003)(86362001)(82740400003)(478600001)(81166007)(316002); DIR:OUT; SFP:1101; 
X-OriginatorOrg: arm.com
X-MS-Exchange-CrossTenant-OriginalArrivalTime: 21 Oct 2020 09:03:04.8204 (UTC)
X-MS-Exchange-CrossTenant-Network-Message-Id: 6bacdd74-d0e1-49f9-5b9c-08d875a01f08
X-MS-Exchange-CrossTenant-Id: f34e5979-57d9-4aaa-ad4d-b122a662184d
X-MS-Exchange-CrossTenant-OriginalAttributedTenantConnectingIp: TenantId=f34e5979-57d9-4aaa-ad4d-b122a662184d; Ip=[63.35.35.123];  Helo=[64aa7808-outbound-1.mta.getcheckrecipient.com]
X-MS-Exchange-CrossTenant-AuthSource: AM5EUR03FT055.eop-EUR03.prod.protection.outlook.com
X-MS-Exchange-CrossTenant-AuthAs: Anonymous
X-MS-Exchange-CrossTenant-FromEntityHeader: HybridOnPrem
X-MS-Exchange-Transport-CrossTenantHeadersStamped: VE1PR08MB5615
Archived-At: <https://mailarchive.ietf.org/arch/msg/emu/jsfk-SEIWEcQ486ClJKmCNqR11U>
Subject: [Emu] draft-ietf-emu-eap-tls13-11: OCSP Stapling
X-BeenThere: emu@ietf.org
X-Mailman-Version: 2.1.29
Precedence: list
List-Id: "EAP Methods Update \(EMU\)" <emu.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/emu>, <mailto:emu-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/emu/>
List-Post: <mailto:emu@ietf.org>
List-Help: <mailto:emu-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/emu>, <mailto:emu-request@ietf.org?subject=subscribe>
X-List-Received-Date: Wed, 21 Oct 2020 09:03:10 -0000

--_000_AM0PR08MB371647618F993B8C5BA6EB5FFA1C0AM0PR08MB3716eurp_
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: quoted-printable

Hi all,

this draft mandates OCSCP stapling (for use with TLS 1.3 in EAP-TLS) and I =
believe this is a problem for implementations. This extra burden is IMHO un=
justified. For the type of deployments where EAP is used there is no need f=
or a mandatory certificate revocation checking with OCSP.

Having it optional, like the use of many other TLS extensions, is fine for =
me. FWIW even TLS 1.3, which is used in a more generic environment, does no=
t mandate the use of OCSP stapling.

This requirement will make the problem described in draft-ietf-emu-eaptlsce=
rt worse. I am sure the authors are aware of this fact since they are also =
co-authors of draft-ietf-emu-eaptlscert.

Ciao
Hannes
IMPORTANT NOTICE: The contents of this email and any attachments are confid=
ential and may also be privileged. If you are not the intended recipient, p=
lease notify the sender immediately and do not disclose the contents to any=
 other person, use it for any purpose, or store or copy the information in =
any medium. Thank you.

--_000_AM0PR08MB371647618F993B8C5BA6EB5FFA1C0AM0PR08MB3716eurp_
Content-Type: text/html; charset="us-ascii"
Content-Transfer-Encoding: quoted-printable

<html xmlns:v=3D"urn:schemas-microsoft-com:vml" xmlns:o=3D"urn:schemas-micr=
osoft-com:office:office" xmlns:w=3D"urn:schemas-microsoft-com:office:word" =
xmlns:m=3D"http://schemas.microsoft.com/office/2004/12/omml" xmlns=3D"http:=
//www.w3.org/TR/REC-html40">
<head>
<meta http-equiv=3D"Content-Type" content=3D"text/html; charset=3Dus-ascii"=
>
<meta name=3D"Generator" content=3D"Microsoft Word 15 (filtered medium)">
<style><!--
/* Font Definitions */
@font-face
	{font-family:"Cambria Math";
	panose-1:2 4 5 3 5 4 6 3 2 4;}
@font-face
	{font-family:DengXian;
	panose-1:2 1 6 0 3 1 1 1 1 1;}
@font-face
	{font-family:Calibri;
	panose-1:2 15 5 2 2 2 4 3 2 4;}
@font-face
	{font-family:"\@DengXian";
	panose-1:2 1 6 0 3 1 1 1 1 1;}
/* Style Definitions */
p.MsoNormal, li.MsoNormal, div.MsoNormal
	{margin:0in;
	font-size:11.0pt;
	font-family:"Calibri",sans-serif;}
span.EmailStyle17
	{mso-style-type:personal-compose;
	font-family:"Calibri",sans-serif;
	color:windowtext;}
.MsoChpDefault
	{mso-style-type:export-only;
	font-family:"Calibri",sans-serif;}
@page WordSection1
	{size:8.5in 11.0in;
	margin:1.0in 1.0in 1.0in 1.0in;}
div.WordSection1
	{page:WordSection1;}
--></style><!--[if gte mso 9]><xml>
<o:shapedefaults v:ext=3D"edit" spidmax=3D"1026" />
</xml><![endif]--><!--[if gte mso 9]><xml>
<o:shapelayout v:ext=3D"edit">
<o:idmap v:ext=3D"edit" data=3D"1" />
</o:shapelayout></xml><![endif]-->
</head>
<body lang=3D"EN-US" link=3D"#0563C1" vlink=3D"#954F72">
<div class=3D"WordSection1">
<p class=3D"MsoNormal">Hi all, <o:p></o:p></p>
<p class=3D"MsoNormal"><o:p>&nbsp;</o:p></p>
<p class=3D"MsoNormal">this draft mandates OCSCP stapling (for use with TLS=
 1.3 in EAP-TLS) and I believe this is a problem for implementations. This =
extra burden is IMHO unjustified. For the type of deployments where EAP is =
used there is no need for a mandatory
 certificate revocation checking with OCSP.<o:p></o:p></p>
<p class=3D"MsoNormal"><o:p>&nbsp;</o:p></p>
<p class=3D"MsoNormal">Having it optional, like the use of many other TLS e=
xtensions, is fine for me. FWIW even TLS 1.3, which is used in a more gener=
ic environment, does not mandate the use of OCSP stapling.
<o:p></o:p></p>
<p class=3D"MsoNormal"><o:p>&nbsp;</o:p></p>
<p class=3D"MsoNormal">This requirement will make the problem described in =
draft-ietf-emu-eaptlscert worse. I am sure the authors are aware of this fa=
ct since they are also co-authors of draft-ietf-emu-eaptlscert.<o:p></o:p><=
/p>
<p class=3D"MsoNormal"><o:p>&nbsp;</o:p></p>
<p class=3D"MsoNormal">Ciao<o:p></o:p></p>
<p class=3D"MsoNormal">Hannes<o:p></o:p></p>
</div>
IMPORTANT NOTICE: The contents of this email and any attachments are confid=
ential and may also be privileged. If you are not the intended recipient, p=
lease notify the sender immediately and do not disclose the contents to any=
 other person, use it for any purpose,
 or store or copy the information in any medium. Thank you.
</body>
</html>

--_000_AM0PR08MB371647618F993B8C5BA6EB5FFA1C0AM0PR08MB3716eurp_--


From nobody Wed Oct 21 02:08:06 2020
Return-Path: <Hannes.Tschofenig@arm.com>
X-Original-To: emu@ietfa.amsl.com
Delivered-To: emu@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id D2EAB3A13D3 for <emu@ietfa.amsl.com>; Wed, 21 Oct 2020 02:08:04 -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, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, HTML_MESSAGE=0.001, RCVD_IN_MSPIKE_H2=-0.001, SPF_PASS=-0.001, UNPARSEABLE_RELAY=0.001] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (1024-bit key) header.d=armh.onmicrosoft.com header.b=PWN+wsKZ; dkim=pass (1024-bit key) header.d=armh.onmicrosoft.com header.b=PWN+wsKZ
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 nsfZktdwQ_6o for <emu@ietfa.amsl.com>; Wed, 21 Oct 2020 02:08:03 -0700 (PDT)
Received: from EUR01-DB5-obe.outbound.protection.outlook.com (mail-eopbgr150049.outbound.protection.outlook.com [40.107.15.49]) (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 7F8573A13D4 for <emu@ietf.org>; Wed, 21 Oct 2020 02:08:02 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=armh.onmicrosoft.com;  s=selector2-armh-onmicrosoft-com; h=From:Date:Subject:Message-ID:Content-Type:MIME-Version:X-MS-Exchange-SenderADCheck; bh=GYa5N2z/XNCzuJXMGoTo8IE4ngz2ix01/9ngyChwZyw=; b=PWN+wsKZMxjkCBiAf7y7Gp4Rni/wGHXy+qqn/UN8RVBi+Fm70OLCsgB7Asw1+681vQ4oO+m3gAdtWmh848fYwrPyblHeK8rH4vThIGmP1lMSA2DimBqhqm4YU2fn9Ad6L8u52qgtmaH+WY0pnWaxp2n3dE5m+G1tdWT60gta+zE=
Received: from DB6PR1001CA0025.EURPRD10.PROD.OUTLOOK.COM (2603:10a6:4:55::11) by AM6PR08MB3047.eurprd08.prod.outlook.com (2603:10a6:209:4c::23) with Microsoft SMTP Server (version=TLS1_2, cipher=TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384) id 15.20.3499.18; Wed, 21 Oct 2020 09:07:59 +0000
Received: from DB5EUR03FT045.eop-EUR03.prod.protection.outlook.com (2603:10a6:4:55:cafe::8a) by DB6PR1001CA0025.outlook.office365.com (2603:10a6:4:55::11) with Microsoft SMTP Server (version=TLS1_2, cipher=TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384) id 15.20.3499.18 via Frontend Transport; Wed, 21 Oct 2020 09:07:59 +0000
X-MS-Exchange-Authentication-Results: spf=pass (sender IP is 63.35.35.123) smtp.mailfrom=arm.com; ietf.org; dkim=pass (signature was verified) header.d=armh.onmicrosoft.com;ietf.org; dmarc=pass action=none header.from=arm.com;
Received-SPF: Pass (protection.outlook.com: domain of arm.com designates 63.35.35.123 as permitted sender) receiver=protection.outlook.com; client-ip=63.35.35.123; helo=64aa7808-outbound-1.mta.getcheckrecipient.com;
Received: from 64aa7808-outbound-1.mta.getcheckrecipient.com (63.35.35.123) by DB5EUR03FT045.mail.protection.outlook.com (10.152.21.164) with Microsoft SMTP Server (version=TLS1_2, cipher=TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384) id 15.20.3499.18 via Frontend Transport; Wed, 21 Oct 2020 09:07:59 +0000
Received: ("Tessian outbound c579d876a324:v64"); Wed, 21 Oct 2020 09:07:59 +0000
X-CR-MTA-TID: 64aa7808
Received: from ae7d711858eb.1 by 64aa7808-outbound-1.mta.getcheckrecipient.com id A13E7880-1D66-4858-9FE7-148BA7343FB8.1;  Wed, 21 Oct 2020 09:07:54 +0000
Received: from EUR02-VE1-obe.outbound.protection.outlook.com by 64aa7808-outbound-1.mta.getcheckrecipient.com with ESMTPS id ae7d711858eb.1 (version=TLSv1.2 cipher=ECDHE-RSA-AES256-GCM-SHA384); Wed, 21 Oct 2020 09:07:54 +0000
ARC-Seal: i=1; a=rsa-sha256; s=arcselector9901; d=microsoft.com; cv=none; b=LRF9HjXak67qGjFqgJ5fo9+6Y16s622AVa153hI1YVgN+QCD/EvJpYQyGGM4GvQ53nMW6T5He/9cJKgiKrNjTwKHB1SElZRzKvtUpljYNjzT1kBS2AbZgUmBBAtfFE5mamnbhGlVJqQ3QVD/nP068hj+3wTwRwW0+zX9LPHglBEbmuZB0canMXf9SUvZA0NAZpp1NFY0N5xzPhcgKOuU0SKweX3EnhZhpJ8UGfUIr6vfMhRoMNELkvvXQPglZNxUowr/pzy7G1P0mtambkP3BVmCMRsqud0KsOtFIzrfFuwXCKPLrp8OltVdytjaOmEPL+qLhkhJMzqcA695IR8FVw==
ARC-Message-Signature: i=1; a=rsa-sha256; c=relaxed/relaxed; d=microsoft.com;  s=arcselector9901; h=From:Date:Subject:Message-ID:Content-Type:MIME-Version:X-MS-Exchange-SenderADCheck; bh=GYa5N2z/XNCzuJXMGoTo8IE4ngz2ix01/9ngyChwZyw=; b=B7uWf+kXMs0gPE2xebrmu9qV3UT5jEroPH4aaIIhN9ITopIvmNfjn7AWdZ9+medmQgxOGcTOjAW/uS74K/fznpJKZ2gaOLqOa8vKGr3kfUXxuwOHVG3/WIi8Z09/QI0fR1oxIXZ3u0d6D+X24/HgNOVlMV1+BzO51ucpEvk1spPPSz5C6paxbLxgQn+WJ5Ir/V9NQ4awwtZ8drGZ7V//D6SoygV8mMtbI/avhjtsBSwzHgCyEehN1UvCUfLhtpRIBQG7yAKfuemEqGKJLcPRhEWZX1UFKSr0x+fMjImJhnc0feUdhyj0qvxcw6F5Vjs0X3grRTBRD2jTQsRp7QChUg==
ARC-Authentication-Results: i=1; mx.microsoft.com 1; spf=pass smtp.mailfrom=arm.com; dmarc=pass action=none header.from=arm.com; dkim=pass header.d=arm.com; arc=none
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=armh.onmicrosoft.com;  s=selector2-armh-onmicrosoft-com; h=From:Date:Subject:Message-ID:Content-Type:MIME-Version:X-MS-Exchange-SenderADCheck; bh=GYa5N2z/XNCzuJXMGoTo8IE4ngz2ix01/9ngyChwZyw=; b=PWN+wsKZMxjkCBiAf7y7Gp4Rni/wGHXy+qqn/UN8RVBi+Fm70OLCsgB7Asw1+681vQ4oO+m3gAdtWmh848fYwrPyblHeK8rH4vThIGmP1lMSA2DimBqhqm4YU2fn9Ad6L8u52qgtmaH+WY0pnWaxp2n3dE5m+G1tdWT60gta+zE=
Received: from AM0PR08MB3716.eurprd08.prod.outlook.com (2603:10a6:208:106::13) by AM0PR08MB3796.eurprd08.prod.outlook.com (2603:10a6:208:100::13) with Microsoft SMTP Server (version=TLS1_2, cipher=TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384) id 15.20.3499.18; Wed, 21 Oct 2020 09:07:52 +0000
Received: from AM0PR08MB3716.eurprd08.prod.outlook.com ([fe80::900e:c64d:a006:4860]) by AM0PR08MB3716.eurprd08.prod.outlook.com ([fe80::900e:c64d:a006:4860%6]) with mapi id 15.20.3455.037; Wed, 21 Oct 2020 09:07:52 +0000
From: Hannes Tschofenig <Hannes.Tschofenig@arm.com>
To: "emu@ietf.org" <emu@ietf.org>
Thread-Topic: draft-ietf-emu-eap-tls13-11: Editorial
Thread-Index: AdaniaYL3ecaRhcmSsm4XGBn4bu3fQ==
Date: Wed, 21 Oct 2020 09:07:52 +0000
Message-ID: <AM0PR08MB3716ADBBC1CEA32F119E3715FA1C0@AM0PR08MB3716.eurprd08.prod.outlook.com>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
x-ts-tracking-id: 96FD25BC6566C14BBA15B40C07E2A0DF.0
x-checkrecipientchecked: true
Authentication-Results-Original: ietf.org; dkim=none (message not signed) header.d=none;ietf.org; dmarc=none action=none header.from=arm.com;
x-originating-ip: [156.67.196.116]
x-ms-publictraffictype: Email
X-MS-Office365-Filtering-HT: Tenant
X-MS-Office365-Filtering-Correlation-Id: 4e3407b6-ade2-4e98-c78b-08d875a0ceb1
x-ms-traffictypediagnostic: AM0PR08MB3796:|AM6PR08MB3047:
X-Microsoft-Antispam-PRVS: <AM6PR08MB3047DD8F4CCF132384D12D07FA1C0@AM6PR08MB3047.eurprd08.prod.outlook.com>
x-checkrecipientrouted: true
nodisclaimer: true
x-ms-oob-tlc-oobclassifiers: OLM:9508;OLM:10000;
X-MS-Exchange-SenderADCheck: 1
X-Microsoft-Antispam-Untrusted: BCL:0;
X-Microsoft-Antispam-Message-Info-Original: iy3m1x1sunwtmpdfVncqXDqVuyvhbHY7IJmGHJzpdgJBqbSdapTft6LXS+MHYegeQv/BTtX78bSgSpgg5NcaS4aCfF07ln+UDI8OVJ+hAGJUascVajVWWc4nC+/vDNnV3azB+ihi4r/GwisHULAkXSddQsCPuaC/6rLvJinwjxEq7aorsfiwrs//mLF/B2U5FqhSpTjQNeDjp98yh7oAhwzs6gkL7sPyiuGsiw9uPWSVfvkct49+3hvKrveEdaM2GIRArQ249a6nf2jXM46r2s2OvOyDu/cOwB3xVPWkR4fxIYlLlXN2LZJboXzRKTeftvyweoutp/OFjPxmjpI49g==
X-Forefront-Antispam-Report-Untrusted: CIP:255.255.255.255; CTRY:; LANG:en; SCL:1; SRV:; IPV:NLI; SFV:NSPM; H:AM0PR08MB3716.eurprd08.prod.outlook.com; PTR:; CAT:NONE; SFS:(4636009)(376002)(346002)(366004)(396003)(136003)(39860400002)(55016002)(316002)(186003)(6506007)(26005)(478600001)(7696005)(33656002)(86362001)(8936002)(2906002)(76116006)(71200400001)(6916009)(8676002)(66446008)(64756008)(66556008)(66946007)(5660300002)(9686003)(52536014)(66476007)(83380400001); DIR:OUT; SFP:1101; 
x-ms-exchange-antispam-messagedata: sDCd1d56JSEAGqvayKmZOD8hJTjA/XucvkIf37BPSi+TU4DZG0TGmKqsY+3/N4KdsqhA9rXHLEzBwxNAGcFjvYZPDLJ3q5fQJO9Rc8OuWQT7Crm7TxXQddzU3zN7ru7NKzoe5FnJOuTt+r8z3dgjUx9GY9u9bGOPkWVOVyf3jXgSHiqS9OU+SO0cKgA28gK0j3K02LN+ybg0bW30oK5CH4YLwCU1vlw5Bog3mmRVFsieI3gur0edRBPJFEYatMCGdmFQgcDuBU88ZTkwFOk62JpebLXrWqMSZOffgFFU07GW45iuUhbml3EV2Ilr/9Nlm0tavGNnNmMUoFApYrR71xVC4TQK336pJ2F7pxlewgZhFAT74L06IrEUOD504MiQu4PEFr/xp8PhK+2iCD2QqzuDkenxyoVlDyEd83VGFJhn2EWyBIorxzQiuxHCwE4m6L221gAuqb0XuFi+7TND20R3Gnn7XfKICYKaRlLHZgHTiBskMNLwMweWaNwwvRitlGLbTFBFI5I5c2CK6SOWDY/pHVmpfMDyrL6EbeUayEM+FzxbRPcrfQnj3ENP8ihBVOvzaPdVpCcCCddGeU/5NflHjzw5ZOuSZmnvZvVwC1jhhcU+VO4hrkurXhKGH0u2h3ICzi4I1qgoFHrzzn23YA==
x-ms-exchange-transport-forked: True
Content-Type: multipart/alternative; boundary="_000_AM0PR08MB3716ADBBC1CEA32F119E3715FA1C0AM0PR08MB3716eurp_"
MIME-Version: 1.0
X-MS-Exchange-Transport-CrossTenantHeadersStamped: AM0PR08MB3796
Original-Authentication-Results: ietf.org; dkim=none (message not signed) header.d=none;ietf.org; dmarc=none action=none header.from=arm.com;
X-EOPAttributedMessage: 0
X-MS-Exchange-Transport-CrossTenantHeadersStripped: DB5EUR03FT045.eop-EUR03.prod.protection.outlook.com
X-MS-Office365-Filtering-Correlation-Id-Prvs: 449fc558-2af3-41ac-b719-08d875a0caa8
X-Microsoft-Antispam: BCL:0;
X-Microsoft-Antispam-Message-Info: DqMVINUo1FNNfwHcSnpMBnb7a3MyXX61NxahG2ajXjpvmPZkYgaJZDipFBs+2lxmvVU0JmAtIOJyj1dpSpjL6qFHEodpEKPAYev9+FqDe5s72iaYE99+pQo3PO8j79ReQC46ZiaY9m5lr9EyiwPt/PYVDa01kS4x7OhmrpVR8E5OMct9beEVN99mlZi79SQt5jz9PHvbJp0V5J17dR8y1S+WamJiwfhW0H7bReY0Wt6TdBVdFYS7yNo8N3YBSfMqvLZgwmT19JzW1ZpFb98XtdL/xCiCs1dcnMD0bvPB2sLXKqRTpKM0Zv1Vc16li30erVgUBJRAOCJ4YWmKeYdceEyQ2XBlRvGngoKa7+6WbdzjLqsSvr5/MLPPU+USXbLenFDIMFfpnzBl/CJ+eSR4VQ==
X-Forefront-Antispam-Report: CIP:63.35.35.123; CTRY:IE; LANG:en; SCL:1; SRV:;  IPV:CAL; SFV:NSPM; H:64aa7808-outbound-1.mta.getcheckrecipient.com;  PTR:ec2-63-35-35-123.eu-west-1.compute.amazonaws.com; CAT:NONE; SFS:(4636009)(39860400002)(346002)(376002)(396003)(136003)(46966005)(86362001)(336012)(6916009)(5660300002)(2906002)(8936002)(7696005)(8676002)(52536014)(316002)(82740400003)(9686003)(83380400001)(55016002)(70206006)(81166007)(70586007)(33656002)(478600001)(186003)(47076004)(26005)(82310400003)(356005)(6506007); DIR:OUT; SFP:1101; 
X-OriginatorOrg: arm.com
X-MS-Exchange-CrossTenant-OriginalArrivalTime: 21 Oct 2020 09:07:59.5699 (UTC)
X-MS-Exchange-CrossTenant-Network-Message-Id: 4e3407b6-ade2-4e98-c78b-08d875a0ceb1
X-MS-Exchange-CrossTenant-Id: f34e5979-57d9-4aaa-ad4d-b122a662184d
X-MS-Exchange-CrossTenant-OriginalAttributedTenantConnectingIp: TenantId=f34e5979-57d9-4aaa-ad4d-b122a662184d; Ip=[63.35.35.123];  Helo=[64aa7808-outbound-1.mta.getcheckrecipient.com]
X-MS-Exchange-CrossTenant-AuthSource: DB5EUR03FT045.eop-EUR03.prod.protection.outlook.com
X-MS-Exchange-CrossTenant-AuthAs: Anonymous
X-MS-Exchange-CrossTenant-FromEntityHeader: HybridOnPrem
X-MS-Exchange-Transport-CrossTenantHeadersStamped: AM6PR08MB3047
Archived-At: <https://mailarchive.ietf.org/arch/msg/emu/hHyMjcl0xr4jqpxHwXSXakGwsuE>
Subject: [Emu] draft-ietf-emu-eap-tls13-11: Editorial
X-BeenThere: emu@ietf.org
X-Mailman-Version: 2.1.29
Precedence: list
List-Id: "EAP Methods Update \(EMU\)" <emu.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/emu>, <mailto:emu-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/emu/>
List-Post: <mailto:emu@ietf.org>
List-Help: <mailto:emu-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/emu>, <mailto:emu-request@ietf.org?subject=subscribe>
X-List-Received-Date: Wed, 21 Oct 2020 09:08:05 -0000

--_000_AM0PR08MB3716ADBBC1CEA32F119E3715FA1C0AM0PR08MB3716eurp_
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: quoted-printable

Hi all,

there are lots of editorial bugs in the text. I noticed many missing commas=
, missing articles, etc.

I know that the RFC Editor does a great job in correcting all of those erro=
rs but we have to do our work as well.

It would also be good to be consistent with the terms. How do you want to w=
ant to distinguish between EAP-TLS based on RFC 5216 and EAP-TLS with TLS 1=
.3? Sometimes it is possible to understand this from the context because ce=
rtain features are not available in TLS 1.2 or have different names but it =
will help those who are less familiar with the history of TLS to be precise=
.

The terms EAP-TLS peer, EAP-TLS, and EAP peer seem to be used interchangeab=
ly. It would be good to use the terms consistently.

Here is an example from Section 5.8:

"
EAP peers SHOULD use record padding, see
   Section 5.4 of [RFC8446] to reduce information leakage of certificate
   sizes.
"

In this example the reader is asked to understand that we are not talking a=
bout the EAP layer, nor about EAP-TLS with RFC 5216 but about the client an=
d the server of EAP-TLS with TLS 1.3.

Ciao
Hannes
IMPORTANT NOTICE: The contents of this email and any attachments are confid=
ential and may also be privileged. If you are not the intended recipient, p=
lease notify the sender immediately and do not disclose the contents to any=
 other person, use it for any purpose, or store or copy the information in =
any medium. Thank you.

--_000_AM0PR08MB3716ADBBC1CEA32F119E3715FA1C0AM0PR08MB3716eurp_
Content-Type: text/html; charset="us-ascii"
Content-Transfer-Encoding: quoted-printable

<html xmlns:v=3D"urn:schemas-microsoft-com:vml" xmlns:o=3D"urn:schemas-micr=
osoft-com:office:office" xmlns:w=3D"urn:schemas-microsoft-com:office:word" =
xmlns:m=3D"http://schemas.microsoft.com/office/2004/12/omml" xmlns=3D"http:=
//www.w3.org/TR/REC-html40">
<head>
<meta http-equiv=3D"Content-Type" content=3D"text/html; charset=3Dus-ascii"=
>
<meta name=3D"Generator" content=3D"Microsoft Word 15 (filtered medium)">
<style><!--
/* Font Definitions */
@font-face
	{font-family:"Cambria Math";
	panose-1:2 4 5 3 5 4 6 3 2 4;}
@font-face
	{font-family:DengXian;
	panose-1:2 1 6 0 3 1 1 1 1 1;}
@font-face
	{font-family:Calibri;
	panose-1:2 15 5 2 2 2 4 3 2 4;}
@font-face
	{font-family:"\@DengXian";
	panose-1:2 1 6 0 3 1 1 1 1 1;}
/* Style Definitions */
p.MsoNormal, li.MsoNormal, div.MsoNormal
	{margin:0in;
	font-size:11.0pt;
	font-family:"Calibri",sans-serif;}
span.EmailStyle17
	{mso-style-type:personal-compose;
	font-family:"Calibri",sans-serif;
	color:windowtext;}
.MsoChpDefault
	{mso-style-type:export-only;
	font-family:"Calibri",sans-serif;}
@page WordSection1
	{size:8.5in 11.0in;
	margin:1.0in 1.0in 1.0in 1.0in;}
div.WordSection1
	{page:WordSection1;}
--></style><!--[if gte mso 9]><xml>
<o:shapedefaults v:ext=3D"edit" spidmax=3D"1026" />
</xml><![endif]--><!--[if gte mso 9]><xml>
<o:shapelayout v:ext=3D"edit">
<o:idmap v:ext=3D"edit" data=3D"1" />
</o:shapelayout></xml><![endif]-->
</head>
<body lang=3D"EN-US" link=3D"#0563C1" vlink=3D"#954F72">
<div class=3D"WordSection1">
<p class=3D"MsoNormal">Hi all, <o:p></o:p></p>
<p class=3D"MsoNormal"><o:p>&nbsp;</o:p></p>
<p class=3D"MsoNormal">there are lots of editorial bugs in the text. I noti=
ced many missing commas, missing articles, etc.
<o:p></o:p></p>
<p class=3D"MsoNormal"><o:p>&nbsp;</o:p></p>
<p class=3D"MsoNormal">I know that the RFC Editor does a great job in corre=
cting all of those errors but we have to do our work as well.
<o:p></o:p></p>
<p class=3D"MsoNormal"><o:p>&nbsp;</o:p></p>
<p class=3D"MsoNormal">It would also be good to be consistent with the term=
s. How do you want to want to distinguish between EAP-TLS based on RFC 5216=
 and EAP-TLS with TLS 1.3? Sometimes it is possible to understand this from=
 the context because certain features
 are not available in TLS 1.2 or have different names but it will help thos=
e who are less familiar with the history of TLS to be precise.
<o:p></o:p></p>
<p class=3D"MsoNormal"><o:p>&nbsp;</o:p></p>
<p class=3D"MsoNormal">The terms EAP-TLS peer, EAP-TLS, and EAP peer seem t=
o be used interchangeably. It would be good to use the terms consistently.
<o:p></o:p></p>
<p class=3D"MsoNormal"><o:p>&nbsp;</o:p></p>
<p class=3D"MsoNormal">Here is an example from Section 5.8:<o:p></o:p></p>
<p class=3D"MsoNormal"><o:p>&nbsp;</o:p></p>
<p class=3D"MsoNormal">&quot;<o:p></o:p></p>
<p class=3D"MsoNormal">EAP peers SHOULD use record padding, see<o:p></o:p><=
/p>
<p class=3D"MsoNormal">&nbsp;&nbsp; Section 5.4 of [RFC8446] to reduce info=
rmation leakage of certificate<o:p></o:p></p>
<p class=3D"MsoNormal">&nbsp;&nbsp; sizes.<o:p></o:p></p>
<p class=3D"MsoNormal">&quot;<o:p></o:p></p>
<p class=3D"MsoNormal"><o:p>&nbsp;</o:p></p>
<p class=3D"MsoNormal">In this example the reader is asked to understand th=
at we are not talking about the EAP layer, nor about EAP-TLS with RFC 5216 =
but about the client and the server of EAP-TLS with TLS 1.3.
<o:p></o:p></p>
<p class=3D"MsoNormal"><o:p>&nbsp;</o:p></p>
<p class=3D"MsoNormal">Ciao<o:p></o:p></p>
<p class=3D"MsoNormal">Hannes<o:p></o:p></p>
</div>
IMPORTANT NOTICE: The contents of this email and any attachments are confid=
ential and may also be privileged. If you are not the intended recipient, p=
lease notify the sender immediately and do not disclose the contents to any=
 other person, use it for any purpose,
 or store or copy the information in any medium. Thank you.
</body>
</html>

--_000_AM0PR08MB3716ADBBC1CEA32F119E3715FA1C0AM0PR08MB3716eurp_--


From nobody Wed Oct 21 02:12:20 2020
Return-Path: <Hannes.Tschofenig@arm.com>
X-Original-To: emu@ietfa.amsl.com
Delivered-To: emu@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id ADDE73A13E4 for <emu@ietfa.amsl.com>; Wed, 21 Oct 2020 02:12:18 -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, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, HTML_MESSAGE=0.001, RCVD_IN_MSPIKE_H2=-0.001, SPF_PASS=-0.001, UNPARSEABLE_RELAY=0.001] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (1024-bit key) header.d=armh.onmicrosoft.com header.b=cXyiHlmN; dkim=pass (1024-bit key) header.d=armh.onmicrosoft.com header.b=cXyiHlmN
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 cDXsmhyWuf12 for <emu@ietfa.amsl.com>; Wed, 21 Oct 2020 02:12:15 -0700 (PDT)
Received: from EUR05-AM6-obe.outbound.protection.outlook.com (mail-am6eur05on2069.outbound.protection.outlook.com [40.107.22.69]) (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 509693A13E0 for <emu@ietf.org>; Wed, 21 Oct 2020 02:12:15 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=armh.onmicrosoft.com;  s=selector2-armh-onmicrosoft-com; h=From:Date:Subject:Message-ID:Content-Type:MIME-Version:X-MS-Exchange-SenderADCheck; bh=DXtWHG2SGCG12YZwNZ+hyN94VrG5l3HgF01UyhzEmUE=; b=cXyiHlmNNiMq+7iYBn0elgeSP4crTajL5yALDcZR2cBOKh8VIi7tA5R8Qr13xOfMKTfQdGwbykn+KjqWzy1CHNc6bbt73hPkz2p/WBNnE6Qpp2rV5TQ+NhuSwKe8/tj4hfuBAwfupKga0tambY7qjHRlj0yGGnyh9tf0Rm10NNE=
Received: from DB7PR05CA0061.eurprd05.prod.outlook.com (2603:10a6:10:2e::38) by VI1PR08MB3951.eurprd08.prod.outlook.com (2603:10a6:803:e3::19) with Microsoft SMTP Server (version=TLS1_2, cipher=TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384) id 15.20.3477.20; Wed, 21 Oct 2020 09:12:12 +0000
Received: from DB5EUR03FT026.eop-EUR03.prod.protection.outlook.com (2603:10a6:10:2e:cafe::5f) by DB7PR05CA0061.outlook.office365.com (2603:10a6:10:2e::38) with Microsoft SMTP Server (version=TLS1_2, cipher=TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384) id 15.20.3499.18 via Frontend Transport; Wed, 21 Oct 2020 09:12:12 +0000
X-MS-Exchange-Authentication-Results: spf=pass (sender IP is 63.35.35.123) smtp.mailfrom=arm.com; ietf.org; dkim=pass (signature was verified) header.d=armh.onmicrosoft.com;ietf.org; dmarc=pass action=none header.from=arm.com;
Received-SPF: Pass (protection.outlook.com: domain of arm.com designates 63.35.35.123 as permitted sender) receiver=protection.outlook.com; client-ip=63.35.35.123; helo=64aa7808-outbound-1.mta.getcheckrecipient.com;
Received: from 64aa7808-outbound-1.mta.getcheckrecipient.com (63.35.35.123) by DB5EUR03FT026.mail.protection.outlook.com (10.152.20.159) with Microsoft SMTP Server (version=TLS1_2, cipher=TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384) id 15.20.3499.18 via Frontend Transport; Wed, 21 Oct 2020 09:12:12 +0000
Received: ("Tessian outbound c189680f801b:v64"); Wed, 21 Oct 2020 09:12:12 +0000
X-CR-MTA-TID: 64aa7808
Received: from 3f3cb0477d35.1 by 64aa7808-outbound-1.mta.getcheckrecipient.com id CC11765E-6299-48AF-BF69-02A04308209E.1;  Wed, 21 Oct 2020 09:12:07 +0000
Received: from EUR04-VI1-obe.outbound.protection.outlook.com by 64aa7808-outbound-1.mta.getcheckrecipient.com with ESMTPS id 3f3cb0477d35.1 (version=TLSv1.2 cipher=ECDHE-RSA-AES256-GCM-SHA384); Wed, 21 Oct 2020 09:12:07 +0000
ARC-Seal: i=1; a=rsa-sha256; s=arcselector9901; d=microsoft.com; cv=none; b=Dt/ENOGM2fLpTdEEvLyC74nQlzX/0N61sbBHvlAuGAOxAn+gav0N0fqORYqVuIDP93IymHgQg2vM/0qac4j8wcy0wcqoH6r/wWQrNoqRgYQA4+PM2BSBvixEENgTyreemjLoM+JKZTflLPTTw51L0GLkCJXd8AhkaFaw1lfqckuajIzasfDE9z+afdfg77T/u4i+7+HFCli3rCo4y3TEJOlPlhGwhF5DKzhpeBO2J2UXuaJ+cQ2gbTcPNvgTIku3ZUKF+0yq3FxeidVGGA9mmKbMG5+Uacz34hAqfcpMA6lN9s0Pwh/VoC+zOU9AigjsGzGqOh8umHeZ3ysq6J0XbQ==
ARC-Message-Signature: i=1; a=rsa-sha256; c=relaxed/relaxed; d=microsoft.com;  s=arcselector9901; h=From:Date:Subject:Message-ID:Content-Type:MIME-Version:X-MS-Exchange-SenderADCheck; bh=DXtWHG2SGCG12YZwNZ+hyN94VrG5l3HgF01UyhzEmUE=; b=dItkfYDfKpe1lgzY96VeektNu4euqem2OtRglgi4AQdcSYEQUm6rjlQeizTfWvm7YTfxH9pTDdyOB+Uw8prkikHFEywtQ0y93OgjmrpnamRAMtujpUR3G27iWTwgcA4y9GIl+S369aU+KzmEyOTaWiAgmn3mTspXQH7BO98TdGWOdShikzoFHQMCaTNL8JuoPnipsxe3btaayuVyHMFqj3rBuU3NSyjeX/cmNSuRhH/vQQCS1/hdhyWsdDDHMil7J9d6f2ZMlqSpkTB1vBLBAMEzYlx+xSrKRE/f3/scAGkP0RFle+kJ7aoENofdAzHOMA+ZKKJHSrho+sOeFCfbow==
ARC-Authentication-Results: i=1; mx.microsoft.com 1; spf=pass smtp.mailfrom=arm.com; dmarc=pass action=none header.from=arm.com; dkim=pass header.d=arm.com; arc=none
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=armh.onmicrosoft.com;  s=selector2-armh-onmicrosoft-com; h=From:Date:Subject:Message-ID:Content-Type:MIME-Version:X-MS-Exchange-SenderADCheck; bh=DXtWHG2SGCG12YZwNZ+hyN94VrG5l3HgF01UyhzEmUE=; b=cXyiHlmNNiMq+7iYBn0elgeSP4crTajL5yALDcZR2cBOKh8VIi7tA5R8Qr13xOfMKTfQdGwbykn+KjqWzy1CHNc6bbt73hPkz2p/WBNnE6Qpp2rV5TQ+NhuSwKe8/tj4hfuBAwfupKga0tambY7qjHRlj0yGGnyh9tf0Rm10NNE=
Received: from AM0PR08MB3716.eurprd08.prod.outlook.com (2603:10a6:208:106::13) by AM8PR08MB5825.eurprd08.prod.outlook.com (2603:10a6:20b:1d6::9) with Microsoft SMTP Server (version=TLS1_2, cipher=TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384) id 15.20.3477.20; Wed, 21 Oct 2020 09:12:04 +0000
Received: from AM0PR08MB3716.eurprd08.prod.outlook.com ([fe80::900e:c64d:a006:4860]) by AM0PR08MB3716.eurprd08.prod.outlook.com ([fe80::900e:c64d:a006:4860%6]) with mapi id 15.20.3455.037; Wed, 21 Oct 2020 09:12:04 +0000
From: Hannes Tschofenig <Hannes.Tschofenig@arm.com>
To: "emu@ietf.org" <emu@ietf.org>
Thread-Topic: draft-ietf-emu-eap-tls13-11: Fuzzy statements
Thread-Index: AdanibbbNEDhzsgYS9iH1Ccd30UwCQ==
Date: Wed, 21 Oct 2020 09:12:04 +0000
Message-ID: <AM0PR08MB37166BE43DC27978FF5D2DA9FA1C0@AM0PR08MB3716.eurprd08.prod.outlook.com>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
x-ts-tracking-id: 4CB4D12163304248A4A0E6980D5C0B31.0
x-checkrecipientchecked: true
Authentication-Results-Original: ietf.org; dkim=none (message not signed) header.d=none;ietf.org; dmarc=none action=none header.from=arm.com;
x-originating-ip: [156.67.196.116]
x-ms-publictraffictype: Email
X-MS-Office365-Filtering-HT: Tenant
X-MS-Office365-Filtering-Correlation-Id: a4f6d495-da74-4fdc-8361-08d875a16531
x-ms-traffictypediagnostic: AM8PR08MB5825:|VI1PR08MB3951:
X-Microsoft-Antispam-PRVS: <VI1PR08MB3951C58DFA74434A46B78F51FA1C0@VI1PR08MB3951.eurprd08.prod.outlook.com>
x-checkrecipientrouted: true
nodisclaimer: true
x-ms-oob-tlc-oobclassifiers: OLM:10000;OLM:10000;
X-MS-Exchange-SenderADCheck: 1
X-Microsoft-Antispam-Untrusted: BCL:0;
X-Microsoft-Antispam-Message-Info-Original: LhWsuFsH9ug5WXAv6guCPWqLdiZRHwJWV58t08bscU3IRW87ljMVnRXUTRHPlyqREnivhkQMLJsC/46yDegcczkDb1dHEF/PhFBoikcAfU4LnOT2ugFkpFMcUEQuXbOyAKOAelT6X4ZOeA8SErp2BAb8Pv2Y6JxCmgixUwpMi6CB+XWHfx1Xn7AOE4g5XUNaJ4Z0Xc2gURtwd61xY/Mzft7E0JnAYmryrRMXKRnC2twwuoD2y4eCaRMVEhtW8Kc2f6+8L5cPLw40dJJ9aBpHdv5NxBjNLbV9oCJgqoRrQI5dWLIpIzEhdYasQLaMo8W0xvcCADj2qWTqai1sNHFfYA==
X-Forefront-Antispam-Report-Untrusted: CIP:255.255.255.255; CTRY:; LANG:en; SCL:1; SRV:; IPV:NLI; SFV:NSPM; H:AM0PR08MB3716.eurprd08.prod.outlook.com; PTR:; CAT:NONE; SFS:(4636009)(39860400002)(136003)(346002)(366004)(396003)(376002)(26005)(66446008)(8936002)(186003)(55016002)(83380400001)(478600001)(8676002)(86362001)(9686003)(7696005)(76116006)(66946007)(6916009)(2906002)(6506007)(66476007)(64756008)(52536014)(5660300002)(66556008)(71200400001)(316002)(33656002); DIR:OUT; SFP:1101; 
x-ms-exchange-antispam-messagedata: tzZkeXNQ6urTRgfDHqHjnGPd6wrWnh90znZoZLxXDcKBnUAvxvAatC/nJpq5CXveqns1iCje6yygGC9hs3ycFEgTABCsuxeZ4vzAGUwxn5qQ0tn0OHe+aU/ijMZlR6ty4eVQxXO9ZaI26TufUebDEyw4jwVwoMlWR6vJaZSWIFQeyO2D1rKIuHJP018z89rWOkil8INa3uPgZXoUI7R7wkT2OOPt1c21vZcThEUrbQmwD//7Uf2d1rif5unJo1aqgn/fFlVZ56XWo+8UbKQ04i3niVCKZ99YL+UR9iQvcL6mrlxa5MGR/mptHM2bjPDCjfPHEvd0BUIxHWbM4gxdtNCmZANuFTozirNxphzrXMGxjWBPJjK1nt4F53e/anR4migMLFI66ZQdq5eNR7MdwCiBeYkhu3eX/LyQBtph2RkD4BoAS+z+wdNUkxW4BfFUEmCGLIp7tcqmULObtT6pT2nSlPF9CjT/dP60yS7YL0DWumi2cJ4BvnPOJRzvD2JfNO5jeqnjBnslkWEvlnsgCODJF3RP5J5/qNN08zEboyNP+5KBPN1d0tEhRknBP+ToemwjJzKgczuQYzqaHF9DKVExh9VXFrIWKJGzGwUotxq3Iree2SMD7QYylN7yjQZ5PLaN6BmkColxS+exYmsp1w==
x-ms-exchange-transport-forked: True
Content-Type: multipart/alternative; boundary="_000_AM0PR08MB37166BE43DC27978FF5D2DA9FA1C0AM0PR08MB3716eurp_"
MIME-Version: 1.0
X-MS-Exchange-Transport-CrossTenantHeadersStamped: AM8PR08MB5825
Original-Authentication-Results: ietf.org; dkim=none (message not signed) header.d=none;ietf.org; dmarc=none action=none header.from=arm.com;
X-EOPAttributedMessage: 0
X-MS-Exchange-Transport-CrossTenantHeadersStripped: DB5EUR03FT026.eop-EUR03.prod.protection.outlook.com
X-MS-Office365-Filtering-Correlation-Id-Prvs: 6deabca6-50fd-4682-dbde-08d875a160c4
X-Microsoft-Antispam: BCL:0;
X-Microsoft-Antispam-Message-Info: BRejc/4Lmc6JoxKpJOxdTskDmJvC1sEgc1IawG1DpDolRwEN7Ybn68tHswSN7Uy07KdlPdvsXnyXxVsMNNUcO+rBzb0wH5sEO1pMwI1Ikb8b933VOm/BM6CqoU/cJPZWCwx+M7zFWa6qWwsqN0J+TjGPZsufZosr9DkdvoPugb8NLidVO6HX2toYBv8Gbf+6vmJlxuS3yCLCcOUWjAafp3wOtKrNxSaFlyEsH4UxgVKdVHJtK0tcodPVVjof2FHL/eBCs62syvcl8WhQykKNov2pMKBrID29YY5T74+Iq/BITDJjIayJTIU7ePZyBe8r9B9HbnRB623m9tfsojRDtsxoPLx5W2jrwL0pnyrMCwhFNiHtqB1jcL5CfsIhk+ON3rtQiXPIgIKM310ewJE3XQ==
X-Forefront-Antispam-Report: CIP:63.35.35.123; CTRY:IE; LANG:en; SCL:1; SRV:;  IPV:CAL; SFV:NSPM; H:64aa7808-outbound-1.mta.getcheckrecipient.com;  PTR:ec2-63-35-35-123.eu-west-1.compute.amazonaws.com; CAT:NONE; SFS:(4636009)(376002)(396003)(346002)(136003)(39860400002)(46966005)(70206006)(6506007)(33656002)(7696005)(2906002)(316002)(5660300002)(52536014)(70586007)(30864003)(81166007)(82310400003)(336012)(356005)(55016002)(186003)(26005)(6916009)(8936002)(8676002)(83380400001)(478600001)(9686003)(86362001)(47076004)(82740400003); DIR:OUT; SFP:1101; 
X-OriginatorOrg: arm.com
X-MS-Exchange-CrossTenant-OriginalArrivalTime: 21 Oct 2020 09:12:12.0773 (UTC)
X-MS-Exchange-CrossTenant-Network-Message-Id: a4f6d495-da74-4fdc-8361-08d875a16531
X-MS-Exchange-CrossTenant-Id: f34e5979-57d9-4aaa-ad4d-b122a662184d
X-MS-Exchange-CrossTenant-OriginalAttributedTenantConnectingIp: TenantId=f34e5979-57d9-4aaa-ad4d-b122a662184d; Ip=[63.35.35.123];  Helo=[64aa7808-outbound-1.mta.getcheckrecipient.com]
X-MS-Exchange-CrossTenant-AuthSource: DB5EUR03FT026.eop-EUR03.prod.protection.outlook.com
X-MS-Exchange-CrossTenant-AuthAs: Anonymous
X-MS-Exchange-CrossTenant-FromEntityHeader: HybridOnPrem
X-MS-Exchange-Transport-CrossTenantHeadersStamped: VI1PR08MB3951
Archived-At: <https://mailarchive.ietf.org/arch/msg/emu/TknZMQHNhwfpCHMuQsoVJA376hg>
Subject: [Emu] draft-ietf-emu-eap-tls13-11: Fuzzy statements
X-BeenThere: emu@ietf.org
X-Mailman-Version: 2.1.29
Precedence: list
List-Id: "EAP Methods Update \(EMU\)" <emu.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/emu>, <mailto:emu-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/emu/>
List-Post: <mailto:emu@ietf.org>
List-Help: <mailto:emu-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/emu>, <mailto:emu-request@ietf.org?subject=subscribe>
X-List-Received-Date: Wed, 21 Oct 2020 09:12:19 -0000

--_000_AM0PR08MB37166BE43DC27978FF5D2DA9FA1C0AM0PR08MB3716eurp_
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: quoted-printable

Hi all,

There are plenty of places in the draft where statements are made in a some=
what sloppy manner.

Section 5.1:

" TLS 1.3 increases the number of
  cryptographic parameters that are negotiated in the handshake.
"

Increases the number of parameters compared to what?

Section 5.1:

"
TLS 1.3 forbids all algorithms with known
   weaknesses including 3DES, CBC mode, RC4, SHA-1, and MD5.  TLS 1.3
   only supports cryptographic algorithms offering at least 112-bit
   security, see [RFC8446].
"

Most of those algorithms have been depreciated also with TLS 1.2
I would instead say that TLS 1.3 only uses AEAD ciphers.

 Section 2.5:

"
The Commitment Message is
   an encrypted TLS record with application data 0x00 (i.e. a TLS record
   with TLSPlaintext.type =3D application_data, TLSPlaintext.length =3D 1,
   and TLSPlaintext.fragment =3D 0x00).
"

Adding the note about TLSPlaintext.type, TLSPlaintext.length, and TLSPlaint=
ext.fragment is not helpful given that both plaintext TLS records as well a=
s encrypted TLS records use these structures. There is also a mistake in th=
ere because the TLSInnerPlaintext.type contains the application_data type (=
of course the TLSCiphertext.opaque_type also contains the application_data)=
.

Introduction:
"
Privacy is mandatory ...
"

It depends what you call "privacy". TLS 1.3 offers a range of features that=
 increase privacy protection but not all of them are mandatory to use. Exam=
ple: record padding

In Section 2.1.8 you talk about privacy and say:

"
   TLS 1.3 significantly improves privacy when compared to earlier
   versions of TLS by forbidding cipher suites without confidentiality
   and encrypting large parts of the TLS handshake including the
   certificate messages.
"

This list is not exhaustive when it comes to the privacy features in TLS 1.=
3, as you know. If you think it is worthwhile to highlight the privacy feat=
ures then why not list all of them?


Section 2.1.1:

"
SessionID is deprecated in TLS 1.3 and the EAP
   server SHALL ignore the legacy_session_id field if TLS 1.3 is
   negotiated.
"

This is misleading because the EAP server does not look into the TLS handsh=
ake messages.
Additionally, the session ID is not deprecated - it is a legacy feature tha=
t is used in the backwards compatibility mode.
FWIW you are not saying anything about the backwards compatibility mode and=
 hence I believe you are not using it. That's something that has to be made=
 more explicit.

Section 2.1.3:

"
The TLS PSK identity is typically derived by
   the TLS implementation and may be an opaque blob without a routable
   realm.  The TLS PSK identity is therefore in general unsuitable for
   deriving a NAI to use in the Identity Response.
"

There is no requirement in the TLS 1.3 spec that a PSK identity has to be i=
n a NAI format. Hence, most implementations will not produce one in a NAI f=
ormat. It can still be used to derive a NAI in an Identity Response if you =
stick a @realm to it at a different layer.

Section 2.1.6:

"
   TLS 1.3 [RFC8446] defines that TLS servers can send a
   HelloRetryRequest message in response to a ClientHello if the server
   finds an acceptable set of parameters but the initial ClientHello
   does not contain all the needed information to continue the
   handshake.
"

The TLS specification also says that this message can be used for DDoS miti=
gation. I think that DDoS mitigation is a valid use case in an EAP-based de=
ployment.

Section 2.1.7:

"
  Many client certificates
   contains an identity such as an email address, which is already in
   NAI format.  When the client certificate contains a NAI as subject
   name or alternative subject name, an anonymous NAI SHOULD be derived
   from the NAI in the certificate, see Section 2.1.8.
"

>From where do you get the impression that "many client certificates" contai=
n an identity, such as an email address?
Why does it matter whether the NAI is contained in the subject name or in t=
he alt subject name?
You refer to Section 2.1.8 regarding how to derive a anonymous NAI from the=
 certificate and I couldn't find the text.


"
   As the certificate messages in TLS 1.3 are encrypted, there is no
   need to send an empty certificate_list and perform a second handshake
   for privacy (as needed by EAP-TLS with earlier versions of TLS).
"

Most readers are probably not familiar with the problem you are describing =
here.
Also, this issue is not specific to EAP-TLS; the same approach has been use=
d in TLS (prior to 1.3) in general.

"   When EAP-TLS is used with TLS version 1.3 or higher the EAP-TLS peer
   and EAP-TLS server SHALL follow the processing specified by the used
   version of TLS.
"

This statement is obvious and does not say much. What else do you want to d=
o?

"
   For TLS 1.3 this means that the EAP-TLS peer only
   sends an empty certificate_list if it does not have an appropriate
   certificate to send, and the EAP-TLS server MAY treat an empty
   certificate_list as a terminal condition.
"

In Section 2.1.5 you describe the case where the EAP peer is not authentica=
ted. This is a second way in TLS to delay authentication of the client to a=
 latter phase. The approach in Section 2.1.5 was declared as acceptable wit=
h reference to emergency services but this case seems to be less acceptable=
. While both parties in TLS exchange may send an alert for a number of reas=
ons I am curious why you point this situation out.

Section 2.1.3:

"
When EAP-TLS is used with
   TLS version 1.3 or higher, EAP-TLS SHALL use a resumption mechanism
   compatible with that version of TLS.
"

This is a meaningless statement. What else do you want to do? You cannot us=
e the session resumption mechanism of TLS 1.3 in 1.2.
Section 5.8:

"
   Tracking of users by eavesdropping on identity responses or
   certificates is a well-known problem in many EAP methods.
"

I would not only focus on users because EAP methods are also used by device=
s.

Section 5.9 talks about pervasive monitoring and does not add any new conte=
nt beyond what is already said in the privacy section. Could you merge the =
two?

Section 5.10 talks about discovered vulnerabilities of earlier versions of =
TLS. It should be explicitly stated that these vulnerabilities are not abou=
t TLS 1.3. The text then goes on and says

" The use of TLS 1.3 mitigates most of the known attacks. "

Which attacks are not mitigated in TLS 1.3?


Section 2.1.9:
"
   Including ContentType and ProtocolVersion a single TLS record may be
   up to 16387 octets in length.
"

This is true if you do not use the Maximum Fragment Length Extension or the=
 Record Size Limit extension.
The question is therefore: why don't you want to use them?

Section 5.6:

"
   EAP-TLS is typically encapsulated in other protocols, such as PPP
   [RFC1661], RADIUS [RFC2865], Diameter [RFC6733], or PANA [RFC5191].
"

EAP-TLS is encapsulated into EAP, which is then encapsulated into other pro=
tocols (such as RADIUS, Diameter, etc.).


Ciao
Hannes
IMPORTANT NOTICE: The contents of this email and any attachments are confid=
ential and may also be privileged. If you are not the intended recipient, p=
lease notify the sender immediately and do not disclose the contents to any=
 other person, use it for any purpose, or store or copy the information in =
any medium. Thank you.

--_000_AM0PR08MB37166BE43DC27978FF5D2DA9FA1C0AM0PR08MB3716eurp_
Content-Type: text/html; charset="us-ascii"
Content-Transfer-Encoding: quoted-printable

<html xmlns:v=3D"urn:schemas-microsoft-com:vml" xmlns:o=3D"urn:schemas-micr=
osoft-com:office:office" xmlns:w=3D"urn:schemas-microsoft-com:office:word" =
xmlns:m=3D"http://schemas.microsoft.com/office/2004/12/omml" xmlns=3D"http:=
//www.w3.org/TR/REC-html40">
<head>
<meta http-equiv=3D"Content-Type" content=3D"text/html; charset=3Dus-ascii"=
>
<meta name=3D"Generator" content=3D"Microsoft Word 15 (filtered medium)">
<style><!--
/* Font Definitions */
@font-face
	{font-family:"Cambria Math";
	panose-1:2 4 5 3 5 4 6 3 2 4;}
@font-face
	{font-family:DengXian;
	panose-1:2 1 6 0 3 1 1 1 1 1;}
@font-face
	{font-family:Calibri;
	panose-1:2 15 5 2 2 2 4 3 2 4;}
@font-face
	{font-family:"\@DengXian";
	panose-1:2 1 6 0 3 1 1 1 1 1;}
/* Style Definitions */
p.MsoNormal, li.MsoNormal, div.MsoNormal
	{margin:0in;
	font-size:11.0pt;
	font-family:"Calibri",sans-serif;}
span.EmailStyle17
	{mso-style-type:personal-compose;
	font-family:"Calibri",sans-serif;
	color:windowtext;}
.MsoChpDefault
	{mso-style-type:export-only;
	font-family:"Calibri",sans-serif;}
@page WordSection1
	{size:8.5in 11.0in;
	margin:1.0in 1.0in 1.0in 1.0in;}
div.WordSection1
	{page:WordSection1;}
--></style><!--[if gte mso 9]><xml>
<o:shapedefaults v:ext=3D"edit" spidmax=3D"1026" />
</xml><![endif]--><!--[if gte mso 9]><xml>
<o:shapelayout v:ext=3D"edit">
<o:idmap v:ext=3D"edit" data=3D"1" />
</o:shapelayout></xml><![endif]-->
</head>
<body lang=3D"EN-US" link=3D"#0563C1" vlink=3D"#954F72">
<div class=3D"WordSection1">
<p class=3D"MsoNormal">Hi all, <o:p></o:p></p>
<p class=3D"MsoNormal"><o:p>&nbsp;</o:p></p>
<p class=3D"MsoNormal">There are plenty of places in the draft where statem=
ents are made in a somewhat sloppy manner.
<o:p></o:p></p>
<p class=3D"MsoNormal"><o:p>&nbsp;</o:p></p>
<p class=3D"MsoNormal">Section 5.1: <o:p></o:p></p>
<p class=3D"MsoNormal"><o:p>&nbsp;</o:p></p>
<p class=3D"MsoNormal">&quot; TLS 1.3 increases the number of<o:p></o:p></p=
>
<p class=3D"MsoNormal">&nbsp; cryptographic parameters that are negotiated =
in the handshake.<o:p></o:p></p>
<p class=3D"MsoNormal">&quot;<o:p></o:p></p>
<p class=3D"MsoNormal"><o:p>&nbsp;</o:p></p>
<p class=3D"MsoNormal">Increases the number of parameters compared to what?=
 <o:p></o:p></p>
<p class=3D"MsoNormal"><o:p>&nbsp;</o:p></p>
<p class=3D"MsoNormal">Section 5.1: <o:p></o:p></p>
<p class=3D"MsoNormal"><o:p>&nbsp;</o:p></p>
<p class=3D"MsoNormal">&quot;<o:p></o:p></p>
<p class=3D"MsoNormal">TLS 1.3 forbids all algorithms with known<o:p></o:p>=
</p>
<p class=3D"MsoNormal">&nbsp;&nbsp; weaknesses including 3DES, CBC mode, RC=
4, SHA-1, and MD5.&nbsp; TLS 1.3<o:p></o:p></p>
<p class=3D"MsoNormal">&nbsp;&nbsp; only supports cryptographic algorithms =
offering at least 112-bit<o:p></o:p></p>
<p class=3D"MsoNormal">&nbsp;&nbsp; security, see [RFC8446].<o:p></o:p></p>
<p class=3D"MsoNormal">&quot;<o:p></o:p></p>
<p class=3D"MsoNormal"><o:p>&nbsp;</o:p></p>
<p class=3D"MsoNormal">Most of those algorithms have been depreciated also =
with TLS 1.2
<o:p></o:p></p>
<p class=3D"MsoNormal">I would instead say that TLS 1.3 only uses AEAD ciph=
ers. <o:p>
</o:p></p>
<p class=3D"MsoNormal">&nbsp;<o:p></o:p></p>
<p class=3D"MsoNormal">&nbsp;Section 2.5: <o:p></o:p></p>
<p class=3D"MsoNormal"><o:p>&nbsp;</o:p></p>
<p class=3D"MsoNormal">&quot;<o:p></o:p></p>
<p class=3D"MsoNormal">The Commitment Message is<o:p></o:p></p>
<p class=3D"MsoNormal">&nbsp;&nbsp; an encrypted TLS record with applicatio=
n data 0x00 (i.e. a TLS record<o:p></o:p></p>
<p class=3D"MsoNormal">&nbsp;&nbsp; with TLSPlaintext.type =3D application_=
data, TLSPlaintext.length =3D 1,<o:p></o:p></p>
<p class=3D"MsoNormal">&nbsp;&nbsp; and TLSPlaintext.fragment =3D 0x00).<o:=
p></o:p></p>
<p class=3D"MsoNormal">&quot;<o:p></o:p></p>
<p class=3D"MsoNormal"><o:p>&nbsp;</o:p></p>
<p class=3D"MsoNormal">Adding the note about TLSPlaintext.type, TLSPlaintex=
t.length, and TLSPlaintext.fragment is not helpful given that both plaintex=
t TLS records as well as encrypted TLS records use these structures. There =
is also a mistake in there because
 the TLSInnerPlaintext.type contains the application_data type (of course t=
he TLSCiphertext.opaque_type also contains the application_data).<o:p></o:p=
></p>
<p class=3D"MsoNormal"><o:p>&nbsp;</o:p></p>
<p class=3D"MsoNormal">Introduction: <o:p></o:p></p>
<p class=3D"MsoNormal">&quot;<o:p></o:p></p>
<p class=3D"MsoNormal">Privacy is mandatory ... <o:p></o:p></p>
<p class=3D"MsoNormal">&quot;<o:p></o:p></p>
<p class=3D"MsoNormal"><o:p>&nbsp;</o:p></p>
<p class=3D"MsoNormal">It depends what you call &quot;privacy&quot;. TLS 1.=
3 offers a range of features that increase privacy protection but not all o=
f them are mandatory to use. Example: record padding
<o:p></o:p></p>
<p class=3D"MsoNormal"><o:p>&nbsp;</o:p></p>
<p class=3D"MsoNormal">In Section 2.1.8 you talk about privacy and say:<o:p=
></o:p></p>
<p class=3D"MsoNormal"><o:p>&nbsp;</o:p></p>
<p class=3D"MsoNormal">&quot;<o:p></o:p></p>
<p class=3D"MsoNormal">&nbsp;&nbsp; TLS 1.3 significantly improves privacy =
when compared to earlier<o:p></o:p></p>
<p class=3D"MsoNormal">&nbsp;&nbsp; versions of TLS by forbidding cipher su=
ites without confidentiality<o:p></o:p></p>
<p class=3D"MsoNormal">&nbsp;&nbsp; and encrypting large parts of the TLS h=
andshake including the<o:p></o:p></p>
<p class=3D"MsoNormal">&nbsp;&nbsp; certificate messages.<o:p></o:p></p>
<p class=3D"MsoNormal">&quot;<o:p></o:p></p>
<p class=3D"MsoNormal"><o:p>&nbsp;</o:p></p>
<p class=3D"MsoNormal">This list is not exhaustive when it comes to the pri=
vacy features in TLS 1.3, as you know. If you think it is worthwhile to hig=
hlight the privacy features then why not list all of them?<o:p></o:p></p>
<p class=3D"MsoNormal"><o:p>&nbsp;</o:p></p>
<p class=3D"MsoNormal"><o:p>&nbsp;</o:p></p>
<p class=3D"MsoNormal">Section 2.1.1: <o:p></o:p></p>
<p class=3D"MsoNormal"><o:p>&nbsp;</o:p></p>
<p class=3D"MsoNormal">&quot;<o:p></o:p></p>
<p class=3D"MsoNormal">SessionID is deprecated in TLS 1.3 and the EAP<o:p><=
/o:p></p>
<p class=3D"MsoNormal">&nbsp;&nbsp; server SHALL ignore the legacy_session_=
id field if TLS 1.3 is<o:p></o:p></p>
<p class=3D"MsoNormal">&nbsp;&nbsp; negotiated.<o:p></o:p></p>
<p class=3D"MsoNormal">&quot;<o:p></o:p></p>
<p class=3D"MsoNormal"><o:p>&nbsp;</o:p></p>
<p class=3D"MsoNormal">This is misleading because the EAP server does not l=
ook into the TLS handshake messages.
<o:p></o:p></p>
<p class=3D"MsoNormal">Additionally, the session ID is not deprecated - it =
is a legacy feature that is used in the backwards compatibility mode.
<o:p></o:p></p>
<p class=3D"MsoNormal">FWIW you are not saying anything about the backwards=
 compatibility mode and hence I believe you are not using it. That's someth=
ing that has to be made more explicit.
<o:p></o:p></p>
<p class=3D"MsoNormal"><o:p>&nbsp;</o:p></p>
<p class=3D"MsoNormal">Section 2.1.3: <o:p></o:p></p>
<p class=3D"MsoNormal"><o:p>&nbsp;</o:p></p>
<p class=3D"MsoNormal">&quot;<o:p></o:p></p>
<p class=3D"MsoNormal">The TLS PSK identity is typically derived by<o:p></o=
:p></p>
<p class=3D"MsoNormal">&nbsp;&nbsp; the TLS implementation and may be an op=
aque blob without a routable<o:p></o:p></p>
<p class=3D"MsoNormal">&nbsp;&nbsp; realm.&nbsp; The TLS PSK identity is th=
erefore in general unsuitable for<o:p></o:p></p>
<p class=3D"MsoNormal">&nbsp;&nbsp; deriving a NAI to use in the Identity R=
esponse.<o:p></o:p></p>
<p class=3D"MsoNormal">&quot;<o:p></o:p></p>
<p class=3D"MsoNormal"><o:p>&nbsp;</o:p></p>
<p class=3D"MsoNormal">There is no requirement in the TLS 1.3 spec that a P=
SK identity has to be in a NAI format. Hence, most implementations will not=
 produce one in a NAI format. It can still be used to derive a NAI in an Id=
entity Response if you stick a @realm
 to it at a different layer. <o:p></o:p></p>
<p class=3D"MsoNormal"><o:p>&nbsp;</o:p></p>
<p class=3D"MsoNormal">Section 2.1.6:<o:p></o:p></p>
<p class=3D"MsoNormal"><o:p>&nbsp;</o:p></p>
<p class=3D"MsoNormal">&quot;<o:p></o:p></p>
<p class=3D"MsoNormal">&nbsp;&nbsp; TLS 1.3 [RFC8446] defines that TLS serv=
ers can send a<o:p></o:p></p>
<p class=3D"MsoNormal">&nbsp;&nbsp; HelloRetryRequest message in response t=
o a ClientHello if the server<o:p></o:p></p>
<p class=3D"MsoNormal">&nbsp;&nbsp; finds an acceptable set of parameters b=
ut the initial ClientHello<o:p></o:p></p>
<p class=3D"MsoNormal">&nbsp;&nbsp; does not contain all the needed informa=
tion to continue the<o:p></o:p></p>
<p class=3D"MsoNormal">&nbsp;&nbsp; handshake.<o:p></o:p></p>
<p class=3D"MsoNormal">&quot;<o:p></o:p></p>
<p class=3D"MsoNormal"><o:p>&nbsp;</o:p></p>
<p class=3D"MsoNormal">The TLS specification also says that this message ca=
n be used for DDoS mitigation. I think that DDoS mitigation is a valid use =
case in an EAP-based deployment.
<o:p></o:p></p>
<p class=3D"MsoNormal"><o:p>&nbsp;</o:p></p>
<p class=3D"MsoNormal">Section 2.1.7:<o:p></o:p></p>
<p class=3D"MsoNormal"><o:p>&nbsp;</o:p></p>
<p class=3D"MsoNormal">&quot;<o:p></o:p></p>
<p class=3D"MsoNormal">&nbsp; Many client certificates<o:p></o:p></p>
<p class=3D"MsoNormal">&nbsp;&nbsp; contains an identity such as an email a=
ddress, which is already in<o:p></o:p></p>
<p class=3D"MsoNormal">&nbsp;&nbsp; NAI format.&nbsp; When the client certi=
ficate contains a NAI as subject<o:p></o:p></p>
<p class=3D"MsoNormal">&nbsp;&nbsp; name or alternative subject name, an an=
onymous NAI SHOULD be derived<o:p></o:p></p>
<p class=3D"MsoNormal">&nbsp;&nbsp; from the NAI in the certificate, see Se=
ction 2.1.8.<o:p></o:p></p>
<p class=3D"MsoNormal">&quot;&nbsp;&nbsp; <o:p></o:p></p>
<p class=3D"MsoNormal"><o:p>&nbsp;</o:p></p>
<p class=3D"MsoNormal">From where do you get the impression that &quot;many=
 client certificates&quot; contain an identity, such as an email address?
<o:p></o:p></p>
<p class=3D"MsoNormal">Why does it matter whether the NAI is contained in t=
he subject name or in the alt subject name?
<o:p></o:p></p>
<p class=3D"MsoNormal">You refer to Section 2.1.8 regarding how to derive a=
 anonymous NAI from the certificate and I couldn't find the text.&nbsp;&nbs=
p;&nbsp;
<o:p></o:p></p>
<p class=3D"MsoNormal"><o:p>&nbsp;</o:p></p>
<p class=3D"MsoNormal"><o:p>&nbsp;</o:p></p>
<p class=3D"MsoNormal">&quot;<o:p></o:p></p>
<p class=3D"MsoNormal">&nbsp;&nbsp; As the certificate messages in TLS 1.3 =
are encrypted, there is no<o:p></o:p></p>
<p class=3D"MsoNormal">&nbsp;&nbsp; need to send an empty certificate_list =
and perform a second handshake<o:p></o:p></p>
<p class=3D"MsoNormal">&nbsp;&nbsp; for privacy (as needed by EAP-TLS with =
earlier versions of TLS).<o:p></o:p></p>
<p class=3D"MsoNormal">&quot;<o:p></o:p></p>
<p class=3D"MsoNormal"><o:p>&nbsp;</o:p></p>
<p class=3D"MsoNormal">Most readers are probably not familiar with the prob=
lem you are describing here.
<o:p></o:p></p>
<p class=3D"MsoNormal">Also, this issue is not specific to EAP-TLS; the sam=
e approach has been used in TLS (prior to 1.3) in general.
<o:p></o:p></p>
<p class=3D"MsoNormal"><o:p>&nbsp;</o:p></p>
<p class=3D"MsoNormal">&quot;&nbsp;&nbsp; When EAP-TLS is used with TLS ver=
sion 1.3 or higher the EAP-TLS peer<o:p></o:p></p>
<p class=3D"MsoNormal">&nbsp;&nbsp; and EAP-TLS server SHALL follow the pro=
cessing specified by the used<o:p></o:p></p>
<p class=3D"MsoNormal">&nbsp;&nbsp; version of TLS.<o:p></o:p></p>
<p class=3D"MsoNormal">&quot;<o:p></o:p></p>
<p class=3D"MsoNormal"><o:p>&nbsp;</o:p></p>
<p class=3D"MsoNormal">This statement is obvious and does not say much. Wha=
t else do you want to do?
<o:p></o:p></p>
<p class=3D"MsoNormal"><o:p>&nbsp;</o:p></p>
<p class=3D"MsoNormal">&quot;<o:p></o:p></p>
<p class=3D"MsoNormal">&nbsp;&nbsp; For TLS 1.3 this means that the EAP-TLS=
 peer only<o:p></o:p></p>
<p class=3D"MsoNormal">&nbsp;&nbsp; sends an empty certificate_list if it d=
oes not have an appropriate<o:p></o:p></p>
<p class=3D"MsoNormal">&nbsp;&nbsp; certificate to send, and the EAP-TLS se=
rver MAY treat an empty<o:p></o:p></p>
<p class=3D"MsoNormal">&nbsp;&nbsp; certificate_list as a terminal conditio=
n.<o:p></o:p></p>
<p class=3D"MsoNormal">&quot;<o:p></o:p></p>
<p class=3D"MsoNormal"><o:p>&nbsp;</o:p></p>
<p class=3D"MsoNormal">In Section 2.1.5 you describe the case where the EAP=
 peer is not authenticated. This is a second way in TLS to delay authentica=
tion of the client to a latter phase. The approach in Section 2.1.5 was dec=
lared as acceptable with reference
 to emergency services but this case seems to be less acceptable. While bot=
h parties in TLS exchange may send an alert for a number of reasons I am cu=
rious why you point this situation out.<o:p></o:p></p>
<p class=3D"MsoNormal"><o:p>&nbsp;</o:p></p>
<p class=3D"MsoNormal">Section 2.1.3: <o:p></o:p></p>
<p class=3D"MsoNormal"><o:p>&nbsp;</o:p></p>
<p class=3D"MsoNormal">&quot;<o:p></o:p></p>
<p class=3D"MsoNormal">When EAP-TLS is used with<o:p></o:p></p>
<p class=3D"MsoNormal">&nbsp;&nbsp; TLS version 1.3 or higher, EAP-TLS SHAL=
L use a resumption mechanism<o:p></o:p></p>
<p class=3D"MsoNormal">&nbsp;&nbsp; compatible with that version of TLS.<o:=
p></o:p></p>
<p class=3D"MsoNormal">&quot;<o:p></o:p></p>
<p class=3D"MsoNormal"><o:p>&nbsp;</o:p></p>
<p class=3D"MsoNormal">This is a meaningless statement. What else do you wa=
nt to do? You cannot use the session resumption mechanism of TLS 1.3 in 1.2=
.<o:p></o:p></p>
<p class=3D"MsoNormal"><o:p></o:p></p>
<p class=3D"MsoNormal">Section 5.8: <o:p></o:p></p>
<p class=3D"MsoNormal"><o:p>&nbsp;</o:p></p>
<p class=3D"MsoNormal">&quot;<o:p></o:p></p>
<p class=3D"MsoNormal">&nbsp;&nbsp; Tracking of users by eavesdropping on i=
dentity responses or<o:p></o:p></p>
<p class=3D"MsoNormal">&nbsp;&nbsp; certificates is a well-known problem in=
 many EAP methods.
<o:p></o:p></p>
<p class=3D"MsoNormal">&quot;<o:p></o:p></p>
<p class=3D"MsoNormal"><o:p>&nbsp;</o:p></p>
<p class=3D"MsoNormal">I would not only focus on users because EAP methods =
are also used by devices.
<o:p></o:p></p>
<p class=3D"MsoNormal"><o:p>&nbsp;</o:p></p>
<p class=3D"MsoNormal">Section 5.9 talks about pervasive monitoring and doe=
s not add any new content beyond what is already said in the privacy sectio=
n. Could you merge the two?
<o:p></o:p></p>
<p class=3D"MsoNormal"><o:p>&nbsp;</o:p></p>
<p class=3D"MsoNormal">Section 5.10 talks about discovered vulnerabilities =
of earlier versions of TLS. It should be explicitly stated that these vulne=
rabilities are not about TLS 1.3. The text then goes on and says<o:p></o:p>=
</p>
<p class=3D"MsoNormal"><o:p>&nbsp;</o:p></p>
<p class=3D"MsoNormal">&quot; The use of TLS 1.3 mitigates most of the know=
n attacks. &quot;<o:p></o:p></p>
<p class=3D"MsoNormal"><o:p>&nbsp;</o:p></p>
<p class=3D"MsoNormal">Which attacks are not mitigated in TLS 1.3? <o:p></o=
:p></p>
<p class=3D"MsoNormal"><o:p>&nbsp;</o:p></p>
<p class=3D"MsoNormal"><o:p>&nbsp;</o:p></p>
<p class=3D"MsoNormal">Section 2.1.9:<o:p></o:p></p>
<p class=3D"MsoNormal">&quot;<o:p></o:p></p>
<p class=3D"MsoNormal">&nbsp;&nbsp; Including ContentType and ProtocolVersi=
on a single TLS record may be<o:p></o:p></p>
<p class=3D"MsoNormal">&nbsp;&nbsp; up to 16387 octets in length. <o:p></o:=
p></p>
<p class=3D"MsoNormal">&quot;<o:p></o:p></p>
<p class=3D"MsoNormal"><o:p>&nbsp;</o:p></p>
<p class=3D"MsoNormal">This is true if you do not use the Maximum Fragment =
Length Extension or the Record Size Limit extension.
<o:p></o:p></p>
<p class=3D"MsoNormal">The question is therefore: why don't you want to use=
 them?<o:p></o:p></p>
<p class=3D"MsoNormal"><o:p>&nbsp;</o:p></p>
<p class=3D"MsoNormal">Section 5.6:<o:p></o:p></p>
<p class=3D"MsoNormal"><o:p>&nbsp;</o:p></p>
<p class=3D"MsoNormal">&quot;<o:p></o:p></p>
<p class=3D"MsoNormal">&nbsp;&nbsp; EAP-TLS is typically encapsulated in ot=
her protocols, such as PPP<o:p></o:p></p>
<p class=3D"MsoNormal">&nbsp;&nbsp; [RFC1661], RADIUS [RFC2865], Diameter [=
RFC6733], or PANA [RFC5191].<o:p></o:p></p>
<p class=3D"MsoNormal">&quot;<o:p></o:p></p>
<p class=3D"MsoNormal"><o:p>&nbsp;</o:p></p>
<p class=3D"MsoNormal">EAP-TLS is encapsulated into EAP, which is then enca=
psulated into other protocols (such as RADIUS, Diameter, etc.).<o:p></o:p><=
/p>
<p class=3D"MsoNormal">&nbsp;&nbsp; <o:p></o:p></p>
<p class=3D"MsoNormal"><o:p>&nbsp;</o:p></p>
<p class=3D"MsoNormal">Ciao<o:p></o:p></p>
<p class=3D"MsoNormal">Hannes<o:p></o:p></p>
</div>
IMPORTANT NOTICE: The contents of this email and any attachments are confid=
ential and may also be privileged. If you are not the intended recipient, p=
lease notify the sender immediately and do not disclose the contents to any=
 other person, use it for any purpose,
 or store or copy the information in any medium. Thank you.
</body>
</html>

--_000_AM0PR08MB37166BE43DC27978FF5D2DA9FA1C0AM0PR08MB3716eurp_--


From nobody Wed Oct 21 02:14:17 2020
Return-Path: <Hannes.Tschofenig@arm.com>
X-Original-To: emu@ietfa.amsl.com
Delivered-To: emu@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 6F1A23A13E8 for <emu@ietfa.amsl.com>; Wed, 21 Oct 2020 02:14:16 -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, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, HTML_MESSAGE=0.001, RCVD_IN_MSPIKE_H2=-0.001, SPF_PASS=-0.001, UNPARSEABLE_RELAY=0.001] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (1024-bit key) header.d=armh.onmicrosoft.com header.b=HxtcrFiV; dkim=pass (1024-bit key) header.d=armh.onmicrosoft.com header.b=HxtcrFiV
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 rZdWEx2mXCl9 for <emu@ietfa.amsl.com>; Wed, 21 Oct 2020 02:14:14 -0700 (PDT)
Received: from EUR04-HE1-obe.outbound.protection.outlook.com (mail-eopbgr70079.outbound.protection.outlook.com [40.107.7.79]) (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 9A7113A13E7 for <emu@ietf.org>; Wed, 21 Oct 2020 02:14:13 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=armh.onmicrosoft.com;  s=selector2-armh-onmicrosoft-com; h=From:Date:Subject:Message-ID:Content-Type:MIME-Version:X-MS-Exchange-SenderADCheck; bh=XQJ/UJhmFHOpsAIcxlQ5jAE1aEmWVidzY5WCJfNZP7I=; b=HxtcrFiVgsefHJTvzl5SVd2eEGCljV/x89QnG5j7/jvuk+tCmfXw2Hn5bhvMtaZI3vwIFza+rXPJusqxSbhmVvfpxw22Ink2jbQT3GMFAr1ZpPTWiAnAtoXo90n+oukEU7CQClYsGFF7uXfX/G06g3OpJeIuEv49/Y17vQRVNyo=
Received: from DB7PR05CA0051.eurprd05.prod.outlook.com (2603:10a6:10:2e::28) by VI1PR0801MB1997.eurprd08.prod.outlook.com (2603:10a6:800:88::21) with Microsoft SMTP Server (version=TLS1_2, cipher=TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384) id 15.20.3477.23; Wed, 21 Oct 2020 09:14:10 +0000
Received: from DB5EUR03FT026.eop-EUR03.prod.protection.outlook.com (2603:10a6:10:2e:cafe::67) by DB7PR05CA0051.outlook.office365.com (2603:10a6:10:2e::28) with Microsoft SMTP Server (version=TLS1_2, cipher=TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384) id 15.20.3499.18 via Frontend Transport; Wed, 21 Oct 2020 09:14:09 +0000
X-MS-Exchange-Authentication-Results: spf=pass (sender IP is 63.35.35.123) smtp.mailfrom=arm.com; ietf.org; dkim=pass (signature was verified) header.d=armh.onmicrosoft.com;ietf.org; dmarc=pass action=none header.from=arm.com;
Received-SPF: Pass (protection.outlook.com: domain of arm.com designates 63.35.35.123 as permitted sender) receiver=protection.outlook.com; client-ip=63.35.35.123; helo=64aa7808-outbound-1.mta.getcheckrecipient.com;
Received: from 64aa7808-outbound-1.mta.getcheckrecipient.com (63.35.35.123) by DB5EUR03FT026.mail.protection.outlook.com (10.152.20.159) with Microsoft SMTP Server (version=TLS1_2, cipher=TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384) id 15.20.3499.18 via Frontend Transport; Wed, 21 Oct 2020 09:14:08 +0000
Received: ("Tessian outbound d5e343850048:v64"); Wed, 21 Oct 2020 09:14:08 +0000
X-CheckRecipientChecked: true
X-CR-MTA-CID: d30f331929edd6c7
X-CR-MTA-TID: 64aa7808
Received: from 6eecc76c0d08.1 by 64aa7808-outbound-1.mta.getcheckrecipient.com id F836A845-0F4F-426A-9F3C-ACEB9C7B8BEC.1;  Wed, 21 Oct 2020 09:14:00 +0000
Received: from EUR05-AM6-obe.outbound.protection.outlook.com by 64aa7808-outbound-1.mta.getcheckrecipient.com with ESMTPS id 6eecc76c0d08.1 (version=TLSv1.2 cipher=ECDHE-RSA-AES256-GCM-SHA384); Wed, 21 Oct 2020 09:14:00 +0000
ARC-Seal: i=1; a=rsa-sha256; s=arcselector9901; d=microsoft.com; cv=none; b=i7/e/+SMKgOWUpxE3DXxUgzQB51cyGWwhbZtI9/V3GNee7FWINbog8tgKbxMHjymtC+3am0Ojorl+vLSOrNGK8QBKcsQwd31GF1gG3qd4jzd7c24ce+exh2ZYHCs0PbE319+HWvZlW7InZQfVO6OuPQ//noX3TpdZ/mnlKnvuTtvQnuLW6P3m8TmGoqfyCeCfwYkZS+enbmNlWtrVL66aAIhKKnw8UTEhYfa7yvwYeB6nMa5wo1dESAHBWe1QrXkE+j3ceq7jfsr5MSu3H4TNyXNglkBsNu/b/Os4/U3voim/mCWYxPfwoLQERAixNM2bYmkW0U8Ehw0IFBdD3qdQw==
ARC-Message-Signature: i=1; a=rsa-sha256; c=relaxed/relaxed; d=microsoft.com;  s=arcselector9901; h=From:Date:Subject:Message-ID:Content-Type:MIME-Version:X-MS-Exchange-SenderADCheck; bh=XQJ/UJhmFHOpsAIcxlQ5jAE1aEmWVidzY5WCJfNZP7I=; b=j+tAaQubuiA8DAtS3Gwta4sBnrXbn7QgquJNMhhIEZSktnLdtZRKN72Ts7vRK5KdMwza9f+lgQH1XSZYzQsKOygusOkd4BzWUVcVbNGNFkzPPj5QTcNGim7uJynwe2thgRYUJkBiT34fKnfwet067QmJTEU++y4RlTdvy9M+B8r3kbjC+TBozvUzHet0JGrAjKIhdU7o+hSwGnszCM1flqyIJ6+duBGNvVYxF3qLoozQa6QvMHzC3uSXLcX+2LGM3sMK2cHhcwISmnxyo11vlowFklvgIqE4vm8xa0Y2QeD0HuS2etKaZkWMxAEv1RUgGX+s4Q7m9lXGWNCC3UYH+Q==
ARC-Authentication-Results: i=1; mx.microsoft.com 1; spf=pass smtp.mailfrom=arm.com; dmarc=pass action=none header.from=arm.com; dkim=pass header.d=arm.com; arc=none
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=armh.onmicrosoft.com;  s=selector2-armh-onmicrosoft-com; h=From:Date:Subject:Message-ID:Content-Type:MIME-Version:X-MS-Exchange-SenderADCheck; bh=XQJ/UJhmFHOpsAIcxlQ5jAE1aEmWVidzY5WCJfNZP7I=; b=HxtcrFiVgsefHJTvzl5SVd2eEGCljV/x89QnG5j7/jvuk+tCmfXw2Hn5bhvMtaZI3vwIFza+rXPJusqxSbhmVvfpxw22Ink2jbQT3GMFAr1ZpPTWiAnAtoXo90n+oukEU7CQClYsGFF7uXfX/G06g3OpJeIuEv49/Y17vQRVNyo=
Received: from AM0PR08MB3716.eurprd08.prod.outlook.com (2603:10a6:208:106::13) by AM0PR08MB3026.eurprd08.prod.outlook.com (2603:10a6:208:65::21) with Microsoft SMTP Server (version=TLS1_2, cipher=TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384) id 15.20.3477.25; Wed, 21 Oct 2020 09:13:58 +0000
Received: from AM0PR08MB3716.eurprd08.prod.outlook.com ([fe80::900e:c64d:a006:4860]) by AM0PR08MB3716.eurprd08.prod.outlook.com ([fe80::900e:c64d:a006:4860%6]) with mapi id 15.20.3455.037; Wed, 21 Oct 2020 09:13:58 +0000
From: Hannes Tschofenig <Hannes.Tschofenig@arm.com>
To: "emu@ietf.org" <emu@ietf.org>
Thread-Topic: draft-ietf-emu-eap-tls13-11: Repetition of Text
Thread-Index: Adanik6spbBuLdhaT1G315nmPE6BWg==
Date: Wed, 21 Oct 2020 09:13:58 +0000
Message-ID: <AM0PR08MB3716337D6E03EBCA4E89F037FA1C0@AM0PR08MB3716.eurprd08.prod.outlook.com>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
x-ts-tracking-id: FFA53FE40FC23A4CB3DC42BB31031DF5.0
Authentication-Results-Original: ietf.org; dkim=none (message not signed) header.d=none;ietf.org; dmarc=none action=none header.from=arm.com;
x-originating-ip: [156.67.196.116]
x-ms-publictraffictype: Email
X-MS-Office365-Filtering-HT: Tenant
X-MS-Office365-Filtering-Correlation-Id: 0c6ac6de-6d93-492d-448f-08d875a1aa75
x-ms-traffictypediagnostic: AM0PR08MB3026:|VI1PR0801MB1997:
X-Microsoft-Antispam-PRVS: <VI1PR0801MB19978788B673928B1E48FF79FA1C0@VI1PR0801MB1997.eurprd08.prod.outlook.com>
x-checkrecipientrouted: true
nodisclaimer: true
x-ms-oob-tlc-oobclassifiers: OLM:10000;OLM:10000;
X-MS-Exchange-SenderADCheck: 1
X-Microsoft-Antispam-Untrusted: BCL:0;
X-Microsoft-Antispam-Message-Info-Original: I+T2Gj517XY0XLAQVdXxudiiy5umFobah4OLwDFQkpF9mUt4zOZmhUTC0HBkhmsltw5hk/wlNg69PyPTagPP6kVpR5ZnbP1M3Dc2FUS8chxnRpOAu2nvOKEMDy6ukZctYCC5Gr2dUws5C09bNA8qLCBFNx+0GUdxNE1EkGM6WyysaBQMW/Y4BoodK8BgVVaScd865OLnDH8rohIkbnH/0Ir41HNEAP6Rjw3oE/t+8lUWOIFaRNKRXAsEepD2mgmoAxxqHkSDgdSGNv9sLuprzt/VSXTIxEsaVE+0faADuO8onGIoBRkwwGN1gfDB04GvTTQ6Z0zWPJHXaLvNFXWk1w==
X-Forefront-Antispam-Report-Untrusted: CIP:255.255.255.255; CTRY:; LANG:en; SCL:1; SRV:; IPV:NLI; SFV:NSPM; H:AM0PR08MB3716.eurprd08.prod.outlook.com; PTR:; CAT:NONE; SFS:(4636009)(39860400002)(136003)(396003)(346002)(376002)(366004)(26005)(186003)(9686003)(8936002)(316002)(7696005)(6916009)(6506007)(8676002)(71200400001)(66556008)(66476007)(76116006)(2906002)(66946007)(52536014)(478600001)(64756008)(83380400001)(66446008)(55016002)(5660300002)(33656002)(86362001); DIR:OUT; SFP:1101; 
x-ms-exchange-antispam-messagedata: jgtFeIaPWZqWQHIYE3qhZId5i0aN98mbPhzqN771Hmwc5fqt4VQE/3TyH4yejDfBHZKAwjnFthAaPCEBNvyAopQRHanoBCYRkdzAIUirhiu+WW86HLcqbXCniD1zwcvQEgN/rGO2VdcGSfH36GoNpaetIuAmjOwESuBQhq3FSp+T/keso1Jr0JBr/DWmM9elXlWtSYy2LM4Hp77tU50ArfHQVzMTBkvay2C1tyWCOffeT++XukKsMRAbjYE5gj7frdbNou1CDGRxKgdp/TfVAjL8cZxR3h2NXr3LfWuALnHGQ4OiewklTPZMS5N4AN/fQROHZotxjNijoqwZ3L8L++n2QPcSasVprWkQKrlhnfgDbXmsgu+hdSQh6f/G2RTxJfBoB+/SvmrkX5RN78wEfoviHPFc3R5Oj7nUu7bxj+ZbtjguB73xUYjwclmQrt7T0ysMnNoxCq4SAhRNGHoU4Emyb1MwPQ15v4AVkGqekzZddcRdTHbPiCA38mRi8YZc4FuKzr4+lCxCzyc3FqgupqGWIKjMCenKgKL/iJ1RWVcpATx00xm3DgAoCIfCnh3Jb89QF4W7ZVOqvskB3frXy3ePgSRMXr4QCnRoMxCVlwWPA5qdaHrNcdIZ0UXEE9N5uvk01ayDyWSAq7Wvo5YGAw==
x-ms-exchange-transport-forked: True
Content-Type: multipart/alternative; boundary="_000_AM0PR08MB3716337D6E03EBCA4E89F037FA1C0AM0PR08MB3716eurp_"
MIME-Version: 1.0
X-MS-Exchange-Transport-CrossTenantHeadersStamped: AM0PR08MB3026
Original-Authentication-Results: ietf.org; dkim=none (message not signed) header.d=none;ietf.org; dmarc=none action=none header.from=arm.com;
X-EOPAttributedMessage: 0
X-MS-Exchange-Transport-CrossTenantHeadersStripped: DB5EUR03FT026.eop-EUR03.prod.protection.outlook.com
X-MS-Office365-Filtering-Correlation-Id-Prvs: b960bec1-5cd9-42b5-7a26-08d875a1a4cd
X-Microsoft-Antispam: BCL:0;
X-Microsoft-Antispam-Message-Info: 8GpnuHWzvVSMNwv/F3U7kQP5970cg7A6BZBfQSIGPI13hNhWf5xCE/vJIpNFSE6NDRJi7mk/T2eGdbCtXhJG7RnS0nTAc1aVW8XKHAMZyWsolBK2XAPaurgBf/6Q4L8WSgcrj7tSg4J4FBQLzO08pe7D6kxYtglleSX24yXHYTqGEKNt8leXoVNx8hCcSoH62Jzjgv+sFgc+A9iS4TEBzOfAGew35Vsvz2j8hRq+v80EOrs+EdwFrfMLlCpJT1dzrc9TgAqPlj/eyDJlfcAkLypvTVQ9BHNDTLTOpBgn53vQi+KbZ2veZHg9cHy8Xq6WLJMxR30nCSIcK8AFlmm+zhPBt6NrCDNtzV4g+VauW4WkFNPL2/vgYn3GIcDXCqAHw+vhliNvnOOnOgYOCe9aDA==
X-Forefront-Antispam-Report: CIP:63.35.35.123; CTRY:IE; LANG:en; SCL:1; SRV:;  IPV:CAL; SFV:NSPM; H:64aa7808-outbound-1.mta.getcheckrecipient.com;  PTR:ec2-63-35-35-123.eu-west-1.compute.amazonaws.com; CAT:NONE; SFS:(4636009)(396003)(376002)(39860400002)(346002)(136003)(46966005)(6506007)(2906002)(8676002)(5660300002)(6916009)(86362001)(336012)(7696005)(82310400003)(26005)(81166007)(55016002)(9686003)(33656002)(356005)(70586007)(70206006)(316002)(47076004)(82740400003)(8936002)(478600001)(83380400001)(186003)(52536014); DIR:OUT; SFP:1101; 
X-OriginatorOrg: arm.com
X-MS-Exchange-CrossTenant-OriginalArrivalTime: 21 Oct 2020 09:14:08.2841 (UTC)
X-MS-Exchange-CrossTenant-Network-Message-Id: 0c6ac6de-6d93-492d-448f-08d875a1aa75
X-MS-Exchange-CrossTenant-Id: f34e5979-57d9-4aaa-ad4d-b122a662184d
X-MS-Exchange-CrossTenant-OriginalAttributedTenantConnectingIp: TenantId=f34e5979-57d9-4aaa-ad4d-b122a662184d; Ip=[63.35.35.123];  Helo=[64aa7808-outbound-1.mta.getcheckrecipient.com]
X-MS-Exchange-CrossTenant-AuthSource: DB5EUR03FT026.eop-EUR03.prod.protection.outlook.com
X-MS-Exchange-CrossTenant-AuthAs: Anonymous
X-MS-Exchange-CrossTenant-FromEntityHeader: HybridOnPrem
X-MS-Exchange-Transport-CrossTenantHeadersStamped: VI1PR0801MB1997
Archived-At: <https://mailarchive.ietf.org/arch/msg/emu/NkeYdi_wP9AG1iXkM3JGOz1OiIw>
Subject: [Emu] draft-ietf-emu-eap-tls13-11: Repetition of Text
X-BeenThere: emu@ietf.org
X-Mailman-Version: 2.1.29
Precedence: list
List-Id: "EAP Methods Update \(EMU\)" <emu.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/emu>, <mailto:emu-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/emu/>
List-Post: <mailto:emu@ietf.org>
List-Help: <mailto:emu-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/emu>, <mailto:emu-request@ietf.org?subject=subscribe>
X-List-Received-Date: Wed, 21 Oct 2020 09:14:16 -0000

--_000_AM0PR08MB3716337D6E03EBCA4E89F037FA1C0AM0PR08MB3716eurp_
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: quoted-printable

Hi all,

the draft contains a number of cases where text from the TLS 1.3 specificat=
ion or other specifications is repeated. Often, only fragments are used, wh=
ich can easily fool the reader into believing that the omitted parts do not=
 apply. Hence, I would avoid the repetition where not strictly necessary.

Here are two examples:

Section 2.1.6:

"
   As noted in Section 4.1.4 of [RFC8446],
   the server MUST provide the supported_versions extensions and SHOULD
   contain the minimal set of extensions necessary for the client to
   generate a correct ClientHello pair.  A HelloRetryRequest MUST NOT
   contain any extensions that were not first offered by the client in
   its ClientHello, with the exception of optionally including the
   cookie extension.
"

Section 2.1.9:

"
To avoid fragmentation, it
   is RECOMMENDED to keep the sizes of client, server, and trust anchor
   certificates small and the length of the certificate chains short.
   In addition, it is RECOMMENDED to use mechanisms that reduce the
   sizes of Certificate messages.

   While Elliptic Curve Cryptography (ECC) was optional for earlier
   version of TLS, TLS 1.3 mandates support of ECC (see Section 9 of
   [RFC8446]).  To avoid fragmentation, the use of ECC in certificates,
   signature algorithms, and groups are RECOMMENDED when using EAP-TLS
   with TLS 1.3 or higher.  At a 128-bit security level, this reduces
   public key sizes from 384 bytes (RSA and DHE) to 32-64 bytes (ECDHE)
   and signatures from 384 bytes (RSA) to 64 bytes (ECDSA and EdDSA).
   An EAP-TLS deployment MAY further reduce the certificate sizes by
   limiting the number of Subject Alternative Names.

   Endpoints SHOULD reduce the sizes of Certificate messages by omitting
   certificates that the other endpoint is known to possess.  When using
   TLS 1.3, all certificates that specifies a trust anchor may be
   omitted (see Section 4.4.2 of [RFC8446]).  When using TLS 1.2, only
   the self-signed certificate that specifies the root certificate
   authority may be omitted (see Section 7.4.2 of [RFC5246]).  EAP-TLS
   peers and servers SHOULD support and use the Cached Information
   Extension as specified in [RFC7924].  EAP-TLS peers and servers MAY
   use other extensions for reducing the sizes of Certificate messages,
   e.g. certificate compression [I-D.ietf-tls-certificate-compression].

   For a detailed discussion on reducing message sizes to prevent
   fragmentation, see [I-D.ietf-emu-eaptlscert].
"

This entire text should be replaced by a reference to [I-D.ietf-emu-eaptlsc=
ert], which offers a more detailed discussion.
It makes no sense to just copy a fragment of the text here, particularly wh=
en we are talking about a document from the same working group written by t=
he same authors.

An small error in the text above: trust anchors are not exchanged in the TL=
S handshake.

Ciao
Hannes
IMPORTANT NOTICE: The contents of this email and any attachments are confid=
ential and may also be privileged. If you are not the intended recipient, p=
lease notify the sender immediately and do not disclose the contents to any=
 other person, use it for any purpose, or store or copy the information in =
any medium. Thank you.

--_000_AM0PR08MB3716337D6E03EBCA4E89F037FA1C0AM0PR08MB3716eurp_
Content-Type: text/html; charset="us-ascii"
Content-Transfer-Encoding: quoted-printable

<html xmlns:v=3D"urn:schemas-microsoft-com:vml" xmlns:o=3D"urn:schemas-micr=
osoft-com:office:office" xmlns:w=3D"urn:schemas-microsoft-com:office:word" =
xmlns:m=3D"http://schemas.microsoft.com/office/2004/12/omml" xmlns=3D"http:=
//www.w3.org/TR/REC-html40">
<head>
<meta http-equiv=3D"Content-Type" content=3D"text/html; charset=3Dus-ascii"=
>
<meta name=3D"Generator" content=3D"Microsoft Word 15 (filtered medium)">
<style><!--
/* Font Definitions */
@font-face
	{font-family:"Cambria Math";
	panose-1:2 4 5 3 5 4 6 3 2 4;}
@font-face
	{font-family:DengXian;
	panose-1:2 1 6 0 3 1 1 1 1 1;}
@font-face
	{font-family:Calibri;
	panose-1:2 15 5 2 2 2 4 3 2 4;}
@font-face
	{font-family:"\@DengXian";
	panose-1:2 1 6 0 3 1 1 1 1 1;}
/* Style Definitions */
p.MsoNormal, li.MsoNormal, div.MsoNormal
	{margin:0in;
	font-size:11.0pt;
	font-family:"Calibri",sans-serif;}
span.EmailStyle17
	{mso-style-type:personal-compose;
	font-family:"Calibri",sans-serif;
	color:windowtext;}
.MsoChpDefault
	{mso-style-type:export-only;
	font-family:"Calibri",sans-serif;}
@page WordSection1
	{size:8.5in 11.0in;
	margin:1.0in 1.0in 1.0in 1.0in;}
div.WordSection1
	{page:WordSection1;}
--></style><!--[if gte mso 9]><xml>
<o:shapedefaults v:ext=3D"edit" spidmax=3D"1026" />
</xml><![endif]--><!--[if gte mso 9]><xml>
<o:shapelayout v:ext=3D"edit">
<o:idmap v:ext=3D"edit" data=3D"1" />
</o:shapelayout></xml><![endif]-->
</head>
<body lang=3D"EN-US" link=3D"#0563C1" vlink=3D"#954F72">
<div class=3D"WordSection1">
<p class=3D"MsoNormal">Hi all, <o:p></o:p></p>
<p class=3D"MsoNormal"><o:p>&nbsp;</o:p></p>
<p class=3D"MsoNormal">the draft contains a number of cases where text from=
 the TLS 1.3 specification or other specifications is repeated. Often, only=
 fragments are used, which can easily fool the reader into believing that t=
he omitted parts do not apply. Hence,
 I would avoid the repetition where not strictly necessary. <o:p></o:p></p>
<p class=3D"MsoNormal"><o:p>&nbsp;</o:p></p>
<p class=3D"MsoNormal">Here are two examples:<o:p></o:p></p>
<p class=3D"MsoNormal"><o:p>&nbsp;</o:p></p>
<p class=3D"MsoNormal">Section 2.1.6: <o:p></o:p></p>
<p class=3D"MsoNormal"><o:p>&nbsp;</o:p></p>
<p class=3D"MsoNormal">&quot;<o:p></o:p></p>
<p class=3D"MsoNormal">&nbsp;&nbsp; As noted in Section 4.1.4 of [RFC8446],=
<o:p></o:p></p>
<p class=3D"MsoNormal">&nbsp;&nbsp; the server MUST provide the supported_v=
ersions extensions and SHOULD<o:p></o:p></p>
<p class=3D"MsoNormal">&nbsp;&nbsp; contain the minimal set of extensions n=
ecessary for the client to<o:p></o:p></p>
<p class=3D"MsoNormal">&nbsp;&nbsp; generate a correct ClientHello pair.&nb=
sp; A HelloRetryRequest MUST NOT<o:p></o:p></p>
<p class=3D"MsoNormal">&nbsp; &nbsp;contain any extensions that were not fi=
rst offered by the client in<o:p></o:p></p>
<p class=3D"MsoNormal">&nbsp;&nbsp; its ClientHello, with the exception of =
optionally including the<o:p></o:p></p>
<p class=3D"MsoNormal">&nbsp;&nbsp; cookie extension.<o:p></o:p></p>
<p class=3D"MsoNormal">&quot;&nbsp; <o:p></o:p></p>
<p class=3D"MsoNormal"><o:p>&nbsp;</o:p></p>
<p class=3D"MsoNormal">Section 2.1.9:<o:p></o:p></p>
<p class=3D"MsoNormal"><o:p>&nbsp;</o:p></p>
<p class=3D"MsoNormal">&quot;<o:p></o:p></p>
<p class=3D"MsoNormal">To avoid fragmentation, it<o:p></o:p></p>
<p class=3D"MsoNormal">&nbsp;&nbsp; is RECOMMENDED to keep the sizes of cli=
ent, server, and trust anchor<o:p></o:p></p>
<p class=3D"MsoNormal">&nbsp;&nbsp; certificates small and the length of th=
e certificate chains short.<o:p></o:p></p>
<p class=3D"MsoNormal">&nbsp;&nbsp; In addition, it is RECOMMENDED to use m=
echanisms that reduce the<o:p></o:p></p>
<p class=3D"MsoNormal">&nbsp;&nbsp; sizes of Certificate messages.<o:p></o:=
p></p>
<p class=3D"MsoNormal"><o:p>&nbsp;</o:p></p>
<p class=3D"MsoNormal">&nbsp;&nbsp; While Elliptic Curve Cryptography (ECC)=
 was optional for earlier<o:p></o:p></p>
<p class=3D"MsoNormal">&nbsp;&nbsp; version of TLS, TLS 1.3 mandates suppor=
t of ECC (see Section 9 of<o:p></o:p></p>
<p class=3D"MsoNormal">&nbsp;&nbsp; [RFC8446]).&nbsp; To avoid fragmentatio=
n, the use of ECC in certificates,<o:p></o:p></p>
<p class=3D"MsoNormal">&nbsp;&nbsp; signature algorithms, and groups are RE=
COMMENDED when using EAP-TLS<o:p></o:p></p>
<p class=3D"MsoNormal">&nbsp;&nbsp; with TLS 1.3 or higher.&nbsp; At a 128-=
bit security level, this reduces<o:p></o:p></p>
<p class=3D"MsoNormal">&nbsp;&nbsp; public key sizes from 384 bytes (RSA an=
d DHE) to 32-64 bytes (ECDHE)<o:p></o:p></p>
<p class=3D"MsoNormal">&nbsp;&nbsp; and signatures from 384 bytes (RSA) to =
64 bytes (ECDSA and EdDSA).<o:p></o:p></p>
<p class=3D"MsoNormal">&nbsp;&nbsp; An EAP-TLS deployment MAY further reduc=
e the certificate sizes by<o:p></o:p></p>
<p class=3D"MsoNormal">&nbsp;&nbsp; limiting the number of Subject Alternat=
ive Names.<o:p></o:p></p>
<p class=3D"MsoNormal"><o:p>&nbsp;</o:p></p>
<p class=3D"MsoNormal">&nbsp;&nbsp; Endpoints SHOULD reduce the sizes of Ce=
rtificate messages by omitting<o:p></o:p></p>
<p class=3D"MsoNormal">&nbsp;&nbsp; certificates that the other endpoint is=
 known to possess.&nbsp; When using<o:p></o:p></p>
<p class=3D"MsoNormal">&nbsp;&nbsp; TLS 1.3, all certificates that specifie=
s a trust anchor may be<o:p></o:p></p>
<p class=3D"MsoNormal">&nbsp;&nbsp; omitted (see Section 4.4.2 of [RFC8446]=
).&nbsp; When using TLS 1.2, only<o:p></o:p></p>
<p class=3D"MsoNormal">&nbsp;&nbsp; the self-signed certificate that specif=
ies the root certificate<o:p></o:p></p>
<p class=3D"MsoNormal">&nbsp;&nbsp; authority may be omitted (see Section 7=
.4.2 of [RFC5246]).&nbsp; EAP-TLS<o:p></o:p></p>
<p class=3D"MsoNormal">&nbsp;&nbsp; peers and servers SHOULD support and us=
e the Cached Information<o:p></o:p></p>
<p class=3D"MsoNormal">&nbsp;&nbsp; Extension as specified in [RFC7924].&nb=
sp; EAP-TLS peers and servers MAY<o:p></o:p></p>
<p class=3D"MsoNormal">&nbsp;&nbsp; use other extensions for reducing the s=
izes of Certificate messages,<o:p></o:p></p>
<p class=3D"MsoNormal">&nbsp;&nbsp; e.g. certificate compression [I-D.ietf-=
tls-certificate-compression].<o:p></o:p></p>
<p class=3D"MsoNormal"><o:p>&nbsp;</o:p></p>
<p class=3D"MsoNormal">&nbsp;&nbsp; For a detailed discussion on reducing m=
essage sizes to prevent<o:p></o:p></p>
<p class=3D"MsoNormal">&nbsp;&nbsp; fragmentation, see [I-D.ietf-emu-eaptls=
cert].<o:p></o:p></p>
<p class=3D"MsoNormal">&quot;<o:p></o:p></p>
<p class=3D"MsoNormal"><o:p>&nbsp;</o:p></p>
<p class=3D"MsoNormal">This entire text should be replaced by a reference t=
o [I-D.ietf-emu-eaptlscert], which offers a more detailed discussion.
<o:p></o:p></p>
<p class=3D"MsoNormal">It makes no sense to just copy a fragment of the tex=
t here, particularly when we are talking about a document from the same wor=
king group written by the same authors.
<o:p></o:p></p>
<p class=3D"MsoNormal"><o:p>&nbsp;</o:p></p>
<p class=3D"MsoNormal">An small error in the text above: trust anchors are =
not exchanged in the TLS handshake.<o:p></o:p></p>
<p class=3D"MsoNormal">&nbsp;&nbsp; <o:p></o:p></p>
<p class=3D"MsoNormal">Ciao<o:p></o:p></p>
<p class=3D"MsoNormal">Hannes<o:p></o:p></p>
</div>
IMPORTANT NOTICE: The contents of this email and any attachments are confid=
ential and may also be privileged. If you are not the intended recipient, p=
lease notify the sender immediately and do not disclose the contents to any=
 other person, use it for any purpose,
 or store or copy the information in any medium. Thank you.
</body>
</html>

--_000_AM0PR08MB3716337D6E03EBCA4E89F037FA1C0AM0PR08MB3716eurp_--


From nobody Wed Oct 21 02:16:17 2020
Return-Path: <Hannes.Tschofenig@arm.com>
X-Original-To: emu@ietfa.amsl.com
Delivered-To: emu@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 554F33A13EB for <emu@ietfa.amsl.com>; Wed, 21 Oct 2020 02:16:15 -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, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, HTML_MESSAGE=0.001, RCVD_IN_MSPIKE_H2=-0.001, SPF_PASS=-0.001, UNPARSEABLE_RELAY=0.001] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (1024-bit key) header.d=armh.onmicrosoft.com header.b=EIt8z4w9; dkim=pass (1024-bit key) header.d=armh.onmicrosoft.com header.b=EIt8z4w9
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 rpJwATOluq5V for <emu@ietfa.amsl.com>; Wed, 21 Oct 2020 02:16:13 -0700 (PDT)
Received: from EUR04-VI1-obe.outbound.protection.outlook.com (mail-eopbgr80081.outbound.protection.outlook.com [40.107.8.81]) (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 6C42F3A13E9 for <emu@ietf.org>; Wed, 21 Oct 2020 02:16:13 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=armh.onmicrosoft.com;  s=selector2-armh-onmicrosoft-com; h=From:Date:Subject:Message-ID:Content-Type:MIME-Version:X-MS-Exchange-SenderADCheck; bh=ghqcKI7FvmAzQUyZg9yx34AybKzBTDV4PRRS1MMiABI=; b=EIt8z4w9xhWQpoG0yhqVcVna0EUBBBqkPSKffTjlfIpmTT5US6F5R2igm2Ps27Euj3O9KUTUn1mlge2Um6LMehexFcRbtTA0rQC5JHPyNcHZm9+U4pKBsJ1XPyr5ydcRoVBWSZ78KapnUIUybr3M0P70DHg1W98dVqBPSqgXbD4=
Received: from DB6P193CA0010.EURP193.PROD.OUTLOOK.COM (2603:10a6:6:29::20) by AM6PR08MB5125.eurprd08.prod.outlook.com (2603:10a6:20b:e2::29) with Microsoft SMTP Server (version=TLS1_2, cipher=TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384) id 15.20.3499.18; Wed, 21 Oct 2020 09:16:07 +0000
Received: from DB5EUR03FT060.eop-EUR03.prod.protection.outlook.com (2603:10a6:6:29:cafe::7c) by DB6P193CA0010.outlook.office365.com (2603:10a6:6:29::20) with Microsoft SMTP Server (version=TLS1_2, cipher=TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384) id 15.20.3499.18 via Frontend Transport; Wed, 21 Oct 2020 09:16:07 +0000
X-MS-Exchange-Authentication-Results: spf=pass (sender IP is 63.35.35.123) smtp.mailfrom=arm.com; ietf.org; dkim=pass (signature was verified) header.d=armh.onmicrosoft.com;ietf.org; dmarc=pass action=none header.from=arm.com;
Received-SPF: Pass (protection.outlook.com: domain of arm.com designates 63.35.35.123 as permitted sender) receiver=protection.outlook.com; client-ip=63.35.35.123; helo=64aa7808-outbound-1.mta.getcheckrecipient.com;
Received: from 64aa7808-outbound-1.mta.getcheckrecipient.com (63.35.35.123) by DB5EUR03FT060.mail.protection.outlook.com (10.152.21.231) with Microsoft SMTP Server (version=TLS1_2, cipher=TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384) id 15.20.3499.18 via Frontend Transport; Wed, 21 Oct 2020 09:16:07 +0000
Received: ("Tessian outbound ba2270a55485:v64"); Wed, 21 Oct 2020 09:16:06 +0000
X-CR-MTA-TID: 64aa7808
Received: from 489a55f581d9.1 by 64aa7808-outbound-1.mta.getcheckrecipient.com id F6F66AFD-7EC1-44D1-9EC8-754ADA5C94F5.1;  Wed, 21 Oct 2020 09:16:01 +0000
Received: from EUR04-VI1-obe.outbound.protection.outlook.com by 64aa7808-outbound-1.mta.getcheckrecipient.com with ESMTPS id 489a55f581d9.1 (version=TLSv1.2 cipher=ECDHE-RSA-AES256-GCM-SHA384); Wed, 21 Oct 2020 09:16:01 +0000
ARC-Seal: i=1; a=rsa-sha256; s=arcselector9901; d=microsoft.com; cv=none; b=KmlsC4NSjx7HZdbUeJL8H2xca+lhMQ+AS8jDVuFVgZ7M4upcIvgsdw/MBpvk4r9CxuQpM7FSQwOl/p7QKYKo1U5Jk0y0SKVR72a5EFUiS8lw1HeiIUm98z8HaGKj5J+6RHfm9zvTq1wCRcjHVDbFIOBJ/T2Xd9aUn+PMXfIiMBOXgyXtpp+d0HueZJln95h1USNzwrPyq6NhpEwAS3js7pB47BfdmIp/MjIdmi8O8DZ0xslmOeIdKX1mzkfcCop3Xsi8maEH8QVdjjyFN1nF8y+1WQMVAUfl9vVOdOc3wWEptscHYoNFYUkk4q7Hg02BCqXmClTKIwbEpBDj91ZOYA==
ARC-Message-Signature: i=1; a=rsa-sha256; c=relaxed/relaxed; d=microsoft.com;  s=arcselector9901; h=From:Date:Subject:Message-ID:Content-Type:MIME-Version:X-MS-Exchange-SenderADCheck; bh=ghqcKI7FvmAzQUyZg9yx34AybKzBTDV4PRRS1MMiABI=; b=mXwNZh+80Tp6U9ceBR8CaqCr2mmeicwK2s9NAP0sGO7QO9adXGBaaRg/sdRcrt5WcMNc9v7KW1PKnmO1WDqguds8g56H1KbOgUrmQpJnhVvfn3zj0OhxoqlCfi65/kK+myCiXMBgy4MRgWEvpNfKcdpJJ82UQLay/F8xYYfkeBj2PZlMs3gzvwrgI7PXjXhw8pIKEe24VM7vEQCVOTxZJ04SP/VMjNk3gTbbSgt2XSLIa9sZfP3tCFLnG5eMKg1oyfIaq/GXTEBETL0gjoB225YrAxCKVtKsHZzedMZk7fQndqiLwhkBZ/9A9GqZ3XtlrB+yBKgr4tx5RqhplntDsg==
ARC-Authentication-Results: i=1; mx.microsoft.com 1; spf=pass smtp.mailfrom=arm.com; dmarc=pass action=none header.from=arm.com; dkim=pass header.d=arm.com; arc=none
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=armh.onmicrosoft.com;  s=selector2-armh-onmicrosoft-com; h=From:Date:Subject:Message-ID:Content-Type:MIME-Version:X-MS-Exchange-SenderADCheck; bh=ghqcKI7FvmAzQUyZg9yx34AybKzBTDV4PRRS1MMiABI=; b=EIt8z4w9xhWQpoG0yhqVcVna0EUBBBqkPSKffTjlfIpmTT5US6F5R2igm2Ps27Euj3O9KUTUn1mlge2Um6LMehexFcRbtTA0rQC5JHPyNcHZm9+U4pKBsJ1XPyr5ydcRoVBWSZ78KapnUIUybr3M0P70DHg1W98dVqBPSqgXbD4=
Received: from AM0PR08MB3716.eurprd08.prod.outlook.com (2603:10a6:208:106::13) by AM8PR08MB5825.eurprd08.prod.outlook.com (2603:10a6:20b:1d6::9) with Microsoft SMTP Server (version=TLS1_2, cipher=TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384) id 15.20.3477.20; Wed, 21 Oct 2020 09:16:00 +0000
Received: from AM0PR08MB3716.eurprd08.prod.outlook.com ([fe80::900e:c64d:a006:4860]) by AM0PR08MB3716.eurprd08.prod.outlook.com ([fe80::900e:c64d:a006:4860%6]) with mapi id 15.20.3455.037; Wed, 21 Oct 2020 09:16:00 +0000
From: Hannes Tschofenig <Hannes.Tschofenig@arm.com>
To: "emu@ietf.org" <emu@ietf.org>
Thread-Topic: draft-ietf-emu-eap-tls13-11: Conformance with the TLS 13 Spec
Thread-Index: AdanipBIa3KYIg/4R32+I03iMOAOFA==
Date: Wed, 21 Oct 2020 09:16:00 +0000
Message-ID: <AM0PR08MB3716356D95FCD7240F205EEBFA1C0@AM0PR08MB3716.eurprd08.prod.outlook.com>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
x-ts-tracking-id: CA9609D83FBDA142BE71DEF1CB2A089D.0
x-checkrecipientchecked: true
Authentication-Results-Original: ietf.org; dkim=none (message not signed) header.d=none;ietf.org; dmarc=none action=none header.from=arm.com;
x-originating-ip: [156.67.196.116]
x-ms-publictraffictype: Email
X-MS-Office365-Filtering-HT: Tenant
X-MS-Office365-Filtering-Correlation-Id: 0a7b21f1-96c4-403c-6ac4-08d875a1f13a
x-ms-traffictypediagnostic: AM8PR08MB5825:|AM6PR08MB5125:
X-Microsoft-Antispam-PRVS: <AM6PR08MB5125F46BBDB3FAC1CC4B319DFA1C0@AM6PR08MB5125.eurprd08.prod.outlook.com>
x-checkrecipientrouted: true
nodisclaimer: true
x-ms-oob-tlc-oobclassifiers: OLM:8273;OLM:10000;
X-MS-Exchange-SenderADCheck: 1
X-Microsoft-Antispam-Untrusted: BCL:0;
X-Microsoft-Antispam-Message-Info-Original: NqPHClXlFeKRqwp3Fx3bb/+J5Mzi/p/S57gEVMmyOgVHDacQ3MKT7JyMrcy/4j43MptYWOe/+bHATZgNZLaIbBKiK4WcO5bFBEVrpfhgLgl9oxsEESEb64fBdPho9ck79u8uirBc/3N64uXV9/+m6tag4d8o5otcsaVLYmK89Oczt5WNgw1CO1pzQP/cEesV4KB3vjAR9zDIMYXFSGPi9ULTyIGnUgpsiY74PYRxjEQKXmnz6nRhPcn2Gd65tmMIdn0U2hVtAVoNXprH+YweCqBLQ5EcrynTHsdn5gUGAzel+lWCgCK+2zncZv6Z0b6iGVZMYbeuj8yEpXYmfW9nbw==
X-Forefront-Antispam-Report-Untrusted: CIP:255.255.255.255; CTRY:; LANG:en; SCL:1; SRV:; IPV:NLI; SFV:NSPM; H:AM0PR08MB3716.eurprd08.prod.outlook.com; PTR:; CAT:NONE; SFS:(4636009)(39860400002)(136003)(346002)(366004)(396003)(376002)(26005)(66446008)(8936002)(186003)(55016002)(83380400001)(478600001)(8676002)(86362001)(9686003)(7696005)(76116006)(66946007)(6916009)(2906002)(6506007)(66476007)(64756008)(4744005)(52536014)(5660300002)(66556008)(71200400001)(316002)(33656002); DIR:OUT; SFP:1101; 
x-ms-exchange-antispam-messagedata: 9/d/I3vwuhMo4xcrpFDppUjIYBqo0cL+jMRqeH54GCdeM6vNWyxHHkjkqHJBcbGcVP8CQ11syf3PjaRJz1NjVdZOzSbnoGZQbFnGt20c5T3LpRCld0ELlSNQbnXTacPcJVHSlzRsyPi5+uiWtSrTQ/rntqOdcWW1F4LosoDQcMdyVBU54SI8Mi7kN838eTjILqiAYvQISPc1wulNjPMtUZocwLAdclL/d+BPUS/M3gIcFSmK8Dl21WY/R28AZt5akQT+YcPxih9zF2RX+knq/95B2A8oGG4Yh6RiiCFN9rF1nAkqlZNbNV3fgmelzfwrSHMxR8JDyUtBCuxbv2pBQc3ZnMDe41q8vadyOzB13St675s/rkstGXs+QFkHWC6o3fYUiif0Qq2kFsSTfwTf7hgL1OvA9OhkWsTVf3lm6lefw6zOiCS8FoQ64auv5VfSd0HM2dfiSyDRIUJyzxz5LtaYp+KDSfU5+UwTBDosRSU+pXu5Y++Npc6YeDg8EvlsSgNaPXxMINHwD8c9L9/+ERxrGQ1SWXwG1T//Zpbxv6KYBnQ9CkvKUdd8GoHaXWYvmfRJrjbWb6QLIU4IP3WI0z7c6U/lbSv7VLCDUEsq/VceeTpUSlAS09P275/LgiRPZB1E7Xt2NRhptjWXRD3vYQ==
x-ms-exchange-transport-forked: True
Content-Type: multipart/alternative; boundary="_000_AM0PR08MB3716356D95FCD7240F205EEBFA1C0AM0PR08MB3716eurp_"
MIME-Version: 1.0
X-MS-Exchange-Transport-CrossTenantHeadersStamped: AM8PR08MB5825
Original-Authentication-Results: ietf.org; dkim=none (message not signed) header.d=none;ietf.org; dmarc=none action=none header.from=arm.com;
X-EOPAttributedMessage: 0
X-MS-Exchange-Transport-CrossTenantHeadersStripped: DB5EUR03FT060.eop-EUR03.prod.protection.outlook.com
X-MS-Office365-Filtering-Correlation-Id-Prvs: 5e1d96df-264c-4db4-b5b2-08d875a1ed60
X-Microsoft-Antispam: BCL:0;
X-Microsoft-Antispam-Message-Info: dRyyT1ZXGEqJAG6rT/b5Av7XQ+uLGXt2tUKtVK4Qnts/o8SjnuO52iVJHMtqVNMLc2tKJMwUVxA1m7ZCZqKSNnrZ/xw1tdex/Y5RxL3v0dhVt5CeMRSqwAwoNj2iec40OyeugZ5qqXJk/J+SWseGaIjYHlmgB1HOYmQTF4p0t1fJiiVCZQyrXsMaxWFj210M7RB86YZ0SbdEafiK4cD4yDme+T+j931JGKE8z6pYl57i7s9uV9a05hGqudIeIs/cDXHEMn2BF8/EM9Wmlh117OlLeAvnEgAcGn8yVnopeyG3TE1buMsWYwKmUjh364x+W3IqQogstloAuVYY3qTn8THxf5KXpTJw3Ns62SwuIqRkrwHOX9uoz1lZ13ulOFqvMhsJeTkMurIHS8wA/1paog==
X-Forefront-Antispam-Report: CIP:63.35.35.123; CTRY:IE; LANG:en; SCL:1; SRV:;  IPV:CAL; SFV:NSPM; H:64aa7808-outbound-1.mta.getcheckrecipient.com;  PTR:ec2-63-35-35-123.eu-west-1.compute.amazonaws.com; CAT:NONE; SFS:(4636009)(136003)(376002)(396003)(346002)(39860400002)(46966005)(52536014)(186003)(5660300002)(26005)(8676002)(70206006)(316002)(6916009)(33656002)(86362001)(70586007)(9686003)(55016002)(8936002)(336012)(7696005)(82740400003)(47076004)(81166007)(6506007)(356005)(83380400001)(2906002)(478600001)(82310400003); DIR:OUT; SFP:1101; 
X-OriginatorOrg: arm.com
X-MS-Exchange-CrossTenant-OriginalArrivalTime: 21 Oct 2020 09:16:07.0187 (UTC)
X-MS-Exchange-CrossTenant-Network-Message-Id: 0a7b21f1-96c4-403c-6ac4-08d875a1f13a
X-MS-Exchange-CrossTenant-Id: f34e5979-57d9-4aaa-ad4d-b122a662184d
X-MS-Exchange-CrossTenant-OriginalAttributedTenantConnectingIp: TenantId=f34e5979-57d9-4aaa-ad4d-b122a662184d; Ip=[63.35.35.123];  Helo=[64aa7808-outbound-1.mta.getcheckrecipient.com]
X-MS-Exchange-CrossTenant-AuthSource: DB5EUR03FT060.eop-EUR03.prod.protection.outlook.com
X-MS-Exchange-CrossTenant-AuthAs: Anonymous
X-MS-Exchange-CrossTenant-FromEntityHeader: HybridOnPrem
X-MS-Exchange-Transport-CrossTenantHeadersStamped: AM6PR08MB5125
Archived-At: <https://mailarchive.ietf.org/arch/msg/emu/2nd2SHeN6oCK4vHY295CYTqxaE4>
Subject: [Emu] draft-ietf-emu-eap-tls13-11: Conformance with the TLS 13 Spec
X-BeenThere: emu@ietf.org
X-Mailman-Version: 2.1.29
Precedence: list
List-Id: "EAP Methods Update \(EMU\)" <emu.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/emu>, <mailto:emu-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/emu/>
List-Post: <mailto:emu@ietf.org>
List-Help: <mailto:emu-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/emu>, <mailto:emu-request@ietf.org?subject=subscribe>
X-List-Received-Date: Wed, 21 Oct 2020 09:16:15 -0000

--_000_AM0PR08MB3716356D95FCD7240F205EEBFA1C0AM0PR08MB3716eurp_
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: quoted-printable

Hi all,

Section 2.1.6 says:

"
   An EAP-TLS peer and server SHOULD support the use of
   HelloRetryRequest message.
"

My understanding of the TLS 1.3 specification is that the HelloRetryRequest=
 is not an optional-to-implement message but it is only optional to use.

Is there a reason to deviate from the TLS 1.3 specification? Is there any r=
eason to talk about the HRR message? The purpose of the message is given in=
 the TLS 1.3 spec and whether you use it or not is up to the deployment.

Ciao
Hannes


IMPORTANT NOTICE: The contents of this email and any attachments are confid=
ential and may also be privileged. If you are not the intended recipient, p=
lease notify the sender immediately and do not disclose the contents to any=
 other person, use it for any purpose, or store or copy the information in =
any medium. Thank you.

--_000_AM0PR08MB3716356D95FCD7240F205EEBFA1C0AM0PR08MB3716eurp_
Content-Type: text/html; charset="us-ascii"
Content-Transfer-Encoding: quoted-printable

<html xmlns:v=3D"urn:schemas-microsoft-com:vml" xmlns:o=3D"urn:schemas-micr=
osoft-com:office:office" xmlns:w=3D"urn:schemas-microsoft-com:office:word" =
xmlns:m=3D"http://schemas.microsoft.com/office/2004/12/omml" xmlns=3D"http:=
//www.w3.org/TR/REC-html40">
<head>
<meta http-equiv=3D"Content-Type" content=3D"text/html; charset=3Dus-ascii"=
>
<meta name=3D"Generator" content=3D"Microsoft Word 15 (filtered medium)">
<style><!--
/* Font Definitions */
@font-face
	{font-family:"Cambria Math";
	panose-1:2 4 5 3 5 4 6 3 2 4;}
@font-face
	{font-family:DengXian;
	panose-1:2 1 6 0 3 1 1 1 1 1;}
@font-face
	{font-family:Calibri;
	panose-1:2 15 5 2 2 2 4 3 2 4;}
@font-face
	{font-family:"\@DengXian";
	panose-1:2 1 6 0 3 1 1 1 1 1;}
/* Style Definitions */
p.MsoNormal, li.MsoNormal, div.MsoNormal
	{margin:0in;
	font-size:11.0pt;
	font-family:"Calibri",sans-serif;}
span.EmailStyle17
	{mso-style-type:personal-compose;
	font-family:"Calibri",sans-serif;
	color:windowtext;}
.MsoChpDefault
	{mso-style-type:export-only;
	font-family:"Calibri",sans-serif;}
@page WordSection1
	{size:8.5in 11.0in;
	margin:1.0in 1.0in 1.0in 1.0in;}
div.WordSection1
	{page:WordSection1;}
--></style><!--[if gte mso 9]><xml>
<o:shapedefaults v:ext=3D"edit" spidmax=3D"1026" />
</xml><![endif]--><!--[if gte mso 9]><xml>
<o:shapelayout v:ext=3D"edit">
<o:idmap v:ext=3D"edit" data=3D"1" />
</o:shapelayout></xml><![endif]-->
</head>
<body lang=3D"EN-US" link=3D"#0563C1" vlink=3D"#954F72">
<div class=3D"WordSection1">
<p class=3D"MsoNormal">Hi all, <o:p></o:p></p>
<p class=3D"MsoNormal"><o:p>&nbsp;</o:p></p>
<p class=3D"MsoNormal">Section 2.1.6 says:<o:p></o:p></p>
<p class=3D"MsoNormal"><o:p>&nbsp;</o:p></p>
<p class=3D"MsoNormal">&quot;<o:p></o:p></p>
<p class=3D"MsoNormal">&nbsp;&nbsp; An EAP-TLS peer and server SHOULD suppo=
rt the use of<o:p></o:p></p>
<p class=3D"MsoNormal">&nbsp;&nbsp; HelloRetryRequest message.&nbsp; <o:p><=
/o:p></p>
<p class=3D"MsoNormal">&quot;<o:p></o:p></p>
<p class=3D"MsoNormal"><o:p>&nbsp;</o:p></p>
<p class=3D"MsoNormal">My understanding of the TLS 1.3 specification is tha=
t the HelloRetryRequest is not an optional-to-implement message but it is o=
nly optional to use.
<o:p></o:p></p>
<p class=3D"MsoNormal"><o:p>&nbsp;</o:p></p>
<p class=3D"MsoNormal">Is there a reason to deviate from the TLS 1.3 specif=
ication? Is there any reason to talk about the HRR message? The purpose of =
the message is given in the TLS 1.3 spec and whether you use it or not is u=
p to the deployment.
<o:p></o:p></p>
<p class=3D"MsoNormal"><o:p>&nbsp;</o:p></p>
<p class=3D"MsoNormal">Ciao<o:p></o:p></p>
<p class=3D"MsoNormal">Hannes<o:p></o:p></p>
<p class=3D"MsoNormal"><o:p>&nbsp;</o:p></p>
<p class=3D"MsoNormal">&nbsp;&nbsp; <o:p></o:p></p>
</div>
IMPORTANT NOTICE: The contents of this email and any attachments are confid=
ential and may also be privileged. If you are not the intended recipient, p=
lease notify the sender immediately and do not disclose the contents to any=
 other person, use it for any purpose,
 or store or copy the information in any medium. Thank you.
</body>
</html>

--_000_AM0PR08MB3716356D95FCD7240F205EEBFA1C0AM0PR08MB3716eurp_--


From nobody Wed Oct 21 06:37:46 2020
Return-Path: <aland@deployingradius.com>
X-Original-To: emu@ietfa.amsl.com
Delivered-To: emu@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 2B14B3A10E5 for <emu@ietfa.amsl.com>; Wed, 21 Oct 2020 06:37:45 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.899
X-Spam-Level: 
X-Spam-Status: No, score=-1.899 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, SPF_HELO_NONE=0.001, SPF_PASS=-0.001, URIBL_BLOCKED=0.001] autolearn=ham autolearn_force=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 A88e_EjL_9Yk for <emu@ietfa.amsl.com>; Wed, 21 Oct 2020 06:37:43 -0700 (PDT)
Received: from mail.networkradius.com (mail.networkradius.com [62.210.147.122]) (using TLSv1.2 with cipher ADH-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id A43823A133F for <emu@ietf.org>; Wed, 21 Oct 2020 06:35:59 -0700 (PDT)
Received: from [192.168.46.130] (24-52-251-6.cable.teksavvy.com [24.52.251.6]) by mail.networkradius.com (Postfix) with ESMTPSA id 43801192; Wed, 21 Oct 2020 13:35:57 +0000 (UTC)
Authentication-Results: NetworkRADIUS; dmarc=none (p=none dis=none) header.from=deployingradius.com
Content-Type: text/plain; charset=utf-8
Mime-Version: 1.0 (Mac OS X Mail 13.4 \(3608.120.23.2.1\))
From: Alan DeKok <aland@deployingradius.com>
In-Reply-To: <AM0PR08MB3716A5224BA1C5D36BC150A0FA1C0@AM0PR08MB3716.eurprd08.prod.outlook.com>
Date: Wed, 21 Oct 2020 09:35:55 -0400
Cc: "emu@ietf.org" <emu@ietf.org>
Content-Transfer-Encoding: quoted-printable
Message-Id: <6F537472-91CD-4095-9039-113B43AB2D19@deployingradius.com>
References: <AM0PR08MB3716A5224BA1C5D36BC150A0FA1C0@AM0PR08MB3716.eurprd08.prod.outlook.com>
To: Hannes Tschofenig <Hannes.Tschofenig@arm.com>
X-Mailer: Apple Mail (2.3608.120.23.2.1)
Archived-At: <https://mailarchive.ietf.org/arch/msg/emu/roBVPnZsO5uTN5Ti6QXmMyRirwM>
Subject: Re: [Emu] draft-ietf-emu-eap-tls13-11: Updates RFC 5216
X-BeenThere: emu@ietf.org
X-Mailman-Version: 2.1.29
Precedence: list
List-Id: "EAP Methods Update \(EMU\)" <emu.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/emu>, <mailto:emu-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/emu/>
List-Post: <mailto:emu@ietf.org>
List-Help: <mailto:emu-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/emu>, <mailto:emu-request@ietf.org?subject=subscribe>
X-List-Received-Date: Wed, 21 Oct 2020 13:37:45 -0000

On Oct 21, 2020, at 5:00 AM, Hannes Tschofenig =
<Hannes.Tschofenig@arm.com> wrote:
> the draft says it updates the earlier EAP-TLS version and claims that =
the updates are related to
> =20
> * Section 5.6 Authorization
> * Section 5.7 Resumption
> =20
> The content of Section 5.6 actually does not relate to EAP-TLS but is =
generic to all EAP methods. I don't think it even belongs in an EAP =
method document.

  The second paragraph is generic to all EAP methods.  But it's =
explanatory, and doesn't offer specific security advice.

  The third paragraph is relevant to EAP-TLS, even if the first part =
true for all EAP methods.  However, the second part refers to the PSK =
used for resumption, and is specific to EAP-TLS.  As such, I believe =
that the text should stay. =20

> The content of Section 5.7 claims that there are aspects of =
resumptions that are not described in the earlier version of EAP-TLS. =
The focus is then on the way how the cached data is stored, an =
implementation-specific aspect, that is not specific to EAP-TLS because =
the concept of caching is used by other EAP methods too.

  That's nice, but I don't recall any other document which discusses =
cached data with respect to EAP.  Since we're updating EAP-TLS here, I =
think it's relevant.

  i.e. if we could refer to another document, that would be preferred.  =
Since no other document exists, we need to discuss security =
considerations with respect to EAP-TLS.  Even if the discussion is =
_also_ relevant to non-TLS EAP methods.

> Then, there is a threat presented whereby the authorization =
information changes between the full handshake and the resumption =
handshake. I believe that this is not a threat that is unique to EAP-TLS =
because this can happen even when there is no resumption.

  Yes.

  However, the identity used for authentication changes when doing =
resumption.  This change means that authorization based on identities is =
more difficult than with "normal" authentication.  As such, there are =
attacks unique to resumption which must be mitigated.

  Perhaps this point could be made more clear.  i.e. instead of the =
focus being on cached data, the focus could be on changing identities, =
and how cached data can help detect and address that change.

> Nothing prevents you from checking authorization again when you do =
resumption though and even during an ongoing session. I would argue that =
there is a lot of text in there that has nothing to do with EAP-TLS but =
rather concerns the whole system in which EAP is used. If this is indeed =
a problem, I believe it should be covered in a separate document.

  Given the time frame and the need to update EAP-TLS for TLS 1.3, I =
disagree.  It is a problem, and it should be addressed here.

> I don=E2=80=99t think it is a problem because extensions for RADIUS =
and Diameter have been developed to address this issue to revoke =
authorization during the lifetime of a session.

  This document should give guidance on how to implement EAP-TLS =
securely.  RADIUS and Diameter don't help with issues such as the =
identity changing for resumption.

> Here is where it gets confusing. The introduction says "This document =
defines how to use EAP-TLS with TLS 1.3 (or higher) and does not change =
how EAP-TLS is used with older versions of TLS." To me, this does not =
sound like an update.

 It doesn't not change earlier versions of EAP-TLS.  But it gives new =
guidance.  Perhaps this could be clearer.

> At a minimum, I would clarify in the introduction what the updates to =
RFC 5216 are. This will help those implementers that focus on a variant =
of EAP-TLS that uses version 1.2.

  I agree.

> As mentioned above, I don't believe Sections 5.6 and 5.7 belong to =
this document. Leave it in there if someone in the group gets paid by =
the number of published pages.

  Or if the authors wish to give practical, timely, advice to =
implementors of EAP-TLS.

  Alan DeKok.


From nobody Wed Oct 21 06:39:50 2020
Return-Path: <aland@deployingradius.com>
X-Original-To: emu@ietfa.amsl.com
Delivered-To: emu@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 736613A09E3 for <emu@ietfa.amsl.com>; Wed, 21 Oct 2020 06:39:48 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.899
X-Spam-Level: 
X-Spam-Status: No, score=-1.899 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, SPF_HELO_NONE=0.001, SPF_PASS=-0.001, URIBL_BLOCKED=0.001] autolearn=ham autolearn_force=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 SuE9Ja3c_RmT for <emu@ietfa.amsl.com>; Wed, 21 Oct 2020 06:39:47 -0700 (PDT)
Received: from mail.networkradius.com (mail.networkradius.com [62.210.147.122]) (using TLSv1.2 with cipher ADH-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 2DF323A0FD7 for <emu@ietf.org>; Wed, 21 Oct 2020 06:38:20 -0700 (PDT)
Received: from [192.168.46.130] (24-52-251-6.cable.teksavvy.com [24.52.251.6]) by mail.networkradius.com (Postfix) with ESMTPSA id 72102102; Wed, 21 Oct 2020 13:38:18 +0000 (UTC)
Authentication-Results: NetworkRADIUS; dmarc=none (p=none dis=none) header.from=deployingradius.com
Content-Type: text/plain; charset=us-ascii
Mime-Version: 1.0 (Mac OS X Mail 13.4 \(3608.120.23.2.1\))
From: Alan DeKok <aland@deployingradius.com>
In-Reply-To: <AM0PR08MB371647618F993B8C5BA6EB5FFA1C0@AM0PR08MB3716.eurprd08.prod.outlook.com>
Date: Wed, 21 Oct 2020 09:38:17 -0400
Cc: "emu@ietf.org" <emu@ietf.org>
Content-Transfer-Encoding: quoted-printable
Message-Id: <39F1D3BD-0726-4DFC-8165-E8077AF6CE6A@deployingradius.com>
References: <AM0PR08MB371647618F993B8C5BA6EB5FFA1C0@AM0PR08MB3716.eurprd08.prod.outlook.com>
To: Hannes Tschofenig <Hannes.Tschofenig@arm.com>
X-Mailer: Apple Mail (2.3608.120.23.2.1)
Archived-At: <https://mailarchive.ietf.org/arch/msg/emu/zdJtGUJzJMAZVTQ5VD9Y37wnm34>
Subject: Re: [Emu] draft-ietf-emu-eap-tls13-11: OCSP Stapling
X-BeenThere: emu@ietf.org
X-Mailman-Version: 2.1.29
Precedence: list
List-Id: "EAP Methods Update \(EMU\)" <emu.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/emu>, <mailto:emu-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/emu/>
List-Post: <mailto:emu@ietf.org>
List-Help: <mailto:emu-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/emu>, <mailto:emu-request@ietf.org?subject=subscribe>
X-List-Received-Date: Wed, 21 Oct 2020 13:39:48 -0000

On Oct 21, 2020, at 5:02 AM, Hannes Tschofenig =
<Hannes.Tschofenig@arm.com> wrote:
> this draft mandates OCSCP stapling (for use with TLS 1.3 in EAP-TLS) =
and I believe this is a problem for implementations. This extra burden =
is IMHO unjustified. For the type of deployments where EAP is used there =
is no need for a mandatory certificate revocation checking with OCSP.
> =20
> Having it optional, like the use of many other TLS extensions, is fine =
for me. FWIW even TLS 1.3, which is used in a more generic environment, =
does not mandate the use of OCSP stapling.

  I agree.  It should be fine to make OCSP stapling optional.

  Alan DeKok.


From nobody Wed Oct 21 08:57:00 2020
Return-Path: <joe@salowey.net>
X-Original-To: emu@ietfa.amsl.com
Delivered-To: emu@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id EB23E3A003E for <emu@ietfa.amsl.com>; Wed, 21 Oct 2020 08:56:59 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.898
X-Spam-Level: 
X-Spam-Status: No, score=-1.898 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, HTML_MESSAGE=0.001, SPF_HELO_NONE=0.001, SPF_PASS=-0.001, URIBL_BLOCKED=0.001] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (2048-bit key) header.d=salowey-net.20150623.gappssmtp.com
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 gwOUo7w8I28u for <emu@ietfa.amsl.com>; Wed, 21 Oct 2020 08:56:58 -0700 (PDT)
Received: from mail-qk1-x729.google.com (mail-qk1-x729.google.com [IPv6:2607:f8b0:4864:20::729]) (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 A00183A0FF9 for <emu@ietf.org>; Wed, 21 Oct 2020 08:56:58 -0700 (PDT)
Received: by mail-qk1-x729.google.com with SMTP id i22so2928573qkn.9 for <emu@ietf.org>; Wed, 21 Oct 2020 08:56:58 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=salowey-net.20150623.gappssmtp.com; s=20150623; h=mime-version:from:date:message-id:subject:to:cc; bh=Z4rdSn+oWMoFXy9KxyFGdjhL6Vt1nz0Naae7rBAvQY0=; b=Sa5NXo06KdVSTJc4x+wBfnU4Wd9uAk+Q2vZbW8XPpCuI4I2QbXdNKyh4d1xafHqRvW icEW2hxyp7t1iR/jN29tFkJ2GoUxFjaaUOQErItoVuIsguNaI8bJ4fPhQ9gYGbSm9E4T NQnLz/ujcfnxEzAUNCEgmVXcjzo6zAvwVgqv/tk+x5DXUhaTMT3H8eVuC9S+isnDrTmX ixNziDtmCM5Lf7YdbcOsMJuYneTtIH9nmZGmSNJ3L9o9+6k8Du9tw96pYiDsgAnLhrVM MLJynYBSFslNmwokl6nVGw6PvPeo7kk3XPsydkowZJzhIf2CQ+l89QZsb+BFRAosaZYW FaGA==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:mime-version:from:date:message-id:subject:to:cc; bh=Z4rdSn+oWMoFXy9KxyFGdjhL6Vt1nz0Naae7rBAvQY0=; b=hhwX7TNjGF1zwIDx10m3CyHJwsZc6LLSHVMIBffLS+aJbZliZlWErumrVAFJu1M8fb xO14YrmCUlLwyzVZYp+JBEB8De9uE6DqamM887NL7WRyMjV/sQGkjkpfAVir38xJ48D2 WvUgF9twgSvkZr7YIFAs/jUlrOXLFsQsDS7wyR4bOi0CXIEyCgWCTNe4Ut2PET5CQ6JN ucGOl3YLl5eNFOeXMVK0T1SX24YKrL0hRiF0lb9bF2Wn2SKRlKZ8H4nGloCLTnRBetMW T4yRvXoB+rEqLfcGrfAUMdQDHYF/87LQkoeNk362s+G296dGw30jn5CsPcm43Bxsk2Ze /z4g==
X-Gm-Message-State: AOAM530oiFxY1WKIrt52VxP6wa9Isazmlz3uEXpZhWuxh0Uk4Qhdi56n Dhs6xjebEjE8H4bEYPfdUnI5pM3cP+qTqKljOUXWDQbpukVo2Q==
X-Google-Smtp-Source: ABdhPJwuDRPH9pIj1E7dvBSt2Yfoo9I0emuWGhPBtereHJ3aR718Sv3Qm2zEWSsRzhUQIE2Ix68zcI9R1GFTPZIvw44=
X-Received: by 2002:a37:849:: with SMTP id 70mr3856976qki.332.1603295817393; Wed, 21 Oct 2020 08:56:57 -0700 (PDT)
MIME-Version: 1.0
From: Joseph Salowey <joe@salowey.net>
Date: Wed, 21 Oct 2020 08:56:46 -0700
Message-ID: <CAOgPGoAm+b7QZ2QpJuVhrsjhrCMN6b-ujeWW+1ARxMWmCYgkow@mail.gmail.com>
To: EMU WG <emu@ietf.org>
Cc: Oleg Pekar <oleg.pekar.2017@gmail.com>, Jorge Vergara <jovergar@microsoft.com>,  Jouni Malinen <j@w1.fi>, Eliot Lear <lear@cisco.com>, Roman Danyliw <rdd@cert.org>
Content-Type: multipart/alternative; boundary="000000000000aa7f1105b230654c"
Archived-At: <https://mailarchive.ietf.org/arch/msg/emu/OpaqygfIuco02AI8J9H5YA8vtYU>
Subject: [Emu] Resolution of TEAP Errata
X-BeenThere: emu@ietf.org
X-Mailman-Version: 2.1.29
Precedence: list
List-Id: "EAP Methods Update \(EMU\)" <emu.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/emu>, <mailto:emu-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/emu/>
List-Post: <mailto:emu@ietf.org>
List-Help: <mailto:emu-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/emu>, <mailto:emu-request@ietf.org?subject=subscribe>
X-List-Received-Date: Wed, 21 Oct 2020 15:57:00 -0000

--000000000000aa7f1105b230654c
Content-Type: text/plain; charset="UTF-8"

I'll be posting proposed errata revisions for a short, 1 week, final review
before sending it off to the Area Director (Roman) who has the
responsibility of the final action.  For more information how errata are
handled and the please see [1].

Please take a little time to review the errata resolution to make sure that
they match what was discussed on the list and in meetings.

Thanks,

Joe

[1] https://www.ietf.org/about/groups/iesg/statements/processing-rfc-errata/

--000000000000aa7f1105b230654c
Content-Type: text/html; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable

<div dir=3D"ltr">I&#39;ll be posting proposed errata revisions for a short,=
 1 week, final review before sending it off to the Area Director (Roman) wh=
o has the responsibility=C2=A0of the final action.=C2=A0 For more informati=
on how errata are handled and the please see [1].=C2=A0 =C2=A0<div><br></di=
v><div>Please take a little time to review the errata resolution to make su=
re that they match what was discussed on the list and in meetings.=C2=A0=C2=
=A0</div><div><br></div><div>Thanks,</div><div><br></div><div>Joe</div><div=
><br></div><div>[1]=C2=A0<a href=3D"https://www.ietf.org/about/groups/iesg/=
statements/processing-rfc-errata/">https://www.ietf.org/about/groups/iesg/s=
tatements/processing-rfc-errata/</a></div><div><br></div><div><br></div><di=
v><br></div><div><br></div></div>

--000000000000aa7f1105b230654c--


From nobody Wed Oct 21 09:30:49 2020
Return-Path: <joe@salowey.net>
X-Original-To: emu@ietfa.amsl.com
Delivered-To: emu@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 3B97F3A12CF for <emu@ietfa.amsl.com>; Wed, 21 Oct 2020 09:30:47 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.898
X-Spam-Level: 
X-Spam-Status: No, score=-1.898 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, HTML_MESSAGE=0.001, SPF_HELO_NONE=0.001, SPF_PASS=-0.001, URIBL_BLOCKED=0.001] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (2048-bit key) header.d=salowey-net.20150623.gappssmtp.com
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 WB60JJbu4cLB for <emu@ietfa.amsl.com>; Wed, 21 Oct 2020 09:30:45 -0700 (PDT)
Received: from mail-qk1-x730.google.com (mail-qk1-x730.google.com [IPv6:2607:f8b0:4864:20::730]) (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 379BF3A1239 for <emu@ietf.org>; Wed, 21 Oct 2020 09:30:45 -0700 (PDT)
Received: by mail-qk1-x730.google.com with SMTP id 188so3018940qkk.12 for <emu@ietf.org>; Wed, 21 Oct 2020 09:30:45 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=salowey-net.20150623.gappssmtp.com; s=20150623; h=mime-version:from:date:message-id:subject:to; bh=D0wt5KTpHv9lGS/acmamBUmqz/sGhC+JKeSRWTOwjZY=; b=iuhQAvCzeKBEd5SaA91ni3MW5UZ/OugSoeqabgSXH1SWHsmHEetQokM19iN+sSWKjE gHM49Fr9DWDSvmanhJFFg4WvM1x2f7L44wJ88U7Ullxw2YPxnFeilY0DdTMkED23F3/g 4eKU53rtAqFHfi2y7hKw0KdBELpDZUc6wt0pNbmKqaNbgSs+uhO23CkxPE8FT6QWZkh7 xc69fPq+GylaAZccLk45jAv6jkJ6VWviL/LUYSva8YYb1wEh+sIjJ2jirFQd6nu6RiSo WcmAlZ8Aj1bemmwtqKVrqBjl4XzE1mo4UmrU+cPumjNogLClevZH1AjQTzxI5khE9u6w XDFw==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:mime-version:from:date:message-id:subject:to; bh=D0wt5KTpHv9lGS/acmamBUmqz/sGhC+JKeSRWTOwjZY=; b=Wgp8IMJ+UdArQJ8x/pqGRBdfNeqigv3pnMTPXh4snhLy+JzqQYE/iUqxHKXZxC3nYV EwiSThyuSEn51KFLZCThHJtLWqPB/25j6rGPi6HCNeA95nHkoSVNYpIE8guDdhqkdcZ9 egXG3iSeYBH6jMZh7J3oTEsvtu6tJ8LvrXtx1K5mKx9lcT0kq/GsIgI1oSj6fnmjDX4O znVIQ+AHZUwshKtuvgiITElImIUFkvcuXmDGFNiu0j1eOKxtuZWVIL5ldGK410rK3Hti HQm3eX+MapyD2cN8sYroki/zBu/lqSc3Qzr9JwZkyvuIhiK4c0FYMrNoP/DS5fQJkXT3 Q+2Q==
X-Gm-Message-State: AOAM530Gak/4RLXhTYUbkDTWIYjoFRHtJtrsWJiWZBJHK4OBZApWbaRJ AgschZiDuAgsoRFZHCVe2vE818Xs3NAWe+J+vuILsST1rVUb2w==
X-Google-Smtp-Source: ABdhPJz3a6RZyJ+FGMQg4OMtcgByBCANj/LE7TSFSKUhreCafz0OHI08b6ykmcXQ+27D1yoIf3tEMgUig1i8n6UYeCA=
X-Received: by 2002:a05:620a:219a:: with SMTP id g26mr3878499qka.416.1603297843875;  Wed, 21 Oct 2020 09:30:43 -0700 (PDT)
MIME-Version: 1.0
From: Joseph Salowey <joe@salowey.net>
Date: Wed, 21 Oct 2020 09:30:33 -0700
Message-ID: <CAOgPGoC83neA1mGBwbA5Bqfj1K3CFOvphb0ZNwcMeUAFyB1PRw@mail.gmail.com>
To: EMU WG <emu@ietf.org>, "Oleg Pekar (olpekar)" <olpekar@cisco.com>,  Jorge Vergara <jovergar=40microsoft.com@dmarc.ietf.org>, Jouni Malinen <j@w1.fi>
Content-Type: multipart/alternative; boundary="000000000000743a3005b230de04"
Archived-At: <https://mailarchive.ietf.org/arch/msg/emu/xgQdQ-pAS0D6BB15XKGqU0xuEq4>
Subject: [Emu] Proposed resolution for TEAP errata 5127
X-BeenThere: emu@ietf.org
X-Mailman-Version: 2.1.29
Precedence: list
List-Id: "EAP Methods Update \(EMU\)" <emu.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/emu>, <mailto:emu-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/emu/>
List-Post: <mailto:emu@ietf.org>
List-Help: <mailto:emu-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/emu>, <mailto:emu-request@ietf.org?subject=subscribe>
X-List-Received-Date: Wed, 21 Oct 2020 16:30:47 -0000

--000000000000743a3005b230de04
Content-Type: text/plain; charset="UTF-8"

Errata 5127: https://www.rfc-editor.org/errata/eid5127
Proposed State: Verified
Revision:
Section 5.2.
OLD

IMSK = First 32 octets of TLS-PRF(EMSK, "TEAPbindkey@ietf.org" |
     "\0" | 64)

NEW

IMSK = First 32 octets of TLS-PRF(EMSK, "TEAPbindkey@ietf.org" |
   '/0', 64)

Notes:
According to

RFC5246 The Transport Layer Security (TLS) Protocol Version 1.2

5. HMAC and the Pseudorandom Function

"TLS's PRF is created by applying P_hash to the secret as:

PRF(secret, label, seed) = P_<hash>(secret, label + seed)"

In this case the seed is the 2-byte length of the output as defined by RFC
5295.  In terms of P_<Hash> the derivation would look like:

IMSK = P_<Hash>(EMSK, "TEAPbindkey@ietf.org" | 0x00 | 0x00 | 0x40)

--000000000000743a3005b230de04
Content-Type: text/html; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable

<div dir=3D"ltr">Errata 5127:=C2=A0<a href=3D"https://www.rfc-editor.org/er=
rata/eid5127">https://www.rfc-editor.org/errata/eid5127</a><div></div><div>=
Proposed State: Verified</div><div>Revision:</div>Section 5.2.=C2=A0<br>OLD=
<div><br>IMSK =3D First 32 octets of TLS-PRF(EMSK, &quot;<a href=3D"mailto:=
TEAPbindkey@ietf.org">TEAPbindkey@ietf.org</a>&quot; |<br>=C2=A0 =C2=A0 =C2=
=A0&quot;\0&quot; | 64)<div><br><div>NEW</div><div><br><div>IMSK =3D First =
32 octets of TLS-PRF(EMSK, &quot;<a href=3D"mailto:TEAPbindkey@ietf.org">TE=
APbindkey@ietf.org</a>&quot; |</div>=C2=A0 =C2=A0&#39;/0&#39;, 64)=C2=A0<di=
v><br></div><div>Notes:=C2=A0</div>According to<br><br>RFC5246 The Transpor=
t Layer Security (TLS) Protocol Version 1.2<br><br>5. HMAC and the Pseudora=
ndom Function<br><br>&quot;TLS&#39;s PRF is created by applying P_hash to t=
he secret as:<br><br>PRF(secret, label, seed) =3D P_&lt;hash&gt;(secret, la=
bel + seed)&quot;=C2=A0</div><div><br></div><div>In this case the seed is t=
he 2-byte length of the output as defined by RFC 5295.=C2=A0 In terms of P_=
&lt;Hash&gt; the derivation would look like:<br><br>IMSK =3D P_&lt;Hash&gt;=
(EMSK, &quot;<a href=3D"mailto:TEAPbindkey@ietf.org">TEAPbindkey@ietf.org</=
a>&quot; | 0x00 | 0x00 | 0x40)</div></div></div><div><br></div><div><br></d=
iv></div>

--000000000000743a3005b230de04--


From nobody Wed Oct 21 09:45:57 2020
Return-Path: <mcr+ietf@sandelman.ca>
X-Original-To: emu@ietfa.amsl.com
Delivered-To: emu@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id C9AAB3A0B7B for <emu@ietfa.amsl.com>; Wed, 21 Oct 2020 09:45:55 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.899
X-Spam-Level: 
X-Spam-Status: No, score=-1.899 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, SPF_HELO_NONE=0.001, SPF_PASS=-0.001, URIBL_BLOCKED=0.001] autolearn=ham autolearn_force=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 F9vwy0ZaBesu for <emu@ietfa.amsl.com>; Wed, 21 Oct 2020 09:45:54 -0700 (PDT)
Received: from tuna.sandelman.ca (tuna.sandelman.ca [IPv6:2607:f0b0:f:3:216:3eff:fe7c:d1f3]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 159BE3A067A for <emu@ietf.org>; Wed, 21 Oct 2020 09:45:53 -0700 (PDT)
Received: from localhost (localhost [127.0.0.1]) by tuna.sandelman.ca (Postfix) with ESMTP id 66FCA389C1; Wed, 21 Oct 2020 12:52:08 -0400 (EDT)
Received: from tuna.sandelman.ca ([127.0.0.1]) by localhost (localhost [127.0.0.1]) (amavisd-new, port 10024) with LMTP id 2YOrh102HcBg; Wed, 21 Oct 2020 12:52:07 -0400 (EDT)
Received: from sandelman.ca (obiwan.sandelman.ca [209.87.249.21]) by tuna.sandelman.ca (Postfix) with ESMTP id 62A65389BF; Wed, 21 Oct 2020 12:52:07 -0400 (EDT)
Received: from localhost (localhost [IPv6:::1]) by sandelman.ca (Postfix) with ESMTP id 2BE321D2; Wed, 21 Oct 2020 12:45:51 -0400 (EDT)
From: Michael Richardson <mcr+ietf@sandelman.ca>
To: Hannes Tschofenig <Hannes.Tschofenig@arm.com>, "emu\@ietf.org" <emu@ietf.org>
In-Reply-To: <AM0PR08MB371647618F993B8C5BA6EB5FFA1C0@AM0PR08MB3716.eurprd08.prod.outlook.com>
References: <AM0PR08MB371647618F993B8C5BA6EB5FFA1C0@AM0PR08MB3716.eurprd08.prod.outlook.com>
X-Mailer: MH-E 8.6+git; nmh 1.7+dev; GNU Emacs 26.1
X-Face: $\n1pF)h^`}$H>Hk{L"x@)JS7<%Az}5RyS@k9X%29-lHB$Ti.V>2bi.~ehC0; <'$9xN5Ub# z!G,p`nR&p7Fz@^UXIn156S8.~^@MJ*mMsD7=QFeq%AL4m<nPbLgmtKK-5dC@#:k
MIME-Version: 1.0
Content-Type: multipart/signed; boundary="=-=-="; micalg=pgp-sha512; protocol="application/pgp-signature"
Date: Wed, 21 Oct 2020 12:45:51 -0400
Message-ID: <15861.1603298751@localhost>
Archived-At: <https://mailarchive.ietf.org/arch/msg/emu/wkc8Es8IbaKfCf7MAe25FQt78oI>
Subject: Re: [Emu] draft-ietf-emu-eap-tls13-11: OCSP Stapling
X-BeenThere: emu@ietf.org
X-Mailman-Version: 2.1.29
Precedence: list
List-Id: "EAP Methods Update \(EMU\)" <emu.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/emu>, <mailto:emu-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/emu/>
List-Post: <mailto:emu@ietf.org>
List-Help: <mailto:emu-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/emu>, <mailto:emu-request@ietf.org?subject=subscribe>
X-List-Received-Date: Wed, 21 Oct 2020 16:45:56 -0000

--=-=-=
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: quoted-printable


Hannes Tschofenig <Hannes.Tschofenig@arm.com> wrote:
    > this draft mandates OCSCP stapling (for use with TLS 1.3 in EAP-TLS)
    > and I believe this is a problem for implementations. This extra burden
    > is IMHO unjustified. For the type of deployments where EAP is used
    > there is no need for a mandatory certificate revocation checking with
    > OCSP.

Is it:
   1) there is no need for mandatory certificate revocation checking
   2) there is no need to make OCSP checking the mandatory method for certi=
ficate revocation checking

Are you objecting to:
   a) mandatory certificate revocation checking
   b) mandatory OCSP
   c) mandatory OCSP *stapling* when using OCSP

I think, if you the client (who has no Internet yet), is going to be able to
do certificate revocation checking, then doing it via OCSP stapling is the
right way to go.  It can't do ONLINE CSP, because it has no Internet.

    > Having it optional, like the use of many other TLS extensions, is fine
    > for me. FWIW even TLS 1.3, which is used in a more generic environmen=
t,
    > does not mandate the use of OCSP stapling.

    > This requirement will make the problem described in
    > draft-ietf-emu-eaptlscert worse. I am sure the authors are aware of
    > this fact since they are also co-authors of draft-ietf-emu-eaptlscert.

=2D-
Michael Richardson <mcr+IETF@sandelman.ca>   . o O ( IPv6 I=C3=B8T consulti=
ng )
           Sandelman Software Works Inc, Ottawa and Worldwide

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

-----BEGIN PGP SIGNATURE-----

iQEzBAEBCgAdFiEEbsyLEzg/qUTA43uogItw+93Q3WUFAl+QZb4ACgkQgItw+93Q
3WU0iwf/RVqv+gjOdnLskQMXhc24TV53Wca5KfAV9Xpypfjmy3laNBiR/iwQWfW0
/tjVvHsyWAcBXep097+zBfLRZw/yxPAkYF427LNzM1Rfa+9mCQowiCr30kxQ9Svx
neKLLs/S/StHV7Bcx7BmSVVfYwSVZQYRl0uflFoTSnWNrBKNTw89BBJJRYdMIIT+
+5EzNyYyt4wjFJrEWLVfnrtnzoVpBT/YRS59jh588nVbLybyYpjSPu6bT2VbRqDS
TIbuhqDcVQarEW0aAZB28xrRNscFCKUYZ6SOdPSgtdhmU+7nWgbw+VzF35AgiB2o
z9a7zvhdyrxYlMs6paQ6v2vuJSWZOA==
=LmZf
-----END PGP SIGNATURE-----
--=-=-=--


From nobody Wed Oct 21 12:11:26 2020
Return-Path: <j@w1.fi>
X-Original-To: emu@ietfa.amsl.com
Delivered-To: emu@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 703D33A129A for <emu@ietfa.amsl.com>; Wed, 21 Oct 2020 12:11:24 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.899
X-Spam-Level: 
X-Spam-Status: No, score=-1.899 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, SPF_HELO_NONE=0.001, SPF_PASS=-0.001, URIBL_BLOCKED=0.001] autolearn=ham autolearn_force=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 Ec8KzZ5a7RuI for <emu@ietfa.amsl.com>; Wed, 21 Oct 2020 12:11:23 -0700 (PDT)
Received: from li674-96.members.linode.com (mail.w1.fi [212.71.239.96]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id D389E3A1296 for <emu@ietf.org>; Wed, 21 Oct 2020 12:11:22 -0700 (PDT)
Received: from localhost (localhost [127.0.0.1]) by li674-96.members.linode.com (Postfix) with ESMTP id 9171611A21; Wed, 21 Oct 2020 19:11:20 +0000 (UTC)
X-Virus-Scanned: Debian amavisd-new at w1.fi
Received: from li674-96.members.linode.com ([127.0.0.1]) by localhost (mail.w1.fi [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id fiI4KimdU8JZ; Wed, 21 Oct 2020 19:11:18 +0000 (UTC)
Received: by jm (sSMTP sendmail emulation); Wed, 21 Oct 2020 22:08:24 +0300
Date: Wed, 21 Oct 2020 22:08:24 +0300
From: Jouni Malinen <j@w1.fi>
To: Joseph Salowey <joe@salowey.net>
Cc: EMU WG <emu@ietf.org>, "Oleg Pekar (olpekar)" <olpekar@cisco.com>, Jorge Vergara <jovergar=40microsoft.com@dmarc.ietf.org>
Message-ID: <20201021190824.GA8827@w1.fi>
References: <CAOgPGoC83neA1mGBwbA5Bqfj1K3CFOvphb0ZNwcMeUAFyB1PRw@mail.gmail.com>
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
In-Reply-To: <CAOgPGoC83neA1mGBwbA5Bqfj1K3CFOvphb0ZNwcMeUAFyB1PRw@mail.gmail.com>
Archived-At: <https://mailarchive.ietf.org/arch/msg/emu/jKkgx845xHzC6Am5Nd2_Kz1W8mE>
Subject: Re: [Emu] Proposed resolution for TEAP errata 5127
X-BeenThere: emu@ietf.org
X-Mailman-Version: 2.1.29
Precedence: list
List-Id: "EAP Methods Update \(EMU\)" <emu.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/emu>, <mailto:emu-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/emu/>
List-Post: <mailto:emu@ietf.org>
List-Help: <mailto:emu-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/emu>, <mailto:emu-request@ietf.org?subject=subscribe>
X-List-Received-Date: Wed, 21 Oct 2020 19:11:25 -0000

On Wed, Oct 21, 2020 at 09:30:33AM -0700, Joseph Salowey wrote:
> Errata 5127: https://www.rfc-editor.org/errata/eid5127
> Proposed State: Verified
> Revision:
> Section 5.2.
> OLD
> 
> IMSK = First 32 octets of TLS-PRF(EMSK, "TEAPbindkey@ietf.org" |
>      "\0" | 64)
> 
> NEW
> 
> IMSK = First 32 octets of TLS-PRF(EMSK, "TEAPbindkey@ietf.org" |
>    '/0', 64)

Why would this change "\0" to '/0'?

How is that 64 supposed to be encoded if it is the "seed" argument to
PRF(secret, label, seed) define in RFC 5246 Section 5?

> Notes:
> According to
> 
> RFC5246 The Transport Layer Security (TLS) Protocol Version 1.2
> 
> 5. HMAC and the Pseudorandom Function
> 
> "TLS's PRF is created by applying P_hash to the secret as:
> 
> PRF(secret, label, seed) = P_<hash>(secret, label + seed)"
> 
> In this case the seed is the 2-byte length of the output as defined by RFC
> 5295.  In terms of P_<Hash> the derivation would look like:
> 
> IMSK = P_<Hash>(EMSK, "TEAPbindkey@ietf.org" | 0x00 | 0x00 | 0x40)

Using P_hash(EMSK, "TEAPbindkey@ietf.org" | 0x00 | 0x00 | 0x40) looks
correct, but it looks strange to me if we are trying to include the
first 0x00 at the end of the "label" argument to PRF(secret, label,
seed) especially when the label is define to be "an ASCII string. It
should be included in the exact form it is given without a length byte
or trailing null character". I would have expected
"TEAPbindkey@ietf.org" to be the "label" while 0x00 | 0x00 | 0x40 would
be the "seed". In other words:

IMSK = First 32 octets of TLS-PRF(EMSK, "TEAPbindkey@ietf.org",
				  0x00 | 0x00 | 0x40).


Please note that this is followed by this explanation:

     where "|" denotes concatenation, EMSK is the EMSK from the inner
     method, "TEAPbindkey@ietf.org" consists the ASCII value for the
     label "TEAPbindkey@ietf.org" (without quotes), "\0" = is a NULL
     octet (0x00 in hex), length is the 2-octet unsigned integer in
     network byte order, and TLS-PRF is the PRF negotiated as part of
     TLS handshake [RFC5246].

Using "64" as the seed would require the reader to interpret 64 to be
the "length" and use the "2-octet unsigned integer in network byte
order" from that to determine the exact encoding of the seed. And the
first 0x00 as part of the label to TLS-PRF would be be confusing as well
with this explanation that is clearly defining the label without
including the explicitly noted "\0" after the label.

-- 
Jouni Malinen                                            PGP id EFC895FA


From nobody Wed Oct 21 14:15:04 2020
Return-Path: <joe@salowey.net>
X-Original-To: emu@ietfa.amsl.com
Delivered-To: emu@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 0D0D53A093D for <emu@ietfa.amsl.com>; Wed, 21 Oct 2020 14:15:03 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.898
X-Spam-Level: 
X-Spam-Status: No, score=-1.898 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, HTML_MESSAGE=0.001, SPF_HELO_NONE=0.001, SPF_PASS=-0.001, URIBL_BLOCKED=0.001] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (2048-bit key) header.d=salowey-net.20150623.gappssmtp.com
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 xCjG6Y4xLjCv for <emu@ietfa.amsl.com>; Wed, 21 Oct 2020 14:15:01 -0700 (PDT)
Received: from mail-qk1-x72b.google.com (mail-qk1-x72b.google.com [IPv6:2607:f8b0:4864:20::72b]) (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 EE5EC3A0924 for <emu@ietf.org>; Wed, 21 Oct 2020 14:15:00 -0700 (PDT)
Received: by mail-qk1-x72b.google.com with SMTP id v200so4168366qka.0 for <emu@ietf.org>; Wed, 21 Oct 2020 14:15:00 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=salowey-net.20150623.gappssmtp.com; s=20150623; h=mime-version:references:in-reply-to:from:date:message-id:subject:to :cc; bh=JdnZpqxnzhbLBmLmr9Wm4ZQJ/ypHnDgCNyhymAsR0kw=; b=RflAIq6JWhhItLLVjqTds8aRPS0DNblkYqlFHLMb3w9Kab+JazaY1RbaiYV2/WmVyX gJoV8weTXV6g2YlwlNcOQ2gkqEXV8NUeqGWAqnoZxdoUlVuYTt3Yt/ABjU862sR5p9gg 0miGAqlZeWKbZhP702vMGVvNh3oGIqBnRNwrchEJiDPsYMN2XLgtaUb4wr9RAiE1WxSU JpbdozUEyWD+SWf3+8HYMDZ1v+dKULmL+nx35nTABu10/S80OCx2pFoJ7s1rzUzp+tju c4s0FMCOLAXZ8xb2XAMIFlev4iTqc5U8uUUI7FtjfV8/jQfMBqo2jy/uhhXxo+nOy/jx eMBw==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:mime-version:references:in-reply-to:from:date :message-id:subject:to:cc; bh=JdnZpqxnzhbLBmLmr9Wm4ZQJ/ypHnDgCNyhymAsR0kw=; b=eCH2eRVID6yfuHpuggKMfrnMQ/4GQOKHEsk2Z5hfVXqcXS9AkcCFL4rtd5Rwf3f3B0 ZRzuhA+iPd6uYaKZ7AnaMeEvZnvt14xox/e33syRjv7SQhLHRZOZnbZ6N7pfBrv5BUt2 KWd/Zw9p3ACC17yBIfDgBqqIkAmQr15UNrPNIOA2UByGBXVnJC5WdkcEmajY7qvP1ICf ET+Xab4VvAcaa2pEvDLeKvwqi6FunDUZI9HmdX53a+ixIHoBXuOsEARqsRB8AsJdUdbD jyHj7etEp4VPYVW6tr7MYvVWh/9O2Zz9FTrCA17ZGqhPnsA07kOht5ObRr6OneHxvyrv 3r+g==
X-Gm-Message-State: AOAM532mlnAGV2168Ravp3/Up52S4uiQl2/txhZgD/oRfXtW5uPEAnuH J+Gy9GFXMqwgespfof7UXEhCyaFyKDrxIp0ALGiwKQ==
X-Google-Smtp-Source: ABdhPJw0OivYUF/F9oBQIuDRtKUs6F15XYL6REzxdfoyeDvWhp//Nz3rBWSi8aehnsFmkv5OAMoNNzYPYVFkK7+T5zg=
X-Received: by 2002:a37:9b04:: with SMTP id d4mr5076709qke.472.1603314896715;  Wed, 21 Oct 2020 14:14:56 -0700 (PDT)
MIME-Version: 1.0
References: <CAOgPGoC83neA1mGBwbA5Bqfj1K3CFOvphb0ZNwcMeUAFyB1PRw@mail.gmail.com> <20201021190824.GA8827@w1.fi>
In-Reply-To: <20201021190824.GA8827@w1.fi>
From: Joseph Salowey <joe@salowey.net>
Date: Wed, 21 Oct 2020 14:14:45 -0700
Message-ID: <CAOgPGoCqdFucScjOp30aj3EcTZ72x_aOBSOBYD1r04Us_8ZUNg@mail.gmail.com>
To: Jouni Malinen <j@w1.fi>
Cc: EMU WG <emu@ietf.org>, "Oleg Pekar (olpekar)" <olpekar@cisco.com>,  Jorge Vergara <jovergar=40microsoft.com@dmarc.ietf.org>
Content-Type: multipart/alternative; boundary="000000000000e1d15c05b234d679"
Archived-At: <https://mailarchive.ietf.org/arch/msg/emu/QW--cGVENOug98O-Z2eTN58GHvc>
Subject: Re: [Emu] Proposed resolution for TEAP errata 5127
X-BeenThere: emu@ietf.org
X-Mailman-Version: 2.1.29
Precedence: list
List-Id: "EAP Methods Update \(EMU\)" <emu.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/emu>, <mailto:emu-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/emu/>
List-Post: <mailto:emu@ietf.org>
List-Help: <mailto:emu-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/emu>, <mailto:emu-request@ietf.org?subject=subscribe>
X-List-Received-Date: Wed, 21 Oct 2020 21:15:03 -0000

--000000000000e1d15c05b234d679
Content-Type: text/plain; charset="UTF-8"

On Wed, Oct 21, 2020 at 12:11 PM Jouni Malinen <j@w1.fi> wrote:

> On Wed, Oct 21, 2020 at 09:30:33AM -0700, Joseph Salowey wrote:
> > Errata 5127: https://www.rfc-editor.org/errata/eid5127
> > Proposed State: Verified
> > Revision:
> > Section 5.2.
> > OLD
> >
> > IMSK = First 32 octets of TLS-PRF(EMSK, "TEAPbindkey@ietf.org" |
> >      "\0" | 64)
> >
> > NEW
> >
> > IMSK = First 32 octets of TLS-PRF(EMSK, "TEAPbindkey@ietf.org" |
> >    '/0', 64)
>
> Why would this change "\0" to '/0'?
>
> [Joe] that was my mistake should be "/0"


> How is that 64 supposed to be encoded if it is the "seed" argument to
> PRF(secret, label, seed) define in RFC 5246 Section 5?
>
>
[Joe] 7170 says "length is the 2-octet unsigned integer in network byte
order"


> > Notes:
> > According to
> >
> > RFC5246 The Transport Layer Security (TLS) Protocol Version 1.2
> >
> > 5. HMAC and the Pseudorandom Function
> >
> > "TLS's PRF is created by applying P_hash to the secret as:
> >
> > PRF(secret, label, seed) = P_<hash>(secret, label + seed)"
> >
> > In this case the seed is the 2-byte length of the output as defined by
> RFC
> > 5295.  In terms of P_<Hash> the derivation would look like:
> >
> > IMSK = P_<Hash>(EMSK, "TEAPbindkey@ietf.org" | 0x00 | 0x00 | 0x40)
>
> Using P_hash(EMSK, "TEAPbindkey@ietf.org" | 0x00 | 0x00 | 0x40) looks
> correct, but it looks strange to me if we are trying to include the
> first 0x00 at the end of the "label" argument to PRF(secret, label,
> seed) especially when the label is define to be "an ASCII string. It
> should be included in the exact form it is given without a length byte
> or trailing null character". I would have expected
> "TEAPbindkey@ietf.org" to be the "label" while 0x00 | 0x00 | 0x40 would
> be the "seed". In other words:
>
> IMSK = First 32 octets of TLS-PRF(EMSK, "TEAPbindkey@ietf.org",
>                                   0x00 | 0x00 | 0x40).
>
>
[Joe] Yes I agree that is better how about this as the text change

IMSK = First 32 octets of TLS-PRF(EMSK, "TEAPbindkey@ietf.org", "\0" |  64)


>
> Please note that this is followed by this explanation:
>
>      where "|" denotes concatenation, EMSK is the EMSK from the inner
>      method, "TEAPbindkey@ietf.org" consists the ASCII value for the
>      label "TEAPbindkey@ietf.org" (without quotes), "\0" = is a NULL
>      octet (0x00 in hex), length is the 2-octet unsigned integer in
>      network byte order, and TLS-PRF is the PRF negotiated as part of
>      TLS handshake [RFC5246].
>
> Using "64" as the seed would require the reader to interpret 64 to be
> the "length" and use the "2-octet unsigned integer in network byte
> order" from that to determine the exact encoding of the seed. And the
> first 0x00 as part of the label to TLS-PRF would be be confusing as well
> with this explanation that is clearly defining the label without
> including the explicitly noted "\0" after the label.
>
> --
> Jouni Malinen                                            PGP id EFC895FA
>

--000000000000e1d15c05b234d679
Content-Type: text/html; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable

<div dir=3D"ltr"><div dir=3D"ltr"><br></div><br><div class=3D"gmail_quote">=
<div dir=3D"ltr" class=3D"gmail_attr">On Wed, Oct 21, 2020 at 12:11 PM Joun=
i Malinen &lt;<a href=3D"mailto:j@w1.fi">j@w1.fi</a>&gt; wrote:<br></div><b=
lockquote class=3D"gmail_quote" style=3D"margin:0px 0px 0px 0.8ex;border-le=
ft:1px solid rgb(204,204,204);padding-left:1ex">On Wed, Oct 21, 2020 at 09:=
30:33AM -0700, Joseph Salowey wrote:<br>
&gt; Errata 5127: <a href=3D"https://www.rfc-editor.org/errata/eid5127" rel=
=3D"noreferrer" target=3D"_blank">https://www.rfc-editor.org/errata/eid5127=
</a><br>
&gt; Proposed State: Verified<br>
&gt; Revision:<br>
&gt; Section 5.2.<br>
&gt; OLD<br>
&gt; <br>
&gt; IMSK =3D First 32 octets of TLS-PRF(EMSK, &quot;<a href=3D"mailto:TEAP=
bindkey@ietf.org" target=3D"_blank">TEAPbindkey@ietf.org</a>&quot; |<br>
&gt;=C2=A0 =C2=A0 =C2=A0 &quot;\0&quot; | 64)<br>
&gt; <br>
&gt; NEW<br>
&gt; <br>
&gt; IMSK =3D First 32 octets of TLS-PRF(EMSK, &quot;<a href=3D"mailto:TEAP=
bindkey@ietf.org" target=3D"_blank">TEAPbindkey@ietf.org</a>&quot; |<br>
&gt;=C2=A0 =C2=A0 &#39;/0&#39;, 64)<br>
<br>
Why would this change &quot;\0&quot; to &#39;/0&#39;?<br>
<br></blockquote><div>[Joe] that was my mistake should be &quot;/0&quot;</d=
iv><div>=C2=A0</div><blockquote class=3D"gmail_quote" style=3D"margin:0px 0=
px 0px 0.8ex;border-left:1px solid rgb(204,204,204);padding-left:1ex">
How is that 64 supposed to be encoded if it is the &quot;seed&quot; argumen=
t to<br>
PRF(secret, label, seed) define in RFC 5246 Section 5?<br>
<br></blockquote><div><br></div><div>[Joe] 7170 says=C2=A0&quot;length is t=
he 2-octet unsigned integer in network byte order&quot;</div><div>=C2=A0</d=
iv><blockquote class=3D"gmail_quote" style=3D"margin:0px 0px 0px 0.8ex;bord=
er-left:1px solid rgb(204,204,204);padding-left:1ex">
&gt; Notes:<br>
&gt; According to<br>
&gt; <br>
&gt; RFC5246 The Transport Layer Security (TLS) Protocol Version 1.2<br>
&gt; <br>
&gt; 5. HMAC and the Pseudorandom Function<br>
&gt; <br>
&gt; &quot;TLS&#39;s PRF is created by applying P_hash to the secret as:<br=
>
&gt; <br>
&gt; PRF(secret, label, seed) =3D P_&lt;hash&gt;(secret, label + seed)&quot=
;<br>
&gt; <br>
&gt; In this case the seed is the 2-byte length of the output as defined by=
 RFC<br>
&gt; 5295.=C2=A0 In terms of P_&lt;Hash&gt; the derivation would look like:=
<br>
&gt; <br>
&gt; IMSK =3D P_&lt;Hash&gt;(EMSK, &quot;<a href=3D"mailto:TEAPbindkey@ietf=
.org" target=3D"_blank">TEAPbindkey@ietf.org</a>&quot; | 0x00 | 0x00 | 0x40=
)<br>
<br>
Using P_hash(EMSK, &quot;<a href=3D"mailto:TEAPbindkey@ietf.org" target=3D"=
_blank">TEAPbindkey@ietf.org</a>&quot; | 0x00 | 0x00 | 0x40) looks<br>
correct, but it looks strange to me if we are trying to include the<br>
first 0x00 at the end of the &quot;label&quot; argument to PRF(secret, labe=
l,<br>
seed) especially when the label is define to be &quot;an ASCII string. It<b=
r>
should be included in the exact form it is given without a length byte<br>
or trailing null character&quot;. I would have expected<br>
&quot;<a href=3D"mailto:TEAPbindkey@ietf.org" target=3D"_blank">TEAPbindkey=
@ietf.org</a>&quot; to be the &quot;label&quot; while 0x00 | 0x00 | 0x40 wo=
uld<br>
be the &quot;seed&quot;. In other words:<br>
<br>
IMSK =3D First 32 octets of TLS-PRF(EMSK, &quot;<a href=3D"mailto:TEAPbindk=
ey@ietf.org" target=3D"_blank">TEAPbindkey@ietf.org</a>&quot;,<br>
=C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=
=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 0x00 | 0x00 | 0x40).<br>
<br></blockquote><div><br></div><div>[Joe] Yes I agree that is better how a=
bout this as the text change</div><div><br></div><div>IMSK =3D First 32 oct=
ets of TLS-PRF(EMSK, &quot;<a href=3D"mailto:TEAPbindkey@ietf.org" target=
=3D"_blank">TEAPbindkey@ietf.org</a>&quot;, &quot;\0&quot; |=C2=A0 64)<br><=
/div><div>=C2=A0</div><blockquote class=3D"gmail_quote" style=3D"margin:0px=
 0px 0px 0.8ex;border-left:1px solid rgb(204,204,204);padding-left:1ex">
<br>
Please note that this is followed by this explanation:<br>
<br>
=C2=A0 =C2=A0 =C2=A0where &quot;|&quot; denotes concatenation, EMSK is the =
EMSK from the inner<br>
=C2=A0 =C2=A0 =C2=A0method, &quot;<a href=3D"mailto:TEAPbindkey@ietf.org" t=
arget=3D"_blank">TEAPbindkey@ietf.org</a>&quot; consists the ASCII value fo=
r the<br>
=C2=A0 =C2=A0 =C2=A0label &quot;<a href=3D"mailto:TEAPbindkey@ietf.org" tar=
get=3D"_blank">TEAPbindkey@ietf.org</a>&quot; (without quotes), &quot;\0&qu=
ot; =3D is a NULL<br>
=C2=A0 =C2=A0 =C2=A0octet (0x00 in hex), length is the 2-octet unsigned int=
eger in<br>
=C2=A0 =C2=A0 =C2=A0network byte order, and TLS-PRF is the PRF negotiated a=
s part of<br>
=C2=A0 =C2=A0 =C2=A0TLS handshake [RFC5246].<br>
<br>
Using &quot;64&quot; as the seed would require the reader to interpret 64 t=
o be<br>
the &quot;length&quot; and use the &quot;2-octet unsigned integer in networ=
k byte<br>
order&quot; from that to determine the exact encoding of the seed. And the<=
br>
first 0x00 as part of the label to TLS-PRF would be be confusing as well<br=
>
with this explanation that is clearly defining the label without<br>
including the explicitly noted &quot;\0&quot; after the label.<br>
<br>
-- <br>
Jouni Malinen=C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0=
 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=
=A0 =C2=A0 =C2=A0 PGP id EFC895FA<br>
</blockquote></div></div>

--000000000000e1d15c05b234d679--


From nobody Wed Oct 21 14:34:43 2020
Return-Path: <joe@salowey.net>
X-Original-To: emu@ietfa.amsl.com
Delivered-To: emu@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 95B3B3A09BC for <emu@ietfa.amsl.com>; Wed, 21 Oct 2020 14:34:42 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.898
X-Spam-Level: 
X-Spam-Status: No, score=-1.898 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, HTML_MESSAGE=0.001, SPF_HELO_NONE=0.001, SPF_PASS=-0.001, URIBL_BLOCKED=0.001] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (2048-bit key) header.d=salowey-net.20150623.gappssmtp.com
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 rMYI_mLR_3m8 for <emu@ietfa.amsl.com>; Wed, 21 Oct 2020 14:34:41 -0700 (PDT)
Received: from mail-qk1-x736.google.com (mail-qk1-x736.google.com [IPv6:2607:f8b0:4864:20::736]) (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 401813A09BA for <emu@ietf.org>; Wed, 21 Oct 2020 14:34:41 -0700 (PDT)
Received: by mail-qk1-x736.google.com with SMTP id z6so4194066qkz.4 for <emu@ietf.org>; Wed, 21 Oct 2020 14:34:41 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=salowey-net.20150623.gappssmtp.com; s=20150623; h=mime-version:from:date:message-id:subject:to; bh=mNn1sG/R/5w+YswrQk7lg3IcpaD6djY/Ua050nIQ2F0=; b=ow15xM/ysFA0lcYCk8K3YdKA4xmMpx/EwoRXM8YaxjrvJM7OdC4pVoqpM+UQSqdLW5 cGn7W/l1fe+ha6Tt/JHTddQi3PheR2AzTB1nbM/PbkoHP3Y8SCkIYYcsEoT82k1MnjRw KgR6IfYs5vxqFdwxAlHpYP2L5tbWnUnTI3yXNNXypDNrDGtoaBR9mh+idmTx3URj8VU9 0q9wNc7MxV40zw8JwlnB1tns4KTYiXcdGQboHZZJ/dMh+lO09alQ5i2VwkgbbYizrJLX fRxRVzWrGXetV6SWtGlBx8bCKx3rPqVpPaDDsebvRucp80PvNttPo0XCk+OgXYAc9gUl j3sg==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:mime-version:from:date:message-id:subject:to; bh=mNn1sG/R/5w+YswrQk7lg3IcpaD6djY/Ua050nIQ2F0=; b=Ac41K6WdbDn0G9xjvxT15k2PaCk+NuSxI0ePA3jeaG4c5ctwpVmYzms2JHooIrfI6M ioL6jpzdrv5gl6ImA8jbPWlnOGgwnyc+x8CRFhHj5T0rTgzfib+O5HycJrFz9NNi6g5d 94XFkqSt1XjhyaN24Tsly/h40wcREBpLJ1wmevSwoT2bxcIZw1ZywVMpae6a7CGn86xM oMCygsZ1gBXdVwdpNwIf2TdjYjExU7bHHPNyIXiw3MO2+AabvNku+7aHiF8KD5dNFb69 r4uHD+STuAknga9TWPJ70njHUdDi4KXd5dbAPO2Usvqtx0kwcrj/5GSJ7kKunAV+jY5w o//Q==
X-Gm-Message-State: AOAM5323ljKKE54tAMuTS1z4/59/jul5Zr6k8TNT0DE/9am+g1Q+BMLU EkXJWH3W7xgPhbW0S79RjerQ9JNpfaK1YyzUX6t7EFN6YTiVLA==
X-Google-Smtp-Source: ABdhPJw04FS8X9MtujiIDcD0E2FvDpI7aNnPfGegsiRRfF9sjpVgbI+RNJn+Ksx9OGIxAhAULCpLzfdT5llibPI1hm0=
X-Received: by 2002:a37:849:: with SMTP id 70mr5297171qki.332.1603316080015; Wed, 21 Oct 2020 14:34:40 -0700 (PDT)
MIME-Version: 1.0
From: Joseph Salowey <joe@salowey.net>
Date: Wed, 21 Oct 2020 14:34:29 -0700
Message-ID: <CAOgPGoBay+GG=F8WV0gLOOwLtGdGALGw_cM2JoAnXOtmGq7A+w@mail.gmail.com>
To: EMU WG <emu@ietf.org>, Jouni Malinen <j@w1.fi>,  Jorge Vergara <jovergar=40microsoft.com@dmarc.ietf.org>,  "Oleg Pekar (olpekar)" <olpekar@cisco.com>
Content-Type: multipart/alternative; boundary="000000000000699c3f05b2351d20"
Archived-At: <https://mailarchive.ietf.org/arch/msg/emu/eCL5I9lvJiq5ruRyRiY3eHg1CSA>
Subject: [Emu] Proposed resolution for TEAP errata for 5128
X-BeenThere: emu@ietf.org
X-Mailman-Version: 2.1.29
Precedence: list
List-Id: "EAP Methods Update \(EMU\)" <emu.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/emu>, <mailto:emu-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/emu/>
List-Post: <mailto:emu@ietf.org>
List-Help: <mailto:emu-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/emu>, <mailto:emu-request@ietf.org?subject=subscribe>
X-List-Received-Date: Wed, 21 Oct 2020 21:34:43 -0000

--000000000000699c3f05b2351d20
Content-Type: text/plain; charset="UTF-8"

Errata 5128: https://www.rfc-editor.org/errata/eid5128
Proposed State: Verified
Revision:

Section 5.2. says


IMCK[j] = TLS-PRF(S-IMCK[j-1], "Inner Methods Compound Keys",
                IMSK[j], 60)

It should say:

IMCK[j] = TLS-PRF(S-IMCK[j-1], "Inner Methods Compound Keys", IMSK[j] | 60)

Note:
According to

RFC5246 The Transport Layer Security (TLS) Protocol Version 1.2

5. HMAC and the Pseudorandom Function

"TLS's PRF is created by applying P_hash to the secret as:

PRF(secret, label, seed) = P_<hash>(secret, label + seed)"

In terms of P_<hash> this would look like the following with the length
represented as a 2 byte value in network byte order:

IMCK[j] = P_<hash>(S-IMCK[j-1], "Inner Methods Compound Keys" | IMSK[j] |
0x00 | 0x3C)

--000000000000699c3f05b2351d20
Content-Type: text/html; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable

<div dir=3D"ltr">Errata 5128:=C2=A0<a href=3D"https://www.rfc-editor.org/er=
rata/eid5128">https://www.rfc-editor.org/errata/eid5128</a><div>Proposed St=
ate: Verified</div><div>Revision:</div><div><br></div><div>Section 5.2. say=
s</div><div><p style=3D"margin:5px 5px 10px"><br>IMCK[j] =3D TLS-PRF(S-IMCK=
[j-1], &quot;Inner Methods Compound Keys&quot;,<br>=C2=A0 =C2=A0 =C2=A0 =C2=
=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 IMSK[j], 60)<br><br>It should say:<br><br>I=
MCK[j] =3D TLS-PRF(S-IMCK[j-1], &quot;Inner Methods Compound Keys&quot;,=C2=
=A0<span style=3D"color:rgb(44,67,83);font-family:Arial,Helvetica,sans-seri=
f;font-size:14px">IMSK[j] | 60)</span><br></p><p style=3D"margin:5px 5px 10=
px"><span style=3D"color:rgb(44,67,83);font-family:Arial,Helvetica,sans-ser=
if;font-size:14px">Note:=C2=A0=C2=A0</span></p>According to<br><br>RFC5246 =
The Transport Layer Security (TLS) Protocol Version 1.2<br><br>5. HMAC and =
the Pseudorandom Function<br><br>&quot;TLS&#39;s PRF is created by applying=
 P_hash to the secret as:<br><br>PRF(secret, label, seed) =3D P_&lt;hash&gt=
;(secret, label + seed)&quot;</div><div><br></div><div>In terms of P_&lt;ha=
sh&gt; this would look like the following with the length represented as a =
2 byte value in network byte order:</div><div><br></div><div>IMCK[j] =3D P_=
&lt;hash&gt;(S-IMCK[j-1], &quot;Inner Methods Compound Keys&quot; |=C2=A0<s=
pan style=3D"color:rgb(44,67,83);font-size:14px">IMSK[j] | 0x00 | 0x3C)</sp=
an></div><div><span style=3D"color:rgb(44,67,83);font-size:14px"><br></span=
></div><div><span style=3D"color:rgb(44,67,83);font-size:14px"><br></span><=
/div></div>

--000000000000699c3f05b2351d20--


From nobody Wed Oct 21 14:47:35 2020
Return-Path: <joe@salowey.net>
X-Original-To: emu@ietfa.amsl.com
Delivered-To: emu@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 869183A09EB for <emu@ietfa.amsl.com>; Wed, 21 Oct 2020 14:47:33 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.898
X-Spam-Level: 
X-Spam-Status: No, score=-1.898 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, HTML_MESSAGE=0.001, SPF_HELO_NONE=0.001, SPF_PASS=-0.001, URIBL_BLOCKED=0.001] autolearn=unavailable autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (2048-bit key) header.d=salowey-net.20150623.gappssmtp.com
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 yrrWUv_ZpluN for <emu@ietfa.amsl.com>; Wed, 21 Oct 2020 14:47:32 -0700 (PDT)
Received: from mail-qv1-xf2d.google.com (mail-qv1-xf2d.google.com [IPv6:2607:f8b0:4864:20::f2d]) (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 3514F3A09F1 for <emu@ietf.org>; Wed, 21 Oct 2020 14:47:31 -0700 (PDT)
Received: by mail-qv1-xf2d.google.com with SMTP id de3so1980482qvb.5 for <emu@ietf.org>; Wed, 21 Oct 2020 14:47:31 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=salowey-net.20150623.gappssmtp.com; s=20150623; h=mime-version:from:date:message-id:subject:to; bh=T6TEHwuTkqT7RVC1+bpW9YHX0mr0w47xxqE2nj5IQiY=; b=NrVxYWALmKKg92vmqdoa3VF1lGMfiFQQDaGiA2XQ3VIhIIT9b7+a4MIlc1EvHHgbcO Ufb4h1PmCwOVTu8zMwVkQuc8I0v/V/Hyr5+o/Kb30jXHT0nmOh0240wxnahWuXCfefa1 E6SmhM4necbSTUadTVEM2mA2XTv0U/uPoSLXZPWXTk+DQ6H3Ilj8A8JBOechVQdYJH16 ZwINYDunlSNFM2BIFk5zXKJUH+QtSEPXjZpWg+7taFunUAWlv9a6H34yMvBCOd+cC9AO MnOm28u5eQL9WMJk65esIF5Km2kQ7+tmBuNab6f08Fm0bRgEvLalragj4sVMehLQANJE h8cA==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:mime-version:from:date:message-id:subject:to; bh=T6TEHwuTkqT7RVC1+bpW9YHX0mr0w47xxqE2nj5IQiY=; b=H0+8k/I+ZkTSCIJfXGu4VUP5YWJzcoHtHAhRiaKBt7yJIlefeaw3DcOlcH+xOrWO6O 0fS6U7H36Wi0QOAn55F5MX9nkeZGMu949QzdWNwRg0JVnoeevM3Y/vFGQ+1QCecv511j 0ZPuWq1ZP4vtZT56Rli4mIpGBIiiljQrAY3dDA1CMU8lcOO3aaGaTn3mbVgXb747bjrt Q5D/ypqYfk4IsxZ0scFlRpu9VqM7n4CSDJFQEFO5oECNjaKmVNyDtk4AKkqw1Xf7t6vL tZMWYJ3YSnMuZyOE62YA0BWv5Sqz2Zm7YGo1N/olZV/eRQCd2Os4kkCoQEGQR37LkxEL /BKA==
X-Gm-Message-State: AOAM532IvpdHRskMH26drEE6c3tG/928svB0TxXbtC5Zh+jLQiXnGVtJ hExnkc6LWu1sPbQ4kL7gICuR9KiVNkkLR7lzsfSni6vJ1bDdcA==
X-Google-Smtp-Source: ABdhPJwsFn4Mf2vTZuS7fidH28V1ea5CY7fKSR/PSp7BDfdPVJH5aOTe3ifttvc+1p9ACMJ36hwawRXInPfo1QO1eKw=
X-Received: by 2002:a0c:f102:: with SMTP id i2mr4956999qvl.29.1603316849992; Wed, 21 Oct 2020 14:47:29 -0700 (PDT)
MIME-Version: 1.0
From: Joseph Salowey <joe@salowey.net>
Date: Wed, 21 Oct 2020 14:47:19 -0700
Message-ID: <CAOgPGoCmYCEKgE6P_Ja5VRLh4M1jWSML_WNuqdHA-t2TibBnjA@mail.gmail.com>
To: EMU WG <emu@ietf.org>, Jouni Malinen <j@w1.fi>,  Jorge Vergara <jovergar=40microsoft.com@dmarc.ietf.org>,  Oleg Pekar <oleg.pekar.2017@gmail.com>
Content-Type: multipart/alternative; boundary="0000000000004e79b705b2354b35"
Archived-At: <https://mailarchive.ietf.org/arch/msg/emu/Ga8evJZzLG8lCML-kkxV6G_JS0E>
Subject: [Emu] Proposed resolution for TEAP errata 5765
X-BeenThere: emu@ietf.org
X-Mailman-Version: 2.1.29
Precedence: list
List-Id: "EAP Methods Update \(EMU\)" <emu.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/emu>, <mailto:emu-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/emu/>
List-Post: <mailto:emu@ietf.org>
List-Help: <mailto:emu-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/emu>, <mailto:emu-request@ietf.org?subject=subscribe>
X-List-Received-Date: Wed, 21 Oct 2020 21:47:34 -0000

--0000000000004e79b705b2354b35
Content-Type: text/plain; charset="UTF-8"

Errata 5765: https://www.rfc-editor.org/errata/eid5765
Proposed Status: Verified
Revision: (unmodified from original posting)

Section 4.2.2 says:

   M

      Mandatory, set to one (1)

It should say:

   M

      0 (Optional)

Notes:

Authority-ID TLV is used only as an Outer TLV (in TEAP/Start) and Section
4.3.1 mandates all Outer TLVs to be marked as optional ("Outer TLVs MUST be
marked as optional"). As such, Section 4.2.2 is incorrect in claiming the
Authority-ID TLV to use M=1.

--0000000000004e79b705b2354b35
Content-Type: text/html; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable

<div dir=3D"ltr">Errata 5765:=C2=A0<a href=3D"https://www.rfc-editor.org/er=
rata/eid5765">https://www.rfc-editor.org/errata/eid5765</a><div>Proposed St=
atus: Verified</div><div>Revision: (unmodified from original posting)</div>=
<div><br></div>Section 4.2.2 says:<br><br>=C2=A0 =C2=A0M<br><br>=C2=A0 =C2=
=A0 =C2=A0 Mandatory, set to one (1)<br><br>It should say:<br><br>=C2=A0 =
=C2=A0M<br><br>=C2=A0 =C2=A0 =C2=A0 0 (Optional)<br><br>Notes:<br><br>Autho=
rity-ID TLV is used only as an Outer TLV (in TEAP/Start) and Section 4.3.1 =
mandates all Outer TLVs to be marked as optional (&quot;Outer TLVs MUST be =
marked as optional&quot;). As such, Section 4.2.2 is incorrect in claiming =
the Authority-ID TLV to use M=3D1.</div>

--0000000000004e79b705b2354b35--


From nobody Wed Oct 21 15:20:32 2020
Return-Path: <jovergar@microsoft.com>
X-Original-To: emu@ietfa.amsl.com
Delivered-To: emu@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 9DCDC3A0A86 for <emu@ietfa.amsl.com>; Wed, 21 Oct 2020 15:20:31 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.001
X-Spam-Level: 
X-Spam-Status: No, score=-2.001 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIMWL_WL_HIGH=-0.001, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, DKIM_VALID_EF=-0.1, HTML_MESSAGE=0.001, HTTPS_HTTP_MISMATCH=0.1, RCVD_IN_MSPIKE_H2=-0.001, SPF_PASS=-0.001, URIBL_BLOCKED=0.001] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (1024-bit key) header.d=microsoft.com
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 A8UW3EcLHOMP for <emu@ietfa.amsl.com>; Wed, 21 Oct 2020 15:20:30 -0700 (PDT)
Received: from NAM12-DM6-obe.outbound.protection.outlook.com (mail-dm6nam12on2111.outbound.protection.outlook.com [40.107.243.111]) (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 100FC3A09E1 for <emu@ietf.org>; Wed, 21 Oct 2020 15:20:29 -0700 (PDT)
ARC-Seal: i=1; a=rsa-sha256; s=arcselector9901; d=microsoft.com; cv=none; b=JYI8DwlO/lQ3vqjEnFJk7BkmNei1eXnQMVfGl5dDe9WnS8oUPqGeBZwf0BaxVWp/speVkHth16q9O29e9doSdcFelxszQ2HLsduSTv2u7IYSsNrD6I6J0oL/uIlrZRgIog3dWEEo0z32CF/1dB4lddAlP4b661DkkMfEwqrOSckpwZKUWk9Qc/UY/y3NgEPHDzrgMqQD7ubJ8EovI1ereGijRGJBVyPEhcySk23pAhszuf0I3bUv1bnS9zBbMplG+K+xmsojzsrPQB8lt9Z9+/RcUTMd6CXoAqr3ly/ZxcFcngqFBby0ywsdNu5NNBdIIcjDv2hdTsjcLXI1LZ99jg==
ARC-Message-Signature: i=1; a=rsa-sha256; c=relaxed/relaxed; d=microsoft.com;  s=arcselector9901; h=From:Date:Subject:Message-ID:Content-Type:MIME-Version:X-MS-Exchange-SenderADCheck; bh=RHXGLxWSB1fx9qzyhO0oQWQ9eM4160X47EfNcTV7u9U=; b=Vl9mEQN3ldiYSYt4Gu6fpwcQGia4iD2U3u0/JN8mhr93a/bRQ0xmlYxZDorzc7XpGmBDiar+X6e7m/u+pLGIvSoUICcSgjEm58ihPF8Fnvr6wGhamfBjOZcDkRGL8oxTQu5CqPU4AbEp7xP1xxMbwsz2VVVfqF7eHRN32lrAbhTKpkixrw8sN907aH2yYHKxShubplBfsuWQXBHPLxvacli/RoImmPlHvvIxI0SNQFKv8lruH0kEOIbXL/5BH89SQe49EK18vtvBRkHXOxmSxLaWGl8eWyXTL5uV7etotO6pqI2/NFiSck7/evxE5hs0Hz3xrf/+YtiAzCbIiGFhyg==
ARC-Authentication-Results: i=1; mx.microsoft.com 1; spf=pass smtp.mailfrom=microsoft.com; dmarc=pass action=none header.from=microsoft.com; dkim=pass header.d=microsoft.com; arc=none
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=microsoft.com; s=selector2; h=From:Date:Subject:Message-ID:Content-Type:MIME-Version:X-MS-Exchange-SenderADCheck; bh=RHXGLxWSB1fx9qzyhO0oQWQ9eM4160X47EfNcTV7u9U=; b=GdYZ1DMFxQv46TMUDKfZJ47ANy1CtNJ7NsGnfzfiUNWZPb6FQSp8BDna96wH+egV0qDk+tMvojlpq+U9+B9HXfS3cKFKwrryaBslwZz+kQlkd/FhnLhEbV4uKM3H2mnIHlTCIEuMID7x97WOX0l8PhOtqWH8TdUK7fqZnelCtHo=
Received: from CH2PR21MB1381.namprd21.prod.outlook.com (2603:10b6:610:8e::12) by CH2PR21MB1526.namprd21.prod.outlook.com (2603:10b6:610:84::8) with Microsoft SMTP Server (version=TLS1_2, cipher=TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384) id 15.20.3499.3; Wed, 21 Oct 2020 22:20:28 +0000
Received: from CH2PR21MB1381.namprd21.prod.outlook.com ([fe80::dfd:b166:92c:5a84]) by CH2PR21MB1381.namprd21.prod.outlook.com ([fe80::dfd:b166:92c:5a84%9]) with mapi id 15.20.3499.017; Wed, 21 Oct 2020 22:20:28 +0000
From: Jorge Vergara <jovergar@microsoft.com>
To: Joseph Salowey <joe@salowey.net>, EMU WG <emu@ietf.org>, Jouni Malinen <j@w1.fi>, "Oleg Pekar (olpekar)" <olpekar@cisco.com>
Thread-Topic: Proposed resolution for TEAP errata for 5128
Thread-Index: AQHWp/H/5iLrTwXdRkW9JLXm9c5wSaminKRA
Date: Wed, 21 Oct 2020 22:20:28 +0000
Message-ID: <CH2PR21MB138143E929DAFE3C893D8144D11C0@CH2PR21MB1381.namprd21.prod.outlook.com>
References: <CAOgPGoBay+GG=F8WV0gLOOwLtGdGALGw_cM2JoAnXOtmGq7A+w@mail.gmail.com>
In-Reply-To: <CAOgPGoBay+GG=F8WV0gLOOwLtGdGALGw_cM2JoAnXOtmGq7A+w@mail.gmail.com>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
msip_labels: MSIP_Label_f42aa342-8706-4288-bd11-ebb85995028c_ActionId=b0024be0-5407-43c3-a5d7-17263b92b5cd; MSIP_Label_f42aa342-8706-4288-bd11-ebb85995028c_ContentBits=0; MSIP_Label_f42aa342-8706-4288-bd11-ebb85995028c_Enabled=true; MSIP_Label_f42aa342-8706-4288-bd11-ebb85995028c_Method=Standard; MSIP_Label_f42aa342-8706-4288-bd11-ebb85995028c_Name=Internal; MSIP_Label_f42aa342-8706-4288-bd11-ebb85995028c_SetDate=2020-10-21T22:05:20Z;  MSIP_Label_f42aa342-8706-4288-bd11-ebb85995028c_SiteId=72f988bf-86f1-41af-91ab-2d7cd011db47;
authentication-results: salowey.net; dkim=none (message not signed) header.d=none;salowey.net; dmarc=none action=none header.from=microsoft.com;
x-originating-ip: [2001:4898:80e8:0:8491:ee7b:fe42:78ce]
x-ms-publictraffictype: Email
x-ms-office365-filtering-ht: Tenant
x-ms-office365-filtering-correlation-id: d0dc81b5-5acf-4e3e-d73a-08d8760f83eb
x-ms-traffictypediagnostic: CH2PR21MB1526:
x-ld-processed: 72f988bf-86f1-41af-91ab-2d7cd011db47,ExtAddr
x-microsoft-antispam-prvs: <CH2PR21MB1526C1FCAAAEDACABCCBB342D11C0@CH2PR21MB1526.namprd21.prod.outlook.com>
x-ms-oob-tlc-oobclassifiers: OLM:9508;
x-ms-exchange-senderadcheck: 1
x-microsoft-antispam: BCL:0;
x-microsoft-antispam-message-info: bBusa54vOo+NyqJexpP90/UgfmA5QfwwXLYksNPFAgkwCrYqAj8+/B4EeHw9gWaXE8MU6gHwSAhCTEcxnCTV3EEDVhPxGLqql2gAXKpmr1TXXsVfyGPtO4fuJnN6D+rbyFSrJH0iI/3x1F8SO99P8tuhsB2RQT33Y20fxB4VILSR74tmnQsgA4mhXZtbDi7YstnKOkLX99R5c0dmtzQkmCx412YmAbYlohhMukCy5q5gmsGHQA4bhhLPiaylnsMxZYAFltgB8rYmuuvNCDoLBgkbSmrTbeDK/o8Ni40QpksruZVuAzd/bLfvvFXakAbjWbD4jIq8Gz5bLkifrOM4C9Q+EjkvpDKNVW+ThZQeQsqib3VLebGGwx6trZ0xjkLxxgRqmGtuowdpBaLdEw7m+loCLxux7X5Axv1DmGifwR5T7oC0gEKptA1qo3ZdTBKl0vhICFjIbpng//EhX6Af4w==
x-forefront-antispam-report: CIP:255.255.255.255; CTRY:; LANG:en; SCL:1; SRV:;  IPV:NLI; SFV:NSPM; H:CH2PR21MB1381.namprd21.prod.outlook.com; PTR:; CAT:NONE;  SFS:(4636009)(366004)(39860400002)(396003)(376002)(136003)(346002)(83380400001)(82960400001)(166002)(82950400001)(66946007)(86362001)(66476007)(64756008)(66446008)(316002)(76116006)(66556008)(8990500004)(55016002)(110136005)(8676002)(10290500003)(6506007)(186003)(9686003)(33656002)(478600001)(8936002)(53546011)(2906002)(52536014)(71200400001)(966005)(7696005)(5660300002)(781001); DIR:OUT; SFP:1102; 
x-ms-exchange-antispam-messagedata: A/YM48sgLMkvJRDuohCMf36KJCjbwv1aWaccnHd9yMv5D7U2Acl9eXWhlsAbtMiZu9LI+xfhDNdTNflGOfg1yr8ULH47Mz9yxIro7rp/GniT9DfaBx1nz5CPJmhdZvjcWtWTedlXIiTaBiBOKcMLL/GcqRZGJ1ml/2qCdPd2+Bjdo4WzRnu2hXt9C5CFbgMSEUV7tMLOSVcKCeaCxQ4aLRtttv0oXFms5U/PpZ6x2qEUNJV36O3mNh3sj9g/VBjn9GxuqLvIY2e+UJViVA+3Aze6Y0atIlDuKdbElCvi5XP6uQiH8tJKK24hkEsiZE0p0Wdok+7Dy1AMUP3LVQSU9yB3RNeA/oM0i9GQ+En4EAsktR6oVO2OuAVJsr0kp7BM3VyAf61A2H6Y/gYNvSPntRmYYy9AcBxTHa7P081e9krzuUnoKz9Unc/iSpNcbPIZzCOGBlTHO7R1RUROHUIJ4jACX/mh/8LUTttQzytNLC3UaKs/xTeWjIKGtEd4ex44e0+xpHINK4pARG515DknSQw2vR5kPTFN4MBjr0vATPnTBoel96EWAqMF8vAtbCY8SvAvBceuLJS/KIiL7Pfu44K0C0N/Q51Da99nbIkg6tVw/dCMPIHANLw9x6MU3aj9wGLDpL8nQ3M6GyZHfxJG50xC26A1GxrN298/W1A9KgavKSeVJ8JC31Q+iYNQSyoZRif4dXrppFFYSboGlQy9Wg==
x-ms-exchange-transport-forked: True
Content-Type: multipart/alternative; boundary="_000_CH2PR21MB138143E929DAFE3C893D8144D11C0CH2PR21MB1381namp_"
MIME-Version: 1.0
X-OriginatorOrg: microsoft.com
X-MS-Exchange-CrossTenant-AuthAs: Internal
X-MS-Exchange-CrossTenant-AuthSource: CH2PR21MB1381.namprd21.prod.outlook.com
X-MS-Exchange-CrossTenant-Network-Message-Id: d0dc81b5-5acf-4e3e-d73a-08d8760f83eb
X-MS-Exchange-CrossTenant-originalarrivaltime: 21 Oct 2020 22:20:28.2036 (UTC)
X-MS-Exchange-CrossTenant-fromentityheader: Hosted
X-MS-Exchange-CrossTenant-id: 72f988bf-86f1-41af-91ab-2d7cd011db47
X-MS-Exchange-CrossTenant-mailboxtype: HOSTED
X-MS-Exchange-CrossTenant-userprincipalname: r7Md177Ta9uco7CLKgHw3VsOtsuuebVtBeCkjZ8xl3Lu5w6eI9OK9IxRFqaqsQlWeAbQTvBHSOopso9/V9Dgbg==
X-MS-Exchange-Transport-CrossTenantHeadersStamped: CH2PR21MB1526
Archived-At: <https://mailarchive.ietf.org/arch/msg/emu/Yi_hIP2fMZvQaPL9K2kj6lj6JWw>
Subject: Re: [Emu] Proposed resolution for TEAP errata for 5128
X-BeenThere: emu@ietf.org
X-Mailman-Version: 2.1.29
Precedence: list
List-Id: "EAP Methods Update \(EMU\)" <emu.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/emu>, <mailto:emu-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/emu/>
List-Post: <mailto:emu@ietf.org>
List-Help: <mailto:emu-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/emu>, <mailto:emu-request@ietf.org?subject=subscribe>
X-List-Received-Date: Wed, 21 Oct 2020 22:20:32 -0000

--_000_CH2PR21MB138143E929DAFE3C893D8144D11C0CH2PR21MB1381namp_
Content-Type: text/plain; charset="utf-8"
Content-Transfer-Encoding: base64

SW4gdGhlb3J5IEkgYWdyZWUgdGhpcyBpcyBhIHBvc3NpYmxlIHJlc29sdXRpb24uIEhvd2V2ZXIs
IHRoaXMgZG9lc27igJl0IG1hdGNoIGFueSBvZiB0aGUgY3VycmVudCBURUFQIGltcGxlbWVudGF0
aW9ucyB0aGF0IEkgYW0gYXdhcmUgb2YuIFBlcmhhcHMgT2xlZyBjYW4gd2VpZ2ggaW4gYXMgd2Vs
bCBpbiB0ZXJtcyBvZiB3aGF0IGhl4oCZcyBzZWVuLg0KDQpJIGJlbGlldmUgYWxsIGN1cnJlbnQg
aW1wbGVtZW50YXRpb25zIHRyZWF0IDYwIGFzIHRoZSBkZXNpcmVkIG91dHB1dCBsZW5ndGggd2l0
aG91dCB0cmVhdGluZyBhcyBhIHNlZWQuIEluIHRlcm1zIG9mIFBfPGhhc2g+LCB0aGlzIG1lYW5z
IGltcGxlbWVudGF0aW9ucyBhcmUgcGVyZm9ybWluZyB0aGUgY2FsY3VsYXRpb24gd2l0aG91dCBh
IHNlZWQuDQoNClJGQyA1MjQ2IGRlZmluZXMgdGhlIFRMUyAxLjIgUFJGIGFzOg0KUFJGKHNlY3Jl
dCwgbGFiZWwsIHNlZWQpID0gUF88aGFzaD4oc2VjcmV0LCBsYWJlbCArIHNlZWQpDQoNClNvIHRo
ZSBjYWxjdWxhdGlvbiBpbXBsZW1lbnRhdGlvbnMgYXJlIGN1cnJlbnRseSBwZXJmb3JtaW5nIHdp
dGggYW4gZW1wdHkgc2VlZCBlbmRzIHVwIGFzOg0KUF88aGFzaD4oc2VjcmV0LCBsYWJlbCkNCg0K
Tm90ZSB0aGF0IGluIFJGQyA1Mjk1LCB0aGUgbGVuZ3RoICppcyogZXhwbGljaXRseSBtZW50aW9u
ZWQgYXMgYmVpbmcgY29uY2F0ZW5hdGVkIHdpdGggdGhlIGxhYmVsDQpVU1JLID0gS0RGKEVNU0ss
IGtleSBsYWJlbCB8ICJcMCIgfCBvcHRpb25hbCBkYXRhIHwgbGVuZ3RoKQ0KDQpSRkMgNTI5NSBp
cyBtZW50aW9uZWQgZWFybGllciBpbiB0aGUgVEVBUCBSRkMsIGluIHRoZSBzZWN0aW9uIGNvdmVy
ZWQgYnkgZXJyYXRhIDUxMjcuICpIb3dldmVyKiBpdCBpcyBub3QgbWVudGlvbmVkIGluIHRoaXMg
cG9ydGlvbiBvZiB0aGUgUkZDLiBTaW5jZSB0aGlzIGNhbGN1bGF0aW9uIGlzIG5vdCBvbiBhbiBF
TVNLLCBJIGRvIG5vdCBiZWxpZXZlIFJGQyAyMzk1IGFwcGxpZXMgYW5kIHRoaXMgaXMgbGlrZWx5
IHdoeSBpbXBsZW1lbnRhdGlvbnMgd2VudCB3aXRoIHRoZSBzZWVkbGVzcyBQXzxoYXNoPihzZWNy
ZXQsIGxhYmVsKSBjYWxjdWxhdGlvbiBpbnN0ZWFkLg0KDQpJcyB0aGVyZSBjb25jZXJuIGFib3V0
IHVwZGF0aW5nIHRoZSBSRkMgaW4gYSB3YXkgdGhhdCBicmVha3MgZXhpc3RpbmcgaW1wbGVtZW50
YXRpb25zPw0KDQpKb3JnZSBWZXJnYXJhDQoNCkZyb206IEpvc2VwaCBTYWxvd2V5IDxqb2VAc2Fs
b3dleS5uZXQ+DQpTZW50OiBXZWRuZXNkYXksIE9jdG9iZXIgMjEsIDIwMjAgMjozNCBQTQ0KVG86
IEVNVSBXRyA8ZW11QGlldGYub3JnPjsgSm91bmkgTWFsaW5lbiA8akB3MS5maT47IEpvcmdlIFZl
cmdhcmEgPGpvdmVyZ2FyQG1pY3Jvc29mdC5jb20+OyBPbGVnIFBla2FyIChvbHBla2FyKSA8b2xw
ZWthckBjaXNjby5jb20+DQpTdWJqZWN0OiBQcm9wb3NlZCByZXNvbHV0aW9uIGZvciBURUFQIGVy
cmF0YSBmb3IgNTEyOA0KDQpFcnJhdGEgNTEyODogaHR0cHM6Ly93d3cucmZjLWVkaXRvci5vcmcv
ZXJyYXRhL2VpZDUxMjg8aHR0cHM6Ly9uYW0wNi5zYWZlbGlua3MucHJvdGVjdGlvbi5vdXRsb29r
LmNvbS8/dXJsPWh0dHBzJTNBJTJGJTJGd3d3LnJmYy1lZGl0b3Iub3JnJTJGZXJyYXRhJTJGZWlk
NTEyOCZkYXRhPTA0JTdDMDElN0Nqb3ZlcmdhciU0MG1pY3Jvc29mdC5jb20lN0NhODVjNzE4YTNm
ZDE0YWI1ZDg4ZjA4ZDg3NjA5MjA5ZCU3QzcyZjk4OGJmODZmMTQxYWY5MWFiMmQ3Y2QwMTFkYjQ3
JTdDMSU3QzAlN0M2MzczODkxMjg4NjA5MjE0MDklN0NVbmtub3duJTdDVFdGcGJHWnNiM2Q4ZXlK
V0lqb2lNQzR3TGpBd01EQWlMQ0pRSWpvaVYybHVNeklpTENKQlRpSTZJazFoYVd3aUxDSlhWQ0k2
TW4wJTNEJTdDMTAwMCZzZGF0YT1HWHdVNHRPMSUyQmxKZzlhWVklMkJjJTJCTktHZFJBTWxXeTNJ
JTJCcUVseWIlMkJOZDdjayUzRCZyZXNlcnZlZD0wPg0KUHJvcG9zZWQgU3RhdGU6IFZlcmlmaWVk
DQpSZXZpc2lvbjoNCg0KU2VjdGlvbiA1LjIuIHNheXMNCg0KSU1DS1tqXSA9IFRMUy1QUkYoUy1J
TUNLW2otMV0sICJJbm5lciBNZXRob2RzIENvbXBvdW5kIEtleXMiLA0KICAgICAgICAgICAgICAg
IElNU0tbal0sIDYwKQ0KDQpJdCBzaG91bGQgc2F5Og0KDQpJTUNLW2pdID0gVExTLVBSRihTLUlN
Q0tbai0xXSwgIklubmVyIE1ldGhvZHMgQ29tcG91bmQgS2V5cyIsIElNU0tbal0gfCA2MCkNCg0K
Tm90ZToNCkFjY29yZGluZyB0bw0KDQpSRkM1MjQ2IFRoZSBUcmFuc3BvcnQgTGF5ZXIgU2VjdXJp
dHkgKFRMUykgUHJvdG9jb2wgVmVyc2lvbiAxLjINCg0KNS4gSE1BQyBhbmQgdGhlIFBzZXVkb3Jh
bmRvbSBGdW5jdGlvbg0KDQoiVExTJ3MgUFJGIGlzIGNyZWF0ZWQgYnkgYXBwbHlpbmcgUF9oYXNo
IHRvIHRoZSBzZWNyZXQgYXM6DQoNClBSRihzZWNyZXQsIGxhYmVsLCBzZWVkKSA9IFBfPGhhc2g+
KHNlY3JldCwgbGFiZWwgKyBzZWVkKSINCg0KSW4gdGVybXMgb2YgUF88aGFzaD4gdGhpcyB3b3Vs
ZCBsb29rIGxpa2UgdGhlIGZvbGxvd2luZyB3aXRoIHRoZSBsZW5ndGggcmVwcmVzZW50ZWQgYXMg
YSAyIGJ5dGUgdmFsdWUgaW4gbmV0d29yayBieXRlIG9yZGVyOg0KDQpJTUNLW2pdID0gUF88aGFz
aD4oUy1JTUNLW2otMV0sICJJbm5lciBNZXRob2RzIENvbXBvdW5kIEtleXMiIHwgSU1TS1tqXSB8
IDB4MDAgfCAweDNDKQ0KDQoNCg==

--_000_CH2PR21MB138143E929DAFE3C893D8144D11C0CH2PR21MB1381namp_
Content-Type: text/html; charset="utf-8"
Content-Transfer-Encoding: base64

PGh0bWwgeG1sbnM6dj0idXJuOnNjaGVtYXMtbWljcm9zb2Z0LWNvbTp2bWwiIHhtbG5zOm89InVy
bjpzY2hlbWFzLW1pY3Jvc29mdC1jb206b2ZmaWNlOm9mZmljZSIgeG1sbnM6dz0idXJuOnNjaGVt
YXMtbWljcm9zb2Z0LWNvbTpvZmZpY2U6d29yZCIgeG1sbnM6bT0iaHR0cDovL3NjaGVtYXMubWlj
cm9zb2Z0LmNvbS9vZmZpY2UvMjAwNC8xMi9vbW1sIiB4bWxucz0iaHR0cDovL3d3dy53My5vcmcv
VFIvUkVDLWh0bWw0MCI+DQo8aGVhZD4NCjxtZXRhIGh0dHAtZXF1aXY9IkNvbnRlbnQtVHlwZSIg
Y29udGVudD0idGV4dC9odG1sOyBjaGFyc2V0PXV0Zi04Ij4NCjxtZXRhIG5hbWU9IkdlbmVyYXRv
ciIgY29udGVudD0iTWljcm9zb2Z0IFdvcmQgMTUgKGZpbHRlcmVkIG1lZGl1bSkiPg0KPHN0eWxl
PjwhLS0NCi8qIEZvbnQgRGVmaW5pdGlvbnMgKi8NCkBmb250LWZhY2UNCgl7Zm9udC1mYW1pbHk6
IkNhbWJyaWEgTWF0aCI7DQoJcGFub3NlLTE6MiA0IDUgMyA1IDQgNiAzIDIgNDt9DQpAZm9udC1m
YWNlDQoJe2ZvbnQtZmFtaWx5OkNhbGlicmk7DQoJcGFub3NlLTE6MiAxNSA1IDIgMiAyIDQgMyAy
IDQ7fQ0KLyogU3R5bGUgRGVmaW5pdGlvbnMgKi8NCnAuTXNvTm9ybWFsLCBsaS5Nc29Ob3JtYWws
IGRpdi5Nc29Ob3JtYWwNCgl7bWFyZ2luOjBpbjsNCglmb250LXNpemU6MTEuMHB0Ow0KCWZvbnQt
ZmFtaWx5OiJDYWxpYnJpIixzYW5zLXNlcmlmO30NCmE6bGluaywgc3Bhbi5Nc29IeXBlcmxpbmsN
Cgl7bXNvLXN0eWxlLXByaW9yaXR5Ojk5Ow0KCWNvbG9yOmJsdWU7DQoJdGV4dC1kZWNvcmF0aW9u
OnVuZGVybGluZTt9DQpzcGFuLkVtYWlsU3R5bGUyMA0KCXttc28tc3R5bGUtdHlwZTpwZXJzb25h
bC1jb21wb3NlOw0KCWZvbnQtZmFtaWx5OiJDYWxpYnJpIixzYW5zLXNlcmlmOw0KCWNvbG9yOndp
bmRvd3RleHQ7fQ0KLk1zb0NocERlZmF1bHQNCgl7bXNvLXN0eWxlLXR5cGU6ZXhwb3J0LW9ubHk7
DQoJZm9udC1mYW1pbHk6IkNhbGlicmkiLHNhbnMtc2VyaWY7fQ0KQHBhZ2UgV29yZFNlY3Rpb24x
DQoJe3NpemU6OC41aW4gMTEuMGluOw0KCW1hcmdpbjoxLjBpbiAxLjBpbiAxLjBpbiAxLjBpbjt9
DQpkaXYuV29yZFNlY3Rpb24xDQoJe3BhZ2U6V29yZFNlY3Rpb24xO30NCi0tPjwvc3R5bGU+PCEt
LVtpZiBndGUgbXNvIDldPjx4bWw+DQo8bzpzaGFwZWRlZmF1bHRzIHY6ZXh0PSJlZGl0IiBzcGlk
bWF4PSIxMDI2IiAvPg0KPC94bWw+PCFbZW5kaWZdLS0+PCEtLVtpZiBndGUgbXNvIDldPjx4bWw+
DQo8bzpzaGFwZWxheW91dCB2OmV4dD0iZWRpdCI+DQo8bzppZG1hcCB2OmV4dD0iZWRpdCIgZGF0
YT0iMSIgLz4NCjwvbzpzaGFwZWxheW91dD48L3htbD48IVtlbmRpZl0tLT4NCjwvaGVhZD4NCjxi
b2R5IGxhbmc9IkVOLVVTIiBsaW5rPSJibHVlIiB2bGluaz0icHVycGxlIiBzdHlsZT0id29yZC13
cmFwOmJyZWFrLXdvcmQiPg0KPGRpdiBjbGFzcz0iV29yZFNlY3Rpb24xIj4NCjxwIGNsYXNzPSJN
c29Ob3JtYWwiPkluIHRoZW9yeSBJIGFncmVlIHRoaXMgaXMgYSBwb3NzaWJsZSByZXNvbHV0aW9u
LiBIb3dldmVyLCB0aGlzIGRvZXNu4oCZdCBtYXRjaCBhbnkgb2YgdGhlIGN1cnJlbnQgVEVBUCBp
bXBsZW1lbnRhdGlvbnMgdGhhdCBJIGFtIGF3YXJlIG9mLiBQZXJoYXBzIE9sZWcgY2FuIHdlaWdo
IGluIGFzIHdlbGwgaW4gdGVybXMgb2Ygd2hhdCBoZeKAmXMgc2Vlbi48bzpwPjwvbzpwPjwvcD4N
CjxwIGNsYXNzPSJNc29Ob3JtYWwiPjxvOnA+Jm5ic3A7PC9vOnA+PC9wPg0KPHAgY2xhc3M9Ik1z
b05vcm1hbCI+SSBiZWxpZXZlIGFsbCBjdXJyZW50IGltcGxlbWVudGF0aW9ucyB0cmVhdCA2MCBh
cyB0aGUgZGVzaXJlZCBvdXRwdXQgbGVuZ3RoIHdpdGhvdXQgdHJlYXRpbmcgYXMgYSBzZWVkLiBJ
biB0ZXJtcyBvZiBQXyZsdDtoYXNoJmd0OywgdGhpcyBtZWFucyBpbXBsZW1lbnRhdGlvbnMgYXJl
IHBlcmZvcm1pbmcgdGhlIGNhbGN1bGF0aW9uIHdpdGhvdXQgYSBzZWVkLjxvOnA+PC9vOnA+PC9w
Pg0KPHAgY2xhc3M9Ik1zb05vcm1hbCI+PG86cD4mbmJzcDs8L286cD48L3A+DQo8cCBjbGFzcz0i
TXNvTm9ybWFsIj5SRkMgNTI0NiBkZWZpbmVzIHRoZSBUTFMgMS4yIFBSRiBhczo8bzpwPjwvbzpw
PjwvcD4NCjxwIGNsYXNzPSJNc29Ob3JtYWwiPlBSRihzZWNyZXQsIGxhYmVsLCBzZWVkKSA9IFBf
Jmx0O2hhc2gmZ3Q7KHNlY3JldCwgbGFiZWwgKyBzZWVkKTxvOnA+PC9vOnA+PC9wPg0KPHAgY2xh
c3M9Ik1zb05vcm1hbCI+PG86cD4mbmJzcDs8L286cD48L3A+DQo8cCBjbGFzcz0iTXNvTm9ybWFs
Ij5TbyB0aGUgY2FsY3VsYXRpb24gaW1wbGVtZW50YXRpb25zIGFyZSBjdXJyZW50bHkgcGVyZm9y
bWluZyB3aXRoIGFuIGVtcHR5IHNlZWQgZW5kcyB1cCBhczo8bzpwPjwvbzpwPjwvcD4NCjxwIGNs
YXNzPSJNc29Ob3JtYWwiPlBfJmx0O2hhc2gmZ3Q7KHNlY3JldCwgbGFiZWwpPG86cD48L286cD48
L3A+DQo8cCBjbGFzcz0iTXNvTm9ybWFsIj48bzpwPiZuYnNwOzwvbzpwPjwvcD4NCjxwIGNsYXNz
PSJNc29Ob3JtYWwiPk5vdGUgdGhhdCBpbiBSRkMgNTI5NSwgdGhlIGxlbmd0aCAqaXMqIGV4cGxp
Y2l0bHkgbWVudGlvbmVkIGFzIGJlaW5nIGNvbmNhdGVuYXRlZCB3aXRoIHRoZSBsYWJlbDxvOnA+
PC9vOnA+PC9wPg0KPHAgY2xhc3M9Ik1zb05vcm1hbCI+VVNSSyA9IEtERihFTVNLLCBrZXkgbGFi
ZWwgfCAmcXVvdDtcMCZxdW90OyB8IG9wdGlvbmFsIGRhdGEgfCBsZW5ndGgpPG86cD48L286cD48
L3A+DQo8cCBjbGFzcz0iTXNvTm9ybWFsIj48bzpwPiZuYnNwOzwvbzpwPjwvcD4NCjxwIGNsYXNz
PSJNc29Ob3JtYWwiPlJGQyA1Mjk1IGlzIG1lbnRpb25lZCBlYXJsaWVyIGluIHRoZSBURUFQIFJG
QywgaW4gdGhlIHNlY3Rpb24gY292ZXJlZCBieSBlcnJhdGEgNTEyNy4gKkhvd2V2ZXIqIGl0IGlz
IG5vdCBtZW50aW9uZWQgaW4gdGhpcyBwb3J0aW9uIG9mIHRoZSBSRkMuIFNpbmNlIHRoaXMgY2Fs
Y3VsYXRpb24gaXMgbm90IG9uIGFuIEVNU0ssIEkgZG8gbm90IGJlbGlldmUgUkZDIDIzOTUgYXBw
bGllcyBhbmQgdGhpcyBpcyBsaWtlbHkNCiB3aHkgaW1wbGVtZW50YXRpb25zIHdlbnQgd2l0aCB0
aGUgc2VlZGxlc3MgUF8mbHQ7aGFzaCZndDsoc2VjcmV0LCBsYWJlbCkgY2FsY3VsYXRpb24gaW5z
dGVhZC48bzpwPjwvbzpwPjwvcD4NCjxwIGNsYXNzPSJNc29Ob3JtYWwiPjxvOnA+Jm5ic3A7PC9v
OnA+PC9wPg0KPHAgY2xhc3M9Ik1zb05vcm1hbCI+SXMgdGhlcmUgY29uY2VybiBhYm91dCB1cGRh
dGluZyB0aGUgUkZDIGluIGEgd2F5IHRoYXQgYnJlYWtzIGV4aXN0aW5nIGltcGxlbWVudGF0aW9u
cz88bzpwPjwvbzpwPjwvcD4NCjxwIGNsYXNzPSJNc29Ob3JtYWwiPjxvOnA+Jm5ic3A7PC9vOnA+
PC9wPg0KPHAgY2xhc3M9Ik1zb05vcm1hbCI+Sm9yZ2UgVmVyZ2FyYTxvOnA+PC9vOnA+PC9wPg0K
PHAgY2xhc3M9Ik1zb05vcm1hbCI+PG86cD4mbmJzcDs8L286cD48L3A+DQo8ZGl2IHN0eWxlPSJi
b3JkZXI6bm9uZTtib3JkZXItdG9wOnNvbGlkICNFMUUxRTEgMS4wcHQ7cGFkZGluZzozLjBwdCAw
aW4gMGluIDBpbiI+DQo8cCBjbGFzcz0iTXNvTm9ybWFsIj48Yj5Gcm9tOjwvYj4gSm9zZXBoIFNh
bG93ZXkgJmx0O2pvZUBzYWxvd2V5Lm5ldCZndDsgPGJyPg0KPGI+U2VudDo8L2I+IFdlZG5lc2Rh
eSwgT2N0b2JlciAyMSwgMjAyMCAyOjM0IFBNPGJyPg0KPGI+VG86PC9iPiBFTVUgV0cgJmx0O2Vt
dUBpZXRmLm9yZyZndDs7IEpvdW5pIE1hbGluZW4gJmx0O2pAdzEuZmkmZ3Q7OyBKb3JnZSBWZXJn
YXJhICZsdDtqb3ZlcmdhckBtaWNyb3NvZnQuY29tJmd0OzsgT2xlZyBQZWthciAob2xwZWthcikg
Jmx0O29scGVrYXJAY2lzY28uY29tJmd0Ozxicj4NCjxiPlN1YmplY3Q6PC9iPiBQcm9wb3NlZCBy
ZXNvbHV0aW9uIGZvciBURUFQIGVycmF0YSBmb3IgNTEyODxvOnA+PC9vOnA+PC9wPg0KPC9kaXY+
DQo8cCBjbGFzcz0iTXNvTm9ybWFsIj48bzpwPiZuYnNwOzwvbzpwPjwvcD4NCjxkaXY+DQo8cCBj
bGFzcz0iTXNvTm9ybWFsIj5FcnJhdGEgNTEyODombmJzcDs8YSBocmVmPSJodHRwczovL25hbTA2
LnNhZmVsaW5rcy5wcm90ZWN0aW9uLm91dGxvb2suY29tLz91cmw9aHR0cHMlM0ElMkYlMkZ3d3cu
cmZjLWVkaXRvci5vcmclMkZlcnJhdGElMkZlaWQ1MTI4JmFtcDtkYXRhPTA0JTdDMDElN0Nqb3Zl
cmdhciU0MG1pY3Jvc29mdC5jb20lN0NhODVjNzE4YTNmZDE0YWI1ZDg4ZjA4ZDg3NjA5MjA5ZCU3
QzcyZjk4OGJmODZmMTQxYWY5MWFiMmQ3Y2QwMTFkYjQ3JTdDMSU3QzAlN0M2MzczODkxMjg4NjA5
MjE0MDklN0NVbmtub3duJTdDVFdGcGJHWnNiM2Q4ZXlKV0lqb2lNQzR3TGpBd01EQWlMQ0pRSWpv
aVYybHVNeklpTENKQlRpSTZJazFoYVd3aUxDSlhWQ0k2TW4wJTNEJTdDMTAwMCZhbXA7c2RhdGE9
R1h3VTR0TzElMkJsSmc5YVlZJTJCYyUyQk5LR2RSQU1sV3kzSSUyQnFFbHliJTJCTmQ3Y2slM0Qm
YW1wO3Jlc2VydmVkPTAiPmh0dHBzOi8vd3d3LnJmYy1lZGl0b3Iub3JnL2VycmF0YS9laWQ1MTI4
PC9hPjxvOnA+PC9vOnA+PC9wPg0KPGRpdj4NCjxwIGNsYXNzPSJNc29Ob3JtYWwiPlByb3Bvc2Vk
IFN0YXRlOiBWZXJpZmllZDxvOnA+PC9vOnA+PC9wPg0KPC9kaXY+DQo8ZGl2Pg0KPHAgY2xhc3M9
Ik1zb05vcm1hbCI+UmV2aXNpb246PG86cD48L286cD48L3A+DQo8L2Rpdj4NCjxkaXY+DQo8cCBj
bGFzcz0iTXNvTm9ybWFsIj48bzpwPiZuYnNwOzwvbzpwPjwvcD4NCjwvZGl2Pg0KPGRpdj4NCjxw
IGNsYXNzPSJNc29Ob3JtYWwiPlNlY3Rpb24gNS4yLiBzYXlzPG86cD48L286cD48L3A+DQo8L2Rp
dj4NCjxkaXY+DQo8cCBzdHlsZT0ibXNvLW1hcmdpbi10b3AtYWx0OjMuNzVwdDttYXJnaW4tcmln
aHQ6My43NXB0O21hcmdpbi1ib3R0b206Ny41cHQ7bWFyZ2luLWxlZnQ6My43NXB0Ij4NCjxicj4N
CklNQ0tbal0gPSBUTFMtUFJGKFMtSU1DS1tqLTFdLCAmcXVvdDtJbm5lciBNZXRob2RzIENvbXBv
dW5kIEtleXMmcXVvdDssPGJyPg0KJm5ic3A7ICZuYnNwOyAmbmJzcDsgJm5ic3A7ICZuYnNwOyAm
bmJzcDsgJm5ic3A7ICZuYnNwOyBJTVNLW2pdLCA2MCk8YnI+DQo8YnI+DQpJdCBzaG91bGQgc2F5
Ojxicj4NCjxicj4NCklNQ0tbal0gPSBUTFMtUFJGKFMtSU1DS1tqLTFdLCAmcXVvdDtJbm5lciBN
ZXRob2RzIENvbXBvdW5kIEtleXMmcXVvdDssJm5ic3A7PHNwYW4gc3R5bGU9ImZvbnQtc2l6ZTox
MC41cHQ7Zm9udC1mYW1pbHk6JnF1b3Q7QXJpYWwmcXVvdDssc2Fucy1zZXJpZjtjb2xvcjojMkM0
MzUzIj5JTVNLW2pdIHwgNjApPC9zcGFuPjxvOnA+PC9vOnA+PC9wPg0KPHAgc3R5bGU9Im1zby1t
YXJnaW4tdG9wLWFsdDozLjc1cHQ7bWFyZ2luLXJpZ2h0OjMuNzVwdDttYXJnaW4tYm90dG9tOjcu
NXB0O21hcmdpbi1sZWZ0OjMuNzVwdCI+DQo8c3BhbiBzdHlsZT0iZm9udC1zaXplOjEwLjVwdDtm
b250LWZhbWlseTomcXVvdDtBcmlhbCZxdW90OyxzYW5zLXNlcmlmO2NvbG9yOiMyQzQzNTMiPk5v
dGU6Jm5ic3A7Jm5ic3A7PC9zcGFuPjxvOnA+PC9vOnA+PC9wPg0KPHAgY2xhc3M9Ik1zb05vcm1h
bCI+QWNjb3JkaW5nIHRvPGJyPg0KPGJyPg0KUkZDNTI0NiBUaGUgVHJhbnNwb3J0IExheWVyIFNl
Y3VyaXR5IChUTFMpIFByb3RvY29sIFZlcnNpb24gMS4yPGJyPg0KPGJyPg0KNS4gSE1BQyBhbmQg
dGhlIFBzZXVkb3JhbmRvbSBGdW5jdGlvbjxicj4NCjxicj4NCiZxdW90O1RMUydzIFBSRiBpcyBj
cmVhdGVkIGJ5IGFwcGx5aW5nIFBfaGFzaCB0byB0aGUgc2VjcmV0IGFzOjxicj4NCjxicj4NClBS
RihzZWNyZXQsIGxhYmVsLCBzZWVkKSA9IFBfJmx0O2hhc2gmZ3Q7KHNlY3JldCwgbGFiZWwgKyBz
ZWVkKSZxdW90OzxvOnA+PC9vOnA+PC9wPg0KPC9kaXY+DQo8ZGl2Pg0KPHAgY2xhc3M9Ik1zb05v
cm1hbCI+PG86cD4mbmJzcDs8L286cD48L3A+DQo8L2Rpdj4NCjxkaXY+DQo8cCBjbGFzcz0iTXNv
Tm9ybWFsIj5JbiB0ZXJtcyBvZiBQXyZsdDtoYXNoJmd0OyB0aGlzIHdvdWxkIGxvb2sgbGlrZSB0
aGUgZm9sbG93aW5nIHdpdGggdGhlIGxlbmd0aCByZXByZXNlbnRlZCBhcyBhIDIgYnl0ZSB2YWx1
ZSBpbiBuZXR3b3JrIGJ5dGUgb3JkZXI6PG86cD48L286cD48L3A+DQo8L2Rpdj4NCjxkaXY+DQo8
cCBjbGFzcz0iTXNvTm9ybWFsIj48bzpwPiZuYnNwOzwvbzpwPjwvcD4NCjwvZGl2Pg0KPGRpdj4N
CjxwIGNsYXNzPSJNc29Ob3JtYWwiPklNQ0tbal0gPSBQXyZsdDtoYXNoJmd0OyhTLUlNQ0tbai0x
XSwgJnF1b3Q7SW5uZXIgTWV0aG9kcyBDb21wb3VuZCBLZXlzJnF1b3Q7IHwmbmJzcDs8c3BhbiBz
dHlsZT0iZm9udC1zaXplOjEwLjVwdDtjb2xvcjojMkM0MzUzIj5JTVNLW2pdIHwgMHgwMCB8IDB4
M0MpPC9zcGFuPjxvOnA+PC9vOnA+PC9wPg0KPC9kaXY+DQo8ZGl2Pg0KPHAgY2xhc3M9Ik1zb05v
cm1hbCI+PG86cD4mbmJzcDs8L286cD48L3A+DQo8L2Rpdj4NCjxkaXY+DQo8cCBjbGFzcz0iTXNv
Tm9ybWFsIj48bzpwPiZuYnNwOzwvbzpwPjwvcD4NCjwvZGl2Pg0KPC9kaXY+DQo8L2Rpdj4NCjwv
Ym9keT4NCjwvaHRtbD4NCg==

--_000_CH2PR21MB138143E929DAFE3C893D8144D11C0CH2PR21MB1381namp_--


From nobody Wed Oct 21 16:54:42 2020
Return-Path: <joe@salowey.net>
X-Original-To: emu@ietfa.amsl.com
Delivered-To: emu@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id A1CF23A0C30 for <emu@ietfa.amsl.com>; Wed, 21 Oct 2020 16:54:40 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.798
X-Spam-Level: 
X-Spam-Status: No, score=-1.798 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, HTML_MESSAGE=0.001, HTTPS_HTTP_MISMATCH=0.1, SPF_HELO_NONE=0.001, SPF_PASS=-0.001, URIBL_BLOCKED=0.001] autolearn=no autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (2048-bit key) header.d=salowey-net.20150623.gappssmtp.com
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 T8crnwfU48T6 for <emu@ietfa.amsl.com>; Wed, 21 Oct 2020 16:54:38 -0700 (PDT)
Received: from mail-qk1-x736.google.com (mail-qk1-x736.google.com [IPv6:2607:f8b0:4864:20::736]) (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 891643A0C33 for <emu@ietf.org>; Wed, 21 Oct 2020 16:54:38 -0700 (PDT)
Received: by mail-qk1-x736.google.com with SMTP id v200so4679262qka.0 for <emu@ietf.org>; Wed, 21 Oct 2020 16:54:38 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=salowey-net.20150623.gappssmtp.com; s=20150623; h=mime-version:references:in-reply-to:from:date:message-id:subject:to; bh=fP44xKZExNFN+ReJD5UXF4CitPdbpSUdK1jDzxKWuIQ=; b=rz6EeqnEb5dHJ/pPPSNxK/2uJNUnS61E+nSxsqxATA/tedHL5VQHogRMoGjTg1ADi+ B7QpwgLWECUgPTgTcrJlAd0z8lY2LCQX/oPhCbs/gglXfSLnm23VEUixUnjMME47g3gT v9iby9LbvLUVfJOsYzFFXaUXevnn62fjkDXn5P/IlbJscTKxbR2lYd691D/s/uH0ul1Z OMSH9gwrvCYniIEl8mHo3E2akhUxjvoB8nE6uT3f8DF9XoEjhV83D5rwcpBb/Rtu3zNC uyadCmxthPg6L+sv2q6XbfZK3UrYtt2tfDFwbC4TTbvtRqDFl3yqgmF74vXpcfan+QmC cDcA==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:mime-version:references:in-reply-to:from:date :message-id:subject:to; bh=fP44xKZExNFN+ReJD5UXF4CitPdbpSUdK1jDzxKWuIQ=; b=Q4OuagbblB6yigfxtqhhJSeUrS/Z+tQN7cpmVdPuVnm6/tjcL/IOOZblYURYhi+eJC m3+P/9gZ4d0mwhoudsQ04D+8lF7KIMH3Q273rVpHtT0p922dj7t2O4smBAn37p5A7kvE fzajAGU/8d0evr6Tk7lDGSOWd1G7jlTq6LOD5A4WFKiXGax/ZFlqv8PctDGvhCc4mJ0w +ElAHAETcYFrA+MTd87P2ViWFLTlyfiobx8DoI7uWhr4Q8keMBnfatYPdnMc5jGtho5i xw98bTyfE0OYCFPhilTEhvHRc83WyBzT8w8oV1ydD4xErkh04tdn3C+K7MIYA68nQLwQ 3WmA==
X-Gm-Message-State: AOAM533dpAI92rPEfK0KMR1A+ukDCPNfIOvacPczeDV0i1I3AOlrzRJC F8Cxnn2piLK+Cf2OCHOIaO+Y73n4UBMRvVjk30apdtoAwig=
X-Google-Smtp-Source: ABdhPJwft5/wYMgUlYlJGibp5GicHrMl+6EZBTreN1jl832YgH7TQtZSZRMzCTPj6pXzEXW1tqq1QE4Niob9ZqBKBlA=
X-Received: by 2002:a37:849:: with SMTP id 70mr5788435qki.332.1603324475874; Wed, 21 Oct 2020 16:54:35 -0700 (PDT)
MIME-Version: 1.0
References: <CAOgPGoBay+GG=F8WV0gLOOwLtGdGALGw_cM2JoAnXOtmGq7A+w@mail.gmail.com> <CH2PR21MB138143E929DAFE3C893D8144D11C0@CH2PR21MB1381.namprd21.prod.outlook.com> <CAOgPGoAtcm+Br+YkCyTtg5nJjqO7LGSo77b+CD4+Ba05azafew@mail.gmail.com> <CH2PR21MB13815BCEDC846D7C440AD564D11C0@CH2PR21MB1381.namprd21.prod.outlook.com>
In-Reply-To: <CH2PR21MB13815BCEDC846D7C440AD564D11C0@CH2PR21MB1381.namprd21.prod.outlook.com>
From: Joseph Salowey <joe@salowey.net>
Date: Wed, 21 Oct 2020 16:54:24 -0700
Message-ID: <CAOgPGoDTC-qiHOXFTJd7aMn2To7ySzBcx+iQMB9m5foC1bFxzw@mail.gmail.com>
To: EMU WG <emu@ietf.org>, Jorge Vergara <jovergar=40microsoft.com@dmarc.ietf.org>,  Jouni Malinen <j@w1.fi>, Oleg Pekar <oleg.pekar.2017@gmail.com>
Content-Type: multipart/alternative; boundary="000000000000d832fc05b2371122"
Archived-At: <https://mailarchive.ietf.org/arch/msg/emu/aSulu7T1ibmusKXB01CgNgFl-ms>
Subject: Re: [Emu] Proposed resolution for TEAP errata for 5128
X-BeenThere: emu@ietf.org
X-Mailman-Version: 2.1.29
Precedence: list
List-Id: "EAP Methods Update \(EMU\)" <emu.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/emu>, <mailto:emu-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/emu/>
List-Post: <mailto:emu@ietf.org>
List-Help: <mailto:emu-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/emu>, <mailto:emu-request@ietf.org?subject=subscribe>
X-List-Received-Date: Wed, 21 Oct 2020 23:54:41 -0000

--000000000000d832fc05b2371122
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable

(I accidentally dropped this list from the conversation)

On Wed, Oct 21, 2020 at 4:48 PM Jorge Vergara <jovergar@microsoft.com>
wrote:

> >[Joe] Yes this is a concern and I think your interpretation of the
> current document is also valid.  There may be more than one
> implementation.  So what you implemented was:
>
> >
>
> >IMCK[j] =3D TLS-PRF(S-IMCK[j-1], "Inner Methods Compound Keys", IMSK[j])=
 =3D
> P_<hash>(S-IMCK[j-1], "Inner Methods Compound Keys" | IMSK[j])
>
>
>
> Yes, this is what I implemented. As you mentioned, there are multiple
> possible interpretations of this since the TEAP usage is incorrect.
> However, my implementation does interop with at least 2 large vendor
> implementations. If the implementations were using different calculations
> here, the Wi-Fi/Ethernet connections that depend on the MSK would fail. B=
ut
> since connections work, I can assume we are all using the same
> implementation and arriving at the same MSK. Cisco is one of the
> implementations that I have tested against which is why I was hoping Oleg
> may offer more context as to what he has seen.
>
>
>
[Joe] I can hope Jouni can chime in on this as well.  I think the original
intent was to not include the length as is your suggestion.



> >[Joe] Does the revision in 5167 match you implementation ( I don't think
> Jouni's comment changes the underly calculation, just its representation)=
?
>
>
>
> I have not implemented this portion of the RFC as I found it too unclear
> to work with. Thus I can=E2=80=99t comment on what implementations may be=
 doing.
> However, I agree with the current revision in 5167 as the most natural
> interpretation. If others have implemented this portion of the RFC then
> certainly their comments would be welcome.
>
>
> By the way, we=E2=80=99ve dropped the EMU group on our replies here =E2=
=80=93 not sure if
> intentional or not.
>
>
>
> Jorge Vergara
>
>
>
> *From:* Joseph Salowey <joe@salowey.net>
> *Sent:* Wednesday, October 21, 2020 4:36 PM
> *To:* Jorge Vergara <jovergar@microsoft.com>
> *Subject:* Re: Proposed resolution for TEAP errata for 5128
>
>
>
>
>
>
>
> On Wed, Oct 21, 2020 at 3:20 PM Jorge Vergara <jovergar@microsoft.com>
> wrote:
>
> In theory I agree this is a possible resolution. However, this doesn=E2=
=80=99t
> match any of the current TEAP implementations that I am aware of. Perhaps
> Oleg can weigh in as well in terms of what he=E2=80=99s seen.
>
>
>
> I believe all current implementations treat 60 as the desired output
> length without treating as a seed. In terms of P_<hash>, this means
> implementations are performing the calculation without a seed.
>
>
>
> RFC 5246 defines the TLS 1.2 PRF as:
>
> PRF(secret, label, seed) =3D P_<hash>(secret, label + seed)
>
>
>
> So the calculation implementations are currently performing with an empty
> seed ends up as:
>
> P_<hash>(secret, label)
>
>
>
> Note that in RFC 5295, the length *is* explicitly mentioned as being
> concatenated with the label
>
> USRK =3D KDF(EMSK, key label | "\0" | optional data | length)
>
>
>
> RFC 5295 is mentioned earlier in the TEAP RFC, in the section covered by
> errata 5127. *However* it is not mentioned in this portion of the RFC.
> Since this calculation is not on an EMSK, I do not believe RFC 2395 appli=
es
> and this is likely why implementations went with the seedless
> P_<hash>(secret, label) calculation instead.
>
>
>
> Is there concern about updating the RFC in a way that breaks existing
> implementations?
>
>
>
> [Joe] Yes this is a concern and I think your interpretation of the curren=
t
> document is also valid.  There may be more than one implementation.  So
> what you implemented was:
>
>
>
> IMCK[j] =3D TLS-PRF(S-IMCK[j-1], "Inner Methods Compound Keys", IMSK[j]) =
=3D
> P_<hash>(S-IMCK[j-1], "Inner Methods Compound Keys" | IMSK[j])
>
>
>
> taken out to 60 bytes.  The problem is that the TEAP spec references a
> TLS-PRF in a way that it does not define.  I think the errata points out
> the definition that should be used:
>
>
>
> PRF(secret, label, seed) =3D P_<hash>(secret, label + seed)
>
>
>
> That does not include length so the 60 in the original definition is
> ambiguous.   The new text would then be something like:
>
>
>
> IMCK[j] =3D TLS-PRF(S-IMCK[j-1], "Inner Methods Compound Keys", IMSK[j])
> to generate a length of 60 bytes
>
>
>
> Does the revision in 5167 match you implementation ( I don't think
> Jouni's comment changes the underly calculation, just its representation)=
?
>
>
>
>
>
>
>
>
>
>
>
> Jorge Vergara
>
>
>
> *From:* Joseph Salowey <joe@salowey.net>
> *Sent:* Wednesday, October 21, 2020 2:34 PM
> *To:* EMU WG <emu@ietf.org>; Jouni Malinen <j@w1.fi>; Jorge Vergara <
> jovergar@microsoft.com>; Oleg Pekar (olpekar) <olpekar@cisco.com>
> *Subject:* Proposed resolution for TEAP errata for 5128
>
>
>
> Errata 5128: https://www.rfc-editor.org/errata/eid5128
> <https://nam06.safelinks.protection.outlook.com/?url=3Dhttps%3A%2F%2Fwww.=
rfc-editor.org%2Ferrata%2Feid5128&data=3D04%7C01%7Cjovergar%40microsoft.com=
%7C38c27add2cb64a06310108d8761a22d3%7C72f988bf86f141af91ab2d7cd011db47%7C1%=
7C0%7C637389201909062787%7CUnknown%7CTWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIj=
oiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D%7C1000&sdata=3DXudZt9FPh4jOBFQj01S=
QysnhX4p7G%2BflW2Pn2yIaJRM%3D&reserved=3D0>
>
> Proposed State: Verified
>
> Revision:
>
>
>
> Section 5.2. says
>
>
> IMCK[j] =3D TLS-PRF(S-IMCK[j-1], "Inner Methods Compound Keys",
>                 IMSK[j], 60)
>
> It should say:
>
> IMCK[j] =3D TLS-PRF(S-IMCK[j-1], "Inner Methods Compound Keys", IMSK[j] |
> 60)
>
> Note:
>
> According to
>
> RFC5246 The Transport Layer Security (TLS) Protocol Version 1.2
>
> 5. HMAC and the Pseudorandom Function
>
> "TLS's PRF is created by applying P_hash to the secret as:
>
> PRF(secret, label, seed) =3D P_<hash>(secret, label + seed)"
>
>
>
> In terms of P_<hash> this would look like the following with the length
> represented as a 2 byte value in network byte order:
>
>
>
> IMCK[j] =3D P_<hash>(S-IMCK[j-1], "Inner Methods Compound Keys" | IMSK[j]=
 |
> 0x00 | 0x3C)
>
>
>
>
>
>

--000000000000d832fc05b2371122
Content-Type: text/html; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable

<div dir=3D"ltr"><div>(I accidentally=C2=A0dropped this list from the conve=
rsation)</div><br><div class=3D"gmail_quote"><div dir=3D"ltr" class=3D"gmai=
l_attr">On Wed, Oct 21, 2020 at 4:48 PM Jorge Vergara &lt;<a href=3D"mailto=
:jovergar@microsoft.com">jovergar@microsoft.com</a>&gt; wrote:<br></div><bl=
ockquote class=3D"gmail_quote" style=3D"margin:0px 0px 0px 0.8ex;border-lef=
t:1px solid rgb(204,204,204);padding-left:1ex">





<div lang=3D"EN-US" style=3D"overflow-wrap: break-word;">
<div class=3D"gmail-m_-2411216852304539647WordSection1">
<p class=3D"MsoNormal">&gt;[Joe] Yes this is a concern and I think your=C2=
=A0interpretation of the current document is also valid.=C2=A0 There may be=
 more than one implementation.=C2=A0 So what you implemented was:<u></u><u>=
</u></p>
<p class=3D"MsoNormal">&gt;<u></u>=C2=A0<u></u></p>
<p class=3D"MsoNormal">&gt;IMCK[j] =3D TLS-PRF(S-IMCK[j-1], &quot;Inner Met=
hods Compound Keys&quot;,=C2=A0<span style=3D"font-size:10.5pt;color:rgb(44=
,67,83)">IMSK[j]) =3D P_&lt;hash&gt;(S-IMCK[j-1], &quot;Inner Methods Compo=
und Keys&quot; | IMSK[j])</span><u></u><u></u></p>
<p class=3D"MsoNormal"><u></u>=C2=A0<u></u></p>
<p class=3D"MsoNormal">Yes, this is what I implemented. As you mentioned, t=
here are multiple possible interpretations of this since the TEAP usage is =
incorrect. However, my implementation does interop with at least 2 large ve=
ndor implementations. If the implementations
 were using different calculations here, the Wi-Fi/Ethernet connections tha=
t depend on the MSK would fail. But since connections work, I can assume we=
 are all using the same implementation and arriving at the same MSK. Cisco =
is one of the implementations that
 I have tested against which is why I was hoping Oleg may offer more contex=
t as to what he has seen.<u></u><u></u></p>
<p class=3D"MsoNormal"><u></u>=C2=A0</p></div></div></blockquote><div>[Joe]=
 I can hope Jouni can chime in on this as well.=C2=A0 I think the original =
intent was to not include the length as is your suggestion.=C2=A0</div><div=
><br></div><div>=C2=A0</div><blockquote class=3D"gmail_quote" style=3D"marg=
in:0px 0px 0px 0.8ex;border-left:1px solid rgb(204,204,204);padding-left:1e=
x"><div lang=3D"EN-US" style=3D"overflow-wrap: break-word;"><div class=3D"g=
mail-m_-2411216852304539647WordSection1"><p class=3D"MsoNormal"><u></u></p>
<p class=3D"MsoNormal">&gt;[Joe]<span style=3D"font-size:10.5pt;color:rgb(4=
4,67,83)"> Does the revision in 5167 match you implementation ( I don&#39;t=
 think Jouni&#39;s=C2=A0comment changes the underly=C2=A0calculation, just =
its representation)?=C2=A0</span><u></u><u></u></p>
<p class=3D"MsoNormal"><u></u>=C2=A0<u></u></p>
<p class=3D"MsoNormal">I have not implemented this portion of the RFC as I =
found it too unclear to work with. Thus I can=E2=80=99t comment on what imp=
lementations may be doing. However, I agree with the current revision in 51=
67 as the most natural interpretation. If
 others have implemented this portion of the RFC then certainly their comme=
nts would be welcome.<u></u><u></u></p>
<p class=3D"MsoNormal"><br><u></u></p></div></div></blockquote><blockquote =
class=3D"gmail_quote" style=3D"margin:0px 0px 0px 0.8ex;border-left:1px sol=
id rgb(204,204,204);padding-left:1ex"><div lang=3D"EN-US" style=3D"overflow=
-wrap: break-word;"><div class=3D"gmail-m_-2411216852304539647WordSection1"=
><p class=3D"MsoNormal"><u></u></p>
<p class=3D"MsoNormal">By the way, we=E2=80=99ve dropped the EMU group on o=
ur replies here =E2=80=93 not sure if intentional or not.<u></u><u></u></p>
<p class=3D"MsoNormal"><u></u>=C2=A0<u></u></p>
<p class=3D"MsoNormal">Jorge Vergara<u></u><u></u></p>
<p class=3D"MsoNormal"><u></u>=C2=A0<u></u></p>
<div style=3D"border-right:none;border-bottom:none;border-left:none;border-=
top:1pt solid rgb(225,225,225);padding:3pt 0in 0in">
<p class=3D"MsoNormal"><b>From:</b> Joseph Salowey &lt;<a href=3D"mailto:jo=
e@salowey.net" target=3D"_blank">joe@salowey.net</a>&gt; <br>
<b>Sent:</b> Wednesday, October 21, 2020 4:36 PM<br>
<b>To:</b> Jorge Vergara &lt;<a href=3D"mailto:jovergar@microsoft.com" targ=
et=3D"_blank">jovergar@microsoft.com</a>&gt;<br>
<b>Subject:</b> Re: Proposed resolution for TEAP errata for 5128<u></u><u><=
/u></p>
</div>
<p class=3D"MsoNormal"><u></u>=C2=A0<u></u></p>
<div>
<div>
<p class=3D"MsoNormal"><u></u>=C2=A0<u></u></p>
</div>
<p class=3D"MsoNormal"><u></u>=C2=A0<u></u></p>
<div>
<div>
<p class=3D"MsoNormal">On Wed, Oct 21, 2020 at 3:20 PM Jorge Vergara &lt;<a=
 href=3D"mailto:jovergar@microsoft.com" target=3D"_blank">jovergar@microsof=
t.com</a>&gt; wrote:<u></u><u></u></p>
</div>
<blockquote style=3D"border-top:none;border-right:none;border-bottom:none;b=
order-left:1pt solid rgb(204,204,204);padding:0in 0in 0in 6pt;margin-left:4=
.8pt;margin-right:0in">
<div>
<div>
<p class=3D"MsoNormal">In theory I agree this is a possible resolution. How=
ever, this doesn=E2=80=99t match any of the current TEAP implementations th=
at I am aware of. Perhaps Oleg can weigh in as well in terms
 of what he=E2=80=99s seen.<u></u><u></u></p>
<p class=3D"MsoNormal">=C2=A0<u></u><u></u></p>
<p class=3D"MsoNormal">I believe all current implementations treat 60 as th=
e desired output length without treating as a seed. In terms of P_&lt;hash&=
gt;, this means implementations are performing the calculation
 without a seed.<u></u><u></u></p>
<p class=3D"MsoNormal">=C2=A0<u></u><u></u></p>
<p class=3D"MsoNormal">RFC 5246 defines the TLS 1.2 PRF as:<u></u><u></u></=
p>
<p class=3D"MsoNormal">PRF(secret, label, seed) =3D P_&lt;hash&gt;(secret, =
label + seed)<u></u><u></u></p>
<p class=3D"MsoNormal">=C2=A0<u></u><u></u></p>
<p class=3D"MsoNormal">So the calculation implementations are currently per=
forming with an empty seed ends up as:<u></u><u></u></p>
<p class=3D"MsoNormal">P_&lt;hash&gt;(secret, label)<u></u><u></u></p>
<p class=3D"MsoNormal">=C2=A0<u></u><u></u></p>
<p class=3D"MsoNormal">Note that in RFC 5295, the length *is* explicitly me=
ntioned as being concatenated with the label<u></u><u></u></p>
<p class=3D"MsoNormal">USRK =3D KDF(EMSK, key label | &quot;\0&quot; | opti=
onal data | length)<u></u><u></u></p>
<p class=3D"MsoNormal">=C2=A0<u></u><u></u></p>
<p class=3D"MsoNormal">RFC 5295 is mentioned earlier in the TEAP RFC, in th=
e section covered by errata 5127. *However* it is not mentioned in this por=
tion of the RFC. Since this calculation is not on
 an EMSK, I do not believe RFC 2395 applies and this is likely why implemen=
tations went with the seedless P_&lt;hash&gt;(secret, label) calculation in=
stead.<u></u><u></u></p>
<p class=3D"MsoNormal">=C2=A0<u></u><u></u></p>
<p class=3D"MsoNormal">Is there concern about updating the RFC in a way tha=
t breaks existing implementations?<u></u><u></u></p>
<p class=3D"MsoNormal">=C2=A0<u></u><u></u></p>
</div>
</div>
</blockquote>
<div>
<p class=3D"MsoNormal">[Joe] Yes this is a concern and I think your=C2=A0in=
terpretation of the current document is also valid.=C2=A0 There may be more=
 than one implementation.=C2=A0 So what you implemented was:<u></u><u></u><=
/p>
</div>
<div>
<p class=3D"MsoNormal"><u></u>=C2=A0<u></u></p>
</div>
<div>
<p class=3D"MsoNormal">IMCK[j] =3D TLS-PRF(S-IMCK[j-1], &quot;Inner Methods=
 Compound Keys&quot;,=C2=A0<span style=3D"font-size:10.5pt;color:rgb(44,67,=
83)">IMSK[j]) =3D P_&lt;hash&gt;(S-IMCK[j-1], &quot;Inner Methods Compound =
Keys&quot; | IMSK[j])</span><u></u><u></u></p>
</div>
<div>
<p class=3D"MsoNormal"><u></u>=C2=A0<u></u></p>
</div>
<div>
<p class=3D"MsoNormal">taken out to 60 bytes.=C2=A0 The problem is that the=
 TEAP spec references a TLS-PRF in a way that it does not define.=C2=A0 I t=
hink the errata points out the definition that should be used:<u></u><u></u=
></p>
</div>
<div>
<p class=3D"MsoNormal"><u></u>=C2=A0<u></u></p>
</div>
<div>
<p class=3D"MsoNormal">PRF(secret, label, seed) =3D P_&lt;hash&gt;(secret, =
label + seed)<u></u><u></u></p>
</div>
<div>
<p class=3D"MsoNormal"><u></u>=C2=A0<u></u></p>
</div>
<div>
<p class=3D"MsoNormal">That does not include length so the 60 in the origin=
al definition=C2=A0is ambiguous.=C2=A0 =C2=A0The new text would then be som=
ething like:<u></u><u></u></p>
</div>
<div>
<p class=3D"MsoNormal"><u></u>=C2=A0<u></u></p>
</div>
<div>
<p class=3D"MsoNormal">IMCK[j] =3D TLS-PRF(S-IMCK[j-1], &quot;Inner Methods=
 Compound Keys&quot;,=C2=A0<span style=3D"font-size:10.5pt;color:rgb(44,67,=
83)">IMSK[j])=C2=A0 to generate a length of 60 bytes</span><u></u><u></u></=
p>
</div>
<div>
<p class=3D"MsoNormal"><u></u>=C2=A0<u></u></p>
</div>
<div>
<p class=3D"MsoNormal"><span style=3D"font-size:10.5pt;color:rgb(44,67,83)"=
>Does the revision in 5167 match you implementation ( I don&#39;t think Jou=
ni&#39;s=C2=A0comment changes the underly=C2=A0calculation, just its repres=
entation)?=C2=A0</span><u></u><u></u></p>
</div>
<div>
<p class=3D"MsoNormal"><u></u>=C2=A0<u></u></p>
</div>
<div>
<p class=3D"MsoNormal"><u></u>=C2=A0<u></u></p>
</div>
<div>
<p class=3D"MsoNormal"><u></u>=C2=A0<u></u></p>
</div>
<div>
<p class=3D"MsoNormal"><u></u>=C2=A0<u></u></p>
</div>
<div>
<p class=3D"MsoNormal">=C2=A0<u></u><u></u></p>
</div>
<blockquote style=3D"border-top:none;border-right:none;border-bottom:none;b=
order-left:1pt solid rgb(204,204,204);padding:0in 0in 0in 6pt;margin-left:4=
.8pt;margin-right:0in">
<div>
<div>
<p class=3D"MsoNormal">Jorge Vergara<u></u><u></u></p>
<p class=3D"MsoNormal">=C2=A0<u></u><u></u></p>
<div style=3D"border-right:none;border-bottom:none;border-left:none;border-=
top:1pt solid rgb(225,225,225);padding:3pt 0in 0in">
<p class=3D"MsoNormal"><b>From:</b> Joseph Salowey &lt;<a href=3D"mailto:jo=
e@salowey.net" target=3D"_blank">joe@salowey.net</a>&gt;
<br>
<b>Sent:</b> Wednesday, October 21, 2020 2:34 PM<br>
<b>To:</b> EMU WG &lt;<a href=3D"mailto:emu@ietf.org" target=3D"_blank">emu=
@ietf.org</a>&gt;; Jouni Malinen &lt;<a href=3D"mailto:j@w1.fi" target=3D"_=
blank">j@w1.fi</a>&gt;; Jorge Vergara &lt;<a href=3D"mailto:jovergar@micros=
oft.com" target=3D"_blank">jovergar@microsoft.com</a>&gt;; Oleg
 Pekar (olpekar) &lt;<a href=3D"mailto:olpekar@cisco.com" target=3D"_blank"=
>olpekar@cisco.com</a>&gt;<br>
<b>Subject:</b> Proposed resolution for TEAP errata for 5128<u></u><u></u><=
/p>
</div>
<p class=3D"MsoNormal">=C2=A0<u></u><u></u></p>
<div>
<p class=3D"MsoNormal">Errata 5128:=C2=A0<a href=3D"https://nam06.safelinks=
.protection.outlook.com/?url=3Dhttps%3A%2F%2Fwww.rfc-editor.org%2Ferrata%2F=
eid5128&amp;data=3D04%7C01%7Cjovergar%40microsoft.com%7C38c27add2cb64a06310=
108d8761a22d3%7C72f988bf86f141af91ab2d7cd011db47%7C1%7C0%7C6373892019090627=
87%7CUnknown%7CTWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1h=
aWwiLCJXVCI6Mn0%3D%7C1000&amp;sdata=3DXudZt9FPh4jOBFQj01SQysnhX4p7G%2BflW2P=
n2yIaJRM%3D&amp;reserved=3D0" target=3D"_blank">https://www.rfc-editor.org/=
errata/eid5128</a><u></u><u></u></p>
<div>
<p class=3D"MsoNormal">Proposed State: Verified<u></u><u></u></p>
</div>
<div>
<p class=3D"MsoNormal">Revision:<u></u><u></u></p>
</div>
<div>
<p class=3D"MsoNormal">=C2=A0<u></u><u></u></p>
</div>
<div>
<p class=3D"MsoNormal">Section 5.2. says<u></u><u></u></p>
</div>
<div>
<p style=3D"margin-right:3.75pt;margin-bottom:7.5pt;margin-left:3.75pt">
<br>
IMCK[j] =3D TLS-PRF(S-IMCK[j-1], &quot;Inner Methods Compound Keys&quot;,<b=
r>
=C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 IMSK[j], 60)<br>
<br>
It should say:<br>
<br>
IMCK[j] =3D TLS-PRF(S-IMCK[j-1], &quot;Inner Methods Compound Keys&quot;,=
=C2=A0<span style=3D"font-size:10.5pt;font-family:Arial,sans-serif;color:rg=
b(44,67,83)">IMSK[j] | 60)</span><u></u><u></u></p>
<p style=3D"margin-right:3.75pt;margin-bottom:7.5pt;margin-left:3.75pt">
<span style=3D"font-size:10.5pt;font-family:Arial,sans-serif;color:rgb(44,6=
7,83)">Note:=C2=A0=C2=A0</span><u></u><u></u></p>
<p class=3D"MsoNormal">According to<br>
<br>
RFC5246 The Transport Layer Security (TLS) Protocol Version 1.2<br>
<br>
5. HMAC and the Pseudorandom Function<br>
<br>
&quot;TLS&#39;s PRF is created by applying P_hash to the secret as:<br>
<br>
PRF(secret, label, seed) =3D P_&lt;hash&gt;(secret, label + seed)&quot;<u><=
/u><u></u></p>
</div>
<div>
<p class=3D"MsoNormal">=C2=A0<u></u><u></u></p>
</div>
<div>
<p class=3D"MsoNormal">In terms of P_&lt;hash&gt; this would look like the =
following with the length represented as a 2 byte value in network byte ord=
er:<u></u><u></u></p>
</div>
<div>
<p class=3D"MsoNormal">=C2=A0<u></u><u></u></p>
</div>
<div>
<p class=3D"MsoNormal">IMCK[j] =3D P_&lt;hash&gt;(S-IMCK[j-1], &quot;Inner =
Methods Compound Keys&quot; |=C2=A0<span style=3D"font-size:10.5pt;color:rg=
b(44,67,83)">IMSK[j] | 0x00 | 0x3C)</span><u></u><u></u></p>
</div>
<div>
<p class=3D"MsoNormal">=C2=A0<u></u><u></u></p>
</div>
<div>
<p class=3D"MsoNormal">=C2=A0<u></u><u></u></p>
</div>
</div>
</div>
</div>
</blockquote>
</div>
</div>
</div>
</div>

</blockquote></div></div>

--000000000000d832fc05b2371122--


From nobody Wed Oct 21 17:13:16 2020
Return-Path: <joe@salowey.net>
X-Original-To: emu@ietfa.amsl.com
Delivered-To: emu@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 616253A0CC4 for <emu@ietfa.amsl.com>; Wed, 21 Oct 2020 17:13:14 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.898
X-Spam-Level: 
X-Spam-Status: No, score=-1.898 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, HTML_MESSAGE=0.001, SPF_HELO_NONE=0.001, SPF_PASS=-0.001, URIBL_BLOCKED=0.001] autolearn=unavailable autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (2048-bit key) header.d=salowey-net.20150623.gappssmtp.com
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 06o7RaBoMlul for <emu@ietfa.amsl.com>; Wed, 21 Oct 2020 17:13:12 -0700 (PDT)
Received: from mail-qk1-x733.google.com (mail-qk1-x733.google.com [IPv6:2607:f8b0:4864:20::733]) (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 908353A0CD5 for <emu@ietf.org>; Wed, 21 Oct 2020 17:13:12 -0700 (PDT)
Received: by mail-qk1-x733.google.com with SMTP id k9so4664448qki.6 for <emu@ietf.org>; Wed, 21 Oct 2020 17:13:12 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=salowey-net.20150623.gappssmtp.com; s=20150623; h=mime-version:from:date:message-id:subject:to; bh=X+5MukpzG1ZZoc/hvBNhJxegwdJ3OtjwTlhQTmTpCXM=; b=AU/XYy+VWktiV1QJb/Gztax6UszsQmzHZrN5BHvdme7ZZWM/l/7mZRts+lChT3IBDA cKdRdxc0OhrFj+SZn9Gbkq+PxDPBXViWAA9MuWYOJchv2jf6G2ZQa/TKVVg/GJ38W7DE grPqY/Roafts6zEleqJJHIL13ZqvtSPoGl0kpjX8N3G5MAiTDsurEBBMhqDTjlPO9av/ TrKo8ggTNWBUerVDfPrMZe4uZ/zy1ZkPU4U/T8Dy2kvnQfau6XVQcks2/Kf+EbbY+m5E NBJl56lWFYS3GtiN2l24C3hEWDpsgPOUXFY486at0Tf72n9FkIKR3UNC2Rj0AAd4zdyb qPWg==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:mime-version:from:date:message-id:subject:to; bh=X+5MukpzG1ZZoc/hvBNhJxegwdJ3OtjwTlhQTmTpCXM=; b=VBSYF3qg1teS84iHcDbgJf5wPQ2UxYMEbBEJyJqdQU/OFlBC+6joCYW5guIcZtwVL9 PCzUkQpv1sZxGcVEFcIgXK1liHjxKnMwkghyKD3qR4w6azwEFsPlVpJ0g/zpBwbXzZyB 4HpUzi/+BHpd+Q4MdN/wxPeyRyfXfbQ2eVAPEzoOMKnsYwKCEadMpyrSCnRFBmXOnJOn yPBGHto+d3onkdRTsjDckRvwjE0+dl7L8heYRIl+F0+tjhRslBG5xeVuOYBxKxBSnh3r eW5k3akWCQy//a+cpQOcZbRT1cSqcy71mQHlzM2caKZT9SFdz6XJNytlgEjPm8qnLaXM ouhw==
X-Gm-Message-State: AOAM531rcvOMu5L9ZKAiZBs/WXLE7ZaWopXXXJZEH+b9yyjdBsoNzc84 uK5K4KUw5ONGy50MkxU5XUQY/CLiovuaTNEQ2cA06zr1IdQmoA==
X-Google-Smtp-Source: ABdhPJw4c+a/hTXWF1moowpN019YU6BBUUNP6kW5FjlumIulIRPLTA7gJ4+VVws30tW1LwcSkPJzy4aewSAI2aFo13A=
X-Received: by 2002:a37:a0d7:: with SMTP id j206mr5510345qke.375.1603325590971;  Wed, 21 Oct 2020 17:13:10 -0700 (PDT)
MIME-Version: 1.0
From: Joseph Salowey <joe@salowey.net>
Date: Wed, 21 Oct 2020 17:13:00 -0700
Message-ID: <CAOgPGoCAFD+Z6_hCNMN8F9ODC-VTxOM+DuxjSHU25HWjqzt+ag@mail.gmail.com>
To: EMU WG <emu@ietf.org>, Jouni Malinen <j@w1.fi>,  Jorge Vergara <jovergar=40microsoft.com@dmarc.ietf.org>,  Oleg Pekar <oleg.pekar.2017@gmail.com>
Content-Type: multipart/alternative; boundary="0000000000004f6a1305b23754bf"
Archived-At: <https://mailarchive.ietf.org/arch/msg/emu/yPfNWoXy60N_LbUJ0zbf5EyFHAM>
Subject: [Emu] Resolution of TEAP Errata 5767
X-BeenThere: emu@ietf.org
X-Mailman-Version: 2.1.29
Precedence: list
List-Id: "EAP Methods Update \(EMU\)" <emu.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/emu>, <mailto:emu-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/emu/>
List-Post: <mailto:emu@ietf.org>
List-Help: <mailto:emu-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/emu>, <mailto:emu-request@ietf.org?subject=subscribe>
X-List-Received-Date: Thu, 22 Oct 2020 00:13:14 -0000

--0000000000004f6a1305b23754bf
Content-Type: text/plain; charset="UTF-8"

Errata 5767: https://www.rfc-editor.org/errata/eid5767
Status: Verified
Revision:

Section 3.3.1 says:

   EAP method messages are carried within EAP-Payload TLVs defined in
   Section 4.2.10.  If more than one method is going to be executed in
   the tunnel, then upon method completion, the server MUST send an
   Intermediate-Result TLV indicating the result.

It should say:

   EAP method messages are carried within EAP-Payload TLVs defined in
   Section 4.2.10.  Upon completion of each EAP authentication method in
   the tunnel, the server MUST send an Intermediate-Result TLV
   indicating the result.

Section 3.3.3 says:

  The Crypto-Binding TLV and Intermediate-Result TLV MUST be included
  to perform cryptographic binding after each successful EAP method in a
  sequence of one or more EAP methods.

It should say:

  The Crypto-Binding TLV and Intermediate-Result TLV MUST be included
  to perform cryptographic binding after each successful EAP authentication
  method in a sequence of one or more EAP methods.

Section 3.8.3 says:

   Upon successful completion of the EAP method in Phase 2, the peer and
   server exchange a Crypto-Binding TLV to bind the inner method with
   the outer tunnel and ensure that a man-in-the-middle attack has not
   been attempted.

It should say:

   Upon successful completion of the EAP authentication method in Phase 2,
   the peer and server exchange a Crypto-Binding TLV to bind the inner
   method with the outer tunnel and ensure that a man-in-the-middle attack
   has not been attempted.

Section 4.2.11 says:

   The Intermediate-Result TLV provides support for acknowledged
   intermediate Success and Failure messages between multiple
   inner EAP methods within EAP.

It should say:

  The Intermediate-Result TLV provides support for acknowledged
  intermediate Success and Failure messages after each inner EAP
  authentication method.

Section 4.2.13 says:

 It MUST be included with the Intermediate-Result TLV to perform
 cryptographic binding after each successful EAP method in a
 sequence of EAP methods, before proceeding with another inner
 EAP method.

It should say:

 It MUST be included with the Intermediate-Result TLV to perform
 cryptographic binding after each successful EAP authentication
 method in a sequence of EAP methods, before proceeding with
 another inner EAP method.

Notes:

TEAP description is somewhat vague in discussion about "EAP methods" vs.
"EAP authentication methods" as it comes to the EAP methods performed in
Phase 2 within the TLS tunnel. RFC 3748 defines Identity request/response
as an EAP method. However, this method is not an "authentication method"
which is a special case of an method where the Type is 4 or greater.

RFC 7170 uses correct terminology in the first paragraph of Section 3.3.1
when talking about multiple authentication methods not being allowed by RFC
3748 in a single EAP conversation. However, many, but not all, of the
following "[EAP] method" instances are actually referring to "[EAP]
authentication method". This results in incorrect claims on when the
Intermediate-Result TLV and Crypto-Binding TLV are used. They are not used
after an EAP non-authentication method like Identity (e.g., see the example
in C.3); they are used after each EAP authentication method like EAP-pwd.

Furthermore, the comment about "more than one method is going to be
executed in the tunnel" does not sound accurate. This applies even if only
a single EAP authentication method is executed in the tunnel (Identity
method is not required to be executed). The proposed text in this errata
entry addresses these two issues in Section 3.3.1. The following additional
changes would be needed to make rest of the specification use the terms
more accurately:

3.3.3: "after each successful EAP method" --> "after each successful EAP
authentication method"
3.8.3: "completion of the EAP method" --> "completion of the EAP
authentication method"
4.2.11: "between multiple inner EAP methods within EAP" --> "after each
inner EAP authentication method"
4.2.13: "after each successful EAP method" --> "after each successful EAP
authentication method"

--0000000000004f6a1305b23754bf
Content-Type: text/html; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable

<div dir=3D"ltr">Errata 5767:=C2=A0<a href=3D"https://www.rfc-editor.org/er=
rata/eid5767">https://www.rfc-editor.org/errata/eid5767</a><br>Status: Veri=
fied<br><div>Revision:</div><div><br></div>Section 3.3.1 says:<br><br>=C2=
=A0 =C2=A0EAP method messages are carried within EAP-Payload TLVs defined i=
n<br>=C2=A0 =C2=A0Section 4.2.10.=C2=A0 If more than one method is going to=
 be executed in<br>=C2=A0 =C2=A0the tunnel, then upon method completion, th=
e server MUST send an<br>=C2=A0 =C2=A0Intermediate-Result TLV indicating th=
e result.<br><br>It should say:<br><br>=C2=A0 =C2=A0EAP method messages are=
 carried within EAP-Payload TLVs defined in<br>=C2=A0 =C2=A0Section 4.2.10.=
=C2=A0 Upon completion of each EAP authentication method in<br>=C2=A0 =C2=
=A0the tunnel, the server MUST send an Intermediate-Result TLV<br>=C2=A0 =
=C2=A0indicating the result.<div><br></div><div>Section 3.3.3 says:=C2=A0</=
div><div><br></div>=C2=A0 The Crypto-Binding TLV and Intermediate-Result TL=
V MUST be included=C2=A0<div>=C2=A0 to perform cryptographic binding after =
each successful EAP method in a=C2=A0</div><div>=C2=A0 sequence of one or m=
ore EAP methods.</div><div><br></div><div>It should say:</div><div><br></di=
v><div>=C2=A0 The Crypto-Binding TLV and Intermediate-Result TLV MUST be in=
cluded=C2=A0<div>=C2=A0 to perform cryptographic binding after each success=
ful EAP authentication=C2=A0</div><div>=C2=A0 method in a sequence of one o=
r more EAP methods.</div></div><div><br></div><div>Section 3.8.3 says:=C2=
=A0</div><br>=C2=A0 =C2=A0Upon successful completion of the EAP method in P=
hase 2, the peer and<br>=C2=A0 =C2=A0server exchange a Crypto-Binding TLV t=
o bind the inner method with<br>=C2=A0 =C2=A0the outer tunnel and ensure th=
at a man-in-the-middle attack has not<br>=C2=A0 =C2=A0been attempted.<div><=
br></div><div>It should say:</div><div><br></div><div>=C2=A0 =C2=A0Upon suc=
cessful completion of the EAP authentication method in Phase 2,=C2=A0</div>=
<div>=C2=A0 =C2=A0the peer and server exchange a Crypto-Binding TLV to bind=
 the inner=C2=A0</div><div>=C2=A0 =C2=A0method with the outer tunnel and en=
sure that a man-in-the-middle attack=C2=A0</div><div>=C2=A0 =C2=A0has not b=
een attempted.<br></div><div><br></div><div>Section 4.2.11 says:</div><div>=
<br></div>=C2=A0 =C2=A0The Intermediate-Result TLV provides support for ack=
nowledged<div>=C2=A0 =C2=A0intermediate Success and Failure messages betwee=
n multiple=C2=A0</div><div>=C2=A0 =C2=A0inner EAP methods within EAP.<div><=
br></div><div>It should say:</div><div><br></div><div>=C2=A0 The Intermedia=
te-Result TLV provides support for acknowledged=C2=A0</div><div>=C2=A0 inte=
rmediate Success and Failure messages after each inner EAP=C2=A0</div><div>=
=C2=A0 authentication method.<span style=3D"color:rgb(0,0,0);font-size:13.3=
333px"><br></span></div></div><div><br></div><div>Section 4.2.13 says:<br><=
/div><div><br></div>=C2=A0It MUST be included with the Intermediate-Result =
TLV to perform=C2=A0<div>=C2=A0cryptographic binding after each successful =
EAP method in a=C2=A0</div><div>=C2=A0sequence of EAP methods, before proce=
eding with another inner=C2=A0</div><div>=C2=A0EAP method.<div><br></div><d=
iv>It should say:</div><div><br></div><div>=C2=A0It MUST be included with t=
he Intermediate-Result TLV to perform</div><div>=C2=A0cryptographic binding=
 after each successful EAP authentication=C2=A0</div><div>=C2=A0method in a=
 sequence of EAP methods, before proceeding with=C2=A0</div><div>=C2=A0anot=
her inner EAP method.<br></div></div><div><br></div>Notes:<br><br>TEAP desc=
ription is somewhat vague in discussion about &quot;EAP methods&quot; vs. &=
quot;EAP authentication methods&quot; as it comes to the EAP methods perfor=
med in Phase 2 within the TLS tunnel. RFC 3748 defines Identity request/res=
ponse as an EAP method. However, this method is not an &quot;authentication=
 method&quot; which is a special case of an method where the Type is 4 or g=
reater.<br><br>RFC 7170 uses correct terminology in the first paragraph of =
Section 3.3.1 when talking about multiple authentication methods not being =
allowed by RFC 3748 in a single EAP conversation. However, many, but not al=
l, of the following &quot;[EAP] method&quot; instances are actually referri=
ng to &quot;[EAP] authentication method&quot;. This results in incorrect cl=
aims on when the Intermediate-Result TLV and Crypto-Binding TLV are used. T=
hey are not used after an EAP non-authentication method like Identity (e.g.=
, see the example in C.3); they are used after each EAP authentication meth=
od like EAP-pwd.<br><br>Furthermore, the comment about &quot;more than one =
method is going to be executed in the tunnel&quot; does not sound accurate.=
 This applies even if only a single EAP authentication method is executed i=
n the tunnel (Identity method is not required to be executed). The proposed=
 text in this errata entry addresses these two issues in Section 3.3.1. The=
 following additional changes would be needed to make rest of the specifica=
tion use the terms more accurately:<br><br>3.3.3: &quot;after each successf=
ul EAP method&quot; --&gt; &quot;after each successful EAP authentication m=
ethod&quot;<br>3.8.3: &quot;completion of the EAP method&quot; --&gt; &quot=
;completion of the EAP authentication method&quot;<br>4.2.11: &quot;between=
 multiple inner EAP methods within EAP&quot; --&gt; &quot;after each inner =
EAP authentication method&quot;<br>4.2.13: &quot;after each successful EAP =
method&quot; --&gt; &quot;after each successful EAP authentication method&q=
uot;</div>

--0000000000004f6a1305b23754bf--


From nobody Wed Oct 21 17:39:12 2020
Return-Path: <jovergar@microsoft.com>
X-Original-To: emu@ietfa.amsl.com
Delivered-To: emu@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 6FAE73A0EB3 for <emu@ietfa.amsl.com>; Wed, 21 Oct 2020 17:39:11 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.001
X-Spam-Level: 
X-Spam-Status: No, score=-2.001 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIMWL_WL_HIGH=-0.001, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, DKIM_VALID_EF=-0.1, HTML_MESSAGE=0.001, HTTPS_HTTP_MISMATCH=0.1, RCVD_IN_MSPIKE_H2=-0.001, SPF_PASS=-0.001, URIBL_BLOCKED=0.001] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (1024-bit key) header.d=microsoft.com
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 DsOe7o8SEiw4 for <emu@ietfa.amsl.com>; Wed, 21 Oct 2020 17:39:08 -0700 (PDT)
Received: from NAM10-MW2-obe.outbound.protection.outlook.com (mail-mw2nam10on2122.outbound.protection.outlook.com [40.107.94.122]) (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 0C1573A0A50 for <emu@ietf.org>; Wed, 21 Oct 2020 17:39:07 -0700 (PDT)
ARC-Seal: i=1; a=rsa-sha256; s=arcselector9901; d=microsoft.com; cv=none; b=X11NABgVNdzlceakLa47tOi4e5hXbo51T30Sr55ji8e9Tcxs/W0w+K550QEjNW/Jcod6njb+1geiNYqghQlHPHro2hhbh3d6l2igvzXLiycm1BqVjhIZFvlhbg4DP5JTClHIKVJg2DJpjNu/ATg+hvkiaMX+RAJtpW/+PVW5GxmqKP+3uZIi+0IwroMyJS27FvxKcmVD48h48GuD2rcokAqJAKJFw+TvD09tJZSP3drlXpReU0kiiYvFpYHPOWQvkHYT8V1y2ujVtqTuHQWFFVQICoCb2krB9WUnmD+9tbaH8FKkFpv9s9TW3PE06aU3yHPKSdeMn/AXGgFCUVAEcA==
ARC-Message-Signature: i=1; a=rsa-sha256; c=relaxed/relaxed; d=microsoft.com;  s=arcselector9901; h=From:Date:Subject:Message-ID:Content-Type:MIME-Version:X-MS-Exchange-SenderADCheck; bh=EnmLnOB5UIj2XPY03Jd9OFPX25+91akzdhEckgsRhqs=; b=SZQS27woqE9am7aTzjk8Qwiy9b090khP7w4c9HGGEsjHO4LueDdghZCIDiAJuiAyhgz6xLspZOFWOf8HIs6x6SzrSQ/LxcRnLklzpUXgtnK4r9WIFhSavRJC8LDvjjX39lcmbahtHeAH2mBFibrS+Aj1Yi95VClPK2mwjzDTOnBXFnpKTVnYZSE4+sy83vZ14L5F0n6XujsVpwguBvtisL5+n7n0XvEpcRKr58uFPQ7HhzmOz/mAqDBWK8m8I1/x77qS6XJ4cQ1RHyG9OSHeqsZDfaWvJcc8LhTRaMbVJyNE3a2iYUBU9LzEAvw85ZscDEyG0yxP8CnWNb5rDQigyg==
ARC-Authentication-Results: i=1; mx.microsoft.com 1; spf=pass smtp.mailfrom=microsoft.com; dmarc=pass action=none header.from=microsoft.com; dkim=pass header.d=microsoft.com; arc=none
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=microsoft.com; s=selector2; h=From:Date:Subject:Message-ID:Content-Type:MIME-Version:X-MS-Exchange-SenderADCheck; bh=EnmLnOB5UIj2XPY03Jd9OFPX25+91akzdhEckgsRhqs=; b=O6kvV9qEMTRcFBWLvps1PkePqL2Q8vb7JJE0l/I9pjzK+Av15gycmN7VkdWkDwpkN8HH1OAsvqDVxIsgARcAl364rhqyOM3wU2vrdMPI00bBYfIcGvPzYh7XNr7qJ1MroWDYreqMtMdNs3N8+Om2laXBIm3lJhDsOr2qPQlB0g4=
Received: from CH2PR21MB1381.namprd21.prod.outlook.com (2603:10b6:610:8e::12) by CH2PR21MB1528.namprd21.prod.outlook.com (2603:10b6:610:80::13) with Microsoft SMTP Server (version=TLS1_2, cipher=TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384) id 15.20.3499.17; Thu, 22 Oct 2020 00:39:06 +0000
Received: from CH2PR21MB1381.namprd21.prod.outlook.com ([fe80::dfd:b166:92c:5a84]) by CH2PR21MB1381.namprd21.prod.outlook.com ([fe80::dfd:b166:92c:5a84%9]) with mapi id 15.20.3499.017; Thu, 22 Oct 2020 00:39:06 +0000
From: Jorge Vergara <jovergar@microsoft.com>
To: Joseph Salowey <joe@salowey.net>, EMU WG <emu@ietf.org>, Jouni Malinen <j@w1.fi>, Oleg Pekar <oleg.pekar.2017@gmail.com>
Thread-Topic: Resolution of TEAP Errata 5767
Thread-Index: AQHWqAgktSNO+oUqWESaGm4ABx1w+amixrGA
Date: Thu, 22 Oct 2020 00:39:05 +0000
Message-ID: <CH2PR21MB1381F392AAF246CE1590A318D11D0@CH2PR21MB1381.namprd21.prod.outlook.com>
References: <CAOgPGoCAFD+Z6_hCNMN8F9ODC-VTxOM+DuxjSHU25HWjqzt+ag@mail.gmail.com>
In-Reply-To: <CAOgPGoCAFD+Z6_hCNMN8F9ODC-VTxOM+DuxjSHU25HWjqzt+ag@mail.gmail.com>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
msip_labels: MSIP_Label_f42aa342-8706-4288-bd11-ebb85995028c_ActionId=013df3a4-8637-461a-bce6-8e427c5e4c38; MSIP_Label_f42aa342-8706-4288-bd11-ebb85995028c_ContentBits=0; MSIP_Label_f42aa342-8706-4288-bd11-ebb85995028c_Enabled=true; MSIP_Label_f42aa342-8706-4288-bd11-ebb85995028c_Method=Standard; MSIP_Label_f42aa342-8706-4288-bd11-ebb85995028c_Name=Internal; MSIP_Label_f42aa342-8706-4288-bd11-ebb85995028c_SetDate=2020-10-22T00:36:28Z;  MSIP_Label_f42aa342-8706-4288-bd11-ebb85995028c_SiteId=72f988bf-86f1-41af-91ab-2d7cd011db47;
authentication-results: salowey.net; dkim=none (message not signed) header.d=none;salowey.net; dmarc=none action=none header.from=microsoft.com;
x-originating-ip: [2001:4898:80e8:f:28:eedc:a141:1405]
x-ms-publictraffictype: Email
x-ms-office365-filtering-ht: Tenant
x-ms-office365-filtering-correlation-id: 51be80c7-0115-428a-64de-08d87622e1c4
x-ms-traffictypediagnostic: CH2PR21MB1528:
x-microsoft-antispam-prvs: <CH2PR21MB1528BF66C1D6BC01B5A9C5B6D11D0@CH2PR21MB1528.namprd21.prod.outlook.com>
x-ms-oob-tlc-oobclassifiers: OLM:10000;
x-ms-exchange-senderadcheck: 1
x-microsoft-antispam: BCL:0;
x-microsoft-antispam-message-info: qx0eWrd8bfGZWYptMTm0MpDqzE1d3WPNrE/3jx3mt2NngaZOr0dNQ+J0VBx4FWOC79xB4bKIJBOkFzG+52RTEyHMF9Lpi+M4Z6vlBXDKNgfXiSvgBjW3mqyGyRdldzNzCeSnsZCdYh8miVTzcPwkTGlvL03ZYP269NQUokCTXySF95Zxbbhbs9N4Pkl1fCnUP5lR+TLyqgAx59jgBFI8O5hvwtRnR3ALgjEv2bqmvh/u3Y4UU3b/ltQW3Zt/NRmtYINFTLbzyd7QoqzeG28XAM0ERQZRcj7JpcYXtSQFwDC6bT95Bx1VEFwgZkxOCnvuiGumMuXcNt2xyGTpxEkZL8D/BzX4Y9XT/KZIXWxmfxrnPVzmyzjPzmCM4ViapUiripcTZBKtXa970Z7asRhkyxGdylm300tJJMQu1P+WSF66++kjcFFajymNEAvxW28j
x-forefront-antispam-report: CIP:255.255.255.255; CTRY:; LANG:en; SCL:1; SRV:;  IPV:NLI; SFV:NSPM; H:CH2PR21MB1381.namprd21.prod.outlook.com; PTR:; CAT:NONE;  SFS:(4636009)(396003)(346002)(39860400002)(366004)(136003)(376002)(10290500003)(478600001)(64756008)(52536014)(966005)(66946007)(66476007)(66446008)(76116006)(66556008)(5660300002)(166002)(86362001)(6506007)(71200400001)(8990500004)(110136005)(53546011)(8936002)(55016002)(33656002)(7696005)(82950400001)(186003)(316002)(83380400001)(82960400001)(8676002)(9686003)(2906002)(781001); DIR:OUT; SFP:1102; 
x-ms-exchange-antispam-messagedata: f3UvfB+DI7p1cXAqE8+LLbdHAugjFMUukd9PdA6XFPtHU3uVt/nyvlvSiUjB5sW3wOIpLi9++crxF7hz8epRxYFJLF/IsxssAZHvS9KYdbAYVSMeUa7iAgC4LLVRLwa9zjrtj1ObdIB/XRziI+yvvNA7tfHto8/22NBVs//SMxNm7ru6fA2aTAtC6IGWEBP1BT+iE/9nR4LPRex1gYNo4qejoh2kYURiKxDkFTwN+9huZo2gh9qbRwTUbvDJiXYysWzxqYbE/WBdmK1Lz1urA9wFXFuEWgfYK15J2fZgUCpahr5lcxkM1+1Xin9qHmRW6jJp5Im5LXF4PPxTwLv4Auf66TSjrS6Mkinn1/Nba16jKxvaXj+V91+Zfnn2h57icoptXUluDCq012538+zfL9wrmMt3vDOS7n3p/OpSGPJvvcRE/z9kC53cbDXkNiNL/vjmuzOsppvJXK5ZIzLvFGZNi6VkqKXkx2MfmA5LxStFTklACgX5VHM6LdGUlZYWhWO17MbXpEXjk+3z42riutRg8M2fzo3mFwTHcJRkMAMtERbiPfWeiBpIDF3Qx7OJivJCSf/FsJcwrdCtkROws5TBy7pbQtkJ5IMT4Qq5FUKBxJ9qi6jvzgIAGhqnybur3QIGV2v+lpbeA1UjZXQ2zTh0A184SIZO84zetgXs/k8zGW+SJNPbOLnR9IGvVGZose5LWvKXIn5IvLuY8MX8aQ==
x-ms-exchange-transport-forked: True
Content-Type: multipart/alternative; boundary="_000_CH2PR21MB1381F392AAF246CE1590A318D11D0CH2PR21MB1381namp_"
MIME-Version: 1.0
X-OriginatorOrg: microsoft.com
X-MS-Exchange-CrossTenant-AuthAs: Internal
X-MS-Exchange-CrossTenant-AuthSource: CH2PR21MB1381.namprd21.prod.outlook.com
X-MS-Exchange-CrossTenant-Network-Message-Id: 51be80c7-0115-428a-64de-08d87622e1c4
X-MS-Exchange-CrossTenant-originalarrivaltime: 22 Oct 2020 00:39:06.0171 (UTC)
X-MS-Exchange-CrossTenant-fromentityheader: Hosted
X-MS-Exchange-CrossTenant-id: 72f988bf-86f1-41af-91ab-2d7cd011db47
X-MS-Exchange-CrossTenant-mailboxtype: HOSTED
X-MS-Exchange-CrossTenant-userprincipalname: BkBAq6nBebZ+ZfBoaxsORlEaz6Ce4wOLXAQfiXOGH/lAQjXsmE9inh/bjptiC1PUTtJij0ltA1/ySPFaDbOZrg==
X-MS-Exchange-Transport-CrossTenantHeadersStamped: CH2PR21MB1528
Archived-At: <https://mailarchive.ietf.org/arch/msg/emu/7mrivP4pwrK94N9tAuhjiNZZ8Kc>
Subject: Re: [Emu] Resolution of TEAP Errata 5767
X-BeenThere: emu@ietf.org
X-Mailman-Version: 2.1.29
Precedence: list
List-Id: "EAP Methods Update \(EMU\)" <emu.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/emu>, <mailto:emu-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/emu/>
List-Post: <mailto:emu@ietf.org>
List-Help: <mailto:emu-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/emu>, <mailto:emu-request@ietf.org?subject=subscribe>
X-List-Received-Date: Thu, 22 Oct 2020 00:39:11 -0000

--_000_CH2PR21MB1381F392AAF246CE1590A318D11D0CH2PR21MB1381namp_
Content-Type: text/plain; charset="utf-8"
Content-Transfer-Encoding: base64

SSBhZ3JlZSB3aXRoIGFsbCB0aGUgcHJvcG9zZWQgcmVzb2x1dGlvbnMuIEZvciBjb250ZXh0LCB0
aGVyZSB3YXMgc29tZSBwcmlvciBkaXNjdXNzaW9uIG9mIHRoaXMgZXJyYXRhIGhlcmU6IGh0dHBz
Oi8vbWFpbGFyY2hpdmUuaWV0Zi5vcmcvYXJjaC9tc2cvZW11L0tfWFdCTWV2S05keGRXc2tLOFJr
QnQxWnBTUS8NCg0KSm9yZ2UgVmVyZ2FyYQ0KDQpGcm9tOiBKb3NlcGggU2Fsb3dleSA8am9lQHNh
bG93ZXkubmV0Pg0KU2VudDogV2VkbmVzZGF5LCBPY3RvYmVyIDIxLCAyMDIwIDU6MTMgUE0NClRv
OiBFTVUgV0cgPGVtdUBpZXRmLm9yZz47IEpvdW5pIE1hbGluZW4gPGpAdzEuZmk+OyBKb3JnZSBW
ZXJnYXJhIDxqb3ZlcmdhckBtaWNyb3NvZnQuY29tPjsgT2xlZyBQZWthciA8b2xlZy5wZWthci4y
MDE3QGdtYWlsLmNvbT4NClN1YmplY3Q6IFJlc29sdXRpb24gb2YgVEVBUCBFcnJhdGEgNTc2Nw0K
DQpFcnJhdGEgNTc2NzogaHR0cHM6Ly93d3cucmZjLWVkaXRvci5vcmcvZXJyYXRhL2VpZDU3Njc8
aHR0cHM6Ly9uYW0wNi5zYWZlbGlua3MucHJvdGVjdGlvbi5vdXRsb29rLmNvbS8/dXJsPWh0dHBz
JTNBJTJGJTJGd3d3LnJmYy1lZGl0b3Iub3JnJTJGZXJyYXRhJTJGZWlkNTc2NyZkYXRhPTA0JTdD
MDElN0Nqb3ZlcmdhciU0MG1pY3Jvc29mdC5jb20lN0M1MGI1NmFmYWRjZjM0NzMyZDUwNzA4ZDg3
NjFmNDVkNSU3QzcyZjk4OGJmODZmMTQxYWY5MWFiMmQ3Y2QwMTFkYjQ3JTdDMSU3QzAlN0M2Mzcz
ODkyMjM5Nzc0MTA0NDQlN0NVbmtub3duJTdDVFdGcGJHWnNiM2Q4ZXlKV0lqb2lNQzR3TGpBd01E
QWlMQ0pRSWpvaVYybHVNeklpTENKQlRpSTZJazFoYVd3aUxDSlhWQ0k2TW4wJTNEJTdDMTAwMCZz
ZGF0YT0yNHklMkJrcnNCdzFtZEd1Tk1NZ3FtcWlSeiUyQnFlRnQ5alZYNHFVSHRsVUp3WSUzRCZy
ZXNlcnZlZD0wPg0KU3RhdHVzOiBWZXJpZmllZA0KUmV2aXNpb246DQoNClNlY3Rpb24gMy4zLjEg
c2F5czoNCg0KICAgRUFQIG1ldGhvZCBtZXNzYWdlcyBhcmUgY2FycmllZCB3aXRoaW4gRUFQLVBh
eWxvYWQgVExWcyBkZWZpbmVkIGluDQogICBTZWN0aW9uIDQuMi4xMC4gIElmIG1vcmUgdGhhbiBv
bmUgbWV0aG9kIGlzIGdvaW5nIHRvIGJlIGV4ZWN1dGVkIGluDQogICB0aGUgdHVubmVsLCB0aGVu
IHVwb24gbWV0aG9kIGNvbXBsZXRpb24sIHRoZSBzZXJ2ZXIgTVVTVCBzZW5kIGFuDQogICBJbnRl
cm1lZGlhdGUtUmVzdWx0IFRMViBpbmRpY2F0aW5nIHRoZSByZXN1bHQuDQoNCkl0IHNob3VsZCBz
YXk6DQoNCiAgIEVBUCBtZXRob2QgbWVzc2FnZXMgYXJlIGNhcnJpZWQgd2l0aGluIEVBUC1QYXls
b2FkIFRMVnMgZGVmaW5lZCBpbg0KICAgU2VjdGlvbiA0LjIuMTAuICBVcG9uIGNvbXBsZXRpb24g
b2YgZWFjaCBFQVAgYXV0aGVudGljYXRpb24gbWV0aG9kIGluDQogICB0aGUgdHVubmVsLCB0aGUg
c2VydmVyIE1VU1Qgc2VuZCBhbiBJbnRlcm1lZGlhdGUtUmVzdWx0IFRMVg0KICAgaW5kaWNhdGlu
ZyB0aGUgcmVzdWx0Lg0KDQpTZWN0aW9uIDMuMy4zIHNheXM6DQoNCiAgVGhlIENyeXB0by1CaW5k
aW5nIFRMViBhbmQgSW50ZXJtZWRpYXRlLVJlc3VsdCBUTFYgTVVTVCBiZSBpbmNsdWRlZA0KICB0
byBwZXJmb3JtIGNyeXB0b2dyYXBoaWMgYmluZGluZyBhZnRlciBlYWNoIHN1Y2Nlc3NmdWwgRUFQ
IG1ldGhvZCBpbiBhDQogIHNlcXVlbmNlIG9mIG9uZSBvciBtb3JlIEVBUCBtZXRob2RzLg0KDQpJ
dCBzaG91bGQgc2F5Og0KDQogIFRoZSBDcnlwdG8tQmluZGluZyBUTFYgYW5kIEludGVybWVkaWF0
ZS1SZXN1bHQgVExWIE1VU1QgYmUgaW5jbHVkZWQNCiAgdG8gcGVyZm9ybSBjcnlwdG9ncmFwaGlj
IGJpbmRpbmcgYWZ0ZXIgZWFjaCBzdWNjZXNzZnVsIEVBUCBhdXRoZW50aWNhdGlvbg0KICBtZXRo
b2QgaW4gYSBzZXF1ZW5jZSBvZiBvbmUgb3IgbW9yZSBFQVAgbWV0aG9kcy4NCg0KU2VjdGlvbiAz
LjguMyBzYXlzOg0KDQogICBVcG9uIHN1Y2Nlc3NmdWwgY29tcGxldGlvbiBvZiB0aGUgRUFQIG1l
dGhvZCBpbiBQaGFzZSAyLCB0aGUgcGVlciBhbmQNCiAgIHNlcnZlciBleGNoYW5nZSBhIENyeXB0
by1CaW5kaW5nIFRMViB0byBiaW5kIHRoZSBpbm5lciBtZXRob2Qgd2l0aA0KICAgdGhlIG91dGVy
IHR1bm5lbCBhbmQgZW5zdXJlIHRoYXQgYSBtYW4taW4tdGhlLW1pZGRsZSBhdHRhY2sgaGFzIG5v
dA0KICAgYmVlbiBhdHRlbXB0ZWQuDQoNCkl0IHNob3VsZCBzYXk6DQoNCiAgIFVwb24gc3VjY2Vz
c2Z1bCBjb21wbGV0aW9uIG9mIHRoZSBFQVAgYXV0aGVudGljYXRpb24gbWV0aG9kIGluIFBoYXNl
IDIsDQogICB0aGUgcGVlciBhbmQgc2VydmVyIGV4Y2hhbmdlIGEgQ3J5cHRvLUJpbmRpbmcgVExW
IHRvIGJpbmQgdGhlIGlubmVyDQogICBtZXRob2Qgd2l0aCB0aGUgb3V0ZXIgdHVubmVsIGFuZCBl
bnN1cmUgdGhhdCBhIG1hbi1pbi10aGUtbWlkZGxlIGF0dGFjaw0KICAgaGFzIG5vdCBiZWVuIGF0
dGVtcHRlZC4NCg0KU2VjdGlvbiA0LjIuMTEgc2F5czoNCg0KICAgVGhlIEludGVybWVkaWF0ZS1S
ZXN1bHQgVExWIHByb3ZpZGVzIHN1cHBvcnQgZm9yIGFja25vd2xlZGdlZA0KICAgaW50ZXJtZWRp
YXRlIFN1Y2Nlc3MgYW5kIEZhaWx1cmUgbWVzc2FnZXMgYmV0d2VlbiBtdWx0aXBsZQ0KICAgaW5u
ZXIgRUFQIG1ldGhvZHMgd2l0aGluIEVBUC4NCg0KSXQgc2hvdWxkIHNheToNCg0KICBUaGUgSW50
ZXJtZWRpYXRlLVJlc3VsdCBUTFYgcHJvdmlkZXMgc3VwcG9ydCBmb3IgYWNrbm93bGVkZ2VkDQog
IGludGVybWVkaWF0ZSBTdWNjZXNzIGFuZCBGYWlsdXJlIG1lc3NhZ2VzIGFmdGVyIGVhY2ggaW5u
ZXIgRUFQDQogIGF1dGhlbnRpY2F0aW9uIG1ldGhvZC4NCg0KU2VjdGlvbiA0LjIuMTMgc2F5czoN
Cg0KIEl0IE1VU1QgYmUgaW5jbHVkZWQgd2l0aCB0aGUgSW50ZXJtZWRpYXRlLVJlc3VsdCBUTFYg
dG8gcGVyZm9ybQ0KIGNyeXB0b2dyYXBoaWMgYmluZGluZyBhZnRlciBlYWNoIHN1Y2Nlc3NmdWwg
RUFQIG1ldGhvZCBpbiBhDQogc2VxdWVuY2Ugb2YgRUFQIG1ldGhvZHMsIGJlZm9yZSBwcm9jZWVk
aW5nIHdpdGggYW5vdGhlciBpbm5lcg0KIEVBUCBtZXRob2QuDQoNCkl0IHNob3VsZCBzYXk6DQoN
CiBJdCBNVVNUIGJlIGluY2x1ZGVkIHdpdGggdGhlIEludGVybWVkaWF0ZS1SZXN1bHQgVExWIHRv
IHBlcmZvcm0NCiBjcnlwdG9ncmFwaGljIGJpbmRpbmcgYWZ0ZXIgZWFjaCBzdWNjZXNzZnVsIEVB
UCBhdXRoZW50aWNhdGlvbg0KIG1ldGhvZCBpbiBhIHNlcXVlbmNlIG9mIEVBUCBtZXRob2RzLCBi
ZWZvcmUgcHJvY2VlZGluZyB3aXRoDQogYW5vdGhlciBpbm5lciBFQVAgbWV0aG9kLg0KDQpOb3Rl
czoNCg0KVEVBUCBkZXNjcmlwdGlvbiBpcyBzb21ld2hhdCB2YWd1ZSBpbiBkaXNjdXNzaW9uIGFi
b3V0ICJFQVAgbWV0aG9kcyIgdnMuICJFQVAgYXV0aGVudGljYXRpb24gbWV0aG9kcyIgYXMgaXQg
Y29tZXMgdG8gdGhlIEVBUCBtZXRob2RzIHBlcmZvcm1lZCBpbiBQaGFzZSAyIHdpdGhpbiB0aGUg
VExTIHR1bm5lbC4gUkZDIDM3NDggZGVmaW5lcyBJZGVudGl0eSByZXF1ZXN0L3Jlc3BvbnNlIGFz
IGFuIEVBUCBtZXRob2QuIEhvd2V2ZXIsIHRoaXMgbWV0aG9kIGlzIG5vdCBhbiAiYXV0aGVudGlj
YXRpb24gbWV0aG9kIiB3aGljaCBpcyBhIHNwZWNpYWwgY2FzZSBvZiBhbiBtZXRob2Qgd2hlcmUg
dGhlIFR5cGUgaXMgNCBvciBncmVhdGVyLg0KDQpSRkMgNzE3MCB1c2VzIGNvcnJlY3QgdGVybWlu
b2xvZ3kgaW4gdGhlIGZpcnN0IHBhcmFncmFwaCBvZiBTZWN0aW9uIDMuMy4xIHdoZW4gdGFsa2lu
ZyBhYm91dCBtdWx0aXBsZSBhdXRoZW50aWNhdGlvbiBtZXRob2RzIG5vdCBiZWluZyBhbGxvd2Vk
IGJ5IFJGQyAzNzQ4IGluIGEgc2luZ2xlIEVBUCBjb252ZXJzYXRpb24uIEhvd2V2ZXIsIG1hbnks
IGJ1dCBub3QgYWxsLCBvZiB0aGUgZm9sbG93aW5nICJbRUFQXSBtZXRob2QiIGluc3RhbmNlcyBh
cmUgYWN0dWFsbHkgcmVmZXJyaW5nIHRvICJbRUFQXSBhdXRoZW50aWNhdGlvbiBtZXRob2QiLiBU
aGlzIHJlc3VsdHMgaW4gaW5jb3JyZWN0IGNsYWltcyBvbiB3aGVuIHRoZSBJbnRlcm1lZGlhdGUt
UmVzdWx0IFRMViBhbmQgQ3J5cHRvLUJpbmRpbmcgVExWIGFyZSB1c2VkLiBUaGV5IGFyZSBub3Qg
dXNlZCBhZnRlciBhbiBFQVAgbm9uLWF1dGhlbnRpY2F0aW9uIG1ldGhvZCBsaWtlIElkZW50aXR5
IChlLmcuLCBzZWUgdGhlIGV4YW1wbGUgaW4gQy4zKTsgdGhleSBhcmUgdXNlZCBhZnRlciBlYWNo
IEVBUCBhdXRoZW50aWNhdGlvbiBtZXRob2QgbGlrZSBFQVAtcHdkLg0KDQpGdXJ0aGVybW9yZSwg
dGhlIGNvbW1lbnQgYWJvdXQgIm1vcmUgdGhhbiBvbmUgbWV0aG9kIGlzIGdvaW5nIHRvIGJlIGV4
ZWN1dGVkIGluIHRoZSB0dW5uZWwiIGRvZXMgbm90IHNvdW5kIGFjY3VyYXRlLiBUaGlzIGFwcGxp
ZXMgZXZlbiBpZiBvbmx5IGEgc2luZ2xlIEVBUCBhdXRoZW50aWNhdGlvbiBtZXRob2QgaXMgZXhl
Y3V0ZWQgaW4gdGhlIHR1bm5lbCAoSWRlbnRpdHkgbWV0aG9kIGlzIG5vdCByZXF1aXJlZCB0byBi
ZSBleGVjdXRlZCkuIFRoZSBwcm9wb3NlZCB0ZXh0IGluIHRoaXMgZXJyYXRhIGVudHJ5IGFkZHJl
c3NlcyB0aGVzZSB0d28gaXNzdWVzIGluIFNlY3Rpb24gMy4zLjEuIFRoZSBmb2xsb3dpbmcgYWRk
aXRpb25hbCBjaGFuZ2VzIHdvdWxkIGJlIG5lZWRlZCB0byBtYWtlIHJlc3Qgb2YgdGhlIHNwZWNp
ZmljYXRpb24gdXNlIHRoZSB0ZXJtcyBtb3JlIGFjY3VyYXRlbHk6DQoNCjMuMy4zOiAiYWZ0ZXIg
ZWFjaCBzdWNjZXNzZnVsIEVBUCBtZXRob2QiIC0tPiAiYWZ0ZXIgZWFjaCBzdWNjZXNzZnVsIEVB
UCBhdXRoZW50aWNhdGlvbiBtZXRob2QiDQozLjguMzogImNvbXBsZXRpb24gb2YgdGhlIEVBUCBt
ZXRob2QiIC0tPiAiY29tcGxldGlvbiBvZiB0aGUgRUFQIGF1dGhlbnRpY2F0aW9uIG1ldGhvZCIN
CjQuMi4xMTogImJldHdlZW4gbXVsdGlwbGUgaW5uZXIgRUFQIG1ldGhvZHMgd2l0aGluIEVBUCIg
LS0+ICJhZnRlciBlYWNoIGlubmVyIEVBUCBhdXRoZW50aWNhdGlvbiBtZXRob2QiDQo0LjIuMTM6
ICJhZnRlciBlYWNoIHN1Y2Nlc3NmdWwgRUFQIG1ldGhvZCIgLS0+ICJhZnRlciBlYWNoIHN1Y2Nl
c3NmdWwgRUFQIGF1dGhlbnRpY2F0aW9uIG1ldGhvZCINCg==

--_000_CH2PR21MB1381F392AAF246CE1590A318D11D0CH2PR21MB1381namp_
Content-Type: text/html; charset="utf-8"
Content-Transfer-Encoding: base64

PGh0bWwgeG1sbnM6dj0idXJuOnNjaGVtYXMtbWljcm9zb2Z0LWNvbTp2bWwiIHhtbG5zOm89InVy
bjpzY2hlbWFzLW1pY3Jvc29mdC1jb206b2ZmaWNlOm9mZmljZSIgeG1sbnM6dz0idXJuOnNjaGVt
YXMtbWljcm9zb2Z0LWNvbTpvZmZpY2U6d29yZCIgeG1sbnM6bT0iaHR0cDovL3NjaGVtYXMubWlj
cm9zb2Z0LmNvbS9vZmZpY2UvMjAwNC8xMi9vbW1sIiB4bWxucz0iaHR0cDovL3d3dy53My5vcmcv
VFIvUkVDLWh0bWw0MCI+DQo8aGVhZD4NCjxtZXRhIGh0dHAtZXF1aXY9IkNvbnRlbnQtVHlwZSIg
Y29udGVudD0idGV4dC9odG1sOyBjaGFyc2V0PXV0Zi04Ij4NCjxtZXRhIG5hbWU9IkdlbmVyYXRv
ciIgY29udGVudD0iTWljcm9zb2Z0IFdvcmQgMTUgKGZpbHRlcmVkIG1lZGl1bSkiPg0KPHN0eWxl
PjwhLS0NCi8qIEZvbnQgRGVmaW5pdGlvbnMgKi8NCkBmb250LWZhY2UNCgl7Zm9udC1mYW1pbHk6
IkNhbWJyaWEgTWF0aCI7DQoJcGFub3NlLTE6MiA0IDUgMyA1IDQgNiAzIDIgNDt9DQpAZm9udC1m
YWNlDQoJe2ZvbnQtZmFtaWx5OkNhbGlicmk7DQoJcGFub3NlLTE6MiAxNSA1IDIgMiAyIDQgMyAy
IDQ7fQ0KLyogU3R5bGUgRGVmaW5pdGlvbnMgKi8NCnAuTXNvTm9ybWFsLCBsaS5Nc29Ob3JtYWws
IGRpdi5Nc29Ob3JtYWwNCgl7bWFyZ2luOjBpbjsNCglmb250LXNpemU6MTEuMHB0Ow0KCWZvbnQt
ZmFtaWx5OiJDYWxpYnJpIixzYW5zLXNlcmlmO30NCmE6bGluaywgc3Bhbi5Nc29IeXBlcmxpbmsN
Cgl7bXNvLXN0eWxlLXByaW9yaXR5Ojk5Ow0KCWNvbG9yOmJsdWU7DQoJdGV4dC1kZWNvcmF0aW9u
OnVuZGVybGluZTt9DQpzcGFuLkVtYWlsU3R5bGUxOA0KCXttc28tc3R5bGUtdHlwZTpwZXJzb25h
bC1yZXBseTsNCglmb250LWZhbWlseToiQ2FsaWJyaSIsc2Fucy1zZXJpZjsNCgljb2xvcjp3aW5k
b3d0ZXh0O30NCi5Nc29DaHBEZWZhdWx0DQoJe21zby1zdHlsZS10eXBlOmV4cG9ydC1vbmx5Ow0K
CWZvbnQtZmFtaWx5OiJDYWxpYnJpIixzYW5zLXNlcmlmO30NCkBwYWdlIFdvcmRTZWN0aW9uMQ0K
CXtzaXplOjguNWluIDExLjBpbjsNCgltYXJnaW46MS4waW4gMS4waW4gMS4waW4gMS4waW47fQ0K
ZGl2LldvcmRTZWN0aW9uMQ0KCXtwYWdlOldvcmRTZWN0aW9uMTt9DQotLT48L3N0eWxlPjwhLS1b
aWYgZ3RlIG1zbyA5XT48eG1sPg0KPG86c2hhcGVkZWZhdWx0cyB2OmV4dD0iZWRpdCIgc3BpZG1h
eD0iMTAyNiIgLz4NCjwveG1sPjwhW2VuZGlmXS0tPjwhLS1baWYgZ3RlIG1zbyA5XT48eG1sPg0K
PG86c2hhcGVsYXlvdXQgdjpleHQ9ImVkaXQiPg0KPG86aWRtYXAgdjpleHQ9ImVkaXQiIGRhdGE9
IjEiIC8+DQo8L286c2hhcGVsYXlvdXQ+PC94bWw+PCFbZW5kaWZdLS0+DQo8L2hlYWQ+DQo8Ym9k
eSBsYW5nPSJFTi1VUyIgbGluaz0iYmx1ZSIgdmxpbms9InB1cnBsZSIgc3R5bGU9IndvcmQtd3Jh
cDpicmVhay13b3JkIj4NCjxkaXYgY2xhc3M9IldvcmRTZWN0aW9uMSI+DQo8cCBjbGFzcz0iTXNv
Tm9ybWFsIj5JIGFncmVlIHdpdGggYWxsIHRoZSBwcm9wb3NlZCByZXNvbHV0aW9ucy4gRm9yIGNv
bnRleHQsIHRoZXJlIHdhcyBzb21lIHByaW9yIGRpc2N1c3Npb24gb2YgdGhpcyBlcnJhdGEgaGVy
ZToNCjxhIGhyZWY9Imh0dHBzOi8vbWFpbGFyY2hpdmUuaWV0Zi5vcmcvYXJjaC9tc2cvZW11L0tf
WFdCTWV2S05keGRXc2tLOFJrQnQxWnBTUS8iPg0KaHR0cHM6Ly9tYWlsYXJjaGl2ZS5pZXRmLm9y
Zy9hcmNoL21zZy9lbXUvS19YV0JNZXZLTmR4ZFdza0s4UmtCdDFacFNRLzwvYT48bzpwPjwvbzpw
PjwvcD4NCjxwIGNsYXNzPSJNc29Ob3JtYWwiPjxvOnA+Jm5ic3A7PC9vOnA+PC9wPg0KPHAgY2xh
c3M9Ik1zb05vcm1hbCI+Sm9yZ2UgVmVyZ2FyYTxvOnA+PC9vOnA+PC9wPg0KPHAgY2xhc3M9Ik1z
b05vcm1hbCI+PG86cD4mbmJzcDs8L286cD48L3A+DQo8ZGl2IHN0eWxlPSJib3JkZXI6bm9uZTti
b3JkZXItdG9wOnNvbGlkICNFMUUxRTEgMS4wcHQ7cGFkZGluZzozLjBwdCAwaW4gMGluIDBpbiI+
DQo8cCBjbGFzcz0iTXNvTm9ybWFsIj48Yj5Gcm9tOjwvYj4gSm9zZXBoIFNhbG93ZXkgJmx0O2pv
ZUBzYWxvd2V5Lm5ldCZndDsgPGJyPg0KPGI+U2VudDo8L2I+IFdlZG5lc2RheSwgT2N0b2JlciAy
MSwgMjAyMCA1OjEzIFBNPGJyPg0KPGI+VG86PC9iPiBFTVUgV0cgJmx0O2VtdUBpZXRmLm9yZyZn
dDs7IEpvdW5pIE1hbGluZW4gJmx0O2pAdzEuZmkmZ3Q7OyBKb3JnZSBWZXJnYXJhICZsdDtqb3Zl
cmdhckBtaWNyb3NvZnQuY29tJmd0OzsgT2xlZyBQZWthciAmbHQ7b2xlZy5wZWthci4yMDE3QGdt
YWlsLmNvbSZndDs8YnI+DQo8Yj5TdWJqZWN0OjwvYj4gUmVzb2x1dGlvbiBvZiBURUFQIEVycmF0
YSA1NzY3PG86cD48L286cD48L3A+DQo8L2Rpdj4NCjxwIGNsYXNzPSJNc29Ob3JtYWwiPjxvOnA+
Jm5ic3A7PC9vOnA+PC9wPg0KPHAgY2xhc3M9Ik1zb05vcm1hbCI+RXJyYXRhIDU3Njc6Jm5ic3A7
PGEgaHJlZj0iaHR0cHM6Ly9uYW0wNi5zYWZlbGlua3MucHJvdGVjdGlvbi5vdXRsb29rLmNvbS8/
dXJsPWh0dHBzJTNBJTJGJTJGd3d3LnJmYy1lZGl0b3Iub3JnJTJGZXJyYXRhJTJGZWlkNTc2NyZh
bXA7ZGF0YT0wNCU3QzAxJTdDam92ZXJnYXIlNDBtaWNyb3NvZnQuY29tJTdDNTBiNTZhZmFkY2Yz
NDczMmQ1MDcwOGQ4NzYxZjQ1ZDUlN0M3MmY5ODhiZjg2ZjE0MWFmOTFhYjJkN2NkMDExZGI0NyU3
QzElN0MwJTdDNjM3Mzg5MjIzOTc3NDEwNDQ0JTdDVW5rbm93biU3Q1RXRnBiR1pzYjNkOGV5SldJ
am9pTUM0d0xqQXdNREFpTENKUUlqb2lWMmx1TXpJaUxDSkJUaUk2SWsxaGFXd2lMQ0pYVkNJNk1u
MCUzRCU3QzEwMDAmYW1wO3NkYXRhPTI0eSUyQmtyc0J3MW1kR3VOTU1ncW1xaVJ6JTJCcWVGdDlq
Vlg0cVVIdGxVSndZJTNEJmFtcDtyZXNlcnZlZD0wIj5odHRwczovL3d3dy5yZmMtZWRpdG9yLm9y
Zy9lcnJhdGEvZWlkNTc2NzwvYT48YnI+DQpTdGF0dXM6IFZlcmlmaWVkPG86cD48L286cD48L3A+
DQo8ZGl2Pg0KPHAgY2xhc3M9Ik1zb05vcm1hbCI+UmV2aXNpb246PG86cD48L286cD48L3A+DQo8
L2Rpdj4NCjxkaXY+DQo8cCBjbGFzcz0iTXNvTm9ybWFsIj48bzpwPiZuYnNwOzwvbzpwPjwvcD4N
CjwvZGl2Pg0KPHAgY2xhc3M9Ik1zb05vcm1hbCI+U2VjdGlvbiAzLjMuMSBzYXlzOjxicj4NCjxi
cj4NCiZuYnNwOyAmbmJzcDtFQVAgbWV0aG9kIG1lc3NhZ2VzIGFyZSBjYXJyaWVkIHdpdGhpbiBF
QVAtUGF5bG9hZCBUTFZzIGRlZmluZWQgaW48YnI+DQombmJzcDsgJm5ic3A7U2VjdGlvbiA0LjIu
MTAuJm5ic3A7IElmIG1vcmUgdGhhbiBvbmUgbWV0aG9kIGlzIGdvaW5nIHRvIGJlIGV4ZWN1dGVk
IGluPGJyPg0KJm5ic3A7ICZuYnNwO3RoZSB0dW5uZWwsIHRoZW4gdXBvbiBtZXRob2QgY29tcGxl
dGlvbiwgdGhlIHNlcnZlciBNVVNUIHNlbmQgYW48YnI+DQombmJzcDsgJm5ic3A7SW50ZXJtZWRp
YXRlLVJlc3VsdCBUTFYgaW5kaWNhdGluZyB0aGUgcmVzdWx0Ljxicj4NCjxicj4NCkl0IHNob3Vs
ZCBzYXk6PGJyPg0KPGJyPg0KJm5ic3A7ICZuYnNwO0VBUCBtZXRob2QgbWVzc2FnZXMgYXJlIGNh
cnJpZWQgd2l0aGluIEVBUC1QYXlsb2FkIFRMVnMgZGVmaW5lZCBpbjxicj4NCiZuYnNwOyAmbmJz
cDtTZWN0aW9uIDQuMi4xMC4mbmJzcDsgVXBvbiBjb21wbGV0aW9uIG9mIGVhY2ggRUFQIGF1dGhl
bnRpY2F0aW9uIG1ldGhvZCBpbjxicj4NCiZuYnNwOyAmbmJzcDt0aGUgdHVubmVsLCB0aGUgc2Vy
dmVyIE1VU1Qgc2VuZCBhbiBJbnRlcm1lZGlhdGUtUmVzdWx0IFRMVjxicj4NCiZuYnNwOyAmbmJz
cDtpbmRpY2F0aW5nIHRoZSByZXN1bHQuPG86cD48L286cD48L3A+DQo8ZGl2Pg0KPHAgY2xhc3M9
Ik1zb05vcm1hbCI+PG86cD4mbmJzcDs8L286cD48L3A+DQo8L2Rpdj4NCjxkaXY+DQo8cCBjbGFz
cz0iTXNvTm9ybWFsIj5TZWN0aW9uIDMuMy4zIHNheXM6Jm5ic3A7PG86cD48L286cD48L3A+DQo8
L2Rpdj4NCjxkaXY+DQo8cCBjbGFzcz0iTXNvTm9ybWFsIj48bzpwPiZuYnNwOzwvbzpwPjwvcD4N
CjwvZGl2Pg0KPHAgY2xhc3M9Ik1zb05vcm1hbCI+Jm5ic3A7IFRoZSBDcnlwdG8tQmluZGluZyBU
TFYgYW5kIEludGVybWVkaWF0ZS1SZXN1bHQgVExWIE1VU1QgYmUgaW5jbHVkZWQmbmJzcDs8bzpw
PjwvbzpwPjwvcD4NCjxkaXY+DQo8cCBjbGFzcz0iTXNvTm9ybWFsIj4mbmJzcDsgdG8gcGVyZm9y
bSBjcnlwdG9ncmFwaGljIGJpbmRpbmcgYWZ0ZXIgZWFjaCBzdWNjZXNzZnVsIEVBUCBtZXRob2Qg
aW4gYSZuYnNwOzxvOnA+PC9vOnA+PC9wPg0KPC9kaXY+DQo8ZGl2Pg0KPHAgY2xhc3M9Ik1zb05v
cm1hbCI+Jm5ic3A7IHNlcXVlbmNlIG9mIG9uZSBvciBtb3JlIEVBUCBtZXRob2RzLjxvOnA+PC9v
OnA+PC9wPg0KPC9kaXY+DQo8ZGl2Pg0KPHAgY2xhc3M9Ik1zb05vcm1hbCI+PG86cD4mbmJzcDs8
L286cD48L3A+DQo8L2Rpdj4NCjxkaXY+DQo8cCBjbGFzcz0iTXNvTm9ybWFsIj5JdCBzaG91bGQg
c2F5OjxvOnA+PC9vOnA+PC9wPg0KPC9kaXY+DQo8ZGl2Pg0KPHAgY2xhc3M9Ik1zb05vcm1hbCI+
PG86cD4mbmJzcDs8L286cD48L3A+DQo8L2Rpdj4NCjxkaXY+DQo8cCBjbGFzcz0iTXNvTm9ybWFs
Ij4mbmJzcDsgVGhlIENyeXB0by1CaW5kaW5nIFRMViBhbmQgSW50ZXJtZWRpYXRlLVJlc3VsdCBU
TFYgTVVTVCBiZSBpbmNsdWRlZCZuYnNwOzxvOnA+PC9vOnA+PC9wPg0KPGRpdj4NCjxwIGNsYXNz
PSJNc29Ob3JtYWwiPiZuYnNwOyB0byBwZXJmb3JtIGNyeXB0b2dyYXBoaWMgYmluZGluZyBhZnRl
ciBlYWNoIHN1Y2Nlc3NmdWwgRUFQIGF1dGhlbnRpY2F0aW9uJm5ic3A7PG86cD48L286cD48L3A+
DQo8L2Rpdj4NCjxkaXY+DQo8cCBjbGFzcz0iTXNvTm9ybWFsIj4mbmJzcDsgbWV0aG9kIGluIGEg
c2VxdWVuY2Ugb2Ygb25lIG9yIG1vcmUgRUFQIG1ldGhvZHMuPG86cD48L286cD48L3A+DQo8L2Rp
dj4NCjwvZGl2Pg0KPGRpdj4NCjxwIGNsYXNzPSJNc29Ob3JtYWwiPjxvOnA+Jm5ic3A7PC9vOnA+
PC9wPg0KPC9kaXY+DQo8ZGl2Pg0KPHAgY2xhc3M9Ik1zb05vcm1hbCI+U2VjdGlvbiAzLjguMyBz
YXlzOiZuYnNwOzxvOnA+PC9vOnA+PC9wPg0KPC9kaXY+DQo8cCBjbGFzcz0iTXNvTm9ybWFsIj48
YnI+DQombmJzcDsgJm5ic3A7VXBvbiBzdWNjZXNzZnVsIGNvbXBsZXRpb24gb2YgdGhlIEVBUCBt
ZXRob2QgaW4gUGhhc2UgMiwgdGhlIHBlZXIgYW5kPGJyPg0KJm5ic3A7ICZuYnNwO3NlcnZlciBl
eGNoYW5nZSBhIENyeXB0by1CaW5kaW5nIFRMViB0byBiaW5kIHRoZSBpbm5lciBtZXRob2Qgd2l0
aDxicj4NCiZuYnNwOyAmbmJzcDt0aGUgb3V0ZXIgdHVubmVsIGFuZCBlbnN1cmUgdGhhdCBhIG1h
bi1pbi10aGUtbWlkZGxlIGF0dGFjayBoYXMgbm90PGJyPg0KJm5ic3A7ICZuYnNwO2JlZW4gYXR0
ZW1wdGVkLjxvOnA+PC9vOnA+PC9wPg0KPGRpdj4NCjxwIGNsYXNzPSJNc29Ob3JtYWwiPjxvOnA+
Jm5ic3A7PC9vOnA+PC9wPg0KPC9kaXY+DQo8ZGl2Pg0KPHAgY2xhc3M9Ik1zb05vcm1hbCI+SXQg
c2hvdWxkIHNheTo8bzpwPjwvbzpwPjwvcD4NCjwvZGl2Pg0KPGRpdj4NCjxwIGNsYXNzPSJNc29O
b3JtYWwiPjxvOnA+Jm5ic3A7PC9vOnA+PC9wPg0KPC9kaXY+DQo8ZGl2Pg0KPHAgY2xhc3M9Ik1z
b05vcm1hbCI+Jm5ic3A7ICZuYnNwO1Vwb24gc3VjY2Vzc2Z1bCBjb21wbGV0aW9uIG9mIHRoZSBF
QVAgYXV0aGVudGljYXRpb24gbWV0aG9kIGluIFBoYXNlIDIsJm5ic3A7PG86cD48L286cD48L3A+
DQo8L2Rpdj4NCjxkaXY+DQo8cCBjbGFzcz0iTXNvTm9ybWFsIj4mbmJzcDsgJm5ic3A7dGhlIHBl
ZXIgYW5kIHNlcnZlciBleGNoYW5nZSBhIENyeXB0by1CaW5kaW5nIFRMViB0byBiaW5kIHRoZSBp
bm5lciZuYnNwOzxvOnA+PC9vOnA+PC9wPg0KPC9kaXY+DQo8ZGl2Pg0KPHAgY2xhc3M9Ik1zb05v
cm1hbCI+Jm5ic3A7ICZuYnNwO21ldGhvZCB3aXRoIHRoZSBvdXRlciB0dW5uZWwgYW5kIGVuc3Vy
ZSB0aGF0IGEgbWFuLWluLXRoZS1taWRkbGUgYXR0YWNrJm5ic3A7PG86cD48L286cD48L3A+DQo8
L2Rpdj4NCjxkaXY+DQo8cCBjbGFzcz0iTXNvTm9ybWFsIj4mbmJzcDsgJm5ic3A7aGFzIG5vdCBi
ZWVuIGF0dGVtcHRlZC48bzpwPjwvbzpwPjwvcD4NCjwvZGl2Pg0KPGRpdj4NCjxwIGNsYXNzPSJN
c29Ob3JtYWwiPjxvOnA+Jm5ic3A7PC9vOnA+PC9wPg0KPC9kaXY+DQo8ZGl2Pg0KPHAgY2xhc3M9
Ik1zb05vcm1hbCI+U2VjdGlvbiA0LjIuMTEgc2F5czo8bzpwPjwvbzpwPjwvcD4NCjwvZGl2Pg0K
PGRpdj4NCjxwIGNsYXNzPSJNc29Ob3JtYWwiPjxvOnA+Jm5ic3A7PC9vOnA+PC9wPg0KPC9kaXY+
DQo8cCBjbGFzcz0iTXNvTm9ybWFsIj4mbmJzcDsgJm5ic3A7VGhlIEludGVybWVkaWF0ZS1SZXN1
bHQgVExWIHByb3ZpZGVzIHN1cHBvcnQgZm9yIGFja25vd2xlZGdlZDxvOnA+PC9vOnA+PC9wPg0K
PGRpdj4NCjxwIGNsYXNzPSJNc29Ob3JtYWwiPiZuYnNwOyAmbmJzcDtpbnRlcm1lZGlhdGUgU3Vj
Y2VzcyBhbmQgRmFpbHVyZSBtZXNzYWdlcyBiZXR3ZWVuIG11bHRpcGxlJm5ic3A7PG86cD48L286
cD48L3A+DQo8L2Rpdj4NCjxkaXY+DQo8cCBjbGFzcz0iTXNvTm9ybWFsIj4mbmJzcDsgJm5ic3A7
aW5uZXIgRUFQIG1ldGhvZHMgd2l0aGluIEVBUC48bzpwPjwvbzpwPjwvcD4NCjxkaXY+DQo8cCBj
bGFzcz0iTXNvTm9ybWFsIj48bzpwPiZuYnNwOzwvbzpwPjwvcD4NCjwvZGl2Pg0KPGRpdj4NCjxw
IGNsYXNzPSJNc29Ob3JtYWwiPkl0IHNob3VsZCBzYXk6PG86cD48L286cD48L3A+DQo8L2Rpdj4N
CjxkaXY+DQo8cCBjbGFzcz0iTXNvTm9ybWFsIj48bzpwPiZuYnNwOzwvbzpwPjwvcD4NCjwvZGl2
Pg0KPGRpdj4NCjxwIGNsYXNzPSJNc29Ob3JtYWwiPiZuYnNwOyBUaGUgSW50ZXJtZWRpYXRlLVJl
c3VsdCBUTFYgcHJvdmlkZXMgc3VwcG9ydCBmb3IgYWNrbm93bGVkZ2VkJm5ic3A7PG86cD48L286
cD48L3A+DQo8L2Rpdj4NCjxkaXY+DQo8cCBjbGFzcz0iTXNvTm9ybWFsIj4mbmJzcDsgaW50ZXJt
ZWRpYXRlIFN1Y2Nlc3MgYW5kIEZhaWx1cmUgbWVzc2FnZXMgYWZ0ZXIgZWFjaCBpbm5lciBFQVAm
bmJzcDs8bzpwPjwvbzpwPjwvcD4NCjwvZGl2Pg0KPGRpdj4NCjxwIGNsYXNzPSJNc29Ob3JtYWwi
PiZuYnNwOyBhdXRoZW50aWNhdGlvbiBtZXRob2QuPG86cD48L286cD48L3A+DQo8L2Rpdj4NCjwv
ZGl2Pg0KPGRpdj4NCjxwIGNsYXNzPSJNc29Ob3JtYWwiPjxvOnA+Jm5ic3A7PC9vOnA+PC9wPg0K
PC9kaXY+DQo8ZGl2Pg0KPHAgY2xhc3M9Ik1zb05vcm1hbCI+U2VjdGlvbiA0LjIuMTMgc2F5czo8
bzpwPjwvbzpwPjwvcD4NCjwvZGl2Pg0KPGRpdj4NCjxwIGNsYXNzPSJNc29Ob3JtYWwiPjxvOnA+
Jm5ic3A7PC9vOnA+PC9wPg0KPC9kaXY+DQo8cCBjbGFzcz0iTXNvTm9ybWFsIj4mbmJzcDtJdCBN
VVNUIGJlIGluY2x1ZGVkIHdpdGggdGhlIEludGVybWVkaWF0ZS1SZXN1bHQgVExWIHRvIHBlcmZv
cm0mbmJzcDs8bzpwPjwvbzpwPjwvcD4NCjxkaXY+DQo8cCBjbGFzcz0iTXNvTm9ybWFsIj4mbmJz
cDtjcnlwdG9ncmFwaGljIGJpbmRpbmcgYWZ0ZXIgZWFjaCBzdWNjZXNzZnVsIEVBUCBtZXRob2Qg
aW4gYSZuYnNwOzxvOnA+PC9vOnA+PC9wPg0KPC9kaXY+DQo8ZGl2Pg0KPHAgY2xhc3M9Ik1zb05v
cm1hbCI+Jm5ic3A7c2VxdWVuY2Ugb2YgRUFQIG1ldGhvZHMsIGJlZm9yZSBwcm9jZWVkaW5nIHdp
dGggYW5vdGhlciBpbm5lciZuYnNwOzxvOnA+PC9vOnA+PC9wPg0KPC9kaXY+DQo8ZGl2Pg0KPHAg
Y2xhc3M9Ik1zb05vcm1hbCI+Jm5ic3A7RUFQIG1ldGhvZC48bzpwPjwvbzpwPjwvcD4NCjxkaXY+
DQo8cCBjbGFzcz0iTXNvTm9ybWFsIj48bzpwPiZuYnNwOzwvbzpwPjwvcD4NCjwvZGl2Pg0KPGRp
dj4NCjxwIGNsYXNzPSJNc29Ob3JtYWwiPkl0IHNob3VsZCBzYXk6PG86cD48L286cD48L3A+DQo8
L2Rpdj4NCjxkaXY+DQo8cCBjbGFzcz0iTXNvTm9ybWFsIj48bzpwPiZuYnNwOzwvbzpwPjwvcD4N
CjwvZGl2Pg0KPGRpdj4NCjxwIGNsYXNzPSJNc29Ob3JtYWwiPiZuYnNwO0l0IE1VU1QgYmUgaW5j
bHVkZWQgd2l0aCB0aGUgSW50ZXJtZWRpYXRlLVJlc3VsdCBUTFYgdG8gcGVyZm9ybTxvOnA+PC9v
OnA+PC9wPg0KPC9kaXY+DQo8ZGl2Pg0KPHAgY2xhc3M9Ik1zb05vcm1hbCI+Jm5ic3A7Y3J5cHRv
Z3JhcGhpYyBiaW5kaW5nIGFmdGVyIGVhY2ggc3VjY2Vzc2Z1bCBFQVAgYXV0aGVudGljYXRpb24m
bmJzcDs8bzpwPjwvbzpwPjwvcD4NCjwvZGl2Pg0KPGRpdj4NCjxwIGNsYXNzPSJNc29Ob3JtYWwi
PiZuYnNwO21ldGhvZCBpbiBhIHNlcXVlbmNlIG9mIEVBUCBtZXRob2RzLCBiZWZvcmUgcHJvY2Vl
ZGluZyB3aXRoJm5ic3A7PG86cD48L286cD48L3A+DQo8L2Rpdj4NCjxkaXY+DQo8cCBjbGFzcz0i
TXNvTm9ybWFsIj4mbmJzcDthbm90aGVyIGlubmVyIEVBUCBtZXRob2QuPG86cD48L286cD48L3A+
DQo8L2Rpdj4NCjwvZGl2Pg0KPGRpdj4NCjxwIGNsYXNzPSJNc29Ob3JtYWwiPjxvOnA+Jm5ic3A7
PC9vOnA+PC9wPg0KPC9kaXY+DQo8cCBjbGFzcz0iTXNvTm9ybWFsIj5Ob3Rlczo8YnI+DQo8YnI+
DQpURUFQIGRlc2NyaXB0aW9uIGlzIHNvbWV3aGF0IHZhZ3VlIGluIGRpc2N1c3Npb24gYWJvdXQg
JnF1b3Q7RUFQIG1ldGhvZHMmcXVvdDsgdnMuICZxdW90O0VBUCBhdXRoZW50aWNhdGlvbiBtZXRo
b2RzJnF1b3Q7IGFzIGl0IGNvbWVzIHRvIHRoZSBFQVAgbWV0aG9kcyBwZXJmb3JtZWQgaW4gUGhh
c2UgMiB3aXRoaW4gdGhlIFRMUyB0dW5uZWwuIFJGQyAzNzQ4IGRlZmluZXMgSWRlbnRpdHkgcmVx
dWVzdC9yZXNwb25zZSBhcyBhbiBFQVAgbWV0aG9kLiBIb3dldmVyLCB0aGlzIG1ldGhvZA0KIGlz
IG5vdCBhbiAmcXVvdDthdXRoZW50aWNhdGlvbiBtZXRob2QmcXVvdDsgd2hpY2ggaXMgYSBzcGVj
aWFsIGNhc2Ugb2YgYW4gbWV0aG9kIHdoZXJlIHRoZSBUeXBlIGlzIDQgb3IgZ3JlYXRlci48YnI+
DQo8YnI+DQpSRkMgNzE3MCB1c2VzIGNvcnJlY3QgdGVybWlub2xvZ3kgaW4gdGhlIGZpcnN0IHBh
cmFncmFwaCBvZiBTZWN0aW9uIDMuMy4xIHdoZW4gdGFsa2luZyBhYm91dCBtdWx0aXBsZSBhdXRo
ZW50aWNhdGlvbiBtZXRob2RzIG5vdCBiZWluZyBhbGxvd2VkIGJ5IFJGQyAzNzQ4IGluIGEgc2lu
Z2xlIEVBUCBjb252ZXJzYXRpb24uIEhvd2V2ZXIsIG1hbnksIGJ1dCBub3QgYWxsLCBvZiB0aGUg
Zm9sbG93aW5nICZxdW90O1tFQVBdIG1ldGhvZCZxdW90OyBpbnN0YW5jZXMgYXJlDQogYWN0dWFs
bHkgcmVmZXJyaW5nIHRvICZxdW90O1tFQVBdIGF1dGhlbnRpY2F0aW9uIG1ldGhvZCZxdW90Oy4g
VGhpcyByZXN1bHRzIGluIGluY29ycmVjdCBjbGFpbXMgb24gd2hlbiB0aGUgSW50ZXJtZWRpYXRl
LVJlc3VsdCBUTFYgYW5kIENyeXB0by1CaW5kaW5nIFRMViBhcmUgdXNlZC4gVGhleSBhcmUgbm90
IHVzZWQgYWZ0ZXIgYW4gRUFQIG5vbi1hdXRoZW50aWNhdGlvbiBtZXRob2QgbGlrZSBJZGVudGl0
eSAoZS5nLiwgc2VlIHRoZSBleGFtcGxlIGluIEMuMyk7DQogdGhleSBhcmUgdXNlZCBhZnRlciBl
YWNoIEVBUCBhdXRoZW50aWNhdGlvbiBtZXRob2QgbGlrZSBFQVAtcHdkLjxicj4NCjxicj4NCkZ1
cnRoZXJtb3JlLCB0aGUgY29tbWVudCBhYm91dCAmcXVvdDttb3JlIHRoYW4gb25lIG1ldGhvZCBp
cyBnb2luZyB0byBiZSBleGVjdXRlZCBpbiB0aGUgdHVubmVsJnF1b3Q7IGRvZXMgbm90IHNvdW5k
IGFjY3VyYXRlLiBUaGlzIGFwcGxpZXMgZXZlbiBpZiBvbmx5IGEgc2luZ2xlIEVBUCBhdXRoZW50
aWNhdGlvbiBtZXRob2QgaXMgZXhlY3V0ZWQgaW4gdGhlIHR1bm5lbCAoSWRlbnRpdHkgbWV0aG9k
IGlzIG5vdCByZXF1aXJlZCB0byBiZSBleGVjdXRlZCkuIFRoZQ0KIHByb3Bvc2VkIHRleHQgaW4g
dGhpcyBlcnJhdGEgZW50cnkgYWRkcmVzc2VzIHRoZXNlIHR3byBpc3N1ZXMgaW4gU2VjdGlvbiAz
LjMuMS4gVGhlIGZvbGxvd2luZyBhZGRpdGlvbmFsIGNoYW5nZXMgd291bGQgYmUgbmVlZGVkIHRv
IG1ha2UgcmVzdCBvZiB0aGUgc3BlY2lmaWNhdGlvbiB1c2UgdGhlIHRlcm1zIG1vcmUgYWNjdXJh
dGVseTo8YnI+DQo8YnI+DQozLjMuMzogJnF1b3Q7YWZ0ZXIgZWFjaCBzdWNjZXNzZnVsIEVBUCBt
ZXRob2QmcXVvdDsgLS0mZ3Q7ICZxdW90O2FmdGVyIGVhY2ggc3VjY2Vzc2Z1bCBFQVAgYXV0aGVu
dGljYXRpb24gbWV0aG9kJnF1b3Q7PGJyPg0KMy44LjM6ICZxdW90O2NvbXBsZXRpb24gb2YgdGhl
IEVBUCBtZXRob2QmcXVvdDsgLS0mZ3Q7ICZxdW90O2NvbXBsZXRpb24gb2YgdGhlIEVBUCBhdXRo
ZW50aWNhdGlvbiBtZXRob2QmcXVvdDs8YnI+DQo0LjIuMTE6ICZxdW90O2JldHdlZW4gbXVsdGlw
bGUgaW5uZXIgRUFQIG1ldGhvZHMgd2l0aGluIEVBUCZxdW90OyAtLSZndDsgJnF1b3Q7YWZ0ZXIg
ZWFjaCBpbm5lciBFQVAgYXV0aGVudGljYXRpb24gbWV0aG9kJnF1b3Q7PGJyPg0KNC4yLjEzOiAm
cXVvdDthZnRlciBlYWNoIHN1Y2Nlc3NmdWwgRUFQIG1ldGhvZCZxdW90OyAtLSZndDsgJnF1b3Q7
YWZ0ZXIgZWFjaCBzdWNjZXNzZnVsIEVBUCBhdXRoZW50aWNhdGlvbiBtZXRob2QmcXVvdDs8bzpw
PjwvbzpwPjwvcD4NCjwvZGl2Pg0KPC9ib2R5Pg0KPC9odG1sPg0K

--_000_CH2PR21MB1381F392AAF246CE1590A318D11D0CH2PR21MB1381namp_--


From nobody Thu Oct 22 00:35:22 2020
Return-Path: <Hannes.Tschofenig@arm.com>
X-Original-To: emu@ietfa.amsl.com
Delivered-To: emu@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 27F443A0E72 for <emu@ietfa.amsl.com>; Thu, 22 Oct 2020 00:35:21 -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, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, RCVD_IN_MSPIKE_H2=-0.001, SPF_PASS=-0.001, UNPARSEABLE_RELAY=0.001, URIBL_BLOCKED=0.001] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (1024-bit key) header.d=armh.onmicrosoft.com header.b=bU4Sf4jl; dkim=pass (1024-bit key) header.d=armh.onmicrosoft.com header.b=bU4Sf4jl
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 z9VKNmgQZdYJ for <emu@ietfa.amsl.com>; Thu, 22 Oct 2020 00:35:19 -0700 (PDT)
Received: from EUR05-AM6-obe.outbound.protection.outlook.com (mail-am6eur05on2046.outbound.protection.outlook.com [40.107.22.46]) (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 CEAD83A0D31 for <emu@ietf.org>; Thu, 22 Oct 2020 00:35:18 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=armh.onmicrosoft.com;  s=selector2-armh-onmicrosoft-com; h=From:Date:Subject:Message-ID:Content-Type:MIME-Version:X-MS-Exchange-SenderADCheck; bh=a3clolZI6MsqPjhUb4IrKNe4XrCUrDjBhFC/XyVLLQk=; b=bU4Sf4jl9OOxe3KF1fSVT8tsp7w8+a6LCYB8ZVJvmcJJd22rFWlAXi/FI7XYzlqONooDdgMmzsUKXurSaC5jRmr2/DI72kcrZwOMeDwpAd660llkiceNoYCszf793Ir23t9xTFH8saH1omg4cLRueng2j7/gDsKyWRtaFRF7+T4=
Received: from AM5PR0601CA0044.eurprd06.prod.outlook.com (2603:10a6:203:68::30) by DB8PR08MB5450.eurprd08.prod.outlook.com (2603:10a6:10:116::22) with Microsoft SMTP Server (version=TLS1_2, cipher=TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384) id 15.20.3477.20; Thu, 22 Oct 2020 07:35:11 +0000
Received: from VE1EUR03FT031.eop-EUR03.prod.protection.outlook.com (2603:10a6:203:68:cafe::6c) by AM5PR0601CA0044.outlook.office365.com (2603:10a6:203:68::30) with Microsoft SMTP Server (version=TLS1_2, cipher=TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384) id 15.20.3499.18 via Frontend Transport; Thu, 22 Oct 2020 07:35:10 +0000
X-MS-Exchange-Authentication-Results: spf=pass (sender IP is 63.35.35.123) smtp.mailfrom=arm.com; ietf.org; dkim=pass (signature was verified) header.d=armh.onmicrosoft.com;ietf.org; dmarc=pass action=none header.from=arm.com;
Received-SPF: Pass (protection.outlook.com: domain of arm.com designates 63.35.35.123 as permitted sender) receiver=protection.outlook.com; client-ip=63.35.35.123; helo=64aa7808-outbound-1.mta.getcheckrecipient.com;
Received: from 64aa7808-outbound-1.mta.getcheckrecipient.com (63.35.35.123) by VE1EUR03FT031.mail.protection.outlook.com (10.152.18.69) with Microsoft SMTP Server (version=TLS1_2, cipher=TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384) id 15.20.3499.18 via Frontend Transport; Thu, 22 Oct 2020 07:35:10 +0000
Received: ("Tessian outbound d5e343850048:v64"); Thu, 22 Oct 2020 07:35:10 +0000
X-CR-MTA-TID: 64aa7808
Received: from 493a1c788d58.1 by 64aa7808-outbound-1.mta.getcheckrecipient.com id 10B7C33B-427A-4CC5-83A4-DA9662B8C09B.1;  Thu, 22 Oct 2020 07:35:05 +0000
Received: from EUR03-AM5-obe.outbound.protection.outlook.com by 64aa7808-outbound-1.mta.getcheckrecipient.com with ESMTPS id 493a1c788d58.1 (version=TLSv1.2 cipher=ECDHE-RSA-AES256-GCM-SHA384); Thu, 22 Oct 2020 07:35:05 +0000
ARC-Seal: i=1; a=rsa-sha256; s=arcselector9901; d=microsoft.com; cv=none; b=c5ENdpjrg6S6lO24Lx5264UStUiVySmV8P41ctA2ZJDIsUnLbUn+TBABhQYCfWogiuMemos/ryrjwaDLDfV1Xhwu9IMidLc1Z7OcqgMob4/3DNqYpZEjm8AW2fan7992Gnmj6ONjZOEklUN5xAhuaELeCMQFqfut6vKKWxDMHMS4HQ+iBXCo55OkvoewJvC/vHTN85AplPp3qex3JpTmRMcwpxGHC76kzCr6afr33aKyYrRwtCC5fDa0zZ6SUg2y3c4fUx1MERK2KpVweHQm8dNqRb9F79zUcLLxE15xlXC2XKaGf8qPyDs3Mk1dCO6tTq+fmhEYElJSrXMIjhhCWg==
ARC-Message-Signature: i=1; a=rsa-sha256; c=relaxed/relaxed; d=microsoft.com;  s=arcselector9901; h=From:Date:Subject:Message-ID:Content-Type:MIME-Version:X-MS-Exchange-SenderADCheck; bh=a3clolZI6MsqPjhUb4IrKNe4XrCUrDjBhFC/XyVLLQk=; b=Kf6A05WnmKgIenrJcnGLuyZFNTYLdYKTlsq6YZN5X/h47onFy/1eGMuDCWdcaY4ULBP4Lshbs8Er6Mhzd8SWMUp2D/NMOX0M8p/iIPf+KAiP6qTFHniBuXlgwDxDzzNn0wgfrT1HWi7epeeRsLJefAGGYdQt9hPMLHS+Xwg3QXY0kWXeb/UhLNMbq9RqX8diZTdnRKikYoabx2ylPfaViUgbtxuod0rDTNeXfrc7AiRvFwv5eQLxHV6fR5K6HWZ5fp0SYOOxbOLalC4VFF+lpOXynwR4hJmxpO7bvhpPzQXghr1ZYI7Gs24rqkDPfNaWddo11GMng999FnXxQznytw==
ARC-Authentication-Results: i=1; mx.microsoft.com 1; spf=pass smtp.mailfrom=arm.com; dmarc=pass action=none header.from=arm.com; dkim=pass header.d=arm.com; arc=none
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=armh.onmicrosoft.com;  s=selector2-armh-onmicrosoft-com; h=From:Date:Subject:Message-ID:Content-Type:MIME-Version:X-MS-Exchange-SenderADCheck; bh=a3clolZI6MsqPjhUb4IrKNe4XrCUrDjBhFC/XyVLLQk=; b=bU4Sf4jl9OOxe3KF1fSVT8tsp7w8+a6LCYB8ZVJvmcJJd22rFWlAXi/FI7XYzlqONooDdgMmzsUKXurSaC5jRmr2/DI72kcrZwOMeDwpAd660llkiceNoYCszf793Ir23t9xTFH8saH1omg4cLRueng2j7/gDsKyWRtaFRF7+T4=
Received: from AM0PR08MB3716.eurprd08.prod.outlook.com (2603:10a6:208:106::13) by AM0PR08MB3026.eurprd08.prod.outlook.com (2603:10a6:208:65::21) with Microsoft SMTP Server (version=TLS1_2, cipher=TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384) id 15.20.3477.25; Thu, 22 Oct 2020 07:35:03 +0000
Received: from AM0PR08MB3716.eurprd08.prod.outlook.com ([fe80::900e:c64d:a006:4860]) by AM0PR08MB3716.eurprd08.prod.outlook.com ([fe80::900e:c64d:a006:4860%6]) with mapi id 15.20.3455.037; Thu, 22 Oct 2020 07:35:03 +0000
From: Hannes Tschofenig <Hannes.Tschofenig@arm.com>
To: Michael Richardson <mcr+ietf@sandelman.ca>, "emu@ietf.org" <emu@ietf.org>
Thread-Topic: [Emu] draft-ietf-emu-eap-tls13-11: OCSP Stapling
Thread-Index: AdaniLvyfaHHD0ANRluj1nshuTAidQAQOaGAAB3J2tA=
Date: Thu, 22 Oct 2020 07:35:03 +0000
Message-ID: <AM0PR08MB3716CCE7C843CAA50B86995DFA1D0@AM0PR08MB3716.eurprd08.prod.outlook.com>
References: <AM0PR08MB371647618F993B8C5BA6EB5FFA1C0@AM0PR08MB3716.eurprd08.prod.outlook.com> <15861.1603298751@localhost>
In-Reply-To: <15861.1603298751@localhost>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
x-ts-tracking-id: 67CDA6E4A452F6429AABFA13E918DAA0.0
x-checkrecipientchecked: true
Authentication-Results-Original: sandelman.ca; dkim=none (message not signed) header.d=none; sandelman.ca; dmarc=none action=none header.from=arm.com; 
x-originating-ip: [156.67.196.116]
x-ms-publictraffictype: Email
X-MS-Office365-Filtering-HT: Tenant
X-MS-Office365-Filtering-Correlation-Id: c8ce55d9-f547-4f03-ea85-08d8765d01cf
x-ms-traffictypediagnostic: AM0PR08MB3026:|DB8PR08MB5450:
X-Microsoft-Antispam-PRVS: <DB8PR08MB54506C66BBD6BC3ED83F72BEFA1D0@DB8PR08MB5450.eurprd08.prod.outlook.com>
x-checkrecipientrouted: true
nodisclaimer: true
x-ms-oob-tlc-oobclassifiers: OLM:9508;OLM:10000;
X-MS-Exchange-SenderADCheck: 1
X-Microsoft-Antispam-Untrusted: BCL:0;
X-Microsoft-Antispam-Message-Info-Original: gWmLFPzOqI2Oxs3RytAXAqJOcejr8+e1QGRymriAh9LjAeKMhTQY9L4jUx3Gf4XCmL3TgP1UJfHDx2294k2OLXFO3REwWm9AZ3SMHIYh2njjCXnEgfVuO8glxZw/AFKOVnzl+B6K24XtvzR/y0n9QOwMMqNfqFsJwfJtnvpwcEhpZj7ZjUUnlADHZLAZBAPNX5YxZihaYoIza2p2lz1nCXvgqpVu48UxzyNTDmMLz/kU+F7Cxk0dZL5smNu7l1gWFXV5qWmvo6iTweKwP8tGwb8S0kB0Fru15HnIKpC5ovODKZyGcB60+6kTwS2BZDT5HsXxNOx3Qhc8YQ8I0YfX+Q==
X-Forefront-Antispam-Report-Untrusted: CIP:255.255.255.255; CTRY:; LANG:en; SCL:1; SRV:; IPV:NLI; SFV:NSPM; H:AM0PR08MB3716.eurprd08.prod.outlook.com; PTR:; CAT:NONE; SFS:(4636009)(376002)(366004)(346002)(39860400002)(396003)(136003)(478600001)(66446008)(64756008)(83380400001)(55016002)(2906002)(71200400001)(52536014)(66556008)(76116006)(66946007)(66476007)(110136005)(5660300002)(33656002)(86362001)(186003)(26005)(9686003)(66574015)(6506007)(8676002)(53546011)(316002)(7696005)(8936002); DIR:OUT; SFP:1101; 
x-ms-exchange-antispam-messagedata: uboqciH55jHCLZ5G4nVKzPIHJ30KgtHOEMqLE4KMVe6/BGMOsBCRAjWiZLnCZvyXmx0Xu4BxKFACkuVWmqca85CVUGTD1G57b4DNlcY7Miqhu94iHEgYt1giBDd0BkULbUfAIO3YkNuDMjHM9H9v9IQDeqzaSR58dSU0FwtGvZJdqRi1yhPLZ4hEuVY5MdtkPyx64osHXo1VriIot9VWY2Mcqv9x16eBsRT/clPyU6c+X2XwcySOcr/9P/H46y0ohHIK7bgofy6j80fSmb5Q9/DfklXVfN1NFZMw83PkKmLhlviTtX2KObbPgVtwsa1pl9PTp/t2B736c09LT3mTRPjBx7+4VV3wMlSx3SvXqOMpkEh+q4sguO3EhX3mvkD580fZ3n7mDxrlmhusaaPwK0sRJ13jmvva4rpQ9jbjngnsmxLVfqEWQZVkPN8/nkln3koWiHYPM0/FRKJ/plRrDPKoJGBLmpUkqnkf5s+aqoF4KgwIN+A+7MX8HHs/xrh29X0lg6WGZ7LvgckzIpvcgSpx6I4zRnfXvO2nbnv/DejLISrMLAPVrBW7YyskVjR58U2Tt0fG7R5xYGvRD63xibjMDmonbPaRbR28oCROKGLadqCfNOG4hc7BlNUsUGd5LpEk/Y93kRKM0B8HffITpw==
x-ms-exchange-transport-forked: True
Content-Type: text/plain; charset="utf-8"
Content-Transfer-Encoding: base64
MIME-Version: 1.0
X-MS-Exchange-Transport-CrossTenantHeadersStamped: AM0PR08MB3026
Original-Authentication-Results: sandelman.ca; dkim=none (message not signed) header.d=none; sandelman.ca; dmarc=none action=none header.from=arm.com; 
X-EOPAttributedMessage: 0
X-MS-Exchange-Transport-CrossTenantHeadersStripped: VE1EUR03FT031.eop-EUR03.prod.protection.outlook.com
X-MS-Office365-Filtering-Correlation-Id-Prvs: 4bd0a5a2-0efa-4033-f9bd-08d8765cfda0
X-Microsoft-Antispam: BCL:0;
X-Microsoft-Antispam-Message-Info: rW2C1za9neoirlnT9S7HcCeahia3kt89q41FN+Z9J8IT8/VbWVzKpyKZQZKsvb641jiRIdB5pl9EQR3nEY0jT3G+s8xIeL/imqb9VlBebOvodqh6shd7muA7Jc4tp21LZw7AFUYrcKcL5gv69ygOM5T3Y7R85qXkVroeD+xVlpiBX2EC1rmVwbp1prm+rY5npMzUbP160jlX1pR/hgVYb5B7l1cG/xZdWkmYbX1GiuRxU32HdmOcMSuJcgUUzcAeRJl+6y+qxjj5h+BZ5Yk7b7OYm5UV/Stl4JfVLmedBIZih7wT6z7+o1Y2RulIRMuMnujjkI5pPhP/MIsvel4TXzG7JYjXBhTeT+3Mu4p+Xb6R9gPOZSPCOpV3Gxk3jYvKaLQt6C1mYdw85TU9uvpoWg==
X-Forefront-Antispam-Report: CIP:63.35.35.123; CTRY:IE; LANG:en; SCL:1; SRV:;  IPV:CAL; SFV:NSPM; H:64aa7808-outbound-1.mta.getcheckrecipient.com;  PTR:ec2-63-35-35-123.eu-west-1.compute.amazonaws.com; CAT:NONE; SFS:(4636009)(39860400002)(376002)(396003)(346002)(136003)(46966005)(8676002)(82310400003)(336012)(55016002)(9686003)(5660300002)(52536014)(66574015)(478600001)(83380400001)(356005)(36906005)(33656002)(8936002)(316002)(81166007)(6506007)(53546011)(86362001)(70206006)(70586007)(26005)(110136005)(2906002)(7696005)(47076004)(186003)(82740400003); DIR:OUT; SFP:1101; 
X-OriginatorOrg: arm.com
X-MS-Exchange-CrossTenant-OriginalArrivalTime: 22 Oct 2020 07:35:10.6235 (UTC)
X-MS-Exchange-CrossTenant-Network-Message-Id: c8ce55d9-f547-4f03-ea85-08d8765d01cf
X-MS-Exchange-CrossTenant-Id: f34e5979-57d9-4aaa-ad4d-b122a662184d
X-MS-Exchange-CrossTenant-OriginalAttributedTenantConnectingIp: TenantId=f34e5979-57d9-4aaa-ad4d-b122a662184d; Ip=[63.35.35.123];  Helo=[64aa7808-outbound-1.mta.getcheckrecipient.com]
X-MS-Exchange-CrossTenant-AuthSource: VE1EUR03FT031.eop-EUR03.prod.protection.outlook.com
X-MS-Exchange-CrossTenant-AuthAs: Anonymous
X-MS-Exchange-CrossTenant-FromEntityHeader: HybridOnPrem
X-MS-Exchange-Transport-CrossTenantHeadersStamped: DB8PR08MB5450
Archived-At: <https://mailarchive.ietf.org/arch/msg/emu/y0hbJUbPrG4ONUCTiuW75eaqtA8>
Subject: Re: [Emu] draft-ietf-emu-eap-tls13-11: OCSP Stapling
X-BeenThere: emu@ietf.org
X-Mailman-Version: 2.1.29
Precedence: list
List-Id: "EAP Methods Update \(EMU\)" <emu.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/emu>, <mailto:emu-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/emu/>
List-Post: <mailto:emu@ietf.org>
List-Help: <mailto:emu-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/emu>, <mailto:emu-request@ietf.org?subject=subscribe>
X-List-Received-Date: Thu, 22 Oct 2020 07:35:21 -0000

SGkgTWljaGFlbCwNCg0KVGhhbmtzIGZvciB0aGUgcXVlc3Rpb24uIEkgYW0gb2JqZWN0aW5nIHRv
IHRoZSBtYW5kYXRvcnkgdXNlIG9mIE9DU1AgZm9yIFRMUyAxLjMgaW4gRUFQLVRMUy4NCkkgYW0g
ZmluZSB3aXRoIGhhdmluZyBpdCBvcHRpb25hbC4NCg0KTWJlZCBUTFMgaXMgdXNlZCBpbiBpbXBs
ZW1lbnRhdGlvbnMgb2YgRUFQLVRMUyBhbmQgd2UgaGF2ZSByZWNlaXZlZCBsaXR0bGUgaW50ZXJl
c3QgaW4gT0NTUCBzdXBwb3J0LiBUaGUgaW50ZXJlc3QgaXMgc28gbG93IHRoYXQgdGhlIHByb3Bv
c2VkIGNvZGUgd2FzIG5ldmVyIG1lcmdlZC4NCg0KQ29tcGFuaWVzIHNlZW0gdG8gdXNlIGFuIGFs
dGVybmF0aXZlIGFwcHJvYWNoIGluc3RlYWQsIG5hbWVseSB0byBjaGFuZ2UgY2VydGlmaWNhdGVz
IHZpYSBhIGRldmljZSBtYW5hZ2VtZW50IHNvbHV0aW9uLiBBZnRlciBhbGwsIHlvdSB3aWxsIGhh
dmUgdG8gb2ZmZXIgYSBzb2x1dGlvbiBhbnl3YXkuIFlvdSBjYW5ub3QganVzdCByZWplY3QgYWNj
ZXNzIHRvIHlvdXIgYmFja2VuZCBhdXRoZW50aWNhdGlvbiBpbmZyYXN0cnVjdHVyZSBhbmQgZG8g
bm90aGluZy4NCg0KRG8gb3RoZXIgRUFQIG1ldGhvZHMgcmVseSBvbiBPQ1NQPw0KDQpDaWFvDQpI
YW5uZXMNCg0KLS0tLS1PcmlnaW5hbCBNZXNzYWdlLS0tLS0NCkZyb206IE1pY2hhZWwgUmljaGFy
ZHNvbiA8bWNyK2lldGZAc2FuZGVsbWFuLmNhPg0KU2VudDogV2VkbmVzZGF5LCBPY3RvYmVyIDIx
LCAyMDIwIDY6NDYgUE0NClRvOiBIYW5uZXMgVHNjaG9mZW5pZyA8SGFubmVzLlRzY2hvZmVuaWdA
YXJtLmNvbT47IGVtdUBpZXRmLm9yZw0KU3ViamVjdDogUmU6IFtFbXVdIGRyYWZ0LWlldGYtZW11
LWVhcC10bHMxMy0xMTogT0NTUCBTdGFwbGluZw0KDQoNCkhhbm5lcyBUc2Nob2ZlbmlnIDxIYW5u
ZXMuVHNjaG9mZW5pZ0Bhcm0uY29tPiB3cm90ZToNCiAgICA+IHRoaXMgZHJhZnQgbWFuZGF0ZXMg
T0NTQ1Agc3RhcGxpbmcgKGZvciB1c2Ugd2l0aCBUTFMgMS4zIGluIEVBUC1UTFMpDQogICAgPiBh
bmQgSSBiZWxpZXZlIHRoaXMgaXMgYSBwcm9ibGVtIGZvciBpbXBsZW1lbnRhdGlvbnMuIFRoaXMg
ZXh0cmEgYnVyZGVuDQogICAgPiBpcyBJTUhPIHVuanVzdGlmaWVkLiBGb3IgdGhlIHR5cGUgb2Yg
ZGVwbG95bWVudHMgd2hlcmUgRUFQIGlzIHVzZWQNCiAgICA+IHRoZXJlIGlzIG5vIG5lZWQgZm9y
IGEgbWFuZGF0b3J5IGNlcnRpZmljYXRlIHJldm9jYXRpb24gY2hlY2tpbmcgd2l0aA0KICAgID4g
T0NTUC4NCg0KSXMgaXQ6DQogICAxKSB0aGVyZSBpcyBubyBuZWVkIGZvciBtYW5kYXRvcnkgY2Vy
dGlmaWNhdGUgcmV2b2NhdGlvbiBjaGVja2luZw0KICAgMikgdGhlcmUgaXMgbm8gbmVlZCB0byBt
YWtlIE9DU1AgY2hlY2tpbmcgdGhlIG1hbmRhdG9yeSBtZXRob2QgZm9yIGNlcnRpZmljYXRlIHJl
dm9jYXRpb24gY2hlY2tpbmcNCg0KQXJlIHlvdSBvYmplY3RpbmcgdG86DQogICBhKSBtYW5kYXRv
cnkgY2VydGlmaWNhdGUgcmV2b2NhdGlvbiBjaGVja2luZw0KICAgYikgbWFuZGF0b3J5IE9DU1AN
CiAgIGMpIG1hbmRhdG9yeSBPQ1NQICpzdGFwbGluZyogd2hlbiB1c2luZyBPQ1NQDQoNCkkgdGhp
bmssIGlmIHlvdSB0aGUgY2xpZW50ICh3aG8gaGFzIG5vIEludGVybmV0IHlldCksIGlzIGdvaW5n
IHRvIGJlIGFibGUgdG8gZG8gY2VydGlmaWNhdGUgcmV2b2NhdGlvbiBjaGVja2luZywgdGhlbiBk
b2luZyBpdCB2aWEgT0NTUCBzdGFwbGluZyBpcyB0aGUgcmlnaHQgd2F5IHRvIGdvLiAgSXQgY2Fu
J3QgZG8gT05MSU5FIENTUCwgYmVjYXVzZSBpdCBoYXMgbm8gSW50ZXJuZXQuDQoNCiAgICA+IEhh
dmluZyBpdCBvcHRpb25hbCwgbGlrZSB0aGUgdXNlIG9mIG1hbnkgb3RoZXIgVExTIGV4dGVuc2lv
bnMsIGlzIGZpbmUNCiAgICA+IGZvciBtZS4gRldJVyBldmVuIFRMUyAxLjMsIHdoaWNoIGlzIHVz
ZWQgaW4gYSBtb3JlIGdlbmVyaWMgZW52aXJvbm1lbnQsDQogICAgPiBkb2VzIG5vdCBtYW5kYXRl
IHRoZSB1c2Ugb2YgT0NTUCBzdGFwbGluZy4NCg0KICAgID4gVGhpcyByZXF1aXJlbWVudCB3aWxs
IG1ha2UgdGhlIHByb2JsZW0gZGVzY3JpYmVkIGluDQogICAgPiBkcmFmdC1pZXRmLWVtdS1lYXB0
bHNjZXJ0IHdvcnNlLiBJIGFtIHN1cmUgdGhlIGF1dGhvcnMgYXJlIGF3YXJlIG9mDQogICAgPiB0
aGlzIGZhY3Qgc2luY2UgdGhleSBhcmUgYWxzbyBjby1hdXRob3JzIG9mIGRyYWZ0LWlldGYtZW11
LWVhcHRsc2NlcnQuDQoNCi0tDQpNaWNoYWVsIFJpY2hhcmRzb24gPG1jcitJRVRGQHNhbmRlbG1h
bi5jYT4gICAuIG8gTyAoIElQdjYgScO4VCBjb25zdWx0aW5nICkNCiAgICAgICAgICAgU2FuZGVs
bWFuIFNvZnR3YXJlIFdvcmtzIEluYywgT3R0YXdhIGFuZCBXb3JsZHdpZGUNCklNUE9SVEFOVCBO
T1RJQ0U6IFRoZSBjb250ZW50cyBvZiB0aGlzIGVtYWlsIGFuZCBhbnkgYXR0YWNobWVudHMgYXJl
IGNvbmZpZGVudGlhbCBhbmQgbWF5IGFsc28gYmUgcHJpdmlsZWdlZC4gSWYgeW91IGFyZSBub3Qg
dGhlIGludGVuZGVkIHJlY2lwaWVudCwgcGxlYXNlIG5vdGlmeSB0aGUgc2VuZGVyIGltbWVkaWF0
ZWx5IGFuZCBkbyBub3QgZGlzY2xvc2UgdGhlIGNvbnRlbnRzIHRvIGFueSBvdGhlciBwZXJzb24s
IHVzZSBpdCBmb3IgYW55IHB1cnBvc2UsIG9yIHN0b3JlIG9yIGNvcHkgdGhlIGluZm9ybWF0aW9u
IGluIGFueSBtZWRpdW0uIFRoYW5rIHlvdS4NCg==


From nobody Thu Oct 22 02:30:09 2020
Return-Path: <rieckers@uni-bremen.de>
X-Original-To: emu@ietfa.amsl.com
Delivered-To: emu@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 17BB93A03F3 for <emu@ietfa.amsl.com>; Thu, 22 Oct 2020 02:30:07 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.344
X-Spam-Level: 
X-Spam-Status: No, score=-2.344 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, DKIM_VALID_EF=-0.1, NICE_REPLY_A=-0.247, RCVD_IN_MSPIKE_H4=0.001, RCVD_IN_MSPIKE_WL=0.001, SPF_HELO_NONE=0.001, SPF_PASS=-0.001, URIBL_BLOCKED=0.001] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (2048-bit key) header.d=uni-bremen.de
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 JhbhlhFHQUIv for <emu@ietfa.amsl.com>; Thu, 22 Oct 2020 02:30:05 -0700 (PDT)
Received: from gabriel-vm-2.zfn.uni-bremen.de (gabriel-vm-2.zfn.uni-bremen.de [134.102.50.17]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id BD1AE3A03F2 for <emu@ietf.org>; Thu, 22 Oct 2020 02:30:04 -0700 (PDT)
Received: from [192.168.42.169] (eduroam-pool12-022.wlan.uni-bremen.de [134.102.152.22]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (No client certificate requested) by gabriel-vm-2.zfn.uni-bremen.de (Postfix) with ESMTPSA id 4CH2By5VzBzyvB for <emu@ietf.org>; Thu, 22 Oct 2020 11:30:02 +0200 (CEST)
DKIM-Signature: v=1; a=rsa-sha256; c=simple/simple; d=uni-bremen.de; s=2019; t=1603359002; bh=6hHoDAHeJxGjpqkXt7HiLpl/8JLwlqR/9UrOSWB6Pqs=; h=To:References:From:Date:In-Reply-To; b=dZ+4Gdn0fUgxEAsHkkAx+q+nrdfCz7tW49fH3hnmMt93tWji0rj/lgh/tBwkGjGhe GsCgIkQWq1JfJ5rbIvi2UQ9miX/NhAeIst2TOtg2zfzuXe8AidIevXGoyZQSdPTI4r 8LEx+8c2OE/cSFV4fw8pm0X3cOZMdLqdFCcnrl9lBI+quu9tXt2AOQK9eXpgvMAOkF GG6PlIciWsm9AlSidudlS5b+lOUDyd85DlBgligJfNdK/tjcz4XUvn4lL5bcPbUSN+ lYMZ26mVpEJ59NagFGfAub1bH6yQudEqlSYKQ++SbAEeHXLxDtY2uFrE7CnnEA+fhD ngMoLKK6V+Gqg==
To: emu@ietf.org
References: <AM0PR08MB371647618F993B8C5BA6EB5FFA1C0@AM0PR08MB3716.eurprd08.prod.outlook.com> <15861.1603298751@localhost> <AM0PR08MB3716CCE7C843CAA50B86995DFA1D0@AM0PR08MB3716.eurprd08.prod.outlook.com>
From: Jan-Frederik Rieckers <rieckers@uni-bremen.de>
Message-ID: <f10343b3-0c03-2de1-827b-1b645eac699c@uni-bremen.de>
Date: Thu, 22 Oct 2020 11:29:58 +0200
User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:68.0) Gecko/20100101 Thunderbird/68.12.0
MIME-Version: 1.0
In-Reply-To: <AM0PR08MB3716CCE7C843CAA50B86995DFA1D0@AM0PR08MB3716.eurprd08.prod.outlook.com>
Content-Type: multipart/signed; micalg=pgp-sha256; protocol="application/pgp-signature"; boundary="PERK89A4NSZfT2kLc9SPkQzKsKNGbPd6j"
Archived-At: <https://mailarchive.ietf.org/arch/msg/emu/X9Mm24LSzaq63bHSvmkBbiSsrJc>
Subject: Re: [Emu] draft-ietf-emu-eap-tls13-11: OCSP Stapling
X-BeenThere: emu@ietf.org
X-Mailman-Version: 2.1.29
Precedence: list
List-Id: "EAP Methods Update \(EMU\)" <emu.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/emu>, <mailto:emu-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/emu/>
List-Post: <mailto:emu@ietf.org>
List-Help: <mailto:emu-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/emu>, <mailto:emu-request@ietf.org?subject=subscribe>
X-List-Received-Date: Thu, 22 Oct 2020 09:30:07 -0000

This is an OpenPGP/MIME signed message (RFC 4880 and 3156)
--PERK89A4NSZfT2kLc9SPkQzKsKNGbPd6j
Content-Type: multipart/mixed; boundary="ZjWQxei30gaNdksiB2bCb7Ot3RSd0U0mh";
 protected-headers="v1"
From: Jan-Frederik Rieckers <rieckers@uni-bremen.de>
To: emu@ietf.org
Message-ID: <f10343b3-0c03-2de1-827b-1b645eac699c@uni-bremen.de>
Subject: Re: [Emu] draft-ietf-emu-eap-tls13-11: OCSP Stapling
References: <AM0PR08MB371647618F993B8C5BA6EB5FFA1C0@AM0PR08MB3716.eurprd08.prod.outlook.com>
 <15861.1603298751@localhost>
 <AM0PR08MB3716CCE7C843CAA50B86995DFA1D0@AM0PR08MB3716.eurprd08.prod.outlook.com>
In-Reply-To: <AM0PR08MB3716CCE7C843CAA50B86995DFA1D0@AM0PR08MB3716.eurprd08.prod.outlook.com>

--ZjWQxei30gaNdksiB2bCb7Ot3RSd0U0mh
Content-Type: text/plain; charset=utf-8
Content-Language: en-US
Content-Transfer-Encoding: quoted-printable

Hi to all,

as an operator of a EAP-TLS server for eduroam at the University Bremen
I just want to give some of my thoughts here, feel free to read or
ignore them ;)

The eduroam environment is heavily used for BYOD, so we don't have any
opportunity to change certificates via a Device Management.
Our clients are researchers, employees, students, ... so we can't (and
won't) control all devices logging in to our network.
We have to use either a private CA (which brings its own problems) or we
use a public trust anchor (e.g. T-Telesec with the DFN-Intermediate for
most German universities).
The deployment is done either manually by the users or with help of
tools like eduroam CAT (cat.eduroam.org).

I have done some research regarding the revocation of certificates in
EAP-TLS and have come to the conclusion that, if a private key gets
compromised, we have no possibility to effectively revoke the
certificate in a way the clients would notice.

This is the result of different problems:

* Clients don't support OCSP Stapling
The only client platform with default OCSP Stapling enabled in the
Client Hello (that I'm aware of) is currently Apple devices.

* Servers don't support OCSP Stapling
FreeRADIUS 3.0 does not support OCSP Stapling (but FreeRADIUS 4.0 will
have support for it)
This is probably the software mostly used for eduroam.

* Clients don't support the MustStaple Certificate extension
I don't have enough knowledge about TLSv1.3 yet, but for <=3DTLSv1.2 OCSP=

won't add much security, since the OCSP Stapling is not mandatory.
I will look into TLSv1.3 and MustStaple in near future, maybe someone
can give me a hint if MustStaple is also active for TLSv1.3?

All in all, I definitely think that making OCSP Stapling optional will
have a benefit on small devices, but especially for the diverse
environment of eduroam, making OCSP Stapling mandatory will increase the
overall security of this federation.
Maybe it might be a good idea to make OCSP Stapling mandatory for
EAP-TLS Servers?

Greetings
Janfred


--ZjWQxei30gaNdksiB2bCb7Ot3RSd0U0mh--

--PERK89A4NSZfT2kLc9SPkQzKsKNGbPd6j
Content-Type: application/pgp-signature; name="signature.asc"
Content-Description: OpenPGP digital signature
Content-Disposition: attachment; filename="signature.asc"

-----BEGIN PGP SIGNATURE-----

iQIzBAEBCAAdFiEEO9n8U/6Yuq3qYHN1UHR7NOiKGm0FAl+RURoACgkQUHR7NOiK
Gm36og/+MUS2YCEvMo0Z2NLqVehDtEM6l3EmNo+B60uuo7abnK3n6ZBOiOd3VDQ1
y/isx/pqFQvQ2/RUa+YP93UU9I/jEzD+6gdE+tgq+7oU0HlGdEtfeMEjYITbLVuC
uhR7ah9hby7HjCAwquVOlfA60jcWNAXi1RrM4TVFcP7Ubhd0wSqR0nLlu9dM4iHL
tzUxtJNWUQdzbrfOk30Leh3np0eelCJ8F6egM/azK6SkZcbDTwOJ+iwEqVeBMiLv
232s87eZo+KQjuowLPCurnx8GjrGVCjcaZkhXgejQfCpIb9rqeqyetvN5RqyHp8h
Du0eXemkF4jcqlIhqfs+MIoQh36ENkK806TNMUN61sZzVMWZoEPGUL0zdOJq6hJ7
Zw44J0WuyqHoF19S+DFy/BJ0oK+HHKRj1rtARo8aJx68GNODHJdlepWNoGJLT+Qs
Fsd+hHiaTE/8WlXfMTe8Kk6tKvPy7GY8xxyllX+2wuDfxS68C8oFi6mYMEllOhTs
3Ay/91xs0hEfXgEdNG+S41JtXrqcH8RQ2DJHIndBFOT5SYZNGySt61fda1SiYto1
lXiHOxeIo2H9XRlmYEfKt3ELVeFl1/6SRLN8xxZ2TVxs5/MZokXGAUmJI0FV4z+a
k7mqmMfgIrnfis1/ZPj5NBgGgq1TlMqHFyQZPqkqpaZg4Gh1FD0=
=sHTC
-----END PGP SIGNATURE-----

--PERK89A4NSZfT2kLc9SPkQzKsKNGbPd6j--


From nobody Thu Oct 22 06:59:35 2020
Return-Path: <oleg.pekar.2017@gmail.com>
X-Original-To: emu@ietfa.amsl.com
Delivered-To: emu@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 603CB3A0C9E for <emu@ietfa.amsl.com>; Thu, 22 Oct 2020 06:59:32 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.747
X-Spam-Level: 
X-Spam-Status: No, score=-1.747 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, DKIM_VALID_EF=-0.1, FREEMAIL_ENVFROM_END_DIGIT=0.25, FREEMAIL_FROM=0.001, HTML_MESSAGE=0.001, HTTPS_HTTP_MISMATCH=0.1, SPF_HELO_NONE=0.001, SPF_PASS=-0.001, URIBL_BLOCKED=0.001] autolearn=no autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (2048-bit key) header.d=gmail.com
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 VZqCuu2S3LXU for <emu@ietfa.amsl.com>; Thu, 22 Oct 2020 06:59:30 -0700 (PDT)
Received: from mail-oo1-xc32.google.com (mail-oo1-xc32.google.com [IPv6:2607:f8b0:4864:20::c32]) (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 3282F3A0C5F for <emu@ietf.org>; Thu, 22 Oct 2020 06:59:30 -0700 (PDT)
Received: by mail-oo1-xc32.google.com with SMTP id v123so374482ooa.5 for <emu@ietf.org>; Thu, 22 Oct 2020 06:59:30 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20161025;  h=mime-version:references:in-reply-to:from:date:message-id:subject:to :cc; bh=C3YB8nc9ThWwEsEqLYDVZRr4VN/EvVOyoTcpSeKXAuU=; b=VsdjUoLwD8qpC5i4PLV1yzkZgkanFIFsuvKoRkZnGcb3tKOhiN07TACzjR0A2Jgulp AiFVy2z9pm4P5SsMk5tfu9wpbwXvPtt060zsD1laVdheuEqkSWwz9dZNE+XwoepuJGdO IUIAZ8tvZPmW3cbGB+0fCYhj+ynpqYdaxq9CpnOzmZ4l4zJBuBezjwGZb3ulTPiqDhMt Ghbs4sBYoZjxDiAKm83R8E/A0D0GxRyXVyeYysA9ta0AM7aK1RnVR/rZKtfpDixyAFLN jBczxiAkmGoGkTbs3fZAjGAOG710KFa/rk646Cm2wE0zooyQZE8n0yTKCsTzmtNJ7nK+ 7N1g==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:mime-version:references:in-reply-to:from:date :message-id:subject:to:cc; bh=C3YB8nc9ThWwEsEqLYDVZRr4VN/EvVOyoTcpSeKXAuU=; b=KoKlOZfmNiS+wfqErXr+HxgiBCUiK3Tjea30D/3o//8gDUt7fSKWdCMdNlJkYL36Rg InjGPfHgYeDHazqCC1gAkoGnGJS8cb/MljJtCaMODd1HsixQF4ipdDIBwx+xkk1Cv48j 4kkc22ycj2lWvQ2qgdTFDWEk8nowUJLFRHRqciIh2OyZYkMk7PZd8XfLnU14gxYfZDFD Jklb4lHd8iqgLzFMqiMZ1TiRKqp658CTMC39vbtXRVpPFVPjv4jZavbE/nyVqRJ+HdOW 5nHXoLtJpr7ci0/MBIeVupvNxntQrzjg/SR5byr2ybzcZ7f/HptWBHwEPJ2xFFqhGtv9 TPHg==
X-Gm-Message-State: AOAM532vGTVhBoO84PJ3UfJnNqDiTEXmbHSA9eNmMQef5F1Lb2+YPuTk 2+o42JvlBVqJVaIHKD2ExLd9S4OyJimla0qn8cAnp9kfeJ0ICg==
X-Google-Smtp-Source: ABdhPJx+defJeKLENTJPZMcogx/QXnUUxYmsBVlCgeR+NdJbx2OPiUQy5G6DTyj96Y43z4l1kj6oH8Qpkg783SjQafw=
X-Received: by 2002:a4a:4981:: with SMTP id z123mr2034663ooa.91.1603375169424;  Thu, 22 Oct 2020 06:59:29 -0700 (PDT)
MIME-Version: 1.0
References: <CAOgPGoBay+GG=F8WV0gLOOwLtGdGALGw_cM2JoAnXOtmGq7A+w@mail.gmail.com> <CH2PR21MB138143E929DAFE3C893D8144D11C0@CH2PR21MB1381.namprd21.prod.outlook.com> <CAOgPGoAtcm+Br+YkCyTtg5nJjqO7LGSo77b+CD4+Ba05azafew@mail.gmail.com> <CH2PR21MB13815BCEDC846D7C440AD564D11C0@CH2PR21MB1381.namprd21.prod.outlook.com> <CAOgPGoDTC-qiHOXFTJd7aMn2To7ySzBcx+iQMB9m5foC1bFxzw@mail.gmail.com>
In-Reply-To: <CAOgPGoDTC-qiHOXFTJd7aMn2To7ySzBcx+iQMB9m5foC1bFxzw@mail.gmail.com>
From: Oleg Pekar <oleg.pekar.2017@gmail.com>
Date: Thu, 22 Oct 2020 16:59:18 +0300
Message-ID: <CABXxEz8SRvMXdMR8_cPfvWdauJZwCjnd=7ytnVZ+_L-sB48wvw@mail.gmail.com>
To: Joseph Salowey <joe@salowey.net>
Cc: EMU WG <emu@ietf.org>, Jorge Vergara <jovergar=40microsoft.com@dmarc.ietf.org>,  Jouni Malinen <j@w1.fi>
Content-Type: multipart/alternative; boundary="0000000000006a4f8505b242df5f"
Archived-At: <https://mailarchive.ietf.org/arch/msg/emu/00P6PTcCrQ6chHCUu6jJ489HDZ8>
Subject: Re: [Emu] Proposed resolution for TEAP errata for 5128
X-BeenThere: emu@ietf.org
X-Mailman-Version: 2.1.29
Precedence: list
List-Id: "EAP Methods Update \(EMU\)" <emu.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/emu>, <mailto:emu-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/emu/>
List-Post: <mailto:emu@ietf.org>
List-Help: <mailto:emu-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/emu>, <mailto:emu-request@ietf.org?subject=subscribe>
X-List-Received-Date: Thu, 22 Oct 2020 13:59:32 -0000

--0000000000006a4f8505b242df5f
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable

Hi all,
Speaking about both errata 5127 and 5128, I think we need to align all key
derivation calls in TEAP RFC with the same rule/format to make the RFC
easier to understand. This can be achieved by introducing a unified single
PRF function that will be called from all the relevant RFC locations. For
me it sounds better than if we align just part of KDF calls with RFC 5295
(where the output length is included into seed). Also: in some KDF calls we
do have optional data and in some no. This could be also unified.

So I would suggest introducing:
TEAP-PRF (secret, key label, optional data, length) =3D TLS-PRF(secret, key
label | 0x00 | optional data, length)
where a single byte 0x00 is used for no optional data, length is a 2-octet
unsigned integer in network byte order.

Then:
IMSK =3D First 32 octets of TEAP-PRF(EMSK, "TEAPbindkey@ietf.org", 64) =3D
TLS-PRF(EMSK, "TEAPbindkey@ietf.org" | 0x00 | 0x00 | 0x00 | 0x40)
IMCK[j] =3D TEAP-PRF(S-IMCK[j-1], "Inner Methods Compound Keys", IMSK[j], 6=
0)
=3D TLS-PRF(S-IMCK[j-1], "Inner Methods Compound Keys" | 0x00 | IMSK[j] |
0x00 | 0x3C)
MSK =3D TEAP-PRF(S-IMCK[j], "Session Key Generating Function=E2=80=9D, 64) =
=3D
TLS-PRF(S-IMCK[j], "Session Key Generating Function" | 0x00 | 0x00 | 0x00 |
0x40)
EMSK =3D TEAP-PRF(S-IMCK[j], =E2=80=9DExtended Session Key Generating Funct=
ion=E2=80=9D, 64)
=3D TLS-PRF(S-IMCK[j], "Extended Session Key Generating Function" | 0x00 |
0x00 | 0x00 | 0x40)

This may change the existing implementation but will make it more clear -
need to create and call just one KDF function.

We can remove 0x00 that comes after the key label - while it is required
by RFC 5295. But there the key label is also ASCII printable string. Joe,
do you remember what was the motivation to put 0x00 after the key label
parameter?

Oleg


On Thu, Oct 22, 2020 at 2:54 AM Joseph Salowey <joe@salowey.net> wrote:

> (I accidentally dropped this list from the conversation)
>
> On Wed, Oct 21, 2020 at 4:48 PM Jorge Vergara <jovergar@microsoft.com>
> wrote:
>
>> >[Joe] Yes this is a concern and I think your interpretation of the
>> current document is also valid.  There may be more than one
>> implementation.  So what you implemented was:
>>
>> >
>>
>> >IMCK[j] =3D TLS-PRF(S-IMCK[j-1], "Inner Methods Compound Keys", IMSK[j]=
)
>> =3D P_<hash>(S-IMCK[j-1], "Inner Methods Compound Keys" | IMSK[j])
>>
>>
>>
>> Yes, this is what I implemented. As you mentioned, there are multiple
>> possible interpretations of this since the TEAP usage is incorrect.
>> However, my implementation does interop with at least 2 large vendor
>> implementations. If the implementations were using different calculation=
s
>> here, the Wi-Fi/Ethernet connections that depend on the MSK would fail. =
But
>> since connections work, I can assume we are all using the same
>> implementation and arriving at the same MSK. Cisco is one of the
>> implementations that I have tested against which is why I was hoping Ole=
g
>> may offer more context as to what he has seen.
>>
>>
>>
> [Joe] I can hope Jouni can chime in on this as well.  I think the origina=
l
> intent was to not include the length as is your suggestion.
>
>
>
>> >[Joe] Does the revision in 5167 match you implementation ( I don't
>> think Jouni's comment changes the underly calculation, just its
>> representation)?
>>
>>
>>
>> I have not implemented this portion of the RFC as I found it too unclear
>> to work with. Thus I can=E2=80=99t comment on what implementations may b=
e doing.
>> However, I agree with the current revision in 5167 as the most natural
>> interpretation. If others have implemented this portion of the RFC then
>> certainly their comments would be welcome.
>>
>>
>> By the way, we=E2=80=99ve dropped the EMU group on our replies here =E2=
=80=93 not sure if
>> intentional or not.
>>
>>
>>
>> Jorge Vergara
>>
>>
>>
>> *From:* Joseph Salowey <joe@salowey.net>
>> *Sent:* Wednesday, October 21, 2020 4:36 PM
>> *To:* Jorge Vergara <jovergar@microsoft.com>
>> *Subject:* Re: Proposed resolution for TEAP errata for 5128
>>
>>
>>
>>
>>
>>
>>
>> On Wed, Oct 21, 2020 at 3:20 PM Jorge Vergara <jovergar@microsoft.com>
>> wrote:
>>
>> In theory I agree this is a possible resolution. However, this doesn=E2=
=80=99t
>> match any of the current TEAP implementations that I am aware of. Perhap=
s
>> Oleg can weigh in as well in terms of what he=E2=80=99s seen.
>>
>>
>>
>> I believe all current implementations treat 60 as the desired output
>> length without treating as a seed. In terms of P_<hash>, this means
>> implementations are performing the calculation without a seed.
>>
>>
>>
>> RFC 5246 defines the TLS 1.2 PRF as:
>>
>> PRF(secret, label, seed) =3D P_<hash>(secret, label + seed)
>>
>>
>>
>> So the calculation implementations are currently performing with an empt=
y
>> seed ends up as:
>>
>> P_<hash>(secret, label)
>>
>>
>>
>> Note that in RFC 5295, the length *is* explicitly mentioned as being
>> concatenated with the label
>>
>> USRK =3D KDF(EMSK, key label | "\0" | optional data | length)
>>
>>
>>
>> RFC 5295 is mentioned earlier in the TEAP RFC, in the section covered by
>> errata 5127. *However* it is not mentioned in this portion of the RFC.
>> Since this calculation is not on an EMSK, I do not believe RFC 2395 appl=
ies
>> and this is likely why implementations went with the seedless
>> P_<hash>(secret, label) calculation instead.
>>
>>
>>
>> Is there concern about updating the RFC in a way that breaks existing
>> implementations?
>>
>>
>>
>> [Joe] Yes this is a concern and I think your interpretation of the
>> current document is also valid.  There may be more than one
>> implementation.  So what you implemented was:
>>
>>
>>
>> IMCK[j] =3D TLS-PRF(S-IMCK[j-1], "Inner Methods Compound Keys", IMSK[j])=
 =3D
>> P_<hash>(S-IMCK[j-1], "Inner Methods Compound Keys" | IMSK[j])
>>
>>
>>
>> taken out to 60 bytes.  The problem is that the TEAP spec references a
>> TLS-PRF in a way that it does not define.  I think the errata points out
>> the definition that should be used:
>>
>>
>>
>> PRF(secret, label, seed) =3D P_<hash>(secret, label + seed)
>>
>>
>>
>> That does not include length so the 60 in the original definition is
>> ambiguous.   The new text would then be something like:
>>
>>
>>
>> IMCK[j] =3D TLS-PRF(S-IMCK[j-1], "Inner Methods Compound Keys", IMSK[j])
>> to generate a length of 60 bytes
>>
>>
>>
>> Does the revision in 5167 match you implementation ( I don't think
>> Jouni's comment changes the underly calculation, just its representation=
)?
>>
>>
>>
>>
>>
>>
>>
>>
>>
>>
>>
>> Jorge Vergara
>>
>>
>>
>> *From:* Joseph Salowey <joe@salowey.net>
>> *Sent:* Wednesday, October 21, 2020 2:34 PM
>> *To:* EMU WG <emu@ietf.org>; Jouni Malinen <j@w1.fi>; Jorge Vergara <
>> jovergar@microsoft.com>; Oleg Pekar (olpekar) <olpekar@cisco.com>
>> *Subject:* Proposed resolution for TEAP errata for 5128
>>
>>
>>
>> Errata 5128: https://www.rfc-editor.org/errata/eid5128
>> <https://nam06.safelinks.protection.outlook.com/?url=3Dhttps%3A%2F%2Fwww=
.rfc-editor.org%2Ferrata%2Feid5128&data=3D04%7C01%7Cjovergar%40microsoft.co=
m%7C38c27add2cb64a06310108d8761a22d3%7C72f988bf86f141af91ab2d7cd011db47%7C1=
%7C0%7C637389201909062787%7CUnknown%7CTWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQI=
joiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D%7C1000&sdata=3DXudZt9FPh4jOBFQj01=
SQysnhX4p7G%2BflW2Pn2yIaJRM%3D&reserved=3D0>
>>
>> Proposed State: Verified
>>
>> Revision:
>>
>>
>>
>> Section 5.2. says
>>
>>
>> IMCK[j] =3D TLS-PRF(S-IMCK[j-1], "Inner Methods Compound Keys",
>>                 IMSK[j], 60)
>>
>> It should say:
>>
>> IMCK[j] =3D TLS-PRF(S-IMCK[j-1], "Inner Methods Compound Keys", IMSK[j] =
|
>> 60)
>>
>> Note:
>>
>> According to
>>
>> RFC5246 The Transport Layer Security (TLS) Protocol Version 1.2
>>
>> 5. HMAC and the Pseudorandom Function
>>
>> "TLS's PRF is created by applying P_hash to the secret as:
>>
>> PRF(secret, label, seed) =3D P_<hash>(secret, label + seed)"
>>
>>
>>
>> In terms of P_<hash> this would look like the following with the length
>> represented as a 2 byte value in network byte order:
>>
>>
>>
>> IMCK[j] =3D P_<hash>(S-IMCK[j-1], "Inner Methods Compound Keys" | IMSK[j=
]
>> | 0x00 | 0x3C)
>>
>>
>>
>>
>>
>>

--0000000000006a4f8505b242df5f
Content-Type: text/html; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable

<div dir=3D"ltr"><div>Hi all,</div><div>Speaking about both errata 5127 and=
 5128, I think we need to align all key derivation calls in TEAP RFC with t=
he same rule/format to make the RFC easier to understand. This can be achie=
ved by introducing a unified single PRF function that will be called from a=
ll the relevant RFC locations. For me it sounds better than if we align jus=
t part of KDF calls with RFC 5295 (where the output length is included into=
 seed). Also: in some KDF calls we do have optional data and in some no. Th=
is could be also unified.=C2=A0</div><div><br></div><div>So I would suggest=
 introducing:</div><div>TEAP-PRF (secret, key label, optional data, length)=
 =3D TLS-PRF(secret, key label | 0x00 | optional data, length)<br></div><di=
v>where a single byte 0x00 is used for no optional data, length is a 2-octe=
t unsigned integer in network byte order.<br></div><div><br></div><div>Then=
:</div><div>IMSK =3D First 32 octets of TEAP-PRF(EMSK, &quot;<a href=3D"mai=
lto:TEAPbindkey@ietf.org">TEAPbindkey@ietf.org</a>&quot;, 64) =3D TLS-PRF(E=
MSK, &quot;<a href=3D"mailto:TEAPbindkey@ietf.org">TEAPbindkey@ietf.org</a>=
&quot; | 0x00 | 0x00 | 0x00 | 0x40)<br>IMCK[j] =3D TEAP-PRF(S-IMCK[j-1], &q=
uot;Inner Methods Compound Keys&quot;, IMSK[j], 60) =3D TLS-PRF(S-IMCK[j-1]=
, &quot;Inner Methods Compound Keys&quot; | 0x00 | IMSK[j] | 0x00 | 0x3C)<b=
r>MSK =3D TEAP-PRF(S-IMCK[j], &quot;Session Key Generating Function=E2=80=
=9D, 64) =3D TLS-PRF(S-IMCK[j], &quot;Session Key Generating Function&quot;=
 | 0x00 | 0x00 | 0x00 | 0x40)<br>EMSK =3D TEAP-PRF(S-IMCK[j], =E2=80=9DExte=
nded Session Key Generating Function=E2=80=9D, 64) =3D TLS-PRF(S-IMCK[j], &=
quot;Extended Session Key Generating Function&quot; | 0x00 | 0x00 | 0x00 | =
0x40)<br></div><div><br></div><div>This may change the existing implementat=
ion but will make it more clear - need to create and call just one KDF func=
tion.</div><div><br></div><div>We can remove=C2=A00x00 that comes after the=
 key label - while it is required by=C2=A0RFC 5295. But there=C2=A0the key =
label is also ASCII printable string. Joe, do you remember what was the mot=
ivation to put 0x00 after the key label parameter?</div><div><br></div><div=
>Oleg</div><div><br></div><div><br></div><div class=3D"gmail_quote"><div di=
r=3D"ltr" class=3D"gmail_attr">On Thu, Oct 22, 2020 at 2:54 AM Joseph Salow=
ey &lt;<a href=3D"mailto:joe@salowey.net">joe@salowey.net</a>&gt; wrote:<br=
></div><blockquote class=3D"gmail_quote" style=3D"margin:0px 0px 0px 0.8ex;=
border-left:1px solid rgb(204,204,204);padding-left:1ex"><div dir=3D"ltr"><=
div>(I accidentally=C2=A0dropped this list from the conversation)</div><br>=
<div class=3D"gmail_quote"><div dir=3D"ltr" class=3D"gmail_attr">On Wed, Oc=
t 21, 2020 at 4:48 PM Jorge Vergara &lt;<a href=3D"mailto:jovergar@microsof=
t.com" target=3D"_blank">jovergar@microsoft.com</a>&gt; wrote:<br></div><bl=
ockquote class=3D"gmail_quote" style=3D"margin:0px 0px 0px 0.8ex;border-lef=
t:1px solid rgb(204,204,204);padding-left:1ex">





<div lang=3D"EN-US">
<div>
<p class=3D"MsoNormal">&gt;[Joe] Yes this is a concern and I think your=C2=
=A0interpretation of the current document is also valid.=C2=A0 There may be=
 more than one implementation.=C2=A0 So what you implemented was:<u></u><u>=
</u></p>
<p class=3D"MsoNormal">&gt;<u></u>=C2=A0<u></u></p>
<p class=3D"MsoNormal">&gt;IMCK[j] =3D TLS-PRF(S-IMCK[j-1], &quot;Inner Met=
hods Compound Keys&quot;,=C2=A0<span style=3D"font-size:10.5pt;color:rgb(44=
,67,83)">IMSK[j]) =3D P_&lt;hash&gt;(S-IMCK[j-1], &quot;Inner Methods Compo=
und Keys&quot; | IMSK[j])</span><u></u><u></u></p>
<p class=3D"MsoNormal"><u></u>=C2=A0<u></u></p>
<p class=3D"MsoNormal">Yes, this is what I implemented. As you mentioned, t=
here are multiple possible interpretations of this since the TEAP usage is =
incorrect. However, my implementation does interop with at least 2 large ve=
ndor implementations. If the implementations
 were using different calculations here, the Wi-Fi/Ethernet connections tha=
t depend on the MSK would fail. But since connections work, I can assume we=
 are all using the same implementation and arriving at the same MSK. Cisco =
is one of the implementations that
 I have tested against which is why I was hoping Oleg may offer more contex=
t as to what he has seen.<u></u><u></u></p>
<p class=3D"MsoNormal"><u></u>=C2=A0</p></div></div></blockquote><div>[Joe]=
 I can hope Jouni can chime in on this as well.=C2=A0 I think the original =
intent was to not include the length as is your suggestion.=C2=A0</div><div=
><br></div><div>=C2=A0</div><blockquote class=3D"gmail_quote" style=3D"marg=
in:0px 0px 0px 0.8ex;border-left:1px solid rgb(204,204,204);padding-left:1e=
x"><div lang=3D"EN-US"><div><p class=3D"MsoNormal"><u></u></p>
<p class=3D"MsoNormal">&gt;[Joe]<span style=3D"font-size:10.5pt;color:rgb(4=
4,67,83)"> Does the revision in 5167 match you implementation ( I don&#39;t=
 think Jouni&#39;s=C2=A0comment changes the underly=C2=A0calculation, just =
its representation)?=C2=A0</span><u></u><u></u></p>
<p class=3D"MsoNormal"><u></u>=C2=A0<u></u></p>
<p class=3D"MsoNormal">I have not implemented this portion of the RFC as I =
found it too unclear to work with. Thus I can=E2=80=99t comment on what imp=
lementations may be doing. However, I agree with the current revision in 51=
67 as the most natural interpretation. If
 others have implemented this portion of the RFC then certainly their comme=
nts would be welcome.<u></u><u></u></p>
<p class=3D"MsoNormal"><br><u></u></p></div></div></blockquote><blockquote =
class=3D"gmail_quote" style=3D"margin:0px 0px 0px 0.8ex;border-left:1px sol=
id rgb(204,204,204);padding-left:1ex"><div lang=3D"EN-US"><div><p class=3D"=
MsoNormal"><u></u></p>
<p class=3D"MsoNormal">By the way, we=E2=80=99ve dropped the EMU group on o=
ur replies here =E2=80=93 not sure if intentional or not.<u></u><u></u></p>
<p class=3D"MsoNormal"><u></u>=C2=A0<u></u></p>
<p class=3D"MsoNormal">Jorge Vergara<u></u><u></u></p>
<p class=3D"MsoNormal"><u></u>=C2=A0<u></u></p>
<div style=3D"border-right:none;border-bottom:none;border-left:none;border-=
top:1pt solid rgb(225,225,225);padding:3pt 0in 0in">
<p class=3D"MsoNormal"><b>From:</b> Joseph Salowey &lt;<a href=3D"mailto:jo=
e@salowey.net" target=3D"_blank">joe@salowey.net</a>&gt; <br>
<b>Sent:</b> Wednesday, October 21, 2020 4:36 PM<br>
<b>To:</b> Jorge Vergara &lt;<a href=3D"mailto:jovergar@microsoft.com" targ=
et=3D"_blank">jovergar@microsoft.com</a>&gt;<br>
<b>Subject:</b> Re: Proposed resolution for TEAP errata for 5128<u></u><u><=
/u></p>
</div>
<p class=3D"MsoNormal"><u></u>=C2=A0<u></u></p>
<div>
<div>
<p class=3D"MsoNormal"><u></u>=C2=A0<u></u></p>
</div>
<p class=3D"MsoNormal"><u></u>=C2=A0<u></u></p>
<div>
<div>
<p class=3D"MsoNormal">On Wed, Oct 21, 2020 at 3:20 PM Jorge Vergara &lt;<a=
 href=3D"mailto:jovergar@microsoft.com" target=3D"_blank">jovergar@microsof=
t.com</a>&gt; wrote:<u></u><u></u></p>
</div>
<blockquote style=3D"border-top:none;border-right:none;border-bottom:none;b=
order-left:1pt solid rgb(204,204,204);padding:0in 0in 0in 6pt;margin-left:4=
.8pt;margin-right:0in">
<div>
<div>
<p class=3D"MsoNormal">In theory I agree this is a possible resolution. How=
ever, this doesn=E2=80=99t match any of the current TEAP implementations th=
at I am aware of. Perhaps Oleg can weigh in as well in terms
 of what he=E2=80=99s seen.<u></u><u></u></p>
<p class=3D"MsoNormal">=C2=A0<u></u><u></u></p>
<p class=3D"MsoNormal">I believe all current implementations treat 60 as th=
e desired output length without treating as a seed. In terms of P_&lt;hash&=
gt;, this means implementations are performing the calculation
 without a seed.<u></u><u></u></p>
<p class=3D"MsoNormal">=C2=A0<u></u><u></u></p>
<p class=3D"MsoNormal">RFC 5246 defines the TLS 1.2 PRF as:<u></u><u></u></=
p>
<p class=3D"MsoNormal">PRF(secret, label, seed) =3D P_&lt;hash&gt;(secret, =
label + seed)<u></u><u></u></p>
<p class=3D"MsoNormal">=C2=A0<u></u><u></u></p>
<p class=3D"MsoNormal">So the calculation implementations are currently per=
forming with an empty seed ends up as:<u></u><u></u></p>
<p class=3D"MsoNormal">P_&lt;hash&gt;(secret, label)<u></u><u></u></p>
<p class=3D"MsoNormal">=C2=A0<u></u><u></u></p>
<p class=3D"MsoNormal">Note that in RFC 5295, the length *is* explicitly me=
ntioned as being concatenated with the label<u></u><u></u></p>
<p class=3D"MsoNormal">USRK =3D KDF(EMSK, key label | &quot;\0&quot; | opti=
onal data | length)<u></u><u></u></p>
<p class=3D"MsoNormal">=C2=A0<u></u><u></u></p>
<p class=3D"MsoNormal">RFC 5295 is mentioned earlier in the TEAP RFC, in th=
e section covered by errata 5127. *However* it is not mentioned in this por=
tion of the RFC. Since this calculation is not on
 an EMSK, I do not believe RFC 2395 applies and this is likely why implemen=
tations went with the seedless P_&lt;hash&gt;(secret, label) calculation in=
stead.<u></u><u></u></p>
<p class=3D"MsoNormal">=C2=A0<u></u><u></u></p>
<p class=3D"MsoNormal">Is there concern about updating the RFC in a way tha=
t breaks existing implementations?<u></u><u></u></p>
<p class=3D"MsoNormal">=C2=A0<u></u><u></u></p>
</div>
</div>
</blockquote>
<div>
<p class=3D"MsoNormal">[Joe] Yes this is a concern and I think your=C2=A0in=
terpretation of the current document is also valid.=C2=A0 There may be more=
 than one implementation.=C2=A0 So what you implemented was:<u></u><u></u><=
/p>
</div>
<div>
<p class=3D"MsoNormal"><u></u>=C2=A0<u></u></p>
</div>
<div>
<p class=3D"MsoNormal">IMCK[j] =3D TLS-PRF(S-IMCK[j-1], &quot;Inner Methods=
 Compound Keys&quot;,=C2=A0<span style=3D"font-size:10.5pt;color:rgb(44,67,=
83)">IMSK[j]) =3D P_&lt;hash&gt;(S-IMCK[j-1], &quot;Inner Methods Compound =
Keys&quot; | IMSK[j])</span><u></u><u></u></p>
</div>
<div>
<p class=3D"MsoNormal"><u></u>=C2=A0<u></u></p>
</div>
<div>
<p class=3D"MsoNormal">taken out to 60 bytes.=C2=A0 The problem is that the=
 TEAP spec references a TLS-PRF in a way that it does not define.=C2=A0 I t=
hink the errata points out the definition that should be used:<u></u><u></u=
></p>
</div>
<div>
<p class=3D"MsoNormal"><u></u>=C2=A0<u></u></p>
</div>
<div>
<p class=3D"MsoNormal">PRF(secret, label, seed) =3D P_&lt;hash&gt;(secret, =
label + seed)<u></u><u></u></p>
</div>
<div>
<p class=3D"MsoNormal"><u></u>=C2=A0<u></u></p>
</div>
<div>
<p class=3D"MsoNormal">That does not include length so the 60 in the origin=
al definition=C2=A0is ambiguous.=C2=A0 =C2=A0The new text would then be som=
ething like:<u></u><u></u></p>
</div>
<div>
<p class=3D"MsoNormal"><u></u>=C2=A0<u></u></p>
</div>
<div>
<p class=3D"MsoNormal">IMCK[j] =3D TLS-PRF(S-IMCK[j-1], &quot;Inner Methods=
 Compound Keys&quot;,=C2=A0<span style=3D"font-size:10.5pt;color:rgb(44,67,=
83)">IMSK[j])=C2=A0 to generate a length of 60 bytes</span><u></u><u></u></=
p>
</div>
<div>
<p class=3D"MsoNormal"><u></u>=C2=A0<u></u></p>
</div>
<div>
<p class=3D"MsoNormal"><span style=3D"font-size:10.5pt;color:rgb(44,67,83)"=
>Does the revision in 5167 match you implementation ( I don&#39;t think Jou=
ni&#39;s=C2=A0comment changes the underly=C2=A0calculation, just its repres=
entation)?=C2=A0</span><u></u><u></u></p>
</div>
<div>
<p class=3D"MsoNormal"><u></u>=C2=A0<u></u></p>
</div>
<div>
<p class=3D"MsoNormal"><u></u>=C2=A0<u></u></p>
</div>
<div>
<p class=3D"MsoNormal"><u></u>=C2=A0<u></u></p>
</div>
<div>
<p class=3D"MsoNormal"><u></u>=C2=A0<u></u></p>
</div>
<div>
<p class=3D"MsoNormal">=C2=A0<u></u><u></u></p>
</div>
<blockquote style=3D"border-top:none;border-right:none;border-bottom:none;b=
order-left:1pt solid rgb(204,204,204);padding:0in 0in 0in 6pt;margin-left:4=
.8pt;margin-right:0in">
<div>
<div>
<p class=3D"MsoNormal">Jorge Vergara<u></u><u></u></p>
<p class=3D"MsoNormal">=C2=A0<u></u><u></u></p>
<div style=3D"border-right:none;border-bottom:none;border-left:none;border-=
top:1pt solid rgb(225,225,225);padding:3pt 0in 0in">
<p class=3D"MsoNormal"><b>From:</b> Joseph Salowey &lt;<a href=3D"mailto:jo=
e@salowey.net" target=3D"_blank">joe@salowey.net</a>&gt;
<br>
<b>Sent:</b> Wednesday, October 21, 2020 2:34 PM<br>
<b>To:</b> EMU WG &lt;<a href=3D"mailto:emu@ietf.org" target=3D"_blank">emu=
@ietf.org</a>&gt;; Jouni Malinen &lt;<a href=3D"mailto:j@w1.fi" target=3D"_=
blank">j@w1.fi</a>&gt;; Jorge Vergara &lt;<a href=3D"mailto:jovergar@micros=
oft.com" target=3D"_blank">jovergar@microsoft.com</a>&gt;; Oleg
 Pekar (olpekar) &lt;<a href=3D"mailto:olpekar@cisco.com" target=3D"_blank"=
>olpekar@cisco.com</a>&gt;<br>
<b>Subject:</b> Proposed resolution for TEAP errata for 5128<u></u><u></u><=
/p>
</div>
<p class=3D"MsoNormal">=C2=A0<u></u><u></u></p>
<div>
<p class=3D"MsoNormal">Errata 5128:=C2=A0<a href=3D"https://nam06.safelinks=
.protection.outlook.com/?url=3Dhttps%3A%2F%2Fwww.rfc-editor.org%2Ferrata%2F=
eid5128&amp;data=3D04%7C01%7Cjovergar%40microsoft.com%7C38c27add2cb64a06310=
108d8761a22d3%7C72f988bf86f141af91ab2d7cd011db47%7C1%7C0%7C6373892019090627=
87%7CUnknown%7CTWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1h=
aWwiLCJXVCI6Mn0%3D%7C1000&amp;sdata=3DXudZt9FPh4jOBFQj01SQysnhX4p7G%2BflW2P=
n2yIaJRM%3D&amp;reserved=3D0" target=3D"_blank">https://www.rfc-editor.org/=
errata/eid5128</a><u></u><u></u></p>
<div>
<p class=3D"MsoNormal">Proposed State: Verified<u></u><u></u></p>
</div>
<div>
<p class=3D"MsoNormal">Revision:<u></u><u></u></p>
</div>
<div>
<p class=3D"MsoNormal">=C2=A0<u></u><u></u></p>
</div>
<div>
<p class=3D"MsoNormal">Section 5.2. says<u></u><u></u></p>
</div>
<div>
<p style=3D"margin-right:3.75pt;margin-bottom:7.5pt;margin-left:3.75pt">
<br>
IMCK[j] =3D TLS-PRF(S-IMCK[j-1], &quot;Inner Methods Compound Keys&quot;,<b=
r>
=C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 IMSK[j], 60)<br>
<br>
It should say:<br>
<br>
IMCK[j] =3D TLS-PRF(S-IMCK[j-1], &quot;Inner Methods Compound Keys&quot;,=
=C2=A0<span style=3D"font-size:10.5pt;font-family:Arial,sans-serif;color:rg=
b(44,67,83)">IMSK[j] | 60)</span><u></u><u></u></p>
<p style=3D"margin-right:3.75pt;margin-bottom:7.5pt;margin-left:3.75pt">
<span style=3D"font-size:10.5pt;font-family:Arial,sans-serif;color:rgb(44,6=
7,83)">Note:=C2=A0=C2=A0</span><u></u><u></u></p>
<p class=3D"MsoNormal">According to<br>
<br>
RFC5246 The Transport Layer Security (TLS) Protocol Version 1.2<br>
<br>
5. HMAC and the Pseudorandom Function<br>
<br>
&quot;TLS&#39;s PRF is created by applying P_hash to the secret as:<br>
<br>
PRF(secret, label, seed) =3D P_&lt;hash&gt;(secret, label + seed)&quot;<u><=
/u><u></u></p>
</div>
<div>
<p class=3D"MsoNormal">=C2=A0<u></u><u></u></p>
</div>
<div>
<p class=3D"MsoNormal">In terms of P_&lt;hash&gt; this would look like the =
following with the length represented as a 2 byte value in network byte ord=
er:<u></u><u></u></p>
</div>
<div>
<p class=3D"MsoNormal">=C2=A0<u></u><u></u></p>
</div>
<div>
<p class=3D"MsoNormal">IMCK[j] =3D P_&lt;hash&gt;(S-IMCK[j-1], &quot;Inner =
Methods Compound Keys&quot; |=C2=A0<span style=3D"font-size:10.5pt;color:rg=
b(44,67,83)">IMSK[j] | 0x00 | 0x3C)</span><u></u><u></u></p>
</div>
<div>
<p class=3D"MsoNormal">=C2=A0<u></u><u></u></p>
</div>
<div>
<p class=3D"MsoNormal">=C2=A0<u></u><u></u></p>
</div>
</div>
</div>
</div>
</blockquote>
</div>
</div>
</div>
</div>

</blockquote></div></div>
</blockquote></div></div>

--0000000000006a4f8505b242df5f--


From nobody Thu Oct 22 07:13:12 2020
Return-Path: <jovergar@microsoft.com>
X-Original-To: emu@ietfa.amsl.com
Delivered-To: emu@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 257673A0D33 for <emu@ietfa.amsl.com>; Thu, 22 Oct 2020 07:13:11 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.001
X-Spam-Level: 
X-Spam-Status: No, score=-2.001 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIMWL_WL_HIGH=-0.001, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, DKIM_VALID_EF=-0.1, HTML_MESSAGE=0.001, HTTPS_HTTP_MISMATCH=0.1, RCVD_IN_MSPIKE_H2=-0.001, SPF_PASS=-0.001, URIBL_BLOCKED=0.001] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (1024-bit key) header.d=microsoft.com
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 wW1iCWMAtBQa for <emu@ietfa.amsl.com>; Thu, 22 Oct 2020 07:13:08 -0700 (PDT)
Received: from NAM10-DM6-obe.outbound.protection.outlook.com (mail-dm6nam10on2111.outbound.protection.outlook.com [40.107.93.111]) (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 92AA53A0147 for <emu@ietf.org>; Thu, 22 Oct 2020 07:13:05 -0700 (PDT)
ARC-Seal: i=1; a=rsa-sha256; s=arcselector9901; d=microsoft.com; cv=none; b=axEyxTltKqHB11utJj8Jw0bpyqEDv7DdI5xYQMkhK+cXsK+yTtMSnmTvkuwNefzZmnp6aOHKRPzb44tbN0wsZLoaAEuG0eDUt004HIRSBJMzuiDl4wGPiwJdJVyWzSUW6nNTit91PGeJaT12DjSo5GUZXhwQPbLoFfCJ69o50i9Pzz1bKbvQkn8kf1yBMQaVHJ1f0XGwmBSpTzyQmt/kPmJm/gYWlK7y15FIAMQEKCjbcziex3qTQiETK0DsdG7qCp3Ds1pPPDBgZA4+TL8I06T9mJWjWj8oqJCgEn+nLDvYNuEz8iJlYs1kNC53sDsBgpHWgohaSpTy30vLHA1wPA==
ARC-Message-Signature: i=1; a=rsa-sha256; c=relaxed/relaxed; d=microsoft.com;  s=arcselector9901; h=From:Date:Subject:Message-ID:Content-Type:MIME-Version:X-MS-Exchange-SenderADCheck; bh=6avmtQS1HxbrUkwOW/a1X5CN45HkKhQcZ9zL5jo7Dyk=; b=UrUeo2348XLFlK+yqIQ186fkB6f12OrSJd+ax7zSXguwEDVs5MPWNXCCWfZU5YKSK5ySPjgG2Hp7CkgZbbrBtZYe5UBdVtfSv2EjhQrI6Z2728TyFKepr1nNTH7pVnEvo8J2UbiFf91c6NG3An8vWNoHcbzoYvOyVjxLREjmUzPoQJXVFqbVZBPNltTOG/8T5D7mMOkJExhGIo1+lxtAHaR47mcbs4ghz/wVZMf/JZeBC3xpywjIuCI6mq0jPCjaRyIqlsEfpkSNRvoG2evHVc9TFt6A3aGcEG84WyB+krqYPNcTmPs6P878GGZAWO1x9CNFbrYClGT3QhLzCMmSAQ==
ARC-Authentication-Results: i=1; mx.microsoft.com 1; spf=pass smtp.mailfrom=microsoft.com; dmarc=pass action=none header.from=microsoft.com; dkim=pass header.d=microsoft.com; arc=none
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=microsoft.com; s=selector2; h=From:Date:Subject:Message-ID:Content-Type:MIME-Version:X-MS-Exchange-SenderADCheck; bh=6avmtQS1HxbrUkwOW/a1X5CN45HkKhQcZ9zL5jo7Dyk=; b=bpbNZaktqTKffyeAFoax/Y7EivB2kM0OClxDH2lDYwCJjo3yygt50vy0jy9bdoG7X+0HR1zSJM/ijQhJm/R3tFrq8b8Lvfn1kb2lYB79Ne6v4sAWdtJcBYxEEeeyRSFtWDmQJyp1eAxFgHkfTTH4mnNib6I4D7Z3rjW4h6fcZzI=
Received: from CH2PR21MB1381.namprd21.prod.outlook.com (2603:10b6:610:8e::12) by CH2PR21MB1413.namprd21.prod.outlook.com (2603:10b6:610:8c::24) with Microsoft SMTP Server (version=TLS1_2, cipher=TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384) id 15.20.3499.3; Thu, 22 Oct 2020 14:13:00 +0000
Received: from CH2PR21MB1381.namprd21.prod.outlook.com ([fe80::dfd:b166:92c:5a84]) by CH2PR21MB1381.namprd21.prod.outlook.com ([fe80::dfd:b166:92c:5a84%9]) with mapi id 15.20.3499.017; Thu, 22 Oct 2020 14:13:00 +0000
From: Jorge Vergara <jovergar@microsoft.com>
To: Oleg Pekar <oleg.pekar.2017@gmail.com>, Joseph Salowey <joe@salowey.net>
CC: EMU WG <emu@ietf.org>, Jouni Malinen <j@w1.fi>
Thread-Topic: Proposed resolution for TEAP errata for 5128
Thread-Index: AQHWp/H/5iLrTwXdRkW9JLXm9c5wSaminKRAgAAZaYCAAADdIIAABDMAgADsEACAAAHRwA==
Date: Thu, 22 Oct 2020 14:12:59 +0000
Message-ID: <CH2PR21MB1381E75B194E1CEDEBFDE113D11D0@CH2PR21MB1381.namprd21.prod.outlook.com>
References: <CAOgPGoBay+GG=F8WV0gLOOwLtGdGALGw_cM2JoAnXOtmGq7A+w@mail.gmail.com> <CH2PR21MB138143E929DAFE3C893D8144D11C0@CH2PR21MB1381.namprd21.prod.outlook.com> <CAOgPGoAtcm+Br+YkCyTtg5nJjqO7LGSo77b+CD4+Ba05azafew@mail.gmail.com> <CH2PR21MB13815BCEDC846D7C440AD564D11C0@CH2PR21MB1381.namprd21.prod.outlook.com> <CAOgPGoDTC-qiHOXFTJd7aMn2To7ySzBcx+iQMB9m5foC1bFxzw@mail.gmail.com> <CABXxEz8SRvMXdMR8_cPfvWdauJZwCjnd=7ytnVZ+_L-sB48wvw@mail.gmail.com>
In-Reply-To: <CABXxEz8SRvMXdMR8_cPfvWdauJZwCjnd=7ytnVZ+_L-sB48wvw@mail.gmail.com>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
msip_labels: MSIP_Label_f42aa342-8706-4288-bd11-ebb85995028c_ActionId=7e7c722d-ab20-448b-b8a5-058e7aaa3f30; MSIP_Label_f42aa342-8706-4288-bd11-ebb85995028c_ContentBits=0; MSIP_Label_f42aa342-8706-4288-bd11-ebb85995028c_Enabled=true; MSIP_Label_f42aa342-8706-4288-bd11-ebb85995028c_Method=Standard; MSIP_Label_f42aa342-8706-4288-bd11-ebb85995028c_Name=Internal; MSIP_Label_f42aa342-8706-4288-bd11-ebb85995028c_SetDate=2020-10-22T14:05:49Z;  MSIP_Label_f42aa342-8706-4288-bd11-ebb85995028c_SiteId=72f988bf-86f1-41af-91ab-2d7cd011db47;
authentication-results: gmail.com; dkim=none (message not signed) header.d=none;gmail.com; dmarc=none action=none header.from=microsoft.com;
x-originating-ip: [2001:4898:80e8:f:28:eedc:a141:1405]
x-ms-publictraffictype: Email
x-ms-office365-filtering-ht: Tenant
x-ms-office365-filtering-correlation-id: f0f25ec9-cac4-45f9-7de4-08d876949506
x-ms-traffictypediagnostic: CH2PR21MB1413:
x-microsoft-antispam-prvs: <CH2PR21MB1413730F29416D497CEBD1B3D11D0@CH2PR21MB1413.namprd21.prod.outlook.com>
x-ms-oob-tlc-oobclassifiers: OLM:10000;
x-ms-exchange-senderadcheck: 1
x-microsoft-antispam: BCL:0;
x-microsoft-antispam-message-info: fvUQOK7imr51zpAHFa2sc3+EuYnnlSfhms1025q+7igW7yOG69Mr4Lb8GzmwHpDy+DdURY4MYiRX2vCTBtKfsae2yjYIkymuk1o6EL6OXdJOiND7xc7pP7TCNgcyS1kk8sDm33USaY8LaN/Hrsme4Zd5cj+ffce4qLgbHMFlWC08MC2Jx+6FtQmSdrPVVBXwoKZa3XnCH3ULNTNOhKWtUAyfjYBimPGwg+6iB1MrXuS7lGewPf6en8TTzEYX8pp6Ots70QWBYmMBaPQEuKX0yAGiNhstNSKpS0UIlh8sc6PMxfLmeFW4SeV+z0evtNmpUpDtq8cbqVqfUYi80VpmMfs8VLvjAfqZFHseeQmvF0U6vL+DfbWW9yH7X686oHsaRDHk6vzQXQj24kkFcwn4Ag==
x-forefront-antispam-report: CIP:255.255.255.255; CTRY:; LANG:en; SCL:1; SRV:;  IPV:NLI; SFV:NSPM; H:CH2PR21MB1381.namprd21.prod.outlook.com; PTR:; CAT:NONE;  SFS:(4636009)(346002)(366004)(136003)(376002)(396003)(39860400002)(33656002)(9686003)(4326008)(8936002)(54906003)(10290500003)(8990500004)(110136005)(82950400001)(2906002)(8676002)(316002)(83380400001)(166002)(66446008)(66476007)(71200400001)(55016002)(82960400001)(66946007)(186003)(7696005)(76116006)(478600001)(966005)(53546011)(86362001)(6506007)(5660300002)(52536014)(66556008)(64756008); DIR:OUT; SFP:1102; 
x-ms-exchange-antispam-messagedata: GlCMQ3SD5sd7oPEAai5wMtAQiKtTW/sKMvHmelNdxasq4yJVwYV+3v4RnG/dLSM8Ttcfl/YNuK176SLqCaZnv2OlcsyhJS4Oecczd7EDHzJNqWosdBFOkTU8mEy+2+MEpD/9NzUkdmdp1l5n8f6kCJ48UKwJY+slnlffvJVEZ1GUlV+/QTfqq9T0UEmOrxkA4q67g6usi46SS7noqjK9DX/4LR7NzB0Q0r1PHLUqMv6K4K6wk4FR+GYPXA8p1dfFOoA34G1EK0BXkO+kmR7GXtqtyTYKwzwm0wjnWy8PwlG8OwH6nVXckiWJVqTub9M8/LWQ/NdX5uaC9cVLz7xCcosQXfRVMMkTR145IL1TrKNU5z5/vp52ovNSKgP5lIAGvJ9F3sHoZ/BGwJdWe2SxpMjrFEXe4I5jt39zaCjFgoqGRQmW29Qxtsar8oPtPM/r22482K+fqObOdesP7sAdwVKEohk3ksTgM0+qGFK7rEbLaVabBfQoHRmImAdjKW7TqyASLWc8iFlyYIp5hIKIS9uS2xGMXDOqIxmdAlEwCWGGURsOM5f94r7M29YvXgLm44puyCecYBW3vdwCtakzSJ96cKic8GdIwzZbV1swR9FRJPpc8bQHvQTeApoo1/iF/RKl/15yWhmAa5splSCyG6rw5IcEQB5EsnNpSsHhHCVrTBgFqG6iAzzVORAMs67OYjsQ0aqWFOJYNKDr85EwQg==
x-ms-exchange-transport-forked: True
Content-Type: multipart/alternative; boundary="_000_CH2PR21MB1381E75B194E1CEDEBFDE113D11D0CH2PR21MB1381namp_"
MIME-Version: 1.0
X-OriginatorOrg: microsoft.com
X-MS-Exchange-CrossTenant-AuthAs: Internal
X-MS-Exchange-CrossTenant-AuthSource: CH2PR21MB1381.namprd21.prod.outlook.com
X-MS-Exchange-CrossTenant-Network-Message-Id: f0f25ec9-cac4-45f9-7de4-08d876949506
X-MS-Exchange-CrossTenant-originalarrivaltime: 22 Oct 2020 14:12:59.8820 (UTC)
X-MS-Exchange-CrossTenant-fromentityheader: Hosted
X-MS-Exchange-CrossTenant-id: 72f988bf-86f1-41af-91ab-2d7cd011db47
X-MS-Exchange-CrossTenant-mailboxtype: HOSTED
X-MS-Exchange-CrossTenant-userprincipalname: SBnciJpwj6krViB1b5QVf0qkKIhP6mYe0vGB+0niU1Z+TuPcOOhKhXGB2sjq7z2pTw6rjg0Ov/0XfoLPAqbDvA==
X-MS-Exchange-Transport-CrossTenantHeadersStamped: CH2PR21MB1413
Archived-At: <https://mailarchive.ietf.org/arch/msg/emu/Hn-2N2mjKugUf9ByHvPIOUwdtDg>
Subject: Re: [Emu] Proposed resolution for TEAP errata for 5128
X-BeenThere: emu@ietf.org
X-Mailman-Version: 2.1.29
Precedence: list
List-Id: "EAP Methods Update \(EMU\)" <emu.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/emu>, <mailto:emu-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/emu/>
List-Post: <mailto:emu@ietf.org>
List-Help: <mailto:emu-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/emu>, <mailto:emu-request@ietf.org?subject=subscribe>
X-List-Received-Date: Thu, 22 Oct 2020 14:13:11 -0000

--_000_CH2PR21MB1381E75B194E1CEDEBFDE113D11D0CH2PR21MB1381namp_
Content-Type: text/plain; charset="utf-8"
Content-Transfer-Encoding: base64

TXkgY29uY2VybiB3aXRoIHRoaXMgcHJvcG9zYWwgb2YgZGVmaW5pbmcgYSBuZXcgS0RGIGlzIHRo
YXQgaXQgaXMgYSBjbGVhciBicmVha2luZyBjaGFuZ2UgdG8gYW55IGltcGxlbWVudGF0aW9uIHRo
YXQgbWF5IGV4aXN0Lg0KDQpJbiBteSBvcGluaW9uIHN1Y2ggYSBjaGFuZ2Ugd291bGQgYmUgZmlu
ZSBpZiB3ZSB3YW50IHRvIGJ1bXAgc29tZSB2ZXJzaW9uIG51bWJlcnMgLSBtYXliZSB0aGUgVEVB
UCB2ZXJzaW9uIG51bWJlciBoYXMgdG8gYmUgYnVtcGVkLCBvciBtYXliZSB0aGlzIGNhbiBiZSBh
Y2hpZXZlZCBzb2xlbHkgd2l0aCB0aGUgVExWIHZlcnNpb24gZmllbGRzIHNvbWUgb2YgdGhlIFRM
VnMgY29udGFpbi4gSSBoYXZlbuKAmXQgdGhvdWdodCBhYm91dCB0aGlzIGFzcGVjdCBvZiB0b28g
bXVjaC4gQnV0IHJlZGVmaW5pbmcgdGhlIEtERiBlbnRpcmVseSB3aXRoIG5vIHZlcnNpb24gY2hh
bmdlcyB3b3VsZCBiZSBkaXNydXB0aXZlIHRvIG11bHRpcGxlIHByb2R1Y3RzLg0KDQpUaGlzIGxl
YWRzIHRvIGEgZm9sbG93LXVwIGNvbmNlcm4gaXMgLSBpZiBhbiBlbnRpcmVseSBuZXcgS0RGIHdl
cmUgdG8gYmUgZGVmaW5lZCwgSSBiZWxpZXZlIGl0IHNob3VsZCBhdm9pZCB1c2luZyB0aGUgVExT
IDEuMiBQUkYgc2luY2UgaXQgaXMgYWxyZWFkeSBvYnNvbGV0ZWQgaW4gVExTIDEuMy4NCg0KSm9y
Z2UgVmVyZ2FyYQ0KDQpGcm9tOiBPbGVnIFBla2FyIDxvbGVnLnBla2FyLjIwMTdAZ21haWwuY29t
Pg0KU2VudDogVGh1cnNkYXksIE9jdG9iZXIgMjIsIDIwMjAgNjo1OSBBTQ0KVG86IEpvc2VwaCBT
YWxvd2V5IDxqb2VAc2Fsb3dleS5uZXQ+DQpDYzogRU1VIFdHIDxlbXVAaWV0Zi5vcmc+OyBKb3Jn
ZSBWZXJnYXJhIDxqb3ZlcmdhckBtaWNyb3NvZnQuY29tPjsgSm91bmkgTWFsaW5lbiA8akB3MS5m
aT4NClN1YmplY3Q6IFJlOiBQcm9wb3NlZCByZXNvbHV0aW9uIGZvciBURUFQIGVycmF0YSBmb3Ig
NTEyOA0KDQpIaSBhbGwsDQpTcGVha2luZyBhYm91dCBib3RoIGVycmF0YSA1MTI3IGFuZCA1MTI4
LCBJIHRoaW5rIHdlIG5lZWQgdG8gYWxpZ24gYWxsIGtleSBkZXJpdmF0aW9uIGNhbGxzIGluIFRF
QVAgUkZDIHdpdGggdGhlIHNhbWUgcnVsZS9mb3JtYXQgdG8gbWFrZSB0aGUgUkZDIGVhc2llciB0
byB1bmRlcnN0YW5kLiBUaGlzIGNhbiBiZSBhY2hpZXZlZCBieSBpbnRyb2R1Y2luZyBhIHVuaWZp
ZWQgc2luZ2xlIFBSRiBmdW5jdGlvbiB0aGF0IHdpbGwgYmUgY2FsbGVkIGZyb20gYWxsIHRoZSBy
ZWxldmFudCBSRkMgbG9jYXRpb25zLiBGb3IgbWUgaXQgc291bmRzIGJldHRlciB0aGFuIGlmIHdl
IGFsaWduIGp1c3QgcGFydCBvZiBLREYgY2FsbHMgd2l0aCBSRkMgNTI5NSAod2hlcmUgdGhlIG91
dHB1dCBsZW5ndGggaXMgaW5jbHVkZWQgaW50byBzZWVkKS4gQWxzbzogaW4gc29tZSBLREYgY2Fs
bHMgd2UgZG8gaGF2ZSBvcHRpb25hbCBkYXRhIGFuZCBpbiBzb21lIG5vLiBUaGlzIGNvdWxkIGJl
IGFsc28gdW5pZmllZC4NCg0KU28gSSB3b3VsZCBzdWdnZXN0IGludHJvZHVjaW5nOg0KVEVBUC1Q
UkYgKHNlY3JldCwga2V5IGxhYmVsLCBvcHRpb25hbCBkYXRhLCBsZW5ndGgpID0gVExTLVBSRihz
ZWNyZXQsIGtleSBsYWJlbCB8IDB4MDAgfCBvcHRpb25hbCBkYXRhLCBsZW5ndGgpDQp3aGVyZSBh
IHNpbmdsZSBieXRlIDB4MDAgaXMgdXNlZCBmb3Igbm8gb3B0aW9uYWwgZGF0YSwgbGVuZ3RoIGlz
IGEgMi1vY3RldCB1bnNpZ25lZCBpbnRlZ2VyIGluIG5ldHdvcmsgYnl0ZSBvcmRlci4NCg0KVGhl
bjoNCklNU0sgPSBGaXJzdCAzMiBvY3RldHMgb2YgVEVBUC1QUkYoRU1TSywgIlRFQVBiaW5ka2V5
QGlldGYub3JnPG1haWx0bzpURUFQYmluZGtleUBpZXRmLm9yZz4iLCA2NCkgPSBUTFMtUFJGKEVN
U0ssICJURUFQYmluZGtleUBpZXRmLm9yZzxtYWlsdG86VEVBUGJpbmRrZXlAaWV0Zi5vcmc+IiB8
IDB4MDAgfCAweDAwIHwgMHgwMCB8IDB4NDApDQpJTUNLW2pdID0gVEVBUC1QUkYoUy1JTUNLW2ot
MV0sICJJbm5lciBNZXRob2RzIENvbXBvdW5kIEtleXMiLCBJTVNLW2pdLCA2MCkgPSBUTFMtUFJG
KFMtSU1DS1tqLTFdLCAiSW5uZXIgTWV0aG9kcyBDb21wb3VuZCBLZXlzIiB8IDB4MDAgfCBJTVNL
W2pdIHwgMHgwMCB8IDB4M0MpDQpNU0sgPSBURUFQLVBSRihTLUlNQ0tbal0sICJTZXNzaW9uIEtl
eSBHZW5lcmF0aW5nIEZ1bmN0aW9u4oCdLCA2NCkgPSBUTFMtUFJGKFMtSU1DS1tqXSwgIlNlc3Np
b24gS2V5IEdlbmVyYXRpbmcgRnVuY3Rpb24iIHwgMHgwMCB8IDB4MDAgfCAweDAwIHwgMHg0MCkN
CkVNU0sgPSBURUFQLVBSRihTLUlNQ0tbal0sIOKAnUV4dGVuZGVkIFNlc3Npb24gS2V5IEdlbmVy
YXRpbmcgRnVuY3Rpb27igJ0sIDY0KSA9IFRMUy1QUkYoUy1JTUNLW2pdLCAiRXh0ZW5kZWQgU2Vz
c2lvbiBLZXkgR2VuZXJhdGluZyBGdW5jdGlvbiIgfCAweDAwIHwgMHgwMCB8IDB4MDAgfCAweDQw
KQ0KDQpUaGlzIG1heSBjaGFuZ2UgdGhlIGV4aXN0aW5nIGltcGxlbWVudGF0aW9uIGJ1dCB3aWxs
IG1ha2UgaXQgbW9yZSBjbGVhciAtIG5lZWQgdG8gY3JlYXRlIGFuZCBjYWxsIGp1c3Qgb25lIEtE
RiBmdW5jdGlvbi4NCg0KV2UgY2FuIHJlbW92ZSAweDAwIHRoYXQgY29tZXMgYWZ0ZXIgdGhlIGtl
eSBsYWJlbCAtIHdoaWxlIGl0IGlzIHJlcXVpcmVkIGJ5IFJGQyA1Mjk1LiBCdXQgdGhlcmUgdGhl
IGtleSBsYWJlbCBpcyBhbHNvIEFTQ0lJIHByaW50YWJsZSBzdHJpbmcuIEpvZSwgZG8geW91IHJl
bWVtYmVyIHdoYXQgd2FzIHRoZSBtb3RpdmF0aW9uIHRvIHB1dCAweDAwIGFmdGVyIHRoZSBrZXkg
bGFiZWwgcGFyYW1ldGVyPw0KDQpPbGVnDQoNCg0KT24gVGh1LCBPY3QgMjIsIDIwMjAgYXQgMjo1
NCBBTSBKb3NlcGggU2Fsb3dleSA8am9lQHNhbG93ZXkubmV0PG1haWx0bzpqb2VAc2Fsb3dleS5u
ZXQ+PiB3cm90ZToNCihJIGFjY2lkZW50YWxseSBkcm9wcGVkIHRoaXMgbGlzdCBmcm9tIHRoZSBj
b252ZXJzYXRpb24pDQoNCk9uIFdlZCwgT2N0IDIxLCAyMDIwIGF0IDQ6NDggUE0gSm9yZ2UgVmVy
Z2FyYSA8am92ZXJnYXJAbWljcm9zb2Z0LmNvbTxtYWlsdG86am92ZXJnYXJAbWljcm9zb2Z0LmNv
bT4+IHdyb3RlOg0KPltKb2VdIFllcyB0aGlzIGlzIGEgY29uY2VybiBhbmQgSSB0aGluayB5b3Vy
IGludGVycHJldGF0aW9uIG9mIHRoZSBjdXJyZW50IGRvY3VtZW50IGlzIGFsc28gdmFsaWQuICBU
aGVyZSBtYXkgYmUgbW9yZSB0aGFuIG9uZSBpbXBsZW1lbnRhdGlvbi4gIFNvIHdoYXQgeW91IGlt
cGxlbWVudGVkIHdhczoNCj4NCj5JTUNLW2pdID0gVExTLVBSRihTLUlNQ0tbai0xXSwgIklubmVy
IE1ldGhvZHMgQ29tcG91bmQgS2V5cyIsIElNU0tbal0pID0gUF88aGFzaD4oUy1JTUNLW2otMV0s
ICJJbm5lciBNZXRob2RzIENvbXBvdW5kIEtleXMiIHwgSU1TS1tqXSkNCg0KWWVzLCB0aGlzIGlz
IHdoYXQgSSBpbXBsZW1lbnRlZC4gQXMgeW91IG1lbnRpb25lZCwgdGhlcmUgYXJlIG11bHRpcGxl
IHBvc3NpYmxlIGludGVycHJldGF0aW9ucyBvZiB0aGlzIHNpbmNlIHRoZSBURUFQIHVzYWdlIGlz
IGluY29ycmVjdC4gSG93ZXZlciwgbXkgaW1wbGVtZW50YXRpb24gZG9lcyBpbnRlcm9wIHdpdGgg
YXQgbGVhc3QgMiBsYXJnZSB2ZW5kb3IgaW1wbGVtZW50YXRpb25zLiBJZiB0aGUgaW1wbGVtZW50
YXRpb25zIHdlcmUgdXNpbmcgZGlmZmVyZW50IGNhbGN1bGF0aW9ucyBoZXJlLCB0aGUgV2ktRmkv
RXRoZXJuZXQgY29ubmVjdGlvbnMgdGhhdCBkZXBlbmQgb24gdGhlIE1TSyB3b3VsZCBmYWlsLiBC
dXQgc2luY2UgY29ubmVjdGlvbnMgd29yaywgSSBjYW4gYXNzdW1lIHdlIGFyZSBhbGwgdXNpbmcg
dGhlIHNhbWUgaW1wbGVtZW50YXRpb24gYW5kIGFycml2aW5nIGF0IHRoZSBzYW1lIE1TSy4gQ2lz
Y28gaXMgb25lIG9mIHRoZSBpbXBsZW1lbnRhdGlvbnMgdGhhdCBJIGhhdmUgdGVzdGVkIGFnYWlu
c3Qgd2hpY2ggaXMgd2h5IEkgd2FzIGhvcGluZyBPbGVnIG1heSBvZmZlciBtb3JlIGNvbnRleHQg
YXMgdG8gd2hhdCBoZSBoYXMgc2Vlbi4NCg0KW0pvZV0gSSBjYW4gaG9wZSBKb3VuaSBjYW4gY2hp
bWUgaW4gb24gdGhpcyBhcyB3ZWxsLiAgSSB0aGluayB0aGUgb3JpZ2luYWwgaW50ZW50IHdhcyB0
byBub3QgaW5jbHVkZSB0aGUgbGVuZ3RoIGFzIGlzIHlvdXIgc3VnZ2VzdGlvbi4NCg0KDQo+W0pv
ZV0gRG9lcyB0aGUgcmV2aXNpb24gaW4gNTE2NyBtYXRjaCB5b3UgaW1wbGVtZW50YXRpb24gKCBJ
IGRvbid0IHRoaW5rIEpvdW5pJ3MgY29tbWVudCBjaGFuZ2VzIHRoZSB1bmRlcmx5IGNhbGN1bGF0
aW9uLCBqdXN0IGl0cyByZXByZXNlbnRhdGlvbik/DQoNCkkgaGF2ZSBub3QgaW1wbGVtZW50ZWQg
dGhpcyBwb3J0aW9uIG9mIHRoZSBSRkMgYXMgSSBmb3VuZCBpdCB0b28gdW5jbGVhciB0byB3b3Jr
IHdpdGguIFRodXMgSSBjYW7igJl0IGNvbW1lbnQgb24gd2hhdCBpbXBsZW1lbnRhdGlvbnMgbWF5
IGJlIGRvaW5nLiBIb3dldmVyLCBJIGFncmVlIHdpdGggdGhlIGN1cnJlbnQgcmV2aXNpb24gaW4g
NTE2NyBhcyB0aGUgbW9zdCBuYXR1cmFsIGludGVycHJldGF0aW9uLiBJZiBvdGhlcnMgaGF2ZSBp
bXBsZW1lbnRlZCB0aGlzIHBvcnRpb24gb2YgdGhlIFJGQyB0aGVuIGNlcnRhaW5seSB0aGVpciBj
b21tZW50cyB3b3VsZCBiZSB3ZWxjb21lLg0KDQpCeSB0aGUgd2F5LCB3ZeKAmXZlIGRyb3BwZWQg
dGhlIEVNVSBncm91cCBvbiBvdXIgcmVwbGllcyBoZXJlIOKAkyBub3Qgc3VyZSBpZiBpbnRlbnRp
b25hbCBvciBub3QuDQoNCkpvcmdlIFZlcmdhcmENCg0KRnJvbTogSm9zZXBoIFNhbG93ZXkgPGpv
ZUBzYWxvd2V5Lm5ldDxtYWlsdG86am9lQHNhbG93ZXkubmV0Pj4NClNlbnQ6IFdlZG5lc2RheSwg
T2N0b2JlciAyMSwgMjAyMCA0OjM2IFBNDQpUbzogSm9yZ2UgVmVyZ2FyYSA8am92ZXJnYXJAbWlj
cm9zb2Z0LmNvbTxtYWlsdG86am92ZXJnYXJAbWljcm9zb2Z0LmNvbT4+DQpTdWJqZWN0OiBSZTog
UHJvcG9zZWQgcmVzb2x1dGlvbiBmb3IgVEVBUCBlcnJhdGEgZm9yIDUxMjgNCg0KDQoNCk9uIFdl
ZCwgT2N0IDIxLCAyMDIwIGF0IDM6MjAgUE0gSm9yZ2UgVmVyZ2FyYSA8am92ZXJnYXJAbWljcm9z
b2Z0LmNvbTxtYWlsdG86am92ZXJnYXJAbWljcm9zb2Z0LmNvbT4+IHdyb3RlOg0KSW4gdGhlb3J5
IEkgYWdyZWUgdGhpcyBpcyBhIHBvc3NpYmxlIHJlc29sdXRpb24uIEhvd2V2ZXIsIHRoaXMgZG9l
c27igJl0IG1hdGNoIGFueSBvZiB0aGUgY3VycmVudCBURUFQIGltcGxlbWVudGF0aW9ucyB0aGF0
IEkgYW0gYXdhcmUgb2YuIFBlcmhhcHMgT2xlZyBjYW4gd2VpZ2ggaW4gYXMgd2VsbCBpbiB0ZXJt
cyBvZiB3aGF0IGhl4oCZcyBzZWVuLg0KDQpJIGJlbGlldmUgYWxsIGN1cnJlbnQgaW1wbGVtZW50
YXRpb25zIHRyZWF0IDYwIGFzIHRoZSBkZXNpcmVkIG91dHB1dCBsZW5ndGggd2l0aG91dCB0cmVh
dGluZyBhcyBhIHNlZWQuIEluIHRlcm1zIG9mIFBfPGhhc2g+LCB0aGlzIG1lYW5zIGltcGxlbWVu
dGF0aW9ucyBhcmUgcGVyZm9ybWluZyB0aGUgY2FsY3VsYXRpb24gd2l0aG91dCBhIHNlZWQuDQoN
ClJGQyA1MjQ2IGRlZmluZXMgdGhlIFRMUyAxLjIgUFJGIGFzOg0KUFJGKHNlY3JldCwgbGFiZWws
IHNlZWQpID0gUF88aGFzaD4oc2VjcmV0LCBsYWJlbCArIHNlZWQpDQoNClNvIHRoZSBjYWxjdWxh
dGlvbiBpbXBsZW1lbnRhdGlvbnMgYXJlIGN1cnJlbnRseSBwZXJmb3JtaW5nIHdpdGggYW4gZW1w
dHkgc2VlZCBlbmRzIHVwIGFzOg0KUF88aGFzaD4oc2VjcmV0LCBsYWJlbCkNCg0KTm90ZSB0aGF0
IGluIFJGQyA1Mjk1LCB0aGUgbGVuZ3RoICppcyogZXhwbGljaXRseSBtZW50aW9uZWQgYXMgYmVp
bmcgY29uY2F0ZW5hdGVkIHdpdGggdGhlIGxhYmVsDQpVU1JLID0gS0RGKEVNU0ssIGtleSBsYWJl
bCB8ICJcMCIgfCBvcHRpb25hbCBkYXRhIHwgbGVuZ3RoKQ0KDQpSRkMgNTI5NSBpcyBtZW50aW9u
ZWQgZWFybGllciBpbiB0aGUgVEVBUCBSRkMsIGluIHRoZSBzZWN0aW9uIGNvdmVyZWQgYnkgZXJy
YXRhIDUxMjcuICpIb3dldmVyKiBpdCBpcyBub3QgbWVudGlvbmVkIGluIHRoaXMgcG9ydGlvbiBv
ZiB0aGUgUkZDLiBTaW5jZSB0aGlzIGNhbGN1bGF0aW9uIGlzIG5vdCBvbiBhbiBFTVNLLCBJIGRv
IG5vdCBiZWxpZXZlIFJGQyAyMzk1IGFwcGxpZXMgYW5kIHRoaXMgaXMgbGlrZWx5IHdoeSBpbXBs
ZW1lbnRhdGlvbnMgd2VudCB3aXRoIHRoZSBzZWVkbGVzcyBQXzxoYXNoPihzZWNyZXQsIGxhYmVs
KSBjYWxjdWxhdGlvbiBpbnN0ZWFkLg0KDQpJcyB0aGVyZSBjb25jZXJuIGFib3V0IHVwZGF0aW5n
IHRoZSBSRkMgaW4gYSB3YXkgdGhhdCBicmVha3MgZXhpc3RpbmcgaW1wbGVtZW50YXRpb25zPw0K
DQpbSm9lXSBZZXMgdGhpcyBpcyBhIGNvbmNlcm4gYW5kIEkgdGhpbmsgeW91ciBpbnRlcnByZXRh
dGlvbiBvZiB0aGUgY3VycmVudCBkb2N1bWVudCBpcyBhbHNvIHZhbGlkLiAgVGhlcmUgbWF5IGJl
IG1vcmUgdGhhbiBvbmUgaW1wbGVtZW50YXRpb24uICBTbyB3aGF0IHlvdSBpbXBsZW1lbnRlZCB3
YXM6DQoNCklNQ0tbal0gPSBUTFMtUFJGKFMtSU1DS1tqLTFdLCAiSW5uZXIgTWV0aG9kcyBDb21w
b3VuZCBLZXlzIiwgSU1TS1tqXSkgPSBQXzxoYXNoPihTLUlNQ0tbai0xXSwgIklubmVyIE1ldGhv
ZHMgQ29tcG91bmQgS2V5cyIgfCBJTVNLW2pdKQ0KDQp0YWtlbiBvdXQgdG8gNjAgYnl0ZXMuICBU
aGUgcHJvYmxlbSBpcyB0aGF0IHRoZSBURUFQIHNwZWMgcmVmZXJlbmNlcyBhIFRMUy1QUkYgaW4g
YSB3YXkgdGhhdCBpdCBkb2VzIG5vdCBkZWZpbmUuICBJIHRoaW5rIHRoZSBlcnJhdGEgcG9pbnRz
IG91dCB0aGUgZGVmaW5pdGlvbiB0aGF0IHNob3VsZCBiZSB1c2VkOg0KDQpQUkYoc2VjcmV0LCBs
YWJlbCwgc2VlZCkgPSBQXzxoYXNoPihzZWNyZXQsIGxhYmVsICsgc2VlZCkNCg0KVGhhdCBkb2Vz
IG5vdCBpbmNsdWRlIGxlbmd0aCBzbyB0aGUgNjAgaW4gdGhlIG9yaWdpbmFsIGRlZmluaXRpb24g
aXMgYW1iaWd1b3VzLiAgIFRoZSBuZXcgdGV4dCB3b3VsZCB0aGVuIGJlIHNvbWV0aGluZyBsaWtl
Og0KDQpJTUNLW2pdID0gVExTLVBSRihTLUlNQ0tbai0xXSwgIklubmVyIE1ldGhvZHMgQ29tcG91
bmQgS2V5cyIsIElNU0tbal0pICB0byBnZW5lcmF0ZSBhIGxlbmd0aCBvZiA2MCBieXRlcw0KDQpE
b2VzIHRoZSByZXZpc2lvbiBpbiA1MTY3IG1hdGNoIHlvdSBpbXBsZW1lbnRhdGlvbiAoIEkgZG9u
J3QgdGhpbmsgSm91bmkncyBjb21tZW50IGNoYW5nZXMgdGhlIHVuZGVybHkgY2FsY3VsYXRpb24s
IGp1c3QgaXRzIHJlcHJlc2VudGF0aW9uKT8NCg0KDQoNCg0KDQpKb3JnZSBWZXJnYXJhDQoNCkZy
b206IEpvc2VwaCBTYWxvd2V5IDxqb2VAc2Fsb3dleS5uZXQ8bWFpbHRvOmpvZUBzYWxvd2V5Lm5l
dD4+DQpTZW50OiBXZWRuZXNkYXksIE9jdG9iZXIgMjEsIDIwMjAgMjozNCBQTQ0KVG86IEVNVSBX
RyA8ZW11QGlldGYub3JnPG1haWx0bzplbXVAaWV0Zi5vcmc+PjsgSm91bmkgTWFsaW5lbiA8akB3
MS5maTxtYWlsdG86akB3MS5maT4+OyBKb3JnZSBWZXJnYXJhIDxqb3ZlcmdhckBtaWNyb3NvZnQu
Y29tPG1haWx0bzpqb3ZlcmdhckBtaWNyb3NvZnQuY29tPj47IE9sZWcgUGVrYXIgKG9scGVrYXIp
IDxvbHBla2FyQGNpc2NvLmNvbTxtYWlsdG86b2xwZWthckBjaXNjby5jb20+Pg0KU3ViamVjdDog
UHJvcG9zZWQgcmVzb2x1dGlvbiBmb3IgVEVBUCBlcnJhdGEgZm9yIDUxMjgNCg0KRXJyYXRhIDUx
Mjg6IGh0dHBzOi8vd3d3LnJmYy1lZGl0b3Iub3JnL2VycmF0YS9laWQ1MTI4PGh0dHBzOi8vbmFt
MDYuc2FmZWxpbmtzLnByb3RlY3Rpb24ub3V0bG9vay5jb20vP3VybD1odHRwcyUzQSUyRiUyRnd3
dy5yZmMtZWRpdG9yLm9yZyUyRmVycmF0YSUyRmVpZDUxMjgmZGF0YT0wNCU3QzAxJTdDam92ZXJn
YXIlNDBtaWNyb3NvZnQuY29tJTdDMGMzN2RiMzNkN2E3NGM0ZmRmZDEwOGQ4NzY5MmI0NmYlN0M3
MmY5ODhiZjg2ZjE0MWFmOTFhYjJkN2NkMDExZGI0NyU3QzElN0MwJTdDNjM3Mzg5NzE5NzYyNDgx
MDc1JTdDVW5rbm93biU3Q1RXRnBiR1pzYjNkOGV5SldJam9pTUM0d0xqQXdNREFpTENKUUlqb2lW
Mmx1TXpJaUxDSkJUaUk2SWsxaGFXd2lMQ0pYVkNJNk1uMCUzRCU3QzEwMDAmc2RhdGE9dG0wMSUy
RnFMQUdhUTlIeGV5QmVlVTB5R1BYVk9QZFdqSVJEdFB3VyUyRlJqR0klM0QmcmVzZXJ2ZWQ9MD4N
ClByb3Bvc2VkIFN0YXRlOiBWZXJpZmllZA0KUmV2aXNpb246DQoNClNlY3Rpb24gNS4yLiBzYXlz
DQoNCklNQ0tbal0gPSBUTFMtUFJGKFMtSU1DS1tqLTFdLCAiSW5uZXIgTWV0aG9kcyBDb21wb3Vu
ZCBLZXlzIiwNCiAgICAgICAgICAgICAgICBJTVNLW2pdLCA2MCkNCg0KSXQgc2hvdWxkIHNheToN
Cg0KSU1DS1tqXSA9IFRMUy1QUkYoUy1JTUNLW2otMV0sICJJbm5lciBNZXRob2RzIENvbXBvdW5k
IEtleXMiLCBJTVNLW2pdIHwgNjApDQoNCk5vdGU6DQpBY2NvcmRpbmcgdG8NCg0KUkZDNTI0NiBU
aGUgVHJhbnNwb3J0IExheWVyIFNlY3VyaXR5IChUTFMpIFByb3RvY29sIFZlcnNpb24gMS4yDQoN
CjUuIEhNQUMgYW5kIHRoZSBQc2V1ZG9yYW5kb20gRnVuY3Rpb24NCg0KIlRMUydzIFBSRiBpcyBj
cmVhdGVkIGJ5IGFwcGx5aW5nIFBfaGFzaCB0byB0aGUgc2VjcmV0IGFzOg0KDQpQUkYoc2VjcmV0
LCBsYWJlbCwgc2VlZCkgPSBQXzxoYXNoPihzZWNyZXQsIGxhYmVsICsgc2VlZCkiDQoNCkluIHRl
cm1zIG9mIFBfPGhhc2g+IHRoaXMgd291bGQgbG9vayBsaWtlIHRoZSBmb2xsb3dpbmcgd2l0aCB0
aGUgbGVuZ3RoIHJlcHJlc2VudGVkIGFzIGEgMiBieXRlIHZhbHVlIGluIG5ldHdvcmsgYnl0ZSBv
cmRlcjoNCg0KSU1DS1tqXSA9IFBfPGhhc2g+KFMtSU1DS1tqLTFdLCAiSW5uZXIgTWV0aG9kcyBD
b21wb3VuZCBLZXlzIiB8IElNU0tbal0gfCAweDAwIHwgMHgzQykNCg0KDQo=

--_000_CH2PR21MB1381E75B194E1CEDEBFDE113D11D0CH2PR21MB1381namp_
Content-Type: text/html; charset="utf-8"
Content-Transfer-Encoding: base64

PGh0bWwgeG1sbnM6dj0idXJuOnNjaGVtYXMtbWljcm9zb2Z0LWNvbTp2bWwiIHhtbG5zOm89InVy
bjpzY2hlbWFzLW1pY3Jvc29mdC1jb206b2ZmaWNlOm9mZmljZSIgeG1sbnM6dz0idXJuOnNjaGVt
YXMtbWljcm9zb2Z0LWNvbTpvZmZpY2U6d29yZCIgeG1sbnM6bT0iaHR0cDovL3NjaGVtYXMubWlj
cm9zb2Z0LmNvbS9vZmZpY2UvMjAwNC8xMi9vbW1sIiB4bWxucz0iaHR0cDovL3d3dy53My5vcmcv
VFIvUkVDLWh0bWw0MCI+DQo8aGVhZD4NCjxtZXRhIGh0dHAtZXF1aXY9IkNvbnRlbnQtVHlwZSIg
Y29udGVudD0idGV4dC9odG1sOyBjaGFyc2V0PXV0Zi04Ij4NCjxtZXRhIG5hbWU9IkdlbmVyYXRv
ciIgY29udGVudD0iTWljcm9zb2Z0IFdvcmQgMTUgKGZpbHRlcmVkIG1lZGl1bSkiPg0KPHN0eWxl
PjwhLS0NCi8qIEZvbnQgRGVmaW5pdGlvbnMgKi8NCkBmb250LWZhY2UNCgl7Zm9udC1mYW1pbHk6
IkNhbWJyaWEgTWF0aCI7DQoJcGFub3NlLTE6MiA0IDUgMyA1IDQgNiAzIDIgNDt9DQpAZm9udC1m
YWNlDQoJe2ZvbnQtZmFtaWx5OkNhbGlicmk7DQoJcGFub3NlLTE6MiAxNSA1IDIgMiAyIDQgMyAy
IDQ7fQ0KLyogU3R5bGUgRGVmaW5pdGlvbnMgKi8NCnAuTXNvTm9ybWFsLCBsaS5Nc29Ob3JtYWws
IGRpdi5Nc29Ob3JtYWwNCgl7bWFyZ2luOjBpbjsNCglmb250LXNpemU6MTEuMHB0Ow0KCWZvbnQt
ZmFtaWx5OiJDYWxpYnJpIixzYW5zLXNlcmlmO30NCmE6bGluaywgc3Bhbi5Nc29IeXBlcmxpbmsN
Cgl7bXNvLXN0eWxlLXByaW9yaXR5Ojk5Ow0KCWNvbG9yOmJsdWU7DQoJdGV4dC1kZWNvcmF0aW9u
OnVuZGVybGluZTt9DQpzcGFuLkVtYWlsU3R5bGUxOQ0KCXttc28tc3R5bGUtdHlwZTpwZXJzb25h
bC1yZXBseTsNCglmb250LWZhbWlseToiQ2FsaWJyaSIsc2Fucy1zZXJpZjsNCgljb2xvcjp3aW5k
b3d0ZXh0O30NCi5Nc29DaHBEZWZhdWx0DQoJe21zby1zdHlsZS10eXBlOmV4cG9ydC1vbmx5Ow0K
CWZvbnQtZmFtaWx5OiJDYWxpYnJpIixzYW5zLXNlcmlmO30NCkBwYWdlIFdvcmRTZWN0aW9uMQ0K
CXtzaXplOjguNWluIDExLjBpbjsNCgltYXJnaW46MS4waW4gMS4waW4gMS4waW4gMS4waW47fQ0K
ZGl2LldvcmRTZWN0aW9uMQ0KCXtwYWdlOldvcmRTZWN0aW9uMTt9DQotLT48L3N0eWxlPjwhLS1b
aWYgZ3RlIG1zbyA5XT48eG1sPg0KPG86c2hhcGVkZWZhdWx0cyB2OmV4dD0iZWRpdCIgc3BpZG1h
eD0iMTAyNiIgLz4NCjwveG1sPjwhW2VuZGlmXS0tPjwhLS1baWYgZ3RlIG1zbyA5XT48eG1sPg0K
PG86c2hhcGVsYXlvdXQgdjpleHQ9ImVkaXQiPg0KPG86aWRtYXAgdjpleHQ9ImVkaXQiIGRhdGE9
IjEiIC8+DQo8L286c2hhcGVsYXlvdXQ+PC94bWw+PCFbZW5kaWZdLS0+DQo8L2hlYWQ+DQo8Ym9k
eSBsYW5nPSJFTi1VUyIgbGluaz0iYmx1ZSIgdmxpbms9InB1cnBsZSIgc3R5bGU9IndvcmQtd3Jh
cDpicmVhay13b3JkIj4NCjxkaXYgY2xhc3M9IldvcmRTZWN0aW9uMSI+DQo8cCBjbGFzcz0iTXNv
Tm9ybWFsIj5NeSBjb25jZXJuIHdpdGggdGhpcyBwcm9wb3NhbCBvZiBkZWZpbmluZyBhIG5ldyBL
REYgaXMgdGhhdCBpdCBpcyBhIGNsZWFyIGJyZWFraW5nIGNoYW5nZSB0byBhbnkgaW1wbGVtZW50
YXRpb24gdGhhdCBtYXkgZXhpc3QuPG86cD48L286cD48L3A+DQo8cCBjbGFzcz0iTXNvTm9ybWFs
Ij48bzpwPiZuYnNwOzwvbzpwPjwvcD4NCjxwIGNsYXNzPSJNc29Ob3JtYWwiPkluIG15IG9waW5p
b24gc3VjaCBhIGNoYW5nZSB3b3VsZCBiZSBmaW5lIGlmIHdlIHdhbnQgdG8gYnVtcCBzb21lIHZl
cnNpb24gbnVtYmVycyAtIG1heWJlIHRoZSBURUFQIHZlcnNpb24gbnVtYmVyIGhhcyB0byBiZSBi
dW1wZWQsIG9yIG1heWJlIHRoaXMgY2FuIGJlIGFjaGlldmVkIHNvbGVseSB3aXRoIHRoZSBUTFYg
dmVyc2lvbiBmaWVsZHMgc29tZSBvZiB0aGUgVExWcyBjb250YWluLiBJIGhhdmVu4oCZdCB0aG91
Z2h0DQogYWJvdXQgdGhpcyBhc3BlY3Qgb2YgdG9vIG11Y2guIEJ1dCByZWRlZmluaW5nIHRoZSBL
REYgZW50aXJlbHkgd2l0aCBubyB2ZXJzaW9uIGNoYW5nZXMgd291bGQgYmUgZGlzcnVwdGl2ZSB0
byBtdWx0aXBsZSBwcm9kdWN0cy48bzpwPjwvbzpwPjwvcD4NCjxwIGNsYXNzPSJNc29Ob3JtYWwi
PjxvOnA+Jm5ic3A7PC9vOnA+PC9wPg0KPHAgY2xhc3M9Ik1zb05vcm1hbCI+VGhpcyBsZWFkcyB0
byBhIGZvbGxvdy11cCBjb25jZXJuIGlzIC0gaWYgYW4gZW50aXJlbHkgbmV3IEtERiB3ZXJlIHRv
IGJlIGRlZmluZWQsIEkgYmVsaWV2ZSBpdCBzaG91bGQgYXZvaWQgdXNpbmcgdGhlIFRMUyAxLjIg
UFJGIHNpbmNlIGl0IGlzIGFscmVhZHkgb2Jzb2xldGVkIGluIFRMUyAxLjMuPG86cD48L286cD48
L3A+DQo8cCBjbGFzcz0iTXNvTm9ybWFsIj48bzpwPiZuYnNwOzwvbzpwPjwvcD4NCjxwIGNsYXNz
PSJNc29Ob3JtYWwiPkpvcmdlIFZlcmdhcmE8bzpwPjwvbzpwPjwvcD4NCjxwIGNsYXNzPSJNc29O
b3JtYWwiPjxvOnA+Jm5ic3A7PC9vOnA+PC9wPg0KPGRpdiBzdHlsZT0iYm9yZGVyOm5vbmU7Ym9y
ZGVyLXRvcDpzb2xpZCAjRTFFMUUxIDEuMHB0O3BhZGRpbmc6My4wcHQgMGluIDBpbiAwaW4iPg0K
PHAgY2xhc3M9Ik1zb05vcm1hbCI+PGI+RnJvbTo8L2I+IE9sZWcgUGVrYXIgJmx0O29sZWcucGVr
YXIuMjAxN0BnbWFpbC5jb20mZ3Q7IDxicj4NCjxiPlNlbnQ6PC9iPiBUaHVyc2RheSwgT2N0b2Jl
ciAyMiwgMjAyMCA2OjU5IEFNPGJyPg0KPGI+VG86PC9iPiBKb3NlcGggU2Fsb3dleSAmbHQ7am9l
QHNhbG93ZXkubmV0Jmd0Ozxicj4NCjxiPkNjOjwvYj4gRU1VIFdHICZsdDtlbXVAaWV0Zi5vcmcm
Z3Q7OyBKb3JnZSBWZXJnYXJhICZsdDtqb3ZlcmdhckBtaWNyb3NvZnQuY29tJmd0OzsgSm91bmkg
TWFsaW5lbiAmbHQ7akB3MS5maSZndDs8YnI+DQo8Yj5TdWJqZWN0OjwvYj4gUmU6IFByb3Bvc2Vk
IHJlc29sdXRpb24gZm9yIFRFQVAgZXJyYXRhIGZvciA1MTI4PG86cD48L286cD48L3A+DQo8L2Rp
dj4NCjxwIGNsYXNzPSJNc29Ob3JtYWwiPjxvOnA+Jm5ic3A7PC9vOnA+PC9wPg0KPGRpdj4NCjxk
aXY+DQo8cCBjbGFzcz0iTXNvTm9ybWFsIj5IaSBhbGwsPG86cD48L286cD48L3A+DQo8L2Rpdj4N
CjxkaXY+DQo8cCBjbGFzcz0iTXNvTm9ybWFsIj5TcGVha2luZyBhYm91dCBib3RoIGVycmF0YSA1
MTI3IGFuZCA1MTI4LCBJIHRoaW5rIHdlIG5lZWQgdG8gYWxpZ24gYWxsIGtleSBkZXJpdmF0aW9u
IGNhbGxzIGluIFRFQVAgUkZDIHdpdGggdGhlIHNhbWUgcnVsZS9mb3JtYXQgdG8gbWFrZSB0aGUg
UkZDIGVhc2llciB0byB1bmRlcnN0YW5kLiBUaGlzIGNhbiBiZSBhY2hpZXZlZCBieSBpbnRyb2R1
Y2luZyBhIHVuaWZpZWQgc2luZ2xlIFBSRiBmdW5jdGlvbiB0aGF0DQogd2lsbCBiZSBjYWxsZWQg
ZnJvbSBhbGwgdGhlIHJlbGV2YW50IFJGQyBsb2NhdGlvbnMuIEZvciBtZSBpdCBzb3VuZHMgYmV0
dGVyIHRoYW4gaWYgd2UgYWxpZ24ganVzdCBwYXJ0IG9mIEtERiBjYWxscyB3aXRoIFJGQyA1Mjk1
ICh3aGVyZSB0aGUgb3V0cHV0IGxlbmd0aCBpcyBpbmNsdWRlZCBpbnRvIHNlZWQpLiBBbHNvOiBp
biBzb21lIEtERiBjYWxscyB3ZSBkbyBoYXZlIG9wdGlvbmFsIGRhdGEgYW5kIGluIHNvbWUgbm8u
IFRoaXMgY291bGQgYmUNCiBhbHNvIHVuaWZpZWQuJm5ic3A7PG86cD48L286cD48L3A+DQo8L2Rp
dj4NCjxkaXY+DQo8cCBjbGFzcz0iTXNvTm9ybWFsIj48bzpwPiZuYnNwOzwvbzpwPjwvcD4NCjwv
ZGl2Pg0KPGRpdj4NCjxwIGNsYXNzPSJNc29Ob3JtYWwiPlNvIEkgd291bGQgc3VnZ2VzdCBpbnRy
b2R1Y2luZzo8bzpwPjwvbzpwPjwvcD4NCjwvZGl2Pg0KPGRpdj4NCjxwIGNsYXNzPSJNc29Ob3Jt
YWwiPlRFQVAtUFJGIChzZWNyZXQsIGtleSBsYWJlbCwgb3B0aW9uYWwgZGF0YSwgbGVuZ3RoKSA9
IFRMUy1QUkYoc2VjcmV0LCBrZXkgbGFiZWwgfCAweDAwIHwgb3B0aW9uYWwgZGF0YSwgbGVuZ3Ro
KTxvOnA+PC9vOnA+PC9wPg0KPC9kaXY+DQo8ZGl2Pg0KPHAgY2xhc3M9Ik1zb05vcm1hbCI+d2hl
cmUgYSBzaW5nbGUgYnl0ZSAweDAwIGlzIHVzZWQgZm9yIG5vIG9wdGlvbmFsIGRhdGEsIGxlbmd0
aCBpcyBhIDItb2N0ZXQgdW5zaWduZWQgaW50ZWdlciBpbiBuZXR3b3JrIGJ5dGUgb3JkZXIuPG86
cD48L286cD48L3A+DQo8L2Rpdj4NCjxkaXY+DQo8cCBjbGFzcz0iTXNvTm9ybWFsIj48bzpwPiZu
YnNwOzwvbzpwPjwvcD4NCjwvZGl2Pg0KPGRpdj4NCjxwIGNsYXNzPSJNc29Ob3JtYWwiPlRoZW46
PG86cD48L286cD48L3A+DQo8L2Rpdj4NCjxkaXY+DQo8cCBjbGFzcz0iTXNvTm9ybWFsIj5JTVNL
ID0gRmlyc3QgMzIgb2N0ZXRzIG9mIFRFQVAtUFJGKEVNU0ssICZxdW90OzxhIGhyZWY9Im1haWx0
bzpURUFQYmluZGtleUBpZXRmLm9yZyI+VEVBUGJpbmRrZXlAaWV0Zi5vcmc8L2E+JnF1b3Q7LCA2
NCkgPSBUTFMtUFJGKEVNU0ssICZxdW90OzxhIGhyZWY9Im1haWx0bzpURUFQYmluZGtleUBpZXRm
Lm9yZyI+VEVBUGJpbmRrZXlAaWV0Zi5vcmc8L2E+JnF1b3Q7IHwgMHgwMCB8IDB4MDAgfCAweDAw
IHwgMHg0MCk8YnI+DQpJTUNLW2pdID0gVEVBUC1QUkYoUy1JTUNLW2otMV0sICZxdW90O0lubmVy
IE1ldGhvZHMgQ29tcG91bmQgS2V5cyZxdW90OywgSU1TS1tqXSwgNjApID0gVExTLVBSRihTLUlN
Q0tbai0xXSwgJnF1b3Q7SW5uZXIgTWV0aG9kcyBDb21wb3VuZCBLZXlzJnF1b3Q7IHwgMHgwMCB8
IElNU0tbal0gfCAweDAwIHwgMHgzQyk8YnI+DQpNU0sgPSBURUFQLVBSRihTLUlNQ0tbal0sICZx
dW90O1Nlc3Npb24gS2V5IEdlbmVyYXRpbmcgRnVuY3Rpb27igJ0sIDY0KSA9IFRMUy1QUkYoUy1J
TUNLW2pdLCAmcXVvdDtTZXNzaW9uIEtleSBHZW5lcmF0aW5nIEZ1bmN0aW9uJnF1b3Q7IHwgMHgw
MCB8IDB4MDAgfCAweDAwIHwgMHg0MCk8YnI+DQpFTVNLID0gVEVBUC1QUkYoUy1JTUNLW2pdLCDi
gJ1FeHRlbmRlZCBTZXNzaW9uIEtleSBHZW5lcmF0aW5nIEZ1bmN0aW9u4oCdLCA2NCkgPSBUTFMt
UFJGKFMtSU1DS1tqXSwgJnF1b3Q7RXh0ZW5kZWQgU2Vzc2lvbiBLZXkgR2VuZXJhdGluZyBGdW5j
dGlvbiZxdW90OyB8IDB4MDAgfCAweDAwIHwgMHgwMCB8IDB4NDApPG86cD48L286cD48L3A+DQo8
L2Rpdj4NCjxkaXY+DQo8cCBjbGFzcz0iTXNvTm9ybWFsIj48bzpwPiZuYnNwOzwvbzpwPjwvcD4N
CjwvZGl2Pg0KPGRpdj4NCjxwIGNsYXNzPSJNc29Ob3JtYWwiPlRoaXMgbWF5IGNoYW5nZSB0aGUg
ZXhpc3RpbmcgaW1wbGVtZW50YXRpb24gYnV0IHdpbGwgbWFrZSBpdCBtb3JlIGNsZWFyIC0gbmVl
ZCB0byBjcmVhdGUgYW5kIGNhbGwganVzdCBvbmUgS0RGIGZ1bmN0aW9uLjxvOnA+PC9vOnA+PC9w
Pg0KPC9kaXY+DQo8ZGl2Pg0KPHAgY2xhc3M9Ik1zb05vcm1hbCI+PG86cD4mbmJzcDs8L286cD48
L3A+DQo8L2Rpdj4NCjxkaXY+DQo8cCBjbGFzcz0iTXNvTm9ybWFsIj5XZSBjYW4gcmVtb3ZlJm5i
c3A7MHgwMCB0aGF0IGNvbWVzIGFmdGVyIHRoZSBrZXkgbGFiZWwgLSB3aGlsZSBpdCBpcyByZXF1
aXJlZCBieSZuYnNwO1JGQyA1Mjk1LiBCdXQgdGhlcmUmbmJzcDt0aGUga2V5IGxhYmVsIGlzIGFs
c28gQVNDSUkgcHJpbnRhYmxlIHN0cmluZy4gSm9lLCBkbyB5b3UgcmVtZW1iZXIgd2hhdCB3YXMg
dGhlIG1vdGl2YXRpb24gdG8gcHV0IDB4MDAgYWZ0ZXIgdGhlIGtleSBsYWJlbCBwYXJhbWV0ZXI/
PG86cD48L286cD48L3A+DQo8L2Rpdj4NCjxkaXY+DQo8cCBjbGFzcz0iTXNvTm9ybWFsIj48bzpw
PiZuYnNwOzwvbzpwPjwvcD4NCjwvZGl2Pg0KPGRpdj4NCjxwIGNsYXNzPSJNc29Ob3JtYWwiPk9s
ZWc8bzpwPjwvbzpwPjwvcD4NCjwvZGl2Pg0KPGRpdj4NCjxwIGNsYXNzPSJNc29Ob3JtYWwiPjxv
OnA+Jm5ic3A7PC9vOnA+PC9wPg0KPC9kaXY+DQo8ZGl2Pg0KPHAgY2xhc3M9Ik1zb05vcm1hbCI+
PG86cD4mbmJzcDs8L286cD48L3A+DQo8L2Rpdj4NCjxkaXY+DQo8ZGl2Pg0KPHAgY2xhc3M9Ik1z
b05vcm1hbCI+T24gVGh1LCBPY3QgMjIsIDIwMjAgYXQgMjo1NCBBTSBKb3NlcGggU2Fsb3dleSAm
bHQ7PGEgaHJlZj0ibWFpbHRvOmpvZUBzYWxvd2V5Lm5ldCI+am9lQHNhbG93ZXkubmV0PC9hPiZn
dDsgd3JvdGU6PG86cD48L286cD48L3A+DQo8L2Rpdj4NCjxibG9ja3F1b3RlIHN0eWxlPSJib3Jk
ZXI6bm9uZTtib3JkZXItbGVmdDpzb2xpZCAjQ0NDQ0NDIDEuMHB0O3BhZGRpbmc6MGluIDBpbiAw
aW4gNi4wcHQ7bWFyZ2luLWxlZnQ6NC44cHQ7bWFyZ2luLXJpZ2h0OjBpbiI+DQo8ZGl2Pg0KPGRp
dj4NCjxwIGNsYXNzPSJNc29Ob3JtYWwiPihJIGFjY2lkZW50YWxseSZuYnNwO2Ryb3BwZWQgdGhp
cyBsaXN0IGZyb20gdGhlIGNvbnZlcnNhdGlvbik8bzpwPjwvbzpwPjwvcD4NCjwvZGl2Pg0KPHAg
Y2xhc3M9Ik1zb05vcm1hbCI+PG86cD4mbmJzcDs8L286cD48L3A+DQo8ZGl2Pg0KPGRpdj4NCjxw
IGNsYXNzPSJNc29Ob3JtYWwiPk9uIFdlZCwgT2N0IDIxLCAyMDIwIGF0IDQ6NDggUE0gSm9yZ2Ug
VmVyZ2FyYSAmbHQ7PGEgaHJlZj0ibWFpbHRvOmpvdmVyZ2FyQG1pY3Jvc29mdC5jb20iIHRhcmdl
dD0iX2JsYW5rIj5qb3ZlcmdhckBtaWNyb3NvZnQuY29tPC9hPiZndDsgd3JvdGU6PG86cD48L286
cD48L3A+DQo8L2Rpdj4NCjxibG9ja3F1b3RlIHN0eWxlPSJib3JkZXI6bm9uZTtib3JkZXItbGVm
dDpzb2xpZCAjQ0NDQ0NDIDEuMHB0O3BhZGRpbmc6MGluIDBpbiAwaW4gNi4wcHQ7bWFyZ2luLWxl
ZnQ6NC44cHQ7bWFyZ2luLXJpZ2h0OjBpbiI+DQo8ZGl2Pg0KPGRpdj4NCjxwIGNsYXNzPSJNc29O
b3JtYWwiIHN0eWxlPSJtc28tbWFyZ2luLXRvcC1hbHQ6YXV0bzttc28tbWFyZ2luLWJvdHRvbS1h
bHQ6YXV0byI+Jmd0O1tKb2VdIFllcyB0aGlzIGlzIGEgY29uY2VybiBhbmQgSSB0aGluayB5b3Vy
Jm5ic3A7aW50ZXJwcmV0YXRpb24gb2YgdGhlIGN1cnJlbnQgZG9jdW1lbnQgaXMgYWxzbyB2YWxp
ZC4mbmJzcDsgVGhlcmUgbWF5IGJlIG1vcmUgdGhhbiBvbmUgaW1wbGVtZW50YXRpb24uJm5ic3A7
IFNvIHdoYXQgeW91IGltcGxlbWVudGVkIHdhczo8bzpwPjwvbzpwPjwvcD4NCjxwIGNsYXNzPSJN
c29Ob3JtYWwiIHN0eWxlPSJtc28tbWFyZ2luLXRvcC1hbHQ6YXV0bzttc28tbWFyZ2luLWJvdHRv
bS1hbHQ6YXV0byI+Jmd0OyZuYnNwOzxvOnA+PC9vOnA+PC9wPg0KPHAgY2xhc3M9Ik1zb05vcm1h
bCIgc3R5bGU9Im1zby1tYXJnaW4tdG9wLWFsdDphdXRvO21zby1tYXJnaW4tYm90dG9tLWFsdDph
dXRvIj4mZ3Q7SU1DS1tqXSA9IFRMUy1QUkYoUy1JTUNLW2otMV0sICZxdW90O0lubmVyIE1ldGhv
ZHMgQ29tcG91bmQgS2V5cyZxdW90OywmbmJzcDs8c3BhbiBzdHlsZT0iZm9udC1zaXplOjEwLjVw
dDtjb2xvcjojMkM0MzUzIj5JTVNLW2pdKSA9IFBfJmx0O2hhc2gmZ3Q7KFMtSU1DS1tqLTFdLCAm
cXVvdDtJbm5lciBNZXRob2RzIENvbXBvdW5kIEtleXMmcXVvdDsgfCBJTVNLW2pdKTwvc3Bhbj48
bzpwPjwvbzpwPjwvcD4NCjxwIGNsYXNzPSJNc29Ob3JtYWwiIHN0eWxlPSJtc28tbWFyZ2luLXRv
cC1hbHQ6YXV0bzttc28tbWFyZ2luLWJvdHRvbS1hbHQ6YXV0byI+Jm5ic3A7PG86cD48L286cD48
L3A+DQo8cCBjbGFzcz0iTXNvTm9ybWFsIiBzdHlsZT0ibXNvLW1hcmdpbi10b3AtYWx0OmF1dG87
bXNvLW1hcmdpbi1ib3R0b20tYWx0OmF1dG8iPlllcywgdGhpcyBpcyB3aGF0IEkgaW1wbGVtZW50
ZWQuIEFzIHlvdSBtZW50aW9uZWQsIHRoZXJlIGFyZSBtdWx0aXBsZSBwb3NzaWJsZSBpbnRlcnBy
ZXRhdGlvbnMgb2YgdGhpcyBzaW5jZSB0aGUgVEVBUCB1c2FnZSBpcyBpbmNvcnJlY3QuIEhvd2V2
ZXIsIG15IGltcGxlbWVudGF0aW9uIGRvZXMgaW50ZXJvcA0KIHdpdGggYXQgbGVhc3QgMiBsYXJn
ZSB2ZW5kb3IgaW1wbGVtZW50YXRpb25zLiBJZiB0aGUgaW1wbGVtZW50YXRpb25zIHdlcmUgdXNp
bmcgZGlmZmVyZW50IGNhbGN1bGF0aW9ucyBoZXJlLCB0aGUgV2ktRmkvRXRoZXJuZXQgY29ubmVj
dGlvbnMgdGhhdCBkZXBlbmQgb24gdGhlIE1TSyB3b3VsZCBmYWlsLiBCdXQgc2luY2UgY29ubmVj
dGlvbnMgd29yaywgSSBjYW4gYXNzdW1lIHdlIGFyZSBhbGwgdXNpbmcgdGhlIHNhbWUgaW1wbGVt
ZW50YXRpb24NCiBhbmQgYXJyaXZpbmcgYXQgdGhlIHNhbWUgTVNLLiBDaXNjbyBpcyBvbmUgb2Yg
dGhlIGltcGxlbWVudGF0aW9ucyB0aGF0IEkgaGF2ZSB0ZXN0ZWQgYWdhaW5zdCB3aGljaCBpcyB3
aHkgSSB3YXMgaG9waW5nIE9sZWcgbWF5IG9mZmVyIG1vcmUgY29udGV4dCBhcyB0byB3aGF0IGhl
IGhhcyBzZWVuLjxvOnA+PC9vOnA+PC9wPg0KPHAgY2xhc3M9Ik1zb05vcm1hbCIgc3R5bGU9Im1z
by1tYXJnaW4tdG9wLWFsdDphdXRvO21zby1tYXJnaW4tYm90dG9tLWFsdDphdXRvIj4mbmJzcDs8
bzpwPjwvbzpwPjwvcD4NCjwvZGl2Pg0KPC9kaXY+DQo8L2Jsb2NrcXVvdGU+DQo8ZGl2Pg0KPHAg
Y2xhc3M9Ik1zb05vcm1hbCI+W0pvZV0gSSBjYW4gaG9wZSBKb3VuaSBjYW4gY2hpbWUgaW4gb24g
dGhpcyBhcyB3ZWxsLiZuYnNwOyBJIHRoaW5rIHRoZSBvcmlnaW5hbCBpbnRlbnQgd2FzIHRvIG5v
dCBpbmNsdWRlIHRoZSBsZW5ndGggYXMgaXMgeW91ciBzdWdnZXN0aW9uLiZuYnNwOzxvOnA+PC9v
OnA+PC9wPg0KPC9kaXY+DQo8ZGl2Pg0KPHAgY2xhc3M9Ik1zb05vcm1hbCI+PG86cD4mbmJzcDs8
L286cD48L3A+DQo8L2Rpdj4NCjxkaXY+DQo8cCBjbGFzcz0iTXNvTm9ybWFsIj4mbmJzcDs8bzpw
PjwvbzpwPjwvcD4NCjwvZGl2Pg0KPGJsb2NrcXVvdGUgc3R5bGU9ImJvcmRlcjpub25lO2JvcmRl
ci1sZWZ0OnNvbGlkICNDQ0NDQ0MgMS4wcHQ7cGFkZGluZzowaW4gMGluIDBpbiA2LjBwdDttYXJn
aW4tbGVmdDo0LjhwdDttYXJnaW4tcmlnaHQ6MGluIj4NCjxkaXY+DQo8ZGl2Pg0KPHAgY2xhc3M9
Ik1zb05vcm1hbCIgc3R5bGU9Im1zby1tYXJnaW4tdG9wLWFsdDphdXRvO21zby1tYXJnaW4tYm90
dG9tLWFsdDphdXRvIj4mZ3Q7W0pvZV08c3BhbiBzdHlsZT0iZm9udC1zaXplOjEwLjVwdDtjb2xv
cjojMkM0MzUzIj4gRG9lcyB0aGUgcmV2aXNpb24gaW4gNTE2NyBtYXRjaCB5b3UgaW1wbGVtZW50
YXRpb24gKCBJIGRvbid0IHRoaW5rIEpvdW5pJ3MmbmJzcDtjb21tZW50IGNoYW5nZXMgdGhlIHVu
ZGVybHkmbmJzcDtjYWxjdWxhdGlvbiwganVzdCBpdHMNCiByZXByZXNlbnRhdGlvbik/Jm5ic3A7
PC9zcGFuPjxvOnA+PC9vOnA+PC9wPg0KPHAgY2xhc3M9Ik1zb05vcm1hbCIgc3R5bGU9Im1zby1t
YXJnaW4tdG9wLWFsdDphdXRvO21zby1tYXJnaW4tYm90dG9tLWFsdDphdXRvIj4mbmJzcDs8bzpw
PjwvbzpwPjwvcD4NCjxwIGNsYXNzPSJNc29Ob3JtYWwiIHN0eWxlPSJtc28tbWFyZ2luLXRvcC1h
bHQ6YXV0bzttc28tbWFyZ2luLWJvdHRvbS1hbHQ6YXV0byI+SSBoYXZlIG5vdCBpbXBsZW1lbnRl
ZCB0aGlzIHBvcnRpb24gb2YgdGhlIFJGQyBhcyBJIGZvdW5kIGl0IHRvbyB1bmNsZWFyIHRvIHdv
cmsgd2l0aC4gVGh1cyBJIGNhbuKAmXQgY29tbWVudCBvbiB3aGF0IGltcGxlbWVudGF0aW9ucyBt
YXkgYmUgZG9pbmcuIEhvd2V2ZXIsIEkgYWdyZWUgd2l0aCB0aGUgY3VycmVudA0KIHJldmlzaW9u
IGluIDUxNjcgYXMgdGhlIG1vc3QgbmF0dXJhbCBpbnRlcnByZXRhdGlvbi4gSWYgb3RoZXJzIGhh
dmUgaW1wbGVtZW50ZWQgdGhpcyBwb3J0aW9uIG9mIHRoZSBSRkMgdGhlbiBjZXJ0YWlubHkgdGhl
aXIgY29tbWVudHMgd291bGQgYmUgd2VsY29tZS48bzpwPjwvbzpwPjwvcD4NCjxwIGNsYXNzPSJN
c29Ob3JtYWwiIHN0eWxlPSJtc28tbWFyZ2luLXRvcC1hbHQ6YXV0bzttc28tbWFyZ2luLWJvdHRv
bS1hbHQ6YXV0byI+PG86cD4mbmJzcDs8L286cD48L3A+DQo8L2Rpdj4NCjwvZGl2Pg0KPC9ibG9j
a3F1b3RlPg0KPGJsb2NrcXVvdGUgc3R5bGU9ImJvcmRlcjpub25lO2JvcmRlci1sZWZ0OnNvbGlk
ICNDQ0NDQ0MgMS4wcHQ7cGFkZGluZzowaW4gMGluIDBpbiA2LjBwdDttYXJnaW4tbGVmdDo0Ljhw
dDttYXJnaW4tcmlnaHQ6MGluIj4NCjxkaXY+DQo8ZGl2Pg0KPHAgY2xhc3M9Ik1zb05vcm1hbCIg
c3R5bGU9Im1zby1tYXJnaW4tdG9wLWFsdDphdXRvO21zby1tYXJnaW4tYm90dG9tLWFsdDphdXRv
Ij5CeSB0aGUgd2F5LCB3ZeKAmXZlIGRyb3BwZWQgdGhlIEVNVSBncm91cCBvbiBvdXIgcmVwbGll
cyBoZXJlIOKAkyBub3Qgc3VyZSBpZiBpbnRlbnRpb25hbCBvciBub3QuPG86cD48L286cD48L3A+
DQo8cCBjbGFzcz0iTXNvTm9ybWFsIiBzdHlsZT0ibXNvLW1hcmdpbi10b3AtYWx0OmF1dG87bXNv
LW1hcmdpbi1ib3R0b20tYWx0OmF1dG8iPiZuYnNwOzxvOnA+PC9vOnA+PC9wPg0KPHAgY2xhc3M9
Ik1zb05vcm1hbCIgc3R5bGU9Im1zby1tYXJnaW4tdG9wLWFsdDphdXRvO21zby1tYXJnaW4tYm90
dG9tLWFsdDphdXRvIj5Kb3JnZSBWZXJnYXJhPG86cD48L286cD48L3A+DQo8cCBjbGFzcz0iTXNv
Tm9ybWFsIiBzdHlsZT0ibXNvLW1hcmdpbi10b3AtYWx0OmF1dG87bXNvLW1hcmdpbi1ib3R0b20t
YWx0OmF1dG8iPiZuYnNwOzxvOnA+PC9vOnA+PC9wPg0KPGRpdiBzdHlsZT0iYm9yZGVyOm5vbmU7
Ym9yZGVyLXRvcDpzb2xpZCAjRTFFMUUxIDEuMHB0O3BhZGRpbmc6My4wcHQgMGluIDBpbiAwaW4i
Pg0KPHAgY2xhc3M9Ik1zb05vcm1hbCIgc3R5bGU9Im1zby1tYXJnaW4tdG9wLWFsdDphdXRvO21z
by1tYXJnaW4tYm90dG9tLWFsdDphdXRvIj48Yj5Gcm9tOjwvYj4gSm9zZXBoIFNhbG93ZXkgJmx0
OzxhIGhyZWY9Im1haWx0bzpqb2VAc2Fsb3dleS5uZXQiIHRhcmdldD0iX2JsYW5rIj5qb2VAc2Fs
b3dleS5uZXQ8L2E+Jmd0Ow0KPGJyPg0KPGI+U2VudDo8L2I+IFdlZG5lc2RheSwgT2N0b2JlciAy
MSwgMjAyMCA0OjM2IFBNPGJyPg0KPGI+VG86PC9iPiBKb3JnZSBWZXJnYXJhICZsdDs8YSBocmVm
PSJtYWlsdG86am92ZXJnYXJAbWljcm9zb2Z0LmNvbSIgdGFyZ2V0PSJfYmxhbmsiPmpvdmVyZ2Fy
QG1pY3Jvc29mdC5jb208L2E+Jmd0Ozxicj4NCjxiPlN1YmplY3Q6PC9iPiBSZTogUHJvcG9zZWQg
cmVzb2x1dGlvbiBmb3IgVEVBUCBlcnJhdGEgZm9yIDUxMjg8bzpwPjwvbzpwPjwvcD4NCjwvZGl2
Pg0KPHAgY2xhc3M9Ik1zb05vcm1hbCIgc3R5bGU9Im1zby1tYXJnaW4tdG9wLWFsdDphdXRvO21z
by1tYXJnaW4tYm90dG9tLWFsdDphdXRvIj4mbmJzcDs8bzpwPjwvbzpwPjwvcD4NCjxkaXY+DQo8
ZGl2Pg0KPHAgY2xhc3M9Ik1zb05vcm1hbCIgc3R5bGU9Im1zby1tYXJnaW4tdG9wLWFsdDphdXRv
O21zby1tYXJnaW4tYm90dG9tLWFsdDphdXRvIj4mbmJzcDs8bzpwPjwvbzpwPjwvcD4NCjwvZGl2
Pg0KPHAgY2xhc3M9Ik1zb05vcm1hbCIgc3R5bGU9Im1zby1tYXJnaW4tdG9wLWFsdDphdXRvO21z
by1tYXJnaW4tYm90dG9tLWFsdDphdXRvIj4mbmJzcDs8bzpwPjwvbzpwPjwvcD4NCjxkaXY+DQo8
ZGl2Pg0KPHAgY2xhc3M9Ik1zb05vcm1hbCIgc3R5bGU9Im1zby1tYXJnaW4tdG9wLWFsdDphdXRv
O21zby1tYXJnaW4tYm90dG9tLWFsdDphdXRvIj5PbiBXZWQsIE9jdCAyMSwgMjAyMCBhdCAzOjIw
IFBNIEpvcmdlIFZlcmdhcmEgJmx0OzxhIGhyZWY9Im1haWx0bzpqb3ZlcmdhckBtaWNyb3NvZnQu
Y29tIiB0YXJnZXQ9Il9ibGFuayI+am92ZXJnYXJAbWljcm9zb2Z0LmNvbTwvYT4mZ3Q7IHdyb3Rl
OjxvOnA+PC9vOnA+PC9wPg0KPC9kaXY+DQo8YmxvY2txdW90ZSBzdHlsZT0iYm9yZGVyOm5vbmU7
Ym9yZGVyLWxlZnQ6c29saWQgI0NDQ0NDQyAxLjBwdDtwYWRkaW5nOjBpbiAwaW4gMGluIDYuMHB0
O21hcmdpbi1sZWZ0OjQuOHB0O21hcmdpbi10b3A6NS4wcHQ7bWFyZ2luLXJpZ2h0OjBpbjttYXJn
aW4tYm90dG9tOjUuMHB0Ij4NCjxkaXY+DQo8ZGl2Pg0KPHAgY2xhc3M9Ik1zb05vcm1hbCIgc3R5
bGU9Im1zby1tYXJnaW4tdG9wLWFsdDphdXRvO21zby1tYXJnaW4tYm90dG9tLWFsdDphdXRvIj5J
biB0aGVvcnkgSSBhZ3JlZSB0aGlzIGlzIGEgcG9zc2libGUgcmVzb2x1dGlvbi4gSG93ZXZlciwg
dGhpcyBkb2VzbuKAmXQgbWF0Y2ggYW55IG9mIHRoZSBjdXJyZW50IFRFQVAgaW1wbGVtZW50YXRp
b25zIHRoYXQgSSBhbSBhd2FyZSBvZi4gUGVyaGFwcyBPbGVnIGNhbiB3ZWlnaCBpbiBhcyB3ZWxs
IGluIHRlcm1zDQogb2Ygd2hhdCBoZeKAmXMgc2Vlbi48bzpwPjwvbzpwPjwvcD4NCjxwIGNsYXNz
PSJNc29Ob3JtYWwiIHN0eWxlPSJtc28tbWFyZ2luLXRvcC1hbHQ6YXV0bzttc28tbWFyZ2luLWJv
dHRvbS1hbHQ6YXV0byI+Jm5ic3A7PG86cD48L286cD48L3A+DQo8cCBjbGFzcz0iTXNvTm9ybWFs
IiBzdHlsZT0ibXNvLW1hcmdpbi10b3AtYWx0OmF1dG87bXNvLW1hcmdpbi1ib3R0b20tYWx0OmF1
dG8iPkkgYmVsaWV2ZSBhbGwgY3VycmVudCBpbXBsZW1lbnRhdGlvbnMgdHJlYXQgNjAgYXMgdGhl
IGRlc2lyZWQgb3V0cHV0IGxlbmd0aCB3aXRob3V0IHRyZWF0aW5nIGFzIGEgc2VlZC4gSW4gdGVy
bXMgb2YgUF8mbHQ7aGFzaCZndDssIHRoaXMgbWVhbnMgaW1wbGVtZW50YXRpb25zIGFyZSBwZXJm
b3JtaW5nIHRoZSBjYWxjdWxhdGlvbg0KIHdpdGhvdXQgYSBzZWVkLjxvOnA+PC9vOnA+PC9wPg0K
PHAgY2xhc3M9Ik1zb05vcm1hbCIgc3R5bGU9Im1zby1tYXJnaW4tdG9wLWFsdDphdXRvO21zby1t
YXJnaW4tYm90dG9tLWFsdDphdXRvIj4mbmJzcDs8bzpwPjwvbzpwPjwvcD4NCjxwIGNsYXNzPSJN
c29Ob3JtYWwiIHN0eWxlPSJtc28tbWFyZ2luLXRvcC1hbHQ6YXV0bzttc28tbWFyZ2luLWJvdHRv
bS1hbHQ6YXV0byI+UkZDIDUyNDYgZGVmaW5lcyB0aGUgVExTIDEuMiBQUkYgYXM6PG86cD48L286
cD48L3A+DQo8cCBjbGFzcz0iTXNvTm9ybWFsIiBzdHlsZT0ibXNvLW1hcmdpbi10b3AtYWx0OmF1
dG87bXNvLW1hcmdpbi1ib3R0b20tYWx0OmF1dG8iPlBSRihzZWNyZXQsIGxhYmVsLCBzZWVkKSA9
IFBfJmx0O2hhc2gmZ3Q7KHNlY3JldCwgbGFiZWwgKyBzZWVkKTxvOnA+PC9vOnA+PC9wPg0KPHAg
Y2xhc3M9Ik1zb05vcm1hbCIgc3R5bGU9Im1zby1tYXJnaW4tdG9wLWFsdDphdXRvO21zby1tYXJn
aW4tYm90dG9tLWFsdDphdXRvIj4mbmJzcDs8bzpwPjwvbzpwPjwvcD4NCjxwIGNsYXNzPSJNc29O
b3JtYWwiIHN0eWxlPSJtc28tbWFyZ2luLXRvcC1hbHQ6YXV0bzttc28tbWFyZ2luLWJvdHRvbS1h
bHQ6YXV0byI+U28gdGhlIGNhbGN1bGF0aW9uIGltcGxlbWVudGF0aW9ucyBhcmUgY3VycmVudGx5
IHBlcmZvcm1pbmcgd2l0aCBhbiBlbXB0eSBzZWVkIGVuZHMgdXAgYXM6PG86cD48L286cD48L3A+
DQo8cCBjbGFzcz0iTXNvTm9ybWFsIiBzdHlsZT0ibXNvLW1hcmdpbi10b3AtYWx0OmF1dG87bXNv
LW1hcmdpbi1ib3R0b20tYWx0OmF1dG8iPlBfJmx0O2hhc2gmZ3Q7KHNlY3JldCwgbGFiZWwpPG86
cD48L286cD48L3A+DQo8cCBjbGFzcz0iTXNvTm9ybWFsIiBzdHlsZT0ibXNvLW1hcmdpbi10b3At
YWx0OmF1dG87bXNvLW1hcmdpbi1ib3R0b20tYWx0OmF1dG8iPiZuYnNwOzxvOnA+PC9vOnA+PC9w
Pg0KPHAgY2xhc3M9Ik1zb05vcm1hbCIgc3R5bGU9Im1zby1tYXJnaW4tdG9wLWFsdDphdXRvO21z
by1tYXJnaW4tYm90dG9tLWFsdDphdXRvIj5Ob3RlIHRoYXQgaW4gUkZDIDUyOTUsIHRoZSBsZW5n
dGggKmlzKiBleHBsaWNpdGx5IG1lbnRpb25lZCBhcyBiZWluZyBjb25jYXRlbmF0ZWQgd2l0aCB0
aGUgbGFiZWw8bzpwPjwvbzpwPjwvcD4NCjxwIGNsYXNzPSJNc29Ob3JtYWwiIHN0eWxlPSJtc28t
bWFyZ2luLXRvcC1hbHQ6YXV0bzttc28tbWFyZ2luLWJvdHRvbS1hbHQ6YXV0byI+VVNSSyA9IEtE
RihFTVNLLCBrZXkgbGFiZWwgfCAmcXVvdDtcMCZxdW90OyB8IG9wdGlvbmFsIGRhdGEgfCBsZW5n
dGgpPG86cD48L286cD48L3A+DQo8cCBjbGFzcz0iTXNvTm9ybWFsIiBzdHlsZT0ibXNvLW1hcmdp
bi10b3AtYWx0OmF1dG87bXNvLW1hcmdpbi1ib3R0b20tYWx0OmF1dG8iPiZuYnNwOzxvOnA+PC9v
OnA+PC9wPg0KPHAgY2xhc3M9Ik1zb05vcm1hbCIgc3R5bGU9Im1zby1tYXJnaW4tdG9wLWFsdDph
dXRvO21zby1tYXJnaW4tYm90dG9tLWFsdDphdXRvIj5SRkMgNTI5NSBpcyBtZW50aW9uZWQgZWFy
bGllciBpbiB0aGUgVEVBUCBSRkMsIGluIHRoZSBzZWN0aW9uIGNvdmVyZWQgYnkgZXJyYXRhIDUx
MjcuICpIb3dldmVyKiBpdCBpcyBub3QgbWVudGlvbmVkIGluIHRoaXMgcG9ydGlvbiBvZiB0aGUg
UkZDLiBTaW5jZSB0aGlzIGNhbGN1bGF0aW9uIGlzIG5vdCBvbg0KIGFuIEVNU0ssIEkgZG8gbm90
IGJlbGlldmUgUkZDIDIzOTUgYXBwbGllcyBhbmQgdGhpcyBpcyBsaWtlbHkgd2h5IGltcGxlbWVu
dGF0aW9ucyB3ZW50IHdpdGggdGhlIHNlZWRsZXNzIFBfJmx0O2hhc2gmZ3Q7KHNlY3JldCwgbGFi
ZWwpIGNhbGN1bGF0aW9uIGluc3RlYWQuPG86cD48L286cD48L3A+DQo8cCBjbGFzcz0iTXNvTm9y
bWFsIiBzdHlsZT0ibXNvLW1hcmdpbi10b3AtYWx0OmF1dG87bXNvLW1hcmdpbi1ib3R0b20tYWx0
OmF1dG8iPiZuYnNwOzxvOnA+PC9vOnA+PC9wPg0KPHAgY2xhc3M9Ik1zb05vcm1hbCIgc3R5bGU9
Im1zby1tYXJnaW4tdG9wLWFsdDphdXRvO21zby1tYXJnaW4tYm90dG9tLWFsdDphdXRvIj5JcyB0
aGVyZSBjb25jZXJuIGFib3V0IHVwZGF0aW5nIHRoZSBSRkMgaW4gYSB3YXkgdGhhdCBicmVha3Mg
ZXhpc3RpbmcgaW1wbGVtZW50YXRpb25zPzxvOnA+PC9vOnA+PC9wPg0KPHAgY2xhc3M9Ik1zb05v
cm1hbCIgc3R5bGU9Im1zby1tYXJnaW4tdG9wLWFsdDphdXRvO21zby1tYXJnaW4tYm90dG9tLWFs
dDphdXRvIj4mbmJzcDs8bzpwPjwvbzpwPjwvcD4NCjwvZGl2Pg0KPC9kaXY+DQo8L2Jsb2NrcXVv
dGU+DQo8ZGl2Pg0KPHAgY2xhc3M9Ik1zb05vcm1hbCIgc3R5bGU9Im1zby1tYXJnaW4tdG9wLWFs
dDphdXRvO21zby1tYXJnaW4tYm90dG9tLWFsdDphdXRvIj5bSm9lXSBZZXMgdGhpcyBpcyBhIGNv
bmNlcm4gYW5kIEkgdGhpbmsgeW91ciZuYnNwO2ludGVycHJldGF0aW9uIG9mIHRoZSBjdXJyZW50
IGRvY3VtZW50IGlzIGFsc28gdmFsaWQuJm5ic3A7IFRoZXJlIG1heSBiZSBtb3JlIHRoYW4gb25l
IGltcGxlbWVudGF0aW9uLiZuYnNwOyBTbyB3aGF0IHlvdSBpbXBsZW1lbnRlZCB3YXM6PG86cD48
L286cD48L3A+DQo8L2Rpdj4NCjxkaXY+DQo8cCBjbGFzcz0iTXNvTm9ybWFsIiBzdHlsZT0ibXNv
LW1hcmdpbi10b3AtYWx0OmF1dG87bXNvLW1hcmdpbi1ib3R0b20tYWx0OmF1dG8iPiZuYnNwOzxv
OnA+PC9vOnA+PC9wPg0KPC9kaXY+DQo8ZGl2Pg0KPHAgY2xhc3M9Ik1zb05vcm1hbCIgc3R5bGU9
Im1zby1tYXJnaW4tdG9wLWFsdDphdXRvO21zby1tYXJnaW4tYm90dG9tLWFsdDphdXRvIj5JTUNL
W2pdID0gVExTLVBSRihTLUlNQ0tbai0xXSwgJnF1b3Q7SW5uZXIgTWV0aG9kcyBDb21wb3VuZCBL
ZXlzJnF1b3Q7LCZuYnNwOzxzcGFuIHN0eWxlPSJmb250LXNpemU6MTAuNXB0O2NvbG9yOiMyQzQz
NTMiPklNU0tbal0pID0gUF8mbHQ7aGFzaCZndDsoUy1JTUNLW2otMV0sICZxdW90O0lubmVyIE1l
dGhvZHMgQ29tcG91bmQgS2V5cyZxdW90OyB8IElNU0tbal0pPC9zcGFuPjxvOnA+PC9vOnA+PC9w
Pg0KPC9kaXY+DQo8ZGl2Pg0KPHAgY2xhc3M9Ik1zb05vcm1hbCIgc3R5bGU9Im1zby1tYXJnaW4t
dG9wLWFsdDphdXRvO21zby1tYXJnaW4tYm90dG9tLWFsdDphdXRvIj4mbmJzcDs8bzpwPjwvbzpw
PjwvcD4NCjwvZGl2Pg0KPGRpdj4NCjxwIGNsYXNzPSJNc29Ob3JtYWwiIHN0eWxlPSJtc28tbWFy
Z2luLXRvcC1hbHQ6YXV0bzttc28tbWFyZ2luLWJvdHRvbS1hbHQ6YXV0byI+dGFrZW4gb3V0IHRv
IDYwIGJ5dGVzLiZuYnNwOyBUaGUgcHJvYmxlbSBpcyB0aGF0IHRoZSBURUFQIHNwZWMgcmVmZXJl
bmNlcyBhIFRMUy1QUkYgaW4gYSB3YXkgdGhhdCBpdCBkb2VzIG5vdCBkZWZpbmUuJm5ic3A7IEkg
dGhpbmsgdGhlIGVycmF0YSBwb2ludHMgb3V0IHRoZSBkZWZpbml0aW9uIHRoYXQgc2hvdWxkIGJl
IHVzZWQ6PG86cD48L286cD48L3A+DQo8L2Rpdj4NCjxkaXY+DQo8cCBjbGFzcz0iTXNvTm9ybWFs
IiBzdHlsZT0ibXNvLW1hcmdpbi10b3AtYWx0OmF1dG87bXNvLW1hcmdpbi1ib3R0b20tYWx0OmF1
dG8iPiZuYnNwOzxvOnA+PC9vOnA+PC9wPg0KPC9kaXY+DQo8ZGl2Pg0KPHAgY2xhc3M9Ik1zb05v
cm1hbCIgc3R5bGU9Im1zby1tYXJnaW4tdG9wLWFsdDphdXRvO21zby1tYXJnaW4tYm90dG9tLWFs
dDphdXRvIj5QUkYoc2VjcmV0LCBsYWJlbCwgc2VlZCkgPSBQXyZsdDtoYXNoJmd0OyhzZWNyZXQs
IGxhYmVsICsgc2VlZCk8bzpwPjwvbzpwPjwvcD4NCjwvZGl2Pg0KPGRpdj4NCjxwIGNsYXNzPSJN
c29Ob3JtYWwiIHN0eWxlPSJtc28tbWFyZ2luLXRvcC1hbHQ6YXV0bzttc28tbWFyZ2luLWJvdHRv
bS1hbHQ6YXV0byI+Jm5ic3A7PG86cD48L286cD48L3A+DQo8L2Rpdj4NCjxkaXY+DQo8cCBjbGFz
cz0iTXNvTm9ybWFsIiBzdHlsZT0ibXNvLW1hcmdpbi10b3AtYWx0OmF1dG87bXNvLW1hcmdpbi1i
b3R0b20tYWx0OmF1dG8iPlRoYXQgZG9lcyBub3QgaW5jbHVkZSBsZW5ndGggc28gdGhlIDYwIGlu
IHRoZSBvcmlnaW5hbCBkZWZpbml0aW9uJm5ic3A7aXMgYW1iaWd1b3VzLiZuYnNwOyAmbmJzcDtU
aGUgbmV3IHRleHQgd291bGQgdGhlbiBiZSBzb21ldGhpbmcgbGlrZTo8bzpwPjwvbzpwPjwvcD4N
CjwvZGl2Pg0KPGRpdj4NCjxwIGNsYXNzPSJNc29Ob3JtYWwiIHN0eWxlPSJtc28tbWFyZ2luLXRv
cC1hbHQ6YXV0bzttc28tbWFyZ2luLWJvdHRvbS1hbHQ6YXV0byI+Jm5ic3A7PG86cD48L286cD48
L3A+DQo8L2Rpdj4NCjxkaXY+DQo8cCBjbGFzcz0iTXNvTm9ybWFsIiBzdHlsZT0ibXNvLW1hcmdp
bi10b3AtYWx0OmF1dG87bXNvLW1hcmdpbi1ib3R0b20tYWx0OmF1dG8iPklNQ0tbal0gPSBUTFMt
UFJGKFMtSU1DS1tqLTFdLCAmcXVvdDtJbm5lciBNZXRob2RzIENvbXBvdW5kIEtleXMmcXVvdDss
Jm5ic3A7PHNwYW4gc3R5bGU9ImZvbnQtc2l6ZToxMC41cHQ7Y29sb3I6IzJDNDM1MyI+SU1TS1tq
XSkmbmJzcDsgdG8gZ2VuZXJhdGUgYSBsZW5ndGggb2YgNjAgYnl0ZXM8L3NwYW4+PG86cD48L286
cD48L3A+DQo8L2Rpdj4NCjxkaXY+DQo8cCBjbGFzcz0iTXNvTm9ybWFsIiBzdHlsZT0ibXNvLW1h
cmdpbi10b3AtYWx0OmF1dG87bXNvLW1hcmdpbi1ib3R0b20tYWx0OmF1dG8iPiZuYnNwOzxvOnA+
PC9vOnA+PC9wPg0KPC9kaXY+DQo8ZGl2Pg0KPHAgY2xhc3M9Ik1zb05vcm1hbCIgc3R5bGU9Im1z
by1tYXJnaW4tdG9wLWFsdDphdXRvO21zby1tYXJnaW4tYm90dG9tLWFsdDphdXRvIj48c3BhbiBz
dHlsZT0iZm9udC1zaXplOjEwLjVwdDtjb2xvcjojMkM0MzUzIj5Eb2VzIHRoZSByZXZpc2lvbiBp
biA1MTY3IG1hdGNoIHlvdSBpbXBsZW1lbnRhdGlvbiAoIEkgZG9uJ3QgdGhpbmsgSm91bmkncyZu
YnNwO2NvbW1lbnQgY2hhbmdlcyB0aGUgdW5kZXJseSZuYnNwO2NhbGN1bGF0aW9uLCBqdXN0IGl0
cyByZXByZXNlbnRhdGlvbik/Jm5ic3A7PC9zcGFuPjxvOnA+PC9vOnA+PC9wPg0KPC9kaXY+DQo8
ZGl2Pg0KPHAgY2xhc3M9Ik1zb05vcm1hbCIgc3R5bGU9Im1zby1tYXJnaW4tdG9wLWFsdDphdXRv
O21zby1tYXJnaW4tYm90dG9tLWFsdDphdXRvIj4mbmJzcDs8bzpwPjwvbzpwPjwvcD4NCjwvZGl2
Pg0KPGRpdj4NCjxwIGNsYXNzPSJNc29Ob3JtYWwiIHN0eWxlPSJtc28tbWFyZ2luLXRvcC1hbHQ6
YXV0bzttc28tbWFyZ2luLWJvdHRvbS1hbHQ6YXV0byI+Jm5ic3A7PG86cD48L286cD48L3A+DQo8
L2Rpdj4NCjxkaXY+DQo8cCBjbGFzcz0iTXNvTm9ybWFsIiBzdHlsZT0ibXNvLW1hcmdpbi10b3At
YWx0OmF1dG87bXNvLW1hcmdpbi1ib3R0b20tYWx0OmF1dG8iPiZuYnNwOzxvOnA+PC9vOnA+PC9w
Pg0KPC9kaXY+DQo8ZGl2Pg0KPHAgY2xhc3M9Ik1zb05vcm1hbCIgc3R5bGU9Im1zby1tYXJnaW4t
dG9wLWFsdDphdXRvO21zby1tYXJnaW4tYm90dG9tLWFsdDphdXRvIj4mbmJzcDs8bzpwPjwvbzpw
PjwvcD4NCjwvZGl2Pg0KPGRpdj4NCjxwIGNsYXNzPSJNc29Ob3JtYWwiIHN0eWxlPSJtc28tbWFy
Z2luLXRvcC1hbHQ6YXV0bzttc28tbWFyZ2luLWJvdHRvbS1hbHQ6YXV0byI+Jm5ic3A7PG86cD48
L286cD48L3A+DQo8L2Rpdj4NCjxibG9ja3F1b3RlIHN0eWxlPSJib3JkZXI6bm9uZTtib3JkZXIt
bGVmdDpzb2xpZCAjQ0NDQ0NDIDEuMHB0O3BhZGRpbmc6MGluIDBpbiAwaW4gNi4wcHQ7bWFyZ2lu
LWxlZnQ6NC44cHQ7bWFyZ2luLXRvcDo1LjBwdDttYXJnaW4tcmlnaHQ6MGluO21hcmdpbi1ib3R0
b206NS4wcHQiPg0KPGRpdj4NCjxkaXY+DQo8cCBjbGFzcz0iTXNvTm9ybWFsIiBzdHlsZT0ibXNv
LW1hcmdpbi10b3AtYWx0OmF1dG87bXNvLW1hcmdpbi1ib3R0b20tYWx0OmF1dG8iPkpvcmdlIFZl
cmdhcmE8bzpwPjwvbzpwPjwvcD4NCjxwIGNsYXNzPSJNc29Ob3JtYWwiIHN0eWxlPSJtc28tbWFy
Z2luLXRvcC1hbHQ6YXV0bzttc28tbWFyZ2luLWJvdHRvbS1hbHQ6YXV0byI+Jm5ic3A7PG86cD48
L286cD48L3A+DQo8ZGl2IHN0eWxlPSJib3JkZXI6bm9uZTtib3JkZXItdG9wOnNvbGlkICNFMUUx
RTEgMS4wcHQ7cGFkZGluZzozLjBwdCAwaW4gMGluIDBpbiI+DQo8cCBjbGFzcz0iTXNvTm9ybWFs
IiBzdHlsZT0ibXNvLW1hcmdpbi10b3AtYWx0OmF1dG87bXNvLW1hcmdpbi1ib3R0b20tYWx0OmF1
dG8iPjxiPkZyb206PC9iPiBKb3NlcGggU2Fsb3dleSAmbHQ7PGEgaHJlZj0ibWFpbHRvOmpvZUBz
YWxvd2V5Lm5ldCIgdGFyZ2V0PSJfYmxhbmsiPmpvZUBzYWxvd2V5Lm5ldDwvYT4mZ3Q7DQo8YnI+
DQo8Yj5TZW50OjwvYj4gV2VkbmVzZGF5LCBPY3RvYmVyIDIxLCAyMDIwIDI6MzQgUE08YnI+DQo8
Yj5Ubzo8L2I+IEVNVSBXRyAmbHQ7PGEgaHJlZj0ibWFpbHRvOmVtdUBpZXRmLm9yZyIgdGFyZ2V0
PSJfYmxhbmsiPmVtdUBpZXRmLm9yZzwvYT4mZ3Q7OyBKb3VuaSBNYWxpbmVuICZsdDs8YSBocmVm
PSJtYWlsdG86akB3MS5maSIgdGFyZ2V0PSJfYmxhbmsiPmpAdzEuZmk8L2E+Jmd0OzsgSm9yZ2Ug
VmVyZ2FyYSAmbHQ7PGEgaHJlZj0ibWFpbHRvOmpvdmVyZ2FyQG1pY3Jvc29mdC5jb20iIHRhcmdl
dD0iX2JsYW5rIj5qb3ZlcmdhckBtaWNyb3NvZnQuY29tPC9hPiZndDs7IE9sZWcNCiBQZWthciAo
b2xwZWthcikgJmx0OzxhIGhyZWY9Im1haWx0bzpvbHBla2FyQGNpc2NvLmNvbSIgdGFyZ2V0PSJf
YmxhbmsiPm9scGVrYXJAY2lzY28uY29tPC9hPiZndDs8YnI+DQo8Yj5TdWJqZWN0OjwvYj4gUHJv
cG9zZWQgcmVzb2x1dGlvbiBmb3IgVEVBUCBlcnJhdGEgZm9yIDUxMjg8bzpwPjwvbzpwPjwvcD4N
CjwvZGl2Pg0KPHAgY2xhc3M9Ik1zb05vcm1hbCIgc3R5bGU9Im1zby1tYXJnaW4tdG9wLWFsdDph
dXRvO21zby1tYXJnaW4tYm90dG9tLWFsdDphdXRvIj4mbmJzcDs8bzpwPjwvbzpwPjwvcD4NCjxk
aXY+DQo8cCBjbGFzcz0iTXNvTm9ybWFsIiBzdHlsZT0ibXNvLW1hcmdpbi10b3AtYWx0OmF1dG87
bXNvLW1hcmdpbi1ib3R0b20tYWx0OmF1dG8iPkVycmF0YSA1MTI4OiZuYnNwOzxhIGhyZWY9Imh0
dHBzOi8vbmFtMDYuc2FmZWxpbmtzLnByb3RlY3Rpb24ub3V0bG9vay5jb20vP3VybD1odHRwcyUz
QSUyRiUyRnd3dy5yZmMtZWRpdG9yLm9yZyUyRmVycmF0YSUyRmVpZDUxMjgmYW1wO2RhdGE9MDQl
N0MwMSU3Q2pvdmVyZ2FyJTQwbWljcm9zb2Z0LmNvbSU3QzBjMzdkYjMzZDdhNzRjNGZkZmQxMDhk
ODc2OTJiNDZmJTdDNzJmOTg4YmY4NmYxNDFhZjkxYWIyZDdjZDAxMWRiNDclN0MxJTdDMCU3QzYz
NzM4OTcxOTc2MjQ4MTA3NSU3Q1Vua25vd24lN0NUV0ZwYkdac2IzZDhleUpXSWpvaU1DNHdMakF3
TURBaUxDSlFJam9pVjJsdU16SWlMQ0pCVGlJNklrMWhhV3dpTENKWFZDSTZNbjAlM0QlN0MxMDAw
JmFtcDtzZGF0YT10bTAxJTJGcUxBR2FROUh4ZXlCZWVVMHlHUFhWT1BkV2pJUkR0UHdXJTJGUmpH
SSUzRCZhbXA7cmVzZXJ2ZWQ9MCIgdGFyZ2V0PSJfYmxhbmsiPmh0dHBzOi8vd3d3LnJmYy1lZGl0
b3Iub3JnL2VycmF0YS9laWQ1MTI4PC9hPjxvOnA+PC9vOnA+PC9wPg0KPGRpdj4NCjxwIGNsYXNz
PSJNc29Ob3JtYWwiIHN0eWxlPSJtc28tbWFyZ2luLXRvcC1hbHQ6YXV0bzttc28tbWFyZ2luLWJv
dHRvbS1hbHQ6YXV0byI+UHJvcG9zZWQgU3RhdGU6IFZlcmlmaWVkPG86cD48L286cD48L3A+DQo8
L2Rpdj4NCjxkaXY+DQo8cCBjbGFzcz0iTXNvTm9ybWFsIiBzdHlsZT0ibXNvLW1hcmdpbi10b3At
YWx0OmF1dG87bXNvLW1hcmdpbi1ib3R0b20tYWx0OmF1dG8iPlJldmlzaW9uOjxvOnA+PC9vOnA+
PC9wPg0KPC9kaXY+DQo8ZGl2Pg0KPHAgY2xhc3M9Ik1zb05vcm1hbCIgc3R5bGU9Im1zby1tYXJn
aW4tdG9wLWFsdDphdXRvO21zby1tYXJnaW4tYm90dG9tLWFsdDphdXRvIj4mbmJzcDs8bzpwPjwv
bzpwPjwvcD4NCjwvZGl2Pg0KPGRpdj4NCjxwIGNsYXNzPSJNc29Ob3JtYWwiIHN0eWxlPSJtc28t
bWFyZ2luLXRvcC1hbHQ6YXV0bzttc28tbWFyZ2luLWJvdHRvbS1hbHQ6YXV0byI+U2VjdGlvbiA1
LjIuIHNheXM8bzpwPjwvbzpwPjwvcD4NCjwvZGl2Pg0KPGRpdj4NCjxwIHN0eWxlPSJtc28tbWFy
Z2luLXRvcC1hbHQ6NS4wcHQ7bWFyZ2luLXJpZ2h0OjMuNzVwdDttYXJnaW4tYm90dG9tOjcuNXB0
O21hcmdpbi1sZWZ0OjMuNzVwdCI+DQo8YnI+DQpJTUNLW2pdID0gVExTLVBSRihTLUlNQ0tbai0x
XSwgJnF1b3Q7SW5uZXIgTWV0aG9kcyBDb21wb3VuZCBLZXlzJnF1b3Q7LDxicj4NCiZuYnNwOyAm
bmJzcDsgJm5ic3A7ICZuYnNwOyAmbmJzcDsgJm5ic3A7ICZuYnNwOyAmbmJzcDsgSU1TS1tqXSwg
NjApPGJyPg0KPGJyPg0KSXQgc2hvdWxkIHNheTo8YnI+DQo8YnI+DQpJTUNLW2pdID0gVExTLVBS
RihTLUlNQ0tbai0xXSwgJnF1b3Q7SW5uZXIgTWV0aG9kcyBDb21wb3VuZCBLZXlzJnF1b3Q7LCZu
YnNwOzxzcGFuIHN0eWxlPSJmb250LXNpemU6MTAuNXB0O2ZvbnQtZmFtaWx5OiZxdW90O0FyaWFs
JnF1b3Q7LHNhbnMtc2VyaWY7Y29sb3I6IzJDNDM1MyI+SU1TS1tqXSB8IDYwKTwvc3Bhbj48bzpw
PjwvbzpwPjwvcD4NCjxwIHN0eWxlPSJtc28tbWFyZ2luLXRvcC1hbHQ6NS4wcHQ7bWFyZ2luLXJp
Z2h0OjMuNzVwdDttYXJnaW4tYm90dG9tOjcuNXB0O21hcmdpbi1sZWZ0OjMuNzVwdCI+DQo8c3Bh
biBzdHlsZT0iZm9udC1zaXplOjEwLjVwdDtmb250LWZhbWlseTomcXVvdDtBcmlhbCZxdW90Oyxz
YW5zLXNlcmlmO2NvbG9yOiMyQzQzNTMiPk5vdGU6Jm5ic3A7Jm5ic3A7PC9zcGFuPjxvOnA+PC9v
OnA+PC9wPg0KPHAgY2xhc3M9Ik1zb05vcm1hbCIgc3R5bGU9Im1zby1tYXJnaW4tdG9wLWFsdDph
dXRvO21zby1tYXJnaW4tYm90dG9tLWFsdDphdXRvIj5BY2NvcmRpbmcgdG88YnI+DQo8YnI+DQpS
RkM1MjQ2IFRoZSBUcmFuc3BvcnQgTGF5ZXIgU2VjdXJpdHkgKFRMUykgUHJvdG9jb2wgVmVyc2lv
biAxLjI8YnI+DQo8YnI+DQo1LiBITUFDIGFuZCB0aGUgUHNldWRvcmFuZG9tIEZ1bmN0aW9uPGJy
Pg0KPGJyPg0KJnF1b3Q7VExTJ3MgUFJGIGlzIGNyZWF0ZWQgYnkgYXBwbHlpbmcgUF9oYXNoIHRv
IHRoZSBzZWNyZXQgYXM6PGJyPg0KPGJyPg0KUFJGKHNlY3JldCwgbGFiZWwsIHNlZWQpID0gUF8m
bHQ7aGFzaCZndDsoc2VjcmV0LCBsYWJlbCArIHNlZWQpJnF1b3Q7PG86cD48L286cD48L3A+DQo8
L2Rpdj4NCjxkaXY+DQo8cCBjbGFzcz0iTXNvTm9ybWFsIiBzdHlsZT0ibXNvLW1hcmdpbi10b3At
YWx0OmF1dG87bXNvLW1hcmdpbi1ib3R0b20tYWx0OmF1dG8iPiZuYnNwOzxvOnA+PC9vOnA+PC9w
Pg0KPC9kaXY+DQo8ZGl2Pg0KPHAgY2xhc3M9Ik1zb05vcm1hbCIgc3R5bGU9Im1zby1tYXJnaW4t
dG9wLWFsdDphdXRvO21zby1tYXJnaW4tYm90dG9tLWFsdDphdXRvIj5JbiB0ZXJtcyBvZiBQXyZs
dDtoYXNoJmd0OyB0aGlzIHdvdWxkIGxvb2sgbGlrZSB0aGUgZm9sbG93aW5nIHdpdGggdGhlIGxl
bmd0aCByZXByZXNlbnRlZCBhcyBhIDIgYnl0ZSB2YWx1ZSBpbiBuZXR3b3JrIGJ5dGUgb3JkZXI6
PG86cD48L286cD48L3A+DQo8L2Rpdj4NCjxkaXY+DQo8cCBjbGFzcz0iTXNvTm9ybWFsIiBzdHls
ZT0ibXNvLW1hcmdpbi10b3AtYWx0OmF1dG87bXNvLW1hcmdpbi1ib3R0b20tYWx0OmF1dG8iPiZu
YnNwOzxvOnA+PC9vOnA+PC9wPg0KPC9kaXY+DQo8ZGl2Pg0KPHAgY2xhc3M9Ik1zb05vcm1hbCIg
c3R5bGU9Im1zby1tYXJnaW4tdG9wLWFsdDphdXRvO21zby1tYXJnaW4tYm90dG9tLWFsdDphdXRv
Ij5JTUNLW2pdID0gUF8mbHQ7aGFzaCZndDsoUy1JTUNLW2otMV0sICZxdW90O0lubmVyIE1ldGhv
ZHMgQ29tcG91bmQgS2V5cyZxdW90OyB8Jm5ic3A7PHNwYW4gc3R5bGU9ImZvbnQtc2l6ZToxMC41
cHQ7Y29sb3I6IzJDNDM1MyI+SU1TS1tqXSB8IDB4MDAgfCAweDNDKTwvc3Bhbj48bzpwPjwvbzpw
PjwvcD4NCjwvZGl2Pg0KPGRpdj4NCjxwIGNsYXNzPSJNc29Ob3JtYWwiIHN0eWxlPSJtc28tbWFy
Z2luLXRvcC1hbHQ6YXV0bzttc28tbWFyZ2luLWJvdHRvbS1hbHQ6YXV0byI+Jm5ic3A7PG86cD48
L286cD48L3A+DQo8L2Rpdj4NCjxkaXY+DQo8cCBjbGFzcz0iTXNvTm9ybWFsIiBzdHlsZT0ibXNv
LW1hcmdpbi10b3AtYWx0OmF1dG87bXNvLW1hcmdpbi1ib3R0b20tYWx0OmF1dG8iPiZuYnNwOzxv
OnA+PC9vOnA+PC9wPg0KPC9kaXY+DQo8L2Rpdj4NCjwvZGl2Pg0KPC9kaXY+DQo8L2Jsb2NrcXVv
dGU+DQo8L2Rpdj4NCjwvZGl2Pg0KPC9kaXY+DQo8L2Rpdj4NCjwvYmxvY2txdW90ZT4NCjwvZGl2
Pg0KPC9kaXY+DQo8L2Jsb2NrcXVvdGU+DQo8L2Rpdj4NCjwvZGl2Pg0KPC9kaXY+DQo8L2JvZHk+
DQo8L2h0bWw+DQo=

--_000_CH2PR21MB1381E75B194E1CEDEBFDE113D11D0CH2PR21MB1381namp_--


From nobody Thu Oct 22 07:28:00 2020
Return-Path: <aland@deployingradius.com>
X-Original-To: emu@ietfa.amsl.com
Delivered-To: emu@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 32D043A0A10 for <emu@ietfa.amsl.com>; Thu, 22 Oct 2020 07:27:59 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.899
X-Spam-Level: 
X-Spam-Status: No, score=-1.899 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, SPF_HELO_NONE=0.001, SPF_PASS=-0.001, URIBL_BLOCKED=0.001] autolearn=unavailable autolearn_force=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 ytNC7IytjmAA for <emu@ietfa.amsl.com>; Thu, 22 Oct 2020 07:27:57 -0700 (PDT)
Received: from mail.networkradius.com (mail.networkradius.com [62.210.147.122]) (using TLSv1.2 with cipher ADH-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id C192E3A0DD1 for <emu@ietf.org>; Thu, 22 Oct 2020 07:27:57 -0700 (PDT)
Received: from [192.168.46.130] (24-52-251-6.cable.teksavvy.com [24.52.251.6]) by mail.networkradius.com (Postfix) with ESMTPSA id 1C7EC3B8; Thu, 22 Oct 2020 14:27:54 +0000 (UTC)
Authentication-Results: NetworkRADIUS; dmarc=none (p=none dis=none) header.from=deployingradius.com
Content-Type: text/plain; charset=utf-8
Mime-Version: 1.0 (Mac OS X Mail 13.4 \(3608.120.23.2.1\))
From: Alan DeKok <aland@deployingradius.com>
In-Reply-To: <CH2PR21MB1381E75B194E1CEDEBFDE113D11D0@CH2PR21MB1381.namprd21.prod.outlook.com>
Date: Thu, 22 Oct 2020 10:27:53 -0400
Cc: Oleg Pekar <oleg.pekar.2017@gmail.com>, Joseph Salowey <joe@salowey.net>,  EMU WG <emu@ietf.org>
Content-Transfer-Encoding: quoted-printable
Message-Id: <9B36569B-5BDF-4FE3-A081-72C82F3339AC@deployingradius.com>
References: <CAOgPGoBay+GG=F8WV0gLOOwLtGdGALGw_cM2JoAnXOtmGq7A+w@mail.gmail.com> <CH2PR21MB138143E929DAFE3C893D8144D11C0@CH2PR21MB1381.namprd21.prod.outlook.com> <CAOgPGoAtcm+Br+YkCyTtg5nJjqO7LGSo77b+CD4+Ba05azafew@mail.gmail.com> <CH2PR21MB13815BCEDC846D7C440AD564D11C0@CH2PR21MB1381.namprd21.prod.outlook.com> <CAOgPGoDTC-qiHOXFTJd7aMn2To7ySzBcx+iQMB9m5foC1bFxzw@mail.gmail.com> <CABXxEz8SRvMXdMR8_cPfvWdauJZwCjnd=7ytnVZ+_L-sB48wvw@mail.gmail.com> <CH2PR21MB1381E75B194E1CEDEBFDE113D11D0@CH2PR21MB1381.namprd21.prod.outlook.com>
To: Jorge Vergara <jovergar=40microsoft.com@dmarc.ietf.org>
X-Mailer: Apple Mail (2.3608.120.23.2.1)
Archived-At: <https://mailarchive.ietf.org/arch/msg/emu/C-NVd0gqlP34fZX69lVHX-H7PmM>
Subject: Re: [Emu] Proposed resolution for TEAP errata for 5128
X-BeenThere: emu@ietf.org
X-Mailman-Version: 2.1.29
Precedence: list
List-Id: "EAP Methods Update \(EMU\)" <emu.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/emu>, <mailto:emu-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/emu/>
List-Post: <mailto:emu@ietf.org>
List-Help: <mailto:emu-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/emu>, <mailto:emu-request@ietf.org?subject=subscribe>
X-List-Received-Date: Thu, 22 Oct 2020 14:27:59 -0000

On Oct 22, 2020, at 10:12 AM, Jorge Vergara =
<jovergar=3D40microsoft.com@dmarc.ietf.org> wrote:
>=20
> My concern with this proposal of defining a new KDF is that it is a =
clear breaking change to any implementation that may exist.

  I am wary of breaking existing and deployed implementations.

> In my opinion such a change would be fine if we want to bump some =
version numbers - maybe the TEAP version number has to be bumped, or =
maybe this can be achieved solely with the TLV version fields some of =
the TLVs contain. I haven=E2=80=99t thought about this aspect of too =
much. But redefining the KDF entirely with no version changes would be =
disruptive to multiple products.

  TBH, there isn't a lot of point.  We should just document what =
implementations do today.  Then, suggest that everyone move to TLS 1.3, =
and define entirely new derivations there.

  Alan DeKok.


From nobody Thu Oct 22 07:44:49 2020
Return-Path: <oleg.pekar.2017@gmail.com>
X-Original-To: emu@ietfa.amsl.com
Delivered-To: emu@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 383E43A0F41 for <emu@ietfa.amsl.com>; Thu, 22 Oct 2020 07:44:47 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.847
X-Spam-Level: 
X-Spam-Status: No, score=-1.847 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, DKIM_VALID_EF=-0.1, FREEMAIL_ENVFROM_END_DIGIT=0.25, FREEMAIL_FROM=0.001, HTML_MESSAGE=0.001, SPF_HELO_NONE=0.001, SPF_PASS=-0.001, URIBL_BLOCKED=0.001] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (2048-bit key) header.d=gmail.com
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 S_UFA9vZSVN2 for <emu@ietfa.amsl.com>; Thu, 22 Oct 2020 07:44:45 -0700 (PDT)
Received: from mail-ot1-x336.google.com (mail-ot1-x336.google.com [IPv6:2607:f8b0:4864:20::336]) (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 61A0B3A0F22 for <emu@ietf.org>; Thu, 22 Oct 2020 07:44:45 -0700 (PDT)
Received: by mail-ot1-x336.google.com with SMTP id 32so1715254otm.3 for <emu@ietf.org>; Thu, 22 Oct 2020 07:44:45 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20161025;  h=mime-version:references:in-reply-to:from:date:message-id:subject:to :cc; bh=Kh3uNKyHWssfvr4efJiaT3dKzFTt9tMU3HQxBH+hblQ=; b=GSg7jVZSRzp33iryw1lfNrGcOkAJXgL+VCqOJHBWBfwxjHNTV4YMf3Os/faCRCm+fx VObhbEzwJQwRcQaURVedsM6s7b5yKkV3yeXn1/4p8wVdagOaOpDIs2TskBIf0Mi8Emmc iFtkeIQAs2CrSUYHPCvL7rh53B/Yol3qxuyToMXkSZf9j7XSuIW3XQSJpaSSxXKG/6bj pPWRhie6hfN5WPJlZBk1Grb8T+iwSnI4pXKrO3JeV8D6AnMdhlLaSDh+yMrA/hleUZdE 0MDFokH6kEqMo0zqJkzZwNZstSVTLDGy5BMpPED5DUCpR+WXAcdRDeC409j8RnYhb0gR vbJQ==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:mime-version:references:in-reply-to:from:date :message-id:subject:to:cc; bh=Kh3uNKyHWssfvr4efJiaT3dKzFTt9tMU3HQxBH+hblQ=; b=azMFCa27+efbfdjj8zQajANVVjr+/HidbR0gXx3Tgn1Z+axA9o3EcIRsE0MsfyU2OE eFQcKEHk+q/ce4rV1L+Xv/97S7MSGi/d2kXE4zJHnmBkgzJWpC/8efSqzANzhwnrYJm2 Ass910Y+GKNpTPKoaP4TwVhPNimk9zoMw3nd/1g/l5jBPDvtVKIQlnXi+3Q58QRpf7Xz F4rwp7Fh5446llcmxobIwqjnvCg5IUtjuPefJVVYwgRUkXTI8Js7ojx8SB7k0+ge4aQ9 KwuYS+IsSpRusPKGltOyxjcXpTry7WMt3dSQnBPBe7ARyHYtPxlLbTLLIbcZfdnl61nJ zqlQ==
X-Gm-Message-State: AOAM531PxQhjsT4WU4f2bHbaFGkSpj6PexdT86Y1syc0ghbn4zmjj5g/ R13OlRkH9Mtr15swJQ9VYHG4dZl3tosflVvM57hybVlFzXEYfdfW
X-Google-Smtp-Source: ABdhPJynRCnVDc/BepazrKe6ARgBxEAnfjtijRurO1Cl3N+qtg4KQZPRtQUHcxGA+pnFXR2uTAUt6JO6aPrXiqxnMZk=
X-Received: by 2002:a9d:6a0a:: with SMTP id g10mr2221373otn.44.1603377884638;  Thu, 22 Oct 2020 07:44:44 -0700 (PDT)
MIME-Version: 1.0
References: <CAOgPGoCmYCEKgE6P_Ja5VRLh4M1jWSML_WNuqdHA-t2TibBnjA@mail.gmail.com>
In-Reply-To: <CAOgPGoCmYCEKgE6P_Ja5VRLh4M1jWSML_WNuqdHA-t2TibBnjA@mail.gmail.com>
From: Oleg Pekar <oleg.pekar.2017@gmail.com>
Date: Thu, 22 Oct 2020 17:44:33 +0300
Message-ID: <CABXxEz877CEXHnMSR88KhbYQHZEoEve0EY+ORQr-KN3ehEsY8w@mail.gmail.com>
To: Joseph Salowey <joe@salowey.net>
Cc: EMU WG <emu@ietf.org>, Jouni Malinen <j@w1.fi>,  Jorge Vergara <jovergar=40microsoft.com@dmarc.ietf.org>
Content-Type: multipart/alternative; boundary="00000000000041327905b24381e1"
Archived-At: <https://mailarchive.ietf.org/arch/msg/emu/LEOqV-DNjDM67XHXXxcZqhDfEQg>
Subject: Re: [Emu] Proposed resolution for TEAP errata 5765
X-BeenThere: emu@ietf.org
X-Mailman-Version: 2.1.29
Precedence: list
List-Id: "EAP Methods Update \(EMU\)" <emu.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/emu>, <mailto:emu-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/emu/>
List-Post: <mailto:emu@ietf.org>
List-Help: <mailto:emu-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/emu>, <mailto:emu-request@ietf.org?subject=subscribe>
X-List-Received-Date: Thu, 22 Oct 2020 14:44:47 -0000

--00000000000041327905b24381e1
Content-Type: text/plain; charset="UTF-8"

The Authority-ID TLV is used by the client to identify the TEAP server it
is talking to. If the same client talks to more than one TEAP server - it
can keep PACs or cached data from all of them identified by
the Authority-ID. If we make it optional in TEAP start message but keep
mandatory in PAC-Info part of the PAC - TEAP servers can stop sending it
during TEAP start and then clients will need to fetch it from PAC, if there
is a PAC in the conversation. But if there's no PAC - then no way to
identify TEAP server.

Maybe we should keep it mandatory?



On Thu, Oct 22, 2020 at 12:47 AM Joseph Salowey <joe@salowey.net> wrote:

> Errata 5765: https://www.rfc-editor.org/errata/eid5765
> Proposed Status: Verified
> Revision: (unmodified from original posting)
>
> Section 4.2.2 says:
>
>    M
>
>       Mandatory, set to one (1)
>
> It should say:
>
>    M
>
>       0 (Optional)
>
> Notes:
>
> Authority-ID TLV is used only as an Outer TLV (in TEAP/Start) and Section
> 4.3.1 mandates all Outer TLVs to be marked as optional ("Outer TLVs MUST be
> marked as optional"). As such, Section 4.2.2 is incorrect in claiming the
> Authority-ID TLV to use M=1.
>

--00000000000041327905b24381e1
Content-Type: text/html; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable

<div dir=3D"ltr">The Authority-ID TLV is used by the client to identify the=
 TEAP server it is talking to. If the same client talks to more than one TE=
AP server - it can keep PACs or cached data from all of them identified by =
the=C2=A0Authority-ID. If we make it optional in TEAP start message but kee=
p mandatory in PAC-Info part of the PAC - TEAP servers can stop sending it =
during TEAP start and then clients will need to fetch it from PAC, if there=
 is a PAC in the conversation. But if there&#39;s no PAC - then no way to i=
dentify TEAP server.=C2=A0<div><br></div><div>Maybe we should keep it manda=
tory?=C2=A0<br><div><br></div><div><br></div></div></div><br><div class=3D"=
gmail_quote"><div dir=3D"ltr" class=3D"gmail_attr">On Thu, Oct 22, 2020 at =
12:47 AM Joseph Salowey &lt;<a href=3D"mailto:joe@salowey.net">joe@salowey.=
net</a>&gt; wrote:<br></div><blockquote class=3D"gmail_quote" style=3D"marg=
in:0px 0px 0px 0.8ex;border-left:1px solid rgb(204,204,204);padding-left:1e=
x"><div dir=3D"ltr">Errata 5765:=C2=A0<a href=3D"https://www.rfc-editor.org=
/errata/eid5765" target=3D"_blank">https://www.rfc-editor.org/errata/eid576=
5</a><div>Proposed Status: Verified</div><div>Revision: (unmodified from or=
iginal posting)</div><div><br></div>Section 4.2.2 says:<br><br>=C2=A0 =C2=
=A0M<br><br>=C2=A0 =C2=A0 =C2=A0 Mandatory, set to one (1)<br><br>It should=
 say:<br><br>=C2=A0 =C2=A0M<br><br>=C2=A0 =C2=A0 =C2=A0 0 (Optional)<br><br=
>Notes:<br><br>Authority-ID TLV is used only as an Outer TLV (in TEAP/Start=
) and Section 4.3.1 mandates all Outer TLVs to be marked as optional (&quot=
;Outer TLVs MUST be marked as optional&quot;). As such, Section 4.2.2 is in=
correct in claiming the Authority-ID TLV to use M=3D1.</div>
</blockquote></div>

--00000000000041327905b24381e1--


From nobody Thu Oct 22 08:04:02 2020
Return-Path: <oleg.pekar.2017@gmail.com>
X-Original-To: emu@ietfa.amsl.com
Delivered-To: emu@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id E7E893A0FEC for <emu@ietfa.amsl.com>; Thu, 22 Oct 2020 08:04:00 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.747
X-Spam-Level: 
X-Spam-Status: No, score=-1.747 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, DKIM_VALID_EF=-0.1, FREEMAIL_ENVFROM_END_DIGIT=0.25, FREEMAIL_FROM=0.001, HTML_MESSAGE=0.001, HTTPS_HTTP_MISMATCH=0.1, SPF_HELO_NONE=0.001, SPF_PASS=-0.001, URIBL_BLOCKED=0.001] autolearn=no autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (2048-bit key) header.d=gmail.com
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 Z0eRQg_ANh0g for <emu@ietfa.amsl.com>; Thu, 22 Oct 2020 08:03:59 -0700 (PDT)
Received: from mail-ot1-x334.google.com (mail-ot1-x334.google.com [IPv6:2607:f8b0:4864:20::334]) (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 D6FFA3A0FC4 for <emu@ietf.org>; Thu, 22 Oct 2020 08:03:58 -0700 (PDT)
Received: by mail-ot1-x334.google.com with SMTP id f97so928112otb.7 for <emu@ietf.org>; Thu, 22 Oct 2020 08:03:58 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20161025;  h=mime-version:references:in-reply-to:from:date:message-id:subject:to :cc; bh=xg8FQwL3l/kckebRddYhPH0ii8A2isuoIIfL1vxKAJg=; b=eythvQhOdAEiakXQGH6JTpTnfVuqKYvwCz/5lnh08fbFEYXS6O8D8XA75xUcEVWszV Wgi7NWBPS2FlTFxHAXExG559YhUsYcatvKIfDj38334I8DAdnnWZyKxwnmFMY4m/kj0d an3Hih3YhlY3hOy4JT82zstckscE8a0Afyw/0wWT4PnYz6HJFxLtIKJClSvF+KOSFxoo PhTQ3AUMnP+3JhLUxWGwD8ORb/GW2a/7SZuIgP5kXhLFKckSyXZ/HPxGyLIqiLpq6PH/ 7/rDEWA1cuhqD0+sy2J65fnOGoKeutHeGKWQnc/Fx24ajVwZBiG/JE4XPc758zxW0npV syOQ==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:mime-version:references:in-reply-to:from:date :message-id:subject:to:cc; bh=xg8FQwL3l/kckebRddYhPH0ii8A2isuoIIfL1vxKAJg=; b=sWRCuFOOO3lQ60uilGkhHkhGwbiLCmXcKHvom+5wXyxeU9CVgT6YffaCO5hr6kchn4 /qLxRZawJe/ccqwp6eE6LE2n0IBawmXYJQ0bPPRV5r8ZTnFaJdKJ9fkmo3cfp2EUUn+O C2q8VaHbBJiJxJT1adWtqxpMaXRe9772oiT4/6VsFV+PHLuYNnLXmG6wGUPH3xEoEELd pFxafq6WBlwi3NqwOoYW+fo8bdlAfI5tOmhjguRX6zEeTJ1vAiIBg/ch973uxnEjsZi2 gAW/7goVFFs6Swq8iwymZAzCX5boTOnVH52A7miu3xwMxZUVyh/LgNU8uEaRoRdK8Ur3 mB1w==
X-Gm-Message-State: AOAM532V8DdZ3zRmB/ndDmv1dKBBXp3YEFnWqo9TW9DcQxKZa358+IW6 1DbFrcO1tIiqw1+B6P5KU05eZP3AWrt5yYslib4=
X-Google-Smtp-Source: ABdhPJzssGw/sKGlMCJMqAfNjh/BILq+ttq+fav0p4Dp2Dfx1mkxBusHhsh5U3C4n90B/+g3uMZXy0p2BM9KXpFTKmI=
X-Received: by 2002:a9d:7752:: with SMTP id t18mr2228580otl.341.1603379037908;  Thu, 22 Oct 2020 08:03:57 -0700 (PDT)
MIME-Version: 1.0
References: <CAOgPGoCAFD+Z6_hCNMN8F9ODC-VTxOM+DuxjSHU25HWjqzt+ag@mail.gmail.com> <CH2PR21MB1381F392AAF246CE1590A318D11D0@CH2PR21MB1381.namprd21.prod.outlook.com>
In-Reply-To: <CH2PR21MB1381F392AAF246CE1590A318D11D0@CH2PR21MB1381.namprd21.prod.outlook.com>
From: Oleg Pekar <oleg.pekar.2017@gmail.com>
Date: Thu, 22 Oct 2020 18:03:46 +0300
Message-ID: <CABXxEz9hJQfPQjyNrycwfgYKYeX50yciUBceLZHo7KJFPuO6wQ@mail.gmail.com>
To: Jorge Vergara <jovergar@microsoft.com>
Cc: Joseph Salowey <joe@salowey.net>, EMU WG <emu@ietf.org>, Jouni Malinen <j@w1.fi>
Content-Type: multipart/alternative; boundary="000000000000feb64b05b243c504"
Archived-At: <https://mailarchive.ietf.org/arch/msg/emu/NE3401eSR5y1xkfuXK2GCijHftI>
Subject: Re: [Emu] Resolution of TEAP Errata 5767
X-BeenThere: emu@ietf.org
X-Mailman-Version: 2.1.29
Precedence: list
List-Id: "EAP Methods Update \(EMU\)" <emu.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/emu>, <mailto:emu-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/emu/>
List-Post: <mailto:emu@ietf.org>
List-Help: <mailto:emu-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/emu>, <mailto:emu-request@ietf.org?subject=subscribe>
X-List-Received-Date: Thu, 22 Oct 2020 15:04:01 -0000

--000000000000feb64b05b243c504
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable

The proposal is aligned with previously discussed. One small wording I
would change is:

Section 4.2.13 says:
It MUST be included with the Intermediate-Result TLV to perform
cryptographic binding after each successful EAP authentication method in a
sequence of >>>one or more<<< EAP methods, before proceeding with another
inner EAP method.

Just "sequence" sounds like it denotes the case where there should be more
than one EAP authentication method.

On Thu, Oct 22, 2020 at 3:39 AM Jorge Vergara <jovergar@microsoft.com>
wrote:

> I agree with all the proposed resolutions. For context, there was some
> prior discussion of this errata here:
> https://mailarchive.ietf.org/arch/msg/emu/K_XWBMevKNdxdWskK8RkBt1ZpSQ/
>
>
>
> Jorge Vergara
>
>
>
> *From:* Joseph Salowey <joe@salowey.net>
> *Sent:* Wednesday, October 21, 2020 5:13 PM
> *To:* EMU WG <emu@ietf.org>; Jouni Malinen <j@w1.fi>; Jorge Vergara <
> jovergar@microsoft.com>; Oleg Pekar <oleg.pekar.2017@gmail.com>
> *Subject:* Resolution of TEAP Errata 5767
>
>
>
> Errata 5767: https://www.rfc-editor.org/errata/eid5767
> <https://nam06.safelinks.protection.outlook.com/?url=3Dhttps%3A%2F%2Fwww.=
rfc-editor.org%2Ferrata%2Feid5767&data=3D04%7C01%7Cjovergar%40microsoft.com=
%7C50b56afadcf34732d50708d8761f45d5%7C72f988bf86f141af91ab2d7cd011db47%7C1%=
7C0%7C637389223977410444%7CUnknown%7CTWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIj=
oiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D%7C1000&sdata=3D24y%2BkrsBw1mdGuNMM=
gqmqiRz%2BqeFt9jVX4qUHtlUJwY%3D&reserved=3D0>
> Status: Verified
>
> Revision:
>
>
>
> Section 3.3.1 says:
>
>    EAP method messages are carried within EAP-Payload TLVs defined in
>    Section 4.2.10.  If more than one method is going to be executed in
>    the tunnel, then upon method completion, the server MUST send an
>    Intermediate-Result TLV indicating the result.
>
> It should say:
>
>    EAP method messages are carried within EAP-Payload TLVs defined in
>    Section 4.2.10.  Upon completion of each EAP authentication method in
>    the tunnel, the server MUST send an Intermediate-Result TLV
>    indicating the result.
>
>
>
> Section 3.3.3 says:
>
>
>
>   The Crypto-Binding TLV and Intermediate-Result TLV MUST be included
>
>   to perform cryptographic binding after each successful EAP method in a
>
>   sequence of one or more EAP methods.
>
>
>
> It should say:
>
>
>
>   The Crypto-Binding TLV and Intermediate-Result TLV MUST be included
>
>   to perform cryptographic binding after each successful EAP
> authentication
>
>   method in a sequence of one or more EAP methods.
>
>
>
> Section 3.8.3 says:
>
>
>    Upon successful completion of the EAP method in Phase 2, the peer and
>    server exchange a Crypto-Binding TLV to bind the inner method with
>    the outer tunnel and ensure that a man-in-the-middle attack has not
>    been attempted.
>
>
>
> It should say:
>
>
>
>    Upon successful completion of the EAP authentication method in Phase 2=
,
>
>    the peer and server exchange a Crypto-Binding TLV to bind the inner
>
>    method with the outer tunnel and ensure that a man-in-the-middle attac=
k
>
>    has not been attempted.
>
>
>
> Section 4.2.11 says:
>
>
>
>    The Intermediate-Result TLV provides support for acknowledged
>
>    intermediate Success and Failure messages between multiple
>
>    inner EAP methods within EAP.
>
>
>
> It should say:
>
>
>
>   The Intermediate-Result TLV provides support for acknowledged
>
>   intermediate Success and Failure messages after each inner EAP
>
>   authentication method.
>
>
>
> Section 4.2.13 says:
>
>
>
>  It MUST be included with the Intermediate-Result TLV to perform
>
>  cryptographic binding after each successful EAP method in a
>
>  sequence of EAP methods, before proceeding with another inner
>
>  EAP method.
>
>
>
> It should say:
>
>
>
>  It MUST be included with the Intermediate-Result TLV to perform
>
>  cryptographic binding after each successful EAP authentication
>
>  method in a sequence of EAP methods, before proceeding with
>
>  another inner EAP method.
>
>
>
> Notes:
>
> TEAP description is somewhat vague in discussion about "EAP methods" vs.
> "EAP authentication methods" as it comes to the EAP methods performed in
> Phase 2 within the TLS tunnel. RFC 3748 defines Identity request/response
> as an EAP method. However, this method is not an "authentication method"
> which is a special case of an method where the Type is 4 or greater.
>
> RFC 7170 uses correct terminology in the first paragraph of Section 3.3.1
> when talking about multiple authentication methods not being allowed by R=
FC
> 3748 in a single EAP conversation. However, many, but not all, of the
> following "[EAP] method" instances are actually referring to "[EAP]
> authentication method". This results in incorrect claims on when the
> Intermediate-Result TLV and Crypto-Binding TLV are used. They are not use=
d
> after an EAP non-authentication method like Identity (e.g., see the examp=
le
> in C.3); they are used after each EAP authentication method like EAP-pwd.
>
> Furthermore, the comment about "more than one method is going to be
> executed in the tunnel" does not sound accurate. This applies even if onl=
y
> a single EAP authentication method is executed in the tunnel (Identity
> method is not required to be executed). The proposed text in this errata
> entry addresses these two issues in Section 3.3.1. The following addition=
al
> changes would be needed to make rest of the specification use the terms
> more accurately:
>
> 3.3.3: "after each successful EAP method" --> "after each successful EAP
> authentication method"
> 3.8.3: "completion of the EAP method" --> "completion of the EAP
> authentication method"
> 4.2.11: "between multiple inner EAP methods within EAP" --> "after each
> inner EAP authentication method"
> 4.2.13: "after each successful EAP method" --> "after each successful EAP
> authentication method"
>

--000000000000feb64b05b243c504
Content-Type: text/html; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable

<div dir=3D"ltr">The proposal is aligned with previously discussed. One sma=
ll wording I would change is:<div><br></div><div>Section 4.2.13 says:<br></=
div><div>It MUST be included with the Intermediate-Result TLV to perform cr=
yptographic binding after each successful EAP authentication method in a
sequence of &gt;&gt;&gt;one or more&lt;&lt;&lt; EAP methods, before proceed=
ing with another inner EAP method.<br></div><div><br></div><div>Just &quot;=
sequence&quot; sounds like it denotes the case where there should=C2=A0be m=
ore than one EAP authentication method.=C2=A0</div></div><br><div class=3D"=
gmail_quote"><div dir=3D"ltr" class=3D"gmail_attr">On Thu, Oct 22, 2020 at =
3:39 AM Jorge Vergara &lt;<a href=3D"mailto:jovergar@microsoft.com">joverga=
r@microsoft.com</a>&gt; wrote:<br></div><blockquote class=3D"gmail_quote" s=
tyle=3D"margin:0px 0px 0px 0.8ex;border-left:1px solid rgb(204,204,204);pad=
ding-left:1ex">





<div lang=3D"EN-US" style=3D"overflow-wrap: break-word;">
<div class=3D"gmail-m_-977586881517622851WordSection1">
<p class=3D"MsoNormal">I agree with all the proposed resolutions. For conte=
xt, there was some prior discussion of this errata here:
<a href=3D"https://mailarchive.ietf.org/arch/msg/emu/K_XWBMevKNdxdWskK8RkBt=
1ZpSQ/" target=3D"_blank">
https://mailarchive.ietf.org/arch/msg/emu/K_XWBMevKNdxdWskK8RkBt1ZpSQ/</a><=
u></u><u></u></p>
<p class=3D"MsoNormal"><u></u>=C2=A0<u></u></p>
<p class=3D"MsoNormal">Jorge Vergara<u></u><u></u></p>
<p class=3D"MsoNormal"><u></u>=C2=A0<u></u></p>
<div style=3D"border-right:none;border-bottom:none;border-left:none;border-=
top:1pt solid rgb(225,225,225);padding:3pt 0in 0in">
<p class=3D"MsoNormal"><b>From:</b> Joseph Salowey &lt;<a href=3D"mailto:jo=
e@salowey.net" target=3D"_blank">joe@salowey.net</a>&gt; <br>
<b>Sent:</b> Wednesday, October 21, 2020 5:13 PM<br>
<b>To:</b> EMU WG &lt;<a href=3D"mailto:emu@ietf.org" target=3D"_blank">emu=
@ietf.org</a>&gt;; Jouni Malinen &lt;<a href=3D"mailto:j@w1.fi" target=3D"_=
blank">j@w1.fi</a>&gt;; Jorge Vergara &lt;<a href=3D"mailto:jovergar@micros=
oft.com" target=3D"_blank">jovergar@microsoft.com</a>&gt;; Oleg Pekar &lt;<=
a href=3D"mailto:oleg.pekar.2017@gmail.com" target=3D"_blank">oleg.pekar.20=
17@gmail.com</a>&gt;<br>
<b>Subject:</b> Resolution of TEAP Errata 5767<u></u><u></u></p>
</div>
<p class=3D"MsoNormal"><u></u>=C2=A0<u></u></p>
<p class=3D"MsoNormal">Errata 5767:=C2=A0<a href=3D"https://nam06.safelinks=
.protection.outlook.com/?url=3Dhttps%3A%2F%2Fwww.rfc-editor.org%2Ferrata%2F=
eid5767&amp;data=3D04%7C01%7Cjovergar%40microsoft.com%7C50b56afadcf34732d50=
708d8761f45d5%7C72f988bf86f141af91ab2d7cd011db47%7C1%7C0%7C6373892239774104=
44%7CUnknown%7CTWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1h=
aWwiLCJXVCI6Mn0%3D%7C1000&amp;sdata=3D24y%2BkrsBw1mdGuNMMgqmqiRz%2BqeFt9jVX=
4qUHtlUJwY%3D&amp;reserved=3D0" target=3D"_blank">https://www.rfc-editor.or=
g/errata/eid5767</a><br>
Status: Verified<u></u><u></u></p>
<div>
<p class=3D"MsoNormal">Revision:<u></u><u></u></p>
</div>
<div>
<p class=3D"MsoNormal"><u></u>=C2=A0<u></u></p>
</div>
<p class=3D"MsoNormal">Section 3.3.1 says:<br>
<br>
=C2=A0 =C2=A0EAP method messages are carried within EAP-Payload TLVs define=
d in<br>
=C2=A0 =C2=A0Section 4.2.10.=C2=A0 If more than one method is going to be e=
xecuted in<br>
=C2=A0 =C2=A0the tunnel, then upon method completion, the server MUST send =
an<br>
=C2=A0 =C2=A0Intermediate-Result TLV indicating the result.<br>
<br>
It should say:<br>
<br>
=C2=A0 =C2=A0EAP method messages are carried within EAP-Payload TLVs define=
d in<br>
=C2=A0 =C2=A0Section 4.2.10.=C2=A0 Upon completion of each EAP authenticati=
on method in<br>
=C2=A0 =C2=A0the tunnel, the server MUST send an Intermediate-Result TLV<br=
>
=C2=A0 =C2=A0indicating the result.<u></u><u></u></p>
<div>
<p class=3D"MsoNormal"><u></u>=C2=A0<u></u></p>
</div>
<div>
<p class=3D"MsoNormal">Section 3.3.3 says:=C2=A0<u></u><u></u></p>
</div>
<div>
<p class=3D"MsoNormal"><u></u>=C2=A0<u></u></p>
</div>
<p class=3D"MsoNormal">=C2=A0 The Crypto-Binding TLV and Intermediate-Resul=
t TLV MUST be included=C2=A0<u></u><u></u></p>
<div>
<p class=3D"MsoNormal">=C2=A0 to perform cryptographic binding after each s=
uccessful EAP method in a=C2=A0<u></u><u></u></p>
</div>
<div>
<p class=3D"MsoNormal">=C2=A0 sequence of one or more EAP methods.<u></u><u=
></u></p>
</div>
<div>
<p class=3D"MsoNormal"><u></u>=C2=A0<u></u></p>
</div>
<div>
<p class=3D"MsoNormal">It should say:<u></u><u></u></p>
</div>
<div>
<p class=3D"MsoNormal"><u></u>=C2=A0<u></u></p>
</div>
<div>
<p class=3D"MsoNormal">=C2=A0 The Crypto-Binding TLV and Intermediate-Resul=
t TLV MUST be included=C2=A0<u></u><u></u></p>
<div>
<p class=3D"MsoNormal">=C2=A0 to perform cryptographic binding after each s=
uccessful EAP authentication=C2=A0<u></u><u></u></p>
</div>
<div>
<p class=3D"MsoNormal">=C2=A0 method in a sequence of one or more EAP metho=
ds.<u></u><u></u></p>
</div>
</div>
<div>
<p class=3D"MsoNormal"><u></u>=C2=A0<u></u></p>
</div>
<div>
<p class=3D"MsoNormal">Section 3.8.3 says:=C2=A0<u></u><u></u></p>
</div>
<p class=3D"MsoNormal"><br>
=C2=A0 =C2=A0Upon successful completion of the EAP method in Phase 2, the p=
eer and<br>
=C2=A0 =C2=A0server exchange a Crypto-Binding TLV to bind the inner method =
with<br>
=C2=A0 =C2=A0the outer tunnel and ensure that a man-in-the-middle attack ha=
s not<br>
=C2=A0 =C2=A0been attempted.<u></u><u></u></p>
<div>
<p class=3D"MsoNormal"><u></u>=C2=A0<u></u></p>
</div>
<div>
<p class=3D"MsoNormal">It should say:<u></u><u></u></p>
</div>
<div>
<p class=3D"MsoNormal"><u></u>=C2=A0<u></u></p>
</div>
<div>
<p class=3D"MsoNormal">=C2=A0 =C2=A0Upon successful completion of the EAP a=
uthentication method in Phase 2,=C2=A0<u></u><u></u></p>
</div>
<div>
<p class=3D"MsoNormal">=C2=A0 =C2=A0the peer and server exchange a Crypto-B=
inding TLV to bind the inner=C2=A0<u></u><u></u></p>
</div>
<div>
<p class=3D"MsoNormal">=C2=A0 =C2=A0method with the outer tunnel and ensure=
 that a man-in-the-middle attack=C2=A0<u></u><u></u></p>
</div>
<div>
<p class=3D"MsoNormal">=C2=A0 =C2=A0has not been attempted.<u></u><u></u></=
p>
</div>
<div>
<p class=3D"MsoNormal"><u></u>=C2=A0<u></u></p>
</div>
<div>
<p class=3D"MsoNormal">Section 4.2.11 says:<u></u><u></u></p>
</div>
<div>
<p class=3D"MsoNormal"><u></u>=C2=A0<u></u></p>
</div>
<p class=3D"MsoNormal">=C2=A0 =C2=A0The Intermediate-Result TLV provides su=
pport for acknowledged<u></u><u></u></p>
<div>
<p class=3D"MsoNormal">=C2=A0 =C2=A0intermediate Success and Failure messag=
es between multiple=C2=A0<u></u><u></u></p>
</div>
<div>
<p class=3D"MsoNormal">=C2=A0 =C2=A0inner EAP methods within EAP.<u></u><u>=
</u></p>
<div>
<p class=3D"MsoNormal"><u></u>=C2=A0<u></u></p>
</div>
<div>
<p class=3D"MsoNormal">It should say:<u></u><u></u></p>
</div>
<div>
<p class=3D"MsoNormal"><u></u>=C2=A0<u></u></p>
</div>
<div>
<p class=3D"MsoNormal">=C2=A0 The Intermediate-Result TLV provides support =
for acknowledged=C2=A0<u></u><u></u></p>
</div>
<div>
<p class=3D"MsoNormal">=C2=A0 intermediate Success and Failure messages aft=
er each inner EAP=C2=A0<u></u><u></u></p>
</div>
<div>
<p class=3D"MsoNormal">=C2=A0 authentication method.<u></u><u></u></p>
</div>
</div>
<div>
<p class=3D"MsoNormal"><u></u>=C2=A0<u></u></p>
</div>
<div>
<p class=3D"MsoNormal">Section 4.2.13 says:<u></u><u></u></p>
</div>
<div>
<p class=3D"MsoNormal"><u></u>=C2=A0<u></u></p>
</div>
<p class=3D"MsoNormal">=C2=A0It MUST be included with the Intermediate-Resu=
lt TLV to perform=C2=A0<u></u><u></u></p>
<div>
<p class=3D"MsoNormal">=C2=A0cryptographic binding after each successful EA=
P method in a=C2=A0<u></u><u></u></p>
</div>
<div>
<p class=3D"MsoNormal">=C2=A0sequence of EAP methods, before proceeding wit=
h another inner=C2=A0<u></u><u></u></p>
</div>
<div>
<p class=3D"MsoNormal">=C2=A0EAP method.<u></u><u></u></p>
<div>
<p class=3D"MsoNormal"><u></u>=C2=A0<u></u></p>
</div>
<div>
<p class=3D"MsoNormal">It should say:<u></u><u></u></p>
</div>
<div>
<p class=3D"MsoNormal"><u></u>=C2=A0<u></u></p>
</div>
<div>
<p class=3D"MsoNormal">=C2=A0It MUST be included with the Intermediate-Resu=
lt TLV to perform<u></u><u></u></p>
</div>
<div>
<p class=3D"MsoNormal">=C2=A0cryptographic binding after each successful EA=
P authentication=C2=A0<u></u><u></u></p>
</div>
<div>
<p class=3D"MsoNormal">=C2=A0method in a sequence of EAP methods, before pr=
oceeding with=C2=A0<u></u><u></u></p>
</div>
<div>
<p class=3D"MsoNormal">=C2=A0another inner EAP method.<u></u><u></u></p>
</div>
</div>
<div>
<p class=3D"MsoNormal"><u></u>=C2=A0<u></u></p>
</div>
<p class=3D"MsoNormal">Notes:<br>
<br>
TEAP description is somewhat vague in discussion about &quot;EAP methods&qu=
ot; vs. &quot;EAP authentication methods&quot; as it comes to the EAP metho=
ds performed in Phase 2 within the TLS tunnel. RFC 3748 defines Identity re=
quest/response as an EAP method. However, this method
 is not an &quot;authentication method&quot; which is a special case of an =
method where the Type is 4 or greater.<br>
<br>
RFC 7170 uses correct terminology in the first paragraph of Section 3.3.1 w=
hen talking about multiple authentication methods not being allowed by RFC =
3748 in a single EAP conversation. However, many, but not all, of the follo=
wing &quot;[EAP] method&quot; instances are
 actually referring to &quot;[EAP] authentication method&quot;. This result=
s in incorrect claims on when the Intermediate-Result TLV and Crypto-Bindin=
g TLV are used. They are not used after an EAP non-authentication method li=
ke Identity (e.g., see the example in C.3);
 they are used after each EAP authentication method like EAP-pwd.<br>
<br>
Furthermore, the comment about &quot;more than one method is going to be ex=
ecuted in the tunnel&quot; does not sound accurate. This applies even if on=
ly a single EAP authentication method is executed in the tunnel (Identity m=
ethod is not required to be executed). The
 proposed text in this errata entry addresses these two issues in Section 3=
.3.1. The following additional changes would be needed to make rest of the =
specification use the terms more accurately:<br>
<br>
3.3.3: &quot;after each successful EAP method&quot; --&gt; &quot;after each=
 successful EAP authentication method&quot;<br>
3.8.3: &quot;completion of the EAP method&quot; --&gt; &quot;completion of =
the EAP authentication method&quot;<br>
4.2.11: &quot;between multiple inner EAP methods within EAP&quot; --&gt; &q=
uot;after each inner EAP authentication method&quot;<br>
4.2.13: &quot;after each successful EAP method&quot; --&gt; &quot;after eac=
h successful EAP authentication method&quot;<u></u><u></u></p>
</div>
</div>

</blockquote></div>

--000000000000feb64b05b243c504--


From nobody Thu Oct 22 08:08:55 2020
Return-Path: <lear@cisco.com>
X-Original-To: emu@ietfa.amsl.com
Delivered-To: emu@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 8A7063A0FBA for <emu@ietfa.amsl.com>; Thu, 22 Oct 2020 08:08:53 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -9.6
X-Spam-Level: 
X-Spam-Status: No, score=-9.6 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIMWL_WL_MED=-0.001, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, DKIM_VALID_EF=-0.1, HTML_MESSAGE=0.001, SPF_PASS=-0.001, URIBL_BLOCKED=0.001, USER_IN_DEF_DKIM_WL=-7.5] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (1024-bit key) header.d=cisco.com
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 44gBQa8zTbGn for <emu@ietfa.amsl.com>; Thu, 22 Oct 2020 08:08:51 -0700 (PDT)
Received: from aer-iport-3.cisco.com (aer-iport-3.cisco.com [173.38.203.53]) (using TLSv1.2 with cipher DHE-RSA-SEED-SHA (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 79F103A0F00 for <emu@ietf.org>; Thu, 22 Oct 2020 08:08:51 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=cisco.com; i=@cisco.com; l=8129; q=dns/txt; s=iport; t=1603379331; x=1604588931; h=from:message-id:mime-version:subject:date:in-reply-to:cc: to:references; bh=PGtQR1ibJfdSPgiV1JDEmZSB/TeFhTF4J9JmqbluaGk=; b=bm3PbsqblICYOsnNTPkMPMfpEiUaD7sba9xnaVELu6sL7xo06cnylGDB 9PWdKPClZFOcpcoZkN/ml7RC4fdGWJLZMXUvZmV9n1tQMwzareL5UksIK I+YWyCbnO8x2yU347+w5sXGFJZ3nfz+Odq0aRaeLQUd0JPELKU3ufdV/s s=;
X-IPAS-Result: =?us-ascii?q?A0DUAgAioJFf/xbLJq1gHAEBAQEBAQcBARIBAQQEAQFAg?= =?us-ascii?q?U+BI1iBH1UBMiyNQYgWlAuGMYFpCwEBAQ0BARgBCgwEAQGESgKCCiY4EwIDA?= =?us-ascii?q?QEBAwIDAQEBAQUBAQECAQYEbYVhDIVyAQEBAwEBAWwCCQULCxgnBycfEQYTg?= =?us-ascii?q?yYBglwgD7IHdIE0hVeEYQaBOIwbgTmCACZrJxyCTT6CXAEBgSoBEgGDa4IsB?= =?us-ascii?q?JARp3SCdIMWkWeFfAMfgxc5iVSFII8asBWDXgIEBgUCFYFrI2dwMxoIGxU7K?= =?us-ascii?q?gGCPj4SGQ2PRAECh12FRD8DMDgCBgoBAQMJjkgBAQ?=
X-IronPort-Anti-Spam-Filtered: true
X-IronPort-AV: E=Sophos; i="5.77,404,1596499200"; d="scan'208,217"; a="28124871"
Received: from aer-iport-nat.cisco.com (HELO aer-core-1.cisco.com) ([173.38.203.22]) by aer-iport-3.cisco.com with ESMTP/TLS/DHE-RSA-SEED-SHA; 22 Oct 2020 15:08:27 +0000
Received: from [10.61.173.192] ([10.61.173.192]) by aer-core-1.cisco.com (8.15.2/8.15.2) with ESMTPS id 09MF8O3n004850 (version=TLSv1.2 cipher=DHE-RSA-AES256-GCM-SHA384 bits=256 verify=NO); Thu, 22 Oct 2020 15:08:25 GMT
From: Eliot Lear <lear@cisco.com>
Message-Id: <AD94F3FF-31A7-4F44-95F7-6A7E70FA8D27@cisco.com>
Content-Type: multipart/alternative; boundary="Apple-Mail=_902098D2-4A40-4E6C-A419-4ED622A207C5"
Mime-Version: 1.0 (Mac OS X Mail 13.4 \(3608.120.23.2.4\))
Date: Thu, 22 Oct 2020 17:08:23 +0200
In-Reply-To: <AM0PR08MB371647618F993B8C5BA6EB5FFA1C0@AM0PR08MB3716.eurprd08.prod.outlook.com>
Cc: "emu@ietf.org" <emu@ietf.org>
To: Hannes Tschofenig <Hannes.Tschofenig@arm.com>
References: <AM0PR08MB371647618F993B8C5BA6EB5FFA1C0@AM0PR08MB3716.eurprd08.prod.outlook.com>
X-Mailer: Apple Mail (2.3608.120.23.2.4)
X-Outbound-SMTP-Client: 10.61.173.192, [10.61.173.192]
X-Outbound-Node: aer-core-1.cisco.com
Archived-At: <https://mailarchive.ietf.org/arch/msg/emu/-IFaiKDdloonb4LGwXoIjjJ1VH8>
Subject: Re: [Emu] draft-ietf-emu-eap-tls13-11: OCSP Stapling
X-BeenThere: emu@ietf.org
X-Mailman-Version: 2.1.29
Precedence: list
List-Id: "EAP Methods Update \(EMU\)" <emu.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/emu>, <mailto:emu-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/emu/>
List-Post: <mailto:emu@ietf.org>
List-Help: <mailto:emu-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/emu>, <mailto:emu-request@ietf.org?subject=subscribe>
X-List-Received-Date: Thu, 22 Oct 2020 15:08:54 -0000

--Apple-Mail=_902098D2-4A40-4E6C-A419-4ED622A207C5
Content-Transfer-Encoding: quoted-printable
Content-Type: text/plain;
	charset=us-ascii

+1.  How does anyone even do OCSP without having first gotten onto the =
network?

Eliot

> On 21 Oct 2020, at 11:02, Hannes Tschofenig =
<Hannes.Tschofenig@arm.com> wrote:
>=20
> Hi all,=20
> =20
> this draft mandates OCSCP stapling (for use with TLS 1.3 in EAP-TLS) =
and I believe this is a problem for implementations. This extra burden =
is IMHO unjustified. For the type of deployments where EAP is used there =
is no need for a mandatory certificate revocation checking with OCSP.
> =20
> Having it optional, like the use of many other TLS extensions, is fine =
for me. FWIW even TLS 1.3, which is used in a more generic environment, =
does not mandate the use of OCSP stapling.
> =20
> This requirement will make the problem described in =
draft-ietf-emu-eaptlscert worse. I am sure the authors are aware of this =
fact since they are also co-authors of draft-ietf-emu-eaptlscert.
> =20
> Ciao
> Hannes
> IMPORTANT NOTICE: The contents of this email and any attachments are =
confidential and may also be privileged. If you are not the intended =
recipient, please notify the sender immediately and do not disclose the =
contents to any other person, use it for any purpose, or store or copy =
the information in any medium. Thank you. =
_______________________________________________
> Emu mailing list
> Emu@ietf.org <mailto:Emu@ietf.org>
> https://www.ietf.org/mailman/listinfo/emu =
<https://www.ietf.org/mailman/listinfo/emu>

--Apple-Mail=_902098D2-4A40-4E6C-A419-4ED622A207C5
Content-Transfer-Encoding: quoted-printable
Content-Type: text/html;
	charset=us-ascii

<html><head><meta http-equiv=3D"Content-Type" content=3D"text/html; =
charset=3Dus-ascii"></head><body style=3D"word-wrap: break-word; =
-webkit-nbsp-mode: space; line-break: after-white-space;" class=3D"">+1. =
&nbsp;How does anyone even do OCSP without having first gotten onto the =
network?<div class=3D""><br class=3D""></div><div =
class=3D"">Eliot</div><div class=3D""><br class=3D""><div><blockquote =
type=3D"cite" class=3D""><div class=3D"">On 21 Oct 2020, at 11:02, =
Hannes Tschofenig &lt;<a href=3D"mailto:Hannes.Tschofenig@arm.com" =
class=3D"">Hannes.Tschofenig@arm.com</a>&gt; wrote:</div><br =
class=3D"Apple-interchange-newline"><div class=3D""><div =
class=3D"WordSection1" style=3D"page: WordSection1; caret-color: rgb(0, =
0, 0); font-family: Helvetica; font-size: 16px; font-style: normal; =
font-variant-caps: normal; font-weight: normal; letter-spacing: normal; =
text-align: start; text-indent: 0px; text-transform: none; white-space: =
normal; word-spacing: 0px; -webkit-text-stroke-width: 0px; =
text-decoration: none;"><div style=3D"margin: 0in; font-size: 11pt; =
font-family: Calibri, sans-serif;" class=3D"">Hi all,<span =
class=3D"Apple-converted-space">&nbsp;</span><o:p =
class=3D""></o:p></div><div style=3D"margin: 0in; font-size: 11pt; =
font-family: Calibri, sans-serif;" class=3D""><o:p =
class=3D"">&nbsp;</o:p></div><div style=3D"margin: 0in; font-size: 11pt; =
font-family: Calibri, sans-serif;" class=3D"">this draft mandates OCSCP =
stapling (for use with TLS 1.3 in EAP-TLS) and I believe this is a =
problem for implementations. This extra burden is IMHO unjustified. For =
the type of deployments where EAP is used there is no need for a =
mandatory certificate revocation checking with OCSP.<o:p =
class=3D""></o:p></div><div style=3D"margin: 0in; font-size: 11pt; =
font-family: Calibri, sans-serif;" class=3D""><o:p =
class=3D"">&nbsp;</o:p></div><div style=3D"margin: 0in; font-size: 11pt; =
font-family: Calibri, sans-serif;" class=3D"">Having it optional, like =
the use of many other TLS extensions, is fine for me. FWIW even TLS 1.3, =
which is used in a more generic environment, does not mandate the use of =
OCSP stapling.<o:p class=3D""></o:p></div><div style=3D"margin: 0in; =
font-size: 11pt; font-family: Calibri, sans-serif;" class=3D""><o:p =
class=3D"">&nbsp;</o:p></div><div style=3D"margin: 0in; font-size: 11pt; =
font-family: Calibri, sans-serif;" class=3D"">This requirement will make =
the problem described in draft-ietf-emu-eaptlscert worse. I am sure the =
authors are aware of this fact since they are also co-authors of =
draft-ietf-emu-eaptlscert.<o:p class=3D""></o:p></div><div =
style=3D"margin: 0in; font-size: 11pt; font-family: Calibri, =
sans-serif;" class=3D""><o:p class=3D"">&nbsp;</o:p></div><div =
style=3D"margin: 0in; font-size: 11pt; font-family: Calibri, =
sans-serif;" class=3D"">Ciao<o:p class=3D""></o:p></div><div =
style=3D"margin: 0in; font-size: 11pt; font-family: Calibri, =
sans-serif;" class=3D"">Hannes<o:p class=3D""></o:p></div></div><span =
style=3D"caret-color: rgb(0, 0, 0); font-family: Helvetica; font-size: =
16px; font-style: normal; font-variant-caps: normal; font-weight: =
normal; letter-spacing: normal; text-align: start; text-indent: 0px; =
text-transform: none; white-space: normal; word-spacing: 0px; =
-webkit-text-stroke-width: 0px; text-decoration: none; float: none; =
display: inline !important;" class=3D"">IMPORTANT NOTICE: The contents =
of this email and any attachments are confidential and may also be =
privileged. If you are not the intended recipient, please notify the =
sender immediately and do not disclose the contents to any other person, =
use it for any purpose, or store or copy the information in any medium. =
Thank you. _______________________________________________</span><br =
style=3D"caret-color: rgb(0, 0, 0); font-family: Helvetica; font-size: =
16px; font-style: normal; font-variant-caps: normal; font-weight: =
normal; letter-spacing: normal; text-align: start; text-indent: 0px; =
text-transform: none; white-space: normal; word-spacing: 0px; =
-webkit-text-stroke-width: 0px; text-decoration: none;" class=3D""><span =
style=3D"caret-color: rgb(0, 0, 0); font-family: Helvetica; font-size: =
16px; font-style: normal; font-variant-caps: normal; font-weight: =
normal; letter-spacing: normal; text-align: start; text-indent: 0px; =
text-transform: none; white-space: normal; word-spacing: 0px; =
-webkit-text-stroke-width: 0px; text-decoration: none; float: none; =
display: inline !important;" class=3D"">Emu mailing list</span><br =
style=3D"caret-color: rgb(0, 0, 0); font-family: Helvetica; font-size: =
16px; font-style: normal; font-variant-caps: normal; font-weight: =
normal; letter-spacing: normal; text-align: start; text-indent: 0px; =
text-transform: none; white-space: normal; word-spacing: 0px; =
-webkit-text-stroke-width: 0px; text-decoration: none;" class=3D""><a =
href=3D"mailto:Emu@ietf.org" style=3D"font-family: Helvetica; font-size: =
16px; font-style: normal; font-variant-caps: normal; font-weight: =
normal; letter-spacing: normal; orphans: auto; text-align: start; =
text-indent: 0px; text-transform: none; white-space: normal; widows: =
auto; word-spacing: 0px; -webkit-text-size-adjust: auto; =
-webkit-text-stroke-width: 0px;" class=3D"">Emu@ietf.org</a><br =
style=3D"caret-color: rgb(0, 0, 0); font-family: Helvetica; font-size: =
16px; font-style: normal; font-variant-caps: normal; font-weight: =
normal; letter-spacing: normal; text-align: start; text-indent: 0px; =
text-transform: none; white-space: normal; word-spacing: 0px; =
-webkit-text-stroke-width: 0px; text-decoration: none;" class=3D""><a =
href=3D"https://www.ietf.org/mailman/listinfo/emu" style=3D"font-family: =
Helvetica; font-size: 16px; font-style: normal; font-variant-caps: =
normal; font-weight: normal; letter-spacing: normal; orphans: auto; =
text-align: start; text-indent: 0px; text-transform: none; white-space: =
normal; widows: auto; word-spacing: 0px; -webkit-text-size-adjust: auto; =
-webkit-text-stroke-width: 0px;" =
class=3D"">https://www.ietf.org/mailman/listinfo/emu</a></div></blockquote=
></div><br class=3D""></div></body></html>=

--Apple-Mail=_902098D2-4A40-4E6C-A419-4ED622A207C5--


From nobody Thu Oct 22 08:55:39 2020
Return-Path: <joe@salowey.net>
X-Original-To: emu@ietfa.amsl.com
Delivered-To: emu@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 9FD243A00D9 for <emu@ietfa.amsl.com>; Thu, 22 Oct 2020 08:55:37 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.798
X-Spam-Level: 
X-Spam-Status: No, score=-1.798 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, HTML_MESSAGE=0.001, HTTPS_HTTP_MISMATCH=0.1, SPF_HELO_NONE=0.001, SPF_PASS=-0.001, URIBL_BLOCKED=0.001] autolearn=no autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (2048-bit key) header.d=salowey-net.20150623.gappssmtp.com
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 h59x01jVCmgY for <emu@ietfa.amsl.com>; Thu, 22 Oct 2020 08:55:35 -0700 (PDT)
Received: from mail-qt1-x834.google.com (mail-qt1-x834.google.com [IPv6:2607:f8b0:4864:20::834]) (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 4C8243A0A00 for <emu@ietf.org>; Thu, 22 Oct 2020 08:55:21 -0700 (PDT)
Received: by mail-qt1-x834.google.com with SMTP id m65so1395749qte.11 for <emu@ietf.org>; Thu, 22 Oct 2020 08:55:21 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=salowey-net.20150623.gappssmtp.com; s=20150623; h=mime-version:references:in-reply-to:from:date:message-id:subject:to :cc; bh=FGihA4Ta0086Edh2+76doeXwF3ZTO6e4Nlly8mO3oWo=; b=OfNPFbbzh3TmS1O7+PBF6n4+NlurNuJpylwThRqdvo+Pj6xPU+lhjCsmar6GfQ3Y45 +65YIXg8eZ+z23tLBTcoVpqXDCK+t4/w/+GdxDdGuZEywgo9RePKfy3z2wTlaqYFHdQl Qu4Zki6zUo+dbS0zjPGPKR8uIxdOE+p9nKLMDYfoyJ10l+woWJsKmTOd8D9tY5MJ+Ck9 qDXsC4SwJHgGsCjynoIhHP4usLsyZOLUDZWGf4+si+vh6KpgA1OmggwK6r3g6qv9I9r4 dPr1rdcHqiTtFQJPSKXpu5RKAUZLsKD9qUUKKWy6MPlatHLyxIXntz+gnIk0dDUuNn/H HnbQ==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:mime-version:references:in-reply-to:from:date :message-id:subject:to:cc; bh=FGihA4Ta0086Edh2+76doeXwF3ZTO6e4Nlly8mO3oWo=; b=o1pRiGv1MyHZYRp/2e+qoO9QxQFJ8NfOaiD5dQBWNDiKlG45hirmlWItsAbjywkyZL u3ScnDHbyfTCjQFrAnu3izEO1JtkllN/mNEZ7M9n7mOByD6cyhrL38rdaBLK6lfsMBBo AvgvyjTw5UDu7IJPkWyfUzbsX+r2IOziIG/lyqTsZoXoUhN0meVlJxjkUF+Rve2mKpbr oAeuVn9sHkw7K2HK37lj+Rxxz+j4typik5mYGk09tIpa2Qu+tYLTWtWhBQd2/hkej8GF QMFaP93ZTJZvT6MxaV8Yc/QVGWa4EdgoYn4Dxh2X0okOHN9QIMd5LdGqw1+RyCybxnj6 W1Cw==
X-Gm-Message-State: AOAM531XWtb47l7zXj+UTeabz+oRZ0tzyXcc8zTaNExdsK4cfobsgSbd jvkGEuHsDx/e0q3naqYj64KTdJYdEFVxrr9TRTEU5w==
X-Google-Smtp-Source: ABdhPJz+5cBlwcS/fyWyQTjTwA0OAVL1iI0s0Gc3cpfEKg3a8POdqDUmD2q5o61QLK8z+tsgvsmsZmehAKm0hUA8JmE=
X-Received: by 2002:aed:243b:: with SMTP id r56mr2732295qtc.249.1603382120210;  Thu, 22 Oct 2020 08:55:20 -0700 (PDT)
MIME-Version: 1.0
References: <CAOgPGoBay+GG=F8WV0gLOOwLtGdGALGw_cM2JoAnXOtmGq7A+w@mail.gmail.com> <CH2PR21MB138143E929DAFE3C893D8144D11C0@CH2PR21MB1381.namprd21.prod.outlook.com> <CAOgPGoAtcm+Br+YkCyTtg5nJjqO7LGSo77b+CD4+Ba05azafew@mail.gmail.com> <CH2PR21MB13815BCEDC846D7C440AD564D11C0@CH2PR21MB1381.namprd21.prod.outlook.com> <CAOgPGoDTC-qiHOXFTJd7aMn2To7ySzBcx+iQMB9m5foC1bFxzw@mail.gmail.com> <CABXxEz8SRvMXdMR8_cPfvWdauJZwCjnd=7ytnVZ+_L-sB48wvw@mail.gmail.com>
In-Reply-To: <CABXxEz8SRvMXdMR8_cPfvWdauJZwCjnd=7ytnVZ+_L-sB48wvw@mail.gmail.com>
From: Joseph Salowey <joe@salowey.net>
Date: Thu, 22 Oct 2020 08:55:08 -0700
Message-ID: <CAOgPGoCsWy-uhYeeHCDUaazjAwfWtr_zkS5CUoX8+baASahFEg@mail.gmail.com>
To: Oleg Pekar <oleg.pekar.2017@gmail.com>
Cc: EMU WG <emu@ietf.org>, Jorge Vergara <jovergar=40microsoft.com@dmarc.ietf.org>,  Jouni Malinen <j@w1.fi>
Content-Type: multipart/alternative; boundary="000000000000b6f9e405b2447dbb"
Archived-At: <https://mailarchive.ietf.org/arch/msg/emu/T6vg6WiVx10qIvr1AzpLwUN9yY8>
Subject: Re: [Emu] Proposed resolution for TEAP errata for 5128
X-BeenThere: emu@ietf.org
X-Mailman-Version: 2.1.29
Precedence: list
List-Id: "EAP Methods Update \(EMU\)" <emu.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/emu>, <mailto:emu-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/emu/>
List-Post: <mailto:emu@ietf.org>
List-Help: <mailto:emu-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/emu>, <mailto:emu-request@ietf.org?subject=subscribe>
X-List-Received-Date: Thu, 22 Oct 2020 15:55:38 -0000

--000000000000b6f9e405b2447dbb
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable

On Thu, Oct 22, 2020 at 6:59 AM Oleg Pekar <oleg.pekar.2017@gmail.com>
wrote:

> Hi all,
> Speaking about both errata 5127 and 5128, I think we need to align all ke=
y
> derivation calls in TEAP RFC with the same rule/format to make the RFC
> easier to understand. This can be achieved by introducing a unified singl=
e
> PRF function that will be called from all the relevant RFC locations. For
> me it sounds better than if we align just part of KDF calls with RFC 5295
> (where the output length is included into seed). Also: in some KDF calls =
we
> do have optional data and in some no. This could be also unified.
>
> [Joe] I don't think this was the original intent of the document.  The
IMSK derivation referenced 5295 while the others just reference the TLS
PRF.  I think to unify them would require a document update and I'm not
sure what we would gain especially if we have implementations that do
this.


> So I would suggest introducing:
> TEAP-PRF (secret, key label, optional data, length) =3D TLS-PRF(secret, k=
ey
> label | 0x00 | optional data, length)
> where a single byte 0x00 is used for no optional data, length is a 2-octe=
t
> unsigned integer in network byte order.
>
> [Joe] I don't think that 5295 specifies that a 0x00 is used to represent
no optional data.  Did you see this in the spec? It may be ambiguous, but I
think the intent is that optional data is just omitted if it is not
provided.



> Then:
> IMSK =3D First 32 octets of TEAP-PRF(EMSK, "TEAPbindkey@ietf.org", 64) =
=3D
> TLS-PRF(EMSK, "TEAPbindkey@ietf.org" | 0x00 | 0x00 | 0x00 | 0x40)
> IMCK[j] =3D TEAP-PRF(S-IMCK[j-1], "Inner Methods Compound Keys", IMSK[j],
> 60) =3D TLS-PRF(S-IMCK[j-1], "Inner Methods Compound Keys" | 0x00 | IMSK[=
j] |
> 0x00 | 0x3C)
> MSK =3D TEAP-PRF(S-IMCK[j], "Session Key Generating Function=E2=80=9D, 64=
) =3D
> TLS-PRF(S-IMCK[j], "Session Key Generating Function" | 0x00 | 0x00 | 0x00=
 |
> 0x40)
> EMSK =3D TEAP-PRF(S-IMCK[j], =E2=80=9DExtended Session Key Generating Fun=
ction=E2=80=9D, 64)
> =3D TLS-PRF(S-IMCK[j], "Extended Session Key Generating Function" | 0x00 =
|
> 0x00 | 0x00 | 0x40)
>
> This may change the existing implementation but will make it more clear -
> need to create and call just one KDF function.
>
> We can remove 0x00 that comes after the key label - while it is required
> by RFC 5295. But there the key label is also ASCII printable string. Joe,
> do you remember what was the motivation to put 0x00 after the key label
> parameter?
>

[Joe] the null after the key label is to provide a delimiter between the
key label and optional data.  Since the optional data can be arbitrary
content the null prevents two different lablels with specially crafted
optional data from deriving the same key.


>
> Oleg
>
>
> On Thu, Oct 22, 2020 at 2:54 AM Joseph Salowey <joe@salowey.net> wrote:
>
>> (I accidentally dropped this list from the conversation)
>>
>> On Wed, Oct 21, 2020 at 4:48 PM Jorge Vergara <jovergar@microsoft.com>
>> wrote:
>>
>>> >[Joe] Yes this is a concern and I think your interpretation of the
>>> current document is also valid.  There may be more than one
>>> implementation.  So what you implemented was:
>>>
>>> >
>>>
>>> >IMCK[j] =3D TLS-PRF(S-IMCK[j-1], "Inner Methods Compound Keys", IMSK[j=
])
>>> =3D P_<hash>(S-IMCK[j-1], "Inner Methods Compound Keys" | IMSK[j])
>>>
>>>
>>>
>>> Yes, this is what I implemented. As you mentioned, there are multiple
>>> possible interpretations of this since the TEAP usage is incorrect.
>>> However, my implementation does interop with at least 2 large vendor
>>> implementations. If the implementations were using different calculatio=
ns
>>> here, the Wi-Fi/Ethernet connections that depend on the MSK would fail.=
 But
>>> since connections work, I can assume we are all using the same
>>> implementation and arriving at the same MSK. Cisco is one of the
>>> implementations that I have tested against which is why I was hoping Ol=
eg
>>> may offer more context as to what he has seen.
>>>
>>>
>>>
>> [Joe] I can hope Jouni can chime in on this as well.  I think the
>> original intent was to not include the length as is your suggestion.
>>
>>
>>
>>> >[Joe] Does the revision in 5167 match you implementation ( I don't
>>> think Jouni's comment changes the underly calculation, just its
>>> representation)?
>>>
>>>
>>>
>>> I have not implemented this portion of the RFC as I found it too unclea=
r
>>> to work with. Thus I can=E2=80=99t comment on what implementations may =
be doing.
>>> However, I agree with the current revision in 5167 as the most natural
>>> interpretation. If others have implemented this portion of the RFC then
>>> certainly their comments would be welcome.
>>>
>>>
>>> By the way, we=E2=80=99ve dropped the EMU group on our replies here =E2=
=80=93 not sure
>>> if intentional or not.
>>>
>>>
>>>
>>> Jorge Vergara
>>>
>>>
>>>
>>> *From:* Joseph Salowey <joe@salowey.net>
>>> *Sent:* Wednesday, October 21, 2020 4:36 PM
>>> *To:* Jorge Vergara <jovergar@microsoft.com>
>>> *Subject:* Re: Proposed resolution for TEAP errata for 5128
>>>
>>>
>>>
>>>
>>>
>>>
>>>
>>> On Wed, Oct 21, 2020 at 3:20 PM Jorge Vergara <jovergar@microsoft.com>
>>> wrote:
>>>
>>> In theory I agree this is a possible resolution. However, this doesn=E2=
=80=99t
>>> match any of the current TEAP implementations that I am aware of. Perha=
ps
>>> Oleg can weigh in as well in terms of what he=E2=80=99s seen.
>>>
>>>
>>>
>>> I believe all current implementations treat 60 as the desired output
>>> length without treating as a seed. In terms of P_<hash>, this means
>>> implementations are performing the calculation without a seed.
>>>
>>>
>>>
>>> RFC 5246 defines the TLS 1.2 PRF as:
>>>
>>> PRF(secret, label, seed) =3D P_<hash>(secret, label + seed)
>>>
>>>
>>>
>>> So the calculation implementations are currently performing with an
>>> empty seed ends up as:
>>>
>>> P_<hash>(secret, label)
>>>
>>>
>>>
>>> Note that in RFC 5295, the length *is* explicitly mentioned as being
>>> concatenated with the label
>>>
>>> USRK =3D KDF(EMSK, key label | "\0" | optional data | length)
>>>
>>>
>>>
>>> RFC 5295 is mentioned earlier in the TEAP RFC, in the section covered b=
y
>>> errata 5127. *However* it is not mentioned in this portion of the RFC.
>>> Since this calculation is not on an EMSK, I do not believe RFC 2395 app=
lies
>>> and this is likely why implementations went with the seedless
>>> P_<hash>(secret, label) calculation instead.
>>>
>>>
>>>
>>> Is there concern about updating the RFC in a way that breaks existing
>>> implementations?
>>>
>>>
>>>
>>> [Joe] Yes this is a concern and I think your interpretation of the
>>> current document is also valid.  There may be more than one
>>> implementation.  So what you implemented was:
>>>
>>>
>>>
>>> IMCK[j] =3D TLS-PRF(S-IMCK[j-1], "Inner Methods Compound Keys", IMSK[j]=
)
>>> =3D P_<hash>(S-IMCK[j-1], "Inner Methods Compound Keys" | IMSK[j])
>>>
>>>
>>>
>>> taken out to 60 bytes.  The problem is that the TEAP spec references a
>>> TLS-PRF in a way that it does not define.  I think the errata points ou=
t
>>> the definition that should be used:
>>>
>>>
>>>
>>> PRF(secret, label, seed) =3D P_<hash>(secret, label + seed)
>>>
>>>
>>>
>>> That does not include length so the 60 in the original definition is
>>> ambiguous.   The new text would then be something like:
>>>
>>>
>>>
>>> IMCK[j] =3D TLS-PRF(S-IMCK[j-1], "Inner Methods Compound Keys", IMSK[j]=
)
>>> to generate a length of 60 bytes
>>>
>>>
>>>
>>> Does the revision in 5167 match you implementation ( I don't think
>>> Jouni's comment changes the underly calculation, just its representatio=
n)?
>>>
>>>
>>>
>>>
>>>
>>>
>>>
>>>
>>>
>>>
>>>
>>> Jorge Vergara
>>>
>>>
>>>
>>> *From:* Joseph Salowey <joe@salowey.net>
>>> *Sent:* Wednesday, October 21, 2020 2:34 PM
>>> *To:* EMU WG <emu@ietf.org>; Jouni Malinen <j@w1.fi>; Jorge Vergara <
>>> jovergar@microsoft.com>; Oleg Pekar (olpekar) <olpekar@cisco.com>
>>> *Subject:* Proposed resolution for TEAP errata for 5128
>>>
>>>
>>>
>>> Errata 5128: https://www.rfc-editor.org/errata/eid5128
>>> <https://nam06.safelinks.protection.outlook.com/?url=3Dhttps%3A%2F%2Fww=
w.rfc-editor.org%2Ferrata%2Feid5128&data=3D04%7C01%7Cjovergar%40microsoft.c=
om%7C38c27add2cb64a06310108d8761a22d3%7C72f988bf86f141af91ab2d7cd011db47%7C=
1%7C0%7C637389201909062787%7CUnknown%7CTWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQ=
IjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D%7C1000&sdata=3DXudZt9FPh4jOBFQj0=
1SQysnhX4p7G%2BflW2Pn2yIaJRM%3D&reserved=3D0>
>>>
>>> Proposed State: Verified
>>>
>>> Revision:
>>>
>>>
>>>
>>> Section 5.2. says
>>>
>>>
>>> IMCK[j] =3D TLS-PRF(S-IMCK[j-1], "Inner Methods Compound Keys",
>>>                 IMSK[j], 60)
>>>
>>> It should say:
>>>
>>> IMCK[j] =3D TLS-PRF(S-IMCK[j-1], "Inner Methods Compound Keys", IMSK[j]=
 |
>>> 60)
>>>
>>> Note:
>>>
>>> According to
>>>
>>> RFC5246 The Transport Layer Security (TLS) Protocol Version 1.2
>>>
>>> 5. HMAC and the Pseudorandom Function
>>>
>>> "TLS's PRF is created by applying P_hash to the secret as:
>>>
>>> PRF(secret, label, seed) =3D P_<hash>(secret, label + seed)"
>>>
>>>
>>>
>>> In terms of P_<hash> this would look like the following with the length
>>> represented as a 2 byte value in network byte order:
>>>
>>>
>>>
>>> IMCK[j] =3D P_<hash>(S-IMCK[j-1], "Inner Methods Compound Keys" | IMSK[=
j]
>>> | 0x00 | 0x3C)
>>>
>>>
>>>
>>>
>>>
>>>

--000000000000b6f9e405b2447dbb
Content-Type: text/html; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable

<div dir=3D"ltr"><div dir=3D"ltr"><br></div><br><div class=3D"gmail_quote">=
<div dir=3D"ltr" class=3D"gmail_attr">On Thu, Oct 22, 2020 at 6:59 AM Oleg =
Pekar &lt;<a href=3D"mailto:oleg.pekar.2017@gmail.com">oleg.pekar.2017@gmai=
l.com</a>&gt; wrote:<br></div><blockquote class=3D"gmail_quote" style=3D"ma=
rgin:0px 0px 0px 0.8ex;border-left:1px solid rgb(204,204,204);padding-left:=
1ex"><div dir=3D"ltr"><div>Hi all,</div><div>Speaking about both errata 512=
7 and 5128, I think we need to align all key derivation calls in TEAP RFC w=
ith the same rule/format to make the RFC easier to understand. This can be =
achieved by introducing a unified single PRF function that will be called f=
rom all the relevant RFC locations. For me it sounds better than if we alig=
n just part of KDF calls with RFC 5295 (where the output length is included=
 into seed). Also: in some KDF calls we do have optional data and in some n=
o. This could be also unified.=C2=A0</div><div><br></div></div></blockquote=
><div>[Joe] I don&#39;t think this was the original intent of the document.=
=C2=A0 The IMSK derivation referenced 5295 while the others just reference =
the TLS PRF.=C2=A0 I think to unify them would require a document update an=
d I&#39;m not sure what we would gain especially if we have implementations=
 that do this.=C2=A0=C2=A0</div><div>=C2=A0</div><blockquote class=3D"gmail=
_quote" style=3D"margin:0px 0px 0px 0.8ex;border-left:1px solid rgb(204,204=
,204);padding-left:1ex"><div dir=3D"ltr"><div></div><div>So I would suggest=
 introducing:</div><div>TEAP-PRF (secret, key label, optional data, length)=
 =3D TLS-PRF(secret, key label | 0x00 | optional data, length)<br></div><di=
v>where a single byte 0x00 is used for no optional data, length is a 2-octe=
t unsigned integer in network byte order.<br></div><div><br></div></div></b=
lockquote><div>[Joe] I don&#39;t think that 5295 specifies that a 0x00 is u=
sed to represent no optional data.=C2=A0 Did you see this in the spec? It m=
ay be ambiguous, but I think the intent is that optional data is just omitt=
ed if it is not provided.=C2=A0</div><div><br></div><div>=C2=A0</div><block=
quote class=3D"gmail_quote" style=3D"margin:0px 0px 0px 0.8ex;border-left:1=
px solid rgb(204,204,204);padding-left:1ex"><div dir=3D"ltr"><div></div><di=
v>Then:</div><div>IMSK =3D First 32 octets of TEAP-PRF(EMSK, &quot;<a href=
=3D"mailto:TEAPbindkey@ietf.org" target=3D"_blank">TEAPbindkey@ietf.org</a>=
&quot;, 64) =3D TLS-PRF(EMSK, &quot;<a href=3D"mailto:TEAPbindkey@ietf.org"=
 target=3D"_blank">TEAPbindkey@ietf.org</a>&quot; | 0x00 | 0x00 | 0x00 | 0x=
40)<br>IMCK[j] =3D TEAP-PRF(S-IMCK[j-1], &quot;Inner Methods Compound Keys&=
quot;, IMSK[j], 60) =3D TLS-PRF(S-IMCK[j-1], &quot;Inner Methods Compound K=
eys&quot; | 0x00 | IMSK[j] | 0x00 | 0x3C)<br>MSK =3D TEAP-PRF(S-IMCK[j], &q=
uot;Session Key Generating Function=E2=80=9D, 64) =3D TLS-PRF(S-IMCK[j], &q=
uot;Session Key Generating Function&quot; | 0x00 | 0x00 | 0x00 | 0x40)<br>E=
MSK =3D TEAP-PRF(S-IMCK[j], =E2=80=9DExtended Session Key Generating Functi=
on=E2=80=9D, 64) =3D TLS-PRF(S-IMCK[j], &quot;Extended Session Key Generati=
ng Function&quot; | 0x00 | 0x00 | 0x00 | 0x40)<br></div><div><br></div><div=
>This may change the existing implementation but will make it more clear - =
need to create and call just one KDF function.</div><div><br></div><div>We =
can remove=C2=A00x00 that comes after the key label - while it is required =
by=C2=A0RFC 5295. But there=C2=A0the key label is also ASCII printable stri=
ng. Joe, do you remember what was the motivation to put 0x00 after the key =
label parameter?</div></div></blockquote><div><br></div><div>[Joe] the null=
 after the key label is to provide a delimiter between the key label and op=
tional data.=C2=A0 Since the optional data can be arbitrary content the nul=
l prevents two different lablels=C2=A0with specially=C2=A0crafted optional =
data from deriving the same key.=C2=A0=C2=A0</div><div>=C2=A0</div><blockqu=
ote class=3D"gmail_quote" style=3D"margin:0px 0px 0px 0.8ex;border-left:1px=
 solid rgb(204,204,204);padding-left:1ex"><div dir=3D"ltr"><div><br></div><=
div>Oleg</div><div><br></div><div><br></div><div class=3D"gmail_quote"><div=
 dir=3D"ltr" class=3D"gmail_attr">On Thu, Oct 22, 2020 at 2:54 AM Joseph Sa=
lowey &lt;<a href=3D"mailto:joe@salowey.net" target=3D"_blank">joe@salowey.=
net</a>&gt; wrote:<br></div><blockquote class=3D"gmail_quote" style=3D"marg=
in:0px 0px 0px 0.8ex;border-left:1px solid rgb(204,204,204);padding-left:1e=
x"><div dir=3D"ltr"><div>(I accidentally=C2=A0dropped this list from the co=
nversation)</div><br><div class=3D"gmail_quote"><div dir=3D"ltr" class=3D"g=
mail_attr">On Wed, Oct 21, 2020 at 4:48 PM Jorge Vergara &lt;<a href=3D"mai=
lto:jovergar@microsoft.com" target=3D"_blank">jovergar@microsoft.com</a>&gt=
; wrote:<br></div><blockquote class=3D"gmail_quote" style=3D"margin:0px 0px=
 0px 0.8ex;border-left:1px solid rgb(204,204,204);padding-left:1ex">





<div lang=3D"EN-US">
<div>
<p class=3D"MsoNormal">&gt;[Joe] Yes this is a concern and I think your=C2=
=A0interpretation of the current document is also valid.=C2=A0 There may be=
 more than one implementation.=C2=A0 So what you implemented was:<u></u><u>=
</u></p>
<p class=3D"MsoNormal">&gt;<u></u>=C2=A0<u></u></p>
<p class=3D"MsoNormal">&gt;IMCK[j] =3D TLS-PRF(S-IMCK[j-1], &quot;Inner Met=
hods Compound Keys&quot;,=C2=A0<span style=3D"font-size:10.5pt;color:rgb(44=
,67,83)">IMSK[j]) =3D P_&lt;hash&gt;(S-IMCK[j-1], &quot;Inner Methods Compo=
und Keys&quot; | IMSK[j])</span><u></u><u></u></p>
<p class=3D"MsoNormal"><u></u>=C2=A0<u></u></p>
<p class=3D"MsoNormal">Yes, this is what I implemented. As you mentioned, t=
here are multiple possible interpretations of this since the TEAP usage is =
incorrect. However, my implementation does interop with at least 2 large ve=
ndor implementations. If the implementations
 were using different calculations here, the Wi-Fi/Ethernet connections tha=
t depend on the MSK would fail. But since connections work, I can assume we=
 are all using the same implementation and arriving at the same MSK. Cisco =
is one of the implementations that
 I have tested against which is why I was hoping Oleg may offer more contex=
t as to what he has seen.<u></u><u></u></p>
<p class=3D"MsoNormal"><u></u>=C2=A0</p></div></div></blockquote><div>[Joe]=
 I can hope Jouni can chime in on this as well.=C2=A0 I think the original =
intent was to not include the length as is your suggestion.=C2=A0</div><div=
><br></div><div>=C2=A0</div><blockquote class=3D"gmail_quote" style=3D"marg=
in:0px 0px 0px 0.8ex;border-left:1px solid rgb(204,204,204);padding-left:1e=
x"><div lang=3D"EN-US"><div><p class=3D"MsoNormal"><u></u></p>
<p class=3D"MsoNormal">&gt;[Joe]<span style=3D"font-size:10.5pt;color:rgb(4=
4,67,83)"> Does the revision in 5167 match you implementation ( I don&#39;t=
 think Jouni&#39;s=C2=A0comment changes the underly=C2=A0calculation, just =
its representation)?=C2=A0</span><u></u><u></u></p>
<p class=3D"MsoNormal"><u></u>=C2=A0<u></u></p>
<p class=3D"MsoNormal">I have not implemented this portion of the RFC as I =
found it too unclear to work with. Thus I can=E2=80=99t comment on what imp=
lementations may be doing. However, I agree with the current revision in 51=
67 as the most natural interpretation. If
 others have implemented this portion of the RFC then certainly their comme=
nts would be welcome.<u></u><u></u></p>
<p class=3D"MsoNormal"><br><u></u></p></div></div></blockquote><blockquote =
class=3D"gmail_quote" style=3D"margin:0px 0px 0px 0.8ex;border-left:1px sol=
id rgb(204,204,204);padding-left:1ex"><div lang=3D"EN-US"><div><p class=3D"=
MsoNormal"><u></u></p>
<p class=3D"MsoNormal">By the way, we=E2=80=99ve dropped the EMU group on o=
ur replies here =E2=80=93 not sure if intentional or not.<u></u><u></u></p>
<p class=3D"MsoNormal"><u></u>=C2=A0<u></u></p>
<p class=3D"MsoNormal">Jorge Vergara<u></u><u></u></p>
<p class=3D"MsoNormal"><u></u>=C2=A0<u></u></p>
<div style=3D"border-right:none;border-bottom:none;border-left:none;border-=
top:1pt solid rgb(225,225,225);padding:3pt 0in 0in">
<p class=3D"MsoNormal"><b>From:</b> Joseph Salowey &lt;<a href=3D"mailto:jo=
e@salowey.net" target=3D"_blank">joe@salowey.net</a>&gt; <br>
<b>Sent:</b> Wednesday, October 21, 2020 4:36 PM<br>
<b>To:</b> Jorge Vergara &lt;<a href=3D"mailto:jovergar@microsoft.com" targ=
et=3D"_blank">jovergar@microsoft.com</a>&gt;<br>
<b>Subject:</b> Re: Proposed resolution for TEAP errata for 5128<u></u><u><=
/u></p>
</div>
<p class=3D"MsoNormal"><u></u>=C2=A0<u></u></p>
<div>
<div>
<p class=3D"MsoNormal"><u></u>=C2=A0<u></u></p>
</div>
<p class=3D"MsoNormal"><u></u>=C2=A0<u></u></p>
<div>
<div>
<p class=3D"MsoNormal">On Wed, Oct 21, 2020 at 3:20 PM Jorge Vergara &lt;<a=
 href=3D"mailto:jovergar@microsoft.com" target=3D"_blank">jovergar@microsof=
t.com</a>&gt; wrote:<u></u><u></u></p>
</div>
<blockquote style=3D"border-top:none;border-right:none;border-bottom:none;b=
order-left:1pt solid rgb(204,204,204);padding:0in 0in 0in 6pt;margin-left:4=
.8pt;margin-right:0in">
<div>
<div>
<p class=3D"MsoNormal">In theory I agree this is a possible resolution. How=
ever, this doesn=E2=80=99t match any of the current TEAP implementations th=
at I am aware of. Perhaps Oleg can weigh in as well in terms
 of what he=E2=80=99s seen.<u></u><u></u></p>
<p class=3D"MsoNormal">=C2=A0<u></u><u></u></p>
<p class=3D"MsoNormal">I believe all current implementations treat 60 as th=
e desired output length without treating as a seed. In terms of P_&lt;hash&=
gt;, this means implementations are performing the calculation
 without a seed.<u></u><u></u></p>
<p class=3D"MsoNormal">=C2=A0<u></u><u></u></p>
<p class=3D"MsoNormal">RFC 5246 defines the TLS 1.2 PRF as:<u></u><u></u></=
p>
<p class=3D"MsoNormal">PRF(secret, label, seed) =3D P_&lt;hash&gt;(secret, =
label + seed)<u></u><u></u></p>
<p class=3D"MsoNormal">=C2=A0<u></u><u></u></p>
<p class=3D"MsoNormal">So the calculation implementations are currently per=
forming with an empty seed ends up as:<u></u><u></u></p>
<p class=3D"MsoNormal">P_&lt;hash&gt;(secret, label)<u></u><u></u></p>
<p class=3D"MsoNormal">=C2=A0<u></u><u></u></p>
<p class=3D"MsoNormal">Note that in RFC 5295, the length *is* explicitly me=
ntioned as being concatenated with the label<u></u><u></u></p>
<p class=3D"MsoNormal">USRK =3D KDF(EMSK, key label | &quot;\0&quot; | opti=
onal data | length)<u></u><u></u></p>
<p class=3D"MsoNormal">=C2=A0<u></u><u></u></p>
<p class=3D"MsoNormal">RFC 5295 is mentioned earlier in the TEAP RFC, in th=
e section covered by errata 5127. *However* it is not mentioned in this por=
tion of the RFC. Since this calculation is not on
 an EMSK, I do not believe RFC 2395 applies and this is likely why implemen=
tations went with the seedless P_&lt;hash&gt;(secret, label) calculation in=
stead.<u></u><u></u></p>
<p class=3D"MsoNormal">=C2=A0<u></u><u></u></p>
<p class=3D"MsoNormal">Is there concern about updating the RFC in a way tha=
t breaks existing implementations?<u></u><u></u></p>
<p class=3D"MsoNormal">=C2=A0<u></u><u></u></p>
</div>
</div>
</blockquote>
<div>
<p class=3D"MsoNormal">[Joe] Yes this is a concern and I think your=C2=A0in=
terpretation of the current document is also valid.=C2=A0 There may be more=
 than one implementation.=C2=A0 So what you implemented was:<u></u><u></u><=
/p>
</div>
<div>
<p class=3D"MsoNormal"><u></u>=C2=A0<u></u></p>
</div>
<div>
<p class=3D"MsoNormal">IMCK[j] =3D TLS-PRF(S-IMCK[j-1], &quot;Inner Methods=
 Compound Keys&quot;,=C2=A0<span style=3D"font-size:10.5pt;color:rgb(44,67,=
83)">IMSK[j]) =3D P_&lt;hash&gt;(S-IMCK[j-1], &quot;Inner Methods Compound =
Keys&quot; | IMSK[j])</span><u></u><u></u></p>
</div>
<div>
<p class=3D"MsoNormal"><u></u>=C2=A0<u></u></p>
</div>
<div>
<p class=3D"MsoNormal">taken out to 60 bytes.=C2=A0 The problem is that the=
 TEAP spec references a TLS-PRF in a way that it does not define.=C2=A0 I t=
hink the errata points out the definition that should be used:<u></u><u></u=
></p>
</div>
<div>
<p class=3D"MsoNormal"><u></u>=C2=A0<u></u></p>
</div>
<div>
<p class=3D"MsoNormal">PRF(secret, label, seed) =3D P_&lt;hash&gt;(secret, =
label + seed)<u></u><u></u></p>
</div>
<div>
<p class=3D"MsoNormal"><u></u>=C2=A0<u></u></p>
</div>
<div>
<p class=3D"MsoNormal">That does not include length so the 60 in the origin=
al definition=C2=A0is ambiguous.=C2=A0 =C2=A0The new text would then be som=
ething like:<u></u><u></u></p>
</div>
<div>
<p class=3D"MsoNormal"><u></u>=C2=A0<u></u></p>
</div>
<div>
<p class=3D"MsoNormal">IMCK[j] =3D TLS-PRF(S-IMCK[j-1], &quot;Inner Methods=
 Compound Keys&quot;,=C2=A0<span style=3D"font-size:10.5pt;color:rgb(44,67,=
83)">IMSK[j])=C2=A0 to generate a length of 60 bytes</span><u></u><u></u></=
p>
</div>
<div>
<p class=3D"MsoNormal"><u></u>=C2=A0<u></u></p>
</div>
<div>
<p class=3D"MsoNormal"><span style=3D"font-size:10.5pt;color:rgb(44,67,83)"=
>Does the revision in 5167 match you implementation ( I don&#39;t think Jou=
ni&#39;s=C2=A0comment changes the underly=C2=A0calculation, just its repres=
entation)?=C2=A0</span><u></u><u></u></p>
</div>
<div>
<p class=3D"MsoNormal"><u></u>=C2=A0<u></u></p>
</div>
<div>
<p class=3D"MsoNormal"><u></u>=C2=A0<u></u></p>
</div>
<div>
<p class=3D"MsoNormal"><u></u>=C2=A0<u></u></p>
</div>
<div>
<p class=3D"MsoNormal"><u></u>=C2=A0<u></u></p>
</div>
<div>
<p class=3D"MsoNormal">=C2=A0<u></u><u></u></p>
</div>
<blockquote style=3D"border-top:none;border-right:none;border-bottom:none;b=
order-left:1pt solid rgb(204,204,204);padding:0in 0in 0in 6pt;margin-left:4=
.8pt;margin-right:0in">
<div>
<div>
<p class=3D"MsoNormal">Jorge Vergara<u></u><u></u></p>
<p class=3D"MsoNormal">=C2=A0<u></u><u></u></p>
<div style=3D"border-right:none;border-bottom:none;border-left:none;border-=
top:1pt solid rgb(225,225,225);padding:3pt 0in 0in">
<p class=3D"MsoNormal"><b>From:</b> Joseph Salowey &lt;<a href=3D"mailto:jo=
e@salowey.net" target=3D"_blank">joe@salowey.net</a>&gt;
<br>
<b>Sent:</b> Wednesday, October 21, 2020 2:34 PM<br>
<b>To:</b> EMU WG &lt;<a href=3D"mailto:emu@ietf.org" target=3D"_blank">emu=
@ietf.org</a>&gt;; Jouni Malinen &lt;<a href=3D"mailto:j@w1.fi" target=3D"_=
blank">j@w1.fi</a>&gt;; Jorge Vergara &lt;<a href=3D"mailto:jovergar@micros=
oft.com" target=3D"_blank">jovergar@microsoft.com</a>&gt;; Oleg
 Pekar (olpekar) &lt;<a href=3D"mailto:olpekar@cisco.com" target=3D"_blank"=
>olpekar@cisco.com</a>&gt;<br>
<b>Subject:</b> Proposed resolution for TEAP errata for 5128<u></u><u></u><=
/p>
</div>
<p class=3D"MsoNormal">=C2=A0<u></u><u></u></p>
<div>
<p class=3D"MsoNormal">Errata 5128:=C2=A0<a href=3D"https://nam06.safelinks=
.protection.outlook.com/?url=3Dhttps%3A%2F%2Fwww.rfc-editor.org%2Ferrata%2F=
eid5128&amp;data=3D04%7C01%7Cjovergar%40microsoft.com%7C38c27add2cb64a06310=
108d8761a22d3%7C72f988bf86f141af91ab2d7cd011db47%7C1%7C0%7C6373892019090627=
87%7CUnknown%7CTWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1h=
aWwiLCJXVCI6Mn0%3D%7C1000&amp;sdata=3DXudZt9FPh4jOBFQj01SQysnhX4p7G%2BflW2P=
n2yIaJRM%3D&amp;reserved=3D0" target=3D"_blank">https://www.rfc-editor.org/=
errata/eid5128</a><u></u><u></u></p>
<div>
<p class=3D"MsoNormal">Proposed State: Verified<u></u><u></u></p>
</div>
<div>
<p class=3D"MsoNormal">Revision:<u></u><u></u></p>
</div>
<div>
<p class=3D"MsoNormal">=C2=A0<u></u><u></u></p>
</div>
<div>
<p class=3D"MsoNormal">Section 5.2. says<u></u><u></u></p>
</div>
<div>
<p style=3D"margin-right:3.75pt;margin-bottom:7.5pt;margin-left:3.75pt">
<br>
IMCK[j] =3D TLS-PRF(S-IMCK[j-1], &quot;Inner Methods Compound Keys&quot;,<b=
r>
=C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 IMSK[j], 60)<br>
<br>
It should say:<br>
<br>
IMCK[j] =3D TLS-PRF(S-IMCK[j-1], &quot;Inner Methods Compound Keys&quot;,=
=C2=A0<span style=3D"font-size:10.5pt;font-family:Arial,sans-serif;color:rg=
b(44,67,83)">IMSK[j] | 60)</span><u></u><u></u></p>
<p style=3D"margin-right:3.75pt;margin-bottom:7.5pt;margin-left:3.75pt">
<span style=3D"font-size:10.5pt;font-family:Arial,sans-serif;color:rgb(44,6=
7,83)">Note:=C2=A0=C2=A0</span><u></u><u></u></p>
<p class=3D"MsoNormal">According to<br>
<br>
RFC5246 The Transport Layer Security (TLS) Protocol Version 1.2<br>
<br>
5. HMAC and the Pseudorandom Function<br>
<br>
&quot;TLS&#39;s PRF is created by applying P_hash to the secret as:<br>
<br>
PRF(secret, label, seed) =3D P_&lt;hash&gt;(secret, label + seed)&quot;<u><=
/u><u></u></p>
</div>
<div>
<p class=3D"MsoNormal">=C2=A0<u></u><u></u></p>
</div>
<div>
<p class=3D"MsoNormal">In terms of P_&lt;hash&gt; this would look like the =
following with the length represented as a 2 byte value in network byte ord=
er:<u></u><u></u></p>
</div>
<div>
<p class=3D"MsoNormal">=C2=A0<u></u><u></u></p>
</div>
<div>
<p class=3D"MsoNormal">IMCK[j] =3D P_&lt;hash&gt;(S-IMCK[j-1], &quot;Inner =
Methods Compound Keys&quot; |=C2=A0<span style=3D"font-size:10.5pt;color:rg=
b(44,67,83)">IMSK[j] | 0x00 | 0x3C)</span><u></u><u></u></p>
</div>
<div>
<p class=3D"MsoNormal">=C2=A0<u></u><u></u></p>
</div>
<div>
<p class=3D"MsoNormal">=C2=A0<u></u><u></u></p>
</div>
</div>
</div>
</div>
</blockquote>
</div>
</div>
</div>
</div>

</blockquote></div></div>
</blockquote></div></div>
</blockquote></div></div>

--000000000000b6f9e405b2447dbb--


From nobody Thu Oct 22 09:29:33 2020
Return-Path: <oleg.pekar.2017@gmail.com>
X-Original-To: emu@ietfa.amsl.com
Delivered-To: emu@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id A28083A083F for <emu@ietfa.amsl.com>; Thu, 22 Oct 2020 09:29:31 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.747
X-Spam-Level: 
X-Spam-Status: No, score=-1.747 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, DKIM_VALID_EF=-0.1, FREEMAIL_ENVFROM_END_DIGIT=0.25, FREEMAIL_FROM=0.001, HTML_MESSAGE=0.001, HTTPS_HTTP_MISMATCH=0.1, SPF_HELO_NONE=0.001, SPF_PASS=-0.001, URIBL_BLOCKED=0.001] autolearn=no autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (2048-bit key) header.d=gmail.com
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 S09YL2Jvlo4Y for <emu@ietfa.amsl.com>; Thu, 22 Oct 2020 09:29:29 -0700 (PDT)
Received: from mail-ot1-x333.google.com (mail-ot1-x333.google.com [IPv6:2607:f8b0:4864:20::333]) (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 345B43A07BD for <emu@ietf.org>; Thu, 22 Oct 2020 09:29:29 -0700 (PDT)
Received: by mail-ot1-x333.google.com with SMTP id n11so2037280ota.2 for <emu@ietf.org>; Thu, 22 Oct 2020 09:29:29 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20161025;  h=mime-version:references:in-reply-to:from:date:message-id:subject:to :cc; bh=bmw11qJFlKxUJymbwE2q3ghsIOoNdAZwoREpE8CyJ9c=; b=BJGjZhXhMHwYYFDJqwRpRP/zejpl8rziNp+CaJyN56TXjFTrTVs/c4fi1hmNsLQLbQ jF9EFv3hD0pqUrm21wtZphSeUM6N1KyCMEcR3tO31cJNFLU3vG9sNHfYJp77yO7iU+fg Ytp4U0t3BMy1zcLeYqNTXCiMFIKAycBEjCldq1HLjxcMl/41v7z8Cn72+SB6Uxzx1diK FVgVm7pNN9q6sHWZFwNRy4szt2uoerCs5j8AxvSW2bpFwSY/Us+rjuVN4xOqzIOeFjvC guvhT1DvvjptDC0vrCl5aKKpu8d9eWBuIheX957ecrWwXhaH0SkElM7kIK3wtCm8qo5I pFvQ==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:mime-version:references:in-reply-to:from:date :message-id:subject:to:cc; bh=bmw11qJFlKxUJymbwE2q3ghsIOoNdAZwoREpE8CyJ9c=; b=ha+j5WfgNJ2EiSc3xUx5ZmslCETEVc/nVm6kHLv5RMrbqOdBwT7hNzkjwabqaH9ueO N3dRUgpx4R24ZihC0NHB5gxusOi2tb+/l9doBESD2k4dORMWT/1f1YuxJHZmsDF9QUOi d31B0youd7/Yy8GLDzpkIJqFWSbDoBDYlvcOyCFgkqE8JL/D8QI2PagjycwmlM72ADf7 WX/SmX7kYEcF42cqP360Izz0t2wo5vZHSi0dFAGHPy1ti8H3lBmkN+mhP6bwWybM3FY7 /N655BHUzNIecCMfa9SAJr54DLJ0QQN7QMPoDcB6DYwnQlGeH9RvfabH6UeKym/hBmH7 igyQ==
X-Gm-Message-State: AOAM530HGThurYgipvCpAXAcN3NbKoveX9190+pu7x3IeD02a/3QhI3u LoQqh+lktuHJFg+0BmhdNw/b9AoNRuTkVMOfyYbYZlSFZt7fIWG5
X-Google-Smtp-Source: ABdhPJx1aur4PPoJp8PTevlsadchCdhoINIqt7hMwroME/ZQdzkoS5eoIAo5SuX3MXLvSt2im3tm1teEQ2TSa3vdF6U=
X-Received: by 2002:a9d:7752:: with SMTP id t18mr2506181otl.341.1603384168381;  Thu, 22 Oct 2020 09:29:28 -0700 (PDT)
MIME-Version: 1.0
References: <CAOgPGoBay+GG=F8WV0gLOOwLtGdGALGw_cM2JoAnXOtmGq7A+w@mail.gmail.com> <CH2PR21MB138143E929DAFE3C893D8144D11C0@CH2PR21MB1381.namprd21.prod.outlook.com> <CAOgPGoAtcm+Br+YkCyTtg5nJjqO7LGSo77b+CD4+Ba05azafew@mail.gmail.com> <CH2PR21MB13815BCEDC846D7C440AD564D11C0@CH2PR21MB1381.namprd21.prod.outlook.com> <CAOgPGoDTC-qiHOXFTJd7aMn2To7ySzBcx+iQMB9m5foC1bFxzw@mail.gmail.com> <CABXxEz8SRvMXdMR8_cPfvWdauJZwCjnd=7ytnVZ+_L-sB48wvw@mail.gmail.com> <CAOgPGoCsWy-uhYeeHCDUaazjAwfWtr_zkS5CUoX8+baASahFEg@mail.gmail.com>
In-Reply-To: <CAOgPGoCsWy-uhYeeHCDUaazjAwfWtr_zkS5CUoX8+baASahFEg@mail.gmail.com>
From: Oleg Pekar <oleg.pekar.2017@gmail.com>
Date: Thu, 22 Oct 2020 19:29:17 +0300
Message-ID: <CABXxEz9euWaA9Y66+1u4gtFCWkrPUEd-juY_TFUHPQE4R_OpRg@mail.gmail.com>
To: Joseph Salowey <joe@salowey.net>
Cc: EMU WG <emu@ietf.org>, Jorge Vergara <jovergar=40microsoft.com@dmarc.ietf.org>,  Jouni Malinen <j@w1.fi>
Content-Type: multipart/alternative; boundary="000000000000cb81e105b244f768"
Archived-At: <https://mailarchive.ietf.org/arch/msg/emu/zBnVozSYtfEjc8xS1RgYdUD8B7I>
Subject: Re: [Emu] Proposed resolution for TEAP errata for 5128
X-BeenThere: emu@ietf.org
X-Mailman-Version: 2.1.29
Precedence: list
List-Id: "EAP Methods Update \(EMU\)" <emu.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/emu>, <mailto:emu-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/emu/>
List-Post: <mailto:emu@ietf.org>
List-Help: <mailto:emu-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/emu>, <mailto:emu-request@ietf.org?subject=subscribe>
X-List-Received-Date: Thu, 22 Oct 2020 16:29:32 -0000

--000000000000cb81e105b244f768
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable

I agree that changing the KDF is harmful to existing implementations.
However, if I understood correctly, Joe's suggestion for IMCK[j] also
breaks the existing implementation. I still see that we can define a
unified KDF by changing the API in the RFC but with the same harm to the
existing implementation in IMCK[j] as in both proposals:

TEAP-PRF (secret, key label, optional data, length) =3D TLS-PRF(secret, key
label | 0x00 | optional data, length)
Joe, thanks for pointing out that RFC 5295 doesn't specify that a 0x00 is
used to represent no optional data, that was just my mistake.

IMSK:
Current Microsoft and Cisco implementation: P_hash(EMSK, "
TEAPbindkey@ietf.org" | 0x00 | 0x00 | 0x40)
Joe's proposal: P_hash(EMSK, "TEAPbindkey@ietf.org" | 0x00 | 0x00 | 0x40),
the same, just the API correction
Unified KDF proposal: TEAP-PRF(EMSK, "TEAPbindkey@ietf.org", <no optional
data>, 64) =3D P_hash(EMSK, "TEAPbindkey@ietf.org" | 0x00 | 0x00 | 0x40)
--- no implementation change

IMCK[j]:
Current Microsoft and Cisco implementation: P_hash(S-IMCK[j-1], "Inner
Methods Compound Keys=E2=80=9D | IMSK[j])
Joe's proposal: P_hash(S-IMCK[j-1], "Inner Methods Compound Keys" | IMSK[j]
| 0x00 | 0x3C)
Unified KDF proposal: TEAP-PRF(S-IMCK[j-1], "Inner Methods Compound Keys",
IMSK[j], 60) =3D P_hash(S-IMCK[j-1], "Inner Methods Compound Keys" | IMSK[j=
]
| 0x00 | 0x3C)
--- implementation change

MSK:
Current Microsoft and Cisco implementation: P_hash(S-IMCK[j], "Session Key
Generating Function=E2=80=9D | 0x00 | 0x00 | 0x40)
Unified KDF proposal: TEAP-PRF(S-IMCK[j], "Session Key Generating
Function=E2=80=9D, <no optional data>, 64) =3D P_hash(S-IMCK[j], "Session K=
ey
Generating Function=E2=80=9D | 0x00 | 0x00 | 0x40)
--- no implementation change

Jorge, please correct me if I misinterpret the Microsoft implementation.

On Thu, Oct 22, 2020 at 6:55 PM Joseph Salowey <joe@salowey.net> wrote:

>
>
> On Thu, Oct 22, 2020 at 6:59 AM Oleg Pekar <oleg.pekar.2017@gmail.com>
> wrote:
>
>> Hi all,
>> Speaking about both errata 5127 and 5128, I think we need to align all
>> key derivation calls in TEAP RFC with the same rule/format to make the R=
FC
>> easier to understand. This can be achieved by introducing a unified sing=
le
>> PRF function that will be called from all the relevant RFC locations. Fo=
r
>> me it sounds better than if we align just part of KDF calls with RFC 529=
5
>> (where the output length is included into seed). Also: in some KDF calls=
 we
>> do have optional data and in some no. This could be also unified.
>>
>> [Joe] I don't think this was the original intent of the document.  The
> IMSK derivation referenced 5295 while the others just reference the TLS
> PRF.  I think to unify them would require a document update and I'm not
> sure what we would gain especially if we have implementations that do
> this.
>
>
>> So I would suggest introducing:
>> TEAP-PRF (secret, key label, optional data, length) =3D TLS-PRF(secret, =
key
>> label | 0x00 | optional data, length)
>> where a single byte 0x00 is used for no optional data, length is a
>> 2-octet unsigned integer in network byte order.
>>
>> [Joe] I don't think that 5295 specifies that a 0x00 is used to represent
> no optional data.  Did you see this in the spec? It may be ambiguous, but=
 I
> think the intent is that optional data is just omitted if it is not
> provided.
>
>
>
>> Then:
>> IMSK =3D First 32 octets of TEAP-PRF(EMSK, "TEAPbindkey@ietf.org", 64) =
=3D
>> TLS-PRF(EMSK, "TEAPbindkey@ietf.org" | 0x00 | 0x00 | 0x00 | 0x40)
>> IMCK[j] =3D TEAP-PRF(S-IMCK[j-1], "Inner Methods Compound Keys", IMSK[j]=
,
>> 60) =3D TLS-PRF(S-IMCK[j-1], "Inner Methods Compound Keys" | 0x00 | IMSK=
[j] |
>> 0x00 | 0x3C)
>> MSK =3D TEAP-PRF(S-IMCK[j], "Session Key Generating Function=E2=80=9D, 6=
4) =3D
>> TLS-PRF(S-IMCK[j], "Session Key Generating Function" | 0x00 | 0x00 | 0x0=
0 |
>> 0x40)
>> EMSK =3D TEAP-PRF(S-IMCK[j], =E2=80=9DExtended Session Key Generating Fu=
nction=E2=80=9D,
>> 64) =3D TLS-PRF(S-IMCK[j], "Extended Session Key Generating Function" | =
0x00
>> | 0x00 | 0x00 | 0x40)
>>
>> This may change the existing implementation but will make it more clear =
-
>> need to create and call just one KDF function.
>>
>> We can remove 0x00 that comes after the key label - while it is required
>> by RFC 5295. But there the key label is also ASCII printable string. Joe=
,
>> do you remember what was the motivation to put 0x00 after the key label
>> parameter?
>>
>
> [Joe] the null after the key label is to provide a delimiter between the
> key label and optional data.  Since the optional data can be arbitrary
> content the null prevents two different lablels with specially crafted
> optional data from deriving the same key.
>
>
>>
>> Oleg
>>
>>
>> On Thu, Oct 22, 2020 at 2:54 AM Joseph Salowey <joe@salowey.net> wrote:
>>
>>> (I accidentally dropped this list from the conversation)
>>>
>>> On Wed, Oct 21, 2020 at 4:48 PM Jorge Vergara <jovergar@microsoft.com>
>>> wrote:
>>>
>>>> >[Joe] Yes this is a concern and I think your interpretation of the
>>>> current document is also valid.  There may be more than one
>>>> implementation.  So what you implemented was:
>>>>
>>>> >
>>>>
>>>> >IMCK[j] =3D TLS-PRF(S-IMCK[j-1], "Inner Methods Compound Keys", IMSK[=
j])
>>>> =3D P_<hash>(S-IMCK[j-1], "Inner Methods Compound Keys" | IMSK[j])
>>>>
>>>>
>>>>
>>>> Yes, this is what I implemented. As you mentioned, there are multiple
>>>> possible interpretations of this since the TEAP usage is incorrect.
>>>> However, my implementation does interop with at least 2 large vendor
>>>> implementations. If the implementations were using different calculati=
ons
>>>> here, the Wi-Fi/Ethernet connections that depend on the MSK would fail=
. But
>>>> since connections work, I can assume we are all using the same
>>>> implementation and arriving at the same MSK. Cisco is one of the
>>>> implementations that I have tested against which is why I was hoping O=
leg
>>>> may offer more context as to what he has seen.
>>>>
>>>>
>>>>
>>> [Joe] I can hope Jouni can chime in on this as well.  I think the
>>> original intent was to not include the length as is your suggestion.
>>>
>>>
>>>
>>>> >[Joe] Does the revision in 5167 match you implementation ( I don't
>>>> think Jouni's comment changes the underly calculation, just its
>>>> representation)?
>>>>
>>>>
>>>>
>>>> I have not implemented this portion of the RFC as I found it too
>>>> unclear to work with. Thus I can=E2=80=99t comment on what implementat=
ions may be
>>>> doing. However, I agree with the current revision in 5167 as the most
>>>> natural interpretation. If others have implemented this portion of the=
 RFC
>>>> then certainly their comments would be welcome.
>>>>
>>>>
>>>> By the way, we=E2=80=99ve dropped the EMU group on our replies here =
=E2=80=93 not sure
>>>> if intentional or not.
>>>>
>>>>
>>>>
>>>> Jorge Vergara
>>>>
>>>>
>>>>
>>>> *From:* Joseph Salowey <joe@salowey.net>
>>>> *Sent:* Wednesday, October 21, 2020 4:36 PM
>>>> *To:* Jorge Vergara <jovergar@microsoft.com>
>>>> *Subject:* Re: Proposed resolution for TEAP errata for 5128
>>>>
>>>>
>>>>
>>>>
>>>>
>>>>
>>>>
>>>> On Wed, Oct 21, 2020 at 3:20 PM Jorge Vergara <jovergar@microsoft.com>
>>>> wrote:
>>>>
>>>> In theory I agree this is a possible resolution. However, this doesn=
=E2=80=99t
>>>> match any of the current TEAP implementations that I am aware of. Perh=
aps
>>>> Oleg can weigh in as well in terms of what he=E2=80=99s seen.
>>>>
>>>>
>>>>
>>>> I believe all current implementations treat 60 as the desired output
>>>> length without treating as a seed. In terms of P_<hash>, this means
>>>> implementations are performing the calculation without a seed.
>>>>
>>>>
>>>>
>>>> RFC 5246 defines the TLS 1.2 PRF as:
>>>>
>>>> PRF(secret, label, seed) =3D P_<hash>(secret, label + seed)
>>>>
>>>>
>>>>
>>>> So the calculation implementations are currently performing with an
>>>> empty seed ends up as:
>>>>
>>>> P_<hash>(secret, label)
>>>>
>>>>
>>>>
>>>> Note that in RFC 5295, the length *is* explicitly mentioned as being
>>>> concatenated with the label
>>>>
>>>> USRK =3D KDF(EMSK, key label | "\0" | optional data | length)
>>>>
>>>>
>>>>
>>>> RFC 5295 is mentioned earlier in the TEAP RFC, in the section covered
>>>> by errata 5127. *However* it is not mentioned in this portion of the R=
FC.
>>>> Since this calculation is not on an EMSK, I do not believe RFC 2395 ap=
plies
>>>> and this is likely why implementations went with the seedless
>>>> P_<hash>(secret, label) calculation instead.
>>>>
>>>>
>>>>
>>>> Is there concern about updating the RFC in a way that breaks existing
>>>> implementations?
>>>>
>>>>
>>>>
>>>> [Joe] Yes this is a concern and I think your interpretation of the
>>>> current document is also valid.  There may be more than one
>>>> implementation.  So what you implemented was:
>>>>
>>>>
>>>>
>>>> IMCK[j] =3D TLS-PRF(S-IMCK[j-1], "Inner Methods Compound Keys", IMSK[j=
])
>>>> =3D P_<hash>(S-IMCK[j-1], "Inner Methods Compound Keys" | IMSK[j])
>>>>
>>>>
>>>>
>>>> taken out to 60 bytes.  The problem is that the TEAP spec references a
>>>> TLS-PRF in a way that it does not define.  I think the errata points o=
ut
>>>> the definition that should be used:
>>>>
>>>>
>>>>
>>>> PRF(secret, label, seed) =3D P_<hash>(secret, label + seed)
>>>>
>>>>
>>>>
>>>> That does not include length so the 60 in the original definition is
>>>> ambiguous.   The new text would then be something like:
>>>>
>>>>
>>>>
>>>> IMCK[j] =3D TLS-PRF(S-IMCK[j-1], "Inner Methods Compound Keys", IMSK[j=
])
>>>> to generate a length of 60 bytes
>>>>
>>>>
>>>>
>>>> Does the revision in 5167 match you implementation ( I don't think
>>>> Jouni's comment changes the underly calculation, just its representati=
on)?
>>>>
>>>>
>>>>
>>>>
>>>>
>>>>
>>>>
>>>>
>>>>
>>>>
>>>>
>>>> Jorge Vergara
>>>>
>>>>
>>>>
>>>> *From:* Joseph Salowey <joe@salowey.net>
>>>> *Sent:* Wednesday, October 21, 2020 2:34 PM
>>>> *To:* EMU WG <emu@ietf.org>; Jouni Malinen <j@w1.fi>; Jorge Vergara <
>>>> jovergar@microsoft.com>; Oleg Pekar (olpekar) <olpekar@cisco.com>
>>>> *Subject:* Proposed resolution for TEAP errata for 5128
>>>>
>>>>
>>>>
>>>> Errata 5128: https://www.rfc-editor.org/errata/eid5128
>>>> <https://nam06.safelinks.protection.outlook.com/?url=3Dhttps%3A%2F%2Fw=
ww.rfc-editor.org%2Ferrata%2Feid5128&data=3D04%7C01%7Cjovergar%40microsoft.=
com%7C38c27add2cb64a06310108d8761a22d3%7C72f988bf86f141af91ab2d7cd011db47%7=
C1%7C0%7C637389201909062787%7CUnknown%7CTWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJ=
QIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D%7C1000&sdata=3DXudZt9FPh4jOBFQj=
01SQysnhX4p7G%2BflW2Pn2yIaJRM%3D&reserved=3D0>
>>>>
>>>> Proposed State: Verified
>>>>
>>>> Revision:
>>>>
>>>>
>>>>
>>>> Section 5.2. says
>>>>
>>>>
>>>> IMCK[j] =3D TLS-PRF(S-IMCK[j-1], "Inner Methods Compound Keys",
>>>>                 IMSK[j], 60)
>>>>
>>>> It should say:
>>>>
>>>> IMCK[j] =3D TLS-PRF(S-IMCK[j-1], "Inner Methods Compound Keys", IMSK[j=
]
>>>> | 60)
>>>>
>>>> Note:
>>>>
>>>> According to
>>>>
>>>> RFC5246 The Transport Layer Security (TLS) Protocol Version 1.2
>>>>
>>>> 5. HMAC and the Pseudorandom Function
>>>>
>>>> "TLS's PRF is created by applying P_hash to the secret as:
>>>>
>>>> PRF(secret, label, seed) =3D P_<hash>(secret, label + seed)"
>>>>
>>>>
>>>>
>>>> In terms of P_<hash> this would look like the following with the lengt=
h
>>>> represented as a 2 byte value in network byte order:
>>>>
>>>>
>>>>
>>>> IMCK[j] =3D P_<hash>(S-IMCK[j-1], "Inner Methods Compound Keys" | IMSK=
[j]
>>>> | 0x00 | 0x3C)
>>>>
>>>>
>>>>
>>>>
>>>>
>>>>

--000000000000cb81e105b244f768
Content-Type: text/html; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable

<div dir=3D"ltr">I agree that changing the KDF is harmful to existing imple=
mentations. However, if I understood correctly, Joe&#39;s suggestion=C2=A0f=
or IMCK[j] also breaks the existing=C2=A0implementation. I still see that w=
e can define a unified KDF by changing the API in the RFC but with the same=
 harm to the existing implementation in IMCK[j] as in both proposals:<div><=
br></div><div>TEAP-PRF (secret, key label, optional data, length) =3D TLS-P=
RF(secret, key label | 0x00 | optional data, length)</div><div>Joe, thanks =
for pointing out that RFC 5295 doesn&#39;t specify that a 0x00 is used to r=
epresent no optional data, that was just my mistake.</div><div><br><div>IMS=
K:</div><div>Current Microsoft and Cisco implementation: P_hash(EMSK, &quot=
;<a href=3D"mailto:TEAPbindkey@ietf.org" target=3D"_blank">TEAPbindkey@ietf=
.org</a>&quot; | 0x00 | 0x00 | 0x40) <br></div><div>Joe&#39;s proposal: P_h=
ash(EMSK, &quot;<a href=3D"mailto:TEAPbindkey@ietf.org" target=3D"_blank">T=
EAPbindkey@ietf.org</a>&quot; | 0x00 | 0x00 | 0x40), the same, just the API=
 correction<br></div><div>Unified KDF proposal:=C2=A0TEAP-PRF(EMSK, &quot;<=
a href=3D"mailto:TEAPbindkey@ietf.org">TEAPbindkey@ietf.org</a>&quot;, &lt;=
no optional data&gt;, 64) =3D P_hash(EMSK, &quot;<a href=3D"mailto:TEAPbind=
key@ietf.org" target=3D"_blank">TEAPbindkey@ietf.org</a>&quot; | 0x00 | 0x0=
0 | 0x40)=C2=A0<br></div><div>--- no implementation change</div><div><br></=
div><div>IMCK[j]:<br></div><div><div>Current Microsoft and Cisco implementa=
tion: P_hash(S-IMCK[j-1], &quot;Inner Methods Compound Keys=E2=80=9D | IMSK=
[j])=C2=A0<br></div><div>Joe&#39;s proposal:=C2=A0P_hash(S-IMCK[j-1], &quot=
;Inner Methods Compound Keys&quot; | IMSK[j] | 0x00 | 0x3C)<br></div><div>U=
nified KDF proposal: TEAP-PRF(S-IMCK[j-1], &quot;Inner Methods Compound Key=
s&quot;, IMSK[j], 60) =3D P_hash(S-IMCK[j-1], &quot;Inner Methods Compound =
Keys&quot; | IMSK[j] | 0x00 | 0x3C)</div></div><div><div>--- implementation=
 change</div><div></div></div><div><br></div><div>MSK:</div><div>Current Mi=
crosoft and Cisco implementation: P_hash(S-IMCK[j], &quot;Session Key Gener=
ating Function=E2=80=9D | 0x00 | 0x00 | 0x40)</div><div>Unified KDF proposa=
l:  TEAP-PRF(S-IMCK[j], &quot;Session Key Generating Function=E2=80=9D, &lt=
;no optional data&gt;,  64) =3D P_hash(S-IMCK[j], &quot;Session Key Generat=
ing Function=E2=80=9D | 0x00 | 0x00 | 0x40)</div><div><div>--- no implement=
ation change</div><div></div></div><div><br></div><div>Jorge, please correc=
t me if I misinterpret=C2=A0the Microsoft implementation.=C2=A0</div></div>=
</div><br><div class=3D"gmail_quote"><div dir=3D"ltr" class=3D"gmail_attr">=
On Thu, Oct 22, 2020 at 6:55 PM Joseph Salowey &lt;<a href=3D"mailto:joe@sa=
lowey.net">joe@salowey.net</a>&gt; wrote:<br></div><blockquote class=3D"gma=
il_quote" style=3D"margin:0px 0px 0px 0.8ex;border-left:1px solid rgb(204,2=
04,204);padding-left:1ex"><div dir=3D"ltr"><div dir=3D"ltr"><br></div><br><=
div class=3D"gmail_quote"><div dir=3D"ltr" class=3D"gmail_attr">On Thu, Oct=
 22, 2020 at 6:59 AM Oleg Pekar &lt;<a href=3D"mailto:oleg.pekar.2017@gmail=
.com" target=3D"_blank">oleg.pekar.2017@gmail.com</a>&gt; wrote:<br></div><=
blockquote class=3D"gmail_quote" style=3D"margin:0px 0px 0px 0.8ex;border-l=
eft:1px solid rgb(204,204,204);padding-left:1ex"><div dir=3D"ltr"><div>Hi a=
ll,</div><div>Speaking about both errata 5127 and 5128, I think we need to =
align all key derivation calls in TEAP RFC with the same rule/format to mak=
e the RFC easier to understand. This can be achieved by introducing a unifi=
ed single PRF function that will be called from all the relevant RFC locati=
ons. For me it sounds better than if we align just part of KDF calls with R=
FC 5295 (where the output length is included into seed). Also: in some KDF =
calls we do have optional data and in some no. This could be also unified.=
=C2=A0</div><div><br></div></div></blockquote><div>[Joe] I don&#39;t think =
this was the original intent of the document.=C2=A0 The IMSK derivation ref=
erenced 5295 while the others just reference the TLS PRF.=C2=A0 I think to =
unify them would require a document update and I&#39;m not sure what we wou=
ld gain especially if we have implementations that do this.=C2=A0=C2=A0</di=
v><div>=C2=A0</div><blockquote class=3D"gmail_quote" style=3D"margin:0px 0p=
x 0px 0.8ex;border-left:1px solid rgb(204,204,204);padding-left:1ex"><div d=
ir=3D"ltr"><div></div><div>So I would suggest introducing:</div><div>TEAP-P=
RF (secret, key label, optional data, length) =3D TLS-PRF(secret, key label=
 | 0x00 | optional data, length)<br></div><div>where a single byte 0x00 is =
used for no optional data, length is a 2-octet unsigned integer in network =
byte order.<br></div><div><br></div></div></blockquote><div>[Joe] I don&#39=
;t think that 5295 specifies that a 0x00 is used to represent no optional d=
ata.=C2=A0 Did you see this in the spec? It may be ambiguous, but I think t=
he intent is that optional data is just omitted if it is not provided.=C2=
=A0</div><div><br></div><div>=C2=A0</div><blockquote class=3D"gmail_quote" =
style=3D"margin:0px 0px 0px 0.8ex;border-left:1px solid rgb(204,204,204);pa=
dding-left:1ex"><div dir=3D"ltr"><div></div><div>Then:</div><div>IMSK =3D F=
irst 32 octets of TEAP-PRF(EMSK, &quot;<a href=3D"mailto:TEAPbindkey@ietf.o=
rg" target=3D"_blank">TEAPbindkey@ietf.org</a>&quot;, 64) =3D TLS-PRF(EMSK,=
 &quot;<a href=3D"mailto:TEAPbindkey@ietf.org" target=3D"_blank">TEAPbindke=
y@ietf.org</a>&quot; | 0x00 | 0x00 | 0x00 | 0x40)<br>IMCK[j] =3D TEAP-PRF(S=
-IMCK[j-1], &quot;Inner Methods Compound Keys&quot;, IMSK[j], 60) =3D TLS-P=
RF(S-IMCK[j-1], &quot;Inner Methods Compound Keys&quot; | 0x00 | IMSK[j] | =
0x00 | 0x3C)<br>MSK =3D TEAP-PRF(S-IMCK[j], &quot;Session Key Generating Fu=
nction=E2=80=9D, 64) =3D TLS-PRF(S-IMCK[j], &quot;Session Key Generating Fu=
nction&quot; | 0x00 | 0x00 | 0x00 | 0x40)<br>EMSK =3D TEAP-PRF(S-IMCK[j], =
=E2=80=9DExtended Session Key Generating Function=E2=80=9D, 64) =3D TLS-PRF=
(S-IMCK[j], &quot;Extended Session Key Generating Function&quot; | 0x00 | 0=
x00 | 0x00 | 0x40)<br></div><div><br></div><div>This may change the existin=
g implementation but will make it more clear - need to create and call just=
 one KDF function.</div><div><br></div><div>We can remove=C2=A00x00 that co=
mes after the key label - while it is required by=C2=A0RFC 5295. But there=
=C2=A0the key label is also ASCII printable string. Joe, do you remember wh=
at was the motivation to put 0x00 after the key label parameter?</div></div=
></blockquote><div><br></div><div>[Joe] the null after the key label is to =
provide a delimiter between the key label and optional data.=C2=A0 Since th=
e optional data can be arbitrary content the null prevents two different la=
blels=C2=A0with specially=C2=A0crafted optional data from deriving the same=
 key.=C2=A0=C2=A0</div><div>=C2=A0</div><blockquote class=3D"gmail_quote" s=
tyle=3D"margin:0px 0px 0px 0.8ex;border-left:1px solid rgb(204,204,204);pad=
ding-left:1ex"><div dir=3D"ltr"><div><br></div><div>Oleg</div><div><br></di=
v><div><br></div><div class=3D"gmail_quote"><div dir=3D"ltr" class=3D"gmail=
_attr">On Thu, Oct 22, 2020 at 2:54 AM Joseph Salowey &lt;<a href=3D"mailto=
:joe@salowey.net" target=3D"_blank">joe@salowey.net</a>&gt; wrote:<br></div=
><blockquote class=3D"gmail_quote" style=3D"margin:0px 0px 0px 0.8ex;border=
-left:1px solid rgb(204,204,204);padding-left:1ex"><div dir=3D"ltr"><div>(I=
 accidentally=C2=A0dropped this list from the conversation)</div><br><div c=
lass=3D"gmail_quote"><div dir=3D"ltr" class=3D"gmail_attr">On Wed, Oct 21, =
2020 at 4:48 PM Jorge Vergara &lt;<a href=3D"mailto:jovergar@microsoft.com"=
 target=3D"_blank">jovergar@microsoft.com</a>&gt; wrote:<br></div><blockquo=
te class=3D"gmail_quote" style=3D"margin:0px 0px 0px 0.8ex;border-left:1px =
solid rgb(204,204,204);padding-left:1ex">





<div lang=3D"EN-US">
<div>
<p class=3D"MsoNormal">&gt;[Joe] Yes this is a concern and I think your=C2=
=A0interpretation of the current document is also valid.=C2=A0 There may be=
 more than one implementation.=C2=A0 So what you implemented was:<u></u><u>=
</u></p>
<p class=3D"MsoNormal">&gt;<u></u>=C2=A0<u></u></p>
<p class=3D"MsoNormal">&gt;IMCK[j] =3D TLS-PRF(S-IMCK[j-1], &quot;Inner Met=
hods Compound Keys&quot;,=C2=A0<span style=3D"font-size:10.5pt;color:rgb(44=
,67,83)">IMSK[j]) =3D P_&lt;hash&gt;(S-IMCK[j-1], &quot;Inner Methods Compo=
und Keys&quot; | IMSK[j])</span><u></u><u></u></p>
<p class=3D"MsoNormal"><u></u>=C2=A0<u></u></p>
<p class=3D"MsoNormal">Yes, this is what I implemented. As you mentioned, t=
here are multiple possible interpretations of this since the TEAP usage is =
incorrect. However, my implementation does interop with at least 2 large ve=
ndor implementations. If the implementations
 were using different calculations here, the Wi-Fi/Ethernet connections tha=
t depend on the MSK would fail. But since connections work, I can assume we=
 are all using the same implementation and arriving at the same MSK. Cisco =
is one of the implementations that
 I have tested against which is why I was hoping Oleg may offer more contex=
t as to what he has seen.<u></u><u></u></p>
<p class=3D"MsoNormal"><u></u>=C2=A0</p></div></div></blockquote><div>[Joe]=
 I can hope Jouni can chime in on this as well.=C2=A0 I think the original =
intent was to not include the length as is your suggestion.=C2=A0</div><div=
><br></div><div>=C2=A0</div><blockquote class=3D"gmail_quote" style=3D"marg=
in:0px 0px 0px 0.8ex;border-left:1px solid rgb(204,204,204);padding-left:1e=
x"><div lang=3D"EN-US"><div><p class=3D"MsoNormal"><u></u></p>
<p class=3D"MsoNormal">&gt;[Joe]<span style=3D"font-size:10.5pt;color:rgb(4=
4,67,83)"> Does the revision in 5167 match you implementation ( I don&#39;t=
 think Jouni&#39;s=C2=A0comment changes the underly=C2=A0calculation, just =
its representation)?=C2=A0</span><u></u><u></u></p>
<p class=3D"MsoNormal"><u></u>=C2=A0<u></u></p>
<p class=3D"MsoNormal">I have not implemented this portion of the RFC as I =
found it too unclear to work with. Thus I can=E2=80=99t comment on what imp=
lementations may be doing. However, I agree with the current revision in 51=
67 as the most natural interpretation. If
 others have implemented this portion of the RFC then certainly their comme=
nts would be welcome.<u></u><u></u></p>
<p class=3D"MsoNormal"><br><u></u></p></div></div></blockquote><blockquote =
class=3D"gmail_quote" style=3D"margin:0px 0px 0px 0.8ex;border-left:1px sol=
id rgb(204,204,204);padding-left:1ex"><div lang=3D"EN-US"><div><p class=3D"=
MsoNormal"><u></u></p>
<p class=3D"MsoNormal">By the way, we=E2=80=99ve dropped the EMU group on o=
ur replies here =E2=80=93 not sure if intentional or not.<u></u><u></u></p>
<p class=3D"MsoNormal"><u></u>=C2=A0<u></u></p>
<p class=3D"MsoNormal">Jorge Vergara<u></u><u></u></p>
<p class=3D"MsoNormal"><u></u>=C2=A0<u></u></p>
<div style=3D"border-right:none;border-bottom:none;border-left:none;border-=
top:1pt solid rgb(225,225,225);padding:3pt 0in 0in">
<p class=3D"MsoNormal"><b>From:</b> Joseph Salowey &lt;<a href=3D"mailto:jo=
e@salowey.net" target=3D"_blank">joe@salowey.net</a>&gt; <br>
<b>Sent:</b> Wednesday, October 21, 2020 4:36 PM<br>
<b>To:</b> Jorge Vergara &lt;<a href=3D"mailto:jovergar@microsoft.com" targ=
et=3D"_blank">jovergar@microsoft.com</a>&gt;<br>
<b>Subject:</b> Re: Proposed resolution for TEAP errata for 5128<u></u><u><=
/u></p>
</div>
<p class=3D"MsoNormal"><u></u>=C2=A0<u></u></p>
<div>
<div>
<p class=3D"MsoNormal"><u></u>=C2=A0<u></u></p>
</div>
<p class=3D"MsoNormal"><u></u>=C2=A0<u></u></p>
<div>
<div>
<p class=3D"MsoNormal">On Wed, Oct 21, 2020 at 3:20 PM Jorge Vergara &lt;<a=
 href=3D"mailto:jovergar@microsoft.com" target=3D"_blank">jovergar@microsof=
t.com</a>&gt; wrote:<u></u><u></u></p>
</div>
<blockquote style=3D"border-top:none;border-right:none;border-bottom:none;b=
order-left:1pt solid rgb(204,204,204);padding:0in 0in 0in 6pt;margin-left:4=
.8pt;margin-right:0in">
<div>
<div>
<p class=3D"MsoNormal">In theory I agree this is a possible resolution. How=
ever, this doesn=E2=80=99t match any of the current TEAP implementations th=
at I am aware of. Perhaps Oleg can weigh in as well in terms
 of what he=E2=80=99s seen.<u></u><u></u></p>
<p class=3D"MsoNormal">=C2=A0<u></u><u></u></p>
<p class=3D"MsoNormal">I believe all current implementations treat 60 as th=
e desired output length without treating as a seed. In terms of P_&lt;hash&=
gt;, this means implementations are performing the calculation
 without a seed.<u></u><u></u></p>
<p class=3D"MsoNormal">=C2=A0<u></u><u></u></p>
<p class=3D"MsoNormal">RFC 5246 defines the TLS 1.2 PRF as:<u></u><u></u></=
p>
<p class=3D"MsoNormal">PRF(secret, label, seed) =3D P_&lt;hash&gt;(secret, =
label + seed)<u></u><u></u></p>
<p class=3D"MsoNormal">=C2=A0<u></u><u></u></p>
<p class=3D"MsoNormal">So the calculation implementations are currently per=
forming with an empty seed ends up as:<u></u><u></u></p>
<p class=3D"MsoNormal">P_&lt;hash&gt;(secret, label)<u></u><u></u></p>
<p class=3D"MsoNormal">=C2=A0<u></u><u></u></p>
<p class=3D"MsoNormal">Note that in RFC 5295, the length *is* explicitly me=
ntioned as being concatenated with the label<u></u><u></u></p>
<p class=3D"MsoNormal">USRK =3D KDF(EMSK, key label | &quot;\0&quot; | opti=
onal data | length)<u></u><u></u></p>
<p class=3D"MsoNormal">=C2=A0<u></u><u></u></p>
<p class=3D"MsoNormal">RFC 5295 is mentioned earlier in the TEAP RFC, in th=
e section covered by errata 5127. *However* it is not mentioned in this por=
tion of the RFC. Since this calculation is not on
 an EMSK, I do not believe RFC 2395 applies and this is likely why implemen=
tations went with the seedless P_&lt;hash&gt;(secret, label) calculation in=
stead.<u></u><u></u></p>
<p class=3D"MsoNormal">=C2=A0<u></u><u></u></p>
<p class=3D"MsoNormal">Is there concern about updating the RFC in a way tha=
t breaks existing implementations?<u></u><u></u></p>
<p class=3D"MsoNormal">=C2=A0<u></u><u></u></p>
</div>
</div>
</blockquote>
<div>
<p class=3D"MsoNormal">[Joe] Yes this is a concern and I think your=C2=A0in=
terpretation of the current document is also valid.=C2=A0 There may be more=
 than one implementation.=C2=A0 So what you implemented was:<u></u><u></u><=
/p>
</div>
<div>
<p class=3D"MsoNormal"><u></u>=C2=A0<u></u></p>
</div>
<div>
<p class=3D"MsoNormal">IMCK[j] =3D TLS-PRF(S-IMCK[j-1], &quot;Inner Methods=
 Compound Keys&quot;,=C2=A0<span style=3D"font-size:10.5pt;color:rgb(44,67,=
83)">IMSK[j]) =3D P_&lt;hash&gt;(S-IMCK[j-1], &quot;Inner Methods Compound =
Keys&quot; | IMSK[j])</span><u></u><u></u></p>
</div>
<div>
<p class=3D"MsoNormal"><u></u>=C2=A0<u></u></p>
</div>
<div>
<p class=3D"MsoNormal">taken out to 60 bytes.=C2=A0 The problem is that the=
 TEAP spec references a TLS-PRF in a way that it does not define.=C2=A0 I t=
hink the errata points out the definition that should be used:<u></u><u></u=
></p>
</div>
<div>
<p class=3D"MsoNormal"><u></u>=C2=A0<u></u></p>
</div>
<div>
<p class=3D"MsoNormal">PRF(secret, label, seed) =3D P_&lt;hash&gt;(secret, =
label + seed)<u></u><u></u></p>
</div>
<div>
<p class=3D"MsoNormal"><u></u>=C2=A0<u></u></p>
</div>
<div>
<p class=3D"MsoNormal">That does not include length so the 60 in the origin=
al definition=C2=A0is ambiguous.=C2=A0 =C2=A0The new text would then be som=
ething like:<u></u><u></u></p>
</div>
<div>
<p class=3D"MsoNormal"><u></u>=C2=A0<u></u></p>
</div>
<div>
<p class=3D"MsoNormal">IMCK[j] =3D TLS-PRF(S-IMCK[j-1], &quot;Inner Methods=
 Compound Keys&quot;,=C2=A0<span style=3D"font-size:10.5pt;color:rgb(44,67,=
83)">IMSK[j])=C2=A0 to generate a length of 60 bytes</span><u></u><u></u></=
p>
</div>
<div>
<p class=3D"MsoNormal"><u></u>=C2=A0<u></u></p>
</div>
<div>
<p class=3D"MsoNormal"><span style=3D"font-size:10.5pt;color:rgb(44,67,83)"=
>Does the revision in 5167 match you implementation ( I don&#39;t think Jou=
ni&#39;s=C2=A0comment changes the underly=C2=A0calculation, just its repres=
entation)?=C2=A0</span><u></u><u></u></p>
</div>
<div>
<p class=3D"MsoNormal"><u></u>=C2=A0<u></u></p>
</div>
<div>
<p class=3D"MsoNormal"><u></u>=C2=A0<u></u></p>
</div>
<div>
<p class=3D"MsoNormal"><u></u>=C2=A0<u></u></p>
</div>
<div>
<p class=3D"MsoNormal"><u></u>=C2=A0<u></u></p>
</div>
<div>
<p class=3D"MsoNormal">=C2=A0<u></u><u></u></p>
</div>
<blockquote style=3D"border-top:none;border-right:none;border-bottom:none;b=
order-left:1pt solid rgb(204,204,204);padding:0in 0in 0in 6pt;margin-left:4=
.8pt;margin-right:0in">
<div>
<div>
<p class=3D"MsoNormal">Jorge Vergara<u></u><u></u></p>
<p class=3D"MsoNormal">=C2=A0<u></u><u></u></p>
<div style=3D"border-right:none;border-bottom:none;border-left:none;border-=
top:1pt solid rgb(225,225,225);padding:3pt 0in 0in">
<p class=3D"MsoNormal"><b>From:</b> Joseph Salowey &lt;<a href=3D"mailto:jo=
e@salowey.net" target=3D"_blank">joe@salowey.net</a>&gt;
<br>
<b>Sent:</b> Wednesday, October 21, 2020 2:34 PM<br>
<b>To:</b> EMU WG &lt;<a href=3D"mailto:emu@ietf.org" target=3D"_blank">emu=
@ietf.org</a>&gt;; Jouni Malinen &lt;<a href=3D"mailto:j@w1.fi" target=3D"_=
blank">j@w1.fi</a>&gt;; Jorge Vergara &lt;<a href=3D"mailto:jovergar@micros=
oft.com" target=3D"_blank">jovergar@microsoft.com</a>&gt;; Oleg
 Pekar (olpekar) &lt;<a href=3D"mailto:olpekar@cisco.com" target=3D"_blank"=
>olpekar@cisco.com</a>&gt;<br>
<b>Subject:</b> Proposed resolution for TEAP errata for 5128<u></u><u></u><=
/p>
</div>
<p class=3D"MsoNormal">=C2=A0<u></u><u></u></p>
<div>
<p class=3D"MsoNormal">Errata 5128:=C2=A0<a href=3D"https://nam06.safelinks=
.protection.outlook.com/?url=3Dhttps%3A%2F%2Fwww.rfc-editor.org%2Ferrata%2F=
eid5128&amp;data=3D04%7C01%7Cjovergar%40microsoft.com%7C38c27add2cb64a06310=
108d8761a22d3%7C72f988bf86f141af91ab2d7cd011db47%7C1%7C0%7C6373892019090627=
87%7CUnknown%7CTWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1h=
aWwiLCJXVCI6Mn0%3D%7C1000&amp;sdata=3DXudZt9FPh4jOBFQj01SQysnhX4p7G%2BflW2P=
n2yIaJRM%3D&amp;reserved=3D0" target=3D"_blank">https://www.rfc-editor.org/=
errata/eid5128</a><u></u><u></u></p>
<div>
<p class=3D"MsoNormal">Proposed State: Verified<u></u><u></u></p>
</div>
<div>
<p class=3D"MsoNormal">Revision:<u></u><u></u></p>
</div>
<div>
<p class=3D"MsoNormal">=C2=A0<u></u><u></u></p>
</div>
<div>
<p class=3D"MsoNormal">Section 5.2. says<u></u><u></u></p>
</div>
<div>
<p style=3D"margin-right:3.75pt;margin-bottom:7.5pt;margin-left:3.75pt">
<br>
IMCK[j] =3D TLS-PRF(S-IMCK[j-1], &quot;Inner Methods Compound Keys&quot;,<b=
r>
=C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 IMSK[j], 60)<br>
<br>
It should say:<br>
<br>
IMCK[j] =3D TLS-PRF(S-IMCK[j-1], &quot;Inner Methods Compound Keys&quot;,=
=C2=A0<span style=3D"font-size:10.5pt;font-family:Arial,sans-serif;color:rg=
b(44,67,83)">IMSK[j] | 60)</span><u></u><u></u></p>
<p style=3D"margin-right:3.75pt;margin-bottom:7.5pt;margin-left:3.75pt">
<span style=3D"font-size:10.5pt;font-family:Arial,sans-serif;color:rgb(44,6=
7,83)">Note:=C2=A0=C2=A0</span><u></u><u></u></p>
<p class=3D"MsoNormal">According to<br>
<br>
RFC5246 The Transport Layer Security (TLS) Protocol Version 1.2<br>
<br>
5. HMAC and the Pseudorandom Function<br>
<br>
&quot;TLS&#39;s PRF is created by applying P_hash to the secret as:<br>
<br>
PRF(secret, label, seed) =3D P_&lt;hash&gt;(secret, label + seed)&quot;<u><=
/u><u></u></p>
</div>
<div>
<p class=3D"MsoNormal">=C2=A0<u></u><u></u></p>
</div>
<div>
<p class=3D"MsoNormal">In terms of P_&lt;hash&gt; this would look like the =
following with the length represented as a 2 byte value in network byte ord=
er:<u></u><u></u></p>
</div>
<div>
<p class=3D"MsoNormal">=C2=A0<u></u><u></u></p>
</div>
<div>
<p class=3D"MsoNormal">IMCK[j] =3D P_&lt;hash&gt;(S-IMCK[j-1], &quot;Inner =
Methods Compound Keys&quot; |=C2=A0<span style=3D"font-size:10.5pt;color:rg=
b(44,67,83)">IMSK[j] | 0x00 | 0x3C)</span><u></u><u></u></p>
</div>
<div>
<p class=3D"MsoNormal">=C2=A0<u></u><u></u></p>
</div>
<div>
<p class=3D"MsoNormal">=C2=A0<u></u><u></u></p>
</div>
</div>
</div>
</div>
</blockquote>
</div>
</div>
</div>
</div>

</blockquote></div></div>
</blockquote></div></div>
</blockquote></div></div>
</blockquote></div>

--000000000000cb81e105b244f768--


From nobody Thu Oct 22 09:53:29 2020
Return-Path: <joe@salowey.net>
X-Original-To: emu@ietfa.amsl.com
Delivered-To: emu@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id C369D3A08C6 for <emu@ietfa.amsl.com>; Thu, 22 Oct 2020 09:53:28 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.798
X-Spam-Level: 
X-Spam-Status: No, score=-1.798 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, HTML_MESSAGE=0.001, HTTPS_HTTP_MISMATCH=0.1, SPF_HELO_NONE=0.001, SPF_PASS=-0.001, URIBL_BLOCKED=0.001] autolearn=no autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (2048-bit key) header.d=salowey-net.20150623.gappssmtp.com
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 eaiRQZkzkPqY for <emu@ietfa.amsl.com>; Thu, 22 Oct 2020 09:53:25 -0700 (PDT)
Received: from mail-qt1-x82c.google.com (mail-qt1-x82c.google.com [IPv6:2607:f8b0:4864:20::82c]) (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 952D13A08C1 for <emu@ietf.org>; Thu, 22 Oct 2020 09:53:25 -0700 (PDT)
Received: by mail-qt1-x82c.google.com with SMTP id p88so1597755qtd.12 for <emu@ietf.org>; Thu, 22 Oct 2020 09:53:25 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=salowey-net.20150623.gappssmtp.com; s=20150623; h=mime-version:references:in-reply-to:from:date:message-id:subject:to :cc; bh=sZdgMk6T11GBBY8xbp72YfNOR+uqbFGt+GFNgmVt60Q=; b=A5FaL4SJ7RscW2ogsE3UVrpQt6nv6ZA1CopT9yzlyFhP7DUs+tlW+rOeDkISe24cfL IrVsj7tqAmb5JNIh/suuHwXv+srSgKKn1gcLYGjBVFUcpzed0JCtZD+thf2JmbdJEvDD z3+YYo//99ktYatejtcoGKtsTDhGJKN5aB0LHPtvW2KuQ5SgY69dtY1M4DkZj7wVmFCT VoHvPEZgbD1s1G++hdGjgYoiS+cdgZo7Pq3sq8kGi6oyNViB7J9jcsVbIqdvU4sK9y/4 bTkf1daVo6AF+V/G/Doj/5YK7WDPo84v2RDsYEg8DaMYiASMWN2apBqnyD+wc6CioD7l JrQg==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:mime-version:references:in-reply-to:from:date :message-id:subject:to:cc; bh=sZdgMk6T11GBBY8xbp72YfNOR+uqbFGt+GFNgmVt60Q=; b=lxTnBvxXs/H7dGbE925ZklaBJw2Vr+szN1gH2VfhI+biQ5il9iYeKq8aQoCRTFyTX7 EjWtqgEtg++kcmTMp8c1ftZiaLEPxxCxLQA6f9ZjzafA4sM+wHbnCKt1pfM4bcez91QK sdcwsKtOyMCTkOvFhNBaszEoh25gTXFgstBvzUmTfawu0YdSxr9MejLjo1Iuj+p/kIwl CXxWs6CTK3hC4iizDoXcaty/rokZI5V/Ip6xy0YP9k133Vf+psxk0oFfGCShKehy+uzs tn9Y88jJDQRWLJq5NHaBPTDb/fP8f4yQrkAU8SHSLPh+4LCLDCYPQShyt2AgDMRv2YyQ 9ptA==
X-Gm-Message-State: AOAM530RAMG5BRNTJFjQlDpXyLRC40nUoTUVJMTkqveBQHk2NgrHsZgH DodtvzY2Enqg/rPf31vm/qbmIBcj6iVkaCNw3ahh5Q==
X-Google-Smtp-Source: ABdhPJyHoSWBLVDgCD+MQZZXQvRgLPxvg1kX5BcHsxkhJfUYe+xZGYU2K7Plf7hjx3il6Ak1QPwiOwdsk8w7LlROHRA=
X-Received: by 2002:aed:243b:: with SMTP id r56mr3010755qtc.249.1603385604448;  Thu, 22 Oct 2020 09:53:24 -0700 (PDT)
MIME-Version: 1.0
References: <CAOgPGoBay+GG=F8WV0gLOOwLtGdGALGw_cM2JoAnXOtmGq7A+w@mail.gmail.com> <CH2PR21MB138143E929DAFE3C893D8144D11C0@CH2PR21MB1381.namprd21.prod.outlook.com> <CAOgPGoAtcm+Br+YkCyTtg5nJjqO7LGSo77b+CD4+Ba05azafew@mail.gmail.com> <CH2PR21MB13815BCEDC846D7C440AD564D11C0@CH2PR21MB1381.namprd21.prod.outlook.com> <CAOgPGoDTC-qiHOXFTJd7aMn2To7ySzBcx+iQMB9m5foC1bFxzw@mail.gmail.com> <CABXxEz8SRvMXdMR8_cPfvWdauJZwCjnd=7ytnVZ+_L-sB48wvw@mail.gmail.com> <CAOgPGoCsWy-uhYeeHCDUaazjAwfWtr_zkS5CUoX8+baASahFEg@mail.gmail.com> <CABXxEz9euWaA9Y66+1u4gtFCWkrPUEd-juY_TFUHPQE4R_OpRg@mail.gmail.com>
In-Reply-To: <CABXxEz9euWaA9Y66+1u4gtFCWkrPUEd-juY_TFUHPQE4R_OpRg@mail.gmail.com>
From: Joseph Salowey <joe@salowey.net>
Date: Thu, 22 Oct 2020 09:53:13 -0700
Message-ID: <CAOgPGoDcD7wjiMt2=t0vx2FPr2LD2S3eU1d0_bVU1c88S=tA=w@mail.gmail.com>
To: Oleg Pekar <oleg.pekar.2017@gmail.com>
Cc: EMU WG <emu@ietf.org>, Jorge Vergara <jovergar=40microsoft.com@dmarc.ietf.org>,  Jouni Malinen <j@w1.fi>
Content-Type: multipart/alternative; boundary="0000000000006441ea05b2454dce"
Archived-At: <https://mailarchive.ietf.org/arch/msg/emu/5_QUVmlkKnqEq0beHHVtVYYYnPw>
Subject: Re: [Emu] Proposed resolution for TEAP errata for 5128
X-BeenThere: emu@ietf.org
X-Mailman-Version: 2.1.29
Precedence: list
List-Id: "EAP Methods Update \(EMU\)" <emu.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/emu>, <mailto:emu-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/emu/>
List-Post: <mailto:emu@ietf.org>
List-Help: <mailto:emu-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/emu>, <mailto:emu-request@ietf.org?subject=subscribe>
X-List-Received-Date: Thu, 22 Oct 2020 16:53:29 -0000

--0000000000006441ea05b2454dce
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable

On Thu, Oct 22, 2020 at 9:29 AM Oleg Pekar <oleg.pekar.2017@gmail.com>
wrote:

> I agree that changing the KDF is harmful to existing implementations.
> However, if I understood correctly, Joe's suggestion for IMCK[j] also
> breaks the existing implementation. I still see that we can define a
> unified KDF by changing the API in the RFC but with the same harm to the
> existing implementation in IMCK[j] as in both proposals:
>
> TEAP-PRF (secret, key label, optional data, length) =3D TLS-PRF(secret, k=
ey
> label | 0x00 | optional data, length)
> Joe, thanks for pointing out that RFC 5295 doesn't specify that a 0x00 is
> used to represent no optional data, that was just my mistake.
>
> IMSK:
> Current Microsoft and Cisco implementation: P_hash(EMSK, "
> TEAPbindkey@ietf.org" | 0x00 | 0x00 | 0x40)
> Joe's proposal: P_hash(EMSK, "TEAPbindkey@ietf.org" | 0x00 | 0x00 |
> 0x40), the same, just the API correction
> Unified KDF proposal: TEAP-PRF(EMSK, "TEAPbindkey@ietf.org", <no optional
> data>, 64) =3D P_hash(EMSK, "TEAPbindkey@ietf.org" | 0x00 | 0x00 | 0x40)
> --- no implementation change
>
> IMCK[j]:
> Current Microsoft and Cisco implementation: P_hash(S-IMCK[j-1], "Inner
> Methods Compound Keys=E2=80=9D | IMSK[j])
> Joe's proposal: P_hash(S-IMCK[j-1], "Inner Methods Compound Keys" |
> IMSK[j] | 0x00 | 0x3C)
> Unified KDF proposal: TEAP-PRF(S-IMCK[j-1], "Inner Methods Compound Keys"=
,
> IMSK[j], 60) =3D P_hash(S-IMCK[j-1], "Inner Methods Compound Keys" | IMSK=
[j]
> | 0x00 | 0x3C)
> --- implementation change
>

[Joe] That was my initial proposal, but based on Jorge's comment it is
modified to:

IMCK[j] =3D TLS-PRF(S-IMCK[j-1], "Inner Methods Compound Keys", IMSK[j])  t=
o
generate a length of 60 bytes
IMCK[j] =3D P_hash(S-IMCK[j-1], "Inner Methods Compound Keys=E2=80=9D | IMS=
K[j])


>
> MSK:
> Current Microsoft and Cisco implementation: P_hash(S-IMCK[j], "Session Ke=
y
> Generating Function=E2=80=9D | 0x00 | 0x00 | 0x40)
> Unified KDF proposal: TEAP-PRF(S-IMCK[j], "Session Key Generating
> Function=E2=80=9D, <no optional data>, 64) =3D P_hash(S-IMCK[j], "Session=
 Key
> Generating Function=E2=80=9D | 0x00 | 0x00 | 0x40)
> --- no implementation change
>
> [Joe] This is the one we have not discussed yet.  This derivation is also
ambiguous.  THis section does not reference 5295.  It's not clear if the
original intent was to include the length in the hash or not.  I think
there are a few interpretations:

1. TLS-PRF(S-IMCK[j], "Session Key Generating Function")  iterated to
generate 64 bytes =3D P_hash(S-IMCK[j], "Session Key Generating Function=E2=
=80=9D)
2. TLS-PRF(S-IMCK[j], "Session Key Generating Function", 64)  iterated to
generate 64 bytes =3D P_hash(S-IMCK[j], "Session Key Generating Function=E2=
=80=9D |
0x00 | 0x40)
3. (Follow 5295 parameters) TLS-PRF(S-IMCK[j], "Session Key Generating
Function", "\0" | 64) =3D P_hash(S-IMCK[j], "Session Key Generating Functio=
n=E2=80=9D
| 0x00 | 0x00 | 0x40)

I think 1 or 2 is what was probably originally intended, however it seems
that 3 is what has been implemented.  Do we have agreement on this is what
current implementations do?





> Jorge, please correct me if I misinterpret the Microsoft implementation.
>
> On Thu, Oct 22, 2020 at 6:55 PM Joseph Salowey <joe@salowey.net> wrote:
>
>>
>>
>> On Thu, Oct 22, 2020 at 6:59 AM Oleg Pekar <oleg.pekar.2017@gmail.com>
>> wrote:
>>
>>> Hi all,
>>> Speaking about both errata 5127 and 5128, I think we need to align all
>>> key derivation calls in TEAP RFC with the same rule/format to make the =
RFC
>>> easier to understand. This can be achieved by introducing a unified sin=
gle
>>> PRF function that will be called from all the relevant RFC locations. F=
or
>>> me it sounds better than if we align just part of KDF calls with RFC 52=
95
>>> (where the output length is included into seed). Also: in some KDF call=
s we
>>> do have optional data and in some no. This could be also unified.
>>>
>>> [Joe] I don't think this was the original intent of the document.  The
>> IMSK derivation referenced 5295 while the others just reference the TLS
>> PRF.  I think to unify them would require a document update and I'm not
>> sure what we would gain especially if we have implementations that do
>> this.
>>
>>
>>> So I would suggest introducing:
>>> TEAP-PRF (secret, key label, optional data, length) =3D TLS-PRF(secret,
>>> key label | 0x00 | optional data, length)
>>> where a single byte 0x00 is used for no optional data, length is a
>>> 2-octet unsigned integer in network byte order.
>>>
>>> [Joe] I don't think that 5295 specifies that a 0x00 is used to represen=
t
>> no optional data.  Did you see this in the spec? It may be ambiguous, bu=
t I
>> think the intent is that optional data is just omitted if it is not
>> provided.
>>
>>
>>
>>> Then:
>>> IMSK =3D First 32 octets of TEAP-PRF(EMSK, "TEAPbindkey@ietf.org", 64) =
=3D
>>> TLS-PRF(EMSK, "TEAPbindkey@ietf.org" | 0x00 | 0x00 | 0x00 | 0x40)
>>> IMCK[j] =3D TEAP-PRF(S-IMCK[j-1], "Inner Methods Compound Keys", IMSK[j=
],
>>> 60) =3D TLS-PRF(S-IMCK[j-1], "Inner Methods Compound Keys" | 0x00 | IMS=
K[j] |
>>> 0x00 | 0x3C)
>>> MSK =3D TEAP-PRF(S-IMCK[j], "Session Key Generating Function=E2=80=9D, =
64) =3D
>>> TLS-PRF(S-IMCK[j], "Session Key Generating Function" | 0x00 | 0x00 | 0x=
00 |
>>> 0x40)
>>> EMSK =3D TEAP-PRF(S-IMCK[j], =E2=80=9DExtended Session Key Generating F=
unction=E2=80=9D,
>>> 64) =3D TLS-PRF(S-IMCK[j], "Extended Session Key Generating Function" |=
 0x00
>>> | 0x00 | 0x00 | 0x40)
>>>
>>> This may change the existing implementation but will make it more clear
>>> - need to create and call just one KDF function.
>>>
>>> We can remove 0x00 that comes after the key label - while it is require=
d
>>> by RFC 5295. But there the key label is also ASCII printable string. Jo=
e,
>>> do you remember what was the motivation to put 0x00 after the key label
>>> parameter?
>>>
>>
>> [Joe] the null after the key label is to provide a delimiter between the
>> key label and optional data.  Since the optional data can be arbitrary
>> content the null prevents two different lablels with specially crafted
>> optional data from deriving the same key.
>>
>>
>>>
>>> Oleg
>>>
>>>
>>> On Thu, Oct 22, 2020 at 2:54 AM Joseph Salowey <joe@salowey.net> wrote:
>>>
>>>> (I accidentally dropped this list from the conversation)
>>>>
>>>> On Wed, Oct 21, 2020 at 4:48 PM Jorge Vergara <jovergar@microsoft.com>
>>>> wrote:
>>>>
>>>>> >[Joe] Yes this is a concern and I think your interpretation of the
>>>>> current document is also valid.  There may be more than one
>>>>> implementation.  So what you implemented was:
>>>>>
>>>>> >
>>>>>
>>>>> >IMCK[j] =3D TLS-PRF(S-IMCK[j-1], "Inner Methods Compound Keys", IMSK=
[j])
>>>>> =3D P_<hash>(S-IMCK[j-1], "Inner Methods Compound Keys" | IMSK[j])
>>>>>
>>>>>
>>>>>
>>>>> Yes, this is what I implemented. As you mentioned, there are multiple
>>>>> possible interpretations of this since the TEAP usage is incorrect.
>>>>> However, my implementation does interop with at least 2 large vendor
>>>>> implementations. If the implementations were using different calculat=
ions
>>>>> here, the Wi-Fi/Ethernet connections that depend on the MSK would fai=
l. But
>>>>> since connections work, I can assume we are all using the same
>>>>> implementation and arriving at the same MSK. Cisco is one of the
>>>>> implementations that I have tested against which is why I was hoping =
Oleg
>>>>> may offer more context as to what he has seen.
>>>>>
>>>>>
>>>>>
>>>> [Joe] I can hope Jouni can chime in on this as well.  I think the
>>>> original intent was to not include the length as is your suggestion.
>>>>
>>>>
>>>>
>>>>> >[Joe] Does the revision in 5167 match you implementation ( I don't
>>>>> think Jouni's comment changes the underly calculation, just its
>>>>> representation)?
>>>>>
>>>>>
>>>>>
>>>>> I have not implemented this portion of the RFC as I found it too
>>>>> unclear to work with. Thus I can=E2=80=99t comment on what implementa=
tions may be
>>>>> doing. However, I agree with the current revision in 5167 as the most
>>>>> natural interpretation. If others have implemented this portion of th=
e RFC
>>>>> then certainly their comments would be welcome.
>>>>>
>>>>>
>>>>> By the way, we=E2=80=99ve dropped the EMU group on our replies here =
=E2=80=93 not sure
>>>>> if intentional or not.
>>>>>
>>>>>
>>>>>
>>>>> Jorge Vergara
>>>>>
>>>>>
>>>>>
>>>>> *From:* Joseph Salowey <joe@salowey.net>
>>>>> *Sent:* Wednesday, October 21, 2020 4:36 PM
>>>>> *To:* Jorge Vergara <jovergar@microsoft.com>
>>>>> *Subject:* Re: Proposed resolution for TEAP errata for 5128
>>>>>
>>>>>
>>>>>
>>>>>
>>>>>
>>>>>
>>>>>
>>>>> On Wed, Oct 21, 2020 at 3:20 PM Jorge Vergara <jovergar@microsoft.com=
>
>>>>> wrote:
>>>>>
>>>>> In theory I agree this is a possible resolution. However, this doesn=
=E2=80=99t
>>>>> match any of the current TEAP implementations that I am aware of. Per=
haps
>>>>> Oleg can weigh in as well in terms of what he=E2=80=99s seen.
>>>>>
>>>>>
>>>>>
>>>>> I believe all current implementations treat 60 as the desired output
>>>>> length without treating as a seed. In terms of P_<hash>, this means
>>>>> implementations are performing the calculation without a seed.
>>>>>
>>>>>
>>>>>
>>>>> RFC 5246 defines the TLS 1.2 PRF as:
>>>>>
>>>>> PRF(secret, label, seed) =3D P_<hash>(secret, label + seed)
>>>>>
>>>>>
>>>>>
>>>>> So the calculation implementations are currently performing with an
>>>>> empty seed ends up as:
>>>>>
>>>>> P_<hash>(secret, label)
>>>>>
>>>>>
>>>>>
>>>>> Note that in RFC 5295, the length *is* explicitly mentioned as being
>>>>> concatenated with the label
>>>>>
>>>>> USRK =3D KDF(EMSK, key label | "\0" | optional data | length)
>>>>>
>>>>>
>>>>>
>>>>> RFC 5295 is mentioned earlier in the TEAP RFC, in the section covered
>>>>> by errata 5127. *However* it is not mentioned in this portion of the =
RFC.
>>>>> Since this calculation is not on an EMSK, I do not believe RFC 2395 a=
pplies
>>>>> and this is likely why implementations went with the seedless
>>>>> P_<hash>(secret, label) calculation instead.
>>>>>
>>>>>
>>>>>
>>>>> Is there concern about updating the RFC in a way that breaks existing
>>>>> implementations?
>>>>>
>>>>>
>>>>>
>>>>> [Joe] Yes this is a concern and I think your interpretation of the
>>>>> current document is also valid.  There may be more than one
>>>>> implementation.  So what you implemented was:
>>>>>
>>>>>
>>>>>
>>>>> IMCK[j] =3D TLS-PRF(S-IMCK[j-1], "Inner Methods Compound Keys", IMSK[=
j])
>>>>> =3D P_<hash>(S-IMCK[j-1], "Inner Methods Compound Keys" | IMSK[j])
>>>>>
>>>>>
>>>>>
>>>>> taken out to 60 bytes.  The problem is that the TEAP spec references =
a
>>>>> TLS-PRF in a way that it does not define.  I think the errata points =
out
>>>>> the definition that should be used:
>>>>>
>>>>>
>>>>>
>>>>> PRF(secret, label, seed) =3D P_<hash>(secret, label + seed)
>>>>>
>>>>>
>>>>>
>>>>> That does not include length so the 60 in the original definition is
>>>>> ambiguous.   The new text would then be something like:
>>>>>
>>>>>
>>>>>
>>>>> IMCK[j] =3D TLS-PRF(S-IMCK[j-1], "Inner Methods Compound Keys", IMSK[=
j])
>>>>> to generate a length of 60 bytes
>>>>>
>>>>>
>>>>>
>>>>> Does the revision in 5167 match you implementation ( I don't think
>>>>> Jouni's comment changes the underly calculation, just its representat=
ion)?
>>>>>
>>>>>
>>>>>
>>>>>
>>>>>
>>>>>
>>>>>
>>>>>
>>>>>
>>>>>
>>>>>
>>>>> Jorge Vergara
>>>>>
>>>>>
>>>>>
>>>>> *From:* Joseph Salowey <joe@salowey.net>
>>>>> *Sent:* Wednesday, October 21, 2020 2:34 PM
>>>>> *To:* EMU WG <emu@ietf.org>; Jouni Malinen <j@w1.fi>; Jorge Vergara <
>>>>> jovergar@microsoft.com>; Oleg Pekar (olpekar) <olpekar@cisco.com>
>>>>> *Subject:* Proposed resolution for TEAP errata for 5128
>>>>>
>>>>>
>>>>>
>>>>> Errata 5128: https://www.rfc-editor.org/errata/eid5128
>>>>> <https://nam06.safelinks.protection.outlook.com/?url=3Dhttps%3A%2F%2F=
www.rfc-editor.org%2Ferrata%2Feid5128&data=3D04%7C01%7Cjovergar%40microsoft=
.com%7C38c27add2cb64a06310108d8761a22d3%7C72f988bf86f141af91ab2d7cd011db47%=
7C1%7C0%7C637389201909062787%7CUnknown%7CTWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLC=
JQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D%7C1000&sdata=3DXudZt9FPh4jOBFQ=
j01SQysnhX4p7G%2BflW2Pn2yIaJRM%3D&reserved=3D0>
>>>>>
>>>>> Proposed State: Verified
>>>>>
>>>>> Revision:
>>>>>
>>>>>
>>>>>
>>>>> Section 5.2. says
>>>>>
>>>>>
>>>>> IMCK[j] =3D TLS-PRF(S-IMCK[j-1], "Inner Methods Compound Keys",
>>>>>                 IMSK[j], 60)
>>>>>
>>>>> It should say:
>>>>>
>>>>> IMCK[j] =3D TLS-PRF(S-IMCK[j-1], "Inner Methods Compound Keys", IMSK[=
j]
>>>>> | 60)
>>>>>
>>>>> Note:
>>>>>
>>>>> According to
>>>>>
>>>>> RFC5246 The Transport Layer Security (TLS) Protocol Version 1.2
>>>>>
>>>>> 5. HMAC and the Pseudorandom Function
>>>>>
>>>>> "TLS's PRF is created by applying P_hash to the secret as:
>>>>>
>>>>> PRF(secret, label, seed) =3D P_<hash>(secret, label + seed)"
>>>>>
>>>>>
>>>>>
>>>>> In terms of P_<hash> this would look like the following with the
>>>>> length represented as a 2 byte value in network byte order:
>>>>>
>>>>>
>>>>>
>>>>> IMCK[j] =3D P_<hash>(S-IMCK[j-1], "Inner Methods Compound Keys" | IMS=
K[j]
>>>>> | 0x00 | 0x3C)
>>>>>
>>>>>
>>>>>
>>>>>
>>>>>
>>>>>

--0000000000006441ea05b2454dce
Content-Type: text/html; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable

<div dir=3D"ltr"><div dir=3D"ltr"><br></div><br><div class=3D"gmail_quote">=
<div dir=3D"ltr" class=3D"gmail_attr">On Thu, Oct 22, 2020 at 9:29 AM Oleg =
Pekar &lt;<a href=3D"mailto:oleg.pekar.2017@gmail.com" target=3D"_blank">ol=
eg.pekar.2017@gmail.com</a>&gt; wrote:<br></div><blockquote class=3D"gmail_=
quote" style=3D"margin:0px 0px 0px 0.8ex;border-left:1px solid rgb(204,204,=
204);padding-left:1ex"><div dir=3D"ltr">I agree that changing the KDF is ha=
rmful to existing implementations. However, if I understood correctly, Joe&=
#39;s suggestion=C2=A0for IMCK[j] also breaks the existing=C2=A0implementat=
ion. I still see that we can define a unified KDF by changing the API in th=
e RFC but with the same harm to the existing implementation in IMCK[j] as i=
n both proposals:<div><br></div><div>TEAP-PRF (secret, key label, optional =
data, length) =3D TLS-PRF(secret, key label | 0x00 | optional data, length)=
</div><div>Joe, thanks for pointing out that RFC 5295 doesn&#39;t specify t=
hat a 0x00 is used to represent no optional data, that was just my mistake.=
</div><div><br><div>IMSK:</div><div>Current Microsoft and Cisco implementat=
ion: P_hash(EMSK, &quot;<a href=3D"mailto:TEAPbindkey@ietf.org" target=3D"_=
blank">TEAPbindkey@ietf.org</a>&quot; | 0x00 | 0x00 | 0x40) <br></div><div>=
Joe&#39;s proposal: P_hash(EMSK, &quot;<a href=3D"mailto:TEAPbindkey@ietf.o=
rg" target=3D"_blank">TEAPbindkey@ietf.org</a>&quot; | 0x00 | 0x00 | 0x40),=
 the same, just the API correction<br></div><div>Unified KDF proposal:=C2=
=A0TEAP-PRF(EMSK, &quot;<a href=3D"mailto:TEAPbindkey@ietf.org" target=3D"_=
blank">TEAPbindkey@ietf.org</a>&quot;, &lt;no optional data&gt;, 64) =3D P_=
hash(EMSK, &quot;<a href=3D"mailto:TEAPbindkey@ietf.org" target=3D"_blank">=
TEAPbindkey@ietf.org</a>&quot; | 0x00 | 0x00 | 0x40)=C2=A0<br></div><div>--=
- no implementation change</div><div><br></div><div>IMCK[j]:<br></div><div>=
<div>Current Microsoft and Cisco implementation: P_hash(S-IMCK[j-1], &quot;=
Inner Methods Compound Keys=E2=80=9D | IMSK[j])=C2=A0<br></div><div>Joe&#39=
;s proposal:=C2=A0P_hash(S-IMCK[j-1], &quot;Inner Methods Compound Keys&quo=
t; | IMSK[j] | 0x00 | 0x3C)<br></div><div>Unified KDF proposal: TEAP-PRF(S-=
IMCK[j-1], &quot;Inner Methods Compound Keys&quot;, IMSK[j], 60) =3D P_hash=
(S-IMCK[j-1], &quot;Inner Methods Compound Keys&quot; | IMSK[j] | 0x00 | 0x=
3C)</div></div><div><div>--- implementation change</div></div></div></div><=
/blockquote><div><br></div><div>[Joe] That was my initial proposal, but bas=
ed on Jorge&#39;s comment it is modified to:</div><div><br class=3D"gmail-A=
pple-interchange-newline">IMCK[j] =3D TLS-PRF(S-IMCK[j-1], &quot;Inner Meth=
ods Compound Keys&quot;,=C2=A0<span style=3D"color:rgb(44,67,83);font-size:=
14px">IMSK[j])=C2=A0 to generate a length of 60 bytes</span></div><div><fon=
t color=3D"#2c4353"><span style=3D"font-size:14px">IMCK[j] =3D=C2=A0</span>=
</font>P_hash(S-IMCK[j-1], &quot;Inner Methods Compound Keys=E2=80=9D | IMS=
K[j])=C2=A0</div><div>=C2=A0</div><blockquote class=3D"gmail_quote" style=
=3D"margin:0px 0px 0px 0.8ex;border-left:1px solid rgb(204,204,204);padding=
-left:1ex"><div dir=3D"ltr"><div><div><div></div></div><div><br></div><div>=
MSK:</div><div>Current Microsoft and Cisco implementation: P_hash(S-IMCK[j]=
, &quot;Session Key Generating Function=E2=80=9D | 0x00 | 0x00 | 0x40)</div=
><div>Unified KDF proposal:  TEAP-PRF(S-IMCK[j], &quot;Session Key Generati=
ng Function=E2=80=9D, &lt;no optional data&gt;,  64) =3D P_hash(S-IMCK[j], =
&quot;Session Key Generating Function=E2=80=9D | 0x00 | 0x00 | 0x40)</div><=
div><div>--- no implementation change</div><div></div></div><div><br></div>=
</div></div></blockquote><div>[Joe] This is the one we have not discussed y=
et.=C2=A0 This derivation is also ambiguous.=C2=A0 THis section does not re=
ference 5295.=C2=A0 It&#39;s not clear if the original intent was to includ=
e the length in the hash or not.=C2=A0 I think there are a few interpretati=
ons:</div><div><br></div><div><span style=3D"color:rgb(0,0,0);font-size:13.=
3333px">1. TLS-PRF(S-IMCK[j], &quot;Session Key Generating Function&quot;)<=
/span>=C2=A0 iterated to generate 64 bytes =3D=C2=A0P_hash(S-IMCK[j], &quot=
;Session Key Generating Function=E2=80=9D)</div><div><span style=3D"color:r=
gb(0,0,0);font-size:13.3333px">2. TLS-PRF(S-IMCK[j], &quot;Session Key Gene=
rating Function&quot;, 64)</span>=C2=A0 iterated to generate 64 bytes =3D=
=C2=A0P_hash(S-IMCK[j], &quot;Session Key Generating Function=E2=80=9D | 0x=
00 | 0x40)<br></div><div>3. (Follow 5295 parameters)=C2=A0<span style=3D"co=
lor:rgb(0,0,0);font-size:13.3333px">TLS-PRF(S-IMCK[j], &quot;Session Key Ge=
nerating Function&quot;, &quot;\0&quot; | 64)</span>=C2=A0=3D=C2=A0P_hash(S=
-IMCK[j], &quot;Session Key Generating Function=E2=80=9D | 0x00 | 0x00 | 0x=
40)</div><div><br></div><div>I think 1 or 2 is what was probably originally=
 intended, however it seems that 3 is what has been implemented.=C2=A0 Do w=
e have agreement on this is what current implementations do?=C2=A0</div><di=
v><pre class=3D"gmail-newpage" style=3D"font-size:13.3333px;margin-top:0px;=
margin-bottom:0px;break-before:page;color:rgb(0,0,0)"><br></pre></div><div>=
<br></div><div>=C2=A0</div><blockquote class=3D"gmail_quote" style=3D"margi=
n:0px 0px 0px 0.8ex;border-left:1px solid rgb(204,204,204);padding-left:1ex=
"><div dir=3D"ltr"><div><div></div><div>Jorge, please correct me if I misin=
terpret=C2=A0the Microsoft implementation.=C2=A0</div></div></div><br><div =
class=3D"gmail_quote"><div dir=3D"ltr" class=3D"gmail_attr">On Thu, Oct 22,=
 2020 at 6:55 PM Joseph Salowey &lt;<a href=3D"mailto:joe@salowey.net" targ=
et=3D"_blank">joe@salowey.net</a>&gt; wrote:<br></div><blockquote class=3D"=
gmail_quote" style=3D"margin:0px 0px 0px 0.8ex;border-left:1px solid rgb(20=
4,204,204);padding-left:1ex"><div dir=3D"ltr"><div dir=3D"ltr"><br></div><b=
r><div class=3D"gmail_quote"><div dir=3D"ltr" class=3D"gmail_attr">On Thu, =
Oct 22, 2020 at 6:59 AM Oleg Pekar &lt;<a href=3D"mailto:oleg.pekar.2017@gm=
ail.com" target=3D"_blank">oleg.pekar.2017@gmail.com</a>&gt; wrote:<br></di=
v><blockquote class=3D"gmail_quote" style=3D"margin:0px 0px 0px 0.8ex;borde=
r-left:1px solid rgb(204,204,204);padding-left:1ex"><div dir=3D"ltr"><div>H=
i all,</div><div>Speaking about both errata 5127 and 5128, I think we need =
to align all key derivation calls in TEAP RFC with the same rule/format to =
make the RFC easier to understand. This can be achieved by introducing a un=
ified single PRF function that will be called from all the relevant RFC loc=
ations. For me it sounds better than if we align just part of KDF calls wit=
h RFC 5295 (where the output length is included into seed). Also: in some K=
DF calls we do have optional data and in some no. This could be also unifie=
d.=C2=A0</div><div><br></div></div></blockquote><div>[Joe] I don&#39;t thin=
k this was the original intent of the document.=C2=A0 The IMSK derivation r=
eferenced 5295 while the others just reference the TLS PRF.=C2=A0 I think t=
o unify them would require a document update and I&#39;m not sure what we w=
ould gain especially if we have implementations that do this.=C2=A0=C2=A0</=
div><div>=C2=A0</div><blockquote class=3D"gmail_quote" style=3D"margin:0px =
0px 0px 0.8ex;border-left:1px solid rgb(204,204,204);padding-left:1ex"><div=
 dir=3D"ltr"><div></div><div>So I would suggest introducing:</div><div>TEAP=
-PRF (secret, key label, optional data, length) =3D TLS-PRF(secret, key lab=
el | 0x00 | optional data, length)<br></div><div>where a single byte 0x00 i=
s used for no optional data, length is a 2-octet unsigned integer in networ=
k byte order.<br></div><div><br></div></div></blockquote><div>[Joe] I don&#=
39;t think that 5295 specifies that a 0x00 is used to represent no optional=
 data.=C2=A0 Did you see this in the spec? It may be ambiguous, but I think=
 the intent is that optional data is just omitted if it is not provided.=C2=
=A0</div><div><br></div><div>=C2=A0</div><blockquote class=3D"gmail_quote" =
style=3D"margin:0px 0px 0px 0.8ex;border-left:1px solid rgb(204,204,204);pa=
dding-left:1ex"><div dir=3D"ltr"><div></div><div>Then:</div><div>IMSK =3D F=
irst 32 octets of TEAP-PRF(EMSK, &quot;<a href=3D"mailto:TEAPbindkey@ietf.o=
rg" target=3D"_blank">TEAPbindkey@ietf.org</a>&quot;, 64) =3D TLS-PRF(EMSK,=
 &quot;<a href=3D"mailto:TEAPbindkey@ietf.org" target=3D"_blank">TEAPbindke=
y@ietf.org</a>&quot; | 0x00 | 0x00 | 0x00 | 0x40)<br>IMCK[j] =3D TEAP-PRF(S=
-IMCK[j-1], &quot;Inner Methods Compound Keys&quot;, IMSK[j], 60) =3D TLS-P=
RF(S-IMCK[j-1], &quot;Inner Methods Compound Keys&quot; | 0x00 | IMSK[j] | =
0x00 | 0x3C)<br>MSK =3D TEAP-PRF(S-IMCK[j], &quot;Session Key Generating Fu=
nction=E2=80=9D, 64) =3D TLS-PRF(S-IMCK[j], &quot;Session Key Generating Fu=
nction&quot; | 0x00 | 0x00 | 0x00 | 0x40)<br>EMSK =3D TEAP-PRF(S-IMCK[j], =
=E2=80=9DExtended Session Key Generating Function=E2=80=9D, 64) =3D TLS-PRF=
(S-IMCK[j], &quot;Extended Session Key Generating Function&quot; | 0x00 | 0=
x00 | 0x00 | 0x40)<br></div><div><br></div><div>This may change the existin=
g implementation but will make it more clear - need to create and call just=
 one KDF function.</div><div><br></div><div>We can remove=C2=A00x00 that co=
mes after the key label - while it is required by=C2=A0RFC 5295. But there=
=C2=A0the key label is also ASCII printable string. Joe, do you remember wh=
at was the motivation to put 0x00 after the key label parameter?</div></div=
></blockquote><div><br></div><div>[Joe] the null after the key label is to =
provide a delimiter between the key label and optional data.=C2=A0 Since th=
e optional data can be arbitrary content the null prevents two different la=
blels=C2=A0with specially=C2=A0crafted optional data from deriving the same=
 key.=C2=A0=C2=A0</div><div>=C2=A0</div><blockquote class=3D"gmail_quote" s=
tyle=3D"margin:0px 0px 0px 0.8ex;border-left:1px solid rgb(204,204,204);pad=
ding-left:1ex"><div dir=3D"ltr"><div><br></div><div>Oleg</div><div><br></di=
v><div><br></div><div class=3D"gmail_quote"><div dir=3D"ltr" class=3D"gmail=
_attr">On Thu, Oct 22, 2020 at 2:54 AM Joseph Salowey &lt;<a href=3D"mailto=
:joe@salowey.net" target=3D"_blank">joe@salowey.net</a>&gt; wrote:<br></div=
><blockquote class=3D"gmail_quote" style=3D"margin:0px 0px 0px 0.8ex;border=
-left:1px solid rgb(204,204,204);padding-left:1ex"><div dir=3D"ltr"><div>(I=
 accidentally=C2=A0dropped this list from the conversation)</div><br><div c=
lass=3D"gmail_quote"><div dir=3D"ltr" class=3D"gmail_attr">On Wed, Oct 21, =
2020 at 4:48 PM Jorge Vergara &lt;<a href=3D"mailto:jovergar@microsoft.com"=
 target=3D"_blank">jovergar@microsoft.com</a>&gt; wrote:<br></div><blockquo=
te class=3D"gmail_quote" style=3D"margin:0px 0px 0px 0.8ex;border-left:1px =
solid rgb(204,204,204);padding-left:1ex">





<div lang=3D"EN-US">
<div>
<p class=3D"MsoNormal">&gt;[Joe] Yes this is a concern and I think your=C2=
=A0interpretation of the current document is also valid.=C2=A0 There may be=
 more than one implementation.=C2=A0 So what you implemented was:<u></u><u>=
</u></p>
<p class=3D"MsoNormal">&gt;<u></u>=C2=A0<u></u></p>
<p class=3D"MsoNormal">&gt;IMCK[j] =3D TLS-PRF(S-IMCK[j-1], &quot;Inner Met=
hods Compound Keys&quot;,=C2=A0<span style=3D"font-size:10.5pt;color:rgb(44=
,67,83)">IMSK[j]) =3D P_&lt;hash&gt;(S-IMCK[j-1], &quot;Inner Methods Compo=
und Keys&quot; | IMSK[j])</span><u></u><u></u></p>
<p class=3D"MsoNormal"><u></u>=C2=A0<u></u></p>
<p class=3D"MsoNormal">Yes, this is what I implemented. As you mentioned, t=
here are multiple possible interpretations of this since the TEAP usage is =
incorrect. However, my implementation does interop with at least 2 large ve=
ndor implementations. If the implementations
 were using different calculations here, the Wi-Fi/Ethernet connections tha=
t depend on the MSK would fail. But since connections work, I can assume we=
 are all using the same implementation and arriving at the same MSK. Cisco =
is one of the implementations that
 I have tested against which is why I was hoping Oleg may offer more contex=
t as to what he has seen.<u></u><u></u></p>
<p class=3D"MsoNormal"><u></u>=C2=A0</p></div></div></blockquote><div>[Joe]=
 I can hope Jouni can chime in on this as well.=C2=A0 I think the original =
intent was to not include the length as is your suggestion.=C2=A0</div><div=
><br></div><div>=C2=A0</div><blockquote class=3D"gmail_quote" style=3D"marg=
in:0px 0px 0px 0.8ex;border-left:1px solid rgb(204,204,204);padding-left:1e=
x"><div lang=3D"EN-US"><div><p class=3D"MsoNormal"><u></u></p>
<p class=3D"MsoNormal">&gt;[Joe]<span style=3D"font-size:10.5pt;color:rgb(4=
4,67,83)"> Does the revision in 5167 match you implementation ( I don&#39;t=
 think Jouni&#39;s=C2=A0comment changes the underly=C2=A0calculation, just =
its representation)?=C2=A0</span><u></u><u></u></p>
<p class=3D"MsoNormal"><u></u>=C2=A0<u></u></p>
<p class=3D"MsoNormal">I have not implemented this portion of the RFC as I =
found it too unclear to work with. Thus I can=E2=80=99t comment on what imp=
lementations may be doing. However, I agree with the current revision in 51=
67 as the most natural interpretation. If
 others have implemented this portion of the RFC then certainly their comme=
nts would be welcome.<u></u><u></u></p>
<p class=3D"MsoNormal"><br><u></u></p></div></div></blockquote><blockquote =
class=3D"gmail_quote" style=3D"margin:0px 0px 0px 0.8ex;border-left:1px sol=
id rgb(204,204,204);padding-left:1ex"><div lang=3D"EN-US"><div><p class=3D"=
MsoNormal"><u></u></p>
<p class=3D"MsoNormal">By the way, we=E2=80=99ve dropped the EMU group on o=
ur replies here =E2=80=93 not sure if intentional or not.<u></u><u></u></p>
<p class=3D"MsoNormal"><u></u>=C2=A0<u></u></p>
<p class=3D"MsoNormal">Jorge Vergara<u></u><u></u></p>
<p class=3D"MsoNormal"><u></u>=C2=A0<u></u></p>
<div style=3D"border-right:none;border-bottom:none;border-left:none;border-=
top:1pt solid rgb(225,225,225);padding:3pt 0in 0in">
<p class=3D"MsoNormal"><b>From:</b> Joseph Salowey &lt;<a href=3D"mailto:jo=
e@salowey.net" target=3D"_blank">joe@salowey.net</a>&gt; <br>
<b>Sent:</b> Wednesday, October 21, 2020 4:36 PM<br>
<b>To:</b> Jorge Vergara &lt;<a href=3D"mailto:jovergar@microsoft.com" targ=
et=3D"_blank">jovergar@microsoft.com</a>&gt;<br>
<b>Subject:</b> Re: Proposed resolution for TEAP errata for 5128<u></u><u><=
/u></p>
</div>
<p class=3D"MsoNormal"><u></u>=C2=A0<u></u></p>
<div>
<div>
<p class=3D"MsoNormal"><u></u>=C2=A0<u></u></p>
</div>
<p class=3D"MsoNormal"><u></u>=C2=A0<u></u></p>
<div>
<div>
<p class=3D"MsoNormal">On Wed, Oct 21, 2020 at 3:20 PM Jorge Vergara &lt;<a=
 href=3D"mailto:jovergar@microsoft.com" target=3D"_blank">jovergar@microsof=
t.com</a>&gt; wrote:<u></u><u></u></p>
</div>
<blockquote style=3D"border-top:none;border-right:none;border-bottom:none;b=
order-left:1pt solid rgb(204,204,204);padding:0in 0in 0in 6pt;margin-left:4=
.8pt;margin-right:0in">
<div>
<div>
<p class=3D"MsoNormal">In theory I agree this is a possible resolution. How=
ever, this doesn=E2=80=99t match any of the current TEAP implementations th=
at I am aware of. Perhaps Oleg can weigh in as well in terms
 of what he=E2=80=99s seen.<u></u><u></u></p>
<p class=3D"MsoNormal">=C2=A0<u></u><u></u></p>
<p class=3D"MsoNormal">I believe all current implementations treat 60 as th=
e desired output length without treating as a seed. In terms of P_&lt;hash&=
gt;, this means implementations are performing the calculation
 without a seed.<u></u><u></u></p>
<p class=3D"MsoNormal">=C2=A0<u></u><u></u></p>
<p class=3D"MsoNormal">RFC 5246 defines the TLS 1.2 PRF as:<u></u><u></u></=
p>
<p class=3D"MsoNormal">PRF(secret, label, seed) =3D P_&lt;hash&gt;(secret, =
label + seed)<u></u><u></u></p>
<p class=3D"MsoNormal">=C2=A0<u></u><u></u></p>
<p class=3D"MsoNormal">So the calculation implementations are currently per=
forming with an empty seed ends up as:<u></u><u></u></p>
<p class=3D"MsoNormal">P_&lt;hash&gt;(secret, label)<u></u><u></u></p>
<p class=3D"MsoNormal">=C2=A0<u></u><u></u></p>
<p class=3D"MsoNormal">Note that in RFC 5295, the length *is* explicitly me=
ntioned as being concatenated with the label<u></u><u></u></p>
<p class=3D"MsoNormal">USRK =3D KDF(EMSK, key label | &quot;\0&quot; | opti=
onal data | length)<u></u><u></u></p>
<p class=3D"MsoNormal">=C2=A0<u></u><u></u></p>
<p class=3D"MsoNormal">RFC 5295 is mentioned earlier in the TEAP RFC, in th=
e section covered by errata 5127. *However* it is not mentioned in this por=
tion of the RFC. Since this calculation is not on
 an EMSK, I do not believe RFC 2395 applies and this is likely why implemen=
tations went with the seedless P_&lt;hash&gt;(secret, label) calculation in=
stead.<u></u><u></u></p>
<p class=3D"MsoNormal">=C2=A0<u></u><u></u></p>
<p class=3D"MsoNormal">Is there concern about updating the RFC in a way tha=
t breaks existing implementations?<u></u><u></u></p>
<p class=3D"MsoNormal">=C2=A0<u></u><u></u></p>
</div>
</div>
</blockquote>
<div>
<p class=3D"MsoNormal">[Joe] Yes this is a concern and I think your=C2=A0in=
terpretation of the current document is also valid.=C2=A0 There may be more=
 than one implementation.=C2=A0 So what you implemented was:<u></u><u></u><=
/p>
</div>
<div>
<p class=3D"MsoNormal"><u></u>=C2=A0<u></u></p>
</div>
<div>
<p class=3D"MsoNormal">IMCK[j] =3D TLS-PRF(S-IMCK[j-1], &quot;Inner Methods=
 Compound Keys&quot;,=C2=A0<span style=3D"font-size:10.5pt;color:rgb(44,67,=
83)">IMSK[j]) =3D P_&lt;hash&gt;(S-IMCK[j-1], &quot;Inner Methods Compound =
Keys&quot; | IMSK[j])</span><u></u><u></u></p>
</div>
<div>
<p class=3D"MsoNormal"><u></u>=C2=A0<u></u></p>
</div>
<div>
<p class=3D"MsoNormal">taken out to 60 bytes.=C2=A0 The problem is that the=
 TEAP spec references a TLS-PRF in a way that it does not define.=C2=A0 I t=
hink the errata points out the definition that should be used:<u></u><u></u=
></p>
</div>
<div>
<p class=3D"MsoNormal"><u></u>=C2=A0<u></u></p>
</div>
<div>
<p class=3D"MsoNormal">PRF(secret, label, seed) =3D P_&lt;hash&gt;(secret, =
label + seed)<u></u><u></u></p>
</div>
<div>
<p class=3D"MsoNormal"><u></u>=C2=A0<u></u></p>
</div>
<div>
<p class=3D"MsoNormal">That does not include length so the 60 in the origin=
al definition=C2=A0is ambiguous.=C2=A0 =C2=A0The new text would then be som=
ething like:<u></u><u></u></p>
</div>
<div>
<p class=3D"MsoNormal"><u></u>=C2=A0<u></u></p>
</div>
<div>
<p class=3D"MsoNormal">IMCK[j] =3D TLS-PRF(S-IMCK[j-1], &quot;Inner Methods=
 Compound Keys&quot;,=C2=A0<span style=3D"font-size:10.5pt;color:rgb(44,67,=
83)">IMSK[j])=C2=A0 to generate a length of 60 bytes</span><u></u><u></u></=
p>
</div>
<div>
<p class=3D"MsoNormal"><u></u>=C2=A0<u></u></p>
</div>
<div>
<p class=3D"MsoNormal"><span style=3D"font-size:10.5pt;color:rgb(44,67,83)"=
>Does the revision in 5167 match you implementation ( I don&#39;t think Jou=
ni&#39;s=C2=A0comment changes the underly=C2=A0calculation, just its repres=
entation)?=C2=A0</span><u></u><u></u></p>
</div>
<div>
<p class=3D"MsoNormal"><u></u>=C2=A0<u></u></p>
</div>
<div>
<p class=3D"MsoNormal"><u></u>=C2=A0<u></u></p>
</div>
<div>
<p class=3D"MsoNormal"><u></u>=C2=A0<u></u></p>
</div>
<div>
<p class=3D"MsoNormal"><u></u>=C2=A0<u></u></p>
</div>
<div>
<p class=3D"MsoNormal">=C2=A0<u></u><u></u></p>
</div>
<blockquote style=3D"border-top:none;border-right:none;border-bottom:none;b=
order-left:1pt solid rgb(204,204,204);padding:0in 0in 0in 6pt;margin-left:4=
.8pt;margin-right:0in">
<div>
<div>
<p class=3D"MsoNormal">Jorge Vergara<u></u><u></u></p>
<p class=3D"MsoNormal">=C2=A0<u></u><u></u></p>
<div style=3D"border-right:none;border-bottom:none;border-left:none;border-=
top:1pt solid rgb(225,225,225);padding:3pt 0in 0in">
<p class=3D"MsoNormal"><b>From:</b> Joseph Salowey &lt;<a href=3D"mailto:jo=
e@salowey.net" target=3D"_blank">joe@salowey.net</a>&gt;
<br>
<b>Sent:</b> Wednesday, October 21, 2020 2:34 PM<br>
<b>To:</b> EMU WG &lt;<a href=3D"mailto:emu@ietf.org" target=3D"_blank">emu=
@ietf.org</a>&gt;; Jouni Malinen &lt;<a href=3D"mailto:j@w1.fi" target=3D"_=
blank">j@w1.fi</a>&gt;; Jorge Vergara &lt;<a href=3D"mailto:jovergar@micros=
oft.com" target=3D"_blank">jovergar@microsoft.com</a>&gt;; Oleg
 Pekar (olpekar) &lt;<a href=3D"mailto:olpekar@cisco.com" target=3D"_blank"=
>olpekar@cisco.com</a>&gt;<br>
<b>Subject:</b> Proposed resolution for TEAP errata for 5128<u></u><u></u><=
/p>
</div>
<p class=3D"MsoNormal">=C2=A0<u></u><u></u></p>
<div>
<p class=3D"MsoNormal">Errata 5128:=C2=A0<a href=3D"https://nam06.safelinks=
.protection.outlook.com/?url=3Dhttps%3A%2F%2Fwww.rfc-editor.org%2Ferrata%2F=
eid5128&amp;data=3D04%7C01%7Cjovergar%40microsoft.com%7C38c27add2cb64a06310=
108d8761a22d3%7C72f988bf86f141af91ab2d7cd011db47%7C1%7C0%7C6373892019090627=
87%7CUnknown%7CTWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1h=
aWwiLCJXVCI6Mn0%3D%7C1000&amp;sdata=3DXudZt9FPh4jOBFQj01SQysnhX4p7G%2BflW2P=
n2yIaJRM%3D&amp;reserved=3D0" target=3D"_blank">https://www.rfc-editor.org/=
errata/eid5128</a><u></u><u></u></p>
<div>
<p class=3D"MsoNormal">Proposed State: Verified<u></u><u></u></p>
</div>
<div>
<p class=3D"MsoNormal">Revision:<u></u><u></u></p>
</div>
<div>
<p class=3D"MsoNormal">=C2=A0<u></u><u></u></p>
</div>
<div>
<p class=3D"MsoNormal">Section 5.2. says<u></u><u></u></p>
</div>
<div>
<p style=3D"margin-right:3.75pt;margin-bottom:7.5pt;margin-left:3.75pt">
<br>
IMCK[j] =3D TLS-PRF(S-IMCK[j-1], &quot;Inner Methods Compound Keys&quot;,<b=
r>
=C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 IMSK[j], 60)<br>
<br>
It should say:<br>
<br>
IMCK[j] =3D TLS-PRF(S-IMCK[j-1], &quot;Inner Methods Compound Keys&quot;,=
=C2=A0<span style=3D"font-size:10.5pt;font-family:Arial,sans-serif;color:rg=
b(44,67,83)">IMSK[j] | 60)</span><u></u><u></u></p>
<p style=3D"margin-right:3.75pt;margin-bottom:7.5pt;margin-left:3.75pt">
<span style=3D"font-size:10.5pt;font-family:Arial,sans-serif;color:rgb(44,6=
7,83)">Note:=C2=A0=C2=A0</span><u></u><u></u></p>
<p class=3D"MsoNormal">According to<br>
<br>
RFC5246 The Transport Layer Security (TLS) Protocol Version 1.2<br>
<br>
5. HMAC and the Pseudorandom Function<br>
<br>
&quot;TLS&#39;s PRF is created by applying P_hash to the secret as:<br>
<br>
PRF(secret, label, seed) =3D P_&lt;hash&gt;(secret, label + seed)&quot;<u><=
/u><u></u></p>
</div>
<div>
<p class=3D"MsoNormal">=C2=A0<u></u><u></u></p>
</div>
<div>
<p class=3D"MsoNormal">In terms of P_&lt;hash&gt; this would look like the =
following with the length represented as a 2 byte value in network byte ord=
er:<u></u><u></u></p>
</div>
<div>
<p class=3D"MsoNormal">=C2=A0<u></u><u></u></p>
</div>
<div>
<p class=3D"MsoNormal">IMCK[j] =3D P_&lt;hash&gt;(S-IMCK[j-1], &quot;Inner =
Methods Compound Keys&quot; |=C2=A0<span style=3D"font-size:10.5pt;color:rg=
b(44,67,83)">IMSK[j] | 0x00 | 0x3C)</span><u></u><u></u></p>
</div>
<div>
<p class=3D"MsoNormal">=C2=A0<u></u><u></u></p>
</div>
<div>
<p class=3D"MsoNormal">=C2=A0<u></u><u></u></p>
</div>
</div>
</div>
</div>
</blockquote>
</div>
</div>
</div>
</div>

</blockquote></div></div>
</blockquote></div></div>
</blockquote></div></div>
</blockquote></div>
</blockquote></div></div>

--0000000000006441ea05b2454dce--


From nobody Thu Oct 22 09:58:31 2020
Return-Path: <jovergar@microsoft.com>
X-Original-To: emu@ietfa.amsl.com
Delivered-To: emu@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 87B9B3A08DC for <emu@ietfa.amsl.com>; Thu, 22 Oct 2020 09:58:29 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.001
X-Spam-Level: 
X-Spam-Status: No, score=-2.001 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIMWL_WL_HIGH=-0.001, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, DKIM_VALID_EF=-0.1, HTML_MESSAGE=0.001, HTTPS_HTTP_MISMATCH=0.1, RCVD_IN_MSPIKE_H2=-0.001, SPF_PASS=-0.001, URIBL_BLOCKED=0.001] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (1024-bit key) header.d=microsoft.com
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 guRbTVgpfDxB for <emu@ietfa.amsl.com>; Thu, 22 Oct 2020 09:58:26 -0700 (PDT)
Received: from NAM11-DM6-obe.outbound.protection.outlook.com (mail-dm6nam11on2104.outbound.protection.outlook.com [40.107.223.104]) (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 E229C3A09CD for <emu@ietf.org>; Thu, 22 Oct 2020 09:58:15 -0700 (PDT)
ARC-Seal: i=1; a=rsa-sha256; s=arcselector9901; d=microsoft.com; cv=none; b=F0F6uNuIWvhz86VxmSdnZjs5o82xInnoBrbnErxick01AnFwT26zbvju5qJep419EUjb97XaXOGIbhGgzUlXOLmtxM/SV30q5Am7xyHsCyGHM/OkwdR1Op2cg0hs7+Qg0OC/KKD4ADgKtsgBS7TMwvG8NW8z00ywbllfeLZD109smO+Jq1VLDSgRkPkplP/DgsHWdK5JTvQLNHBcPMi5uspGGE5LoGG7tIb5bUzegV3kKzXH5RwhLcYtG91UGMsCAFI5ssZYomrgKqEHfcaITbo3QBMDc0ek9bZxq0X3+N/wnw5AOBBnu0wO0LSuR6HnxJssLCmWCzUYFGmY3zVH1g==
ARC-Message-Signature: i=1; a=rsa-sha256; c=relaxed/relaxed; d=microsoft.com;  s=arcselector9901; h=From:Date:Subject:Message-ID:Content-Type:MIME-Version:X-MS-Exchange-SenderADCheck; bh=AN3HMd4nNY+Tt8V7WCm+FXgrFDl+0weWdWIiVdKqRJs=; b=dqWD2XDLMN1mFCVoakUuhMF7KrRVTZ8Is7pGlWzh8NRvmz5a3laTHvlVTnkZ5hC///QZYkpTxyDlsWwS7Uf/Dzf28s7Xha7k7mbFI8Ghe5w04GoR3qeVm5ZVurUH660+cfLV8dh0d04vty6abZt4JsJqfO+Z7b9ZADJORGOiyFEzAe52uyAz15Dl3Nr+Wr+AAgQaU9lm1yLEXo2E9QprtiTUXf5b8iNB/rRofQbOQCCXQpIBxo293ZTTUYGScBpe+tI/NqiFvOHhz3o3uOZ1IFg5/Th7+/kEeKzytjkYpOSztB1DfGvlJGJqXtaqJgw4mScCJ1BlVMv2r1sGpMeTGg==
ARC-Authentication-Results: i=1; mx.microsoft.com 1; spf=pass smtp.mailfrom=microsoft.com; dmarc=pass action=none header.from=microsoft.com; dkim=pass header.d=microsoft.com; arc=none
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=microsoft.com; s=selector2; h=From:Date:Subject:Message-ID:Content-Type:MIME-Version:X-MS-Exchange-SenderADCheck; bh=AN3HMd4nNY+Tt8V7WCm+FXgrFDl+0weWdWIiVdKqRJs=; b=cHQnBjdHWpG4oNAn3LPlpoM3czz3sb+c7Hvr7V0QcSwXA5PhlT55D6irQqETBBsnrlWcpXIeA1ttdFLt6DJR7hKo8qDrRMY1JHf3VPo6eQl3tMp5ACADhPrxrCWdGvWEU7nxGYRsULw9EFObJDAlMtBne9A78hZfxXo1G8AOukU=
Received: from CH2PR21MB1381.namprd21.prod.outlook.com (2603:10b6:610:8e::12) by CH2PR21MB1430.namprd21.prod.outlook.com (2603:10b6:610:80::17) with Microsoft SMTP Server (version=TLS1_2, cipher=TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384) id 15.20.3477.11; Thu, 22 Oct 2020 16:58:14 +0000
Received: from CH2PR21MB1381.namprd21.prod.outlook.com ([fe80::dfd:b166:92c:5a84]) by CH2PR21MB1381.namprd21.prod.outlook.com ([fe80::dfd:b166:92c:5a84%9]) with mapi id 15.20.3499.017; Thu, 22 Oct 2020 16:58:14 +0000
From: Jorge Vergara <jovergar@microsoft.com>
To: Joseph Salowey <joe@salowey.net>, Oleg Pekar <oleg.pekar.2017@gmail.com>
CC: EMU WG <emu@ietf.org>, Jouni Malinen <j@w1.fi>
Thread-Topic: Proposed resolution for TEAP errata for 5128
Thread-Index: AQHWp/H/5iLrTwXdRkW9JLXm9c5wSaminKRAgAAZaYCAAADdIIAABDMAgADsEACAACBdAIAACYqAgAAGsICAAABEQA==
Date: Thu, 22 Oct 2020 16:58:13 +0000
Message-ID: <CH2PR21MB13810C16054DD1DDB4055659D11D0@CH2PR21MB1381.namprd21.prod.outlook.com>
References: <CAOgPGoBay+GG=F8WV0gLOOwLtGdGALGw_cM2JoAnXOtmGq7A+w@mail.gmail.com> <CH2PR21MB138143E929DAFE3C893D8144D11C0@CH2PR21MB1381.namprd21.prod.outlook.com> <CAOgPGoAtcm+Br+YkCyTtg5nJjqO7LGSo77b+CD4+Ba05azafew@mail.gmail.com> <CH2PR21MB13815BCEDC846D7C440AD564D11C0@CH2PR21MB1381.namprd21.prod.outlook.com> <CAOgPGoDTC-qiHOXFTJd7aMn2To7ySzBcx+iQMB9m5foC1bFxzw@mail.gmail.com> <CABXxEz8SRvMXdMR8_cPfvWdauJZwCjnd=7ytnVZ+_L-sB48wvw@mail.gmail.com> <CAOgPGoCsWy-uhYeeHCDUaazjAwfWtr_zkS5CUoX8+baASahFEg@mail.gmail.com> <CABXxEz9euWaA9Y66+1u4gtFCWkrPUEd-juY_TFUHPQE4R_OpRg@mail.gmail.com> <CAOgPGoDcD7wjiMt2=t0vx2FPr2LD2S3eU1d0_bVU1c88S=tA=w@mail.gmail.com>
In-Reply-To: <CAOgPGoDcD7wjiMt2=t0vx2FPr2LD2S3eU1d0_bVU1c88S=tA=w@mail.gmail.com>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
msip_labels: MSIP_Label_f42aa342-8706-4288-bd11-ebb85995028c_ActionId=768dca1f-9e0d-4dd1-ae9b-1435c13caf8c; MSIP_Label_f42aa342-8706-4288-bd11-ebb85995028c_ContentBits=0; MSIP_Label_f42aa342-8706-4288-bd11-ebb85995028c_Enabled=true; MSIP_Label_f42aa342-8706-4288-bd11-ebb85995028c_Method=Standard; MSIP_Label_f42aa342-8706-4288-bd11-ebb85995028c_Name=Internal; MSIP_Label_f42aa342-8706-4288-bd11-ebb85995028c_SetDate=2020-10-22T16:54:10Z;  MSIP_Label_f42aa342-8706-4288-bd11-ebb85995028c_SiteId=72f988bf-86f1-41af-91ab-2d7cd011db47;
authentication-results: salowey.net; dkim=none (message not signed) header.d=none;salowey.net; dmarc=none action=none header.from=microsoft.com;
x-originating-ip: [2001:4898:80e8:f:28:eedc:a141:1405]
x-ms-publictraffictype: Email
x-ms-office365-filtering-ht: Tenant
x-ms-office365-filtering-correlation-id: 07415692-a5f3-41fc-df57-08d876abaa3e
x-ms-traffictypediagnostic: CH2PR21MB1430:
x-microsoft-antispam-prvs: <CH2PR21MB14304E1128C6E9B67F26B046D11D0@CH2PR21MB1430.namprd21.prod.outlook.com>
x-ms-oob-tlc-oobclassifiers: OLM:10000;
x-ms-exchange-senderadcheck: 1
x-microsoft-antispam: BCL:0;
x-microsoft-antispam-message-info: /aFxwFDl5/Hx2KeEr3eZZNlIGYGspkO4gCWdgq3sXNuxfke1FWWbGTYvZdETdmU9Ybr6NIZz3DilEUxv1h3e8p9yo7RxYkZahcvlgHN5f7nJREz7HgMHx64mitrG/F4MuLS6lgduVrX2e+P3izaN5CkAkfB9+sWCuoRG+auyEmtCY4HCsOL/jtsIzvghrpYcb33AVRMOgr7TpqgyTOYZn4bFKSOA5Iiv9UbUPvvFe2mYYbFybeui6yzuGiBdNvKAYIwA7wdKaOR9TrDVd46gx4lC+EXsT3PUMf1m9GNbFwfMZplDnfnMB6ejDlUUvqBUxoL509t15d2udqudzuOYi1mJQHEm5E0DEVqIVlmr+wVIMCghZdgBDwEngGEjhvxYWCPl6cMPrig24ZiQy0oi+w==
x-forefront-antispam-report: CIP:255.255.255.255; CTRY:; LANG:en; SCL:1; SRV:;  IPV:NLI; SFV:NSPM; H:CH2PR21MB1381.namprd21.prod.outlook.com; PTR:; CAT:NONE;  SFS:(4636009)(136003)(396003)(376002)(346002)(366004)(39860400002)(4326008)(76116006)(54906003)(8676002)(7696005)(6506007)(71200400001)(316002)(110136005)(82950400001)(8990500004)(478600001)(86362001)(966005)(8936002)(82960400001)(10290500003)(66946007)(64756008)(83380400001)(2906002)(53546011)(186003)(166002)(5660300002)(55016002)(66476007)(66556008)(52536014)(66446008)(9686003)(30864003)(33656002); DIR:OUT; SFP:1102; 
x-ms-exchange-antispam-messagedata: YlfZiZzy3xik0phcgBDltpS8TXGVrHI46XOp+bh4Y4DAGOIGSer7rDb3y3l/y09TXNNvu+8nQxZJRWoCSvn0WiRQKruwON9qvj7uz4CiPI2uHjPKUYF6lXMrBN/70eRPnd+3dLBqMjvBwp14zjcTXqvvUq+y6pJDzuayye/WHMGgaS33TlwGwIhykNV2wLcRxGkdtXySyZpDn8o7HYAzWCNE2+q318byrgpQ3VA3GuM6v5GB+kqAfUexR6x9nx5eVWk+vwbd0AS7gn99WaVVG+5VDm1lCMAw4rwBbjX1IhwNQ+htoa7Boop64+g3sdBrYJ11DNDqreV5YMikBm9O//erhMVGgBRa4ygrWb2XW3QJMIVNtGbIAujdxXIKOSK0UebmZz53R/K0amoWrJDjJo5DBCe5zdGu2+DQbjto//MpheHESBnV/9jbfq1KwFdpRiJgcJTduCZLMeG0UDNCndepID4Q9vFumHzHqv3sAnWlS940G8el71EIhzwZ6ad8NYbjEIz21NB8ykPgE/xg3j3fv9wpCDnjhNUHZM57LgvlbubXctDtbhBtIfnILO8viw1XX1tPT9ELUrnPmHev5fMrFEdxty1/xq90YqTE6aOGuThN/C6SeYjJH+v4Hf8pxQt7TPBJDlwJBA30kk8rNcfoat+/EMt1Uv86t7pnkZZdeimivul77Kvdurvz1cKExVbfHPkJLt4cgR62bLht9g==
x-ms-exchange-transport-forked: True
Content-Type: multipart/alternative; boundary="_000_CH2PR21MB13810C16054DD1DDB4055659D11D0CH2PR21MB1381namp_"
MIME-Version: 1.0
X-OriginatorOrg: microsoft.com
X-MS-Exchange-CrossTenant-AuthAs: Internal
X-MS-Exchange-CrossTenant-AuthSource: CH2PR21MB1381.namprd21.prod.outlook.com
X-MS-Exchange-CrossTenant-Network-Message-Id: 07415692-a5f3-41fc-df57-08d876abaa3e
X-MS-Exchange-CrossTenant-originalarrivaltime: 22 Oct 2020 16:58:13.8984 (UTC)
X-MS-Exchange-CrossTenant-fromentityheader: Hosted
X-MS-Exchange-CrossTenant-id: 72f988bf-86f1-41af-91ab-2d7cd011db47
X-MS-Exchange-CrossTenant-mailboxtype: HOSTED
X-MS-Exchange-CrossTenant-userprincipalname: yK0qfOyrZvqnmQsUSc+6SO8bg8Yy4uJHqxMPIwlc/ENC2okCDnaUBTVYZZjVZatA5O6bdvza27ocoqc/Bw01Kw==
X-MS-Exchange-Transport-CrossTenantHeadersStamped: CH2PR21MB1430
Archived-At: <https://mailarchive.ietf.org/arch/msg/emu/nhPDonvouop-viv-PvcRqDBu_HA>
Subject: Re: [Emu] Proposed resolution for TEAP errata for 5128
X-BeenThere: emu@ietf.org
X-Mailman-Version: 2.1.29
Precedence: list
List-Id: "EAP Methods Update \(EMU\)" <emu.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/emu>, <mailto:emu-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/emu/>
List-Post: <mailto:emu@ietf.org>
List-Help: <mailto:emu-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/emu>, <mailto:emu-request@ietf.org?subject=subscribe>
X-List-Received-Date: Thu, 22 Oct 2020 16:58:30 -0000

--_000_CH2PR21MB13810C16054DD1DDB4055659D11D0CH2PR21MB1381namp_
Content-Type: text/plain; charset="utf-8"
Content-Transfer-Encoding: base64

PltKb2VdIFRoaXMgaXMgdGhlIG9uZSB3ZSBoYXZlIG5vdCBkaXNjdXNzZWQgeWV0LiAgVGhpcyBk
ZXJpdmF0aW9uIGlzIGFsc28gYW1iaWd1b3VzLiAgVEhpcyBzZWN0aW9uIGRvZXMgbm90IHJlZmVy
ZW5jZSA1Mjk1LiAgSXQncyBub3QgY2xlYXIgaWYgdGhlIG9yaWdpbmFsIGludGVudCB3YXMgdG8g
aW5jbHVkZSB0aGUgbGVuZ3RoIGluIHRoZSBoYXNoIG9yIG5vdC4gIEkgdGhpbmsgdGhlcmUgYXJl
IGEgZmV3IGludGVycHJldGF0aW9uczoNCj4NCj4xLiBUTFMtUFJGKFMtSU1DS1tqXSwgIlNlc3Np
b24gS2V5IEdlbmVyYXRpbmcgRnVuY3Rpb24iKSAgaXRlcmF0ZWQgdG8gZ2VuZXJhdGUgNjQgYnl0
ZXMgPSBQX2hhc2goUy1JTUNLW2pdLCAiU2Vzc2lvbiBLZXkgR2VuZXJhdGluZyBGdW5jdGlvbuKA
nSkNCj4yLiBUTFMtUFJGKFMtSU1DS1tqXSwgIlNlc3Npb24gS2V5IEdlbmVyYXRpbmcgRnVuY3Rp
b24iLCA2NCkgIGl0ZXJhdGVkIHRvIGdlbmVyYXRlIDY0IGJ5dGVzID0gUF9oYXNoKFMtSU1DS1tq
XSwgIlNlc3Npb24gS2V5IEdlbmVyYXRpbmcgRnVuY3Rpb27igJ0gfCAweDAwIHwgMHg0MCkNCj4z
LiAoRm9sbG93IDUyOTUgcGFyYW1ldGVycykgVExTLVBSRihTLUlNQ0tbal0sICJTZXNzaW9uIEtl
eSBHZW5lcmF0aW5nIEZ1bmN0aW9uIiwgIlwwIiB8IDY0KSA9IFBfaGFzaChTLUlNQ0tbal0sICJT
ZXNzaW9uIEtleSBHZW5lcmF0aW5nIEZ1bmN0aW9u4oCdIHwgMHgwMCB8IDB4MDAgfCAweDQwKQ0K
Pg0KPkkgdGhpbmsgMSBvciAyIGlzIHdoYXQgd2FzIHByb2JhYmx5IG9yaWdpbmFsbHkgaW50ZW5k
ZWQsIGhvd2V2ZXIgaXQgc2VlbXMgdGhhdCAzIGlzIHdoYXQgaGFzIGJlZW4gaW1wbGVtZW50ZWQu
ICBEbyB3ZSBoYXZlIGFncmVlbWVudCBvbiB0aGlzIGlzIHdoYXQgY3VycmVudCBpbXBsZW1lbnRh
dGlvbnMgZG8/DQoNCk5vLCBNaWNyb3NvZnQgaW1wbGVtZW50cyBudW1iZXIgMSBvZiBKb2XigJlz
IHByZXNlbnRlZCBvcHRpb25zLiBUaGF0IGlzIC0gUF88aGFzaD4oUy1JTUNLW2pdLCAiU2Vzc2lv
biBLZXkgR2VuZXJhdGluZyBGdW5jdGlvbiIpLg0KDQpUaGlzIGZvbGxvd3MgdGhlIHNhbWUgcGF0
dGVybiBhcyB0aGUgZXJyYXRhIHdlIGFyZSBkaXNjdXNzaW9uLiBJIGFtIHZlcnkgc3VycHJpc2Vk
IHRvIGhlYXIgdGhhdCBDaXNjb+KAmXMgaW1wbGVtZW50YXRpb24gbWF5IGJlIGRpZmZlcmVudC4g
T2xlZywgY291bGQgeW91IHBsZWFzZSBkb3VibGUgY2hlY2s/IEkgaGF2ZSBqdXN0IGRvdWJsZSBj
aGVja2VkIG91ciBpbXBsZW1lbnRhdGlvbi4gU2luY2Ugb3VyIGltcGxlbWVudGF0aW9ucyBpbnRl
cm9wLCBJIGFzc3VtZSB3ZSBtdXN0IGhhdmUgdGhlIHNhbWUgaW1wbGVtZW50YXRpb24uDQoNCkpv
cmdlIFZlcmdhcmENCg0KDQpGcm9tOiBKb3NlcGggU2Fsb3dleSA8am9lQHNhbG93ZXkubmV0Pg0K
U2VudDogVGh1cnNkYXksIE9jdG9iZXIgMjIsIDIwMjAgOTo1MyBBTQ0KVG86IE9sZWcgUGVrYXIg
PG9sZWcucGVrYXIuMjAxN0BnbWFpbC5jb20+DQpDYzogRU1VIFdHIDxlbXVAaWV0Zi5vcmc+OyBK
b3JnZSBWZXJnYXJhIDxqb3ZlcmdhckBtaWNyb3NvZnQuY29tPjsgSm91bmkgTWFsaW5lbiA8akB3
MS5maT4NClN1YmplY3Q6IFJlOiBQcm9wb3NlZCByZXNvbHV0aW9uIGZvciBURUFQIGVycmF0YSBm
b3IgNTEyOA0KDQoNCg0KT24gVGh1LCBPY3QgMjIsIDIwMjAgYXQgOToyOSBBTSBPbGVnIFBla2Fy
IDxvbGVnLnBla2FyLjIwMTdAZ21haWwuY29tPG1haWx0bzpvbGVnLnBla2FyLjIwMTdAZ21haWwu
Y29tPj4gd3JvdGU6DQpJIGFncmVlIHRoYXQgY2hhbmdpbmcgdGhlIEtERiBpcyBoYXJtZnVsIHRv
IGV4aXN0aW5nIGltcGxlbWVudGF0aW9ucy4gSG93ZXZlciwgaWYgSSB1bmRlcnN0b29kIGNvcnJl
Y3RseSwgSm9lJ3Mgc3VnZ2VzdGlvbiBmb3IgSU1DS1tqXSBhbHNvIGJyZWFrcyB0aGUgZXhpc3Rp
bmcgaW1wbGVtZW50YXRpb24uIEkgc3RpbGwgc2VlIHRoYXQgd2UgY2FuIGRlZmluZSBhIHVuaWZp
ZWQgS0RGIGJ5IGNoYW5naW5nIHRoZSBBUEkgaW4gdGhlIFJGQyBidXQgd2l0aCB0aGUgc2FtZSBo
YXJtIHRvIHRoZSBleGlzdGluZyBpbXBsZW1lbnRhdGlvbiBpbiBJTUNLW2pdIGFzIGluIGJvdGgg
cHJvcG9zYWxzOg0KDQpURUFQLVBSRiAoc2VjcmV0LCBrZXkgbGFiZWwsIG9wdGlvbmFsIGRhdGEs
IGxlbmd0aCkgPSBUTFMtUFJGKHNlY3JldCwga2V5IGxhYmVsIHwgMHgwMCB8IG9wdGlvbmFsIGRh
dGEsIGxlbmd0aCkNCkpvZSwgdGhhbmtzIGZvciBwb2ludGluZyBvdXQgdGhhdCBSRkMgNTI5NSBk
b2Vzbid0IHNwZWNpZnkgdGhhdCBhIDB4MDAgaXMgdXNlZCB0byByZXByZXNlbnQgbm8gb3B0aW9u
YWwgZGF0YSwgdGhhdCB3YXMganVzdCBteSBtaXN0YWtlLg0KDQpJTVNLOg0KQ3VycmVudCBNaWNy
b3NvZnQgYW5kIENpc2NvIGltcGxlbWVudGF0aW9uOiBQX2hhc2goRU1TSywgIlRFQVBiaW5ka2V5
QGlldGYub3JnPG1haWx0bzpURUFQYmluZGtleUBpZXRmLm9yZz4iIHwgMHgwMCB8IDB4MDAgfCAw
eDQwKQ0KSm9lJ3MgcHJvcG9zYWw6IFBfaGFzaChFTVNLLCAiVEVBUGJpbmRrZXlAaWV0Zi5vcmc8
bWFpbHRvOlRFQVBiaW5ka2V5QGlldGYub3JnPiIgfCAweDAwIHwgMHgwMCB8IDB4NDApLCB0aGUg
c2FtZSwganVzdCB0aGUgQVBJIGNvcnJlY3Rpb24NClVuaWZpZWQgS0RGIHByb3Bvc2FsOiBURUFQ
LVBSRihFTVNLLCAiVEVBUGJpbmRrZXlAaWV0Zi5vcmc8bWFpbHRvOlRFQVBiaW5ka2V5QGlldGYu
b3JnPiIsIDxubyBvcHRpb25hbCBkYXRhPiwgNjQpID0gUF9oYXNoKEVNU0ssICJURUFQYmluZGtl
eUBpZXRmLm9yZzxtYWlsdG86VEVBUGJpbmRrZXlAaWV0Zi5vcmc+IiB8IDB4MDAgfCAweDAwIHwg
MHg0MCkNCi0tLSBubyBpbXBsZW1lbnRhdGlvbiBjaGFuZ2UNCg0KSU1DS1tqXToNCkN1cnJlbnQg
TWljcm9zb2Z0IGFuZCBDaXNjbyBpbXBsZW1lbnRhdGlvbjogUF9oYXNoKFMtSU1DS1tqLTFdLCAi
SW5uZXIgTWV0aG9kcyBDb21wb3VuZCBLZXlz4oCdIHwgSU1TS1tqXSkNCkpvZSdzIHByb3Bvc2Fs
OiBQX2hhc2goUy1JTUNLW2otMV0sICJJbm5lciBNZXRob2RzIENvbXBvdW5kIEtleXMiIHwgSU1T
S1tqXSB8IDB4MDAgfCAweDNDKQ0KVW5pZmllZCBLREYgcHJvcG9zYWw6IFRFQVAtUFJGKFMtSU1D
S1tqLTFdLCAiSW5uZXIgTWV0aG9kcyBDb21wb3VuZCBLZXlzIiwgSU1TS1tqXSwgNjApID0gUF9o
YXNoKFMtSU1DS1tqLTFdLCAiSW5uZXIgTWV0aG9kcyBDb21wb3VuZCBLZXlzIiB8IElNU0tbal0g
fCAweDAwIHwgMHgzQykNCi0tLSBpbXBsZW1lbnRhdGlvbiBjaGFuZ2UNCg0KW0pvZV0gVGhhdCB3
YXMgbXkgaW5pdGlhbCBwcm9wb3NhbCwgYnV0IGJhc2VkIG9uIEpvcmdlJ3MgY29tbWVudCBpdCBp
cyBtb2RpZmllZCB0bzoNCg0KSU1DS1tqXSA9IFRMUy1QUkYoUy1JTUNLW2otMV0sICJJbm5lciBN
ZXRob2RzIENvbXBvdW5kIEtleXMiLCBJTVNLW2pdKSAgdG8gZ2VuZXJhdGUgYSBsZW5ndGggb2Yg
NjAgYnl0ZXMNCklNQ0tbal0gPSBQX2hhc2goUy1JTUNLW2otMV0sICJJbm5lciBNZXRob2RzIENv
bXBvdW5kIEtleXPigJ0gfCBJTVNLW2pdKQ0KDQoNCk1TSzoNCkN1cnJlbnQgTWljcm9zb2Z0IGFu
ZCBDaXNjbyBpbXBsZW1lbnRhdGlvbjogUF9oYXNoKFMtSU1DS1tqXSwgIlNlc3Npb24gS2V5IEdl
bmVyYXRpbmcgRnVuY3Rpb27igJ0gfCAweDAwIHwgMHgwMCB8IDB4NDApDQpVbmlmaWVkIEtERiBw
cm9wb3NhbDogVEVBUC1QUkYoUy1JTUNLW2pdLCAiU2Vzc2lvbiBLZXkgR2VuZXJhdGluZyBGdW5j
dGlvbuKAnSwgPG5vIG9wdGlvbmFsIGRhdGE+LCA2NCkgPSBQX2hhc2goUy1JTUNLW2pdLCAiU2Vz
c2lvbiBLZXkgR2VuZXJhdGluZyBGdW5jdGlvbuKAnSB8IDB4MDAgfCAweDAwIHwgMHg0MCkNCi0t
LSBubyBpbXBsZW1lbnRhdGlvbiBjaGFuZ2UNCg0KW0pvZV0gVGhpcyBpcyB0aGUgb25lIHdlIGhh
dmUgbm90IGRpc2N1c3NlZCB5ZXQuICBUaGlzIGRlcml2YXRpb24gaXMgYWxzbyBhbWJpZ3VvdXMu
ICBUSGlzIHNlY3Rpb24gZG9lcyBub3QgcmVmZXJlbmNlIDUyOTUuICBJdCdzIG5vdCBjbGVhciBp
ZiB0aGUgb3JpZ2luYWwgaW50ZW50IHdhcyB0byBpbmNsdWRlIHRoZSBsZW5ndGggaW4gdGhlIGhh
c2ggb3Igbm90LiAgSSB0aGluayB0aGVyZSBhcmUgYSBmZXcgaW50ZXJwcmV0YXRpb25zOg0KDQox
LiBUTFMtUFJGKFMtSU1DS1tqXSwgIlNlc3Npb24gS2V5IEdlbmVyYXRpbmcgRnVuY3Rpb24iKSAg
aXRlcmF0ZWQgdG8gZ2VuZXJhdGUgNjQgYnl0ZXMgPSBQX2hhc2goUy1JTUNLW2pdLCAiU2Vzc2lv
biBLZXkgR2VuZXJhdGluZyBGdW5jdGlvbuKAnSkNCjIuIFRMUy1QUkYoUy1JTUNLW2pdLCAiU2Vz
c2lvbiBLZXkgR2VuZXJhdGluZyBGdW5jdGlvbiIsIDY0KSAgaXRlcmF0ZWQgdG8gZ2VuZXJhdGUg
NjQgYnl0ZXMgPSBQX2hhc2goUy1JTUNLW2pdLCAiU2Vzc2lvbiBLZXkgR2VuZXJhdGluZyBGdW5j
dGlvbuKAnSB8IDB4MDAgfCAweDQwKQ0KMy4gKEZvbGxvdyA1Mjk1IHBhcmFtZXRlcnMpIFRMUy1Q
UkYoUy1JTUNLW2pdLCAiU2Vzc2lvbiBLZXkgR2VuZXJhdGluZyBGdW5jdGlvbiIsICJcMCIgfCA2
NCkgPSBQX2hhc2goUy1JTUNLW2pdLCAiU2Vzc2lvbiBLZXkgR2VuZXJhdGluZyBGdW5jdGlvbuKA
nSB8IDB4MDAgfCAweDAwIHwgMHg0MCkNCg0KSSB0aGluayAxIG9yIDIgaXMgd2hhdCB3YXMgcHJv
YmFibHkgb3JpZ2luYWxseSBpbnRlbmRlZCwgaG93ZXZlciBpdCBzZWVtcyB0aGF0IDMgaXMgd2hh
dCBoYXMgYmVlbiBpbXBsZW1lbnRlZC4gIERvIHdlIGhhdmUgYWdyZWVtZW50IG9uIHRoaXMgaXMg
d2hhdCBjdXJyZW50IGltcGxlbWVudGF0aW9ucyBkbz8NCg0KDQoNCg0KSm9yZ2UsIHBsZWFzZSBj
b3JyZWN0IG1lIGlmIEkgbWlzaW50ZXJwcmV0IHRoZSBNaWNyb3NvZnQgaW1wbGVtZW50YXRpb24u
DQoNCk9uIFRodSwgT2N0IDIyLCAyMDIwIGF0IDY6NTUgUE0gSm9zZXBoIFNhbG93ZXkgPGpvZUBz
YWxvd2V5Lm5ldDxtYWlsdG86am9lQHNhbG93ZXkubmV0Pj4gd3JvdGU6DQoNCg0KT24gVGh1LCBP
Y3QgMjIsIDIwMjAgYXQgNjo1OSBBTSBPbGVnIFBla2FyIDxvbGVnLnBla2FyLjIwMTdAZ21haWwu
Y29tPG1haWx0bzpvbGVnLnBla2FyLjIwMTdAZ21haWwuY29tPj4gd3JvdGU6DQpIaSBhbGwsDQpT
cGVha2luZyBhYm91dCBib3RoIGVycmF0YSA1MTI3IGFuZCA1MTI4LCBJIHRoaW5rIHdlIG5lZWQg
dG8gYWxpZ24gYWxsIGtleSBkZXJpdmF0aW9uIGNhbGxzIGluIFRFQVAgUkZDIHdpdGggdGhlIHNh
bWUgcnVsZS9mb3JtYXQgdG8gbWFrZSB0aGUgUkZDIGVhc2llciB0byB1bmRlcnN0YW5kLiBUaGlz
IGNhbiBiZSBhY2hpZXZlZCBieSBpbnRyb2R1Y2luZyBhIHVuaWZpZWQgc2luZ2xlIFBSRiBmdW5j
dGlvbiB0aGF0IHdpbGwgYmUgY2FsbGVkIGZyb20gYWxsIHRoZSByZWxldmFudCBSRkMgbG9jYXRp
b25zLiBGb3IgbWUgaXQgc291bmRzIGJldHRlciB0aGFuIGlmIHdlIGFsaWduIGp1c3QgcGFydCBv
ZiBLREYgY2FsbHMgd2l0aCBSRkMgNTI5NSAod2hlcmUgdGhlIG91dHB1dCBsZW5ndGggaXMgaW5j
bHVkZWQgaW50byBzZWVkKS4gQWxzbzogaW4gc29tZSBLREYgY2FsbHMgd2UgZG8gaGF2ZSBvcHRp
b25hbCBkYXRhIGFuZCBpbiBzb21lIG5vLiBUaGlzIGNvdWxkIGJlIGFsc28gdW5pZmllZC4NCg0K
W0pvZV0gSSBkb24ndCB0aGluayB0aGlzIHdhcyB0aGUgb3JpZ2luYWwgaW50ZW50IG9mIHRoZSBk
b2N1bWVudC4gIFRoZSBJTVNLIGRlcml2YXRpb24gcmVmZXJlbmNlZCA1Mjk1IHdoaWxlIHRoZSBv
dGhlcnMganVzdCByZWZlcmVuY2UgdGhlIFRMUyBQUkYuICBJIHRoaW5rIHRvIHVuaWZ5IHRoZW0g
d291bGQgcmVxdWlyZSBhIGRvY3VtZW50IHVwZGF0ZSBhbmQgSSdtIG5vdCBzdXJlIHdoYXQgd2Ug
d291bGQgZ2FpbiBlc3BlY2lhbGx5IGlmIHdlIGhhdmUgaW1wbGVtZW50YXRpb25zIHRoYXQgZG8g
dGhpcy4NCg0KU28gSSB3b3VsZCBzdWdnZXN0IGludHJvZHVjaW5nOg0KVEVBUC1QUkYgKHNlY3Jl
dCwga2V5IGxhYmVsLCBvcHRpb25hbCBkYXRhLCBsZW5ndGgpID0gVExTLVBSRihzZWNyZXQsIGtl
eSBsYWJlbCB8IDB4MDAgfCBvcHRpb25hbCBkYXRhLCBsZW5ndGgpDQp3aGVyZSBhIHNpbmdsZSBi
eXRlIDB4MDAgaXMgdXNlZCBmb3Igbm8gb3B0aW9uYWwgZGF0YSwgbGVuZ3RoIGlzIGEgMi1vY3Rl
dCB1bnNpZ25lZCBpbnRlZ2VyIGluIG5ldHdvcmsgYnl0ZSBvcmRlci4NCg0KW0pvZV0gSSBkb24n
dCB0aGluayB0aGF0IDUyOTUgc3BlY2lmaWVzIHRoYXQgYSAweDAwIGlzIHVzZWQgdG8gcmVwcmVz
ZW50IG5vIG9wdGlvbmFsIGRhdGEuICBEaWQgeW91IHNlZSB0aGlzIGluIHRoZSBzcGVjPyBJdCBt
YXkgYmUgYW1iaWd1b3VzLCBidXQgSSB0aGluayB0aGUgaW50ZW50IGlzIHRoYXQgb3B0aW9uYWwg
ZGF0YSBpcyBqdXN0IG9taXR0ZWQgaWYgaXQgaXMgbm90IHByb3ZpZGVkLg0KDQoNClRoZW46DQpJ
TVNLID0gRmlyc3QgMzIgb2N0ZXRzIG9mIFRFQVAtUFJGKEVNU0ssICJURUFQYmluZGtleUBpZXRm
Lm9yZzxtYWlsdG86VEVBUGJpbmRrZXlAaWV0Zi5vcmc+IiwgNjQpID0gVExTLVBSRihFTVNLLCAi
VEVBUGJpbmRrZXlAaWV0Zi5vcmc8bWFpbHRvOlRFQVBiaW5ka2V5QGlldGYub3JnPiIgfCAweDAw
IHwgMHgwMCB8IDB4MDAgfCAweDQwKQ0KSU1DS1tqXSA9IFRFQVAtUFJGKFMtSU1DS1tqLTFdLCAi
SW5uZXIgTWV0aG9kcyBDb21wb3VuZCBLZXlzIiwgSU1TS1tqXSwgNjApID0gVExTLVBSRihTLUlN
Q0tbai0xXSwgIklubmVyIE1ldGhvZHMgQ29tcG91bmQgS2V5cyIgfCAweDAwIHwgSU1TS1tqXSB8
IDB4MDAgfCAweDNDKQ0KTVNLID0gVEVBUC1QUkYoUy1JTUNLW2pdLCAiU2Vzc2lvbiBLZXkgR2Vu
ZXJhdGluZyBGdW5jdGlvbuKAnSwgNjQpID0gVExTLVBSRihTLUlNQ0tbal0sICJTZXNzaW9uIEtl
eSBHZW5lcmF0aW5nIEZ1bmN0aW9uIiB8IDB4MDAgfCAweDAwIHwgMHgwMCB8IDB4NDApDQpFTVNL
ID0gVEVBUC1QUkYoUy1JTUNLW2pdLCDigJ1FeHRlbmRlZCBTZXNzaW9uIEtleSBHZW5lcmF0aW5n
IEZ1bmN0aW9u4oCdLCA2NCkgPSBUTFMtUFJGKFMtSU1DS1tqXSwgIkV4dGVuZGVkIFNlc3Npb24g
S2V5IEdlbmVyYXRpbmcgRnVuY3Rpb24iIHwgMHgwMCB8IDB4MDAgfCAweDAwIHwgMHg0MCkNCg0K
VGhpcyBtYXkgY2hhbmdlIHRoZSBleGlzdGluZyBpbXBsZW1lbnRhdGlvbiBidXQgd2lsbCBtYWtl
IGl0IG1vcmUgY2xlYXIgLSBuZWVkIHRvIGNyZWF0ZSBhbmQgY2FsbCBqdXN0IG9uZSBLREYgZnVu
Y3Rpb24uDQoNCldlIGNhbiByZW1vdmUgMHgwMCB0aGF0IGNvbWVzIGFmdGVyIHRoZSBrZXkgbGFi
ZWwgLSB3aGlsZSBpdCBpcyByZXF1aXJlZCBieSBSRkMgNTI5NS4gQnV0IHRoZXJlIHRoZSBrZXkg
bGFiZWwgaXMgYWxzbyBBU0NJSSBwcmludGFibGUgc3RyaW5nLiBKb2UsIGRvIHlvdSByZW1lbWJl
ciB3aGF0IHdhcyB0aGUgbW90aXZhdGlvbiB0byBwdXQgMHgwMCBhZnRlciB0aGUga2V5IGxhYmVs
IHBhcmFtZXRlcj8NCg0KW0pvZV0gdGhlIG51bGwgYWZ0ZXIgdGhlIGtleSBsYWJlbCBpcyB0byBw
cm92aWRlIGEgZGVsaW1pdGVyIGJldHdlZW4gdGhlIGtleSBsYWJlbCBhbmQgb3B0aW9uYWwgZGF0
YS4gIFNpbmNlIHRoZSBvcHRpb25hbCBkYXRhIGNhbiBiZSBhcmJpdHJhcnkgY29udGVudCB0aGUg
bnVsbCBwcmV2ZW50cyB0d28gZGlmZmVyZW50IGxhYmxlbHMgd2l0aCBzcGVjaWFsbHkgY3JhZnRl
ZCBvcHRpb25hbCBkYXRhIGZyb20gZGVyaXZpbmcgdGhlIHNhbWUga2V5Lg0KDQoNCk9sZWcNCg0K
DQpPbiBUaHUsIE9jdCAyMiwgMjAyMCBhdCAyOjU0IEFNIEpvc2VwaCBTYWxvd2V5IDxqb2VAc2Fs
b3dleS5uZXQ8bWFpbHRvOmpvZUBzYWxvd2V5Lm5ldD4+IHdyb3RlOg0KKEkgYWNjaWRlbnRhbGx5
IGRyb3BwZWQgdGhpcyBsaXN0IGZyb20gdGhlIGNvbnZlcnNhdGlvbikNCg0KT24gV2VkLCBPY3Qg
MjEsIDIwMjAgYXQgNDo0OCBQTSBKb3JnZSBWZXJnYXJhIDxqb3ZlcmdhckBtaWNyb3NvZnQuY29t
PG1haWx0bzpqb3ZlcmdhckBtaWNyb3NvZnQuY29tPj4gd3JvdGU6DQo+W0pvZV0gWWVzIHRoaXMg
aXMgYSBjb25jZXJuIGFuZCBJIHRoaW5rIHlvdXIgaW50ZXJwcmV0YXRpb24gb2YgdGhlIGN1cnJl
bnQgZG9jdW1lbnQgaXMgYWxzbyB2YWxpZC4gIFRoZXJlIG1heSBiZSBtb3JlIHRoYW4gb25lIGlt
cGxlbWVudGF0aW9uLiAgU28gd2hhdCB5b3UgaW1wbGVtZW50ZWQgd2FzOg0KPg0KPklNQ0tbal0g
PSBUTFMtUFJGKFMtSU1DS1tqLTFdLCAiSW5uZXIgTWV0aG9kcyBDb21wb3VuZCBLZXlzIiwgSU1T
S1tqXSkgPSBQXzxoYXNoPihTLUlNQ0tbai0xXSwgIklubmVyIE1ldGhvZHMgQ29tcG91bmQgS2V5
cyIgfCBJTVNLW2pdKQ0KDQpZZXMsIHRoaXMgaXMgd2hhdCBJIGltcGxlbWVudGVkLiBBcyB5b3Ug
bWVudGlvbmVkLCB0aGVyZSBhcmUgbXVsdGlwbGUgcG9zc2libGUgaW50ZXJwcmV0YXRpb25zIG9m
IHRoaXMgc2luY2UgdGhlIFRFQVAgdXNhZ2UgaXMgaW5jb3JyZWN0LiBIb3dldmVyLCBteSBpbXBs
ZW1lbnRhdGlvbiBkb2VzIGludGVyb3Agd2l0aCBhdCBsZWFzdCAyIGxhcmdlIHZlbmRvciBpbXBs
ZW1lbnRhdGlvbnMuIElmIHRoZSBpbXBsZW1lbnRhdGlvbnMgd2VyZSB1c2luZyBkaWZmZXJlbnQg
Y2FsY3VsYXRpb25zIGhlcmUsIHRoZSBXaS1GaS9FdGhlcm5ldCBjb25uZWN0aW9ucyB0aGF0IGRl
cGVuZCBvbiB0aGUgTVNLIHdvdWxkIGZhaWwuIEJ1dCBzaW5jZSBjb25uZWN0aW9ucyB3b3JrLCBJ
IGNhbiBhc3N1bWUgd2UgYXJlIGFsbCB1c2luZyB0aGUgc2FtZSBpbXBsZW1lbnRhdGlvbiBhbmQg
YXJyaXZpbmcgYXQgdGhlIHNhbWUgTVNLLiBDaXNjbyBpcyBvbmUgb2YgdGhlIGltcGxlbWVudGF0
aW9ucyB0aGF0IEkgaGF2ZSB0ZXN0ZWQgYWdhaW5zdCB3aGljaCBpcyB3aHkgSSB3YXMgaG9waW5n
IE9sZWcgbWF5IG9mZmVyIG1vcmUgY29udGV4dCBhcyB0byB3aGF0IGhlIGhhcyBzZWVuLg0KDQpb
Sm9lXSBJIGNhbiBob3BlIEpvdW5pIGNhbiBjaGltZSBpbiBvbiB0aGlzIGFzIHdlbGwuICBJIHRo
aW5rIHRoZSBvcmlnaW5hbCBpbnRlbnQgd2FzIHRvIG5vdCBpbmNsdWRlIHRoZSBsZW5ndGggYXMg
aXMgeW91ciBzdWdnZXN0aW9uLg0KDQoNCj5bSm9lXSBEb2VzIHRoZSByZXZpc2lvbiBpbiA1MTY3
IG1hdGNoIHlvdSBpbXBsZW1lbnRhdGlvbiAoIEkgZG9uJ3QgdGhpbmsgSm91bmkncyBjb21tZW50
IGNoYW5nZXMgdGhlIHVuZGVybHkgY2FsY3VsYXRpb24sIGp1c3QgaXRzIHJlcHJlc2VudGF0aW9u
KT8NCg0KSSBoYXZlIG5vdCBpbXBsZW1lbnRlZCB0aGlzIHBvcnRpb24gb2YgdGhlIFJGQyBhcyBJ
IGZvdW5kIGl0IHRvbyB1bmNsZWFyIHRvIHdvcmsgd2l0aC4gVGh1cyBJIGNhbuKAmXQgY29tbWVu
dCBvbiB3aGF0IGltcGxlbWVudGF0aW9ucyBtYXkgYmUgZG9pbmcuIEhvd2V2ZXIsIEkgYWdyZWUg
d2l0aCB0aGUgY3VycmVudCByZXZpc2lvbiBpbiA1MTY3IGFzIHRoZSBtb3N0IG5hdHVyYWwgaW50
ZXJwcmV0YXRpb24uIElmIG90aGVycyBoYXZlIGltcGxlbWVudGVkIHRoaXMgcG9ydGlvbiBvZiB0
aGUgUkZDIHRoZW4gY2VydGFpbmx5IHRoZWlyIGNvbW1lbnRzIHdvdWxkIGJlIHdlbGNvbWUuDQoN
CkJ5IHRoZSB3YXksIHdl4oCZdmUgZHJvcHBlZCB0aGUgRU1VIGdyb3VwIG9uIG91ciByZXBsaWVz
IGhlcmUg4oCTIG5vdCBzdXJlIGlmIGludGVudGlvbmFsIG9yIG5vdC4NCg0KSm9yZ2UgVmVyZ2Fy
YQ0KDQpGcm9tOiBKb3NlcGggU2Fsb3dleSA8am9lQHNhbG93ZXkubmV0PG1haWx0bzpqb2VAc2Fs
b3dleS5uZXQ+Pg0KU2VudDogV2VkbmVzZGF5LCBPY3RvYmVyIDIxLCAyMDIwIDQ6MzYgUE0NClRv
OiBKb3JnZSBWZXJnYXJhIDxqb3ZlcmdhckBtaWNyb3NvZnQuY29tPG1haWx0bzpqb3ZlcmdhckBt
aWNyb3NvZnQuY29tPj4NClN1YmplY3Q6IFJlOiBQcm9wb3NlZCByZXNvbHV0aW9uIGZvciBURUFQ
IGVycmF0YSBmb3IgNTEyOA0KDQoNCg0KT24gV2VkLCBPY3QgMjEsIDIwMjAgYXQgMzoyMCBQTSBK
b3JnZSBWZXJnYXJhIDxqb3ZlcmdhckBtaWNyb3NvZnQuY29tPG1haWx0bzpqb3ZlcmdhckBtaWNy
b3NvZnQuY29tPj4gd3JvdGU6DQpJbiB0aGVvcnkgSSBhZ3JlZSB0aGlzIGlzIGEgcG9zc2libGUg
cmVzb2x1dGlvbi4gSG93ZXZlciwgdGhpcyBkb2VzbuKAmXQgbWF0Y2ggYW55IG9mIHRoZSBjdXJy
ZW50IFRFQVAgaW1wbGVtZW50YXRpb25zIHRoYXQgSSBhbSBhd2FyZSBvZi4gUGVyaGFwcyBPbGVn
IGNhbiB3ZWlnaCBpbiBhcyB3ZWxsIGluIHRlcm1zIG9mIHdoYXQgaGXigJlzIHNlZW4uDQoNCkkg
YmVsaWV2ZSBhbGwgY3VycmVudCBpbXBsZW1lbnRhdGlvbnMgdHJlYXQgNjAgYXMgdGhlIGRlc2ly
ZWQgb3V0cHV0IGxlbmd0aCB3aXRob3V0IHRyZWF0aW5nIGFzIGEgc2VlZC4gSW4gdGVybXMgb2Yg
UF88aGFzaD4sIHRoaXMgbWVhbnMgaW1wbGVtZW50YXRpb25zIGFyZSBwZXJmb3JtaW5nIHRoZSBj
YWxjdWxhdGlvbiB3aXRob3V0IGEgc2VlZC4NCg0KUkZDIDUyNDYgZGVmaW5lcyB0aGUgVExTIDEu
MiBQUkYgYXM6DQpQUkYoc2VjcmV0LCBsYWJlbCwgc2VlZCkgPSBQXzxoYXNoPihzZWNyZXQsIGxh
YmVsICsgc2VlZCkNCg0KU28gdGhlIGNhbGN1bGF0aW9uIGltcGxlbWVudGF0aW9ucyBhcmUgY3Vy
cmVudGx5IHBlcmZvcm1pbmcgd2l0aCBhbiBlbXB0eSBzZWVkIGVuZHMgdXAgYXM6DQpQXzxoYXNo
PihzZWNyZXQsIGxhYmVsKQ0KDQpOb3RlIHRoYXQgaW4gUkZDIDUyOTUsIHRoZSBsZW5ndGggKmlz
KiBleHBsaWNpdGx5IG1lbnRpb25lZCBhcyBiZWluZyBjb25jYXRlbmF0ZWQgd2l0aCB0aGUgbGFi
ZWwNClVTUksgPSBLREYoRU1TSywga2V5IGxhYmVsIHwgIlwwIiB8IG9wdGlvbmFsIGRhdGEgfCBs
ZW5ndGgpDQoNClJGQyA1Mjk1IGlzIG1lbnRpb25lZCBlYXJsaWVyIGluIHRoZSBURUFQIFJGQywg
aW4gdGhlIHNlY3Rpb24gY292ZXJlZCBieSBlcnJhdGEgNTEyNy4gKkhvd2V2ZXIqIGl0IGlzIG5v
dCBtZW50aW9uZWQgaW4gdGhpcyBwb3J0aW9uIG9mIHRoZSBSRkMuIFNpbmNlIHRoaXMgY2FsY3Vs
YXRpb24gaXMgbm90IG9uIGFuIEVNU0ssIEkgZG8gbm90IGJlbGlldmUgUkZDIDIzOTUgYXBwbGll
cyBhbmQgdGhpcyBpcyBsaWtlbHkgd2h5IGltcGxlbWVudGF0aW9ucyB3ZW50IHdpdGggdGhlIHNl
ZWRsZXNzIFBfPGhhc2g+KHNlY3JldCwgbGFiZWwpIGNhbGN1bGF0aW9uIGluc3RlYWQuDQoNCklz
IHRoZXJlIGNvbmNlcm4gYWJvdXQgdXBkYXRpbmcgdGhlIFJGQyBpbiBhIHdheSB0aGF0IGJyZWFr
cyBleGlzdGluZyBpbXBsZW1lbnRhdGlvbnM/DQoNCltKb2VdIFllcyB0aGlzIGlzIGEgY29uY2Vy
biBhbmQgSSB0aGluayB5b3VyIGludGVycHJldGF0aW9uIG9mIHRoZSBjdXJyZW50IGRvY3VtZW50
IGlzIGFsc28gdmFsaWQuICBUaGVyZSBtYXkgYmUgbW9yZSB0aGFuIG9uZSBpbXBsZW1lbnRhdGlv
bi4gIFNvIHdoYXQgeW91IGltcGxlbWVudGVkIHdhczoNCg0KSU1DS1tqXSA9IFRMUy1QUkYoUy1J
TUNLW2otMV0sICJJbm5lciBNZXRob2RzIENvbXBvdW5kIEtleXMiLCBJTVNLW2pdKSA9IFBfPGhh
c2g+KFMtSU1DS1tqLTFdLCAiSW5uZXIgTWV0aG9kcyBDb21wb3VuZCBLZXlzIiB8IElNU0tbal0p
DQoNCnRha2VuIG91dCB0byA2MCBieXRlcy4gIFRoZSBwcm9ibGVtIGlzIHRoYXQgdGhlIFRFQVAg
c3BlYyByZWZlcmVuY2VzIGEgVExTLVBSRiBpbiBhIHdheSB0aGF0IGl0IGRvZXMgbm90IGRlZmlu
ZS4gIEkgdGhpbmsgdGhlIGVycmF0YSBwb2ludHMgb3V0IHRoZSBkZWZpbml0aW9uIHRoYXQgc2hv
dWxkIGJlIHVzZWQ6DQoNClBSRihzZWNyZXQsIGxhYmVsLCBzZWVkKSA9IFBfPGhhc2g+KHNlY3Jl
dCwgbGFiZWwgKyBzZWVkKQ0KDQpUaGF0IGRvZXMgbm90IGluY2x1ZGUgbGVuZ3RoIHNvIHRoZSA2
MCBpbiB0aGUgb3JpZ2luYWwgZGVmaW5pdGlvbiBpcyBhbWJpZ3VvdXMuICAgVGhlIG5ldyB0ZXh0
IHdvdWxkIHRoZW4gYmUgc29tZXRoaW5nIGxpa2U6DQoNCklNQ0tbal0gPSBUTFMtUFJGKFMtSU1D
S1tqLTFdLCAiSW5uZXIgTWV0aG9kcyBDb21wb3VuZCBLZXlzIiwgSU1TS1tqXSkgIHRvIGdlbmVy
YXRlIGEgbGVuZ3RoIG9mIDYwIGJ5dGVzDQoNCkRvZXMgdGhlIHJldmlzaW9uIGluIDUxNjcgbWF0
Y2ggeW91IGltcGxlbWVudGF0aW9uICggSSBkb24ndCB0aGluayBKb3VuaSdzIGNvbW1lbnQgY2hh
bmdlcyB0aGUgdW5kZXJseSBjYWxjdWxhdGlvbiwganVzdCBpdHMgcmVwcmVzZW50YXRpb24pPw0K
DQoNCg0KDQoNCkpvcmdlIFZlcmdhcmENCg0KRnJvbTogSm9zZXBoIFNhbG93ZXkgPGpvZUBzYWxv
d2V5Lm5ldDxtYWlsdG86am9lQHNhbG93ZXkubmV0Pj4NClNlbnQ6IFdlZG5lc2RheSwgT2N0b2Jl
ciAyMSwgMjAyMCAyOjM0IFBNDQpUbzogRU1VIFdHIDxlbXVAaWV0Zi5vcmc8bWFpbHRvOmVtdUBp
ZXRmLm9yZz4+OyBKb3VuaSBNYWxpbmVuIDxqQHcxLmZpPG1haWx0bzpqQHcxLmZpPj47IEpvcmdl
IFZlcmdhcmEgPGpvdmVyZ2FyQG1pY3Jvc29mdC5jb208bWFpbHRvOmpvdmVyZ2FyQG1pY3Jvc29m
dC5jb20+PjsgT2xlZyBQZWthciAob2xwZWthcikgPG9scGVrYXJAY2lzY28uY29tPG1haWx0bzpv
bHBla2FyQGNpc2NvLmNvbT4+DQpTdWJqZWN0OiBQcm9wb3NlZCByZXNvbHV0aW9uIGZvciBURUFQ
IGVycmF0YSBmb3IgNTEyOA0KDQpFcnJhdGEgNTEyODogaHR0cHM6Ly93d3cucmZjLWVkaXRvci5v
cmcvZXJyYXRhL2VpZDUxMjg8aHR0cHM6Ly9uYW0wNi5zYWZlbGlua3MucHJvdGVjdGlvbi5vdXRs
b29rLmNvbS8/dXJsPWh0dHBzJTNBJTJGJTJGd3d3LnJmYy1lZGl0b3Iub3JnJTJGZXJyYXRhJTJG
ZWlkNTEyOCZkYXRhPTA0JTdDMDElN0Nqb3ZlcmdhciU0MG1pY3Jvc29mdC5jb20lN0MxNjA3ZjVm
MDVhYjY0YzExMjI4MTA4ZDg3NmFiMDMwNCU3QzcyZjk4OGJmODZmMTQxYWY5MWFiMmQ3Y2QwMTFk
YjQ3JTdDMSU3QzAlN0M2MzczODk4MjQxNTA3OTI1MzclN0NVbmtub3duJTdDVFdGcGJHWnNiM2Q4
ZXlKV0lqb2lNQzR3TGpBd01EQWlMQ0pRSWpvaVYybHVNeklpTENKQlRpSTZJazFoYVd3aUxDSlhW
Q0k2TW4wJTNEJTdDMTAwMCZzZGF0YT0lMkZZNzdnZDUlMkJablJQSFQlMkJrcTJLa1RKUGxrSzJo
SXUlMkZmRmVqSGxqOWU3Q1ElM0QmcmVzZXJ2ZWQ9MD4NClByb3Bvc2VkIFN0YXRlOiBWZXJpZmll
ZA0KUmV2aXNpb246DQoNClNlY3Rpb24gNS4yLiBzYXlzDQoNCklNQ0tbal0gPSBUTFMtUFJGKFMt
SU1DS1tqLTFdLCAiSW5uZXIgTWV0aG9kcyBDb21wb3VuZCBLZXlzIiwNCiAgICAgICAgICAgICAg
ICBJTVNLW2pdLCA2MCkNCg0KSXQgc2hvdWxkIHNheToNCg0KSU1DS1tqXSA9IFRMUy1QUkYoUy1J
TUNLW2otMV0sICJJbm5lciBNZXRob2RzIENvbXBvdW5kIEtleXMiLCBJTVNLW2pdIHwgNjApDQoN
Ck5vdGU6DQpBY2NvcmRpbmcgdG8NCg0KUkZDNTI0NiBUaGUgVHJhbnNwb3J0IExheWVyIFNlY3Vy
aXR5IChUTFMpIFByb3RvY29sIFZlcnNpb24gMS4yDQoNCjUuIEhNQUMgYW5kIHRoZSBQc2V1ZG9y
YW5kb20gRnVuY3Rpb24NCg0KIlRMUydzIFBSRiBpcyBjcmVhdGVkIGJ5IGFwcGx5aW5nIFBfaGFz
aCB0byB0aGUgc2VjcmV0IGFzOg0KDQpQUkYoc2VjcmV0LCBsYWJlbCwgc2VlZCkgPSBQXzxoYXNo
PihzZWNyZXQsIGxhYmVsICsgc2VlZCkiDQoNCkluIHRlcm1zIG9mIFBfPGhhc2g+IHRoaXMgd291
bGQgbG9vayBsaWtlIHRoZSBmb2xsb3dpbmcgd2l0aCB0aGUgbGVuZ3RoIHJlcHJlc2VudGVkIGFz
IGEgMiBieXRlIHZhbHVlIGluIG5ldHdvcmsgYnl0ZSBvcmRlcjoNCg0KSU1DS1tqXSA9IFBfPGhh
c2g+KFMtSU1DS1tqLTFdLCAiSW5uZXIgTWV0aG9kcyBDb21wb3VuZCBLZXlzIiB8IElNU0tbal0g
fCAweDAwIHwgMHgzQykNCg0KDQo=

--_000_CH2PR21MB13810C16054DD1DDB4055659D11D0CH2PR21MB1381namp_
Content-Type: text/html; charset="utf-8"
Content-Transfer-Encoding: base64

PGh0bWwgeG1sbnM6dj0idXJuOnNjaGVtYXMtbWljcm9zb2Z0LWNvbTp2bWwiIHhtbG5zOm89InVy
bjpzY2hlbWFzLW1pY3Jvc29mdC1jb206b2ZmaWNlOm9mZmljZSIgeG1sbnM6dz0idXJuOnNjaGVt
YXMtbWljcm9zb2Z0LWNvbTpvZmZpY2U6d29yZCIgeG1sbnM6bT0iaHR0cDovL3NjaGVtYXMubWlj
cm9zb2Z0LmNvbS9vZmZpY2UvMjAwNC8xMi9vbW1sIiB4bWxucz0iaHR0cDovL3d3dy53My5vcmcv
VFIvUkVDLWh0bWw0MCI+DQo8aGVhZD4NCjxtZXRhIGh0dHAtZXF1aXY9IkNvbnRlbnQtVHlwZSIg
Y29udGVudD0idGV4dC9odG1sOyBjaGFyc2V0PXV0Zi04Ij4NCjxtZXRhIG5hbWU9IkdlbmVyYXRv
ciIgY29udGVudD0iTWljcm9zb2Z0IFdvcmQgMTUgKGZpbHRlcmVkIG1lZGl1bSkiPg0KPHN0eWxl
PjwhLS0NCi8qIEZvbnQgRGVmaW5pdGlvbnMgKi8NCkBmb250LWZhY2UNCgl7Zm9udC1mYW1pbHk6
IkNhbWJyaWEgTWF0aCI7DQoJcGFub3NlLTE6MiA0IDUgMyA1IDQgNiAzIDIgNDt9DQpAZm9udC1m
YWNlDQoJe2ZvbnQtZmFtaWx5OkNhbGlicmk7DQoJcGFub3NlLTE6MiAxNSA1IDIgMiAyIDQgMyAy
IDQ7fQ0KQGZvbnQtZmFjZQ0KCXtmb250LWZhbWlseTpDb25zb2xhczsNCglwYW5vc2UtMToyIDEx
IDYgOSAyIDIgNCAzIDIgNDt9DQovKiBTdHlsZSBEZWZpbml0aW9ucyAqLw0KcC5Nc29Ob3JtYWws
IGxpLk1zb05vcm1hbCwgZGl2Lk1zb05vcm1hbA0KCXttYXJnaW46MGluOw0KCWZvbnQtc2l6ZTox
MS4wcHQ7DQoJZm9udC1mYW1pbHk6IkNhbGlicmkiLHNhbnMtc2VyaWY7fQ0KYTpsaW5rLCBzcGFu
Lk1zb0h5cGVybGluaw0KCXttc28tc3R5bGUtcHJpb3JpdHk6OTk7DQoJY29sb3I6Ymx1ZTsNCgl0
ZXh0LWRlY29yYXRpb246dW5kZXJsaW5lO30NCnByZQ0KCXttc28tc3R5bGUtcHJpb3JpdHk6OTk7
DQoJbXNvLXN0eWxlLWxpbms6IkhUTUwgUHJlZm9ybWF0dGVkIENoYXIiOw0KCW1hcmdpbjowaW47
DQoJZm9udC1zaXplOjEwLjBwdDsNCglmb250LWZhbWlseToiQ291cmllciBOZXciO30NCnNwYW4u
SFRNTFByZWZvcm1hdHRlZENoYXINCgl7bXNvLXN0eWxlLW5hbWU6IkhUTUwgUHJlZm9ybWF0dGVk
IENoYXIiOw0KCW1zby1zdHlsZS1wcmlvcml0eTo5OTsNCgltc28tc3R5bGUtbGluazoiSFRNTCBQ
cmVmb3JtYXR0ZWQiOw0KCWZvbnQtZmFtaWx5OkNvbnNvbGFzO30NCnNwYW4uRW1haWxTdHlsZTIx
DQoJe21zby1zdHlsZS10eXBlOnBlcnNvbmFsLXJlcGx5Ow0KCWZvbnQtZmFtaWx5OiJDYWxpYnJp
IixzYW5zLXNlcmlmOw0KCWNvbG9yOndpbmRvd3RleHQ7fQ0KLk1zb0NocERlZmF1bHQNCgl7bXNv
LXN0eWxlLXR5cGU6ZXhwb3J0LW9ubHk7DQoJZm9udC1mYW1pbHk6IkNhbGlicmkiLHNhbnMtc2Vy
aWY7fQ0KQHBhZ2UgV29yZFNlY3Rpb24xDQoJe3NpemU6OC41aW4gMTEuMGluOw0KCW1hcmdpbjox
LjBpbiAxLjBpbiAxLjBpbiAxLjBpbjt9DQpkaXYuV29yZFNlY3Rpb24xDQoJe3BhZ2U6V29yZFNl
Y3Rpb24xO30NCi0tPjwvc3R5bGU+PCEtLVtpZiBndGUgbXNvIDldPjx4bWw+DQo8bzpzaGFwZWRl
ZmF1bHRzIHY6ZXh0PSJlZGl0IiBzcGlkbWF4PSIxMDI2IiAvPg0KPC94bWw+PCFbZW5kaWZdLS0+
PCEtLVtpZiBndGUgbXNvIDldPjx4bWw+DQo8bzpzaGFwZWxheW91dCB2OmV4dD0iZWRpdCI+DQo8
bzppZG1hcCB2OmV4dD0iZWRpdCIgZGF0YT0iMSIgLz4NCjwvbzpzaGFwZWxheW91dD48L3htbD48
IVtlbmRpZl0tLT4NCjwvaGVhZD4NCjxib2R5IGxhbmc9IkVOLVVTIiBsaW5rPSJibHVlIiB2bGlu
az0icHVycGxlIiBzdHlsZT0id29yZC13cmFwOmJyZWFrLXdvcmQiPg0KPGRpdiBjbGFzcz0iV29y
ZFNlY3Rpb24xIj4NCjxwIGNsYXNzPSJNc29Ob3JtYWwiPiZndDtbSm9lXSBUaGlzIGlzIHRoZSBv
bmUgd2UgaGF2ZSBub3QgZGlzY3Vzc2VkIHlldC4mbmJzcDsgVGhpcyBkZXJpdmF0aW9uIGlzIGFs
c28gYW1iaWd1b3VzLiZuYnNwOyBUSGlzIHNlY3Rpb24gZG9lcyBub3QgcmVmZXJlbmNlIDUyOTUu
Jm5ic3A7IEl0J3Mgbm90IGNsZWFyIGlmIHRoZSBvcmlnaW5hbCBpbnRlbnQgd2FzIHRvIGluY2x1
ZGUgdGhlIGxlbmd0aCBpbiB0aGUgaGFzaCBvciBub3QuJm5ic3A7IEkgdGhpbmsgdGhlcmUgYXJl
IGEgZmV3IGludGVycHJldGF0aW9uczo8bzpwPjwvbzpwPjwvcD4NCjxwIGNsYXNzPSJNc29Ob3Jt
YWwiPiZndDs8bzpwPiZuYnNwOzwvbzpwPjwvcD4NCjxwIGNsYXNzPSJNc29Ob3JtYWwiPjxzcGFu
IHN0eWxlPSJmb250LXNpemU6MTAuMHB0O2NvbG9yOmJsYWNrIj4mZ3Q7MS4gVExTLVBSRihTLUlN
Q0tbal0sICZxdW90O1Nlc3Npb24gS2V5IEdlbmVyYXRpbmcgRnVuY3Rpb24mcXVvdDspPC9zcGFu
PiZuYnNwOyBpdGVyYXRlZCB0byBnZW5lcmF0ZSA2NCBieXRlcyA9Jm5ic3A7UF9oYXNoKFMtSU1D
S1tqXSwgJnF1b3Q7U2Vzc2lvbiBLZXkgR2VuZXJhdGluZyBGdW5jdGlvbuKAnSk8bzpwPjwvbzpw
PjwvcD4NCjxwIGNsYXNzPSJNc29Ob3JtYWwiPjxzcGFuIHN0eWxlPSJmb250LXNpemU6MTAuMHB0
O2NvbG9yOmJsYWNrIj4mZ3Q7Mi4gVExTLVBSRihTLUlNQ0tbal0sICZxdW90O1Nlc3Npb24gS2V5
IEdlbmVyYXRpbmcgRnVuY3Rpb24mcXVvdDssIDY0KTwvc3Bhbj4mbmJzcDsgaXRlcmF0ZWQgdG8g
Z2VuZXJhdGUgNjQgYnl0ZXMgPSZuYnNwO1BfaGFzaChTLUlNQ0tbal0sICZxdW90O1Nlc3Npb24g
S2V5IEdlbmVyYXRpbmcgRnVuY3Rpb27igJ0gfCAweDAwIHwgMHg0MCk8bzpwPjwvbzpwPjwvcD4N
CjxwIGNsYXNzPSJNc29Ob3JtYWwiPiZndDszLiAoRm9sbG93IDUyOTUgcGFyYW1ldGVycykmbmJz
cDs8c3BhbiBzdHlsZT0iZm9udC1zaXplOjEwLjBwdDtjb2xvcjpibGFjayI+VExTLVBSRihTLUlN
Q0tbal0sICZxdW90O1Nlc3Npb24gS2V5IEdlbmVyYXRpbmcgRnVuY3Rpb24mcXVvdDssICZxdW90
O1wwJnF1b3Q7IHwgNjQpPC9zcGFuPiZuYnNwOz0mbmJzcDtQX2hhc2goUy1JTUNLW2pdLCAmcXVv
dDtTZXNzaW9uIEtleSBHZW5lcmF0aW5nIEZ1bmN0aW9u4oCdIHwgMHgwMCB8IDB4MDAgfCAweDQw
KTxvOnA+PC9vOnA+PC9wPg0KPHAgY2xhc3M9Ik1zb05vcm1hbCI+Jmd0OzxvOnA+Jm5ic3A7PC9v
OnA+PC9wPg0KPHAgY2xhc3M9Ik1zb05vcm1hbCI+Jmd0O0kgdGhpbmsgMSBvciAyIGlzIHdoYXQg
d2FzIHByb2JhYmx5IG9yaWdpbmFsbHkgaW50ZW5kZWQsIGhvd2V2ZXIgaXQgc2VlbXMgdGhhdCAz
IGlzIHdoYXQgaGFzIGJlZW4gaW1wbGVtZW50ZWQuJm5ic3A7IERvIHdlIGhhdmUgYWdyZWVtZW50
IG9uIHRoaXMgaXMgd2hhdCBjdXJyZW50IGltcGxlbWVudGF0aW9ucyBkbz8mbmJzcDs8bzpwPjwv
bzpwPjwvcD4NCjxwIGNsYXNzPSJNc29Ob3JtYWwiPjxvOnA+Jm5ic3A7PC9vOnA+PC9wPg0KPHAg
Y2xhc3M9Ik1zb05vcm1hbCI+Tm8sIE1pY3Jvc29mdCBpbXBsZW1lbnRzIG51bWJlciAxIG9mIEpv
ZeKAmXMgcHJlc2VudGVkIG9wdGlvbnMuIFRoYXQgaXMgLSBQXyZsdDtoYXNoJmd0OyhTLUlNQ0tb
al0sICZxdW90O1Nlc3Npb24gS2V5IEdlbmVyYXRpbmcgRnVuY3Rpb24mcXVvdDspLjxvOnA+PC9v
OnA+PC9wPg0KPHAgY2xhc3M9Ik1zb05vcm1hbCI+PG86cD4mbmJzcDs8L286cD48L3A+DQo8cCBj
bGFzcz0iTXNvTm9ybWFsIj5UaGlzIGZvbGxvd3MgdGhlIHNhbWUgcGF0dGVybiBhcyB0aGUgZXJy
YXRhIHdlIGFyZSBkaXNjdXNzaW9uLiBJIGFtIHZlcnkgc3VycHJpc2VkIHRvIGhlYXIgdGhhdCBD
aXNjb+KAmXMgaW1wbGVtZW50YXRpb24gbWF5IGJlIGRpZmZlcmVudC4gT2xlZywgY291bGQgeW91
IHBsZWFzZSBkb3VibGUgY2hlY2s/IEkgaGF2ZSBqdXN0IGRvdWJsZSBjaGVja2VkIG91ciBpbXBs
ZW1lbnRhdGlvbi4gU2luY2Ugb3VyIGltcGxlbWVudGF0aW9ucw0KIGludGVyb3AsIEkgYXNzdW1l
IHdlIG11c3QgaGF2ZSB0aGUgc2FtZSBpbXBsZW1lbnRhdGlvbi48bzpwPjwvbzpwPjwvcD4NCjxw
IGNsYXNzPSJNc29Ob3JtYWwiPjxvOnA+Jm5ic3A7PC9vOnA+PC9wPg0KPHAgY2xhc3M9Ik1zb05v
cm1hbCI+Sm9yZ2UgVmVyZ2FyYTxvOnA+PC9vOnA+PC9wPg0KPHAgY2xhc3M9Ik1zb05vcm1hbCI+
PG86cD4mbmJzcDs8L286cD48L3A+DQo8cCBjbGFzcz0iTXNvTm9ybWFsIj48bzpwPiZuYnNwOzwv
bzpwPjwvcD4NCjxkaXYgc3R5bGU9ImJvcmRlcjpub25lO2JvcmRlci10b3A6c29saWQgI0UxRTFF
MSAxLjBwdDtwYWRkaW5nOjMuMHB0IDBpbiAwaW4gMGluIj4NCjxwIGNsYXNzPSJNc29Ob3JtYWwi
PjxiPkZyb206PC9iPiBKb3NlcGggU2Fsb3dleSAmbHQ7am9lQHNhbG93ZXkubmV0Jmd0OyA8YnI+
DQo8Yj5TZW50OjwvYj4gVGh1cnNkYXksIE9jdG9iZXIgMjIsIDIwMjAgOTo1MyBBTTxicj4NCjxi
PlRvOjwvYj4gT2xlZyBQZWthciAmbHQ7b2xlZy5wZWthci4yMDE3QGdtYWlsLmNvbSZndDs8YnI+
DQo8Yj5DYzo8L2I+IEVNVSBXRyAmbHQ7ZW11QGlldGYub3JnJmd0OzsgSm9yZ2UgVmVyZ2FyYSAm
bHQ7am92ZXJnYXJAbWljcm9zb2Z0LmNvbSZndDs7IEpvdW5pIE1hbGluZW4gJmx0O2pAdzEuZmkm
Z3Q7PGJyPg0KPGI+U3ViamVjdDo8L2I+IFJlOiBQcm9wb3NlZCByZXNvbHV0aW9uIGZvciBURUFQ
IGVycmF0YSBmb3IgNTEyODxvOnA+PC9vOnA+PC9wPg0KPC9kaXY+DQo8cCBjbGFzcz0iTXNvTm9y
bWFsIj48bzpwPiZuYnNwOzwvbzpwPjwvcD4NCjxkaXY+DQo8ZGl2Pg0KPHAgY2xhc3M9Ik1zb05v
cm1hbCI+PG86cD4mbmJzcDs8L286cD48L3A+DQo8L2Rpdj4NCjxwIGNsYXNzPSJNc29Ob3JtYWwi
PjxvOnA+Jm5ic3A7PC9vOnA+PC9wPg0KPGRpdj4NCjxkaXY+DQo8cCBjbGFzcz0iTXNvTm9ybWFs
Ij5PbiBUaHUsIE9jdCAyMiwgMjAyMCBhdCA5OjI5IEFNIE9sZWcgUGVrYXIgJmx0OzxhIGhyZWY9
Im1haWx0bzpvbGVnLnBla2FyLjIwMTdAZ21haWwuY29tIiB0YXJnZXQ9Il9ibGFuayI+b2xlZy5w
ZWthci4yMDE3QGdtYWlsLmNvbTwvYT4mZ3Q7IHdyb3RlOjxvOnA+PC9vOnA+PC9wPg0KPC9kaXY+
DQo8YmxvY2txdW90ZSBzdHlsZT0iYm9yZGVyOm5vbmU7Ym9yZGVyLWxlZnQ6c29saWQgI0NDQ0ND
QyAxLjBwdDtwYWRkaW5nOjBpbiAwaW4gMGluIDYuMHB0O21hcmdpbi1sZWZ0OjQuOHB0O21hcmdp
bi1yaWdodDowaW4iPg0KPGRpdj4NCjxwIGNsYXNzPSJNc29Ob3JtYWwiPkkgYWdyZWUgdGhhdCBj
aGFuZ2luZyB0aGUgS0RGIGlzIGhhcm1mdWwgdG8gZXhpc3RpbmcgaW1wbGVtZW50YXRpb25zLiBI
b3dldmVyLCBpZiBJIHVuZGVyc3Rvb2QgY29ycmVjdGx5LCBKb2UncyBzdWdnZXN0aW9uJm5ic3A7
Zm9yIElNQ0tbal0gYWxzbyBicmVha3MgdGhlIGV4aXN0aW5nJm5ic3A7aW1wbGVtZW50YXRpb24u
IEkgc3RpbGwgc2VlIHRoYXQgd2UgY2FuIGRlZmluZSBhIHVuaWZpZWQgS0RGIGJ5IGNoYW5naW5n
IHRoZQ0KIEFQSSBpbiB0aGUgUkZDIGJ1dCB3aXRoIHRoZSBzYW1lIGhhcm0gdG8gdGhlIGV4aXN0
aW5nIGltcGxlbWVudGF0aW9uIGluIElNQ0tbal0gYXMgaW4gYm90aCBwcm9wb3NhbHM6PG86cD48
L286cD48L3A+DQo8ZGl2Pg0KPHAgY2xhc3M9Ik1zb05vcm1hbCI+PG86cD4mbmJzcDs8L286cD48
L3A+DQo8L2Rpdj4NCjxkaXY+DQo8cCBjbGFzcz0iTXNvTm9ybWFsIj5URUFQLVBSRiAoc2VjcmV0
LCBrZXkgbGFiZWwsIG9wdGlvbmFsIGRhdGEsIGxlbmd0aCkgPSBUTFMtUFJGKHNlY3JldCwga2V5
IGxhYmVsIHwgMHgwMCB8IG9wdGlvbmFsIGRhdGEsIGxlbmd0aCk8bzpwPjwvbzpwPjwvcD4NCjwv
ZGl2Pg0KPGRpdj4NCjxwIGNsYXNzPSJNc29Ob3JtYWwiPkpvZSwgdGhhbmtzIGZvciBwb2ludGlu
ZyBvdXQgdGhhdCBSRkMgNTI5NSBkb2Vzbid0IHNwZWNpZnkgdGhhdCBhIDB4MDAgaXMgdXNlZCB0
byByZXByZXNlbnQgbm8gb3B0aW9uYWwgZGF0YSwgdGhhdCB3YXMganVzdCBteSBtaXN0YWtlLjxv
OnA+PC9vOnA+PC9wPg0KPC9kaXY+DQo8ZGl2Pg0KPHAgY2xhc3M9Ik1zb05vcm1hbCI+PG86cD4m
bmJzcDs8L286cD48L3A+DQo8ZGl2Pg0KPHAgY2xhc3M9Ik1zb05vcm1hbCI+SU1TSzo8bzpwPjwv
bzpwPjwvcD4NCjwvZGl2Pg0KPGRpdj4NCjxwIGNsYXNzPSJNc29Ob3JtYWwiPkN1cnJlbnQgTWlj
cm9zb2Z0IGFuZCBDaXNjbyBpbXBsZW1lbnRhdGlvbjogUF9oYXNoKEVNU0ssICZxdW90OzxhIGhy
ZWY9Im1haWx0bzpURUFQYmluZGtleUBpZXRmLm9yZyIgdGFyZ2V0PSJfYmxhbmsiPlRFQVBiaW5k
a2V5QGlldGYub3JnPC9hPiZxdW90OyB8IDB4MDAgfCAweDAwIHwgMHg0MCkNCjxvOnA+PC9vOnA+
PC9wPg0KPC9kaXY+DQo8ZGl2Pg0KPHAgY2xhc3M9Ik1zb05vcm1hbCI+Sm9lJ3MgcHJvcG9zYWw6
IFBfaGFzaChFTVNLLCAmcXVvdDs8YSBocmVmPSJtYWlsdG86VEVBUGJpbmRrZXlAaWV0Zi5vcmci
IHRhcmdldD0iX2JsYW5rIj5URUFQYmluZGtleUBpZXRmLm9yZzwvYT4mcXVvdDsgfCAweDAwIHwg
MHgwMCB8IDB4NDApLCB0aGUgc2FtZSwganVzdCB0aGUgQVBJIGNvcnJlY3Rpb248bzpwPjwvbzpw
PjwvcD4NCjwvZGl2Pg0KPGRpdj4NCjxwIGNsYXNzPSJNc29Ob3JtYWwiPlVuaWZpZWQgS0RGIHBy
b3Bvc2FsOiZuYnNwO1RFQVAtUFJGKEVNU0ssICZxdW90OzxhIGhyZWY9Im1haWx0bzpURUFQYmlu
ZGtleUBpZXRmLm9yZyIgdGFyZ2V0PSJfYmxhbmsiPlRFQVBiaW5ka2V5QGlldGYub3JnPC9hPiZx
dW90OywgJmx0O25vIG9wdGlvbmFsIGRhdGEmZ3Q7LCA2NCkgPSBQX2hhc2goRU1TSywgJnF1b3Q7
PGEgaHJlZj0ibWFpbHRvOlRFQVBiaW5ka2V5QGlldGYub3JnIiB0YXJnZXQ9Il9ibGFuayI+VEVB
UGJpbmRrZXlAaWV0Zi5vcmc8L2E+JnF1b3Q7DQogfCAweDAwIHwgMHgwMCB8IDB4NDApJm5ic3A7
PG86cD48L286cD48L3A+DQo8L2Rpdj4NCjxkaXY+DQo8cCBjbGFzcz0iTXNvTm9ybWFsIj4tLS0g
bm8gaW1wbGVtZW50YXRpb24gY2hhbmdlPG86cD48L286cD48L3A+DQo8L2Rpdj4NCjxkaXY+DQo8
cCBjbGFzcz0iTXNvTm9ybWFsIj48bzpwPiZuYnNwOzwvbzpwPjwvcD4NCjwvZGl2Pg0KPGRpdj4N
CjxwIGNsYXNzPSJNc29Ob3JtYWwiPklNQ0tbal06PG86cD48L286cD48L3A+DQo8L2Rpdj4NCjxk
aXY+DQo8ZGl2Pg0KPHAgY2xhc3M9Ik1zb05vcm1hbCI+Q3VycmVudCBNaWNyb3NvZnQgYW5kIENp
c2NvIGltcGxlbWVudGF0aW9uOiBQX2hhc2goUy1JTUNLW2otMV0sICZxdW90O0lubmVyIE1ldGhv
ZHMgQ29tcG91bmQgS2V5c+KAnSB8IElNU0tbal0pJm5ic3A7PG86cD48L286cD48L3A+DQo8L2Rp
dj4NCjxkaXY+DQo8cCBjbGFzcz0iTXNvTm9ybWFsIj5Kb2UncyBwcm9wb3NhbDombmJzcDtQX2hh
c2goUy1JTUNLW2otMV0sICZxdW90O0lubmVyIE1ldGhvZHMgQ29tcG91bmQgS2V5cyZxdW90OyB8
IElNU0tbal0gfCAweDAwIHwgMHgzQyk8bzpwPjwvbzpwPjwvcD4NCjwvZGl2Pg0KPGRpdj4NCjxw
IGNsYXNzPSJNc29Ob3JtYWwiPlVuaWZpZWQgS0RGIHByb3Bvc2FsOiBURUFQLVBSRihTLUlNQ0tb
ai0xXSwgJnF1b3Q7SW5uZXIgTWV0aG9kcyBDb21wb3VuZCBLZXlzJnF1b3Q7LCBJTVNLW2pdLCA2
MCkgPSBQX2hhc2goUy1JTUNLW2otMV0sICZxdW90O0lubmVyIE1ldGhvZHMgQ29tcG91bmQgS2V5
cyZxdW90OyB8IElNU0tbal0gfCAweDAwIHwgMHgzQyk8bzpwPjwvbzpwPjwvcD4NCjwvZGl2Pg0K
PC9kaXY+DQo8ZGl2Pg0KPGRpdj4NCjxwIGNsYXNzPSJNc29Ob3JtYWwiPi0tLSBpbXBsZW1lbnRh
dGlvbiBjaGFuZ2U8bzpwPjwvbzpwPjwvcD4NCjwvZGl2Pg0KPC9kaXY+DQo8L2Rpdj4NCjwvZGl2
Pg0KPC9ibG9ja3F1b3RlPg0KPGRpdj4NCjxwIGNsYXNzPSJNc29Ob3JtYWwiPjxvOnA+Jm5ic3A7
PC9vOnA+PC9wPg0KPC9kaXY+DQo8ZGl2Pg0KPHAgY2xhc3M9Ik1zb05vcm1hbCI+W0pvZV0gVGhh
dCB3YXMgbXkgaW5pdGlhbCBwcm9wb3NhbCwgYnV0IGJhc2VkIG9uIEpvcmdlJ3MgY29tbWVudCBp
dCBpcyBtb2RpZmllZCB0bzo8bzpwPjwvbzpwPjwvcD4NCjwvZGl2Pg0KPGRpdj4NCjxwIGNsYXNz
PSJNc29Ob3JtYWwiPjxicj4NCklNQ0tbal0gPSBUTFMtUFJGKFMtSU1DS1tqLTFdLCAmcXVvdDtJ
bm5lciBNZXRob2RzIENvbXBvdW5kIEtleXMmcXVvdDssJm5ic3A7PHNwYW4gc3R5bGU9ImZvbnQt
c2l6ZToxMC41cHQ7Y29sb3I6IzJDNDM1MyI+SU1TS1tqXSkmbmJzcDsgdG8gZ2VuZXJhdGUgYSBs
ZW5ndGggb2YgNjAgYnl0ZXM8L3NwYW4+PG86cD48L286cD48L3A+DQo8L2Rpdj4NCjxkaXY+DQo8
cCBjbGFzcz0iTXNvTm9ybWFsIj48c3BhbiBzdHlsZT0iZm9udC1zaXplOjEwLjVwdDtjb2xvcjoj
MkM0MzUzIj5JTUNLW2pdID0mbmJzcDs8L3NwYW4+UF9oYXNoKFMtSU1DS1tqLTFdLCAmcXVvdDtJ
bm5lciBNZXRob2RzIENvbXBvdW5kIEtleXPigJ0gfCBJTVNLW2pdKSZuYnNwOzxvOnA+PC9vOnA+
PC9wPg0KPC9kaXY+DQo8ZGl2Pg0KPHAgY2xhc3M9Ik1zb05vcm1hbCI+Jm5ic3A7PG86cD48L286
cD48L3A+DQo8L2Rpdj4NCjxibG9ja3F1b3RlIHN0eWxlPSJib3JkZXI6bm9uZTtib3JkZXItbGVm
dDpzb2xpZCAjQ0NDQ0NDIDEuMHB0O3BhZGRpbmc6MGluIDBpbiAwaW4gNi4wcHQ7bWFyZ2luLWxl
ZnQ6NC44cHQ7bWFyZ2luLXJpZ2h0OjBpbiI+DQo8ZGl2Pg0KPGRpdj4NCjxkaXY+DQo8cCBjbGFz
cz0iTXNvTm9ybWFsIj48bzpwPiZuYnNwOzwvbzpwPjwvcD4NCjwvZGl2Pg0KPGRpdj4NCjxwIGNs
YXNzPSJNc29Ob3JtYWwiPk1TSzo8bzpwPjwvbzpwPjwvcD4NCjwvZGl2Pg0KPGRpdj4NCjxwIGNs
YXNzPSJNc29Ob3JtYWwiPkN1cnJlbnQgTWljcm9zb2Z0IGFuZCBDaXNjbyBpbXBsZW1lbnRhdGlv
bjogUF9oYXNoKFMtSU1DS1tqXSwgJnF1b3Q7U2Vzc2lvbiBLZXkgR2VuZXJhdGluZyBGdW5jdGlv
buKAnSB8IDB4MDAgfCAweDAwIHwgMHg0MCk8bzpwPjwvbzpwPjwvcD4NCjwvZGl2Pg0KPGRpdj4N
CjxwIGNsYXNzPSJNc29Ob3JtYWwiPlVuaWZpZWQgS0RGIHByb3Bvc2FsOiBURUFQLVBSRihTLUlN
Q0tbal0sICZxdW90O1Nlc3Npb24gS2V5IEdlbmVyYXRpbmcgRnVuY3Rpb27igJ0sICZsdDtubyBv
cHRpb25hbCBkYXRhJmd0OywgNjQpID0gUF9oYXNoKFMtSU1DS1tqXSwgJnF1b3Q7U2Vzc2lvbiBL
ZXkgR2VuZXJhdGluZyBGdW5jdGlvbuKAnSB8IDB4MDAgfCAweDAwIHwgMHg0MCk8bzpwPjwvbzpw
PjwvcD4NCjwvZGl2Pg0KPGRpdj4NCjxkaXY+DQo8cCBjbGFzcz0iTXNvTm9ybWFsIj4tLS0gbm8g
aW1wbGVtZW50YXRpb24gY2hhbmdlPG86cD48L286cD48L3A+DQo8L2Rpdj4NCjwvZGl2Pg0KPGRp
dj4NCjxwIGNsYXNzPSJNc29Ob3JtYWwiPjxvOnA+Jm5ic3A7PC9vOnA+PC9wPg0KPC9kaXY+DQo8
L2Rpdj4NCjwvZGl2Pg0KPC9ibG9ja3F1b3RlPg0KPGRpdj4NCjxwIGNsYXNzPSJNc29Ob3JtYWwi
PltKb2VdIFRoaXMgaXMgdGhlIG9uZSB3ZSBoYXZlIG5vdCBkaXNjdXNzZWQgeWV0LiZuYnNwOyBU
aGlzIGRlcml2YXRpb24gaXMgYWxzbyBhbWJpZ3VvdXMuJm5ic3A7IFRIaXMgc2VjdGlvbiBkb2Vz
IG5vdCByZWZlcmVuY2UgNTI5NS4mbmJzcDsgSXQncyBub3QgY2xlYXIgaWYgdGhlIG9yaWdpbmFs
IGludGVudCB3YXMgdG8gaW5jbHVkZSB0aGUgbGVuZ3RoIGluIHRoZSBoYXNoIG9yIG5vdC4mbmJz
cDsgSSB0aGluayB0aGVyZSBhcmUgYSBmZXcgaW50ZXJwcmV0YXRpb25zOjxvOnA+PC9vOnA+PC9w
Pg0KPC9kaXY+DQo8ZGl2Pg0KPHAgY2xhc3M9Ik1zb05vcm1hbCI+PG86cD4mbmJzcDs8L286cD48
L3A+DQo8L2Rpdj4NCjxkaXY+DQo8cCBjbGFzcz0iTXNvTm9ybWFsIj48c3BhbiBzdHlsZT0iZm9u
dC1zaXplOjEwLjBwdDtjb2xvcjpibGFjayI+MS4gVExTLVBSRihTLUlNQ0tbal0sICZxdW90O1Nl
c3Npb24gS2V5IEdlbmVyYXRpbmcgRnVuY3Rpb24mcXVvdDspPC9zcGFuPiZuYnNwOyBpdGVyYXRl
ZCB0byBnZW5lcmF0ZSA2NCBieXRlcyA9Jm5ic3A7UF9oYXNoKFMtSU1DS1tqXSwgJnF1b3Q7U2Vz
c2lvbiBLZXkgR2VuZXJhdGluZyBGdW5jdGlvbuKAnSk8bzpwPjwvbzpwPjwvcD4NCjwvZGl2Pg0K
PGRpdj4NCjxwIGNsYXNzPSJNc29Ob3JtYWwiPjxzcGFuIHN0eWxlPSJmb250LXNpemU6MTAuMHB0
O2NvbG9yOmJsYWNrIj4yLiBUTFMtUFJGKFMtSU1DS1tqXSwgJnF1b3Q7U2Vzc2lvbiBLZXkgR2Vu
ZXJhdGluZyBGdW5jdGlvbiZxdW90OywgNjQpPC9zcGFuPiZuYnNwOyBpdGVyYXRlZCB0byBnZW5l
cmF0ZSA2NCBieXRlcyA9Jm5ic3A7UF9oYXNoKFMtSU1DS1tqXSwgJnF1b3Q7U2Vzc2lvbiBLZXkg
R2VuZXJhdGluZyBGdW5jdGlvbuKAnSB8IDB4MDAgfCAweDQwKTxvOnA+PC9vOnA+PC9wPg0KPC9k
aXY+DQo8ZGl2Pg0KPHAgY2xhc3M9Ik1zb05vcm1hbCI+My4gKEZvbGxvdyA1Mjk1IHBhcmFtZXRl
cnMpJm5ic3A7PHNwYW4gc3R5bGU9ImZvbnQtc2l6ZToxMC4wcHQ7Y29sb3I6YmxhY2siPlRMUy1Q
UkYoUy1JTUNLW2pdLCAmcXVvdDtTZXNzaW9uIEtleSBHZW5lcmF0aW5nIEZ1bmN0aW9uJnF1b3Q7
LCAmcXVvdDtcMCZxdW90OyB8IDY0KTwvc3Bhbj4mbmJzcDs9Jm5ic3A7UF9oYXNoKFMtSU1DS1tq
XSwgJnF1b3Q7U2Vzc2lvbiBLZXkgR2VuZXJhdGluZyBGdW5jdGlvbuKAnSB8IDB4MDAgfCAweDAw
IHwgMHg0MCk8bzpwPjwvbzpwPjwvcD4NCjwvZGl2Pg0KPGRpdj4NCjxwIGNsYXNzPSJNc29Ob3Jt
YWwiPjxvOnA+Jm5ic3A7PC9vOnA+PC9wPg0KPC9kaXY+DQo8ZGl2Pg0KPHAgY2xhc3M9Ik1zb05v
cm1hbCI+SSB0aGluayAxIG9yIDIgaXMgd2hhdCB3YXMgcHJvYmFibHkgb3JpZ2luYWxseSBpbnRl
bmRlZCwgaG93ZXZlciBpdCBzZWVtcyB0aGF0IDMgaXMgd2hhdCBoYXMgYmVlbiBpbXBsZW1lbnRl
ZC4mbmJzcDsgRG8gd2UgaGF2ZSBhZ3JlZW1lbnQgb24gdGhpcyBpcyB3aGF0IGN1cnJlbnQgaW1w
bGVtZW50YXRpb25zIGRvPyZuYnNwOzxvOnA+PC9vOnA+PC9wPg0KPC9kaXY+DQo8ZGl2Pg0KPHBy
ZSBzdHlsZT0iYnJlYWstYmVmb3JlOnBhZ2UiPjxzcGFuIHN0eWxlPSJjb2xvcjpibGFjayI+PG86
cD4mbmJzcDs8L286cD48L3NwYW4+PC9wcmU+DQo8L2Rpdj4NCjxkaXY+DQo8cCBjbGFzcz0iTXNv
Tm9ybWFsIj48bzpwPiZuYnNwOzwvbzpwPjwvcD4NCjwvZGl2Pg0KPGRpdj4NCjxwIGNsYXNzPSJN
c29Ob3JtYWwiPiZuYnNwOzxvOnA+PC9vOnA+PC9wPg0KPC9kaXY+DQo8YmxvY2txdW90ZSBzdHls
ZT0iYm9yZGVyOm5vbmU7Ym9yZGVyLWxlZnQ6c29saWQgI0NDQ0NDQyAxLjBwdDtwYWRkaW5nOjBp
biAwaW4gMGluIDYuMHB0O21hcmdpbi1sZWZ0OjQuOHB0O21hcmdpbi1yaWdodDowaW4iPg0KPGRp
dj4NCjxkaXY+DQo8ZGl2Pg0KPHAgY2xhc3M9Ik1zb05vcm1hbCI+Sm9yZ2UsIHBsZWFzZSBjb3Jy
ZWN0IG1lIGlmIEkgbWlzaW50ZXJwcmV0Jm5ic3A7dGhlIE1pY3Jvc29mdCBpbXBsZW1lbnRhdGlv
bi4mbmJzcDs8bzpwPjwvbzpwPjwvcD4NCjwvZGl2Pg0KPC9kaXY+DQo8L2Rpdj4NCjxwIGNsYXNz
PSJNc29Ob3JtYWwiPjxvOnA+Jm5ic3A7PC9vOnA+PC9wPg0KPGRpdj4NCjxkaXY+DQo8cCBjbGFz
cz0iTXNvTm9ybWFsIj5PbiBUaHUsIE9jdCAyMiwgMjAyMCBhdCA2OjU1IFBNIEpvc2VwaCBTYWxv
d2V5ICZsdDs8YSBocmVmPSJtYWlsdG86am9lQHNhbG93ZXkubmV0IiB0YXJnZXQ9Il9ibGFuayI+
am9lQHNhbG93ZXkubmV0PC9hPiZndDsgd3JvdGU6PG86cD48L286cD48L3A+DQo8L2Rpdj4NCjxi
bG9ja3F1b3RlIHN0eWxlPSJib3JkZXI6bm9uZTtib3JkZXItbGVmdDpzb2xpZCAjQ0NDQ0NDIDEu
MHB0O3BhZGRpbmc6MGluIDBpbiAwaW4gNi4wcHQ7bWFyZ2luLWxlZnQ6NC44cHQ7bWFyZ2luLXJp
Z2h0OjBpbiI+DQo8ZGl2Pg0KPGRpdj4NCjxwIGNsYXNzPSJNc29Ob3JtYWwiPjxvOnA+Jm5ic3A7
PC9vOnA+PC9wPg0KPC9kaXY+DQo8cCBjbGFzcz0iTXNvTm9ybWFsIj48bzpwPiZuYnNwOzwvbzpw
PjwvcD4NCjxkaXY+DQo8ZGl2Pg0KPHAgY2xhc3M9Ik1zb05vcm1hbCI+T24gVGh1LCBPY3QgMjIs
IDIwMjAgYXQgNjo1OSBBTSBPbGVnIFBla2FyICZsdDs8YSBocmVmPSJtYWlsdG86b2xlZy5wZWth
ci4yMDE3QGdtYWlsLmNvbSIgdGFyZ2V0PSJfYmxhbmsiPm9sZWcucGVrYXIuMjAxN0BnbWFpbC5j
b208L2E+Jmd0OyB3cm90ZTo8bzpwPjwvbzpwPjwvcD4NCjwvZGl2Pg0KPGJsb2NrcXVvdGUgc3R5
bGU9ImJvcmRlcjpub25lO2JvcmRlci1sZWZ0OnNvbGlkICNDQ0NDQ0MgMS4wcHQ7cGFkZGluZzow
aW4gMGluIDBpbiA2LjBwdDttYXJnaW4tbGVmdDo0LjhwdDttYXJnaW4tcmlnaHQ6MGluIj4NCjxk
aXY+DQo8ZGl2Pg0KPHAgY2xhc3M9Ik1zb05vcm1hbCI+SGkgYWxsLDxvOnA+PC9vOnA+PC9wPg0K
PC9kaXY+DQo8ZGl2Pg0KPHAgY2xhc3M9Ik1zb05vcm1hbCI+U3BlYWtpbmcgYWJvdXQgYm90aCBl
cnJhdGEgNTEyNyBhbmQgNTEyOCwgSSB0aGluayB3ZSBuZWVkIHRvIGFsaWduIGFsbCBrZXkgZGVy
aXZhdGlvbiBjYWxscyBpbiBURUFQIFJGQyB3aXRoIHRoZSBzYW1lIHJ1bGUvZm9ybWF0IHRvIG1h
a2UgdGhlIFJGQyBlYXNpZXIgdG8gdW5kZXJzdGFuZC4gVGhpcyBjYW4gYmUgYWNoaWV2ZWQgYnkg
aW50cm9kdWNpbmcgYSB1bmlmaWVkIHNpbmdsZSBQUkYgZnVuY3Rpb24gdGhhdA0KIHdpbGwgYmUg
Y2FsbGVkIGZyb20gYWxsIHRoZSByZWxldmFudCBSRkMgbG9jYXRpb25zLiBGb3IgbWUgaXQgc291
bmRzIGJldHRlciB0aGFuIGlmIHdlIGFsaWduIGp1c3QgcGFydCBvZiBLREYgY2FsbHMgd2l0aCBS
RkMgNTI5NSAod2hlcmUgdGhlIG91dHB1dCBsZW5ndGggaXMgaW5jbHVkZWQgaW50byBzZWVkKS4g
QWxzbzogaW4gc29tZSBLREYgY2FsbHMgd2UgZG8gaGF2ZSBvcHRpb25hbCBkYXRhIGFuZCBpbiBz
b21lIG5vLiBUaGlzIGNvdWxkIGJlDQogYWxzbyB1bmlmaWVkLiZuYnNwOzxvOnA+PC9vOnA+PC9w
Pg0KPC9kaXY+DQo8ZGl2Pg0KPHAgY2xhc3M9Ik1zb05vcm1hbCI+PG86cD4mbmJzcDs8L286cD48
L3A+DQo8L2Rpdj4NCjwvZGl2Pg0KPC9ibG9ja3F1b3RlPg0KPGRpdj4NCjxwIGNsYXNzPSJNc29O
b3JtYWwiPltKb2VdIEkgZG9uJ3QgdGhpbmsgdGhpcyB3YXMgdGhlIG9yaWdpbmFsIGludGVudCBv
ZiB0aGUgZG9jdW1lbnQuJm5ic3A7IFRoZSBJTVNLIGRlcml2YXRpb24gcmVmZXJlbmNlZCA1Mjk1
IHdoaWxlIHRoZSBvdGhlcnMganVzdCByZWZlcmVuY2UgdGhlIFRMUyBQUkYuJm5ic3A7IEkgdGhp
bmsgdG8gdW5pZnkgdGhlbSB3b3VsZCByZXF1aXJlIGEgZG9jdW1lbnQgdXBkYXRlIGFuZCBJJ20g
bm90IHN1cmUgd2hhdCB3ZSB3b3VsZCBnYWluDQogZXNwZWNpYWxseSBpZiB3ZSBoYXZlIGltcGxl
bWVudGF0aW9ucyB0aGF0IGRvIHRoaXMuJm5ic3A7Jm5ic3A7PG86cD48L286cD48L3A+DQo8L2Rp
dj4NCjxkaXY+DQo8cCBjbGFzcz0iTXNvTm9ybWFsIj4mbmJzcDs8bzpwPjwvbzpwPjwvcD4NCjwv
ZGl2Pg0KPGJsb2NrcXVvdGUgc3R5bGU9ImJvcmRlcjpub25lO2JvcmRlci1sZWZ0OnNvbGlkICND
Q0NDQ0MgMS4wcHQ7cGFkZGluZzowaW4gMGluIDBpbiA2LjBwdDttYXJnaW4tbGVmdDo0LjhwdDtt
YXJnaW4tcmlnaHQ6MGluIj4NCjxkaXY+DQo8ZGl2Pg0KPHAgY2xhc3M9Ik1zb05vcm1hbCI+U28g
SSB3b3VsZCBzdWdnZXN0IGludHJvZHVjaW5nOjxvOnA+PC9vOnA+PC9wPg0KPC9kaXY+DQo8ZGl2
Pg0KPHAgY2xhc3M9Ik1zb05vcm1hbCI+VEVBUC1QUkYgKHNlY3JldCwga2V5IGxhYmVsLCBvcHRp
b25hbCBkYXRhLCBsZW5ndGgpID0gVExTLVBSRihzZWNyZXQsIGtleSBsYWJlbCB8IDB4MDAgfCBv
cHRpb25hbCBkYXRhLCBsZW5ndGgpPG86cD48L286cD48L3A+DQo8L2Rpdj4NCjxkaXY+DQo8cCBj
bGFzcz0iTXNvTm9ybWFsIj53aGVyZSBhIHNpbmdsZSBieXRlIDB4MDAgaXMgdXNlZCBmb3Igbm8g
b3B0aW9uYWwgZGF0YSwgbGVuZ3RoIGlzIGEgMi1vY3RldCB1bnNpZ25lZCBpbnRlZ2VyIGluIG5l
dHdvcmsgYnl0ZSBvcmRlci48bzpwPjwvbzpwPjwvcD4NCjwvZGl2Pg0KPGRpdj4NCjxwIGNsYXNz
PSJNc29Ob3JtYWwiPjxvOnA+Jm5ic3A7PC9vOnA+PC9wPg0KPC9kaXY+DQo8L2Rpdj4NCjwvYmxv
Y2txdW90ZT4NCjxkaXY+DQo8cCBjbGFzcz0iTXNvTm9ybWFsIj5bSm9lXSBJIGRvbid0IHRoaW5r
IHRoYXQgNTI5NSBzcGVjaWZpZXMgdGhhdCBhIDB4MDAgaXMgdXNlZCB0byByZXByZXNlbnQgbm8g
b3B0aW9uYWwgZGF0YS4mbmJzcDsgRGlkIHlvdSBzZWUgdGhpcyBpbiB0aGUgc3BlYz8gSXQgbWF5
IGJlIGFtYmlndW91cywgYnV0IEkgdGhpbmsgdGhlIGludGVudCBpcyB0aGF0IG9wdGlvbmFsIGRh
dGEgaXMganVzdCBvbWl0dGVkIGlmIGl0IGlzIG5vdCBwcm92aWRlZC4mbmJzcDs8bzpwPjwvbzpw
PjwvcD4NCjwvZGl2Pg0KPGRpdj4NCjxwIGNsYXNzPSJNc29Ob3JtYWwiPjxvOnA+Jm5ic3A7PC9v
OnA+PC9wPg0KPC9kaXY+DQo8ZGl2Pg0KPHAgY2xhc3M9Ik1zb05vcm1hbCI+Jm5ic3A7PG86cD48
L286cD48L3A+DQo8L2Rpdj4NCjxibG9ja3F1b3RlIHN0eWxlPSJib3JkZXI6bm9uZTtib3JkZXIt
bGVmdDpzb2xpZCAjQ0NDQ0NDIDEuMHB0O3BhZGRpbmc6MGluIDBpbiAwaW4gNi4wcHQ7bWFyZ2lu
LWxlZnQ6NC44cHQ7bWFyZ2luLXJpZ2h0OjBpbiI+DQo8ZGl2Pg0KPGRpdj4NCjxwIGNsYXNzPSJN
c29Ob3JtYWwiPlRoZW46PG86cD48L286cD48L3A+DQo8L2Rpdj4NCjxkaXY+DQo8cCBjbGFzcz0i
TXNvTm9ybWFsIj5JTVNLID0gRmlyc3QgMzIgb2N0ZXRzIG9mIFRFQVAtUFJGKEVNU0ssICZxdW90
OzxhIGhyZWY9Im1haWx0bzpURUFQYmluZGtleUBpZXRmLm9yZyIgdGFyZ2V0PSJfYmxhbmsiPlRF
QVBiaW5ka2V5QGlldGYub3JnPC9hPiZxdW90OywgNjQpID0gVExTLVBSRihFTVNLLCAmcXVvdDs8
YSBocmVmPSJtYWlsdG86VEVBUGJpbmRrZXlAaWV0Zi5vcmciIHRhcmdldD0iX2JsYW5rIj5URUFQ
YmluZGtleUBpZXRmLm9yZzwvYT4mcXVvdDsgfCAweDAwIHwgMHgwMA0KIHwgMHgwMCB8IDB4NDAp
PGJyPg0KSU1DS1tqXSA9IFRFQVAtUFJGKFMtSU1DS1tqLTFdLCAmcXVvdDtJbm5lciBNZXRob2Rz
IENvbXBvdW5kIEtleXMmcXVvdDssIElNU0tbal0sIDYwKSA9IFRMUy1QUkYoUy1JTUNLW2otMV0s
ICZxdW90O0lubmVyIE1ldGhvZHMgQ29tcG91bmQgS2V5cyZxdW90OyB8IDB4MDAgfCBJTVNLW2pd
IHwgMHgwMCB8IDB4M0MpPGJyPg0KTVNLID0gVEVBUC1QUkYoUy1JTUNLW2pdLCAmcXVvdDtTZXNz
aW9uIEtleSBHZW5lcmF0aW5nIEZ1bmN0aW9u4oCdLCA2NCkgPSBUTFMtUFJGKFMtSU1DS1tqXSwg
JnF1b3Q7U2Vzc2lvbiBLZXkgR2VuZXJhdGluZyBGdW5jdGlvbiZxdW90OyB8IDB4MDAgfCAweDAw
IHwgMHgwMCB8IDB4NDApPGJyPg0KRU1TSyA9IFRFQVAtUFJGKFMtSU1DS1tqXSwg4oCdRXh0ZW5k
ZWQgU2Vzc2lvbiBLZXkgR2VuZXJhdGluZyBGdW5jdGlvbuKAnSwgNjQpID0gVExTLVBSRihTLUlN
Q0tbal0sICZxdW90O0V4dGVuZGVkIFNlc3Npb24gS2V5IEdlbmVyYXRpbmcgRnVuY3Rpb24mcXVv
dDsgfCAweDAwIHwgMHgwMCB8IDB4MDAgfCAweDQwKTxvOnA+PC9vOnA+PC9wPg0KPC9kaXY+DQo8
ZGl2Pg0KPHAgY2xhc3M9Ik1zb05vcm1hbCI+PG86cD4mbmJzcDs8L286cD48L3A+DQo8L2Rpdj4N
CjxkaXY+DQo8cCBjbGFzcz0iTXNvTm9ybWFsIj5UaGlzIG1heSBjaGFuZ2UgdGhlIGV4aXN0aW5n
IGltcGxlbWVudGF0aW9uIGJ1dCB3aWxsIG1ha2UgaXQgbW9yZSBjbGVhciAtIG5lZWQgdG8gY3Jl
YXRlIGFuZCBjYWxsIGp1c3Qgb25lIEtERiBmdW5jdGlvbi48bzpwPjwvbzpwPjwvcD4NCjwvZGl2
Pg0KPGRpdj4NCjxwIGNsYXNzPSJNc29Ob3JtYWwiPjxvOnA+Jm5ic3A7PC9vOnA+PC9wPg0KPC9k
aXY+DQo8ZGl2Pg0KPHAgY2xhc3M9Ik1zb05vcm1hbCI+V2UgY2FuIHJlbW92ZSZuYnNwOzB4MDAg
dGhhdCBjb21lcyBhZnRlciB0aGUga2V5IGxhYmVsIC0gd2hpbGUgaXQgaXMgcmVxdWlyZWQgYnkm
bmJzcDtSRkMgNTI5NS4gQnV0IHRoZXJlJm5ic3A7dGhlIGtleSBsYWJlbCBpcyBhbHNvIEFTQ0lJ
IHByaW50YWJsZSBzdHJpbmcuIEpvZSwgZG8geW91IHJlbWVtYmVyIHdoYXQgd2FzIHRoZSBtb3Rp
dmF0aW9uIHRvIHB1dCAweDAwIGFmdGVyIHRoZSBrZXkgbGFiZWwgcGFyYW1ldGVyPzxvOnA+PC9v
OnA+PC9wPg0KPC9kaXY+DQo8L2Rpdj4NCjwvYmxvY2txdW90ZT4NCjxkaXY+DQo8cCBjbGFzcz0i
TXNvTm9ybWFsIj48bzpwPiZuYnNwOzwvbzpwPjwvcD4NCjwvZGl2Pg0KPGRpdj4NCjxwIGNsYXNz
PSJNc29Ob3JtYWwiPltKb2VdIHRoZSBudWxsIGFmdGVyIHRoZSBrZXkgbGFiZWwgaXMgdG8gcHJv
dmlkZSBhIGRlbGltaXRlciBiZXR3ZWVuIHRoZSBrZXkgbGFiZWwgYW5kIG9wdGlvbmFsIGRhdGEu
Jm5ic3A7IFNpbmNlIHRoZSBvcHRpb25hbCBkYXRhIGNhbiBiZSBhcmJpdHJhcnkgY29udGVudCB0
aGUgbnVsbCBwcmV2ZW50cyB0d28gZGlmZmVyZW50IGxhYmxlbHMmbmJzcDt3aXRoIHNwZWNpYWxs
eSZuYnNwO2NyYWZ0ZWQgb3B0aW9uYWwgZGF0YSBmcm9tIGRlcml2aW5nDQogdGhlIHNhbWUga2V5
LiZuYnNwOyZuYnNwOzxvOnA+PC9vOnA+PC9wPg0KPC9kaXY+DQo8ZGl2Pg0KPHAgY2xhc3M9Ik1z
b05vcm1hbCI+Jm5ic3A7PG86cD48L286cD48L3A+DQo8L2Rpdj4NCjxibG9ja3F1b3RlIHN0eWxl
PSJib3JkZXI6bm9uZTtib3JkZXItbGVmdDpzb2xpZCAjQ0NDQ0NDIDEuMHB0O3BhZGRpbmc6MGlu
IDBpbiAwaW4gNi4wcHQ7bWFyZ2luLWxlZnQ6NC44cHQ7bWFyZ2luLXJpZ2h0OjBpbiI+DQo8ZGl2
Pg0KPGRpdj4NCjxwIGNsYXNzPSJNc29Ob3JtYWwiPjxvOnA+Jm5ic3A7PC9vOnA+PC9wPg0KPC9k
aXY+DQo8ZGl2Pg0KPHAgY2xhc3M9Ik1zb05vcm1hbCI+T2xlZzxvOnA+PC9vOnA+PC9wPg0KPC9k
aXY+DQo8ZGl2Pg0KPHAgY2xhc3M9Ik1zb05vcm1hbCI+PG86cD4mbmJzcDs8L286cD48L3A+DQo8
L2Rpdj4NCjxkaXY+DQo8cCBjbGFzcz0iTXNvTm9ybWFsIj48bzpwPiZuYnNwOzwvbzpwPjwvcD4N
CjwvZGl2Pg0KPGRpdj4NCjxkaXY+DQo8cCBjbGFzcz0iTXNvTm9ybWFsIj5PbiBUaHUsIE9jdCAy
MiwgMjAyMCBhdCAyOjU0IEFNIEpvc2VwaCBTYWxvd2V5ICZsdDs8YSBocmVmPSJtYWlsdG86am9l
QHNhbG93ZXkubmV0IiB0YXJnZXQ9Il9ibGFuayI+am9lQHNhbG93ZXkubmV0PC9hPiZndDsgd3Jv
dGU6PG86cD48L286cD48L3A+DQo8L2Rpdj4NCjxibG9ja3F1b3RlIHN0eWxlPSJib3JkZXI6bm9u
ZTtib3JkZXItbGVmdDpzb2xpZCAjQ0NDQ0NDIDEuMHB0O3BhZGRpbmc6MGluIDBpbiAwaW4gNi4w
cHQ7bWFyZ2luLWxlZnQ6NC44cHQ7bWFyZ2luLXJpZ2h0OjBpbiI+DQo8ZGl2Pg0KPGRpdj4NCjxw
IGNsYXNzPSJNc29Ob3JtYWwiPihJIGFjY2lkZW50YWxseSZuYnNwO2Ryb3BwZWQgdGhpcyBsaXN0
IGZyb20gdGhlIGNvbnZlcnNhdGlvbik8bzpwPjwvbzpwPjwvcD4NCjwvZGl2Pg0KPHAgY2xhc3M9
Ik1zb05vcm1hbCI+PG86cD4mbmJzcDs8L286cD48L3A+DQo8ZGl2Pg0KPGRpdj4NCjxwIGNsYXNz
PSJNc29Ob3JtYWwiPk9uIFdlZCwgT2N0IDIxLCAyMDIwIGF0IDQ6NDggUE0gSm9yZ2UgVmVyZ2Fy
YSAmbHQ7PGEgaHJlZj0ibWFpbHRvOmpvdmVyZ2FyQG1pY3Jvc29mdC5jb20iIHRhcmdldD0iX2Js
YW5rIj5qb3ZlcmdhckBtaWNyb3NvZnQuY29tPC9hPiZndDsgd3JvdGU6PG86cD48L286cD48L3A+
DQo8L2Rpdj4NCjxibG9ja3F1b3RlIHN0eWxlPSJib3JkZXI6bm9uZTtib3JkZXItbGVmdDpzb2xp
ZCAjQ0NDQ0NDIDEuMHB0O3BhZGRpbmc6MGluIDBpbiAwaW4gNi4wcHQ7bWFyZ2luLWxlZnQ6NC44
cHQ7bWFyZ2luLXJpZ2h0OjBpbiI+DQo8ZGl2Pg0KPGRpdj4NCjxwIGNsYXNzPSJNc29Ob3JtYWwi
IHN0eWxlPSJtc28tbWFyZ2luLXRvcC1hbHQ6YXV0bzttc28tbWFyZ2luLWJvdHRvbS1hbHQ6YXV0
byI+Jmd0O1tKb2VdIFllcyB0aGlzIGlzIGEgY29uY2VybiBhbmQgSSB0aGluayB5b3VyJm5ic3A7
aW50ZXJwcmV0YXRpb24gb2YgdGhlIGN1cnJlbnQgZG9jdW1lbnQgaXMgYWxzbyB2YWxpZC4mbmJz
cDsgVGhlcmUgbWF5IGJlIG1vcmUgdGhhbiBvbmUgaW1wbGVtZW50YXRpb24uJm5ic3A7IFNvIHdo
YXQgeW91IGltcGxlbWVudGVkIHdhczo8bzpwPjwvbzpwPjwvcD4NCjxwIGNsYXNzPSJNc29Ob3Jt
YWwiIHN0eWxlPSJtc28tbWFyZ2luLXRvcC1hbHQ6YXV0bzttc28tbWFyZ2luLWJvdHRvbS1hbHQ6
YXV0byI+Jmd0OyZuYnNwOzxvOnA+PC9vOnA+PC9wPg0KPHAgY2xhc3M9Ik1zb05vcm1hbCIgc3R5
bGU9Im1zby1tYXJnaW4tdG9wLWFsdDphdXRvO21zby1tYXJnaW4tYm90dG9tLWFsdDphdXRvIj4m
Z3Q7SU1DS1tqXSA9IFRMUy1QUkYoUy1JTUNLW2otMV0sICZxdW90O0lubmVyIE1ldGhvZHMgQ29t
cG91bmQgS2V5cyZxdW90OywmbmJzcDs8c3BhbiBzdHlsZT0iZm9udC1zaXplOjEwLjVwdDtjb2xv
cjojMkM0MzUzIj5JTVNLW2pdKSA9IFBfJmx0O2hhc2gmZ3Q7KFMtSU1DS1tqLTFdLCAmcXVvdDtJ
bm5lciBNZXRob2RzIENvbXBvdW5kIEtleXMmcXVvdDsgfCBJTVNLW2pdKTwvc3Bhbj48bzpwPjwv
bzpwPjwvcD4NCjxwIGNsYXNzPSJNc29Ob3JtYWwiIHN0eWxlPSJtc28tbWFyZ2luLXRvcC1hbHQ6
YXV0bzttc28tbWFyZ2luLWJvdHRvbS1hbHQ6YXV0byI+Jm5ic3A7PG86cD48L286cD48L3A+DQo8
cCBjbGFzcz0iTXNvTm9ybWFsIiBzdHlsZT0ibXNvLW1hcmdpbi10b3AtYWx0OmF1dG87bXNvLW1h
cmdpbi1ib3R0b20tYWx0OmF1dG8iPlllcywgdGhpcyBpcyB3aGF0IEkgaW1wbGVtZW50ZWQuIEFz
IHlvdSBtZW50aW9uZWQsIHRoZXJlIGFyZSBtdWx0aXBsZSBwb3NzaWJsZSBpbnRlcnByZXRhdGlv
bnMgb2YgdGhpcyBzaW5jZSB0aGUgVEVBUCB1c2FnZSBpcyBpbmNvcnJlY3QuIEhvd2V2ZXIsIG15
IGltcGxlbWVudGF0aW9uIGRvZXMgaW50ZXJvcA0KIHdpdGggYXQgbGVhc3QgMiBsYXJnZSB2ZW5k
b3IgaW1wbGVtZW50YXRpb25zLiBJZiB0aGUgaW1wbGVtZW50YXRpb25zIHdlcmUgdXNpbmcgZGlm
ZmVyZW50IGNhbGN1bGF0aW9ucyBoZXJlLCB0aGUgV2ktRmkvRXRoZXJuZXQgY29ubmVjdGlvbnMg
dGhhdCBkZXBlbmQgb24gdGhlIE1TSyB3b3VsZCBmYWlsLiBCdXQgc2luY2UgY29ubmVjdGlvbnMg
d29yaywgSSBjYW4gYXNzdW1lIHdlIGFyZSBhbGwgdXNpbmcgdGhlIHNhbWUgaW1wbGVtZW50YXRp
b24NCiBhbmQgYXJyaXZpbmcgYXQgdGhlIHNhbWUgTVNLLiBDaXNjbyBpcyBvbmUgb2YgdGhlIGlt
cGxlbWVudGF0aW9ucyB0aGF0IEkgaGF2ZSB0ZXN0ZWQgYWdhaW5zdCB3aGljaCBpcyB3aHkgSSB3
YXMgaG9waW5nIE9sZWcgbWF5IG9mZmVyIG1vcmUgY29udGV4dCBhcyB0byB3aGF0IGhlIGhhcyBz
ZWVuLjxvOnA+PC9vOnA+PC9wPg0KPHAgY2xhc3M9Ik1zb05vcm1hbCIgc3R5bGU9Im1zby1tYXJn
aW4tdG9wLWFsdDphdXRvO21zby1tYXJnaW4tYm90dG9tLWFsdDphdXRvIj4mbmJzcDs8bzpwPjwv
bzpwPjwvcD4NCjwvZGl2Pg0KPC9kaXY+DQo8L2Jsb2NrcXVvdGU+DQo8ZGl2Pg0KPHAgY2xhc3M9
Ik1zb05vcm1hbCI+W0pvZV0gSSBjYW4gaG9wZSBKb3VuaSBjYW4gY2hpbWUgaW4gb24gdGhpcyBh
cyB3ZWxsLiZuYnNwOyBJIHRoaW5rIHRoZSBvcmlnaW5hbCBpbnRlbnQgd2FzIHRvIG5vdCBpbmNs
dWRlIHRoZSBsZW5ndGggYXMgaXMgeW91ciBzdWdnZXN0aW9uLiZuYnNwOzxvOnA+PC9vOnA+PC9w
Pg0KPC9kaXY+DQo8ZGl2Pg0KPHAgY2xhc3M9Ik1zb05vcm1hbCI+PG86cD4mbmJzcDs8L286cD48
L3A+DQo8L2Rpdj4NCjxkaXY+DQo8cCBjbGFzcz0iTXNvTm9ybWFsIj4mbmJzcDs8bzpwPjwvbzpw
PjwvcD4NCjwvZGl2Pg0KPGJsb2NrcXVvdGUgc3R5bGU9ImJvcmRlcjpub25lO2JvcmRlci1sZWZ0
OnNvbGlkICNDQ0NDQ0MgMS4wcHQ7cGFkZGluZzowaW4gMGluIDBpbiA2LjBwdDttYXJnaW4tbGVm
dDo0LjhwdDttYXJnaW4tcmlnaHQ6MGluIj4NCjxkaXY+DQo8ZGl2Pg0KPHAgY2xhc3M9Ik1zb05v
cm1hbCIgc3R5bGU9Im1zby1tYXJnaW4tdG9wLWFsdDphdXRvO21zby1tYXJnaW4tYm90dG9tLWFs
dDphdXRvIj4mZ3Q7W0pvZV08c3BhbiBzdHlsZT0iZm9udC1zaXplOjEwLjVwdDtjb2xvcjojMkM0
MzUzIj4gRG9lcyB0aGUgcmV2aXNpb24gaW4gNTE2NyBtYXRjaCB5b3UgaW1wbGVtZW50YXRpb24g
KCBJIGRvbid0IHRoaW5rIEpvdW5pJ3MmbmJzcDtjb21tZW50IGNoYW5nZXMgdGhlIHVuZGVybHkm
bmJzcDtjYWxjdWxhdGlvbiwganVzdCBpdHMNCiByZXByZXNlbnRhdGlvbik/Jm5ic3A7PC9zcGFu
PjxvOnA+PC9vOnA+PC9wPg0KPHAgY2xhc3M9Ik1zb05vcm1hbCIgc3R5bGU9Im1zby1tYXJnaW4t
dG9wLWFsdDphdXRvO21zby1tYXJnaW4tYm90dG9tLWFsdDphdXRvIj4mbmJzcDs8bzpwPjwvbzpw
PjwvcD4NCjxwIGNsYXNzPSJNc29Ob3JtYWwiIHN0eWxlPSJtc28tbWFyZ2luLXRvcC1hbHQ6YXV0
bzttc28tbWFyZ2luLWJvdHRvbS1hbHQ6YXV0byI+SSBoYXZlIG5vdCBpbXBsZW1lbnRlZCB0aGlz
IHBvcnRpb24gb2YgdGhlIFJGQyBhcyBJIGZvdW5kIGl0IHRvbyB1bmNsZWFyIHRvIHdvcmsgd2l0
aC4gVGh1cyBJIGNhbuKAmXQgY29tbWVudCBvbiB3aGF0IGltcGxlbWVudGF0aW9ucyBtYXkgYmUg
ZG9pbmcuIEhvd2V2ZXIsIEkgYWdyZWUgd2l0aCB0aGUgY3VycmVudA0KIHJldmlzaW9uIGluIDUx
NjcgYXMgdGhlIG1vc3QgbmF0dXJhbCBpbnRlcnByZXRhdGlvbi4gSWYgb3RoZXJzIGhhdmUgaW1w
bGVtZW50ZWQgdGhpcyBwb3J0aW9uIG9mIHRoZSBSRkMgdGhlbiBjZXJ0YWlubHkgdGhlaXIgY29t
bWVudHMgd291bGQgYmUgd2VsY29tZS48bzpwPjwvbzpwPjwvcD4NCjxwIGNsYXNzPSJNc29Ob3Jt
YWwiIHN0eWxlPSJtc28tbWFyZ2luLXRvcC1hbHQ6YXV0bzttc28tbWFyZ2luLWJvdHRvbS1hbHQ6
YXV0byI+PG86cD4mbmJzcDs8L286cD48L3A+DQo8L2Rpdj4NCjwvZGl2Pg0KPC9ibG9ja3F1b3Rl
Pg0KPGJsb2NrcXVvdGUgc3R5bGU9ImJvcmRlcjpub25lO2JvcmRlci1sZWZ0OnNvbGlkICNDQ0ND
Q0MgMS4wcHQ7cGFkZGluZzowaW4gMGluIDBpbiA2LjBwdDttYXJnaW4tbGVmdDo0LjhwdDttYXJn
aW4tcmlnaHQ6MGluIj4NCjxkaXY+DQo8ZGl2Pg0KPHAgY2xhc3M9Ik1zb05vcm1hbCIgc3R5bGU9
Im1zby1tYXJnaW4tdG9wLWFsdDphdXRvO21zby1tYXJnaW4tYm90dG9tLWFsdDphdXRvIj5CeSB0
aGUgd2F5LCB3ZeKAmXZlIGRyb3BwZWQgdGhlIEVNVSBncm91cCBvbiBvdXIgcmVwbGllcyBoZXJl
IOKAkyBub3Qgc3VyZSBpZiBpbnRlbnRpb25hbCBvciBub3QuPG86cD48L286cD48L3A+DQo8cCBj
bGFzcz0iTXNvTm9ybWFsIiBzdHlsZT0ibXNvLW1hcmdpbi10b3AtYWx0OmF1dG87bXNvLW1hcmdp
bi1ib3R0b20tYWx0OmF1dG8iPiZuYnNwOzxvOnA+PC9vOnA+PC9wPg0KPHAgY2xhc3M9Ik1zb05v
cm1hbCIgc3R5bGU9Im1zby1tYXJnaW4tdG9wLWFsdDphdXRvO21zby1tYXJnaW4tYm90dG9tLWFs
dDphdXRvIj5Kb3JnZSBWZXJnYXJhPG86cD48L286cD48L3A+DQo8cCBjbGFzcz0iTXNvTm9ybWFs
IiBzdHlsZT0ibXNvLW1hcmdpbi10b3AtYWx0OmF1dG87bXNvLW1hcmdpbi1ib3R0b20tYWx0OmF1
dG8iPiZuYnNwOzxvOnA+PC9vOnA+PC9wPg0KPGRpdiBzdHlsZT0iYm9yZGVyOm5vbmU7Ym9yZGVy
LXRvcDpzb2xpZCAjRTFFMUUxIDEuMHB0O3BhZGRpbmc6My4wcHQgMGluIDBpbiAwaW4iPg0KPHAg
Y2xhc3M9Ik1zb05vcm1hbCIgc3R5bGU9Im1zby1tYXJnaW4tdG9wLWFsdDphdXRvO21zby1tYXJn
aW4tYm90dG9tLWFsdDphdXRvIj48Yj5Gcm9tOjwvYj4gSm9zZXBoIFNhbG93ZXkgJmx0OzxhIGhy
ZWY9Im1haWx0bzpqb2VAc2Fsb3dleS5uZXQiIHRhcmdldD0iX2JsYW5rIj5qb2VAc2Fsb3dleS5u
ZXQ8L2E+Jmd0Ow0KPGJyPg0KPGI+U2VudDo8L2I+IFdlZG5lc2RheSwgT2N0b2JlciAyMSwgMjAy
MCA0OjM2IFBNPGJyPg0KPGI+VG86PC9iPiBKb3JnZSBWZXJnYXJhICZsdDs8YSBocmVmPSJtYWls
dG86am92ZXJnYXJAbWljcm9zb2Z0LmNvbSIgdGFyZ2V0PSJfYmxhbmsiPmpvdmVyZ2FyQG1pY3Jv
c29mdC5jb208L2E+Jmd0Ozxicj4NCjxiPlN1YmplY3Q6PC9iPiBSZTogUHJvcG9zZWQgcmVzb2x1
dGlvbiBmb3IgVEVBUCBlcnJhdGEgZm9yIDUxMjg8bzpwPjwvbzpwPjwvcD4NCjwvZGl2Pg0KPHAg
Y2xhc3M9Ik1zb05vcm1hbCIgc3R5bGU9Im1zby1tYXJnaW4tdG9wLWFsdDphdXRvO21zby1tYXJn
aW4tYm90dG9tLWFsdDphdXRvIj4mbmJzcDs8bzpwPjwvbzpwPjwvcD4NCjxkaXY+DQo8ZGl2Pg0K
PHAgY2xhc3M9Ik1zb05vcm1hbCIgc3R5bGU9Im1zby1tYXJnaW4tdG9wLWFsdDphdXRvO21zby1t
YXJnaW4tYm90dG9tLWFsdDphdXRvIj4mbmJzcDs8bzpwPjwvbzpwPjwvcD4NCjwvZGl2Pg0KPHAg
Y2xhc3M9Ik1zb05vcm1hbCIgc3R5bGU9Im1zby1tYXJnaW4tdG9wLWFsdDphdXRvO21zby1tYXJn
aW4tYm90dG9tLWFsdDphdXRvIj4mbmJzcDs8bzpwPjwvbzpwPjwvcD4NCjxkaXY+DQo8ZGl2Pg0K
PHAgY2xhc3M9Ik1zb05vcm1hbCIgc3R5bGU9Im1zby1tYXJnaW4tdG9wLWFsdDphdXRvO21zby1t
YXJnaW4tYm90dG9tLWFsdDphdXRvIj5PbiBXZWQsIE9jdCAyMSwgMjAyMCBhdCAzOjIwIFBNIEpv
cmdlIFZlcmdhcmEgJmx0OzxhIGhyZWY9Im1haWx0bzpqb3ZlcmdhckBtaWNyb3NvZnQuY29tIiB0
YXJnZXQ9Il9ibGFuayI+am92ZXJnYXJAbWljcm9zb2Z0LmNvbTwvYT4mZ3Q7IHdyb3RlOjxvOnA+
PC9vOnA+PC9wPg0KPC9kaXY+DQo8YmxvY2txdW90ZSBzdHlsZT0iYm9yZGVyOm5vbmU7Ym9yZGVy
LWxlZnQ6c29saWQgI0NDQ0NDQyAxLjBwdDtwYWRkaW5nOjBpbiAwaW4gMGluIDYuMHB0O21hcmdp
bi1sZWZ0OjQuOHB0O21hcmdpbi10b3A6NS4wcHQ7bWFyZ2luLXJpZ2h0OjBpbjttYXJnaW4tYm90
dG9tOjUuMHB0Ij4NCjxkaXY+DQo8ZGl2Pg0KPHAgY2xhc3M9Ik1zb05vcm1hbCIgc3R5bGU9Im1z
by1tYXJnaW4tdG9wLWFsdDphdXRvO21zby1tYXJnaW4tYm90dG9tLWFsdDphdXRvIj5JbiB0aGVv
cnkgSSBhZ3JlZSB0aGlzIGlzIGEgcG9zc2libGUgcmVzb2x1dGlvbi4gSG93ZXZlciwgdGhpcyBk
b2VzbuKAmXQgbWF0Y2ggYW55IG9mIHRoZSBjdXJyZW50IFRFQVAgaW1wbGVtZW50YXRpb25zIHRo
YXQgSSBhbSBhd2FyZSBvZi4gUGVyaGFwcyBPbGVnIGNhbiB3ZWlnaCBpbiBhcyB3ZWxsIGluIHRl
cm1zDQogb2Ygd2hhdCBoZeKAmXMgc2Vlbi48bzpwPjwvbzpwPjwvcD4NCjxwIGNsYXNzPSJNc29O
b3JtYWwiIHN0eWxlPSJtc28tbWFyZ2luLXRvcC1hbHQ6YXV0bzttc28tbWFyZ2luLWJvdHRvbS1h
bHQ6YXV0byI+Jm5ic3A7PG86cD48L286cD48L3A+DQo8cCBjbGFzcz0iTXNvTm9ybWFsIiBzdHls
ZT0ibXNvLW1hcmdpbi10b3AtYWx0OmF1dG87bXNvLW1hcmdpbi1ib3R0b20tYWx0OmF1dG8iPkkg
YmVsaWV2ZSBhbGwgY3VycmVudCBpbXBsZW1lbnRhdGlvbnMgdHJlYXQgNjAgYXMgdGhlIGRlc2ly
ZWQgb3V0cHV0IGxlbmd0aCB3aXRob3V0IHRyZWF0aW5nIGFzIGEgc2VlZC4gSW4gdGVybXMgb2Yg
UF8mbHQ7aGFzaCZndDssIHRoaXMgbWVhbnMgaW1wbGVtZW50YXRpb25zIGFyZSBwZXJmb3JtaW5n
IHRoZSBjYWxjdWxhdGlvbg0KIHdpdGhvdXQgYSBzZWVkLjxvOnA+PC9vOnA+PC9wPg0KPHAgY2xh
c3M9Ik1zb05vcm1hbCIgc3R5bGU9Im1zby1tYXJnaW4tdG9wLWFsdDphdXRvO21zby1tYXJnaW4t
Ym90dG9tLWFsdDphdXRvIj4mbmJzcDs8bzpwPjwvbzpwPjwvcD4NCjxwIGNsYXNzPSJNc29Ob3Jt
YWwiIHN0eWxlPSJtc28tbWFyZ2luLXRvcC1hbHQ6YXV0bzttc28tbWFyZ2luLWJvdHRvbS1hbHQ6
YXV0byI+UkZDIDUyNDYgZGVmaW5lcyB0aGUgVExTIDEuMiBQUkYgYXM6PG86cD48L286cD48L3A+
DQo8cCBjbGFzcz0iTXNvTm9ybWFsIiBzdHlsZT0ibXNvLW1hcmdpbi10b3AtYWx0OmF1dG87bXNv
LW1hcmdpbi1ib3R0b20tYWx0OmF1dG8iPlBSRihzZWNyZXQsIGxhYmVsLCBzZWVkKSA9IFBfJmx0
O2hhc2gmZ3Q7KHNlY3JldCwgbGFiZWwgKyBzZWVkKTxvOnA+PC9vOnA+PC9wPg0KPHAgY2xhc3M9
Ik1zb05vcm1hbCIgc3R5bGU9Im1zby1tYXJnaW4tdG9wLWFsdDphdXRvO21zby1tYXJnaW4tYm90
dG9tLWFsdDphdXRvIj4mbmJzcDs8bzpwPjwvbzpwPjwvcD4NCjxwIGNsYXNzPSJNc29Ob3JtYWwi
IHN0eWxlPSJtc28tbWFyZ2luLXRvcC1hbHQ6YXV0bzttc28tbWFyZ2luLWJvdHRvbS1hbHQ6YXV0
byI+U28gdGhlIGNhbGN1bGF0aW9uIGltcGxlbWVudGF0aW9ucyBhcmUgY3VycmVudGx5IHBlcmZv
cm1pbmcgd2l0aCBhbiBlbXB0eSBzZWVkIGVuZHMgdXAgYXM6PG86cD48L286cD48L3A+DQo8cCBj
bGFzcz0iTXNvTm9ybWFsIiBzdHlsZT0ibXNvLW1hcmdpbi10b3AtYWx0OmF1dG87bXNvLW1hcmdp
bi1ib3R0b20tYWx0OmF1dG8iPlBfJmx0O2hhc2gmZ3Q7KHNlY3JldCwgbGFiZWwpPG86cD48L286
cD48L3A+DQo8cCBjbGFzcz0iTXNvTm9ybWFsIiBzdHlsZT0ibXNvLW1hcmdpbi10b3AtYWx0OmF1
dG87bXNvLW1hcmdpbi1ib3R0b20tYWx0OmF1dG8iPiZuYnNwOzxvOnA+PC9vOnA+PC9wPg0KPHAg
Y2xhc3M9Ik1zb05vcm1hbCIgc3R5bGU9Im1zby1tYXJnaW4tdG9wLWFsdDphdXRvO21zby1tYXJn
aW4tYm90dG9tLWFsdDphdXRvIj5Ob3RlIHRoYXQgaW4gUkZDIDUyOTUsIHRoZSBsZW5ndGggKmlz
KiBleHBsaWNpdGx5IG1lbnRpb25lZCBhcyBiZWluZyBjb25jYXRlbmF0ZWQgd2l0aCB0aGUgbGFi
ZWw8bzpwPjwvbzpwPjwvcD4NCjxwIGNsYXNzPSJNc29Ob3JtYWwiIHN0eWxlPSJtc28tbWFyZ2lu
LXRvcC1hbHQ6YXV0bzttc28tbWFyZ2luLWJvdHRvbS1hbHQ6YXV0byI+VVNSSyA9IEtERihFTVNL
LCBrZXkgbGFiZWwgfCAmcXVvdDtcMCZxdW90OyB8IG9wdGlvbmFsIGRhdGEgfCBsZW5ndGgpPG86
cD48L286cD48L3A+DQo8cCBjbGFzcz0iTXNvTm9ybWFsIiBzdHlsZT0ibXNvLW1hcmdpbi10b3At
YWx0OmF1dG87bXNvLW1hcmdpbi1ib3R0b20tYWx0OmF1dG8iPiZuYnNwOzxvOnA+PC9vOnA+PC9w
Pg0KPHAgY2xhc3M9Ik1zb05vcm1hbCIgc3R5bGU9Im1zby1tYXJnaW4tdG9wLWFsdDphdXRvO21z
by1tYXJnaW4tYm90dG9tLWFsdDphdXRvIj5SRkMgNTI5NSBpcyBtZW50aW9uZWQgZWFybGllciBp
biB0aGUgVEVBUCBSRkMsIGluIHRoZSBzZWN0aW9uIGNvdmVyZWQgYnkgZXJyYXRhIDUxMjcuICpI
b3dldmVyKiBpdCBpcyBub3QgbWVudGlvbmVkIGluIHRoaXMgcG9ydGlvbiBvZiB0aGUgUkZDLiBT
aW5jZSB0aGlzIGNhbGN1bGF0aW9uIGlzIG5vdCBvbg0KIGFuIEVNU0ssIEkgZG8gbm90IGJlbGll
dmUgUkZDIDIzOTUgYXBwbGllcyBhbmQgdGhpcyBpcyBsaWtlbHkgd2h5IGltcGxlbWVudGF0aW9u
cyB3ZW50IHdpdGggdGhlIHNlZWRsZXNzIFBfJmx0O2hhc2gmZ3Q7KHNlY3JldCwgbGFiZWwpIGNh
bGN1bGF0aW9uIGluc3RlYWQuPG86cD48L286cD48L3A+DQo8cCBjbGFzcz0iTXNvTm9ybWFsIiBz
dHlsZT0ibXNvLW1hcmdpbi10b3AtYWx0OmF1dG87bXNvLW1hcmdpbi1ib3R0b20tYWx0OmF1dG8i
PiZuYnNwOzxvOnA+PC9vOnA+PC9wPg0KPHAgY2xhc3M9Ik1zb05vcm1hbCIgc3R5bGU9Im1zby1t
YXJnaW4tdG9wLWFsdDphdXRvO21zby1tYXJnaW4tYm90dG9tLWFsdDphdXRvIj5JcyB0aGVyZSBj
b25jZXJuIGFib3V0IHVwZGF0aW5nIHRoZSBSRkMgaW4gYSB3YXkgdGhhdCBicmVha3MgZXhpc3Rp
bmcgaW1wbGVtZW50YXRpb25zPzxvOnA+PC9vOnA+PC9wPg0KPHAgY2xhc3M9Ik1zb05vcm1hbCIg
c3R5bGU9Im1zby1tYXJnaW4tdG9wLWFsdDphdXRvO21zby1tYXJnaW4tYm90dG9tLWFsdDphdXRv
Ij4mbmJzcDs8bzpwPjwvbzpwPjwvcD4NCjwvZGl2Pg0KPC9kaXY+DQo8L2Jsb2NrcXVvdGU+DQo8
ZGl2Pg0KPHAgY2xhc3M9Ik1zb05vcm1hbCIgc3R5bGU9Im1zby1tYXJnaW4tdG9wLWFsdDphdXRv
O21zby1tYXJnaW4tYm90dG9tLWFsdDphdXRvIj5bSm9lXSBZZXMgdGhpcyBpcyBhIGNvbmNlcm4g
YW5kIEkgdGhpbmsgeW91ciZuYnNwO2ludGVycHJldGF0aW9uIG9mIHRoZSBjdXJyZW50IGRvY3Vt
ZW50IGlzIGFsc28gdmFsaWQuJm5ic3A7IFRoZXJlIG1heSBiZSBtb3JlIHRoYW4gb25lIGltcGxl
bWVudGF0aW9uLiZuYnNwOyBTbyB3aGF0IHlvdSBpbXBsZW1lbnRlZCB3YXM6PG86cD48L286cD48
L3A+DQo8L2Rpdj4NCjxkaXY+DQo8cCBjbGFzcz0iTXNvTm9ybWFsIiBzdHlsZT0ibXNvLW1hcmdp
bi10b3AtYWx0OmF1dG87bXNvLW1hcmdpbi1ib3R0b20tYWx0OmF1dG8iPiZuYnNwOzxvOnA+PC9v
OnA+PC9wPg0KPC9kaXY+DQo8ZGl2Pg0KPHAgY2xhc3M9Ik1zb05vcm1hbCIgc3R5bGU9Im1zby1t
YXJnaW4tdG9wLWFsdDphdXRvO21zby1tYXJnaW4tYm90dG9tLWFsdDphdXRvIj5JTUNLW2pdID0g
VExTLVBSRihTLUlNQ0tbai0xXSwgJnF1b3Q7SW5uZXIgTWV0aG9kcyBDb21wb3VuZCBLZXlzJnF1
b3Q7LCZuYnNwOzxzcGFuIHN0eWxlPSJmb250LXNpemU6MTAuNXB0O2NvbG9yOiMyQzQzNTMiPklN
U0tbal0pID0gUF8mbHQ7aGFzaCZndDsoUy1JTUNLW2otMV0sICZxdW90O0lubmVyIE1ldGhvZHMg
Q29tcG91bmQgS2V5cyZxdW90OyB8IElNU0tbal0pPC9zcGFuPjxvOnA+PC9vOnA+PC9wPg0KPC9k
aXY+DQo8ZGl2Pg0KPHAgY2xhc3M9Ik1zb05vcm1hbCIgc3R5bGU9Im1zby1tYXJnaW4tdG9wLWFs
dDphdXRvO21zby1tYXJnaW4tYm90dG9tLWFsdDphdXRvIj4mbmJzcDs8bzpwPjwvbzpwPjwvcD4N
CjwvZGl2Pg0KPGRpdj4NCjxwIGNsYXNzPSJNc29Ob3JtYWwiIHN0eWxlPSJtc28tbWFyZ2luLXRv
cC1hbHQ6YXV0bzttc28tbWFyZ2luLWJvdHRvbS1hbHQ6YXV0byI+dGFrZW4gb3V0IHRvIDYwIGJ5
dGVzLiZuYnNwOyBUaGUgcHJvYmxlbSBpcyB0aGF0IHRoZSBURUFQIHNwZWMgcmVmZXJlbmNlcyBh
IFRMUy1QUkYgaW4gYSB3YXkgdGhhdCBpdCBkb2VzIG5vdCBkZWZpbmUuJm5ic3A7IEkgdGhpbmsg
dGhlIGVycmF0YSBwb2ludHMgb3V0IHRoZSBkZWZpbml0aW9uIHRoYXQgc2hvdWxkIGJlIHVzZWQ6
PG86cD48L286cD48L3A+DQo8L2Rpdj4NCjxkaXY+DQo8cCBjbGFzcz0iTXNvTm9ybWFsIiBzdHls
ZT0ibXNvLW1hcmdpbi10b3AtYWx0OmF1dG87bXNvLW1hcmdpbi1ib3R0b20tYWx0OmF1dG8iPiZu
YnNwOzxvOnA+PC9vOnA+PC9wPg0KPC9kaXY+DQo8ZGl2Pg0KPHAgY2xhc3M9Ik1zb05vcm1hbCIg
c3R5bGU9Im1zby1tYXJnaW4tdG9wLWFsdDphdXRvO21zby1tYXJnaW4tYm90dG9tLWFsdDphdXRv
Ij5QUkYoc2VjcmV0LCBsYWJlbCwgc2VlZCkgPSBQXyZsdDtoYXNoJmd0OyhzZWNyZXQsIGxhYmVs
ICsgc2VlZCk8bzpwPjwvbzpwPjwvcD4NCjwvZGl2Pg0KPGRpdj4NCjxwIGNsYXNzPSJNc29Ob3Jt
YWwiIHN0eWxlPSJtc28tbWFyZ2luLXRvcC1hbHQ6YXV0bzttc28tbWFyZ2luLWJvdHRvbS1hbHQ6
YXV0byI+Jm5ic3A7PG86cD48L286cD48L3A+DQo8L2Rpdj4NCjxkaXY+DQo8cCBjbGFzcz0iTXNv
Tm9ybWFsIiBzdHlsZT0ibXNvLW1hcmdpbi10b3AtYWx0OmF1dG87bXNvLW1hcmdpbi1ib3R0b20t
YWx0OmF1dG8iPlRoYXQgZG9lcyBub3QgaW5jbHVkZSBsZW5ndGggc28gdGhlIDYwIGluIHRoZSBv
cmlnaW5hbCBkZWZpbml0aW9uJm5ic3A7aXMgYW1iaWd1b3VzLiZuYnNwOyAmbmJzcDtUaGUgbmV3
IHRleHQgd291bGQgdGhlbiBiZSBzb21ldGhpbmcgbGlrZTo8bzpwPjwvbzpwPjwvcD4NCjwvZGl2
Pg0KPGRpdj4NCjxwIGNsYXNzPSJNc29Ob3JtYWwiIHN0eWxlPSJtc28tbWFyZ2luLXRvcC1hbHQ6
YXV0bzttc28tbWFyZ2luLWJvdHRvbS1hbHQ6YXV0byI+Jm5ic3A7PG86cD48L286cD48L3A+DQo8
L2Rpdj4NCjxkaXY+DQo8cCBjbGFzcz0iTXNvTm9ybWFsIiBzdHlsZT0ibXNvLW1hcmdpbi10b3At
YWx0OmF1dG87bXNvLW1hcmdpbi1ib3R0b20tYWx0OmF1dG8iPklNQ0tbal0gPSBUTFMtUFJGKFMt
SU1DS1tqLTFdLCAmcXVvdDtJbm5lciBNZXRob2RzIENvbXBvdW5kIEtleXMmcXVvdDssJm5ic3A7
PHNwYW4gc3R5bGU9ImZvbnQtc2l6ZToxMC41cHQ7Y29sb3I6IzJDNDM1MyI+SU1TS1tqXSkmbmJz
cDsgdG8gZ2VuZXJhdGUgYSBsZW5ndGggb2YgNjAgYnl0ZXM8L3NwYW4+PG86cD48L286cD48L3A+
DQo8L2Rpdj4NCjxkaXY+DQo8cCBjbGFzcz0iTXNvTm9ybWFsIiBzdHlsZT0ibXNvLW1hcmdpbi10
b3AtYWx0OmF1dG87bXNvLW1hcmdpbi1ib3R0b20tYWx0OmF1dG8iPiZuYnNwOzxvOnA+PC9vOnA+
PC9wPg0KPC9kaXY+DQo8ZGl2Pg0KPHAgY2xhc3M9Ik1zb05vcm1hbCIgc3R5bGU9Im1zby1tYXJn
aW4tdG9wLWFsdDphdXRvO21zby1tYXJnaW4tYm90dG9tLWFsdDphdXRvIj48c3BhbiBzdHlsZT0i
Zm9udC1zaXplOjEwLjVwdDtjb2xvcjojMkM0MzUzIj5Eb2VzIHRoZSByZXZpc2lvbiBpbiA1MTY3
IG1hdGNoIHlvdSBpbXBsZW1lbnRhdGlvbiAoIEkgZG9uJ3QgdGhpbmsgSm91bmkncyZuYnNwO2Nv
bW1lbnQgY2hhbmdlcyB0aGUgdW5kZXJseSZuYnNwO2NhbGN1bGF0aW9uLCBqdXN0IGl0cyByZXBy
ZXNlbnRhdGlvbik/Jm5ic3A7PC9zcGFuPjxvOnA+PC9vOnA+PC9wPg0KPC9kaXY+DQo8ZGl2Pg0K
PHAgY2xhc3M9Ik1zb05vcm1hbCIgc3R5bGU9Im1zby1tYXJnaW4tdG9wLWFsdDphdXRvO21zby1t
YXJnaW4tYm90dG9tLWFsdDphdXRvIj4mbmJzcDs8bzpwPjwvbzpwPjwvcD4NCjwvZGl2Pg0KPGRp
dj4NCjxwIGNsYXNzPSJNc29Ob3JtYWwiIHN0eWxlPSJtc28tbWFyZ2luLXRvcC1hbHQ6YXV0bztt
c28tbWFyZ2luLWJvdHRvbS1hbHQ6YXV0byI+Jm5ic3A7PG86cD48L286cD48L3A+DQo8L2Rpdj4N
CjxkaXY+DQo8cCBjbGFzcz0iTXNvTm9ybWFsIiBzdHlsZT0ibXNvLW1hcmdpbi10b3AtYWx0OmF1
dG87bXNvLW1hcmdpbi1ib3R0b20tYWx0OmF1dG8iPiZuYnNwOzxvOnA+PC9vOnA+PC9wPg0KPC9k
aXY+DQo8ZGl2Pg0KPHAgY2xhc3M9Ik1zb05vcm1hbCIgc3R5bGU9Im1zby1tYXJnaW4tdG9wLWFs
dDphdXRvO21zby1tYXJnaW4tYm90dG9tLWFsdDphdXRvIj4mbmJzcDs8bzpwPjwvbzpwPjwvcD4N
CjwvZGl2Pg0KPGRpdj4NCjxwIGNsYXNzPSJNc29Ob3JtYWwiIHN0eWxlPSJtc28tbWFyZ2luLXRv
cC1hbHQ6YXV0bzttc28tbWFyZ2luLWJvdHRvbS1hbHQ6YXV0byI+Jm5ic3A7PG86cD48L286cD48
L3A+DQo8L2Rpdj4NCjxibG9ja3F1b3RlIHN0eWxlPSJib3JkZXI6bm9uZTtib3JkZXItbGVmdDpz
b2xpZCAjQ0NDQ0NDIDEuMHB0O3BhZGRpbmc6MGluIDBpbiAwaW4gNi4wcHQ7bWFyZ2luLWxlZnQ6
NC44cHQ7bWFyZ2luLXRvcDo1LjBwdDttYXJnaW4tcmlnaHQ6MGluO21hcmdpbi1ib3R0b206NS4w
cHQiPg0KPGRpdj4NCjxkaXY+DQo8cCBjbGFzcz0iTXNvTm9ybWFsIiBzdHlsZT0ibXNvLW1hcmdp
bi10b3AtYWx0OmF1dG87bXNvLW1hcmdpbi1ib3R0b20tYWx0OmF1dG8iPkpvcmdlIFZlcmdhcmE8
bzpwPjwvbzpwPjwvcD4NCjxwIGNsYXNzPSJNc29Ob3JtYWwiIHN0eWxlPSJtc28tbWFyZ2luLXRv
cC1hbHQ6YXV0bzttc28tbWFyZ2luLWJvdHRvbS1hbHQ6YXV0byI+Jm5ic3A7PG86cD48L286cD48
L3A+DQo8ZGl2IHN0eWxlPSJib3JkZXI6bm9uZTtib3JkZXItdG9wOnNvbGlkICNFMUUxRTEgMS4w
cHQ7cGFkZGluZzozLjBwdCAwaW4gMGluIDBpbiI+DQo8cCBjbGFzcz0iTXNvTm9ybWFsIiBzdHls
ZT0ibXNvLW1hcmdpbi10b3AtYWx0OmF1dG87bXNvLW1hcmdpbi1ib3R0b20tYWx0OmF1dG8iPjxi
PkZyb206PC9iPiBKb3NlcGggU2Fsb3dleSAmbHQ7PGEgaHJlZj0ibWFpbHRvOmpvZUBzYWxvd2V5
Lm5ldCIgdGFyZ2V0PSJfYmxhbmsiPmpvZUBzYWxvd2V5Lm5ldDwvYT4mZ3Q7DQo8YnI+DQo8Yj5T
ZW50OjwvYj4gV2VkbmVzZGF5LCBPY3RvYmVyIDIxLCAyMDIwIDI6MzQgUE08YnI+DQo8Yj5Ubzo8
L2I+IEVNVSBXRyAmbHQ7PGEgaHJlZj0ibWFpbHRvOmVtdUBpZXRmLm9yZyIgdGFyZ2V0PSJfYmxh
bmsiPmVtdUBpZXRmLm9yZzwvYT4mZ3Q7OyBKb3VuaSBNYWxpbmVuICZsdDs8YSBocmVmPSJtYWls
dG86akB3MS5maSIgdGFyZ2V0PSJfYmxhbmsiPmpAdzEuZmk8L2E+Jmd0OzsgSm9yZ2UgVmVyZ2Fy
YSAmbHQ7PGEgaHJlZj0ibWFpbHRvOmpvdmVyZ2FyQG1pY3Jvc29mdC5jb20iIHRhcmdldD0iX2Js
YW5rIj5qb3ZlcmdhckBtaWNyb3NvZnQuY29tPC9hPiZndDs7IE9sZWcNCiBQZWthciAob2xwZWth
cikgJmx0OzxhIGhyZWY9Im1haWx0bzpvbHBla2FyQGNpc2NvLmNvbSIgdGFyZ2V0PSJfYmxhbmsi
Pm9scGVrYXJAY2lzY28uY29tPC9hPiZndDs8YnI+DQo8Yj5TdWJqZWN0OjwvYj4gUHJvcG9zZWQg
cmVzb2x1dGlvbiBmb3IgVEVBUCBlcnJhdGEgZm9yIDUxMjg8bzpwPjwvbzpwPjwvcD4NCjwvZGl2
Pg0KPHAgY2xhc3M9Ik1zb05vcm1hbCIgc3R5bGU9Im1zby1tYXJnaW4tdG9wLWFsdDphdXRvO21z
by1tYXJnaW4tYm90dG9tLWFsdDphdXRvIj4mbmJzcDs8bzpwPjwvbzpwPjwvcD4NCjxkaXY+DQo8
cCBjbGFzcz0iTXNvTm9ybWFsIiBzdHlsZT0ibXNvLW1hcmdpbi10b3AtYWx0OmF1dG87bXNvLW1h
cmdpbi1ib3R0b20tYWx0OmF1dG8iPkVycmF0YSA1MTI4OiZuYnNwOzxhIGhyZWY9Imh0dHBzOi8v
bmFtMDYuc2FmZWxpbmtzLnByb3RlY3Rpb24ub3V0bG9vay5jb20vP3VybD1odHRwcyUzQSUyRiUy
Rnd3dy5yZmMtZWRpdG9yLm9yZyUyRmVycmF0YSUyRmVpZDUxMjgmYW1wO2RhdGE9MDQlN0MwMSU3
Q2pvdmVyZ2FyJTQwbWljcm9zb2Z0LmNvbSU3QzE2MDdmNWYwNWFiNjRjMTEyMjgxMDhkODc2YWIw
MzA0JTdDNzJmOTg4YmY4NmYxNDFhZjkxYWIyZDdjZDAxMWRiNDclN0MxJTdDMCU3QzYzNzM4OTgy
NDE1MDc5MjUzNyU3Q1Vua25vd24lN0NUV0ZwYkdac2IzZDhleUpXSWpvaU1DNHdMakF3TURBaUxD
SlFJam9pVjJsdU16SWlMQ0pCVGlJNklrMWhhV3dpTENKWFZDSTZNbjAlM0QlN0MxMDAwJmFtcDtz
ZGF0YT0lMkZZNzdnZDUlMkJablJQSFQlMkJrcTJLa1RKUGxrSzJoSXUlMkZmRmVqSGxqOWU3Q1El
M0QmYW1wO3Jlc2VydmVkPTAiIHRhcmdldD0iX2JsYW5rIj5odHRwczovL3d3dy5yZmMtZWRpdG9y
Lm9yZy9lcnJhdGEvZWlkNTEyODwvYT48bzpwPjwvbzpwPjwvcD4NCjxkaXY+DQo8cCBjbGFzcz0i
TXNvTm9ybWFsIiBzdHlsZT0ibXNvLW1hcmdpbi10b3AtYWx0OmF1dG87bXNvLW1hcmdpbi1ib3R0
b20tYWx0OmF1dG8iPlByb3Bvc2VkIFN0YXRlOiBWZXJpZmllZDxvOnA+PC9vOnA+PC9wPg0KPC9k
aXY+DQo8ZGl2Pg0KPHAgY2xhc3M9Ik1zb05vcm1hbCIgc3R5bGU9Im1zby1tYXJnaW4tdG9wLWFs
dDphdXRvO21zby1tYXJnaW4tYm90dG9tLWFsdDphdXRvIj5SZXZpc2lvbjo8bzpwPjwvbzpwPjwv
cD4NCjwvZGl2Pg0KPGRpdj4NCjxwIGNsYXNzPSJNc29Ob3JtYWwiIHN0eWxlPSJtc28tbWFyZ2lu
LXRvcC1hbHQ6YXV0bzttc28tbWFyZ2luLWJvdHRvbS1hbHQ6YXV0byI+Jm5ic3A7PG86cD48L286
cD48L3A+DQo8L2Rpdj4NCjxkaXY+DQo8cCBjbGFzcz0iTXNvTm9ybWFsIiBzdHlsZT0ibXNvLW1h
cmdpbi10b3AtYWx0OmF1dG87bXNvLW1hcmdpbi1ib3R0b20tYWx0OmF1dG8iPlNlY3Rpb24gNS4y
LiBzYXlzPG86cD48L286cD48L3A+DQo8L2Rpdj4NCjxkaXY+DQo8cCBzdHlsZT0ibXNvLW1hcmdp
bi10b3AtYWx0OjUuMHB0O21hcmdpbi1yaWdodDozLjc1cHQ7bWFyZ2luLWJvdHRvbTo3LjVwdDtt
YXJnaW4tbGVmdDozLjc1cHQiPg0KPGJyPg0KSU1DS1tqXSA9IFRMUy1QUkYoUy1JTUNLW2otMV0s
ICZxdW90O0lubmVyIE1ldGhvZHMgQ29tcG91bmQgS2V5cyZxdW90Oyw8YnI+DQombmJzcDsgJm5i
c3A7ICZuYnNwOyAmbmJzcDsgJm5ic3A7ICZuYnNwOyAmbmJzcDsgJm5ic3A7IElNU0tbal0sIDYw
KTxicj4NCjxicj4NCkl0IHNob3VsZCBzYXk6PGJyPg0KPGJyPg0KSU1DS1tqXSA9IFRMUy1QUkYo
Uy1JTUNLW2otMV0sICZxdW90O0lubmVyIE1ldGhvZHMgQ29tcG91bmQgS2V5cyZxdW90OywmbmJz
cDs8c3BhbiBzdHlsZT0iZm9udC1zaXplOjEwLjVwdDtmb250LWZhbWlseTomcXVvdDtBcmlhbCZx
dW90OyxzYW5zLXNlcmlmO2NvbG9yOiMyQzQzNTMiPklNU0tbal0gfCA2MCk8L3NwYW4+PG86cD48
L286cD48L3A+DQo8cCBzdHlsZT0ibXNvLW1hcmdpbi10b3AtYWx0OjUuMHB0O21hcmdpbi1yaWdo
dDozLjc1cHQ7bWFyZ2luLWJvdHRvbTo3LjVwdDttYXJnaW4tbGVmdDozLjc1cHQiPg0KPHNwYW4g
c3R5bGU9ImZvbnQtc2l6ZToxMC41cHQ7Zm9udC1mYW1pbHk6JnF1b3Q7QXJpYWwmcXVvdDssc2Fu
cy1zZXJpZjtjb2xvcjojMkM0MzUzIj5Ob3RlOiZuYnNwOyZuYnNwOzwvc3Bhbj48bzpwPjwvbzpw
PjwvcD4NCjxwIGNsYXNzPSJNc29Ob3JtYWwiIHN0eWxlPSJtc28tbWFyZ2luLXRvcC1hbHQ6YXV0
bzttc28tbWFyZ2luLWJvdHRvbS1hbHQ6YXV0byI+QWNjb3JkaW5nIHRvPGJyPg0KPGJyPg0KUkZD
NTI0NiBUaGUgVHJhbnNwb3J0IExheWVyIFNlY3VyaXR5IChUTFMpIFByb3RvY29sIFZlcnNpb24g
MS4yPGJyPg0KPGJyPg0KNS4gSE1BQyBhbmQgdGhlIFBzZXVkb3JhbmRvbSBGdW5jdGlvbjxicj4N
Cjxicj4NCiZxdW90O1RMUydzIFBSRiBpcyBjcmVhdGVkIGJ5IGFwcGx5aW5nIFBfaGFzaCB0byB0
aGUgc2VjcmV0IGFzOjxicj4NCjxicj4NClBSRihzZWNyZXQsIGxhYmVsLCBzZWVkKSA9IFBfJmx0
O2hhc2gmZ3Q7KHNlY3JldCwgbGFiZWwgKyBzZWVkKSZxdW90OzxvOnA+PC9vOnA+PC9wPg0KPC9k
aXY+DQo8ZGl2Pg0KPHAgY2xhc3M9Ik1zb05vcm1hbCIgc3R5bGU9Im1zby1tYXJnaW4tdG9wLWFs
dDphdXRvO21zby1tYXJnaW4tYm90dG9tLWFsdDphdXRvIj4mbmJzcDs8bzpwPjwvbzpwPjwvcD4N
CjwvZGl2Pg0KPGRpdj4NCjxwIGNsYXNzPSJNc29Ob3JtYWwiIHN0eWxlPSJtc28tbWFyZ2luLXRv
cC1hbHQ6YXV0bzttc28tbWFyZ2luLWJvdHRvbS1hbHQ6YXV0byI+SW4gdGVybXMgb2YgUF8mbHQ7
aGFzaCZndDsgdGhpcyB3b3VsZCBsb29rIGxpa2UgdGhlIGZvbGxvd2luZyB3aXRoIHRoZSBsZW5n
dGggcmVwcmVzZW50ZWQgYXMgYSAyIGJ5dGUgdmFsdWUgaW4gbmV0d29yayBieXRlIG9yZGVyOjxv
OnA+PC9vOnA+PC9wPg0KPC9kaXY+DQo8ZGl2Pg0KPHAgY2xhc3M9Ik1zb05vcm1hbCIgc3R5bGU9
Im1zby1tYXJnaW4tdG9wLWFsdDphdXRvO21zby1tYXJnaW4tYm90dG9tLWFsdDphdXRvIj4mbmJz
cDs8bzpwPjwvbzpwPjwvcD4NCjwvZGl2Pg0KPGRpdj4NCjxwIGNsYXNzPSJNc29Ob3JtYWwiIHN0
eWxlPSJtc28tbWFyZ2luLXRvcC1hbHQ6YXV0bzttc28tbWFyZ2luLWJvdHRvbS1hbHQ6YXV0byI+
SU1DS1tqXSA9IFBfJmx0O2hhc2gmZ3Q7KFMtSU1DS1tqLTFdLCAmcXVvdDtJbm5lciBNZXRob2Rz
IENvbXBvdW5kIEtleXMmcXVvdDsgfCZuYnNwOzxzcGFuIHN0eWxlPSJmb250LXNpemU6MTAuNXB0
O2NvbG9yOiMyQzQzNTMiPklNU0tbal0gfCAweDAwIHwgMHgzQyk8L3NwYW4+PG86cD48L286cD48
L3A+DQo8L2Rpdj4NCjxkaXY+DQo8cCBjbGFzcz0iTXNvTm9ybWFsIiBzdHlsZT0ibXNvLW1hcmdp
bi10b3AtYWx0OmF1dG87bXNvLW1hcmdpbi1ib3R0b20tYWx0OmF1dG8iPiZuYnNwOzxvOnA+PC9v
OnA+PC9wPg0KPC9kaXY+DQo8ZGl2Pg0KPHAgY2xhc3M9Ik1zb05vcm1hbCIgc3R5bGU9Im1zby1t
YXJnaW4tdG9wLWFsdDphdXRvO21zby1tYXJnaW4tYm90dG9tLWFsdDphdXRvIj4mbmJzcDs8bzpw
PjwvbzpwPjwvcD4NCjwvZGl2Pg0KPC9kaXY+DQo8L2Rpdj4NCjwvZGl2Pg0KPC9ibG9ja3F1b3Rl
Pg0KPC9kaXY+DQo8L2Rpdj4NCjwvZGl2Pg0KPC9kaXY+DQo8L2Jsb2NrcXVvdGU+DQo8L2Rpdj4N
CjwvZGl2Pg0KPC9ibG9ja3F1b3RlPg0KPC9kaXY+DQo8L2Rpdj4NCjwvYmxvY2txdW90ZT4NCjwv
ZGl2Pg0KPC9kaXY+DQo8L2Jsb2NrcXVvdGU+DQo8L2Rpdj4NCjwvYmxvY2txdW90ZT4NCjwvZGl2
Pg0KPC9kaXY+DQo8L2Rpdj4NCjwvYm9keT4NCjwvaHRtbD4NCg==

--_000_CH2PR21MB13810C16054DD1DDB4055659D11D0CH2PR21MB1381namp_--


From nobody Thu Oct 22 10:50:35 2020
Return-Path: <oleg.pekar.2017@gmail.com>
X-Original-To: emu@ietfa.amsl.com
Delivered-To: emu@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 28F913A09C0 for <emu@ietfa.amsl.com>; Thu, 22 Oct 2020 10:50:34 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.747
X-Spam-Level: 
X-Spam-Status: No, score=-1.747 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, DKIM_VALID_EF=-0.1, FREEMAIL_ENVFROM_END_DIGIT=0.25, FREEMAIL_FROM=0.001, HTML_MESSAGE=0.001, HTTPS_HTTP_MISMATCH=0.1, SPF_HELO_NONE=0.001, SPF_PASS=-0.001, URIBL_BLOCKED=0.001] autolearn=no autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (2048-bit key) header.d=gmail.com
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 a1jpJosywVqU for <emu@ietfa.amsl.com>; Thu, 22 Oct 2020 10:50:31 -0700 (PDT)
Received: from mail-ot1-x32f.google.com (mail-ot1-x32f.google.com [IPv6:2607:f8b0:4864:20::32f]) (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 9FDAB3A09BE for <emu@ietf.org>; Thu, 22 Oct 2020 10:50:30 -0700 (PDT)
Received: by mail-ot1-x32f.google.com with SMTP id h62so2257053oth.9 for <emu@ietf.org>; Thu, 22 Oct 2020 10:50:30 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20161025;  h=mime-version:references:in-reply-to:from:date:message-id:subject:to :cc; bh=BbijiGE3UaFNv2bRgbl4DsWZrs6ZrReN4iTOGpouXtk=; b=QE/RLVi5oMceafcu0uIYFfxqPsi7081nidbOZQ2XU2RMGxJPlMMB+3VlPgvZHOJ1SN GmyrqKW7XECzthxIYgj/EuBt1unrYcMnj35+ff7AwIbt2UKNlMt3DYr2aGMJ+EXWCkyS egLt1A6fWwHtm7HDboEedMjAQNnVx1viEGQljGkSkyE011VsUdeQotFmnCflUyk5eC76 dGRPgwpiD4BzybJSoPaYWz6tryx8i5+Hp5/yeN4jss6JJOFsfeKzQs1H4N8RHySIM4vR vXWvOAcKAr6D3CzLJ0mFH3UtzdKd/qA1syASmgHX17Ba7CCsdkQMbImE5gbYBDwgacDJ loOQ==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:mime-version:references:in-reply-to:from:date :message-id:subject:to:cc; bh=BbijiGE3UaFNv2bRgbl4DsWZrs6ZrReN4iTOGpouXtk=; b=uHG4MUqbT3GeTHVnD4CsT42fksgvBh49Wa5vSaOIsOhtUa+SpMXrlfKz+HMDx7jLcd n53VomjmIsFkTEeJtoCZ+qRlwenkE929huWI/L+Pt6PqIteqnmE2xujIJ/1lEX4eI+hm B9+s6NRMNm2wJF8/U4L3t/LphCLLl638hiwCwCdywxtjrh23tSDCdK+X+rqhDcN3YuOV 4OKrIlqIY0oLGsAwXzjE7rdxBeqpf0j7kfmaI6jSqCUT4E5BNBI26NHrRqM5+IVTfBjv CY76DyJ9ElDQU5oRUa7TiXtc8v8RQmXNjgMXTflTL8jHMbde7fWe5tqsEEvewJT3l54Z fo/A==
X-Gm-Message-State: AOAM531ADDj+O1HAAI439xYv1jWho/U6h6ApOPr/1knGMUcy6xN74Bb4 MD1PxLcqd9kjNCHPN72G7lKwULZWUBUFpj7GWjw=
X-Google-Smtp-Source: ABdhPJzBOlxebCoNNadsFH9MikYsprvkwLj1ihBWldZ/KzOaef73pig5AT5kVuZOuq7nwbEtMXmv2rY2DKthLfcWmOQ=
X-Received: by 2002:a9d:6a0a:: with SMTP id g10mr2806486otn.44.1603389029701;  Thu, 22 Oct 2020 10:50:29 -0700 (PDT)
MIME-Version: 1.0
References: <CAOgPGoBay+GG=F8WV0gLOOwLtGdGALGw_cM2JoAnXOtmGq7A+w@mail.gmail.com> <CH2PR21MB138143E929DAFE3C893D8144D11C0@CH2PR21MB1381.namprd21.prod.outlook.com> <CAOgPGoAtcm+Br+YkCyTtg5nJjqO7LGSo77b+CD4+Ba05azafew@mail.gmail.com> <CH2PR21MB13815BCEDC846D7C440AD564D11C0@CH2PR21MB1381.namprd21.prod.outlook.com> <CAOgPGoDTC-qiHOXFTJd7aMn2To7ySzBcx+iQMB9m5foC1bFxzw@mail.gmail.com> <CABXxEz8SRvMXdMR8_cPfvWdauJZwCjnd=7ytnVZ+_L-sB48wvw@mail.gmail.com> <CAOgPGoCsWy-uhYeeHCDUaazjAwfWtr_zkS5CUoX8+baASahFEg@mail.gmail.com> <CABXxEz9euWaA9Y66+1u4gtFCWkrPUEd-juY_TFUHPQE4R_OpRg@mail.gmail.com> <CAOgPGoDcD7wjiMt2=t0vx2FPr2LD2S3eU1d0_bVU1c88S=tA=w@mail.gmail.com> <CH2PR21MB13810C16054DD1DDB4055659D11D0@CH2PR21MB1381.namprd21.prod.outlook.com>
In-Reply-To: <CH2PR21MB13810C16054DD1DDB4055659D11D0@CH2PR21MB1381.namprd21.prod.outlook.com>
From: Oleg Pekar <oleg.pekar.2017@gmail.com>
Date: Thu, 22 Oct 2020 20:50:18 +0300
Message-ID: <CABXxEz8JP07gLB2Tknx1ahErZ=ydVVq2XORLadDatBcSjVu3-Q@mail.gmail.com>
To: Jorge Vergara <jovergar@microsoft.com>
Cc: Joseph Salowey <joe@salowey.net>, EMU WG <emu@ietf.org>, Jouni Malinen <j@w1.fi>
Content-Type: multipart/alternative; boundary="0000000000008d5b7805b246190b"
Archived-At: <https://mailarchive.ietf.org/arch/msg/emu/NPEE6rHq5AmSGX4340mbX8gQ-xg>
Subject: Re: [Emu] Proposed resolution for TEAP errata for 5128
X-BeenThere: emu@ietf.org
X-Mailman-Version: 2.1.29
Precedence: list
List-Id: "EAP Methods Update \(EMU\)" <emu.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/emu>, <mailto:emu-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/emu/>
List-Post: <mailto:emu@ietf.org>
List-Help: <mailto:emu-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/emu>, <mailto:emu-request@ietf.org?subject=subscribe>
X-List-Received-Date: Thu, 22 Oct 2020 17:50:34 -0000

--0000000000008d5b7805b246190b
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable

>No, Microsoft implements number 1 of Joe=E2=80=99s presented options. That=
 is -
P_<hash>(S-IMCK[j], "Session Key Generating Function").



>This follows the same pattern as the errata we are discussion. I am very
surprised to hear that Cisco=E2=80=99s implementation may be different. Ole=
g, could
you please double check? I have just double checked our

>implementation. Since our implementations interop, I assume we must have
the same implementation.



Jorge, thanks for pointing that out. Cisco also implements option number 1
from above. I referenced to EAP-FAST implementation by mistake, sorry.


So, not to harm at least two implementations, all we can do for errata
5127, 5128 - is just to change the wording to be more clear, removing
ambiguity.

On Thu, Oct 22, 2020 at 7:58 PM Jorge Vergara <jovergar@microsoft.com>
wrote:

> >[Joe] This is the one we have not discussed yet.  This derivation is als=
o
> ambiguous.  THis section does not reference 5295.  It's not clear if the
> original intent was to include the length in the hash or not.  I think
> there are a few interpretations:
>
> >
>
> >1. TLS-PRF(S-IMCK[j], "Session Key Generating Function")  iterated to
> generate 64 bytes =3D P_hash(S-IMCK[j], "Session Key Generating Function=
=E2=80=9D)
>
> >2. TLS-PRF(S-IMCK[j], "Session Key Generating Function", 64)  iterated
> to generate 64 bytes =3D P_hash(S-IMCK[j], "Session Key Generating Functi=
on=E2=80=9D
> | 0x00 | 0x40)
>
> >3. (Follow 5295 parameters) TLS-PRF(S-IMCK[j], "Session Key Generating
> Function", "\0" | 64) =3D P_hash(S-IMCK[j], "Session Key Generating
> Function=E2=80=9D | 0x00 | 0x00 | 0x40)
>
> >
>
> >I think 1 or 2 is what was probably originally intended, however it seem=
s
> that 3 is what has been implemented.  Do we have agreement on this is wha=
t
> current implementations do?
>
>
>
> No, Microsoft implements number 1 of Joe=E2=80=99s presented options. Tha=
t is -
> P_<hash>(S-IMCK[j], "Session Key Generating Function").
>
>
>
> This follows the same pattern as the errata we are discussion. I am very
> surprised to hear that Cisco=E2=80=99s implementation may be different. O=
leg, could
> you please double check? I have just double checked our implementation.
> Since our implementations interop, I assume we must have the same
> implementation.
>
>
>
> Jorge Vergara
>
>
>
>
>
> *From:* Joseph Salowey <joe@salowey.net>
> *Sent:* Thursday, October 22, 2020 9:53 AM
> *To:* Oleg Pekar <oleg.pekar.2017@gmail.com>
> *Cc:* EMU WG <emu@ietf.org>; Jorge Vergara <jovergar@microsoft.com>;
> Jouni Malinen <j@w1.fi>
> *Subject:* Re: Proposed resolution for TEAP errata for 5128
>
>
>
>
>
>
>
> On Thu, Oct 22, 2020 at 9:29 AM Oleg Pekar <oleg.pekar.2017@gmail.com>
> wrote:
>
> I agree that changing the KDF is harmful to existing implementations.
> However, if I understood correctly, Joe's suggestion for IMCK[j] also
> breaks the existing implementation. I still see that we can define a
> unified KDF by changing the API in the RFC but with the same harm to the
> existing implementation in IMCK[j] as in both proposals:
>
>
>
> TEAP-PRF (secret, key label, optional data, length) =3D TLS-PRF(secret, k=
ey
> label | 0x00 | optional data, length)
>
> Joe, thanks for pointing out that RFC 5295 doesn't specify that a 0x00 is
> used to represent no optional data, that was just my mistake.
>
>
>
> IMSK:
>
> Current Microsoft and Cisco implementation: P_hash(EMSK, "
> TEAPbindkey@ietf.org" | 0x00 | 0x00 | 0x40)
>
> Joe's proposal: P_hash(EMSK, "TEAPbindkey@ietf.org" | 0x00 | 0x00 |
> 0x40), the same, just the API correction
>
> Unified KDF proposal: TEAP-PRF(EMSK, "TEAPbindkey@ietf.org", <no optional
> data>, 64) =3D P_hash(EMSK, "TEAPbindkey@ietf.org" | 0x00 | 0x00 | 0x40)
>
> --- no implementation change
>
>
>
> IMCK[j]:
>
> Current Microsoft and Cisco implementation: P_hash(S-IMCK[j-1], "Inner
> Methods Compound Keys=E2=80=9D | IMSK[j])
>
> Joe's proposal: P_hash(S-IMCK[j-1], "Inner Methods Compound Keys" |
> IMSK[j] | 0x00 | 0x3C)
>
> Unified KDF proposal: TEAP-PRF(S-IMCK[j-1], "Inner Methods Compound Keys"=
,
> IMSK[j], 60) =3D P_hash(S-IMCK[j-1], "Inner Methods Compound Keys" | IMSK=
[j]
> | 0x00 | 0x3C)
>
> --- implementation change
>
>
>
> [Joe] That was my initial proposal, but based on Jorge's comment it is
> modified to:
>
>
> IMCK[j] =3D TLS-PRF(S-IMCK[j-1], "Inner Methods Compound Keys", IMSK[j])
> to generate a length of 60 bytes
>
> IMCK[j] =3D P_hash(S-IMCK[j-1], "Inner Methods Compound Keys=E2=80=9D | I=
MSK[j])
>
>
>
>
>
> MSK:
>
> Current Microsoft and Cisco implementation: P_hash(S-IMCK[j], "Session Ke=
y
> Generating Function=E2=80=9D | 0x00 | 0x00 | 0x40)
>
> Unified KDF proposal: TEAP-PRF(S-IMCK[j], "Session Key Generating
> Function=E2=80=9D, <no optional data>, 64) =3D P_hash(S-IMCK[j], "Session=
 Key
> Generating Function=E2=80=9D | 0x00 | 0x00 | 0x40)
>
> --- no implementation change
>
>
>
> [Joe] This is the one we have not discussed yet.  This derivation is also
> ambiguous.  THis section does not reference 5295.  It's not clear if the
> original intent was to include the length in the hash or not.  I think
> there are a few interpretations:
>
>
>
> 1. TLS-PRF(S-IMCK[j], "Session Key Generating Function")  iterated to
> generate 64 bytes =3D P_hash(S-IMCK[j], "Session Key Generating Function=
=E2=80=9D)
>
> 2. TLS-PRF(S-IMCK[j], "Session Key Generating Function", 64)  iterated to
> generate 64 bytes =3D P_hash(S-IMCK[j], "Session Key Generating Function=
=E2=80=9D |
> 0x00 | 0x40)
>
> 3. (Follow 5295 parameters) TLS-PRF(S-IMCK[j], "Session Key Generating
> Function", "\0" | 64) =3D P_hash(S-IMCK[j], "Session Key Generating
> Function=E2=80=9D | 0x00 | 0x00 | 0x40)
>
>
>
> I think 1 or 2 is what was probably originally intended, however it seems
> that 3 is what has been implemented.  Do we have agreement on this is wha=
t
> current implementations do?
>
>
>
>
>
>
>
> Jorge, please correct me if I misinterpret the Microsoft implementation.
>
>
>
> On Thu, Oct 22, 2020 at 6:55 PM Joseph Salowey <joe@salowey.net> wrote:
>
>
>
>
>
> On Thu, Oct 22, 2020 at 6:59 AM Oleg Pekar <oleg.pekar.2017@gmail.com>
> wrote:
>
> Hi all,
>
> Speaking about both errata 5127 and 5128, I think we need to align all ke=
y
> derivation calls in TEAP RFC with the same rule/format to make the RFC
> easier to understand. This can be achieved by introducing a unified singl=
e
> PRF function that will be called from all the relevant RFC locations. For
> me it sounds better than if we align just part of KDF calls with RFC 5295
> (where the output length is included into seed). Also: in some KDF calls =
we
> do have optional data and in some no. This could be also unified.
>
>
>
> [Joe] I don't think this was the original intent of the document.  The
> IMSK derivation referenced 5295 while the others just reference the TLS
> PRF.  I think to unify them would require a document update and I'm not
> sure what we would gain especially if we have implementations that do
> this.
>
>
>
> So I would suggest introducing:
>
> TEAP-PRF (secret, key label, optional data, length) =3D TLS-PRF(secret, k=
ey
> label | 0x00 | optional data, length)
>
> where a single byte 0x00 is used for no optional data, length is a 2-octe=
t
> unsigned integer in network byte order.
>
>
>
> [Joe] I don't think that 5295 specifies that a 0x00 is used to represent
> no optional data.  Did you see this in the spec? It may be ambiguous, but=
 I
> think the intent is that optional data is just omitted if it is not
> provided.
>
>
>
>
>
> Then:
>
> IMSK =3D First 32 octets of TEAP-PRF(EMSK, "TEAPbindkey@ietf.org", 64) =
=3D
> TLS-PRF(EMSK, "TEAPbindkey@ietf.org" | 0x00 | 0x00 | 0x00 | 0x40)
> IMCK[j] =3D TEAP-PRF(S-IMCK[j-1], "Inner Methods Compound Keys", IMSK[j],
> 60) =3D TLS-PRF(S-IMCK[j-1], "Inner Methods Compound Keys" | 0x00 | IMSK[=
j] |
> 0x00 | 0x3C)
> MSK =3D TEAP-PRF(S-IMCK[j], "Session Key Generating Function=E2=80=9D, 64=
) =3D
> TLS-PRF(S-IMCK[j], "Session Key Generating Function" | 0x00 | 0x00 | 0x00=
 |
> 0x40)
> EMSK =3D TEAP-PRF(S-IMCK[j], =E2=80=9DExtended Session Key Generating Fun=
ction=E2=80=9D, 64)
> =3D TLS-PRF(S-IMCK[j], "Extended Session Key Generating Function" | 0x00 =
|
> 0x00 | 0x00 | 0x40)
>
>
>
> This may change the existing implementation but will make it more clear -
> need to create and call just one KDF function.
>
>
>
> We can remove 0x00 that comes after the key label - while it is required
> by RFC 5295. But there the key label is also ASCII printable string. Joe,
> do you remember what was the motivation to put 0x00 after the key label
> parameter?
>
>
>
> [Joe] the null after the key label is to provide a delimiter between the
> key label and optional data.  Since the optional data can be arbitrary
> content the null prevents two different lablels with specially crafted
> optional data from deriving the same key.
>
>
>
>
>
> Oleg
>
>
>
>
>
> On Thu, Oct 22, 2020 at 2:54 AM Joseph Salowey <joe@salowey.net> wrote:
>
> (I accidentally dropped this list from the conversation)
>
>
>
> On Wed, Oct 21, 2020 at 4:48 PM Jorge Vergara <jovergar@microsoft.com>
> wrote:
>
> >[Joe] Yes this is a concern and I think your interpretation of the
> current document is also valid.  There may be more than one
> implementation.  So what you implemented was:
>
> >
>
> >IMCK[j] =3D TLS-PRF(S-IMCK[j-1], "Inner Methods Compound Keys", IMSK[j])=
 =3D
> P_<hash>(S-IMCK[j-1], "Inner Methods Compound Keys" | IMSK[j])
>
>
>
> Yes, this is what I implemented. As you mentioned, there are multiple
> possible interpretations of this since the TEAP usage is incorrect.
> However, my implementation does interop with at least 2 large vendor
> implementations. If the implementations were using different calculations
> here, the Wi-Fi/Ethernet connections that depend on the MSK would fail. B=
ut
> since connections work, I can assume we are all using the same
> implementation and arriving at the same MSK. Cisco is one of the
> implementations that I have tested against which is why I was hoping Oleg
> may offer more context as to what he has seen.
>
>
>
> [Joe] I can hope Jouni can chime in on this as well.  I think the origina=
l
> intent was to not include the length as is your suggestion.
>
>
>
>
>
> >[Joe] Does the revision in 5167 match you implementation ( I don't think
> Jouni's comment changes the underly calculation, just its representation)=
?
>
>
>
> I have not implemented this portion of the RFC as I found it too unclear
> to work with. Thus I can=E2=80=99t comment on what implementations may be=
 doing.
> However, I agree with the current revision in 5167 as the most natural
> interpretation. If others have implemented this portion of the RFC then
> certainly their comments would be welcome.
>
>
>
> By the way, we=E2=80=99ve dropped the EMU group on our replies here =E2=
=80=93 not sure if
> intentional or not.
>
>
>
> Jorge Vergara
>
>
>
> *From:* Joseph Salowey <joe@salowey.net>
> *Sent:* Wednesday, October 21, 2020 4:36 PM
> *To:* Jorge Vergara <jovergar@microsoft.com>
> *Subject:* Re: Proposed resolution for TEAP errata for 5128
>
>
>
>
>
>
>
> On Wed, Oct 21, 2020 at 3:20 PM Jorge Vergara <jovergar@microsoft.com>
> wrote:
>
> In theory I agree this is a possible resolution. However, this doesn=E2=
=80=99t
> match any of the current TEAP implementations that I am aware of. Perhaps
> Oleg can weigh in as well in terms of what he=E2=80=99s seen.
>
>
>
> I believe all current implementations treat 60 as the desired output
> length without treating as a seed. In terms of P_<hash>, this means
> implementations are performing the calculation without a seed.
>
>
>
> RFC 5246 defines the TLS 1.2 PRF as:
>
> PRF(secret, label, seed) =3D P_<hash>(secret, label + seed)
>
>
>
> So the calculation implementations are currently performing with an empty
> seed ends up as:
>
> P_<hash>(secret, label)
>
>
>
> Note that in RFC 5295, the length *is* explicitly mentioned as being
> concatenated with the label
>
> USRK =3D KDF(EMSK, key label | "\0" | optional data | length)
>
>
>
> RFC 5295 is mentioned earlier in the TEAP RFC, in the section covered by
> errata 5127. *However* it is not mentioned in this portion of the RFC.
> Since this calculation is not on an EMSK, I do not believe RFC 2395 appli=
es
> and this is likely why implementations went with the seedless
> P_<hash>(secret, label) calculation instead.
>
>
>
> Is there concern about updating the RFC in a way that breaks existing
> implementations?
>
>
>
> [Joe] Yes this is a concern and I think your interpretation of the curren=
t
> document is also valid.  There may be more than one implementation.  So
> what you implemented was:
>
>
>
> IMCK[j] =3D TLS-PRF(S-IMCK[j-1], "Inner Methods Compound Keys", IMSK[j]) =
=3D
> P_<hash>(S-IMCK[j-1], "Inner Methods Compound Keys" | IMSK[j])
>
>
>
> taken out to 60 bytes.  The problem is that the TEAP spec references a
> TLS-PRF in a way that it does not define.  I think the errata points out
> the definition that should be used:
>
>
>
> PRF(secret, label, seed) =3D P_<hash>(secret, label + seed)
>
>
>
> That does not include length so the 60 in the original definition is
> ambiguous.   The new text would then be something like:
>
>
>
> IMCK[j] =3D TLS-PRF(S-IMCK[j-1], "Inner Methods Compound Keys", IMSK[j])
> to generate a length of 60 bytes
>
>
>
> Does the revision in 5167 match you implementation ( I don't think
> Jouni's comment changes the underly calculation, just its representation)=
?
>
>
>
>
>
>
>
>
>
>
>
> Jorge Vergara
>
>
>
> *From:* Joseph Salowey <joe@salowey.net>
> *Sent:* Wednesday, October 21, 2020 2:34 PM
> *To:* EMU WG <emu@ietf.org>; Jouni Malinen <j@w1.fi>; Jorge Vergara <
> jovergar@microsoft.com>; Oleg Pekar (olpekar) <olpekar@cisco.com>
> *Subject:* Proposed resolution for TEAP errata for 5128
>
>
>
> Errata 5128: https://www.rfc-editor.org/errata/eid5128
> <https://nam06.safelinks.protection.outlook.com/?url=3Dhttps%3A%2F%2Fwww.=
rfc-editor.org%2Ferrata%2Feid5128&data=3D04%7C01%7Cjovergar%40microsoft.com=
%7C1607f5f05ab64c11228108d876ab0304%7C72f988bf86f141af91ab2d7cd011db47%7C1%=
7C0%7C637389824150792537%7CUnknown%7CTWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIj=
oiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D%7C1000&sdata=3D%2FY77gd5%2BZnRPHT%=
2Bkq2KkTJPlkK2hIu%2FfFejHlj9e7CQ%3D&reserved=3D0>
>
> Proposed State: Verified
>
> Revision:
>
>
>
> Section 5.2. says
>
>
> IMCK[j] =3D TLS-PRF(S-IMCK[j-1], "Inner Methods Compound Keys",
>                 IMSK[j], 60)
>
> It should say:
>
> IMCK[j] =3D TLS-PRF(S-IMCK[j-1], "Inner Methods Compound Keys", IMSK[j] |
> 60)
>
> Note:
>
> According to
>
> RFC5246 The Transport Layer Security (TLS) Protocol Version 1.2
>
> 5. HMAC and the Pseudorandom Function
>
> "TLS's PRF is created by applying P_hash to the secret as:
>
> PRF(secret, label, seed) =3D P_<hash>(secret, label + seed)"
>
>
>
> In terms of P_<hash> this would look like the following with the length
> represented as a 2 byte value in network byte order:
>
>
>
> IMCK[j] =3D P_<hash>(S-IMCK[j-1], "Inner Methods Compound Keys" | IMSK[j]=
 |
> 0x00 | 0x3C)
>
>
>
>
>
>

--0000000000008d5b7805b246190b
Content-Type: text/html; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable

<div dir=3D"ltr">&gt;No, Microsoft implements number 1 of Joe=E2=80=99s pre=
sented options. That is - P_&lt;hash&gt;(S-IMCK[j], &quot;Session Key Gener=
ating Function&quot;).<p class=3D"MsoNormal"><u></u></p><p class=3D"MsoNorm=
al"><u></u>=C2=A0<u></u></p><p class=3D"MsoNormal">&gt;This follows the sam=
e pattern as the errata we are discussion. I am very surprised to hear that=
 Cisco=E2=80=99s implementation may be different. Oleg, could you please do=
uble check? I have just double checked our</p><p class=3D"MsoNormal">&gt;im=
plementation. Since our implementations interop, I assume we must have the =
same implementation.<font color=3D"#888888"><u></u><u></u></font></p><font =
color=3D"#888888"><p class=3D"MsoNormal"><u></u>=C2=A0</p><p class=3D"MsoNo=
rmal">Jorge, thanks for pointing that out. Cisco also implements option num=
ber 1 from above. I referenced to EAP-FAST implementation by mistake, sorry=
.</p><p class=3D"MsoNormal"><br></p><p class=3D"MsoNormal">So, not to harm =
at least two implementations, all we can do for errata 5127, 5128 - is just=
 to change the wording to be more clear, removing ambiguity.=C2=A0</p></fon=
t></div><br><div class=3D"gmail_quote"><div dir=3D"ltr" class=3D"gmail_attr=
">On Thu, Oct 22, 2020 at 7:58 PM Jorge Vergara &lt;<a href=3D"mailto:jover=
gar@microsoft.com">jovergar@microsoft.com</a>&gt; wrote:<br></div><blockquo=
te class=3D"gmail_quote" style=3D"margin:0px 0px 0px 0.8ex;border-left:1px =
solid rgb(204,204,204);padding-left:1ex">





<div lang=3D"EN-US" style=3D"overflow-wrap: break-word;">
<div class=3D"gmail-m_-4205747541474325603WordSection1">
<p class=3D"MsoNormal">&gt;[Joe] This is the one we have not discussed yet.=
=C2=A0 This derivation is also ambiguous.=C2=A0 THis section does not refer=
ence 5295.=C2=A0 It&#39;s not clear if the original intent was to include t=
he length in the hash or not.=C2=A0 I think there are a few interpretations=
:<u></u><u></u></p>
<p class=3D"MsoNormal">&gt;<u></u>=C2=A0<u></u></p>
<p class=3D"MsoNormal"><span style=3D"font-size:10pt;color:black">&gt;1. TL=
S-PRF(S-IMCK[j], &quot;Session Key Generating Function&quot;)</span>=C2=A0 =
iterated to generate 64 bytes =3D=C2=A0P_hash(S-IMCK[j], &quot;Session Key =
Generating Function=E2=80=9D)<u></u><u></u></p>
<p class=3D"MsoNormal"><span style=3D"font-size:10pt;color:black">&gt;2. TL=
S-PRF(S-IMCK[j], &quot;Session Key Generating Function&quot;, 64)</span>=C2=
=A0 iterated to generate 64 bytes =3D=C2=A0P_hash(S-IMCK[j], &quot;Session =
Key Generating Function=E2=80=9D | 0x00 | 0x40)<u></u><u></u></p>
<p class=3D"MsoNormal">&gt;3. (Follow 5295 parameters)=C2=A0<span style=3D"=
font-size:10pt;color:black">TLS-PRF(S-IMCK[j], &quot;Session Key Generating=
 Function&quot;, &quot;\0&quot; | 64)</span>=C2=A0=3D=C2=A0P_hash(S-IMCK[j]=
, &quot;Session Key Generating Function=E2=80=9D | 0x00 | 0x00 | 0x40)<u></=
u><u></u></p>
<p class=3D"MsoNormal">&gt;<u></u>=C2=A0<u></u></p>
<p class=3D"MsoNormal">&gt;I think 1 or 2 is what was probably originally i=
ntended, however it seems that 3 is what has been implemented.=C2=A0 Do we =
have agreement on this is what current implementations do?=C2=A0<u></u><u><=
/u></p>
<p class=3D"MsoNormal"><u></u>=C2=A0<u></u></p>
<p class=3D"MsoNormal">No, Microsoft implements number 1 of Joe=E2=80=99s p=
resented options. That is - P_&lt;hash&gt;(S-IMCK[j], &quot;Session Key Gen=
erating Function&quot;).<u></u><u></u></p>
<p class=3D"MsoNormal"><u></u>=C2=A0<u></u></p>
<p class=3D"MsoNormal">This follows the same pattern as the errata we are d=
iscussion. I am very surprised to hear that Cisco=E2=80=99s implementation =
may be different. Oleg, could you please double check? I have just double c=
hecked our implementation. Since our implementations
 interop, I assume we must have the same implementation.<u></u><u></u></p>
<p class=3D"MsoNormal"><u></u>=C2=A0<u></u></p>
<p class=3D"MsoNormal">Jorge Vergara<u></u><u></u></p>
<p class=3D"MsoNormal"><u></u>=C2=A0<u></u></p>
<p class=3D"MsoNormal"><u></u>=C2=A0<u></u></p>
<div style=3D"border-right:none;border-bottom:none;border-left:none;border-=
top:1pt solid rgb(225,225,225);padding:3pt 0in 0in">
<p class=3D"MsoNormal"><b>From:</b> Joseph Salowey &lt;<a href=3D"mailto:jo=
e@salowey.net" target=3D"_blank">joe@salowey.net</a>&gt; <br>
<b>Sent:</b> Thursday, October 22, 2020 9:53 AM<br>
<b>To:</b> Oleg Pekar &lt;<a href=3D"mailto:oleg.pekar.2017@gmail.com" targ=
et=3D"_blank">oleg.pekar.2017@gmail.com</a>&gt;<br>
<b>Cc:</b> EMU WG &lt;<a href=3D"mailto:emu@ietf.org" target=3D"_blank">emu=
@ietf.org</a>&gt;; Jorge Vergara &lt;<a href=3D"mailto:jovergar@microsoft.c=
om" target=3D"_blank">jovergar@microsoft.com</a>&gt;; Jouni Malinen &lt;<a =
href=3D"mailto:j@w1.fi" target=3D"_blank">j@w1.fi</a>&gt;<br>
<b>Subject:</b> Re: Proposed resolution for TEAP errata for 5128<u></u><u><=
/u></p>
</div>
<p class=3D"MsoNormal"><u></u>=C2=A0<u></u></p>
<div>
<div>
<p class=3D"MsoNormal"><u></u>=C2=A0<u></u></p>
</div>
<p class=3D"MsoNormal"><u></u>=C2=A0<u></u></p>
<div>
<div>
<p class=3D"MsoNormal">On Thu, Oct 22, 2020 at 9:29 AM Oleg Pekar &lt;<a hr=
ef=3D"mailto:oleg.pekar.2017@gmail.com" target=3D"_blank">oleg.pekar.2017@g=
mail.com</a>&gt; wrote:<u></u><u></u></p>
</div>
<blockquote style=3D"border-top:none;border-right:none;border-bottom:none;b=
order-left:1pt solid rgb(204,204,204);padding:0in 0in 0in 6pt;margin-left:4=
.8pt;margin-right:0in">
<div>
<p class=3D"MsoNormal">I agree that changing the KDF is harmful to existing=
 implementations. However, if I understood correctly, Joe&#39;s suggestion=
=C2=A0for IMCK[j] also breaks the existing=C2=A0implementation. I still see=
 that we can define a unified KDF by changing the
 API in the RFC but with the same harm to the existing implementation in IM=
CK[j] as in both proposals:<u></u><u></u></p>
<div>
<p class=3D"MsoNormal"><u></u>=C2=A0<u></u></p>
</div>
<div>
<p class=3D"MsoNormal">TEAP-PRF (secret, key label, optional data, length) =
=3D TLS-PRF(secret, key label | 0x00 | optional data, length)<u></u><u></u>=
</p>
</div>
<div>
<p class=3D"MsoNormal">Joe, thanks for pointing out that RFC 5295 doesn&#39=
;t specify that a 0x00 is used to represent no optional data, that was just=
 my mistake.<u></u><u></u></p>
</div>
<div>
<p class=3D"MsoNormal"><u></u>=C2=A0<u></u></p>
<div>
<p class=3D"MsoNormal">IMSK:<u></u><u></u></p>
</div>
<div>
<p class=3D"MsoNormal">Current Microsoft and Cisco implementation: P_hash(E=
MSK, &quot;<a href=3D"mailto:TEAPbindkey@ietf.org" target=3D"_blank">TEAPbi=
ndkey@ietf.org</a>&quot; | 0x00 | 0x00 | 0x40)
<u></u><u></u></p>
</div>
<div>
<p class=3D"MsoNormal">Joe&#39;s proposal: P_hash(EMSK, &quot;<a href=3D"ma=
ilto:TEAPbindkey@ietf.org" target=3D"_blank">TEAPbindkey@ietf.org</a>&quot;=
 | 0x00 | 0x00 | 0x40), the same, just the API correction<u></u><u></u></p>
</div>
<div>
<p class=3D"MsoNormal">Unified KDF proposal:=C2=A0TEAP-PRF(EMSK, &quot;<a h=
ref=3D"mailto:TEAPbindkey@ietf.org" target=3D"_blank">TEAPbindkey@ietf.org<=
/a>&quot;, &lt;no optional data&gt;, 64) =3D P_hash(EMSK, &quot;<a href=3D"=
mailto:TEAPbindkey@ietf.org" target=3D"_blank">TEAPbindkey@ietf.org</a>&quo=
t;
 | 0x00 | 0x00 | 0x40)=C2=A0<u></u><u></u></p>
</div>
<div>
<p class=3D"MsoNormal">--- no implementation change<u></u><u></u></p>
</div>
<div>
<p class=3D"MsoNormal"><u></u>=C2=A0<u></u></p>
</div>
<div>
<p class=3D"MsoNormal">IMCK[j]:<u></u><u></u></p>
</div>
<div>
<div>
<p class=3D"MsoNormal">Current Microsoft and Cisco implementation: P_hash(S=
-IMCK[j-1], &quot;Inner Methods Compound Keys=E2=80=9D | IMSK[j])=C2=A0<u><=
/u><u></u></p>
</div>
<div>
<p class=3D"MsoNormal">Joe&#39;s proposal:=C2=A0P_hash(S-IMCK[j-1], &quot;I=
nner Methods Compound Keys&quot; | IMSK[j] | 0x00 | 0x3C)<u></u><u></u></p>
</div>
<div>
<p class=3D"MsoNormal">Unified KDF proposal: TEAP-PRF(S-IMCK[j-1], &quot;In=
ner Methods Compound Keys&quot;, IMSK[j], 60) =3D P_hash(S-IMCK[j-1], &quot=
;Inner Methods Compound Keys&quot; | IMSK[j] | 0x00 | 0x3C)<u></u><u></u></=
p>
</div>
</div>
<div>
<div>
<p class=3D"MsoNormal">--- implementation change<u></u><u></u></p>
</div>
</div>
</div>
</div>
</blockquote>
<div>
<p class=3D"MsoNormal"><u></u>=C2=A0<u></u></p>
</div>
<div>
<p class=3D"MsoNormal">[Joe] That was my initial proposal, but based on Jor=
ge&#39;s comment it is modified to:<u></u><u></u></p>
</div>
<div>
<p class=3D"MsoNormal"><br>
IMCK[j] =3D TLS-PRF(S-IMCK[j-1], &quot;Inner Methods Compound Keys&quot;,=
=C2=A0<span style=3D"font-size:10.5pt;color:rgb(44,67,83)">IMSK[j])=C2=A0 t=
o generate a length of 60 bytes</span><u></u><u></u></p>
</div>
<div>
<p class=3D"MsoNormal"><span style=3D"font-size:10.5pt;color:rgb(44,67,83)"=
>IMCK[j] =3D=C2=A0</span>P_hash(S-IMCK[j-1], &quot;Inner Methods Compound K=
eys=E2=80=9D | IMSK[j])=C2=A0<u></u><u></u></p>
</div>
<div>
<p class=3D"MsoNormal">=C2=A0<u></u><u></u></p>
</div>
<blockquote style=3D"border-top:none;border-right:none;border-bottom:none;b=
order-left:1pt solid rgb(204,204,204);padding:0in 0in 0in 6pt;margin-left:4=
.8pt;margin-right:0in">
<div>
<div>
<div>
<p class=3D"MsoNormal"><u></u>=C2=A0<u></u></p>
</div>
<div>
<p class=3D"MsoNormal">MSK:<u></u><u></u></p>
</div>
<div>
<p class=3D"MsoNormal">Current Microsoft and Cisco implementation: P_hash(S=
-IMCK[j], &quot;Session Key Generating Function=E2=80=9D | 0x00 | 0x00 | 0x=
40)<u></u><u></u></p>
</div>
<div>
<p class=3D"MsoNormal">Unified KDF proposal: TEAP-PRF(S-IMCK[j], &quot;Sess=
ion Key Generating Function=E2=80=9D, &lt;no optional data&gt;, 64) =3D P_h=
ash(S-IMCK[j], &quot;Session Key Generating Function=E2=80=9D | 0x00 | 0x00=
 | 0x40)<u></u><u></u></p>
</div>
<div>
<div>
<p class=3D"MsoNormal">--- no implementation change<u></u><u></u></p>
</div>
</div>
<div>
<p class=3D"MsoNormal"><u></u>=C2=A0<u></u></p>
</div>
</div>
</div>
</blockquote>
<div>
<p class=3D"MsoNormal">[Joe] This is the one we have not discussed yet.=C2=
=A0 This derivation is also ambiguous.=C2=A0 THis section does not referenc=
e 5295.=C2=A0 It&#39;s not clear if the original intent was to include the =
length in the hash or not.=C2=A0 I think there are a few interpretations:<u=
></u><u></u></p>
</div>
<div>
<p class=3D"MsoNormal"><u></u>=C2=A0<u></u></p>
</div>
<div>
<p class=3D"MsoNormal"><span style=3D"font-size:10pt;color:black">1. TLS-PR=
F(S-IMCK[j], &quot;Session Key Generating Function&quot;)</span>=C2=A0 iter=
ated to generate 64 bytes =3D=C2=A0P_hash(S-IMCK[j], &quot;Session Key Gene=
rating Function=E2=80=9D)<u></u><u></u></p>
</div>
<div>
<p class=3D"MsoNormal"><span style=3D"font-size:10pt;color:black">2. TLS-PR=
F(S-IMCK[j], &quot;Session Key Generating Function&quot;, 64)</span>=C2=A0 =
iterated to generate 64 bytes =3D=C2=A0P_hash(S-IMCK[j], &quot;Session Key =
Generating Function=E2=80=9D | 0x00 | 0x40)<u></u><u></u></p>
</div>
<div>
<p class=3D"MsoNormal">3. (Follow 5295 parameters)=C2=A0<span style=3D"font=
-size:10pt;color:black">TLS-PRF(S-IMCK[j], &quot;Session Key Generating Fun=
ction&quot;, &quot;\0&quot; | 64)</span>=C2=A0=3D=C2=A0P_hash(S-IMCK[j], &q=
uot;Session Key Generating Function=E2=80=9D | 0x00 | 0x00 | 0x40)<u></u><u=
></u></p>
</div>
<div>
<p class=3D"MsoNormal"><u></u>=C2=A0<u></u></p>
</div>
<div>
<p class=3D"MsoNormal">I think 1 or 2 is what was probably originally inten=
ded, however it seems that 3 is what has been implemented.=C2=A0 Do we have=
 agreement on this is what current implementations do?=C2=A0<u></u><u></u><=
/p>
</div>
<div>
<pre style=3D"break-before:page"><span style=3D"color:black"><u></u>=C2=A0<=
u></u></span></pre>
</div>
<div>
<p class=3D"MsoNormal"><u></u>=C2=A0<u></u></p>
</div>
<div>
<p class=3D"MsoNormal">=C2=A0<u></u><u></u></p>
</div>
<blockquote style=3D"border-top:none;border-right:none;border-bottom:none;b=
order-left:1pt solid rgb(204,204,204);padding:0in 0in 0in 6pt;margin-left:4=
.8pt;margin-right:0in">
<div>
<div>
<div>
<p class=3D"MsoNormal">Jorge, please correct me if I misinterpret=C2=A0the =
Microsoft implementation.=C2=A0<u></u><u></u></p>
</div>
</div>
</div>
<p class=3D"MsoNormal"><u></u>=C2=A0<u></u></p>
<div>
<div>
<p class=3D"MsoNormal">On Thu, Oct 22, 2020 at 6:55 PM Joseph Salowey &lt;<=
a href=3D"mailto:joe@salowey.net" target=3D"_blank">joe@salowey.net</a>&gt;=
 wrote:<u></u><u></u></p>
</div>
<blockquote style=3D"border-top:none;border-right:none;border-bottom:none;b=
order-left:1pt solid rgb(204,204,204);padding:0in 0in 0in 6pt;margin-left:4=
.8pt;margin-right:0in">
<div>
<div>
<p class=3D"MsoNormal"><u></u>=C2=A0<u></u></p>
</div>
<p class=3D"MsoNormal"><u></u>=C2=A0<u></u></p>
<div>
<div>
<p class=3D"MsoNormal">On Thu, Oct 22, 2020 at 6:59 AM Oleg Pekar &lt;<a hr=
ef=3D"mailto:oleg.pekar.2017@gmail.com" target=3D"_blank">oleg.pekar.2017@g=
mail.com</a>&gt; wrote:<u></u><u></u></p>
</div>
<blockquote style=3D"border-top:none;border-right:none;border-bottom:none;b=
order-left:1pt solid rgb(204,204,204);padding:0in 0in 0in 6pt;margin-left:4=
.8pt;margin-right:0in">
<div>
<div>
<p class=3D"MsoNormal">Hi all,<u></u><u></u></p>
</div>
<div>
<p class=3D"MsoNormal">Speaking about both errata 5127 and 5128, I think we=
 need to align all key derivation calls in TEAP RFC with the same rule/form=
at to make the RFC easier to understand. This can be achieved by introducin=
g a unified single PRF function that
 will be called from all the relevant RFC locations. For me it sounds bette=
r than if we align just part of KDF calls with RFC 5295 (where the output l=
ength is included into seed). Also: in some KDF calls we do have optional d=
ata and in some no. This could be
 also unified.=C2=A0<u></u><u></u></p>
</div>
<div>
<p class=3D"MsoNormal"><u></u>=C2=A0<u></u></p>
</div>
</div>
</blockquote>
<div>
<p class=3D"MsoNormal">[Joe] I don&#39;t think this was the original intent=
 of the document.=C2=A0 The IMSK derivation referenced 5295 while the other=
s just reference the TLS PRF.=C2=A0 I think to unify them would require a d=
ocument update and I&#39;m not sure what we would gain
 especially if we have implementations that do this.=C2=A0=C2=A0<u></u><u><=
/u></p>
</div>
<div>
<p class=3D"MsoNormal">=C2=A0<u></u><u></u></p>
</div>
<blockquote style=3D"border-top:none;border-right:none;border-bottom:none;b=
order-left:1pt solid rgb(204,204,204);padding:0in 0in 0in 6pt;margin-left:4=
.8pt;margin-right:0in">
<div>
<div>
<p class=3D"MsoNormal">So I would suggest introducing:<u></u><u></u></p>
</div>
<div>
<p class=3D"MsoNormal">TEAP-PRF (secret, key label, optional data, length) =
=3D TLS-PRF(secret, key label | 0x00 | optional data, length)<u></u><u></u>=
</p>
</div>
<div>
<p class=3D"MsoNormal">where a single byte 0x00 is used for no optional dat=
a, length is a 2-octet unsigned integer in network byte order.<u></u><u></u=
></p>
</div>
<div>
<p class=3D"MsoNormal"><u></u>=C2=A0<u></u></p>
</div>
</div>
</blockquote>
<div>
<p class=3D"MsoNormal">[Joe] I don&#39;t think that 5295 specifies that a 0=
x00 is used to represent no optional data.=C2=A0 Did you see this in the sp=
ec? It may be ambiguous, but I think the intent is that optional data is ju=
st omitted if it is not provided.=C2=A0<u></u><u></u></p>
</div>
<div>
<p class=3D"MsoNormal"><u></u>=C2=A0<u></u></p>
</div>
<div>
<p class=3D"MsoNormal">=C2=A0<u></u><u></u></p>
</div>
<blockquote style=3D"border-top:none;border-right:none;border-bottom:none;b=
order-left:1pt solid rgb(204,204,204);padding:0in 0in 0in 6pt;margin-left:4=
.8pt;margin-right:0in">
<div>
<div>
<p class=3D"MsoNormal">Then:<u></u><u></u></p>
</div>
<div>
<p class=3D"MsoNormal">IMSK =3D First 32 octets of TEAP-PRF(EMSK, &quot;<a =
href=3D"mailto:TEAPbindkey@ietf.org" target=3D"_blank">TEAPbindkey@ietf.org=
</a>&quot;, 64) =3D TLS-PRF(EMSK, &quot;<a href=3D"mailto:TEAPbindkey@ietf.=
org" target=3D"_blank">TEAPbindkey@ietf.org</a>&quot; | 0x00 | 0x00
 | 0x00 | 0x40)<br>
IMCK[j] =3D TEAP-PRF(S-IMCK[j-1], &quot;Inner Methods Compound Keys&quot;, =
IMSK[j], 60) =3D TLS-PRF(S-IMCK[j-1], &quot;Inner Methods Compound Keys&quo=
t; | 0x00 | IMSK[j] | 0x00 | 0x3C)<br>
MSK =3D TEAP-PRF(S-IMCK[j], &quot;Session Key Generating Function=E2=80=9D,=
 64) =3D TLS-PRF(S-IMCK[j], &quot;Session Key Generating Function&quot; | 0=
x00 | 0x00 | 0x00 | 0x40)<br>
EMSK =3D TEAP-PRF(S-IMCK[j], =E2=80=9DExtended Session Key Generating Funct=
ion=E2=80=9D, 64) =3D TLS-PRF(S-IMCK[j], &quot;Extended Session Key Generat=
ing Function&quot; | 0x00 | 0x00 | 0x00 | 0x40)<u></u><u></u></p>
</div>
<div>
<p class=3D"MsoNormal"><u></u>=C2=A0<u></u></p>
</div>
<div>
<p class=3D"MsoNormal">This may change the existing implementation but will=
 make it more clear - need to create and call just one KDF function.<u></u>=
<u></u></p>
</div>
<div>
<p class=3D"MsoNormal"><u></u>=C2=A0<u></u></p>
</div>
<div>
<p class=3D"MsoNormal">We can remove=C2=A00x00 that comes after the key lab=
el - while it is required by=C2=A0RFC 5295. But there=C2=A0the key label is=
 also ASCII printable string. Joe, do you remember what was the motivation =
to put 0x00 after the key label parameter?<u></u><u></u></p>
</div>
</div>
</blockquote>
<div>
<p class=3D"MsoNormal"><u></u>=C2=A0<u></u></p>
</div>
<div>
<p class=3D"MsoNormal">[Joe] the null after the key label is to provide a d=
elimiter between the key label and optional data.=C2=A0 Since the optional =
data can be arbitrary content the null prevents two different lablels=C2=A0=
with specially=C2=A0crafted optional data from deriving
 the same key.=C2=A0=C2=A0<u></u><u></u></p>
</div>
<div>
<p class=3D"MsoNormal">=C2=A0<u></u><u></u></p>
</div>
<blockquote style=3D"border-top:none;border-right:none;border-bottom:none;b=
order-left:1pt solid rgb(204,204,204);padding:0in 0in 0in 6pt;margin-left:4=
.8pt;margin-right:0in">
<div>
<div>
<p class=3D"MsoNormal"><u></u>=C2=A0<u></u></p>
</div>
<div>
<p class=3D"MsoNormal">Oleg<u></u><u></u></p>
</div>
<div>
<p class=3D"MsoNormal"><u></u>=C2=A0<u></u></p>
</div>
<div>
<p class=3D"MsoNormal"><u></u>=C2=A0<u></u></p>
</div>
<div>
<div>
<p class=3D"MsoNormal">On Thu, Oct 22, 2020 at 2:54 AM Joseph Salowey &lt;<=
a href=3D"mailto:joe@salowey.net" target=3D"_blank">joe@salowey.net</a>&gt;=
 wrote:<u></u><u></u></p>
</div>
<blockquote style=3D"border-top:none;border-right:none;border-bottom:none;b=
order-left:1pt solid rgb(204,204,204);padding:0in 0in 0in 6pt;margin-left:4=
.8pt;margin-right:0in">
<div>
<div>
<p class=3D"MsoNormal">(I accidentally=C2=A0dropped this list from the conv=
ersation)<u></u><u></u></p>
</div>
<p class=3D"MsoNormal"><u></u>=C2=A0<u></u></p>
<div>
<div>
<p class=3D"MsoNormal">On Wed, Oct 21, 2020 at 4:48 PM Jorge Vergara &lt;<a=
 href=3D"mailto:jovergar@microsoft.com" target=3D"_blank">jovergar@microsof=
t.com</a>&gt; wrote:<u></u><u></u></p>
</div>
<blockquote style=3D"border-top:none;border-right:none;border-bottom:none;b=
order-left:1pt solid rgb(204,204,204);padding:0in 0in 0in 6pt;margin-left:4=
.8pt;margin-right:0in">
<div>
<div>
<p class=3D"MsoNormal">&gt;[Joe] Yes this is a concern and I think your=C2=
=A0interpretation of the current document is also valid.=C2=A0 There may be=
 more than one implementation.=C2=A0 So what you implemented was:<u></u><u>=
</u></p>
<p class=3D"MsoNormal">&gt;=C2=A0<u></u><u></u></p>
<p class=3D"MsoNormal">&gt;IMCK[j] =3D TLS-PRF(S-IMCK[j-1], &quot;Inner Met=
hods Compound Keys&quot;,=C2=A0<span style=3D"font-size:10.5pt;color:rgb(44=
,67,83)">IMSK[j]) =3D P_&lt;hash&gt;(S-IMCK[j-1], &quot;Inner Methods Compo=
und Keys&quot; | IMSK[j])</span><u></u><u></u></p>
<p class=3D"MsoNormal">=C2=A0<u></u><u></u></p>
<p class=3D"MsoNormal">Yes, this is what I implemented. As you mentioned, t=
here are multiple possible interpretations of this since the TEAP usage is =
incorrect. However, my implementation does interop
 with at least 2 large vendor implementations. If the implementations were =
using different calculations here, the Wi-Fi/Ethernet connections that depe=
nd on the MSK would fail. But since connections work, I can assume we are a=
ll using the same implementation
 and arriving at the same MSK. Cisco is one of the implementations that I h=
ave tested against which is why I was hoping Oleg may offer more context as=
 to what he has seen.<u></u><u></u></p>
<p class=3D"MsoNormal">=C2=A0<u></u><u></u></p>
</div>
</div>
</blockquote>
<div>
<p class=3D"MsoNormal">[Joe] I can hope Jouni can chime in on this as well.=
=C2=A0 I think the original intent was to not include the length as is your=
 suggestion.=C2=A0<u></u><u></u></p>
</div>
<div>
<p class=3D"MsoNormal"><u></u>=C2=A0<u></u></p>
</div>
<div>
<p class=3D"MsoNormal">=C2=A0<u></u><u></u></p>
</div>
<blockquote style=3D"border-top:none;border-right:none;border-bottom:none;b=
order-left:1pt solid rgb(204,204,204);padding:0in 0in 0in 6pt;margin-left:4=
.8pt;margin-right:0in">
<div>
<div>
<p class=3D"MsoNormal">&gt;[Joe]<span style=3D"font-size:10.5pt;color:rgb(4=
4,67,83)"> Does the revision in 5167 match you implementation ( I don&#39;t=
 think Jouni&#39;s=C2=A0comment changes the underly=C2=A0calculation, just =
its
 representation)?=C2=A0</span><u></u><u></u></p>
<p class=3D"MsoNormal">=C2=A0<u></u><u></u></p>
<p class=3D"MsoNormal">I have not implemented this portion of the RFC as I =
found it too unclear to work with. Thus I can=E2=80=99t comment on what imp=
lementations may be doing. However, I agree with the current
 revision in 5167 as the most natural interpretation. If others have implem=
ented this portion of the RFC then certainly their comments would be welcom=
e.<u></u><u></u></p>
<p class=3D"MsoNormal"><u></u>=C2=A0<u></u></p>
</div>
</div>
</blockquote>
<blockquote style=3D"border-top:none;border-right:none;border-bottom:none;b=
order-left:1pt solid rgb(204,204,204);padding:0in 0in 0in 6pt;margin-left:4=
.8pt;margin-right:0in">
<div>
<div>
<p class=3D"MsoNormal">By the way, we=E2=80=99ve dropped the EMU group on o=
ur replies here =E2=80=93 not sure if intentional or not.<u></u><u></u></p>
<p class=3D"MsoNormal">=C2=A0<u></u><u></u></p>
<p class=3D"MsoNormal">Jorge Vergara<u></u><u></u></p>
<p class=3D"MsoNormal">=C2=A0<u></u><u></u></p>
<div style=3D"border-right:none;border-bottom:none;border-left:none;border-=
top:1pt solid rgb(225,225,225);padding:3pt 0in 0in">
<p class=3D"MsoNormal"><b>From:</b> Joseph Salowey &lt;<a href=3D"mailto:jo=
e@salowey.net" target=3D"_blank">joe@salowey.net</a>&gt;
<br>
<b>Sent:</b> Wednesday, October 21, 2020 4:36 PM<br>
<b>To:</b> Jorge Vergara &lt;<a href=3D"mailto:jovergar@microsoft.com" targ=
et=3D"_blank">jovergar@microsoft.com</a>&gt;<br>
<b>Subject:</b> Re: Proposed resolution for TEAP errata for 5128<u></u><u><=
/u></p>
</div>
<p class=3D"MsoNormal">=C2=A0<u></u><u></u></p>
<div>
<div>
<p class=3D"MsoNormal">=C2=A0<u></u><u></u></p>
</div>
<p class=3D"MsoNormal">=C2=A0<u></u><u></u></p>
<div>
<div>
<p class=3D"MsoNormal">On Wed, Oct 21, 2020 at 3:20 PM Jorge Vergara &lt;<a=
 href=3D"mailto:jovergar@microsoft.com" target=3D"_blank">jovergar@microsof=
t.com</a>&gt; wrote:<u></u><u></u></p>
</div>
<blockquote style=3D"border-top:none;border-right:none;border-bottom:none;b=
order-left:1pt solid rgb(204,204,204);padding:0in 0in 0in 6pt;margin:5pt 0i=
n 5pt 4.8pt">
<div>
<div>
<p class=3D"MsoNormal">In theory I agree this is a possible resolution. How=
ever, this doesn=E2=80=99t match any of the current TEAP implementations th=
at I am aware of. Perhaps Oleg can weigh in as well in terms
 of what he=E2=80=99s seen.<u></u><u></u></p>
<p class=3D"MsoNormal">=C2=A0<u></u><u></u></p>
<p class=3D"MsoNormal">I believe all current implementations treat 60 as th=
e desired output length without treating as a seed. In terms of P_&lt;hash&=
gt;, this means implementations are performing the calculation
 without a seed.<u></u><u></u></p>
<p class=3D"MsoNormal">=C2=A0<u></u><u></u></p>
<p class=3D"MsoNormal">RFC 5246 defines the TLS 1.2 PRF as:<u></u><u></u></=
p>
<p class=3D"MsoNormal">PRF(secret, label, seed) =3D P_&lt;hash&gt;(secret, =
label + seed)<u></u><u></u></p>
<p class=3D"MsoNormal">=C2=A0<u></u><u></u></p>
<p class=3D"MsoNormal">So the calculation implementations are currently per=
forming with an empty seed ends up as:<u></u><u></u></p>
<p class=3D"MsoNormal">P_&lt;hash&gt;(secret, label)<u></u><u></u></p>
<p class=3D"MsoNormal">=C2=A0<u></u><u></u></p>
<p class=3D"MsoNormal">Note that in RFC 5295, the length *is* explicitly me=
ntioned as being concatenated with the label<u></u><u></u></p>
<p class=3D"MsoNormal">USRK =3D KDF(EMSK, key label | &quot;\0&quot; | opti=
onal data | length)<u></u><u></u></p>
<p class=3D"MsoNormal">=C2=A0<u></u><u></u></p>
<p class=3D"MsoNormal">RFC 5295 is mentioned earlier in the TEAP RFC, in th=
e section covered by errata 5127. *However* it is not mentioned in this por=
tion of the RFC. Since this calculation is not on
 an EMSK, I do not believe RFC 2395 applies and this is likely why implemen=
tations went with the seedless P_&lt;hash&gt;(secret, label) calculation in=
stead.<u></u><u></u></p>
<p class=3D"MsoNormal">=C2=A0<u></u><u></u></p>
<p class=3D"MsoNormal">Is there concern about updating the RFC in a way tha=
t breaks existing implementations?<u></u><u></u></p>
<p class=3D"MsoNormal">=C2=A0<u></u><u></u></p>
</div>
</div>
</blockquote>
<div>
<p class=3D"MsoNormal">[Joe] Yes this is a concern and I think your=C2=A0in=
terpretation of the current document is also valid.=C2=A0 There may be more=
 than one implementation.=C2=A0 So what you implemented was:<u></u><u></u><=
/p>
</div>
<div>
<p class=3D"MsoNormal">=C2=A0<u></u><u></u></p>
</div>
<div>
<p class=3D"MsoNormal">IMCK[j] =3D TLS-PRF(S-IMCK[j-1], &quot;Inner Methods=
 Compound Keys&quot;,=C2=A0<span style=3D"font-size:10.5pt;color:rgb(44,67,=
83)">IMSK[j]) =3D P_&lt;hash&gt;(S-IMCK[j-1], &quot;Inner Methods Compound =
Keys&quot; | IMSK[j])</span><u></u><u></u></p>
</div>
<div>
<p class=3D"MsoNormal">=C2=A0<u></u><u></u></p>
</div>
<div>
<p class=3D"MsoNormal">taken out to 60 bytes.=C2=A0 The problem is that the=
 TEAP spec references a TLS-PRF in a way that it does not define.=C2=A0 I t=
hink the errata points out the definition that should be used:<u></u><u></u=
></p>
</div>
<div>
<p class=3D"MsoNormal">=C2=A0<u></u><u></u></p>
</div>
<div>
<p class=3D"MsoNormal">PRF(secret, label, seed) =3D P_&lt;hash&gt;(secret, =
label + seed)<u></u><u></u></p>
</div>
<div>
<p class=3D"MsoNormal">=C2=A0<u></u><u></u></p>
</div>
<div>
<p class=3D"MsoNormal">That does not include length so the 60 in the origin=
al definition=C2=A0is ambiguous.=C2=A0 =C2=A0The new text would then be som=
ething like:<u></u><u></u></p>
</div>
<div>
<p class=3D"MsoNormal">=C2=A0<u></u><u></u></p>
</div>
<div>
<p class=3D"MsoNormal">IMCK[j] =3D TLS-PRF(S-IMCK[j-1], &quot;Inner Methods=
 Compound Keys&quot;,=C2=A0<span style=3D"font-size:10.5pt;color:rgb(44,67,=
83)">IMSK[j])=C2=A0 to generate a length of 60 bytes</span><u></u><u></u></=
p>
</div>
<div>
<p class=3D"MsoNormal">=C2=A0<u></u><u></u></p>
</div>
<div>
<p class=3D"MsoNormal"><span style=3D"font-size:10.5pt;color:rgb(44,67,83)"=
>Does the revision in 5167 match you implementation ( I don&#39;t think Jou=
ni&#39;s=C2=A0comment changes the underly=C2=A0calculation, just its repres=
entation)?=C2=A0</span><u></u><u></u></p>
</div>
<div>
<p class=3D"MsoNormal">=C2=A0<u></u><u></u></p>
</div>
<div>
<p class=3D"MsoNormal">=C2=A0<u></u><u></u></p>
</div>
<div>
<p class=3D"MsoNormal">=C2=A0<u></u><u></u></p>
</div>
<div>
<p class=3D"MsoNormal">=C2=A0<u></u><u></u></p>
</div>
<div>
<p class=3D"MsoNormal">=C2=A0<u></u><u></u></p>
</div>
<blockquote style=3D"border-top:none;border-right:none;border-bottom:none;b=
order-left:1pt solid rgb(204,204,204);padding:0in 0in 0in 6pt;margin:5pt 0i=
n 5pt 4.8pt">
<div>
<div>
<p class=3D"MsoNormal">Jorge Vergara<u></u><u></u></p>
<p class=3D"MsoNormal">=C2=A0<u></u><u></u></p>
<div style=3D"border-right:none;border-bottom:none;border-left:none;border-=
top:1pt solid rgb(225,225,225);padding:3pt 0in 0in">
<p class=3D"MsoNormal"><b>From:</b> Joseph Salowey &lt;<a href=3D"mailto:jo=
e@salowey.net" target=3D"_blank">joe@salowey.net</a>&gt;
<br>
<b>Sent:</b> Wednesday, October 21, 2020 2:34 PM<br>
<b>To:</b> EMU WG &lt;<a href=3D"mailto:emu@ietf.org" target=3D"_blank">emu=
@ietf.org</a>&gt;; Jouni Malinen &lt;<a href=3D"mailto:j@w1.fi" target=3D"_=
blank">j@w1.fi</a>&gt;; Jorge Vergara &lt;<a href=3D"mailto:jovergar@micros=
oft.com" target=3D"_blank">jovergar@microsoft.com</a>&gt;; Oleg
 Pekar (olpekar) &lt;<a href=3D"mailto:olpekar@cisco.com" target=3D"_blank"=
>olpekar@cisco.com</a>&gt;<br>
<b>Subject:</b> Proposed resolution for TEAP errata for 5128<u></u><u></u><=
/p>
</div>
<p class=3D"MsoNormal">=C2=A0<u></u><u></u></p>
<div>
<p class=3D"MsoNormal">Errata 5128:=C2=A0<a href=3D"https://nam06.safelinks=
.protection.outlook.com/?url=3Dhttps%3A%2F%2Fwww.rfc-editor.org%2Ferrata%2F=
eid5128&amp;data=3D04%7C01%7Cjovergar%40microsoft.com%7C1607f5f05ab64c11228=
108d876ab0304%7C72f988bf86f141af91ab2d7cd011db47%7C1%7C0%7C6373898241507925=
37%7CUnknown%7CTWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1h=
aWwiLCJXVCI6Mn0%3D%7C1000&amp;sdata=3D%2FY77gd5%2BZnRPHT%2Bkq2KkTJPlkK2hIu%=
2FfFejHlj9e7CQ%3D&amp;reserved=3D0" target=3D"_blank">https://www.rfc-edito=
r.org/errata/eid5128</a><u></u><u></u></p>
<div>
<p class=3D"MsoNormal">Proposed State: Verified<u></u><u></u></p>
</div>
<div>
<p class=3D"MsoNormal">Revision:<u></u><u></u></p>
</div>
<div>
<p class=3D"MsoNormal">=C2=A0<u></u><u></u></p>
</div>
<div>
<p class=3D"MsoNormal">Section 5.2. says<u></u><u></u></p>
</div>
<div>
<p style=3D"margin-right:3.75pt;margin-bottom:7.5pt;margin-left:3.75pt">
<br>
IMCK[j] =3D TLS-PRF(S-IMCK[j-1], &quot;Inner Methods Compound Keys&quot;,<b=
r>
=C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 IMSK[j], 60)<br>
<br>
It should say:<br>
<br>
IMCK[j] =3D TLS-PRF(S-IMCK[j-1], &quot;Inner Methods Compound Keys&quot;,=
=C2=A0<span style=3D"font-size:10.5pt;font-family:Arial,sans-serif;color:rg=
b(44,67,83)">IMSK[j] | 60)</span><u></u><u></u></p>
<p style=3D"margin-right:3.75pt;margin-bottom:7.5pt;margin-left:3.75pt">
<span style=3D"font-size:10.5pt;font-family:Arial,sans-serif;color:rgb(44,6=
7,83)">Note:=C2=A0=C2=A0</span><u></u><u></u></p>
<p class=3D"MsoNormal">According to<br>
<br>
RFC5246 The Transport Layer Security (TLS) Protocol Version 1.2<br>
<br>
5. HMAC and the Pseudorandom Function<br>
<br>
&quot;TLS&#39;s PRF is created by applying P_hash to the secret as:<br>
<br>
PRF(secret, label, seed) =3D P_&lt;hash&gt;(secret, label + seed)&quot;<u><=
/u><u></u></p>
</div>
<div>
<p class=3D"MsoNormal">=C2=A0<u></u><u></u></p>
</div>
<div>
<p class=3D"MsoNormal">In terms of P_&lt;hash&gt; this would look like the =
following with the length represented as a 2 byte value in network byte ord=
er:<u></u><u></u></p>
</div>
<div>
<p class=3D"MsoNormal">=C2=A0<u></u><u></u></p>
</div>
<div>
<p class=3D"MsoNormal">IMCK[j] =3D P_&lt;hash&gt;(S-IMCK[j-1], &quot;Inner =
Methods Compound Keys&quot; |=C2=A0<span style=3D"font-size:10.5pt;color:rg=
b(44,67,83)">IMSK[j] | 0x00 | 0x3C)</span><u></u><u></u></p>
</div>
<div>
<p class=3D"MsoNormal">=C2=A0<u></u><u></u></p>
</div>
<div>
<p class=3D"MsoNormal">=C2=A0<u></u><u></u></p>
</div>
</div>
</div>
</div>
</blockquote>
</div>
</div>
</div>
</div>
</blockquote>
</div>
</div>
</blockquote>
</div>
</div>
</blockquote>
</div>
</div>
</blockquote>
</div>
</blockquote>
</div>
</div>
</div>
</div>

</blockquote></div>

--0000000000008d5b7805b246190b--


From nobody Thu Oct 22 14:02:54 2020
Return-Path: <mcr+ietf@sandelman.ca>
X-Original-To: emu@ietfa.amsl.com
Delivered-To: emu@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 1FD643A1033 for <emu@ietfa.amsl.com>; Thu, 22 Oct 2020 14:02:52 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.899
X-Spam-Level: 
X-Spam-Status: No, score=-1.899 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, SPF_HELO_NONE=0.001, SPF_PASS=-0.001, URIBL_BLOCKED=0.001] autolearn=ham autolearn_force=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 04Wf2eID9MrA for <emu@ietfa.amsl.com>; Thu, 22 Oct 2020 14:02:50 -0700 (PDT)
Received: from tuna.sandelman.ca (tuna.sandelman.ca [IPv6:2607:f0b0:f:3:216:3eff:fe7c:d1f3]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id D05083A1032 for <emu@ietf.org>; Thu, 22 Oct 2020 14:02:50 -0700 (PDT)
Received: from localhost (localhost [127.0.0.1]) by tuna.sandelman.ca (Postfix) with ESMTP id CF5E7389BA; Thu, 22 Oct 2020 17:09:09 -0400 (EDT)
Received: from tuna.sandelman.ca ([127.0.0.1]) by localhost (localhost [127.0.0.1]) (amavisd-new, port 10024) with LMTP id 4wSHFgz3BL8k; Thu, 22 Oct 2020 17:09:09 -0400 (EDT)
Received: from sandelman.ca (obiwan.sandelman.ca [IPv6:2607:f0b0:f:2::247]) by tuna.sandelman.ca (Postfix) with ESMTP id 5E7933899E; Thu, 22 Oct 2020 17:09:09 -0400 (EDT)
Received: from localhost (localhost [IPv6:::1]) by sandelman.ca (Postfix) with ESMTP id B1D911FB; Thu, 22 Oct 2020 17:02:48 -0400 (EDT)
From: Michael Richardson <mcr+ietf@sandelman.ca>
To: Hannes Tschofenig <Hannes.Tschofenig@arm.com>
cc: "emu\@ietf.org" <emu@ietf.org>
In-Reply-To: <AM0PR08MB3716CCE7C843CAA50B86995DFA1D0@AM0PR08MB3716.eurprd08.prod.outlook.com>
References: <AM0PR08MB371647618F993B8C5BA6EB5FFA1C0@AM0PR08MB3716.eurprd08.prod.outlook.com> <15861.1603298751@localhost> <AM0PR08MB3716CCE7C843CAA50B86995DFA1D0@AM0PR08MB3716.eurprd08.prod.outlook.com>
X-Mailer: MH-E 8.6+git; nmh 1.7+dev; GNU Emacs 26.1
X-Face: $\n1pF)h^`}$H>Hk{L"x@)JS7<%Az}5RyS@k9X%29-lHB$Ti.V>2bi.~ehC0; <'$9xN5Ub# z!G,p`nR&p7Fz@^UXIn156S8.~^@MJ*mMsD7=QFeq%AL4m<nPbLgmtKK-5dC@#:k
MIME-Version: 1.0
Content-Type: multipart/signed; boundary="=-=-="; micalg=pgp-sha512; protocol="application/pgp-signature"
Date: Thu, 22 Oct 2020 17:02:48 -0400
Message-ID: <4677.1603400568@localhost>
Archived-At: <https://mailarchive.ietf.org/arch/msg/emu/dGQ18M5FQFvWbXHnuXoddyYwlZM>
Subject: Re: [Emu] draft-ietf-emu-eap-tls13-11: OCSP Stapling
X-BeenThere: emu@ietf.org
X-Mailman-Version: 2.1.29
Precedence: list
List-Id: "EAP Methods Update \(EMU\)" <emu.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/emu>, <mailto:emu-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/emu/>
List-Post: <mailto:emu@ietf.org>
List-Help: <mailto:emu-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/emu>, <mailto:emu-request@ietf.org?subject=subscribe>
X-List-Received-Date: Thu, 22 Oct 2020 21:02:52 -0000

--=-=-=
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: quoted-printable


Hannes Tschofenig <Hannes.Tschofenig@arm.com> wrote:
    > Thanks for the question. I am objecting to the mandatory use of OCSP =
for TLS 1.3 in EAP-TLS.
    > I am fine with having it optional.

okay, so it's not about the stapling, at all for you, it's about the OCSP i=
tself.

=2D-
Michael Richardson <mcr+IETF@sandelman.ca>   . o O ( IPv6 I=C3=B8T consulti=
ng )
           Sandelman Software Works Inc, Ottawa and Worldwide





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

-----BEGIN PGP SIGNATURE-----

iQEzBAEBCgAdFiEEbsyLEzg/qUTA43uogItw+93Q3WUFAl+R83gACgkQgItw+93Q
3WVDxwf+K/UqtUqUlbA+nqowB1vQHISBl/jFPAFsOkvRtwq/m48JA3Nz3R5PvvZK
Djstg343lvdHf2fn1Hbr61IM33DnTHo31DUZvQYvShbFNHJYv1JAha4mrpxALPq9
lr6m7tRCjQfFzITzmxhf5kIpjxc4zKVcoW+A0SsG5zIATW39BD6DHSzRRfYrpmZ6
H1ITv20VeWqscP3g8XEM5RFQpu5glKH1pHvTY0HCsQ08hLgp+9QHWueDObG5e0Ej
HrlyAMbnBQMyGXM/s7MwS5mvJNGbYuhXMWgDcFS/zKSIYCyCwEHQlOL6PjbE4Hr3
GDwUONbWEvbOPyubltJuDiWGWzcb6A==
=zZoT
-----END PGP SIGNATURE-----
--=-=-=--


From nobody Thu Oct 22 14:12:21 2020
Return-Path: <joe@salowey.net>
X-Original-To: emu@ietfa.amsl.com
Delivered-To: emu@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 7711F3A104E for <emu@ietfa.amsl.com>; Thu, 22 Oct 2020 14:12:20 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.898
X-Spam-Level: 
X-Spam-Status: No, score=-1.898 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, HTML_MESSAGE=0.001, SPF_HELO_NONE=0.001, SPF_PASS=-0.001, URIBL_BLOCKED=0.001] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (2048-bit key) header.d=salowey-net.20150623.gappssmtp.com
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 iwkv30H-2P9v for <emu@ietfa.amsl.com>; Thu, 22 Oct 2020 14:12:18 -0700 (PDT)
Received: from mail-qt1-x836.google.com (mail-qt1-x836.google.com [IPv6:2607:f8b0:4864:20::836]) (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 CBC363A104C for <emu@ietf.org>; Thu, 22 Oct 2020 14:12:18 -0700 (PDT)
Received: by mail-qt1-x836.google.com with SMTP id c5so2438112qtw.3 for <emu@ietf.org>; Thu, 22 Oct 2020 14:12:18 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=salowey-net.20150623.gappssmtp.com; s=20150623; h=mime-version:references:in-reply-to:from:date:message-id:subject:to :cc; bh=dcQoP7q/xxsfGw8diU7DULRMlOGgp2QASKmcz3nL0d0=; b=SemZz0LTxBDQ1+RYc9+xcBWXUsI1R9uTKORiQYOksWP+gf5OEWu5qkoTEE28uspJTC xjgEVkL7qLEGUr1wSzMv4YoEpXdRP6UobPn8Of+xiNQasP8k1Y0PAEo4sIbQgJ3tibel U+UionZ67Lh2rbaebePkw/E29SuSZvY8oaYVWc8/3nVOq+t759fj/lLPx3GYnEMGUWeD GbioGqWCNIturDFpvMRMDuqPfh45Uzv0eZM7w6FgvihG2zM9tD90nzKOzIS2QPRpN7tC UhBp1arsIEh7JfQmnvQfSBl0U+cu3NaRMhgjBZ0x8gLRURuiTKKT78emAyOkmWitfTwq X7CQ==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:mime-version:references:in-reply-to:from:date :message-id:subject:to:cc; bh=dcQoP7q/xxsfGw8diU7DULRMlOGgp2QASKmcz3nL0d0=; b=lHg/0MXorXgwkP6EJmQaFKHiFsJjxct3tA0tyLH068EuFMxVml2UbL0G6Bc1m9k9JX CdDkIrOcGhGEF/RbJansIeUziheAiQL0WrvA6U6uoH2vudfxJutgD48YzeE5L3agJxDm T+7/kyKsyZo4QidhwBc9Mt0/9BKkckijL59k22yzp+rlRvbYkVx3owi56dpPcSMG5Zec vlKMC0nER7KOFxBcVOAnM+49C/zlBXvg9cqcWZcTtu1jeixYEzm6WAtf/zSCDHR2Ly+V INxgI28KMPx1P56TF6IpiRQiShtvS9aar0fHrxBcH9mRkVFF4N39f+GuxcCyGTozIYeW KZMA==
X-Gm-Message-State: AOAM5309BwGOpsdHgeUc9xNYoY+5BrDDv6U7ghwUXoRrp/EUOcWY+TnF FFZx4oftSe4XB2FQl7BTpwQuaZ6rHghSmKhi7XbbCw==
X-Google-Smtp-Source: ABdhPJyJTlLym9wjvAIkFhdP8sZIU0W0RFg/h9LaoEuwKj3d4TquNsfKLK/FtQ3R4N+CopDYcIP20LF2PKgBi5jy9r8=
X-Received: by 2002:ac8:1c57:: with SMTP id j23mr4018547qtk.231.1603401137735;  Thu, 22 Oct 2020 14:12:17 -0700 (PDT)
MIME-Version: 1.0
References: <AM0PR08MB371647618F993B8C5BA6EB5FFA1C0@AM0PR08MB3716.eurprd08.prod.outlook.com> <AD94F3FF-31A7-4F44-95F7-6A7E70FA8D27@cisco.com>
In-Reply-To: <AD94F3FF-31A7-4F44-95F7-6A7E70FA8D27@cisco.com>
From: Joseph Salowey <joe@salowey.net>
Date: Thu, 22 Oct 2020 14:12:06 -0700
Message-ID: <CAOgPGoD3MQu=Hv6HTfug0XredaRt_T7oD7z_uwnATmHku9DmLg@mail.gmail.com>
To: Eliot Lear <lear=40cisco.com@dmarc.ietf.org>
Cc: Hannes Tschofenig <Hannes.Tschofenig@arm.com>, "emu@ietf.org" <emu@ietf.org>
Content-Type: multipart/alternative; boundary="0000000000003f5cef05b248eb0a"
Archived-At: <https://mailarchive.ietf.org/arch/msg/emu/Sq-gU3BEMJjalfcAaRwGDL8u5Aw>
Subject: Re: [Emu] draft-ietf-emu-eap-tls13-11: OCSP Stapling
X-BeenThere: emu@ietf.org
X-Mailman-Version: 2.1.29
Precedence: list
List-Id: "EAP Methods Update \(EMU\)" <emu.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/emu>, <mailto:emu-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/emu/>
List-Post: <mailto:emu@ietf.org>
List-Help: <mailto:emu-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/emu>, <mailto:emu-request@ietf.org?subject=subscribe>
X-List-Received-Date: Thu, 22 Oct 2020 21:12:21 -0000

--0000000000003f5cef05b248eb0a
Content-Type: text/plain; charset="UTF-8"

On Thu, Oct 22, 2020 at 8:08 AM Eliot Lear <lear=40cisco.com@dmarc.ietf.org>
wrote:

> +1.  How does anyone even do OCSP without having first gotten onto the
> network?
>
>
[Joe] THat is what OCSP stapling is supposed to solve since the OCSP
messages are sent in the TLS handshake.   I believe there are some EAP-TLS
implementations that support OCSP, but I am not sure if it is actually
deployed.


> Eliot
>
> On 21 Oct 2020, at 11:02, Hannes Tschofenig <Hannes.Tschofenig@arm.com>
> wrote:
>
> Hi all,
>
> this draft mandates OCSCP stapling (for use with TLS 1.3 in EAP-TLS) and I
> believe this is a problem for implementations. This extra burden is IMHO
> unjustified. For the type of deployments where EAP is used there is no need
> for a mandatory certificate revocation checking with OCSP.
>
> Having it optional, like the use of many other TLS extensions, is fine for
> me. FWIW even TLS 1.3, which is used in a more generic environment, does
> not mandate the use of OCSP stapling.
>
> This requirement will make the problem described in
> draft-ietf-emu-eaptlscert worse. I am sure the authors are aware of this
> fact since they are also co-authors of draft-ietf-emu-eaptlscert.
>
> Ciao
> Hannes
> IMPORTANT NOTICE: The contents of this email and any attachments are
> confidential and may also be privileged. If you are not the intended
> recipient, please notify the sender immediately and do not disclose the
> contents to any other person, use it for any purpose, or store or copy the
> information in any medium. Thank you.
> _______________________________________________
> Emu mailing list
> Emu@ietf.org
> https://www.ietf.org/mailman/listinfo/emu
>
>
> _______________________________________________
> Emu mailing list
> Emu@ietf.org
> https://www.ietf.org/mailman/listinfo/emu
>

--0000000000003f5cef05b248eb0a
Content-Type: text/html; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable

<div dir=3D"ltr"><div dir=3D"ltr"><br></div><br><div class=3D"gmail_quote">=
<div dir=3D"ltr" class=3D"gmail_attr">On Thu, Oct 22, 2020 at 8:08 AM Eliot=
 Lear &lt;lear=3D<a href=3D"mailto:40cisco.com@dmarc.ietf.org">40cisco.com@=
dmarc.ietf.org</a>&gt; wrote:<br></div><blockquote class=3D"gmail_quote" st=
yle=3D"margin:0px 0px 0px 0.8ex;border-left:1px solid rgb(204,204,204);padd=
ing-left:1ex"><div style=3D"overflow-wrap: break-word;">+1.=C2=A0 How does =
anyone even do OCSP without having first gotten onto the network?<div><br><=
/div></div></blockquote><div><br></div><div>[Joe] THat is what OCSP staplin=
g is supposed to solve since the OCSP messages are sent in the TLS handshak=
e.=C2=A0 =C2=A0I believe there are some EAP-TLS implementations that suppor=
t OCSP, but I am not sure if it is actually deployed.=C2=A0=C2=A0</div><div=
>=C2=A0</div><blockquote class=3D"gmail_quote" style=3D"margin:0px 0px 0px =
0.8ex;border-left:1px solid rgb(204,204,204);padding-left:1ex"><div style=
=3D"overflow-wrap: break-word;"><div></div><div>Eliot</div><div><br><div><b=
lockquote type=3D"cite"><div>On 21 Oct 2020, at 11:02, Hannes Tschofenig &l=
t;<a href=3D"mailto:Hannes.Tschofenig@arm.com" target=3D"_blank">Hannes.Tsc=
hofenig@arm.com</a>&gt; wrote:</div><br><div><div style=3D"font-family:Helv=
etica;font-size:16px;font-style:normal;font-variant-caps:normal;font-weight=
:normal;letter-spacing:normal;text-align:start;text-indent:0px;text-transfo=
rm:none;white-space:normal;word-spacing:0px;text-decoration:none"><div styl=
e=3D"margin:0in;font-size:11pt;font-family:Calibri,sans-serif">Hi all,<span=
>=C2=A0</span><u></u><u></u></div><div style=3D"margin:0in;font-size:11pt;f=
ont-family:Calibri,sans-serif"><u></u>=C2=A0<u></u></div><div style=3D"marg=
in:0in;font-size:11pt;font-family:Calibri,sans-serif">this draft mandates O=
CSCP stapling (for use with TLS 1.3 in EAP-TLS) and I believe this is a pro=
blem for implementations. This extra burden is IMHO unjustified. For the ty=
pe of deployments where EAP is used there is no need for a mandatory certif=
icate revocation checking with OCSP.<u></u><u></u></div><div style=3D"margi=
n:0in;font-size:11pt;font-family:Calibri,sans-serif"><u></u>=C2=A0<u></u></=
div><div style=3D"margin:0in;font-size:11pt;font-family:Calibri,sans-serif"=
>Having it optional, like the use of many other TLS extensions, is fine for=
 me. FWIW even TLS 1.3, which is used in a more generic environment, does n=
ot mandate the use of OCSP stapling.<u></u><u></u></div><div style=3D"margi=
n:0in;font-size:11pt;font-family:Calibri,sans-serif"><u></u>=C2=A0<u></u></=
div><div style=3D"margin:0in;font-size:11pt;font-family:Calibri,sans-serif"=
>This requirement will make the problem described in draft-ietf-emu-eaptlsc=
ert worse. I am sure the authors are aware of this fact since they are also=
 co-authors of draft-ietf-emu-eaptlscert.<u></u><u></u></div><div style=3D"=
margin:0in;font-size:11pt;font-family:Calibri,sans-serif"><u></u>=C2=A0<u><=
/u></div><div style=3D"margin:0in;font-size:11pt;font-family:Calibri,sans-s=
erif">Ciao<u></u><u></u></div><div style=3D"margin:0in;font-size:11pt;font-=
family:Calibri,sans-serif">Hannes<u></u><u></u></div></div><span style=3D"f=
ont-family:Helvetica;font-size:16px;font-style:normal;font-variant-caps:nor=
mal;font-weight:normal;letter-spacing:normal;text-align:start;text-indent:0=
px;text-transform:none;white-space:normal;word-spacing:0px;text-decoration:=
none;float:none;display:inline">IMPORTANT NOTICE: The contents of this emai=
l and any attachments are confidential and may also be privileged. If you a=
re not the intended recipient, please notify the sender immediately and do =
not disclose the contents to any other person, use it for any purpose, or s=
tore or copy the information in any medium. Thank you. ____________________=
___________________________</span><br style=3D"font-family:Helvetica;font-s=
ize:16px;font-style:normal;font-variant-caps:normal;font-weight:normal;lett=
er-spacing:normal;text-align:start;text-indent:0px;text-transform:none;whit=
e-space:normal;word-spacing:0px;text-decoration:none"><span style=3D"font-f=
amily:Helvetica;font-size:16px;font-style:normal;font-variant-caps:normal;f=
ont-weight:normal;letter-spacing:normal;text-align:start;text-indent:0px;te=
xt-transform:none;white-space:normal;word-spacing:0px;text-decoration:none;=
float:none;display:inline">Emu mailing list</span><br style=3D"font-family:=
Helvetica;font-size:16px;font-style:normal;font-variant-caps:normal;font-we=
ight:normal;letter-spacing:normal;text-align:start;text-indent:0px;text-tra=
nsform:none;white-space:normal;word-spacing:0px;text-decoration:none"><a hr=
ef=3D"mailto:Emu@ietf.org" style=3D"font-family:Helvetica;font-size:16px;fo=
nt-style:normal;font-variant-caps:normal;font-weight:normal;letter-spacing:=
normal;text-align:start;text-indent:0px;text-transform:none;white-space:nor=
mal;word-spacing:0px" target=3D"_blank">Emu@ietf.org</a><br style=3D"font-f=
amily:Helvetica;font-size:16px;font-style:normal;font-variant-caps:normal;f=
ont-weight:normal;letter-spacing:normal;text-align:start;text-indent:0px;te=
xt-transform:none;white-space:normal;word-spacing:0px;text-decoration:none"=
><a href=3D"https://www.ietf.org/mailman/listinfo/emu" style=3D"font-family=
:Helvetica;font-size:16px;font-style:normal;font-variant-caps:normal;font-w=
eight:normal;letter-spacing:normal;text-align:start;text-indent:0px;text-tr=
ansform:none;white-space:normal;word-spacing:0px" target=3D"_blank">https:/=
/www.ietf.org/mailman/listinfo/emu</a></div></blockquote></div><br></div></=
div>_______________________________________________<br>
Emu mailing list<br>
<a href=3D"mailto:Emu@ietf.org" target=3D"_blank">Emu@ietf.org</a><br>
<a href=3D"https://www.ietf.org/mailman/listinfo/emu" rel=3D"noreferrer" ta=
rget=3D"_blank">https://www.ietf.org/mailman/listinfo/emu</a><br>
</blockquote></div></div>

--0000000000003f5cef05b248eb0a--


From nobody Thu Oct 22 17:13:51 2020
Return-Path: <mcr+ietf@sandelman.ca>
X-Original-To: emu@ietfa.amsl.com
Delivered-To: emu@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 9DBAE3A0ADE for <emu@ietfa.amsl.com>; Thu, 22 Oct 2020 17:13:49 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.899
X-Spam-Level: 
X-Spam-Status: No, score=-1.899 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, SPF_HELO_NONE=0.001, SPF_PASS=-0.001, URIBL_BLOCKED=0.001] autolearn=ham autolearn_force=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 LkSXWp_BrSX8 for <emu@ietfa.amsl.com>; Thu, 22 Oct 2020 17:13:47 -0700 (PDT)
Received: from tuna.sandelman.ca (tuna.sandelman.ca [209.87.249.19]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id E0F143A0AD8 for <emu@ietf.org>; Thu, 22 Oct 2020 17:13:46 -0700 (PDT)
Received: from localhost (localhost [127.0.0.1]) by tuna.sandelman.ca (Postfix) with ESMTP id 1EF61389AF for <emu@ietf.org>; Thu, 22 Oct 2020 20:20:06 -0400 (EDT)
Received: from tuna.sandelman.ca ([127.0.0.1]) by localhost (localhost [127.0.0.1]) (amavisd-new, port 10024) with LMTP id 8Q-pvtLx9RAP for <emu@ietf.org>; Thu, 22 Oct 2020 20:20:04 -0400 (EDT)
Received: from sandelman.ca (obiwan.sandelman.ca [IPv6:2607:f0b0:f:2::247]) by tuna.sandelman.ca (Postfix) with ESMTP id 98643389A7 for <emu@ietf.org>; Thu, 22 Oct 2020 20:20:04 -0400 (EDT)
Received: from localhost (localhost [IPv6:::1]) by sandelman.ca (Postfix) with ESMTP id 73EBCDAF for <emu@ietf.org>; Thu, 22 Oct 2020 20:13:43 -0400 (EDT)
From: Michael Richardson <mcr+ietf@sandelman.ca>
To: "emu\@ietf.org" <emu@ietf.org>
In-Reply-To: <CAOgPGoD3MQu=Hv6HTfug0XredaRt_T7oD7z_uwnATmHku9DmLg@mail.gmail.com>
References: <AM0PR08MB371647618F993B8C5BA6EB5FFA1C0@AM0PR08MB3716.eurprd08.prod.outlook.com> <AD94F3FF-31A7-4F44-95F7-6A7E70FA8D27@cisco.com> <CAOgPGoD3MQu=Hv6HTfug0XredaRt_T7oD7z_uwnATmHku9DmLg@mail.gmail.com>
X-Mailer: MH-E 8.6+git; nmh 1.7+dev; GNU Emacs 26.1
X-Face: $\n1pF)h^`}$H>Hk{L"x@)JS7<%Az}5RyS@k9X%29-lHB$Ti.V>2bi.~ehC0; <'$9xN5Ub# z!G,p`nR&p7Fz@^UXIn156S8.~^@MJ*mMsD7=QFeq%AL4m<nPbLgmtKK-5dC@#:k
MIME-Version: 1.0
Content-Type: multipart/signed; boundary="=-=-="; micalg=pgp-sha512; protocol="application/pgp-signature"
Date: Thu, 22 Oct 2020 20:13:43 -0400
Message-ID: <21741.1603412023@localhost>
Archived-At: <https://mailarchive.ietf.org/arch/msg/emu/45UF5eMIsNBT7EY-uOc_H8WyrhE>
Subject: Re: [Emu] draft-ietf-emu-eap-tls13-11: OCSP Stapling
X-BeenThere: emu@ietf.org
X-Mailman-Version: 2.1.29
Precedence: list
List-Id: "EAP Methods Update \(EMU\)" <emu.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/emu>, <mailto:emu-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/emu/>
List-Post: <mailto:emu@ietf.org>
List-Help: <mailto:emu-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/emu>, <mailto:emu-request@ietf.org?subject=subscribe>
X-List-Received-Date: Fri, 23 Oct 2020 00:13:50 -0000

--=-=-=
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: quoted-printable


Joseph Salowey <joe@salowey.net> wrote:
    > On Thu, Oct 22, 2020 at 8:08 AM Eliot Lear <lear=3D40cisco.com@dmarc.=
ietf.org>
    > wrote:

    >> +1.  How does anyone even do OCSP without having first gotten onto t=
he
    >> network?

    > [Joe] THat is what OCSP stapling is supposed to solve since the OCSP
    > messages are sent in the TLS handshake.   I believe there are some EA=
P-TLS
    > implementations that support OCSP, but I am not sure if it is actually
    > deployed.

I think that it should say, if you do OCSP, then you must staple.
But, the intro suggests that revocation checking is mandatory with TLS 1.3.
(I didn't double check if that's MUST, SHOULD, or what)

Since CRLs won't be fresh and can't be retrieved until online, then it seems
that OCSP is needed if one is going to revocation checking.

What I read in section 5.4 is that servers have to support OCSP stapling
requests.  I see a tiny bit of wiggle room as to whether the peer actually
must USE it :-)
Maybe that wiggle room can be made official for Hannes.

The document currently says: (1.0)

   Privacy is mandatory and achieved without any additional round-trips,
   revocation checking is mandatory and simplified with OCSP stapling,

and:

5.4.  Certificate Revocation

   This section updates Section 5.4 of [RFC5216].

   While certificates may have long validity periods, there are a number
   of reasons (e.g. key compromise, CA compromise, privilege withdrawn,
   etc.) why client, server, or sub-CA certificates have to be revoked
   before their expiry date.  Revocation of the EAP server's certificate
   is complicated by the fact that the EAP peer may not have Internet
   connectivity until authentication completes.

   EAP-TLS peers and servers supporting TLS 1.3 MUST support Certificate
   Status Requests (OCSP stapling) as specified in [RFC6066] and
   Section 4.4.2.1 of [RFC8446].  When EAP-TLS is used with TLS 1.3, the
   peer and server MUST use Certificate Status Requests [RFC6066] for
   the server's certificate chain and the EAP peer MUST treat a
   CertificateEntry (except the trust anchor) without a valid
   CertificateStatus extension as invalid and abort the handshake with
   an appropriate alert.  When EAP-TLS is used with TLS 1.3, the server
   MUST check the revocation status of the certificates in the client's
   certificate chain.

   The OCSP status handling in TLS 1.3 is different from earlier
   versions of TLS, see Section 4.4.2.1 of [RFC8446].  In TLS 1.3 the
   OCSP information is carried in the CertificateEntry containing the
   associated certificate instead of a separate CertificateStatus
   message as in [RFC4366].  This enables sending OCSP information for
   all certificates in the certificate chain.


    >> Eliot
    >>
    >> On 21 Oct 2020, at 11:02, Hannes Tschofenig <Hannes.Tschofenig@arm.c=
om>
    >> wrote:
    >>
    >> Hi all,
    >>
    >> this draft mandates OCSCP stapling (for use with TLS 1.3 in EAP-TLS)=
 and I
    >> believe this is a problem for implementations. This extra burden is =
IMHO
    >> unjustified. For the type of deployments where EAP is used there is =
no need
    >> for a mandatory certificate revocation checking with OCSP.
    >>
    >> Having it optional, like the use of many other TLS extensions, is fi=
ne for
    >> me. FWIW even TLS 1.3, which is used in a more generic environment, =
does
    >> not mandate the use of OCSP stapling.
    >>
    >> This requirement will make the problem described in
    >> draft-ietf-emu-eaptlscert worse. I am sure the authors are aware of =
this
    >> fact since they are also co-authors of draft-ietf-emu-eaptlscert.
    >>
    >> Ciao
    >> Hannes
    >> IMPORTANT NOTICE: The contents of this email and any attachments are
    >> confidential and may also be privileged. If you are not the intended
    >> recipient, please notify the sender immediately and do not disclose =
the
    >> contents to any other person, use it for any purpose, or store or co=
py the
    >> information in any medium. Thank you.
    >> _______________________________________________
    >> Emu mailing list
    >> Emu@ietf.org
    >> https://www.ietf.org/mailman/listinfo/emu
    >>
    >>
    >> _______________________________________________
    >> Emu mailing list
    >> Emu@ietf.org
    >> https://www.ietf.org/mailman/listinfo/emu
    >>

    > ----------------------------------------------------
    > Alternatives:

    > ----------------------------------------------------
    > _______________________________________________
    > Emu mailing list
    > Emu@ietf.org
    > https://www.ietf.org/mailman/listinfo/emu

=2D-
Michael Richardson <mcr+IETF@sandelman.ca>   . o O ( IPv6 I=C3=B8T consulti=
ng )
           Sandelman Software Works Inc, Ottawa and Worldwide





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

-----BEGIN PGP SIGNATURE-----

iQEzBAEBCgAdFiEEbsyLEzg/qUTA43uogItw+93Q3WUFAl+SIDcACgkQgItw+93Q
3WXeVAf9GKvAZgAYJwO1oeKj2j3vKG+w9/+t1J/0zBbl8WNM2bC7L2jLSGrmSx11
lT7N1ZHwD3F8uMevoX+cfYf5AYE+Xt4pMVI2w3kDxuFDqJoQyT47svInpSi59rG6
pFqfapBBDIfFvkrHbPj3MGduXL7IOyQLXBj5asYEWobW3FoPU7zu1p8dMNqkiaxK
7k+mzckA9P52eygGMtqbhsl1RPe4TpnPfrw71v13YMBEA/l/YoBniUOibVzNsP+8
u91HphYAoOj4wWa2g9/gyM0Je5iPrZs4JT27syU8wA9fTHVKV+Jz2ava8z58Ymfm
suTP2wlTAfshr0qjjQ4uPh6uuJg4gw==
=imug
-----END PGP SIGNATURE-----
--=-=-=--


From nobody Thu Oct 22 23:24:57 2020
Return-Path: <lear@cisco.com>
X-Original-To: emu@ietfa.amsl.com
Delivered-To: emu@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id B398D3A1263 for <emu@ietfa.amsl.com>; Thu, 22 Oct 2020 23:24:56 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -9.601
X-Spam-Level: 
X-Spam-Status: No, score=-9.601 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIMWL_WL_MED=-0.001, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, DKIM_VALID_EF=-0.1, SPF_PASS=-0.001, URIBL_BLOCKED=0.001, USER_IN_DEF_DKIM_WL=-7.5] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (1024-bit key) header.d=cisco.com
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 W1lU0Ys4CmEt for <emu@ietfa.amsl.com>; Thu, 22 Oct 2020 23:24:55 -0700 (PDT)
Received: from aer-iport-4.cisco.com (aer-iport-4.cisco.com [173.38.203.54]) (using TLSv1.2 with cipher DHE-RSA-SEED-SHA (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 486843A125F for <emu@ietf.org>; Thu, 22 Oct 2020 23:24:55 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=cisco.com; i=@cisco.com; l=305; q=dns/txt; s=iport; t=1603434295; x=1604643895; h=mime-version:subject:from:in-reply-to:date:cc: content-transfer-encoding:message-id:references:to; bh=Ehen43Xsmkykpq7+pXz9VzO+qcSqDVmOQ6t9UOheO54=; b=Txou/rrHCSSj9ffEGojco17Z9VoftWDvSY0t00Cn7Vb2Bdwx8Wth+7SL xHL5n7x/uK88Du2ZELIsu6pkdD7uGDbyndS8e3itgzS2Rs0kg0vZ8cE2j /ZRycrk9lcWUp1bctOrySKEZ6Eip/fEtriWu7oNmH+Fs4drME8tSh9HNx 8=;
X-IronPort-Anti-Spam-Filtered: true
X-IronPort-Anti-Spam-Result: =?us-ascii?q?A0AzAwCDdpJf/xbLJq1gHAEBAQEBAQc?= =?us-ascii?q?BARIBAQQEAQFAgU+CKoFFASAShGiJBYdvkGKLaQsBAQENAQEvBAEBhEoCggo?= =?us-ascii?q?mOBMCAwEBCwEBBQEBAQIBBgRthW2FcwYjVhALDgwCJgICVwaDOYJ9sFx2gTK?= =?us-ascii?q?FV4RmgQ4qjVSCAIERJwwQgk0+hCUYgxczgiwEuAWCdIMWl2MDH4MFAZ5YsBW?= =?us-ascii?q?DXgIEBgUCFYFrI4FXMxoIGxVlAYI/PRIZDZxoPwNoAgYBCQEBAwmOSAEB?=
X-IronPort-AV: E=Sophos;i="5.77,407,1596499200"; d="scan'208";a="30517972"
Received: from aer-iport-nat.cisco.com (HELO aer-core-2.cisco.com) ([173.38.203.22]) by aer-iport-4.cisco.com with ESMTP/TLS/DHE-RSA-SEED-SHA; 23 Oct 2020 06:24:51 +0000
Received: from dhcp-10-61-103-21.cisco.com (dhcp-10-61-103-21.cisco.com [10.61.103.21]) by aer-core-2.cisco.com (8.15.2/8.15.2) with ESMTPS id 09N6Oo3q012675 (version=TLSv1.2 cipher=DHE-RSA-AES256-GCM-SHA384 bits=256 verify=NO); Fri, 23 Oct 2020 06:24:50 GMT
Content-Type: text/plain; charset=utf-8
Mime-Version: 1.0 (Mac OS X Mail 13.4 \(3608.120.23.2.4\))
From: Eliot Lear <lear@cisco.com>
In-Reply-To: <CAOgPGoD3MQu=Hv6HTfug0XredaRt_T7oD7z_uwnATmHku9DmLg@mail.gmail.com>
Date: Fri, 23 Oct 2020 08:24:48 +0200
Cc: Hannes Tschofenig <Hannes.Tschofenig@arm.com>, "emu@ietf.org" <emu@ietf.org>
Content-Transfer-Encoding: quoted-printable
Message-Id: <789372DC-6028-4E2B-9F69-A6E90A75352A@cisco.com>
References: <AM0PR08MB371647618F993B8C5BA6EB5FFA1C0@AM0PR08MB3716.eurprd08.prod.outlook.com> <AD94F3FF-31A7-4F44-95F7-6A7E70FA8D27@cisco.com> <CAOgPGoD3MQu=Hv6HTfug0XredaRt_T7oD7z_uwnATmHku9DmLg@mail.gmail.com>
To: Joseph Salowey <joe@salowey.net>
X-Mailer: Apple Mail (2.3608.120.23.2.4)
X-Outbound-SMTP-Client: 10.61.103.21, dhcp-10-61-103-21.cisco.com
X-Outbound-Node: aer-core-2.cisco.com
Archived-At: <https://mailarchive.ietf.org/arch/msg/emu/NMA4P3jzUrdO1qtfwYgLUip5eQA>
Subject: Re: [Emu] draft-ietf-emu-eap-tls13-11: OCSP Stapling
X-BeenThere: emu@ietf.org
X-Mailman-Version: 2.1.29
Precedence: list
List-Id: "EAP Methods Update \(EMU\)" <emu.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/emu>, <mailto:emu-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/emu/>
List-Post: <mailto:emu@ietf.org>
List-Help: <mailto:emu-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/emu>, <mailto:emu-request@ietf.org?subject=subscribe>
X-List-Received-Date: Fri, 23 Oct 2020 06:24:57 -0000

So I=E2=80=99m a client and include a certificate status request.  The =
EAP server isn=E2=80=99t talking to the CA at the moment.  Does a nonce =
have to be used?  If so=E2=80=A6 #fail.  If not, what prevents a replay? =
 And if the answer is nothing, what is the threat model we are =
addressing?=


From nobody Fri Oct 23 00:38:15 2020
Return-Path: <Hannes.Tschofenig@arm.com>
X-Original-To: emu@ietfa.amsl.com
Delivered-To: emu@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 1A6693A09C5 for <emu@ietfa.amsl.com>; Fri, 23 Oct 2020 00:38:13 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.899
X-Spam-Level: 
X-Spam-Status: No, score=-1.899 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, HTML_MESSAGE=0.001, RCVD_IN_MSPIKE_H2=-0.001, SPF_PASS=-0.001, UNPARSEABLE_RELAY=0.001, URIBL_BLOCKED=0.001] autolearn=unavailable autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (1024-bit key) header.d=armh.onmicrosoft.com header.b=XQ74/Dc2; dkim=pass (1024-bit key) header.d=armh.onmicrosoft.com header.b=XQ74/Dc2
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 XiHVsfozB555 for <emu@ietfa.amsl.com>; Fri, 23 Oct 2020 00:38:10 -0700 (PDT)
Received: from EUR02-AM5-obe.outbound.protection.outlook.com (mail-eopbgr00068.outbound.protection.outlook.com [40.107.0.68]) (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 AD76E3A09CF for <emu@ietf.org>; Fri, 23 Oct 2020 00:38:08 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=armh.onmicrosoft.com;  s=selector2-armh-onmicrosoft-com; h=From:Date:Subject:Message-ID:Content-Type:MIME-Version:X-MS-Exchange-SenderADCheck; bh=aG/83t1uwhkU2igiJcsxa5HJGNNJaxpwe92nWAOkPpw=; b=XQ74/Dc2bjLoH/Sv7xmKX3c4ubSKJsJhSI1CvAEefJLcvOuFrGHWAA2JX7WePuw1u/s9TBCyo4K1fMXY5xdUPCiV2V4Aby+Yv0w+TQx0f5HQusTYhXSKpxI3qvdBW9xdJ4zf8fEocB9IaYz+aLC07SWOh7c3+WesYDjc7u+wumE=
Received: from AM5PR0701CA0058.eurprd07.prod.outlook.com (2603:10a6:203:2::20) by PR3PR08MB5721.eurprd08.prod.outlook.com (2603:10a6:102:84::21) with Microsoft SMTP Server (version=TLS1_2, cipher=TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384) id 15.20.3477.20; Fri, 23 Oct 2020 07:38:04 +0000
Received: from VE1EUR03FT007.eop-EUR03.prod.protection.outlook.com (2603:10a6:203:2:cafe::a3) by AM5PR0701CA0058.outlook.office365.com (2603:10a6:203:2::20) with Microsoft SMTP Server (version=TLS1_2, cipher=TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384) id 15.20.3499.6 via Frontend Transport; Fri, 23 Oct 2020 07:38:04 +0000
X-MS-Exchange-Authentication-Results: spf=pass (sender IP is 63.35.35.123) smtp.mailfrom=arm.com; ietf.org; dkim=pass (signature was verified) header.d=armh.onmicrosoft.com;ietf.org; dmarc=pass action=none header.from=arm.com;
Received-SPF: Pass (protection.outlook.com: domain of arm.com designates 63.35.35.123 as permitted sender) receiver=protection.outlook.com; client-ip=63.35.35.123; helo=64aa7808-outbound-1.mta.getcheckrecipient.com;
Received: from 64aa7808-outbound-1.mta.getcheckrecipient.com (63.35.35.123) by VE1EUR03FT007.mail.protection.outlook.com (10.152.18.114) with Microsoft SMTP Server (version=TLS1_2, cipher=TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384) id 15.20.3499.18 via Frontend Transport; Fri, 23 Oct 2020 07:38:03 +0000
Received: ("Tessian outbound c189680f801b:v64"); Fri, 23 Oct 2020 07:38:03 +0000
X-CR-MTA-TID: 64aa7808
Received: from 052bc6c56d93.1 by 64aa7808-outbound-1.mta.getcheckrecipient.com id 99AD46A2-CC8D-4A93-986C-CC8CA729CDF6.1;  Fri, 23 Oct 2020 07:37:58 +0000
Received: from EUR05-AM6-obe.outbound.protection.outlook.com by 64aa7808-outbound-1.mta.getcheckrecipient.com with ESMTPS id 052bc6c56d93.1 (version=TLSv1.2 cipher=ECDHE-RSA-AES256-GCM-SHA384); Fri, 23 Oct 2020 07:37:58 +0000
ARC-Seal: i=1; a=rsa-sha256; s=arcselector9901; d=microsoft.com; cv=none; b=D7+suHKu47VvmJD9PPCFit27YqKEZfTmsH8BX3ae1yEh+LgVi83jnw2yeXy/LmO3D/VB0pmh/WYcdrQhAdzw0rpZ6TuhJKw3oMWpfh+ub5HVOC+kFQ+zedb5/DcaNZrEGafGi87e4Tx1er4/uBLEFWw246YJeFMHwN7xcT3tNi3DjHgmG2RfXjpnj+fNom8ZQTc27KV9BgsCgQ0zPCYQHDmwV4mxvuqtkNrkNTsoRvO7GXi7LBGjxK3mQWRtZusTjtXoDprlY9piiPSTqJ2ek0mJVbbwzLZKajHEufghy8jUVc0ofKicIJYXNcJ7vFV7kkoJSi3ddKKQmffBrhVrfQ==
ARC-Message-Signature: i=1; a=rsa-sha256; c=relaxed/relaxed; d=microsoft.com;  s=arcselector9901; h=From:Date:Subject:Message-ID:Content-Type:MIME-Version:X-MS-Exchange-SenderADCheck; bh=aG/83t1uwhkU2igiJcsxa5HJGNNJaxpwe92nWAOkPpw=; b=IAseEZW1y+pqVbOiJa168HYwTgJwyNQyX1LvMVzR+uXd/6yoFkJbmoEiFyVZy+LklzoLlGVLhiOvPZvWq+18c7KBGV4Gaqu+T4dNXikra/YACljn9UtWS0O4vvO6smk2CQVi7qkIGD7XO5kudZAVxWE+72m5TM1sbp6mEVxXRV+YiH9TeEFFPIV/wNqGHjnLE/BYu2WzLEMhW7YgwoQ1zffMRa2qKtKnhOmyyDshJZKx/HpoI2nAsqYSJz04XJMGrQQSpDnzYYiI/oGdFmlq41iG2Z5oXk3Xv9HvYG0QEm0pzKNDr1Sqf/3hUM3ZZiAqGHrVH4FPrNPyiK2as82G3Q==
ARC-Authentication-Results: i=1; mx.microsoft.com 1; spf=pass smtp.mailfrom=arm.com; dmarc=pass action=none header.from=arm.com; dkim=pass header.d=arm.com; arc=none
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=armh.onmicrosoft.com;  s=selector2-armh-onmicrosoft-com; h=From:Date:Subject:Message-ID:Content-Type:MIME-Version:X-MS-Exchange-SenderADCheck; bh=aG/83t1uwhkU2igiJcsxa5HJGNNJaxpwe92nWAOkPpw=; b=XQ74/Dc2bjLoH/Sv7xmKX3c4ubSKJsJhSI1CvAEefJLcvOuFrGHWAA2JX7WePuw1u/s9TBCyo4K1fMXY5xdUPCiV2V4Aby+Yv0w+TQx0f5HQusTYhXSKpxI3qvdBW9xdJ4zf8fEocB9IaYz+aLC07SWOh7c3+WesYDjc7u+wumE=
Received: from AM0PR08MB3716.eurprd08.prod.outlook.com (2603:10a6:208:106::13) by AM0PR08MB4292.eurprd08.prod.outlook.com (2603:10a6:208:143::17) with Microsoft SMTP Server (version=TLS1_2, cipher=TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384) id 15.20.3499.18; Fri, 23 Oct 2020 07:37:56 +0000
Received: from AM0PR08MB3716.eurprd08.prod.outlook.com ([fe80::900e:c64d:a006:4860]) by AM0PR08MB3716.eurprd08.prod.outlook.com ([fe80::900e:c64d:a006:4860%6]) with mapi id 15.20.3455.037; Fri, 23 Oct 2020 07:37:56 +0000
From: Hannes Tschofenig <Hannes.Tschofenig@arm.com>
To: Joseph Salowey <joe@salowey.net>, Eliot Lear <lear=40cisco.com@dmarc.ietf.org>
CC: "emu@ietf.org" <emu@ietf.org>
Thread-Topic: [Emu] draft-ietf-emu-eap-tls13-11: OCSP Stapling
Thread-Index: AdaniLvyfaHHD0ANRluj1nshuTAidQA/HNCAAAyz4QAAFaqz0A==
Date: Fri, 23 Oct 2020 07:37:56 +0000
Message-ID: <AM0PR08MB371649BBA92B7F624008D0B3FA1A0@AM0PR08MB3716.eurprd08.prod.outlook.com>
References: <AM0PR08MB371647618F993B8C5BA6EB5FFA1C0@AM0PR08MB3716.eurprd08.prod.outlook.com> <AD94F3FF-31A7-4F44-95F7-6A7E70FA8D27@cisco.com> <CAOgPGoD3MQu=Hv6HTfug0XredaRt_T7oD7z_uwnATmHku9DmLg@mail.gmail.com>
In-Reply-To: <CAOgPGoD3MQu=Hv6HTfug0XredaRt_T7oD7z_uwnATmHku9DmLg@mail.gmail.com>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
x-ts-tracking-id: 0DA60C0BE889F44582291E6C998D3C21.0
x-checkrecipientchecked: true
Authentication-Results-Original: salowey.net; dkim=none (message not signed) header.d=none;salowey.net; dmarc=none action=none header.from=arm.com;
x-originating-ip: [80.92.115.241]
x-ms-publictraffictype: Email
X-MS-Office365-Filtering-HT: Tenant
X-MS-Office365-Filtering-Correlation-Id: 5daa1038-bac8-4def-e6c7-08d877269349
x-ms-traffictypediagnostic: AM0PR08MB4292:|PR3PR08MB5721:
X-Microsoft-Antispam-PRVS: <PR3PR08MB5721BD37CB295646A19E87B8FA1A0@PR3PR08MB5721.eurprd08.prod.outlook.com>
x-checkrecipientrouted: true
nodisclaimer: true
x-ms-oob-tlc-oobclassifiers: OLM:9508;OLM:9508;
X-MS-Exchange-SenderADCheck: 1
X-Microsoft-Antispam-Untrusted: BCL:0;
X-Microsoft-Antispam-Message-Info-Original: S3yOn0Sx1RU6FJss2lQE7UwKRNtppPY//D0WeRIV+My8H9Fh8U0IJ3RDr/SgqR/cCx7u71nIPfpacwO0sp2M98jb3aYCgFVHdl8hOOEY7pUmcjM/vvPvHzcwMWUNnxJqHPrt7DvM2hlxZQD23M+D/Up1siEz2CAcqVjgML6/kjyBJapSNeRrxIGe+uApl/m08hQgWJryJzrJvmlroER94KfvqJFvxJ4kz+Qh5STs5IKZsP8+BQDrjvNqhAk45PZDDQpEjdECz+hLs+KWN76OZU1UdfXZvF97IWVkDONgsOC95uOqtX9bD9VkSX7ucZ2w1Cc6u86SLSJ455jOQgmoY1sx2LbffRq2GSrfZ4hFI4kZWT5usBkuoFLs7ul5thLooRlx4vYOYWo8IMtlXFTHqA==
X-Forefront-Antispam-Report-Untrusted: CIP:255.255.255.255; CTRY:; LANG:en; SCL:1; SRV:; IPV:NLI; SFV:NSPM; H:AM0PR08MB3716.eurprd08.prod.outlook.com; PTR:; CAT:NONE; SFS:(4636009)(136003)(376002)(396003)(346002)(39860400002)(366004)(478600001)(966005)(71200400001)(52536014)(5660300002)(110136005)(316002)(55016002)(76116006)(64756008)(66556008)(66476007)(66946007)(166002)(8676002)(83380400001)(26005)(186003)(8936002)(4326008)(9326002)(7696005)(9686003)(86362001)(66446008)(33656002)(2906002)(53546011)(6506007); DIR:OUT; SFP:1101; 
x-ms-exchange-antispam-messagedata: wTm7ftXfjaQpTDqf3g0rM8rbZDlZhBAJEs4Wi9fkV7RlNN+uhr3h1DgcY5/jo4A9ND4g4Yo4+Cq4JmUj/S5L+wONGgWXUC714VVAcNLb3MNt38/pTbfNHrjAVfIzcffIRsKTRBVurtcW+ZSylA2Ze8gVS5M4830BT3qrVrt2g7CdtsFC4Z9taVIqm4Rkmw0v82p2QEBZ6Rcdk5yq0k88w/njH4S2lF1TdNx6AXL6edUqoHI8+HQr+D+gFkkBm9Tksc3DbWz5KRaxC5Z/Y1CNUIab8c/7cSNkI7lqmCx6JRHPJ2bDPn4RGlpnbynMho7Ig0/Hn+Rg3HwhgPyeERVWj/5s2k1ym2HiZ8mNrG9GcdNm2PizpnLZyfA2m2sKCH+e0r1yyC30F6YDrfmM/TsWZBAWD5rBkA9LFzY7qp0G8qdKFFc8t68oaem5ebNGb4Gm/T8m+mjNdElkbaL0hfpX6s36cQMFLvs6m+dTgsrq2B1P5to+TJASvBmoGeB74+uE1p5xG9zYxDOd+Cr6L77CTCEk0G5VcTPt6nkGaTeganvs5q0037JmZ5UZwt8XL05B3i8SfOXNxcX3n08mvDlrNVNHGXxgtx65m447AUR0aSSXRePV57eGjPI9P7+jzDOuc1vcskNG8alNATQj6Ndz9g==
x-ms-exchange-transport-forked: True
Content-Type: multipart/alternative; boundary="_000_AM0PR08MB371649BBA92B7F624008D0B3FA1A0AM0PR08MB3716eurp_"
MIME-Version: 1.0
X-MS-Exchange-Transport-CrossTenantHeadersStamped: AM0PR08MB4292
Original-Authentication-Results: salowey.net; dkim=none (message not signed) header.d=none;salowey.net; dmarc=none action=none header.from=arm.com;
X-EOPAttributedMessage: 0
X-MS-Exchange-Transport-CrossTenantHeadersStripped: VE1EUR03FT007.eop-EUR03.prod.protection.outlook.com
X-MS-Office365-Filtering-Correlation-Id-Prvs: 439a1ebb-6318-4f60-c92e-08d877268f0d
X-Microsoft-Antispam: BCL:0;
X-Microsoft-Antispam-Message-Info: 39sxH2n3cj41b7zYrYDtR3KkhN84YQ2HVmtzu/3UWdNBXqXBrpragdi0eCdTbdDAs+jTZm69Aey7rRG7scaGq01/jOm1s6sI/j6lf68+GGuSZJaxIG+Y43zfIrGVTrhGEPQxD/mDrFOZOhExkP50zFn4CQ9twPurTj2Srxsv7s7sCJkDOHcFuwDR33pMBOboxUgH1jkOF33fFS+tNfYX5WLL+HrsMHQXm6z6ZfKdS3jXrACMffEXRbyTvRCBFKZjJaOX9qoRuj0qGlhRqmiV2nQHprGaR/EUN47ZHQKcFSq7Ogl533GvGyTr/YAUOt4tUbuOojuYMlTqA5j07G+6epzLBE4Glmy41RkAIYQTn5tar/0YnwwlLsHDd9/1iAzZlTAwEVONeZqNN9SJUj9lkRoIqyLUgzkfpMKzlZJjWMdaVrSqOFvcPRMfhfWqapqHUFGK+Sz/bReC1Ili3/qJ8bYvEB1/ScrO2XFypKG1zUw=
X-Forefront-Antispam-Report: CIP:63.35.35.123; CTRY:IE; LANG:en; SCL:1; SRV:;  IPV:CAL; SFV:NSPM; H:64aa7808-outbound-1.mta.getcheckrecipient.com;  PTR:ec2-63-35-35-123.eu-west-1.compute.amazonaws.com; CAT:NONE; SFS:(4636009)(396003)(39860400002)(376002)(136003)(346002)(46966005)(55016002)(83380400001)(9326002)(81166007)(47076004)(82310400003)(356005)(82740400003)(8936002)(4326008)(86362001)(5660300002)(36906005)(26005)(336012)(166002)(8676002)(186003)(110136005)(70586007)(478600001)(70206006)(7696005)(33964004)(53546011)(316002)(33656002)(52536014)(2906002)(966005)(6506007)(9686003); DIR:OUT; SFP:1101; 
X-OriginatorOrg: arm.com
X-MS-Exchange-CrossTenant-OriginalArrivalTime: 23 Oct 2020 07:38:03.5362 (UTC)
X-MS-Exchange-CrossTenant-Network-Message-Id: 5daa1038-bac8-4def-e6c7-08d877269349
X-MS-Exchange-CrossTenant-Id: f34e5979-57d9-4aaa-ad4d-b122a662184d
X-MS-Exchange-CrossTenant-OriginalAttributedTenantConnectingIp: TenantId=f34e5979-57d9-4aaa-ad4d-b122a662184d; Ip=[63.35.35.123];  Helo=[64aa7808-outbound-1.mta.getcheckrecipient.com]
X-MS-Exchange-CrossTenant-AuthSource: VE1EUR03FT007.eop-EUR03.prod.protection.outlook.com
X-MS-Exchange-CrossTenant-AuthAs: Anonymous
X-MS-Exchange-CrossTenant-FromEntityHeader: HybridOnPrem
X-MS-Exchange-Transport-CrossTenantHeadersStamped: PR3PR08MB5721
Archived-At: <https://mailarchive.ietf.org/arch/msg/emu/z6H_1iZrd3Lz-LrfEWw_iYhD_7o>
Subject: Re: [Emu] draft-ietf-emu-eap-tls13-11: OCSP Stapling
X-BeenThere: emu@ietf.org
X-Mailman-Version: 2.1.29
Precedence: list
List-Id: "EAP Methods Update \(EMU\)" <emu.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/emu>, <mailto:emu-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/emu/>
List-Post: <mailto:emu@ietf.org>
List-Help: <mailto:emu-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/emu>, <mailto:emu-request@ietf.org?subject=subscribe>
X-List-Received-Date: Fri, 23 Oct 2020 07:38:13 -0000

--_000_AM0PR08MB371649BBA92B7F624008D0B3FA1A0AM0PR08MB3716eurp_
Content-Type: text/plain; charset="utf-8"
Content-Transfer-Encoding: base64

SGkgSm9lLA0KDQpJIGRvIG5vdCB1bmRlcnN0YW5kIGNlcnRpZmljYXRlIHJldm9jYXRpb24gY2hl
Y2tpbmcgaXMgYSB0b3BpYyBzcGVjaWZpYyB0byB0aGUgdXNlIG9mIFRMUyAxLjMgaW4gRUFQLVRM
Uy4NCg0KSWYgdGhpcyB0b3BpYyBpcyBpbXBvcnRhbnQgdG8gdGhlIGdyb3VwIHRoZW4gd2h5IGlz
buKAmXQgdGhpcyBhIGdlbmVyaWMgcmVjb21tZW5kYXRpb25zIGZvciBhbGwgRUFQIG1ldGhvZHMg
dGhhdCB1c2UgcHVibGljIGtleSBiYXNlZCBhdXRoZW50aWNhdGlvbj8NCg0KV291bGRu4oCZdCB0
aGlzIGJlIGEgdG9waWMgdG8gYWRkcmVzcyBpbiA8ZHJhZnQtaWV0Zi1lbXUtZWFwdGxzY2VydD4/
IElNSE8gdGhpcyB3b3VsZCBtYWtlIG1vcmUgc2Vuc2UgZ2l2ZW4gdGhhdCA8ZHJhZnQtaWV0Zi1l
bXUtZWFwdGxzY2VydD4gdGFsa3MgYWJvdXQgbGFyZ2UgY2VydGlmaWNhdGVzIGFuZCBsb25nIGNl
cnRpZmljYXRlIGNoYWlucyBhbmQgYW55IHByb3Bvc2FsIHRvIG1ha2UgdGhvc2UgZXZlbiBsYXJn
ZXIgc2hvdWxkIGJlIGV2YWx1YXRlZCBpbiB0aGlzIGNvbnRleHQuDQoNCkNpYW8NCkhhbm5lcw0K
DQpGcm9tOiBKb3NlcGggU2Fsb3dleSA8am9lQHNhbG93ZXkubmV0Pg0KU2VudDogVGh1cnNkYXks
IE9jdG9iZXIgMjIsIDIwMjAgMTE6MTIgUE0NClRvOiBFbGlvdCBMZWFyIDxsZWFyPTQwY2lzY28u
Y29tQGRtYXJjLmlldGYub3JnPg0KQ2M6IEhhbm5lcyBUc2Nob2ZlbmlnIDxIYW5uZXMuVHNjaG9m
ZW5pZ0Bhcm0uY29tPjsgZW11QGlldGYub3JnDQpTdWJqZWN0OiBSZTogW0VtdV0gZHJhZnQtaWV0
Zi1lbXUtZWFwLXRsczEzLTExOiBPQ1NQIFN0YXBsaW5nDQoNCg0KDQpPbiBUaHUsIE9jdCAyMiwg
MjAyMCBhdCA4OjA4IEFNIEVsaW90IExlYXIgPGxlYXI9NDBjaXNjby5jb21AZG1hcmMuaWV0Zi5v
cmc8bWFpbHRvOjQwY2lzY28uY29tQGRtYXJjLmlldGYub3JnPj4gd3JvdGU6DQorMS4gIEhvdyBk
b2VzIGFueW9uZSBldmVuIGRvIE9DU1Agd2l0aG91dCBoYXZpbmcgZmlyc3QgZ290dGVuIG9udG8g
dGhlIG5ldHdvcms/DQoNCg0KW0pvZV0gVEhhdCBpcyB3aGF0IE9DU1Agc3RhcGxpbmcgaXMgc3Vw
cG9zZWQgdG8gc29sdmUgc2luY2UgdGhlIE9DU1AgbWVzc2FnZXMgYXJlIHNlbnQgaW4gdGhlIFRM
UyBoYW5kc2hha2UuICAgSSBiZWxpZXZlIHRoZXJlIGFyZSBzb21lIEVBUC1UTFMgaW1wbGVtZW50
YXRpb25zIHRoYXQgc3VwcG9ydCBPQ1NQLCBidXQgSSBhbSBub3Qgc3VyZSBpZiBpdCBpcyBhY3R1
YWxseSBkZXBsb3llZC4NCg0KRWxpb3QNCg0KT24gMjEgT2N0IDIwMjAsIGF0IDExOjAyLCBIYW5u
ZXMgVHNjaG9mZW5pZyA8SGFubmVzLlRzY2hvZmVuaWdAYXJtLmNvbTxtYWlsdG86SGFubmVzLlRz
Y2hvZmVuaWdAYXJtLmNvbT4+IHdyb3RlOg0KDQpIaSBhbGwsDQoNCnRoaXMgZHJhZnQgbWFuZGF0
ZXMgT0NTQ1Agc3RhcGxpbmcgKGZvciB1c2Ugd2l0aCBUTFMgMS4zIGluIEVBUC1UTFMpIGFuZCBJ
IGJlbGlldmUgdGhpcyBpcyBhIHByb2JsZW0gZm9yIGltcGxlbWVudGF0aW9ucy4gVGhpcyBleHRy
YSBidXJkZW4gaXMgSU1ITyB1bmp1c3RpZmllZC4gRm9yIHRoZSB0eXBlIG9mIGRlcGxveW1lbnRz
IHdoZXJlIEVBUCBpcyB1c2VkIHRoZXJlIGlzIG5vIG5lZWQgZm9yIGEgbWFuZGF0b3J5IGNlcnRp
ZmljYXRlIHJldm9jYXRpb24gY2hlY2tpbmcgd2l0aCBPQ1NQLg0KDQpIYXZpbmcgaXQgb3B0aW9u
YWwsIGxpa2UgdGhlIHVzZSBvZiBtYW55IG90aGVyIFRMUyBleHRlbnNpb25zLCBpcyBmaW5lIGZv
ciBtZS4gRldJVyBldmVuIFRMUyAxLjMsIHdoaWNoIGlzIHVzZWQgaW4gYSBtb3JlIGdlbmVyaWMg
ZW52aXJvbm1lbnQsIGRvZXMgbm90IG1hbmRhdGUgdGhlIHVzZSBvZiBPQ1NQIHN0YXBsaW5nLg0K
DQpUaGlzIHJlcXVpcmVtZW50IHdpbGwgbWFrZSB0aGUgcHJvYmxlbSBkZXNjcmliZWQgaW4gZHJh
ZnQtaWV0Zi1lbXUtZWFwdGxzY2VydCB3b3JzZS4gSSBhbSBzdXJlIHRoZSBhdXRob3JzIGFyZSBh
d2FyZSBvZiB0aGlzIGZhY3Qgc2luY2UgdGhleSBhcmUgYWxzbyBjby1hdXRob3JzIG9mIGRyYWZ0
LWlldGYtZW11LWVhcHRsc2NlcnQuDQoNCkNpYW8NCkhhbm5lcw0KSU1QT1JUQU5UIE5PVElDRTog
VGhlIGNvbnRlbnRzIG9mIHRoaXMgZW1haWwgYW5kIGFueSBhdHRhY2htZW50cyBhcmUgY29uZmlk
ZW50aWFsIGFuZCBtYXkgYWxzbyBiZSBwcml2aWxlZ2VkLiBJZiB5b3UgYXJlIG5vdCB0aGUgaW50
ZW5kZWQgcmVjaXBpZW50LCBwbGVhc2Ugbm90aWZ5IHRoZSBzZW5kZXIgaW1tZWRpYXRlbHkgYW5k
IGRvIG5vdCBkaXNjbG9zZSB0aGUgY29udGVudHMgdG8gYW55IG90aGVyIHBlcnNvbiwgdXNlIGl0
IGZvciBhbnkgcHVycG9zZSwgb3Igc3RvcmUgb3IgY29weSB0aGUgaW5mb3JtYXRpb24gaW4gYW55
IG1lZGl1bS4gVGhhbmsgeW91LiBfX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19f
X19fX19fX19fXw0KRW11IG1haWxpbmcgbGlzdA0KRW11QGlldGYub3JnPG1haWx0bzpFbXVAaWV0
Zi5vcmc+DQpodHRwczovL3d3dy5pZXRmLm9yZy9tYWlsbWFuL2xpc3RpbmZvL2VtdQ0KDQpfX19f
X19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fXw0KRW11IG1haWxpbmcg
bGlzdA0KRW11QGlldGYub3JnPG1haWx0bzpFbXVAaWV0Zi5vcmc+DQpodHRwczovL3d3dy5pZXRm
Lm9yZy9tYWlsbWFuL2xpc3RpbmZvL2VtdQ0KSU1QT1JUQU5UIE5PVElDRTogVGhlIGNvbnRlbnRz
IG9mIHRoaXMgZW1haWwgYW5kIGFueSBhdHRhY2htZW50cyBhcmUgY29uZmlkZW50aWFsIGFuZCBt
YXkgYWxzbyBiZSBwcml2aWxlZ2VkLiBJZiB5b3UgYXJlIG5vdCB0aGUgaW50ZW5kZWQgcmVjaXBp
ZW50LCBwbGVhc2Ugbm90aWZ5IHRoZSBzZW5kZXIgaW1tZWRpYXRlbHkgYW5kIGRvIG5vdCBkaXNj
bG9zZSB0aGUgY29udGVudHMgdG8gYW55IG90aGVyIHBlcnNvbiwgdXNlIGl0IGZvciBhbnkgcHVy
cG9zZSwgb3Igc3RvcmUgb3IgY29weSB0aGUgaW5mb3JtYXRpb24gaW4gYW55IG1lZGl1bS4gVGhh
bmsgeW91Lg0K

--_000_AM0PR08MB371649BBA92B7F624008D0B3FA1A0AM0PR08MB3716eurp_
Content-Type: text/html; charset="utf-8"
Content-Transfer-Encoding: base64

PGh0bWwgeG1sbnM6dj0idXJuOnNjaGVtYXMtbWljcm9zb2Z0LWNvbTp2bWwiIHhtbG5zOm89InVy
bjpzY2hlbWFzLW1pY3Jvc29mdC1jb206b2ZmaWNlOm9mZmljZSIgeG1sbnM6dz0idXJuOnNjaGVt
YXMtbWljcm9zb2Z0LWNvbTpvZmZpY2U6d29yZCIgeG1sbnM6bT0iaHR0cDovL3NjaGVtYXMubWlj
cm9zb2Z0LmNvbS9vZmZpY2UvMjAwNC8xMi9vbW1sIiB4bWxucz0iaHR0cDovL3d3dy53My5vcmcv
VFIvUkVDLWh0bWw0MCI+DQo8aGVhZD4NCjxtZXRhIGh0dHAtZXF1aXY9IkNvbnRlbnQtVHlwZSIg
Y29udGVudD0idGV4dC9odG1sOyBjaGFyc2V0PXV0Zi04Ij4NCjxtZXRhIG5hbWU9IkdlbmVyYXRv
ciIgY29udGVudD0iTWljcm9zb2Z0IFdvcmQgMTUgKGZpbHRlcmVkIG1lZGl1bSkiPg0KPHN0eWxl
PjwhLS0NCi8qIEZvbnQgRGVmaW5pdGlvbnMgKi8NCkBmb250LWZhY2UNCgl7Zm9udC1mYW1pbHk6
SGVsdmV0aWNhOw0KCXBhbm9zZS0xOjIgMTEgNiA0IDIgMiAyIDIgMiA0O30NCkBmb250LWZhY2UN
Cgl7Zm9udC1mYW1pbHk6IkNhbWJyaWEgTWF0aCI7DQoJcGFub3NlLTE6MiA0IDUgMyA1IDQgNiAz
IDIgNDt9DQpAZm9udC1mYWNlDQoJe2ZvbnQtZmFtaWx5OkRlbmdYaWFuOw0KCXBhbm9zZS0xOjIg
MSA2IDAgMyAxIDEgMSAxIDE7fQ0KQGZvbnQtZmFjZQ0KCXtmb250LWZhbWlseTpDYWxpYnJpOw0K
CXBhbm9zZS0xOjIgMTUgNSAyIDIgMiA0IDMgMiA0O30NCkBmb250LWZhY2UNCgl7Zm9udC1mYW1p
bHk6IlxARGVuZ1hpYW4iOw0KCXBhbm9zZS0xOjIgMSA2IDAgMyAxIDEgMSAxIDE7fQ0KLyogU3R5
bGUgRGVmaW5pdGlvbnMgKi8NCnAuTXNvTm9ybWFsLCBsaS5Nc29Ob3JtYWwsIGRpdi5Nc29Ob3Jt
YWwNCgl7bWFyZ2luOjBpbjsNCglmb250LXNpemU6MTEuMHB0Ow0KCWZvbnQtZmFtaWx5OiJDYWxp
YnJpIixzYW5zLXNlcmlmO30NCmE6bGluaywgc3Bhbi5Nc29IeXBlcmxpbmsNCgl7bXNvLXN0eWxl
LXByaW9yaXR5Ojk5Ow0KCWNvbG9yOmJsdWU7DQoJdGV4dC1kZWNvcmF0aW9uOnVuZGVybGluZTt9
DQpzcGFuLkVtYWlsU3R5bGUxOA0KCXttc28tc3R5bGUtdHlwZTpwZXJzb25hbC1yZXBseTsNCglm
b250LWZhbWlseToiQ2FsaWJyaSIsc2Fucy1zZXJpZjsNCgljb2xvcjp3aW5kb3d0ZXh0O30NCi5N
c29DaHBEZWZhdWx0DQoJe21zby1zdHlsZS10eXBlOmV4cG9ydC1vbmx5Ow0KCWZvbnQtZmFtaWx5
OiJDYWxpYnJpIixzYW5zLXNlcmlmO30NCkBwYWdlIFdvcmRTZWN0aW9uMQ0KCXtzaXplOjguNWlu
IDExLjBpbjsNCgltYXJnaW46MS4waW4gMS4waW4gMS4waW4gMS4waW47fQ0KZGl2LldvcmRTZWN0
aW9uMQ0KCXtwYWdlOldvcmRTZWN0aW9uMTt9DQotLT48L3N0eWxlPjwhLS1baWYgZ3RlIG1zbyA5
XT48eG1sPg0KPG86c2hhcGVkZWZhdWx0cyB2OmV4dD0iZWRpdCIgc3BpZG1heD0iMTAyNiIgLz4N
CjwveG1sPjwhW2VuZGlmXS0tPjwhLS1baWYgZ3RlIG1zbyA5XT48eG1sPg0KPG86c2hhcGVsYXlv
dXQgdjpleHQ9ImVkaXQiPg0KPG86aWRtYXAgdjpleHQ9ImVkaXQiIGRhdGE9IjEiIC8+DQo8L286
c2hhcGVsYXlvdXQ+PC94bWw+PCFbZW5kaWZdLS0+DQo8L2hlYWQ+DQo8Ym9keSBsYW5nPSJFTi1V
UyIgbGluaz0iYmx1ZSIgdmxpbms9InB1cnBsZSI+DQo8ZGl2IGNsYXNzPSJXb3JkU2VjdGlvbjEi
Pg0KPHAgY2xhc3M9Ik1zb05vcm1hbCI+SGkgSm9lLCA8bzpwPjwvbzpwPjwvcD4NCjxwIGNsYXNz
PSJNc29Ob3JtYWwiPjxvOnA+Jm5ic3A7PC9vOnA+PC9wPg0KPHAgY2xhc3M9Ik1zb05vcm1hbCI+
SSBkbyBub3QgdW5kZXJzdGFuZCBjZXJ0aWZpY2F0ZSByZXZvY2F0aW9uIGNoZWNraW5nIGlzIGEg
dG9waWMgc3BlY2lmaWMgdG8gdGhlIHVzZSBvZiBUTFMgMS4zIGluIEVBUC1UTFMuDQo8bzpwPjwv
bzpwPjwvcD4NCjxwIGNsYXNzPSJNc29Ob3JtYWwiPjxvOnA+Jm5ic3A7PC9vOnA+PC9wPg0KPHAg
Y2xhc3M9Ik1zb05vcm1hbCI+SWYgdGhpcyB0b3BpYyBpcyBpbXBvcnRhbnQgdG8gdGhlIGdyb3Vw
IHRoZW4gd2h5IGlzbuKAmXQgdGhpcyBhIGdlbmVyaWMgcmVjb21tZW5kYXRpb25zIGZvciBhbGwg
RUFQIG1ldGhvZHMgdGhhdCB1c2UgcHVibGljIGtleSBiYXNlZCBhdXRoZW50aWNhdGlvbj8NCjxv
OnA+PC9vOnA+PC9wPg0KPHAgY2xhc3M9Ik1zb05vcm1hbCI+PG86cD4mbmJzcDs8L286cD48L3A+
DQo8cCBjbGFzcz0iTXNvTm9ybWFsIj5Xb3VsZG7igJl0IHRoaXMgYmUgYSB0b3BpYyB0byBhZGRy
ZXNzIGluICZsdDtkcmFmdC1pZXRmLWVtdS1lYXB0bHNjZXJ0Jmd0Oz8gSU1ITyB0aGlzIHdvdWxk
IG1ha2UgbW9yZSBzZW5zZSBnaXZlbiB0aGF0ICZsdDtkcmFmdC1pZXRmLWVtdS1lYXB0bHNjZXJ0
Jmd0OyB0YWxrcyBhYm91dCBsYXJnZSBjZXJ0aWZpY2F0ZXMgYW5kIGxvbmcgY2VydGlmaWNhdGUg
Y2hhaW5zIGFuZCBhbnkgcHJvcG9zYWwgdG8gbWFrZSB0aG9zZSBldmVuIGxhcmdlcg0KIHNob3Vs
ZCBiZSBldmFsdWF0ZWQgaW4gdGhpcyBjb250ZXh0LiA8bzpwPjwvbzpwPjwvcD4NCjxwIGNsYXNz
PSJNc29Ob3JtYWwiPjxvOnA+Jm5ic3A7PC9vOnA+PC9wPg0KPHAgY2xhc3M9Ik1zb05vcm1hbCI+
Q2lhbzxvOnA+PC9vOnA+PC9wPg0KPHAgY2xhc3M9Ik1zb05vcm1hbCI+SGFubmVzPG86cD48L286
cD48L3A+DQo8cCBjbGFzcz0iTXNvTm9ybWFsIj48bzpwPiZuYnNwOzwvbzpwPjwvcD4NCjxkaXYg
c3R5bGU9ImJvcmRlcjpub25lO2JvcmRlci10b3A6c29saWQgI0UxRTFFMSAxLjBwdDtwYWRkaW5n
OjMuMHB0IDBpbiAwaW4gMGluIj4NCjxwIGNsYXNzPSJNc29Ob3JtYWwiPjxiPkZyb206PC9iPiBK
b3NlcGggU2Fsb3dleSAmbHQ7am9lQHNhbG93ZXkubmV0Jmd0OyA8YnI+DQo8Yj5TZW50OjwvYj4g
VGh1cnNkYXksIE9jdG9iZXIgMjIsIDIwMjAgMTE6MTIgUE08YnI+DQo8Yj5Ubzo8L2I+IEVsaW90
IExlYXIgJmx0O2xlYXI9NDBjaXNjby5jb21AZG1hcmMuaWV0Zi5vcmcmZ3Q7PGJyPg0KPGI+Q2M6
PC9iPiBIYW5uZXMgVHNjaG9mZW5pZyAmbHQ7SGFubmVzLlRzY2hvZmVuaWdAYXJtLmNvbSZndDs7
IGVtdUBpZXRmLm9yZzxicj4NCjxiPlN1YmplY3Q6PC9iPiBSZTogW0VtdV0gZHJhZnQtaWV0Zi1l
bXUtZWFwLXRsczEzLTExOiBPQ1NQIFN0YXBsaW5nPG86cD48L286cD48L3A+DQo8L2Rpdj4NCjxw
IGNsYXNzPSJNc29Ob3JtYWwiPjxvOnA+Jm5ic3A7PC9vOnA+PC9wPg0KPGRpdj4NCjxkaXY+DQo8
cCBjbGFzcz0iTXNvTm9ybWFsIj48bzpwPiZuYnNwOzwvbzpwPjwvcD4NCjwvZGl2Pg0KPHAgY2xh
c3M9Ik1zb05vcm1hbCI+PG86cD4mbmJzcDs8L286cD48L3A+DQo8ZGl2Pg0KPGRpdj4NCjxwIGNs
YXNzPSJNc29Ob3JtYWwiPk9uIFRodSwgT2N0IDIyLCAyMDIwIGF0IDg6MDggQU0gRWxpb3QgTGVh
ciAmbHQ7bGVhcj08YSBocmVmPSJtYWlsdG86NDBjaXNjby5jb21AZG1hcmMuaWV0Zi5vcmciPjQw
Y2lzY28uY29tQGRtYXJjLmlldGYub3JnPC9hPiZndDsgd3JvdGU6PG86cD48L286cD48L3A+DQo8
L2Rpdj4NCjxibG9ja3F1b3RlIHN0eWxlPSJib3JkZXI6bm9uZTtib3JkZXItbGVmdDpzb2xpZCAj
Q0NDQ0NDIDEuMHB0O3BhZGRpbmc6MGluIDBpbiAwaW4gNi4wcHQ7bWFyZ2luLWxlZnQ6NC44cHQ7
bWFyZ2luLXJpZ2h0OjBpbiI+DQo8ZGl2Pg0KPHAgY2xhc3M9Ik1zb05vcm1hbCI+KzEuJm5ic3A7
IEhvdyBkb2VzIGFueW9uZSBldmVuIGRvIE9DU1Agd2l0aG91dCBoYXZpbmcgZmlyc3QgZ290dGVu
IG9udG8gdGhlIG5ldHdvcms/PG86cD48L286cD48L3A+DQo8ZGl2Pg0KPHAgY2xhc3M9Ik1zb05v
cm1hbCI+PG86cD4mbmJzcDs8L286cD48L3A+DQo8L2Rpdj4NCjwvZGl2Pg0KPC9ibG9ja3F1b3Rl
Pg0KPGRpdj4NCjxwIGNsYXNzPSJNc29Ob3JtYWwiPjxvOnA+Jm5ic3A7PC9vOnA+PC9wPg0KPC9k
aXY+DQo8ZGl2Pg0KPHAgY2xhc3M9Ik1zb05vcm1hbCI+W0pvZV0gVEhhdCBpcyB3aGF0IE9DU1Ag
c3RhcGxpbmcgaXMgc3VwcG9zZWQgdG8gc29sdmUgc2luY2UgdGhlIE9DU1AgbWVzc2FnZXMgYXJl
IHNlbnQgaW4gdGhlIFRMUyBoYW5kc2hha2UuJm5ic3A7ICZuYnNwO0kgYmVsaWV2ZSB0aGVyZSBh
cmUgc29tZSBFQVAtVExTIGltcGxlbWVudGF0aW9ucyB0aGF0IHN1cHBvcnQgT0NTUCwgYnV0IEkg
YW0gbm90IHN1cmUgaWYgaXQgaXMgYWN0dWFsbHkgZGVwbG95ZWQuJm5ic3A7Jm5ic3A7PG86cD48
L286cD48L3A+DQo8L2Rpdj4NCjxkaXY+DQo8cCBjbGFzcz0iTXNvTm9ybWFsIj4mbmJzcDs8bzpw
PjwvbzpwPjwvcD4NCjwvZGl2Pg0KPGJsb2NrcXVvdGUgc3R5bGU9ImJvcmRlcjpub25lO2JvcmRl
ci1sZWZ0OnNvbGlkICNDQ0NDQ0MgMS4wcHQ7cGFkZGluZzowaW4gMGluIDBpbiA2LjBwdDttYXJn
aW4tbGVmdDo0LjhwdDttYXJnaW4tcmlnaHQ6MGluIj4NCjxkaXY+DQo8ZGl2Pg0KPHAgY2xhc3M9
Ik1zb05vcm1hbCI+RWxpb3Q8bzpwPjwvbzpwPjwvcD4NCjwvZGl2Pg0KPGRpdj4NCjxwIGNsYXNz
PSJNc29Ob3JtYWwiPjxvOnA+Jm5ic3A7PC9vOnA+PC9wPg0KPGRpdj4NCjxibG9ja3F1b3RlIHN0
eWxlPSJtYXJnaW4tdG9wOjUuMHB0O21hcmdpbi1ib3R0b206NS4wcHQiPg0KPGRpdj4NCjxwIGNs
YXNzPSJNc29Ob3JtYWwiPk9uIDIxIE9jdCAyMDIwLCBhdCAxMTowMiwgSGFubmVzIFRzY2hvZmVu
aWcgJmx0OzxhIGhyZWY9Im1haWx0bzpIYW5uZXMuVHNjaG9mZW5pZ0Bhcm0uY29tIiB0YXJnZXQ9
Il9ibGFuayI+SGFubmVzLlRzY2hvZmVuaWdAYXJtLmNvbTwvYT4mZ3Q7IHdyb3RlOjxvOnA+PC9v
OnA+PC9wPg0KPC9kaXY+DQo8cCBjbGFzcz0iTXNvTm9ybWFsIj48bzpwPiZuYnNwOzwvbzpwPjwv
cD4NCjxkaXY+DQo8ZGl2Pg0KPGRpdj4NCjxwIGNsYXNzPSJNc29Ob3JtYWwiPkhpIGFsbCwmbmJz
cDs8bzpwPjwvbzpwPjwvcD4NCjwvZGl2Pg0KPGRpdj4NCjxwIGNsYXNzPSJNc29Ob3JtYWwiPiZu
YnNwOzxvOnA+PC9vOnA+PC9wPg0KPC9kaXY+DQo8ZGl2Pg0KPHAgY2xhc3M9Ik1zb05vcm1hbCI+
dGhpcyBkcmFmdCBtYW5kYXRlcyBPQ1NDUCBzdGFwbGluZyAoZm9yIHVzZSB3aXRoIFRMUyAxLjMg
aW4gRUFQLVRMUykgYW5kIEkgYmVsaWV2ZSB0aGlzIGlzIGEgcHJvYmxlbSBmb3IgaW1wbGVtZW50
YXRpb25zLiBUaGlzIGV4dHJhIGJ1cmRlbiBpcyBJTUhPIHVuanVzdGlmaWVkLiBGb3IgdGhlIHR5
cGUgb2YgZGVwbG95bWVudHMgd2hlcmUgRUFQIGlzIHVzZWQgdGhlcmUgaXMgbm8gbmVlZCBmb3Ig
YSBtYW5kYXRvcnkNCiBjZXJ0aWZpY2F0ZSByZXZvY2F0aW9uIGNoZWNraW5nIHdpdGggT0NTUC48
bzpwPjwvbzpwPjwvcD4NCjwvZGl2Pg0KPGRpdj4NCjxwIGNsYXNzPSJNc29Ob3JtYWwiPiZuYnNw
OzxvOnA+PC9vOnA+PC9wPg0KPC9kaXY+DQo8ZGl2Pg0KPHAgY2xhc3M9Ik1zb05vcm1hbCI+SGF2
aW5nIGl0IG9wdGlvbmFsLCBsaWtlIHRoZSB1c2Ugb2YgbWFueSBvdGhlciBUTFMgZXh0ZW5zaW9u
cywgaXMgZmluZSBmb3IgbWUuIEZXSVcgZXZlbiBUTFMgMS4zLCB3aGljaCBpcyB1c2VkIGluIGEg
bW9yZSBnZW5lcmljIGVudmlyb25tZW50LCBkb2VzIG5vdCBtYW5kYXRlIHRoZSB1c2Ugb2YgT0NT
UCBzdGFwbGluZy48bzpwPjwvbzpwPjwvcD4NCjwvZGl2Pg0KPGRpdj4NCjxwIGNsYXNzPSJNc29O
b3JtYWwiPiZuYnNwOzxvOnA+PC9vOnA+PC9wPg0KPC9kaXY+DQo8ZGl2Pg0KPHAgY2xhc3M9Ik1z
b05vcm1hbCI+VGhpcyByZXF1aXJlbWVudCB3aWxsIG1ha2UgdGhlIHByb2JsZW0gZGVzY3JpYmVk
IGluIGRyYWZ0LWlldGYtZW11LWVhcHRsc2NlcnQgd29yc2UuIEkgYW0gc3VyZSB0aGUgYXV0aG9y
cyBhcmUgYXdhcmUgb2YgdGhpcyBmYWN0IHNpbmNlIHRoZXkgYXJlIGFsc28gY28tYXV0aG9ycyBv
ZiBkcmFmdC1pZXRmLWVtdS1lYXB0bHNjZXJ0LjxvOnA+PC9vOnA+PC9wPg0KPC9kaXY+DQo8ZGl2
Pg0KPHAgY2xhc3M9Ik1zb05vcm1hbCI+Jm5ic3A7PG86cD48L286cD48L3A+DQo8L2Rpdj4NCjxk
aXY+DQo8cCBjbGFzcz0iTXNvTm9ybWFsIj5DaWFvPG86cD48L286cD48L3A+DQo8L2Rpdj4NCjxk
aXY+DQo8cCBjbGFzcz0iTXNvTm9ybWFsIj5IYW5uZXM8bzpwPjwvbzpwPjwvcD4NCjwvZGl2Pg0K
PC9kaXY+DQo8cCBjbGFzcz0iTXNvTm9ybWFsIj48c3BhbiBzdHlsZT0iZm9udC1zaXplOjEyLjBw
dDtmb250LWZhbWlseTomcXVvdDtIZWx2ZXRpY2EmcXVvdDssc2Fucy1zZXJpZiI+SU1QT1JUQU5U
IE5PVElDRTogVGhlIGNvbnRlbnRzIG9mIHRoaXMgZW1haWwgYW5kIGFueSBhdHRhY2htZW50cyBh
cmUgY29uZmlkZW50aWFsIGFuZCBtYXkgYWxzbyBiZSBwcml2aWxlZ2VkLiBJZiB5b3UgYXJlIG5v
dCB0aGUgaW50ZW5kZWQgcmVjaXBpZW50LCBwbGVhc2Ugbm90aWZ5IHRoZSBzZW5kZXINCiBpbW1l
ZGlhdGVseSBhbmQgZG8gbm90IGRpc2Nsb3NlIHRoZSBjb250ZW50cyB0byBhbnkgb3RoZXIgcGVy
c29uLCB1c2UgaXQgZm9yIGFueSBwdXJwb3NlLCBvciBzdG9yZSBvciBjb3B5IHRoZSBpbmZvcm1h
dGlvbiBpbiBhbnkgbWVkaXVtLiBUaGFuayB5b3UuIF9fX19fX19fX19fX19fX19fX19fX19fX19f
X19fX19fX19fX19fX19fX19fX19fPGJyPg0KRW11IG1haWxpbmcgbGlzdDxicj4NCjwvc3Bhbj48
YSBocmVmPSJtYWlsdG86RW11QGlldGYub3JnIiB0YXJnZXQ9Il9ibGFuayI+PHNwYW4gc3R5bGU9
ImZvbnQtc2l6ZToxMi4wcHQ7Zm9udC1mYW1pbHk6JnF1b3Q7SGVsdmV0aWNhJnF1b3Q7LHNhbnMt
c2VyaWYiPkVtdUBpZXRmLm9yZzwvc3Bhbj48L2E+PHNwYW4gc3R5bGU9ImZvbnQtc2l6ZToxMi4w
cHQ7Zm9udC1mYW1pbHk6JnF1b3Q7SGVsdmV0aWNhJnF1b3Q7LHNhbnMtc2VyaWYiPjxicj4NCjwv
c3Bhbj48YSBocmVmPSJodHRwczovL3d3dy5pZXRmLm9yZy9tYWlsbWFuL2xpc3RpbmZvL2VtdSIg
dGFyZ2V0PSJfYmxhbmsiPjxzcGFuIHN0eWxlPSJmb250LXNpemU6MTIuMHB0O2ZvbnQtZmFtaWx5
OiZxdW90O0hlbHZldGljYSZxdW90OyxzYW5zLXNlcmlmIj5odHRwczovL3d3dy5pZXRmLm9yZy9t
YWlsbWFuL2xpc3RpbmZvL2VtdTwvc3Bhbj48L2E+PG86cD48L286cD48L3A+DQo8L2Rpdj4NCjwv
YmxvY2txdW90ZT4NCjwvZGl2Pg0KPHAgY2xhc3M9Ik1zb05vcm1hbCI+PG86cD4mbmJzcDs8L286
cD48L3A+DQo8L2Rpdj4NCjwvZGl2Pg0KPHAgY2xhc3M9Ik1zb05vcm1hbCI+X19fX19fX19fX19f
X19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX188YnI+DQpFbXUgbWFpbGluZyBsaXN0
PGJyPg0KPGEgaHJlZj0ibWFpbHRvOkVtdUBpZXRmLm9yZyIgdGFyZ2V0PSJfYmxhbmsiPkVtdUBp
ZXRmLm9yZzwvYT48YnI+DQo8YSBocmVmPSJodHRwczovL3d3dy5pZXRmLm9yZy9tYWlsbWFuL2xp
c3RpbmZvL2VtdSIgdGFyZ2V0PSJfYmxhbmsiPmh0dHBzOi8vd3d3LmlldGYub3JnL21haWxtYW4v
bGlzdGluZm8vZW11PC9hPjxvOnA+PC9vOnA+PC9wPg0KPC9ibG9ja3F1b3RlPg0KPC9kaXY+DQo8
L2Rpdj4NCjwvZGl2Pg0KSU1QT1JUQU5UIE5PVElDRTogVGhlIGNvbnRlbnRzIG9mIHRoaXMgZW1h
aWwgYW5kIGFueSBhdHRhY2htZW50cyBhcmUgY29uZmlkZW50aWFsIGFuZCBtYXkgYWxzbyBiZSBw
cml2aWxlZ2VkLiBJZiB5b3UgYXJlIG5vdCB0aGUgaW50ZW5kZWQgcmVjaXBpZW50LCBwbGVhc2Ug
bm90aWZ5IHRoZSBzZW5kZXIgaW1tZWRpYXRlbHkgYW5kIGRvIG5vdCBkaXNjbG9zZSB0aGUgY29u
dGVudHMgdG8gYW55IG90aGVyIHBlcnNvbiwgdXNlIGl0IGZvciBhbnkgcHVycG9zZSwNCiBvciBz
dG9yZSBvciBjb3B5IHRoZSBpbmZvcm1hdGlvbiBpbiBhbnkgbWVkaXVtLiBUaGFuayB5b3UuDQo8
L2JvZHk+DQo8L2h0bWw+DQo=

--_000_AM0PR08MB371649BBA92B7F624008D0B3FA1A0AM0PR08MB3716eurp_--


From nobody Fri Oct 23 05:54:12 2020
Return-Path: <aland@deployingradius.com>
X-Original-To: emu@ietfa.amsl.com
Delivered-To: emu@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 1B3E13A0ADC for <emu@ietfa.amsl.com>; Fri, 23 Oct 2020 05:54:11 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.899
X-Spam-Level: 
X-Spam-Status: No, score=-1.899 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, SPF_HELO_NONE=0.001, SPF_PASS=-0.001, URIBL_BLOCKED=0.001] autolearn=ham autolearn_force=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 lEJaXKEKtDuk for <emu@ietfa.amsl.com>; Fri, 23 Oct 2020 05:54:09 -0700 (PDT)
Received: from mail.networkradius.com (mail.networkradius.com [62.210.147.122]) (using TLSv1.2 with cipher ADH-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id BE7B03A0AB2 for <emu@ietf.org>; Fri, 23 Oct 2020 05:54:09 -0700 (PDT)
Received: from [192.168.46.130] (24-52-251-6.cable.teksavvy.com [24.52.251.6]) by mail.networkradius.com (Postfix) with ESMTPSA id EC38D91; Fri, 23 Oct 2020 12:54:06 +0000 (UTC)
Authentication-Results: NetworkRADIUS; dmarc=none (p=none dis=none) header.from=deployingradius.com
Content-Type: text/plain; charset=utf-8
Mime-Version: 1.0 (Mac OS X Mail 13.4 \(3608.120.23.2.1\))
From: Alan DeKok <aland@deployingradius.com>
In-Reply-To: <AM0PR08MB371649BBA92B7F624008D0B3FA1A0@AM0PR08MB3716.eurprd08.prod.outlook.com>
Date: Fri, 23 Oct 2020 08:54:05 -0400
Cc: Joseph Salowey <joe@salowey.net>, Eliot Lear <lear=40cisco.com@dmarc.ietf.org>, "emu@ietf.org" <emu@ietf.org>
Content-Transfer-Encoding: quoted-printable
Message-Id: <D7FC8B51-3545-4D30-8B6F-35C169B0462B@deployingradius.com>
References: <AM0PR08MB371647618F993B8C5BA6EB5FFA1C0@AM0PR08MB3716.eurprd08.prod.outlook.com> <AD94F3FF-31A7-4F44-95F7-6A7E70FA8D27@cisco.com> <CAOgPGoD3MQu=Hv6HTfug0XredaRt_T7oD7z_uwnATmHku9DmLg@mail.gmail.com> <AM0PR08MB371649BBA92B7F624008D0B3FA1A0@AM0PR08MB3716.eurprd08.prod.outlook.com>
To: Hannes Tschofenig <Hannes.Tschofenig@arm.com>
X-Mailer: Apple Mail (2.3608.120.23.2.1)
Archived-At: <https://mailarchive.ietf.org/arch/msg/emu/bX_-VzNf7PCPjcJglRicFTvplaQ>
Subject: Re: [Emu] draft-ietf-emu-eap-tls13-11: OCSP Stapling
X-BeenThere: emu@ietf.org
X-Mailman-Version: 2.1.29
Precedence: list
List-Id: "EAP Methods Update \(EMU\)" <emu.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/emu>, <mailto:emu-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/emu/>
List-Post: <mailto:emu@ietf.org>
List-Help: <mailto:emu-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/emu>, <mailto:emu-request@ietf.org?subject=subscribe>
X-List-Received-Date: Fri, 23 Oct 2020 12:54:11 -0000

On Oct 23, 2020, at 3:37 AM, Hannes Tschofenig =
<Hannes.Tschofenig@arm.com> wrote:
> I do not understand certificate revocation checking is a topic =
specific to the use of TLS 1.3 in EAP-TLS.

  It's not.

  However, in the absence of another specification, we need to say =
*something* for EAP-TLS.

> If this topic is important to the group then why isn=E2=80=99t this a =
generic recommendations for all EAP methods that use public key based =
authentication?

  I believe it should be.  I can update draft-ietf-emu-tls-eap-types to =
clarify this.  Basically "almost everything else in EAP-TLS applies to =
all other TLS-based EAP types, too".

> Wouldn=E2=80=99t this be a topic to address in =
<draft-ietf-emu-eaptlscert>? IMHO this would make more sense given that =
<draft-ietf-emu-eaptlscert> talks about large certificates and long =
certificate chains and any proposal to make those even larger should be =
evaluated in this context.=20

  I think that the topics are related.  But draft-ietf-emu-eap-tls13 is =
more about the protocol, and draft-ietf-emu-eaptlscert is more about =
deployment considerations.

  For me, this means that security issues such as certificate revocation =
checking belong in the protocol specification, not in a deployment =
guide.

  Alan DeKok.


From nobody Fri Oct 23 09:11:18 2020
Return-Path: <j@w1.fi>
X-Original-To: emu@ietfa.amsl.com
Delivered-To: emu@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id C5F573A0FCE for <emu@ietfa.amsl.com>; Fri, 23 Oct 2020 09:11:16 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.899
X-Spam-Level: 
X-Spam-Status: No, score=-1.899 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, SPF_HELO_NONE=0.001, SPF_PASS=-0.001, URIBL_BLOCKED=0.001] autolearn=ham autolearn_force=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 gBHYdpEExvh9 for <emu@ietfa.amsl.com>; Fri, 23 Oct 2020 09:11:15 -0700 (PDT)
Received: from li674-96.members.linode.com (mail.w1.fi [212.71.239.96]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id A2FF33A0FCC for <emu@ietf.org>; Fri, 23 Oct 2020 09:11:14 -0700 (PDT)
Received: from localhost (localhost [127.0.0.1]) by li674-96.members.linode.com (Postfix) with ESMTP id C01BB11B71; Fri, 23 Oct 2020 16:11:12 +0000 (UTC)
X-Virus-Scanned: Debian amavisd-new at w1.fi
Received: from li674-96.members.linode.com ([127.0.0.1]) by localhost (mail.w1.fi [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id E_93arYi52rH; Fri, 23 Oct 2020 16:11:10 +0000 (UTC)
Received: by jm (sSMTP sendmail emulation); Fri, 23 Oct 2020 19:08:15 +0300
Date: Fri, 23 Oct 2020 19:08:15 +0300
From: Jouni Malinen <j@w1.fi>
To: Joseph Salowey <joe@salowey.net>
Cc: EMU WG <emu@ietf.org>, "Oleg Pekar (olpekar)" <olpekar@cisco.com>, Jorge Vergara <jovergar=40microsoft.com@dmarc.ietf.org>
Message-ID: <20201023160815.GA15442@w1.fi>
References: <CAOgPGoC83neA1mGBwbA5Bqfj1K3CFOvphb0ZNwcMeUAFyB1PRw@mail.gmail.com> <20201021190824.GA8827@w1.fi> <CAOgPGoCqdFucScjOp30aj3EcTZ72x_aOBSOBYD1r04Us_8ZUNg@mail.gmail.com>
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
In-Reply-To: <CAOgPGoCqdFucScjOp30aj3EcTZ72x_aOBSOBYD1r04Us_8ZUNg@mail.gmail.com>
Archived-At: <https://mailarchive.ietf.org/arch/msg/emu/czo2i9B2eKwH33nJW85Z4RtkGY8>
Subject: Re: [Emu] Proposed resolution for TEAP errata 5127
X-BeenThere: emu@ietf.org
X-Mailman-Version: 2.1.29
Precedence: list
List-Id: "EAP Methods Update \(EMU\)" <emu.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/emu>, <mailto:emu-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/emu/>
List-Post: <mailto:emu@ietf.org>
List-Help: <mailto:emu-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/emu>, <mailto:emu-request@ietf.org?subject=subscribe>
X-List-Received-Date: Fri, 23 Oct 2020 16:11:17 -0000

On Wed, Oct 21, 2020 at 02:14:45PM -0700, Joseph Salowey wrote:
> On Wed, Oct 21, 2020 at 12:11 PM Jouni Malinen <j@w1.fi> wrote:
> 
> > On Wed, Oct 21, 2020 at 09:30:33AM -0700, Joseph Salowey wrote:
> > > Errata 5127: https://www.rfc-editor.org/errata/eid5127
> > > Proposed State: Verified
> > > Revision:
> > > Section 5.2.
> > > OLD
> > >
> > > IMSK = First 32 octets of TLS-PRF(EMSK, "TEAPbindkey@ietf.org" |
> > >      "\0" | 64)
> > >
> > > NEW
> > >
> > > IMSK = First 32 octets of TLS-PRF(EMSK, "TEAPbindkey@ietf.org" |
> > >    '/0', 64)
> >
> > Why would this change "\0" to '/0'?
> >
> > [Joe] that was my mistake should be "/0"
> 
> 
> > How is that 64 supposed to be encoded if it is the "seed" argument to
> > PRF(secret, label, seed) define in RFC 5246 Section 5?
> >
> >
> [Joe] 7170 says "length is the 2-octet unsigned integer in network byte
> order"

It does, but how would one know that this particular 64 is "length"?
This "64" argument is the "seed" argument to PRF and that could be any
arbitrary data.. The length of TLS-PRF output is meta data that is not
passed to the PSK() defined in RFC 5246 directly as an argument, i.e.,
inclusion of the output length in the seed is something that RFC 7170 is
doing here for some reason and it could have included any other
arbitrary seed value here for that matter.. IMHO, this is too vague and
it would be better to spell out the exact contents of the seed value
(0x00 | 0x40 im this particular case shown here or 0x00 | 0x00 | 0x40 if
following the proposal below).

> > Using P_hash(EMSK, "TEAPbindkey@ietf.org" | 0x00 | 0x00 | 0x40) looks
> > correct, but it looks strange to me if we are trying to include the
> > first 0x00 at the end of the "label" argument to PRF(secret, label,
> > seed) especially when the label is define to be "an ASCII string. It
> > should be included in the exact form it is given without a length byte
> > or trailing null character". I would have expected
> > "TEAPbindkey@ietf.org" to be the "label" while 0x00 | 0x00 | 0x40 would
> > be the "seed". In other words:
> >
> > IMSK = First 32 octets of TLS-PRF(EMSK, "TEAPbindkey@ietf.org",
> >                                   0x00 | 0x00 | 0x40).
> >
> >
> [Joe] Yes I agree that is better how about this as the text change
> 
> IMSK = First 32 octets of TLS-PRF(EMSK, "TEAPbindkey@ietf.org", "\0" |  64)

It looks quite strange to me to define a binary seed data as a
concatenation of a string and an integer. I have the exact same question
about the encoding of 64 here since this does not describe explicitly
this instance of 64 to be the "length" which has the particular encoding
described in RFC 7170. For me, using 0x00 | 0x00 | 0x40 and deleting
that note about length encoding would be significantly clearer. If that
is not acceptable, I would still replace "\0" with 0x00 in this context
since this is not an ASCII string or label anymore, but binary data. And
in addition to that, the "64" part would need to be replaced with
something like "TLS-PRF output length" and then the "TLS-PRF output
length" could be mentioned to be 64 in this instance and the encoding
for that would be 2-octet unsigned integer in network byte order.

-- 
Jouni Malinen                                            PGP id EFC895FA


From nobody Fri Oct 23 09:20:11 2020
Return-Path: <j@w1.fi>
X-Original-To: emu@ietfa.amsl.com
Delivered-To: emu@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id C393D3A0FE8 for <emu@ietfa.amsl.com>; Fri, 23 Oct 2020 09:20:09 -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, SPF_HELO_NONE=0.001, SPF_PASS=-0.001] autolearn=unavailable autolearn_force=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 qt4jQ-mIs-_7 for <emu@ietfa.amsl.com>; Fri, 23 Oct 2020 09:20:07 -0700 (PDT)
Received: from li674-96.members.linode.com (mail.w1.fi [212.71.239.96]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id AD5363A0FDF for <emu@ietf.org>; Fri, 23 Oct 2020 09:20:07 -0700 (PDT)
Received: from localhost (localhost [127.0.0.1]) by li674-96.members.linode.com (Postfix) with ESMTP id 2C5FF11B71; Fri, 23 Oct 2020 16:20:06 +0000 (UTC)
X-Virus-Scanned: Debian amavisd-new at w1.fi
Received: from li674-96.members.linode.com ([127.0.0.1]) by localhost (mail.w1.fi [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 61rhl0fiHFSo; Fri, 23 Oct 2020 16:20:00 +0000 (UTC)
Received: by jm (sSMTP sendmail emulation); Fri, 23 Oct 2020 19:17:05 +0300
Date: Fri, 23 Oct 2020 19:17:05 +0300
From: Jouni Malinen <j@w1.fi>
To: Oleg Pekar <oleg.pekar.2017@gmail.com>
Cc: Joseph Salowey <joe@salowey.net>, EMU WG <emu@ietf.org>, Jorge Vergara <jovergar=40microsoft.com@dmarc.ietf.org>
Message-ID: <20201023161705.GB15442@w1.fi>
References: <CAOgPGoCmYCEKgE6P_Ja5VRLh4M1jWSML_WNuqdHA-t2TibBnjA@mail.gmail.com> <CABXxEz877CEXHnMSR88KhbYQHZEoEve0EY+ORQr-KN3ehEsY8w@mail.gmail.com>
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
In-Reply-To: <CABXxEz877CEXHnMSR88KhbYQHZEoEve0EY+ORQr-KN3ehEsY8w@mail.gmail.com>
Archived-At: <https://mailarchive.ietf.org/arch/msg/emu/sq7bVRJO5SKI_RY8wkKUv9bz73M>
Subject: Re: [Emu] Proposed resolution for TEAP errata 5765
X-BeenThere: emu@ietf.org
X-Mailman-Version: 2.1.29
Precedence: list
List-Id: "EAP Methods Update \(EMU\)" <emu.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/emu>, <mailto:emu-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/emu/>
List-Post: <mailto:emu@ietf.org>
List-Help: <mailto:emu-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/emu>, <mailto:emu-request@ietf.org?subject=subscribe>
X-List-Received-Date: Fri, 23 Oct 2020 16:20:10 -0000

On Thu, Oct 22, 2020 at 05:44:33PM +0300, Oleg Pekar wrote:
> The Authority-ID TLV is used by the client to identify the TEAP server it
> is talking to. If the same client talks to more than one TEAP server - it
> can keep PACs or cached data from all of them identified by
> the Authority-ID. If we make it optional in TEAP start message but keep
> mandatory in PAC-Info part of the PAC - TEAP servers can stop sending it
> during TEAP start and then clients will need to fetch it from PAC, if there
> is a PAC in the conversation. But if there's no PAC - then no way to
> identify TEAP server.
> 
> Maybe we should keep it mandatory?

That would be in conflict with Section 4.3.1: "Outer TLVs MUST be marked
as optional."

Please note that this M flag does not define whether the attribute must
be included in the message; it defines whether the recipient has to
reject the message if it does not support the TLV. We can still
require the Authority-ID TLV to be present in TEAP/Start while marking
it optional for the receiver to understand it (M=0).. And Section 3.2
does indeed say that:
   The EAP server initiates the TEAP conversation with an EAP request
   containing a TEAP/Start packet.  This packet includes a set Start (S)
   bit, the TEAP version as specified in Section 3.1, and an authority
   identity TLV.

This is still valid with M=0 for that TLV..

-- 
Jouni Malinen                                            PGP id EFC895FA


From nobody Fri Oct 23 09:58:51 2020
Return-Path: <j@w1.fi>
X-Original-To: emu@ietfa.amsl.com
Delivered-To: emu@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 46C883A0769 for <emu@ietfa.amsl.com>; Fri, 23 Oct 2020 09:58:50 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.898
X-Spam-Level: 
X-Spam-Status: No, score=-1.898 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RCVD_IN_DNSWL_BLOCKED=0.001, SPF_HELO_NONE=0.001, SPF_PASS=-0.001, URIBL_BLOCKED=0.001] autolearn=ham autolearn_force=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 AtJRYhitP9-k for <emu@ietfa.amsl.com>; Fri, 23 Oct 2020 09:58:48 -0700 (PDT)
Received: from li674-96.members.linode.com (mail.w1.fi [212.71.239.96]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 160EF3A03FC for <emu@ietf.org>; Fri, 23 Oct 2020 09:58:47 -0700 (PDT)
Received: from localhost (localhost [127.0.0.1]) by li674-96.members.linode.com (Postfix) with ESMTP id 300F811B73; Fri, 23 Oct 2020 16:58:46 +0000 (UTC)
X-Virus-Scanned: Debian amavisd-new at w1.fi
Received: from li674-96.members.linode.com ([127.0.0.1]) by localhost (mail.w1.fi [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id EZnfx73QbBGz; Fri, 23 Oct 2020 16:58:44 +0000 (UTC)
Received: by jm (sSMTP sendmail emulation); Fri, 23 Oct 2020 19:55:49 +0300
Date: Fri, 23 Oct 2020 19:55:49 +0300
From: Jouni Malinen <j@w1.fi>
To: Oleg Pekar <oleg.pekar.2017@gmail.com>
Cc: Jorge Vergara <jovergar@microsoft.com>, Joseph Salowey <joe@salowey.net>, EMU WG <emu@ietf.org>
Message-ID: <20201023165549.GC15442@w1.fi>
References: <CH2PR21MB138143E929DAFE3C893D8144D11C0@CH2PR21MB1381.namprd21.prod.outlook.com> <CAOgPGoAtcm+Br+YkCyTtg5nJjqO7LGSo77b+CD4+Ba05azafew@mail.gmail.com> <CH2PR21MB13815BCEDC846D7C440AD564D11C0@CH2PR21MB1381.namprd21.prod.outlook.com> <CAOgPGoDTC-qiHOXFTJd7aMn2To7ySzBcx+iQMB9m5foC1bFxzw@mail.gmail.com> <CABXxEz8SRvMXdMR8_cPfvWdauJZwCjnd=7ytnVZ+_L-sB48wvw@mail.gmail.com> <CAOgPGoCsWy-uhYeeHCDUaazjAwfWtr_zkS5CUoX8+baASahFEg@mail.gmail.com> <CABXxEz9euWaA9Y66+1u4gtFCWkrPUEd-juY_TFUHPQE4R_OpRg@mail.gmail.com> <CAOgPGoDcD7wjiMt2=t0vx2FPr2LD2S3eU1d0_bVU1c88S=tA=w@mail.gmail.com> <CH2PR21MB13810C16054DD1DDB4055659D11D0@CH2PR21MB1381.namprd21.prod.outlook.com> <CABXxEz8JP07gLB2Tknx1ahErZ=ydVVq2XORLadDatBcSjVu3-Q@mail.gmail.com>
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
In-Reply-To: <CABXxEz8JP07gLB2Tknx1ahErZ=ydVVq2XORLadDatBcSjVu3-Q@mail.gmail.com>
Archived-At: <https://mailarchive.ietf.org/arch/msg/emu/DiaeBIQT15ofKuf0S2AXiwGnXk4>
Subject: Re: [Emu] Proposed resolution for TEAP errata for 5128
X-BeenThere: emu@ietf.org
X-Mailman-Version: 2.1.29
Precedence: list
List-Id: "EAP Methods Update \(EMU\)" <emu.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/emu>, <mailto:emu-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/emu/>
List-Post: <mailto:emu@ietf.org>
List-Help: <mailto:emu-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/emu>, <mailto:emu-request@ietf.org?subject=subscribe>
X-List-Received-Date: Fri, 23 Oct 2020 16:58:50 -0000

There were so many messages in this thread that I'm not going try to
address each point separately, but I think in general I do agree with
the comments and it looks like all the identified implementation are
doing the same thing here..

I don't see any strong need to encode the output length of the PRF into
the input data especially since we are using hardcoded output lengths in
these cases. That said, I'm not against keeping it there for the IMSK
derivation since that particular case seemed to be explicitly defined as
using a 2-octet field in network byte order (and all the known
implementations doing exactly that). IMHO, the other cases should not be
modified to try to be consistent with this.

While I do understand the benefits of having an explicit fixed delimiter
"\0" between the label and seed to enforce unique interpretation if two
labels were to have same prefix, I don't see that as a critical issue in
any of the instances used within TEAP due to no such common prefix case
exist nor do we even use TLS-PRF with the same secret/key. Furthermore,
RFC 5246 does not mandate or even discuss such delimiter.

There is no need to convert an empty seed to 0x00 or anything else.
TLS-PRF can be used with secret=something, label=ASCII string,
seed=0-length data) without issues.

If we want to define a new TEAP-PRF() function, I'd prefer it to be
using consistent terminology with TLS-PRF in RFC 5246 (and well, to
extend possible, also be as consistent as can be with the TLS-Exporter
use in RFC 8446). This would also mean not trying to enforce some 0x00
delimiter or length in context data. At its simplest and only with TLS
v1.2 in mind for clarity here, this could look something like

TEAP-PRF(secret, label, seed, output length) =
PRF(secret, label, seed) outputting "output length" octets

label = ASCII string, no "\x0" termination
seed = arbitrary binary data (including possibility of 0-length empty
case)

With this, we would have following:
IMSK = First 32 octets of TEAP-PRF(EMSK, "TEAPbindkey@ietf.org", 0x00 |
0x00 | 0x40, 64)
IMCK[j] = TEAP-PRF(S-IMCK[j-1], "Inner Methods Compound Keys", IMSK[j], 60)
MSK = TEAP-PRF(S-IMCK[j], "Session Key Generating Function", <empty>, 64)
EMSK = TEAP-PRF(S-IMCK[j], "Extended Session Key Generating Function",
<empty>, 64)

RFC 5295 rules about EMSK use for USRK/DSRK applies for the first one of
these and it does seem to give justification for the seed to have "\0"
and "length" (as 2-octet unsigned integer in network byte order). While
one could claim that the rules for DSUSRK derivation applies to those
other instances and as such, would require 0x00 and length to be added
around the seed shown above, I'd note that there does not seem to be any
MUST statement about that in RFC 5295 and as such, I think the versions
described above (and the ones used in known implementations today) seem
to be justifiable especially taken into account the unique label string
prefixes and fixed length of output data.

-- 
Jouni Malinen                                            PGP id EFC895FA


From nobody Fri Oct 23 12:27:08 2020
Return-Path: <joe@salowey.net>
X-Original-To: emu@ietfa.amsl.com
Delivered-To: emu@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 6E1E93A0639 for <emu@ietfa.amsl.com>; Fri, 23 Oct 2020 12:27:07 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.898
X-Spam-Level: 
X-Spam-Status: No, score=-1.898 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, HTML_MESSAGE=0.001, SPF_HELO_NONE=0.001, SPF_PASS=-0.001, URIBL_BLOCKED=0.001] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (2048-bit key) header.d=salowey-net.20150623.gappssmtp.com
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 bs_rP6TzzSut for <emu@ietfa.amsl.com>; Fri, 23 Oct 2020 12:27:05 -0700 (PDT)
Received: from mail-qk1-x72c.google.com (mail-qk1-x72c.google.com [IPv6:2607:f8b0:4864:20::72c]) (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 753413A05A6 for <emu@ietf.org>; Fri, 23 Oct 2020 12:27:05 -0700 (PDT)
Received: by mail-qk1-x72c.google.com with SMTP id s14so2241832qkg.11 for <emu@ietf.org>; Fri, 23 Oct 2020 12:27:05 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=salowey-net.20150623.gappssmtp.com; s=20150623; h=mime-version:references:in-reply-to:from:date:message-id:subject:to :cc; bh=ExZNtDQ8Nz16k8AFBj5DB1sgcIScqQM+swRtw/qtKGU=; b=s/7wUOr8kel42cYDjk8B7n3awaU9tWeB1xrEDAOe/Q/r8GL8R+yozqHP52pqTXbQ53 nCU1NLvU+RH3WBhJ5XQ102PMraiuaCEivWKfAhJFuphIVTX1cwPiIGEGRj4PjKVnZ4aW SsAwlkjRE8fyvkxjz0PYyBvuAo08jn4htCSfiD3/h3x5dSk0WQZmcvb8MxiNJ0HglOb2 2PfCWPX0ephqlbmVawTn/DDCPGMs+/Hs7KY9EF0LoIuz0KwZxuobwq/C+2qC4tpnBLHA G4ByMI2Iu19pimA4rXoRMWqDLpFsh0kdPzVleABvRgjrZ8FmYxnvFKn0MAGOGYn/EhDn A6VQ==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:mime-version:references:in-reply-to:from:date :message-id:subject:to:cc; bh=ExZNtDQ8Nz16k8AFBj5DB1sgcIScqQM+swRtw/qtKGU=; b=MEUG0/IyzwUAW7N/hVLfLWghTGu1GskENYWpodwHm8bc6m0lHSnB59xfg59rVKgJ8Z TiZhAk7HCcGTvLNF5d87XGu3Zp+0HoAAXp0lbQefmTmwFjb5jm9Tuy2DrlnpZGht8Z8x qccAD0APwM1sfmv+ZxFQ7Px2TkuA6oTtM826in5Sk2grcLuWjwjreXEo5uIhCitdXINQ TdgU+cj/g9xEMBvYT5jK6iSAvW0ZSfVk1TyQWj/vYrZXGgCRrPQ+69pxIl3AQK0dv2xU MndNkO9cWgwUeiASa8ZVEnYuzohyTXjbqEtx1lSGMqrT4Ipw+MRh1gyWbfM3ZyOhuANZ YkFw==
X-Gm-Message-State: AOAM532IrOjeMSXTjT8o5kqvQxcqT1YaUvC2lE0mTuvgjBHbadbmMcFP qU0Zn2+npnMBAy3vlEqjE/+KBps7XTAJAEokMTnc6heN7IjLeQ==
X-Google-Smtp-Source: ABdhPJzCLm5n2hWqOb2NqW5V/JFhUJObGkbu3srBAwrcyywxlRoTqkDFAC9m69pZS2ZkPwQDz5q5EP7PEhWUEnsAbOk=
X-Received: by 2002:a05:620a:215d:: with SMTP id m29mr3937752qkm.138.1603481224400;  Fri, 23 Oct 2020 12:27:04 -0700 (PDT)
MIME-Version: 1.0
References: <CAOgPGoC83neA1mGBwbA5Bqfj1K3CFOvphb0ZNwcMeUAFyB1PRw@mail.gmail.com> <20201021190824.GA8827@w1.fi> <CAOgPGoCqdFucScjOp30aj3EcTZ72x_aOBSOBYD1r04Us_8ZUNg@mail.gmail.com> <20201023160815.GA15442@w1.fi>
In-Reply-To: <20201023160815.GA15442@w1.fi>
From: Joseph Salowey <joe@salowey.net>
Date: Fri, 23 Oct 2020 12:26:53 -0700
Message-ID: <CAOgPGoC5iLtL6SqDPMD0Fn52HSwMNDR1fbHcq5EpU_FAuo3yxg@mail.gmail.com>
To: Jouni Malinen <j@w1.fi>
Cc: EMU WG <emu@ietf.org>, "Oleg Pekar (olpekar)" <olpekar@cisco.com>,  Jorge Vergara <jovergar=40microsoft.com@dmarc.ietf.org>
Content-Type: multipart/alternative; boundary="000000000000c8e6f605b25b90df"
Archived-At: <https://mailarchive.ietf.org/arch/msg/emu/tudIX51gwUrpfafhAVEELzrVy-4>
Subject: Re: [Emu] Proposed resolution for TEAP errata 5127
X-BeenThere: emu@ietf.org
X-Mailman-Version: 2.1.29
Precedence: list
List-Id: "EAP Methods Update \(EMU\)" <emu.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/emu>, <mailto:emu-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/emu/>
List-Post: <mailto:emu@ietf.org>
List-Help: <mailto:emu-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/emu>, <mailto:emu-request@ietf.org?subject=subscribe>
X-List-Received-Date: Fri, 23 Oct 2020 19:27:07 -0000

--000000000000c8e6f605b25b90df
Content-Type: text/plain; charset="UTF-8"

On Fri, Oct 23, 2020 at 9:11 AM Jouni Malinen <j@w1.fi> wrote:

> On Wed, Oct 21, 2020 at 02:14:45PM -0700, Joseph Salowey wrote:
> > On Wed, Oct 21, 2020 at 12:11 PM Jouni Malinen <j@w1.fi> wrote:
> >
> > > On Wed, Oct 21, 2020 at 09:30:33AM -0700, Joseph Salowey wrote:
> > > > Errata 5127: https://www.rfc-editor.org/errata/eid5127
> > > > Proposed State: Verified
> > > > Revision:
> > > > Section 5.2.
> > > > OLD
> > > >
> > > > IMSK = First 32 octets of TLS-PRF(EMSK, "TEAPbindkey@ietf.org" |
> > > >      "\0" | 64)
> > > >
> > > > NEW
> > > >
> > > > IMSK = First 32 octets of TLS-PRF(EMSK, "TEAPbindkey@ietf.org" |
> > > >    '/0', 64)
> > >
> > > Why would this change "\0" to '/0'?
> > >
> > > [Joe] that was my mistake should be "/0"
> >
> >
> > > How is that 64 supposed to be encoded if it is the "seed" argument to
> > > PRF(secret, label, seed) define in RFC 5246 Section 5?
> > >
> > >
> > [Joe] 7170 says "length is the 2-octet unsigned integer in network byte
> > order"
>
> It does, but how would one know that this particular 64 is "length"?
> This "64" argument is the "seed" argument to PRF and that could be any
> arbitrary data.. The length of TLS-PRF output is meta data that is not
> passed to the PSK() defined in RFC 5246 directly as an argument, i.e.,
> inclusion of the output length in the seed is something that RFC 7170 is
> doing here for some reason and it could have included any other
> arbitrary seed value here for that matter.. IMHO, this is too vague and
> it would be better to spell out the exact contents of the seed value
> (0x00 | 0x40 im this particular case shown here or 0x00 | 0x00 | 0x40 if
> following the proposal below).
>
>
[Joe]  The length is called out as 64 octets in the sentence just before
this, to me this is not very vague.   However, I do agree that specifying
the exact encoding would be even clearer.  Here is a proposed revision that
I think addresses this and the comment later on in the message:

IMSK = First 32 octets of TLS-PRF(EMSK, "TEAPbindkey@ietf.org",
     0x00 | 0x00 | 0x40)

     where "|" denotes concatenation and the TLS-PRF is defined in
      [RFC5246] as

     PRF(secret, label, seed) = P_<hash>(secret, label | seed).

     the secret is the EMSK from the inner method, the label is
     "TEAPbindkey@ietf.org" consisting of the ASCII value for the
     label "TEAPbindkey@ietf.org" (without quotes),  the seed
     consists of the "\0" null delimiter (0x00) and 2-octet unsigned
     integer length in network byte order (0x00 | 0x4) specified
     in [RFC5295]


> > > Using P_hash(EMSK, "TEAPbindkey@ietf.org" | 0x00 | 0x00 | 0x40) looks
> > > correct, but it looks strange to me if we are trying to include the
> > > first 0x00 at the end of the "label" argument to PRF(secret, label,
> > > seed) especially when the label is define to be "an ASCII string. It
> > > should be included in the exact form it is given without a length byte
> > > or trailing null character". I would have expected
> > > "TEAPbindkey@ietf.org" to be the "label" while 0x00 | 0x00 | 0x40
> would
> > > be the "seed". In other words:
> > >
> > > IMSK = First 32 octets of TLS-PRF(EMSK, "TEAPbindkey@ietf.org",
> > >                                   0x00 | 0x00 | 0x40).
> > >
> > >
> > [Joe] Yes I agree that is better how about this as the text change
> >
> > IMSK = First 32 octets of TLS-PRF(EMSK, "TEAPbindkey@ietf.org", "\0" |
> 64)
>
> It looks quite strange to me to define a binary seed data as a
> concatenation of a string and an integer. I have the exact same question
> about the encoding of 64 here since this does not describe explicitly
> this instance of 64 to be the "length" which has the particular encoding
> described in RFC 7170. For me, using 0x00 | 0x00 | 0x40 and deleting
> that note about length encoding would be significantly clearer. If that
> is not acceptable, I would still replace "\0" with 0x00 in this context
> since this is not an ASCII string or label anymore, but binary data. And
> in addition to that, the "64" part would need to be replaced with
> something like "TLS-PRF output length" and then the "TLS-PRF output
> length" could be mentioned to be 64 in this instance and the encoding
> for that would be 2-octet unsigned integer in network byte order.
>
> --
> Jouni Malinen                                            PGP id EFC895FA
>

--000000000000c8e6f605b25b90df
Content-Type: text/html; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable

<div dir=3D"ltr"><div dir=3D"ltr"><br></div><br><div class=3D"gmail_quote">=
<div dir=3D"ltr" class=3D"gmail_attr">On Fri, Oct 23, 2020 at 9:11 AM Jouni=
 Malinen &lt;<a href=3D"mailto:j@w1.fi" target=3D"_blank">j@w1.fi</a>&gt; w=
rote:<br></div><blockquote class=3D"gmail_quote" style=3D"margin:0px 0px 0p=
x 0.8ex;border-left:1px solid rgb(204,204,204);padding-left:1ex">On Wed, Oc=
t 21, 2020 at 02:14:45PM -0700, Joseph Salowey wrote:<br>
&gt; On Wed, Oct 21, 2020 at 12:11 PM Jouni Malinen &lt;<a href=3D"mailto:j=
@w1.fi" target=3D"_blank">j@w1.fi</a>&gt; wrote:<br>
&gt; <br>
&gt; &gt; On Wed, Oct 21, 2020 at 09:30:33AM -0700, Joseph Salowey wrote:<b=
r>
&gt; &gt; &gt; Errata 5127: <a href=3D"https://www.rfc-editor.org/errata/ei=
d5127" rel=3D"noreferrer" target=3D"_blank">https://www.rfc-editor.org/erra=
ta/eid5127</a><br>
&gt; &gt; &gt; Proposed State: Verified<br>
&gt; &gt; &gt; Revision:<br>
&gt; &gt; &gt; Section 5.2.<br>
&gt; &gt; &gt; OLD<br>
&gt; &gt; &gt;<br>
&gt; &gt; &gt; IMSK =3D First 32 octets of TLS-PRF(EMSK, &quot;<a href=3D"m=
ailto:TEAPbindkey@ietf.org" target=3D"_blank">TEAPbindkey@ietf.org</a>&quot=
; |<br>
&gt; &gt; &gt;=C2=A0 =C2=A0 =C2=A0 &quot;\0&quot; | 64)<br>
&gt; &gt; &gt;<br>
&gt; &gt; &gt; NEW<br>
&gt; &gt; &gt;<br>
&gt; &gt; &gt; IMSK =3D First 32 octets of TLS-PRF(EMSK, &quot;<a href=3D"m=
ailto:TEAPbindkey@ietf.org" target=3D"_blank">TEAPbindkey@ietf.org</a>&quot=
; |<br>
&gt; &gt; &gt;=C2=A0 =C2=A0 &#39;/0&#39;, 64)<br>
&gt; &gt;<br>
&gt; &gt; Why would this change &quot;\0&quot; to &#39;/0&#39;?<br>
&gt; &gt;<br>
&gt; &gt; [Joe] that was my mistake should be &quot;/0&quot;<br>
&gt; <br>
&gt; <br>
&gt; &gt; How is that 64 supposed to be encoded if it is the &quot;seed&quo=
t; argument to<br>
&gt; &gt; PRF(secret, label, seed) define in RFC 5246 Section 5?<br>
&gt; &gt;<br>
&gt; &gt;<br>
&gt; [Joe] 7170 says &quot;length is the 2-octet unsigned integer in networ=
k byte<br>
&gt; order&quot;<br>
<br>
It does, but how would one know that this particular 64 is &quot;length&quo=
t;?<br>
This &quot;64&quot; argument is the &quot;seed&quot; argument to PRF and th=
at could be any<br>
arbitrary data.. The length of TLS-PRF output is meta data that is not<br>
passed to the PSK() defined in RFC 5246 directly as an argument, i.e.,<br>
inclusion of the output length in the seed is something that RFC 7170 is<br=
>
doing here for some reason and it could have included any other<br>
arbitrary seed value here for that matter.. IMHO, this is too vague and<br>
it would be better to spell out the exact contents of the seed value<br>
(0x00 | 0x40 im this particular case shown here or 0x00 | 0x00 | 0x40 if<br=
>
following the proposal below).<br>
<br></blockquote><div><br></div><div>[Joe]=C2=A0 The length is called out a=
s 64 octets in the sentence just before this, to me this is not very vague.=
=C2=A0 =C2=A0However, I do agree that specifying the exact encoding would b=
e even clearer.=C2=A0 Here is a proposed revision that I think addresses th=
is and the comment later on in the message:</div><br>IMSK =3D First 32 octe=
ts of TLS-PRF(EMSK, &quot;<a href=3D"mailto:TEAPbindkey@ietf.org" target=3D=
"_blank">TEAPbindkey@ietf.org</a>&quot;,<br>=C2=A0 =C2=A0 =C2=A00x00 | 0x00=
 | 0x40)<br><br>=C2=A0 =C2=A0 =C2=A0where &quot;|&quot; denotes concatenati=
on and the TLS-PRF is defined in</div><div class=3D"gmail_quote">=C2=A0 =C2=
=A0 =C2=A0 [RFC5246] as=C2=A0</div><div class=3D"gmail_quote">=C2=A0 =C2=A0=
 =C2=A0</div><div class=3D"gmail_quote">=C2=A0 =C2=A0 =C2=A0PRF(secret, lab=
el, seed) =3D P_&lt;hash&gt;(secret, label | seed).<br></div><div class=3D"=
gmail_quote"><br></div><div class=3D"gmail_quote">=C2=A0 =C2=A0 =C2=A0the s=
ecret is the EMSK from the inner method, the label is=C2=A0</div><div class=
=3D"gmail_quote">=C2=A0 =C2=A0 =C2=A0&quot;<a href=3D"mailto:TEAPbindkey@ie=
tf.org" target=3D"_blank">TEAPbindkey@ietf.org</a>&quot; consisting of the =
ASCII value for the<br>=C2=A0 =C2=A0 =C2=A0label &quot;<a href=3D"mailto:TE=
APbindkey@ietf.org" target=3D"_blank">TEAPbindkey@ietf.org</a>&quot; (witho=
ut quotes),=C2=A0 the seed=C2=A0</div><div class=3D"gmail_quote">=C2=A0 =C2=
=A0 =C2=A0consists of=C2=A0the &quot;\0&quot; null delimiter (0x00) and 2-o=
ctet unsigned=C2=A0</div><div class=3D"gmail_quote">=C2=A0 =C2=A0 =C2=A0int=
eger length in network byte order (0x00 | 0x4) specified=C2=A0</div><div cl=
ass=3D"gmail_quote">=C2=A0 =C2=A0 =C2=A0in [RFC5295]</div><div class=3D"gma=
il_quote"><div>=C2=A0</div><blockquote class=3D"gmail_quote" style=3D"margi=
n:0px 0px 0px 0.8ex;border-left:1px solid rgb(204,204,204);padding-left:1ex=
">
&gt; &gt; Using P_hash(EMSK, &quot;<a href=3D"mailto:TEAPbindkey@ietf.org" =
target=3D"_blank">TEAPbindkey@ietf.org</a>&quot; | 0x00 | 0x00 | 0x40) look=
s<br>
&gt; &gt; correct, but it looks strange to me if we are trying to include t=
he<br>
&gt; &gt; first 0x00 at the end of the &quot;label&quot; argument to PRF(se=
cret, label,<br>
&gt; &gt; seed) especially when the label is define to be &quot;an ASCII st=
ring. It<br>
&gt; &gt; should be included in the exact form it is given without a length=
 byte<br>
&gt; &gt; or trailing null character&quot;. I would have expected<br>
&gt; &gt; &quot;<a href=3D"mailto:TEAPbindkey@ietf.org" target=3D"_blank">T=
EAPbindkey@ietf.org</a>&quot; to be the &quot;label&quot; while 0x00 | 0x00=
 | 0x40 would<br>
&gt; &gt; be the &quot;seed&quot;. In other words:<br>
&gt; &gt;<br>
&gt; &gt; IMSK =3D First 32 octets of TLS-PRF(EMSK, &quot;<a href=3D"mailto=
:TEAPbindkey@ietf.org" target=3D"_blank">TEAPbindkey@ietf.org</a>&quot;,<br=
>
&gt; &gt;=C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=
=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A00x00 | 0x00 | 0x=
40).<br>
&gt; &gt;<br>
&gt; &gt;<br>
&gt; [Joe] Yes I agree that is better how about this as the text change<br>
&gt; <br>
&gt; IMSK =3D First 32 octets of TLS-PRF(EMSK, &quot;<a href=3D"mailto:TEAP=
bindkey@ietf.org" target=3D"_blank">TEAPbindkey@ietf.org</a>&quot;, &quot;\=
0&quot; |=C2=A0 64)<br>
<br>
It looks quite strange to me to define a binary seed data as a<br>
concatenation of a string and an integer. I have the exact same question<br=
>
about the encoding of 64 here since this does not describe explicitly<br>
this instance of 64 to be the &quot;length&quot; which has the particular e=
ncoding<br>
described in RFC 7170. For me, using 0x00 | 0x00 | 0x40 and deleting<br>
that note about length encoding would be significantly clearer. If that<br>
is not acceptable, I would still replace &quot;\0&quot; with 0x00 in this c=
ontext<br>
since this is not an ASCII string or label anymore, but binary data. And<br=
>
in addition to that, the &quot;64&quot; part would need to be replaced with=
<br>
something like &quot;TLS-PRF output length&quot; and then the &quot;TLS-PRF=
 output<br>
length&quot; could be mentioned to be 64 in this instance and the encoding<=
br>
for that would be 2-octet unsigned integer in network byte order.<br>
<br>
-- <br>
Jouni Malinen=C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0=
 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=
=A0 =C2=A0 =C2=A0 PGP id EFC895FA<br>
</blockquote></div></div>

--000000000000c8e6f605b25b90df--


From nobody Fri Oct 23 14:11:20 2020
Return-Path: <joe@salowey.net>
X-Original-To: emu@ietfa.amsl.com
Delivered-To: emu@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 9ECD63A0836 for <emu@ietfa.amsl.com>; Fri, 23 Oct 2020 14:11:18 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.898
X-Spam-Level: 
X-Spam-Status: No, score=-1.898 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, HTML_MESSAGE=0.001, SPF_HELO_NONE=0.001, SPF_PASS=-0.001, URIBL_BLOCKED=0.001] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (2048-bit key) header.d=salowey-net.20150623.gappssmtp.com
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 fpmtkam1htsm for <emu@ietfa.amsl.com>; Fri, 23 Oct 2020 14:11:16 -0700 (PDT)
Received: from mail-qt1-x834.google.com (mail-qt1-x834.google.com [IPv6:2607:f8b0:4864:20::834]) (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 9F2573A0820 for <emu@ietf.org>; Fri, 23 Oct 2020 14:11:16 -0700 (PDT)
Received: by mail-qt1-x834.google.com with SMTP id r8so2201362qtp.13 for <emu@ietf.org>; Fri, 23 Oct 2020 14:11:16 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=salowey-net.20150623.gappssmtp.com; s=20150623; h=mime-version:references:in-reply-to:from:date:message-id:subject:to :cc; bh=NNPeOJA2JkGgsoZ4dgliV6c+qPqV4hDuYfeyhcnlbO0=; b=EHWKtO6QjYirxsdsanFQFE3WuaONfvPUWNILKsGs7hRQu5zO5zXyZ2So2bdZ/B91y2 /OC40r9cnzV4y+fs9Jb9BO+oZ0F/wjRq2EoyXqJ3oSqpficU/ilmBjHdVKh1T0kAG7ny Q4DsW07GEzmJoiE6fqbPpZV3dLErpF+DOyJV6QdN/5yxCit2nav7D0/ffJDcFkI6RCx5 GI57CozCPGx+mSkA56jL3Ai7Bq0D8ygos5gZg+IB4Np5ZntnSgxnMPLmh0H/g5YZNtT9 3NDY/D0nutZRvzn5kp+r7XWZ0pekCd2pfKv5Be8Svd9eBz+havnha0VABqHBABeItFIO a1+w==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:mime-version:references:in-reply-to:from:date :message-id:subject:to:cc; bh=NNPeOJA2JkGgsoZ4dgliV6c+qPqV4hDuYfeyhcnlbO0=; b=j7JKfaoCOoFA78Z+Cy2k4ZgfaIyAdBRw/9hcpcZY6aOAsDzElve2o+s9a0HASt7nNd icRJQ4VuubBhf0I6sGr34j67AuXNBkL4NktVfeQsBvQnKqyOHUZS1n6X+3D9VVDYDcT7 tz8pMv0r/6KRzHu39TVJPiAjjvEApOBflV361/X5DFWKzkKSPeetwRHRzgOnpmqawm3Y pWB4JY0TK2Sf57Ds89Nleujdbj0KwaXnmPma2RZ0UVcCuhL52IhRUl5BKBG1XezNCTh3 6qwSR7KpUwsxHA7s+buM64HtGoBMcDjQEYpUVMDm8TBsSjaeOGOiI9sId6O428ndvvgO VGXw==
X-Gm-Message-State: AOAM533mJqKEiM6ZiQiexIKEg1PX+vIMy/+IoIQfF64W5i0zE1ikB1vQ qjGujpg56ZwbHGjK5kjtSTB5XdjpWpBbLCrOzSc9kQ==
X-Google-Smtp-Source: ABdhPJwVtlFyzLMWbEe+f8FWDx2BUcEx3b9KProl8yWLgThcfu0oofO/xaI+j44+uFzV0Bva9h713WTiXG+I3z5GVpg=
X-Received: by 2002:ac8:b4a:: with SMTP id m10mr4149805qti.71.1603487475559; Fri, 23 Oct 2020 14:11:15 -0700 (PDT)
MIME-Version: 1.0
References: <CH2PR21MB138143E929DAFE3C893D8144D11C0@CH2PR21MB1381.namprd21.prod.outlook.com> <CAOgPGoAtcm+Br+YkCyTtg5nJjqO7LGSo77b+CD4+Ba05azafew@mail.gmail.com> <CH2PR21MB13815BCEDC846D7C440AD564D11C0@CH2PR21MB1381.namprd21.prod.outlook.com> <CAOgPGoDTC-qiHOXFTJd7aMn2To7ySzBcx+iQMB9m5foC1bFxzw@mail.gmail.com> <CABXxEz8SRvMXdMR8_cPfvWdauJZwCjnd=7ytnVZ+_L-sB48wvw@mail.gmail.com> <CAOgPGoCsWy-uhYeeHCDUaazjAwfWtr_zkS5CUoX8+baASahFEg@mail.gmail.com> <CABXxEz9euWaA9Y66+1u4gtFCWkrPUEd-juY_TFUHPQE4R_OpRg@mail.gmail.com> <CAOgPGoDcD7wjiMt2=t0vx2FPr2LD2S3eU1d0_bVU1c88S=tA=w@mail.gmail.com> <CH2PR21MB13810C16054DD1DDB4055659D11D0@CH2PR21MB1381.namprd21.prod.outlook.com> <CABXxEz8JP07gLB2Tknx1ahErZ=ydVVq2XORLadDatBcSjVu3-Q@mail.gmail.com> <20201023165549.GC15442@w1.fi>
In-Reply-To: <20201023165549.GC15442@w1.fi>
From: Joseph Salowey <joe@salowey.net>
Date: Fri, 23 Oct 2020 14:11:04 -0700
Message-ID: <CAOgPGoCvwTQFq6c5MqxqV1uYXznRmFYLixpeeTCP6_5Eg2Vy9Q@mail.gmail.com>
To: Jouni Malinen <j@w1.fi>
Cc: Oleg Pekar <oleg.pekar.2017@gmail.com>, Jorge Vergara <jovergar@microsoft.com>, EMU WG <emu@ietf.org>
Content-Type: multipart/alternative; boundary="00000000000062036805b25d05b0"
Archived-At: <https://mailarchive.ietf.org/arch/msg/emu/mr4whjo9ECriteOZ0cnCDck0rpg>
Subject: Re: [Emu] Proposed resolution for TEAP errata for 5128
X-BeenThere: emu@ietf.org
X-Mailman-Version: 2.1.29
Precedence: list
List-Id: "EAP Methods Update \(EMU\)" <emu.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/emu>, <mailto:emu-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/emu/>
List-Post: <mailto:emu@ietf.org>
List-Help: <mailto:emu-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/emu>, <mailto:emu-request@ietf.org?subject=subscribe>
X-List-Received-Date: Fri, 23 Oct 2020 21:11:19 -0000

--00000000000062036805b25d05b0
Content-Type: text/plain; charset="UTF-8"

I think we have agreement on what the derivation would be now it's a matter
of clearly describing it. Here is a proposal:
IMCK[j] = the first 60 bytes of TLS-PRF(S-IMCK[j-1], "Inner Methods
Compound Keys", IMSK[j])

      where "|" denotes concatenation and the TLS-PRF is defined in
      [RFC5246] as

        PRF(secret, label, seed) = P_<hash>(secret, label | seed).

     the secret is S-IMCK[j-1],  the label is
     "Inner Methods Compound Keys" consisting of the ASCII value for the
     label "Inner Methods Compound Keys" (without quotes),  the seed
     consists IMSK[j].

MSK = the first 64 bytes of TLS-PRF(S-IMCK[j], "Session Key Generating
Function")
EMSK = the first 64 bytes of TLS-PRF(S-IMCK[j], "Extended Session Key
Generating Function")

      where "|" denotes concatenation and the TLS-PRF is defined in
      [RFC5246] as

        PRF(secret, label, seed) = P_<hash>(secret, label | seed).

     The secret is S-IMCK[j-1]  where j is the number of the last
successfully
     executed inner EAP method.  The label is is the ASCII value for the
     string without quotes.  The seed is empty (0 length) and omitted from
     the derivation.

On Fri, Oct 23, 2020 at 9:58 AM Jouni Malinen <j@w1.fi> wrote:

> There were so many messages in this thread that I'm not going try to
> address each point separately, but I think in general I do agree with
> the comments and it looks like all the identified implementation are
> doing the same thing here..
>
> I don't see any strong need to encode the output length of the PRF into
> the input data especially since we are using hardcoded output lengths in
> these cases. That said, I'm not against keeping it there for the IMSK
> derivation since that particular case seemed to be explicitly defined as
> using a 2-octet field in network byte order (and all the known
> implementations doing exactly that). IMHO, the other cases should not be
> modified to try to be consistent with this.
>
> While I do understand the benefits of having an explicit fixed delimiter
> "\0" between the label and seed to enforce unique interpretation if two
> labels were to have same prefix, I don't see that as a critical issue in
> any of the instances used within TEAP due to no such common prefix case
> exist nor do we even use TLS-PRF with the same secret/key. Furthermore,
> RFC 5246 does not mandate or even discuss such delimiter.
>
> There is no need to convert an empty seed to 0x00 or anything else.
> TLS-PRF can be used with secret=something, label=ASCII string,
> seed=0-length data) without issues.
>
> If we want to define a new TEAP-PRF() function, I'd prefer it to be
> using consistent terminology with TLS-PRF in RFC 5246 (and well, to
> extend possible, also be as consistent as can be with the TLS-Exporter
> use in RFC 8446). This would also mean not trying to enforce some 0x00
> delimiter or length in context data. At its simplest and only with TLS
> v1.2 in mind for clarity here, this could look something like
>
> TEAP-PRF(secret, label, seed, output length) =
> PRF(secret, label, seed) outputting "output length" octets
>
> label = ASCII string, no "\x0" termination
> seed = arbitrary binary data (including possibility of 0-length empty
> case)
>
> With this, we would have following:
> IMSK = First 32 octets of TEAP-PRF(EMSK, "TEAPbindkey@ietf.org", 0x00 |
> 0x00 | 0x40, 64)
> IMCK[j] = TEAP-PRF(S-IMCK[j-1], "Inner Methods Compound Keys", IMSK[j], 60)
> MSK = TEAP-PRF(S-IMCK[j], "Session Key Generating Function", <empty>, 64)
> EMSK = TEAP-PRF(S-IMCK[j], "Extended Session Key Generating Function",
> <empty>, 64)
>
> RFC 5295 rules about EMSK use for USRK/DSRK applies for the first one of
> these and it does seem to give justification for the seed to have "\0"
> and "length" (as 2-octet unsigned integer in network byte order). While
> one could claim that the rules for DSUSRK derivation applies to those
> other instances and as such, would require 0x00 and length to be added
> around the seed shown above, I'd note that there does not seem to be any
> MUST statement about that in RFC 5295 and as such, I think the versions
> described above (and the ones used in known implementations today) seem
> to be justifiable especially taken into account the unique label string
> prefixes and fixed length of output data.
>
> --
> Jouni Malinen                                            PGP id EFC895FA
>

--00000000000062036805b25d05b0
Content-Type: text/html; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable

<div dir=3D"ltr">I think we have agreement on what the derivation would be =
now it&#39;s a matter of clearly describing it. Here is a proposal:<div cla=
ss=3D"gmail-" style=3D"font-family:Roboto,RobotoDraft,Helvetica,Arial,sans-=
serif;font-size:medium"><div id=3D"gmail-:35z" class=3D"gmail-ii gmail-gt g=
mail-adO" style=3D"font-size:0.875rem;direction:ltr;margin:8px 0px 0px;padd=
ing:0px"><div id=3D"gmail-:2u9" class=3D"gmail-a3s gmail-aiL" style=3D"over=
flow:hidden;font-variant-numeric:normal;font-variant-east-asian:normal;font=
-stretch:normal;font-size:small;line-height:1.5;font-family:Arial,Helvetica=
,sans-serif"><div dir=3D"ltr"><div dir=3D"ltr">IMCK[j] =3D the first 60 byt=
es of TLS-PRF(S-IMCK[j-1], &quot;Inner Methods Compound Keys&quot;, IMSK[j]=
)<div><br></div><div><div class=3D"gmail_quote">=C2=A0 =C2=A0 =C2=A0 where =
&quot;|&quot; denotes concatenation and the TLS-PRF is defined in</div><div=
 class=3D"gmail_quote">=C2=A0 =C2=A0 =C2=A0 [RFC5246] as=C2=A0</div><div cl=
ass=3D"gmail_quote">=C2=A0 =C2=A0 =C2=A0</div><div class=3D"gmail_quote">=
=C2=A0 =C2=A0 =C2=A0 =C2=A0 PRF(secret, label, seed) =3D P_&lt;hash&gt;(sec=
ret, label | seed).<br></div><div class=3D"gmail_quote"><br></div><div clas=
s=3D"gmail_quote">=C2=A0 =C2=A0 =C2=A0the secret is S-IMCK[j-1],=C2=A0 the =
label is=C2=A0</div><div class=3D"gmail_quote">=C2=A0 =C2=A0 =C2=A0&quot;In=
ner Methods Compound Keys&quot; consisting of the ASCII value for the<br>=
=C2=A0 =C2=A0 =C2=A0label &quot;Inner Methods Compound Keys&quot;=C2=A0(wit=
hout quotes),=C2=A0 the seed=C2=A0</div><div class=3D"gmail_quote">=C2=A0 =
=C2=A0 =C2=A0consists IMSK[j].=C2=A0</div><div style=3D"outline:none;paddin=
g:10px 0px;width:22px;margin:2px 0px 0px"><br></div>MSK =3D the first 64 by=
tes of TLS-PRF(S-IMCK[j], &quot;Session Key Generating Function&quot;)=C2=
=A0</div><div>EMSK =3D the first 64 bytes of TLS-PRF(S-IMCK[j], &quot;Exten=
ded Session Key Generating Function&quot;)</div><div><br></div><div><div cl=
ass=3D"gmail_quote">=C2=A0 =C2=A0 =C2=A0 where &quot;|&quot; denotes concat=
enation and the TLS-PRF is defined in</div><div class=3D"gmail_quote">=C2=
=A0 =C2=A0 =C2=A0 [RFC5246] as=C2=A0</div><div class=3D"gmail_quote">=C2=A0=
 =C2=A0 =C2=A0</div><div class=3D"gmail_quote">=C2=A0 =C2=A0 =C2=A0 =C2=A0 =
PRF(secret, label, seed) =3D P_&lt;hash&gt;(secret, label | seed).<br></div=
><div class=3D"gmail_quote"><br></div><div class=3D"gmail_quote">=C2=A0 =C2=
=A0 =C2=A0The secret is S-IMCK[j-1]=C2=A0=C2=A0where j is the number of the=
 last successfully=C2=A0</div><div class=3D"gmail_quote">=C2=A0 =C2=A0 =C2=
=A0executed inner EAP method.=C2=A0 The label is is the ASCII value for the=
</div>=C2=A0 =C2=A0 =C2=A0string without quotes.=C2=A0 The seed is empty (0=
 length) and omitted from=C2=A0</div><div>=C2=A0 =C2=A0 =C2=A0the derivatio=
n.</div></div></div></div></div></div></div><br><div class=3D"gmail_quote">=
<div dir=3D"ltr" class=3D"gmail_attr">On Fri, Oct 23, 2020 at 9:58 AM Jouni=
 Malinen &lt;<a href=3D"mailto:j@w1.fi">j@w1.fi</a>&gt; wrote:<br></div><bl=
ockquote class=3D"gmail_quote" style=3D"margin:0px 0px 0px 0.8ex;border-lef=
t:1px solid rgb(204,204,204);padding-left:1ex">There were so many messages =
in this thread that I&#39;m not going try to<br>
address each point separately, but I think in general I do agree with<br>
the comments and it looks like all the identified implementation are<br>
doing the same thing here..<br>
<br>
I don&#39;t see any strong need to encode the output length of the PRF into=
<br>
the input data especially since we are using hardcoded output lengths in<br=
>
these cases. That said, I&#39;m not against keeping it there for the IMSK<b=
r>
derivation since that particular case seemed to be explicitly defined as<br=
>
using a 2-octet field in network byte order (and all the known<br>
implementations doing exactly that). IMHO, the other cases should not be<br=
>
modified to try to be consistent with this.<br>
<br>
While I do understand the benefits of having an explicit fixed delimiter<br=
>
&quot;\0&quot; between the label and seed to enforce unique interpretation =
if two<br>
labels were to have same prefix, I don&#39;t see that as a critical issue i=
n<br>
any of the instances used within TEAP due to no such common prefix case<br>
exist nor do we even use TLS-PRF with the same secret/key. Furthermore,<br>
RFC 5246 does not mandate or even discuss such delimiter.<br>
<br>
There is no need to convert an empty seed to 0x00 or anything else.<br>
TLS-PRF can be used with secret=3Dsomething, label=3DASCII string,<br>
seed=3D0-length data) without issues.<br>
<br>
If we want to define a new TEAP-PRF() function, I&#39;d prefer it to be<br>
using consistent terminology with TLS-PRF in RFC 5246 (and well, to<br>
extend possible, also be as consistent as can be with the TLS-Exporter<br>
use in RFC 8446). This would also mean not trying to enforce some 0x00<br>
delimiter or length in context data. At its simplest and only with TLS<br>
v1.2 in mind for clarity here, this could look something like<br>
<br>
TEAP-PRF(secret, label, seed, output length) =3D<br>
PRF(secret, label, seed) outputting &quot;output length&quot; octets<br>
<br>
label =3D ASCII string, no &quot;\x0&quot; termination<br>
seed =3D arbitrary binary data (including possibility of 0-length empty<br>
case)<br>
<br>
With this, we would have following:<br>
IMSK =3D First 32 octets of TEAP-PRF(EMSK, &quot;<a href=3D"mailto:TEAPbind=
key@ietf.org" target=3D"_blank">TEAPbindkey@ietf.org</a>&quot;, 0x00 |<br>
0x00 | 0x40, 64)<br>
IMCK[j] =3D TEAP-PRF(S-IMCK[j-1], &quot;Inner Methods Compound Keys&quot;, =
IMSK[j], 60)<br>
MSK =3D TEAP-PRF(S-IMCK[j], &quot;Session Key Generating Function&quot;, &l=
t;empty&gt;, 64)<br>
EMSK =3D TEAP-PRF(S-IMCK[j], &quot;Extended Session Key Generating Function=
&quot;,<br>
&lt;empty&gt;, 64)<br>
<br>
RFC 5295 rules about EMSK use for USRK/DSRK applies for the first one of<br=
>
these and it does seem to give justification for the seed to have &quot;\0&=
quot;<br>
and &quot;length&quot; (as 2-octet unsigned integer in network byte order).=
 While<br>
one could claim that the rules for DSUSRK derivation applies to those<br>
other instances and as such, would require 0x00 and length to be added<br>
around the seed shown above, I&#39;d note that there does not seem to be an=
y<br>
MUST statement about that in RFC 5295 and as such, I think the versions<br>
described above (and the ones used in known implementations today) seem<br>
to be justifiable especially taken into account the unique label string<br>
prefixes and fixed length of output data.<br>
<br>
-- <br>
Jouni Malinen=C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0=
 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=
=A0 =C2=A0 =C2=A0 PGP id EFC895FA<br>
</blockquote></div>

--00000000000062036805b25d05b0--


From nobody Fri Oct 23 14:17:49 2020
Return-Path: <agenda@ietf.org>
X-Original-To: emu@ietf.org
Delivered-To: emu@ietfa.amsl.com
Received: from ietfa.amsl.com (localhost [IPv6:::1]) by ietfa.amsl.com (Postfix) with ESMTP id 5D5983A10D9; Fri, 23 Oct 2020 14:15:48 -0700 (PDT)
MIME-Version: 1.0
Content-Type: text/plain; charset="utf-8"
Content-Transfer-Encoding: 7bit
From: "\"IETF Secretariat\"" <agenda@ietf.org>
To: <mohit.m.sethi@ericsson.com>, <emu-chairs@ietf.org>
Cc: rdd@cert.org, emu@ietf.org
X-Test-IDTracker: no
X-IETF-IDTracker: 7.20.0
Auto-Submitted: auto-generated
Precedence: bulk
Message-ID: <160348774837.5087.164640084438474554@ietfa.amsl.com>
Date: Fri, 23 Oct 2020 14:15:48 -0700
Archived-At: <https://mailarchive.ietf.org/arch/msg/emu/8URZftOlu7XcdrO7FznD8KIKvKo>
Subject: [Emu] emu - Requested session has been scheduled for IETF 109
X-BeenThere: emu@ietf.org
X-Mailman-Version: 2.1.29
List-Id: "EAP Methods Update \(EMU\)" <emu.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/emu>, <mailto:emu-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/emu/>
List-Post: <mailto:emu@ietf.org>
List-Help: <mailto:emu-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/emu>, <mailto:emu-request@ietf.org?subject=subscribe>
X-List-Received-Date: Fri, 23 Oct 2020 21:15:52 -0000

Dear Mohit Sethi,

The session(s) that you have requested have been scheduled.
Below is the scheduled session information followed by
the original request. 


    emu Session 1 (2:00 requested)
    Friday, 20 November 2020, Session I 1200-1400
    Room Name: Room 7 size: 507
    ---------------------------------------------


iCalendar: https://datatracker.ietf.org/meeting/109/sessions/emu.ics

Request Information:


---------------------------------------------------------
Working Group Name: EAP Method Update
Area Name: Security Area
Session Requester: Mohit Sethi


Number of Sessions: 1
Length of Session(s):  2 Hours
Number of Attendees: 50
Conflicts to Avoid: 
 Chair Conflict: saag tls cfrg lwig privacypass
 Technology Overlap: curdle uta secdispatch oauth mls t2trg pearg lake
 Key Participant Conflict: sacm quic kitten bier acme 6lo





People who must be present:
  Jari Arkko
  Joseph A. Salowey
  Roman Danyliw
  Alan DeKok
  John Preuss Mattsson
  Mohit Sethi

Resources Requested:

Special Requests:
  
---------------------------------------------------------



From nobody Fri Oct 23 15:38:04 2020
Return-Path: <wwwrun@rfc-editor.org>
X-Original-To: emu@ietfa.amsl.com
Delivered-To: emu@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 4C7393A09F7; Fri, 23 Oct 2020 15:38:03 -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, SPF_PASS=-0.001, URIBL_BLOCKED=0.001] autolearn=ham autolearn_force=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 VThZHDJKbOSi; Fri, 23 Oct 2020 15:38:02 -0700 (PDT)
Received: from rfc-editor.org (rfc-editor.org [4.31.198.49]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 0D2BC3A09F6; Fri, 23 Oct 2020 15:38:02 -0700 (PDT)
Received: by rfc-editor.org (Postfix, from userid 30) id E0F33F40737; Fri, 23 Oct 2020 15:37:54 -0700 (PDT)
To: ietf-announce@ietf.org, rfc-dist@rfc-editor.org
X-PHP-Originating-Script: 1005:ams_util_lib.php
From: rfc-editor@rfc-editor.org
Cc: rfc-editor@rfc-editor.org, drafts-update-ref@iana.org, emu@ietf.org
Content-type: text/plain; charset=UTF-8
Message-Id: <20201023223754.E0F33F40737@rfc-editor.org>
Date: Fri, 23 Oct 2020 15:37:54 -0700 (PDT)
Archived-At: <https://mailarchive.ietf.org/arch/msg/emu/OLelL_7p_4xYIBZACFySLKq854M>
Subject: [Emu] =?utf-8?q?RFC_8940_on_Extensible_Authentication_Protocol_?= =?utf-8?q?=28EAP=29_Session-Id_Derivation_for_EAP_Subscriber_Identity_Mod?= =?utf-8?q?ule_=28EAP-SIM=29=2C_EAP_Authentication_and_Key_Agreement_=28EA?= =?utf-8?q?P-AKA=29=2C_and_Protected_EAP_=28PEAP=29?=
X-BeenThere: emu@ietf.org
X-Mailman-Version: 2.1.29
Precedence: list
List-Id: "EAP Methods Update \(EMU\)" <emu.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/emu>, <mailto:emu-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/emu/>
List-Post: <mailto:emu@ietf.org>
List-Help: <mailto:emu-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/emu>, <mailto:emu-request@ietf.org?subject=subscribe>
X-List-Received-Date: Fri, 23 Oct 2020 22:38:03 -0000

A new Request for Comments is now available in online RFC libraries.

        
        RFC 8940

        Title:      Extensible Authentication Protocol (EAP) Session-Id 
                    Derivation for EAP Subscriber Identity Module 
                    (EAP-SIM), EAP Authentication and Key Agreement 
                    (EAP-AKA), and Protected EAP (PEAP) 
        Author:     A. DeKok
        Status:     Standards Track
        Stream:     IETF
        Date:       October 2020
        Mailbox:    aland@freeradius.org
        Pages:      7
        Updates:    RFC 5247

        I-D Tag:    draft-ietf-emu-eap-session-id-07.txt

        URL:        https://www.rfc-editor.org/info/rfc8940

        DOI:        10.17487/RFC8940

RFC 5247 is updated to define and clarify EAP Session-Id derivation
for multiple Extensible Authentication Protocol (EAP) methods.  The
derivation of Session-Id was not given for EAP Subscriber Identity
Module (EAP-SIM) or EAP Authentication and Key Agreement (EAP-AKA)
when using the fast reconnect exchange instead of full
authentication.  The derivation of Session-Id for full authentication
is clarified for both EAP-SIM and EAP-AKA.  The derivation of
Session-Id for Protected EAP (PEAP) is also given.  The definition
for PEAP follows the definition for other TLS-based EAP methods.

This document is a product of the EAP Method Update Working Group of the IETF.

This is now a Proposed Standard.

STANDARDS TRACK: This document specifies an Internet Standards Track
protocol for the Internet community, and requests discussion and suggestions
for improvements.  Please refer to the current edition of the Official
Internet Protocol Standards (https://www.rfc-editor.org/standards) for the 
standardization state and status of this protocol.  Distribution of this 
memo is unlimited.

This announcement is sent to the IETF-Announce and rfc-dist lists.
To subscribe or unsubscribe, see
  https://www.ietf.org/mailman/listinfo/ietf-announce
  https://mailman.rfc-editor.org/mailman/listinfo/rfc-dist

For searching the RFC series, see https://www.rfc-editor.org/search
For downloading RFCs, see https://www.rfc-editor.org/retrieve/bulk

Requests for special distribution should be addressed to either the
author of the RFC in question, or to rfc-editor@rfc-editor.org.  Unless
specifically noted otherwise on the RFC itself, all RFCs are for
unlimited distribution.


The RFC Editor Team
Association Management Solutions, LLC



From nobody Sat Oct 24 03:44:20 2020
Return-Path: <noreply@ietf.org>
X-Original-To: emu@ietf.org
Delivered-To: emu@ietfa.amsl.com
Received: from ietfa.amsl.com (localhost [IPv6:::1]) by ietfa.amsl.com (Postfix) with ESMTP id 35B623A0953; Sat, 24 Oct 2020 03:44:18 -0700 (PDT)
MIME-Version: 1.0
Content-Type: text/plain; charset="utf-8"
Content-Transfer-Encoding: 8bit
From: Elwyn Davies via Datatracker <noreply@ietf.org>
To: <gen-art@ietf.org>
Cc: last-call@ietf.org, emu@ietf.org, draft-ietf-emu-eaptlscert.all@ietf.org
X-Test-IDTracker: no
X-IETF-IDTracker: 7.20.0
Auto-Submitted: auto-generated
Precedence: bulk
Message-ID: <160353625817.30765.14852413837090655602@ietfa.amsl.com>
Reply-To: Elwyn Davies <elwynd@dial.pipex.com>
Date: Sat, 24 Oct 2020 03:44:18 -0700
Archived-At: <https://mailarchive.ietf.org/arch/msg/emu/8LCXxC9y2rlmBebl0IyfWs6Jlys>
Subject: [Emu] Genart last call review of draft-ietf-emu-eaptlscert-05
X-BeenThere: emu@ietf.org
X-Mailman-Version: 2.1.29
List-Id: "EAP Methods Update \(EMU\)" <emu.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/emu>, <mailto:emu-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/emu/>
List-Post: <mailto:emu@ietf.org>
List-Help: <mailto:emu-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/emu>, <mailto:emu-request@ietf.org?subject=subscribe>
X-List-Received-Date: Sat, 24 Oct 2020 10:44:18 -0000

Reviewer: Elwyn Davies
Review result: Ready with Nits

I am the assigned Gen-ART reviewer for this draft. The General Area
Review Team (Gen-ART) reviews all IETF documents being processed
by the IESG for the IETF Chair.  Please treat these comments just
like any other last call comments.

For more information, please see the FAQ at

<https://trac.ietf.org/trac/gen/wiki/GenArtfaq>.

Document: draft-ietf-emu-eaptlscert-05
Reviewer: Elwyn Davies
Review Date: 2020-10-24
IETF LC End Date: 2020-10-28
IESG Telechat date: Not scheduled for a telechat

Summary:  Ready with nits.  There are quite a number of references to
associated work that is still in progress as drafts.  Whilst this is unlikely
to compromise the content of this work, it will potentially delay its
publication.  In particular I have suggested rewriting s4.2.7 to omit more
speculative references to incomplete work in favour of a general recommendation
to make use of relevant new proposals as they become available.

Major Issues:
None

Minor Issues:
None

Nits and Editoral Issues:

General:Â  RFC 2119 key words:Â  In the document there are two MUSTs and a SHOULD
NOT none of which are appropriate usages in my opinion (see notes below), aside
from theÂ  intended infromational status.Â  The RFC 2119 etc boilerplate in s2
could be omitted.

Abstract:Â  Need to expand EAP-TLS and EAP on first occurrence.

s1, end of para 2:Â  Suggest s/involves significantly more octets/involves
exchange of significantly more octets/

s2, definition of EAP server:Â  Where would a reader find a definition of
"backend authentication"?Â  Uncle Google was singularly unhelpful.

s3, last para:Â  clarify the meaning of kB:Â  suggest s/~ 60kB/approximately 60
kbytes/ (I assume).

s4:Â  The usage of the form " we look/discuss/etc." typicallyÂ  used in academic
papers is not appropriate for standards documents.Â  Section 4 needs to be
redrafted to eliminate this usage.Â  The following may be appropriate:

OLD:
This section discusses some possible alternatives for overcoming the challenge
of large certificates and long certificate chains in EAP- TLS authentication.
In Section 4.1 we look at recommendations that require an update of the
certificates or certificate chains that are used for EAP-TLS authentication
without requiring changes to the existing EAP-TLS code base. We also provide
some guidelines when issuing certificates for use with EAP-TLS. In Section 4.2
we look at recommendations that rely on updates to the EAP-TLS implementations
which can be deployed with existing certificates. In Section 4.3 we shortly
discuss the solution to update or reconfigure authenticator which can be
deployed without changes to existing certificates or EAP-TLS code.

NEW:
This section discusses some possible alternatives for overcoming the challenge
of large certificates and long certificate chains in EAP- TLS authentication.
Section 4.1 considers recommendations that require an update of the
certificates or certificate chains that are used for EAP-TLS authentication
without requiring changes to the existing EAP-TLS code base. The section also
provides some guidelines that ahould be followed when issuing certificates for
use with EAP-TLS. Section 4.2 considers recommendations that rely on updates to
the EAP-TLS implementations which can be deployed with existing certificates.
Finally Section 4.3 briefly discusses what could be done to update or
reconfigure authenticators where it is infeasible to replace deployed
components giving a solution can be deployed without changes to existing
certificates or EAP-TLS code. ENDS

s4.1.1, para 1: s/is as follows/are as follows/

s4.1.1, para 2 (1st bullet): s/Object Identifiers (OIDs) is ASN.1/The Object
Identifier (OID) is an ASN.1/

s4.1.1, para 3 (1st bullet): Need to expand DER. Also useful to add reference
to RFC5280 after X.509.

s4.1.1, para 4 (1st sub-bullet n 1st bullet) 'vs' needs to be expanded - either
'versus' or (Better) 'as against'.

s4.1.3, para 1: The use of capitalized SHOULD NOT here is, I think,
inappropriate. This is an operational recommendation rather than a protocol
requirement, so s/SHOULD NOT/should not/.

s4.2.2, para 1: s/useful when, for example, when/useful when, for example,/

s4.2.4: s/can define dictionary of/can define a dictionary of/

s4.2.5: s/For a client that has all intermediates,/For a client that has all
intermediate certificates in the certificate chain/

s4.2.5: The second sentence of this section needs to be rewritten as if
draft-thomson-tls-sic is already an RFC.

s4.2.7: This section is not 'future proof'. It should be rewritten omitting the
explicit examples but exhorting implementors and operatirs to consider relevant
future developments.

s4.3, para 1: The second and third sentences don't read well.Suggest:
OLD:
Another second reason is that unlimited communication from an unauthenticated
device as EAP could otherwise be use for bulk data transfer. A third reason is
to prevent denial-of-service attacks. NEW: Other reasons include that unlimited
communication from an unauthenticated device using EAP could provide a channel
for inappropriate bulk data transfer, and that communication could facilitate
denial-of-service attacks. ENDS

s6, para 2: The MUSTs look as if they are imposing requirements on
draft-ietf-tls-certificate-compression. I am sure that the draft would be
effectively saying these things anyway (if not, why not?) Also the first
sentence appears to be truncated - it doesn't make any sense as it stands. I
suggest rewriting the paragraph with the third sentence first, and, if really
necessary, adding the two points from the first sentences as reminders rather
than MUSTs.




From nobody Sat Oct 24 14:45:47 2020
Return-Path: <joe@salowey.net>
X-Original-To: emu@ietfa.amsl.com
Delivered-To: emu@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id D80E13A045E for <emu@ietfa.amsl.com>; Sat, 24 Oct 2020 14:45:45 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.898
X-Spam-Level: 
X-Spam-Status: No, score=-1.898 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, HTML_MESSAGE=0.001, SPF_HELO_NONE=0.001, SPF_PASS=-0.001, URIBL_BLOCKED=0.001] autolearn=unavailable autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (2048-bit key) header.d=salowey-net.20150623.gappssmtp.com
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 lsluG0oM39-D for <emu@ietfa.amsl.com>; Sat, 24 Oct 2020 14:45:44 -0700 (PDT)
Received: from mail-qt1-x82a.google.com (mail-qt1-x82a.google.com [IPv6:2607:f8b0:4864:20::82a]) (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 D43D83A07C4 for <emu@ietf.org>; Sat, 24 Oct 2020 14:45:43 -0700 (PDT)
Received: by mail-qt1-x82a.google.com with SMTP id i7so3395682qti.6 for <emu@ietf.org>; Sat, 24 Oct 2020 14:45:43 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=salowey-net.20150623.gappssmtp.com; s=20150623; h=mime-version:from:date:message-id:subject:to:cc; bh=fDmX92GZ5Y7IzPYpehSN7oWmv30rF0xyrYJNghbXRDY=; b=htwEpGGzzQMhmD7BBl2EPIep0X0Z7unwL5LRyjqAFlf62StOw8r57KW9Xw12M9+jKE S3enrhVESRx8wpxGcvSV4HHsOniwvvF54f89/F6Q3LuSrTUNDGI+R/qdAw7hWEoRtOOD gjMWLr2ZlvnRqYr+LGmaIJVzPdUg4GFCe3GSmK3Hhyu6EQrcq/AOOwub0IOwF2NZnOLP OAXprdI7lFpuyFGmVuptVHDCAZof/kQbxQHtopbltMsLtEjxKj3shDMw392ejiIqfUcw pXkjy6EVYHzUN7BgwORKvy3ErDm2eOFIywEYbPTusdS5JfuHG2Ymhjed6rIQKQTbnBws JGLw==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:mime-version:from:date:message-id:subject:to:cc; bh=fDmX92GZ5Y7IzPYpehSN7oWmv30rF0xyrYJNghbXRDY=; b=aRcBEjh6ZgrDD1x29Jxlumn+SA2933uLozqD5bOveN0WE/5EqVva4GQuSkDww2kSNc zXoyebd3imb7/Yqc+YWWRrKE6ZHGZRxHkV48xV+kaXaTuut2GOUtqdWVRKhqPCSvfN8W GMMilGWwumrvIdAAAjXBQYc/OneuNDasyI3Ll0YgBATjLeJ3DeOghpUO93IAPYklkwCl RDi3P7hdL/2iGN8nnW9AEkhe/lcrCpH4nxz6zuSEHsGCrfXHuJtKEMcsXJ6SqjIiP6tT 9sboNb/cPagDiWkTnCelNyDVdzng+Cc7+9NQsYTTYrZVI5uyNFjtxtTYUygEQ1nZuOPo Kyvw==
X-Gm-Message-State: AOAM5302WRRepyz/xY79vyFjWU55W0bGGv6LpA2V0YQPZxtbcL4bqlm3 mgUgOjLOPP1ntCVQ4cXV6sFrXgNqbHRdCz+Ii6Tt0Yiz6vCtNg==
X-Google-Smtp-Source: ABdhPJxPHFeot+exsIroCqdB43/vmpdDtw9igbCLftLHnef1+iikpZBqATBIvhWlUbT2iEG38Cu2nyOAm4VBtWx/bgI=
X-Received: by 2002:ac8:7559:: with SMTP id b25mr9588677qtr.38.1603575942477;  Sat, 24 Oct 2020 14:45:42 -0700 (PDT)
MIME-Version: 1.0
From: Joseph Salowey <joe@salowey.net>
Date: Sat, 24 Oct 2020 14:45:31 -0700
Message-ID: <CAOgPGoBonHYt_0ZVutnMk-ijVHFqk+_xNKhchkiHzhvzYkNf-Q@mail.gmail.com>
To: EMU WG <emu@ietf.org>
Cc: Oleg Pekar <oleg.pekar.2017@gmail.com>, Jouni Malinen <j@w1.fi>,  Jorge Vergara <jovergar=40microsoft.com@dmarc.ietf.org>
Content-Type: multipart/alternative; boundary="0000000000006c0f6f05b2719e56"
Archived-At: <https://mailarchive.ietf.org/arch/msg/emu/HzbK29U4W_Q0ntM-Am1kAaa2G9c>
Subject: [Emu] Proposed Resolution for TEAP errata 5768
X-BeenThere: emu@ietf.org
X-Mailman-Version: 2.1.29
Precedence: list
List-Id: "EAP Methods Update \(EMU\)" <emu.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/emu>, <mailto:emu-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/emu/>
List-Post: <mailto:emu@ietf.org>
List-Help: <mailto:emu-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/emu>, <mailto:emu-request@ietf.org?subject=subscribe>
X-List-Received-Date: Sat, 24 Oct 2020 21:45:46 -0000

--0000000000006c0f6f05b2719e56
Content-Type: text/plain; charset="UTF-8"

Errata 5768:  https://www.rfc-editor.org/errata/eid5768
Proposed State: Verified
Revision:

Section 4.2.13. Says:

Length

    76

It should say:

Length

     36 plus the length of the 2 MAC fields

Section 4.2.13. Says:

   EMSK Compound MAC

      The EMSK Compound MAC field is 20 octets.  This can be the Server
      MAC (B1_MAC) or the Client MAC (B2_MAC).  The computation of the
      MAC is described in Section 5.3.

   MSK Compound MAC

      The MSK Compound MAC field is 20 octets.  This can be the Server
      MAC (B1_MAC) or the Client MAC (B2_MAC).  The computation of the
      MAC is described in Section 5.3.

It Should Say:

   EMSK Compound MAC

      The computation of the MAC is described in Section 5.3.  This can be
      the Server MAC (B1_MAC) or the Client MAC (B2_MAC).

   MSK Compound MAC

      The computation of the MAC is described in Section 5.3.  This can be
      the Server MAC (B1_MAC) or the Client MAC (B2_MAC).

Section 5.3 Says:

 The Compound MAC computation is as follows:

      CMK = CMK[j]
      Compound-MAC = MAC( CMK, BUFFER )

   where j is the number of the last successfully executed inner EAP
   method, MAC is the MAC function negotiated in TLS 1.2 [RFC5246], and
   BUFFER is created after concatenating these fields in the following
   order:

   1  The entire Crypto-Binding TLV attribute with both the EMSK and MSK
      Compound MAC fields zeroed out.

   2  The EAP Type sent by the other party in the first TEAP message.

It Should say:

 The Compound MAC computation is as follows:

      CMK = CMK[j]
      Compound-MAC = MAC( CMK, BUFFER )

   where j is the number of the last successfully executed inner EAP
   method, MAC is HMAC [RFC2104] using the hash function negotiated in
   TLS [RFC5246].  The output length is the length of the output of the HMAC
   function.  The BUFFER is created after concatenating these fields in
   the following order:

   1  The entire Crypto-Binding TLV attribute with both the EMSK and MSK
      Compound MAC fields zeroed out.

   2  The EAP Type sent by the other party in the first TEAP message. This
       is a single octet encoded as (0x37)

Notes:

This corrects the problem that the MAC output will vary depending upon the
TLS hash function. It clarifies that HMAC is used with the hash function
negotiated in TLS.   It also clarifies that the  EAP Type used in the TLS
message is the TEAP EAP type encoded as a single byte.

--0000000000006c0f6f05b2719e56
Content-Type: text/html; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable

<div dir=3D"ltr">Errata 5768:=C2=A0=C2=A0<a href=3D"https://www.rfc-editor.=
org/errata/eid5768">https://www.rfc-editor.org/errata/eid5768</a><div>Propo=
sed State: Verified</div><div>Revision:</div><div><br></div><div>Section 4.=
2.13. Says:</div><div><br></div><div>Length=C2=A0</div><div><br></div><div>=
=C2=A0 =C2=A0 76</div><div><br></div><div>It should say:</div><div><br></di=
v><div>Length</div><div>=C2=A0=C2=A0</div><div>=C2=A0 =C2=A0 =C2=A036 plus =
the length of the 2 MAC fields</div><div><br></div><div>Section 4.2.13. Say=
s:</div><br>=C2=A0 =C2=A0EMSK Compound MAC<br><br>=C2=A0 =C2=A0 =C2=A0 The =
EMSK Compound MAC field is 20 octets.=C2=A0 This can be the Server<br>=C2=
=A0 =C2=A0 =C2=A0 MAC (B1_MAC) or the Client MAC (B2_MAC).=C2=A0 The comput=
ation of the<br>=C2=A0 =C2=A0 =C2=A0 MAC is described in Section 5.3.<br><b=
r>=C2=A0 =C2=A0MSK Compound MAC<br><br>=C2=A0 =C2=A0 =C2=A0 The MSK Compoun=
d MAC field is 20 octets.=C2=A0 This can be the Server<br>=C2=A0 =C2=A0 =C2=
=A0 MAC (B1_MAC) or the Client MAC (B2_MAC).=C2=A0 The computation of the<b=
r>=C2=A0 =C2=A0 =C2=A0 MAC is described in Section 5.3.<div><br></div><div>=
It Should Say:</div><div><br></div><div>=C2=A0 =C2=A0EMSK Compound MAC<br><=
br>=C2=A0 =C2=A0 =C2=A0 The computation of the MAC is described in Section =
5.3.=C2=A0 This can be=C2=A0</div><div>=C2=A0 =C2=A0 =C2=A0 the Server MAC =
(B1_MAC) or the Client MAC (B2_MAC). =C2=A0<br><br>=C2=A0 =C2=A0MSK Compoun=
d MAC<br><br>=C2=A0 =C2=A0 =C2=A0 The computation of the MAC is described i=
n Section 5.3.=C2=A0 This can be=C2=A0</div><div>=C2=A0 =C2=A0 =C2=A0 the S=
erver MAC (B1_MAC) or the Client MAC (B2_MAC). =C2=A0<div></div></div><div>=
<br></div><div>Section 5.3 Says:</div><div><br></div>=C2=A0The Compound MAC=
 computation is as follows:<br><br>=C2=A0 =C2=A0 =C2=A0 CMK =3D CMK[j]<br>=
=C2=A0 =C2=A0 =C2=A0 Compound-MAC =3D MAC( CMK, BUFFER )<br><br>=C2=A0 =C2=
=A0where j is the number of the last successfully executed inner EAP<br>=C2=
=A0 =C2=A0method, MAC is the MAC function negotiated in TLS 1.2 [RFC5246], =
and<br>=C2=A0 =C2=A0BUFFER is created after concatenating these fields in t=
he following<br>=C2=A0 =C2=A0order:<br><br>=C2=A0 =C2=A01 =C2=A0The entire =
Crypto-Binding TLV attribute with both the EMSK and MSK<br>=C2=A0 =C2=A0 =
=C2=A0 Compound MAC fields zeroed out.<br><br>=C2=A0 =C2=A02 =C2=A0The EAP =
Type sent by the other party in the first TEAP message.<div><br></div><div>=
It Should say:=C2=A0<br><div><br></div></div><div>=C2=A0The Compound MAC co=
mputation is as follows:<br><br>=C2=A0 =C2=A0 =C2=A0 CMK =3D CMK[j]<br>=C2=
=A0 =C2=A0 =C2=A0 Compound-MAC =3D MAC( CMK, BUFFER )<br><br>=C2=A0 =C2=A0w=
here j is the number of the last successfully executed inner EAP<br>=C2=A0 =
=C2=A0method, MAC is HMAC [RFC2104] using the hash function negotiated in</=
div><div>=C2=A0 =C2=A0TLS [RFC5246].=C2=A0 The output length is the length =
of the output of the HMAC</div><div>=C2=A0 =C2=A0function.=C2=A0 The BUFFER=
 is created after concatenating these fields in=C2=A0</div><div>=C2=A0 =C2=
=A0the following order:</div><div><br>=C2=A0 =C2=A01 =C2=A0The entire Crypt=
o-Binding TLV attribute with both the EMSK and MSK<br>=C2=A0 =C2=A0 =C2=A0 =
Compound MAC fields zeroed out.<br><br>=C2=A0 =C2=A02 =C2=A0The EAP Type se=
nt by the other party in the first TEAP message. This<br></div><div>=C2=A0 =
=C2=A0 =C2=A0 =C2=A0is a single octet encoded as (0x37)</div><div><br></div=
><div>Notes:</div><div><br></div><div>This corrects the problem that the MA=
C output will vary depending upon the TLS hash function. It clarifies that =
HMAC is used with the hash function negotiated in TLS.=C2=A0 =C2=A0It also =
clarifies that the=C2=A0 EAP Type used in the TLS message is the TEAP EAP t=
ype encoded as a single byte.=C2=A0=C2=A0</div></div>

--0000000000006c0f6f05b2719e56--


From nobody Sat Oct 24 16:29:51 2020
Return-Path: <oleg.pekar.2017@gmail.com>
X-Original-To: emu@ietfa.amsl.com
Delivered-To: emu@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id E53F93A1165 for <emu@ietfa.amsl.com>; Sat, 24 Oct 2020 16:29:50 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.847
X-Spam-Level: 
X-Spam-Status: No, score=-1.847 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, DKIM_VALID_EF=-0.1, FREEMAIL_ENVFROM_END_DIGIT=0.25, FREEMAIL_FROM=0.001, HTML_MESSAGE=0.001, SPF_HELO_NONE=0.001, SPF_PASS=-0.001, URIBL_BLOCKED=0.001] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (2048-bit key) header.d=gmail.com
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 Lf2CWIg4WF62 for <emu@ietfa.amsl.com>; Sat, 24 Oct 2020 16:29:49 -0700 (PDT)
Received: from mail-ot1-x331.google.com (mail-ot1-x331.google.com [IPv6:2607:f8b0:4864:20::331]) (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 541663A1164 for <emu@ietf.org>; Sat, 24 Oct 2020 16:29:49 -0700 (PDT)
Received: by mail-ot1-x331.google.com with SMTP id m11so4849654otk.13 for <emu@ietf.org>; Sat, 24 Oct 2020 16:29:49 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20161025;  h=mime-version:references:in-reply-to:from:date:message-id:subject:to :cc; bh=Nk6uaQI7/o+Vup20WHbqZgCKmQx7xBZy5ntDnSqrH9M=; b=scbW0QRL4ZYSPSLu2QqIXDr9WsxlNtQzdg2gqq/Jw4vl3DhH/CbA3LZvTxWhNH5T15 Zxuzgtm5uPgwcXbcwrzyFh4WZakCvp06i5+GxKcHT7hYO1chhztkir+BkUqE0oCrNVmX YqY43AN6E5ExalH2eZeOcdgeqILxapQWaseBcgmhFMz05CVZyu3qCFqzOkevKk/TqkDD J4gb2OEpnWLV0RXy5Fv/VrK/AlOLQ4pGV+GNwh3nNhTSxRN85MwcIt7FoZiULEMErBJ5 9NixvQVi64x7UtBglpbw1dwOCj+wlmECRtd9xWz71Rxo9mtc6FtJIGNrKfN1dTh0eo0E e4Jg==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:mime-version:references:in-reply-to:from:date :message-id:subject:to:cc; bh=Nk6uaQI7/o+Vup20WHbqZgCKmQx7xBZy5ntDnSqrH9M=; b=eO4V5xI3BP7x39J+bthAFEJn7I1wsroz5Ets6jqCu19iTcl9Npim8VjxGPWjG8ACKc XGOab+iinKfYawPYcd7zcO6Mf9FQgTGh91z4nCL/sNekWh7/wxeO5mknBvWGulmX+ua1 fyYjHS+FImd49VJxOu5MF3BssSVB/KyY/FVs6lPrqL5fKeuzPoFXkDYlcR8NgufXn6oI QBVFUwRmXSWA35VHxUsr8PmrMS8x8o6gQdUuIL7iV/RS6mtIZDP8jzMPsanmvvRJct8w SYr25/L9bc2+ElsWMjMFO/iNjgnRXQq953IuHPcZM/VcxHi0M3xCVS/XVhFIN+c/7pDV OGUA==
X-Gm-Message-State: AOAM532u9dfhjailosf1gjWdzPDKvsQ1loNicIMDp3FNPdMl8BJCweLk tRFyX+OZb6UiA1m4MqZoK3lAk+69kixjF7Y3IBbVOqJYIF8znw==
X-Google-Smtp-Source: ABdhPJwvjSLvhmfD0+wFCmVUAIzT5jzn76T3t4a0896SWvLK+1WKdEEKw6+tfUjsKf5FOgud7EJ9e+nrsXsR/mGzAQQ=
X-Received: by 2002:a9d:5547:: with SMTP id h7mr8209228oti.248.1603582188628;  Sat, 24 Oct 2020 16:29:48 -0700 (PDT)
MIME-Version: 1.0
References: <CAOgPGoBonHYt_0ZVutnMk-ijVHFqk+_xNKhchkiHzhvzYkNf-Q@mail.gmail.com>
In-Reply-To: <CAOgPGoBonHYt_0ZVutnMk-ijVHFqk+_xNKhchkiHzhvzYkNf-Q@mail.gmail.com>
From: Oleg Pekar <oleg.pekar.2017@gmail.com>
Date: Sun, 25 Oct 2020 01:29:37 +0200
Message-ID: <CABXxEz-UnLvPmWFuqKHtT6MoNTrhSLEf3SyqhSWFrnapMrmmSg@mail.gmail.com>
To: Joseph Salowey <joe@salowey.net>
Cc: EMU WG <emu@ietf.org>, Jouni Malinen <j@w1.fi>,  Jorge Vergara <jovergar=40microsoft.com@dmarc.ietf.org>
Content-Type: multipart/alternative; boundary="000000000000b8adf405b2731296"
Archived-At: <https://mailarchive.ietf.org/arch/msg/emu/xHVNYFhf6DUzTw1eXuIzLXgdpCg>
Subject: Re: [Emu] Proposed Resolution for TEAP errata 5768
X-BeenThere: emu@ietf.org
X-Mailman-Version: 2.1.29
Precedence: list
List-Id: "EAP Methods Update \(EMU\)" <emu.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/emu>, <mailto:emu-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/emu/>
List-Post: <mailto:emu@ietf.org>
List-Help: <mailto:emu-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/emu>, <mailto:emu-request@ietf.org?subject=subscribe>
X-List-Received-Date: Sat, 24 Oct 2020 23:29:51 -0000

--000000000000b8adf405b2731296
Content-Type: text/plain; charset="UTF-8"

> 2  The EAP Type sent by the other party in the first TEAP message. This
is a single octet encoded as (0x37)

Shouldn't we clarify the motivation for placing the octet with TEAP type
0x37 into the BUFFER? Joe, I remember you explained that it is for
protection against cross protocol attacks if Crypto-Binding TLV was reused
(e.g. from PEAP).

On Sun, Oct 25, 2020 at 12:45 AM Joseph Salowey <joe@salowey.net> wrote:

> Errata 5768:  https://www.rfc-editor.org/errata/eid5768
> Proposed State: Verified
> Revision:
>
> Section 4.2.13. Says:
>
> Length
>
>     76
>
> It should say:
>
> Length
>
>      36 plus the length of the 2 MAC fields
>
> Section 4.2.13. Says:
>
>    EMSK Compound MAC
>
>       The EMSK Compound MAC field is 20 octets.  This can be the Server
>       MAC (B1_MAC) or the Client MAC (B2_MAC).  The computation of the
>       MAC is described in Section 5.3.
>
>    MSK Compound MAC
>
>       The MSK Compound MAC field is 20 octets.  This can be the Server
>       MAC (B1_MAC) or the Client MAC (B2_MAC).  The computation of the
>       MAC is described in Section 5.3.
>
> It Should Say:
>
>    EMSK Compound MAC
>
>       The computation of the MAC is described in Section 5.3.  This can be
>       the Server MAC (B1_MAC) or the Client MAC (B2_MAC).
>
>    MSK Compound MAC
>
>       The computation of the MAC is described in Section 5.3.  This can be
>       the Server MAC (B1_MAC) or the Client MAC (B2_MAC).
>
> Section 5.3 Says:
>
>  The Compound MAC computation is as follows:
>
>       CMK = CMK[j]
>       Compound-MAC = MAC( CMK, BUFFER )
>
>    where j is the number of the last successfully executed inner EAP
>    method, MAC is the MAC function negotiated in TLS 1.2 [RFC5246], and
>    BUFFER is created after concatenating these fields in the following
>    order:
>
>    1  The entire Crypto-Binding TLV attribute with both the EMSK and MSK
>       Compound MAC fields zeroed out.
>
>    2  The EAP Type sent by the other party in the first TEAP message.
>
> It Should say:
>
>  The Compound MAC computation is as follows:
>
>       CMK = CMK[j]
>       Compound-MAC = MAC( CMK, BUFFER )
>
>    where j is the number of the last successfully executed inner EAP
>    method, MAC is HMAC [RFC2104] using the hash function negotiated in
>    TLS [RFC5246].  The output length is the length of the output of the
> HMAC
>    function.  The BUFFER is created after concatenating these fields in
>    the following order:
>
>    1  The entire Crypto-Binding TLV attribute with both the EMSK and MSK
>       Compound MAC fields zeroed out.
>
>    2  The EAP Type sent by the other party in the first TEAP message. This
>        is a single octet encoded as (0x37)
>
> Notes:
>
> This corrects the problem that the MAC output will vary depending upon the
> TLS hash function. It clarifies that HMAC is used with the hash function
> negotiated in TLS.   It also clarifies that the  EAP Type used in the TLS
> message is the TEAP EAP type encoded as a single byte.
>

--000000000000b8adf405b2731296
Content-Type: text/html; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable

<div dir=3D"ltr">&gt; 2 =C2=A0The EAP Type sent by the other party in the f=
irst TEAP message. This is a single octet encoded as (0x37)<div><br></div><=
div>Shouldn&#39;t we clarify the motivation for placing the octet with TEAP=
 type 0x37 into the BUFFER? Joe, I remember you explained that it is for pr=
otection against cross protocol attacks if Crypto-Binding TLV was reused (e=
.g. from PEAP).</div></div><br><div class=3D"gmail_quote"><div dir=3D"ltr" =
class=3D"gmail_attr">On Sun, Oct 25, 2020 at 12:45 AM Joseph Salowey &lt;<a=
 href=3D"mailto:joe@salowey.net">joe@salowey.net</a>&gt; wrote:<br></div><b=
lockquote class=3D"gmail_quote" style=3D"margin:0px 0px 0px 0.8ex;border-le=
ft:1px solid rgb(204,204,204);padding-left:1ex"><div dir=3D"ltr">Errata 576=
8:=C2=A0=C2=A0<a href=3D"https://www.rfc-editor.org/errata/eid5768" target=
=3D"_blank">https://www.rfc-editor.org/errata/eid5768</a><div>Proposed Stat=
e: Verified</div><div>Revision:</div><div><br></div><div>Section 4.2.13. Sa=
ys:</div><div><br></div><div>Length=C2=A0</div><div><br></div><div>=C2=A0 =
=C2=A0 76</div><div><br></div><div>It should say:</div><div><br></div><div>=
Length</div><div>=C2=A0=C2=A0</div><div>=C2=A0 =C2=A0 =C2=A036 plus the len=
gth of the 2 MAC fields</div><div><br></div><div>Section 4.2.13. Says:</div=
><br>=C2=A0 =C2=A0EMSK Compound MAC<br><br>=C2=A0 =C2=A0 =C2=A0 The EMSK Co=
mpound MAC field is 20 octets.=C2=A0 This can be the Server<br>=C2=A0 =C2=
=A0 =C2=A0 MAC (B1_MAC) or the Client MAC (B2_MAC).=C2=A0 The computation o=
f the<br>=C2=A0 =C2=A0 =C2=A0 MAC is described in Section 5.3.<br><br>=C2=
=A0 =C2=A0MSK Compound MAC<br><br>=C2=A0 =C2=A0 =C2=A0 The MSK Compound MAC=
 field is 20 octets.=C2=A0 This can be the Server<br>=C2=A0 =C2=A0 =C2=A0 M=
AC (B1_MAC) or the Client MAC (B2_MAC).=C2=A0 The computation of the<br>=C2=
=A0 =C2=A0 =C2=A0 MAC is described in Section 5.3.<div><br></div><div>It Sh=
ould Say:</div><div><br></div><div>=C2=A0 =C2=A0EMSK Compound MAC<br><br>=
=C2=A0 =C2=A0 =C2=A0 The computation of the MAC is described in Section 5.3=
.=C2=A0 This can be=C2=A0</div><div>=C2=A0 =C2=A0 =C2=A0 the Server MAC (B1=
_MAC) or the Client MAC (B2_MAC). =C2=A0<br><br>=C2=A0 =C2=A0MSK Compound M=
AC<br><br>=C2=A0 =C2=A0 =C2=A0 The computation of the MAC is described in S=
ection 5.3.=C2=A0 This can be=C2=A0</div><div>=C2=A0 =C2=A0 =C2=A0 the Serv=
er MAC (B1_MAC) or the Client MAC (B2_MAC). =C2=A0<div></div></div><div><br=
></div><div>Section 5.3 Says:</div><div><br></div>=C2=A0The Compound MAC co=
mputation is as follows:<br><br>=C2=A0 =C2=A0 =C2=A0 CMK =3D CMK[j]<br>=C2=
=A0 =C2=A0 =C2=A0 Compound-MAC =3D MAC( CMK, BUFFER )<br><br>=C2=A0 =C2=A0w=
here j is the number of the last successfully executed inner EAP<br>=C2=A0 =
=C2=A0method, MAC is the MAC function negotiated in TLS 1.2 [RFC5246], and<=
br>=C2=A0 =C2=A0BUFFER is created after concatenating these fields in the f=
ollowing<br>=C2=A0 =C2=A0order:<br><br>=C2=A0 =C2=A01 =C2=A0The entire Cryp=
to-Binding TLV attribute with both the EMSK and MSK<br>=C2=A0 =C2=A0 =C2=A0=
 Compound MAC fields zeroed out.<br><br>=C2=A0 =C2=A02 =C2=A0The EAP Type s=
ent by the other party in the first TEAP message.<div><br></div><div>It Sho=
uld say:=C2=A0<br><div><br></div></div><div>=C2=A0The Compound MAC computat=
ion is as follows:<br><br>=C2=A0 =C2=A0 =C2=A0 CMK =3D CMK[j]<br>=C2=A0 =C2=
=A0 =C2=A0 Compound-MAC =3D MAC( CMK, BUFFER )<br><br>=C2=A0 =C2=A0where j =
is the number of the last successfully executed inner EAP<br>=C2=A0 =C2=A0m=
ethod, MAC is HMAC [RFC2104] using the hash function negotiated in</div><di=
v>=C2=A0 =C2=A0TLS [RFC5246].=C2=A0 The output length is the length of the =
output of the HMAC</div><div>=C2=A0 =C2=A0function.=C2=A0 The BUFFER is cre=
ated after concatenating these fields in=C2=A0</div><div>=C2=A0 =C2=A0the f=
ollowing order:</div><div><br>=C2=A0 =C2=A01 =C2=A0The entire Crypto-Bindin=
g TLV attribute with both the EMSK and MSK<br>=C2=A0 =C2=A0 =C2=A0 Compound=
 MAC fields zeroed out.<br><br>=C2=A0 =C2=A02 =C2=A0The EAP Type sent by th=
e other party in the first TEAP message. This<br></div><div>=C2=A0 =C2=A0 =
=C2=A0 =C2=A0is a single octet encoded as (0x37)</div><div><br></div><div>N=
otes:</div><div><br></div><div>This corrects the problem that the MAC outpu=
t will vary depending upon the TLS hash function. It clarifies that HMAC is=
 used with the hash function negotiated in TLS.=C2=A0 =C2=A0It also clarifi=
es that the=C2=A0 EAP Type used in the TLS message is the TEAP EAP type enc=
oded as a single byte.=C2=A0=C2=A0</div></div>
</blockquote></div>

--000000000000b8adf405b2731296--


From nobody Sat Oct 24 17:17:46 2020
Return-Path: <joe@salowey.net>
X-Original-To: emu@ietfa.amsl.com
Delivered-To: emu@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 7E8773A1185 for <emu@ietfa.amsl.com>; Sat, 24 Oct 2020 17:17:45 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.898
X-Spam-Level: 
X-Spam-Status: No, score=-1.898 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, HTML_MESSAGE=0.001, SPF_HELO_NONE=0.001, SPF_PASS=-0.001, URIBL_BLOCKED=0.001] autolearn=unavailable autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (2048-bit key) header.d=salowey-net.20150623.gappssmtp.com
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 z_DTTo9_8rO7 for <emu@ietfa.amsl.com>; Sat, 24 Oct 2020 17:17:43 -0700 (PDT)
Received: from mail-qv1-xf2e.google.com (mail-qv1-xf2e.google.com [IPv6:2607:f8b0:4864:20::f2e]) (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 5DC743A1184 for <emu@ietf.org>; Sat, 24 Oct 2020 17:17:43 -0700 (PDT)
Received: by mail-qv1-xf2e.google.com with SMTP id de3so2696800qvb.5 for <emu@ietf.org>; Sat, 24 Oct 2020 17:17:43 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=salowey-net.20150623.gappssmtp.com; s=20150623; h=mime-version:from:date:message-id:subject:to:cc; bh=a9AC2RAFe6OOSYv1FXfMa1Boht12ky8qk1Kjc3PINYg=; b=yulywLQ4beB1HdGLkzVeaivDjXi8ZiwBNh9uFrdZJOribQkFz2vzdAjRjxbkIPqsXQ Tc3YbTWyLytLPJXxYsppf1u0g8UDz3sOsqhXkYHy6yt5PgQrhAEfoFEBW6NmPRNakpbQ 1RxHi5PZvGwkI+EaQPRjMA5yWgFExIIMRyqeZHvqBuqjA9E2A0RFtGuYZxlY3wpYFcka XHTxhtH7iygfDHhLQhn9LwGh6IBQfaVdHWocrFgTMCjPfNWONO+1IdcdVEHSWTfjg0oA 8seA9iJ2uqisNM5hJu7HsqilW5MP5DitoILORApnuYj/5JMZfvvK8r+umIVJbLHROx9W yc+A==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:mime-version:from:date:message-id:subject:to:cc; bh=a9AC2RAFe6OOSYv1FXfMa1Boht12ky8qk1Kjc3PINYg=; b=tiLFfGtgOJGMjX1w1aUqrvvMDvuyLNvIvdACxLI1pl4A2gB/lEJtHngO2nMDkE0U3n brNLx4lI4vs1MaQ9Fs5gg8RWDfo7oK4gB/c+T390kgL2CG0ho3u39haS5lzNkVrKMhRY MjkhNkD+OUeQlbT0a8+9XgsO2ncg3jWmQLeB0dz30cjUiS9HavB6D+8uycTfFM84/ahV yI1fvKbR5z9265tvZDwGYcZrraOdM/Puspj1lYHHR+ol+cN8RAqRCMdIi0U4JN1GUfC8 t/Ceq0cltF68iBEJKvcwDE52Zeb3E6sAix/w/aEIYvdqiBhkI4geA2iT4Px8buObW5Vp CM/Q==
X-Gm-Message-State: AOAM530gia+KYh2ka6nG7SGMftowxDKprNq1iE6NaCduUaYWOi2wgf23 GfFjs+kBQOUu+gf7ZvYnAr/BLiMR2gMWgh5bcw66kyvEetjGdg==
X-Google-Smtp-Source: ABdhPJziaz+vp1Tz9eveYSUQN4+C2Rqj1wEjna/rymGIm/Niwk0KZLZPHxqfTalc85eoPMReY7GZv2DfK6KUyDZH4Q8=
X-Received: by 2002:ad4:4105:: with SMTP id i5mr6314709qvp.47.1603585061929; Sat, 24 Oct 2020 17:17:41 -0700 (PDT)
MIME-Version: 1.0
From: Joseph Salowey <joe@salowey.net>
Date: Sat, 24 Oct 2020 17:17:31 -0700
Message-ID: <CAOgPGoCg2wRKFVKz2kqkomt7mkp1W98jSh6xLT8z1_uWBMXdmA@mail.gmail.com>
To: EMU WG <emu@ietf.org>
Cc: Oleg Pekar <oleg.pekar.2017@gmail.com>, Jouni Malinen <j@w1.fi>,  Jorge Vergara <jovergar=40microsoft.com@dmarc.ietf.org>
Content-Type: multipart/alternative; boundary="000000000000fbe19f05b273bd3e"
Archived-At: <https://mailarchive.ietf.org/arch/msg/emu/cgjOE0FP7A-Y8PkQDXZs9ThHUHQ>
Subject: [Emu] Proposed Resolution to TEAP Errata 5770
X-BeenThere: emu@ietf.org
X-Mailman-Version: 2.1.29
Precedence: list
List-Id: "EAP Methods Update \(EMU\)" <emu.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/emu>, <mailto:emu-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/emu/>
List-Post: <mailto:emu@ietf.org>
List-Help: <mailto:emu-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/emu>, <mailto:emu-request@ietf.org?subject=subscribe>
X-List-Received-Date: Sun, 25 Oct 2020 00:17:46 -0000

--000000000000fbe19f05b273bd3e
Content-Type: text/plain; charset="UTF-8"

Errata 5770: https://www.rfc-editor.org/errata/eid5770
Proposed Status: Verified
Revision:

Section 5.2 Says:

On the sender of the Crypto-Binding TLV side:

     If the EMSK is not available, then the sender computes the Compound
     MAC using the MSK of the inner method.

     If the EMSK is available and the sender's policy accepts MSK-based
     MAC, then the sender computes two Compound MAC values.  The first
     is computed with the EMSK.  The second one is computed using the
     MSK.  Both MACs are then sent to the other side.

     If the EMSK is available but the sender's policy does not allow
     downgrading to MSK-generated MAC, then the sender SHOULD only send
     EMSK-based MAC.

   On the receiver of the Crypto-Binding TLV side:

     If the EMSK is not available and an MSK-based Compound MAC was
     sent, then the receiver validates the Compound MAC and sends back
     an MSK-based Compound MAC response.

     If the EMSK is not available and no MSK-based Compound MAC was
     sent, then the receiver handles like an invalid Crypto-Binding TLV
     with a fatal error.

     If the EMSK is available and an EMSK-based Compound MAC was sent,
     then the receiver validates it and creates a response Compound MAC
     using the EMSK.

     If the EMSK is available but no EMSK-based Compound MAC was sent
     and its policy accepts MSK-based MAC, then the receiver validates
     it using the MSK and, if successful, generates and returns an MSK-
     based Compound MAC.

     If the EMSK is available but no EMSK Compound MAC was sent and its
     policy does not accept MSK-based MAC, then the receiver handles
     like an invalid Crypto-Binding TLV with a fatal error.

If the ith inner method does not generate an EMSK or MSK, then IMSKi
is set to zero (e.g., MSKi = 32 octets of 0x00s).  If an inner method
fails, then it is not included in this calculation.

It Should Say:

On the sender of the Crypto-Binding TLV side:

     If the EMSK is not available, then the sender computes the Compound
     MAC using the CMK generated from MSK (CMK-MSK) of the inner method.

     If the EMSK is available and the sender's policy accepts MSK-based
     MAC, then the sender computes two Compound MAC values.  The first
     is computed with the CMK generated from the EMSK (CMK-EMSK).  The
     second one is computed using the CMK-MSK.  Both MACs are
     then sent to the other side.  This also means the sender must generate
     both EMSK and MSK based S-IMCKs.

     If the EMSK is available but the sender's policy does not allow
     downgrading to CMK-MSK MAC, then the sender SHOULD only send
     a MAC computed from the CMK-EMSK.

   On the receiver of the Crypto-Binding TLV side:

     If the EMSK is not available and an CMK-MSK Compound MAC was
     sent, then the receiver validates the Compound MAC and sends back
     an CMK-MSK Compound MAC response.

     If the EMSK is not available and no CMK-MSK Compound MAC was
     sent, then the receiver handles like an invalid Crypto-Binding TLV
     with a fatal error.

     If the EMSK is available and a CMK-EMSK Compound MAC was sent,
     then the receiver validates it and creates a response Compound MAC
     using the CMK-EMSK.

     If the EMSK is available but no CMK-EMSK Compound MAC was sent
     and its policy accepts CMK-MSK MAC, then the receiver validates
     it using the CMK-MSK and, if successful, generates and returns an MSK-
     based Compound MAC.

     If the EMSK is available but no CMK-EMSK Compound MAC was sent and its
     policy does not accept CMK-MSK MAC, then the receiver handles
     like an invalid Crypto-Binding TLV with a fatal error.

The IMSK used is either the EMSK-based IMSK or the MSK based IMSK depending
upon the rules outlined above. If the ith inner method does not generate an
EMSK
or MSK, then IMSKi is set to zero (e.g., MSKi = 32 octets of 0x00s).    It
is possible
that two S-IMCKs for a step may be generated based on the rules above.  In
this
case the S-IMCK for further calculations is chosen as follows.  If the MAC
based
on the CMK-EMSK is verified then the S-IMCK generated based on the EMSK is
used.  Else, if the MAC based on the CMK-MSK is verified then the S-IMCK
generated based on the MSK is used.  If an inner method fails or MAC
verification
fails then S-IMCK is not used in further calculation.

Section 5.4 Says:

TEAP authentication assures the Master Session Key (MSK) and Extended
 Master Session Key (EMSK) output from the EAP method are the result
 of all authentication conversations by generating an Intermediate
 Compound Key (IMCK).  The IMCK is mutually derived by the peer and
 the server as described in Section 5.2 by combining the MSKs from inner
 EAP methods with key material from TEAP Phase 1.

It should say:

TEAP authentication assures the Master Session Key (MSK) and Extended
 Master Session Key (EMSK) output from the EAP method are the result
 of all authentication conversations by generating an Intermediate
 Compound Key (IMCK).  The IMCK is mutually derived by the peer and
 the server as described in Section 5.2 by combining the IMSKs from inner
 EAP methods with key material from TEAP Phase 1.

Note:

This revision is to clarify how to handle the case where you need to
generate
both MSK and EMSK keys.   The original text was incomplete and ambiguous
in some places.

--000000000000fbe19f05b273bd3e
Content-Type: text/html; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable

<div dir=3D"ltr">Errata 5770:=C2=A0<a href=3D"https://www.rfc-editor.org/er=
rata/eid5770">https://www.rfc-editor.org/errata/eid5770</a><div>Proposed St=
atus: Verified</div><div>Revision:</div><div><br></div><div>Section 5.2 Say=
s:</div><div><br></div>On the sender of the Crypto-Binding TLV side: =C2=A0=
 =C2=A0<br><br>=C2=A0 =C2=A0 =C2=A0If the EMSK is not available, then the s=
ender computes the Compound<br>=C2=A0 =C2=A0 =C2=A0MAC using the MSK of the=
 inner method.<br><br>=C2=A0 =C2=A0 =C2=A0If the EMSK is available and the =
sender&#39;s policy accepts MSK-based<br>=C2=A0 =C2=A0 =C2=A0MAC, then the =
sender computes two Compound MAC values.=C2=A0 The first<br>=C2=A0 =C2=A0 =
=C2=A0is computed with the EMSK.=C2=A0 The second one is computed using the=
<br>=C2=A0 =C2=A0 =C2=A0MSK.=C2=A0 Both MACs are then sent to the other sid=
e.<br><br>=C2=A0 =C2=A0 =C2=A0If the EMSK is available but the sender&#39;s=
 policy does not allow<br>=C2=A0 =C2=A0 =C2=A0downgrading to MSK-generated =
MAC, then the sender SHOULD only send<br>=C2=A0 =C2=A0 =C2=A0EMSK-based MAC=
.<br><br>=C2=A0 =C2=A0On the receiver of the Crypto-Binding TLV side:<br><b=
r>=C2=A0 =C2=A0 =C2=A0If the EMSK is not available and an MSK-based Compoun=
d MAC was<br>=C2=A0 =C2=A0 =C2=A0sent, then the receiver validates the Comp=
ound MAC and sends back<br>=C2=A0 =C2=A0 =C2=A0an MSK-based Compound MAC re=
sponse.<br><br>=C2=A0 =C2=A0 =C2=A0If the EMSK is not available and no MSK-=
based Compound MAC was<br>=C2=A0 =C2=A0 =C2=A0sent, then the receiver handl=
es like an invalid Crypto-Binding TLV<br>=C2=A0 =C2=A0 =C2=A0with a fatal e=
rror.<br><br>=C2=A0 =C2=A0 =C2=A0If the EMSK is available and an EMSK-based=
 Compound MAC was sent,<br>=C2=A0 =C2=A0 =C2=A0then the receiver validates =
it and creates a response Compound MAC<br>=C2=A0 =C2=A0 =C2=A0using the EMS=
K.<br><br>=C2=A0 =C2=A0 =C2=A0If the EMSK is available but no EMSK-based Co=
mpound MAC was sent<br>=C2=A0 =C2=A0 =C2=A0and its policy accepts MSK-based=
 MAC, then the receiver validates<br>=C2=A0 =C2=A0 =C2=A0it using the MSK a=
nd, if successful, generates and returns an MSK-<br>=C2=A0 =C2=A0 =C2=A0bas=
ed Compound MAC.<br><br>=C2=A0 =C2=A0 =C2=A0If the EMSK is available but no=
 EMSK Compound MAC was sent and its<br>=C2=A0 =C2=A0 =C2=A0policy does not =
accept MSK-based MAC, then the receiver handles<br>=C2=A0 =C2=A0 =C2=A0like=
 an invalid Crypto-Binding TLV with a fatal error.<div><br></div><div>If th=
e ith inner method does not generate an EMSK or MSK, then IMSKi<br>is set t=
o zero (e.g., MSKi =3D 32 octets of 0x00s).=C2=A0 If an inner method<br>fai=
ls, then it is not included in this calculation.<br></div><div><br></div><d=
iv>It Should Say:</div><div><br></div><div>On the sender of the Crypto-Bind=
ing TLV side: =C2=A0 =C2=A0<br><br>=C2=A0 =C2=A0 =C2=A0If the EMSK is not a=
vailable, then the sender computes the Compound<br>=C2=A0 =C2=A0 =C2=A0MAC =
using the CMK generated from MSK (CMK-MSK) of the inner method.<br><br>=C2=
=A0 =C2=A0 =C2=A0If the EMSK is available and the sender&#39;s policy accep=
ts MSK-based<br>=C2=A0 =C2=A0 =C2=A0MAC, then the sender computes two Compo=
und MAC values.=C2=A0 The first<br>=C2=A0 =C2=A0 =C2=A0is computed with the=
 CMK generated from the EMSK (CMK-EMSK).=C2=A0 The=C2=A0</div><div>=C2=A0 =
=C2=A0 =C2=A0second one is computed using the=C2=A0CMK-MSK.=C2=A0 Both MACs=
 are=C2=A0</div><div>=C2=A0 =C2=A0 =C2=A0then sent to the other side.=C2=A0=
 This also means the sender must generate</div><div>=C2=A0 =C2=A0 =C2=A0bot=
h EMSK and MSK based S-IMCKs.<br><br>=C2=A0 =C2=A0 =C2=A0If the EMSK is ava=
ilable but the sender&#39;s policy does not allow<br>=C2=A0 =C2=A0 =C2=A0do=
wngrading to CMK-MSK MAC, then the sender SHOULD only send<br>=C2=A0 =C2=A0=
 =C2=A0a MAC computed from the CMK-EMSK.<br><br>=C2=A0 =C2=A0On the receive=
r of the Crypto-Binding TLV side:<br><br>=C2=A0 =C2=A0 =C2=A0If the EMSK is=
 not available and an CMK-MSK Compound MAC was<br>=C2=A0 =C2=A0 =C2=A0sent,=
 then the receiver validates the Compound MAC and sends back<br>=C2=A0 =C2=
=A0 =C2=A0an CMK-MSK Compound MAC response.<br><br>=C2=A0 =C2=A0 =C2=A0If t=
he EMSK is not available and no CMK-MSK Compound MAC was<br>=C2=A0 =C2=A0 =
=C2=A0sent, then the receiver handles like an invalid Crypto-Binding TLV<br=
>=C2=A0 =C2=A0 =C2=A0with a fatal error.<br><br>=C2=A0 =C2=A0 =C2=A0If the =
EMSK is available and a CMK-EMSK Compound MAC was sent,<br>=C2=A0 =C2=A0 =
=C2=A0then the receiver validates it and creates a response Compound MAC<br=
>=C2=A0 =C2=A0 =C2=A0using the CMK-EMSK.<br><br>=C2=A0 =C2=A0 =C2=A0If the =
EMSK is available but no CMK-EMSK Compound MAC was sent<br>=C2=A0 =C2=A0 =
=C2=A0and its policy accepts CMK-MSK MAC, then the receiver validates<br>=
=C2=A0 =C2=A0 =C2=A0it using the CMK-MSK and, if successful, generates and =
returns an MSK-<br>=C2=A0 =C2=A0 =C2=A0based Compound MAC.<br><br>=C2=A0 =
=C2=A0 =C2=A0If the EMSK is available but no CMK-EMSK Compound MAC was sent=
 and its<br>=C2=A0 =C2=A0 =C2=A0policy does not accept CMK-MSK MAC, then th=
e receiver handles<br>=C2=A0 =C2=A0 =C2=A0like an invalid Crypto-Binding TL=
V with a fatal error.<br></div><div><br></div>The IMSK used is either the E=
MSK-based IMSK or the MSK based IMSK depending<br>upon the rules outlined a=
bove. If the ith inner method does not generate an EMSK=C2=A0<br>or MSK, th=
en IMSKi is set to zero (e.g., MSKi =3D 32 octets of 0x00s). =C2=A0=C2=A0 I=
t is possible=C2=A0<div>that two S-IMCKs for a step may be generated based =
on the rules above.=C2=A0 In this=C2=A0</div><div>case the S-IMCK for=C2=A0=
further calculations is chosen as follows.=C2=A0 If the MAC based=C2=A0</di=
v><div>on the CMK-EMSK is=C2=A0verified then the S-IMCK generated based on =
the EMSK is=C2=A0</div><div>used.=C2=A0 Else, if the MAC=C2=A0based on the =
CMK-MSK is verified then the S-IMCK=C2=A0</div><div>generated based on the =
MSK=C2=A0is used.=C2=A0 If an inner method fails or MAC verification=C2=A0<=
/div><div>fails then S-IMCK is not used in further calculation.=C2=A0=C2=A0=
<div><div><br></div><div>Section 5.4 Says:<br><br></div><div>TEAP authentic=
ation assures the Master Session Key (MSK) and Extended<br>=C2=A0Master Ses=
sion Key (EMSK) output from the EAP method are the result<br>=C2=A0of all a=
uthentication conversations by generating an Intermediate<br>=C2=A0Compound=
 Key (IMCK).=C2=A0 The IMCK is mutually derived by the peer and<br>=C2=A0th=
e server as described in Section 5.2 by combining the MSKs from inner</div>=
<div>=C2=A0EAP methods with key material from TEAP Phase 1.<br></div><div><=
br></div><div>It should say:</div><div><br></div><div><div>TEAP authenticat=
ion assures the Master Session Key (MSK) and Extended<br>=C2=A0Master Sessi=
on Key (EMSK) output from the EAP method are the result<br>=C2=A0of all aut=
hentication conversations by generating an Intermediate<br>=C2=A0Compound K=
ey (IMCK).=C2=A0 The IMCK is mutually derived by the peer and<br>=C2=A0the =
server as described in Section 5.2 by combining the IMSKs from inner</div><=
div>=C2=A0EAP methods with key material from TEAP Phase 1.</div></div><div>=
<br></div></div></div><div>Note:</div><div><br></div><div>This revision is =
to clarify how to handle the case where you need to generate=C2=A0</div><di=
v>both MSK and EMSK keys.=C2=A0 =C2=A0The original text was incomplete=C2=
=A0and ambiguous=C2=A0</div><div>in some places.=C2=A0=C2=A0</div></div>

--000000000000fbe19f05b273bd3e--


From nobody Sat Oct 24 17:20:07 2020
Return-Path: <joe@salowey.net>
X-Original-To: emu@ietfa.amsl.com
Delivered-To: emu@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id C06193A1186 for <emu@ietfa.amsl.com>; Sat, 24 Oct 2020 17:20:06 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.898
X-Spam-Level: 
X-Spam-Status: No, score=-1.898 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, HTML_MESSAGE=0.001, SPF_HELO_NONE=0.001, SPF_PASS=-0.001, URIBL_BLOCKED=0.001] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (2048-bit key) header.d=salowey-net.20150623.gappssmtp.com
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 9iJKGT0ijfPl for <emu@ietfa.amsl.com>; Sat, 24 Oct 2020 17:20:05 -0700 (PDT)
Received: from mail-qk1-x72a.google.com (mail-qk1-x72a.google.com [IPv6:2607:f8b0:4864:20::72a]) (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 158043A1181 for <emu@ietf.org>; Sat, 24 Oct 2020 17:20:05 -0700 (PDT)
Received: by mail-qk1-x72a.google.com with SMTP id b69so5193249qkg.8 for <emu@ietf.org>; Sat, 24 Oct 2020 17:20:05 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=salowey-net.20150623.gappssmtp.com; s=20150623; h=mime-version:references:in-reply-to:from:date:message-id:subject:to :cc; bh=jtl3StKUKpsDTb8OadTvNmSShRSJ2RUpEwbSEBT3DAA=; b=yQJW2qg5i6k7owSAuUoWphF+VF1yY0/XuRYCzf5eaViXxSPoZTzuvKFj5jc43JTz9e PQuP9zAdwxDOfzv87ZhRDTuPwr4dv8ReVMEGhzyB0pBh10Yi22DnYsStO0dw+6lVG0WE X1IK8pyKxKn7vOjNpadZR1WEM89PPDoxPhqqNaC+SeWZQxna45x5q7eMq9PB/hUPbtKK e3iRhQtIjgjz5WmS8Crl54ifOu+G8EGK485CohhVDIhzddEDGxarvdPQt4DsPg0+Pkbe b+RkEgI/vE44TNo95ypACzAn6HCCE38webHvUWb8Tptsjcie19U3DWXyD1bewaUxSkvU wNPg==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:mime-version:references:in-reply-to:from:date :message-id:subject:to:cc; bh=jtl3StKUKpsDTb8OadTvNmSShRSJ2RUpEwbSEBT3DAA=; b=YQ+JMRfjkAGaQ9yuGOGDxsEdt5S8L89vtZ5qtUl+pm6S3jAyd7d0canrJoHv6veiH5 RyYCVSOFoPfjNf70fDZzFja/D8/vYty48rMviL8+F7rrzYhK3V+dB4kRlhzvDX0uOvfu OpDhx8s7TKsdQ4OiBKF7rQQx0Rd7+CVxSE5yLA+KPQPGhIUK+c9ZhBopyTjMv2OjzX1d Q46jjjxavK0xMTrvQIFmo0qrUOq6gJwgLSjfABRmTXjz59qOamsQFWMdtLZ7LTQz1zOj COva8ZIJ5EpWVfKzmHsjz4LgtQz7kiaB7hFLVmbOsZSt9KtjiAvURtbn0arm0pHeM2n1 eCfg==
X-Gm-Message-State: AOAM530YLz8LakQQECD/IoW5x0hWe+wRe+GmQsXqcBJqjYaZ4SPoHXzF HGPNhWste9wXYFSEA8rPAwoy+JGcuGXFLWjP7ZFUDg==
X-Google-Smtp-Source: ABdhPJyh4+ktPbPx4ku+p9Qrf9yP/R67tfrl+pRiR6b5OjfEKa3gXNiFDp+sCJfJE6WNi/OZQdmuLqnF4kaYMfWCQ2g=
X-Received: by 2002:a05:620a:215d:: with SMTP id m29mr10025573qkm.138.1603585204075;  Sat, 24 Oct 2020 17:20:04 -0700 (PDT)
MIME-Version: 1.0
References: <CAOgPGoBonHYt_0ZVutnMk-ijVHFqk+_xNKhchkiHzhvzYkNf-Q@mail.gmail.com> <CABXxEz-UnLvPmWFuqKHtT6MoNTrhSLEf3SyqhSWFrnapMrmmSg@mail.gmail.com>
In-Reply-To: <CABXxEz-UnLvPmWFuqKHtT6MoNTrhSLEf3SyqhSWFrnapMrmmSg@mail.gmail.com>
From: Joseph Salowey <joe@salowey.net>
Date: Sat, 24 Oct 2020 17:19:53 -0700
Message-ID: <CAOgPGoCEwXH4ozv17iS-C_0bEcG6eJO+m+SjeUVLL_AFTtMULg@mail.gmail.com>
To: Oleg Pekar <oleg.pekar.2017@gmail.com>
Cc: EMU WG <emu@ietf.org>, Jouni Malinen <j@w1.fi>,  Jorge Vergara <jovergar=40microsoft.com@dmarc.ietf.org>
Content-Type: multipart/alternative; boundary="00000000000074e14705b273c689"
Archived-At: <https://mailarchive.ietf.org/arch/msg/emu/ZCfbj-tgfFvV4P_tpDSOhQMtt2w>
Subject: Re: [Emu] Proposed Resolution for TEAP errata 5768
X-BeenThere: emu@ietf.org
X-Mailman-Version: 2.1.29
Precedence: list
List-Id: "EAP Methods Update \(EMU\)" <emu.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/emu>, <mailto:emu-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/emu/>
List-Post: <mailto:emu@ietf.org>
List-Help: <mailto:emu-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/emu>, <mailto:emu-request@ietf.org?subject=subscribe>
X-List-Received-Date: Sun, 25 Oct 2020 00:20:07 -0000

--00000000000074e14705b273c689
Content-Type: text/plain; charset="UTF-8"

On Sat, Oct 24, 2020 at 4:29 PM Oleg Pekar <oleg.pekar.2017@gmail.com>
wrote:

> > 2  The EAP Type sent by the other party in the first TEAP message. This
> is a single octet encoded as (0x37)
>
> Shouldn't we clarify the motivation for placing the octet with TEAP type
> 0x37 into the BUFFER? Joe, I remember you explained that it is for
> protection against cross protocol attacks if Crypto-Binding TLV was reused
> (e.g. from PEAP).
>

[Joe]  That's more of an editorial comment that we would hold for a
document revision.  I think we should try to keep the revision text at a
minimum, but we certainly can include this information in the errata
notes.


> On Sun, Oct 25, 2020 at 12:45 AM Joseph Salowey <joe@salowey.net> wrote:
>
>> Errata 5768:  https://www.rfc-editor.org/errata/eid5768
>> Proposed State: Verified
>> Revision:
>>
>> Section 4.2.13. Says:
>>
>> Length
>>
>>     76
>>
>> It should say:
>>
>> Length
>>
>>      36 plus the length of the 2 MAC fields
>>
>> Section 4.2.13. Says:
>>
>>    EMSK Compound MAC
>>
>>       The EMSK Compound MAC field is 20 octets.  This can be the Server
>>       MAC (B1_MAC) or the Client MAC (B2_MAC).  The computation of the
>>       MAC is described in Section 5.3.
>>
>>    MSK Compound MAC
>>
>>       The MSK Compound MAC field is 20 octets.  This can be the Server
>>       MAC (B1_MAC) or the Client MAC (B2_MAC).  The computation of the
>>       MAC is described in Section 5.3.
>>
>> It Should Say:
>>
>>    EMSK Compound MAC
>>
>>       The computation of the MAC is described in Section 5.3.  This can
>> be
>>       the Server MAC (B1_MAC) or the Client MAC (B2_MAC).
>>
>>    MSK Compound MAC
>>
>>       The computation of the MAC is described in Section 5.3.  This can
>> be
>>       the Server MAC (B1_MAC) or the Client MAC (B2_MAC).
>>
>> Section 5.3 Says:
>>
>>  The Compound MAC computation is as follows:
>>
>>       CMK = CMK[j]
>>       Compound-MAC = MAC( CMK, BUFFER )
>>
>>    where j is the number of the last successfully executed inner EAP
>>    method, MAC is the MAC function negotiated in TLS 1.2 [RFC5246], and
>>    BUFFER is created after concatenating these fields in the following
>>    order:
>>
>>    1  The entire Crypto-Binding TLV attribute with both the EMSK and MSK
>>       Compound MAC fields zeroed out.
>>
>>    2  The EAP Type sent by the other party in the first TEAP message.
>>
>> It Should say:
>>
>>  The Compound MAC computation is as follows:
>>
>>       CMK = CMK[j]
>>       Compound-MAC = MAC( CMK, BUFFER )
>>
>>    where j is the number of the last successfully executed inner EAP
>>    method, MAC is HMAC [RFC2104] using the hash function negotiated in
>>    TLS [RFC5246].  The output length is the length of the output of the
>> HMAC
>>    function.  The BUFFER is created after concatenating these fields in
>>    the following order:
>>
>>    1  The entire Crypto-Binding TLV attribute with both the EMSK and MSK
>>       Compound MAC fields zeroed out.
>>
>>    2  The EAP Type sent by the other party in the first TEAP message. This
>>        is a single octet encoded as (0x37)
>>
>> Notes:
>>
>> This corrects the problem that the MAC output will vary depending upon
>> the TLS hash function. It clarifies that HMAC is used with the hash
>> function negotiated in TLS.   It also clarifies that the  EAP Type used in
>> the TLS message is the TEAP EAP type encoded as a single byte.
>>
>

--00000000000074e14705b273c689
Content-Type: text/html; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable

<div dir=3D"ltr"><div dir=3D"ltr"><br></div><br><div class=3D"gmail_quote">=
<div dir=3D"ltr" class=3D"gmail_attr">On Sat, Oct 24, 2020 at 4:29 PM Oleg =
Pekar &lt;<a href=3D"mailto:oleg.pekar.2017@gmail.com">oleg.pekar.2017@gmai=
l.com</a>&gt; wrote:<br></div><blockquote class=3D"gmail_quote" style=3D"ma=
rgin:0px 0px 0px 0.8ex;border-left:1px solid rgb(204,204,204);padding-left:=
1ex"><div dir=3D"ltr">&gt; 2 =C2=A0The EAP Type sent by the other party in =
the first TEAP message. This is a single octet encoded as (0x37)<div><br></=
div><div>Shouldn&#39;t we clarify the motivation for placing the octet with=
 TEAP type 0x37 into the BUFFER? Joe, I remember you explained that it is f=
or protection against cross protocol attacks if Crypto-Binding TLV was reus=
ed (e.g. from PEAP).</div></div></blockquote><div><br></div><div>[Joe]=C2=
=A0 That&#39;s more of an editorial comment that we would hold for a docume=
nt revision.=C2=A0 I think we should try to keep the revision text at a min=
imum, but we certainly can include this information in the errata notes.=C2=
=A0 =C2=A0</div><div>=C2=A0</div><blockquote class=3D"gmail_quote" style=3D=
"margin:0px 0px 0px 0.8ex;border-left:1px solid rgb(204,204,204);padding-le=
ft:1ex"><div class=3D"gmail_quote"><div dir=3D"ltr" class=3D"gmail_attr">On=
 Sun, Oct 25, 2020 at 12:45 AM Joseph Salowey &lt;<a href=3D"mailto:joe@sal=
owey.net" target=3D"_blank">joe@salowey.net</a>&gt; wrote:<br></div><blockq=
uote class=3D"gmail_quote" style=3D"margin:0px 0px 0px 0.8ex;border-left:1p=
x solid rgb(204,204,204);padding-left:1ex"><div dir=3D"ltr">Errata 5768:=C2=
=A0=C2=A0<a href=3D"https://www.rfc-editor.org/errata/eid5768" target=3D"_b=
lank">https://www.rfc-editor.org/errata/eid5768</a><div>Proposed State: Ver=
ified</div><div>Revision:</div><div><br></div><div>Section 4.2.13. Says:</d=
iv><div><br></div><div>Length=C2=A0</div><div><br></div><div>=C2=A0 =C2=A0 =
76</div><div><br></div><div>It should say:</div><div><br></div><div>Length<=
/div><div>=C2=A0=C2=A0</div><div>=C2=A0 =C2=A0 =C2=A036 plus the length of =
the 2 MAC fields</div><div><br></div><div>Section 4.2.13. Says:</div><br>=
=C2=A0 =C2=A0EMSK Compound MAC<br><br>=C2=A0 =C2=A0 =C2=A0 The EMSK Compoun=
d MAC field is 20 octets.=C2=A0 This can be the Server<br>=C2=A0 =C2=A0 =C2=
=A0 MAC (B1_MAC) or the Client MAC (B2_MAC).=C2=A0 The computation of the<b=
r>=C2=A0 =C2=A0 =C2=A0 MAC is described in Section 5.3.<br><br>=C2=A0 =C2=
=A0MSK Compound MAC<br><br>=C2=A0 =C2=A0 =C2=A0 The MSK Compound MAC field =
is 20 octets.=C2=A0 This can be the Server<br>=C2=A0 =C2=A0 =C2=A0 MAC (B1_=
MAC) or the Client MAC (B2_MAC).=C2=A0 The computation of the<br>=C2=A0 =C2=
=A0 =C2=A0 MAC is described in Section 5.3.<div><br></div><div>It Should Sa=
y:</div><div><br></div><div>=C2=A0 =C2=A0EMSK Compound MAC<br><br>=C2=A0 =
=C2=A0 =C2=A0 The computation of the MAC is described in Section 5.3.=C2=A0=
 This can be=C2=A0</div><div>=C2=A0 =C2=A0 =C2=A0 the Server MAC (B1_MAC) o=
r the Client MAC (B2_MAC). =C2=A0<br><br>=C2=A0 =C2=A0MSK Compound MAC<br><=
br>=C2=A0 =C2=A0 =C2=A0 The computation of the MAC is described in Section =
5.3.=C2=A0 This can be=C2=A0</div><div>=C2=A0 =C2=A0 =C2=A0 the Server MAC =
(B1_MAC) or the Client MAC (B2_MAC). =C2=A0<div></div></div><div><br></div>=
<div>Section 5.3 Says:</div><div><br></div>=C2=A0The Compound MAC computati=
on is as follows:<br><br>=C2=A0 =C2=A0 =C2=A0 CMK =3D CMK[j]<br>=C2=A0 =C2=
=A0 =C2=A0 Compound-MAC =3D MAC( CMK, BUFFER )<br><br>=C2=A0 =C2=A0where j =
is the number of the last successfully executed inner EAP<br>=C2=A0 =C2=A0m=
ethod, MAC is the MAC function negotiated in TLS 1.2 [RFC5246], and<br>=C2=
=A0 =C2=A0BUFFER is created after concatenating these fields in the followi=
ng<br>=C2=A0 =C2=A0order:<br><br>=C2=A0 =C2=A01 =C2=A0The entire Crypto-Bin=
ding TLV attribute with both the EMSK and MSK<br>=C2=A0 =C2=A0 =C2=A0 Compo=
und MAC fields zeroed out.<br><br>=C2=A0 =C2=A02 =C2=A0The EAP Type sent by=
 the other party in the first TEAP message.<div><br></div><div>It Should sa=
y:=C2=A0<br><div><br></div></div><div>=C2=A0The Compound MAC computation is=
 as follows:<br><br>=C2=A0 =C2=A0 =C2=A0 CMK =3D CMK[j]<br>=C2=A0 =C2=A0 =
=C2=A0 Compound-MAC =3D MAC( CMK, BUFFER )<br><br>=C2=A0 =C2=A0where j is t=
he number of the last successfully executed inner EAP<br>=C2=A0 =C2=A0metho=
d, MAC is HMAC [RFC2104] using the hash function negotiated in</div><div>=
=C2=A0 =C2=A0TLS [RFC5246].=C2=A0 The output length is the length of the ou=
tput of the HMAC</div><div>=C2=A0 =C2=A0function.=C2=A0 The BUFFER is creat=
ed after concatenating these fields in=C2=A0</div><div>=C2=A0 =C2=A0the fol=
lowing order:</div><div><br>=C2=A0 =C2=A01 =C2=A0The entire Crypto-Binding =
TLV attribute with both the EMSK and MSK<br>=C2=A0 =C2=A0 =C2=A0 Compound M=
AC fields zeroed out.<br><br>=C2=A0 =C2=A02 =C2=A0The EAP Type sent by the =
other party in the first TEAP message. This<br></div><div>=C2=A0 =C2=A0 =C2=
=A0 =C2=A0is a single octet encoded as (0x37)</div><div><br></div><div>Note=
s:</div><div><br></div><div>This corrects the problem that the MAC output w=
ill vary depending upon the TLS hash function. It clarifies that HMAC is us=
ed with the hash function negotiated in TLS.=C2=A0 =C2=A0It also clarifies =
that the=C2=A0 EAP Type used in the TLS message is the TEAP EAP type encode=
d as a single byte.=C2=A0=C2=A0</div></div>
</blockquote></div>
</blockquote></div></div>

--00000000000074e14705b273c689--


From nobody Sun Oct 25 11:15:59 2020
Return-Path: <joe@salowey.net>
X-Original-To: emu@ietfa.amsl.com
Delivered-To: emu@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id D382F3A0C10 for <emu@ietfa.amsl.com>; Sun, 25 Oct 2020 11:15:57 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.898
X-Spam-Level: 
X-Spam-Status: No, score=-1.898 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, HTML_MESSAGE=0.001, SPF_HELO_NONE=0.001, SPF_PASS=-0.001, URIBL_BLOCKED=0.001] autolearn=unavailable autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (2048-bit key) header.d=salowey-net.20150623.gappssmtp.com
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 99x_BRl4JwfB for <emu@ietfa.amsl.com>; Sun, 25 Oct 2020 11:15:55 -0700 (PDT)
Received: from mail-qk1-x72b.google.com (mail-qk1-x72b.google.com [IPv6:2607:f8b0:4864:20::72b]) (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 3338C3A0C01 for <emu@ietf.org>; Sun, 25 Oct 2020 11:15:55 -0700 (PDT)
Received: by mail-qk1-x72b.google.com with SMTP id j129so2531233qke.5 for <emu@ietf.org>; Sun, 25 Oct 2020 11:15:55 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=salowey-net.20150623.gappssmtp.com; s=20150623; h=mime-version:from:date:message-id:subject:to:cc; bh=RdzLe4DVv1Dkp5lJY85PTAqxfGM3xhSW1JsUNY5xAAU=; b=GVNqmPKdT1KFGC7epbulPmoVk8s3q5wgAsVY7RMRJBcKA5aNjKg1SZUfI4OLGRRo3E 9mdwOORfPqyczTEmtHn4ozGYlKEkfssvjHBFnFDMKvHt2XZbAD8LcVQV6o8BxN+y/EIk G2bmwl29zF6fR4t/FbJF+P5ue4Cf9nGcAGokAfXLCEihmStpne2gtk3lIHK2Yn3qOmdY 6vOYqNvWYK2NI4vWUdnDNHbKgrOuq6g1T8KgwsBUzU4ZTFNl6eW+ace4vWFh5TPfY2Av 1mtr7WnEKX0mDbK55SVsDPruKPJS81C7GnNd9bUPq+jjXze/74NUETkSdPzenRWlLT9H aGkA==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:mime-version:from:date:message-id:subject:to:cc; bh=RdzLe4DVv1Dkp5lJY85PTAqxfGM3xhSW1JsUNY5xAAU=; b=dOljxBdEyeDIItaaMuuxmkQWqsqqF42ITg+ucwawgovGaCrgY8W+i6DSUOm8/oN7Bj 09xe6w9HVNTwXFxjKRy0EUJIZgg+VdKX2l3oFqBpscosISpeAen4rLgtgU2H/CHE9KxV Ffh8uJs2MYriCzUvVO1vDOvXxH3TB+gZEr++0Ycm1Zvh1Dm4iNnXhcNhgqgvuYU8MO6r dN7Ppd1d6hQPTMq59zplMR1c7a+tY2h9yvfqWvrg8qamGAuIVIGVZfsuF4uXeXMPK8uR vszicOsb+VG7UruVd+1G0y12/vL/wT0jJQJp0JayOnK9ibnJRPPFhgr3PR3+cHsfBS2z /zIw==
X-Gm-Message-State: AOAM532Refz4BPAQGVSiWUAbJt2F5TtoPwfH/ugp4rwdJYl1RjpZGcZO pEjLk2FNfvM5fIzuE4o4jcqGEKgUDtzGbbwatVqRxS64KGKKijhg
X-Google-Smtp-Source: ABdhPJxtWuEGHeYlTnuM/EpWKeXOCGYdnKJdYLvIUi6EGzDkVYGQfegOvGxloWJLu/fh14QEh8H5U6EfBIECDX3n5MY=
X-Received: by 2002:a37:a0d7:: with SMTP id j206mr11310063qke.375.1603649753806;  Sun, 25 Oct 2020 11:15:53 -0700 (PDT)
MIME-Version: 1.0
From: Joseph Salowey <joe@salowey.net>
Date: Sun, 25 Oct 2020 11:15:42 -0700
Message-ID: <CAOgPGoBO161S5su8J8Tt8tazYMNWp83T2MdkLFDQ4y2ZvbcaNw@mail.gmail.com>
To: EMU WG <emu@ietf.org>
Cc: Jouni Malinen <j@w1.fi>, Jorge Vergara <jovergar=40microsoft.com@dmarc.ietf.org>,  Oleg Pekar <oleg.pekar.2017@gmail.com>
Content-Type: multipart/alternative; boundary="000000000000eb8de205b282cd4d"
Archived-At: <https://mailarchive.ietf.org/arch/msg/emu/N8kFvWmB46Li0W2oJMjNtwarXJY>
Subject: [Emu] Proposed resolution for TEAP errata 5775
X-BeenThere: emu@ietf.org
X-Mailman-Version: 2.1.29
Precedence: list
List-Id: "EAP Methods Update \(EMU\)" <emu.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/emu>, <mailto:emu-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/emu/>
List-Post: <mailto:emu@ietf.org>
List-Help: <mailto:emu-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/emu>, <mailto:emu-request@ietf.org?subject=subscribe>
X-List-Received-Date: Sun, 25 Oct 2020 18:15:58 -0000

--000000000000eb8de205b282cd4d
Content-Type: text/plain; charset="UTF-8"

Errata 5775: https://www.rfc-editor.org/errata/eid5775
Proposed Status: Verified
Revision:

Section 5.2 Says:

    S-IMCK[j] = first 40 octets of IMCK[j]
    CMK[j] = last 20 octets of IMCK[j]

where TLS-PRF is the PRF negotiated as part of TLS handshake [RFC5246].

It Should say:

    S-IMCK[j] = first 40 octets of IMCK[j]
    CMK[j] = last 20 octets of IMCK[j]

where TLS-PRF is the PRF negotiated as part of TLS handshake [RFC5246].
If no inner EAP method has been run the S-IMCK and CMK are generated as
above from S-IMCK[0].

Section 4.2.13 Says:

The Crypto-Binding TLV MUST be exchanged and verified before the
 final Result TLV exchange, regardless of whether there is an inner
 EAP method authentication or not.  It MUST be included with the
 Intermediate-Result TLV to perform cryptographic binding after each
 successful EAP method in a sequence of EAP methods, before proceeding
 with another inner EAP method.  The Crypto-Binding TLV is valid only
 if the following checks pass:

It should say:

 The Crypto-Binding TLV MUST be exchanged and verified before the
 final Result TLV exchange, regardless of whether there is an inner
 EAP method authentication or not.  If an inner EAP method is not
 executed with successful authentication then the EMSK Compound MAC
 field contains the MAC using keys generated according to section 5.2.
 It MUST be included with the Intermediate-Result TLV to perform
 cryptographic binding after each successful EAP method in a sequence
 of EAP methods, before proceeding with another inner EAP method.  The
 Crypto-Binding TLV is valid only if the following checks pass:

Notes:

How to calculate the CMK and other keys when no inner method was run was
unspecified.  This revision specifies that the CMK is generated from
S-IMSK[0]
and the MAC goes into the EMSK field.

--000000000000eb8de205b282cd4d
Content-Type: text/html; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable

<div dir=3D"ltr">Errata 5775:=C2=A0<a href=3D"https://www.rfc-editor.org/er=
rata/eid5775">https://www.rfc-editor.org/errata/eid5775</a><div>Proposed St=
atus: Verified</div><div>Revision:</div><div><br></div><div>Section 5.2 Say=
s:</div><div><br></div>=C2=A0 =C2=A0 S-IMCK[j] =3D first 40 octets of IMCK[=
j]=C2=A0<div>=C2=A0 =C2=A0 CMK[j] =3D last 20 octets of IMCK[j]=C2=A0</div>=
<div><br></div><div>where TLS-PRF is the PRF negotiated as part of TLS hand=
shake [RFC5246].=C2=A0=C2=A0</div><div><br></div><div>It Should say:</div><=
div>=C2=A0 =C2=A0=C2=A0</div><div>=C2=A0 =C2=A0 S-IMCK[j] =3D first 40 octe=
ts of IMCK[j]=C2=A0<div>=C2=A0 =C2=A0 CMK[j] =3D last 20 octets of IMCK[j]=
=C2=A0</div><div><br></div><div>where TLS-PRF is the PRF negotiated as part=
 of TLS handshake [RFC5246].=C2=A0=C2=A0</div></div><div>If no inner EAP me=
thod has been run the S-IMCK and CMK are generated as</div><div>above from =
S-IMCK[0].</div><div><br></div><div>Section 4.2.13 Says:</div><br>The Crypt=
o-Binding TLV MUST be exchanged and verified before the<br>=C2=A0final Resu=
lt TLV exchange, regardless of whether there is an inner<br>=C2=A0EAP metho=
d authentication or not.=C2=A0 It MUST be included with the<br>=C2=A0Interm=
ediate-Result TLV to perform cryptographic binding after each<br>=C2=A0succ=
essful EAP method in a sequence of EAP methods, before proceeding<br>=C2=A0=
with another inner EAP method.=C2=A0 The Crypto-Binding TLV is valid only<b=
r>=C2=A0if the following checks pass:<div></div><div><br></div><div><div>It=
 should say:</div><br>=C2=A0The Crypto-Binding TLV MUST be exchanged and ve=
rified before the<br>=C2=A0final Result TLV exchange, regardless of whether=
 there is an inner<br>=C2=A0EAP method authentication or not.=C2=A0 If an i=
nner EAP method is not=C2=A0</div><div>=C2=A0executed with successful authe=
ntication then the EMSK Compound MAC=C2=A0</div><div>=C2=A0field contains t=
he MAC using keys generated according to section 5.2.=C2=A0</div><div>=C2=
=A0It MUST be included with the Intermediate-Result TLV to perform=C2=A0</d=
iv><div>=C2=A0cryptographic binding after each successful EAP method in a s=
equence</div><div>=C2=A0of EAP methods, before proceeding=C2=A0with another=
 inner EAP method.=C2=A0 The</div><div>=C2=A0Crypto-Binding TLV is valid on=
ly if the following checks pass:<br></div><div><br></div><div>Notes:</div><=
div><br></div><div>How to calculate the CMK and other keys when no inner me=
thod was run was</div><div>unspecified.=C2=A0 This revision specifies that =
the CMK is generated from S-IMSK[0]</div><div>and the MAC goes into the EMS=
K field.</div></div>

--000000000000eb8de205b282cd4d--


From nobody Sun Oct 25 12:10:57 2020
Return-Path: <joe@salowey.net>
X-Original-To: emu@ietfa.amsl.com
Delivered-To: emu@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 797443A152D for <emu@ietfa.amsl.com>; Sun, 25 Oct 2020 12:10:55 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.898
X-Spam-Level: 
X-Spam-Status: No, score=-1.898 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, HTML_MESSAGE=0.001, SPF_HELO_NONE=0.001, SPF_PASS=-0.001, URIBL_BLOCKED=0.001] autolearn=unavailable autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (2048-bit key) header.d=salowey-net.20150623.gappssmtp.com
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 yM3ORqWReahm for <emu@ietfa.amsl.com>; Sun, 25 Oct 2020 12:10:54 -0700 (PDT)
Received: from mail-qk1-x72f.google.com (mail-qk1-x72f.google.com [IPv6:2607:f8b0:4864:20::72f]) (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 DF3F43A152E for <emu@ietf.org>; Sun, 25 Oct 2020 12:10:53 -0700 (PDT)
Received: by mail-qk1-x72f.google.com with SMTP id b69so6437675qkg.8 for <emu@ietf.org>; Sun, 25 Oct 2020 12:10:53 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=salowey-net.20150623.gappssmtp.com; s=20150623; h=mime-version:from:date:message-id:subject:to:cc; bh=JqevzHUS957a66aVROR48THghl6iirdowD50WXpvarA=; b=ZLXLfACuvAgvxAEJGk/rhu3u6e1cU6Y0tL59gddaX9tMhRXHQTickqR/7GR9N1r+LC syH0tfmW6DiwlkqH2E2ICh6S337UDjczKh/6xSm+ozO0tubdxvvmbYvcLD2EzxgpSDgj DeBpRldu07RvBnn0bx86WGe6SSrpxIcl7yMGKIHfFmpTv1xbs3TI15i/FM7wRJndg7xi haBp6McduMUaM7mxeVa4hfodeUTLzffcf9Ruk6jcgA9XJhIsRHwCKMtEWsCXBBIKhPpm Pk+Borcca8WZNmykcFHk+e0BBtUAw0aK6QoNCRiSYoesjhKRNO+trmIrUYzcts+OHpb0 wvnw==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:mime-version:from:date:message-id:subject:to:cc; bh=JqevzHUS957a66aVROR48THghl6iirdowD50WXpvarA=; b=ixaoKq2r1fDY+G47L6PMXlYr6wz1FqjN5ic3M4PY8tYIaumKhXcxkasdVN6hRvOV3e 10YEgGKeNsdVGrEX7f/kKKQa7NqjvVR3SY+iW/jEaZrPjCQR8dnTgREYN01Z1N1+3PxU ylhVhJna8PiHwNCv7YJUn2rEkobo1kNtajOeT8YPIam+8Ue324TPnzTniJf+ZDF/1bxy Nua2P0QaQSGsOQ4DSbcpkBQiDf51ediI769qk9LcXeLDy89FwR9iKooTGlBVMcW9k+A4 NCa2v6jduuPHCAMvov4GuN9dyFppgN5NRrKpm0nEurdUR4FyLH0oIoRCn07E53tq0tcH z1cA==
X-Gm-Message-State: AOAM531un+b4G8/6U+iDITybLl/oA0J4gqySFXOgwakDsM6CVqmFRwe6 TBg+dt+m27HdkuWYwr5FbaMp2O2yr7OuXkGPG3hmtRPlgIXf6CMP
X-Google-Smtp-Source: ABdhPJxF5vef16wF4BPTumXa/KmlVIioYGedScUK2K81UoJdLyAClW2MPl6c8LeY3nymkukalV8sMkinHV9HFaVxXsQ=
X-Received: by 2002:a37:a0d7:: with SMTP id j206mr11472372qke.375.1603653052595;  Sun, 25 Oct 2020 12:10:52 -0700 (PDT)
MIME-Version: 1.0
From: Joseph Salowey <joe@salowey.net>
Date: Sun, 25 Oct 2020 12:10:41 -0700
Message-ID: <CAOgPGoDfmCJwnZJLqeyXD0+X_aeqXXkiZZOo2WYP4SC0D67HQw@mail.gmail.com>
To: EMU WG <emu@ietf.org>
Cc: Jouni Malinen <j@w1.fi>, Jorge Vergara <jovergar=40microsoft.com@dmarc.ietf.org>,  Oleg Pekar <oleg.pekar.2017@gmail.com>
Content-Type: multipart/alternative; boundary="0000000000008b18e705b2839299"
Archived-At: <https://mailarchive.ietf.org/arch/msg/emu/csnucI4zAzCxoZ28QeixSOnYuG4>
Subject: [Emu] Proposed Resolution to TEAP Errata 5844
X-BeenThere: emu@ietf.org
X-Mailman-Version: 2.1.29
Precedence: list
List-Id: "EAP Methods Update \(EMU\)" <emu.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/emu>, <mailto:emu-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/emu/>
List-Post: <mailto:emu@ietf.org>
List-Help: <mailto:emu-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/emu>, <mailto:emu-request@ietf.org?subject=subscribe>
X-List-Received-Date: Sun, 25 Oct 2020 19:10:55 -0000

--0000000000008b18e705b2839299
Content-Type: text/plain; charset="UTF-8"

Errata 5844: https://www.rfc-editor.org/errata/eid5844
Status: Verified
Revision:

Section 3.3.2 says:

Upon receiving the response, the server
   indicates the success or failure of the exchange using an
   Intermediate-Result TLV.

It Should say:

Upon receiving the response, the server MUST
   indicate the success or failure of the exchange using an
   Intermediate-Result TLV.

Section 3.6 says:

3. The Intermediate-Result TLVs carry success or failure indications of the
individual EAP methods in TEAP Phase 2.

It Should say:

3. The Intermediate-Result TLVs carry success or failure indications of the
individual EAP methods and basic password authentication in TEAP Phase 2.

Section 4.2.11 says:

The Intermediate-Result TLV provides support for acknowledged intermediate
Success and Failure messages between multiple inner EAP methods within EAP.

It Should say:

The Intermediate-Result TLV provides support for acknowledged intermediate
Success and Failure messages between multiple inner EAP methods or basic
password authentication within EAP.

Section C.1 says:

                            <- Crypto-Binding TLV (Request),
                                Result TLV (Success),
                                (Optional PAC TLV)

       Crypto-Binding TLV(Response),
       Result TLV (Success),
       (PAC-Acknowledgement TLV) ->

It should say:

                            <- Intermediate-Result-TLV (Success),
                                Crypto-Binding TLV (Request),
                                Result TLV (Success),
                                (Optional PAC TLV)

       Intermediate-Result-TLV (Success),
       Crypto-Binding TLV(Response),
       Result TLV (Success),
       (PAC-Acknowledgement TLV) ->

Section C.2 Says:
                <- Result TLV (Failure)

            Result TLV (Failure) ->

It Should Say:

                <- Intermediate-Result-TLV (Failure),
                     Result TLV (Failure)

            Intermediate-Result-TLV (Failure),
       Result TLV (Failure) ->


Notes:

Section 3.3.2 implies that Intermediate-Result TLV is used after each round
of Basic-Password-Auth-Req/Resp TLVs. However, the example sequence in C.1
does not show this. The proposed change in this errata adds the
Intermediate-Result TLV indication here. Similar change should be done in
C.2 (i.e., add Intermediate-Result TLV (Failure) to the messages that
include Result TLV) since the language in 3.3.2 describe the indication to
be used for both success and failure cases.

In addition to this change in C.1, it would be good to clarify the
specification globally to avoid confusion about this case since almost all
discussion regarding Intermediate-Result TLV currently is in the context of
inner EAP authentication. 3.3.2 should have a MUST statement similar to
3.3.1. 3.6 should cover success or failure indications of basic password
auth like it does EAP methods. 4.2.11 should note Intermediate-Result TLV
is used with both inner EAP and basic password auth.

--0000000000008b18e705b2839299
Content-Type: text/html; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable

<div dir=3D"ltr">Errata 5844:=C2=A0<a href=3D"https://www.rfc-editor.org/er=
rata/eid5844">https://www.rfc-editor.org/errata/eid5844</a><div>Status: Ver=
ified</div><div>Revision:</div><div><br></div><div>Section 3.3.2 says:</div=
><div><br></div>Upon receiving the response, the server<br>=C2=A0 =C2=A0ind=
icates the success or failure of the exchange using an<br>=C2=A0 =C2=A0Inte=
rmediate-Result TLV.<div><br></div><div>It Should say:</div><div><br></div>=
<div>Upon receiving the response, the server MUST<br>=C2=A0 =C2=A0indicate =
the success or failure of the exchange using an<br>=C2=A0 =C2=A0Intermediat=
e-Result TLV.<br></div><div><br></div><div>Section 3.6 says:</div><div><br>=
</div>3. The Intermediate-Result TLVs carry success or failure indications =
of the individual EAP methods in TEAP Phase 2.<div><br></div><div>It Should=
 say:</div><div><br></div><div>3. The Intermediate-Result TLVs carry succes=
s or failure indications of the individual EAP methods and basic=C2=A0passw=
ord authentication in TEAP Phase 2.<br></div><div><br><div>Section 4.2.11 s=
ays:</div><div><br></div>The Intermediate-Result TLV provides support for a=
cknowledged intermediate Success and Failure messages between multiple inne=
r EAP methods within EAP.</div><div><br></div><div>It Should say:</div><div=
><br></div><div>The Intermediate-Result TLV provides support for acknowledg=
ed intermediate Success and Failure messages between multiple inner EAP met=
hods or basic password authentication within EAP.<br><div><br></div><div>Se=
ction C.1 says:<br><br>=C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=
=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 &lt;- Crypto-Binding TLV (Req=
uest),<br>=C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =
=C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 Result TLV (Success),<br>=
=C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=
=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 (Optional PAC TLV)<br><br>=C2=A0 =C2=
=A0 =C2=A0 =C2=A0Crypto-Binding TLV(Response),<br>=C2=A0 =C2=A0 =C2=A0 =C2=
=A0Result TLV (Success),<br>=C2=A0 =C2=A0 =C2=A0 =C2=A0(PAC-Acknowledgement=
 TLV) -&gt;<br><br>It should say:<br><br>=C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0=
 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 &lt;- Inter=
mediate-Result-TLV (Success),<br>=C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =
=C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 Crypt=
o-Binding TLV (Request),<br>=C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=
=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 Result T=
LV (Success),<br>=C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =
=C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 (Optional PAC TLV)<=
br><br>=C2=A0 =C2=A0 =C2=A0 =C2=A0Intermediate-Result-TLV (Success),<br>=C2=
=A0 =C2=A0 =C2=A0 =C2=A0Crypto-Binding TLV(Response),<br>=C2=A0 =C2=A0 =C2=
=A0 =C2=A0Result TLV (Success),<br>=C2=A0 =C2=A0 =C2=A0 =C2=A0(PAC-Acknowle=
dgement TLV) -&gt;<div><br></div><div>Section C.2 Says:</div><div>=C2=A0 =
=C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 &lt;- Result TLV (Failure)=
<pre class=3D"gmail-newpage" style=3D"font-size:13.3333px;margin-top:0px;ma=
rgin-bottom:0px;break-before:page;color:rgb(0,0,0)"></pre><pre class=3D"gma=
il-newpage" style=3D"font-size:13.3333px;margin-top:0px;margin-bottom:0px;b=
reak-before:page;color:rgb(0,0,0)">     </pre>=C2=A0 =C2=A0 =C2=A0 =C2=A0Re=
sult TLV (Failure) -&gt;</div><div><br></div><div>It Should Say:</div><div>=
<br></div><div>=C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 &lt;=
- Intermediate-Result-TLV (Failure),<br>=C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =
=C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0Result TLV (Failure)<pre class=3D"=
gmail-newpage" style=3D"font-size:13.3333px;margin-top:0px;margin-bottom:0p=
x;break-before:page;color:rgb(0,0,0)"></pre><pre class=3D"gmail-newpage" st=
yle=3D"font-size:13.3333px;margin-top:0px;margin-bottom:0px;break-before:pa=
ge;color:rgb(0,0,0)">     </pre>=C2=A0 =C2=A0 =C2=A0 =C2=A0Intermediate-Res=
ult-TLV (Failure),=C2=A0<br>=C2=A0 =C2=A0 =C2=A0 =C2=A0Result TLV (Failure)=
 -&gt;<br><pre class=3D"gmail-newpage" style=3D"font-size:13.3333px;margin-=
top:0px;margin-bottom:0px;break-before:page;color:rgb(0,0,0)"></pre><pre cl=
ass=3D"gmail-newpage" style=3D"font-size:13.3333px;margin-top:0px;margin-bo=
ttom:0px;break-before:page;color:rgb(0,0,0)"><br></pre>Notes: <br><br>Secti=
on 3.3.2 implies that Intermediate-Result TLV is used after each round of B=
asic-Password-Auth-Req/Resp TLVs. However, the example sequence in C.1 does=
 not show this. The proposed change in this errata adds the Intermediate-Re=
sult TLV indication here. Similar change should be done in C.2 (i.e., add I=
ntermediate-Result TLV (Failure) to the messages that include Result TLV) s=
ince the language in 3.3.2 describe the indication to be used for both succ=
ess and failure cases.</div></div></div><br>In addition to this change in C=
.1, it would be good to clarify the specification globally to avoid confusi=
on about this case since almost all discussion regarding Intermediate-Resul=
t TLV currently is in the context of inner EAP authentication. 3.3.2 should=
 have a MUST statement similar to 3.3.1. 3.6 should cover success or failur=
e indications of basic password auth like it does EAP methods. 4.2.11 shoul=
d note Intermediate-Result TLV is used with both inner EAP and basic passwo=
rd auth.=C2=A0=C2=A0</div>

--0000000000008b18e705b2839299--


From nobody Sun Oct 25 12:14:16 2020
Return-Path: <joe@salowey.net>
X-Original-To: emu@ietfa.amsl.com
Delivered-To: emu@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 59EEA3A1531 for <emu@ietfa.amsl.com>; Sun, 25 Oct 2020 12:14:14 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.898
X-Spam-Level: 
X-Spam-Status: No, score=-1.898 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, HTML_MESSAGE=0.001, SPF_HELO_NONE=0.001, SPF_PASS=-0.001, URIBL_BLOCKED=0.001] autolearn=unavailable autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (2048-bit key) header.d=salowey-net.20150623.gappssmtp.com
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 F14iD92po7E5 for <emu@ietfa.amsl.com>; Sun, 25 Oct 2020 12:14:13 -0700 (PDT)
Received: from mail-qt1-x830.google.com (mail-qt1-x830.google.com [IPv6:2607:f8b0:4864:20::830]) (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 DA7843A152F for <emu@ietf.org>; Sun, 25 Oct 2020 12:14:12 -0700 (PDT)
Received: by mail-qt1-x830.google.com with SMTP id z33so5228552qth.8 for <emu@ietf.org>; Sun, 25 Oct 2020 12:14:12 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=salowey-net.20150623.gappssmtp.com; s=20150623; h=mime-version:from:date:message-id:subject:to:cc; bh=9L2hsAmrt3j09kJbSpI/IbQsWnmZ/pSDV6kZLyEkWSQ=; b=Z751Kvc/rR+4NEsRjjhDdi+IDdRiUvvNA0FqQ2HrezWLTfpSncpYCl2PNNqAt0qy6j 9ocrYLaEbYjgvmq7gOa3m9dyRouyrGGov5PGIUMMII8uaFn8SeqKE+z9xl3iExQOlC1v /AsjFBSxNdun+ykasF5QAz/Dh2TTv9jAPKPnsg9NnSQWQrVxINB9HCraDgtXVK+dsBZL 79hS/yxrqt8/9d6MOfdkxsUopbsXUZfOXt2OqRhYw5UFWioWYPf24NEiqv1U9U76eYX6 O16FJD0btoRD5ttpQn9y6dgYhGLEgvdo0/3tvNaagUH3cJPuweI6VMdEGJZjY4RbaCGE DeRA==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:mime-version:from:date:message-id:subject:to:cc; bh=9L2hsAmrt3j09kJbSpI/IbQsWnmZ/pSDV6kZLyEkWSQ=; b=m2ZvsPBL+wZctyrFlT/Dgp+NUgsIh/BTBFITwqjXDkW5voeIfWhk7Is0ymIquIBdpi GBvd7svjVC2L2WyBV1C9ChTNZ9f6LeyBy43Fg7QEeaPpTrNrmt9TjK3v1UGnw22ABHbR +i6LjNFITOR0Llf72boylFcieBveuP5W4Hu0FTOU0US5kGzDI8KQSIPAWcPbK5N2BzYT m4k9HIcaeqPsXa0n6n0lWgg6AGFIKVrvWMDSqSzSZF03S+as63+m4PcjKj9iMCRmro4L QYK9kkjA5rLH4vYBeSolAf3JxftK71bM6iBsDGHJ82hhGeaXr3p/yaiM9pHUgjS1WSs2 tTHQ==
X-Gm-Message-State: AOAM532FVAvh0Z3LpCnz9vKvJ8khuwyBRsrqAi7mZhOSTXZwUkCfsTFa jlV4y+KMZ+O1Icz9YriuzbEjqI/V/NzGc1rOS5shmvbKRX0MFzSW
X-Google-Smtp-Source: ABdhPJzkyuEQqfwj1ADbLC4tqMblLQ2c9Ak7VSTIYGtxwabcdAivmniIY93p26mgYjEEXrdx4dmmONe5j/y0/+Z2HAU=
X-Received: by 2002:aed:2125:: with SMTP id 34mr9961903qtc.249.1603653251587;  Sun, 25 Oct 2020 12:14:11 -0700 (PDT)
MIME-Version: 1.0
From: Joseph Salowey <joe@salowey.net>
Date: Sun, 25 Oct 2020 12:14:00 -0700
Message-ID: <CAOgPGoBsGEGwC+3Z=uNz5an4ywmiopmakJFDVh4ZW=DRH6uFJg@mail.gmail.com>
To: EMU WG <emu@ietf.org>
Cc: Jouni Malinen <j@w1.fi>, Jorge Vergara <jovergar=40microsoft.com@dmarc.ietf.org>,  Oleg Pekar <oleg.pekar.2017@gmail.com>
Content-Type: multipart/alternative; boundary="0000000000006778ba05b2839e0d"
Archived-At: <https://mailarchive.ietf.org/arch/msg/emu/RU3R6AdjrZd08f6njL37f2thlQE>
Subject: [Emu] Proposed Resolution for Errata 5845
X-BeenThere: emu@ietf.org
X-Mailman-Version: 2.1.29
Precedence: list
List-Id: "EAP Methods Update \(EMU\)" <emu.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/emu>, <mailto:emu-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/emu/>
List-Post: <mailto:emu@ietf.org>
List-Help: <mailto:emu-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/emu>, <mailto:emu-request@ietf.org?subject=subscribe>
X-List-Received-Date: Sun, 25 Oct 2020 19:14:14 -0000

--0000000000006778ba05b2839e0d
Content-Type: text/plain; charset="UTF-8"

Errata 5845: https://www.rfc-editor.org/errata/eid5845
Proposed Status: Verified
Revision:

Section 3.3.1 says:

   EAP method messages are carried within EAP-Payload TLVs defined in
   Section 4.2.10.  If more than one method is going to be executed in
   the tunnel, then upon method completion, the server MUST send an
   Intermediate-Result TLV indicating the result.

It should say:

   EAP method messages are carried within EAP-Payload TLVs defined in
   Section 4.2.10.  Upon method completion, the server MUST send an
   Intermediate-Result TLV indicating the result.

Notes:

Description of whether Intermediate-Result TLV is supposed to be used in
the case where only a single inner EAP authentication method is used.
Section 3.3.1 says "more than one method is going to be executed in the
tunnel, then upon method completion, the server MUST send an
Intermediate-Result TLV indicating the result", Section 3.3.3 says "The
Crypto-Binding TLV and Intermediate-Result TLV MUST be included to perform
cryptographic binding after each successful EAP method in a sequence of one
or more EAP methods", 4.2.13 says "It MUST be included with the
Intermediate-Result TLV to perform cryptographic binding after each
successful EAP method in a sequence of EAP methods", Annex C.3 shows an
example exchange with a single inner EAP authentication method with use of
Intermediate-Result TLV.

It looks like the majority of the places discussion this topic implies that
there is going to be an Intermediate-Result TLV after each inner EAP
authentication method and the text in 3.3.1 is the only clear case of
conflicting (or well, at least misleading if one were to claim it does not
explicitly say MUST NOT for the one inner EAP authentication method case).
As such, I'd conclude the Intermediate-Result TLV is indeed going to be
exchanged after each EAP authentication method and the proposed text change
to 3.3.1 covers that.

--0000000000006778ba05b2839e0d
Content-Type: text/html; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable

<div dir=3D"ltr">Errata 5845:=C2=A0<a href=3D"https://www.rfc-editor.org/er=
rata/eid5845">https://www.rfc-editor.org/errata/eid5845</a><div>Proposed St=
atus: Verified</div><div>Revision:</div><br>Section 3.3.1 says:<br><br>=C2=
=A0 =C2=A0EAP method messages are carried within EAP-Payload TLVs defined i=
n<br>=C2=A0 =C2=A0Section 4.2.10.=C2=A0 If more than one method is going to=
 be executed in<br>=C2=A0 =C2=A0the tunnel, then upon method completion, th=
e server MUST send an<br>=C2=A0 =C2=A0Intermediate-Result TLV indicating th=
e result.<br><br>It should say:<br><br>=C2=A0 =C2=A0EAP method messages are=
 carried within EAP-Payload TLVs defined in<br>=C2=A0 =C2=A0Section 4.2.10.=
=C2=A0 Upon method completion, the server MUST send an<br>=C2=A0 =C2=A0Inte=
rmediate-Result TLV indicating the result.<div><br></div>Notes:<br><br>Desc=
ription of whether Intermediate-Result TLV is supposed to be used in the ca=
se where only a single inner EAP authentication method is used. Section 3.3=
.1 says &quot;more than one method is going to be executed in the tunnel, t=
hen upon method completion, the server MUST send an Intermediate-Result TLV=
 indicating the result&quot;, Section 3.3.3 says &quot;The Crypto-Binding T=
LV and Intermediate-Result TLV MUST be included to perform cryptographic bi=
nding after each successful EAP method in a sequence of one or more EAP met=
hods&quot;, 4.2.13 says &quot;It MUST be included with the Intermediate-Res=
ult TLV to perform cryptographic binding after each successful EAP method i=
n a sequence of EAP methods&quot;, Annex C.3 shows an example exchange with=
 a single inner EAP authentication method with use of Intermediate-Result T=
LV.<br><br>It looks like the majority of the places discussion this topic i=
mplies that there is going to be an Intermediate-Result TLV after each inne=
r EAP authentication method and the text in 3.3.1 is the only clear case of=
 conflicting (or well, at least misleading if one were to claim it does not=
 explicitly say MUST NOT for the one inner EAP authentication method case).=
 As such, I&#39;d conclude the Intermediate-Result TLV is indeed going to b=
e exchanged after each EAP authentication method and the proposed text chan=
ge to 3.3.1 covers that.</div>

--0000000000006778ba05b2839e0d--


From nobody Sun Oct 25 12:16:51 2020
Return-Path: <joe@salowey.net>
X-Original-To: emu@ietfa.amsl.com
Delivered-To: emu@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id BE7FA3A1538 for <emu@ietfa.amsl.com>; Sun, 25 Oct 2020 12:16:49 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.898
X-Spam-Level: 
X-Spam-Status: No, score=-1.898 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, HTML_MESSAGE=0.001, SPF_HELO_NONE=0.001, SPF_PASS=-0.001, URIBL_BLOCKED=0.001] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (2048-bit key) header.d=salowey-net.20150623.gappssmtp.com
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 iTd-xz6qvrgM for <emu@ietfa.amsl.com>; Sun, 25 Oct 2020 12:16:48 -0700 (PDT)
Received: from mail-qk1-x729.google.com (mail-qk1-x729.google.com [IPv6:2607:f8b0:4864:20::729]) (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 162C33A1537 for <emu@ietf.org>; Sun, 25 Oct 2020 12:16:48 -0700 (PDT)
Received: by mail-qk1-x729.google.com with SMTP id k9so6465187qki.6 for <emu@ietf.org>; Sun, 25 Oct 2020 12:16:48 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=salowey-net.20150623.gappssmtp.com; s=20150623; h=mime-version:from:date:message-id:subject:to:cc; bh=CUSurxlbmJiA3+mnaOw7nBA9vULlgTCxNVWaqJrsFHQ=; b=Lh7fDs8/9E8c8yjTM35GZDoEEOyecxdHf/bfdrZj0MlXTNrOb+NxphzGmxj+IVNxG1 AE0kmJUsdy6E50Bc79meQEr5GLubfJst9bhgNzahg7cfvOvACrxMGfWFfh3swJvZB7Vn dX7WP3ce6+unbiNB+X4NzQypK6LjqoHi/OM7OW2qL8CVrJZTQBUWHDHCrSUZ2ap2jfKD Blq85zBKB8v2xUzjydLiDRRenGjd0awcEU4HLZcwwJ7s3ZkmniF+Ujo9AHgoRPWnnr3w uKHhlh8qIw/GXte6QqiGHMApM4a1eRG2q0wG0iyR34rUx7QrxABuTwDkl2uoCiUFcmpU BMTQ==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:mime-version:from:date:message-id:subject:to:cc; bh=CUSurxlbmJiA3+mnaOw7nBA9vULlgTCxNVWaqJrsFHQ=; b=hi3q0iEBoKA3x251NsKNCdFd0tyBZY83ZXxM+RuBKG4eBAiyIBaSK+s+ELT0V6D0iA 0qYJbBNr4TdwkGqY0z6jGizk7EfMaBOg2TAea+l5GJV+vQ30Y3jS13toCeUrpghJefkd 94JeOpPf+xkH7Ng6O1fIYFkNJYFI/FtQL8BjILP2D4DJPieXxQgwTFpiTkszyRMfdJjs uFCa6ZeRerteChuUPVLYDCBb7/ImrLc1ZYWDkhfHwD3S7/uctsmUYfSi8MwtP4KOG3zy HJdLdyVgYsD8mP8FY7WrI0EchKXVZKF/vu1GB0QaTwmoBm2JGIttoeW8kKvBQbyQf/Sd MgQw==
X-Gm-Message-State: AOAM533AHoC+XqeaGdr9hLUu2MXQUVjc1eLOXxzKXIZLtVrv/LXsXouo FWsQKKar9Y2MUibzVny10D4wStsJMyC0Iw+EWboLbrJ4PB33W0on
X-Google-Smtp-Source: ABdhPJxIJbNRINu9kIM03/VNkh1j6ovQPbGFh4moDawb5ftvO1VOmU7Vjv9sUl72yOTZaIgVlGdEuiYdevGMy2X6qAY=
X-Received: by 2002:a37:9b04:: with SMTP id d4mr11966826qke.472.1603653406963;  Sun, 25 Oct 2020 12:16:46 -0700 (PDT)
MIME-Version: 1.0
From: Joseph Salowey <joe@salowey.net>
Date: Sun, 25 Oct 2020 12:16:36 -0700
Message-ID: <CAOgPGoCUECBQG7JhBEtGnynKfUq+3Or3Vn5D5PgXsbx1dscvBw@mail.gmail.com>
To: EMU WG <emu@ietf.org>
Content-Type: multipart/alternative; boundary="000000000000aa507305b283a779"
Archived-At: <https://mailarchive.ietf.org/arch/msg/emu/t1HhhUL0QFgBmgAFYRMRkKXWXaA>
Subject: [Emu] Proposed Resolution for TEAP Errata 6157
X-BeenThere: emu@ietf.org
X-Mailman-Version: 2.1.29
Precedence: list
List-Id: "EAP Methods Update \(EMU\)" <emu.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/emu>, <mailto:emu-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/emu/>
List-Post: <mailto:emu@ietf.org>
List-Help: <mailto:emu-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/emu>, <mailto:emu-request@ietf.org?subject=subscribe>
X-List-Received-Date: Sun, 25 Oct 2020 19:16:50 -0000

--000000000000aa507305b283a779
Content-Type: text/plain; charset="UTF-8"

Errata 6157: https://www.rfc-editor.org/errata/eid6157
Proposed Status: Verified
Revision:
Section 4.2.9 says:

  Status

      The Status field is one octet.  This indicates the result if the
      server does not process the action requested by the peer.

It should say:

  Status

      The Status field is one octet.  This indicates the result if the
      party who receives this TLV does not process the action.

Notes:

The status field is carried in the "Request-Action" frame. As is repeatedly
stated in the chapeau of the section, the frame can be sent either by the
server or the peer.

--000000000000aa507305b283a779
Content-Type: text/html; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable

<div dir=3D"ltr">Errata 6157:=C2=A0<a href=3D"https://www.rfc-editor.org/er=
rata/eid6157">https://www.rfc-editor.org/errata/eid6157</a><div>Proposed St=
atus: Verified</div><div>Revision:</div>Section 4.2.9 says:<br><br>=C2=A0 S=
tatus<br><br>=C2=A0 =C2=A0 =C2=A0 The Status field is one octet.=C2=A0 This=
 indicates the result if the<br>=C2=A0 =C2=A0 =C2=A0 server does not proces=
s the action requested by the peer.<br><br>It should say:<br><br>=C2=A0 Sta=
tus<br><br>=C2=A0 =C2=A0 =C2=A0 The Status field is one octet.=C2=A0 This i=
ndicates the result if the<br>=C2=A0 =C2=A0 =C2=A0 party who receives this =
TLV does not process the action.<br><br>Notes:<br><br>The status field is c=
arried in the &quot;Request-Action&quot; frame. As is repeatedly stated in =
the chapeau of the section, the frame can be sent either by the server or t=
he peer.</div>

--000000000000aa507305b283a779--


From nobody Mon Oct 26 01:25:35 2020
Return-Path: <oleg.pekar.2017@gmail.com>
X-Original-To: emu@ietfa.amsl.com
Delivered-To: emu@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id D61E63A19BB for <emu@ietfa.amsl.com>; Mon, 26 Oct 2020 01:25:32 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.848
X-Spam-Level: 
X-Spam-Status: No, score=-1.848 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, DKIM_VALID_EF=-0.1, FREEMAIL_ENVFROM_END_DIGIT=0.25, FREEMAIL_FROM=0.001, HTML_MESSAGE=0.001, SPF_HELO_NONE=0.001, SPF_PASS=-0.001] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (2048-bit key) header.d=gmail.com
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 xtwu1VYBYya5 for <emu@ietfa.amsl.com>; Mon, 26 Oct 2020 01:25:31 -0700 (PDT)
Received: from mail-ot1-x332.google.com (mail-ot1-x332.google.com [IPv6:2607:f8b0:4864:20::332]) (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 B48CC3A14AB for <emu@ietf.org>; Mon, 26 Oct 2020 01:25:31 -0700 (PDT)
Received: by mail-ot1-x332.google.com with SMTP id n11so7276847ota.2 for <emu@ietf.org>; Mon, 26 Oct 2020 01:25:31 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20161025;  h=mime-version:references:in-reply-to:from:date:message-id:subject:to :cc; bh=TaMX/VtrxiXW/h/z1Hqcw+2s4Pn5meU2L+CgEKtxbRE=; b=XqFmug2oXzrdSDUa2HJLwUeXL+3JuMpbd4YCTfus7E42dDeoNEZ1SzVf0i0jxzn2L8 s1vYBMJHwclmPmY6tLBPFnHkrMQuxPs172OIYDUNl/SstOdY9mjCAhLEfp2BCDcI63d6 dav8HyTQBmRfpF5JtXeciPATNuz7pg1u9rUx+56GYvPpCgkyRSsuH4wJtsTN/lwmZ3W0 IVOUoTYdGOMHnBhV9eMPsiGkbFbLUZs/vUM+cuSHl+TYv0cKWys95MVFOPaEUXiOAi2p W0RxgM2kLn9kzi3cZftRP6gLFUUJHRgU/hwoKAQwnFF6aXsVtJrCgoPOqx9FMlXCgmYK ggww==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:mime-version:references:in-reply-to:from:date :message-id:subject:to:cc; bh=TaMX/VtrxiXW/h/z1Hqcw+2s4Pn5meU2L+CgEKtxbRE=; b=THbnyMYccS+b2XjZHmRnRn0weozKCWbV7CLQuSDRe+CW6cWEiIJtkq/r9v0VSL8U2K KZVj7g70txK13utLwjlRm7cuJo6rGG+Os9QJhglFbPfkPe+tJzKrAGMGhQrp827E1RQH q/wZP5N61iHK5q4bl0U1XUMMRDjjcXkR+UegSjNbsYQsAq1r3vGTCsfYwM8lv9vHzjtR r8vEr/IdGlQoxqAhdqiWwO9iwCfuIekJTB60YtyjIm4GLtVI2xWZLJM8290iqKVoEWaY eBFlYAc6ov2Iw+8zJVxRXqC9WoW+VAQJFTqJukJDpnuys0cyHrgcu2dOJJ/9nCLmcAco N9Lg==
X-Gm-Message-State: AOAM5331ekCLt4HXMrr3HCdky4XrcsRT16hTV0UxZozRCA9vXBcnjFCR c1BQMjYWrzI6gamaZUMOE4hYYkwASy5cHuMvpTdyXwWYJmNrBQ==
X-Google-Smtp-Source: ABdhPJwowjCgZO2LRoCZXs6HciaXxDq/cUn0KWpP0PS8XAfLE/BF4y50HqtOGoCY8ABhDKtY3jVlwNSG2/YDOrnFbhc=
X-Received: by 2002:a9d:5547:: with SMTP id h7mr13894506oti.248.1603700730953;  Mon, 26 Oct 2020 01:25:30 -0700 (PDT)
MIME-Version: 1.0
References: <CAOgPGoBO161S5su8J8Tt8tazYMNWp83T2MdkLFDQ4y2ZvbcaNw@mail.gmail.com>
In-Reply-To: <CAOgPGoBO161S5su8J8Tt8tazYMNWp83T2MdkLFDQ4y2ZvbcaNw@mail.gmail.com>
From: Oleg Pekar <oleg.pekar.2017@gmail.com>
Date: Mon, 26 Oct 2020 10:25:19 +0200
Message-ID: <CABXxEz_r+5d+swfkbg2vQ-CRr5KaWcsjwLrAHb00rRA7K_Cb9w@mail.gmail.com>
To: Joseph Salowey <joe@salowey.net>
Cc: EMU WG <emu@ietf.org>, Jouni Malinen <j@w1.fi>,  Jorge Vergara <jovergar=40microsoft.com@dmarc.ietf.org>
Content-Type: multipart/alternative; boundary="0000000000006502f305b28eac85"
Archived-At: <https://mailarchive.ietf.org/arch/msg/emu/uUL0ZvOVsajm6GmkY4ZB2beNKeg>
Subject: Re: [Emu] Proposed resolution for TEAP errata 5775
X-BeenThere: emu@ietf.org
X-Mailman-Version: 2.1.29
Precedence: list
List-Id: "EAP Methods Update \(EMU\)" <emu.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/emu>, <mailto:emu-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/emu/>
List-Post: <mailto:emu@ietf.org>
List-Help: <mailto:emu-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/emu>, <mailto:emu-request@ietf.org?subject=subscribe>
X-List-Received-Date: Mon, 26 Oct 2020 08:25:33 -0000

--0000000000006502f305b28eac85
Content-Type: text/plain; charset="UTF-8"

>
> It Should say:
>
>     S-IMCK[j] = first 40 octets of IMCK[j]
>     CMK[j] = last 20 octets of IMCK[j]
> where TLS-PRF is the PRF negotiated as part of TLS handshake [RFC5246].
> If no inner EAP method has been run the S-IMCK and CMK are generated as
> above from S-IMCK[0].


Joe, for me it still doesn't sound as exact enough instructions. We should
explain how to generate S-IMCK and CMK for no inner method case with more
details.

The Crypto-Binding TLV MUST be exchanged and verified before the
>  final Result TLV exchange, regardless of whether there is an inner
>  EAP method authentication or not.

This still remains an open question whether we MUST send Crypto-Binding TLV
after Basic-Password-Authentication exchange or not. Is
Basic-Password-Authentication treated just as a case of no inner EAP
authentication method? It is also discussed in the errata 5844 thread.

Regarding introduction of Zero-MSK flag in Crypto-Binding TLV - do you
think it is unnecessary? So if one peer doesn't export a specific inner
method MSK and ESMK and uses Zero-MSK and another peer expects MSK or ESMK
- then the Crypto-Binding TLV exchange will fail naturally. Maybe it's
worth saying exactly that if the inner method exports MSK or EMSK then each
peer MUST use it and not Zero-MSK.

>

--0000000000006502f305b28eac85
Content-Type: text/html; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable

<div dir=3D"ltr"><div dir=3D"ltr"><blockquote class=3D"gmail_quote" style=
=3D"margin:0px 0px 0px 0.8ex;border-left:1px solid rgb(204,204,204);padding=
-left:1ex">It Should say:<br>=C2=A0 =C2=A0=C2=A0<br>=C2=A0 =C2=A0 S-IMCK[j]=
 =3D first 40 octets of IMCK[j]=C2=A0<br>=C2=A0 =C2=A0 CMK[j] =3D last 20 o=
ctets of IMCK[j]=C2=A0<br>where TLS-PRF is the PRF negotiated as part of TL=
S handshake [RFC5246].=C2=A0=C2=A0<br>If no inner EAP method has been run t=
he S-IMCK and CMK are generated as<br>above from S-IMCK[0].</blockquote><di=
v><br></div><div>Joe, for me it still doesn&#39;t sound as exact=C2=A0enoug=
h instructions. We should explain how to generate=C2=A0S-IMCK and CMK for n=
o inner method case with more details.=C2=A0</div><div><br></div><blockquot=
e class=3D"gmail_quote" style=3D"margin:0px 0px 0px 0.8ex;border-left:1px s=
olid rgb(204,204,204);padding-left:1ex">The Crypto-Binding TLV MUST be exch=
anged and verified before the<br>=C2=A0final Result TLV exchange, regardles=
s of whether there is an inner<br>=C2=A0EAP method authentication or not.=
=C2=A0=C2=A0</blockquote><div>This still remains an open question whether w=
e MUST send Crypto-Binding TLV after Basic-Password-Authentication=C2=A0exc=
hange or not. Is Basic-Password-Authentication treated just as a case of no=
 inner EAP authentication method? It is also discussed in the errata=C2=A05=
844 thread.</div><div><br></div><div>Regarding introduction of Zero-MSK fla=
g in Crypto-Binding TLV - do you think it is unnecessary? So if one peer do=
esn&#39;t export a specific inner method MSK and ESMK and uses Zero-MSK and=
 another peer expects MSK or ESMK - then the=C2=A0Crypto-Binding TLV exchan=
ge will fail naturally. Maybe it&#39;s worth saying exactly that if the inn=
er method exports MSK or EMSK then each peer MUST use it and not Zero-MSK.<=
/div></div><div class=3D"gmail_quote"><blockquote class=3D"gmail_quote" sty=
le=3D"margin:0px 0px 0px 0.8ex;border-left:1px solid rgb(204,204,204);paddi=
ng-left:1ex">
</blockquote></div></div>

--0000000000006502f305b28eac85--


From nobody Mon Oct 26 01:27:09 2020
Return-Path: <oleg.pekar.2017@gmail.com>
X-Original-To: emu@ietfa.amsl.com
Delivered-To: emu@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 1AD5B3A19BA for <emu@ietfa.amsl.com>; Mon, 26 Oct 2020 01:27:08 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.847
X-Spam-Level: 
X-Spam-Status: No, score=-1.847 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, DKIM_VALID_EF=-0.1, FREEMAIL_ENVFROM_END_DIGIT=0.25, FREEMAIL_FROM=0.001, HTML_MESSAGE=0.001, SPF_HELO_NONE=0.001, SPF_PASS=-0.001, URIBL_BLOCKED=0.001] autolearn=unavailable autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (2048-bit key) header.d=gmail.com
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 syNY3yK9AMGV for <emu@ietfa.amsl.com>; Mon, 26 Oct 2020 01:27:06 -0700 (PDT)
Received: from mail-ot1-x32e.google.com (mail-ot1-x32e.google.com [IPv6:2607:f8b0:4864:20::32e]) (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 40CA23A19B8 for <emu@ietf.org>; Mon, 26 Oct 2020 01:27:06 -0700 (PDT)
Received: by mail-ot1-x32e.google.com with SMTP id m22so7275733ots.4 for <emu@ietf.org>; Mon, 26 Oct 2020 01:27:06 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20161025;  h=mime-version:references:in-reply-to:from:date:message-id:subject:to :cc; bh=q8td29DwsyGjSMpSdvXJAUYfugCk06F2aO2shNxD948=; b=T2zts5TiQRotuDdbLFtFZ76P7H0r9KbQo28+VN2aPInWJ6RoXD4YMdbp+0AMvMuKqj Jb9g/ab7/3e2xXj+ZlotMn0YE0GJYzUQmfLJNIasRJMW9WAHKe0Va0tZWORZd9LqGDTG eRG+rhcnqI8ZW+UTD2MccHHt/o00UIxMX6dzgMiZeYYCHtUVMUJx/vXQThyXBj0CjUrY kNkOERk2hZlpv0OAe3j6odkXUMBAwl1diwk35ua9178jdYonLimC6I6pyNCkNWASKee+ jOvj/7OszlYFhfvdI631576N3jIA8X1C2mEe7aXD5zsTFIQWoHyqBA/bZbV4LXGrD+XU tULg==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:mime-version:references:in-reply-to:from:date :message-id:subject:to:cc; bh=q8td29DwsyGjSMpSdvXJAUYfugCk06F2aO2shNxD948=; b=eiHvCqRF3GwI239K4UlbheACrOGaH7yHtuKVExXWU/k4huycJfnL/nY0rpL/FYmkpu CueqEisS7dCauMppMpRphAv0jGWrgR6way2MYVdAWrkXEGTc9jE3V87hDD17gl6Lb8QU fm8IapGOzHOtYwLcRXuFA8K7bWiMk2NOhUG+78cBqco2KNvSrD0jHzFnbOGpAE9FYsWE NfV+kV70MGxEklJWRODHQNVf64Pqq8opIm6ZlPMTPqDSRQKedrcyYLswKr45SR3pw32j J3xgwsI5wJvuBSiN7ApE1T8p3Fr5S7WTZLx3yMZHfKXOg2mPeFYrmphucPYg2IgtFCCe t94A==
X-Gm-Message-State: AOAM5300yOcfLWsl4HOEv0W6jLO1QrvKIbMGvDCx9/eft1gPyCbpus3F w3EYLpBnNggoKKVEAgvOjZIllMwIDwUz6qMSOcskJ6nLNkE=
X-Google-Smtp-Source: ABdhPJwhmhZCjujYD8SDEHkoK2R+QZjsJ1GaMfXjDBgdr0GZsMOTI456cneyXNaG/C8kgDoe9ioqjNLVDZ70fPgQJ7U=
X-Received: by 2002:a9d:6a0a:: with SMTP id g10mr13678472otn.44.1603700825574;  Mon, 26 Oct 2020 01:27:05 -0700 (PDT)
MIME-Version: 1.0
References: <CAOgPGoBsGEGwC+3Z=uNz5an4ywmiopmakJFDVh4ZW=DRH6uFJg@mail.gmail.com>
In-Reply-To: <CAOgPGoBsGEGwC+3Z=uNz5an4ywmiopmakJFDVh4ZW=DRH6uFJg@mail.gmail.com>
From: Oleg Pekar <oleg.pekar.2017@gmail.com>
Date: Mon, 26 Oct 2020 10:26:54 +0200
Message-ID: <CABXxEz8yDvxB=g_ob1KZfLVFd2S4zRq=wvbUnc0SH1VJqf4Vaw@mail.gmail.com>
To: Joseph Salowey <joe@salowey.net>
Cc: EMU WG <emu@ietf.org>, Jouni Malinen <j@w1.fi>,  Jorge Vergara <jovergar=40microsoft.com@dmarc.ietf.org>
Content-Type: multipart/alternative; boundary="00000000000008d08b05b28eb2ff"
Archived-At: <https://mailarchive.ietf.org/arch/msg/emu/E6CN7B5iEkbjhxxBKnGMjHqFT-0>
Subject: Re: [Emu] Proposed Resolution for Errata 5845
X-BeenThere: emu@ietf.org
X-Mailman-Version: 2.1.29
Precedence: list
List-Id: "EAP Methods Update \(EMU\)" <emu.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/emu>, <mailto:emu-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/emu/>
List-Post: <mailto:emu@ietf.org>
List-Help: <mailto:emu-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/emu>, <mailto:emu-request@ietf.org?subject=subscribe>
X-List-Received-Date: Mon, 26 Oct 2020 08:27:08 -0000

--00000000000008d08b05b28eb2ff
Content-Type: text/plain; charset="UTF-8"

>It should say:
>
>   EAP method messages are carried within EAP-Payload TLVs defined in
>   Section 4.2.10.  Upon method completion, the server MUST send an
>  Intermediate-Result TLV indicating the result.

Jouni explained in errata 5767 that not all EAP methods are EAP
authentication methods, to be exact. In the proposed fix for errata 5767
you have already suggested that for Section 3.3.1 text:

>Section 3.3.1
>
>It should say:

>   EAP method messages are carried within EAP-Payload TLVs defined in
>   Section 4.2.10.  Upon completion of each EAP authentication method in
>   the tunnel, the server MUST send an Intermediate-Result TLV
>   indicating the result.



On Sun, Oct 25, 2020 at 9:14 PM Joseph Salowey <joe@salowey.net> wrote:

> Errata 5845: https://www.rfc-editor.org/errata/eid5845
> Proposed Status: Verified
> Revision:
>
> Section 3.3.1 says:
>
>    EAP method messages are carried within EAP-Payload TLVs defined in
>    Section 4.2.10.  If more than one method is going to be executed in
>    the tunnel, then upon method completion, the server MUST send an
>    Intermediate-Result TLV indicating the result.
>
> It should say:
>
>    EAP method messages are carried within EAP-Payload TLVs defined in
>    Section 4.2.10.  Upon method completion, the server MUST send an
>    Intermediate-Result TLV indicating the result.
>
> Notes:
>
> Description of whether Intermediate-Result TLV is supposed to be used in
> the case where only a single inner EAP authentication method is used.
> Section 3.3.1 says "more than one method is going to be executed in the
> tunnel, then upon method completion, the server MUST send an
> Intermediate-Result TLV indicating the result", Section 3.3.3 says "The
> Crypto-Binding TLV and Intermediate-Result TLV MUST be included to perform
> cryptographic binding after each successful EAP method in a sequence of one
> or more EAP methods", 4.2.13 says "It MUST be included with the
> Intermediate-Result TLV to perform cryptographic binding after each
> successful EAP method in a sequence of EAP methods", Annex C.3 shows an
> example exchange with a single inner EAP authentication method with use of
> Intermediate-Result TLV.
>
> It looks like the majority of the places discussion this topic implies
> that there is going to be an Intermediate-Result TLV after each inner EAP
> authentication method and the text in 3.3.1 is the only clear case of
> conflicting (or well, at least misleading if one were to claim it does not
> explicitly say MUST NOT for the one inner EAP authentication method case).
> As such, I'd conclude the Intermediate-Result TLV is indeed going to be
> exchanged after each EAP authentication method and the proposed text change
> to 3.3.1 covers that.
>

--00000000000008d08b05b28eb2ff
Content-Type: text/html; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable

<div dir=3D"ltr">&gt;It should say:<br>&gt;<br>&gt;=C2=A0 =C2=A0EAP method =
messages are carried within EAP-Payload TLVs defined in<br>&gt;=C2=A0 =C2=
=A0Section 4.2.10.=C2=A0 Upon method completion, the server MUST send an<di=
v>&gt;=C2=A0 Intermediate-Result TLV indicating the result.<br><div><br></d=
iv></div><div>Jouni explained in errata 5767 that not all EAP methods are E=
AP authentication methods, to be exact. In the proposed fix for errata 5767=
 you have already suggested that for Section 3.3.1 text:</div><div><br></di=
v><div>&gt;Section 3.3.1</div><div>&gt;</div><div>&gt;It should say:<br><br=
>&gt;=C2=A0 =C2=A0<span>EAP</span>=C2=A0method messages are carried within=
=C2=A0<span>EAP</span>-Payload TLVs defined in<br>&gt;=C2=A0 =C2=A0Section =
4.2.10.=C2=A0 Upon completion of each=C2=A0<span>EAP</span>=C2=A0<span>auth=
entication</span>=C2=A0method in<br>&gt;=C2=A0 =C2=A0the tunnel, the server=
 MUST send an Intermediate-Result TLV<br>&gt;=C2=A0 =C2=A0indicating the re=
sult.<br></div><div><br></div><div><br></div></div><br><div class=3D"gmail_=
quote"><div dir=3D"ltr" class=3D"gmail_attr">On Sun, Oct 25, 2020 at 9:14 P=
M Joseph Salowey &lt;<a href=3D"mailto:joe@salowey.net" target=3D"_blank">j=
oe@salowey.net</a>&gt; wrote:<br></div><blockquote class=3D"gmail_quote" st=
yle=3D"margin:0px 0px 0px 0.8ex;border-left:1px solid rgb(204,204,204);padd=
ing-left:1ex"><div dir=3D"ltr">Errata 5845:=C2=A0<a href=3D"https://www.rfc=
-editor.org/errata/eid5845" target=3D"_blank">https://www.rfc-editor.org/er=
rata/eid5845</a><div>Proposed Status: Verified</div><div>Revision:</div><br=
>Section 3.3.1 says:<br><br>=C2=A0 =C2=A0EAP method messages are carried wi=
thin EAP-Payload TLVs defined in<br>=C2=A0 =C2=A0Section 4.2.10.=C2=A0 If m=
ore than one method is going to be executed in<br>=C2=A0 =C2=A0the tunnel, =
then upon method completion, the server MUST send an<br>=C2=A0 =C2=A0Interm=
ediate-Result TLV indicating the result.<br><br>It should say:<br><br>=C2=
=A0 =C2=A0EAP method messages are carried within EAP-Payload TLVs defined i=
n<br>=C2=A0 =C2=A0Section 4.2.10.=C2=A0 Upon method completion, the server =
MUST send an<br>=C2=A0 =C2=A0Intermediate-Result TLV indicating the result.=
<div><br></div>Notes:<br><br>Description of whether Intermediate-Result TLV=
 is supposed to be used in the case where only a single inner EAP authentic=
ation method is used. Section 3.3.1 says &quot;more than one method is goin=
g to be executed in the tunnel, then upon method completion, the server MUS=
T send an Intermediate-Result TLV indicating the result&quot;, Section 3.3.=
3 says &quot;The Crypto-Binding TLV and Intermediate-Result TLV MUST be inc=
luded to perform cryptographic binding after each successful EAP method in =
a sequence of one or more EAP methods&quot;, 4.2.13 says &quot;It MUST be i=
ncluded with the Intermediate-Result TLV to perform cryptographic binding a=
fter each successful EAP method in a sequence of EAP methods&quot;, Annex C=
.3 shows an example exchange with a single inner EAP authentication method =
with use of Intermediate-Result TLV.<br><br>It looks like the majority of t=
he places discussion this topic implies that there is going to be an Interm=
ediate-Result TLV after each inner EAP authentication method and the text i=
n 3.3.1 is the only clear case of conflicting (or well, at least misleading=
 if one were to claim it does not explicitly say MUST NOT for the one inner=
 EAP authentication method case). As such, I&#39;d conclude the Intermediat=
e-Result TLV is indeed going to be exchanged after each EAP authentication =
method and the proposed text change to 3.3.1 covers that.</div>
</blockquote></div>

--00000000000008d08b05b28eb2ff--


From nobody Mon Oct 26 01:27:48 2020
Return-Path: <oleg.pekar.2017@gmail.com>
X-Original-To: emu@ietfa.amsl.com
Delivered-To: emu@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 8B09E3A19BA for <emu@ietfa.amsl.com>; Mon, 26 Oct 2020 01:27:46 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.847
X-Spam-Level: 
X-Spam-Status: No, score=-1.847 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, DKIM_VALID_EF=-0.1, FREEMAIL_ENVFROM_END_DIGIT=0.25, FREEMAIL_FROM=0.001, HTML_MESSAGE=0.001, SPF_HELO_NONE=0.001, SPF_PASS=-0.001, URIBL_BLOCKED=0.001] autolearn=unavailable autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (2048-bit key) header.d=gmail.com
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 T-J8y49zTVrT for <emu@ietfa.amsl.com>; Mon, 26 Oct 2020 01:27:45 -0700 (PDT)
Received: from mail-oi1-x231.google.com (mail-oi1-x231.google.com [IPv6:2607:f8b0:4864:20::231]) (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 D6BC43A19B6 for <emu@ietf.org>; Mon, 26 Oct 2020 01:27:44 -0700 (PDT)
Received: by mail-oi1-x231.google.com with SMTP id s21so9759450oij.0 for <emu@ietf.org>; Mon, 26 Oct 2020 01:27:44 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20161025;  h=mime-version:references:in-reply-to:from:date:message-id:subject:to :cc; bh=ebNyyHU7G2ijjwQvrcpNmEPW0p2kNN8iY9RyS0ZkIlk=; b=ViYZGiBdVzt9pcDDlLVjw9jJ+uu44injKdHRcRWvhtnJLLhB5xw5luP0ZVWBallffl KzPys1QFGnMGuNFTOZbPk2vNEE2ZMutobF//EV8wmLvw19WmInoeeQSzc9JAV5tH6kGU QkOpC+uVDeZrRvmmWexGJH7dcmw97z114FjjM6ip0sHcfSCEdJchCPQypzEx+AwqygJz nlwwCpV8GTlSx/prnBvO+eu1lIwFOYAgVUX83AEqvKHvEDHcLmZCJ46BShxDdkNYU5YF XJZot90IKdIjmh2oqAFs6PAQn9MIwx1JBqtk2u/XM5WxEVoJS56iq1H/zIr0c60Q91fb V15g==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:mime-version:references:in-reply-to:from:date :message-id:subject:to:cc; bh=ebNyyHU7G2ijjwQvrcpNmEPW0p2kNN8iY9RyS0ZkIlk=; b=rNbXFyqhYsFz6ICGBw8GUMvTQTzoZkGgtfSjoToh3JryM79Vm88T2JWeSsd6LR2EVB lYxBi2WTn3zi3+jIzMLQknhCbgets/x2YHTT21la6QlMYphAcbVKTu5jhHIWBQRQ7bwk TMeEOz0FCMMkxB3KeaUbx/1QlsK5WVmdRzht/zXc3oJXOV0XHvUp6+Ub7TVSHUZ2O7wN LQtGp3qJlHSWUiEWqP8MF/18EbvktXP3RxfJUZrUD5G+ADI0G2qZ/OaKaHYS17dE4GMG R3Bjx8us3CplUYil+56jiRS6ZPQJntZVMOf+KZmzdTmHkfXyWuttuedTzaGJPBx5YNhm C0mg==
X-Gm-Message-State: AOAM532Ra/8bZAXrrcRYV8iauGsSdUJsBbCqCVrce9A6o6fAAuAZmPmd JBmJnyn0ZW2LQczC9e2YKrMdgaS83yCMUwRBgpBufLxPaWA=
X-Google-Smtp-Source: ABdhPJwBx07nAFz3yH7yUfDupQNMHOPohe3xz5ltHvlZVC3gsW1qdiaAac+xKR4Q7yXlD3FDgqIIuX0iUuvf4K1IglM=
X-Received: by 2002:a05:6808:696:: with SMTP id k22mr12932639oig.107.1603700864202;  Mon, 26 Oct 2020 01:27:44 -0700 (PDT)
MIME-Version: 1.0
References: <CAOgPGoDfmCJwnZJLqeyXD0+X_aeqXXkiZZOo2WYP4SC0D67HQw@mail.gmail.com>
In-Reply-To: <CAOgPGoDfmCJwnZJLqeyXD0+X_aeqXXkiZZOo2WYP4SC0D67HQw@mail.gmail.com>
From: Oleg Pekar <oleg.pekar.2017@gmail.com>
Date: Mon, 26 Oct 2020 10:27:33 +0200
Message-ID: <CABXxEz8M=QLP=qrqdeyMvNt+nAd-o_RLmUDUmTOibxm-d4D26A@mail.gmail.com>
To: Joseph Salowey <joe@salowey.net>
Cc: EMU WG <emu@ietf.org>, Jouni Malinen <j@w1.fi>,  Jorge Vergara <jovergar=40microsoft.com@dmarc.ietf.org>
Content-Type: multipart/alternative; boundary="000000000000563be205b28eb4fc"
Archived-At: <https://mailarchive.ietf.org/arch/msg/emu/dd9lBXlJF-7dq1k8AmTDiRZm0Ms>
Subject: Re: [Emu] Proposed Resolution to TEAP Errata 5844
X-BeenThere: emu@ietf.org
X-Mailman-Version: 2.1.29
Precedence: list
List-Id: "EAP Methods Update \(EMU\)" <emu.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/emu>, <mailto:emu-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/emu/>
List-Post: <mailto:emu@ietf.org>
List-Help: <mailto:emu-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/emu>, <mailto:emu-request@ietf.org?subject=subscribe>
X-List-Received-Date: Mon, 26 Oct 2020 08:27:47 -0000

--000000000000563be205b28eb4fc
Content-Type: text/plain; charset="UTF-8"

Few comments:
1) It seems that the server MUST send Crypto-Binding TLV after a single EAP
authentication method, after each of EAP authentications methods in a
sequence, after no inner method but not after
Basic-Password-Authentication. Shouldn't we close this gap for the sake of
simplicity and structure? (Only Zero-MSK Crypto-Binding TLV is possible in
this case, the same as in no inner method case). Is
Basic-Password-Authentication treated as a case of no inner method?
Technically it is already correct but still may not be clear enough.

This also affects section "4.2.13. Crypto-Binding TLV":

The Crypto-Binding TLV MUST be exchanged and verified before the final
Result TLV exchange, regardless of whether there is an inner EAP
method authentication or not.

Shouldn't we mention "inner EAP method or basic password authentication"?

2) [Minor] It is written both "EAP methods **and** basic password
authentication" and "EAP methods **or**basic password authentication" in
different sections above. Shouldn't we use the same all the time?


On Sun, Oct 25, 2020 at 9:10 PM Joseph Salowey <joe@salowey.net> wrote:

> Errata 5844: https://www.rfc-editor.org/errata/eid5844
> Status: Verified
> Revision:
>
> Section 3.3.2 says:
>
> Upon receiving the response, the server
>    indicates the success or failure of the exchange using an
>    Intermediate-Result TLV.
>
> It Should say:
>
> Upon receiving the response, the server MUST
>    indicate the success or failure of the exchange using an
>    Intermediate-Result TLV.
>
> Section 3.6 says:
>
> 3. The Intermediate-Result TLVs carry success or failure indications of
> the individual EAP methods in TEAP Phase 2.
>
> It Should say:
>
> 3. The Intermediate-Result TLVs carry success or failure indications of
> the individual EAP methods and basic password authentication in TEAP Phase
> 2.
>
> Section 4.2.11 says:
>
> The Intermediate-Result TLV provides support for acknowledged intermediate
> Success and Failure messages between multiple inner EAP methods within EAP.
>
> It Should say:
>
> The Intermediate-Result TLV provides support for acknowledged intermediate
> Success and Failure messages between multiple inner EAP methods or basic
> password authentication within EAP.
>
> Section C.1 says:
>
>                             <- Crypto-Binding TLV (Request),
>                                 Result TLV (Success),
>                                 (Optional PAC TLV)
>
>        Crypto-Binding TLV(Response),
>        Result TLV (Success),
>        (PAC-Acknowledgement TLV) ->
>
> It should say:
>
>                             <- Intermediate-Result-TLV (Success),
>                                 Crypto-Binding TLV (Request),
>                                 Result TLV (Success),
>                                 (Optional PAC TLV)
>
>        Intermediate-Result-TLV (Success),
>        Crypto-Binding TLV(Response),
>        Result TLV (Success),
>        (PAC-Acknowledgement TLV) ->
>
> Section C.2 Says:
>                 <- Result TLV (Failure)
>
>             Result TLV (Failure) ->
>
> It Should Say:
>
>                 <- Intermediate-Result-TLV (Failure),
>                      Result TLV (Failure)
>
>             Intermediate-Result-TLV (Failure),
>        Result TLV (Failure) ->
>
>
> Notes:
>
> Section 3.3.2 implies that Intermediate-Result TLV is used after each
> round of Basic-Password-Auth-Req/Resp TLVs. However, the example sequence
> in C.1 does not show this. The proposed change in this errata adds the
> Intermediate-Result TLV indication here. Similar change should be done in
> C.2 (i.e., add Intermediate-Result TLV (Failure) to the messages that
> include Result TLV) since the language in 3.3.2 describe the indication to
> be used for both success and failure cases.
>
> In addition to this change in C.1, it would be good to clarify the
> specification globally to avoid confusion about this case since almost all
> discussion regarding Intermediate-Result TLV currently is in the context of
> inner EAP authentication. 3.3.2 should have a MUST statement similar to
> 3.3.1. 3.6 should cover success or failure indications of basic password
> auth like it does EAP methods. 4.2.11 should note Intermediate-Result TLV
> is used with both inner EAP and basic password auth.
>

--000000000000563be205b28eb4fc
Content-Type: text/html; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable

<div dir=3D"ltr"><div>Few comments:</div>1) It seems that the server MUST s=
end Crypto-Binding TLV after a single EAP authentication method, after each=
 of EAP authentications methods in a sequence, after no inner method=C2=A0b=
ut not after Basic-Password-Authentication. Shouldn&#39;t we close this gap=
 for the sake of simplicity and structure? (Only Zero-MSK Crypto-Binding TL=
V is possible in this case, the same as in no inner method case). Is Basic-=
Password-Authentication treated as a case of no inner method? Technically i=
t is already correct but still may not be clear enough.=C2=A0<div><br></div=
><div>This also affects section &quot;4.2.13. Crypto-Binding TLV&quot;:=C2=
=A0</div><div><br></div>The Crypto-Binding TLV MUST be exchanged and verifi=
ed before the final Result TLV exchange, regardless of whether there is an =
inner EAP<br>method authentication or not.<div><br></div><div>Shouldn&#39;t=
 we mention &quot;inner EAP method or basic password authentication&quot;?<=
div><br><div>2) [Minor] It is written both &quot;EAP methods **and** basic=
=C2=A0password authentication&quot; and &quot;EAP methods **or**basic=C2=A0=
password authentication&quot; in different sections above. Shouldn&#39;t we=
 use the same all the time?</div><div><br></div></div></div></div><br><div =
class=3D"gmail_quote"><div dir=3D"ltr" class=3D"gmail_attr">On Sun, Oct 25,=
 2020 at 9:10 PM Joseph Salowey &lt;<a href=3D"mailto:joe@salowey.net" targ=
et=3D"_blank">joe@salowey.net</a>&gt; wrote:<br></div><blockquote class=3D"=
gmail_quote" style=3D"margin:0px 0px 0px 0.8ex;border-left:1px solid rgb(20=
4,204,204);padding-left:1ex"><div dir=3D"ltr">Errata 5844:=C2=A0<a href=3D"=
https://www.rfc-editor.org/errata/eid5844" target=3D"_blank">https://www.rf=
c-editor.org/errata/eid5844</a><div>Status: Verified</div><div>Revision:</d=
iv><div><br></div><div>Section 3.3.2 says:</div><div><br></div>Upon receivi=
ng the response, the server<br>=C2=A0 =C2=A0indicates the success or failur=
e of the exchange using an<br>=C2=A0 =C2=A0Intermediate-Result TLV.<div><br=
></div><div>It Should say:</div><div><br></div><div>Upon receiving the resp=
onse, the server MUST<br>=C2=A0 =C2=A0indicate the success or failure of th=
e exchange using an<br>=C2=A0 =C2=A0Intermediate-Result TLV.<br></div><div>=
<br></div><div>Section 3.6 says:</div><div><br></div>3. The Intermediate-Re=
sult TLVs carry success or failure indications of the individual EAP method=
s in TEAP Phase 2.<div><br></div><div>It Should say:</div><div><br></div><d=
iv>3. The Intermediate-Result TLVs carry success or failure indications of =
the individual EAP methods and basic=C2=A0password authentication in TEAP P=
hase 2.<br></div><div><br><div>Section 4.2.11 says:</div><div><br></div>The=
 Intermediate-Result TLV provides support for acknowledged intermediate Suc=
cess and Failure messages between multiple inner EAP methods within EAP.</d=
iv><div><br></div><div>It Should say:</div><div><br></div><div>The Intermed=
iate-Result TLV provides support for acknowledged intermediate Success and =
Failure messages between multiple inner EAP methods or basic password authe=
ntication within EAP.<br><div><br></div><div>Section C.1 says:<br><br>=C2=
=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =
=C2=A0 =C2=A0 =C2=A0 &lt;- Crypto-Binding TLV (Request),<br>=C2=A0 =C2=A0 =
=C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=
=A0 =C2=A0 =C2=A0 =C2=A0 Result TLV (Success),<br>=C2=A0 =C2=A0 =C2=A0 =C2=
=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =
=C2=A0 =C2=A0 (Optional PAC TLV)<br><br>=C2=A0 =C2=A0 =C2=A0 =C2=A0Crypto-B=
inding TLV(Response),<br>=C2=A0 =C2=A0 =C2=A0 =C2=A0Result TLV (Success),<b=
r>=C2=A0 =C2=A0 =C2=A0 =C2=A0(PAC-Acknowledgement TLV) -&gt;<br><br>It shou=
ld say:<br><br>=C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=
=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 &lt;- Intermediate-Result-TLV (Succe=
ss),<br>=C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=
=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 Crypto-Binding TLV (Request),=
<br>=C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =
=C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 Result TLV (Success),<br>=C2=A0 =
=C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=
=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 (Optional PAC TLV)<br><br>=C2=A0 =C2=A0 =C2=
=A0 =C2=A0Intermediate-Result-TLV (Success),<br>=C2=A0 =C2=A0 =C2=A0 =C2=A0=
Crypto-Binding TLV(Response),<br>=C2=A0 =C2=A0 =C2=A0 =C2=A0Result TLV (Suc=
cess),<br>=C2=A0 =C2=A0 =C2=A0 =C2=A0(PAC-Acknowledgement TLV) -&gt;<div><b=
r></div><div>Section C.2 Says:</div><div>=C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0=
 =C2=A0 =C2=A0 =C2=A0 &lt;- Result TLV (Failure)<pre style=3D"font-size:13.=
3333px;margin-top:0px;margin-bottom:0px;break-before:page;color:rgb(0,0,0)"=
></pre><pre style=3D"font-size:13.3333px;margin-top:0px;margin-bottom:0px;b=
reak-before:page;color:rgb(0,0,0)">     </pre>=C2=A0 =C2=A0 =C2=A0 =C2=A0Re=
sult TLV (Failure) -&gt;</div><div><br></div><div>It Should Say:</div><div>=
<br></div><div>=C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 &lt;=
- Intermediate-Result-TLV (Failure),<br>=C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =
=C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0Result TLV (Failure)<pre style=3D"=
font-size:13.3333px;margin-top:0px;margin-bottom:0px;break-before:page;colo=
r:rgb(0,0,0)"></pre><pre style=3D"font-size:13.3333px;margin-top:0px;margin=
-bottom:0px;break-before:page;color:rgb(0,0,0)">     </pre>=C2=A0 =C2=A0 =
=C2=A0 =C2=A0Intermediate-Result-TLV (Failure),=C2=A0<br>=C2=A0 =C2=A0 =C2=
=A0 =C2=A0Result TLV (Failure) -&gt;<br><pre style=3D"font-size:13.3333px;m=
argin-top:0px;margin-bottom:0px;break-before:page;color:rgb(0,0,0)"></pre><=
pre style=3D"font-size:13.3333px;margin-top:0px;margin-bottom:0px;break-bef=
ore:page;color:rgb(0,0,0)"><br></pre>Notes: <br><br>Section 3.3.2 implies t=
hat Intermediate-Result TLV is used after each round of Basic-Password-Auth=
-Req/Resp TLVs. However, the example sequence in C.1 does not show this. Th=
e proposed change in this errata adds the Intermediate-Result TLV indicatio=
n here. Similar change should be done in C.2 (i.e., add Intermediate-Result=
 TLV (Failure) to the messages that include Result TLV) since the language =
in 3.3.2 describe the indication to be used for both success and failure ca=
ses.</div></div></div><br>In addition to this change in C.1, it would be go=
od to clarify the specification globally to avoid confusion about this case=
 since almost all discussion regarding Intermediate-Result TLV currently is=
 in the context of inner EAP authentication. 3.3.2 should have a MUST state=
ment similar to 3.3.1. 3.6 should cover success or failure indications of b=
asic password auth like it does EAP methods. 4.2.11 should note Intermediat=
e-Result TLV is used with both inner EAP and basic password auth.=C2=A0=C2=
=A0</div>
</blockquote></div>

--000000000000563be205b28eb4fc--


From nobody Mon Oct 26 05:08:37 2020
Return-Path: <john.mattsson@ericsson.com>
X-Original-To: emu@ietfa.amsl.com
Delivered-To: emu@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 055F03A08A9 for <emu@ietfa.amsl.com>; Mon, 26 Oct 2020 05:08:35 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.102
X-Spam-Level: 
X-Spam-Status: No, score=-2.102 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIMWL_WL_HIGH=-0.001, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, DKIM_VALID_EF=-0.1, RCVD_IN_MSPIKE_H2=-0.001, SPF_PASS=-0.001, URIBL_BLOCKED=0.001] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (1024-bit key) header.d=ericsson.com
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 Xm5eRCgjl5LU for <emu@ietfa.amsl.com>; Mon, 26 Oct 2020 05:08:33 -0700 (PDT)
Received: from EUR04-HE1-obe.outbound.protection.outlook.com (mail-eopbgr70089.outbound.protection.outlook.com [40.107.7.89]) (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 E27A63A0880 for <emu@ietf.org>; Mon, 26 Oct 2020 05:08:32 -0700 (PDT)
ARC-Seal: i=1; a=rsa-sha256; s=arcselector9901; d=microsoft.com; cv=none; b=ndCqsq3LJYCBsqVCDMilh9nfLaN/oCRjRBVGBB9qDMheDF/Xw6KTVVlcGkrkoo4P0hj1qWuYyzesWu4nED4/oGw6I5ciTA4hMqhcJvr0mWhBB6DNtHmLqaFjtYlSibyf2o/E2O/1kWS96wSwpYieHYJQxqERc8vgnpRjSZDbw1QtyNZVGb+VNyskMezQiPqau4yXkCP+C8s7GqV+UlaKWtiulFi7aZ2MuiJGQbZ18UrXxCCaOcbcX2JMdRtyXSCPVkemmXsSyR8JZhr70FR2FJrgUjItlyvCdl+2V0xAWUqXMV3pE/Fv6h2ZuTekkE/2tqUDIOU2LpOa2hb58NhX0A==
ARC-Message-Signature: i=1; a=rsa-sha256; c=relaxed/relaxed; d=microsoft.com;  s=arcselector9901; h=From:Date:Subject:Message-ID:Content-Type:MIME-Version:X-MS-Exchange-SenderADCheck; bh=udB+VMvcO997bOHZBtsLV0+BDq465o8M3DCMvV78IkA=; b=PuTv/C9C9YualQ8E0K9tNhJvhm35u7Oi3kb9ipRwoN1YpsLCBCl8iJDq/flcx/HTPAqU3OMxiiwDOrxzjs/uNflZafycx0QXO5WfDfX0zgUbUCBBj5PksYed+Dq8rDFOnTA0M7wGJck+g/+BFclCoB2kcvNYPZ/d0bXEBmTH0EcdSxiqYyBg8ZzxeHD+Q82yLyFVLX46mZDO+qzBXWR3+IG44laNmLsKJ0IPXtAhfjO7iDg5NhLnomDG9t5o//gGz7J5xTfONMBdoBtgw1f1jFjiqYu7cJ8oHnc6ZNMqv9KFYuSmoxdxSNBshUPJ852dxZM8+zFqKhD78GiHyprwpw==
ARC-Authentication-Results: i=1; mx.microsoft.com 1; spf=pass smtp.mailfrom=ericsson.com; dmarc=pass action=none header.from=ericsson.com; dkim=pass header.d=ericsson.com; arc=none
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=ericsson.com; s=selector1; h=From:Date:Subject:Message-ID:Content-Type:MIME-Version:X-MS-Exchange-SenderADCheck; bh=udB+VMvcO997bOHZBtsLV0+BDq465o8M3DCMvV78IkA=; b=Ymci42cd0V+oI+vHONhvjbQqSu6Mp1mXikLXJCxLhflhTdNHPcpdinOMlrXv04ScRP0MGnmKllkSvRosqC4Yn9/wtIGjaiIE6ZMRp8+pnvHATen1YMZGObyRpvvM0bFJSpYJwa94FONTkB1bUR9V/B1n8CbhRHgLDjMeJkvcp+c=
Received: from AM6PR07MB4584.eurprd07.prod.outlook.com (2603:10a6:20b:17::24) by AM6PR07MB5399.eurprd07.prod.outlook.com (2603:10a6:20b:8d::32) with Microsoft SMTP Server (version=TLS1_2, cipher=TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384) id 15.20.3499.4; Mon, 26 Oct 2020 12:08:26 +0000
Received: from AM6PR07MB4584.eurprd07.prod.outlook.com ([fe80::951:a4c3:7f39:e39c]) by AM6PR07MB4584.eurprd07.prod.outlook.com ([fe80::951:a4c3:7f39:e39c%5]) with mapi id 15.20.3499.015; Mon, 26 Oct 2020 12:08:26 +0000
From: John Mattsson <john.mattsson@ericsson.com>
To: "emu@ietf.org" <emu@ietf.org>
Thread-Topic: [Emu] draft-ietf-emu-eap-tls13-11: OCSP Stapling
Thread-Index: AQHWq5C1GWGefoT7/UmcfGZXldFKNA==
Date: Mon, 26 Oct 2020 12:08:26 +0000
Message-ID: <7E22462D-3668-4F4F-BD66-A125A26B34DC@ericsson.com>
Accept-Language: en-US
Content-Language: en-GB
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
user-agent: Microsoft-MacOutlook/16.42.20101102
authentication-results: ietf.org; dkim=none (message not signed) header.d=none;ietf.org; dmarc=none action=none header.from=ericsson.com;
x-originating-ip: [81.225.97.222]
x-ms-publictraffictype: Email
x-ms-office365-filtering-correlation-id: 8a3836f3-ef6a-4a22-9947-08d879a7d84d
x-ms-traffictypediagnostic: AM6PR07MB5399:
x-microsoft-antispam-prvs: <AM6PR07MB53993EDCA848D2707114023689190@AM6PR07MB5399.eurprd07.prod.outlook.com>
x-ms-oob-tlc-oobclassifiers: OLM:10000;
x-ms-exchange-senderadcheck: 1
x-microsoft-antispam: BCL:0;
x-microsoft-antispam-message-info: b+uo7lnTP8vnbPWWTpirSUNhpG4VzWmDMYXCjdi4mppaIv93O+XQBAvF3L+ncMrZwgiMdNrGpCbPTFAqSg9t09WIu6zAhUgB6eje+WzVf7zyQBeiEvHjq2ZsOqbd75OboGAe8OLLvNPAZlBYewgrQsJSJuWx9AqkkKQRHz6IY8NHTfy+yD0GbSrA6fS5ZqdIe7go78HWnwUdvpBdEwQ0GV1QXEGV+Le/mcFDT5sH9MVnwbO0L0j5O25hMDDOIRNkDOhRK94Yr55IdXTmzVwAe6XVp238hHkxekTahcYtdpXkaW1GZPEUtlY8natwdHNjJB/gE7cV94zt67abreULQoaZ8i238QNAldVPrrFEpYrGlLCTTrL1cdx3KbCreLwcht5vsS6lVi0pmJjZgn+qcw==
x-forefront-antispam-report: CIP:255.255.255.255; CTRY:; LANG:en; SCL:1; SRV:;  IPV:NLI; SFV:NSPM; H:AM6PR07MB4584.eurprd07.prod.outlook.com; PTR:; CAT:NONE;  SFS:(4636009)(366004)(396003)(136003)(39860400002)(346002)(376002)(8676002)(5660300002)(6486002)(966005)(6916009)(6506007)(186003)(86362001)(36756003)(71200400001)(76116006)(33656002)(478600001)(316002)(44832011)(26005)(8936002)(6512007)(64756008)(66946007)(66556008)(83380400001)(2616005)(66446008)(91956017)(2906002)(66476007); DIR:OUT; SFP:1101; 
x-ms-exchange-antispam-messagedata: sECWCdxAJD7bc1d+B/dYAvY4E5FS2UbdwFR6CJOgpSvYoycH0KldP8gHEJrECBjWWqFIoyMHBgg6uxC5xlA7yz7K5821KAaslOXhakjxbL1ibczV1wMh7HRzb7PH0A7fkLrbryolHXWrRFnsJWFtyD7otANGz+Afqb7dnH00wb/PzSSOlTiLL+eol3CIhZT4D5ps3hJUaMi17OzIdt5z8Bt8jQO7FvB8vEfQJEplCaOcq7pwVk91wqNyyib95JW8GXIz/P+wNushZIpaKmFW8AIf9hKvDjFhyQ//4/gVr1h71Q2laK0uZU5XXrqgZswanWqk2LETxi1Om4p4YyhEfpU9+Tyk6r95+aMw4iopElUcpmstDZeJWOsoRWCIXpZNbjrwlFAdUOXy5gpykZPKglEQ/4To6wkHS81lYXnYQq8HvfcHQEHkG769q++yOgjlJ+0Mo+JDCRZlCOS5OkG0q05JFMHWXn9kxj9MvpzuqlQ6IfPuT5bU5bpzrSVyJHlfvA/odWeb1szEheffLggimNvwvEpC998jRrghw2+Mhg/Ce1yIfHneobSyDGoVwS8iL7/KNRkGCh968lzB62fLJuWKPWlS4UaoMq2zy7D+LvA3RFim/GXu1X33WPdRaxsS/LQkgRPyFETETHkDXPUgFw==
x-ms-exchange-transport-forked: True
Content-Type: text/plain; charset="utf-8"
Content-ID: <5AB2DE8A9B271141A1353DAAC2FBBD3F@eurprd07.prod.outlook.com>
Content-Transfer-Encoding: base64
MIME-Version: 1.0
X-OriginatorOrg: ericsson.com
X-MS-Exchange-CrossTenant-AuthAs: Internal
X-MS-Exchange-CrossTenant-AuthSource: AM6PR07MB4584.eurprd07.prod.outlook.com
X-MS-Exchange-CrossTenant-Network-Message-Id: 8a3836f3-ef6a-4a22-9947-08d879a7d84d
X-MS-Exchange-CrossTenant-originalarrivaltime: 26 Oct 2020 12:08:26.6949 (UTC)
X-MS-Exchange-CrossTenant-fromentityheader: Hosted
X-MS-Exchange-CrossTenant-id: 92e84ceb-fbfd-47ab-be52-080c6b87953f
X-MS-Exchange-CrossTenant-mailboxtype: HOSTED
X-MS-Exchange-CrossTenant-userprincipalname: B+2NlNf1V7nXnKi0OUCor1Av86eFAPx5i80Pz/5gNSVwz+GW4MJz+eltKGF/2KodmgMNOs0QiW+tA1auXpg08zKEPlDN7UJYPlxXzH1kdX4=
X-MS-Exchange-Transport-CrossTenantHeadersStamped: AM6PR07MB5399
Archived-At: <https://mailarchive.ietf.org/arch/msg/emu/HP39yRUD0QkwwzuoXuv6_XGrUsY>
Subject: Re: [Emu] draft-ietf-emu-eap-tls13-11: OCSP Stapling
X-BeenThere: emu@ietf.org
X-Mailman-Version: 2.1.29
Precedence: list
List-Id: "EAP Methods Update \(EMU\)" <emu.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/emu>, <mailto:emu-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/emu/>
List-Post: <mailto:emu@ietf.org>
List-Help: <mailto:emu-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/emu>, <mailto:emu-request@ietf.org?subject=subscribe>
X-List-Received-Date: Mon, 26 Oct 2020 12:08:35 -0000

SGksDQoNCldoZW4gdGhpcyB3YXMgZGlzY3Vzc2VkIGluIHRoZSBncm91cCwgaXQgd2FzIGRlY2lk
ZWQgdG8gbm90IG9ubHkgbWFuZGF0ZSByZXZvY2F0aW9uIGNoZWNraW5nLCBidXQgdG8gYWxzbyBt
YW5kYXRlIE9DU1Agc3RhcGxpbmcgYXMgaXMgaXQgb2Z0ZW4gdGhlIG9ubHkgdmlhYmxlIHNvbHV0
aW9uIHRvIGxldCBhbiBvZmZsaW5lIHBlZXIgY2hlY2sgdGhlIHJldm9jYXRpb24gc3RhdHVzIG9m
IHRoZSBzZXJ2ZXIuIFdlIGhhZCBhIGRpc2N1c3Npb24gb24gbXVzdC1zdGFwbGUsIGFuZCB0aGUg
ZGVjaXNpb24gd2FzIHRvIG1hbmRhdGUgc3RhcGxpbmcgaW4gdGhlIGRyYWZ0IGluc3RlYWQgb2Yg
d2FpdGluZyBmb3Igc3VwcG9ydCBvZiB0aGUgWC41MDkgbXVzdC1zdGFwbGUgZXh0ZW5zaW9uLiBP
Q1NQIGFuZCBPQ1NQIHN0YXBsaW5nIGFyZSBxdWl0ZSB3ZWxsIHN1cHBvcnRlZCBhbHJlYWR5IGFu
ZCBzaG91bGQgYmUgZXZlbiBtb3JlIHdlbGwtc3VwcG9ydGVkIGluIGEgZmV3IHllYXJzOg0KDQox
LiBCYXNpY2FsbHkgYWxsIFRMUyBpbXBsZW1lbnRhdGlvbnMgc3VwcG9ydCBPU0NQLCBhbmQgYSBt
YWpvcml0eSBzdXBwb3J0IE9TQ1Agc3RhcGxpbmcgKENlcnRpZmljYXRlIFN0YXR1cyBSZXF1ZXN0
KS4gTWJlZCBpcyBhbiBleGNlcHRpb24gcmF0aGVyIHRoYW4gdGhlIHJ1bGUuDQoNCmh0dHBzOi8v
ZW4ud2lraXBlZGlhLm9yZy93aWtpL0NvbXBhcmlzb25fb2ZfVExTX2ltcGxlbWVudGF0aW9ucw0K
DQoyLiBBbGwgYnJvd3NlcnMgKGRlc2t0b3AgYW5kIG1vYmlsZSkgc3VwcG9ydCBPQ1NQIHN0YXBs
aW5nLg0KDQpodHRwczovL2Jsb2cuYXBuaWMubmV0LzIwMTkvMDEvMTUvaXMtdGhlLXdlYi1yZWFk
eS1mb3Itb2NzcC1tdXN0LXN0YXBsZS8jOn46dGV4dD1PQ1NQJTIwTXVzdCUyRFN0YXBsZSUyMGlz
JTIwYSxDZXJ0aWZpY2F0ZSUyMFN0YXR1cyUyMFByb3RvY29sJTIwKE9DU1ApLg0KDQozLiBOSVNU
IFNQIDgwMC01MiBSZXYgMiBtYW5kYXRlcyB0aGF0IHRoZSBzZXJ2ZXIgc2hhbGwgc3VwcG9ydCB1
c2Ugb2YgdGhlIENlcnRpZmljYXRlIFN0YXR1cyBSZXF1ZXN0IGV4dGVuc2lvbiAoaS5lLiBPQ1NQ
IHN0YXBsaW5nKS4NCg0KDQotIEkgZG8gbm90IHRoaW5rIHRoZXJlIGlzIGFueSB3aWdnbGUgcm9v
bSBhdCBhbGwgaW4gdGhlIGN1cnJlbnQgdmVyc2lvbiBvZiB0aGUgZHJhZnQ6DQoNCiAgIldoZW4g
RUFQLVRMUyBpcyB1c2VkIHdpdGggVExTIDEuMywgdGhlIHBlZXIgYW5kIHNlcnZlciBNVVNUIHVz
ZSBDZXJ0aWZpY2F0ZSBTdGF0dXMgUmVxdWVzdHMgW1JGQzYwNjZdDQogICAgZm9yIHRoZSBzZXJ2
ZXIncyBjZXJ0aWZpY2F0ZSBjaGFpbiINCg0KICBOb3RlIHRoYXQgaW4gdGhlIGN1cnJlbnQgZHJh
ZnQgaXQgaXMgdW5zcGVjaWZpZWQgaG93IHRoZSBzZXJ2ZXIgY2hlY2tzIHRoZSByZXZvY2F0aW9u
IHN0YXR1cyBvZiB0aGUgY2xpZW50J3MgY2VydGlmaWNhdGU6DQogIA0KICAiV2hlbiBFQVAtVExT
IGlzIHVzZWQgd2l0aCBUTFMgMS4zLCB0aGUgc2VydmVyIE1VU1QgY2hlY2sgdGhlIHJldm9jYXRp
b24gc3RhdHVzIG9mIHRoZSBjZXJ0aWZpY2F0ZXMgaW4gdGhlDQogICAgY2xpZW50J3MgY2VydGlm
aWNhdGUgY2hhaW4uIg0KDQoNCi0gVGhlIFguNTA5IG11c3Qtc3RhcGxlIGV4dGVuc2lvbiAoaHR0
cHM6Ly90b29scy5pZXRmLm9yZy9odG1sL2RyYWZ0LWhhbGxhbWJha2VyLW11c3RzdGFwbGUtMDAp
IGlzIG5vdCByZWxldmFudCBmb3Igc2VydmVyIGNlcnRpZmljYXRlcyBpbiB0aGUgY3VycmVudCBF
QVAtVExTIDEuMyBkcmFmdCBhcyBzdGFwbGluZyBpcyBhbHJlYWR5IGEgbXVzdC4gT1NDUCBzdGFw
bGluZyBpcyBub3QgdmVyeSB1c2VmdWwgZm9yIGNsaWVudCBjZXJ0cy4gSSBkbyBub3Qga25vdyBp
ZiB0aGUgWC41MDkgbXVzdC1zdGFwbGUgZXh0ZW5zaW9uIGlzIHdlbGwgc3VwcG9ydGVkIG9yIG5v
dC4gSXQgY291bGQgYmVjb21lIHJlbGV2YW50IGZvciBzZXJ2ZXIgY2VydHMgaWYgdGhlIHJlcXVp
cmVtZW50cyBhcmUgc29mdGVuZWQuDQoNCg0KLSBNeSB2aWV3IGlzIHRoYXQgT1NDUCBzdGFwbGlu
ZyBpcyBhIHZlcnkgZ29vZCBmaXQgZm9yIEVBUCBpbiBwYXJ0aWN1bGFyIGFuZCBpcyB3ZWxsLXN1
cHBvcnRlZCBlbm91Z2ggdG8gYmUgbWFuZGF0ZWQuIE1hbmRhdGluZyBzdGFwbGluZyBmb3IgRUFQ
LVRMUyAxLjMgZnJvbSB0aGUgc3RhcnQgYXZvaWRzIGhhdmluZyB0byByZWx5IG9uIHRoZSBYLjUw
OSBtdXN0LXN0YXBsZSBleHRlbnNpb24uIEFueSBpbXBsZW1lbnRhdGlvbiBub3Qgc3VwcG9ydGlu
ZyBPQ1NQIHN0YXBsaW5nIHNob3VsZCBpbXBsZW1lbnQgaXQgdG9nZXRoZXIgd2l0aCBUTFMgMS4z
LiBJIGRvIG5vdCB0aGluayB0aGUgcmVxdWlyZW50IHNob3VsZCBiZSBzb2Z0ZW5lZCwgYnV0IGlm
IGl0IGlzLCBteSB2aWV3IGlzIHRoYXQgaXMgc2hvdWxkIGJlIHNvZnRlbmVkIGFzIGxpdHRsZSBh
cyBwb3NzaWJsZS4NCg0KQ2hlZXJzLA0KSm9obg0KDQo=


From nobody Mon Oct 26 05:16:08 2020
Return-Path: <lear@cisco.com>
X-Original-To: emu@ietfa.amsl.com
Delivered-To: emu@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 6C5883A091C for <emu@ietfa.amsl.com>; Mon, 26 Oct 2020 05:16:07 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -9.601
X-Spam-Level: 
X-Spam-Status: No, score=-9.601 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIMWL_WL_MED=-0.001, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, DKIM_VALID_EF=-0.1, SPF_PASS=-0.001, URIBL_BLOCKED=0.001, USER_IN_DEF_DKIM_WL=-7.5] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (1024-bit key) header.d=cisco.com
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_SIicajUK3m for <emu@ietfa.amsl.com>; Mon, 26 Oct 2020 05:16:05 -0700 (PDT)
Received: from aer-iport-1.cisco.com (aer-iport-1.cisco.com [173.38.203.51]) (using TLSv1.2 with cipher DHE-RSA-SEED-SHA (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 813843A091B for <emu@ietf.org>; Mon, 26 Oct 2020 05:16:05 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=cisco.com; i=@cisco.com; l=3106; q=dns/txt; s=iport; t=1603714565; x=1604924165; h=mime-version:subject:from:in-reply-to:date:cc: content-transfer-encoding:message-id:references:to; bh=AmZNbqxt19GUwM9g7y0ibAl0d5kJYsYreL+FTbta5No=; b=aHT8tz1/mMTqiRhxhFIUV0IrRi1jaclIbaq5nbDugNV2q2xTvJNWtRlk c934F0LPFxS1arnkY589/EqnACant9azzEg5PxyRY5E33KhuESOzhoXHY S+Yf/thpzjiWEEnw0fRpMnm5f6shttXG9ltsI+SOMGpoPHGo18T6Hw2kE k=;
X-IronPort-Anti-Spam-Filtered: true
X-IronPort-Anti-Spam-Result: =?us-ascii?q?A0D6AADHvJZf/xbLJq1gFgUBAQEBAQE?= =?us-ascii?q?BAQUBAQESAQEBAwMBAQFAgU+CKnBVASASLI1BiA2cJQsBAQENAQEYBhEEAQG?= =?us-ascii?q?ESgKCDCY4EwIDAQELAQEFAQEBAgEGBG2FYQyFcgEBAQMBAQE4NAsFCwsYLic?= =?us-ascii?q?wBhMbgwsBglwgD6s+dIE0hD4BAwIRAQ4JaoRtBoE4jVSCAIERJxyCTT6CXAE?= =?us-ascii?q?BAgGBRBiDSoIsBJAap2yCdIMWhW6RdQMWCaFenjORY4NfAgQGBQIVgWsjgVc?= =?us-ascii?q?zGggbFTsqAYI+PhIZDVeWEjuFQ0ADMAIBNQIGCgEBAwmOSAEB?=
X-IronPort-AV: E=Sophos;i="5.77,419,1596499200"; d="scan'208";a="30637823"
Received: from aer-iport-nat.cisco.com (HELO aer-core-3.cisco.com) ([173.38.203.22]) by aer-iport-1.cisco.com with ESMTP/TLS/DHE-RSA-SEED-SHA; 26 Oct 2020 12:16:01 +0000
Received: from dhcp-10-61-101-216.cisco.com (dhcp-10-61-101-216.cisco.com [10.61.101.216]) by aer-core-3.cisco.com (8.15.2/8.15.2) with ESMTPS id 09QCG06A001621 (version=TLSv1.2 cipher=DHE-RSA-AES256-GCM-SHA384 bits=256 verify=NO); Mon, 26 Oct 2020 12:16:01 GMT
Content-Type: text/plain; charset=us-ascii
Mime-Version: 1.0 (Mac OS X Mail 13.4 \(3608.120.23.2.4\))
From: Eliot Lear <lear@cisco.com>
In-Reply-To: <7E22462D-3668-4F4F-BD66-A125A26B34DC@ericsson.com>
Date: Mon, 26 Oct 2020 13:16:00 +0100
Cc: "emu@ietf.org" <emu@ietf.org>
Content-Transfer-Encoding: quoted-printable
Message-Id: <E32DAFB7-152F-4E04-9C25-7373EA3BB711@cisco.com>
References: <7E22462D-3668-4F4F-BD66-A125A26B34DC@ericsson.com>
To: John Mattsson <john.mattsson=40ericsson.com@dmarc.ietf.org>
X-Mailer: Apple Mail (2.3608.120.23.2.4)
X-Outbound-SMTP-Client: 10.61.101.216, dhcp-10-61-101-216.cisco.com
X-Outbound-Node: aer-core-3.cisco.com
Archived-At: <https://mailarchive.ietf.org/arch/msg/emu/pXpvxLHhZ1Gg-kYnywrG2nvNr14>
Subject: Re: [Emu] draft-ietf-emu-eap-tls13-11: OCSP Stapling
X-BeenThere: emu@ietf.org
X-Mailman-Version: 2.1.29
Precedence: list
List-Id: "EAP Methods Update \(EMU\)" <emu.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/emu>, <mailto:emu-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/emu/>
List-Post: <mailto:emu@ietf.org>
List-Help: <mailto:emu-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/emu>, <mailto:emu-request@ietf.org?subject=subscribe>
X-List-Received-Date: Mon, 26 Oct 2020 12:16:07 -0000

Hi John,

My question is one of pragmatics.  In an offline industrial environment, =
what is expected of the server to accomplish the stapling?  Especially =
if the request is nonced.

Eliot

> On 26 Oct 2020, at 13:08, John Mattsson =
<john.mattsson=3D40ericsson.com@dmarc.ietf.org> wrote:
>=20
> Hi,
>=20
> When this was discussed in the group, it was decided to not only =
mandate revocation checking, but to also mandate OCSP stapling as is it =
often the only viable solution to let an offline peer check the =
revocation status of the server. We had a discussion on must-staple, and =
the decision was to mandate stapling in the draft instead of waiting for =
support of the X.509 must-staple extension. OCSP and OCSP stapling are =
quite well supported already and should be even more well-supported in a =
few years:
>=20
> 1. Basically all TLS implementations support OSCP, and a majority =
support OSCP stapling (Certificate Status Request). Mbed is an exception =
rather than the rule.
>=20
> https://en.wikipedia.org/wiki/Comparison_of_TLS_implementations
>=20
> 2. All browsers (desktop and mobile) support OCSP stapling.
>=20
> =
https://blog.apnic.net/2019/01/15/is-the-web-ready-for-ocsp-must-staple/#:=
~:text=3DOCSP%20Must%2DStaple%20is%20a,Certificate%20Status%20Protocol%20(=
OCSP).
>=20
> 3. NIST SP 800-52 Rev 2 mandates that the server shall support use of =
the Certificate Status Request extension (i.e. OCSP stapling).
>=20
>=20
> - I do not think there is any wiggle room at all in the current =
version of the draft:
>=20
>  "When EAP-TLS is used with TLS 1.3, the peer and server MUST use =
Certificate Status Requests [RFC6066]
>    for the server's certificate chain"
>=20
>  Note that in the current draft it is unspecified how the server =
checks the revocation status of the client's certificate:
>=20
>  "When EAP-TLS is used with TLS 1.3, the server MUST check the =
revocation status of the certificates in the
>    client's certificate chain."
>=20
>=20
> - The X.509 must-staple extension =
(https://tools.ietf.org/html/draft-hallambaker-muststaple-00) is not =
relevant for server certificates in the current EAP-TLS 1.3 draft as =
stapling is already a must. OSCP stapling is not very useful for client =
certs. I do not know if the X.509 must-staple extension is well =
supported or not. It could become relevant for server certs if the =
requirements are softened.
>=20
>=20
> - My view is that OSCP stapling is a very good fit for EAP in =
particular and is well-supported enough to be mandated. Mandating =
stapling for EAP-TLS 1.3 from the start avoids having to rely on the =
X.509 must-staple extension. Any implementation not supporting OCSP =
stapling should implement it together with TLS 1.3. I do not think the =
requirent should be softened, but if it is, my view is that is should be =
softened as little as possible.
>=20
> Cheers,
> John
>=20
> _______________________________________________
> Emu mailing list
> Emu@ietf.org
> https://www.ietf.org/mailman/listinfo/emu


From nobody Mon Oct 26 05:58:21 2020
Return-Path: <john.mattsson@ericsson.com>
X-Original-To: emu@ietfa.amsl.com
Delivered-To: emu@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id B06433A0AD9 for <emu@ietfa.amsl.com>; Mon, 26 Oct 2020 05:58:13 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.102
X-Spam-Level: 
X-Spam-Status: No, score=-2.102 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIMWL_WL_HIGH=-0.001, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, DKIM_VALID_EF=-0.1, RCVD_IN_MSPIKE_H2=-0.001, SPF_PASS=-0.001, URIBL_BLOCKED=0.001] autolearn=unavailable autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (1024-bit key) header.d=ericsson.com
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 nr1qCDJwI5wO for <emu@ietfa.amsl.com>; Mon, 26 Oct 2020 05:58:12 -0700 (PDT)
Received: from EUR04-HE1-obe.outbound.protection.outlook.com (mail-eopbgr70071.outbound.protection.outlook.com [40.107.7.71]) (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 6D7843A0B2E for <emu@ietf.org>; Mon, 26 Oct 2020 05:58:07 -0700 (PDT)
ARC-Seal: i=1; a=rsa-sha256; s=arcselector9901; d=microsoft.com; cv=none; b=WsKzs6mq6JooovWdyhpTi+8/sZHQREkWKE3CAV9RbILmWgw3hRUVuIMFeXiDM1S2OrpQnSEdykzOVpzpPhE0joksS2cnuXtic/CqRGd2zOas2F+qv7FMuX1ctsrz1lmSG+z9lv8770RB3jYQ1an16W04nFkWroKaMM61HjWV3DBpB1u/1pvOZY6YJmo/i/ajCioX+xDmvlzvI80FaLWKm1Gurcn4nGRF8vd78Aa80UXhasRD1RK1reXzKRpZERhmTUN0y5qZpgtWfCEke7j3SXZIF2/AimBiTnVW/3shJ3/iD9P7pu4RjISmiS55yYGX90Qo8emIJhIx5tSI9vogbw==
ARC-Message-Signature: i=1; a=rsa-sha256; c=relaxed/relaxed; d=microsoft.com;  s=arcselector9901; h=From:Date:Subject:Message-ID:Content-Type:MIME-Version:X-MS-Exchange-SenderADCheck; bh=GVG/1ulxc1B3FuX6GJrJQhRTowMTy2nPnAoaQwDzvy8=; b=LpGU08xWDvuOsDMaeldIBZIZcvsPMzEVUWFFyPug/ozGqE7ZeqblhlbX4G8NyzoZBFJ22a/DdKe8oL8knkkd678/KTfLBeeeVGthwPHVQVV94pZ8ZocrxiIHeMqYej0+JK31Y+tu1mhuytqHSSDKfriHnh9z5kdRTexlqXuoJ6WL3Qw7p7fDPHfd76X7wIW8dxl3dVYZIv+qa7ZbsWqjaKWb7UlrRha5f9J2WMRaYvwR5vA9A9nTp69HzDbh6bo8CwKkO6XdnS7iJVNQs8QYWvXx4hZbij6O0h8cRQkFMbn7w1S6SslTC0pNb0hVjA55slCs6fHrZDu221Jszo9dWA==
ARC-Authentication-Results: i=1; mx.microsoft.com 1; spf=pass smtp.mailfrom=ericsson.com; dmarc=pass action=none header.from=ericsson.com; dkim=pass header.d=ericsson.com; arc=none
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=ericsson.com; s=selector1; h=From:Date:Subject:Message-ID:Content-Type:MIME-Version:X-MS-Exchange-SenderADCheck; bh=GVG/1ulxc1B3FuX6GJrJQhRTowMTy2nPnAoaQwDzvy8=; b=gJgRzO+Yl6PAoWpmm3eOVTyhDdP5uKRgoZieP7bAtdTQWMXSSE8cUKM7GHGi/DXOjcqbXKp5Sp4s8ATmJWIr4EymRyIDkykPcfC/KqbHwcim0bBU8rgp7/b14vK60yffpNUaIlh/HhwYDA2Mzjfd6ioSLFFht3HxR4NG+y2uZmg=
Received: from AM6PR07MB4584.eurprd07.prod.outlook.com (2603:10a6:20b:17::24) by AM6PR07MB5254.eurprd07.prod.outlook.com (2603:10a6:20b:62::27) with Microsoft SMTP Server (version=TLS1_2, cipher=TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384) id 15.20.3499.8; Mon, 26 Oct 2020 12:58:00 +0000
Received: from AM6PR07MB4584.eurprd07.prod.outlook.com ([fe80::951:a4c3:7f39:e39c]) by AM6PR07MB4584.eurprd07.prod.outlook.com ([fe80::951:a4c3:7f39:e39c%5]) with mapi id 15.20.3499.015; Mon, 26 Oct 2020 12:58:00 +0000
From: John Mattsson <john.mattsson@ericsson.com>
To: Eliot Lear <lear=40cisco.com@dmarc.ietf.org>
CC: "emu@ietf.org" <emu@ietf.org>
Thread-Topic: [Emu] draft-ietf-emu-eap-tls13-11: OCSP Stapling
Thread-Index: AQHWq5C1GWGefoT7/UmcfGZXldFKNKmpzGYAgAAcgAA=
Date: Mon, 26 Oct 2020 12:58:00 +0000
Message-ID: <82B68018-80A0-461E-8D55-A1232B2D057D@ericsson.com>
References: <7E22462D-3668-4F4F-BD66-A125A26B34DC@ericsson.com> <E32DAFB7-152F-4E04-9C25-7373EA3BB711@cisco.com>
In-Reply-To: <E32DAFB7-152F-4E04-9C25-7373EA3BB711@cisco.com>
Accept-Language: en-US
Content-Language: en-GB
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
user-agent: Microsoft-MacOutlook/16.42.20101102
authentication-results: dmarc.ietf.org; dkim=none (message not signed) header.d=none;dmarc.ietf.org; dmarc=none action=none header.from=ericsson.com;
x-originating-ip: [81.225.97.222]
x-ms-publictraffictype: Email
x-ms-office365-filtering-correlation-id: c0afb587-5306-4f44-96a7-08d879aec4e4
x-ms-traffictypediagnostic: AM6PR07MB5254:
x-microsoft-antispam-prvs: <AM6PR07MB5254F3264EA47DE373DA98AC89190@AM6PR07MB5254.eurprd07.prod.outlook.com>
x-ms-oob-tlc-oobclassifiers: OLM:10000;
x-ms-exchange-senderadcheck: 1
x-microsoft-antispam: BCL:0;
x-microsoft-antispam-message-info: jDiM83roc2JwCbPXr3XYcTSrMBnWeiplCRTU84aEuzuu5so08e8zdBcLk1Bj7u/GKemeHAmcAWVc4gckhef0e8YsVHx6Z56iYVlJDZUJ01Oy5h/CMF/R9vO21h7XvuwDC1jmPahmdtbB7h3Q18bEtuFmYJp++L/5DBZjjHpRqWrwQzJ4NtfwKVoMMndEGAajrX60IK1fAA17z6gQRLojWpsU3UHwBkPh/NuQTQnr90NgaynSGVzGIxJHeesrg9ldquEnKBLbUog3tDzxVnsnfu/tzkWb7tYwDbfroFR+6Xi7fb/OlZTi6qE7wON20Owx+HcnNW6FJKL7LHT7uLvhXlDMeuqYpm4h76EmH3qR1bKz8qXEPD5V9GlC3fMJ4WnzTwN6ko8CYyuOV5I5zLuXRw==
x-forefront-antispam-report: CIP:255.255.255.255; CTRY:; LANG:en; SCL:1; SRV:;  IPV:NLI; SFV:NSPM; H:AM6PR07MB4584.eurprd07.prod.outlook.com; PTR:; CAT:NONE;  SFS:(4636009)(39860400002)(396003)(366004)(346002)(376002)(136003)(6506007)(36756003)(33656002)(5660300002)(478600001)(4326008)(53546011)(966005)(26005)(83380400001)(6512007)(86362001)(6486002)(76116006)(2616005)(91956017)(186003)(66556008)(44832011)(66476007)(316002)(66946007)(8936002)(71200400001)(66446008)(2906002)(8676002)(64756008); DIR:OUT; SFP:1101; 
x-ms-exchange-antispam-messagedata: 1BIb1dgzB08ForDU3KeCAXfr+aGt3ByJ1eFDv1JC9msyueZE14JPqBWJ0l3+6QHsmkfa2zkpmY1YNUXamy/R5QGQ09BgcVwZ6inf6h12fgnP+OlEKosBeiW8JL8dEmWmzaaEsSz2tvqtZLi9T84nCDuqF3Nt0lhq1morCgBH9otUOAOZv18/YugUzJ11iPhtmRHXyCol3bWLka0VFGDoDsHvPt6TBIriYDZ3A7y1056cejpKdFeDOgjZ5bEOtGKQP2V6ufK6ieeAncmXUtcFw1dX9FIihgkP2VzFUa1n4v5h6skrAoxdWA5p8RzthEsECmNsAkRirSd/pY9YWIGHn1kBuOzOr+OOHCfYhsQ/SQIjlpIF+u5DJS4m1pTX5fxcRKIxh01Mv57j6a4n/Jz1+uES4XQ7ncTa8+7gzPdg+swaGgdH9M1eX8H32VzOJwxeBDnL0T5GdldfPJtVYA864nFjKp34RNOVc/vyxd3CAenwfdLvD2ipAQAHGHvZjgTKujAF0wIhmTzaE11gibiHh5vdg7T2eWYBfytyTnCx8yFtPRnlleKnTRiiyqglPap34XozUlgYhvfPrf+UbkHGGLLiRTWCjSp7aOsp2xgfZYf0DCQFJP6Y/UevAratjsTXWhFHEnjMmJMJqJyZfWyqNg==
x-ms-exchange-transport-forked: True
Content-Type: text/plain; charset="utf-8"
Content-ID: <492F521A9A887E4C960853D80C7E1DCE@eurprd07.prod.outlook.com>
Content-Transfer-Encoding: base64
MIME-Version: 1.0
X-OriginatorOrg: ericsson.com
X-MS-Exchange-CrossTenant-AuthAs: Internal
X-MS-Exchange-CrossTenant-AuthSource: AM6PR07MB4584.eurprd07.prod.outlook.com
X-MS-Exchange-CrossTenant-Network-Message-Id: c0afb587-5306-4f44-96a7-08d879aec4e4
X-MS-Exchange-CrossTenant-originalarrivaltime: 26 Oct 2020 12:58:00.6391 (UTC)
X-MS-Exchange-CrossTenant-fromentityheader: Hosted
X-MS-Exchange-CrossTenant-id: 92e84ceb-fbfd-47ab-be52-080c6b87953f
X-MS-Exchange-CrossTenant-mailboxtype: HOSTED
X-MS-Exchange-CrossTenant-userprincipalname: aBoCS+dZm984N+2/1xSLQYle00fOgmgMl3UYymaQvzMpnvMkz3nO8/PZl5t9r24Tel9Y1SzCgGfEp4cYYeBQ1R4dnwU5Vzgzx513AORqINg=
X-MS-Exchange-Transport-CrossTenantHeadersStamped: AM6PR07MB5254
Archived-At: <https://mailarchive.ietf.org/arch/msg/emu/S0vgeSlEI3vMHr8tUR8iXXFMUEQ>
Subject: Re: [Emu] draft-ietf-emu-eap-tls13-11: OCSP Stapling
X-BeenThere: emu@ietf.org
X-Mailman-Version: 2.1.29
Precedence: list
List-Id: "EAP Methods Update \(EMU\)" <emu.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/emu>, <mailto:emu-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/emu/>
List-Post: <mailto:emu@ietf.org>
List-Help: <mailto:emu-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/emu>, <mailto:emu-request@ietf.org?subject=subscribe>
X-List-Received-Date: Mon, 26 Oct 2020 12:58:20 -0000

SGkgRWxpb3QsDQoNClRoZSBFQVAgc2VydmVyIGlzIGV4cGVjdGVkIHRvIGZyZXF1ZW50bHkgcmVx
dWVzdCBhIE9DU1AgcmVzcG9uc2UgZnJvbSB0aGUgT0NTUCByZXNwb25kZXIgKGEgc2VydmVyIHR5
cGljYWxseSBydW4gYnkgdGhlIGNlcnRpZmljYXRlIGlzc3VlcikuIFRoZSBPQ1NQIHJlc3BvbnNl
IGlzIHRoZW4gYWRkZWQgdG8gdGhlIFNlcnZlcnMgQ2VydGlmaWNhdGUgbWVzc2FnZSBhcyBsb25n
IGFzIGl0IGlzIHZhbGlkLiBCZWZvcmUgdGhlIE9DU1AgcmVzcG9uc2UgaXMgY2xvc2UgdG8gZXhw
aXJpbmcsIHRoZSBFQVAgc2VydmVyIHJlcXVlc3RzIGEgbmV3IE9DU1AgcmVzcG9uc2UgZnJvbSB0
aGUgT0NTUCByZXNwb25kZXIuDQoNCkkgYXNzdW1lIHlvdSBtZWFuIHRoZSBjbGllbnQgaXMgb2Zm
bGluZT8gSWYgdXNlIGNhc2VzIHdoZXJlIG5vbmUgb2YgdGhlIGVudGl0aWVzIGNhbiBjb250YWN0
IHRoZSBPQ1NQIHJlc3BvbmRlciBpcyBpbiBzY29wZSwgT0NTUCBzdGFwbGluZyBkb2VzIG5vdCB3
b3JrLg0KDQpPQ1NQIE5vbmNlIGRvZXMgbm90IHdvcmsgd2l0aCBPQ1NQIHN0YXBsaW5nLiBJZiB5
b3Ugd2FudCB5b3UgcmV2b2NhdGlvbiBkYXRhIHRvIGJlIHJlYWwtdGltZSB5b3UgbmVlZCB0byBt
YWtlIGFuIG9ubGluZSBPQ1NQIHJlcXVlc3QtcmVzcG9uc2UgdG8gdGhlIE9DU1AgcmVzcG9uZGVy
Lg0KDQpKb2huDQoNCu+7vy0tLS0tT3JpZ2luYWwgTWVzc2FnZS0tLS0tDQpGcm9tOiBFbGlvdCBM
ZWFyIDxsZWFyPTQwY2lzY28uY29tQGRtYXJjLmlldGYub3JnPg0KRGF0ZTogTW9uZGF5LCAyNiBP
Y3RvYmVyIDIwMjAgYXQgMTM6MTYNClRvOiBKb2huIE1hdHRzc29uIDxqb2huLm1hdHRzc29uQGVy
aWNzc29uLmNvbT4NCkNjOiAiZW11QGlldGYub3JnIiA8ZW11QGlldGYub3JnPg0KU3ViamVjdDog
UmU6IFtFbXVdIGRyYWZ0LWlldGYtZW11LWVhcC10bHMxMy0xMTogT0NTUCBTdGFwbGluZw0KDQpI
aSBKb2huLA0KDQpNeSBxdWVzdGlvbiBpcyBvbmUgb2YgcHJhZ21hdGljcy4gIEluIGFuIG9mZmxp
bmUgaW5kdXN0cmlhbCBlbnZpcm9ubWVudCwgd2hhdCBpcyBleHBlY3RlZCBvZiB0aGUgc2VydmVy
IHRvIGFjY29tcGxpc2ggdGhlIHN0YXBsaW5nPyAgRXNwZWNpYWxseSBpZiB0aGUgcmVxdWVzdCBp
cyBub25jZWQuDQoNCkVsaW90DQoNCj4gT24gMjYgT2N0IDIwMjAsIGF0IDEzOjA4LCBKb2huIE1h
dHRzc29uIDxqb2huLm1hdHRzc29uPTQwZXJpY3Nzb24uY29tQGRtYXJjLmlldGYub3JnPiB3cm90
ZToNCj4gDQo+IEhpLA0KPiANCj4gV2hlbiB0aGlzIHdhcyBkaXNjdXNzZWQgaW4gdGhlIGdyb3Vw
LCBpdCB3YXMgZGVjaWRlZCB0byBub3Qgb25seSBtYW5kYXRlIHJldm9jYXRpb24gY2hlY2tpbmcs
IGJ1dCB0byBhbHNvIG1hbmRhdGUgT0NTUCBzdGFwbGluZyBhcyBpcyBpdCBvZnRlbiB0aGUgb25s
eSB2aWFibGUgc29sdXRpb24gdG8gbGV0IGFuIG9mZmxpbmUgcGVlciBjaGVjayB0aGUgcmV2b2Nh
dGlvbiBzdGF0dXMgb2YgdGhlIHNlcnZlci4gV2UgaGFkIGEgZGlzY3Vzc2lvbiBvbiBtdXN0LXN0
YXBsZSwgYW5kIHRoZSBkZWNpc2lvbiB3YXMgdG8gbWFuZGF0ZSBzdGFwbGluZyBpbiB0aGUgZHJh
ZnQgaW5zdGVhZCBvZiB3YWl0aW5nIGZvciBzdXBwb3J0IG9mIHRoZSBYLjUwOSBtdXN0LXN0YXBs
ZSBleHRlbnNpb24uIE9DU1AgYW5kIE9DU1Agc3RhcGxpbmcgYXJlIHF1aXRlIHdlbGwgc3VwcG9y
dGVkIGFscmVhZHkgYW5kIHNob3VsZCBiZSBldmVuIG1vcmUgd2VsbC1zdXBwb3J0ZWQgaW4gYSBm
ZXcgeWVhcnM6DQo+IA0KPiAxLiBCYXNpY2FsbHkgYWxsIFRMUyBpbXBsZW1lbnRhdGlvbnMgc3Vw
cG9ydCBPU0NQLCBhbmQgYSBtYWpvcml0eSBzdXBwb3J0IE9TQ1Agc3RhcGxpbmcgKENlcnRpZmlj
YXRlIFN0YXR1cyBSZXF1ZXN0KS4gTWJlZCBpcyBhbiBleGNlcHRpb24gcmF0aGVyIHRoYW4gdGhl
IHJ1bGUuDQo+IA0KPiBodHRwczovL2VuLndpa2lwZWRpYS5vcmcvd2lraS9Db21wYXJpc29uX29m
X1RMU19pbXBsZW1lbnRhdGlvbnMNCj4gDQo+IDIuIEFsbCBicm93c2VycyAoZGVza3RvcCBhbmQg
bW9iaWxlKSBzdXBwb3J0IE9DU1Agc3RhcGxpbmcuDQo+IA0KPiBodHRwczovL2Jsb2cuYXBuaWMu
bmV0LzIwMTkvMDEvMTUvaXMtdGhlLXdlYi1yZWFkeS1mb3Itb2NzcC1tdXN0LXN0YXBsZS8jOn46
dGV4dD1PQ1NQJTIwTXVzdCUyRFN0YXBsZSUyMGlzJTIwYSxDZXJ0aWZpY2F0ZSUyMFN0YXR1cyUy
MFByb3RvY29sJTIwKE9DU1ApLg0KPiANCj4gMy4gTklTVCBTUCA4MDAtNTIgUmV2IDIgbWFuZGF0
ZXMgdGhhdCB0aGUgc2VydmVyIHNoYWxsIHN1cHBvcnQgdXNlIG9mIHRoZSBDZXJ0aWZpY2F0ZSBT
dGF0dXMgUmVxdWVzdCBleHRlbnNpb24gKGkuZS4gT0NTUCBzdGFwbGluZykuDQo+IA0KPiANCj4g
LSBJIGRvIG5vdCB0aGluayB0aGVyZSBpcyBhbnkgd2lnZ2xlIHJvb20gYXQgYWxsIGluIHRoZSBj
dXJyZW50IHZlcnNpb24gb2YgdGhlIGRyYWZ0Og0KPiANCj4gICJXaGVuIEVBUC1UTFMgaXMgdXNl
ZCB3aXRoIFRMUyAxLjMsIHRoZSBwZWVyIGFuZCBzZXJ2ZXIgTVVTVCB1c2UgQ2VydGlmaWNhdGUg
U3RhdHVzIFJlcXVlc3RzIFtSRkM2MDY2XQ0KPiAgICBmb3IgdGhlIHNlcnZlcidzIGNlcnRpZmlj
YXRlIGNoYWluIg0KPiANCj4gIE5vdGUgdGhhdCBpbiB0aGUgY3VycmVudCBkcmFmdCBpdCBpcyB1
bnNwZWNpZmllZCBob3cgdGhlIHNlcnZlciBjaGVja3MgdGhlIHJldm9jYXRpb24gc3RhdHVzIG9m
IHRoZSBjbGllbnQncyBjZXJ0aWZpY2F0ZToNCj4gDQo+ICAiV2hlbiBFQVAtVExTIGlzIHVzZWQg
d2l0aCBUTFMgMS4zLCB0aGUgc2VydmVyIE1VU1QgY2hlY2sgdGhlIHJldm9jYXRpb24gc3RhdHVz
IG9mIHRoZSBjZXJ0aWZpY2F0ZXMgaW4gdGhlDQo+ICAgIGNsaWVudCdzIGNlcnRpZmljYXRlIGNo
YWluLiINCj4gDQo+IA0KPiAtIFRoZSBYLjUwOSBtdXN0LXN0YXBsZSBleHRlbnNpb24gKGh0dHBz
Oi8vdG9vbHMuaWV0Zi5vcmcvaHRtbC9kcmFmdC1oYWxsYW1iYWtlci1tdXN0c3RhcGxlLTAwKSBp
cyBub3QgcmVsZXZhbnQgZm9yIHNlcnZlciBjZXJ0aWZpY2F0ZXMgaW4gdGhlIGN1cnJlbnQgRUFQ
LVRMUyAxLjMgZHJhZnQgYXMgc3RhcGxpbmcgaXMgYWxyZWFkeSBhIG11c3QuIE9TQ1Agc3RhcGxp
bmcgaXMgbm90IHZlcnkgdXNlZnVsIGZvciBjbGllbnQgY2VydHMuIEkgZG8gbm90IGtub3cgaWYg
dGhlIFguNTA5IG11c3Qtc3RhcGxlIGV4dGVuc2lvbiBpcyB3ZWxsIHN1cHBvcnRlZCBvciBub3Qu
IEl0IGNvdWxkIGJlY29tZSByZWxldmFudCBmb3Igc2VydmVyIGNlcnRzIGlmIHRoZSByZXF1aXJl
bWVudHMgYXJlIHNvZnRlbmVkLg0KPiANCj4gDQo+IC0gTXkgdmlldyBpcyB0aGF0IE9TQ1Agc3Rh
cGxpbmcgaXMgYSB2ZXJ5IGdvb2QgZml0IGZvciBFQVAgaW4gcGFydGljdWxhciBhbmQgaXMgd2Vs
bC1zdXBwb3J0ZWQgZW5vdWdoIHRvIGJlIG1hbmRhdGVkLiBNYW5kYXRpbmcgc3RhcGxpbmcgZm9y
IEVBUC1UTFMgMS4zIGZyb20gdGhlIHN0YXJ0IGF2b2lkcyBoYXZpbmcgdG8gcmVseSBvbiB0aGUg
WC41MDkgbXVzdC1zdGFwbGUgZXh0ZW5zaW9uLiBBbnkgaW1wbGVtZW50YXRpb24gbm90IHN1cHBv
cnRpbmcgT0NTUCBzdGFwbGluZyBzaG91bGQgaW1wbGVtZW50IGl0IHRvZ2V0aGVyIHdpdGggVExT
IDEuMy4gSSBkbyBub3QgdGhpbmsgdGhlIHJlcXVpcmVudCBzaG91bGQgYmUgc29mdGVuZWQsIGJ1
dCBpZiBpdCBpcywgbXkgdmlldyBpcyB0aGF0IGlzIHNob3VsZCBiZSBzb2Z0ZW5lZCBhcyBsaXR0
bGUgYXMgcG9zc2libGUuDQo+IA0KPiBDaGVlcnMsDQo+IEpvaG4NCj4gDQo+IF9fX19fX19fX19f
X19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fDQo+IEVtdSBtYWlsaW5nIGxpc3QN
Cj4gRW11QGlldGYub3JnDQo+IGh0dHBzOi8vd3d3LmlldGYub3JnL21haWxtYW4vbGlzdGluZm8v
ZW11DQoNCg0K


From nobody Mon Oct 26 06:42:49 2020
Return-Path: <lear@cisco.com>
X-Original-To: emu@ietfa.amsl.com
Delivered-To: emu@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id EB9423A05A6 for <emu@ietfa.amsl.com>; Mon, 26 Oct 2020 06:42:47 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -9.601
X-Spam-Level: 
X-Spam-Status: No, score=-9.601 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIMWL_WL_MED=-0.001, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, DKIM_VALID_EF=-0.1, SPF_PASS=-0.001, URIBL_BLOCKED=0.001, USER_IN_DEF_DKIM_WL=-7.5] autolearn=unavailable autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (1024-bit key) header.d=cisco.com
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 wUr-OXTfcFYp for <emu@ietfa.amsl.com>; Mon, 26 Oct 2020 06:42:46 -0700 (PDT)
Received: from aer-iport-1.cisco.com (aer-iport-1.cisco.com [173.38.203.51]) (using TLSv1.2 with cipher DHE-RSA-SEED-SHA (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 6C9F73A0B02 for <emu@ietf.org>; Mon, 26 Oct 2020 06:42:46 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=cisco.com; i=@cisco.com; l=1472; q=dns/txt; s=iport; t=1603719766; x=1604929366; h=mime-version:subject:from:in-reply-to:date:cc: content-transfer-encoding:message-id:references:to; bh=QP0YOI3wCG/BjS9XYm15SnOEb+hQOeYn1pIRb7CisN0=; b=h2YOVBR79I7kq3KFgJd+Za7XfguTH0wF65JasNrJwqO8YR9B0K10MFw+ tLPGbPHXiaj/IlcX9gQvnp/tt98zZZ8Lp9k2UWIFFyUv/uEtibhHYcdgB z2wI1JkMaCmd75WoRVTgy2bvP6eD/rFqFco+MK1/2nI3QNGJLPzyQb7Fb k=;
X-IronPort-Anti-Spam-Filtered: true
X-IronPort-Anti-Spam-Result: =?us-ascii?q?A0BbAADK0ZZf/xbLJq1gGgEBAQEBAQE?= =?us-ascii?q?BAQEDAQEBARIBAQEBAgIBAQEBQIFPgiqBRQEgEiyNQYgNnCULAQEBDQEBLwQ?= =?us-ascii?q?BAYRKAoIMJjgTAgMBAQsBAQUBAQECAQYEbYVthXIBAQEDATo/BQsLGC5XBhO?= =?us-ascii?q?DJoJdIKs1dIE0hVeEc4E4jVSCAIERJxyCTT6CXASBRRiDSoIsBLgGgnSDFpd?= =?us-ascii?q?jAx+DF4oNjmSFVrAWg18CBAYFAhWBayOBVzMaCBsVZQGCPj4SGQ2cZ0ADMAI?= =?us-ascii?q?BNQIGCgEBAwmNaV8BAQ?=
X-IronPort-AV: E=Sophos;i="5.77,419,1596499200"; d="scan'208";a="30639047"
Received: from aer-iport-nat.cisco.com (HELO aer-core-4.cisco.com) ([173.38.203.22]) by aer-iport-1.cisco.com with ESMTP/TLS/DHE-RSA-SEED-SHA; 26 Oct 2020 13:42:42 +0000
Received: from dhcp-10-61-101-216.cisco.com (dhcp-10-61-101-216.cisco.com [10.61.101.216]) by aer-core-4.cisco.com (8.15.2/8.15.2) with ESMTPS id 09QDgftN015953 (version=TLSv1.2 cipher=DHE-RSA-AES256-GCM-SHA384 bits=256 verify=NO); Mon, 26 Oct 2020 13:42:42 GMT
Content-Type: text/plain; charset=us-ascii
Mime-Version: 1.0 (Mac OS X Mail 13.4 \(3608.120.23.2.4\))
From: Eliot Lear <lear@cisco.com>
In-Reply-To: <82B68018-80A0-461E-8D55-A1232B2D057D@ericsson.com>
Date: Mon, 26 Oct 2020 14:42:41 +0100
Cc: "emu@ietf.org" <emu@ietf.org>
Content-Transfer-Encoding: quoted-printable
Message-Id: <8B99541A-0C10-48C5-825D-5BC219684BB4@cisco.com>
References: <7E22462D-3668-4F4F-BD66-A125A26B34DC@ericsson.com> <E32DAFB7-152F-4E04-9C25-7373EA3BB711@cisco.com> <82B68018-80A0-461E-8D55-A1232B2D057D@ericsson.com>
To: John Mattsson <john.mattsson=40ericsson.com@dmarc.ietf.org>
X-Mailer: Apple Mail (2.3608.120.23.2.4)
X-Outbound-SMTP-Client: 10.61.101.216, dhcp-10-61-101-216.cisco.com
X-Outbound-Node: aer-core-4.cisco.com
Archived-At: <https://mailarchive.ietf.org/arch/msg/emu/30qJHbHxFBL3REEHEJ8easg3GGs>
Subject: Re: [Emu] draft-ietf-emu-eap-tls13-11: OCSP Stapling
X-BeenThere: emu@ietf.org
X-Mailman-Version: 2.1.29
Precedence: list
List-Id: "EAP Methods Update \(EMU\)" <emu.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/emu>, <mailto:emu-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/emu/>
List-Post: <mailto:emu@ietf.org>
List-Help: <mailto:emu-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/emu>, <mailto:emu-request@ietf.org?subject=subscribe>
X-List-Received-Date: Mon, 26 Oct 2020 13:42:48 -0000

Thanks, John.  Please see below:

> On 26 Oct 2020, at 13:58, John Mattsson =
<john.mattsson=3D40ericsson.com@dmarc.ietf.org> wrote:
>=20
> Hi Eliot,
>=20
> The EAP server is expected to frequently request a OCSP response from =
the OCSP responder (a server typically run by the certificate issuer). =
The OCSP response is then added to the Servers Certificate message as =
long as it is valid. Before the OCSP response is close to expiring, the =
EAP server requests a new OCSP response from the OCSP responder.
>=20

Right.  What this is saying is that a local deployment MUST run an OCSP =
responder.  If that OCSP responder is unavailable, then what?  Now =
imagine we are discussing critical infrastructure where the responder is =
not in the same room, and there are network connectivity problems.  The =
device joining the network needs local access and that is it.  Does that =
mean it should not use EAP-TLS?  Or are we saying that they MUST use =
naked public keys?

> I assume you mean the client is offline? If use cases where none of =
the entities can contact the OCSP responder is in scope, OCSP stapling =
does not work.

Right.  So then what?  Fail?

For many devices the manufacturers will be unable to predict whether a =
device will or will not have direct access to anything.  It specific to =
deployment circumstances.  Also, running an OCSP server is something =
that will be very new for many enterprises.

Eliot=


From nobody Mon Oct 26 07:06:31 2020
Return-Path: <mcr+ietf@sandelman.ca>
X-Original-To: emu@ietfa.amsl.com
Delivered-To: emu@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 3D0753A0B98 for <emu@ietfa.amsl.com>; Mon, 26 Oct 2020 07:06:30 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.899
X-Spam-Level: 
X-Spam-Status: No, score=-1.899 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, SPF_HELO_NONE=0.001, SPF_PASS=-0.001, URIBL_BLOCKED=0.001] autolearn=unavailable autolearn_force=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 TBqHQJM6ta5S for <emu@ietfa.amsl.com>; Mon, 26 Oct 2020 07:06:28 -0700 (PDT)
Received: from tuna.sandelman.ca (tuna.sandelman.ca [IPv6:2607:f0b0:f:3:216:3eff:fe7c:d1f3]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 19DF83A0BA5 for <emu@ietf.org>; Mon, 26 Oct 2020 07:06:27 -0700 (PDT)
Received: from localhost (localhost [127.0.0.1]) by tuna.sandelman.ca (Postfix) with ESMTP id 22B1F389D6; Mon, 26 Oct 2020 10:13:01 -0400 (EDT)
Received: from tuna.sandelman.ca ([127.0.0.1]) by localhost (localhost [127.0.0.1]) (amavisd-new, port 10024) with LMTP id T4kMAvg4sZok; Mon, 26 Oct 2020 10:13:00 -0400 (EDT)
Received: from sandelman.ca (obiwan.sandelman.ca [IPv6:2607:f0b0:f:2::247]) by tuna.sandelman.ca (Postfix) with ESMTP id A1456389D0; Mon, 26 Oct 2020 10:13:00 -0400 (EDT)
Received: from localhost (localhost [IPv6:::1]) by sandelman.ca (Postfix) with ESMTP id 05EA898E; Mon, 26 Oct 2020 10:06:26 -0400 (EDT)
From: Michael Richardson <mcr+ietf@sandelman.ca>
To: John Mattsson <john.mattsson=40ericsson.com@dmarc.ietf.org>
cc: "emu\@ietf.org" <emu@ietf.org>
In-Reply-To: <7E22462D-3668-4F4F-BD66-A125A26B34DC@ericsson.com>
References: <7E22462D-3668-4F4F-BD66-A125A26B34DC@ericsson.com>
X-Mailer: MH-E 8.6+git; nmh 1.7+dev; GNU Emacs 26.1
X-Face: $\n1pF)h^`}$H>Hk{L"x@)JS7<%Az}5RyS@k9X%29-lHB$Ti.V>2bi.~ehC0; <'$9xN5Ub# z!G,p`nR&p7Fz@^UXIn156S8.~^@MJ*mMsD7=QFeq%AL4m<nPbLgmtKK-5dC@#:k
MIME-Version: 1.0
Content-Type: multipart/signed; boundary="=-=-="; micalg=pgp-sha512; protocol="application/pgp-signature"
Date: Mon, 26 Oct 2020 10:06:25 -0400
Message-ID: <8623.1603721185@localhost>
Archived-At: <https://mailarchive.ietf.org/arch/msg/emu/bjz01IbIUrFHFfVBtSKICoKyilU>
Subject: Re: [Emu] draft-ietf-emu-eap-tls13-11: OCSP Stapling
X-BeenThere: emu@ietf.org
X-Mailman-Version: 2.1.29
Precedence: list
List-Id: "EAP Methods Update \(EMU\)" <emu.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/emu>, <mailto:emu-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/emu/>
List-Post: <mailto:emu@ietf.org>
List-Help: <mailto:emu-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/emu>, <mailto:emu-request@ietf.org?subject=subscribe>
X-List-Received-Date: Mon, 26 Oct 2020 14:06:30 -0000

--=-=-=
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: quoted-printable


John Mattsson <john.mattsson=3D40ericsson.com@dmarc.ietf.org> wrote:
    > 1. Basically all TLS implementations support OSCP, and a majority
    > support OSCP stapling (Certificate Status Request). Mbed is an
    > exception rather than the rule.

Is this for server and client certificates, or just server certificates?
It seems that getting the client certificate staple would be difficult for
offline clients :-)

    > https://en.wikipedia.org/wiki/Comparison_of_TLS_implementations

Also, consider that an mbedtls EAP client could just not process the OCSP+S=
taple
for now.  That would be non-compliant, but it would work.
(The opposite for the server is not the case)

    > 3. NIST SP 800-52 Rev 2 mandates that the server shall support use of
    > the Certificate Status Request extension (i.e. OCSP stapling).

    > - I do not think there is any wiggle room at all in the current versi=
on of the draft:

    > "When EAP-TLS is used with TLS 1.3, the peer and server MUST use Cert=
ificate Status Requests [RFC6066]
    > for the server's certificate chain"

    > Note that in the current draft it is unspecified how the server checks
    > the revocation status of the client's certificate:

    > "When EAP-TLS is used with TLS 1.3, the server MUST check the
    > revocation status of the certificates in the client's certificate cha=
in."

So, OCSP would comply work, but insisting on stapling would be dumb.

    > - My view is that OSCP stapling is a very good fit for EAP in
    > particular and is well-supported enough to be mandated. Mandating
    > stapling for EAP-TLS 1.3 from the start avoids having to rely on the
    > X.509 must-staple extension. Any implementation not supporting OCSP
    > stapling should implement it together with TLS 1.3. I do not think the
    > requirent should be softened, but if it is, my view is that is should
    > be softened as little as possible.

=2D-
Michael Richardson <mcr+IETF@sandelman.ca>   . o O ( IPv6 I=C3=B8T consulti=
ng )
           Sandelman Software Works Inc, Ottawa and Worldwide

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

-----BEGIN PGP SIGNATURE-----

iQEzBAEBCgAdFiEEbsyLEzg/qUTA43uogItw+93Q3WUFAl+W1+EACgkQgItw+93Q
3WXfvQf/eEDuJH0QXQCHxc0P/kk47QR2POZVfn/KuLVB1RyBA2Cy0/qeF+iH+6+o
cTuMeOKT6f5+PN5zW/D+em4igWIvjH/vBgsxvvlR27AgqNWf/Ltk46xvR8Ejg8wh
T0jgnP85AihsrPxLFMZPZWqBHceURzZna3N3FyQHRcEimcvMNxuwlHETAMWxGYTu
uXWh6aNQNr8ZoanG9yvJhfeO3KiIm7Dr/nAFJS6TKNj4x+onRe0rxuFrgBLJmzwN
HsXO0jbeH9tnQ+2dIVTMwAcZbFzdfamYV0gY5w5ai36dYhI89yqHIg57zIWBKwWT
K6FMFR+kdzkRqveGp1PP9aPypmx91g==
=IAR4
-----END PGP SIGNATURE-----
--=-=-=--


From nobody Mon Oct 26 07:19:59 2020
Return-Path: <mcr+ietf@sandelman.ca>
X-Original-To: emu@ietfa.amsl.com
Delivered-To: emu@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id C254C3A0BB2 for <emu@ietfa.amsl.com>; Mon, 26 Oct 2020 07:19:57 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.898
X-Spam-Level: 
X-Spam-Status: No, score=-1.898 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RCVD_IN_DNSWL_BLOCKED=0.001, SPF_HELO_NONE=0.001, SPF_PASS=-0.001, URIBL_BLOCKED=0.001] autolearn=ham autolearn_force=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 nbAmOkPtkEXr for <emu@ietfa.amsl.com>; Mon, 26 Oct 2020 07:19:56 -0700 (PDT)
Received: from tuna.sandelman.ca (tuna.sandelman.ca [IPv6:2607:f0b0:f:3:216:3eff:fe7c:d1f3]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id D9D283A0BB0 for <emu@ietf.org>; Mon, 26 Oct 2020 07:19:55 -0700 (PDT)
Received: from localhost (localhost [127.0.0.1]) by tuna.sandelman.ca (Postfix) with ESMTP id 77648389C9; Mon, 26 Oct 2020 10:26:29 -0400 (EDT)
Received: from tuna.sandelman.ca ([127.0.0.1]) by localhost (localhost [127.0.0.1]) (amavisd-new, port 10024) with LMTP id ZvBz4wc9dlkg; Mon, 26 Oct 2020 10:26:29 -0400 (EDT)
Received: from sandelman.ca (obiwan.sandelman.ca [IPv6:2607:f0b0:f:2::247]) by tuna.sandelman.ca (Postfix) with ESMTP id F4058389AC; Mon, 26 Oct 2020 10:26:28 -0400 (EDT)
Received: from localhost (localhost [IPv6:::1]) by sandelman.ca (Postfix) with ESMTP id 51C4D493; Mon, 26 Oct 2020 10:19:54 -0400 (EDT)
From: Michael Richardson <mcr+ietf@sandelman.ca>
To: Eliot Lear <lear=40cisco.com@dmarc.ietf.org>, John Mattsson <john.mattsson=40ericsson.com@dmarc.ietf.org>, "emu\@ietf.org" <emu@ietf.org>
In-Reply-To: <8B99541A-0C10-48C5-825D-5BC219684BB4@cisco.com>
References: <7E22462D-3668-4F4F-BD66-A125A26B34DC@ericsson.com> <E32DAFB7-152F-4E04-9C25-7373EA3BB711@cisco.com> <82B68018-80A0-461E-8D55-A1232B2D057D@ericsson.com> <8B99541A-0C10-48C5-825D-5BC219684BB4@cisco.com>
X-Mailer: MH-E 8.6+git; nmh 1.7+dev; GNU Emacs 26.1
X-Face: $\n1pF)h^`}$H>Hk{L"x@)JS7<%Az}5RyS@k9X%29-lHB$Ti.V>2bi.~ehC0; <'$9xN5Ub# z!G,p`nR&p7Fz@^UXIn156S8.~^@MJ*mMsD7=QFeq%AL4m<nPbLgmtKK-5dC@#:k
MIME-Version: 1.0
Content-Type: multipart/signed; boundary="=-=-="; micalg=pgp-sha512; protocol="application/pgp-signature"
Date: Mon, 26 Oct 2020 10:19:54 -0400
Message-ID: <11997.1603721994@localhost>
Archived-At: <https://mailarchive.ietf.org/arch/msg/emu/w97VeY3_4NDmB2l-1JmXl7T1m_w>
Subject: Re: [Emu] draft-ietf-emu-eap-tls13-11: OCSP Stapling
X-BeenThere: emu@ietf.org
X-Mailman-Version: 2.1.29
Precedence: list
List-Id: "EAP Methods Update \(EMU\)" <emu.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/emu>, <mailto:emu-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/emu/>
List-Post: <mailto:emu@ietf.org>
List-Help: <mailto:emu-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/emu>, <mailto:emu-request@ietf.org?subject=subscribe>
X-List-Received-Date: Mon, 26 Oct 2020 14:19:58 -0000

--=-=-=
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: quoted-printable


Eliot Lear <lear=3D40cisco.com@dmarc.ietf.org> wrote:
    >> The EAP server is expected to frequently request a OCSP response from
    >>the OCSP responder (a server typically run by the certificate
    >>issuer). The OCSP response is then added to the Servers Certificate
    >>message as long as it is valid. Before the OCSP response is close to
    >>expiring, the EAP server requests a new OCSP response from the OCSP
    >>responder.

    > Right.  What this is saying is that a local deployment MUST run an OC=
SP
    > responder.  If that OCSP responder is unavailable, then what?  Now
    > imagine we are discussing critical infrastructure where the responder
    > is not in the same room, and there are network connectivity problems.
    > The device joining the network needs local access and that is it.  Do=
es
    > that mean it should not use EAP-TLS?  Or are we saying that they MUST
    > use naked public keys?

No.  There are several steps before we get to raw public keys.

The first is that the duration of the Staples could be lengthed to accomoda=
te
anticipated down time for the (now) critical OCSP responder.
A second part is that perhaps staples could be provisioned in advance for t=
he
server to cover for planned maintenance periods.  I don't imagine this is in
any protocol, but could be added.

The second is, I think, that the EAP server (Authentication Server), would =
run
an OCSP responder locally so that it can mint it's own staples.
AFAIK, each certificate can point to a different OCSP signer.
While this degenerate case of Authentication Server + OCSP Signer on the sa=
me
machine is kinda dumb from a overall security point of view, it's still
better than raw public keys.  If the OCSP signer is moved to some TPM then
there is a win.  Not all TPMs can provide the performance required to handle
the server certificate, but resigning an OCSP Staple once every ten minutes
or something shouldn't be a problem.

The third is, I think, that the EAP server runs an entirely self-contained
private CA.  The OCSP responder is now clearly an integral part of the local
system.

Do we need to write an Operational Considerations document here?

    > For many devices the manufacturers will be unable to predict whether a
    > device will or will not have direct access to anything.  It specific =
to
    > deployment circumstances.  Also, running an OCSP server is something
    > that will be very new for many enterprises.


=2D-
Michael Richardson <mcr+IETF@sandelman.ca>   . o O ( IPv6 I=C3=B8T consulti=
ng )
           Sandelman Software Works Inc, Ottawa and Worldwide

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

-----BEGIN PGP SIGNATURE-----

iQEzBAEBCgAdFiEEbsyLEzg/qUTA43uogItw+93Q3WUFAl+W2woACgkQgItw+93Q
3WV37Af/Sto6xYxL8GzziCHUfj++pk0Sh9cIRYjBI+hHFZCFmZR6n9WoJ3ZwS4EA
GZjIM8+86TQdA79mzgbVKgiBi1IXeT1m60Rl16YRg3IwshVuBMCPXu3ir1rte5CB
+osw5xzGrHfMBSbtLghfkZA1CjUPDGIlclwZLrTbbPbeLvdI6MBJR2IWXTRuIoJJ
eT93OLjjmzi1Q9RvEhwLIpqrnT40ocDKed5q9xhwFC5eL6XUd7W7zFZYgyBzsrl1
cQWiC5mspm0c5v1rc2ju8+DQqT1uzHlYtaG1lkA+5ACxO8ruO8wMvMx8NRxX9cjZ
8XdAZdBAGNFcGXUmLGM7QZeLqBbBhw==
=dfCj
-----END PGP SIGNATURE-----
--=-=-=--


From nobody Mon Oct 26 07:31:29 2020
Return-Path: <lear@cisco.com>
X-Original-To: emu@ietfa.amsl.com
Delivered-To: emu@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 295DF3A0BD9 for <emu@ietfa.amsl.com>; Mon, 26 Oct 2020 07:31:28 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -9.601
X-Spam-Level: 
X-Spam-Status: No, score=-9.601 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIMWL_WL_MED=-0.001, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, DKIM_VALID_EF=-0.1, SPF_PASS=-0.001, URIBL_BLOCKED=0.001, USER_IN_DEF_DKIM_WL=-7.5] autolearn=unavailable autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (1024-bit key) header.d=cisco.com
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 IEhZw_KCtkF3 for <emu@ietfa.amsl.com>; Mon, 26 Oct 2020 07:31:25 -0700 (PDT)
Received: from aer-iport-1.cisco.com (aer-iport-1.cisco.com [173.38.203.51]) (using TLSv1.2 with cipher DHE-RSA-SEED-SHA (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 0F1673A0BCF for <emu@ietf.org>; Mon, 26 Oct 2020 07:31:24 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=cisco.com; i=@cisco.com; l=3985; q=dns/txt; s=iport; t=1603722685; x=1604932285; h=from:message-id:mime-version:subject:date:in-reply-to:cc: to:references; bh=OF8v9IaA2upVMfWi+zh4cXKXDLsyCyVBJyKZahNAub0=; b=A8dXJoyclCOSlp69DTEPk2HMxlxiG3FWYJu72b4fEeDbW0TEu8OI3qqd BGE7cXGbgUVFRolUfmGDYB/wqPAVNOwHM4UGMco6C6obRLqUnbisPLHC4 umNUHqVpDPAXZNL1LZInCYV6SKcAOc9B4kZCK9E5YOkv82+z6yZ33yjr/ w=;
X-Files: signature.asc : 488
X-IronPort-Anti-Spam-Filtered: true
X-IronPort-Anti-Spam-Result: =?us-ascii?q?A0CIAACn25Zf/xbLJq1gGgEBAQEBAQE?= =?us-ascii?q?BAQEDAQEBARIBAQEBAgIBAQEBgg8CgiiBRQEgEiyEPIkFh2cmnCUEBwEBAQo?= =?us-ascii?q?DAQEvBAEBhEoCggwmOQUNAgMBAQsBAQUBAQECAQYEbYVthXIBAQEDASNWBQs?= =?us-ascii?q?LGCoCAlcGEx6DCAGCXCCmLXaBMoVXhGMQgTiBU4wBggCBEScMEIJNPoJcBIF?= =?us-ascii?q?Fgy8zgiwEkCqLe5thgnSDFoE3liwDH6FesBaDXwIEBgUCFYFsIoFXMxoIGxV?= =?us-ascii?q?lAYI+PhIZDZxnQAMwAjYCBgEJAQEDCY5IAQE?=
X-IronPort-AV: E=Sophos;i="5.77,419,1596499200";  d="asc'?scan'208";a="30639873"
Received: from aer-iport-nat.cisco.com (HELO aer-core-3.cisco.com) ([173.38.203.22]) by aer-iport-1.cisco.com with ESMTP/TLS/DHE-RSA-SEED-SHA; 26 Oct 2020 14:31:21 +0000
Received: from dhcp-10-61-101-216.cisco.com (dhcp-10-61-101-216.cisco.com [10.61.101.216]) by aer-core-3.cisco.com (8.15.2/8.15.2) with ESMTPS id 09QEVKNf001372 (version=TLSv1.2 cipher=DHE-RSA-AES256-GCM-SHA384 bits=256 verify=NO); Mon, 26 Oct 2020 14:31:20 GMT
From: Eliot Lear <lear@cisco.com>
Message-Id: <68AB850D-1695-447C-86CF-ACCEA92662E8@cisco.com>
Content-Type: multipart/signed; boundary="Apple-Mail=_6EB101DF-F1A8-413D-A250-E02DFFDB6E43"; protocol="application/pgp-signature"; micalg=pgp-sha256
Mime-Version: 1.0 (Mac OS X Mail 13.4 \(3608.120.23.2.4\))
Date: Mon, 26 Oct 2020 15:31:19 +0100
In-Reply-To: <11997.1603721994@localhost>
Cc: Eliot Lear <lear=40cisco.com@dmarc.ietf.org>, John Mattsson <john.mattsson=40ericsson.com@dmarc.ietf.org>, "emu@ietf.org" <emu@ietf.org>
To: Michael Richardson <mcr+ietf@sandelman.ca>
References: <7E22462D-3668-4F4F-BD66-A125A26B34DC@ericsson.com> <E32DAFB7-152F-4E04-9C25-7373EA3BB711@cisco.com> <82B68018-80A0-461E-8D55-A1232B2D057D@ericsson.com> <8B99541A-0C10-48C5-825D-5BC219684BB4@cisco.com> <11997.1603721994@localhost>
X-Mailer: Apple Mail (2.3608.120.23.2.4)
X-Outbound-SMTP-Client: 10.61.101.216, dhcp-10-61-101-216.cisco.com
X-Outbound-Node: aer-core-3.cisco.com
Archived-At: <https://mailarchive.ietf.org/arch/msg/emu/2w4I3Y8e3MG-BcNk1CELeGAn4AY>
Subject: Re: [Emu] draft-ietf-emu-eap-tls13-11: OCSP Stapling
X-BeenThere: emu@ietf.org
X-Mailman-Version: 2.1.29
Precedence: list
List-Id: "EAP Methods Update \(EMU\)" <emu.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/emu>, <mailto:emu-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/emu/>
List-Post: <mailto:emu@ietf.org>
List-Help: <mailto:emu-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/emu>, <mailto:emu-request@ietf.org?subject=subscribe>
X-List-Received-Date: Mon, 26 Oct 2020 14:31:28 -0000

--Apple-Mail=_6EB101DF-F1A8-413D-A250-E02DFFDB6E43
Content-Transfer-Encoding: quoted-printable
Content-Type: text/plain;
	charset=utf-8



> On 26 Oct 2020, at 15:19, Michael Richardson <mcr+ietf@sandelman.ca> =
wrote:
>=20
> Signed PGP part
>=20
> Eliot Lear <lear=3D40cisco.com@dmarc.ietf.org> wrote:
>>> The EAP server is expected to frequently request a OCSP response =
from
>>> the OCSP responder (a server typically run by the certificate
>>> issuer). The OCSP response is then added to the Servers Certificate
>>> message as long as it is valid. Before the OCSP response is close to
>>> expiring, the EAP server requests a new OCSP response from the OCSP
>>> responder.
>=20
>> Right.  What this is saying is that a local deployment MUST run an =
OCSP
>> responder.  If that OCSP responder is unavailable, then what?  Now
>> imagine we are discussing critical infrastructure where the responder
>> is not in the same room, and there are network connectivity problems.
>> The device joining the network needs local access and that is it.  =
Does
>> that mean it should not use EAP-TLS?  Or are we saying that they MUST
>> use naked public keys?
>=20
> No.  There are several steps before we get to raw public keys.
>=20
> The first is that the duration of the Staples could be lengthed to =
accomodate
> anticipated down time for the (now) critical OCSP responder.
> A second part is that perhaps staples could be provisioned in advance =
for the
> server to cover for planned maintenance periods.  I don't imagine this =
is in
> any protocol, but could be added.

But to what end?  We don=E2=80=99t even know if these devices can =
reasonably deal with any secure notion of time.  Even checking cert =
expiry is a bit questionable in some cases, especially if the cert has =
been seen before, and the device is of someone critical value.  And =
it=E2=80=99s not clear what the value is with a lengthy expiry.


>=20
> The second is, I think, that the EAP server (Authentication Server), =
would run
> an OCSP responder locally so that it can mint it's own staples.
> AFAIK, each certificate can point to a different OCSP signer.

Does anyone actually do that?

> While this degenerate case of Authentication Server + OCSP Signer on =
the same
> machine is kinda dumb from a overall security point of view, it's =
still
> better than raw public keys.

Yes.  Let=E2=80=99s think about who OCSP is protecting in this case.  =
It=E2=80=99s protecting the client from the Authentication Server, in =
theory.


> If the OCSP signer is moved to some TPM then
> there is a win.  Not all TPMs can provide the performance required to =
handle
> the server certificate, but resigning an OCSP Staple once every ten =
minutes
> or something shouldn't be a problem.

If this is the case, then a public key could be moved into the the TPM =
just as easily.

>=20
> The third is, I think, that the EAP server runs an entirely =
self-contained
> private CA.  The OCSP responder is now clearly an integral part of the =
local
> system.

Again, what threat are we protecting against?

Eliot

--Apple-Mail=_6EB101DF-F1A8-413D-A250-E02DFFDB6E43
Content-Transfer-Encoding: 7bit
Content-Disposition: attachment;
	filename=signature.asc
Content-Type: application/pgp-signature;
	name=signature.asc
Content-Description: Message signed with OpenPGP

-----BEGIN PGP SIGNATURE-----

iQEzBAEBCAAdFiEEmNC9kEYdsJKnsmEdh7ZrRtnSejMFAl+W3bcACgkQh7ZrRtnS
ejPafwf+JzeiZe/u7HNQGcpV+EX1uoPO9hd4DMxywTcKz85MFvUdyNwEqcs7c6rL
vFSD8lnLmMKHwAu/9GY/A09m4QWLg/qLb9JWWH+yfniMe4Lg8Oy06W9fEqRVJv+K
nUECs9y512fEcsS5ufcmJCfZA4NjxmTZNGsBpFrq3haQ8HexcRen0CVERy9UQPX/
ELykj+faGUNo0E1CkAAubS67gmNHbS1vqIdWoRb1Hnc3OXgdiLh3/lK0PbPHNMyi
CxrJLBCDXHbJa21ssIV7J4zDtYfVp+ACCH2R5TZUk907TLes9+3BQ17QVfKsXKAB
vZxtsiftiClEDdOnefGZT1qm9oR3UA==
=xWjv
-----END PGP SIGNATURE-----

--Apple-Mail=_6EB101DF-F1A8-413D-A250-E02DFFDB6E43--


From nobody Mon Oct 26 07:45:53 2020
Return-Path: <housley@vigilsec.com>
X-Original-To: emu@ietfa.amsl.com
Delivered-To: emu@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id CE78F3A0BEE for <emu@ietfa.amsl.com>; Mon, 26 Oct 2020 07:45:51 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.898
X-Spam-Level: 
X-Spam-Status: No, score=-1.898 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, SPF_HELO_NONE=0.001, SPF_NONE=0.001] autolearn=ham autolearn_force=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 wBHsIqWVk7Pn for <emu@ietfa.amsl.com>; Mon, 26 Oct 2020 07:45:50 -0700 (PDT)
Received: from mail.smeinc.net (mail.smeinc.net [209.135.209.11]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 875C43A0BE9 for <emu@ietf.org>; Mon, 26 Oct 2020 07:45:50 -0700 (PDT)
Received: from localhost (localhost [127.0.0.1]) by mail.smeinc.net (Postfix) with ESMTP id D0BB1300B75 for <emu@ietf.org>; Mon, 26 Oct 2020 10:45:47 -0400 (EDT)
X-Virus-Scanned: amavisd-new at mail.smeinc.net
Received: from mail.smeinc.net ([127.0.0.1]) by localhost (mail.smeinc.net [127.0.0.1]) (amavisd-new, port 10026) with ESMTP id xW7ysLB2a0_e for <emu@ietf.org>; Mon, 26 Oct 2020 10:45:47 -0400 (EDT)
Received: from [192.168.1.161] (pool-141-156-161-153.washdc.fios.verizon.net [141.156.161.153]) by mail.smeinc.net (Postfix) with ESMTPSA id E4D5B300ABE; Mon, 26 Oct 2020 10:45:46 -0400 (EDT)
Content-Type: text/plain; charset=us-ascii
Mime-Version: 1.0 (Mac OS X Mail 12.4 \(3445.104.17\))
From: Russ Housley <housley@vigilsec.com>
In-Reply-To: <68AB850D-1695-447C-86CF-ACCEA92662E8@cisco.com>
Date: Mon, 26 Oct 2020 10:45:48 -0400
Cc: "emu@ietf.org" <emu@ietf.org>
Content-Transfer-Encoding: quoted-printable
Message-Id: <82409D52-EE5A-4402-A9CA-EE36AC67E2AB@vigilsec.com>
References: <7E22462D-3668-4F4F-BD66-A125A26B34DC@ericsson.com> <E32DAFB7-152F-4E04-9C25-7373EA3BB711@cisco.com> <82B68018-80A0-461E-8D55-A1232B2D057D@ericsson.com> <8B99541A-0C10-48C5-825D-5BC219684BB4@cisco.com> <11997.1603721994@localhost> <68AB850D-1695-447C-86CF-ACCEA92662E8@cisco.com>
To: Eliot Lear <lear@cisco.com>
X-Mailer: Apple Mail (2.3445.104.17)
Archived-At: <https://mailarchive.ietf.org/arch/msg/emu/fMmE4Xai6efcpq47FJ5YEhGe6UA>
Subject: Re: [Emu] draft-ietf-emu-eap-tls13-11: OCSP Stapling
X-BeenThere: emu@ietf.org
X-Mailman-Version: 2.1.29
Precedence: list
List-Id: "EAP Methods Update \(EMU\)" <emu.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/emu>, <mailto:emu-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/emu/>
List-Post: <mailto:emu@ietf.org>
List-Help: <mailto:emu-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/emu>, <mailto:emu-request@ietf.org?subject=subscribe>
X-List-Received-Date: Mon, 26 Oct 2020 14:45:52 -0000

>> The second is, I think, that the EAP server (Authentication Server), =
would run
>> an OCSP responder locally so that it can mint it's own staples.
>> AFAIK, each certificate can point to a different OCSP signer.
>=20
> Does anyone actually do that?

I am aware of some places that generate an OCSP response for the entire =
population of certificates, and those responsed are distributed to many =
locations.  I am not aware of anyone that distributes the OCSP responder =
signature private key to multiple locations.

Russ


From nobody Mon Oct 26 08:27:04 2020
Return-Path: <mcr+ietf@sandelman.ca>
X-Original-To: emu@ietfa.amsl.com
Delivered-To: emu@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 38D5A3A0C4C for <emu@ietfa.amsl.com>; Mon, 26 Oct 2020 08:27:02 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.898
X-Spam-Level: 
X-Spam-Status: No, score=-1.898 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RCVD_IN_DNSWL_BLOCKED=0.001, SPF_HELO_NONE=0.001, SPF_PASS=-0.001, URIBL_BLOCKED=0.001] autolearn=ham autolearn_force=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 oJEwyMFou0tv for <emu@ietfa.amsl.com>; Mon, 26 Oct 2020 08:27:00 -0700 (PDT)
Received: from tuna.sandelman.ca (tuna.sandelman.ca [209.87.249.19]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 1FCB73A0C47 for <emu@ietf.org>; Mon, 26 Oct 2020 08:26:59 -0700 (PDT)
Received: from localhost (localhost [127.0.0.1]) by tuna.sandelman.ca (Postfix) with ESMTP id 7FA10389A7; Mon, 26 Oct 2020 11:33:33 -0400 (EDT)
Received: from tuna.sandelman.ca ([127.0.0.1]) by localhost (localhost [127.0.0.1]) (amavisd-new, port 10024) with LMTP id jB8wDqXWIr31; Mon, 26 Oct 2020 11:33:32 -0400 (EDT)
Received: from sandelman.ca (obiwan.sandelman.ca [IPv6:2607:f0b0:f:2::247]) by tuna.sandelman.ca (Postfix) with ESMTP id 7536738997; Mon, 26 Oct 2020 11:33:32 -0400 (EDT)
Received: from localhost (localhost [IPv6:::1]) by sandelman.ca (Postfix) with ESMTP id 9CB9E493; Mon, 26 Oct 2020 11:26:57 -0400 (EDT)
From: Michael Richardson <mcr+ietf@sandelman.ca>
To: Eliot Lear <lear@cisco.com>, "emu\@ietf.org" <emu@ietf.org>
In-Reply-To: <68AB850D-1695-447C-86CF-ACCEA92662E8@cisco.com>
References: <7E22462D-3668-4F4F-BD66-A125A26B34DC@ericsson.com> <E32DAFB7-152F-4E04-9C25-7373EA3BB711@cisco.com> <82B68018-80A0-461E-8D55-A1232B2D057D@ericsson.com> <8B99541A-0C10-48C5-825D-5BC219684BB4@cisco.com> <11997.1603721994@localhost> <68AB850D-1695-447C-86CF-ACCEA92662E8@cisco.com>
X-Mailer: MH-E 8.6+git; nmh 1.7+dev; GNU Emacs 26.1
X-Face: $\n1pF)h^`}$H>Hk{L"x@)JS7<%Az}5RyS@k9X%29-lHB$Ti.V>2bi.~ehC0; <'$9xN5Ub# z!G,p`nR&p7Fz@^UXIn156S8.~^@MJ*mMsD7=QFeq%AL4m<nPbLgmtKK-5dC@#:k
MIME-Version: 1.0
Content-Type: multipart/signed; boundary="=-=-="; micalg=pgp-sha512; protocol="application/pgp-signature"
Date: Mon, 26 Oct 2020 11:26:57 -0400
Message-ID: <708.1603726017@localhost>
Archived-At: <https://mailarchive.ietf.org/arch/msg/emu/nklr55sjQu81ozu-6fWdb6km3XU>
Subject: Re: [Emu] draft-ietf-emu-eap-tls13-11: OCSP Stapling
X-BeenThere: emu@ietf.org
X-Mailman-Version: 2.1.29
Precedence: list
List-Id: "EAP Methods Update \(EMU\)" <emu.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/emu>, <mailto:emu-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/emu/>
List-Post: <mailto:emu@ietf.org>
List-Help: <mailto:emu-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/emu>, <mailto:emu-request@ietf.org?subject=subscribe>
X-List-Received-Date: Mon, 26 Oct 2020 15:27:02 -0000

--=-=-=
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: quoted-printable


Eliot Lear <lear@cisco.com> wrote:
    >> No.  There are several steps before we get to raw public keys.
    >>
    >> The first is that the duration of the Staples could be lengthed to a=
ccomodate
    >> anticipated down time for the (now) critical OCSP responder.
    >> A second part is that perhaps staples could be provisioned in advanc=
e for the
    >> server to cover for planned maintenance periods.  I don't imagine th=
is is in
    >> any protocol, but could be added.

    > But to what end?  We don=E2=80=99t even know if these devices can rea=
sonably
    > deal with any secure notion of time.  Even checking cert expiry is a
    > bit questionable in some cases, especially if the cert has been seen
    > before, and the device is of someone critical value.  And it=E2=80=99=
s not
    > clear what the value is with a lengthy expiry.

okay, but this is clearly a problem regardless.
Devices without known good time can't do very many useful things, and
probably just could ignore the staple.
But, laptops and mobiles do have good time, and they can do the right thing.

    >> The second is, I think, that the EAP server (Authentication Server),=
 would run
    >> an OCSP responder locally so that it can mint it's own staples.
    >> AFAIK, each certificate can point to a different OCSP signer.

    > Does anyone actually do that?

I dunno, but it is possible as far as I can tell.

    >> While this degenerate case of Authentication Server + OCSP Signer on=
 the same
    >> machine is kinda dumb from a overall security point of view, it's st=
ill
    >> better than raw public keys.

    > Yes.  Let=E2=80=99s think about who OCSP is protecting in this case. =
 It=E2=80=99s
    > protecting the client from the Authentication Server, in theory.

Yes, from compromises of the Authentication Server via loss of control of p=
rivate key.

    >> If the OCSP signer is moved to some TPM then
    >> there is a win.  Not all TPMs can provide the performance required t=
o handle
    >> the server certificate, but resigning an OCSP Staple once every ten =
minutes
    >> or something shouldn't be a problem.

    > If this is the case, then a public key could be moved into the the TP=
M just as easily.

If the TPM can accomodate thousands of signatures per minute, which fTPMs
probably can accomodate (same CPU, just different context), then sure.
Many older, i2c interfaced physical-TPMs do not accomodate that rate.

    >> The third is, I think, that the EAP server runs an entirely self-con=
tained
    >> private CA.  The OCSP responder is now clearly an integral part of t=
he local
    >> system.

    > Again, what threat are we protecting against?

The self-contained CA might have a passphrase, so there is some accomodation
updating the signing key for new algorithms, etc.  while the trust anchor
which is distributed is appropriate pessimistic.

=2D-
Michael Richardson <mcr+IETF@sandelman.ca>   . o O ( IPv6 I=C3=B8T consulti=
ng )
           Sandelman Software Works Inc, Ottawa and Worldwide

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

-----BEGIN PGP SIGNATURE-----

iQEzBAEBCgAdFiEEbsyLEzg/qUTA43uogItw+93Q3WUFAl+W6sEACgkQgItw+93Q
3WXkMAf7Bf6h8JjkuRj1rko0npuGV4ho4tGeNRgQic0l6oZZ66OGXNtwCH0AvP8g
GZyx9sQEp+wga9bR1wy6FiuoQnCxtQwbqujGnaTg+OPvuo5+Go8OMj8U0ERVEQYN
UzOy8ehebYMq6yNLRzZWy4K41fqdGJq38wCvrdA59qgqnnNMU7brIW+Fd2+AAmjg
wzip0Cy9rwBTKkSBbtRD8+rpP4pud6DwKTviakauKK42ARmMRDTvJ6S1G/skfSMy
oJFgFomuUhKdgxA6Cd5poCx3GtXQIm1uSlowAhWZ9p811dUyctiMCTXUACBOqxSD
7GUZSyNDenta/QJhC1/HocAHiMR1eQ==
=wE5q
-----END PGP SIGNATURE-----
--=-=-=--


From nobody Mon Oct 26 08:30:11 2020
Return-Path: <mcr@sandelman.ca>
X-Original-To: emu@ietfa.amsl.com
Delivered-To: emu@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 3E4063A0CA1 for <emu@ietfa.amsl.com>; Mon, 26 Oct 2020 08:30:05 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.899
X-Spam-Level: 
X-Spam-Status: No, score=-1.899 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, SPF_HELO_NONE=0.001, SPF_PASS=-0.001, URIBL_BLOCKED=0.001] autolearn=ham autolearn_force=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 3LrfqoXVp6Dt for <emu@ietfa.amsl.com>; Mon, 26 Oct 2020 08:30:03 -0700 (PDT)
Received: from tuna.sandelman.ca (tuna.sandelman.ca [209.87.249.19]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id B837D3A0C55 for <emu@ietf.org>; Mon, 26 Oct 2020 08:30:03 -0700 (PDT)
Received: from localhost (localhost [127.0.0.1]) by tuna.sandelman.ca (Postfix) with ESMTP id A343E389B5; Mon, 26 Oct 2020 11:36:37 -0400 (EDT)
Received: from tuna.sandelman.ca ([127.0.0.1]) by localhost (localhost [127.0.0.1]) (amavisd-new, port 10024) with LMTP id g6KVJGXldoP7; Mon, 26 Oct 2020 11:36:36 -0400 (EDT)
Received: from sandelman.ca (obiwan.sandelman.ca [209.87.249.21]) by tuna.sandelman.ca (Postfix) with ESMTP id 8BBC5389AB; Mon, 26 Oct 2020 11:36:36 -0400 (EDT)
Received: from localhost (localhost [IPv6:::1]) by sandelman.ca (Postfix) with ESMTP id AF9B7493; Mon, 26 Oct 2020 11:30:01 -0400 (EDT)
From: Michael Richardson <mcr@sandelman.ca>
To: Russ Housley <housley@vigilsec.com>, Eliot Lear <lear@cisco.com>, "emu\@ietf.org" <emu@ietf.org>
In-Reply-To: <82409D52-EE5A-4402-A9CA-EE36AC67E2AB@vigilsec.com>
References: <7E22462D-3668-4F4F-BD66-A125A26B34DC@ericsson.com> <E32DAFB7-152F-4E04-9C25-7373EA3BB711@cisco.com> <82B68018-80A0-461E-8D55-A1232B2D057D@ericsson.com> <8B99541A-0C10-48C5-825D-5BC219684BB4@cisco.com> <11997.1603721994@localhost> <68AB850D-1695-447C-86CF-ACCEA92662E8@cisco.com> <82409D52-EE5A-4402-A9CA-EE36AC67E2AB@vigilsec.com>
X-Mailer: MH-E 8.6+git; nmh 1.7+dev; GNU Emacs 26.1
X-Face: $\n1pF)h^`}$H>Hk{L"x@)JS7<%Az}5RyS@k9X%29-lHB$Ti.V>2bi.~ehC0; <'$9xN5Ub# z!G,p`nR&p7Fz@^UXIn156S8.~^@MJ*mMsD7=QFeq%AL4m<nPbLgmtKK-5dC@#:k
MIME-Version: 1.0
Content-Type: multipart/signed; boundary="=-=-="; micalg=pgp-sha512; protocol="application/pgp-signature"
Date: Mon, 26 Oct 2020 11:30:01 -0400
Message-ID: <1507.1603726201@localhost>
Archived-At: <https://mailarchive.ietf.org/arch/msg/emu/asgYzW_8sKZG7nExiawfeJlLe08>
Subject: Re: [Emu] draft-ietf-emu-eap-tls13-11: OCSP Stapling
X-BeenThere: emu@ietf.org
X-Mailman-Version: 2.1.29
Precedence: list
List-Id: "EAP Methods Update \(EMU\)" <emu.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/emu>, <mailto:emu-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/emu/>
List-Post: <mailto:emu@ietf.org>
List-Help: <mailto:emu-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/emu>, <mailto:emu-request@ietf.org?subject=subscribe>
X-List-Received-Date: Mon, 26 Oct 2020 15:30:10 -0000

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


Russ Housley <housley@vigilsec.com> wrote:
    >>> The second is, I think, that the EAP server (Authentication Server), would run
    >>> an OCSP responder locally so that it can mint it's own staples.
    >>> AFAIK, each certificate can point to a different OCSP signer.
    >>
    >> Does anyone actually do that?

    > I am aware of some places that generate an OCSP response for the entire
    > population of certificates, and those responsed are distributed to many
    > locations.  I am not aware of anyone that distributes the OCSP
    > responder signature private key to multiple locations.

Does anyone put different OCSP signers into different certificates?
I.e. shard the work?

I think that splitting the OCSP reponses to many locations might solve the
industrial situation well.
I think that there is also some significant space to tune the validity
periods.

But, I agree with Eliot: the OCSP responder is new.

It seems that maybe SHOULD would appropriate on OCSP.

--
]               Never tell me the odds!                 | ipv6 mesh networks [
]   Michael Richardson, Sandelman Software Works        |    IoT architect   [
]     mcr@sandelman.ca  http://www.sandelman.ca/        |   ruby on rails    [


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

-----BEGIN PGP SIGNATURE-----

iQEzBAEBCgAdFiEEbsyLEzg/qUTA43uogItw+93Q3WUFAl+W63kACgkQgItw+93Q
3WVCxwf+Mg0NR0lXyMv35Uuc5LB6/9krCju8Bs6YwDAJ8Ae+dswgc8/LuYo/Fwi4
QwlyumkwGZ1QE8L9n4hcvuDy+LStO15taNvj/s4PAUtoryxQ4MDn8UyXp0tF4FR0
qnB0Qu7m31mJpU71U9+OvhFwiDfrCm1u/gctr82TkDpI4HMYmNQIhbNBOPwXcRjm
T9LVvt/8t0W+UOG5jx+vE3MGpDnQtYSLGOyxn41vA0dxfzm7jcBLCKBrXrzNqnWt
VjVF5qEk8DOwVftf7KNkA9EWtCXF+pRT6WCBXz8PaqvxaoeMXU5ok++6UOTTz8gi
qsM7lvMRfq5wrxPxr8eeL4yJa90/fA==
=dblC
-----END PGP SIGNATURE-----
--=-=-=--


From nobody Mon Oct 26 10:00:30 2020
Return-Path: <housley@vigilsec.com>
X-Original-To: emu@ietfa.amsl.com
Delivered-To: emu@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id A75A23A0D42 for <emu@ietfa.amsl.com>; Mon, 26 Oct 2020 10:00:28 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.898
X-Spam-Level: 
X-Spam-Status: No, score=-1.898 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, SPF_HELO_NONE=0.001, SPF_NONE=0.001] autolearn=ham autolearn_force=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 XL4dAPoVrid8 for <emu@ietfa.amsl.com>; Mon, 26 Oct 2020 10:00:27 -0700 (PDT)
Received: from mail.smeinc.net (mail.smeinc.net [209.135.209.11]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 2E6373A0E7C for <emu@ietf.org>; Mon, 26 Oct 2020 10:00:04 -0700 (PDT)
Received: from localhost (localhost [127.0.0.1]) by mail.smeinc.net (Postfix) with ESMTP id BC5E5300B55 for <emu@ietf.org>; Mon, 26 Oct 2020 13:00:01 -0400 (EDT)
X-Virus-Scanned: amavisd-new at mail.smeinc.net
Received: from mail.smeinc.net ([127.0.0.1]) by localhost (mail.smeinc.net [127.0.0.1]) (amavisd-new, port 10026) with ESMTP id 9uw-Ujohoaf9 for <emu@ietf.org>; Mon, 26 Oct 2020 13:00:00 -0400 (EDT)
Received: from [192.168.1.161] (pool-141-156-161-153.washdc.fios.verizon.net [141.156.161.153]) by mail.smeinc.net (Postfix) with ESMTPSA id 50681300A91; Mon, 26 Oct 2020 13:00:00 -0400 (EDT)
Content-Type: text/plain; charset=us-ascii
Mime-Version: 1.0 (Mac OS X Mail 12.4 \(3445.104.17\))
From: Russ Housley <housley@vigilsec.com>
In-Reply-To: <1507.1603726201@localhost>
Date: Mon, 26 Oct 2020 13:00:01 -0400
Cc: "emu@ietf.org" <emu@ietf.org>
Content-Transfer-Encoding: quoted-printable
Message-Id: <3B520CCA-E8BE-415F-8979-7359A945DE53@vigilsec.com>
References: <7E22462D-3668-4F4F-BD66-A125A26B34DC@ericsson.com> <E32DAFB7-152F-4E04-9C25-7373EA3BB711@cisco.com> <82B68018-80A0-461E-8D55-A1232B2D057D@ericsson.com> <8B99541A-0C10-48C5-825D-5BC219684BB4@cisco.com> <11997.1603721994@localhost> <68AB850D-1695-447C-86CF-ACCEA92662E8@cisco.com> <82409D52-EE5A-4402-A9CA-EE36AC67E2AB@vigilsec.com> <1507.1603726201@localhost>
To: Michael Richardson <mcr@sandelman.ca>, Eliot Lear <lear@cisco.com>
X-Mailer: Apple Mail (2.3445.104.17)
Archived-At: <https://mailarchive.ietf.org/arch/msg/emu/gkvY4kStTyn46wsbwLw6dbMI_R4>
Subject: Re: [Emu] draft-ietf-emu-eap-tls13-11: OCSP Stapling
X-BeenThere: emu@ietf.org
X-Mailman-Version: 2.1.29
Precedence: list
List-Id: "EAP Methods Update \(EMU\)" <emu.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/emu>, <mailto:emu-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/emu/>
List-Post: <mailto:emu@ietf.org>
List-Help: <mailto:emu-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/emu>, <mailto:emu-request@ietf.org?subject=subscribe>
X-List-Received-Date: Mon, 26 Oct 2020 17:00:29 -0000

Michael:

>> I am aware of some places that generate an OCSP response for the =
entire
>> population of certificates, and those responsed are distributed to =
many
>> locations.  I am not aware of anyone that distributes the OCSP
>> responder signature private key to multiple locations.
>=20
> Does anyone put different OCSP signers into different certificates?
> I.e. shard the work?

This could be done by including different AIA certificate extensions, =
but I am not aware of anyone that does so.

> I think that splitting the OCSP reponses to many locations might solve =
the
> industrial situation well.

One could put multiple id-ad-ocsp entries in the AuthorityInfoAccess =
extension, but this could lead to a relying party trying each one in =
turn, resulting in a long timeout interval.

Russ


From nobody Mon Oct 26 10:34:52 2020
Return-Path: <lear@cisco.com>
X-Original-To: emu@ietfa.amsl.com
Delivered-To: emu@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id BA9373A0DEA for <emu@ietfa.amsl.com>; Mon, 26 Oct 2020 10:34:50 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -9.6
X-Spam-Level: 
X-Spam-Status: No, score=-9.6 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIMWL_WL_MED=-0.001, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, DKIM_VALID_EF=-0.1, RCVD_IN_DNSWL_BLOCKED=0.001, SPF_PASS=-0.001, URIBL_BLOCKED=0.001, USER_IN_DEF_DKIM_WL=-7.5] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (1024-bit key) header.d=cisco.com
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 MpLpFMF6gNjZ for <emu@ietfa.amsl.com>; Mon, 26 Oct 2020 10:34:49 -0700 (PDT)
Received: from aer-iport-1.cisco.com (aer-iport-1.cisco.com [173.38.203.51]) (using TLSv1.2 with cipher DHE-RSA-SEED-SHA (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 302CB3A0DE8 for <emu@ietf.org>; Mon, 26 Oct 2020 10:34:49 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=cisco.com; i=@cisco.com; l=3256; q=dns/txt; s=iport; t=1603733689; x=1604943289; h=from:message-id:mime-version:subject:date:in-reply-to:cc: to:references; bh=ingLm9Zg990LYA/t6XdNST3hZKp6odzX+b5f3aujQRc=; b=Imyy437pxb8NithyAG2iecrKdDjy4NuU80capPbQS+J8hrQfE0awDC3D iLG6hU6WvuSAYWfWgqNVYo2L0uvaIDyDNMCjQAkFZdeEpP3wvaf/Iginx G750V5s1dt+nJ87onby4URtg/kqLxOtC2b9odwx5msG+dXvy++LDAH35l 4=;
X-Files: signature.asc : 488
X-IronPort-Anti-Spam-Filtered: true
X-IronPort-Anti-Spam-Result: =?us-ascii?q?A0DeAgAKCJdf/xbLJq1gHAEBAQEBAQc?= =?us-ascii?q?BARIBAQQEAQGCD4NvASASLIQ8iQWHZyacJQQHAQEBCgMBAS8EAQGESgKCDCY?= =?us-ascii?q?4EwIDAQELAQEFAQEBAgEGBG2FbYVyAQEBAwEjVgULCxgqAgJXBhMegwgBglw?= =?us-ascii?q?gow52gTKFV4RhEIE4gVOMAYIAgREnDBCCTT6EJYMvM4IsBJAqi3ubYYJ0gxa?= =?us-ascii?q?BN5YsAx+SRI8asBaDXwIEBgUCFYFrI4FXMxoIGxVlAYI+PhIZDZxnQAMwOAI?= =?us-ascii?q?GAQkBAQMJjkgBAQ?=
X-IronPort-AV: E=Sophos;i="5.77,420,1596499200";  d="asc'?scan'208";a="30642965"
Received: from aer-iport-nat.cisco.com (HELO aer-core-2.cisco.com) ([173.38.203.22]) by aer-iport-1.cisco.com with ESMTP/TLS/DHE-RSA-SEED-SHA; 26 Oct 2020 17:34:45 +0000
Received: from [10.61.194.56] ([10.61.194.56]) by aer-core-2.cisco.com (8.15.2/8.15.2) with ESMTPS id 09QHYih8022149 (version=TLSv1.2 cipher=DHE-RSA-AES256-GCM-SHA384 bits=256 verify=NO); Mon, 26 Oct 2020 17:34:45 GMT
From: Eliot Lear <lear@cisco.com>
Message-Id: <68AD9BEE-2504-4E16-92F5-121F0BEFC5C0@cisco.com>
Content-Type: multipart/signed; boundary="Apple-Mail=_4FEBDECD-47B4-451A-AD64-BC9260C1DB5F"; protocol="application/pgp-signature"; micalg=pgp-sha256
Mime-Version: 1.0 (Mac OS X Mail 13.4 \(3608.120.23.2.4\))
Date: Mon, 26 Oct 2020 18:34:43 +0100
In-Reply-To: <708.1603726017@localhost>
Cc: "emu@ietf.org" <emu@ietf.org>
To: Michael Richardson <mcr+ietf@sandelman.ca>
References: <7E22462D-3668-4F4F-BD66-A125A26B34DC@ericsson.com> <E32DAFB7-152F-4E04-9C25-7373EA3BB711@cisco.com> <82B68018-80A0-461E-8D55-A1232B2D057D@ericsson.com> <8B99541A-0C10-48C5-825D-5BC219684BB4@cisco.com> <11997.1603721994@localhost> <68AB850D-1695-447C-86CF-ACCEA92662E8@cisco.com> <708.1603726017@localhost>
X-Mailer: Apple Mail (2.3608.120.23.2.4)
X-Outbound-SMTP-Client: 10.61.194.56, [10.61.194.56]
X-Outbound-Node: aer-core-2.cisco.com
Archived-At: <https://mailarchive.ietf.org/arch/msg/emu/XZCbBEuTJ8g_cWCqvNF_O0RbOrE>
Subject: Re: [Emu] draft-ietf-emu-eap-tls13-11: OCSP Stapling
X-BeenThere: emu@ietf.org
X-Mailman-Version: 2.1.29
Precedence: list
List-Id: "EAP Methods Update \(EMU\)" <emu.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/emu>, <mailto:emu-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/emu/>
List-Post: <mailto:emu@ietf.org>
List-Help: <mailto:emu-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/emu>, <mailto:emu-request@ietf.org?subject=subscribe>
X-List-Received-Date: Mon, 26 Oct 2020 17:34:51 -0000

--Apple-Mail=_4FEBDECD-47B4-451A-AD64-BC9260C1DB5F
Content-Transfer-Encoding: quoted-printable
Content-Type: text/plain;
	charset=utf-8

[Trimming]

> On 26 Oct 2020, at 16:26, Michael Richardson <mcr+ietf@sandelman.ca> =
wrote:
>=20
>=20
>>> While this degenerate case of Authentication Server + OCSP Signer on =
the same
>>> machine is kinda dumb from a overall security point of view, it's =
still
>>> better than raw public keys.
>=20
>> Yes.  Let=E2=80=99s think about who OCSP is protecting in this case.  =
It=E2=80=99s
>> protecting the client from the Authentication Server, in theory.
>=20
> Yes, from compromises of the Authentication Server via loss of control =
of private key.

And so the authentication server and OCSP signer being on the same =
device itself represents both a scaling problem and a security problem.  =
Just imagine having to manage all of that.

>=20
>>> If the OCSP signer is moved to some TPM then
>>> there is a win.  Not all TPMs can provide the performance required =
to handle
>>> the server certificate, but resigning an OCSP Staple once every ten =
minutes
>>> or something shouldn't be a problem.
>=20
>> If this is the case, then a public key could be moved into the the =
TPM just as easily.
>=20
> If the TPM can accomodate thousands of signatures per minute, which =
fTPMs
> probably can accomodate (same CPU, just different context), then sure.
> Many older, i2c interfaced physical-TPMs do not accomodate that rate.

I=E2=80=99ll admit to only secondary interest in performance.  That is- =
one can optimize around this.  But managing naked public keys of servers =
themselves is not scalable from a key management perspective.


>>> The third is, I think, that the EAP server runs an entirely =
self-contained
>>> private CA.  The OCSP responder is now clearly an integral part of =
the local
>>> system.
>=20
>> Again, what threat are we protecting against?
>=20
> The self-contained CA might have a passphrase, so there is some =
accomodation
> updating the signing key for new algorithms, etc.  while the trust =
anchor
> which is distributed is appropriate pessimistic.
>=20


I guess the issue I=E2=80=99m having is that stapling is requiring more =
connectivity than may be present, and making it a MUST means that we are =
making very VERY broad deployment assumptions.  It is WAY too early for =
that.

Eliot

--Apple-Mail=_4FEBDECD-47B4-451A-AD64-BC9260C1DB5F
Content-Transfer-Encoding: 7bit
Content-Disposition: attachment;
	filename=signature.asc
Content-Type: application/pgp-signature;
	name=signature.asc
Content-Description: Message signed with OpenPGP

-----BEGIN PGP SIGNATURE-----

iQEzBAEBCAAdFiEEmNC9kEYdsJKnsmEdh7ZrRtnSejMFAl+XCLMACgkQh7ZrRtnS
ejO8Cgf/a2rk+t4dQDcM5s0ZQaIJdl02wraDOT6tjazKqDj+x1BomB4Lo1XisKvh
DKatCk4QOJSMPbwpG6w/TANdSxtNZr6ROsuysr+n9tukCuwu4pxd0+RTQiEiiDQt
YdJujhRm6dLDcG90lugkk6zNL2EL886qh97mSzH3KnqZpekLllzIB65JJYnryb0I
gdpLArf3/V9GzjzFToTidgWhvehlALvf5HjAhsthMYMbzQ3vpM5HFms/Ab2UxARi
KFdBmnDUU58OihXgd/vCVVPBaUrYWjkHokKDUKxgGn/4Ii+ypySJ6eIdL2lwQVNZ
hQXRrBgaBh+omFA6XkmwhubIJwBjIA==
=zSXg
-----END PGP SIGNATURE-----

--Apple-Mail=_4FEBDECD-47B4-451A-AD64-BC9260C1DB5F--


From nobody Mon Oct 26 12:51:15 2020
Return-Path: <jovergar@microsoft.com>
X-Original-To: emu@ietfa.amsl.com
Delivered-To: emu@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 05D0C3A0E7C for <emu@ietfa.amsl.com>; Mon, 26 Oct 2020 12:51:14 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2
X-Spam-Level: 
X-Spam-Status: No, score=-2 tagged_above=-999 required=5 tests=[BAYES_00=-1.9,  DKIMWL_WL_HIGH=-0.001, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, DKIM_VALID_EF=-0.1, HTML_MESSAGE=0.001, HTTPS_HTTP_MISMATCH=0.1, RCVD_IN_DNSWL_BLOCKED=0.001, RCVD_IN_MSPIKE_H2=-0.001, SPF_PASS=-0.001, URIBL_BLOCKED=0.001] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (1024-bit key) header.d=microsoft.com
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 fS6WEZXFjj14 for <emu@ietfa.amsl.com>; Mon, 26 Oct 2020 12:51:11 -0700 (PDT)
Received: from NAM02-BL2-obe.outbound.protection.outlook.com (mail-eopbgr750102.outbound.protection.outlook.com [40.107.75.102]) (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 782683A0E75 for <emu@ietf.org>; Mon, 26 Oct 2020 12:51:11 -0700 (PDT)
ARC-Seal: i=1; a=rsa-sha256; s=arcselector9901; d=microsoft.com; cv=none; b=Xf77ci+tQO7lVzu4/ZnQy1gu+uAMvcIgv/omIfh6ioouhxU248s+PlrjzUwYtmTRMVEbCJ2F6NjPlPVC4Dp4fVlCcJ/YDOqYI/RtUaPblkmMUhDswDlRVrB/7hdikXgZRSDrxlbC6DlcyhMnu1ykWzJaIxhAWhK20wWoQ2fhd1gUd3xQFrpv8p1bDP0x4mN2BDPG4qyTimAemq4NuqvvDua4Xbv2qg2F3YvoSy+ZYqwDiqPjd7BaDVeo0gJBsGUgHPk9JlRc/BbssqawzIHnxbyX0AvWv+3zqOAUj2J8lfo56/9+UmhCorabeO/fXLfCGyTwYqp6NkRUNqNmKLvXOg==
ARC-Message-Signature: i=1; a=rsa-sha256; c=relaxed/relaxed; d=microsoft.com;  s=arcselector9901; h=From:Date:Subject:Message-ID:Content-Type:MIME-Version:X-MS-Exchange-SenderADCheck; bh=l7xHYYWchUsoXjN97UiwDXbI8FRC9Ke/8i1kMAv12Ls=; b=Zzn/caL6tLqdnJJvHI5OOxWr88CwxHgnw3OP9H89NuPGdCeUUm+9/xiOpUGt6yL6QCnOkrGLZm+L5seklHpeF1k6ujV4XCkRk96kHQcLu6IoWEodWvWPpV8NGu+QFFNZ3SVc2xG9tQzogkFkhnaCuJGIMaRV0M8ExShuTx1qQHBpNIitgIy7taMdA4mLi632GNd2iBJ8vNeuP5Iew6I6XGxa6aBnE7ED90eVj7hX60MfIGtpNA9ssflBgn3yIKfbECB2iynEK5oSuWYoQ7G84H7+fukwl6dhumRS213bJgvW34vZvtblFdVZeo4n43SxF9rpBQKZpw/oCP8hQUNeFA==
ARC-Authentication-Results: i=1; mx.microsoft.com 1; spf=pass smtp.mailfrom=microsoft.com; dmarc=pass action=none header.from=microsoft.com; dkim=pass header.d=microsoft.com; arc=none
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=microsoft.com; s=selector2; h=From:Date:Subject:Message-ID:Content-Type:MIME-Version:X-MS-Exchange-SenderADCheck; bh=l7xHYYWchUsoXjN97UiwDXbI8FRC9Ke/8i1kMAv12Ls=; b=IKeBvEggxW4mbL7tfxh2/Mt2fBCzH0YkK+CHdfPBs7fnWDBriVHe1fed7MZGq4nfTSKLdGswd11cd0m9ett6T1+yOkV9nfXXdAwd1Ije6jlbtGVe2Q+IzvynJkcsHUf2SHeFl7bJicM0m87j+5ofXpVe88CAGedQXVzfyqPvVho=
Received: from CH2PR21MB1381.namprd21.prod.outlook.com (2603:10b6:610:8e::12) by CH2PR21MB1493.namprd21.prod.outlook.com (2603:10b6:610:5d::7) with Microsoft SMTP Server (version=TLS1_2, cipher=TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384) id 15.20.3499.3; Mon, 26 Oct 2020 19:51:05 +0000
Received: from CH2PR21MB1381.namprd21.prod.outlook.com ([fe80::dfd:b166:92c:5a84]) by CH2PR21MB1381.namprd21.prod.outlook.com ([fe80::dfd:b166:92c:5a84%9]) with mapi id 15.20.3499.017; Mon, 26 Oct 2020 19:51:05 +0000
From: Jorge Vergara <jovergar@microsoft.com>
To: Joseph Salowey <joe@salowey.net>, EMU WG <emu@ietf.org>
Thread-Topic: Proposed Resolution to TEAP Errata 5770
Thread-Index: AQHWqmRFpQXCgddk6U+PvaXt7wE7sKmqTEaA
Date: Mon, 26 Oct 2020 19:51:05 +0000
Message-ID: <CH2PR21MB138172CE5A552084A62E3AA9D1190@CH2PR21MB1381.namprd21.prod.outlook.com>
References: <CAOgPGoCg2wRKFVKz2kqkomt7mkp1W98jSh6xLT8z1_uWBMXdmA@mail.gmail.com>
In-Reply-To: <CAOgPGoCg2wRKFVKz2kqkomt7mkp1W98jSh6xLT8z1_uWBMXdmA@mail.gmail.com>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
msip_labels: MSIP_Label_f42aa342-8706-4288-bd11-ebb85995028c_ActionId=d3cea91e-1357-43ad-84b5-71828490a040; MSIP_Label_f42aa342-8706-4288-bd11-ebb85995028c_ContentBits=0; MSIP_Label_f42aa342-8706-4288-bd11-ebb85995028c_Enabled=true; MSIP_Label_f42aa342-8706-4288-bd11-ebb85995028c_Method=Standard; MSIP_Label_f42aa342-8706-4288-bd11-ebb85995028c_Name=Internal; MSIP_Label_f42aa342-8706-4288-bd11-ebb85995028c_SetDate=2020-10-26T19:45:17Z;  MSIP_Label_f42aa342-8706-4288-bd11-ebb85995028c_SiteId=72f988bf-86f1-41af-91ab-2d7cd011db47;
authentication-results: salowey.net; dkim=none (message not signed) header.d=none;salowey.net; dmarc=none action=none header.from=microsoft.com;
x-originating-ip: [2001:4898:80e8:0:2078:f6c3:f922:8f39]
x-ms-publictraffictype: Email
x-ms-office365-filtering-ht: Tenant
x-ms-office365-filtering-correlation-id: d1b4203b-5f7b-4ec2-61f4-08d879e879ff
x-ms-traffictypediagnostic: CH2PR21MB1493:
x-microsoft-antispam-prvs: <CH2PR21MB149314A802D9A0F7A017986DD1190@CH2PR21MB1493.namprd21.prod.outlook.com>
x-ms-oob-tlc-oobclassifiers: OLM:10000;
x-ms-exchange-senderadcheck: 1
x-microsoft-antispam: BCL:0;
x-microsoft-antispam-message-info: eZANioVK77btsVQ5divv/bLVUX0na9xfZyKBxYgdbFx89i+GhUzs8zw3OG0/ztT0TFW94ChYWEIKUDuUjOHU7XSo/+hkJS/eib6XomF402MDIJCgTXtG75oxne2BGSMBbPTiSoCQMMqe52vd5bYw6wh2q/15QLaY70fHSb7QoP1R7H9mrHswYFSRfda5GbyR3lkBihxKfzFqSORVj0u5QMYJ4lz7MLMQ2e1lk3R4CaJ/60hoVZNsyZEkAueqMg1AYSOdbD98jVq4Up0Wp0pFrh1TNfXDUoy5iIhalZi4xYQiQExQ5Xnegu7eGRbI2n6aq6+bwqLiyrNWArb5sOmIzo42DU4/nJAhpTr+7sufiCQZw83Gr/a8uOjR8H11eMIOGFPyeSePi6yLx9rQ27RsbA==
x-forefront-antispam-report: CIP:255.255.255.255; CTRY:; LANG:en; SCL:1; SRV:;  IPV:NLI; SFV:NSPM; H:CH2PR21MB1381.namprd21.prod.outlook.com; PTR:; CAT:NONE;  SFS:(4636009)(39860400002)(376002)(346002)(136003)(396003)(366004)(966005)(66476007)(64756008)(8936002)(86362001)(82950400001)(66556008)(9686003)(4326008)(478600001)(66446008)(66946007)(76116006)(82960400001)(10290500003)(55016002)(71200400001)(8990500004)(8676002)(110136005)(53546011)(166002)(7696005)(6506007)(83380400001)(5660300002)(52536014)(186003)(54906003)(2906002)(33656002)(316002); DIR:OUT; SFP:1102; 
x-ms-exchange-antispam-messagedata: VwJ1sZpsb9jaI2hJh1B5tlqToFHVoS3/FMHhupg6wFV127pzqcJkQO7kOJE1uTxa3yKBa+aarW689OEEls9qpp7Q68LASP/ZRi3/Xha8UcHoKxmLV13eKr7rwIpoWGygtRzU0rpp2INFKKx4Kt8pdcd9P1/j1nNWlNoEzhkPFLjSg3S+4CiPJOWWQWQZ88jD2ipkviOmMakfrMqUYbSuDHOVQ9E746Rhisx6Fs8G9O1BrKL3CEtupgJl7sjLRGn9azgsPB9H9TC5V012Er4vCUXUBsLXAtRWnuwnZ3Tpw+/IcwVzkWkvlQFq9J46ZJBaXr9K9zzVZPZ3vTZu5/fkyXwIK6+DZ6tEEV2QAJTI3FBTZEgP/q7LmiBMcSFyIgD2FGJ4Bt3Dd9m2tf5sGgHHQliENfufG8enJMFPFMl9mZdr1yaxCscYZ5ZfKK8KSAqtFPzDbcIsJRns8LzfmxGTf6FZ+G5TRlWNz6yo3beNcKsKK9TMgn2pqA0X+1j37r+sKkhR7SSkX+hEtG8u63kRkUZzrOjm7f5EPVIXiWbo+sLEfXIb0QjXA/usENs3/rg6P2Uywzbv+doFLbVP8tloWYUGrTGO7k36e9DduYJOMq3raIfvAgsBrZ5x0/R701/72IXziGCoz+S8db4WmU1p5oDwXNM70Hxp+zB1MSdwUl8mM26+N8cpEWiwXV6OlrD/xmiWIHsj5RnX1WpfsdsJaw==
x-ms-exchange-transport-forked: True
Content-Type: multipart/alternative; boundary="_000_CH2PR21MB138172CE5A552084A62E3AA9D1190CH2PR21MB1381namp_"
MIME-Version: 1.0
X-OriginatorOrg: microsoft.com
X-MS-Exchange-CrossTenant-AuthAs: Internal
X-MS-Exchange-CrossTenant-AuthSource: CH2PR21MB1381.namprd21.prod.outlook.com
X-MS-Exchange-CrossTenant-Network-Message-Id: d1b4203b-5f7b-4ec2-61f4-08d879e879ff
X-MS-Exchange-CrossTenant-originalarrivaltime: 26 Oct 2020 19:51:05.7525 (UTC)
X-MS-Exchange-CrossTenant-fromentityheader: Hosted
X-MS-Exchange-CrossTenant-id: 72f988bf-86f1-41af-91ab-2d7cd011db47
X-MS-Exchange-CrossTenant-mailboxtype: HOSTED
X-MS-Exchange-CrossTenant-userprincipalname: vTejxuYN5egunrZ+bOcpeRLjwxyQtQTSWMwvbVnUZAvD2Vbpeo8C9a+JavfSR8jo+mrIP98El6xAddsysiBTNw==
X-MS-Exchange-Transport-CrossTenantHeadersStamped: CH2PR21MB1493
Archived-At: <https://mailarchive.ietf.org/arch/msg/emu/AhGBjUP4BWFnEvEXo2MTsdwvEvc>
Subject: Re: [Emu] Proposed Resolution to TEAP Errata 5770
X-BeenThere: emu@ietf.org
X-Mailman-Version: 2.1.29
Precedence: list
List-Id: "EAP Methods Update \(EMU\)" <emu.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/emu>, <mailto:emu-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/emu/>
List-Post: <mailto:emu@ietf.org>
List-Help: <mailto:emu-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/emu>, <mailto:emu-request@ietf.org?subject=subscribe>
X-List-Received-Date: Mon, 26 Oct 2020 19:51:14 -0000

--_000_CH2PR21MB138172CE5A552084A62E3AA9D1190CH2PR21MB1381namp_
Content-Type: text/plain; charset="utf-8"
Content-Transfer-Encoding: base64

VGhpcyBpcyBhIGRldGFpbGVkIG9uZSBzbyBJ4oCZdmUgdHJpZWQgdG8gZ28gb3ZlciBpdCBjYXJl
ZnVsbHkuIE1vc3Qgb2YgaXQgbG9va3MgZ29vZCBidXQgSeKAmW0gdW5zdXJlIGFib3V0IHRoaXMg
cGFydDoNCg0KPiBJZiBhbiBpbm5lciBtZXRob2QgZmFpbHMgb3IgTUFDIHZlcmlmaWNhdGlvbg0K
ZmFpbHMgdGhlbiBTLUlNQ0sgaXMgbm90IHVzZWQgaW4gZnVydGhlciBjYWxjdWxhdGlvbi4NCg0K
SXQgaXMgYSB2YWxpZCBzY2VuYXJpbyB0aGF0IG11bHRpcGxlIGF1dGhlbnRpY2F0aW9uIG1ldGhv
ZHMgcnVuIGFuZCBzb21lIGZhaWwsIGJ1dCB0aGUgb3ZlcmFsbCBURUFQIGF1dGhlbnRpY2F0aW9u
IHN1Y2NlZWRzLiBGb3IgZXhhbXBsZSwgaWYgdHdvIGlubmVyIEVBUCBBdXRoZW50aWNhdGlvbiBt
ZXRob2RzIHJ1biBhbmQgdGhlIGZpcnN0IGZhaWxzIGJ1dCB0aGUgc2Vjb25kcyBzdWNjZWVkcywg
dGhlIGNhbGN1bGF0aW9uIG5lZWRzIHRvIGJlIHZhbGlkLiBCYXNlZCBvbiB0aGUgb2xkIHRleHQs
IHRoYXQgYXV0aGVudGljYXRpb24gbWV0aG9kIGlzIG9taXR0ZWQgZnJvbSBjYWxjdWxhdGlvbnMu
IFRoaXMgaXMgd2hhdCBjdXJyZW50IGltcGxlbWVudGF0aW9ucyBkby4NCg0KTXkgZWRpdG9yaWFs
IGNvbW1lbnQgYmFzZWQgb24gc29tZSBvdGhlciBlcnJhdGEgd291bGQgYmUgdG8gdGhhdCB0ZXh0
IG5lZWRzIHRvIHNwZWNpZnkg4oCcYXV0aGVudGljYXRpb27igJ0gbWV0aG9kcyAocGVyIEpvdW5p
4oCZcyBvdGhlciBlcnJhdGEpIHNpbmNlIHRoZSBJZGVudGl0eSBtZXRob2QgZG9lc27igJl0IGZh
Y3RvciBpbiBoZXJlLiBJIHRoaW5rIGl0IHdvdWxkIGFsc28gYmUgYmVuZWZpY2lhbCB0byBiZSBz
cGVjaWZpYyBhYm91dCB0aGUgYmVoYXZpb3Igb2YgYmFzaWMgdXNlcm5hbWUgYW5kIHBhc3N3b3Jk
IGF1dGhlbnRpY2F0aW9uIGhlcmUuIE9sZWcgbWFkZSBzb21lIGNvbW1lbnRzIHRvIHRoaXMgZWZm
ZWN0IG9uIGFub3RoZXIgZW1haWwuIE91ciBpbXBsZW1lbnRhdGlvbiBkb2VzbuKAmXQgc3VwcG9y
dCBiYXNpYyB1c2VybmFtZSBhbmQgcGFzc3dvcmQgYXV0aGVudGljYXRpb24gc28gSSBkb27igJl0
IGhhdmUgYW55IHByaW9yIGV4cGVyaWVuY2UgaGVyZS4NCg0KSm9yZ2UgVmVyZ2FyYQ0KDQpGcm9t
OiBKb3NlcGggU2Fsb3dleSA8am9lQHNhbG93ZXkubmV0Pg0KU2VudDogU2F0dXJkYXksIE9jdG9i
ZXIgMjQsIDIwMjAgNToxOCBQTQ0KVG86IEVNVSBXRyA8ZW11QGlldGYub3JnPg0KQ2M6IE9sZWcg
UGVrYXIgPG9sZWcucGVrYXIuMjAxN0BnbWFpbC5jb20+OyBKb3VuaSBNYWxpbmVuIDxqQHcxLmZp
PjsgSm9yZ2UgVmVyZ2FyYSA8am92ZXJnYXJAbWljcm9zb2Z0LmNvbT4NClN1YmplY3Q6IFByb3Bv
c2VkIFJlc29sdXRpb24gdG8gVEVBUCBFcnJhdGEgNTc3MA0KDQpFcnJhdGEgNTc3MDogaHR0cHM6
Ly93d3cucmZjLWVkaXRvci5vcmcvZXJyYXRhL2VpZDU3NzA8aHR0cHM6Ly9uYW0wNi5zYWZlbGlu
a3MucHJvdGVjdGlvbi5vdXRsb29rLmNvbS8/dXJsPWh0dHBzJTNBJTJGJTJGd3d3LnJmYy1lZGl0
b3Iub3JnJTJGZXJyYXRhJTJGZWlkNTc3MCZkYXRhPTA0JTdDMDElN0Nqb3ZlcmdhciU0MG1pY3Jv
c29mdC5jb20lN0M3MjhjZWI2YWY2Njk0ZTQwZTA4ZTA4ZDg3ODdiNjY5ZCU3QzcyZjk4OGJmODZm
MTQxYWY5MWFiMmQ3Y2QwMTFkYjQ3JTdDMSU3QzAlN0M2MzczOTE4MTg2ODk3ODE3MjMlN0NVbmtu
b3duJTdDVFdGcGJHWnNiM2Q4ZXlKV0lqb2lNQzR3TGpBd01EQWlMQ0pRSWpvaVYybHVNeklpTENK
QlRpSTZJazFoYVd3aUxDSlhWQ0k2TW4wJTNEJTdDMTAwMCZzZGF0YT1SdVJyWFo1YzcwcjQzUm15
bDRzJTJCVlVLQUEyMm5HdG9lbkxFbGJDZVVrbUUlM0QmcmVzZXJ2ZWQ9MD4NClByb3Bvc2VkIFN0
YXR1czogVmVyaWZpZWQNClJldmlzaW9uOg0KDQpTZWN0aW9uIDUuMiBTYXlzOg0KDQpPbiB0aGUg
c2VuZGVyIG9mIHRoZSBDcnlwdG8tQmluZGluZyBUTFYgc2lkZToNCg0KICAgICBJZiB0aGUgRU1T
SyBpcyBub3QgYXZhaWxhYmxlLCB0aGVuIHRoZSBzZW5kZXIgY29tcHV0ZXMgdGhlIENvbXBvdW5k
DQogICAgIE1BQyB1c2luZyB0aGUgTVNLIG9mIHRoZSBpbm5lciBtZXRob2QuDQoNCiAgICAgSWYg
dGhlIEVNU0sgaXMgYXZhaWxhYmxlIGFuZCB0aGUgc2VuZGVyJ3MgcG9saWN5IGFjY2VwdHMgTVNL
LWJhc2VkDQogICAgIE1BQywgdGhlbiB0aGUgc2VuZGVyIGNvbXB1dGVzIHR3byBDb21wb3VuZCBN
QUMgdmFsdWVzLiAgVGhlIGZpcnN0DQogICAgIGlzIGNvbXB1dGVkIHdpdGggdGhlIEVNU0suICBU
aGUgc2Vjb25kIG9uZSBpcyBjb21wdXRlZCB1c2luZyB0aGUNCiAgICAgTVNLLiAgQm90aCBNQUNz
IGFyZSB0aGVuIHNlbnQgdG8gdGhlIG90aGVyIHNpZGUuDQoNCiAgICAgSWYgdGhlIEVNU0sgaXMg
YXZhaWxhYmxlIGJ1dCB0aGUgc2VuZGVyJ3MgcG9saWN5IGRvZXMgbm90IGFsbG93DQogICAgIGRv
d25ncmFkaW5nIHRvIE1TSy1nZW5lcmF0ZWQgTUFDLCB0aGVuIHRoZSBzZW5kZXIgU0hPVUxEIG9u
bHkgc2VuZA0KICAgICBFTVNLLWJhc2VkIE1BQy4NCg0KICAgT24gdGhlIHJlY2VpdmVyIG9mIHRo
ZSBDcnlwdG8tQmluZGluZyBUTFYgc2lkZToNCg0KICAgICBJZiB0aGUgRU1TSyBpcyBub3QgYXZh
aWxhYmxlIGFuZCBhbiBNU0stYmFzZWQgQ29tcG91bmQgTUFDIHdhcw0KICAgICBzZW50LCB0aGVu
IHRoZSByZWNlaXZlciB2YWxpZGF0ZXMgdGhlIENvbXBvdW5kIE1BQyBhbmQgc2VuZHMgYmFjaw0K
ICAgICBhbiBNU0stYmFzZWQgQ29tcG91bmQgTUFDIHJlc3BvbnNlLg0KDQogICAgIElmIHRoZSBF
TVNLIGlzIG5vdCBhdmFpbGFibGUgYW5kIG5vIE1TSy1iYXNlZCBDb21wb3VuZCBNQUMgd2FzDQog
ICAgIHNlbnQsIHRoZW4gdGhlIHJlY2VpdmVyIGhhbmRsZXMgbGlrZSBhbiBpbnZhbGlkIENyeXB0
by1CaW5kaW5nIFRMVg0KICAgICB3aXRoIGEgZmF0YWwgZXJyb3IuDQoNCiAgICAgSWYgdGhlIEVN
U0sgaXMgYXZhaWxhYmxlIGFuZCBhbiBFTVNLLWJhc2VkIENvbXBvdW5kIE1BQyB3YXMgc2VudCwN
CiAgICAgdGhlbiB0aGUgcmVjZWl2ZXIgdmFsaWRhdGVzIGl0IGFuZCBjcmVhdGVzIGEgcmVzcG9u
c2UgQ29tcG91bmQgTUFDDQogICAgIHVzaW5nIHRoZSBFTVNLLg0KDQogICAgIElmIHRoZSBFTVNL
IGlzIGF2YWlsYWJsZSBidXQgbm8gRU1TSy1iYXNlZCBDb21wb3VuZCBNQUMgd2FzIHNlbnQNCiAg
ICAgYW5kIGl0cyBwb2xpY3kgYWNjZXB0cyBNU0stYmFzZWQgTUFDLCB0aGVuIHRoZSByZWNlaXZl
ciB2YWxpZGF0ZXMNCiAgICAgaXQgdXNpbmcgdGhlIE1TSyBhbmQsIGlmIHN1Y2Nlc3NmdWwsIGdl
bmVyYXRlcyBhbmQgcmV0dXJucyBhbiBNU0stDQogICAgIGJhc2VkIENvbXBvdW5kIE1BQy4NCg0K
ICAgICBJZiB0aGUgRU1TSyBpcyBhdmFpbGFibGUgYnV0IG5vIEVNU0sgQ29tcG91bmQgTUFDIHdh
cyBzZW50IGFuZCBpdHMNCiAgICAgcG9saWN5IGRvZXMgbm90IGFjY2VwdCBNU0stYmFzZWQgTUFD
LCB0aGVuIHRoZSByZWNlaXZlciBoYW5kbGVzDQogICAgIGxpa2UgYW4gaW52YWxpZCBDcnlwdG8t
QmluZGluZyBUTFYgd2l0aCBhIGZhdGFsIGVycm9yLg0KDQpJZiB0aGUgaXRoIGlubmVyIG1ldGhv
ZCBkb2VzIG5vdCBnZW5lcmF0ZSBhbiBFTVNLIG9yIE1TSywgdGhlbiBJTVNLaQ0KaXMgc2V0IHRv
IHplcm8gKGUuZy4sIE1TS2kgPSAzMiBvY3RldHMgb2YgMHgwMHMpLiAgSWYgYW4gaW5uZXIgbWV0
aG9kDQpmYWlscywgdGhlbiBpdCBpcyBub3QgaW5jbHVkZWQgaW4gdGhpcyBjYWxjdWxhdGlvbi4N
Cg0KSXQgU2hvdWxkIFNheToNCg0KT24gdGhlIHNlbmRlciBvZiB0aGUgQ3J5cHRvLUJpbmRpbmcg
VExWIHNpZGU6DQoNCiAgICAgSWYgdGhlIEVNU0sgaXMgbm90IGF2YWlsYWJsZSwgdGhlbiB0aGUg
c2VuZGVyIGNvbXB1dGVzIHRoZSBDb21wb3VuZA0KICAgICBNQUMgdXNpbmcgdGhlIENNSyBnZW5l
cmF0ZWQgZnJvbSBNU0sgKENNSy1NU0spIG9mIHRoZSBpbm5lciBtZXRob2QuDQoNCiAgICAgSWYg
dGhlIEVNU0sgaXMgYXZhaWxhYmxlIGFuZCB0aGUgc2VuZGVyJ3MgcG9saWN5IGFjY2VwdHMgTVNL
LWJhc2VkDQogICAgIE1BQywgdGhlbiB0aGUgc2VuZGVyIGNvbXB1dGVzIHR3byBDb21wb3VuZCBN
QUMgdmFsdWVzLiAgVGhlIGZpcnN0DQogICAgIGlzIGNvbXB1dGVkIHdpdGggdGhlIENNSyBnZW5l
cmF0ZWQgZnJvbSB0aGUgRU1TSyAoQ01LLUVNU0spLiAgVGhlDQogICAgIHNlY29uZCBvbmUgaXMg
Y29tcHV0ZWQgdXNpbmcgdGhlIENNSy1NU0suICBCb3RoIE1BQ3MgYXJlDQogICAgIHRoZW4gc2Vu
dCB0byB0aGUgb3RoZXIgc2lkZS4gIFRoaXMgYWxzbyBtZWFucyB0aGUgc2VuZGVyIG11c3QgZ2Vu
ZXJhdGUNCiAgICAgYm90aCBFTVNLIGFuZCBNU0sgYmFzZWQgUy1JTUNLcy4NCg0KICAgICBJZiB0
aGUgRU1TSyBpcyBhdmFpbGFibGUgYnV0IHRoZSBzZW5kZXIncyBwb2xpY3kgZG9lcyBub3QgYWxs
b3cNCiAgICAgZG93bmdyYWRpbmcgdG8gQ01LLU1TSyBNQUMsIHRoZW4gdGhlIHNlbmRlciBTSE9V
TEQgb25seSBzZW5kDQogICAgIGEgTUFDIGNvbXB1dGVkIGZyb20gdGhlIENNSy1FTVNLLg0KDQog
ICBPbiB0aGUgcmVjZWl2ZXIgb2YgdGhlIENyeXB0by1CaW5kaW5nIFRMViBzaWRlOg0KDQogICAg
IElmIHRoZSBFTVNLIGlzIG5vdCBhdmFpbGFibGUgYW5kIGFuIENNSy1NU0sgQ29tcG91bmQgTUFD
IHdhcw0KICAgICBzZW50LCB0aGVuIHRoZSByZWNlaXZlciB2YWxpZGF0ZXMgdGhlIENvbXBvdW5k
IE1BQyBhbmQgc2VuZHMgYmFjaw0KICAgICBhbiBDTUstTVNLIENvbXBvdW5kIE1BQyByZXNwb25z
ZS4NCg0KICAgICBJZiB0aGUgRU1TSyBpcyBub3QgYXZhaWxhYmxlIGFuZCBubyBDTUstTVNLIENv
bXBvdW5kIE1BQyB3YXMNCiAgICAgc2VudCwgdGhlbiB0aGUgcmVjZWl2ZXIgaGFuZGxlcyBsaWtl
IGFuIGludmFsaWQgQ3J5cHRvLUJpbmRpbmcgVExWDQogICAgIHdpdGggYSBmYXRhbCBlcnJvci4N
Cg0KICAgICBJZiB0aGUgRU1TSyBpcyBhdmFpbGFibGUgYW5kIGEgQ01LLUVNU0sgQ29tcG91bmQg
TUFDIHdhcyBzZW50LA0KICAgICB0aGVuIHRoZSByZWNlaXZlciB2YWxpZGF0ZXMgaXQgYW5kIGNy
ZWF0ZXMgYSByZXNwb25zZSBDb21wb3VuZCBNQUMNCiAgICAgdXNpbmcgdGhlIENNSy1FTVNLLg0K
DQogICAgIElmIHRoZSBFTVNLIGlzIGF2YWlsYWJsZSBidXQgbm8gQ01LLUVNU0sgQ29tcG91bmQg
TUFDIHdhcyBzZW50DQogICAgIGFuZCBpdHMgcG9saWN5IGFjY2VwdHMgQ01LLU1TSyBNQUMsIHRo
ZW4gdGhlIHJlY2VpdmVyIHZhbGlkYXRlcw0KICAgICBpdCB1c2luZyB0aGUgQ01LLU1TSyBhbmQs
IGlmIHN1Y2Nlc3NmdWwsIGdlbmVyYXRlcyBhbmQgcmV0dXJucyBhbiBNU0stDQogICAgIGJhc2Vk
IENvbXBvdW5kIE1BQy4NCg0KICAgICBJZiB0aGUgRU1TSyBpcyBhdmFpbGFibGUgYnV0IG5vIENN
Sy1FTVNLIENvbXBvdW5kIE1BQyB3YXMgc2VudCBhbmQgaXRzDQogICAgIHBvbGljeSBkb2VzIG5v
dCBhY2NlcHQgQ01LLU1TSyBNQUMsIHRoZW4gdGhlIHJlY2VpdmVyIGhhbmRsZXMNCiAgICAgbGlr
ZSBhbiBpbnZhbGlkIENyeXB0by1CaW5kaW5nIFRMViB3aXRoIGEgZmF0YWwgZXJyb3IuDQoNClRo
ZSBJTVNLIHVzZWQgaXMgZWl0aGVyIHRoZSBFTVNLLWJhc2VkIElNU0sgb3IgdGhlIE1TSyBiYXNl
ZCBJTVNLIGRlcGVuZGluZw0KdXBvbiB0aGUgcnVsZXMgb3V0bGluZWQgYWJvdmUuIElmIHRoZSBp
dGggaW5uZXIgbWV0aG9kIGRvZXMgbm90IGdlbmVyYXRlIGFuIEVNU0sNCm9yIE1TSywgdGhlbiBJ
TVNLaSBpcyBzZXQgdG8gemVybyAoZS5nLiwgTVNLaSA9IDMyIG9jdGV0cyBvZiAweDAwcykuICAg
IEl0IGlzIHBvc3NpYmxlDQp0aGF0IHR3byBTLUlNQ0tzIGZvciBhIHN0ZXAgbWF5IGJlIGdlbmVy
YXRlZCBiYXNlZCBvbiB0aGUgcnVsZXMgYWJvdmUuICBJbiB0aGlzDQpjYXNlIHRoZSBTLUlNQ0sg
Zm9yIGZ1cnRoZXIgY2FsY3VsYXRpb25zIGlzIGNob3NlbiBhcyBmb2xsb3dzLiAgSWYgdGhlIE1B
QyBiYXNlZA0Kb24gdGhlIENNSy1FTVNLIGlzIHZlcmlmaWVkIHRoZW4gdGhlIFMtSU1DSyBnZW5l
cmF0ZWQgYmFzZWQgb24gdGhlIEVNU0sgaXMNCnVzZWQuICBFbHNlLCBpZiB0aGUgTUFDIGJhc2Vk
IG9uIHRoZSBDTUstTVNLIGlzIHZlcmlmaWVkIHRoZW4gdGhlIFMtSU1DSw0KZ2VuZXJhdGVkIGJh
c2VkIG9uIHRoZSBNU0sgaXMgdXNlZC4gIElmIGFuIGlubmVyIG1ldGhvZCBmYWlscyBvciBNQUMg
dmVyaWZpY2F0aW9uDQpmYWlscyB0aGVuIFMtSU1DSyBpcyBub3QgdXNlZCBpbiBmdXJ0aGVyIGNh
bGN1bGF0aW9uLg0KDQpTZWN0aW9uIDUuNCBTYXlzOg0KVEVBUCBhdXRoZW50aWNhdGlvbiBhc3N1
cmVzIHRoZSBNYXN0ZXIgU2Vzc2lvbiBLZXkgKE1TSykgYW5kIEV4dGVuZGVkDQogTWFzdGVyIFNl
c3Npb24gS2V5IChFTVNLKSBvdXRwdXQgZnJvbSB0aGUgRUFQIG1ldGhvZCBhcmUgdGhlIHJlc3Vs
dA0KIG9mIGFsbCBhdXRoZW50aWNhdGlvbiBjb252ZXJzYXRpb25zIGJ5IGdlbmVyYXRpbmcgYW4g
SW50ZXJtZWRpYXRlDQogQ29tcG91bmQgS2V5IChJTUNLKS4gIFRoZSBJTUNLIGlzIG11dHVhbGx5
IGRlcml2ZWQgYnkgdGhlIHBlZXIgYW5kDQogdGhlIHNlcnZlciBhcyBkZXNjcmliZWQgaW4gU2Vj
dGlvbiA1LjIgYnkgY29tYmluaW5nIHRoZSBNU0tzIGZyb20gaW5uZXINCiBFQVAgbWV0aG9kcyB3
aXRoIGtleSBtYXRlcmlhbCBmcm9tIFRFQVAgUGhhc2UgMS4NCg0KSXQgc2hvdWxkIHNheToNCg0K
VEVBUCBhdXRoZW50aWNhdGlvbiBhc3N1cmVzIHRoZSBNYXN0ZXIgU2Vzc2lvbiBLZXkgKE1TSykg
YW5kIEV4dGVuZGVkDQogTWFzdGVyIFNlc3Npb24gS2V5IChFTVNLKSBvdXRwdXQgZnJvbSB0aGUg
RUFQIG1ldGhvZCBhcmUgdGhlIHJlc3VsdA0KIG9mIGFsbCBhdXRoZW50aWNhdGlvbiBjb252ZXJz
YXRpb25zIGJ5IGdlbmVyYXRpbmcgYW4gSW50ZXJtZWRpYXRlDQogQ29tcG91bmQgS2V5IChJTUNL
KS4gIFRoZSBJTUNLIGlzIG11dHVhbGx5IGRlcml2ZWQgYnkgdGhlIHBlZXIgYW5kDQogdGhlIHNl
cnZlciBhcyBkZXNjcmliZWQgaW4gU2VjdGlvbiA1LjIgYnkgY29tYmluaW5nIHRoZSBJTVNLcyBm
cm9tIGlubmVyDQogRUFQIG1ldGhvZHMgd2l0aCBrZXkgbWF0ZXJpYWwgZnJvbSBURUFQIFBoYXNl
IDEuDQoNCk5vdGU6DQoNClRoaXMgcmV2aXNpb24gaXMgdG8gY2xhcmlmeSBob3cgdG8gaGFuZGxl
IHRoZSBjYXNlIHdoZXJlIHlvdSBuZWVkIHRvIGdlbmVyYXRlDQpib3RoIE1TSyBhbmQgRU1TSyBr
ZXlzLiAgIFRoZSBvcmlnaW5hbCB0ZXh0IHdhcyBpbmNvbXBsZXRlIGFuZCBhbWJpZ3VvdXMNCmlu
IHNvbWUgcGxhY2VzLg0K

--_000_CH2PR21MB138172CE5A552084A62E3AA9D1190CH2PR21MB1381namp_
Content-Type: text/html; charset="utf-8"
Content-Transfer-Encoding: base64

PGh0bWwgeG1sbnM6dj0idXJuOnNjaGVtYXMtbWljcm9zb2Z0LWNvbTp2bWwiIHhtbG5zOm89InVy
bjpzY2hlbWFzLW1pY3Jvc29mdC1jb206b2ZmaWNlOm9mZmljZSIgeG1sbnM6dz0idXJuOnNjaGVt
YXMtbWljcm9zb2Z0LWNvbTpvZmZpY2U6d29yZCIgeG1sbnM6bT0iaHR0cDovL3NjaGVtYXMubWlj
cm9zb2Z0LmNvbS9vZmZpY2UvMjAwNC8xMi9vbW1sIiB4bWxucz0iaHR0cDovL3d3dy53My5vcmcv
VFIvUkVDLWh0bWw0MCI+DQo8aGVhZD4NCjxtZXRhIGh0dHAtZXF1aXY9IkNvbnRlbnQtVHlwZSIg
Y29udGVudD0idGV4dC9odG1sOyBjaGFyc2V0PXV0Zi04Ij4NCjxtZXRhIG5hbWU9IkdlbmVyYXRv
ciIgY29udGVudD0iTWljcm9zb2Z0IFdvcmQgMTUgKGZpbHRlcmVkIG1lZGl1bSkiPg0KPHN0eWxl
PjwhLS0NCi8qIEZvbnQgRGVmaW5pdGlvbnMgKi8NCkBmb250LWZhY2UNCgl7Zm9udC1mYW1pbHk6
IkNhbWJyaWEgTWF0aCI7DQoJcGFub3NlLTE6MiA0IDUgMyA1IDQgNiAzIDIgNDt9DQpAZm9udC1m
YWNlDQoJe2ZvbnQtZmFtaWx5OkNhbGlicmk7DQoJcGFub3NlLTE6MiAxNSA1IDIgMiAyIDQgMyAy
IDQ7fQ0KLyogU3R5bGUgRGVmaW5pdGlvbnMgKi8NCnAuTXNvTm9ybWFsLCBsaS5Nc29Ob3JtYWws
IGRpdi5Nc29Ob3JtYWwNCgl7bWFyZ2luOjBpbjsNCglmb250LXNpemU6MTEuMHB0Ow0KCWZvbnQt
ZmFtaWx5OiJDYWxpYnJpIixzYW5zLXNlcmlmO30NCmE6bGluaywgc3Bhbi5Nc29IeXBlcmxpbmsN
Cgl7bXNvLXN0eWxlLXByaW9yaXR5Ojk5Ow0KCWNvbG9yOmJsdWU7DQoJdGV4dC1kZWNvcmF0aW9u
OnVuZGVybGluZTt9DQpzcGFuLkVtYWlsU3R5bGUxOA0KCXttc28tc3R5bGUtdHlwZTpwZXJzb25h
bC1yZXBseTsNCglmb250LWZhbWlseToiQ2FsaWJyaSIsc2Fucy1zZXJpZjsNCgljb2xvcjp3aW5k
b3d0ZXh0O30NCi5Nc29DaHBEZWZhdWx0DQoJe21zby1zdHlsZS10eXBlOmV4cG9ydC1vbmx5Ow0K
CWZvbnQtZmFtaWx5OiJDYWxpYnJpIixzYW5zLXNlcmlmO30NCkBwYWdlIFdvcmRTZWN0aW9uMQ0K
CXtzaXplOjguNWluIDExLjBpbjsNCgltYXJnaW46MS4waW4gMS4waW4gMS4waW4gMS4waW47fQ0K
ZGl2LldvcmRTZWN0aW9uMQ0KCXtwYWdlOldvcmRTZWN0aW9uMTt9DQotLT48L3N0eWxlPjwhLS1b
aWYgZ3RlIG1zbyA5XT48eG1sPg0KPG86c2hhcGVkZWZhdWx0cyB2OmV4dD0iZWRpdCIgc3BpZG1h
eD0iMTAyNiIgLz4NCjwveG1sPjwhW2VuZGlmXS0tPjwhLS1baWYgZ3RlIG1zbyA5XT48eG1sPg0K
PG86c2hhcGVsYXlvdXQgdjpleHQ9ImVkaXQiPg0KPG86aWRtYXAgdjpleHQ9ImVkaXQiIGRhdGE9
IjEiIC8+DQo8L286c2hhcGVsYXlvdXQ+PC94bWw+PCFbZW5kaWZdLS0+DQo8L2hlYWQ+DQo8Ym9k
eSBsYW5nPSJFTi1VUyIgbGluaz0iYmx1ZSIgdmxpbms9InB1cnBsZSIgc3R5bGU9IndvcmQtd3Jh
cDpicmVhay13b3JkIj4NCjxkaXYgY2xhc3M9IldvcmRTZWN0aW9uMSI+DQo8cCBjbGFzcz0iTXNv
Tm9ybWFsIj5UaGlzIGlzIGEgZGV0YWlsZWQgb25lIHNvIEnigJl2ZSB0cmllZCB0byBnbyBvdmVy
IGl0IGNhcmVmdWxseS4gTW9zdCBvZiBpdCBsb29rcyBnb29kIGJ1dCBJ4oCZbSB1bnN1cmUgYWJv
dXQgdGhpcyBwYXJ0OjxvOnA+PC9vOnA+PC9wPg0KPHAgY2xhc3M9Ik1zb05vcm1hbCI+PG86cD4m
bmJzcDs8L286cD48L3A+DQo8cCBjbGFzcz0iTXNvTm9ybWFsIj4mZ3Q7IElmIGFuIGlubmVyIG1l
dGhvZCBmYWlscyBvciBNQUMgdmVyaWZpY2F0aW9uJm5ic3A7PG86cD48L286cD48L3A+DQo8cCBj
bGFzcz0iTXNvTm9ybWFsIj5mYWlscyB0aGVuIFMtSU1DSyBpcyBub3QgdXNlZCBpbiBmdXJ0aGVy
IGNhbGN1bGF0aW9uLiZuYnNwOyZuYnNwOzxvOnA+PC9vOnA+PC9wPg0KPHAgY2xhc3M9Ik1zb05v
cm1hbCI+PG86cD4mbmJzcDs8L286cD48L3A+DQo8cCBjbGFzcz0iTXNvTm9ybWFsIj5JdCBpcyBh
IHZhbGlkIHNjZW5hcmlvIHRoYXQgbXVsdGlwbGUgYXV0aGVudGljYXRpb24gbWV0aG9kcyBydW4g
YW5kIHNvbWUgZmFpbCwgYnV0IHRoZSBvdmVyYWxsIFRFQVAgYXV0aGVudGljYXRpb24gc3VjY2Vl
ZHMuIEZvciBleGFtcGxlLCBpZiB0d28gaW5uZXIgRUFQIEF1dGhlbnRpY2F0aW9uIG1ldGhvZHMg
cnVuIGFuZCB0aGUgZmlyc3QgZmFpbHMgYnV0IHRoZSBzZWNvbmRzIHN1Y2NlZWRzLCB0aGUgY2Fs
Y3VsYXRpb24NCiBuZWVkcyB0byBiZSB2YWxpZC4gQmFzZWQgb24gdGhlIG9sZCB0ZXh0LCB0aGF0
IGF1dGhlbnRpY2F0aW9uIG1ldGhvZCBpcyBvbWl0dGVkIGZyb20gY2FsY3VsYXRpb25zLiBUaGlz
IGlzIHdoYXQgY3VycmVudCBpbXBsZW1lbnRhdGlvbnMgZG8uPG86cD48L286cD48L3A+DQo8cCBj
bGFzcz0iTXNvTm9ybWFsIj48bzpwPiZuYnNwOzwvbzpwPjwvcD4NCjxwIGNsYXNzPSJNc29Ob3Jt
YWwiPk15IGVkaXRvcmlhbCBjb21tZW50IGJhc2VkIG9uIHNvbWUgb3RoZXIgZXJyYXRhIHdvdWxk
IGJlIHRvIHRoYXQgdGV4dCBuZWVkcyB0byBzcGVjaWZ5IOKAnGF1dGhlbnRpY2F0aW9u4oCdIG1l
dGhvZHMgKHBlciBKb3VuaeKAmXMgb3RoZXIgZXJyYXRhKSBzaW5jZSB0aGUgSWRlbnRpdHkgbWV0
aG9kIGRvZXNu4oCZdCBmYWN0b3IgaW4gaGVyZS4gSSB0aGluayBpdCB3b3VsZCBhbHNvIGJlIGJl
bmVmaWNpYWwgdG8gYmUgc3BlY2lmaWMNCiBhYm91dCB0aGUgYmVoYXZpb3Igb2YgYmFzaWMgdXNl
cm5hbWUgYW5kIHBhc3N3b3JkIGF1dGhlbnRpY2F0aW9uIGhlcmUuIE9sZWcgbWFkZSBzb21lIGNv
bW1lbnRzIHRvIHRoaXMgZWZmZWN0IG9uIGFub3RoZXIgZW1haWwuIE91ciBpbXBsZW1lbnRhdGlv
biBkb2VzbuKAmXQgc3VwcG9ydCBiYXNpYyB1c2VybmFtZSBhbmQgcGFzc3dvcmQgYXV0aGVudGlj
YXRpb24gc28gSSBkb27igJl0IGhhdmUgYW55IHByaW9yIGV4cGVyaWVuY2UgaGVyZS48bzpwPjwv
bzpwPjwvcD4NCjxwIGNsYXNzPSJNc29Ob3JtYWwiPjxvOnA+Jm5ic3A7PC9vOnA+PC9wPg0KPHAg
Y2xhc3M9Ik1zb05vcm1hbCI+Sm9yZ2UgVmVyZ2FyYTxvOnA+PC9vOnA+PC9wPg0KPHAgY2xhc3M9
Ik1zb05vcm1hbCI+PG86cD4mbmJzcDs8L286cD48L3A+DQo8ZGl2IHN0eWxlPSJib3JkZXI6bm9u
ZTtib3JkZXItdG9wOnNvbGlkICNFMUUxRTEgMS4wcHQ7cGFkZGluZzozLjBwdCAwaW4gMGluIDBp
biI+DQo8cCBjbGFzcz0iTXNvTm9ybWFsIj48Yj5Gcm9tOjwvYj4gSm9zZXBoIFNhbG93ZXkgJmx0
O2pvZUBzYWxvd2V5Lm5ldCZndDsgPGJyPg0KPGI+U2VudDo8L2I+IFNhdHVyZGF5LCBPY3RvYmVy
IDI0LCAyMDIwIDU6MTggUE08YnI+DQo8Yj5Ubzo8L2I+IEVNVSBXRyAmbHQ7ZW11QGlldGYub3Jn
Jmd0Ozxicj4NCjxiPkNjOjwvYj4gT2xlZyBQZWthciAmbHQ7b2xlZy5wZWthci4yMDE3QGdtYWls
LmNvbSZndDs7IEpvdW5pIE1hbGluZW4gJmx0O2pAdzEuZmkmZ3Q7OyBKb3JnZSBWZXJnYXJhICZs
dDtqb3ZlcmdhckBtaWNyb3NvZnQuY29tJmd0Ozxicj4NCjxiPlN1YmplY3Q6PC9iPiBQcm9wb3Nl
ZCBSZXNvbHV0aW9uIHRvIFRFQVAgRXJyYXRhIDU3NzA8bzpwPjwvbzpwPjwvcD4NCjwvZGl2Pg0K
PHAgY2xhc3M9Ik1zb05vcm1hbCI+PG86cD4mbmJzcDs8L286cD48L3A+DQo8ZGl2Pg0KPHAgY2xh
c3M9Ik1zb05vcm1hbCI+RXJyYXRhIDU3NzA6Jm5ic3A7PGEgaHJlZj0iaHR0cHM6Ly9uYW0wNi5z
YWZlbGlua3MucHJvdGVjdGlvbi5vdXRsb29rLmNvbS8/dXJsPWh0dHBzJTNBJTJGJTJGd3d3LnJm
Yy1lZGl0b3Iub3JnJTJGZXJyYXRhJTJGZWlkNTc3MCZhbXA7ZGF0YT0wNCU3QzAxJTdDam92ZXJn
YXIlNDBtaWNyb3NvZnQuY29tJTdDNzI4Y2ViNmFmNjY5NGU0MGUwOGUwOGQ4Nzg3YjY2OWQlN0M3
MmY5ODhiZjg2ZjE0MWFmOTFhYjJkN2NkMDExZGI0NyU3QzElN0MwJTdDNjM3MzkxODE4Njg5Nzgx
NzIzJTdDVW5rbm93biU3Q1RXRnBiR1pzYjNkOGV5SldJam9pTUM0d0xqQXdNREFpTENKUUlqb2lW
Mmx1TXpJaUxDSkJUaUk2SWsxaGFXd2lMQ0pYVkNJNk1uMCUzRCU3QzEwMDAmYW1wO3NkYXRhPVJ1
UnJYWjVjNzByNDNSbXlsNHMlMkJWVUtBQTIybkd0b2VuTEVsYkNlVWttRSUzRCZhbXA7cmVzZXJ2
ZWQ9MCI+aHR0cHM6Ly93d3cucmZjLWVkaXRvci5vcmcvZXJyYXRhL2VpZDU3NzA8L2E+PG86cD48
L286cD48L3A+DQo8ZGl2Pg0KPHAgY2xhc3M9Ik1zb05vcm1hbCI+UHJvcG9zZWQgU3RhdHVzOiBW
ZXJpZmllZDxvOnA+PC9vOnA+PC9wPg0KPC9kaXY+DQo8ZGl2Pg0KPHAgY2xhc3M9Ik1zb05vcm1h
bCI+UmV2aXNpb246PG86cD48L286cD48L3A+DQo8L2Rpdj4NCjxkaXY+DQo8cCBjbGFzcz0iTXNv
Tm9ybWFsIj48bzpwPiZuYnNwOzwvbzpwPjwvcD4NCjwvZGl2Pg0KPGRpdj4NCjxwIGNsYXNzPSJN
c29Ob3JtYWwiPlNlY3Rpb24gNS4yIFNheXM6PG86cD48L286cD48L3A+DQo8L2Rpdj4NCjxkaXY+
DQo8cCBjbGFzcz0iTXNvTm9ybWFsIj48bzpwPiZuYnNwOzwvbzpwPjwvcD4NCjwvZGl2Pg0KPHAg
Y2xhc3M9Ik1zb05vcm1hbCI+T24gdGhlIHNlbmRlciBvZiB0aGUgQ3J5cHRvLUJpbmRpbmcgVExW
IHNpZGU6ICZuYnNwOyAmbmJzcDs8YnI+DQo8YnI+DQombmJzcDsgJm5ic3A7ICZuYnNwO0lmIHRo
ZSBFTVNLIGlzIG5vdCBhdmFpbGFibGUsIHRoZW4gdGhlIHNlbmRlciBjb21wdXRlcyB0aGUgQ29t
cG91bmQ8YnI+DQombmJzcDsgJm5ic3A7ICZuYnNwO01BQyB1c2luZyB0aGUgTVNLIG9mIHRoZSBp
bm5lciBtZXRob2QuPGJyPg0KPGJyPg0KJm5ic3A7ICZuYnNwOyAmbmJzcDtJZiB0aGUgRU1TSyBp
cyBhdmFpbGFibGUgYW5kIHRoZSBzZW5kZXIncyBwb2xpY3kgYWNjZXB0cyBNU0stYmFzZWQ8YnI+
DQombmJzcDsgJm5ic3A7ICZuYnNwO01BQywgdGhlbiB0aGUgc2VuZGVyIGNvbXB1dGVzIHR3byBD
b21wb3VuZCBNQUMgdmFsdWVzLiZuYnNwOyBUaGUgZmlyc3Q8YnI+DQombmJzcDsgJm5ic3A7ICZu
YnNwO2lzIGNvbXB1dGVkIHdpdGggdGhlIEVNU0suJm5ic3A7IFRoZSBzZWNvbmQgb25lIGlzIGNv
bXB1dGVkIHVzaW5nIHRoZTxicj4NCiZuYnNwOyAmbmJzcDsgJm5ic3A7TVNLLiZuYnNwOyBCb3Ro
IE1BQ3MgYXJlIHRoZW4gc2VudCB0byB0aGUgb3RoZXIgc2lkZS48YnI+DQo8YnI+DQombmJzcDsg
Jm5ic3A7ICZuYnNwO0lmIHRoZSBFTVNLIGlzIGF2YWlsYWJsZSBidXQgdGhlIHNlbmRlcidzIHBv
bGljeSBkb2VzIG5vdCBhbGxvdzxicj4NCiZuYnNwOyAmbmJzcDsgJm5ic3A7ZG93bmdyYWRpbmcg
dG8gTVNLLWdlbmVyYXRlZCBNQUMsIHRoZW4gdGhlIHNlbmRlciBTSE9VTEQgb25seSBzZW5kPGJy
Pg0KJm5ic3A7ICZuYnNwOyAmbmJzcDtFTVNLLWJhc2VkIE1BQy48YnI+DQo8YnI+DQombmJzcDsg
Jm5ic3A7T24gdGhlIHJlY2VpdmVyIG9mIHRoZSBDcnlwdG8tQmluZGluZyBUTFYgc2lkZTo8YnI+
DQo8YnI+DQombmJzcDsgJm5ic3A7ICZuYnNwO0lmIHRoZSBFTVNLIGlzIG5vdCBhdmFpbGFibGUg
YW5kIGFuIE1TSy1iYXNlZCBDb21wb3VuZCBNQUMgd2FzPGJyPg0KJm5ic3A7ICZuYnNwOyAmbmJz
cDtzZW50LCB0aGVuIHRoZSByZWNlaXZlciB2YWxpZGF0ZXMgdGhlIENvbXBvdW5kIE1BQyBhbmQg
c2VuZHMgYmFjazxicj4NCiZuYnNwOyAmbmJzcDsgJm5ic3A7YW4gTVNLLWJhc2VkIENvbXBvdW5k
IE1BQyByZXNwb25zZS48YnI+DQo8YnI+DQombmJzcDsgJm5ic3A7ICZuYnNwO0lmIHRoZSBFTVNL
IGlzIG5vdCBhdmFpbGFibGUgYW5kIG5vIE1TSy1iYXNlZCBDb21wb3VuZCBNQUMgd2FzPGJyPg0K
Jm5ic3A7ICZuYnNwOyAmbmJzcDtzZW50LCB0aGVuIHRoZSByZWNlaXZlciBoYW5kbGVzIGxpa2Ug
YW4gaW52YWxpZCBDcnlwdG8tQmluZGluZyBUTFY8YnI+DQombmJzcDsgJm5ic3A7ICZuYnNwO3dp
dGggYSBmYXRhbCBlcnJvci48YnI+DQo8YnI+DQombmJzcDsgJm5ic3A7ICZuYnNwO0lmIHRoZSBF
TVNLIGlzIGF2YWlsYWJsZSBhbmQgYW4gRU1TSy1iYXNlZCBDb21wb3VuZCBNQUMgd2FzIHNlbnQs
PGJyPg0KJm5ic3A7ICZuYnNwOyAmbmJzcDt0aGVuIHRoZSByZWNlaXZlciB2YWxpZGF0ZXMgaXQg
YW5kIGNyZWF0ZXMgYSByZXNwb25zZSBDb21wb3VuZCBNQUM8YnI+DQombmJzcDsgJm5ic3A7ICZu
YnNwO3VzaW5nIHRoZSBFTVNLLjxicj4NCjxicj4NCiZuYnNwOyAmbmJzcDsgJm5ic3A7SWYgdGhl
IEVNU0sgaXMgYXZhaWxhYmxlIGJ1dCBubyBFTVNLLWJhc2VkIENvbXBvdW5kIE1BQyB3YXMgc2Vu
dDxicj4NCiZuYnNwOyAmbmJzcDsgJm5ic3A7YW5kIGl0cyBwb2xpY3kgYWNjZXB0cyBNU0stYmFz
ZWQgTUFDLCB0aGVuIHRoZSByZWNlaXZlciB2YWxpZGF0ZXM8YnI+DQombmJzcDsgJm5ic3A7ICZu
YnNwO2l0IHVzaW5nIHRoZSBNU0sgYW5kLCBpZiBzdWNjZXNzZnVsLCBnZW5lcmF0ZXMgYW5kIHJl
dHVybnMgYW4gTVNLLTxicj4NCiZuYnNwOyAmbmJzcDsgJm5ic3A7YmFzZWQgQ29tcG91bmQgTUFD
Ljxicj4NCjxicj4NCiZuYnNwOyAmbmJzcDsgJm5ic3A7SWYgdGhlIEVNU0sgaXMgYXZhaWxhYmxl
IGJ1dCBubyBFTVNLIENvbXBvdW5kIE1BQyB3YXMgc2VudCBhbmQgaXRzPGJyPg0KJm5ic3A7ICZu
YnNwOyAmbmJzcDtwb2xpY3kgZG9lcyBub3QgYWNjZXB0IE1TSy1iYXNlZCBNQUMsIHRoZW4gdGhl
IHJlY2VpdmVyIGhhbmRsZXM8YnI+DQombmJzcDsgJm5ic3A7ICZuYnNwO2xpa2UgYW4gaW52YWxp
ZCBDcnlwdG8tQmluZGluZyBUTFYgd2l0aCBhIGZhdGFsIGVycm9yLjxvOnA+PC9vOnA+PC9wPg0K
PGRpdj4NCjxwIGNsYXNzPSJNc29Ob3JtYWwiPjxvOnA+Jm5ic3A7PC9vOnA+PC9wPg0KPC9kaXY+
DQo8ZGl2Pg0KPHAgY2xhc3M9Ik1zb05vcm1hbCI+SWYgdGhlIGl0aCBpbm5lciBtZXRob2QgZG9l
cyBub3QgZ2VuZXJhdGUgYW4gRU1TSyBvciBNU0ssIHRoZW4gSU1TS2k8YnI+DQppcyBzZXQgdG8g
emVybyAoZS5nLiwgTVNLaSA9IDMyIG9jdGV0cyBvZiAweDAwcykuJm5ic3A7IElmIGFuIGlubmVy
IG1ldGhvZDxicj4NCmZhaWxzLCB0aGVuIGl0IGlzIG5vdCBpbmNsdWRlZCBpbiB0aGlzIGNhbGN1
bGF0aW9uLjxvOnA+PC9vOnA+PC9wPg0KPC9kaXY+DQo8ZGl2Pg0KPHAgY2xhc3M9Ik1zb05vcm1h
bCI+PG86cD4mbmJzcDs8L286cD48L3A+DQo8L2Rpdj4NCjxkaXY+DQo8cCBjbGFzcz0iTXNvTm9y
bWFsIj5JdCBTaG91bGQgU2F5OjxvOnA+PC9vOnA+PC9wPg0KPC9kaXY+DQo8ZGl2Pg0KPHAgY2xh
c3M9Ik1zb05vcm1hbCI+PG86cD4mbmJzcDs8L286cD48L3A+DQo8L2Rpdj4NCjxkaXY+DQo8cCBj
bGFzcz0iTXNvTm9ybWFsIj5PbiB0aGUgc2VuZGVyIG9mIHRoZSBDcnlwdG8tQmluZGluZyBUTFYg
c2lkZTogJm5ic3A7ICZuYnNwOzxicj4NCjxicj4NCiZuYnNwOyAmbmJzcDsgJm5ic3A7SWYgdGhl
IEVNU0sgaXMgbm90IGF2YWlsYWJsZSwgdGhlbiB0aGUgc2VuZGVyIGNvbXB1dGVzIHRoZSBDb21w
b3VuZDxicj4NCiZuYnNwOyAmbmJzcDsgJm5ic3A7TUFDIHVzaW5nIHRoZSBDTUsgZ2VuZXJhdGVk
IGZyb20gTVNLIChDTUstTVNLKSBvZiB0aGUgaW5uZXIgbWV0aG9kLjxicj4NCjxicj4NCiZuYnNw
OyAmbmJzcDsgJm5ic3A7SWYgdGhlIEVNU0sgaXMgYXZhaWxhYmxlIGFuZCB0aGUgc2VuZGVyJ3Mg
cG9saWN5IGFjY2VwdHMgTVNLLWJhc2VkPGJyPg0KJm5ic3A7ICZuYnNwOyAmbmJzcDtNQUMsIHRo
ZW4gdGhlIHNlbmRlciBjb21wdXRlcyB0d28gQ29tcG91bmQgTUFDIHZhbHVlcy4mbmJzcDsgVGhl
IGZpcnN0PGJyPg0KJm5ic3A7ICZuYnNwOyAmbmJzcDtpcyBjb21wdXRlZCB3aXRoIHRoZSBDTUsg
Z2VuZXJhdGVkIGZyb20gdGhlIEVNU0sgKENNSy1FTVNLKS4mbmJzcDsgVGhlJm5ic3A7PG86cD48
L286cD48L3A+DQo8L2Rpdj4NCjxkaXY+DQo8cCBjbGFzcz0iTXNvTm9ybWFsIj4mbmJzcDsgJm5i
c3A7ICZuYnNwO3NlY29uZCBvbmUgaXMgY29tcHV0ZWQgdXNpbmcgdGhlJm5ic3A7Q01LLU1TSy4m
bmJzcDsgQm90aCBNQUNzIGFyZSZuYnNwOzxvOnA+PC9vOnA+PC9wPg0KPC9kaXY+DQo8ZGl2Pg0K
PHAgY2xhc3M9Ik1zb05vcm1hbCI+Jm5ic3A7ICZuYnNwOyAmbmJzcDt0aGVuIHNlbnQgdG8gdGhl
IG90aGVyIHNpZGUuJm5ic3A7IFRoaXMgYWxzbyBtZWFucyB0aGUgc2VuZGVyIG11c3QgZ2VuZXJh
dGU8bzpwPjwvbzpwPjwvcD4NCjwvZGl2Pg0KPGRpdj4NCjxwIGNsYXNzPSJNc29Ob3JtYWwiPiZu
YnNwOyAmbmJzcDsgJm5ic3A7Ym90aCBFTVNLIGFuZCBNU0sgYmFzZWQgUy1JTUNLcy48YnI+DQo8
YnI+DQombmJzcDsgJm5ic3A7ICZuYnNwO0lmIHRoZSBFTVNLIGlzIGF2YWlsYWJsZSBidXQgdGhl
IHNlbmRlcidzIHBvbGljeSBkb2VzIG5vdCBhbGxvdzxicj4NCiZuYnNwOyAmbmJzcDsgJm5ic3A7
ZG93bmdyYWRpbmcgdG8gQ01LLU1TSyBNQUMsIHRoZW4gdGhlIHNlbmRlciBTSE9VTEQgb25seSBz
ZW5kPGJyPg0KJm5ic3A7ICZuYnNwOyAmbmJzcDthIE1BQyBjb21wdXRlZCBmcm9tIHRoZSBDTUst
RU1TSy48YnI+DQo8YnI+DQombmJzcDsgJm5ic3A7T24gdGhlIHJlY2VpdmVyIG9mIHRoZSBDcnlw
dG8tQmluZGluZyBUTFYgc2lkZTo8YnI+DQo8YnI+DQombmJzcDsgJm5ic3A7ICZuYnNwO0lmIHRo
ZSBFTVNLIGlzIG5vdCBhdmFpbGFibGUgYW5kIGFuIENNSy1NU0sgQ29tcG91bmQgTUFDIHdhczxi
cj4NCiZuYnNwOyAmbmJzcDsgJm5ic3A7c2VudCwgdGhlbiB0aGUgcmVjZWl2ZXIgdmFsaWRhdGVz
IHRoZSBDb21wb3VuZCBNQUMgYW5kIHNlbmRzIGJhY2s8YnI+DQombmJzcDsgJm5ic3A7ICZuYnNw
O2FuIENNSy1NU0sgQ29tcG91bmQgTUFDIHJlc3BvbnNlLjxicj4NCjxicj4NCiZuYnNwOyAmbmJz
cDsgJm5ic3A7SWYgdGhlIEVNU0sgaXMgbm90IGF2YWlsYWJsZSBhbmQgbm8gQ01LLU1TSyBDb21w
b3VuZCBNQUMgd2FzPGJyPg0KJm5ic3A7ICZuYnNwOyAmbmJzcDtzZW50LCB0aGVuIHRoZSByZWNl
aXZlciBoYW5kbGVzIGxpa2UgYW4gaW52YWxpZCBDcnlwdG8tQmluZGluZyBUTFY8YnI+DQombmJz
cDsgJm5ic3A7ICZuYnNwO3dpdGggYSBmYXRhbCBlcnJvci48YnI+DQo8YnI+DQombmJzcDsgJm5i
c3A7ICZuYnNwO0lmIHRoZSBFTVNLIGlzIGF2YWlsYWJsZSBhbmQgYSBDTUstRU1TSyBDb21wb3Vu
ZCBNQUMgd2FzIHNlbnQsPGJyPg0KJm5ic3A7ICZuYnNwOyAmbmJzcDt0aGVuIHRoZSByZWNlaXZl
ciB2YWxpZGF0ZXMgaXQgYW5kIGNyZWF0ZXMgYSByZXNwb25zZSBDb21wb3VuZCBNQUM8YnI+DQom
bmJzcDsgJm5ic3A7ICZuYnNwO3VzaW5nIHRoZSBDTUstRU1TSy48YnI+DQo8YnI+DQombmJzcDsg
Jm5ic3A7ICZuYnNwO0lmIHRoZSBFTVNLIGlzIGF2YWlsYWJsZSBidXQgbm8gQ01LLUVNU0sgQ29t
cG91bmQgTUFDIHdhcyBzZW50PGJyPg0KJm5ic3A7ICZuYnNwOyAmbmJzcDthbmQgaXRzIHBvbGlj
eSBhY2NlcHRzIENNSy1NU0sgTUFDLCB0aGVuIHRoZSByZWNlaXZlciB2YWxpZGF0ZXM8YnI+DQom
bmJzcDsgJm5ic3A7ICZuYnNwO2l0IHVzaW5nIHRoZSBDTUstTVNLIGFuZCwgaWYgc3VjY2Vzc2Z1
bCwgZ2VuZXJhdGVzIGFuZCByZXR1cm5zIGFuIE1TSy08YnI+DQombmJzcDsgJm5ic3A7ICZuYnNw
O2Jhc2VkIENvbXBvdW5kIE1BQy48YnI+DQo8YnI+DQombmJzcDsgJm5ic3A7ICZuYnNwO0lmIHRo
ZSBFTVNLIGlzIGF2YWlsYWJsZSBidXQgbm8gQ01LLUVNU0sgQ29tcG91bmQgTUFDIHdhcyBzZW50
IGFuZCBpdHM8YnI+DQombmJzcDsgJm5ic3A7ICZuYnNwO3BvbGljeSBkb2VzIG5vdCBhY2NlcHQg
Q01LLU1TSyBNQUMsIHRoZW4gdGhlIHJlY2VpdmVyIGhhbmRsZXM8YnI+DQombmJzcDsgJm5ic3A7
ICZuYnNwO2xpa2UgYW4gaW52YWxpZCBDcnlwdG8tQmluZGluZyBUTFYgd2l0aCBhIGZhdGFsIGVy
cm9yLjxvOnA+PC9vOnA+PC9wPg0KPC9kaXY+DQo8ZGl2Pg0KPHAgY2xhc3M9Ik1zb05vcm1hbCI+
PG86cD4mbmJzcDs8L286cD48L3A+DQo8L2Rpdj4NCjxwIGNsYXNzPSJNc29Ob3JtYWwiPlRoZSBJ
TVNLIHVzZWQgaXMgZWl0aGVyIHRoZSBFTVNLLWJhc2VkIElNU0sgb3IgdGhlIE1TSyBiYXNlZCBJ
TVNLIGRlcGVuZGluZzxicj4NCnVwb24gdGhlIHJ1bGVzIG91dGxpbmVkIGFib3ZlLiBJZiB0aGUg
aXRoIGlubmVyIG1ldGhvZCBkb2VzIG5vdCBnZW5lcmF0ZSBhbiBFTVNLJm5ic3A7PGJyPg0Kb3Ig
TVNLLCB0aGVuIElNU0tpIGlzIHNldCB0byB6ZXJvIChlLmcuLCBNU0tpID0gMzIgb2N0ZXRzIG9m
IDB4MDBzKS4gJm5ic3A7Jm5ic3A7IEl0IGlzIHBvc3NpYmxlJm5ic3A7PG86cD48L286cD48L3A+
DQo8ZGl2Pg0KPHAgY2xhc3M9Ik1zb05vcm1hbCI+dGhhdCB0d28gUy1JTUNLcyBmb3IgYSBzdGVw
IG1heSBiZSBnZW5lcmF0ZWQgYmFzZWQgb24gdGhlIHJ1bGVzIGFib3ZlLiZuYnNwOyBJbiB0aGlz
Jm5ic3A7PG86cD48L286cD48L3A+DQo8L2Rpdj4NCjxkaXY+DQo8cCBjbGFzcz0iTXNvTm9ybWFs
Ij5jYXNlIHRoZSBTLUlNQ0sgZm9yJm5ic3A7ZnVydGhlciBjYWxjdWxhdGlvbnMgaXMgY2hvc2Vu
IGFzIGZvbGxvd3MuJm5ic3A7IElmIHRoZSBNQUMgYmFzZWQmbmJzcDs8bzpwPjwvbzpwPjwvcD4N
CjwvZGl2Pg0KPGRpdj4NCjxwIGNsYXNzPSJNc29Ob3JtYWwiPm9uIHRoZSBDTUstRU1TSyBpcyZu
YnNwO3ZlcmlmaWVkIHRoZW4gdGhlIFMtSU1DSyBnZW5lcmF0ZWQgYmFzZWQgb24gdGhlIEVNU0sg
aXMmbmJzcDs8bzpwPjwvbzpwPjwvcD4NCjwvZGl2Pg0KPGRpdj4NCjxwIGNsYXNzPSJNc29Ob3Jt
YWwiPnVzZWQuJm5ic3A7IEVsc2UsIGlmIHRoZSBNQUMmbmJzcDtiYXNlZCBvbiB0aGUgQ01LLU1T
SyBpcyB2ZXJpZmllZCB0aGVuIHRoZSBTLUlNQ0smbmJzcDs8bzpwPjwvbzpwPjwvcD4NCjwvZGl2
Pg0KPGRpdj4NCjxwIGNsYXNzPSJNc29Ob3JtYWwiPmdlbmVyYXRlZCBiYXNlZCBvbiB0aGUgTVNL
Jm5ic3A7aXMgdXNlZC4mbmJzcDsgSWYgYW4gaW5uZXIgbWV0aG9kIGZhaWxzIG9yIE1BQyB2ZXJp
ZmljYXRpb24mbmJzcDs8bzpwPjwvbzpwPjwvcD4NCjwvZGl2Pg0KPGRpdj4NCjxwIGNsYXNzPSJN
c29Ob3JtYWwiPmZhaWxzIHRoZW4gUy1JTUNLIGlzIG5vdCB1c2VkIGluIGZ1cnRoZXIgY2FsY3Vs
YXRpb24uJm5ic3A7Jm5ic3A7PG86cD48L286cD48L3A+DQo8ZGl2Pg0KPGRpdj4NCjxwIGNsYXNz
PSJNc29Ob3JtYWwiPjxvOnA+Jm5ic3A7PC9vOnA+PC9wPg0KPC9kaXY+DQo8ZGl2Pg0KPHAgY2xh
c3M9Ik1zb05vcm1hbCIgc3R5bGU9Im1hcmdpbi1ib3R0b206MTIuMHB0Ij5TZWN0aW9uIDUuNCBT
YXlzOjxvOnA+PC9vOnA+PC9wPg0KPC9kaXY+DQo8ZGl2Pg0KPHAgY2xhc3M9Ik1zb05vcm1hbCI+
VEVBUCBhdXRoZW50aWNhdGlvbiBhc3N1cmVzIHRoZSBNYXN0ZXIgU2Vzc2lvbiBLZXkgKE1TSykg
YW5kIEV4dGVuZGVkPGJyPg0KJm5ic3A7TWFzdGVyIFNlc3Npb24gS2V5IChFTVNLKSBvdXRwdXQg
ZnJvbSB0aGUgRUFQIG1ldGhvZCBhcmUgdGhlIHJlc3VsdDxicj4NCiZuYnNwO29mIGFsbCBhdXRo
ZW50aWNhdGlvbiBjb252ZXJzYXRpb25zIGJ5IGdlbmVyYXRpbmcgYW4gSW50ZXJtZWRpYXRlPGJy
Pg0KJm5ic3A7Q29tcG91bmQgS2V5IChJTUNLKS4mbmJzcDsgVGhlIElNQ0sgaXMgbXV0dWFsbHkg
ZGVyaXZlZCBieSB0aGUgcGVlciBhbmQ8YnI+DQombmJzcDt0aGUgc2VydmVyIGFzIGRlc2NyaWJl
ZCBpbiBTZWN0aW9uIDUuMiBieSBjb21iaW5pbmcgdGhlIE1TS3MgZnJvbSBpbm5lcjxvOnA+PC9v
OnA+PC9wPg0KPC9kaXY+DQo8ZGl2Pg0KPHAgY2xhc3M9Ik1zb05vcm1hbCI+Jm5ic3A7RUFQIG1l
dGhvZHMgd2l0aCBrZXkgbWF0ZXJpYWwgZnJvbSBURUFQIFBoYXNlIDEuPG86cD48L286cD48L3A+
DQo8L2Rpdj4NCjxkaXY+DQo8cCBjbGFzcz0iTXNvTm9ybWFsIj48bzpwPiZuYnNwOzwvbzpwPjwv
cD4NCjwvZGl2Pg0KPGRpdj4NCjxwIGNsYXNzPSJNc29Ob3JtYWwiPkl0IHNob3VsZCBzYXk6PG86
cD48L286cD48L3A+DQo8L2Rpdj4NCjxkaXY+DQo8cCBjbGFzcz0iTXNvTm9ybWFsIj48bzpwPiZu
YnNwOzwvbzpwPjwvcD4NCjwvZGl2Pg0KPGRpdj4NCjxkaXY+DQo8cCBjbGFzcz0iTXNvTm9ybWFs
Ij5URUFQIGF1dGhlbnRpY2F0aW9uIGFzc3VyZXMgdGhlIE1hc3RlciBTZXNzaW9uIEtleSAoTVNL
KSBhbmQgRXh0ZW5kZWQ8YnI+DQombmJzcDtNYXN0ZXIgU2Vzc2lvbiBLZXkgKEVNU0spIG91dHB1
dCBmcm9tIHRoZSBFQVAgbWV0aG9kIGFyZSB0aGUgcmVzdWx0PGJyPg0KJm5ic3A7b2YgYWxsIGF1
dGhlbnRpY2F0aW9uIGNvbnZlcnNhdGlvbnMgYnkgZ2VuZXJhdGluZyBhbiBJbnRlcm1lZGlhdGU8
YnI+DQombmJzcDtDb21wb3VuZCBLZXkgKElNQ0spLiZuYnNwOyBUaGUgSU1DSyBpcyBtdXR1YWxs
eSBkZXJpdmVkIGJ5IHRoZSBwZWVyIGFuZDxicj4NCiZuYnNwO3RoZSBzZXJ2ZXIgYXMgZGVzY3Jp
YmVkIGluIFNlY3Rpb24gNS4yIGJ5IGNvbWJpbmluZyB0aGUgSU1TS3MgZnJvbSBpbm5lcjxvOnA+
PC9vOnA+PC9wPg0KPC9kaXY+DQo8ZGl2Pg0KPHAgY2xhc3M9Ik1zb05vcm1hbCI+Jm5ic3A7RUFQ
IG1ldGhvZHMgd2l0aCBrZXkgbWF0ZXJpYWwgZnJvbSBURUFQIFBoYXNlIDEuPG86cD48L286cD48
L3A+DQo8L2Rpdj4NCjwvZGl2Pg0KPGRpdj4NCjxwIGNsYXNzPSJNc29Ob3JtYWwiPjxvOnA+Jm5i
c3A7PC9vOnA+PC9wPg0KPC9kaXY+DQo8L2Rpdj4NCjwvZGl2Pg0KPGRpdj4NCjxwIGNsYXNzPSJN
c29Ob3JtYWwiPk5vdGU6PG86cD48L286cD48L3A+DQo8L2Rpdj4NCjxkaXY+DQo8cCBjbGFzcz0i
TXNvTm9ybWFsIj48bzpwPiZuYnNwOzwvbzpwPjwvcD4NCjwvZGl2Pg0KPGRpdj4NCjxwIGNsYXNz
PSJNc29Ob3JtYWwiPlRoaXMgcmV2aXNpb24gaXMgdG8gY2xhcmlmeSBob3cgdG8gaGFuZGxlIHRo
ZSBjYXNlIHdoZXJlIHlvdSBuZWVkIHRvIGdlbmVyYXRlJm5ic3A7PG86cD48L286cD48L3A+DQo8
L2Rpdj4NCjxkaXY+DQo8cCBjbGFzcz0iTXNvTm9ybWFsIj5ib3RoIE1TSyBhbmQgRU1TSyBrZXlz
LiZuYnNwOyAmbmJzcDtUaGUgb3JpZ2luYWwgdGV4dCB3YXMgaW5jb21wbGV0ZSZuYnNwO2FuZCBh
bWJpZ3VvdXMmbmJzcDs8bzpwPjwvbzpwPjwvcD4NCjwvZGl2Pg0KPGRpdj4NCjxwIGNsYXNzPSJN
c29Ob3JtYWwiPmluIHNvbWUgcGxhY2VzLiZuYnNwOyZuYnNwOzxvOnA+PC9vOnA+PC9wPg0KPC9k
aXY+DQo8L2Rpdj4NCjwvZGl2Pg0KPC9ib2R5Pg0KPC9odG1sPg0K

--_000_CH2PR21MB138172CE5A552084A62E3AA9D1190CH2PR21MB1381namp_--


From nobody Mon Oct 26 20:22:16 2020
Return-Path: <joe@salowey.net>
X-Original-To: emu@ietfa.amsl.com
Delivered-To: emu@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 537A73A12CE for <emu@ietfa.amsl.com>; Mon, 26 Oct 2020 20:22:14 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.899
X-Spam-Level: 
X-Spam-Status: No, score=-1.899 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, HTML_MESSAGE=0.001, SPF_HELO_NONE=0.001, SPF_PASS=-0.001] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (2048-bit key) header.d=salowey-net.20150623.gappssmtp.com
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 R5gRq97_z-zI for <emu@ietfa.amsl.com>; Mon, 26 Oct 2020 20:22:12 -0700 (PDT)
Received: from mail-qk1-x736.google.com (mail-qk1-x736.google.com [IPv6:2607:f8b0:4864:20::736]) (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 C30293A12D0 for <emu@ietf.org>; Mon, 26 Oct 2020 20:22:12 -0700 (PDT)
Received: by mail-qk1-x736.google.com with SMTP id t128so42719qke.0 for <emu@ietf.org>; Mon, 26 Oct 2020 20:22:12 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=salowey-net.20150623.gappssmtp.com; s=20150623; h=mime-version:references:in-reply-to:from:date:message-id:subject:to :cc; bh=+fQ/WH4Y1Wny8MxVq2jg+vHof73+1mKqYXQq09N5rKA=; b=kyur42pZowtm6dEvfM0/qnqvH6wvxpgKya72VrriZNCyaCobgzKC6TsocK8ybEg8Rs Otta3f42/tNRYVc/QTBMuhanYnGjZpO/60StRIsvMygAjmipiHzIb5LfF/YlXA9Jvb0b JG6WjmyqtABMuBJ0EvHJsxe20Jw+koFo2gQLLevndcmPEcUIzcshjup6quel4+wuY1C2 TBau0TdEY2+8b/vZAIizi9/u4wrw/cHllLHF1N/hBMKPRayhUtaBjL7GFyoZHgEHDxk5 CFsbjuv1W4Ly50zdCfaX/VoLPkA+I91D5Ul7IAzs1rP0U1P7kzr77EEI/K/rI8Nkj7E+ McAA==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:mime-version:references:in-reply-to:from:date :message-id:subject:to:cc; bh=+fQ/WH4Y1Wny8MxVq2jg+vHof73+1mKqYXQq09N5rKA=; b=RGi4+YEReZD4xhaGfkCnL/iDM4WidU5dXISD2pBIB8nEWa7cKOx3+dlkfpnQX4czQ8 d6veag1/V7QwIM+kmhLJg0RJD5v8/8fNDXtblLue0zILvw8Wc6l7Y0dlv3Ey96G51pFL nQz4cQ9IjX4ZLW5/0y84clGu60kkNA4cgjSbqC5h+eHbIdyoe0FpM9+AWNZiSiMc+kFy 7yQqqy+GaOp5UzNg4VrRtwxvCRUSUoQfLibDCOgzXFvQjFfQ9ar//pLOi0hbPn1QNnDB CSNfV3lMGnN/g7wuSLl4cPnn/yRYdyM21obMTwodTiUU7xC0RTrzTUlxMDwuNYpoNP9c yzJA==
X-Gm-Message-State: AOAM531VsmVbruKPS8uqWUbGDzDl6MEuXcg26NYEG+6PDERS9vW49SLT 7+jJilcvickVJksHsd6B57oqPdyy9YcH1AgJP1hbDg==
X-Google-Smtp-Source: ABdhPJzpTCp85xvP0Nq/MbieHhaJCEQCJXQ7LisGxQXIxv4dhdKsXR4BiOVPkMpkbxrMR7bb7DvwYwItQaZKJouydIc=
X-Received: by 2002:a05:620a:215d:: with SMTP id m29mr298355qkm.138.1603768931694;  Mon, 26 Oct 2020 20:22:11 -0700 (PDT)
MIME-Version: 1.0
References: <CAOgPGoBO161S5su8J8Tt8tazYMNWp83T2MdkLFDQ4y2ZvbcaNw@mail.gmail.com> <CABXxEz_r+5d+swfkbg2vQ-CRr5KaWcsjwLrAHb00rRA7K_Cb9w@mail.gmail.com>
In-Reply-To: <CABXxEz_r+5d+swfkbg2vQ-CRr5KaWcsjwLrAHb00rRA7K_Cb9w@mail.gmail.com>
From: Joseph Salowey <joe@salowey.net>
Date: Mon, 26 Oct 2020 20:22:00 -0700
Message-ID: <CAOgPGoAUj6qXbOA8VW33D5u6ww-YFtD16oCyOqFe25_V5tidRQ@mail.gmail.com>
To: Oleg Pekar <oleg.pekar.2017@gmail.com>
Cc: EMU WG <emu@ietf.org>, Jouni Malinen <j@w1.fi>,  Jorge Vergara <jovergar=40microsoft.com@dmarc.ietf.org>
Content-Type: multipart/alternative; boundary="00000000000079d05f05b29e8d81"
Archived-At: <https://mailarchive.ietf.org/arch/msg/emu/4fMynYuUUaqGUks7qa4wju-wwpc>
Subject: Re: [Emu] Proposed resolution for TEAP errata 5775
X-BeenThere: emu@ietf.org
X-Mailman-Version: 2.1.29
Precedence: list
List-Id: "EAP Methods Update \(EMU\)" <emu.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/emu>, <mailto:emu-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/emu/>
List-Post: <mailto:emu@ietf.org>
List-Help: <mailto:emu-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/emu>, <mailto:emu-request@ietf.org?subject=subscribe>
X-List-Received-Date: Tue, 27 Oct 2020 03:22:14 -0000

--00000000000079d05f05b29e8d81
Content-Type: text/plain; charset="UTF-8"

On Mon, Oct 26, 2020 at 1:25 AM Oleg Pekar <oleg.pekar.2017@gmail.com>
wrote:

> It Should say:
>>
>>     S-IMCK[j] = first 40 octets of IMCK[j]
>>     CMK[j] = last 20 octets of IMCK[j]
>> where TLS-PRF is the PRF negotiated as part of TLS handshake [RFC5246].
>> If no inner EAP method has been run the S-IMCK and CMK are generated as
>> above from S-IMCK[0].
>
>
> Joe, for me it still doesn't sound as exact enough instructions. We should
> explain how to generate S-IMCK and CMK for no inner method case with more
> details.
>
>
[Joe]  Good catch,  S-IMCK[0] is only 40 octets.   Looking at this I think
it makes more sense to Change

If the ith inner method does not generate an EMSK or MSK, then IMSKi
   is set to zero (e.g., MSKi = 32 octets of 0x00s).


To:

If the jth inner method does not generate an EMSK or MSK, or no inner

  method has been run then IMSK[j] is set to zero (32 octets of 0x00s).




> The Crypto-Binding TLV MUST be exchanged and verified before the
>>  final Result TLV exchange, regardless of whether there is an inner
>>  EAP method authentication or not.
>
> This still remains an open question whether we MUST send Crypto-Binding
> TLV after Basic-Password-Authentication exchange or not. Is
> Basic-Password-Authentication treated just as a case of no inner EAP
> authentication method? It is also discussed in the errata 5844 thread.
>
> [Joe] I don't think so, but let's discuss on the 5844 thread.


> Regarding introduction of Zero-MSK flag in Crypto-Binding TLV - do you
> think it is unnecessary? So if one peer doesn't export a specific inner
> method MSK and ESMK and uses Zero-MSK and another peer expects MSK or ESMK
> - then the Crypto-Binding TLV exchange will fail naturally. Maybe it's
> worth saying exactly that if the inner method exports MSK or EMSK then each
> peer MUST use it and not Zero-MSK.
>

[Joe]  It doesn't seem to me that the Zero-MSK flag is necessary, I'd
rather not add new signals if we do not need them now.  If a method
generates an MSK then I think it must be used.   We can add a sentence
saying that to the above revision.

 If the jth inner method does not generate an EMSK or MSK, or no inner

 method has been run then IMSK[j] is set to zero (32 octets of 0x00s).

 If a method generates an MSK or EMSK the zero IMSK MUST NOT be used.

--00000000000079d05f05b29e8d81
Content-Type: text/html; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable

<div dir=3D"ltr"><div dir=3D"ltr"><br></div><br><div class=3D"gmail_quote">=
<div dir=3D"ltr" class=3D"gmail_attr">On Mon, Oct 26, 2020 at 1:25 AM Oleg =
Pekar &lt;<a href=3D"mailto:oleg.pekar.2017@gmail.com" target=3D"_blank">ol=
eg.pekar.2017@gmail.com</a>&gt; wrote:<br></div><blockquote class=3D"gmail_=
quote" style=3D"margin:0px 0px 0px 0.8ex;border-left:1px solid rgb(204,204,=
204);padding-left:1ex"><div dir=3D"ltr"><div dir=3D"ltr"><blockquote class=
=3D"gmail_quote" style=3D"margin:0px 0px 0px 0.8ex;border-left:1px solid rg=
b(204,204,204);padding-left:1ex">It Should say:<br>=C2=A0 =C2=A0=C2=A0<br>=
=C2=A0 =C2=A0 S-IMCK[j] =3D first 40 octets of IMCK[j]=C2=A0<br>=C2=A0 =C2=
=A0 CMK[j] =3D last 20 octets of IMCK[j]=C2=A0<br>where TLS-PRF is the PRF =
negotiated as part of TLS handshake [RFC5246].=C2=A0=C2=A0<br>If no inner E=
AP method has been run the S-IMCK and CMK are generated as<br>above from S-=
IMCK[0].</blockquote><div><br></div><div>Joe, for me it still doesn&#39;t s=
ound as exact=C2=A0enough instructions. We should explain how to generate=
=C2=A0S-IMCK and CMK for no inner method case with more details.=C2=A0</div=
><div><br></div></div></div></blockquote><div><br></div><div>[Joe]=C2=A0 Go=
od catch,=C2=A0 S-IMCK[0] is only 40 octets.=C2=A0 =C2=A0Looking at this I =
think it makes more sense to Change</div><div><br></div><div><pre style=3D"=
font-size:13.3333px;margin-top:0px;margin-bottom:0px;break-before:page;colo=
r:rgb(0,0,0)">If the ith inner method does not generate an EMSK or MSK, the=
n IMSKi
   is set to zero (e.g., MSKi =3D 32 octets of 0x00s). </pre><pre style=3D"=
font-size:13.3333px;margin-top:0px;margin-bottom:0px;break-before:page;colo=
r:rgb(0,0,0)"><br></pre>To:</div><div><br></div><div><pre style=3D"font-siz=
e:13.3333px;margin-top:0px;margin-bottom:0px;break-before:page;color:rgb(0,=
0,0)">If the jth inner method does not generate an EMSK or MSK, or no inner=
</pre><pre style=3D"font-size:13.3333px;margin-top:0px;margin-bottom:0px;br=
eak-before:page;color:rgb(0,0,0)">  method has been run then IMSK[j] is set=
 to zero (32 octets of 0x00s). </pre><pre style=3D"font-size:13.3333px;marg=
in-top:0px;margin-bottom:0px;break-before:page;color:rgb(0,0,0)"><br></pre>=
</div><div>=C2=A0</div><blockquote class=3D"gmail_quote" style=3D"margin:0p=
x 0px 0px 0.8ex;border-left:1px solid rgb(204,204,204);padding-left:1ex"><d=
iv dir=3D"ltr"><div dir=3D"ltr"><div></div><blockquote class=3D"gmail_quote=
" style=3D"margin:0px 0px 0px 0.8ex;border-left:1px solid rgb(204,204,204);=
padding-left:1ex">The Crypto-Binding TLV MUST be exchanged and verified bef=
ore the<br>=C2=A0final Result TLV exchange, regardless of whether there is =
an inner<br>=C2=A0EAP method authentication or not.=C2=A0=C2=A0</blockquote=
><div>This still remains an open question whether we MUST send Crypto-Bindi=
ng TLV after Basic-Password-Authentication=C2=A0exchange or not. Is Basic-P=
assword-Authentication treated just as a case of no inner EAP authenticatio=
n method? It is also discussed in the errata=C2=A05844 thread.</div><div><b=
r></div></div></div></blockquote><div>[Joe] I don&#39;t think so, but let&#=
39;s discuss on the 5844 thread.=C2=A0=C2=A0</div><div>=C2=A0</div><blockqu=
ote class=3D"gmail_quote" style=3D"margin:0px 0px 0px 0.8ex;border-left:1px=
 solid rgb(204,204,204);padding-left:1ex"><div dir=3D"ltr"><div dir=3D"ltr"=
><div></div><div>Regarding introduction of Zero-MSK flag in Crypto-Binding =
TLV - do you think it is unnecessary? So if one peer doesn&#39;t export a s=
pecific inner method MSK and ESMK and uses Zero-MSK and another peer expect=
s MSK or ESMK - then the=C2=A0Crypto-Binding TLV exchange will fail natural=
ly. Maybe it&#39;s worth saying exactly that if the inner method exports MS=
K or EMSK then each peer MUST use it and not Zero-MSK.</div></div></div></b=
lockquote><div>=C2=A0</div><div>[Joe]=C2=A0 It doesn&#39;t seem to me that =
the Zero-MSK flag is necessary,=C2=A0I&#39;d rather not add new signals if =
we do not need them now.=C2=A0 If a method generates an MSK then I think it=
 must be used.=C2=A0 =C2=A0We can add a sentence saying that to the above r=
evision.=C2=A0</div><div><br></div><div><font face=3D"monospace">=C2=A0<spa=
n style=3D"color:rgb(0,0,0);font-size:13.3333px">If the jth inner method do=
es not generate an EMSK or MSK, or no inner</span></font></div><pre style=
=3D"font-size:13.3333px;margin-top:0px;margin-bottom:0px;break-before:page;=
color:rgb(0,0,0)"> method has been run then IMSK[j] is set to zero (32 octe=
ts of 0x00s). </pre><pre style=3D"font-size:13.3333px;margin-top:0px;margin=
-bottom:0px;break-before:page;color:rgb(0,0,0)"> If a method generates an M=
SK or EMSK the zero IMSK MUST NOT be used.  </pre></div></div>

--00000000000079d05f05b29e8d81--


From nobody Mon Oct 26 20:23:53 2020
Return-Path: <joe@salowey.net>
X-Original-To: emu@ietfa.amsl.com
Delivered-To: emu@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id D19AA3A12D2 for <emu@ietfa.amsl.com>; Mon, 26 Oct 2020 20:23:52 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.898
X-Spam-Level: 
X-Spam-Status: No, score=-1.898 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, HTML_MESSAGE=0.001, SPF_HELO_NONE=0.001, SPF_PASS=-0.001, URIBL_BLOCKED=0.001] autolearn=unavailable autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (2048-bit key) header.d=salowey-net.20150623.gappssmtp.com
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 6QOW9hKxgWYP for <emu@ietfa.amsl.com>; Mon, 26 Oct 2020 20:23:50 -0700 (PDT)
Received: from mail-qt1-x82f.google.com (mail-qt1-x82f.google.com [IPv6:2607:f8b0:4864:20::82f]) (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 5EC0B3A12D1 for <emu@ietf.org>; Mon, 26 Oct 2020 20:23:50 -0700 (PDT)
Received: by mail-qt1-x82f.google.com with SMTP id m65so77715qte.11 for <emu@ietf.org>; Mon, 26 Oct 2020 20:23:50 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=salowey-net.20150623.gappssmtp.com; s=20150623; h=mime-version:references:in-reply-to:from:date:message-id:subject:to :cc; bh=s4r8DFs/zZA2Z1FDTACgxOg50fXlYvAKhW9aC4vN5/Y=; b=fuoDh3CveRF2UHlt91njVZOETlGHMHyyiQhJoLQSko/g48NqB24RlkNBHVw6wXZ6FT TjkHwtGopEQF2H2GIZOLRjB8l2R0V+xApRgv6SUAXYIjWivjiq2QdIRC0Sg4AGppABTb eLUtL4DWJPv4SPmnaZaZg0Otm/dA6wjSVRhKIhu+pn2rbMQb2Sm+yfgy/cDIGOduOXx4 3FAFoEXO/JeKx9JRmazIni+ONcBKWqt15mz38cMLcBPUs2KGZaHtdpYl0HIlpGlyFZ0u tqknoGPlOm4ee7D1B3r3O/xfEmJe9kZYsvU8sdXQu2EFgiuZz6Qdrvr6OKM4rq/+NZg8 Vvyw==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:mime-version:references:in-reply-to:from:date :message-id:subject:to:cc; bh=s4r8DFs/zZA2Z1FDTACgxOg50fXlYvAKhW9aC4vN5/Y=; b=i5HGUXJI9BWlrF4Rovp7gQIIWxO5c+SeA2k6YQ4XpEiDThJyBteU7pTUhedeAi5KSG DSPNJhv4lj3lA6FbU1EK9AuItqUsk/+Y9u5irIWCtmzWtaebb2oPjPpE+wTmuO2cSacr mmbrp2gaTaXrpywAvAOSpW8n8DkTyV/0/gor31fkAyC/RIdD/CkcZyJQaT/Vpb+dPxtb 1IiokFY9BpRhvN2dm80hcwQe9M+ddapfYtUMxnTd0imM/h5jLALsuwrwUxh3mmsDr6j7 rnr5hoCqYmb5eckN+eIo6disqUP7YfPcbpBW7DqK25sOyLdBnyK+Ebd96Eu+tkYNBvIe 7Ptw==
X-Gm-Message-State: AOAM531MOw66g4ClP2JSqKnItoKTPiQ7+ZHy2kCWctBBQXlOSg4HYrDY W6skb/zRs5H3iUNxYigXhtG/j1eLLYXdXyEd9aChxw==
X-Google-Smtp-Source: ABdhPJwwqiMsm3hgR6BjqFO17K7jJ4MBfmNnTn8mloG3LJZJdDz3h1zHBQN+krB+odienpXEeUDNeYTKle+QSTaUr70=
X-Received: by 2002:ac8:b4a:: with SMTP id m10mr260292qti.71.1603769029411; Mon, 26 Oct 2020 20:23:49 -0700 (PDT)
MIME-Version: 1.0
References: <CAOgPGoBsGEGwC+3Z=uNz5an4ywmiopmakJFDVh4ZW=DRH6uFJg@mail.gmail.com> <CABXxEz8yDvxB=g_ob1KZfLVFd2S4zRq=wvbUnc0SH1VJqf4Vaw@mail.gmail.com>
In-Reply-To: <CABXxEz8yDvxB=g_ob1KZfLVFd2S4zRq=wvbUnc0SH1VJqf4Vaw@mail.gmail.com>
From: Joseph Salowey <joe@salowey.net>
Date: Mon, 26 Oct 2020 20:23:38 -0700
Message-ID: <CAOgPGoDx5-20CPok2CvONQ1OKp6POUiBQSt6fUF_oy66b2qCWQ@mail.gmail.com>
To: Oleg Pekar <oleg.pekar.2017@gmail.com>
Cc: EMU WG <emu@ietf.org>, Jouni Malinen <j@w1.fi>,  Jorge Vergara <jovergar=40microsoft.com@dmarc.ietf.org>
Content-Type: multipart/alternative; boundary="0000000000004cd92a05b29e93dc"
Archived-At: <https://mailarchive.ietf.org/arch/msg/emu/FrDEEbjVzrw99IOBHFiRonGF5u8>
Subject: Re: [Emu] Proposed Resolution for Errata 5845
X-BeenThere: emu@ietf.org
X-Mailman-Version: 2.1.29
Precedence: list
List-Id: "EAP Methods Update \(EMU\)" <emu.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/emu>, <mailto:emu-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/emu/>
List-Post: <mailto:emu@ietf.org>
List-Help: <mailto:emu-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/emu>, <mailto:emu-request@ietf.org?subject=subscribe>
X-List-Received-Date: Tue, 27 Oct 2020 03:23:53 -0000

--0000000000004cd92a05b29e93dc
Content-Type: text/plain; charset="UTF-8"

On Mon, Oct 26, 2020 at 1:27 AM Oleg Pekar <oleg.pekar.2017@gmail.com>
wrote:

> >It should say:
> >
> >   EAP method messages are carried within EAP-Payload TLVs defined in
> >   Section 4.2.10.  Upon method completion, the server MUST send an
> >  Intermediate-Result TLV indicating the result.
>
> Jouni explained in errata 5767 that not all EAP methods are EAP
> authentication methods, to be exact. In the proposed fix for errata 5767
> you have already suggested that for Section 3.3.1 text:
>
> >Section 3.3.1
> >
> >It should say:
>
> >   EAP method messages are carried within EAP-Payload TLVs defined in
> >   Section 4.2.10.  Upon completion of each EAP authentication method in
> >   the tunnel, the server MUST send an Intermediate-Result TLV
> >   indicating the result.
>
>
[Joe] Yes, I think you are correct.


>
>
> On Sun, Oct 25, 2020 at 9:14 PM Joseph Salowey <joe@salowey.net> wrote:
>
>> Errata 5845: https://www.rfc-editor.org/errata/eid5845
>> Proposed Status: Verified
>> Revision:
>>
>> Section 3.3.1 says:
>>
>>    EAP method messages are carried within EAP-Payload TLVs defined in
>>    Section 4.2.10.  If more than one method is going to be executed in
>>    the tunnel, then upon method completion, the server MUST send an
>>    Intermediate-Result TLV indicating the result.
>>
>> It should say:
>>
>>    EAP method messages are carried within EAP-Payload TLVs defined in
>>    Section 4.2.10.  Upon method completion, the server MUST send an
>>    Intermediate-Result TLV indicating the result.
>>
>> Notes:
>>
>> Description of whether Intermediate-Result TLV is supposed to be used in
>> the case where only a single inner EAP authentication method is used.
>> Section 3.3.1 says "more than one method is going to be executed in the
>> tunnel, then upon method completion, the server MUST send an
>> Intermediate-Result TLV indicating the result", Section 3.3.3 says "The
>> Crypto-Binding TLV and Intermediate-Result TLV MUST be included to perform
>> cryptographic binding after each successful EAP method in a sequence of one
>> or more EAP methods", 4.2.13 says "It MUST be included with the
>> Intermediate-Result TLV to perform cryptographic binding after each
>> successful EAP method in a sequence of EAP methods", Annex C.3 shows an
>> example exchange with a single inner EAP authentication method with use of
>> Intermediate-Result TLV.
>>
>> It looks like the majority of the places discussion this topic implies
>> that there is going to be an Intermediate-Result TLV after each inner EAP
>> authentication method and the text in 3.3.1 is the only clear case of
>> conflicting (or well, at least misleading if one were to claim it does not
>> explicitly say MUST NOT for the one inner EAP authentication method case).
>> As such, I'd conclude the Intermediate-Result TLV is indeed going to be
>> exchanged after each EAP authentication method and the proposed text change
>> to 3.3.1 covers that.
>>
>

--0000000000004cd92a05b29e93dc
Content-Type: text/html; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable

<div dir=3D"ltr"><div dir=3D"ltr"><br></div><br><div class=3D"gmail_quote">=
<div dir=3D"ltr" class=3D"gmail_attr">On Mon, Oct 26, 2020 at 1:27 AM Oleg =
Pekar &lt;<a href=3D"mailto:oleg.pekar.2017@gmail.com">oleg.pekar.2017@gmai=
l.com</a>&gt; wrote:<br></div><blockquote class=3D"gmail_quote" style=3D"ma=
rgin:0px 0px 0px 0.8ex;border-left:1px solid rgb(204,204,204);padding-left:=
1ex"><div dir=3D"ltr">&gt;It should say:<br>&gt;<br>&gt;=C2=A0 =C2=A0EAP me=
thod messages are carried within EAP-Payload TLVs defined in<br>&gt;=C2=A0 =
=C2=A0Section 4.2.10.=C2=A0 Upon method completion, the server MUST send an=
<div>&gt;=C2=A0 Intermediate-Result TLV indicating the result.<br><div><br>=
</div></div><div>Jouni explained in errata 5767 that not all EAP methods ar=
e EAP authentication methods, to be exact. In the proposed fix for errata 5=
767 you have already suggested that for Section 3.3.1 text:</div><div><br><=
/div><div>&gt;Section 3.3.1</div><div>&gt;</div><div>&gt;It should say:<br>=
<br>&gt;=C2=A0 =C2=A0<span>EAP</span>=C2=A0method messages are carried with=
in=C2=A0<span>EAP</span>-Payload TLVs defined in<br>&gt;=C2=A0 =C2=A0Sectio=
n 4.2.10.=C2=A0 Upon completion of each=C2=A0<span>EAP</span>=C2=A0<span>au=
thentication</span>=C2=A0method in<br>&gt;=C2=A0 =C2=A0the tunnel, the serv=
er MUST send an Intermediate-Result TLV<br>&gt;=C2=A0 =C2=A0indicating the =
result.<br></div><div><br></div></div></blockquote><div><br></div><div>[Joe=
] Yes, I think you are correct.=C2=A0=C2=A0</div><div>=C2=A0</div><blockquo=
te class=3D"gmail_quote" style=3D"margin:0px 0px 0px 0.8ex;border-left:1px =
solid rgb(204,204,204);padding-left:1ex"><div dir=3D"ltr"><div></div><div><=
br></div></div><br><div class=3D"gmail_quote"><div dir=3D"ltr" class=3D"gma=
il_attr">On Sun, Oct 25, 2020 at 9:14 PM Joseph Salowey &lt;<a href=3D"mail=
to:joe@salowey.net" target=3D"_blank">joe@salowey.net</a>&gt; wrote:<br></d=
iv><blockquote class=3D"gmail_quote" style=3D"margin:0px 0px 0px 0.8ex;bord=
er-left:1px solid rgb(204,204,204);padding-left:1ex"><div dir=3D"ltr">Errat=
a 5845:=C2=A0<a href=3D"https://www.rfc-editor.org/errata/eid5845" target=
=3D"_blank">https://www.rfc-editor.org/errata/eid5845</a><div>Proposed Stat=
us: Verified</div><div>Revision:</div><br>Section 3.3.1 says:<br><br>=C2=A0=
 =C2=A0EAP method messages are carried within EAP-Payload TLVs defined in<b=
r>=C2=A0 =C2=A0Section 4.2.10.=C2=A0 If more than one method is going to be=
 executed in<br>=C2=A0 =C2=A0the tunnel, then upon method completion, the s=
erver MUST send an<br>=C2=A0 =C2=A0Intermediate-Result TLV indicating the r=
esult.<br><br>It should say:<br><br>=C2=A0 =C2=A0EAP method messages are ca=
rried within EAP-Payload TLVs defined in<br>=C2=A0 =C2=A0Section 4.2.10.=C2=
=A0 Upon method completion, the server MUST send an<br>=C2=A0 =C2=A0Interme=
diate-Result TLV indicating the result.<div><br></div>Notes:<br><br>Descrip=
tion of whether Intermediate-Result TLV is supposed to be used in the case =
where only a single inner EAP authentication method is used. Section 3.3.1 =
says &quot;more than one method is going to be executed in the tunnel, then=
 upon method completion, the server MUST send an Intermediate-Result TLV in=
dicating the result&quot;, Section 3.3.3 says &quot;The Crypto-Binding TLV =
and Intermediate-Result TLV MUST be included to perform cryptographic bindi=
ng after each successful EAP method in a sequence of one or more EAP method=
s&quot;, 4.2.13 says &quot;It MUST be included with the Intermediate-Result=
 TLV to perform cryptographic binding after each successful EAP method in a=
 sequence of EAP methods&quot;, Annex C.3 shows an example exchange with a =
single inner EAP authentication method with use of Intermediate-Result TLV.=
<br><br>It looks like the majority of the places discussion this topic impl=
ies that there is going to be an Intermediate-Result TLV after each inner E=
AP authentication method and the text in 3.3.1 is the only clear case of co=
nflicting (or well, at least misleading if one were to claim it does not ex=
plicitly say MUST NOT for the one inner EAP authentication method case). As=
 such, I&#39;d conclude the Intermediate-Result TLV is indeed going to be e=
xchanged after each EAP authentication method and the proposed text change =
to 3.3.1 covers that.</div>
</blockquote></div>
</blockquote></div></div>

--0000000000004cd92a05b29e93dc--


From nobody Mon Oct 26 20:39:32 2020
Return-Path: <joe@salowey.net>
X-Original-To: emu@ietfa.amsl.com
Delivered-To: emu@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 35C3F3A14D7 for <emu@ietfa.amsl.com>; Mon, 26 Oct 2020 20:39:24 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.898
X-Spam-Level: 
X-Spam-Status: No, score=-1.898 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, HTML_MESSAGE=0.001, SPF_HELO_NONE=0.001, SPF_PASS=-0.001, URIBL_BLOCKED=0.001] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (2048-bit key) header.d=salowey-net.20150623.gappssmtp.com
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 I8EohqeqIcWw for <emu@ietfa.amsl.com>; Mon, 26 Oct 2020 20:39:22 -0700 (PDT)
Received: from mail-qv1-xf29.google.com (mail-qv1-xf29.google.com [IPv6:2607:f8b0:4864:20::f29]) (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 14E7C3A14CA for <emu@ietf.org>; Mon, 26 Oct 2020 20:39:20 -0700 (PDT)
Received: by mail-qv1-xf29.google.com with SMTP id f5so73859qvx.6 for <emu@ietf.org>; Mon, 26 Oct 2020 20:39:19 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=salowey-net.20150623.gappssmtp.com; s=20150623; h=mime-version:references:in-reply-to:from:date:message-id:subject:to :cc; bh=tSkE81vLFBEsBtWoOiYLB/gOWM76BSlkIrKN7UPLxq0=; b=OZhdxNAqC7QvuLnfVF+LDpN54C2SfUQX6rGXtedWW+SXPMXpgSMR7teNQ8u1uq1v7a /ACl+M5D3BVuDbAJiV62CvB7p1DQB1OPvpMwG8WBZ+oeXyhd0+zo7IIQ8fY1AOsjJweb mXmhL9o9p6q8LkpZ37oEvfk5kR9tKUcYp57gbgmqaG2cgF0LoyYcJIRHmr9TVLdx/1Lv DLrWu49srzD3FZQzuJXZcIOnKx/COaA3Use2z50BmEE8E8RmvfdZs9sKBXyqD1TmXNFi ik+KSzMr4GU5UShYc4MaDO9fb7bHo9O48EfPeSGUnu+0vkuxdsxeL2w/4lX9MEn0nrD4 ZCLw==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:mime-version:references:in-reply-to:from:date :message-id:subject:to:cc; bh=tSkE81vLFBEsBtWoOiYLB/gOWM76BSlkIrKN7UPLxq0=; b=JoVnay1+OfysdEHaZKa38U2hr8BQe5vmbyQdoVskZe3P6sWsjBCQGaF8GoxgnEIRka osX3ERp+JtcCacIHUGsZg3OoyONbhkF3/Pem5ODTuIfQk+3Ts/CNhrh4mgVIRGWOb0Kj xAAyQEOExsAg2Mp4IQZBv8XclbxjeAdCDbL33YWK4hcMpaW07L3NC4gRvMWTH2drXPtL WxjcFvVdWw+iLwKBwrw+Moe55Z8dlSgiNCft86lG3LFKk/tj3ab9il/np/Dmzs84IXzv CXajKzdgWDQMP5QmvwdXHlh/Ug1dYxecw9XPnUdNKOytAiMm+E/ESjaZL6TQCzifID20 J/KA==
X-Gm-Message-State: AOAM530NZEV5iIcaPPju0QKc64CjoXKKb9nlvYT7pLZea3BCDKhxpgoP 9rf87B8O1P490Zj9OMTXSEWezqBzoAXhSneqJZ9tnuB6cf/Fa8kn
X-Google-Smtp-Source: ABdhPJzH1I5TSxwxj+pSbepdnm+78729hOc9bk/VEhIyN4QARGOa7zV9FDL78RsqX9Qn1PmMFz7qkOroc1zQK+2nN5Q=
X-Received: by 2002:a0c:f188:: with SMTP id m8mr551953qvl.37.1603769959091; Mon, 26 Oct 2020 20:39:19 -0700 (PDT)
MIME-Version: 1.0
References: <CAOgPGoDfmCJwnZJLqeyXD0+X_aeqXXkiZZOo2WYP4SC0D67HQw@mail.gmail.com> <CABXxEz8M=QLP=qrqdeyMvNt+nAd-o_RLmUDUmTOibxm-d4D26A@mail.gmail.com>
In-Reply-To: <CABXxEz8M=QLP=qrqdeyMvNt+nAd-o_RLmUDUmTOibxm-d4D26A@mail.gmail.com>
From: Joseph Salowey <joe@salowey.net>
Date: Mon, 26 Oct 2020 20:39:08 -0700
Message-ID: <CAOgPGoDAaSLqfQs+ZDBatzn2N43tOY-XERVL=v=Zgv9GE+byTQ@mail.gmail.com>
To: Oleg Pekar <oleg.pekar.2017@gmail.com>
Cc: EMU WG <emu@ietf.org>, Jouni Malinen <j@w1.fi>,  Jorge Vergara <jovergar=40microsoft.com@dmarc.ietf.org>
Content-Type: multipart/alternative; boundary="000000000000b6a5e505b29ecae7"
Archived-At: <https://mailarchive.ietf.org/arch/msg/emu/9MYpiLctpujwIj3KWXK-2zujP4Y>
Subject: Re: [Emu] Proposed Resolution to TEAP Errata 5844
X-BeenThere: emu@ietf.org
X-Mailman-Version: 2.1.29
Precedence: list
List-Id: "EAP Methods Update \(EMU\)" <emu.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/emu>, <mailto:emu-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/emu/>
List-Post: <mailto:emu@ietf.org>
List-Help: <mailto:emu-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/emu>, <mailto:emu-request@ietf.org?subject=subscribe>
X-List-Received-Date: Tue, 27 Oct 2020 03:39:31 -0000

--000000000000b6a5e505b29ecae7
Content-Type: text/plain; charset="UTF-8"

On Mon, Oct 26, 2020 at 1:27 AM Oleg Pekar <oleg.pekar.2017@gmail.com>
wrote:

> Few comments:
> 1) It seems that the server MUST send Crypto-Binding TLV after a single
> EAP authentication method, after each of EAP authentications methods in a
> sequence, after no inner method but not after
> Basic-Password-Authentication. Shouldn't we close this gap for the sake of
> simplicity and structure? (Only Zero-MSK Crypto-Binding TLV is possible in
> this case, the same as in no inner method case). Is
> Basic-Password-Authentication treated as a case of no inner method?
> Technically it is already correct but still may not be clear enough.
>
> This also affects section "4.2.13. Crypto-Binding TLV":
>
> The Crypto-Binding TLV MUST be exchanged and verified before the final
> Result TLV exchange, regardless of whether there is an inner EAP
> method authentication or not.
>
> Shouldn't we mention "inner EAP method or basic password authentication"?
>

[Joe] There are two cases where CryptoBinding is used, after completion of
an EAP authentication exchange and with the Result-TLV exchange.   Since
password based authentication does not generate a key there is no need for
crypto binding.  It is just treated as a TLV.


>
> 2) [Minor] It is written both "EAP methods **and** basic password
> authentication" and "EAP methods **or**basic password authentication" in
> different sections above. Shouldn't we use the same all the time?
>
> [Joe] It should be consistent. Re-worded slightly:

3. The Intermediate-Result TLVs carry success or failure indications of
each individual EAP authentication method or basic password authentication
in TEAP Phase 2.

And

The Intermediate-Result TLV provides support for acknowledged intermediate
Success and Failure messages for inner EAP authentication methods or basic
password authentication.


>
> On Sun, Oct 25, 2020 at 9:10 PM Joseph Salowey <joe@salowey.net> wrote:
>
>> Errata 5844: https://www.rfc-editor.org/errata/eid5844
>> Status: Verified
>> Revision:
>>
>> Section 3.3.2 says:
>>
>> Upon receiving the response, the server
>>    indicates the success or failure of the exchange using an
>>    Intermediate-Result TLV.
>>
>> It Should say:
>>
>> Upon receiving the response, the server MUST
>>    indicate the success or failure of the exchange using an
>>    Intermediate-Result TLV.
>>
>> Section 3.6 says:
>>
>> 3. The Intermediate-Result TLVs carry success or failure indications of
>> the individual EAP methods in TEAP Phase 2.
>>
>> It Should say:
>>
>> 3. The Intermediate-Result TLVs carry success or failure indications of
>> the individual EAP methods and basic password authentication in TEAP Phase
>> 2.
>>
>> Section 4.2.11 says:
>>
>> The Intermediate-Result TLV provides support for acknowledged
>> intermediate Success and Failure messages between multiple inner EAP
>> methods within EAP.
>>
>> It Should say:
>>
>> The Intermediate-Result TLV provides support for acknowledged
>> intermediate Success and Failure messages between multiple inner EAP
>> methods or basic password authentication within EAP.
>>
>> Section C.1 says:
>>
>>                             <- Crypto-Binding TLV (Request),
>>                                 Result TLV (Success),
>>                                 (Optional PAC TLV)
>>
>>        Crypto-Binding TLV(Response),
>>        Result TLV (Success),
>>        (PAC-Acknowledgement TLV) ->
>>
>> It should say:
>>
>>                             <- Intermediate-Result-TLV (Success),
>>                                 Crypto-Binding TLV (Request),
>>                                 Result TLV (Success),
>>                                 (Optional PAC TLV)
>>
>>        Intermediate-Result-TLV (Success),
>>        Crypto-Binding TLV(Response),
>>        Result TLV (Success),
>>        (PAC-Acknowledgement TLV) ->
>>
>> Section C.2 Says:
>>                 <- Result TLV (Failure)
>>
>>             Result TLV (Failure) ->
>>
>> It Should Say:
>>
>>                 <- Intermediate-Result-TLV (Failure),
>>                      Result TLV (Failure)
>>
>>             Intermediate-Result-TLV (Failure),
>>        Result TLV (Failure) ->
>>
>>
>> Notes:
>>
>> Section 3.3.2 implies that Intermediate-Result TLV is used after each
>> round of Basic-Password-Auth-Req/Resp TLVs. However, the example sequence
>> in C.1 does not show this. The proposed change in this errata adds the
>> Intermediate-Result TLV indication here. Similar change should be done in
>> C.2 (i.e., add Intermediate-Result TLV (Failure) to the messages that
>> include Result TLV) since the language in 3.3.2 describe the indication to
>> be used for both success and failure cases.
>>
>> In addition to this change in C.1, it would be good to clarify the
>> specification globally to avoid confusion about this case since almost all
>> discussion regarding Intermediate-Result TLV currently is in the context of
>> inner EAP authentication. 3.3.2 should have a MUST statement similar to
>> 3.3.1. 3.6 should cover success or failure indications of basic password
>> auth like it does EAP methods. 4.2.11 should note Intermediate-Result TLV
>> is used with both inner EAP and basic password auth.
>>
>

--000000000000b6a5e505b29ecae7
Content-Type: text/html; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable

<div dir=3D"ltr"><div dir=3D"ltr"><br></div><br><div class=3D"gmail_quote">=
<div dir=3D"ltr" class=3D"gmail_attr">On Mon, Oct 26, 2020 at 1:27 AM Oleg =
Pekar &lt;<a href=3D"mailto:oleg.pekar.2017@gmail.com">oleg.pekar.2017@gmai=
l.com</a>&gt; wrote:<br></div><blockquote class=3D"gmail_quote" style=3D"ma=
rgin:0px 0px 0px 0.8ex;border-left:1px solid rgb(204,204,204);padding-left:=
1ex"><div dir=3D"ltr"><div>Few comments:</div>1) It seems that the server M=
UST send Crypto-Binding TLV after a single EAP authentication method, after=
 each of EAP authentications methods in a sequence, after no inner method=
=C2=A0but not after Basic-Password-Authentication. Shouldn&#39;t we close t=
his gap for the sake of simplicity and structure? (Only Zero-MSK Crypto-Bin=
ding TLV is possible in this case, the same as in no inner method case). Is=
 Basic-Password-Authentication treated as a case of no inner method? Techni=
cally it is already correct but still may not be clear enough.=C2=A0<div><b=
r></div><div>This also affects section &quot;4.2.13. Crypto-Binding TLV&quo=
t;:=C2=A0</div><div><br></div>The Crypto-Binding TLV MUST be exchanged and =
verified before the final Result TLV exchange, regardless of whether there =
is an inner EAP<br>method authentication or not.<div><br></div><div>Shouldn=
&#39;t we mention &quot;inner EAP method or basic password authentication&q=
uot;?</div></div></blockquote><div><br></div><div>[Joe] There are two cases=
 where CryptoBinding is used, after completion of an EAP authentication exc=
hange and with the Result-TLV exchange.=C2=A0 =C2=A0Since password based au=
thentication does not generate a key there is no need for crypto binding.=
=C2=A0 It is just treated as a TLV.=C2=A0=C2=A0</div><div>=C2=A0</div><bloc=
kquote class=3D"gmail_quote" style=3D"margin:0px 0px 0px 0.8ex;border-left:=
1px solid rgb(204,204,204);padding-left:1ex"><div dir=3D"ltr"><div><div><br=
><div>2) [Minor] It is written both &quot;EAP methods **and** basic=C2=A0pa=
ssword authentication&quot; and &quot;EAP methods **or**basic=C2=A0password=
 authentication&quot; in different sections above. Shouldn&#39;t we use the=
 same all the time?</div><div><br></div></div></div></div></blockquote><div=
>[Joe] It should be consistent. Re-worded slightly:=C2=A0</div><div><br></d=
iv><div><font face=3D"monospace">3. The Intermediate-Result TLVs carry succ=
ess or failure indications of each individual EAP authentication method or =
basic=C2=A0password authentication in TEAP Phase 2.</font><br></div><div><f=
ont face=3D"monospace"><br></font></div><div><font face=3D"arial, sans-seri=
f">And</font></div><div><font face=3D"monospace"><br></font></div><div><fon=
t face=3D"monospace">The Intermediate-Result TLV provides support for ackno=
wledged intermediate Success and Failure messages for inner EAP authenticat=
ion methods or basic password authentication.<br></font></div><div>=C2=A0</=
div><blockquote class=3D"gmail_quote" style=3D"margin:0px 0px 0px 0.8ex;bor=
der-left:1px solid rgb(204,204,204);padding-left:1ex"><div dir=3D"ltr"><div=
><div><div></div></div></div></div><br><div class=3D"gmail_quote"><div dir=
=3D"ltr" class=3D"gmail_attr">On Sun, Oct 25, 2020 at 9:10 PM Joseph Salowe=
y &lt;<a href=3D"mailto:joe@salowey.net" target=3D"_blank">joe@salowey.net<=
/a>&gt; wrote:<br></div><blockquote class=3D"gmail_quote" style=3D"margin:0=
px 0px 0px 0.8ex;border-left:1px solid rgb(204,204,204);padding-left:1ex"><=
div dir=3D"ltr">Errata 5844:=C2=A0<a href=3D"https://www.rfc-editor.org/err=
ata/eid5844" target=3D"_blank">https://www.rfc-editor.org/errata/eid5844</a=
><div>Status: Verified</div><div>Revision:</div><div><br></div><div>Section=
 3.3.2 says:</div><div><br></div>Upon receiving the response, the server<br=
>=C2=A0 =C2=A0indicates the success or failure of the exchange using an<br>=
=C2=A0 =C2=A0Intermediate-Result TLV.<div><br></div><div>It Should say:</di=
v><div><br></div><div>Upon receiving the response, the server MUST<br>=C2=
=A0 =C2=A0indicate the success or failure of the exchange using an<br>=C2=
=A0 =C2=A0Intermediate-Result TLV.<br></div><div><br></div><div>Section 3.6=
 says:</div><div><br></div>3. The Intermediate-Result TLVs carry success or=
 failure indications of the individual EAP methods in TEAP Phase 2.<div><br=
></div><div>It Should say:</div><div><br></div><div>3. The Intermediate-Res=
ult TLVs carry success or failure indications of the individual EAP methods=
 and basic=C2=A0password authentication in TEAP Phase 2.<br></div><div><br>=
<div>Section 4.2.11 says:</div><div><br></div>The Intermediate-Result TLV p=
rovides support for acknowledged intermediate Success and Failure messages =
between multiple inner EAP methods within EAP.</div><div><br></div><div>It =
Should say:</div><div><br></div><div>The Intermediate-Result TLV provides s=
upport for acknowledged intermediate Success and Failure messages between m=
ultiple inner EAP methods or basic password authentication within EAP.<br><=
div><br></div><div>Section C.1 says:<br><br>=C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=
=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 &lt;- Cr=
ypto-Binding TLV (Request),<br>=C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =
=C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 Resul=
t TLV (Success),<br>=C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0=
 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 (Optional PAC TLV)=
<br><br>=C2=A0 =C2=A0 =C2=A0 =C2=A0Crypto-Binding TLV(Response),<br>=C2=A0 =
=C2=A0 =C2=A0 =C2=A0Result TLV (Success),<br>=C2=A0 =C2=A0 =C2=A0 =C2=A0(PA=
C-Acknowledgement TLV) -&gt;<br><br>It should say:<br><br>=C2=A0 =C2=A0 =C2=
=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =
=C2=A0 &lt;- Intermediate-Result-TLV (Success),<br>=C2=A0 =C2=A0 =C2=A0 =C2=
=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =
=C2=A0 =C2=A0 Crypto-Binding TLV (Request),<br>=C2=A0 =C2=A0 =C2=A0 =C2=A0 =
=C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=
=A0 =C2=A0 Result TLV (Success),<br>=C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=
=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 (=
Optional PAC TLV)<br><br>=C2=A0 =C2=A0 =C2=A0 =C2=A0Intermediate-Result-TLV=
 (Success),<br>=C2=A0 =C2=A0 =C2=A0 =C2=A0Crypto-Binding TLV(Response),<br>=
=C2=A0 =C2=A0 =C2=A0 =C2=A0Result TLV (Success),<br>=C2=A0 =C2=A0 =C2=A0 =
=C2=A0(PAC-Acknowledgement TLV) -&gt;<div><br></div><div>Section C.2 Says:<=
/div><div>=C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 &lt;- Res=
ult TLV (Failure)<pre style=3D"font-size:13.3333px;margin-top:0px;margin-bo=
ttom:0px;break-before:page;color:rgb(0,0,0)"></pre><pre style=3D"font-size:=
13.3333px;margin-top:0px;margin-bottom:0px;break-before:page;color:rgb(0,0,=
0)">     </pre>=C2=A0 =C2=A0 =C2=A0 =C2=A0Result TLV (Failure) -&gt;</div><=
div><br></div><div>It Should Say:</div><div><br></div><div>=C2=A0 =C2=A0 =
=C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 &lt;- Intermediate-Result-TLV (Fa=
ilure),<br>=C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =
=C2=A0 =C2=A0Result TLV (Failure)<pre style=3D"font-size:13.3333px;margin-t=
op:0px;margin-bottom:0px;break-before:page;color:rgb(0,0,0)"></pre><pre sty=
le=3D"font-size:13.3333px;margin-top:0px;margin-bottom:0px;break-before:pag=
e;color:rgb(0,0,0)">     </pre>=C2=A0 =C2=A0 =C2=A0 =C2=A0Intermediate-Resu=
lt-TLV (Failure),=C2=A0<br>=C2=A0 =C2=A0 =C2=A0 =C2=A0Result TLV (Failure) =
-&gt;<br><pre style=3D"font-size:13.3333px;margin-top:0px;margin-bottom:0px=
;break-before:page;color:rgb(0,0,0)"></pre><pre style=3D"font-size:13.3333p=
x;margin-top:0px;margin-bottom:0px;break-before:page;color:rgb(0,0,0)"><br>=
</pre>Notes: <br><br>Section 3.3.2 implies that Intermediate-Result TLV is =
used after each round of Basic-Password-Auth-Req/Resp TLVs. However, the ex=
ample sequence in C.1 does not show this. The proposed change in this errat=
a adds the Intermediate-Result TLV indication here. Similar change should b=
e done in C.2 (i.e., add Intermediate-Result TLV (Failure) to the messages =
that include Result TLV) since the language in 3.3.2 describe the indicatio=
n to be used for both success and failure cases.</div></div></div><br>In ad=
dition to this change in C.1, it would be good to clarify the specification=
 globally to avoid confusion about this case since almost all discussion re=
garding Intermediate-Result TLV currently is in the context of inner EAP au=
thentication. 3.3.2 should have a MUST statement similar to 3.3.1. 3.6 shou=
ld cover success or failure indications of basic password auth like it does=
 EAP methods. 4.2.11 should note Intermediate-Result TLV is used with both =
inner EAP and basic password auth.=C2=A0=C2=A0</div>
</blockquote></div>
</blockquote></div></div>

--000000000000b6a5e505b29ecae7--


From nobody Mon Oct 26 20:44:49 2020
Return-Path: <joe@salowey.net>
X-Original-To: emu@ietfa.amsl.com
Delivered-To: emu@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 3A8F63A14F2 for <emu@ietfa.amsl.com>; Mon, 26 Oct 2020 20:44:42 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.898
X-Spam-Level: 
X-Spam-Status: No, score=-1.898 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, HTML_MESSAGE=0.001, SPF_HELO_NONE=0.001, SPF_PASS=-0.001, URIBL_BLOCKED=0.001] autolearn=unavailable autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (2048-bit key) header.d=salowey-net.20150623.gappssmtp.com
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 0wfU07wUrM80 for <emu@ietfa.amsl.com>; Mon, 26 Oct 2020 20:44:40 -0700 (PDT)
Received: from mail-qk1-x72b.google.com (mail-qk1-x72b.google.com [IPv6:2607:f8b0:4864:20::72b]) (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 890F43A1477 for <emu@ietf.org>; Mon, 26 Oct 2020 20:44:32 -0700 (PDT)
Received: by mail-qk1-x72b.google.com with SMTP id k9so55530qki.6 for <emu@ietf.org>; Mon, 26 Oct 2020 20:44:32 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=salowey-net.20150623.gappssmtp.com; s=20150623; h=mime-version:references:in-reply-to:from:date:message-id:subject:to :cc; bh=4KJYAvyCSFCv5zU1LfnHlm62bb4ua6g/2btjGojO/IQ=; b=qTi39fgD4OamGU0JxA2yPcwmxlPbg1wu49h3i9LZ9zSATKeYq9d10MpFBIwkEFgUvu ku2N8f2nE0RV8Ml0iMma0tbkHMdg+hvBaXJVSm6DzHAD/bAAdm+VtiYVoGwbKFPF1UEm rybw6sBbO60EddQyV+LJ778pj2vw4ztQQfyGinc60hHCIYfkZLYWUGMIoYC1Rbs/PC3d 91OSSkZDuafBLdecp1FER9J3eMGMkNvXRrk8PPzl+7Z0oEaN3UPQP7qmSeaN4NMIF6OM KSPhT1EiMqI7n+jNxd9q/sVGhdjuGbKmHg/gBLFWD3MlqVGk1qSKI2fQUTlvACepyCFM pfWA==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:mime-version:references:in-reply-to:from:date :message-id:subject:to:cc; bh=4KJYAvyCSFCv5zU1LfnHlm62bb4ua6g/2btjGojO/IQ=; b=ZCARMJhVQ7ILbDghuRWDz0XvQgP2+flxcobUTNACnB1NHzAzvT/PAN5wYu7s4OEykR nJtYdqDBykVggw0bGT77Osjs0qgkCHlkhM0GOShDPEa3JfX9Zw47BsGC10NA1ujaaetC VoLGDyTZkzlNjJ5WDLyyaPOAfQqdMjE65FdSam8iEW07zeq3dQK2WFnOFrM4Ne/r3zBH e+gVMNdR7kmb/vi2T9CTeU9aoU2vG+iNvKDaN9sKinF64QVO2wDQGrWHpz2v7MNCzyer eL5rJSlAol0v3FOnhmGeoT4R0rQd0PIwvXxxRpwnK66uSrk3YAjBMHG9THGdhMTujGtM BQkg==
X-Gm-Message-State: AOAM533mzRtn2cOl6VIZB16pWUvr8HdLej/EkMzPMQTp8QTR3y0OK+MM O+NHqLggHaMo+6pnU+9XHuqHhL0f2OdBr2wO/pVvkQ==
X-Google-Smtp-Source: ABdhPJxGDir9+fuoyVIoGhI/FPuTOXQcTfqPo0SYmjRv1PgRNIIoQ/FbZGCpDmQ0S76yqxvW2+bpTFtRzmRT9PLwX9w=
X-Received: by 2002:a05:620a:215d:: with SMTP id m29mr349418qkm.138.1603770271589;  Mon, 26 Oct 2020 20:44:31 -0700 (PDT)
MIME-Version: 1.0
References: <CAOgPGoDfmCJwnZJLqeyXD0+X_aeqXXkiZZOo2WYP4SC0D67HQw@mail.gmail.com> <CABXxEz8M=QLP=qrqdeyMvNt+nAd-o_RLmUDUmTOibxm-d4D26A@mail.gmail.com> <CAOgPGoDAaSLqfQs+ZDBatzn2N43tOY-XERVL=v=Zgv9GE+byTQ@mail.gmail.com>
In-Reply-To: <CAOgPGoDAaSLqfQs+ZDBatzn2N43tOY-XERVL=v=Zgv9GE+byTQ@mail.gmail.com>
From: Joseph Salowey <joe@salowey.net>
Date: Mon, 26 Oct 2020 20:44:20 -0700
Message-ID: <CAOgPGoDTAO55aRqYKOE-uZq0X-DcSr6X0hor4VXHT-BhwmSXag@mail.gmail.com>
To: Oleg Pekar <oleg.pekar.2017@gmail.com>
Cc: EMU WG <emu@ietf.org>, Jouni Malinen <j@w1.fi>,  Jorge Vergara <jovergar=40microsoft.com@dmarc.ietf.org>
Content-Type: multipart/alternative; boundary="00000000000056f7c305b29edd84"
Archived-At: <https://mailarchive.ietf.org/arch/msg/emu/65i2T6G2pQ7tUalhtqtDvmQNI5w>
Subject: Re: [Emu] Proposed Resolution to TEAP Errata 5844
X-BeenThere: emu@ietf.org
X-Mailman-Version: 2.1.29
Precedence: list
List-Id: "EAP Methods Update \(EMU\)" <emu.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/emu>, <mailto:emu-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/emu/>
List-Post: <mailto:emu@ietf.org>
List-Help: <mailto:emu-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/emu>, <mailto:emu-request@ietf.org?subject=subscribe>
X-List-Received-Date: Tue, 27 Oct 2020 03:44:48 -0000

--00000000000056f7c305b29edd84
Content-Type: text/plain; charset="UTF-8"

On Mon, Oct 26, 2020 at 8:39 PM Joseph Salowey <joe@salowey.net> wrote:

>
>
> On Mon, Oct 26, 2020 at 1:27 AM Oleg Pekar <oleg.pekar.2017@gmail.com>
> wrote:
>
>> Few comments:
>> 1) It seems that the server MUST send Crypto-Binding TLV after a single
>> EAP authentication method, after each of EAP authentications methods in a
>> sequence, after no inner method but not after
>> Basic-Password-Authentication. Shouldn't we close this gap for the sake of
>> simplicity and structure? (Only Zero-MSK Crypto-Binding TLV is possible in
>> this case, the same as in no inner method case). Is
>> Basic-Password-Authentication treated as a case of no inner method?
>> Technically it is already correct but still may not be clear enough.
>>
>> This also affects section "4.2.13. Crypto-Binding TLV":
>>
>> The Crypto-Binding TLV MUST be exchanged and verified before the final
>> Result TLV exchange, regardless of whether there is an inner EAP
>> method authentication or not.
>>
>> Shouldn't we mention "inner EAP method or basic password authentication"?
>>
>
> [Joe] There are two cases where CryptoBinding is used, after completion of
> an EAP authentication exchange and with the Result-TLV exchange.   Since
> password based authentication does not generate a key there is no need for
> crypto binding.  It is just treated as a TLV.
>
>

[Joe] Section 4.2.11 contradicts this - "An Intermediate-Result TLV
indicating success MUST be accompanied by a Crypto-Binding TLV."  I think
we need to use the 0 MSK with the basic password authentication.


>
>> 2) [Minor] It is written both "EAP methods **and** basic password
>> authentication" and "EAP methods **or**basic password authentication" in
>> different sections above. Shouldn't we use the same all the time?
>>
>> [Joe] It should be consistent. Re-worded slightly:
>
> 3. The Intermediate-Result TLVs carry success or failure indications of
> each individual EAP authentication method or basic password authentication
> in TEAP Phase 2.
>
> And
>
> The Intermediate-Result TLV provides support for acknowledged intermediate
> Success and Failure messages for inner EAP authentication methods or basic
> password authentication.
>
>
>>
>> On Sun, Oct 25, 2020 at 9:10 PM Joseph Salowey <joe@salowey.net> wrote:
>>
>>> Errata 5844: https://www.rfc-editor.org/errata/eid5844
>>> Status: Verified
>>> Revision:
>>>
>>> Section 3.3.2 says:
>>>
>>> Upon receiving the response, the server
>>>    indicates the success or failure of the exchange using an
>>>    Intermediate-Result TLV.
>>>
>>> It Should say:
>>>
>>> Upon receiving the response, the server MUST
>>>    indicate the success or failure of the exchange using an
>>>    Intermediate-Result TLV.
>>>
>>> Section 3.6 says:
>>>
>>> 3. The Intermediate-Result TLVs carry success or failure indications of
>>> the individual EAP methods in TEAP Phase 2.
>>>
>>> It Should say:
>>>
>>> 3. The Intermediate-Result TLVs carry success or failure indications of
>>> the individual EAP methods and basic password authentication in TEAP Phase
>>> 2.
>>>
>>> Section 4.2.11 says:
>>>
>>> The Intermediate-Result TLV provides support for acknowledged
>>> intermediate Success and Failure messages between multiple inner EAP
>>> methods within EAP.
>>>
>>> It Should say:
>>>
>>> The Intermediate-Result TLV provides support for acknowledged
>>> intermediate Success and Failure messages between multiple inner EAP
>>> methods or basic password authentication within EAP.
>>>
>>> Section C.1 says:
>>>
>>>                             <- Crypto-Binding TLV (Request),
>>>                                 Result TLV (Success),
>>>                                 (Optional PAC TLV)
>>>
>>>        Crypto-Binding TLV(Response),
>>>        Result TLV (Success),
>>>        (PAC-Acknowledgement TLV) ->
>>>
>>> It should say:
>>>
>>>                             <- Intermediate-Result-TLV (Success),
>>>                                 Crypto-Binding TLV (Request),
>>>                                 Result TLV (Success),
>>>                                 (Optional PAC TLV)
>>>
>>>        Intermediate-Result-TLV (Success),
>>>        Crypto-Binding TLV(Response),
>>>        Result TLV (Success),
>>>        (PAC-Acknowledgement TLV) ->
>>>
>>> Section C.2 Says:
>>>                 <- Result TLV (Failure)
>>>
>>>             Result TLV (Failure) ->
>>>
>>> It Should Say:
>>>
>>>                 <- Intermediate-Result-TLV (Failure),
>>>                      Result TLV (Failure)
>>>
>>>             Intermediate-Result-TLV (Failure),
>>>        Result TLV (Failure) ->
>>>
>>>
>>> Notes:
>>>
>>> Section 3.3.2 implies that Intermediate-Result TLV is used after each
>>> round of Basic-Password-Auth-Req/Resp TLVs. However, the example sequence
>>> in C.1 does not show this. The proposed change in this errata adds the
>>> Intermediate-Result TLV indication here. Similar change should be done in
>>> C.2 (i.e., add Intermediate-Result TLV (Failure) to the messages that
>>> include Result TLV) since the language in 3.3.2 describe the indication to
>>> be used for both success and failure cases.
>>>
>>> In addition to this change in C.1, it would be good to clarify the
>>> specification globally to avoid confusion about this case since almost all
>>> discussion regarding Intermediate-Result TLV currently is in the context of
>>> inner EAP authentication. 3.3.2 should have a MUST statement similar to
>>> 3.3.1. 3.6 should cover success or failure indications of basic password
>>> auth like it does EAP methods. 4.2.11 should note Intermediate-Result TLV
>>> is used with both inner EAP and basic password auth.
>>>
>>

--00000000000056f7c305b29edd84
Content-Type: text/html; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable

<div dir=3D"ltr"><div dir=3D"ltr"><br></div><br><div class=3D"gmail_quote">=
<div dir=3D"ltr" class=3D"gmail_attr">On Mon, Oct 26, 2020 at 8:39 PM Josep=
h Salowey &lt;<a href=3D"mailto:joe@salowey.net">joe@salowey.net</a>&gt; wr=
ote:<br></div><blockquote class=3D"gmail_quote" style=3D"margin:0px 0px 0px=
 0.8ex;border-left:1px solid rgb(204,204,204);padding-left:1ex"><div dir=3D=
"ltr"><div dir=3D"ltr"><br></div><br><div class=3D"gmail_quote"><div dir=3D=
"ltr" class=3D"gmail_attr">On Mon, Oct 26, 2020 at 1:27 AM Oleg Pekar &lt;<=
a href=3D"mailto:oleg.pekar.2017@gmail.com" target=3D"_blank">oleg.pekar.20=
17@gmail.com</a>&gt; wrote:<br></div><blockquote class=3D"gmail_quote" styl=
e=3D"margin:0px 0px 0px 0.8ex;border-left:1px solid rgb(204,204,204);paddin=
g-left:1ex"><div dir=3D"ltr"><div>Few comments:</div>1) It seems that the s=
erver MUST send Crypto-Binding TLV after a single EAP authentication method=
, after each of EAP authentications methods in a sequence, after no inner m=
ethod=C2=A0but not after Basic-Password-Authentication. Shouldn&#39;t we cl=
ose this gap for the sake of simplicity and structure? (Only Zero-MSK Crypt=
o-Binding TLV is possible in this case, the same as in no inner method case=
). Is Basic-Password-Authentication treated as a case of no inner method? T=
echnically it is already correct but still may not be clear enough.=C2=A0<d=
iv><br></div><div>This also affects section &quot;4.2.13. Crypto-Binding TL=
V&quot;:=C2=A0</div><div><br></div>The Crypto-Binding TLV MUST be exchanged=
 and verified before the final Result TLV exchange, regardless of whether t=
here is an inner EAP<br>method authentication or not.<div><br></div><div>Sh=
ouldn&#39;t we mention &quot;inner EAP method or basic password authenticat=
ion&quot;?</div></div></blockquote><div><br></div><div>[Joe] There are two =
cases where CryptoBinding is used, after completion of an EAP authenticatio=
n exchange and with the Result-TLV exchange.=C2=A0 =C2=A0Since password bas=
ed authentication does not generate a key there is no need for crypto bindi=
ng.=C2=A0 It is just treated as a TLV.=C2=A0=C2=A0</div><div>=C2=A0</div></=
div></div></blockquote><div><br></div><div>[Joe] Section 4.2.11 contradicts=
 this - &quot;<span style=3D"color:rgb(0,0,0);font-size:13.3333px">An Inter=
mediate-Result TLV indicating success=C2=A0</span><span style=3D"color:rgb(=
0,0,0);font-size:13.3333px">MUST be accompanied by a Crypto-Binding TLV.&qu=
ot;=C2=A0 I think we need to use the 0 MSK with the basic password authenti=
cation.=C2=A0=C2=A0</span></div><div>=C2=A0</div><blockquote class=3D"gmail=
_quote" style=3D"margin:0px 0px 0px 0.8ex;border-left:1px solid rgb(204,204=
,204);padding-left:1ex"><div dir=3D"ltr"><div class=3D"gmail_quote"><blockq=
uote class=3D"gmail_quote" style=3D"margin:0px 0px 0px 0.8ex;border-left:1p=
x solid rgb(204,204,204);padding-left:1ex"><div dir=3D"ltr"><div><div><br><=
div>2) [Minor] It is written both &quot;EAP methods **and** basic=C2=A0pass=
word authentication&quot; and &quot;EAP methods **or**basic=C2=A0password a=
uthentication&quot; in different sections above. Shouldn&#39;t we use the s=
ame all the time?</div><div><br></div></div></div></div></blockquote><div>[=
Joe] It should be consistent. Re-worded slightly:=C2=A0</div><div><br></div=
><div><font face=3D"monospace">3. The Intermediate-Result TLVs carry succes=
s or failure indications of each individual EAP authentication method or ba=
sic=C2=A0password authentication in TEAP Phase 2.</font><br></div><div><fon=
t face=3D"monospace"><br></font></div><div><font face=3D"arial, sans-serif"=
>And</font></div><div><font face=3D"monospace"><br></font></div><div><font =
face=3D"monospace">The Intermediate-Result TLV provides support for acknowl=
edged intermediate Success and Failure messages for inner EAP authenticatio=
n methods or basic password authentication.<br></font></div><div>=C2=A0</di=
v><blockquote class=3D"gmail_quote" style=3D"margin:0px 0px 0px 0.8ex;borde=
r-left:1px solid rgb(204,204,204);padding-left:1ex"><div dir=3D"ltr"><div><=
div><div></div></div></div></div><br><div class=3D"gmail_quote"><div dir=3D=
"ltr" class=3D"gmail_attr">On Sun, Oct 25, 2020 at 9:10 PM Joseph Salowey &=
lt;<a href=3D"mailto:joe@salowey.net" target=3D"_blank">joe@salowey.net</a>=
&gt; wrote:<br></div><blockquote class=3D"gmail_quote" style=3D"margin:0px =
0px 0px 0.8ex;border-left:1px solid rgb(204,204,204);padding-left:1ex"><div=
 dir=3D"ltr">Errata 5844:=C2=A0<a href=3D"https://www.rfc-editor.org/errata=
/eid5844" target=3D"_blank">https://www.rfc-editor.org/errata/eid5844</a><d=
iv>Status: Verified</div><div>Revision:</div><div><br></div><div>Section 3.=
3.2 says:</div><div><br></div>Upon receiving the response, the server<br>=
=C2=A0 =C2=A0indicates the success or failure of the exchange using an<br>=
=C2=A0 =C2=A0Intermediate-Result TLV.<div><br></div><div>It Should say:</di=
v><div><br></div><div>Upon receiving the response, the server MUST<br>=C2=
=A0 =C2=A0indicate the success or failure of the exchange using an<br>=C2=
=A0 =C2=A0Intermediate-Result TLV.<br></div><div><br></div><div>Section 3.6=
 says:</div><div><br></div>3. The Intermediate-Result TLVs carry success or=
 failure indications of the individual EAP methods in TEAP Phase 2.<div><br=
></div><div>It Should say:</div><div><br></div><div>3. The Intermediate-Res=
ult TLVs carry success or failure indications of the individual EAP methods=
 and basic=C2=A0password authentication in TEAP Phase 2.<br></div><div><br>=
<div>Section 4.2.11 says:</div><div><br></div>The Intermediate-Result TLV p=
rovides support for acknowledged intermediate Success and Failure messages =
between multiple inner EAP methods within EAP.</div><div><br></div><div>It =
Should say:</div><div><br></div><div>The Intermediate-Result TLV provides s=
upport for acknowledged intermediate Success and Failure messages between m=
ultiple inner EAP methods or basic password authentication within EAP.<br><=
div><br></div><div>Section C.1 says:<br><br>=C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=
=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 &lt;- Cr=
ypto-Binding TLV (Request),<br>=C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =
=C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 Resul=
t TLV (Success),<br>=C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0=
 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 (Optional PAC TLV)=
<br><br>=C2=A0 =C2=A0 =C2=A0 =C2=A0Crypto-Binding TLV(Response),<br>=C2=A0 =
=C2=A0 =C2=A0 =C2=A0Result TLV (Success),<br>=C2=A0 =C2=A0 =C2=A0 =C2=A0(PA=
C-Acknowledgement TLV) -&gt;<br><br>It should say:<br><br>=C2=A0 =C2=A0 =C2=
=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =
=C2=A0 &lt;- Intermediate-Result-TLV (Success),<br>=C2=A0 =C2=A0 =C2=A0 =C2=
=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =
=C2=A0 =C2=A0 Crypto-Binding TLV (Request),<br>=C2=A0 =C2=A0 =C2=A0 =C2=A0 =
=C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=
=A0 =C2=A0 Result TLV (Success),<br>=C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=
=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 (=
Optional PAC TLV)<br><br>=C2=A0 =C2=A0 =C2=A0 =C2=A0Intermediate-Result-TLV=
 (Success),<br>=C2=A0 =C2=A0 =C2=A0 =C2=A0Crypto-Binding TLV(Response),<br>=
=C2=A0 =C2=A0 =C2=A0 =C2=A0Result TLV (Success),<br>=C2=A0 =C2=A0 =C2=A0 =
=C2=A0(PAC-Acknowledgement TLV) -&gt;<div><br></div><div>Section C.2 Says:<=
/div><div>=C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 &lt;- Res=
ult TLV (Failure)<pre style=3D"font-size:13.3333px;margin-top:0px;margin-bo=
ttom:0px;break-before:page;color:rgb(0,0,0)"></pre><pre style=3D"font-size:=
13.3333px;margin-top:0px;margin-bottom:0px;break-before:page;color:rgb(0,0,=
0)">     </pre>=C2=A0 =C2=A0 =C2=A0 =C2=A0Result TLV (Failure) -&gt;</div><=
div><br></div><div>It Should Say:</div><div><br></div><div>=C2=A0 =C2=A0 =
=C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 &lt;- Intermediate-Result-TLV (Fa=
ilure),<br>=C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =
=C2=A0 =C2=A0Result TLV (Failure)<pre style=3D"font-size:13.3333px;margin-t=
op:0px;margin-bottom:0px;break-before:page;color:rgb(0,0,0)"></pre><pre sty=
le=3D"font-size:13.3333px;margin-top:0px;margin-bottom:0px;break-before:pag=
e;color:rgb(0,0,0)">     </pre>=C2=A0 =C2=A0 =C2=A0 =C2=A0Intermediate-Resu=
lt-TLV (Failure),=C2=A0<br>=C2=A0 =C2=A0 =C2=A0 =C2=A0Result TLV (Failure) =
-&gt;<br><pre style=3D"font-size:13.3333px;margin-top:0px;margin-bottom:0px=
;break-before:page;color:rgb(0,0,0)"></pre><pre style=3D"font-size:13.3333p=
x;margin-top:0px;margin-bottom:0px;break-before:page;color:rgb(0,0,0)"><br>=
</pre>Notes: <br><br>Section 3.3.2 implies that Intermediate-Result TLV is =
used after each round of Basic-Password-Auth-Req/Resp TLVs. However, the ex=
ample sequence in C.1 does not show this. The proposed change in this errat=
a adds the Intermediate-Result TLV indication here. Similar change should b=
e done in C.2 (i.e., add Intermediate-Result TLV (Failure) to the messages =
that include Result TLV) since the language in 3.3.2 describe the indicatio=
n to be used for both success and failure cases.</div></div></div><br>In ad=
dition to this change in C.1, it would be good to clarify the specification=
 globally to avoid confusion about this case since almost all discussion re=
garding Intermediate-Result TLV currently is in the context of inner EAP au=
thentication. 3.3.2 should have a MUST statement similar to 3.3.1. 3.6 shou=
ld cover success or failure indications of basic password auth like it does=
 EAP methods. 4.2.11 should note Intermediate-Result TLV is used with both =
inner EAP and basic password auth.=C2=A0=C2=A0</div>
</blockquote></div>
</blockquote></div></div>
</blockquote></div></div>

--00000000000056f7c305b29edd84--


From nobody Mon Oct 26 20:51:27 2020
Return-Path: <joe@salowey.net>
X-Original-To: emu@ietfa.amsl.com
Delivered-To: emu@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id E2BAE3A14A5 for <emu@ietfa.amsl.com>; Mon, 26 Oct 2020 20:51:25 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.798
X-Spam-Level: 
X-Spam-Status: No, score=-1.798 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, HTML_MESSAGE=0.001, HTTPS_HTTP_MISMATCH=0.1, SPF_HELO_NONE=0.001, SPF_PASS=-0.001, URIBL_BLOCKED=0.001] autolearn=no autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (2048-bit key) header.d=salowey-net.20150623.gappssmtp.com
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 7bwxdlzrfMAb for <emu@ietfa.amsl.com>; Mon, 26 Oct 2020 20:51:23 -0700 (PDT)
Received: from mail-qv1-xf33.google.com (mail-qv1-xf33.google.com [IPv6:2607:f8b0:4864:20::f33]) (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 AAEF23A149E for <emu@ietf.org>; Mon, 26 Oct 2020 20:51:23 -0700 (PDT)
Received: by mail-qv1-xf33.google.com with SMTP id s1so70712qvm.13 for <emu@ietf.org>; Mon, 26 Oct 2020 20:51:23 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=salowey-net.20150623.gappssmtp.com; s=20150623; h=mime-version:references:in-reply-to:from:date:message-id:subject:to :cc; bh=kS76lhzTzMyrwTnMFMsdmfPvF6YPt4Hj36KKOJfyudc=; b=0uLY+YEPNinaAc5ximzmlJbyri45mJMotagQPl0PtyaNiHN/KexCLx/xhig/yPW8EG jZnVlDJmZC7JylH4c4/etZ6UGZirf2wQ39v8OHer3UzznH0YBqLn42pF2FHJfZ3cXA5R jlsj+pHmCjNj5/WxwdQqaJbGBz6TtQEWKo3ZZ1da/yqfB4B6Q0Bux/Yu/jHrZYYi63Ce 4qOgoYjZWDvmNGvI4PcwCRNwA7b8+UmHQnHV84IUpn1euLYcaHRTQa2ZSqeV82cd5Bt/ e1C/OzDOvsi/JboQKzgOmtVPtcDdfZSi+bZ1hQQFJAcwplhQbAu8CHnTsVbetnb5LKgG MQpg==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:mime-version:references:in-reply-to:from:date :message-id:subject:to:cc; bh=kS76lhzTzMyrwTnMFMsdmfPvF6YPt4Hj36KKOJfyudc=; b=oGqtFTWBUoU73Oe8wu9W5Ml5zNAxuRCfB3hqnZqZbKT9pPKK3O/1RNrvsG60CWRIP7 FZ/ygzRfLyHCvH97Oc7Lc3lpF1PVLQDX9zcSzTExmu4yfmAq5j45/C23EWdjyxYd5PdU hjKfdHHJaC2ee+3/APAXfQuCxFKKPoZWd9J885Mh2a7tgv4/rFxQXn4CkqMohhUVh0Rb kDKLYdf7AhyyODTMV2k2pinlTSc9jpJxcZvRm6fgkZ2g8gL0St8PAINv+dw0FKtbmVh8 2EkWAIdBuBqWY3BLlPjQpeCJ6Znyn1hgCylmAKmKywNlw4lp0skVyJoghL6rY7noyqhL cP6w==
X-Gm-Message-State: AOAM533E9YACYnrSx7ZkcmOWZHx4gyp2UuUaypazjF8hKZfHYs1qWPSD XcEuUiACChssgH7ekpTeBVArP0vsQpv7/v26B9Y4Aw==
X-Google-Smtp-Source: ABdhPJxJn3Lyz3d051STHcws2eUIyHLjb8X6Y2YnpNg+x3b/HF5wuTikRXeA9JA5PnSqLLoEW7KthesQZfZCHxUhwt8=
X-Received: by 2002:a0c:f188:: with SMTP id m8mr581650qvl.37.1603770682761; Mon, 26 Oct 2020 20:51:22 -0700 (PDT)
MIME-Version: 1.0
References: <CAOgPGoCg2wRKFVKz2kqkomt7mkp1W98jSh6xLT8z1_uWBMXdmA@mail.gmail.com> <CH2PR21MB138172CE5A552084A62E3AA9D1190@CH2PR21MB1381.namprd21.prod.outlook.com>
In-Reply-To: <CH2PR21MB138172CE5A552084A62E3AA9D1190@CH2PR21MB1381.namprd21.prod.outlook.com>
From: Joseph Salowey <joe@salowey.net>
Date: Mon, 26 Oct 2020 20:51:11 -0700
Message-ID: <CAOgPGoBrNM8Kxuoic7wXmkWjavk_rsewDj8paS4CTR97+e3V_g@mail.gmail.com>
To: Jorge Vergara <jovergar@microsoft.com>
Cc: EMU WG <emu@ietf.org>, Oleg Pekar <oleg.pekar.2017@gmail.com>, Jouni Malinen <j@w1.fi>
Content-Type: multipart/alternative; boundary="000000000000d8ef1a05b29ef51f"
Archived-At: <https://mailarchive.ietf.org/arch/msg/emu/WsBd-7gIkfFNHP5avTVgc0c10jQ>
Subject: Re: [Emu] Proposed Resolution to TEAP Errata 5770
X-BeenThere: emu@ietf.org
X-Mailman-Version: 2.1.29
Precedence: list
List-Id: "EAP Methods Update \(EMU\)" <emu.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/emu>, <mailto:emu-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/emu/>
List-Post: <mailto:emu@ietf.org>
List-Help: <mailto:emu-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/emu>, <mailto:emu-request@ietf.org?subject=subscribe>
X-List-Received-Date: Tue, 27 Oct 2020 03:51:26 -0000

--000000000000d8ef1a05b29ef51f
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable

On Mon, Oct 26, 2020 at 12:51 PM Jorge Vergara <jovergar@microsoft.com>
wrote:

> This is a detailed one so I=E2=80=99ve tried to go over it carefully. Mos=
t of it
> looks good but I=E2=80=99m unsure about this part:
>
>
>
> > If an inner method fails or MAC verification
>
> fails then S-IMCK is not used in further calculation.
>
>
>
> It is a valid scenario that multiple authentication methods run and some
> fail, but the overall TEAP authentication succeeds. For example, if two
> inner EAP Authentication methods run and the first fails but the seconds
> succeeds, the calculation needs to be valid. Based on the old text, that
> authentication method is omitted from calculations. This is what current
> implementations do.
>
>
>
> My editorial comment based on some other errata would be to that text
> needs to specify =E2=80=9Cauthentication=E2=80=9D methods (per Jouni=E2=
=80=99s other errata) since
> the Identity method doesn=E2=80=99t factor in here. I think it would also=
 be
> beneficial to be specific about the behavior of basic username and passwo=
rd
> authentication here. Oleg made some comments to this effect on another
> email. Our implementation doesn=E2=80=99t support basic username and pass=
word
> authentication so I don=E2=80=99t have any prior experience here.
>
>
[Joe] Yes I think it is fine to say EAP authentication method.   I
have been convinced that the spec requires crypto-binding with the basic
password authentication.   I'll need to add this in.


>
>
> Jorge Vergara
>
>
>
> *From:* Joseph Salowey <joe@salowey.net>
> *Sent:* Saturday, October 24, 2020 5:18 PM
> *To:* EMU WG <emu@ietf.org>
> *Cc:* Oleg Pekar <oleg.pekar.2017@gmail.com>; Jouni Malinen <j@w1.fi>;
> Jorge Vergara <jovergar@microsoft.com>
> *Subject:* Proposed Resolution to TEAP Errata 5770
>
>
>
> Errata 5770: https://www.rfc-editor.org/errata/eid5770
> <https://nam06.safelinks.protection.outlook.com/?url=3Dhttps%3A%2F%2Fwww.=
rfc-editor.org%2Ferrata%2Feid5770&data=3D04%7C01%7Cjovergar%40microsoft.com=
%7C728ceb6af6694e40e08e08d8787b669d%7C72f988bf86f141af91ab2d7cd011db47%7C1%=
7C0%7C637391818689781723%7CUnknown%7CTWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIj=
oiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D%7C1000&sdata=3DRuRrXZ5c70r43Rmyl4s=
%2BVUKAA22nGtoenLElbCeUkmE%3D&reserved=3D0>
>
> Proposed Status: Verified
>
> Revision:
>
>
>
> Section 5.2 Says:
>
>
>
> On the sender of the Crypto-Binding TLV side:
>
>      If the EMSK is not available, then the sender computes the Compound
>      MAC using the MSK of the inner method.
>
>      If the EMSK is available and the sender's policy accepts MSK-based
>      MAC, then the sender computes two Compound MAC values.  The first
>      is computed with the EMSK.  The second one is computed using the
>      MSK.  Both MACs are then sent to the other side.
>
>      If the EMSK is available but the sender's policy does not allow
>      downgrading to MSK-generated MAC, then the sender SHOULD only send
>      EMSK-based MAC.
>
>    On the receiver of the Crypto-Binding TLV side:
>
>      If the EMSK is not available and an MSK-based Compound MAC was
>      sent, then the receiver validates the Compound MAC and sends back
>      an MSK-based Compound MAC response.
>
>      If the EMSK is not available and no MSK-based Compound MAC was
>      sent, then the receiver handles like an invalid Crypto-Binding TLV
>      with a fatal error.
>
>      If the EMSK is available and an EMSK-based Compound MAC was sent,
>      then the receiver validates it and creates a response Compound MAC
>      using the EMSK.
>
>      If the EMSK is available but no EMSK-based Compound MAC was sent
>      and its policy accepts MSK-based MAC, then the receiver validates
>      it using the MSK and, if successful, generates and returns an MSK-
>      based Compound MAC.
>
>      If the EMSK is available but no EMSK Compound MAC was sent and its
>      policy does not accept MSK-based MAC, then the receiver handles
>      like an invalid Crypto-Binding TLV with a fatal error.
>
>
>
> If the ith inner method does not generate an EMSK or MSK, then IMSKi
> is set to zero (e.g., MSKi =3D 32 octets of 0x00s).  If an inner method
> fails, then it is not included in this calculation.
>
>
>
> It Should Say:
>
>
>
> On the sender of the Crypto-Binding TLV side:
>
>      If the EMSK is not available, then the sender computes the Compound
>      MAC using the CMK generated from MSK (CMK-MSK) of the inner method.
>
>      If the EMSK is available and the sender's policy accepts MSK-based
>      MAC, then the sender computes two Compound MAC values.  The first
>      is computed with the CMK generated from the EMSK (CMK-EMSK).  The
>
>      second one is computed using the CMK-MSK.  Both MACs are
>
>      then sent to the other side.  This also means the sender must genera=
te
>
>      both EMSK and MSK based S-IMCKs.
>
>      If the EMSK is available but the sender's policy does not allow
>      downgrading to CMK-MSK MAC, then the sender SHOULD only send
>      a MAC computed from the CMK-EMSK.
>
>    On the receiver of the Crypto-Binding TLV side:
>
>      If the EMSK is not available and an CMK-MSK Compound MAC was
>      sent, then the receiver validates the Compound MAC and sends back
>      an CMK-MSK Compound MAC response.
>
>      If the EMSK is not available and no CMK-MSK Compound MAC was
>      sent, then the receiver handles like an invalid Crypto-Binding TLV
>      with a fatal error.
>
>      If the EMSK is available and a CMK-EMSK Compound MAC was sent,
>      then the receiver validates it and creates a response Compound MAC
>      using the CMK-EMSK.
>
>      If the EMSK is available but no CMK-EMSK Compound MAC was sent
>      and its policy accepts CMK-MSK MAC, then the receiver validates
>      it using the CMK-MSK and, if successful, generates and returns an MS=
K-
>      based Compound MAC.
>
>      If the EMSK is available but no CMK-EMSK Compound MAC was sent and i=
ts
>      policy does not accept CMK-MSK MAC, then the receiver handles
>      like an invalid Crypto-Binding TLV with a fatal error.
>
>
>
> The IMSK used is either the EMSK-based IMSK or the MSK based IMSK dependi=
ng
> upon the rules outlined above. If the ith inner method does not generate
> an EMSK
> or MSK, then IMSKi is set to zero (e.g., MSKi =3D 32 octets of 0x00s).   =
 It
> is possible
>
> that two S-IMCKs for a step may be generated based on the rules above.  I=
n
> this
>
> case the S-IMCK for further calculations is chosen as follows.  If the MA=
C
> based
>
> on the CMK-EMSK is verified then the S-IMCK generated based on the EMSK i=
s
>
> used.  Else, if the MAC based on the CMK-MSK is verified then the S-IMCK
>
> generated based on the MSK is used.  If an inner method fails or MAC
> verification
>
> fails then S-IMCK is not used in further calculation.
>
>
>
> Section 5.4 Says:
>
> TEAP authentication assures the Master Session Key (MSK) and Extended
>  Master Session Key (EMSK) output from the EAP method are the result
>  of all authentication conversations by generating an Intermediate
>  Compound Key (IMCK).  The IMCK is mutually derived by the peer and
>  the server as described in Section 5.2 by combining the MSKs from inner
>
>  EAP methods with key material from TEAP Phase 1.
>
>
>
> It should say:
>
>
>
> TEAP authentication assures the Master Session Key (MSK) and Extended
>  Master Session Key (EMSK) output from the EAP method are the result
>  of all authentication conversations by generating an Intermediate
>  Compound Key (IMCK).  The IMCK is mutually derived by the peer and
>  the server as described in Section 5.2 by combining the IMSKs from inner
>
>  EAP methods with key material from TEAP Phase 1.
>
>
>
> Note:
>
>
>
> This revision is to clarify how to handle the case where you need to
> generate
>
> both MSK and EMSK keys.   The original text was incomplete and ambiguous
>
> in some places.
>

--000000000000d8ef1a05b29ef51f
Content-Type: text/html; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable

<div dir=3D"ltr"><div dir=3D"ltr"><br></div><br><div class=3D"gmail_quote">=
<div dir=3D"ltr" class=3D"gmail_attr">On Mon, Oct 26, 2020 at 12:51 PM Jorg=
e Vergara &lt;<a href=3D"mailto:jovergar@microsoft.com">jovergar@microsoft.=
com</a>&gt; wrote:<br></div><blockquote class=3D"gmail_quote" style=3D"marg=
in:0px 0px 0px 0.8ex;border-left:1px solid rgb(204,204,204);padding-left:1e=
x">





<div lang=3D"EN-US" style=3D"overflow-wrap: break-word;">
<div class=3D"gmail-m_-1610661603253490824WordSection1">
<p class=3D"MsoNormal">This is a detailed one so I=E2=80=99ve tried to go o=
ver it carefully. Most of it looks good but I=E2=80=99m unsure about this p=
art:<u></u><u></u></p>
<p class=3D"MsoNormal"><u></u>=C2=A0<u></u></p>
<p class=3D"MsoNormal">&gt; If an inner method fails or MAC verification=C2=
=A0<u></u><u></u></p>
<p class=3D"MsoNormal">fails then S-IMCK is not used in further calculation=
.=C2=A0=C2=A0<u></u><u></u></p>
<p class=3D"MsoNormal"><u></u>=C2=A0<u></u></p>
<p class=3D"MsoNormal">It is a valid scenario that multiple authentication =
methods run and some fail, but the overall TEAP authentication succeeds. Fo=
r example, if two inner EAP Authentication methods run and the first fails =
but the seconds succeeds, the calculation
 needs to be valid. Based on the old text, that authentication method is om=
itted from calculations. This is what current implementations do.<u></u><u>=
</u></p>
<p class=3D"MsoNormal"><u></u>=C2=A0<u></u></p>
<p class=3D"MsoNormal">My editorial comment based on some other errata woul=
d be to that text needs to specify =E2=80=9Cauthentication=E2=80=9D methods=
 (per Jouni=E2=80=99s other errata) since the Identity method doesn=E2=80=
=99t factor in here. I think it would also be beneficial to be specific
 about the behavior of basic username and password authentication here. Ole=
g made some comments to this effect on another email. Our implementation do=
esn=E2=80=99t support basic username and password authentication so I don=
=E2=80=99t have any prior experience here.<u></u><u></u></p>
<p class=3D"MsoNormal"><u></u></p></div></div></blockquote><div><br></div><=
div>[Joe] Yes I think it is fine to say EAP authentication=C2=A0method.=C2=
=A0 =C2=A0I have=C2=A0been convinced that the spec requires crypto-binding =
with the basic password authentication.=C2=A0 =C2=A0I&#39;ll need to add th=
is in.=C2=A0</div><div>=C2=A0</div><blockquote class=3D"gmail_quote" style=
=3D"margin:0px 0px 0px 0.8ex;border-left:1px solid rgb(204,204,204);padding=
-left:1ex"><div lang=3D"EN-US" style=3D"overflow-wrap: break-word;"><div cl=
ass=3D"gmail-m_-1610661603253490824WordSection1"><p class=3D"MsoNormal">=C2=
=A0<u></u></p>
<p class=3D"MsoNormal">Jorge Vergara<u></u><u></u></p>
<p class=3D"MsoNormal"><u></u>=C2=A0<u></u></p>
<div style=3D"border-right:none;border-bottom:none;border-left:none;border-=
top:1pt solid rgb(225,225,225);padding:3pt 0in 0in">
<p class=3D"MsoNormal"><b>From:</b> Joseph Salowey &lt;<a href=3D"mailto:jo=
e@salowey.net" target=3D"_blank">joe@salowey.net</a>&gt; <br>
<b>Sent:</b> Saturday, October 24, 2020 5:18 PM<br>
<b>To:</b> EMU WG &lt;<a href=3D"mailto:emu@ietf.org" target=3D"_blank">emu=
@ietf.org</a>&gt;<br>
<b>Cc:</b> Oleg Pekar &lt;<a href=3D"mailto:oleg.pekar.2017@gmail.com" targ=
et=3D"_blank">oleg.pekar.2017@gmail.com</a>&gt;; Jouni Malinen &lt;<a href=
=3D"mailto:j@w1.fi" target=3D"_blank">j@w1.fi</a>&gt;; Jorge Vergara &lt;<a=
 href=3D"mailto:jovergar@microsoft.com" target=3D"_blank">jovergar@microsof=
t.com</a>&gt;<br>
<b>Subject:</b> Proposed Resolution to TEAP Errata 5770<u></u><u></u></p>
</div>
<p class=3D"MsoNormal"><u></u>=C2=A0<u></u></p>
<div>
<p class=3D"MsoNormal">Errata 5770:=C2=A0<a href=3D"https://nam06.safelinks=
.protection.outlook.com/?url=3Dhttps%3A%2F%2Fwww.rfc-editor.org%2Ferrata%2F=
eid5770&amp;data=3D04%7C01%7Cjovergar%40microsoft.com%7C728ceb6af6694e40e08=
e08d8787b669d%7C72f988bf86f141af91ab2d7cd011db47%7C1%7C0%7C6373918186897817=
23%7CUnknown%7CTWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1h=
aWwiLCJXVCI6Mn0%3D%7C1000&amp;sdata=3DRuRrXZ5c70r43Rmyl4s%2BVUKAA22nGtoenLE=
lbCeUkmE%3D&amp;reserved=3D0" target=3D"_blank">https://www.rfc-editor.org/=
errata/eid5770</a><u></u><u></u></p>
<div>
<p class=3D"MsoNormal">Proposed Status: Verified<u></u><u></u></p>
</div>
<div>
<p class=3D"MsoNormal">Revision:<u></u><u></u></p>
</div>
<div>
<p class=3D"MsoNormal"><u></u>=C2=A0<u></u></p>
</div>
<div>
<p class=3D"MsoNormal">Section 5.2 Says:<u></u><u></u></p>
</div>
<div>
<p class=3D"MsoNormal"><u></u>=C2=A0<u></u></p>
</div>
<p class=3D"MsoNormal">On the sender of the Crypto-Binding TLV side: =C2=A0=
 =C2=A0<br>
<br>
=C2=A0 =C2=A0 =C2=A0If the EMSK is not available, then the sender computes =
the Compound<br>
=C2=A0 =C2=A0 =C2=A0MAC using the MSK of the inner method.<br>
<br>
=C2=A0 =C2=A0 =C2=A0If the EMSK is available and the sender&#39;s policy ac=
cepts MSK-based<br>
=C2=A0 =C2=A0 =C2=A0MAC, then the sender computes two Compound MAC values.=
=C2=A0 The first<br>
=C2=A0 =C2=A0 =C2=A0is computed with the EMSK.=C2=A0 The second one is comp=
uted using the<br>
=C2=A0 =C2=A0 =C2=A0MSK.=C2=A0 Both MACs are then sent to the other side.<b=
r>
<br>
=C2=A0 =C2=A0 =C2=A0If the EMSK is available but the sender&#39;s policy do=
es not allow<br>
=C2=A0 =C2=A0 =C2=A0downgrading to MSK-generated MAC, then the sender SHOUL=
D only send<br>
=C2=A0 =C2=A0 =C2=A0EMSK-based MAC.<br>
<br>
=C2=A0 =C2=A0On the receiver of the Crypto-Binding TLV side:<br>
<br>
=C2=A0 =C2=A0 =C2=A0If the EMSK is not available and an MSK-based Compound =
MAC was<br>
=C2=A0 =C2=A0 =C2=A0sent, then the receiver validates the Compound MAC and =
sends back<br>
=C2=A0 =C2=A0 =C2=A0an MSK-based Compound MAC response.<br>
<br>
=C2=A0 =C2=A0 =C2=A0If the EMSK is not available and no MSK-based Compound =
MAC was<br>
=C2=A0 =C2=A0 =C2=A0sent, then the receiver handles like an invalid Crypto-=
Binding TLV<br>
=C2=A0 =C2=A0 =C2=A0with a fatal error.<br>
<br>
=C2=A0 =C2=A0 =C2=A0If the EMSK is available and an EMSK-based Compound MAC=
 was sent,<br>
=C2=A0 =C2=A0 =C2=A0then the receiver validates it and creates a response C=
ompound MAC<br>
=C2=A0 =C2=A0 =C2=A0using the EMSK.<br>
<br>
=C2=A0 =C2=A0 =C2=A0If the EMSK is available but no EMSK-based Compound MAC=
 was sent<br>
=C2=A0 =C2=A0 =C2=A0and its policy accepts MSK-based MAC, then the receiver=
 validates<br>
=C2=A0 =C2=A0 =C2=A0it using the MSK and, if successful, generates and retu=
rns an MSK-<br>
=C2=A0 =C2=A0 =C2=A0based Compound MAC.<br>
<br>
=C2=A0 =C2=A0 =C2=A0If the EMSK is available but no EMSK Compound MAC was s=
ent and its<br>
=C2=A0 =C2=A0 =C2=A0policy does not accept MSK-based MAC, then the receiver=
 handles<br>
=C2=A0 =C2=A0 =C2=A0like an invalid Crypto-Binding TLV with a fatal error.<=
u></u><u></u></p>
<div>
<p class=3D"MsoNormal"><u></u>=C2=A0<u></u></p>
</div>
<div>
<p class=3D"MsoNormal">If the ith inner method does not generate an EMSK or=
 MSK, then IMSKi<br>
is set to zero (e.g., MSKi =3D 32 octets of 0x00s).=C2=A0 If an inner metho=
d<br>
fails, then it is not included in this calculation.<u></u><u></u></p>
</div>
<div>
<p class=3D"MsoNormal"><u></u>=C2=A0<u></u></p>
</div>
<div>
<p class=3D"MsoNormal">It Should Say:<u></u><u></u></p>
</div>
<div>
<p class=3D"MsoNormal"><u></u>=C2=A0<u></u></p>
</div>
<div>
<p class=3D"MsoNormal">On the sender of the Crypto-Binding TLV side: =C2=A0=
 =C2=A0<br>
<br>
=C2=A0 =C2=A0 =C2=A0If the EMSK is not available, then the sender computes =
the Compound<br>
=C2=A0 =C2=A0 =C2=A0MAC using the CMK generated from MSK (CMK-MSK) of the i=
nner method.<br>
<br>
=C2=A0 =C2=A0 =C2=A0If the EMSK is available and the sender&#39;s policy ac=
cepts MSK-based<br>
=C2=A0 =C2=A0 =C2=A0MAC, then the sender computes two Compound MAC values.=
=C2=A0 The first<br>
=C2=A0 =C2=A0 =C2=A0is computed with the CMK generated from the EMSK (CMK-E=
MSK).=C2=A0 The=C2=A0<u></u><u></u></p>
</div>
<div>
<p class=3D"MsoNormal">=C2=A0 =C2=A0 =C2=A0second one is computed using the=
=C2=A0CMK-MSK.=C2=A0 Both MACs are=C2=A0<u></u><u></u></p>
</div>
<div>
<p class=3D"MsoNormal">=C2=A0 =C2=A0 =C2=A0then sent to the other side.=C2=
=A0 This also means the sender must generate<u></u><u></u></p>
</div>
<div>
<p class=3D"MsoNormal">=C2=A0 =C2=A0 =C2=A0both EMSK and MSK based S-IMCKs.=
<br>
<br>
=C2=A0 =C2=A0 =C2=A0If the EMSK is available but the sender&#39;s policy do=
es not allow<br>
=C2=A0 =C2=A0 =C2=A0downgrading to CMK-MSK MAC, then the sender SHOULD only=
 send<br>
=C2=A0 =C2=A0 =C2=A0a MAC computed from the CMK-EMSK.<br>
<br>
=C2=A0 =C2=A0On the receiver of the Crypto-Binding TLV side:<br>
<br>
=C2=A0 =C2=A0 =C2=A0If the EMSK is not available and an CMK-MSK Compound MA=
C was<br>
=C2=A0 =C2=A0 =C2=A0sent, then the receiver validates the Compound MAC and =
sends back<br>
=C2=A0 =C2=A0 =C2=A0an CMK-MSK Compound MAC response.<br>
<br>
=C2=A0 =C2=A0 =C2=A0If the EMSK is not available and no CMK-MSK Compound MA=
C was<br>
=C2=A0 =C2=A0 =C2=A0sent, then the receiver handles like an invalid Crypto-=
Binding TLV<br>
=C2=A0 =C2=A0 =C2=A0with a fatal error.<br>
<br>
=C2=A0 =C2=A0 =C2=A0If the EMSK is available and a CMK-EMSK Compound MAC wa=
s sent,<br>
=C2=A0 =C2=A0 =C2=A0then the receiver validates it and creates a response C=
ompound MAC<br>
=C2=A0 =C2=A0 =C2=A0using the CMK-EMSK.<br>
<br>
=C2=A0 =C2=A0 =C2=A0If the EMSK is available but no CMK-EMSK Compound MAC w=
as sent<br>
=C2=A0 =C2=A0 =C2=A0and its policy accepts CMK-MSK MAC, then the receiver v=
alidates<br>
=C2=A0 =C2=A0 =C2=A0it using the CMK-MSK and, if successful, generates and =
returns an MSK-<br>
=C2=A0 =C2=A0 =C2=A0based Compound MAC.<br>
<br>
=C2=A0 =C2=A0 =C2=A0If the EMSK is available but no CMK-EMSK Compound MAC w=
as sent and its<br>
=C2=A0 =C2=A0 =C2=A0policy does not accept CMK-MSK MAC, then the receiver h=
andles<br>
=C2=A0 =C2=A0 =C2=A0like an invalid Crypto-Binding TLV with a fatal error.<=
u></u><u></u></p>
</div>
<div>
<p class=3D"MsoNormal"><u></u>=C2=A0<u></u></p>
</div>
<p class=3D"MsoNormal">The IMSK used is either the EMSK-based IMSK or the M=
SK based IMSK depending<br>
upon the rules outlined above. If the ith inner method does not generate an=
 EMSK=C2=A0<br>
or MSK, then IMSKi is set to zero (e.g., MSKi =3D 32 octets of 0x00s). =C2=
=A0=C2=A0 It is possible=C2=A0<u></u><u></u></p>
<div>
<p class=3D"MsoNormal">that two S-IMCKs for a step may be generated based o=
n the rules above.=C2=A0 In this=C2=A0<u></u><u></u></p>
</div>
<div>
<p class=3D"MsoNormal">case the S-IMCK for=C2=A0further calculations is cho=
sen as follows.=C2=A0 If the MAC based=C2=A0<u></u><u></u></p>
</div>
<div>
<p class=3D"MsoNormal">on the CMK-EMSK is=C2=A0verified then the S-IMCK gen=
erated based on the EMSK is=C2=A0<u></u><u></u></p>
</div>
<div>
<p class=3D"MsoNormal">used.=C2=A0 Else, if the MAC=C2=A0based on the CMK-M=
SK is verified then the S-IMCK=C2=A0<u></u><u></u></p>
</div>
<div>
<p class=3D"MsoNormal">generated based on the MSK=C2=A0is used.=C2=A0 If an=
 inner method fails or MAC verification=C2=A0<u></u><u></u></p>
</div>
<div>
<p class=3D"MsoNormal">fails then S-IMCK is not used in further calculation=
.=C2=A0=C2=A0<u></u><u></u></p>
<div>
<div>
<p class=3D"MsoNormal"><u></u>=C2=A0<u></u></p>
</div>
<div>
<p class=3D"MsoNormal" style=3D"margin-bottom:12pt">Section 5.4 Says:<u></u=
><u></u></p>
</div>
<div>
<p class=3D"MsoNormal">TEAP authentication assures the Master Session Key (=
MSK) and Extended<br>
=C2=A0Master Session Key (EMSK) output from the EAP method are the result<b=
r>
=C2=A0of all authentication conversations by generating an Intermediate<br>
=C2=A0Compound Key (IMCK).=C2=A0 The IMCK is mutually derived by the peer a=
nd<br>
=C2=A0the server as described in Section 5.2 by combining the MSKs from inn=
er<u></u><u></u></p>
</div>
<div>
<p class=3D"MsoNormal">=C2=A0EAP methods with key material from TEAP Phase =
1.<u></u><u></u></p>
</div>
<div>
<p class=3D"MsoNormal"><u></u>=C2=A0<u></u></p>
</div>
<div>
<p class=3D"MsoNormal">It should say:<u></u><u></u></p>
</div>
<div>
<p class=3D"MsoNormal"><u></u>=C2=A0<u></u></p>
</div>
<div>
<div>
<p class=3D"MsoNormal">TEAP authentication assures the Master Session Key (=
MSK) and Extended<br>
=C2=A0Master Session Key (EMSK) output from the EAP method are the result<b=
r>
=C2=A0of all authentication conversations by generating an Intermediate<br>
=C2=A0Compound Key (IMCK).=C2=A0 The IMCK is mutually derived by the peer a=
nd<br>
=C2=A0the server as described in Section 5.2 by combining the IMSKs from in=
ner<u></u><u></u></p>
</div>
<div>
<p class=3D"MsoNormal">=C2=A0EAP methods with key material from TEAP Phase =
1.<u></u><u></u></p>
</div>
</div>
<div>
<p class=3D"MsoNormal"><u></u>=C2=A0<u></u></p>
</div>
</div>
</div>
<div>
<p class=3D"MsoNormal">Note:<u></u><u></u></p>
</div>
<div>
<p class=3D"MsoNormal"><u></u>=C2=A0<u></u></p>
</div>
<div>
<p class=3D"MsoNormal">This revision is to clarify how to handle the case w=
here you need to generate=C2=A0<u></u><u></u></p>
</div>
<div>
<p class=3D"MsoNormal">both MSK and EMSK keys.=C2=A0 =C2=A0The original tex=
t was incomplete=C2=A0and ambiguous=C2=A0<u></u><u></u></p>
</div>
<div>
<p class=3D"MsoNormal">in some places.=C2=A0=C2=A0<u></u><u></u></p>
</div>
</div>
</div>
</div>

</blockquote></div></div>

--000000000000d8ef1a05b29ef51f--


From nobody Tue Oct 27 00:23:48 2020
Return-Path: <lear@cisco.com>
X-Original-To: emu@ietfa.amsl.com
Delivered-To: emu@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 038543A1618 for <emu@ietfa.amsl.com>; Tue, 27 Oct 2020 00:23:46 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -9.601
X-Spam-Level: 
X-Spam-Status: No, score=-9.601 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIMWL_WL_MED=-0.001, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, DKIM_VALID_EF=-0.1, SPF_PASS=-0.001, URIBL_BLOCKED=0.001, USER_IN_DEF_DKIM_WL=-7.5] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (1024-bit key) header.d=cisco.com
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 ai_k-Id6wpSo for <emu@ietfa.amsl.com>; Tue, 27 Oct 2020 00:23:45 -0700 (PDT)
Received: from aer-iport-3.cisco.com (aer-iport-3.cisco.com [173.38.203.53]) (using TLSv1.2 with cipher DHE-RSA-SEED-SHA (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 95F203A1608 for <emu@ietf.org>; Tue, 27 Oct 2020 00:23:44 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=cisco.com; i=@cisco.com; l=468; q=dns/txt; s=iport; t=1603783424; x=1604993024; h=mime-version:subject:from:in-reply-to:date:cc: content-transfer-encoding:message-id:references:to; bh=Zvp8P94sE8099sQ8uT958wHbPOYFxmRPeeer1RiU1Mc=; b=b9WST+4nLh6GbLs9mSjHoY8iFDEX6BnwsnVry6WrRczhbPZaYW/2PQz6 C+Fu5IJQw3r36XyT9wt/4pujS6mjNW1OhI5dYjBlT46LIpaYKawuNBrgT q3iLTaiP4hlA5kkhJu9ulQVM0w7midkPf5IiBf6+7/E4SXCcniEJTeWTn A=;
X-IPAS-Result: =?us-ascii?q?A0ApAwDGyJdf/xbLJq1gHAEBAQEBAQcBARIBAQQEAQFAg?= =?us-ascii?q?U+CKoFFASASjW2YSotpCwEBAQ0BAS8EAQGESgKCDCY4EwIDAQEBAwIDAQEBA?= =?us-ascii?q?QUBAQECAQYEbYVthXMGOj8QCw4iFlcGgzmCfaUjdIE0hVeEboE4i3aBXoIAg?= =?us-ascii?q?REnHIIfLj6EPU+Ce4IsBLgGgnWDF5dlAx+DBQGeWLAZg18CBAYFAhWBayMqg?= =?us-ascii?q?S0zGggbFWUBgj89EhkNnGdAA2gCBgoBAQMJjCiCIAEB?=
X-IronPort-Anti-Spam-Filtered: true
X-IronPort-AV: E=Sophos;i="5.77,422,1596499200"; d="scan'208";a="28224737"
Received: from aer-iport-nat.cisco.com (HELO aer-core-1.cisco.com) ([173.38.203.22]) by aer-iport-3.cisco.com with ESMTP/TLS/DHE-RSA-SEED-SHA; 27 Oct 2020 07:23:40 +0000
Received: from dhcp-10-61-108-253.cisco.com (dhcp-10-61-108-253.cisco.com [10.61.108.253]) by aer-core-1.cisco.com (8.15.2/8.15.2) with ESMTPS id 09R7Ndj1026074 (version=TLSv1.2 cipher=DHE-RSA-AES256-GCM-SHA384 bits=256 verify=NO); Tue, 27 Oct 2020 07:23:40 GMT
Content-Type: text/plain; charset=us-ascii
Mime-Version: 1.0 (Mac OS X Mail 13.4 \(3608.120.23.2.4\))
From: Eliot Lear <lear@cisco.com>
In-Reply-To: <CAOgPGoBrNM8Kxuoic7wXmkWjavk_rsewDj8paS4CTR97+e3V_g@mail.gmail.com>
Date: Tue, 27 Oct 2020 08:23:39 +0100
Cc: Jorge Vergara <jovergar@microsoft.com>, EMU WG <emu@ietf.org>
Content-Transfer-Encoding: quoted-printable
Message-Id: <8B94A17A-0EE9-4A05-82FF-C807B2C35555@cisco.com>
References: <CAOgPGoCg2wRKFVKz2kqkomt7mkp1W98jSh6xLT8z1_uWBMXdmA@mail.gmail.com> <CH2PR21MB138172CE5A552084A62E3AA9D1190@CH2PR21MB1381.namprd21.prod.outlook.com> <CAOgPGoBrNM8Kxuoic7wXmkWjavk_rsewDj8paS4CTR97+e3V_g@mail.gmail.com>
To: Joseph Salowey <joe@salowey.net>
X-Mailer: Apple Mail (2.3608.120.23.2.4)
X-Outbound-SMTP-Client: 10.61.108.253, dhcp-10-61-108-253.cisco.com
X-Outbound-Node: aer-core-1.cisco.com
Archived-At: <https://mailarchive.ietf.org/arch/msg/emu/x2hV8I_CJwYUreXg8u3A12nx5Ao>
Subject: Re: [Emu] Proposed Resolution to TEAP Errata 5770
X-BeenThere: emu@ietf.org
X-Mailman-Version: 2.1.29
Precedence: list
List-Id: "EAP Methods Update \(EMU\)" <emu.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/emu>, <mailto:emu-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/emu/>
List-Post: <mailto:emu@ietf.org>
List-Help: <mailto:emu-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/emu>, <mailto:emu-request@ietf.org?subject=subscribe>
X-List-Received-Date: Tue, 27 Oct 2020 07:23:46 -0000

Hi,

>=20
> [Joe] Yes I think it is fine to say EAP authentication method.   I =
have been convinced that the spec requires crypto-binding with the basic =
password authentication.   I'll need to add this in.=20
> =20

Keep in mind that there might not even be basic auth.  One case is that =
one just uses the OUTER auth, does some PKCS ops or extensions and then =
wants to conclude.  No inner in this case.  Which erratum is that =
covered by?

Eliot


From nobody Tue Oct 27 02:34:06 2020
Return-Path: <Hannes.Tschofenig@arm.com>
X-Original-To: emu@ietfa.amsl.com
Delivered-To: emu@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 59BFD3A1672 for <emu@ietfa.amsl.com>; Tue, 27 Oct 2020 02:34:05 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.901
X-Spam-Level: 
X-Spam-Status: No, score=-1.901 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, RCVD_IN_MSPIKE_H2=-0.001, SPF_PASS=-0.001, UNPARSEABLE_RELAY=0.001] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (1024-bit key) header.d=armh.onmicrosoft.com header.b=UvyAShfL; dkim=pass (1024-bit key) header.d=armh.onmicrosoft.com header.b=UvyAShfL
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 HcUOQm6NKrqE for <emu@ietfa.amsl.com>; Tue, 27 Oct 2020 02:34:04 -0700 (PDT)
Received: from EUR04-HE1-obe.outbound.protection.outlook.com (mail-eopbgr70055.outbound.protection.outlook.com [40.107.7.55]) (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 907B83A167A for <emu@ietf.org>; Tue, 27 Oct 2020 02:34:03 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=armh.onmicrosoft.com;  s=selector2-armh-onmicrosoft-com; h=From:Date:Subject:Message-ID:Content-Type:MIME-Version:X-MS-Exchange-SenderADCheck; bh=TS/uR7mKgLnFzKw/oH5xnPpDoWw9d0pekcNBa79uAsA=; b=UvyAShfLmV1rf8jcikgVew4yGiTv+GCH70EMohbmKAR/iJNRrRoUpYyQp3rHeko0JcbmeZ/z+fbOTErFhDd695Kxg4zyO4IGLT+WVIEWYGjfRM5JPZOlTi3xs3zR/YPGmxAABW5cpHvW8IhL14QwX0EPygaO2w3pCHcuQZ3vYZQ=
Received: from AM0PR01CA0143.eurprd01.prod.exchangelabs.com (2603:10a6:208:168::48) by VI1PR0802MB2160.eurprd08.prod.outlook.com (2603:10a6:800:9b::17) with Microsoft SMTP Server (version=TLS1_2, cipher=TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384) id 15.20.3499.18; Tue, 27 Oct 2020 09:34:00 +0000
Received: from VE1EUR03FT046.eop-EUR03.prod.protection.outlook.com (2603:10a6:208:168:cafe::25) by AM0PR01CA0143.outlook.office365.com (2603:10a6:208:168::48) with Microsoft SMTP Server (version=TLS1_2, cipher=TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384) id 15.20.3499.19 via Frontend Transport; Tue, 27 Oct 2020 09:34:00 +0000
X-MS-Exchange-Authentication-Results: spf=temperror (sender IP is 63.35.35.123) smtp.mailfrom=arm.com; ietf.org; dkim=pass (signature was verified) header.d=armh.onmicrosoft.com; ietf.org; dmarc=temperror action=none header.from=arm.com;
Received-SPF: TempError (protection.outlook.com: error in processing during lookup of arm.com: DNS Timeout)
Received: from 64aa7808-outbound-1.mta.getcheckrecipient.com (63.35.35.123) by VE1EUR03FT046.mail.protection.outlook.com (10.152.19.226) with Microsoft SMTP Server (version=TLS1_2, cipher=TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384) id 15.20.3499.18 via Frontend Transport; Tue, 27 Oct 2020 09:33:57 +0000
Received: ("Tessian outbound c579d876a324:v64"); Tue, 27 Oct 2020 09:33:56 +0000
X-CR-MTA-TID: 64aa7808
Received: from 72369d46d4b2.1 by 64aa7808-outbound-1.mta.getcheckrecipient.com id 9A9B25CB-C471-460E-9991-B497091557A6.1;  Tue, 27 Oct 2020 09:33:51 +0000
Received: from EUR05-DB8-obe.outbound.protection.outlook.com by 64aa7808-outbound-1.mta.getcheckrecipient.com with ESMTPS id 72369d46d4b2.1 (version=TLSv1.2 cipher=ECDHE-RSA-AES256-GCM-SHA384); Tue, 27 Oct 2020 09:33:51 +0000
ARC-Seal: i=1; a=rsa-sha256; s=arcselector9901; d=microsoft.com; cv=none; b=eimtzQGA1K6ZdgUAxl2BV6VcZUtqbDSqNnQOH2NOMvq+XORTjNWEv4sAvltlisgTFPgKa+AU6MMAzTMyEOURSUxaFsgBp8WYkaP5PZwA8S+LcPQe/z+fyOz7ZPNIKlJvM/aDEUDCpeZdwdyGk91nayPfdjimSLxi6VdpGG+O51tied5IEyhF1uhqzJOHvut+9TYcpf6saoUOFc7qfuEn1iWraCNOTa59UDyKerUo1JjL0ribRbUDmQF3i3817g16PhHNA6dqJ/Ljtvb3TjKVjbrQzEkzE+lAwLkfsBg/toYKtpTOEdnVMkBu8DFLxfqlGzksC9Uvs7tlZah2HeVNUw==
ARC-Message-Signature: i=1; a=rsa-sha256; c=relaxed/relaxed; d=microsoft.com;  s=arcselector9901; h=From:Date:Subject:Message-ID:Content-Type:MIME-Version:X-MS-Exchange-SenderADCheck; bh=TS/uR7mKgLnFzKw/oH5xnPpDoWw9d0pekcNBa79uAsA=; b=OWqaVzIRjG/ZzrF8+IXR2e3BeVkqCADrrc11SfrR8KwT/rR5hgj6l02OJRnz3KDEG81MweT5V29Msi9Xkox8mYTR9UKgE71AZwRT/6x8KDh/hNnfUQXDrGlxgTr2uEJPL85l35P5HrQf0azBSNpbdzuNYtPH35e/QbxTd/O7JyC0CFQEBv3qHUOzuJ9wa8Uw78rRmMdO7t70Z+lbF+ijhhusMSGGKgvvlADMLGqb2nsqP57BuANcgQyw1JLzQa9UduPzzoQYOtxeOEo8HS116c6n6rFMJsT6ALw3/UGdzUeKGX6+DiAwP48zMKJsT3y4IiASnRqAGyDiFUsH8tnbgw==
ARC-Authentication-Results: i=1; mx.microsoft.com 1; spf=pass smtp.mailfrom=arm.com; dmarc=pass action=none header.from=arm.com; dkim=pass header.d=arm.com; arc=none
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=armh.onmicrosoft.com;  s=selector2-armh-onmicrosoft-com; h=From:Date:Subject:Message-ID:Content-Type:MIME-Version:X-MS-Exchange-SenderADCheck; bh=TS/uR7mKgLnFzKw/oH5xnPpDoWw9d0pekcNBa79uAsA=; b=UvyAShfLmV1rf8jcikgVew4yGiTv+GCH70EMohbmKAR/iJNRrRoUpYyQp3rHeko0JcbmeZ/z+fbOTErFhDd695Kxg4zyO4IGLT+WVIEWYGjfRM5JPZOlTi3xs3zR/YPGmxAABW5cpHvW8IhL14QwX0EPygaO2w3pCHcuQZ3vYZQ=
Received: from AM0PR08MB3716.eurprd08.prod.outlook.com (2603:10a6:208:106::13) by AM8PR08MB5828.eurprd08.prod.outlook.com (2603:10a6:20b:1df::21) with Microsoft SMTP Server (version=TLS1_2, cipher=TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384) id 15.20.3477.20; Tue, 27 Oct 2020 09:33:51 +0000
Received: from AM0PR08MB3716.eurprd08.prod.outlook.com ([fe80::900e:c64d:a006:4860]) by AM0PR08MB3716.eurprd08.prod.outlook.com ([fe80::900e:c64d:a006:4860%6]) with mapi id 15.20.3455.037; Tue, 27 Oct 2020 09:33:51 +0000
From: Hannes Tschofenig <Hannes.Tschofenig@arm.com>
To: Alan DeKok <aland@deployingradius.com>
CC: Joseph Salowey <joe@salowey.net>, Eliot Lear <lear=40cisco.com@dmarc.ietf.org>, "emu@ietf.org" <emu@ietf.org>
Thread-Topic: [Emu] draft-ietf-emu-eap-tls13-11: OCSP Stapling
Thread-Index: AdaniLvyfaHHD0ANRluj1nshuTAidQA/HNCAAAyz4QAAFaqz0AALO0qAAMIQfvA=
Date: Tue, 27 Oct 2020 09:33:50 +0000
Message-ID: <AM0PR08MB3716DFF5010A19B7CD3E7002FA160@AM0PR08MB3716.eurprd08.prod.outlook.com>
References: <AM0PR08MB371647618F993B8C5BA6EB5FFA1C0@AM0PR08MB3716.eurprd08.prod.outlook.com> <AD94F3FF-31A7-4F44-95F7-6A7E70FA8D27@cisco.com> <CAOgPGoD3MQu=Hv6HTfug0XredaRt_T7oD7z_uwnATmHku9DmLg@mail.gmail.com> <AM0PR08MB371649BBA92B7F624008D0B3FA1A0@AM0PR08MB3716.eurprd08.prod.outlook.com> <D7FC8B51-3545-4D30-8B6F-35C169B0462B@deployingradius.com>
In-Reply-To: <D7FC8B51-3545-4D30-8B6F-35C169B0462B@deployingradius.com>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
x-ts-tracking-id: C2BD7FFC4127A6478C856558E9B4F574.0
x-checkrecipientchecked: true
Authentication-Results-Original: deployingradius.com; dkim=none (message not signed) header.d=none;deployingradius.com; dmarc=none action=none header.from=arm.com;
x-originating-ip: [80.92.116.60]
x-ms-publictraffictype: Email
X-MS-Office365-Filtering-HT: Tenant
X-MS-Office365-Filtering-Correlation-Id: 386ff0c3-3e97-4fd5-bc57-08d87a5b6e08
x-ms-traffictypediagnostic: AM8PR08MB5828:|VI1PR0802MB2160:
X-Microsoft-Antispam-PRVS: <VI1PR0802MB21608C40D74CF8910DFDA7D5FA160@VI1PR0802MB2160.eurprd08.prod.outlook.com>
x-checkrecipientrouted: true
nodisclaimer: true
x-ms-oob-tlc-oobclassifiers: OLM:9508;OLM:10000;
X-MS-Exchange-SenderADCheck: 1
X-Microsoft-Antispam-Untrusted: BCL:0;
X-Microsoft-Antispam-Message-Info-Original: 7ByfUOa+mayyWTaQ7VsylbFC2tP8Shoa8DBpuh72m2sfK0xg6amtB/CSFSVx9S1+UdkdYKffB7urQSIG3YFwosvY7P7YrmV12EruP9P13y0zLMpRQUlhn7Lv7AKi+x/IZ+hPA68TLhNQWec8tS99CxP/w6aaQHKyyiWU3R4kIHbKk9F0cBxyUxOGjTOA7Ll+smDlLBYS659vvbk1/MZ7Ecercg1QkDGC5DO33NL8tcSMO0ayCV41tI7GDU/AbrqpvwhpjlNGNOZS++p6RTXPXaLsrrnkgrUkmpQUwiNuzU2KBfoD36YE7PSLB+cF50a04AhrN7TKT/UP6N2+hMJZyQ==
X-Forefront-Antispam-Report-Untrusted: CIP:255.255.255.255; CTRY:; LANG:en; SCL:1; SRV:; IPV:NLI; SFV:NSPM; H:AM0PR08MB3716.eurprd08.prod.outlook.com; PTR:; CAT:NONE; SFS:(4636009)(366004)(39860400002)(376002)(346002)(396003)(136003)(66446008)(71200400001)(83380400001)(55016002)(8936002)(4326008)(33656002)(66946007)(86362001)(26005)(9686003)(186003)(6916009)(8676002)(2906002)(66556008)(478600001)(5660300002)(66476007)(64756008)(6506007)(54906003)(76116006)(316002)(52536014)(7696005); DIR:OUT; SFP:1101; 
x-ms-exchange-antispam-messagedata: dbQgQ3UN+f3UK04nrerOM1kF/c9yvmOzI3KLIib7RVpUS2YVtKcdrTVvzybcIixECw+AtiaXxG5tAVTo2zSPHPndixqaDrD/jfpfkVp4o9t2iWxGqp8/RO9+fmeh7RMaMYwuzTMXCpqwT2JAM8aIZ1M3d1V3gzzu9ToMTcjR90aG5Aem7wY5vtHz1TPNMICLYFREO6iMtHkqKXfxrw6T7cLwbpoxK90tVkrK+iGWTsffZCOYRrYcXFMQrZAhg7fPsIcU5Jd7dQP3xnnMABAAzPXmwDhN4H89brE8doviSvuuMLgBCZmqiNQnEyHdNtOoDuOVxEpo4gQBh2bycqoX3kmXFfBgTuU4H0p/cCBvou7GNUP0YqoeK6FDAAPczZU+bdCKC0V1Dh40z7JFXTAX7WZ0RgACR1rzdy6YIu8Lk+7IFA0YBlzG8A6p7mVlheU6P25VOgq4cJgSlRholT7EUaL9csry6r3ODAP7X+K9mD8I9TslfKxvLVTi/H1J7eZMaNEHZaIevs2yTXOqa7O20aVlI41F0NUD86glX6e+wZ4qlpa6ZWqtDGCl6Og0x3ZSR4+dPQzFBVdv4TtFwJA6m7ep65CHSn6qtob26S55+hCv+QCwS4XGv0wfd+7EZqYqPPVx6zCESSdjRWb1HPChOw==
x-ms-exchange-transport-forked: True
Content-Type: text/plain; charset="utf-8"
Content-Transfer-Encoding: base64
MIME-Version: 1.0
X-MS-Exchange-Transport-CrossTenantHeadersStamped: AM8PR08MB5828
Original-Authentication-Results: deployingradius.com; dkim=none (message not signed) header.d=none;deployingradius.com; dmarc=none action=none header.from=arm.com;
X-EOPAttributedMessage: 0
X-MS-Exchange-Transport-CrossTenantHeadersStripped: VE1EUR03FT046.eop-EUR03.prod.protection.outlook.com
X-MS-Office365-Filtering-Correlation-Id-Prvs: ab6ca125-3ce6-42da-115e-08d87a5b69ed
X-Microsoft-Antispam: BCL:0;
X-Microsoft-Antispam-Message-Info: yAXfkwTAFtYl73gKZ5CbZjEwOfktnbNT7lfNyXORevBnE7orWLx9uQ2Ubu16OzCPDJ955NPnroScXmIqJwA9eMVept5puUUogOK/2KGsKJd6YohXDP4Wq3s1BjZCdXXaS1/zGoL8j4JZQuChQL8yWDTilkjJItGkujfkEc99sfwUdw5oI9TH9Ac7O986hKA+UtdsNcrBtkWhSmyfgB07fT008qAShr4SyOyMuePa4XzoG0KUFBpqliLa0ZvNLkFIUz1jOvUOcZ75AYPP0hoQZuAK9EfxIob4diNQbEd8+sG9/AIvy2IQPk8S9GRxuJvyKUyx1ZUncebO47BJX/Qlj9eZVzFNZCJ0uKHxmy4BmD5HCIbBVdygXAC7q/sTRqDmskqf9QGXR8OBG4J8dYCZ4A==
X-Forefront-Antispam-Report: CIP:63.35.35.123; CTRY:IE; LANG:en; SCL:1; SRV:;  IPV:CAL; SFV:NSPM; H:64aa7808-outbound-1.mta.getcheckrecipient.com;  PTR:ec2-63-35-35-123.eu-west-1.compute.amazonaws.com; CAT:NONE; SFS:(4636009)(346002)(396003)(39860400002)(136003)(376002)(46966005)(36906005)(54906003)(356005)(6506007)(55016002)(8936002)(63350400001)(81166007)(7696005)(336012)(478600001)(186003)(26005)(316002)(2906002)(8676002)(86362001)(6862004)(83380400001)(52536014)(33656002)(63370400001)(5660300002)(82310400003)(47076004)(4326008)(9686003)(70586007)(70206006)(82740400003); DIR:OUT; SFP:1101; 
X-OriginatorOrg: arm.com
X-MS-Exchange-CrossTenant-OriginalArrivalTime: 27 Oct 2020 09:33:57.8534 (UTC)
X-MS-Exchange-CrossTenant-Network-Message-Id: 386ff0c3-3e97-4fd5-bc57-08d87a5b6e08
X-MS-Exchange-CrossTenant-Id: f34e5979-57d9-4aaa-ad4d-b122a662184d
X-MS-Exchange-CrossTenant-OriginalAttributedTenantConnectingIp: TenantId=f34e5979-57d9-4aaa-ad4d-b122a662184d; Ip=[63.35.35.123];  Helo=[64aa7808-outbound-1.mta.getcheckrecipient.com]
X-MS-Exchange-CrossTenant-AuthSource: VE1EUR03FT046.eop-EUR03.prod.protection.outlook.com
X-MS-Exchange-CrossTenant-AuthAs: Anonymous
X-MS-Exchange-CrossTenant-FromEntityHeader: HybridOnPrem
X-MS-Exchange-Transport-CrossTenantHeadersStamped: VI1PR0802MB2160
Archived-At: <https://mailarchive.ietf.org/arch/msg/emu/kAXuLbquC04iC68069fPotU1Al0>
Subject: Re: [Emu] draft-ietf-emu-eap-tls13-11: OCSP Stapling
X-BeenThere: emu@ietf.org
X-Mailman-Version: 2.1.29
Precedence: list
List-Id: "EAP Methods Update \(EMU\)" <emu.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/emu>, <mailto:emu-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/emu/>
List-Post: <mailto:emu@ietf.org>
List-Help: <mailto:emu-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/emu>, <mailto:emu-request@ietf.org?subject=subscribe>
X-List-Received-Date: Tue, 27 Oct 2020 09:34:05 -0000

SGkgQWxhbiwNCg0KDQo+ICBIb3dldmVyLCBpbiB0aGUgYWJzZW5jZSBvZiBhbm90aGVyIHNwZWNp
ZmljYXRpb24sIHdlIG5lZWQgdG8gc2F5ICpzb21ldGhpbmcqIGZvciBFQVAtVExTLg0KDQpXaHkg
ZG9lc24ndCB0aGUgZ3JvdXAgd3JpdGUgdGhhdCBvdGhlciBkb2N1bWVudD8gVGhlcmUgYXJlIHNl
dmVyYWwgb3RoZXIgRUFQIG1ldGhvZHMgdGhhdCB1c2UgY2VydGlmaWNhdGVzIGFzIHdlbGwuDQoN
Cj4+IFdvdWxkbuKAmXQgdGhpcyBiZSBhIHRvcGljIHRvIGFkZHJlc3MgaW4gPGRyYWZ0LWlldGYt
ZW11LWVhcHRsc2NlcnQ+PyBJTUhPIHRoaXMgd291bGQgbWFrZSBtb3JlIHNlbnNlIGdpdmVuIHRo
YXQgPGRyYWZ0LWlldGYtZW11LWVhcHRsc2NlcnQ+IHRhbGtzIGFib3V0IGxhcmdlIGNlcnRpZmlj
YXRlcyBhbmQgbG9uZyBjZXJ0aWZpY2F0ZSBjaGFpbnMgYW5kIGFueSBwcm9wb3NhbCB0byBtYWtl
IHRob3NlIGV2ZW4gbGFyZ2VyIHNob3VsZCBiZSBldmFsdWF0ZWQgaW4gdGhpcyBjb250ZXh0Lg0K
DQo+ICBJIHRoaW5rIHRoYXQgdGhlIHRvcGljcyBhcmUgcmVsYXRlZC4gIEJ1dCBkcmFmdC1pZXRm
LWVtdS1lYXAtdGxzMTMgaXMgbW9yZSBhYm91dCB0aGUgcHJvdG9jb2wsIGFuZCBkcmFmdC1pZXRm
LWVtdS1lYXB0bHNjZXJ0IGlzIG1vcmUgYWJvdXQgZGVwbG95bWVudCBjb25zaWRlcmF0aW9ucy4N
Cg0KVGhlIHNjb3BlIG9mIGRyYWZ0LWlldGYtZW11LWVhcHRsc2NlcnQgaXMgd2hhdGV2ZXIgeW91
IHdhbnQgaXQgdG8gYmUuIEN1cnJlbnRseSwgaXQgaXMgYSBtaXh0dXJlIG9mIGRlcGxveW1lbnQg
c3VnZ2VzdGlvbnMgYW5kIHRoZSB1c2Ugb2YgVExTIGV4dGVuc2lvbnMuDQpNYXliZSB0aGF0IHNj
b3BlIGlzIHdyb25nIGJ1dCBoYXMgcHJvYmFibHkgZ3Jvd24gb3JnYW5pY2FsbHkuDQoNCkNpYW8N
Ckhhbm5lcw0KDQpJTVBPUlRBTlQgTk9USUNFOiBUaGUgY29udGVudHMgb2YgdGhpcyBlbWFpbCBh
bmQgYW55IGF0dGFjaG1lbnRzIGFyZSBjb25maWRlbnRpYWwgYW5kIG1heSBhbHNvIGJlIHByaXZp
bGVnZWQuIElmIHlvdSBhcmUgbm90IHRoZSBpbnRlbmRlZCByZWNpcGllbnQsIHBsZWFzZSBub3Rp
ZnkgdGhlIHNlbmRlciBpbW1lZGlhdGVseSBhbmQgZG8gbm90IGRpc2Nsb3NlIHRoZSBjb250ZW50
cyB0byBhbnkgb3RoZXIgcGVyc29uLCB1c2UgaXQgZm9yIGFueSBwdXJwb3NlLCBvciBzdG9yZSBv
ciBjb3B5IHRoZSBpbmZvcm1hdGlvbiBpbiBhbnkgbWVkaXVtLiBUaGFuayB5b3UuDQo=


From nobody Tue Oct 27 10:49:25 2020
Return-Path: <joe@salowey.net>
X-Original-To: emu@ietfa.amsl.com
Delivered-To: emu@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 66F4D3A1287 for <emu@ietfa.amsl.com>; Tue, 27 Oct 2020 10:49:14 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.898
X-Spam-Level: 
X-Spam-Status: No, score=-1.898 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, HTML_MESSAGE=0.001, SPF_HELO_NONE=0.001, SPF_PASS=-0.001, URIBL_BLOCKED=0.001] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (2048-bit key) header.d=salowey-net.20150623.gappssmtp.com
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 MK2O83O5WNxF for <emu@ietfa.amsl.com>; Tue, 27 Oct 2020 10:49:12 -0700 (PDT)
Received: from mail-qt1-x82f.google.com (mail-qt1-x82f.google.com [IPv6:2607:f8b0:4864:20::82f]) (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 32DC23A12E1 for <emu@ietf.org>; Tue, 27 Oct 2020 10:49:11 -0700 (PDT)
Received: by mail-qt1-x82f.google.com with SMTP id p45so1491436qtb.5 for <emu@ietf.org>; Tue, 27 Oct 2020 10:49:11 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=salowey-net.20150623.gappssmtp.com; s=20150623; h=mime-version:references:in-reply-to:from:date:message-id:subject:to :cc; bh=zXEOD0b45ncjDXBP53Qwou/NUhaEu3y7y3+e87uytmQ=; b=M1eYGO8exF8f9N2MBbdVBkvUJy8UUA0ZkCh9t6wJeVO+fFYZVbJY42ZmydfhVvKZOd KUmiwjyjtVnqoj8d6mVwTA3jd9Qyfl97yL/BZKsPFTu8nilNM7DiTU2CAg92D4A3y1mi 4CXAnMzHXhBZPxDr3z0GAlRBlVmtzECVIcGmsbxpFkOzRLEMZtRvUIhEUxoqgQ/AXqiY q14CSkPsv2mEHNtC9vVuycxS1Um8ZmDeexR8fNOjjY1FeVeEV0f0trQPLqlV/5LaT2PN 7CXRPTIG7T7luxWB7gT9622gc8Q5j1b4TWlNtb8UjxUuBtty7BwhEaIhbr7fQvzefIdj C7Hw==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:mime-version:references:in-reply-to:from:date :message-id:subject:to:cc; bh=zXEOD0b45ncjDXBP53Qwou/NUhaEu3y7y3+e87uytmQ=; b=YcOuEDki+5G3CB3WU+F4cSLoz0eXvpX5mTZBnaCOrO1M4YFjQcYBe6sjvorguAK5te VGAgaJO8EtTRP1JdDwKjwKFugPhWFnKBqRqfgJ5+zg0PdnPNyZIA1XdX4mP8BJzBIeUU AUsWmQBBUahiP5MRKnyLETKFp6EtI5Gko2Iog9ijc+1oH4UF2MWfnxadSIJKoMrSIHqd h9Zz8VPgnH22u7zhJJdY8waSsDn4BxIUDuk8SJ6V24Pm353lJZ68P9RSWM5V+K5v8Oh+ Cap28aHHarw8usFOtN/fXfqibejPc+VL5MIed+BN7Ah6bB4YhKlMHt79sutWrd8A1aqn DxgA==
X-Gm-Message-State: AOAM533v6PHUk1J7fqR22dyZ2Ynrny43ZeljBREcV50Y/uj4tMJy33E0 1RX3nf+lN8L2mrvMOl7OnaklfEpAJHobSVeXM6z1kqLBRiUkAlpF
X-Google-Smtp-Source: ABdhPJxgFHQq6JXRcL+phCatLU+v1SiwDbowvcbj2RIw2oVhCUixLBY2oKR6LmnS0qw741fmJY6ymiMtDLkju+YVgxk=
X-Received: by 2002:ac8:120a:: with SMTP id x10mr3141128qti.95.1603820950045;  Tue, 27 Oct 2020 10:49:10 -0700 (PDT)
MIME-Version: 1.0
References: <AM0PR08MB371647618F993B8C5BA6EB5FFA1C0@AM0PR08MB3716.eurprd08.prod.outlook.com> <AD94F3FF-31A7-4F44-95F7-6A7E70FA8D27@cisco.com> <CAOgPGoD3MQu=Hv6HTfug0XredaRt_T7oD7z_uwnATmHku9DmLg@mail.gmail.com> <AM0PR08MB371649BBA92B7F624008D0B3FA1A0@AM0PR08MB3716.eurprd08.prod.outlook.com>
In-Reply-To: <AM0PR08MB371649BBA92B7F624008D0B3FA1A0@AM0PR08MB3716.eurprd08.prod.outlook.com>
From: Joseph Salowey <joe@salowey.net>
Date: Tue, 27 Oct 2020 10:48:58 -0700
Message-ID: <CAOgPGoDaC893pAwfsEj5DNdKwd+z4_HmsOGZ2y8ruDs12Sx+kg@mail.gmail.com>
To: Hannes Tschofenig <Hannes.Tschofenig@arm.com>
Cc: Eliot Lear <lear=40cisco.com@dmarc.ietf.org>, "emu@ietf.org" <emu@ietf.org>
Content-Type: multipart/alternative; boundary="00000000000002e39d05b2aaaa11"
Archived-At: <https://mailarchive.ietf.org/arch/msg/emu/5DTjUppTPygGzwYkYZQTNdj8qkk>
Subject: Re: [Emu] draft-ietf-emu-eap-tls13-11: OCSP Stapling
X-BeenThere: emu@ietf.org
X-Mailman-Version: 2.1.29
Precedence: list
List-Id: "EAP Methods Update \(EMU\)" <emu.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/emu>, <mailto:emu-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/emu/>
List-Post: <mailto:emu@ietf.org>
List-Help: <mailto:emu-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/emu>, <mailto:emu-request@ietf.org?subject=subscribe>
X-List-Received-Date: Tue, 27 Oct 2020 17:49:21 -0000

--00000000000002e39d05b2aaaa11
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable

On Fri, Oct 23, 2020 at 12:38 AM Hannes Tschofenig <
Hannes.Tschofenig@arm.com> wrote:

> Hi Joe,
>
>
>
> I do not understand certificate revocation checking is a topic specific t=
o
> the use of TLS 1.3 in EAP-TLS.
>
>
>

[Joe]  TLS 1.3 discusses OCSP and (SCT).  OCSP stapling is a revocation
mechanism that will work when the EAP-TLS client does not have connectivity
yet, which is a common case in EAP-TLS deployments.    The way the draft is
written now it mandates that this mechanism be used and implements.  TLS
1.3 does not require this.


> If this topic is important to the group then why isn=E2=80=99t this a gen=
eric
> recommendations for all EAP methods that use public key based
> authentication?
>
>
>

[Joe] Certificate revocation is specific to the use of certificates.


> Wouldn=E2=80=99t this be a topic to address in <draft-ietf-emu-eaptlscert=
>? IMHO
> this would make more sense given that <draft-ietf-emu-eaptlscert> talks
> about large certificates and long certificate chains and any proposal to
> make those even larger should be evaluated in this context.
>
>
>

[Joe] No, <draft-ietf-emu-eaptlscert> discusses handling large certificates
not revocation.  EAP-TLS is the right place to discuss revocation issues.
It seems there are several questions that need to be answered:

1. Should the document mandate that OCSP stapling be used?
2. Should the document mandate that OCSP stapling be implemented?
3. What should the document say in the security sections with respect to
OCSP stapling and other mechanisms?







> Ciao
>
> Hannes
>
>
>
> *From:* Joseph Salowey <joe@salowey.net>
> *Sent:* Thursday, October 22, 2020 11:12 PM
> *To:* Eliot Lear <lear=3D40cisco.com@dmarc.ietf.org>
> *Cc:* Hannes Tschofenig <Hannes.Tschofenig@arm.com>; emu@ietf.org
> *Subject:* Re: [Emu] draft-ietf-emu-eap-tls13-11: OCSP Stapling
>
>
>
>
>
>
>
> On Thu, Oct 22, 2020 at 8:08 AM Eliot Lear <lear=3D
> 40cisco.com@dmarc.ietf.org> wrote:
>
> +1.  How does anyone even do OCSP without having first gotten onto the
> network?
>
>
>
>
>
> [Joe] THat is what OCSP stapling is supposed to solve since the OCSP
> messages are sent in the TLS handshake.   I believe there are some EAP-TL=
S
> implementations that support OCSP, but I am not sure if it is actually
> deployed.
>
>
>
> Eliot
>
>
>
> On 21 Oct 2020, at 11:02, Hannes Tschofenig <Hannes.Tschofenig@arm.com>
> wrote:
>
>
>
> Hi all,
>
>
>
> this draft mandates OCSCP stapling (for use with TLS 1.3 in EAP-TLS) and =
I
> believe this is a problem for implementations. This extra burden is IMHO
> unjustified. For the type of deployments where EAP is used there is no ne=
ed
> for a mandatory certificate revocation checking with OCSP.
>
>
>
> Having it optional, like the use of many other TLS extensions, is fine fo=
r
> me. FWIW even TLS 1.3, which is used in a more generic environment, does
> not mandate the use of OCSP stapling.
>
>
>
> This requirement will make the problem described in
> draft-ietf-emu-eaptlscert worse. I am sure the authors are aware of this
> fact since they are also co-authors of draft-ietf-emu-eaptlscert.
>
>
>
> Ciao
>
> Hannes
>
> IMPORTANT NOTICE: The contents of this email and any attachments are
> confidential and may also be privileged. If you are not the intended
> recipient, please notify the sender immediately and do not disclose the
> contents to any other person, use it for any purpose, or store or copy th=
e
> information in any medium. Thank you.
> _______________________________________________
> Emu mailing list
> Emu@ietf.org
> https://www.ietf.org/mailman/listinfo/emu
>
>
>
> _______________________________________________
> Emu mailing list
> Emu@ietf.org
> https://www.ietf.org/mailman/listinfo/emu
>
> IMPORTANT NOTICE: The contents of this email and any attachments are
> confidential and may also be privileged. If you are not the intended
> recipient, please notify the sender immediately and do not disclose the
> contents to any other person, use it for any purpose, or store or copy th=
e
> information in any medium. Thank you.
>

--00000000000002e39d05b2aaaa11
Content-Type: text/html; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable

<div dir=3D"ltr"><div dir=3D"ltr"><br></div><br><div class=3D"gmail_quote">=
<div dir=3D"ltr" class=3D"gmail_attr">On Fri, Oct 23, 2020 at 12:38 AM Hann=
es Tschofenig &lt;<a href=3D"mailto:Hannes.Tschofenig@arm.com">Hannes.Tscho=
fenig@arm.com</a>&gt; wrote:<br></div><blockquote class=3D"gmail_quote" sty=
le=3D"margin:0px 0px 0px 0.8ex;border-left:1px solid rgb(204,204,204);paddi=
ng-left:1ex">





<div lang=3D"EN-US">
<div class=3D"gmail-m_-2886452935219390257WordSection1">
<p class=3D"MsoNormal">Hi Joe, <u></u><u></u></p>
<p class=3D"MsoNormal"><u></u>=C2=A0<u></u></p>
<p class=3D"MsoNormal">I do not understand certificate revocation checking =
is a topic specific to the use of TLS 1.3 in EAP-TLS.
<u></u><u></u></p>
<p class=3D"MsoNormal"><u></u>=C2=A0</p></div></div></blockquote><div><br><=
/div><div>[Joe]=C2=A0 TLS 1.3 discusses=C2=A0OCSP and (SCT).=C2=A0 OCSP sta=
pling is a revocation mechanism that will work when the EAP-TLS client does=
 not have connectivity yet, which is a common case in EAP-TLS deployments.=
=C2=A0 =C2=A0 The way the draft is written now it mandates that this mechan=
ism be used and implements.=C2=A0 TLS 1.3 does not require this.=C2=A0=C2=
=A0</div><div>=C2=A0</div><blockquote class=3D"gmail_quote" style=3D"margin=
:0px 0px 0px 0.8ex;border-left:1px solid rgb(204,204,204);padding-left:1ex"=
><div lang=3D"EN-US"><div class=3D"gmail-m_-2886452935219390257WordSection1=
"><p class=3D"MsoNormal"><u></u></p>
<p class=3D"MsoNormal">If this topic is important to the group then why isn=
=E2=80=99t this a generic recommendations for all EAP methods that use publ=
ic key based authentication?
<u></u><u></u></p>
<p class=3D"MsoNormal"><u></u>=C2=A0</p></div></div></blockquote><div><br><=
/div><div>[Joe] Certificate revocation is specific to the use of certificat=
es.=C2=A0</div><div>=C2=A0</div><blockquote class=3D"gmail_quote" style=3D"=
margin:0px 0px 0px 0.8ex;border-left:1px solid rgb(204,204,204);padding-lef=
t:1ex"><div lang=3D"EN-US"><div class=3D"gmail-m_-2886452935219390257WordSe=
ction1"><p class=3D"MsoNormal"><u></u></p>
<p class=3D"MsoNormal">Wouldn=E2=80=99t this be a topic to address in &lt;d=
raft-ietf-emu-eaptlscert&gt;? IMHO this would make more sense given that &l=
t;draft-ietf-emu-eaptlscert&gt; talks about large certificates and long cer=
tificate chains and any proposal to make those even larger
 should be evaluated in this context. <u></u><u></u></p>
<p class=3D"MsoNormal"><u></u>=C2=A0</p></div></div></blockquote><div><br><=
/div><div>[Joe] No, &lt;draft-ietf-emu-eaptlscert&gt; discusses handling la=
rge certificates not revocation.=C2=A0 EAP-TLS is the right place to discus=
s revocation issues.=C2=A0 It seems there are several questions that need t=
o be answered:</div><div><br></div><div>1. Should the document mandate that=
 OCSP stapling=C2=A0be used?</div><div>2. Should the document mandate that =
OCSP stapling be implemented?</div><div>3. What should the document say in =
the security sections with respect to OCSP stapling and other mechanisms?=
=C2=A0</div><div><br></div><div><br></div><div><br></div><div><br></div><di=
v><br></div><div>=C2=A0</div><blockquote class=3D"gmail_quote" style=3D"mar=
gin:0px 0px 0px 0.8ex;border-left:1px solid rgb(204,204,204);padding-left:1=
ex"><div lang=3D"EN-US"><div class=3D"gmail-m_-2886452935219390257WordSecti=
on1"><p class=3D"MsoNormal"><u></u></p>
<p class=3D"MsoNormal">Ciao<u></u><u></u></p>
<p class=3D"MsoNormal">Hannes<u></u><u></u></p>
<p class=3D"MsoNormal"><u></u>=C2=A0<u></u></p>
<div style=3D"border-right:none;border-bottom:none;border-left:none;border-=
top:1pt solid rgb(225,225,225);padding:3pt 0in 0in">
<p class=3D"MsoNormal"><b>From:</b> Joseph Salowey &lt;<a href=3D"mailto:jo=
e@salowey.net" target=3D"_blank">joe@salowey.net</a>&gt; <br>
<b>Sent:</b> Thursday, October 22, 2020 11:12 PM<br>
<b>To:</b> Eliot Lear &lt;lear=3D<a href=3D"mailto:40cisco.com@dmarc.ietf.o=
rg" target=3D"_blank">40cisco.com@dmarc.ietf.org</a>&gt;<br>
<b>Cc:</b> Hannes Tschofenig &lt;<a href=3D"mailto:Hannes.Tschofenig@arm.co=
m" target=3D"_blank">Hannes.Tschofenig@arm.com</a>&gt;; <a href=3D"mailto:e=
mu@ietf.org" target=3D"_blank">emu@ietf.org</a><br>
<b>Subject:</b> Re: [Emu] draft-ietf-emu-eap-tls13-11: OCSP Stapling<u></u>=
<u></u></p>
</div>
<p class=3D"MsoNormal"><u></u>=C2=A0<u></u></p>
<div>
<div>
<p class=3D"MsoNormal"><u></u>=C2=A0<u></u></p>
</div>
<p class=3D"MsoNormal"><u></u>=C2=A0<u></u></p>
<div>
<div>
<p class=3D"MsoNormal">On Thu, Oct 22, 2020 at 8:08 AM Eliot Lear &lt;lear=
=3D<a href=3D"mailto:40cisco.com@dmarc.ietf.org" target=3D"_blank">40cisco.=
com@dmarc.ietf.org</a>&gt; wrote:<u></u><u></u></p>
</div>
<blockquote style=3D"border-top:none;border-right:none;border-bottom:none;b=
order-left:1pt solid rgb(204,204,204);padding:0in 0in 0in 6pt;margin-left:4=
.8pt;margin-right:0in">
<div>
<p class=3D"MsoNormal">+1.=C2=A0 How does anyone even do OCSP without havin=
g first gotten onto the network?<u></u><u></u></p>
<div>
<p class=3D"MsoNormal"><u></u>=C2=A0<u></u></p>
</div>
</div>
</blockquote>
<div>
<p class=3D"MsoNormal"><u></u>=C2=A0<u></u></p>
</div>
<div>
<p class=3D"MsoNormal">[Joe] THat is what OCSP stapling is supposed to solv=
e since the OCSP messages are sent in the TLS handshake.=C2=A0 =C2=A0I beli=
eve there are some EAP-TLS implementations that support OCSP, but I am not =
sure if it is actually deployed.=C2=A0=C2=A0<u></u><u></u></p>
</div>
<div>
<p class=3D"MsoNormal">=C2=A0<u></u><u></u></p>
</div>
<blockquote style=3D"border-top:none;border-right:none;border-bottom:none;b=
order-left:1pt solid rgb(204,204,204);padding:0in 0in 0in 6pt;margin-left:4=
.8pt;margin-right:0in">
<div>
<div>
<p class=3D"MsoNormal">Eliot<u></u><u></u></p>
</div>
<div>
<p class=3D"MsoNormal"><u></u>=C2=A0<u></u></p>
<div>
<blockquote style=3D"margin-top:5pt;margin-bottom:5pt">
<div>
<p class=3D"MsoNormal">On 21 Oct 2020, at 11:02, Hannes Tschofenig &lt;<a h=
ref=3D"mailto:Hannes.Tschofenig@arm.com" target=3D"_blank">Hannes.Tschofeni=
g@arm.com</a>&gt; wrote:<u></u><u></u></p>
</div>
<p class=3D"MsoNormal"><u></u>=C2=A0<u></u></p>
<div>
<div>
<div>
<p class=3D"MsoNormal">Hi all,=C2=A0<u></u><u></u></p>
</div>
<div>
<p class=3D"MsoNormal">=C2=A0<u></u><u></u></p>
</div>
<div>
<p class=3D"MsoNormal">this draft mandates OCSCP stapling (for use with TLS=
 1.3 in EAP-TLS) and I believe this is a problem for implementations. This =
extra burden is IMHO unjustified. For the type of deployments where EAP is =
used there is no need for a mandatory
 certificate revocation checking with OCSP.<u></u><u></u></p>
</div>
<div>
<p class=3D"MsoNormal">=C2=A0<u></u><u></u></p>
</div>
<div>
<p class=3D"MsoNormal">Having it optional, like the use of many other TLS e=
xtensions, is fine for me. FWIW even TLS 1.3, which is used in a more gener=
ic environment, does not mandate the use of OCSP stapling.<u></u><u></u></p=
>
</div>
<div>
<p class=3D"MsoNormal">=C2=A0<u></u><u></u></p>
</div>
<div>
<p class=3D"MsoNormal">This requirement will make the problem described in =
draft-ietf-emu-eaptlscert worse. I am sure the authors are aware of this fa=
ct since they are also co-authors of draft-ietf-emu-eaptlscert.<u></u><u></=
u></p>
</div>
<div>
<p class=3D"MsoNormal">=C2=A0<u></u><u></u></p>
</div>
<div>
<p class=3D"MsoNormal">Ciao<u></u><u></u></p>
</div>
<div>
<p class=3D"MsoNormal">Hannes<u></u><u></u></p>
</div>
</div>
<p class=3D"MsoNormal"><span style=3D"font-size:12pt;font-family:Helvetica,=
sans-serif">IMPORTANT NOTICE: The contents of this email and any attachment=
s are confidential and may also be privileged. If you are not the intended =
recipient, please notify the sender
 immediately and do not disclose the contents to any other person, use it f=
or any purpose, or store or copy the information in any medium. Thank you. =
_______________________________________________<br>
Emu mailing list<br>
</span><a href=3D"mailto:Emu@ietf.org" target=3D"_blank"><span style=3D"fon=
t-size:12pt;font-family:Helvetica,sans-serif">Emu@ietf.org</span></a><span =
style=3D"font-size:12pt;font-family:Helvetica,sans-serif"><br>
</span><a href=3D"https://www.ietf.org/mailman/listinfo/emu" target=3D"_bla=
nk"><span style=3D"font-size:12pt;font-family:Helvetica,sans-serif">https:/=
/www.ietf.org/mailman/listinfo/emu</span></a><u></u><u></u></p>
</div>
</blockquote>
</div>
<p class=3D"MsoNormal"><u></u>=C2=A0<u></u></p>
</div>
</div>
<p class=3D"MsoNormal">_______________________________________________<br>
Emu mailing list<br>
<a href=3D"mailto:Emu@ietf.org" target=3D"_blank">Emu@ietf.org</a><br>
<a href=3D"https://www.ietf.org/mailman/listinfo/emu" target=3D"_blank">htt=
ps://www.ietf.org/mailman/listinfo/emu</a><u></u><u></u></p>
</blockquote>
</div>
</div>
</div>
IMPORTANT NOTICE: The contents of this email and any attachments are confid=
ential and may also be privileged. If you are not the intended recipient, p=
lease notify the sender immediately and do not disclose the contents to any=
 other person, use it for any purpose,
 or store or copy the information in any medium. Thank you.
</div>

</blockquote></div></div>

--00000000000002e39d05b2aaaa11--


From nobody Tue Oct 27 11:27:30 2020
Return-Path: <Hannes.Tschofenig@arm.com>
X-Original-To: emu@ietfa.amsl.com
Delivered-To: emu@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 8EED43A148A for <emu@ietfa.amsl.com>; Tue, 27 Oct 2020 11:27:23 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.899
X-Spam-Level: 
X-Spam-Status: No, score=-1.899 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, HTML_MESSAGE=0.001, RCVD_IN_MSPIKE_H2=-0.001, SPF_PASS=-0.001, UNPARSEABLE_RELAY=0.001, URIBL_BLOCKED=0.001] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (1024-bit key) header.d=armh.onmicrosoft.com header.b=Gvr5fxEv; dkim=pass (1024-bit key) header.d=armh.onmicrosoft.com header.b=Gvr5fxEv
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 g0LYD49igsJG for <emu@ietfa.amsl.com>; Tue, 27 Oct 2020 11:27:19 -0700 (PDT)
Received: from EUR03-VE1-obe.outbound.protection.outlook.com (mail-eopbgr50078.outbound.protection.outlook.com [40.107.5.78]) (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 1907A3A1453 for <emu@ietf.org>; Tue, 27 Oct 2020 11:27:18 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=armh.onmicrosoft.com;  s=selector2-armh-onmicrosoft-com; h=From:Date:Subject:Message-ID:Content-Type:MIME-Version:X-MS-Exchange-SenderADCheck; bh=0/R9xpoEoA+idCr8Ye2AAgqyUEUyDNCXqkPhgAwugk4=; b=Gvr5fxEvBgeFF9vdv5FvXw5CvlS90eUYE90ZM/qEXb0WFIFGwxxvRuYkVpWdw7JQy80qyecBoh2KxQdqrW5Qq9veKPwA8XLL1zrmP3bVyfN9RX40DBzJM4AwbfNIRVp9qHILCmQv+EfSFljiCABHIkHnasJ7DohE5OfJjol2GxI=
Received: from DB6P192CA0002.EURP192.PROD.OUTLOOK.COM (2603:10a6:4:b8::12) by AM6PR08MB4103.eurprd08.prod.outlook.com (2603:10a6:20b:a4::14) with Microsoft SMTP Server (version=TLS1_2, cipher=TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384) id 15.20.3477.27; Tue, 27 Oct 2020 18:27:15 +0000
Received: from DB5EUR03FT055.eop-EUR03.prod.protection.outlook.com (2603:10a6:4:b8:cafe::b8) by DB6P192CA0002.outlook.office365.com (2603:10a6:4:b8::12) with Microsoft SMTP Server (version=TLS1_2, cipher=TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384) id 15.20.3499.18 via Frontend Transport; Tue, 27 Oct 2020 18:27:15 +0000
X-MS-Exchange-Authentication-Results: spf=pass (sender IP is 63.35.35.123) smtp.mailfrom=arm.com; ietf.org; dkim=pass (signature was verified) header.d=armh.onmicrosoft.com;ietf.org; dmarc=pass action=none header.from=arm.com;
Received-SPF: Pass (protection.outlook.com: domain of arm.com designates 63.35.35.123 as permitted sender) receiver=protection.outlook.com; client-ip=63.35.35.123; helo=64aa7808-outbound-1.mta.getcheckrecipient.com;
Received: from 64aa7808-outbound-1.mta.getcheckrecipient.com (63.35.35.123) by DB5EUR03FT055.mail.protection.outlook.com (10.152.21.30) with Microsoft SMTP Server (version=TLS1_2, cipher=TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384) id 15.20.3499.18 via Frontend Transport; Tue, 27 Oct 2020 18:27:15 +0000
Received: ("Tessian outbound d5e343850048:v64"); Tue, 27 Oct 2020 18:27:15 +0000
X-CR-MTA-TID: 64aa7808
Received: from b5a72be682c5.1 by 64aa7808-outbound-1.mta.getcheckrecipient.com id DEC6C8E7-271B-487E-B495-2AFE6477F7E2.1;  Tue, 27 Oct 2020 18:27:10 +0000
Received: from EUR05-VI1-obe.outbound.protection.outlook.com by 64aa7808-outbound-1.mta.getcheckrecipient.com with ESMTPS id b5a72be682c5.1 (version=TLSv1.2 cipher=ECDHE-RSA-AES256-GCM-SHA384); Tue, 27 Oct 2020 18:27:10 +0000
ARC-Seal: i=1; a=rsa-sha256; s=arcselector9901; d=microsoft.com; cv=none; b=Fh+yljmfbMc3Iv+iBi8UuUB2PeGatceycvUPaMygLYQUqD6soPLIQElVfnxZ/NH8gpBfhakJqJDWYlNgUSLznx/BscwfY6s/1xQGps6Rbam5r7BeI1TMJEUf5EwiHvMC0DjVeyEDXbFSe70Sbh8YfADIJDPOfVWlYPCpELwRDZQ3uZfkd1NxCv6KtIK8ObrbugB2ef7+gutXhih4GEHVwkRaSDJfKAV73iYRIwddR6ifIQgfhMsK9EzwMWTkpklOMCANtfiR2KInawJhGtGv5jK/Jugx2RkYHaSErJ4PpqXsE+vRRe0yamiy8mCAWSdPYcj8tAx+bj9XIrklYHROyw==
ARC-Message-Signature: i=1; a=rsa-sha256; c=relaxed/relaxed; d=microsoft.com;  s=arcselector9901; h=From:Date:Subject:Message-ID:Content-Type:MIME-Version:X-MS-Exchange-SenderADCheck; bh=0/R9xpoEoA+idCr8Ye2AAgqyUEUyDNCXqkPhgAwugk4=; b=F0HdrwDeQvuxe9BPaltFPqRWARyJgpon0S6EQz1gDre4ZK+CvBg0SymJXcIjg3Rbxd5z94I+rcXKJaFHBw2UgogAy+hcOmXSCJd+XKMBl23FKlMzkda6nSixfcubw7g8/wPPU7kHxw9WXgfEDhb4+tOLj0Qi7D5Zzh39w+G7tVIahGZsBwMzOPfQvC5wSOfrHWulxDGqZf9xb7xzDdAqTRLF5LoH8AupZ+bwVf209XhIYl3JsJYS1U8xDUXEV8N7wscJAQWAR7AhsJaJSsS0GOekf0sRFrFI8lwPHgpO2uv8OnM3325t1yPqVwa1Hu5mSp06buwsud3HC9Qw/7sXGw==
ARC-Authentication-Results: i=1; mx.microsoft.com 1; spf=pass smtp.mailfrom=arm.com; dmarc=pass action=none header.from=arm.com; dkim=pass header.d=arm.com; arc=none
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=armh.onmicrosoft.com;  s=selector2-armh-onmicrosoft-com; h=From:Date:Subject:Message-ID:Content-Type:MIME-Version:X-MS-Exchange-SenderADCheck; bh=0/R9xpoEoA+idCr8Ye2AAgqyUEUyDNCXqkPhgAwugk4=; b=Gvr5fxEvBgeFF9vdv5FvXw5CvlS90eUYE90ZM/qEXb0WFIFGwxxvRuYkVpWdw7JQy80qyecBoh2KxQdqrW5Qq9veKPwA8XLL1zrmP3bVyfN9RX40DBzJM4AwbfNIRVp9qHILCmQv+EfSFljiCABHIkHnasJ7DohE5OfJjol2GxI=
Received: from AM0PR08MB3716.eurprd08.prod.outlook.com (2603:10a6:208:106::13) by AM0PR08MB2945.eurprd08.prod.outlook.com (2603:10a6:208:63::29) with Microsoft SMTP Server (version=TLS1_2, cipher=TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384) id 15.20.3477.25; Tue, 27 Oct 2020 18:27:08 +0000
Received: from AM0PR08MB3716.eurprd08.prod.outlook.com ([fe80::900e:c64d:a006:4860]) by AM0PR08MB3716.eurprd08.prod.outlook.com ([fe80::900e:c64d:a006:4860%6]) with mapi id 15.20.3455.037; Tue, 27 Oct 2020 18:27:08 +0000
From: Hannes Tschofenig <Hannes.Tschofenig@arm.com>
To: Joseph Salowey <joe@salowey.net>
CC: Eliot Lear <lear=40cisco.com@dmarc.ietf.org>, "emu@ietf.org" <emu@ietf.org>
Thread-Topic: [Emu] draft-ietf-emu-eap-tls13-11: OCSP Stapling
Thread-Index: AdaniLvyfaHHD0ANRluj1nshuTAidQA/HNCAAAyz4QAAFaqz0ADesioAAACtSIA=
Date: Tue, 27 Oct 2020 18:27:07 +0000
Message-ID: <AM0PR08MB3716466445022163A7C624AAFA160@AM0PR08MB3716.eurprd08.prod.outlook.com>
References: <AM0PR08MB371647618F993B8C5BA6EB5FFA1C0@AM0PR08MB3716.eurprd08.prod.outlook.com> <AD94F3FF-31A7-4F44-95F7-6A7E70FA8D27@cisco.com> <CAOgPGoD3MQu=Hv6HTfug0XredaRt_T7oD7z_uwnATmHku9DmLg@mail.gmail.com> <AM0PR08MB371649BBA92B7F624008D0B3FA1A0@AM0PR08MB3716.eurprd08.prod.outlook.com> <CAOgPGoDaC893pAwfsEj5DNdKwd+z4_HmsOGZ2y8ruDs12Sx+kg@mail.gmail.com>
In-Reply-To: <CAOgPGoDaC893pAwfsEj5DNdKwd+z4_HmsOGZ2y8ruDs12Sx+kg@mail.gmail.com>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
x-ts-tracking-id: 9753B50B53BFF14089BA3EA289CF84D1.0
x-checkrecipientchecked: true
Authentication-Results-Original: salowey.net; dkim=none (message not signed) header.d=none;salowey.net; dmarc=none action=none header.from=arm.com;
x-originating-ip: [80.92.116.60]
x-ms-publictraffictype: Email
X-MS-Office365-Filtering-HT: Tenant
X-MS-Office365-Filtering-Correlation-Id: 0adbde7c-5ca9-4e94-d711-08d87aa5ee0c
x-ms-traffictypediagnostic: AM0PR08MB2945:|AM6PR08MB4103:
X-Microsoft-Antispam-PRVS: <AM6PR08MB4103F147EFE9F16E4E5E0CCDFA160@AM6PR08MB4103.eurprd08.prod.outlook.com>
x-checkrecipientrouted: true
nodisclaimer: true
x-ms-oob-tlc-oobclassifiers: OLM:9508;OLM:9508;
X-MS-Exchange-SenderADCheck: 1
X-Microsoft-Antispam-Untrusted: BCL:0;
X-Microsoft-Antispam-Message-Info-Original: vUDwF4brZfuWABrHXtO0lh0TQSOYprN2KemmTQGQGMSagd8aSfpvCNDDOKbtnfq8+l2bD6LBhtd8kJcvPd42Cjr8DcKSAW+aLfhWtjO2l7bSF2tcQMtoza7B6fJOZXJlEfF8sCeZ5Bi7m0wLaosuVCeQ4K3Q7RX0YfUwk4a672BLa+GfeFvwnrVUcgIzMHVT7+N1zyv+Jt9WtLhDVJlxSO2lyrzo4HJYn+WXYMYJp90I/ivOX2MleHUClFYHTXiN42exT4S5RgZi+Yl75vXP2PYVFXBsFvh8nFXeAza/NYC5rX8I2Vab/14EedPhCsgHLN1kf81wkSHuz+eMgjtx47xxEXlpYqM6O7Eyc/9Hcd0ycPEJ65mpCzSqCk9bD1LiIpvInI/auHWRMeil/J5u8Q==
X-Forefront-Antispam-Report-Untrusted: CIP:255.255.255.255; CTRY:; LANG:en; SCL:1; SRV:; IPV:NLI; SFV:NSPM; H:AM0PR08MB3716.eurprd08.prod.outlook.com; PTR:; CAT:NONE; SFS:(4636009)(346002)(376002)(39850400004)(136003)(396003)(366004)(33656002)(186003)(26005)(6916009)(71200400001)(2906002)(66476007)(76116006)(9686003)(66556008)(66946007)(316002)(52536014)(8676002)(9326002)(86362001)(166002)(54906003)(8936002)(64756008)(83380400001)(478600001)(6506007)(7696005)(966005)(4326008)(53546011)(66446008)(5660300002)(55016002); DIR:OUT; SFP:1101; 
x-ms-exchange-antispam-messagedata: mbwtb+3fPbmEJA68jVgjRtyCmWqRSExlVn+Lk5HieqkSpfQ13wiSgwjMivKOvPIlrHXycNMP/15jLcjef46iwVrLOhyuXHEdDEHJwcWPcExtxlpKtKWZvoDdo9E1WMFYZ21bbD925hB6TkYQPCNTEqFvMA3vz778vlY9O68LHMKbmaJEunM2eI9LWZ1eKzcCpG/8dg1XiEKI82o7ZkbVoF7wxDGH6c/ScXIvbjcGu8cCSe09Ko9whn/2URhnMMPQix3DAWwIovtaxqijOFQq8T1Mr45GraaKLvYYvgOVgQVMRkbHWMFXuo4AfIjBcB3589nOq6oETZ3dtbgdbVnPomBr2UuwXUpyhwuD+WQ6zaBrhJccdHHjS9JAmukKp2PT8H7Ue+H3IHI5enuK4pKihbGf5p7bnY/TdRbXRUU4qYoD//IR3ZOgPVRNEBWLT1G1RYniu28OjGKwwXic0xKyGTdAg9ACAEcjjjm3qB789SzZ2OSRHHDTS0gorKjO4qkXOHDIqH/sjpwoPpPglQZDzsfUVHFieKZSs9II7cbdYvlO7tmquZYa8H9NbRpf3OZzqownXqQDD4xczoDafxSksmpYEBlc43/gko/jjGepn6HZjXePeKR0vsodgzyDxXZmgZ560/X+DUi2CvDQMsrgOQ==
x-ms-exchange-transport-forked: True
Content-Type: multipart/alternative; boundary="_000_AM0PR08MB3716466445022163A7C624AAFA160AM0PR08MB3716eurp_"
MIME-Version: 1.0
X-MS-Exchange-Transport-CrossTenantHeadersStamped: AM0PR08MB2945
Original-Authentication-Results: salowey.net; dkim=none (message not signed) header.d=none;salowey.net; dmarc=none action=none header.from=arm.com;
X-EOPAttributedMessage: 0
X-MS-Exchange-Transport-CrossTenantHeadersStripped: DB5EUR03FT055.eop-EUR03.prod.protection.outlook.com
X-MS-Office365-Filtering-Correlation-Id-Prvs: 141895e9-7af2-4e5a-9194-08d87aa5e998
X-Microsoft-Antispam: BCL:0;
X-Microsoft-Antispam-Message-Info: cnY8VJQ38IHqRaiN3rPMGDrIs+zgUh3kRyKB1VlLj6bUfOsebPsnkK6YZklwppElS9dGzGUqByv8AoYGxtx5UaKQkFUOA+D4MWQOqJoUoO4eX+lbOHe901UCaaaxj53BB5zcizUmmkgG5zvxZW4zFOwNyabjC1XIgBfzspjv/BF6p6NR3EO86n1R6YCXNBPm9GEJvertaLYXIrszoFyjwj5tVO09wVDwt20D2EIGcvkPA/5TuPOvDbCZ/vwMBuPme9y3uqeegNrIeJbaYAcE3F2ACLFwwdIGSUqMKnb53peQGQ4OHQLfONTv1PzOmI4moJzuhzb1MAXnGtUK5GzRhYNBa3DA36csNqnuI+PRA7EmqnaorEx2+wwKAlp8wclWSBi8/zmV2s942piAVyburmfledZJJYYHt4vawfJ+JZVog09xtX5tc+00YHnhQNn666xcPemJwm2l0fEYjnX3rZhQmafS3KN3bMukuPydPIg=
X-Forefront-Antispam-Report: CIP:63.35.35.123; CTRY:IE; LANG:en; SCL:1; SRV:;  IPV:CAL; SFV:NSPM; H:64aa7808-outbound-1.mta.getcheckrecipient.com;  PTR:ec2-63-35-35-123.eu-west-1.compute.amazonaws.com; CAT:NONE; SFS:(4636009)(39850400004)(346002)(376002)(396003)(136003)(46966005)(316002)(4326008)(54906003)(33656002)(9686003)(83380400001)(53546011)(82740400003)(356005)(7696005)(47076004)(81166007)(166002)(55016002)(336012)(33964004)(6506007)(186003)(26005)(8936002)(9326002)(86362001)(70206006)(82310400003)(6862004)(52536014)(70586007)(478600001)(5660300002)(966005)(2906002)(30864003)(8676002); DIR:OUT; SFP:1101; 
X-OriginatorOrg: arm.com
X-MS-Exchange-CrossTenant-OriginalArrivalTime: 27 Oct 2020 18:27:15.4856 (UTC)
X-MS-Exchange-CrossTenant-Network-Message-Id: 0adbde7c-5ca9-4e94-d711-08d87aa5ee0c
X-MS-Exchange-CrossTenant-Id: f34e5979-57d9-4aaa-ad4d-b122a662184d
X-MS-Exchange-CrossTenant-OriginalAttributedTenantConnectingIp: TenantId=f34e5979-57d9-4aaa-ad4d-b122a662184d; Ip=[63.35.35.123];  Helo=[64aa7808-outbound-1.mta.getcheckrecipient.com]
X-MS-Exchange-CrossTenant-AuthSource: DB5EUR03FT055.eop-EUR03.prod.protection.outlook.com
X-MS-Exchange-CrossTenant-AuthAs: Anonymous
X-MS-Exchange-CrossTenant-FromEntityHeader: HybridOnPrem
X-MS-Exchange-Transport-CrossTenantHeadersStamped: AM6PR08MB4103
Archived-At: <https://mailarchive.ietf.org/arch/msg/emu/aqx3Xdf6A2yxZM8Dclrs2PAbRa0>
Subject: Re: [Emu] draft-ietf-emu-eap-tls13-11: OCSP Stapling
X-BeenThere: emu@ietf.org
X-Mailman-Version: 2.1.29
Precedence: list
List-Id: "EAP Methods Update \(EMU\)" <emu.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/emu>, <mailto:emu-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/emu/>
List-Post: <mailto:emu@ietf.org>
List-Help: <mailto:emu-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/emu>, <mailto:emu-request@ietf.org?subject=subscribe>
X-List-Received-Date: Tue, 27 Oct 2020 18:27:30 -0000

--_000_AM0PR08MB3716466445022163A7C624AAFA160AM0PR08MB3716eurp_
Content-Type: text/plain; charset="utf-8"
Content-Transfer-Encoding: base64

SGkgSm9lLA0KDQphIGZldyByZW1hcmtzIGJlbG93Lg0KDQoNCk9uIEZyaSwgT2N0IDIzLCAyMDIw
IGF0IDEyOjM4IEFNIEhhbm5lcyBUc2Nob2ZlbmlnIDxIYW5uZXMuVHNjaG9mZW5pZ0Bhcm0uY29t
PG1haWx0bzpIYW5uZXMuVHNjaG9mZW5pZ0Bhcm0uY29tPj4gd3JvdGU6DQpIaSBKb2UsDQoNCkkg
ZG8gbm90IHVuZGVyc3RhbmQgY2VydGlmaWNhdGUgcmV2b2NhdGlvbiBjaGVja2luZyBpcyBhIHRv
cGljIHNwZWNpZmljIHRvIHRoZSB1c2Ugb2YgVExTIDEuMyBpbiBFQVAtVExTLg0KDQpbSm9lXSAg
VExTIDEuMyBkaXNjdXNzZXMgT0NTUCBhbmQgKFNDVCkuICBPQ1NQIHN0YXBsaW5nIGlzIGEgcmV2
b2NhdGlvbiBtZWNoYW5pc20gdGhhdCB3aWxsIHdvcmsgd2hlbiB0aGUgRUFQLVRMUyBjbGllbnQg
ZG9lcyBub3QgaGF2ZSBjb25uZWN0aXZpdHkgeWV0LCB3aGljaCBpcyBhIGNvbW1vbiBjYXNlIGlu
IEVBUC1UTFMgZGVwbG95bWVudHMuICAgIFRoZSB3YXkgdGhlIGRyYWZ0IGlzIHdyaXR0ZW4gbm93
IGl0IG1hbmRhdGVzIHRoYXQgdGhpcyBtZWNoYW5pc20gYmUgdXNlZCBhbmQgaW1wbGVtZW50cy4g
IFRMUyAxLjMgZG9lcyBub3QgcmVxdWlyZSB0aGlzLg0KDQpbaGFubmVzXSBJdCBpcyBhbHNvIGNv
bW1vbiB0byBnaXZlIG5ldHdvcmsgYWNjZXNzIHRvIGRldmljZXMgdGhhdCBuZWVkIGEgc29mdHdh
cmUgdXBkYXRlIG9yIGNvbmZpZ3VyYXRpb24gY2hhbmdlcy4NCg0KV2hhdCBkbyB5b3UgZXhwZWN0
IHRvIGhhcHBlbiBpZiB0aGUgZGV2aWNlIGZpbmRzIG91dCB0aGF0IHRoZSBjZXJ0aWZpY2F0ZSBv
ZmZlcmVkIGJ5IHRoZSBzZXJ2ZXIgaGFzIGV4cGlyZWQ/DQoNCg0KSWYgdGhpcyB0b3BpYyBpcyBp
bXBvcnRhbnQgdG8gdGhlIGdyb3VwIHRoZW4gd2h5IGlzbuKAmXQgdGhpcyBhIGdlbmVyaWMgcmVj
b21tZW5kYXRpb25zIGZvciBhbGwgRUFQIG1ldGhvZHMgdGhhdCB1c2UgcHVibGljIGtleSBiYXNl
ZCBhdXRoZW50aWNhdGlvbj8NCg0KDQpbSm9lXSBDZXJ0aWZpY2F0ZSByZXZvY2F0aW9uIGlzIHNw
ZWNpZmljIHRvIHRoZSB1c2Ugb2YgY2VydGlmaWNhdGVzLg0KDQpbSGFubmVzXSBNYW55IEVBUCBt
ZXRob2RzIHVzZSBjZXJ0aWZpY2F0ZXMgYnV0IHRoZXkgZG8gbm90IG1hbmRhdGUgdGhlIHVzZSBv
ZiBPQ1NQLg0KDQpXb3VsZG7igJl0IHRoaXMgYmUgYSB0b3BpYyB0byBhZGRyZXNzIGluIDxkcmFm
dC1pZXRmLWVtdS1lYXB0bHNjZXJ0Pj8gSU1ITyB0aGlzIHdvdWxkIG1ha2UgbW9yZSBzZW5zZSBn
aXZlbiB0aGF0IDxkcmFmdC1pZXRmLWVtdS1lYXB0bHNjZXJ0PiB0YWxrcyBhYm91dCBsYXJnZSBj
ZXJ0aWZpY2F0ZXMgYW5kIGxvbmcgY2VydGlmaWNhdGUgY2hhaW5zIGFuZCBhbnkgcHJvcG9zYWwg
dG8gbWFrZSB0aG9zZSBldmVuIGxhcmdlciBzaG91bGQgYmUgZXZhbHVhdGVkIGluIHRoaXMgY29u
dGV4dC4NCg0KDQpbSm9lXSBObywgPGRyYWZ0LWlldGYtZW11LWVhcHRsc2NlcnQ+IGRpc2N1c3Nl
cyBoYW5kbGluZyBsYXJnZSBjZXJ0aWZpY2F0ZXMgbm90IHJldm9jYXRpb24uDQoNCltIYW5uZXNd
IEhlcmUgdGhlIHByb2JsZW0gZGVzY3JpcHRpb24gdGhhdCBtb3RpdmF0ZXMgPGRyYWZ0LWlldGYt
ZW11LWVhcHRsc2NlcnQ+DQrigJwNCkxhcmdlIGNlcnRpZmljYXRlcyBhbmQgbG9uZw0KICAgY2Vy
dGlmaWNhdGUgY2hhaW5zIGNvbWJpbmVkIHdpdGggYXV0aGVudGljYXRvcnMgdGhhdCBkcm9wIGFu
IEVBUA0KICAgc2Vzc2lvbiBhZnRlciBvbmx5IDQwIC0gNTAgcm91bmQtdHJpcHMgaXMgYSBtYWpv
ciBkZXBsb3ltZW50IHByb2JsZW0uDQogICBUaGlzIGRvY3VtZW50IGxvb2tzIGF0IHRoZSB0aGlz
IHByb2JsZW0gaW4gZGV0YWlsIGFuZCBkZXNjcmliZXMgdGhlDQogICBwb3RlbnRpYWwgc29sdXRp
b25zIGF2YWlsYWJsZS4NCuKAnA0KT0NTUCBpbmZvcm1hdGlvbiB0cmF2ZWxzIGFsb25nc2lkZSB0
aGUgY2VydGlmaWNhdGVzIGFuZCB0aGVyZWZvcmUgaW5jcmVhc2VzIHRoZSBwcm9ibGVtIG91dGxp
bmVkIGJ5IDxkcmFmdC1pZXRmLWVtdS1lYXB0bHNjZXJ0Pg0KDQpFQVAtVExTIGlzIHRoZSByaWdo
dCBwbGFjZSB0byBkaXNjdXNzIHJldm9jYXRpb24gaXNzdWVzLg0KDQpJdCBzZWVtcyB0aGVyZSBh
cmUgc2V2ZXJhbCBxdWVzdGlvbnMgdGhhdCBuZWVkIHRvIGJlIGFuc3dlcmVkOg0KDQoNCiAgMS4g
IFNob3VsZCB0aGUgZG9jdW1lbnQgbWFuZGF0ZSB0aGF0IE9DU1Agc3RhcGxpbmcgYmUgdXNlZD8N
CltIYW5uZXNdIE5vLg0KDQoyLiBTaG91bGQgdGhlIGRvY3VtZW50IG1hbmRhdGUgdGhhdCBPQ1NQ
IHN0YXBsaW5nIGJlIGltcGxlbWVudGVkPw0KW0hhbm5lc10gTm8uDQoNCjMuIFdoYXQgc2hvdWxk
IHRoZSBkb2N1bWVudCBzYXkgaW4gdGhlIHNlY3VyaXR5IHNlY3Rpb25zIHdpdGggcmVzcGVjdCB0
byBPQ1NQIHN0YXBsaW5nIGFuZCBvdGhlciBtZWNoYW5pc21zPw0KW0hhbm5lc10gSU1ITyBUTFMg
MS4zIHNheXMgdGhlIHJlbGV2YW50IHNvbHV0aW9uIHBhcnRzLiBPQ1NQIHN0YXBsaW5nIGlzIGF2
YWlsYWJsZSBmb3IgdXNlIGluIFRMUyAxLjMgYW5kIGl0IGlzIG9uZSBzdWl0YWJsZSBtZWNoYW5p
c20gZm9yIGNlcnRpZmljYXRlIHJldm9jYXRpb24uDQoNCkRvIGFueSBvZiB0aGVzZSByZWNvbW1l
bmRhdGlvbnMgYWxzbyBhcHBseSB0byBFQVAtVExTIHdpdGggVExTIDEuMiBhcyB3ZWxsIChzaW5j
ZSBpdCBhbHNvIG9mZmVycyBPQ1NQIHN0YXBsaW5nKT8gV291bGQgdGhlIHJlY29tbWVuZGF0aW9u
cyBhbHNvIGFwcGx5IHRvIEVBUCBtZXRob2RzIHRoYXQgdXNlIFRMUyB1bmRlciB0aGUgaG9vZCwg
c3VjaCBhcyBURUFQLCBFQVAtRkFTVCwgb3IgRUFQLVRUTFM/IFdvdWxkIHRoZXkgYXBwbHkgdG8g
bWV0aG9kcyBsaWtlIEVBUC1JS0V2MiBvciB0aGUgcmVjZW50bHkgc3VnZ2VzdGVkIEVBUC1FREhP
Qywgd2hpY2ggYXJlIGFsc28gbWV0aG9kcyB0aGF0IHVzZSBjZXJ0aWZpY2F0ZXM/DQoNCkNpYW8N
Ckhhbm5lcw0KDQpDaWFvDQpIYW5uZXMNCg0KRnJvbTogSm9zZXBoIFNhbG93ZXkgPGpvZUBzYWxv
d2V5Lm5ldDxtYWlsdG86am9lQHNhbG93ZXkubmV0Pj4NClNlbnQ6IFRodXJzZGF5LCBPY3RvYmVy
IDIyLCAyMDIwIDExOjEyIFBNDQpUbzogRWxpb3QgTGVhciA8bGVhcj00MGNpc2NvLmNvbUBkbWFy
Yy5pZXRmLm9yZzxtYWlsdG86NDBjaXNjby5jb21AZG1hcmMuaWV0Zi5vcmc+Pg0KQ2M6IEhhbm5l
cyBUc2Nob2ZlbmlnIDxIYW5uZXMuVHNjaG9mZW5pZ0Bhcm0uY29tPG1haWx0bzpIYW5uZXMuVHNj
aG9mZW5pZ0Bhcm0uY29tPj47IGVtdUBpZXRmLm9yZzxtYWlsdG86ZW11QGlldGYub3JnPg0KU3Vi
amVjdDogUmU6IFtFbXVdIGRyYWZ0LWlldGYtZW11LWVhcC10bHMxMy0xMTogT0NTUCBTdGFwbGlu
Zw0KDQoNCg0KT24gVGh1LCBPY3QgMjIsIDIwMjAgYXQgODowOCBBTSBFbGlvdCBMZWFyIDxsZWFy
PTQwY2lzY28uY29tQGRtYXJjLmlldGYub3JnPG1haWx0bzo0MGNpc2NvLmNvbUBkbWFyYy5pZXRm
Lm9yZz4+IHdyb3RlOg0KKzEuICBIb3cgZG9lcyBhbnlvbmUgZXZlbiBkbyBPQ1NQIHdpdGhvdXQg
aGF2aW5nIGZpcnN0IGdvdHRlbiBvbnRvIHRoZSBuZXR3b3JrPw0KDQoNCltKb2VdIFRIYXQgaXMg
d2hhdCBPQ1NQIHN0YXBsaW5nIGlzIHN1cHBvc2VkIHRvIHNvbHZlIHNpbmNlIHRoZSBPQ1NQIG1l
c3NhZ2VzIGFyZSBzZW50IGluIHRoZSBUTFMgaGFuZHNoYWtlLiAgIEkgYmVsaWV2ZSB0aGVyZSBh
cmUgc29tZSBFQVAtVExTIGltcGxlbWVudGF0aW9ucyB0aGF0IHN1cHBvcnQgT0NTUCwgYnV0IEkg
YW0gbm90IHN1cmUgaWYgaXQgaXMgYWN0dWFsbHkgZGVwbG95ZWQuDQoNCkVsaW90DQoNCk9uIDIx
IE9jdCAyMDIwLCBhdCAxMTowMiwgSGFubmVzIFRzY2hvZmVuaWcgPEhhbm5lcy5Uc2Nob2Zlbmln
QGFybS5jb208bWFpbHRvOkhhbm5lcy5Uc2Nob2ZlbmlnQGFybS5jb20+PiB3cm90ZToNCg0KSGkg
YWxsLA0KDQp0aGlzIGRyYWZ0IG1hbmRhdGVzIE9DU0NQIHN0YXBsaW5nIChmb3IgdXNlIHdpdGgg
VExTIDEuMyBpbiBFQVAtVExTKSBhbmQgSSBiZWxpZXZlIHRoaXMgaXMgYSBwcm9ibGVtIGZvciBp
bXBsZW1lbnRhdGlvbnMuIFRoaXMgZXh0cmEgYnVyZGVuIGlzIElNSE8gdW5qdXN0aWZpZWQuIEZv
ciB0aGUgdHlwZSBvZiBkZXBsb3ltZW50cyB3aGVyZSBFQVAgaXMgdXNlZCB0aGVyZSBpcyBubyBu
ZWVkIGZvciBhIG1hbmRhdG9yeSBjZXJ0aWZpY2F0ZSByZXZvY2F0aW9uIGNoZWNraW5nIHdpdGgg
T0NTUC4NCg0KSGF2aW5nIGl0IG9wdGlvbmFsLCBsaWtlIHRoZSB1c2Ugb2YgbWFueSBvdGhlciBU
TFMgZXh0ZW5zaW9ucywgaXMgZmluZSBmb3IgbWUuIEZXSVcgZXZlbiBUTFMgMS4zLCB3aGljaCBp
cyB1c2VkIGluIGEgbW9yZSBnZW5lcmljIGVudmlyb25tZW50LCBkb2VzIG5vdCBtYW5kYXRlIHRo
ZSB1c2Ugb2YgT0NTUCBzdGFwbGluZy4NCg0KVGhpcyByZXF1aXJlbWVudCB3aWxsIG1ha2UgdGhl
IHByb2JsZW0gZGVzY3JpYmVkIGluIGRyYWZ0LWlldGYtZW11LWVhcHRsc2NlcnQgd29yc2UuIEkg
YW0gc3VyZSB0aGUgYXV0aG9ycyBhcmUgYXdhcmUgb2YgdGhpcyBmYWN0IHNpbmNlIHRoZXkgYXJl
IGFsc28gY28tYXV0aG9ycyBvZiBkcmFmdC1pZXRmLWVtdS1lYXB0bHNjZXJ0Lg0KDQpDaWFvDQpI
YW5uZXMNCklNUE9SVEFOVCBOT1RJQ0U6IFRoZSBjb250ZW50cyBvZiB0aGlzIGVtYWlsIGFuZCBh
bnkgYXR0YWNobWVudHMgYXJlIGNvbmZpZGVudGlhbCBhbmQgbWF5IGFsc28gYmUgcHJpdmlsZWdl
ZC4gSWYgeW91IGFyZSBub3QgdGhlIGludGVuZGVkIHJlY2lwaWVudCwgcGxlYXNlIG5vdGlmeSB0
aGUgc2VuZGVyIGltbWVkaWF0ZWx5IGFuZCBkbyBub3QgZGlzY2xvc2UgdGhlIGNvbnRlbnRzIHRv
IGFueSBvdGhlciBwZXJzb24sIHVzZSBpdCBmb3IgYW55IHB1cnBvc2UsIG9yIHN0b3JlIG9yIGNv
cHkgdGhlIGluZm9ybWF0aW9uIGluIGFueSBtZWRpdW0uIFRoYW5rIHlvdS4gX19fX19fX19fX19f
X19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX18NCkVtdSBtYWlsaW5nIGxpc3QNCkVt
dUBpZXRmLm9yZzxtYWlsdG86RW11QGlldGYub3JnPg0KaHR0cHM6Ly93d3cuaWV0Zi5vcmcvbWFp
bG1hbi9saXN0aW5mby9lbXUNCg0KX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19f
X19fX19fX19fX18NCkVtdSBtYWlsaW5nIGxpc3QNCkVtdUBpZXRmLm9yZzxtYWlsdG86RW11QGll
dGYub3JnPg0KaHR0cHM6Ly93d3cuaWV0Zi5vcmcvbWFpbG1hbi9saXN0aW5mby9lbXUNCklNUE9S
VEFOVCBOT1RJQ0U6IFRoZSBjb250ZW50cyBvZiB0aGlzIGVtYWlsIGFuZCBhbnkgYXR0YWNobWVu
dHMgYXJlIGNvbmZpZGVudGlhbCBhbmQgbWF5IGFsc28gYmUgcHJpdmlsZWdlZC4gSWYgeW91IGFy
ZSBub3QgdGhlIGludGVuZGVkIHJlY2lwaWVudCwgcGxlYXNlIG5vdGlmeSB0aGUgc2VuZGVyIGlt
bWVkaWF0ZWx5IGFuZCBkbyBub3QgZGlzY2xvc2UgdGhlIGNvbnRlbnRzIHRvIGFueSBvdGhlciBw
ZXJzb24sIHVzZSBpdCBmb3IgYW55IHB1cnBvc2UsIG9yIHN0b3JlIG9yIGNvcHkgdGhlIGluZm9y
bWF0aW9uIGluIGFueSBtZWRpdW0uIFRoYW5rIHlvdS4NCklNUE9SVEFOVCBOT1RJQ0U6IFRoZSBj
b250ZW50cyBvZiB0aGlzIGVtYWlsIGFuZCBhbnkgYXR0YWNobWVudHMgYXJlIGNvbmZpZGVudGlh
bCBhbmQgbWF5IGFsc28gYmUgcHJpdmlsZWdlZC4gSWYgeW91IGFyZSBub3QgdGhlIGludGVuZGVk
IHJlY2lwaWVudCwgcGxlYXNlIG5vdGlmeSB0aGUgc2VuZGVyIGltbWVkaWF0ZWx5IGFuZCBkbyBu
b3QgZGlzY2xvc2UgdGhlIGNvbnRlbnRzIHRvIGFueSBvdGhlciBwZXJzb24sIHVzZSBpdCBmb3Ig
YW55IHB1cnBvc2UsIG9yIHN0b3JlIG9yIGNvcHkgdGhlIGluZm9ybWF0aW9uIGluIGFueSBtZWRp
dW0uIFRoYW5rIHlvdS4NCg==

--_000_AM0PR08MB3716466445022163A7C624AAFA160AM0PR08MB3716eurp_
Content-Type: text/html; charset="utf-8"
Content-Transfer-Encoding: base64

PGh0bWwgeG1sbnM6dj0idXJuOnNjaGVtYXMtbWljcm9zb2Z0LWNvbTp2bWwiIHhtbG5zOm89InVy
bjpzY2hlbWFzLW1pY3Jvc29mdC1jb206b2ZmaWNlOm9mZmljZSIgeG1sbnM6dz0idXJuOnNjaGVt
YXMtbWljcm9zb2Z0LWNvbTpvZmZpY2U6d29yZCIgeG1sbnM6bT0iaHR0cDovL3NjaGVtYXMubWlj
cm9zb2Z0LmNvbS9vZmZpY2UvMjAwNC8xMi9vbW1sIiB4bWxucz0iaHR0cDovL3d3dy53My5vcmcv
VFIvUkVDLWh0bWw0MCI+DQo8aGVhZD4NCjxtZXRhIGh0dHAtZXF1aXY9IkNvbnRlbnQtVHlwZSIg
Y29udGVudD0idGV4dC9odG1sOyBjaGFyc2V0PXV0Zi04Ij4NCjxtZXRhIG5hbWU9IkdlbmVyYXRv
ciIgY29udGVudD0iTWljcm9zb2Z0IFdvcmQgMTUgKGZpbHRlcmVkIG1lZGl1bSkiPg0KPHN0eWxl
PjwhLS0NCi8qIEZvbnQgRGVmaW5pdGlvbnMgKi8NCkBmb250LWZhY2UNCgl7Zm9udC1mYW1pbHk6
SGVsdmV0aWNhOw0KCXBhbm9zZS0xOjIgMTEgNiA0IDIgMiAyIDIgMiA0O30NCkBmb250LWZhY2UN
Cgl7Zm9udC1mYW1pbHk6IkNhbWJyaWEgTWF0aCI7DQoJcGFub3NlLTE6MiA0IDUgMyA1IDQgNiAz
IDIgNDt9DQpAZm9udC1mYWNlDQoJe2ZvbnQtZmFtaWx5OkRlbmdYaWFuOw0KCXBhbm9zZS0xOjIg
MSA2IDAgMyAxIDEgMSAxIDE7fQ0KQGZvbnQtZmFjZQ0KCXtmb250LWZhbWlseTpDYWxpYnJpOw0K
CXBhbm9zZS0xOjIgMTUgNSAyIDIgMiA0IDMgMiA0O30NCkBmb250LWZhY2UNCgl7Zm9udC1mYW1p
bHk6IlxARGVuZ1hpYW4iOw0KCXBhbm9zZS0xOjIgMSA2IDAgMyAxIDEgMSAxIDE7fQ0KLyogU3R5
bGUgRGVmaW5pdGlvbnMgKi8NCnAuTXNvTm9ybWFsLCBsaS5Nc29Ob3JtYWwsIGRpdi5Nc29Ob3Jt
YWwNCgl7bWFyZ2luOjBpbjsNCglmb250LXNpemU6MTEuMHB0Ow0KCWZvbnQtZmFtaWx5OiJDYWxp
YnJpIixzYW5zLXNlcmlmO30NCmE6bGluaywgc3Bhbi5Nc29IeXBlcmxpbmsNCgl7bXNvLXN0eWxl
LXByaW9yaXR5Ojk5Ow0KCWNvbG9yOmJsdWU7DQoJdGV4dC1kZWNvcmF0aW9uOnVuZGVybGluZTt9
DQpwLk1zb0xpc3RQYXJhZ3JhcGgsIGxpLk1zb0xpc3RQYXJhZ3JhcGgsIGRpdi5Nc29MaXN0UGFy
YWdyYXBoDQoJe21zby1zdHlsZS1wcmlvcml0eTozNDsNCgltYXJnaW4tdG9wOjBpbjsNCgltYXJn
aW4tcmlnaHQ6MGluOw0KCW1hcmdpbi1ib3R0b206MGluOw0KCW1hcmdpbi1sZWZ0Oi41aW47DQoJ
Zm9udC1zaXplOjExLjBwdDsNCglmb250LWZhbWlseToiQ2FsaWJyaSIsc2Fucy1zZXJpZjt9DQpz
cGFuLkVtYWlsU3R5bGUxOQ0KCXttc28tc3R5bGUtdHlwZTpwZXJzb25hbC1jb21wb3NlOw0KCWZv
bnQtZmFtaWx5OiJDYWxpYnJpIixzYW5zLXNlcmlmOw0KCWNvbG9yOndpbmRvd3RleHQ7fQ0KLk1z
b0NocERlZmF1bHQNCgl7bXNvLXN0eWxlLXR5cGU6ZXhwb3J0LW9ubHk7DQoJZm9udC1mYW1pbHk6
IkNhbGlicmkiLHNhbnMtc2VyaWY7fQ0KQHBhZ2UgV29yZFNlY3Rpb24xDQoJe3NpemU6OC41aW4g
MTEuMGluOw0KCW1hcmdpbjoxLjBpbiAxLjBpbiAxLjBpbiAxLjBpbjt9DQpkaXYuV29yZFNlY3Rp
b24xDQoJe3BhZ2U6V29yZFNlY3Rpb24xO30NCi8qIExpc3QgRGVmaW5pdGlvbnMgKi8NCkBsaXN0
IGwwDQoJe21zby1saXN0LWlkOjkzMTg1Njc5NDsNCgltc28tbGlzdC10eXBlOmh5YnJpZDsNCglt
c28tbGlzdC10ZW1wbGF0ZS1pZHM6NjE4NjY4NjE4IDY3Njk4NzAzIDY3Njk4NzEzIDY3Njk4NzE1
IDY3Njk4NzAzIDY3Njk4NzEzIDY3Njk4NzE1IDY3Njk4NzAzIDY3Njk4NzEzIDY3Njk4NzE1O30N
CkBsaXN0IGwwOmxldmVsMQ0KCXttc28tbGV2ZWwtdGFiLXN0b3A6bm9uZTsNCgltc28tbGV2ZWwt
bnVtYmVyLXBvc2l0aW9uOmxlZnQ7DQoJdGV4dC1pbmRlbnQ6LS4yNWluO30NCkBsaXN0IGwwOmxl
dmVsMg0KCXttc28tbGV2ZWwtbnVtYmVyLWZvcm1hdDphbHBoYS1sb3dlcjsNCgltc28tbGV2ZWwt
dGFiLXN0b3A6bm9uZTsNCgltc28tbGV2ZWwtbnVtYmVyLXBvc2l0aW9uOmxlZnQ7DQoJdGV4dC1p
bmRlbnQ6LS4yNWluO30NCkBsaXN0IGwwOmxldmVsMw0KCXttc28tbGV2ZWwtbnVtYmVyLWZvcm1h
dDpyb21hbi1sb3dlcjsNCgltc28tbGV2ZWwtdGFiLXN0b3A6bm9uZTsNCgltc28tbGV2ZWwtbnVt
YmVyLXBvc2l0aW9uOnJpZ2h0Ow0KCXRleHQtaW5kZW50Oi05LjBwdDt9DQpAbGlzdCBsMDpsZXZl
bDQNCgl7bXNvLWxldmVsLXRhYi1zdG9wOm5vbmU7DQoJbXNvLWxldmVsLW51bWJlci1wb3NpdGlv
bjpsZWZ0Ow0KCXRleHQtaW5kZW50Oi0uMjVpbjt9DQpAbGlzdCBsMDpsZXZlbDUNCgl7bXNvLWxl
dmVsLW51bWJlci1mb3JtYXQ6YWxwaGEtbG93ZXI7DQoJbXNvLWxldmVsLXRhYi1zdG9wOm5vbmU7
DQoJbXNvLWxldmVsLW51bWJlci1wb3NpdGlvbjpsZWZ0Ow0KCXRleHQtaW5kZW50Oi0uMjVpbjt9
DQpAbGlzdCBsMDpsZXZlbDYNCgl7bXNvLWxldmVsLW51bWJlci1mb3JtYXQ6cm9tYW4tbG93ZXI7
DQoJbXNvLWxldmVsLXRhYi1zdG9wOm5vbmU7DQoJbXNvLWxldmVsLW51bWJlci1wb3NpdGlvbjpy
aWdodDsNCgl0ZXh0LWluZGVudDotOS4wcHQ7fQ0KQGxpc3QgbDA6bGV2ZWw3DQoJe21zby1sZXZl
bC10YWItc3RvcDpub25lOw0KCW1zby1sZXZlbC1udW1iZXItcG9zaXRpb246bGVmdDsNCgl0ZXh0
LWluZGVudDotLjI1aW47fQ0KQGxpc3QgbDA6bGV2ZWw4DQoJe21zby1sZXZlbC1udW1iZXItZm9y
bWF0OmFscGhhLWxvd2VyOw0KCW1zby1sZXZlbC10YWItc3RvcDpub25lOw0KCW1zby1sZXZlbC1u
dW1iZXItcG9zaXRpb246bGVmdDsNCgl0ZXh0LWluZGVudDotLjI1aW47fQ0KQGxpc3QgbDA6bGV2
ZWw5DQoJe21zby1sZXZlbC1udW1iZXItZm9ybWF0OnJvbWFuLWxvd2VyOw0KCW1zby1sZXZlbC10
YWItc3RvcDpub25lOw0KCW1zby1sZXZlbC1udW1iZXItcG9zaXRpb246cmlnaHQ7DQoJdGV4dC1p
bmRlbnQ6LTkuMHB0O30NCm9sDQoJe21hcmdpbi1ib3R0b206MGluO30NCnVsDQoJe21hcmdpbi1i
b3R0b206MGluO30NCi0tPjwvc3R5bGU+PCEtLVtpZiBndGUgbXNvIDldPjx4bWw+DQo8bzpzaGFw
ZWRlZmF1bHRzIHY6ZXh0PSJlZGl0IiBzcGlkbWF4PSIxMDI2IiAvPg0KPC94bWw+PCFbZW5kaWZd
LS0+PCEtLVtpZiBndGUgbXNvIDldPjx4bWw+DQo8bzpzaGFwZWxheW91dCB2OmV4dD0iZWRpdCI+
DQo8bzppZG1hcCB2OmV4dD0iZWRpdCIgZGF0YT0iMSIgLz4NCjwvbzpzaGFwZWxheW91dD48L3ht
bD48IVtlbmRpZl0tLT4NCjwvaGVhZD4NCjxib2R5IGxhbmc9IkVOLVVTIiBsaW5rPSJibHVlIiB2
bGluaz0icHVycGxlIiBzdHlsZT0id29yZC13cmFwOmJyZWFrLXdvcmQiPg0KPGRpdiBjbGFzcz0i
V29yZFNlY3Rpb24xIj4NCjxwIGNsYXNzPSJNc29Ob3JtYWwiPkhpIEpvZSwgPG86cD48L286cD48
L3A+DQo8cCBjbGFzcz0iTXNvTm9ybWFsIj48bzpwPiZuYnNwOzwvbzpwPjwvcD4NCjxwIGNsYXNz
PSJNc29Ob3JtYWwiPmEgZmV3IHJlbWFya3MgYmVsb3cuIDxvOnA+PC9vOnA+PC9wPg0KPGRpdj4N
CjxkaXY+DQo8cCBjbGFzcz0iTXNvTm9ybWFsIj48bzpwPiZuYnNwOzwvbzpwPjwvcD4NCjwvZGl2
Pg0KPHAgY2xhc3M9Ik1zb05vcm1hbCI+PG86cD4mbmJzcDs8L286cD48L3A+DQo8ZGl2Pg0KPGRp
dj4NCjxwIGNsYXNzPSJNc29Ob3JtYWwiPk9uIEZyaSwgT2N0IDIzLCAyMDIwIGF0IDEyOjM4IEFN
IEhhbm5lcyBUc2Nob2ZlbmlnICZsdDs8YSBocmVmPSJtYWlsdG86SGFubmVzLlRzY2hvZmVuaWdA
YXJtLmNvbSI+SGFubmVzLlRzY2hvZmVuaWdAYXJtLmNvbTwvYT4mZ3Q7IHdyb3RlOjxvOnA+PC9v
OnA+PC9wPg0KPC9kaXY+DQo8YmxvY2txdW90ZSBzdHlsZT0iYm9yZGVyOm5vbmU7Ym9yZGVyLWxl
ZnQ6c29saWQgI0NDQ0NDQyAxLjBwdDtwYWRkaW5nOjBpbiAwaW4gMGluIDYuMHB0O21hcmdpbi1s
ZWZ0OjQuOHB0O21hcmdpbi1yaWdodDowaW4iPg0KPGRpdj4NCjxkaXY+DQo8cCBjbGFzcz0iTXNv
Tm9ybWFsIiBzdHlsZT0ibXNvLW1hcmdpbi10b3AtYWx0OmF1dG87bXNvLW1hcmdpbi1ib3R0b20t
YWx0OmF1dG8iPkhpIEpvZSwNCjxvOnA+PC9vOnA+PC9wPg0KPHAgY2xhc3M9Ik1zb05vcm1hbCIg
c3R5bGU9Im1zby1tYXJnaW4tdG9wLWFsdDphdXRvO21zby1tYXJnaW4tYm90dG9tLWFsdDphdXRv
Ij4mbmJzcDs8bzpwPjwvbzpwPjwvcD4NCjxwIGNsYXNzPSJNc29Ob3JtYWwiIHN0eWxlPSJtc28t
bWFyZ2luLXRvcC1hbHQ6YXV0bzttc28tbWFyZ2luLWJvdHRvbS1hbHQ6YXV0byI+SSBkbyBub3Qg
dW5kZXJzdGFuZCBjZXJ0aWZpY2F0ZSByZXZvY2F0aW9uIGNoZWNraW5nIGlzIGEgdG9waWMgc3Bl
Y2lmaWMgdG8gdGhlIHVzZSBvZiBUTFMgMS4zIGluIEVBUC1UTFMuDQo8bzpwPjwvbzpwPjwvcD4N
CjwvZGl2Pg0KPC9kaXY+DQo8L2Jsb2NrcXVvdGU+DQo8ZGl2Pg0KPHAgY2xhc3M9Ik1zb05vcm1h
bCIgc3R5bGU9Im1zby1tYXJnaW4tdG9wLWFsdDphdXRvO21zby1tYXJnaW4tYm90dG9tLWFsdDph
dXRvIj4mbmJzcDs8bzpwPjwvbzpwPjwvcD4NCjwvZGl2Pg0KPGRpdj4NCjxwIGNsYXNzPSJNc29O
b3JtYWwiPltKb2VdJm5ic3A7IFRMUyAxLjMgZGlzY3Vzc2VzJm5ic3A7T0NTUCBhbmQgKFNDVCku
Jm5ic3A7IE9DU1Agc3RhcGxpbmcgaXMgYSByZXZvY2F0aW9uIG1lY2hhbmlzbSB0aGF0IHdpbGwg
d29yayB3aGVuIHRoZSBFQVAtVExTIGNsaWVudCBkb2VzIG5vdCBoYXZlIGNvbm5lY3Rpdml0eSB5
ZXQsIHdoaWNoIGlzIGEgY29tbW9uIGNhc2UgaW4gRUFQLVRMUyBkZXBsb3ltZW50cy4mbmJzcDsg
Jm5ic3A7IFRoZSB3YXkgdGhlIGRyYWZ0IGlzIHdyaXR0ZW4gbm93DQogaXQgbWFuZGF0ZXMgdGhh
dCB0aGlzIG1lY2hhbmlzbSBiZSB1c2VkIGFuZCBpbXBsZW1lbnRzLiZuYnNwOyBUTFMgMS4zIGRv
ZXMgbm90IHJlcXVpcmUgdGhpcy4mbmJzcDsmbmJzcDs8bzpwPjwvbzpwPjwvcD4NCjwvZGl2Pg0K
PGRpdj4NCjxwIGNsYXNzPSJNc29Ob3JtYWwiPjxvOnA+Jm5ic3A7PC9vOnA+PC9wPg0KPHAgY2xh
c3M9Ik1zb05vcm1hbCI+W2hhbm5lc10gSXQgaXMgYWxzbyBjb21tb24gdG8gZ2l2ZSBuZXR3b3Jr
IGFjY2VzcyB0byBkZXZpY2VzIHRoYXQgbmVlZCBhIHNvZnR3YXJlIHVwZGF0ZSBvciBjb25maWd1
cmF0aW9uIGNoYW5nZXMuDQo8bzpwPjwvbzpwPjwvcD4NCjxwIGNsYXNzPSJNc29Ob3JtYWwiPjxv
OnA+Jm5ic3A7PC9vOnA+PC9wPg0KPHAgY2xhc3M9Ik1zb05vcm1hbCI+V2hhdCBkbyB5b3UgZXhw
ZWN0IHRvIGhhcHBlbiBpZiB0aGUgZGV2aWNlIGZpbmRzIG91dCB0aGF0IHRoZSBjZXJ0aWZpY2F0
ZSBvZmZlcmVkIGJ5IHRoZSBzZXJ2ZXIgaGFzIGV4cGlyZWQ/DQo8bzpwPjwvbzpwPjwvcD4NCjxw
IGNsYXNzPSJNc29Ob3JtYWwiPiZuYnNwOzxvOnA+PC9vOnA+PC9wPg0KPHAgY2xhc3M9Ik1zb05v
cm1hbCI+PG86cD4mbmJzcDs8L286cD48L3A+DQo8L2Rpdj4NCjxibG9ja3F1b3RlIHN0eWxlPSJi
b3JkZXI6bm9uZTtib3JkZXItbGVmdDpzb2xpZCAjQ0NDQ0NDIDEuMHB0O3BhZGRpbmc6MGluIDBp
biAwaW4gNi4wcHQ7bWFyZ2luLWxlZnQ6NC44cHQ7bWFyZ2luLXJpZ2h0OjBpbiI+DQo8ZGl2Pg0K
PGRpdj4NCjxwIGNsYXNzPSJNc29Ob3JtYWwiIHN0eWxlPSJtc28tbWFyZ2luLXRvcC1hbHQ6YXV0
bzttc28tbWFyZ2luLWJvdHRvbS1hbHQ6YXV0byI+SWYgdGhpcyB0b3BpYyBpcyBpbXBvcnRhbnQg
dG8gdGhlIGdyb3VwIHRoZW4gd2h5IGlzbuKAmXQgdGhpcyBhIGdlbmVyaWMgcmVjb21tZW5kYXRp
b25zIGZvciBhbGwgRUFQIG1ldGhvZHMgdGhhdCB1c2UgcHVibGljIGtleSBiYXNlZCBhdXRoZW50
aWNhdGlvbj8NCjxvOnA+PC9vOnA+PC9wPg0KPHAgY2xhc3M9Ik1zb05vcm1hbCIgc3R5bGU9Im1z
by1tYXJnaW4tdG9wLWFsdDphdXRvO21zby1tYXJnaW4tYm90dG9tLWFsdDphdXRvIj4mbmJzcDs8
bzpwPjwvbzpwPjwvcD4NCjwvZGl2Pg0KPC9kaXY+DQo8L2Jsb2NrcXVvdGU+DQo8ZGl2Pg0KPHAg
Y2xhc3M9Ik1zb05vcm1hbCI+PG86cD4mbmJzcDs8L286cD48L3A+DQo8L2Rpdj4NCjxkaXY+DQo8
cCBjbGFzcz0iTXNvTm9ybWFsIj5bSm9lXSBDZXJ0aWZpY2F0ZSByZXZvY2F0aW9uIGlzIHNwZWNp
ZmljIHRvIHRoZSB1c2Ugb2YgY2VydGlmaWNhdGVzLiZuYnNwOzxvOnA+PC9vOnA+PC9wPg0KPC9k
aXY+DQo8ZGl2Pg0KPHAgY2xhc3M9Ik1zb05vcm1hbCI+Jm5ic3A7PG86cD48L286cD48L3A+DQo8
cCBjbGFzcz0iTXNvTm9ybWFsIj5bSGFubmVzXSBNYW55IEVBUCBtZXRob2RzIHVzZSBjZXJ0aWZp
Y2F0ZXMgYnV0IHRoZXkgZG8gbm90IG1hbmRhdGUgdGhlIHVzZSBvZiBPQ1NQLg0KPG86cD48L286
cD48L3A+DQo8cCBjbGFzcz0iTXNvTm9ybWFsIj48bzpwPiZuYnNwOzwvbzpwPjwvcD4NCjwvZGl2
Pg0KPGJsb2NrcXVvdGUgc3R5bGU9ImJvcmRlcjpub25lO2JvcmRlci1sZWZ0OnNvbGlkICNDQ0ND
Q0MgMS4wcHQ7cGFkZGluZzowaW4gMGluIDBpbiA2LjBwdDttYXJnaW4tbGVmdDo0LjhwdDttYXJn
aW4tcmlnaHQ6MGluIj4NCjxkaXY+DQo8ZGl2Pg0KPHAgY2xhc3M9Ik1zb05vcm1hbCIgc3R5bGU9
Im1zby1tYXJnaW4tdG9wLWFsdDphdXRvO21zby1tYXJnaW4tYm90dG9tLWFsdDphdXRvIj5Xb3Vs
ZG7igJl0IHRoaXMgYmUgYSB0b3BpYyB0byBhZGRyZXNzIGluICZsdDtkcmFmdC1pZXRmLWVtdS1l
YXB0bHNjZXJ0Jmd0Oz8gSU1ITyB0aGlzIHdvdWxkIG1ha2UgbW9yZSBzZW5zZSBnaXZlbiB0aGF0
ICZsdDtkcmFmdC1pZXRmLWVtdS1lYXB0bHNjZXJ0Jmd0OyB0YWxrcyBhYm91dCBsYXJnZSBjZXJ0
aWZpY2F0ZXMgYW5kIGxvbmcNCiBjZXJ0aWZpY2F0ZSBjaGFpbnMgYW5kIGFueSBwcm9wb3NhbCB0
byBtYWtlIHRob3NlIGV2ZW4gbGFyZ2VyIHNob3VsZCBiZSBldmFsdWF0ZWQgaW4gdGhpcyBjb250
ZXh0Lg0KPG86cD48L286cD48L3A+DQo8cCBjbGFzcz0iTXNvTm9ybWFsIiBzdHlsZT0ibXNvLW1h
cmdpbi10b3AtYWx0OmF1dG87bXNvLW1hcmdpbi1ib3R0b20tYWx0OmF1dG8iPiZuYnNwOzxvOnA+
PC9vOnA+PC9wPg0KPC9kaXY+DQo8L2Rpdj4NCjwvYmxvY2txdW90ZT4NCjxkaXY+DQo8cCBjbGFz
cz0iTXNvTm9ybWFsIj48bzpwPiZuYnNwOzwvbzpwPjwvcD4NCjwvZGl2Pg0KPGRpdj4NCjxwIGNs
YXNzPSJNc29Ob3JtYWwiPltKb2VdIE5vLCAmbHQ7ZHJhZnQtaWV0Zi1lbXUtZWFwdGxzY2VydCZn
dDsgZGlzY3Vzc2VzIGhhbmRsaW5nIGxhcmdlIGNlcnRpZmljYXRlcyBub3QgcmV2b2NhdGlvbi4m
bmJzcDs8bzpwPjwvbzpwPjwvcD4NCjxwIGNsYXNzPSJNc29Ob3JtYWwiPjxvOnA+Jm5ic3A7PC9v
OnA+PC9wPg0KPHAgY2xhc3M9Ik1zb05vcm1hbCI+W0hhbm5lc10gSGVyZSB0aGUgcHJvYmxlbSBk
ZXNjcmlwdGlvbiB0aGF0IG1vdGl2YXRlcyAmbHQ7ZHJhZnQtaWV0Zi1lbXUtZWFwdGxzY2VydCZn
dDs8bzpwPjwvbzpwPjwvcD4NCjxwIGNsYXNzPSJNc29Ob3JtYWwiPjxzcGFuIHN0eWxlPSJmb250
LXNpemU6MTAuMHB0O2ZvbnQtZmFtaWx5OiZxdW90O0NvdXJpZXIgTmV3JnF1b3Q7Ij7igJw8bzpw
PjwvbzpwPjwvc3Bhbj48L3A+DQo8cCBjbGFzcz0iTXNvTm9ybWFsIj48c3BhbiBzdHlsZT0iZm9u
dC1zaXplOjEwLjBwdDtmb250LWZhbWlseTomcXVvdDtDb3VyaWVyIE5ldyZxdW90OyI+TGFyZ2Ug
Y2VydGlmaWNhdGVzIGFuZCBsb25nPG86cD48L286cD48L3NwYW4+PC9wPg0KPHAgY2xhc3M9Ik1z
b05vcm1hbCI+PHNwYW4gc3R5bGU9ImZvbnQtc2l6ZToxMC4wcHQ7Zm9udC1mYW1pbHk6JnF1b3Q7
Q291cmllciBOZXcmcXVvdDsiPiZuYnNwOyZuYnNwOyBjZXJ0aWZpY2F0ZSBjaGFpbnMgY29tYmlu
ZWQgd2l0aCBhdXRoZW50aWNhdG9ycyB0aGF0IGRyb3AgYW4gRUFQPG86cD48L286cD48L3NwYW4+
PC9wPg0KPHAgY2xhc3M9Ik1zb05vcm1hbCI+PHNwYW4gc3R5bGU9ImZvbnQtc2l6ZToxMC4wcHQ7
Zm9udC1mYW1pbHk6JnF1b3Q7Q291cmllciBOZXcmcXVvdDsiPiZuYnNwOyZuYnNwOyBzZXNzaW9u
IGFmdGVyIG9ubHkgNDAgLSA1MCByb3VuZC10cmlwcyBpcyBhIG1ham9yIGRlcGxveW1lbnQgcHJv
YmxlbS48bzpwPjwvbzpwPjwvc3Bhbj48L3A+DQo8cCBjbGFzcz0iTXNvTm9ybWFsIj48c3BhbiBz
dHlsZT0iZm9udC1zaXplOjEwLjBwdDtmb250LWZhbWlseTomcXVvdDtDb3VyaWVyIE5ldyZxdW90
OyI+Jm5ic3A7Jm5ic3A7IFRoaXMgZG9jdW1lbnQgbG9va3MgYXQgdGhlIHRoaXMgcHJvYmxlbSBp
biBkZXRhaWwgYW5kIGRlc2NyaWJlcyB0aGU8bzpwPjwvbzpwPjwvc3Bhbj48L3A+DQo8cCBjbGFz
cz0iTXNvTm9ybWFsIj48c3BhbiBzdHlsZT0iZm9udC1zaXplOjEwLjBwdDtmb250LWZhbWlseTom
cXVvdDtDb3VyaWVyIE5ldyZxdW90OyI+Jm5ic3A7Jm5ic3A7IHBvdGVudGlhbCBzb2x1dGlvbnMg
YXZhaWxhYmxlLjxvOnA+PC9vOnA+PC9zcGFuPjwvcD4NCjxwIGNsYXNzPSJNc29Ob3JtYWwiPuKA
nDxvOnA+PC9vOnA+PC9wPg0KPHAgY2xhc3M9Ik1zb05vcm1hbCI+T0NTUCBpbmZvcm1hdGlvbiB0
cmF2ZWxzIGFsb25nc2lkZSB0aGUgY2VydGlmaWNhdGVzIGFuZCB0aGVyZWZvcmUgaW5jcmVhc2Vz
IHRoZSBwcm9ibGVtIG91dGxpbmVkIGJ5ICZsdDtkcmFmdC1pZXRmLWVtdS1lYXB0bHNjZXJ0Jmd0
OzxvOnA+PC9vOnA+PC9wPg0KPHAgY2xhc3M9Ik1zb05vcm1hbCI+PG86cD4mbmJzcDs8L286cD48
L3A+DQo8cCBjbGFzcz0iTXNvTm9ybWFsIj5FQVAtVExTIGlzIHRoZSByaWdodCBwbGFjZSB0byBk
aXNjdXNzIHJldm9jYXRpb24gaXNzdWVzLiZuYnNwOzxvOnA+PC9vOnA+PC9wPg0KPHAgY2xhc3M9
Ik1zb05vcm1hbCI+PG86cD4mbmJzcDs8L286cD48L3A+DQo8cCBjbGFzcz0iTXNvTm9ybWFsIj5J
dCBzZWVtcyB0aGVyZSBhcmUgc2V2ZXJhbCBxdWVzdGlvbnMgdGhhdCBuZWVkIHRvIGJlIGFuc3dl
cmVkOjxvOnA+PC9vOnA+PC9wPg0KPC9kaXY+DQo8ZGl2Pg0KPHAgY2xhc3M9Ik1zb05vcm1hbCI+
PG86cD4mbmJzcDs8L286cD48L3A+DQo8L2Rpdj4NCjxkaXY+DQo8b2wgc3R5bGU9Im1hcmdpbi10
b3A6MGluIiBzdGFydD0iMSIgdHlwZT0iMSI+DQo8bGkgY2xhc3M9Ik1zb0xpc3RQYXJhZ3JhcGgi
IHN0eWxlPSJtYXJnaW4tbGVmdDowaW47bXNvLWxpc3Q6bDAgbGV2ZWwxIGxmbzEiPlNob3VsZCB0
aGUgZG9jdW1lbnQgbWFuZGF0ZSB0aGF0IE9DU1Agc3RhcGxpbmcmbmJzcDtiZSB1c2VkPzxvOnA+
PC9vOnA+PC9saT48L29sPg0KPHAgY2xhc3M9Ik1zb05vcm1hbCI+W0hhbm5lc10gTm8uIDxvOnA+
PC9vOnA+PC9wPg0KPHAgY2xhc3M9Ik1zb05vcm1hbCI+PG86cD4mbmJzcDs8L286cD48L3A+DQo8
L2Rpdj4NCjxkaXY+DQo8cCBjbGFzcz0iTXNvTm9ybWFsIj4yLiBTaG91bGQgdGhlIGRvY3VtZW50
IG1hbmRhdGUgdGhhdCBPQ1NQIHN0YXBsaW5nIGJlIGltcGxlbWVudGVkPzxvOnA+PC9vOnA+PC9w
Pg0KPC9kaXY+DQo8ZGl2Pg0KPHAgY2xhc3M9Ik1zb05vcm1hbCI+W0hhbm5lc10gTm8uIDxvOnA+
PC9vOnA+PC9wPg0KPHAgY2xhc3M9Ik1zb05vcm1hbCI+PG86cD4mbmJzcDs8L286cD48L3A+DQo8
cCBjbGFzcz0iTXNvTm9ybWFsIj4zLiBXaGF0IHNob3VsZCB0aGUgZG9jdW1lbnQgc2F5IGluIHRo
ZSBzZWN1cml0eSBzZWN0aW9ucyB3aXRoIHJlc3BlY3QgdG8gT0NTUCBzdGFwbGluZyBhbmQgb3Ro
ZXIgbWVjaGFuaXNtcz8mbmJzcDs8bzpwPjwvbzpwPjwvcD4NCjwvZGl2Pg0KPGRpdj4NCjxwIGNs
YXNzPSJNc29Ob3JtYWwiPltIYW5uZXNdIElNSE8gVExTIDEuMyBzYXlzIHRoZSByZWxldmFudCBz
b2x1dGlvbiBwYXJ0cy4gT0NTUCBzdGFwbGluZyBpcyBhdmFpbGFibGUgZm9yIHVzZSBpbiBUTFMg
MS4zIGFuZCBpdCBpcyBvbmUgc3VpdGFibGUgbWVjaGFuaXNtIGZvciBjZXJ0aWZpY2F0ZSByZXZv
Y2F0aW9uLjxvOnA+PC9vOnA+PC9wPg0KPC9kaXY+DQo8ZGl2Pg0KPHAgY2xhc3M9Ik1zb05vcm1h
bCI+PG86cD4mbmJzcDs8L286cD48L3A+DQo8cCBjbGFzcz0iTXNvTm9ybWFsIj5EbyBhbnkgb2Yg
dGhlc2UgcmVjb21tZW5kYXRpb25zIGFsc28gYXBwbHkgdG8gRUFQLVRMUyB3aXRoIFRMUyAxLjIg
YXMgd2VsbCAoc2luY2UgaXQgYWxzbyBvZmZlcnMgT0NTUCBzdGFwbGluZyk/IFdvdWxkIHRoZSBy
ZWNvbW1lbmRhdGlvbnMgYWxzbyBhcHBseSB0byBFQVAgbWV0aG9kcyB0aGF0IHVzZSBUTFMgdW5k
ZXIgdGhlIGhvb2QsIHN1Y2ggYXMgVEVBUCwgRUFQLUZBU1QsIG9yIEVBUC1UVExTPyBXb3VsZA0K
IHRoZXkgYXBwbHkgdG8gbWV0aG9kcyBsaWtlIEVBUC1JS0V2MiBvciB0aGUgcmVjZW50bHkgc3Vn
Z2VzdGVkIEVBUC1FREhPQywgd2hpY2ggYXJlIGFsc28gbWV0aG9kcyB0aGF0IHVzZSBjZXJ0aWZp
Y2F0ZXM/DQo8bzpwPjwvbzpwPjwvcD4NCjwvZGl2Pg0KPGRpdj4NCjxwIGNsYXNzPSJNc29Ob3Jt
YWwiPjxvOnA+Jm5ic3A7PC9vOnA+PC9wPg0KPC9kaXY+DQo8ZGl2Pg0KPHAgY2xhc3M9Ik1zb05v
cm1hbCI+Q2lhbzxvOnA+PC9vOnA+PC9wPg0KPHAgY2xhc3M9Ik1zb05vcm1hbCI+SGFubmVzPG86
cD48L286cD48L3A+DQo8L2Rpdj4NCjxkaXY+DQo8cCBjbGFzcz0iTXNvTm9ybWFsIj48bzpwPiZu
YnNwOzwvbzpwPjwvcD4NCjwvZGl2Pg0KPGJsb2NrcXVvdGUgc3R5bGU9ImJvcmRlcjpub25lO2Jv
cmRlci1sZWZ0OnNvbGlkICNDQ0NDQ0MgMS4wcHQ7cGFkZGluZzowaW4gMGluIDBpbiA2LjBwdDtt
YXJnaW4tbGVmdDo0LjhwdDttYXJnaW4tcmlnaHQ6MGluIj4NCjxkaXY+DQo8ZGl2Pg0KPHAgY2xh
c3M9Ik1zb05vcm1hbCIgc3R5bGU9Im1zby1tYXJnaW4tdG9wLWFsdDphdXRvO21zby1tYXJnaW4t
Ym90dG9tLWFsdDphdXRvIj5DaWFvPG86cD48L286cD48L3A+DQo8cCBjbGFzcz0iTXNvTm9ybWFs
IiBzdHlsZT0ibXNvLW1hcmdpbi10b3AtYWx0OmF1dG87bXNvLW1hcmdpbi1ib3R0b20tYWx0OmF1
dG8iPkhhbm5lczxvOnA+PC9vOnA+PC9wPg0KPHAgY2xhc3M9Ik1zb05vcm1hbCIgc3R5bGU9Im1z
by1tYXJnaW4tdG9wLWFsdDphdXRvO21zby1tYXJnaW4tYm90dG9tLWFsdDphdXRvIj4mbmJzcDs8
bzpwPjwvbzpwPjwvcD4NCjxkaXYgc3R5bGU9ImJvcmRlcjpub25lO2JvcmRlci10b3A6c29saWQg
I0UxRTFFMSAxLjBwdDtwYWRkaW5nOjMuMHB0IDBpbiAwaW4gMGluIj4NCjxwIGNsYXNzPSJNc29O
b3JtYWwiIHN0eWxlPSJtc28tbWFyZ2luLXRvcC1hbHQ6YXV0bzttc28tbWFyZ2luLWJvdHRvbS1h
bHQ6YXV0byI+PGI+RnJvbTo8L2I+IEpvc2VwaCBTYWxvd2V5ICZsdDs8YSBocmVmPSJtYWlsdG86
am9lQHNhbG93ZXkubmV0IiB0YXJnZXQ9Il9ibGFuayI+am9lQHNhbG93ZXkubmV0PC9hPiZndDsN
Cjxicj4NCjxiPlNlbnQ6PC9iPiBUaHVyc2RheSwgT2N0b2JlciAyMiwgMjAyMCAxMToxMiBQTTxi
cj4NCjxiPlRvOjwvYj4gRWxpb3QgTGVhciAmbHQ7bGVhcj08YSBocmVmPSJtYWlsdG86NDBjaXNj
by5jb21AZG1hcmMuaWV0Zi5vcmciIHRhcmdldD0iX2JsYW5rIj40MGNpc2NvLmNvbUBkbWFyYy5p
ZXRmLm9yZzwvYT4mZ3Q7PGJyPg0KPGI+Q2M6PC9iPiBIYW5uZXMgVHNjaG9mZW5pZyAmbHQ7PGEg
aHJlZj0ibWFpbHRvOkhhbm5lcy5Uc2Nob2ZlbmlnQGFybS5jb20iIHRhcmdldD0iX2JsYW5rIj5I
YW5uZXMuVHNjaG9mZW5pZ0Bhcm0uY29tPC9hPiZndDs7DQo8YSBocmVmPSJtYWlsdG86ZW11QGll
dGYub3JnIiB0YXJnZXQ9Il9ibGFuayI+ZW11QGlldGYub3JnPC9hPjxicj4NCjxiPlN1YmplY3Q6
PC9iPiBSZTogW0VtdV0gZHJhZnQtaWV0Zi1lbXUtZWFwLXRsczEzLTExOiBPQ1NQIFN0YXBsaW5n
PG86cD48L286cD48L3A+DQo8L2Rpdj4NCjxwIGNsYXNzPSJNc29Ob3JtYWwiIHN0eWxlPSJtc28t
bWFyZ2luLXRvcC1hbHQ6YXV0bzttc28tbWFyZ2luLWJvdHRvbS1hbHQ6YXV0byI+Jm5ic3A7PG86
cD48L286cD48L3A+DQo8ZGl2Pg0KPGRpdj4NCjxwIGNsYXNzPSJNc29Ob3JtYWwiIHN0eWxlPSJt
c28tbWFyZ2luLXRvcC1hbHQ6YXV0bzttc28tbWFyZ2luLWJvdHRvbS1hbHQ6YXV0byI+Jm5ic3A7
PG86cD48L286cD48L3A+DQo8L2Rpdj4NCjxwIGNsYXNzPSJNc29Ob3JtYWwiIHN0eWxlPSJtc28t
bWFyZ2luLXRvcC1hbHQ6YXV0bzttc28tbWFyZ2luLWJvdHRvbS1hbHQ6YXV0byI+Jm5ic3A7PG86
cD48L286cD48L3A+DQo8ZGl2Pg0KPGRpdj4NCjxwIGNsYXNzPSJNc29Ob3JtYWwiIHN0eWxlPSJt
c28tbWFyZ2luLXRvcC1hbHQ6YXV0bzttc28tbWFyZ2luLWJvdHRvbS1hbHQ6YXV0byI+T24gVGh1
LCBPY3QgMjIsIDIwMjAgYXQgODowOCBBTSBFbGlvdCBMZWFyICZsdDtsZWFyPTxhIGhyZWY9Im1h
aWx0bzo0MGNpc2NvLmNvbUBkbWFyYy5pZXRmLm9yZyIgdGFyZ2V0PSJfYmxhbmsiPjQwY2lzY28u
Y29tQGRtYXJjLmlldGYub3JnPC9hPiZndDsgd3JvdGU6PG86cD48L286cD48L3A+DQo8L2Rpdj4N
CjxibG9ja3F1b3RlIHN0eWxlPSJib3JkZXI6bm9uZTtib3JkZXItbGVmdDpzb2xpZCAjQ0NDQ0ND
IDEuMHB0O3BhZGRpbmc6MGluIDBpbiAwaW4gNi4wcHQ7bWFyZ2luLWxlZnQ6NC44cHQ7bWFyZ2lu
LXRvcDo1LjBwdDttYXJnaW4tcmlnaHQ6MGluO21hcmdpbi1ib3R0b206NS4wcHQiPg0KPGRpdj4N
CjxwIGNsYXNzPSJNc29Ob3JtYWwiIHN0eWxlPSJtc28tbWFyZ2luLXRvcC1hbHQ6YXV0bzttc28t
bWFyZ2luLWJvdHRvbS1hbHQ6YXV0byI+KzEuJm5ic3A7IEhvdyBkb2VzIGFueW9uZSBldmVuIGRv
IE9DU1Agd2l0aG91dCBoYXZpbmcgZmlyc3QgZ290dGVuIG9udG8gdGhlIG5ldHdvcms/PG86cD48
L286cD48L3A+DQo8ZGl2Pg0KPHAgY2xhc3M9Ik1zb05vcm1hbCIgc3R5bGU9Im1zby1tYXJnaW4t
dG9wLWFsdDphdXRvO21zby1tYXJnaW4tYm90dG9tLWFsdDphdXRvIj4mbmJzcDs8bzpwPjwvbzpw
PjwvcD4NCjwvZGl2Pg0KPC9kaXY+DQo8L2Jsb2NrcXVvdGU+DQo8ZGl2Pg0KPHAgY2xhc3M9Ik1z
b05vcm1hbCIgc3R5bGU9Im1zby1tYXJnaW4tdG9wLWFsdDphdXRvO21zby1tYXJnaW4tYm90dG9t
LWFsdDphdXRvIj4mbmJzcDs8bzpwPjwvbzpwPjwvcD4NCjwvZGl2Pg0KPGRpdj4NCjxwIGNsYXNz
PSJNc29Ob3JtYWwiIHN0eWxlPSJtc28tbWFyZ2luLXRvcC1hbHQ6YXV0bzttc28tbWFyZ2luLWJv
dHRvbS1hbHQ6YXV0byI+W0pvZV0gVEhhdCBpcyB3aGF0IE9DU1Agc3RhcGxpbmcgaXMgc3VwcG9z
ZWQgdG8gc29sdmUgc2luY2UgdGhlIE9DU1AgbWVzc2FnZXMgYXJlIHNlbnQgaW4gdGhlIFRMUyBo
YW5kc2hha2UuJm5ic3A7ICZuYnNwO0kgYmVsaWV2ZSB0aGVyZSBhcmUgc29tZSBFQVAtVExTIGlt
cGxlbWVudGF0aW9ucyB0aGF0IHN1cHBvcnQgT0NTUCwNCiBidXQgSSBhbSBub3Qgc3VyZSBpZiBp
dCBpcyBhY3R1YWxseSBkZXBsb3llZC4mbmJzcDsmbmJzcDs8bzpwPjwvbzpwPjwvcD4NCjwvZGl2
Pg0KPGRpdj4NCjxwIGNsYXNzPSJNc29Ob3JtYWwiIHN0eWxlPSJtc28tbWFyZ2luLXRvcC1hbHQ6
YXV0bzttc28tbWFyZ2luLWJvdHRvbS1hbHQ6YXV0byI+Jm5ic3A7PG86cD48L286cD48L3A+DQo8
L2Rpdj4NCjxibG9ja3F1b3RlIHN0eWxlPSJib3JkZXI6bm9uZTtib3JkZXItbGVmdDpzb2xpZCAj
Q0NDQ0NDIDEuMHB0O3BhZGRpbmc6MGluIDBpbiAwaW4gNi4wcHQ7bWFyZ2luLWxlZnQ6NC44cHQ7
bWFyZ2luLXRvcDo1LjBwdDttYXJnaW4tcmlnaHQ6MGluO21hcmdpbi1ib3R0b206NS4wcHQiPg0K
PGRpdj4NCjxkaXY+DQo8cCBjbGFzcz0iTXNvTm9ybWFsIiBzdHlsZT0ibXNvLW1hcmdpbi10b3At
YWx0OmF1dG87bXNvLW1hcmdpbi1ib3R0b20tYWx0OmF1dG8iPkVsaW90PG86cD48L286cD48L3A+
DQo8L2Rpdj4NCjxkaXY+DQo8cCBjbGFzcz0iTXNvTm9ybWFsIiBzdHlsZT0ibXNvLW1hcmdpbi10
b3AtYWx0OmF1dG87bXNvLW1hcmdpbi1ib3R0b20tYWx0OmF1dG8iPiZuYnNwOzxvOnA+PC9vOnA+
PC9wPg0KPGRpdj4NCjxibG9ja3F1b3RlIHN0eWxlPSJtYXJnaW4tdG9wOjUuMHB0O21hcmdpbi1i
b3R0b206NS4wcHQiPg0KPGRpdj4NCjxwIGNsYXNzPSJNc29Ob3JtYWwiIHN0eWxlPSJtc28tbWFy
Z2luLXRvcC1hbHQ6YXV0bzttc28tbWFyZ2luLWJvdHRvbS1hbHQ6YXV0byI+T24gMjEgT2N0IDIw
MjAsIGF0IDExOjAyLCBIYW5uZXMgVHNjaG9mZW5pZyAmbHQ7PGEgaHJlZj0ibWFpbHRvOkhhbm5l
cy5Uc2Nob2ZlbmlnQGFybS5jb20iIHRhcmdldD0iX2JsYW5rIj5IYW5uZXMuVHNjaG9mZW5pZ0Bh
cm0uY29tPC9hPiZndDsgd3JvdGU6PG86cD48L286cD48L3A+DQo8L2Rpdj4NCjxwIGNsYXNzPSJN
c29Ob3JtYWwiIHN0eWxlPSJtc28tbWFyZ2luLXRvcC1hbHQ6YXV0bzttc28tbWFyZ2luLWJvdHRv
bS1hbHQ6YXV0byI+Jm5ic3A7PG86cD48L286cD48L3A+DQo8ZGl2Pg0KPGRpdj4NCjxkaXY+DQo8
cCBjbGFzcz0iTXNvTm9ybWFsIiBzdHlsZT0ibXNvLW1hcmdpbi10b3AtYWx0OmF1dG87bXNvLW1h
cmdpbi1ib3R0b20tYWx0OmF1dG8iPkhpIGFsbCwmbmJzcDs8bzpwPjwvbzpwPjwvcD4NCjwvZGl2
Pg0KPGRpdj4NCjxwIGNsYXNzPSJNc29Ob3JtYWwiIHN0eWxlPSJtc28tbWFyZ2luLXRvcC1hbHQ6
YXV0bzttc28tbWFyZ2luLWJvdHRvbS1hbHQ6YXV0byI+Jm5ic3A7PG86cD48L286cD48L3A+DQo8
L2Rpdj4NCjxkaXY+DQo8cCBjbGFzcz0iTXNvTm9ybWFsIiBzdHlsZT0ibXNvLW1hcmdpbi10b3At
YWx0OmF1dG87bXNvLW1hcmdpbi1ib3R0b20tYWx0OmF1dG8iPnRoaXMgZHJhZnQgbWFuZGF0ZXMg
T0NTQ1Agc3RhcGxpbmcgKGZvciB1c2Ugd2l0aCBUTFMgMS4zIGluIEVBUC1UTFMpIGFuZCBJIGJl
bGlldmUgdGhpcyBpcyBhIHByb2JsZW0gZm9yIGltcGxlbWVudGF0aW9ucy4gVGhpcyBleHRyYSBi
dXJkZW4gaXMgSU1ITyB1bmp1c3RpZmllZC4gRm9yIHRoZSB0eXBlIG9mDQogZGVwbG95bWVudHMg
d2hlcmUgRUFQIGlzIHVzZWQgdGhlcmUgaXMgbm8gbmVlZCBmb3IgYSBtYW5kYXRvcnkgY2VydGlm
aWNhdGUgcmV2b2NhdGlvbiBjaGVja2luZyB3aXRoIE9DU1AuPG86cD48L286cD48L3A+DQo8L2Rp
dj4NCjxkaXY+DQo8cCBjbGFzcz0iTXNvTm9ybWFsIiBzdHlsZT0ibXNvLW1hcmdpbi10b3AtYWx0
OmF1dG87bXNvLW1hcmdpbi1ib3R0b20tYWx0OmF1dG8iPiZuYnNwOzxvOnA+PC9vOnA+PC9wPg0K
PC9kaXY+DQo8ZGl2Pg0KPHAgY2xhc3M9Ik1zb05vcm1hbCIgc3R5bGU9Im1zby1tYXJnaW4tdG9w
LWFsdDphdXRvO21zby1tYXJnaW4tYm90dG9tLWFsdDphdXRvIj5IYXZpbmcgaXQgb3B0aW9uYWws
IGxpa2UgdGhlIHVzZSBvZiBtYW55IG90aGVyIFRMUyBleHRlbnNpb25zLCBpcyBmaW5lIGZvciBt
ZS4gRldJVyBldmVuIFRMUyAxLjMsIHdoaWNoIGlzIHVzZWQgaW4gYSBtb3JlIGdlbmVyaWMgZW52
aXJvbm1lbnQsIGRvZXMgbm90IG1hbmRhdGUgdGhlIHVzZSBvZiBPQ1NQIHN0YXBsaW5nLjxvOnA+
PC9vOnA+PC9wPg0KPC9kaXY+DQo8ZGl2Pg0KPHAgY2xhc3M9Ik1zb05vcm1hbCIgc3R5bGU9Im1z
by1tYXJnaW4tdG9wLWFsdDphdXRvO21zby1tYXJnaW4tYm90dG9tLWFsdDphdXRvIj4mbmJzcDs8
bzpwPjwvbzpwPjwvcD4NCjwvZGl2Pg0KPGRpdj4NCjxwIGNsYXNzPSJNc29Ob3JtYWwiIHN0eWxl
PSJtc28tbWFyZ2luLXRvcC1hbHQ6YXV0bzttc28tbWFyZ2luLWJvdHRvbS1hbHQ6YXV0byI+VGhp
cyByZXF1aXJlbWVudCB3aWxsIG1ha2UgdGhlIHByb2JsZW0gZGVzY3JpYmVkIGluIGRyYWZ0LWll
dGYtZW11LWVhcHRsc2NlcnQgd29yc2UuIEkgYW0gc3VyZSB0aGUgYXV0aG9ycyBhcmUgYXdhcmUg
b2YgdGhpcyBmYWN0IHNpbmNlIHRoZXkgYXJlIGFsc28gY28tYXV0aG9ycyBvZiBkcmFmdC1pZXRm
LWVtdS1lYXB0bHNjZXJ0LjxvOnA+PC9vOnA+PC9wPg0KPC9kaXY+DQo8ZGl2Pg0KPHAgY2xhc3M9
Ik1zb05vcm1hbCIgc3R5bGU9Im1zby1tYXJnaW4tdG9wLWFsdDphdXRvO21zby1tYXJnaW4tYm90
dG9tLWFsdDphdXRvIj4mbmJzcDs8bzpwPjwvbzpwPjwvcD4NCjwvZGl2Pg0KPGRpdj4NCjxwIGNs
YXNzPSJNc29Ob3JtYWwiIHN0eWxlPSJtc28tbWFyZ2luLXRvcC1hbHQ6YXV0bzttc28tbWFyZ2lu
LWJvdHRvbS1hbHQ6YXV0byI+Q2lhbzxvOnA+PC9vOnA+PC9wPg0KPC9kaXY+DQo8ZGl2Pg0KPHAg
Y2xhc3M9Ik1zb05vcm1hbCIgc3R5bGU9Im1zby1tYXJnaW4tdG9wLWFsdDphdXRvO21zby1tYXJn
aW4tYm90dG9tLWFsdDphdXRvIj5IYW5uZXM8bzpwPjwvbzpwPjwvcD4NCjwvZGl2Pg0KPC9kaXY+
DQo8cCBjbGFzcz0iTXNvTm9ybWFsIiBzdHlsZT0ibXNvLW1hcmdpbi10b3AtYWx0OmF1dG87bXNv
LW1hcmdpbi1ib3R0b20tYWx0OmF1dG8iPjxzcGFuIHN0eWxlPSJmb250LXNpemU6MTIuMHB0O2Zv
bnQtZmFtaWx5OiZxdW90O0hlbHZldGljYSZxdW90OyxzYW5zLXNlcmlmIj5JTVBPUlRBTlQgTk9U
SUNFOiBUaGUgY29udGVudHMgb2YgdGhpcyBlbWFpbCBhbmQgYW55IGF0dGFjaG1lbnRzIGFyZSBj
b25maWRlbnRpYWwgYW5kIG1heSBhbHNvIGJlIHByaXZpbGVnZWQuIElmDQogeW91IGFyZSBub3Qg
dGhlIGludGVuZGVkIHJlY2lwaWVudCwgcGxlYXNlIG5vdGlmeSB0aGUgc2VuZGVyIGltbWVkaWF0
ZWx5IGFuZCBkbyBub3QgZGlzY2xvc2UgdGhlIGNvbnRlbnRzIHRvIGFueSBvdGhlciBwZXJzb24s
IHVzZSBpdCBmb3IgYW55IHB1cnBvc2UsIG9yIHN0b3JlIG9yIGNvcHkgdGhlIGluZm9ybWF0aW9u
IGluIGFueSBtZWRpdW0uIFRoYW5rIHlvdS4gX19fX19fX19fX19fX19fX19fX19fX19fX19fX19f
X19fX19fX19fX19fX19fX188YnI+DQpFbXUgbWFpbGluZyBsaXN0PGJyPg0KPC9zcGFuPjxhIGhy
ZWY9Im1haWx0bzpFbXVAaWV0Zi5vcmciIHRhcmdldD0iX2JsYW5rIj48c3BhbiBzdHlsZT0iZm9u
dC1zaXplOjEyLjBwdDtmb250LWZhbWlseTomcXVvdDtIZWx2ZXRpY2EmcXVvdDssc2Fucy1zZXJp
ZiI+RW11QGlldGYub3JnPC9zcGFuPjwvYT48c3BhbiBzdHlsZT0iZm9udC1zaXplOjEyLjBwdDtm
b250LWZhbWlseTomcXVvdDtIZWx2ZXRpY2EmcXVvdDssc2Fucy1zZXJpZiI+PGJyPg0KPC9zcGFu
PjxhIGhyZWY9Imh0dHBzOi8vd3d3LmlldGYub3JnL21haWxtYW4vbGlzdGluZm8vZW11IiB0YXJn
ZXQ9Il9ibGFuayI+PHNwYW4gc3R5bGU9ImZvbnQtc2l6ZToxMi4wcHQ7Zm9udC1mYW1pbHk6JnF1
b3Q7SGVsdmV0aWNhJnF1b3Q7LHNhbnMtc2VyaWYiPmh0dHBzOi8vd3d3LmlldGYub3JnL21haWxt
YW4vbGlzdGluZm8vZW11PC9zcGFuPjwvYT48bzpwPjwvbzpwPjwvcD4NCjwvZGl2Pg0KPC9ibG9j
a3F1b3RlPg0KPC9kaXY+DQo8cCBjbGFzcz0iTXNvTm9ybWFsIiBzdHlsZT0ibXNvLW1hcmdpbi10
b3AtYWx0OmF1dG87bXNvLW1hcmdpbi1ib3R0b20tYWx0OmF1dG8iPiZuYnNwOzxvOnA+PC9vOnA+
PC9wPg0KPC9kaXY+DQo8L2Rpdj4NCjxwIGNsYXNzPSJNc29Ob3JtYWwiIHN0eWxlPSJtc28tbWFy
Z2luLXRvcC1hbHQ6YXV0bzttc28tbWFyZ2luLWJvdHRvbS1hbHQ6YXV0byI+X19fX19fX19fX19f
X19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX188YnI+DQpFbXUgbWFpbGluZyBsaXN0
PGJyPg0KPGEgaHJlZj0ibWFpbHRvOkVtdUBpZXRmLm9yZyIgdGFyZ2V0PSJfYmxhbmsiPkVtdUBp
ZXRmLm9yZzwvYT48YnI+DQo8YSBocmVmPSJodHRwczovL3d3dy5pZXRmLm9yZy9tYWlsbWFuL2xp
c3RpbmZvL2VtdSIgdGFyZ2V0PSJfYmxhbmsiPmh0dHBzOi8vd3d3LmlldGYub3JnL21haWxtYW4v
bGlzdGluZm8vZW11PC9hPjxvOnA+PC9vOnA+PC9wPg0KPC9ibG9ja3F1b3RlPg0KPC9kaXY+DQo8
L2Rpdj4NCjwvZGl2Pg0KPHAgY2xhc3M9Ik1zb05vcm1hbCI+SU1QT1JUQU5UIE5PVElDRTogVGhl
IGNvbnRlbnRzIG9mIHRoaXMgZW1haWwgYW5kIGFueSBhdHRhY2htZW50cyBhcmUgY29uZmlkZW50
aWFsIGFuZCBtYXkgYWxzbyBiZSBwcml2aWxlZ2VkLiBJZiB5b3UgYXJlIG5vdCB0aGUgaW50ZW5k
ZWQgcmVjaXBpZW50LCBwbGVhc2Ugbm90aWZ5IHRoZSBzZW5kZXIgaW1tZWRpYXRlbHkgYW5kIGRv
IG5vdCBkaXNjbG9zZSB0aGUgY29udGVudHMgdG8gYW55IG90aGVyIHBlcnNvbiwNCiB1c2UgaXQg
Zm9yIGFueSBwdXJwb3NlLCBvciBzdG9yZSBvciBjb3B5IHRoZSBpbmZvcm1hdGlvbiBpbiBhbnkg
bWVkaXVtLiBUaGFuayB5b3UuDQo8bzpwPjwvbzpwPjwvcD4NCjwvZGl2Pg0KPC9ibG9ja3F1b3Rl
Pg0KPC9kaXY+DQo8L2Rpdj4NCjwvZGl2Pg0KSU1QT1JUQU5UIE5PVElDRTogVGhlIGNvbnRlbnRz
IG9mIHRoaXMgZW1haWwgYW5kIGFueSBhdHRhY2htZW50cyBhcmUgY29uZmlkZW50aWFsIGFuZCBt
YXkgYWxzbyBiZSBwcml2aWxlZ2VkLiBJZiB5b3UgYXJlIG5vdCB0aGUgaW50ZW5kZWQgcmVjaXBp
ZW50LCBwbGVhc2Ugbm90aWZ5IHRoZSBzZW5kZXIgaW1tZWRpYXRlbHkgYW5kIGRvIG5vdCBkaXNj
bG9zZSB0aGUgY29udGVudHMgdG8gYW55IG90aGVyIHBlcnNvbiwgdXNlIGl0IGZvciBhbnkgcHVy
cG9zZSwNCiBvciBzdG9yZSBvciBjb3B5IHRoZSBpbmZvcm1hdGlvbiBpbiBhbnkgbWVkaXVtLiBU
aGFuayB5b3UuDQo8L2JvZHk+DQo8L2h0bWw+DQo=

--_000_AM0PR08MB3716466445022163A7C624AAFA160AM0PR08MB3716eurp_--


From nobody Tue Oct 27 11:54:00 2020
Return-Path: <joe@salowey.net>
X-Original-To: emu@ietfa.amsl.com
Delivered-To: emu@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 1053C3A14C5 for <emu@ietfa.amsl.com>; Tue, 27 Oct 2020 11:53:58 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.898
X-Spam-Level: 
X-Spam-Status: No, score=-1.898 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, HTML_MESSAGE=0.001, SPF_HELO_NONE=0.001, SPF_PASS=-0.001, URIBL_BLOCKED=0.001] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (2048-bit key) header.d=salowey-net.20150623.gappssmtp.com
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 Pe8nVFxIRU2S for <emu@ietfa.amsl.com>; Tue, 27 Oct 2020 11:53:56 -0700 (PDT)
Received: from mail-qt1-x831.google.com (mail-qt1-x831.google.com [IPv6:2607:f8b0:4864:20::831]) (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 6374E3A164F for <emu@ietf.org>; Tue, 27 Oct 2020 11:53:34 -0700 (PDT)
Received: by mail-qt1-x831.google.com with SMTP id p45so1656899qtb.5 for <emu@ietf.org>; Tue, 27 Oct 2020 11:53:34 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=salowey-net.20150623.gappssmtp.com; s=20150623; h=mime-version:references:in-reply-to:from:date:message-id:subject:to :cc; bh=frQEG0uaQbiyU0Tj/06Iyb06awxZMsSHpkzm4MDIhEU=; b=PoPdt6ATG06tFSLYTexvEo71MhyziRXdZmJyJ13I+ThtrAI1IxgGiX/eoJBC5rE+gO tSt52ycd97LvGcE4F4tsvKoJ7RqBVHcLiaguqSXf4sgrleHBs9QuZ7ZMqvo32PoUx4V2 8PNvtZy5+F3GP7wDYSjm8aDbR2QdukMBesP2t/wMAkIdsRwdyGHa4Pq7PVTOcR1LjXWF G/I2y246I7nZUGmn0ZCJjPNXkXBNhF0P9v5XjOtDkFXpjo/wDcE0m/jNN03T6PXVOdoU 4iOh8WB20HPmsuaQOgJhQrSCGruLtDiY9KuVc+0DCevqe9ssdNSiyBMfTYUd0k4OXqap 0s7w==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:mime-version:references:in-reply-to:from:date :message-id:subject:to:cc; bh=frQEG0uaQbiyU0Tj/06Iyb06awxZMsSHpkzm4MDIhEU=; b=H8z8ytTnL/AFjPevANXVGWlxVEj9dQT1G2hE6BU71omcSwYsQGh5wzQyxtPn7NxcL+ E8Uhg4WBa6w5w/ygmXQKvxzCRVSEb6ami/3maZvLfmITa0G6hxrkT8V8F9/1vaRI39nD A789AqZHmbrW401MrMKb1YE3BTsueF35Jp6hMT407TlzRzBoOUblom5agxs8JXhdBONT usOewjlbgyE3wWl10LlybDjQh65AbprZsJwotIi6/30X1eUoeHa7wc7YdYnJ3gpKhdbv gZrw0oPut85eSKjfJm2hLG6OHgEdu+unrgolSR1sk5ax2x4AR3wQc7WAlLEGuQbuxLG2 7Leg==
X-Gm-Message-State: AOAM533N+ts7Nr9esqRbiksSgQvoDlEWs0xlJpBYAHroEhLNRPPRHwU6 K5mHdd4K2Q1BCusmkbDWG4HjMrP8+4jHWjE73C6/P6TizynIAw==
X-Google-Smtp-Source: ABdhPJyouNAFulCOBUp/1q2hl7njS9vLrSBYzuJB1SEpFX7TbQKu9AKuBqcRycEJZLxW260wSyUDivQtgcbzNKxsnSU=
X-Received: by 2002:ac8:120a:: with SMTP id x10mr3421660qti.95.1603824813309;  Tue, 27 Oct 2020 11:53:33 -0700 (PDT)
MIME-Version: 1.0
References: <AM0PR08MB371647618F993B8C5BA6EB5FFA1C0@AM0PR08MB3716.eurprd08.prod.outlook.com> <AD94F3FF-31A7-4F44-95F7-6A7E70FA8D27@cisco.com> <CAOgPGoD3MQu=Hv6HTfug0XredaRt_T7oD7z_uwnATmHku9DmLg@mail.gmail.com> <AM0PR08MB371649BBA92B7F624008D0B3FA1A0@AM0PR08MB3716.eurprd08.prod.outlook.com> <CAOgPGoDaC893pAwfsEj5DNdKwd+z4_HmsOGZ2y8ruDs12Sx+kg@mail.gmail.com> <AM0PR08MB3716466445022163A7C624AAFA160@AM0PR08MB3716.eurprd08.prod.outlook.com>
In-Reply-To: <AM0PR08MB3716466445022163A7C624AAFA160@AM0PR08MB3716.eurprd08.prod.outlook.com>
From: Joseph Salowey <joe@salowey.net>
Date: Tue, 27 Oct 2020 11:53:22 -0700
Message-ID: <CAOgPGoBOJip2v1h7L-jZWKMwgDMmEGVr1M7nSK_CE5fAnFwhOA@mail.gmail.com>
To: Hannes Tschofenig <Hannes.Tschofenig@arm.com>
Cc: Eliot Lear <lear=40cisco.com@dmarc.ietf.org>, "emu@ietf.org" <emu@ietf.org>
Content-Type: multipart/alternative; boundary="00000000000047a0dd05b2ab906c"
Archived-At: <https://mailarchive.ietf.org/arch/msg/emu/UpdZpKhG9RK2ixlff0lsD-fLifU>
Subject: Re: [Emu] draft-ietf-emu-eap-tls13-11: OCSP Stapling
X-BeenThere: emu@ietf.org
X-Mailman-Version: 2.1.29
Precedence: list
List-Id: "EAP Methods Update \(EMU\)" <emu.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/emu>, <mailto:emu-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/emu/>
List-Post: <mailto:emu@ietf.org>
List-Help: <mailto:emu-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/emu>, <mailto:emu-request@ietf.org?subject=subscribe>
X-List-Received-Date: Tue, 27 Oct 2020 18:53:58 -0000

--00000000000047a0dd05b2ab906c
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable

On Tue, Oct 27, 2020 at 11:27 AM Hannes Tschofenig <
Hannes.Tschofenig@arm.com> wrote:

> Hi Joe,
>
>
>
> a few remarks below.
>
>
>
>
>
> On Fri, Oct 23, 2020 at 12:38 AM Hannes Tschofenig <
> Hannes.Tschofenig@arm.com> wrote:
>
> Hi Joe,
>
>
>
> I do not understand certificate revocation checking is a topic specific t=
o
> the use of TLS 1.3 in EAP-TLS.
>
>
>
> [Joe]  TLS 1.3 discusses OCSP and (SCT).  OCSP stapling is a revocation
> mechanism that will work when the EAP-TLS client does not have connectivi=
ty
> yet, which is a common case in EAP-TLS deployments.    The way the draft =
is
> written now it mandates that this mechanism be used and implements.  TLS
> 1.3 does not require this.
>
>
>
> [hannes] It is also common to give network access to devices that need a
> software update or configuration changes.
>
>
>
> What do you expect to happen if the device finds out that the certificate
> offered by the server has expired?
>
>
>
[Joe] If the server is offering an expired or revoked certificate then that
needs to be remedied on the server.


>
>
> If this topic is important to the group then why isn=E2=80=99t this a gen=
eric
> recommendations for all EAP methods that use public key based
> authentication?
>
>
>
>
>
> [Joe] Certificate revocation is specific to the use of certificates.
>
>
>
> [Hannes] Many EAP methods use certificates but they do not mandate the us=
e
> of OCSP.
>
>
>
> Wouldn=E2=80=99t this be a topic to address in <draft-ietf-emu-eaptlscert=
>? IMHO
> this would make more sense given that <draft-ietf-emu-eaptlscert> talks
> about large certificates and long certificate chains and any proposal to
> make those even larger should be evaluated in this context.
>
>
>
>
>
> [Joe] No, <draft-ietf-emu-eaptlscert> discusses handling large
> certificates not revocation.
>
>
>
> [Hannes] Here the problem description that motivates
> <draft-ietf-emu-eaptlscert>
>
> =E2=80=9C
>
> Large certificates and long
>
>    certificate chains combined with authenticators that drop an EAP
>
>    session after only 40 - 50 round-trips is a major deployment problem.
>
>    This document looks at the this problem in detail and describes the
>
>    potential solutions available.
>
> =E2=80=9C
>
> OCSP information travels alongside the certificates and therefore
> increases the problem outlined by <draft-ietf-emu-eaptlscert>
>
>
>
> EAP-TLS is the right place to discuss revocation issues.
>
>
>
> It seems there are several questions that need to be answered:
>
>
>
>    1. Should the document mandate that OCSP stapling be used?
>
> [Hannes] No.
>
>
>
> 2. Should the document mandate that OCSP stapling be implemented?
>
> [Hannes] No.
>
>
>
> 3. What should the document say in the security sections with respect to
> OCSP stapling and other mechanisms?
>
> [Hannes] IMHO TLS 1.3 says the relevant solution parts. OCSP stapling is
> available for use in TLS 1.3 and it is one suitable mechanism for
> certificate revocation.
>
>
>
> Do any of these recommendations also apply to EAP-TLS with TLS 1.2 as wel=
l
> (since it also offers OCSP stapling)? Would the recommendations also appl=
y
> to EAP methods that use TLS under the hood, such as TEAP, EAP-FAST, or
> EAP-TTLS? Would they apply to methods like EAP-IKEv2 or the recently
> suggested EAP-EDHOC, which are also methods that use certificates?
>

[Joe] the document under consideration is EAP-TLS 1.3.   In my opinion any
document that deals with certificates ought to have some discussion on
revocation.  In particular, EAP is deployed into an environment where some
revocation mechanisms may not work as expected because there is no network
access available to do out of band checks.


>
>
> Ciao
>
> Hannes
>
>
>
> Ciao
>
> Hannes
>
>
>
> *From:* Joseph Salowey <joe@salowey.net>
> *Sent:* Thursday, October 22, 2020 11:12 PM
> *To:* Eliot Lear <lear=3D40cisco.com@dmarc.ietf.org>
> *Cc:* Hannes Tschofenig <Hannes.Tschofenig@arm.com>; emu@ietf.org
> *Subject:* Re: [Emu] draft-ietf-emu-eap-tls13-11: OCSP Stapling
>
>
>
>
>
>
>
> On Thu, Oct 22, 2020 at 8:08 AM Eliot Lear <lear=3D
> 40cisco.com@dmarc.ietf.org> wrote:
>
> +1.  How does anyone even do OCSP without having first gotten onto the
> network?
>
>
>
>
>
> [Joe] THat is what OCSP stapling is supposed to solve since the OCSP
> messages are sent in the TLS handshake.   I believe there are some EAP-TL=
S
> implementations that support OCSP, but I am not sure if it is actually
> deployed.
>
>
>
> Eliot
>
>
>
> On 21 Oct 2020, at 11:02, Hannes Tschofenig <Hannes.Tschofenig@arm.com>
> wrote:
>
>
>
> Hi all,
>
>
>
> this draft mandates OCSCP stapling (for use with TLS 1.3 in EAP-TLS) and =
I
> believe this is a problem for implementations. This extra burden is IMHO
> unjustified. For the type of deployments where EAP is used there is no ne=
ed
> for a mandatory certificate revocation checking with OCSP.
>
>
>
> Having it optional, like the use of many other TLS extensions, is fine fo=
r
> me. FWIW even TLS 1.3, which is used in a more generic environment, does
> not mandate the use of OCSP stapling.
>
>
>
> This requirement will make the problem described in
> draft-ietf-emu-eaptlscert worse. I am sure the authors are aware of this
> fact since they are also co-authors of draft-ietf-emu-eaptlscert.
>
>
>
> Ciao
>
> Hannes
>
> IMPORTANT NOTICE: The contents of this email and any attachments are
> confidential and may also be privileged. If you are not the intended
> recipient, please notify the sender immediately and do not disclose the
> contents to any other person, use it for any purpose, or store or copy th=
e
> information in any medium. Thank you.
> _______________________________________________
> Emu mailing list
> Emu@ietf.org
> https://www.ietf.org/mailman/listinfo/emu
>
>
>
> _______________________________________________
> Emu mailing list
> Emu@ietf.org
> https://www.ietf.org/mailman/listinfo/emu
>
> IMPORTANT NOTICE: The contents of this email and any attachments are
> confidential and may also be privileged. If you are not the intended
> recipient, please notify the sender immediately and do not disclose the
> contents to any other person, use it for any purpose, or store or copy th=
e
> information in any medium. Thank you.
>
> IMPORTANT NOTICE: The contents of this email and any attachments are
> confidential and may also be privileged. If you are not the intended
> recipient, please notify the sender immediately and do not disclose the
> contents to any other person, use it for any purpose, or store or copy th=
e
> information in any medium. Thank you.
>

--00000000000047a0dd05b2ab906c
Content-Type: text/html; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable

<div dir=3D"ltr"><div dir=3D"ltr"><br></div><br><div class=3D"gmail_quote">=
<div dir=3D"ltr" class=3D"gmail_attr">On Tue, Oct 27, 2020 at 11:27 AM Hann=
es Tschofenig &lt;<a href=3D"mailto:Hannes.Tschofenig@arm.com">Hannes.Tscho=
fenig@arm.com</a>&gt; wrote:<br></div><blockquote class=3D"gmail_quote" sty=
le=3D"margin:0px 0px 0px 0.8ex;border-left:1px solid rgb(204,204,204);paddi=
ng-left:1ex">





<div lang=3D"EN-US" style=3D"overflow-wrap: break-word;">
<div class=3D"gmail-m_-7676623449542533801WordSection1">
<p class=3D"MsoNormal">Hi Joe, <u></u><u></u></p>
<p class=3D"MsoNormal"><u></u>=C2=A0<u></u></p>
<p class=3D"MsoNormal">a few remarks below. <u></u><u></u></p>
<div>
<div>
<p class=3D"MsoNormal"><u></u>=C2=A0<u></u></p>
</div>
<p class=3D"MsoNormal"><u></u>=C2=A0<u></u></p>
<div>
<div>
<p class=3D"MsoNormal">On Fri, Oct 23, 2020 at 12:38 AM Hannes Tschofenig &=
lt;<a href=3D"mailto:Hannes.Tschofenig@arm.com" target=3D"_blank">Hannes.Ts=
chofenig@arm.com</a>&gt; wrote:<u></u><u></u></p>
</div>
<blockquote style=3D"border-top:none;border-right:none;border-bottom:none;b=
order-left:1pt solid rgb(204,204,204);padding:0in 0in 0in 6pt;margin-left:4=
.8pt;margin-right:0in">
<div>
<div>
<p class=3D"MsoNormal">Hi Joe,
<u></u><u></u></p>
<p class=3D"MsoNormal">=C2=A0<u></u><u></u></p>
<p class=3D"MsoNormal">I do not understand certificate revocation checking =
is a topic specific to the use of TLS 1.3 in EAP-TLS.
<u></u><u></u></p>
</div>
</div>
</blockquote>
<div>
<p class=3D"MsoNormal">=C2=A0<u></u><u></u></p>
</div>
<div>
<p class=3D"MsoNormal">[Joe]=C2=A0 TLS 1.3 discusses=C2=A0OCSP and (SCT).=
=C2=A0 OCSP stapling is a revocation mechanism that will work when the EAP-=
TLS client does not have connectivity yet, which is a common case in EAP-TL=
S deployments.=C2=A0 =C2=A0 The way the draft is written now
 it mandates that this mechanism be used and implements.=C2=A0 TLS 1.3 does=
 not require this.=C2=A0=C2=A0<u></u><u></u></p>
</div>
<div>
<p class=3D"MsoNormal"><u></u>=C2=A0<u></u></p>
<p class=3D"MsoNormal">[hannes] It is also common to give network access to=
 devices that need a software update or configuration changes.
<u></u><u></u></p>
<p class=3D"MsoNormal"><u></u>=C2=A0<u></u></p>
<p class=3D"MsoNormal">What do you expect to happen if the device finds out=
 that the certificate offered by the server has expired?
<u></u><u></u></p>
<p class=3D"MsoNormal">=C2=A0</p></div></div></div></div></div></blockquote=
><div>[Joe] If the server is offering an expired or revoked certificate the=
n that needs to be remedied on the server.=C2=A0=C2=A0</div><div>=C2=A0</di=
v><blockquote class=3D"gmail_quote" style=3D"margin:0px 0px 0px 0.8ex;borde=
r-left:1px solid rgb(204,204,204);padding-left:1ex"><div lang=3D"EN-US" sty=
le=3D"overflow-wrap: break-word;"><div class=3D"gmail-m_-767662344954253380=
1WordSection1"><div><div><div><p class=3D"MsoNormal"><u></u><u></u></p>
<p class=3D"MsoNormal"><u></u>=C2=A0<u></u></p>
</div>
<blockquote style=3D"border-top:none;border-right:none;border-bottom:none;b=
order-left:1pt solid rgb(204,204,204);padding:0in 0in 0in 6pt;margin-left:4=
.8pt;margin-right:0in">
<div>
<div>
<p class=3D"MsoNormal">If this topic is important to the group then why isn=
=E2=80=99t this a generic recommendations for all EAP methods that use publ=
ic key based authentication?
<u></u><u></u></p>
<p class=3D"MsoNormal">=C2=A0<u></u><u></u></p>
</div>
</div>
</blockquote>
<div>
<p class=3D"MsoNormal"><u></u>=C2=A0<u></u></p>
</div>
<div>
<p class=3D"MsoNormal">[Joe] Certificate revocation is specific to the use =
of certificates.=C2=A0<u></u><u></u></p>
</div>
<div>
<p class=3D"MsoNormal">=C2=A0<u></u><u></u></p>
<p class=3D"MsoNormal">[Hannes] Many EAP methods use certificates but they =
do not mandate the use of OCSP.
<u></u><u></u></p>
<p class=3D"MsoNormal"><u></u>=C2=A0<u></u></p>
</div>
<blockquote style=3D"border-top:none;border-right:none;border-bottom:none;b=
order-left:1pt solid rgb(204,204,204);padding:0in 0in 0in 6pt;margin-left:4=
.8pt;margin-right:0in">
<div>
<div>
<p class=3D"MsoNormal">Wouldn=E2=80=99t this be a topic to address in &lt;d=
raft-ietf-emu-eaptlscert&gt;? IMHO this would make more sense given that &l=
t;draft-ietf-emu-eaptlscert&gt; talks about large certificates and long
 certificate chains and any proposal to make those even larger should be ev=
aluated in this context.
<u></u><u></u></p>
<p class=3D"MsoNormal">=C2=A0<u></u><u></u></p>
</div>
</div>
</blockquote>
<div>
<p class=3D"MsoNormal"><u></u>=C2=A0<u></u></p>
</div>
<div>
<p class=3D"MsoNormal">[Joe] No, &lt;draft-ietf-emu-eaptlscert&gt; discusse=
s handling large certificates not revocation.=C2=A0<u></u><u></u></p>
<p class=3D"MsoNormal"><u></u>=C2=A0<u></u></p>
<p class=3D"MsoNormal">[Hannes] Here the problem description that motivates=
 &lt;draft-ietf-emu-eaptlscert&gt;<u></u><u></u></p>
<p class=3D"MsoNormal"><span style=3D"font-size:10pt;font-family:&quot;Cour=
ier New&quot;">=E2=80=9C<u></u><u></u></span></p>
<p class=3D"MsoNormal"><span style=3D"font-size:10pt;font-family:&quot;Cour=
ier New&quot;">Large certificates and long<u></u><u></u></span></p>
<p class=3D"MsoNormal"><span style=3D"font-size:10pt;font-family:&quot;Cour=
ier New&quot;">=C2=A0=C2=A0 certificate chains combined with authenticators=
 that drop an EAP<u></u><u></u></span></p>
<p class=3D"MsoNormal"><span style=3D"font-size:10pt;font-family:&quot;Cour=
ier New&quot;">=C2=A0=C2=A0 session after only 40 - 50 round-trips is a maj=
or deployment problem.<u></u><u></u></span></p>
<p class=3D"MsoNormal"><span style=3D"font-size:10pt;font-family:&quot;Cour=
ier New&quot;">=C2=A0=C2=A0 This document looks at the this problem in deta=
il and describes the<u></u><u></u></span></p>
<p class=3D"MsoNormal"><span style=3D"font-size:10pt;font-family:&quot;Cour=
ier New&quot;">=C2=A0=C2=A0 potential solutions available.<u></u><u></u></s=
pan></p>
<p class=3D"MsoNormal">=E2=80=9C<u></u><u></u></p>
<p class=3D"MsoNormal">OCSP information travels alongside the certificates =
and therefore increases the problem outlined by &lt;draft-ietf-emu-eaptlsce=
rt&gt;<u></u><u></u></p>
<p class=3D"MsoNormal"><u></u>=C2=A0<u></u></p>
<p class=3D"MsoNormal">EAP-TLS is the right place to discuss revocation iss=
ues.=C2=A0<u></u><u></u></p>
<p class=3D"MsoNormal"><u></u>=C2=A0<u></u></p>
<p class=3D"MsoNormal">It seems there are several questions that need to be=
 answered:<u></u><u></u></p>
</div>
<div>
<p class=3D"MsoNormal"><u></u>=C2=A0<u></u></p>
</div>
<div>
<ol style=3D"margin-top:0in" start=3D"1" type=3D"1">
<li class=3D"gmail-m_-7676623449542533801MsoListParagraph" style=3D"margin-=
left:0in">Should the document mandate that OCSP stapling=C2=A0be used?<u></=
u><u></u></li></ol>
<p class=3D"MsoNormal">[Hannes] No. <u></u><u></u></p>
<p class=3D"MsoNormal"><u></u>=C2=A0<u></u></p>
</div>
<div>
<p class=3D"MsoNormal">2. Should the document mandate that OCSP stapling be=
 implemented?<u></u><u></u></p>
</div>
<div>
<p class=3D"MsoNormal">[Hannes] No. <u></u><u></u></p>
<p class=3D"MsoNormal"><u></u>=C2=A0<u></u></p>
<p class=3D"MsoNormal">3. What should the document say in the security sect=
ions with respect to OCSP stapling and other mechanisms?=C2=A0<u></u><u></u=
></p>
</div>
<div>
<p class=3D"MsoNormal">[Hannes] IMHO TLS 1.3 says the relevant solution par=
ts. OCSP stapling is available for use in TLS 1.3 and it is one suitable me=
chanism for certificate revocation.<u></u><u></u></p>
</div>
<div>
<p class=3D"MsoNormal"><u></u>=C2=A0<u></u></p>
<p class=3D"MsoNormal">Do any of these recommendations also apply to EAP-TL=
S with TLS 1.2 as well (since it also offers OCSP stapling)? Would the reco=
mmendations also apply to EAP methods that use TLS under the hood, such as =
TEAP, EAP-FAST, or EAP-TTLS? Would
 they apply to methods like EAP-IKEv2 or the recently suggested EAP-EDHOC, =
which are also methods that use certificates?</p></div></div></div></div></=
div></blockquote><div><br></div><div>[Joe] the document under consideration=
 is EAP-TLS 1.3.=C2=A0 =C2=A0In my opinion any document that deals with cer=
tificates ought to have some discussion on revocation.=C2=A0 In particular,=
 EAP is deployed into an environment where some revocation mechanisms may n=
ot work as expected because=C2=A0there is no network access available to do=
 out of band checks.=C2=A0=C2=A0</div><div>=C2=A0</div><blockquote class=3D=
"gmail_quote" style=3D"margin:0px 0px 0px 0.8ex;border-left:1px solid rgb(2=
04,204,204);padding-left:1ex"><div lang=3D"EN-US" style=3D"overflow-wrap: b=
reak-word;"><div class=3D"gmail-m_-7676623449542533801WordSection1"><div><d=
iv><div><p class=3D"MsoNormal">
<u></u><u></u></p>
</div>
<div>
<p class=3D"MsoNormal"><u></u>=C2=A0<u></u></p>
</div>
<div>
<p class=3D"MsoNormal">Ciao<u></u><u></u></p>
<p class=3D"MsoNormal">Hannes<u></u><u></u></p>
</div>
<div>
<p class=3D"MsoNormal"><u></u>=C2=A0<u></u></p>
</div>
<blockquote style=3D"border-top:none;border-right:none;border-bottom:none;b=
order-left:1pt solid rgb(204,204,204);padding:0in 0in 0in 6pt;margin-left:4=
.8pt;margin-right:0in">
<div>
<div>
<p class=3D"MsoNormal">Ciao<u></u><u></u></p>
<p class=3D"MsoNormal">Hannes<u></u><u></u></p>
<p class=3D"MsoNormal">=C2=A0<u></u><u></u></p>
<div style=3D"border-right:none;border-bottom:none;border-left:none;border-=
top:1pt solid rgb(225,225,225);padding:3pt 0in 0in">
<p class=3D"MsoNormal"><b>From:</b> Joseph Salowey &lt;<a href=3D"mailto:jo=
e@salowey.net" target=3D"_blank">joe@salowey.net</a>&gt;
<br>
<b>Sent:</b> Thursday, October 22, 2020 11:12 PM<br>
<b>To:</b> Eliot Lear &lt;lear=3D<a href=3D"mailto:40cisco.com@dmarc.ietf.o=
rg" target=3D"_blank">40cisco.com@dmarc.ietf.org</a>&gt;<br>
<b>Cc:</b> Hannes Tschofenig &lt;<a href=3D"mailto:Hannes.Tschofenig@arm.co=
m" target=3D"_blank">Hannes.Tschofenig@arm.com</a>&gt;;
<a href=3D"mailto:emu@ietf.org" target=3D"_blank">emu@ietf.org</a><br>
<b>Subject:</b> Re: [Emu] draft-ietf-emu-eap-tls13-11: OCSP Stapling<u></u>=
<u></u></p>
</div>
<p class=3D"MsoNormal">=C2=A0<u></u><u></u></p>
<div>
<div>
<p class=3D"MsoNormal">=C2=A0<u></u><u></u></p>
</div>
<p class=3D"MsoNormal">=C2=A0<u></u><u></u></p>
<div>
<div>
<p class=3D"MsoNormal">On Thu, Oct 22, 2020 at 8:08 AM Eliot Lear &lt;lear=
=3D<a href=3D"mailto:40cisco.com@dmarc.ietf.org" target=3D"_blank">40cisco.=
com@dmarc.ietf.org</a>&gt; wrote:<u></u><u></u></p>
</div>
<blockquote style=3D"border-top:none;border-right:none;border-bottom:none;b=
order-left:1pt solid rgb(204,204,204);padding:0in 0in 0in 6pt;margin:5pt 0i=
n 5pt 4.8pt">
<div>
<p class=3D"MsoNormal">+1.=C2=A0 How does anyone even do OCSP without havin=
g first gotten onto the network?<u></u><u></u></p>
<div>
<p class=3D"MsoNormal">=C2=A0<u></u><u></u></p>
</div>
</div>
</blockquote>
<div>
<p class=3D"MsoNormal">=C2=A0<u></u><u></u></p>
</div>
<div>
<p class=3D"MsoNormal">[Joe] THat is what OCSP stapling is supposed to solv=
e since the OCSP messages are sent in the TLS handshake.=C2=A0 =C2=A0I beli=
eve there are some EAP-TLS implementations that support OCSP,
 but I am not sure if it is actually deployed.=C2=A0=C2=A0<u></u><u></u></p=
>
</div>
<div>
<p class=3D"MsoNormal">=C2=A0<u></u><u></u></p>
</div>
<blockquote style=3D"border-top:none;border-right:none;border-bottom:none;b=
order-left:1pt solid rgb(204,204,204);padding:0in 0in 0in 6pt;margin:5pt 0i=
n 5pt 4.8pt">
<div>
<div>
<p class=3D"MsoNormal">Eliot<u></u><u></u></p>
</div>
<div>
<p class=3D"MsoNormal">=C2=A0<u></u><u></u></p>
<div>
<blockquote style=3D"margin-top:5pt;margin-bottom:5pt">
<div>
<p class=3D"MsoNormal">On 21 Oct 2020, at 11:02, Hannes Tschofenig &lt;<a h=
ref=3D"mailto:Hannes.Tschofenig@arm.com" target=3D"_blank">Hannes.Tschofeni=
g@arm.com</a>&gt; wrote:<u></u><u></u></p>
</div>
<p class=3D"MsoNormal">=C2=A0<u></u><u></u></p>
<div>
<div>
<div>
<p class=3D"MsoNormal">Hi all,=C2=A0<u></u><u></u></p>
</div>
<div>
<p class=3D"MsoNormal">=C2=A0<u></u><u></u></p>
</div>
<div>
<p class=3D"MsoNormal">this draft mandates OCSCP stapling (for use with TLS=
 1.3 in EAP-TLS) and I believe this is a problem for implementations. This =
extra burden is IMHO unjustified. For the type of
 deployments where EAP is used there is no need for a mandatory certificate=
 revocation checking with OCSP.<u></u><u></u></p>
</div>
<div>
<p class=3D"MsoNormal">=C2=A0<u></u><u></u></p>
</div>
<div>
<p class=3D"MsoNormal">Having it optional, like the use of many other TLS e=
xtensions, is fine for me. FWIW even TLS 1.3, which is used in a more gener=
ic environment, does not mandate the use of OCSP stapling.<u></u><u></u></p=
>
</div>
<div>
<p class=3D"MsoNormal">=C2=A0<u></u><u></u></p>
</div>
<div>
<p class=3D"MsoNormal">This requirement will make the problem described in =
draft-ietf-emu-eaptlscert worse. I am sure the authors are aware of this fa=
ct since they are also co-authors of draft-ietf-emu-eaptlscert.<u></u><u></=
u></p>
</div>
<div>
<p class=3D"MsoNormal">=C2=A0<u></u><u></u></p>
</div>
<div>
<p class=3D"MsoNormal">Ciao<u></u><u></u></p>
</div>
<div>
<p class=3D"MsoNormal">Hannes<u></u><u></u></p>
</div>
</div>
<p class=3D"MsoNormal"><span style=3D"font-size:12pt;font-family:Helvetica,=
sans-serif">IMPORTANT NOTICE: The contents of this email and any attachment=
s are confidential and may also be privileged. If
 you are not the intended recipient, please notify the sender immediately a=
nd do not disclose the contents to any other person, use it for any purpose=
, or store or copy the information in any medium. Thank you. ______________=
_________________________________<br>
Emu mailing list<br>
</span><a href=3D"mailto:Emu@ietf.org" target=3D"_blank"><span style=3D"fon=
t-size:12pt;font-family:Helvetica,sans-serif">Emu@ietf.org</span></a><span =
style=3D"font-size:12pt;font-family:Helvetica,sans-serif"><br>
</span><a href=3D"https://www.ietf.org/mailman/listinfo/emu" target=3D"_bla=
nk"><span style=3D"font-size:12pt;font-family:Helvetica,sans-serif">https:/=
/www.ietf.org/mailman/listinfo/emu</span></a><u></u><u></u></p>
</div>
</blockquote>
</div>
<p class=3D"MsoNormal">=C2=A0<u></u><u></u></p>
</div>
</div>
<p class=3D"MsoNormal">_______________________________________________<br>
Emu mailing list<br>
<a href=3D"mailto:Emu@ietf.org" target=3D"_blank">Emu@ietf.org</a><br>
<a href=3D"https://www.ietf.org/mailman/listinfo/emu" target=3D"_blank">htt=
ps://www.ietf.org/mailman/listinfo/emu</a><u></u><u></u></p>
</blockquote>
</div>
</div>
</div>
<p class=3D"MsoNormal">IMPORTANT NOTICE: The contents of this email and any=
 attachments are confidential and may also be privileged. If you are not th=
e intended recipient, please notify the sender immediately and do not discl=
ose the contents to any other person,
 use it for any purpose, or store or copy the information in any medium. Th=
ank you.
<u></u><u></u></p>
</div>
</blockquote>
</div>
</div>
</div>
IMPORTANT NOTICE: The contents of this email and any attachments are confid=
ential and may also be privileged. If you are not the intended recipient, p=
lease notify the sender immediately and do not disclose the contents to any=
 other person, use it for any purpose,
 or store or copy the information in any medium. Thank you.
</div>

</blockquote></div></div>

--00000000000047a0dd05b2ab906c--


From nobody Tue Oct 27 11:58:19 2020
Return-Path: <joe@salowey.net>
X-Original-To: emu@ietfa.amsl.com
Delivered-To: emu@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id CE7A93A149A for <emu@ietfa.amsl.com>; Tue, 27 Oct 2020 11:58:17 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.898
X-Spam-Level: 
X-Spam-Status: No, score=-1.898 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, HTML_MESSAGE=0.001, SPF_HELO_NONE=0.001, SPF_PASS=-0.001, URIBL_BLOCKED=0.001] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (2048-bit key) header.d=salowey-net.20150623.gappssmtp.com
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 dXK7W6cEvu_O for <emu@ietfa.amsl.com>; Tue, 27 Oct 2020 11:58:16 -0700 (PDT)
Received: from mail-qt1-x82b.google.com (mail-qt1-x82b.google.com [IPv6:2607:f8b0:4864:20::82b]) (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 6AD973A14AC for <emu@ietf.org>; Tue, 27 Oct 2020 11:58:16 -0700 (PDT)
Received: by mail-qt1-x82b.google.com with SMTP id h12so1830760qtu.1 for <emu@ietf.org>; Tue, 27 Oct 2020 11:58:16 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=salowey-net.20150623.gappssmtp.com; s=20150623; h=mime-version:references:in-reply-to:from:date:message-id:subject:to :cc; bh=q/mL9oszdIz+SbmQIe/ge5F2qcJ26fbu1oE0XIqDI4M=; b=tZGQWAk4N2JyLhhrvNDFBiZ31nIWARUDRqKiE7Hof4E5k2XPhh+sN1xj+0J38kenPx pXFkCw+CjQIJFm8j3Wnc+YXPj/8fsAgWw8Gr1noRrEmWh11Lc2hiWTkE/Dim7KyJC5Ox 58bfEroadR/J5vZPOEJCYDbjbvuvyErMNI4uNm93aiQy/d32IxFybYWJqaS8KIfKZOso 1dCzf3EAbtChGUGTtQKFSZd/thJi4Xh6ahBHsQxPbQUyktmk2hKOYNHdb7ntKwncRAFl LkDC8GRH0gW/9rYVoi3B7EtIiunNimHVn0LkUMOuEZtGNSNauNm8080LTJQo5QnFickc hiUQ==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:mime-version:references:in-reply-to:from:date :message-id:subject:to:cc; bh=q/mL9oszdIz+SbmQIe/ge5F2qcJ26fbu1oE0XIqDI4M=; b=GZZbYUVfkEtOmFNeBO1xS+H1ZA1gOrw79dEX2SuiYKwm8oUaD6lymRsbXv+61jvl7G sjgS4eKF4HplJZqgDYLicdxTrcr4cpLpu0hXrxL9UWfTP8u4DkcZcr4/mcJhzKuLbfRd owVEIl6MP64JAxrSdOCP0OouzX2G5eEHMVUKTLbvyeDLiQhdNTwXD8zlY92K/wwnABmZ 9XjeZbP9Cm/j7oyayfK1JCdhPJN74ud3iC0MhbOuSavL32JIAsSAER54J2ylp4d0Dlqk JTNV4Rc5SagjQnKNy3keQ5Df1YB1ByWn7GEhA7yShDikp/b7jFhDBJ8X+4ggWP2HoPYL n4bg==
X-Gm-Message-State: AOAM530DNsP49w5QbFe9QLdmp/FOM7jpZ/cidmC/koragIwFNbDIyHwp K9qFQrBij8C79VBHruWfVIiivUSBNiouD0MaPVUynQ==
X-Google-Smtp-Source: ABdhPJy8eVJAXxQ5cABslqjWNnUmxWj2lWWZ1wkIDX8j2lnAnobgHyOCaKzLMM+r5ORQaes/hr9a0Iwdz0Caf9Q98Ic=
X-Received: by 2002:ac8:67c3:: with SMTP id r3mr3813298qtp.297.1603825095475;  Tue, 27 Oct 2020 11:58:15 -0700 (PDT)
MIME-Version: 1.0
References: <CAOgPGoCg2wRKFVKz2kqkomt7mkp1W98jSh6xLT8z1_uWBMXdmA@mail.gmail.com> <CH2PR21MB138172CE5A552084A62E3AA9D1190@CH2PR21MB1381.namprd21.prod.outlook.com> <CAOgPGoBrNM8Kxuoic7wXmkWjavk_rsewDj8paS4CTR97+e3V_g@mail.gmail.com> <8B94A17A-0EE9-4A05-82FF-C807B2C35555@cisco.com>
In-Reply-To: <8B94A17A-0EE9-4A05-82FF-C807B2C35555@cisco.com>
From: Joseph Salowey <joe@salowey.net>
Date: Tue, 27 Oct 2020 11:58:04 -0700
Message-ID: <CAOgPGoAi2osh83BPBoudkTWe1bjhcZ4pna79t-FicoC1YS9N2g@mail.gmail.com>
To: Eliot Lear <lear@cisco.com>
Cc: Jorge Vergara <jovergar@microsoft.com>, EMU WG <emu@ietf.org>
Content-Type: multipart/alternative; boundary="0000000000001916bd05b2aba140"
Archived-At: <https://mailarchive.ietf.org/arch/msg/emu/MImWo-xkJY6f-vBwaZeX7_4yWJ4>
Subject: Re: [Emu] Proposed Resolution to TEAP Errata 5770
X-BeenThere: emu@ietf.org
X-Mailman-Version: 2.1.29
Precedence: list
List-Id: "EAP Methods Update \(EMU\)" <emu.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/emu>, <mailto:emu-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/emu/>
List-Post: <mailto:emu@ietf.org>
List-Help: <mailto:emu-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/emu>, <mailto:emu-request@ietf.org?subject=subscribe>
X-List-Received-Date: Tue, 27 Oct 2020 18:58:18 -0000

--0000000000001916bd05b2aba140
Content-Type: text/plain; charset="UTF-8"

On Tue, Oct 27, 2020 at 12:23 AM Eliot Lear <lear@cisco.com> wrote:

> Hi,
>
> >
> > [Joe] Yes I think it is fine to say EAP authentication method.   I have
> been convinced that the spec requires crypto-binding with the basic
> password authentication.   I'll need to add this in.
> >
>
> Keep in mind that there might not even be basic auth.  One case is that
> one just uses the OUTER auth, does some PKCS ops or extensions and then
> wants to conclude.  No inner in this case.  Which erratum is that covered
> by?
>
>
[Joe]  Erratum 5775 discusses how to generate key material when there is
no inner authentication method such as the case you describe.


> Eliot
>
>

--0000000000001916bd05b2aba140
Content-Type: text/html; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable

<div dir=3D"ltr"><div dir=3D"ltr"><br></div><br><div class=3D"gmail_quote">=
<div dir=3D"ltr" class=3D"gmail_attr">On Tue, Oct 27, 2020 at 12:23 AM Elio=
t Lear &lt;<a href=3D"mailto:lear@cisco.com">lear@cisco.com</a>&gt; wrote:<=
br></div><blockquote class=3D"gmail_quote" style=3D"margin:0px 0px 0px 0.8e=
x;border-left:1px solid rgb(204,204,204);padding-left:1ex">Hi,<br>
<br>
&gt; <br>
&gt; [Joe] Yes I think it is fine to say EAP authentication method.=C2=A0 =
=C2=A0I have been convinced that the spec requires crypto-binding with the =
basic password authentication.=C2=A0 =C2=A0I&#39;ll need to add this in. <b=
r>
&gt;=C2=A0 <br>
<br>
Keep in mind that there might not even be basic auth.=C2=A0 One case is tha=
t one just uses the OUTER auth, does some PKCS ops or extensions and then w=
ants to conclude.=C2=A0 No inner in this case.=C2=A0 Which erratum is that =
covered by?<br>
<br></blockquote><div><br></div><div>[Joe]=C2=A0 Erratum 5775 discusses how=
 to generate key material when there is no=C2=A0inner authentication method=
 such as the case you describe.=C2=A0=C2=A0</div><div>=C2=A0</div><blockquo=
te class=3D"gmail_quote" style=3D"margin:0px 0px 0px 0.8ex;border-left:1px =
solid rgb(204,204,204);padding-left:1ex">
Eliot<br>
<br>
</blockquote></div></div>

--0000000000001916bd05b2aba140--


From nobody Tue Oct 27 12:10:25 2020
Return-Path: <Hannes.Tschofenig@arm.com>
X-Original-To: emu@ietfa.amsl.com
Delivered-To: emu@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 93FD23A14F9 for <emu@ietfa.amsl.com>; Tue, 27 Oct 2020 12:10:23 -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, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, HTML_MESSAGE=0.001, RCVD_IN_MSPIKE_H2=-0.001, SPF_PASS=-0.001, UNPARSEABLE_RELAY=0.001] autolearn=unavailable autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (1024-bit key) header.d=armh.onmicrosoft.com header.b=JhQlP4Ae; dkim=pass (1024-bit key) header.d=armh.onmicrosoft.com header.b=JhQlP4Ae
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 MCt6pQHs9Tkw for <emu@ietfa.amsl.com>; Tue, 27 Oct 2020 12:10:21 -0700 (PDT)
Received: from EUR04-VI1-obe.outbound.protection.outlook.com (mail-eopbgr80048.outbound.protection.outlook.com [40.107.8.48]) (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 2CAB33A0E60 for <emu@ietf.org>; Tue, 27 Oct 2020 12:10:20 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=armh.onmicrosoft.com;  s=selector2-armh-onmicrosoft-com; h=From:Date:Subject:Message-ID:Content-Type:MIME-Version:X-MS-Exchange-SenderADCheck; bh=96O9zE/COKrTSv6L1VmVAOAS/qOgh8X8ass2SP5C4qQ=; b=JhQlP4AeP7SmwRip9aJ4LnHk0eaCfPt6TflxbblbqqC0ykY5iMTWyZWCsm0ypqOXe9IHB2fcmdXE2QmsJZIfYl0mEc55cFGJQ+fu6Lbym/yuVG6tqJkQ80VYAzc6GSNMecB8ipUZRLWtJI0pgc+3ZqSbGYjHXJ5p0CAS9tmkrJ8=
Received: from AM5PR0701CA0002.eurprd07.prod.outlook.com (2603:10a6:203:51::12) by AM0PR08MB4066.eurprd08.prod.outlook.com (2603:10a6:208:125::27) with Microsoft SMTP Server (version=TLS1_2, cipher=TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384) id 15.20.3477.20; Tue, 27 Oct 2020 19:10:18 +0000
Received: from VE1EUR03FT030.eop-EUR03.prod.protection.outlook.com (2603:10a6:203:51:cafe::89) by AM5PR0701CA0002.outlook.office365.com (2603:10a6:203:51::12) with Microsoft SMTP Server (version=TLS1_2, cipher=TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384) id 15.20.3499.6 via Frontend Transport; Tue, 27 Oct 2020 19:10:18 +0000
X-MS-Exchange-Authentication-Results: spf=pass (sender IP is 63.35.35.123) smtp.mailfrom=arm.com; ietf.org; dkim=pass (signature was verified) header.d=armh.onmicrosoft.com;ietf.org; dmarc=pass action=none header.from=arm.com;
Received-SPF: Pass (protection.outlook.com: domain of arm.com designates 63.35.35.123 as permitted sender) receiver=protection.outlook.com; client-ip=63.35.35.123; helo=64aa7808-outbound-1.mta.getcheckrecipient.com;
Received: from 64aa7808-outbound-1.mta.getcheckrecipient.com (63.35.35.123) by VE1EUR03FT030.mail.protection.outlook.com (10.152.18.66) with Microsoft SMTP Server (version=TLS1_2, cipher=TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384) id 15.20.3499.18 via Frontend Transport; Tue, 27 Oct 2020 19:10:18 +0000
Received: ("Tessian outbound e6c55a0b9ba9:v64"); Tue, 27 Oct 2020 19:10:17 +0000
X-CR-MTA-TID: 64aa7808
Received: from f5e3c6848934.1 by 64aa7808-outbound-1.mta.getcheckrecipient.com id DBEE4B5A-22E4-41F8-8882-7C5F554C91FF.1;  Tue, 27 Oct 2020 19:10:12 +0000
Received: from EUR01-VE1-obe.outbound.protection.outlook.com by 64aa7808-outbound-1.mta.getcheckrecipient.com with ESMTPS id f5e3c6848934.1 (version=TLSv1.2 cipher=ECDHE-RSA-AES256-GCM-SHA384); Tue, 27 Oct 2020 19:10:12 +0000
ARC-Seal: i=1; a=rsa-sha256; s=arcselector9901; d=microsoft.com; cv=none; b=oFs5WWyZAwNGe/cJ0xVbrMfLwLgKb31+AqtEJ66WPN6YAw2u2ZH1OogGh2Q38rpQCkny8IJ8obNBKrpDTCUI8Y+erWKqcumUCw61uc2XgW9Nolo4jb2IiJsZdObpqYnwgmQ/5Xj0DePoCvs6W2TV80Jywz7wSRaQvZCKWFbobDp9Gjiw3CATv2ghKwgcanjyy+6Z1fYkbX3lybkAvTEskb2L7CrJamgKuPcg+8aYkYKOLolEGTjvd9+KIvcOPy6hrMnMQ2TVCDy1wqR8XfL33atXX4f9btbsKUp4+WTxvJLOobAycRRzOI8wE0YD6kdyg9Gv/EJoRbfHHVkkK0k0JA==
ARC-Message-Signature: i=1; a=rsa-sha256; c=relaxed/relaxed; d=microsoft.com;  s=arcselector9901; h=From:Date:Subject:Message-ID:Content-Type:MIME-Version:X-MS-Exchange-SenderADCheck; bh=96O9zE/COKrTSv6L1VmVAOAS/qOgh8X8ass2SP5C4qQ=; b=mYY52gMOmNqo45a4Cf+9uRsdZWoMDI/VIhFwza1TgGd5Lgblih8FsX3rNIuOvW53O3n4CBNmBeX1Udfn8zgPORN/VvAHzaiBFcabxmE1YlTjvMP8fHHbFUZZR91SyjT3Fpl0jF4BnjMvpXEnt/02XxtENbweVBBzGZ6f/R4z3vebSwlKoB/kwdeVM/q8rC5mLhK+QgUg2vACZYcHmTe0NQ4C2aHyc4+8wP2DY0FYjBnBsWc7i5k9A1a2Z+DfXJQ2SSv1x2WfhBdnUeRIfmymBg674lAYMJPWxxRm4CaKc/i6uq77jXNm9CiwkRLNUpTQ6eNHEJWiFs+lMX0IIl/pnQ==
ARC-Authentication-Results: i=1; mx.microsoft.com 1; spf=pass smtp.mailfrom=arm.com; dmarc=pass action=none header.from=arm.com; dkim=pass header.d=arm.com; arc=none
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=armh.onmicrosoft.com;  s=selector2-armh-onmicrosoft-com; h=From:Date:Subject:Message-ID:Content-Type:MIME-Version:X-MS-Exchange-SenderADCheck; bh=96O9zE/COKrTSv6L1VmVAOAS/qOgh8X8ass2SP5C4qQ=; b=JhQlP4AeP7SmwRip9aJ4LnHk0eaCfPt6TflxbblbqqC0ykY5iMTWyZWCsm0ypqOXe9IHB2fcmdXE2QmsJZIfYl0mEc55cFGJQ+fu6Lbym/yuVG6tqJkQ80VYAzc6GSNMecB8ipUZRLWtJI0pgc+3ZqSbGYjHXJ5p0CAS9tmkrJ8=
Received: from AM0PR08MB3716.eurprd08.prod.outlook.com (2603:10a6:208:106::13) by AM8PR08MB5810.eurprd08.prod.outlook.com (2603:10a6:20b:1d2::20) with Microsoft SMTP Server (version=TLS1_2, cipher=TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384) id 15.20.3477.25; Tue, 27 Oct 2020 19:10:11 +0000
Received: from AM0PR08MB3716.eurprd08.prod.outlook.com ([fe80::900e:c64d:a006:4860]) by AM0PR08MB3716.eurprd08.prod.outlook.com ([fe80::900e:c64d:a006:4860%6]) with mapi id 15.20.3455.037; Tue, 27 Oct 2020 19:10:11 +0000
From: Hannes Tschofenig <Hannes.Tschofenig@arm.com>
To: Joseph Salowey <joe@salowey.net>
CC: Eliot Lear <lear=40cisco.com@dmarc.ietf.org>, "emu@ietf.org" <emu@ietf.org>
Thread-Topic: [Emu] draft-ietf-emu-eap-tls13-11: OCSP Stapling
Thread-Index: AdaniLvyfaHHD0ANRluj1nshuTAidQA/HNCAAAyz4QAAFaqz0ADesioAAACtSIAAAZKAAAAAIhlw
Date: Tue, 27 Oct 2020 19:10:11 +0000
Message-ID: <AM0PR08MB3716B6C9F27DB904E509B50CFA160@AM0PR08MB3716.eurprd08.prod.outlook.com>
References: <AM0PR08MB371647618F993B8C5BA6EB5FFA1C0@AM0PR08MB3716.eurprd08.prod.outlook.com> <AD94F3FF-31A7-4F44-95F7-6A7E70FA8D27@cisco.com> <CAOgPGoD3MQu=Hv6HTfug0XredaRt_T7oD7z_uwnATmHku9DmLg@mail.gmail.com> <AM0PR08MB371649BBA92B7F624008D0B3FA1A0@AM0PR08MB3716.eurprd08.prod.outlook.com> <CAOgPGoDaC893pAwfsEj5DNdKwd+z4_HmsOGZ2y8ruDs12Sx+kg@mail.gmail.com> <AM0PR08MB3716466445022163A7C624AAFA160@AM0PR08MB3716.eurprd08.prod.outlook.com> <CAOgPGoBOJip2v1h7L-jZWKMwgDMmEGVr1M7nSK_CE5fAnFwhOA@mail.gmail.com>
In-Reply-To: <CAOgPGoBOJip2v1h7L-jZWKMwgDMmEGVr1M7nSK_CE5fAnFwhOA@mail.gmail.com>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
x-ts-tracking-id: 023A193A590876459BAC437D97CCE05B.0
x-checkrecipientchecked: true
Authentication-Results-Original: salowey.net; dkim=none (message not signed) header.d=none;salowey.net; dmarc=none action=none header.from=arm.com;
x-originating-ip: [80.92.116.60]
x-ms-publictraffictype: Email
X-MS-Office365-Filtering-HT: Tenant
X-MS-Office365-Filtering-Correlation-Id: 42672ad4-934d-426e-d0d3-08d87aabf173
x-ms-traffictypediagnostic: AM8PR08MB5810:|AM0PR08MB4066:
X-Microsoft-Antispam-PRVS: <AM0PR08MB4066870883F77C801880BBF6FA160@AM0PR08MB4066.eurprd08.prod.outlook.com>
x-checkrecipientrouted: true
nodisclaimer: true
x-ms-oob-tlc-oobclassifiers: OLM:10000;OLM:10000;
X-MS-Exchange-SenderADCheck: 1
X-Microsoft-Antispam-Untrusted: BCL:0;
X-Microsoft-Antispam-Message-Info-Original: 9U+Gal1Lwcfi7tYrStx/T2o/RmuEwDjd5M+mKwSmkEW9sItfydP8UEYGZ+U/FgM3SjpxWk+QSF67B3UYLUHVXufNZFCJJjK7N+XtRCD1+0IhrYtENDQOhGg/qvbAmJj9ICoUNYjjZnpjouo8gvP4hO3Mcja98uVPjESHI8XL4fCoNOeRig9xE4pcfNQetL23Qmxw842+XToOYMRAPe0HnK8uGlwebFXrdbA9kwCkLRgC/63pEYOfVnRUbd6Sse8nbQTjJylYxAqsQjjS1Vb6WXaqUPkL4f8Zm+4QCsl6OeTOmmo6fm4UQIYmFfWD08AtLEdRvOZWB67J9NKMjY9P3A==
X-Forefront-Antispam-Report-Untrusted: CIP:255.255.255.255; CTRY:; LANG:en; SCL:1; SRV:; IPV:NLI; SFV:NSPM; H:AM0PR08MB3716.eurprd08.prod.outlook.com; PTR:; CAT:NONE; SFS:(4636009)(39850400004)(396003)(136003)(366004)(376002)(346002)(55016002)(2906002)(54906003)(316002)(8936002)(71200400001)(4326008)(186003)(83380400001)(9686003)(8676002)(52536014)(86362001)(66476007)(26005)(64756008)(66946007)(66446008)(9326002)(5660300002)(33656002)(66556008)(76116006)(7696005)(6916009)(478600001)(6506007); DIR:OUT; SFP:1101; 
x-ms-exchange-antispam-messagedata: q5zHf5aUuP+n8tlof2ogekUQvb/Ycri+lE5yMCpI9zezZukYcJFQ2CjcI/NBCXGNepb1OuIwKXClwRv/JFwVUGA0RFWjvWK4HJSn7PcO7a41utFd23qNn0V/nA8J3ozb00PcGq3LzlfX0ihOMdobolt9CFxxiDe2oCnvb+YqmRNwi1af53oAr8ynJ52owvG44aKWWb6LQV/gzEqCYB9TLsRr1+DuMz05cJFw7m+NWMYx9Zhum/TDnJknQtwagEUNTWHIZWGw62+oQKneHnbw76zJgzjxB2WSBWtJTGR87yeveXWRDcbikjDQLjxvLnsGmfVCAmNCnHMFc1hJ7DTJrho4+8RlEa23UTQkG8ssVrA9PQpuvOaL64Nq4VdhiD37hhtOtlXHQjxM/5vcBKrafk/Ok/KSBSNnDdIpCyBXhNF+oB6I29bmM7+gG/6jtoa5SqSrLqMPdZsLzQG+42fj4wuvBskjzwp6BniHxlCrAZGz8fFgPNUNCuTXWlAnhRJ9POTiwfngcFDE+sVS//B2EV7bjyySk+udkozB98SznIJb2ldASPF3LoN+PFah5yz9P7poPnTDW3FQILteKodWqwJT8iB/ko+mW/NIJplap63dCN0I30nf/ZS5hbHJj4WfK3dUahxrzzeLwrDcdIGlZQ==
x-ms-exchange-transport-forked: True
Content-Type: multipart/alternative; boundary="_000_AM0PR08MB3716B6C9F27DB904E509B50CFA160AM0PR08MB3716eurp_"
MIME-Version: 1.0
X-MS-Exchange-Transport-CrossTenantHeadersStamped: AM8PR08MB5810
Original-Authentication-Results: salowey.net; dkim=none (message not signed) header.d=none;salowey.net; dmarc=none action=none header.from=arm.com;
X-EOPAttributedMessage: 0
X-MS-Exchange-Transport-CrossTenantHeadersStripped: VE1EUR03FT030.eop-EUR03.prod.protection.outlook.com
X-MS-Office365-Filtering-Correlation-Id-Prvs: 8f78545c-d861-47e1-b49c-08d87aabed5b
X-Microsoft-Antispam: BCL:0;
X-Microsoft-Antispam-Message-Info: XVMe0MSLYLQOrwaqSVIboiCkKWE6YmEO9gKmk3ZTmwnex8LfQN4IQeOliljuUfmbnnpjcmTSXBBsubjfruG8He+nsI6IEjlnTIhQj8tyty9XLv4lO50WlPhKkOxesAsf/QR8/bN1FWCz9ZPwLOZokl7CnDwH06coKqTgGw7mHmRAAiaO0HQPe+HmlyO26MUfqwW3yiMuyjHoaWa08fiUkPa8vDtp1ma0tghBN0npwynjO63gAYOvyoT2HO44T7VYOKG4rKcrHACHGt1XLKaj5NyGAkKqcjjp+IzRTPMIF8TdUxoCYsxXbBj7zDQytW+ZmwJ3TKpEyA+7fOxxqFz9g7VEKdcsG8RudQcxgcmKDfJEoBqTnTAjoOXMN0Mhj4z1Kj0m0T8vUqy8IhOaA9AKpg==
X-Forefront-Antispam-Report: CIP:63.35.35.123; CTRY:IE; LANG:en; SCL:1; SRV:;  IPV:CAL; SFV:NSPM; H:64aa7808-outbound-1.mta.getcheckrecipient.com;  PTR:ec2-63-35-35-123.eu-west-1.compute.amazonaws.com; CAT:NONE; SFS:(4636009)(346002)(136003)(376002)(396003)(39850400004)(46966005)(2906002)(6862004)(54906003)(4326008)(36906005)(316002)(478600001)(55016002)(9686003)(9326002)(8936002)(8676002)(356005)(82310400003)(33964004)(6506007)(33656002)(336012)(83380400001)(186003)(81166007)(7696005)(86362001)(47076004)(82740400003)(26005)(52536014)(5660300002)(70206006)(70586007); DIR:OUT; SFP:1101; 
X-OriginatorOrg: arm.com
X-MS-Exchange-CrossTenant-OriginalArrivalTime: 27 Oct 2020 19:10:18.0441 (UTC)
X-MS-Exchange-CrossTenant-Network-Message-Id: 42672ad4-934d-426e-d0d3-08d87aabf173
X-MS-Exchange-CrossTenant-Id: f34e5979-57d9-4aaa-ad4d-b122a662184d
X-MS-Exchange-CrossTenant-OriginalAttributedTenantConnectingIp: TenantId=f34e5979-57d9-4aaa-ad4d-b122a662184d; Ip=[63.35.35.123];  Helo=[64aa7808-outbound-1.mta.getcheckrecipient.com]
X-MS-Exchange-CrossTenant-AuthSource: VE1EUR03FT030.eop-EUR03.prod.protection.outlook.com
X-MS-Exchange-CrossTenant-AuthAs: Anonymous
X-MS-Exchange-CrossTenant-FromEntityHeader: HybridOnPrem
X-MS-Exchange-Transport-CrossTenantHeadersStamped: AM0PR08MB4066
Archived-At: <https://mailarchive.ietf.org/arch/msg/emu/vwrQQAng1IgZCRIKisQ-YljBYQo>
Subject: Re: [Emu] draft-ietf-emu-eap-tls13-11: OCSP Stapling
X-BeenThere: emu@ietf.org
X-Mailman-Version: 2.1.29
Precedence: list
List-Id: "EAP Methods Update \(EMU\)" <emu.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/emu>, <mailto:emu-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/emu/>
List-Post: <mailto:emu@ietf.org>
List-Help: <mailto:emu-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/emu>, <mailto:emu-request@ietf.org?subject=subscribe>
X-List-Received-Date: Tue, 27 Oct 2020 19:10:24 -0000

--_000_AM0PR08MB3716B6C9F27DB904E509B50CFA160AM0PR08MB3716eurp_
Content-Type: text/plain; charset="utf-8"
Content-Transfer-Encoding: base64

SGkgSm9lLA0KDQpUaGFua3MgZm9yIHRoZSBxdWljayByZXNwb25zZS4NCg0KW0pvZV0gSWYgdGhl
IHNlcnZlciBpcyBvZmZlcmluZyBhbiBleHBpcmVkIG9yIHJldm9rZWQgY2VydGlmaWNhdGUgdGhl
biB0aGF0IG5lZWRzIHRvIGJlIHJlbWVkaWVkIG9uIHRoZSBzZXJ2ZXIuDQoNCldoZXJlIGRvIHlv
dSBiZWxpZXZlIHRoZSB2YWx1ZSBvZiBPQ1NQIGNvbWVzIGludG8gdGhlIHBpY3R1cmUgZm9yIHRo
aXMgRUFQLVRMUyB1c2UgY2FzZSBhbmQgd2hhdCBhY3Rpb25zIG5lZWQgdG8gYmUgdGFrZW4gd2hl
biBhIG5vdGlmaWNhdGlvbiBvZiBhIHJldm9rZWQvZXhwaXJlZCBjZXJ0aWZpY2F0ZSBzaG93cyB1
cD8NCg0KW0pvZV0gdGhlIGRvY3VtZW50IHVuZGVyIGNvbnNpZGVyYXRpb24gaXMgRUFQLVRMUyAx
LjMuICAgSW4gbXkgb3BpbmlvbiBhbnkgZG9jdW1lbnQgdGhhdCBkZWFscyB3aXRoIGNlcnRpZmlj
YXRlcyBvdWdodCB0byBoYXZlIHNvbWUgZGlzY3Vzc2lvbiBvbiByZXZvY2F0aW9uLiAgSW4gcGFy
dGljdWxhciwgRUFQIGlzIGRlcGxveWVkIGludG8gYW4gZW52aXJvbm1lbnQgd2hlcmUgc29tZSBy
ZXZvY2F0aW9uIG1lY2hhbmlzbXMgbWF5IG5vdCB3b3JrIGFzIGV4cGVjdGVkIGJlY2F1c2UgdGhl
cmUgaXMgbm8gbmV0d29yayBhY2Nlc3MgYXZhaWxhYmxlIHRvIGRvIG91dCBvZiBiYW5kIGNoZWNr
cy4NCg0KZHJhZnQtaWV0Zi1lbXUtZWFwLXRsczEzIGFsc28gbWFrZXMgY2hhbmdlcyB0byBUTFMg
MS4yIGluIEVBUC1UTFMuIEl0IHVwZGF0ZXMgdGhlIGNvbnRlbnQgb2YgdGhlIG9yaWdpbmFsIFJG
Qy4gVGhpcyB3YXMgc3VycHJpc2luZyB0byBtZSBhcyB3ZWxsLg0KSW4gdGhhdCBzcGlyaXQgaXQg
d291bGRu4oCZdCBiZSB1bm5hdHVyYWwgdG8gYWxzbyByZXF1aXJlIE9DU1AgdGhlcmUgYW5kIHRv
IGFwcGx5IHRoYXQgdG8gYWxsIEVBUCBtZXRob2RzIHRoYXQgdXNlIFRMUy4NCg0KTm90ZSB0aGF0
IEkgYW0gbm90IHJlY29tbWVuZGluZyBpdCBidXQgaXQgc2hvd3MgdGhlIGluY29uc2lzdGVuY3kg
aW4gdGhlIGFwcHJvYWNoIGJlaW5nIHRha2VuIHRvZGF5Lg0KDQpDaWFvDQpIYW5uZXMNCg0KDQoN
CklNUE9SVEFOVCBOT1RJQ0U6IFRoZSBjb250ZW50cyBvZiB0aGlzIGVtYWlsIGFuZCBhbnkgYXR0
YWNobWVudHMgYXJlIGNvbmZpZGVudGlhbCBhbmQgbWF5IGFsc28gYmUgcHJpdmlsZWdlZC4gSWYg
eW91IGFyZSBub3QgdGhlIGludGVuZGVkIHJlY2lwaWVudCwgcGxlYXNlIG5vdGlmeSB0aGUgc2Vu
ZGVyIGltbWVkaWF0ZWx5IGFuZCBkbyBub3QgZGlzY2xvc2UgdGhlIGNvbnRlbnRzIHRvIGFueSBv
dGhlciBwZXJzb24sIHVzZSBpdCBmb3IgYW55IHB1cnBvc2UsIG9yIHN0b3JlIG9yIGNvcHkgdGhl
IGluZm9ybWF0aW9uIGluIGFueSBtZWRpdW0uIFRoYW5rIHlvdS4NCg==

--_000_AM0PR08MB3716B6C9F27DB904E509B50CFA160AM0PR08MB3716eurp_
Content-Type: text/html; charset="utf-8"
Content-Transfer-Encoding: base64

PGh0bWwgeG1sbnM6dj0idXJuOnNjaGVtYXMtbWljcm9zb2Z0LWNvbTp2bWwiIHhtbG5zOm89InVy
bjpzY2hlbWFzLW1pY3Jvc29mdC1jb206b2ZmaWNlOm9mZmljZSIgeG1sbnM6dz0idXJuOnNjaGVt
YXMtbWljcm9zb2Z0LWNvbTpvZmZpY2U6d29yZCIgeG1sbnM6bT0iaHR0cDovL3NjaGVtYXMubWlj
cm9zb2Z0LmNvbS9vZmZpY2UvMjAwNC8xMi9vbW1sIiB4bWxucz0iaHR0cDovL3d3dy53My5vcmcv
VFIvUkVDLWh0bWw0MCI+DQo8aGVhZD4NCjxtZXRhIGh0dHAtZXF1aXY9IkNvbnRlbnQtVHlwZSIg
Y29udGVudD0idGV4dC9odG1sOyBjaGFyc2V0PXV0Zi04Ij4NCjxtZXRhIG5hbWU9IkdlbmVyYXRv
ciIgY29udGVudD0iTWljcm9zb2Z0IFdvcmQgMTUgKGZpbHRlcmVkIG1lZGl1bSkiPg0KPHN0eWxl
PjwhLS0NCi8qIEZvbnQgRGVmaW5pdGlvbnMgKi8NCkBmb250LWZhY2UNCgl7Zm9udC1mYW1pbHk6
IkNhbWJyaWEgTWF0aCI7DQoJcGFub3NlLTE6MiA0IDUgMyA1IDQgNiAzIDIgNDt9DQpAZm9udC1m
YWNlDQoJe2ZvbnQtZmFtaWx5OkRlbmdYaWFuOw0KCXBhbm9zZS0xOjIgMSA2IDAgMyAxIDEgMSAx
IDE7fQ0KQGZvbnQtZmFjZQ0KCXtmb250LWZhbWlseTpDYWxpYnJpOw0KCXBhbm9zZS0xOjIgMTUg
NSAyIDIgMiA0IDMgMiA0O30NCkBmb250LWZhY2UNCgl7Zm9udC1mYW1pbHk6IlxARGVuZ1hpYW4i
Ow0KCXBhbm9zZS0xOjIgMSA2IDAgMyAxIDEgMSAxIDE7fQ0KLyogU3R5bGUgRGVmaW5pdGlvbnMg
Ki8NCnAuTXNvTm9ybWFsLCBsaS5Nc29Ob3JtYWwsIGRpdi5Nc29Ob3JtYWwNCgl7bWFyZ2luOjBp
bjsNCglmb250LXNpemU6MTEuMHB0Ow0KCWZvbnQtZmFtaWx5OiJDYWxpYnJpIixzYW5zLXNlcmlm
O30NCnNwYW4uRW1haWxTdHlsZTIwDQoJe21zby1zdHlsZS10eXBlOnBlcnNvbmFsLWNvbXBvc2U7
DQoJZm9udC1mYW1pbHk6IkNhbGlicmkiLHNhbnMtc2VyaWY7DQoJY29sb3I6d2luZG93dGV4dDt9
DQouTXNvQ2hwRGVmYXVsdA0KCXttc28tc3R5bGUtdHlwZTpleHBvcnQtb25seTsNCglmb250LWZh
bWlseToiQ2FsaWJyaSIsc2Fucy1zZXJpZjt9DQpAcGFnZSBXb3JkU2VjdGlvbjENCgl7c2l6ZTo4
LjVpbiAxMS4waW47DQoJbWFyZ2luOjEuMGluIDEuMGluIDEuMGluIDEuMGluO30NCmRpdi5Xb3Jk
U2VjdGlvbjENCgl7cGFnZTpXb3JkU2VjdGlvbjE7fQ0KLyogTGlzdCBEZWZpbml0aW9ucyAqLw0K
QGxpc3QgbDANCgl7bXNvLWxpc3QtaWQ6MTU1MzYxODQzMzsNCgltc28tbGlzdC10ZW1wbGF0ZS1p
ZHM6MTE1NjQ5OTA2NDt9DQpvbA0KCXttYXJnaW4tYm90dG9tOjBpbjt9DQp1bA0KCXttYXJnaW4t
Ym90dG9tOjBpbjt9DQotLT48L3N0eWxlPjwhLS1baWYgZ3RlIG1zbyA5XT48eG1sPg0KPG86c2hh
cGVkZWZhdWx0cyB2OmV4dD0iZWRpdCIgc3BpZG1heD0iMTAyNiIgLz4NCjwveG1sPjwhW2VuZGlm
XS0tPjwhLS1baWYgZ3RlIG1zbyA5XT48eG1sPg0KPG86c2hhcGVsYXlvdXQgdjpleHQ9ImVkaXQi
Pg0KPG86aWRtYXAgdjpleHQ9ImVkaXQiIGRhdGE9IjEiIC8+DQo8L286c2hhcGVsYXlvdXQ+PC94
bWw+PCFbZW5kaWZdLS0+DQo8L2hlYWQ+DQo8Ym9keSBsYW5nPSJFTi1VUyIgbGluaz0iYmx1ZSIg
dmxpbms9InB1cnBsZSIgc3R5bGU9IndvcmQtd3JhcDpicmVhay13b3JkIj4NCjxkaXYgY2xhc3M9
IldvcmRTZWN0aW9uMSI+DQo8ZGl2Pg0KPGRpdj4NCjxkaXY+DQo8cCBjbGFzcz0iTXNvTm9ybWFs
Ij5IaSBKb2UsIDxvOnA+PC9vOnA+PC9wPg0KPHAgY2xhc3M9Ik1zb05vcm1hbCI+PG86cD4mbmJz
cDs8L286cD48L3A+DQo8cCBjbGFzcz0iTXNvTm9ybWFsIj5UaGFua3MgZm9yIHRoZSBxdWljayBy
ZXNwb25zZS4gPG86cD48L286cD48L3A+DQo8cCBjbGFzcz0iTXNvTm9ybWFsIj48bzpwPiZuYnNw
OzwvbzpwPjwvcD4NCjxwIGNsYXNzPSJNc29Ob3JtYWwiPltKb2VdIElmIHRoZSBzZXJ2ZXIgaXMg
b2ZmZXJpbmcgYW4gZXhwaXJlZCBvciByZXZva2VkIGNlcnRpZmljYXRlIHRoZW4gdGhhdCBuZWVk
cyB0byBiZSByZW1lZGllZCBvbiB0aGUgc2VydmVyLiZuYnNwOyZuYnNwOzxvOnA+PC9vOnA+PC9w
Pg0KPC9kaXY+DQo8ZGl2Pg0KPHAgY2xhc3M9Ik1zb05vcm1hbCI+PG86cD4mbmJzcDs8L286cD48
L3A+DQo8cCBjbGFzcz0iTXNvTm9ybWFsIj5XaGVyZSBkbyB5b3UgYmVsaWV2ZSB0aGUgdmFsdWUg
b2YgT0NTUCBjb21lcyBpbnRvIHRoZSBwaWN0dXJlIGZvciB0aGlzIEVBUC1UTFMgdXNlIGNhc2Ug
YW5kIHdoYXQgYWN0aW9ucyBuZWVkIHRvIGJlIHRha2VuIHdoZW4gYSBub3RpZmljYXRpb24gb2Yg
YSByZXZva2VkL2V4cGlyZWQgY2VydGlmaWNhdGUgc2hvd3MgdXA/DQo8bzpwPjwvbzpwPjwvcD4N
CjwvZGl2Pg0KPGRpdj4NCjxwIGNsYXNzPSJNc29Ob3JtYWwiPjxvOnA+Jm5ic3A7PC9vOnA+PC9w
Pg0KPC9kaXY+DQo8ZGl2Pg0KPHAgY2xhc3M9Ik1zb05vcm1hbCI+W0pvZV0gdGhlIGRvY3VtZW50
IHVuZGVyIGNvbnNpZGVyYXRpb24gaXMgRUFQLVRMUyAxLjMuJm5ic3A7ICZuYnNwO0luIG15IG9w
aW5pb24gYW55IGRvY3VtZW50IHRoYXQgZGVhbHMgd2l0aCBjZXJ0aWZpY2F0ZXMgb3VnaHQgdG8g
aGF2ZSBzb21lIGRpc2N1c3Npb24gb24gcmV2b2NhdGlvbi4mbmJzcDsgSW4gcGFydGljdWxhciwg
RUFQIGlzIGRlcGxveWVkIGludG8gYW4gZW52aXJvbm1lbnQgd2hlcmUgc29tZSByZXZvY2F0aW9u
IG1lY2hhbmlzbXMNCiBtYXkgbm90IHdvcmsgYXMgZXhwZWN0ZWQgYmVjYXVzZSZuYnNwO3RoZXJl
IGlzIG5vIG5ldHdvcmsgYWNjZXNzIGF2YWlsYWJsZSB0byBkbyBvdXQgb2YgYmFuZCBjaGVja3Mu
Jm5ic3A7Jm5ic3A7PG86cD48L286cD48L3A+DQo8L2Rpdj4NCjxkaXY+DQo8cCBjbGFzcz0iTXNv
Tm9ybWFsIj48bzpwPiZuYnNwOzwvbzpwPjwvcD4NCjxwIGNsYXNzPSJNc29Ob3JtYWwiPmRyYWZ0
LWlldGYtZW11LWVhcC10bHMxMyBhbHNvIG1ha2VzIGNoYW5nZXMgdG8gVExTIDEuMiBpbiBFQVAt
VExTLiBJdCB1cGRhdGVzIHRoZSBjb250ZW50IG9mIHRoZSBvcmlnaW5hbCBSRkMuIFRoaXMgd2Fz
IHN1cnByaXNpbmcgdG8gbWUgYXMgd2VsbC4NCjxvOnA+PC9vOnA+PC9wPg0KPHAgY2xhc3M9Ik1z
b05vcm1hbCI+SW4gdGhhdCBzcGlyaXQgaXQgd291bGRu4oCZdCBiZSB1bm5hdHVyYWwgdG8gYWxz
byByZXF1aXJlIE9DU1AgdGhlcmUgYW5kIHRvIGFwcGx5IHRoYXQgdG8gYWxsIEVBUCBtZXRob2Rz
IHRoYXQgdXNlIFRMUy4NCjxvOnA+PC9vOnA+PC9wPg0KPHAgY2xhc3M9Ik1zb05vcm1hbCI+PG86
cD4mbmJzcDs8L286cD48L3A+DQo8cCBjbGFzcz0iTXNvTm9ybWFsIj5Ob3RlIHRoYXQgSSBhbSBu
b3QgcmVjb21tZW5kaW5nIGl0IGJ1dCBpdCBzaG93cyB0aGUgaW5jb25zaXN0ZW5jeSBpbiB0aGUg
YXBwcm9hY2ggYmVpbmcgdGFrZW4gdG9kYXkuDQo8bzpwPjwvbzpwPjwvcD4NCjxwIGNsYXNzPSJN
c29Ob3JtYWwiPjxvOnA+Jm5ic3A7PC9vOnA+PC9wPg0KPHAgY2xhc3M9Ik1zb05vcm1hbCI+Q2lh
bzxicj4NCkhhbm5lczxvOnA+PC9vOnA+PC9wPg0KPHAgY2xhc3M9Ik1zb05vcm1hbCI+PG86cD4m
bmJzcDs8L286cD48L3A+DQo8cCBjbGFzcz0iTXNvTm9ybWFsIj48bzpwPiZuYnNwOzwvbzpwPjwv
cD4NCjxwIGNsYXNzPSJNc29Ob3JtYWwiPjxvOnA+Jm5ic3A7PC9vOnA+PC9wPg0KPC9kaXY+DQo8
L2Rpdj4NCjwvZGl2Pg0KPC9kaXY+DQpJTVBPUlRBTlQgTk9USUNFOiBUaGUgY29udGVudHMgb2Yg
dGhpcyBlbWFpbCBhbmQgYW55IGF0dGFjaG1lbnRzIGFyZSBjb25maWRlbnRpYWwgYW5kIG1heSBh
bHNvIGJlIHByaXZpbGVnZWQuIElmIHlvdSBhcmUgbm90IHRoZSBpbnRlbmRlZCByZWNpcGllbnQs
IHBsZWFzZSBub3RpZnkgdGhlIHNlbmRlciBpbW1lZGlhdGVseSBhbmQgZG8gbm90IGRpc2Nsb3Nl
IHRoZSBjb250ZW50cyB0byBhbnkgb3RoZXIgcGVyc29uLCB1c2UgaXQgZm9yIGFueSBwdXJwb3Nl
LA0KIG9yIHN0b3JlIG9yIGNvcHkgdGhlIGluZm9ybWF0aW9uIGluIGFueSBtZWRpdW0uIFRoYW5r
IHlvdS4NCjwvYm9keT4NCjwvaHRtbD4NCg==

--_000_AM0PR08MB3716B6C9F27DB904E509B50CFA160AM0PR08MB3716eurp_--


From nobody Tue Oct 27 17:11:11 2020
Return-Path: <noreply@ietf.org>
X-Original-To: emu@ietf.org
Delivered-To: emu@ietfa.amsl.com
Received: from ietfa.amsl.com (localhost [IPv6:::1]) by ietfa.amsl.com (Postfix) with ESMTP id 852B93A098D; Tue, 27 Oct 2020 17:11:09 -0700 (PDT)
MIME-Version: 1.0
Content-Type: text/plain; charset="utf-8"
Content-Transfer-Encoding: 7bit
From: Kyle Rose via Datatracker <noreply@ietf.org>
To: <secdir@ietf.org>
Cc: emu@ietf.org, last-call@ietf.org, draft-ietf-emu-eap-tls13.all@ietf.org
X-Test-IDTracker: no
X-IETF-IDTracker: 7.21.0
Auto-Submitted: auto-generated
Precedence: bulk
Message-ID: <160384386950.10450.5930216784938121668@ietfa.amsl.com>
Reply-To: Kyle Rose <krose@krose.org>
Date: Tue, 27 Oct 2020 17:11:09 -0700
Archived-At: <https://mailarchive.ietf.org/arch/msg/emu/ZN8ZWKvABShFykox_jHNjKxAeTk>
Subject: [Emu] Secdir last call review of draft-ietf-emu-eap-tls13-11
X-BeenThere: emu@ietf.org
X-Mailman-Version: 2.1.29
List-Id: "EAP Methods Update \(EMU\)" <emu.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/emu>, <mailto:emu-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/emu/>
List-Post: <mailto:emu@ietf.org>
List-Help: <mailto:emu-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/emu>, <mailto:emu-request@ietf.org?subject=subscribe>
X-List-Received-Date: Wed, 28 Oct 2020 00:11:10 -0000

Reviewer: Kyle Rose
Review result: Has Nits

I have reviewed this document as part of the security directorate's ongoing
effort to review all IETF documents being processed by the IESG.  These
comments were written primarily for the benefit of the security area directors.
 Document editors and WG chairs should treat these comments just like any other
last call comments.

This document is ready with nits.

The purpose of this document is to update the TLS method of EAP to accommodate
the changes to TLS in 1.3: in this, it appears to be complete and to have been
thoroughly vetted. I have two nits and a high-level suggestion:

* The introduction at one point says "Privacy is mandatory". Later in the
document it becomes clear what is meant by this, but at this point in the
document "privacy" is somewhat of a Rorschach test. It clearly doesn't mean
that repeated EAP requests from the same IP will be unlinkable, for instance.
What appears to be meant here is that encryption of the client certificate
prevents linkability via passive surveillance. Say that instead.

* Expand NAI into "Network Access Identifiers", with the appropriate
informative reference, at its first use, not halfway through the document.

* My high-level suggestion for this document is to be forward-looking in how
you specify the relationship of EAP to TLS. Expect there to be a TLS 1.4 (or
2.0) and beyond, and specify this protocol using standardized TLS interfaces
only, with the rest of the protocol (including the specific handshake messages)
treated as a black box. This may or may not have been possible in the pre-TLS
1.3 era, but it is certainly possible to do so now. At best, no normative
changes will be required; at worst, the size of the update to the EAP RFC will
be minimized.



From nobody Wed Oct 28 03:16:07 2020
Return-Path: <internet-drafts@ietf.org>
X-Original-To: emu@ietf.org
Delivered-To: emu@ietfa.amsl.com
Received: from ietfa.amsl.com (localhost [IPv6:::1]) by ietfa.amsl.com (Postfix) with ESMTP id 6ED503A0657; Wed, 28 Oct 2020 03:16:01 -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>
Cc: emu@ietf.org
X-Test-IDTracker: no
X-IETF-IDTracker: 7.21.0
Auto-Submitted: auto-generated
Precedence: bulk
Reply-To: emu@ietf.org
Message-ID: <160388016140.19325.12093393779688032209@ietfa.amsl.com>
Date: Wed, 28 Oct 2020 03:16:01 -0700
Archived-At: <https://mailarchive.ietf.org/arch/msg/emu/9H-c8Bmrcnvx2g7WNjDPUSvaTW0>
Subject: [Emu] I-D Action: draft-ietf-emu-eaptlscert-06.txt
X-BeenThere: emu@ietf.org
X-Mailman-Version: 2.1.29
List-Id: "EAP Methods Update \(EMU\)" <emu.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/emu>, <mailto:emu-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/emu/>
List-Post: <mailto:emu@ietf.org>
List-Help: <mailto:emu-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/emu>, <mailto:emu-request@ietf.org?subject=subscribe>
X-List-Received-Date: Wed, 28 Oct 2020 10:16:02 -0000

A New Internet-Draft is available from the on-line Internet-Drafts directories.
This draft is a work item of the EAP Method Update WG of the IETF.

        Title           : Handling Large Certificates and Long Certificate Chains in TLS-based EAP Methods
        Authors         : Mohit Sethi
                          John Mattsson
                          Sean Turner
	Filename        : draft-ietf-emu-eaptlscert-06.txt
	Pages           : 14
	Date            : 2020-10-28

Abstract:
   The Extensible Authentication Protocol (EAP), defined in RFC3748,
   provides a standard mechanism for support of multiple authentication
   methods.  EAP-Transport Layer Security (EAP-TLS) and other TLS-based
   EAP methods are widely deployed and used for network access
   authentication.  Large certificates and long certificate chains
   combined with authenticators that drop an EAP session after only 40 -
   50 round-trips is a major deployment problem.  This document looks at
   the this problem in detail and describes the potential solutions
   available.


The IETF datatracker status page for this draft is:
https://datatracker.ietf.org/doc/draft-ietf-emu-eaptlscert/

There are also htmlized versions available at:
https://tools.ietf.org/html/draft-ietf-emu-eaptlscert-06
https://datatracker.ietf.org/doc/html/draft-ietf-emu-eaptlscert-06

A diff from the previous version is available at:
https://www.ietf.org/rfcdiff?url2=draft-ietf-emu-eaptlscert-06


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 Wed Oct 28 03:46:05 2020
Return-Path: <mohit.m.sethi@ericsson.com>
X-Original-To: emu@ietfa.amsl.com
Delivered-To: emu@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 811BC3A08E3; Wed, 28 Oct 2020 03:46:03 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.349
X-Spam-Level: 
X-Spam-Status: No, score=-2.349 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIMWL_WL_HIGH=-0.001, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, DKIM_VALID_EF=-0.1, NICE_REPLY_A=-0.247, RCVD_IN_MSPIKE_H2=-0.001, SPF_PASS=-0.001, URIBL_BLOCKED=0.001] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (1024-bit key) header.d=ericsson.com
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 OetZ-i_IDbQe; Wed, 28 Oct 2020 03:46:01 -0700 (PDT)
Received: from EUR04-HE1-obe.outbound.protection.outlook.com (mail-eopbgr70055.outbound.protection.outlook.com [40.107.7.55]) (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 BABDB3A0820; Wed, 28 Oct 2020 03:45:57 -0700 (PDT)
ARC-Seal: i=1; a=rsa-sha256; s=arcselector9901; d=microsoft.com; cv=none; b=TaCXqwYQ9YR7d1sfYzPM5CSFdWd5XtfAA6WrP7z6psl+R62tOT1KUp90geHPLSNPyhoclmg2fLcorkimmsHZb5RY/b4aeqiYfG/01qvAwOw/grmtBZUxUWnHxJEEcfD6MLs69bUlOpzziKavTc/fuw0adrdO9wWRezYEXgp8glrytRCjm+5Ztws/5oAuJhBY+X9PMNY39VhmrFpnWit6NPheLRd8T2xibyGAX3dbO+8HkH/n+eEBL78245Nqmnu6kjkMga+Ix23M+7oDzNGkmq/AmgBEaAZAqIhwTZvLmFUUENcBpgtIpgwk0/jL3fzJHYQNzCJEaMsWFGgws3I94w==
ARC-Message-Signature: i=1; a=rsa-sha256; c=relaxed/relaxed; d=microsoft.com;  s=arcselector9901; h=From:Date:Subject:Message-ID:Content-Type:MIME-Version:X-MS-Exchange-SenderADCheck; bh=jYS1R5dp1zD0821hviauYKfJiqoxMJO752H/HiWDWII=; b=WJ3fdPbhbjnXIGHGLyls7j4bn77kLY5FnzB3M3uaWHo73NW2TnqpCGDuvwI4qR3H2+XSDS7XKKBhICb2KNJ6Gryfl5Ae2e8OdtFoRegsdnu+sPymZQ83AmMDApPW654Do6/l2OYx4pXcrLq9N3UCNiglevrFvYw5W2sKpfhurRo9/Rgdez1cbya2iEO7zodnI9cVAfVZfqo4slQfPlf1gPwI9HJF7LJJ0/QKUHGabmRMPAUyknwhUdcpyM1WbV/DKFjjCUE6M0xbKmjotHEQY4zFqJMU5IXZ+oxizCx18hxWDmB2wIBw2EzTjajAwaRUw94mRv3lERbGf2QQwn70mA==
ARC-Authentication-Results: i=1; mx.microsoft.com 1; spf=pass smtp.mailfrom=ericsson.com; dmarc=pass action=none header.from=ericsson.com; dkim=pass header.d=ericsson.com; arc=none
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=ericsson.com; s=selector1; h=From:Date:Subject:Message-ID:Content-Type:MIME-Version:X-MS-Exchange-SenderADCheck; bh=jYS1R5dp1zD0821hviauYKfJiqoxMJO752H/HiWDWII=; b=cxFDXpxBeZAKv2JqvVFj2YoSWH91a/6fPPs87v5w8WEPk1NwiMSRrpzpV8XnLNQmbZ3y9CcCCo2812S8OxUrkOi62VqMjR897lvfVFDZshCwhdCqcEWADkRvdny/7XNK7Xig7vkYynty/u+oiqq49yrMEFzEr6vuQOWtPYl2fJk=
Received: from HE1PR07MB3209.eurprd07.prod.outlook.com (2603:10a6:7:32::14) by HE1PR0701MB2730.eurprd07.prod.outlook.com (2603:10a6:3:98::12) with Microsoft SMTP Server (version=TLS1_2, cipher=TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384) id 15.20.3499.8; Wed, 28 Oct 2020 10:45:54 +0000
Received: from HE1PR07MB3209.eurprd07.prod.outlook.com ([fe80::1550:2d88:a5be:95ca]) by HE1PR07MB3209.eurprd07.prod.outlook.com ([fe80::1550:2d88:a5be:95ca%6]) with mapi id 15.20.3499.018; Wed, 28 Oct 2020 10:45:54 +0000
From: Mohit Sethi M <mohit.m.sethi@ericsson.com>
To: Elwyn Davies <elwynd@dial.pipex.com>, "gen-art@ietf.org" <gen-art@ietf.org>
CC: "last-call@ietf.org" <last-call@ietf.org>, "draft-ietf-emu-eaptlscert.all@ietf.org" <draft-ietf-emu-eaptlscert.all@ietf.org>, "emu@ietf.org" <emu@ietf.org>
Thread-Topic: [Emu] Genart last call review of draft-ietf-emu-eaptlscert-05
Thread-Index: AQHWqfKlqhflg4aBaUOBXqV8XBPAeqms2x6A
Date: Wed, 28 Oct 2020 10:45:54 +0000
Message-ID: <d3797730-ca22-162f-a887-9c593838fde1@ericsson.com>
References: <160353625817.30765.14852413837090655602@ietfa.amsl.com>
In-Reply-To: <160353625817.30765.14852413837090655602@ietfa.amsl.com>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
user-agent: Mozilla/5.0 (X11; Linux x86_64; rv:68.0) Gecko/20100101 Thunderbird/68.10.0
authentication-results: dial.pipex.com; dkim=none (message not signed) header.d=none;dial.pipex.com; dmarc=none action=none header.from=ericsson.com;
x-originating-ip: [37.136.189.206]
x-ms-publictraffictype: Email
x-ms-office365-filtering-correlation-id: 701bd155-a8e9-4f07-0bb1-08d87b2ea583
x-ms-traffictypediagnostic: HE1PR0701MB2730:
x-microsoft-antispam-prvs: <HE1PR0701MB2730E959A0006452D1F4061BD0170@HE1PR0701MB2730.eurprd07.prod.outlook.com>
x-ms-oob-tlc-oobclassifiers: OLM:9508;
x-ms-exchange-senderadcheck: 1
x-microsoft-antispam: BCL:0;
x-microsoft-antispam-message-info: sYmOBH3RsuKEIJtHAezjv5Wh7s4rEJq5g74MFp3MpBujr5tlgufX3WClR4rcrxK5C6LYLBpTnk+TZEKIvDUa4cpOH3hJZ9LR5sbRM8WGyaGUPyhrA33PjGLkRe5vMXOQcIeKa9cyfO0eknFz2io/zJC9rcYkb/O6JyIMfXB+FQZ0pryu+5HwTYNT4BTLoZ9I2q9Mceh6ea0WV6v0zpS2H7sdIVagjNxVC1CPcBIsRa3K6ZEp8B4G/jM3mK+C1z3z94q6U82XcjoE6NVOxfhgSRFBq3VmR9gLQ32fR/ZpgH6O/8YDbF/7B2IwMoHn6n4u0ApFt2dLEUjSVuMJV1rgRCwr750HTngoY4V9oq3h2TJt0Qa5/84qKD1C7Gz2OjCA9IjmvkFgD78u8dhF5hJR1qqcH3a+nKy2y7CaDi2uglxOHsUsCjaE0iP2ldA3eyprP45aHwQJqqvVhqqCfvCZvQ==
x-forefront-antispam-report: CIP:255.255.255.255; CTRY:; LANG:en; SCL:1; SRV:;  IPV:NLI; SFV:NSPM; H:HE1PR07MB3209.eurprd07.prod.outlook.com; PTR:; CAT:NONE;  SFS:(4636009)(136003)(396003)(376002)(366004)(39860400002)(346002)(186003)(110136005)(66556008)(6506007)(54906003)(8936002)(2906002)(66476007)(53546011)(4326008)(66446008)(26005)(2616005)(316002)(5660300002)(76116006)(6512007)(6486002)(71200400001)(36756003)(86362001)(64756008)(66946007)(31696002)(8676002)(966005)(478600001)(31686004)(4001150100001)(83380400001)(43740500002); DIR:OUT; SFP:1101; 
x-ms-exchange-antispam-messagedata: MwKc4JbrZ3rUD4qgYKL7OeV/pCESb3BRBiOOWkES8e88s/mZY8O0qF8ah4zl96YEDFWol3GvVGOl9RclK96X555CGQo26mKbY9VVjEgFzXg+Wn0Xl5/TSa0a9sxO4gsk4MGFmMWSNHIGEsZ0iLgDxXLjtWDvE6ZDH+7sqCGBem9afOlS/50Yq0tjcuv0D8xHXKtLLqCrBNRuQLdWkaImtvi7WJX73jO/e4v1OF92WBm0tme5y6eQtFb0TENaFFTGg/6NduRCbRfJ6oR1Kog2UCCG6EPCT9Md4FWjI7k85jfx1TJZn0LfXiYT/1M7lG4zY90HGYs49ydsgKQC56uQRN8pFN1aQ06iCEcs0B7WjczlDQrOlPd2EJBkHfspByxbNL0r9BsQZ/TzBAPwj2k9S1GZJnQ6UIstQE2Zki9wzkyU5OSvqoLeptrUIinbj8eT/oGtiWpMkogOQ3slUoNYpETGY8R6VYs9nZvAc03ndsJPzakU2fpbZ55dI7pfgobNmH0J4JRG/5ylLVjgExBidVW7HUDZMNCZ6ZWz6iGQBTdkngSdTZH6rxH/pepbCX3ya3rXfmkZ/zdhJBciqkNNxJ9R/oz3gLJ/d2H2A3e1GyFCYXhNGqcR3uKkkNc7anS4qg7jzFQVSqY39Ht1nk3TMw==
x-ms-exchange-transport-forked: True
Content-Type: text/plain; charset="utf-8"
Content-ID: <641D095DAE4A654082DCECF0EE2BF044@eurprd07.prod.outlook.com>
Content-Transfer-Encoding: base64
MIME-Version: 1.0
X-OriginatorOrg: ericsson.com
X-MS-Exchange-CrossTenant-AuthAs: Internal
X-MS-Exchange-CrossTenant-AuthSource: HE1PR07MB3209.eurprd07.prod.outlook.com
X-MS-Exchange-CrossTenant-Network-Message-Id: 701bd155-a8e9-4f07-0bb1-08d87b2ea583
X-MS-Exchange-CrossTenant-originalarrivaltime: 28 Oct 2020 10:45:54.6727 (UTC)
X-MS-Exchange-CrossTenant-fromentityheader: Hosted
X-MS-Exchange-CrossTenant-id: 92e84ceb-fbfd-47ab-be52-080c6b87953f
X-MS-Exchange-CrossTenant-mailboxtype: HOSTED
X-MS-Exchange-CrossTenant-userprincipalname: sWjn66bU2FK7We8/vLzMpAkgA4E72FM2k+phJy0IRQku8IeazmVXstJO16aSXWlkItf6qCAPgF7NwGeQjiMlx9zbIZyaFEs3AACeIKC+UF8=
X-MS-Exchange-Transport-CrossTenantHeadersStamped: HE1PR0701MB2730
Archived-At: <https://mailarchive.ietf.org/arch/msg/emu/Q_TZTTj_tlDk-GOYgq8jtS2dZCU>
Subject: Re: [Emu] Genart last call review of draft-ietf-emu-eaptlscert-05
X-BeenThere: emu@ietf.org
X-Mailman-Version: 2.1.29
Precedence: list
List-Id: "EAP Methods Update \(EMU\)" <emu.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/emu>, <mailto:emu-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/emu/>
List-Post: <mailto:emu@ietf.org>
List-Help: <mailto:emu-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/emu>, <mailto:emu-request@ietf.org?subject=subscribe>
X-List-Received-Date: Wed, 28 Oct 2020 10:46:04 -0000

SGkgRWx3eW4sDQoNClRoYW5rIHlvdSBmb3IgdGhlIGNhcmVmdWwgcmV2aWV3LiBXZSBoYXZlIHVw
ZGF0ZWQgdGhlIGRyYWZ0IGJhc2VkIG9uIA0KeW91ciBmZWVkYmFjay4gSGVyZSBpcyB0aGUgZGlm
ZiBmb3IgeW91IGNvbnZlbmllbmNlOiANCmh0dHBzOi8vd3d3LmlldGYub3JnL3JmY2RpZmY/dXJs
Mj1kcmFmdC1pZXRmLWVtdS1lYXB0bHNjZXJ0LTA2Lg0KDQpTZWUgb3VyIHJlc3BvbnNlcyBpbi1s
aW5lLg0KDQotLU1vaGl0DQoNCk9uIDEwLzI0LzIwIDE6NDQgUE0sIEVsd3luIERhdmllcyB2aWEg
RGF0YXRyYWNrZXIgd3JvdGU6DQo+IFJldmlld2VyOiBFbHd5biBEYXZpZXMNCj4gUmV2aWV3IHJl
c3VsdDogUmVhZHkgd2l0aCBOaXRzDQo+DQo+IEkgYW0gdGhlIGFzc2lnbmVkIEdlbi1BUlQgcmV2
aWV3ZXIgZm9yIHRoaXMgZHJhZnQuIFRoZSBHZW5lcmFsIEFyZWENCj4gUmV2aWV3IFRlYW0gKEdl
bi1BUlQpIHJldmlld3MgYWxsIElFVEYgZG9jdW1lbnRzIGJlaW5nIHByb2Nlc3NlZA0KPiBieSB0
aGUgSUVTRyBmb3IgdGhlIElFVEYgQ2hhaXIuICBQbGVhc2UgdHJlYXQgdGhlc2UgY29tbWVudHMg
anVzdA0KPiBsaWtlIGFueSBvdGhlciBsYXN0IGNhbGwgY29tbWVudHMuDQo+DQo+IEZvciBtb3Jl
IGluZm9ybWF0aW9uLCBwbGVhc2Ugc2VlIHRoZSBGQVEgYXQNCj4NCj4gPGh0dHBzOi8vdHJhYy5p
ZXRmLm9yZy90cmFjL2dlbi93aWtpL0dlbkFydGZhcT4uDQo+DQo+IERvY3VtZW50OiBkcmFmdC1p
ZXRmLWVtdS1lYXB0bHNjZXJ0LTA1DQo+IFJldmlld2VyOiBFbHd5biBEYXZpZXMNCj4gUmV2aWV3
IERhdGU6IDIwMjAtMTAtMjQNCj4gSUVURiBMQyBFbmQgRGF0ZTogMjAyMC0xMC0yOA0KPiBJRVNH
IFRlbGVjaGF0IGRhdGU6IE5vdCBzY2hlZHVsZWQgZm9yIGEgdGVsZWNoYXQNCj4NCj4gU3VtbWFy
eTogIFJlYWR5IHdpdGggbml0cy4gIFRoZXJlIGFyZSBxdWl0ZSBhIG51bWJlciBvZiByZWZlcmVu
Y2VzIHRvDQo+IGFzc29jaWF0ZWQgd29yayB0aGF0IGlzIHN0aWxsIGluIHByb2dyZXNzIGFzIGRy
YWZ0cy4gIFdoaWxzdCB0aGlzIGlzIHVubGlrZWx5DQo+IHRvIGNvbXByb21pc2UgdGhlIGNvbnRl
bnQgb2YgdGhpcyB3b3JrLCBpdCB3aWxsIHBvdGVudGlhbGx5IGRlbGF5IGl0cw0KPiBwdWJsaWNh
dGlvbi4gIEluIHBhcnRpY3VsYXIgSSBoYXZlIHN1Z2dlc3RlZCByZXdyaXRpbmcgczQuMi43IHRv
IG9taXQgbW9yZQ0KPiBzcGVjdWxhdGl2ZSByZWZlcmVuY2VzIHRvIGluY29tcGxldGUgd29yayBp
biBmYXZvdXIgb2YgYSBnZW5lcmFsIHJlY29tbWVuZGF0aW9uDQo+IHRvIG1ha2UgdXNlIG9mIHJl
bGV2YW50IG5ldyBwcm9wb3NhbHMgYXMgdGhleSBiZWNvbWUgYXZhaWxhYmxlLg0KTW9zdCBvZiB0
aGUgbm9ybWF0aXZlIHJlZmVyZW5jZXMgYXJlIHRvIGFscmVhZHkgcHVibGlzaGVkIFJGQ3MuIFRo
ZXJlIGlzIA0Kb25seSBvbmUgbm9ybWF0aXZlIHJlZmVyZW5jZSB0byBhIGRyYWZ0IHdoaWNoIHdp
bGwgYWxzbyBob3BlZnVsbHkgbW92ZSANCmZvcndhcmQgc29vbi4gWW91IGFyZSByaWdodCB0aGF0
IHRoZXJlIGFyZSBtYW55IGluZm9ybWF0aW9uYWwgcmVmZXJlbmNlcyANCnRvIHdvcmsgaW4gcHJv
Z3Jlc3MuIEJ1dCB0aGlzIGlzIHdoYXQgdGhlIHdvcmtpbmcgZ3JvdXAgcGFydGljaXBhbnRzIA0K
d2FudGVkLiBGb3IgZXhhbXBsZSwgSGFubmVzIHN1Z2dlc3RlZCB0byBhZGQgcmVmZXJlbmNlcyB0
byBuZXcgVExTIA0KY2VydGlmaWNhdGUgdHlwZXMgYW5kIGNlcnRpZmljYXRlIGNvbXByZXNzaW9u
IHdpdGggQ0JPUjogDQpodHRwczovL21haWxhcmNoaXZlLmlldGYub3JnL2FyY2gvbXNnL2VtdS9j
SVZFR0Y2ZUxDdnJkQ3FrQTVaemp4b3I5dnMvLiANCkkgdGhpbmsgaXQgY2FuIGJlIHZhbHVhYmxl
IGZvciBhIHJlYWRlciB0byBoYXZlIGNvbmNyZXRlIGV4YW1wbGVzIG9mIA0Kd29yayBpbiBwcm9n
cmVzcy4NCj4NCj4gTWFqb3IgSXNzdWVzOg0KPiBOb25lDQo+DQo+IE1pbm9yIElzc3VlczoNCj4g
Tm9uZQ0KPg0KPiBOaXRzIGFuZCBFZGl0b3JhbCBJc3N1ZXM6DQo+DQo+IEdlbmVyYWw6wqAgUkZD
IDIxMTkga2V5IHdvcmRzOsKgIEluIHRoZSBkb2N1bWVudCB0aGVyZSBhcmUgdHdvIE1VU1RzIGFu
ZCBhIFNIT1VMRA0KPiBOT1Qgbm9uZSBvZiB3aGljaCBhcmUgYXBwcm9wcmlhdGUgdXNhZ2VzIGlu
IG15IG9waW5pb24gKHNlZSBub3RlcyBiZWxvdyksIGFzaWRlDQo+IGZyb20gdGhlwqAgaW50ZW5k
ZWQgaW5mcm9tYXRpb25hbCBzdGF0dXMuwqAgVGhlIFJGQyAyMTE5IGV0YyBib2lsZXJwbGF0ZSBp
biBzMg0KPiBjb3VsZCBiZSBvbWl0dGVkLg0KTm93IHRoZXJlIGlzIG9ubHkgb25lIFNIT1VMRCBO
T1QuIEknbGwgbGV0IHRoZSBJRVNHIGRlbGliZXJhdGUgaWYgdGhleSANCndhbnQgdXMgdG8gY2hh
bmdlIHRvICJzaG91bGQgbm90IiBpbnN0ZWFkLiBCdXQgSSB0aGluayBpdCBpcyBhbiANCmltcG9y
dGFudCBvcGVyYXRpb25hbCBndWlkZWxpbmUgYW5kIGFzIEFsYW4gRGVLb2sgbm90ZWQsIGFkbWlu
aXN0cmF0b3JzIA0Kc2hvdWxkIHJlYWxseSBlbnN1cmUgdGhhdCBjZXJ0aWZpY2F0ZSBjaGFpbnMg
ZG9uJ3QgY29udGFpbiBtb3JlIHRoYW4gMi00IA0KaW50ZXJtZWRpYXRlIGNlcnRpZmljYXRlcy4N
Cj4NCj4gQWJzdHJhY3Q6wqAgTmVlZCB0byBleHBhbmQgRUFQLVRMUyBhbmQgRUFQIG9uIGZpcnN0
IG9jY3VycmVuY2UuDQpEb25lLg0KPg0KPiBzMSwgZW5kIG9mIHBhcmEgMjrCoCBTdWdnZXN0IHMv
aW52b2x2ZXMgc2lnbmlmaWNhbnRseSBtb3JlIG9jdGV0cy9pbnZvbHZlcw0KPiBleGNoYW5nZSBv
ZiBzaWduaWZpY2FudGx5IG1vcmUgb2N0ZXRzLw0KRG9uZS4NCj4NCj4gczIsIGRlZmluaXRpb24g
b2YgRUFQIHNlcnZlcjrCoCBXaGVyZSB3b3VsZCBhIHJlYWRlciBmaW5kIGEgZGVmaW5pdGlvbiBv
Zg0KPiAiYmFja2VuZCBhdXRoZW50aWNhdGlvbiI/wqAgVW5jbGUgR29vZ2xlIHdhcyBzaW5ndWxh
cmx5IHVuaGVscGZ1bC4NClRoZSB0ZXh0IGRvZXMgc2F5ICJSZWFkZXJzIGFyZSBleHBlY3RlZCB0
byBiZSBmYW1pbGlhciB3aXRoIHRoZSB0ZXJtcyANCmFuZCBjb25jZXB0cyB1c2VkIGluIEVBUCBb
UkZDMzc0OF0iLiBUaGUgdGVybSBiYWNrZW5kIGF1dGhlbnRpY2F0aW9uIA0Kc2VydmVyIGlzIGRl
ZmluZWQgdGhlcmU6IA0KaHR0cHM6Ly90b29scy5pZXRmLm9yZy9odG1sL3JmYzM3NDgjc2VjdGlv
bi0xLjIuIEluIHRoaXMgZG9jdW1lbnQsIHdlIA0Kb25seSBkZWZpbmUgdGhlIHRlcm1zIHRoYXQg
YXJlIHVzZWQgZnJlcXVlbnRseS4gQW5kIGJhY2tlbmQgDQphdXRoZW50aWNhdGlvbiBzZXJ2ZXIg
d2Fzbid0IG9uZSBvZiB0aGVtLg0KPg0KPiBzMywgbGFzdCBwYXJhOsKgIGNsYXJpZnkgdGhlIG1l
YW5pbmcgb2Yga0I6wqAgc3VnZ2VzdCBzL34gNjBrQi9hcHByb3hpbWF0ZWx5IDYwDQo+IGtieXRl
cy8gKEkgYXNzdW1lKS4NCkRvbmUuDQo+DQo+IHM0OsKgIFRoZSB1c2FnZSBvZiB0aGUgZm9ybSAi
IHdlIGxvb2svZGlzY3Vzcy9ldGMuIiB0eXBpY2FsbHnCoCB1c2VkIGluIGFjYWRlbWljDQo+IHBh
cGVycyBpcyBub3QgYXBwcm9wcmlhdGUgZm9yIHN0YW5kYXJkcyBkb2N1bWVudHMuwqAgU2VjdGlv
biA0IG5lZWRzIHRvIGJlDQo+IHJlZHJhZnRlZCB0byBlbGltaW5hdGUgdGhpcyB1c2FnZS7CoCBU
aGUgZm9sbG93aW5nIG1heSBiZSBhcHByb3ByaWF0ZToNCj4NCj4gT0xEOg0KPiBUaGlzIHNlY3Rp
b24gZGlzY3Vzc2VzIHNvbWUgcG9zc2libGUgYWx0ZXJuYXRpdmVzIGZvciBvdmVyY29taW5nIHRo
ZSBjaGFsbGVuZ2UNCj4gb2YgbGFyZ2UgY2VydGlmaWNhdGVzIGFuZCBsb25nIGNlcnRpZmljYXRl
IGNoYWlucyBpbiBFQVAtIFRMUyBhdXRoZW50aWNhdGlvbi4NCj4gSW4gU2VjdGlvbiA0LjEgd2Ug
bG9vayBhdCByZWNvbW1lbmRhdGlvbnMgdGhhdCByZXF1aXJlIGFuIHVwZGF0ZSBvZiB0aGUNCj4g
Y2VydGlmaWNhdGVzIG9yIGNlcnRpZmljYXRlIGNoYWlucyB0aGF0IGFyZSB1c2VkIGZvciBFQVAt
VExTIGF1dGhlbnRpY2F0aW9uDQo+IHdpdGhvdXQgcmVxdWlyaW5nIGNoYW5nZXMgdG8gdGhlIGV4
aXN0aW5nIEVBUC1UTFMgY29kZSBiYXNlLiBXZSBhbHNvIHByb3ZpZGUNCj4gc29tZSBndWlkZWxp
bmVzIHdoZW4gaXNzdWluZyBjZXJ0aWZpY2F0ZXMgZm9yIHVzZSB3aXRoIEVBUC1UTFMuIEluIFNl
Y3Rpb24gNC4yDQo+IHdlIGxvb2sgYXQgcmVjb21tZW5kYXRpb25zIHRoYXQgcmVseSBvbiB1cGRh
dGVzIHRvIHRoZSBFQVAtVExTIGltcGxlbWVudGF0aW9ucw0KPiB3aGljaCBjYW4gYmUgZGVwbG95
ZWQgd2l0aCBleGlzdGluZyBjZXJ0aWZpY2F0ZXMuIEluIFNlY3Rpb24gNC4zIHdlIHNob3J0bHkN
Cj4gZGlzY3VzcyB0aGUgc29sdXRpb24gdG8gdXBkYXRlIG9yIHJlY29uZmlndXJlIGF1dGhlbnRp
Y2F0b3Igd2hpY2ggY2FuIGJlDQo+IGRlcGxveWVkIHdpdGhvdXQgY2hhbmdlcyB0byBleGlzdGlu
ZyBjZXJ0aWZpY2F0ZXMgb3IgRUFQLVRMUyBjb2RlLg0KPg0KPiBORVc6DQo+IFRoaXMgc2VjdGlv
biBkaXNjdXNzZXMgc29tZSBwb3NzaWJsZSBhbHRlcm5hdGl2ZXMgZm9yIG92ZXJjb21pbmcgdGhl
IGNoYWxsZW5nZQ0KPiBvZiBsYXJnZSBjZXJ0aWZpY2F0ZXMgYW5kIGxvbmcgY2VydGlmaWNhdGUg
Y2hhaW5zIGluIEVBUC0gVExTIGF1dGhlbnRpY2F0aW9uLg0KPiBTZWN0aW9uIDQuMSBjb25zaWRl
cnMgcmVjb21tZW5kYXRpb25zIHRoYXQgcmVxdWlyZSBhbiB1cGRhdGUgb2YgdGhlDQo+IGNlcnRp
ZmljYXRlcyBvciBjZXJ0aWZpY2F0ZSBjaGFpbnMgdGhhdCBhcmUgdXNlZCBmb3IgRUFQLVRMUyBh
dXRoZW50aWNhdGlvbg0KPiB3aXRob3V0IHJlcXVpcmluZyBjaGFuZ2VzIHRvIHRoZSBleGlzdGlu
ZyBFQVAtVExTIGNvZGUgYmFzZS4gVGhlIHNlY3Rpb24gYWxzbw0KPiBwcm92aWRlcyBzb21lIGd1
aWRlbGluZXMgdGhhdCBhaG91bGQgYmUgZm9sbG93ZWQgd2hlbiBpc3N1aW5nIGNlcnRpZmljYXRl
cyBmb3INCj4gdXNlIHdpdGggRUFQLVRMUy4gU2VjdGlvbiA0LjIgY29uc2lkZXJzIHJlY29tbWVu
ZGF0aW9ucyB0aGF0IHJlbHkgb24gdXBkYXRlcyB0bw0KPiB0aGUgRUFQLVRMUyBpbXBsZW1lbnRh
dGlvbnMgd2hpY2ggY2FuIGJlIGRlcGxveWVkIHdpdGggZXhpc3RpbmcgY2VydGlmaWNhdGVzLg0K
PiBGaW5hbGx5IFNlY3Rpb24gNC4zIGJyaWVmbHkgZGlzY3Vzc2VzIHdoYXQgY291bGQgYmUgZG9u
ZSB0byB1cGRhdGUgb3INCj4gcmVjb25maWd1cmUgYXV0aGVudGljYXRvcnMgd2hlcmUgaXQgaXMg
aW5mZWFzaWJsZSB0byByZXBsYWNlIGRlcGxveWVkDQo+IGNvbXBvbmVudHMgZ2l2aW5nIGEgc29s
dXRpb24gY2FuIGJlIGRlcGxveWVkIHdpdGhvdXQgY2hhbmdlcyB0byBleGlzdGluZw0KPiBjZXJ0
aWZpY2F0ZXMgb3IgRUFQLVRMUyBjb2RlLiBFTkRTDQpUaGFuayB5b3UuIEkgaGF2ZSB1c2VkIHlv
dXIgdGV4dCB3aXRoIHNsaWdodCBtb2RpZmljYXRpb25zLg0KPg0KPiBzNC4xLjEsIHBhcmEgMTog
cy9pcyBhcyBmb2xsb3dzL2FyZSBhcyBmb2xsb3dzLw0KRG9uZS4NCj4NCj4gczQuMS4xLCBwYXJh
IDIgKDFzdCBidWxsZXQpOiBzL09iamVjdCBJZGVudGlmaWVycyAoT0lEcykgaXMgQVNOLjEvVGhl
IE9iamVjdA0KPiBJZGVudGlmaWVyIChPSUQpIGlzIGFuIEFTTi4xLw0KRG9uZS4NCj4NCj4gczQu
MS4xLCBwYXJhIDMgKDFzdCBidWxsZXQpOiBOZWVkIHRvIGV4cGFuZCBERVIuIEFsc28gdXNlZnVs
IHRvIGFkZCByZWZlcmVuY2UNCj4gdG8gUkZDNTI4MCBhZnRlciBYLjUwOS4NCkRvbmUuDQo+DQo+
IHM0LjEuMSwgcGFyYSA0ICgxc3Qgc3ViLWJ1bGxldCBuIDFzdCBidWxsZXQpICd2cycgbmVlZHMg
dG8gYmUgZXhwYW5kZWQgLSBlaXRoZXINCj4gJ3ZlcnN1cycgb3IgKEJldHRlcikgJ2FzIGFnYWlu
c3QnLg0KRG9uZS4NCj4NCj4gczQuMS4zLCBwYXJhIDE6IFRoZSB1c2Ugb2YgY2FwaXRhbGl6ZWQg
U0hPVUxEIE5PVCBoZXJlIGlzLCBJIHRoaW5rLA0KPiBpbmFwcHJvcHJpYXRlLiBUaGlzIGlzIGFu
IG9wZXJhdGlvbmFsIHJlY29tbWVuZGF0aW9uIHJhdGhlciB0aGFuIGEgcHJvdG9jb2wNCj4gcmVx
dWlyZW1lbnQsIHNvIHMvU0hPVUxEIE5PVC9zaG91bGQgbm90Ly4NCk5vIGNoYW5nZS4gU2VlIGFi
b3ZlLg0KPg0KPiBzNC4yLjIsIHBhcmEgMTogcy91c2VmdWwgd2hlbiwgZm9yIGV4YW1wbGUsIHdo
ZW4vdXNlZnVsIHdoZW4sIGZvciBleGFtcGxlLC8NCkRvbmUuDQo+DQo+IHM0LjIuNDogcy9jYW4g
ZGVmaW5lIGRpY3Rpb25hcnkgb2YvY2FuIGRlZmluZSBhIGRpY3Rpb25hcnkgb2YvDQpEb25lLg0K
Pg0KPiBzNC4yLjU6IHMvRm9yIGEgY2xpZW50IHRoYXQgaGFzIGFsbCBpbnRlcm1lZGlhdGVzLC9G
b3IgYSBjbGllbnQgdGhhdCBoYXMgYWxsDQo+IGludGVybWVkaWF0ZSBjZXJ0aWZpY2F0ZXMgaW4g
dGhlIGNlcnRpZmljYXRlIGNoYWluLw0KRG9uZS4NCj4NCj4gczQuMi41OiBUaGUgc2Vjb25kIHNl
bnRlbmNlIG9mIHRoaXMgc2VjdGlvbiBuZWVkcyB0byBiZSByZXdyaXR0ZW4gYXMgaWYNCj4gZHJh
ZnQtdGhvbXNvbi10bHMtc2ljIGlzIGFscmVhZHkgYW4gUkZDLg0KQ291bGQgeW91IGdpdmUgdGhl
IFJGQyBudW1iZXIuIEFzIGZhciBhcyBJIGNhbiB0ZWxsLCBpdCBpcyBhbiBleHBpcmVkIA0KcGVy
c29uYWwgc3VibWlzc2lvbiBidXQgSSBjb3VsZCBiZSB3cm9uZzogDQpodHRwczovL2RhdGF0cmFj
a2VyLmlldGYub3JnL2RvYy9kcmFmdC10aG9tc29uLXRscy1zaWMvDQo+DQo+IHM0LjIuNzogVGhp
cyBzZWN0aW9uIGlzIG5vdCAnZnV0dXJlIHByb29mJy4gSXQgc2hvdWxkIGJlIHJld3JpdHRlbiBv
bWl0dGluZyB0aGUNCj4gZXhwbGljaXQgZXhhbXBsZXMgYnV0IGV4aG9ydGluZyBpbXBsZW1lbnRv
cnMgYW5kIG9wZXJhdGlycyB0byBjb25zaWRlciByZWxldmFudA0KPiBmdXR1cmUgZGV2ZWxvcG1l
bnRzLg0KTm8gY2hhbmdlLiBTZWUgYWJvdmUuDQo+DQo+IHM0LjMsIHBhcmEgMTogVGhlIHNlY29u
ZCBhbmQgdGhpcmQgc2VudGVuY2VzIGRvbid0IHJlYWQgd2VsbC5TdWdnZXN0Og0KPiBPTEQ6DQo+
IEFub3RoZXIgc2Vjb25kIHJlYXNvbiBpcyB0aGF0IHVubGltaXRlZCBjb21tdW5pY2F0aW9uIGZy
b20gYW4gdW5hdXRoZW50aWNhdGVkDQo+IGRldmljZSBhcyBFQVAgY291bGQgb3RoZXJ3aXNlIGJl
IHVzZSBmb3IgYnVsayBkYXRhIHRyYW5zZmVyLiBBIHRoaXJkIHJlYXNvbiBpcw0KPiB0byBwcmV2
ZW50IGRlbmlhbC1vZi1zZXJ2aWNlIGF0dGFja3MuIE5FVzogT3RoZXIgcmVhc29ucyBpbmNsdWRl
IHRoYXQgdW5saW1pdGVkDQo+IGNvbW11bmljYXRpb24gZnJvbSBhbiB1bmF1dGhlbnRpY2F0ZWQg
ZGV2aWNlIHVzaW5nIEVBUCBjb3VsZCBwcm92aWRlIGEgY2hhbm5lbA0KPiBmb3IgaW5hcHByb3By
aWF0ZSBidWxrIGRhdGEgdHJhbnNmZXIsIGFuZCB0aGF0IGNvbW11bmljYXRpb24gY291bGQgZmFj
aWxpdGF0ZQ0KPiBkZW5pYWwtb2Ytc2VydmljZSBhdHRhY2tzLiBFTkRTDQpVcGRhdGVkIHdpdGgg
c2xpZ2h0IG1vZGlmaWNhdGlvbnMuDQo+DQo+IHM2LCBwYXJhIDI6IFRoZSBNVVNUcyBsb29rIGFz
IGlmIHRoZXkgYXJlIGltcG9zaW5nIHJlcXVpcmVtZW50cyBvbg0KPiBkcmFmdC1pZXRmLXRscy1j
ZXJ0aWZpY2F0ZS1jb21wcmVzc2lvbi4gSSBhbSBzdXJlIHRoYXQgdGhlIGRyYWZ0IHdvdWxkIGJl
DQo+IGVmZmVjdGl2ZWx5IHNheWluZyB0aGVzZSB0aGluZ3MgYW55d2F5IChpZiBub3QsIHdoeSBu
b3Q/KSBBbHNvIHRoZSBmaXJzdA0KPiBzZW50ZW5jZSBhcHBlYXJzIHRvIGJlIHRydW5jYXRlZCAt
IGl0IGRvZXNuJ3QgbWFrZSBhbnkgc2Vuc2UgYXMgaXQgc3RhbmRzLiBJDQo+IHN1Z2dlc3QgcmV3
cml0aW5nIHRoZSBwYXJhZ3JhcGggd2l0aCB0aGUgdGhpcmQgc2VudGVuY2UgZmlyc3QsIGFuZCwg
aWYgcmVhbGx5DQo+IG5lY2Vzc2FyeSwgYWRkaW5nIHRoZSB0d28gcG9pbnRzIGZyb20gdGhlIGZp
cnN0IHNlbnRlbmNlcyBhcyByZW1pbmRlcnMgcmF0aGVyDQo+IHRoYW4gTVVTVHMuDQpEb25lLg0K
Pg0KPg0KPg0KPiBfX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19f
Xw0KPiBFbXUgbWFpbGluZyBsaXN0DQo+IEVtdUBpZXRmLm9yZw0KPiBodHRwczovL3d3dy5pZXRm
Lm9yZy9tYWlsbWFuL2xpc3RpbmZvL2VtdQ0K


From nobody Wed Oct 28 12:21:19 2020
Return-Path: <noreply@ietf.org>
X-Original-To: emu@ietf.org
Delivered-To: emu@ietfa.amsl.com
Received: from ietfa.amsl.com (localhost [IPv6:::1]) by ietfa.amsl.com (Postfix) with ESMTP id AE7AF3A0BAD; Wed, 28 Oct 2020 12:21:14 -0700 (PDT)
MIME-Version: 1.0
Content-Type: text/plain; charset="utf-8"
Content-Transfer-Encoding: 8bit
From: Barry Leiba via Datatracker <noreply@ietf.org>
To: "The IESG" <iesg@ietf.org>
Cc: draft-ietf-emu-eaptlscert@ietf.org, emu-chairs@ietf.org, emu@ietf.org, Joseph Salowey <joe@salowey.net>, joe@salowey.net
X-Test-IDTracker: no
X-IETF-IDTracker: 7.21.0
Auto-Submitted: auto-generated
Precedence: bulk
Reply-To: Barry Leiba <barryleiba@computer.org>
Message-ID: <160391287468.14554.8990471287012823249@ietfa.amsl.com>
Date: Wed, 28 Oct 2020 12:21:14 -0700
Archived-At: <https://mailarchive.ietf.org/arch/msg/emu/ZxcvQ8JQHoRGF0DyuoK_v9ACqXg>
Subject: [Emu] Barry Leiba's No Objection on draft-ietf-emu-eaptlscert-06: (with COMMENT)
X-BeenThere: emu@ietf.org
X-Mailman-Version: 2.1.29
List-Id: "EAP Methods Update \(EMU\)" <emu.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/emu>, <mailto:emu-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/emu/>
List-Post: <mailto:emu@ietf.org>
List-Help: <mailto:emu-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/emu>, <mailto:emu-request@ietf.org?subject=subscribe>
X-List-Received-Date: Wed, 28 Oct 2020 19:21:15 -0000

Barry Leiba has entered the following ballot position for
draft-ietf-emu-eaptlscert-06: No Objection

When responding, please keep the subject line intact and reply to all
email addresses included in the To and CC lines. (Feel free to cut this
introductory paragraph, however.)


Please refer to https://www.ietf.org/iesg/statement/discuss-criteria.html
for more information about IESG DISCUSS and COMMENT positions.


The document, along with other ballot positions, can be found here:
https://datatracker.ietf.org/doc/draft-ietf-emu-eaptlscert/



----------------------------------------------------------------------
COMMENT:
----------------------------------------------------------------------

Thanks for this; it will be useful to have this issue fixed.

Thereâs something Iâd like to discuss, but without making it a blocking DISCUSS:
While I understand the reason for putting this forward as Informational, it
does strike me more as a Standards Track Applicability Statement.  BCP 9 says
(in RFC 2026 Section 3.2):

   An Applicability Statement specifies how, and under what
   circumstances, one or more TSs may be applied to support a particular
   Internet capability.

Reading the rest of Section 3.2 as well, I think that it fits exactly what
youâre doing with this document: the document is saying that thereâs an
interoperability problem with large certs and long chains, and here are things
to do in order to make that work.  Letâs please have a brief discussion about
whether this should instead be published at Proposed Standard as an AS.

âââââ

Below are some nits that I hope youâll consider, but thereâs no need to respond
in detail here; please do as you think best.

â Section 1 â

   vendor specific EAP methods.

Need a hyphen in âvendor-specificâ.

   EAP-TLS
   deployments typically authenticates both the EAP peer and the EAP

Make it âauthenticateâ.

   Section 3.1 of [RFC3748] states that EAP implementations can assume a
   MTU of at least 1020 octets from lower layers.

Unless you have a way of pronouncing âMTUâ that I donât, make it âan MTUâ.

   Such fragmentation can not only negatively
   affect the latency, but also results in other challenges.

The âcanâ is misplaced; make it ânot only can affectâ.

â Section 2 â

   The document additionally uses the terms trust anchor and
   certification path defined in [RFC5280].

I would put âtrust anchorâ and âcertification pathâ in quotes here.

â Section 3 â

   Certificate sizes can however be large

Commas are needed both before and after âhoweverâ.  Also, the list talks about
a singular âcertificateâ, so the lead-in should match that (and you donât need
to say that a *size* can be large): âA certificate can, however, be large for a
number of reasons:â

The list is also not parallel (the third item, in particular, is not like the
others).  I would make the whole list be complete sentences, like this,
referring to âa certificateâ in the lead-in:

NEW
   o  It can have a long Subject Alternative Name field.

   o  It can have long Public Key and Signature fields.

   o  It can contain multiple object identifiers (OID) that indicate the
      permitted uses of the certificate as noted in Section 5.3 of
      [RFC5216].  Most implementations verify the presence of these OIDs
      for successful authentication.

   o  It can contain multiple user groups.
END

â Section 4.1 â

Throughout this paragraph you refer to âsize of public keysâ and âsize of
digital signaturesâ.  Itâs a really nitty nit, but I would make these all
singular, because weâre really talking about the size of an individual public
key or digital signature, not the size of a collection of them.

   authentication which can alleviate the problem of authenticators

There needs to be a comma before âwhichâ.

   ECC based cipher suites with existing code can significantly

Hyphenate âECC-basedâ.

â Section 4.1.1 â

   OIDs are used lavishly in X.509 certificates

I like it: âlavishlyâ is not a word we often see in RFCs.  :-)

      DNs
      used in the issuer and subject fields as well as numerous
      extensions.

This is not a complete sentence; please fix that (I think youâre just missing
âareâ after âDNsâ).

   CN=Coolest IoT Gadget Ever

Oh!  I want that!




From nobody Thu Oct 29 09:23:56 2020
Return-Path: <joe@salowey.net>
X-Original-To: emu@ietfa.amsl.com
Delivered-To: emu@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 4EB053A07E6 for <emu@ietfa.amsl.com>; Thu, 29 Oct 2020 09:23:54 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.898
X-Spam-Level: 
X-Spam-Status: No, score=-1.898 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, HTML_MESSAGE=0.001, SPF_HELO_NONE=0.001, SPF_PASS=-0.001, URIBL_BLOCKED=0.001] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (2048-bit key) header.d=salowey-net.20150623.gappssmtp.com
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 ayv0Pm0ggVCp for <emu@ietfa.amsl.com>; Thu, 29 Oct 2020 09:23:52 -0700 (PDT)
Received: from mail-qt1-x82d.google.com (mail-qt1-x82d.google.com [IPv6:2607:f8b0:4864:20::82d]) (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 A91D53A00C9 for <emu@ietf.org>; Thu, 29 Oct 2020 09:23:52 -0700 (PDT)
Received: by mail-qt1-x82d.google.com with SMTP id s39so2202048qtb.2 for <emu@ietf.org>; Thu, 29 Oct 2020 09:23:52 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=salowey-net.20150623.gappssmtp.com; s=20150623; h=mime-version:from:date:message-id:subject:to; bh=kFbjBr7UMvyzvcYieXJBZG/WU/gEj2TOCdbQUeQfJWg=; b=u5/pb6qHnXXmbjju1zlFWdNPHTV0ZRRk9H66zAk5IKqjhho5RVmyNn/i9qzW2mXiGd UGHbOLuI6pfaFS4Z417JCkE5Dchy4YnEN7b/J3OkCCMR05dQ7NaUv1t12POpRjEKRwUR U3zcaZYHTMXbBB/GmpuvaT7YSfaVni6bKkTYjGk3h5dnhVYxrUnDuwRDDVwlW5Qlqq4U D2S78jg0ce69pQGDj/lIbLnkdP5SqQNE0bQUFrMrjW4f4WkxUaWBfXPz4u4X9Oywooyp aqqImqiRDrFiHR06GE9qTqGL3Op2zgUpe9oVMs9i+VvkcW7hpJFT3Sy61jjR0txvBK5W /IVQ==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:mime-version:from:date:message-id:subject:to; bh=kFbjBr7UMvyzvcYieXJBZG/WU/gEj2TOCdbQUeQfJWg=; b=Epi2GEeX4GBpqmz1kBuVCqZ19yTB2uzSDFPoW93I7ooNF7u0W1lHSKDJBlFy10Bvx7 d07ks1EIDEwhfKA06tiuGfwjSfHgBwPK3CaQfga1OUcAYL4C+Jm4+08SJz3Cl6nJQrUK ooj5mCEpMf7amfdMc6aGIgoW1TY3MUETpsQACjzSPFR/a8AOWnyiop720r5+/uSdHNxN kqeWhM0l8twtvPxUOLh9Rw24Z7845CDNJF/KdHTnHsGu8Dm9joZRwCM727VkomcqyuEm zcI1V5X3g9pUzLsG8+GILtJ3leQiUQZIf2zsakmMf9b9mb1sL/vbrTziJO1uXaWs8l+o fV7Q==
X-Gm-Message-State: AOAM531WqkStPhDhOll0z2azJ8c7M7lhY9BXH+sZ8ME1Mlds2yBsE56d IjZUPP6W0lF/0TrKeVhtoJ8mQHtY3iTOPxktX/FemZcSDXjig8kp
X-Google-Smtp-Source: ABdhPJwG1lVBgxEMceEKVzX6KwcYvSWSH64Q7P7h9zTzJhbdLunawsoxWR8rrz4rtYYbewSe0ut4UElSJKrCFze8OWk=
X-Received: by 2002:ac8:120a:: with SMTP id x10mr4223095qti.95.1603988631488;  Thu, 29 Oct 2020 09:23:51 -0700 (PDT)
MIME-Version: 1.0
From: Joseph Salowey <joe@salowey.net>
Date: Thu, 29 Oct 2020 09:23:40 -0700
Message-ID: <CAOgPGoDbsunLOxrnFxa8uMxG6JYObX_r5VLOvVib5QmFHGOrwA@mail.gmail.com>
To: EMU WG <emu@ietf.org>
Content-Type: multipart/alternative; boundary="0000000000009ab73c05b2d1b4d4"
Archived-At: <https://mailarchive.ietf.org/arch/msg/emu/kvwl5pRWEPrca2OdX7MjpF_nw5o>
Subject: [Emu] Consensus Call on OCSP usage in draft-ietf-emu-eap-tls13-11
X-BeenThere: emu@ietf.org
X-Mailman-Version: 2.1.29
Precedence: list
List-Id: "EAP Methods Update \(EMU\)" <emu.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/emu>, <mailto:emu-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/emu/>
List-Post: <mailto:emu@ietf.org>
List-Help: <mailto:emu-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/emu>, <mailto:emu-request@ietf.org?subject=subscribe>
X-List-Received-Date: Thu, 29 Oct 2020 16:23:54 -0000

--0000000000009ab73c05b2d1b4d4
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable

An issue was raised in a review of  draft-ietf-emu-eap-tls13-11 on the
mandatory requirement for OCSP stapling [1].  The document makes the use of
OCSP mandatory in section 5.4 [2]. Several folks have pointed out that this
may not be feasible in all deployments.  This is a quick consensus call for
this issue.   Please indicate which option below you support and why.
Please respond by November 5, 2020.

1. Keep the text as is with OCSP mandatory for all implementations

2. Require Servers to Implement and Recommended to Use OCSP with text
similar to the following:

=E2=80=9CEAP-TLS servers supporting TLS 1.3 MUST implement Certificate Stat=
us
Requests (OCSP stapling) as specified in Section 4.4.2.1 of [RFC8446].  It
is RECOMMENDED that EAP-TLS peers and servers use OCSP stapling for
verifying the status of server certificates as specified in Section 4.4.2.1
of [RFC8446]. When an EAP-TLS peer uses OCSP to verify the certificate
status of the EAP-TLS server, it MUST use Certificate Status Requests for
the server's certificate chain and it MUST treat a CertificateEntry (except
the trust anchor) without a valid CertificateStatus extension as invalid
and abort the handshake with an appropriate alert.=E2=80=9C

Thanks,

Joe

[1] https://mailarchive.ietf.org/arch/msg/emu/0DnfUWPqvKX0_Wo8s-ZypergMHI/
[2] https://tools.ietf.org/html/draft-ietf-emu-eap-tls13-11#section-5.4

--0000000000009ab73c05b2d1b4d4
Content-Type: text/html; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable

<div dir=3D"ltr">An issue was raised in a review of =C2=A0draft-ietf-emu-ea=
p-tls13-11 on the mandatory requirement for OCSP stapling [1].=C2=A0 The do=
cument makes the use of OCSP mandatory in section 5.4 [2]. Several folks ha=
ve pointed out that this may not be feasible in all deployments.=C2=A0 This=
 is a quick consensus call for this issue. =C2=A0 Please indicate which opt=
ion below you support and why.=C2=A0 Please respond=C2=A0by November 5, 202=
0.=C2=A0<br><br>1. Keep the text as is with OCSP mandatory for all implemen=
tations<br><br>2. Require Servers to Implement and Recommended to Use OCSP =
with text similar to the following:<br><br>=E2=80=9CEAP-TLS servers support=
ing TLS 1.3 MUST implement Certificate Status Requests (OCSP stapling) as s=
pecified in Section 4.4.2.1 of [RFC8446].=C2=A0 It is RECOMMENDED that EAP-=
TLS peers and servers use OCSP stapling for verifying the status of server =
certificates as specified in Section 4.4.2.1 of [RFC8446]. When an EAP-TLS =
peer uses OCSP to verify the certificate status of the EAP-TLS server, it M=
UST use Certificate Status Requests for the server&#39;s certificate chain =
and it MUST treat a CertificateEntry (except the trust anchor) without a va=
lid CertificateStatus extension as invalid and abort the handshake with an =
appropriate alert.=E2=80=9C<div><br></div><div>Thanks,</div><div><br></div>=
<div>Joe</div><div><div><br></div>[1] <a href=3D"https://mailarchive.ietf.o=
rg/arch/msg/emu/0DnfUWPqvKX0_Wo8s-ZypergMHI/">https://mailarchive.ietf.org/=
arch/msg/emu/0DnfUWPqvKX0_Wo8s-ZypergMHI/</a><br>[2] <a href=3D"https://too=
ls.ietf.org/html/draft-ietf-emu-eap-tls13-11#section-5.4">https://tools.iet=
f.org/html/draft-ietf-emu-eap-tls13-11#section-5.4</a></div></div>

--0000000000009ab73c05b2d1b4d4--


From nobody Thu Oct 29 09:53:00 2020
Return-Path: <lear@cisco.com>
X-Original-To: emu@ietfa.amsl.com
Delivered-To: emu@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id E4D0F3A0971 for <emu@ietfa.amsl.com>; Thu, 29 Oct 2020 09:52:58 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -9.6
X-Spam-Level: 
X-Spam-Status: No, score=-9.6 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIMWL_WL_MED=-0.001, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, DKIM_VALID_EF=-0.1, HTML_MESSAGE=0.001, SPF_PASS=-0.001, URIBL_BLOCKED=0.001, USER_IN_DEF_DKIM_WL=-7.5] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (1024-bit key) header.d=cisco.com
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 RSuceb7vI1Gl for <emu@ietfa.amsl.com>; Thu, 29 Oct 2020 09:52:57 -0700 (PDT)
Received: from aer-iport-1.cisco.com (aer-iport-1.cisco.com [173.38.203.51]) (using TLSv1.2 with cipher DHE-RSA-SEED-SHA (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 046953A09D4 for <emu@ietf.org>; Thu, 29 Oct 2020 09:52:56 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=cisco.com; i=@cisco.com; l=5957; q=dns/txt; s=iport; t=1603990377; x=1605199977; h=from:message-id:mime-version:subject:date:in-reply-to:cc: to:references; bh=1G84lBc04ilLK6ZIGLKg3JJoi3PDrzVn+L2+b8sWF+8=; b=GdgeXxZGNJ51OwxycfbKHIWeM1TqJwQkNAggfoNaBtxNRZecXXC+8Ha2 EH55TNGqy6ITKJoyW+FZJs5/7kOUgg/5zVhEs/097ixAyWW0iqkK6/K0s pErLZHEwBTjdkaZ1Xg19B+fjqJW1Ri81GDUVBdH3/qCpEQJYKRcU6fZxE A=;
X-IronPort-Anti-Spam-Filtered: true
X-IronPort-Anti-Spam-Result: =?us-ascii?q?A0DSAgAo85pf/xbLJq1iHAEBAQEBAQc?= =?us-ascii?q?BARIBAQQEAQGCD4F7gR9VATIthD2JBYgQlAyIGQsBAQENAQEYAQoMBAEBhEo?= =?us-ascii?q?CgggmOBMCAwEBCwEBBQEBAQIBBgRxhWEMhXIBAQEBAgEBARsGSwsFCwsOCic?= =?us-ascii?q?DAgInHxEGE4MmAYJcIA+uLnaBMoQ+AYEYhQsGgTiNVYIAgREnHIIfLj6CXAE?= =?us-ascii?q?BAgGBRIMvM4IsBLgZgnaDGYVvkXoDH4MXihCUPpI7DIt0kWaDYAIEBgUCFYF?= =?us-ascii?q?rI4FXMxoIGxU7KgGCCgEBMj4SGQ2PRAEIh1eFRUADMAI2AgYBCQEBAwmOSAE?= =?us-ascii?q?B?=
X-IronPort-AV: E=Sophos; i="5.77,430,1596499200"; d="scan'208,217"; a="30732462"
Received: from aer-iport-nat.cisco.com (HELO aer-core-2.cisco.com) ([173.38.203.22]) by aer-iport-1.cisco.com with ESMTP/TLS/DHE-RSA-SEED-SHA; 29 Oct 2020 16:52:52 +0000
Received: from ams3-vpn-dhcp86.cisco.com (ams3-vpn-dhcp86.cisco.com [10.61.64.86]) by aer-core-2.cisco.com (8.15.2/8.15.2) with ESMTPS id 09TGqq8w031546 (version=TLSv1.2 cipher=DHE-RSA-AES256-GCM-SHA384 bits=256 verify=NO); Thu, 29 Oct 2020 16:52:52 GMT
From: Eliot Lear <lear@cisco.com>
Message-Id: <5D2BBCBB-62B9-41F5-86C3-A9CFD17AB38C@cisco.com>
Content-Type: multipart/alternative; boundary="Apple-Mail=_EE0C34E8-8633-46F5-88E4-6E299D2A7D08"
Mime-Version: 1.0 (Mac OS X Mail 13.4 \(3608.120.23.2.4\))
Date: Thu, 29 Oct 2020 17:52:52 +0100
In-Reply-To: <CAOgPGoDbsunLOxrnFxa8uMxG6JYObX_r5VLOvVib5QmFHGOrwA@mail.gmail.com>
Cc: EMU WG <emu@ietf.org>
To: Joseph Salowey <joe@salowey.net>
References: <CAOgPGoDbsunLOxrnFxa8uMxG6JYObX_r5VLOvVib5QmFHGOrwA@mail.gmail.com>
X-Mailer: Apple Mail (2.3608.120.23.2.4)
X-Outbound-SMTP-Client: 10.61.64.86, ams3-vpn-dhcp86.cisco.com
X-Outbound-Node: aer-core-2.cisco.com
Archived-At: <https://mailarchive.ietf.org/arch/msg/emu/7S26iap5KZsp5lwkmfGW0lyV6d0>
Subject: Re: [Emu] Consensus Call on OCSP usage in draft-ietf-emu-eap-tls13-11
X-BeenThere: emu@ietf.org
X-Mailman-Version: 2.1.29
Precedence: list
List-Id: "EAP Methods Update \(EMU\)" <emu.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/emu>, <mailto:emu-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/emu/>
List-Post: <mailto:emu@ietf.org>
List-Help: <mailto:emu-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/emu>, <mailto:emu-request@ietf.org?subject=subscribe>
X-List-Received-Date: Thu, 29 Oct 2020 16:52:59 -0000

--Apple-Mail=_EE0C34E8-8633-46F5-88E4-6E299D2A7D08
Content-Transfer-Encoding: quoted-printable
Content-Type: text/plain;
	charset=utf-8

Hi Joe,

My suggestion is that we add some discussion about what to do in the =
case of no connectivity to the CA.  This will be a not-uncommon =
occurrence, IMHO, in industrial use cases.

Eliot

> On 29 Oct 2020, at 17:23, Joseph Salowey <joe@salowey.net =
<mailto:joe@salowey.net>> wrote:
>=20
> An issue was raised in a review of  draft-ietf-emu-eap-tls13-11 on the =
mandatory requirement for OCSP stapling [1].  The document makes the use =
of OCSP mandatory in section 5.4 [2]. Several folks have pointed out =
that this may not be feasible in all deployments.  This is a quick =
consensus call for this issue.   Please indicate which option below you =
support and why.  Please respond by November 5, 2020.=20
>=20
> 1. Keep the text as is with OCSP mandatory for all implementations
>=20
> 2. Require Servers to Implement and Recommended to Use OCSP with text =
similar to the following:
>=20
> =E2=80=9CEAP-TLS servers supporting TLS 1.3 MUST implement Certificate =
Status Requests (OCSP stapling) as specified in Section 4.4.2.1 of =
[RFC8446].  It is RECOMMENDED that EAP-TLS peers and servers use OCSP =
stapling for verifying the status of server certificates as specified in =
Section 4.4.2.1 of [RFC8446]. When an EAP-TLS peer uses OCSP to verify =
the certificate status of the EAP-TLS server, it MUST use Certificate =
Status Requests for the server's certificate chain and it MUST treat a =
CertificateEntry (except the trust anchor) without a valid =
CertificateStatus extension as invalid and abort the handshake with an =
appropriate alert.=E2=80=9C
>=20
> Thanks,
>=20
> Joe
>=20
> [1] =
https://mailarchive.ietf.org/arch/msg/emu/0DnfUWPqvKX0_Wo8s-ZypergMHI/ =
<https://mailarchive.ietf.org/arch/msg/emu/0DnfUWPqvKX0_Wo8s-ZypergMHI/>
> [2] =
https://tools.ietf.org/html/draft-ietf-emu-eap-tls13-11#section-5.4 =
<https://tools.ietf.org/html/draft-ietf-emu-eap-tls13-11#section-5.4>_____=
__________________________________________
> Emu mailing list
> Emu@ietf.org <mailto:Emu@ietf.org>
> https://www.ietf.org/mailman/listinfo/emu


--Apple-Mail=_EE0C34E8-8633-46F5-88E4-6E299D2A7D08
Content-Transfer-Encoding: quoted-printable
Content-Type: text/html;
	charset=utf-8

<html><head><meta http-equiv=3D"Content-Type" content=3D"text/html; =
charset=3Dutf-8"></head><body style=3D"word-wrap: break-word; =
-webkit-nbsp-mode: space; line-break: after-white-space;" class=3D""><meta=
 http-equiv=3D"Content-Type" content=3D"text/html; charset=3Dutf-8" =
class=3D""><div style=3D"word-wrap: break-word; -webkit-nbsp-mode: =
space; line-break: after-white-space;" class=3D"">Hi Joe,<div =
class=3D""><br class=3D""></div><div class=3D"">My suggestion is that we =
add some discussion about what to do in the case of no connectivity to =
the CA. &nbsp;This will be a not-uncommon occurrence, IMHO, in =
industrial use cases.</div><div class=3D""><br class=3D""></div><div =
class=3D"">Eliot</div><div class=3D""><div class=3D""><br =
class=3D""><blockquote type=3D"cite" class=3D""><div class=3D"">On 29 =
Oct 2020, at 17:23, Joseph Salowey &lt;<a href=3D"mailto:joe@salowey.net" =
class=3D"">joe@salowey.net</a>&gt; wrote:</div><br =
class=3D"Apple-interchange-newline"><div class=3D""><meta =
http-equiv=3D"Content-Type" content=3D"text/html; charset=3Dutf-8" =
class=3D""><div dir=3D"ltr" class=3D"">An issue was raised in a review =
of &nbsp;draft-ietf-emu-eap-tls13-11 on the mandatory requirement for =
OCSP stapling [1].&nbsp; The document makes the use of OCSP mandatory in =
section 5.4 [2]. Several folks have pointed out that this may not be =
feasible in all deployments.&nbsp; This is a quick consensus call for =
this issue. &nbsp; Please indicate which option below you support and =
why.&nbsp; Please respond&nbsp;by November 5, 2020.&nbsp;<br =
class=3D""><br class=3D"">1. Keep the text as is with OCSP mandatory for =
all implementations<br class=3D""><br class=3D"">2. Require Servers to =
Implement and Recommended to Use OCSP with text similar to the =
following:<br class=3D""><br class=3D"">=E2=80=9CEAP-TLS servers =
supporting TLS 1.3 MUST implement Certificate Status Requests (OCSP =
stapling) as specified in Section 4.4.2.1 of [RFC8446].&nbsp; It is =
RECOMMENDED that EAP-TLS peers and servers use OCSP stapling for =
verifying the status of server certificates as specified in Section =
4.4.2.1 of [RFC8446]. When an EAP-TLS peer uses OCSP to verify the =
certificate status of the EAP-TLS server, it MUST use Certificate Status =
Requests for the server's certificate chain and it MUST treat a =
CertificateEntry (except the trust anchor) without a valid =
CertificateStatus extension as invalid and abort the handshake with an =
appropriate alert.=E2=80=9C<div class=3D""><br class=3D""></div><div =
class=3D"">Thanks,</div><div class=3D""><br class=3D""></div><div =
class=3D"">Joe</div><div class=3D""><div class=3D""><br =
class=3D""></div>[1] <a =
href=3D"https://mailarchive.ietf.org/arch/msg/emu/0DnfUWPqvKX0_Wo8s-Zyperg=
MHI/" =
class=3D"">https://mailarchive.ietf.org/arch/msg/emu/0DnfUWPqvKX0_Wo8s-Zyp=
ergMHI/</a><br class=3D"">[2] <a =
href=3D"https://tools.ietf.org/html/draft-ietf-emu-eap-tls13-11#section-5.=
4" =
class=3D"">https://tools.ietf.org/html/draft-ietf-emu-eap-tls13-11#section=
-5.4</a></div></div>
_______________________________________________<br class=3D"">Emu =
mailing list<br class=3D""><a href=3D"mailto:Emu@ietf.org" =
class=3D"">Emu@ietf.org</a><br class=3D""><a =
href=3D"https://www.ietf.org/mailman/listinfo/emu" =
class=3D"">https://www.ietf.org/mailman/listinfo/emu</a><br =
class=3D""></div></blockquote></div><br =
class=3D""></div></div></body></html>=

--Apple-Mail=_EE0C34E8-8633-46F5-88E4-6E299D2A7D08--


From nobody Thu Oct 29 10:30:43 2020
Return-Path: <madwolf@openca.org>
X-Original-To: emu@ietfa.amsl.com
Delivered-To: emu@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id B866D3A0B77 for <emu@ietfa.amsl.com>; Thu, 29 Oct 2020 10:30:41 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.897
X-Spam-Level: 
X-Spam-Status: No, score=-1.897 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, HTML_MESSAGE=0.001, MIME_QP_LONG_LINE=0.001, SPF_HELO_NONE=0.001, SPF_PASS=-0.001, URIBL_BLOCKED=0.001] autolearn=unavailable autolearn_force=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 u1kwqQhNEILu for <emu@ietfa.amsl.com>; Thu, 29 Oct 2020 10:30:40 -0700 (PDT)
Received: from mail.katezarealty.com (mail.katezarealty.com [104.168.158.213]) by ietfa.amsl.com (Postfix) with ESMTP id E8F4B3A0B75 for <emu@ietf.org>; Thu, 29 Oct 2020 10:30:39 -0700 (PDT)
Received: from localhost (unknown [127.0.0.1]) by mail.katezarealty.com (Postfix) with ESMTP id A74AD37413DF; Thu, 29 Oct 2020 17:30:39 +0000 (UTC)
X-Virus-Scanned: amavisd-new at katezarealty.com
Received: from mail.katezarealty.com ([127.0.0.1]) by localhost (mail.katezarealty.com [127.0.0.1]) (amavisd-new, port 10024) with LMTP id TCcaFZYsTt6J; Thu, 29 Oct 2020 13:30:38 -0400 (EDT)
Received: from [192.168.1.180] (c-76-25-82-103.hsd1.co.comcast.net [76.25.82.103]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by mail.katezarealty.com (Postfix) with ESMTPSA id 5DFFF3740957; Thu, 29 Oct 2020 13:30:38 -0400 (EDT)
User-Agent: Microsoft-MacOutlook/16.42.20101102
Date: Thu, 29 Oct 2020 11:30:36 -0600
From: Max Pala <madwolf@openca.org>
To: Eliot Lear <lear=40cisco.com@dmarc.ietf.org>, Joseph Salowey <joe@salowey.net>
CC: EMU WG <emu@ietf.org>
Message-ID: <6B43F397-A15F-46E9-95AD-EE0FBB5DDBD7@cablelabs.com>
Thread-Topic: [Emu] Consensus Call on OCSP usage in draft-ietf-emu-eap-tls13-11
References: <CAOgPGoDbsunLOxrnFxa8uMxG6JYObX_r5VLOvVib5QmFHGOrwA@mail.gmail.com> <5D2BBCBB-62B9-41F5-86C3-A9CFD17AB38C@cisco.com>
In-Reply-To: <5D2BBCBB-62B9-41F5-86C3-A9CFD17AB38C@cisco.com>
Mime-version: 1.0
Content-type: multipart/alternative; boundary="B_3686815838_1396932525"
Archived-At: <https://mailarchive.ietf.org/arch/msg/emu/kLgax1C-6IBKsKJsmgWCSyLai2c>
Subject: Re: [Emu] Consensus Call on OCSP usage in draft-ietf-emu-eap-tls13-11
X-BeenThere: emu@ietf.org
X-Mailman-Version: 2.1.29
Precedence: list
List-Id: "EAP Methods Update \(EMU\)" <emu.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/emu>, <mailto:emu-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/emu/>
List-Post: <mailto:emu@ietf.org>
List-Help: <mailto:emu-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/emu>, <mailto:emu-request@ietf.org?subject=subscribe>
X-List-Received-Date: Thu, 29 Oct 2020 17:30:42 -0000

> This message is in MIME format. Since your mail reader does not understand
this format, some or all of this message may not be legible.

--B_3686815838_1396932525
Content-type: text/plain;
	charset="UTF-8"
Content-transfer-encoding: quoted-printable

Hi Eliot, all,

=20

In our industry we solved this issue by requiring OCSP stapling if and only=
 if the certificate being validated carries the OCSP URI in the certificate.=
=20

=20

This allows us to live in a mixed environment where support for OCSP might =
have been introduced later on and allows the CA to explicitly support OCSP f=
or the certificate by including the URL in it.

=20

If the =E2=80=9Cecosystem=E2=80=9D policy allows it =E2=80=93 you might suggest that if OCSP =
responses are not not provided but the URL where to get OCSP responses is kn=
own to the device (or it is in the certificate), the device/entity can conti=
nue with the authentication but it should not enable any device/entity funct=
ionality before successfully executing (and validating) the OCSP protocol fi=
rst (and disconnect if not reachable/invalid/revoked).

=20

Just my 2 cents.

=20

Cheers,
Max

=20

From: Emu <emu-bounces@ietf.org> on behalf of Eliot Lear <lear=3D40cisco.com@=
dmarc.ietf.org>
Date: Thursday, October 29, 2020 at 10:53 AM
To: Joseph Salowey <joe@salowey.net>
Cc: EMU WG <emu@ietf.org>
Subject: Re: [Emu] Consensus Call on OCSP usage in draft-ietf-emu-eap-tls13=
-11

=20

Hi Joe,

=20

My suggestion is that we add some discussion about what to do in the case o=
f no connectivity to the CA.  This will be a not-uncommon occurrence, IMHO, =
in industrial use cases.

=20

Eliot



On 29 Oct 2020, at 17:23, Joseph Salowey <joe@salowey.net> wrote:

=20

An issue was raised in a review of  draft-ietf-emu-eap-tls13-11 on the mand=
atory requirement for OCSP stapling [1].  The document makes the use of OCSP=
 mandatory in section 5.4 [2]. Several folks have pointed out that this may =
not be feasible in all deployments.  This is a quick consensus call for this=
 issue.   Please indicate which option below you support and why.  Please re=
spond by November 5, 2020.=20

1. Keep the text as is with OCSP mandatory for all implementations

2. Require Servers to Implement and Recommended to Use OCSP with text simil=
ar to the following:

=E2=80=9CEAP-TLS servers supporting TLS 1.3 MUST implement Certificate Status Req=
uests (OCSP stapling) as specified in Section 4.4.2.1 of [RFC8446].  It is R=
ECOMMENDED that EAP-TLS peers and servers use OCSP stapling for verifying th=
e status of server certificates as specified in Section 4.4.2.1 of [RFC8446]=
. When an EAP-TLS peer uses OCSP to verify the certificate status of the EAP=
-TLS server, it MUST use Certificate Status Requests for the server's certif=
icate chain and it MUST treat a CertificateEntry (except the trust anchor) w=
ithout a valid CertificateStatus extension as invalid and abort the handshak=
e with an appropriate alert.=E2=80=9C

=20

Thanks,

=20

Joe

=20

[1] https://mailarchive.ietf.org/arch/msg/emu/0DnfUWPqvKX0_Wo8s-ZypergMHI/
[2] https://tools.ietf.org/html/draft-ietf-emu-eap-tls13-11#section-5.4

_______________________________________________
Emu mailing list
Emu@ietf.org
https://www.ietf.org/mailman/listinfo/emu

=20

_______________________________________________ Emu mailing list Emu@ietf.o=
rg https://www.ietf.org/mailman/listinfo/emu=20


--B_3686815838_1396932525
Content-type: text/html;
	charset="UTF-8"
Content-transfer-encoding: quoted-printable

<html xmlns:v=3D"urn:schemas-microsoft-com:vml" xmlns:o=3D"urn:schemas-microsof=
t-com:office:office" xmlns:w=3D"urn:schemas-microsoft-com:office:word" xmlns:m=
=3D"http://schemas.microsoft.com/office/2004/12/omml" xmlns=3D"http://www.w3.org=
/TR/REC-html40"><head><meta http-equiv=3DContent-Type content=3D"text/html; char=
set=3Dutf-8"><meta name=3DGenerator content=3D"Microsoft Word 15 (filtered medium)=
"><style><!--
/* Font Definitions */
@font-face
	{font-family:"Cambria Math";
	panose-1:2 4 5 3 5 4 6 3 2 4;}
@font-face
	{font-family:Calibri;
	panose-1:2 15 5 2 2 2 4 3 2 4;}
/* Style Definitions */
p.MsoNormal, li.MsoNormal, div.MsoNormal
	{margin:0in;
	font-size:11.0pt;
	font-family:"Calibri",sans-serif;}
a:link, span.MsoHyperlink
	{mso-style-priority:99;
	color:blue;
	text-decoration:underline;}
span.EmailStyle18
	{mso-style-type:personal-reply;
	font-family:"Calibri",sans-serif;
	color:windowtext;}
.MsoChpDefault
	{mso-style-type:export-only;
	font-size:10.0pt;}
@page WordSection1
	{size:8.5in 11.0in;
	margin:1.0in 1.0in 1.0in 1.0in;}
div.WordSection1
	{page:WordSection1;}
--></style></head><body lang=3DEN-US link=3Dblue vlink=3Dpurple style=3D'word-wrap:=
break-word'><div class=3DWordSection1><p class=3DMsoNormal>Hi Eliot, all,<o:p></=
o:p></p><p class=3DMsoNormal><o:p>&nbsp;</o:p></p><p class=3DMsoNormal>In our in=
dustry we solved this issue by <b><i>requiring OCSP stapling if and only if =
the certificate being validated carries the OCSP URI in the certificate</i><=
/b>. <o:p></o:p></p><p class=3DMsoNormal><o:p>&nbsp;</o:p></p><p class=3DMsoNorm=
al>This allows us to live in a mixed environment where support for OCSP migh=
t have been introduced later on and allows the CA to explicitly support OCSP=
 for the certificate by including the URL in it.<o:p></o:p></p><p class=3DMsoN=
ormal><o:p>&nbsp;</o:p></p><p class=3DMsoNormal>If the =E2=80=9Cecosystem=E2=80=9D policy =
allows it =E2=80=93 you might suggest that if OCSP responses are not not provided =
but the URL where to get OCSP responses is known to the device (or it is in =
the certificate), the device/entity can continue with the authentication but=
 it should not enable any device/entity functionality before successfully ex=
ecuting (and validating) the OCSP protocol first (and disconnect if not reac=
hable/invalid/revoked).<o:p></o:p></p><p class=3DMsoNormal><o:p>&nbsp;</o:p></=
p><p class=3DMsoNormal>Just my 2 cents.<o:p></o:p></p><p class=3DMsoNormal><o:p>=
&nbsp;</o:p></p><p class=3DMsoNormal>Cheers,<br>Max<o:p></o:p></p><p class=3DMso=
Normal><o:p>&nbsp;</o:p></p><div style=3D'border:none;border-top:solid #B5C4DF=
 1.0pt;padding:3.0pt 0in 0in 0in'><p class=3DMsoNormal style=3D'margin-left:.5in=
'><b><span style=3D'font-size:12.0pt;color:black'>From: </span></b><span style=
=3D'font-size:12.0pt;color:black'>Emu &lt;emu-bounces@ietf.org&gt; on behalf o=
f Eliot Lear &lt;lear=3D40cisco.com@dmarc.ietf.org&gt;<br><b>Date: </b>Thursda=
y, October 29, 2020 at 10:53 AM<br><b>To: </b>Joseph Salowey &lt;joe@salowey=
.net&gt;<br><b>Cc: </b>EMU WG &lt;emu@ietf.org&gt;<br><b>Subject: </b>Re: [E=
mu] Consensus Call on OCSP usage in draft-ietf-emu-eap-tls13-11<o:p></o:p></=
span></p></div><div><p class=3DMsoNormal style=3D'margin-left:.5in'><o:p>&nbsp;<=
/o:p></p></div><div><p class=3DMsoNormal style=3D'margin-left:.5in'>Hi Joe,<o:p>=
</o:p></p><div><p class=3DMsoNormal style=3D'margin-left:.5in'><o:p>&nbsp;</o:p>=
</p></div><div><p class=3DMsoNormal style=3D'margin-left:.5in'>My suggestion is =
that we add some discussion about what to do in the case of no connectivity =
to the CA. &nbsp;This will be a not-uncommon occurrence, IMHO, in industrial=
 use cases.<o:p></o:p></p></div><div><p class=3DMsoNormal style=3D'margin-left:.=
5in'><o:p>&nbsp;</o:p></p></div><div><p class=3DMsoNormal style=3D'margin-left:.=
5in'>Eliot<o:p></o:p></p></div><div><div><p class=3DMsoNormal style=3D'margin-le=
ft:.5in'><br><br><o:p></o:p></p><blockquote style=3D'margin-top:5.0pt;margin-b=
ottom:5.0pt'><div><p class=3DMsoNormal style=3D'margin-left:.5in'>On 29 Oct 2020=
, at 17:23, Joseph Salowey &lt;<a href=3D"mailto:joe@salowey.net">joe@salowey.=
net</a>&gt; wrote:<o:p></o:p></p></div><p class=3DMsoNormal style=3D'margin-left=
:.5in'><o:p>&nbsp;</o:p></p><div><div><p class=3DMsoNormal style=3D'margin-left:=
.5in'>An issue was raised in a review of &nbsp;draft-ietf-emu-eap-tls13-11 o=
n the mandatory requirement for OCSP stapling [1].&nbsp; The document makes =
the use of OCSP mandatory in section 5.4 [2]. Several folks have pointed out=
 that this may not be feasible in all deployments.&nbsp; This is a quick con=
sensus call for this issue. &nbsp; Please indicate which option below you su=
pport and why.&nbsp; Please respond&nbsp;by November 5, 2020.&nbsp;<br><br>1=
. Keep the text as is with OCSP mandatory for all implementations<br><br>2. =
Require Servers to Implement and Recommended to Use OCSP with text similar t=
o the following:<br><br>=E2=80=9CEAP-TLS servers supporting TLS 1.3 MUST implement=
 Certificate Status Requests (OCSP stapling) as specified in Section 4.4.2.1=
 of [RFC8446].&nbsp; It is RECOMMENDED that EAP-TLS peers and servers use OC=
SP stapling for verifying the status of server certificates as specified in =
Section 4.4.2.1 of [RFC8446]. When an EAP-TLS peer uses OCSP to verify the c=
ertificate status of the EAP-TLS server, it MUST use Certificate Status Requ=
ests for the server's certificate chain and it MUST treat a CertificateEntry=
 (except the trust anchor) without a valid CertificateStatus extension as in=
valid and abort the handshake with an appropriate alert.=E2=80=9C<o:p></o:p></p><d=
iv><p class=3DMsoNormal style=3D'margin-left:.5in'><o:p>&nbsp;</o:p></p></div><d=
iv><p class=3DMsoNormal style=3D'margin-left:.5in'>Thanks,<o:p></o:p></p></div><=
div><p class=3DMsoNormal style=3D'margin-left:.5in'><o:p>&nbsp;</o:p></p></div><=
div><p class=3DMsoNormal style=3D'margin-left:.5in'>Joe<o:p></o:p></p></div><div=
><div><p class=3DMsoNormal style=3D'margin-left:.5in'><o:p>&nbsp;</o:p></p></div=
><p class=3DMsoNormal style=3D'margin-left:.5in'>[1] <a href=3D"https://mailarchiv=
e.ietf.org/arch/msg/emu/0DnfUWPqvKX0_Wo8s-ZypergMHI/">https://mailarchive.ie=
tf.org/arch/msg/emu/0DnfUWPqvKX0_Wo8s-ZypergMHI/</a><br>[2] <a href=3D"https:/=
/tools.ietf.org/html/draft-ietf-emu-eap-tls13-11#section-5.4">https://tools.=
ietf.org/html/draft-ietf-emu-eap-tls13-11#section-5.4</a><o:p></o:p></p></di=
v></div><p class=3DMsoNormal style=3D'margin-left:.5in'>________________________=
_______________________<br>Emu mailing list<br><a href=3D"mailto:Emu@ietf.org"=
>Emu@ietf.org</a><br><a href=3D"https://www.ietf.org/mailman/listinfo/emu">htt=
ps://www.ietf.org/mailman/listinfo/emu</a><o:p></o:p></p></div></blockquote>=
</div><p class=3DMsoNormal style=3D'margin-left:.5in'><o:p>&nbsp;</o:p></p></div=
></div><p class=3DMsoNormal style=3D'margin-left:.5in'>_________________________=
______________________ Emu mailing list Emu@ietf.org https://www.ietf.org/ma=
ilman/listinfo/emu <o:p></o:p></p></div></body></html>

--B_3686815838_1396932525--



From nobody Thu Oct 29 10:37:15 2020
Return-Path: <lear@cisco.com>
X-Original-To: emu@ietfa.amsl.com
Delivered-To: emu@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 31BCE3A07D7 for <emu@ietfa.amsl.com>; Thu, 29 Oct 2020 10:37:13 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -9.6
X-Spam-Level: 
X-Spam-Status: No, score=-9.6 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIMWL_WL_MED=-0.001, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, DKIM_VALID_EF=-0.1, HTML_MESSAGE=0.001, SPF_PASS=-0.001, URIBL_BLOCKED=0.001, USER_IN_DEF_DKIM_WL=-7.5] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (1024-bit key) header.d=cisco.com
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 G4z8ytus8qsc for <emu@ietfa.amsl.com>; Thu, 29 Oct 2020 10:37:11 -0700 (PDT)
Received: from aer-iport-2.cisco.com (aer-iport-2.cisco.com [173.38.203.52]) (using TLSv1.2 with cipher DHE-RSA-SEED-SHA (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 126BD3A0B9F for <emu@ietf.org>; Thu, 29 Oct 2020 10:37:06 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=cisco.com; i=@cisco.com; l=17713; q=dns/txt; s=iport; t=1603993027; x=1605202627; h=from:message-id:mime-version:subject:date:in-reply-to:cc: to:references; bh=CmPLTC7CkCM4azcmttk3ZyTDXNxQKL85mKqd2volmoY=; b=L5M86xaKRB+NTVOdfInZcX83BZdPsm4FFucBdmA3JVlbFqshza5V+OI8 o2fa/KHtViCaweB2CjP5w3Nzd/W/N30Aqu7Uyow/kIlU+3zy4vJPwHdr3 HggUii66+Z3B38LEeCVv1jHufFWCKTnUj31KfaZxT8JGeHaO442kOzZEC 8=;
X-IronPort-Anti-Spam-Filtered: true
X-IronPort-Anti-Spam-Result: =?us-ascii?q?A0DYAgDK/Jpf/xbLJq1iHAEBAQEBAQc?= =?us-ascii?q?BARIBAQQEAQGCD4EjUgaBH1UBMi2EPYkFiBCUDIgZCwEBAQ0BARgBCgwEAQG?= =?us-ascii?q?ESgKCCCY4EwIDAQELAQEFAQEBAgEGBHGFYQyFcgEBAQECAQEBGwZEBwsFCws?= =?us-ascii?q?OAwMBAgEnAwICJx8JCAYTCYMdAYJcIA+uWnaBMoQ+AYEYhROBOI1VggCBESc?= =?us-ascii?q?cgh8uPoIEWAEBAgGBRDgWgmEzgiwEpn2RHIJ2gxmFb5F6Ax+DF4oQlD6SOwy?= =?us-ascii?q?LdJFmg2ACBAYFAhWBayOBVzMaCBsVOyoBggoBATIJNRIZDY9EAQiHV4VFQAM?= =?us-ascii?q?wAjYCBgEJAQEDCYwCAiYCBYE4XwEB?=
X-IronPort-AV: E=Sophos; i="5.77,430,1596499200"; d="scan'208,217"; a="30735708"
Received: from aer-iport-nat.cisco.com (HELO aer-core-4.cisco.com) ([173.38.203.22]) by aer-iport-2.cisco.com with ESMTP/TLS/DHE-RSA-SEED-SHA; 29 Oct 2020 17:37:02 +0000
Received: from ams3-vpn-dhcp86.cisco.com (ams3-vpn-dhcp86.cisco.com [10.61.64.86]) by aer-core-4.cisco.com (8.15.2/8.15.2) with ESMTPS id 09THb2jY018632 (version=TLSv1.2 cipher=DHE-RSA-AES256-GCM-SHA384 bits=256 verify=NO); Thu, 29 Oct 2020 17:37:02 GMT
From: Eliot Lear <lear@cisco.com>
Message-Id: <B18C7AC4-51AD-4C89-90D0-1EC16271BA1F@cisco.com>
Content-Type: multipart/alternative; boundary="Apple-Mail=_E1B46995-45D2-4413-9736-6C8C3B91054D"
Mime-Version: 1.0 (Mac OS X Mail 13.4 \(3608.120.23.2.4\))
Date: Thu, 29 Oct 2020 18:37:01 +0100
In-Reply-To: <6B43F397-A15F-46E9-95AD-EE0FBB5DDBD7@cablelabs.com>
Cc: Joseph Salowey <joe@salowey.net>, EMU WG <emu@ietf.org>
To: Max Pala <madwolf@openca.org>
References: <CAOgPGoDbsunLOxrnFxa8uMxG6JYObX_r5VLOvVib5QmFHGOrwA@mail.gmail.com> <5D2BBCBB-62B9-41F5-86C3-A9CFD17AB38C@cisco.com> <6B43F397-A15F-46E9-95AD-EE0FBB5DDBD7@cablelabs.com>
X-Mailer: Apple Mail (2.3608.120.23.2.4)
X-Outbound-SMTP-Client: 10.61.64.86, ams3-vpn-dhcp86.cisco.com
X-Outbound-Node: aer-core-4.cisco.com
Archived-At: <https://mailarchive.ietf.org/arch/msg/emu/3O_pw8zWH_btFe2bKgoj9jS5WYM>
Subject: Re: [Emu] Consensus Call on OCSP usage in draft-ietf-emu-eap-tls13-11
X-BeenThere: emu@ietf.org
X-Mailman-Version: 2.1.29
Precedence: list
List-Id: "EAP Methods Update \(EMU\)" <emu.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/emu>, <mailto:emu-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/emu/>
List-Post: <mailto:emu@ietf.org>
List-Help: <mailto:emu-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/emu>, <mailto:emu-request@ietf.org?subject=subscribe>
X-List-Received-Date: Thu, 29 Oct 2020 17:37:13 -0000

--Apple-Mail=_E1B46995-45D2-4413-9736-6C8C3B91054D
Content-Transfer-Encoding: quoted-printable
Content-Type: text/plain;
	charset=utf-8

Hi Max

> On 29 Oct 2020, at 18:30, Max Pala <madwolf@openca.org =
<mailto:madwolf@openca.org>> wrote:
>=20
> Hi Eliot, all,
> =20
> In our industry we solved this issue by requiring OCSP stapling if and =
only if the certificate being validated carries the OCSP URI in the =
certificate.=20

Perfectly reasonable.

> =20
> This allows us to live in a mixed environment where support for OCSP =
might have been introduced later on and allows the CA to explicitly =
support OCSP for the certificate by including the URL in it.

Yep.

> =20
> If the =E2=80=9Cecosystem=E2=80=9D policy allows it =E2=80=93 you =
might suggest that if OCSP responses are not not provided but the URL =
where to get OCSP responses is known to the device (or it is in the =
certificate), the device/entity can continue with the authentication but =
it should not enable any device/entity functionality before successfully =
executing (and validating) the OCSP protocol first (and disconnect if =
not reachable/invalid/revoked).
> =20
> Just my 2 cents.
> =20

Worth more.

Eliot

> Cheers,
> Max
> =20
> From: Emu <emu-bounces@ietf.org <mailto:emu-bounces@ietf.org>> on =
behalf of Eliot Lear <lear=3D40cisco.com@dmarc.ietf.org =
<mailto:lear=3D40cisco.com@dmarc.ietf.org>>
> Date: Thursday, October 29, 2020 at 10:53 AM
> To: Joseph Salowey <joe@salowey.net <mailto:joe@salowey.net>>
> Cc: EMU WG <emu@ietf.org <mailto:emu@ietf.org>>
> Subject: Re: [Emu] Consensus Call on OCSP usage in =
draft-ietf-emu-eap-tls13-11
> =20
> Hi Joe,
> =20
> My suggestion is that we add some discussion about what to do in the =
case of no connectivity to the CA.  This will be a not-uncommon =
occurrence, IMHO, in industrial use cases.
> =20
> Eliot
>=20
>=20
>> On 29 Oct 2020, at 17:23, Joseph Salowey <joe@salowey.net =
<mailto:joe@salowey.net>> wrote:
>> =20
>> An issue was raised in a review of  draft-ietf-emu-eap-tls13-11 on =
the mandatory requirement for OCSP stapling [1].  The document makes the =
use of OCSP mandatory in section 5.4 [2]. Several folks have pointed out =
that this may not be feasible in all deployments.  This is a quick =
consensus call for this issue.   Please indicate which option below you =
support and why.  Please respond by November 5, 2020.=20
>>=20
>> 1. Keep the text as is with OCSP mandatory for all implementations
>>=20
>> 2. Require Servers to Implement and Recommended to Use OCSP with text =
similar to the following:
>>=20
>> =E2=80=9CEAP-TLS servers supporting TLS 1.3 MUST implement =
Certificate Status Requests (OCSP stapling) as specified in Section =
4.4.2.1 of [RFC8446].  It is RECOMMENDED that EAP-TLS peers and servers =
use OCSP stapling for verifying the status of server certificates as =
specified in Section 4.4.2.1 of [RFC8446]. When an EAP-TLS peer uses =
OCSP to verify the certificate status of the EAP-TLS server, it MUST use =
Certificate Status Requests for the server's certificate chain and it =
MUST treat a CertificateEntry (except the trust anchor) without a valid =
CertificateStatus extension as invalid and abort the handshake with an =
appropriate alert.=E2=80=9C
>> =20
>> Thanks,
>> =20
>> Joe
>> =20
>> [1] =
https://mailarchive.ietf.org/arch/msg/emu/0DnfUWPqvKX0_Wo8s-ZypergMHI/ =
<https://mailarchive.ietf.org/arch/msg/emu/0DnfUWPqvKX0_Wo8s-ZypergMHI/>
>> [2] =
https://tools.ietf.org/html/draft-ietf-emu-eap-tls13-11#section-5.4 =
<https://tools.ietf.org/html/draft-ietf-emu-eap-tls13-11#section-5.4>
>> _______________________________________________
>> Emu mailing list
>> Emu@ietf.org <mailto:Emu@ietf.org>
>> https://www.ietf.org/mailman/listinfo/emu =
<https://www.ietf.org/mailman/listinfo/emu>
> =20
> _______________________________________________ Emu mailing list =
Emu@ietf.org =
<mailto:Emu@ietf.org>https://www.ietf.org/mailman/listinfo/emu =
<https://www.ietf.org/mailman/listinfo/emu>

--Apple-Mail=_E1B46995-45D2-4413-9736-6C8C3B91054D
Content-Transfer-Encoding: quoted-printable
Content-Type: text/html;
	charset=utf-8

<html><head><meta http-equiv=3D"Content-Type" content=3D"text/html; =
charset=3Dutf-8"></head><body style=3D"word-wrap: break-word; =
-webkit-nbsp-mode: space; line-break: after-white-space;" class=3D""><meta=
 http-equiv=3D"Content-Type" content=3D"text/html; charset=3Dutf-8" =
class=3D""><div style=3D"word-wrap: break-word; -webkit-nbsp-mode: =
space; line-break: after-white-space;" class=3D"">Hi Max<br =
class=3D""><div class=3D""><br class=3D""><blockquote type=3D"cite" =
class=3D""><div class=3D"">On 29 Oct 2020, at 18:30, Max Pala &lt;<a =
href=3D"mailto:madwolf@openca.org" class=3D"">madwolf@openca.org</a>&gt; =
wrote:</div><br class=3D"Apple-interchange-newline"><div class=3D""><div =
class=3D"WordSection1" style=3D"page: WordSection1; caret-color: rgb(0, =
0, 0); font-family: Helvetica; font-size: 16px; font-style: normal; =
font-variant-caps: normal; font-weight: normal; letter-spacing: normal; =
text-align: start; text-indent: 0px; text-transform: none; white-space: =
normal; word-spacing: 0px; -webkit-text-stroke-width: 0px; =
text-decoration: none;"><div style=3D"margin: 0in; font-size: 11pt; =
font-family: Calibri, sans-serif;" class=3D"">Hi Eliot, all,<o:p =
class=3D""></o:p></div><div style=3D"margin: 0in; font-size: 11pt; =
font-family: Calibri, sans-serif;" class=3D""><o:p =
class=3D"">&nbsp;</o:p></div><div style=3D"margin: 0in; font-size: 11pt; =
font-family: Calibri, sans-serif;" class=3D"">In our industry we solved =
this issue by<span class=3D"Apple-converted-space">&nbsp;</span><b =
class=3D""><i class=3D"">requiring OCSP stapling if and only if the =
certificate being validated carries the OCSP URI in the =
certificate</i></b>.<span =
class=3D"Apple-converted-space">&nbsp;</span></div></div></div></blockquot=
e><div class=3D""><br class=3D""></div><div class=3D"">Perfectly =
reasonable.</div><div class=3D""><br class=3D""></div><blockquote =
type=3D"cite" class=3D""><div class=3D""><div class=3D"WordSection1" =
style=3D"page: WordSection1; caret-color: rgb(0, 0, 0); font-family: =
Helvetica; font-size: 16px; font-style: normal; font-variant-caps: =
normal; font-weight: normal; letter-spacing: normal; text-align: start; =
text-indent: 0px; text-transform: none; white-space: normal; =
word-spacing: 0px; -webkit-text-stroke-width: 0px; text-decoration: =
none;"><div style=3D"margin: 0in; font-size: 11pt; font-family: Calibri, =
sans-serif;" class=3D""><o:p class=3D""></o:p></div><div style=3D"margin: =
0in; font-size: 11pt; font-family: Calibri, sans-serif;" class=3D""><o:p =
class=3D"">&nbsp;</o:p></div><div style=3D"margin: 0in; font-size: 11pt; =
font-family: Calibri, sans-serif;" class=3D"">This allows us to live in =
a mixed environment where support for OCSP might have been introduced =
later on and allows the CA to explicitly support OCSP for the =
certificate by including the URL in =
it.</div></div></div></blockquote><div class=3D""><br =
class=3D""></div>Yep.</div><div class=3D""><br class=3D""><blockquote =
type=3D"cite" class=3D""><div class=3D""><div class=3D"WordSection1" =
style=3D"page: WordSection1; caret-color: rgb(0, 0, 0); font-family: =
Helvetica; font-size: 16px; font-style: normal; font-variant-caps: =
normal; font-weight: normal; letter-spacing: normal; text-align: start; =
text-indent: 0px; text-transform: none; white-space: normal; =
word-spacing: 0px; -webkit-text-stroke-width: 0px; text-decoration: =
none;"><div style=3D"margin: 0in; font-size: 11pt; font-family: Calibri, =
sans-serif;" class=3D""><o:p class=3D""></o:p></div><div style=3D"margin: =
0in; font-size: 11pt; font-family: Calibri, sans-serif;" class=3D""><o:p =
class=3D"">&nbsp;</o:p></div><div style=3D"margin: 0in; font-size: 11pt; =
font-family: Calibri, sans-serif;" class=3D"">If the =E2=80=9Cecosystem=E2=
=80=9D policy allows it =E2=80=93 you might suggest that if OCSP =
responses are not not provided but the URL where to get OCSP responses =
is known to the device (or it is in the certificate), the device/entity =
can continue with the authentication but it should not enable any =
device/entity functionality before successfully executing (and =
validating) the OCSP protocol first (and disconnect if not =
reachable/invalid/revoked).<o:p class=3D""></o:p></div><div =
style=3D"margin: 0in; font-size: 11pt; font-family: Calibri, =
sans-serif;" class=3D""><o:p class=3D"">&nbsp;</o:p></div><div =
style=3D"margin: 0in; font-size: 11pt; font-family: Calibri, =
sans-serif;" class=3D"">Just my 2 cents.<o:p class=3D""></o:p></div><div =
style=3D"margin: 0in; font-size: 11pt; font-family: Calibri, =
sans-serif;" class=3D""><o:p =
class=3D"">&nbsp;</o:p></div></div></div></blockquote><div class=3D""><br =
class=3D""></div>Worth more.</div><div class=3D""><br =
class=3D""></div><div class=3D"">Eliot</div><div class=3D""><br =
class=3D""><blockquote type=3D"cite" class=3D""><div class=3D""><div =
class=3D"WordSection1" style=3D"page: WordSection1; caret-color: rgb(0, =
0, 0); font-family: Helvetica; font-size: 16px; font-style: normal; =
font-variant-caps: normal; font-weight: normal; letter-spacing: normal; =
text-align: start; text-indent: 0px; text-transform: none; white-space: =
normal; word-spacing: 0px; -webkit-text-stroke-width: 0px; =
text-decoration: none;"><div style=3D"margin: 0in; font-size: 11pt; =
font-family: Calibri, sans-serif;" class=3D"">Cheers,<br =
class=3D"">Max<o:p class=3D""></o:p></div><div style=3D"margin: 0in; =
font-size: 11pt; font-family: Calibri, sans-serif;" class=3D""><o:p =
class=3D"">&nbsp;</o:p></div><div style=3D"border-style: solid none =
none; border-top-width: 1pt; border-top-color: rgb(181, 196, 223); =
padding: 3pt 0in 0in;" class=3D""><div style=3D"margin: 0in 0in 0in =
0.5in; font-size: 11pt; font-family: Calibri, sans-serif;" class=3D""><b =
class=3D""><span style=3D"font-size: 12pt;" class=3D"">From:<span =
class=3D"Apple-converted-space">&nbsp;</span></span></b><span =
style=3D"font-size: 12pt;" class=3D"">Emu &lt;<a =
href=3D"mailto:emu-bounces@ietf.org" =
class=3D"">emu-bounces@ietf.org</a>&gt; on behalf of Eliot Lear &lt;<a =
href=3D"mailto:lear=3D40cisco.com@dmarc.ietf.org" =
class=3D"">lear=3D40cisco.com@dmarc.ietf.org</a>&gt;<br class=3D""><b =
class=3D"">Date:<span =
class=3D"Apple-converted-space">&nbsp;</span></b>Thursday, October 29, =
2020 at 10:53 AM<br class=3D""><b class=3D"">To:<span =
class=3D"Apple-converted-space">&nbsp;</span></b>Joseph Salowey &lt;<a =
href=3D"mailto:joe@salowey.net" class=3D"">joe@salowey.net</a>&gt;<br =
class=3D""><b class=3D"">Cc:<span =
class=3D"Apple-converted-space">&nbsp;</span></b>EMU WG &lt;<a =
href=3D"mailto:emu@ietf.org" class=3D"">emu@ietf.org</a>&gt;<br =
class=3D""><b class=3D"">Subject:<span =
class=3D"Apple-converted-space">&nbsp;</span></b>Re: [Emu] Consensus =
Call on OCSP usage in draft-ietf-emu-eap-tls13-11<o:p =
class=3D""></o:p></span></div></div><div class=3D""><div style=3D"margin: =
0in 0in 0in 0.5in; font-size: 11pt; font-family: Calibri, sans-serif;" =
class=3D""><o:p class=3D"">&nbsp;</o:p></div></div><div class=3D""><div =
style=3D"margin: 0in 0in 0in 0.5in; font-size: 11pt; font-family: =
Calibri, sans-serif;" class=3D"">Hi Joe,<o:p class=3D""></o:p></div><div =
class=3D""><div style=3D"margin: 0in 0in 0in 0.5in; font-size: 11pt; =
font-family: Calibri, sans-serif;" class=3D""><o:p =
class=3D"">&nbsp;</o:p></div></div><div class=3D""><div style=3D"margin: =
0in 0in 0in 0.5in; font-size: 11pt; font-family: Calibri, sans-serif;" =
class=3D"">My suggestion is that we add some discussion about what to do =
in the case of no connectivity to the CA. &nbsp;This will be a =
not-uncommon occurrence, IMHO, in industrial use cases.<o:p =
class=3D""></o:p></div></div><div class=3D""><div style=3D"margin: 0in =
0in 0in 0.5in; font-size: 11pt; font-family: Calibri, sans-serif;" =
class=3D""><o:p class=3D"">&nbsp;</o:p></div></div><div class=3D""><div =
style=3D"margin: 0in 0in 0in 0.5in; font-size: 11pt; font-family: =
Calibri, sans-serif;" class=3D"">Eliot<o:p =
class=3D""></o:p></div></div><div class=3D""><div class=3D""><div =
style=3D"margin: 0in 0in 0in 0.5in; font-size: 11pt; font-family: =
Calibri, sans-serif;" class=3D""><br class=3D""><br class=3D""><o:p =
class=3D""></o:p></div><blockquote style=3D"margin-top: 5pt; =
margin-bottom: 5pt;" class=3D"" type=3D"cite"><div class=3D""><div =
style=3D"margin: 0in 0in 0in 0.5in; font-size: 11pt; font-family: =
Calibri, sans-serif;" class=3D"">On 29 Oct 2020, at 17:23, Joseph =
Salowey &lt;<a href=3D"mailto:joe@salowey.net" style=3D"color: blue; =
text-decoration: underline;" class=3D"">joe@salowey.net</a>&gt; =
wrote:<o:p class=3D""></o:p></div></div><div style=3D"margin: 0in 0in =
0in 0.5in; font-size: 11pt; font-family: Calibri, sans-serif;" =
class=3D""><o:p class=3D"">&nbsp;</o:p></div><div class=3D""><div =
class=3D""><div style=3D"margin: 0in 0in 0in 0.5in; font-size: 11pt; =
font-family: Calibri, sans-serif;" class=3D"">An issue was raised in a =
review of &nbsp;draft-ietf-emu-eap-tls13-11 on the mandatory requirement =
for OCSP stapling [1].&nbsp; The document makes the use of OCSP =
mandatory in section 5.4 [2]. Several folks have pointed out that this =
may not be feasible in all deployments.&nbsp; This is a quick consensus =
call for this issue. &nbsp; Please indicate which option below you =
support and why.&nbsp; Please respond&nbsp;by November 5, 2020.&nbsp;<br =
class=3D""><br class=3D"">1. Keep the text as is with OCSP mandatory for =
all implementations<br class=3D""><br class=3D"">2. Require Servers to =
Implement and Recommended to Use OCSP with text similar to the =
following:<br class=3D""><br class=3D"">=E2=80=9CEAP-TLS servers =
supporting TLS 1.3 MUST implement Certificate Status Requests (OCSP =
stapling) as specified in Section 4.4.2.1 of [RFC8446].&nbsp; It is =
RECOMMENDED that EAP-TLS peers and servers use OCSP stapling for =
verifying the status of server certificates as specified in Section =
4.4.2.1 of [RFC8446]. When an EAP-TLS peer uses OCSP to verify the =
certificate status of the EAP-TLS server, it MUST use Certificate Status =
Requests for the server's certificate chain and it MUST treat a =
CertificateEntry (except the trust anchor) without a valid =
CertificateStatus extension as invalid and abort the handshake with an =
appropriate alert.=E2=80=9C<o:p class=3D""></o:p></div><div =
class=3D""><div style=3D"margin: 0in 0in 0in 0.5in; font-size: 11pt; =
font-family: Calibri, sans-serif;" class=3D""><o:p =
class=3D"">&nbsp;</o:p></div></div><div class=3D""><div style=3D"margin: =
0in 0in 0in 0.5in; font-size: 11pt; font-family: Calibri, sans-serif;" =
class=3D"">Thanks,<o:p class=3D""></o:p></div></div><div class=3D""><div =
style=3D"margin: 0in 0in 0in 0.5in; font-size: 11pt; font-family: =
Calibri, sans-serif;" class=3D""><o:p =
class=3D"">&nbsp;</o:p></div></div><div class=3D""><div style=3D"margin: =
0in 0in 0in 0.5in; font-size: 11pt; font-family: Calibri, sans-serif;" =
class=3D"">Joe<o:p class=3D""></o:p></div></div><div class=3D""><div =
class=3D""><div style=3D"margin: 0in 0in 0in 0.5in; font-size: 11pt; =
font-family: Calibri, sans-serif;" class=3D""><o:p =
class=3D"">&nbsp;</o:p></div></div><div style=3D"margin: 0in 0in 0in =
0.5in; font-size: 11pt; font-family: Calibri, sans-serif;" =
class=3D"">[1]<span class=3D"Apple-converted-space">&nbsp;</span><a =
href=3D"https://mailarchive.ietf.org/arch/msg/emu/0DnfUWPqvKX0_Wo8s-Zyperg=
MHI/" style=3D"color: blue; text-decoration: underline;" =
class=3D"">https://mailarchive.ietf.org/arch/msg/emu/0DnfUWPqvKX0_Wo8s-Zyp=
ergMHI/</a><br class=3D"">[2]<span =
class=3D"Apple-converted-space">&nbsp;</span><a =
href=3D"https://tools.ietf.org/html/draft-ietf-emu-eap-tls13-11#section-5.=
4" style=3D"color: blue; text-decoration: underline;" =
class=3D"">https://tools.ietf.org/html/draft-ietf-emu-eap-tls13-11#section=
-5.4</a><o:p class=3D""></o:p></div></div></div><div style=3D"margin: =
0in 0in 0in 0.5in; font-size: 11pt; font-family: Calibri, sans-serif;" =
class=3D"">_______________________________________________<br =
class=3D"">Emu mailing list<br class=3D""><a href=3D"mailto:Emu@ietf.org" =
style=3D"color: blue; text-decoration: underline;" =
class=3D"">Emu@ietf.org</a><br class=3D""><a =
href=3D"https://www.ietf.org/mailman/listinfo/emu" style=3D"color: blue; =
text-decoration: underline;" =
class=3D"">https://www.ietf.org/mailman/listinfo/emu</a><o:p =
class=3D""></o:p></div></div></blockquote></div><div style=3D"margin: =
0in 0in 0in 0.5in; font-size: 11pt; font-family: Calibri, sans-serif;" =
class=3D""><o:p class=3D"">&nbsp;</o:p></div></div></div><div =
style=3D"margin: 0in 0in 0in 0.5in; font-size: 11pt; font-family: =
Calibri, sans-serif;" =
class=3D"">_______________________________________________ Emu mailing =
list<span class=3D"Apple-converted-space">&nbsp;</span><a =
href=3D"mailto:Emu@ietf.org" style=3D"color: blue; text-decoration: =
underline;" class=3D"">Emu@ietf.org</a><a =
href=3D"https://www.ietf.org/mailman/listinfo/emu" style=3D"color: blue; =
text-decoration: underline;" =
class=3D"">https://www.ietf.org/mailman/listinfo/emu</a></div></div></div>=
</blockquote></div><br class=3D""></div></body></html>=

--Apple-Mail=_E1B46995-45D2-4413-9736-6C8C3B91054D--


From nobody Thu Oct 29 11:09:44 2020
Return-Path: <aland@deployingradius.com>
X-Original-To: emu@ietfa.amsl.com
Delivered-To: emu@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id BC0DE3A0948 for <emu@ietfa.amsl.com>; Thu, 29 Oct 2020 11:09:43 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.899
X-Spam-Level: 
X-Spam-Status: No, score=-1.899 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, SPF_HELO_NONE=0.001, SPF_PASS=-0.001, URIBL_BLOCKED=0.001] autolearn=ham autolearn_force=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 zyVF_0373DoN for <emu@ietfa.amsl.com>; Thu, 29 Oct 2020 11:09:39 -0700 (PDT)
Received: from mail.networkradius.com (mail.networkradius.com [62.210.147.122]) (using TLSv1.2 with cipher ADH-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 33F463A0879 for <emu@ietf.org>; Thu, 29 Oct 2020 11:09:38 -0700 (PDT)
Received: from [192.168.46.130] (24-52-251-6.cable.teksavvy.com [24.52.251.6]) by mail.networkradius.com (Postfix) with ESMTPSA id B8D1918F; Thu, 29 Oct 2020 18:09:36 +0000 (UTC)
Authentication-Results: NetworkRADIUS; dmarc=none (p=none dis=none) header.from=deployingradius.com
Content-Type: text/plain; charset=utf-8
Mime-Version: 1.0 (Mac OS X Mail 13.4 \(3608.120.23.2.1\))
From: Alan DeKok <aland@deployingradius.com>
In-Reply-To: <B18C7AC4-51AD-4C89-90D0-1EC16271BA1F@cisco.com>
Date: Thu, 29 Oct 2020 14:09:36 -0400
Cc: Max Pala <madwolf@openca.org>, EMU WG <emu@ietf.org>
Content-Transfer-Encoding: quoted-printable
Message-Id: <C339ADFC-BD51-4012-8C49-3ED17AEB5807@deployingradius.com>
References: <CAOgPGoDbsunLOxrnFxa8uMxG6JYObX_r5VLOvVib5QmFHGOrwA@mail.gmail.com> <5D2BBCBB-62B9-41F5-86C3-A9CFD17AB38C@cisco.com> <6B43F397-A15F-46E9-95AD-EE0FBB5DDBD7@cablelabs.com> <B18C7AC4-51AD-4C89-90D0-1EC16271BA1F@cisco.com>
To: Eliot Lear <lear=40cisco.com@dmarc.ietf.org>
X-Mailer: Apple Mail (2.3608.120.23.2.1)
Archived-At: <https://mailarchive.ietf.org/arch/msg/emu/Tc0Gaz_1DgtrPJUUiDAfAG-MnWM>
Subject: Re: [Emu] Consensus Call on OCSP usage in draft-ietf-emu-eap-tls13-11
X-BeenThere: emu@ietf.org
X-Mailman-Version: 2.1.29
Precedence: list
List-Id: "EAP Methods Update \(EMU\)" <emu.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/emu>, <mailto:emu-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/emu/>
List-Post: <mailto:emu@ietf.org>
List-Help: <mailto:emu-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/emu>, <mailto:emu-request@ietf.org?subject=subscribe>
X-List-Received-Date: Thu, 29 Oct 2020 18:09:44 -0000

  +1

> On Oct 29, 2020, at 1:37 PM, Eliot Lear =
<lear=3D40cisco.com@dmarc.ietf.org> wrote:
>=20
> Hi Max
>=20
>> On 29 Oct 2020, at 18:30, Max Pala <madwolf@openca.org> wrote:
>>=20
>> Hi Eliot, all,
>> =20
>> In our industry we solved this issue by requiring OCSP stapling if =
and only if the certificate being validated carries the OCSP URI in the =
certificate.=20
>=20
> Perfectly reasonable.
>=20
>> =20
>> This allows us to live in a mixed environment where support for OCSP =
might have been introduced later on and allows the CA to explicitly =
support OCSP for the certificate by including the URL in it.
>=20
> Yep.
>=20
>> =20
>> If the =E2=80=9Cecosystem=E2=80=9D policy allows it =E2=80=93 you =
might suggest that if OCSP responses are not not provided but the URL =
where to get OCSP responses is known to the device (or it is in the =
certificate), the device/entity can continue with the authentication but =
it should not enable any device/entity functionality before successfully =
executing (and validating) the OCSP protocol first (and disconnect if =
not reachable/invalid/revoked).
>> =20
>> Just my 2 cents.
>> =20
>=20
> Worth more.
>=20
> Eliot
>=20
>> Cheers,
>> Max
>> =20
>> From: Emu <emu-bounces@ietf.org> on behalf of Eliot Lear =
<lear=3D40cisco.com@dmarc.ietf.org>
>> Date: Thursday, October 29, 2020 at 10:53 AM
>> To: Joseph Salowey <joe@salowey.net>
>> Cc: EMU WG <emu@ietf.org>
>> Subject: Re: [Emu] Consensus Call on OCSP usage in =
draft-ietf-emu-eap-tls13-11
>> =20
>> Hi Joe,
>> =20
>> My suggestion is that we add some discussion about what to do in the =
case of no connectivity to the CA.  This will be a not-uncommon =
occurrence, IMHO, in industrial use cases.
>> =20
>> Eliot
>>=20
>>=20
>>> On 29 Oct 2020, at 17:23, Joseph Salowey <joe@salowey.net> wrote:
>>> =20
>>> An issue was raised in a review of  draft-ietf-emu-eap-tls13-11 on =
the mandatory requirement for OCSP stapling [1].  The document makes the =
use of OCSP mandatory in section 5.4 [2]. Several folks have pointed out =
that this may not be feasible in all deployments.  This is a quick =
consensus call for this issue.   Please indicate which option below you =
support and why.  Please respond by November 5, 2020.=20
>>>=20
>>> 1. Keep the text as is with OCSP mandatory for all implementations
>>>=20
>>> 2. Require Servers to Implement and Recommended to Use OCSP with =
text similar to the following:
>>>=20
>>> =E2=80=9CEAP-TLS servers supporting TLS 1.3 MUST implement =
Certificate Status Requests (OCSP stapling) as specified in Section =
4.4.2.1 of [RFC8446].  It is RECOMMENDED that EAP-TLS peers and servers =
use OCSP stapling for verifying the status of server certificates as =
specified in Section 4.4.2.1 of [RFC8446]. When an EAP-TLS peer uses =
OCSP to verify the certificate status of the EAP-TLS server, it MUST use =
Certificate Status Requests for the server's certificate chain and it =
MUST treat a CertificateEntry (except the trust anchor) without a valid =
CertificateStatus extension as invalid and abort the handshake with an =
appropriate alert.=E2=80=9C
>>> =20
>>> Thanks,
>>> =20
>>> Joe
>>> =20
>>> [1] =
https://mailarchive.ietf.org/arch/msg/emu/0DnfUWPqvKX0_Wo8s-ZypergMHI/
>>> [2] =
https://tools.ietf.org/html/draft-ietf-emu-eap-tls13-11#section-5.4
>>> _______________________________________________
>>> Emu mailing list
>>> Emu@ietf.org
>>> https://www.ietf.org/mailman/listinfo/emu
>> =20
>> _______________________________________________ Emu mailing list =
Emu@ietf.orghttps://www.ietf.org/mailman/listinfo/emu
>=20
> _______________________________________________
> Emu mailing list
> Emu@ietf.org
> https://www.ietf.org/mailman/listinfo/emu


From nobody Thu Oct 29 12:19:29 2020
Return-Path: <Tim.Cappalli@microsoft.com>
X-Original-To: emu@ietfa.amsl.com
Delivered-To: emu@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 209E13A08C5 for <emu@ietfa.amsl.com>; Thu, 29 Oct 2020 12:19:27 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.1
X-Spam-Level: 
X-Spam-Status: No, score=-2.1 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIMWL_WL_HIGH=-0.001, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, DKIM_VALID_EF=-0.1, HTML_MESSAGE=0.001, SPF_PASS=-0.001, URIBL_BLOCKED=0.001] autolearn=unavailable autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (1024-bit key) header.d=microsoft.com
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 iYb_oQGOZCVV for <emu@ietfa.amsl.com>; Thu, 29 Oct 2020 12:19:23 -0700 (PDT)
Received: from NAM06-DM3-obe.outbound.protection.outlook.com (mail-eopbgr640108.outbound.protection.outlook.com [40.107.64.108]) (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 31C043A0A6C for <emu@ietf.org>; Thu, 29 Oct 2020 12:19:23 -0700 (PDT)
ARC-Seal: i=1; a=rsa-sha256; s=arcselector9901; d=microsoft.com; cv=none; b=IoSRjZHshXDIh2e8lAwTv1Gyck3f1y96uewWmOkJT/M9i4J0dn9FXzzkdohB2i9E6/B5hKZCtowNIgGXuzDXZbv/07bIEu/Rp4dL/0sIkXHnfrvNTV3k3wtuklG81ZOYrYtHmT5HCPVGgKCm38kNlEfaifaUHROvYDHbYQ9GNnCQi8rms58RcgaGegjHp9a3Y4PPHmDv4NjowhETVfwgJlnWPa5hEQuYEYGaBfGfZBlJQ8XB3MRplZFzr3Xiq9V/uRvmI/JonNsyfWSKOBbU1cPZk6sBEVCSfkNQiFHQlkQq9m0K+AJiIHDJ6MxDtpQ5/owPZyA3zg2M/Tr58uczcg==
ARC-Message-Signature: i=1; a=rsa-sha256; c=relaxed/relaxed; d=microsoft.com;  s=arcselector9901; h=From:Date:Subject:Message-ID:Content-Type:MIME-Version:X-MS-Exchange-SenderADCheck; bh=UJpnUbzb6m5r87i0BjmmJkD5SI16i7uLAbmJ47Fi4MA=; b=NM7ohX5EuI/gupufWcpY8hYqoxv4wxQvbvArtxU0XCtxhPjj551ifnVviviInMmZpfY3Qd5dXEH8frvIh62s9Hu0VZ2PnFMSnqgTRj+RMcha4c4WIHTSdORCxFDovvKjAzvXsKNUFqsUnPhwZglUmXACP5G109dZUtbKlnlMO5f7uHqDRhPOG3eMXP6ZKNZUizowl9idKCA3JByPW4KRHZs4XkvxjWHjWIvOkAbNgJOC/M9f/d7DZDnibbu4KKC5fKIKRcsLCG5uWxIR2hOxj9RZ53OF5KQbCwaV62WPjq4X5dMowUXBRtaTTpuTtTixHNsuG+rYenn1piOVWPnTcQ==
ARC-Authentication-Results: i=1; mx.microsoft.com 1; spf=pass smtp.mailfrom=microsoft.com; dmarc=pass action=none header.from=microsoft.com; dkim=pass header.d=microsoft.com; arc=none
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=microsoft.com; s=selector2; h=From:Date:Subject:Message-ID:Content-Type:MIME-Version:X-MS-Exchange-SenderADCheck; bh=UJpnUbzb6m5r87i0BjmmJkD5SI16i7uLAbmJ47Fi4MA=; b=IQnNDAv+1u5rXNUsvzXZAobvcx0YAQWCi5JSk1kJllqKzuw5np8x7OJF/q1k1ZI5itOo3BRtAdYZjqosGlb3p0u0bl/HXXrUwsW2gG8LkUHJDZrM2f2jOebXB4Ggf8QN3C7dQM+09P5vHm5PHsqEjAgOe1beALsQHBopVPlpegM=
Received: from (2603:10b6:208:39::10) by MN2PR00MB0877.namprd00.prod.outlook.com (2603:10b6:208:38::30) with Microsoft SMTP Server (version=TLS1_2, cipher=TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384) id 15.20.3565.0; Thu, 29 Oct 2020 19:19:20 +0000
Received: from MN2PR00MB0622.namprd00.prod.outlook.com ([fe80::5462:2d47:839f:8446]) by MN2PR00MB0622.namprd00.prod.outlook.com ([fe80::5462:2d47:839f:8446%9]) with mapi id 15.20.3565.000; Thu, 29 Oct 2020 19:19:20 +0000
From: Tim Cappalli <Tim.Cappalli@microsoft.com>
To: Alan DeKok <aland@deployingradius.com>, Eliot Lear <lear=40cisco.com@dmarc.ietf.org>
CC: Max Pala <madwolf@openca.org>, EMU WG <emu@ietf.org>
Thread-Topic: [Emu] Consensus Call on OCSP usage in draft-ietf-emu-eap-tls13-11
Thread-Index: AQHWrg/pRBAKP68VrUaSTippL6q6g6muy8EAgAAKiwCAAAHLgIAACRoAgAATd8g=
Date: Thu, 29 Oct 2020 19:19:20 +0000
Message-ID: <MN2PR00MB06223CC9CA8EA107B8D9072395141@MN2PR00MB0622.namprd00.prod.outlook.com>
References: <CAOgPGoDbsunLOxrnFxa8uMxG6JYObX_r5VLOvVib5QmFHGOrwA@mail.gmail.com> <5D2BBCBB-62B9-41F5-86C3-A9CFD17AB38C@cisco.com> <6B43F397-A15F-46E9-95AD-EE0FBB5DDBD7@cablelabs.com> <B18C7AC4-51AD-4C89-90D0-1EC16271BA1F@cisco.com>, <C339ADFC-BD51-4012-8C49-3ED17AEB5807@deployingradius.com>
In-Reply-To: <C339ADFC-BD51-4012-8C49-3ED17AEB5807@deployingradius.com>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
authentication-results: deployingradius.com; dkim=none (message not signed) header.d=none;deployingradius.com; dmarc=none action=none header.from=microsoft.com;
x-originating-ip: [100.0.202.137]
x-ms-publictraffictype: Email
x-ms-office365-filtering-ht: Tenant
x-ms-office365-filtering-correlation-id: 2e53c4dd-12d5-4ae8-8088-08d87c3f89b3
x-ms-traffictypediagnostic: MN2PR00MB0877:
x-microsoft-antispam-prvs: <MN2PR00MB0877CBEDFD9CE08B4125DEDB95141@MN2PR00MB0877.namprd00.prod.outlook.com>
x-ms-oob-tlc-oobclassifiers: OLM:9508;
x-ms-exchange-senderadcheck: 1
x-microsoft-antispam: BCL:0;
x-microsoft-antispam-message-info: KL++iSv0xVujipPxADsbRdgiZPz1BScXr5Ey+YHUzbSfT6qeHx+sEb1CL3ZAuGSOHuUMjU5IzcYbz3mCyv4wxSSV4fz4ybkUHsKds92GpMd0CLJhK15tiOfD0RmGTwcbu7+oaoD1iKmANvHvUY7sZBBNzXns4a/r8EXBfuqiJaqf9zBle1nBCF/F8npvawueLPAQWpa2UEUSaPk8QtEmwGke0Tqu3FgzN6f5ymSfaBItZyeq26Bili1bOkceza27uN55s5W/vi6VBU7JcnX/A0OTsK2N4+Jlk6ROoKoKzwWbhgknXhWnvvQXqT1Z/DNflMEm0p6mwdD94D/SAI1AvHUTNsVknrWK+aSZVT4vQgfPCrhWV2Dydq0civnjQP4LnvbymxSNFjvCGeqlgz6r5A==
x-forefront-antispam-report: CIP:255.255.255.255; CTRY:; LANG:en; SCL:1; SRV:;  IPV:NLI; SFV:NSPM; H:MN2PR00MB0622.namprd00.prod.outlook.com; PTR:; CAT:NONE;  SFS:(4636009)(366004)(376002)(346002)(39860400002)(396003)(136003)(8676002)(9686003)(55016002)(8936002)(2906002)(110136005)(54906003)(316002)(82950400001)(82960400001)(5660300002)(26005)(186003)(8990500004)(4326008)(166002)(83380400001)(7696005)(53546011)(6506007)(966005)(86362001)(10290500003)(478600001)(66556008)(71200400001)(52536014)(33656002)(66476007)(66946007)(76116006)(66446008)(64756008); DIR:OUT; SFP:1102; 
x-ms-exchange-antispam-messagedata: InDNqmt+JH99tObHWlvHT6XnljNk1G6V1E1/eQYFFCVKwVG7dGpE5KXZriEt/9PyGNrR6vu6QqsmzDKtPEs1NUsfOXsySECRHJANA04sjOPipxtDFh3ZKSc21JkrpmfYObxu5QnzDN2Qb8zHCvF1CiXpIdXEQEJ02GrXF34ZR8wWKL4QXJLwWnNWCkmFvYFh+puH1MgvzRRz+stLZsCdadmQQdKpO927hUhemPIlf9PxLDbImkNPd0HRjeTke7RxWFfg912a59ml0u2Ussd9YUYfXZ7xjV1EUsBOjzCT28moLh9+5lH/J1VyVmRmEOU0voPqkBReU9w4qaKV4o8b0q8Sy7GKeVhrQj4h3QPn29iqobTRWrSe1AfLMTyeFPlQYYvR2SIUKPlRK2ZFSNoVySvHouuwhOWNbzhmimTYR40wpIKZ7oaianbYt864iPGt6VqydSEBwRUieaCJ8YYSguhb4hjuc6h0YghvLF4dSS0rFU1+ZFqvvmaQlbqmobYnlSte3QOYHW8HGi2Bon0sm0F7BH6xvukPEs0e+Nna9mPUav7+nF46AG0nVnEYq0dGvz17Lxw+OC0ow1q7QxcVhA==
x-ms-exchange-transport-forked: True
Content-Type: multipart/alternative; boundary="_000_MN2PR00MB06223CC9CA8EA107B8D9072395141MN2PR00MB0622namp_"
MIME-Version: 1.0
X-OriginatorOrg: microsoft.com
X-MS-Exchange-CrossTenant-AuthAs: Internal
X-MS-Exchange-CrossTenant-AuthSource: MN2PR00MB0622.namprd00.prod.outlook.com
X-MS-Exchange-CrossTenant-Network-Message-Id: 2e53c4dd-12d5-4ae8-8088-08d87c3f89b3
X-MS-Exchange-CrossTenant-originalarrivaltime: 29 Oct 2020 19:19:20.7211 (UTC)
X-MS-Exchange-CrossTenant-fromentityheader: Hosted
X-MS-Exchange-CrossTenant-id: 72f988bf-86f1-41af-91ab-2d7cd011db47
X-MS-Exchange-CrossTenant-mailboxtype: HOSTED
X-MS-Exchange-CrossTenant-userprincipalname: zVuYSgKzylP16WWLd4KYKrElGf9O9xsQrjDwV1Qu12ZqiPspK+birhglOhXSybPjJDzsx6anrPTHelwzWdfC6g==
X-MS-Exchange-Transport-CrossTenantHeadersStamped: MN2PR00MB0877
Archived-At: <https://mailarchive.ietf.org/arch/msg/emu/_vLskRR8vsj3vDVmvMuoH-941wc>
Subject: Re: [Emu] Consensus Call on OCSP usage in draft-ietf-emu-eap-tls13-11
X-BeenThere: emu@ietf.org
X-Mailman-Version: 2.1.29
Precedence: list
List-Id: "EAP Methods Update \(EMU\)" <emu.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/emu>, <mailto:emu-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/emu/>
List-Post: <mailto:emu@ietf.org>
List-Help: <mailto:emu-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/emu>, <mailto:emu-request@ietf.org?subject=subscribe>
X-List-Received-Date: Thu, 29 Oct 2020 19:19:27 -0000

--_000_MN2PR00MB06223CC9CA8EA107B8D9072395141MN2PR00MB0622namp_
Content-Type: text/plain; charset="Windows-1252"
Content-Transfer-Encoding: quoted-printable

+1

From: Emu <emu-bounces@ietf.org>
Date: Thursday, October 29, 2020 at 14:10
To: Eliot Lear <lear=3D40cisco.com@dmarc.ietf.org>
Cc: Max Pala <madwolf@openca.org>, EMU WG <emu@ietf.org>
Subject: Re: [Emu] Consensus Call on OCSP usage in draft-ietf-emu-eap-tls13=
-11
  +1

> On Oct 29, 2020, at 1:37 PM, Eliot Lear <lear=3D40cisco.com@dmarc.ietf.or=
g> wrote:
>
> Hi Max
>
>> On 29 Oct 2020, at 18:30, Max Pala <madwolf@openca.org> wrote:
>>
>> Hi Eliot, all,
>>
>> In our industry we solved this issue by requiring OCSP stapling if and o=
nly if the certificate being validated carries the OCSP URI in the certific=
ate.
>
> Perfectly reasonable.
>
>>
>> This allows us to live in a mixed environment where support for OCSP mig=
ht have been introduced later on and allows the CA to explicitly support OC=
SP for the certificate by including the URL in it.
>
> Yep.
>
>>
>> If the =93ecosystem=94 policy allows it =96 you might suggest that if OC=
SP responses are not not provided but the URL where to get OCSP responses i=
s known to the device (or it is in the certificate), the device/entity can =
continue with the authentication but it should not enable any device/entity=
 functionality before successfully executing (and validating) the OCSP prot=
ocol first (and disconnect if not reachable/invalid/revoked).
>>
>> Just my 2 cents.
>>
>
> Worth more.
>
> Eliot
>
>> Cheers,
>> Max
>>
>> From: Emu <emu-bounces@ietf.org> on behalf of Eliot Lear <lear=3D40cisco=
.com@dmarc.ietf.org>
>> Date: Thursday, October 29, 2020 at 10:53 AM
>> To: Joseph Salowey <joe@salowey.net>
>> Cc: EMU WG <emu@ietf.org>
>> Subject: Re: [Emu] Consensus Call on OCSP usage in draft-ietf-emu-eap-tl=
s13-11
>>
>> Hi Joe,
>>
>> My suggestion is that we add some discussion about what to do in the cas=
e of no connectivity to the CA.  This will be a not-uncommon occurrence, IM=
HO, in industrial use cases.
>>
>> Eliot
>>
>>
>>> On 29 Oct 2020, at 17:23, Joseph Salowey <joe@salowey.net> wrote:
>>>
>>> An issue was raised in a review of  draft-ietf-emu-eap-tls13-11 on the =
mandatory requirement for OCSP stapling [1].  The document makes the use of=
 OCSP mandatory in section 5.4 [2]. Several folks have pointed out that thi=
s may not be feasible in all deployments.  This is a quick consensus call f=
or this issue.   Please indicate which option below you support and why.  P=
lease respond by November 5, 2020.
>>>
>>> 1. Keep the text as is with OCSP mandatory for all implementations
>>>
>>> 2. Require Servers to Implement and Recommended to Use OCSP with text s=
imilar to the following:
>>>
>>> =93EAP-TLS servers supporting TLS 1.3 MUST implement Certificate Status=
 Requests (OCSP stapling) as specified in Section 4.4.2.1 of [RFC8446].  It=
 is RECOMMENDED that EAP-TLS peers and servers use OCSP stapling for verify=
ing the status of server certificates as specified in Section 4.4.2.1 of [R=
FC8446]. When an EAP-TLS peer uses OCSP to verify the certificate status of=
 the EAP-TLS server, it MUST use Certificate Status Requests for the server=
's certificate chain and it MUST treat a CertificateEntry (except the trust=
 anchor) without a valid CertificateStatus extension as invalid and abort t=
he handshake with an appropriate alert.=93
>>>
>>> Thanks,
>>>
>>> Joe
>>>
>>> [1] https://nam06.safelinks.protection.outlook.com/?url=3Dhttps%3A%2F%2=
Fmailarchive.ietf.org%2Farch%2Fmsg%2Femu%2F0DnfUWPqvKX0_Wo8s-ZypergMHI%2F&a=
mp;data=3D04%7C01%7Ctim.cappalli%40microsoft.com%7C78d538dffbd7449646e508d8=
7c35d391%7C72f988bf86f141af91ab2d7cd011db47%7C1%7C0%7C637395918459834859%7C=
Unknown%7CTWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiL=
CJXVCI6Mn0%3D%7C3000&amp;sdata=3DKrJVJ6Un4%2BHpycHthG7MZPKDJUCHxrCPqib4bMrt=
RMQ%3D&amp;reserved=3D0
>>> [2] https://nam06.safelinks.protection.outlook.com/?url=3Dhttps%3A%2F%2=
Ftools.ietf.org%2Fhtml%2Fdraft-ietf-emu-eap-tls13-11%23section-5.4&amp;data=
=3D04%7C01%7Ctim.cappalli%40microsoft.com%7C78d538dffbd7449646e508d87c35d39=
1%7C72f988bf86f141af91ab2d7cd011db47%7C1%7C0%7C637395918459834859%7CUnknown=
%7CTWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6=
Mn0%3D%7C3000&amp;sdata=3DxuERey5ZNv3DjwO10WKS0f2cK87ObmQ6H2WXTzqtBDA%3D&am=
p;reserved=3D0
>>> _______________________________________________
>>> Emu mailing list
>>> Emu@ietf.org
>>> https://nam06.safelinks.protection.outlook.com/?url=3Dhttps%3A%2F%2Fwww=
.ietf.org%2Fmailman%2Flistinfo%2Femu&amp;data=3D04%7C01%7Ctim.cappalli%40mi=
crosoft.com%7C78d538dffbd7449646e508d87c35d391%7C72f988bf86f141af91ab2d7cd0=
11db47%7C1%7C0%7C637395918459834859%7CUnknown%7CTWFpbGZsb3d8eyJWIjoiMC4wLjA=
wMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D%7C3000&amp;sdata=3Dsl%2=
B4jNsThcZ8381i7AxlQ7z38dBM%2Bqz1Stox7h7ThLw%3D&amp;reserved=3D0
>>
>> _______________________________________________ Emu mailing list Emu@iet=
f.orghttps://nam06.safelinks.protection.outlook.com/?url=3Dhttps%3A%2F%2Fww=
w.ietf.org%2Fmailman%2Flistinfo%2Femu&amp;data=3D04%7C01%7Ctim.cappalli%40m=
icrosoft.com%7C78d538dffbd7449646e508d87c35d391%7C72f988bf86f141af91ab2d7cd=
011db47%7C1%7C0%7C637395918459834859%7CUnknown%7CTWFpbGZsb3d8eyJWIjoiMC4wLj=
AwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D%7C3000&amp;sdata=3Dsl%=
2B4jNsThcZ8381i7AxlQ7z38dBM%2Bqz1Stox7h7ThLw%3D&amp;reserved=3D0
>
> _______________________________________________
> Emu mailing list
> Emu@ietf.org
> https://nam06.safelinks.protection.outlook.com/?url=3Dhttps%3A%2F%2Fwww.i=
etf.org%2Fmailman%2Flistinfo%2Femu&amp;data=3D04%7C01%7Ctim.cappalli%40micr=
osoft.com%7C78d538dffbd7449646e508d87c35d391%7C72f988bf86f141af91ab2d7cd011=
db47%7C1%7C0%7C637395918459834859%7CUnknown%7CTWFpbGZsb3d8eyJWIjoiMC4wLjAwM=
DAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D%7C3000&amp;sdata=3Dsl%2B4=
jNsThcZ8381i7AxlQ7z38dBM%2Bqz1Stox7h7ThLw%3D&amp;reserved=3D0

_______________________________________________
Emu mailing list
Emu@ietf.org
https://nam06.safelinks.protection.outlook.com/?url=3Dhttps%3A%2F%2Fwww.iet=
f.org%2Fmailman%2Flistinfo%2Femu&amp;data=3D04%7C01%7Ctim.cappalli%40micros=
oft.com%7C78d538dffbd7449646e508d87c35d391%7C72f988bf86f141af91ab2d7cd011db=
47%7C1%7C0%7C637395918459844854%7CUnknown%7CTWFpbGZsb3d8eyJWIjoiMC4wLjAwMDA=
iLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D%7C3000&amp;sdata=3DErp6hV0d=
ny9j3vyAbFhDmqHLxrn66Aet9XtjOwCKSLw%3D&amp;reserved=3D0

--_000_MN2PR00MB06223CC9CA8EA107B8D9072395141MN2PR00MB0622namp_
Content-Type: text/html; charset="Windows-1252"
Content-Transfer-Encoding: quoted-printable

<html xmlns:o=3D"urn:schemas-microsoft-com:office:office" xmlns:w=3D"urn:sc=
hemas-microsoft-com:office:word" xmlns:m=3D"http://schemas.microsoft.com/of=
fice/2004/12/omml" xmlns=3D"http://www.w3.org/TR/REC-html40">
<head>
<meta http-equiv=3D"Content-Type" content=3D"text/html; charset=3DWindows-1=
252">
<meta name=3D"Generator" content=3D"Microsoft Word 15 (filtered medium)">
<style><!--
/* Font Definitions */
@font-face
	{font-family:"Cambria Math";
	panose-1:2 4 5 3 5 4 6 3 2 4;}
@font-face
	{font-family:Calibri;
	panose-1:2 15 5 2 2 2 4 3 2 4;}
@font-face
	{font-family:"Times New Roman \(Body CS\)";
	panose-1:2 11 6 4 2 2 2 2 2 4;}
/* Style Definitions */
p.MsoNormal, li.MsoNormal, div.MsoNormal
	{margin:0in;
	font-size:11.0pt;
	font-family:"Calibri",sans-serif;}
a:link, span.MsoHyperlink
	{mso-style-priority:99;
	color:blue;
	text-decoration:underline;}
span.EmailStyle19
	{mso-style-type:personal-reply;
	font-family:"Arial",sans-serif;
	color:windowtext;}
.MsoChpDefault
	{mso-style-type:export-only;
	font-size:10.0pt;}
@page WordSection1
	{size:8.5in 11.0in;
	margin:1.0in 1.0in 1.0in 1.0in;}
div.WordSection1
	{page:WordSection1;}
--></style>
</head>
<body lang=3D"EN-US" link=3D"blue" vlink=3D"purple" style=3D"word-wrap:brea=
k-word">
<div class=3D"WordSection1">
<p class=3D"MsoNormal"><span style=3D"font-family:&quot;Arial&quot;,sans-se=
rif">+1<o:p></o:p></span></p>
<p class=3D"MsoNormal"><span style=3D"font-family:&quot;Arial&quot;,sans-se=
rif"><o:p>&nbsp;</o:p></span></p>
<div style=3D"border:none;border-top:solid #B5C4DF 1.0pt;padding:3.0pt 0in =
0in 0in">
<p class=3D"MsoNormal" style=3D"margin-bottom:12.0pt"><b><span style=3D"fon=
t-size:12.0pt;color:black">From:
</span></b><span style=3D"font-size:12.0pt;color:black">Emu &lt;emu-bounces=
@ietf.org&gt;<br>
<b>Date: </b>Thursday, October 29, 2020 at 14:10<br>
<b>To: </b>Eliot Lear &lt;lear=3D40cisco.com@dmarc.ietf.org&gt;<br>
<b>Cc: </b>Max Pala &lt;madwolf@openca.org&gt;, EMU WG &lt;emu@ietf.org&gt;=
<br>
<b>Subject: </b>Re: [Emu] Consensus Call on OCSP usage in draft-ietf-emu-ea=
p-tls13-11<o:p></o:p></span></p>
</div>
<div>
<p class=3D"MsoNormal">&nbsp; +1<br>
<br>
&gt; On Oct 29, 2020, at 1:37 PM, Eliot Lear &lt;lear=3D40cisco.com@dmarc.i=
etf.org&gt; wrote:<br>
&gt; <br>
&gt; Hi Max<br>
&gt; <br>
&gt;&gt; On 29 Oct 2020, at 18:30, Max Pala &lt;madwolf@openca.org&gt; wrot=
e:<br>
&gt;&gt; <br>
&gt;&gt; Hi Eliot, all,<br>
&gt;&gt;&nbsp; <br>
&gt;&gt; In our industry we solved this issue by requiring OCSP stapling if=
 and only if the certificate being validated carries the OCSP URI in the ce=
rtificate.
<br>
&gt; <br>
&gt; Perfectly reasonable.<br>
&gt; <br>
&gt;&gt;&nbsp; <br>
&gt;&gt; This allows us to live in a mixed environment where support for OC=
SP might have been introduced later on and allows the CA to explicitly supp=
ort OCSP for the certificate by including the URL in it.<br>
&gt; <br>
&gt; Yep.<br>
&gt; <br>
&gt;&gt;&nbsp; <br>
&gt;&gt; If the =93ecosystem=94 policy allows it =96 you might suggest that=
 if OCSP responses are not not provided but the URL where to get OCSP respo=
nses is known to the device (or it is in the certificate), the device/entit=
y can continue with the authentication but it
 should not enable any device/entity functionality before successfully exec=
uting (and validating) the OCSP protocol first (and disconnect if not reach=
able/invalid/revoked).<br>
&gt;&gt;&nbsp; <br>
&gt;&gt; Just my 2 cents.<br>
&gt;&gt;&nbsp; <br>
&gt; <br>
&gt; Worth more.<br>
&gt; <br>
&gt; Eliot<br>
&gt; <br>
&gt;&gt; Cheers,<br>
&gt;&gt; Max<br>
&gt;&gt;&nbsp; <br>
&gt;&gt; From: Emu &lt;emu-bounces@ietf.org&gt; on behalf of Eliot Lear &lt=
;lear=3D40cisco.com@dmarc.ietf.org&gt;<br>
&gt;&gt; Date: Thursday, October 29, 2020 at 10:53 AM<br>
&gt;&gt; To: Joseph Salowey &lt;joe@salowey.net&gt;<br>
&gt;&gt; Cc: EMU WG &lt;emu@ietf.org&gt;<br>
&gt;&gt; Subject: Re: [Emu] Consensus Call on OCSP usage in draft-ietf-emu-=
eap-tls13-11<br>
&gt;&gt;&nbsp; <br>
&gt;&gt; Hi Joe,<br>
&gt;&gt;&nbsp; <br>
&gt;&gt; My suggestion is that we add some discussion about what to do in t=
he case of no connectivity to the CA.&nbsp; This will be a not-uncommon occ=
urrence, IMHO, in industrial use cases.<br>
&gt;&gt;&nbsp; <br>
&gt;&gt; Eliot<br>
&gt;&gt; <br>
&gt;&gt; <br>
&gt;&gt;&gt; On 29 Oct 2020, at 17:23, Joseph Salowey &lt;joe@salowey.net&g=
t; wrote:<br>
&gt;&gt;&gt;&nbsp; <br>
&gt;&gt;&gt; An issue was raised in a review of&nbsp; draft-ietf-emu-eap-tl=
s13-11 on the mandatory requirement for OCSP stapling [1].&nbsp; The docume=
nt makes the use of OCSP mandatory in section 5.4 [2]. Several folks have p=
ointed out that this may not be feasible in all deployments.&nbsp;
 This is a quick consensus call for this issue.&nbsp;&nbsp; Please indicate=
 which option below you support and why.&nbsp; Please respond by November 5=
, 2020.
<br>
&gt;&gt;&gt; <br>
&gt;&gt;&gt; 1. Keep the text as is with OCSP mandatory for all implementat=
ions<br>
&gt;&gt;&gt; <br>
&gt;&gt;&gt; 2. Require Servers to Implement and Recommended to Use OCSP wi=
th text similar to the following:<br>
&gt;&gt;&gt; <br>
&gt;&gt;&gt; =93EAP-TLS servers supporting TLS 1.3 MUST implement Certifica=
te Status Requests (OCSP stapling) as specified in Section 4.4.2.1 of [RFC8=
446].&nbsp; It is RECOMMENDED that EAP-TLS peers and servers use OCSP stapl=
ing for verifying the status of server certificates
 as specified in Section 4.4.2.1 of [RFC8446]. When an EAP-TLS peer uses OC=
SP to verify the certificate status of the EAP-TLS server, it MUST use Cert=
ificate Status Requests for the server's certificate chain and it MUST trea=
t a CertificateEntry (except the
 trust anchor) without a valid CertificateStatus extension as invalid and a=
bort the handshake with an appropriate alert.=93<br>
&gt;&gt;&gt;&nbsp; <br>
&gt;&gt;&gt; Thanks,<br>
&gt;&gt;&gt;&nbsp; <br>
&gt;&gt;&gt; Joe<br>
&gt;&gt;&gt;&nbsp; <br>
&gt;&gt;&gt; [1] <a href=3D"https://nam06.safelinks.protection.outlook.com/=
?url=3Dhttps%3A%2F%2Fmailarchive.ietf.org%2Farch%2Fmsg%2Femu%2F0DnfUWPqvKX0=
_Wo8s-ZypergMHI%2F&amp;amp;data=3D04%7C01%7Ctim.cappalli%40microsoft.com%7C=
78d538dffbd7449646e508d87c35d391%7C72f988bf86f141af91ab2d7cd011db47%7C1%7C0=
%7C637395918459834859%7CUnknown%7CTWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV=
2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D%7C3000&amp;amp;sdata=3DKrJVJ6Un4%2BHp=
ycHthG7MZPKDJUCHxrCPqib4bMrtRMQ%3D&amp;amp;reserved=3D0">
https://nam06.safelinks.protection.outlook.com/?url=3Dhttps%3A%2F%2Fmailarc=
hive.ietf.org%2Farch%2Fmsg%2Femu%2F0DnfUWPqvKX0_Wo8s-ZypergMHI%2F&amp;amp;d=
ata=3D04%7C01%7Ctim.cappalli%40microsoft.com%7C78d538dffbd7449646e508d87c35=
d391%7C72f988bf86f141af91ab2d7cd011db47%7C1%7C0%7C637395918459834859%7CUnkn=
own%7CTWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXV=
CI6Mn0%3D%7C3000&amp;amp;sdata=3DKrJVJ6Un4%2BHpycHthG7MZPKDJUCHxrCPqib4bMrt=
RMQ%3D&amp;amp;reserved=3D0</a><br>
&gt;&gt;&gt; [2] <a href=3D"https://nam06.safelinks.protection.outlook.com/=
?url=3Dhttps%3A%2F%2Ftools.ietf.org%2Fhtml%2Fdraft-ietf-emu-eap-tls13-11%23=
section-5.4&amp;amp;data=3D04%7C01%7Ctim.cappalli%40microsoft.com%7C78d538d=
ffbd7449646e508d87c35d391%7C72f988bf86f141af91ab2d7cd011db47%7C1%7C0%7C6373=
95918459834859%7CUnknown%7CTWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIi=
LCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D%7C3000&amp;amp;sdata=3DxuERey5ZNv3DjwO10WKS0=
f2cK87ObmQ6H2WXTzqtBDA%3D&amp;amp;reserved=3D0">
https://nam06.safelinks.protection.outlook.com/?url=3Dhttps%3A%2F%2Ftools.i=
etf.org%2Fhtml%2Fdraft-ietf-emu-eap-tls13-11%23section-5.4&amp;amp;data=3D0=
4%7C01%7Ctim.cappalli%40microsoft.com%7C78d538dffbd7449646e508d87c35d391%7C=
72f988bf86f141af91ab2d7cd011db47%7C1%7C0%7C637395918459834859%7CUnknown%7CT=
WFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%=
3D%7C3000&amp;amp;sdata=3DxuERey5ZNv3DjwO10WKS0f2cK87ObmQ6H2WXTzqtBDA%3D&am=
p;amp;reserved=3D0</a><br>
&gt;&gt;&gt; _______________________________________________<br>
&gt;&gt;&gt; Emu mailing list<br>
&gt;&gt;&gt; Emu@ietf.org<br>
&gt;&gt;&gt; <a href=3D"https://nam06.safelinks.protection.outlook.com/?url=
=3Dhttps%3A%2F%2Fwww.ietf.org%2Fmailman%2Flistinfo%2Femu&amp;amp;data=3D04%=
7C01%7Ctim.cappalli%40microsoft.com%7C78d538dffbd7449646e508d87c35d391%7C72=
f988bf86f141af91ab2d7cd011db47%7C1%7C0%7C637395918459834859%7CUnknown%7CTWF=
pbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D=
%7C3000&amp;amp;sdata=3Dsl%2B4jNsThcZ8381i7AxlQ7z38dBM%2Bqz1Stox7h7ThLw%3D&=
amp;amp;reserved=3D0">
https://nam06.safelinks.protection.outlook.com/?url=3Dhttps%3A%2F%2Fwww.iet=
f.org%2Fmailman%2Flistinfo%2Femu&amp;amp;data=3D04%7C01%7Ctim.cappalli%40mi=
crosoft.com%7C78d538dffbd7449646e508d87c35d391%7C72f988bf86f141af91ab2d7cd0=
11db47%7C1%7C0%7C637395918459834859%7CUnknown%7CTWFpbGZsb3d8eyJWIjoiMC4wLjA=
wMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D%7C3000&amp;amp;sdata=3D=
sl%2B4jNsThcZ8381i7AxlQ7z38dBM%2Bqz1Stox7h7ThLw%3D&amp;amp;reserved=3D0</a>=
<br>
&gt;&gt;&nbsp; <br>
&gt;&gt; _______________________________________________ Emu mailing list E=
mu@ietf.orghttps://nam06.safelinks.protection.outlook.com/?url=3Dhttps%3A%2=
F%2Fwww.ietf.org%2Fmailman%2Flistinfo%2Femu&amp;amp;data=3D04%7C01%7Ctim.ca=
ppalli%40microsoft.com%7C78d538dffbd7449646e508d87c35d391%7C72f988bf86f141a=
f91ab2d7cd011db47%7C1%7C0%7C637395918459834859%7CUnknown%7CTWFpbGZsb3d8eyJW=
IjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D%7C3000&amp;a=
mp;sdata=3Dsl%2B4jNsThcZ8381i7AxlQ7z38dBM%2Bqz1Stox7h7ThLw%3D&amp;amp;reser=
ved=3D0<br>
&gt; <br>
&gt; _______________________________________________<br>
&gt; Emu mailing list<br>
&gt; Emu@ietf.org<br>
&gt; <a href=3D"https://nam06.safelinks.protection.outlook.com/?url=3Dhttps=
%3A%2F%2Fwww.ietf.org%2Fmailman%2Flistinfo%2Femu&amp;amp;data=3D04%7C01%7Ct=
im.cappalli%40microsoft.com%7C78d538dffbd7449646e508d87c35d391%7C72f988bf86=
f141af91ab2d7cd011db47%7C1%7C0%7C637395918459834859%7CUnknown%7CTWFpbGZsb3d=
8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D%7C3000&=
amp;amp;sdata=3Dsl%2B4jNsThcZ8381i7AxlQ7z38dBM%2Bqz1Stox7h7ThLw%3D&amp;amp;=
reserved=3D0">
https://nam06.safelinks.protection.outlook.com/?url=3Dhttps%3A%2F%2Fwww.iet=
f.org%2Fmailman%2Flistinfo%2Femu&amp;amp;data=3D04%7C01%7Ctim.cappalli%40mi=
crosoft.com%7C78d538dffbd7449646e508d87c35d391%7C72f988bf86f141af91ab2d7cd0=
11db47%7C1%7C0%7C637395918459834859%7CUnknown%7CTWFpbGZsb3d8eyJWIjoiMC4wLjA=
wMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D%7C3000&amp;amp;sdata=3D=
sl%2B4jNsThcZ8381i7AxlQ7z38dBM%2Bqz1Stox7h7ThLw%3D&amp;amp;reserved=3D0</a>=
<br>
<br>
_______________________________________________<br>
Emu mailing list<br>
Emu@ietf.org<br>
<a href=3D"https://nam06.safelinks.protection.outlook.com/?url=3Dhttps%3A%2=
F%2Fwww.ietf.org%2Fmailman%2Flistinfo%2Femu&amp;amp;data=3D04%7C01%7Ctim.ca=
ppalli%40microsoft.com%7C78d538dffbd7449646e508d87c35d391%7C72f988bf86f141a=
f91ab2d7cd011db47%7C1%7C0%7C637395918459844854%7CUnknown%7CTWFpbGZsb3d8eyJW=
IjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D%7C3000&amp;a=
mp;sdata=3DErp6hV0dny9j3vyAbFhDmqHLxrn66Aet9XtjOwCKSLw%3D&amp;amp;reserved=
=3D0">https://nam06.safelinks.protection.outlook.com/?url=3Dhttps%3A%2F%2Fw=
ww.ietf.org%2Fmailman%2Flistinfo%2Femu&amp;amp;data=3D04%7C01%7Ctim.cappall=
i%40microsoft.com%7C78d538dffbd7449646e508d87c35d391%7C72f988bf86f141af91ab=
2d7cd011db47%7C1%7C0%7C637395918459844854%7CUnknown%7CTWFpbGZsb3d8eyJWIjoiM=
C4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D%7C3000&amp;amp;sd=
ata=3DErp6hV0dny9j3vyAbFhDmqHLxrn66Aet9XtjOwCKSLw%3D&amp;amp;reserved=3D0</=
a><o:p></o:p></p>
</div>
</div>
</body>
</html>

--_000_MN2PR00MB06223CC9CA8EA107B8D9072395141MN2PR00MB0622namp_--


From nobody Thu Oct 29 12:37:18 2020
Return-Path: <joe@salowey.net>
X-Original-To: emu@ietfa.amsl.com
Delivered-To: emu@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 712CC3A0A20 for <emu@ietfa.amsl.com>; Thu, 29 Oct 2020 12:37:17 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.898
X-Spam-Level: 
X-Spam-Status: No, score=-1.898 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, HTML_MESSAGE=0.001, SPF_HELO_NONE=0.001, SPF_PASS=-0.001, URIBL_BLOCKED=0.001] autolearn=unavailable autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (2048-bit key) header.d=salowey-net.20150623.gappssmtp.com
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 Yi4dhDSY16Kz for <emu@ietfa.amsl.com>; Thu, 29 Oct 2020 12:37:15 -0700 (PDT)
Received: from mail-qv1-xf2b.google.com (mail-qv1-xf2b.google.com [IPv6:2607:f8b0:4864:20::f2b]) (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 8C8263A0B9D for <emu@ietf.org>; Thu, 29 Oct 2020 12:37:12 -0700 (PDT)
Received: by mail-qv1-xf2b.google.com with SMTP id t20so1832897qvv.8 for <emu@ietf.org>; Thu, 29 Oct 2020 12:37:12 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=salowey-net.20150623.gappssmtp.com; s=20150623; h=mime-version:references:in-reply-to:from:date:message-id:subject:to :cc; bh=zJhalFPYbbaoXErxrZzGVkTZe2Wn1jrU07x92uGuf3A=; b=qcWGRefwL4Ce2tKqy7iuh7fCTX+hI486zDboRaAKcZvCrR/dYN7TzaCMH7K/LiBpmt VA81cIE4+LsPXw9QGl6FDCklOQoSjQTCFBfc9HJGszSCNwxGzouP4LpFB9jPxelNP6n9 L6JuZe7nawumAAOlYkY7Z3mMnGgxS0Vgqsdpgsyboc9tbu9yNLvWJYkbCR6xl1f7NNeQ ra7kITH9m1eY+NhhFuY6rFFX4PkDKmRqeDSZs4wW/aY0HJin3LwT/oWcendP1OFIdbkm l+Z5OiA+PrxqDabPIZQYVbtSxTFB7HPbuOuHhIT5laCH0jUQLLRbSJugt5gtktvZw6cY wxOA==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:mime-version:references:in-reply-to:from:date :message-id:subject:to:cc; bh=zJhalFPYbbaoXErxrZzGVkTZe2Wn1jrU07x92uGuf3A=; b=IiBXfUGZbVHHsqxWztA0EkJbwHD8KxLb4bAyPASvan6+kkm5JYrFst/gfF4xPpVu+d 6nM7jvfCVZHcwkOFfKvumsAgftpk57MhLDix0ClmfC5AaMHdQB1CVznOLQ+eywkB8TIr akS0W+OG1k7mX4Yu/tDohzE/4/1Iu6jWbyEmjBCkO9o93+58GEbaiUbNU7viqKYGqqeV 8nug61FBj86UNOqqtjdnQ3xKXBSmFxbWBaQzHlDY/mYoDWNVQu7aYv4Z1RhDWfJ5uP1J ikigIbfgZ1drtUyXmWLEY0m9TZOAd9J02mn1qfr6Ay57W/nkDLhv3TcoL7ZnrqQPPBKz k25g==
X-Gm-Message-State: AOAM532yhTLnHDjvjtn4EFRr9FqNWI5rjxJgeSDRZZGAT2I22cyEZ34C Vo1rD6EBIy88ESEQSSKDyQ5ErQr1NK5ZXN8jiKKxBg==
X-Google-Smtp-Source: ABdhPJxdlcRdKEc3xUIbpuk9a10xq27Zx8MgOuCINDxwsSl+VR7sK+NU76y7tWLjStz8ZdyuPlgwB4kHLXcxNAJ6I20=
X-Received: by 2002:ad4:4105:: with SMTP id i5mr5974131qvp.47.1604000231550; Thu, 29 Oct 2020 12:37:11 -0700 (PDT)
MIME-Version: 1.0
References: <CAOgPGoDbsunLOxrnFxa8uMxG6JYObX_r5VLOvVib5QmFHGOrwA@mail.gmail.com> <5D2BBCBB-62B9-41F5-86C3-A9CFD17AB38C@cisco.com> <6B43F397-A15F-46E9-95AD-EE0FBB5DDBD7@cablelabs.com>
In-Reply-To: <6B43F397-A15F-46E9-95AD-EE0FBB5DDBD7@cablelabs.com>
From: Joseph Salowey <joe@salowey.net>
Date: Thu, 29 Oct 2020 12:37:00 -0700
Message-ID: <CAOgPGoDRMyGJ_PQEf=h21sT26GcKPfraFj=MuVPX9yjbWJboVA@mail.gmail.com>
To: Max Pala <madwolf@openca.org>
Cc: Eliot Lear <lear=40cisco.com@dmarc.ietf.org>, EMU WG <emu@ietf.org>
Content-Type: multipart/alternative; boundary="0000000000000588de05b2d468e1"
Archived-At: <https://mailarchive.ietf.org/arch/msg/emu/3iOhMvC47wWNssSPsDEJWXQSheU>
Subject: Re: [Emu] Consensus Call on OCSP usage in draft-ietf-emu-eap-tls13-11
X-BeenThere: emu@ietf.org
X-Mailman-Version: 2.1.29
Precedence: list
List-Id: "EAP Methods Update \(EMU\)" <emu.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/emu>, <mailto:emu-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/emu/>
List-Post: <mailto:emu@ietf.org>
List-Help: <mailto:emu-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/emu>, <mailto:emu-request@ietf.org?subject=subscribe>
X-List-Received-Date: Thu, 29 Oct 2020 19:37:17 -0000

--0000000000000588de05b2d468e1
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable

On Thu, Oct 29, 2020 at 10:30 AM Max Pala <madwolf@openca.org> wrote:

> Hi Eliot, all,
>
>
>
> In our industry we solved this issue by *requiring OCSP stapling if and
> only if the certificate being validated carries the OCSP URI in the
> certificate*.
>
>
>
> This allows us to live in a mixed environment where support for OCSP migh=
t
> have been introduced later on and allows the CA to explicitly support OCS=
P
> for the certificate by including the URL in it.
>
>
>
> If the =E2=80=9Cecosystem=E2=80=9D policy allows it =E2=80=93 you might s=
uggest that if OCSP
> responses are not not provided but the URL where to get OCSP responses is
> known to the device (or it is in the certificate), the device/entity can
> continue with the authentication but it should not enable any device/enti=
ty
> functionality before successfully executing (and validating) the OCSP
> protocol first (and disconnect if not reachable/invalid/revoked).
>
>
>

[Joe] So you are in favor of both clients and servers
mandatory implementing OCSP, but only requiring it be used when it is
signalled in the certificate?


> Just my 2 cents.
>
>
>
> Cheers,
> Max
>
>
>
> *From: *Emu <emu-bounces@ietf.org> on behalf of Eliot Lear <lear=3D
> 40cisco.com@dmarc.ietf.org>
> *Date: *Thursday, October 29, 2020 at 10:53 AM
> *To: *Joseph Salowey <joe@salowey.net>
> *Cc: *EMU WG <emu@ietf.org>
> *Subject: *Re: [Emu] Consensus Call on OCSP usage in
> draft-ietf-emu-eap-tls13-11
>
>
>
> Hi Joe,
>
>
>
> My suggestion is that we add some discussion about what to do in the case
> of no connectivity to the CA.  This will be a not-uncommon occurrence,
> IMHO, in industrial use cases.
>
>
>
> Eliot
>
>
>
> On 29 Oct 2020, at 17:23, Joseph Salowey <joe@salowey.net> wrote:
>
>
>
> An issue was raised in a review of  draft-ietf-emu-eap-tls13-11 on the
> mandatory requirement for OCSP stapling [1].  The document makes the use =
of
> OCSP mandatory in section 5.4 [2]. Several folks have pointed out that th=
is
> may not be feasible in all deployments.  This is a quick consensus call f=
or
> this issue.   Please indicate which option below you support and why.
> Please respond by November 5, 2020.
>
> 1. Keep the text as is with OCSP mandatory for all implementations
>
> 2. Require Servers to Implement and Recommended to Use OCSP with text
> similar to the following:
>
> =E2=80=9CEAP-TLS servers supporting TLS 1.3 MUST implement Certificate St=
atus
> Requests (OCSP stapling) as specified in Section 4.4.2.1 of [RFC8446].  I=
t
> is RECOMMENDED that EAP-TLS peers and servers use OCSP stapling for
> verifying the status of server certificates as specified in Section 4.4.2=
.1
> of [RFC8446]. When an EAP-TLS peer uses OCSP to verify the certificate
> status of the EAP-TLS server, it MUST use Certificate Status Requests for
> the server's certificate chain and it MUST treat a CertificateEntry (exce=
pt
> the trust anchor) without a valid CertificateStatus extension as invalid
> and abort the handshake with an appropriate alert.=E2=80=9C
>
>
>
> Thanks,
>
>
>
> Joe
>
>
>
> [1] https://mailarchive.ietf.org/arch/msg/emu/0DnfUWPqvKX0_Wo8s-ZypergMHI=
/
> [2] https://tools.ietf.org/html/draft-ietf-emu-eap-tls13-11#section-5.4
>
> _______________________________________________
> Emu mailing list
> Emu@ietf.org
> https://www.ietf.org/mailman/listinfo/emu
>
>
>
> _______________________________________________ Emu mailing list
> Emu@ietf.org https://www.ietf.org/mailman/listinfo/emu
>

--0000000000000588de05b2d468e1
Content-Type: text/html; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable

<div dir=3D"ltr"><div dir=3D"ltr"><br></div><br><div class=3D"gmail_quote">=
<div dir=3D"ltr" class=3D"gmail_attr">On Thu, Oct 29, 2020 at 10:30 AM Max =
Pala &lt;<a href=3D"mailto:madwolf@openca.org">madwolf@openca.org</a>&gt; w=
rote:<br></div><blockquote class=3D"gmail_quote" style=3D"margin:0px 0px 0p=
x 0.8ex;border-left:1px solid rgb(204,204,204);padding-left:1ex"><div lang=
=3D"EN-US" style=3D"overflow-wrap: break-word;"><div class=3D"gmail-m_14443=
84397523289385WordSection1"><p class=3D"MsoNormal">Hi Eliot, all,<u></u><u>=
</u></p><p class=3D"MsoNormal"><u></u>=C2=A0<u></u></p><p class=3D"MsoNorma=
l">In our industry we solved this issue by <b><i>requiring OCSP stapling if=
 and only if the certificate being validated carries the OCSP URI in the ce=
rtificate</i></b>. <u></u><u></u></p><p class=3D"MsoNormal"><u></u>=C2=A0<u=
></u></p><p class=3D"MsoNormal">This allows us to live in a mixed environme=
nt where support for OCSP might have been introduced later on and allows th=
e CA to explicitly support OCSP for the certificate by including the URL in=
 it.<u></u><u></u></p><p class=3D"MsoNormal"><u></u>=C2=A0<u></u></p><p cla=
ss=3D"MsoNormal">If the =E2=80=9Cecosystem=E2=80=9D policy allows it =E2=80=
=93 you might suggest that if OCSP responses are not not provided but the U=
RL where to get OCSP responses is known to the device (or it is in the cert=
ificate), the device/entity can continue with the authentication but it sho=
uld not enable any device/entity functionality before successfully executin=
g (and validating) the OCSP protocol first (and disconnect if not reachable=
/invalid/revoked).<u></u><u></u></p><p class=3D"MsoNormal"><u></u>=C2=A0</p=
></div></div></blockquote><div><br></div><div>[Joe] So you are in favor of =
both clients and servers mandatory=C2=A0implementing OCSP, but only requiri=
ng it be used when it is signalled in the certificate?</div><div>=C2=A0</di=
v><blockquote class=3D"gmail_quote" style=3D"margin:0px 0px 0px 0.8ex;borde=
r-left:1px solid rgb(204,204,204);padding-left:1ex"><div lang=3D"EN-US" sty=
le=3D"overflow-wrap: break-word;"><div class=3D"gmail-m_1444384397523289385=
WordSection1"><p class=3D"MsoNormal"><u></u></p><p class=3D"MsoNormal">Just=
 my 2 cents.<u></u><u></u></p><p class=3D"MsoNormal"><u></u>=C2=A0<u></u></=
p><p class=3D"MsoNormal">Cheers,<br>Max<u></u><u></u></p><p class=3D"MsoNor=
mal"><u></u>=C2=A0<u></u></p><div style=3D"border-right:none;border-bottom:=
none;border-left:none;border-top:1pt solid rgb(181,196,223);padding:3pt 0in=
 0in"><p class=3D"MsoNormal" style=3D"margin-left:0.5in"><b><span style=3D"=
font-size:12pt;color:black">From: </span></b><span style=3D"font-size:12pt;=
color:black">Emu &lt;<a href=3D"mailto:emu-bounces@ietf.org" target=3D"_bla=
nk">emu-bounces@ietf.org</a>&gt; on behalf of Eliot Lear &lt;lear=3D<a href=
=3D"mailto:40cisco.com@dmarc.ietf.org" target=3D"_blank">40cisco.com@dmarc.=
ietf.org</a>&gt;<br><b>Date: </b>Thursday, October 29, 2020 at 10:53 AM<br>=
<b>To: </b>Joseph Salowey &lt;<a href=3D"mailto:joe@salowey.net" target=3D"=
_blank">joe@salowey.net</a>&gt;<br><b>Cc: </b>EMU WG &lt;<a href=3D"mailto:=
emu@ietf.org" target=3D"_blank">emu@ietf.org</a>&gt;<br><b>Subject: </b>Re:=
 [Emu] Consensus Call on OCSP usage in draft-ietf-emu-eap-tls13-11<u></u><u=
></u></span></p></div><div><p class=3D"MsoNormal" style=3D"margin-left:0.5i=
n"><u></u>=C2=A0<u></u></p></div><div><p class=3D"MsoNormal" style=3D"margi=
n-left:0.5in">Hi Joe,<u></u><u></u></p><div><p class=3D"MsoNormal" style=3D=
"margin-left:0.5in"><u></u>=C2=A0<u></u></p></div><div><p class=3D"MsoNorma=
l" style=3D"margin-left:0.5in">My suggestion is that we add some discussion=
 about what to do in the case of no connectivity to the CA.=C2=A0 This will=
 be a not-uncommon occurrence, IMHO, in industrial use cases.<u></u><u></u>=
</p></div><div><p class=3D"MsoNormal" style=3D"margin-left:0.5in"><u></u>=
=C2=A0<u></u></p></div><div><p class=3D"MsoNormal" style=3D"margin-left:0.5=
in">Eliot<u></u><u></u></p></div><div><div><p class=3D"MsoNormal" style=3D"=
margin-left:0.5in"><br><br><u></u><u></u></p><blockquote style=3D"margin-to=
p:5pt;margin-bottom:5pt"><div><p class=3D"MsoNormal" style=3D"margin-left:0=
.5in">On 29 Oct 2020, at 17:23, Joseph Salowey &lt;<a href=3D"mailto:joe@sa=
lowey.net" target=3D"_blank">joe@salowey.net</a>&gt; wrote:<u></u><u></u></=
p></div><p class=3D"MsoNormal" style=3D"margin-left:0.5in"><u></u>=C2=A0<u>=
</u></p><div><div><p class=3D"MsoNormal" style=3D"margin-left:0.5in">An iss=
ue was raised in a review of =C2=A0draft-ietf-emu-eap-tls13-11 on the manda=
tory requirement for OCSP stapling [1].=C2=A0 The document makes the use of=
 OCSP mandatory in section 5.4 [2]. Several folks have pointed out that thi=
s may not be feasible in all deployments.=C2=A0 This is a quick consensus c=
all for this issue. =C2=A0 Please indicate which option below you support a=
nd why.=C2=A0 Please respond=C2=A0by November 5, 2020.=C2=A0<br><br>1. Keep=
 the text as is with OCSP mandatory for all implementations<br><br>2. Requi=
re Servers to Implement and Recommended to Use OCSP with text similar to th=
e following:<br><br>=E2=80=9CEAP-TLS servers supporting TLS 1.3 MUST implem=
ent Certificate Status Requests (OCSP stapling) as specified in Section 4.4=
.2.1 of [RFC8446].=C2=A0 It is RECOMMENDED that EAP-TLS peers and servers u=
se OCSP stapling for verifying the status of server certificates as specifi=
ed in Section 4.4.2.1 of [RFC8446]. When an EAP-TLS peer uses OCSP to verif=
y the certificate status of the EAP-TLS server, it MUST use Certificate Sta=
tus Requests for the server&#39;s certificate chain and it MUST treat a Cer=
tificateEntry (except the trust anchor) without a valid CertificateStatus e=
xtension as invalid and abort the handshake with an appropriate alert.=E2=
=80=9C<u></u><u></u></p><div><p class=3D"MsoNormal" style=3D"margin-left:0.=
5in"><u></u>=C2=A0<u></u></p></div><div><p class=3D"MsoNormal" style=3D"mar=
gin-left:0.5in">Thanks,<u></u><u></u></p></div><div><p class=3D"MsoNormal" =
style=3D"margin-left:0.5in"><u></u>=C2=A0<u></u></p></div><div><p class=3D"=
MsoNormal" style=3D"margin-left:0.5in">Joe<u></u><u></u></p></div><div><div=
><p class=3D"MsoNormal" style=3D"margin-left:0.5in"><u></u>=C2=A0<u></u></p=
></div><p class=3D"MsoNormal" style=3D"margin-left:0.5in">[1] <a href=3D"ht=
tps://mailarchive.ietf.org/arch/msg/emu/0DnfUWPqvKX0_Wo8s-ZypergMHI/" targe=
t=3D"_blank">https://mailarchive.ietf.org/arch/msg/emu/0DnfUWPqvKX0_Wo8s-Zy=
pergMHI/</a><br>[2] <a href=3D"https://tools.ietf.org/html/draft-ietf-emu-e=
ap-tls13-11#section-5.4" target=3D"_blank">https://tools.ietf.org/html/draf=
t-ietf-emu-eap-tls13-11#section-5.4</a><u></u><u></u></p></div></div><p cla=
ss=3D"MsoNormal" style=3D"margin-left:0.5in">______________________________=
_________________<br>Emu mailing list<br><a href=3D"mailto:Emu@ietf.org" ta=
rget=3D"_blank">Emu@ietf.org</a><br><a href=3D"https://www.ietf.org/mailman=
/listinfo/emu" target=3D"_blank">https://www.ietf.org/mailman/listinfo/emu<=
/a><u></u><u></u></p></div></blockquote></div><p class=3D"MsoNormal" style=
=3D"margin-left:0.5in"><u></u>=C2=A0<u></u></p></div></div><p class=3D"MsoN=
ormal" style=3D"margin-left:0.5in">________________________________________=
_______ Emu mailing list <a href=3D"mailto:Emu@ietf.org" target=3D"_blank">=
Emu@ietf.org</a> <a href=3D"https://www.ietf.org/mailman/listinfo/emu" targ=
et=3D"_blank">https://www.ietf.org/mailman/listinfo/emu</a> <u></u><u></u><=
/p></div></div>
</blockquote></div></div>

--0000000000000588de05b2d468e1--


From nobody Thu Oct 29 15:12:58 2020
Return-Path: <mcr+ietf@sandelman.ca>
X-Original-To: emu@ietfa.amsl.com
Delivered-To: emu@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 147733A0930 for <emu@ietfa.amsl.com>; Thu, 29 Oct 2020 15:12:57 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.899
X-Spam-Level: 
X-Spam-Status: No, score=-1.899 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, SPF_HELO_NONE=0.001, SPF_PASS=-0.001, URIBL_BLOCKED=0.001] autolearn=ham autolearn_force=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 tJfYGCPeETgE for <emu@ietfa.amsl.com>; Thu, 29 Oct 2020 15:12:55 -0700 (PDT)
Received: from tuna.sandelman.ca (tuna.sandelman.ca [IPv6:2607:f0b0:f:3:216:3eff:fe7c:d1f3]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id E7F3C3A08AF for <emu@ietf.org>; Thu, 29 Oct 2020 15:12:54 -0700 (PDT)
Received: from localhost (localhost [127.0.0.1]) by tuna.sandelman.ca (Postfix) with ESMTP id 73575389D9; Thu, 29 Oct 2020 18:19:40 -0400 (EDT)
Received: from tuna.sandelman.ca ([127.0.0.1]) by localhost (localhost [127.0.0.1]) (amavisd-new, port 10024) with LMTP id JyUXqh-4Szpd; Thu, 29 Oct 2020 18:19:40 -0400 (EDT)
Received: from sandelman.ca (obiwan.sandelman.ca [IPv6:2607:f0b0:f:2::247]) by tuna.sandelman.ca (Postfix) with ESMTP id 07AFD389D3; Thu, 29 Oct 2020 18:19:40 -0400 (EDT)
Received: from localhost (localhost [IPv6:::1]) by sandelman.ca (Postfix) with ESMTP id C7B3F59A; Thu, 29 Oct 2020 18:12:52 -0400 (EDT)
From: Michael Richardson <mcr+ietf@sandelman.ca>
To: Joseph Salowey <joe@salowey.net>
cc: EMU WG <emu@ietf.org>
In-Reply-To: <CAOgPGoDbsunLOxrnFxa8uMxG6JYObX_r5VLOvVib5QmFHGOrwA@mail.gmail.com>
References: <CAOgPGoDbsunLOxrnFxa8uMxG6JYObX_r5VLOvVib5QmFHGOrwA@mail.gmail.com>
X-Mailer: MH-E 8.6+git; nmh 1.7+dev; GNU Emacs 26.1
X-Face: $\n1pF)h^`}$H>Hk{L"x@)JS7<%Az}5RyS@k9X%29-lHB$Ti.V>2bi.~ehC0; <'$9xN5Ub# z!G,p`nR&p7Fz@^UXIn156S8.~^@MJ*mMsD7=QFeq%AL4m<nPbLgmtKK-5dC@#:k
MIME-Version: 1.0
Content-Type: multipart/signed; boundary="=-=-="; micalg=pgp-sha512; protocol="application/pgp-signature"
Date: Thu, 29 Oct 2020 18:12:52 -0400
Message-ID: <4858.1604009572@localhost>
Archived-At: <https://mailarchive.ietf.org/arch/msg/emu/3EUJ8j_6QwftAZg6y3nPzDX5YaA>
Subject: Re: [Emu] Consensus Call on OCSP usage in draft-ietf-emu-eap-tls13-11
X-BeenThere: emu@ietf.org
X-Mailman-Version: 2.1.29
Precedence: list
List-Id: "EAP Methods Update \(EMU\)" <emu.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/emu>, <mailto:emu-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/emu/>
List-Post: <mailto:emu@ietf.org>
List-Help: <mailto:emu-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/emu>, <mailto:emu-request@ietf.org?subject=subscribe>
X-List-Received-Date: Thu, 29 Oct 2020 22:12:57 -0000

--=-=-=
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: quoted-printable


Joseph Salowey <joe@salowey.net> wrote:
    > 2. Require Servers to Implement and Recommended to Use OCSP with text
    > similar to the following:

I don't think that this text is quite right.

I note that "RECOMMENDED" is a synonym for SHOULD, and usually we ask
documents to explain what a reasonable exception might look like.
This text does not do that.

    > =E2=80=9CEAP-TLS servers supporting TLS 1.3 MUST implement Certificat=
e Status
    > Requests (OCSP stapling) as specified in Section 4.4.2.1 of [RFC8446]=
.  It
    > is RECOMMENDED that EAP-TLS peers and servers use OCSP stapling for
    > verifying the status of server certificates as specified in Section 4=
.4.2.1
    > of [RFC8446]. When an EAP-TLS peer uses OCSP to verify the certificate
    > status of the EAP-TLS server, it MUST use Certificate Status Requests=
 for
    > the server's certificate chain and it MUST treat a CertificateEntry (=
except
    > the trust anchor) without a valid CertificateStatus extension as inva=
lid
    > and abort the handshake with an appropriate alert.=E2=80=9C

I suggest:

=E2=80=9CEAP-TLS servers supporting TLS 1.3 that use OCSP to do certificate
recovation checks,  MUST implement Certificate Status Requests using OCSP
stapling as specified in Section 4.4.2.1 of [RFC8446].

It is RECOMMENDED that EAP-TLS peers and servers use OCSP (with stapling) f=
or
verifying the status of server certificates as specified in Section 4.4.2.1
of [RFC8446].
<MCR: BUT, I think that section 4.4.2.1 is not where certificate status is
mandated for TLS. I can't find the right place>

When an EAP-TLS peer uses OCSP to verify the certificate status of the
EAP-TLS server, it MUST use Certificate Status Requests for the server's
certificate chain and it MUST treat a CertificateEntry (except the trust
anchor) without a valid CertificateStatus extension as invalid and abort the
handshake with an appropriate alert.=E2=80=9C

I don't know much about the last part.
I suggest it be split as three paragraphs for readability.

=2D-
Michael Richardson <mcr+IETF@sandelman.ca>   . o O ( IPv6 I=C3=B8T consulti=
ng )
           Sandelman Software Works Inc, Ottawa and Worldwide

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

-----BEGIN PGP SIGNATURE-----

iQEzBAEBCgAdFiEEbsyLEzg/qUTA43uogItw+93Q3WUFAl+bPmQACgkQgItw+93Q
3WVUPwf/dWrpfvBMNX3xv5wQdrlpFsgYRfy5ajIj3n+/3q69d2dv5xOW7K0aMVeo
qX4byaWvu3L+/ObDiSGcPvuvc0FV4iXIGUDYgnHOzdCin5nyZbN6nWL7O2HjPouw
fNqwch+v8QPSt/28p0E142kwZdU8wMrxNN2ZMI7z5USyT7tf15CL10ZAP0mWqr4P
VindeSnViqoG28dtA3fU2wW/5Z/WfHgDz8iFk+o0AH3y79aNdGueXfdd6sYakC66
uefkUf04IQSRRqQnxGgz1FnO7u4H4k2bGc2zz0a+RcHwrybsMHv6uN2Up/4ksiYW
+w5+6fCUhJGBNgQguYbFyC8Tmv8FWQ==
=TcFX
-----END PGP SIGNATURE-----
--=-=-=--


From nobody Thu Oct 29 16:13:04 2020
Return-Path: <noreply@ietf.org>
X-Original-To: emu@ietf.org
Delivered-To: emu@ietfa.amsl.com
Received: from ietfa.amsl.com (localhost [IPv6:::1]) by ietfa.amsl.com (Postfix) with ESMTP id D90363A09D1; Thu, 29 Oct 2020 16:13:02 -0700 (PDT)
MIME-Version: 1.0
Content-Type: text/plain; charset="utf-8"
Content-Transfer-Encoding: 7bit
From: Stefan Santesson via Datatracker <noreply@ietf.org>
To: <secdir@ietf.org>
Cc: last-call@ietf.org, draft-ietf-emu-eaptlscert.all@ietf.org, emu@ietf.org
X-Test-IDTracker: no
X-IETF-IDTracker: 7.21.0
Auto-Submitted: auto-generated
Precedence: bulk
Message-ID: <160401318284.11167.6795105917637378641@ietfa.amsl.com>
Reply-To: Stefan Santesson <stefan@aaa-sec.com>
Date: Thu, 29 Oct 2020 16:13:02 -0700
Archived-At: <https://mailarchive.ietf.org/arch/msg/emu/8Ed6bWcR6AJj8DTYC76c8Qm5bhE>
Subject: [Emu] Secdir last call review of draft-ietf-emu-eaptlscert-06
X-BeenThere: emu@ietf.org
X-Mailman-Version: 2.1.29
List-Id: "EAP Methods Update \(EMU\)" <emu.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/emu>, <mailto:emu-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/emu/>
List-Post: <mailto:emu@ietf.org>
List-Help: <mailto:emu-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/emu>, <mailto:emu-request@ietf.org?subject=subscribe>
X-List-Received-Date: Thu, 29 Oct 2020 23:13:03 -0000

Reviewer: Stefan Santesson
Review result: Has Nits

The document in general is good and well written.

Some nits needs attention before publication as the general review also points
out. Ex in the abstract "This document looks at the this problem"

Some abbreviations needs to be spelled out at first usage, such as MTU (Maximum
Transmission Unit)

On the content itself I have two questions:

- Wouldn't it be relevant to also discuss the risks with regard to introduction
of quantum safe crypto, if that leads to significantly increased key sizes? It
could be troublesome if transition to a safer crypto is made impossible due to
size limitations. - Would it be relevant to discuss usage of AIA extension as
means of possibly excluding intermediary certs from the path as they could be
located using AIA?

Finally, I agree with the general review that this document reference quite
some work in progress. If this document is to be published before these
referenced works are concluded, are there alternatives to make the same point?




From nobody Thu Oct 29 20:04:34 2020
Return-Path: <kaduk@mit.edu>
X-Original-To: emu@ietfa.amsl.com
Delivered-To: emu@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 03CC33A0D67; Thu, 29 Oct 2020 20:04:28 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.897
X-Spam-Level: 
X-Spam-Status: No, score=-1.897 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RCVD_IN_MSPIKE_H4=0.001, RCVD_IN_MSPIKE_WL=0.001, SPF_HELO_NONE=0.001, SPF_PASS=-0.001, URIBL_BLOCKED=0.001] autolearn=ham autolearn_force=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 qZ5si9zKwcLc; Thu, 29 Oct 2020 20:04:26 -0700 (PDT)
Received: from outgoing.mit.edu (outgoing-auth-1.mit.edu [18.9.28.11]) (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 465C33A0D66; Thu, 29 Oct 2020 20:04:25 -0700 (PDT)
Received: from kduck.mit.edu ([24.16.140.251]) (authenticated bits=56) (User authenticated as kaduk@ATHENA.MIT.EDU) by outgoing.mit.edu (8.14.7/8.12.4) with ESMTP id 09U34F8w028039 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-GCM-SHA384 bits=256 verify=NOT); Thu, 29 Oct 2020 23:04:20 -0400
Date: Thu, 29 Oct 2020 20:04:15 -0700
From: Benjamin Kaduk <kaduk@mit.edu>
To: Stefan Santesson <stefan@aaa-sec.com>
Cc: secdir@ietf.org, last-call@ietf.org, draft-ietf-emu-eaptlscert.all@ietf.org, emu@ietf.org
Message-ID: <20201030030415.GE39170@kduck.mit.edu>
References: <160401318284.11167.6795105917637378641@ietfa.amsl.com>
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
In-Reply-To: <160401318284.11167.6795105917637378641@ietfa.amsl.com>
Archived-At: <https://mailarchive.ietf.org/arch/msg/emu/5d39BW8LDjZlZ3KK1Yjie0L07Ls>
Subject: Re: [Emu] Secdir last call review of draft-ietf-emu-eaptlscert-06
X-BeenThere: emu@ietf.org
X-Mailman-Version: 2.1.29
Precedence: list
List-Id: "EAP Methods Update \(EMU\)" <emu.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/emu>, <mailto:emu-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/emu/>
List-Post: <mailto:emu@ietf.org>
List-Help: <mailto:emu-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/emu>, <mailto:emu-request@ietf.org?subject=subscribe>
X-List-Received-Date: Fri, 30 Oct 2020 03:04:28 -0000

Hi Stefan,

Thanks for the review; it raises some good topics.
Replying on a couple points...

On Thu, Oct 29, 2020 at 04:13:02PM -0700, Stefan Santesson via Datatracker wrote:
> Reviewer: Stefan Santesson
> Review result: Has Nits
> 
> The document in general is good and well written.
> 
> Some nits needs attention before publication as the general review also points
> out. Ex in the abstract "This document looks at the this problem"
> 
> Some abbreviations needs to be spelled out at first usage, such as MTU (Maximum
> Transmission Unit)

MTU may actually be okay; per
https://www.rfc-editor.org/materials/abbrev.expansion.txt it is marked as
"well-known" and does not always need to be expanded.

> On the content itself I have two questions:
> 
> - Wouldn't it be relevant to also discuss the risks with regard to introduction
> of quantum safe crypto, if that leads to significantly increased key sizes? It
> could be troublesome if transition to a safer crypto is made impossible due to
> size limitations. - Would it be relevant to discuss usage of AIA extension as
> means of possibly excluding intermediary certs from the path as they could be
> located using AIA?
> 
> Finally, I agree with the general review that this document reference quite
> some work in progress. If this document is to be published before these
> referenced works are concluded, are there alternatives to make the same point?

They seem to mostly be informative references, and so would not require us
to hold publication of this document.  It is probably still worth
considering if there are alternatives anyway, though.

-Ben


From nobody Thu Oct 29 21:26:46 2020
Return-Path: <joe@salowey.net>
X-Original-To: emu@ietfa.amsl.com
Delivered-To: emu@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 5489F3A00E3 for <emu@ietfa.amsl.com>; Thu, 29 Oct 2020 21:26:44 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.898
X-Spam-Level: 
X-Spam-Status: No, score=-1.898 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, HTML_MESSAGE=0.001, SPF_HELO_NONE=0.001, SPF_PASS=-0.001, URIBL_BLOCKED=0.001] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (2048-bit key) header.d=salowey-net.20150623.gappssmtp.com
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 ZYBukdOiBydj for <emu@ietfa.amsl.com>; Thu, 29 Oct 2020 21:26:42 -0700 (PDT)
Received: from mail-qk1-x731.google.com (mail-qk1-x731.google.com [IPv6:2607:f8b0:4864:20::731]) (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 8B17A3A00D9 for <emu@ietf.org>; Thu, 29 Oct 2020 21:26:42 -0700 (PDT)
Received: by mail-qk1-x731.google.com with SMTP id a64so489570qkc.5 for <emu@ietf.org>; Thu, 29 Oct 2020 21:26:42 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=salowey-net.20150623.gappssmtp.com; s=20150623; h=mime-version:references:in-reply-to:from:date:message-id:subject:to :cc; bh=6gkfqFfF52XAJGjIHXlrgETEB8qpu9xGBCQ/aRxLvNU=; b=bFU/0gQQVKRd8IU8ets51644ufgnE3f5XGHb2A1JgWtanpjjk+C+alAzUY/hhC/rmz BnzvAwQmZ0FuCf2fQOnERMWIvQMlZBbFKj4YrkD4h4q1ivgrMTYJ8IofweuFNfIw/zCU 9sTqC6tYAwf4JfSI+Wkmmfga/FUm7lUAftvBw8H90RSO3uJHe5k3PlfOeebRldPEkG4b 7lKjlfHl0Uncm+Sm1sMLmk9icm28ZjJCOiELIck4phyL5/6mdnwiYnRb1suL3F4ergjZ /rPfBtIXDb1VibyfBgAvAO7Et6fc/mNHSYiCP3eBUxjsFZ/Lj9ZyhQoGPEdxJwrCA3RC BDTg==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:mime-version:references:in-reply-to:from:date :message-id:subject:to:cc; bh=6gkfqFfF52XAJGjIHXlrgETEB8qpu9xGBCQ/aRxLvNU=; b=G6AblU6Qu0Y5FjhFXKuFR51L4Qc+6ij3YWBXRmsDx3Uh5Jazbq4vYyoWTQef7n3w9s I2IGrO5Q+mZgWuBG2O+wglUFkQyMEmi4xT9A4KqZytYaTcwDJ2Buz6Ry5OjOF8Ew4v4v roJpmeiyjY/Hk37+jtwRBpgI07TOsXdgCxk8boLms9fYrarnUeviAGqogoXEuH2C1T1R Fvq0JgkWnKkSEEAIcsGnJwH9smFB2wbRirtnku9UI8V4b/oC9z4ez4/HvEF7CmBv9EIv wFeevKNKPTolNRNOHqYuaxf7OLcFsK/D8Vup2DVoZf+uu7YkRE0oleIySsPY0msJwdjr ycHg==
X-Gm-Message-State: AOAM532Er7bGXaMacB8M4taczP9a3yPsPotZYnLDUy/iOYDwypqQbvdC H4VGWd2yT/RJYprcjl8u/UZyB3VFKsW1jw/y+ygNq52/Lv/4bQ==
X-Google-Smtp-Source: ABdhPJxtdrWigU2ndA1YocdK8qeI39cDBro6iTf5EVrLLUEM/Ah4nahqbwVj4bUiKwplJfMI8UNnhh1OODUJLAsWXHE=
X-Received: by 2002:a37:a0d7:: with SMTP id j206mr446289qke.375.1604032001438;  Thu, 29 Oct 2020 21:26:41 -0700 (PDT)
MIME-Version: 1.0
References: <CAOgPGoDbsunLOxrnFxa8uMxG6JYObX_r5VLOvVib5QmFHGOrwA@mail.gmail.com> <4858.1604009572@localhost>
In-Reply-To: <4858.1604009572@localhost>
From: Joseph Salowey <joe@salowey.net>
Date: Thu, 29 Oct 2020 21:26:30 -0700
Message-ID: <CAOgPGoDC8gyBLD4a7Ms-h823sZ5q6USpbE=6HXdVWo3TEVfoYA@mail.gmail.com>
To: Michael Richardson <mcr+ietf@sandelman.ca>
Cc: EMU WG <emu@ietf.org>
Content-Type: multipart/alternative; boundary="000000000000a787bc05b2dbcdfa"
Archived-At: <https://mailarchive.ietf.org/arch/msg/emu/BK8_ch3k5uJ_Uwz4luLrOi4k3Q0>
Subject: Re: [Emu] Consensus Call on OCSP usage in draft-ietf-emu-eap-tls13-11
X-BeenThere: emu@ietf.org
X-Mailman-Version: 2.1.29
Precedence: list
List-Id: "EAP Methods Update \(EMU\)" <emu.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/emu>, <mailto:emu-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/emu/>
List-Post: <mailto:emu@ietf.org>
List-Help: <mailto:emu-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/emu>, <mailto:emu-request@ietf.org?subject=subscribe>
X-List-Received-Date: Fri, 30 Oct 2020 04:26:44 -0000

--000000000000a787bc05b2dbcdfa
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable

On Thu, Oct 29, 2020 at 3:12 PM Michael Richardson <mcr+ietf@sandelman.ca>
wrote:

>
> Joseph Salowey <joe@salowey.net> wrote:
>     > 2. Require Servers to Implement and Recommended to Use OCSP with te=
xt
>     > similar to the following:
>
> I don't think that this text is quite right.
>
> I note that "RECOMMENDED" is a synonym for SHOULD, and usually we ask
> documents to explain what a reasonable exception might look like.
> This text does not do that.
>
>     > =E2=80=9CEAP-TLS servers supporting TLS 1.3 MUST implement Certific=
ate Status
>     > Requests (OCSP stapling) as specified in Section 4.4.2.1 of
> [RFC8446].  It
>     > is RECOMMENDED that EAP-TLS peers and servers use OCSP stapling for
>     > verifying the status of server certificates as specified in Section
> 4.4.2.1
>     > of [RFC8446]. When an EAP-TLS peer uses OCSP to verify the
> certificate
>     > status of the EAP-TLS server, it MUST use Certificate Status
> Requests for
>     > the server's certificate chain and it MUST treat a CertificateEntry
> (except
>     > the trust anchor) without a valid CertificateStatus extension as
> invalid
>     > and abort the handshake with an appropriate alert.=E2=80=9C
>
> I suggest:
>
> =E2=80=9CEAP-TLS servers supporting TLS 1.3 that use OCSP to do certifica=
te
> recovation checks,  MUST implement Certificate Status Requests using OCSP
> stapling as specified in Section 4.4.2.1 of [RFC8446].
>
> It is RECOMMENDED that EAP-TLS peers and servers use OCSP (with stapling)
> for
> verifying the status of server certificates as specified in Section 4.4.2=
.1
> of [RFC8446].
> <MCR: BUT, I think that section 4.4.2.1 is not where certificate status i=
s
> mandated for TLS. I can't find the right place>
>
> When an EAP-TLS peer uses OCSP to verify the certificate status of the
> EAP-TLS server, it MUST use Certificate Status Requests for the server's
> certificate chain and it MUST treat a CertificateEntry (except the trust
> anchor) without a valid CertificateStatus extension as invalid and abort
> the
> handshake with an appropriate alert.=E2=80=9C
>
> I don't know much about the last part.
> I suggest it be split as three paragraphs for readability.
>
>
[Joe] Thanks Michael,  I think your suggestion is a better way to phrase it


> --
> Michael Richardson <mcr+IETF@sandelman.ca>   . o O ( IPv6 I=C3=B8T consul=
ting )
>            Sandelman Software Works Inc, Ottawa and Worldwide
>

--000000000000a787bc05b2dbcdfa
Content-Type: text/html; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable

<div dir=3D"ltr"><div dir=3D"ltr"><br></div><br><div class=3D"gmail_quote">=
<div dir=3D"ltr" class=3D"gmail_attr">On Thu, Oct 29, 2020 at 3:12 PM Micha=
el Richardson &lt;<a href=3D"mailto:mcr%2Bietf@sandelman.ca">mcr+ietf@sande=
lman.ca</a>&gt; wrote:<br></div><blockquote class=3D"gmail_quote" style=3D"=
margin:0px 0px 0px 0.8ex;border-left:1px solid rgb(204,204,204);padding-lef=
t:1ex"><br>
Joseph Salowey &lt;<a href=3D"mailto:joe@salowey.net" target=3D"_blank">joe=
@salowey.net</a>&gt; wrote:<br>
=C2=A0 =C2=A0 &gt; 2. Require Servers to Implement and Recommended to Use O=
CSP with text<br>
=C2=A0 =C2=A0 &gt; similar to the following:<br>
<br>
I don&#39;t think that this text is quite right.<br>
<br>
I note that &quot;RECOMMENDED&quot; is a synonym for SHOULD, and usually we=
 ask<br>
documents to explain what a reasonable exception might look like.<br>
This text does not do that.<br>
<br>
=C2=A0 =C2=A0 &gt; =E2=80=9CEAP-TLS servers supporting TLS 1.3 MUST impleme=
nt Certificate Status<br>
=C2=A0 =C2=A0 &gt; Requests (OCSP stapling) as specified in Section 4.4.2.1=
 of [RFC8446].=C2=A0 It<br>
=C2=A0 =C2=A0 &gt; is RECOMMENDED that EAP-TLS peers and servers use OCSP s=
tapling for<br>
=C2=A0 =C2=A0 &gt; verifying the status of server certificates as specified=
 in Section 4.4.2.1<br>
=C2=A0 =C2=A0 &gt; of [RFC8446]. When an EAP-TLS peer uses OCSP to verify t=
he certificate<br>
=C2=A0 =C2=A0 &gt; status of the EAP-TLS server, it MUST use Certificate St=
atus Requests for<br>
=C2=A0 =C2=A0 &gt; the server&#39;s certificate chain and it MUST treat a C=
ertificateEntry (except<br>
=C2=A0 =C2=A0 &gt; the trust anchor) without a valid CertificateStatus exte=
nsion as invalid<br>
=C2=A0 =C2=A0 &gt; and abort the handshake with an appropriate alert.=E2=80=
=9C<br>
<br>
I suggest:<br>
<br>
=E2=80=9CEAP-TLS servers supporting TLS 1.3 that use OCSP to do certificate=
<br>
recovation checks,=C2=A0 MUST implement Certificate Status Requests using O=
CSP<br>
stapling as specified in Section 4.4.2.1 of [RFC8446].<br>
<br>
It is RECOMMENDED that EAP-TLS peers and servers use OCSP (with stapling) f=
or<br>
verifying the status of server certificates as specified in Section 4.4.2.1=
<br>
of [RFC8446].<br>
&lt;MCR: BUT, I think that section 4.4.2.1 is not where certificate status =
is<br>
mandated for TLS. I can&#39;t find the right place&gt;<br>
<br>
When an EAP-TLS peer uses OCSP to verify the certificate status of the<br>
EAP-TLS server, it MUST use Certificate Status Requests for the server&#39;=
s<br>
certificate chain and it MUST treat a CertificateEntry (except the trust<br=
>
anchor) without a valid CertificateStatus extension as invalid and abort th=
e<br>
handshake with an appropriate alert.=E2=80=9C<br>
<br>
I don&#39;t know much about the last part.<br>
I suggest it be split as three paragraphs for readability.<br>
<br></blockquote><div><br></div><div>[Joe] Thanks Michael,=C2=A0 I think yo=
ur suggestion is a better way to phrase it=C2=A0</div><div>=C2=A0</div><blo=
ckquote class=3D"gmail_quote" style=3D"margin:0px 0px 0px 0.8ex;border-left=
:1px solid rgb(204,204,204);padding-left:1ex">
--<br>
Michael Richardson &lt;<a href=3D"mailto:mcr%2BIETF@sandelman.ca" target=3D=
"_blank">mcr+IETF@sandelman.ca</a>&gt;=C2=A0 =C2=A0. o O ( IPv6 I=C3=B8T co=
nsulting )<br>
=C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0Sandelman Software Works Inc, Otta=
wa and Worldwide<br>
</blockquote></div></div>

--000000000000a787bc05b2dbcdfa--


From nobody Thu Oct 29 22:05:49 2020
Return-Path: <joe@salowey.net>
X-Original-To: emu@ietfa.amsl.com
Delivered-To: emu@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id CC1963A08AF for <emu@ietfa.amsl.com>; Thu, 29 Oct 2020 22:05:47 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.888
X-Spam-Level: 
X-Spam-Status: No, score=-1.888 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, HTML_MESSAGE=0.001, SPF_HELO_NONE=0.001, SPF_PASS=-0.001, T_KAM_HTML_FONT_INVALID=0.01, URIBL_BLOCKED=0.001] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (2048-bit key) header.d=salowey-net.20150623.gappssmtp.com
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 ezApt2I4ZMXQ for <emu@ietfa.amsl.com>; Thu, 29 Oct 2020 22:05:46 -0700 (PDT)
Received: from mail-qk1-x734.google.com (mail-qk1-x734.google.com [IPv6:2607:f8b0:4864:20::734]) (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 DAE043A0876 for <emu@ietf.org>; Thu, 29 Oct 2020 22:05:45 -0700 (PDT)
Received: by mail-qk1-x734.google.com with SMTP id k9so3901132qki.6 for <emu@ietf.org>; Thu, 29 Oct 2020 22:05:45 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=salowey-net.20150623.gappssmtp.com; s=20150623; h=mime-version:from:date:message-id:subject:to; bh=QWMa8sVkZ9qZQBEgfAbuO6EOSsg7GwyA1vkKg9nMO4U=; b=Q1M61m+i/Ux6H5CPrF2IlB3HZQ7dB6ahQ/N4o7/dJEUdq+RIcw72D6LMIe6dbU4AMl VP7M22cdAlWaQYucHYCIyPYYKkgdaId19XjTDQdlzHLNu8qWYdNy7oyKmv86Xol+x3UL ttDneqyUWV1RkQnImusKpStpNlpYuJJQCuIsSk32GhGNglCzd6kaFlwOOQTeu93KCy44 avlpBmIzK/DZCrYAix73v/049JLvyVXAy9lb/8OTKBLlatcQhThV2MdgLXzYDhZqSgPS VKA+lkvgqk3W+riCQRbjthHSLdCCDpnTUwnTSd/J1vv7lCPhW9QZDH3ZFfjtbRqPWT6P gmaA==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:mime-version:from:date:message-id:subject:to; bh=QWMa8sVkZ9qZQBEgfAbuO6EOSsg7GwyA1vkKg9nMO4U=; b=lmZpCy0I2O43vgmojUzvdAPjCuM+cDFIu+aQgx4057StfH5JS+L6eN3Hf8pQ6P7sAU 9AifcFFK1ENntkI8oBfvdY3m24YhsoNs6Qoz1XPI+i09HugycHOVmE3CsewKz9VRlERm XzI716Z+4Jfd+aEvWJx2bCsEb2LANMRr5RV8I35kKYn6ddZmkSU+86c+jAuTR3ZMnK3Z sAjPIUxGg4hvuwjM+Tbqvvdjgjnw8K2vrrLUQ4GKXVzKxjSlBNuynxOPAYd2hu/2G2yY jTX01Ka+BAr/iBS1A6nVZfcA7zwIshnX8anw9dQLmfEB2ErqV0wDgnxFgV7hrFxS6/Jv uAfw==
X-Gm-Message-State: AOAM533acXT6q1YSN9SgWrM3Y5yLOk1Qjaxd9fo96Rt99yGlb2LgPnHV y2hiBjs7wqQU1SBk9O9DdoETlIln3zYd0cAU8E1KUHTbHiIy6k+N
X-Google-Smtp-Source: ABdhPJy/S9NrPh/PejrSIJ6JIypyr/tixgY4cHrDegXnsVzuDu7ARYaNvjQJ8P8j8h2RRxHaRkfVSmSo5JAWbZ1lt4k=
X-Received: by 2002:a37:a0d7:: with SMTP id j206mr521983qke.375.1604034344739;  Thu, 29 Oct 2020 22:05:44 -0700 (PDT)
MIME-Version: 1.0
From: Joseph Salowey <joe@salowey.net>
Date: Thu, 29 Oct 2020 22:05:34 -0700
Message-ID: <CAOgPGoAsJTEMWEY46enq2=V3Gqb4SzOgYvv6g8TeijGYYXB9og@mail.gmail.com>
To: EMU WG <emu@ietf.org>
Content-Type: multipart/alternative; boundary="00000000000053743e05b2dc59e3"
Archived-At: <https://mailarchive.ietf.org/arch/msg/emu/R5uypu9Kna8vTpyV5BlIXDm-Mdk>
Subject: [Emu] Revised resolution for TEAP erratum 5127
X-BeenThere: emu@ietf.org
X-Mailman-Version: 2.1.29
Precedence: list
List-Id: "EAP Methods Update \(EMU\)" <emu.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/emu>, <mailto:emu-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/emu/>
List-Post: <mailto:emu@ietf.org>
List-Help: <mailto:emu-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/emu>, <mailto:emu-request@ietf.org?subject=subscribe>
X-List-Received-Date: Fri, 30 Oct 2020 05:05:48 -0000

--00000000000053743e05b2dc59e3
Content-Type: text/plain; charset="UTF-8"

I think this erratum is done. I've also started a GH repo to track the
changes in the document which might help show them in context a bit better.
The PR for this issue is https://github.com/emu-wg/teap-errata/pull/2.
Please post here or comment on the PR if you think this needs any
additional work.

Errata 5127: https://www.rfc-editor.org/errata/eid5127
Proposed State: Verified
Revision: https://github.com/emu-wg/teap-errata/pull/2
Section 5.2 says

 IMSK = First 32 octets of TLS-PRF(EMSK, "TEAPbindkey@ietf.org" |
 "\0" | 64)

 where "|" denotes concatenation, EMSK is the EMSK from the inner
 method, "TEAPbindkey@ietf.org" consists the ASCII value for the
 label "TEAPbindkey@ietf.org" (without quotes), "\0" = is a NULL
 octet (0x00 in hex), length is the 2-octet unsigned integer in
 network byte order, and TLS-PRF is the PRF negotiated as part of
 TLS handshake [RFC5246].

It should say:

 IMSK = First 32 octets of TLS-PRF(EMSK, "TEAPbindkey@ietf.org",
 0x00 | 0x00 | 0x40)

 where "|" denotes concatenation and the TLS-PRF is defined in
 [RFC5246] as

 PRF(secret, label, seed) = P_<hash>(secret, label | seed).

 the secret is the EMSK from the inner method, the label is
 "TEAPbindkey@ietf.org" consisting of the ASCII value for the
 label "TEAPbindkey@ietf.org" (without quotes),  the seed
 consists of the "\0" null delimiter (0x00) and 2-octet unsigned
 integer length in network byte order (0x00 | 0x4) specified
 in [RFC5295].

Notes:

RFC5246 The Transport Layer Security (TLS) Protocol Version 1.2
5. HMAC and the Pseudorandom Function

"TLS's PRF is created by applying P_<hash> to the secret as:

PRF(secret, label, seed) = P_<hash>(secret, label + seed)"

In this case the seed is the 2-byte length of the output as defined by RFC
5295. In terms of P_ the derivation would look like:

IMSK = P_<hash>(EMSK, "TEAPbindkey@ietf.org" | 0x00 | 0x00 | 0x40)

--00000000000053743e05b2dc59e3
Content-Type: text/html; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable

<div dir=3D"ltr"><div>I think this erratum is done. I&#39;ve also started a=
 GH repo to track the changes in the document which might help show them in=
 context a bit better. The PR for this issue is=C2=A0<a href=3D"https://git=
hub.com/emu-wg/teap-errata/pull/2">https://github.com/emu-wg/teap-errata/pu=
ll/2</a>.=C2=A0 Please post here or comment on the PR if you think this nee=
ds any additional work.=C2=A0=C2=A0</div><div><br></div>Errata 5127:=C2=A0<=
a href=3D"https://www.rfc-editor.org/errata/eid5127" target=3D"_blank">http=
s://www.rfc-editor.org/errata/eid5127</a><div></div><div>Proposed State: Ve=
rified</div><div>Revision:=C2=A0<a href=3D"https://github.com/emu-wg/teap-e=
rrata/pull/2">https://github.com/emu-wg/teap-errata/pull/2</a></div>Section=
 5.2 says<br><br>=C2=A0IMSK =3D First 32 octets of TLS-PRF(EMSK, &quot;<a h=
ref=3D"mailto:TEAPbindkey@ietf.org">TEAPbindkey@ietf.org</a>&quot; |<br>=C2=
=A0&quot;\0&quot; | 64)<br><br>=C2=A0where &quot;|&quot; denotes concatenat=
ion, EMSK is the EMSK from the inner<br>=C2=A0method, &quot;<a href=3D"mail=
to:TEAPbindkey@ietf.org">TEAPbindkey@ietf.org</a>&quot; consists the ASCII =
value for the<br>=C2=A0label &quot;<a href=3D"mailto:TEAPbindkey@ietf.org">=
TEAPbindkey@ietf.org</a>&quot; (without quotes), &quot;\0&quot; =3D is a NU=
LL<br>=C2=A0octet (0x00 in hex), length is the 2-octet unsigned integer in<=
br>=C2=A0network byte order, and TLS-PRF is the PRF negotiated as part of<b=
r>=C2=A0TLS handshake [RFC5246].<div><br></div><div>It should say:</div><br=
>=C2=A0IMSK =3D First 32 octets of TLS-PRF(EMSK, &quot;<a href=3D"mailto:TE=
APbindkey@ietf.org">TEAPbindkey@ietf.org</a>&quot;,<br>=C2=A00x00 | 0x00 | =
0x40)<div><br>=C2=A0where &quot;|&quot; denotes concatenation and the TLS-P=
RF is defined in<br>=C2=A0[RFC5246] as <br>=C2=A0<br>=C2=A0PRF(secret, labe=
l, seed) =3D P_&lt;hash&gt;(secret, label | seed).<br><br>=C2=A0the secret =
is the EMSK from the inner method, the label is <br>=C2=A0&quot;<a href=3D"=
mailto:TEAPbindkey@ietf.org">TEAPbindkey@ietf.org</a>&quot; consisting of t=
he ASCII value for the<br>=C2=A0label &quot;<a href=3D"mailto:TEAPbindkey@i=
etf.org">TEAPbindkey@ietf.org</a>&quot; (without quotes), =C2=A0the seed <b=
r>=C2=A0consists of the &quot;\0&quot; null delimiter (0x00) and 2-octet un=
signed <br>=C2=A0integer length in network byte order (0x00 | 0x4) specifie=
d <br>=C2=A0in [RFC5295].</div><div><br></div><div>Notes:=C2=A0</div><div><=
br></div><div><p style=3D"box-sizing:border-box;margin-top:0px;margin-botto=
m:16px;color:rgb(36,41,46);font-family:-apple-system,system-ui,&quot;Segoe =
UI&quot;,Helvetica,Arial,sans-serif,&quot;Apple Color Emoji&quot;,&quot;Seg=
oe UI Emoji&quot;;font-size:14px">RFC5246 The Transport Layer Security (TLS=
) Protocol Version 1.2<br style=3D"box-sizing:border-box">5. HMAC and the P=
seudorandom Function</p><blockquote style=3D"box-sizing:border-box;margin:0=
px 0px 16px;padding:0px 1em;font-family:-apple-system,system-ui,&quot;Segoe=
 UI&quot;,Helvetica,Arial,sans-serif,&quot;Apple Color Emoji&quot;,&quot;Se=
goe UI Emoji&quot;;font-size:14px"><p style=3D"box-sizing:border-box;margin=
-top:0px;margin-bottom:16px">&quot;TLS&#39;s PRF is created by applying P_&=
lt;hash&gt; to the secret as:</p><p style=3D"box-sizing:border-box;margin-t=
op:0px;margin-bottom:0px">PRF(secret, label, seed) =3D P_&lt;hash&gt;(secre=
t, label + seed)&quot;</p></blockquote><p style=3D"box-sizing:border-box;ma=
rgin-top:0px;margin-bottom:16px;color:rgb(36,41,46);font-family:-apple-syst=
em,system-ui,&quot;Segoe UI&quot;,Helvetica,Arial,sans-serif,&quot;Apple Co=
lor Emoji&quot;,&quot;Segoe UI Emoji&quot;;font-size:14px">In this case the=
 seed is the 2-byte length of the output as defined by RFC 5295. In terms o=
f P_ the derivation would look like:</p><p style=3D"box-sizing:border-box;m=
argin-top:0px;color:rgb(36,41,46);font-family:-apple-system,system-ui,&quot=
;Segoe UI&quot;,Helvetica,Arial,sans-serif,&quot;Apple Color Emoji&quot;,&q=
uot;Segoe UI Emoji&quot;;font-size:14px;margin-bottom:0px">IMSK =3D P_&lt;h=
ash&gt;(EMSK, &quot;<a href=3D"mailto:TEAPbindkey@ietf.org" style=3D"box-si=
zing:border-box;background-color:initial;text-decoration-line:none">TEAPbin=
dkey@ietf.org</a>&quot; | 0x00 | 0x00 | 0x40)</p></div></div>

--00000000000053743e05b2dc59e3--


From nobody Thu Oct 29 22:43:44 2020
Return-Path: <joe@salowey.net>
X-Original-To: emu@ietfa.amsl.com
Delivered-To: emu@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 4BAE43A09F6 for <emu@ietfa.amsl.com>; Thu, 29 Oct 2020 22:43:41 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.898
X-Spam-Level: 
X-Spam-Status: No, score=-1.898 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, HTML_MESSAGE=0.001, SPF_HELO_NONE=0.001, SPF_PASS=-0.001, URIBL_BLOCKED=0.001] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (2048-bit key) header.d=salowey-net.20150623.gappssmtp.com
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 DvXNlEcKGDuN for <emu@ietfa.amsl.com>; Thu, 29 Oct 2020 22:43:39 -0700 (PDT)
Received: from mail-qt1-x830.google.com (mail-qt1-x830.google.com [IPv6:2607:f8b0:4864:20::830]) (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 79BC83A09F0 for <emu@ietf.org>; Thu, 29 Oct 2020 22:43:39 -0700 (PDT)
Received: by mail-qt1-x830.google.com with SMTP id c5so3400519qtw.3 for <emu@ietf.org>; Thu, 29 Oct 2020 22:43:39 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=salowey-net.20150623.gappssmtp.com; s=20150623; h=mime-version:from:date:message-id:subject:to; bh=M+8SaUh0wbvxGS+ZUZsleWYB877KMjmPi4ENZIYQ2z4=; b=QE46fu8iN6BDAsggvhNED5Qv5G6hFc3p5rVh2Wn5Dxsl0D4xMf6mvxlrRpIOJVPmej qmA+8Tjnpkofty6bHNv739bEiIduTSraEqjSnZJt1dnxASAl0mY+CSeNUynHd5W+wGvg Ng/ROodL6DQIcnSO3MeJteFQn5rqWYcc4zRoHOBKKKQyUoeliUMTcQny7VWgBJ3FdOrB fF06fpyGq8EuPNgpIEZL0LBkagASGLrLByFEx32FiDWAKVZXX/oyVktx/lml3SrsYSyP Y1PMK8fEbR3V8kI3e1bK97BypD2j8wudMGfR+TnpKzpt9mX63alMRXvexD8J1sX1hbHd OVWA==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:mime-version:from:date:message-id:subject:to; bh=M+8SaUh0wbvxGS+ZUZsleWYB877KMjmPi4ENZIYQ2z4=; b=io4IJaMhZFBcZKAmTzsdUA0eSQss5/lcVFBD5bY+TwveBhXv8dKOJxauY2XZmZruCi RGqy1IUTGNYEHWz49hcgRlZtYXX98alK+wMTvjx5mzpPm5B91aWLBJqSQQVVdDIE0zFG OYnLCOSHWb08dxW51HIRsHHg40Q7/PSrM1oG3600TlzwzDLu0MSegNgURZV5FDG8Krvh CULLrgroyB6fqbs8L+NcsAJG/gNtBEGc+SURKr768ydmT46kzUh6WYKJkWSbd1TpKkrV R5a4FCNMV4sduAKmotLkgaVeD/B7oJ9dEjW0zV7ZLYXjnTVkJ4nZXlHe/a8Fm/SYrsz1 jfoA==
X-Gm-Message-State: AOAM530zUnURQBiOl2CpY5VUMDeYFFL6pdC/UyitK/0alxzx6DHbUtJp jWYRrYpLbz8RC5idNrHm1AOpHsqzYEqvYJ+bKdnGQxWvogjPRSMN
X-Google-Smtp-Source: ABdhPJxr4fOnyDtVnFLkymeYX5tqldo/Ll0U1jDF7SMOUH09GOscWrkAk8UiMJ43aLPfWoHQNCHs6wzI87ncplepdnA=
X-Received: by 2002:ac8:120a:: with SMTP id x10mr566484qti.95.1604036618202; Thu, 29 Oct 2020 22:43:38 -0700 (PDT)
MIME-Version: 1.0
From: Joseph Salowey <joe@salowey.net>
Date: Thu, 29 Oct 2020 22:43:27 -0700
Message-ID: <CAOgPGoCzw2L5jx8YL-1Vu=n=tjpUogHabwXU5Zhv8Tf_VvrCQQ@mail.gmail.com>
To: EMU WG <emu@ietf.org>
Content-Type: multipart/alternative; boundary="000000000000d5c27f05b2dce0b3"
Archived-At: <https://mailarchive.ietf.org/arch/msg/emu/fYBuPgWa7xiH7JmoHfP5yrU7HV0>
Subject: [Emu] Revised resolution for Erratum 5128
X-BeenThere: emu@ietf.org
X-Mailman-Version: 2.1.29
Precedence: list
List-Id: "EAP Methods Update \(EMU\)" <emu.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/emu>, <mailto:emu-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/emu/>
List-Post: <mailto:emu@ietf.org>
List-Help: <mailto:emu-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/emu>, <mailto:emu-request@ietf.org?subject=subscribe>
X-List-Received-Date: Fri, 30 Oct 2020 05:43:41 -0000

--000000000000d5c27f05b2dce0b3
Content-Type: text/plain; charset="UTF-8"

I think this one is also done.  PR is here
https://github.com/emu-wg/teap-errata/pull/4.  Please comment on this
thread or PR if you think it still needs work:

Errata 5128: https://www.rfc-editor.org/errata/eid5128
Proposed State: Verified
Revision:

Section 5.2. says

 S-IMCK[0] = session_key_seed
  For j = 1 to n-1 do
       IMCK[j] = TLS-PRF(S-IMCK[j-1], "Inner Methods Compound Keys",
            IMSK[j], 60)
       S-IMCK[j] = first 40 octets of IMCK[j]
       CMK[j] = last 20 octets of IMCK[j]

where TLS-PRF is the PRF negotiated as part of TLS handshake [RFC5246].

It Should Say:

 S-IMCK[0] = session_key_seed
    For j = 1 to n-1 do
           IMCK[j] = the first 60 octets of TLS-PRF(S-IMCK[j-1],
              "Inner Methods Compound Keys", IMSK[j])
           S-IMCK[j] = first 40 octets of IMCK[j]
           CMK[j] = last 20 octets of IMCK[j]

    where "|" denotes concatenation and the TLS-PRF is defined in
    [RFC5246] as

        PRF(secret, label, seed) = P_<hash>(secret, label | seed).

    the secret is S-IMCK[j-1],  the label is
    "Inner Methods Compound Keys" consisting of the ASCII value for the
    label "Inner Methods Compound Keys" (without quotes),  the seed
    consists IMSK[j].

Section 5.4 Says:

  MSK  = TLS-PRF(S-IMCK[j], "Session Key Generating Function", 64)
  EMSK = TLS-PRF(S-IMCK[j],
       "Extended Session Key Generating Function", 64)

  where j is the number of the last successfully executed inner EAP method.

It should say:

      MSK = the first 64 octets of TLS-PRF(S-IMCK[j],
           "Session Key Generating Function")
      EMSK = the first 64 octets of TLS-PRF(S-IMCK[j],
           "Extended Session Key Generating Function")

      where "|" denotes concatenation and the TLS-PRF is defined in
      [RFC5246] as

        PRF(secret, label, seed) = P_<hash>(secret, label | seed).

     The secret is S-IMCK[j]  where j is the number of the last generated
     S-IMCK from section 5.2.  The label is is the ASCII value for the
     string without quotes.  The seed is empty (0 length) and omitted from
     the derivation.

Notes:

According to

RFC5246 The Transport Layer Security (TLS) Protocol Version 1.2

5. HMAC and the Pseudorandom Function

"TLS's PRF is created by applying P_hash to the secret as:

PRF(secret, label, seed) = P_<hash>(secret, label + seed)"

--000000000000d5c27f05b2dce0b3
Content-Type: text/html; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable

<div dir=3D"ltr">I think this one is also done.=C2=A0 PR is here=C2=A0<a hr=
ef=3D"https://github.com/emu-wg/teap-errata/pull/4">https://github.com/emu-=
wg/teap-errata/pull/4</a>.=C2=A0 Please comment on this thread or PR if you=
 think it still needs work:<div><br></div><div>Errata=C2=A0<span class=3D"g=
mail-il">5128</span>:=C2=A0<a href=3D"https://www.rfc-editor.org/errata/eid=
5128" target=3D"_blank">https://www.rfc-editor.org/errata/eid5128</a><div>P=
roposed State: Verified</div><div>Revision:</div><div><br></div><div>Sectio=
n 5.2. says</div></div><div><br></div>=C2=A0S-IMCK[0] =3D session_key_seed<=
br>=C2=A0 For j =3D 1 to n-1 do<br>=C2=A0 =C2=A0 =C2=A0 =C2=A0IMCK[j] =3D T=
LS-PRF(S-IMCK[j-1], &quot;Inner Methods Compound Keys&quot;,<br>=C2=A0 =C2=
=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 IMSK[j], 60)<br>=C2=A0 =C2=A0 =C2=A0 =C2=A0=
S-IMCK[j] =3D first 40 octets of IMCK[j]<br>=C2=A0 =C2=A0 =C2=A0 =C2=A0CMK[=
j] =3D last 20 octets of IMCK[j]<br><br>where TLS-PRF is the PRF negotiated=
 as part of TLS handshake [RFC5246].<div><br></div><div>It Should Say:</div=
><div><br></div>=C2=A0S-IMCK[0] =3D session_key_seed<br>=C2=A0 =C2=A0 For j=
 =3D 1 to n-1 do<br>=C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0IMCK[j] =3D th=
e first 60 octets of TLS-PRF(S-IMCK[j-1],<br>=C2=A0 =C2=A0 =C2=A0 =C2=A0 =
=C2=A0 =C2=A0 =C2=A0 &quot;Inner Methods Compound Keys&quot;, IMSK[j])<br>=
=C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0S-IMCK[j] =3D first 40 octets of I=
MCK[j]<br>=C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0CMK[j] =3D last 20 octet=
s of IMCK[j]<br>=C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0<br>=C2=A0 =C2=A0 =
where &quot;|&quot; denotes concatenation and the TLS-PRF is defined in<br>=
=C2=A0 =C2=A0 [RFC5246] as<br>=C2=A0 =C2=A0 =C2=A0<br>=C2=A0 =C2=A0 =C2=A0 =
=C2=A0 PRF(secret, label, seed) =3D P_&lt;hash&gt;(secret, label | seed).<b=
r><br>=C2=A0 =C2=A0 the secret is S-IMCK[j-1], =C2=A0the label is<br>=C2=A0=
 =C2=A0 &quot;Inner Methods Compound Keys&quot; consisting of the ASCII val=
ue for the<br>=C2=A0 =C2=A0 label &quot;Inner Methods Compound Keys&quot; (=
without quotes), =C2=A0the seed<br>=C2=A0 =C2=A0 consists IMSK[j]. <br><div=
><br></div><div>Section 5.4 Says:</div><div><br></div>=C2=A0 MSK =C2=A0=3D =
TLS-PRF(S-IMCK[j], &quot;Session Key Generating Function&quot;, 64)<br>=C2=
=A0 EMSK =3D TLS-PRF(S-IMCK[j],<br>=C2=A0 =C2=A0 =C2=A0 =C2=A0&quot;Extende=
d Session Key Generating Function&quot;, 64)<br><br>=C2=A0 where j is the n=
umber of the last successfully executed inner EAP method.<div><br></div><di=
v>It should say:</div><div><br>=C2=A0 =C2=A0 =C2=A0 MSK =3D the first 64 oc=
tets of TLS-PRF(S-IMCK[j],<br>=C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0&quo=
t;Session Key Generating Function&quot;)<br>=C2=A0 =C2=A0 =C2=A0 EMSK =3D t=
he first 64 octets of TLS-PRF(S-IMCK[j],<br>=C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=
=A0 =C2=A0&quot;Extended Session Key Generating Function&quot;)<br><br>=C2=
=A0 =C2=A0 =C2=A0 where &quot;|&quot; denotes concatenation and the TLS-PRF=
 is defined in<br>=C2=A0 =C2=A0 =C2=A0 [RFC5246] as<br>=C2=A0 =C2=A0 =C2=A0=
<br>=C2=A0 =C2=A0 =C2=A0 =C2=A0 PRF(secret, label, seed) =3D P_&lt;hash&gt;=
(secret, label | seed).<br><br>=C2=A0 =C2=A0 =C2=A0The secret is S-IMCK[j] =
=C2=A0where j is the number of the last generated<br>=C2=A0 =C2=A0 =C2=A0S-=
IMCK from section 5.2.=C2=A0 The label is is the ASCII value for the<br>=C2=
=A0 =C2=A0 =C2=A0string without quotes.=C2=A0 The seed is empty (0 length) =
and omitted from<br>=C2=A0 =C2=A0 =C2=A0the derivation.</div><div><br></div=
><div>Notes:=C2=A0=C2=A0</div><div><br></div><div>According to<br><br>RFC52=
46 The Transport Layer Security (TLS) Protocol Version 1.2<br><br>5. HMAC a=
nd the Pseudorandom Function<br><br>&quot;TLS&#39;s PRF is created by apply=
ing P_hash to the secret as:<br><br>PRF(secret, label, seed) =3D P_&lt;hash=
&gt;(secret, label + seed)&quot;<br></div></div>

--000000000000d5c27f05b2dce0b3--


From nobody Fri Oct 30 01:12:14 2020
Return-Path: <mohit.m.sethi@ericsson.com>
X-Original-To: emu@ietfa.amsl.com
Delivered-To: emu@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 17E413A0AA7; Fri, 30 Oct 2020 01:12:13 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.349
X-Spam-Level: 
X-Spam-Status: No, score=-2.349 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIMWL_WL_HIGH=-0.001, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, DKIM_VALID_EF=-0.1, NICE_REPLY_A=-0.247, RCVD_IN_MSPIKE_H2=-0.001, SPF_PASS=-0.001, URIBL_BLOCKED=0.001] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (1024-bit key) header.d=ericsson.com
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 hTNLHoJAaAbQ; Fri, 30 Oct 2020 01:12:11 -0700 (PDT)
Received: from EUR05-AM6-obe.outbound.protection.outlook.com (mail-am6eur05on2047.outbound.protection.outlook.com [40.107.22.47]) (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 2FF3A3A0AA3; Fri, 30 Oct 2020 01:12:10 -0700 (PDT)
ARC-Seal: i=1; a=rsa-sha256; s=arcselector9901; d=microsoft.com; cv=none; b=B1mPTU1fchN9YIW0QNwdbtBFKYpvS5JF/IFDfX5kTDNX3sDLtQheKuqRw/mLeXI/jGQ/RUx06rE5oqeA6Ea3eLRUTD5aK58nYw2tapHREi501tZhYBQjPXYTDWZifu7oj4Kyt/vmbCFL1iZvTlbaQS3+4a7Wt2e+X/xMh2H/+wA7b4ctBu7I41jEeO4ALQ8qaXp0FArgTVeApeWq9NXuol639KzwDOIOSdZgGWj2cetpe5rCa9p5VikDM4Nzu1LDq4dHOKVLpu3dOXW8Ys4hC8tvy/rWkJB9g3+f1BNhYRknhK+dTmSDm/8cXGSG+rSefspwpsGaW/LzizuvBHteRg==
ARC-Message-Signature: i=1; a=rsa-sha256; c=relaxed/relaxed; d=microsoft.com;  s=arcselector9901; h=From:Date:Subject:Message-ID:Content-Type:MIME-Version:X-MS-Exchange-SenderADCheck; bh=94GgHhmPhhZx9J004nja24CcsqoWlKyM+TIcvSzxthA=; b=fai4ywlTgraxRlw/5rV0fXJpKfOPakCLg4LyWLdsVIqQYEChgNvaVPaqHAsG2Xwqyg8c00pN5S1IIrHG0VMNFxGXxnJFyXTXWUYPY12Ky6avpmpr6RCoMCeDv27+Z7kA28CWAjwN5ZunufkUatEg9NHsdt1cMFc6/qVqi+IOgwsLQdHiieNE0Pm6I0JBFPCQDPgCEC+qZIwzNZEy42ORZPA01m0o1XNI0tUyYy3Len5jOyFJqEUIpAn1J97l/rydc0wmChtPuoUAf1n10CrIui2qw6RYAXloOy1d5VcS1doRaPe1DlWAzBmx3MlS8QI82xpkwmWg6s005NwRVO0Isw==
ARC-Authentication-Results: i=1; mx.microsoft.com 1; spf=pass smtp.mailfrom=ericsson.com; dmarc=pass action=none header.from=ericsson.com; dkim=pass header.d=ericsson.com; arc=none
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=ericsson.com; s=selector1; h=From:Date:Subject:Message-ID:Content-Type:MIME-Version:X-MS-Exchange-SenderADCheck; bh=94GgHhmPhhZx9J004nja24CcsqoWlKyM+TIcvSzxthA=; b=pADQw0h2PSv6CbB52aMA7RKnm8oF7ZrwPAVjVGi49bLJk961AClQj5gAkHbWKBopX6i0rBKl+LSCyzIZ4KbwiuE9Qq/0t2MFBzMO9OBN7o+NycfIQLm8Fd9qHiCOpm3zvdik/zcmeO2OxFDCD9M8mfVGjzywRKzwEA8JHvGDTSE=
Received: from HE1PR07MB3209.eurprd07.prod.outlook.com (2603:10a6:7:32::14) by HE1PR0701MB2729.eurprd07.prod.outlook.com (2603:10a6:3:93::14) with Microsoft SMTP Server (version=TLS1_2, cipher=TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384) id 15.20.3499.8; Fri, 30 Oct 2020 08:12:07 +0000
Received: from HE1PR07MB3209.eurprd07.prod.outlook.com ([fe80::1550:2d88:a5be:95ca]) by HE1PR07MB3209.eurprd07.prod.outlook.com ([fe80::1550:2d88:a5be:95ca%6]) with mapi id 15.20.3499.028; Fri, 30 Oct 2020 08:12:07 +0000
From: Mohit Sethi M <mohit.m.sethi@ericsson.com>
To: Barry Leiba <barryleiba@computer.org>, The IESG <iesg@ietf.org>
CC: "draft-ietf-emu-eaptlscert@ietf.org" <draft-ietf-emu-eaptlscert@ietf.org>,  "emu-chairs@ietf.org" <emu-chairs@ietf.org>, "emu@ietf.org" <emu@ietf.org>
Thread-Topic: [Emu] Barry Leiba's No Objection on draft-ietf-emu-eaptlscert-06: (with COMMENT)
Thread-Index: AQHWrV+EkMJyVhlVr0u/Tjw5zs9/EamvzfcA
Date: Fri, 30 Oct 2020 08:12:07 +0000
Message-ID: <dfb630f1-f42d-0589-ffc7-e860b2782fed@ericsson.com>
References: <160391287468.14554.8990471287012823249@ietfa.amsl.com>
In-Reply-To: <160391287468.14554.8990471287012823249@ietfa.amsl.com>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
user-agent: Mozilla/5.0 (X11; Linux x86_64; rv:68.0) Gecko/20100101 Thunderbird/68.10.0
authentication-results: computer.org; dkim=none (message not signed) header.d=none;computer.org; dmarc=none action=none header.from=ericsson.com;
x-originating-ip: [37.136.189.206]
x-ms-publictraffictype: Email
x-ms-office365-filtering-correlation-id: 2289e9dc-2051-4704-6436-08d87cab7e9d
x-ms-traffictypediagnostic: HE1PR0701MB2729:
x-microsoft-antispam-prvs: <HE1PR0701MB27297F5C93CCFF7910379C51D0150@HE1PR0701MB2729.eurprd07.prod.outlook.com>
x-ms-oob-tlc-oobclassifiers: OLM:10000;
x-ms-exchange-senderadcheck: 1
x-microsoft-antispam: BCL:0;
x-microsoft-antispam-message-info: VTPenfcMW4QCb1ZdS6RO0g4PJU+GBPVrf6Ao+reQKWSc5Ki8zFWL63PhgF3E/bmnDpuVGkeTSMNbLgNi1R8w8lRW9F9/prT3Q1V/adlxO6aLGkS5/EcF18u+PzEs/trqZmhqBzJJqxPvMw+4XPu22OT5tylU8glEmIattYKi/Mi3c1DChbzpmnEajDd5defCVQ6HvZK9AZRkSCioosOgHozbwxusAZH40IbxM/BVA/IcBNq3C57WHKWSXTI/imk8LJwveeNxEnpSmlHcozD/ACwyYk7FUzfk0nAbBfjJFAvJFMTj64j1ZR40j7ZPMj985Y8rPKO49Env+JC8PACLXdIhXaWaBqQ/oHppCqnxb92V5zUlzT4XVHiJjGAsnutcKiCMDGxaj0Ml3fl08UtxK7H8XrWPd5eA/DY/l6cuxRP48f9naDRKpfbX0zcZ3QrLORYvadQd5mIGC++SgzAx6A==
x-forefront-antispam-report: CIP:255.255.255.255; CTRY:; LANG:en; SCL:1; SRV:;  IPV:NLI; SFV:NSPM; H:HE1PR07MB3209.eurprd07.prod.outlook.com; PTR:; CAT:NONE;  SFS:(4636009)(396003)(366004)(136003)(39860400002)(346002)(376002)(8676002)(36756003)(5660300002)(2906002)(8936002)(66446008)(66574015)(31686004)(478600001)(31696002)(966005)(64756008)(83380400001)(66476007)(66556008)(66946007)(76116006)(6512007)(86362001)(110136005)(26005)(316002)(54906003)(186003)(71200400001)(4326008)(2616005)(53546011)(6506007)(6486002)(43740500002); DIR:OUT; SFP:1101; 
x-ms-exchange-antispam-messagedata: BnM9vNADJ3Ceuh3A51jsg3Mt+rqbj82HCQPPFsYkd0qC78vzYCYXkhcaafgk4VCvxWFBjRsNRVqXPJ1Jn4P+9ArN5XVD6YBELi7jsxyC9VKVl8jUhB2QZjveDYBn6PnAVbESBUn2/EogVfYegRqX+suacBH0Gh6AuDoawc/a2/TwqwvpUg84oVKWrWofWcGp1geK+efd03eg+yO7E6PmWpRO9hKt4JmNXS7o+y7O//C63543HZvTHa7E8siUjlyobNmjuwx1zkxAZ7FntdfpDL6mgyXADMn48IUnv8PwBl9PlK0wKYjv+m3uvGpdt6iB6Q2Uc+1RjqgEd84jDgJI1uQE5R1Y+zh8qaogyx9j4oDKF+fQRgf/qZB8d4tjH98zO06plt87fdU7dDNqNMC1kxvEeCEMq1dEjAruLr3hTTe1TEk/LJ/v7U6YuETRiFK8HC5O6HtXJP0nGIq5HXZjynmlXD15ckB6GMytEqDLhgLWxmLB+Sa4kJ8BPXPlwpC3DG6RyqBvUcLVYCCmk1jzwDTuYHKsZkaFPuWrNQVyQWT4JW/QB/uWdywh34Cuf3Y10e9GJ/Wh8Zaz0Cqf4krl8J1ziKZECZMXlsupXlWT6DAUElyfu0VHYbtH8t+o+QPkDWKdHVnVgtj7DFcT581ypg==
x-ms-exchange-transport-forked: True
Content-Type: text/plain; charset="utf-8"
Content-ID: <74D90EBA786EDA408EA9F5DBA77304F6@eurprd07.prod.outlook.com>
Content-Transfer-Encoding: base64
MIME-Version: 1.0
X-OriginatorOrg: ericsson.com
X-MS-Exchange-CrossTenant-AuthAs: Internal
X-MS-Exchange-CrossTenant-AuthSource: HE1PR07MB3209.eurprd07.prod.outlook.com
X-MS-Exchange-CrossTenant-Network-Message-Id: 2289e9dc-2051-4704-6436-08d87cab7e9d
X-MS-Exchange-CrossTenant-originalarrivaltime: 30 Oct 2020 08:12:07.6412 (UTC)
X-MS-Exchange-CrossTenant-fromentityheader: Hosted
X-MS-Exchange-CrossTenant-id: 92e84ceb-fbfd-47ab-be52-080c6b87953f
X-MS-Exchange-CrossTenant-mailboxtype: HOSTED
X-MS-Exchange-CrossTenant-userprincipalname: 9LaOOyaavUpQW3gke5wgscyOlZnDLtTxIIHmdfBxUtojTXcURv0Kh42jD5DNC1CxRoyzBA4bPLWXS9Tf/WTOA+GFgAUCKwuH1cxsDSCbQuA=
X-MS-Exchange-Transport-CrossTenantHeadersStamped: HE1PR0701MB2729
Archived-At: <https://mailarchive.ietf.org/arch/msg/emu/rjEf97B8LD9bo9qz-UmGW-z2zS4>
Subject: Re: [Emu] Barry Leiba's No Objection on draft-ietf-emu-eaptlscert-06: (with COMMENT)
X-BeenThere: emu@ietf.org
X-Mailman-Version: 2.1.29
Precedence: list
List-Id: "EAP Methods Update \(EMU\)" <emu.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/emu>, <mailto:emu-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/emu/>
List-Post: <mailto:emu@ietf.org>
List-Help: <mailto:emu-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/emu>, <mailto:emu-request@ietf.org?subject=subscribe>
X-List-Received-Date: Fri, 30 Oct 2020 08:12:13 -0000

SGkgQmFycnksDQoNClRoYW5rIHlvdSBmb3IgdGhlIGNhcmVmdWwgcmV2aWV3LiBJIGhhdmUgdXBk
YXRlZCB0aGUgZHJhZnQgaW4gZ2l0aHViIA0KKGh0dHBzOi8vZ2l0aHViLmNvbS9lbXUtd2cvZWFw
dGxzLWxvbmdjZXJ0KS4gSGVyZSBpcyB0aGUgZGlmZiBmb3IgeW91ciANCmNvbnZlbmllbmNlOiAN
Cmh0dHBzOi8vdG9vbHMuaWV0Zi5vcmcvcmZjZGlmZj91cmwxPWh0dHBzOi8vdG9vbHMuaWV0Zi5v
cmcvaWQvZHJhZnQtaWV0Zi1lbXUtZWFwdGxzY2VydC50eHQmdXJsMj1odHRwczovL2VtdS13Zy5n
aXRodWIuaW8vZWFwdGxzLWxvbmdjZXJ0L2RyYWZ0LWlldGYtZW11LWVhcHRsc2NlcnQudHh0LiAN
Ckkgd2lsbCB3YWl0IGZvciBhbGwgdGhlIGNvbW1lbnRzIHRvIGNvbWUgaW4gYmVmb3JlIHN1Ym1p
dHRpbmcgYSBuZXcgdmVyc2lvbi4NCg0KUmVnYXJkaW5nIHlvdXIgY29tbWVudCBvZiBpbmZvcm1h
dGlvbmFsIHZzLiBhcHBsaWNhYmlsaXR5IHN0YXRlbWVudDogSSANCmFtIG5vdCBvcHBvc2VkIHRv
IHRoZSBpZGVhLiBJIGFtIGhhcHB5IHRvIGZvbGxvdyB3aGF0ZXZlciB0aGUgSUVTRyANCnJlY29t
bWVuZHMuDQoNCi0tTW9oaXQNCg0KT24gMTAvMjgvMjAgOToyMSBQTSwgQmFycnkgTGVpYmEgdmlh
IERhdGF0cmFja2VyIHdyb3RlOg0KPiBCYXJyeSBMZWliYSBoYXMgZW50ZXJlZCB0aGUgZm9sbG93
aW5nIGJhbGxvdCBwb3NpdGlvbiBmb3INCj4gZHJhZnQtaWV0Zi1lbXUtZWFwdGxzY2VydC0wNjog
Tm8gT2JqZWN0aW9uDQo+DQo+IFdoZW4gcmVzcG9uZGluZywgcGxlYXNlIGtlZXAgdGhlIHN1Ympl
Y3QgbGluZSBpbnRhY3QgYW5kIHJlcGx5IHRvIGFsbA0KPiBlbWFpbCBhZGRyZXNzZXMgaW5jbHVk
ZWQgaW4gdGhlIFRvIGFuZCBDQyBsaW5lcy4gKEZlZWwgZnJlZSB0byBjdXQgdGhpcw0KPiBpbnRy
b2R1Y3RvcnkgcGFyYWdyYXBoLCBob3dldmVyLikNCj4NCj4NCj4gUGxlYXNlIHJlZmVyIHRvIGh0
dHBzOi8vd3d3LmlldGYub3JnL2llc2cvc3RhdGVtZW50L2Rpc2N1c3MtY3JpdGVyaWEuaHRtbA0K
PiBmb3IgbW9yZSBpbmZvcm1hdGlvbiBhYm91dCBJRVNHIERJU0NVU1MgYW5kIENPTU1FTlQgcG9z
aXRpb25zLg0KPg0KPg0KPiBUaGUgZG9jdW1lbnQsIGFsb25nIHdpdGggb3RoZXIgYmFsbG90IHBv
c2l0aW9ucywgY2FuIGJlIGZvdW5kIGhlcmU6DQo+IGh0dHBzOi8vZGF0YXRyYWNrZXIuaWV0Zi5v
cmcvZG9jL2RyYWZ0LWlldGYtZW11LWVhcHRsc2NlcnQvDQo+DQo+DQo+DQo+IC0tLS0tLS0tLS0t
LS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0t
LS0NCj4gQ09NTUVOVDoNCj4gLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0t
LS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLQ0KPg0KPiBUaGFua3MgZm9yIHRoaXM7IGl0
IHdpbGwgYmUgdXNlZnVsIHRvIGhhdmUgdGhpcyBpc3N1ZSBmaXhlZC4NCj4NCj4gVGhlcmXigJlz
IHNvbWV0aGluZyBJ4oCZZCBsaWtlIHRvIGRpc2N1c3MsIGJ1dCB3aXRob3V0IG1ha2luZyBpdCBh
IGJsb2NraW5nIERJU0NVU1M6DQo+IFdoaWxlIEkgdW5kZXJzdGFuZCB0aGUgcmVhc29uIGZvciBw
dXR0aW5nIHRoaXMgZm9yd2FyZCBhcyBJbmZvcm1hdGlvbmFsLCBpdA0KPiBkb2VzIHN0cmlrZSBt
ZSBtb3JlIGFzIGEgU3RhbmRhcmRzIFRyYWNrIEFwcGxpY2FiaWxpdHkgU3RhdGVtZW50LiAgQkNQ
IDkgc2F5cw0KPiAoaW4gUkZDIDIwMjYgU2VjdGlvbiAzLjIpOg0KPg0KPiAgICAgQW4gQXBwbGlj
YWJpbGl0eSBTdGF0ZW1lbnQgc3BlY2lmaWVzIGhvdywgYW5kIHVuZGVyIHdoYXQNCj4gICAgIGNp
cmN1bXN0YW5jZXMsIG9uZSBvciBtb3JlIFRTcyBtYXkgYmUgYXBwbGllZCB0byBzdXBwb3J0IGEg
cGFydGljdWxhcg0KPiAgICAgSW50ZXJuZXQgY2FwYWJpbGl0eS4NCj4NCj4gUmVhZGluZyB0aGUg
cmVzdCBvZiBTZWN0aW9uIDMuMiBhcyB3ZWxsLCBJIHRoaW5rIHRoYXQgaXQgZml0cyBleGFjdGx5
IHdoYXQNCj4geW914oCZcmUgZG9pbmcgd2l0aCB0aGlzIGRvY3VtZW50OiB0aGUgZG9jdW1lbnQg
aXMgc2F5aW5nIHRoYXQgdGhlcmXigJlzIGFuDQo+IGludGVyb3BlcmFiaWxpdHkgcHJvYmxlbSB3
aXRoIGxhcmdlIGNlcnRzIGFuZCBsb25nIGNoYWlucywgYW5kIGhlcmUgYXJlIHRoaW5ncw0KPiB0
byBkbyBpbiBvcmRlciB0byBtYWtlIHRoYXQgd29yay4gIExldOKAmXMgcGxlYXNlIGhhdmUgYSBi
cmllZiBkaXNjdXNzaW9uIGFib3V0DQo+IHdoZXRoZXIgdGhpcyBzaG91bGQgaW5zdGVhZCBiZSBw
dWJsaXNoZWQgYXQgUHJvcG9zZWQgU3RhbmRhcmQgYXMgYW4gQVMuDQo+DQo+IOKAlOKAlOKAlOKA
lOKAlA0KPg0KPiBCZWxvdyBhcmUgc29tZSBuaXRzIHRoYXQgSSBob3BlIHlvdeKAmWxsIGNvbnNp
ZGVyLCBidXQgdGhlcmXigJlzIG5vIG5lZWQgdG8gcmVzcG9uZA0KPiBpbiBkZXRhaWwgaGVyZTsg
cGxlYXNlIGRvIGFzIHlvdSB0aGluayBiZXN0Lg0KPg0KPiDigJQgU2VjdGlvbiAxIOKAlA0KPg0K
PiAgICAgdmVuZG9yIHNwZWNpZmljIEVBUCBtZXRob2RzLg0KPg0KPiBOZWVkIGEgaHlwaGVuIGlu
IOKAnHZlbmRvci1zcGVjaWZpY+KAnS4NCj4NCj4gICAgIEVBUC1UTFMNCj4gICAgIGRlcGxveW1l
bnRzIHR5cGljYWxseSBhdXRoZW50aWNhdGVzIGJvdGggdGhlIEVBUCBwZWVyIGFuZCB0aGUgRUFQ
DQo+DQo+IE1ha2UgaXQg4oCcYXV0aGVudGljYXRl4oCdLg0KPg0KPiAgICAgU2VjdGlvbiAzLjEg
b2YgW1JGQzM3NDhdIHN0YXRlcyB0aGF0IEVBUCBpbXBsZW1lbnRhdGlvbnMgY2FuIGFzc3VtZSBh
DQo+ICAgICBNVFUgb2YgYXQgbGVhc3QgMTAyMCBvY3RldHMgZnJvbSBsb3dlciBsYXllcnMuDQo+
DQo+IFVubGVzcyB5b3UgaGF2ZSBhIHdheSBvZiBwcm9ub3VuY2luZyDigJxNVFXigJ0gdGhhdCBJ
IGRvbuKAmXQsIG1ha2UgaXQg4oCcYW4gTVRV4oCdLg0KPg0KPiAgICAgU3VjaCBmcmFnbWVudGF0
aW9uIGNhbiBub3Qgb25seSBuZWdhdGl2ZWx5DQo+ICAgICBhZmZlY3QgdGhlIGxhdGVuY3ksIGJ1
dCBhbHNvIHJlc3VsdHMgaW4gb3RoZXIgY2hhbGxlbmdlcy4NCj4NCj4gVGhlIOKAnGNhbuKAnSBp
cyBtaXNwbGFjZWQ7IG1ha2UgaXQg4oCcbm90IG9ubHkgY2FuIGFmZmVjdOKAnS4NCj4NCj4g4oCU
IFNlY3Rpb24gMiDigJQNCj4NCj4gICAgIFRoZSBkb2N1bWVudCBhZGRpdGlvbmFsbHkgdXNlcyB0
aGUgdGVybXMgdHJ1c3QgYW5jaG9yIGFuZA0KPiAgICAgY2VydGlmaWNhdGlvbiBwYXRoIGRlZmlu
ZWQgaW4gW1JGQzUyODBdLg0KPg0KPiBJIHdvdWxkIHB1dCDigJx0cnVzdCBhbmNob3LigJ0gYW5k
IOKAnGNlcnRpZmljYXRpb24gcGF0aOKAnSBpbiBxdW90ZXMgaGVyZS4NCj4NCj4g4oCUIFNlY3Rp
b24gMyDigJQNCj4NCj4gICAgIENlcnRpZmljYXRlIHNpemVzIGNhbiBob3dldmVyIGJlIGxhcmdl
DQo+DQo+IENvbW1hcyBhcmUgbmVlZGVkIGJvdGggYmVmb3JlIGFuZCBhZnRlciDigJxob3dldmVy
4oCdLiAgQWxzbywgdGhlIGxpc3QgdGFsa3MgYWJvdXQNCj4gYSBzaW5ndWxhciDigJxjZXJ0aWZp
Y2F0ZeKAnSwgc28gdGhlIGxlYWQtaW4gc2hvdWxkIG1hdGNoIHRoYXQgKGFuZCB5b3UgZG9u4oCZ
dCBuZWVkDQo+IHRvIHNheSB0aGF0IGEgKnNpemUqIGNhbiBiZSBsYXJnZSk6IOKAnEEgY2VydGlm
aWNhdGUgY2FuLCBob3dldmVyLCBiZSBsYXJnZSBmb3IgYQ0KPiBudW1iZXIgb2YgcmVhc29uczri
gJ0NCj4NCj4gVGhlIGxpc3QgaXMgYWxzbyBub3QgcGFyYWxsZWwgKHRoZSB0aGlyZCBpdGVtLCBp
biBwYXJ0aWN1bGFyLCBpcyBub3QgbGlrZSB0aGUNCj4gb3RoZXJzKS4gIEkgd291bGQgbWFrZSB0
aGUgd2hvbGUgbGlzdCBiZSBjb21wbGV0ZSBzZW50ZW5jZXMsIGxpa2UgdGhpcywNCj4gcmVmZXJy
aW5nIHRvIOKAnGEgY2VydGlmaWNhdGXigJ0gaW4gdGhlIGxlYWQtaW46DQo+DQo+IE5FVw0KPiAg
ICAgbyAgSXQgY2FuIGhhdmUgYSBsb25nIFN1YmplY3QgQWx0ZXJuYXRpdmUgTmFtZSBmaWVsZC4N
Cj4NCj4gICAgIG8gIEl0IGNhbiBoYXZlIGxvbmcgUHVibGljIEtleSBhbmQgU2lnbmF0dXJlIGZp
ZWxkcy4NCj4NCj4gICAgIG8gIEl0IGNhbiBjb250YWluIG11bHRpcGxlIG9iamVjdCBpZGVudGlm
aWVycyAoT0lEKSB0aGF0IGluZGljYXRlIHRoZQ0KPiAgICAgICAgcGVybWl0dGVkIHVzZXMgb2Yg
dGhlIGNlcnRpZmljYXRlIGFzIG5vdGVkIGluIFNlY3Rpb24gNS4zIG9mDQo+ICAgICAgICBbUkZD
NTIxNl0uICBNb3N0IGltcGxlbWVudGF0aW9ucyB2ZXJpZnkgdGhlIHByZXNlbmNlIG9mIHRoZXNl
IE9JRHMNCj4gICAgICAgIGZvciBzdWNjZXNzZnVsIGF1dGhlbnRpY2F0aW9uLg0KPg0KPiAgICAg
byAgSXQgY2FuIGNvbnRhaW4gbXVsdGlwbGUgdXNlciBncm91cHMuDQo+IEVORA0KPg0KPiDigJQg
U2VjdGlvbiA0LjEg4oCUDQo+DQo+IFRocm91Z2hvdXQgdGhpcyBwYXJhZ3JhcGggeW91IHJlZmVy
IHRvIOKAnHNpemUgb2YgcHVibGljIGtleXPigJ0gYW5kIOKAnHNpemUgb2YNCj4gZGlnaXRhbCBz
aWduYXR1cmVz4oCdLiAgSXTigJlzIGEgcmVhbGx5IG5pdHR5IG5pdCwgYnV0IEkgd291bGQgbWFr
ZSB0aGVzZSBhbGwNCj4gc2luZ3VsYXIsIGJlY2F1c2Ugd2XigJlyZSByZWFsbHkgdGFsa2luZyBh
Ym91dCB0aGUgc2l6ZSBvZiBhbiBpbmRpdmlkdWFsIHB1YmxpYw0KPiBrZXkgb3IgZGlnaXRhbCBz
aWduYXR1cmUsIG5vdCB0aGUgc2l6ZSBvZiBhIGNvbGxlY3Rpb24gb2YgdGhlbS4NCj4NCj4gICAg
IGF1dGhlbnRpY2F0aW9uIHdoaWNoIGNhbiBhbGxldmlhdGUgdGhlIHByb2JsZW0gb2YgYXV0aGVu
dGljYXRvcnMNCj4NCj4gVGhlcmUgbmVlZHMgdG8gYmUgYSBjb21tYSBiZWZvcmUg4oCcd2hpY2ji
gJ0uDQo+DQo+ICAgICBFQ0MgYmFzZWQgY2lwaGVyIHN1aXRlcyB3aXRoIGV4aXN0aW5nIGNvZGUg
Y2FuIHNpZ25pZmljYW50bHkNCj4NCj4gSHlwaGVuYXRlIOKAnEVDQy1iYXNlZOKAnS4NCj4NCj4g
4oCUIFNlY3Rpb24gNC4xLjEg4oCUDQo+DQo+ICAgICBPSURzIGFyZSB1c2VkIGxhdmlzaGx5IGlu
IFguNTA5IGNlcnRpZmljYXRlcw0KPg0KPiBJIGxpa2UgaXQ6IOKAnGxhdmlzaGx54oCdIGlzIG5v
dCBhIHdvcmQgd2Ugb2Z0ZW4gc2VlIGluIFJGQ3MuICA6LSkNCj4NCj4gICAgICAgIEROcw0KPiAg
ICAgICAgdXNlZCBpbiB0aGUgaXNzdWVyIGFuZCBzdWJqZWN0IGZpZWxkcyBhcyB3ZWxsIGFzIG51
bWVyb3VzDQo+ICAgICAgICBleHRlbnNpb25zLg0KPg0KPiBUaGlzIGlzIG5vdCBhIGNvbXBsZXRl
IHNlbnRlbmNlOyBwbGVhc2UgZml4IHRoYXQgKEkgdGhpbmsgeW914oCZcmUganVzdCBtaXNzaW5n
DQo+IOKAnGFyZeKAnSBhZnRlciDigJxETnPigJ0pLg0KPg0KPiAgICAgQ049Q29vbGVzdCBJb1Qg
R2FkZ2V0IEV2ZXINCj4NCj4gT2ghICBJIHdhbnQgdGhhdCENCj4NCj4NCj4NCj4gX19fX19fX19f
X19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX18NCj4gRW11IG1haWxpbmcgbGlz
dA0KPiBFbXVAaWV0Zi5vcmcNCj4gaHR0cHM6Ly93d3cuaWV0Zi5vcmcvbWFpbG1hbi9saXN0aW5m
by9lbXUNCg==


From nobody Fri Oct 30 04:45:04 2020
Return-Path: <mcr+ietf@sandelman.ca>
X-Original-To: emu@ietfa.amsl.com
Delivered-To: emu@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 621DC3A0E08 for <emu@ietfa.amsl.com>; Fri, 30 Oct 2020 04:44:58 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.899
X-Spam-Level: 
X-Spam-Status: No, score=-1.899 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, SPF_HELO_NONE=0.001, SPF_PASS=-0.001, URIBL_BLOCKED=0.001] autolearn=ham autolearn_force=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 MryNPlZl2b0a for <emu@ietfa.amsl.com>; Fri, 30 Oct 2020 04:44:56 -0700 (PDT)
Received: from tuna.sandelman.ca (tuna.sandelman.ca [209.87.249.19]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id D67743A0E09 for <emu@ietf.org>; Fri, 30 Oct 2020 04:44:56 -0700 (PDT)
Received: from localhost (localhost [127.0.0.1]) by tuna.sandelman.ca (Postfix) with ESMTP id 0ECF0389BE; Fri, 30 Oct 2020 07:51:44 -0400 (EDT)
Received: from tuna.sandelman.ca ([127.0.0.1]) by localhost (localhost [127.0.0.1]) (amavisd-new, port 10024) with LMTP id 6ATvv3Cfzwcw; Fri, 30 Oct 2020 07:51:43 -0400 (EDT)
Received: from sandelman.ca (obiwan.sandelman.ca [IPv6:2607:f0b0:f:2::247]) by tuna.sandelman.ca (Postfix) with ESMTP id 59BB4389BD; Fri, 30 Oct 2020 07:51:43 -0400 (EDT)
Received: from localhost (localhost [IPv6:::1]) by sandelman.ca (Postfix) with ESMTP id 05554362; Fri, 30 Oct 2020 07:44:54 -0400 (EDT)
From: Michael Richardson <mcr+ietf@sandelman.ca>
To: Joseph Salowey <joe@salowey.net>, EMU WG <emu@ietf.org>
In-Reply-To: <CAOgPGoDC8gyBLD4a7Ms-h823sZ5q6USpbE=6HXdVWo3TEVfoYA@mail.gmail.com>
References: <CAOgPGoDbsunLOxrnFxa8uMxG6JYObX_r5VLOvVib5QmFHGOrwA@mail.gmail.com> <4858.1604009572@localhost> <CAOgPGoDC8gyBLD4a7Ms-h823sZ5q6USpbE=6HXdVWo3TEVfoYA@mail.gmail.com>
X-Mailer: MH-E 8.6+git; nmh 1.7+dev; GNU Emacs 26.1
X-Face: $\n1pF)h^`}$H>Hk{L"x@)JS7<%Az}5RyS@k9X%29-lHB$Ti.V>2bi.~ehC0; <'$9xN5Ub# z!G,p`nR&p7Fz@^UXIn156S8.~^@MJ*mMsD7=QFeq%AL4m<nPbLgmtKK-5dC@#:k
MIME-Version: 1.0
Content-Type: multipart/signed; boundary="=-=-="; micalg=pgp-sha512; protocol="application/pgp-signature"
Date: Fri, 30 Oct 2020 07:44:53 -0400
Message-ID: <4217.1604058293@localhost>
Archived-At: <https://mailarchive.ietf.org/arch/msg/emu/4pXPkUjf6hs_ufqJGpRS3dESlNI>
Subject: Re: [Emu] Consensus Call on OCSP usage in draft-ietf-emu-eap-tls13-11
X-BeenThere: emu@ietf.org
X-Mailman-Version: 2.1.29
Precedence: list
List-Id: "EAP Methods Update \(EMU\)" <emu.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/emu>, <mailto:emu-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/emu/>
List-Post: <mailto:emu@ietf.org>
List-Help: <mailto:emu-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/emu>, <mailto:emu-request@ietf.org?subject=subscribe>
X-List-Received-Date: Fri, 30 Oct 2020 11:44:58 -0000

--=-=-=
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: quoted-printable


Joseph Salowey <joe@salowey.net> wrote:
    >> I suggest:
    >>
    >> =E2=80=9CEAP-TLS servers supporting TLS 1.3 that use OCSP to do cert=
ificate
    >> recovation checks,  MUST implement Certificate Status Requests using=
 OCSP
    >> stapling as specified in Section 4.4.2.1 of [RFC8446].

    > [Joe] Thanks Michael,  I think your suggestion is a better way to phr=
ase it

Just so that we are clear:  this mandates OCSP+stapling for systems that do
revocation checks.

Systems that don't do revocation checks (current mbedtls), therefore don't
need to do OCSP or stapling.

=2D-
Michael Richardson <mcr+IETF@sandelman.ca>   . o O ( IPv6 I=C3=B8T consulti=
ng )
           Sandelman Software Works Inc, Ottawa and Worldwide


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

-----BEGIN PGP SIGNATURE-----

iQEzBAEBCgAdFiEEbsyLEzg/qUTA43uogItw+93Q3WUFAl+b/LUACgkQgItw+93Q
3WV8jAgAgspayKANY54LBtRKJiG0bgCNaph50UuNc8p+5OKkbAzRg9K8pJqUMF03
ke3RoahX6EQBo5T2OO9DI9WkYQuRo7eNMvm2t7PJktqJlOmUt7C7vKJbv0tdHE12
qp3pQc+iSMmGIT13ymBH7xNszA6CsyvGI5evvvXXf15K0qqBe37iXg6SNT0MvkuI
dbsJaVSquqzau/IjPWUyHlInCiSZK5hJ9deA1FLcItfSMaCvJ2L9b1xp1RmwB3BM
Vm2F4wBGJwJWZGzDmjOQ9uepqZpRq/LFJNCR01lQAmDqxT2M5ol2RfLiH1fUh9Fk
LcFc0lJPNaYMz+NajYoTZ3bhlux+4A==
=M14R
-----END PGP SIGNATURE-----
--=-=-=--


From nobody Fri Oct 30 06:48:43 2020
Return-Path: <mohit.m.sethi@ericsson.com>
X-Original-To: emu@ietfa.amsl.com
Delivered-To: emu@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id C9D123A0EA9; Fri, 30 Oct 2020 06:48:41 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.349
X-Spam-Level: 
X-Spam-Status: No, score=-2.349 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIMWL_WL_HIGH=-0.001, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, DKIM_VALID_EF=-0.1, NICE_REPLY_A=-0.247, RCVD_IN_MSPIKE_H2=-0.001, SPF_PASS=-0.001, URIBL_BLOCKED=0.001] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (1024-bit key) header.d=ericsson.com
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 bE88ZMQODUBd; Fri, 30 Oct 2020 06:48:39 -0700 (PDT)
Received: from EUR05-AM6-obe.outbound.protection.outlook.com (mail-am6eur05on2046.outbound.protection.outlook.com [40.107.22.46]) (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 2555E3A0EAA; Fri, 30 Oct 2020 06:48:38 -0700 (PDT)
ARC-Seal: i=1; a=rsa-sha256; s=arcselector9901; d=microsoft.com; cv=none; b=GEB102smUNi7NZGrUka8cGVKCAnhhMzcAgU09l1M/82b9vv0MbzKHwy/UnTXsYmA4vwX98EAnvZnZsl5vod5Aip/rDqNdxTNNQc+PLXGT3r+N2eiGhSE3Z1DaxC1slCf4JjqIE+jii/BB3wEgRlcwgFPhAqPDrwBdROwzlCBuLlWXoaRac7fiNvRtrn1PmkLyxM4ZLvz1KCiS/m+EGqz+mxE9Y0kNxIVApGijZVgpJukQIMSxh45crB9xzuhwivBlZQwvnbsbKLSW5Ap2s2c9Eporb+8HTqQdMul8l404Ss3PS7v8bXMQ/bzPzZirI8Xw+Jr3R6on68QkLmcoU6tZA==
ARC-Message-Signature: i=1; a=rsa-sha256; c=relaxed/relaxed; d=microsoft.com;  s=arcselector9901; h=From:Date:Subject:Message-ID:Content-Type:MIME-Version:X-MS-Exchange-SenderADCheck; bh=pYCXdhp4G0/RUuWv8YZ95LSVyexi7dxkw4geU02Q2C4=; b=BzWBJsGUaflf/wl8dZ9I0+1q2aInHRxqbH8tGEWnUmzzMxLIOdsibuXqpFFYA0rOB4zC8rWpuPpWtf7OXJSu2s2dTXjmROzxmIJGlRDQOw3dflKXHhD68IXgE7SPdvsJ9bDwLnOBu54mXuRU/Ja/jDEVZ4qaTz4/2ENfCLOIcUv5fch4+VAkKWfd5fwWrU9LUIeuw1rEUD05ShqyMf0+APfpdyjIYkw2NFCPm3wXjkhFnmk+S51nvwUSqNOMPoHUr03dd+awfMiEn/byiyVwlj9XPpLsAG2P+Y0h1W36jJTJQR1sy7hJPo55/txWg9fbP0cH7jVp35RkEFEI7kW8bw==
ARC-Authentication-Results: i=1; mx.microsoft.com 1; spf=pass smtp.mailfrom=ericsson.com; dmarc=pass action=none header.from=ericsson.com; dkim=pass header.d=ericsson.com; arc=none
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=ericsson.com; s=selector1; h=From:Date:Subject:Message-ID:Content-Type:MIME-Version:X-MS-Exchange-SenderADCheck; bh=pYCXdhp4G0/RUuWv8YZ95LSVyexi7dxkw4geU02Q2C4=; b=imAWpWgG+3ftncTToSWb4Bpba+8FLf4b7TgW5lrkikYPfgmXE6fXGG6W0wbrh/NLye+/CovreZl6PbvW9MihxnjmUwjoQJmPjCuH2/PQbbNqmMP+WGjmdnQDkb8v/n2oR/0pTP10qfQmCt/Smmbp7Yhy0di4RADOrWcwUSEXCyg=
Received: from HE1PR07MB3209.eurprd07.prod.outlook.com (2603:10a6:7:32::14) by HE1PR07MB4282.eurprd07.prod.outlook.com (2603:10a6:7:a1::18) with Microsoft SMTP Server (version=TLS1_2, cipher=TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384) id 15.20.3499.14; Fri, 30 Oct 2020 13:48:36 +0000
Received: from HE1PR07MB3209.eurprd07.prod.outlook.com ([fe80::1550:2d88:a5be:95ca]) by HE1PR07MB3209.eurprd07.prod.outlook.com ([fe80::1550:2d88:a5be:95ca%6]) with mapi id 15.20.3499.028; Fri, 30 Oct 2020 13:48:36 +0000
From: Mohit Sethi M <mohit.m.sethi@ericsson.com>
To: Benjamin Kaduk <kaduk@mit.edu>, Stefan Santesson <stefan@aaa-sec.com>
CC: "last-call@ietf.org" <last-call@ietf.org>, "draft-ietf-emu-eaptlscert.all@ietf.org" <draft-ietf-emu-eaptlscert.all@ietf.org>, "emu@ietf.org" <emu@ietf.org>, "secdir@ietf.org" <secdir@ietf.org>
Thread-Topic: [Emu] Secdir last call review of draft-ietf-emu-eaptlscert-06
Thread-Index: AQHWrkkTSwTr5auJQke8Pqw//Tx6KKmvdiCAgAC0B4A=
Date: Fri, 30 Oct 2020 13:48:36 +0000
Message-ID: <12167567-9dc5-6161-abef-826b0a8b6602@ericsson.com>
References: <160401318284.11167.6795105917637378641@ietfa.amsl.com> <20201030030415.GE39170@kduck.mit.edu>
In-Reply-To: <20201030030415.GE39170@kduck.mit.edu>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
user-agent: Mozilla/5.0 (X11; Linux x86_64; rv:68.0) Gecko/20100101 Thunderbird/68.10.0
authentication-results: mit.edu; dkim=none (message not signed) header.d=none;mit.edu; dmarc=none action=none header.from=ericsson.com;
x-originating-ip: [37.136.189.206]
x-ms-publictraffictype: Email
x-ms-office365-filtering-correlation-id: ba5d73b1-d910-40ef-0ac3-08d87cda8001
x-ms-traffictypediagnostic: HE1PR07MB4282:
x-microsoft-antispam-prvs: <HE1PR07MB42823A004BE50BE91117CE4ED0150@HE1PR07MB4282.eurprd07.prod.outlook.com>
x-ms-oob-tlc-oobclassifiers: OLM:10000;
x-ms-exchange-senderadcheck: 1
x-microsoft-antispam: BCL:0;
x-microsoft-antispam-message-info: waP+WaeO/N3ilp8m4JZ4dq1EBrvMYt1UMn2ZymoyjK1DogGS57NewyUltnaSGxMbqMy9ybw19gd1vf4yA5hFllrvS8xpj1YyUiOER7yZNX2PJxoSTQWhq/5J7WfTjSy/9DD04la1GIGSgGDnvgWPQjFLdOWvIJXC6vDomBTjlSuzDI7GDx5PWF7634SooBFYJq9ULHXJJtlIZ34LOa5dO0xWgFcNakAUfNU6sw80GVE7AgF3cDKj65gEgcjn/v6S9Y7e1nAUfmDnf0zZP1WSorS4BMEnyadAA1NijLo54RZDRuX6JtB7NAm+TY7REZ9q7NSTZCZ97goa32pRppKI8imYOtL6nmiLxi7eQRX4E5VP0tx+EXUwKVJKCioKcWSnDfCnoeO0OArGFEZ9ZkSjsp0fnizGySf/VihUbummlnD5VaaExbq53LHLDD9rRxZq55sXDJRHFKq9ug4zGzN+Tg==
x-forefront-antispam-report: CIP:255.255.255.255; CTRY:; LANG:en; SCL:1; SRV:;  IPV:NLI; SFV:NSPM; H:HE1PR07MB3209.eurprd07.prod.outlook.com; PTR:; CAT:NONE;  SFS:(4636009)(366004)(376002)(136003)(39860400002)(396003)(346002)(8676002)(86362001)(36756003)(6512007)(8936002)(4326008)(2906002)(71200400001)(6486002)(26005)(478600001)(66946007)(66476007)(66556008)(66446008)(966005)(64756008)(76116006)(316002)(31686004)(186003)(110136005)(54906003)(31696002)(2616005)(53546011)(6506007)(83380400001)(5660300002)(43740500002); DIR:OUT; SFP:1101; 
x-ms-exchange-antispam-messagedata: ytX6PwytVD694xiBp7MY2kOIozHeL89H8cw4+4wdYS9CaxLNXiNGtEWvVy+UU/I6jgn4aDaa6wqcK6mveeLZtKB2L+xxHRLNJF+F0YacEefv1mA3rLWuh1lo92yZQmjmikx5G6HQ9ack0w+agWJrNOPfCW61tSXheZzn9VP5TEHUx5EBc+Yqts5fErRwFrBJPWV6FwcfP1BZPcIT2WbJn/XmClHnyanWSRVFvFYreMz8q9qSgt66A8dOeGMdYaJk0PCBoy9fmSSs/lOcd4aBwkfvC6TXXE69aewbgUrXLqfWZsr7Zx1RJpcfjNCh8X9KN8Jff/2pwS3Pj5zjCjrfbl0Eh5W5KDSUv3JSc5M1cZWlDKyFr2x+WR+L1xNrMnjaWtIAaSExpSMikPpUcZAgsx8dfBKfclfSicNtqYGOfnnkTyE0pZa5D5tlydxfkAqlwHX3HWTuAOrQdv4enacZ2ijFvyLuWFWj6H8hs2bHEarDI+6Uq6YS/Sv8NBcrP+FMZPKafN+cvC/PVi7ByZzWS8LI3mIuA04GKYajGcm6G/j6iw605eDJc+AfVo2dmLfrHFggqEme5qRhNr/VvOliaKdRvt5quIqAx/PYeXn7390Jy8c2y/5R7L4a/zNEJM+HvRLluH+x/wRCPq8wjc4T8w==
x-ms-exchange-transport-forked: True
Content-Type: text/plain; charset="utf-8"
Content-ID: <50D831937F3C6640BB6348DC7A79BC5D@eurprd07.prod.outlook.com>
Content-Transfer-Encoding: base64
MIME-Version: 1.0
X-OriginatorOrg: ericsson.com
X-MS-Exchange-CrossTenant-AuthAs: Internal
X-MS-Exchange-CrossTenant-AuthSource: HE1PR07MB3209.eurprd07.prod.outlook.com
X-MS-Exchange-CrossTenant-Network-Message-Id: ba5d73b1-d910-40ef-0ac3-08d87cda8001
X-MS-Exchange-CrossTenant-originalarrivaltime: 30 Oct 2020 13:48:36.3522 (UTC)
X-MS-Exchange-CrossTenant-fromentityheader: Hosted
X-MS-Exchange-CrossTenant-id: 92e84ceb-fbfd-47ab-be52-080c6b87953f
X-MS-Exchange-CrossTenant-mailboxtype: HOSTED
X-MS-Exchange-CrossTenant-userprincipalname: cDhwQMKaSL26ZeT2OlBLq7rkMijy+RNUV6LGwXc683DH1YUvUatECBKIgahOTOnFOOxtJvNKavKXNagHH/NUMznBwp+P7u89ugYDags7sjI=
X-MS-Exchange-Transport-CrossTenantHeadersStamped: HE1PR07MB4282
Archived-At: <https://mailarchive.ietf.org/arch/msg/emu/jhLmkpFH7Vd4WIoATB1_0fbLPXc>
Subject: Re: [Emu] Secdir last call review of draft-ietf-emu-eaptlscert-06
X-BeenThere: emu@ietf.org
X-Mailman-Version: 2.1.29
Precedence: list
List-Id: "EAP Methods Update \(EMU\)" <emu.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/emu>, <mailto:emu-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/emu/>
List-Post: <mailto:emu@ietf.org>
List-Help: <mailto:emu-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/emu>, <mailto:emu-request@ietf.org?subject=subscribe>
X-List-Received-Date: Fri, 30 Oct 2020 13:48:42 -0000

SGkgU3RlZmFuLA0KDQpUaGFuayB5b3UgZm9yIHRoZSByZXZpZXcuIEkgaGF2ZSB1cGRhdGVkIHRo
ZSBkcmFmdCBpbiBnaXRodWIgDQooaHR0cHM6Ly9naXRodWIuY29tL2VtdS13Zy9lYXB0bHMtbG9u
Z2NlcnQpLiBIZXJlIGlzIHRoZSBkaWZmIGZvciB5b3VyIA0KY29udmVuaWVuY2U6IA0KaHR0cHM6
Ly90b29scy5pZXRmLm9yZy9yZmNkaWZmP3VybDE9aHR0cHM6Ly90b29scy5pZXRmLm9yZy9pZC9k
cmFmdC1pZXRmLWVtdS1lYXB0bHNjZXJ0LnR4dCZ1cmwyPWh0dHBzOi8vZW11LXdnLmdpdGh1Yi5p
by9lYXB0bHMtbG9uZ2NlcnQvZHJhZnQtaWV0Zi1lbXUtZWFwdGxzY2VydC50eHQuDQoNClRoZSBm
b2xsb3dpbmcgdGV4dCB3YXMgYWRkZWQ6DQoNCj4gwqDCoCBUaGUgc2l6ZSBvZiBjZXJ0aWZpY2F0
ZXMgKGFuZCBjZXJ0aWZpY2F0ZSBjaGFpbnMpIG1heSBhbHNvIGluY3JlYXNlDQo+IMKgwqAgbWFu
aWZvbGQgaW4gdGhlIGZ1dHVyZSB3aXRoIHRoZSBpbnRyb2R1Y3Rpb24gb2YgcXVhbnR1bS1zYWZl
DQo+IMKgwqAgY3J5cHRvZ3JhcGh5LsKgIEZvciBleGFtcGxlLCBsYXR0aWNlLWJhc2VkIGNyeXB0
b2dyYXBoeSB3b3VsZCBoYXZlDQo+IMKgwqAgcHVibGljIGtleXMgb2YgYXBwcm94aW1hdGVseSAx
MDAwIGJ5dGVzIGFuZCBzaWduYXR1cmVzIG9mDQo+IMKgwqAgYXBwcm94aW1hdGVseSAyMDAwIGJ5
dGVzLg0KYW5kIGluIFNlY3Rpb24gNC4yLjUNCg0KPiDCoMKgIFRoZSBBdXRob3JpdHkgSW5mb3Jt
YXRpb24gQWNjZXNzIChBSUEpIGV4dGVuc2lvbiBzcGVjaWZpZWQgaW4NCj4gwqDCoCBbUkZDNTI4
MF0gY2FuIGJlIHVzZWQgd2l0aCBlbmQtZW50aXR5IGFuZCBDQSBjZXJ0aWZpY2F0ZXMgdG8gYWNj
ZXNzDQo+IMKgwqAgaW5mb3JtYXRpb24gYWJvdXQgdGhlIGlzc3VlciBvZiB0aGUgY2VydGlmaWNh
dGUgaW4gd2hpY2ggdGhlDQo+IMKgwqAgZXh0ZW5zaW9uIGFwcGVhcnMuwqAgRm9yIGV4YW1wbGUs
IGl0IGNhbiBiZSB1c2VkIHRvIHByb3ZpZGUgdGhlDQo+IMKgwqAgYWRkcmVzcyBvZiB0aGUgT0NT
UCByZXNwb25kZXIgZnJvbSB3aGVyZSByZXZvY2F0aW9uIHN0YXR1cyBvZiB0aGUNCj4gwqDCoCBj
ZXJ0aWZpY2F0ZSAoaW4gd2hpY2ggdGhlIGV4dGVuc2lvbiBhcHBlYXJzKSBjYW4gYmUgY2hlY2tl
ZC4gSXQgY2FuDQo+IMKgwqAgYWxzbyBiZSB1c2VkIHRvIG9idGFpbiB0aGUgaXNzdWVyIGNlcnRp
ZmljYXRlLsKgIFRodXMsIHRoZSBBSUENCj4gwqDCoCBleHRlbnNpb24gY2FuIHJlZHVjZSB0aGUg
c2l6ZSBvZiB0aGUgY2VydGlmaWNhdGUgY2hhaW4gYnkgb25seQ0KPiDCoMKgIGluY2x1ZGluZyBh
IHBvaW50ZXIgdG8gdGhlIGlzc3VlciBjZXJ0aWZpY2F0ZSBpbnN0ZWFkIG9mIGluY2x1ZGluZw0K
PiDCoMKgIHRoZSBlbnRpcmUgaXNzdWVyIGNlcnRpZmljYXRlLsKgIEhvd2V2ZXIsIGl0IHJlcXVp
cmVzIHRoZSBzaWRlDQo+IMKgwqAgcmVjZWl2aW5nIHRoZSBjZXJ0aWZpY2F0ZSBjb250YWluaW5n
IHRoZSBleHRlbnNpb24gdG8gaGF2ZSBuZXR3b3JrDQo+IMKgwqAgY29ubmVjdGl2aXR5LsKgIE5h
dHVyYWxseSwgc3VjaCBpbmRpcmVjdGlvbiBjYW5ub3QgYmUgdXNlZCBmb3IgdGhlDQo+IMKgwqAg
c2VydmVyIGNlcnRpZmljYXRlIChzaW5jZSB0aGUgRUFQIHBlZXIgaW4gbW9zdCBkZXBsb3ltZW50
cyBkb2VzIG5vdA0KPiDCoMKgIGhhdmUgbmV0d29yayBjb25uZWN0aXZpdHkgYmVmb3JlIGF1dGhl
bg0KDQpMZXQgbWUga25vdyB3aGF0IHlvdSB0aGluay4gSSBhbSBub3QgYW4gZXhwZXJ0IG9uIHF1
YW50dW0gY3J5cHRvZ3JhcGh5IA0Kb3Igb24gdGhlIEFJQSBleHRlbnNpb24uIEkgd2lsbCB3YWl0
IGZvciBhbGwgdGhlIGNvbW1lbnRzIHRvIGNvbWUgaW4gDQpiZWZvcmUgc3VibWl0dGluZyBhIG5l
dyB2ZXJzaW9uLg0KDQotLU1vaGl0DQoNCk9uIDEwLzMwLzIwIDU6MDQgQU0sIEJlbmphbWluIEth
ZHVrIHdyb3RlOg0KPiBIaSBTdGVmYW4sDQo+DQo+IFRoYW5rcyBmb3IgdGhlIHJldmlldzsgaXQg
cmFpc2VzIHNvbWUgZ29vZCB0b3BpY3MuDQo+IFJlcGx5aW5nIG9uIGEgY291cGxlIHBvaW50cy4u
Lg0KPg0KPiBPbiBUaHUsIE9jdCAyOSwgMjAyMCBhdCAwNDoxMzowMlBNIC0wNzAwLCBTdGVmYW4g
U2FudGVzc29uIHZpYSBEYXRhdHJhY2tlciB3cm90ZToNCj4+IFJldmlld2VyOiBTdGVmYW4gU2Fu
dGVzc29uDQo+PiBSZXZpZXcgcmVzdWx0OiBIYXMgTml0cw0KPj4NCj4+IFRoZSBkb2N1bWVudCBp
biBnZW5lcmFsIGlzIGdvb2QgYW5kIHdlbGwgd3JpdHRlbi4NCj4+DQo+PiBTb21lIG5pdHMgbmVl
ZHMgYXR0ZW50aW9uIGJlZm9yZSBwdWJsaWNhdGlvbiBhcyB0aGUgZ2VuZXJhbCByZXZpZXcgYWxz
byBwb2ludHMNCj4+IG91dC4gRXggaW4gdGhlIGFic3RyYWN0ICJUaGlzIGRvY3VtZW50IGxvb2tz
IGF0IHRoZSB0aGlzIHByb2JsZW0iDQo+Pg0KPj4gU29tZSBhYmJyZXZpYXRpb25zIG5lZWRzIHRv
IGJlIHNwZWxsZWQgb3V0IGF0IGZpcnN0IHVzYWdlLCBzdWNoIGFzIE1UVSAoTWF4aW11bQ0KPj4g
VHJhbnNtaXNzaW9uIFVuaXQpDQo+IE1UVSBtYXkgYWN0dWFsbHkgYmUgb2theTsgcGVyDQo+IGh0
dHBzOi8vd3d3LnJmYy1lZGl0b3Iub3JnL21hdGVyaWFscy9hYmJyZXYuZXhwYW5zaW9uLnR4dCBp
dCBpcyBtYXJrZWQgYXMNCj4gIndlbGwta25vd24iIGFuZCBkb2VzIG5vdCBhbHdheXMgbmVlZCB0
byBiZSBleHBhbmRlZC4NCj4NCj4+IE9uIHRoZSBjb250ZW50IGl0c2VsZiBJIGhhdmUgdHdvIHF1
ZXN0aW9uczoNCj4+DQo+PiAtIFdvdWxkbid0IGl0IGJlIHJlbGV2YW50IHRvIGFsc28gZGlzY3Vz
cyB0aGUgcmlza3Mgd2l0aCByZWdhcmQgdG8gaW50cm9kdWN0aW9uDQo+PiBvZiBxdWFudHVtIHNh
ZmUgY3J5cHRvLCBpZiB0aGF0IGxlYWRzIHRvIHNpZ25pZmljYW50bHkgaW5jcmVhc2VkIGtleSBz
aXplcz8gSXQNCj4+IGNvdWxkIGJlIHRyb3VibGVzb21lIGlmIHRyYW5zaXRpb24gdG8gYSBzYWZl
ciBjcnlwdG8gaXMgbWFkZSBpbXBvc3NpYmxlIGR1ZSB0bw0KPj4gc2l6ZSBsaW1pdGF0aW9ucy4g
LSBXb3VsZCBpdCBiZSByZWxldmFudCB0byBkaXNjdXNzIHVzYWdlIG9mIEFJQSBleHRlbnNpb24g
YXMNCj4+IG1lYW5zIG9mIHBvc3NpYmx5IGV4Y2x1ZGluZyBpbnRlcm1lZGlhcnkgY2VydHMgZnJv
bSB0aGUgcGF0aCBhcyB0aGV5IGNvdWxkIGJlDQo+PiBsb2NhdGVkIHVzaW5nIEFJQT8NCj4+DQo+
PiBGaW5hbGx5LCBJIGFncmVlIHdpdGggdGhlIGdlbmVyYWwgcmV2aWV3IHRoYXQgdGhpcyBkb2N1
bWVudCByZWZlcmVuY2UgcXVpdGUNCj4+IHNvbWUgd29yayBpbiBwcm9ncmVzcy4gSWYgdGhpcyBk
b2N1bWVudCBpcyB0byBiZSBwdWJsaXNoZWQgYmVmb3JlIHRoZXNlDQo+PiByZWZlcmVuY2VkIHdv
cmtzIGFyZSBjb25jbHVkZWQsIGFyZSB0aGVyZSBhbHRlcm5hdGl2ZXMgdG8gbWFrZSB0aGUgc2Ft
ZSBwb2ludD8NCj4gVGhleSBzZWVtIHRvIG1vc3RseSBiZSBpbmZvcm1hdGl2ZSByZWZlcmVuY2Vz
LCBhbmQgc28gd291bGQgbm90IHJlcXVpcmUgdXMNCj4gdG8gaG9sZCBwdWJsaWNhdGlvbiBvZiB0
aGlzIGRvY3VtZW50LiAgSXQgaXMgcHJvYmFibHkgc3RpbGwgd29ydGgNCj4gY29uc2lkZXJpbmcg
aWYgdGhlcmUgYXJlIGFsdGVybmF0aXZlcyBhbnl3YXksIHRob3VnaC4NCj4NCj4gLUJlbg0KPg0K
PiBfX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fXw0KPiBFbXUg
bWFpbGluZyBsaXN0DQo+IEVtdUBpZXRmLm9yZw0KPiBodHRwczovL3d3dy5pZXRmLm9yZy9tYWls
bWFuL2xpc3RpbmZvL2VtdQ0K


From nobody Fri Oct 30 07:17:13 2020
Return-Path: <barryleiba@gmail.com>
X-Original-To: emu@ietfa.amsl.com
Delivered-To: emu@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id E39EE3A0ED6; Fri, 30 Oct 2020 07:17:11 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.399
X-Spam-Level: 
X-Spam-Status: No, score=-1.399 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, FREEMAIL_FORGED_FROMDOMAIN=0.25, FREEMAIL_FROM=0.001, HEADER_FROM_DIFFERENT_DOMAINS=0.25, RCVD_IN_MSPIKE_H2=-0.001, SPF_HELO_NONE=0.001, SPF_PASS=-0.001, URIBL_BLOCKED=0.001] autolearn=no autolearn_force=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 JocwFO0BDR5k; Fri, 30 Oct 2020 07:17:10 -0700 (PDT)
Received: from mail-ua1-f53.google.com (mail-ua1-f53.google.com [209.85.222.53]) (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 061033A0ED5; Fri, 30 Oct 2020 07:17:09 -0700 (PDT)
Received: by mail-ua1-f53.google.com with SMTP id 52so1761235uaj.4; Fri, 30 Oct 2020 07:17:09 -0700 (PDT)
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:mime-version:references:in-reply-to:from:date :message-id:subject:to:cc:content-transfer-encoding; bh=9SYeoVqgvFqRL1K1h17zDh5+0Z6gHieIw5BaPGItrTE=; b=eRLLtrh+Y3CE2a79S1HKz68VRGfs9PYx37zpdfuv2/EhoedfctvWF17nRpPnVW9bQ/ 63Yvc8oo0LrGvAklgh+FFXKU5Bdko9AITfUOpxmARXdwbBRcG7RzYn3+WMS+OBPxVVTA 129q+rYClOdeup52TKa9IiFrMkTnQ2X0OJt6o3cnU3jDxkOY106JLvY72U46DyH//saZ vtKk/JqInVbteXeckAwRGjFhwF70EmSCKR5DyrPzJMhKXz5Hg+UY1gkpAPAWRWmCWbDG zFmuX/I2SC5r8pI99wNQFTXOD0fjqFhvRZXs8ypYrPDWIEldscOoWdy/YwMRmeWf/fdF SC/g==
X-Gm-Message-State: AOAM532brmdqU6ebcjkdD5N8kd5EEuO2ykqC7JOqNAGy+f4Rk9HbvUy9 x9Dfj7w80P0sf/yZBj4KZew91gw2vOk86RBUH04=
X-Google-Smtp-Source: ABdhPJy3ZIPtQEOACTuzltvtCUutTW3GPTmcGnPOGeeEeBgli1034dftsq8bbOUvEUoCj9haychF6JKHA5IPvWBGH0I=
X-Received: by 2002:ab0:308f:: with SMTP id h15mr1451757ual.49.1604067428764;  Fri, 30 Oct 2020 07:17:08 -0700 (PDT)
MIME-Version: 1.0
References: <160391287468.14554.8990471287012823249@ietfa.amsl.com> <dfb630f1-f42d-0589-ffc7-e860b2782fed@ericsson.com>
In-Reply-To: <dfb630f1-f42d-0589-ffc7-e860b2782fed@ericsson.com>
From: Barry Leiba <barryleiba@computer.org>
Date: Fri, 30 Oct 2020 10:16:57 -0400
Message-ID: <CALaySJKRb1z=TfVWNz1JMmzoBxpEMBozOxyZweZ5bCoKrK7UfQ@mail.gmail.com>
To: Mohit Sethi M <mohit.m.sethi@ericsson.com>
Cc: The IESG <iesg@ietf.org>,  "draft-ietf-emu-eaptlscert@ietf.org" <draft-ietf-emu-eaptlscert@ietf.org>,  "emu-chairs@ietf.org" <emu-chairs@ietf.org>, "emu@ietf.org" <emu@ietf.org>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
Archived-At: <https://mailarchive.ietf.org/arch/msg/emu/aB-LwGsH22LjAQM0hMKdymE0dmo>
Subject: Re: [Emu] Barry Leiba's No Objection on draft-ietf-emu-eaptlscert-06: (with COMMENT)
X-BeenThere: emu@ietf.org
X-Mailman-Version: 2.1.29
Precedence: list
List-Id: "EAP Methods Update \(EMU\)" <emu.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/emu>, <mailto:emu-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/emu/>
List-Post: <mailto:emu@ietf.org>
List-Help: <mailto:emu-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/emu>, <mailto:emu-request@ietf.org?subject=subscribe>
X-List-Received-Date: Fri, 30 Oct 2020 14:17:12 -0000

Thanks, Mohit, for addressing my comments... and I'm glad you also
added text about the effect of quantum-safe algorithms on key and
signature sizes.

On the document status issue, I'd like to hear what other working
group participants think, and also what Roman's thoughts are.

Barry

On Fri, Oct 30, 2020 at 4:12 AM Mohit Sethi M
<mohit.m.sethi@ericsson.com> wrote:
>
> Hi Barry,
>
> Thank you for the careful review. I have updated the draft in github
> (https://github.com/emu-wg/eaptls-longcert). Here is the diff for your
> convenience:
> https://tools.ietf.org/rfcdiff?url1=3Dhttps://tools.ietf.org/id/draft-iet=
f-emu-eaptlscert.txt&url2=3Dhttps://emu-wg.github.io/eaptls-longcert/draft-=
ietf-emu-eaptlscert.txt.
> I will wait for all the comments to come in before submitting a new versi=
on.
>
> Regarding your comment of informational vs. applicability statement: I
> am not opposed to the idea. I am happy to follow whatever the IESG
> recommends.
>
> --Mohit
>
> On 10/28/20 9:21 PM, Barry Leiba via Datatracker wrote:
> > Barry Leiba has entered the following ballot position for
> > draft-ietf-emu-eaptlscert-06: No Objection
> >
> > When responding, please keep the subject line intact and reply to all
> > email addresses included in the To and CC lines. (Feel free to cut this
> > introductory paragraph, however.)
> >
> >
> > Please refer to https://www.ietf.org/iesg/statement/discuss-criteria.ht=
ml
> > for more information about IESG DISCUSS and COMMENT positions.
> >
> >
> > The document, along with other ballot positions, can be found here:
> > https://datatracker.ietf.org/doc/draft-ietf-emu-eaptlscert/
> >
> >
> >
> > ----------------------------------------------------------------------
> > COMMENT:
> > ----------------------------------------------------------------------
> >
> > Thanks for this; it will be useful to have this issue fixed.
> >
> > There=E2=80=99s something I=E2=80=99d like to discuss, but without maki=
ng it a blocking DISCUSS:
> > While I understand the reason for putting this forward as Informational=
, it
> > does strike me more as a Standards Track Applicability Statement.  BCP =
9 says
> > (in RFC 2026 Section 3.2):
> >
> >     An Applicability Statement specifies how, and under what
> >     circumstances, one or more TSs may be applied to support a particul=
ar
> >     Internet capability.
> >
> > Reading the rest of Section 3.2 as well, I think that it fits exactly w=
hat
> > you=E2=80=99re doing with this document: the document is saying that th=
ere=E2=80=99s an
> > interoperability problem with large certs and long chains, and here are=
 things
> > to do in order to make that work.  Let=E2=80=99s please have a brief di=
scussion about
> > whether this should instead be published at Proposed Standard as an AS.
> >
> > =E2=80=94=E2=80=94=E2=80=94=E2=80=94=E2=80=94
> >
> > Below are some nits that I hope you=E2=80=99ll consider, but there=E2=
=80=99s no need to respond
> > in detail here; please do as you think best.
> >
> > =E2=80=94 Section 1 =E2=80=94
> >
> >     vendor specific EAP methods.
> >
> > Need a hyphen in =E2=80=9Cvendor-specific=E2=80=9D.
> >
> >     EAP-TLS
> >     deployments typically authenticates both the EAP peer and the EAP
> >
> > Make it =E2=80=9Cauthenticate=E2=80=9D.
> >
> >     Section 3.1 of [RFC3748] states that EAP implementations can assume=
 a
> >     MTU of at least 1020 octets from lower layers.
> >
> > Unless you have a way of pronouncing =E2=80=9CMTU=E2=80=9D that I don=
=E2=80=99t, make it =E2=80=9Can MTU=E2=80=9D.
> >
> >     Such fragmentation can not only negatively
> >     affect the latency, but also results in other challenges.
> >
> > The =E2=80=9Ccan=E2=80=9D is misplaced; make it =E2=80=9Cnot only can a=
ffect=E2=80=9D.
> >
> > =E2=80=94 Section 2 =E2=80=94
> >
> >     The document additionally uses the terms trust anchor and
> >     certification path defined in [RFC5280].
> >
> > I would put =E2=80=9Ctrust anchor=E2=80=9D and =E2=80=9Ccertification p=
ath=E2=80=9D in quotes here.
> >
> > =E2=80=94 Section 3 =E2=80=94
> >
> >     Certificate sizes can however be large
> >
> > Commas are needed both before and after =E2=80=9Chowever=E2=80=9D.  Als=
o, the list talks about
> > a singular =E2=80=9Ccertificate=E2=80=9D, so the lead-in should match t=
hat (and you don=E2=80=99t need
> > to say that a *size* can be large): =E2=80=9CA certificate can, however=
, be large for a
> > number of reasons:=E2=80=9D
> >
> > The list is also not parallel (the third item, in particular, is not li=
ke the
> > others).  I would make the whole list be complete sentences, like this,
> > referring to =E2=80=9Ca certificate=E2=80=9D in the lead-in:
> >
> > NEW
> >     o  It can have a long Subject Alternative Name field.
> >
> >     o  It can have long Public Key and Signature fields.
> >
> >     o  It can contain multiple object identifiers (OID) that indicate t=
he
> >        permitted uses of the certificate as noted in Section 5.3 of
> >        [RFC5216].  Most implementations verify the presence of these OI=
Ds
> >        for successful authentication.
> >
> >     o  It can contain multiple user groups.
> > END
> >
> > =E2=80=94 Section 4.1 =E2=80=94
> >
> > Throughout this paragraph you refer to =E2=80=9Csize of public keys=E2=
=80=9D and =E2=80=9Csize of
> > digital signatures=E2=80=9D.  It=E2=80=99s a really nitty nit, but I wo=
uld make these all
> > singular, because we=E2=80=99re really talking about the size of an ind=
ividual public
> > key or digital signature, not the size of a collection of them.
> >
> >     authentication which can alleviate the problem of authenticators
> >
> > There needs to be a comma before =E2=80=9Cwhich=E2=80=9D.
> >
> >     ECC based cipher suites with existing code can significantly
> >
> > Hyphenate =E2=80=9CECC-based=E2=80=9D.
> >
> > =E2=80=94 Section 4.1.1 =E2=80=94
> >
> >     OIDs are used lavishly in X.509 certificates
> >
> > I like it: =E2=80=9Clavishly=E2=80=9D is not a word we often see in RFC=
s.  :-)
> >
> >        DNs
> >        used in the issuer and subject fields as well as numerous
> >        extensions.
> >
> > This is not a complete sentence; please fix that (I think you=E2=80=99r=
e just missing
> > =E2=80=9Care=E2=80=9D after =E2=80=9CDNs=E2=80=9D).
> >
> >     CN=3DCoolest IoT Gadget Ever
> >
> > Oh!  I want that!
> >
> >
> >
> > _______________________________________________
> > Emu mailing list
> > Emu@ietf.org
> > https://www.ietf.org/mailman/listinfo/emu


From nobody Fri Oct 30 07:47:31 2020
Return-Path: <internet-drafts@ietf.org>
X-Original-To: emu@ietf.org
Delivered-To: emu@ietfa.amsl.com
Received: from ietfa.amsl.com (localhost [IPv6:::1]) by ietfa.amsl.com (Postfix) with ESMTP id 166F93A0EFA; Fri, 30 Oct 2020 07:47:24 -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>
Cc: emu@ietf.org
X-Test-IDTracker: no
X-IETF-IDTracker: 7.21.0
Auto-Submitted: auto-generated
Precedence: bulk
Reply-To: emu@ietf.org
Message-ID: <160406924404.28733.3969815842864147055@ietfa.amsl.com>
Date: Fri, 30 Oct 2020 07:47:24 -0700
Archived-At: <https://mailarchive.ietf.org/arch/msg/emu/2jD25Q-d-F1CS5L3ZCIfd-hYAgs>
Subject: [Emu] I-D Action: draft-ietf-emu-aka-pfs-05.txt
X-BeenThere: emu@ietf.org
X-Mailman-Version: 2.1.29
List-Id: "EAP Methods Update \(EMU\)" <emu.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/emu>, <mailto:emu-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/emu/>
List-Post: <mailto:emu@ietf.org>
List-Help: <mailto:emu-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/emu>, <mailto:emu-request@ietf.org?subject=subscribe>
X-List-Received-Date: Fri, 30 Oct 2020 14:47:24 -0000

A New Internet-Draft is available from the on-line Internet-Drafts directories.
This draft is a work item of the EAP Method Update WG of the IETF.

        Title           : Perfect-Forward Secrecy for the Extensible Authentication Protocol Method for Authentication and Key Agreement (EAP-AKA' PFS)
        Authors         : Jari Arkko
                          Karl Norrman
                          Vesa Torvinen
	Filename        : draft-ietf-emu-aka-pfs-05.txt
	Pages           : 26
	Date            : 2020-10-30

Abstract:
   Many different attacks have been reported as part of revelations
   associated with pervasive surveillance.  Some of the reported attacks
   involved compromising smart cards, such as attacking SIM card
   manufacturers and operators in an effort to compromise shared secrets
   stored on these cards.  Since the publication of those reports,
   manufacturing and provisioning processes have gained much scrutiny
   and have improved.  However, the danger of resourceful attackers for
   these systems is still a concern.

   This specification is an optional extension to the EAP-AKA'
   authentication method which was defined in [I-D.ietf-emu-rfc5448bis].
   The extension, when negotiated, provides Perfect Forward Secrecy for
   the session key generated as a part of the authentication run in EAP-
   AKA'.  This prevents an attacker who has gained access to the long-
   term pre-shared secret in a SIM card from being able to decrypt any
   past communications.  In addition, if the attacker stays merely a
   passive eavesdropper, the extension prevents attacks against future
   sessions.  This forces attackers to use active attacks instead.


The IETF datatracker status page for this draft is:
https://datatracker.ietf.org/doc/draft-ietf-emu-aka-pfs/

There are also htmlized versions available at:
https://tools.ietf.org/html/draft-ietf-emu-aka-pfs-05
https://datatracker.ietf.org/doc/html/draft-ietf-emu-aka-pfs-05

A diff from the previous version is available at:
https://www.ietf.org/rfcdiff?url2=draft-ietf-emu-aka-pfs-05


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 Fri Oct 30 07:48:46 2020
Return-Path: <stefan@aaa-sec.com>
X-Original-To: emu@ietfa.amsl.com
Delivered-To: emu@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id DD3D53A0B1F for <emu@ietfa.amsl.com>; Fri, 30 Oct 2020 07:48:40 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.894
X-Spam-Level: 
X-Spam-Status: No, score=-1.894 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, MIME_QP_LONG_LINE=0.001, RCVD_IN_MSPIKE_H4=0.001, RCVD_IN_MSPIKE_WL=0.001, SPF_HELO_NONE=0.001, SPF_NONE=0.001, URIBL_BLOCKED=0.001] autolearn=unavailable autolearn_force=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 GL5jmCxBmTVD for <emu@ietfa.amsl.com>; Fri, 30 Oct 2020 07:48:38 -0700 (PDT)
Received: from smtp.outgoing.loopia.se (smtp.outgoing.loopia.se [93.188.3.37]) (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 36CF93A09EE for <emu@ietf.org>; Fri, 30 Oct 2020 07:48:37 -0700 (PDT)
Received: from s807.loopia.se (localhost [127.0.0.1]) by s807.loopia.se (Postfix) with ESMTP id C69B410D0373 for <emu@ietf.org>; Fri, 30 Oct 2020 15:40:29 +0100 (CET)
Received: from s499.loopia.se (unknown [172.22.191.6]) by s807.loopia.se (Postfix) with ESMTP id A78AC2EB3BC6; Fri, 30 Oct 2020 15:40:29 +0100 (CET)
Received: from s475.loopia.se (unknown [172.22.191.5]) by s499.loopia.se (Postfix) with ESMTP id A1ACD1CE5F2A; Fri, 30 Oct 2020 15:40:29 +0100 (CET)
X-Virus-Scanned: amavisd-new at amavis.loopia.se
Received: from s498.loopia.se ([172.22.191.6]) by s475.loopia.se (s475.loopia.se [172.22.190.15]) (amavisd-new, port 10024) with LMTP id wTSvIyf-K5hE; Fri, 30 Oct 2020 15:40:28 +0100 (CET)
X-Loopia-Auth: user
X-Loopia-User: mailstore2@aaa-sec.com
X-Loopia-Originating-IP: 85.235.7.89
Received: from [192.168.2.50] (gw.aaa-sec.ideon.se [85.235.7.89]) (Authenticated sender: mailstore2@aaa-sec.com) by s498.loopia.se (Postfix) with ESMTPSA id 577B94893BB; Fri, 30 Oct 2020 15:40:28 +0100 (CET)
User-Agent: Microsoft-MacOutlook/16.42.20101102
Date: Fri, 30 Oct 2020 15:40:26 +0100
From: Stefan Santesson <stefan@aaa-sec.com>
To: Mohit Sethi M <mohit.m.sethi@ericsson.com>, Benjamin Kaduk <kaduk@mit.edu>
CC: "last-call@ietf.org" <last-call@ietf.org>, "draft-ietf-emu-eaptlscert.all@ietf.org" <draft-ietf-emu-eaptlscert.all@ietf.org>, "emu@ietf.org" <emu@ietf.org>, "secdir@ietf.org" <secdir@ietf.org>
Message-ID: <2F8F716A-C063-4DF4-8384-BBD59C636C8A@aaa-sec.com>
Thread-Topic: [Emu] Secdir last call review of draft-ietf-emu-eaptlscert-06
References: <160401318284.11167.6795105917637378641@ietfa.amsl.com> <20201030030415.GE39170@kduck.mit.edu> <12167567-9dc5-6161-abef-826b0a8b6602@ericsson.com>
In-Reply-To: <12167567-9dc5-6161-abef-826b0a8b6602@ericsson.com>
Mime-version: 1.0
Content-type: text/plain; charset="UTF-8"
Content-transfer-encoding: quoted-printable
Archived-At: <https://mailarchive.ietf.org/arch/msg/emu/4HBu6CIYC61io6SjMsL0wRwSJ24>
Subject: Re: [Emu] Secdir last call review of draft-ietf-emu-eaptlscert-06
X-BeenThere: emu@ietf.org
X-Mailman-Version: 2.1.29
Precedence: list
List-Id: "EAP Methods Update \(EMU\)" <emu.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/emu>, <mailto:emu-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/emu/>
List-Post: <mailto:emu@ietf.org>
List-Help: <mailto:emu-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/emu>, <mailto:emu-request@ietf.org?subject=subscribe>
X-List-Received-Date: Fri, 30 Oct 2020 14:48:41 -0000

Hi,

I think the text is great.=20
However I'm not entirely convinced that AIA requires network connectivity a=
t all times.
The AIA CA cert url is static and works fine as identifier for a locally ca=
ched cert
The fact that it is the correct cert is assured by the path validation proc=
ess.
As such, the AIA works fine with a http cache implementation or similar or =
any other solution using locally stored data.
If used in a local corporate context, a cache mechanism could be provided w=
ith pre-loaded relevant certs.

But I don=E2=80=99t know how this may or may not interoperate with deployed base =
of EAP implementations.

Stefan Santesson=20

=EF=BB=BFOn 2020-10-30, 14:48, "Mohit Sethi M" <mohit.m.sethi@ericsson.com> wrote=
:

    Hi Stefan,

    Thank you for the review. I have updated the draft in github=20
    (https://github.com/emu-wg/eaptls-longcert). Here is the diff for your=20
    convenience:=20
    https://tools.ietf.org/rfcdiff?url1=3Dhttps://tools.ietf.org/id/draft-iet=
f-emu-eaptlscert.txt&url2=3Dhttps://emu-wg.github.io/eaptls-longcert/draft-iet=
f-emu-eaptlscert.txt.

    The following text was added:

    >    The size of certificates (and certificate chains) may also increas=
e
    >    manifold in the future with the introduction of quantum-safe
    >    cryptography.  For example, lattice-based cryptography would have
    >    public keys of approximately 1000 bytes and signatures of
    >    approximately 2000 bytes.
    and in Section 4.2.5

    >    The Authority Information Access (AIA) extension specified in
    >    [RFC5280] can be used with end-entity and CA certificates to acces=
s
    >    information about the issuer of the certificate in which the
    >    extension appears.  For example, it can be used to provide the
    >    address of the OCSP responder from where revocation status of the
    >    certificate (in which the extension appears) can be checked. It ca=
n
    >    also be used to obtain the issuer certificate.  Thus, the AIA
    >    extension can reduce the size of the certificate chain by only
    >    including a pointer to the issuer certificate instead of including
    >    the entire issuer certificate.  However, it requires the side
    >    receiving the certificate containing the extension to have network
    >    connectivity.  Naturally, such indirection cannot be used for the
    >    server certificate (since the EAP peer in most deployments does no=
t
    >    have network connectivity before authen

    Let me know what you think. I am not an expert on quantum cryptography=20
    or on the AIA extension. I will wait for all the comments to come in=20
    before submitting a new version.

    --Mohit

    On 10/30/20 5:04 AM, Benjamin Kaduk wrote:
    > Hi Stefan,
    >
    > Thanks for the review; it raises some good topics.
    > Replying on a couple points...
    >
    > On Thu, Oct 29, 2020 at 04:13:02PM -0700, Stefan Santesson via Datatr=
acker wrote:
    >> Reviewer: Stefan Santesson
    >> Review result: Has Nits
    >>
    >> The document in general is good and well written.
    >>
    >> Some nits needs attention before publication as the general review a=
lso points
    >> out. Ex in the abstract "This document looks at the this problem"
    >>
    >> Some abbreviations needs to be spelled out at first usage, such as M=
TU (Maximum
    >> Transmission Unit)
    > MTU may actually be okay; per
    > https://www.rfc-editor.org/materials/abbrev.expansion.txt it is marke=
d as
    > "well-known" and does not always need to be expanded.
    >
    >> On the content itself I have two questions:
    >>
    >> - Wouldn't it be relevant to also discuss the risks with regard to i=
ntroduction
    >> of quantum safe crypto, if that leads to significantly increased key=
 sizes? It
    >> could be troublesome if transition to a safer crypto is made impossi=
ble due to
    >> size limitations. - Would it be relevant to discuss usage of AIA ext=
ension as
    >> means of possibly excluding intermediary certs from the path as they=
 could be
    >> located using AIA?
    >>
    >> Finally, I agree with the general review that this document referenc=
e quite
    >> some work in progress. If this document is to be published before th=
ese
    >> referenced works are concluded, are there alternatives to make the s=
ame point?
    > They seem to mostly be informative references, and so would not requi=
re us
    > to hold publication of this document.  It is probably still worth
    > considering if there are alternatives anyway, though.
    >
    > -Ben
    >
    > _______________________________________________
    > Emu mailing list
    > Emu@ietf.org
    > https://www.ietf.org/mailman/listinfo/emu



From nobody Fri Oct 30 07:50:48 2020
Return-Path: <internet-drafts@ietf.org>
X-Original-To: emu@ietf.org
Delivered-To: emu@ietfa.amsl.com
Received: from ietfa.amsl.com (localhost [IPv6:::1]) by ietfa.amsl.com (Postfix) with ESMTP id EEACA3A09EE; Fri, 30 Oct 2020 07:50:43 -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>
Cc: emu@ietf.org
X-Test-IDTracker: no
X-IETF-IDTracker: 7.21.0
Auto-Submitted: auto-generated
Precedence: bulk
Reply-To: emu@ietf.org
Message-ID: <160406944393.2140.398488693037034910@ietfa.amsl.com>
Date: Fri, 30 Oct 2020 07:50:43 -0700
Archived-At: <https://mailarchive.ietf.org/arch/msg/emu/beJ6J32i80saHqMimI0141nSeRw>
Subject: [Emu] I-D Action: draft-ietf-emu-rfc5448bis-08.txt
X-BeenThere: emu@ietf.org
X-Mailman-Version: 2.1.29
List-Id: "EAP Methods Update \(EMU\)" <emu.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/emu>, <mailto:emu-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/emu/>
List-Post: <mailto:emu@ietf.org>
List-Help: <mailto:emu-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/emu>, <mailto:emu-request@ietf.org?subject=subscribe>
X-List-Received-Date: Fri, 30 Oct 2020 14:50:44 -0000

A New Internet-Draft is available from the on-line Internet-Drafts directories.
This draft is a work item of the EAP Method Update WG of the IETF.

        Title           : Improved Extensible Authentication Protocol Method for 3GPP Mobile Network Authentication and Key Agreement (EAP-AKA')
        Authors         : Jari Arkko
                          Vesa Lehtovirta
                          Vesa Torvinen
                          Pasi Eronen
	Filename        : draft-ietf-emu-rfc5448bis-08.txt
	Pages           : 49
	Date            : 2020-10-30

Abstract:
   The 3GPP Mobile Network Authentication and Key Agreement (AKA) is the
   primary authentication mechanism for devices wishing to access mobile
   networks.  RFC 4187 (EAP-AKA) made the use of this mechanism possible
   within the Extensible Authentication Protocol (EAP) framework.  RFC
   5448 (EAP-AKA') was an improved version of EAP-AKA.

   This memo replaces the specification of EAP-AKA'.  EAP-AKA' was
   defined in RFC 5448 and updated EAP-AKA RFC 4187.  As such this
   document obsoletes RFC 5448 and updates RFC 4187.

   EAP-AKA' differs from EAP-AKA by providing a key derivation function
   that binds the keys derived within the method to the name of the
   access network.  The key derivation function has been defined in the
   3rd Generation Partnership Project (3GPP).  EAP-AKA' allows its use
   in EAP in an interoperable manner.  EAP-AKA' also updates the
   algorithm used in hash functions, as it employs SHA-256 / HMAC-
   SHA-256 instead of SHA-1 / HMAC-SHA-1 as in EAP-AKA.

   This version of EAP-AKA' specification specifies the protocol
   behaviour for both 4G and 5G deployments, whereas the previous
   version only did this for 4G.


The IETF datatracker status page for this draft is:
https://datatracker.ietf.org/doc/draft-ietf-emu-rfc5448bis/

There are also htmlized versions available at:
https://tools.ietf.org/html/draft-ietf-emu-rfc5448bis-08
https://datatracker.ietf.org/doc/html/draft-ietf-emu-rfc5448bis-08

A diff from the previous version is available at:
https://www.ietf.org/rfcdiff?url2=draft-ietf-emu-rfc5448bis-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 Fri Oct 30 09:26:23 2020
Return-Path: <joe@salowey.net>
X-Original-To: emu@ietfa.amsl.com
Delivered-To: emu@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id E37263A0FCF for <emu@ietfa.amsl.com>; Fri, 30 Oct 2020 09:26:21 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.898
X-Spam-Level: 
X-Spam-Status: No, score=-1.898 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, HTML_MESSAGE=0.001, SPF_HELO_NONE=0.001, SPF_PASS=-0.001, URIBL_BLOCKED=0.001] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (2048-bit key) header.d=salowey-net.20150623.gappssmtp.com
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 D8J9eIT2pke5 for <emu@ietfa.amsl.com>; Fri, 30 Oct 2020 09:26:20 -0700 (PDT)
Received: from mail-qk1-x72e.google.com (mail-qk1-x72e.google.com [IPv6:2607:f8b0:4864:20::72e]) (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 2D6413A0FD7 for <emu@ietf.org>; Fri, 30 Oct 2020 09:26:13 -0700 (PDT)
Received: by mail-qk1-x72e.google.com with SMTP id p3so5337040qkk.7 for <emu@ietf.org>; Fri, 30 Oct 2020 09:26:13 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=salowey-net.20150623.gappssmtp.com; s=20150623; h=mime-version:references:in-reply-to:from:date:message-id:subject:to :cc; bh=lgCbZ7AxY9W8d14ot0gDPHoo4VSDT9N7MYy1KkT+bqg=; b=JbrEWsJLEZhpAPZ8sMYy/IfnUrL6h8+mtMjzYojX4V4q3mTGiRM/lR3Yq0KKzE9Zgd O7D6Hoz5PNzd6FTAZZfTAWkgmy9jk61fX1z8fwv6vx08xbJUspq1aRAsAB8wJw1Bti0E /6k+JBU8lS8jCwj9vyC1bzY7+t89Ukb7C6O0UXY9KgDgyI43fbjagfl7deh+Ah5x+YXg IO5N2KSk0gIV8LFwSXXXI/OPpGoPXEYfI8hPOgxlUjxmFWXauSibS9GONxujRfmXgrwG kBGwQrv4lmfD/Yz6j2Jvw2E5xAbHzEdVe333/8MPqsvvDi9fZnzhWl3DIVyEgk7KqygP y4ug==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:mime-version:references:in-reply-to:from:date :message-id:subject:to:cc; bh=lgCbZ7AxY9W8d14ot0gDPHoo4VSDT9N7MYy1KkT+bqg=; b=SfRFiciVm20yvVkgbHMhvd8krvM3gNgEhex/q2LUd8s4okQWE8sRGLr/G2vFXvPjuQ nqxaYUBucvtZ8mG4T79uYR0T4Kp1SacGWh8yw3omvYv5eookfoxszSzNfsC+oo5APl+n mO66WWn5Y/r/s0e3kPMiWGfVj/fM2LvSph6kmpoMFgEHWgWNVQ7jP7HV2jl51yGZqCVv O7tgRn/sb4CfDJkoE+g0756ZYaQaV8N1rgB/5Y/CHpOVQTCFprBmKoiJkXBRrJVXSOSj 6s/9Hkuqf/7Inam4b5YDgXjPkObMAWUxsbl+YIWuBF/BXmD425ld2k3yXivNQs91u1s2 JgeQ==
X-Gm-Message-State: AOAM530Zp6Iuw6k1CJJIMigmbpCZz6d1IUDbKDyuLvLmYHEHg0CPEOLY GoO8B0phHBPzPWzqwPqU0XbW1aVtaWEXubPQRCV2hw==
X-Google-Smtp-Source: ABdhPJwSgH5CyqJRNQG1WUlZCfgCGyGmpc5o32q2z2RHpy8ajoUJRscV9fu+3f092zgziYllXDaddgp9BxK+ywPP2ZI=
X-Received: by 2002:a37:76c7:: with SMTP id r190mr2850586qkc.416.1604075171943;  Fri, 30 Oct 2020 09:26:11 -0700 (PDT)
MIME-Version: 1.0
References: <CAOgPGoDbsunLOxrnFxa8uMxG6JYObX_r5VLOvVib5QmFHGOrwA@mail.gmail.com> <4858.1604009572@localhost> <CAOgPGoDC8gyBLD4a7Ms-h823sZ5q6USpbE=6HXdVWo3TEVfoYA@mail.gmail.com> <4217.1604058293@localhost>
In-Reply-To: <4217.1604058293@localhost>
From: Joseph Salowey <joe@salowey.net>
Date: Fri, 30 Oct 2020 09:26:01 -0700
Message-ID: <CAOgPGoBpUkQuTRVB1GKYtgtFLsckbPfQkkvRVD+xERpgNDYyYg@mail.gmail.com>
To: Michael Richardson <mcr+ietf@sandelman.ca>
Cc: EMU WG <emu@ietf.org>
Content-Type: multipart/alternative; boundary="000000000000d12f3105b2e5da86"
Archived-At: <https://mailarchive.ietf.org/arch/msg/emu/4vou4CfJZXYhqke4yXIVEhLx-Xw>
Subject: Re: [Emu] Consensus Call on OCSP usage in draft-ietf-emu-eap-tls13-11
X-BeenThere: emu@ietf.org
X-Mailman-Version: 2.1.29
Precedence: list
List-Id: "EAP Methods Update \(EMU\)" <emu.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/emu>, <mailto:emu-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/emu/>
List-Post: <mailto:emu@ietf.org>
List-Help: <mailto:emu-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/emu>, <mailto:emu-request@ietf.org?subject=subscribe>
X-List-Received-Date: Fri, 30 Oct 2020 16:26:22 -0000

--000000000000d12f3105b2e5da86
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable

On Fri, Oct 30, 2020 at 4:44 AM Michael Richardson <mcr+ietf@sandelman.ca>
wrote:

>
> Joseph Salowey <joe@salowey.net> wrote:
>     >> I suggest:
>     >>
>     >> =E2=80=9CEAP-TLS servers supporting TLS 1.3 that use OCSP to do ce=
rtificate
>     >> recovation checks,  MUST implement Certificate Status Requests
> using OCSP
>     >> stapling as specified in Section 4.4.2.1 of [RFC8446].
>
>     > [Joe] Thanks Michael,  I think your suggestion is a better way to
> phrase it
>
> Just so that we are clear:  this mandates OCSP+stapling for systems that =
do
> revocation checks.
>
> Systems that don't do revocation checks (current mbedtls), therefore don'=
t
> need to do OCSP or stapling.
>

[Joe] That's not how I read your text.  I think your text mandates
OCSP+stapling for systems that use OCSP for revocation.

TLS 1.3 RFC 8446 does not mandate a particular revocation mechanism either,
as revocation is part of PKIX.

Also to be clear you text does not mandate that either servers or clients
support OCSP Stapling.

I think it would be appropriate to modify your text to replace "use" with
support.

"EAP-TLS servers supporting TLS 1.3 that support OCSP to do certificate
revocation checks,  MUST implement Certificate Status Requests using OCSP
stapling as specified in Section 4.4.2.1 of [RFC8446]."





> --
> Michael Richardson <mcr+IETF@sandelman.ca>   . o O ( IPv6 I=C3=B8T consul=
ting )
>            Sandelman Software Works Inc, Ottawa and Worldwide
>
>

--000000000000d12f3105b2e5da86
Content-Type: text/html; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable

<div dir=3D"ltr"><div dir=3D"ltr"><br></div><br><div class=3D"gmail_quote">=
<div dir=3D"ltr" class=3D"gmail_attr">On Fri, Oct 30, 2020 at 4:44 AM Micha=
el Richardson &lt;<a href=3D"mailto:mcr%2Bietf@sandelman.ca">mcr+ietf@sande=
lman.ca</a>&gt; wrote:<br></div><blockquote class=3D"gmail_quote" style=3D"=
margin:0px 0px 0px 0.8ex;border-left:1px solid rgb(204,204,204);padding-lef=
t:1ex"><br>
Joseph Salowey &lt;<a href=3D"mailto:joe@salowey.net" target=3D"_blank">joe=
@salowey.net</a>&gt; wrote:<br>
=C2=A0 =C2=A0 &gt;&gt; I suggest:<br>
=C2=A0 =C2=A0 &gt;&gt;<br>
=C2=A0 =C2=A0 &gt;&gt; =E2=80=9CEAP-TLS servers supporting TLS 1.3 that use=
 OCSP to do certificate<br>
=C2=A0 =C2=A0 &gt;&gt; recovation checks,=C2=A0 MUST implement Certificate =
Status Requests using OCSP<br>
=C2=A0 =C2=A0 &gt;&gt; stapling as specified in Section 4.4.2.1 of [RFC8446=
].<br>
<br>
=C2=A0 =C2=A0 &gt; [Joe] Thanks Michael,=C2=A0 I think your suggestion is a=
 better way to phrase it<br>
<br>
Just so that we are clear:=C2=A0 this mandates OCSP+stapling for systems th=
at do<br>
revocation checks.<br>
<br>
Systems that don&#39;t do revocation checks (current mbedtls), therefore do=
n&#39;t<br>
need to do OCSP or stapling.<br></blockquote><div><br></div><div>[Joe] That=
&#39;s not how I read your text.=C2=A0 I think your text mandates OCSP+stap=
ling for systems that use OCSP for revocation.=C2=A0=C2=A0</div><div><br></=
div><div>TLS 1.3 RFC 8446 does not mandate a particular revocation mechanis=
m either, as revocation is part of PKIX.=C2=A0=C2=A0</div><div><br></div><d=
iv>Also to be clear you text does not mandate that either servers or client=
s support OCSP Stapling.=C2=A0=C2=A0</div><div><br></div><div>I think it wo=
uld be appropriate to modify your text to replace &quot;use&quot; with supp=
ort.=C2=A0=C2=A0</div><div><br></div><div>&quot;EAP-TLS servers supporting =
TLS 1.3 that support OCSP to do certificate<br>revocation checks,=C2=A0 MUS=
T implement Certificate Status Requests using OCSP<br>stapling as specified=
 in Section 4.4.2.1 of [RFC8446].&quot;<br></div><div><br></div><div><br></=
div><div><br></div><div><br></div><blockquote class=3D"gmail_quote" style=
=3D"margin:0px 0px 0px 0.8ex;border-left:1px solid rgb(204,204,204);padding=
-left:1ex">
<br>
--<br>
Michael Richardson &lt;<a href=3D"mailto:mcr%2BIETF@sandelman.ca" target=3D=
"_blank">mcr+IETF@sandelman.ca</a>&gt;=C2=A0 =C2=A0. o O ( IPv6 I=C3=B8T co=
nsulting )<br>
=C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0Sandelman Software Works Inc, Otta=
wa and Worldwide<br>
<br>
</blockquote></div></div>

--000000000000d12f3105b2e5da86--


From nobody Fri Oct 30 10:21:31 2020
Return-Path: <mcr+ietf@sandelman.ca>
X-Original-To: emu@ietfa.amsl.com
Delivered-To: emu@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id C5ECC3A1050 for <emu@ietfa.amsl.com>; Fri, 30 Oct 2020 10:21:29 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.899
X-Spam-Level: 
X-Spam-Status: No, score=-1.899 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, SPF_HELO_NONE=0.001, SPF_PASS=-0.001, URIBL_BLOCKED=0.001] autolearn=ham autolearn_force=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 Zr4u1PiCjIuH for <emu@ietfa.amsl.com>; Fri, 30 Oct 2020 10:21:27 -0700 (PDT)
Received: from tuna.sandelman.ca (tuna.sandelman.ca [IPv6:2607:f0b0:f:3:216:3eff:fe7c:d1f3]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 8FF983A104D for <emu@ietf.org>; Fri, 30 Oct 2020 10:21:27 -0700 (PDT)
Received: from localhost (localhost [127.0.0.1]) by tuna.sandelman.ca (Postfix) with ESMTP id E524F389BB; Fri, 30 Oct 2020 13:28:16 -0400 (EDT)
Received: from tuna.sandelman.ca ([127.0.0.1]) by localhost (localhost [127.0.0.1]) (amavisd-new, port 10024) with LMTP id jSpi8jtFcPmh; Fri, 30 Oct 2020 13:28:16 -0400 (EDT)
Received: from sandelman.ca (obiwan.sandelman.ca [209.87.249.21]) by tuna.sandelman.ca (Postfix) with ESMTP id 6EF17389BA; Fri, 30 Oct 2020 13:28:16 -0400 (EDT)
Received: from localhost (localhost [IPv6:::1]) by sandelman.ca (Postfix) with ESMTP id 392E9362; Fri, 30 Oct 2020 13:21:26 -0400 (EDT)
From: Michael Richardson <mcr+ietf@sandelman.ca>
To: Joseph Salowey <joe@salowey.net>, EMU WG <emu@ietf.org>
In-Reply-To: <CAOgPGoBpUkQuTRVB1GKYtgtFLsckbPfQkkvRVD+xERpgNDYyYg@mail.gmail.com>
References: <CAOgPGoDbsunLOxrnFxa8uMxG6JYObX_r5VLOvVib5QmFHGOrwA@mail.gmail.com> <4858.1604009572@localhost> <CAOgPGoDC8gyBLD4a7Ms-h823sZ5q6USpbE=6HXdVWo3TEVfoYA@mail.gmail.com> <4217.1604058293@localhost> <CAOgPGoBpUkQuTRVB1GKYtgtFLsckbPfQkkvRVD+xERpgNDYyYg@mail.gmail.com>
X-Mailer: MH-E 8.6+git; nmh 1.7+dev; GNU Emacs 26.1
X-Face: $\n1pF)h^`}$H>Hk{L"x@)JS7<%Az}5RyS@k9X%29-lHB$Ti.V>2bi.~ehC0; <'$9xN5Ub# z!G,p`nR&p7Fz@^UXIn156S8.~^@MJ*mMsD7=QFeq%AL4m<nPbLgmtKK-5dC@#:k
MIME-Version: 1.0
Content-Type: multipart/signed; boundary="=-=-="; micalg=pgp-sha512; protocol="application/pgp-signature"
Date: Fri, 30 Oct 2020 13:21:26 -0400
Message-ID: <27420.1604078486@localhost>
Archived-At: <https://mailarchive.ietf.org/arch/msg/emu/350nqSEjp-k6UWStfppVTxXj-_w>
Subject: Re: [Emu] Consensus Call on OCSP usage in draft-ietf-emu-eap-tls13-11
X-BeenThere: emu@ietf.org
X-Mailman-Version: 2.1.29
Precedence: list
List-Id: "EAP Methods Update \(EMU\)" <emu.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/emu>, <mailto:emu-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/emu/>
List-Post: <mailto:emu@ietf.org>
List-Help: <mailto:emu-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/emu>, <mailto:emu-request@ietf.org?subject=subscribe>
X-List-Received-Date: Fri, 30 Oct 2020 17:21:30 -0000

--=-=-=
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: quoted-printable


Joseph Salowey <joe@salowey.net> wrote:
    > On Fri, Oct 30, 2020 at 4:44 AM Michael Richardson <mcr+ietf@sandelma=
n.ca>
    > wrote:

    >>
    >> Joseph Salowey <joe@salowey.net> wrote:
    >> >> I suggest:
    >> >>
    >> >> =E2=80=9CEAP-TLS servers supporting TLS 1.3 that use OCSP to do c=
ertificate
    >> >> recovation checks,  MUST implement Certificate Status Requests
    >> using OCSP
    >> >> stapling as specified in Section 4.4.2.1 of [RFC8446].
    >>
    >> > [Joe] Thanks Michael,  I think your suggestion is a better way to
    >> phrase it
    >>
    >> Just so that we are clear:  this mandates OCSP+stapling for systems =
that do
    >> revocation checks.
    >>
    >> Systems that don't do revocation checks (current mbedtls), therefore=
 don't
    >> need to do OCSP or stapling.
    >>

    > [Joe] That's not how I read your text.  I think your text mandates
    > OCSP+stapling for systems that use OCSP for revocation.

    > TLS 1.3 RFC 8446 does not mandate a particular revocation mechanism e=
ither,
    > as revocation is part of PKIX.

I thought that someone said that it did.
In which case, we are under no additional compulsion to support revocation
than we were before.

Hannes and Eliot have brought up significant operational challenges in
supporting OCSP in some environments.  I think that it should be a local de=
cision.

    > Also to be clear you text does not mandate that either servers or cli=
ents
    > support OCSP Stapling.

    > I think it would be appropriate to modify your text to replace "use" =
with
    > support.

    > "EAP-TLS servers supporting TLS 1.3 that support OCSP to do certifica=
te
    > revocation checks,  MUST implement Certificate Status Requests using =
OCSP
    > stapling as specified in Section 4.4.2.1 of [RFC8446]."

okay.

=2D-
]               Never tell me the odds!                 | ipv6 mesh network=
s [
]   Michael Richardson, Sandelman Software Works        |    IoT architect =
  [
]     mcr@sandelman.ca  http://www.sandelman.ca/        |   ruby on rails  =
  [






    >> --
    >> Michael Richardson <mcr+IETF@sandelman.ca>   . o O ( IPv6 I=C3=B8T c=
onsulting )
    >> Sandelman Software Works Inc, Ottawa and Worldwide
    >>
    >>

    > ----------------------------------------------------
    > Alternatives:

    > ----------------------------------------------------

=2D-
Michael Richardson <mcr+IETF@sandelman.ca>   . o O ( IPv6 I=C3=B8T consulti=
ng )
           Sandelman Software Works Inc, Ottawa and Worldwide





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

-----BEGIN PGP SIGNATURE-----

iQEzBAEBCgAdFiEEbsyLEzg/qUTA43uogItw+93Q3WUFAl+cS5UACgkQgItw+93Q
3WW7ngf+K56MQTN/GmpzrZdNXzdcSrqbqFPQ1g0uRYT9X7PaC0DtdZWGOpjUq18r
55Sd5zzIOfAKqvpS4n8tUfRTzye94NITr0WKZII90Ov03u1aM0PJwD9BSNh9z7G1
WK5Go0qBMHwNkQXNdfiAkcBsRm3azPHFhDZCMcHEwiwtI2MgigycQxaDuUKwrKmZ
rE+CZo4z2TjsqOhJ1T+ZJ7/zKNtpj8HyYOLwIzoWS/l/DTru2ugy2PKtjMLcDWAV
c7vrNU+lW3Wa08eOOwDAtFrLwVoTIZ3T8naJY/GgNQ5QHlFDVJDY1+93ACDcr1DQ
vRtsOwSBhVbtn3IiLq2PvXU+3DB38A==
=ksKp
-----END PGP SIGNATURE-----
--=-=-=--


From nobody Sat Oct 31 06:14:52 2020
Return-Path: <mohit.m.sethi@ericsson.com>
X-Original-To: emu@ietfa.amsl.com
Delivered-To: emu@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 691923A0AAD for <emu@ietfa.amsl.com>; Sat, 31 Oct 2020 06:14:51 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.101
X-Spam-Level: 
X-Spam-Status: No, score=-2.101 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIMWL_WL_HIGH=-0.001, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, DKIM_VALID_EF=-0.1, HTML_MESSAGE=0.001, RCVD_IN_MSPIKE_H2=-0.001, SPF_PASS=-0.001, URIBL_BLOCKED=0.001] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (1024-bit key) header.d=ericsson.com
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 lXe0vzmY_Myr for <emu@ietfa.amsl.com>; Sat, 31 Oct 2020 06:14:49 -0700 (PDT)
Received: from EUR05-DB8-obe.outbound.protection.outlook.com (mail-db8eur05on2087.outbound.protection.outlook.com [40.107.20.87]) (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 83D673A0AA3 for <emu@ietf.org>; Sat, 31 Oct 2020 06:14:42 -0700 (PDT)
ARC-Seal: i=1; a=rsa-sha256; s=arcselector9901; d=microsoft.com; cv=none; b=S5rd4rsFPPmTDBAt5hccer34r7rlEMe4dwJVrLpUn4iUBvEe8nZyDlCQNglknetXDmcBmUgHn+BvLXIoroKHCCNxzwedV4eDu5AYuyGWfGm74q2IwylTEGbQ9ZWIXjywd+StVShnYsyXFpOl1E4yhWwmEXbqzG/nL67PN/S0wDA3mpYEEtFmAKLAYuIn6bVTQ41Q6yKd9KnJEjWGr3WFNp8WxmNpiEWuoZxBujU1eGuH1HGHvpoCZsbRq0FQdWZ41N94JrNgAqbfKxSCONaVdXilKQ2VTw9nlnsDnmET/E18JlWC35HAlEg4MjwnzWhkzBXW6/FKFRYlCcmsv9j46g==
ARC-Message-Signature: i=1; a=rsa-sha256; c=relaxed/relaxed; d=microsoft.com;  s=arcselector9901; h=From:Date:Subject:Message-ID:Content-Type:MIME-Version:X-MS-Exchange-SenderADCheck; bh=uhSP/d+Z/8YlQSIgIaUT4+XhfMr1tqCiW/cZ/LRw2Es=; b=MuavWYVZIxdqUgHYa7oah8EHSr6jCD62c3VaZEo6gV5ZAwLVcnLJhyktKyinKDdKqCTwoClK7Vl5VDhQC6Z0FCm6UYHks3wgDADSYuxQLu3HylixBJox/y5W6/nz1/bYrl00A05B96kx+vYHLGEQEdbRNGo5IVzEBTsEkZIKlTYI4MP9MaXdW+vHp3XoEw7DRkAFvak64kZAsUBFj6309C23pNaxl91f2fC38yssnb2rCkNqfV29AiVAePWCg4WRFVngznYS/iHnK78zN7yv5fGoOCYVGgMLqvc5SezZB8FyxhfmhKT2XnFgTbisTw8VlSv9FI3LqOPrqQWCG5QhPg==
ARC-Authentication-Results: i=1; mx.microsoft.com 1; spf=pass smtp.mailfrom=ericsson.com; dmarc=pass action=none header.from=ericsson.com; dkim=pass header.d=ericsson.com; arc=none
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=ericsson.com; s=selector1; h=From:Date:Subject:Message-ID:Content-Type:MIME-Version:X-MS-Exchange-SenderADCheck; bh=uhSP/d+Z/8YlQSIgIaUT4+XhfMr1tqCiW/cZ/LRw2Es=; b=sRzbXjNBXqfB0DCg6YTLr4owWQF0TL2n5N4HatXtoawNzTWEHapOTq14tynLRaSjD0uzIqQGddk3wBvJOCGZ/Sc2JmatZJPItQeWabX8zZFjjy8EI9SS0JBgcQuxJsiMNq7dExfXLJu6R9xBfR5hyqVUpR0z3TDJogr/uYWspmA=
Received: from HE1PR07MB3209.eurprd07.prod.outlook.com (2603:10a6:7:32::14) by HE1PR0702MB3564.eurprd07.prod.outlook.com (2603:10a6:7:8c::11) with Microsoft SMTP Server (version=TLS1_2, cipher=TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384) id 15.20.3541.10; Sat, 31 Oct 2020 13:14:38 +0000
Received: from HE1PR07MB3209.eurprd07.prod.outlook.com ([fe80::1550:2d88:a5be:95ca]) by HE1PR07MB3209.eurprd07.prod.outlook.com ([fe80::1550:2d88:a5be:95ca%6]) with mapi id 15.20.3499.028; Sat, 31 Oct 2020 13:14:38 +0000
From: Mohit Sethi M <mohit.m.sethi@ericsson.com>
To: "emu@ietf.org" <emu@ietf.org>
Thread-Topic: Moving towards less security in 2020 - OCSP
Thread-Index: AQHWr4fIgE+zwSuaOUaU3dGJhOUmzA==
Date: Sat, 31 Oct 2020 13:14:38 +0000
Message-ID: <d339e0e2-7e3b-aeb5-4741-a75adba324ec@ericsson.com>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
user-agent: Mozilla/5.0 (X11; Linux x86_64; rv:68.0) Gecko/20100101 Thunderbird/68.10.0
authentication-results: ietf.org; dkim=none (message not signed) header.d=none;ietf.org; dmarc=none action=none header.from=ericsson.com;
x-originating-ip: [37.136.189.206]
x-ms-publictraffictype: Email
x-ms-office365-filtering-correlation-id: 0b7f3b85-2c51-47f3-a491-08d87d9eebc7
x-ms-traffictypediagnostic: HE1PR0702MB3564:
x-microsoft-antispam-prvs: <HE1PR0702MB356453756F3561DC44169914D0120@HE1PR0702MB3564.eurprd07.prod.outlook.com>
x-ms-oob-tlc-oobclassifiers: OLM:10000;
x-ms-exchange-senderadcheck: 1
x-microsoft-antispam: BCL:0;
x-microsoft-antispam-message-info: TEls2V/HsroivX3XD2wvI3u0Cao28rU2RKYzjnHfsA4tPpn7BDdv6ajQWTSEmQhEKCzCdehI0IcxX+oCSN/zFuzpCpU2UeWEHg0QkUtorRkfHvhfS6A2qRzhTYJdzePi0AgEh6SGJu/HoTgJlbXoUp+8vCrlS4CEtbcVNz9oJD6eO10jT55kKYZzUdXwE29TP/B4IM4BP+s39SDbhY1Y0o6QgNUm7Ho2MFQBIBp0seT2BsxzHNOSaakgNBMt+z8lw+qE7/FKr9xp3fL6J28W5GvL8zBTXnk0ZvFjRGJiAqaa/DJ2LUadYtYguWJn2yjNadEyVoesvGD36ivySWQzyxNIx1cVwqoNq6MQepkASHSbfZlNU7oSZotemvSIKiU5W0OvYDIgSRDPPTEX02DA4gG9awHL1yx9FTWZYMBJmAPIjjgIHUfyYLG67zXrzh0oJxkFUSmzg5w94sp+aYC7CA==
x-forefront-antispam-report: CIP:255.255.255.255; CTRY:; LANG:en; SCL:1; SRV:;  IPV:NLI; SFV:NSPM; H:HE1PR07MB3209.eurprd07.prod.outlook.com; PTR:; CAT:NONE;  SFS:(4636009)(376002)(346002)(366004)(136003)(396003)(39860400002)(71200400001)(66476007)(5660300002)(31696002)(66946007)(66446008)(76116006)(66556008)(64756008)(316002)(15650500001)(6512007)(31686004)(36756003)(66574015)(86362001)(8676002)(8936002)(26005)(966005)(6916009)(166002)(2616005)(186003)(6506007)(2906002)(83380400001)(478600001)(6486002)(43740500002); DIR:OUT; SFP:1101; 
x-ms-exchange-antispam-messagedata: x9Pj5lNCsWuGxN/7/BT1m4MfX55gK+M8V1A8/WlMsuSgBo7lVJDTrzcWiEPy7p4x46yITkw9NXkJ69kOoNei5HOUK1V0gRyUbXMJ8K7T96MA9oOuSl9kmucIWZL2uAFMxzZrBcgk7NmanQPOhcyLiDy/jxXDzJfDcBu/9BMCBlj9W+WJx/0swFuXefVpl+t8EV2Vemncc5Cx0AN3OyFq3CNtE7fmjv2F9Uq81ktq/Tj6Icb/9wZUy9XMYNbGpblGf9iWvwSd/irZf3D9RJXI5b1FbdqCOcj36hrdffMKzuHZRHenTsJwWu2Bm5lusBkSv9aOG+BcFB88qJwC8hx+3P25Q+dJpBF3TXWstzJwfEHAViDtNdVFIkkI1RZLrx8q8yszt1tlYpa0XocL+TjiMV6NP6uJYAklVjo/JV4J+GhJk5KOCOHJkqlJ+bVw64PAgLJJZqMCJr56efUFZYACJdIP6a2jTCd1hqiLTIs2eZT+LQT0TSa5UkOFCPVbT7CM67CRkLAEF9TOvu1VShcav8jULdwAWVWJSkvhOe2R3xepqM5eAuNwI0AXCB8YM/H0A/ADQxLtwY4vZr4BQOlNE+Y610ArB4knmeBo5GrUgPdCyvfYKQU0xcSyliy+EPUJjzlDBqcbCJa9caSeW6jwbw==
x-ms-exchange-transport-forked: True
Content-Type: multipart/alternative; boundary="_000_d339e0e27e3baeb54741a75adba324ecericssoncom_"
MIME-Version: 1.0
X-OriginatorOrg: ericsson.com
X-MS-Exchange-CrossTenant-AuthAs: Internal
X-MS-Exchange-CrossTenant-AuthSource: HE1PR07MB3209.eurprd07.prod.outlook.com
X-MS-Exchange-CrossTenant-Network-Message-Id: 0b7f3b85-2c51-47f3-a491-08d87d9eebc7
X-MS-Exchange-CrossTenant-originalarrivaltime: 31 Oct 2020 13:14:38.5530 (UTC)
X-MS-Exchange-CrossTenant-fromentityheader: Hosted
X-MS-Exchange-CrossTenant-id: 92e84ceb-fbfd-47ab-be52-080c6b87953f
X-MS-Exchange-CrossTenant-mailboxtype: HOSTED
X-MS-Exchange-CrossTenant-userprincipalname: 2Zf9ep3Q88lBIfwUOMsQrGrZXCjmpUOfL12sh/iQGpQUjJQCTM5N9SW1zlZ5zrsUwoY1+LEmasmkrujWIEeAhM4MPnjB7jtZBCRkmoNzKPM=
X-MS-Exchange-Transport-CrossTenantHeadersStamped: HE1PR0702MB3564
Archived-At: <https://mailarchive.ietf.org/arch/msg/emu/G7fMFLeEbGCzbQEyCVaiuyG_l_8>
Subject: [Emu] Moving towards less security in 2020 - OCSP
X-BeenThere: emu@ietf.org
X-Mailman-Version: 2.1.29
Precedence: list
List-Id: "EAP Methods Update \(EMU\)" <emu.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/emu>, <mailto:emu-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/emu/>
List-Post: <mailto:emu@ietf.org>
List-Help: <mailto:emu-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/emu>, <mailto:emu-request@ietf.org?subject=subscribe>
X-List-Received-Date: Sat, 31 Oct 2020 13:14:51 -0000

--_000_d339e0e27e3baeb54741a75adba324ecericssoncom_
Content-Type: text/plain; charset="utf-8"
Content-Transfer-Encoding: base64

RGVhciBhbGwsDQoNClNvcnJ5IGZvciB0aGUgcmFkaW8gc2lsZW5jZS4gSSBoYXZlIG92ZXItY29t
bWl0dGVkIG15c2VsZiB0byB0b28gbWFueSB0aGluZ3MuIEkgdGhpbmsgSSBoYXZlIG5vdyByZWFk
IHRoZSBlbnRpcmUgZGlzY3Vzc2lvbiBvbiBPQ1NQLg0KDQpFQVAtVExTIHdpdGggVExTIDEuMyBp
cyBhIHdvcmtpbmcgZ3JvdXAgZG9jdW1lbnQgc28gdGhlIHRleHQgd2lsbCByZWZsZWN0IHdoYXRl
dmVyIHRoZSB3b3JraW5nIGdyb3VwIHdhbnRzLiBUaGUgYXV0aG9ycyBhbmQgY29udHJpYnV0b3Jz
IGFyZSBhdCB0aGUgc2VydmljZSBvZiB0aGUgd29ya2luZyBncm91cC4gT2J2aW91c2x5IGl0IGlz
IGVhc3kgZm9yIHVzIHRvIHNpbXBseSBjaGFuZ2UgYWxsIE1VU1RzIHRvIE1BWXMsIG1ha2UgZXZl
cnlvbmUgaGFwcHksIGFuZCBoYW5kIG92ZXIgdGhlIGRvY3VtZW50IHRvIHRoZSBJRVNHLg0KDQpZ
ZXQsIEkgdGhpbmsgYXMgYSBjb25zY2llbnRpb3VzIHNlY3VyaXR5IHBlcnNvbiBhbmQgaW5kaXZp
ZHVhbCBjb250cmlidXRvciwgSSBhbSBzYWRkZW5lZCBieSB0aGUgZGlzY3Vzc2lvbiB0aHVzIGZh
ci4gVG8gYmVnaW4gd2l0aCwgSSBhc3N1bWUgdGhhdCBldmVyeW9uZSBrbm93cyB0aGUgZGlmZmVy
ZW5jZSBiZXR3ZWVuIE9DU1AgYW5kIE9DU1Agc3RhcGxpbmcuIEkgYWxzbyBob3BlIHRoYXQgZXZl
cnlvbmUgaGFzIHJlYWQgUkZDIDUyMTYgKHRoZSBwcmV2aW91cyBFQVAtVExTIHNwZWNpZmljYXRp
b24pLiBJbiBwYXJ0aWN1bGFyIEkgaG9wZSB0aGF0IHRoZSB3b3JraW5nIGdyb3VwIGhhcyBhY3R1
YWxseSByZWFkIHNlY3Rpb24gNS40IG9uICJDZXJ0aWZpY2F0ZSBSZXZvY2F0aW9uIiAoaHR0cHM6
Ly90b29scy5pZXRmLm9yZy9odG1sL3JmYzUyMTYjc2VjdGlvbi01LjQpLiBJIGNvcHkgdGhlIHJl
bGV2YW50IHRleHQgaGVyZSBmb3IgeW91ciBjb252ZW5pZW5jZToNCg0KICAgRUFQLVRMUyBwZWVy
IGFuZCBzZXJ2ZXIgaW1wbGVtZW50YXRpb25zIE1VU1Qgc3VwcG9ydCB0aGUgdXNlIG9mDQogICBD
ZXJ0aWZpY2F0ZSBSZXZvY2F0aW9uIExpc3RzIChDUkxzKTsgZm9yIGRldGFpbHMsIHNlZSBTZWN0
aW9uIDMuMyBvZg0KICAgW1JGQzMyODBdPGh0dHBzOi8vdG9vbHMuaWV0Zi5vcmcvaHRtbC9yZmMz
MjgwI3NlY3Rpb24tMy4zPi4gIEVBUC1UTFMgcGVlciBhbmQgc2VydmVyIGltcGxlbWVudGF0aW9u
cyBTSE9VTEQgYWxzbw0KICAgc3VwcG9ydCB0aGUgT25saW5lIENlcnRpZmljYXRlIFN0YXR1cyBQ
cm90b2NvbCAoT0NTUCksIGRlc2NyaWJlZCBpbg0KICAgIlguNTA5IEludGVybmV0IFB1YmxpYyBL
ZXkgSW5mcmFzdHJ1Y3R1cmUgT25saW5lIENlcnRpZmljYXRlIFN0YXR1cw0KICAgUHJvdG9jb2wg
LSBPQ1NQIiBbUkZDMjU2MDxodHRwczovL3Rvb2xzLmlldGYub3JnL2h0bWwvcmZjMjU2MD5dLiAg
T0NTUCBtZXNzYWdlcyBhcmUgdHlwaWNhbGx5IG11Y2ggc21hbGxlcg0KICAgdGhhbiBDUkxzLCB3
aGljaCBjYW4gc2hvcnRlbiBjb25uZWN0aW9uIHRpbWVzIGVzcGVjaWFsbHkgaW4NCiAgIGJhbmR3
aWR0aC1jb25zdHJhaW5lZCBlbnZpcm9ubWVudHMuDQoNCmFuZA0KDQogICBGb3IgdGhpcyByZWFz
b24sIEVBUC1UTFMgcGVlcnMgYW5kIHNlcnZlcnMgU0hPVUxEIGltcGxlbWVudA0KICAgQ2VydGlm
aWNhdGUgU3RhdHVzIFJlcXVlc3QgbWVzc2FnZXMsIGFzIGRlc2NyaWJlZCBpbiAiVHJhbnNwb3J0
IExheWVyDQogICBTZWN1cml0eSAoVExTKSBFeHRlbnNpb25zIiwgU2VjdGlvbiAzLjYgb2YgW1JG
QzQzNjZdPGh0dHBzOi8vdG9vbHMuaWV0Zi5vcmcvaHRtbC9yZmM0MzY2I3NlY3Rpb24tMy42Pi4g
IFRvIGVuYWJsZQ0KICAgcmV2b2NhdGlvbiBjaGVja2luZyBpbiBzaXR1YXRpb25zIHdoZXJlIHNl
cnZlcnMgZG8gbm90IHN1cHBvcnQNCiAgIENlcnRpZmljYXRlIFN0YXR1cyBSZXF1ZXN0IG1lc3Nh
Z2VzIGFuZCBuZXR3b3JrIGNvbm5lY3Rpdml0eSBpcyBub3QNCiAgIGF2YWlsYWJsZSBwcmlvciB0
byBhdXRoZW50aWNhdGlvbiBjb21wbGV0aW9uLCBwZWVyIGltcGxlbWVudGF0aW9ucw0KICAgTVVT
VCBhbHNvIHN1cHBvcnQgY2hlY2tpbmcgZm9yIGNlcnRpZmljYXRlIHJldm9jYXRpb24gYWZ0ZXIN
CiAgIGF1dGhlbnRpY2F0aW9uIGNvbXBsZXRlcyBhbmQgbmV0d29yayBjb25uZWN0aXZpdHkgaXMg
YXZhaWxhYmxlLCBhbmQNCiAgIHRoZXkgU0hPVUxEIHV0aWxpemUgdGhpcyBjYXBhYmlsaXR5IGJ5
IGRlZmF1bHQuDQoNClNvIHdlIHdlcmUgYWxyZWFkeSBzYXlpbmcgIlNIT1VMRCIgZm9yIE9DU1Ag
aW4gMjAwOCB3aGVuIFJGQyA1MjE2IHdhcyBwdWJsaXNoZWQuIEFuZCBub3cgMTIvMTMgeWVhcnMg
bGF0ZXIsIHNvbWUgcGVvcGxlIGluIHRoZSB3b3JraW5nIGdyb3VwIGFyZSBzdWdnZXN0aW5nIHRv
IG1ha2UgdGhlIHNlY3VyaXR5IHN0YW5jZSB3ZWFrZXIuIEZvciB3aGF0PyBTb21lIHNwZWN1bGF0
aXZlIGluc2VjdXJlIGZ1dHVyZSBkZXBsb3ltZW50cz8gUGxlYXNlIG5vdGUgdGhhdCBFQVAtVExT
IGlzIGN1cnJlbnRseSBpbXBsZW1lbnRlZCBpbiBiaWxsaW9ucyBvZiBkZXZpY2VzIGFuZCB1c2Vk
IGluIG1hbnkgaGlnaCBzZWN1cml0eSBkZXBsb3ltZW50cy4NCg0KSXQgaXMgdmVyeSBzdXJwcmlz
aW5nIHRvIHNlZSBIYW5uZXMgd2FudGluZyB0byB3YXRlciBkb3duIHNlY3VyaXR5IGFuZCBnZXQg
cmlkIG9mIHRoZSB0ZXh0IG9uIE9DU1AuIEhlIHdyb3RlICJJIGRvIG5vdCB1bmRlcnN0YW5kIGNl
cnRpZmljYXRlIHJldm9jYXRpb24gY2hlY2tpbmcgaXMgYSB0b3BpYyBzcGVjaWZpYyB0byB0aGUg
dXNlIG9mIFRMUyAxLjMgaW4gRUFQLVRMUy4iLiBXZWxsLCBhcyB5b3Ugc2VlLCBSRkMgNTIxNiBo
YXMgcXVpdGUgZGV0YWlsZWQgZ3VpZGVsaW5lcyBvbiBjZXJ0aWZpY2F0ZSByZXZvY2F0aW9uIGNo
ZWNraW5nIHdpdGggQ1JMcyBhbmQgT0NTUCBzbyBJIGRvbid0IHNlZSBhbnkgc2Vuc2libGUgcmVh
c29uIG9uIHdoeSBhbiB1cGRhdGUgdG8gaXQgc2hvdWxkIG5vdCBjb250YWluIHJlbGV2YW50IHRl
eHQuIE1pY2hhZWwgd3JvdGUgIiB3ZSBhcmUgdW5kZXIgbm8gYWRkaXRpb25hbCBjb21wdWxzaW9u
IHRvIHN1cHBvcnQgcmV2b2NhdGlvbiB0aGFuIHdlIHdlcmUgYmVmb3JlLiIgRG8geW91IHNlZSB0
aGUgcHJvYmxlbSBoZXJlIGdpdmVuIHRoZSB0ZXh0IGluIFJGQyA1MjE2IHNob3duIGFib3ZlPw0K
DQpXaGlsZSBFbGxpb3QgYW5kIEhhbm5lcyBoYXZlIGJlZW4gdm9jYWwgYWJvdXQgdGhlaXIgdmll
d3MsIHdlIGFsc28gc2F3IGZlZWRiYWNrIGZyb20gSmFuZnJlZCBleHBsYWluaW5nIHRoZSBzaXR1
YXRpb24gd2l0aG91dCBPQ1NQIGluIGEgbGl2ZSBuZXR3b3JrIGxpa2UgZWR1cm9hbTogaHR0cHM6
Ly9tYWlsYXJjaGl2ZS5pZXRmLm9yZy9hcmNoL21zZy9lbXUvWDlNbTI0TFN6YXE2M2JIU3Zta0Ji
aVNzckpjLy4gSGUgZW5kcyBoaXMgZW1haWwgd2l0aA0KDQpBbGwgaW4gYWxsLCBJIGRlZmluaXRl
bHkgdGhpbmsgdGhhdCBtYWtpbmcgT0NTUCBTdGFwbGluZyBvcHRpb25hbCB3aWxsDQpoYXZlIGEg
YmVuZWZpdCBvbiBzbWFsbCBkZXZpY2VzLCBidXQgZXNwZWNpYWxseSBmb3IgdGhlIGRpdmVyc2UN
CmVudmlyb25tZW50IG9mIGVkdXJvYW0sIG1ha2luZyBPQ1NQIFN0YXBsaW5nIG1hbmRhdG9yeSB3
aWxsIGluY3JlYXNlIHRoZQ0Kb3ZlcmFsbCBzZWN1cml0eSBvZiB0aGlzIGZlZGVyYXRpb24uDQpN
YXliZSBpdCBtaWdodCBiZSBhIGdvb2QgaWRlYSB0byBtYWtlIE9DU1AgU3RhcGxpbmcgbWFuZGF0
b3J5IGZvcg0KRUFQLVRMUyBTZXJ2ZXJzPw0KDQpTbyB3aGVyZSB3ZSBhcmUgd2l0aCB0aGUgY3Vy
cmVudCBkcmFmdC4gVGhlIGN1cnJlbnQgZHJhZnQgKGh0dHBzOi8vdG9vbHMuaWV0Zi5vcmcvaHRt
bC9kcmFmdC1pZXRmLWVtdS1lYXAtdGxzMTMtMTEjc2VjdGlvbi01LjQpIHNheXMsICJXaGVuIEVB
UC1UTFMgaXMgdXNlZCB3aXRoIFRMUyAxLjMsIHRoZSBzZXJ2ZXIgTVVTVCBjaGVjayB0aGUgcmV2
b2NhdGlvbiBzdGF0dXMgb2YgdGhlIGNlcnRpZmljYXRlcyBpbiB0aGUgY2xpZW50J3MgY2VydGlm
aWNhdGUgY2hhaW4uIi4gSXQgZG9lc24ndCBtYW5kYXRlIGFueSBzcGVjaWZpYyB0ZWNobmlxdWUu
IFlvdSBhcmUgZnJlZSB0byB1c2Ugd2hhdGV2ZXIgcHJvcHJpZXR5IChwb3RlbnRpYWxseSBpbnNl
Y3VyZSkgbWV0aG9kIHlvdSB3YW50LiBUaGUgcmV2b2NhdGlvbiBjaGVja2luZyBjb3VsZCB1c2Ug
dGhlIGZvbGxvd2luZyBwc2V1ZG9jb2RlIGZvciBjaGVja2luZyB0aGUgcmV2b2NhdGlvbiBzdGF0
dXMgb2YgY2xpZW50IGNlcnRpZmljYXRlczoNCg0KZnVuIGNoZWNrX3Jldm9jYXRpb24gew0KcmV0
dXJuIHN1Y2Nlc3M7DQp9DQoNCmFuZCB5b3Ugd291bGQgY29tcGx5IHdpdGggc3BlY2lmaWNhdGlv
bi4gTmF0dXJhbGx5LCB1c2luZyBDUkxzIG9yIGxvY2FsbHktY29uZmlndXJlZCBPQ1NQIHJlc3Bv
bmRlciBvbiB0aGUgc2VydmVyIChmb3IgcmV2b2NhdGlvbiBjaGVja2luZyBvZiBjbGllbnQgY2Vy
dGlmaWNhdGVzKSB3aWxsIGdldCB5b3UgYmV0dGVyIHNlY3VyaXR5LiBUaGUgY3VycmVudCB0ZXh0
IGluIHRoZSBkcmFmdCBkb2VzIG1hbmRhdGUgT0NTUCBzdGFwbGluZyBmb3IgY2xpZW50cyB0byB2
ZXJpZnkgdGhlIHJldm9jYXRpb24gc3RhdHVzIG9mIHNlcnZlciBjZXJ0aWZpY2F0ZXMuIEdpdmVu
IHRoZSByZXNpc3RhbmNlIGluIHRoZSB3b3JraW5nIGdyb3VwLCBJIHRoaW5rIGl0IGlzIGEgcmVh
c29uYWJsZSBjb21wcm9taXNlIGZvciBzZXJ2ZXJzIHRvIGltcGxlbWVudCBPQ1NQIHN0YXBsaW5n
LiBDbGllbnRzIGNhbiBpbXBsZW1lbnQgYW5kIHVzZSBpdCwgYnV0IHRoZXkgd291bGQgYmUgY29t
cGxpYW50IGV2ZW4gaWYgdGhleSBkb24ndC4gU28gdGhlIHVwZGF0ZWQgdGV4dCB3b3VsZCBiZSAo
YXMgSm9lIHdyb3RlIGluIGhpcyBlbWFpbCk6DQoNCkVBUC1UTFMgc2VydmVycyBzdXBwb3J0aW5n
IFRMUyAxLjMgTVVTVCBpbXBsZW1lbnQgQ2VydGlmaWNhdGUgU3RhdHVzIFJlcXVlc3RzIChPQ1NQ
IHN0YXBsaW5nKSBhcyBzcGVjaWZpZWQgaW4gU2VjdGlvbiA0LjQuMi4xIG9mIFtSRkM4NDQ2XS4g
SXQgaXMgUkVDT01NRU5ERUQgdGhhdCBFQVAtVExTIHBlZXJzIGFuZCBzZXJ2ZXJzIHVzZSBPQ1NQ
IHN0YXBsaW5nIGZvciB2ZXJpZnlpbmcgdGhlIHN0YXR1cyBvZiBzZXJ2ZXIgY2VydGlmaWNhdGVz
IGFzIHNwZWNpZmllZCBpbiBTZWN0aW9uIDQuNC4yLjEgb2YgW1JGQzg0NDZdLiBXaGVuIGFuIEVB
UC1UTFMgcGVlciB1c2VzIE9DU1AgdG8gdmVyaWZ5IHRoZSBjZXJ0aWZpY2F0ZSBzdGF0dXMgb2Yg
dGhlIEVBUC1UTFMgc2VydmVyLCBpdCBNVVNUIHVzZSBDZXJ0aWZpY2F0ZSBTdGF0dXMgUmVxdWVz
dHMgZm9yIHRoZSBzZXJ2ZXIncyBjZXJ0aWZpY2F0ZSBjaGFpbiBhbmQgaXQgTVVTVCB0cmVhdCBh
IENlcnRpZmljYXRlRW50cnkgKGV4Y2VwdCB0aGUgdHJ1c3QgYW5jaG9yKSB3aXRob3V0IGEgdmFs
aWQgQ2VydGlmaWNhdGVTdGF0dXMgZXh0ZW5zaW9uIGFzIGludmFsaWQgYW5kIGFib3J0IHRoZSBo
YW5kc2hha2Ugd2l0aCBhbiBhcHByb3ByaWF0ZSBhbGVydC4NCg0KTm90ZSB0aGF0IHRoaXMgaXMg
YWxzbyBjb21wbGlhbnQgd2l0aCB0aGUgTklTVCBTUCA4MDAtNTIgUmV2LiAyLg0KDQotLU1vaGl0
DQo=

--_000_d339e0e27e3baeb54741a75adba324ecericssoncom_
Content-Type: text/html; charset="utf-8"
Content-ID: <E647538EEDCBEC48B1DA95ED60ADB2CE@eurprd07.prod.outlook.com>
Content-Transfer-Encoding: base64

PGh0bWw+DQo8aGVhZD4NCjxtZXRhIGh0dHAtZXF1aXY9IkNvbnRlbnQtVHlwZSIgY29udGVudD0i
dGV4dC9odG1sOyBjaGFyc2V0PXV0Zi04Ij4NCjwvaGVhZD4NCjxib2R5Pg0KPHA+RGVhciBhbGws
PC9wPg0KPHA+U29ycnkgZm9yIHRoZSByYWRpbyBzaWxlbmNlLiBJIGhhdmUgb3Zlci1jb21taXR0
ZWQgbXlzZWxmIHRvIHRvbyBtYW55IHRoaW5ncy4gSSB0aGluayBJIGhhdmUgbm93IHJlYWQgdGhl
IGVudGlyZSBkaXNjdXNzaW9uIG9uIE9DU1AuDQo8YnI+DQo8L3A+DQo8cD5FQVAtVExTIHdpdGgg
VExTIDEuMyBpcyBhIHdvcmtpbmcgZ3JvdXAgZG9jdW1lbnQgc28gdGhlIHRleHQgd2lsbCByZWZs
ZWN0IHdoYXRldmVyIHRoZSB3b3JraW5nIGdyb3VwIHdhbnRzLiBUaGUgYXV0aG9ycyBhbmQgY29u
dHJpYnV0b3JzIGFyZSBhdCB0aGUgc2VydmljZSBvZiB0aGUgd29ya2luZyBncm91cC4gT2J2aW91
c2x5IGl0IGlzIGVhc3kgZm9yIHVzIHRvIHNpbXBseSBjaGFuZ2UgYWxsIE1VU1RzIHRvIE1BWXMs
IG1ha2UgZXZlcnlvbmUNCiBoYXBweSwgYW5kIGhhbmQgb3ZlciB0aGUgZG9jdW1lbnQgdG8gdGhl
IElFU0cuIDxicj4NCjwvcD4NCjxwPllldCwgSSB0aGluayBhcyBhIGNvbnNjaWVudGlvdXMgc2Vj
dXJpdHkgcGVyc29uIGFuZCBpbmRpdmlkdWFsIGNvbnRyaWJ1dG9yLCBJIGFtIHNhZGRlbmVkIGJ5
IHRoZSBkaXNjdXNzaW9uIHRodXMgZmFyLiBUbyBiZWdpbiB3aXRoLCBJIGFzc3VtZSB0aGF0IGV2
ZXJ5b25lIGtub3dzIHRoZSBkaWZmZXJlbmNlIGJldHdlZW4gT0NTUCBhbmQgT0NTUCBzdGFwbGlu
Zy4gSSBhbHNvIGhvcGUgdGhhdCBldmVyeW9uZSBoYXMgcmVhZCBSRkMgNTIxNiAodGhlDQogcHJl
dmlvdXMgRUFQLVRMUyBzcGVjaWZpY2F0aW9uKS4gSW4gcGFydGljdWxhciBJIGhvcGUgdGhhdCB0
aGUgd29ya2luZyBncm91cCBoYXMgYWN0dWFsbHkgcmVhZCBzZWN0aW9uIDUuNCBvbiAmcXVvdDtD
ZXJ0aWZpY2F0ZSBSZXZvY2F0aW9uJnF1b3Q7ICg8YSBjbGFzcz0ibW96LXR4dC1saW5rLWZyZWV0
ZXh0IiBocmVmPSJodHRwczovL3Rvb2xzLmlldGYub3JnL2h0bWwvcmZjNTIxNiNzZWN0aW9uLTUu
NCI+aHR0cHM6Ly90b29scy5pZXRmLm9yZy9odG1sL3JmYzUyMTYjc2VjdGlvbi01LjQ8L2E+KS4N
CiBJIGNvcHkgdGhlIHJlbGV2YW50IHRleHQgaGVyZSBmb3IgeW91ciBjb252ZW5pZW5jZTo8L3A+
DQo8cD48L3A+DQo8YmxvY2txdW90ZSB0eXBlPSJjaXRlIj4NCjxwcmUgY2xhc3M9Im5ld3BhZ2Ui
PiAgIEVBUC1UTFMgcGVlciBhbmQgc2VydmVyIGltcGxlbWVudGF0aW9ucyBNVVNUIHN1cHBvcnQg
dGhlIHVzZSBvZg0KICAgQ2VydGlmaWNhdGUgUmV2b2NhdGlvbiBMaXN0cyAoQ1JMcyk7IGZvciBk
ZXRhaWxzLCBzZWUgPGEgaHJlZj0iaHR0cHM6Ly90b29scy5pZXRmLm9yZy9odG1sL3JmYzMyODAj
c2VjdGlvbi0zLjMiPlNlY3Rpb24mbmJzcDszLjMgb2YNCiAgIFtSRkMzMjgwXTwvYT4uICBFQVAt
VExTIHBlZXIgYW5kIHNlcnZlciBpbXBsZW1lbnRhdGlvbnMgU0hPVUxEIGFsc28NCiAgIHN1cHBv
cnQgdGhlIE9ubGluZSBDZXJ0aWZpY2F0ZSBTdGF0dXMgUHJvdG9jb2wgKE9DU1ApLCBkZXNjcmli
ZWQgaW4NCiAgICZxdW90O1guNTA5IEludGVybmV0IFB1YmxpYyBLZXkgSW5mcmFzdHJ1Y3R1cmUg
T25saW5lIENlcnRpZmljYXRlIFN0YXR1cw0KICAgUHJvdG9jb2wgLSBPQ1NQJnF1b3Q7IFs8YSBo
cmVmPSJodHRwczovL3Rvb2xzLmlldGYub3JnL2h0bWwvcmZjMjU2MCIgdGl0bGU9IiZxdW90O1gu
NTA5IEludGVybmV0IFB1YmxpYyBLZXkgSW5mcmFzdHJ1Y3R1cmUgT25saW5lIENlcnRpZmljYXRl
IFN0YXR1cyBQcm90b2NvbCAtIE9DU1AmcXVvdDsiPlJGQzI1NjA8L2E+XS4gIE9DU1AgbWVzc2Fn
ZXMgYXJlIHR5cGljYWxseSBtdWNoIHNtYWxsZXINCiAgIHRoYW4gQ1JMcywgd2hpY2ggY2FuIHNo
b3J0ZW4gY29ubmVjdGlvbiB0aW1lcyBlc3BlY2lhbGx5IGluDQogICBiYW5kd2lkdGgtY29uc3Ry
YWluZWQgZW52aXJvbm1lbnRzLiA8L3ByZT4NCjwvYmxvY2txdW90ZT4NCmFuZA0KPHA+PC9wPg0K
PHA+PC9wPg0KPGJsb2NrcXVvdGUgdHlwZT0iY2l0ZSI+DQo8cHJlIGNsYXNzPSJuZXdwYWdlIj4g
ICBGb3IgdGhpcyByZWFzb24sIEVBUC1UTFMgcGVlcnMgYW5kIHNlcnZlcnMgU0hPVUxEIGltcGxl
bWVudA0KICAgQ2VydGlmaWNhdGUgU3RhdHVzIFJlcXVlc3QgbWVzc2FnZXMsIGFzIGRlc2NyaWJl
ZCBpbiAmcXVvdDtUcmFuc3BvcnQgTGF5ZXINCiAgIFNlY3VyaXR5IChUTFMpIEV4dGVuc2lvbnMm
cXVvdDssIDxhIGhyZWY9Imh0dHBzOi8vdG9vbHMuaWV0Zi5vcmcvaHRtbC9yZmM0MzY2I3NlY3Rp
b24tMy42Ij5TZWN0aW9uJm5ic3A7My42IG9mIFtSRkM0MzY2XTwvYT4uICBUbyBlbmFibGUNCiAg
IHJldm9jYXRpb24gY2hlY2tpbmcgaW4gc2l0dWF0aW9ucyB3aGVyZSBzZXJ2ZXJzIGRvIG5vdCBz
dXBwb3J0DQogICBDZXJ0aWZpY2F0ZSBTdGF0dXMgUmVxdWVzdCBtZXNzYWdlcyBhbmQgbmV0d29y
ayBjb25uZWN0aXZpdHkgaXMgbm90DQogICBhdmFpbGFibGUgcHJpb3IgdG8gYXV0aGVudGljYXRp
b24gY29tcGxldGlvbiwgcGVlciBpbXBsZW1lbnRhdGlvbnMNCiAgIE1VU1QgYWxzbyBzdXBwb3J0
IGNoZWNraW5nIGZvciBjZXJ0aWZpY2F0ZSByZXZvY2F0aW9uIGFmdGVyDQogICBhdXRoZW50aWNh
dGlvbiBjb21wbGV0ZXMgYW5kIG5ldHdvcmsgY29ubmVjdGl2aXR5IGlzIGF2YWlsYWJsZSwgYW5k
DQogICB0aGV5IFNIT1VMRCB1dGlsaXplIHRoaXMgY2FwYWJpbGl0eSBieSBkZWZhdWx0LjwvcHJl
Pg0KPC9ibG9ja3F1b3RlPg0KPGJyPg0KU28gd2Ugd2VyZSBhbHJlYWR5IHNheWluZyAmcXVvdDtT
SE9VTEQmcXVvdDsgZm9yIE9DU1AgaW4gMjAwOCB3aGVuIFJGQyA1MjE2IHdhcyBwdWJsaXNoZWQu
IEFuZCBub3cgMTIvMTMgeWVhcnMgbGF0ZXIsIHNvbWUgcGVvcGxlIGluIHRoZSB3b3JraW5nIGdy
b3VwIGFyZSBzdWdnZXN0aW5nIHRvIG1ha2UgdGhlIHNlY3VyaXR5IHN0YW5jZSB3ZWFrZXIuIEZv
ciB3aGF0PyBTb21lIHNwZWN1bGF0aXZlIGluc2VjdXJlIGZ1dHVyZSBkZXBsb3ltZW50cz8gUGxl
YXNlIG5vdGUNCiB0aGF0IEVBUC1UTFMgaXMgY3VycmVudGx5IGltcGxlbWVudGVkIGluIGJpbGxp
b25zIG9mIGRldmljZXMgYW5kIHVzZWQgaW4gbWFueSBoaWdoIHNlY3VyaXR5IGRlcGxveW1lbnRz
Ljxicj4NCjxwPjwvcD4NCjxwPkl0IGlzIHZlcnkgc3VycHJpc2luZyB0byBzZWUgSGFubmVzIHdh
bnRpbmcgdG8gd2F0ZXIgZG93biBzZWN1cml0eSBhbmQgZ2V0IHJpZCBvZiB0aGUgdGV4dCBvbiBP
Q1NQLiBIZSB3cm90ZSAmcXVvdDtJIGRvIG5vdCB1bmRlcnN0YW5kIGNlcnRpZmljYXRlIHJldm9j
YXRpb24gY2hlY2tpbmcgaXMgYSB0b3BpYyBzcGVjaWZpYyB0byB0aGUgdXNlIG9mIFRMUyAxLjMg
aW4gRUFQLVRMUy4mcXVvdDsuIFdlbGwsIGFzIHlvdSBzZWUsIFJGQyA1MjE2IGhhcyBxdWl0ZQ0K
IGRldGFpbGVkIGd1aWRlbGluZXMgb24gY2VydGlmaWNhdGUgcmV2b2NhdGlvbiBjaGVja2luZyB3
aXRoIENSTHMgYW5kIE9DU1Agc28gSSBkb24ndCBzZWUgYW55IHNlbnNpYmxlIHJlYXNvbiBvbiB3
aHkgYW4gdXBkYXRlIHRvIGl0IHNob3VsZCBub3QgY29udGFpbiByZWxldmFudCB0ZXh0LiBNaWNo
YWVsIHdyb3RlICZxdW90OyB3ZSBhcmUgdW5kZXIgbm8gYWRkaXRpb25hbCBjb21wdWxzaW9uIHRv
IHN1cHBvcnQgcmV2b2NhdGlvbiB0aGFuIHdlIHdlcmUgYmVmb3JlLiZxdW90Ow0KIERvIHlvdSBz
ZWUgdGhlIHByb2JsZW0gaGVyZSBnaXZlbiB0aGUgdGV4dCBpbiBSRkMgNTIxNiBzaG93biBhYm92
ZT88YnI+DQo8L3A+DQo8cD5XaGlsZSBFbGxpb3QgYW5kIEhhbm5lcyBoYXZlIGJlZW4gdm9jYWwg
YWJvdXQgdGhlaXIgdmlld3MsIHdlIGFsc28gc2F3IGZlZWRiYWNrIGZyb20gSmFuZnJlZCBleHBs
YWluaW5nIHRoZSBzaXR1YXRpb24gd2l0aG91dCBPQ1NQIGluIGEgbGl2ZSBuZXR3b3JrIGxpa2Ug
ZWR1cm9hbToNCjxhIG1vei1kby1ub3Qtc2VuZD0idHJ1ZSIgaHJlZj0iaHR0cHM6Ly9tYWlsYXJj
aGl2ZS5pZXRmLm9yZy9hcmNoL21zZy9lbXUvWDlNbTI0TFN6YXE2M2JIU3Zta0JiaVNzckpjLyI+
DQpodHRwczovL21haWxhcmNoaXZlLmlldGYub3JnL2FyY2gvbXNnL2VtdS9YOU1tMjRMU3phcTYz
YkhTdm1rQmJpU3NySmMvPC9hPi4gSGUgZW5kcyBoaXMgZW1haWwgd2l0aDxicj4NCjwvcD4NCjxw
PjwvcD4NCjxibG9ja3F1b3RlIHR5cGU9ImNpdGUiPg0KPHByZSBjbGFzcz0id29yZHdyYXAiPkFs
bCBpbiBhbGwsIEkgZGVmaW5pdGVseSB0aGluayB0aGF0IG1ha2luZyBPQ1NQIFN0YXBsaW5nIG9w
dGlvbmFsIHdpbGwNCmhhdmUgYSBiZW5lZml0IG9uIHNtYWxsIGRldmljZXMsIGJ1dCBlc3BlY2lh
bGx5IGZvciB0aGUgZGl2ZXJzZQ0KZW52aXJvbm1lbnQgb2YgZWR1cm9hbSwgbWFraW5nIE9DU1Ag
U3RhcGxpbmcgbWFuZGF0b3J5IHdpbGwgaW5jcmVhc2UgdGhlDQpvdmVyYWxsIHNlY3VyaXR5IG9m
IHRoaXMgZmVkZXJhdGlvbi4NCk1heWJlIGl0IG1pZ2h0IGJlIGEgZ29vZCBpZGVhIHRvIG1ha2Ug
T0NTUCBTdGFwbGluZyBtYW5kYXRvcnkgZm9yDQpFQVAtVExTIFNlcnZlcnM/PC9wcmU+DQo8L2Js
b2NrcXVvdGU+DQo8cD48L3A+DQo8cD5TbyB3aGVyZSB3ZSBhcmUgd2l0aCB0aGUgY3VycmVudCBk
cmFmdC4gVGhlIGN1cnJlbnQgZHJhZnQgKDxhIGNsYXNzPSJtb3otdHh0LWxpbmstZnJlZXRleHQi
IGhyZWY9Imh0dHBzOi8vdG9vbHMuaWV0Zi5vcmcvaHRtbC9kcmFmdC1pZXRmLWVtdS1lYXAtdGxz
MTMtMTEjc2VjdGlvbi01LjQiPmh0dHBzOi8vdG9vbHMuaWV0Zi5vcmcvaHRtbC9kcmFmdC1pZXRm
LWVtdS1lYXAtdGxzMTMtMTEjc2VjdGlvbi01LjQ8L2E+KSBzYXlzLCAmcXVvdDtXaGVuIEVBUC1U
TFMNCiBpcyB1c2VkIHdpdGggVExTIDEuMywgdGhlIHNlcnZlciBNVVNUIGNoZWNrIHRoZSByZXZv
Y2F0aW9uIHN0YXR1cyBvZiB0aGUgY2VydGlmaWNhdGVzIGluIHRoZSBjbGllbnQncyBjZXJ0aWZp
Y2F0ZSBjaGFpbi4mcXVvdDsuIEl0IGRvZXNuJ3QgbWFuZGF0ZSBhbnkgc3BlY2lmaWMgdGVjaG5p
cXVlLiBZb3UgYXJlIGZyZWUgdG8gdXNlIHdoYXRldmVyIHByb3ByaWV0eSAocG90ZW50aWFsbHkg
aW5zZWN1cmUpIG1ldGhvZCB5b3Ugd2FudC4gVGhlIHJldm9jYXRpb24NCiBjaGVja2luZyBjb3Vs
ZCB1c2UgdGhlIGZvbGxvd2luZyBwc2V1ZG9jb2RlIGZvciBjaGVja2luZyB0aGUgcmV2b2NhdGlv
biBzdGF0dXMgb2YgY2xpZW50IGNlcnRpZmljYXRlczo8L3A+DQo8cD5mdW4gY2hlY2tfcmV2b2Nh
dGlvbiB7PGJyPg0KcmV0dXJuIHN1Y2Nlc3M7PGJyPg0KfTwvcD4NCjxwPmFuZCB5b3Ugd291bGQg
Y29tcGx5IHdpdGggc3BlY2lmaWNhdGlvbi4gTmF0dXJhbGx5LCB1c2luZyBDUkxzIG9yIGxvY2Fs
bHktY29uZmlndXJlZCBPQ1NQIHJlc3BvbmRlciBvbiB0aGUgc2VydmVyIChmb3IgcmV2b2NhdGlv
biBjaGVja2luZyBvZiBjbGllbnQgY2VydGlmaWNhdGVzKSB3aWxsIGdldCB5b3UgYmV0dGVyIHNl
Y3VyaXR5LiBUaGUgY3VycmVudCB0ZXh0IGluIHRoZSBkcmFmdCBkb2VzIG1hbmRhdGUgT0NTUCBz
dGFwbGluZyBmb3INCiBjbGllbnRzIHRvIHZlcmlmeSB0aGUgcmV2b2NhdGlvbiBzdGF0dXMgb2Yg
c2VydmVyIGNlcnRpZmljYXRlcy4gR2l2ZW4gdGhlIHJlc2lzdGFuY2UgaW4gdGhlIHdvcmtpbmcg
Z3JvdXAsIEkgdGhpbmsgaXQgaXMgYSByZWFzb25hYmxlIGNvbXByb21pc2UgZm9yIHNlcnZlcnMg
dG8gaW1wbGVtZW50IE9DU1Agc3RhcGxpbmcuIENsaWVudHMgY2FuIGltcGxlbWVudCBhbmQgdXNl
IGl0LCBidXQgdGhleSB3b3VsZCBiZSBjb21wbGlhbnQgZXZlbiBpZiB0aGV5DQogZG9uJ3QuIFNv
IHRoZSB1cGRhdGVkIHRleHQgd291bGQgYmUgKGFzIEpvZSB3cm90ZSBpbiBoaXMgZW1haWwpOjwv
cD4NCjxwPjwvcD4NCjxibG9ja3F1b3RlIHR5cGU9ImNpdGUiPkVBUC1UTFMgc2VydmVycyBzdXBw
b3J0aW5nIFRMUyAxLjMgTVVTVCBpbXBsZW1lbnQgQ2VydGlmaWNhdGUgU3RhdHVzIFJlcXVlc3Rz
IChPQ1NQIHN0YXBsaW5nKSBhcyBzcGVjaWZpZWQgaW4gU2VjdGlvbiA0LjQuMi4xIG9mIFtSRkM4
NDQ2XS4gSXQgaXMgUkVDT01NRU5ERUQgdGhhdCBFQVAtVExTIHBlZXJzIGFuZCBzZXJ2ZXJzIHVz
ZSBPQ1NQIHN0YXBsaW5nIGZvciB2ZXJpZnlpbmcgdGhlIHN0YXR1cyBvZg0KIHNlcnZlciBjZXJ0
aWZpY2F0ZXMgYXMgc3BlY2lmaWVkIGluIFNlY3Rpb24gNC40LjIuMSBvZiBbUkZDODQ0Nl0uIFdo
ZW4gYW4gRUFQLVRMUyBwZWVyIHVzZXMgT0NTUCB0byB2ZXJpZnkgdGhlIGNlcnRpZmljYXRlIHN0
YXR1cyBvZiB0aGUgRUFQLVRMUyBzZXJ2ZXIsIGl0IE1VU1QgdXNlIENlcnRpZmljYXRlIFN0YXR1
cyBSZXF1ZXN0cyBmb3IgdGhlIHNlcnZlcidzIGNlcnRpZmljYXRlIGNoYWluIGFuZCBpdCBNVVNU
IHRyZWF0IGEgQ2VydGlmaWNhdGVFbnRyeQ0KIChleGNlcHQgdGhlIHRydXN0IGFuY2hvcikgd2l0
aG91dCBhIHZhbGlkIENlcnRpZmljYXRlU3RhdHVzIGV4dGVuc2lvbiBhcyBpbnZhbGlkIGFuZCBh
Ym9ydCB0aGUgaGFuZHNoYWtlIHdpdGggYW4gYXBwcm9wcmlhdGUgYWxlcnQuPC9ibG9ja3F1b3Rl
Pg0KPHA+PC9wPg0KPHA+Tm90ZSB0aGF0IHRoaXMgaXMgYWxzbyBjb21wbGlhbnQgd2l0aCB0aGUg
TklTVCBTUCA4MDAtNTIgUmV2LiAyLiA8YnI+DQo8L3A+DQo8cD4tLU1vaGl0PGJyPg0KPC9wPg0K
PC9ib2R5Pg0KPC9odG1sPg0K

--_000_d339e0e27e3baeb54741a75adba324ecericssoncom_--


From nobody Sat Oct 31 07:19:44 2020
Return-Path: <mohit.m.sethi@ericsson.com>
X-Original-To: emu@ietfa.amsl.com
Delivered-To: emu@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 65ACE3A0BFD; Sat, 31 Oct 2020 07:19:43 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.348
X-Spam-Level: 
X-Spam-Status: No, score=-2.348 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIMWL_WL_HIGH=-0.001, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, DKIM_VALID_EF=-0.1, HTML_MESSAGE=0.001, NICE_REPLY_A=-0.247, RCVD_IN_MSPIKE_H2=-0.001, SPF_PASS=-0.001, URIBL_BLOCKED=0.001] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (1024-bit key) header.d=ericsson.com
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 gMb3iBOzErTa; Sat, 31 Oct 2020 07:19:41 -0700 (PDT)
Received: from EUR03-VE1-obe.outbound.protection.outlook.com (mail-eopbgr50055.outbound.protection.outlook.com [40.107.5.55]) (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 498343A0BFC; Sat, 31 Oct 2020 07:19:39 -0700 (PDT)
ARC-Seal: i=1; a=rsa-sha256; s=arcselector9901; d=microsoft.com; cv=none; b=VJQZz8Q8+4epPSsNnqqNqNVcvzCtg5XGq/FUdr3VSO9meVkHaPDAPcbiOd4ydlJxFl88Tm++46WyxK3wK5z7XDbWLOl5UObrQgfTJyc4SIF6kEW6H/j+wEmeRsbDtUFPFZuEYCLMyHVxaqTNWuj0JPCj2OchrOBdlGyjaX/l3uteKV4WLxhDJyfCXDMClAtFfX+fkPFE4Atn97klep3JFUU2QX0Bouw3R2H+Ydo2NzY5ofaLxhceB9flcwll6iuv/ebchBH0a6ZkKNzb4UkX55F0ZY6gScxyCoyplfkkXqx5JMUoYZk5vfcov1sb/J5q+npthD1uF+5LNlIxsC7rHg==
ARC-Message-Signature: i=1; a=rsa-sha256; c=relaxed/relaxed; d=microsoft.com;  s=arcselector9901; h=From:Date:Subject:Message-ID:Content-Type:MIME-Version:X-MS-Exchange-SenderADCheck; bh=UCKnCqCgjfFTa5jAncrMZipS35URQooARU4I9xpbPRw=; b=BzRexDqZYao3pfjFGPity7ACTQ6Cee/HfjiBOhfzO0O0WowjM7+PQp7XlP5enLR8WueQU3XtFwrcCnJZPMnv4OdV+l+Bykd//UvskRT1mrPfGN/a0CvcGdS3TB3s3sm+2KCRnOpEZq96QbD0BQTDUoBEqfTtkID0zc3uNjVtJ95REpqOoRCFcedgbigrke1I3mw3nArfPk+BOc1iSzN4xajZ3PBlTjnfdUcwqZTGhBCbugOIq87NLGsZgjrUbjPfso8Z1i6gQvZfr65YqbP3NS/WK+hav0oHDzIWStF7FgIo1FRiRr1GAVsGqRTYmMTywYDODxrj0VivOZ/2LNfw1g==
ARC-Authentication-Results: i=1; mx.microsoft.com 1; spf=pass smtp.mailfrom=ericsson.com; dmarc=pass action=none header.from=ericsson.com; dkim=pass header.d=ericsson.com; arc=none
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=ericsson.com; s=selector1; h=From:Date:Subject:Message-ID:Content-Type:MIME-Version:X-MS-Exchange-SenderADCheck; bh=UCKnCqCgjfFTa5jAncrMZipS35URQooARU4I9xpbPRw=; b=aZQ++vkigc/ugxucwIoG3GIut2xsKXDDBgEix+kfpyqdH5r6A3C2Y8qEFDWz7hIK2Gh0uY3ZirDH1It2lLYnMZD1WCiEem9xJRk9Y6cQaFr2wtPu7l9ORmycGNthc6GA83Gog/kvxP3MxoyA/xkURODHKWJpKlxiMpQsFGlUFC8=
Received: from HE1PR07MB3209.eurprd07.prod.outlook.com (2603:10a6:7:32::14) by HE1PR0702MB3547.eurprd07.prod.outlook.com (2603:10a6:7:85::31) with Microsoft SMTP Server (version=TLS1_2, cipher=TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384) id 15.20.3499.17; Sat, 31 Oct 2020 14:19:31 +0000
Received: from HE1PR07MB3209.eurprd07.prod.outlook.com ([fe80::1550:2d88:a5be:95ca]) by HE1PR07MB3209.eurprd07.prod.outlook.com ([fe80::1550:2d88:a5be:95ca%6]) with mapi id 15.20.3499.028; Sat, 31 Oct 2020 14:19:31 +0000
From: Mohit Sethi M <mohit.m.sethi@ericsson.com>
To: Stefan Santesson <stefan@aaa-sec.com>, Mohit Sethi M <mohit.m.sethi@ericsson.com>, Benjamin Kaduk <kaduk@mit.edu>
CC: "last-call@ietf.org" <last-call@ietf.org>, "draft-ietf-emu-eaptlscert.all@ietf.org" <draft-ietf-emu-eaptlscert.all@ietf.org>, "emu@ietf.org" <emu@ietf.org>, "secdir@ietf.org" <secdir@ietf.org>
Thread-Topic: [Emu] Secdir last call review of draft-ietf-emu-eaptlscert-06
Thread-Index: AQHWrkkTSwTr5auJQke8Pqw//Tx6KKmvdiCAgAC0B4CAAA58AIABjHwA
Date: Sat, 31 Oct 2020 14:19:31 +0000
Message-ID: <36dd411f-853c-f7fb-957a-c6eb90be130b@ericsson.com>
References: <160401318284.11167.6795105917637378641@ietfa.amsl.com> <20201030030415.GE39170@kduck.mit.edu> <12167567-9dc5-6161-abef-826b0a8b6602@ericsson.com> <2F8F716A-C063-4DF4-8384-BBD59C636C8A@aaa-sec.com>
In-Reply-To: <2F8F716A-C063-4DF4-8384-BBD59C636C8A@aaa-sec.com>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
user-agent: Mozilla/5.0 (X11; Linux x86_64; rv:68.0) Gecko/20100101 Thunderbird/68.10.0
authentication-results: aaa-sec.com; dkim=none (message not signed) header.d=none;aaa-sec.com; dmarc=none action=none header.from=ericsson.com;
x-originating-ip: [37.136.189.206]
x-ms-publictraffictype: Email
x-ms-office365-filtering-correlation-id: fcffd502-68e3-4f11-0ff7-08d87da7fc12
x-ms-traffictypediagnostic: HE1PR0702MB3547:
x-ms-exchange-transport-forked: True
x-microsoft-antispam-prvs: <HE1PR0702MB3547057148EC47B7322AE8E3D0120@HE1PR0702MB3547.eurprd07.prod.outlook.com>
x-ms-oob-tlc-oobclassifiers: OLM:10000;
x-ms-exchange-senderadcheck: 1
x-microsoft-antispam: BCL:0;
x-microsoft-antispam-message-info: LUWzNfV0YvrXv0mSbRDHbej5L3XJwo/G8ub7V0+74G8v141W4v3LJAVIeMj3EsBXGmgPnv002bWn62qh5sKRe6gYd87an61LEXZGVkE2s5NxdTQlcVAcqMqGRUet5VwLwsOmEpp7yVw66kpEv784FWewjocKGDGhcR9MdpVjSa1j7aF21aKlofh6jdToev7mgfl/+IsE1eGIGQ20tv+qf8Dne6jp5am4zTDD/5HrQn/4DcTo6IVpnKx3MrUTdfWiKWuV4bOXpLrUiL0LJiJDM2a+tu3tlnX0snL5q+YedrMKUBDN89R+v2y9ebK1+mUp9AHXv/S6sZPpA8PYAW6X7JKsvDKYETmWow468zSDbv6wolYheUm1UThMjYPcHzPM0JO8OjurWFdscqoGbYbTAnBB8JPvw9+qTpjHHbe8EEl10SaJzfxuDhCJJl2uZyGuJhYuUaxtUuZWVyq0lliVbQ==
x-forefront-antispam-report: CIP:255.255.255.255; CTRY:; LANG:en; SCL:1; SRV:;  IPV:NLI; SFV:NSPM; H:HE1PR07MB3209.eurprd07.prod.outlook.com; PTR:; CAT:NONE;  SFS:(4636009)(376002)(396003)(346002)(366004)(136003)(39860400002)(2616005)(166002)(966005)(6506007)(53546011)(6486002)(316002)(186003)(86362001)(4326008)(83380400001)(4001150100001)(71200400001)(5660300002)(2906002)(66476007)(66446008)(64756008)(66556008)(54906003)(110136005)(478600001)(66946007)(6512007)(76116006)(8936002)(31696002)(31686004)(8676002)(26005)(36756003)(43740500002); DIR:OUT; SFP:1101; 
x-ms-exchange-antispam-messagedata: qA4tGYis09LVqOduykv0RCJQ+5f5x/ykGTiFNjSm7+WJdyDpPnZHN7hTtBMomUMuLzantGh5QxsfVuzFt+jX7ny3TMlwuY13GBzZoFifVvFtOKZsOl6N6MrpaxBotCCTd5HQjgL1MTkjGjrv50lu8L/bk8jkz7vE9ZZOOrtdBy1AXPrA274ZZyGotqzvXq55YRO3vhgXNK8VDd0u4i6gizNdvD09QuThfXA0/r7uOYtEykOxYzUm5uSIpzJ33X6oQwnuQKqW0T7VRhi7u4xhrvj1O1i02sNfwa6taJBeXnWZtcBOP14W5TFmzIYIqYgc9pdcnGDUedZSAy0hJ5muRGQ9P8LITqsUJesuopCIEwtAAyhbjEQS6XBlPPOeYBCwDkH9ubcXFCR2+E+BrSCkqmEWC5F0X27DELFH6r9+4reh3WvRB6Vlm3oc50Awvey2JsEfbCdNQRvDRRohoh7NMKF5mjrFhqFHbnj2EwXCbCZfvPEWapbfagGTAlFuyoU0HK0kwoyBp0Wk8WSXDzrzr0f+75u3lb7pNyUP+wR5M/EYBIyDca5M6AbiM5Xt5GblUWA22rXn7MSAl2wY6YoMOLyZvyFoTIiM0tXb5IJpbkrkrG+6duNRTcSZILgf25PmCK6RIWmytk1Onndq1VdQzg==
Content-Type: multipart/alternative; boundary="_000_36dd411f853cf7fb957ac6eb90be130bericssoncom_"
MIME-Version: 1.0
X-OriginatorOrg: ericsson.com
X-MS-Exchange-CrossTenant-AuthAs: Internal
X-MS-Exchange-CrossTenant-AuthSource: HE1PR07MB3209.eurprd07.prod.outlook.com
X-MS-Exchange-CrossTenant-Network-Message-Id: fcffd502-68e3-4f11-0ff7-08d87da7fc12
X-MS-Exchange-CrossTenant-originalarrivaltime: 31 Oct 2020 14:19:31.3548 (UTC)
X-MS-Exchange-CrossTenant-fromentityheader: Hosted
X-MS-Exchange-CrossTenant-id: 92e84ceb-fbfd-47ab-be52-080c6b87953f
X-MS-Exchange-CrossTenant-mailboxtype: HOSTED
X-MS-Exchange-CrossTenant-userprincipalname: rG5O279KSJncMZU4Pci/JRW2QEoC8P8EFru6HNPnnIokz4aQHmbo4DPfxUhw5PuE1CRp0UMWKDSX8fH5MZd+eHzA3TJvhlcjGrP2Olviokk=
X-MS-Exchange-Transport-CrossTenantHeadersStamped: HE1PR0702MB3547
Archived-At: <https://mailarchive.ietf.org/arch/msg/emu/nILzdzhbBOouqpGsvhOMC-14nQk>
Subject: Re: [Emu] Secdir last call review of draft-ietf-emu-eaptlscert-06
X-BeenThere: emu@ietf.org
X-Mailman-Version: 2.1.29
Precedence: list
List-Id: "EAP Methods Update \(EMU\)" <emu.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/emu>, <mailto:emu-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/emu/>
List-Post: <mailto:emu@ietf.org>
List-Help: <mailto:emu-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/emu>, <mailto:emu-request@ietf.org?subject=subscribe>
X-List-Received-Date: Sat, 31 Oct 2020 14:19:43 -0000

--_000_36dd411f853cf7fb957ac6eb90be130bericssoncom_
Content-Type: text/plain; charset="utf-8"
Content-Transfer-Encoding: base64

SGkgU3RlZmFuLA0KDQpJIG1hZGUgYSBtaW5vciB1cGRhdGUgdG8gcmVmbGVjdCB5b3VyIGZlZWRi
YWNrIChodHRwczovL2dpdGh1Yi5jb20vZW11LXdnL2VhcHRscy1sb25nY2VydC9jb21wYXJlLzNh
YzBhMTguLjIwOTMwMjYpOg0KDQpUaHVzLCB0aGUgQUlBIGV4dGVuc2lvbiBjYW4gcmVkdWNlIHRo
ZSBzaXplIG9mIHRoZSBjZXJ0aWZpY2F0ZSBjaGFpbiBieSBvbmx5IGluY2x1ZGluZyBhIHBvaW50
ZXIgdG8gdGhlIGlzc3VlciBjZXJ0aWZpY2F0ZSBpbnN0ZWFkIG9mIGluY2x1ZGluZyB0aGUgZW50
aXJlIGlzc3VlciBjZXJ0aWZpY2F0ZS4gSG93ZXZlciwgaXQgcmVxdWlyZXMgdGhlIHNpZGUgcmVj
ZWl2aW5nIHRoZSBjZXJ0aWZpY2F0ZSBjb250YWluaW5nIHRoZSBleHRlbnNpb24gdG8gaGF2ZSBu
ZXR3b3JrIGNvbm5lY3Rpdml0eSAodW5sZXNzIHRoZSBpbmZvcm1hdGlvbiBpcyBhbHJlYWR5IGNh
Y2hlZCBsb2NhbGx5KS4gTmF0dXJhbGx5LCBzdWNoIGluZGlyZWN0aW9uIGNhbm5vdCBiZSB1c2Vk
IGZvciB0aGUgc2VydmVyIGNlcnRpZmljYXRlIChzaW5jZSBFQVAgcGVlcnMgaW4gbW9zdCBkZXBs
b3ltZW50cyBkbyBub3QgaGF2ZSBuZXR3b3JrIGNvbm5lY3Rpdml0eSBiZWZvcmUgYXV0aGVudGlj
YXRpb24gYW5kIHR5cGljYWxseSBkbyBub3QgbWFpbnRhaW4gYW4gdXAtdG8tZGF0ZSBsb2NhbCBj
YWNoZSBvZiBpc3N1ZXIgY2VydGlmaWNhdGVzKS4NCg0KSG9wZSB0aGlzIGlzIGNvcnJlY3QgKGFu
ZCBzdWZmaWNpZW50KS4NCg0KLS1Nb2hpdA0KDQpPbiAxMC8zMC8yMCA0OjQwIFBNLCBTdGVmYW4g
U2FudGVzc29uIHdyb3RlOg0KDQpIaSwNCg0KSSB0aGluayB0aGUgdGV4dCBpcyBncmVhdC4NCkhv
d2V2ZXIgSSdtIG5vdCBlbnRpcmVseSBjb252aW5jZWQgdGhhdCBBSUEgcmVxdWlyZXMgbmV0d29y
ayBjb25uZWN0aXZpdHkgYXQgYWxsIHRpbWVzLg0KVGhlIEFJQSBDQSBjZXJ0IHVybCBpcyBzdGF0
aWMgYW5kIHdvcmtzIGZpbmUgYXMgaWRlbnRpZmllciBmb3IgYSBsb2NhbGx5IGNhY2hlZCBjZXJ0
DQpUaGUgZmFjdCB0aGF0IGl0IGlzIHRoZSBjb3JyZWN0IGNlcnQgaXMgYXNzdXJlZCBieSB0aGUg
cGF0aCB2YWxpZGF0aW9uIHByb2Nlc3MuDQpBcyBzdWNoLCB0aGUgQUlBIHdvcmtzIGZpbmUgd2l0
aCBhIGh0dHAgY2FjaGUgaW1wbGVtZW50YXRpb24gb3Igc2ltaWxhciBvciBhbnkgb3RoZXIgc29s
dXRpb24gdXNpbmcgbG9jYWxseSBzdG9yZWQgZGF0YS4NCklmIHVzZWQgaW4gYSBsb2NhbCBjb3Jw
b3JhdGUgY29udGV4dCwgYSBjYWNoZSBtZWNoYW5pc20gY291bGQgYmUgcHJvdmlkZWQgd2l0aCBw
cmUtbG9hZGVkIHJlbGV2YW50IGNlcnRzLg0KDQpCdXQgSSBkb27igJl0IGtub3cgaG93IHRoaXMg
bWF5IG9yIG1heSBub3QgaW50ZXJvcGVyYXRlIHdpdGggZGVwbG95ZWQgYmFzZSBvZiBFQVAgaW1w
bGVtZW50YXRpb25zLg0KDQpTdGVmYW4gU2FudGVzc29uDQoNCu+7v09uIDIwMjAtMTAtMzAsIDE0
OjQ4LCAiTW9oaXQgU2V0aGkgTSIgPG1vaGl0Lm0uc2V0aGlAZXJpY3Nzb24uY29tPjxtYWlsdG86
bW9oaXQubS5zZXRoaUBlcmljc3Nvbi5jb20+IHdyb3RlOg0KDQogICAgSGkgU3RlZmFuLA0KDQog
ICAgVGhhbmsgeW91IGZvciB0aGUgcmV2aWV3LiBJIGhhdmUgdXBkYXRlZCB0aGUgZHJhZnQgaW4g
Z2l0aHViDQogICAgKGh0dHBzOi8vZ2l0aHViLmNvbS9lbXUtd2cvZWFwdGxzLWxvbmdjZXJ0KS4g
SGVyZSBpcyB0aGUgZGlmZiBmb3IgeW91cg0KICAgIGNvbnZlbmllbmNlOg0KICAgIGh0dHBzOi8v
dG9vbHMuaWV0Zi5vcmcvcmZjZGlmZj91cmwxPWh0dHBzOi8vdG9vbHMuaWV0Zi5vcmcvaWQvZHJh
ZnQtaWV0Zi1lbXUtZWFwdGxzY2VydC50eHQmdXJsMj1odHRwczovL2VtdS13Zy5naXRodWIuaW8v
ZWFwdGxzLWxvbmdjZXJ0L2RyYWZ0LWlldGYtZW11LWVhcHRsc2NlcnQudHh0Lg0KDQogICAgVGhl
IGZvbGxvd2luZyB0ZXh0IHdhcyBhZGRlZDoNCg0KICAgID4gICAgVGhlIHNpemUgb2YgY2VydGlm
aWNhdGVzIChhbmQgY2VydGlmaWNhdGUgY2hhaW5zKSBtYXkgYWxzbyBpbmNyZWFzZQ0KICAgID4g
ICAgbWFuaWZvbGQgaW4gdGhlIGZ1dHVyZSB3aXRoIHRoZSBpbnRyb2R1Y3Rpb24gb2YgcXVhbnR1
bS1zYWZlDQogICAgPiAgICBjcnlwdG9ncmFwaHkuICBGb3IgZXhhbXBsZSwgbGF0dGljZS1iYXNl
ZCBjcnlwdG9ncmFwaHkgd291bGQgaGF2ZQ0KICAgID4gICAgcHVibGljIGtleXMgb2YgYXBwcm94
aW1hdGVseSAxMDAwIGJ5dGVzIGFuZCBzaWduYXR1cmVzIG9mDQogICAgPiAgICBhcHByb3hpbWF0
ZWx5IDIwMDAgYnl0ZXMuDQogICAgYW5kIGluIFNlY3Rpb24gNC4yLjUNCg0KICAgID4gICAgVGhl
IEF1dGhvcml0eSBJbmZvcm1hdGlvbiBBY2Nlc3MgKEFJQSkgZXh0ZW5zaW9uIHNwZWNpZmllZCBp
bg0KICAgID4gICAgW1JGQzUyODBdIGNhbiBiZSB1c2VkIHdpdGggZW5kLWVudGl0eSBhbmQgQ0Eg
Y2VydGlmaWNhdGVzIHRvIGFjY2Vzcw0KICAgID4gICAgaW5mb3JtYXRpb24gYWJvdXQgdGhlIGlz
c3VlciBvZiB0aGUgY2VydGlmaWNhdGUgaW4gd2hpY2ggdGhlDQogICAgPiAgICBleHRlbnNpb24g
YXBwZWFycy4gIEZvciBleGFtcGxlLCBpdCBjYW4gYmUgdXNlZCB0byBwcm92aWRlIHRoZQ0KICAg
ID4gICAgYWRkcmVzcyBvZiB0aGUgT0NTUCByZXNwb25kZXIgZnJvbSB3aGVyZSByZXZvY2F0aW9u
IHN0YXR1cyBvZiB0aGUNCiAgICA+ICAgIGNlcnRpZmljYXRlIChpbiB3aGljaCB0aGUgZXh0ZW5z
aW9uIGFwcGVhcnMpIGNhbiBiZSBjaGVja2VkLiBJdCBjYW4NCiAgICA+ICAgIGFsc28gYmUgdXNl
ZCB0byBvYnRhaW4gdGhlIGlzc3VlciBjZXJ0aWZpY2F0ZS4gIFRodXMsIHRoZSBBSUENCiAgICA+
ICAgIGV4dGVuc2lvbiBjYW4gcmVkdWNlIHRoZSBzaXplIG9mIHRoZSBjZXJ0aWZpY2F0ZSBjaGFp
biBieSBvbmx5DQogICAgPiAgICBpbmNsdWRpbmcgYSBwb2ludGVyIHRvIHRoZSBpc3N1ZXIgY2Vy
dGlmaWNhdGUgaW5zdGVhZCBvZiBpbmNsdWRpbmcNCiAgICA+ICAgIHRoZSBlbnRpcmUgaXNzdWVy
IGNlcnRpZmljYXRlLiAgSG93ZXZlciwgaXQgcmVxdWlyZXMgdGhlIHNpZGUNCiAgICA+ICAgIHJl
Y2VpdmluZyB0aGUgY2VydGlmaWNhdGUgY29udGFpbmluZyB0aGUgZXh0ZW5zaW9uIHRvIGhhdmUg
bmV0d29yaw0KICAgID4gICAgY29ubmVjdGl2aXR5LiAgTmF0dXJhbGx5LCBzdWNoIGluZGlyZWN0
aW9uIGNhbm5vdCBiZSB1c2VkIGZvciB0aGUNCiAgICA+ICAgIHNlcnZlciBjZXJ0aWZpY2F0ZSAo
c2luY2UgdGhlIEVBUCBwZWVyIGluIG1vc3QgZGVwbG95bWVudHMgZG9lcyBub3QNCiAgICA+ICAg
IGhhdmUgbmV0d29yayBjb25uZWN0aXZpdHkgYmVmb3JlIGF1dGhlbg0KDQogICAgTGV0IG1lIGtu
b3cgd2hhdCB5b3UgdGhpbmsuIEkgYW0gbm90IGFuIGV4cGVydCBvbiBxdWFudHVtIGNyeXB0b2dy
YXBoeQ0KICAgIG9yIG9uIHRoZSBBSUEgZXh0ZW5zaW9uLiBJIHdpbGwgd2FpdCBmb3IgYWxsIHRo
ZSBjb21tZW50cyB0byBjb21lIGluDQogICAgYmVmb3JlIHN1Ym1pdHRpbmcgYSBuZXcgdmVyc2lv
bi4NCg0KICAgIC0tTW9oaXQNCg0KICAgIE9uIDEwLzMwLzIwIDU6MDQgQU0sIEJlbmphbWluIEth
ZHVrIHdyb3RlOg0KICAgID4gSGkgU3RlZmFuLA0KICAgID4NCiAgICA+IFRoYW5rcyBmb3IgdGhl
IHJldmlldzsgaXQgcmFpc2VzIHNvbWUgZ29vZCB0b3BpY3MuDQogICAgPiBSZXBseWluZyBvbiBh
IGNvdXBsZSBwb2ludHMuLi4NCiAgICA+DQogICAgPiBPbiBUaHUsIE9jdCAyOSwgMjAyMCBhdCAw
NDoxMzowMlBNIC0wNzAwLCBTdGVmYW4gU2FudGVzc29uIHZpYSBEYXRhdHJhY2tlciB3cm90ZToN
CiAgICA+PiBSZXZpZXdlcjogU3RlZmFuIFNhbnRlc3Nvbg0KICAgID4+IFJldmlldyByZXN1bHQ6
IEhhcyBOaXRzDQogICAgPj4NCiAgICA+PiBUaGUgZG9jdW1lbnQgaW4gZ2VuZXJhbCBpcyBnb29k
IGFuZCB3ZWxsIHdyaXR0ZW4uDQogICAgPj4NCiAgICA+PiBTb21lIG5pdHMgbmVlZHMgYXR0ZW50
aW9uIGJlZm9yZSBwdWJsaWNhdGlvbiBhcyB0aGUgZ2VuZXJhbCByZXZpZXcgYWxzbyBwb2ludHMN
CiAgICA+PiBvdXQuIEV4IGluIHRoZSBhYnN0cmFjdCAiVGhpcyBkb2N1bWVudCBsb29rcyBhdCB0
aGUgdGhpcyBwcm9ibGVtIg0KICAgID4+DQogICAgPj4gU29tZSBhYmJyZXZpYXRpb25zIG5lZWRz
IHRvIGJlIHNwZWxsZWQgb3V0IGF0IGZpcnN0IHVzYWdlLCBzdWNoIGFzIE1UVSAoTWF4aW11bQ0K
ICAgID4+IFRyYW5zbWlzc2lvbiBVbml0KQ0KICAgID4gTVRVIG1heSBhY3R1YWxseSBiZSBva2F5
OyBwZXINCiAgICA+IGh0dHBzOi8vd3d3LnJmYy1lZGl0b3Iub3JnL21hdGVyaWFscy9hYmJyZXYu
ZXhwYW5zaW9uLnR4dCBpdCBpcyBtYXJrZWQgYXMNCiAgICA+ICJ3ZWxsLWtub3duIiBhbmQgZG9l
cyBub3QgYWx3YXlzIG5lZWQgdG8gYmUgZXhwYW5kZWQuDQogICAgPg0KICAgID4+IE9uIHRoZSBj
b250ZW50IGl0c2VsZiBJIGhhdmUgdHdvIHF1ZXN0aW9uczoNCiAgICA+Pg0KICAgID4+IC0gV291
bGRuJ3QgaXQgYmUgcmVsZXZhbnQgdG8gYWxzbyBkaXNjdXNzIHRoZSByaXNrcyB3aXRoIHJlZ2Fy
ZCB0byBpbnRyb2R1Y3Rpb24NCiAgICA+PiBvZiBxdWFudHVtIHNhZmUgY3J5cHRvLCBpZiB0aGF0
IGxlYWRzIHRvIHNpZ25pZmljYW50bHkgaW5jcmVhc2VkIGtleSBzaXplcz8gSXQNCiAgICA+PiBj
b3VsZCBiZSB0cm91Ymxlc29tZSBpZiB0cmFuc2l0aW9uIHRvIGEgc2FmZXIgY3J5cHRvIGlzIG1h
ZGUgaW1wb3NzaWJsZSBkdWUgdG8NCiAgICA+PiBzaXplIGxpbWl0YXRpb25zLiAtIFdvdWxkIGl0
IGJlIHJlbGV2YW50IHRvIGRpc2N1c3MgdXNhZ2Ugb2YgQUlBIGV4dGVuc2lvbiBhcw0KICAgID4+
IG1lYW5zIG9mIHBvc3NpYmx5IGV4Y2x1ZGluZyBpbnRlcm1lZGlhcnkgY2VydHMgZnJvbSB0aGUg
cGF0aCBhcyB0aGV5IGNvdWxkIGJlDQogICAgPj4gbG9jYXRlZCB1c2luZyBBSUE/DQogICAgPj4N
CiAgICA+PiBGaW5hbGx5LCBJIGFncmVlIHdpdGggdGhlIGdlbmVyYWwgcmV2aWV3IHRoYXQgdGhp
cyBkb2N1bWVudCByZWZlcmVuY2UgcXVpdGUNCiAgICA+PiBzb21lIHdvcmsgaW4gcHJvZ3Jlc3Mu
IElmIHRoaXMgZG9jdW1lbnQgaXMgdG8gYmUgcHVibGlzaGVkIGJlZm9yZSB0aGVzZQ0KICAgID4+
IHJlZmVyZW5jZWQgd29ya3MgYXJlIGNvbmNsdWRlZCwgYXJlIHRoZXJlIGFsdGVybmF0aXZlcyB0
byBtYWtlIHRoZSBzYW1lIHBvaW50Pw0KICAgID4gVGhleSBzZWVtIHRvIG1vc3RseSBiZSBpbmZv
cm1hdGl2ZSByZWZlcmVuY2VzLCBhbmQgc28gd291bGQgbm90IHJlcXVpcmUgdXMNCiAgICA+IHRv
IGhvbGQgcHVibGljYXRpb24gb2YgdGhpcyBkb2N1bWVudC4gIEl0IGlzIHByb2JhYmx5IHN0aWxs
IHdvcnRoDQogICAgPiBjb25zaWRlcmluZyBpZiB0aGVyZSBhcmUgYWx0ZXJuYXRpdmVzIGFueXdh
eSwgdGhvdWdoLg0KICAgID4NCiAgICA+IC1CZW4NCiAgICA+DQogICAgPiBfX19fX19fX19fX19f
X19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fXw0KICAgID4gRW11IG1haWxpbmcgbGlz
dA0KICAgID4gRW11QGlldGYub3JnPG1haWx0bzpFbXVAaWV0Zi5vcmc+DQogICAgPiBodHRwczov
L3d3dy5pZXRmLm9yZy9tYWlsbWFuL2xpc3RpbmZvL2VtdQ0KDQoNCg0K

--_000_36dd411f853cf7fb957ac6eb90be130bericssoncom_
Content-Type: text/html; charset="utf-8"
Content-ID: <E7C80CC8386B524AA72486373F1F30B7@eurprd07.prod.outlook.com>
Content-Transfer-Encoding: base64

PGh0bWw+DQo8aGVhZD4NCjxtZXRhIGh0dHAtZXF1aXY9IkNvbnRlbnQtVHlwZSIgY29udGVudD0i
dGV4dC9odG1sOyBjaGFyc2V0PXV0Zi04Ij4NCjwvaGVhZD4NCjxib2R5Pg0KPHA+SGkgU3RlZmFu
LDwvcD4NCjxwPkkgbWFkZSBhIG1pbm9yIHVwZGF0ZSB0byByZWZsZWN0IHlvdXIgZmVlZGJhY2sg
KDxhIG1vei1kby1ub3Qtc2VuZD0idHJ1ZSIgaHJlZj0iaHR0cHM6Ly9naXRodWIuY29tL2VtdS13
Zy9lYXB0bHMtbG9uZ2NlcnQvY29tcGFyZS8zYWMwYTE4Li4yMDkzMDI2Ij5odHRwczovL2dpdGh1
Yi5jb20vZW11LXdnL2VhcHRscy1sb25nY2VydC9jb21wYXJlLzNhYzBhMTguLjIwOTMwMjY8L2E+
KTo8L3A+DQo8cD48L3A+DQo8YmxvY2txdW90ZSB0eXBlPSJjaXRlIj48c3BhbiBjbGFzcz0iYmxv
Yi1jb2RlLWlubmVyDQogICAgICAgICAgYmxvYi1jb2RlLW1hcmtlciIgZGF0YS1jb2RlLW1hcmtl
cj0iKyI+VGh1cywgdGhlIEFJQSBleHRlbnNpb24gY2FuIHJlZHVjZSB0aGUgc2l6ZSBvZiB0aGUg
Y2VydGlmaWNhdGUgY2hhaW4gYnkgb25seSBpbmNsdWRpbmcgYSBwb2ludGVyIHRvIHRoZSBpc3N1
ZXIgY2VydGlmaWNhdGUgaW5zdGVhZCBvZiBpbmNsdWRpbmcgdGhlIGVudGlyZQ0KIGlzc3VlciBj
ZXJ0aWZpY2F0ZS4gSG93ZXZlciwgaXQgcmVxdWlyZXMgdGhlIHNpZGUgcmVjZWl2aW5nIHRoZSBj
ZXJ0aWZpY2F0ZSBjb250YWluaW5nIHRoZSBleHRlbnNpb24gdG8gaGF2ZSBuZXR3b3JrIGNvbm5l
Y3Rpdml0eSAodW5sZXNzIHRoZSBpbmZvcm1hdGlvbiBpcyBhbHJlYWR5IGNhY2hlZCBsb2NhbGx5
KS4gTmF0dXJhbGx5LCBzdWNoIGluZGlyZWN0aW9uIGNhbm5vdCBiZSB1c2VkIGZvciB0aGUgc2Vy
dmVyIGNlcnRpZmljYXRlIChzaW5jZQ0KIEVBUCBwZWVycyBpbiBtb3N0IGRlcGxveW1lbnRzIGRv
IG5vdCBoYXZlIG5ldHdvcmsgY29ubmVjdGl2aXR5IGJlZm9yZSBhdXRoZW50aWNhdGlvbiBhbmQg
dHlwaWNhbGx5IGRvIG5vdCBtYWludGFpbiBhbiB1cC10by1kYXRlIGxvY2FsIGNhY2hlIG9mIGlz
c3VlciBjZXJ0aWZpY2F0ZXMpLjwvc3Bhbj48L2Jsb2NrcXVvdGU+DQo8cD48L3A+DQo8cD5Ib3Bl
IHRoaXMgaXMgY29ycmVjdCAoYW5kIHN1ZmZpY2llbnQpLiA8YnI+DQo8L3A+DQo8cD4tLU1vaGl0
PC9wPg0KPGRpdiBjbGFzcz0ibW96LWNpdGUtcHJlZml4Ij5PbiAxMC8zMC8yMCA0OjQwIFBNLCBT
dGVmYW4gU2FudGVzc29uIHdyb3RlOjxicj4NCjwvZGl2Pg0KPGJsb2NrcXVvdGUgdHlwZT0iY2l0
ZSIgY2l0ZT0ibWlkOjJGOEY3MTZBLUMwNjMtNERGNC04Mzg0LUJCRDU5QzYzNkM4QUBhYWEtc2Vj
LmNvbSI+DQo8cHJlIGNsYXNzPSJtb3otcXVvdGUtcHJlIiB3cmFwPSIiPkhpLA0KDQpJIHRoaW5r
IHRoZSB0ZXh0IGlzIGdyZWF0LiANCkhvd2V2ZXIgSSdtIG5vdCBlbnRpcmVseSBjb252aW5jZWQg
dGhhdCBBSUEgcmVxdWlyZXMgbmV0d29yayBjb25uZWN0aXZpdHkgYXQgYWxsIHRpbWVzLg0KVGhl
IEFJQSBDQSBjZXJ0IHVybCBpcyBzdGF0aWMgYW5kIHdvcmtzIGZpbmUgYXMgaWRlbnRpZmllciBm
b3IgYSBsb2NhbGx5IGNhY2hlZCBjZXJ0DQpUaGUgZmFjdCB0aGF0IGl0IGlzIHRoZSBjb3JyZWN0
IGNlcnQgaXMgYXNzdXJlZCBieSB0aGUgcGF0aCB2YWxpZGF0aW9uIHByb2Nlc3MuDQpBcyBzdWNo
LCB0aGUgQUlBIHdvcmtzIGZpbmUgd2l0aCBhIGh0dHAgY2FjaGUgaW1wbGVtZW50YXRpb24gb3Ig
c2ltaWxhciBvciBhbnkgb3RoZXIgc29sdXRpb24gdXNpbmcgbG9jYWxseSBzdG9yZWQgZGF0YS4N
CklmIHVzZWQgaW4gYSBsb2NhbCBjb3Jwb3JhdGUgY29udGV4dCwgYSBjYWNoZSBtZWNoYW5pc20g
Y291bGQgYmUgcHJvdmlkZWQgd2l0aCBwcmUtbG9hZGVkIHJlbGV2YW50IGNlcnRzLg0KDQpCdXQg
SSBkb27igJl0IGtub3cgaG93IHRoaXMgbWF5IG9yIG1heSBub3QgaW50ZXJvcGVyYXRlIHdpdGgg
ZGVwbG95ZWQgYmFzZSBvZiBFQVAgaW1wbGVtZW50YXRpb25zLg0KDQpTdGVmYW4gU2FudGVzc29u
IA0KDQrvu79PbiAyMDIwLTEwLTMwLCAxNDo0OCwgJnF1b3Q7TW9oaXQgU2V0aGkgTSZxdW90OyA8
YSBjbGFzcz0ibW96LXR4dC1saW5rLXJmYzIzOTZFIiBocmVmPSJtYWlsdG86bW9oaXQubS5zZXRo
aUBlcmljc3Nvbi5jb20iPiZsdDttb2hpdC5tLnNldGhpQGVyaWNzc29uLmNvbSZndDs8L2E+IHdy
b3RlOg0KDQogICAgSGkgU3RlZmFuLA0KDQogICAgVGhhbmsgeW91IGZvciB0aGUgcmV2aWV3LiBJ
IGhhdmUgdXBkYXRlZCB0aGUgZHJhZnQgaW4gZ2l0aHViIA0KICAgICg8YSBjbGFzcz0ibW96LXR4
dC1saW5rLWZyZWV0ZXh0IiBocmVmPSJodHRwczovL2dpdGh1Yi5jb20vZW11LXdnL2VhcHRscy1s
b25nY2VydCI+aHR0cHM6Ly9naXRodWIuY29tL2VtdS13Zy9lYXB0bHMtbG9uZ2NlcnQ8L2E+KS4g
SGVyZSBpcyB0aGUgZGlmZiBmb3IgeW91ciANCiAgICBjb252ZW5pZW5jZTogDQogICAgPGEgY2xh
c3M9Im1vei10eHQtbGluay1mcmVldGV4dCIgaHJlZj0iaHR0cHM6Ly90b29scy5pZXRmLm9yZy9y
ZmNkaWZmP3VybDE9aHR0cHM6Ly90b29scy5pZXRmLm9yZy9pZC9kcmFmdC1pZXRmLWVtdS1lYXB0
bHNjZXJ0LnR4dCZhbXA7dXJsMj1odHRwczovL2VtdS13Zy5naXRodWIuaW8vZWFwdGxzLWxvbmdj
ZXJ0L2RyYWZ0LWlldGYtZW11LWVhcHRsc2NlcnQudHh0Ij5odHRwczovL3Rvb2xzLmlldGYub3Jn
L3JmY2RpZmY/dXJsMT1odHRwczovL3Rvb2xzLmlldGYub3JnL2lkL2RyYWZ0LWlldGYtZW11LWVh
cHRsc2NlcnQudHh0JmFtcDt1cmwyPWh0dHBzOi8vZW11LXdnLmdpdGh1Yi5pby9lYXB0bHMtbG9u
Z2NlcnQvZHJhZnQtaWV0Zi1lbXUtZWFwdGxzY2VydC50eHQ8L2E+Lg0KDQogICAgVGhlIGZvbGxv
d2luZyB0ZXh0IHdhcyBhZGRlZDoNCg0KICAgICZndDsgICAgVGhlIHNpemUgb2YgY2VydGlmaWNh
dGVzIChhbmQgY2VydGlmaWNhdGUgY2hhaW5zKSBtYXkgYWxzbyBpbmNyZWFzZQ0KICAgICZndDsg
ICAgbWFuaWZvbGQgaW4gdGhlIGZ1dHVyZSB3aXRoIHRoZSBpbnRyb2R1Y3Rpb24gb2YgcXVhbnR1
bS1zYWZlDQogICAgJmd0OyAgICBjcnlwdG9ncmFwaHkuICBGb3IgZXhhbXBsZSwgbGF0dGljZS1i
YXNlZCBjcnlwdG9ncmFwaHkgd291bGQgaGF2ZQ0KICAgICZndDsgICAgcHVibGljIGtleXMgb2Yg
YXBwcm94aW1hdGVseSAxMDAwIGJ5dGVzIGFuZCBzaWduYXR1cmVzIG9mDQogICAgJmd0OyAgICBh
cHByb3hpbWF0ZWx5IDIwMDAgYnl0ZXMuDQogICAgYW5kIGluIFNlY3Rpb24gNC4yLjUNCg0KICAg
ICZndDsgICAgVGhlIEF1dGhvcml0eSBJbmZvcm1hdGlvbiBBY2Nlc3MgKEFJQSkgZXh0ZW5zaW9u
IHNwZWNpZmllZCBpbg0KICAgICZndDsgICAgW1JGQzUyODBdIGNhbiBiZSB1c2VkIHdpdGggZW5k
LWVudGl0eSBhbmQgQ0EgY2VydGlmaWNhdGVzIHRvIGFjY2Vzcw0KICAgICZndDsgICAgaW5mb3Jt
YXRpb24gYWJvdXQgdGhlIGlzc3VlciBvZiB0aGUgY2VydGlmaWNhdGUgaW4gd2hpY2ggdGhlDQog
ICAgJmd0OyAgICBleHRlbnNpb24gYXBwZWFycy4gIEZvciBleGFtcGxlLCBpdCBjYW4gYmUgdXNl
ZCB0byBwcm92aWRlIHRoZQ0KICAgICZndDsgICAgYWRkcmVzcyBvZiB0aGUgT0NTUCByZXNwb25k
ZXIgZnJvbSB3aGVyZSByZXZvY2F0aW9uIHN0YXR1cyBvZiB0aGUNCiAgICAmZ3Q7ICAgIGNlcnRp
ZmljYXRlIChpbiB3aGljaCB0aGUgZXh0ZW5zaW9uIGFwcGVhcnMpIGNhbiBiZSBjaGVja2VkLiBJ
dCBjYW4NCiAgICAmZ3Q7ICAgIGFsc28gYmUgdXNlZCB0byBvYnRhaW4gdGhlIGlzc3VlciBjZXJ0
aWZpY2F0ZS4gIFRodXMsIHRoZSBBSUENCiAgICAmZ3Q7ICAgIGV4dGVuc2lvbiBjYW4gcmVkdWNl
IHRoZSBzaXplIG9mIHRoZSBjZXJ0aWZpY2F0ZSBjaGFpbiBieSBvbmx5DQogICAgJmd0OyAgICBp
bmNsdWRpbmcgYSBwb2ludGVyIHRvIHRoZSBpc3N1ZXIgY2VydGlmaWNhdGUgaW5zdGVhZCBvZiBp
bmNsdWRpbmcNCiAgICAmZ3Q7ICAgIHRoZSBlbnRpcmUgaXNzdWVyIGNlcnRpZmljYXRlLiAgSG93
ZXZlciwgaXQgcmVxdWlyZXMgdGhlIHNpZGUNCiAgICAmZ3Q7ICAgIHJlY2VpdmluZyB0aGUgY2Vy
dGlmaWNhdGUgY29udGFpbmluZyB0aGUgZXh0ZW5zaW9uIHRvIGhhdmUgbmV0d29yaw0KICAgICZn
dDsgICAgY29ubmVjdGl2aXR5LiAgTmF0dXJhbGx5LCBzdWNoIGluZGlyZWN0aW9uIGNhbm5vdCBi
ZSB1c2VkIGZvciB0aGUNCiAgICAmZ3Q7ICAgIHNlcnZlciBjZXJ0aWZpY2F0ZSAoc2luY2UgdGhl
IEVBUCBwZWVyIGluIG1vc3QgZGVwbG95bWVudHMgZG9lcyBub3QNCiAgICAmZ3Q7ICAgIGhhdmUg
bmV0d29yayBjb25uZWN0aXZpdHkgYmVmb3JlIGF1dGhlbg0KDQogICAgTGV0IG1lIGtub3cgd2hh
dCB5b3UgdGhpbmsuIEkgYW0gbm90IGFuIGV4cGVydCBvbiBxdWFudHVtIGNyeXB0b2dyYXBoeSAN
CiAgICBvciBvbiB0aGUgQUlBIGV4dGVuc2lvbi4gSSB3aWxsIHdhaXQgZm9yIGFsbCB0aGUgY29t
bWVudHMgdG8gY29tZSBpbiANCiAgICBiZWZvcmUgc3VibWl0dGluZyBhIG5ldyB2ZXJzaW9uLg0K
DQogICAgLS1Nb2hpdA0KDQogICAgT24gMTAvMzAvMjAgNTowNCBBTSwgQmVuamFtaW4gS2FkdWsg
d3JvdGU6DQogICAgJmd0OyBIaSBTdGVmYW4sDQogICAgJmd0Ow0KICAgICZndDsgVGhhbmtzIGZv
ciB0aGUgcmV2aWV3OyBpdCByYWlzZXMgc29tZSBnb29kIHRvcGljcy4NCiAgICAmZ3Q7IFJlcGx5
aW5nIG9uIGEgY291cGxlIHBvaW50cy4uLg0KICAgICZndDsNCiAgICAmZ3Q7IE9uIFRodSwgT2N0
IDI5LCAyMDIwIGF0IDA0OjEzOjAyUE0gLTA3MDAsIFN0ZWZhbiBTYW50ZXNzb24gdmlhIERhdGF0
cmFja2VyIHdyb3RlOg0KICAgICZndDsmZ3Q7IFJldmlld2VyOiBTdGVmYW4gU2FudGVzc29uDQog
ICAgJmd0OyZndDsgUmV2aWV3IHJlc3VsdDogSGFzIE5pdHMNCiAgICAmZ3Q7Jmd0Ow0KICAgICZn
dDsmZ3Q7IFRoZSBkb2N1bWVudCBpbiBnZW5lcmFsIGlzIGdvb2QgYW5kIHdlbGwgd3JpdHRlbi4N
CiAgICAmZ3Q7Jmd0Ow0KICAgICZndDsmZ3Q7IFNvbWUgbml0cyBuZWVkcyBhdHRlbnRpb24gYmVm
b3JlIHB1YmxpY2F0aW9uIGFzIHRoZSBnZW5lcmFsIHJldmlldyBhbHNvIHBvaW50cw0KICAgICZn
dDsmZ3Q7IG91dC4gRXggaW4gdGhlIGFic3RyYWN0ICZxdW90O1RoaXMgZG9jdW1lbnQgbG9va3Mg
YXQgdGhlIHRoaXMgcHJvYmxlbSZxdW90Ow0KICAgICZndDsmZ3Q7DQogICAgJmd0OyZndDsgU29t
ZSBhYmJyZXZpYXRpb25zIG5lZWRzIHRvIGJlIHNwZWxsZWQgb3V0IGF0IGZpcnN0IHVzYWdlLCBz
dWNoIGFzIE1UVSAoTWF4aW11bQ0KICAgICZndDsmZ3Q7IFRyYW5zbWlzc2lvbiBVbml0KQ0KICAg
ICZndDsgTVRVIG1heSBhY3R1YWxseSBiZSBva2F5OyBwZXINCiAgICAmZ3Q7IDxhIGNsYXNzPSJt
b3otdHh0LWxpbmstZnJlZXRleHQiIGhyZWY9Imh0dHBzOi8vd3d3LnJmYy1lZGl0b3Iub3JnL21h
dGVyaWFscy9hYmJyZXYuZXhwYW5zaW9uLnR4dCI+aHR0cHM6Ly93d3cucmZjLWVkaXRvci5vcmcv
bWF0ZXJpYWxzL2FiYnJldi5leHBhbnNpb24udHh0PC9hPiBpdCBpcyBtYXJrZWQgYXMNCiAgICAm
Z3Q7ICZxdW90O3dlbGwta25vd24mcXVvdDsgYW5kIGRvZXMgbm90IGFsd2F5cyBuZWVkIHRvIGJl
IGV4cGFuZGVkLg0KICAgICZndDsNCiAgICAmZ3Q7Jmd0OyBPbiB0aGUgY29udGVudCBpdHNlbGYg
SSBoYXZlIHR3byBxdWVzdGlvbnM6DQogICAgJmd0OyZndDsNCiAgICAmZ3Q7Jmd0OyAtIFdvdWxk
bid0IGl0IGJlIHJlbGV2YW50IHRvIGFsc28gZGlzY3VzcyB0aGUgcmlza3Mgd2l0aCByZWdhcmQg
dG8gaW50cm9kdWN0aW9uDQogICAgJmd0OyZndDsgb2YgcXVhbnR1bSBzYWZlIGNyeXB0bywgaWYg
dGhhdCBsZWFkcyB0byBzaWduaWZpY2FudGx5IGluY3JlYXNlZCBrZXkgc2l6ZXM/IEl0DQogICAg
Jmd0OyZndDsgY291bGQgYmUgdHJvdWJsZXNvbWUgaWYgdHJhbnNpdGlvbiB0byBhIHNhZmVyIGNy
eXB0byBpcyBtYWRlIGltcG9zc2libGUgZHVlIHRvDQogICAgJmd0OyZndDsgc2l6ZSBsaW1pdGF0
aW9ucy4gLSBXb3VsZCBpdCBiZSByZWxldmFudCB0byBkaXNjdXNzIHVzYWdlIG9mIEFJQSBleHRl
bnNpb24gYXMNCiAgICAmZ3Q7Jmd0OyBtZWFucyBvZiBwb3NzaWJseSBleGNsdWRpbmcgaW50ZXJt
ZWRpYXJ5IGNlcnRzIGZyb20gdGhlIHBhdGggYXMgdGhleSBjb3VsZCBiZQ0KICAgICZndDsmZ3Q7
IGxvY2F0ZWQgdXNpbmcgQUlBPw0KICAgICZndDsmZ3Q7DQogICAgJmd0OyZndDsgRmluYWxseSwg
SSBhZ3JlZSB3aXRoIHRoZSBnZW5lcmFsIHJldmlldyB0aGF0IHRoaXMgZG9jdW1lbnQgcmVmZXJl
bmNlIHF1aXRlDQogICAgJmd0OyZndDsgc29tZSB3b3JrIGluIHByb2dyZXNzLiBJZiB0aGlzIGRv
Y3VtZW50IGlzIHRvIGJlIHB1Ymxpc2hlZCBiZWZvcmUgdGhlc2UNCiAgICAmZ3Q7Jmd0OyByZWZl
cmVuY2VkIHdvcmtzIGFyZSBjb25jbHVkZWQsIGFyZSB0aGVyZSBhbHRlcm5hdGl2ZXMgdG8gbWFr
ZSB0aGUgc2FtZSBwb2ludD8NCiAgICAmZ3Q7IFRoZXkgc2VlbSB0byBtb3N0bHkgYmUgaW5mb3Jt
YXRpdmUgcmVmZXJlbmNlcywgYW5kIHNvIHdvdWxkIG5vdCByZXF1aXJlIHVzDQogICAgJmd0OyB0
byBob2xkIHB1YmxpY2F0aW9uIG9mIHRoaXMgZG9jdW1lbnQuICBJdCBpcyBwcm9iYWJseSBzdGls
bCB3b3J0aA0KICAgICZndDsgY29uc2lkZXJpbmcgaWYgdGhlcmUgYXJlIGFsdGVybmF0aXZlcyBh
bnl3YXksIHRob3VnaC4NCiAgICAmZ3Q7DQogICAgJmd0OyAtQmVuDQogICAgJmd0Ow0KICAgICZn
dDsgX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX18NCiAgICAm
Z3Q7IEVtdSBtYWlsaW5nIGxpc3QNCiAgICAmZ3Q7IDxhIGNsYXNzPSJtb3otdHh0LWxpbmstYWJi
cmV2aWF0ZWQiIGhyZWY9Im1haWx0bzpFbXVAaWV0Zi5vcmciPkVtdUBpZXRmLm9yZzwvYT4NCiAg
ICAmZ3Q7IDxhIGNsYXNzPSJtb3otdHh0LWxpbmstZnJlZXRleHQiIGhyZWY9Imh0dHBzOi8vd3d3
LmlldGYub3JnL21haWxtYW4vbGlzdGluZm8vZW11Ij5odHRwczovL3d3dy5pZXRmLm9yZy9tYWls
bWFuL2xpc3RpbmZvL2VtdTwvYT4NCg0KDQo8L3ByZT4NCjwvYmxvY2txdW90ZT4NCjwvYm9keT4N
CjwvaHRtbD4NCg==

--_000_36dd411f853cf7fb957ac6eb90be130bericssoncom_--


From nobody Sat Oct 31 09:53:07 2020
Return-Path: <mohit.sethi@nomadiclab.com>
X-Original-To: emu@ietfa.amsl.com
Delivered-To: emu@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 4AE2F3A0656 for <emu@ietfa.amsl.com>; Sat, 31 Oct 2020 09:53:05 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.35
X-Spam-Level: 
X-Spam-Status: No, score=-1.35 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, HTML_MESSAGE=0.001, NICE_REPLY_A=-0.247, RDNS_NONE=0.793, SPF_HELO_NONE=0.001, SPF_NONE=0.001, URIBL_BLOCKED=0.001] autolearn=no autolearn_force=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 y3GNCFQwLz3a for <emu@ietfa.amsl.com>; Sat, 31 Oct 2020 09:53:03 -0700 (PDT)
Received: from gw.nomadiclab.com (unknown [IPv6:2001:14b8:1829:11::2]) by ietfa.amsl.com (Postfix) with ESMTP id AE94E3A0489 for <emu@ietf.org>; Sat, 31 Oct 2020 09:53:02 -0700 (PDT)
Received: from localhost (localhost [127.0.0.1]) by gw.nomadiclab.com (Postfix) with ESMTP id 063FE500499; Sat, 31 Oct 2020 18:53:00 +0200 (EET)
Received: from gw.nomadiclab.com ([127.0.0.1]) by localhost (inside.nomadiclab.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id rGOlzRROGtc7; Sat, 31 Oct 2020 18:52:55 +0200 (EET)
Received: from [127.0.0.1] (localhost [IPv6:::1]) by gw.nomadiclab.com (Postfix) with ESMTP id A3E4C50040B; Sat, 31 Oct 2020 18:52:55 +0200 (EET)
To: Hannes Tschofenig <Hannes.Tschofenig@arm.com>, "emu@ietf.org" <emu@ietf.org>
References: <AM0PR08MB3716D1CAAC616D85118DEAD7FA1C0@AM0PR08MB3716.eurprd08.prod.outlook.com>
From: Mohit <mohit.sethi@nomadiclab.com>
Message-ID: <64b5ee84-5865-d073-b9c1-5690328cfa4a@nomadiclab.com>
Date: Sat, 31 Oct 2020 18:52:55 +0200
User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:68.0) Gecko/20100101 Thunderbird/68.10.0
MIME-Version: 1.0
In-Reply-To: <AM0PR08MB3716D1CAAC616D85118DEAD7FA1C0@AM0PR08MB3716.eurprd08.prod.outlook.com>
Content-Type: multipart/alternative; boundary="------------5A07B58B11892357518193A0"
Content-Language: en-US
Archived-At: <https://mailarchive.ietf.org/arch/msg/emu/xAV_5b4fOYRiBCCjLJQ70Lrm99k>
Subject: Re: [Emu] draft-ietf-emu-eap-tls13-11
X-BeenThere: emu@ietf.org
X-Mailman-Version: 2.1.29
Precedence: list
List-Id: "EAP Methods Update \(EMU\)" <emu.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/emu>, <mailto:emu-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/emu/>
List-Post: <mailto:emu@ietf.org>
List-Help: <mailto:emu-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/emu>, <mailto:emu-request@ietf.org?subject=subscribe>
X-List-Received-Date: Sat, 31 Oct 2020 16:53:05 -0000

This is a multi-part message in MIME format.
--------------5A07B58B11892357518193A0
Content-Type: text/plain; charset=windows-1252; format=flowed
Content-Transfer-Encoding: 7bit

Hi Hannes,

Thanks. I have opened several issues on github based on your review: 
https://github.com/emu-wg/draft-ietf-emu-eap-tls13/issues

--Mohit

On 10/21/20 11:55 AM, Hannes Tschofenig wrote:
>
> Hi all,
>
> Roman asked me to look at draft-ietf-emu-eap-tls13-11.
>
> I have carefully read through the document and I will post my reviews 
> in separate emails.
>
> There are still lots of room for improvement.
>
> Ciao
>
> Hannes
>
> IMPORTANT NOTICE: The contents of this email and any attachments are 
> confidential and may also be privileged. If you are not the intended 
> recipient, please notify the sender immediately and do not disclose 
> the contents to any other person, use it for any purpose, or store or 
> copy the information in any medium. Thank you.
>
> _______________________________________________
> Emu mailing list
> Emu@ietf.org
> https://www.ietf.org/mailman/listinfo/emu

--------------5A07B58B11892357518193A0
Content-Type: text/html; charset=windows-1252
Content-Transfer-Encoding: 8bit

<html>
  <head>
    <meta http-equiv="Content-Type" content="text/html;
      charset=windows-1252">
  </head>
  <body>
    <p>Hi Hannes,</p>
    <p>Thanks. I have opened several issues on github based on your
      review: <a moz-do-not-send="true"
        href="https://github.com/emu-wg/draft-ietf-emu-eap-tls13/issues">https://github.com/emu-wg/draft-ietf-emu-eap-tls13/issues</a></p>
    <p>--Mohit<br>
    </p>
    <div class="moz-cite-prefix">On 10/21/20 11:55 AM, Hannes Tschofenig
      wrote:<br>
    </div>
    <blockquote type="cite"
cite="mid:AM0PR08MB3716D1CAAC616D85118DEAD7FA1C0@AM0PR08MB3716.eurprd08.prod.outlook.com">
      <meta http-equiv="Content-Type" content="text/html;
        charset=windows-1252">
      <meta name="Generator" content="Microsoft Word 15 (filtered
        medium)">
      <style><!--
/* Font Definitions */
@font-face
	{font-family:"Cambria Math";
	panose-1:2 4 5 3 5 4 6 3 2 4;}
@font-face
	{font-family:DengXian;
	panose-1:2 1 6 0 3 1 1 1 1 1;}
@font-face
	{font-family:Calibri;
	panose-1:2 15 5 2 2 2 4 3 2 4;}
@font-face
	{font-family:"\@DengXian";
	panose-1:2 1 6 0 3 1 1 1 1 1;}
/* Style Definitions */
p.MsoNormal, li.MsoNormal, div.MsoNormal
	{margin:0in;
	font-size:11.0pt;
	font-family:"Calibri",sans-serif;}
span.EmailStyle17
	{mso-style-type:personal-compose;
	font-family:"Calibri",sans-serif;
	color:windowtext;}
.MsoChpDefault
	{mso-style-type:export-only;
	font-family:"Calibri",sans-serif;}
@page WordSection1
	{size:8.5in 11.0in;
	margin:1.0in 1.0in 1.0in 1.0in;}
div.WordSection1
	{page:WordSection1;}
--></style><!--[if gte mso 9]><xml>
<o:shapedefaults v:ext="edit" spidmax="1026" />
</xml><![endif]--><!--[if gte mso 9]><xml>
<o:shapelayout v:ext="edit">
<o:idmap v:ext="edit" data="1" />
</o:shapelayout></xml><![endif]-->
      <div class="WordSection1">
        <p class="MsoNormal">Hi all, <o:p></o:p></p>
        <p class="MsoNormal"><o:p> </o:p></p>
        <p class="MsoNormal">Roman asked me to look at
          draft-ietf-emu-eap-tls13-11. <o:p>
          </o:p></p>
        <p class="MsoNormal"><o:p> </o:p></p>
        <p class="MsoNormal">I have carefully read through the document
          and I will post my reviews in separate emails.
          <o:p></o:p></p>
        <p class="MsoNormal">There are still lots of room for
          improvement. <o:p></o:p></p>
        <p class="MsoNormal"><o:p> </o:p></p>
        <p class="MsoNormal">Ciao<o:p></o:p></p>
        <p class="MsoNormal">Hannes<o:p></o:p></p>
        <p class="MsoNormal"><o:p> </o:p></p>
      </div>
      IMPORTANT NOTICE: The contents of this email and any attachments
      are confidential and may also be privileged. If you are not the
      intended recipient, please notify the sender immediately and do
      not disclose the contents to any other person, use it for any
      purpose, or store or copy the information in any medium. Thank
      you.
      <br>
      <fieldset class="mimeAttachmentHeader"></fieldset>
      <pre class="moz-quote-pre" wrap="">_______________________________________________
Emu mailing list
<a class="moz-txt-link-abbreviated" href="mailto:Emu@ietf.org">Emu@ietf.org</a>
<a class="moz-txt-link-freetext" href="https://www.ietf.org/mailman/listinfo/emu">https://www.ietf.org/mailman/listinfo/emu</a>
</pre>
    </blockquote>
  </body>
</html>

--------------5A07B58B11892357518193A0--


From nobody Sat Oct 31 10:04:32 2020
Return-Path: <mohit.m.sethi@ericsson.com>
X-Original-To: emu@ietfa.amsl.com
Delivered-To: emu@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 3814C3A0844 for <emu@ietfa.amsl.com>; Sat, 31 Oct 2020 10:04:30 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.348
X-Spam-Level: 
X-Spam-Status: No, score=-2.348 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIMWL_WL_HIGH=-0.001, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, DKIM_VALID_EF=-0.1, HTML_MESSAGE=0.001, NICE_REPLY_A=-0.247, RCVD_IN_MSPIKE_H2=-0.001, SPF_PASS=-0.001, URIBL_BLOCKED=0.001] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (1024-bit key) header.d=ericsson.com
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 qm5_OUgCsnQy for <emu@ietfa.amsl.com>; Sat, 31 Oct 2020 10:04:28 -0700 (PDT)
Received: from EUR04-VI1-obe.outbound.protection.outlook.com (mail-eopbgr80081.outbound.protection.outlook.com [40.107.8.81]) (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 49D2F3A083F for <emu@ietf.org>; Sat, 31 Oct 2020 10:04:27 -0700 (PDT)
ARC-Seal: i=1; a=rsa-sha256; s=arcselector9901; d=microsoft.com; cv=none; b=M3gq77GIY4hiTbpeRB14EPu8pZ+3PiY5C0wjxHgBWgN3BzfBObUek9UL4FsPPqW+eYGPP+E08WNNlT1BWRXHU4P4suZE3KUPv7hYpMvNRK5/BJQXGbQoHb+qBvNux2xclFi36v653gak4VHjFcn8reD8QIcrZCP/UEqvNKZdYadNrjuYmBwBnlV/NWx8RvcLNTKH4BpCLILjzzY1KkwlpjaRzI1DW023f16M7WGaqLrBBioIr0acX+88a/Wxwp7/csM+FOzoOFBbxDNShd5YmxrIdwEPa5+ld6LhUM54KeLFaw7uR69FSxjQLU52ncakcjMZTEbqUsk+m37OaEjQkg==
ARC-Message-Signature: i=1; a=rsa-sha256; c=relaxed/relaxed; d=microsoft.com;  s=arcselector9901; h=From:Date:Subject:Message-ID:Content-Type:MIME-Version:X-MS-Exchange-SenderADCheck; bh=Nb9p9IUFW4QVLNQ5TZUTdhweUvPaTjkGdtX1V8tXxCg=; b=lgsha1orHfyLescRG8tMbplESXQZQigXaR+V68MIhbumLuGMHM4r/Ko+dCVPmWG2fwXXBoXHwpQibJ1O9jr2VqsMUEzCwXLRst8eotiIATiT/w0J/h7Db2jsy+c9XMlLTp4ZHGLvz7pKXbrJBaoV3ExhWi37kGpsvbYvofcIIz8QLkZ3ZAL2GtVt/EharQIRa7g6xoEfArjll9hden5kiWJbRjJqlUhfezCUKXXZ9dn7NyQBfq7R0pseVpPvRUKe6Oaf5l8+T+cZ9VHw8o3MWCmmCXKGGkVqdD1wHaf0PBo4XOGeLi4PiXZ4HmqNZv9tTWN5yQI1u58R1dJ7AEHtNQ==
ARC-Authentication-Results: i=1; mx.microsoft.com 1; spf=pass smtp.mailfrom=ericsson.com; dmarc=pass action=none header.from=ericsson.com; dkim=pass header.d=ericsson.com; arc=none
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=ericsson.com; s=selector1; h=From:Date:Subject:Message-ID:Content-Type:MIME-Version:X-MS-Exchange-SenderADCheck; bh=Nb9p9IUFW4QVLNQ5TZUTdhweUvPaTjkGdtX1V8tXxCg=; b=RFMvsmiqkWBiMxZWZKT0p1zP5wPrDJ6ATBAMH5k7KNIMOjw7d2nfUWYasr2sA+pyD+5t5PuTUwzNZEoVWM8MUHNJCXZWMqedHKBwaTK8fs3Y+v0AMGQnrTEn48oyi0+TlUk7hTTMKLBgtu4o9vMk6PttSJsD36vv6bRoBA4DHmc=
Received: from HE1PR07MB3209.eurprd07.prod.outlook.com (2603:10a6:7:32::14) by HE1PR07MB3082.eurprd07.prod.outlook.com (2603:10a6:7:38::25) with Microsoft SMTP Server (version=TLS1_2, cipher=TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384) id 15.20.3499.15; Sat, 31 Oct 2020 17:04:25 +0000
Received: from HE1PR07MB3209.eurprd07.prod.outlook.com ([fe80::1550:2d88:a5be:95ca]) by HE1PR07MB3209.eurprd07.prod.outlook.com ([fe80::1550:2d88:a5be:95ca%6]) with mapi id 15.20.3499.028; Sat, 31 Oct 2020 17:04:24 +0000
From: Mohit Sethi M <mohit.m.sethi@ericsson.com>
To: Hannes Tschofenig <Hannes.Tschofenig@arm.com>, "emu@ietf.org" <emu@ietf.org>
Thread-Topic: [Emu] draft-ietf-emu-eap-tls13-11: Conformance with the TLS 13 Spec
Thread-Index: AQHWr6fh4TRyftUxhUabEISAANwIMQ==
Date: Sat, 31 Oct 2020 17:04:24 +0000
Message-ID: <87e7acdb-b5a2-ccff-67bb-63ca2038d05b@ericsson.com>
References: <AM0PR08MB3716356D95FCD7240F205EEBFA1C0@AM0PR08MB3716.eurprd08.prod.outlook.com>
In-Reply-To: <AM0PR08MB3716356D95FCD7240F205EEBFA1C0@AM0PR08MB3716.eurprd08.prod.outlook.com>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
user-agent: Mozilla/5.0 (X11; Linux x86_64; rv:68.0) Gecko/20100101 Thunderbird/68.10.0
authentication-results: arm.com; dkim=none (message not signed) header.d=none;arm.com; dmarc=none action=none header.from=ericsson.com;
x-originating-ip: [2001:14bb:180:15bb:bc96:4bfb:2e27:6503]
x-ms-publictraffictype: Email
x-ms-office365-filtering-correlation-id: bd4c41c2-813b-4eb3-57ba-08d87dbf050b
x-ms-traffictypediagnostic: HE1PR07MB3082:
x-microsoft-antispam-prvs: <HE1PR07MB3082EB97B8DD10DEF5509640D0120@HE1PR07MB3082.eurprd07.prod.outlook.com>
x-ms-oob-tlc-oobclassifiers: OLM:10000;
x-ms-exchange-senderadcheck: 1
x-microsoft-antispam: BCL:0;
x-microsoft-antispam-message-info: iG8bpyfDa9Ptw/SJGj+KWlmH25cMgISUAF46FeyvtDT/w250PZMEh8Ojn+Y+UBWO+ZnJiSmHjcwoo9nWqYKBtPsXVzQpKE4VG9dJqJRm2Hy9dk84SY2cfKjGrjHzDd//SaOVDeJx2zTFrdWJRcevmKROU3/0213uACrqffCp37xea0h99OGj1zYs7975ltcOR1/JDc40M6RXywX0OrHX/qQGv3y89G3DAgINgWeP4xcnFMAzlN6GtHeOy0jOcRHJov+Z3UqqMcuJ5aN7CdO0rhty5Su+VKCrKQen4wVVfQukZFomMhL6wD7wBnNjGgU36bWTGXVC2Vk1kdCOQsm6splIF1uOU5FeQM5zA9IQ733wGaSLnYVP/sEXrwNPmc4zpMvHr46bd/LV7ATAH7oXzyLMj96EtYW+8nmRcC/kWYsyQb0Ry0aeCt0YTuz3HltI89UqxoljudDX51EQ5MtYHw==
x-forefront-antispam-report: CIP:255.255.255.255; CTRY:; LANG:en; SCL:1; SRV:;  IPV:NLI; SFV:NSPM; H:HE1PR07MB3209.eurprd07.prod.outlook.com; PTR:; CAT:NONE;  SFS:(4636009)(136003)(396003)(376002)(346002)(39860400002)(366004)(8676002)(478600001)(316002)(166002)(31696002)(5660300002)(83380400001)(110136005)(71200400001)(53546011)(6506007)(66476007)(31686004)(36756003)(2906002)(64756008)(66446008)(966005)(6486002)(76116006)(66946007)(6512007)(86362001)(8936002)(2616005)(186003)(66556008)(43740500002); DIR:OUT; SFP:1101; 
x-ms-exchange-antispam-messagedata: vQDDjYZ6ox4jjg5HpFf5FHBefFPdEoj0TjzZkFV8glshJRsaQ967+qs5xG7wjQGP01dkDvWP0/6+kD/ru9S25nEZAJebPbvFb3fowaHRPkaqmNoZb2DSnOtNTjwPin6bLLjnM1E2myTCyh7IuVYNuPZG+egpuLbzW8eU6aQv5lGB4xDRmwbogzkRRolPNbhkdWTndUXzdDBzwfnW8IGi4i6Hu73y1PmEsFB0arb9RvzSyTfAcvjjegOMWqdieTLW6rb7V5+B2BLrdI0Af3DIZ3/fKNT0s7yK8PRu9ISKpJpxTAWix9+Z9bHIO+Xy7NFqIBNJgZyST0yRVsb5tgbsZcNebYEfkNzgW/cPS6J+xI7YAkzJ+Y3fTjLMLmh6aPIzaIDzw/wmadlZyWiJrkJxj5uDzixCQ2piQJGG+dQCaMD5QQf0pWfngtzVlm9Isf8493WyDG4YHXsaC/AT0qlj9Qge8bZ7Fz0xdlKbCAsanyE5HaCTcY1n4YQH0Hfd6ks2X43Aia0Zn/zDxarnFJnx3QVzZq6MIP8vmvCnkd16/fnAH6JQK+9r2DGG4/IpGCwo+94Rptvvp4lRCKQrUBn1MyDbbuzWDFn3fFag2RWnvmVR2Tk3/0slr4xhNB3cY+uS2eHZ3zCpszuJ/xswQcg3JnTvqci/Wgyju113EUkTDJkLt6Ne5Hd12kFPTQm9MlpbDZ+pIWC3JY9KmMsgPJNUSg==
x-ms-exchange-transport-forked: True
Content-Type: multipart/alternative; boundary="_000_87e7acdbb5a2ccff67bb63ca2038d05bericssoncom_"
MIME-Version: 1.0
X-OriginatorOrg: ericsson.com
X-MS-Exchange-CrossTenant-AuthAs: Internal
X-MS-Exchange-CrossTenant-AuthSource: HE1PR07MB3209.eurprd07.prod.outlook.com
X-MS-Exchange-CrossTenant-Network-Message-Id: bd4c41c2-813b-4eb3-57ba-08d87dbf050b
X-MS-Exchange-CrossTenant-originalarrivaltime: 31 Oct 2020 17:04:24.8121 (UTC)
X-MS-Exchange-CrossTenant-fromentityheader: Hosted
X-MS-Exchange-CrossTenant-id: 92e84ceb-fbfd-47ab-be52-080c6b87953f
X-MS-Exchange-CrossTenant-mailboxtype: HOSTED
X-MS-Exchange-CrossTenant-userprincipalname: 1TmWWcze0c3nnv9Qb/QSenr1NUsjK/ytRwoCmfaq81gp3+iVNzI4QeHIOnpJAq6ZuKOdisAztLvtRhEyxbk0a69fZXjK9ZwkSkm65r1Q2IM=
X-MS-Exchange-Transport-CrossTenantHeadersStamped: HE1PR07MB3082
Archived-At: <https://mailarchive.ietf.org/arch/msg/emu/n-aBYXZdpqvrwAVwIHZsXXdkU4c>
Subject: Re: [Emu] draft-ietf-emu-eap-tls13-11: Conformance with the TLS 13 Spec
X-BeenThere: emu@ietf.org
X-Mailman-Version: 2.1.29
Precedence: list
List-Id: "EAP Methods Update \(EMU\)" <emu.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/emu>, <mailto:emu-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/emu/>
List-Post: <mailto:emu@ietf.org>
List-Help: <mailto:emu-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/emu>, <mailto:emu-request@ietf.org?subject=subscribe>
X-List-Received-Date: Sat, 31 Oct 2020 17:04:30 -0000

--_000_87e7acdbb5a2ccff67bb63ca2038d05bericssoncom_
Content-Type: text/plain; charset="Windows-1252"
Content-Transfer-Encoding: quoted-printable

Hi Hannes,

Jim Schaad had asked for this: https://mailarchive.ietf.org/arch/msg/emu/Xp=
RkNN-mh5BuiTD1O8iEfz9sM4M/

It is still optional to use. The figure only shows what the exchange would =
look like if a HRR was sent by the server.

--Mohit

On 10/21/20 12:16 PM, Hannes Tschofenig wrote:
Hi all,

Section 2.1.6 says:

"
   An EAP-TLS peer and server SHOULD support the use of
   HelloRetryRequest message.
"

My understanding of the TLS 1.3 specification is that the HelloRetryRequest=
 is not an optional-to-implement message but it is only optional to use.

Is there a reason to deviate from the TLS 1.3 specification? Is there any r=
eason to talk about the HRR message? The purpose of the message is given in=
 the TLS 1.3 spec and whether you use it or not is up to the deployment.

Ciao
Hannes


IMPORTANT NOTICE: The contents of this email and any attachments are confid=
ential and may also be privileged. If you are not the intended recipient, p=
lease notify the sender immediately and do not disclose the contents to any=
 other person, use it for any purpose, or store or copy the information in =
any medium. Thank you.


_______________________________________________
Emu mailing list
Emu@ietf.org<mailto:Emu@ietf.org>
https://www.ietf.org/mailman/listinfo/emu


--_000_87e7acdbb5a2ccff67bb63ca2038d05bericssoncom_
Content-Type: text/html; charset="Windows-1252"
Content-ID: <0D32F01EE5CC474EBA1A8553516717DF@eurprd07.prod.outlook.com>
Content-Transfer-Encoding: quoted-printable

<html>
<head>
<meta http-equiv=3D"Content-Type" content=3D"text/html; charset=3DWindows-1=
252">
</head>
<body>
<p>Hi Hannes,</p>
<p>Jim Schaad had asked for this: <a moz-do-not-send=3D"true" href=3D"https=
://mailarchive.ietf.org/arch/msg/emu/XpRkNN-mh5BuiTD1O8iEfz9sM4M/">
https://mailarchive.ietf.org/arch/msg/emu/XpRkNN-mh5BuiTD1O8iEfz9sM4M/</a><=
/p>
<p>It is still optional to use. The figure only shows what the exchange wou=
ld look like if a HRR was sent by the server.
<br>
</p>
<p>--Mohit<br>
</p>
<div class=3D"moz-cite-prefix">On 10/21/20 12:16 PM, Hannes Tschofenig wrot=
e:<br>
</div>
<blockquote type=3D"cite" cite=3D"mid:AM0PR08MB3716356D95FCD7240F205EEBFA1C=
0@AM0PR08MB3716.eurprd08.prod.outlook.com">
<meta name=3D"Generator" content=3D"Microsoft Word 15 (filtered
        medium)">
<style><!--
/* Font Definitions */
@font-face
	{font-family:"Cambria Math";
	panose-1:2 4 5 3 5 4 6 3 2 4;}
@font-face
	{font-family:DengXian;
	panose-1:2 1 6 0 3 1 1 1 1 1;}
@font-face
	{font-family:Calibri;
	panose-1:2 15 5 2 2 2 4 3 2 4;}
@font-face
	{font-family:"\@DengXian";
	panose-1:2 1 6 0 3 1 1 1 1 1;}
/* Style Definitions */
p.MsoNormal, li.MsoNormal, div.MsoNormal
	{margin:0in;
	font-size:11.0pt;
	font-family:"Calibri",sans-serif;}
span.EmailStyle17
	{mso-style-type:personal-compose;
	font-family:"Calibri",sans-serif;
	color:windowtext;}
.MsoChpDefault
	{mso-style-type:export-only;
	font-family:"Calibri",sans-serif;}
@page WordSection1
	{size:8.5in 11.0in;
	margin:1.0in 1.0in 1.0in 1.0in;}
div.WordSection1
	{page:WordSection1;}
--></style><!--[if gte mso 9]><xml>
<o:shapedefaults v:ext=3D"edit" spidmax=3D"1026" />
</xml><![endif]--><!--[if gte mso 9]><xml>
<o:shapelayout v:ext=3D"edit">
<o:idmap v:ext=3D"edit" data=3D"1" />
</o:shapelayout></xml><![endif]-->
<div class=3D"WordSection1">
<p class=3D"MsoNormal">Hi all, <o:p></o:p></p>
<p class=3D"MsoNormal"><o:p>&nbsp;</o:p></p>
<p class=3D"MsoNormal">Section 2.1.6 says:<o:p></o:p></p>
<p class=3D"MsoNormal"><o:p>&nbsp;</o:p></p>
<p class=3D"MsoNormal">&quot;<o:p></o:p></p>
<p class=3D"MsoNormal">&nbsp;&nbsp; An EAP-TLS peer and server SHOULD suppo=
rt the use of<o:p></o:p></p>
<p class=3D"MsoNormal">&nbsp;&nbsp; HelloRetryRequest message.&nbsp; <o:p><=
/o:p></p>
<p class=3D"MsoNormal">&quot;<o:p></o:p></p>
<p class=3D"MsoNormal"><o:p>&nbsp;</o:p></p>
<p class=3D"MsoNormal">My understanding of the TLS 1.3 specification is tha=
t the HelloRetryRequest is not an optional-to-implement message but it is o=
nly optional to use.
<o:p></o:p></p>
<p class=3D"MsoNormal"><o:p>&nbsp;</o:p></p>
<p class=3D"MsoNormal">Is there a reason to deviate from the TLS 1.3 specif=
ication? Is there any reason to talk about the HRR message? The purpose of =
the message is given in the TLS 1.3 spec and whether you use it or not is u=
p to the deployment.
<o:p></o:p></p>
<p class=3D"MsoNormal"><o:p>&nbsp;</o:p></p>
<p class=3D"MsoNormal">Ciao<o:p></o:p></p>
<p class=3D"MsoNormal">Hannes<o:p></o:p></p>
<p class=3D"MsoNormal"><o:p>&nbsp;</o:p></p>
<p class=3D"MsoNormal">&nbsp;&nbsp; <o:p></o:p></p>
</div>
IMPORTANT NOTICE: The contents of this email and any attachments are confid=
ential and may also be privileged. If you are not the intended recipient, p=
lease notify the sender immediately and do not disclose the contents to any=
 other person, use it for any purpose,
 or store or copy the information in any medium. Thank you. <br>
<fieldset class=3D"mimeAttachmentHeader"></fieldset>
<pre class=3D"moz-quote-pre" wrap=3D"">____________________________________=
___________
Emu mailing list
<a class=3D"moz-txt-link-abbreviated" href=3D"mailto:Emu@ietf.org">Emu@ietf=
.org</a>
<a class=3D"moz-txt-link-freetext" href=3D"https://www.ietf.org/mailman/lis=
tinfo/emu">https://www.ietf.org/mailman/listinfo/emu</a>
</pre>
</blockquote>
</body>
</html>

--_000_87e7acdbb5a2ccff67bb63ca2038d05bericssoncom_--


From nobody Sat Oct 31 10:06:11 2020
Return-Path: <mohit.m.sethi@ericsson.com>
X-Original-To: emu@ietfa.amsl.com
Delivered-To: emu@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id C50273A0844 for <emu@ietfa.amsl.com>; Sat, 31 Oct 2020 10:06:08 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.348
X-Spam-Level: 
X-Spam-Status: No, score=-2.348 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIMWL_WL_HIGH=-0.001, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, DKIM_VALID_EF=-0.1, HTML_MESSAGE=0.001, NICE_REPLY_A=-0.247, RCVD_IN_MSPIKE_H2=-0.001, SPF_PASS=-0.001, URIBL_BLOCKED=0.001] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (1024-bit key) header.d=ericsson.com
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 wvXKPUg6z1dz for <emu@ietfa.amsl.com>; Sat, 31 Oct 2020 10:06:06 -0700 (PDT)
Received: from EUR04-VI1-obe.outbound.protection.outlook.com (mail-eopbgr80089.outbound.protection.outlook.com [40.107.8.89]) (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 06F283A083F for <emu@ietf.org>; Sat, 31 Oct 2020 10:06:05 -0700 (PDT)
ARC-Seal: i=1; a=rsa-sha256; s=arcselector9901; d=microsoft.com; cv=none; b=i7McFXDizu6gOECuLJzxavNOeLfsZBv5RooqFAR/ox5JyWAnxSg9qP0BXO8fvpK5PGIV34w04uMTEdSKP+UZll/MN4k3/uWKSHvR8PLRxxkj54MBCINM/+JGyRfhvoWqdUjzt2h7pDpqsJcseeSwa5LE24rpv7SuomezkXklCf+pQ4gXpZ/cay02sLjii1dvzBbCOSxaiPHLz0mraejO/TXeVmfwblrl6+We/Yy5DIQyl0UiaoHx05kGH9oTPgtKql6O0Y/Mb2qnlwXj0fnS/RLMbMvtL6nGEwmVTIvJrUaH60uAsMulcUXj7yZGx56V55GtA6wZ0Y2nlr7HS5UCjA==
ARC-Message-Signature: i=1; a=rsa-sha256; c=relaxed/relaxed; d=microsoft.com;  s=arcselector9901; h=From:Date:Subject:Message-ID:Content-Type:MIME-Version:X-MS-Exchange-SenderADCheck; bh=SAQOkE+zztsJ5cyG5b5BPYtN0ws8q3dEV75we/d486s=; b=M84YUTDwPzpJ+HLqDp0lLqfjed7xz5eTVrW8TEwQF8RoDHM3VbQp9nIN2b95XAyd5ioXQ6sCKcrmb0YiDkP910AOSTuf14RQ9P1qkkXzaGshONHMOr5nfKrBjmYpKYr2g3amuxNyR6DDjXwjlL7nZNEBs459wmzgUyQvb8RZ9RfGvuJLXEqtcDFzS3BcfEnWciLdPixko1QvBXFmSmsdC1XpZatGz3ehPFiEeuox5KRmctlTsUjZPxuBoNpc6+hKlXPhUfoCzUJaRLkp4uDOby2SlJqllnfnCBJSM/m/mrCq27Tl8nigbykI8WWq480Qjt84j9cyXWSNcGGWARkKXQ==
ARC-Authentication-Results: i=1; mx.microsoft.com 1; spf=pass smtp.mailfrom=ericsson.com; dmarc=pass action=none header.from=ericsson.com; dkim=pass header.d=ericsson.com; arc=none
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=ericsson.com; s=selector1; h=From:Date:Subject:Message-ID:Content-Type:MIME-Version:X-MS-Exchange-SenderADCheck; bh=SAQOkE+zztsJ5cyG5b5BPYtN0ws8q3dEV75we/d486s=; b=gh/TbrGguY18tVIjsxtxGKoxM28dPYQCHIhpDMfcgiMgZLAZB5mtNtQe/aagUAJCHB+KseDnzOtPeXCoksIb9sL2hhNgNtNkQ/ttd71r2uMPMycHv4vzSgfPJlN5mRQ9g9DBP1xgZCkcR7x7oyQgVcvYDfxAoL/S9CqVrwnL2Tc=
Received: from HE1PR07MB3209.eurprd07.prod.outlook.com (2603:10a6:7:32::14) by HE1PR07MB3082.eurprd07.prod.outlook.com (2603:10a6:7:38::25) with Microsoft SMTP Server (version=TLS1_2, cipher=TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384) id 15.20.3499.15; Sat, 31 Oct 2020 17:06:03 +0000
Received: from HE1PR07MB3209.eurprd07.prod.outlook.com ([fe80::1550:2d88:a5be:95ca]) by HE1PR07MB3209.eurprd07.prod.outlook.com ([fe80::1550:2d88:a5be:95ca%6]) with mapi id 15.20.3499.028; Sat, 31 Oct 2020 17:06:03 +0000
From: Mohit Sethi M <mohit.m.sethi@ericsson.com>
To: Hannes Tschofenig <Hannes.Tschofenig@arm.com>, "emu@ietf.org" <emu@ietf.org>
Thread-Topic: [Emu] draft-ietf-emu-eap-tls13-11: Updates RFC 5216
Thread-Index: AQHWr6gda8D+gUqjfEKF9/RDpH1ttA==
Date: Sat, 31 Oct 2020 17:06:03 +0000
Message-ID: <de5c4134-7274-98ea-a6cd-78cfb680ba66@ericsson.com>
References: <AM0PR08MB3716A5224BA1C5D36BC150A0FA1C0@AM0PR08MB3716.eurprd08.prod.outlook.com>
In-Reply-To: <AM0PR08MB3716A5224BA1C5D36BC150A0FA1C0@AM0PR08MB3716.eurprd08.prod.outlook.com>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
user-agent: Mozilla/5.0 (X11; Linux x86_64; rv:68.0) Gecko/20100101 Thunderbird/68.10.0
authentication-results: arm.com; dkim=none (message not signed) header.d=none;arm.com; dmarc=none action=none header.from=ericsson.com;
x-originating-ip: [2001:14bb:180:15bb:bc96:4bfb:2e27:6503]
x-ms-publictraffictype: Email
x-ms-office365-filtering-correlation-id: 4b132183-b5f0-40a4-1c7c-08d87dbf3fd0
x-ms-traffictypediagnostic: HE1PR07MB3082:
x-microsoft-antispam-prvs: <HE1PR07MB308252B542B7C84550D6C1A0D0120@HE1PR07MB3082.eurprd07.prod.outlook.com>
x-ms-oob-tlc-oobclassifiers: OLM:10000;
x-ms-exchange-senderadcheck: 1
x-microsoft-antispam: BCL:0;
x-microsoft-antispam-message-info: g0M0z6ZjAwAJS+WeFJH2PJhr000fGeEq44BtRN74+N0m8Suw5J7TCBR/VawR5btGBGJv2ZShUtKPnTZ+WbFmd1p+yN7Sek7QWUkjU9tRMrHKc3t05cggk9UUET2wKvqLxbwEgYNlMyQP8Qk6xlIultaZGpGL+0+G6W94ggTfCVJi8aKqr0fPBVUwwPvhjonku4xBqP5ujvlJw2fv3NOiAzxiBn6YqdsO5A7X8ETxbFxZoZy/CzoLyACAN/+/lhARNbBBKW7KTHM8I0dsFgqXN560+XO92kNw56WUaEperz2OX6pzhMAYYJrw8Z5QnaGXCPjX33/CJaDA4OiJpk52pCXs9Y9UIzVBjBgH4faO59T6Wm8K1XFJqJz9cvC68sYVPx57YlHWxS/vfb6Iwp50riJh0heSOJTsg/j/VuYu1W+KxH+O1wvgy8Q1JExjq/U0eDqrjLgEgM4I2X4QJherAA==
x-forefront-antispam-report: CIP:255.255.255.255; CTRY:; LANG:en; SCL:1; SRV:;  IPV:NLI; SFV:NSPM; H:HE1PR07MB3209.eurprd07.prod.outlook.com; PTR:; CAT:NONE;  SFS:(4636009)(136003)(396003)(376002)(346002)(39860400002)(366004)(8676002)(478600001)(316002)(166002)(31696002)(15650500001)(5660300002)(83380400001)(110136005)(71200400001)(53546011)(6506007)(66476007)(31686004)(36756003)(2906002)(64756008)(66446008)(966005)(6486002)(76116006)(66946007)(6512007)(86362001)(8936002)(2616005)(186003)(66556008)(43740500002); DIR:OUT; SFP:1101; 
x-ms-exchange-antispam-messagedata: uYiB9SAVBL7gaeh5W1vWJ1jWgG1NduQeQb6zFOmCk6lWTJ1UtBJX6VKswEpU5fJDh7KRunSjhnaRFBCD0oFNqXscOwqCvy8ZV18R6h8XaHnwpgNNEOA5HcKHhTA7/uXRRo3ZPfMWp2q01PMErnjOIsnSRBpfyjubzx0igzmb62GnqbwKnMs2KgVsRlMKTBZNdikSkUnarF468ZKNZvIvPF8I2pd0TYGMTHUWQ3HuwMKcGUQt1Hq++8jjE8As/iQoox9lVG+nvm5g4pnIk51YYhVk5vH4Bc1aEuP/+XFmbX6n80nuF1/tnabmuJZ52Iblth8qe0IB4cWsbWXq+yidA0fwqmjHkOITR0WgMJFURODczQ3g5XT0iOfjE58rdygobKwaFINqc5Eu7VvfT7GnAma0/wFw98BwGBpP61fcY8S+iLfbhe3LLOHooHGKZT9y5mTQnfaNaA6hLJoHwVdw+ss+P4z5U489br4gUEkHpwBkJpuMOgsLm0sawt7LEQBkGPaacD7TRQH9kqHwxi8p6dXZkAqRXh3uZKPqa9fOOayd79u6mW1fibMNNQaVULkH9RoYmiXJMZsEf1fZjfelUEF6o6Mh7T3llmC299QA7rMrkOldUvoxez/2X92ooZbdpN+3TRWXJ7iAHAWckkySifDcs2nbSEl9cpjBWC4exME97xfn47rzpfA6007jnlnP0M0mWqpuRWyXbtN/wVUCkw==
x-ms-exchange-transport-forked: True
Content-Type: multipart/alternative; boundary="_000_de5c4134727498eaa6cd78cfb680ba66ericssoncom_"
MIME-Version: 1.0
X-OriginatorOrg: ericsson.com
X-MS-Exchange-CrossTenant-AuthAs: Internal
X-MS-Exchange-CrossTenant-AuthSource: HE1PR07MB3209.eurprd07.prod.outlook.com
X-MS-Exchange-CrossTenant-Network-Message-Id: 4b132183-b5f0-40a4-1c7c-08d87dbf3fd0
X-MS-Exchange-CrossTenant-originalarrivaltime: 31 Oct 2020 17:06:03.4934 (UTC)
X-MS-Exchange-CrossTenant-fromentityheader: Hosted
X-MS-Exchange-CrossTenant-id: 92e84ceb-fbfd-47ab-be52-080c6b87953f
X-MS-Exchange-CrossTenant-mailboxtype: HOSTED
X-MS-Exchange-CrossTenant-userprincipalname: 7YNr36UWNfcn/PMYw3yTcSF658+oBhV7bJ4dBB8Lz1uVISQYEptGFY5HNYpUrbwjEWogXiNcNw9I3A8RL7SMn5NW1Ec71cLTMqQOjwZhSsk=
X-MS-Exchange-Transport-CrossTenantHeadersStamped: HE1PR07MB3082
Archived-At: <https://mailarchive.ietf.org/arch/msg/emu/V3n5su6IlgXkhTlkgcIUfPYBrPM>
Subject: Re: [Emu] draft-ietf-emu-eap-tls13-11: Updates RFC 5216
X-BeenThere: emu@ietf.org
X-Mailman-Version: 2.1.29
Precedence: list
List-Id: "EAP Methods Update \(EMU\)" <emu.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/emu>, <mailto:emu-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/emu/>
List-Post: <mailto:emu@ietf.org>
List-Help: <mailto:emu-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/emu>, <mailto:emu-request@ietf.org?subject=subscribe>
X-List-Received-Date: Sat, 31 Oct 2020 17:06:09 -0000

--_000_de5c4134727498eaa6cd78cfb680ba66ericssoncom_
Content-Type: text/plain; charset="Windows-1252"
Content-Transfer-Encoding: quoted-printable

Hi Hannes,

This text and guidance was specifically requested by working group members =
like Alan. Unless the text is wrong, I don't see any point in removing it. =
Other TLS-based EAP methods are obviously free to use parts of this text re=
levant to them. Note that their resumption and authorization might be even =
more complex as some decisions may depend on the inner authentication metho=
d.

--Mohit

On 10/21/20 12:00 PM, Hannes Tschofenig wrote:
Hi all,

the draft says it updates the earlier EAP-TLS version and claims that the u=
pdates are related to

* Section 5.6 Authorization
* Section 5.7 Resumption

The content of Section 5.6 actually does not relate to EAP-TLS but is gener=
ic to all EAP methods. I don't think it even belongs in an EAP method docum=
ent.

The content of Section 5.7 claims that there are aspects of resumptions tha=
t are not described in the earlier version of EAP-TLS. The focus is then on=
 the way how the cached data is stored, an implementation-specific aspect, =
that is not specific to EAP-TLS because the concept of caching is used by o=
ther EAP methods too. Then, there is a threat presented whereby the authori=
zation information changes between the full handshake and the resumption ha=
ndshake. I believe that this is not a threat that is unique to EAP-TLS beca=
use this can happen even when there is no resumption. Nothing prevents you =
from checking authorization again when you do resumption though and even du=
ring an ongoing session. I would argue that there is a lot of text in there=
 that has nothing to do with EAP-TLS but rather concerns the whole system i=
n which EAP is used. If this is indeed a problem, I believe it should be co=
vered in a separate document. I don=92t think it is a problem because exten=
sions for RADIUS and Diameter have been developed to address this issue to =
revoke authorization during the lifetime of a session.

Here is where it gets confusing. The introduction says "This document defin=
es how to use EAP-TLS with TLS 1.3 (or higher) and does not change how EAP-=
TLS is used with older versions of TLS." To me, this does not sound like an=
 update.

Reading more carefully one can notice that the actual update to EAP-TLS is =
hidden in Section 5.8 "Privacy Considerations" and Section 5.10 "Discovered=
 Vulnerabilities".

Section 5.8 says:
"
   it is RECOMMENDED for EAP peers to not use EAP-TLS with
   TLS 1.2 and static RSA based cipher suites without privacy.  This
   implies that an EAP peer SHOULD NOT continue the handshake if a TLS
   1.2 EAP server responds to an empty certificate message with a TLS
   alert message.
"

Section 5.10 says:
"
EAP-TLS implementations
   SHOULD mitigate known attacks and follow the recommendations in
   [RFC7525] and [I-D.ietf-tls-oldversions-deprecate].
"

Interestingly, RFC 7525 does not talk about EAP (and instead focuses on app=
lications like  HTTP, SMTP, IMAP, POP, SIP, and XMPP, as noted in the abstr=
act). RFC 7525, for example, does not mandate OCSP. It also recommends RSA,=
 which draft-ietf-emu-eaptlscert and this draft does not do. There seems to=
 be contradiction here.

At a minimum, I would clarify in the introduction what the updates to RFC 5=
216 are. This will help those implementers that focus on a variant of EAP-T=
LS that uses version 1.2. As mentioned above, I don't believe Sections 5.6 =
and 5.7 belong to this document. Leave it in there if someone in the group =
gets paid by the number of published pages.

Ciao
Hannes
IMPORTANT NOTICE: The contents of this email and any attachments are confid=
ential and may also be privileged. If you are not the intended recipient, p=
lease notify the sender immediately and do not disclose the contents to any=
 other person, use it for any purpose, or store or copy the information in =
any medium. Thank you.


_______________________________________________
Emu mailing list
Emu@ietf.org<mailto:Emu@ietf.org>
https://www.ietf.org/mailman/listinfo/emu


--_000_de5c4134727498eaa6cd78cfb680ba66ericssoncom_
Content-Type: text/html; charset="Windows-1252"
Content-ID: <971C92B35A846346B00FA784F84B860A@eurprd07.prod.outlook.com>
Content-Transfer-Encoding: quoted-printable

<html>
<head>
<meta http-equiv=3D"Content-Type" content=3D"text/html; charset=3DWindows-1=
252">
</head>
<body>
<p>Hi Hannes,</p>
<p>This text and guidance was specifically requested by working group membe=
rs like Alan. Unless the text is wrong, I don't see any point in removing i=
t. Other TLS-based EAP methods are obviously free to use parts of this text=
 relevant to them. Note that their
 resumption and authorization might be even more complex as some decisions =
may depend on the inner authentication method.
<br>
</p>
<p>--Mohit<br>
</p>
<div class=3D"moz-cite-prefix">On 10/21/20 12:00 PM, Hannes Tschofenig wrot=
e:<br>
</div>
<blockquote type=3D"cite" cite=3D"mid:AM0PR08MB3716A5224BA1C5D36BC150A0FA1C=
0@AM0PR08MB3716.eurprd08.prod.outlook.com">
<meta name=3D"Generator" content=3D"Microsoft Word 15 (filtered
        medium)">
<style><!--
/* Font Definitions */
@font-face
	{font-family:"Cambria Math";
	panose-1:2 4 5 3 5 4 6 3 2 4;}
@font-face
	{font-family:DengXian;
	panose-1:2 1 6 0 3 1 1 1 1 1;}
@font-face
	{font-family:Calibri;
	panose-1:2 15 5 2 2 2 4 3 2 4;}
@font-face
	{font-family:"\@DengXian";
	panose-1:2 1 6 0 3 1 1 1 1 1;}
/* Style Definitions */
p.MsoNormal, li.MsoNormal, div.MsoNormal
	{margin:0in;
	font-size:11.0pt;
	font-family:"Calibri",sans-serif;}
span.EmailStyle17
	{mso-style-type:personal-compose;
	font-family:"Calibri",sans-serif;
	color:windowtext;}
.MsoChpDefault
	{mso-style-type:export-only;
	font-family:"Calibri",sans-serif;}
@page WordSection1
	{size:8.5in 11.0in;
	margin:1.0in 1.0in 1.0in 1.0in;}
div.WordSection1
	{page:WordSection1;}
--></style><!--[if gte mso 9]><xml>
<o:shapedefaults v:ext=3D"edit" spidmax=3D"1026" />
</xml><![endif]--><!--[if gte mso 9]><xml>
<o:shapelayout v:ext=3D"edit">
<o:idmap v:ext=3D"edit" data=3D"1" />
</o:shapelayout></xml><![endif]-->
<div class=3D"WordSection1">
<p class=3D"MsoNormal">Hi all, <o:p></o:p></p>
<p class=3D"MsoNormal"><o:p>&nbsp;</o:p></p>
<p class=3D"MsoNormal">the draft says it updates the earlier EAP-TLS versio=
n and claims that the updates are related to
<o:p></o:p></p>
<p class=3D"MsoNormal"><o:p>&nbsp;</o:p></p>
<p class=3D"MsoNormal">* Section 5.6 Authorization<o:p></o:p></p>
<p class=3D"MsoNormal">* Section 5.7 Resumption<o:p></o:p></p>
<p class=3D"MsoNormal"><o:p>&nbsp;</o:p></p>
<p class=3D"MsoNormal">The content of Section 5.6 actually does not relate =
to EAP-TLS but is generic to all EAP methods. I don't think it even belongs=
 in an EAP method document.
<o:p></o:p></p>
<p class=3D"MsoNormal"><o:p>&nbsp;</o:p></p>
<p class=3D"MsoNormal">The content of Section 5.7 claims that there are asp=
ects of resumptions that are not described in the earlier version of EAP-TL=
S. The focus is then on the way how the cached data is stored, an implement=
ation-specific aspect, that is not
 specific to EAP-TLS because the concept of caching is used by other EAP me=
thods too. Then, there is a threat presented whereby the authorization info=
rmation changes between the full handshake and the resumption handshake. I =
believe that this is not a threat
 that is unique to EAP-TLS because this can happen even when there is no re=
sumption. Nothing prevents you from checking authorization again when you d=
o resumption though and even during an ongoing session. I would argue that =
there is a lot of text in there
 that has nothing to do with EAP-TLS but rather concerns the whole system i=
n which EAP is used. If this is indeed a problem, I believe it should be co=
vered in a separate document. I don=92t think it is a problem because exten=
sions for RADIUS and Diameter have
 been developed to address this issue to revoke authorization during the li=
fetime of a session.<o:p></o:p></p>
<p class=3D"MsoNormal"><o:p>&nbsp;</o:p></p>
<p class=3D"MsoNormal">Here is where it gets confusing. The introduction sa=
ys &quot;This document defines how to use EAP-TLS with TLS 1.3 (or higher) =
and does not change how EAP-TLS is used with older versions of TLS.&quot; T=
o me, this does not sound like an update.
<o:p></o:p></p>
<p class=3D"MsoNormal"><o:p>&nbsp;</o:p></p>
<p class=3D"MsoNormal">Reading more carefully one can notice that the actua=
l update to EAP-TLS is hidden in Section 5.8 &quot;Privacy Considerations&q=
uot; and Section 5.10 &quot;Discovered Vulnerabilities&quot;.
<o:p></o:p></p>
<p class=3D"MsoNormal"><o:p>&nbsp;</o:p></p>
<p class=3D"MsoNormal">Section 5.8 says:<o:p></o:p></p>
<p class=3D"MsoNormal">&quot;<o:p></o:p></p>
<p class=3D"MsoNormal">&nbsp;&nbsp; it is RECOMMENDED for EAP peers to not =
use EAP-TLS with<o:p></o:p></p>
<p class=3D"MsoNormal">&nbsp;&nbsp; TLS 1.2 and static RSA based cipher sui=
tes without privacy.&nbsp; This<o:p></o:p></p>
<p class=3D"MsoNormal">&nbsp;&nbsp; implies that an EAP peer SHOULD NOT con=
tinue the handshake if a TLS<o:p></o:p></p>
<p class=3D"MsoNormal">&nbsp;&nbsp; 1.2 EAP server responds to an empty cer=
tificate message with a TLS<o:p></o:p></p>
<p class=3D"MsoNormal">&nbsp;&nbsp; alert message.<o:p></o:p></p>
<p class=3D"MsoNormal">&quot;<o:p></o:p></p>
<p class=3D"MsoNormal"><o:p>&nbsp;</o:p></p>
<p class=3D"MsoNormal">Section 5.10 says:<o:p></o:p></p>
<p class=3D"MsoNormal">&quot;<o:p></o:p></p>
<p class=3D"MsoNormal">EAP-TLS implementations<o:p></o:p></p>
<p class=3D"MsoNormal">&nbsp;&nbsp; SHOULD mitigate known attacks and follo=
w the recommendations in<o:p></o:p></p>
<p class=3D"MsoNormal">&nbsp;&nbsp; [RFC7525] and [I-D.ietf-tls-oldversions=
-deprecate].<o:p></o:p></p>
<p class=3D"MsoNormal">&quot;<o:p></o:p></p>
<p class=3D"MsoNormal"><o:p>&nbsp;</o:p></p>
<p class=3D"MsoNormal">Interestingly, RFC 7525 does not talk about EAP (and=
 instead focuses on applications like&nbsp; HTTP, SMTP, IMAP, POP, SIP, and=
 XMPP, as noted in the abstract). RFC 7525, for example, does not mandate O=
CSP. It also recommends RSA, which draft-ietf-emu-eaptlscert
 and this draft does not do. There seems to be contradiction here. <o:p></o=
:p></p>
<p class=3D"MsoNormal"><o:p>&nbsp;</o:p></p>
<p class=3D"MsoNormal">At a minimum, I would clarify in the introduction wh=
at the updates to RFC 5216 are. This will help those implementers that focu=
s on a variant of EAP-TLS that uses version 1.2. As mentioned above, I don'=
t believe Sections 5.6 and 5.7 belong
 to this document. Leave it in there if someone in the group gets paid by t=
he number of published pages.
<o:p></o:p></p>
<p class=3D"MsoNormal"><o:p>&nbsp;</o:p></p>
<p class=3D"MsoNormal">Ciao<o:p></o:p></p>
<p class=3D"MsoNormal">Hannes<o:p></o:p></p>
</div>
IMPORTANT NOTICE: The contents of this email and any attachments are confid=
ential and may also be privileged. If you are not the intended recipient, p=
lease notify the sender immediately and do not disclose the contents to any=
 other person, use it for any purpose,
 or store or copy the information in any medium. Thank you. <br>
<fieldset class=3D"mimeAttachmentHeader"></fieldset>
<pre class=3D"moz-quote-pre" wrap=3D"">____________________________________=
___________
Emu mailing list
<a class=3D"moz-txt-link-abbreviated" href=3D"mailto:Emu@ietf.org">Emu@ietf=
.org</a>
<a class=3D"moz-txt-link-freetext" href=3D"https://www.ietf.org/mailman/lis=
tinfo/emu">https://www.ietf.org/mailman/listinfo/emu</a>
</pre>
</blockquote>
</body>
</html>

--_000_de5c4134727498eaa6cd78cfb680ba66ericssoncom_--


From nobody Sat Oct 31 15:03:44 2020
Return-Path: <stefan@aaa-sec.com>
X-Original-To: emu@ietfa.amsl.com
Delivered-To: emu@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 319D23A0656 for <emu@ietfa.amsl.com>; Sat, 31 Oct 2020 15:03:40 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.893
X-Spam-Level: 
X-Spam-Status: No, score=-1.893 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, HTML_MESSAGE=0.001, MIME_QP_LONG_LINE=0.001, RCVD_IN_MSPIKE_H4=0.001, RCVD_IN_MSPIKE_WL=0.001, SPF_HELO_NONE=0.001, SPF_NONE=0.001, URIBL_BLOCKED=0.001] autolearn=unavailable autolearn_force=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 ct0GEwc4zyrt for <emu@ietfa.amsl.com>; Sat, 31 Oct 2020 15:03:37 -0700 (PDT)
Received: from smtp.outgoing.loopia.se (smtp.outgoing.loopia.se [93.188.3.37]) (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 383CA3A0880 for <emu@ietf.org>; Sat, 31 Oct 2020 15:03:37 -0700 (PDT)
Received: from s807.loopia.se (localhost [127.0.0.1]) by s807.loopia.se (Postfix) with ESMTP id 5307B10C44BA for <emu@ietf.org>; Sat, 31 Oct 2020 22:56:38 +0100 (CET)
Received: from s630.loopia.se (unknown [172.22.191.6]) by s807.loopia.se (Postfix) with ESMTP id 33DA62EBADFB; Sat, 31 Oct 2020 22:56:38 +0100 (CET)
Received: from s474.loopia.se (unknown [172.22.191.6]) by s630.loopia.se (Postfix) with ESMTP id 1D27C13B92DF; Sat, 31 Oct 2020 22:56:38 +0100 (CET)
X-Virus-Scanned: amavisd-new at amavis.loopia.se
Received: from s498.loopia.se ([172.22.191.6]) by s474.loopia.se (s474.loopia.se [172.22.190.14]) (amavisd-new, port 10024) with LMTP id Ho9_QOiu1V0C; Sat, 31 Oct 2020 22:56:37 +0100 (CET)
X-Loopia-Auth: user
X-Loopia-User: mailstore2@aaa-sec.com
X-Loopia-Originating-IP: 90.229.17.25
Received: from [10.0.1.104] (unknown [90.229.17.25]) (Authenticated sender: mailstore2@aaa-sec.com) by s498.loopia.se (Postfix) with ESMTPSA id C6D3A473233; Sat, 31 Oct 2020 22:56:33 +0100 (CET)
User-Agent: Microsoft-MacOutlook/16.42.20101102
Date: Sat, 31 Oct 2020 22:56:24 +0100
From: Stefan Santesson <stefan@aaa-sec.com>
To: Mohit Sethi M <mohit.m.sethi@ericsson.com>, Benjamin Kaduk <kaduk@mit.edu>
CC: "last-call@ietf.org" <last-call@ietf.org>, "draft-ietf-emu-eaptlscert.all@ietf.org" <draft-ietf-emu-eaptlscert.all@ietf.org>, "emu@ietf.org" <emu@ietf.org>, "secdir@ietf.org" <secdir@ietf.org>
Message-ID: <E6F03204-2DD6-45A2-8C6E-02F41AEE5319@aaa-sec.com>
Thread-Topic: [Emu] Secdir last call review of draft-ietf-emu-eaptlscert-06
References: <160401318284.11167.6795105917637378641@ietfa.amsl.com> <20201030030415.GE39170@kduck.mit.edu> <12167567-9dc5-6161-abef-826b0a8b6602@ericsson.com> <2F8F716A-C063-4DF4-8384-BBD59C636C8A@aaa-sec.com> <36dd411f-853c-f7fb-957a-c6eb90be130b@ericsson.com>
In-Reply-To: <36dd411f-853c-f7fb-957a-c6eb90be130b@ericsson.com>
Mime-version: 1.0
Content-type: multipart/alternative; boundary="B_3687029795_1029242773"
Archived-At: <https://mailarchive.ietf.org/arch/msg/emu/0ixA_k2Nzn4vtTsE7umjmt4ReNA>
Subject: Re: [Emu] Secdir last call review of draft-ietf-emu-eaptlscert-06
X-BeenThere: emu@ietf.org
X-Mailman-Version: 2.1.29
Precedence: list
List-Id: "EAP Methods Update \(EMU\)" <emu.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/emu>, <mailto:emu-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/emu/>
List-Post: <mailto:emu@ietf.org>
List-Help: <mailto:emu-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/emu>, <mailto:emu-request@ietf.org?subject=subscribe>
X-List-Received-Date: Sat, 31 Oct 2020 22:03:40 -0000

> This message is in MIME format. Since your mail reader does not understand
this format, some or all of this message may not be legible.

--B_3687029795_1029242773
Content-type: text/plain;
	charset="UTF-8"
Content-transfer-encoding: quoted-printable

I think that is great!

=20

Stefan Santesson=20

=20

From: Mohit Sethi M <mohit.m.sethi@ericsson.com>
Date: Saturday, 31 October 2020 at 15:19
To: Stefan Santesson <stefan@aaa-sec.com>, Mohit Sethi M <mohit.m.sethi@eri=
csson.com>, Benjamin Kaduk <kaduk@mit.edu>
Cc: "last-call@ietf.org" <last-call@ietf.org>, "draft-ietf-emu-eaptlscert.a=
ll@ietf.org" <draft-ietf-emu-eaptlscert.all@ietf.org>, "emu@ietf.org" <emu@i=
etf.org>, "secdir@ietf.org" <secdir@ietf.org>
Subject: Re: [Emu] Secdir last call review of draft-ietf-emu-eaptlscert-06

=20

Hi Stefan,

I made a minor update to reflect your feedback (https://github.com/emu-wg/e=
aptls-longcert/compare/3ac0a18..2093026):

Thus, the AIA extension can reduce the size of the certificate chain by onl=
y including a pointer to the issuer certificate instead of including the ent=
ire issuer certificate. However, it requires the side receiving the certific=
ate containing the extension to have network connectivity (unless the inform=
ation is already cached locally). Naturally, such indirection cannot be used=
 for the server certificate (since EAP peers in most deployments do not have=
 network connectivity before authentication and typically do not maintain an=
 up-to-date local cache of issuer certificates).

Hope this is correct (and sufficient).=20

--Mohit

On 10/30/20 4:40 PM, Stefan Santesson wrote:
Hi,
=20
I think the text is great.=20
However I'm not entirely convinced that AIA requires network connectivity a=
t all times.
The AIA CA cert url is static and works fine as identifier for a locally ca=
ched cert
The fact that it is the correct cert is assured by the path validation proc=
ess.
As such, the AIA works fine with a http cache implementation or similar or =
any other solution using locally stored data.
If used in a local corporate context, a cache mechanism could be provided w=
ith pre-loaded relevant certs.
=20
But I don=E2=80=99t know how this may or may not interoperate with deployed base =
of EAP implementations.
=20
Stefan Santesson=20
=20
=EF=BB=BFOn 2020-10-30, 14:48, "Mohit Sethi M" <mohit.m.sethi@ericsson.com> wrote=
:
=20
=C2=A0=C2=A0=C2=A0 Hi Stefan,
=20
=C2=A0=C2=A0=C2=A0 Thank you for the review. I have updated the draft in github=20
=C2=A0=C2=A0=C2=A0=C2=A0(https://github.com/emu-wg/eaptls-longcert). Here is the diff for y=
our=20
=C2=A0=C2=A0=C2=A0=C2=A0convenience:=20
=C2=A0=C2=A0=C2=A0=C2=A0https://tools.ietf.org/rfcdiff?url1=3Dhttps://tools.ietf.org/id/draft=
-ietf-emu-eaptlscert.txt&url2=3Dhttps://emu-wg.github.io/eaptls-longcert/draft=
-ietf-emu-eaptlscert.txt.
=20
=C2=A0=C2=A0=C2=A0 The following text was added:
=20
=C2=A0=C2=A0=C2=A0 >=C2=A0=C2=A0=C2=A0 The size of certificates (and certificate chains) may also i=
ncrease
=C2=A0=C2=A0=C2=A0 >=C2=A0=C2=A0=C2=A0 manifold in the future with the introduction of quantum-safe
=C2=A0=C2=A0=C2=A0 >=C2=A0=C2=A0=C2=A0 cryptography.=C2=A0 For example, lattice-based cryptography woul=
d have
=C2=A0=C2=A0=C2=A0 >=C2=A0=C2=A0=C2=A0 public keys of approximately 1000 bytes and signatures of
=C2=A0=C2=A0=C2=A0 >=C2=A0=C2=A0=C2=A0 approximately 2000 bytes.
=C2=A0=C2=A0=C2=A0 and in Section 4.2.5
=20
=C2=A0=C2=A0=C2=A0 >=C2=A0=C2=A0=C2=A0 The Authority Information Access (AIA) extension specified i=
n
=C2=A0=C2=A0=C2=A0 >=C2=A0=C2=A0=C2=A0 [RFC5280] can be used with end-entity and CA certificates to=
 access
=C2=A0=C2=A0=C2=A0 >=C2=A0=C2=A0=C2=A0 information about the issuer of the certificate in which the
=C2=A0=C2=A0=C2=A0 >=C2=A0=C2=A0=C2=A0 extension appears.=C2=A0 For example, it can be used to provide =
the
=C2=A0=C2=A0=C2=A0 >=C2=A0=C2=A0=C2=A0 address of the OCSP responder from where revocation status o=
f the
=C2=A0=C2=A0=C2=A0 >=C2=A0=C2=A0=C2=A0 certificate (in which the extension appears) can be checked.=
 It can
=C2=A0=C2=A0=C2=A0 >=C2=A0=C2=A0=C2=A0 also be used to obtain the issuer certificate.=C2=A0 Thus, the A=
IA
=C2=A0=C2=A0=C2=A0 >=C2=A0=C2=A0=C2=A0 extension can reduce the size of the certificate chain by on=
ly
=C2=A0=C2=A0=C2=A0 >=C2=A0=C2=A0=C2=A0 including a pointer to the issuer certificate instead of inc=
luding
=C2=A0=C2=A0=C2=A0 >=C2=A0=C2=A0=C2=A0 the entire issuer certificate.=C2=A0 However, it requires the si=
de
=C2=A0=C2=A0=C2=A0 >=C2=A0=C2=A0=C2=A0 receiving the certificate containing the extension to have n=
etwork
=C2=A0=C2=A0=C2=A0 >=C2=A0=C2=A0=C2=A0 connectivity.=C2=A0 Naturally, such indirection cannot be used f=
or the
=C2=A0=C2=A0=C2=A0 >=C2=A0=C2=A0=C2=A0 server certificate (since the EAP peer in most deployments d=
oes not
=C2=A0=C2=A0=C2=A0 >=C2=A0=C2=A0=C2=A0 have network connectivity before authen
=20
=C2=A0=C2=A0=C2=A0 Let me know what you think. I am not an expert on quantum cryptograp=
hy=20
=C2=A0=C2=A0=C2=A0=C2=A0or on the AIA extension. I will wait for all the comments to come i=
n=20
=C2=A0=C2=A0=C2=A0=C2=A0before submitting a new version.
=20
=C2=A0=C2=A0=C2=A0 --Mohit
=20
=C2=A0=C2=A0=C2=A0 On 10/30/20 5:04 AM, Benjamin Kaduk wrote:
=C2=A0=C2=A0=C2=A0 > Hi Stefan,
=C2=A0=C2=A0=C2=A0 >
=C2=A0=C2=A0=C2=A0 > Thanks for the review; it raises some good topics.
=C2=A0=C2=A0=C2=A0 > Replying on a couple points...
=C2=A0=C2=A0=C2=A0 >
=C2=A0=C2=A0=C2=A0 > On Thu, Oct 29, 2020 at 04:13:02PM -0700, Stefan Santesson via Dat=
atracker wrote:
=C2=A0=C2=A0=C2=A0 >> Reviewer: Stefan Santesson
=C2=A0=C2=A0=C2=A0 >> Review result: Has Nits
=C2=A0=C2=A0=C2=A0 >>
=C2=A0=C2=A0=C2=A0 >> The document in general is good and well written.
=C2=A0=C2=A0=C2=A0 >>
=C2=A0=C2=A0=C2=A0 >> Some nits needs attention before publication as the general revie=
w also points
=C2=A0=C2=A0=C2=A0 >> out. Ex in the abstract "This document looks at the this problem"
=C2=A0=C2=A0=C2=A0 >>
=C2=A0=C2=A0=C2=A0 >> Some abbreviations needs to be spelled out at first usage, such a=
s MTU (Maximum
=C2=A0=C2=A0=C2=A0 >> Transmission Unit)
=C2=A0=C2=A0=C2=A0 > MTU may actually be okay; per
=C2=A0=C2=A0=C2=A0 > https://www.rfc-editor.org/materials/abbrev.expansion.txt it is ma=
rked as
=C2=A0=C2=A0=C2=A0 > "well-known" and does not always need to be expanded.
=C2=A0=C2=A0=C2=A0 >
=C2=A0=C2=A0=C2=A0 >> On the content itself I have two questions:
=C2=A0=C2=A0=C2=A0 >>
=C2=A0=C2=A0=C2=A0 >> - Wouldn't it be relevant to also discuss the risks with regard t=
o introduction
=C2=A0=C2=A0=C2=A0 >> of quantum safe crypto, if that leads to significantly increased =
key sizes? It
=C2=A0=C2=A0=C2=A0 >> could be troublesome if transition to a safer crypto is made impo=
ssible due to
=C2=A0=C2=A0=C2=A0 >> size limitations. - Would it be relevant to discuss usage of AIA =
extension as
=C2=A0=C2=A0=C2=A0 >> means of possibly excluding intermediary certs from the path as t=
hey could be
=C2=A0=C2=A0=C2=A0 >> located using AIA?
=C2=A0=C2=A0=C2=A0 >>
=C2=A0=C2=A0=C2=A0 >> Finally, I agree with the general review that this document refer=
ence quite
=C2=A0=C2=A0=C2=A0 >> some work in progress. If this document is to be published before=
 these
=C2=A0=C2=A0=C2=A0 >> referenced works are concluded, are there alternatives to make th=
e same point?
=C2=A0=C2=A0=C2=A0 > They seem to mostly be informative references, and so would not re=
quire us
=C2=A0=C2=A0=C2=A0 > to hold publication of this document.=C2=A0 It is probably still worth
=C2=A0=C2=A0=C2=A0 > considering if there are alternatives anyway, though.
=C2=A0=C2=A0=C2=A0 >
=C2=A0=C2=A0=C2=A0 > -Ben
=C2=A0=C2=A0=C2=A0 >
=C2=A0=C2=A0=C2=A0 > _______________________________________________
=C2=A0=C2=A0=C2=A0 > Emu mailing list
=C2=A0=C2=A0=C2=A0 > Emu@ietf.org
=C2=A0=C2=A0=C2=A0 > https://www.ietf.org/mailman/listinfo/emu
=20
=20


--B_3687029795_1029242773
Content-type: text/html;
	charset="UTF-8"
Content-transfer-encoding: quoted-printable

<html xmlns:o=3D"urn:schemas-microsoft-com:office:office" xmlns:w=3D"urn:schema=
s-microsoft-com:office:word" xmlns:m=3D"http://schemas.microsoft.com/office/20=
04/12/omml" xmlns=3D"http://www.w3.org/TR/REC-html40"><head><meta http-equiv=3DC=
ontent-Type content=3D"text/html; charset=3Dutf-8"><meta name=3DGenerator content=3D=
"Microsoft Word 15 (filtered medium)"><style><!--
/* Font Definitions */
@font-face
	{font-family:"Cambria Math";
	panose-1:2 4 5 3 5 4 6 3 2 4;}
@font-face
	{font-family:Calibri;
	panose-1:2 15 5 2 2 2 4 3 2 4;}
@font-face
	{font-family:Consolas;
	panose-1:2 11 6 9 2 2 4 3 2 4;}
/* Style Definitions */
p.MsoNormal, li.MsoNormal, div.MsoNormal
	{margin:0cm;
	font-size:11.0pt;
	font-family:"Calibri",sans-serif;}
a:link, span.MsoHyperlink
	{mso-style-priority:99;
	color:blue;
	text-decoration:underline;}
pre
	{mso-style-priority:99;
	mso-style-link:"HTML Preformatted Char";
	margin:0cm;
	font-size:10.0pt;
	font-family:"Courier New";}
span.blob-code-inner
	{mso-style-name:blob-code-inner;}
span.HTMLPreformattedChar
	{mso-style-name:"HTML Preformatted Char";
	mso-style-priority:99;
	mso-style-link:"HTML Preformatted";
	font-family:Consolas;}
span.EmailStyle22
	{mso-style-type:personal-reply;
	font-family:"Calibri",sans-serif;
	color:windowtext;}
.MsoChpDefault
	{mso-style-type:export-only;
	font-size:10.0pt;}
@page WordSection1
	{size:612.0pt 792.0pt;
	margin:72.0pt 72.0pt 72.0pt 72.0pt;}
div.WordSection1
	{page:WordSection1;}
--></style></head><body lang=3Den-SE link=3Dblue vlink=3Dpurple style=3D'word-wrap:=
break-word'><div class=3DWordSection1><p class=3DMsoNormal><span lang=3DEN-US styl=
e=3D'mso-fareast-language:EN-US'>I think that is great!<o:p></o:p></span></p><=
p class=3DMsoNormal><span style=3D'mso-fareast-language:EN-US'><o:p>&nbsp;</o:p>=
</span></p><p class=3DMsoNormal><span lang=3DEN-US style=3D'color:black;mso-fareas=
t-language:EN-US'>Stefan Santesson </span><span style=3D'mso-fareast-language:=
EN-US'><o:p></o:p></span></p><p class=3DMsoNormal><span style=3D'mso-fareast-lan=
guage:EN-US'><o:p>&nbsp;</o:p></span></p><div style=3D'border:none;border-top:=
solid #B5C4DF 1.0pt;padding:3.0pt 0cm 0cm 0cm'><p class=3DMsoNormal><b><span s=
tyle=3D'font-size:12.0pt;color:black'>From: </span></b><span style=3D'font-size:=
12.0pt;color:black'>Mohit Sethi M &lt;mohit.m.sethi@ericsson.com&gt;<br><b>D=
ate: </b>Saturday, 31 October 2020 at 15:19<br><b>To: </b>Stefan Santesson &=
lt;stefan@aaa-sec.com&gt;, Mohit Sethi M &lt;mohit.m.sethi@ericsson.com&gt;,=
 Benjamin Kaduk &lt;kaduk@mit.edu&gt;<br><b>Cc: </b>&quot;last-call@ietf.org=
&quot; &lt;last-call@ietf.org&gt;, &quot;draft-ietf-emu-eaptlscert.all@ietf.=
org&quot; &lt;draft-ietf-emu-eaptlscert.all@ietf.org&gt;, &quot;emu@ietf.org=
&quot; &lt;emu@ietf.org&gt;, &quot;secdir@ietf.org&quot; &lt;secdir@ietf.org=
&gt;<br><b>Subject: </b>Re: [Emu] Secdir last call review of draft-ietf-emu-=
eaptlscert-06<o:p></o:p></span></p></div><div><p class=3DMsoNormal><o:p>&nbsp;=
</o:p></p></div><p>Hi Stefan,<o:p></o:p></p><p>I made a minor update to refl=
ect your feedback (<a href=3D"https://github.com/emu-wg/eaptls-longcert/compar=
e/3ac0a18..2093026">https://github.com/emu-wg/eaptls-longcert/compare/3ac0a1=
8..2093026</a>):<o:p></o:p></p><blockquote style=3D'margin-top:5.0pt;margin-bo=
ttom:5.0pt'><p class=3DMsoNormal><span class=3Dblob-code-inner>Thus, the AIA ext=
ension can reduce the size of the certificate chain by only including a poin=
ter to the issuer certificate instead of including the entire issuer certifi=
cate. However, it requires the side receiving the certificate containing the=
 extension to have network connectivity (unless the information is already c=
ached locally). Naturally, such indirection cannot be used for the server ce=
rtificate (since EAP peers in most deployments do not have network connectiv=
ity before authentication and typically do not maintain an up-to-date local =
cache of issuer certificates).</span><o:p></o:p></p></blockquote><p>Hope thi=
s is correct (and sufficient). <o:p></o:p></p><p>--Mohit<o:p></o:p></p><div>=
<p class=3DMsoNormal>On 10/30/20 4:40 PM, Stefan Santesson wrote:<o:p></o:p></=
p></div><blockquote style=3D'margin-top:5.0pt;margin-bottom:5.0pt'><pre>Hi,<o:=
p></o:p></pre><pre><o:p>&nbsp;</o:p></pre><pre>I think the text is great. <o=
:p></o:p></pre><pre>However I'm not entirely convinced that AIA requires net=
work connectivity at all times.<o:p></o:p></pre><pre>The AIA CA cert url is =
static and works fine as identifier for a locally cached cert<o:p></o:p></pr=
e><pre>The fact that it is the correct cert is assured by the path validatio=
n process.<o:p></o:p></pre><pre>As such, the AIA works fine with a http cach=
e implementation or similar or any other solution using locally stored data.=
<o:p></o:p></pre><pre>If used in a local corporate context, a cache mechanis=
m could be provided with pre-loaded relevant certs.<o:p></o:p></pre><pre><o:=
p>&nbsp;</o:p></pre><pre>But I don=E2=80=99t know how this may or may not interope=
rate with deployed base of EAP implementations.<o:p></o:p></pre><pre><o:p>&n=
bsp;</o:p></pre><pre>Stefan Santesson <o:p></o:p></pre><pre><o:p>&nbsp;</o:p=
></pre><pre>=EF=BB=BFOn 2020-10-30, 14:48, &quot;Mohit Sethi M&quot; <a href=3D"mail=
to:mohit.m.sethi@ericsson.com">&lt;mohit.m.sethi@ericsson.com&gt;</a> wrote:=
<o:p></o:p></pre><pre><o:p>&nbsp;</o:p></pre><pre>=C2=A0=C2=A0=C2=A0 Hi Stefan,<o:p></o:=
p></pre><pre><o:p>&nbsp;</o:p></pre><pre>=C2=A0=C2=A0=C2=A0 Thank you for the review. I =
have updated the draft in github <o:p></o:p></pre><pre>=C2=A0=C2=A0=C2=A0=C2=A0(<a href=3D"htt=
ps://github.com/emu-wg/eaptls-longcert">https://github.com/emu-wg/eaptls-lon=
gcert</a>). Here is the diff for your <o:p></o:p></pre><pre>=C2=A0=C2=A0=C2=A0=C2=A0convenie=
nce: <o:p></o:p></pre><pre>=C2=A0=C2=A0=C2=A0=C2=A0<a href=3D"https://tools.ietf.org/rfcdiff?u=
rl1=3Dhttps://tools.ietf.org/id/draft-ietf-emu-eaptlscert.txt&amp;url2=3Dhttps:/=
/emu-wg.github.io/eaptls-longcert/draft-ietf-emu-eaptlscert.txt">https://too=
ls.ietf.org/rfcdiff?url1=3Dhttps://tools.ietf.org/id/draft-ietf-emu-eaptlscert=
.txt&amp;url2=3Dhttps://emu-wg.github.io/eaptls-longcert/draft-ietf-emu-eaptls=
cert.txt</a>.<o:p></o:p></pre><pre><o:p>&nbsp;</o:p></pre><pre>=C2=A0=C2=A0=C2=A0 The fo=
llowing text was added:<o:p></o:p></pre><pre><o:p>&nbsp;</o:p></pre><pre>=C2=A0=C2=
=A0=C2=A0 &gt;=C2=A0=C2=A0=C2=A0 The size of certificates (and certificate chains) may also in=
crease<o:p></o:p></pre><pre>=C2=A0=C2=A0=C2=A0 &gt;=C2=A0=C2=A0=C2=A0 manifold in the future with th=
e introduction of quantum-safe<o:p></o:p></pre><pre>=C2=A0=C2=A0=C2=A0 &gt;=C2=A0=C2=A0=C2=A0 crypto=
graphy.=C2=A0 For example, lattice-based cryptography would have<o:p></o:p></pre=
><pre>=C2=A0=C2=A0=C2=A0 &gt;=C2=A0=C2=A0=C2=A0 public keys of approximately 1000 bytes and signatur=
es of<o:p></o:p></pre><pre>=C2=A0=C2=A0=C2=A0 &gt;=C2=A0=C2=A0=C2=A0 approximately 2000 bytes.<o:p><=
/o:p></pre><pre>=C2=A0=C2=A0=C2=A0 and in Section 4.2.5<o:p></o:p></pre><pre><o:p>&nbsp;=
</o:p></pre><pre>=C2=A0=C2=A0=C2=A0 &gt;=C2=A0=C2=A0=C2=A0 The Authority Information Access (AIA) ex=
tension specified in<o:p></o:p></pre><pre>=C2=A0=C2=A0=C2=A0 &gt;=C2=A0=C2=A0=C2=A0 [RFC5280] can be=
 used with end-entity and CA certificates to access<o:p></o:p></pre><pre>=C2=A0=C2=
=A0=C2=A0 &gt;=C2=A0=C2=A0=C2=A0 information about the issuer of the certificate in which the<=
o:p></o:p></pre><pre>=C2=A0=C2=A0=C2=A0 &gt;=C2=A0=C2=A0=C2=A0 extension appears.=C2=A0 For example, it =
can be used to provide the<o:p></o:p></pre><pre>=C2=A0=C2=A0=C2=A0 &gt;=C2=A0=C2=A0=C2=A0 address of=
 the OCSP responder from where revocation status of the<o:p></o:p></pre><pre=
>=C2=A0=C2=A0=C2=A0 &gt;=C2=A0=C2=A0=C2=A0 certificate (in which the extension appears) can be check=
ed. It can<o:p></o:p></pre><pre>=C2=A0=C2=A0=C2=A0 &gt;=C2=A0=C2=A0=C2=A0 also be used to obtain the=
 issuer certificate.=C2=A0 Thus, the AIA<o:p></o:p></pre><pre>=C2=A0=C2=A0=C2=A0 &gt;=C2=A0=C2=A0=C2=A0 =
extension can reduce the size of the certificate chain by only<o:p></o:p></p=
re><pre>=C2=A0=C2=A0=C2=A0 &gt;=C2=A0=C2=A0=C2=A0 including a pointer to the issuer certificate inst=
ead of including<o:p></o:p></pre><pre>=C2=A0=C2=A0=C2=A0 &gt;=C2=A0=C2=A0=C2=A0 the entire issuer ce=
rtificate.=C2=A0 However, it requires the side<o:p></o:p></pre><pre>=C2=A0=C2=A0=C2=A0 &gt;=C2=
=A0=C2=A0=C2=A0 receiving the certificate containing the extension to have network<o:p=
></o:p></pre><pre>=C2=A0=C2=A0=C2=A0 &gt;=C2=A0=C2=A0=C2=A0 connectivity.=C2=A0 Naturally, such indirect=
ion cannot be used for the<o:p></o:p></pre><pre>=C2=A0=C2=A0=C2=A0 &gt;=C2=A0=C2=A0=C2=A0 server cer=
tificate (since the EAP peer in most deployments does not<o:p></o:p></pre><p=
re>=C2=A0=C2=A0=C2=A0 &gt;=C2=A0=C2=A0=C2=A0 have network connectivity before authen<o:p></o:p></pre=
><pre><o:p>&nbsp;</o:p></pre><pre>=C2=A0=C2=A0=C2=A0 Let me know what you think. I am no=
t an expert on quantum cryptography <o:p></o:p></pre><pre>=C2=A0=C2=A0=C2=A0=C2=A0or on the =
AIA extension. I will wait for all the comments to come in <o:p></o:p></pre>=
<pre>=C2=A0=C2=A0=C2=A0=C2=A0before submitting a new version.<o:p></o:p></pre><pre><o:p>&nbs=
p;</o:p></pre><pre>=C2=A0=C2=A0=C2=A0 --Mohit<o:p></o:p></pre><pre><o:p>&nbsp;</o:p></pr=
e><pre>=C2=A0=C2=A0=C2=A0 On 10/30/20 5:04 AM, Benjamin Kaduk wrote:<o:p></o:p></pre><pr=
e>=C2=A0=C2=A0=C2=A0 &gt; Hi Stefan,<o:p></o:p></pre><pre>=C2=A0=C2=A0=C2=A0 &gt;<o:p></o:p></pre><p=
re>=C2=A0=C2=A0=C2=A0 &gt; Thanks for the review; it raises some good topics.<o:p></o:p>=
</pre><pre>=C2=A0=C2=A0=C2=A0 &gt; Replying on a couple points...<o:p></o:p></pre><pre>=C2=
=A0=C2=A0=C2=A0 &gt;<o:p></o:p></pre><pre>=C2=A0=C2=A0=C2=A0 &gt; On Thu, Oct 29, 2020 at 04:13:02=
PM -0700, Stefan Santesson via Datatracker wrote:<o:p></o:p></pre><pre>=C2=A0=C2=A0=C2=
=A0 &gt;&gt; Reviewer: Stefan Santesson<o:p></o:p></pre><pre>=C2=A0=C2=A0=C2=A0 &gt;&gt; R=
eview result: Has Nits<o:p></o:p></pre><pre>=C2=A0=C2=A0=C2=A0 &gt;&gt;<o:p></o:p></pre>=
<pre>=C2=A0=C2=A0=C2=A0 &gt;&gt; The document in general is good and well written.<o:p><=
/o:p></pre><pre>=C2=A0=C2=A0=C2=A0 &gt;&gt;<o:p></o:p></pre><pre>=C2=A0=C2=A0=C2=A0 &gt;&gt; Some ni=
ts needs attention before publication as the general review also points<o:p>=
</o:p></pre><pre>=C2=A0=C2=A0=C2=A0 &gt;&gt; out. Ex in the abstract &quot;This document=
 looks at the this problem&quot;<o:p></o:p></pre><pre>=C2=A0=C2=A0=C2=A0 &gt;&gt;<o:p></=
o:p></pre><pre>=C2=A0=C2=A0=C2=A0 &gt;&gt; Some abbreviations needs to be spelled out at=
 first usage, such as MTU (Maximum<o:p></o:p></pre><pre>=C2=A0=C2=A0=C2=A0 &gt;&gt; Tran=
smission Unit)<o:p></o:p></pre><pre>=C2=A0=C2=A0=C2=A0 &gt; MTU may actually be okay; pe=
r<o:p></o:p></pre><pre>=C2=A0=C2=A0=C2=A0 &gt; <a href=3D"https://www.rfc-editor.org/mater=
ials/abbrev.expansion.txt">https://www.rfc-editor.org/materials/abbrev.expan=
sion.txt</a> it is marked as<o:p></o:p></pre><pre>=C2=A0=C2=A0=C2=A0 &gt; &quot;well-kno=
wn&quot; and does not always need to be expanded.<o:p></o:p></pre><pre>=C2=A0=C2=A0=C2=
=A0 &gt;<o:p></o:p></pre><pre>=C2=A0=C2=A0=C2=A0 &gt;&gt; On the content itself I have two=
 questions:<o:p></o:p></pre><pre>=C2=A0=C2=A0=C2=A0 &gt;&gt;<o:p></o:p></pre><pre>=C2=A0=C2=A0=C2=A0=
 &gt;&gt; - Wouldn't it be relevant to also discuss the risks with regard to=
 introduction<o:p></o:p></pre><pre>=C2=A0=C2=A0=C2=A0 &gt;&gt; of quantum safe crypto, i=
f that leads to significantly increased key sizes? It<o:p></o:p></pre><pre>=C2=
=A0=C2=A0=C2=A0 &gt;&gt; could be troublesome if transition to a safer crypto is made =
impossible due to<o:p></o:p></pre><pre>=C2=A0=C2=A0=C2=A0 &gt;&gt; size limitations. - W=
ould it be relevant to discuss usage of AIA extension as<o:p></o:p></pre><pr=
e>=C2=A0=C2=A0=C2=A0 &gt;&gt; means of possibly excluding intermediary certs from the pa=
th as they could be<o:p></o:p></pre><pre>=C2=A0=C2=A0=C2=A0 &gt;&gt; located using AIA?<=
o:p></o:p></pre><pre>=C2=A0=C2=A0=C2=A0 &gt;&gt;<o:p></o:p></pre><pre>=C2=A0=C2=A0=C2=A0 &gt;&gt; Fi=
nally, I agree with the general review that this document reference quite<o:=
p></o:p></pre><pre>=C2=A0=C2=A0=C2=A0 &gt;&gt; some work in progress. If this document i=
s to be published before these<o:p></o:p></pre><pre>=C2=A0=C2=A0=C2=A0 &gt;&gt; referenc=
ed works are concluded, are there alternatives to make the same point?<o:p><=
/o:p></pre><pre>=C2=A0=C2=A0=C2=A0 &gt; They seem to mostly be informative references, a=
nd so would not require us<o:p></o:p></pre><pre>=C2=A0=C2=A0=C2=A0 &gt; to hold publicat=
ion of this document.=C2=A0 It is probably still worth<o:p></o:p></pre><pre>=C2=A0=C2=A0=
=C2=A0 &gt; considering if there are alternatives anyway, though.<o:p></o:p></pr=
e><pre>=C2=A0=C2=A0=C2=A0 &gt;<o:p></o:p></pre><pre>=C2=A0=C2=A0=C2=A0 &gt; -Ben<o:p></o:p></pre><pr=
e>=C2=A0=C2=A0=C2=A0 &gt;<o:p></o:p></pre><pre>=C2=A0=C2=A0=C2=A0 &gt; _____________________________=
__________________<o:p></o:p></pre><pre>=C2=A0=C2=A0=C2=A0 &gt; Emu mailing list<o:p></o=
:p></pre><pre>=C2=A0=C2=A0=C2=A0 &gt; <a href=3D"mailto:Emu@ietf.org">Emu@ietf.org</a><o:p=
></o:p></pre><pre>=C2=A0=C2=A0=C2=A0 &gt; <a href=3D"https://www.ietf.org/mailman/listinfo=
/emu">https://www.ietf.org/mailman/listinfo/emu</a><o:p></o:p></pre><pre><o:=
p>&nbsp;</o:p></pre><pre><o:p>&nbsp;</o:p></pre></blockquote></div></body></=
html>

--B_3687029795_1029242773--


