Guidelines for Using the Privacy Mechanism for SIP
draft-munakata-sip-privacy-guideline-04

[Note]: 'Proposing that this use RFC3932 Note 2: � � � 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.
' added by Amy Vezza

[Ballot comment]
Shouldn't our decision on response 2: be included in the RFC-editor  Note section:

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

[Ballot comment]
Nit: Wouldn't the RFC3932 Section 4 clause 1 text be a bit more appropriate for an IESG Note, given that the draft has been discussed in SIP?

[Note]: 'Proposing that this use RFC3932 Note 2:       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.
' added by Jon Peterson

[Note]: 'Proposing that this use RFC3932 Note 2:

      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.
' added by Jon Peterson

IANA Last Call comments:

As noted in the IANA Considerations section, IANA understands that there are
no IANA actions to be taken upon approval of this document.

This RFC-to-be was submitted to the RFC Editor to be published as
Informational: draft-munakata-sip-privacy-guideline-03.txt.

Please let us know if this document conflicts with the IETF standards
process or other work being done in the IETF community.

Four week timeout expires on 3 July 2008.

Guidelines for Using the Privacy Mechanism for SIP

This is an informational document that provides guidelines for
using the privacy mechanism for Session Initiation Protocol (SIP),
that is specified in RFC 3323 and subsequently extended in RFCs
3325 and 4244. It is intended to clarify the handling of the
target SIP headers/parameters and SDP parameters for each of the
privacy header values (priv-values).


This document was reviewed by Mary Barnes and by Joel Halpern.