IETF Logo Mail Archive

RE: Protocol Definition

Yaakov Stein <yaakov_s@rad.com> Tue, 10 January 2012 14:54 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 6C09421F860E for <ietf@ietfa.amsl.com>; Tue, 10 Jan 2012 06:54:01 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -101.731
X-Spam-Level:
X-Spam-Status: No, score=-101.731 tagged_above=-999 required=5 tests=[AWL=0.867, 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 4N4RBQLsnzHJ for <ietf@ietfa.amsl.com>; Tue, 10 Jan 2012 06:54:00 -0800 (PST)
Received: from rad.co.il (mailrelay02-q.rad.co.il [94.188.133.159]) by ietfa.amsl.com (Postfix) with ESMTP id 3674921F854A for <ietf@ietf.org>; Tue, 10 Jan 2012 06:53:57 -0800 (PST)
Received: from Internal Mail-Server by MailRelay02 (envelope-from yaakov?s@rad.com) with AES128-SHA encrypted SMTP; 10 Jan 2012 16:49:23 +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; Tue, 10 Jan 2012 16:53:51 +0200
From: Yaakov Stein <yaakov_s@rad.com>
To: John Day <jeanjour@comcast.net>, "t.petch" <daedulus@btconnect.com>, "dcrocker@bbiw.net" <dcrocker@bbiw.net>
Subject: RE: Protocol Definition
Thread-Topic: Protocol Definition
Thread-Index: AQHMzdv4uTrSvisg80qAwUBf6ZqN4pYCPRcAgAN1cyA=
Date: Tue, 10 Jan 2012 14:53:50 +0000
Message-ID: <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]>
In-Reply-To: <a06240871cb2f30d9735f@[10.0.1.26]>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach:
X-MS-TNEF-Correlator:
x-originating-ip: [172.17.170.143]
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: Tue, 10 Jan 2012 14:54:01 -0000

<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

v2.23.0 | Report a Bug | By Email