Skip to main content

Session initiation Protocol Best-practice Recommendations Against Network Dangers to privacY

The information below is for an older proposed charter
Document Proposed charter SIP Best-practice Recommendations Against Network Dangers to privacY WG (sipbrandy) Snapshot
Title Session initiation Protocol Best-practice Recommendations Against Network Dangers to privacY
Last updated 2016-05-15
State Draft Charter
WG State Proposed
IESG Responsible AD Murray Kucherawy
Charter edit AD Ben Campbell
Send notices to (None)


SIP with the SDP Offer/Answer model, along with RTP are widely used in
modern communications networks. But while secure RTP (SRTP) is available
to provide integrity and privacy protection to such communication, it is
rarely used end-to-end. This lack is due to several factors, notably the
pervasive use of signaling and media intermediaries in such networks and
the difficulties involved in deployment of strong identity mechanisms
for SIP. These factors are complicated by the fact that their are
several incompatible approaches to SRTP key exchange.

The current situation is unacceptable in the face of pervasive
monitoring, which RFC 7258 describes as "an attack on privacy". In
addition, the STIR working group is, at the time of this writing,
revising RFC 4744 to make strong identity attestations for SIP easier to
deploy. This gives the IETF an opportunity to define best practices to
improve privacy protections for users of SIP based communication, in
ways that improve upon the status-quo.


The SIPBRANDY working group will define best practices for establishing
two-party, SIP-signaled SRTP sessions with end-to-end security
associations, including a single, preferred SRTP key exchange mechanism.
These practices are expected to be deployable across typical SIP
networks, without the sharing of SRTP keying material with
intermediaries or third parties. These practices should protect against
man-in-the-middle attacks.

The working group will additionally coordinate with the MMUSIC working
group to define best practices to provide opportunistic security [RFC
7435] for SIP-signaled media sessions for situations where strong
protections are not necessary or not feasible.


The working group is not expected to define practices for multi-party
session topologies, especially those involving media distribution

The working group is not expected to define new protocols or modify
existing ones; rather it will define practices for using existing
protocols. If the working group discovers requirements to create or
modify protocols, it will forward those requirements to the appropriate
working groups.

Inputs and Collaboration:

The WG will consider draft-peterson-dispatch-rtpsec and
draft-johnston-dispatch-osrtp as input to the work. The WG is expected
to collaborate closely with SIPCORE, AVTCORE, STIR, MMUSIC, and possibly