From peter@bsdly.net Mon Mar 07 18:19:56 2016 Return-path: Envelope-to: peter@bsdly.net Delivery-date: Mon, 07 Mar 2016 18:19:56 +0100 Received: from smut.bsdly.net ([192.168.103.72] helo=elke.bsdly.net) by skapet.bsdly.net with esmtp (Exim 4.85) (envelope-from ) id 1acyoz-0002mD-Iu; Mon, 07 Mar 2016 18:19:53 +0100 Subject: Re: " bsdly " To: Jiang zhihai References: <2D2C3E18BB1256064CB2243B11D1CC5D@zivsdqdi> From: "Peter N. M. Hansteen" X-Enigmail-Draft-Status: N1110 Message-ID: <56DDB834.9030207@bsdly.net> Date: Mon, 7 Mar 2016 18:19:48 +0100 User-Agent: Mozilla/5.0 (X11; OpenBSD amd64; rv:38.0) Gecko/20100101 Thunderbird/38.6.0 MIME-Version: 1.0 In-Reply-To: <2D2C3E18BB1256064CB2243B11D1CC5D@zivsdqdi> Content-Type: text/plain; charset=gbk Content-Transfer-Encoding: 8bit Status: RO Content-Length: 2056 Lines: 55 -----BEGIN PGP SIGNED MESSAGE----- Hash: SHA256 Dear Jiang zhihai, You've managed to make me a tad curious as to why the "bsdly" name would be important in these markets. While there is a very specific reason why I chose that name for my domains back in 2004, I don't see any reason why you wouldn't be perfectly well served by picking some other random sequence of character s. So out of pure curiosity, care to explain why you're doing this? Sincerely, Peter N. M. Hansteen On 03/07/16 05:46, Jiang zhihai wrote: > Dear Sirs, > > Our company based in chinese office, our company has submitted the > " bsdly " as CN/ASIA(.asia/.cn/.com.cn/.net.cn/.org.cn) domain name > and Internet Keyword, we are waiting for Mr. Jim's approval. We > think these names are very important for our business in Chinese > and Asia market. Even though Mr. Jim advises us to change another > name, we will persist in this name. > > Best regards > > Jiang zhihai > - -- Peter N. M. Hansteen, member of the first RFC 1149 implementation team http://bsdly.blogspot.com/ http://www.bsdly.net/ http://www.nuug.no/ "Remember to set the evil bit on all malicious network traffic" delilah spamd[29949]: 85.152.224.147: disconnected after 42673 seconds. -----BEGIN PGP SIGNATURE----- Version: GnuPG v2 iQIcBAEBCAAGBQJW3bgxAAoJELJiGF9h4DyeVRIQALqWl9nceEYeq3StMce0ZnvP aiiy3HkdnLYKV7Ap5u0tZtiX/IuQMhUy3xNkG5HhopcS+LiMbg+W3afKSog9ihCG vSdv32BOGitQsQjxbRUfabQD9eWzIScYttORsBo7HV44DjkL/KFSDBbRHSoPvWxR Loz3mpkz0HvCY3J7Zs+jq1Dbv3osKXSz2IxLr9WyXH12Aprwvd6uP/vwgq3vpJy2 e/a3Km7PYnwINIwTTGkQbm3mW2IegvQo4HbYjGuQSKQK31S153nUa8OHcISn8ILK WiHm83sF+I7T+uUBuqRoCGF3TvuGvIctPb8gRtHbVHZUwnfTqftFoZg5BaAOUnIl aTPvGjE8oObZww9xd08QWFjfXkVUwPkOuoM5yObnY7fFZro+Fu4vxj+slptleQFs fwt/eAGcxUzPHBT7ShbmMqXLv7TAre2t0ik8QFg8GZd/xoGo20llr8RAyWZhbKXe CTEbTXOjd12T1cLHFmvO4SQdW/pVQynVC+iggAcOqVnyjNHsf6rp+PAYG2Vi7Xa1 HtKCQl4IsEujZ4tXLM6uNU0aggYJInneeqNAXz+5N5bKTdOyFRTTm43tAgPEVUYj rFvM+ouIX+B9M7G2d3P8gJB/VJ6kgBcL9oLxk+qiLHs1p+v54Mvu/2uSbHgoIVII jbMcS0XRqgfZCbiE1/Fc =ECkK -----END PGP SIGNATURE-----