Re: [Lsr] [Bier] PCE Controller & SDN Controller & Netconf/Yang NMS Controller - lines blurred and can the names be used ubiquitously meaning the same

2020-11-20 Thread Gyan Mishra
w confusion, risk > destabilising the network? Should it use a different code point to be > distinguishable? > > Gyan> Completely agree. I agree negative impact if any exist. See my > comments above. As BGP has the ability to compartmentalize SAFI, > codepoints and p

Re: [Lsr] Prefix Unreachable Announcement Use Cases

2020-11-20 Thread Gyan Mishra
ected > POPs within area could be nicely summarized ? Isn't it better to design > your area such that ABRs are interconnected with redundancy ? > > Thx, > R. > > > > On Fri, Nov 20, 2020 at 3:28 AM Gyan Mishra wrote: > >> >> Aijun >> >> I

Re: [Lsr] Prefix Unreachable Announcement Use Cases

2020-11-19 Thread Gyan Mishra
s co-authors to > refine the solutions for more scenarios. > > > > Thanks in advance. > > > > Best Regards > > > > Aijun Wang > > China Telecom > > > > > > *From:* Acee Lindem (acee) > *Sent:* Thursday, November 19, 2020 12:42 AM > *To

Re: [Lsr] Prefix Unreachable Announcement Use Cases

2020-11-17 Thread Gyan Mishra
ation if we > should use IGP flooding for it. Maybe in some scenarios ... which PUA > authors need to spell out to move fwd I suppose. > > Cheers, > R. > > > > > > > > > On Tue, Nov 17, 2020 at 9:40 PM Gyan Mishra wrote: > >> >> Robert >> >

Re: [Lsr] Prefix Unreachable Announcement Use Cases

2020-11-17 Thread Gyan Mishra
to converge on alternate next hop. Let me update the presentation to add this use case. Thanks Gyan On Tue, Nov 17, 2020 at 2:09 PM Gyan Mishra wrote: > Agreed. > > Robert > > Can you explain the BGP scenario you had in mind that you have mentioned a > number of times that

Re: [Lsr] Prefix Unreachable Announcement Use Cases

2020-11-17 Thread Gyan Mishra
CE interface. No need. > Understood. Bad idea. > > Thx a lot, > R. > > -- <http://www.verizon.com/> *Gyan Mishra* *Network Solutions A**rchitect * *M 301 502-134713101 Columbia Pike *Silver Spring, MD ___ Lsr mailing list Lsr@ietf.org https://www.ietf.org/mailman/listinfo/lsr

Re: [Lsr] Prefix Unreachable Announcement Use Cases

2020-11-17 Thread Gyan Mishra
not convinced the IGP is the right place to solve this problem. > > > > Thanks, > > Acee > > > > *From: *Lsr on behalf of Gyan Mishra < > hayabusa...@gmail.com> > *Date: *Tuesday, November 17, 2020 at 4:02 AM > *To: *Robert Raszuk > *Cc

Re: [Lsr] Prefix Unreachable Announcement Use Cases

2020-11-17 Thread Gyan Mishra
On Tue, Nov 17, 2020 at 4:01 AM Gyan Mishra wrote: > > > On Tue, Nov 17, 2020 at 3:36 AM Robert Raszuk wrote: > >> >> >>Robert, I believe the original intention was related to having the >>> data plane converge quickly when summarization is used

Re: [Lsr] Prefix Unreachable Announcement Use Cases

2020-11-17 Thread Gyan Mishra
m not sure how much faster the data >> plane will converge with PUA. >> > > Even without any of the above listed chain of acronymous things will > generally work well intra-area without PUAs. > Gyan> Agreed which is why I mentioned the BGP next hop self use case if I

Re: [Lsr] Prefix Unreachable Announcement Use Cases

2020-11-17 Thread Gyan Mishra
> > ___ > Lsr mailing list > Lsr@ietf.org > https://www.ietf.org/mailman/listinfo/lsr > -- <http://www.verizon.com/> *Gyan Mishra* *Network Solutions A**rchitect * *M 301 502-134713101 Columbia Pike *Silver Spring, MD ___ Lsr mailing list Lsr@ietf.org https://www.ietf.org/mailman/listinfo/lsr

Re: [Lsr] Prefix Unreachable Announcement Use Cases

2020-11-17 Thread Gyan Mishra
pon reception of PUA are questionable at best. > > > > Cheers, > R. > ___ > Lsr mailing list > Lsr@ietf.org > https://www.ietf.org/mailman/listinfo/lsr > -- <http://www.verizon.com/> *Gyan Mishra* *Network Solutions A**rchitect * *M 301 502-134713101 Columbia Pike *Silver Spring, MD ___ Lsr mailing list Lsr@ietf.org https://www.ietf.org/mailman/listinfo/lsr

Re: [Lsr] Prefix Unreachable Announcement Use Cases

2020-11-16 Thread Gyan Mishra
th protection in a remote area is highly unlikely to have the > topological details necessary to find an alternate path to that prefix. > > Tony > > ___ > Lsr mailing list > Lsr@ietf.org > https://www.ietf.org/mailman/listinfo/lsr > --

