The MPLS WG Archive

Cell Relay Retreat>MPLS WG Archive>month:2006-Apr> msg00088



[Date Prev][Date Next][Thread Prev][Thread Next]  
  [Date Index][Thread Index][Author Index][Subject Index]

[mpls] consolidated response to Q12/15 on T-MPLS

  • From: Scott W Brim <swb@employees.org>
  • Date: Sun, 23 Apr 2006 06:37:29 -0400
  • Cc: mpls@ietf.org
  • User-Agent: Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US;rv:1.8) Gecko/20051201 Thunderbird/1.5 Mnenhy/0.7.3.0
  • X-Enigmail-Version: 0.94.0.0
  • X-IronPort-AV: i="4.04,149,1144047600"; d="scan'208"; a="1797823922:sNHT31293704"
  • X-OriginalArrivalTime: 23 Apr 2006 10:37:31.0209 (UTC)FILETIME=[ECAC8B90:01C666C1]

On 04/23/2006 03:36 AM, Andrew G. Malis allegedly wrote:
> So, I guess we need to know whether or not the T-MPLS equipment will do
> any MPLS-layer processing of the packets, or simply transparently
> transport them without inspection or change, and what signaling (if any)
> would be used across this interface.

That's the plan as far as I know, but I don't think it has been
completely spelled out.

Another interesting scenario is where a device has both "full" MPLS and
T-MPLS LSPs on the same interface.

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