Re: [GROW] IPR Disclosure: Huawei Technologies Co., Ltd's Statement about IPR related to draft-ietf-grow-va-02

"Joel M. Halpern" <jmh@joelhalpern.com> Thu, 24 June 2010 15:32 UTC

Return-Path: <jmh@joelhalpern.com>
X-Original-To: grow@core3.amsl.com
Delivered-To: grow@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id BBF6F3A69F1 for <grow@core3.amsl.com>; Thu, 24 Jun 2010 08:32:35 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.599
X-Spam-Level:
X-Spam-Status: No, score=-2.599 tagged_above=-999 required=5 tests=[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 HZoTr1fXw8Di for <grow@core3.amsl.com>; Thu, 24 Jun 2010 08:32:30 -0700 (PDT)
Received: from hgblob.mail.tigertech.net (hgblob.mail.tigertech.net [64.62.209.71]) by core3.amsl.com (Postfix) with ESMTP id 5C8DC3A6A45 for <grow@ietf.org>; Thu, 24 Jun 2010 08:32:30 -0700 (PDT)
Received: from localhost (localhost [127.0.0.1]) by hgblob.tigertech.net (Postfix) with ESMTP id 82C6332365D0; Thu, 24 Jun 2010 08:32:33 -0700 (PDT)
X-Virus-Scanned: Debian amavisd-new at hgblob.tigertech.net
Received: from [192.168.1.3] (pool-173-66-82-72.washdc.fios.verizon.net [173.66.82.72]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (No client certificate requested) by hgblob.tigertech.net (Postfix) with ESMTPSA id EE67632365CF; Thu, 24 Jun 2010 08:32:32 -0700 (PDT)
Message-ID: <4C237A8F.5020705@joelhalpern.com>
Date: Thu, 24 Jun 2010 11:32:31 -0400
From: "Joel M. Halpern" <jmh@joelhalpern.com>
User-Agent: Thunderbird 2.0.0.24 (Windows/20100228)
MIME-Version: 1.0
To: Christopher Morrow <christopher.morrow@gmail.com>
References: <20100623193156.A78563A6B07@core3.amsl.com> <AANLkTimfIFcDUScuCKCYQBBkcu-WIYLVupruIM7TAPWK@mail.gmail.com> <OFD3C5ACA1.C7FC2E4B-ONC125774C.0027E684-C125774C.002B01E7@notes.mpi-sb.mpg.de> <AANLkTimu3UA76zGXu81kd_0uLW32gp8BMThYo7yGm4dU@mail.gmail.com>
In-Reply-To: <AANLkTimu3UA76zGXu81kd_0uLW32gp8BMThYo7yGm4dU@mail.gmail.com>
Content-Type: text/plain; charset="ISO-8859-1"; format="flowed"
Content-Transfer-Encoding: 7bit
Cc: grow@ietf.org, dromasca@avaya.com
Subject: Re: [GROW] IPR Disclosure: Huawei Technologies Co., Ltd's Statement about IPR related to draft-ietf-grow-va-02
X-BeenThere: grow@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: Grow Working Group Mailing List <grow.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/grow>, <mailto:grow-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/grow>
List-Post: <mailto:grow@ietf.org>
List-Help: <mailto:grow-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/grow>, <mailto:grow-request@ietf.org?subject=subscribe>
X-List-Received-Date: Thu, 24 Jun 2010 15:32:36 -0000

While autoconfig is not "necessary" in order to have a working VA 
system, I think it (some form of autoconfig) is necessary in order to 
have a deployable and operable VA system.  Given that GROW is supposed 
to be focussed on operability, I am not at all sure we should drop 
autoconfig.

{For context, the many concern I heard expressed at the early grow 
presentations was concern that the complexity of configuration made the 
system error prone and sufficient expensive, in terms of operational 
cost, that it woudl cost more than it would save.)

Yours,
Joel

Christopher Morrow wrote:
> On Thu, Jun 24, 2010 at 3:49 AM, Paul Francis <francis@mpi-sws.org> wrote:
>> As it was, I was about to ask the list if folks thought VA could move
>> towards an informational RFC, or if folks felt that more implementation
>> experience were needed.  Currently we have a linux/quagga implementation
>> that does not include MPLS tunneling.  I'm not sure the status of the
>> Huawei implementation, but it is not to the point where it can be tested
>> against the linux implementation.  In any event, VA doesn't require
>> wire-protocol changes, and I can well imagine that only once folks start
>> trying to deploy it will we really learn what configurations work best (at
>> which point we can document that).  In other words, even if we did have a
>> couple working implementations, there would be much more to learn from
>> real deployments.
>>
>> I wasn't aware of the IPR.  According to the statement, it covers
>> technology in draft-ietf-grow-va-auto-01.  This covers a way to simplify
>> configuration of the so-called VP-list.  This approach is not mentioned in
>> either of the main drafts (draft-ietf-grow-va-02 or
>> draft-ietf-grow-simple-va-00).  My personal feeling is that this approach
>> is not very critical to the operation of VA, but lacking experience I
>> could certainly be wrong.  In fact, if you look at the 00 draft of
>> auto-config, you'll see that there was a second method proposed for
>> auto-config which has pros and cons relative to Huawei's approach.  This
>> was dropped from the 01 version primarily so as to keep things simple...I
>> don't think any of the non-Huawei authors felt strongly about these
>> approaches one way or the other.
>>
>> Bottom line, I don't think this IPR should impinge moving the two main
>> drafts forward---first because it is optional, and second because there
>> are alternatives.  There are a couple ways we could move forward:
>>
>> 1.  Stick with the set of drafts we have now (the two main drafts, and the
>> optional auto-config draft with the IPR).
>> 2.  Revive the second auto-config method so as to have a published
>> non-encumbered option (probably as a separate draft so that it is clear
>> what is and is not encumbered).
>> 3.  Drop the auto-config draft, and continue forward with only the two
>> main drafts.
> 
> my feeling is if the autoconfig isn't necessary, and is encumbered how
> about we live without it if possible :)
> (w/participant hat)
> -Chris
> 
>> Thoughts?
>>
>> PF
>>
>>
>>
>>
>>
>>
>> From:   Christopher Morrow <christopher.morrow@gmail.com>
>> To:     grow@ietf.org
>> Cc:     lixia@cs.ucla.edu, raszuk@cisco.com, xuxh@huawei.com,
>> jenster@cs.ucla.edu, hitesh@cs.cornell.edu, francis@mpi-sws.org,
>> dromasca@avaya.com, rbonica@juniper.net, pds@lugs.com
>> Date:   06/23/2010 09:46 PM
>> Subject:        Re: IPR Disclosure: Huawei Technologies Co.,Ltd's
>> Statement about IPR     related to draft-ietf-grow-va-02
>>
>>
>>
>> Grow-folk,
>> we should probably decide whether this is a blocking issue for VA
>> progression or not... I believe the ietf stance is that IPR claims are
>> fine, if there aren't other non-encumbered options available.
>>
>> -Chris
>>
>> On Wed, Jun 23, 2010 at 3:31 PM, IETF Secretariat <ietf-ipr@ietf.org>
>> wrote:
>>> Dear Lixia Zhang, Robert Raszuk, Xiaohu Xu, Dan Jen, Hitesh Ballani,
>> Paul Francis:
>>> An IPR disclosure that pertains to your Internet-Draft entitled "FIB
>> Suppression
>>> with Virtual Aggregation" (draft-ietf-grow-va) was submitted to the IETF
>>> Secretariat on 2010-06-23 and has been posted on the "IETF Page of
>> Intellectual
>>> Property Rights Disclosures" (https://datatracker.ietf.org/ipr/1341/).
>> The title
>>> of the IPR disclosure is "Huawei Technologies Co.,Ltd's Statement about
>> IPR
>>> related to draft-ietf-grow-va-02."
>>>
>>> The IETF Secretariat
>>>
>>>
>>>
>>
>>
> _______________________________________________
> GROW mailing list
> GROW@ietf.org
> https://www.ietf.org/mailman/listinfo/grow
>