Hi Acee,
Thanks for incorporating my comments. Just a few more thoughts...
>
> - Figure 1, I dont understand the reason for labeling the servers as
> A,O,B,O,Z,O,O,O? Further, it might also be worth to explain the topology in
> words clearly marking which nodes belong to which tier as the figure could be
> confusing (for example, is Node 3 Tier-1 or 3 could be unclear from just the
> figure).
I’ve improved the figure and believe I’ve made the tiers evident.
Dhruv: I am a little unsure about the change. When I saw figures 3 and 4 in RFC 7938 (which I assume is the inspiration for this figure), I considered NODE 3,7,10,12 to be part of Tier 1.
Also why the labels of the server now A,B,B,A and X,Z,Z,X - perhaps that can be explained in words - because it is not obvious to me.
>
> - Various instances of articles (a, an, the) missing.
I didn’t see any of these offhand. Note that “policy” in this context can be considered plural.
Dhruv: We could leave those for the professionals in RPC but since you asked -
s/improve convergence/improve the convergence/
s/BGP sessions in hop-by-hop peering/BGP sessions in the hop-by-hop peering/
s/serialized by BGP best-path algorithm/serialized by the BGP best-path algorithm/
s/announcement of BGP-SPF link-state/announcement of the BGP-SPF link-state/
s/With this heuristic, discovery of BGP SPF/With this heuristic, the discovery of BGP SPF/
s/In the context of a data center fabric, direction is either/In the context of a data center fabric, the direction is either/
s/(same level in hierarchy)/(same level in the hierarchy)/
s/However, BGP speaker/However, a BGP speaker/
s/then configuration of IPv6 global addresses/then the configuration of IPv6 global addresses/
--
and found new spelling mistakes -
s/an adverised link/an advertised link/
s/BGP SPF route calcuation/BGP SPF route calculation/
Thanks!
Dhruv
-- last-call mailing list -- last-call@xxxxxxxx To unsubscribe send an email to last-call-leave@xxxxxxxx