Re: [pim] Publishing draft-ietf-pim-dr-improvement-08

<xu.benchong@zte.com.cn> Wed, 09 October 2019 03:40 UTC

Return-Path: <xu.benchong@zte.com.cn>
X-Original-To: pim@ietfa.amsl.com
Delivered-To: pim@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 322CD1200FE; Tue, 8 Oct 2019 20:40:50 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -4.198
X-Spam-Level:
X-Spam-Status: No, score=-4.198 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_MED=-2.3, SPF_HELO_NONE=0.001, SPF_PASS=-0.001, UNPARSEABLE_RELAY=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 BXu7j3LIGkqV; Tue, 8 Oct 2019 20:40:47 -0700 (PDT)
Received: from mxhk.zte.com.cn (mxhk.zte.com.cn [63.217.80.70]) (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 4D2611200F5; Tue, 8 Oct 2019 20:40:47 -0700 (PDT)
Received: from mse-fl1.zte.com.cn (unknown [10.30.14.238]) by Forcepoint Email with ESMTPS id A0C9BD04457454C4A852; Wed, 9 Oct 2019 11:40:44 +0800 (CST)
Received: from njxapp04.zte.com.cn ([10.41.132.203]) by mse-fl1.zte.com.cn with SMTP id x993dPAd046437; Wed, 9 Oct 2019 11:39:25 +0800 (GMT-8) (envelope-from xu.benchong@zte.com.cn)
Received: from mapi (njxapp03[null]) by mapi (Zmail) with MAPI id mid201; Wed, 9 Oct 2019 11:39:25 +0800 (CST)
Date: Wed, 9 Oct 2019 11:39:25 +0800 (CST)
X-Zmail-TransId: 2afb5d9d566d28e0b724
X-Mailer: Zmail v1.0
Message-ID: <201910091139255024392@zte.com.cn>
In-Reply-To: <CAHANBt+2tTBgcdh9sFtVeYqeyVPhUAC+iT05evu2EH+HmVON7Q@mail.gmail.com>
References: CAHANBtJygYq3-Nr6J3nqt16Ucwh1Np4EZj+MPMrz6HzxZe-uaA@mail.gmail.com, CAHANBt+2tTBgcdh9sFtVeYqeyVPhUAC+iT05evu2EH+HmVON7Q@mail.gmail.com
Mime-Version: 1.0
From: <xu.benchong@zte.com.cn>
To: <stig@venaas.com>
Cc: <pim@ietf.org>, <draft-ietf-pim-dr-improvement@ietf.org>
Content-Type: multipart/mixed; boundary="=====_001_next====="
X-MAIL: mse-fl1.zte.com.cn x993dPAd046437
Archived-At: <https://mailarchive.ietf.org/arch/msg/pim/aV9ogTwveWtGHKyKQoiF3Y8tQ2k>
Subject: Re: [pim] =?utf-8?q?Publishing_draft-ietf-pim-dr-improvement-08?=
X-BeenThere: pim@ietf.org
X-Mailman-Version: 2.1.29
Precedence: list
List-Id: Protocol Independent Multicast <pim.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/pim>, <mailto:pim-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/pim/>
List-Post: <mailto:pim@ietf.org>
List-Help: <mailto:pim-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/pim>, <mailto:pim-request@ietf.org?subject=subscribe>
X-List-Received-Date: Wed, 09 Oct 2019 03:40:50 -0000

Hi, Stig


I don't know any other undisclosed IPR.


Thanks


Benchong Xu







原始邮件



发件人:StigVenaas <stig@venaas.com>
收件人:pim@ietf.org <pim@ietf.org>;draft-ietf-pim-dr-improvement@ietf.org <draft-ietf-pim-dr-improvement@ietf.org>rg>;
日 期 :2019年10月09日 06:06
主 题 :Re: Publishing draft-ietf-pim-dr-improvement-08


Hi

Looks that there are no concerns moving ahead with publication. Can
the authors, and any others that might know
anything about IPR, let us know if they are aware of any other IPR
claims than what has been filed already?

Stig

On Tue, Oct 1, 2019 at 11:18 AM Stig Venaas <stig@venaas.com> wrote:
>
> Hi
>
> An earlier version of this draft passed WGLC many months ago. However,
> as discussed in the WG we agreed it should have some text pointing out
> how it relates to draft-mankamana-pim-bdr-02 that we are considering
> for adoption. This text has now been added, as well as some other
> minor changes.
>
> Please look at revision 08 and speak up if you have any concerns.
>
> Authors, and others, please let us know if you are aware of any other
> IPR claims than the one that already has been filed.
>
> I'll wait a week or so to give people a chance to respond. We need at
> least all the authors to respond regarding IPR before proceeding
> though.
>
> Thanks,
> Stig