Re: DNS role (RE: NATs as firewalls, cryptography, and curbing DDoS threats.)

2007-03-09 Thread Stephane Bortzmeyer
On Thu, Mar 08, 2007 at 10:41:02AM -0800, Hallam-Baker, Phillip [EMAIL PROTECTED] wrote a message of 115 lines which said: OK lets try code, at the moment to start up a TCP socket you have code of the form: In C. In every other language I know, it is at a much higher level. (Even in C,

Re: DNS role (RE: NATs as firewalls, cryptography, and curbing DDoS threats.)

2007-03-09 Thread Brian E Carpenter
Cc: Harald Tveit Alvestrand; ietf@ietf.org Subject: Re: DNS role (RE: NATs as firewalls, cryptography, and curbing DDoS threats.) Ah. Well I always learnt that an IP network was a connectionless network. Maybe you'd like to define what you mean by a connection. Brian On 2007-03-08 14:42

Re: DNS role (RE: NATs as firewalls, cryptography, and curbing DDoS threats.)

2007-03-09 Thread Douglas Otis
On Mar 9, 2007, at 2:41 AM, Brian E Carpenter wrote: Phill, I'm not playing with words. The style of 'connection' involved in a SIP session with proxies is very different from that of a classical TCP session or a SOAP/HTTP/TCP session, or something using SCTP for some signalling

Re: DNS role (RE: NATs as firewalls, cryptography, and curbing DDoS threats.)

2007-03-08 Thread Brian E Carpenter
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

RE: DNS role (RE: NATs as firewalls, cryptography, and curbing DDoS threats.)

2007-03-08 Thread michael.dillon
One approach for name based authorization would place an encoded hash label of the domain name being authorized within the authorizing domain. Client validation can be as simple as resolving the name of the client, where this name can then be utilized in conjunction with a name

RE: DNS role (RE: NATs as firewalls, cryptography, and curbing DDoS threats.)

2007-03-08 Thread Hallam-Baker, Phillip
PROTECTED] Sent: Thursday, March 08, 2007 5:13 AM To: Hallam-Baker, Phillip Cc: Harald Tveit Alvestrand; ietf@ietf.org 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

Re: DNS role (RE: NATs as firewalls, cryptography, and curbing DDoS threats.)

2007-03-08 Thread Arnt Gulbrandsen
A prediction: Sooner or later, IPv4 addresses become so scarce that renting a colo server with IPv4 becomes more expensive than IPv6. When that happens, a few NAT-hating spoilsports will set up the first few IPv6-only servers and a year later, the transition to IPv6 starts. I wonder what kind

Re: DNS role (RE: NATs as firewalls, cryptography, and curbing DDoS threats.)

2007-03-08 Thread Joe Abley
On 8-Mar-2007, at 10:17, Arnt Gulbrandsen wrote: A prediction: Sooner or later, IPv4 addresses become so scarce that renting a colo server with IPv4 becomes more expensive than IPv6. When that happens, a few NAT-hating spoilsports will set up the first few IPv6-only servers and a year

Re: DNS role (RE: NATs as firewalls, cryptography, and curbing DDoS threats.)

2007-03-08 Thread Douglas Otis
On Mar 8, 2007, at 2:13 AM, Brian E Carpenter wrote: 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

Re: DNS role (RE: NATs as firewalls, cryptography, and curbing DDoS threats.)

2007-03-08 Thread Dave Crocker
Harald Tveit Alvestrand wrote: In my opinion, we should never introduce any function that involves the DNS where: - the answer is required to be different for different requestors - the answer has to be different at two times separated by less than ~seconds - a temporary failure of the

Re: NATs as firewalls, cryptography, and curbing DDoS threats.

2007-03-07 Thread Douglas Otis
On Mar 7, 2007, at 9:01 AM, John C Klensin wrote: It is true that I tend to be pessimistic about changes to deployed applications that can't be sold in terms of clear value. I'm also negative about changing the architecture to accommodate short- term problems. As examples of the latter,

RE: NATs as firewalls, cryptography, and curbing DDoS threats.

2007-03-07 Thread Hallam-Baker, Phillip
layer beneath it. -Original Message- From: Douglas Otis [mailto:[EMAIL PROTECTED] Sent: Wednesday, March 07, 2007 2:33 PM To: John C Klensin Cc: ietf@ietf.org Subject: Re: NATs as firewalls, cryptography, and curbing DDoS threats. On Mar 7, 2007, at 9:01 AM, John C Klensin

DNS role (RE: NATs as firewalls, cryptography, and curbing DDoS threats.)

2007-03-07 Thread Harald Tveit Alvestrand
as firewalls, cryptography, and curbing DDoS threats. On Mar 7, 2007, at 9:01 AM, John C Klensin wrote: It is true that I tend to be pessimistic about changes to deployed applications that can't be sold in terms of clear value. I'm also negative about changing the architecture to accommodate

Re: DNS role (RE: NATs as firewalls, cryptography, and curbing DDoS threats.)

2007-03-07 Thread Douglas Otis
On Mar 7, 2007, at 3:00 PM, Harald Tveit Alvestrand wrote: Here I was thinking that the DNS needs to be an useful name lookup service for the Internet to function, and now PHB tells me it's a signalling layer. Either I have seriously misunderstood the nature of signalling, seriously

RE: DNS role (RE: NATs as firewalls, cryptography, and curbing DDoS threats.)

2007-03-07 Thread Hallam-Baker, Phillip
07, 2007 6:01 PM To: Hallam-Baker, Phillip Cc: ietf@ietf.org Subject: DNS role (RE: NATs as firewalls, cryptography, and curbing DDoS threats.) Here I was thinking that the DNS needs to be an useful name lookup service for the Internet to function, and now PHB tells me it's a signalling

RE: DNS role (RE: NATs as firewalls, cryptography, and curbing DDoS threats.)

2007-03-07 Thread Harald Tveit Alvestrand
--On 7. mars 2007 17:06 -0800 Hallam-Baker, Phillip [EMAIL PROTECTED] wrote: OK I will restate. All connection initiation should be exclusively mediated through the DNS and only the DNS. OK, I'll restate too. In my opinion, we should never introduce any function that involves the DNS