Contribuciones
[ Origen: Microsoft ] |
|
Número
|
Título
|
Origen
|
AI/Cuestión
|
Fecha
|
|
[ 1062 ]
|
Inter-cloud architecture for trusted cloud, Y.oe2eccm and all other projects in Q19
|
Microsoft
|
Q19/13, (JRG-CCM)
|
2015-11-17 |
|
[ 997 ]
|
Incorporate micro-services in Y.oe2eccm
|
Microsoft
|
Q19/13, (JRG-CCM)
|
2015-11-16 |
|
[ 687 ]
(Rev.1) |
Update to "Use Cases for Trusted Cloud"
|
Microsoft Corporation
|
Q19/13
|
2015-04-01 |
|
[ 614 ]
(Rev.1) |
New draft Recommendation proposal for "Reference architecture for Desktop as a Service"
|
China Telecommunications Corporation
,
Electronics and Telecommunications Research Institute (ETRI)
,
Microsoft Corporation
|
Q17/13
|
2014-06-24 |
|
[ 546 ]
(Rev.1) |
Developing a Repository of Scenarios and Use Cases for Cloud Computing Management
|
Microsoft Corporation
|
Q19/13
|
2014-06-23 |
|
[ 510 ]
(Rev.1) |
Support for the joint Rapporteur group on Cloud Computing Management
|
Microsoft Corporation
|
Q19/13, Q18/13, Q17/13
|
2014-06-20 |
|
[ 509 ]
(Rev.1) |
Proposed updates for M.occm
|
Microsoft Corporation
|
Q19/13
|
2014-06-20 |
|
[ 508 ]
(Rev.1) |
Proposed updates for M.rcsm
|
Microsoft Corporation
|
Q19/13
|
2014-06-20 |
|
[ 374 ]
(Rev.1) |
Proposal on the principles of the separation on DaaS reference architecture from Y.DaaS
|
Electronics and Telecommunications Research Institute (ETRI)
,
Microsoft Corporation
|
Q17/13
|
2013-10-22 |
|
[ 373 ]
(Rev.1) |
Proposal to alignment of requirements between main body and use cases in Y.DaaS
|
Electronics and Telecommunications Research Institute (ETRI)
,
Microsoft Corporation
|
Q17/13
|
2013-10-22 |
|
[ 369 ]
(Rev.1) |
Derived requirements for the use case:"DaaS User Scenario" in Appendix
|
Microsoft Corporation
|
Q17/13
|
2013-10-22 |
|
[ 258 ]
(Rev.1) |
Reference Points between NaaS and SDN Functional Blocks
|
Microsoft Corporation
|
QALL/13
|
2013-10-16 |
|
[ 197 ]
|
Editorial revision of the Draft recommendation Y.CCInfra "Cloud Computing Infrastructure Requirements"
|
China Telecommunications Corporation
,
Microsoft Corporation
,
TELEKOMUNIKACJA POLSKA S.A.
|
Q18/13
|
2013-02-08 |
|
[ 142 ]
|
Proposal for a DaaS relevant use case of home application in Y.DaaS
|
Electronics and Telecommunications Research Institute (ETRI)
,
Microsoft Corporation
|
Q17/13
|
2013-02-05 |
|
[ 141 ]
|
Proposal to add DaaS use cases in Y.ccf
|
Electronics and Telecommunications Research Institute (ETRI)
,
Microsoft Corporation
|
Q17/13
|
2013-02-05 |
|
[ 140 ]
|
Proposal to an alignment policy on DaaS general requirements between Y.DaaS and Y.ccf
|
Electronics and Telecommunications Research Institute (ETRI)
,
Microsoft Corporation
|
Q17/13
|
2013-02-05 |
|
[ 139 ]
(Rev.1) |
Enhancement of requirements with editor's note in Y.DaaS
|
Electronics and Telecommunications Research Institute (ETRI)
,
Microsoft Corporation
|
Q17/13
|
2013-02-05 |
|
[ 138 ]
|
Proposal to reflect derived requirements of use cases in the main body of Y.DaaS
|
Electronics and Telecommunications Research Institute (ETRI)
,
Microsoft Corporation
|
Q17/13
|
2013-02-05 |
|
[ 129 ]
(Rev.1) |
e2ecmrgb - Structure and content of E2E Cloud Mgmt Requirements Guidelines and Best Practices
|
Microsoft Corporation
,
ZTE Corporation
|
Q19/13
|
2013-02-05 |
|
[ 121 ]
|
Proposal of use cases and requirements for NaaS in Y.ccf
|
Electronics and Telecommunications Research Institute (ETRI)
,
Microsoft Corporation
|
Q18/13, Q17/13
|
2013-02-05 |
|
[ 118 ]
|
Cloud service lifecycle management "Features" Sub-clause for Y.e2ecslm
|
Microsoft Corporation
|
Q19/13, Q18/13, Q17/13
|
2013-02-05 |
|
[ 117 ]
(Rev.1) |
Y.e2ecslm - Service lifecycle meta data
|
Microsoft Corporation
,
ZTE Corporation
|
Q19/13, Q18/13, Q17/13
|
2013-02-05 |
|
[ 116 ]
|
Multi-Cloud Entertainment Service Use Case and derived requirements for Y.ccf
|
Microsoft Corporation
|
Q19/13, Q18/13, Q17/13
|
2013-02-05 |
|
[ 115 ]
|
End-to-end resource management scenario and high level requirements and for Y.ccf
|
Microsoft Corporation
|
Q19/13, Q18/13, Q17/13
|
2013-02-05 |
Resultados :24 documentos
|
Telecarga de múltiples documentos: Formatos e idiomas que hay que tener en cuenta (si están disponibles):