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

Donald Eastlake <d3e3e3@gmail.com> Wed, 03 April 2013 21:06 UTC

Return-Path: <d3e3e3@gmail.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 66B2621F8F10 for <trill@ietfa.amsl.com>; Wed, 3 Apr 2013 14:06:49 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -103.599
X-Spam-Level:
X-Spam-Status: No, score=-103.599 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, RCVD_IN_DNSWL_LOW=-1, 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 p9ocXMeaui2O for <trill@ietfa.amsl.com>; Wed, 3 Apr 2013 14:06:49 -0700 (PDT)
Received: from mail-oa0-f42.google.com (mail-oa0-f42.google.com [209.85.219.42]) by ietfa.amsl.com (Postfix) with ESMTP id E218821F8F0D for <trill@ietf.org>; Wed, 3 Apr 2013 14:06:48 -0700 (PDT)
Received: by mail-oa0-f42.google.com with SMTP id i18so2057482oag.1 for <trill@ietf.org>; Wed, 03 Apr 2013 14:06:48 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=x-received:mime-version:in-reply-to:references:from:date:message-id :subject:to:cc:content-type; bh=q2ONY2P+iF36qJiSyitf1egSXY1qnzN6DdL4FXCmOdQ=; b=lCI5Nxv2xzrtbxf92cgXjsXhSAogI4BWEw817qJXJXhBkNimOXy09+C/JSpUdQju/A m/tCO7+BWM7b9MHpL6077wSQXJFHPi5Il+rD8Xi6911PzAe+FxCJ1xtnA623pJXINCSZ zxRaig8yHgIsQoXylW0NZPE2aRUeomwmbufGFB/RYb1PPTKZ9szPlRePwwitDhaHxoCO d8XJyPF44jov14OygLErhnbrDafcnpfkPkve12dTfOF+ZOmp57++xoT/v0EhbOjlmTMt TeqZQJ96te0Ozxh82DxrUXiZDqpj5m+BarC/QwbrXK+QgXMs6frr3ZkPvX7PGsY0t1sp K+Mg==
X-Received: by 10.60.118.104 with SMTP id kl8mr2221111oeb.68.1365023208507; Wed, 03 Apr 2013 14:06:48 -0700 (PDT)
MIME-Version: 1.0
Received: by 10.76.139.200 with HTTP; Wed, 3 Apr 2013 14:06:28 -0700 (PDT)
In-Reply-To: <201304010513.r315DbDx076312@skyhighway.com>
References: <CAF4+nEEWsA6Lt6f3dTMG7RJDVa0Q+p3MWySUAgnLjWMZU9QX-g@mail.gmail.com> <CAF4+nEG3H-UoaF=atise2E0dFDBEnkjNXauZ3sXC1_=tsCd0_g@mail.gmail.com> <201304010513.r315DbDx076312@skyhighway.com>
From: Donald Eastlake <d3e3e3@gmail.com>
Date: Wed, 3 Apr 2013 17:06:28 -0400
Message-ID: <CAF4+nEFf27q0D3W+rf+yN46NV8YaZ2aWji3jjRDng_TexmzDSQ@mail.gmail.com>
To: gayle noble <windy_1@skyhighway.com>
Content-Type: text/plain; charset=ISO-8859-1
Cc: trill@ietf.org
Subject: Re: [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: Wed, 03 Apr 2013 21:06:49 -0000

Hi Gayle,

On Mon, Apr 1, 2013 at 1:13 AM, gayle noble <windy_1@skyhighway.com> wrote:
>  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."

Thanks for the comment...
Maybe it should even say "... has originated at an appropriate
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?

I don't think the IETF is complete consistent on this point but
generally IETF specifications concentrate on the bits on the wire and
the state machines at the end points so they frequently omit saying
anything explicit about logging...

Thanks,
Donald
=============================
 Donald E. Eastlake 3rd   +1-508-333-2270 (cell)
 155 Beaver Street, Milford, MA 01757 USA
 d3e3e3@gmail.com

> gayle