Re: [Lsr] [Idr] WG Adoption for draft-zhu-idr-bgp-ls-path-mtu (11/1/2020 to 11/16/2020)

2020-11-16 Thread Gyan Mishra
BGP-LS additions rather than > > this specific addition, please make that clear in your > > comment in this discussion. > > > > The authors requested a WG adoption at IETF 108. > > The IDR co-chairs thank the authors for their patience. &g

Re: [Lsr] Prefix Unreachable Announcement Use Cases

2020-11-15 Thread Gyan Mishra
> Lsr mailing list > Lsr@ietf.org > https://www.ietf.org/mailman/listinfo/lsr > -- <http://www.verizon.com/> *Gyan Mishra* *Network Solutions A**rchitect * *M 301 502-134713101 Columbia Pike *Silver Spring, MD ___ Lsr mailing list Lsr@ietf.org https://www.ietf.org/mailman/listinfo/lsr

Re: [Lsr] WG Adoption Call for "ISIS Extensions in Support of Inter-AS MPLS and GMPLS TE" - draft-chen-lsr-isis-rfc5316bis-02

2020-10-24 Thread Gyan Mishra
ks, > > Acee > > > > ___ > > Lsr mailing list > > Lsr@ietf.org > > https://www.ietf.org/mailman/listinfo/lsr > > ___ > Lsr mailing list > Lsr@ietf.org > http

Re: [Lsr] WG Last Call draft-ietf-lsr-ospf-prefix-originator-06

2020-10-16 Thread Gyan Mishra
. In this case moreso not pertinent since the primary use case gets into the weeds on a TEAS or PCE topiic. Thanks Gyan On Fri, Oct 16, 2020 at 1:04 AM Ketan Talaulikar (ketant) wrote: > Hi Gyan, > > > > Thanks for your review and feedback. Please check inline below. > > > > *

Re: [Lsr] WG Last Call draft-ietf-lsr-ospf-prefix-originator-06

2020-10-15 Thread Gyan Mishra
TaSzQThghtCFOuYPS2VjLqhK8p03Fg3L9LuCGXw8C0X6qRQdrHjKDKHcz > >>> 5KtUHQ$ > >>> > >>> Authors, > >>> > >>> Please indicate to the list, your knowledge of any other IPR > >>> related to this work. > >>> > >>> Thanks, > >>> Chris. &g

Re: [Lsr] PCE Controller & SDN Controller & Netconf/Yang NMS Controller - lines blurred and can the names be used ubiquitously meaning the same

2020-10-12 Thread Gyan Mishra
t any design objective. Comments welcome. Kind Regards Gyan On Sat, Oct 10, 2020 at 3:26 PM Gyan Mishra wrote: > > Dear TEAS, PCE, IDR, LSR, BESS, BIER Spring Working Groups, > > I have noticed that after reviewing many drafts across many WGs it seems > in the industry that the l

Re: [Lsr] FW: New Version Notification for draft-bonica-lsr-ip-flexalgo-00.txt

2020-10-12 Thread Gyan Mishra
ee - nothing gets me more excited than algo 201 with chocolate over > it ;-) > On Oct 11, 2020, 11:21 AM -0700, Gyan Mishra , > wrote: > > > Jeff > > So basically as SR Flex Algo uses SR data plane (SID ,context) uniqueness > for SR-MPLS label uniqueness and SRv6 Locator u

Re: [Lsr] FW: New Version Notification for draft-wang-lsr-passive-interface-attribute-04.txt

2020-10-11 Thread Gyan Mishra
gt; > 1. I'm not sure the problem needs to be solved by IGPs. I tend > to believe > > > ietf-idr-bgpls-inter-as-topology-ext is sufficient. > > > > > > 2. the solution that you proposed is wrong. You are trying to > deriv

Re: [Lsr] FW: New Version Notification for draft-bonica-lsr-ip-flexalgo-00.txt

2020-10-11 Thread Gyan Mishra
t; > > > Ron > > > > > > > > Juniper Business Use Only > > > > -Original Message- > > From: Jeff Tantsura > > Sent: Saturday, October 10, 2020 3:14 PM > > To: Ron Bonica > > Cc: Dongjie (Jimmy) ; Pe

[Lsr] PCE Controller & SDN Controller & Netconf/Yang NMS Controller - lines blurred and can the names be used ubiquitously meaning the same

2020-10-10 Thread Gyan Mishra
ought I would bring up to the WG as an important discussion point. Lots of food for thought. Welcome all comments as well as concerns related to this topic. Kind Regards, <http://www.verizon.com/> *Gyan Mishra* *Network Solutions A**rchitect * *M 301 502-134713101 Columbia Pike *Silver S

Re: [Lsr] WG adoption call for draft-ketant-lsr-ospf-l2bundles-01

