Multisession BGP IDR WG, IETF-63, Paris, France August 4, 2005

1
Multisession BGPIDR WG, IETF-63, Paris,
FranceAugust 4, 2005

• Chandra Appanna ltachandra_at_cisco.comgt
• John Scudder ltjgs_at_cisco.comgt

2
Multisession-BGP Version 00

• AFI/SAFI based session establishment
• Grouping of AFI/SAFI allowed
• Multisession capability format
• Capability code (1 octet) TBD
• Capability length (1 octet) 1
• Capability value (1 octet) Flags as below
• 0 1 2 3 4 5 6 7
• --------
• G Reserved
• --------

3
Version 00 Feedback

• Why only AFI/SAFI based sessions?
• Allow more flexible session content definition

4
Multisession-BGP Revised Version

• Any relevant capability allowed as session
  differentiator
• Grouping of AFI/SAFI / Session identifiers
  allowed
• Revised Multisession capability format
• Capability code (1 octet) TBD
• Capability length (1 octet) variable
• Capability value (1 octet) Flags followed
  by the list of capabilities that define a
  session.
• 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 2
• --------
• G Reserved
  
• ---------------------
  ------------
• One or more list of Capability codes
  (1 octet each)
• ---------------------
  ------------

5
Revised Version

• Capability list should be agreed to by peers.
• Was implicit with only AFI/SAFI approach but is
  now explicit.
• Approach allows any future capability to be used
  as session identifier as opposed to enumeration
  of valid session identifiers.
• For AFI/SAFI based sessions, use MP-BGP
  capability code as only code in list (which we
  believe will be the most prevalent form used).
• Negotiation and other rules do not change.
• Revised draft will be posted soon. Feedback
  welcome.