Brian Lloyd <[EMAIL PROTECTED]> writes:
>
> Pardon me but, horse hocky! We are not talking about objecting to the
> laws but rather how the FBI reacted to a report of a crime. Even tho'
> they were pretty sure that they had been handed a red herring they were
> still required to investigate. M
In message <[EMAIL PROTECTED]>, Paul Ferguson typed:
>>I wouldn't be so quick to characterize NAT as a "dead-end" technology.
i would.
NATs are classic short term optimisation kills long term benefoit of
the right way of doing things. also:
for NATs to scale to deal with the global net comple
Unsubsribe
John,
> You are absolutely right. Time should be spent developing "good
> algorithms" which is common "good architecture". What NAT does is just
> another form of the same thing that X.25, ATM, and MPLS do with different
> identifiers. It is not bad algorithm there nor bad architecture.
This
At 22:52 30.11.99 -0500, John Day wrote:
>At 18:12 -0500 11/30/99, Mark Atwood wrote:
> >John Day <[EMAIL PROTECTED]> writes:
> >>
> >> Correct. Lets get an application name space so we don't need to worry
> >> about it.
> >>
> >
> >Please gods below, not more ASN.1
>
>What a strange reaction!?
unsubscribe
unsubscribe
At 10:49 PM 11/30/99 -0500, Keith Moore wrote:
>note also that DNS is often slow, and seems less reliable than IP.
>by increasing the reliance on DNS you increase the probability of failure.
Data point: out of 40,000 random DNS requests logged on my work station
over the last year, 20% underwen
Bob,
Bob Braden wrote:
>
>*>
> *> The problem is not to make applications "NAT aware" or "NAT friendly". The
> *> problem is to make applications "IP address unaware". What is an
> *> application doing exchanging and using names for things 2 layers below it?
> *> Sounds like a desi
*> >
*> > I don't believe this argument, John. The IP address is (part of) the
*> > transport layer end point address, something that an application can
*> > reasonably be expected to know about in the existing Internet
*> > architecture.
*>
*> Unfortunately the existing Internet
>John,
>
>> You are absolutely right. Time should be spent developing "good
>> algorithms" which is common "good architecture". What NAT does is just
>> another form of the same thing that X.25, ATM, and MPLS do with different
>> identifiers. It is not bad algorithm there nor bad architecture.
At 11:50 -0500 12/1/99, Brian E Carpenter wrote:
>Bob,
>
>Bob Braden wrote:
>>
>>*>
>> *> The problem is not to make applications "NAT aware" or "NAT
>>friendly". The
>> *> problem is to make applications "IP address unaware". What is an
>> *> application doing exchanging and using nam
At 7:06 -0500 12/1/99, Harald Tveit Alvestrand wrote:
>At 22:52 30.11.99 -0500, John Day wrote:
>>At 18:12 -0500 11/30/99, Mark Atwood wrote:
>> >John Day <[EMAIL PROTECTED]> writes:
>> >>
>> >> Correct. Lets get an application name space so we don't need to worry
>> >> about it.
>> >>
>> >
>> >P
John Day wrote:
> Cmon, surely you can come up with a better counterargument than that! ;-))
> I certainly could. If it is architecturally acceptable for those protocols
> to rewrite the address field at every hop, why shouldn't it be for IP? How
> does it differ? Basically a NAT is doing wha
unsubscribe
Everyone, this conversation isn't really going to be very productive. The
people who like A aren't about to start liking B, and vice versa. (And then
there are the people who don't like either - but they aren't going to change
their minds either! :-) So discussion on this point is not going to be
Christian:
Is this something that you think is an inherent flaw in DNS? Will this new class
of servers be less susceptible to congestion?
Cary.
Christian Huitema wrote:
> At 10:49 PM 11/30/99 -0500, Keith Moore wrote:
>
> >note also that DNS is often slow, and seems less reliable than IP.
> >
unsubscribe
Unsubsribe
>>It seems to me that we may be able to recapture some aspects of end-to-end
>>transparency at the application level if addressing issues are focused on
>>host FQDNs, rather than IP addresses.
>this works to some extent. it specifically doesn't work for applications
>that need to rendezvous with
So we want some application level namespace and a system to translate
it to addresses. What characterstics should such a system have? It
needs to be highly available, so you need replication among multiple
servers. You can't concentrate all the data in one place so it needs
to be distributed, p
Christian,
> Increasing our reliance on the DNS is definitely not a good idea.
Hmmm. This would appear to be the exact opposite of what the IETF has done
with IPv6.
Rgds,
-drc
Cary,
> Is this something that you think is an inherent flaw in DNS?
Inherent flaw in the DNS: probably not. Inherent flaws in implementations of
DNS (including, of course, ISC's BIND) and things in front of the DNS:
probably. It is far too easy to do the wrong thing.
And if this is true to
> > Is this something that you think is an inherent flaw in DNS?
>
> Inherent flaw in the DNS: probably not. Inherent flaws in implementations of
> DNS (including, of course, ISC's BIND) and things in front of the DNS:
> probably. It is far too easy to do the wrong thing.
this is worth elabo
Date: Tue, 30 Nov 1999 23:40:06 -0800 (PST)
From: Brian Lloyd <[EMAIL PROTECTED]>
Pardon me but, horse hocky! We are not talking about objecting to the
laws but rather how the FBI reacted to a report of a crime. Even tho'
they were pretty sure that they had been handed a red herr
Bill and all,
Ok, thanks for the update on your status. Much appreciated.
Were you able to provide a contact for Joe? Given your
generic comments below that does not at all seem clear or
likely in the near term.
Bill Manning wrote:
> > >
> > > Is there a name there at iana of someone who ca
Well - Bill told me he could help them out. I didn't want to burden
anyone with it unnecessarily.
This whole iana trip is a really big bother. Information is always
outdated, updates are never on time. And when updates are done - critical
information like whois servers are not properly recorde
Joe and all,
! wrote:
> I've been doing our little annual update with the cctld community -
> basically verifying that what is contained in the iana database is
> correct. And usually it's not.
You mean as usual don't ya Joe? >;)
>
>
> This year - I'm being approached by alot of tld admins
Thanks Jeff - i've sent a note to manning and have advised the cctld admin
accordingly.
On Wed, 1 Dec 1999, Jeff Williams wrote:
> Joe and all,
>
> ! wrote:
>
> > I've been doing our little annual update with the cctld community -
> > basically verifying that what is contained in the iana data
> >
> > Is there a name there at iana of someone who can be responsible enought to
> > get this done.
>
> Try Bill Manning. I don't have his E-Mail address handy though.
>
Bill Manning has not had anything to do with the IANA task for
a long time. He is busy with other activ
30 matches
Mail list logo