2020-10-06 Thread Gyan Mishra
model. Basically same functionality > provided to controller be able to leverage in a distributed model. > Thanks, > > Ketan > > > > *From:* Lsr *On Behalf Of *Gyan Mishra > *Sent:* 03 October 2020 04:07 > *To:* Les Ginsberg (ginsberg) > *Cc:* lsr@ietf.org; draft-

Re: [Lsr] FW: New Version Notification for draft-bonica-lsr-ip-flexalgo-00.txt

2020-10-04 Thread Gyan Mishra
Thanks Peter! On Sun, Oct 4, 2020 at 5:51 AM Peter Psenak wrote: > Hi Gyan, > > > > On 03/10/2020 18:54, Gyan Mishra wrote: > > > > > > Thanks Peter for the responses to help clear up my flex algo > understanding!! > > > > > > On Sat,

Re: [Lsr] FW: New Version Notification for draft-bonica-lsr-ip-flexalgo-00.txt

2020-10-03 Thread Gyan Mishra
pinning of underlay to overlay. How would that be done with IP based flex algo. So with IP based flex algo as well you would be global table routing with no VPN framework. Thanks Gyan On Sat, Oct 3, 2020 at 12:54 PM Gyan Mishra wrote: > > Thanks Peter for the responses to help clear up m

Re: [Lsr] FW: New Version Notification for draft-bonica-lsr-ip-flexalgo-00.txt

2020-10-03 Thread Gyan Mishra
Thanks Peter for the responses to help clear up my flex algo understanding!! On Sat, Oct 3, 2020 at 5:45 AM Peter Psenak wrote: > Gyan, > > > > On 03/10/2020 02:14, Gyan Mishra wrote: > > > > > > Hi Jeff > > > > > > From a

Re: [Lsr] FW: New Version Notification for draft-bonica-lsr-ip-flexalgo-00.txt

2020-10-03 Thread Gyan Mishra
w!  > > Thx, > R. > > On Sat, Oct 3, 2020 at 2:14 AM Gyan Mishra wrote: > >> >> Hi Jeff >> >> From a domain perspective where you have a group of nodes and associated >> IP addressed and SID are part of a discrete underlay instance flex

Re: [Lsr] FW: New Version Notification for draft-bonica-lsr-ip-flexalgo-00.txt

2020-10-02 Thread Gyan Mishra
> address associated with only one algo, please correct me if I'm missing or > misunderstood something. > > > > > > Thanks, > > > Yingzhen > > > > > > On 10/2/20, 9:43 AM, "Lsr on behalf of Peter Psenak" < > lsr-boun...@ietf.org on behalf

Re: [Lsr] WG adoption call for draft-ketant-lsr-ospf-l2bundles-01

2020-10-02 Thread Gyan Mishra
t; > > > Thanks, > > > Chris and Acee. > > > > ___ > > Lsr mailing list > > Lsr@ietf.org > > https://www.ietf.org/mailman/listinfo/lsr > > -- <http://www.verizon.com/> *Gyan Mishra* *Network Solutions A**rchitect * *M 301 502-134713101 Columbia Pike *Silver Spring, MD ___ Lsr mailing list Lsr@ietf.org https://www.ietf.org/mailman/listinfo/lsr

Re: [Lsr] FW: New Version Notification for draft-bonica-lsr-ip-flexalgo-00.txt

2020-10-02 Thread Gyan Mishra
Thanks Peter! On Fri, Oct 2, 2020 at 12:42 PM Peter Psenak wrote: > Gyan, > > > > On 02/10/2020 18:30, Gyan Mishra wrote: > > > All, > > > > > > With SRv6 and IP based flex algo a generic question as it applies to > > > both. Is it possibl

Re: [Lsr] FW: New Version Notification for draft-bonica-lsr-ip-flexalgo-00.txt

2020-10-02 Thread Gyan Mishra
ietf.org/html/draft-> > > > > bonica-lsr-ip-flexalgo-00__;!!NEt6yMaO-gk!X7PVDP- > > > > FnUA0oCcZMw3Qde6in0C72hu_9hOZ53kPspIarR8fNDyU9Vck81_QrJ_p$ > > > > > > > > > > > > Abstract: > > > >An IGP Flexible Algorithm computes a constraint-based path and maps > > > >

Re: [Lsr] New Version Notification for draft-wang-lsr-prefix-unreachable-annoucement-03.txt

2020-09-04 Thread Gyan Mishra
nsberg (ginsberg)" > *Date: *Friday, September 4, 2020 at 3:00 PM > *To: *Tony Przygienda , Aijun Wang < > wangai...@tsinghua.org.cn> > *Cc: *Gyan Mishra , Robert Raszuk < > rob...@raszuk.net>, Huzhibo , Aijun Wang < > wang...@chinatelecom.cn>, Pet

Re: [Lsr] New Version Notification for draft-wang-lsr-prefix-unreachable-annoucement-03.txt

2020-09-04 Thread Gyan Mishra
t; > China Telecom > > > > *From:* lsr-boun...@ietf.org [mailto:lsr-boun...@ietf.org] *On Behalf Of *Gyan > Mishra > > > *Sent:* Thursday, August 6, 2020 4:44 PM > *To:* Aijun Wang > *Cc:* Peter Psenak ; Robert Raszuk < > rob...@raszuk.net>; Huzhibo

