Re: [Insipid] draft-ietf-insipid-logme-reqs
"Dawes, Peter, Vodafone Group" <Peter.Dawes@vodafone.com> Tue, 06 September 2016 11:59 UTC
Return-Path: <Peter.Dawes@vodafone.com>
X-Original-To: insipid@ietfa.amsl.com
Delivered-To: insipid@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 22C1C12B4AE for <insipid@ietfa.amsl.com>; Tue, 6 Sep 2016 04:59:37 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -3.218
X-Spam-Level:
X-Spam-Status: No, score=-3.218 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, FREEMAIL_FROM=0.001, FREEMAIL_REPLY=1, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_MED=-2.3, RCVD_IN_MSPIKE_H3=-0.01, RCVD_IN_MSPIKE_WL=-0.01] autolearn=ham autolearn_force=no
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 NXp3B17cYl_E for <insipid@ietfa.amsl.com>; Tue, 6 Sep 2016 04:59:34 -0700 (PDT)
Received: from mail1.bemta6.messagelabs.com (mail1.bemta6.messagelabs.com [193.109.254.110]) (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 238B912B3AC for <insipid@ietf.org>; Tue, 6 Sep 2016 04:52:28 -0700 (PDT)
Received: from [193.109.254.3] by server-6.bemta-6.messagelabs.com id 8F/18-11175-AFDAEC75; Tue, 06 Sep 2016 11:52:26 +0000
X-Brightmail-Tracker: H4sIAAAAAAAAA+NgFtrFKsWRWlGSWpSXmKPExsVy+MWXDt1fa8+ FG3TM4raYOfswi0Xjg2nsFvPvP2NyYPaY8nsjq8fOWXfZPZYs+ckUwBzFmpmXlF+RwJqxcott wfPtjBUfun8zNjD2LmPsYuTiEBLYwyjRvGY9C4SzklHizrQJUJnlTBKHTn1mg3AOM0oc2/+JG cKZwyixaMMGoAwHB5uAvcSMPTFdjJwcIgJJEqtWPGQFsZkFNCVWLL7NDmILC2hJXOp9xAhRoy 2xfPI3JgjbSGLmg15mEJtFQEXi3cs+sF5egVCJn1tWsULsagJafGM+2CBOAVuJ/c3PwGxGAVm JL42rmSGWiUvcejIfbKiEgIDEkj3nmSFsUYmXj/9BHZQncWJxOzvEAkGJkzOfsExgFJ2FpH0W krJZSMog4joSC3Z/YoOwtSWWLXzNDGOfOfCYCVl8ASP7Kkb14tSistQiXWO9pKLM9IyS3MTMH F1DAzO93NTi4sT01JzEpGK95PzcTYzAOGUAgh2MHf+cDjFKcjApifKqBZ4LF+JLyk+pzEgszo gvKs1JLT7EKMPBoSTB+3cNUE6wKDU9tSItMweYMGDSEhw8SiK8jMCkIcRbXJCYW5yZDpE6xag oJc57AqRPACSRUZoH1wZLUpcYZaWEeRmBDhHiKUgtys0sQZV/xSjOwagkzHsNZApPZl4J3PRX QIuZgBav230aZHFJIkJKqoFxj5XYq3XRDutKs2btXFTx68KHH043xb3yIneH7pvxbcOjnjmCi g88f/SzfD59qKx4zZfspnN8+ucbOTxiWRb3CSbd/Lst5NnMPTPsuYWvSN7uPVjL5Oq5PPmHvo 5vwKRT1ldz8jeKGQbMEPQtWjhD9fmLDcG3FQwNxOIycs8bvk/gz2z7Hv9aiaU4I9FQi7moOBE AOsuB+k0DAAA=
X-Env-Sender: Peter.Dawes@vodafone.com
X-Msg-Ref: server-14.tower-184.messagelabs.com!1473162745!64622077!1
X-Originating-IP: [195.232.244.136]
X-StarScan-Received:
X-StarScan-Version: 8.84; banners=-,-,-
X-VirusChecked: Checked
Received: (qmail 6689 invoked from network); 6 Sep 2016 11:52:26 -0000
Received: from mailout04.vodafone.com (HELO mailout04.vodafone.com) (195.232.244.136) by server-14.tower-184.messagelabs.com with DHE-RSA-AES256-GCM-SHA384 encrypted SMTP; 6 Sep 2016 11:52:26 -0000
Received: from mailint01.vodafone.com (mailint01.vodafone.com [195.232.244.198]) by mailout04.vodafone.com (Postfix) with ESMTP id 3sT4hm4WZKznVMT; Tue, 6 Sep 2016 13:52:24 +0200 (CEST)
Received: from mailint01.vodafone.com (localhost [127.0.0.1]) by mailint01.vodafone.com (Postfix) with ESMTP id 3sT4f06BWjzxQQV; Tue, 6 Sep 2016 13:50:00 +0200 (CEST)
Received: from VOEXC05W.internal.vodafone.com (voexc05w.dc-ratingen.de [145.230.101.25]) (using TLSv1 with cipher ECDHE-RSA-AES256-SHA (256/256 bits)) (No client certificate requested) by mailint01.vodafone.com (Postfix) with ESMTPS id 3sT4f062drzxQR7; Tue, 6 Sep 2016 13:50:00 +0200 (CEST)
Received: from VOEXC24W.internal.vodafone.com (145.230.103.196) by VOEXC05W.internal.vodafone.com (145.230.101.25) with Microsoft SMTP Server (TLS) id 14.3.224.2; Tue, 6 Sep 2016 13:50:00 +0200
Received: from VOEXM31W.internal.vodafone.com ([169.254.7.18]) by voexc24w ([145.230.103.196]) with mapi id 14.03.0224.002; Tue, 6 Sep 2016 13:50:00 +0200
From: "Dawes, Peter, Vodafone Group" <Peter.Dawes@vodafone.com>
To: "Arun Arunachalam (carunach)" <carunach@cisco.com>, Alberto Llamas <albertollamaso@gmail.com>
Thread-Topic: draft-ietf-insipid-logme-reqs
Thread-Index: AQHR/MGX4UdRaXrMzkqff9+YjWQBnqBsak+g
Date: Tue, 06 Sep 2016 11:49:58 +0000
Message-ID: <4A4F136CBD0E0D44AE1EDE36C4CD9D99C8B3DF6D@VOEXM31W.internal.vodafone.com>
References: <CAHH1jkM6aTvDmcjWY4+PziWkYUHpTA_jrAsbaY_4UO0DNaVbQw@mail.gmail.com> <901FE941-6579-4694-BFD0-5193F274E688@cisco.com>
In-Reply-To: <901FE941-6579-4694-BFD0-5193F274E688@cisco.com>
Accept-Language: en-GB, en-US
Content-Language: en-US
X-MS-Has-Attach:
X-MS-TNEF-Correlator:
Content-Type: multipart/alternative; boundary="_000_4A4F136CBD0E0D44AE1EDE36C4CD9D99C8B3DF6DVOEXM31Winterna_"
MIME-Version: 1.0
Archived-At: <https://mailarchive.ietf.org/arch/msg/insipid/_pE9UBxNpz4gdIvOpKD2eqJCsrc>
Cc: "insipid@ietf.org" <insipid@ietf.org>
Subject: Re: [Insipid] draft-ietf-insipid-logme-reqs
X-BeenThere: insipid@ietf.org
X-Mailman-Version: 2.1.17
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: Tue, 06 Sep 2016 11:59:37 -0000
Hello Albert, I agree with you that B2BUA behaviour is an important consideration for log me behaviour as illustrated by your example. The requirements certainly need to allow the behaviour you describe and but we need to decide whether the B2BUA procedures fit better in the solution description than in the requirements. The current proposal is to cover your comments in the detailed protocol description (https://www.ietf.org/id/draft-ietf-insipid-logme-marking-05.txt) and I have copied the relevant section below. It would be great to hear if you have any comments on this description (some have already been made by Paul Giralt in https://mailarchive.ietf.org/arch/msg/insipid/1z3zSdIAISPepcW1rrSOxWBlRCE). For the requirements, I think that the UA related requirements are enough to cover the B2BUA case but we could consider adding a sentence like "Note that UA requirements apply to each side of a B2BUA" if it makes things clearer. Regards, Peter from https://www.ietf.org/id/draft-ietf-insipid-logme-marking-05: 5.8. B2BUA Handling of Log-Me Marked Dialogs The log-me marking behaviour of a B2BUA needs to be consistent with its purpose of troubleshooting user problems and regression testing. For example, a B2BUA that does no more than transcoding media can simply copy log-me marking from UAS to UAC whereas a B2BUA that performs varied and complex signalling tasks such as distributing calls in a call centre needs flexible configuration so that log-me marking can target specific B2BUA functions. B2BUA behaviour is described below for each of the B2BUA types described in RFC7092 [RFC7092]. Behaviour described in this clause applies only to dialogs that are being log-me marked. 5.8.1. All B2BUA Roles For dialogs that are being log-me marked, all B2BUAs MUST log-me mark in-dialog SIP requests that they generate on their own, without needing explicit configuration to do so. This rule applies to both the originating and terminating sides of a B2BUA. 5.8.2. Proxy-B2BUA 5.8.2.1. Terminating Behaviour A Proxy-B2BUA SHOULD copy log-me marking in requests and responses from its terminating to the originating side without needing explicit configuration to do so. Dawes Expires February 15, 2017 [Page 10] Internet-Draft log me marking August 2016 5.8.3. Signaling-only and SDP-Modifying Signaling-only 5.8.3.1. Terminating Behaviour A signaling-only B2BUA SHOULD NOT copy log-me marking in requests and responses from its terminating to its originating side. Whether a dialog that a signaling-only B2BUA terminates causes log-me marking of a dialog on its originating side SHOULD be controlled by explicit configuration of the originating side, in the same way that a UAC requires configuration to control log-me marking. 5.8.3.2. Originating Behaviour Whether a signaling-only B2BUA log-me marks SIP requests that it generates on its own SHOULD be controlled by explicit configuration of the originating side, in the same way that a UAC requires configuration to control log-me marking. 5.8.4. Media Relay, Media Aware, Media Termination Log-me marking behaviour is independent of B2BUA media-plane functionality. Behaviour of signaling/media plane B2BUA roles is therefore dictated only by the signaling plane role as described in Section 5.8.2 and Section 5.8.3 in this document. From: Arun Arunachalam (carunach) [mailto:carunach@cisco.com] Sent: 22 August 2016 23:08 To: Alberto Llamas Cc: Dawes, Peter, Vodafone Group; insipid@ietf.org Subject: Re: draft-ietf-insipid-logme-reqs Hi Alberto, Thanks for the feedback ! I think your suggestion is to carry the log-me marker across an end-to-end session instead of limiting it to per-dialog. Adding insipid mailing list. Thanks! Arun On Aug 22, 2016, at 3:26 PM, Alberto Llamas <albertollamaso@gmail.com<mailto:albertollamaso@gmail.com>> wrote: Hello Peter and Chidambaram, I have read your proposed RFC [https://www.ietf.org/id/draft-ietf-insipid-logme-reqs-07.txt] which I find a very good document. I believe that in section 5 you should include a requirement for the case when a B2BUA receive a request (A leg INVITE) which contains a "Log Me" marker and this entity generate another INVITE (B leg) regarding the first one. In this case the "Log me" marker should be preserved when the second INVITE is generated. A common example is when Diversion exists and then we receive an INVITE back with Diversion, History-info headers..etc...then we MUST be able to treat this new call as part of debugging or regression testing. Thanks, -- albert
- [Insipid] [insipid] draft-ietf-insipid-logme-reqs Dawes, Peter, Vodafone Group
- Re: [Insipid] draft-ietf-insipid-logme-reqs Arun Arunachalam (carunach)
- Re: [Insipid] draft-ietf-insipid-logme-reqs Dawes, Peter, Vodafone Group
- Re: [Insipid] draft-ietf-insipid-logme-reqs Alberto Llamas
- Re: [Insipid] draft-ietf-insipid-logme-reqs Dawes, Peter, Vodafone Group