IETF Logo Mail Archive

Re: [Id-event] Alissa Cooper's No Objection on draft-ietf-secevent-token-11: (with COMMENT)

Alissa Cooper <alissa@cooperw.in> Thu, 10 May 2018 00:44 UTC

Return-Path: <alissa@cooperw.in>
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 A050012426E; Wed, 9 May 2018 17:44:01 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.699
X-Spam-Level:
X-Spam-Status: No, score=-2.699 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_LOW=-0.7, 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=cooperw.in header.b=YC3zxHJu; dkim=pass (2048-bit key) header.d=messagingengine.com header.b=d3XzQ1Z9
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 GatMZQ04YMsw; Wed, 9 May 2018 17:43:59 -0700 (PDT)
Received: from out1-smtp.messagingengine.com (out1-smtp.messagingengine.com [66.111.4.25]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 93D841200A0; Wed, 9 May 2018 17:43:59 -0700 (PDT)
Received: from compute7.internal (compute7.nyi.internal [10.202.2.47]) by mailout.nyi.internal (Postfix) with ESMTP id EB15E20DBD; Wed, 9 May 2018 20:43:58 -0400 (EDT)
Received: from mailfrontend1 ([10.202.2.162]) by compute7.internal (MEProxy); Wed, 09 May 2018 20:43:58 -0400
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=cooperw.in; h=cc :content-type:date:from:in-reply-to:message-id:mime-version :references:subject:to:x-me-sender:x-me-sender:x-sasl-enc; s= fm3; bh=toKNeYNKJhXTGJhavRwGMrxMqkFca4bgNyr3z9P9M9Q=; b=YC3zxHJu dFaDclN+Q9Etr3eaw+HFxrysK0RtAvP93lxNX1Np00Qv4b7glKzxfFQakfeN6/dR /vJROEG5OwOG4YCBDJTiWgoFn4iwwrcuY2Au9Kcxv10oPUNxl19GGRcvQugYNMIC +l5CUMhqPZTEH55MxMgUVJBa3hZq/Ng/t+1XoaQR1jQnV8kFz7ToDkTI1s/aY6Kk FJHHuJKZTNSYwcPEP67uQ1yM4JTjfHGFbME4dMnEelNy3F0m4e9um0PjIQgE6U6O 7EuJQFCwa0OJ1RxYOsAQY+IKjiob27ikBtj4l9NAPi4ML98kDvTOVlznHlGvJTq7 pnIhgrhRCgFPcw==
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d= messagingengine.com; h=cc:content-type:date:from:in-reply-to :message-id:mime-version:references:subject:to:x-me-sender :x-me-sender:x-sasl-enc; s=fm2; bh=toKNeYNKJhXTGJhavRwGMrxMqkFca 4bgNyr3z9P9M9Q=; b=d3XzQ1Z9nSesw15fW/97WYzQ5L3DRnzJk0coUz5DAPCd/ e0cHNxCIuKhbBdJb3QZPitMpZOwz2GspS7qge2eVpz1LBIoUKreaMQswAqzpyDUX XaFVnYvt8fRE59FwZhwh3n4Szqmmo3EuXKKe/y+ERVuDyRUg53rWvF8j4kVokVvD nstf0OWuPjfZCCWk4X7SKQr/NqmQ0uq6jDg2/1AvNkC6rM0oCzwIHkUh1cnQKu21 9G/6rLCziyIRG/JveDfskL67R/bqCEuO8OvbAHoSo9ImIHyz4XhmwbbLe7FRO4xt +RjRKy3an3U2HtsgB5cxmRGDeXe70SlJrmcDrQkNA==
X-ME-Sender: <xms:zpXzWmlPyJpRGqSNTwkHFZEu5kqifgSHxBAeX8wnpVhVlzbiEbAVfw>
Received: from rtp-alcoop-nitro2.cisco.com (unknown [173.38.117.81]) by mail.messagingengine.com (Postfix) with ESMTPA id 55004E4ED0; Wed, 9 May 2018 20:43:58 -0400 (EDT)
Content-Type: multipart/alternative; boundary="Apple-Mail=_1CBFA7C7-4129-411D-8FE7-FF79FA208F98"
Mime-Version: 1.0 (Mac OS X Mail 9.3 \(3124\))
From: Alissa Cooper <alissa@cooperw.in>
In-Reply-To: <993988C7-0C27-465D-9BEE-9BD40861F93B@oracle.com>
Date: Wed, 09 May 2018 20:43:57 -0400
Cc: IESG <iesg@ietf.org>, draft-ietf-secevent-token@ietf.org, Yaron Sheffer <yaronf.ietf@gmail.com>, secevent-chairs@ietf.org, id-event@ietf.org
Message-Id: <C45DB184-BA1E-4899-889E-93868AEF47D3@cooperw.in>
References: <152589422080.3937.17278656045470630984.idtracker@ietfa.amsl.com> <993988C7-0C27-465D-9BEE-9BD40861F93B@oracle.com>
To: Phil Hunt <phil.hunt@oracle.com>
X-Mailer: Apple Mail (2.3124)
Archived-At: <https://mailarchive.ietf.org/arch/msg/id-event/kN4kuYyiSwWGjlCktilIGrrpye0>
Subject: Re: [Id-event] Alissa Cooper's No Objection on draft-ietf-secevent-token-11: (with COMMENT)
X-BeenThere: id-event@ietf.org
X-Mailman-Version: 2.1.22
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, 10 May 2018 00:44:01 -0000

Thanks!

> On May 9, 2018, at 7:25 PM, Phil Hunt <phil.hunt@oracle.com> wrote:
> 
> Alissa,
> 
> Your feedback is now posted in draft 12. 
> 
> Thanks again,
> 
> Phil
> 
> Oracle Corporation, Identity Cloud Services Architect
> @independentid
> www.independentid.com <http://www.independentid.com/>phil.hunt@oracle.com <mailto:phil.hunt@oracle.com>
> 
>> On May 9, 2018, at 12:30 PM, Alissa Cooper <alissa@cooperw.in <mailto:alissa@cooperw.in>> wrote:
>> 
>> Alissa Cooper has entered the following ballot position for
>> draft-ietf-secevent-token-11: 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 <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-token/ <https://datatracker.ietf.org/doc/draft-ietf-secevent-token/>
>> 
>> 
>> 
>> ----------------------------------------------------------------------
>> COMMENT:
>> ----------------------------------------------------------------------
>> 
>> = Sec. 5.1 =
>> 
>> "Security events distributed through third parties or that carry
>>   personally identifiable information SHOULD be encrypted using JWE
>>   [RFC7516] or secured for confidentiality by other means."
>> 
>> The SHOULD here seems like it should be a MUST unless there are obvious exception cases.
>> 
>> = Sec. 5.2 =
>> 
>> "In
>>   addition to confidentiality and integrity (discussed above),
>>   implementers and profiling specifications MUST consider the
>>   consequences of delivery mechanisms that are not secure and/or not
>>   assured."
>> 
>> The "implementers ... MUST consider" construction seems like an odd use of normative language.
>> 
>> 
>

v2.23.0 | Report a Bug | By Email