When a NVE is initialized or re-started, it uses Virtual Network scoped instances of the IS-IS to announce all the Virtual Networks in which it is participating.
The current draft-dunbar-nvo3-nva-mapping-distribution-01 suggests using the bit map to represent the supported VNs. +-+-+-+-+-+-+-+-+ | Type | (1 byte) +-+-+-+-+-+-+-+-+ | Length | (1 byte) +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ | RESV | Start VN ID | (2 bytes) +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ | VNID bit-map.... +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ Figure 2. Enabled-VN TLV For 24-bits VN ID, there could be 16million VNs. Even with the "Start VN ID" listed, the number of bytes for the bitmap can be very large. Therefore, I think it is better to have a flag indicating if the VNs are listed individually, Upper/Lower ranges, or bit mapped. Any other suggestions? Linda
_______________________________________________ nvo3 mailing list [email protected] https://www.ietf.org/mailman/listinfo/nvo3
