<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0 Transitional//EN">
<HTML xmlns="http://www.w3.org/TR/REC-html40" xmlns:v =
"urn:schemas-microsoft-com:vml" xmlns:o =
"urn:schemas-microsoft-com:office:office" xmlns:w =
"urn:schemas-microsoft-com:office:word" xmlns:x =
"urn:schemas-microsoft-com:office:excel" xmlns:p =
"urn:schemas-microsoft-com:office:powerpoint" xmlns:a =
"urn:schemas-microsoft-com:office:access" xmlns:dt =
"uuid:C2F41010-65B3-11d1-A29F-00AA00C14882" xmlns:s =
"uuid:BDC6E3F0-6DA3-11d1-A2A3-00AA00C14882" xmlns:rs =
"urn:schemas-microsoft-com:rowset" xmlns:z = "#RowsetSchema" xmlns:b =
"urn:schemas-microsoft-com:office:publisher" xmlns:ss =
"urn:schemas-microsoft-com:office:spreadsheet" xmlns:c =
"urn:schemas-microsoft-com:office:component:spreadsheet" xmlns:odc =
"urn:schemas-microsoft-com:office:odc" xmlns:oa =
"urn:schemas-microsoft-com:office:activation" xmlns:html =
"http://www.w3.org/TR/REC-html40" xmlns:q =
"http://schemas.xmlsoap.org/soap/envelope/" xmlns:rtc =
"http://microsoft.com/officenet/conferencing" XMLNS:D = "DAV:" XMLNS:Repl =
"http://schemas.microsoft.com/repl/" xmlns:mt =
"http://schemas.microsoft.com/sharepoint/soap/meetings/" xmlns:x2 =
"http://schemas.microsoft.com/office/excel/2003/xml" xmlns:ppda =
"http://www.passport.com/NameSpace.xsd" xmlns:ois =
"http://schemas.microsoft.com/sharepoint/soap/ois/" xmlns:dir =
"http://schemas.microsoft.com/sharepoint/soap/directory/" xmlns:ds =
"http://www.w3.org/2000/09/xmldsig#" xmlns:dsp =
"http://schemas.microsoft.com/sharepoint/dsp" xmlns:udc =
"http://schemas.microsoft.com/data/udc" xmlns:xsd =
"http://www.w3.org/2001/XMLSchema" xmlns:sub =
"http://schemas.microsoft.com/sharepoint/soap/2002/1/alerts/" xmlns:ec =
"http://www.w3.org/2001/04/xmlenc#" xmlns:sp =
"http://schemas.microsoft.com/sharepoint/" xmlns:sps =
"http://schemas.microsoft.com/sharepoint/soap/" xmlns:xsi =
"http://www.w3.org/2001/XMLSchema-instance" xmlns:udcs =
"http://schemas.microsoft.com/data/udc/soap" xmlns:udcxf =
"http://schemas.microsoft.com/data/udc/xmlfile" xmlns:udcp2p =
"http://schemas.microsoft.com/data/udc/parttopart" xmlns:wf =
"http://schemas.microsoft.com/sharepoint/soap/workflow/" xmlns:dsss =
"http://schemas.microsoft.com/office/2006/digsig-setup" xmlns:dssi =
"http://schemas.microsoft.com/office/2006/digsig" xmlns:mdssi =
"http://schemas.openxmlformats.org/package/2006/digital-signature" xmlns:mver =
"http://schemas.openxmlformats.org/markup-compatibility/2006" xmlns:m =
"http://schemas.microsoft.com/office/2004/12/omml" xmlns:mrels =
"http://schemas.openxmlformats.org/package/2006/relationships" xmlns:spwp =
"http://microsoft.com/sharepoint/webpartpages" xmlns:ex12t =
"http://schemas.microsoft.com/exchange/services/2006/types" xmlns:ex12m =
"http://schemas.microsoft.com/exchange/services/2006/messages" xmlns:pptsl =
"http://schemas.microsoft.com/sharepoint/soap/SlideLibrary/" xmlns:spsl =
"http://microsoft.com/webservices/SharePointPortalServer/PublishedLinksService"
XMLNS:Z = "urn:schemas-microsoft-com:" xmlns:st = ""><HEAD>
<META content="text/html; charset=us-ascii" http-equiv=Content-Type>
<META name=GENERATOR content="MSHTML 8.00.6001.18702">
<STYLE>@font-face {
font-family: Cambria Math;
}
@font-face {
font-family: Calibri;
}
@font-face {
font-family: Tahoma;
}
@page WordSection1 {size: 8.5in 11.0in; margin: 1.0in 1.0in 1.0in 1.0in; }
P.MsoNormal {
MARGIN: 0in 0in 0pt; FONT-FAMILY: "Times New Roman","serif"; FONT-SIZE: 12pt
}
LI.MsoNormal {
MARGIN: 0in 0in 0pt; FONT-FAMILY: "Times New Roman","serif"; FONT-SIZE: 12pt
}
DIV.MsoNormal {
MARGIN: 0in 0in 0pt; FONT-FAMILY: "Times New Roman","serif"; FONT-SIZE: 12pt
}
A:link {
COLOR: blue; TEXT-DECORATION: underline; mso-style-priority: 99
}
SPAN.MsoHyperlink {
COLOR: blue; TEXT-DECORATION: underline; mso-style-priority: 99
}
A:visited {
COLOR: purple; TEXT-DECORATION: underline; mso-style-priority: 99
}
SPAN.MsoHyperlinkFollowed {
COLOR: purple; TEXT-DECORATION: underline; mso-style-priority: 99
}
SPAN.EmailStyle17 {
FONT-FAMILY: "Calibri","sans-serif"; COLOR: #1f497d; mso-style-type: personal-reply
}
.MsoChpDefault {
FONT-SIZE: 10pt; mso-style-type: export-only
}
DIV.WordSection1 {
page: WordSection1
}
</STYLE>
<!--[if gte mso 9]><xml>
<o:shapedefaults v:ext="edit" spidmax="1026" />
</xml><![endif]--><!--[if gte mso 9]><xml>
<o:shapelayout v:ext="edit">
<o:idmap v:ext="edit" data="1" />
</o:shapelayout></xml><![endif]--></HEAD>
<BODY lang=EN-US link=blue vLink=purple>
<DIV dir=ltr align=left><SPAN class=199003420-15112010><FONT color=#0000ff
size=2 face=Arial>That helps a bit, but let me ask for your response on one more
example. </FONT></SPAN></DIV>
<DIV dir=ltr align=left><SPAN class=199003420-15112010><FONT color=#0000ff
size=2 face=Arial></FONT></SPAN> </DIV>
<DIV dir=ltr align=left><SPAN class=199003420-15112010><FONT color=#0000ff
size=2 face=Arial>For example if ARIN see's the following
</FONT></SPAN><SPAN class=199003420-15112010><FONT color=#0000ff size=2
face=Arial>Situation visible in WHOIS or RWHOIS:</FONT></SPAN></DIV>
<DIV dir=ltr align=left><SPAN class=199003420-15112010><FONT color=#0000ff
size=2 face=Arial>ISP Jingle = valid POC</FONT></SPAN></DIV>
<DIV dir=ltr align=left><SPAN class=199003420-15112010><FONT color=#0000ff
size=2 face=Arial>customer of ISP Jingle "Hip Shop" = Invalid
POC</FONT></SPAN></DIV>
<DIV dir=ltr align=left><SPAN class=199003420-15112010><FONT color=#0000ff
size=2 face=Arial></FONT></SPAN> </DIV>
<DIV dir=ltr align=left><SPAN class=199003420-15112010><FONT color=#0000ff
size=2 face=Arial>Possible Answers to how ARIN would respond
are:</FONT></SPAN></DIV>
<DIV dir=ltr align=left><SPAN class=199003420-15112010><FONT color=#0000ff
size=2 face=Arial>1. ISP Jingle will not be barred from a new allocation from
ARIN if they request one, but Hip Shop will be blocked from an
additional re-assignment until ISP Jingle gets their POC
updated/validated. Correct?</FONT></SPAN></DIV>
<DIV dir=ltr align=left><SPAN class=199003420-15112010><FONT color=#0000ff
size=2 face=Arial></FONT></SPAN> </DIV>
<DIV dir=ltr align=left><SPAN class=199003420-15112010><FONT color=#0000ff
size=2 face=Arial>OR</FONT></SPAN></DIV>
<DIV dir=ltr align=left><SPAN class=199003420-15112010><FONT color=#0000ff
size=2 face=Arial></FONT></SPAN> </DIV>
<DIV dir=ltr align=left><SPAN class=199003420-15112010><FONT color=#0000ff
size=2 face=Arial>2. ISP Jingle will be barred from a new allocation from ARIN
if they request one, as long as their customer Hip Shop has an invalid POC on
record in WHOIS. Correct?</FONT></SPAN></DIV>
<DIV dir=ltr align=left><SPAN class=199003420-15112010><FONT color=#0000ff
size=2 face=Arial></FONT></SPAN> </DIV>
<DIV dir=ltr align=left><SPAN class=199003420-15112010><FONT color=#0000ff
size=2 face=Arial></FONT></SPAN> </DIV>
<DIV dir=ltr align=left><SPAN class=199003420-15112010><FONT color=#0000ff
size=2 face=Arial>Sorry for the at nausea questioning and clarifications but I
just want to make sure I fully understand how much this change will impact the
entities and databases I manage. The below items are the ones I'm
focusing on here. I just want to make sure I interpret the level/layer at
which the invalid POC alarm will go off at and exactly how this impacts Direct
Allocations from ARIN.</FONT></SPAN></DIV>
<DIV dir=ltr align=left><FONT color=#0000ff size=2
face=Arial></FONT> </DIV>
<DIV dir=ltr align=left><SPAN lang=EN>
<P>•<FONT size=2 face="Courier New"><FONT size=2 face="Courier New"> ARIN Online
users would only have access to POC validation and modification features until
they validate any non-validated POCs to which they are linked. Once validated,
an ARIN Online user would have access to all available ARIN Online
functionality.</P></FONT></FONT></SPAN><SPAN class=199003420-15112010><FONT
color=#0000ff size=2 face=Arial></FONT></SPAN></DIV>
<DIV dir=ltr align=left><SPAN class=199003420-15112010><FONT color=#0000ff
size=2 face=Arial><SPAN lang=EN>
<P><FONT color=#000000>•<FONT size=2 face="Courier New"><FONT size=2
face="Courier New"> Templates requesting resources directly from ARIN (v4 ISP
request, v4 End-User request, v6 ISP request, v6 End-User request, ASN,
experimental), or requesting resource transfers or ASN modifications would be
accepted and ticketed, however, they will not be processed if the POC is
invalid. ARIN staff would notify submitters via email to validate their
associated POC information through ARIN
Online.</P></FONT></FONT></FONT></SPAN></FONT></SPAN></DIV><FONT color=#0000ff
size=2 face=Arial></FONT><BR>
<DIV dir=ltr lang=en-us class=OutlookMessageHeader align=left>
<HR tabIndex=-1>
<FONT size=2 face=Tahoma><B>From:</B> arin-consult-bounces@arin.net
[mailto:arin-consult-bounces@arin.net] <B>On Behalf Of </B>Nate
Davis<BR><B>Sent:</B> Monday, November 15, 2010 12:14 PM<BR><B>To:</B>
arin-consult@arin.net<BR><B>Subject:</B> Re: [ARIN-consult] Clarification
question<BR></FONT><BR></DIV>
<DIV></DIV>
<DIV class=WordSection1>
<P class=MsoNormal><SPAN
style="FONT-FAMILY: 'Calibri','sans-serif'; COLOR: #1f497d; FONT-SIZE: 11pt">Marla,<o:p></o:p></SPAN></P>
<P class=MsoNormal><SPAN
style="FONT-FAMILY: 'Calibri','sans-serif'; COLOR: #1f497d; FONT-SIZE: 11pt"><o:p> </o:p></SPAN></P>
<P class=MsoNormal><SPAN
style="FONT-FAMILY: 'Calibri','sans-serif'; COLOR: #1f497d; FONT-SIZE: 11pt">Thanks
for your question.<o:p></o:p></SPAN></P>
<P class=MsoNormal><SPAN
style="FONT-FAMILY: 'Calibri','sans-serif'; COLOR: #1f497d; FONT-SIZE: 11pt"><o:p> </o:p></SPAN></P>
<P class=MsoNormal><SPAN
style="FONT-FAMILY: 'Calibri','sans-serif'; COLOR: #1f497d; FONT-SIZE: 11pt">The
overall goal of this proposed change is to improve all WHOIS POC data, not just
those associated with organizations having direct relationship with ARIN.
Therefore this includes direct allocation/assignment POCs as well as indirect
allocation/assignment POCs.<o:p></o:p></SPAN></P>
<P class=MsoNormal><SPAN
style="FONT-FAMILY: 'Calibri','sans-serif'; COLOR: #1f497d; FONT-SIZE: 11pt">So,
an ISP having all valid POCs will NOT be prevented from using ARIN Online or
updating the database in cases where their downstream customers have invalid
POCs. In the example you cite, assuming ISP Jingle has valid POCs while
still having invalid POCs among<o:p></o:p></SPAN></P>
<P class=MsoNormal><SPAN
style="FONT-FAMILY: 'Calibri','sans-serif'; COLOR: #1f497d; FONT-SIZE: 11pt">the
5 downstream reassignments, ISP Jingle will have all access to all services
through ARIN Online as well the ability to submit database changes to
ARIN. ISP Jingle will not be able to use ARIN Online or request database
updates if it’s own POCs are not all valid. <o:p></o:p></SPAN></P>
<P class=MsoNormal><SPAN
style="FONT-FAMILY: 'Calibri','sans-serif'; COLOR: #1f497d; FONT-SIZE: 11pt"><o:p> </o:p></SPAN></P>
<P class=MsoNormal><SPAN
style="FONT-FAMILY: 'Calibri','sans-serif'; COLOR: #1f497d; FONT-SIZE: 11pt">Granted
the likelihood of an indirect allocation/assignment POC using ARIN Online to
maintain data is small, we still wish to provide them the capability to update
their records in cases where their upstream ARIN direct organization does
not. Please note the community<o:p></o:p></SPAN></P>
<P class=MsoNormal><SPAN
style="FONT-FAMILY: 'Calibri','sans-serif'; COLOR: #1f497d; FONT-SIZE: 11pt">requested
that we include indirect POCs as part of POC validation, therefore this is
consistent with that policy. <o:p></o:p></SPAN></P>
<P class=MsoNormal><SPAN
style="FONT-FAMILY: 'Calibri','sans-serif'; COLOR: #1f497d; FONT-SIZE: 11pt"><o:p> </o:p></SPAN></P>
<P class=MsoNormal><SPAN
style="FONT-FAMILY: 'Calibri','sans-serif'; COLOR: #1f497d; FONT-SIZE: 11pt">Regards,<o:p></o:p></SPAN></P>
<P class=MsoNormal><SPAN
style="FONT-FAMILY: 'Calibri','sans-serif'; COLOR: #1f497d; FONT-SIZE: 11pt"><o:p> </o:p></SPAN></P>
<P class=MsoNormal><SPAN
style="FONT-FAMILY: 'Calibri','sans-serif'; COLOR: #1f497d; FONT-SIZE: 11pt">Nate
Davis<o:p></o:p></SPAN></P>
<P class=MsoNormal><SPAN
style="FONT-FAMILY: 'Calibri','sans-serif'; COLOR: #1f497d; FONT-SIZE: 11pt">Chief
Operating Officer<o:p></o:p></SPAN></P>
<P class=MsoNormal><SPAN
style="FONT-FAMILY: 'Calibri','sans-serif'; COLOR: #1f497d; FONT-SIZE: 11pt">The
American Registry for Internet Numbers<o:p></o:p></SPAN></P>
<P class=MsoNormal><SPAN
style="FONT-FAMILY: 'Calibri','sans-serif'; COLOR: #1f497d; FONT-SIZE: 11pt"><o:p> </o:p></SPAN></P>
<P class=MsoNormal><SPAN
style="FONT-FAMILY: 'Calibri','sans-serif'; COLOR: #1f497d; FONT-SIZE: 11pt"><o:p> </o:p></SPAN></P>
<DIV>
<DIV
style="BORDER-BOTTOM: medium none; BORDER-LEFT: medium none; PADDING-BOTTOM: 0in; PADDING-LEFT: 0in; PADDING-RIGHT: 0in; BORDER-TOP: #b5c4df 1pt solid; BORDER-RIGHT: medium none; PADDING-TOP: 3pt">
<P class=MsoNormal><B><SPAN
style="FONT-FAMILY: 'Tahoma','sans-serif'; FONT-SIZE: 10pt">From:</SPAN></B><SPAN
style="FONT-FAMILY: 'Tahoma','sans-serif'; FONT-SIZE: 10pt">
arin-consult-bounces@arin.net [mailto:arin-consult-bounces@arin.net] <B>On
Behalf Of </B>Azinger, Marla<BR><B>Sent:</B> Monday, November 15, 2010 12:55
PM<BR><B>To:</B> arin-consult@arin.net<BR><B>Subject:</B> [ARIN-consult]
Clarification question<o:p></o:p></SPAN></P></DIV></DIV>
<P class=MsoNormal><o:p> </o:p></P>
<DIV>
<P class=MsoNormal><SPAN
style="FONT-FAMILY: 'Arial','sans-serif'; FONT-SIZE: 10pt">I just want to make
sure I interpret this correctly.</SPAN><o:p></o:p></P></DIV>
<DIV>
<P class=MsoNormal> <o:p></o:p></P></DIV>
<DIV>
<P class=MsoNormal><SPAN
style="FONT-FAMILY: 'Arial','sans-serif'; FONT-SIZE: 10pt">This is saying that
direct allocation or assignment recipients of ARIN will basically be forced to
update/validate the POC info before gaining any new ARIN resources.
Correct?</SPAN><o:p></o:p></P></DIV>
<DIV>
<P class=MsoNormal> <o:p></o:p></P></DIV>
<DIV>
<P class=MsoNormal><SPAN
style="FONT-FAMILY: 'Arial','sans-serif'; FONT-SIZE: 10pt">Its NOT saying that
direct allocation or assignment recipients of ARIN who have re-assignments or
re-allocations recorded in WHOIS with an invalidated or incorrect POC on a
re-assignment or re-allocation visible in WHOIS will then block the direct
ARIN recipient from getting more ARIN resources? For example if direct
recipient "ISP Jingle" has a /18 from ARIN and 5 of his re-assignments to his
customers have invalidated or incorrect POC info, these 5 customer of ISP Jingle
wont block ISP Jingle from receiving more resources from ARIN will it?
This is really only concerning the POC info on the Direct Recipient of ARIN,
correct?</SPAN><o:p></o:p></P></DIV>
<DIV>
<P class=MsoNormal> <o:p></o:p></P></DIV>
<DIV>
<P class=MsoNormal><SPAN
style="FONT-FAMILY: 'Arial','sans-serif'; FONT-SIZE: 10pt">Thank
you</SPAN><o:p></o:p></P></DIV>
<DIV>
<P class=MsoNormal><SPAN
style="FONT-FAMILY: 'Arial','sans-serif'; FONT-SIZE: 10pt">Marla</SPAN><o:p></o:p></P></DIV></DIV></BODY></HTML>