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

"Vijay K. Gurbani" <vkg@bell-labs.com> Fri, 08 January 2016 20:59 UTC

Return-Path: <vkg@bell-labs.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 A7BAB1B2BB1 for <insipid@ietfa.amsl.com>; Fri, 8 Jan 2016 12:59:18 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -5.002
X-Spam-Level:
X-Spam-Status: No, score=-5.002 tagged_above=-999 required=5 tests=[BAYES_40=-0.001, RCVD_IN_DNSWL_HI=-5, SPF_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 a2e-1zGYUlcd for <insipid@ietfa.amsl.com>; Fri, 8 Jan 2016 12:59:16 -0800 (PST)
Received: from smtp-fr.alcatel-lucent.com (fr-hpida-esg-02.alcatel-lucent.com [135.245.210.21]) (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 638151B2BAC for <insipid@ietf.org>; Fri, 8 Jan 2016 12:59:16 -0800 (PST)
Received: from us70uusmtp3.zam.alcatel-lucent.com (unknown [135.5.2.65]) by Websense Email Security Gateway with ESMTPS id DF7BDBCC2599A; Fri, 8 Jan 2016 20:59:09 +0000 (GMT)
Received: from umail.lucent.com (umail.ndc.lucent.com [135.3.40.61]) by us70uusmtp3.zam.alcatel-lucent.com (GMO) with ESMTP id u08KxC2h028451 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO); Fri, 8 Jan 2016 20:59:12 GMT
Received: from [135.185.238.169] (shoonya.ih.lucent.com [135.185.238.169]) by umail.lucent.com (8.13.8/TPES) with ESMTP id u08KxBZC006036; Fri, 8 Jan 2016 14:59:11 -0600 (CST)
To: "Dawes, Peter, Vodafone Group" <Peter.Dawes@vodafone.com>
References: <4A4F136CBD0E0D44AE1EDE36C4CD9D99C89BC37B@VOEXM31W.internal.vodafone.com>
From: "Vijay K. Gurbani" <vkg@bell-labs.com>
Message-ID: <5690231F.10205@bell-labs.com>
Date: Fri, 8 Jan 2016 14:59:11 -0600
User-Agent: Mozilla/5.0 (X11; Linux i686; rv:38.0) Gecko/20100101 Thunderbird/38.4.0
MIME-Version: 1.0
In-Reply-To: <4A4F136CBD0E0D44AE1EDE36C4CD9D99C89BC37B@VOEXM31W.internal.vodafone.com>
Content-Type: text/plain; charset=windows-1252; format=flowed
Content-Transfer-Encoding: 7bit
Archived-At: <http://mailarchive.ietf.org/arch/msg/insipid/sc7piAl1HJFvxU2QCxcvLutOu0o>
X-Mailman-Approved-At: Fri, 08 Jan 2016 13:02:08 -0800
Cc: "Arun Arunachalam \(carunach\) \(carunach@cisco.com\)" <carunach@cisco.com>, insipid@ietf.org, "Gonzalo Salgueiro \(gsalguei@cisco.com\)" <gsalguei@cisco.com>
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: Fri, 08 Jan 2016 20:59:18 -0000

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