Re: [Id-event] Duplicate SET Recipient definition

"Richard Backman, Annabelle" <richanna@amazon.com> Mon, 08 July 2019 22:50 UTC

Return-Path: <prvs=0857bd4fb=richanna@amazon.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 86598120346 for <id-event@ietfa.amsl.com>; Mon, 8 Jul 2019 15:50:59 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -14.499
X-Spam-Level:
X-Spam-Status: No, score=-14.499 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, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_HI=-5, SPF_HELO_NONE=0.001, SPF_PASS=-0.001, URIBL_BLOCKED=0.001, USER_IN_DEF_SPF_WL=-7.5] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (1024-bit key) header.d=amazon.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 NiHHY5uY4SMX for <id-event@ietfa.amsl.com>; Mon, 8 Jul 2019 15:50:57 -0700 (PDT)
Received: from smtp-fw-9102.amazon.com (smtp-fw-9102.amazon.com [207.171.184.29]) (using TLSv1.2 with cipher RC4-SHA (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id A46D112033F for <id-event@ietf.org>; Mon, 8 Jul 2019 15:50:56 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=amazon.com; i=@amazon.com; q=dns/txt; s=amazon201209; t=1562626256; x=1594162256; h=from:to:cc:subject:date:message-id:references: in-reply-to:mime-version; bh=Fo1UxglLc7lZW/imjzPIcGWDVk0cKu2rTxYwHp/d4P4=; b=lqmez4gXMFmrn0WmO/3wgJzwv9zUHTvuCnINW4kBfMqRIaOwG4/9gceI JHZYfYq17Vj7MJXzGGO+dEi8VgDqT+90FvwM1TGgH3+ZEYLFthvAmjKpG ES7SIgAKdiIgAjq9y/Xw03Zuy4yi8ULy8f0rVrgXu3OwUnfuvls7I4aVF c=;
X-IronPort-AV: E=Sophos;i="5.62,468,1554768000"; d="scan'208,217";a="684380270"
Received: from sea3-co-svc-lb6-vlan2.sea.amazon.com (HELO email-inbound-relay-1a-67b371d8.us-east-1.amazon.com) ([10.47.22.34]) by smtp-border-fw-out-9102.sea19.amazon.com with ESMTP; 08 Jul 2019 22:50:53 +0000
Received: from EX13MTAUWC001.ant.amazon.com (iad55-ws-svc-p15-lb9-vlan3.iad.amazon.com [10.40.159.166]) by email-inbound-relay-1a-67b371d8.us-east-1.amazon.com (Postfix) with ESMTPS id DB1F9A1E6E; Mon, 8 Jul 2019 22:50:52 +0000 (UTC)
Received: from EX13D11UWC002.ant.amazon.com (10.43.162.174) by EX13MTAUWC001.ant.amazon.com (10.43.162.135) with Microsoft SMTP Server (TLS) id 15.0.1367.3; Mon, 8 Jul 2019 22:50:52 +0000
Received: from EX13D11UWC004.ant.amazon.com (10.43.162.101) by EX13D11UWC002.ant.amazon.com (10.43.162.174) with Microsoft SMTP Server (TLS) id 15.0.1367.3; Mon, 8 Jul 2019 22:50:51 +0000
Received: from EX13D11UWC004.ant.amazon.com ([10.43.162.101]) by EX13D11UWC004.ant.amazon.com ([10.43.162.101]) with mapi id 15.00.1367.000; Mon, 8 Jul 2019 22:50:51 +0000
From: "Richard Backman, Annabelle" <richanna@amazon.com>
To: Mike Jones <Michael.Jones@microsoft.com>
CC: "id-event@ietf.org" <id-event@ietf.org>
Thread-Topic: Duplicate SET Recipient definition
Thread-Index: AdU11GAlq9j5MW5WQryC+jzQpbYcrP//oRWA
Date: Mon, 08 Jul 2019 22:50:51 +0000
Message-ID: <9B832BEA-43DF-4D6F-949C-1C65AB1E1DFF@amazon.com>
References: <SN6PR00MB030180978324E11A8723A68EF5F60@SN6PR00MB0301.namprd00.prod.outlook.com>
In-Reply-To: <SN6PR00MB030180978324E11A8723A68EF5F60@SN6PR00MB0301.namprd00.prod.outlook.com>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach:
X-MS-TNEF-Correlator:
user-agent: Microsoft-MacOutlook/10.10.0.180812
x-ms-exchange-messagesentrepresentingtype: 1
x-ms-exchange-transport-fromentityheader: Hosted
x-originating-ip: [10.43.161.16]
Content-Type: multipart/alternative; boundary="_000_9B832BEA43DF4D6F949C1C65AB1E1DFFamazoncom_"
MIME-Version: 1.0
Archived-At: <https://mailarchive.ietf.org/arch/msg/id-event/2TdnPHnS26Jr8XRGSmec2pHMc-4>
Subject: Re: [Id-event] Duplicate SET Recipient definition
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: Mon, 08 Jul 2019 22:51:09 -0000

The current language was a compromise between it being confusing to have SET Transmitter defined here but not SET Recipient, and the fact that SET Recipient is already defined. See brief discussion here: https://mailarchive.ietf.org/arch/msg/id-event/iUDvQEZHrJ5o1aehCbZIkwqwmWs

I’m open to suggestions. We could separately list the specific terms used in this doc that are defined in 8417?

--
Annabelle Richard Backman
AWS Identity


From: Mike Jones <Michael.Jones@microsoft.com>
Date: Monday, July 8, 2019 at 2:31 PM
To: "Richard Backman, Annabelle" <richanna@amazon.com>
Cc: "id-event@ietf.org" <id-event@ietf.org>
Subject: Duplicate SET Recipient definition

Hi Annabelle,

Please delete the “Set Recipient” definition from the Push spec, as this term is already defined in the Security Event Token (SET)  specification [RFC 8417].

                                                                Thanks,
                                                                -- Mike