Affected SPC is a mandatory parameter in SUA SCON

Hello Folks,

On the one hand, according to SUA RFC, an IPSP MAY indicate local
congestion to an SUA peer with an SCON message. On the other hand,
Affected SPC is a mandatory parameter in SCON. Therefore, in case the
IPSP serves a hostname or IP address, and does not serve an SPC, the
IPSP has to use a dummy SPC, which shall be interpreted as an
indication that own nodal congestion is experienced in the IPSP
originating the SCON message.

To avoid use of dummy SPCs in SCONs, it would be good to change the
SUA RFC, and make the Affected SPC an optional parameter in SCON
exchanged by IPSPs.

I believe RC parameter is sufficient in SCON, and Affected SPC can be
made optional in that case. This is because DPC is not mandatory in
the RK definition of IPSPs.

Perhaps, the same could apply to M3UA, if  DPC was optional in the RK
definition.


Any opinions?

Thank you in advance

-- 
Ilie