[TSG-Access-RD] Notes from TSG-Access-RD Meeting #11 - 5 Mar 2019

Wed Mar 6 17:57:17 UTC 2019

I just finished reviewing the executive summary, and I believe there is no need for any change.

Best Regards,
Jorge Cano P.

-----Original Message-----
From: TSG-Access-RD [mailto:tsg-access-rd-bounces at icann.org] On Behalf Of Andrew Newton
Sent: Wednesday, March 06, 2019 8:29 AM
To: Hollenbeck, Scott <shollenbeck at verisign.com>
Cc: tsg-access-rd at icann.org
Subject: Re: [TSG-Access-RD] Notes from TSG-Access-RD Meeting #11 - 5 Mar 2019

The exec summary is done. Also the system requirements in the preso are done.

-andy

On Wed, Mar 6, 2019 at 8:47 AM Hollenbeck, Scott via TSG-Access-RD <tsg-access-rd at icann.org> wrote:
>
> I’ve completed my edits and reviews. I also took a crack at adding definitions for some of the terms that were added to the new “Other Terms” section.
>
>
>
> Scott
>
>
>
> From: TSG-Access-RD <tsg-access-rd-bounces at icann.org> On Behalf Of
> Eleeza Agopian
> Sent: Tuesday, March 5, 2019 6:19 PM
> To: Diana Middleton <diana.middleton at icann.org>; Technical Study Group
> RD <tsg-access-rd at icann.org>
> Subject: [EXTERNAL] Re: [TSG-Access-RD] Notes from TSG-Access-RD
> Meeting #11 - 5 Mar 2019
>
>
>
> Dear team,
>
>
>
> Following up on my action items:
>
> I wanted to let you know that I have resolved all of the edits/comments in the document, including standardizing formatting for RDAP Proxy, re-numbering sections and resolving comments that were addressed on today’s call.
> The outstanding comments have been assigned to the appropriate owners on the team.
> The only section with outstanding edits is the conclusion, which will be reviewed again by Murray, Jorge and Scott.
> In addition, after reviewing the document again and noting that there are several undefined terms in the document that may make it difficult for a first-time reader, Gustavo, Francisco and I started to compile them in a new section 2, under “Conventions Used in this Document” as “Other Terms.” To the extent some of the terms are already defined (i.e. Section 7, preceding the actor model descriptions), we will include those definitions in Section 2. For those where there are undefined terms (i.e. in 9.2), we will include the term in Section 2, but will note that undefined terms will be fully defined in the final iteration of this model.
>
> Thank you,
>
> Eleeza
>
>
>
> Eleeza Agopian
>
> Strategic Planning & Initiatives Senior Manager
>
> ICANN
>
> 12025 Waterfront Drive, Suite 300
>
> Los Angeles, CA  90094
>
> +1 310 418 8985 mobile
>
> eleeza.agopian at icann.org
>
>
>
> From: TSG-Access-RD <tsg-access-rd-bounces at icann.org> On Behalf Of
> Diana Middleton
> Sent: Tuesday, March 5, 2019 1:30 PM
> To: Technical Study Group RD <tsg-access-rd at icann.org>
> Subject: [TSG-Access-RD] Notes from TSG-Access-RD Meeting #11 - 5 Mar
> 2019
>
>
>
> Dear all,
>
>
>
> See below for notes from meeting #11.  Please let me know if you have any questions or concerns.
>
>
>
> Best,
>
> Diana
>
>
>
>
>
> **************************
>
>
>
> Technical Study Group on Access to Non-Public Registration Data
> Meeting #11
>
> 5 March 2019
>
> 0900 PST / 1200 EST / 1700 UTC
>
>
>
> Attendees:  Steve Crocker, Scott Hollenbeck, Jorge Cano, Andy Newton,
> Jody Kolker, Ram Mohan, Tomofumi Okubo, Murray Kucherawy, Benedict
> Addis, Diana Middleton, Eleeza Agopian, Francisco Arias, Gustavo
> Lozano, Yvette Guigneaux
>
>
>
> Apologies:  John Crain, Gavin Brown
>
>
>
> During this call we discussed the following:
>
>
>
> (1) Finalizing the Draft Technical Model for Access to Non-Public Registration Data, including:
>
> Editing Assumption #9 in the Assumption section Removing Assumption
> #11 in the Assumption section Adding system components IPv4 and IPv6
> in 1(b) of the System Requirements section Changing “coordinating
> party” to “ICANN” in instances when just referring to ICANN (or other
> identified party) in the entire document Add reference to RFC 7525 in
> 1(d) of the System Requirements section Discussion of the term “must”
> in 6(c) of the System Requirements section Discussion of the term
> “must” in 7(a) of the System Requirements section Adjustment of
> language in 8(c) of the System Requirements section Adjustment of
> language “must” to “should” in 8(d) of the System Requirements section
> Review of edits in Actor Models 1, 2, 3, & 4 in the Actor Models
> section Review of language in the Proposed Solution section Discussion
> of adding Glossary section to document Edits of text in 8.2 of the
> Proposed Solution section Discussion of title of the Considerations
> section Discussion of term “must” in 9.2 of the Considerations section
> Discussion of the legal language in 9.7 of the Considerations section
> Removal of the word “generally” in the second paragraph of the
> Proposed Solution section Edits of text in 8.1 of the Proposed
> Solution section
>
> (2) Review of Kobe plans including session agenda, community
> discussions speakers
>
> (3) Review of slide deck
>
>
>
> We have the following action items:
>
> Eleeza to review document to ensure replacement of “RDAP Proxy” with “RDAP Gateway”
> Eleeza to change “coordinating party” to “ICANN” in instances when
> just referring to ICANN (or other identified party) in the System
> Requirements section Eleeza add reference to RFC 7525 Francisco to
> edit placement issue of edits in paragraph 1 of the Proposed Solution
> section of the document Eleeza to add footnote to each instance of the
> term “validates” in #2, #3, & #4 in 8.2 of the Proposed Solution
> section Eleeza to add footnote to the term “indicates” on #4 in 8.2 of
> the Proposed Solution section Scott to update text in 8.1 of the
> Proposed Solution section Murray to author/edit Conclusion, Jorge &
> Scott to review in the next 24 hours Andy/Scott to author/edit
> Executive Summary, Jody, Jorge, Tomofumi to review in the next 24 hours (does it actually reflect what we are trying to accomplish) Eleeza to clean up document’s remaining comments Eleeza/Diana to notify Gavin of his role in the session re: Considerations Diana to draft note to Tijani regarding regrets due to conflict and offer written update?
> Eleeza to make two decks, full scale + smaller (6-7 slide) deck for
> community groups Jody/Jorge to add Considerations slide to the deck
> Full Group: Complete any review of the slide deck by Thursday
>
>
>
>

