Re: SIGTRAN Plugtest Day 5

Barry,

Brian F. G. Bidulock wrote:                                          (Fri, 20 Apr 2007 06:20:02)
> Barry,
> 
> > *******
> > Issue 3 - There is a contradiction between the M3UA spec and the other specs
> > regarding the port number.
> > *******
> > 
> > M3UA states that implementations MAY use a port number other than the IANA
> > port number, while the other xUA specs are silent on this matter.
> 
> Silence means that it is not forbidden, which is the same effect as MAY, so
> there is no inconsistency.

Gee, some are not so silent either:

RFC 3868: (SUA)

|7.2.  Port Number
|
|   IANA has registered SCTP Port Number 14001 for SUA.  It is
|   recommended that SGPs use this SCTP port number for listening for new
|   connections.  SGPs MAY also use statically configured SCTP port
|   numbers instead.

RFC 4165 (M2PA)

|4.1.2.  MTP and SCTP Entities
|
|   This section describes how M2PA relates MTP and SCTP entities.
|
|   Each MTP link corresponds to an SCTP association.  To prevent
|   duplicate associations from being established, it is RECOMMENDED that
|   each endpoint know the IP address (or IP addresses, if multi-homing
|   is used) and port number of both endpoints.  SCTP prevents two
|   associations with the same IP addresses and port numbers from being
|   established.
|
|   It is necessary for at least one of the endpoints to be listening on
|   the port on which the other endpoint is trying to establish the
|   association.  Therefore, at least one of the port numbers SHOULD be
|   the M2PA registered port.

   If only one association is to be established between these two IP
   addresses, then the association SHOULD be established using the M2PA
   registered port at each endpoint.

   If it is desirable to create multiple associations (for multiple
   links) between the two IP addresses, different port numbers can be
   used for each association.  Nevertheless, the M2PA registered port
   number SHOULD be used at one end of each association.

--brian

-- 
Brian F. G. Bidulock
[email protected]
http://www.openss7.org/