It looks like the OS X header files know about SCTP, but the libraries don't actually implement it. You can hack it with third-party extensions.
I get the same thing on OS X 10.8.3. When installing socat, it discovers SCTP support in configure and sets this WITH_SCTP definition.
$ ./configure | grep -i sctp
configure: WARNING: include file netpacket / packet.h not found, disabling interface
checking whether to include SCTP support ... yes
checking for IPPROTO_SCTP ... yes
However, if you look at configure , this is a really simple test. "Enable SCTP support" is to specify the --enable-sctp option and is enabled by default. And the "check for IPPROTO_SCTP" simply determines if a protocol constant is defined in the header files. That is, headers may know this protocol and be relevant to its presentation, but the underlying system may not actually implement the use. I think this is the case: the OS X kernel does not provide an SCTP implementation.
There is "preliminary" third-party SCTP support in new versions of OS X: https://nplab.fh-muenster.de/groups/wiki/wiki/f366c/ . Installing this received SCTP works for me at homebrew socat .
[@ in ~]
$ socat -d -d sctp-listen: 99999 -
2013/04/24 22:19:38 socat [270] E socket (2, 1, 132): Protocol not supported
2013/04/24 22:19:38 socat [270] N exit (1)
[✘ @ in ~]
$ sudo kextload /System/Library/Extensions/SCTP.kext
[✘ @ in ~]
$ socat -d -d -d sctp-listen: 99999 -
[... snip ...]
2013/04/24 22:20:51 socat [291] I socket (2, 1, 132) -> 3
2013/04/24 22:20:51 socat [291] I starting accept loop
2013/04/24 22:20:51 socat [291] N listening on LEN = 16 AF = 2 0.0.0.0{4463
Caution : this is a third-party kernel extension, it is "preliminary", there is not much documentation, and I can not vouch for the source. This is likely to be fragile, and it can be difficult to repair errors. I would do it in a virtual machine, not on your main machine. Virtual machines are great for experimenting with low-level materials and various machine configurations. (Example: to find out this question, I did a bunch of messing around with my machine and some dubious things like root, and then, I returned my virtual machine to a snapshot, and as if that hadn't happened.)
Another option is to look at SCTP "userland" support (not the kernel) in libusrsctp , available in Homebrew. This will not cause socat to work with SCTP, but may support your other programming hobby.