Draft: draft-ietf-rtcweb-jsep

Commentary: This looks basically good . I see one missing reference and some places where I think the text might read better . Feel free to ignore my advice on the text , but you should probably fix the reference 
 PTAL 
 LGTM 
 Depends on resolution of FEC on mailing list 
 This will be dealt with in a future rev . 
 Justin , where are we here ? Should I unmark this discuss ? 
 Unmark as discuss since we need a proposal to discuss first ( which I have the action for ) 
 Action to write draft here listing FEC mechanisms that are MTI 
 Draft completed ; now we just need  to refer to uberti - rtcweb - fec .
Paragraph (version A):
RFC5576 MUST be implemented to signal RTP SSRC values.
Paragraph (version B):
RFC5576 MUST be implemented to signal RTP SSRC values and grouping
semantics.
Paragraph (version B):
RFC4588 MUST be implemented to signal RTX payload type
associations.
Paragraph (version A):
For each supported codec, "a=rtpmap" and "a=fmtp" lines, as
specified in RFC4566, Section 6.  The REQUIRED audio and video
codecs to support are specified in I-D.ietf-rtcweb-audio (see
Section 3) and I-D.ietf-rtcweb-video (see Section 5).
Paragraph (version B):
For each supported codec, "a=rtpmap" and "a=fmtp" lines, as
specified in RFC4566, Section 6.  The audio and video codecs that
MUST be supported are specified in I-D.ietf-rtcweb-audio (see
Section 3) and I-D.ietf-rtcweb-video (see Section 5).
Paragraph (version A):
For each supported FEC mechanism, a corresponding "a=rtpmap" line
indicating the desired FEC codec.
Paragraph (version A):
If FEC is supported for this media type, another "a=ssrc" line
with the FEC SSRC, and an "a=ssrc-group" line, as specified in
RFC5576, section 4.2, with semantics set to "FEC" and including
the primary and FEC SSRCs.
Paragraph (version B):
If FEC is supported for this media type, another "a=ssrc" line
with the FEC SSRC, and an "a=ssrc-group" line with semantics set
to "FEC-FR" and including the primary and FEC SSRCs, as specified
in RFC5956, section 4.3.  For simplicity, if both RTX and FEC are
supported, the FEC SSRC MUST be the same as the RTX SSRC.
Paragraph (version A):
For each supported codec that is present in the offer, "a=rtpmap"
and "a=fmtp" lines, as specified in RFC4566, Section 6, and
RFC3264, Section 6.1.  The REQUIRED audio and video codecs to
support are specified in I-D.ietf-rtcweb-audio (see Section 3) and
I-D.ietf-rtcweb-video (see Section 5).  Note that for simplicity,
the answerer MAY use different payload types for codecs than the
offerer, as it is not prohibited by Section 6.1.
Paragraph (version B):
For each supported codec that is present in the offer, "a=rtpmap"
and "a=fmtp" lines, as specified in RFC4566, Section 6, and
RFC3264, Section 6.1.  The audio and video codecs that MUST be
supported are specified in I-D.ietf-rtcweb-audio (see Section 3)
and I-D.ietf-rtcweb-video (see Section 5).  Note that for
simplicity, the answerer MAY use different payload types for
codecs than the offerer, as it is not prohibited by Section 6.1.
Paragraph (version A):
For each supported FEC mechanism that is present in the offer, a
corresponding "a=rtpmap" line indicating the desired FEC codec.
Paragraph (version A):
If a local MediaStreamTrack has been associated, and FEC has been
negotiated for this m= section, another "a=ssrc" line with the FEC
SSRC, and an "a=ssrc-group" line, as specified in RFC5576, section
SSRCs.
Paragraph (version B):
If a local MediaStreamTrack has been associated, and FEC has been
negotiated for this m= section, another "a=ssrc" line with the FEC
SSRC, and an "a=ssrc-group" line with semantics set to "FEC-FR"
and including the primary and FEC SSRCs, as specified in RFC5956,
section 4.3.  For simplicity, if both RTX and FEC are supported,
the FEC SSRC MUST be the same as the RTX SSRC.