[bess] 答复: WGLC, IPR and implementation poll for draft-ietf-bess-evpn-bum-procedure-updates

Lizhenbin <lizhenbin@huawei.com> Mon, 14 January 2019 17:32 UTC

Return-Path: <lizhenbin@huawei.com>
X-Original-To: bess@ietfa.amsl.com
Delivered-To: bess@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 3DC721311D3 for <bess@ietfa.amsl.com>; Mon, 14 Jan 2019 09:32:30 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.21
X-Spam-Level:
X-Spam-Status: No, score=-2.21 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, HTML_MESSAGE=0.001, HTTPS_HTTP_MISMATCH=1.989, RCVD_IN_DNSWL_MED=-2.3, 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 VCqYlBv3Y_3S for <bess@ietfa.amsl.com>; Mon, 14 Jan 2019 09:32:27 -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 27A871311D2 for <bess@ietf.org>; Mon, 14 Jan 2019 09:32:27 -0800 (PST)
Received: from lhreml707-cah.china.huawei.com (unknown [172.18.7.106]) by Forcepoint Email with ESMTP id 3C1669EB2742528222CE for <bess@ietf.org>; Mon, 14 Jan 2019 17:32:25 +0000 (GMT)
Received: from DGGEMM406-HUB.china.huawei.com (10.3.20.214) by lhreml707-cah.china.huawei.com (10.201.108.48) with Microsoft SMTP Server (TLS) id 14.3.408.0; Mon, 14 Jan 2019 17:32:24 +0000
Received: from DGGEMM532-MBX.china.huawei.com ([169.254.7.23]) by DGGEMM406-HUB.china.huawei.com ([10.3.20.214]) with mapi id 14.03.0415.000; Tue, 15 Jan 2019 01:32:20 +0800
From: Lizhenbin <lizhenbin@huawei.com>
To: "stephane.litkowski@orange.com" <stephane.litkowski@orange.com>, "bess@ietf.org" <bess@ietf.org>
Thread-Topic: [bess] WGLC, IPR and implementation poll for draft-ietf-bess-evpn-bum-procedure-updates
Thread-Index: AQHUmNgXC5RimofIn0Ch2Xt9JliXPKWJVURQgCXWmds=
Date: Mon, 14 Jan 2019 17:32:19 +0000
Message-ID: <5A5B4DE12C0DAC44AF501CD9A2B01A8D8F512D8B@DGGEMM532-MBX.china.huawei.com>
References: <7A6CB066-AC84-4627-923A-AE6690A22E32@cisco.com>, <DM6PR05MB50365163FBA6BBF3AC9D9A17D4B80@DM6PR05MB5036.namprd05.prod.outlook.com>
In-Reply-To: <DM6PR05MB50365163FBA6BBF3AC9D9A17D4B80@DM6PR05MB5036.namprd05.prod.outlook.com>
Accept-Language: zh-CN, en-US
Content-Language: zh-CN
X-MS-Has-Attach:
X-MS-TNEF-Correlator:
x-originating-ip: [10.109.109.151]
Content-Type: multipart/alternative; boundary="_000_5A5B4DE12C0DAC44AF501CD9A2B01A8D8F512D8BDGGEMM532MBXchi_"
MIME-Version: 1.0
X-CFilter-Loop: Reflected
Archived-At: <https://mailarchive.ietf.org/arch/msg/bess/cuZqx4aSMJWv7eAicOJFvHCGfRw>
Subject: [bess] =?gb2312?b?tPC4tDogIFdHTEMsIElQUiBhbmQgaW1wbGVtZW50YXRp?= =?gb2312?b?b24gcG9sbCBmb3IgZHJhZnQtaWV0Zi1iZXNzLWV2cG4tYnVtLXByb2NlZHVy?= =?gb2312?b?ZS11cGRhdGVz?=
X-BeenThere: bess@ietf.org
X-Mailman-Version: 2.1.29
Precedence: list
List-Id: BGP-Enabled ServiceS working group discussion list <bess.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/bess>, <mailto:bess-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/bess/>
List-Post: <mailto:bess@ietf.org>
List-Help: <mailto:bess-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/bess>, <mailto:bess-request@ietf.org?subject=subscribe>
X-List-Received-Date: Mon, 14 Jan 2019 17:32:30 -0000

I am not aware of any IPR on this draft except the following disclosed one:

https://datatracker.ietf.org/ipr/3341/





Zhenbin(Robin)





