Hi, dear all. We have updated two drafts related with the DC fabic recently.
The first is about service model which is used by the orchestration in order to get the service information from users. In the updated version, we modified the usage architecture for the easy understanding. Besides we think it's different from topology models from TEAS. Teas pay attention on the traffic engineering rather than DC deployment, while fabric model is focused on DC network with its details such as spine-leaf architecture and switches and routers deployment. The second is about fabric topology model which is the topology information in DC fabric. We delete the RPC parts in consideration of security. Fabric service model and fabric topology model faces to different levels of network. By combining these two, we can get the DC network deployment much easier. Here are the links of these two drafts. https://datatracker.ietf.org/doc/html/draft-zhuang-i2rs-dc-fabric-service-model https://datatracker.ietf.org/doc/html/draft-zhuang-i2rs-yang-dc-fabric-network-topology Any comments are welcomed. Best regards. Gu Rong [email protected] [email protected]
_______________________________________________ i2rs mailing list [email protected] https://www.ietf.org/mailman/listinfo/i2rs
