In cases like these, one should avoid trying to wedge protocols into 1970s concepts. It looks like the point of the work is to use HTTP as a general purpose switching header. This is what you get with Ethernet, IP ... and mail and Web Services (leaving out connection-oriented protocols). Just because you switch on it doesn't decide what "layer" it is in the old OSI model. If
- it has its own namespace - you switch on it - it has its own fault detection then you might be better off calling it a "layer network" (q.v.) e.g. http://www.niven-jenkins.co.uk/An%20introduction%20to%20functional%20architecture.pdf In any case just because something is used to perform functions similar to those in the transport or internet layers doesn't mean it belongs in the Transport or Internet _Areas_. That is more determined by the protocols being worked on. If it's work on HTTP, imho that belongs in Apps. Scott
