[141051] in North American Network Operators' Group
RE: Deploying IPv6 globally
daemon@ATHENA.MIT.EDU (John Macleod)
Tue May 31 12:00:50 2011
From: John Macleod <JMacleod@alentus.com>
To: eric clark <cabenth@gmail.com>
Date: Tue, 31 May 2011 09:51:55 -0600
In-Reply-To: <632478B3-E40A-4FC8-A39E-C47B2F8399AE@bogus.com>
Cc: NANOG list <nanog@nanog.org>
Errors-To: nanog-bounces+nanog.discuss=bloom-picayune.mit.edu@nanog.org
I have done this several times for NA orgs with global sites with ARIN and =
for EU orgs with global sites with RIPE.
ARIN were fine, RIPE just excluded any non-RIPE governed locations from the=
calculation criteria, however they were granted on all counts.
John
________________________________________
From: Joel Jaeggli [joelja@bogus.com]
Sent: Tuesday, May 31, 2011 4:54 PM
To: eric clark
Cc: NANOG list
Subject: Re: Deploying IPv6 globally
At a previous company my pi assigment request included our overseas sites. =
the bulk of the assignment and the business unit making the request were ba=
sed in north america. resulting request was for a /43.
joel
On May 31, 2011, at 8:36 AM, eric clark wrote:
> Many North American based organizations operate with their ARIN issued BG=
P
> AS distributed globally.
>
> When I discussed obtaining IPv6 space from ARIN a few years ago, they tol=
d
> me to submit an individual request for each of my sites (and they'd issu=
e a
> /48 or larger based on the site). This is the process I've been following=
,
> until now, for my North American sites...
>
> My question is, has anyone started deploying ARIN IP space to their globa=
l
> offices? If so, how are you registering those sites with ARIN?
> Or did they tell you something else?
>
> Thanks
>
> -C
>
"Please consider the environment before printing this e-mail
This e-mail (and/or any attachment) contains information, which is confiden=
tial and intended solely for the attention and use of the named addressee(s=
). If you are not the intended recipient you must not copy, distribute or u=
se it for any purpose or disclose the contents to any person. If you have r=
eceived this e-mail in error, please immediately notify the sender. The inf=
ormation contained in this e-mail (and any attachments) is supplied in good=
faith, but the sender shall not be under any liability in damages or other=
wise for any reliance that may be placed upon it by the recipient, nor does=
it constitute a contract in any way. Any comments or opinions expressed ar=
e those of the originator not of Alentus Corporation unless otherwise expre=
ssly stated."
