[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: v6ops-routing-guidelines ID

- thanks for comments
- partial response below. more later.

Le 07-03-19 à 10:50, Danny McPherson a écrit :


Also, what is the intention of this document?  BCP, at best,
or perhaps even informational?  I would think the latter like
RFC 3330.  It's current status is currently labeled as "Standards
Track", which I suspect is a bit off base.
my fault. I found that too when doing the ID-nits. Intent was informational or BCP. will be fixed in -02. 



Some other nits:

2.6.  Default Route
The default unicast route (::) may be advertised in an IGP. It must 
   not be advertised in an EGP unless it has been requested by the
   recipient.

How does one request a default route?
well, that was the suggestion text from someone who provided comment on the previous version. The intent of the suggestion was to avoid the use of "downstream" which is ambiguous. Do you have any suggestion for text? 




2.8.  Unknown addresses

   Any non listed address above must not be advertised and should be
filtered out. Future work might reserve additional address space for 
   protocol use which might require specific routing guidelines.  The
reader should refer to newer versions of the normative references in 
   this document to verify the existence of newer protocol address
   space.

Where would operators find such a list if we're recommending they
filter these address spaces?
it currently says newer versions of the normative references (that is one way one can do and find). 
Any suggestion?



In section 3.0 in addition to the BCP 84 reference, a BCP 38
reference should be included.


ok. agreed. will add.

Marc.