RE: Protocol Definition

Yaakov Stein <yaakov_s@rad.com> Sat, 07 January 2012 20:11 UTC

Return-Path: <yaakov_s@rad.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 13C2721F848F for <ietf@ietfa.amsl.com>; Sat, 7 Jan 2012 12:11:16 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -102.598
X-Spam-Level:
X-Spam-Status: No, score=-102.598 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, UNPARSEABLE_RELAY=0.001, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id UWGmEbhjl1YT for <ietf@ietfa.amsl.com>; Sat, 7 Jan 2012 12:11:15 -0800 (PST)
Received: from rad.co.il (mailrelay02.rad.co.il [62.0.23.237]) by ietfa.amsl.com (Postfix) with ESMTP id AC53321F84B4 for <ietf@ietf.org>; Sat, 7 Jan 2012 12:11:12 -0800 (PST)
Received: from Internal Mail-Server by MailRelay02 (envelope-from yaakov?s@rad.com) with AES128-SHA encrypted SMTP; 7 Jan 2012 22:07:22 +0200
Received: from EXRAD5.ad.rad.co.il ([192.114.24.28]) by EXRAD5.ad.rad.co.il ([192.114.24.28]) with mapi id 14.01.0323.003; Sat, 7 Jan 2012 22:11:03 +0200
From: Yaakov Stein <yaakov_s@rad.com>
To: "dcrocker@bbiw.net" <dcrocker@bbiw.net>, Dave Cridland <dave@cridland.net>
Subject: RE: Protocol Definition
Thread-Topic: Protocol Definition
Thread-Index: AQHMyoO4uTrSvisg80qAwUBf6ZqN4pX7UmUAgACpgACAAb/WAIAAA6aAgAAk04CAAAs/AIAAP6aAgABZ3ACAAseB0A==
Date: Sat, 07 Jan 2012 20:11:02 +0000
Message-ID: <07F7D7DED63154409F13298786A2ADC9042C6EEA@EXRAD5.ad.rad.co.il>
References: <CAD7Ssm-Vetqmh3sxMWRiOHysp+XUaas7XuBkeg803mkTCsA0vQ@mail.gmail.com> <alpine.OSX.2.01.1201031756290.15402@rcdn-vpn-client-10-89-1-59.cisco.com> <07F7D7DED63154409F13298786A2ADC9042C5169@EXRAD5.ad.rad.co.il> <4F05B856.9050205@dcrocker.net> <3013.1325775717.451646@puncture> <4F05DA49.8050802@dcrocker.net> <4F05E3B8.5030305@mail-abuse.org> <3013.1325799709.099423@puncture> <4F06647E.2010905@dcrocker.net>
In-Reply-To: <4F06647E.2010905@dcrocker.net>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach:
X-MS-TNEF-Correlator:
x-originating-ip: [207.232.33.112]
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: quoted-printable
MIME-Version: 1.0
Cc: IETF-Discussion <ietf@ietf.org>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Sat, 07 Jan 2012 20:11:16 -0000

X.200 - ITU's version of the OSI model - defines an "association" as peering at any layer of the OSI stack.
Thus an association at layer 3 is a pair of IP addresses, while an association at layer 4 is a pair of socket IDs.
If the association is requested then it becomes a "connection".
A "session" is an association at layer 5.

A process in computation is defined as an entity that is independent 
in the sense that it can request and own resources (e.g., CPU time and memory).
Many processes can exist side by side, and can even communicate via IPC,
but processes do not have a hierarchy such as we have in communications.
The closest thing is the fact that processes can own tasks or threads as sub-entities
(tasks are not indendent - their memory and CPU time are taken from their father process).

Just as an association runs protocols at different layers, a single process frequently runs multiple algorithms.
But these algorithms are usually not layered.

A protocol between two entities often involves algorithms on both sides,
but an association does not necessarily link two processes on the communicating sides.

Y(J)S


-----Original Message-----
From: ietf-bounces@ietf.org [mailto:ietf-bounces@ietf.org] On Behalf Of Dave CROCKER
Sent: Friday, January 06, 2012 05:03
To: Dave Cridland
Cc: IETF-Discussion
Subject: Re: Protocol Definition



On 1/5/2012 1:41 PM, Dave Cridland wrote:
> Association, to my mind, means a transport layer connection, hence it's usage in
> SNMP and other OSI-related things.
>
> Session isn't much less damaged, as a term, I admit, but it is in common usage.
> And like algorithms, and protocols, you can open up a session to find other
> sessions inside.


Actually, my recollection is that 'association' was an application-level 
construct from OSI.

But I came to the same conclusion as you:  "session" is an established term in 
IETF parlance and has the basic reality of describing a protocol in operation 
between two (or more?) hosts/endsystems/endpoints/...

Does this resonate with others?

d/
-- 

   Dave Crocker
   Brandenburg InternetWorking
   bbiw.net
_______________________________________________
Ietf mailing list
Ietf@ietf.org
https://www.ietf.org/mailman/listinfo/ietf