Sharing: No permission required.
This is public share as desired.
[email protected]

> -----Original Message-----
> From: [email protected] [mailto:[email protected]] On Behalf Of
> Christopher Morrow
> Sent: Tuesday, March 08, 2011 7:40 PM
> To: Yann Berthier
> Cc: sidr wg list
> Subject: Re: [sidr] rpki-rtr standard port
>
> On Tue, Mar 8, 2011 at 8:44 PM, Yann Berthier <[email protected]>
> wrote:
> >
> > On 2011-03-08, at 4:26 PM, Christopher Morrow wrote:
> >
> >>> so, i suggest asking the iana for a port number, one and only one.
> >>> objections?
> >>
> >> 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
> >
> > A dedicated port for rpki seems a good idea
>
> don't disagree, just seeking some justification for the change. I came
> up with:
>   o diff hosts need ssh vs rpki-rtr (potentially off-net things?)
>   o ability to drop shields in case of problems but still maintain
> management access
I think this is related to your "drop shields" statement but may be different 
enough to capture.

Standard ssh port (22) for any router or router support system should only be 
available from your trusted NOC ips.
So a "new" port should be used for rpki that has different filtering acls or no 
filtering acls.

In a perfect world NOBODY would use 22 for ssh that would slow down the brute 
force attacks by 64k times and make the scanners noisier.



>   o qos/debugging reasons
>   o authentication requirements perhaps are different between user-ssh
> && rpki-rtr
>
> randy came up with: 'maybe we don't trust the ssh code to do this
> heavy lifting?' (or something similar)
>
> just hunting for the reason to be different.
>
> -chris
> _______________________________________________
> sidr mailing list
> [email protected]
> https://www.ietf.org/mailman/listinfo/sidr

This communication is the property of Qwest and may contain confidential or
privileged information. Unauthorized use of this communication is strictly
prohibited and may be unlawful.  If you have received this communication
in error, please immediately notify the sender by reply e-mail and destroy
all copies of the communication and any attachments.
_______________________________________________
sidr mailing list
[email protected]
https://www.ietf.org/mailman/listinfo/sidr

Reply via email to