IETF Logo Mail Archive

Re: [dispatch] draft-dawes-dispatch-logme-reqs-02

"DRAGE, Keith (Keith)" <keith.drage@alcatel-lucent.com> Tue, 23 July 2013 01:49 UTC

Return-Path: <keith.drage@alcatel-lucent.com>
X-Original-To: dispatch@ietfa.amsl.com
Delivered-To: dispatch@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 2A48311E81D0 for <dispatch@ietfa.amsl.com>; Mon, 22 Jul 2013 18:49:21 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -110.372
X-Spam-Level:
X-Spam-Status: No, score=-110.372 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, RCVD_IN_DNSWL_HI=-8, SARE_SUB_OBFU_Q1=0.227, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id pU7Ye8tLm84C for <dispatch@ietfa.amsl.com>; Mon, 22 Jul 2013 18:49:15 -0700 (PDT)
Received: from ihemail2.lucent.com (ihemail2.lucent.com [135.245.0.35]) by ietfa.amsl.com (Postfix) with ESMTP id A3E4611E8183 for <dispatch@ietf.org>; Mon, 22 Jul 2013 18:49:15 -0700 (PDT)
Received: from fr711usmtp1.zeu.alcatel-lucent.com (h135-239-2-122.lucent.com [135.239.2.122]) by ihemail2.lucent.com (8.13.8/IER-o) with ESMTP id r6N1nCNb023934 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=FAIL); Mon, 22 Jul 2013 20:49:13 -0500 (CDT)
Received: from FR712WXCHHUB03.zeu.alcatel-lucent.com (fr712wxchhub03.zeu.alcatel-lucent.com [135.239.2.74]) by fr711usmtp1.zeu.alcatel-lucent.com (GMO) with ESMTP id r6N1nBWN032617 (version=TLSv1/SSLv3 cipher=AES128-SHA bits=128 verify=FAIL); Tue, 23 Jul 2013 03:49:11 +0200
Received: from FR712WXCHMBA11.zeu.alcatel-lucent.com ([169.254.7.194]) by FR712WXCHHUB03.zeu.alcatel-lucent.com ([135.239.2.74]) with mapi id 14.02.0247.003; Tue, 23 Jul 2013 03:49:11 +0200
From: "DRAGE, Keith (Keith)" <keith.drage@alcatel-lucent.com>
To: Paul Kyzivat <pkyzivat@alum.mit.edu>, "dispatch@ietf.org" <dispatch@ietf.org>
Thread-Topic: [dispatch] draft-dawes-dispatch-logme-reqs-02
Thread-Index: AQHOhyHT2fQ5+R9+ZUKrwNePXTabJZlxfzRg
Date: Tue, 23 Jul 2013 01:49:10 +0000
Message-ID: <949EF20990823C4C85C18D59AA11AD8B07036A@FR712WXCHMBA11.zeu.alcatel-lucent.com>
References: <51EDA2E8.1050603@alum.mit.edu>
In-Reply-To: <51EDA2E8.1050603@alum.mit.edu>
Accept-Language: en-GB, en-US
Content-Language: en-US
X-MS-Has-Attach:
X-MS-TNEF-Correlator:
x-originating-ip: [135.239.27.41]
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: quoted-printable
MIME-Version: 1.0
X-Scanned-By: MIMEDefang 2.57 on 135.245.2.35
Subject: Re: [dispatch] draft-dawes-dispatch-logme-reqs-02
X-BeenThere: dispatch@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: DISPATCH Working Group Mail List <dispatch.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/dispatch>, <mailto:dispatch-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/dispatch>
List-Post: <mailto:dispatch@ietf.org>
List-Help: <mailto:dispatch-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/dispatch>, <mailto:dispatch-request@ietf.org?subject=subscribe>
X-List-Received-Date: Tue, 23 Jul 2013 01:49:21 -0000

The next discussion of this draft will take place in the INSIPID group so you might like to post your comments there.

Regards

Keith

> -----Original Message-----
> From: dispatch-bounces@ietf.org [mailto:dispatch-bounces@ietf.org] On
> Behalf Of Paul Kyzivat
> Sent: 22 July 2013 22:24
> To: dispatch@ietf.org
> Subject: [dispatch] draft-dawes-dispatch-logme-reqs-02
> 
> Some questions about this draft:
> 
> The requirements and other discussion imply certain behavior by servers
> that support this. I'd like to hear more explicit discussion of what
> that expected behavior is, within the potential solutions.
> 
> E.g., when some servers are expected to be dialog stateful. Also if
> logging is to stop after some period of time.
> 
> Section 7.1:
> 
> This says the header is first inserted by the UAC. There might be reason
> to have it inserted by the UAS in some cases, or even a proxy or B2BUA
> based on policy for debugging a UA that can't be controlled.
> 
> Is free text good enough for identifying test cases? Isn't there
> possibility of collision? Since there is likely to be resistance to
> meaningful names that might tunnel information, perhaps these should be
> random numbers.
> 
> I want to hear more about sending the address of the server collecting
> logs. For this to be useful there must be an explicit or implicit
> protocol used to transmit the logs. Is there one such protocol or many?
> If many, how do you know which will be supported? What about trust by
> the server doing the logging of the log server, and authorization by the
> log server of those sending logs? Will all servers doing logging want to
> use a server chosen by the one inserting the logme request?
> 
> Section 7.2:
> 
> Where does the test case id go with this solution?
> 
> In Figure 3 the call-info in the figure is syntactically incorrect. The
> parameter is a domain name, but it is required to be a URL.
> 
> 	Thanks,
> 	Paul
> _______________________________________________
> dispatch mailing list
> dispatch@ietf.org
> https://www.ietf.org/mailman/listinfo/dispatch

v2.23.0 | Report a Bug | By Email