IETF Logo Mail Archive

Re: [dispatch] (Fwd) New Version Notification for draft-tveretin-dispatch-remote-01.txt

Paul Kyzivat <pkyzivat@alum.mit.edu> Thu, 03 September 2015 18:15 UTC

Return-Path: <pkyzivat@alum.mit.edu>
X-Original-To: dispatch@ietfa.amsl.com
Delivered-To: dispatch@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 67D311B39E3 for <dispatch@ietfa.amsl.com>; Thu, 3 Sep 2015 11:15:11 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: YES
X-Spam-Score: 18.765
X-Spam-Level: ******************
X-Spam-Status: Yes, score=18.765 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, SPF_SOFTFAIL=0.665, URIBL_SBL=20] autolearn=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 8S-bK5SPbI7C for <dispatch@ietfa.amsl.com>; Thu, 3 Sep 2015 11:15:09 -0700 (PDT)
Received: from resqmta-ch2-05v.sys.comcast.net (resqmta-ch2-05v.sys.comcast.net [IPv6:2001:558:fe21:29:69:252:207:37]) (using TLSv1.2 with cipher DHE-RSA-AES128-SHA (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id BBD591B396B for <dispatch@ietf.org>; Thu, 3 Sep 2015 11:15:09 -0700 (PDT)
Received: from resomta-ch2-14v.sys.comcast.net ([69.252.207.110]) by resqmta-ch2-05v.sys.comcast.net with comcast id CiCj1r00B2PT3Qt01iF8ca; Thu, 03 Sep 2015 18:15:08 +0000
Received: from Paul-Kyzivats-MacBook-Pro.local ([50.138.229.151]) by resomta-ch2-14v.sys.comcast.net with comcast id CiF81r00G3Ge9ey01iF8Gj; Thu, 03 Sep 2015 18:15:08 +0000
To: dispatch@ietf.org
References: <55E8845B.10457.14E9DDA9@fas_vm.surguttel.ru>
From: Paul Kyzivat <pkyzivat@alum.mit.edu>
Message-ID: <55E88E2B.7030006@alum.mit.edu>
Date: Thu, 03 Sep 2015 14:15:07 -0400
User-Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.10; rv:38.0) Gecko/20100101 Thunderbird/38.2.0
MIME-Version: 1.0
In-Reply-To: <55E8845B.10457.14E9DDA9@fas_vm.surguttel.ru>
Content-Type: text/plain; charset="windows-1252"; format="flowed"
Content-Transfer-Encoding: 7bit
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=comcast.net; s=q20140121; t=1441304108; bh=ysFq3yGCpjmSuVjoheWmUDZ2mnfB9ktJVWIccj8/BFA=; h=Received:Received:Subject:To:From:Message-ID:Date:MIME-Version: Content-Type; b=dZPVhsmNwYgVbsqbrp3i1ZvdIrqJDyjJMZ/cszVOwwwPu532qo1egXRyLuzbOC8ju YcHYglqgrtGibt3Jv/vpitCftYNiN1z8vfoqtk2V4sY2udjSdq8huT/uKQHu+ArwuD 0QuM5kMNHkJuAtCO4SJRTNyfZGgKA3QKHVYSpwurPbrxhdIvRNycJO3d4KKkNKQOJy zCL7nlOq9fs5aMgV9et7bxgoyYuaQNwnMv549kl7+ekU6zV9PzSira2t9AqduKB1qs Umd5ekGLPHJmeL5R03CZoOpTZ2JIHDeg5HteR28HMwQ5ioumi5LBvXsWGZvapQePKO b4GDL6qZ81IOA==
Archived-At: <http://mailarchive.ietf.org/arch/msg/dispatch/CsaqXYGcGNS-qMjdqwLhWPAC1lE>
X-Mailman-Approved-At: Thu, 03 Sep 2015 11:17:59 -0700
Subject: Re: [dispatch] (Fwd) New Version Notification for draft-tveretin-dispatch-remote-01.txt
X-BeenThere: dispatch@ietf.org
X-Mailman-Version: 2.1.15
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: <https://mailarchive.ietf.org/arch/browse/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: Thu, 03 Sep 2015 18:15:11 -0000

On 9/3/15 1:33 PM, Anton Tveretin wrote:
> Dear All,
> I want to discuss new ideas. This is a new version of my draft. I will insist on it.

Insist on what?

> I'm sure this is
> not the final version - references need to check. I don't know if I need comparison with RFC
> 3891, or should I remove any reference to it. Some text is commented out of XML.

I would expect to see *much* more in the Security Considerations 
section. This functionality could be used to do lots of bad things. 
There should be a discussion of the threats and how they can be mitigated.

(I find it implausible that individual UAs will contain detailed 
authorization lists, but that may be needed to secure this.)

Without that it is hardly worth discussing the other details of the 
mechanism.

	Thanks,
	Paul

> ------- Forwarded message follows -------
> From:	internet-drafts@ietf.org
> To:	"Anton Tveretin" <fas_vm@surguttel.ru>, "Anton Tveretin"
> 	<fas_vm@surguttel.ru>
> Subject:	New Version Notification for draft-tveretin-dispatch-remote-01.txt
> Date sent:	Tue, 01 Sep 2015 12:33:38 -0700
>
>
>
> A new version of I-D, draft-tveretin-dispatch-remote-01.txt
> has been successfully submitted by Anton Tveretin and posted to the
> IETF repository.
>
> Name:		draft-tveretin-dispatch-remote
> Revision:	01
> Title:		Remote Call Control and Call Pick-up in SIP
> Document date:	2015-09-01
> Group:		Individual Submission
> Pages:		10
> URL:            https://www.ietf.org/internet-drafts/draft-tveretin-dispatch-remote-01.txt
> Status:         https://datatracker.ietf.org/doc/draft-tveretin-dispatch-remote/
> Htmlized:       https://tools.ietf.org/html/draft-tveretin-dispatch-remote-01
> Diff:           https://www.ietf.org/rfcdiff?url2=draft-tveretin-dispatch-remote-01
>
> Abstract:
>     This memo defines a mechanism by which a SIP user agent could inspect
>     calls at another user agent, and control a call, including picking up
>     for itself.
>
>
>
>
> Please note that it may take a couple of minutes from the time of submission
> until the htmlized version and diff are available at tools.ietf.org.
>
> The IETF Secretariat
>
> ------- End of forwarded message -------
>
> _______________________________________________
> dispatch mailing list
> dispatch@ietf.org
> https://www.ietf.org/mailman/listinfo/dispatch
>

v2.28.0 | Report a Bug | By Email | System Status