Re: [PWE3] PWE3 new WG items? PW QoS

[Luca Martini <lmartini at cisco.com>]

Busschbach, Peter B (Peter) wrote:

[snip]

> I would agree that if QoS were the only problem that needs to be solved it could be acceptable to carry QoS information in the LDP messages that are used for PW setup (albeit that it is somewhat ugly since it makes LDP look like CR-LDP which has been depreciated).
>
> However, there are other issues that need to be solved. Several people on this mailing list suggested that we need to address PW stitching. It seems to me that stitching of PWs requires a signaling protocol that establishes a multi-hop PW through switches that switch based on the PW label. RSVP is in my view the only reasonable solution.
>
> Hence, if we don't look at one problem at a time, but at the entire problem space, I think we need to adopt RSVP as a way to establish PWs. It would solve the problems of both QoS and stitching.
>
> Peter
>
>  
Peter,
It is possible ( I already know of one implementation ) to select an 
RSVP LSP to transport a single PW.
That does not change the protocol , and does carry QoS information 
needed by the PSN. It also achieves another property that as it turns 
out is quite useful in practice: explicit routing of the PW across the 
PSN. ( this is for TE , but also other reasons like avoiding shared PSN 
failure modes )

Luca

> _______________________________________________
> pwe3 mailing list
> pwe3@ietf.org
> https://www1.ietf.org/mailman/listinfo/pwe3
>
>  

_______________________________________________
pwe3 mailing list
pwe3@ietf.org
https://www1.ietf.org/mailman/listinfo/pwe3