North American Network Operators Group

Date Prev | Date Next | Date Index | Thread Index | Author Index | Historical

Re: What is multihoming was (design of a real routing v. endpointid seperation)

  • From: Owen DeLong
  • Date: Mon Oct 24 23:06:01 2005

I believe RFC1122 was written in the days when there was a one-to-one
between IP addresses and interfaces, and, you couldn't have one machine with
multiple addresses on the same network.  Obviously, also, we are talking
network multihoming, not host multihoming in a NANOG context.  It is hard
to perceive a situation where Host Multihoming would require coordination.


--On October 24, 2005 1:31:17 PM -0700 Crist Clark
<[email protected]> wrote:

> Stephen Sprunk wrote:
> [snip]
>>> Other people use this term in very different ways. To some people
>>> it means using having multiple IP addresses bound to a single
>>> network interface. To others it means multiple websites on one
>>> server.
>> That is virtual hosting in a NANOG context.  Some undereducated MCSEs 
>> might call it multihoming, but let's not endorse that here.
> Unfortunately, this is a common and "standards blessed" way to refer to
> any host with multiple interfaces/addresses (real or virtual). For
> example,
> from the "Terminology" section, 1.1.3, of RFC1122, "Requirements for
> Internet Hosts -- Communication Layers," says,
>           Multihomed
>                A host is said to be multihomed if it has multiple IP
>                addresses.  For a discussion of multihoming, see Section
>                3.3.4 below.
> -- 
> Crist J. Clark                               [email protected]
> Globalstar Communications                                (408) 933-4387
> The information contained in this e-mail message is confidential,
> intended only for the use of the individual or entity named above.
> If the reader of this e-mail is not the intended recipient, or the
> employee or agent responsible to deliver it to the intended recipient,
> you are hereby notified that any review, dissemination, distribution or
> copying of this communication is strictly prohibited.  If you have
> received this e-mail in error, please contact [email protected]

If it wasn't crypto-signed, it probably didn't come from me.

Attachment: pgp00057.pgp
Description: PGP signature