Hi Gustavo,
> -----Original Message----- > From: Gustavo Lozano <gustavo.loz...@icann.org> > Sent: 17 April 2020 00:59 > To: Rob Wilton (rwilton) <rwil...@cisco.com>; The IESG <i...@ietf.org> > Cc: draft-ietf-regext-data-esc...@ietf.org; regext-cha...@ietf.org; > regext@ietf.org; James Gould <jgo...@verisign.com> > Subject: Re: [Ext] Robert Wilton's Discuss on draft-ietf-regext-data- > escrow-07: (with DISCUSS and COMMENT) > > Thank you Robert, > > Comments inline, prefixed with GL - > > Regards, > Gustavo > > On 4/8/20, 10:04, "Robert Wilton via Datatracker" <nore...@ietf.org> > wrote: > > Robert Wilton 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=DwICaQ&c=FmY1u3PJp6wrcrwll3mSVzgfkbPSS6sJms7xcl4I5cM&r=V > bweciUcwYQpIOZDSxl0ezGd1hGDtd-0BvgAgfmwfE0&m=gZgTftWuC9SsZdq_QWTwb- > T4RjxNiDq9i2krpdXgHfM&s=QHMiOWDTGvuiZh0DtVdWwx_J4DxECAFWGpr-Srux4pQ&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=DwICaQ&c=FmY1u3PJp6wrcrwll3mSVzgfkbPSS6sJms7xcl4I5cM&r=VbweciU > cwYQpIOZDSxl0ezGd1hGDtd-0BvgAgfmwfE0&m=gZgTftWuC9SsZdq_QWTwb- > T4RjxNiDq9i2krpdXgHfM&s=YhAtC7C7hDwiSnfUvetOd_lI7t6Q5KkhtITQ9Vv9OXE&e= > > > > ---------------------------------------------------------------------- > DISCUSS: > ---------------------------------------------------------------------- > > Hi, > > I spotted some issues with the terminology and the description of the > algorithm > that I would like you to please address. > > Section 2: Terminology > > The definitions provided for "Differential" vs "Incremental" are the > opposite > to their standard meaning in backups. The term definitions should be > reversed > to align with the common vernacular. I.e. differential is the diff > against the > last full backup, incremental is the backup since the backup (of any > type) was > performed. > > GL - The definition of differential in the draft complies with the legal > use in the gTLD space. The amount of work required to make this change, > make it unrealistic. It's worth mentioning that data escrow is not the > same as a backup. > I don't see a huge difference between a remote backup vs data escrow. E.g., if I use an online backup service then it seems that they are storing data securely on my behalf that I can subsequently recover if required. It feels like the concepts are so very similar that using the same set of terms with different meanings could easily cause confusion. The choice here is between having (i) a protocol that matches legal data escrow definitions but could easily be confused by people who see this as a type of remote backup (ii) a protocol specification that matches the widely used common definitions for these terms (e.g. https://en.wikipedia.org/wiki/Incremental_backup, https://en.wikipedia.org/wiki/Differential_backup), but that is opposite to the legal definitions. It seems to me that the legal definitions are really self-contained within their documents, and potentially could be updated over time. However, I see no way that we can convince the world in general to reverse their understanding/usage of these terms, and hence if you are to use these terms, I still believe that they should align to their common usage rather than the legal definitions. Of course, an alternative solution would be to define and use completely different terms for the incremental and differential deposits, e.g. full deposit, full-delta deposit, minimal-delta deposit. Thanks, Rob _______________________________________________ regext mailing list regext@ietf.org https://www.ietf.org/mailman/listinfo/regext
