Total Conversation is currently (=EN 3.2.1) only mentioned in a note to clause 6.5.1 about video. It needs to be more clearly required because it is required by the EAA. A new sub-clause in 6.5 or 6. would be appropriate.
We have the requirement 6.2.1.1 that RTT should be provided where there is voice. This automatically means that RTT must also be provided where there is voice and video. So, before we add a separate requirement that requires Total Conversation, we need to be able to identify a difference between Total Conversation communication sessions and communication sessions that simultaneously support voice, video and RTT.
This would require a definition for Total Conversation that would unambiguously clarify this distinction. If we cannot agree such a definition, then we can probably only handle the situation by adding a note to 6.2.1.1 that says that when voice, video, and RTT are all present this is referred to as Total Conversation.
We want Total Conversation to be as close to mainstream as possible. It is conversational communication allowing video, voice and RTT together. And that is already noted in 6.5.1.
I just realized that with so much talk about Total Conversation in the EAA, the EN readers would expect to find requirements with Total Conversation in the title. So I wanted to suggest some.
The EAA has a lot of very specific terminals and maybe services which we only will mention in some tables with relations between them and our clauses. Total Conversation might end up in these tables, but could also possibly need some requirements of its own in 6.5 or a new subclause of 6.
Let us keep the issue until we have a better grip of what is suitable.
I agree that we should leave the issue open as I agree that there should be some way in which people can see which requirements are applicable when Total Conversation is under consideration.