Lines Matching refs:CNAME

99             6.5.1  CNAME: Canonical End-Point Identifier SDES Item .  46
1083       source called the canonical name or CNAME, Section 6.5.1.  Since
1085       program is restarted, receivers require the CNAME to keep track of
1086       each participant.  Receivers may also require the CNAME to
1149    SDES: Source description items, including CNAME
1188    o  New receivers need to receive the CNAME for a source as soon as
1191       include the SDES CNAME except when the compound RTCP packet is
1220    SDES:  An SDES packet containing a CNAME item MUST be included
1274    R[SR #sendinfo #site1#site2][SDES #CNAME PHONE #CNAME LOC][BYE##why]
1363    CNAME for the sending sites.  When the proportion of senders is
1528    a CNAME for that SSRC has been received.  Entries MAY be deleted from
1882    addition to the mandatory CNAME item, such as NAME (personal name)
1887    reports and CNAME are sent, thus impairing the performance of the
1897    For example, an application may be designed to send only CNAME, NAME
1902    SDES packet with the CNAME item would be sent.  For a small session
1918    binding through a common CNAME for each participant, for example in a
1921    other sessions would carry only the CNAME item.  In particular, this
2552    Only the CNAME item is mandatory.  Some items shown here may be
2559 6.5.1 CNAME: Canonical End-Point Identifier SDES Item
2564    |    CNAME=1    |     length    | user and domain name        ...
2567    The CNAME identifier has the following properties:
2570       conflict is discovered or if a program is restarted, the CNAME
2583    o  Like the SSRC identifier, the CNAME identifier SHOULD also be
2587       participant in a set of related RTP sessions, the CNAME SHOULD be
2590    o  To facilitate third-party monitoring, the CNAME SHOULD be suitable
2593    Therefore, the CNAME SHOULD be derived algorithmically and not
2596    alternate syntax or semantics.  The CNAME item SHOULD have the format
2629    to specify additional syntax for the CNAME identifier.
2639    If each application creates its CNAME independently, the resulting
2643    necessary for the CNAME of each tool to be externally configured with
2653    applications MAY provide a means to configure a unique CNAME, but the
2670    sent most frequently of those items other than CNAME.  Profiles MAY
2766    down the rate at which reception reports and CNAME are sent, thus
2772    the rate at which other non-CNAME items such as NAME are transmitted
3145       for example, decide to filter non-CNAME SDES information if
3148       generates its own RR packets MUST send SDES CNAME information
3181       for example, decide to filter non-CNAME SDES information if
3185       generated by an end system.)  A mixer MUST send SDES CNAME
3484                   containing a CNAME item that differs from the CNAME
3501                   containing a CNAME item or CNAME is the
3659    packets begin with an SR or RR packet.  The SDES CNAME item is
3666    [random][RR][SDES #CNAME ...]  [SR #senderinfo #site1 #site2]
3905    CNAME    canonical name                      1
4006       6.3.9); an alternate syntax or semantics for the CNAME item
4059    CNAME and NAME information may be used to impersonate another
5507          CNAME in Section 6.5.1, and "example.com" was used in place of
5522          particular, SDES CNAME is carried in only one part when the