Re: [Lsr] LSR WG Adoption Poll for "IS-IS Topology-Transparent Zone" - draft-chen-isis-ttz-11.txt

2020-09-02 Thread Gyan Mishra
en a goal. >> >> >> >> >> >> >> >> >> >> >> >> >> >> >> >> What we are looking for is value and value that outweighs the complexity. >> >> >> >> >> >> >> &

Re: [Lsr] [OPSAWG] draft-tgraf-ipfix-mpls-sr-label-type

2020-08-17 Thread Gyan Mishra
gt; > On 28.07.2020, at 10:11, > > thomas.g...@swisscom.com wrote: > > > > > > > > > > > > Dear lsr, > > > > > > > > > > > > > > I presented the following draft > > > > > > > > > > > >

Re: [Lsr] [OPSAWG] draft-tgraf-ipfix-mpls-sr-label-type

2020-08-16 Thread Gyan Mishra
their thoughts on complexity and caveats with getting the codepoints assigned. What about IPFIX SRv6 support? Comment on Section 2 A typical use case scenario is to monitor MPLS control plane migrations from LDP to IS-IS or OSPF. By looking at the MPLS label value itself, it is not alwa

Re: [Lsr] [OPSAWG] draft-tgraf-ipfix-mpls-sr-label-type

2020-08-15 Thread Gyan Mishra
ks.protection.outlook.com/?url=https%3A%2F%2Ftools.ietf.org%2Fhtml%2Fdraft-tgraf-ipfix-mpls-sr-label-type-04=02%7C01%7CThomas.Graf%40swisscom.com%7Cdef70609f2d843c24ad908d840d954dc%7C364e5b87c1c7420d9beec35d19b557a1%7C1%7C0%7C637330649465815966=1DIvkRCu5tKMVSooUnsF%2B5R1h12rVOkbYyYzqvKSgV4%3D=0> > > > > > > > > > > > > > > at the spring working group at IETF 108 yesterday > > > > > > > > https://www.ietf.org/proceedings/108/slides/slides-108-spring-ip-flow-information-export-ipfix-00.pdf > <https://eur03.safelinks.protection.outlook.com/?url=https%3A%2F%2Fwww.ietf.org%2Fproceedings%2F108%2Fslides%2Fslides-108-spring-ip-flow-information-export-ipfix-00.pdf=02%7C01%7CThomas.Graf%40swisscom.com%7Cdef70609f2d843c24ad908d840d954dc%7C364e5b87c1c7420d9beec35d19b557a1%7C1%7C0%7C637330649465815966=OM8BhFC%2FQJL3h%2FjqQPULt1c5SBTaz6yp%2Bj6i0QOjJJQ%3D=0> > > > > > > > > > > > > > > and today at OPSAWG where I call for adoption. > > > > > > > > > > > > > > This draft adds additional segment routing code points for in the IANA > IPFIX registry for IS-IS, OPSFv2 and OPSF v3 and segment routing SID types > to gain > > further insights into the MPLS-SR forwarding-plane. > > > > > > > > > > > > > > I have been asked to not only gather feedback from spring and opsawg but > also from lsr and mpls working groups since these code points are related > to link > > state routing protocols and mpls data plane. > > > > > > > > > > > > > > I am looking forward to your feedback and input. > > > > > > > > > > > > > > Best Wishes > > > > > > > Thomas Graf > > > > > ___ > > > Lsr mailing list > > > Lsr@ietf.org > > > https://www.ietf.org/mailman/listinfo/lsr > <https://eur03.safelinks.protection.outlook.com/?url=https%3A%2F%2Fwww.ietf.org%2Fmailman%2Flistinfo%2Flsr=02%7C01%7CThomas.Graf%40swisscom..com%7Cdef70609f2d843c24ad908d840d954dc%7C364e5b87c1c7420d9beec35d19b557a1%7C1%7C0%7C637330649465825923=PHRjGhYIP%2FLnBUvtjdbv%2FweQzspjf640vWDAovlS5Is%3D=0> > > > > > > > > > > > > > > > > > > > > ___ > > OPSAWG mailing list > > ops...@ietf.org > > https://www.ietf.org/mailman/listinfo/opsawg > > -- <http://www.verizon.com/> *Gyan Mishra* *Network Solutions A**rchitect * *M 301 502-134713101 Columbia Pike *Silver Spring, MD ___ Lsr mailing list Lsr@ietf.org https://www.ietf.org/mailman/listinfo/lsr

Re: [Lsr] draft-tgraf-ipfix-mpls-sr-label-type

2020-08-15 Thread Gyan Mishra
aft-tgraf-ipfix-mpls-sr-label-type-04=02%7C01%7CThomas.Graf%40swisscom.com%7Cb7d5f12ae9054d04978608d8407869f6%7C364e5b87c1c7420d9beec35d19b557a1%7C1%7C0%7C637330233200625087=q9GCxkzGIMx9p4WsXwITL4t1GMaP6dj6H4gu7hJAROY%3D=0> > > > > > > > > > > > > > > at

