Rob,

Sorry for not responding sooner.

The emphasis in the definition is "with out any dependence on resources 
other than are needed".  This would allow relay agents in routers or DHCP 
servers in DNS servers.

There are issues raised in solutions like this to insure that the 
co-located services are adequately tied together.  For example in case of a 
"DHCP server in the DNS server" the processes need to be tied together in a 
manner that the DHCP process would not provide the address of the DNS 
server if the DNS server process was down.  Or that the DHCP server not 
provide the addresses for other DNS serves unless it knows that they are up 
and available.

So I think the examples you raised do fit with the definition.  My intent 
was that the requirements should allow for a of number different 
solutions.  Picking a specific solution requires evaluating the strengths 
and weaknesses of the specific solution.  I think this falls into the 
"Desirable aspects" part of the text, as opposed to the basic requirement.

Bob

>However, since you did ask a direct question, I'll try to answer it.
>
> > For this requirement, Server-less is defined to mean the DNS
> > information is learned with out any dependence on resources other
> > than are needed (i.e., links, interfaces, routers, and DNS server)
> > to communicate with the DNS server.
>
>Comments:
>
>   The term "DNS server" is not well defined at the level of detail
>   that this problem statement requires.  Is an entity that implements
>   both the DNS server role and portions of the DHCP server role a "DNS
>   server" within the meaning of this definition?
>
>   The term "router" is not well defined at the level of detail that
>   this problem statement requires.  Eg, would DHCP relay agents
>   co-resident with routers be parts of the routers within the meaning
>   of this definition?
>
>In all seriousness: I can't tell you whether I agree with your
>statement of the problem until I know what what the words mean.


--------------------------------------------------------------------
IETF IPng Working Group Mailing List
IPng Home Page:                      http://playground.sun.com/ipng
FTP archive:                      ftp://playground.sun.com/pub/ipng
Direct all administrative requests to [EMAIL PROTECTED]
--------------------------------------------------------------------

Reply via email to