Stories
Slash Boxes
Comments

News for nerds, stuff that matters

Slashdot Log In

Log In

Create Account  |  Retrieve Password

IPv6 Tested in Space

Posted by CmdrTaco on Sun Apr 08, 2007 09:59 AM
from the still-nobody-using-it-down-here dept.
An anonymous reader writes "Remember the Cisco router orbiting on a satellite in space? Well, it's now also the first to run IPv6 in space. Since no-one is choosing to run IPv6 on the ground, isn't this a bit pointless?"
+ -
story

Related Stories

[+] Router Tested On Satellite In Space 21 comments
The Cisco router launched into orbit in September onboard a satellite built by SSTL (and on a Russian rocket) has now been successfully tested in space, and there's a video describing this and putting routers in space. A neat twenty-year coincidence here: an early Surrey satellite has been operating for twenty years, and Cisco launched its fastest router on its twentieth birthday. What do the next twenty years hold for fast routers in space?
[+] Technology: Interplanetary Internet Tested In Space 124 comments
Anonymous Coward writes "After Vint Cerf planned the Interplanetary Internet, there's a press release saying that the Interplanetary Internet is now being tested in space, using the Bundle Protocol developed by the Delay-Tolerant Networking Research Group. There's a conference paper with details on the testing too. These guys were previously the first to test IPv6 in space. Now they've found something with even fewer users than IPv6 to play with!"
This discussion has been archived. No new comments can be posted.
The Fine Print: The following comments are owned by whoever posted them. We are not responsible for them in any way.
 Full
 Abbreviated
 Hidden
