On Mon, May 12, 2014 at 09:59:46AM -0400, Christopher Morrow wrote: > The authors of draft-ietf-grow-irr-routing-policy-considerations would > like to bring the draft to WGLC, this is that LC. Please have a read > through: > > > <https://datatracker.ietf.org/doc/draft-ietf-grow-irr-routing-policy-considerations/?include_text=1>
Wes covered most of the points I would raise - missing security considerations in particular. Basically, if you filter using IRR and the IRR has issues (perhaps maliciously induced), you'll have routing issues. The entire first part of the document does very well at outlining where the issues are and some of the paths for fixing them. The snippy bit of me wants there to be comments that a lot of the operational issues identified (e.g. "soft reconfig") are mostly one major vendor's issue, but I think it's enough to simply say "these were the sins of the past and no need to name names". (There is plenty of sin to go around.) In general, once the security considerations are addressed, this makes a fine Informational document and I think it's ready to go. What's frustrating is that the state of the art hasn't changed much since I was doing IRR related work in 2000. -- Jeff _______________________________________________ GROW mailing list [email protected] https://www.ietf.org/mailman/listinfo/grow
