NOTE: Sorry for the delay... end of year commitments are pressing... Addressing these comments in descending order.
See inline marked [tievens] On 12/11/18, 1:05 PM, "GROW on behalf of Jeffrey Haas" <[email protected] on behalf of [email protected]> wrote: Authors, In section 4.1, we define a new peer type to cover the loc-rib. This is mostly a pointer to section 4.2 of RFC 7854. 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 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ | Peer Type | Peer Flags | +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ | Peer Distinguisher (present based on peer type) | | | +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ | Peer Address (16 bytes) | ~ ~ +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ | Peer AS | +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ | Peer BGP ID | +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ | Timestamp (seconds) | +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ | Timestamp (microseconds) | +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ My question is with regards to Peer AS and Peer BGP ID: If either of those fields are altered on the router, what is the expected behavior in BMP? I have opinions, but would like to see yours. :-) [tievens] Per this draft, the BGP-ID and ASN are set to the global/default value or based on VRF (Local-RIB it conveys). The simple answer is if you change distinguishing (peer identity) values in the per-peer-header, you will need to send a PEER DOWN (using old values) and PEER UP (using new values). Regardless of this draft, if you send a new per-peer header with different values (sans type, flags, and timestamps), the receiver is likely going to treat that as a different peer. We/OpenBMP, and I believe others, use peer rd, peer addr, peer asn, and peer id as distinguishing identify for a peer, which enables us to multiplex different peers over the same TCP (bmp) stream. -- Jeff _______________________________________________ GROW mailing list [email protected] https://www.ietf.org/mailman/listinfo/grow _______________________________________________ GROW mailing list [email protected] https://www.ietf.org/mailman/listinfo/grow