Este mensaje contiene información confidencial y se entiende dirigido y para uso exclusivo del destinatario. Si recibes este mensaje y no eres el destinatario por favor elimínalo, ya que difundir, revelar, copiar o tomar cualquier acción basada en el contenido está estrictamente prohibido. Network Information Center, S.A. de C.V., ubicado en Ave. Eugenio Garza Sada 427 L4-6 Col. Altavista, Monterrey, México, C.P. 64840 recaba tus datos personales necesarios para: la prestación, estudio, análisis y mejora del servicio, la realización de comunicaciones y notificaciones; la transferencia y publicación en los casos aplicables; el cumplimiento de la relación existente; así como para la prevención o denuncia en la comisión de ilícitos. Si eres colaborador o candidato a colaborador de NIC México, tus datos serán utilizados para: la creación y administración de tu perfil como profesionista; el otorgamiento de herramientas de trabajo; la realización de estudios; el otorgamiento de programas y beneficios para mejorar tu desarrollo profesional; la gestión y administración de servicios de pago y/o nómina; así como para contacto y/o notificaciones. Si participas en promociones o en estudios podrás dejar de participar. Para mayor información revisa el Aviso de Privacidad<http://www.nic.mx/es/NicMx.AvisosDePrivacidad>.

This message contains confidential information and is intended only for the individual named. If you are not the named addressee please delete it, since the dissemination, distribuition, copy or taking any action in reliance on the contents is strictly prohibited. Network Information Center, S.A. de C.V., located on Av. Eugenio Garza Sada 427 L4-6, Col. Altavista, Monterrey, Mexico, CP 64840 collects your personal data which is necessary to: provide, research, analyze and improve the service; send communications and notices; transfer and publish your personal data when applicable; fulfill the existing relationship; prevent or inform in the commission of unlawful acts or events. If the data is processed in your quality of candidate or collaborator of NIC Mexico, the purpose of treatment is to: create and manage your profile as a professional; provide you with working tools; conduct studies; grant benefits and programs to enhance your professional development; manage and administrate payment services and/or payroll; as well as to contact you. If you participate in promotions or surveys you may stop or quit your participation at any time. For more information read the Privacy Note<http://www.nic.mx/es/NicMx.AvisosDePrivacidad>.