Re: WGLC for draft-ietf-bfd-unaffiliated-echo (ending 7 April, 2023)

Jeff, Please see inline... Original From: JeffreyHaas To: 肖敏10093570; Cc: Greg Mirsky ;rtg-bfd@ietf.org ; Date: 2023年04月11日 01:34 Subject: Re: WGLC for draft-ietf-bfd-unaffiliated-echo (ending 7 April, 2023) Xiao Min, On Apr 9, 2023, at 10:42 PM, wrote: After

Re: WGLC for draft-ietf-bfd-unaffiliated-echo (ending 7 April, 2023)

Xiao Min, > On Apr 9, 2023, at 10:42 PM, > wrote: > From: JeffreyHaas > > "could" isn't one of our RFC 2119 normative terms. Do you believe "SHOULD" > is more appropriate? > [XM-2]>>> If we would like to use normative term for SA, then that can also > apply to DA, suggest s/would/MUST.

Re: WGLC for draft-ietf-bfd-unaffiliated-echo (ending 7 April, 2023)

Jeff, Please see inline... Original From: JeffreyHaas To: 肖敏10093570; Cc: gregimir...@gmail.com ;rtg-bfd@ietf.org ; Date: 2023年04月07日 23:32 Subject: Re: WGLC for draft-ietf-bfd-unaffiliated-echo (ending 7 April, 2023) Xiao Min, On Apr 7, 2023, at 3:15 AM, xiao.m...@zte.com.cn

Re: WGLC for draft-ietf-bfd-unaffiliated-echo (ending 7 April, 2023)

Jeff, Aijun, Thank you for the comments. Please see inline... Original From: JeffreyHaas To: Aijun Wang ; Cc: rtg-bfd@ietf.org ; Date: 2023年04月07日 23:27 Subject: Re: WGLC for draft-ietf-bfd-unaffiliated-echo (ending 7 April, 2023) Aijun, > On Apr 6, 2023, at 8:53 PM, Ai

Re: WGLC for draft-ietf-bfd-unaffiliated-echo (ending 7 April, 2023)

Greg, > On Apr 7, 2023, at 1:10 PM, Greg Mirsky wrote: > On Thu, Apr 6, 2023 at 7:36 AM Jeffrey Haas > wrote: > Greg, > > >> On Mar 27, 2023, at 1:40 AM, Greg Mirsky > > wrote: >> >> Dear Authors, >> I read the latest version of the

Re: WGLC for draft-ietf-bfd-unaffiliated-echo (ending 7 April, 2023)

Greg, > On Apr 7, 2023, at 1:03 PM, Greg Mirsky wrote: > Since the feature is intended to be used for single-hop, the source address > SHOULD be an address on the shared subnet with the interface of the device > that is looping the packets back. Perhaps it might even be reasonable to >

Re: WGLC for draft-ietf-bfd-unaffiliated-echo (ending 7 April, 2023)

Hi Jeff, thank you for your thoughtful response. Please find my notes below under the GIM>> tag. Regards, Greg On Thu, Apr 6, 2023 at 7:36 AM Jeffrey Haas wrote: > Greg, > > > On Mar 27, 2023, at 1:40 AM, Greg Mirsky wrote: > > Dear Authors, > I read the latest version of the draft. I

Re: WGLC for draft-ietf-bfd-unaffiliated-echo (ending 7 April, 2023)

Hi Jeff, I hope you will agree with my using your response to continue the discussion. Please find my notes below under the GIM2>> tag. I will respond to other discussion topics in another follow-up mail. Regards, Greg On Thu, Apr 6, 2023 at 7:28 AM Jeffrey Haas wrote: > Xiao Min, > > Thanks

Re: WGLC for draft-ietf-bfd-unaffiliated-echo (ending 7 April, 2023)

Xiao Min, > On Apr 7, 2023, at 3:15 AM, xiao.m...@zte.com.cn wrote: >>> On Apr 6, 2023, at 3:35 AM, >> > >> > wrote: >> One of the considerations may be whether a IPv6 link local address is >> preferable to a global address. >> >> The

