On 2015-06-19 14:00, Sandra Murphy wrote:
Anyone who commented on draft-ietf-sidr-bgpsec-protocol-11.txt is encouraged to review this version and report if your comments have or have not been addressed.
My comments have been addressed, but I have some questions about the way one of them was addressed:
Is the MP_REACH_NLRI encoded with or without the attribute flags and type code?
Don't the values of MP_REACH_NLRI's "Length of Next Hop Network Address" and "Network Address of Next Hop" change with each hop, making it infeasible for remote ASes to verify the origin's signature?
MP_REACH_NLRI has a reserved field that "MUST be set to 0, and SHOULD be ignored upon receipt". If a BGPsec speaker receives an update where reserved is non-zero, what should it do? With the current text, I could interpret "SHOULD be ignored upon receipt" as meaning either "calculate the signature using the reserved field as received" or "calculate the signature using all zeroes in place of the reserved field".
-- David Eric Mandelberg / dseomn http://david.mandelberg.org/ _______________________________________________ sidr mailing list [email protected] https://www.ietf.org/mailman/listinfo/sidr
