[sidr] IETF Technology Terminology and Protocol Implications

Abdussalam Baryun <abdussalambaryun@gmail.com> Sat, 07 July 2012 12:02 UTC

Return-Path: <abdussalambaryun@gmail.com>
X-Original-To: sidr@ietfa.amsl.com
Delivered-To: sidr@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 95DEF21F8629; Sat, 7 Jul 2012 05:02:40 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.657
X-Spam-Level:
X-Spam-Status: No, score=-2.657 tagged_above=-999 required=5 tests=[AWL=-0.663, BAYES_00=-2.599, DEAR_SOMETHING=1.605, 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 woSmBy6vL1gT; Sat, 7 Jul 2012 05:02:36 -0700 (PDT)
Received: from mail-vb0-f44.google.com (mail-vb0-f44.google.com [209.85.212.44]) by ietfa.amsl.com (Postfix) with ESMTP id A411221F8596; Sat, 7 Jul 2012 05:02:35 -0700 (PDT)
Received: by vbbez10 with SMTP id ez10so7180893vbb.31 for <multiple recipients>; Sat, 07 Jul 2012 05:02:54 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:date:message-id:subject:from:to:cc:content-type; bh=yuiP59dEvncHK3ydzVGqErSq7xVJFNxbF85ei0c9z0g=; b=fSY627+OXrtv5EqEg/IaKYJh+QGG+AV9L6Mq1X+ZcNKLhJKPTeTeBl3AhXRkLfKar+ OPlZgeBzfpiPq4Ez5yC1uTpaHiOZ20S61wwl38rhvHQF65LUILpjOjpBEo32xH+Krfbi JAq5A7DB3slzybXqsj84sMi5acVYW4QAfr92QetrJhlUowAcURHZJkKhZZ5f2KGY91zN WUEolxDjmAumITKdV2H3GJFL0sJrh+av++LEGADVTTOjmJtEtLhrPi6xIPnOuSMe70C/ q5yGn2N1xjyM+3gegAuxHK7ySUr6ACvWCA88WeDWmhmmoXmBeLSoUR+l3d42CyL4+x7c UYqA==
MIME-Version: 1.0
Received: by 10.52.94.36 with SMTP id cz4mr13657353vdb.10.1341662574357; Sat, 07 Jul 2012 05:02:54 -0700 (PDT)
Received: by 10.220.110.130 with HTTP; Sat, 7 Jul 2012 05:02:54 -0700 (PDT)
Date: Sat, 07 Jul 2012 14:02:54 +0200
Message-ID: <CADnDZ89Z3shWVjFcadwKdpJG+FYRAxYj+sGNCKO6v+DeTQpsDg@mail.gmail.com>
From: Abdussalam Baryun <abdussalambaryun@gmail.com>
To: ietf <ietf@ietf.org>
Content-Type: text/plain; charset="ISO-8859-1"
Cc: kitten@ietf.org, websec@ietf.org, ipsec@ietf.org, opsec@ietf.org, "iesg@ietf.org" <iesg@ietf.org>, sidr@ietf.org, stephen.farrell@cs.tcd.ie, hokey@ietf.org, karp@ietf.org
Subject: [sidr] IETF Technology Terminology and Protocol Implications
X-BeenThere: sidr@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: Secure Interdomain Routing <sidr.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/sidr>, <mailto:sidr-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/sidr>
List-Post: <mailto:sidr@ietf.org>
List-Help: <mailto:sidr-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/sidr>, <mailto:sidr-request@ietf.org?subject=subscribe>
X-List-Received-Date: Sat, 07 Jul 2012 12:02:41 -0000

Dear Sir or Madam,

I suggest for terminology-documents in WGs to consider the security
terms that are related to WG, and terms implication for security
considerations. Security consideration section as required by RFC2223
(section-9), which can be used to define things. For example the
approach was used in RFC2119 and in the I-D [AB].

Regarding RFCs that specify protocols, I suggest they mention in the
security consideration section additionally to the protocol security
implication also the related works of security WGs in IETF. This will
build interaction between WGs and will help the readers and users.

What do you think? please advise or comment, thanking you,

References:
[RFC2223] http://www.ietf.org/rfc/rfc2223.txt
[RFC2119] http://www.ietf.org/rfc/rfc2119.txt
[AB] http://tools.ietf.org/id/draft-baryun-manet-terminology-00.txt

Yours Faithfully,

Abdussalam Baryun
University of Glamorgan, UK

*****************************************************************************
This email and any attachments are confidential to the intended recipient
and may also be privileged. If you are not the intended recipient please
delete it from your system and notify the sender. The contents are comply
to the IETF regulations, and WG procedures. You should not copy the
email nor use it for any other purpose, nor disclose, nor distribute its
contents to any other person.
*****************************************************************************