Re: [Lsr] LSR WG Adoption Poll for "IS-IS Topology-Transparent Zone" - draft-chen-isis-ttz-11.txt
Support. Thanks, Yanhe From: Lsr On Behalf Of Acee Lindem (acee) Sent: Tuesday, August 18, 2020 10:17 AM To: lsr@ietf.org Subject: [Lsr] LSR WG Adoption Poll for "IS-IS Topology-Transparent Zone" - draft-chen-isis-ttz-11.txt Based on the discussions in the last meeting and on the mailing list regarding draft-chen-isis-ttz-11, the chairs feel that there are enough differences with draft-ietf-lsr-isis-area-proxy-03 and in the community to consider advancing it independently on the experimental track. These differences include abstraction at arbitrary boundaries and IS-IS extensions for smooth transition to/from zone abstraction. We are now starting an LSR WG adoption call for draft-chen-isis-ttz-11.txt. Please indicate your support or objection to adoption prior to Tuesday, September 2nd, 2020. Thanks, Acee and Chris ___ Lsr mailing list Lsr@ietf.org https://www.ietf.org/mailman/listinfo/lsr
Re: [Lsr] LSR WG IPR Poll for "IS-IS Topology-Transparent Zone" - draft-chen-isis-ttz.txt
I’m not aware of any IPR associated this draft. Thanks, Yanhe From: Acee Lindem (acee) Sent: Tuesday, August 18, 2020 10:24 AM To: draft-chen-isis-...@ietf.org Cc: lsr@ietf.org Subject: LSR WG IPR Poll for "IS-IS Topology-Transparent Zone" - draft-chen-isis-ttz.txt Authors, The IETF IPRs declarations submitted for draft-chen-isis-ttz are specified here: https://datatracker.ietf.org/ipr/4029/ Are you aware of any other IPR that applies to draft-chen-isis-ttz? If so, has this IPR been disclosed in compliance with IETF IPR rules (see RFCs 3979, 4879, 3669 and 5378 for more details). If you are listed as a document author or contributor please respond to this email regardless of whether or not you are aware of any relevant IPR. *The response needs to be sent to the LSR WG mailing list.* The document will not advance to the next stage until a response has been received from each author and contributor. If you are on the LSR WG email list but are not listed as an author or contributor, then please explicitly respond only if you are aware of any IPR that has not yet been disclosed in conformance with IETF rules. Thanks, Acee ___ Lsr mailing list Lsr@ietf.org https://www.ietf.org/mailman/listinfo/lsr
Re: [Lsr] Request WG adoption of TTZ
I support adaption of this IS-IS TTZ draft. It is a useful work to address network scalability. Thanks, Yanhe -Original Message- From: Lsr On Behalf Of Donald Eastlake Sent: Friday, July 10, 2020 1:08 PM To: Huaimo Chen Cc: lsr@ietf.org; lsr-cha...@ietf.org Subject: Re: [Lsr] Request WG adoption of TTZ I support adoption of the IS-IS TTZ draft. It seems more flexible and capable although some editorial/nomenclature improvements in the draft would be good. I will send some more detailed suggestions to the authors. Thanks, Donald === Donald E. Eastlake 3rd +1-508-333-2270 (cell) 2386 Panoramic Circle, Apopka, FL 32703 USA d3e...@gmail.com On Thu, Jun 18, 2020 at 11:38 PM Huaimo Chen wrote: > > Hi Chris and Acee, and everyone, > > > > I would like to request working group adoption of "Topology-Transparent > Zone" > > (TTZ for short) https://datatracker.ietf.org/doc/draft-chen-isis-ttz/ . > > > This draft comprises the following solutions for helping to improve > scalability: > > 1) abstracting a zone to a single pseudo node in IS-IS, > > 2) abstracting a zone to a single pseudo node in OSPF, > > 3) abstracting a zone to zone edges' full mess in IS-IS, and > > 4) transferring smoothly between a zone and a single pseudo node. > > A zone is a block of an area (IS-IS L2 or L1 area, OSPF backbone > or > > non-backbone area). > > > > When a network area becomes (too) big, we can reduce its size in > the sense > > of its LSDB size through abstracting a zone to a single pseudo node or > > abstracting a few zones to a few pseudo nodes. > > > > While a zone is being abstracted (or transferred) to a single > pseudo node, > > the network is stable. There is no or minimum service interruption. > > > > After abstracting a few zones to a few pseudo nodes, if we want to > reconstruct > > them, we can transfer (or roll) any of the pseudo nodes back to its > zone smoothly > > with no or minimum service interruption. > > > > We had a prototype implementation of abstracting a zone to zone > edges' full > > mess in OSPF. The procedures and related protocol extensions for > transferring > > smoothly from a zone to zone edges' full mess are implemented and tested. > > A zone (block of an OSPF area) is smoothly transferred to its edges’ > full mess > > without any routing disruptions. The routes on every router are stable > while > > the zone is being transferred to its edges' mess. It is very easy to > operate > > the transferring. > > > > There are two other drafts for improving scalability: "Area Proxy for > IS-IS" > > (Area Proxy for short) and "IS-IS Flood Reflection" (Flood Reflection for > short). > > > > "Area Proxy" > https://tools.ietf.org/html/draft-li-lsr-isis-area-proxy-03 > > abstracts an existing IS-IS L1 area to a single pseudo node. > > > > "Flood Reflection" > https://tools.ietf.org/html/draft-przygienda-lsr-flood-reflection-01 > > abstracts an existing IS-IS L1 area to its edges' connections via one > or more > > flood reflectors. > > > > We believe that TTZ has some special advantages even though > > Area Proxy and Flood Reflection are very worthy. We would like > > to ask for working group adoption of TTZ. > > > > Best Regards, > > Huaimo > > ___ > 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 ___ Lsr mailing list Lsr@ietf.org https://www.ietf.org/mailman/listinfo/lsr
Re: [Lsr] Flooding Topology Computation Algorithm - draft-cc-lsr-flooding-reduction-08 IPR Poll
I’m not aware of any IPR that applies to draft-cc-lsr-flooding-reduction-08.txt. Thanks, Yanhe From: Acee Lindem (acee) Sent: Friday, May 15, 2020 3:47 PM To: draft-cc-lsr-flooding-reduct...@ietf.org Cc: lsr@ietf.org Subject: Flooding Topology Computation Algorithm - draft-cc-lsr-flooding-reduction-08 IPR Poll Authors, Are you aware of any IPR that applies to draft-cc-lsr-flooding-reduction-08.txt. If so, has this IPR been disclosed in compliance with IETF IPR rules (see RFCs 3979, 4879, 3669 and 5378 for more details). If you are listed as a document author or contributor please respond to this email regardless of whether or not you are aware of any relevant IPR. *The response needs to be sent to the LSR WG mailing list.* The document will not advance to the next stage until a response has been received from each author and contributor. If you are on the LSR WG email list but are not listed as an author or contributor, then please explicitly respond only if you are aware of any IPR that has not yet been disclosed in conformance with IETF rules. Thanks, Acee ___ Lsr mailing list Lsr@ietf.org https://www.ietf.org/mailman/listinfo/lsr
Re: [Lsr] Flooding Topology Computation Algorithm - draft-cc-lsr-flooding-reduction-08 Working Group Adoption Call
Support it as a co-author. Thanks, Yanhe From: Lsr On Behalf Of Acee Lindem (acee) Sent: Friday, May 15, 2020 3:40 PM To: lsr@ietf.org Subject: [Lsr] Flooding Topology Computation Algorithm - draft-cc-lsr-flooding-reduction-08 Working Group Adoption Call This begins a 3 week (due to holidays) WG adoption call for the “Flooding Topology Computation Algorithm” draft. Please issue your support or objection to this list by 11:59 PM, UTC on June 5th, 2020. Here is a URL for your convenience. https://datatracker.ietf.org/doc/draft-cc-lsr-flooding-reduction/ Thanks, Acee ___ Lsr mailing list Lsr@ietf.org https://www.ietf.org/mailman/listinfo/lsr
