Re: [cso] Cross-Stratum Optimization Problem Statement revision

[Young Lee <[e-mail]>]

Hi Dave and Ning,

 

Relating to the issue of scoping the CSO work, I just wanted to make sure we
have the same understanding. 

 

The initial work under CSO is simply defining protocol between the ACG
(Application CSO Gateway) and NCG (Network CSO Gateway). I think you refer
to this as proxy-signaling. 

The following figure shows the focus of CSO work. 

 

                    -------------------------------------------

                   |                    Application Overlay    |

                   |                                           |

 ----------        |    -------------         --------------   |


| End-User |       |   | Application |. . . .| Application  |  |

|          |. . . >|   | CSO Gateway |       |  Processes   |  |

 ----------        |   |    (ACG)    |        --------------   |

                   |   |             |        --------------   |

                   |    ------------- . . . .| Application  |  |


                   |          /\             | Related Data |  |

                   |          ||              --------------   |

                    ----------||-------------------------------

                              ||

                              ||   Application - Network

                              ||   Communication Interface & 

                              ||   Protocol (Focus of WG)

                              ||   

                    ----------||-------------------------------

                   |          \/         Network Underlay      |

                   |                                           |


                   |    -------------        ------------------  |

                   |   |   Network   |. . . |    Network     | |

                   |   | CSO Gateway |      |    Processes   | |

                   |   |    (NCG)    |       ----------------  |

                   |   |             |       -----------------  |

                   |    ------------- . . . |    Network     | |

                   |                        |  Related Data  | |

                   |                         ----------------  |

                    -------------------------------------------

 

 

The protocol is simply request/reply and should support:

-          path estimation (from application to network) 

-          path configuration/reservation (from application to network -
here the application profile needs to be communicated)

-          notification (e.g., congestion/failure indication from/to
application to/from network)

-          virtual/abstract info query from/to application to/from network
(we need to define what information to exchange)

 

Once this protocol is clearly defined, then we have quite a few works to be
done in the network side at a minimum:  

-          Interface between NCG and PCE (including multi-domain PCE) 

-          Interface between NCG and Diameter/Radius (for IP network) and
Control Plane (for MPLS/GMPLS network) 

-          How can we make communication of properties (e.g., latency) more
dynamic/agile across functional groups in the network stratum

-          How to provide atomic NM/configuration for the whole network
elements

 

But these items need to be worked on other WG groups such as CCAMP/MPLS,
PCE, PCN, Diameter, netconf/ying, etc. I think the confusion takes place
because all these functions are thought to be part of CSO work. 

CSO is only the trigger for these works to be done in other WG's. 

 

Let's continue to discuss. 

 

Best Regards,

Young