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

Gert Grammel <ggrammel@juniper.net> Fri, 08 November 2013 02:29 UTC

Return-Path: <ggrammel@juniper.net>
X-Original-To: ccamp@ietfa.amsl.com
Delivered-To: ccamp@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 0C31E21E814B for <ccamp@ietfa.amsl.com>; Thu, 7 Nov 2013 18:29:11 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -0.144
X-Spam-Level:
X-Spam-Status: No, score=-0.144 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, FRT_BELOW2=2.154, HTML_MESSAGE=0.001, MIME_8BIT_HEADER=0.3]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id RLIu6i+jEZZP for <ccamp@ietfa.amsl.com>; Thu, 7 Nov 2013 18:29:05 -0800 (PST)
Received: from db8outboundpool.messaging.microsoft.com (mail-db8lp0184.outbound.messaging.microsoft.com [213.199.154.184]) by ietfa.amsl.com (Postfix) with ESMTP id C0A0621E80D2 for <ccamp@ietf.org>; Thu, 7 Nov 2013 18:29:04 -0800 (PST)
Received: from mail53-db8-R.bigfish.com (10.174.8.252) by DB8EHSOBE029.bigfish.com (10.174.4.92) with Microsoft SMTP Server id 14.1.225.22; Fri, 8 Nov 2013 02:29:03 +0000
Received: from mail53-db8 (localhost [127.0.0.1]) by mail53-db8-R.bigfish.com (Postfix) with ESMTP id 82AEA2C01C7; Fri, 8 Nov 2013 02:29:03 +0000 (UTC)
X-Forefront-Antispam-Report: CIP:157.56.240.101; KIP:(null); UIP:(null); IPV:NLI; H:BL2PRD0510HT004.namprd05.prod.outlook.com; RD:none; EFVD:NLI
X-SpamScore: -19
X-BigFish: VPS-19(z579ehzc89bhc85dh14ffIzz1f42h2148h208ch1ee6h1de0h1fdah2073h2146h1202h1e76h1d1ah1d2ah1fc6hzz1d7338h1de098h1033IL17326ah8275bh8275dh18c673h1de097h186068hz2fh109h2a8h839hd24hf0ah1288h12a5h12bdh137ah1441h1504h1537h153bh162dh1631h1758h18e1h1946h19b5h19ceh1ad9h1b0ah1bceh224fh1d07h1d0ch1d2eh1d3fh1de9h1dfeh1dffh1e1dh1fe8h1ff5h20f0h2216h9a9j1155h)
Received-SPF: pass (mail53-db8: domain of juniper.net designates 157.56.240.101 as permitted sender) client-ip=157.56.240.101; envelope-from=ggrammel@juniper.net; helo=BL2PRD0510HT004.namprd05.prod.outlook.com ; .outlook.com ;
X-Forefront-Antispam-Report-Untrusted: SFV:NSPM; SFS:(189002)(199002)(53754006)(85306002)(79102001)(77982001)(59766001)(46102001)(81686001)(54356001)(53806001)(83322001)(19580405001)(19580395003)(83072001)(80976001)(19300405004)(76482001)(33646001)(15202345003)(74316001)(54316002)(51856001)(56776001)(47446002)(74662001)(74502001)(81816001)(31966008)(50986001)(47976001)(47736001)(49866001)(4396001)(76576001)(81542001)(56816003)(66066001)(77096001)(76786001)(74366001)(76796001)(81342001)(2656002)(16236675002)(74706001)(224303002)(69226001)(74876001)(15975445006)(65816001)(63696002)(224313003)(87266001)(80022001)(87936001)(24736002); DIR:OUT; SFP:; SCL:1; SRVR:BN1PR05MB041; H:BN1PR05MB041.namprd05.prod.outlook.com; CLIP:193.110.54.36; FPR:; RD:InfoNoRecords; MX:1; A:1; LANG:en;
Received: from mail53-db8 (localhost.localdomain [127.0.0.1]) by mail53-db8 (MessageSwitch) id 1383877741256907_23987; Fri, 8 Nov 2013 02:29:01 +0000 (UTC)
Received: from DB8EHSMHS031.bigfish.com (unknown [10.174.8.226]) by mail53-db8.bigfish.com (Postfix) with ESMTP id 30CF06A003F; Fri, 8 Nov 2013 02:29:01 +0000 (UTC)
Received: from BL2PRD0510HT004.namprd05.prod.outlook.com (157.56.240.101) by DB8EHSMHS031.bigfish.com (10.174.4.41) with Microsoft SMTP Server (TLS) id 14.16.227.3; Fri, 8 Nov 2013 02:28:57 +0000
Received: from BN1PR05MB041.namprd05.prod.outlook.com (10.255.202.140) by BL2PRD0510HT004.namprd05.prod.outlook.com (10.255.100.39) with Microsoft SMTP Server (TLS) id 14.16.371.2; Fri, 8 Nov 2013 02:28:51 +0000
Received: from BN1PR05MB041.namprd05.prod.outlook.com (10.255.202.140) by BN1PR05MB041.namprd05.prod.outlook.com (10.255.202.140) with Microsoft SMTP Server (TLS) id 15.0.810.5; Fri, 8 Nov 2013 02:28:50 +0000
Received: from BN1PR05MB041.namprd05.prod.outlook.com ([169.254.13.126]) by BN1PR05MB041.namprd05.prod.outlook.com ([169.254.13.126]) with mapi id 15.00.0810.005; Fri, 8 Nov 2013 02:28:50 +0000
From: Gert Grammel <ggrammel@juniper.net>
To: Oscar González de Dios <ogondio@tid.es>, CCAMP <ccamp@ietf.org>
Thread-Topic: Input for Terminology discussion: UNI definitions across different SDOs
Thread-Index: AQHO2+8gmryt/BU0MUSuYCeURJs4dJoam82g
Date: Fri, 08 Nov 2013 02:28:49 +0000
Message-ID: <ea8827a9c62e4679983da62c8504fd2b@BN1PR05MB041.namprd05.prod.outlook.com>
References: <CEA12928.23608%ogondio@tid.es>
In-Reply-To: <CEA12928.23608%ogondio@tid.es>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach:
X-MS-TNEF-Correlator:
x-originating-ip: [193.110.54.36]
x-forefront-prvs: 00246AB517
Content-Type: multipart/alternative; boundary="_000_ea8827a9c62e4679983da62c8504fd2bBN1PR05MB041namprd05pro_"
MIME-Version: 1.0
X-OriginatorOrg: juniper.net
X-FOPE-CONNECTOR: Id%0$Dn%*$RO%0$TLS%0$FQDN%$TlsDn%
Subject: Re: [CCAMP] Input for Terminology discussion: UNI definitions across different SDOs
X-BeenThere: ccamp@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: Discussion list for the CCAMP working group <ccamp.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ccamp>, <mailto:ccamp-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ccamp>
List-Post: <mailto:ccamp@ietf.org>
List-Help: <mailto:ccamp-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ccamp>, <mailto:ccamp-request@ietf.org?subject=subscribe>
X-List-Received-Date: Fri, 08 Nov 2013 02:29:11 -0000

Adding the detail I mentioned on the mic:

[G.8080](ITU-T) "NOTE - The route query interface does not apply for the CC interface at the UNI reference point."

From: ccamp-bounces@ietf.org [mailto:ccamp-bounces@ietf.org] On Behalf Of Oscar González de Dios
Sent: 07 November 2013 20:26
To: CCAMP
Subject: [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