laforge has submitted this change. ( https://gerrit.osmocom.org/c/osmo-gsm-manuals/+/41087?usp=email )
Change subject: sigtran.adoc: small fixes and improvements ......................................................................
sigtran.adoc: small fixes and improvements
Change-Id: Ia8457f3fef3c7e455b102b4685850be5fbf6f186 --- M common/chapters/sigtran.adoc 1 file changed, 3 insertions(+), 2 deletions(-)
Approvals: Jenkins Builder: Verified fixeria: Looks good to me, but someone else must approve laforge: Looks good to me, approved
diff --git a/common/chapters/sigtran.adoc b/common/chapters/sigtran.adoc index 75767e3..308f157 100644 --- a/common/chapters/sigtran.adoc +++ b/common/chapters/sigtran.adoc @@ -419,7 +419,7 @@ transmitting user data to us.
In order to be able to use this feature, the SCTP association peer must support -the ASCONF extension. The extension support is negotiation during the INIT +the ASCONF extension. The extension support is negotiated during the INIT handshake of the association. Furthermore, for ASCONF features to work properly, the assoc also needs to announce/use the AUTH extension, as per RFC5061 section 4.2.7. Otherwise, the peer receiving an SCTP INIT with @@ -430,7 +430,8 @@ As of the time of writing this documentation (linux 6.4.12) and since basically ever, those extensions are runtime-disabled by default. They can be enabled per socket using the kernel sockopts SCTP_ASCONF_SUPPORTED and SCTP_AUTH_SUPPORTED, -and that's what the Osmocom stack is currently doing for all SCTP sockets. +and that's what the Osmocom stack is currently doing for all its SCTP sockets. + However, those sockopts are farily new (linux v5.4), which means user running older kernels will see in the logs setting those sockopts fail, but connection will keep ongoing, simply without those features available (so setting `primary`