More
Loading... please wait.
  • Pointless? No. (Score:5, Interesting)

    by dreamchaser (49529) on Sunday April 08 2007, @10:03AM (#18655213) Homepage Journal
    If you're going to start putting Interplanetary WAN infrastructure in place, might as well go IPv6 from the get go. Then once there are a few billion nodes scattered about the Solar System we won't have any addressing problems ;)
  • by m0ng0l (654467) on Sunday April 08 2007, @10:06AM (#18655233)
    No, testing it in space isn't pointless! If the IPv6 stack fails catastrophically, there's no one around to be hurt by the flying shrapnel!

    I mean after all it might even potentially set the Earths atmosphere on fire, if it were testing on the ground!
  • IP in Space (Score:5, Informative)

    by Anonymous Coward on Sunday April 08 2007, @10:08AM (#18655237)
    This is nothing new. The ill fated STS-107 carried a complete CANDOS pacage offering a wealth of IP protocols. In fact UoSat-12 back in May of 2000 ran an ftp server. The only thing new here is IPV6. IPV4 has been in space for a long time. You an find more about this at our website http://ipinspace.gsfc.nasa.gov/ [nasa.gov]

    Thank you,
    your NASA team
  • Cosmic Rays cause Cisco routers to break enough on Earth, wouldn't the effect be multiplied with them being in space?
  • by ReinisFMF (893095) on Sunday April 08 2007, @10:25AM (#18655315)
    Everybody knows that satellites go round faster than earth rotates. The tubes would certainly break!
  • Cisco - we hold 100% of the IPv6 market*

    Cisco - We circle the globe with IPv6 support.

    Cisco - THE standard for aerospace IPv6 deplyment archetecture.

    Cisco - Our IPv6 technology is rated "higher" than any of our competitors.

    *in space
      • Re: (Score:3, Funny)

        by Stormwatch (703920)

        When I see "Cisco" I think "Crisco". O_o
        And when I see "Cisco" I think "Star Trek: Deep Space Nine".
  • by kimvette (919543) on Sunday April 08 2007, @10:35AM (#18655377) Homepage

    Since no-one is choosing to run IPv6 on the ground, isn't this a bit pointless?


    Why is no one running IPv6 on the ground? Well, I'll tell you why I don't run it:

    • Neither of my ISPs (work or home) supports it
    • NONE of my routers support it
    • A lot of applications I run don't support it
    • Dealing with it on apache would be a PITA, wouldn't it?


    Besides, who wants to deal with IPv6 when dotted quads are easier to memorize? Just wrench the class A address assignments away from the current assignees (not a single one of them needs a class A block) and reallocate them reasonably. Apple does not need a class A block, Merck doesn't, HP doesn't, GE doesn't, IBM doesn't, MIT doesn't. Halliburton doesn't, and the DoD certainly does not need multiple /8 assignments. Besides, isn't the DoD largely on IPv6 now? Reallocate the IPv4 space reasonably, force organizations such as Apple, HP, IBM, Merck, and Halliburton justify their IP allocation request like I had to for my puny /27 block, and then there will be plenty of space for all.
    • 6e9>256*256*256*256
    • Re: (Score:3, Interesting)

      by thegameiam (671961)
      I agree about the downsides of running IPv6, but pulling the /8 assignments from the current assignees would be a lot of headache and trouble for not so much benefit - yeah, a couple of those could be returned easily (probably not the DoD ones - they already returned the ones they don't need anymore) (and you forgot to mention that Level3 currently owns 3 /8s due to their purchase of BBNPlanet (AS1), and that would add maybe an additional year at our current run rate, but we'll come to a point where we need
    • by LighterShadeOfBlack (1011407) on Sunday April 08 2007, @11:14AM (#18655641) Homepage

      Besides, who wants to deal with IPv6 when dotted quads are easier to memorize? Just wrench the class A address assignments away from the current assignees (not a single one of them needs a class A block) and reallocate them reasonably. Apple does not need a class A block, Merck doesn't, HP doesn't, GE doesn't, IBM doesn't, MIT doesn't. Halliburton doesn't, and the DoD certainly does not need multiple /8 assignments. Besides, isn't the DoD largely on IPv6 now? Reallocate the IPv4 space reasonably, force organizations such as Apple, HP, IBM, Merck, and Halliburton justify their IP allocation request like I had to for my puny /27 block, and then there will be plenty of space for all.
      - And who wants to deal with dotted quads when a single digit is even easier to memorise. Except that wouldn't be much good when the 11th person comes along and asks for an IP address would it? Same with IPv4. We will run out of IPv4 addresses. Maybe not today, tomorrow or even next year, but short of the annihilation of civilisation as we know it it will happen sooner or later. It doesn't matter if we liberate x hundred million unused addresses, that will only delay the inevitable by a few years or maybe a decade at most.

      The real PITA then, is trying to get people to do something about this problem before it really becomes a problem. People keep commenting on the slow transition to IPv6 as if it's a failure of the protocol. No, as you implied, it's a failure of the software developers who aren't implementing it, the hardware manufacturers who aren't supporting it, and the ISPs who aren't providing it. Instead of trying to free up more IPv4 address space we should be letting it become a scarce resource to force the guilty parties to make the necessary updates so that nobody's caught short on that fateful day when we well and truly are out of IPv4 addresses. We should be taking every step possible to limit the amount of software and hardware from being deployed that we already know will be useless a couple of decades from now, instead it seems like so many people are quite happy to take their sweet time with it until alarm bells start ringing.

      You'd think with things like the Y2k bug and numerous other situations which exposed the fallacies of the "it'll do for now, we'll deal with that later" ideology that the computing industry would be all too happy to see that the IP address situation was spotted well ahead of time and would be embracing the ability to future-proof their software and IT infrastructures. Instead it seems like we're going to have another case of fingers-in-their-ears-"la-la we're not listening - oh shit! we're out of IP addresses!" situation with a mad dash to half-assed implementations and slap-dash patches.
    • by vertinox (846076) on Sunday April 08 2007, @11:21AM (#18655701)
      Reallocate the IPv4 space reasonably, force organizations such as Apple, HP, IBM, Merck, and Halliburton justify their IP allocation request like I had to for my puny /27 block, and then there will be plenty of space for all.

      If I may make a car analogy...

      Let us say that IPv4 is the oil we get from the ground and all cars run off it. Then a small group of scientists do a study and say discover "Egads! We've only got 10 years worth of oil left!"

      Everyone panics and the scientists come up with a pure ethanol based car (IPv6) that has none of the limitations of oil when it comes to making new ones (In theory we could eventually use up all our natural resources in production of corn, but that would take thousands of years so that is someone eles's problem)

      However, such a switch over would cost millions if not billions of dollars spent replacing all the oil based motors, but they start the work.

      Then.... Some smart ingenious mechanic finds a way to make regular engines work off 50% ethanol and 50% oil (NAT addressing) and everyone goes "Phew! Problem solved!"

      However, that doesn't resolve the fact that oil is still going to run out in 20 years but by then that will be someone else's problem.

      But in reality, I think the US, Canada, and Europe will switch to IPv6 when their counter parts in China and India surpass us economically in 10 to 20 years. (As in Chinese companies start buying US companies and then tell their network departments to migrate so they can communicate better)

      Asia is the big pusher for IPv6 because they simply did not get any of the IPv4 to start with and NAT isn't helping them much considering they will have literally the majority of world's internet users. Unless, like you say, the big US tech companies give up the IPv4 spaces to companies in Asia I think they are on the path to complete IPv6 networks over there.

      Either way... I think most of us will get IPv6 equipment when it was cheaper for the manufacture to not disable the feature in our standard IPv4 products (think built in modem or video into the mother board trend) but this might be some time from now.
      • Re: (Score:3, Insightful)

        ...But in reality, I think the US, Canada, and Europe will switch to IPv6 when their counter parts in China and India surpass us economically in 10 to 20 years...

        The main problem with your theory is that China and India are unlikely to surpass us economically in 20 years. To illustrate my point, let's compare the US and China. According to wikipedia [wikipedia.org] the US GDP is approx $12.5 Trillion. The Chinese GDP is about $2.2 Trillion. If the US economy had zero growth for 20 years, and the Chinese economy wou

          • Re: (Score:3, Informative)

            To quote wikipedia [wikipedia.org] ..."The differences between PPP and market exchange rates can be significant. For example, the World Bank's World Development Indicators 2005 estimates that one United States dollar is equivalent to approximately 1.8 Chinese yuan by purchasing power parity in 2003. [1]. However, based on nominal exchange rates, one U.S. dollar is currently equal to 7.9 yuan. This discrepancy has large implications; for instance, GDP per capita in the People's Republic of China is about US$1,800, while on
    • by Znork (31774) on Sunday April 08 2007, @11:29AM (#18655775)
      "Neither of my ISPs (work or home) supports it"

      You dont need their support. Use 6to4. Or a tunnel.

      "NONE of my routers support it"

      You dont need them to. Use 6to4.

      "A lot of applications I run don't support it."

      Some do tho. It's wonderful to be able to ssh and scp directly into the boxes you have behind a NAT gateway without having to resort to two-stage jumps.

      "Dealing with it on apache would be a PITA, wouldn't it?"

      No.

      "who wants to deal with IPv6 when dotted quads are easier to memorize?"

      There's this new development called DNS you know...

      "Just wrench the class A"

      Mmm, like that's going to happen...

      Meanwhile I sit here on a bazillion addresses, merit of having one single v4 address. Get with the times, it's not like IPv6 is rocket science anymore.
        • Re: (Score:3, Interesting)

          by Tony Hoyle (11698)
          It's quite common not to route 6to4. The ISP I'm with now is the first I've had in 3 years to route 192.88.99.1 and they've got native ipv6 anyway.

          Tunnels I can sympathise. No quality. Abysmal uptime, and nobody to complain to if it goes wrong.. not to mention that 90% of the people who were providing them have packed up and gone home when the 6bone went titsup. I eventually gave up on my hosting machines' ipv6 after I did the uptime graphs.. uptime was about 30%, and the latency never got less than 500
    • Besides, who wants to deal with IPv6 when dotted quads are easier to memorize?

      And I forgot to add... Who memorizes IP addresses anymore?

      I used to back in the day, but DHCP isn't as flaky anymore so no need for static IP on the OS side and if your router setup is worth a snuff you can assign a static IP via DHCP based of your NIC's MAC address so it gets the same IP address each time. And since most people are blocking use of their DNS servers unless you are on their network also makes it pointless to know I
            • Re: (Score:3, Insightful)

              If you're going to flame, I'm going to flame. You're an idiot.

              He never said that knowledge of IP addresses is totally unnecessary, he said that memorization of IP addresses is unnecessary.

              New and different technology means new and different ways of management. Just because it means you have to re-think how you manage and impliment things doesn't mean that it's a bad thing or bad idea..

              Once again: "Somehow, you are suggesting that knowledge of IP addresses is totally unnecessary on the administration a
    • by Ephemeriis (315124) on Sunday April 08 2007, @11:46AM (#18655939) Homepage
      While it is certainly true that there aren't a whole ton of home routers that support IPv6 yet, it's on the way. Vista installs IPv6 by default and it's a pain to get rid of it. Vista tells you you've got full IPv4 connectivity, but limited IPv6 connectivity...and I've already had one client ask me what that meant, and how he could get full IPv6. Folks will buy an IPv6 router just because it's got a bigger number...and now that Vista advertises IPv6 connectivity, people will be aware that there is a bigger number to be had.

      Plus, some stupid applications insist on trying IPv6 if it is installed and wait forever for the packets to time out... A common problem I ran into with folks who tinkered under XP was massive slowdowns with Firefox after someone had installed IPv6. Remove IPv6 and everything was fine. Of course...Vista doesn't like it when you try to remove IPv6... Haven't had any calls about slowdowns yet...maybe Vista handles the stack better than XP did...

      As far as "no-one is choosing to run IPv6 on the ground"... Well, that's just not true. Many ISPs are running IPv6 on their internal networks. You'll never see it because your modem/router/LAN live in an IPv4 tunnel...but it's there. I know I've seen Job Ads for the local hospital asking for IPv6 experience as well...though I don't know if they're actually using it yet or just preparing for the future.

      "Dotted quads" may be easier for you to memorize...but I suspect this is largely because that's what you're dealing with on a day-to-day basis. Remember when you were little and it was hard to memorize addresses or phone numbers? Now that seems incredibly simple, doesn't it? Remember when you were just learning IP and wondered why you couldn't use DNS for absolutely everything (because names are so much easier to memorize than numbers). Plus, IPv6 supports a couple different ways to abbreviate [wikipedia.org] addresses...such as stripping leading 0's or replacing them with :: Which makes our old friend 127.0.0.1 something much easier to remember - ::1

      And simply re-allocating the IPv4 address space just isn't going to cut it. There aren't enough addresses out there. The only reason we've been able to stay with IPv4 for so long is NAT, which causes problems [wikipedia.org] of its own. The bottom line is that we need more addresses than IPv4 has.
      • Re: (Score:3, Interesting)

        by thegameiam (671961)
        I'd challenge the assertion that "many ISPs are running IPv6 on their internal networks" - the only ISP which has made any sort of argument that running IPv6 as a core service (rather than an edge service across the existing IPv4 core) is Comcast, and that has to do with the number of devices they're trying to manage with regard to set-top-boxes.

        Comcast is nowhere near implementing this, either.

        The US ISPs either run IPv6 as an edge service (in a VRF, say) or using tunneling approaches, or on limited deploy
        • Re: (Score:3, Interesting)

          by Ephemeriis (315124)
          Perhaps I am wrong... One of our larger local ISPs is rolling out its own fiber and offering a comprehensive package that includes broadband, unlimited phone, and video - and they're using IPv6 on their internal network. The end user doesn't see that though...they get an IPv4 address on their broadband router, just like with a regular cable/DSL connection. I just assumed that if a local ISP here was doing IPv6 internally that more worldwide would be doing so.
              • Re: (Score:3, Informative)

                by slamb (119285) *

                I've done work on their devices more than once and can attest that they are running IPv6 - a separate address for each interface on the device: bandwidth, video, phone. I have been told by their installers that this is typical and that their internal equipment is all running IPv6, though I have no proof of that myself.

                That doesn't mean they're running it. My MacBook right now says this:

                [slamb@spiff ~]$ /sbin/ifconfig en1
                en1: flags=8863<UP,BROADCAST,SMART,RUNNING,SIMPLEX,MULT ICAST> mtu 1500
                ine

          • Sprint & Verio (Score:3, Interesting)

            by thegameiam (671961)
            I assume by "Verio" you mean NTT (AS2914). NTT is an incumbent Japanese telco, which bought the US-based Verio some years ago. I know that NTT offers IPv6 services, and their brochure is here [ntt.net], which claims that they're running dual stack on all of their routers. That brochure also claims that they have 500 customers for their IPv6 services, and claims that they're the largest provider of IPv6 in the world.

            As for Sprint, they often brag about their L2TPv3 core, with MPLS, and other private-IP services off
  • By using an obscure and unused protocol they are able to confuse most hackers.
     
  • Mars needs IP space!

    - Necron69

    ps. Take my bitch ex-wife while you are at it.
  • by WindBourne (631190) on Sunday April 08 2007, @11:08AM (#18655593) Journal
    Since nobody runs ipv6????? Sad, that so many Americans are clueless. Asia has moved into IPv6 in a big way, esp. China. They are all hoping to get a jump on it before we do. China, Japan, and even South Korea have pushed it like there is no tomorrow.
    • Re: (Score:3, Informative)

      by thegameiam (671961)
      sort of - there's a lot more IPv6 there than here, but there are still a whole bunch of thoroughly under-implemented pieces of IPv6 (like, has anyone written an actual implementation of IPv6Sec yet?), and actual traffic rates using native v6 native v6 all the way through are exceptionally low.

      If you go to one of the good latency calculators [sixxs.net], you'll see that the delta between IPv6 performance and IPv4 performance is substantial, with IPv6 performance showing as a heck of a lot worse (about twice as poor).
      • Re: (Score:3, Insightful)

        by GooberToo (74388)
        Isn't that because it's tunneling IPv6 over IPv4? So of course the latency is going to be much higher. I would be hard pressed to imagine why latency would be higher for IPv4 versus IPv6 so long as it's an apples to apples comparison. If what I read is correct on the URL you provided, it's like comparing IPv4 verses IPv4 traveling over an VPN. So of course the latency is going to be higher...but one has nothing to do with the other if a fair comparison is your intention.

        Please correct me if I failed to
    • by ffejie (779512)
      Nobody runs IPv6 -- yeah, like your rinky-dink corporate network. You know, no one, except the federal government and the 3 of the 4 largest service providers supporting them. Networx deal [telephonyonline.com].
      • Re: (Score:3, Informative)

        by thegameiam (671961)
        None of the significant US ISPs support native IPv6 transport across an infrastructure without any IPv4 present at this time.

        No government agency does either.

        Evidence? Try to get OSPFv3 working without an IPv4 router-ID. Try to get encryption (IPv6SEC) working without using IPSEC (over IPv4 transport). Try getting VoIPv6 working, or looking for hardware support for multiple queues for IPv6 packets.

        Networx was just awarded a couple of days ago, and specifies those services which are to be orderable over t
        • Re: (Score:3, Informative)

          by anticypher (48312)
          Try to get OSPFv3 working without an IPv4 router-ID

          Router IDs, at least in OSPF (all versions) and BGP, are not IPv4 addresses. They are a 32 bit number, that in some implementations are displayed as dotted quad. It is only common practice to make your publicly available router ID to match one of your assigned IPv4 addresses, so that collisions between Router IDs will rarely happen.

          I still run across companies that have router IDs of 1, 2, 3 etc. Some router implementations will randomly grab the lowest IP
          • Re: (Score:3, Informative)

            by thegameiam (671961)
            Many governement projects treat IPv6 support as a checkbox, not as something to be actually used. There are big, big, holes in the implementations, and nobody really wants to go first...
      • Re: (Score:3, Informative)

        by WindBourne (631190)
        My contract with Jeppesen ran out in Sept. Since early Feb, I have been working at Verizon Business. Please look up the players in Networx. I can tell you that very little IPv6 is currently being used. The FEDS are wanting to move to IPv6, but none of the players in Networx currently use it (they have small networks of it, but they are all IPv4 shops). Hopefully, that contract will change things.
  • New meme (Score:5, Funny)

    by bcmm (768152) on Sunday April 08 2007, @11:41AM (#18655897)
    Pretty please can we make this into a new meme?
    Examples:
    • IPv6 Tested ...in Space
    • SCO Vs. IBM Leaks Exposed ...in Space
    • O'Reilly Opens Online Tech School ...in Space
    • Microsoft Opposing California Open Doc Bill ..in Space
  • For this configuration exploit [securitytracker.com], this SNMP vulnerability [cisco.com], this IP sequence generation problem [securityfocus.com], this ICMP vuln [auscert.org.au], this H.323 problem [auscert.org.au], and this buffer overflow [auscert.org.au].

    NOTE: Some of the listed problems indicate a "Cisco 3200 Catalyst", which may not be the same as the orbiting "Cisco 3200 Mobile Access Router". IANACG (I am not a Cisco geek).
  • Slightly off topic, but if there was some way I could figure out how to connect to and hack the ISS computers, I'd love to get in there and replace whatever is on the display to read simply "All of these worlds are yours except Europa. Attempt no landing there".

    It'd have a fun effect, to be sure.
  • by shaitand (626655) on Sunday April 08 2007, @01:04PM (#18656497) Homepage Journal
    Start an open site dedicated to CONTENT providers who have made their content available for IPv6 and give blue ribbon graphics to IPv6 only sites. Then.. and this is the biggest one.

    Make getting address space cheap and easy!!! IPv6 is huge, why do I have pay ridiculous recurring fees to get a block? Make small allocations free, registration free and online, then just make me return a confirmation letter/call/email once every 5 years to renew. IPv6 space is monstrous, it is terrible that you have to pay outrageous fees to become a member organization and then huge recurring fees for addresses. Why do ISP's have to go through the same backflips and outrageous pricing schemes that served to reduce demand for IPv4 addresses.

    Once you have major content providers onboard and make it free and easy to get address space, then ISP can advertise access to the 'NEW AND IMPROVED' internet.
    • Re:Not true (Score:4, Interesting)

      by pla (258480) on Sunday April 08 2007, @10:36AM (#18655383) Journal
      There are many large business models that depend on it.

      Such as?

      First, what does a networking potocol have to do with a business model; And second, how can any company survive with a business model dependant on something not supported by most ISPs?



      Serious questions, not sarcasm.
      • Re: (Score:3, Insightful)

        First, what does a networking potocol have to do with a business model;

        Go look up Communication clients and services, from simple IM and Voice to remote clients and client tracking.

        And second, how can any company survive with a business model dependant on something not supported by most ISPs?

        Go look up, "tunneling."
      • Re: (Score:2, Informative)

        by nevali (942731)
        3G mobile networks utilise IPv6, AIUI; I've a feeling it's part of the specs (well, everything is specified somewhere in mobile telco land), which makes it part of the business model.
      • Such as?
        • Apple's OS X Bonjour relies on it.
        • French telecoms have it
        • Chinese telecoms have it

        First, what does a networking protocol have to do with a business model

        • Apple: OS X is a cornerstone of their business model - Bonjour is a cornerstone of OS X
        • France: Great way to get govt. funding for R&D and keep a telecom business alive while you develop
        • China: Great way to get govt. funding and keep a telecom business or two alive while they develop

        And second, how can any company survive with a busine

        • um, no. (Score:3, Informative)

          by thegameiam (671961)
          Bonjour does not rely on IPv6 - IPv6 autoconf was based on Appletalk autoconf, as was Apple's Bonjour (formerly Rendezvous). Bonjour works just fine with no v6 on the network.

          And Apple's business model is absolutely not dependent on Bonjour: I think perhaps you are misunderstanding the term "business model." An example of a business model is:

          "We give away high-quality software for free to get people to buy our hardware, where we make high margins" - that's an example of Apple's business model.

          "By becoming
      • Re:Not true (Score:4, Interesting)

        by Kizeh (71312) on Sunday April 08 2007, @01:05PM (#18656503)
        Cellular carriers have looked at it very seriously for the next generation (4G?) networks, as one potential idea is to do packetized voice, and the number of addressable devices is potentially huge, and depending on how mobility is done, each device may need several addresses.

        The U.S. federal government has mandated it, so anyone wishing to get into that business needs it.

        That being said, my university has been running IPv6 for a few years now -- we luckily have native IPv6 feed from I2 -- and all of our routers (Cisco IOS), servers (various variants of Linux) and clients (MacOS X, Linux, Windows XP) have supported it just fine.
    • Re: (Score:3, Insightful)

      by thegameiam (671961)
      IPv6 is one possible solution to the address shortage (which is hardly at the *dire* stage, but will be soon enough). Other solutions include widespread adoption of NAT and/or adopting some entirely different layer-3 paradigm.

      The IPv6 designers have hampered adoption by insisting on solving problems which are not directly related to address size (like autoconfiguration, QoS, etc) and rolling those into the protocol - because so many of these useful features which were steadily glommed onto IPv4 have not ye
        • Re: (Score:3, Interesting)

          by thegameiam (671961)
          Oh believe me, I'm familiar with ARIN's policies: I'm one of the people who argued for the adoption of PI (provider independent) allocations as opposed to PA-only allocations, which was the policy for a very long time.

          IPv6 was designed by a lot of smart people who work on end-systems, with not a whole lot of folks who actually run very large networks being involved - that's why multihoming still remains a problem (yes, yes, I know, get some PI-space, or is Shim-6 still the suggested approach? Oh wait, that