Re: I-D Action: draft-ietf-idr-deprecate-as-set-confed-set-01.txt
john heasley <[email protected]> Tue, 5 Nov 2019 21:03:40 +0000
| Newsgroups | gmane.ietf.idr |
|---|---|
| Message-ID | <[email protected]> |
Tue, Nov 05, 2019 at 02:49:17PM -0500, Jeffrey Haas: > My meaning was that it's a best common practice in the operational sense, > not that someone wrote and RFC that has received that capital letter > blessing. IETF BCP or otherwise :) > If you network is a more specific in that aggregate, what policy construct > are you using to detect that your prefix is being covered in a less specific? All one can reasonably do is verify the origin of the shorter aggregate in the DMZ or, preferrably, origin validation. Am I missing something? _______________________________________________ Idr mailing list [email protected] https://www.ietf.org/mailman/listinfo/idr