[sipcore] #1: Editorial: section 3 is not an "Overview of Operations"

"sipcore issue tracker" <trac@tools.ietf.org> Wed, 25 August 2010 22:18 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 B0AFC3A63C9 for <sipcore@core3.amsl.com>; Wed, 25 Aug 2010 15:18:42 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -102.571
X-Spam-Level:
X-Spam-Status: No, score=-102.571 tagged_above=-999 required=5 tests=[AWL=0.029, 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 6-KoHxcGbImm for <sipcore@core3.amsl.com>; Wed, 25 Aug 2010 15:18:41 -0700 (PDT)
Received: from zinfandel.tools.ietf.org (unknown [IPv6:2001:1890:1112:1::2a]) by core3.amsl.com (Postfix) with ESMTP id B2B4A3A6801 for <sipcore@ietf.org>; Wed, 25 Aug 2010 15:18:41 -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 1OoOJN-0004DE-TT; Wed, 25 Aug 2010 15:19:13 -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 22:19:13 -0000
X-URL: http://tools.ietf.org/sipcore/
X-Trac-Ticket-URL: http://trac.tools.ietf.org/wg/sipcore/trac/ticket/1
Message-ID: <064.44026b0cd1e09234b3fd675a6b1dedb0@tools.ietf.org>
X-Trac-Ticket-ID: 1
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
X-Mailman-Approved-At: Wed, 25 Aug 2010 15:21:03 -0700
Cc: sipcore@ietf.org
Subject: [sipcore] #1: Editorial: section 3 is not an "Overview of Operations"
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 22:18:42 -0000

#1: Editorial: section 3 is not an "Overview of Operations"
------------------------------------+---------------------------------------
 Reporter:  hkaplan@…               |       Owner:            
     Type:  defect                  |      Status:  new       
 Priority:  minor                   |   Milestone:  milestone1
Component:  rfc4244bis              |     Version:  2.0       
 Severity:  In WG Last Call         |    Keywords:            
------------------------------------+---------------------------------------
 Section 3 is titled "Overview of Operations".  Of its 4 pages, it has
 about two or three paragraphs which might actually qualify for that title.
 It has about 2 pages of rationale for why the mechanism exists/is-needed,
 and another couple pages of an example description and call flow diagram.
 So... move the first page and a half to a "Background" or "Motivation"
 section (or just delete it).  In fact, ISTM this is the text of the
 original rfc4424's "Background" section.

 The rest of it is still not really an overview of operations, except by-
 example I guess.  What's needed is some text providing an overview of
 operations.

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