IETF Logo Mail Archive

Re: Protocol Definition

tglassey <tglassey@earthlink.net> Sun, 24 June 2012 13:20 UTC

Return-Path: <tglassey@earthlink.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 D184521F860B for <ietf@ietfa.amsl.com>; Sun, 24 Jun 2012 06:20:33 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -0.185
X-Spam-Level:
X-Spam-Status: No, score=-0.185 tagged_above=-999 required=5 tests=[BAYES_40=-0.185]
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 r+rCLrrBoF4B for <ietf@ietfa.amsl.com>; Sun, 24 Jun 2012 06:20:33 -0700 (PDT)
Received: from elasmtp-galgo.atl.sa.earthlink.net (elasmtp-galgo.atl.sa.earthlink.net [209.86.89.61]) by ietfa.amsl.com (Postfix) with ESMTP id 596F921F8633 for <ietf@ietf.org>; Sun, 24 Jun 2012 06:20:33 -0700 (PDT)
DomainKey-Signature: a=rsa-sha1; q=dns; c=nofws; s=dk20050327; d=earthlink.net; b=GxAjioNK7sSNCcqikhA3/XnWQRNgN9zdgklkLBzyMAq9DLdXWR36bT1pniYzFBeO; h=Received:Message-ID:Date:From:User-Agent:MIME-Version:To:Subject:References:In-Reply-To:Content-Type:Content-Transfer-Encoding:X-ELNK-Trace:X-Originating-IP;
Received: from [67.180.133.21] (helo=[192.168.15.2]) by elasmtp-galgo.atl.sa.earthlink.net with esmtpsa (TLSv1:AES256-SHA:256) (Exim 4.67) (envelope-from <tglassey@earthlink.net>) id 1Simjw-0008AS-Ph; Sun, 24 Jun 2012 09:20:32 -0400
Message-ID: <4FE71418.7060600@earthlink.net>
Date: Sun, 24 Jun 2012 06:20:24 -0700
From: tglassey <tglassey@earthlink.net>
User-Agent: Mozilla/5.0 (Windows NT 6.1; WOW64; rv:13.0) Gecko/20120614 Thunderbird/13.0.1
MIME-Version: 1.0
To: Tony Finch <dot@dotat.at>, ietf <ietf@ietf.org>
Subject: Re: Protocol Definition
References: <CADnDZ8_5nH7gNvR_LAB3wJ0zfKh-G0WmWbTm6yDq-M+LMajfbg@mail.gmail.com> <CADnDZ8_XSKgmOq+pfiq=rT5mVRqLk8CnyFKU9CNd+ZG81DJ_xA@mail.gmail.com> <m2y5ng6p99.wl%randy@psg.com> <alpine.LSU.2.00.1206221815380.18854@hermes-2.csi.cam.ac.uk>
In-Reply-To: <alpine.LSU.2.00.1206221815380.18854@hermes-2.csi.cam.ac.uk>
Content-Type: text/plain; charset="ISO-8859-1"; format="flowed"
Content-Transfer-Encoding: 7bit
X-ELNK-Trace: 01b7a7e171bdf5911aa676d7e74259b7b3291a7d08dfec79754bb59eb2d551a848e27f74a711dc45350badd9bab72f9c350badd9bab72f9c350badd9bab72f9c
X-Originating-IP: 67.180.133.21
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: Sun, 24 Jun 2012 13:20:33 -0000

On 6/22/2012 10:17 AM, Tony Finch wrote:
> Randy Bush <randy@psg.com> wrote:
>
>>> All protocols in IETF are based on the Internet or/and the IP.
>> what a laugh.  try, for example, RFC 826
> Perhaps a better example is RFC 6325.
>
> Tony.
Try this

"The IETFis and open and fair framework  produces standards for use in 
both networking and internetworking services for global communication" 
and the reasoning is that when ITU and other orgs like it were formed 
there was not Internetworking or Local Area Networks and so the IETF was 
formed to emerge the need to facilitate standards in these two key areas 
which other groups like ITU and IEEE with the underlying 802 work were 
not providing.

-- 
//Confidential Mailing - Please destroy this if you are not the intended recipient.

v2.14.0 | Report a Bug | By Email