![]() |
![]() |
![]() |
![]() |
![]() |
![]() |
![]() |
![]() |
![]() |
![]() |
![]() |
![]() |
Joe Touch wrote: > Jon Crowcroft wrote: > > > > on reflection (pun intended): > > layering is a clothing methodology for people who live in fractal climates > > not a design pattern for correct or efficient communications > > systems.... > > cheers > > > > jon > > Another adage: > > model != mechanism > > I.e., layering is, IMO at least, a model. Fine for > describing things, but not necessarily a good blueprint > for an implementation. > A problem well-stated is a problem half-solved. Good models are often useful in gaining basic insights into a problem..a good starting point for design before you plunge into the thicket of bewildering details. (I am not passing any judgements on OSI or layering here :) )
Note Well: Messages sent to this mailing list are the opinions of the senders and do not imply endorsement by the IETF.