转发: draft-ietf-bfd-unaffiliated-echo WGLC and IPR check

wangruixue@chinamobile.com Tue, 11 April 2023 06:59 UTC

Return-Path: <wangruixue@chinamobile.com>
X-Original-To: rtg-bfd@ietfa.amsl.com
Delivered-To: rtg-bfd@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 439F5C151B1F; Mon, 10 Apr 2023 23:59:40 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.595
X-Spam-Level:
X-Spam-Status: No, score=-2.595 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_LOW=-0.7, RCVD_IN_ZEN_BLOCKED_OPENDNS=0.001, SPF_HELO_NONE=0.001, SPF_PASS=-0.001, URIBL_BLOCKED=0.001, URIBL_DBL_BLOCKED_OPENDNS=0.001, URIBL_ZEN_BLOCKED_OPENDNS=0.001] autolearn=ham autolearn_force=no
Received: from mail.ietf.org ([50.223.129.194]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id Ofi-UOI9vKLO; Mon, 10 Apr 2023 23:59:36 -0700 (PDT)
Received: from cmccmta1.chinamobile.com (cmccmta1.chinamobile.com [221.176.66.79]) by ietfa.amsl.com (Postfix) with ESMTP id 6D8A8C14CE52; Mon, 10 Apr 2023 23:59:32 -0700 (PDT)
X-RM-TagInfo: emlType=0
X-RM-SPAM-FLAG: 00000000
Received: from spf.mail.chinamobile.com (unknown[172.16.121.99]) by rmmx-syy-dmz-app02-12002 (RichMail) with SMTP id 2ee26435055027e-941d0; Tue, 11 Apr 2023 14:59:30 +0800 (CST)
X-RM-TRANSID: 2ee26435055027e-941d0
X-RM-TagInfo: emlType=0
X-RM-SPAM-FLAG: 00000000
Received: from DESKTOPREBAVM3 (unknown[183.230.39.98]) by rmsmtp-syy-appsvrnew10-12035 (RichMail) with SMTP id 2f03643505508e6-22ed5; Tue, 11 Apr 2023 14:59:29 +0800 (CST)
X-RM-TRANSID: 2f03643505508e6-22ed5
From: wangruixue@chinamobile.com
To: 'Jeffrey Haas' <jhaas@pfrc.org>, 'draft-ietf-bfd-unaffiliated-echo' <draft-ietf-bfd-unaffiliated-echo@ietf.org>
Cc: 'rtg-bfd WG' <rtg-bfd@ietf.org>
References: <202304111457412384511@chinamobile.com>
In-Reply-To: <202304111457412384511@chinamobile.com>
Subject: 转发: draft-ietf-bfd-unaffiliated-echo WGLC and IPR check
Date: Tue, 11 Apr 2023 14:59:29 +0800
Message-ID: <004c01d96c43$29db3220$7d919660$@chinamobile.com>
MIME-Version: 1.0
Content-Type: multipart/alternative; boundary="----=_NextPart_000_004D_01D96C86.37FFF8C0"
X-Mailer: Microsoft Outlook 16.0
Thread-Index: AQG37y4Xie2OtHwxhbTdO65yVeeeNa9op5Rg
Content-Language: zh-cn
Archived-At: <https://mailarchive.ietf.org/arch/msg/rtg-bfd/K9D3KG7MqAm1yk0WaAIOoh5B_Z8>
X-BeenThere: rtg-bfd@ietf.org
X-Mailman-Version: 2.1.39
Precedence: list
List-Id: "RTG Area: Bidirectional Forwarding Detection DT" <rtg-bfd.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/rtg-bfd>, <mailto:rtg-bfd-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/rtg-bfd/>
List-Post: <mailto:rtg-bfd@ietf.org>
List-Help: <mailto:rtg-bfd-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/rtg-bfd>, <mailto:rtg-bfd-request@ietf.org?subject=subscribe>
X-List-Received-Date: Tue, 11 Apr 2023 06:59:40 -0000

I am not aware of any IPR applicable to this document.

 

 

Ruixue Wang

 

From: Jeffrey Haas <mailto:jhaas@pfrc.org> 

Date: 2023-04-10 23:27

To: draft-ietf-bfd-unaffiliated-echo
<mailto:draft-ietf-bfd-unaffiliated-echo@ietf.org> 

CC: rtg-bfd WG <mailto:rtg-bfd@ietf.org> 

Subject: draft-ietf-bfd-unaffiliated-echo WGLC and IPR check

https://datatracker.ietf.org/doc/html/draft-ietf-bfd-unaffiliated-echo

 

Working Group,

 

The Working Group Last Call for draft-ietf-bfd-unaffiliated-echo has
completed.  My judgment is that it has weak, but positive support to proceed
to publication.  This isn't atypical of BFD work at this point in the BFD
Working Group's life.  

 

The next steps for the document:

 

1. Please continue to iterate through the issues raised during last call.  I
will be summarizing them in the original WGLC thread.  I suspect we can
reach conclusion for them shortly.

 

2. Each of the authors needs to make an attestation as to whether they're
aware of any additional IPR applicable to this document.  The rest of the
Working Group, as per BCP 78/79[1] should also disclose of any applicable
IPR if they're aware of it.

 

One thing that makes this document particularly interesting is that this
work is covered partially under work done in BBF in TR-146.  This will be
noted in the shepherd writeup.

 

 

-- Jeff

 

[1] https://www.rfc-editor.org/rfc/rfc8179.html#section-5.1