Opened 7 years ago

Last modified 7 years ago

#10 new enhancement

VPN policy : how to handle VPN merging easily

Reported by: stephane.litkowski@… Owned by: draft-ietf-l3sm-l3vpn-service-model@…
Priority: major Milestone: milestone1
Component: l3vpn-service-model Version: 2.0
Severity: Active WG Document Keywords:
Cc:

Description

In the current model , VPN is a per-site property. VPN policy is defined within the site allowing a site to belong to multiple VPNs with different roles.

There are some cases where two existing VPNs with many sites would need interconnection between them.
With the current model we may need to update all the sites of each VPN.
There was a proposal on the list to create a vpn-policy at vpn level to describe easily the interconnection of two VPNs.
There are some implication on translation of both vpn and site vpn-policy to correct device configuration and this require a strong look.

Change History (2)

comment:1 in reply to: ↑ description Changed 7 years ago by bill.wu@…

Replying to stephane.litkowski@…:

In the current model , VPN is a per-site property. VPN policy is defined within the site allowing a site to belong to multiple VPNs with different roles.

There are some cases where two existing VPNs with many sites would need interconnection between them.
With the current model we may need to update all the sites of each VPN.
There was a proposal on the list to create a vpn-policy at vpn level to describe easily the interconnection of two VPNs.
There are some implication on translation of both vpn and site vpn-policy to correct device configuration and this require a strong look.

VPN policy is about exchange route among VPNs, I agree it has relation with VPNs interconnection.

Can we address this issue with your inventory ops state proposal? It is up to whether inventory ops state is put at VPN level or site level, right?

comment:2 Changed 7 years ago by bill.wu@…

  • Component changed from draft-ltsd-l3sm-l3vpn-service-model to l3vpn-service-model
  • Milestone set to milestone1
  • Owner changed from draft-ltsd-l3sm-l3vpn-service-model@… to draft-ietf-l3sm-l3vpn-service-model@…
  • Severity changed from - to Active WG Document
  • Version set to 2.0
Note: See TracTickets for help on using tickets.