[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
RE: [PWE3] PWE3 new WG items?
> Signaling of the QOS parameters that is specific to
> a given PW-FEC falls within the charter of PWE3 as
> it is an attribute of a PW-FEC.
>
> This is my understanding.
Well, I would say that as:
1) PWs are basically LSPs (and therefore they inherit all the properties of a LSP and add their own PW specific properties)
2) PW signalling is an extension to LSP signalling (and therefore it inherits all the properties of LSP signalling and adds its own PW specific properties)
The problem of signalling QoS parameters is not a PW specific problem and therefore should not be addressed by the PWE3 WG.
If the QoS signalling mechanisms that exist already (e.g. CR-LDP) are adequate then why not re-use them for PWs because PWs should automatically inherit any traffic parameters signalled at the same time as the PW-FEC? If the existing QoS signalling mechanisms are not adequate then fix them but in such a way that they can be used for MPLS LSPs and PWs.
IMO defining PW specific QoS signalling just limits the amount of functional convergence/re-use that can be achieved and therefore increases the complexity of any solution (and by implication increases the opex for any service provider wishing to deploy that solution).
Unfortunately CR-LDP has been deprecated so the opportunities for functional convergence/re-use are more limited and it looks like re-inventing the wheel[1] is one possible (although I would consider it to be an undesirable) solution :-(
Ben
[1] either the PW signalling wheel (e.g. add PW signalling to RSVP-TE) or the LDP QoS wheel (e.g. add QoS signalling to LDP).
_______________________________________________
pwe3 mailing list
pwe3@ietf.org
https://www1.ietf.org/mailman/listinfo/pwe3