Re: [Sip] draft-elwell-sip-e2e-identity-important-00 posted
Dan York <dyork@voxeo.com> Mon, 07 July 2008 18:41 UTC
Return-Path: <sip-bounces@ietf.org>
X-Original-To: sip-archive@optimus.ietf.org
Delivered-To: ietfarch-sip-archive@core3.amsl.com
Received: from [127.0.0.1] (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id BDE9A3A69D1; Mon, 7 Jul 2008 11:41:12 -0700 (PDT)
X-Original-To: sip@core3.amsl.com
Delivered-To: sip@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id 16D353A69D1 for <sip@core3.amsl.com>; Mon, 7 Jul 2008 11:41:11 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.599
X-Spam-Level:
X-Spam-Status: No, score=-2.599 tagged_above=-999 required=5 tests=[AWL=0.000, BAYES_00=-2.599]
Received: from mail.ietf.org ([64.170.98.32]) by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id Ga9-JbUh19X3 for <sip@core3.amsl.com>; Mon, 7 Jul 2008 11:41:10 -0700 (PDT)
Received: from voxeo.com (mmail.voxeo.com [66.193.54.208]) by core3.amsl.com (Postfix) with ESMTP id 1B9633A67F7 for <sip@ietf.org>; Mon, 7 Jul 2008 11:41:09 -0700 (PDT)
Received: from [66.65.228.203] (account dyork HELO pc-00144.lodestar2.dyndns.org) by voxeo.com (CommuniGate Pro SMTP 5.2.3) with ESMTPSA id 32404889; Mon, 07 Jul 2008 18:41:15 +0000
Message-Id: <79C7863E-37A9-4988-8BA3-396D1344186D@voxeo.com>
From: Dan York <dyork@voxeo.com>
To: "Elwell, John" <john.elwell@siemens.com>
In-Reply-To: <0D5F89FAC29E2C41B98A6A762007F5D0E09B39@GBNTHT12009MSX.gb002.siemens.net>
Mime-Version: 1.0 (Apple Message framework v924)
Date: Mon, 07 Jul 2008 14:41:14 -0400
References: <0D5F89FAC29E2C41B98A6A762007F5D0E09B39@GBNTHT12009MSX.gb002.siemens.net>
X-Mailer: Apple Mail (2.924)
Cc: sip@ietf.org
Subject: Re: [Sip] draft-elwell-sip-e2e-identity-important-00 posted
X-BeenThere: sip@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: Session Initiation Protocol <sip.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/sip>, <mailto:sip-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:sip@ietf.org>
List-Help: <mailto:sip-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/sip>, <mailto:sip-request@ietf.org?subject=subscribe>
Content-Transfer-Encoding: 7bit
Content-Type: text/plain; charset="us-ascii"; Format="flowed"; DelSp="yes"
Sender: sip-bounces@ietf.org
Errors-To: sip-bounces@ietf.org
John, On Jul 7, 2008, at 12:05 PM, Elwell, John wrote: > http://www.ietf.org/internet-drafts/draft-elwell-sip-e2e-identity-import > ant-00.txt > > During the long discussions on SIP Identity, some people have > questioned > the need for end-to-end identity. This draft states why end-to-end > identity and end-to-end authentication are important. Excellent document. Very useful in my opinion to help explain the overall issues. My one comment would be that section 3 is titled "Why end-to-end identification is important" but it isn't really as much about WHY e2e identification is important but more showing various use cases where e2e identification fails (or succeeds but would be broken by RFC 4474). It might be better titled "Examples of identification transmission" or something similar. Thanks for taking the time to write this, Dan -- Dan York, CISSP, Director of Emerging Communication Technology Office of the CTO Voxeo Corporation dyork@voxeo.com Phone: +1-407-455-5859 Skype: danyork http://www.voxeo.com Blogs: http://blogs.voxeo.com http://www.disruptivetelephony.com Build voice applications based on open standards. Find out how at http://www.voxeo.com/free _______________________________________________ Sip mailing list https://www.ietf.org/mailman/listinfo/sip This list is for NEW development of the core SIP Protocol Use sip-implementors@cs.columbia.edu for questions on current sip Use sipping@ietf.org for new developments on the application of sip