IETF Logo Mail Archive

Re: Protocol Definition

Abdussalam Baryun <abdussalambaryun@gmail.com> Thu, 21 June 2012 20:00 UTC

Return-Path: <abdussalambaryun@gmail.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 5AB2321F8742 for <ietf@ietfa.amsl.com>; Thu, 21 Jun 2012 13:00:17 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -3.599
X-Spam-Level:
X-Spam-Status: No, score=-3.599 tagged_above=-999 required=5 tests=[AWL=0.000, BAYES_00=-2.599, RCVD_IN_DNSWL_LOW=-1]
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 SvmM4+jBZCWP for <ietf@ietfa.amsl.com>; Thu, 21 Jun 2012 13:00:16 -0700 (PDT)
Received: from mail-vc0-f172.google.com (mail-vc0-f172.google.com [209.85.220.172]) by ietfa.amsl.com (Postfix) with ESMTP id 6306121F862F for <ietf@ietf.org>; Thu, 21 Jun 2012 13:00:16 -0700 (PDT)
Received: by vcqp1 with SMTP id p1so602148vcq.31 for <ietf@ietf.org>; Thu, 21 Jun 2012 13:00:15 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:in-reply-to:references:date:message-id:subject:from:to :content-type; bh=T7JghJFBp3ElVtD6GzevNmJoqGpEzFjS3XkKnP49r3g=; b=d/KlGIwswr9vpQjb7Mi+ZeooxgqgguuJ28AsROYmevypCXmj+m3M00BONe7sPqQ0Du VTUXHMgUmYPirOjJ/0X0OD0XtNPGzCmK+Gk6MIVOAX3aZqwpt8/J40V7ZbU9oLmgsNII qlMIg5/xA62VqA+0hzrdHNMXlCNWuV9wEhvaB6doRBY9BaiDlyBPeM6cwGpYzs3lVdZJ D15A3aLWTPORKCfh67isRd6Gf8GaqvLk7yNqMdHgdIAnJApDumL7JWJsC4cxHCZPM78o AO7iXpkTzMM18iCp0zMw/rtKz2yeHM08nbaq828T5AewMxF1JfGR4PBf3FYlfiEQCy96 WRHw==
MIME-Version: 1.0
Received: by 10.220.140.193 with SMTP id j1mr14410099vcu.4.1340308815648; Thu, 21 Jun 2012 13:00:15 -0700 (PDT)
Received: by 10.220.211.72 with HTTP; Thu, 21 Jun 2012 13:00:15 -0700 (PDT)
In-Reply-To: <CADnDZ8_5nH7gNvR_LAB3wJ0zfKh-G0WmWbTm6yDq-M+LMajfbg@mail.gmail.com>
References: <CADnDZ8_5nH7gNvR_LAB3wJ0zfKh-G0WmWbTm6yDq-M+LMajfbg@mail.gmail.com>
Date: Thu, 21 Jun 2012 22:00:15 +0200
Message-ID: <CADnDZ8_XSKgmOq+pfiq=rT5mVRqLk8CnyFKU9CNd+ZG81DJ_xA@mail.gmail.com>
Subject: Re: Protocol Definition
From: Abdussalam Baryun <abdussalambaryun@gmail.com>
To: ietf <ietf@ietf.org>
Content-Type: text/plain; charset="ISO-8859-1"
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, 21 Jun 2012 20:00:17 -0000

I got help from a friend, to amend the definition statement to:

All protocols in IETF are based on the Internet or/and the IP.

AB
++++
<Defining any protocol has to consider somehow it's networks>


On 6/18/12, Abdussalam Baryun <abdussalambaryun@gmail.com> wrote:
> IMO the important issue in any definition is to include how the IETF
> defines protocol,
> this may be find in some RFCs :)
>
> The IP is the main protocol, and all protocols in IETF are based on IP
> and Internet.
>
> AB

v2.23.0 | Report a Bug | By Email