Re: [Lsr] 答复: Working Group Adoption Poll for "OSPF Extension for Prefix Originator" - draft-wang-lsr-ospf-prefix-originator-ext-01

2019-02-18 Thread Peter Psenak
Aijun, On 19/02/2019 03:01 , Aijun Wang wrote: Hi, Peter and Dirk: Thanks for your comments and the previous explanation. For the use case related to the topology retrieval, I have the following consideration, please point out if I have some misunderstandings for the OSPF LSA procedure: 1)

Re: [Lsr] Working Group Adoption Poll for "OSPF Extension for PrefixOriginator" - draft-wang-lsr-ospf-prefix-originator-ext-01

2019-02-18 Thread zhang.zheng
Support the adoption. Thanks, Sandy 原始邮件 发件人:AceeLindem(acee) 收件人:lsr@ietf.org ; 日 期 :2019年02月13日 21:26 主 题 :[Lsr] Working Group Adoption Poll for "OSPF Extension for PrefixOriginator" - draft-wang-lsr-ospf-prefix-originator-ext-01

Re: [Lsr] 答复: Working Group Adoption Poll for "OSPF Extension for Prefix Originator" - draft-wang-lsr-ospf-prefix-originator-ext-01

2019-02-18 Thread Les Ginsberg (ginsberg)
Aijun – The fact that you have acknowledged the limitations pointed out by others (notably Peter) is a good thing – but it doesn’t alter the fact that what you have proposed cannot be trusted. Routers outside of an area have no way of knowing whether the area in question has unnumbered links

[Lsr] 答复: Working Group Adoption Poll for "OSPF Extension for Prefix Originator" - draft-wang-lsr-ospf-prefix-originator-ext-01

2019-02-18 Thread Aijun Wang
Hi, Les: Thanks for your comments. After the previous discussion within WG list, I had changed the description about the inter-area topology retrieval scenario, which is the original source of this draft that is different from RFC7794. We point out such use case can be applied where each

[Lsr] 答复: Working Group Adoption Poll for "OSPF Extension for Prefix Originator" - draft-wang-lsr-ospf-prefix-originator-ext-01

2019-02-18 Thread Aijun Wang
Hi, Peter and Dirk: Thanks for your comments and the previous explanation. For the use case related to the topology retrieval, I have the following consideration, please point out if I have some misunderstandings for the OSPF LSA procedure: 1) For prefix that is rooted at only one router, such

Re: [Lsr] Working Group Adoption Poll for "OSPF Extension for Prefix Originator" - draft-wang-lsr-ospf-prefix-originator-ext-01

2019-02-18 Thread Lizhenbin
Yes/support. Best Regards, Zhenbin (Robin) From: Lsr mailto:lsr-boun...@ietf.org>> On Behalf Of Acee Lindem (acee) Sent: Wednesday, February 13, 2019 5:26 AM To: lsr@ietf.org Subject: [Lsr] Working Group Adoption Poll for "OSPF Extension for Prefix Originator" -

Re: [Lsr] Working Group Adoption Poll for "OSPF Extension for Prefix Originator" - draft-wang-lsr-ospf-prefix-originator-ext-01

2019-02-18 Thread Zhuangshunwan
Support. Thanks, Shunwan From: Lsr mailto:lsr-boun...@ietf.org>> On Behalf Of Acee Lindem (acee) Sent: Wednesday, February 13, 2019 5:26 AM To: lsr@ietf.org Subject: [Lsr] Working Group Adoption Poll for "OSPF Extension for Prefix Originator" -

Re: [Lsr] Working Group Adoption Poll for "OSPF Extension for Prefix Originator" - draft-wang-lsr-ospf-prefix-originator-ext-01

2019-02-18 Thread Naiming Shen (naiming)
I support. - Naiming From: Lsr mailto:lsr-boun...@ietf.org>> On Behalf Of Acee Lindem (acee) Sent: Wednesday, February 13, 2019 20:26 To: lsr@ietf.org Subject: [Lsr] Working Group Adoption Poll for "OSPF Extension for Prefix Originator" -

Re: [Lsr] Moving Forward [Re: Flooding Reduction Draft Redux]

