6b508e4c   
   From: Simon.Richter@hogyros.de   
      
   Hi.   
      
   On 2010年06月15日 00:05, David Schwartz wrote:   
      
   > IP unicasts are routable. There's no reason they shouldn't be able to   
   > reach a server on another subnet.   
      
   Right, but for that to work, the client actually needs a route to the    
   server. I'd prefer not to hand out a default route if I cannot actually    
   provide Internet routing, and the "classless static route" option is not   
   supported in all clients.   
      
   > The client would be limited to reaching the server only by broadcast   
   > only until it has an IP address and default gateway. Once it has both   
   > of those, it can reach the server by UDP unicast.   
      
   That was precisely my question: can the client always expect that the    
   server is reachable by UDP unicast, or is there a way for a client to    
   have an address configuration but no working route to the server?   
      
   Apparently, the ISC client implements the latter. The RFC contradicts    
   itself on the use of the server ID field in ACK messages (table says    
   MUST, text says MAY), although it could be interpreted as an omission of   
   redundant information here.   
      
   Hence my confusion.   
      
       Simon   
      
   --- SoupGate-Win32 v1.05   
    * Origin: you cannot sedate... all the things you hate (1:229/2)