rfc8859v3.txt   rfc8859.txt 
skipping to change at line 397 skipping to change at line 397
b=AS:256 b=AS:256
4.5. Category: TRANSPORT 4.5. Category: TRANSPORT
The attributes in the TRANSPORT category can be set normally for The attributes in the TRANSPORT category can be set normally for
multiple items in a multiplexed group, but the software MUST pick the multiple items in a multiplexed group, but the software MUST pick the
one that's associated with the "m=" line whose information is used one that's associated with the "m=" line whose information is used
for setting up the underlying transport. for setting up the underlying transport.
In the example below, the "a=crypto" attribute is defined for both In the example below, the "a=crypto" attribute is defined for both
the audio and video "m=" lines. The video media line's a=crypto the audio and video "m=" lines. The video media line's "a=crypto"
attribute is chosen since its mid value (bar) appears first in the attribute is chosen since its MID value (bar) appears first in the
a=group:BUNDLE line. This is due to the BUNDLE grouping semantic "a=group:BUNDLE" line. This is due to the BUNDLE grouping semantic
[RFC8843], which mandates that the values from the "m=" line [RFC8843], which mandates that the values from the "m=" line
corresponding to the mid appearing first on the a=group:BUNDLE line corresponding to the mid appearing first on the "a=group:BUNDLE" line
be considered for setting up the RTP transport. be considered for setting up the RTP transport.
v=0 v=0
o=alice 2890844526 2890844527 IN IP4 host.atlanta.example.com o=alice 2890844526 2890844527 IN IP4 host.atlanta.example.com
s= s=
c=IN IP4 host.atlanta.example.com c=IN IP4 host.atlanta.example.com
t=0 0 t=0 0
a=group:BUNDLE bar foo a=group:BUNDLE bar foo
m=audio 49172 RTP/AVP 99 m=audio 49172 RTP/AVP 99
a=mid:foo a=mid:foo
skipping to change at line 2664 skipping to change at line 2664
+------+-----------------------------------+-------+--------------+ +------+-----------------------------------+-------+--------------+
Table 76: RFC 4566 Attribute Analysis Table 76: RFC 4566 Attribute Analysis
12. content Attribute Analysis 12. content Attribute Analysis
12.1. RFC 4796 12.1. RFC 4796
[RFC4796] defines a new SDP media-level attribute, "content". The [RFC4796] defines a new SDP media-level attribute, "content". The
"content" attribute defines the content of the media stream to a more "content" attribute defines the content of the media stream to a more
detailed level than the media-description line. The sender of an SDP detailed level than the media description line. The sender of an SDP
session description can attach the "content" attribute to one or more session description can attach the "content" attribute to one or more
media streams. The receiving application can then treat each media media streams. The receiving application can then treat each media
stream differently (e.g., show it on a big or small screen) based on stream differently (e.g., show it on a big or small screen) based on
its content. its content.
+-----------------+--------------+-------+--------------+ +-----------------+--------------+-------+--------------+
| Name | Notes | Level | Mux Category | | Name | Notes | Level | Mux Category |
+=================+==============+=======+==============+ +=================+==============+=======+==============+
| content:slides | Not impacted | M | NORMAL | | content:slides | Not impacted | M | NORMAL |
+-----------------+--------------+-------+--------------+ +-----------------+--------------+-------+--------------+
skipping to change at line 2828 skipping to change at line 2828
Although it is possible to analyze the various potential Although it is possible to analyze the various potential
configurations in multiplexed media descriptions to find combinations configurations in multiplexed media descriptions to find combinations
that satisfy such constraints, it can quickly become complicated to that satisfy such constraints, it can quickly become complicated to
do so. do so.
The procedures defined in [RFC5939] state that each potential The procedures defined in [RFC5939] state that each potential
configuration in the SDP has a unique configuration number; however, configuration in the SDP has a unique configuration number; however,
the scope of uniqueness is limited to each media description. To the scope of uniqueness is limited to each media description. To
make it simple for the answerer to chose valid combinations of make it simple for the answerer to chose valid combinations of
potential configurations across media descriptions in a given bundle potential configurations across media descriptions in a given BUNDLE
group, we provide a simple rule for constructing potential group, we provide a simple rule for constructing potential
configurations: configurations:
* Let m-bundle be the set of media descriptions that form a given * Let m-bundle be the set of media descriptions that form a given
bundle. bundle.
* Let m-bundle-pcfg be the set of media descriptions in m-bundle * Let m-bundle-pcfg be the set of media descriptions in m-bundle
that include one or more potential configurations. that include one or more potential configurations.
* Each media description in m-bundle-pcfg MUST have at least one * Each media description in m-bundle-pcfg MUST have at least one
 End of changes. 4 change blocks. 
6 lines changed or deleted 6 lines changed or added

This html diff was produced by rfcdiff 1.45. The latest version is available from http://tools.ietf.org/tools/rfcdiff/