1 / 10

TRILL Working Group

TRILL Working Group. TRansparent Interconnection of Lots of Links Mailing list: rbridge@postel.org Website: http://www.postel.org/rbridge Tools site: http://tools.ietf.org/wg/trill/ Co-Chairs: Erik Nordmark erik.nordmark@oracle.com Donald E. Eastlake 3rd d3e3e3@gmail.com. Note Well !.

garrison-pearson
Download Presentation

TRILL Working Group

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. TRILL Working Group TRansparent Interconnection of Lots of Links Mailing list: rbridge@postel.org Website: http://www.postel.org/rbridge Tools site: http://tools.ietf.org/wg/trill/ Co-Chairs: Erik Nordmark erik.nordmark@oracle.com Donald E. Eastlake 3rd d3e3e3@gmail.com IETF TRILL WG

  2. Note Well ! • Any submission to the IETF intended by the Contributor for publication as all or part of an IETF Internet-Draft or RFC and any statement made within the context of an IETF activity is considered an "IETF Contribution". Such statements include oral statements in IETF sessions, as well as written and electronic communications made at any time or place, which are addressed to: • The IETF plenary session — The IESG, or any member thereof on behalf of the IESG • Any IETF mailing list, including the IETF list itself, any working group or design team list, or any other list functioning under IETF auspices — Any IETF working group or portion thereof • The IAB or any member thereof on behalf of the IAB • The RFC Editor or the Internet-Drafts function • All IETF Contributions are subject to the rules of All IETF Contributions are subject to the rules of RFC 5378 and RFC 3979 (updated by RFC 4879). • Statements made outside of an IETF session, mailing list or other function, that are clearly not intended to be input to an IETF activity, group or function, are not IETF Contributions in the context of this notice. • Please consult RFC 5378 and RFC 3979 for details. • A participant in any IETF activity is deemed to accept all IETF rules of process, as documented in Best Current Practices RFCs and IESG Statements. • A participant in any IETF activity acknowledges that written, audio and video records of meetings may be made and may be available to the public. IETF TRILL WG

  3. Agenda TUESDAY, 1300-1500, Room: 0.4 BrusselsChairs: Erik Nordmark, Donald Eastlake 3rd • 5 min. Administrativia (scribes etc), Agenda Bashing, Chairs • 10 min. Review of Existing Milestones, Document Status, and Non-IETF Code Point Allocations, Chairs • 20 min. ARP for Large DC Problem StatementLinda Dunbar, Sue Hares • draft-dunbar-arp-for-large-dc-problem-statement-00.txt • 15 min. TRILL ARP/ND Optimization, Radia Perlman • 10 min. Requirements for multicast to unicast optimization in TRILL Yizhou Li • draft-liyz-trill-reqs-mlt2uni-opt-00.txt • 15 min. Charter Update, Chairs IETF TRILL WG

  4. Goals and Milestones • COMPLETED • (Earlier milestones related to accepting drafts as working group items and reviews not listed.) • Start work with routing area WG(s) to undertake TRILL extensions   • Submit problem and applicability statement to IESG for Informational RFC [Published as RFC 5556] • Base protocol specification submitted to the IESG for publication as a Proposed Standard • First draft showing what is needed for MIB IETF TRILL WG

  5. Goals and Milestones (cont.) • OVERDUE • None • FUTURE • July 2010: Re-charter or shut down the WG IETF TRILL WG

  6. WG Document Status TRILL Working Group RFC / Approved • TRILL: Problem and Applicability Statement • RFC 5556 • RBridges: Base Protocol Specification • draft-ietf-trill-rbridge-protocol-16 • Approved 15 March 2010 by the IESG as an IETF Proposed Standard, in the RFC Editor queue. • Currently blocked by normative reference to draft on ISIS code points for TRILL IETF TRILL WG

  7. TRILL Base ProtocolNon-IETF Code Points • Ethertypes and Multicast Addresses BlockHave been allocated by the IEEE Registration Authority • Ethertypes: • TRILL: 0x22F3 • L2-IS-IS: 0x22F4 • Multicast Addresses: • 01-80-C2-00-00-40 All-RBridges • 01-80-C2-00-00-41 All-IS-IS-RBridges • 01-80-C2-00-00-42 All-ESADI-RBridges • 01-80-C2-00-00-43 to 01-80-C2-00-00-4F Unassigned IETF TRILL WG

  8. TRILL Base ProtocolNon-IETF Code Points • NLPID – Network Layer Protocol ID • Used in IS-IS Protocols Supported TLV. • 0xC0 has been allocated for TRILL. • Draft documenting this blocked on normative reference to base protocol draft. IETF TRILL WG

  9. WG Document Status (cont.) Other TRILL WG Drafts: • RBridges: VLAN Mapping • draft-ietf-trill-vlan-mapping-02 • Needs update based on mailing list comments • Definitions of Managed Objects for RBridges • draft-ietf-trill-rbridge-mib-00 • RBridges: TRILL Header Options • draft-ietf-trill-rbridge-options-02 IETF TRILL WG

  10. Relevant non-TRILL WG Drafts • PPP TRILL Protocol Control Protocol • draft-ietf-pppext-trill-protocol-01.txt • IS-IS Extensions for Layer 2 Systems • draft-eastlake-isis-trill-01.txt • To be posted as an ISIS WG draft after Maastricht. • Base protocol specification is normatively dependent on approval of TRILL ISIS code points and data structures. IETF TRILL WG

More Related