Re: [dispatch] draft-kyzivat-dispatch-trs-call-info-purpose-00: comments
Paul Kyzivat <pkyzivat@alum.mit.edu> Tue, 13 January 2015 18:30 UTC
Return-Path: <prvs=84558bb34b=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 388CB1A9034 for <dispatch@ietfa.amsl.com>; Tue, 13 Jan 2015 10:30:38 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -4.211
X-Spam-Level:
X-Spam-Status: No, score=-4.211 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RCVD_IN_DNSWL_MED=-2.3, SPF_PASS=-0.001, T_RP_MATCHES_RCVD=-0.01] autolearn=ham
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 2BURQTmTG-nz for <dispatch@ietfa.amsl.com>; Tue, 13 Jan 2015 10:30:35 -0800 (PST)
Received: from alum-mailsec-scanner-2.mit.edu (alum-mailsec-scanner-2.mit.edu [18.7.68.13]) by ietfa.amsl.com (Postfix) with ESMTP id A355F1A902F for <dispatch@ietf.org>; Tue, 13 Jan 2015 10:30:35 -0800 (PST)
X-AuditID: 1207440d-f79976d000005643-d3-54b5644ad84f
Received: from outgoing-alum.mit.edu (OUTGOING-ALUM.MIT.EDU [18.7.68.33]) by alum-mailsec-scanner-2.mit.edu (Symantec Messaging Gateway) with SMTP id 58.C4.22083.A4465B45; Tue, 13 Jan 2015 13:30:35 -0500 (EST)
Received: from Paul-Kyzivats-MacBook-Pro.local (c-50-138-229-151.hsd1.ma.comcast.net [50.138.229.151]) (authenticated bits=0) (User authenticated as pkyzivat@ALUM.MIT.EDU) by outgoing-alum.mit.edu (8.13.8/8.12.4) with ESMTP id t0DIUYB4022002 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES128-SHA bits=128 verify=NOT); Tue, 13 Jan 2015 13:30:34 -0500
Message-ID: <54B5644A.4050807@alum.mit.edu>
Date: Tue, 13 Jan 2015 13:30:34 -0500
From: Paul Kyzivat <pkyzivat@alum.mit.edu>
User-Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.7; rv:24.0) Gecko/20100101 Thunderbird/24.6.0
MIME-Version: 1.0
To: Brett Tate <brett@broadsoft.com>, dispatch@ietf.org
References: <ff4ad8c4cebaa707857b1a8597ca04f7@mail.gmail.com>
In-Reply-To: <ff4ad8c4cebaa707857b1a8597ca04f7@mail.gmail.com>
Content-Type: text/plain; charset="UTF-8"; format="flowed"
Content-Transfer-Encoding: 7bit
X-Brightmail-Tracker: H4sIAAAAAAAAA+NgFuplleLIzCtJLcpLzFFi42IRYndR1PVO2RpicGIho0Xz/H+MFksnLWB1 YPL4cTvQY8mSn0wBTFHcNkmJJWXBmel5+nYJ3BnNx/ezFhzkrTiyfAp7A+Mjri5GTg4JAROJ rbdOsEPYYhIX7q1n62Lk4hASuMwoMWP2ORYI5zmTxK838xhBqngFtCU+3fkM1sEioCpxYsY9 JhCbTUBLYs6h/ywgtqhAssSarZPYIeoFJU7OfAIU5+AQETCXmH+zEiQsLOAm0b1pNliJkICt xKpbf1hBbE4BO4mj334wg9jMAmYSXVu7GCFseYntb+cwT2Dkn4Vk6iwkZbOQlC1gZF7FKJeY U5qrm5uYmVOcmqxbnJyYl5dapGukl5tZopeaUrqJERKQvDsY/6+TOcQowMGoxMMrkLclRIg1 say4MvcQoyQHk5Ior2PQ1hAhvqT8lMqMxOKM+KLSnNTiQ4wSHMxKIryPzIFyvCmJlVWpRfkw KWkOFiVxXrUl6n5CAumJJanZqakFqUUwWT0ODoEvH899YhS49Kb7K6MUS15+XqqSBO+jRKBR gkWp6akVaZk5JQgNTBycIOu4pESKU/NSUosSS0sy4kFRG18MjFuQFA/QJZxJIJcUFyTmAkUh Wk8xKkqJ8z4EmSsAksgozYMbC0tFrxjFgf4W5j0GUsUDTGNw3a+ABjMBDV7cvhlkcEkiQkqq gXHy7TDnUoGg27M6FyZGHpIJ0LdVSFh/vEctOSmB/7HxpvjKB/P3/vMXOrNUZd7Wg59uHrxx zlD20sW5tqIbz/T9cGJdLTt93w7h2Wm8Xws/XhSv2nrlCNcxk65z4XMv6VW5aF/dcXiv6i7f yQG/YrcyOFgoGGoWeTRKGTlfqI39u2SuM9diw/tKLMUZiYZazEXFiQAR4TcMIAMAAA==
Archived-At: <http://mailarchive.ietf.org/arch/msg/dispatch/zPPSPDeCB1f7J5SPSnGZ5pXVpGk>
Subject: Re: [dispatch] draft-kyzivat-dispatch-trs-call-info-purpose-00: comments
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: <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, 13 Jan 2015 18:30:38 -0000
Brett, Thanks for commenting. On 1/13/15 12:59 PM, Brett Tate wrote: > Hi, > > The following are some comments concerning > draft-kyzivat-dispatch-trs-call-info-purpose-00. > > Thanks, > Brett > > ------ > > General comment: It might be better to introduce a new header instead of > using Call-Info. For instance, is the following RFC 3261 section 20.9 > recommendation acceptable for the new purpose value? > > "Therefore, it is RECOMMENDED that a UA only render the information in the > Call-Info > header field if it can verify the authenticity of the element that > originated the header field and trusts that element." So your concern is that with Call-Info the information might be rendered to the user? I don't think that is an important concern. Other purposes aren't intended for rendering. E.g. - list-management (RFC5367) - call-completion (RFC6910) - impp (RFC6993) (Though this might end up being rendered indirectly) - ccmp (RFC7082) IMO using Call-Info for original-identity seems in line with the other uses. > Section 2: Concerning the example, the sip-uri should be within brackets. > > Section 2: Concerning the example, the original-identity should not be > within quotes. Thanks for catching these. The fixes will be in the next version. > Section 3 paragraph 1: Comparing it to an identify header (instead of > Contact) might be more accurate since it might be displayed to the user > and has a billing impact. However, I guess that the same could be said > about Contact and they both can be spoofed. > Yes. I think making an analogy to the Identity header would raise lots of other concerns that aren't appropriate here. Thanks, Paul
- [dispatch] draft-kyzivat-dispatch-trs-call-info-p… Brett Tate
- Re: [dispatch] draft-kyzivat-dispatch-trs-call-in… Paul Kyzivat
- Re: [dispatch] draft-kyzivat-dispatch-trs-call-in… Brett Tate
- Re: [dispatch] draft-kyzivat-dispatch-trs-call-in… Paul Kyzivat