Re: [trill] draft-ietf-trill-directory-assist-mechanisms-02 - 2 week WG (5/29 to 6/12)

Donald Eastlake <d3e3e3@gmail.com> Thu, 11 June 2015 18:41 UTC

Return-Path: <d3e3e3@gmail.com>
X-Original-To: trill@ietfa.amsl.com
Delivered-To: trill@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id E21421B2C80 for <trill@ietfa.amsl.com>; Thu, 11 Jun 2015 11:41:40 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.749
X-Spam-Level:
X-Spam-Status: No, score=-1.749 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, FREEMAIL_ENVFROM_END_DIGIT=0.25, FREEMAIL_FROM=0.001, HTML_MESSAGE=0.001, SPF_PASS=-0.001] autolearn=no
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id WX5x4i6gSi_1 for <trill@ietfa.amsl.com>; Thu, 11 Jun 2015 11:41:39 -0700 (PDT)
Received: from mail-ob0-x244.google.com (mail-ob0-x244.google.com [IPv6:2607:f8b0:4003:c01::244]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 37ACC1B2C7B for <trill@ietf.org>; Thu, 11 Jun 2015 11:41:39 -0700 (PDT)
Received: by obcuy5 with SMTP id uy5so3214175obc.0 for <trill@ietf.org>; Thu, 11 Jun 2015 11:41:38 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:in-reply-to:references:from:date:message-id:subject:to :cc:content-type; bh=dttDAa072wQEzh3CowhGnKmviOIfmBQ5maUQYCqR7aQ=; b=wVDiGDPmLj6eaGqwaX5xq0tlLaoIBx78c2jyoecYR8YY7dHZ3I7DQ5EWssCqArkO1z jlqjA5LEVD0l1wUK3TbpTBJ0Mf9NUZxYf0nEJek8b056BWnb5Xk/8xYTuAPGWK0JK+1J KCMrs/c5aawdLqOyC9YsOzFNfmqk7b1ONbwoMmV76SjEd0RSmljeSbMnX73iFV2NTgIb UYqAB7Xb3taBuyeWKHS9CyNmLWwHoN0XjO/HBoeggXPyutz7Pai7SkOVCoIL1OGZIwKp 7E5NwRuXzbldvOiubvR+U+5hnlWwF8vUqeOt2gfOYSS44FURfdtHlhUxFq1XPhLkAaLd A0fw==
X-Received: by 10.202.188.139 with SMTP id m133mr8531345oif.73.1434048098704; Thu, 11 Jun 2015 11:41:38 -0700 (PDT)
MIME-Version: 1.0
Received: by 10.76.153.2 with HTTP; Thu, 11 Jun 2015 11:41:23 -0700 (PDT)
In-Reply-To: <02c001d09a08$6f42f7a0$4dc8e6e0$@ndzh.com>
References: <02c001d09a08$6f42f7a0$4dc8e6e0$@ndzh.com>
From: Donald Eastlake <d3e3e3@gmail.com>
Date: Thu, 11 Jun 2015 14:41:23 -0400
Message-ID: <CAF4+nEGYpkv7h=G3Wo+7UoMTQVEGpNVHu0mJa7vfEs8MxcjCSQ@mail.gmail.com>
To: Susan Hares <shares@ndzh.com>
Content-Type: multipart/alternative; boundary=001a113dca2083a30d0518425739
Archived-At: <http://mailarchive.ietf.org/arch/msg/trill/Df_BhjKD5q43EQi9CGAcJTgTx6o>
Cc: Jon Hudson <jon.hudson@gmail.com>, "trill@ietf.org" <trill@ietf.org>
Subject: Re: [trill] draft-ietf-trill-directory-assist-mechanisms-02 - 2 week WG (5/29 to 6/12)
X-BeenThere: trill@ietf.org
X-Mailman-Version: 2.1.15
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: Thu, 11 Jun 2015 18:41:41 -0000

I support this draft as a good basis for ARP/ND optimization and reducing
unknown unicast flooding as well as detection of forged source addresses.

I am not aware of any IPR other than that which has already been disclosed.

Looking at the overall draft, in the Pull Directory section, there are four
different message types. While these all have a common header, the
remainder of the message can be various different things, commonly zero or
more instances of a record structure. Exactly what the remainder of the
message is can depend on whether the error field in the header is zero or
non-zero or on flags in the header. While I do not think there is any
technical problem here, I believe a table and section summarizing the
different cases would add clarity to the draft. (In addition, the typos and
clarifications pointed out by Gayle Noble should be incorporated.)

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

On Fri, May 29, 2015 at 8:10 AM, Susan Hares <shares@ndzh.com>; wrote:

> This is to begin a 2 week WG LC on the draft:
> draft-ietf-trill-directory-assist-mechanisms-02 (5/29 to 6/12).  You can
> find the draft at:
>
>
>
>
> http://datatracker.ietf.org/doc/draft-ietf-trill-directory-assist-mechanisms/
>
>
>
> There are 3 IPR statements
>
>
>
>
> https://datatracker.ietf.org/ipr/search/?submit=draft&id=draft-ietf-trill-directory-assist-mechanisms
>
>
>
> The authors (Donald, Linda, Radia, Igor, Yizhou) should indicate if they
> know if any additional IPR.
>
>
>
> A summary of the document is:
>
>
>
>   This document describes mechanisms for providing directory service to
>
>    TRILL (Transparent Interconnection of Lots of Links) edge switches.
>
>    The directory information provided can be used in reducing multi-
>
>    destination traffic, particularly ARP/ND and unknown unicast
>
>    flooding. It can also be used to detect traffic with forged source
>
>    addresses.
>
>
>
> One of our main objects for 2015 is to complete the directory services
> work.  Please answer a few questions
>
>
>
> 1)      Do you consider this draft for IESG publishing?
>
> 2)      Does the IPR cause you any concerns in agreeing to publish this
> as an TRILL standard?
>
> 3)      Does it provide necessary directory services for better
> deployment of TRILL?
>
> 4)      Are there any technical problems?
>
>
>
> Sue Hares and Jon Hudson
>