Re: [trill] AD review of draft-ietf-trill-over-ip-14

[Donald Eastlake <[e-mail]>]

Hi Alia,

On Tue, Feb 20, 2018 at 6:55 PM, Alia Atlas <[e-mail]> wrote:

> As is traditional, I have done my AD review of
> draft-ietf-trill-over-ip-14. First I would like to thank the authors -
> Donald, Margaret, Mingui, and Dacheng, as well as the reviewers for their
> work on this document.
>
> I did find one minor issue (below) and would recommend a spell-checker to
> catch several minor typos.  I will send this to IETF Last Call and place it
> on the IESG telechat on March 8.
>
> Minor:
>
> 1) In Sec 5.2: " An adjacency can be formed between two TRILL over IP
> transport ports if the intersection of the sets of encapsulation methods
> they support is not null. If that intersection is null, then no adjacency
> is formed."
> Given that Sec 5.0 says that the native encapsulation MUST be supported,
> how can the set be null?  Is this the set of encapsulation methods other
> than the native encapsulation?  Please clarify.
>

Unless the port is configured to use some other encapsulation X for all
types of traffic, then a port has to "support" UDP for the low bandwidth of
Hellos and other adjacency establishment PDUs. This is different from
advertising support for UDP which means a willingness to use it for data
traffic and LSPs. This needs to be clarified. Maybe "limited support"
versus "full support".

Thanks,
Donald
===============================
 Donald E. Eastlake 3rd   [phone] (cell)
 155 Beaver Street, Milford, MA 01757 USA
 [e-mail]


> Regards,
> Alia
>