[Lsr] 答复: Working Group Adoption of "IGP Unreachable Prefix Announcement" - draft-ppsenak-lsr-igp-ureach-prefix-announce-04

2023-09-06 Thread Aijun Wang
Hi, Acee: It‘s you that repeat the FALSE statements. What I can do is to give you the FACT again. Please see inline below for the response to your FALSE statements. Best Regards Aijun Wang China Telecom 发件人: Acee Lindem [mailto:acee.i...@gmail.com] 发送时间: 2023年9月6日 20:44 收件人:

Re: [Lsr] 答复: Working Group Adoption of "IGP Unreachable Prefix Announcement" - draft-ppsenak-lsr-igp-ureach-prefix-announce-04

2023-09-06 Thread Peter Psenak
Aijun, On 06/09/2023 11:02, Aijun Wang wrote: My proposal is that we postpone the adoption of this draft, and discuss offline the merger document on the coming IETF118 meeting. I want to be very clear, there is nothing to be merged. regards, Peter Then, we can submit the merged document

Re: [Lsr] 答复: Working Group Adoption of "IGP Unreachable Prefix Announcement" - draft-ppsenak-lsr-igp-ureach-prefix-announce-04

2023-09-06 Thread Aijun Wang
Hi, Peter:Aijun WangChina TelecomOn Sep 6, 2023, at 15:57, Peter Psenak wrote:Aijun,WG adoption should be done based on the draft content, the quality of the solution it describes and not based on the draft age or order.[WAJ] Not exactly. We should also respect the original

Re: [Lsr] 答复: Working Group Adoption of "IGP Unreachable Prefix Announcement" - draft-ppsenak-lsr-igp-ureach-prefix-announce-04

2023-09-06 Thread Peter Psenak
Aijun, WG adoption should be done based on the draft content, the quality of the solution it describes and not based on the draft age or order. Multiple people have pointed out over the years that the solution that you propose in your draft - e.g. using router-id of 0 to indicate the

[Lsr] 答复: Working Group Adoption of "IGP Unreachable Prefix Announcement" - draft-ppsenak-lsr-igp-ureach-prefix-announce-04

2023-09-05 Thread Aijun Wang
Hi, Acee: AGAIN, before making some assertions, please check the following fact: Have you noticed the 00 version of https://datatracker.ietf.org/doc/draft-ppsenak-lsr-igp-event-notification/ was submitted on July 5, 2021? But the description about the short lived notification in

[Lsr] 答复: Working Group Adoption of "IGP Unreachable Prefix Announcement" - draft-ppsenak-lsr-igp-ureach-prefix-announce-04

2023-08-31 Thread Aijun Wang
Hi,Acee: Please read https://datatracker.ietf.org/doc/html/draft-wang-lsr-prefix-unreachable-annoucement-12#section-7 before making misguide assertions: “The advertisement of PUAM message should only last one configurable period to allow the services that run on the failure prefixes are

[Lsr] 答复: Working Group Adoption of "IGP Unreachable Prefix Announcement" - draft-ppsenak-lsr-igp-ureach-prefix-announce-04 (Fixed draft name)

2023-08-29 Thread Xuguoqi
Object its adoption. This document does not solves area/domain partition, but this is a very common scenario. From the perspective of comprehensiveness and maturity, I think https://datatracker.ietf.org/doc/ Draft-wang-lsr-prefix-unreachable-annoucement is a better choice. Thanks, Guoqi Xu

[Lsr] 答复: Working Group Adoption of "IGP Unreachable Prefix Announcement" - draft-ppsenak-lsr-igp-ureach-prefix-announce-04 (Fixed draft name)

2023-08-24 Thread Aijun Wang
Hi, Acee: Please read carefully the description in https://datatracker.ietf.org/doc/html/draft-wang-lsr-prefix-unreachable-annoucement-00#section-3: "In another situation, assume the BGP session is built between Node S2 and T2, via Ps2 and Pt2 respectively. If Node S2 within area 1

[Lsr] 答复: Working Group Adoption of "IGP Unreachable Prefix Announcement" - draft-ppsenak-lsr-igp-ureach-prefix-announce-04 (Fixed draft name)

2023-08-24 Thread Aijun Wang
Object its adoption. The reasons are the followings: 1) It is not the initial draft to describe the problem and provide the solution. 2) The problem and the explicit signaling mechanism is firstly provided by https://datatracker.ietf.org/doc/draft-wang-lsr-prefix-unreachable-annoucement/ in its