draft-begen-avt-rtp-cnames
IETF DataTracker: draft-begen-avt-rtp-cnames
This draft was replaced by
draft-ietf-avt-rtp-cnames
-
Ali C. Begen, Colin Perkins, and Dan Wing,
Guidelines for Choosing RTP Control Protocol (RTCP) Canonical Names (CNAMEs)
(.txt|.pdf),
Internet Engineering Task Force,
May 2010,
Work in progress
(draft-begen-avt-rtp-cnames-02.txt).
-
Ali C. Begen and Colin Perkins,
Guidelines for Choosing RTP Control Protocol (RTCP) Canonical Names (CNAMEs)
(.txt|.pdf),
Internet Engineering Task Force,
May 2010,
Work in progress
(draft-begen-avt-rtp-cnames-01.txt).
-
Ali C. Begen and Colin Perkins,
Guidelines for Choosing an RTP Control Protocol (RTCP) Canonical Name (CNAME) for Hosts with Private IP Addresses
(.txt|.pdf),
Internet Engineering Task Force,
April 2010,
Work in progress
(draft-begen-avt-rtp-cnames-00.txt).
The RTP Control Protocol (RTCP) Canonical Name (CNAME) field is intended
to provide a stable endpoint identifier for participants in an RTP
session. The definition of the CNAME field in 3550 is known
to be problematic in the presence of NAT devices, and there are privacy
concerns around the use long-term persistent identifiers as RTCP CNAMES.
This draft proposes updates to 3550 to address both concerns.