SCTP guidelines for Diameter base protocol specified in section 2.1.1 of RFC 6733

634 views

I have a query on SCTP guidelines for Diameter base protocol specified in section 2.1.1 of RFC 6733 as :

"A Diameter agent SHOULD use dedicated payload protocol identifiers (PPIDs) for clear text and encrypted SCTP DATA chunks instead of only using the unspecified payload protocol identifier (value 0). For this purpose, two PPID values are allocated: the PPID value 46 is for Diameter messages in clear text SCTP DATA chunks, and the PPID value 47 is for Diameter messages in protected DTLS/SCTP DATA chunks."

RFC doesn't specify the behavior if the connected diameter peer doesn't use PPID as 46/47 for diameter message transport over SCTP or DTLS/SCTP. What if diameter messages are received with PPID set to value other than 46/47 or default 0 value? Should the messages be ignored or respond with error diameter message back to peer with same PPID set ? Please comment on this behavior.

posted Aug 23, 2013 by Mandeep Sehgal

Share this question

Facebook Share Button

Twitter Share Button

LinkedIn Share Button

1 Answer

I think the correct behavior would be to discard the data and close the connection, but since this is new in 6733, I haven't seen actual implementations doing this.
Though 3GPP specs insist on SCTP, most implementations on the field seem to be TCP based.

answer Aug 26, 2013 by Rathnakumar Kayyar

Similar Questions

+3 votes

Diameter : What is the difference between rfc 3588 and 6733 ?

Both the RFCs are referred for Diameter protocol. I want to know why two RFCs are defined for same Diameter protocol ? Difference between these two RFCs in term of contents ?

+3 votes

DIAMETER: Why does Device Watchdog Request/Answer messages used at application level, even SCTP is being used ?

When SCTP layer itself takes care of heartbeat ack-nack then why does diameter watchdog mechanism is required at the application layer ?

+2 votes

Issue facing while diameter with SCTP over public network

I want to run the diameter over public network with SCTP protocol.

I am facing issue as :-
PCRF public IP is 115.x.x.x
PCRF private IP is 172.x.x.x

SCTP INIT message from the PCEF is coming to my public IP & getting successfully NATTED & I am getting request on private IP.
PCRF sends SCTP INIT_ACK , but in the IPv4 field (inside INIT_ACK), it sends my private IP.
So, after receiving this message, PCEF sends COOKIE_ECHO message to my private IP ( because it is there in INIT_ACK message)

Because of this I don't receive the COOKIE_ECHO message & so the SCTP connection doesn't work. Anybody has faced this issue before & has any resolution? Also, is the diameter with SCTP is possible over public network?

+3 votes

Clarification on sending CER on Open connection with SCTP association restart

I have a query/doubt on below section of RFC 6733: 1.1.3

Changes from RFC 3588:

" Deprecated the exchange of CER/CEA messages in the open state.

This feature was implied in the peer state machine table of RFC 3588, but it was not clearly defined anywhere else in that document."

Scenario: In case a diameter node using SCTP association and does a restart procedure according to RFC 4960, section 5.2.4.1. Can the node (the one restarted the association) send CER on the association?

From the above RFC-6733 description it looks to me that the node which restart the association should not send CER, is my understanding correct? Please comment on this!

+1 vote

X2-AP: Benefits of having multiple streams of SCTP for the X2-AP protocol ?

How does X2-AP protocol leverage multi stream feature of SCTP protocol for its own functionality ?

...