Re: [Isms] IsmsSNMP SSH ports

["David Harrington" <ietfdbh at comcast.net>]

dbh 

> -----Original Message-----
> From: Joseph Salowey (jsalowey) [mailto:jsalowey at cisco.com] 
> Sent: Wednesday, January 21, 2009 3:35 PM
> To: Wes Hardaker; David Harrington
> Cc: isms at ietf.org
> Subject: RE: [Isms] IsmsSNMP SSH ports
> 
> Why do we need port numbers in the range 1..1023?  The is 
> bound to cause
> a DISCUSS from the IESG. 
> 
> > -----Original Message-----
> > From: isms-bounces at ietf.org [mailto:isms-bounces at ietf.org] On 
> > Behalf Of Wes Hardaker
> > Sent: Wednesday, January 21, 2009 11:50 AM
> > To: David Harrington
> > Cc: isms at ietf.org
> > Subject: Re: [Isms] IsmsSNMP SSH ports
> > 
> > >>>>> On Wed, 21 Jan 2009 12:14:02 -0500, "David Harrington" 
> > <ietfdbh at comcast.net> said:
> > 
> > DH> I think I should eliminate the sentence in section 8. 
> > PLease correct 
> > DH> me if I'm wrong.
> > 
> > Well, we can either do one well known port with two different 
> > service names or two well known ports each with the same 
> service name.
> > 
> > Anything with embedded ssh, though, wouldn't want to do two 
> > different service names if they had both a NR and a CR on the 
> > same box that wasn't the same process.
> > 
> > There has to be some way, however, of distinguishing whether 
> > you're trying to get to a NR or CR entity.  Yes, you could do 
> > it via the SNMPv3 pdu handler registration process but in 
> > reality most software isn't architected that way.
> > --
> > Wes Hardaker
> > Sparta, Inc.
> > _______________________________________________
> > Isms mailing list
> > Isms at ietf.org
> > https://www.ietf.org/mailman/listinfo/isms
> > 
> 

_______________________________________________
Isms mailing list
Isms at ietf.org
https://www.ietf.org/mailman/listinfo/isms