Opened 7 years ago
Last modified 7 years ago
#3 new enhancement
M to N availability support
Reported by: | bill.wu@… | Owned by: | Site Availability |
---|---|---|---|
Priority: | minor | Milestone: | milestone1 |
Component: | l3vpn-service-model | Version: | 2.0 |
Severity: | Active WG Document | Keywords: | |
Cc: |
Description
In v(-01),Site Availability support primary-back,loadsharing,single.
In prague meeting, Kireeti Kompella brought up a case where there is M primary,N backup,loading sharing among M primary, N backups for backup, do we support M to N availability in service model? How do we support it?
One relevant question is,In v(-01), can one site provide more than one attachment? If not, how do we know one site offering backup access is used for another site offering primary access?
Change History (1)
comment:1 Changed 7 years ago by bill.wu@…
- Component changed from draft-ltsd-l3sm-l3vpn-service-model to l3vpn-service-model
- Milestone set to milestone1
- Severity changed from - to Active WG Document
- Version set to 2.0
Note: See
TracTickets for help on using
tickets.