|
|. | ... |. |
| (IGP AS 1) | | (IGP AS N) |
+-+ +-+Regards,
Yao
原始邮件
发件人：HannesGredler
收件人：刘尧00165286;
抄送人：Acee Lindem ;zzhang_i...@hotmail.com
;lsr@ietf.org ;
日 期 ：2020年07月29日 15:14
主 题 ：Re: [Lsr] "IGP Extensions for Segment Routing Service
Segment"-draft-lz-
f.org"
Subject: Re: [Lsr] "IGP Extensions for Segment Routing Service Segment"
-draft-lz-lsr-igp-sr-service-segments-02
Yao,
BGP-LS was designed to solve also the distribution of link-state information
between BGP speakers (see Figure 1 from RFC 7752 below).
Just ask yourself: why wou
Yao,
BGP-LS was designed to solve also the distribution of link-state information
between BGP speakers (see Figure 1 from RFC 7752 below).
Just ask yourself: why would one want to use a point to multipoint state
replication protocol as complex as BGP for *just* client server alike
replication
Hi Acee,
Thanks for reading the draft.
Yes, the main purpose of this draft is to carry the segment segment information
via IGP so only one node per AS need to be connected with the controller
through BGP-LS.
With the existing BGP-LS extension draft, it is certainly one solution to
configure
