Base Protocol Document: -03 to -04 to -05 Changes

1
Base Protocol Document-03 to -04 to -05 Changes

• Donald Eastlake 3rd
• 1-508-786-7754
• Donald.Eastlake_at_motorola.com

2
TRILL Base Protocol Draft Changes that Have
Occurred

• 17 Jan. 2007 draft-ietf-trill-rbridge-protocol-02
• 5 March 2007 draft-ietf-trill-rbridge-protocol-03
• March 2007 IETF Meeting Prague
• Changes from -03 to -04
• 22 June 2007 draft-ietf-trill-rbridge-protocol-04
• Changes from -04 to -05
• 10 July 2007 draft-ietf-trill-rbridge-protocol-05
• July 2007 IETF Meeting Chicago

3
Changes from -03 to -04

• Terminology
• TRILL is the protocol
• RBridges are the devices
• Other see http//www.postel.org/rbridge/terminolo
  gy.html
• Area Removed
• ARP/ND Optimization
• Included learning of IP addresses, optimization
  of some ARP/ND traffic

4
Changes from -03 to -04

• TRILL Header Items Added/Changed
• Add Total Options Size Field. All other options
  details deferred to a separate document.
• Change TRILL Header to expand Version field to
  the Variation (V) field. Distinguish TRILL data
  and IS-IS messages by using Variation 0 and 1.
• -------------------------
  -------
• TRILL Ether Type V
  MROp-Length Hop Count
• -------------------------
  -------
• Egress RBridge Nickname Ingress
  RBridge Nickname
• -------------------------
  -------

5
Changes from -03 to -04

• Other Technical Items Added/Changed
• End station address learning from decapsulated
  TRILL messages as well as received native frames.
  Transfer of end station addresses via per VLAN
  IS-IS optional.
• Will be covered in a separate presentation
• Add nickname allocation priority and optional
  configuration. Reserve nicknames 0 and 0xFFFF.
• Move multicast router attached bit and group
  membership information from per VLAN to core
  IS-IS instance so they can be used to prune
  trees.
• Discard TRILL data frames received on a port that
  does not have an IS-IS adjacency on it.
• Additional material on inner/outer VLAN tags.

6
Changes from -03 to -04

• Other Technical Items Added/Changed
• Designated RBridges determination per VLAN with
  priority for becoming DRB also per VLAN.
• For load splitting and correctness

Rbridge B
Rbridge B
VLANS
Rbridge A
Rbridge A
7
Changes from -03 to -04

• Yet More Stuff Added/Changed
• New top level section of Pseudo Code with
  existing and additional pseudo code.
• Consistently state that VLAN pruning and IP
  derived multicast pruning of distribution trees
  are SHOULD.
• Incremental Deployment Considerations Section.
• Revised and extended Security Considerations
  section particularly incorporating reference to
  IS-IS security.

8
Changes from -03 to -04

• Minor Items
• Split RBridge details section into Header and
  Other.
• Divide IANA Considerations section into IANA and
  IEEE parts.
• Add IANA considerations for TRILL Header
  variations and reserved bit and normative
  references to RFCs 2434 and 4020.
• Add TRILL message variations supported to the per
  RBridge link state information.

9
Changes from -04 to -05

• Eliminate V bit
• Change to distinguish TRILL IS-IS from TRILL data
  frames based on the Inner.MacDA instead of a
  TRILL Header bit.
• TRILL frame gt TRILL Ethertype
• TRILL data gt Inner.MacDA ! All-Rbridges
• TRILL IS-IS gt Inner.MacDA All-Rbridges
• Core IS-IS gt no inner VLAN Tag
• Per VLAN IS-IS gt inner VLAN Tag present

10
Changes from -04 to -05

• Technical Items Added/Changed
• Permit optional unicast transmission of
  multi-destination TRILL frames when there is only
  one receiver out a port.
• Also mentioned in Incremental Deployment Section.
• Split IP multicast router attached bit in two so
  you can separately indicate attachment of IPv4
  and IPv6 routers.
• Provide that these bits must be set if an RBridge
  does not actually do multicast control snooping
  on ingressed traffic so it will get all multicast
  traffic (per VLAN).

11
Changes from -04 to -05

• Other multicast improvements.
• Drop references to PIM.
• Improve discussions of IGMP, MLD, and MRD
  messages.
• Provide for optional encoding into V of pruning
  to make the job of transit Rbridges easier.
• V 0, prune on VLAN, frame not fully analyzed
• V 1, should only prune on VLAN
• V 2, should prune on VLAN and to multicast
  listeners and routers
• V 3, should prune on VLAN and to multicast
  routers