Re: [Lsr] [spring] draft-tgraf-ipfix-mpls-sr-label-type

2020-08-14 Thread Gyan Mishra
nts for in the IANA > IPFIX registry for IS-IS, OPSFv2 and OPSF v3 and segment routing SID types > to gain further insights into the MPLS-SR forwarding-plane. > > > > > > > > > > > > > > I have been asked to not only gather feedback from spring

Re: [Lsr] draft-ietf-lsr-isis-area-proxy-02

2020-08-06 Thread Gyan Mishra
e missing something. My understanding of SR is that you forward > based on the label. Please educate me. > > Tony > > ___ > Lsr mailing list > Lsr@ietf.org > https://www.ietf.org/mailman/listinfo/lsr > -- <http://www.veriz

Re: [Lsr] New Version Notification for draft-wang-lsr-prefix-unreachable-annoucement-03.txt

2020-08-06 Thread Gyan Mishra
rformance routing both at the > service itself or at BGP nh levels. Should IGP assist here ... I am not > sure. > > *[WAJ] when node become down, it can only depend on other nodes within the > same IGP to send such unreachability information. IGP can certainly help > here **J* &

Re: [Lsr] draft-ietf-lsr-isis-area-proxy-02

2020-08-05 Thread Gyan Mishra
ea Leader?* > > > > Does it matter? We have no clear semantics for this prefix. A difference > that makes no difference is no difference. > > Tony > > _______ > Lsr mailing list > Lsr@ietf.org > https://www.ietf.org/mailman

Re: [Lsr] WG adoption call for draft-li-lsr-isis-area-proxy-06

2020-06-15 Thread Gyan Mishra
lks who avoid the controller path > avoid other issues. > > Choose your battles… > > T > > ___ > Lsr mailing list > Lsr@ietf.org > https://www.ietf.org/mailman/listinfo/lsr > -- <http://www.verizon.com/> *Gyan Mishr

Re: [Lsr] WG adoption call for draft-przygienda-lsr-flood-reflection-01

2020-06-15 Thread Gyan Mishra
t; Chris and Acee. > > ___ > Lsr mailing list > Lsr@ietf.org > https://www.ietf.org/mailman/listinfo/lsr > -- <http://www.verizon.com/> *Gyan Mishra* *Network Solutions A**rchitect * *M 301 502-134713101 Columbia Pike *Silver Spring, MD ___ Lsr mailing list Lsr@ietf.org https://www.ietf.org/mailman/listinfo/lsr

Re: [Lsr] Call for WG adoption of https://tools.ietf.org/html/draft-przygienda-lsr-flood-reflection-01

2020-06-05 Thread Gyan Mishra
ble solution between vendors it will be the customer reality that > will drive deployment and ultimately what runs in their networks. > > > > thanks > > > > --- tony > _______ > Lsr mailing list > Lsr@ietf.org > https://www.ietf

Re: [Lsr] Flooding Topology Computation Algorithm - draft-cc-lsr-flooding-reduction-08 Working Group Adoption Call

2020-05-28 Thread Gyan Mishra
-------- > *From:* Gyan Mishra > *Sent:* Friday, May 22, 2020 9:11 PM > *To:* Huaimo Chen > *Cc:* Acee Lindem (acee) ; lsr@ietf.org > *Subject:* Re: [Lsr] Flooding Topology Computation Algorithm - > draft-cc-lsr-flooding-reduction-08 Working Group Adoption Call > >

Re: [Lsr] Flooding Topology Computation Algorithm - draft-cc-lsr-flooding-reduction-08 Working Group Adoption Call

2020-05-28 Thread Gyan Mishra
Les & Tony Please see my replies inline On Wed, May 27, 2020 at 1:49 PM Les Ginsberg (ginsberg) wrote: > Tony/Gyan – > > > > Please find my replies inline. > > > > *From:* Lsr *On Behalf Of * tony...@tony.li > *Sent:* Wednesday, May 20, 2020 8:48 AM > *T

Re: [Lsr] Flooding Topology Computation Algorithm - draft-cc-lsr-flooding-reduction-08 Working Group Adoption Call

2020-05-24 Thread Gyan Mishra
like to understand why one best solution draft we come up with for an FT algorithm for all possible physical topologies cannot be picked for WG adoption. Why would we want to adopt multiple flooding algorithms? Gyan On Sat, May 23, 2020 at 4:43 PM Gyan Mishra wrote: > > > On Fri, May 22, 20

Re: [Lsr] Flooding Topology Computation Algorithm - draft-cc-lsr-flooding-reduction-08 Working Group Adoption Call

2020-05-23 Thread Gyan Mishra
revalent in high density data center clos multi tier leaf spine parial mesh topologies that scale massive bandwidth breadth wise horizontally for E-W flows. > > Regards, > Tony > > -- <http://www.verizon.com/> *Gyan Mishra* *Netw

Re: [Lsr] Flooding Topology Computation Algorithm - draft-cc-lsr-flooding-reduction-08 Working Group Adoption Call

