The MPLS WG Archive

["M.N.V.Suryanarayana" <suryam@future.futsoft.com>]

Hi,

Can someone provide an example in which the interface switching capability
is set to PSC-2/PSC-3/PSC-4. The examples in section 7 of
draft-ietf-ccamp-gmpls-routing-04.txt does not cover the
PSC-2/PSC-3/PSC-4 interface switching capability.

Thanks & Regards,
Surya

> -----Original Message-----
> From: owner-mpls@uu.net [mailto:owner-mpls@uu.net]On Behalf Of Manral,
> Vishwas
> Sent: Tuesday, 28 May 2002 5:03 PM
> To: 'bharathir@future.futsoft.com'; mpls@uu.net
> Cc: gmpls-ops@mplsrc.com
> Subject: RE: GMPLS - PSC switching capability
>
>
> Bharathi,
>
> Though I do not know much about GMPLS, however the draft
>
> http://www.ietf.org/internet-drafts/draft-ietf-ccamp-gmpls-rou
ting-04.txt

states that
"If an interface is of type PSC-1 through PSC-4, it means that the node
receiving data over this interface can switch the received data on a
packet-by-packet basis, based on the label carried in the "shim" header
[RFC3032]. The various levels of PSC establish a hierarchy of LSPs tunneled
within LSPs."
Hope this is what you were looking for,

Thanks,
Vishwas
>  -----Original Message-----
> From: 	Bharathi R [mailto:bharathir@future.futsoft.com]
> Sent:	Tuesday, May 28, 2002 4:04 PM
> To:	mpls@UU.NET
> Cc:	gmpls-ops@mplsrc.com
> Subject:	GMPLS - PSC switching capability
>
> Hi,
> Can anyone tell me why GMPLS routing Extension mention 4 different PSC
> switching capabilities?
> What is the significance of having 4 different PSC switching capabilities?
> Thanks & Regards,
> Bharathi
>

***************************************************************************
This message is proprietary to Future Software Limited (FSL) 
and is intended solely for the use of the individual to whom it
is addressed. It may contain  privileged or confidential information 
and should not be circulated or used for any purpose other than for 
what it is intended. 

If you have received this message in error, please notify the
originator immediately. If you are not the intended recipient,
you are notified that you are strictly prohibited from using,
copying, altering, or disclosing the contents of this message. 
FSL accepts no responsibility for loss or damage arising from 
the use of the information transmitted by this email including
damage from virus.
***************************************************************************