1 / 5

SCTP Sockets Draft

This draft outlines changes to SCTP socket operations, deprecating old functions and introducing new ones for improved use. It presents new association ID values and emphasizes the use of ancillary data for future-proofing methods.

tyanne
Télécharger la présentation

SCTP Sockets Draft

An Image/Link below is provided (as is) to download presentation Download Policy: Content on the Website is provided to you AS IS for your information and personal use and may not be sold / licensed / shared on other websites without getting consent from its author. Content is provided to you AS IS for your information and personal use only. Download presentation by click this link. While downloading, if for some reason you are not able to download a presentation, the publisher may have deleted the file from their server. During download, if you can't get a presentation, the file might be deleted by the publisher.

E N D

Presentation Transcript

  1. SCTP Sockets Draft Randall Stewart – Huawei Michael Tuexen - Muenster Univ.

  2. Changes since last revision • Various nits and other edits per reviews from mailing list and email comments (thank you). • Deprecation of: • sctp_sndrcv_info – replaced by separate send and receive structures. • SCTP_EVENTS – replaced by individual socket on/off options. • sctp_sendmsg() – replaced by sctp_sendv

  3. Changes since last revision • Deprecation of (continued): • sctp_recvmsg() – replaced by sctp_recvv • sctp_send() – replaced by sctp_sendv • sctp_sendx() – replaced by sctp_sendv • New association id values for SCTP_(FUTURE, ALL, CURRENT)_ASSOC and explicitly where they can be used.

  4. Changes since last revision • Specification that the ONLY future-proof method is to use ancillary data (which is awkward). • Addition of the sctp_sendv and sctp_recvv calls which can currently meet all send/recv.

  5. What should happen next? • Working group last call – and hopefully more review by y’all (we are finally ready after 10 years ;-D)

More Related