1 / 8

draft-touch-trill-prob-00

draft-touch-trill-prob-00. Joe Touch Postel Center Director Research Assoc. Prof. CS & EE USC/ISI. Current Status. Redistributed author load Touch – Problem & Applicability Statement Gray – Architecture Perlman – Protocol Issues list Posted lists Discussion on issues New drafts Arch

dspataro
Télécharger la présentation

draft-touch-trill-prob-00

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. draft-touch-trill-prob-00 Joe Touch Postel Center Director Research Assoc. Prof. CS & EE USC/ISI

  2. Current Status • Redistributed author load • Touch – Problem & Applicability Statement • Gray – Architecture • Perlman – Protocol • Issues list • Posted lists • Discussion on issues • New drafts • Arch • Protocol

  3. Issues 1-3 (of 16) • #1 which version of ethernet is baseline? • STP, RSTP, VLAN, provider bridges, wireless, shortest path bridging, etc. (terminology issue) • #2 apply to current vs. larger scales? • Proposed starting point: • 1000 end-hosts in a single bridged LAN of 100 bridges • 100.000 end-hosts inside 1000 VLANs served by 10.000 bridges • #3 IF size is an issue... • what limits the size? STP/RSTP or broadcast traffic, or both?

  4. Issues 4-7 • #4 delivery requirements: • a) is in-order required? • b) is no-duplication required? • #6 address MSTP regions (esp sec 2.2) • as a way to limit STP scale/reconfiguration • IEEE 802.1Q Multiple Spanning Tree Protocol? • #7 differentiate between host reattachment effects • and bridge reattachment effects; the latter impact the STP more

  5. Issues 8-10 • #8 broadcast vs. subnet bcast vs. mcast • who gets a copy of multicast? all ports, or just subscribed? • #9 which addresses are not forwarded? • Bridge Group Addr 01-80-C2-00-00-00 (BPDU frames) • Pause Frame address 01-80-C2-00-00-01 • ?addresses 01-80-C2-00-00-00 to 01-80-C2-00-00-0F • #10 use campus (agreement at last meeting?) • or use "pool" or "set"

  6. Issues 11-13 • #11 internal/external, inside/outside terminology • CLOSED - moved to ARCH issues 12/08/2005 • #12 address VLAN configuration requirements • See recent discussion on mailing list. • #13 need configuration time examples • e.g. references to published research and a summary that shows how small changes can have large effects

  7. Issues 14-16 • #14 add risks of TRANSPARENT • (larger trees, slower to converge, etc.) • #15 sec 2.3 should be more clear about referring to computing backups to • use in case of failure - not that extra links makes routing easier. • #16 clarify ARP replay vs. proxu ARP • (a desired performance optimization) • (agreed on the mailing list)

  8. Next Steps • Approve as WG document • Revise • to unify terminology • to address issues • Restart issues resolution

More Related