Re: [Isis-wg] I-D Action:draft-ietf-isis-layer2-05.txt

Robert Raszuk <raszuk@cisco.com> Wed, 05 May 2010 23:07 UTC

Return-Path: <raszuk@cisco.com>
X-Original-To: isis-wg@core3.amsl.com
Delivered-To: isis-wg@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id 1FE9B3A68D4 for <isis-wg@core3.amsl.com>; Wed, 5 May 2010 16:07:34 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -8.262
X-Spam-Level:
X-Spam-Status: No, score=-8.262 tagged_above=-999 required=5 tests=[AWL=-0.077, BAYES_40=-0.185, RCVD_IN_DNSWL_HI=-8]
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 uBAXIBc0cIax for <isis-wg@core3.amsl.com>; Wed, 5 May 2010 16:07:33 -0700 (PDT)
Received: from sj-iport-1.cisco.com (sj-iport-1.cisco.com [171.71.176.70]) by core3.amsl.com (Postfix) with ESMTP id 6783028C17D for <isis-wg@ietf.org>; Wed, 5 May 2010 16:07:32 -0700 (PDT)
Authentication-Results: sj-iport-1.cisco.com; dkim=neutral (message not signed) header.i=none
X-IronPort-Anti-Spam-Filtered: true
X-IronPort-Anti-Spam-Result: AvsEALaW4UurR7Hu/2dsb2JhbACdV3GkSIFjCwGXa4UTBA
X-IronPort-AV: E=Sophos;i="4.52,337,1270425600"; d="scan'208";a="323436379"
Received: from sj-core-5.cisco.com ([171.71.177.238]) by sj-iport-1.cisco.com with ESMTP; 05 May 2010 23:07:19 +0000
Received: from [192.168.1.61] (sjc-raszuk-87113.cisco.com [10.20.147.254]) by sj-core-5.cisco.com (8.13.8/8.14.3) with ESMTP id o45N7IA3022723; Wed, 5 May 2010 23:07:18 GMT
Message-ID: <4BE1FA23.5010209@cisco.com>
Date: Thu, 06 May 2010 01:07:15 +0200
From: Robert Raszuk <raszuk@cisco.com>
User-Agent: Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US; rv:1.9.1.9) Gecko/20100317 Thunderbird/3.0.4
MIME-Version: 1.0
To: isis-wg@ietf.org, david.i.allan@ericsson.com
References: <60C093A41B5E45409A19D42CF7786DFD4F9AAE46AB@EUSAACMS0703.eamcs.ericsson.se> <7197B78D-D549-42E6-ABE7-0F5814E0C6B5@cisco.com> <8874F6219396A04CA291C90CCD7F9C070CE88927@xmb-sjc-213.amer.cisco.com> <60C093A41B5E45409A19D42CF7786DFD4F9AAE4D47@EUSAACMS0703.eamcs.ericsson.se>
In-Reply-To: <60C093A41B5E45409A19D42CF7786DFD4F9AAE4D47@EUSAACMS0703.eamcs.ericsson.se>
Content-Type: text/plain; charset="ISO-8859-1"; format="flowed"
Content-Transfer-Encoding: 7bit
Subject: Re: [Isis-wg] I-D Action:draft-ietf-isis-layer2-05.txt
X-BeenThere: isis-wg@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
Reply-To: raszuk@cisco.com
List-Id: IETF IS-IS working group <isis-wg.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/isis-wg>, <mailto:isis-wg-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/isis-wg>
List-Post: <mailto:isis-wg@ietf.org>
List-Help: <mailto:isis-wg-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/isis-wg>, <mailto:isis-wg-request@ietf.org?subject=subscribe>
X-List-Received-Date: Wed, 05 May 2010 23:07:34 -0000

Hi David,

I think there is nothing wrong with shipping pre-standard 
implementations of any protocol.

Of course vendor takes a risk here if by going via standards process the 
spec will change based on the input from WG. Then he has to worry about 
interoperability issues with his pre-standard implementation.

Remember how tag switching surfaced ?

If you want to go this path I am sure you are very well aware that there 
is a really long list from any vendor to publish a draft when an 
implementation is ready.

I don't want to start any sort of flame war here on that. But I think 
this was never a showstopper in IETF to have an implementation. Of 
course authors can not use it as justification of any sort and here I am 
with you and others.

So considering both drafts on the table I think draft-hasmit-otv-00 is a 
very good individual contribution which does in fact has a lot of 
technical merit.

On the draft of draft-ietf-isis-layer2-05.txt I think the best way would 
be to indeed separate the new encoding into a separate draft, submit as 
individual contribution (there is still some time before next IETF in 
Maastricht and ask for agenda item on this or other WG to present.

Would you and other's agree that this could be the best way out from 
this thread ?

Cheers,
R.


> Hi Victor:
> This is not progress and innovation, this is simply */bad behavior/* and
> as such should not be rewarded....
> Please go away and publish something informational track and request
> your own IANA code points if you are now so genuinely concerned about
> the "common good", you obviously weren't when you started shipping....
> D