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

[Donald Eastlake <[e-mail]>]

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   [phone] (cell)
 155 Beaver Street, Milford, MA 01757 USA
 [e-mail]

On Fri, May 29, 2015 at 8:10 AM, Susan Hares <[e-mail]> 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
>