Re: [trill] TRILL OAM Requirements: Connectivity
Erik Nordmark <nordmark@acm.org> Fri, 27 April 2012 16:29 UTC
Return-Path: <nordmark@acm.org>
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 5047F21F86A5 for <trill@ietfa.amsl.com>; Fri, 27 Apr 2012 09:29:34 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -102.599
X-Spam-Level:
X-Spam-Status: No, score=-102.599 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, 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 LgkVHwrTNn98 for <trill@ietfa.amsl.com>; Fri, 27 Apr 2012 09:29:33 -0700 (PDT)
Received: from b.mail.sonic.net (b.mail.sonic.net [64.142.19.5]) by ietfa.amsl.com (Postfix) with ESMTP id CD19821F868A for <trill@ietf.org>; Fri, 27 Apr 2012 09:29:33 -0700 (PDT)
Received: from [10.33.22.115] (128-107-239-233.cisco.com [128.107.239.233]) (authenticated bits=0) by b.mail.sonic.net (8.13.8.Beta0-Sonic/8.13.7) with ESMTP id q3RGTVBT019361 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO); Fri, 27 Apr 2012 09:29:31 -0700
Message-ID: <4F9AC96C.8010606@acm.org>
Date: Fri, 27 Apr 2012 09:29:32 -0700
From: Erik Nordmark <nordmark@acm.org>
User-Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.6; rv:12.0) Gecko/20120420 Thunderbird/12.0
MIME-Version: 1.0
To: Thomas Narten <narten@us.ibm.com>
References: <201204261939.q3QJdCfJ019770@cichlid.raleigh.ibm.com>
In-Reply-To: <201204261939.q3QJdCfJ019770@cichlid.raleigh.ibm.com>
Content-Type: text/plain; charset="ISO-8859-1"; format="flowed"
Content-Transfer-Encoding: 7bit
Cc: trill@ietf.org
Subject: Re: [trill] TRILL OAM Requirements: Connectivity
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: Fri, 27 Apr 2012 16:29:34 -0000
On 4/26/12 12:39 PM, Thomas Narten wrote:
> draft-tissa-trill-oam-req-00.txt has the following definition:
>
>> Connected: The term connected is used to indicate reachability; RB2
>> is connected to RB1 implies that RB2 is reachable from RB1.
>
> This is an unituitive definition to me. In my mind, "connected" means
> two device are (essentially) separated by a wire. Or, a node is
> "connected" to a network. I.e,. the two nodes are neighbors.
>
> Where does this definition of "connected" come from? Is this taken
> from somewhere else? Or is this a new definition for TRILL OAM?
When I read the document yesterday the "connected" term made me stumble
as well.
If this is a well-defined term in other OAM standards, then we should
include that definition in the terminology section so that it can be clear.
If it is not, then lets use a term that is more clear.
Erik
- [trill] TRILL OAM Requirements: Connectivity Thomas Narten
- Re: [trill] TRILL OAM Requirements: Connectivity Erik Nordmark