>> When a person or persons register a domain name, a clear >> distinction should be made to exclusively identify a difference >> between input of credit card details and input of domain name >> registrant details. And your point is.....? AFAIK most registries and registrars make that distinction already. Whenever I've registered a domain name, I've always been asked for the admin and tech details before payment info was requested. IIRC some (US based) registrars didn't even ask for address info about the credit card that was used. >> This, as is true in my case, depending on the content of the >> domain names associated website(s), may lead to someone having >> to physical location because _they were not aware that domain >> registrant address details had been taken from their credit >> card details_. So what? Many people don't realise what evil is caused by accepting cookies from web sites. Or that personal details for a domain's technical and admin contacts can end up in a public whois database. This is essentially an education problem. If you think that the WG needs to do something in this area, please write up a draft and post it. If there's enough interest, it can be discussed at the WG and a document produced. This could be a BCP. Or it might be enough to come up with a recommendation to registrars and registries that they should separate credit card info from any admin and tech contact data that's maintained for a domain name. Since you've identified the potential problem, I think you're best placed to get the ball rolling by writing up a draft for the WG to consider. Over to you... BTW, this WG and mailing list works openly. Anonymous contributions should only be made when there is an obvious and convincing reason for privacy.