Re: [regext] Alissa Cooper's Discuss on draft-ietf-regext-login-security-07: (with DISCUSS and COMMENT)

Alissa Cooper <alissa@cooperw.in> Thu, 23 January 2020 02:51 UTC

Return-Path: <alissa@cooperw.in>
X-Original-To: regext@ietfa.amsl.com
Delivered-To: regext@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 5800312004F; Wed, 22 Jan 2020 18:51:31 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.7
X-Spam-Level:
X-Spam-Status: No, score=-2.7 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, 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=YK3AVYnp; dkim=pass (2048-bit key) header.d=messagingengine.com header.b=Y/c+n2a9
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 6D-7pvIYPB6y; Wed, 22 Jan 2020 18:51:29 -0800 (PST)
Received: from out3-smtp.messagingengine.com (out3-smtp.messagingengine.com [66.111.4.27]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 8ADB9120018; Wed, 22 Jan 2020 18:51:29 -0800 (PST)
Received: from compute7.internal (compute7.nyi.internal [10.202.2.47]) by mailout.nyi.internal (Postfix) with ESMTP id DF0CC2016D; Wed, 22 Jan 2020 21:51:28 -0500 (EST)
Received: from mailfrontend1 ([10.202.2.162]) by compute7.internal (MEProxy); Wed, 22 Jan 2020 21:51:28 -0500
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=cooperw.in; h= content-type:mime-version:subject:from:in-reply-to:date:cc :content-transfer-encoding:message-id:references:to; s=fm2; bh=5 g27AzMqnNW1eATfuKmcVCrj2OQ7xytpnVlD6ix5zNw=; b=YK3AVYnpNJAtzDkwH u5h4M1c7Le9aLB5VYh+ROl/cZQlDB/P/MBytLLamC6hXIpBfvfBn/GdvWRGDD6ZG yBf+PDygzx59tOV9QqVl1YyyVhjKo60FfZ86+ugx4Q/ZvkbRJXxFXHeLpuzPmh/m rzAam5X8r64yokjLtjJs4J5ZB8L1K6PxmpqtnRTu6FNwLcVU32qdr+qgobLC+LWw uWGkTUOjq8PTUmj4genEfCN6sSvIV66Se60nxi2/gG5jYKpyFJ1bpDaRj1jk6N+3 lAuBd4ELilmQmIXQVKnlc2L09NVYes7wJH34rjAOLXtnMSfLOEZZxsYBo0qTnwuo enzpQ==
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d= messagingengine.com; h=cc:content-transfer-encoding:content-type :date:from:in-reply-to:message-id:mime-version:references :subject:to:x-me-proxy:x-me-proxy:x-me-sender:x-me-sender :x-sasl-enc; s=fm1; bh=5g27AzMqnNW1eATfuKmcVCrj2OQ7xytpnVlD6ix5z Nw=; b=Y/c+n2a9U4Vr+lyIQLTzCWkIcNmr75B84VQ3+/Ih/MDXXszWu5HYpPM93 dnpr7NRPV2+x/OJ6fT0VY5yFzFZX42iZ7wtZ31BzmYuW4RnElXYdpbF9alUuwNzS 0BZnsl4byyId11NLMrRdnBh1fxCwth2FeOrhLh7IALmZ6cl4J5SRhHge+wGDPDrG y/uUb8PCc6FairMsh1iY4/pk/2if1HKvQnEdZ1vkHblhYtEnFGBBTNOJume5Nvkr eStkzY8IQkiVnwn/GY7aghSgYA5a75E+Mzd8DzhO1uJCZH+FZNWg0felcVQ+74n1 cxJ/d2BINg6DyNm8skzRv6Vuk2yag==
X-ME-Sender: <xms:MAopXq1FcZsjrUK7V3tPlV6KBO8EDop5VMdNUBanO4b4STX6JP38-w>
X-ME-Proxy-Cause: gggruggvucftvghtrhhoucdtuddrgedugedrvddugdegjecutefuodetggdotefrodftvf curfhrohhfihhlvgemucfhrghsthforghilhdpqfgfvfdpuffrtefokffrpgfnqfghnecu uegrihhlohhuthemuceftddtnecusecvtfgvtghiphhivghnthhsucdlqddutddtmdenuc fjughrpegtggfuhfgjfffgkfhfvffosehtqhhmtdhhtdejnecuhfhrohhmpeetlhhishhs rgcuvehoohhpvghruceorghlihhsshgrsegtohhophgvrhifrdhinheqnecuffhomhgrih hnpehvvghrihhsihhgnhhinhgtrdgtohhmpdhivghtfhdrohhrghenucfkphepudehuddr udekuddrjeejrddufedvnecuvehluhhsthgvrhfuihiivgeptdenucfrrghrrghmpehmrg hilhhfrhhomheprghlihhsshgrsegtohhophgvrhifrdhinh
X-ME-Proxy: <xmx:MAopXomrYtic_IiEzI6h5I7Thykljop_CrsJ0brsFS6YZEjYPyo71Q> <xmx:MAopXpVJDT5IG6dPsU-CynsQMxN4077yBLVm1kEroeNQc03Dp0Ezvg> <xmx:MAopXmvvNZy1NsEYN4QKke4JaIOVncLYcXVAqDyFi-PTo87CcXN_fA> <xmx:MAopXjniZlMysS8u3ziiugD7r1mY2gAZB0jj3PLJhX1zJCgnZP2PxA>
Received: from [172.20.16.151] (unknown [151.181.77.132]) by mail.messagingengine.com (Postfix) with ESMTPA id 3A0D9328005C; Wed, 22 Jan 2020 21:51:28 -0500 (EST)
Content-Type: text/plain; charset="utf-8"
Mime-Version: 1.0 (Mac OS X Mail 11.5 \(3445.9.1\))
From: Alissa Cooper <alissa@cooperw.in>
In-Reply-To: <EC1107F4-F10D-43AC-91F3-2DFFC9367CE4@verisign.com>
Date: Wed, 22 Jan 2020 21:51:27 -0500
Cc: IESG <iesg@ietf.org>, "draft-ietf-regext-login-security@ietf.org" <draft-ietf-regext-login-security@ietf.org>, Joseph Yee <jyee@afilias.info>, "regext-chairs@ietf.org" <regext-chairs@ietf.org>, "regext@ietf.org" <regext@ietf.org>
Content-Transfer-Encoding: quoted-printable
Message-Id: <D90E8A8E-C72D-49CC-9A7C-FF6BBE860A2C@cooperw.in>
References: <157963169723.28975.13207875348171735731.idtracker@ietfa.amsl.com> <EC1107F4-F10D-43AC-91F3-2DFFC9367CE4@verisign.com>
To: "Gould, James" <jgould@verisign.com>
X-Mailer: Apple Mail (2.3445.9.1)
Archived-At: <https://mailarchive.ietf.org/arch/msg/regext/ykwOjsGT2TfMIsjBs31QPMFYKwk>
Subject: Re: [regext] Alissa Cooper's Discuss on draft-ietf-regext-login-security-07: (with DISCUSS and COMMENT)
X-BeenThere: regext@ietf.org
X-Mailman-Version: 2.1.29
Precedence: list
List-Id: Registration Protocols Extensions <regext.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/regext>, <mailto:regext-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/regext/>
List-Post: <mailto:regext@ietf.org>
List-Help: <mailto:regext-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/regext>, <mailto:regext-request@ietf.org?subject=subscribe>
X-List-Received-Date: Thu, 23 Jan 2020 02:51:32 -0000

Thanks for the explanation. I cleared my DISCUSS.

Alissa


> On Jan 21, 2020, at 3:29 PM, Gould, James <jgould@verisign.com> wrote:
> 
> Alissa,
> 
> Thank you for your review and comments.  I answer your question below.
> 
> -- 
> 
> JG
> 
> 
> 
> James Gould
> Distinguished Engineer
> jgould@Verisign.com <applewebdata://13890C55-AAE8-4BF3-A6CE-B4BA42740803/jgould@Verisign.com>
> 
> 703-948-3271
> 12061 Bluemont Way
> Reston, VA 20190
> 
> Verisign.com <http://verisigninc.com/>
> 
> On 1/21/20, 1:34 PM, "Alissa Cooper via Datatracker" <noreply@ietf.org> wrote:
> 
>    Alissa Cooper has entered the following ballot position for
>    draft-ietf-regext-login-security-07: Discuss
> 
>    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-regext-login-security/
> 
> 
> 
>    ----------------------------------------------------------------------
>    DISCUSS:
>    ----------------------------------------------------------------------
> 
>    Perhaps some simple questions (apologies if I'm missing something obvious):
>    since there is no registry of custom events, how do developers of independent
>    implementations know which custom events they should be aiming to support? And
>    how do they understand the semantics associated with custom events beyond what
>    the event names can convey?
> 
> JG - The custom security event is following an EPP extensibility pattern that has been used in prior EPP RFCs (e.g., Launch Phases in RFC 8334, Contact Types in RFC 8543, Operations in RFC 8590).  The definition of the custom events can take many forms, such as inclusion in a server policy document or use of an in-band policy query interface.  The EPP policy extension draft-gould-regext-login-security-policy is an example of an EPP query interface for draft-ietf-regext-login-security. 
> 
>    ----------------------------------------------------------------------
>    COMMENT:
>    ----------------------------------------------------------------------
> 
>    = Section 5 =
> 
>    "One schema is presented here that is the EPP Login Security Extension
>       schema."
> 
>    This phrasing seems a little odd (is there more than one schema?). I would
>    suggest "The EPP Login Security Extension schema is presented here."
> 
>   JG - I like your suggested phrase better.  I'll make that change.  
> 
>