November 21st, 2002 Media Transcoding Design Team (a.k.a. team for the deaf) SIPPING WG

November 21st, 2002 Goals Invocation of services that involve media manipulation. –In particular, transcoding. Meet the requirements for the deaf. –But going beyond that Be OPES aware

November 21st, 2002 Deliveries so far Transcoding Services Invocation in SIP –draft-camarillo-sip-deaf-01.txt The source and sink attributes for SIP –draft-camarillo-mmusic-source-sink-00.txt Possible future deliveries Labeling of transcoded media streams Caller preferences extensions

November 21st, 2002 Open Issue in Framework Draft Invocation in the B2BUA model (as opposed to 3pcc model) Use Route header field as if the B2BUA was a proxy Use some kind of message encapsulation Use REFER –More signalling –Takes advantage of security work on REFER –OPES friendly Decision: Use REFER

November 21st, 2002 Open Issue in Plumbing Draft draft-camarillo-mmusic-source-sink-00.txt Is this needed at all? –For simple services it is not, as pointed out in the draft Which types of scenarios do we have in mind? –They are typically implementable without using source/sink –But media streams have to be replicated At the end point –special end points needed even for hearing users Network server –complex

November 21st, 2002 Conference Room Scenario Deaf person Hearing person Speech-to-Text audio text Deaf person Hearing person Speech-to-Text audio text

November 21st, 2002 Person with a Hearing Impairment Hearing Impaired Hearing person Speech-to-Text audio text Hearing person Speech-to-Text audio text Hearing Impaired