Delayed Contributions
[ AI/Question: Q4/13 ]  |
|
Number
|
Title
|
Source
|
AI/Question
|
Date
|
|
[ 564 ]
|
Terminology related to "session-based services"
|
Cisco Systems, Inc.
|
Q11/13, Q8/13, Q4/13, Q3/13
|
2006-01-09 |
|
[ 563 ]
|
Two Clarifications for G.fepo
|
NTT
|
Q4/13
|
2006-01-06 |
|
[ 562 ]
|
Proposal to insert editor's note in Section 7.2.1.2 Static Reference Allocation Approach of G.fepo
|
NTT
|
Q4/13
|
2006-01-06 |
|
[ 549 ]
|
Proposal for Evaluation of IP Network layer 3 Mechanisms for Delivery of Desired Priority and QoS
|
AT&T
|
Q4/13
|
2006-01-06 |
|
[ 548 ]
|
Proposal for Developing IP-Based Service Priority Classifications and Related Signalling Requirements
|
AT&T
|
Q4/13
|
2006-01-06 |
|
[ 547 ]
|
Proposed Framework/Roadmap for QoS and Priority
|
AT&T
|
Q4/13
|
2006-01-06 |
|
[ 545 ]
|
User Plane Priority Levels for IP Networks and Services
|
United States of America
|
Q4/13
|
2006-01-06 |
|
[ 530 ]
|
Proposed RACF changes on mandatory items to optional ones
|
NEC Corporation
|
Q4/13
|
2006-01-06 |
|
[ 527 ]
|
Add description of Rd interface in TR-RACS
|
ETRI
|
Q4/13
|
2006-01-06 |
|
[ 504 ]
|
Considerations of management plane on Revision 7 of TR-RACF
|
Korea (Rep. of)
|
Q4/13
|
2006-01-06 |
|
[ 503 ]
|
Considerations of QoS measurement and management on Revision 7 of TR-RACF
|
Korea (Rep. of)
|
Q4/13
|
2006-01-06 |
|
[ 497 ]
|
A proposal of consideration of performance measurement scenarios from the view point of network operating maintenance
|
Korea (Rep. of)
|
Q4/13
|
2006-01-06 |
|
[ 482 ]
|
Some technical issues on the Resource Control in Heterogeneous NGN Environments
|
Korea (Rep. of)
|
Q4/13
|
2006-01-06 |
|
[ 455 ]
|
Proposed Text for Ub Reference Point in RACF
|
Lucent Technologies
|
Q4/13
|
2006-01-05 |
|
[ 454 ]
|
Proposed Modification for Rq' Reference Point in RACF
|
Lucent Technologies
|
Q4/13
|
2006-01-05 |
|
[ 453 ]
|
Proposed Modification for Go' Reference Point in RACF
|
Lucent Technologies
|
Q4/13
|
2006-01-05 |
|
[ 452 ]
|
Proposed Clarification and Modification for ANF and ENF in RACF
|
Lucent Technologies
|
Q4/13
|
2006-01-05 |
|
[ 448 ]
|
Proposal to request SG 11 to begin work on signalling aspects of flow aware technology for the timely support of emerging requirements
|
BT Group
|
Q4/13, Q3/13
|
2006-01-05 |
|
[ 447 ]
|
IP QoS Signaling Concepts and Requirements for Flow Aware Services
|
BT Group
|
Q4/13, Q3/13
|
2006-01-05 |
|
[ 446 ]
|
Editorial proposal on TR-RACF
|
Fujitsu
|
Q4/13
|
2006-01-05 |
|
[ 442 ]
|
NAPT control and NAT traversal description enhancement of TR-RACF
|
Oki Electric Industry Co., Ltd.
|
Q4/13
|
2006-01-05 |
|
[ 441 ]
|
Clarification of TR-RACF open issues for release 1
|
OKI Electric Industry Co., Ltd.
|
Q4/13
|
2006-01-05 |
|
[ 440 ]
|
Resource reservation and modification request at Rq' in TR-RACF
|
OKI
|
Q4/13
|
2006-01-05 |
|
[ 438 ]
|
Editorial Proposals for TR-RACF open issues
|
OKI
|
Q4/13
|
2006-01-05 |
|
[ 437 ]
|
RACF Functional Architecture
|
France Telecom
|
Q4/13
|
2006-01-05 |
|
[ 436 ]
|
RACF architecture - Re reference point
|
France Telecom
|
Q4/13
|
2006-01-05 |
|
[ 435 ]
|
RACF and Signalling protocols
|
France Telecom
|
Q4/13
|
2006-01-05 |
|
[ 434 ]
|
Terminology in TR-RACF and FRA
|
France Telecom
|
Q4/13
|
2006-01-05 |
|
[ 432 ]
|
Updated proposal for Ranged Allocation Example in G.FEPO
|
Huawei Technologies Co., Ltd.
|
Q4/13
|
2006-01-05 |
|
[ 431 ]
|
Resource modification procedure in TR-123.qos
|
Huawei Technologies Co., Ltd.
|
Q4/13
|
2006-01-05 |
|
[ 430 ]
|
Proposed revisions to TR-123.qos
|
Huawei Technologies Co., Ltd.
|
Q4/13
|
2006-01-05 |
|
[ 429 ]
|
Proposed Modification for Rq Reference Point in RACF
|
Huawei Technologies Co., Ltd.
|
Q4/13
|
2006-01-05 |
|
[ 428 ]
|
Proposed Modification for Rp Reference Point in RACF
|
Huawei Technologies Co., Ltd.
|
Q4/13
|
2006-01-05 |
|
[ 415 ]
|
Failure handling in TR-123
|
Huawei Technologies Co., Ltd.
|
Q4/13
|
2006-01-05 |
|
[ 410 ]
(Rev.1) |
Service Restoration Priority Levels for IP Networks
|
Unites States of America
|
Q4/13
|
2006-01-05 |
|
[ 408 ]
|
Proposed modification on reference point Go' in TR-RACF
|
NTT Corporation
|
Q4/13
|
2006-01-05 |
|
[ 407 ]
|
Comments to TR-pmm
|
NTT Corporation
|
Q4/13
|
2006-01-05 |
|
[ 394 ]
|
Comments regarding D 321 Performance Measurements and Management for NGN
|
Nortel Networks (Canada)
|
Q4/13
|
2006-01-04 |
|
[ 382 ]
|
Proposal for initiation of an activity to formally describe reference points between different NGN functional entities
|
Nortel Networks (Canada)
|
Q7/13, Q4/13, Q3/13
|
2006-01-04 |
|
[ 381 ]
|
Proposed changes to clause 7 of Delayed Contribution D 319
|
Nortel Networks (Canada)
|
Q4/13
|
2006-01-04 |
|
[ 380 ]
|
NAT, NAPT and NAT-Traversal
|
Nortel Networks (Canada)
|
Q4/13, Q3/13
|
2006-01-04 |
|
[ 379 ]
|
Proposed changes to clauses 1 to 5 of Delayed Contribution D 319
|
Nortel Networks (Canada)
|
Q4/13
|
2006-01-04 |
|
[ 372 ]
|
Proposed Editorial Changes for RACF (FGNGN-OD-00241)
|
Co-Editors of RACF
|
Q4/13
|
2006-01-04 |
|
[ 362 ]
|
RACF Messages' Parameters Mapping
|
Reliance Infocomm Ltd., India
|
Q4/13
|
2006-01-04 |
|
[ 359 ]
|
NGN Message Flows
|
Reliance Infocomm Ltd., India
|
Q4/13, Q3/13
|
2006-01-04 |
|
[ 356 ]
|
A proposal of renaming Go' reference point in RACF
|
LM Ericsson
|
Q4/13
|
2006-01-04 |
|
[ 350 ]
|
Initiation of the Protocol Development Work for the RACF Go' Interface
|
United States of America
|
Q4/13
|
2006-01-04 |
|
[ 349 ]
|
Reference Point Requirements in TR-RACF
|
United States of America
|
Q4/13
|
2006-01-04 |
|
[ 321 ]
|
Performance Measurements and Management for NGN (FGNGN-OD-00239r1)
|
FGNGN Chairman
|
Q4/13
|
2005-11-23 |
|
[ 320 ]
|
Revision of TR-ipaqos (Ref. FGNGN-OD-00113)
|
FGNGN Chairman
|
Q4/13
|
2005-11-23 |
Results:56 total items.
Result page:
1 -
2
- Next
|
Multiple Document Download: Formats and Languages to be included (when available):
