[sipcore] #3: Gaps in H-I headers should NOT be treated as "malicious"
"sipcore issue tracker" <trac@tools.ietf.org> Wed, 25 August 2010 23:13 UTC
Return-Path: <trac@tools.ietf.org>
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 51A3A3A6A7D for <sipcore@core3.amsl.com>; Wed, 25 Aug 2010 16:13:34 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -102.572
X-Spam-Level:
X-Spam-Status: No, score=-102.572 tagged_above=-999 required=5 tests=[AWL=0.028, BAYES_00=-2.599, NO_RELAYS=-0.001, 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 8eHciDkoCamQ for <sipcore@core3.amsl.com>; Wed, 25 Aug 2010 16:13:33 -0700 (PDT)
Received: from zinfandel.tools.ietf.org (unknown [IPv6:2001:1890:1112:1::2a]) by core3.amsl.com (Postfix) with ESMTP id 3D41B3A695D for <sipcore@ietf.org>; Wed, 25 Aug 2010 16:13:33 -0700 (PDT)
Received: from localhost ([::1] helo=zinfandel.tools.ietf.org) by zinfandel.tools.ietf.org with esmtp (Exim 4.72) (envelope-from <trac@tools.ietf.org>) id 1OoPAT-0007PV-M7; Wed, 25 Aug 2010 16:14:05 -0700
MIME-Version: 1.0
Content-Type: text/plain; charset="utf-8"
Content-Transfer-Encoding: 8bit
From: sipcore issue tracker <trac@tools.ietf.org>
X-Trac-Version: 0.11.7
Precedence: bulk
Auto-Submitted: auto-generated
X-Mailer: Trac 0.11.7, by Edgewall Software
To: hkaplan@acmepacket.com
X-Trac-Project: sipcore
Date: Wed, 25 Aug 2010 23:14:05 -0000
X-URL: http://tools.ietf.org/sipcore/
X-Trac-Ticket-URL: https://svn.tools.ietf.org/wg/sipcore/trac/ticket/3
Message-ID: <064.927cdf52c269bae5a1d26525c0af4d34@tools.ietf.org>
X-Trac-Ticket-ID: 3
X-SA-Exim-Connect-IP: ::1
X-SA-Exim-Rcpt-To: hkaplan@acmepacket.com, sipcore@ietf.org
X-SA-Exim-Mail-From: trac@tools.ietf.org
X-SA-Exim-Scanned: No (on zinfandel.tools.ietf.org); SAEximRunCond expanded to false
Cc: sipcore@ietf.org
Subject: [sipcore] #3: Gaps in H-I headers should NOT be treated as "malicious"
X-BeenThere: sipcore@ietf.org
X-Mailman-Version: 2.1.9
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, 25 Aug 2010 23:13:34 -0000
#3: Gaps in H-I headers should NOT be treated as "malicious" ------------------------------------+--------------------------------------- Reporter: hkaplan@… | Owner: Type: defect | Status: new Priority: major | Milestone: milestone1 Component: rfc4244bis | Version: 2.0 Severity: In WG Last Call | Keywords: ------------------------------------+--------------------------------------- Section 4.1 and 4.2.1 both say "The entries SHOULD be evaluated to determine gaps in indices, which could indicate that an entry has been maliciously removed." That's a bad SHOULD. First, because it doesn't actually tell you what to do if they're missing. Second, because if missing indeces actually cause a request failure, that's a good way of guaranteeing people won't use hist-info or will delete ALL the entries just to make calls work. Third, because it's highly unlikely to actually be due to "malicious" reasons - if someone wants to "maliciously" remove them, they'll delete them all, or change them all, etc. It's more likely they were removed for security/privacy reasons. Please remove this sentence from both sections. In fact, maybe a sentence should be added to remind people missing indeces are possible and OK. (i.e., MUST NOT cause a request faiure) -- Ticket URL: <https://svn.tools.ietf.org/wg/sipcore/trac/ticket/3> sipcore <http://tools.ietf.org/sipcore/>
- [sipcore] #3: Gaps in H-I headers should NOT be t… sipcore issue tracker
- Re: [sipcore] #3: Gaps in H-I headers should NOT … Mary Barnes