Original text:
If all of the leaf nodes fail to connect during racing, i.e. none of the configurations that satisfy all requirements given in the Transport Properties actually work over the available paths, then the <del> transport system should report an InitiateError to the application. An InitiateError event should also be generated in case the transport system finds no usable candidates to race. </del>  4.5. Data Unit: Byte-stream <del> the Transport Services API mappings for MPTCP are identical to TCP. </del>  MPTCP adds support for multipath properties, such as "multipath" and "multipathPolicy". UDP Connections can only generate errors on initiation due to port conflicts on the local system. <del> Once in use, UDP throws "soft errors" (ERROR.UDP(-Lite)) upon receiving ICMP notifications indicating failures in the network. Additional information can also be provided when this is available to the system (e.g.  ICMP error code and quoted packet header). </del>  LISTEN.UDP.  Calling "Listen" for UDP binds a local port and prepares it to receive inbound UDP datagrams from peers. the local port reservation. Calling "Abort" on a UDP Connection (ABORT.UDP(-Lite)) is <del> identical to calling "Close". </del>  Calling "CloseGroup" on a UDP Connection (ABORT.UDP(-Lite)) is identical to calling "Close" on this Connection and on all Endpoint must be configured with a group IP address and a port. Calling "Initiate" on a UDP Multicast Receive Connection causes an <del> immediate InitiateError.  This is an unsupported operation. </del>  Calling "InitiateWithSend" on a UDP Multicast Receive Connection <del> causes an immediate InitiateError.  This is an unsupported </del>  operation. A UDP Multicast Receive Connection is ready once the system has received traffic for the appropriate group and port. <del> UDP Multicast Receive Connections generate an InitiateError indicating that joining a multicast group failed if Initiate is </del>  called.  LISTEN.UDP.  Calling "Listen" for UDP Multicast Receive binds a local port, prepares it to receive inbound UDP datagrams from peers, and issues a multicast host join.  If a Remote Endpoint stream id assignment procedure described above.  If there are not enough streams available, ADD_STREAM.SCTP must be called. <del> When this value is changed, or a Message with Message Property "msgPriority" is sent, and there are multiple Connection objects assigned to the same SCTP association, CONFIGURE_STREAM_SCHEDULER.SCTP is called to adjust the priorities of streams in the SCTP association. </del> SEND.SCTP.  Message Properties such as "msgLifetime" and "msgOrdered" map to parameters of this primitive. AbortGroup: Calling "AbortGroup" calls ABORT.SCTP, immediately closing all Connections in the SCTP association.  11. RFC-EDITOR: Please remove this section before publication.

Reviewer comments:
This PR covers steps 1 and 2 in . When aligning the error events for UDP multicast I also noticed that the text for UDP was not correct as soft errors do not generate ConnectionError events so also attempted to fix this.
NAME what's the reason for having Abort cause an error, rather than just moving to closed?
NAME This comes from the API draft, which says:
Great, thank you!

Revised text:
If all of the leaf nodes fail to connect during racing, i.e. none of the configurations that satisfy all requirements given in the Transport Properties actually work over the available paths, then the  <ins> transport system should report an EstablishmentError to the application.  An EstablishmentError event should also be generated in case the transport system finds no usable candidates to race. </ins> 4.5. Data Unit: Byte-stream  <ins> The Transport Services API mappings for MPTCP are identical to TCP. </ins> MPTCP adds support for multipath properties, such as "multipath" and "multipathPolicy". UDP Connections can only generate errors on initiation due to port conflicts on the local system.  <ins> UDP Connections can only generate connection errors in response to "Abort" calls.  (Once in use, UDP Connections can also generate "SoftError" Events (ERROR.UDP(-Lite)) upon receiving ICMP notifications indicating failures in the network.) </ins> LISTEN.UDP.  Calling "Listen" for UDP binds a local port and prepares it to receive inbound UDP datagrams from peers. the local port reservation. Calling "Abort" on a UDP Connection (ABORT.UDP(-Lite)) is  <ins> identical to calling "Close", except that the Connection will send a ConnectionError Event rather than a Closed Event. </ins> Calling "CloseGroup" on a UDP Connection (ABORT.UDP(-Lite)) is identical to calling "Close" on this Connection and on all Endpoint must be configured with a group IP address and a port. Calling "Initiate" on a UDP Multicast Receive Connection causes an  <ins> immediate EstablishmentError.  This is an unsupported operation. </ins> Calling "InitiateWithSend" on a UDP Multicast Receive Connection  <ins> causes an immediate EstablishmentError.  This is an unsupported </ins> operation. A UDP Multicast Receive Connection is ready once the system has received traffic for the appropriate group and port.  <ins> UDP Multicast Receive Connections generate an EstablishmentError indicating that joining a multicast group failed if "Initiate" is </ins> called. <ins> The only ConnectionError generated by a UDP Multicast Receive Connection is in response to an "Abort" call. </ins> LISTEN.UDP.  Calling "Listen" for UDP Multicast Receive binds a local port, prepares it to receive inbound UDP datagrams from peers, and issues a multicast host join.  If a Remote Endpoint stream id assignment procedure described above.  If there are not enough streams available, ADD_STREAM.SCTP must be called.  SEND.SCTP.  Message Properties such as "msgLifetime" and "msgOrdered" map to parameters of this primitive. AbortGroup: Calling "AbortGroup" calls ABORT.SCTP, immediately closing all Connections in the SCTP association. <ins> In addition to the API mappings described above, when there are multiple Connection objects assigned to the same SCTP association, SCTP can support Connection properties such as "connPriority"and "connScheduler" where CONFIGURE_STREAM_SCHEDULER.SCTP can be called to adjust the priorities of streams in the SCTP association. </ins> 11. RFC-EDITOR: Please remove this section before publication.