North American Network Operators Group

Date Prev | Date Next | Date Index | Thread Index | Author Index | Historical

Re: Wired Q: Embedded NT

  • From: Ehab Hadi
  • Date: Sat May 16 23:30:37 1998

I admit it if the perspective is to build all or a part of the WIN 
NT suites in a kind of a hardware or ASIC is not clear for me, the 
questions that I would like to raise:
What version of WIN NT? is it 4.0 or beyond..? How do we expect 
customers will be confident enough to make this step?, Is WIN NT 
reliable, stable in a customized ASIC hence WIN NT would be more 
suitable than the general purpose hardware architecture?. Implementing 
standard IPv4 services on the ASIC and optimizing that still on its 
early stages; i.e., mostly for inter LAN routing. So, do how that will 
work for WIN NT?. Let's do it for multi-routed protocols in the ASIC 
switches and think further for the high-level embedded applications. I 
agree it might be a good idea if  embedded NT is doing a single task 
such as Web 
caching, but not a "full fledge" switch/router.


Ehab H. Hadi
Northern Telecom, LTD.
Voice: (613) 763-2762
Fax: (613) 763-5199
E-Mail: [email protected]


>From [email protected] Thu May 14 07:44:09 1998
>Received: from localhost ([email protected])
>	by merit.edu (8.8.7/8.8.5) with SMTP id KAA00208;
>	Thu, 14 May 1998 10:31:17 -0400 (EDT)
>Received: by merit.edu (bulk_mailer v1.5); Thu, 14 May 1998 10:25:33 
-0400
>Received: (from [email protected])
>	by merit.edu (8.8.7/8.8.5) id KAA29922
>	for nanog-outgoing; Thu, 14 May 1998 10:25:33 -0400 (EDT)
>Received: from home.merit.edu (home.merit.edu [198.108.60.42])
>	by merit.edu (8.8.7/8.8.5) with ESMTP id KAA29916
>	for <[email protected]>; Thu, 14 May 1998 10:25:29 -0400 (EDT)
>Received: (from [email protected]) by home.merit.edu (8.8.8/merit-2.0) id 
KAA11610 for [email protected]; Thu, 14 May 1998 10:25:29 -0400 (EDT)
>Received: from wired.com (get.wired.com [204.62.131.5])
>	by merit.edu (8.8.7/8.8.5) with ESMTP id SAA16509
>	for <[email protected]>; Wed, 13 May 1998 18:20:25 -0400 (EDT)
>Received: from glave.hotwired.com (roaming-194-239.hotwired.com 
[206.221.194.239])
>	by wired.com (8.8.7/8.8.7) with SMTP id PAA09202
>	for <[email protected]>; Wed, 13 May 1998 15:19:43 -0700
>Message-Id: <[email protected]>
>X-Sender: [email protected]
>X-Mailer: QUALCOMM Windows Eudora Pro Version 4.0
>Date: Wed, 13 May 1998 15:19:26 -0700
>To: [email protected]
>From: James Glave <[email protected]>
>Subject: Wired Q: Embedded NT
>Mime-Version: 1.0
>Content-Type: text/plain; charset="us-ascii"
>Sender: [email protected]
>
>Hi all,
>
>James Glave at Wired News again. This time around I am seeking opinions 
on
>behalf of a friend up at Wired (the print magazine) -- concerning 
embedded
>NT. I couldn't find any discussion in the nanog archive, so I'm 
wondering
>if anoyne here has any experience with, or knowledge of, embedding NT 
in
>networking hardware - if that even makes any sense....?
>
>>From: Jesse Freund <[email protected]>
>>i'm working on a piece about nt-embedded and i have a couple of 
questions.
>>i'm hoping you might be able to hook me up with a smart network 
operator or
>>someone else in the know or perhaps you know.  basically, i'm curious 
why
>>the hell someone would want a version of nt embedded in a switch or 
router?
>>and who provides the custom solutions nt-embedded is meant to replace?
>
>Thanks, all!
>
>jtg
>
>James Glave, Senior Technology Writer 
>Wired News http://www.wired.com  (415) 276-8430
>
>Unstoppable Force of the Week:  "Gettin' jiggy wit' it!"
>


______________________________________________________
Get Your Private, Free Email at http://www.hotmail.com