Re: [regext] [Ext] Roman Danyliw's No Objection on draft-ietf-regext-dnrd-objects-mapping-09: (with COMMENT)

Gustavo Lozano <gustavo.lozano@icann.org> Thu, 08 October 2020 21:44 UTC

Return-Path: <gustavo.lozano@icann.org>
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 B4ADD3A0E14; Thu, 8 Oct 2020 14:44:36 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.899
X-Spam-Level:
X-Spam-Status: No, score=-1.899 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, SPF_HELO_NONE=0.001, SPF_PASS=-0.001, URIBL_BLOCKED=0.001] autolearn=ham autolearn_force=no
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 6G29L7sy6gXW; Thu, 8 Oct 2020 14:44:34 -0700 (PDT)
Received: from ppa2.lax.icann.org (ppa2.lax.icann.org [192.0.33.77]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id E9F8A3A0CB8; Thu, 8 Oct 2020 14:44:32 -0700 (PDT)
Received: from MBX112-W2-CO-1.pexch112.icann.org (out.mail.icann.org [64.78.33.5]) by ppa2.lax.icann.org (8.16.0.42/8.16.0.42) with ESMTPS id 098LiU8j028265 (version=TLSv1.2 cipher=ECDHE-RSA-AES256-GCM-SHA384 bits=256 verify=NOT); Thu, 8 Oct 2020 21:44:30 GMT
Received: from MBX112-W2-CO-2.pexch112.icann.org (10.226.41.130) by MBX112-W2-CO-2.pexch112.icann.org (10.226.41.130) with Microsoft SMTP Server (version=TLS1_2, cipher=TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384) id 15.2.659.4; Thu, 8 Oct 2020 14:44:29 -0700
Received: from MBX112-W2-CO-2.pexch112.icann.org ([10.226.41.130]) by MBX112-W2-CO-2.pexch112.icann.org ([10.226.41.130]) with mapi id 15.02.0659.006; Thu, 8 Oct 2020 14:44:29 -0700
From: Gustavo Lozano <gustavo.lozano@icann.org>
To: Roman Danyliw <rdd@cert.org>, The IESG <iesg@ietf.org>
CC: "draft-ietf-regext-dnrd-objects-mapping@ietf.org" <draft-ietf-regext-dnrd-objects-mapping@ietf.org>, "regext-chairs@ietf.org" <regext-chairs@ietf.org>, "regext@ietf.org" <regext@ietf.org>, "Scott Hollenbeck" <shollenbeck@verisign.com>
Thread-Topic: [Ext] Roman Danyliw's No Objection on draft-ietf-regext-dnrd-objects-mapping-09: (with COMMENT)
Thread-Index: AQHWek0NM6nnsLUj00ClGycGEkNI0KmOg8yA
Date: Thu, 8 Oct 2020 21:44:29 +0000
Message-ID: <227EFF28-3F3C-4452-9024-E7FF0B07E0C7@icann.org>
References: <159829743704.11951.16778460331586195166@ietfa.amsl.com>
In-Reply-To: <159829743704.11951.16778460331586195166@ietfa.amsl.com>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach:
X-MS-TNEF-Correlator:
user-agent: Microsoft-MacOutlook/16.38.20061401
x-originating-ip: [192.0.32.234]
x-source-routing-agent: Processed
Content-Type: text/plain; charset="utf-8"
Content-ID: <76924F8555A77446A5D9085654C8151B@pexch112.icann.org>
Content-Transfer-Encoding: base64
MIME-Version: 1.0
X-Proofpoint-Virus-Version: vendor=fsecure engine=2.50.10434:6.0.235, 18.0.687 definitions=2020-10-08_15:2020-10-08, 2020-10-08 signatures=0
Archived-At: <https://mailarchive.ietf.org/arch/msg/regext/MqMyZV7GcmY3D9oI-N_ratoFZww>
Subject: Re: [regext] [Ext] Roman Danyliw's No Objection on draft-ietf-regext-dnrd-objects-mapping-09: (with 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, 08 Oct 2020 21:44:37 -0000

Thank you Roman,

Comments below are prefixed with Authors-.

A new version of the I-D has been published here: https://www.ietf.org/id/draft-ietf-regext-dnrd-objects-mapping-10.txt

Regards,
Gustavo

On 8/24/20, 12:30, "Roman Danyliw via Datatracker" <noreply@ietf.org> wrote:

    Roman Danyliw has entered the following ballot position for
    draft-ietf-regext-dnrd-objects-mapping-09: 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://urldefense.com/v3/__https://www.ietf.org/iesg/statement/discuss-criteria.html__;!!PtGJab4!tk33CgA_IPEteHsusEK0roZWxzw786v35y7J1dr-z2AkTO_ktFH_C2B8qt_qla02uh-Mn0wQLRk$ 
    for more information about IESG DISCUSS and COMMENT positions.


    The document, along with other ballot positions, can be found here:
    https://urldefense.com/v3/__https://datatracker.ietf.org/doc/draft-ietf-regext-dnrd-objects-mapping/__;!!PtGJab4!tk33CgA_IPEteHsusEK0roZWxzw786v35y7J1dr-z2AkTO_ktFH_C2B8qt_qla02uh-MCOlAdzI$ 



    ----------------------------------------------------------------------
    COMMENT:
    ----------------------------------------------------------------------

    Thank you for this document and the various XLS/CSV examples related to
    particular elements of the data model.

    ** Section 4.4.  Per the use of SHA-256 as a checksum algorithm, what
    identifier should be used in the cksumAlg attribute?

Authors- text added in the next version of the I-D.

    ** Section 4.4.  I concur with the OPSDIR reviewer (Joe Clarke), it would seem
    like native support (in the format itself) for a more robust checksum algorithm
    would be desirable.

Authors- text added in the next version of the I-D.

    ** Section 4.6.2.1.  Per “The <rdeCsv:file> child element defines a reference
    to the CSV file name”, is any file path information permitted, or are do all
    referenced files in dump need to be unique?

Authors- The CSV file name reference can be any file path, but in general is only a file name that is relative to the location of the XML definition file.

    ** Section 5.8.1.  Please add a normative reference to XPath

Authors- text added in the next version of the I-D.

    ** Section 7.  If one had a business model requiring that checksums  be
    computed using SHA-384 (set @cksumAlg) or using 7z compression (set
    @compression), how would one specify that in the profile per the defined steps
    in this section – nothing needs to be extended (step 1, step 3) or <policy>
    doesn’t seem to support specifying a particular attribute (step 2), so would
    one hard-code that into a custom schema (step 4)?

Authors- only the values need to be specified in @cksumAlg and @compression after an out-of-band negotiation. Escrow services are regulated using legal agreements, and the details are usually specified based on out-of-band-negotiations.

    ** Editorial Nits
    - Section 9.1  Typo. s/Seperated/Separated/

Authors- fixed in the next version of the I-D.

    - Section 11.  Typos.  A few repeated instances.  s/section Section/Section/g

Authors- fixed in the next version of the I-D.