[trill] Review of draft-ietf-trill-oam-framework-01.txt

gayle noble <windy_1@skyhighway.com> Mon, 01 April 2013 05:13 UTC

Return-Path: <windy_1@skyhighway.com>
X-Original-To: trill@ietfa.amsl.com
Delivered-To: trill@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 3A42821F85ED for <trill@ietfa.amsl.com>; Sun, 31 Mar 2013 22:13:52 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -0.74
X-Spam-Level:
X-Spam-Status: No, score=-0.74 tagged_above=-999 required=5 tests=[BAYES_20=-0.74]
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 ptvWkWAbEo4V for <trill@ietfa.amsl.com>; Sun, 31 Mar 2013 22:13:50 -0700 (PDT)
Received: from skyhighway.com (skyhighway.com [63.249.82.6]) by ietfa.amsl.com (Postfix) with ESMTP id 4C47021F85D9 for <trill@ietf.org>; Sun, 31 Mar 2013 22:13:39 -0700 (PDT)
Received: from Firefly.skyhighway.com (dsl-63-249-88-160.static.cruzio.com [63.249.88.160]) by skyhighway.com with ESMTP id r315DbDx076312 for <trill@ietf.org>; Sun, 31 Mar 2013 22:13:38 -0700 (PDT)
Message-Id: <201304010513.r315DbDx076312@skyhighway.com>
X-Mailer: QUALCOMM Windows Eudora Version 7.1.0.9
Date: Sun, 31 Mar 2013 22:13:30 -0700
To: trill@ietf.org
From: gayle noble <windy_1@skyhighway.com>
In-Reply-To: <CAF4+nEG3H-UoaF=atise2E0dFDBEnkjNXauZ3sXC1_=tsCd0_g@mail.g mail.com>
References: <CAF4+nEEWsA6Lt6f3dTMG7RJDVa0Q+p3MWySUAgnLjWMZU9QX-g@mail.gmail.com> <CAF4+nEG3H-UoaF=atise2E0dFDBEnkjNXauZ3sXC1_=tsCd0_g@mail.gmail.com>
Mime-Version: 1.0
Content-Type: text/plain; charset="us-ascii"; format=flowed
Subject: [trill] Review of draft-ietf-trill-oam-framework-01.txt
X-BeenThere: trill@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: "Developing a hybrid router/bridge." <trill.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/trill>, <mailto:trill-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/trill>
List-Post: <mailto:trill@ietf.org>
List-Help: <mailto:trill-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/trill>, <mailto:trill-request@ietf.org?subject=subscribe>
X-List-Received-Date: Mon, 01 Apr 2013 05:13:52 -0000

  In reading some of the drafts it occurred to me that something 
should be specified as to how one should handle OAM messages that 
might be sent from outside the TRILL campus in the draft that talks 
about this.

Currently in draft draft-ietf-trill-oam-framework-01.txt, in the 
Security Considerations Section it says:
"Optionally authenticate communicating endpoints (MEPs and MIPs)"

To be real clear I think it should read something like::

"Optionally authenticate at communicating endpoints (MEPs and MIPs)
that an OAM message has originated at a communicating endpoint."

Perhaps even add in that if the OAM message fails authentication, the 
switch should log the attempt and notify the sys admin. Or maybe that 
is obvious?

gayle