Minutes for SLIM at IETF-94
minutes-94-slim-2

# SLIM Selection of Language for Internet Media WG
* MONDAY, November 2, 2015
* 17:10 - 19:10 Afternoon Session III
* Room 301
* Chairs: Bernard Aboba, Natasha Rooney
* WG Datatracker Web Page: http://datatracker.ietf.org/wg/slim/charter/

## Preliminaries (15 minutes)
* 5:10 PM – 5:25 PM
* Natasha Rooney
* [Slides](https://www.ietf.org/proceedings/94/slides/slides-94-slim-0.pdf)

Topics
* Welcome and Chair introductions
* Remote debugging and audio/video setup
* Note Well
* Blue Sheets
* Note Takers
* Agenda Bash (everyone agreed these were ok)

## Charter (10 minutes)
* 5:25 PM – 5:35 PM
* Bernard Aboba
* [Slides](https://www.ietf.org/proceedings/94/slides/slides-94-slim-0.pdf)

Discussion
* Discussion of the possibility of an AD sponsored draft on privacy
implications of personal information in SDP. It was noted that our drafts would
need security statements and that slim is not the proper venue to handle more
general SDP security issues.

## Use Cases (10 minutes)
* 5:35 PM – 5:45 PM:
* Gunnar Hellstrom
* [Slides](https://www.ietf.org/proceedings/94/slides/slides-94-slim-2.pdf)

Potential modes:
* For some deaf users to have video for sign language communication
* For other deaf users to have text for typed communication
* For adult deaf users to talk and get text back.
* For some deaf-blind users to talk and read enlarged text
* For other deaf-blind users to use sign language out and receive text
displayed as Braille * For other deaf-blind users to use typed text out and
receive text displayed as Braille back * For some persons with speech
disabilities, to hear speech, and type text * For other persons with speech
disabilities, to hear speech and get support from speech-to-speech services to
convert vague speech to clear speech. * lHaving the three media: real-timetext,
video and audio gives opportunities to use the media required for the moment. *
Sign languages are as many and different as there are spoken and written
languages

Discussion
* Brian: reluctant to get into the complex use cases that go beyond the simple
offer/answer mechanism we have in SDP/SIP * We can handle many of the simple
use cases, but we cannot necessarily handle the complex use cases Gunnar
describes. * Pete Resnick: American Sign Language and British Sign Language are
languages. Can you not express language preferences? * Brian: The problem is in
negotiating the combination of language and media. For example, the user
prefers to send and receive American Sign Language (ASL) but can also send and
receive real-time text in English. * This involves a preference between a
language (ASL) and media (Video) and another language and media (English and
real-time text).

## Proposed Work Items Section Introduction (5 minutes)
5:45 – 5:50 PM
Natasha Rooney
* [Documents Link](https://datatracker.ietf.org/wg/slim/documents/)

* We will go through the proposed working group items in this session.

## Negotiating Human Language in Real-Time Communications (20 minutes)
* https://tools.ietf.org/html/draft-gellens-slim-negotiating-human-language
* 5:50 – 6:10 PM
* Randall Gellens
* [Slides](https://www.ietf.org/proceedings/94/slides/slides-94-slim-3.pdf)

Presentation of Draft
* use cases problem statement
* flows
* proposal to use SDP stream attribute
* some history
* overview of the draft updates
* should accept as a WG Document and should be ready for LC soon.

## Multiple Language Content Type (20 minutes)
* https://tools.ietf.org/html/draft-tomkinson-slim-multilangcontent
* 6:10 – 6:30 PM
* Nik Tomkinson
* [Slides](https://www.ietf.org/proceedings/94/slides/slides-94-slim-5.pdf)
* [Wiki](http://trac.tools.ietf.org/wg/slim/trac/wiki)

Presentation of Draft

Problems we are addressing
* Sending mail to recipients with unknown preferred languages especially where
the poor results of machine transla&on is unacceptable. For example
announcement emails to customers, clients and sales prospects. *
Single-language email conversations stifling collaborative communication in a
team spanning multiple languages. Promote inclusivity in email.

Important points
* New Content-type: multipart/multilingual
* Multilingual preface for non-conforming email clients
* Email client selects the message part based on user’s preferred language and
translation type * Translated subjects for list views eg. Inbox * Op&onal
language independent message part to show when there is no preferred language
match

Status so far
* Near to completion but keen for more input
* FAQ at https://trac.tools.ietf.org/wg/slim/trac/wiki
* Discussion will be within SLIM working group on the slim@ietf.org list
* Trials of message format starting now, we just need volunteers. Please see
the SLIM list for details. * but there are some changes I have made to a new
version to be submi[ed today

Discussion
* Pete: don't make these plain text, make message/rfc(822?!)
* Missed Name: suggestions to connect with email providers, and reinforce
security suggestions * Sean Leonard: suggest message/global.

## Other Possible Work Items (10 minutes)
* 6:30 PM - 6:40 PM
* Bernard Aboba

Do we have other use cases we can handle?
* Brian said issue was between media, but we can negotiate within media
language options(?!) * Gunnar suggested routing out of scope also * Gunnar:
yes, but it does need to happen at some point * A description of what is doable
within offer / anser is in scope * Brian: we agree routing is out of scope, but
we haven't decided how to achieve some of these things * Brian: I think we do
need to do some work which we haven't listed so far * Gunnar: my use cases
needed direction of modality * Randall: that's in the draft now, that is the
reason for lang attribute * Brian: you can have preference on choices, but only
within one media * Pete: choice is to do them both, or not, and the sender
chooses which one to do

Decision
* take the use case discussion to the list.

## Work Methods and Group Management (15 minutes)
* 6:40 PM – 6:55 PM
* Natasha Rooney
* [Slides](https://www.ietf.org/proceedings/94/slides/slides-94-slim-4.pdf)

* Humm to adopt gellins-slim-neogotiating-human-language as a WG item
* Chairs: consensus to adopt
* Humm to adopt tomsjonsom-slim-multilangcontent as a WG item
* Chairs: consensus to adopt

## Wrap Up.