There are some points needs to be clarified before it adoption: 1. In section 4.3 of this draft, it says: "The OSPF transport instance is not dependent on any other OSPF instance. It does, however, have much of the same as topology information must be advertised to satisfy the "condition of reachability". Then, this transport instance should also advertise the topology information. Right? But in section 4.5, the advertisement of inter-area information is omitted(Summary-LSA for OSPFv2/inter-area-prefix-LSA for OSPFv3). So, how to transfer the non-routing information across different areas? Using the remote OSPF neighbor?
2. The reason that we use the IGP to transfer the non-routing information is that the IGP assures the reachability/dissemination of such information. Using independent transport instance, the operator need again the design and deployment of the distributed topology. And most important, the correlation between the routing information and non-routing information is not solved or covered within the current draft, which is the merit of other solutions. There should be solutions/considerations to the possible problem as that described in https://datatracker.ietf.org/doc/html/draft-bowers-lsr-isis-gen-info-clarifi cations-00 for IS-IS. 3. Section 4.7 described the "Non-Routing Sparse Topologies". It requires again the careful design and deployment. Is it more straightforward to let the IGP routers relay such information and only the necessary nodes to store/utilize it? Best Regards Aijun Wang China Telecom -----Original Message----- From: [email protected] <[email protected]> On Behalf Of Christian Hopps Sent: Sunday, May 2, 2021 4:39 PM To: [email protected] Cc: [email protected]; [email protected]; [email protected] Subject: [Lsr] WG adoption call for draft-acee-lsr-ospf-transport-instance-02 This begins a 2 week WG adoption call for the following draft: https://datatracker.ietf.org/doc/draft-acee-lsr-ospf-transport-instance/ Please indicate your support or objection by May 16th, 2021. Authors, please respond to the list indicating whether you are aware of any IPR that applies to this draft. Historical Note: The original OSPF transport instance document was adopted by the OSPF WG back in 2009, it was last updated in 2014, and then revived as an individual submission to LSR in Sep 2020. :) Thanks, Chris. _______________________________________________ Lsr mailing list [email protected] https://www.ietf.org/mailman/listinfo/lsr _______________________________________________ Lsr mailing list [email protected] https://www.ietf.org/mailman/listinfo/lsr
