Subject: Re: [L3sm] [l3sm] #9 (draft-ltsd-l3sm-l3vpn-service-model): Do we need to model transport constraints between sites ?

From: "l3sm issue tracker" <[email-masked]>
Date: Tue, 01 Dec 2015 09:54:54 -0000

#9: Do we need to model transport constraints between sites ?

Comment (by [email-masked]):

 To model transport constraints, there are two proposals on the table:
 Now regarding modeling of the transport constraint, I do not see a real
 sexy way for now.
  Proposal #1 :
         Create a transport-constraint container within the vpn-svc to
 describe the constraints. Example :

 rw vpn-svc
     +--rw transport-constraint
                +--rw list [id]
                       +--rw id                uint32
                       +--rw src-site     leafref
                       +--rw dst-site    leafref
                       +--rw constraint-type        identityref
                       +--rw constraint-value      ???

 => constraint-value may have a variable type depending of the constraint-
 type, for example, expressing latency boundary, or disjointness group ...

 Proposal#2 :
         Put the constraint in the site

 rw site
   +--rw services
         +--rw transport-constraint
              +--rw  dst-site-list         [dst-site]
                       +--rw dst-site                        leafref
                       +--rw constraint-type        identityref
                       +--rw constraint-value      ???

 Thoughts ?

 You also can review these two proposal from the following link:
 https://mailarchive.ietf.org/arch/msg/l3sm/qakWoaP0lt_HMNZFkDoNOctMOyw

 Replying to [comment:1 michael.scharf@…]:
 > I think that would be useful input to the SDN controller realizing the
 connectivity.
 >
 > The key question is if there is a simple and abstract way to model those
 customer requirements. It is relatively simply to model constraints for
 the L3VPN as a whole (e.g., that all sites should be connected with lowest
 possible latency), but for connectivity between specific sites an abstract
 specification could be a bit more challenging.
 > Michael

-- 
-------------------------------------+-------------------------------------
 Reporter:                           |       Owner:  draft-ltsd-l3sm-l3vpn-
  [email-masked]      |  [email-masked]
     Type:  enhancement              |      Status:  new
 Priority:  minor                    |   Milestone:
Component:  draft-ltsd-l3sm-l3vpn-   |     Version:
  service-model                      |  Resolution:
 Severity:  -                        |
 Keywords:                           |
-------------------------------------+-------------------------------------

Ticket URL: <https://trac.tools.ietf.org/wg/l3sm/trac/ticket/9#comment:2>
l3sm <https://tools.ietf.org/l3sm/>