On 4/16/14, 7:14 PM, "Jerome Durand (jerduran)" <[email protected]> wrote:
>It is, thanks. I propose to slightly change the end of the first bullet >then: > > o You SHOULD accept from customers only AS(4)-Paths containing ASNs > belonging to (or authorized to transit through) the customer. If > you can not build and generate filtering expressions to implement > this, consider accepting only path lengths relevant to the type of > customer you have (as in, if they are a leaf or have customers of > their own), try to discourage excessive prepending in such paths. > *This loose policy could be combined with filters for specific > AS(4)-Paths that must not be accepted if advertised by the > customer.* I suggest a slight addition- “This loose policy could be combined with filters for specific AS(4)-Paths that must not be accepted if advertised by the customer, such as upstream transit provider or peer ASNs.” I think the examples make it clearer what we mean. Wes This E-mail and any of its attachments may contain Time Warner Cable proprietary information, which is privileged, confidential, or subject to copyright belonging to Time Warner Cable. This E-mail is intended solely for the use of the individual or entity to which it is addressed. If you are not the intended recipient of this E-mail, you are hereby notified that any dissemination, distribution, copying, or action taken in relation to the contents of and attachments to this E-mail is strictly prohibited and may be unlawful. If you have received this E-mail in error, please notify the sender immediately and permanently delete the original and any copy of this E-mail and any printout. _______________________________________________ OPSEC mailing list [email protected] https://www.ietf.org/mailman/listinfo/opsec
