[ppml] Directory Services - Take 2
John.Sweeting at teleglobe.com
Fri Jun 10 10:48:29 EDT 2005
the policy to could refer to an annex or such that ARIN staff would have the
responsibility of approving and maintaining so at least the types supported
could be referenced with the policy.......
*From: Lea Roberts [mailto:lea.roberts at stanford.edu]
*Sent: 10 juin 2005 10:40
*To: ppml at arin.net
*Subject: RE: [ppml] Directory Services - Take 2
*On Fri, 10 Jun 2005, Hannigan, Martin wrote:
*> > -----Original Message-----
*> > From: owner-ppml at arin.net [mailto:owner-ppml at arin.net]On Behalf Of
*> > Michael.Dillon at btradianz.com
*> > Sent: Friday, June 10, 2005 5:51 AM
*> > To: ppml at arin.net
*> > Subject: Re: [ppml] Directory Services - Take 2
*> > > ARIN shall publish the APID in the following methods using
*> > > industry standard practices:
*> > >
*> > > - Via the WHOIS protocol.
*> > > - Via a query form accessible via the HTTP protocol.
*> > > - Via FTP to users who complete the bulk data form.
*> > > - Via CDROM to users who complete the bulk data form.
*> > > - Via the RWHOIS protocol.
*> [ SNIP ]
*> > Let's leave the details of physical media
*> > format between ARIN staff and the applicants. If someone
*> > wants to courier over a hard drive to get an Oracle
*> > dump file, it is none of our business.
*> It's inefficient to require the office to be able to handle
*> each and every exotic media request. Specifying them makes
*> sense for both them and the customers and sets a reasonable
*As often comes up in policy review, sometimes specific implementation
*details, in this case media type, shouldn't be written into a policy.
*I agree that the media types should be limited but I would
*trust the ARIN
*staff to determine which ones they can easily support and make
*available publicly. The list is bound to change over time and it
*shouldn't require a policy change when some fabulous new format becomes
More information about the ARIN-PPML