INtermediary-safe SIP session ID
charter-ietf-insipid-03

[Ballot comment]

I agree with Sean's and Adrian's comments. Making this not turn
into a long lived bit of personally identifying information should be
a top level requirement.

[Ballot comment]
Thank you for including the mention of privacy in the charter. There will be a clear trade-off between the objectives of this work and the desire for user-privacy: what business, a user might ask, is it of a transit node to know who is calling or who they are calling?

I think it is probably enough that the charter places privacy in scope, but it should not come as a surprise to the WG if the IESG seated at the time they request publication gives a very hard look at all the privacy implications of their work.

[Ballot comment]
The purpose of this rechartering is to add a second document to the insipid deliverables (my apology for how that sounds, but I didn't pick the WG name).  With the addition of the second document, the grammar in the last paragraph has become fractured (the first sentence has a comma splice), and the paragraph has become long.  I strongly suggest splitting it this way:

  This group will focus on two documents:

  The first document [...etc...]

  The second document [...etc...]

Now, as to the wording of the description of the second document:

The first sentence reads very awkwardly to me, and I *think* I understand it.  May I suggest this rewording, assuming it's correct?:

NEW
  The second document will define an indicator that can be added to the
  SIP protocol to indicate that signalling should be logged.
END

You can then change "Such marking" in the following sentence to "The indicator".  If my revision is not correct, then the description of the document is even more unclear than I thought, so please reword it for clarity.

[Ballot comment]
"session tracking" sounds bad - is that tracking for billing or something else?  Maybe we should just pick another word or drop it if it's sessions tracking for billing, troubleshooting, etc.