Re: Advancing the Protocol and Morin Drafts

Robert Raszuk <raszuk@juniper.net> Wed, 08 October 2008 00:13 UTC

Return-Path: <l3vpn-bounces@ietf.org>
X-Original-To: l3vpn-archive@megatron.ietf.org
Delivered-To: ietfarch-l3vpn-archive@core3.amsl.com
Received: from [127.0.0.1] (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id C8C2F3A684F; Tue, 7 Oct 2008 17:13:26 -0700 (PDT)
X-Original-To: l3vpn@core3.amsl.com
Delivered-To: l3vpn@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id 0C0263A6768 for <l3vpn@core3.amsl.com>; Tue, 7 Oct 2008 17:13:25 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -6.217
X-Spam-Level:
X-Spam-Status: No, score=-6.217 tagged_above=-999 required=5 tests=[AWL=0.382, BAYES_00=-2.599, RCVD_IN_DNSWL_MED=-4]
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 MhLY+If4C+8r for <l3vpn@core3.amsl.com>; Tue, 7 Oct 2008 17:13:24 -0700 (PDT)
Received: from exprod7og109.obsmtp.com (exprod7og109.obsmtp.com [64.18.2.171]) by core3.amsl.com (Postfix) with ESMTP id B84433A684F for <l3vpn@ietf.org>; Tue, 7 Oct 2008 17:12:57 -0700 (PDT)
Received: from source ([66.129.228.6]) by exprod7ob109.postini.com ([64.18.6.12]) with SMTP; Tue, 07 Oct 2008 17:13:21 PDT
Received: from p-emlb02-sac.jnpr.net ([66.129.254.47]) by p-emsmtp02.jnpr.net with Microsoft SMTPSVC(6.0.3790.3959); Tue, 7 Oct 2008 17:08:07 -0700
Received: from emailsmtp55.jnpr.net ([172.24.18.132]) by p-emlb02-sac.jnpr.net with Microsoft SMTPSVC(6.0.3790.3959); Tue, 7 Oct 2008 17:08:07 -0700
Received: from magenta.juniper.net ([172.17.27.123]) by emailsmtp55.jnpr.net with Microsoft SMTPSVC(6.0.3790.1830); Tue, 7 Oct 2008 17:08:06 -0700
Received: from [172.26.250.98] ([172.26.250.98]) by magenta.juniper.net (8.11.3/8.11.3) with ESMTP id m98085M41266; Tue, 7 Oct 2008 17:08:05 -0700 (PDT) (envelope-from raszuk@juniper.net)
Message-ID: <48EBF9E0.7040204@juniper.net>
Date: Tue, 07 Oct 2008 17:08:00 -0700
From: Robert Raszuk <raszuk@juniper.net>
User-Agent: Thunderbird 2.0.0.17 (Windows/20080914)
MIME-Version: 1.0
To: IJsbrand Wijnands <ice@cisco.com>
Subject: Re: Advancing the Protocol and Morin Drafts
References: <A834346E-E29F-4CD5-94AF-D6B99D1E2D42@multicasttech.com><1222877148.28824.45.camel@l-at11168.FTRD> <81F49736-BA49-4CBC-9437-BEC475B3E53F@cisco.com> <2F1DE4DFCFF32144B771BD2C246E6A20A5F2B4@misout7msgusr7e.ugd.att.com> <ACD7CB73-685B-4921-BC79-D4BCA37982DB@cisco.com>
In-Reply-To: <ACD7CB73-685B-4921-BC79-D4BCA37982DB@cisco.com>
Content-Type: text/plain; charset="ISO-8859-1"; format="flowed"
Content-Transfer-Encoding: 7bit
X-OriginalArrivalTime: 08 Oct 2008 00:08:06.0916 (UTC) FILETIME=[F0C3FC40:01C928D9]
Cc: Ross Callon <rcallon@juniper.net>, Thomas Morin <thomas.morin@orange-ftgroup.com>, l3vpn@ietf.org, David Ward <dward@cisco.com>
X-BeenThere: l3vpn@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
Reply-To: raszuk@juniper.net
List-Id: <l3vpn.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/l3vpn>, <mailto:l3vpn-request@ietf.org?subject=unsubscribe>
List-Archive: <https://www.ietf.org/mailman/private/l3vpn>
List-Post: <mailto:l3vpn@ietf.org>
List-Help: <mailto:l3vpn-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/l3vpn>, <mailto:l3vpn-request@ietf.org?subject=subscribe>
Sender: l3vpn-bounces@ietf.org
Errors-To: l3vpn-bounces@ietf.org

Hey Ice,

Wonderful analogy !!!

> 1. By listing what is a MUST does not guarantee interoperable solutions. 
> Its like giving the ingredients for baking a pie, without saying how to 
> put it together. As a result you'll see many different pie's and you'll 
> be surprised how many variations are possible.

Is this a good thing or bad thing ? After all variations in pie making 
should be encouraged. This is what make the taste or service really 
good. Do you like to have the same taste of a pie when you go to a 
different restaurant ?

Have you ever seen a real chef who opens a cook-book to cook ? If he is 
a good one he knows how to cook by heart.

With this in mind let's don't underestimate the skills of our customers. 
  In my opinion ISPs and service providers can cook really well just 
with ingredients they possess. They do not need to be told how to 
engineer their networks by any vendor or IETF. If anything is missing 
they will surely ask for it either you and me.

So since you agree and admit that you can end up with a pie(s) based on 
current ingredients I really don't see why we should cut the imagination 
on how to mix them together :).

Cheers,
R.

PS. It beats me why you have not used the "pudding" analogy :)))