OlgaHuawei
commented
1 year ago We will not address this comment in yang this until the RFC8345 is extended to support links between multiple areas.
Open OlgaHuawei opened 1 year ago
OlgaHuawei
commented
1 year ago We will not address this comment in yang this until the RFC8345 is extended to support links between multiple areas.
IS-IS model can be changed to have OSPF areas as networks when RFC8345 is improved.
The draft draft-havel-opsawg-digital-map-00 talks about the Digital Map modelling experience and what we believe is missing in the basic RFC8345 model. One of the things identified as missing is links between networks, as links can belong to 1 network only. We modelled IS-IS areas as networks in our PoC and there was an issue how to model the links between different OSPF areas. We added network-id as ref as well for the destination . IS-IS model can be changed to have OSPF areas as networks when RFC8345 is improved, the effort has started to come up with drafts to propose backward compatible solutions for all of the things identified as missing from RFC8345. The links between the networks will be one of the proposals.
The following is the text from the draft-havel-opsawg-digital-map-00 draft: [6.1.3. ][Links Between Networks] The RFC8345 defines all links as belonging to one network instance and having the source and destination as node and termination point only, not allowing to link to termination point of another network. This does not allow for links between networks in the case of multi-domains or partitioning. The only way would be to model each domain as node and have links between them.
We modelled OSPF and IS-IS Areas as networks during the PoC and we needed to extend the capability to have links between different areas. We added network reference as well to the source / destination of the link. The RFC8795 also augments links with external-domain info for the case of links that connect different domains.