[secdir] Secdir last call review of draft-ietf-regext-epp-fees-16
Yoav Nir via Datatracker <noreply@ietf.org> Sat, 29 June 2019 15:26 UTC
Return-Path: <noreply@ietf.org>
X-Original-To: secdir@ietf.org
Delivered-To: secdir@ietfa.amsl.com
Received: from ietfa.amsl.com (localhost [IPv6:::1]) by ietfa.amsl.com (Postfix) with ESMTP id B99281200B6; Sat, 29 Jun 2019 08:26:01 -0700 (PDT)
MIME-Version: 1.0
Content-Type: text/plain; charset="utf-8"
Content-Transfer-Encoding: 7bit
From: Yoav Nir via Datatracker <noreply@ietf.org>
To: secdir@ietf.org
Cc: ietf@ietf.org, draft-ietf-regext-epp-fees.all@ietf.org, regext@ietf.org
X-Test-IDTracker: no
X-IETF-IDTracker: 6.98.1
Auto-Submitted: auto-generated
Precedence: bulk
Reply-To: Yoav Nir <ynir.ietf@gmail.com>
Message-ID: <156182196167.12901.11966487185176024571@ietfa.amsl.com>
Date: Sat, 29 Jun 2019 08:26:01 -0700
Archived-At: <https://mailarchive.ietf.org/arch/msg/secdir/7-a6ajKwahc0xpZbmWOoPpi_sDw>
Subject: [secdir] Secdir last call review of draft-ietf-regext-epp-fees-16
X-BeenThere: secdir@ietf.org
X-Mailman-Version: 2.1.29
List-Id: Security Area Directorate <secdir.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/secdir>, <mailto:secdir-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/secdir/>
List-Post: <mailto:secdir@ietf.org>
List-Help: <mailto:secdir-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/secdir>, <mailto:secdir-request@ietf.org?subject=subscribe>
X-List-Received-Date: Sat, 29 Jun 2019 15:26:02 -0000
Reviewer: Yoav Nir Review result: Has Nits Hi I have reviewed this document as part of the security directorate's ongoing effort to review all IETF documents being processed by the IESG. These comments were written primarily for the benefit of the security area directors. Document editors and WG chairs should treat these comments just like any other last call comments. The entire text of the Security Considerations section is as follows: The mapping extensions described in this document do not provide any security services beyond those described by EPP [RFC5730], the EPP domain name mapping [RFC5731], and protocol layers used by EPP. The security considerations described in these other specifications apply to this specification as well. This is what we like to call "security considerations by reference". I don't know what "security services" are in this context, but they are not the only thing that needs to be described in a Security Considerations section. In this case, the draft adds information about fees, customer credit and pay schedule. This falls under the category of financial information, which should be protected in transit by security mechanisms that protect confidentiality and integrity. It is also true that any transport mechanism that complies with RFC 5730 provides those functions. So what I'm missing here is a sentence that calls this out specifically. Something along the lines of "This extension adds financial information to the EPP protocol, so confidentiality and integrity protection must be provided by the transport mechanism. All transports compliant with RFC5730 provide that"
- [secdir] Secdir last call review of draft-ietf-re… Yoav Nir via Datatracker
- Re: [secdir] Secdir last call review of draft-iet… Barry Leiba
- Re: [secdir] Secdir last call review of draft-iet… Roger D Carney
- Re: [secdir] Secdir last call review of draft-iet… Yoav Nir