[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: Liaison received from ITU-T on T-MPLS ring protection

Hi all, it seems to me there maybe some implications for GMPLS based on previous experience with "software based 4F-BLSRs", that is rings that are setup on portions of a mesh network to provide fast redundant protection using SDH like ring switching mechanisms. These types of rings which are applicable to a number of layers (optical, SDH, whatever) have traditionally had interoperability problems across vendors. This has typically involved how to share the "ring map" information (see section 17.1 of the liaison attachment). In addition "nodes" need information on connections added and dropped so they can prevent mis-connection (the "squelching" process).
Obviously one way to keep track of a ring map is to "mark" a link as belonging to a particular ring and distribute this info via GMPLS routing. 

Regards

Greg B.


Adrian Farrel wrote:

Hi,

We received a liaison from the ITU-T that reads as follows...

  SG15 Q9 has nearly completed its work on a recommendation for
  T-MPLS Ring Protection - G.8132. It is targeted to consent this
  new recommendation in the next SG15 plenary meeting scheduled
  for Feb., 2008.

  We have attached the latest draft for your information and
  comments.

We are requested to comment by 11th February 2008.
At first glance, this work appears to concentrate on the data plane only and so is not within our scope. The MPLS working group was also copied and can handle any issues concerning the MPLS data plane.
As always, you can see all incoming and outgoing communications for CCAMP at www.olddog.co.uk/ccamp.htm 

Thanks,
Adrian





--
===================================================
Dr Greg Bernstein, Grotto Networking (510) 573-2237