Re: [Insipid] Review of draft-ietf-insipid-logme-reqs-02

"Dawes, Peter, Vodafone Group" <Peter.Dawes@vodafone.com> Mon, 11 January 2016 15:42 UTC

Return-Path: <Peter.Dawes@vodafone.com>
X-Original-To: insipid@ietfa.amsl.com
Delivered-To: insipid@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 6D8041A1AB6 for <insipid@ietfa.amsl.com>; Mon, 11 Jan 2016 07:42:06 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: 0.8
X-Spam-Level:
X-Spam-Status: No, score=0.8 tagged_above=-999 required=5 tests=[BAYES_50=0.8, FREEMAIL_FROM=0.001, RCVD_IN_DNSWL_NONE=-0.0001, SPF_HELO_PASS=-0.001] autolearn=ham
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 5Wk1yLLIDU-M for <insipid@ietfa.amsl.com>; Mon, 11 Jan 2016 07:42:04 -0800 (PST)
Received: from mail1.bemta5.messagelabs.com (mail1.bemta5.messagelabs.com [195.245.231.149]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 321AF1A1A96 for <insipid@ietf.org>; Mon, 11 Jan 2016 07:42:03 -0800 (PST)
Received: from [85.158.136.83] by server-13.bemta-5.messagelabs.com id CA/86-06091-94DC3965; Mon, 11 Jan 2016 15:42:01 +0000
X-Env-Sender: Peter.Dawes@vodafone.com
X-Msg-Ref: server-11.tower-36.messagelabs.com!1452526921!11368721!1
X-Originating-IP: [195.232.244.134]
X-StarScan-Received:
X-StarScan-Version: 7.35.1; banners=-,-,-
X-VirusChecked: Checked
Received: (qmail 13312 invoked from network); 11 Jan 2016 15:42:01 -0000
Received: from mailout02.vodafone.com (HELO mailout02.vodafone.com) (195.232.244.134) by server-11.tower-36.messagelabs.com with DHE-RSA-AES256-SHA encrypted SMTP; 11 Jan 2016 15:42:01 -0000
Received: from mailint02.vodafone.com (mailint02.vodafone.com [195.232.244.199]) by mailout02.vodafone.com (Postfix) with ESMTP id 3pfK605rrWzbdMS; Mon, 11 Jan 2016 16:42:00 +0100 (CET)
Received: from mailint02.vodafone.com (localhost [127.0.0.1]) by mailint02.vodafone.com (Postfix) with ESMTP id 3pfK604jbyzQnXY; Mon, 11 Jan 2016 16:42:00 +0100 (CET)
Received: from VOEXC03W.internal.vodafone.com (voexc03w.dc-ratingen.de [145.230.101.23]) (using TLSv1 with cipher AES128-SHA (128/128 bits)) (No client certificate requested) by mailint02.vodafone.com (Postfix) with ESMTPS id 3pfK604c2JzQjyJ; Mon, 11 Jan 2016 16:42:00 +0100 (CET)
Received: from VOEXC15W.internal.vodafone.com (145.230.101.17) by VOEXC03W.internal.vodafone.com (145.230.101.23) with Microsoft SMTP Server (TLS) id 14.3.224.2; Mon, 11 Jan 2016 16:42:00 +0100
Received: from VOEXM31W.internal.vodafone.com ([169.254.7.89]) by voexc15w.internal.vodafone.com ([145.230.101.17]) with mapi id 14.03.0224.002; Mon, 11 Jan 2016 16:41:59 +0100
From: "Dawes, Peter, Vodafone Group" <Peter.Dawes@vodafone.com>
To: "Vijay K. Gurbani (vkg@bell-labs.com)" <vkg@bell-labs.com>, "insipid@ietf.org" <insipid@ietf.org>
Thread-Topic: Re: [Insipid] Review of draft-ietf-insipid-logme-reqs-02
Thread-Index: AdFMeipZMyp4trrwT/iglcqTmH/oHg==
Date: Mon, 11 Jan 2016 15:41:59 +0000
Message-ID: <4A4F136CBD0E0D44AE1EDE36C4CD9D99C89BF77C@VOEXM31W.internal.vodafone.com>
Accept-Language: en-GB, en-US
Content-Language: en-US
X-MS-Has-Attach:
X-MS-TNEF-Correlator:
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: quoted-printable
MIME-Version: 1.0
Archived-At: <http://mailarchive.ietf.org/arch/msg/insipid/FtGTMeEqzq7_EyPK2zwCxc3BSvs>
Cc: "Arun Arunachalam \(carunach\) \(carunach@cisco.com\)" <carunach@cisco.com>, "insipid-chairs@tools.ietf.org" <insipid-chairs@tools.ietf.org>
Subject: Re: [Insipid] Review of draft-ietf-insipid-logme-reqs-02
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: <https://mailarchive.ietf.org/arch/browse/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 Jan 2016 15:42:06 -0000

Hello Vijay, All,
The Introduction text has now been revised to focus on service providers not customers (https://www.ietf.org/id/draft-ietf-insipid-logme-reqs-06.txt). I added the word "or" to the text Arun quotes below to clearly separate the single and multiple service provider cases, i.e. 

"Such debugging and tests might be confined to a single service provider or network,
or may occur between the administrative domains of service providers, including 
providers in different countries that are interconnected through networks belonging
to one or more third parties."

Apologies for jumping from -04 to -06 but I made a mistake in the -05 revision. The authors believe that this latest version (-06) includes resolutions of all review comments. 

Regards,
Peter


Re: [Insipid] Review of draft-ietf-insipid-logme-reqs-02
"Arun Arunachalam (carunach)" <carunach@cisco.com> Fri, 08 January 2016 22:59 UTC

Thanks Vijay!

We will update the text to the following:

"Such debugging and tests might be confined to a single service provider or network,
may occur between the administrative domains of service providers, including 
providers in different countries that are interconnected through networks belonging
to one or more third parties."

Arun

On Jan 8, 2016, at 3:59 PM, Vijay K. Gurbani <vkg@bell-labs.com> wrote:

> On 01/06/2016 10:14 AM, Dawes, Peter, Vodafone Group wrote:
>> Hello Vijay, Our requirements draft
>> (https://datatracker.ietf.org/doc/draft-ietf-insipid-logme-reqs/ )
>> for marking SIP sessions to be logged has received several reviews
>> and comments and has been corrected and improved as a result. We
>> think that yours is now the only review without confirmation that the
>> issues raised are resolved. We appreciate that many IETF contributors
>> are very busy and it was great that you found time to review the
>> draft and post to the insipid list. 3GPP has a dependency on this
>> logme marking functionality that is due to complete in February and
>> it would help a lot if this requirements draft could be completed by
>> then.
>> 
>> Could we kindly ask you to check the following e-mails from the
>> insipid exploder to see if your comments are covered: Your review:
>> https://mailarchive.ietf.org/arch/msg/insipid/lD_87m-plpvQ-gcv_QJdydhmnuA
>> Our resolution of your comments:
>> https://mailarchive.ietf.org/arch/msg/insipid/6tlXJVDw3eFaUyuEM6OXf53_xYE
> 
> Peter, all: Thank you for pinging me on this one.
> 
> I am happy with the resolutions you proposed in
> https://mailarchive.ietf.org/arch/msg/insipid/6tlXJVDw3eFaUyuEM6OXf53_xYE
> 
> In addition, I went quickly through version -04 and have one minor
> comment:
> 
> 1/ S1: Such debugging and tests might be confined to a single
>   service provider but might also be needed for customers who have
>   different service providers, including providers in different
>   countries that are interconnected through networks belonging to one
>   or more third parties.
> 
> I don't like the use of "customers" in the above paragraph; after all,
> the customer will most likely not even know what SIP is.  The issue is
> that the debugging is initiated by the service provider to find a
> fault.
> 
> Probably best to say that "Such debugging and tests might be confined
> to a single service provider or network may occur between the
> administrative domains of service providers, including providers in
> different countries that are interconnected through networks belonging
> to one or more third parties."
> 
> Cheers,
> 
> - vijay
> -- 
> Vijay K. Gurbani, Bell Laboratories, Alcatel-Lucent
> 1960 Lucent Lane, Rm. 9C-533, Naperville, Illinois 60563 (USA)
> Email: vkg@{bell-labs.com,acm.org} / vijay.gurbani@alcatel-lucent.com
> Web: http://ect.bell-labs.com/who/vkg/  | Calendar: http://goo.gl/x3Ogq