[regext] Alissa Cooper's Discuss on draft-ietf-regext-login-security-07: (with DISCUSS and COMMENT)
Alissa Cooper via Datatracker <noreply@ietf.org> Tue, 21 January 2020 18:34 UTC
Return-Path: <noreply@ietf.org>
X-Original-To: regext@ietf.org
Delivered-To: regext@ietfa.amsl.com
Received: from ietfa.amsl.com (localhost [IPv6:::1]) by ietfa.amsl.com (Postfix) with ESMTP id 39D0212003F; Tue, 21 Jan 2020 10:34:57 -0800 (PST)
MIME-Version: 1.0
Content-Type: text/plain; charset="utf-8"
Content-Transfer-Encoding: 7bit
From: Alissa Cooper via Datatracker <noreply@ietf.org>
To: The IESG <iesg@ietf.org>
Cc: draft-ietf-regext-login-security@ietf.org, Joseph Yee <jyee@afilias.info>, regext-chairs@ietf.org, jyee@afilias.info, regext@ietf.org
X-Test-IDTracker: no
X-IETF-IDTracker: 6.116.1
Auto-Submitted: auto-generated
Precedence: bulk
Reply-To: Alissa Cooper <alissa@cooperw.in>
Message-ID: <157963169723.28975.13207875348171735731.idtracker@ietfa.amsl.com>
Date: Tue, 21 Jan 2020 10:34:57 -0800
Archived-At: <https://mailarchive.ietf.org/arch/msg/regext/iqTHaoWtOHsllEg5WLcZDZD7iPM>
Subject: [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
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: Tue, 21 Jan 2020 18:34:57 -0000
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? ---------------------------------------------------------------------- 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."
- [regext] Alissa Cooper's Discuss on draft-ietf-re… Alissa Cooper via Datatracker
- Re: [regext] Alissa Cooper's Discuss on draft-iet… Gould, James
- Re: [regext] Alissa Cooper's Discuss on draft-iet… Alissa Cooper