Re: [Lsr] Intra-domain SAVNET method - draft-lin-savnet-lsr-intra-domain-method-03

2024-03-20 Thread Qiuyuanxiang
-domain-met...@ietf.org Cc: lsr Subject: RE: [Lsr] Intra-domain SAVNET method - draft-lin-savnet-lsr-intra-domain-method-03 +1 The problem can be solved - and in a much more robust way than what is proposed in the draft - without any protocol extensions. There is no reason for this draft

Re: [Lsr] Intra-domain SAVNET method - draft-lin-savnet-lsr-intra-domain-method-03

2024-03-19 Thread Les Ginsberg (ginsberg)
t; To: draft-lin-savnet-lsr-intra-domain-met...@ietf.org > Cc: lsr > Subject: [Lsr] Intra-domain SAVNET method - draft-lin-savnet-lsr-intra- > domain-method-03 > > Speaking as WG member: > > Co-Authors, > > I see you have a slot at the LSR meeting on Thursday to pres

[Lsr] Intra-domain SAVNET method - draft-lin-savnet-lsr-intra-domain-method-03

2024-03-18 Thread Acee Lindem
Speaking as WG member: Co-Authors, I see you have a slot at the LSR meeting on Thursday to present the subject draft. I believe this document is misguided. You shouldn't need to advertise protected prefixes. If you are doing Source Address Validation for intra-domain sources, why wouldn't