Separation of IP control and data channels

["Vishal Sharma" <vsharma87@yahoo.com>]

Folks,

There appears to be an issue about how to separate IP control channels
from IP data channels within OSPF-TE for GMPLS, when one focuses on the
peer model.

In the peer model, a router/switch will get OSPF-TE opaque LSAs from the
the entire network, and needs a way to distinguish between data-capable
IP links in the network from IP control channels. This is to prevent
the calculation of routes for IP data packets that traverse any IP control
channels.

While draft-ietf-ccamp-routing-00.txt mentions a couple of ways to
try to avoid this, they may not be enough, especially if one does not
have the flexibility to seggregate control and data channel address
spaces, and/or if one is focusing only on the IGP case.

A simple way to achieve this goal is to extend
the Switching Cap field in the Interface Switching Capability 
Descriptor to separate an "IP Data packet switch capable" link/interface
from an "IP control packet swich capable" link.

We would like to propose that this be added to the relevant drafts.

Thanks,

-Vishal

 

_________________________________________________________
Do You Yahoo!?
Get your free @yahoo.com address at http://mail.yahoo.com