iana/www.rfc-editor.org/rfc/rfc4695.txt:                 C.2.2.1. The anchor Sending Policy .................104
iana/www.rfc-editor.org/rfc/rfc4695.txt:   loop", "open-loop", and "anchor".
iana/www.rfc-editor.org/rfc/rfc4695.txt:        ch_never, and ch_anchor parameters configure the semantics of
iana/www.rfc-editor.org/rfc/rfc4695.txt:          ch_anchor:    See Appendix C.2.3 for usage details.
iana/www.rfc-editor.org/rfc/rfc4695.txt:         "anchor":  Defined in Appendix C.2.2 of this memo.
iana/www.rfc-editor.org/rfc/rfc4695.txt:          ch_anchor:    See Appendix C.2.3 for usage details.
iana/www.rfc-editor.org/rfc/rfc4695.txt:         "anchor":  Defined in Appendix C.2.2 of this memo.
iana/www.rfc-editor.org/rfc/rfc4695.txt:   ch_never, and ch_anchor parameters modify these definitions, as
iana/www.rfc-editor.org/rfc/rfc4695.txt:     o  Appendix C.2 describes the journalling system (ch_anchor,
iana/www.rfc-editor.org/rfc/rfc4695.txt:   normatively define three sending policies: anchor, closed-loop, and
iana/www.rfc-editor.org/rfc/rfc4695.txt:   We define three symbolic values for j_update: "anchor", to indicate
iana/www.rfc-editor.org/rfc/rfc4695.txt:   that the stream uses the anchor sending policy, "open-loop", to
iana/www.rfc-editor.org/rfc/rfc4695.txt:C.2.2.1.  The anchor Sending Policy
iana/www.rfc-editor.org/rfc/rfc4695.txt:   In the anchor policy, the sender uses the first packet in the stream
iana/www.rfc-editor.org/rfc/rfc4695.txt:   as the checkpoint packet for all packets in the stream.  The anchor
iana/www.rfc-editor.org/rfc/rfc4695.txt:   The anchor policy does not require the use of the RTP control
iana/www.rfc-editor.org/rfc/rfc4695.txt:   The main drawback of the anchor policy is bandwidth efficiency.
iana/www.rfc-editor.org/rfc/rfc4695.txt:   streams, the bandwidth overhead of the anchor policy is often
iana/www.rfc-editor.org/rfc/rfc4695.txt:   bandwidth of a stream, relative to the anchor policy.
iana/www.rfc-editor.org/rfc/rfc4695.txt:   policy, and that are also not able to use the anchor policy because
iana/www.rfc-editor.org/rfc/rfc4695.txt:   use the ch_anchor parameter (defined in Appendix C.2.3) to protect
iana/www.rfc-editor.org/rfc/rfc4695.txt:   all MIDI command types that are not shielded by ch_anchor and
iana/www.rfc-editor.org/rfc/rfc4695.txt:   implementations of the closed-loop (Appendix C.2.2.2) and anchor
iana/www.rfc-editor.org/rfc/rfc4695.txt:     o  ch_anchor.  A chapter assigned to the ch_anchor MUST obey a
iana/www.rfc-editor.org/rfc/rfc4695.txt:   controller number MUST be made to the ch_default or ch_anchor
iana/www.rfc-editor.org/rfc/rfc4695.txt:   ch_anchor=P; ch_anchor=C7.64;
iana/www.rfc-editor.org/rfc/rfc4695.txt:   ch_anchor=__7E_00-7F_09_01.02.03__;
iana/www.rfc-editor.org/rfc/rfc4695.txt:   ch_anchor=__7F_00-7F_04_01.02__
iana/www.rfc-editor.org/rfc/rfc4695.txt:   controller numbers are assigned to ch_anchor.  Note that the ordering
iana/www.rfc-editor.org/rfc/rfc4695.txt:   of the ch_anchor chapter C assignment after the ch_never command acts
iana/www.rfc-editor.org/rfc/rfc4695.txt:   cm_used assignment codes the exception, and the ch_anchor assignment
iana/www.rfc-editor.org/rfc/rfc4695.txt:   recovery journal with the closed-loop or the anchor sending policies.
iana/www.rfc-editor.org/rfc/rfc4695.txt:   and the closed-loop or anchor sending policies.  Servers SHOULD use
iana/www.rfc-editor.org/rfc/rfc4695.txt:   anchor sending policies.  These streams MUST use the stream
iana/www.rfc-editor.org/rfc/rfc4695.txt:   param-assign =/  ("j_update="   ("anchor" / "closed-loop" /
iana/www.rfc-editor.org/rfc/rfc4695.txt:   param-assign =/  ("ch_anchor="  (([channel-list] chapter-list