Re: WGLC for draft-ietf-bfd-unaffiliated-echo (ending 7 April, 2023)

Aijun, > On Apr 6, 2023, at 8:53 PM, Aijun Wang wrote: >> Providing additional detail to help illustrate the mechanism would be >> in-scope and perhaps helpful. Did you have any explicit recommendations for >> the text? > [WAJ] How about to refer the style of >

Re： WGLC for draft-ietf-bfd-unaffiliated-echo (ending 7 April, 2023)

Hi WG， I have read the document and support the publication. Best Regards Yisong 发件人: Jeffrey Haas 时间: 2023/03/22(星期三)00:02 收件人: rtg-bfd; 主题: WGLC for draft-ietf-bfd-unaffiliated-echo (ending 7 April, 2023)Working Group, https://datatracker.ietf.org/doc/draft-ietf-bfd

Re: WGLC for draft-ietf-bfd-unaffiliated-echo (ending 7 April, 2023)

Jeff, Thank you for the comments. Please see inline... Original From: JeffreyHaas To: 肖敏10093570; Cc: gregimir...@gmail.com ;rtg-bfd@ietf.org ; Date: 2023年04月06日 22:28 Subject: Re: WGLC for draft-ietf-bfd-unaffiliated-echo (ending 7 April, 2023) Xiao Min, Thanks for addressing

Re: WGLC for draft-ietf-bfd-unaffiliated-echo (ending 7 April, 2023)

Support publication. Thank you Gyan On Tue, Mar 21, 2023 at 12:02 PM Jeffrey Haas wrote: > Working Group, > > https://datatracker.ietf.org/doc/draft-ietf-bfd-unaffiliated-echo/05/ > > The authors of draft-ietf-bfd-unaffiliated-echo have requested WGLC. > > The draft, in my opinion, is in

RE: WGLC for draft-ietf-bfd-unaffiliated-echo (ending 7 April, 2023)

Hi, Jeffrey: Please see the inline replies [WAJ] -Original Message- From: Jeffrey Haas Sent: Thursday, April 6, 2023 10:22 PM To: Aijun Wang Cc: rtg-bfd@ietf.org Subject: Re: WGLC for draft-ietf-bfd-unaffiliated-echo (ending 7 April, 2023) Aijun, > On Apr 4, 2023, at 5:28 AM, Ai

Re: WGLC for draft-ietf-bfd-unaffiliated-echo (ending 7 April, 2023)

Greg, > On Mar 27, 2023, at 1:40 AM, Greg Mirsky wrote: > > Dear Authors, > I read the latest version of the draft. I appreciate your work on improving > its readability. I have several concerns and appreciate your consideration: > It appears like the document defines the format of the Echo

Re: WGLC for draft-ietf-bfd-unaffiliated-echo (ending 7 April, 2023)

Xiao Min, Thanks for addressing Greg's comments. I some additional comment on Greg's points: > On Apr 6, 2023, at 3:35 AM, > wrote: > The draft describes how the destination IP address of the Echo packet is set. > Are there any special considerations for selecting IPv6 destination

Re: WGLC for draft-ietf-bfd-unaffiliated-echo (ending 7 April, 2023)

Aijun, > On Apr 4, 2023, at 5:28 AM, Aijun Wang wrote: > From the description of this document, the state machine of local device is > conformed that described in RFC5880, the main standard parts of this > document are the contents of related fields within the BFD ECHO Packet. If > so, I

Re: WGLC for draft-ietf-bfd-unaffiliated-echo (ending 7 April, 2023)

... Original From: GregMirsky To: 肖敏10093570; Cc: jh...@pfrc.org ;rtg-bfd@ietf.org ; Date: 2023年04月06日 09:03 Subject: Re: WGLC for draft-ietf-bfd-unaffiliated-echo (ending 7 April, 2023) Hi Xiao Min,thank you for sharing your views. I have several technical questions: As this specification replaces

