Re: [dispatch] DISPATCH @ IETF-87 Deadlines
Paul Kyzivat <pkyzivat@alum.mit.edu> Wed, 26 June 2013 15:41 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 1D00C21F9D76 for <dispatch@ietfa.amsl.com>; Wed, 26 Jun 2013 08:41:45 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -0.168
X-Spam-Level:
X-Spam-Status: No, score=-0.168 tagged_above=-999 required=5 tests=[AWL=0.269, BAYES_00=-2.599, FH_RELAY_NODNS=1.451, HELO_MISMATCH_NET=0.611, RDNS_NONE=0.1]
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 VDPPaY8dptwN for <dispatch@ietfa.amsl.com>; Wed, 26 Jun 2013 08:41:40 -0700 (PDT)
Received: from qmta10.westchester.pa.mail.comcast.net (qmta10.westchester.pa.mail.comcast.net [IPv6:2001:558:fe14:43:76:96:62:17]) by ietfa.amsl.com (Postfix) with ESMTP id 3F82A21F9971 for <dispatch@ietf.org>; Wed, 26 Jun 2013 08:41:40 -0700 (PDT)
Received: from omta24.westchester.pa.mail.comcast.net ([76.96.62.76]) by qmta10.westchester.pa.mail.comcast.net with comcast id szeP1l0041ei1Bg5A3hfER; Wed, 26 Jun 2013 15:41:39 +0000
Received: from Paul-Kyzivats-MacBook-Pro.local ([50.138.229.164]) by omta24.westchester.pa.mail.comcast.net with comcast id t3hf1l00W3ZTu2S3k3hfRS; Wed, 26 Jun 2013 15:41:39 +0000
Message-ID: <51CB0BB2.8050804@alum.mit.edu>
Date: Wed, 26 Jun 2013 11:41:38 -0400
From: Paul Kyzivat <pkyzivat@alum.mit.edu>
User-Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.7; rv:17.0) Gecko/20130509 Thunderbird/17.0.6
MIME-Version: 1.0
To: dispatch@ietf.org
References: <CAHBDyN6Rtg8GZSaqp1m1gV2F4ULuzUgyJhPENUZHSQOH9AFx3A@mail.gmail.com> <4A4F136CBD0E0D44AE1EDE36C4CD9D996EE6F1ED@VOEXM31W.internal.vodafone.com>
In-Reply-To: <4A4F136CBD0E0D44AE1EDE36C4CD9D996EE6F1ED@VOEXM31W.internal.vodafone.com>
Content-Type: text/plain; charset="UTF-8"; format="flowed"
Content-Transfer-Encoding: 8bit
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=comcast.net; s=q20121106; t=1372261299; bh=Og/x/ecKMZfPtZ0Y8n+H71XV2d0Oi6+epOLM31LajbM=; h=Received:Received:Message-ID:Date:From:MIME-Version:To:Subject: Content-Type; b=WfzUMOsFSz73VUsKCYAI+t3XfqVVJbKqa+EAvZtIWmNYqsb5XJovHq+k6irZEtMiG lePpEP9swmtuzRKCMhzQLJeLnyHPyncTQYJmlEN2xvrN1oZ4ZV+oePNM/6QGSQlL1P SyGkOBJmdy9z1u8FqDNNH3iq05p+LdsGuGLsbKMruWRdFuQ0qbag1EADHcmwqz5iOc VQdDwR7BiOV7FsqijrvXD8hblml1JFIhyBxut5Db1Gze0pS8pnfChsM7H1GZqCE5qC z6UHArP7/f6ib18A1eFYpWeGplG+HCVW5UOgSBRZLg96LuwsaULqujCMfxGB3fZtSr c33C8R0wC7Meg==
Subject: Re: [dispatch] DISPATCH @ IETF-87 Deadlines
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: Wed, 26 Jun 2013 15:41:45 -0000
Peter, I'm fine with discussing this in dispatch. My main concern with this is around REQ9 - locator of log collector server: - how is the log collector designated? The examples show just a dns name. I would think it would need to be a URL. But what protocol would be used to transfer the log? Is it required that those supporting log-me also support specific protocol(s) for log collection? If there is more than one protocol, how will the entity inserting the log-me indicator decide which one? (There isn't any opportunity here to negotiate which one will be used.) - This has security implications. How would the server sending the log decide if it can trust the specified server? Would it have a list of servers it trusts? This seems like a hard problem. And it may need to be solved for each protocol that might be used to transfer logs. It is glossed over in the security considerations. Thanks, Paul On 6/21/13 6:29 AM, Dawes, Peter, Vodafone Group wrote: > Hello Mary, > I would like the dispatch working group to consider two drafts at IETF-87 as follows: > > 1) http://www.ietf.org/id/draft-dawes-dispatch-logme-reqs-02.txt > This draft was discussed at IETF-86 and has been updated with potential solutions to requirements (clause 7). I would like to propose that INSIPID adopt this work. > (from IETF-86 http://trac.tools.ietf.org/wg/dispatch/trac/wiki#) > •Logging: General support for adopting this work. Proposal to update INSIPID WG with a new deliverable. > ◦Charter: http://www.ietf.org/mail-archive/web/dispatch/current/msg04560.html > ◦Related documents: > ■draft-dawes-dispatch-logme-reqs > > 2) http://www.ietf.org/id/draft-dawes-dispatch-mediasec-parameter-06.txt > An informational RFC describing a header field parameter to distinguish security mechanisms that protect media (as opposed to those that protect signalling) between a UA and its first-hop SIP entity, and to create an IANA registry to list names of such media-specific security mechanisms. > > Regards, > Peter > > -----Original Message----- > From: dispatch-bounces@ietf.org [mailto:dispatch-bounces@ietf.org] On Behalf Of Mary Barnes > Sent: 18 June 2013 23:05 > To: DISPATCH > Cc: Cullen Jennings > Subject: [dispatch] DISPATCH @ IETF-87 Deadlines > > As a reminder, the deadline for letting the chairs know that you are planning to submit something for consideration for the IETF-87 > deadline is June 24th, 2013 (next Monday - 6 days time). The > subsequent deadlines are also in the wiki: > http://tools.ietf.org/wg/dispatch/trac/wiki > Noting, that the draft deadlines are the same as the IETF draft deadlines. > > Regards, > Mary > DISPATCH WG co-chair > _______________________________________________ > dispatch mailing list > dispatch@ietf.org > https://www.ietf.org/mailman/listinfo/dispatch > _______________________________________________ > dispatch mailing list > dispatch@ietf.org > https://www.ietf.org/mailman/listinfo/dispatch >
- [dispatch] DISPATCH @ IETF-87 Deadlines Mary Barnes
- Re: [dispatch] DISPATCH @ IETF-87 Deadlines Dawes, Peter, Vodafone Group
- Re: [dispatch] DISPATCH @ IETF-87 Deadlines Paul Kyzivat
- Re: [dispatch] DISPATCH @ IETF-87 Deadlines Mary Barnes