Since IETF95 meeting, draft-ietf-taps-transports (addressing the first deliverable) is in the IESG evaluation state and after addressing reviews it is now scheduled for telechat. The UDP transport usage draft has been updated and there was discussions on merger of this to draft-fairhurst-taps-transports-usage draft or keeping this as a separate draft. There was at least no opposition on keeping it separate. In the IETF95 meeting, it was said that if they are separate they should be moved together.
The group is picking up on the third milestone. There has been discussion on the "northbound" information in IETF96 meeting, draft-grinnemo-taps-he discusses the happy-eye ball approach for transport protocol selection, recently a draft (draft-trammell-post-sockets) has been posted addressing the possibilities of post socket era, industry player like Apple - talking about the considerations transport protocol for real-world API, real-time applications are in the discussions too (draft-mcquistin-taps-low-latency-services). This give an indication that TAPS could nurse number of interesting ideas which can be very useful for transport protocol evolution and could be good input to the newly formed working group like QUIC.