PIM Pop Count <draft-farinacci-pim-pop-count-00.txt>

1
PIM Pop Countltdraft-farinacci-pim-pop-count-00.tx
tgt

• Dino Farinacci, Procket Networks
• Greg Shepherd, Procket Networks
• 60th IETF San Diego
• August 2004

2
Agenda

• Problem Statement
• Proposal
• Draft Status

3
Problem Statement

• There is no mechanism today to get distribution
  tree accounting
• There are inefficient out-of-band methods
• There is no in-band method to get MTU information
  efficiently
• There is no way to get accounting information for
  part of the data distribution tree

4
Proposal

• Have the PIM protocol carry a definitive amount
  of accounting information
• Carry accounting data in Join messages per
  multicast route entry
• Encode it efficiently
• Report changes only at periodic Join intervals
• Have PIM Hello negotiate the this new capability

5
Proposal PIM Hello Messages

• If neighbor doesnt include option, Joins have
  original format

0 1 2
3 0 1 2 3 4 5 6 7 8 9 0 1 2 3
4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1
-------------------------
------- 24
8
-------------------------
-------
Unallocated Flags
-------------------------
-------
6
Proposal PIM JP Messages

• New Encoding-Type code-point which can support
  all address families
• Used in join-list entries only
• Accounting data includes
• Transit/Stub oif-list counts
• Max/min link speed
• Domain/Node/Diameter/Time-zone counts
• Effective MTU
• Flags to determine if tree is ASM/SSM and
  auto/manual tunnels present

7
Proposal PIM JP Messages
0 1 2
3 0 1 2 3 4 5 6 7 8 9 0 1 2 3 4
5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1
-------------------------
------- Addr Family Encoding
Type Rsrvd SWR Mask Len
-------------------------
-------
Source Address
-------------------------
------- Effective MTU
Unallocated Flags (Reserved) atAS
-------------------------
------- Domain Count Node Count
Diameter Count TZ Count
-------------------------
------- Transit Oif-List Count
Stub Oif-List Count
-------------------------
------- Minimum Speed Link
Maximum Speed Link
-------------------------
-------
8
Proposal - Benefits

• Can easily get attributes for a distribution tree
  at any on-tree router
• Therefore provides sub-tree accounting as well
• Can determine degrees of fan-out for fan-out
  engineering
• Can determine if native multicast is used across
  the distribution tree
• Lower latency to determine effective MTU

9
Draft Status

• Draft posted to ID directory in May 2004
• draft-farinacci-pim-pop-count-00.txt
• Received one set of comments
• Please send more
• Any other accounting data you think is important?
• Want this a working group draft?

10
Questions?