>> So you're saying that backup paths should be able to be hidden until >> they are actually used? Can you put together a list of the specific >> information you think needs to be hidden, and back it up with use cases? > > No. I hear that it is not a requirement to disclose them ahead of time. The > ASes along the path just need to be able to determine that it is valid before > it is accepted.
Then why doesn't the "requirements document" actually state this? Again, my argument has been, and still is, that the "requirements document," as presented, isn't requirements. If this is a requirement, then list it. I'm not arguing for any particular system, which is where the argument always tends to flow, but only that a requirements document actually list requirements. The only thing I get out of reading this document is, "S-BGP is acceptable and required." Russ
signature.asc
Description: OpenPGP digital signature
_______________________________________________ sidr mailing list [email protected] https://www.ietf.org/mailman/listinfo/sidr