Re: WGLC for draft-ietf-bfd-unaffiliated-echo (ending 7 April, 2023)

Aijun, Thanks for your support and review. Please see inline... Original From: AijunWang To: 'Jeffrey Haas' ;rtg-bfd@ietf.org ; Date: 2023年04月04日 17:28 Subject: RE: WGLC for draft-ietf-bfd-unaffiliated-echo (ending 7 April, 2023) Support its forwarding. The implementation

Re: WGLC for draft-ietf-bfd-unaffiliated-echo (ending 7 April, 2023)

y Haas ; > *Cc: *rtg-bfd@ietf.org ; > *Date: *2023年03月27日 13:40 > *Subject: **Re: WGLC for draft-ietf-bfd-unaffiliated-echo (ending 7 > April, 2023)* > Dear Authors, > I read the latest version of the draft. I appreciate your work on > improving its readability. I hav

RE: WGLC for draft-ietf-bfd-unaffiliated-echo (ending 7 April, 2023)

yle to point out the update to RFC5880? Best Regards Aijun Wang China Telecom -Original Message- From: rtg-bfd-boun...@ietf.org On Behalf Of Jeffrey Haas Sent: Wednesday, March 22, 2023 12:02 AM To: rtg-bfd@ietf.org Subject: WGLC for draft-ietf-bfd-unaffiliated-echo (ending 7 April, 2

Re: WGLC for draft-ietf-bfd-unaffiliated-echo (ending 7 April, 2023)

: JeffreyHaas To: rtg-bfd@ietf.org ; Date: 2023年03月22日 00:02 Subject: WGLC for draft-ietf-bfd-unaffiliated-echo (ending 7 April, 2023) Working Group, https://datatracker.ietf.org/doc/draft-ietf-bfd-unaffiliated-echo/05/ The authors of draft-ietf-bfd-unaffiliated-echo have requested WGLC. The draft

Re: WGLC for draft-ietf-bfd-unaffiliated-echo (ending 7 April, 2023)

Dear Greg, Thanks for sharing your thoughts, even if they're concerns. Please see inline... Original From: GregMirsky To: Jeffrey Haas ; Cc: rtg-bfd@ietf.org ; Date: 2023年03月27日 13:40 Subject: Re: WGLC for draft-ietf-bfd-unaffiliated-echo (ending 7 April, 2023) Dear Authors,I

Re: WGLC for draft-ietf-bfd-unaffiliated-echo (ending 7 April, 2023)

To: rtg-bfd@ietf.org ; Date: 2023年03月22日 00:02 Subject: WGLC for draft-ietf-bfd-unaffiliated-echo (ending 7 April, 2023) Working Group, https://datatracker.ietf.org/doc/draft-ietf-bfd-unaffiliated-echo/05/ The authors of draft-ietf-bfd-unaffiliated-echo have requested WGLC. The draft, in my

Re: WGLC for draft-ietf-bfd-unaffiliated-echo (ending 7 April, 2023)

Dear Authors, I read the latest version of the draft. I appreciate your work on improving its readability. I have several concerns and appreciate your consideration: - It appears like the document defines the format of the Echo message. As I understand the RFC 5880, the format of the Echo

Re: WGLC for draft-ietf-bfd-unaffiliated-echo (ending 7 April, 2023)

Note that the draft is currently expired and will be refreshed when the IETF 116 restrictions permit that to happen. -- Jeff > On Mar 21, 2023, at 12:02 PM, Jeffrey Haas wrote: > > Working Group, > > https://datatracker.ietf.org/doc/draft-ietf-bfd-unaffiliated-echo/05/ > > The authors of

WGLC for draft-ietf-bfd-unaffiliated-echo (ending 7 April, 2023)

Working Group, https://datatracker.ietf.org/doc/draft-ietf-bfd-unaffiliated-echo/05/ The authors of draft-ietf-bfd-unaffiliated-echo have requested WGLC. The draft, in my opinion, is in fairly good shape. However, since it functions via looping packets back to itself and trying to exercise the