![]() |
![]() |
![]() |
![]() |
![]() |
![]() |
![]() |
![]() |
![]() |
![]() |
![]() |
![]() |
"Howard C. Berkowitz" writes: > I can get along with stating thing in those terms, although I would suggest > that this conscious limiting doesn't come across in the architecture > document. Again, my concern is that the enterprise network architect > realistically is not going to go back to the charter. He isn't going to read an RFC, either. They are too technical given the quality of personel likely to be available these days. If he did read and understand the given RFCs, however, he'd know the information that he needs, in all likelyhood. Perry
Note Well: Messages sent to this mailing list are the opinions of the senders and do not imply endorsement by the IETF.