Lines Matching refs:MUST

138    The key words "MUST", "MUST NOT", "REQUIRED", "SHALL", "SHALL NOT",
149    Implementations that fail to satisfy one or more "MUST" requirements
151    "MUST" requirements, but fail to satisfy one or more "SHOULD"
164    payload MUST contain just one of them at a time.
246    first Vorbis packet in the RTP payload.  The clock frequency MUST be
301    payloads.  Each packet MUST contain only a single type of Vorbis
313    The packets with a VDT of value 3 MUST be ignored.
318    packets MUST be set to 0.
365    The payload packing of the Vorbis data packets MUST follow the
368    packets, if any, MUST follow in temporal order.
471    MUST be conveyed via the signalling channel used to set up the
475    the RTP channel.  Implementations MUST support an in-band delivery of
488    MUST have in advance the correct configuration.  If the client
490    information, it MUST NOT decode the raw associated Vorbis data until
496    the packet type bits set to match the Vorbis Data Type.  Clients MUST
498    of [RFC4588] the configuration headers.  The RTP timestamp value MUST
516    MUST be packed as they are, while the Comment header MAY be replaced
625    The following packet definition MUST be used when Configuration is
777    payload header.  The consecutive fragments MUST be sent without any
782    fragmented packets MUST be the same as the first packet sent, with
938    client MUST discard all the remaining Vorbis fragments and decode the
940    above and the first RTP payload is lost, the client MUST detect that
942    Fragment type 2 and MUST drop it.  The next RTP payload, which is the
943    final fragmented packet, MUST be dropped in the same manner.  If the
1111    implementation MUST ignore unknown parameters.
1137    o  The mandated parameters "configuration" MUST be included in the
1148    The timestamp clock rate MUST be a multiple of the sample rate; a
1149    different payload number MUST be used if the clock rate changes.  The