This document describes mechanisms to optimize the ARP (Address
Resolution Protocol) and ND (Neighbor Discovery) traffic in TRILL
campus. Such optimization reduces packet flooding over a TRILL
This WG Draft is part of a directory service solution
that has been discussed for 3 years. Consensus
is strong on the complete solution.
This was sent back to the WG to resolve Discusses about
SEND & the draft is now believed to do that.
a) Are there existing implementations of the protocol?
No, and this draft is part of a 4 draft directory service dealing
with directory services. The four drafts are:
draft-ietf-trill-directory-assist-mechanisms () - describes the push/pull
draft-ietf-trill-channel-tunnel-05 - secure tunnel for directory push
draft-ietf-trill-ia-appsubtlv-05 - reporting of addresses for TRILL interfaces
in ISIS application sub-TLV (reduces/replaces need for ARP/ND )
draft-ietf-trill-arp-optimization - mechanism to optimize ARP and ND traffic
on TRILL campus
b) Have a significant number of vendors indicated their plan to
implement the specification?
Directory service mechanism are currently implemented as proprietary
fashions by every vendor that does some variant of TRILL (cisco, brocade, Huawei
and others). Until we get a full standard solution approved, the
existing vendors with "early TRILL" implementations have little reason
Huawei is planning implementations. Potentially Brocade and Cisco
could switch to these mechanisms, but unless IETF standards are out
as a set - this may not occur.
(note: no change to RFC2119 text, Shepherd is checking on the right RFC2199 text).
Routing QA review: Eric Gray
AD: Alia Atlas
Document Shepherd: Susan Hares