Re: [Bgp-autoconf] Progress report of design team on IDR virtual meeting

["Dongjie (Jimmy)" <[e-mail]>]

Hi Randy, 

Thanks for your further clarification. Thus what you suggest is a generic capability to communicate arbitrary attributes according to the operators' need. Is my understanding correct?

" But there SHOULD be a protocol provision for communicating arbitrary attributes so that the operator may configure as needed for their environment."

Do you think such information exchange should happen in the peer autodiscovery/autoconf stage? 

I'd also appreciate other team members' opinion on:

1. Whether it is a requirement to bgp autoconf, or it should be done after BGP session is established?

2. Whether it should be a generic capability for operator's customization, or some guidance or structure needs be specified as part of the protocol design?

Best regards,
Jie

-----Original Message-----
From: Randy Bush [mailto:[e-mail]] 
Sent: Wednesday, March 25, 2020 6:38 AM
To: Dongjie (Jimmy) <[e-mail]>
Cc: [e-mail]
Subject: Re: [Bgp-autoconf] Progress report of design team on IDR virtual meeting

jimmy,

my apologies for my poor communication.  let me try with text

  Two prospective peers SHOULD be able to exchange arbitrary attributes
  to communicate things such as position or role in a topology, link
  speeds and/or loading, preferred time of day, favorite ice cream, etc.
  None of these example attributes are requirements, will be specified,
  given code points, etc. in the protocol design.  But there SHOULD be a
  protocol provision for communicating arbitrary attributes so that the
  operator may configure as needed for their environment.

hope that helps.

randy