Re: [MMUSIC] draft-gellens-mmusic-negotiating-human-language-00.txt - asymmetric preferences

[Bernard Aboba <[e-mail]>]

 

      This is very similar to the use case included of a user who
        can
        hear English but not speak; an audio and text stream are set up,
        both
        using English.  The point of negotiating language is to get the
        call to a callee who can communicate with the caller (e.g., a
        PSAP and
        call taker who understand at least one language in common with
        the
        caller).  The point is not to fully specify exactly how the
        media
        will be used; there is no need to do so and it won't help get
        the call
        to the right callee, but will make things much more complex.

      
      It is simpler and more robust to handle cases such as you
        describe and the one in the document now by negotiating the
        needed
        media as two-way streams.
    
    [BA]  I think this example points out the limitations of a call routing approach that relies solely on language. In this case, it is important for the "hint" to cause the call to be routed to an endpoint that can handle text media, since otherwise the caller will not be able to communicate.  Since both the audio and text media are set up using English in both directions, one might conclude that the "hint" need only express the language preference (English), but that would not be sufficient to get a satisfactory result.  What needs to be expressed in the "hint" is *both* a preference for English and a requirement for text media support.