Draft: draft-ietf-taps-impl

Commentary: 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 . 
 what 's the reason for having  cause an error , rather than just moving to closed ? 
 This comes from the API draft , which says : 
 Great , thank you !
Paragraph (version A):
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
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.
Paragraph (version B):
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
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.
Paragraph (version A):
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).
Paragraph (version A):
Calling "Abort" on a UDP Connection (ABORT.UDP(-Lite)) is
identical to calling "Close".
Paragraph (version B):
Calling "Abort" on a UDP Connection (ABORT.UDP(-Lite)) is
identical to calling "Close", except that the Connection will send
a ConnectionError Event rather than a Closed Event.
Paragraph (version A):
Calling "Initiate" on a UDP Multicast Receive Connection causes an
immediate InitiateError.  This is an unsupported operation.
Paragraph (version A):
Calling "InitiateWithSend" on a UDP Multicast Receive Connection
causes an immediate InitiateError.  This is an unsupported
operation.
Paragraph (version A):
UDP Multicast Receive Connections generate an InitiateError
indicating that joining a multicast group failed if Initiate is
called.
Paragraph (version B):
Calling "Initiate" on a UDP Multicast Receive Connection causes an
immediate EstablishmentError.  This is an unsupported operation.
Paragraph (version B):
Calling "InitiateWithSend" on a UDP Multicast Receive Connection
causes an immediate EstablishmentError.  This is an unsupported
operation.
Paragraph (version B):
UDP Multicast Receive Connections generate an EstablishmentError
indicating that joining a multicast group failed if "Initiate" is
called.
Paragraph (version B):
The only ConnectionError generated by a UDP Multicast Receive
Connection is in response to an "Abort" call.
Paragraph (version A):
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.
Paragraph (version B):
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.