Re: Protocol Definition
John Day <jeanjour@comcast.net> Mon, 09 January 2012 04:35 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 623C221F861A for <ietf@ietfa.amsl.com>; Sun, 8 Jan 2012 20:35:12 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -103.116
X-Spam-Level:
X-Spam-Status: No, score=-103.116 tagged_above=-999 required=5 tests=[AWL=1.483, BAYES_00=-2.599, GB_I_LETTER=-2, 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 0-DM9zDwBoE8 for <ietf@ietfa.amsl.com>; Sun, 8 Jan 2012 20:35:11 -0800 (PST)
Received: from qmta08.westchester.pa.mail.comcast.net (qmta08.westchester.pa.mail.comcast.net [76.96.62.80]) by ietfa.amsl.com (Postfix) with ESMTP id AE48C21F85EE for <ietf@ietf.org>; Sun, 8 Jan 2012 20:35:11 -0800 (PST)
Received: from omta15.westchester.pa.mail.comcast.net ([76.96.62.87]) by qmta08.westchester.pa.mail.comcast.net with comcast id KGZN1i0011swQuc58GbCeu; Mon, 09 Jan 2012 04:35:12 +0000
Received: from [10.0.1.26] ([24.218.154.214]) by omta15.westchester.pa.mail.comcast.net with comcast id KGbA1i00A4dorGg3bGbBP1; Mon, 09 Jan 2012 04:35:12 +0000
Mime-Version: 1.0
Message-Id: <a06240874cb301ba706ea@[10.0.1.26]>
In-Reply-To: <4F0A1AE4.3050306@250bpm.com>
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]> <4F0A1AE4.3050306@250bpm.com>
Date: Sun, 08 Jan 2012 23:35:05 -0500
To: Martin Sustrik <sustrik@250bpm.com>, John Day <jeanjour@comcast.net>
From: John Day <jeanjour@comcast.net>
Subject: Re: Protocol Definition
Content-Type: text/plain; charset="us-ascii"; format="flowed"
Cc: dcrocker@bbiw.net, 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: Mon, 09 Jan 2012 04:35:12 -0000
At 23:38 +0100 2012/01/08, Martin Sustrik wrote: >On 08/01/12 13:00, John Day wrote: > >>You are also correct that strictly speaking the words "protocol" and >>"algorithm" are probably the same. > >That is an interesting point. > >What I encounter often is the belief that protocol is just >"description of bytes on the wire". People often forget about the >stuff that cannot be seen on the wire (e.g. TCP state machine). This is clearly not the case and has never been the case. In fact, "bytes on the wire" is probably the smallest part of a protocol specification. A protocol specification must specify what to do with the "bytes on the wire/" The next time someone suggests that merely ask, what do you do with the bytes on the wire? Where is that specified? The action to be taken when a message arrives is all there is. There was once a group who thought that names of the fields in their protocol was sufficient to specify what was to be done with them. I pointed out the them that a legal value of every field in their protocol was the letter "Z". They objected to this quite strenuously, but I asked to show me where it said this was not the case. ;-) Anyone who says that merely specifying the format of messages (bytes on the wire, as you say) constitutes a protocol specification is clearly not competent to be making such pronouncements. > >The area I work in has little or no special "bytes on wire" (simple >message-based underlying transport is sufficient) but a lot of >algorithmic stuff. Consequently, it was often dismissed as not being >a protocol. "has little or no special "bytes on wire" (simple message-based underlying transport is sufficient)" I have no clue what this phrase could possibly mean. If you are passing messages, there must be "bytes on the wire" otherwise, the messages have not been exchanged. Take care, John Day >Martin
- 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