![]() |
![]() |
![]() |
![]() |
![]() |
![]() |
![]() |
![]() |
![]() |
![]() |
![]() |
![]() |
On Thu, 1 Mar 2001 graham.travers at bt.com wrote: > Would you not concede, though, that coders ( should ) write to implement > requirements, which are typically not defined by the coders themselves, but > by their "customers" ? That's _exactly_ what the ISO OSI committees thought. > The IETF publishes lots of I-Ds which give > requirements, rather than coding solutions. The people who write these > requirements are not necessarily coders themselves. Anyone can submit an ID. Many do. Oddly, coding experience is better-reflected in the RFCs and STDs. > In my, limited, coding experience, I don't recall finding ASCII diagrams as > part of the code. Poor diagrammatic capability is one of the problems I > have with ASCII. I? (What happened to those ID writers working for you?) > IMHO, standards are about far more than writing code; first, and most > importantly, they are about achieving agreement. That's _exactly_ what the ISO OSI committees thought. > Regards, > > Graham Travers > > Applications Standards Strategist I'm curious. What, exactly, does an ASS do? thanks, L. <L.Wood at surrey.ac.uk>PGP<http://www.ee.surrey.ac.uk/Personal/L.Wood/>
Note Well: Messages sent to this mailing list are the opinions of the senders and do not imply endorsement by the IETF.