1 / 8

Directory Assisted Edge

Directory Assisted Edge. Donald Eastlake, Linda Dunbar Huawei Technologies d3e3e3 @ gmail.com , linda.dunbar@ huawei.com. Directory Assisted Edge: Purposes. Support ARP/ND/RARP optimization by providing IP ⇔ MAC ⇔ nickname mapping information to ingress TRILL switches.

padma
Download Presentation

Directory Assisted Edge

An Image/Link below is provided (as is) to download presentation Download Policy: Content on the Website is provided to you AS IS for your information and personal use and may not be sold / licensed / shared on other websites without getting consent from its author. Content is provided to you AS IS for your information and personal use only. Download presentation by click this link. While downloading, if for some reason you are not able to download a presentation, the publisher may have deleted the file from their server. During download, if you can't get a presentation, the file might be deleted by the publisher.

E N D

Presentation Transcript

  1. Directory Assisted Edge Donald Eastlake, Linda Dunbar Huawei Technologies d3e3e3@gmail.com, linda.dunbar@huawei.com Directory Assist

  2. Directory Assisted Edge: Purposes • Support ARP/ND/RARP optimization by providing IP ⇔ MAC ⇔ nickname mapping information to ingress TRILL switches. • Support pre-encapsulation Directory Assist

  3. Status of Four Drafts • draft-ietf-trill-directory-assist-mechanisms-00 • draft-ietf-trill-ia-appsubtlv-01 • draft-ietf-trill-channel-tunnel-01 • draft-dunbar-trill-directory-assisted-encap-07 Directory Assist

  4. Status of the Four Drafts 1. draft-ietf-trill-directory-assist-mechanisms-00 • Provides both push and pull directory services. Push uses ESADI, pull uses RBridge Channel messages. • Push Directory needs known correction to state machine as discussed on the mailing list. For example see http://www.ietf.org/mail-archive/web/trill/current/msg06197.html • Pull needs some work – in particular there are some error cases not handled. • This draft almost entirely about the directory mechanisms themselves. Section 5 and most of section 4 are not about the directory. They should be split off into a separated working group draft. Directory Assist

  5. Status of the Four Drafts 2. draft-ietf-trill-ia-appsubtlv-01 • Specifies a TLV data structure for address mapping information. • Probably ready for WG Last Call after nit polishing for referenced drafts that have been published as RFCs and the like. Directory Assist

  6. Status of the Four Drafts 3. draft-ietf-trill-channel-tunnel-01 • Extends RBridgeChannel protocol (RFC7178) in a few ways, including the addition of security. • Referenced to by draft-ietf-trill-directory-assist-mechanisms for the security of Pull Directory messages. • Needs some work, particularly on the security parts. Directory Assist

  7. Status of the Four Drafts • draft-dunbar-trill-directory-assisted-encap-04 • Specifies a method for non-RBridge devices to perform TRILL encapsulation before sending data packet to edge RBridge. • Benefits include MAC learning table reduction and nickname conservations. • Being deferred for other work. Directory Assist

  8. END Directory Assist

More Related