Contributions Tardives�� |
�
|
Num�ro�
|
Titre
|
Source
|
AI/Question
|
Date
|
|
[ 67 ]
�
� |
A Proposal on further application method of FDI packet and BDI packet
�
� |
ZTE corporation, China
� |
Q5/13
� |
2004-11-30 |
|
[ 66 ]
�
� |
A Proposal on redefinition of TTSI structure
�
� |
ZTE corporation, China
� |
Q5/13
� |
2004-11-30 |
|
[ 65 ]
�
� |
The NGN Directory Framework - Architecture and Protocols
�
� |
VeriSign, Inc.
� |
Q11/13, Q8/13, Q7/13, Q5/13, Q3/13, Q2/13, Q1/13
� |
2004-11-26 |
|
[ 64 ]
�
� |
Operational Scenarios
�
� |
Nortel Networks (Canada)
� |
Q5/13
� |
2004-11-26 |
|
[ 63 ]
�
� |
Comments on clause 9 of draft Recommendation Y.ethmpls
�
� |
Nortel Networks (Canada)
� |
Q7/13
� |
2004-11-26 |
|
[ 62 ]
�
� |
Comments on clause 8 of draft Recommendation Y.ethmpls
�
� |
Nortel Networks (Canada)
� |
Q7/13
� |
2004-11-26 |
|
[ 61 ]
�
� |
Comments on clause 7 of draft Recommendation Y.ethmpls
�
� |
Nortel Networks (Canada0
� |
Q7/13
� |
2004-11-26 |
|
[ 60 ]
�
� |
Comments on clause 6 of draft Recommendation Y.ethmpls
�
� |
Nortel Networks (Canada)
� |
Q7/13
� |
2004-11-26 |
|
[ 59 ]
�
� |
Comments on clause 5 of draft revised Recommendation Y.1401rev
�
� |
Nortel Networks (Canada)
� |
Q7/13
� |
2004-11-26 |
|
[ 58 ]
�
� |
Comments on clauses 1 to 5 of draft Recommendation Y.ethmpls
�
� |
Nortel Networks (Canada)
� |
Q7/13
� |
2004-11-26 |
|
[ 57 ]
�
� |
Comments on clause 3 of draft revised Recommendation Y.1401rev
�
� |
Nortel Networks (Canada0
� |
Q7/13
� |
2004-11-26 |
|
[ 56 ]
�
� |
Trail Ingress as Source of Fault Notifications
�
� |
Nortel Networks (Canada)
� |
Q7/13, Q5/13
� |
2004-11-26 |
|
[ 55 ]
�
� |
The "Modified Emulated Loop" model of fault notifications
�
� |
Nortel Networks (Canada)
� |
Q7/13, Q5/13
� |
2004-11-26 |
|
[ 54 ]
�
� |
Allocation of ETH ME levels to ETH Path, Segment and Section levels
�
� |
Alcatel
� |
Q5/13
� |
2004-11-26 |
|
[ 53 ]
�
� |
ETH connection management alternatives and ETH OAM
�
� |
Alcatel
� |
Q5/13
� |
2004-11-26 |
|
[ 52 ]
�
� |
ETH OAM for aggregated (bundled) signals
�
� |
Alcatel
� |
Q5/13
� |
2004-11-26 |
|
[ 51 ]
�
� |
TFO-over-IP versus FAX-over-IP - Commonalities & Differences
�
� |
Alcatel
� |
Q7/13
� |
2004-11-26 |
|
[ 50 ]
�
� |
Proposed Draft ITU-T Y.TFOoIP - Tandem Free Operation over IP
�
� |
Alcatel
� |
Q7/13
� |
2004-11-26 |
|
[ 49 ]
�
� |
TFO-over-IP Part IV - Transport Modes for TFO Data in VoIP NGNs
�
� |
Alcatel
� |
Q7/13
� |
2004-11-26 |
|
[ 48 ]
�
� |
TFO-over-IP Part III - Network Reference Scenarios
�
� |
Alcatel
� |
Q7/13
� |
2004-11-26 |
|
[ 47 ]
�
� |
TFO-over-IP Part II - Requirements
�
� |
Alcatel
� |
Q7/13
� |
2004-11-26 |
|
[ 46 ]
�
� |
TFO-over-IP Part I - Motivation
�
� |
Alcatel
� |
Q7/13
� |
2004-11-26 |
|
[ 45 ]
�
(Rev.1)� |
New text on VPN client and server layer functions for Draft Recommendation Y.vpn-decomp
�
� |
BT
� |
Q2/13
� |
2004-11-26 |
|
[ 44 ]
�
� |
Reconsideration of ETH Diagnostic Flow
�
� |
Hitachi
� |
Q5/13
� |
2004-11-26 |
|
[ 43 ]
�
� |
Comment on Ethernet Loopback
�
� |
Hitachi
� |
Q5/13
� |
2004-11-26 |
|
[ 42 ]
�
� |
Comment on Failure Condition
�
� |
Hitachi
� |
Q5/13
� |
2004-11-26 |
|
[ 41 ]
�
� |
Comment on MIP/MEP
�
� |
Hitachi
� |
Q5/13
� |
2004-11-26 |
|
[ 40 ]
�
� |
Requirements for Multicast Service using a Group Label over MPLS
�
� |
Korea (Republic of)
� |
Q2/13
� |
2004-11-25 |
|
[ 39 ]
�
� |
Additions to Y.ethmpls
�
� |
RAD Data Communications
� |
Q7/13
� |
2004-11-25 |
|
[ 38 ]
�
� |
Use of Y.vtoip and Y.1414 for Aggregation of VoIP Streams
�
� |
RAD Data Communications
� |
Q7/13
� |
2004-11-25 |
|
[ 37 ]
�
� |
Y.tdmip - Use of UDP ports
�
� |
RAD Data Communications
� |
Q7/13
� |
2004-11-25 |
|
[ 36 ]
�
� |
More on Y.NGN-GRQ Requirements
�
� |
ZTE Corporation
� |
Q2/13
� |
2004-11-25 |
|
[ 35 ]
�
� |
Refinement of Y.VPN-QoS
�
� |
ZTE Corporation
� |
Q2/13
� |
2004-11-25 |
|
[ 34 ]
�
� |
QoS pipe model VPN implementation example
�
� |
China Telecom
� |
Q4/13, Q2/13
� |
2004-11-25 |
|
[ 33 ]
�
� |
OAM scenario examples without the CC function
�
� |
NTT Corporation
� |
Q5/13
� |
2004-11-25 |
|
[ 32 ]
�
� |
Comments to the CC function
�
� |
NTT Corporation
� |
Q5/13
� |
2004-11-25 |
|
[ 31 ]
�
� |
Proposal about the treatment of FGNGN
�
� |
NTT Corporation
� |
QALL/13
� |
2004-11-25 |
|
[ 30 ]
�
� |
Proposal to develop a new draft Recommendations on the use of IPv6 protocol mechanism in NGN.
�
� |
Korea (Rep. of)
� |
Q9/13
� |
2004-11-25 |
|
[ 29 ]
�
� |
Proposal for initiating a new recommendation for accounting, charging and billing capabilities for NGN
�
� |
Korea (Republic of)
� |
Q2/13
� |
2004-11-25 |
|
[ 28 ]
�
� |
Study Issues on IPv6 over NGN
�
� |
Korea (Republic of)
� |
Q9/13
� |
2004-11-25 |
|
[ 27 ]
�
� |
Requirements of IPv6 Signaling in NGN
�
� |
Korea (Republic of)
� |
Q9/13
� |
2004-11-25 |
|
[ 26 ]
�
� |
MPLS-based Mobility Control/Management in NGN
�
� |
Korea (Republic of)
� |
Q2/13
� |
2004-11-25 |
|
[ 25 ]
�
� |
New Recommendation Plan for IPv6-based NGN(Next Generation Network) Mobility
�
� |
Korea (Republic of)
� |
Q9/13
� |
2004-11-25 |
|
[ 24 ]
�
� |
Principles and requirements for peer partition interworking
�
� |
British Telecommunications PLC
� |
Q7/13
� |
2004-11-25 |
|
[ 23 ]
�
� |
An example of peer partition interworking
�
� |
British Telecommunications PLC
� |
Q7/13
� |
2004-11-25 |
|
[ 22 ]
�
� |
The Introducing of Call Server and the Proposal for the Study of Call Server Functional Requirements and Architecture in the Next Generation Network
�
� |
MII of P.R.China
� |
Q7/13
� |
2004-11-25 |
|
[ 21 ]
�
� |
Use of IPv6 in NGN
�
� |
Huawei Technologies Co. Ltd.
� |
Q9/13
� |
2004-11-23 |
|
[ 20 ]
�
� |
Proposal to develop a new draft recommendation on VPN OAM
�
� |
Huawei Technologies Co. Ltd
� |
Q5/13, Q2/13
� |
2004-11-23 |
|
[ 19 ]
�
� |
Concentration of NGN R1 signalling requirements study into the NGN Focus Group
�
� |
UK
� |
QALL/13
� |
2004-11-23 |
|
[ 18 ]
�
� |
Continued existence of the NGN Focus Group
�
� |
UK
� |
QALL/13
� |
2004-11-23 |
Resultats:67 documents R�sultats :�
1 -
2
�-�Suivant
� |
T�l�chargement de multiples documents:�Formats et langues � prendre en compte (si disponibles):