Re: [MMUSIC] Coding from examples [was Re: I-D Action:draft-ietf-mmusic-ice-tcp-09.txt]

Ari Keranen <ari.keranen@nomadiclab.com> Fri, 03 September 2010 20:27 UTC

Return-Path: <ari.keranen@nomadiclab.com>
X-Original-To: mmusic@core3.amsl.com
Delivered-To: mmusic@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id 59BEF3A65A5 for <mmusic@core3.amsl.com>; Fri, 3 Sep 2010 13:27:50 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.509
X-Spam-Level:
X-Spam-Status: No, score=-2.509 tagged_above=-999 required=5 tests=[AWL=0.090, BAYES_00=-2.599]
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 xWBTgPec3Yk4 for <mmusic@core3.amsl.com>; Fri, 3 Sep 2010 13:27:49 -0700 (PDT)
Received: from gw.nomadiclab.com (unknown [IPv6:2001:14b8:400:101::2]) by core3.amsl.com (Postfix) with ESMTP id B97033A6781 for <mmusic@ietf.org>; Fri, 3 Sep 2010 13:27:48 -0700 (PDT)
Received: from localhost (localhost [127.0.0.1]) by gw.nomadiclab.com (Postfix) with ESMTP id 5C7194E6D5 for <mmusic@ietf.org>; Fri, 3 Sep 2010 23:28:14 +0300 (EEST)
X-Virus-Scanned: amavisd-new at nomadiclab.com
Received: from gw.nomadiclab.com ([127.0.0.1]) by localhost (inside.nomadiclab.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id UNa533MYVpjn for <mmusic@ietf.org>; Fri, 3 Sep 2010 23:28:13 +0300 (EEST)
Received: from [127.0.0.1] (localhost [IPv6:::1]) by gw.nomadiclab.com (Postfix) with ESMTP id 0FA084E6CF for <mmusic@ietf.org>; Fri, 3 Sep 2010 23:28:11 +0300 (EEST)
Message-ID: <4C815A82.6080405@nomadiclab.com>
Date: Fri, 03 Sep 2010 23:28:50 +0300
From: Ari Keranen <ari.keranen@nomadiclab.com>
User-Agent: Mozilla/5.0 (Windows; U; Windows NT 6.1; fi; rv:1.9.2.8) Gecko/20100802 Lightning/1.0b2 Thunderbird/3.1.2
MIME-Version: 1.0
To: mmusic@ietf.org
References: <20100902110001.7AC493A68EF@core3.amsl.com> <4C7F8451.8050502@nomadiclab.com> <4C7F97E1.9080704@viagenie.ca> <028201cb4af7$1cc4d3f0$564e7bd0$@com> <4C80EB20.4040007@viagenie.ca> <4C812C2B.5040306@acm.org>
In-Reply-To: <4C812C2B.5040306@acm.org>
Content-Type: text/plain; charset="ISO-8859-1"; format="flowed"
Content-Transfer-Encoding: 7bit
Subject: Re: [MMUSIC] Coding from examples [was Re: I-D Action:draft-ietf-mmusic-ice-tcp-09.txt]
X-BeenThere: mmusic@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: Multiparty Multimedia Session Control Working Group <mmusic.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/mmusic>, <mailto:mmusic-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/mmusic>
List-Post: <mailto:mmusic@ietf.org>
List-Help: <mailto:mmusic-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/mmusic>, <mailto:mmusic-request@ietf.org?subject=subscribe>
X-List-Received-Date: Fri, 03 Sep 2010 20:27:50 -0000

3.9.2010 20:11, Marc Petit-Huguenin wrote:
> On 09/03/2010 05:33 AM, Simon Perreault wrote:
>> On 2010-09-02 19:32, Dan Wing wrote:
>>> In any event, if we're going to do a big example, how about
>>> a real example in draft-ietf-sipping-nat-scenarios, if it
>>> doesn't have it already?
>>
>> I don't care where it is, but we need one. When you're implementing
>> something, you end up looking longer at examples than at the actual
>> spec. It really is extremely useful.
>
> And, in my opinion, terribly wrong.  I personally would ban all examples from
> RFC, because at best they are exposing only a subset of what the RFC describe
> and at worst there is bugs in it, bugs[1] that you will then find in
> implementations.

I agree with Simon that an example would be really useful, but I think 
also Marc is right that having it wrong is likely worse than not having 
it at all.

Since we have a draft (the nat-scenarions one) that is already 
documenting this kind of things, I'd say that would be a better place 
for the example and we can add an informative reference so that 
implementors know where to look at.

Also, the examples in the nat-scenarios draft should probably be run 
through multiple real implementations and still would need disclaimers 
saying "there are probably errors in the examples, so take a look at the 
errata, etc.", but that's a whole other story..


Cheers,
Ari