Hi all,

The structure of the ip-connection in the spec is inherited from LxNM, which 
reflect most deployments I'm aware of. Only one single local IP address is 
allowed for an AC as shown in the following tree:

        | ...
        +--rw ip-connection
        |  +--rw ipv4 {vpn-common:ipv4}?
        |  |  ...
        |  +--rw ipv6 {vpn-common:ipv6}?
        |     +--rw local-address?          inet:ipv6-address
        |     +--rw virtual-address?        inet:ipv6-address
        |     +--rw prefix-length?                 uint8
        |     +--rw address-allocation-type?       identityref
        |     +--rw (allocation-type)?
        |        +--:(dynamic)
        |        |  +--rw (address-assign)?
        |        |  |  ...
        |        |  +--rw (provider-dhcp)?
        |        |  |  ...
        |        |  +--rw (dhcp-relay)?
        |        |     ...
        |        +--:(static-addresses)
        |           ...
           ...

We used to have an issue about whether we need to define this as a list to 
address corner deployment cases such as migration. An option to address this 
issue without modifying the current structure is to instantiate two ACs, but 
will need to check if this has not impacts on the referencing at the service 
level.

The issue is tracked here : 
https://github.com/boucadair/attachment-circuit-model/issues/6

Please review and let us know if you think this issue is valid and share any 
preference you have.

Thank you.

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

Reply via email to