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

Xu Xiaohu <xuxh@huawei.com> Sat, 26 June 2010 09:20 UTC

Return-Path: <xuxh@huawei.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 56A503A6836 for <grow@core3.amsl.com>; Sat, 26 Jun 2010 02:20:22 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: 3.886
X-Spam-Level: ***
X-Spam-Status: No, score=3.886 tagged_above=-999 required=5 tests=[AWL=0.103, BAYES_05=-1.11, CN_BODY_35=0.339, FH_RELAY_NODNS=1.451, HELO_MISMATCH_COM=0.553, MIME_CHARSET_FARAWAY=2.45, RDNS_NONE=0.1]
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 h45iiAV6JXUc for <grow@core3.amsl.com>; Sat, 26 Jun 2010 02:20:20 -0700 (PDT)
Received: from szxga04-in.huawei.com (unknown [119.145.14.67]) by core3.amsl.com (Postfix) with ESMTP id E3CF13A6842 for <grow@ietf.org>; Sat, 26 Jun 2010 02:20:13 -0700 (PDT)
Received: from huawei.com (szxga04-in [172.24.2.12]) by szxga04-in.huawei.com (iPlanet Messaging Server 5.2 HotFix 2.14 (built Aug 8 2006)) with ESMTP id <0L4M00GRM79M1R@szxga04-in.huawei.com> for grow@ietf.org; Sat, 26 Jun 2010 17:20:11 +0800 (CST)
Received: from huawei.com ([172.24.2.119]) by szxga04-in.huawei.com (iPlanet Messaging Server 5.2 HotFix 2.14 (built Aug 8 2006)) with ESMTP id <0L4M00MAG79M1P@szxga04-in.huawei.com> for grow@ietf.org; Sat, 26 Jun 2010 17:20:10 +0800 (CST)
Received: from x41208c ([10.110.98.89]) by szxml04-in.huawei.com (iPlanet Messaging Server 5.2 HotFix 2.14 (built Aug 8 2006)) with ESMTPA id <0L4M00KY679M9Q@szxml04-in.huawei.com> for grow@ietf.org; Sat, 26 Jun 2010 17:20:10 +0800 (CST)
Date: Sat, 26 Jun 2010 17:20:34 +0800
From: Xu Xiaohu <xuxh@huawei.com>
In-reply-to: <4C25BED1.6040104@cisco.com>
To: raszuk@cisco.com
Message-id: <001601cb1510$d4cd1060$59626e0a@china.huawei.com>
MIME-version: 1.0
X-MIMEOLE: Produced By Microsoft MimeOLE V6.00.2900.3138
X-Mailer: Microsoft Office Outlook 11
Content-type: text/plain; charset="gb2312"
Content-transfer-encoding: quoted-printable
Thread-index: AcsVDFbJIUQR+y04Q3CcMRiqyK6NVAAAwh4A
Cc: grow@ietf.org
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: Sat, 26 Jun 2010 09:20:23 -0000

> -----邮件原件-----
> 发件人: Robert Raszuk [mailto:raszuk@cisco.com]
> 发送时间: 2010年6月26日 16:48
> 收件人: Xu Xiaohu
> 抄送: grow@ietf.org
> 主题: Re: [GROW] IPR Disclosure: Huawei Technologies Co., Ltd's Statement
about
> IPR related to draft-ietf-grow-va-02
> 
> Xu,
> 
> I am not talking about the draft. I am asking about the patent ?
> 
> if you are using BGP communities to carry policy information what is in
> there which is novel and which requires IPR ?

The key part of this IPR is to make a BGP router to selectively FIB-install
BGP routes according to their BGP community values, together with its own
role (i.e., APR or non-APR for a given prefix).

Best wishes,
Xiaohu

> Thx,
> R.
> 
> 
> > Robert,
> >
> >> -----邮件原件-----
> >> 发件人: grow-bounces@ietf.org [mailto:grow-bounces@ietf.org] 代表
Robert
> >> Raszuk
> >> 发送时间: 2010年6月25日 19:26
> >> 收件人: grow@ietf.org
> >> 主题: Re: [GROW] IPR Disclosure: Huawei Technologies Co., Ltd's
Statement
> > about
> >> IPR related to draft-ietf-grow-va-02
> >>
> >> Folks,
> >>
> >> I (as both individual contributor as well as co-author of VA draft)
> >> fully agree with Chris that if needed simple use of BGP communities can
> >> be applied within given domain to carry any form of local policy across
> >> iBGP mesh - that applies to both prefix groups/lists and popular
> >> prefixes using VA terminology.
> >
> >> Reinventing the wheel with some other tool other then those which
> >> already have been successfully used for years makes no sense to me.
> >
> > Agree. Actually the auto-configuration mechanism defined in va-auto
draft
> > DOES use the BGP community to carry the "can-suppress" tag which
determines
> > whether or not the prefix should be suppressed. Hence, we are not
> > reinventing the wheel, and that is why the draft is just informational,
> > rather than standard track.
> >
> > Best wishes,
> > Xiaohu
> >
> >> With this in mind I am completely not clear what such IPR filing could
> >> be about. Are we discussing IPR of carrying local policy by BGP
> >> communities ? That I am afraid has a decent prior art to 2007 filing.
> >>
> >> Many thx,
> >> R.