2019-02-18 Thread Peter Psenak
Hi Huaimo, On 18/02/2019 16:28 , Huaimo Chen wrote: Hi Peter, -Original Message- From: Peter Psenak [mailto:ppse...@cisco.com] Sent: Thursday, February 14, 2019 2:30 AM To: Huaimo Chen ; Acee Lindem (acee) ; Christian Hopps ; lsr@ietf.org Subject: Re: [Lsr] Moving Forward [Re:

Re: [Lsr] Moving Forward [Re: Flooding Reduction Draft Redux]

2019-02-18 Thread Huaimo Chen
Hi Peter, >-Original Message- >From: Peter Psenak [mailto:ppse...@cisco.com] >Sent: Thursday, February 14, 2019 2:30 AM >To: Huaimo Chen ; Acee Lindem (acee) ; >Christian Hopps ; lsr@ietf.org >Subject: Re: [Lsr] Moving Forward [Re: Flooding Reduction Draft Redux] > >Hi Huaimo, > >On

Re: [Lsr] Working Group Adoption Poll for "OSPF Extension for Prefix Originator" - draft-wang-lsr-ospf-prefix-originator-ext-01

2019-02-18 Thread Goethals, Dirk (Nokia - BE/Antwerp)
I think we are in sync, i.e. without this draft there is no use-case for node T1 to send an AS-scoped router info LSA without being ASBR. Please correct if you know of an existing use-case. Thx, Dirk On 2/18/2019 15:01, Peter Psenak wrote: Hi Dirk, On 18/02/2019 14:47 , Goethals, Dirk (Nokia -

Re: [Lsr] Working Group Adoption Poll for "OSPF Extension for Prefix Originator" - draft-wang-lsr-ospf-prefix-originator-ext-01

2019-02-18 Thread Peter Psenak
On 18/02/2019 14:37 , Goethals, Dirk (Nokia - BE/Antwerp) wrote: I agree with Peter. For this to work, the ABR would need to add ALL originators, while I had the impression that we only had 1 originator per prefix, i.e. the originator which was found to be the closed to the ABR and for which the

Re: [Lsr] Working Group Adoption Poll for "OSPF Extension for Prefix Originator" - draft-wang-lsr-ospf-prefix-originator-ext-01

2019-02-18 Thread Peter Psenak
Hi Dirk, On 18/02/2019 14:47 , Goethals, Dirk (Nokia - BE/Antwerp) wrote: Hi Peter, and you use these when you send a traffic to some of the prefixes that T1 originates If T1 is not ASBR, and this draft is not implemented, how are the nodes in the other area's going to know that the

Re: [Lsr] Working Group Adoption Poll for "OSPF Extension for Prefix Originator" - draft-wang-lsr-ospf-prefix-originator-ext-01

2019-02-18 Thread Goethals, Dirk (Nokia - BE/Antwerp)
Hi Peter, and you use these when you send a traffic to some of the prefixes that T1 originates If T1 is not ASBR, and this draft is not implemented, how are the nodes in the other area's going to know that the prefixes belong to T1? Dirk On 2/18/2019 14:34, Peter Psenak wrote: Hi Dirk, On

Re: [Lsr] Working Group Adoption Poll for "OSPF Extension for Prefix Originator" - draft-wang-lsr-ospf-prefix-originator-ext-01

2019-02-18 Thread Goethals, Dirk (Nokia - BE/Antwerp)
I agree with Peter. For this to work, the ABR would need to add ALL originators, while I had the impression that we only had 1 originator per prefix, i.e. the originator which was found to be the closed to the ABR and for which the ABR installed a route. Dirk On 2/18/2019 14:15, Peter Psenak

Re: [Lsr] Working Group Adoption Poll for "OSPF Extension for Prefix Originator" - draft-wang-lsr-ospf-prefix-originator-ext-01

2019-02-18 Thread Peter Psenak
Hi Dirk, On 18/02/2019 14:27 , Goethals, Dirk (Nokia - BE/Antwerp) wrote: Hi Peter, See inline DG>. Dirk On 2/18/2019 14:18, Peter Psenak wrote: Hi Dirk, On 18/02/2019 09:31 , Goethals, Dirk (Nokia - BE/Antwerp) wrote: support +1 1 question: When S1 in another area receives such LSA, it

Re: [Lsr] Working Group Adoption Poll for "OSPF Extension for Prefix Originator" - draft-wang-lsr-ospf-prefix-originator-ext-01

2019-02-18 Thread Goethals, Dirk (Nokia - BE/Antwerp)
Hi Peter, See inline DG>. Dirk On 2/18/2019 14:18, Peter Psenak wrote: Hi Dirk, On 18/02/2019 09:31 , Goethals, Dirk (Nokia - BE/Antwerp) wrote: support +1 1 question: When S1 in another area receives such LSA, it then can learn that prefix Lt1 is associated with node T1, check the ELC,

Re: [Lsr] Working Group Adoption Poll for "OSPF Extension for Prefix Originator" - draft-wang-lsr-ospf-prefix-originator-ext-01

2019-02-18 Thread Les Ginsberg (ginsberg)
To the extent that the draft defines functionality equivalent to that defined in IS-IS RFC 7794 – specifically a means to advertise the source router-id of a given advertisement – it defines a necessary and useful extension to the OSPF protocol – and I support that work. However, in its

Re: [Lsr] Working Group Adoption Poll for "OSPF Extension for Prefix Originator" - draft-wang-lsr-ospf-prefix-originator-ext-01

2019-02-18 Thread Peter Psenak
Hi Dirk, On 18/02/2019 09:31 , Goethals, Dirk (Nokia - BE/Antwerp) wrote: support +1 1 question: When S1 in another area receives such LSA, it then can learn that prefix Lt1 is associated with node T1, check the ELC, ERLD, or MSD value according to its necessity, and construct the

Re: [Lsr] Working Group Adoption Poll for "OSPF Extension for Prefix Originator" - draft-wang-lsr-ospf-prefix-originator-ext-01

2019-02-18 Thread Peter Psenak
Support as coauthor, although I never really agreed with the usage of the prefix originator for topology construction as described in section 3 and 5. I would prefer that part to be removed. thanks, Peter On 13/02/2019 14:25 , Acee Lindem (acee) wrote: This begins a two week adoption poll

Re: [Lsr] Working Group Adoption Poll for "OSPF Extension for Prefix Originator" - draft-wang-lsr-ospf-prefix-originator-ext-01

2019-02-18 Thread Van De Velde, Gunter (Nokia - BE/Antwerp)
+1 for support. Seems as a useful extension to have available in OSPF toolbox. G/ From: Lsr On Behalf Of Acee Lindem (acee) Sent: Wednesday, February 13, 2019 20:26 To: lsr@ietf.org Subject: [Lsr] Working Group Adoption Poll for "OSPF Extension for Prefix Originator" -

Re: [Lsr] Working Group Adoption Poll for "OSPF Extension for Prefix Originator" - draft-wang-lsr-ospf-prefix-originator-ext-01

2019-02-18 Thread Goethals, Dirk (Nokia - BE/Antwerp)
support +1 1 question: When S1 in another area receives such LSA, it then can learn that prefix Lt1 is associated with node T1, check the ELC, ERLD, or MSD value according to its necessity, and construct the right label stack at the ingress node S1 for the traffic destined to Lt1. How