Contribuciones
[ AI/Cuestión: Q5/11 ]  |
|
Número
|
Título
|
Origen
|
AI/Cuestión
|
Fecha
|
|
[ 292 ]
(Rev.1) |
Proposed additions to support the resource reservation protocol in Q.3303.2 V2 (ex Q.3323.2)
|
Huawei Technologies Co. Ltd.
,
Alcatel-Lucent
|
Q5/11
|
2012-05-29 |
|
[ 291 ]
(Rev.1) |
Proposed additions to support Pull mode package in Q.3303.2 v2 (ex Q.3323.2)
|
Huawei Technologies Co. Ltd.
,
Alcatel-Lucent
|
Q5/11
|
2012-05-29 |
|
[ 290 ]
(Rev.1) |
Proposed additions to support IP Realm Availability Package in Q.3303.2 v2 (ex Q.3323.2)
|
Huawei Technologies Co. Ltd.
,
Alcatel-Lucent
|
Q5/11
|
2012-05-29 |
|
[ 278 ]
|
Postpone the Consent of Draft Revised Recommendation Q.3303.3 (Version 3)
|
Applied Communication Sciences
|
Q5/11
|
2012-05-24 |
|
[ 271 ]
(Rev.1) |
Proposed update to draft Q.3303.1v2
|
Huawei Technologies Co. Ltd.
,
Ministry of Industry and Information Technology (MIIT)
|
Q5/11
|
2012-05-22 |
|
[ 266 ]
|
Q.3308.1: proposed text for enhancement
|
Electronics and Telecommunications Research Institute (ETRI)
|
Q5/11
|
2011-10-05 |
|
[ 257 ]
(Rev.1) |
Proposal for the change of TRC-FE with TRC-PE at Figure I.1 in the draft Q.3324.1
|
Electronics and Telecommunications Research Institute (ETRI)
|
Q5/11
|
2011-10-04 |
|
[ 250 ]
|
Proposed new text for Annex A of Q.3308.1
|
Korea (Rep. of)
|
Q5/11
|
2011-09-30 |
|
[ 244 ]
|
Proposed draft Recommendation Q.3323.3 for consent
|
China
,
Huawei Technologies Co. Ltd.
|
Q5/11
|
2011-09-29 |
|
[ 241 ]
|
Proposal to define a new work item on IPv6 signalling procedure
|
Huawei Technologies Co. Ltd.
|
Q5/11
|
2011-09-28 |
|
[ 221 ]
|
Update of Scope chapter of Q.3325
|
Poland
|
Q5/11
|
2011-01-13 |
|
[ 220 ]
|
Update of chapter 6.1 Overview of Q.3325
|
Poland
|
Q5/11
|
2011-01-13 |
|
[ 215 ]
|
Proposed modifications for Q.3323.1:Resource control protocol no.3: COPS Profile Protocol at the Rw interface between Policy Decision Physical Entity (PD-PE) and Policy Enforcement Physical Entity (PE-PE)
|
NEC
|
Q5/11
|
2011-01-10 |
|
[ 211 ]
|
Proposed revision of TD 416 to use FSA Ethertype
|
Anagran Inc.
|
Q5/11
|
2011-01-10 |
|
[ 210 ]
|
Q.Flowstatesig - Need for Technical Report for FSA Signalling Requirement
|
Juniper, AT&T, Cisco
,
Qwest, Verizon, Nokia Siemens, Ericsson
|
Q5/11
|
2011-01-10 |
|
[ 207 ]
|
Proposal for the revised text of Section 6 and 7 in draft Q.M9
|
Korea (Rep. of)
|
Q5/11
|
2011-01-07 |
|
[ 196 ]
|
Stability and Deployment of Q.Flowstatesig
|
Anagran
|
Q5/11
|
2011-01-06 |
|
[ 194 ]
|
Mapping between Q.Flowststesig and Y.1221 & Y.2121 Transfer Capabilities
|
Anagran
|
Q5/11, Q4/13, Q11/12
|
2011-01-06 |
|
[ 188 ]
|
Proposal to add multicast ACL to Q.3323.3
|
Huawei
|
Q5/11
|
2011-01-06 |
|
[ 185 ]
|
Mapping between FSA and Y.1221 Transfer Capabilities
|
Anagran Inc.
|
Q5/11
|
2011-01-06 |
|
[ 184 ]
|
Proposed text for open issues and inconsistencies in TD 416
|
Anagran Inc.
|
Q5/11
|
2011-01-06 |
|
[ 183 ]
|
Proposed revision of TD 416 to use GRE Encapsulation
|
Anagran Inc.
|
Q5/11
|
2011-01-06 |
|
[ 166 ]
|
Proposal for the new recommendation of signalling requirements and protocol at the M9 interface between MLM-PE(P) and MLM-PE(C)
|
Korea (Rep. of)
|
Q7/11, Q5/11
|
2010-04-14 |
|
[ 164 ]
|
Proposed use cases to Q.ANCP
|
Huawei, CATR
|
Q5/11
|
2010-04-14 |
|
[ 163 ]
|
Proposed modifications to procedures of Q.3323.2 (Rw H.248)
|
Huawei, CATR
|
Q5/11
|
2010-04-14 |
|
[ 162 ]
|
Proposed admission control in Q.PCNApp
|
Huawei, CATR
|
Q5/11
|
2010-04-14 |
|
[ 161 ]
|
Editorial changes to Q.3321.1
|
Huawei, CATR
|
Q5/11
|
2010-04-14 |
|
[ 160 ]
|
Q.Flowstatesig Changes to accommodate January issues
|
Anagran Inc.
|
Q5/11
|
2010-04-14 |
|
[ 159 ]
|
Q.Flowstatesig draft - definition of transfer capabilities and QoS parameters for proposed FSA transport services
|
Juniper, Verizon, AT&T, Cisco, Telefon-LM Ericsson
,
Nokia siemens Networks GMBH&Co. KG
|
Q5/11
|
2010-04-14 |
|
[ 158 ]
|
Q.Flowstatesig draft - Scope and Architecture issues
|
Juniper, Verizon, AT&T, Cisco, Telefon-LM Ericsson
,
Nokia Siemens Networks GMBH&Co. KG
|
Q5/11
|
2010-04-14 |
|
[ 157 ]
|
An existing IETF protocol solution for Q.Flowstatesig
|
Juniper, Verzon, AT&T, Cisco, Telefon-LM Ericsson,
,
Nokia Siemens Networks GMBH&Co. KG
|
Q5/11
|
2010-04-14 |
|
[ 149 ]
|
Proposed modifications to Clause 6.16.1 in Q.3323.2 (Rw H.248 version 2)
|
CATR, Huawei
|
Q5/11
|
2010-04-14 |
|
[ 145 ]
|
Q.Flowstatesig State Diagrams
|
Anagran Inc.
|
Q5/11
|
2010-04-14 |
|
[ 144 ]
|
Q.Flowstatesig Response to Open Items
|
Anagran Inc.
|
Q5/11
|
2010-04-14 |
|
[ 143 ]
|
Important Benefits of Q.Flowstatesig
|
Anagran Inc.
|
Q5/11
|
2010-04-14 |
|
[ 142 ]
|
Q.Flowstatesig Proposed Changes
|
Anagran Inc.
|
Q5/11
|
2010-04-14 |
|
[ 141 ]
|
Clarification to Aggregate resource profile over Q.3302.1-RCIP
|
ZTE Corp.
|
Q5/11
|
2010-04-14 |
|
[ 138 ]
|
Proposal for authorization free indication over Rs
|
Russian Federation
|
Q5/11
|
2010-04-07 |
|
[ 137 ]
|
Proposed update for Q.3324.2
|
NTT Corp.
|
Q5/11
|
2010-04-07 |
|
[ 131 ]
|
Proposed additions to Q.flowstatesig, relating to Keywords, Sections 2,3 and 4, and Bibliography
|
Razoom Inc.
|
Q5/11
|
2009-08-27 |
|
[ 130 ]
|
Proposed additions to Q.flowstatesig
|
Razoom Inc.
|
Q5/11
|
2009-08-27 |
|
[ 129 ]
|
Proposed modified figures for Q.flowstatesig
|
Razoom Inc.
|
Q5/11
|
2009-08-27 |
|
[ 128 ]
|
Proposal to add IWK definition in Q.ANCP
|
ZTE Corp.
|
Q5/11
|
2009-08-25 |
|
[ 127 ]
|
Proposal to add bandwidth report message in Q.ANCP
|
ZTE Corp.
|
Q5/11
|
2009-08-25 |
|
[ 126 ]
|
Proposal to add Aggregate resource profile over Q.3302.1-RCIP
|
ZTE Corp.
|
Q5/11
|
2009-08-25 |
|
[ 96 ]
|
Terms definition in Q.QCP
|
Huawei, BT
|
Q5/11
|
2009-08-21 |
|
[ 95 ]
|
Protocol specification in Q.ANCP
|
Huawei, CATR
|
Q5/11
|
2009-08-21 |
|
[ 94 ]
|
Proposed modifications to Q.PCNApp
|
Huawei, CATR
|
Q5/11
|
2009-08-21 |
|
[ 93 ]
|
Muticast admission control procedures in Q.ANCP
|
Huawei, CATR
|
Q5/11
|
2009-08-21 |
|
[ 92 ]
|
Proposed modifications to Q.QCP
|
Huawei, BT
|
Q5/11
|
2009-08-21 |
Resultados :77 documentos
Resultados :
1 -
2
- Siguiente
|
Telecarga de múltiples documentos: Formatos e idiomas que hay que tener en cuenta (si están disponibles):
