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


To: Robert Elz <kre@munnari.OZ.AU>
cc: Kenneth Porter <shiva@sewingwitch.com>, <dnsop@cafax.se>
From: Edward Warnicke <eaw@cisco.com>
Date: Fri, 28 Feb 2003 07:31:31 -0500 (EST)
In-Reply-To: <3501.1046430420@munnari.OZ.AU>
Sender: owner-dnsop@cafax.se
Subject: Re: Request for review of DNS related draft

Not everyone is privy to the routing tables.

For example.  Imagine an MGCP call agent which wishes to
perform a maintenance activity that requires the cooperation
of the first hop gateway for an MGCP gateway.  I'm aware
of no MGCP call agent which participates in the IGP for
the networks containing those endpoints.  Additionally
almost all IGPs will allow for some route summarization
which would prevent me from actually knowing who the
first hop gateway is in some circumstances.

So in this example I would either have to provision the MGCP
call agent with information about where the first hop gateway
for each endpoint was, or allow it to use the method of the
draft to resolve it.

Since many of the environments where MGCP is seeing deployment
have a very large number of endpoints, and an unusually large
churn of first hop gateway changes ( think splitting a cable
node ), as well as a tendency toward hierarchical distibution
of control of the network, DNS resolution of this information
seemed to make sense.

The reason RFC 1101 doesn't get used for these sorts of
purposes is that it doesn't support features in common use
in these networks ( variable length subnet masks ).

Ed

On Fri, 28 Feb 2003, Robert Elz wrote:

>     Date:        Thu, 27 Feb 2003 16:01:03 -0500
>     From:        Ed Warnicke <eaw@cisco.com>
>     Message-ID:  <3E5E7C8F.2000404@cisco.com>
>
>   | But DHCP will not allow a device which
>   | is not the endpoint ( or the DHCP server ) to discover the network which
>   | contains
>   | an IP address and the first hop gateway(s) which service that network.
>
> Rather than how, perhaps the question should be why would anyone care?
>
> That's largely why 1101 never got used - the nodes for which it might
> have provided information that could didn't already know it via other
> means, never had much of a reason to care.
>
> Why would my nodes care what the network that contains some random IP
> address might happen to be (or why would I ever care more than the
> routing tables will tell me) ?
>
> kre
>
>



#----------------------------------------------------------------------
# To unsubscribe, send a message to <dnsop-request@cafax.se>.

Home | Date list | Subject list