| T.R | Title | User | Personal
Name | Date | Lines |
|---|
| 176.1 | Hello? | CRBOSS::LEMONS | And we thank you for your support. | Wed Oct 10 1990 10:07 | 7 |
| Rats. I'd like to see an answer to the questions in .0 also. By the
by, what notes file(s) discuss NAS and provide pointers to
documentation on NAS?
Thanks!
tl
|
| 176.2 | NAS compliance | CLAUDI::PETERS | | Wed Oct 10 1990 10:46 | 13 |
| Anything DEC produces that dinks with the network and any of protocols
we support is NAS compliant, including DECmcc (all flavors). NAS is
a marketing concept designs to consolidate (and so far successfully) DECs
position as THE network vendor with the best products for interoperability.
The press and many of our customers (upper mgmt types mainly) could never
understand the one hundred thousand different network packages we
offer for interconnection, interoperability, interdomain, interETC so
we built a platform (or maybe it's a tent) and billed the individual
products as components of the greater whole called NAS!! The grunts know
the truth, but you have to admire the marketing aspects and the simplicity
of the NAS message at the braodspectrum level.... DEC can provide your
customer networking needs (and the cast of thousand to install and
maintain it). Pseudo-cynic at large, Claudia
|
| 176.3 | .2 is basically correct, but. . . | RANGER::PRAETORIUS | going through life depth first | Mon Oct 15 1990 22:45 | 26 |
| <<< NAC::DISK$WORK295:[NOTES$LIBRARY]DNA.NOTE;1 >>>
-< Digital Network Architecture >-
================================================================================
Note 217.0 NAS: see PIPE::AIA$INFO: No replies
RANGER::PRAETORIUS "reg Penna dept agr" 20 lines 14-SEP-1990 11:36
--------------------------------------------------------------------------------
Since I've seen a coupla questions here about NAS but both were replies to
the Welcome note, which may not be an appropriate place to answer the question
('cause a DIR/TITLE wouldn't show the answer), I'm gonna put a note here that
says what I tell people when they ask me how to find out what NAS is:
do a $ DIR PIPE::AIA$INFO:
also, info on many NAS components may be found in
VIA::ACA$PUBLIC:[*...]
and a NAS Marketing Resource Kit is available internally and it's part # is
EY-F903E-SP
This may not be the best answer (or even a good answer), but perhaps it'll
inspire somebody with a better answer or a reference to an existing note in
another notesfile, so that a DIR/TITLE:NAS of BERGIL::DNA won't come up empty.
Robt. P.
|
| 176.4 | Things Change... | DRUMS::FEHSKENS | len, EMA, LKG2-2/W10, DTN 226-7556 | Tue Mar 26 1991 11:16 | 13 |
| The recent considerable enlargement of scope of NAS radically changes
the answer to this question. NAS is now a set of services, not a
marketing concept, and NAS compliance entails use of these services
and hence ready portability to NAS platforms. NAS conformance/
integration has been submitted as a DECmcc V2.0 requirement.
For more details about the latest on NAS, see
ABBOTT::DUB1:[NOTES$LIBRARY]NAS_ARCHITECTURE.NOTE
len.
|
| 176.5 | did they change that much? | RANGER::PRAETORIUS | face to face to face with duality | Wed Mar 27 1991 17:07 | 23 |
| Where's the big change? Stuff like X, CDA, DNS and RPC (the presentation,
information and communication service categories in figure 14 of the overview)
was already what many people thought of when NAS was mentioned.
APA components have long been visible as part of NAS, for those who took
the trouble to look. These include things like multithreading (CMA), condition
handling (PCH), multilingual message text (MTEXT), memory allocation, compound
string handling (CSLIB), conversion routines, etc (the stuff in computation
and control services in fig. 14).
One problem is that, although specs exist for all the pieces, code doesn't
yet exist for some of them (in fact the funding has been pulled on PCH, last I
heard). I'm glad something has (apparently) been done to increase the amount of
attention received by these NAS components.
I think the major change in NAS is it's visibility (there suddenly a
notesfile dedicated to it and perhaps some people higher up are speaking more
clearly about what's in NAS). The overview document has certainly expanded over
the years, but I don't think there's been a quantum leap in it's scope.
curmudgeonly,
RP
|