RE: SCTP-over-UDP and port 9899

["Dan Wing" <[e-mail]>]

> > For the server, yes, that's okay.  That is what IANA-registered
> > default ports are all about.
> But the SCTP stack is neither a client nor a server...

"Bullpucky".  Next you're going to say that "peer to peer" 
doesn't have a client and a server.

> >> That is why I used a MAY. But I'm open to use any other formulation.
> >> Do you have a suggestion?
> >
> > Yes -- be silent about the source port.  Say nothing in the
> > document about the source port.
> I just talk about the local UDP encapsulation port...
> However, it is the destination port of incoming packets and
> the source port of outgoing packets (as every local port
> number is).
> 
> Would it be acceptable for you if I replace
> 
> Each SCTP stack uses a single local UDP encapsulation port number
> as the source port for all of its outgoing SCTP packets
> and as the destination port for all its incoming SCTP packets.
> 
> by
> 
> Each SCTP stack uses a single local UDP encapsulation port number.
> 
> However, later on I'm saying that the local UDP port is used
> as the source port for outgoing packets. I think I have to say
> that, since I need to say what the source and destination port
> of the inserted UDP are.

Do you understand why I am concerned with specifying the 
source UDP port number?  It gets re-written by NATs, and
the primary reason for this draft is to allow SCTP to work
when behind a NAT.

-d


> Best regards
> Michael
> >
> > -d
> >
> >
> >>
> >> Best regards
> >> Michael
> >>>
> >>> -d
> >>>
> >>>> Best regards
> >>>> Michael
> >>>>>
> >>>>> -d
> >>>>>
> >>>>>
> >>>>>> Best regards
> >>>>>> Michael
> >>>>>>>
> >>>>>>> -d
> >>>>>>>
> >>>>>>>
> >>>>>>>> Best regards
> >>>>>>>> Michael
> >>>>>>>>>
> >>>>>>>>> -d
> >>>>>>>>>
> >>>>>>>>>
> >>>>>>>>>
> >>>>>>>
> >>>>>>>
> >>>>>
> >>>>>
> >>>
> >>>
> >
> >