[regext] I-D Action: draft-ietf-regext-data-escrow-10.txt
A New Internet-Draft is available from the on-line Internet-Drafts directories. This draft is a work item of the Registration Protocols Extensions WG of the IETF. Title : Registry Data Escrow Specification Author : Gustavo Lozano Filename: draft-ietf-regext-data-escrow-10.txt Pages : 23 Date: 2020-06-01 Abstract: This document specifies the format and contents of data escrow deposits targeted primarily for domain name registries. The specification is designed to be independent of the underlying objects that are being escrowed and therefore it could also be used for purposes other than domain name registries. The IETF datatracker status page for this draft is: https://datatracker.ietf.org/doc/draft-ietf-regext-data-escrow/ There are also htmlized versions available at: https://tools.ietf.org/html/draft-ietf-regext-data-escrow-10 https://datatracker.ietf.org/doc/html/draft-ietf-regext-data-escrow-10 A diff from the previous version is available at: https://www.ietf.org/rfcdiff?url2=draft-ietf-regext-data-escrow-10 Please note that it may take a couple of minutes from the time of submission until the htmlized version and diff are available at tools.ietf.org. Internet-Drafts are also available by anonymous FTP at: ftp://ftp.ietf.org/internet-drafts/ ___ regext mailing list regext@ietf.org https://www.ietf.org/mailman/listinfo/regext
Re: [regext] [Ext] Benjamin Kaduk's Discuss on draft-ietf-regext-data-escrow-07: (with DISCUSS and COMMENT)
Thank you, Ben, Text added in the latest version of the draft: https://tools.ietf.org/rfcdiff?url2=draft-ietf-regext-data-escrow-10.txt Regards, Gustavo On 5/30/20, 11:39, "Benjamin Kaduk" wrote: Hi Gustavo, I think that proposed text will work; please go ahead and include it in the next vesrion of the draft. Sorry for the slow response, Ben On Fri, May 22, 2020 at 07:26:03PM +, Gustavo Lozano wrote: > Thank you, Ben, > > I think that the last sentence in the following proposed text for the second paragraph of the security section could attend your second discuss point: > > Depending on local policies, some elements, or, most likely, the whole deposit will be considered confidential. As such, the parties SHOULD take all the necessary precautions such as encrypting the data at rest and in transit to avoid inadvertent disclosure of private data. Regardless of the precautions taken by the parties regarding data at rest and in transit, authentication credentials MUST NOT be escrowed. > > If you agree that this covers your feedback, I will include it in the next version of the draft. > > Regards, > Gustavo > > On 5/21/20, 15:07, "Benjamin Kaduk" wrote: > > Hi Gustavo, > > Thanks for the updates! > I think the mention of the ICANN base agreement in the introduction serves > to give some examples of well-reviewed procedures for escrow, and is enough > to resolve my first discuss point. > > I don't see a whole lot that looks relevant to my second point about > (potential) escrow of authentication credentials, though. If I remember > correctly we discussed that the intent was for those to not be included in > the escrow dumps, but I don't remember whether we talked about putting any > clarifying text in the document. > > Thanks, > > Ben > > On Wed, May 13, 2020 at 06:45:38PM +, Gustavo Lozano wrote: > > Hi Benjamin, > > > > I think that the latest version of the draft covers your feedback. > > > > Here are the differences between 07 and 08, and 08 and 09: > > https://urldefense.proofpoint.com/v2/url?u=https-3A__tools.ietf.org_rfcdiff-3Furl2-3Ddraft-2Dietf-2Dregext-2Ddata-2Descrow-2D08.txt&d=DwIDaQ&c=FmY1u3PJp6wrcrwll3mSVzgfkbPSS6sJms7xcl4I5cM&r=VbweciUcwYQpIOZDSxl0ezGd1hGDtd-0BvgAgfmwfE0&m=VDCiJAnAswUQ4avJ55sPxmYR4hLKtN9JoiudmZhps0M&s=ilArbwqLMrfNyTwmcvU6fk9KseAXlQKxRccN-kUQhOo&e= > > https://urldefense.proofpoint.com/v2/url?u=https-3A__tools.ietf.org_rfcdiff-3Furl2-3Ddraft-2Dietf-2Dregext-2Ddata-2Descrow-2D09.txt&d=DwIDaQ&c=FmY1u3PJp6wrcrwll3mSVzgfkbPSS6sJms7xcl4I5cM&r=VbweciUcwYQpIOZDSxl0ezGd1hGDtd-0BvgAgfmwfE0&m=VDCiJAnAswUQ4avJ55sPxmYR4hLKtN9JoiudmZhps0M&s=iNhLzs77vPa3t0ibX42lkY967mU9pwYMkPEIU1slI1U&e= > > > > Thoughts? > > > > Thank you, > > Gustavo > > > > On 4/20/20, 18:05, "Benjamin Kaduk" wrote: > > > > Hi Gustavo, > > > > On Thu, Apr 16, 2020 at 10:26:40PM +, Gustavo Lozano wrote: > > > Thank you, Benjamin, > > > > > > Comments inline, prefixed with GL -. > > > > > > Regards, > > > Gustavo > > > > > > On 4/8/20, 09:01, "Benjamin Kaduk via Datatracker" wrote: > > > > > > Benjamin Kaduk 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=VbweciUcwYQpIOZDSxl0ezGd1hGDtd-0BvgAgfmwfE0&m=XLPt-K5FLKU1oce9PiZyutUV1_UJqbd348-sDIlLCD8&s=9EVCPSTvj9RgWF9Z3e7HBLsbaPg6R2CPwDhbFPM8sEM&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=VbweciUcwYQpIOZDSxl0ezGd1hGDtd-0BvgAgfmwfE0&m=XLPt-K5FLKU1oce9PiZyutUV1_UJqbd348-sDIlLCD8&s=Avsh9DG_m3aLijuq_I7ulh5IMkYG78XIOq1Puctc2ZU&e= > > > > > > > > > > > > --
[regext] I-D Action: draft-ietf-regext-simple-registration-reporting-00.txt
A New Internet-Draft is available from the on-line Internet-Drafts directories. This draft is a work item of the Registration Protocols Extensions WG of the IETF. Title : Simple Registration Reporting Authors : Joseph Yee James Galvin Filename: draft-ietf-regext-simple-registration-reporting-00.txt Pages : 16 Date: 2020-06-01 Abstract: Domain name registries and registrars report to each other by sharing bulk information through files. This document creates two IANA registries to create a standard reporting mechanism between domain name registries and registrars. The first IANA registry lists standard data elements and their syntax for inclusion in the files. The second IANA registry lists standard reports based on the standard data elements. Each report is a file formatted as a CSV file. The advantage of this reporting mechanism is that reports, each file, can be imported by recipients without any prior knowledge of their contents, although reporting is enhanced with a minimum of knowledge about the files. The mechanism for the transmission and reception of the files is a matter of local policy. The IETF datatracker status page for this draft is: https://datatracker.ietf.org/doc/draft-ietf-regext-simple-registration-reporting/ There are also htmlized versions available at: https://tools.ietf.org/html/draft-ietf-regext-simple-registration-reporting-00 https://datatracker.ietf.org/doc/html/draft-ietf-regext-simple-registration-reporting-00 Please note that it may take a couple of minutes from the time of submission until the htmlized version and diff are available at tools.ietf.org. Internet-Drafts are also available by anonymous FTP at: ftp://ftp.ietf.org/internet-drafts/ ___ regext mailing list regext@ietf.org https://www.ietf.org/mailman/listinfo/regext
Re: [regext] CALL FOR ADOPTION: draft-yee-regext-simple-registration-reporting
Thanks Antoin. New draft submitted. Will actively seek for a document shepherd. And many thanks to all who support this draft. Best, Joseph On Fri, May 29, 2020 at 9:15 AM Antoin Verschuren wrote: > Dear WG, > > The call for adoption for draft-yee-regext-simple-registration-reporting > ended 22 May 2020. > The results were: > Support: 4 valid > Object: 0 > > The chairs considder this draft adopted by the REGEXT WG. > > Request to the authors: > > Now that the draft is adopted, you must look for a document shepherd for > this document. If you have not yet found someone that has volunteered to be > document shepherd for your document, please solicit for a volunteer in the > working group. Working group members are encouraged to volunteer as > document shepherd for this document. Being a shepherd is a great > opportunity! > > Please submit a new version of the draft with the following name: > draft-ietf-regext-simple-registration-reporting-00 > > The co-chair has already pre-approved this document so once submitted it > will be automaticaly accepted as a WG document. > > Your co-chair Antoin > > > > > > > > Op 8 mei 2020, om 19:40 heeft Owen Smigelski > het volgende geschreven: > > +1 > > On May 8, 2020, at 8:44 AM, Joseph Yee wrote: > > +1 > > -Joseph > > On Fri, May 8, 2020 at 11:04 AM Mario Loffredo > wrote: > >> +1 >> >> Mario >> >> Il 08/05/2020 15:36, Antoin Verschuren ha scritto: >> > Dear working group, >> > >> > We will soon have a slot available in our milestone list for a new >> EPP/Registry document. >> > The chairs are not aware of any outstanding adoption requests other >> than this one. >> > >> > This is a formal adoption request for Simple Registration Reporting: >> > >> https://datatracker.ietf.org/doc/draft-yee-regext-simple-registration-reporting/ >> > >> > Please review this draft to see if you think it is suitable for >> adoption by REGEXT, and comment to the list, clearly stating your view. >> > >> > Please also indicate if you are willing to contribute text, review >> text, or be a document shepherd. >> > >> > This call for adoption ends Friday, 22 May 2020. >> > >> > If there are no objections, and we receive enough consensus for >> adoption, the chairs will consider this document adopted. >> > >> > Thanks, >> > >> > Your REGEXT co-chairs Jim and Antoin >> > >> > >> > >> > >> > >> > >> > ___ >> > regext mailing list >> > regext@ietf.org >> > https://www.ietf.org/mailman/listinfo/regext >> >> -- >> Dr. Mario Loffredo >> Systems and Technological Development Unit >> Institute of Informatics and Telematics (IIT) >> National Research Council (CNR) >> via G. Moruzzi 1, I-56124 PISA, Italy >> Phone: +39.0503153497 >> Mobile: +39.3462122240 >> Web: http://www.iit.cnr.it/mario.loffredo >> #pleasestayathome >> >> ___ >> regext mailing list >> regext@ietf.org >> https://www.ietf.org/mailman/listinfo/regext >> > ___ > regext mailing list > regext@ietf.org > https://www.ietf.org/mailman/listinfo/regext > > > > ___ > regext mailing list > regext@ietf.org > https://www.ietf.org/mailman/listinfo/regext > ___ regext mailing list regext@ietf.org https://www.ietf.org/mailman/listinfo/regext
[regext] Benjamin Kaduk's No Objection on draft-ietf-regext-data-escrow-10: (with COMMENT)
Benjamin Kaduk has entered the following ballot position for draft-ietf-regext-data-escrow-10: 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://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-data-escrow/ -- COMMENT: -- Thank you for the discussion and updates in response to my discuss points! ___ regext mailing list regext@ietf.org https://www.ietf.org/mailman/listinfo/regext
Re: [regext] [Ext] Benjamin Kaduk's Discuss on draft-ietf-regext-data-escrow-07: (with DISCUSS and COMMENT)
Excellent; I've updated my ballot position. (It looks like we are still waiting for Alissa to look at the updates, though.) -Ben On Mon, Jun 01, 2020 at 06:51:21PM +, Gustavo Lozano wrote: > Thank you, Ben, > > Text added in the latest version of the draft: > https://tools.ietf.org/rfcdiff?url2=draft-ietf-regext-data-escrow-10.txt > > Regards, > Gustavo > > On 5/30/20, 11:39, "Benjamin Kaduk" wrote: > > Hi Gustavo, > > I think that proposed text will work; please go ahead and include it in > the > next vesrion of the draft. > > Sorry for the slow response, > > Ben > > On Fri, May 22, 2020 at 07:26:03PM +, Gustavo Lozano wrote: > > Thank you, Ben, > > > > I think that the last sentence in the following proposed text for the > second paragraph of the security section could attend your second discuss > point: > > > > Depending on local policies, some elements, or, most likely, the whole > deposit will be considered confidential. As such, the parties SHOULD take all > the necessary precautions such as encrypting the data at rest and in transit > to avoid inadvertent disclosure of private data. Regardless of the > precautions taken by the parties regarding data at rest and in transit, > authentication credentials MUST NOT be escrowed. > > > > If you agree that this covers your feedback, I will include it in the > next version of the draft. > > > > Regards, > > Gustavo > > > > On 5/21/20, 15:07, "Benjamin Kaduk" wrote: > > > > Hi Gustavo, > > > > Thanks for the updates! > > I think the mention of the ICANN base agreement in the introduction > serves > > to give some examples of well-reviewed procedures for escrow, and > is enough > > to resolve my first discuss point. > > > > I don't see a whole lot that looks relevant to my second point about > > (potential) escrow of authentication credentials, though. If I > remember > > correctly we discussed that the intent was for those to not be > included in > > the escrow dumps, but I don't remember whether we talked about > putting any > > clarifying text in the document. > > > > Thanks, > > > > Ben > > > > On Wed, May 13, 2020 at 06:45:38PM +, Gustavo Lozano wrote: > > > Hi Benjamin, > > > > > > I think that the latest version of the draft covers your feedback. > > > > > > Here are the differences between 07 and 08, and 08 and 09: > > > > https://urldefense.proofpoint.com/v2/url?u=https-3A__tools.ietf.org_rfcdiff-3Furl2-3Ddraft-2Dietf-2Dregext-2Ddata-2Descrow-2D08.txt&d=DwIDaQ&c=FmY1u3PJp6wrcrwll3mSVzgfkbPSS6sJms7xcl4I5cM&r=VbweciUcwYQpIOZDSxl0ezGd1hGDtd-0BvgAgfmwfE0&m=VDCiJAnAswUQ4avJ55sPxmYR4hLKtN9JoiudmZhps0M&s=ilArbwqLMrfNyTwmcvU6fk9KseAXlQKxRccN-kUQhOo&e= > > > > > https://urldefense.proofpoint.com/v2/url?u=https-3A__tools.ietf.org_rfcdiff-3Furl2-3Ddraft-2Dietf-2Dregext-2Ddata-2Descrow-2D09.txt&d=DwIDaQ&c=FmY1u3PJp6wrcrwll3mSVzgfkbPSS6sJms7xcl4I5cM&r=VbweciUcwYQpIOZDSxl0ezGd1hGDtd-0BvgAgfmwfE0&m=VDCiJAnAswUQ4avJ55sPxmYR4hLKtN9JoiudmZhps0M&s=iNhLzs77vPa3t0ibX42lkY967mU9pwYMkPEIU1slI1U&e= > > > > > > > Thoughts? > > > > > > Thank you, > > > Gustavo > > > > > > On 4/20/20, 18:05, "Benjamin Kaduk" wrote: > > > > > > Hi Gustavo, > > > > > > On Thu, Apr 16, 2020 at 10:26:40PM +, Gustavo Lozano > wrote: > > > > Thank you, Benjamin, > > > > > > > > Comments inline, prefixed with GL -. > > > > > > > > Regards, > > > > Gustavo > > > > > > > > On 4/8/20, 09:01, "Benjamin Kaduk via Datatracker" > wrote: > > > > > > > > Benjamin Kaduk 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=VbweciUcwYQpIOZDSxl0ezGd1hGDtd-0BvgAgfmwfE0&m=XLPt-K5FLKU1oce9PiZyutUV1_UJqbd348-sDIlLCD8&s=9EVCPSTvj9RgWF9Z3e7HBLsbaPg6R2CPwDhbFPM8sEM&e= > > > > > for more information about IESG DISCUSS and COMMENT > positions. > > > > > > > > > > > > The document, along with other ballot positions, can be > found here: > >
