<<<
Chronological Index
>>> <<<
Thread Index
>>>
RE: Fw: [gnso-acc-sgb] Report for today
- To: gnso-acc-sgb@xxxxxxxxx
- Subject: RE: Fw: [gnso-acc-sgb] Report for today
- From: jwkckid1@xxxxxxxxxxxxx
- Date: Fri, 25 May 2007 21:05:48 -0500 (GMT-05:00)
<HEAD>
<STYLE>body{font-family:
Geneva,Arial,Helvetica,sans-serif;font-size:9pt;background-color:
#ffffff;color: black;}</STYLE>
<META content="MSHTML 6.00.2900.3086" name=GENERATOR></HEAD>
<BODY>
<DIV>Margie and all sgb members,</DIV>
<DIV> </DIV>
<DIV> Good point here. Costs as to scalable is very
important. We must insure that these costs</DIV>
<DIV>are not allowed to be passed down to consumers in terms of higher fees, or
registration</DIV>
<DIV>costs to registrants.</DIV>
<DIV> </DIV>
<DIV> Perhaps a standard form for afidavits with an electronic signature
should or can</DIV>
<DIV>be a requirement of the third party as a potential cost reduction
considerstion?<BR><BR><BR></DIV>
<BLOCKQUOTE style="PADDING-LEFT: 5px; MARGIN-LEFT: 0px; BORDER-LEFT: #0000ff
2px solid">-----Original Message----- <BR>From: Margie Milam
<MARGIE.MILAM@xxxxxxxxxxxxxxx><BR>Sent: May 25, 2007 2:43 PM <BR>To: Hugh
Dierker <HDIERKER2204@xxxxxxxxx><BR>Cc: gnso-acc-sgb@xxxxxxxxx <BR>Subject: RE:
Fw: [gnso-acc-sgb] Report for today <BR><BR><ZZZHTML
xmlns="http://www.w3.org/TR/REC-html40";
xmlns:st1="urn:schemas-microsoft-com:office:smarttags"
xmlns:w="urn:schemas-microsoft-com:office:word"
xmlns:o="urn:schemas-microsoft-com:office:office"
xmlns:v="urn:schemas-microsoft-com:vml"><ZZZHEAD><ZZZMETA CONTENT="text/html;
charset=us-ascii" HTTP-EQUIV="Content-Type"><ZZZMETA content="Microsoft Word 11
(filtered medium)" name="Generator"><ZZZ!--[IF !mso]>
<STYLE>
v\:* {behavior:url(#default#VML);}
o\:* {behavior:url(#default#VML);}
w\:* {behavior:url(#default#VML);}
.shape {behavior:url(#default#VML);}
</STYLE>
<ZZZ![ENDIF]--><?xml:namespace prefix = o /><o:SmartTagType
name="country-region"
namespaceuri="urn:schemas-microsoft-com:office:smarttags"></o:SmartTagType><o:SmartTagType
name="place"
namespaceuri="urn:schemas-microsoft-com:office:smarttags"></o:SmartTagType><o:SmartTagType
name="PostalCode"
namespaceuri="urn:schemas-microsoft-com:office:smarttags"></o:SmartTagType><o:SmartTagType
name="State"
namespaceuri="urn:schemas-microsoft-com:office:smarttags"></o:SmartTagType><o:SmartTagType
name="City"
namespaceuri="urn:schemas-microsoft-com:office:smarttags"></o:SmartTagType><o:SmartTagType
name="Street"
namespaceuri="urn:schemas-microsoft-com:office:smarttags"></o:SmartTagType><o:SmartTagType
name="address"
namespaceuri="urn:schemas-microsoft-com:office:smarttags"></o:SmartTagType><o:SmartTagType
name="PersonName"
namespaceuri="urn:schemas-microsoft-com:office:smarttags"></o:SmartTagType><ZZZ!--[IF
!mso]>
<STYLE>
st1\:*{behavior:url(#default#ieooui) }
</STYLE>
<ZZZ![ENDIF]-->
<STYLE>
<ZZZ!--
/* Font Definitions */
@font-face
{font-family:Tahoma;
panose-1:2 11 6 4 3 5 4 4 2 4;}
/* Style Definitions */
p.MsoNormal, li.MsoNormal, div.MsoNormal
{margin:0in;
margin-bottom:.0001pt;
font-size:12.0pt;
font-family:"Times New Roman";}
a:ZZZlink, span.MsoHyperlink
{color:blue;
text-decoration:underline;}
a:visited, span.MsoHyperlinkFollowed
{color:blue;
text-decoration:underline;}
p
{mso-margin-top-alt:auto;
margin-right:0in;
mso-margin-bottom-alt:auto;
margin-left:0in;
font-size:12.0pt;
font-family:"Times New Roman";}
span.EmailStyle18
{mso-style-type:personal-reply;
font-family:Arial;
color:navy;}
@page Section1
{size:8.5in 11.0in;
margin:1.0in 1.25in 1.0in 1.25in;}
div.Section1
{page:Section1;}
-->
</STYLE>
</ZZZHEAD><ZZZBODY lang=EN-US vlink="blue" link="blue">
<DIV class=Section1>
<P class=MsoNormal><FONT face=Arial color=navy size=2><SPAN style="FONT-SIZE:
10pt; COLOR: navy; FONT-FAMILY: Arial">In my view, cost prohibitive would be
something that would require a significant r&d effort or shift in
operations on the part of registrars to accommodate, without no apparent way to
recoup the costs. <o:p></o:p></SPAN></FONT></P>
<P class=MsoNormal><FONT face=Arial color=navy size=2><SPAN style="FONT-SIZE:
10pt; COLOR: navy; FONT-FAMILY: Arial"><o:p> </o:p></SPAN></FONT></P>
<P class=MsoNormal><FONT face=Arial color=navy size=2><SPAN style="FONT-SIZE:
10pt; COLOR: navy; FONT-FAMILY: Arial">All registrars rely on software, either
internally developed or licensed from a third party, to perform their domain
name registrations. My point is that in developing a WHOIS
solution, we need to take this into account. Anything that
would require a manual process, such as reviewing affidavits or faxes or other
documentation may not be scaleable, when you are talking about millions of
WHOIS records.<o:p></o:p></SPAN></FONT></P>
<P class=MsoNormal><FONT face=Arial color=navy size=2><SPAN style="FONT-SIZE:
10pt; COLOR: navy; FONT-FAMILY: Arial"><o:p> </o:p></SPAN></FONT></P>
<P class=MsoNormal><FONT face=Arial color=navy size=2><SPAN style="FONT-SIZE:
10pt; COLOR: navy; FONT-FAMILY: Arial"><o:p> </o:p></SPAN></FONT></P>
<P class=MsoNormal><FONT face=Arial color=navy size=2><SPAN style="FONT-SIZE:
10pt; COLOR: navy; FONT-FAMILY: Arial">Margie<o:p></o:p></SPAN></FONT></P>
<P class=MsoNormal><FONT face=Arial color=navy size=2><SPAN style="FONT-SIZE:
10pt; COLOR: navy; FONT-FAMILY: Arial"><o:p> </o:p></SPAN></FONT></P>
<P class=MsoNormal><FONT face=Arial color=navy size=2><SPAN style="FONT-SIZE:
10pt; COLOR: navy; FONT-FAMILY: Arial"><o:p> </o:p></SPAN></FONT></P>
<P class=MsoNormal><FONT face=Arial color=navy size=2><SPAN style="FONT-SIZE:
10pt; COLOR: navy; FONT-FAMILY: Arial"><o:p> </o:p></SPAN></FONT></P>
<DIV>
<DIV class=MsoNormal style="TEXT-ALIGN: center" align=center><FONT face="Times
New Roman" size=3><SPAN style="FONT-SIZE: 12pt">
<HR tabIndex=-1 align=center width="100%" SIZE=2>
</SPAN></FONT></DIV>
<P class=MsoNormal><B><FONT face=Tahoma size=2><SPAN style="FONT-WEIGHT: bold;
FONT-SIZE: 10pt; FONT-FAMILY: Tahoma">From:</SPAN></FONT></B><FONT face=Tahoma
size=2><SPAN style="FONT-SIZE: 10pt; FONT-FAMILY: Tahoma"> Hugh Dierker
[mailto:hdierker2204@xxxxxxxxx] <BR><B><SPAN style="FONT-WEIGHT:
bold">Sent:</SPAN></B> Friday, May 25, 2007 12:06 PM<BR><B><SPAN
style="FONT-WEIGHT: bold">To:</SPAN></B> <?xml:namespace prefix = st1
/><st1:PersonName w:st="on">Margie Milam</st1:PersonName>;
ross@xxxxxxxxxx<BR><B><SPAN style="FONT-WEIGHT: bold">Cc:</SPAN></B>
gnso-acc-sgb@xxxxxxxxx<BR><B><SPAN style="FONT-WEIGHT:
bold">Subject:</SPAN></B> RE: Fw: [gnso-acc-sgb] Report for
today</SPAN></FONT><o:p></o:p></P></DIV>
<P class=MsoNormal><FONT face="Times New Roman" size=3><SPAN style="FONT-SIZE:
12pt"><o:p> </o:p></SPAN></FONT></P>
<DIV>
<P class=MsoNormal><FONT face="Times New Roman" size=3><SPAN style="FONT-SIZE:
12pt">Could you elaborate on what would be cost prohibitive. Especially what
would have to be passed on to the consumer.<o:p></o:p></SPAN></FONT></P></DIV>
<DIV>
<P class=MsoNormal><FONT face="Times New Roman" size=3><SPAN style="FONT-SIZE:
12pt"> <o:p></o:p></SPAN></FONT></P></DIV>
<DIV>
<P class=MsoNormal><FONT face="Times New Roman" size=3><SPAN style="FONT-SIZE:
12pt">It seems that we are speaking more of a one time shift in process, rather
than an ongoing increase in cost. Please correct me if I am
wrong.<o:p></o:p></SPAN></FONT></P></DIV>
<DIV>
<P class=MsoNormal><FONT face="Times New Roman" size=3><SPAN style="FONT-SIZE:
12pt"> <o:p></o:p></SPAN></FONT></P></DIV>
<DIV>
<P class=MsoNormal><FONT face="Times New Roman" size=3><SPAN style="FONT-SIZE:
12pt">Just as an aside I find it interesting, although not critical, that no
human being is listed.<o:p></o:p></SPAN></FONT></P></DIV>
<DIV>
<P class=MsoNormal><FONT face="Times New Roman" size=3><SPAN style="FONT-SIZE:
12pt"> <o:p></o:p></SPAN></FONT></P></DIV>
<DIV>
<P class=MsoNormal><FONT face="Times New Roman" size=3><SPAN style="FONT-SIZE:
12pt">Eric<BR><BR><st1:PersonName w:st="on"><B><I><SPAN style="FONT-WEIGHT:
bold; FONT-STYLE: italic">Margie
Milam</SPAN></I></B></st1:PersonName><B><I><SPAN style="FONT-WEIGHT: bold;
FONT-STYLE: italic"> <Margie.Milam@xxxxxxxxxxxxxxx></SPAN></I></B>
wrote:<o:p></o:p></SPAN></FONT></P></DIV>
<BLOCKQUOTE style="BORDER-RIGHT: medium none; PADDING-RIGHT: 0in; BORDER-TOP:
medium none; MARGIN-TOP: 5pt; PADDING-LEFT: 4pt; MARGIN-BOTTOM: 5pt;
PADDING-BOTTOM: 0in; MARGIN-LEFT: 3.75pt; BORDER-LEFT: #1010ff 1.5pt solid;
PADDING-TOP: 0in; BORDER-BOTTOM: medium none">
<P class=MsoNormal style="MARGIN-BOTTOM: 12pt"><FONT face="Times New Roman"
size=3><SPAN style="FONT-SIZE: 12pt">That's correct. <BR><BR>I disagree with
Ross that this is out of scope since we are talking<BR>about whether registrars
currently deploy some technological limitations<BR>on Port 43, and whether such
limitations could be useful in developing a<BR>tiered access approach to WHOIS.
<BR><BR>I believe that the registrar's current practices,
including<BR>blacklisting/whitelisting IP addresses, rate limits per IP
addresses,<BR>and truncated records per IP address, may be some of the
limitations<BR>that could be evaluated in our work. As a registrar, I agree
with Ross<BR>that any changes to WHOIS access need to be implementable and not
cost<BR>prohibitive. <BR><BR>Margie <BR><BR><BR>-----Original
Message-----<BR>From: Ross Rader [mailto:ross@xxxxxxxxxx] <BR>Sent: Friday, May
25, 2007 11:23 AM<BR>To: <st1:PersonName w:st="on">Margie
Milam</st1:PersonName><BR>Cc: gnso-acc-sgb@xxxxxxxxx<BR>Subject: Re: Fw:
[gnso-acc-sgb] Report for today<BR><BR>Completeness is a service specific
notion. In this case, the whois query<BR><BR>was conducted through the
non-authoritative registry whois which has <BR>different collection and
publication requirements. Authoritative <BR>registrar whois requirements are
slightly different, leading to the <BR>payload as illustrated in the example
below. There is a second type of <BR>non-authoritative whois data, also known
as "referral whois data" which <BR>are those whois services provided by third
party services who are simply<BR><BR>reproducing the data found at the
authoritative whois service offered by<BR><BR>the registrar. Depending on the
method of query, there are policy <BR>issues, probably out of scope for this
working group, related to the <BR>methods of acquisition and publication of
this type of data by these <BR>third parties.<BR><BR>Tucows does not employ
rate limiting in its whois services, however we <BR>do employ query limiting
and blacklisting (blacklisting is a form of <BR>rate limiting I suppose, if the
rate limit is always assumed to be<BR>zero).<BR><BR>So yes, the earlier whois
data that was published was complete, as is <BR>the record Margie reproduced
below - the difference between the two is <BR>only the source of the data, in
this case Verisign registry and Tucows <BR>registrar.<BR><BR><st1:PersonName
w:st="on">Margie Milam</st1:PersonName> wrote:<BR>> Is this information from
the registry WHOIS or the registrar WHOIS<BR>> published through Port
43?<BR>> <BR>> The reason for my question is that I understand that some
registrars<BR>> will apply rate-limits on Port 43 with respect to certain
blacklisted<BR>IP<BR>> addresses, and will only publish a truncated WHOIS
record (similar to<BR>> this) when they receive inquiries from an IP address
that they believe<BR>> is abusing Port 43. I don't know if Tucows uses this
method with<BR>> respect to Port 43 (perhaps Ross can clarify). <BR>>
<BR>> This could be relevant to our analysis as we explore, per
Ross'<BR>> suggestion, the technical possibilities related to Port 43,that
could<BR>be<BR>> utilized in a tiered access approach. <BR>> <BR>> I
note that if I go to the Tucows website and do a WHOIS lookup on<BR>>
bankofamerica.com, I get the complete WHOIS record (see below).<BR>>
<BR>> <BR>> Margie<BR>> <BR>>
___________________________________________<BR>> <BR>> Whois info for,
bankofamerica.com:<BR>> <BR>> Registrant:<BR>> Bank of
<st1:country-region w:st="on"><st1:place
w:st="on">America</st1:place></st1:country-region><BR>> <st1:Street
w:st="on"><st1:address w:st="on">1201 Main
St</st1:address></st1:Street>.<BR>> TX1-609-12-15<BR>> <st1:place
w:st="on"><st1:City w:st="on">Dallas</st1:City>, <st1:State
w:st="on">TX</st1:State> <st1:PostalCode
w:st="on">75202</st1:PostalCode></st1:place><BR>> US<BR>> <BR>> Domain
name: BANKOFAMERICA.COM<BR>> <BR>> Administrative Contact:<BR>>
Administrator, Domain Domain.Administrator@xxxxxxxxxxxxxxxxx<BR>>
<st1:Street w:st="on"><st1:address w:st="on">1201 Main
Street</st1:address></st1:Street>, 12th Floor<BR>> M/S TX1-609-12-15<BR>>
<st1:place w:st="on"><st1:City w:st="on">Dallas</st1:City>, <st1:State
w:st="on">TX</st1:State> <st1:PostalCode
w:st="on">75202</st1:PostalCode></st1:place><BR>> US<BR>>
214-508-7868<BR>> Technical Contact:<BR>> HostMaster, The
hostmaster@xxxxxxxxxxxxxxxxx<BR>> <st1:Street w:st="on"><st1:address
w:st="on">2000 Clayton Road</st1:address></st1:Street><BR>> M/S
CA4-704-04-21<BR>> <st1:place w:st="on"><st1:City
w:st="on">Concord</st1:City>, <st1:State w:st="on">CA</st1:State>
<st1:PostalCode w:st="on">94520-2425</st1:PostalCode></st1:place><BR>>
US<BR>> +1.9256928812<BR>> <BR>> <BR>> Registrar of Record: TUCOWS,
INC.<BR>> Record last updated on 16-Mar-2007.<BR>> Record expires on
28-Dec-2010.<BR>> Record created on 28-Dec-1998.<BR>> <BR>> Domain
servers in listed order:<BR>> NS4.BANKOFAMERICA.COM 171.159.192.15<BR>>
NS3.BANKOFAMERICA.COM 171.161.160.15<BR>> NS1.BANKOFAMERICA.COM
171.159.64.15<BR>> <BR>> <BR>> Domain status:
clientTransferProhibited<BR>> clientUpdateProhibited<BR>> Margie<BR>>
<BR>> -----Original Message-----<BR>> From: Ross Rader
[mailto:ross@xxxxxxxxxx] <BR>> Sent: Friday, May 25, 2007 9:39 AM<BR>>
To: <st1:PersonName w:st="on">Margie Milam</st1:PersonName><BR>> Cc:
gnso-acc-sgb@xxxxxxxxx<BR>> Subject: Re: Fw: [gnso-acc-sgb] Report for
today<BR>> <BR>> <st1:PersonName w:st="on">Margie Milam</st1:PersonName>
wrote:<BR>>> Where is the rest of the WHOIS information? If this is this
the <BR>>> complete record, a lot of currently required information is
missing.<BR>> <BR>>> The email address is missing from this, as well
as the phone number<BR>of<BR>> <BR>>> the various contacts. It would
be very difficult to contact Bank of<BR><BR>>> <st1:country-region
w:st="on"><st1:place w:st="on">America</st1:place></st1:country-region> or send
them an email if there were issues related to the<BR>> domain <BR>>>
name.<BR>> <BR>> There is nothing missing from this record.<BR>>
<BR>> -ross<BR>> <BR>>
<BR><BR><BR><o:p></o:p></SPAN></FONT></P></BLOCKQUOTE>
<P class=MsoNormal><FONT face="Times New Roman" size=3><SPAN style="FONT-SIZE:
12pt"><o:p> </o:p></SPAN></FONT></P>
<P><FONT face="Times New Roman" size=3><SPAN style="FONT-SIZE: 12pt"> </P>
<P>Regards,<BR><BR>Jeffrey A. Williams<BR>Spokesman for INEGroup LLA. - (Over
134k members/stakeholders strong!)<BR>"Obedience of the law is the greatest
freedom" -<BR> Abraham Lincoln<BR><BR>"Credit should go with the
performance of duty and not with what is very<BR>often the accident of glory" -
Theodore Roosevelt<BR><BR>"If the probability be called P; the injury, L; and
the burden, B; liability<BR>depends upon whether B is less than L multiplied
by<BR>P: i.e., whether B is less than PL."<BR>United States v. Carroll
Towing (159 F.2d 169 [2d Cir.
1947]<BR>===============================================================<BR>Updated
1/26/04<BR>CSO/DIR. Internet Network Eng. SR. Eng. Network data security IDNS.
div. of<BR>Information Network Eng. INEG. INC.<BR>ABA member in good
standing member ID 01257402 E-Mail jwkckid1@xxxxxxxxxxxxx<BR>Registered Email
addr with the USPS Contact Number: 214-244-4827<BR><ZZZ!--
--></P></ZZZBODY><o:p>
<P>Regards,<BR><BR>Jeffrey A. Williams<BR>Spokesman for INEGroup LLA. - (Over
134k members/stakeholders strong!)<BR>"Obedience of the law is the greatest
freedom" -<BR> Abraham Lincoln<BR><BR>"Credit should go with the
performance of duty and not with what is very<BR>often the accident of glory" -
Theodore Roosevelt<BR><BR>"If the probability be called P; the injury, L; and
the burden, B; liability<BR>depends upon whether B is less than L multiplied
by<BR>P: i.e., whether B is less than PL."<BR>United States v. Carroll
Towing (159 F.2d 169 [2d Cir.
1947]<BR>===============================================================<BR>Updated
1/26/04<BR>CSO/DIR. Internet Network Eng. SR. Eng. Network data security IDNS.
div. of<BR>Information Network Eng. INEG. INC.<BR>ABA member in good
standing member ID 01257402 E-Mail jwkckid1@xxxxxxxxxxxxx<BR>Registered Email
addr with the USPS Contact Number: 214-244-4827<BR><ZZZ!--
--></P></ZZZBODY></o:p></SPAN></FONT></DIV></BLOCKQUOTE></BODY>
<<<
Chronological Index
>>> <<<
Thread Index
>>>
|