Re: [Id-event] Robert Wilton's No Objection on draft-ietf-secevent-http-push-12: (with COMMENT)
Mike Jones <Michael.Jones@microsoft.com> Thu, 25 June 2020 05:26 UTC
Return-Path: <Michael.Jones@microsoft.com>
X-Original-To: id-event@ietfa.amsl.com
Delivered-To: id-event@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 468923A0121; Wed, 24 Jun 2020 22:26:26 -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, 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 7viSyqW7MxMj; Wed, 24 Jun 2020 22:26:24 -0700 (PDT)
Received: from NAM06-DM3-obe.outbound.protection.outlook.com (mail-eopbgr640099.outbound.protection.outlook.com [40.107.64.99]) (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 733AE3A00D3; Wed, 24 Jun 2020 22:26:24 -0700 (PDT)
ARC-Seal: i=1; a=rsa-sha256; s=arcselector9901; d=microsoft.com; cv=none; b=lD7fP5Vg1M/p+gYMoWmHkg79pMk2o40Ons50Cbgp3nM0uI6UIejgd9TEtL+rhTo3zud9useLmSmaB8uoEQMUckJE/y7XXjg75OJBtDEZmhezuMcMHEPtvPawkpG1NBuMpbi85HH5zoN7IVfln4+c+eQhaWpUpewpCFehEGFgkwmzEt8YXCLLdudTwI7m7+w84j4JA1VzDOOomyzAoxON5TAkL9Wkyaem/9dLlBFRGluIIia3R59k3E5c6YLXl4Aszub3Z9qW0cSr5UtBHMst0iloll1PoCm/ZY8wXLW5cEddAajDn3Xu0ijYJKFJaLourQ4+oT/Y2U08czEwikS6OQ==
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=TGXhtWmDvTBsZ2iLsOvYhDtlcUqnlT3VA0wxE5O/QAs=; b=NWv0cBD/ri5dn6DSGvIAPQ8gvh4Y/jEA/WiaB90d4zu7UicVzZIRIM6Ab1WQS93B7cM64aA9bVpBW1Z4SnpLoHij56ji5hSAKxcwuvij25QCKafBV922PacmjTjKTohLwODiSTHimdB13TEPnABd5fyZ+qGU6x1MmctgxExuzZCPd4gt0ufP6I0iuRgcKat9Nu+E9sijHaxCmLLVr3jRlRaI2zwXIEaQGV9BPqoZbHzZpQSHfnGRC+tsRE2BsC75g8H7j5l8uI7zyRYsbHCEAzPnKqCATdVJYB9Hi+buJZQHmZalCY1Vgzdkc5KqgnTtDSVbdP6QTlRv+4naxIgnVQ==
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=TGXhtWmDvTBsZ2iLsOvYhDtlcUqnlT3VA0wxE5O/QAs=; b=PQV18w2Q+Dt7di7qF7mW8GSxnMU6NPNajk3bobjgvF7VU0eQwQuLOis2qYfJwZ5ri4Ws4iHzRXm6NiPdewT2UGjBGvC63VTTCEmyIR50w9Kcv/y88aUbnhtDic3Eyc5EpbQWyOuWiov328Quh089oClgjgngDKrX6gqv5CikYLk=
Received: from CH2PR00MB0678.namprd00.prod.outlook.com (2603:10b6:610:a9::23) by CH2PR00MB0825.namprd00.prod.outlook.com (2603:10b6:610:6f::24) with Microsoft SMTP Server (version=TLS1_2, cipher=TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384) id 15.20.3173.0; Thu, 25 Jun 2020 05:26:19 +0000
Received: from CH2PR00MB0678.namprd00.prod.outlook.com ([fe80::3c44:1c81:e278:edb0]) by CH2PR00MB0678.namprd00.prod.outlook.com ([fe80::3c44:1c81:e278:edb0%2]) with mapi id 15.20.3173.000; Thu, 25 Jun 2020 05:26:19 +0000
From: Mike Jones <Michael.Jones@microsoft.com>
To: Robert Wilton <rwilton@cisco.com>, The IESG <iesg@ietf.org>
CC: "draft-ietf-secevent-http-push@ietf.org" <draft-ietf-secevent-http-push@ietf.org>, "secevent-chairs@ietf.org" <secevent-chairs@ietf.org>, "id-event@ietf.org" <id-event@ietf.org>, Yaron Sheffer <yaronf.ietf@gmail.com>
Thread-Topic: Robert Wilton's No Objection on draft-ietf-secevent-http-push-12: (with COMMENT)
Thread-Index: AdZKsSav5iS1w/bFS129uqOLT+TQsA==
Date: Thu, 25 Jun 2020 05:26:19 +0000
Message-ID: <CH2PR00MB067827D31EE2E02DACE03D13F5920@CH2PR00MB0678.namprd00.prod.outlook.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=10b3b027-0c82-4b39-b019-69119d789500; 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-06-25T05:10:26Z; MSIP_Label_f42aa342-8706-4288-bd11-ebb85995028c_SiteId=72f988bf-86f1-41af-91ab-2d7cd011db47;
authentication-results: cisco.com; dkim=none (message not signed) header.d=none;cisco.com; dmarc=none action=none header.from=microsoft.com;
x-originating-ip: [50.47.87.252]
x-ms-publictraffictype: Email
x-ms-office365-filtering-ht: Tenant
x-ms-office365-filtering-correlation-id: d50ba012-5bd2-4b72-dfa5-08d818c84a61
x-ms-traffictypediagnostic: CH2PR00MB0825:
x-microsoft-antispam-prvs: <CH2PR00MB08254BB84FA7E3D2574BB2CAF5920@CH2PR00MB0825.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: BL/5JWeL4nzU5f7CZzePDiF2GVG8a7YTOZHU1XXJi1BcTwhcNLmc8DS/KU21bvxw20C3qxEDIjBi//ooBhv7vmXmKny3oLg1duoJaBgnfCoipd2TLl7ZX8hz82g1gl75gS5mrFfM7CGrPahVzYCwWi9PNgViIg6zVVvpOxXhIlyLfSiSiQY9fYUVeDmBWfgX1aUy9XdR/dvPDjynnnWspASH9iAikPMcVTekPEyXDAPeEa4d6oliwuWa219hZ4fdQ93G9Gss6cWWJc/pt+dFTRpS767gcvefwF/r7ctQYdUHlOLiY2vXhQCPG9UvaalRDKCQxclZiExhj1z4116Z+3GpDK8dVAIbtTmJns/yFn4=
x-forefront-antispam-report: CIP:255.255.255.255; CTRY:; LANG:en; SCL:1; SRV:; IPV:NLI; SFV:NSPM; H:CH2PR00MB0678.namprd00.prod.outlook.com; PTR:; CAT:NONE; SFTY:; SFS:(4636009)(39860400002)(396003)(346002)(136003)(376002)(366004)(5660300002)(64756008)(54906003)(8676002)(82950400001)(82960400001)(52536014)(71200400001)(33656002)(9686003)(2906002)(4326008)(55016002)(26005)(83380400001)(7696005)(966005)(76116006)(186003)(66446008)(10290500003)(66476007)(110136005)(66556008)(66946007)(86362001)(316002)(8990500004)(8936002)(6506007)(478600001)(53546011); DIR:OUT; SFP:1102;
x-ms-exchange-antispam-messagedata: vkL64+I+OtoZM8hANssF//OWVOd/GgYFqUHCurR1X8XmcNRLfwWJEVbcop0NFkwbqAWXMkFFKcFJHKEVZRkCELvTIKUKNOAu9NACgEwj+OVt0xYoMjf2t4SwKEmgl9RXyb5iZ5lkazyux7fAn6U9/H7iaQ+oJYEUwBffD/2Mgov7iKBXSJC6dHP6wxCrCQhNe7BdDK6jkUn2JnR3Gw/LnhD/DbdvwQheffvj+foc8liRbrz6CgbtJMQPnw6+wMCFVZpfFYD4QLmo60tuvsFmSKf6qS+qmTsnyvMQYhVO5AKtMv95JsoymneXjDrGGG3ZX2fexqzQqjXlbgTMM9LHDmaH2N1lydeDPAre+rKqC+8vW6vSiwgSjOneXqpOypSwK/Awi5o7Crq22gQJ07Cv+5LPtDI4758zXnCH58oLy3Pp5gMJnAVdu5kqHjjWxicTi/otjRX6YnEwyzVnUjmD3MR8xvZWNOIBpMhsxkLriOc=
x-ms-exchange-transport-forked: True
Content-Type: text/plain; charset="utf-8"
Content-Transfer-Encoding: base64
MIME-Version: 1.0
X-OriginatorOrg: microsoft.com
X-MS-Exchange-CrossTenant-AuthAs: Internal
X-MS-Exchange-CrossTenant-AuthSource: CH2PR00MB0678.namprd00.prod.outlook.com
X-MS-Exchange-CrossTenant-Network-Message-Id: d50ba012-5bd2-4b72-dfa5-08d818c84a61
X-MS-Exchange-CrossTenant-originalarrivaltime: 25 Jun 2020 05:26:19.2801 (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: a4tXJCBXlCC5xEP8Z3XwXD91+Jxn58fWuq6ZVlkkPLZDVmYM148+6B52hTiXNHLNHkrbfv0KNtIEf0H/SqK6AQ==
X-MS-Exchange-Transport-CrossTenantHeadersStamped: CH2PR00MB0825
Archived-At: <https://mailarchive.ietf.org/arch/msg/id-event/MeF0F0tFjFYIDkkoTRHCjYNDoc0>
Subject: Re: [Id-event] Robert Wilton's No Objection on draft-ietf-secevent-http-push-12: (with COMMENT)
X-BeenThere: id-event@ietf.org
X-Mailman-Version: 2.1.29
Precedence: list
List-Id: "A mailing list to discuss the potential solution for a common identity event messaging format and distribution system." <id-event.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/id-event>, <mailto:id-event-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/id-event/>
List-Post: <mailto:id-event@ietf.org>
List-Help: <mailto:id-event-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/id-event>, <mailto:id-event-request@ietf.org?subject=subscribe>
X-List-Received-Date: Thu, 25 Jun 2020 05:26:27 -0000
Thanks for your review, Rob. https://tools.ietf.org/html/draft-ietf-secevent-http-push-13 is intended to address your comments. Detailed replies are inline, prefixed by "Mike>". -----Original Message----- From: Robert Wilton via Datatracker <noreply@ietf.org> Sent: Monday, June 22, 2020 9:54 AM To: The IESG <iesg@ietf.org> Cc: draft-ietf-secevent-http-push@ietf.org; secevent-chairs@ietf.org; id-event@ietf.org; Yaron Sheffer <yaronf.ietf@gmail.com>; yaronf.ietf@gmail.com Subject: Robert Wilton's No Objection on draft-ietf-secevent-http-push-12: (with COMMENT) Robert Wilton has entered the following ballot position for draft-ietf-secevent-http-push-12: 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-secevent-http-push/ ---------------------------------------------------------------------- COMMENT: ---------------------------------------------------------------------- Hi, I found this document easy to read. A few minor nits: 1.2. Definitions This specification utilizes the following terms defined in [RFC8417]: "Security Event Token (SET)", "SET Issuer", "SET Recipient", and "Event Payload". This specification utilizes terminology defined in [RFC8417], as well as the terms defined below: This text could probably be simplified/made slightly less repetitive. Mike> Thanks for the suggestion. I removed the redundancy. 2. SET Delivery Once the SET has been validated and persisted, the SET Recipient SHOULD immediately return a response indicating that the SET was successfully delivered. The SET Recipient SHOULD NOT perform anything beyond the required validation steps prior to sending this response. Any additional steps SHOULD be executed asynchronously from delivery, in order to minimize the expense and impact of SET delivery on the SET Transmitter. Rather than "perform anything", perhaps "perform further processing of the SET" Rather than "in order to minimize the expense and impact of SET delivery on the SET Transmitter." perhaps "to minimize the time the SET Transmitter is waiting for a response". Mike> I applied both of these suggestions. 2.2. Success Response Note that the purpose of the acknowledgement response is to let the SET Transmitter know that a SET has been delivered and the information no longer needs to be retained by the SET Transmitter. Before acknowledgement, SET Recipients SHOULD ensure they have validated received SETs and retained them in a manner appropriate to information retention requirements appropriate to the SET event types signaled. The level and method of retention of SETs by SET Recipients is out of scope of this specification. The normative behaviour of retaining SETs is already specified in section 2. It might be better to refer back to that previous paragraph rather than restating it here. Mike> I refactored this to remove the redundancy. 7. IANA Considerations Section 7.1.1 lists the change controller as "IETF SecEvent Working Group", but the examples just list "IETF". Presumably one of these needs to change? Mike> Thanks. It's not just "IETF". Regards, Rob Thanks again, -- Mike
- [Id-event] Robert Wilton's No Objection on draft-… Robert Wilton via Datatracker
- Re: [Id-event] Robert Wilton's No Objection on dr… Mike Jones