Re: [dispatch] draft-dawes-dispatch-logme-reqs-02
Paul Kyzivat <pkyzivat@alum.mit.edu> Tue, 23 July 2013 02:49 UTC
Return-Path: <pkyzivat@alum.mit.edu>
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 0625911E81D4 for <dispatch@ietfa.amsl.com>; Mon, 22 Jul 2013 19:49:35 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: 0.03
X-Spam-Level:
X-Spam-Status: No, score=0.03 tagged_above=-999 required=5 tests=[AWL=0.240, BAYES_00=-2.599, FH_RELAY_NODNS=1.451, HELO_MISMATCH_NET=0.611, RDNS_NONE=0.1, SARE_SUB_OBFU_Q1=0.227]
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 TqJkaqfb1fuE for <dispatch@ietfa.amsl.com>; Mon, 22 Jul 2013 19:49:28 -0700 (PDT)
Received: from qmta04.westchester.pa.mail.comcast.net (qmta04.westchester.pa.mail.comcast.net [IPv6:2001:558:fe14:43:76:96:62:40]) by ietfa.amsl.com (Postfix) with ESMTP id D0B9511E8183 for <dispatch@ietf.org>; Mon, 22 Jul 2013 19:49:27 -0700 (PDT)
Received: from omta07.westchester.pa.mail.comcast.net ([76.96.62.59]) by qmta04.westchester.pa.mail.comcast.net with comcast id 3ekS1m0041GhbT854epThk; Tue, 23 Jul 2013 02:49:27 +0000
Received: from Paul-Kyzivats-MacBook-Pro.local ([50.138.229.164]) by omta07.westchester.pa.mail.comcast.net with comcast id 3epS1m00u3ZTu2S3TepTlY; Tue, 23 Jul 2013 02:49:27 +0000
Message-ID: <51EDEF36.9020702@alum.mit.edu>
Date: Mon, 22 Jul 2013 22:49:26 -0400
From: Paul Kyzivat <pkyzivat@alum.mit.edu>
User-Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.7; rv:17.0) Gecko/20130620 Thunderbird/17.0.7
MIME-Version: 1.0
To: "DRAGE, Keith (Keith)" <keith.drage@alcatel-lucent.com>
References: <51EDA2E8.1050603@alum.mit.edu> <949EF20990823C4C85C18D59AA11AD8B07036A@FR712WXCHMBA11.zeu.alcatel-lucent.com>
In-Reply-To: <949EF20990823C4C85C18D59AA11AD8B07036A@FR712WXCHMBA11.zeu.alcatel-lucent.com>
Content-Type: text/plain; charset="ISO-8859-1"; format="flowed"
Content-Transfer-Encoding: 7bit
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=comcast.net; s=q20121106; t=1374547767; bh=iNT/yvnh++rhEb8eaM/4ubyyBSQCkcxQbHjBKPSN7kA=; h=Received:Received:Message-ID:Date:From:MIME-Version:To:Subject: Content-Type; b=fghHIm6Gr+0W7D/51llB/LDnIH9dasHVsBwsrIkHIaPy3CJ+Akej9WsMqzikN2GOf C5KIQxNnzKCPsXH98x21amawvhqkNdvCO2COMWXTKRR78bSGqyMyuzF6qfxnfRmFB+ DMVXT8RB5l/YzZ/Om7SafFoOsJ6oEQOM+MXUqZRyXvpdofLxljVlvJngQ/GKfgKSgA KJeC/mLaiZY/wRY1qlPoUS+ls9F4RyPQ9WerSXcnnJe1knrUBddQbzjAyYqzllE6j7 GUffiNELVEnJh6p2xvNUsuCXXctpL7/QQI3aD+ZMLClzS4Fs9MaHAC0CYEIhGfqyPt NJ3Gwz+u54rkg==
Cc: "dispatch@ietf.org" <dispatch@ietf.org>
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 02:49:35 -0000
On 7/22/13 9:49 PM, DRAGE, Keith (Keith) wrote: > The next discussion of this draft will take place in the INSIPID group so you might like to post your comments there. OK. I wasn't thinking - just went by the name of the draft. Thanks, Paul > 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 >
- [dispatch] draft-dawes-dispatch-logme-reqs-02 Paul Kyzivat
- Re: [dispatch] draft-dawes-dispatch-logme-reqs-02 DRAGE, Keith (Keith)
- Re: [dispatch] draft-dawes-dispatch-logme-reqs-02 Paul Kyzivat