[sipcore] Security Issue

Samir Srivastava <samirs.lists@gmail.com> Wed, 08 December 2010 08:24 UTC

Return-Path: <samirs.lists@gmail.com>
X-Original-To: sipcore@core3.amsl.com
Delivered-To: sipcore@core3.amsl.com
Received: from localhost (localhost []) by core3.amsl.com (Postfix) with ESMTP id 5A36F3A6920 for <sipcore@core3.amsl.com>; Wed, 8 Dec 2010 00:24:12 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -3.098
X-Spam-Status: No, score=-3.098 tagged_above=-999 required=5 tests=[AWL=0.500, BAYES_00=-2.599, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_LOW=-1]
Received: from mail.ietf.org ([]) by localhost (core3.amsl.com []) (amavisd-new, port 10024) with ESMTP id XC5EWYBBDLIV for <sipcore@core3.amsl.com>; Wed, 8 Dec 2010 00:24:09 -0800 (PST)
Received: from mail-iw0-f182.google.com (mail-iw0-f182.google.com []) by core3.amsl.com (Postfix) with ESMTP id 4D1FF3A6894 for <sipcore@ietf.org>; Wed, 8 Dec 2010 00:24:08 -0800 (PST)
Received: by iwn39 with SMTP id 39so1306219iwn.27 for <sipcore@ietf.org>; Wed, 08 Dec 2010 00:25:32 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=domainkey-signature:mime-version:received:received:date:message-id :subject:from:to:content-type; bh=wTGnNczuiX81Yad6BsEVtv3NNrPZQW4KALEPF46N03g=; b=sUGrxWMd/l9u8aG1y4xKLuRs29UoH2NvMluoaAKKDI77gReFpGvfJRh2mBpiwpft6m ovv4sBkHH+JnoMVWPWG7omZZQ3bvX7fwTMMyqJRqY3I04eEOL9whMa5zvDS8mdhE8O+n McGTOCn6XqILKH4v6LAvOmoczzZN4lu5x4woY=
DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma; h=mime-version:date:message-id:subject:from:to:content-type; b=ie4RYM4Bxebdutdw1GuPJaRtlStAxhxpCGR83ezJOe1T0QLoRne8er/hFud7Xjhieq v4sv7eoHPfmlSY/77AC/Xp3ZbEO2TZrcbmnLnKYORgkeQMOOEjIsycMHGUTJFMWSmVGX c6thFG7m0OefA1mRDZrk4sTPT9MVz+D0VjWas=
MIME-Version: 1.0
Received: by with SMTP id t3mr8778030iba.174.1291796732568; Wed, 08 Dec 2010 00:25:32 -0800 (PST)
Received: by with HTTP; Wed, 8 Dec 2010 00:25:32 -0800 (PST)
Date: Wed, 8 Dec 2010 00:25:32 -0800
Message-ID: <AANLkTinEk6VpQYKoNHPhowv69-7V1KwDgC1o9sbQjssU@mail.gmail.com>
From: Samir Srivastava <samirs.lists@gmail.com>
To: sipcore@ietf.org
Content-Type: multipart/alternative; boundary=0003255758de5de7690496e1dd50
Subject: [sipcore] Security Issue
X-BeenThere: sipcore@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: SIP Core Working Group <sipcore.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/sipcore>, <mailto:sipcore-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/sipcore>
List-Post: <mailto:sipcore@ietf.org>
List-Help: <mailto:sipcore-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/sipcore>, <mailto:sipcore-request@ietf.org?subject=subscribe>
X-List-Received-Date: Wed, 08 Dec 2010 08:24:12 -0000


  I am getting active after a long pause. Trying to figure out the details.

  I posted earlier on the SIP Implementors regarding the

  1)  security for other URI such as IM, PRES, TEL
  2)  feature control such as presence information sent over the secure
channel is distributed over the unsecure channel.
  3)  Alongwith other issues, which I was pointing earlier on the list.

  Does anybody has answer to 1) and 2) or not or what is the plan?
  Paul, Dale other folks active here and active there too. I was expecting
it might have resolved either way to know the result.

Samir Srivastava