Re: SHOCK NEWS: Cisco not RFC-1812 compliant

From: Pete Templin (templin@urdirect.net)
Date: Mon Jan 10 2000 - 20:20:15 EST

Next message: Martin Cooper: "Re: SHOCK NEWS: Cisco not RFC-1812 compliant"
Previous message: Everett Dowd: "Re: SHOCK NEWS: Cisco not RFC-1812 compliant"
In reply to: Martin Cooper: "Re: SHOCK NEWS: Cisco not RFC-1812 compliant"
Next in thread: Jared Mauch: "Re: SHOCK NEWS: Cisco not RFC-1812 compliant"
Reply: Jared Mauch: "Re: SHOCK NEWS: Cisco not RFC-1812 compliant"
Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]
Mail actions: [ respond to this message ] [ mail a new topic ]

On Mon, 10 Jan 2000, Martin Cooper wrote:

> Yes, but then it does look kind of poor when the company the
> guy who edited the RFC works for doesn't bother to implement
> it properly...

I thought you said it didn't implement it at all - is it now supporting it
but with bugs? Make up my mind, please.

Pete

-- Peter J. Templin, Jr., CCNA Systems and Networks Administrator

On-Line Internet Services - URDirect.net A division of Global On-Line Computers 2414 Babcock Rd. Suite 106 templin@urdirect.net San Antonio, TX 78229 (210)692-9911

Next message: Martin Cooper: "Re: SHOCK NEWS: Cisco not RFC-1812 compliant"
Previous message: Everett Dowd: "Re: SHOCK NEWS: Cisco not RFC-1812 compliant"
In reply to: Martin Cooper: "Re: SHOCK NEWS: Cisco not RFC-1812 compliant"
Next in thread: Jared Mauch: "Re: SHOCK NEWS: Cisco not RFC-1812 compliant"
Reply: Jared Mauch: "Re: SHOCK NEWS: Cisco not RFC-1812 compliant"
Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]
Mail actions: [ respond to this message ] [ mail a new topic ]

This archive was generated by hypermail 2b29 : Sun Aug 04 2002 - 04:12:08 EDT