Re: Protocol Definition

Douglas Otis <dotis@mail-abuse.org> Thu, 05 January 2012 17:54 UTC

Return-Path: <dotis@mail-abuse.org>
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 4A46B21F877D for <ietf@ietfa.amsl.com>; Thu, 5 Jan 2012 09:54:00 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -102.176
X-Spam-Level:
X-Spam-Status: No, score=-102.176 tagged_above=-999 required=5 tests=[AWL=0.423, BAYES_00=-2.599, 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 tqKovvw4YN-f for <ietf@ietfa.amsl.com>; Thu, 5 Jan 2012 09:53:59 -0800 (PST)
Received: from mailserv.mail-abuse.org (mailserv.mail-abuse.org [150.70.98.118]) by ietfa.amsl.com (Postfix) with ESMTP id EBDD121F8775 for <ietf@ietf.org>; Thu, 5 Jan 2012 09:53:57 -0800 (PST)
Received: from US-DOUGO-MAC.local (sjdcluxgateway1.sdi.trendnet.org [10.31.37.8]) by mailserv.mail-abuse.org (Postfix) with ESMTPSA id B872E17400FA for <ietf@ietf.org>; Thu, 5 Jan 2012 17:53:56 +0000 (UTC)
Message-ID: <4F05E3B8.5030305@mail-abuse.org>
Date: Thu, 05 Jan 2012 09:54:00 -0800
From: Douglas Otis <dotis@mail-abuse.org>
User-Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.7; rv:9.0) Gecko/20111222 Thunderbird/9.0.1
MIME-Version: 1.0
To: ietf@ietf.org
Subject: Re: Protocol Definition
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>
In-Reply-To: <4F05DA49.8050802@dcrocker.net>
Content-Type: text/plain; charset="ISO-8859-1"; format="flowed"
Content-Transfer-Encoding: 7bit
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: Thu, 05 Jan 2012 17:54:02 -0000

On 1/5/12 9:13 AM, Dave CROCKER wrote:
>  On 1/5/2012 7:01 AM, Dave Cridland wrote:
> > On Thu Jan 5 14:48:54 2012, Dave CROCKER wrote:
> >> If protocol corresponds with program or algorithm, then what is
> >> the communications term that corresponds to process?
> >>
> >> It's tempting to say "port number", but that doesn't seem very
> >> satisfying.
> >
> > "Session"?
>
>  That's an appealing suggestion. It is based on a 'state' existing
>  between the two end points and it is above transport (so we don't
>  have to worry about tcp vs udp vs...).
>
>  On the other hand, isn't a session able to have more than one
>  "connection" and, therefore, possibly be running more than one
>  protocol?

Dave,

Agreed.  A multiple stream protocol aggregates multiple endpoints into 
an Association where each then signals supported protocols.  Within each 
protocol, various algorithms are applied, often in phases such as Bind, 
Listen, Accept, Connect, Close, Shutdown, SendMsg, RecvMsg, 
GetPeerName.  An algorithm might be expressed using computer languages 
that incorporate elaborate mathematical models, such as simple hash 
functions used to validate packets.  One of the protocols supported is 
SDP Session Description Protocol that carries media over the multiple 
streams.  This provides for Sessions, Associations and Connections.

See:
http://tools.ietf.org/html/draft-loreto-mmusic-sctp-sdp-07#page-3

-Doug