DHCP: of course not, its routing address acquisition, not connection initiation Default Gateway: Again no connection. DNS server: of course, it’s a tautology that interactions with the DNS are mediated by the DNS, but again its not connection initiation. The most complicated case here is SLP. The primary problem in SLP is that it has failed to establish a sufficiently diverse adoption community. There are four competing protocols in the space, few signs of life in any of them. The secondary problem in SLP is that it appears to be grounded in the conception of the local network being the locally contiguous network. Using multicast is in theory more scalable than Ethernet broadcast and could take the scheme beyond the SOHO network. In practice you have to believe in Tinkerbell. I don't. Since I can do everything that SLP does using the pure DNS and an announcement service that is my preferred option. If SLP was ubiquitously supported it would be a different matter. Getting three out of four camps to admit that their proposal is not likely to make it and converge on the fourth is likely to be very difficult and the spec that wins is probably not going to do so on technical merit. Again, its five years since this was all promised to the consumer. Grafting the schemas developed onto an existing infrastructure everyone already agrees on is probably an easier prospect politically. > -----Original Message----- > From: Brian E Carpenter [mailto:brc@xxxxxxxxxxxxxx] > Sent: Thursday, March 08, 2007 5:13 AM > To: Hallam-Baker, Phillip > Cc: Harald Tveit Alvestrand; ietf@xxxxxxxx > Subject: Re: DNS role (RE: NATs as firewalls, cryptography, > and curbing DDoS threats.) > > On 2007-03-08 02:06, Hallam-Baker, Phillip wrote: > > OK I will restate. > > > > All connection initiation should be exclusively mediated > through the DNS and only the DNS. > > > > Would that include connections to one's DHCP server, SLP > server, default gateway, and DNS server? > > Hmm... > > Brian >
_______________________________________________ Ietf@xxxxxxxx https://www1.ietf.org/mailman/listinfo/ietf