RE: Palladium (TCP/MS)

2002-11-01 Thread Sean Jones
Good Morning Valdis > -Original Message- > From: [EMAIL PROTECTED] [mailto:Valdis.Kletnieks@;vt.edu] > Sent: 29 October 2002 15:39 > To: Sean Jones > Cc: [EMAIL PROTECTED] > Subject: Re: Palladium (TCP/MS) > You're close. You'd want this for multihomed servers, so a > PTR query works

Re: Palladium (TCP/MS)

2002-11-01 Thread Valdis . Kletnieks
On Fri, 01 Nov 2002 08:48:35 GMT, Sean Jones said: > Forgive my ignorance, but I thought email was handled by Mail eXchange (MX) > records, thus a PTR would not be required? Just because an MTA follows an MX to find where to send a piece of mail doesn't mean that other things don't use PTR record

Re: Palladium (TCP/MS)

2002-11-01 Thread John Stracke
Sean Jones wrote: I understand where I went wrong. But I doubt that any commercial enterprise would want to block access to MS servers in RL. Well, it'd be a good way to inhibit people from sneaking Windows into the company. -- /===

Re: mail headers for announce

2002-11-01 Thread Keith Moore
> > The recipient list is a pretty poor way to deal with things when you > > get mail sent to multiple lists you're on, and often the To: line ends > > up with nothing at all. The Return-Path: is generally the surest way > > to know which of the lists each of the messages was sent to. I've > > trie

Re: mail headers for announce

2002-11-01 Thread Dave Crocker
Perry, Wednesday, October 30, 2002, 1:38:54 PM, you wrote: Perry> As I use Return-Path: headers to filter my mail, this has gotten Perry> annoying, Yes, I can indeed kludge around it, but is there a Perry> particular reason for this being done? Using return-path is a bit like paying attention to

kernelizing the network resolver

2002-11-01 Thread V Guruprasad
Hi everyone, Please check out http://infs.sourceforge.net for a novel INternet FileSystem (INFS) package which appears to be ideally suited to cell phones and other small devices or appliances. By pushing the DNS resolution to the kernel, INFS means to achieve the following: - eliminates socka

Re: Palladium (TCP/MS)

2002-11-01 Thread Valdis . Kletnieks
On Fri, 01 Nov 2002 09:10:59 EST, John Stracke <[EMAIL PROTECTED]> said: > Sean Jones wrote: > >I understand where I went wrong. But I doubt that any commercial enterprise would >want to block access to MS servers in RL. > Well, it'd be a good way to inhibit people from sneaking Windows into > t

RE: Palladium (TCP/MS)

2002-11-01 Thread Sean Jones
Good Afternoon again Valdis > -Original Message- > From: [EMAIL PROTECTED] [mailto:Valdis.Kletnieks@;vt.edu] > Sent: 01 November 2002 13:35 > To: Sean Jones > Cc: [EMAIL PROTECTED] > Subject: Re: Palladium (TCP/MS) > Received: from mm_w2k1.micromedical.local > (mailgate.peakflowmeter.c

Re: mail headers for announce

2002-11-01 Thread John Stracke
Dave Crocker wrote: Using return-path is a bit like paying attention to what mailbox a postal letter is dropped into. Or perhaps what post offices it went through on the way. -- /===\ |John Stracke |[EMAIL PROTECTED]

Re: kernelizing the network resolver

2002-11-01 Thread John Stracke
V Guruprasad wrote: - eliminates sockaddr_t handling in the user space, allowing application code to become free of IPv4/IPv6 (or for that matter raw Ethernet or ATM) dependencies; Doesn't using a shared library for the resolver give you the same benefit? It's in user space, but it's not in

Re: anyone remember when the root servers were hi-jacked? (fwd)

2002-11-01 Thread Dave Crocker
Michael, Thursday, October 31, 2002, 6:28:08 PM, you wrote: Michael> http://www.law.miami.edu/~froomkin/articles/icann-body.htm#B170 Michael> tells the story as best I could reconstruct it. There are footnotes to Michael> the documents I could find. Notice that Professor Froomkin's "To his detr

Re: anyone remember when the root servers were hi-jacked? (fwd)

2002-11-01 Thread Joe Touch
[EMAIL PROTECTED] would be a fine place to discuss this further, as it is (by definition) about (albeit recent) Internet history ;-) Joe Craig Simon wrote: I've got a lot of information on this which I'd be happy to share and exchange, but I still need and want more details. I'm not sure the IET

Re: kernelizing the network resolver

2002-11-01 Thread Perry E. Metzger
V Guruprasad <[EMAIL PROTECTED]> writes: > Please check out http://infs.sourceforge.net for a novel INternet > FileSystem (INFS) package which appears to be ideally suited to > cell phones and other small devices or appliances. By pushing the > DNS resolution to the kernel, INFS means to achieve t

Re: Palladium (TCP/MS)

2002-11-01 Thread Christopher Evans
Wha? they go outlaw windows? Shareholders wont do non of that in realm of lawsuits because M$ & the media done a good job at brain neutering the masses and furthering intellectual ejemity in the schools. Damn, I taking cis-2 and they concentrate in M$ details of operation and not on raw talent,

Re: kernelizing the network resolver

2002-11-01 Thread Keith Moore
> Please check out http://infs.sourceforge.net for a novel INternet > FileSystem (INFS) package which appears to be ideally suited to > cell phones and other small devices or appliances. By pushing the > DNS resolution to the kernel, INFS means to achieve the following: > > - eliminates sockaddr_t

Re: Palladium (TCP/MS)

2002-11-01 Thread Valdis . Kletnieks
On Fri, 01 Nov 2002 15:30:34 GMT, Sean Jones <[EMAIL PROTECTED]> said: > > You might think about where "peakflowmeter" came from > I cheat with Exchange 2000. I manage a number of domains, and in order to > make my job simpler, I have all of these domains forwarded to one domain via > my ISP

Re: anyone remember when the root servers were hi-jacked? (fwd)

2002-11-01 Thread Keith Moore
> That included concern over the possibility that NSI would go rogue. NSI *did* go rogue. They're still levying a toll on much of the net. What ended up becoming ICANN was originally an attempt to keep NSI in check - too bad it's mostly turned out to be ineffective. If there was a mistake mad

SNMP MIB

2002-11-01 Thread Barman, Partha
Does anyone know what SNMP MIB or OID value I can use to know "what mac-addresses are associated to what switch ports" on a Cisco 1900 switch.   Thanks, PB