For whatever reason, Raj's attestation didn't make it into the BFD archives.  
So, a resend.

-- Jeff


> Begin forwarded message:
> 
> From: Raj Chetan Boddireddy <[email protected]>
> Subject: Re: draft-ietf-bfd-unaffiliated-echo WGLC and IPR check
> Date: April 11, 2023 at 9:18:59 AM EDT
> To: Jeffrey Haas <[email protected]>, 
> "[email protected]" 
> <[email protected]>
> Cc: rtg-bfd WG <[email protected]>
> 
> I am not aware of any IPR disclosures applicable to this document.
>  
> Thanks & Regards,
> Raj Chetan
>  
> From: Jeffrey Haas <[email protected] <mailto:[email protected]>>
> Date: Monday, 10 April 2023 at 8:57 PM
> To: [email protected] 
> <mailto:[email protected]> 
> <[email protected] 
> <mailto:[email protected]>>
> Cc: rtg-bfd WG <[email protected] <mailto:[email protected]>>
> Subject: draft-ietf-bfd-unaffiliated-echo WGLC and IPR check
> 
> [External Email. Be cautious of content]
> 
> 
> https://urldefense.com/v3/__https://datatracker.ietf.org/doc/html/draft-ietf-bfd-unaffiliated-echo__;!!NEt6yMaO-gk!EjoTAw5NjwurOf5C-nX-pWzjHov0h8Td00L8sN39lR8wetMhrXZfgZTsZS2NfFYGjcUnIkmvwmVB$
>  
> <https://urldefense.com/v3/__https:/datatracker.ietf.org/doc/html/draft-ietf-bfd-unaffiliated-echo__;!!NEt6yMaO-gk!EjoTAw5NjwurOf5C-nX-pWzjHov0h8Td00L8sN39lR8wetMhrXZfgZTsZS2NfFYGjcUnIkmvwmVB$>
> 
> 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://urldefense.com/v3/__https://www.rfc-editor.org/rfc/rfc8179.html*section-5.1__;Iw!!NEt6yMaO-gk!EjoTAw5NjwurOf5C-nX-pWzjHov0h8Td00L8sN39lR8wetMhrXZfgZTsZS2NfFYGjcUnIlbXqmPa$
>  
> <https://urldefense.com/v3/__https:/www.rfc-editor.org/rfc/rfc8179.html*section-5.1__;Iw!!NEt6yMaO-gk!EjoTAw5NjwurOf5C-nX-pWzjHov0h8Td00L8sN39lR8wetMhrXZfgZTsZS2NfFYGjcUnIlbXqmPa$>
> 
> 
> Juniper Business Use Only
> 

Reply via email to