From d9ea097a23b543b90e8d1a47b4f34c9d77649555 Mon Sep 17 00:00:00 2001 From: Christer Holmberg Date: Sun, 11 Aug 2019 12:20:38 +0300 Subject: [PATCH 1/2] Addressing remaining IESG comments by Benjamin K --- draft-ietf-mmusic-ice-sip-sdp-38.xml | 33 +++++++++++++++++++--------- 1 file changed, 23 insertions(+), 10 deletions(-) diff --git a/draft-ietf-mmusic-ice-sip-sdp-38.xml b/draft-ietf-mmusic-ice-sip-sdp-38.xml index 06bfdc6..c6777d0 100644 --- a/draft-ietf-mmusic-ice-sip-sdp-38.xml +++ b/draft-ietf-mmusic-ice-sip-sdp-38.xml @@ -202,15 +202,22 @@ SDP extension specifying otherwise is used. If an agent utilizes both RTP and RTCP, and separate ports are used for RTP and RTCP, the agent MUST include SDP candidate -attributes for both the RTP and RTCP components and SDP rtcp -attribute SHOULD be included in the "m=" section, as -described in - -In the cases where the port number for the RTCP is one higher than the -RTP port and the RTCP component address is the same as the address of the -RTP component, the SDP rtcp attribute MAY be omitted. +attributes for both the RTP and RTCP components. +The agent includes an SDP rtcp attribute following the procedures +in . Hence, in the cases where the RTCP +port value is one higher than the RTP port value and the RTCP component +address the same as the address of the RTP component, the SDP rtcp attribute +might be omitted. + + +NOTE: required that an agent always includes the +SDP rtcp attribute, even if the RTCP port value was one higher than the +RTP port value. This specification alligns the rtcp attribute procedures +with . + + If the agent does not utilize RTCP, it indicates that by including b=RS:0 and b=RR:0 SDP attributes, as described in . @@ -231,6 +238,12 @@ check Binding requests on those candidates.
+ An ICE agent is considered to indicate support of ICE by including + at least the SDP ice-pwd and ice-ufrag attributes in an offer or answer. + An ICE agent compliant will this specification also includes an + SDP ice-options attribute with an "ice2" attribute value. + + The agents will proceed with the ICE procedures defined in and this specification if, for each data stream in the SDP it received, the default destination for each component of that data stream appears in @@ -392,7 +405,7 @@ connectivity checks towards the peer candidates that were provided in the offer. -If the offer does not indicate support of ICE, the answerer +If the offer does not indicate support of ICE , the answerer MUST NOT accept the usage of ICE. If the answerer still accepts the offer, the answerer MUST NOT include any ICE-related SDP attributes in the answer. Instead the answerer will generate @@ -1103,7 +1116,7 @@ Its grammar is:
@@ -1119,7 +1132,7 @@ defined by the specification defining the extension ( required that an agent always includes the SDP rtcp attribute, even if the RTCP port value was one higher than the -RTP port value. This specification alligns the rtcp attribute procedures +RTP port value. This specification aligns the rtcp attribute procedures with . @@ -240,7 +240,7 @@ check Binding requests on those candidates. An ICE agent is considered to indicate support of ICE by including at least the SDP ice-pwd and ice-ufrag attributes in an offer or answer. - An ICE agent compliant will this specification also includes an + An ICE agent compliant with this specification MUST also include an SDP ice-options attribute with an "ice2" attribute value.