[ALAC] RAA 3.7.8

Carlton Samuels carlton.samuels at gmail.com
Wed Mar 27 17:19:19 UTC 2013


The way I suggested to deal with Clause 3.7.8 concerns on the wiki might be
cleaner.
-Carlton

==============================
Carlton A Samuels
Mobile: 876-818-1799
*Strategy, Planning, Governance, Assessment & Turnaround*
=============================


On Wed, Mar 27, 2013 at 12:04 PM, Alan Greenberg
<alan.greenberg at mcgill.ca>wrote:

> Sorry, forgot one thing.
>
> At 27/03/2013 01:01 PM, Alan Greenberg wrote:
> >At 27/03/2013 12:20 PM, Evan Leibovitch wrote:
> >>On 27 March 2013 11:47, Garth Bruen at KnujOn
> >><<mailto:gbruen at knujon.com>gbruen at knujon.com> wrote:
> >>
> >>Change the WHOIS Accuracy Specification #5 from:
> >>“Upon the occurrence of a Registered Name Holder's willful provision
> >>of inaccurate or unreliable WHOIS information…â€
> >>To:
> >>“Upon the REPORT OR DISCOVERY of a Registered Name Holder's willful
> >>provision of inaccurate or unreliable WHOIS information…â€
> >>
> >>
> >>
> >>Agreed, though I think that "report" is
> >>sufficient. A discovery that is unreported can't be of much help.
> >
> >See my e-mail just sent which explains why I
> >think that "report" is overly broad.
>
> Don't agree about omitting discovery. That covers
> the case where a registrar "discovers" the
> problem, likely due to one of the required checks
> mandated in the earlier sections of the
> specification. It does not make sense for a
> registrar to have to report the problem to
> itself, yet the predicate part of this sentence
> is what allows the registrar to disable the domain with impunity.
>
> Alan
>
>
>
>
> >>
> >>AND modify the contract language of 3.7.8 from:
> >>"...Registrar shall, upon notification by any person of an inaccuracy in
> >>the contact information associated with a Registered Name sponsored by
> >>Registrar, take reasonable steps to investigate that claimed inaccuracy.
> >>In the event Registrar learns of inaccurate contact information
> >>associated with a Registered Name it sponsors, it shall take reasonable
> >>steps to correct that inaccuracy."
> >>To:
> >>"...Registrar shall, upon notification by any person of an inaccuracy in
> >>the contact information associated with a Registered Name sponsored by
> >>Registrar, take reasonable steps to investigate that claimed inaccuracy.
> >>In the event Registrar learns of inaccurate contact information
> >>associated with a Registered Name it sponsors, it shall take reasonable
> >>steps to correct that inaccuracy AND IF NEEDED CANCEL OR SUSPEND THE
> >>DOMAIN IN ACCORDANCE WITH THE ACCURACY SPECIFICATION."
> >>
> >>
> >>I'm OK with the intent, but would suggest
> >>something more explicit, that allows for a period of time to make
> corrections.
> >>
> >>
> >>"...Registrar shall, upon notification by any
> >>person of an inaccuracy in the contact
> >>information associated with a Registered Name
> >>sponsored by Registrar, take reasonable steps
> >>to investigate that claimed  inaccuracy. In the
> >>event Registrar learns of inaccurate contact
> >>information associated with a Registered Name
> >>it sponsors, it shall take reasonable steps to
> >>correct that inaccuracy. Domains that maintain
> >>inaccurate information, after given reasonable
> >>time to be corrected upon notification, shall
> >>be cancelled or suspended by the Registrar in
> >>accordance with the accuracy specification.
> >>
> >>Is this any more palatable?
> >
> >Whois Accuracy Specification explicitly gives a
> >15 day window after which te registrar must disable the domain.
> >
> >Alan
> >
> >
> >>- Evan
> _______________________________________________
> ALAC mailing list
> ALAC at atlarge-lists.icann.org
> https://atlarge-lists.icann.org/mailman/listinfo/alac
>
> At-Large Online: http://www.atlarge.icann.org
> ALAC Working Wiki:
> https://community.icann.org/display/atlarge/At-Large+Advisory+Committee+(ALAC)
>



More information about the ALAC mailing list