Guidelines for Using the Privacy Mechanism for SIP
RFC 5379

Approval announcement
Draft of message to be sent after approval:

From: The IESG <>
To: RFC Editor <>
Cc: The IESG <>, <>,
Subject: Re: Informational RFC to be: 

The IESG has no problem with the publication of 'Guidelines for Using the 
Privacy Mechanism for SIP' <draft-munakata-sip-privacy-guideline-04.txt> 
as an Informational RFC. 

The IESG would also like the IRSG or RFC-Editor to review the comments in 
the datatracker 
related to this document and determine whether or not they merit 
incorporation into the document. Comments may exist in both the ballot 
and the comment log. 

The IESG contact person is Jon Peterson.

A URL of this Internet-Draft is:

The process for such documents is described at

Thank you,

The IESG Secretary

Technical Summary

This document provides guidelines for the use of the privacy mechanisms
in RFC3233 in light of subsequent protocol developments, such as the
addition of new SIP headers that might expose private information. 

Working Group Summary

This document received review and discussion in the SIP WG, but in order
to lighten the workload of that group it was advanced as an individual

Document Quality

This document was reviewed for RFC3932 conflicts by Jon Peterson. Mary
Barnes reviewed this document for the SIP WG prior to submission via
RFC-Editor. Joel Halpern reviewed the document for the RFC-Editor. David
Black reviewed this document for Gen-ART.


Jon Peterson is the document shepherd.

RFC Editor Note

The IESG thinks that this work is related to IETF work done in the SIP
WG, but this does not prevent publishing.


  This RFC is not a candidate for any level of Internet Standard.
  The IETF disclaims any knowledge of the fitness of this RFC for
  any purpose and in particular notes that the decision to publish
  is not based on IETF review for such things as security,
  congestion control, or inappropriate interaction with deployed
  protocols.  The RFC Editor has chosen to publish this document at
  its discretion.  Readers of this document should exercise caution
  in evaluating its value for implementation and deployment.  See
  RFC 3932 for more information.


  (Insert IANA Note here or remove section)