non-normative "must"

wish-wg · May 12, 2022 · aaf0e6b · aaf0e6b
1 parent 689b02f
commit aaf0e6b
Showing 1 changed file with 1 addition and 1 deletion.
diff --git a/draft-ietf-wish-whip.md b/draft-ietf-wish-whip.md
@@ -214,7 +214,7 @@ Given that in order to send new ICE candidates to the WHIP resource, the WHIP cl
 
 In order to reduce the complexity of implementing WHIP in both clients and media servers, some restrictions regarding WebRTC usage are made.
 
-SDP bundle SHALL be used by both the WHIP client and the media server. The SDP offer created by the WHIP client MUST include the bundle-only attribute in all m-lines as per {{!RFC8843}}. Also, RTCP muxing SHALL be supported by both the WHIP client and the media server.
+SDP bundle SHALL be used by both the WHIP client and the media server. The SDP offer created by the WHIP client must include the bundle-only attribute in all m-lines as per {{!RFC8843}}. Also, RTCP muxing SHALL be supported by both the WHIP client and the media server.
 
 Unlike {{!RFC5763}} a WHIP client MAY use a setup attribute value of setup:active in the SDP offer, in which case the WHIP endpoint MUST use a setup attribute value of setup:passive in the SDP answer.