Re: [regext] [Ext] Alissa Cooper's Discuss on draft-ietf-regext-data-escrow-07: (with DISCUSS)

Barry Leiba <barryleiba@computer.org> Fri, 26 June 2020 15:42 UTC

Return-Path: <barryleiba@gmail.com>
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 774BE3A08A7; Fri, 26 Jun 2020 08:42:40 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.4
X-Spam-Level:
X-Spam-Status: No, score=-1.4 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, FREEMAIL_FORGED_FROMDOMAIN=0.25, FREEMAIL_FROM=0.001, HEADER_FROM_DIFFERENT_DOMAINS=0.249, RCVD_IN_MSPIKE_H2=-0.001, SPF_HELO_NONE=0.001, SPF_PASS=-0.001, URIBL_BLOCKED=0.001] autolearn=no 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 JdW6Tg-i4w1Z; Fri, 26 Jun 2020 08:42:39 -0700 (PDT)
Received: from mail-io1-f47.google.com (mail-io1-f47.google.com [209.85.166.47]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 74DA83A0844; Fri, 26 Jun 2020 08:42:25 -0700 (PDT)
Received: by mail-io1-f47.google.com with SMTP id o5so10259900iow.8; Fri, 26 Jun 2020 08:42:25 -0700 (PDT)
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:mime-version:references:in-reply-to:from:date :message-id:subject:to:cc:content-transfer-encoding; bh=WtyAthjokB3HG1uZ7Vr92OQLrjtIL8eV1ZBQhbLJY3M=; b=aiGxdGLFr7fIM7RH1Euoew/bndoSoV7d1Mg1uZKpPbM8o0/tHF5as9NZ1G7ynmShp+ F4izkrmC/jqWq6617Yo24SP2OUqNKFAEhKrNCu+PxCnjnjW34xXhUr+AobCYaQaebVtY oLgxQYZ0ucge1VPmE1RiTnOStKGV2bbQwPkxScAPo+527eETlXVwyjV60dego/cPcwQQ 06ocUd3VdluwRmLsIIOo1g7LLpnOi/Sifi2BsxFxTDi6XnfwSk/apghsjOYYVStXTBV6 MFXxTMR1hriD2oBA9xABbpf7lqRWGBCO91OWfNKJYAJjO9qJIM+FQ6ELGIXpqUBXqMjc L4KA==
X-Gm-Message-State: AOAM531HmDwGF7DatW9RpNloargWQEssl7IpbUtTHoMpkoGHDEdI8mOf fFfPSMuFDTpkgKQPGf1njTbfhbSE7LAdNpuPfqAGEzDyqQ4=
X-Google-Smtp-Source: ABdhPJwSDxZzYVr2njFDlMIP5eh2kSEtFSLNuOP6n0beEtuBzPim8U5lpy2LTahq085CvTdoTxugTEsDi+jwv8QrqMM=
X-Received: by 2002:a6b:8f04:: with SMTP id r4mr4019646iod.160.1593186144435; Fri, 26 Jun 2020 08:42:24 -0700 (PDT)
MIME-Version: 1.0
References: <158644010413.3377.5705483345316701310@ietfa.amsl.com> <E96FFD38-A07C-4F3C-878B-4A758F07FD5C@icann.org>
In-Reply-To: <E96FFD38-A07C-4F3C-878B-4A758F07FD5C@icann.org>
From: Barry Leiba <barryleiba@computer.org>
Date: Fri, 26 Jun 2020 11:42:13 -0400
Message-ID: <CALaySJKwUYTTeBdLuc=WdXH13mrGZM6S5W1cPMakr1zeDba6cg@mail.gmail.com>
To: Alissa Cooper <alissa@cooperw.in>, Gustavo Lozano <gustavo.lozano@icann.org>
Cc: The IESG <iesg@ietf.org>, "regext-chairs@ietf.org" <regext-chairs@ietf.org>, "regext@ietf.org" <regext@ietf.org>, "jgould@verisign.com" <jgould@verisign.com>, "draft-ietf-regext-data-escrow@ietf.org" <draft-ietf-regext-data-escrow@ietf.org>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
Archived-At: <https://mailarchive.ietf.org/arch/msg/regext/X3zWG1z_kp6V0Yi0CDXG0OIkA7I>
Subject: Re: [regext] [Ext] Alissa Cooper's Discuss on draft-ietf-regext-data-escrow-07: (with DISCUSS)
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: Fri, 26 Jun 2020 15:42:41 -0000

Alissa, will you please check the current version of the data-escrow
document < https://datatracker.ietf.org/doc/draft-ietf-regext-data-escrow/
> and see if Gustavo's changes address your concern?  And if not,
please work with Gustavo to get it sorted out.  Thanks.

Barry


On Wed, May 13, 2020 at 3:08 PM Gustavo Lozano <gustavo.lozano@icann.org> wrote:
>
> Thank you Alissa,
>
> Comments inline prefixed with GL-
>
> Regards,
> Gustavo
>
> On 4/9/20, 06:48, "regext on behalf of Alissa Cooper via Datatracker" <regext-bounces@ietf.org on behalf of noreply@ietf.org> wrote:
>
>     Alissa Cooper has entered the following ballot position for
>     draft-ietf-regext-data-escrow-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://urldefense.proofpoint.com/v2/url?u=https-3A__www.ietf.org_iesg_statement_discuss-2Dcriteria.html&d=DwICAg&c=FmY1u3PJp6wrcrwll3mSVzgfkbPSS6sJms7xcl4I5cM&r=VbweciUcwYQpIOZDSxl0ezGd1hGDtd-0BvgAgfmwfE0&m=6KotPsZrrzq2bpn2K-y1yF2urMkEJOz0OITxaBun2Xs&s=hcpPqoVjnm9-aoinq9ndolZqJuxMFPlrXAwKp9NNEi4&e=
>     for more information about IESG DISCUSS and COMMENT positions.
>
>
>     The document, along with other ballot positions, can be found here:
>     https://urldefense.proofpoint.com/v2/url?u=https-3A__datatracker.ietf.org_doc_draft-2Dietf-2Dregext-2Ddata-2Descrow_&d=DwICAg&c=FmY1u3PJp6wrcrwll3mSVzgfkbPSS6sJms7xcl4I5cM&r=VbweciUcwYQpIOZDSxl0ezGd1hGDtd-0BvgAgfmwfE0&m=6KotPsZrrzq2bpn2K-y1yF2urMkEJOz0OITxaBun2Xs&s=tOGRD4dNp47NFz1LacDypLNFM0wMf5om9bc9_HKbQMg&e=
>
>
>
>     ----------------------------------------------------------------------
>     DISCUSS:
>     ----------------------------------------------------------------------
>
>     I support Benjamin's DISCUSS and Roman's last DISCUSS point.
>
> GL - The latest version of the draft covers the feedback from Roman (DISCUSS cleared), and I also believe Benjamin's feedback (waiting for his response)
>
> Regarding Section
>     11, there are often legal agreements in place that govern all sorts of things
>     about how protocols transfer data between parties, but those are not the main
>     thing to document in an RFC. Section 11 should be documenting the technical
>     considerations for how to protect the data that may be escrowed.
>
> GL - draft-ietf-regext-data-escrow describes a standardized format for escrow, and it's not a document specifying escrow services (i.e., no definition of a transport protocol, signaling mechanism, etc.). Section 11 has been strengthen based on the comments from other IESG's members, and I believe it's in good shape now.
>
> Here are the differences between 07 and 08, and 08 and 09:
> https://tools.ietf.org/rfcdiff?url2=draft-ietf-regext-data-escrow-08.txt
> https://tools.ietf.org/rfcdiff?url2=draft-ietf-regext-data-escrow-09.txt
>
> I think that a draft describing the best security / operational practices for escrow service providers could be a good idea. In the case of the gTLD space, there is no urgency for such a document, as the security / operational requirements are detailed in legal agreements.
>
> Hopefully, this clarifies my previous comments.
>
>     _______________________________________________
>     regext mailing list
>     regext@ietf.org
>     https://urldefense.proofpoint.com/v2/url?u=https-3A__www.ietf.org_mailman_listinfo_regext&d=DwICAg&c=FmY1u3PJp6wrcrwll3mSVzgfkbPSS6sJms7xcl4I5cM&r=VbweciUcwYQpIOZDSxl0ezGd1hGDtd-0BvgAgfmwfE0&m=6KotPsZrrzq2bpn2K-y1yF2urMkEJOz0OITxaBun2Xs&s=gtb7G2HcGVH0Nkn1jQNw3zcDejr56jw5emEs2RK8ilw&e=
>