RE: Protocol Definition
John Day <jeanjour@comcast.net> Tue, 10 January 2012 15:15 UTC
Return-Path: <jeanjour@comcast.net>
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 E609E21F8606 for <ietf@ietfa.amsl.com>; Tue, 10 Jan 2012 07:15:23 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -102.641
X-Spam-Level:
X-Spam-Status: No, score=-102.641 tagged_above=-999 required=5 tests=[AWL=-0.042, 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 n4vKh22k+Rkb for <ietf@ietfa.amsl.com>; Tue, 10 Jan 2012 07:15:23 -0800 (PST)
Received: from qmta09.westchester.pa.mail.comcast.net (qmta09.westchester.pa.mail.comcast.net [76.96.62.96]) by ietfa.amsl.com (Postfix) with ESMTP id 4574021F8569 for <ietf@ietf.org>; Tue, 10 Jan 2012 07:15:23 -0800 (PST)
Received: from omta16.westchester.pa.mail.comcast.net ([76.96.62.88]) by qmta09.westchester.pa.mail.comcast.net with comcast id KpWy1i0021uE5Es59rFP8D; Tue, 10 Jan 2012 15:15:23 +0000
Received: from [10.0.1.26] ([24.218.154.214]) by omta16.westchester.pa.mail.comcast.net with comcast id KrFN1i01J4dorGg3crFNab; Tue, 10 Jan 2012 15:15:23 +0000
Mime-Version: 1.0
Message-Id: <a06240802cb320335fbf9@[10.0.1.26]>
In-Reply-To: <07F7D7DED63154409F13298786A2ADC9042C9474@EXRAD5.ad.rad.co.il>
References: <CAD7Ssm-Vetqmh3sxMWRiOHysp+XUaas7XuBkeg803mkTCsA0vQ@mail.gmail.com><alpin e.OSX.2.01.1201031756290.15402@rcdn-vpn-client-10-89-1-59.cisco.com><07F7D 7DED63154409F13298786A2ADC9042C5169@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><4F06662A.6070504@joelhalpern.com> <4F0667B9.30604@dcrocker.net> <000b01cccddb$fd4214c0$4001a8c0@gateway.2wire.net> <a06240871cb2f30d9735f@[10.0.1.26]> <07F7D7DED63154409F13298786A2ADC9042C9474@EXRAD5.ad.rad.co.il>
Date: Tue, 10 Jan 2012 10:07:25 -0500
To: Yaakov Stein <yaakov_s@rad.com>, John Day <jeanjour@comcast.net>, "t.petch" <daedulus@btconnect.com>, "dcrocker@bbiw.net" <dcrocker@bbiw.net>
From: John Day <jeanjour@comcast.net>
Subject: RE: Protocol Definition
Content-Type: text/plain; charset="us-ascii"; format="flowed"
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: Tue, 10 Jan 2012 15:15:24 -0000
What you say is true of "communication or network protocols." The statement below was written in the context of the wider use of the word protocol (and what you would probably find in the dictionary) in the fields of biology, chemistry, and diplomacy. In this case, one could view our use of the term as a specialization of the general use. After all, a network protocol is a distributed algorithm. The communicating peers only make sense together. At 14:53 +0000 2012/01/10, Yaakov Stein wrote: ><You are also correct that strictly speaking the words "protocol" and >< "algorithm" are probably the same. > >No, they aren't. > >In protocols it is essential that there are at least 2 communicating >entities running the same protocol (or at least compatible >protocols). >Each side may be running algorithm(s), but the protocol states what >I have to do when >the other side sends (or doesn't send) me a message of a certain type. > >Algorithms frequently have inputs, but these need not come from >other algorithms, >and are treated accordingly. > >Y(J)S
- Protocol Definition Kaushal Shriyan
- Re: Protocol Definition Ole Jacobsen
- RE: Protocol Definition Yaakov Stein
- Re: Protocol Definition Dave CROCKER
- Re: Protocol Definition Dave Cridland
- Re: Protocol Definition Dave CROCKER
- Re: Protocol Definition John C Klensin
- Re: Protocol Definition todd glassey
- Re: Protocol Definition Dave CROCKER
- Re: Protocol Definition Douglas Otis
- Re: Protocol Definition Dave Cridland
- Re: Protocol Definition Fernando Gont
- Re: Protocol Definition Dave CROCKER
- Re: Protocol Definition Joel M. Halpern
- Re: Protocol Definition Dave CROCKER
- RE: Protocol Definition Yaakov Stein
- RE: Protocol Definition John Day
- Re: Protocol Definition t.petch
- Re: Protocol Definition John Day
- Re: Protocol Definition Martin Sustrik
- Re: Protocol Definition John Day
- Re: Protocol Definition Martin Sustrik
- Re: Protocol Definition John Day
- Re: Protocol Definition pankaj kumar
- Re: Protocol Definition Dave CROCKER
- Re: Protocol Definition John Day
- RE: Protocol Definition Yaakov Stein
- RE: Protocol Definition John Day
- Re: Protocol Definition Joe Touch
- Re: Protocol Definition Alessandro Vesely
- Re: Protocol Definition Abdussalam Baryun
- Re: Protocol Definition Joe Touch
- Re: Protocol Definition Alessandro Vesely
- Re: Protocol Definition Abdussalam Baryun
- Re: Protocol Definition Randy Bush
- Re: Protocol Definition Abdussalam Baryun
- Re: Protocol Definition Joel jaeggli
- Re: Protocol Definition Melinda Shore
- Re: Protocol Definition Tony Finch
- Re: Protocol Definition Donald Eastlake
- Re: Protocol Definition tglassey