Re: [MEDIACTRL] DISCUSS and COMMENT: draft-ietf-mediactrl-sip-control-framework
Eric Burger <eburger@standardstrack.com> Wed, 07 April 2010 22:57 UTC
Return-Path: <eburger@standardstrack.com>
X-Original-To: mediactrl@core3.amsl.com
Delivered-To: mediactrl@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id 8D3E13A699A for <mediactrl@core3.amsl.com>; Wed, 7 Apr 2010 15:57:05 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.799
X-Spam-Level:
X-Spam-Status: No, score=-1.799 tagged_above=-999 required=5 tests=[AWL=0.801, 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 vdIiB+imRhF8 for <mediactrl@core3.amsl.com>; Wed, 7 Apr 2010 15:57:04 -0700 (PDT)
Received: from gs19.inmotionhosting.com (gs19.inmotionhosting.com [205.134.252.251]) by core3.amsl.com (Postfix) with ESMTP id D21EB3A696C for <mediactrl@ietf.org>; Wed, 7 Apr 2010 15:57:04 -0700 (PDT)
Received: from ip68-100-199-8.dc.dc.cox.net ([68.100.199.8] helo=[192.168.15.105]) by gs19.inmotionhosting.com with esmtpsa (TLSv1:AES128-SHA:128) (Exim 4.69) (envelope-from <eburger@standardstrack.com>) id 1Nze9w-0006rl-I8; Wed, 07 Apr 2010 15:55:44 -0700
Mime-Version: 1.0 (Apple Message framework v1078)
Content-Type: text/plain; charset="us-ascii"
From: Eric Burger <eburger@standardstrack.com>
In-Reply-To: <20100405120916.4158A3A6967@core3.amsl.com>
Date: Wed, 07 Apr 2010 18:56:57 -0400
Content-Transfer-Encoding: quoted-printable
Message-Id: <8AFDDCFE-548F-4753-9922-D9F25A1B90C9@standardstrack.com>
References: <20100405120916.4158A3A6967@core3.amsl.com>
To: draft-ietf-mediactrl-sip-control-framework@tools.ietf.org
X-Mailer: Apple Mail (2.1078)
X-AntiAbuse: This header was added to track abuse, please include it with any abuse report
X-AntiAbuse: Primary Hostname - gs19.inmotionhosting.com
X-AntiAbuse: Original Domain - ietf.org
X-AntiAbuse: Originator/Caller UID/GID - [47 12] / [47 12]
X-AntiAbuse: Sender Address Domain - standardstrack.com
X-Source:
X-Source-Args:
X-Source-Dir:
Cc: mediactrl@ietf.org
Subject: Re: [MEDIACTRL] DISCUSS and COMMENT: draft-ietf-mediactrl-sip-control-framework
X-BeenThere: mediactrl@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: Media Control WG Discussion List <mediactrl.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/mediactrl>, <mailto:mediactrl-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/mediactrl>
List-Post: <mailto:mediactrl@ietf.org>
List-Help: <mailto:mediactrl-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/mediactrl>, <mailto:mediactrl-request@ietf.org?subject=subscribe>
X-List-Received-Date: Wed, 07 Apr 2010 22:57:05 -0000
Did we really mean to say that SIP digest will protect the CONTROL channel? Is this simply an oversight? On Apr 5, 2010, at 8:09 AM, Alexey Melnikov wrote: > 12.3. Control Channel Policy Management > > It can be determined that access to resources and use of control > channels relates to policy. It can be considered implementation and > deployment detail that dictates the level of policy that is adopted. > The authorization and associated policy of a control channel can be > linked to the authentication mechanisms described in this section. > For example, strictly authenticating a control channel either using > SIP digest or TLS authentication allows entities to protect resources > > I am confused about how this is relevant in this case. > Can you please show an example of how a control channel can be authenticated using SIP digest? > > and ensure the required level of granularity.
- Re: [MEDIACTRL] DISCUSS and COMMENT: draft-ietf-m… Eric Burger
- Re: [MEDIACTRL] DISCUSS and COMMENT: draft-ietf-m… Chris Boulton