-08 posted addressing alston's discuss
This commit is contained in:
parent
cb1b85375f
commit
0845469ca5
1 changed files with 10 additions and 7 deletions
|
|
@ -10,7 +10,7 @@
|
|||
|
||||
<rfc category="std" consensus="true"
|
||||
submissionType="IETF"
|
||||
docName="draft-ietf-sidrops-rov-no-rr-07"
|
||||
docName="draft-ietf-sidrops-rov-no-rr-08"
|
||||
ipr="trust200902" updates="8481">
|
||||
|
||||
<front>
|
||||
|
|
@ -248,12 +248,15 @@
|
|||
<t>
|
||||
If the BGP speaker's equipment has insufficient resources to
|
||||
support either of the two proposed options (keeping a full
|
||||
AdjRibIn or at least the dropped routes), the equipment should
|
||||
either be replaced with capable equipment or not use ROV. I.e.
|
||||
the configuration setting in <xref target="rib"/> should only be
|
||||
used in very well known and controlled circumstances. Such
|
||||
circumstances could include operational work-arounds such as the
|
||||
informed consent of the affected peers.
|
||||
AdjRibIn or at least the dropped routes), the equipment SHOULD
|
||||
either be replaced with capable equipment or SHOULD NOT be used
|
||||
for ROV.
|
||||
</t>
|
||||
|
||||
<t>
|
||||
The configuration setting in <xref target="rib"/> should only be
|
||||
used in very well known and controlled circumstances where the
|
||||
scaling issues are well understood and anticipated.
|
||||
</t>
|
||||
|
||||
<t>
|
||||
|
|
|
|||
Loading…
Add table
Add a link
Reference in a new issue