Re: [sipcore] #11: H-I does not provide a "stronger security solution for SIP"
Mary Barnes <mary.ietf.barnes@gmail.com> Mon, 30 August 2010 22:10 UTC
Return-Path: <mary.ietf.barnes@gmail.com>
X-Original-To: sipcore@core3.amsl.com
Delivered-To: sipcore@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id EF6633A6A01 for <sipcore@core3.amsl.com>; Mon, 30 Aug 2010 15:10:37 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -102.467
X-Spam-Level:
X-Spam-Status: No, score=-102.467 tagged_above=-999 required=5 tests=[AWL=0.132, BAYES_00=-2.599, USER_IN_WHITELIST=-100]
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 rMjumqr5vnfw for <sipcore@core3.amsl.com>; Mon, 30 Aug 2010 15:10:29 -0700 (PDT)
Received: from mail-iw0-f172.google.com (mail-iw0-f172.google.com [209.85.214.172]) by core3.amsl.com (Postfix) with ESMTP id 5020D3A6A03 for <sipcore@ietf.org>; Mon, 30 Aug 2010 15:10:26 -0700 (PDT)
Received: by iwn3 with SMTP id 3so5735959iwn.31 for <sipcore@ietf.org>; Mon, 30 Aug 2010 15:10:51 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=domainkey-signature:mime-version:received:received:in-reply-to :references:date:message-id:subject:from:to:cc:content-type :content-transfer-encoding; bh=wbaQcE1Ta1ORn8lAOljAnaDQq7ZYgdh/0M2gehOaWdA=; b=OyX5m+qGjAAwMaPFRNgMZOLaPql3hSY0YMXO8neB3L4kRePuhdHszt/u84iEEXlziH dBSb1tF1osS2Ou7GG4sMmubA6yblrsgwBhnksnFMtTYckZiUd/aBOf9UafNtQSk/jkJ/ WNjxSPP5sTcPFWtQJJ0q+Y4hYJT5S85fYnCMk=
DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma; h=mime-version:in-reply-to:references:date:message-id:subject:from:to :cc:content-type:content-transfer-encoding; b=lMzJeN/JS6aPUEK2OkMX6bWvFHxE8+doez+Uat/UBnRKlSbfWxBMzAO9nizdVIALzA NDNPJwOXxZGb+GTbuKlkILo+Z4YEorkqV1qxZKWAndTEYHx1iGns0sqfs86BGhNUiWPT npRPFLG6KlsPNEUAqhfU8A9KQ4M+VPW+Xk4Pw=
MIME-Version: 1.0
Received: by 10.231.19.3 with SMTP id y3mr6006948iba.156.1283206251220; Mon, 30 Aug 2010 15:10:51 -0700 (PDT)
Received: by 10.231.169.14 with HTTP; Mon, 30 Aug 2010 15:10:51 -0700 (PDT)
In-Reply-To: <064.aeb13ec56f57e8ab9861b50c3aecd1ed@tools.ietf.org>
References: <064.aeb13ec56f57e8ab9861b50c3aecd1ed@tools.ietf.org>
Date: Mon, 30 Aug 2010 17:10:51 -0500
Message-ID: <AANLkTi=VU1jw8U47_vMfpaeEbeNX1QsutdgBbX7TfNhz@mail.gmail.com>
From: Mary Barnes <mary.ietf.barnes@gmail.com>
To: Hadriel Kaplan <HKaplan@acmepacket.com>
Content-Type: text/plain; charset="windows-1252"
Content-Transfer-Encoding: quoted-printable
Cc: SIPCORE <sipcore@ietf.org>
Subject: Re: [sipcore] #11: H-I does not provide a "stronger security solution for SIP"
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: Mon, 30 Aug 2010 22:10:39 -0000
Yeah - another 4244 leftover when there was the misguided idea that we could actually use this to help with the m2m and m2e SIP security issues. I'll remove. On Mon, Aug 30, 2010 at 1:39 PM, sipcore issue tracker <trac@tools.ietf.org> wrote: > #11: H-I does not provide a "stronger security solution for SIP" > ------------------------------------+--------------------------------------- > Reporter: hkaplan@… | Owner: > Type: defect | Status: new > Priority: minor | Milestone: milestone1 > Component: rfc4244bis | Version: 2.0 > Severity: In WG Last Call | Keywords: > ------------------------------------+--------------------------------------- > Section 3 has the following bullet point: > o A stronger security solution for SIP. A side effect is that each > proxy that captures the "request history" information in a secure > manner provides an additional means (without requiring signed > keys) for the original requestor to be assured that the request > was properly retargeted. > > That should be removed, since it's not true. > > -- > Ticket URL: <http://trac.tools.ietf.org/wg/sipcore/trac/ticket/11> > sipcore <http://tools.ietf.org/sipcore/> > > _______________________________________________ > sipcore mailing list > sipcore@ietf.org > https://www.ietf.org/mailman/listinfo/sipcore >
- [sipcore] #11: H-I does not provide a "stronger s… sipcore issue tracker
- Re: [sipcore] #11: H-I does not provide a "strong… Mary Barnes