________________________________
发件人: BESS [bess-bounces@ietf.org] 代表 Jeffrey (Zhaohui) Zhang [zzhang@juniper.net]
发送时间: 2018年12月21日 23:40
收件人: stephane.litkowski@orange.com; bess@ietf.org
主题: Re: [bess] WGLC, IPR and implementation poll for draft-ietf-bess-evpn-bum-procedure-updates

As a co-author, I am not aware of any undisclosed IPR on this draft.

Jeffrey

From: BESS <bess-bounces@ietf.org> On Behalf Of Ali Sajassi (sajassi)
Sent: Thursday, December 20, 2018 9:52 PM
To: stephane.litkowski@orange.com; bess@ietf.org
Subject: Re: [bess] WGLC, IPR and implementation poll for draft-ietf-bess-evpn-bum-procedure-updates


As a co-author, I am not aware of any undisclosed IPR on this draft.

Regards,
Ali

From: BESS <bess-bounces@ietf.org<mailto:bess-bounces@ietf.org>> on behalf of "stephane.litkowski@orange.com<mailto:stephane.litkowski@orange.com>" <stephane.litkowski@orange.com<mailto:stephane.litkowski@orange.com>>
Date: Monday, December 17, 2018 at 4:50 AM
To: "bess@ietf.org<mailto:bess@ietf.org>" <bess@ietf.org<mailto:bess@ietf.org>>
Subject: [bess] WGLC, IPR and implementation poll for draft-ietf-bess-evpn-bum-procedure-updates


Hello Working Group,



This email starts a three weeks Working Group Last Call on  draft-ietf-bess-evpn-bum-procedure-updates [1]. The poll period is longer than usual due to the coming vacation period.



This poll runs until *the 7th of January*.



We are also polling for knowledge of any undisclosed IPR that applies to this Document, to ensure that IPR has been disclosed in compliance with IETF IPR rules (see RFCs 3979, 4879, 3669 and 5378 for more details).

If you are listed as an Author or a Contributor of this Document please respond to this email and indicate whether or not you are aware of any relevant undisclosed IPR. The Document won't progress without answers from all the Authors and Contributors.



There is currently no IPR disclosed.



If you are not listed as an Author or a Contributor, then please explicitly respond only if you are aware of any IPR that has not yet been disclosed in conformance with IETF rules.



We are also polling for any existing implementation as per [2].



    Thank you,

    Stephane & Matthew



    [1] https://datatracker.ietf.org/doc/draft-ietf-bess-evpn-bum-procedure-updates/<https://urldefense.proofpoint.com/v2/url?u=https-3A__datatracker.ietf.org_doc_draft-2Dietf-2Dbess-2Devpn-2Dbum-2Dprocedure-2Dupdates_&d=DwMGaQ&c=HAkYuh63rsuhr6Scbfh0UjBXeMK-ndb3voDTXcWzoCI&r=f7wsLGcfzAWDNS6XNTBZwj_OLAOsZZqdrR2IDAzeZqE&m=if32QCzMhkFaC6vZ0G650S7ykzOx94MvUKra-OTxtms&s=rjo8KqQKkxtrNufkcf5-5xBrhTqxYAtyA2ubf39jF6g&e=>



    [2] https://mailarchive.ietf.org/arch/msg/bess/cG3X1tTqb_vPC4rg56SEdkjqDpw<https://urldefense.proofpoint.com/v2/url?u=https-3A__mailarchive.ietf.org_arch_msg_bess_cG3X1tTqb-5FvPC4rg56SEdkjqDpw&d=DwMGaQ&c=HAkYuh63rsuhr6Scbfh0UjBXeMK-ndb3voDTXcWzoCI&r=f7wsLGcfzAWDNS6XNTBZwj_OLAOsZZqdrR2IDAzeZqE&m=if32QCzMhkFaC6vZ0G650S7ykzOx94MvUKra-OTxtms&s=1IGfWic_SiLi7GOrtXmy32MtOdUKUNGL15sKVZx9JU4&e=>


_________________________________________________________________________________________________________________________



Ce message et ses pieces jointes peuvent contenir des informations confidentielles ou privilegiees et ne doivent donc

pas etre diffuses, exploites ou copies sans autorisation. Si vous avez recu ce message par erreur, veuillez le signaler

a l'expediteur et le detruire ainsi que les pieces jointes. Les messages electroniques etant susceptibles d'alteration,

Orange decline toute responsabilite si ce message a ete altere, deforme ou falsifie. Merci.



This message and its attachments may contain confidential or privileged information that may be protected by law;

they should not be distributed, used or copied without authorisation.

If you have received this email in error, please notify the sender and delete this message and its attachments.

As emails may be altered, Orange is not liable for messages that have been modified, changed or falsified.

Thank you.