Hi all, Some deployments may imply some dynamicity in the terminating points of a service (e.g., containers). Providing stable AC references for the service that uses such ACs, while allowing to managing such dynamic AC is worth to consider.
Leveraging the ac-group-profile and allowing for these profiles to be referenced by a service is one option but this would mean that the service has to manipulate two reference types. An alternate approach is to minimize the implications on the service and allow for an AC to inherit properties of another AC; only one reference is needed for a service to be bound to an AC (and the inheriting ones). The full issue (including an example) is described here: https://github.com/boucadair/attachment-circuit-model/issues/14 Please review and share your comments. Cheers, Med ____________________________________________________________________________________________________________ Ce message et ses pieces jointes peuvent contenir des informations confidentielles ou privilegiees et ne doivent donc pas etre diffuses, exploites ou copies sans autorisation. Si vous avez recu ce message par erreur, veuillez le signaler a l'expediteur et le detruire ainsi que les pieces jointes. Les messages electroniques etant susceptibles d'alteration, Orange decline toute responsabilite si ce message a ete altere, deforme ou falsifie. Merci. This message and its attachments may contain confidential or privileged information that may be protected by law; they should not be distributed, used or copied without authorisation. If you have received this email in error, please notify the sender and delete this message and its attachments. As emails may be altered, Orange is not liable for messages that have been modified, changed or falsified. Thank you.
_______________________________________________ OPSAWG mailing list [email protected] https://www.ietf.org/mailman/listinfo/opsawg
