>that's also flawed. >You should be able to sign anything that you can. > >Suppose you receive it from an ibgp peer that sourced it but didn't sign it. > >-- >Jakob Heitz. >
What a BGPSEC router does when "originating" a new BGPSEC update is covered in Section 4.1. You are right -- the router can receive a prefix route (without an AS path) from an ibgp peer who sourced it, and the method of signing that (or any prefix being originated) is in Section 4.1. The discussion here (and John's comment) is related to text in Section 4.2, where we discuss what a BGPSEC router does when "propagating" a route advertisement. "Propagating" connotes here that the update (or route) was received from an eBGP peer. Sriram _______________________________________________ sidr mailing list [email protected] https://www.ietf.org/mailman/listinfo/sidr
