Re: [CCAMP] Input for Terminology discussion: UNI definitions across different SDOs

["Zhangxian (Xian)" <[e-mail]>]

Thank you, Oscar. It indeed helps me to understand the UNI better.



Previously I thought the UNI defintion would include allowing for reachability information across this interface. Clearly, it DOES NOT from the text you provide below.



So, i double-checked RFC4208, it turns out that this "reachability information" is mentioned when talking about overlay model:



" In the overlay model, the core-nodes act more as a closed system. The edge-nodes do not participate
  in the routing protocol instance that runs among the core nodes; in particular, the edge-nodes are unaware

of the topology of the core-nodes.  There may, however, be a routing protocol interaction between
   a core-node and an edge-node for the exchange of reachability information to other edge-nodes."

Hope this helps a bit on clarification and ongoing discussion.



Regards,

Xian

________________________________

发件人: [e-mail] [[e-mail]] 代表 Oscar González de Dios [[e-mail]]
发送时间: 2013年11月8日 3:25
收件人: CCAMP
主题: [CCAMP] Input for Terminology discussion: UNI definitions across different SDOs

Hi all,

As inputs for the terminology discussions, please find bellow a set of definitions for UNI coming from different SDOs (with a short reference, they are easy to find with the number):

[G.807] (ITU-T): "User-Network Interface for the control plane (UNI): A bidirectional signaling interface between service requester and service provider control plane entities."

In the same document: "UNI: This interface supports, as a minimum, the following information elements:
? End-point name and address;
? Authentication and connection admission control;
? Connection service messages.”

[G.8081] (ITU-T): "user-network interface for the control plane (UNI): An UNI is a bidirectional signaling interface between service requester and service provider control plane entities.”

[G.8080] (ITU-T): “UNI
Information flows expected across the UNI reference point support the following functions:
- call control
- resource discovery
- connection control
- connection selection.
Note, there is no routing function associated with the UNI reference point. Additional functions such as security and authentication of calls, or enhanced directory services,
may be added to this basic set of functions."

[RFC3717]: “The client-optical internetwork interface (UNI) represents a service boundary between the client (e.g., IP router) and the optical network.  The client and server (optical network) are essentially two different roles: the client role requests a service connection from a server; the server role establishes the connection to fulfill the service request ― provided all relevant admission control conditions are satisfied.”

   [OIF UNI1.0]: UNI: “The service control interface between a client device and the transport network.”
 UNI-C: ”The logical entity that terminates UNI signalling on the client device side.”
UNI-N: “The logical entity that terminates UNI signalling on the transport network side.”

       [MEF 11]: “The MEF UNI is a reference point for all interactions between Subscribers of MEF defined services and the MEN Service Provider.”

Hope it helps in the discussions,

Best Regards,

Oscar





________________________________

Este mensaje se dirige exclusivamente a su destinatario. Puede consultar nuestra política de envío y recepción de correo electrónico en el enlace situado más abajo.
This message is intended exclusively for its addressee. We only send and receive email on the basis of the terms set out at:
http://www.tid.es/ES/PAGINAS/disclaimer.aspx