Opened 7 years ago

Last modified 7 years ago

#11 new defect

MUST for site diversity?

Reported by: michael.scharf@… Owned by: draft-ietf-l3sm-l3vpn-service-model@…
Priority: trivial Milestone: milestone1
Component: l3vpn-service-model Version: 2.0
Severity: Active WG Document Keywords:


Section 6 states:

As described in Section 5.2.1, the management system MAY
use the location information and MUST use the site-diversity
constraint to find the appropriate PE.

Actually, perhaps this MUST for site-diversity could be turned into a SHOULD, because Section states on site-diversity:

How these diversity constraints are applied is out of scope of the document.

I am not convinced that a MUST on an unspecified mechanism really makes sense, and since this also does not affect the YANG model, the solution to this aspect could be simple...

Change History (2)

comment:1 Changed 7 years ago by stephane.litkowski@…

Agree that we can move it to a SHOULD.

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.