[Insipid] Review of draft-ietf-insipid-logme-reqs-02 [[WAS: Re: draft-ietf-insipid-logme-marking-02.txt: comments]]

"Gonzalo Salgueiro (gsalguei)" <gsalguei@cisco.com> Mon, 11 May 2015 05:25 UTC

Return-Path: <gsalguei@cisco.com>
X-Original-To: insipid@ietfa.amsl.com
Delivered-To: insipid@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com []) by ietfa.amsl.com (Postfix) with ESMTP id D816F1A1A8A for <insipid@ietfa.amsl.com>; Sun, 10 May 2015 22:25:17 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -16.211
X-Spam-Status: No, score=-16.211 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, GB_I_LETTER=-2, MIME_8BIT_HEADER=0.3, RCVD_IN_DNSWL_HI=-5, SPF_PASS=-0.001, T_RP_MATCHES_RCVD=-0.01, USER_IN_DEF_DKIM_WL=-7.5] autolearn=ham
Received: from mail.ietf.org ([]) by localhost (ietfa.amsl.com []) (amavisd-new, port 10024) with ESMTP id DDT2mPOtI2nk for <insipid@ietfa.amsl.com>; Sun, 10 May 2015 22:25:16 -0700 (PDT)
Received: from rcdn-iport-6.cisco.com (rcdn-iport-6.cisco.com []) (using TLSv1 with cipher RC4-SHA (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 2BF281A1A80 for <insipid@ietf.org>; Sun, 10 May 2015 22:25:16 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=cisco.com; i=@cisco.com; l=5370; q=dns/txt; s=iport; t=1431321916; x=1432531516; h=from:to:cc:subject:date:message-id:references: in-reply-to:content-id:content-transfer-encoding: mime-version; bh=LykhbLbYT+JUvJ1Vj2SRjsJUikY+BKkzpdkFBgFg46w=; b=b+i796GbsCsxpoeMyAcw1gyv5CYis5w480V1hQHN5Xl9JwexUJvpcmhU QINMwdpJ4Hyih0SFsGJVXWPHJ8rl0V9il+Mg9Cc3ANQdhFvrxJkjMtYSC Uk/zaNWkoyrleoAHaPKFNi8DQrQ8VIBzJDLl72N8G7C8+XOc0Gm55e/5Z c=;
X-IronPort-Anti-Spam-Filtered: true
X-IronPort-AV: E=Sophos;i="5.13,404,1427760000"; d="scan'208";a="418624901"
Received: from rcdn-core-5.cisco.com ([]) by rcdn-iport-6.cisco.com with ESMTP; 11 May 2015 05:25:15 +0000
Received: from xhc-aln-x10.cisco.com (xhc-aln-x10.cisco.com []) by rcdn-core-5.cisco.com (8.14.5/8.14.5) with ESMTP id t4B5PF1G004607 (version=TLSv1/SSLv3 cipher=AES128-SHA bits=128 verify=FAIL); Mon, 11 May 2015 05:25:15 GMT
Received: from xmb-rcd-x04.cisco.com ([]) by xhc-aln-x10.cisco.com ([]) with mapi id 14.03.0195.001; Mon, 11 May 2015 00:25:15 -0500
From: "Gonzalo Salgueiro (gsalguei)" <gsalguei@cisco.com>
To: Jörgen Axell <jorgen.axell@ericsson.com>
Thread-Topic: Review of draft-ietf-insipid-logme-reqs-02 [[WAS: Re: [Insipid] draft-ietf-insipid-logme-marking-02.txt: comments]]
Thread-Index: AQHQi6rbVMaL5r3BPEaoHMfM/v+kKQ==
Date: Mon, 11 May 2015 05:25:14 +0000
Message-ID: <2237B877-86D9-4C15-B5A6-24B8295DD98E@cisco.com>
References: <5AEA7B339C0B944BB33A6939249264AD1A27578D@ESESSMB305.ericsson.se>
In-Reply-To: <5AEA7B339C0B944BB33A6939249264AD1A27578D@ESESSMB305.ericsson.se>
Accept-Language: en-US
Content-Language: en-US
x-originating-ip: []
Content-Type: text/plain; charset="utf-8"
Content-ID: <7AFAB85A6FE6084C8021C1D05F40DA8C@emea.cisco.com>
Content-Transfer-Encoding: base64
MIME-Version: 1.0
Archived-At: <http://mailarchive.ietf.org/arch/msg/insipid/8sDHLaxBxrClJdcnLyqNll1iRiE>
Cc: Peter Dawes <Peter.Dawes@vodafone.com>, "insipid@ietf.org" <insipid@ietf.org>
Subject: [Insipid] Review of draft-ietf-insipid-logme-reqs-02 [[WAS: Re: draft-ietf-insipid-logme-marking-02.txt: comments]]
X-BeenThere: insipid@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: SIP Session-ID discussion list <insipid.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/insipid>, <mailto:insipid-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/insipid/>
List-Post: <mailto:insipid@ietf.org>
List-Help: <mailto:insipid-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/insipid>, <mailto:insipid-request@ietf.org?subject=subscribe>
X-List-Received-Date: Mon, 11 May 2015 05:25:18 -0000

Thanks for your review, Jorgen.  I will let Peter, as editor of the document, respond to your review but I am updating the subject since it is misleading as it is a review is for the requirements document and not the ‘logme’ solution document.


<as chair>

> On May 8, 2015, at 8:31 AM, Jörgen Axell <jorgen.axell@ericsson.com> wrote:
> 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
> _______________________________________________
> insipid mailing list
> insipid@ietf.org
> https://www.ietf.org/mailman/listinfo/insipid