Contributions
�[�Source:�AT&T�]��� |
�
|
Num�ro�
|
Titre
|
Source
|
AI/Question
|
Date
|
|
[ 1004 ]
�
� |
Proposed additions to draft Y.ETS-Sec (Minimum Security Requirements for Interconnection of Emergency Telecommunications Service (ETS))
�
� |
AT&T, Inc.
,
Telcordia Technologies
� |
Q16/13
� |
2011-09-28 |
|
[ 902 ]
�
� |
Proposed New Recommendation Y.ETS Security (Y.ETS-Sec)
�
� |
Telcordia Technologies
,
AT&T
� |
Q16/13
� |
2011-01-10 |
|
[ 901 ]
�
� |
Supplement: NGN Certificate Management
�
� |
Telcordia Technologies
,
AT&T
� |
Q16/13
� |
2011-01-10 |
|
[ 899 ]
�
� |
Proposed New Supplement: NGN Security Planning and Operations Guidelines
�
� |
Telcordia Technologies
,
AT&T
� |
Q16/13
� |
2011-01-10 |
|
[ 898 ]
�
� |
Comments on Y.2741
�
� |
Telcordia Technologies
,
AT&T
� |
Q16/13
� |
2011-01-10 |
|
[ 897 ]
�
� |
Comments on Y.2740
�
� |
Telcordia Technologies
,
AT&T
� |
Q16/13
� |
2011-01-10 |
|
[ 896 ]
�
� |
Comments on Y.2722
�
� |
Telcordia Technologies
,
AT&T
� |
Q16/13
� |
2011-01-10 |
|
[ 445 ]
�
� |
Y.ngnIdMreq: Example illustrative deployment scenario for IdM in NGN
�
� |
Telcordia and AT&T
� |
Q16/13
� |
2010-03-31 |
|
[ 444 ]
�
� |
Y.ngnIdMreq: Proposed Changes and Modifications
�
� |
Telcordia and AT&T
� |
Q16/13
� |
2010-03-31 |
|
[ 443 ]
�
� |
Event-Based Charging Scenario
�
� |
Telcordia Technologies
,
Alcatel-Lucent
,
AT&T
,
Qwest
,
Verizon
� |
Q3/13
� |
2010-03-31 |
|
[ 442 ]
�
� |
Proposed Updates to Recommendation Y.2233
�
� |
Telcordia Technologies
,
Alcatel-Lucent
,
AT&T
,
Qwest
,
Verizon
� |
Q3/13
� |
2010-03-31 |
|
[ 441 ]
�
� |
Comments on Recommendation Y.2233 Charging Scenarios
�
� |
Telcordia Technologies
,
Alcatel-Lucent
,
AT&T
,
Qwest
,
Verizon
� |
Q3/13
� |
2010-03-31 |
|
[ 395 ]
�
� |
Proposed Modification to Y.SecMechanisms.
�
� |
Telcordia Technologies
,
AT&T
� |
Q16/13
� |
2009-08-26 |
|
[ 297 ]
�
� |
Concerning Charging Information Records and Event-Based Charging
�
� |
Telcordia Technologies
,
Alcatel-Lucent
,
AT&T
,
Qwest
,
Verizon
� |
Q3/13
� |
2009-08-25 |
|
[ 296 ]
�
� |
Concerning the Usage Metering for Service Layer Data
�
� |
Telcordia Technologies
,
Alcatel-Lucent
,
AT&T
,
Qwest
,
Verizon
� |
Q3/13
� |
2009-08-25 |
|
[ 294 ]
�
� |
Proposed New Appendix in for Draft Y.ngnIdMreq: Example of IdM Architecture Deployment
�
� |
AT&T
,
Telcordia Technologies
� |
Q16/13
� |
2009-08-25 |
|
[ 293 ]
�
� |
Proposed inclusion of 3G America IdM Use Cases
�
� |
AT&T
,
Telcordia Technologies
� |
Q16/13
� |
2009-08-25 |
|
[ 292 ]
�
� |
Proposed New Appendix in for Draft Y.ngnIdMreq: Example IdM Transaction Models
�
� |
Telcordia Technologies
,
AT&T
� |
Q16/13
� |
2009-08-25 |
|
[ 290 ]
�
� |
Identity Management Use Cases for Emergency Telecommunications Service (ETS)
�
� |
Telcordia Technologies
,
AT&T
� |
Q16/13
� |
2009-08-25 |
|
[ 289 ]
�
� |
A mechanism for integration of the IMS- and OpenID-based authentication
�
� |
Alcatel-Lucent, USA
,
AT&T, USA
� |
Q16/13
� |
2009-08-25 |
|
[ 285 ]
�
� |
Proposed Changes and Additions to Y.ngnIdMreq (NGN Identity Management Requirements)
�
� |
Telcordia Technologies and AT&T
� |
Q16/13
� |
2009-08-24 |
|
[ 144 ]
�
� |
Proposed Initial Text for ITU-T Supplement "Evaluation of Existing Signaling Protocol Extensions to Support Y.2171 Admission Control Priority Levels"
�
� |
AT&T and Telcordia
� |
Q4/13
� |
2009-01-07 |
|
[ 105 ]
�
� |
Proposed Addition to Y.secMechanisms
�
� |
Telcordia Technologies and AT&T
� |
Q16/13
� |
2009-01-06 |
|
[ 104 ]
�
� |
Proposed Addition to Y.ngnIdMuse
�
� |
Telcordia Technologies and AT&T
� |
Q16/13
� |
2009-01-06 |
|
[ 103 ]
�
� |
Proposed Changes and Addition to Draft Y.ngnIdMreq
�
� |
Telcordia Technologies and AT&T
� |
Q16/13
� |
2009-01-06 |
|
[ 102 ]
�
� |
Proposed Addition to Y.secMechanisms
�
� |
Telcordia Technologies and AT&T
� |
Q16/13
� |
2009-01-06 |
|
[ 7 ]
�
� |
Proposed Modifications to FRA, Release 2 for Inclusion of Server-to-Network Interface
�
� |
Telcordia and AT&T
� |
Q5/13
� |
2009-01-05 |
Resultats:27 documents
� |
T�l�chargement de multiples documents:�Formats et langues � prendre en compte (si disponibles):