2020-05-22 Thread Gyan Mishra
at scenario where their is tremendous ECMP from partial meshing and how the flood reduction algorithm improves the flooding and convergence. Kind regards Gyan On Fri, May 22, 2020 at 8:41 PM Gyan Mishra wrote: > Hi Huaimo > > Thank you for the slide deck. That really helps understand the

Re: [Lsr] Flooding Topology Computation Algorithm - draft-cc-lsr-flooding-reduction-08 Working Group Adoption Call

2020-05-22 Thread Gyan Mishra
, May 22, 2020 at 10:05 AM Huaimo Chen wrote: > Hi Gyan, > > Thanks much for your questions. My answers/explanations are inline > below. > > Best Regards, > Huaimo > ------ > *From:* Gyan Mishra > *Sent:* Thursday, May 21, 2020 10:13 PM >

Re: [Lsr] Flooding Topology Computation Algorithm - draft-cc-lsr-flooding-reduction-08 Working Group Adoption Call

2020-05-21 Thread Gyan Mishra
rithm: > > > https://datatracker.ietf.org/meeting/interim-2020-lsr-01/materials/slides-interim-2020-lsr-01-sessa-2-dynamic-flooding-algo-sarah.pdf > > Thanks, > Sarah > > On Thu, May 21, 2020 at 7:32 PM Gyan Mishra wrote: > >> >> I see the diagrams Appendix A - revie

Re: [Lsr] Flooding Topology Computation Algorithm - draft-cc-lsr-flooding-reduction-08 Working Group Adoption Call

2020-05-21 Thread Gyan Mishra
I see the diagrams Appendix A - reviewing Thanks Gyan On Thu, May 21, 2020 at 10:13 PM Gyan Mishra wrote: > > I think for both drafts it would be good to have a stick diagram at a > minimum. > > I majored in EE with math minor and both drafts are hard to follow >

Re: [Lsr] Flooding Topology Computation Algorithm - draft-cc-lsr-flooding-reduction-08 Working Group Adoption Call

2020-05-21 Thread Gyan Mishra
rch spine leaf spine or leaf spine leaf. Kind regards Gyan On Thu, May 21, 2020 at 7:01 PM Acee Lindem (acee) wrote: > Hi Gyan, > > > > *From: *Gyan Mishra > *Date: *Thursday, May 21, 2020 at 4:20 PM > *To: *Acee Lindem > *Cc: *Huaimo Chen , "lsr@ietf.org" <

Re: [Lsr] Flooding Topology Computation Algorithm - draft-cc-lsr-flooding-reduction-08 Working Group Adoption Call

2020-05-21 Thread Gyan Mishra
s discussion late. It might be a good idea to > review the LSR mailing list archives. > > > > *From: *Gyan Mishra > *Date: *Thursday, May 21, 2020 at 1:51 PM > *To: *Huaimo Chen > *Cc: *Acee Lindem , "lsr@ietf.org" > *Subject: *Re: [Lsr] Flooding Topology Comp

Re: [Lsr] Flooding Topology Computation Algorithm - draft-cc-lsr-flooding-reduction-08 Working Group Adoption Call

2020-05-21 Thread Gyan Mishra
Computation Algorithm - > draft-cc-lsr-flooding-reduction-08 Working Group Adoption Call > > > > On Wed, May 20, 2020 at 11:59 PM Huaimo Chen > wrote: > > Hi Gyan, > > Thanks much for your questions. My answers are inline below with [HC].. > > Best Regards, &g

Re: [Lsr] Flooding Topology Computation Algorithm - draft-cc-lsr-flooding-reduction-08 Working Group Adoption Call

2020-05-21 Thread Gyan Mishra
On Wed, May 20, 2020 at 11:59 PM Huaimo Chen wrote: > Hi Gyan, > > Thanks much for your questions. My answers are inline below with [HC].. > > Best Regards, > Huaimo > -- > *From:* Gyan Mishra > *Sent:* Wednesday, May 20, 2020 11:14 AM

Re: [Lsr] draft-ietf-lsr-flex-algo

2020-05-20 Thread Gyan Mishra
On Wed, May 20, 2020 at 4:16 AM Peter Psenak wrote: > On 20/05/2020 00:37, Gyan Mishra wrote: > > > > > > > > On Tue, May 19, 2020 at 3:38 AM Peter Psenak > <mailto:ppse...@cisco.com>> wrote: > > > > Gyan, > > > > On 19/05

Re: [Lsr] Flooding Topology Computation Algorithm - draft-cc-lsr-flooding-reduction-08 Working Group Adoption Call

2020-05-20 Thread Gyan Mishra
paths. It can be used by > the area leader in the centralized mode to compute the flooding topology. > > Best Regards, > Huaimo > ------ > *From:* Lsr on behalf of Gyan Mishra < > hayabusa...@gmail.com> > *Sent:* Tuesday, May 19, 2020 2:39 AM > *To

Re: [Lsr] draft-ietf-lsr-flex-algo

