jgs work-around alston
This commit is contained in:
parent
e84d93dcac
commit
cb1b85375f
1 changed files with 10 additions and 8 deletions
|
|
@ -10,7 +10,7 @@
|
||||||
|
|
||||||
<rfc category="std" consensus="true"
|
<rfc category="std" consensus="true"
|
||||||
submissionType="IETF"
|
submissionType="IETF"
|
||||||
docName="draft-ietf-sidrops-rov-no-rr-06"
|
docName="draft-ietf-sidrops-rov-no-rr-07"
|
||||||
ipr="trust200902" updates="8481">
|
ipr="trust200902" updates="8481">
|
||||||
|
|
||||||
<front>
|
<front>
|
||||||
|
|
@ -208,8 +208,8 @@
|
||||||
As storing these routes could cause problems in resource
|
As storing these routes could cause problems in resource
|
||||||
constrained devices, there MUST be a global operation, CLI, YANG,
|
constrained devices, there MUST be a global operation, CLI, YANG,
|
||||||
etc. allowing the operator to enable this feature, storing the
|
etc. allowing the operator to enable this feature, storing the
|
||||||
dropped routes. Such a control MUST NOT be per peer, as this
|
dropped routes. Such an operator control MUST NOT be per peer, as
|
||||||
could cause inconsistent behavior.
|
this could cause inconsistent behavior.
|
||||||
</t>
|
</t>
|
||||||
|
|
||||||
<t>
|
<t>
|
||||||
|
|
@ -247,11 +247,13 @@
|
||||||
|
|
||||||
<t>
|
<t>
|
||||||
If the BGP speaker's equipment has insufficient resources to
|
If the BGP speaker's equipment has insufficient resources to
|
||||||
support either of the two proposed options, it MUST NOT be used
|
support either of the two proposed options (keeping a full
|
||||||
for Route Origin Validation. The equipment should either be
|
AdjRibIn or at least the dropped routes), the equipment should
|
||||||
replaced with capable equipment or ROV not used. I.e. the knob
|
either be replaced with capable equipment or not use ROV. I.e.
|
||||||
in <xref target="rib"/> should only be used in very well known and
|
the configuration setting in <xref target="rib"/> should only be
|
||||||
controlled circumstances.
|
used in very well known and controlled circumstances. Such
|
||||||
|
circumstances could include operational work-arounds such as the
|
||||||
|
informed consent of the affected peers.
|
||||||
</t>
|
</t>
|
||||||
|
|
||||||
<t>
|
<t>
|
||||||
|
|
|
||||||
Loading…
Add table
Add a link
Reference in a new issue