Re: [MMUSIC] Modifying an approved document: MSID

Den 19. jan. 2017 13:31, skrev Harald Alvestrand:
> Ted pointed out to me that I sent this to the wrong group.
> 
> Chairs and members, please advise.

My proposed change is here:

https://github.com/alvestrand/rtcweb-msid/pull/16

The filed issue is here:

https://github.com/alvestrand/rtcweb-msid/issues/15

(CCing RTCWEB - please keep discussion, if any, on mmusic)

> 
> 
> 
> -------- Forwarded Message --------
> Subject: 	[rtcweb] Modifying an approved document: MSID
> Date: 	Wed, 18 Jan 2017 23:22:14 +0100
> From: 	Harald Alvestrand <harald@alvestrand.no>
> To: 	rtcweb@ietf.org <rtcweb@ietf.org>
> 
> 
> 
> When reviewing the implications of the PeerConnection API change to
> support AddTrack rather than AddStream, I found an issue.
> 
> This issue concerns draft-ietf-rtcweb-msid, which is currently in
> REF-WAIT state (I believe).
> 
> The issue is that it is possible to add a track without specifying a
> stream. Since the track's ID needs to be carried, we have to send an
> "a=msid" line, but the track's ID is the *second* field on that line,
> with the first being the stream's ID.
> 
> This creates a problem.
> 
> Suggested fix: Insert two lines in the document:
> 
> 1) On SDP generation:
> 
> "If there is no stream associated with the track, use the reserved ID
> value '-'"
> 
> 2) On SDP parsing
> 
> "If the stream ID is the reserved value '-', the track is not associated
> with a stream, and no stream is signalled or created."
> 
> If this is OK with the community, I'll issue an updated draft with this
> change.
> 
> 
> -- 
> Surveillance is pervasive. Go Dark.
> 
> _______________________________________________
> rtcweb mailing list
> rtcweb@ietf.org
> https://www.ietf.org/mailman/listinfo/rtcweb
> 
> 
> 
> _______________________________________________
> mmusic mailing list
> mmusic@ietf.org
> https://www.ietf.org/mailman/listinfo/mmusic
> 