Re: Comments on draft-carpenter-newtrk-questions-00.txt

Pekka Savola <pekkas@netcore.fi> Thu, 13 July 2006 18:41 UTC

Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com) by megatron.ietf.org with esmtp (Exim 4.43) id 1G167r-0005SG-E9; Thu, 13 Jul 2006 14:41:27 -0400
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org) by megatron.ietf.org with esmtp (Exim 4.43) id 1G167p-0005Rx-Vb for ietf@ietf.org; Thu, 13 Jul 2006 14:41:25 -0400
Received: from stsc1260-eth-s1-s1p1-vip.va.neustar.com ([156.154.16.129] helo=chiedprmail1.ietf.org) by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1G0z8O-0006FM-1n for ietf@ietf.org; Thu, 13 Jul 2006 07:13:32 -0400
Received: from netcore.fi ([193.94.160.1]) by chiedprmail1.ietf.org with esmtp (Exim 4.43) id 1G0yzM-00045W-AF for ietf@ietf.org; Thu, 13 Jul 2006 07:04:13 -0400
Received: from localhost (pekkas@localhost) by netcore.fi (8.12.11.20060614/8.12.11) with ESMTP id k6DB3pDh030029; Thu, 13 Jul 2006 14:03:51 +0300
Date: Thu, 13 Jul 2006 14:03:51 +0300
From: Pekka Savola <pekkas@netcore.fi>
To: Eliot Lear <lear@cisco.com>
In-Reply-To: <44B5EC23.6090303@cisco.com>
Message-ID: <Pine.LNX.4.64.0607131354310.29691@netcore.fi>
References: <p06300025c0db326985f9@[142.131.134.210]> <2278C088-133C-4353-9CF1-AC47899ED409@cisco.com> <44B5EC23.6090303@cisco.com>
MIME-Version: 1.0
Content-Type: TEXT/PLAIN; charset="US-ASCII"; format="flowed"
X-Virus-Scanned: ClamAV 0.88.2/1594/Wed Jul 12 18:04:34 2006 on otso.netcore.fi
X-Virus-Status: Clean
X-Spam-Status: No, score=-2.4 required=5.0 tests=AWL,BAYES_00,NO_RELAYS autolearn=ham version=3.1.2
X-Spam-Checker-Version: SpamAssassin 3.1.2 (2006-05-25) on otso.netcore.fi
X-Spam-Score: -2.5 (--)
X-Scan-Signature: 52e1467c2184c31006318542db5614d5
Cc: Randall Gellens <randy@qualcomm.com>, Iljitsch van Beijnum <iljitsch@muada.com>, Fred Baker <fred@cisco.com>, ietf@ietf.org
Subject: Re: Comments on draft-carpenter-newtrk-questions-00.txt
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
Errors-To: ietf-bounces@ietf.org

On Thu, 13 Jul 2006, Eliot Lear wrote:
> By RFC, not by STD (obviously):
>
> Status	1999	2000	2001	2002	2003	2004	2005
> -------------------------------------------------------------
> PS	102	119	71	105	103	131	169
> DRAFT	6	6	2	4	7	7	3
...
> I believe there are two reasons for the huge gap between PS 
> and DRAFT:
>
> - it's difficult to get there (interop requirements, picking out
>   uncommonly used features, etc)

A part of that might also be caused by normative references problems. 
I don't think we have much data on that as we haven't run an 
experiment (yet).

> - nobody wants or needs to do the work (what GM in her right
>   mind would want her experts working on something that neither
>   generates new features nor fixes product bugs)

Some of this would in fact usually be documenting the product bugs 
that were caused by ambiguous or incorrect specification.  You're 
right that once you've figured out a way to fix a spec problem in YOUR 
implementation, there may be marginal interest in fixing it in the 
spec.  However, I believe doing so will reduce the load on customer 
support (and ultimately also engineering which will need to answer the 
escalated support issues), because many of the support issues are 
actually caused by interoperability between different products or 
vendors.

-- 
Pekka Savola                 "You each name yourselves king, yet the
Netcore Oy                    kingdom bleeds."
Systems. Networks. Security. -- George R.R. Martin: A Clash of Kings

_______________________________________________
Ietf mailing list
Ietf@ietf.org
https://www1.ietf.org/mailman/listinfo/ietf