Hi Ping,
My apologies (to all) for making the same point later in the
thread that you had already made here...processing my list of
open mail in the wrong order evidently!
But I am glad to have your confirmation of the wide deployment
of RSVP-TE in carrier MPLS nets. I worked hard to promote tha
Hi,
Were Eric's question and Dean's answer limited to RSVP strictly,
or would RSVP-TE deployments be of interest? If the latter, then
what about emerging deployments of architectures that use RSVP-TE,
such as MPLS, GMPLS, and ASON? (Or are none of the news releases
true? ;-)
Cordially,
BobN
--
Yes, we keep a couple of old "2500" telelphones around
the house too...just for this purpose. I have often
wondered why someone does not make a modern cordless
phone with backup 2500 set capability built into the
handset (which would need an RJ-11 jack as well, of
course)?...in a power failure, on
At 1/23/2003:11:13 AM, Ong, Lyndon wrote:
Hi all,
[I hope no one minds that I've trimmed the numerous individual
recipient names from the address headers on this thread! :-]
FWIW, I'd like to "second" the comments made by Lyndon below,
in all three parts of his message.
Furthermore, I'd like to
Hi Puja,
To enlarge upon Bert's answer just a bit: I would say
that the encoding of data within an octet string type
should be specified in the MIB...this is often done via
a Textual Convention (TC) defined for that purpose, but
can be handled in the DESCRIPTION clause if a TC is not
warranted (
arting points.
Cordially,
BobN
ISO 9001 Registered Quality Supplier ---
Bob Natale | ACE*COMM | 301-721-3000 [v]
Dir, Net Mgmt Prod | 704 Quince Orchard Rd | 301-721-3001 [f]
[EMAIL PROTECTED]| Gaithersburg MD 20878 | www.acecomm.com
- Free downloads at www.winsnmp.com -
ing returned.
>I'm proposing to use this field instead as an index to an error details table.
This is a non-starter due to error in your
suspicion above.
Cordially,
BobN
ISO 9001 Registered Quality Supplier ---
Bob Natale | ACE*COMM | 301-721-300
