Contribuciones |
|
Número
|
Título
|
Origen
|
AI/Cuestión
|
Fecha
|
|
[ 508 ]
|
Proposal for updated text for draft Recommendation Y.OSE-arch.
|
ETRI
|
Q5/13
|
2010-01-08 |
|
[ 507 ]
|
Proposed Appendix to FRA for IdM an illustrative deployment
|
AT&T
,
Telcordia Technologies
|
Q5/13, Q16/13
|
2010-01-08 |
|
[ 506 ]
|
Proposed Scope Change to Y.DPIREQ
|
AT&T
,
Cisco
,
dpacket.org
,
Juniper
|
Q17/13
|
2010-01-08 |
|
[ 505 ]
|
Functional Architecture for Interworking between WiMAX and UMTS
|
ETRI
|
Q8/13
|
2010-01-08 |
|
[ 504 ]
|
Vertical Handover Scenarios between WiMAX and UMTS networks
|
ETRI
|
Q8/13
|
2010-01-08 |
|
[ 503 ]
|
Functional Architecture for Mobile Multicasting in Y.MMC
|
ETRI
|
Q8/13
|
2010-01-08 |
|
[ 502 ]
|
Proposal To Remove QoS Signalling Text Clause 7.3.1.1
|
Cisco
|
Q5/11
|
2010-01-08 |
|
[ 501 ]
|
Proposal To Move draft Y.ipv6migration to the IETF
|
Cisco
|
Q7/13
|
2010-01-08 |
|
[ 500 ]
|
Proposal To Remove Rules Table, Rules Action, Scan, Analyser from Clause 8 and Removal of Clause 8.2 from draft Recommendation Y.dpireq "Requirements of DPI in packet-based networks and NGN environment"
|
Cisco
|
Q17/13
|
2010-01-08 |
|
[ 499 ]
|
Proposal To Remove Clauses 3.2.2 through 3.2.12 from draft Recommendation Y.dpireq "Requirements of DPI in packet-based networks and NGN environment"
|
Cisco
|
Q17/13
|
2010-01-08 |
|
[ 498 ]
|
Proposal for Definition of Deep Packet Inspection [DPI] in draft Recommendation Y.dpireq "Requirements of DPI in packet-based networks and NGN environment"
|
Cisco
|
Q17/13
|
2010-01-08 |
|
[ 497 ]
|
Proposal To Remove Reference to "packet-based networks" Under Scope of draft Recommendation Y.dpireq "Requirements of DPI in packet-based networks and NGN environment"
|
Cisco
|
Q17/13
|
2010-01-08 |
|
[ 496 ]
|
Proposal To Remove Reference QoS Signalling Text Clause 7.3.2
|
Cisco
|
Q5/11
|
2010-01-08 |
|
[ 495 ]
|
Proposed New Text for Section 9.7 (IETF) of TRQ.ETS-Overview
|
AT&T
|
Q13/11
|
2010-01-08 |
|
[ 494 ]
|
Proposed text for the Rh' interface
|
ETRI
|
Q5/11
|
2010-01-08 |
|
[ 493 ]
|
Revised texts of the Draft Recommendation Q.3308.1
|
ETRI
|
Q5/11
|
2010-01-08 |
|
[ 492 ]
|
Proposed division to Q.3308.1
|
ETRI
|
Q5/11
|
2010-01-08 |
|
[ 491 ]
|
Draft Y.dpireq - Update of clause IV.3
|
Alcatel-Lucent
|
Q17/13
|
2010-01-08 |
|
[ 490 ]
|
Draft Y.dpireq - Staged Processing Models - New Appendix III.4
|
Alcatel-Lucent
|
Q17/13
|
2010-01-08 |
|
[ 489 ]
|
Draft Y.dpireq - Proposal of definition for "Signature" (clause 3.2.16)
|
Alcatel-Lucent
|
Q17/13
|
2010-01-08 |
|
[ 488 ]
|
Draft Y.dpireq - Required Functional Entities - Alignment between clauses 8.2 (unidirectional DPI), 8.3 (bidirectional DPI) and 3.2 (DPI definitions)
|
Alcatel-Lucent
|
Q17/13
|
2010-01-08 |
|
[ 487 ]
|
Draft Y.dpireq - Update of clause 3.2.1
|
Alcatel-Lucent
|
Q17/13
|
2010-01-08 |
|
[ 486 ]
|
Draft Y.dpireq - Comments and editorial change proposals
|
Alcatel-Lucent
|
Q17/13
|
2010-01-08 |
|
[ 485 ]
|
Proposed appendix on examples of applications using ubiquitous networking in Y.UbiNet-hn
|
ETRI
|
Q12/13
|
2010-01-08 |
|
[ 484 ]
|
Revised Draft Recommendation Y.UbiNet-hn (Framework of home network using ubiquitous networking)
|
ETRI
|
Q12/13
|
2010-01-08 |
|
[ 483 ]
|
Proposed modification of figure for service classification in Y.NGN-Web
|
ETRI
|
Q12/13
|
2010-01-08 |
|
[ 482 ]
|
Proposed modifications for functional entities in Y.NGN-Web
|
ETRI
|
Q12/13
|
2010-01-08 |
|
[ 481 ]
|
Proposed text for NGN-Web convergence in Y.NGN-Web
|
ETRI
|
Q12/13
|
2010-01-08 |
|
[ 480 ]
|
Proposed modifications to draft recommendation Y.NGN-vehicle
|
ETRI
|
Q12/13
|
2010-01-08 |
|
[ 479 ]
|
Proposed comments to draft recommendation Y.ngn-hn
|
ETRI
|
Q12/13
|
2010-01-08 |
|
[ 478 ]
|
Revised Draft Recommendation Y.ipv6-object (Framework of Object Mapping using IPv6 in NGN)
|
ETRI
|
Q7/13
|
2010-01-08 |
|
[ 477 ]
|
Proposed clarifications for true VoD and pseudo VoD in Y.iptvintw VoD
|
ETRI
|
Q12/13
|
2010-01-08 |
|
[ 476 ]
|
Proposed comments to draft recommendation Y.iptvintwrm
|
ETRI
|
Q12/13
|
2010-01-08 |
|
[ 475 ]
|
Proposed comments for legacy IP-based networks in Y.ipev
|
ETRI
|
Q12/13
|
2010-01-08 |
|
[ 474 ]
|
Discussion of new work items for ICT and climate change in Q.12/13
|
ETRI
|
Q12/13
|
2010-01-08 |
|
[ 473 ]
|
Proposed comments to living list on IPTV brokering
|
ETRI
|
Q12/13
|
2010-01-08 |
|
[ 472 ]
|
Some proposal for the functional architecture of Y.NGN-SIDE-req
|
China Telecom
|
Q3/13
|
2010-01-08 |
|
[ 471 ]
|
Proposal for modification of generic requirements of Y.NGN-SIDE-req
|
China Telecom
|
Q3/13
|
2010-01-08 |
|
[ 470 ]
|
Proposed text on protocol profiles for Q.centrexSig
|
China Telecom
|
Q3/11, Q2/11
|
2010-01-08 |
|
[ 469 ]
|
Proposed editorial modifications for Q.centrexSig
|
China Telecom
|
Q3/11, Q2/11
|
2010-01-08 |
|
[ 468 ]
|
Proposed text for security considerations of Q.iptvsa
|
China Telecom
|
Q1/11
|
2010-01-08 |
|
[ 467 ]
|
Proposed editorial modifications for Q.iptvsa
|
China Telecom
|
Q1/11
|
2010-01-08 |
|
[ 466 ]
|
Proposed Modifications on section 6.1.15.2 for Y.dsnreq
|
China Telecom
|
Q19/13
|
2010-01-08 |
|
[ 465 ]
|
Propose to add function entities of TOCF
|
China Telecom
|
Q19/13
|
2010-01-08 |
|
[ 464 ]
|
Proposal for modification of TOCF requirement
|
China Telecom
|
Q19/13
|
2010-01-08 |
|
[ 463 ]
|
Proposal for discussion about TOCF and DSN architecture
|
China Telecom
|
Q19/13
|
2010-01-08 |
|
[ 462 ]
|
Proposed revision of Q.3911 draft Recommendation
|
China Telecom
|
Q9/11
|
2010-01-08 |
|
[ 461 ]
|
Proposed text added into sub-clause 6.3.4 of Q.3911 draft Recommendation
|
China Telecom
|
Q9/11
|
2010-01-08 |
|
[ 460 ]
|
Proposed text to be added into clause 6.4 of Q.3911 draft Recommendation
|
China Telecom
|
Q9/11
|
2010-01-08 |
|
[ 459 ]
|
Proposed revision of Q.3910 draft Recommendation
|
China Telecom
|
Q9/11
|
2010-01-08 |
Resultados :1358 documentos Resultados :
Anterior -
1 -
2 -
3 -
4 -
5 -
6 -
7 -
8 -
9 -
10 -
11 -
12 -
13 -
14 -
15 -
16 -
17 -
18 -
19 -
20 -
21 -
22 -
23 -
24 -
25 -
26 -
27 -
28
- Siguiente
|
Telecarga de múltiples documentos: Formatos e idiomas que hay que tener en cuenta (si están disponibles):