IETF Logo Mail Archive

Re: [Idr] IPR Call for draft-li-idr-flowspec-srv6

Lizhenbin <lizhenbin@huawei.com> Tue, 25 February 2020 02:39 UTC

Return-Path: <lizhenbin@huawei.com>
X-Original-To: idr@ietfa.amsl.com
Delivered-To: idr@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 387D83A0415 for <idr@ietfa.amsl.com>; Mon, 24 Feb 2020 18:39:03 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.899
X-Spam-Level:
X-Spam-Status: No, score=-1.899 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, HTML_MESSAGE=0.001, SPF_PASS=-0.001, URIBL_BLOCKED=0.001] autolearn=ham autolearn_force=no
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id Ll8xlnR-UGgc for <idr@ietfa.amsl.com>; Mon, 24 Feb 2020 18:39:01 -0800 (PST)
Received: from huawei.com (lhrrgout.huawei.com [185.176.76.210]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 85DCC3A041A for <idr@ietf.org>; Mon, 24 Feb 2020 18:39:01 -0800 (PST)
Received: from lhreml707-cah.china.huawei.com (unknown [172.18.7.107]) by Forcepoint Email with ESMTP id 48C552D82FDD1689AF54 for <idr@ietf.org>; Tue, 25 Feb 2020 02:38:58 +0000 (GMT)
Received: from lhreml728-chm.china.huawei.com (10.201.108.79) by lhreml707-cah.china.huawei.com (10.201.108.48) with Microsoft SMTP Server (TLS) id 14.3.408.0; Tue, 25 Feb 2020 02:38:57 +0000
Received: from lhreml728-chm.china.huawei.com (10.201.108.79) by lhreml728-chm.china.huawei.com (10.201.108.79) with Microsoft SMTP Server (version=TLS1_2, cipher=TLS_ECDHE_RSA_WITH_AES_128_GCM_SHA256) id 15.1.1713.5; Tue, 25 Feb 2020 02:38:57 +0000
Received: from DGGEMM404-HUB.china.huawei.com (10.3.20.212) by lhreml728-chm.china.huawei.com (10.201.108.79) with Microsoft SMTP Server (version=TLS1_0, cipher=TLS_ECDHE_RSA_WITH_AES_128_CBC_SHA) id 15.1.1713.5 via Frontend Transport; Tue, 25 Feb 2020 02:38:57 +0000
Received: from DGGEMM532-MBX.china.huawei.com ([169.254.7.192]) by DGGEMM404-HUB.china.huawei.com ([10.3.20.212]) with mapi id 14.03.0439.000; Tue, 25 Feb 2020 10:38:53 +0800
From: Lizhenbin <lizhenbin@huawei.com>
To: Susan Hares <shares@ndzh.com>, "idr@ietf.org" <idr@ietf.org>
Thread-Topic: [Idr] IPR Call for draft-li-idr-flowspec-srv6
Thread-Index: AdXrF6YefQ/aBuJURImPFwA7se+WjAAbOtuQ
Date: Tue, 25 Feb 2020 02:38:52 +0000
Message-ID: <5A5B4DE12C0DAC44AF501CD9A2B01A8D936450D6@DGGEMM532-MBX.china.huawei.com>
References: <000701d5eb18$71a02200$54e06600$@ndzh.com>
In-Reply-To: <000701d5eb18$71a02200$54e06600$@ndzh.com>
Accept-Language: zh-CN, en-US
Content-Language: zh-CN
X-MS-Has-Attach:
X-MS-TNEF-Correlator:
x-originating-ip: [10.111.206.84]
Content-Type: multipart/alternative; boundary="_000_5A5B4DE12C0DAC44AF501CD9A2B01A8D936450D6DGGEMM532MBXchi_"
MIME-Version: 1.0
X-CFilter-Loop: Reflected
Archived-At: <https://mailarchive.ietf.org/arch/msg/idr/sJWpO8ZCKUGJNLS4viXs1Lm6mn4>
Subject: Re: [Idr] IPR Call for draft-li-idr-flowspec-srv6
X-BeenThere: idr@ietf.org
X-Mailman-Version: 2.1.29
Precedence: list
List-Id: Inter-Domain Routing <idr.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/idr>, <mailto:idr-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/idr/>
List-Post: <mailto:idr@ietf.org>
List-Help: <mailto:idr-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/idr>, <mailto:idr-request@ietf.org?subject=subscribe>
X-List-Received-Date: Tue, 25 Feb 2020 02:39:03 -0000

I am not aware of any IPR related with the draft.


Best Regards,
Zhenbin (Robin)

From: Idr [mailto:idr-bounces@ietf.org] On Behalf Of Susan Hares
Sent: Monday, February 24, 2020 9:44 PM
To: idr@ietf.org
Subject: [Idr] IPR Call for draft-li-idr-flowspec-srv6

Greetings:

This begins a IPR call for /raft-li-idr-flowspec-srv6-02.txt.  The adoption call will begin after all authors have responded to this email with an IPR statement.  For the authors who have responded before, you will need to respond to this email message as well.

A bit thanks to the authors who have waited patiently for the IDR chairs.

For the WG general discussion on IDR flow specification,  this call is to inquiry if this draft's approach is useful.   As has been discussed on the list, the IETF 107 IDR working group meeting will need to decide if all additions to flow specification should go into  a version 2 specification.

In order to have a fruitful discussion regarding the amount of additions for flow specification, we will be calling for the WG to discuss any potential Flow specification drafts.

Cheers, Sue

v2.23.0 | Report a Bug | By Email