[Insipid] draft-ietf-insipid-logme-marking-02.txt: comments

In general, I believe this functionality is useful to be able to trace faults in a network. Having a signalling based activation is a simple way to follow the path in a network.  I have a few comments:

Section 3: I assume the Network A, B, C has no connection to Country A, B, C. Maybe numbers or different letters is clearer.

REQ-6: I understand that if the SIP proxy marks a response for logging because the UAS did not echo the log-me marker, then it needs to remember that the marker was present in the request. It is harder to understand what the SIP proxy needs to remember if it decides to mark a request that the UA did not mark. Is this rather configuration than remembering something?

6.2.1 The text following "Activating a debug mode" contains a number of "it" which I find hard to read. I assume "it" refers to the activation request but I don't think that is clear from the text.

On the nit side, REQ-1 contains a "log me", which I believe should be "log-me".

Regards,
Jörgen

-----Original Message-----
From: insipid [mailto:insipid-bounces@ietf.org] On Behalf Of internet-drafts@ietf.org
Sent: 27 February 2015 14:21
To: i-d-announce@ietf.org
Cc: insipid@ietf.org
Subject: [Insipid] I-D Action: draft-ietf-insipid-logme-marking-02.txt

A New Internet-Draft is available from the on-line Internet-Drafts directories.
 This draft is a work item of the INtermediary-safe SIP session ID Working Group of the IETF.

        Title           : Marking SIP Messages to be Logged
        Author          : Peter Dawes
	Filename        : draft-ietf-insipid-logme-marking-02.txt
	Pages           : 14
	Date            : 2015-02-27

Abstract:
   SIP networks use signalling monitoring tools to diagnose user
   reported problems and for regression testing if network or user agent
   software is upgraded.  As networks grow and become interconnected,
   including connection via transit networks, it becomes impractical to
   predict the path that SIP signalling will take between user agents,
   and therefore impractical to monitor SIP signalling end-to-end.

   This document describes an indicator for the SIP protocol which can
   be used to mark signalling as of interest to logging.  Such marking
   will typically be applied as part of network testing controlled by
   the network operator and not used in regular user agent signalling.
   However, such marking can be carried end-to-end including the SIP
   user agents, even if a session originates and terminates in different
   networks.

The IETF datatracker status page for this draft is:
https://datatracker.ietf.org/doc/draft-ietf-insipid-logme-marking/

There's also a htmlized version available at:
http://tools.ietf.org/html/draft-ietf-insipid-logme-marking-02

A diff from the previous version is available at:
http://www.ietf.org/rfcdiff?url2=draft-ietf-insipid-logme-marking-02

Please note that it may take a couple of minutes from the time of submission until the htmlized version and diff are available at tools.ietf.org.

Internet-Drafts are also available by anonymous FTP at:
ftp://ftp.ietf.org/internet-drafts/

_______________________________________________
insipid mailing list
insipid@ietf.org
https://www.ietf.org/mailman/listinfo/insipid