W3C home > Mailing lists > Public > www-ws-arch@w3.org > February 2003

RE: Messaging Service Layer

From: Anne Thomas Manes <anne@manes.net>
Date: Sun, 16 Feb 2003 07:25:28 -0500
To: "Mark Baker" <distobj@acm.org>, "Cutler, Roger \(RogerCutler\)" <RogerCutler@ChevronTexaco.com>
Cc: <www-ws-arch@w3.org>


The OSI seven layer stack represents the network layer. Anything that can be
represented in the OSI stack is part of the network layer. Everything above
the network (the application and messaging layers) can't be represented in
the OSI stack.

The topmost level of the OSI stack (Level 7 - the application layer)
represents the network layer (application protocol) that applications use to
access the network. HTTP sits in Level 7. That's why we view HTTP as the
"transport" layer. It is the OSI Level 7 application protocol that we use to
access the network.


> -----Original Message-----
> From: www-ws-arch-request@w3.org [mailto:www-ws-arch-request@w3.org]On
> Behalf Of Mark Baker
> Sent: Sunday, February 16, 2003 12:02 AM
> To: Cutler, Roger (RogerCutler)
> Cc: www-ws-arch@w3.org
> Subject: Re: Messaging Service Layer
> On Fri, Feb 14, 2003 at 02:00:06PM -0600, Cutler, Roger
> (RogerCutler) wrote:
> > The application layer is above the messaging layer, the transport layer
> > below.  Examples of inhabitants of the application layer include ERP
> > systems (like SAP), office applications (like Excel or InfoPath) and Web
> > applications (like an ASP or JSP).  Examples of messaging layer
> > implementations include Web services and ebXML.  Examples of transport
> > layer implementations include HTTP and SMTP./
> In addition to comparing this stack to ebXML, I think it would be useful
> to compare it to the stack used in the IETF.
> In that stack, as with the one described above, the top dog is the
> application layer.  Beneath it is an oft-specified, yet unnamed layer
> which roughly corresponds to OSI layers 5 and 6, and from what I can
> tell, isn't too far from the common view of the "messaging layer".
> Beneath that layer, is the transport layer.
> That may not sound very different than what's described above, except
> when you actually take a look at what IETF technologies fit where.
> Consider, from top to bottom;
> - HTTP is at the application layer
> - BEEP is at the "messaging" layer
> - TCP is at the transport layer
> MB
> --
> Mark Baker.   Ottawa, Ontario, CANADA.        http://www.markbaker.ca
> Web architecture consulting, technical reports, evaluation & analysis
Received on Sunday, 16 February 2003 07:25:54 UTC

This archive was generated by hypermail 2.3.1 : Tuesday, 6 January 2015 21:41:03 UTC