[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]


To: mohta@necom830.hpcl.titech.ac.jp (Masataka Ohta)
Cc: hardie@equinix.com, mohta@necom830.hpcl.titech.ac.jp, liman@sunet.se, dnsop@cafax.se
From: hardie@equinix.com
Date: Wed, 7 Jul 1999 09:04:09 -0700 (PDT)
In-Reply-To: <199907070335.MAA11714@necom830.hpcl.titech.ac.jp> from Masataka Ohta at "Jul 7, 99 12:34:58 pm"
Reply-to: hardie@equinix.com
Subject: Re: Order in the working-group!

Masataka,

> 
>   unicast address associated with the root name server.  The other
>   interface, referred to as the AS-internal interface below, should
>   use a distinct address specific to that host.  The host should
> There is no reason to make host specific, globally unique,
> address AS local.

Based on this passage in your draft:

   A possible problem of such addresses is that the shared addresses can
   not be used for global communication. So, it is suggested that the
   root name servers with the administratively scoped shared unicast
   addresses have additional globally unique unicast addresses, which
   may be used for global communication such as zone transfer.

We seem to agree that there should be two addresses, one shared and
one unique.  If you check section 1.2 of my draft, you'll see that I
proposed using the unique address for delivery of zones and
administrative tasks.  If the term "AS-internal" gave you the
impression I meant that address was not globally unique and routable,
the term should certainly be changed.  How does "Shared unicast" and
"Administrative" interfaces strike you as a set of terms to use for
further discussion?


> > If your question
> > is "Why should the shared-unicast addresses have a single origin AS?",
> 
> Wrong question.

Thanks for clearing that up.

> I'm afraid you are not familiar with internet routing with BGP
> and ASes nor its associated problems.

Assuage your fears, Masataka, and be at peace.

> With your proposal, there are multiple ASes sharing the same
> IP address ranges.
> 
> Your proposal does not make the shared address have a single origin.

Not true.  See section 1.5:

  The organization administering the mesh of servers sharing a unicast
  address must have an autonomous system number and speak BGP to its
  peers.  To those peers, the organization announces a route to the
  network containing the shared-unicast address of the root name
  server. 


> As I don't think it worth to repeat the past discussion, see the
> mailing list archive after it is restored.

I believe I have a complete local archive, if you would like to point
me to previous message-ids.


				Ted Hardie


Home | Date list | Subject list