2020-05-19 Thread Gyan Mishra
On Tue, May 19, 2020 at 3:38 AM Peter Psenak wrote: > Gyan, > > On 19/05/2020 03:52, Gyan Mishra wrote: > > > > Flex algo is usually mentioned in the context of SR-TE to help reduced > > SRH size to circumvent MSD issues for both SRV6 and SR-MPLS, > > though s

Re: [Lsr] Flooding Topology Computation Algorithm - draft-cc-lsr-flooding-reduction-08 Working Group Adoption Call

2020-05-19 Thread Gyan Mishra
tatracker.ietf.org/doc/draft-cc-lsr-flooding-reduction/ > > > > Thanks, > Acee > ___ > Lsr mailing list > Lsr@ietf.org > https://www.ietf.org/mailman/listinfo/lsr > -- <http://www.verizon.

Re: [Lsr] Flooding across a network

2020-05-19 Thread Gyan Mishra
two nodes to prevent a fast sender from overwhelming a slow receiver. It > provides a mechanism for the receiver to control the transmission speed, so > that the receiving node is not overwhelmed with data from transmitting > node.” > > > > That’s what we are working on. > >

Re: [Lsr] draft-ietf-lsr-flex-algo

2020-05-18 Thread Gyan Mishra
uct a end to end SR path/tunnel > without SRH, but it still meet TE requirement. So my question is whether > the flex-algo can be used as tool to reduce SRH size? > > > > > > > > *Cheers !* > > > > *WANG Weibin* > > ___ > Lsr mailing lis

Re: [Lsr] Flooding across a network

2020-05-17 Thread Gyan Mishra
> > > > > > > Quoting you “when only some nodes in the network support faster > > > > flooding the behavior of the whole network may not be "better" when > faster > > > > flooding is enabled because it prolongs the period of LSDB > inco

[Lsr] LSR Interim meeting webex link

2020-04-29 Thread Gyan Mishra
-- Gyan Mishra Network Engineering & Technology Verizon Silver Spring, MD 20904 Phone: 301 502-1347 Email: gyan.s.mis...@verizon.com ___ Lsr mailing list Lsr@ietf.org https://www.ietf.org/mailman/listinfo/lsr

Re: [Lsr] Using IS-IS Multi-Topology (MT) for Segment Routing basedVirtual Transport Network

2020-03-29 Thread Gyan Mishra
raft related to using the RSVP extensions for IP based source routing for SR. This may help in having to develop new extensions for VPN+ https://tools.ietf.org/html/draft-saad-teas-rsvpte-ip-tunnels-00 Kind regards Gyan On Sun, Mar 29, 2020 at 5:13 PM Gyan Mishra wrote: > > Hi Chongfeng &

Re: [Lsr] Using IS-IS Multi-Topology (MT) for Segment Routing basedVirtual Transport Network

2020-03-29 Thread Gyan Mishra
ee how a L2 bundle >> link >> > member would ever become part of the L3 topology. >> > > >> > > my 2c, >> > > Peter >> > > >> > > >> > >> At this point, if we needed to extend RFC 8668 to support MTID we >> would >> > need to allocate an additional TLV code point that included MTID – >> similar to >> > the distinction between TLV 22 and TLV 222. >> > >> HTH >> > >>Les >> > >> *From:* Lsr *On Behalf Of * Tony Przygienda >> > >> *Sent:* Saturday, March 28, 2020 10:25 AM >> > >> *To:* peng.shaofu@ >> > >> > ___ >> > Lsr mailing list >> > Lsr@ietf.org >> > https://www.ietf.org/mailman/listinfo/lsr >> > ___ > Lsr mailing list > Lsr@ietf.org > https://www.ietf.org/mailman/listinfo/lsr > -- Gyan Mishra Network Engineering & Technology Verizon Silver Spring, MD 20904 Phone: 301 502-1347 Email: gyan.s.mis...@verizon.com ___ Lsr mailing list Lsr@ietf.org https://www.ietf.org/mailman/listinfo/lsr

Re: [Lsr] WG Adoption Call for draft-ketant-lsr-ospf-reverse-metric

2019-12-16 Thread Gyan Mishra
I support. Gyan On Fri, Dec 13, 2019 at 1:35 PM Jeff Tantsura wrote: > I support the adoption, finally OSPF would catch up with IS-IS ;-) > > Cheers, > Jeff > On Dec 13, 2019, 3:28 AM -0800, Christian Hopps , > wrote: > > Hi LSR WG and Draft Authors, > > This begins a 2 week WG adoption poll

Re: [Lsr] LSR Working Group Virtual Interim on Dynamic Flooding

2019-05-18 Thread Gyan Mishra
I will plan to join. Thank you Gyan S. Mishra IT Network Engineering & Technology Verizon Communications Inc. (VZ) 13101 Columbia Pike FDC1 3rd Floor Silver Spring, MD 20904 www.linkedin.com/in/GYAN-MISHRA-RS-SP-MPLS-IPV6-EXPERT Phone: 301 502-1347 Email: gyan.s.mis...@verizon.com Sent

