Chris Morrow writes:
I believe the authors wanted this to progress, I believe there was
recently (8/29/2013) an updated version submitted, does it deal with the
outstanding comments? (the diff doesn't show much more than
boilerplate-like changes)
Should this be WGLC'd at this point?
Note that routers do not perform prefix origin validation (compute
the validation state as defined in [I-D.ietf-sidr-pfx-validate])
for IBGP learnt routes.
that is opposite of 6811 and running code
When a BGP speaker receives an UPDATE from a neighbor, it SHOULD
perform a lookup as
Note that routers do not perform prefix origin validation (compute
the validation state as defined in [I-D.ietf-sidr-pfx-validate])
for IBGP learnt routes.
that is opposite of 6811 and running code
When a BGP speaker receives an UPDATE from a neighbor, it SHOULD
perform a lookup
I believe the authors wanted this to progress, I believe there was
recently (8/29/2013) an updated version submitted, does it deal with the
outstanding comments? (the diff doesn't show much more than
boilerplate-like changes)
Should this be WGLC'd at this point?
-chris
co-chair-type-item
yes, do proceed to WGLC.
I believe the authors wanted this to progress, I believe there was
recently (8/29/2013) an updated version submitted, does it deal with the
outstanding comments? (the diff doesn't show much more than
boilerplate-like changes)
Should this be WGLC'd at this point?
