>> I'm personally a fan of keeping things simple .... what's the beef >> with tcp/22 here? > The set of source IPs needing access to tcp/22 for mgmt may not be the > same as the set of IPs needing access to tcp/22 for the rpki service
the router is the originator of the ssh connection, so there is no guess as to the port the cache will use. if you are a big fan of ip address based acls, it is the cache you will be protecting, not the router. i think the issues were o predictability and default config of router o other tools may want to reach server on the ssh vs other transport issue, i am less happy. the protocol specifies ssh, and this discussion would lead to standardizing the port on the cache/server to be used. that the testbed currently provides a few clear-text servers for implementors to test without ssh is merely a test service, and, imiho, should not be standardized. unless operators would care to argue that they trust security services which use clear-text. randy _______________________________________________ sidr mailing list [email protected] https://www.ietf.org/mailman/listinfo/sidr
