Re: Addressing versus Routing (Was: Deploying IPv6 in a datacenter)

2005-12-27 Thread Daniel Roesen
On Thu, Dec 22, 2005 at 11:56:07AM +0100, Jeroen Massar wrote: Correct. One of the few solutions you can do is setup connectivity (VPN or so) of your own between them. Oh excellent idea. Pushing traffic twice through the upstream pipes? I'm sure the upstream ISPs will be very happy about such

Re: Addressing versus Routing (Was: Deploying IPv6 in a datacenter)

2005-12-22 Thread Jeroen Massar
Kevin Day wrote: On Dec 21, 2005, at 1:34 PM, Jeroen Massar wrote: Kevin Day wrote: [..] The disincentives for a small-mid sized network to moving to IPv6 are pretty big right now, which means very few of us are going to do it willingly. (Remember, the little guys are who are going to

Re: Addressing versus Routing (Was: Deploying IPv6 in a datacenter)

2005-12-22 Thread Michael . Dillon
However I'm much more concerned that big providers (anyone who can qualify for a /32) need to make nearly zero changes to their way of doing things, but MomPop's regional ISP or Chuck's Web Hosting and Bait Shop are going to be losing out big when it comes to IPv6. Which is preferable,

Re: Addressing versus Routing (Was: Deploying IPv6 in a datacenter)

2005-12-22 Thread Andrew Dul
---Original Message--- From: [EMAIL PROTECTED] Subject: Re: Addressing versus Routing (Was: Deploying IPv6 in a datacenter) Sent: 22 Dec '05 03:55 The RIRs have not made any decisions yet about offering geotop addresses, but 7/8 of the IPv6 address space has been

Re: Addressing versus Routing (Was: Deploying IPv6 in a datacenter)

2005-12-22 Thread Kevin Day
Ok, I promise this is my last reply to the list about this... This has gone too far into theoretical and not operational content, and probably belongs on an IPv6 policy list, so I'll hush. :) I'll follow up with anyone privately who wants to continue the discussion though. On Dec 22,

Addressing versus Routing (Was: Deploying IPv6 in a datacenter)

2005-12-21 Thread Jeroen Massar
Kevin Day wrote: [..] I agree with your point that currently your IPv4-solution can't be applied to IPv6 but..(see the helpful and nice thingy part at the end ;) 1) We've got separate POPs in different cities, with no dedicated connectivity between them. They act as entirely independent

Re: Addressing versus Routing (Was: Deploying IPv6 in a datacenter)

2005-12-21 Thread Daniel Roesen
On Wed, Dec 21, 2005 at 08:34:06PM +0100, Jeroen Massar wrote: The issue with announcing say a /48 is though that networks which filter will filter it out and will only reach you over the aggregate. Of course that is their choice, just like yours is to try to announce the /48's in IPv6, or

Re: Addressing versus Routing (Was: Deploying IPv6 in a datacenter)

2005-12-21 Thread sysadmin
On Wed, Dec 21, 2005 at 11:36:00PM +0100, Daniel Roesen wrote: On Wed, Dec 21, 2005 at 08:34:06PM +0100, Jeroen Massar wrote: The issue with announcing say a /48 is though that networks which filter will filter it out and will only reach you over the aggregate. Of course that is their

Re: Addressing versus Routing (Was: Deploying IPv6 in a datacenter)

2005-12-21 Thread Daniel Roesen
On Wed, Dec 21, 2005 at 04:43:58PM -0600, [EMAIL PROTECTED] wrote: Really? Where are the limits of BGP? Can you show me any numbers? You'd be the first. I'm not aware of any protocol inherent scaling brickwalls like with other protocols where certain timing constraints place limits (or

RE: Addressing versus Routing (Was: Deploying IPv6 in a datacenter)

2005-12-21 Thread Hannigan, Martin
On Wed, Dec 21, 2005 at 04:43:58PM -0600, [EMAIL PROTECTED] wrote: Really? Where are the limits of BGP? Can you show me any numbers? You'd be the first. I'm not aware of any protocol inherent scaling brickwalls like with other protocols where certain timing constraints place

Re: Addressing versus Routing (Was: Deploying IPv6 in a datacenter)

2005-12-21 Thread Daniel Roesen
On Wed, Dec 21, 2005 at 06:11:17PM -0500, Hannigan, Martin wrote: Correct. And there you have minimum frame spacing requirements (IFG) and (e.g. with 10Base2 networks) minimum distance between stations attached to the bus to allow CSMA/CD work correctly. Interframe gap has no dependancy

Re: Addressing versus Routing (Was: Deploying IPv6 in a datacenter)

2005-12-21 Thread Stephen Sprunk
Thus spake [EMAIL PROTECTED] On Wed, Dec 21, 2005 at 11:36:00PM +0100, Daniel Roesen wrote: Really? Where are the limits of BGP? Can you show me any numbers? You'd be the first. I'm not aware of any protocol inherent scaling brickwalls like with other protocols where certain timing constraints

RE: Addressing versus Routing (Was: Deploying IPv6 in a datacenter)

2005-12-21 Thread Hannigan, Martin
Thus spake [EMAIL PROTECTED] On Wed, Dec 21, 2005 at 11:36:00PM +0100, Daniel Roesen wrote: Last time I checked, Ethernet is still CSMA/CD. Ok, sure, half-duplex. People using auto-neg. Only if you're running half-duplex, which is generally an error condition in modern networks.

RE: Addressing versus Routing (Was: Deploying IPv6 in a datacenter)

2005-12-21 Thread Hannigan, Martin
Woops. This is the URL I meant to preface the comment with: http://www.google.com/search?hl=enlr=oi=defmoredefl=enq=define:Interframe+gap -M

Re: Addressing versus Routing (Was: Deploying IPv6 in a datacenter)

2005-12-21 Thread Kevin Day
On Dec 21, 2005, at 1:34 PM, Jeroen Massar wrote:Kevin Day wrote:[..]I agree with your point that currently your IPv4-solution can't beapplied to IPv6 but..(see the helpful and nice thingy part at the end ;)Thanks. I also just want to add that I'm not expecting to be able to do every single thing