[gnso-rds-pdp-wg] 2013 RAA Data Elements

[Paul Keating]

The question was what should be public.

It is not IMHO an objection to say that the information can be found
elsewhere also.

Scams can be and sh oiled be addressed via other methods.

Nameservers are not worthless data.  They are used in security
investigations regularly.  I use them in legal disputes concerning use,
etc.

PRK

On 6/14/17, 5:22 AM, "Rob Golding" <gnso-rds-pdp-wg-bounces at icann.org on
behalf of rob.golding at astutium.com> wrote:

>Registrar WHOIS Server: whois.example-registrar.tld
>
>^ This field only applies to com/net/jobs due to the "thin"
>registry/registar setup, and will be "gone" shortly as part of the
>migration to "thick", so should not be included in the MPDS
>
>Registrar Registration Expiration Date: 2010-10-08T00:44:59Z
>
>^ This field only applies to com/net/jobs due to the "thin"
>registry/registar setup, and will be "gone" shortly as part of the
>migration to "thick", so should not be included in the MPDS
>
>Registrar: EXAMPLE REGISTRAR LLC
>Registrar IANA ID: 5555555
>
>^ You don't need the name in the MPDS if you have the IANA# as the
>relationship can be "looked up"
>
>Domain Status: clientDeleteProhibited2
>Domain Status: clientRenewProhibited
>Domain Status: clientTransferProhibited
>
>^ Whilst _a_ status about the domain can be seen as useful, I still
>object to the publishing of the "detailed status" information as
>unnecessary and an additional "attack vector" for scams
>
>Name Server: NS01.EXAMPLE-REGISTRAR.TLD10
>Name Server: NS02.EXAMPLE-REGISTRAR.TLD
>
>^ This information provides no _functional_ purpose, we have the
>opportunity to tidyup WHOIS/RDS, and so is an ideal time to remove this
>unnecessary bloat
>
>Rob
>_______________________________________________
>gnso-rds-pdp-wg mailing list
>gnso-rds-pdp-wg at icann.org
>https://mm.icann.org/mailman/listinfo/gnso-rds-pdp-wg