[sipcore] #17: Unclear phrasing

"sipcore issue tracker" <trac@tools.ietf.org> Tue, 31 August 2010 17:17 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 BBC7A3A6A2B for <sipcore@core3.amsl.com>; Tue, 31 Aug 2010 10:17:55 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -102.573
X-Spam-Level:
X-Spam-Status: No, score=-102.573 tagged_above=-999 required=5 tests=[AWL=0.027, 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 KhXfWsQ4XUdu for <sipcore@core3.amsl.com>; Tue, 31 Aug 2010 10:17:47 -0700 (PDT)
Received: from zinfandel.tools.ietf.org (unknown [IPv6:2001:1890:1112:1::2a]) by core3.amsl.com (Postfix) with ESMTP id 28BB03A699A for <sipcore@ietf.org>; Tue, 31 Aug 2010 10:17:45 -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 1OqUTO-0005eI-CZ; Tue, 31 Aug 2010 10:18:14 -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: worley@alum.mit.edu
X-Trac-Project: sipcore
Date: Tue, 31 Aug 2010 17:18:14 -0000
X-URL: http://tools.ietf.org/sipcore/
X-Trac-Ticket-URL: http://trac.tools.ietf.org/wg/sipcore/trac/ticket/17
Message-ID: <061.46e77c58ddcdfff893364cde58564820@tools.ietf.org>
X-Trac-Ticket-ID: 17
X-SA-Exim-Connect-IP: ::1
X-SA-Exim-Rcpt-To: worley@alum.mit.edu, 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] #17: Unclear phrasing
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: Tue, 31 Aug 2010 17:17:58 -0000

#17: Unclear phrasing
---------------------------------+------------------------------------------
 Reporter:  worley@…             |       Owner:            
     Type:  defect               |      Status:  new       
 Priority:  minor                |   Milestone:  milestone1
Component:  rfc4244bis           |     Version:  2.0       
 Severity:  In WG Last Call      |    Keywords:            
---------------------------------+------------------------------------------
 In section 3 is the odd phrase "any valid response" -- are there
 invalid responses?  What is validity of responses?  Better would be "any
 response", or probably more informatively, "any provisional or final
 response".

-- 
Ticket URL: <http://trac.tools.ietf.org/wg/sipcore/trac/ticket/17>
sipcore <http://tools.ietf.org/sipcore/>