At Thu, 6 Feb 2014 15:20:58 +0000, David Allan I wrote: > I don’t think it actually matters how many are in an encapsulated > stack. I could think of a use case (BBF TR-101) where NVO3 was used > between a BNG and a VAP where I would want to be able to encapsulate a > tag stack. So I'd not want to restrict it.
I tend to agree. The point is that whatever tag or tags are carried end-to-end can be (and should be) transparent to NVO3 and NVO3 doesn't use them to influence forwarding. If it is useful to preserve tags end-to-end for use at the VAPs, why not? What actual tags are supported (e.g., nested) would be an issue more for the encap/VAP. While I wouldn't want to get carried away and suggest all possible imaginable combinations of tags should be supported, I don't see any reason to be particularly restrictive in the architecture. Thomas _______________________________________________ nvo3 mailing list [email protected] https://www.ietf.org/mailman/listinfo/nvo3