Re: [Lsr] Mirja Kühlewind's No Objection on draft-ietf-isis-segment-routing-extensions-24: (with COMMENT)

2019-05-18 Thread Gyan Mishra
18, 2019, at 10:53 AM, Gyan Mishra wrote: > > Les > > I did some reading and research and lab testing of SR on CISCO XR nodes > physical hardware and VIRL (virtual internet routing lab) and now I know why > the top section says IPv6 and MPLS data planes. > > So IPv6 data

Re: [Lsr] 答复: Working Group Adoption Call for "IS-IS Extensions to Support Routing over IPv6 Dataplane" - draft-bashandy-isis-srv6-extensions-05.txt

2019-05-18 Thread Gyan Mishra
pring, MD 20904 www.linkedin.com/in/GYAN-MISHRA-RS-SP-MPLS-IPV6-EXPERT Phone: 301 502-1347 Email: gyan.s.mis...@verizon.com Sent from my iPhone > On May 15, 2019, at 3:03 AM, Yingzhen Qu wrote: > > Support. > > -- > Thanks, > Yingzhe

Re: [Lsr] Mirja Kühlewind's No Objection on draft-ietf-isis-segment-routing-extensions-24: (with COMMENT)

2019-05-18 Thread Gyan Mishra
but not native non mpls IPv4 data planes. Maybe some other verbiage would be good per what I mentioned here but if not now I understand why it says IPv6 and MPLS data planes. Gyan Sent from my iPhone > On May 17, 2019, at 3:08 AM, Gyan Mishra wrote: > > Les > > I agree the document

Re: [Lsr] Flooding Negotiation bit

2019-05-17 Thread Gyan Mishra
pacing to refresh LSA so full SPF does not have to run on all nodes as root of tree at once. Gyan Gyan S. Mishra IT Network Engineering & Technology Verizon Communications Inc. (VZ) 13101 Columbia Pike FDC1 3rd Floor Silver Spring, MD 20904 www.linkedin.com/in/GYAN-MISHRA-RS-SP-MPLS-IPV6-EX

Re: [Lsr] Mirja Kühlewind's No Objection on draft-ietf-isis-segment-routing-extensions-24: (with COMMENT)

2019-05-17 Thread Gyan Mishra
signaling (other than the regular IGP) Wording seems misleading leaving out IPv4. Gyan Mishra Verizon Communications Phone: 301 502-1347 On Wed, May 15, 2019 at 1:02 AM Les Ginsberg (ginsberg) wrote: > Gyan - > > The paragraph you cut and pasted is providing a short overview of Segment > Ro

Re: [Lsr] Mirja Kühlewind's No Objection on draft-ietf-isis-segment-routing-extensions-24: (with COMMENT)

2019-05-16 Thread Gyan Mishra
to eliminate support for it > in the signaling. > Being able to support it does not require folks to deploy it of course. > > Les > > >> -----Original Message- >> From: Gyan Mishra >> Sent: Tuesday, May 14, 2019 7:23 PM >> To: Mirja Kühlewind

Re: [Lsr] I-D Action: draft-ietf-isis-mpls-elc-07.txt

2019-05-14 Thread Gyan Mishra
Is the EL signaling for ecmp supported with IP LFA and remote LFA LDP label stacking interoperability. Gyan Mishra Verizon Communications Phone 301 502-1347 Sent from my iPhone > On May 14, 2019, at 3:34 AM, internet-dra...@ietf.org wrote: > > > A New Internet-Draft is av

Re: [Lsr] Mirja Kühlewind's No Objection on draft-ietf-isis-segment-routing-extensions-24: (with COMMENT)

2019-05-14 Thread Gyan Mishra
bits of the Prefix-SID are not preserved to the ultimate hop (the Prefix-SID being removed). If the P-flag is unset the received E-flag is ignored. Gyan Mishra Verizon Communications Phone: 301 502-1347 Sent from my iPhone > On May 14, 2019, at 10:09 PM, Gyan Mishra wr

Re: [Lsr] Mirja Kühlewind's No Objection on draft-ietf-isis-segment-routing-extensions-24: (with COMMENT)

2019-05-14 Thread Gyan Mishra
ed in MPLS networks, SR paths do not require any LDP or RSVP-TE signaling. Still, SR can interoperate in the presence of LSPs established with RSVP or LDP. Gyan Mishra Verizon Communications Phone: 301 502-1347 Sent from my iPhone > On May 14, 2019, at 7:58 AM, Mirja Kühlewind via Datatrac

Re: [Lsr] Flooding Negotiation bit

2019-05-14 Thread Gyan Mishra
Inc. (VZ) 13101 Columbia Pike FDC1 3rd Floor Silver Spring, MD 20904 www.linkedin.com/in/GYAN-MISHRA-RS-SP-MPLS-IPV6-EXPERT Phone: 301 502-1347 Email: gyan.s.mis...@verizon.com Sent from my iPhone > On May 14, 2019, at 4:31 PM, tony...@tony.li wrote: > > > Hi Huaimo, > &g