[RDS-WHOIS2-RT] ICANN Proposal to adjust scope of RDS-WHOIS2-RT
Alan Greenberg
alan.greenberg at mcgill.ca
Thu May 17 14:57:31 UTC 2018
I don't think it is a Bylaws problem because they
do add that we have to agree. Although I suspect
we would agree, although with a lot of bad
feelings, but I did ask Larisa what wuld happen
if we did NOT agree. Would we still have funding
and support to continue? And she said they had not thought about that...
I agree that this is a diversion that we could
have done without and it will take resources, at
least at the leadership level.
Alan
At 17/05/2018 09:09 AM, Cathrin.BAUER-BULST at ec.europa.eu wrote:
>I think this raises a bylaws point. This is a
>review mandated by the Bylaws, which even set a
>time frame for its regular occurrence. Now
>putting it up for Community discussion whether
>we're having this review, whether it should
>change its scope or whether it should stop for a
>while, essentially puts the bylaws requirement
>up for Community discussion. We as individuals
>may serve "at the pleasure of the community" but
>the process itself is not at the disposal of any
>public consultation, so I believe this whole
>exercise is legally on not very sound footing.
>
>And this idea that we then agree or disagree
>with the outcome of the public consultation
>seems courageous to me, in the "Yes Minister"
>sense so what is the point off the exercise if
>we then just get to ignore the Community view if
>we so please? To help us make an informed
>decision on options that we never thought of
>ourselves or were invited to have a say in in
>the first place but that someone has
>benevolently designed in an effort to reduce our
>workload? I think we should participate in the
>webinar (we may be the only ones given that
>other RDS/WHOIS mess) and explain this.
>
>But I should be working on surveys instead of
>commenting on this mess
that much for workload reduction.
>
>Best regards
>Cathrin
>
>
>
>From: RDS-WHOIS2-RT
>[mailto:rds-whois2-rt-bounces at icann.org] On Behalf Of Dmitry Belyavsky
>Sent: Thursday, May 17, 2018 11:25 AM
>To: Alan Greenberg
>Cc: RDS WHOIS2-RT List
>Subject: Re: [RDS-WHOIS2-RT] ICANN Proposal to adjust scope of RDS-WHOIS2-RT
>
>Dear Alan,
>
>I think we should continue our work as planned.
>
>I agree with Chris that the RT should respond to
>the call to the comments ASAP.
>
>On Wed, May 16, 2018 at 8:54 PM, Alan Greenberg
><<mailto:alan.greenberg at mcgill.ca>alan.greenberg at mcgill.ca> wrote:
>I presume then that you and others are willing
>to keep working and meet our deadline of a draft
>report at or soon after the July F2F.
>
>Alan
>
>
>At 16/05/2018 10:23 AM, Volker Greimann wrote:
>
>
>Hi Alan,
>
>I absolutely agree that it is strange that ICANN
>seems to want to pause this without consulting
>us first. But as this is the cards we have been
>dealt, we need to figure out how to play them
>and in this case I vote for following the community consensus, if any.
>
>As for Monday, it is a public holiday that I will be travelling on.
>
>Best,
>
>Volker
>
>Am 16.05.2018 um 16:08 schrieb Alan Greenberg:
>
>Volker,
>
>Of course we serve at the pleasure of the community.
>
>The question is process and timing. That this
>was done with no consultation with us, I find
>strange. But the really difficult part is that
>we are being told to keep on working (and I have
>confirmed that this is the intent) with a target
>of having a draft report complete just after the
>July F2F, and at THAT point, we may be told to
>scrap part of what we have been working on
>between now an then, or put the entire project
>on hold for some indeterminate time, and when it
>resumes it may be with a different team and much
>of the work will have to be redone.
>
>We will discuss this further at the Monday
>meeting, and for those who will not be there,
>your input is appreciated ahead of time.
>
>Susan has suggested that we go back to our appointing groups for their input.
>
>Alan
>
>
>
>
>At 16/05/2018 06:03 AM, Volker Greimann wrote:
>
>
>
>
>
>We serve at the pleasure of
>
>the community, so I would not object to any
>
>consensus position either way. While a) is the most logical choice,
>
>preserving most of our work efforts so far, the others also have some
>
>merit due to the changes ahead. And as ICANN has just thrown another
>
>curve-ball in the form of the proposed temporary specification, more
>
>change seems to be on the horizon, which could further outdate our work
>
>product.
>
>
>
>Best,
>
>
>
>Volker
>
>
>
>
>
>Am 16.05.2018 um 04:30 schrieb Alan Greenberg:
>
> > I call your attention to a Public Comment (PC) launched yesterday
>
> > asking for input on alternatives to alter the RDS-WHOIS2-RT Scope
>
>and
>
> > plans (as well possible changes to the not yet started ATRT3) -
>
> >
>
>
>
>
>
><https://www.icann.org/public-comments/specific-reviews-short-term-timeline-2018-05-14-en>https://www.icann.org/public-comments/specific-reviews-short-term-timeline-2018-05-14-en
>
><https://www.icann.org/public-comments/specific-reviews-short-term-timeline-2018-05-14-en>.
>
> >
>
> > I proposes three possible scenarios for our RT:
>
> >
>
> > a) Proceeds as planned;
>
> >
>
> > b) reduce scope to just an analysis of the WHOIS1-RT
>
>Recommendations;
>
> >
>
> > c) pause the review entirely for some as yet to be determined time.
>
> >
>
> > If recommended by the community, b) and c) would require our
>
> > agreement. The implications of a community recommendation that we
>
> > refused to agree with are not known. If there is a pause, it is not
>
> > clear when the unpause would happen and to what extent it would be
>
>the
>
> > same team moving forward.
>
> >
>
> > The PC ends on 06 July 2018 and the report on input received is due
>
>on
>
> > 23 July 2018, a few days before we are currently planning to meet in
>
> > Brussels to close-to-finalize our report.
>
> >
>
> > Although the PC was issues yesterday, neither I nor Susan and
>
>Cathrin
>
> > had any prior knowledge of it and in fact we only heard of it
>
>today.
>
> >
>
> > We have initiated discussions with MSSI on exactly what this means
>
>and
>
> > will get back when I have a better understanding.
>
> >
>
> > Alan
>
> >
>
> > _______________________________________________
>
> > RDS-WHOIS2-RT mailing list
>
> >
>
>
>
><https://mm.icann.org/mailman/listinfo/rds-whois2-rt>RDS-WHOIS2-RT
>at icann.org
>
> >
>
>
>
>
>
>https://mm.icann.org/mailman/listinfo/rds-whois2-rt
>
>
>
>--
>
>Bei weiteren Fragen stehen wir Ihnen gerne zur Verfügung.
>
>
>
>Mit freundlichen GrüÃen,
>
>
>
>Volker A. Greimann
>
>- Rechtsabteilung -
>
>
>
>Key-Systems GmbH
>
>Im Oberen Werk 1
>
>66386 St. Ingbert
>
>Tel.: +49 (0) 6894 - 9396 901
>
>Fax.: +49 (0) 6894 - 9396 851
>
>Email:
>
><https://mm.icann.org/mailman/listinfo/rds-whois2-rt>vgreimann
>
><https://mm.icann.org/mailman/listinfo/rds-whois2-rt>at key-systems.net
>
>
>
>Web:
>
>
>
>
>
><http://www.key-systems.net/>www.key-systems.net /
>
>www.RRPproxy.net
>
>
>
>
>
><http://www.domaindiscount24.com/>www.domaindiscount24.com /
>
>
>
>
>
>www.BrandShelter.com
>
>
>
>Folgen Sie uns bei Twitter oder werden Sie unser Fan bei Facebook:
>
>
>
>
>
><http://www.facebook.com/KeySystems>www.facebook.com/KeySystems
>
>
>
>
>
>www.twitter.com/key_systems
>
>
>
>Geschäftsführer: Alexander Siffrin
>
>Handelsregister Nr.: HR B 18835 - Saarbruecken
>
>Umsatzsteuer ID.: DE211006534
>
>
>
>Member of the KEYDRIVE GROUP
>
><http://www.keydrive.lu/>www.keydrive.lu
>
>
>
>Der Inhalt dieser Nachricht ist vertraulich und nur für den angegebenen
>
>Empfänger bestimmt. Jede Form der Kenntnisgabe, Veröffentlichung oder
>Weitergabe an Dritte durch den Empfänger ist unzulässig. Sollte diese
>
>Nachricht nicht für Sie bestimmt sein, so bitten wir Sie, sich mit uns
>
>per E-Mail oder telefonisch in Verbindung zu setzen.
>
>
>
>--------------------------------------------
>
>
>
>Should you have any further questions, please do not hesitate to contact
>
>us.
>
>
>
>Best regards,
>
>
>
>Volker A. Greimann
>
>- legal department -
>
>
>
>Key-Systems GmbH
>
>Im Oberen Werk 1
>
>66386 St. Ingbert
>
>Tel.: +49 (0) 6894 - 9396 901
>
>Fax.: +49 (0) 6894 - 9396 851
>
>Email:
>
><https://mm.icann.org/mailman/listinfo/rds-whois2-rt>vgreimann
>
><https://mm.icann.org/mailman/listinfo/rds-whois2-rt>at key-systems.net
>
>
>
>Web:
>
>
>
>
>
><http://www.key-systems.net/>www.key-systems.net /
>
>www.RRPproxy.net
>
>
>
>
>
><http://www.domaindiscount24.com/>www.domaindiscount24.com /
>
>
>
>
>
>www.BrandShelter.com
>
>
>
>Follow us on Twitter or join our fan community on Facebook and stay
>
>updated:
>
>
>
>
>
><http://www.facebook.com/KeySystems>www.facebook.com/KeySystems
>
>
>
>
>
>www.twitter.com/key_systems
>
>
>
>CEO: Alexander Siffrin
>
>Registration No.: HR B 18835 - Saarbruecken
>
>V.A.T. ID.: DE211006534
>
>
>
>Member of the KEYDRIVE GROUP
>
><http://www.keydrive.lu/>www.keydrive.lu
>
>
>
>This e-mail and its attachments is intended only for the person to whom
>
>it is addressed. Furthermore it is not permitted to publish any content
>
>of this email. You must not use, disclose, copy, print or rely on this
>
>e-mail. If an addressing or transmission error has misdirected this
>
>e-mail, kindly notify the author by replying to this e-mail or
>
>contacting
>
>us by telephone.
>
>
>--
>
>Bei weiteren Fragen stehen wir Ihnen gerne zur Verfügung.
>
>
>
>Mit freundlichen GrüÃen,
>
>
>
>Volker A. Greimann
>
>- Rechtsabteilung -
>
>
>
>Key-Systems GmbH
>
>Im Oberen Werk 1
>
>66386 St. Ingbert
>
>Tel.: +49 (0) 6894 - 9396 901
>
>Fax.: +49 (0) 6894 - 9396 851
>
>Email:
>
><mailto:vgreimann at key-systems.net>vgreimann at key-systems.net
>
>
>
>Web: <http://www.key-systems.net>www.key-systems.net /
>
>www.RRPproxy.net
>
><http://www.domaindiscount24.com>www.domaindiscount24.com /
>
>
>
>www.BrandShelter.com
>
>
>
>Folgen Sie uns bei Twitter oder werden Sie unser Fan bei Facebook:
>
>
>
><http://www.facebook.com/KeySystems>www.facebook.com/KeySystems
>
>
>
>www.twitter.com/key_systems
>
>
>
>Geschäftsführer: Alexander Siffrin
>
>Handelsregister Nr.: HR B 18835 - Saarbruecken
>
>Umsatzsteuer ID.: DE211006534
>
>
>
>Member of the KEYDRIVE GROUP
>
><http://www.keydrive.lu>www.keydrive.lu
>
>
>
>Der Inhalt dieser Nachricht ist vertraulich und nur für den angegebenen
>
>Empfänger bestimmt. Jede Form der Kenntnisgabe, Veröffentlichung oder
>
>Weitergabe an Dritte durch den Empfänger ist unzulässig. Sollte diese
>
>Nachricht nicht für Sie bestimmt sein, so bitten wir Sie, sich mit uns
>
>per E-Mail oder telefonisch in Verbindung zu setzen.
>
>
>
>--------------------------------------------
>
>
>
>Should you have any further questions, please do not hesitate to contact
>
>us.
>
>
>
>Best regards,
>
>
>
>Volker A. Greimann
>
>- legal department -
>
>
>
>Key-Systems GmbH
>
>Im Oberen Werk 1
>
>66386 St. Ingbert
>
>Tel.: +49 (0) 6894 - 9396 901
>
>Fax.: +49 (0) 6894 - 9396 851
>
>Email:
>
><mailto:vgreimann at key-systems.net>vgreimann at key-systems.net
>
>
>
>Web: <http://www.key-systems.net>www.key-systems.net /
>
>www.RRPproxy.net
>
><http://www.domaindiscount24.com>www.domaindiscount24.com /
>
>
>
>www.BrandShelter.com
>
>
>
>Follow us on Twitter or join our fan community on Facebook and stay
>
>updated:
>
>
>
><http://www.facebook.com/KeySystems>www.facebook.com/KeySystems
>
>
>
>www.twitter.com/key_systems
>
>
>
>CEO: Alexander Siffrin
>
>Registration No.: HR B 18835 - Saarbruecken
>
>V.A.T. ID.: DE211006534
>
>
>Member of the KEYDRIVE GROUP
>
><http://www.keydrive.lu>www.keydrive.lu
>
>
>
>This e-mail and its attachments is intended only for the person to whom
>
>it is addressed. Furthermore it is not permitted to publish any content
>
>of this email. You must not use, disclose, copy, print or rely on this
>
>e-mail. If an addressing or transmission error has misdirected this
>
>e-mail, kindly notify the author by replying to this e-mail or contacting
>
>us by telephone.
>
>
>
>
>
>
>
>_______________________________________________RDS-WHOIS2-RT mailing list
><mailto:RDS-WHOIS2-RT at icann.org>RDS-WHOIS2-RT at icann.org
>https://mm.icann.org/mailman/listinfo/rds-whois2-rt
>
>
>
>--
>SY, Dmitry Belyavsky
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://mm.icann.org/pipermail/rds-whois2-rt/attachments/20180517/854ea08a/attachment-0001.html>
More information about the RDS-WHOIS2-RT
mailing list