SG13 Work Plan
st
(For the 1 phase of Study Period 2009 ~ 2012)
Version 2, September 2009
1. Introduction
During the last study period (2005 - 2008), ITU-T developed many Recommendations for NGN covering various aspects such as requirements,
functional architectures, capabilities, detailed functions for supporting Mobility Management, QoS, Security, Resource Handling and Attachment
Control with related protocol aspects in SG11. It was done with understanding that those Recommendations provide fundamental frameworks to
industry and providers for the implementation and operation of their NGN.
SG13 as a lead group on NGN standards should continue to develop NGN standards in order to enable NGN based telecommunication business and
to facilitate the end user experiences to use NGN. This will continue through this study period. SG13 should be going into deeper functional aspects
to support detailed operation and going into wider aspects in services for stimulating the use of NGN.
ITU-T develops Recommendations, in principle, based on contributions submitted by the ITU-T members. SG13 at the January 2009 meeting in
Geneva agreed to invite contributions to fulfil such aims of SG13 for this study period. As an initial attempt, Question groups in SG13 developed
and proposed the work plan as shown in this document based on each Question mandates given by the WTSA-2008.
1.1 Objectives for Work Plan
This work plan should be used for the following:
 Invite contributions with clear vision, scope and plan from members
 Identify candidate subjects for the future development in SG13
 Identify which subject is still missing in SG13
 Guide overall scopes of candidate deliverables and its target dates
 Identify the responsible Question for issues and relationship with other relevant Questions as appropriate
 Prepare for a consistent SG13 view for future deliverables on scenarios, requirements (high-level and detailed, service and functional) and
architectures (global, component level)
1.2 Relationship between Work Programme and Work Plan
The Work Plan includes candidate (or possible draft) Recommendations or supplements for which agreement to be developed as formal ITU-T
deliverables (ITU-T Recommendations or Supplements) is yet to be reached. Draft Recommendations and supplements recognized as formal ITU-T
deliverables are shown in SG13 Work Programme (refer http://www.itu.int/ITU-T/workprog/wp_search.aspx?isn_sp=545&isn_sg=552 ).
Therefore, any work item included in the work plan will be moved to the Work Programme after agreement for being developed as a formal ITU-T
deliverable (for ITU-T Recommendation or Supplement) is reached at a given meeting. Following Fig.1 shows the relationship between Work
Program and Work Plan.
SG13 Standard Roadmap
Work Programme
(Draft Recs. and
Supplements)
Work Plan
(Identified issues
and proposed
deliverable)
Transfer when meeting agreed
Fig.1 Relationship between Work Programme and Work Plan
2. WP1 Work Plan
 Title: Coordination, Planning and Global Outreach of NGN including Mobile
 Questions: 1, 2, 10, 15 (details for question work scop, please look at COM13-C1)
Q No
Doc No
Document Title
Objectives and Scopes
Stage
Target date
1
TRY.NG
N-newscope
New NGN Scope
This Supplement to ITU-T Y-Series Recommendations on the
scope of beyond NGN release 2 of the Next Generation Network
(NGN) provides business roles and use cases and discusses the
value of the release.
 To clarify the scope of NGN release 2 of the Next
Generation Network (NGN).
 To address a high-level overview of the functional
-
2010,06
Location of
Document
planned
Q No
Doc No
Document Title
Objectives and Scopes

1
1
1
Y.NGNCap2
TRY.IP
TV-newScope
NGN
roadmap
Description of
Capability Set 2 of
NGN
New IPTV Service Use
Cases
NGN Roadmap
Stage
Target date
Location of
Document
independent
2009,09
TD61 R1 (WP
1/13)
-
2010,06
Planned
-
-
TD 48 (WP 1/13)
features
To show the environment, service descriptions and use
cases of NGN Release 2
This Recommendation provides brief descriptions of Capability
Set 2 of NGN in terms of the overall requirements and a highlevel overview of the functional features to be addressed. The
descriptions are from the aspects of environment, capabilities,
architecture, and technical specifications.

To describe NGN Capability Set 2 within ITU-T in terms
of the overall requirements (Y.NGN-Cap2 supersedes
NGN capability set 1, and addresses IPTV-related Recs.)

To list Recommendations relevant to NGN Capability
Set 2
The IPTV Service Use Cases document provides a list of new
IPTV use cases that are informative illustrations of how IPTV
services can be designed, deployed and operated. From the enduser’s perspective, use cases have been categorized by distributed
content services, interactive services, communication services,
and others.
To list IPTV use cases that are informative illustrations of how
IPTV services can be designed, deployed and operated
The NGN roadmap is an informative document that organizes
NGN-related documents by each item and stage.
 To identify gaps between Recs.
 To manage all NGN-related work including other SGs
and SDOs
 To specify Recs. to be reflected to NGN project
management database
Q No
Doc No
Document Title
Objectives and Scopes
Stage
Target date
1
Y.NGNCap3
Description of
Capability Set 3 of
NGN
This Recommendation provides brief descriptions of Capability
Set 3 of NGN in terms of the overall requirements and a highlevel overview of the functional features to be addressed. The
descriptions are from the aspects of environment, capabilities,
architecture, and technical specifications.
independent
2010,12
Location of
Document
planned
independent
2011,06
Planned
1
Y.NGNCap4
Description of
Capability Set 4 of
NGN

To describe NGN Capability Set 3 within ITU-T in terms
of the overall requirements (Y.NGN-Cap3 supersedes
NGN capability set 2, and addresses mobility-related
Recs.)

To list Recommendations relevant to NGN Capability
Set 3
This Recommendation provides brief descriptions of Capability
Set 4 of NGN in terms of the overall requirements and a highlevel overview of the functional features to be addressed. The
descriptions are from the aspects of environment, capabilities,
architecture, and technical specifications.
 To describe NGN Capability Set 3 within ITU-T in terms
of the overall requirements (Y.NGN-Cap4 supersedes
NGN capability set 3, and addresses USN-related Recs.)
 To list Recommendations relevant to NGN Capability
Set 3
Q No
Doc No
Document Title
Objectives and Scopes
Stage
Target date
Location of
Document
planned
1
NGNMM
scope
Scope of Mobility
management in NGN
This Supplement to ITU-T Y-Series Recommendations on the
scope of Mobility management in NGN provides business roles
and use cases and discusses the value of the release.
 To clarify the scope of NGN mobility management.
 To address a high-level overview of the functional
features
 To show the environment, service descriptions and
mobility use cases
-
2009,09
1
NGNMM
roadmap
Mobility management
roadmap in NGN
The NGN-MM roadmap is an informative document that
organizes NGN-MM-related documents by each item and stage.
 To identify gaps between Recs.
 To manage all NGN-MM-related work including other
SGs and SDOs
 To specify Recs. to be reflected to NGN project
management database
-
-
TD107 R1
(GEN/13)
1
TRY.FC
-survey
Draft Supplement of
Global ICT
fora/Consortia Survey
independent
TBD
TD 62 (WP1/13)
2
Y.2091N
ew Rev.
Terms and definitions
for Next Generation
Networks
This Supplement to ITU-T Y-Series Supplement on the Global
ICT fora/Consortia Survey provides information of ICT-related
fora and consortia.
 To clarify the scope of each global ICT forum and
consortium.
This Recommendation contains terms and definitions and a
framework relevant to providing a general understanding of Next
Generation Networks and a guide for the development of NGN
documents in the ITU. It especially reflect the upcoming new
definitions in the context of mobility management. This
Recommendation is not simply a compendium of terms and
definitions. The primary purpose of this Recommendation is to
provide a context for the use of certain terms and definitions to
avoid misunderstandings in NGN activities. Thus, the definitions
are arranged in a specific order and certain necessary
2010,05
Y.2091
Q No
2
2
2
2
Doc No
Y.2091
New
Rev.
Y.2091
Y.iptvter
ms
Ton
FMC
Document Title
Terms and definitions
for Next Generation
Networks
Terms and definitions
for Next Generation
Networks
Terms and definitions
for IPTV
Terms and definitions
for Fix Mobile
Converged network
architectures
2
tonubnw
Terms and definitions
for ubiquitous network
architectures
10
15
RM15
Roadmap for Question
15/13
Y.IMT/I
MS
Develop
GuideIM
T/IMS
Standardization inputs
on IMT and IMS from
Developing countries
A guide for Developing
countries on how to
implement IMT and
IMS
15
15
Objectives and Scopes
Target date
Location of
Document
relationships are illustrated. Additionally, explanatory notes are
also included where deemed appropriate.
New released NGN Recommendation
2011- 1
Y.2091
Multi-vendor Interoperability
2011-1
TD57 R1
(WP1/13)
New Recommendation
2010-1
TD49 (WP1/13)
This document provides the terms and definitions used in the
context of fix mobile converged network architectures in order
 to provide a general understanding of FMC,
 to provide a context of certain terms and definitions
This document provides the terms and definitions used in the
context of ubiquitous network architectures in order
 to provide a general understanding the architecture,
 to provide a context of certain terms and definitions
See Work program Annex 1 to COM 13 – R 13
Using inputs from Developing countries, develop a Roadmap for
Question 15/13 which will be used to update the Study Group 13
Roadmap
Encourage generation of contributions on implementation IMT
and IMS from Developing countries
2011,05
tbd
2012,01
tbd
Produce a guide for Developing countries on how to implement
IMT and IMS using inputs from other SDOs, fora, associations,
etc (in accordance with Res. 38 ), within and outside of ITU, that
are doing similar.
Stage
Independent
2010, 04
Independent
2010, 04
Independent
2010, 09
3. WP2 Work Plan
 Title: Service requirements, scenarios and evolution aspects
 Questions: 3, 12, 13, 14, 18 (details for question work scope, please look at COM13-C1)
Q No
Doc No
Document Title
Objectives and Scopes
Stage*1)
3/13
Various
documents
Work area:
“Service and functional
requirements of emerging
applications/services and
capabilities in NGN” - work
area in line with continuation of
Q.2/13 2005-2008 activities
Topics
• Emerging services in NGN
• Composed services (NGN+legacy,
Internet+Telecom+Broadcasting, SIP+nonSIP based)
• 3rd party services (follow up of MDS etc.)
• Emerging capabilities in NGN
• Composed capabilities (NGN+Web
2.0/Internet capabilities)
• Implementation scenarios
1
3/13
Various
documents
Work area:
“Requirements for
Applications<->NGN service
interface (Telecom APIs for
NGN providers and 3rd
parties)” - new focus in line
with Q.3/13 2009-2012 mandate
Topics
• Key Telecom APIs (common, specific to
relevant applications)
• Building on emerging services and
capabilities, and on relevant use cases
• Requirements for composed services and
capabilities
• Requirements for service interfaces among
capabilities?
1
3/13
Various
documents
Work area:
“Requirements and capabilities
for a SOA enabled NGN open
service delivery environment
(NGN SDP? NGN
Middleware?)”
Topics
• Key telecom reqts for SOA enabled NGN
open service delivery environment
• Application brokering requirements
• Expansion of identified NGN capabilities
(building on NGN OSE)
1
Target date
Location of
Document
Q No
Doc No
Document Title
- new focus in line with Q.3/13
2009-2012 mandate
Objectives and Scopes
•
•
•
12/13
Y.iptv-bs-arch
(tentative)
Service architecture for webbased IPTV brokering
(tentative)
13/13
Y.NGNMMN
(tentative)
Migration from the existing
mobile core network to NGN
(tentative)
14/13
Y.usits
Ubiquitous service scenario for
ITS over NGN
Stage*1)
Target date
Location of
Document
1&2
2011-01
TD72 R1 (WP 2/13)
(as a living list item)
2+3
2011-12
1
2010-12
NGN middleware aspects (common versus
application-specific requirements?, other)
Building on relevant use cases
Framework aspects of NGN open service
delivery environment
This Recommendation describes interworking
requirements, functional architecture, and
procedures to support IPTV brokering service in
the NGN environment
The scope of this Recommendation covers:
• Interworking requirements of the web-based
IPTV brokering service
• Interworking model and functional
architecture of the web-based IPTV
brokering service
• Service procedures of the web-based IPTV
brokering service
This Recommendation is to study the migration
solution (scenario, requirements and framework)
from existing mobile core network to NGN
infrastructure supporting multiple access
technologies.
The study is to define that ITS is to be operated
on ubiquitous environments with ITS
infrastructure , LBS/GIS, secured data
processing, etc.
TD194 (NGN-GSI)
Q No
Doc No
Document Title
Objectives and Scopes
Stage*1)
Target date
14/13
Y.ucs
User-created scenarios for NGN
Services
1
2010-12
14/13
Y.mvs
Multi-media voice (Videphone)
service among NGN operators
using QoS class mapping
1
2011-03
TD194 (NGN-GSI)
14/13
Y.uws
U-work service scenario
1
2011-03
14/13
Y.mis
Mobile IPTV service scenario
1
2010-12
14/13
Y.ufs
U-farm service scenario
1
2011-03
14/13
Y.hns
NGN based home network
service scenario
1
2010-12
14/13
Y.vpns
NGN based VPN service
scenario
The objective of this work is to prepare a
framework enabling users to create their own
service scenarios for NGN services satisfying
their demands. The scope includes reference
model, features of the service components, and
the format and transaction aspects of user-created
scenario.
The study is to define the multimedia
voice(Videphone) service scenario and use - case
among NGN operators by using QoS class
mapping
The study is to define the service scenario for
work and collaboration in home and remote place
on the USN over NGN.
The study is to develop the multimedia services
such as television/video/ audio/text/graphics/data
delivered over IP based wireless networks
managed to provide the required level of
QoS/QoE, security, interactivity and mobility.
The study is to develop the service scenario of
the u-farm service which use the USN
technology
The study is to develop versatile service scenario
of NGN based home network including CPN and
corporate network.
The study is to develop versatile service scenario
of VPN in NGN environment. The objective of
this work is to show the realization of VPN
services in the NGN environment.
Location of
Document
TD194 (NGN-GSI)
1
2010-12
*1) Stages are:
Stage 1: service aspects
Stage 2: functional network aspects
Stage 3: network implementation aspects
Stage independent: all stages are included.
4. WP3 Work Plan
 Title: Frameworks and Functional Architectures
 Questions: 5, 6, 8, 9, 11 (details for question work scop, please look at COM13-C1)
Q No
9/13
Doc No
Y.MC-POL
Document Title
Policy of Multi-connection
9/13
Y.MC-RM
Routing Mechanism of Multiconnection
Objectives and Scopes
This Recommendation describes the policy of
multi-connection, and information flow between
different layers needed to be delivered to meet
the requirements of multiple connections to
support its services in the realm of
heterogeneous accesses.
 To develop the policy of multiconnection, including operator and user
policy for data sending and receiving
etc.
 To develop information flow between
different layers needed to be delivered
to meet the requirements of multiple
connections
This Recommendation describes the routing
mechanism to support the harmonization of
multiple connections for multiple access
technologies.
For routing IP flows to appropriate connections,
several aspects should be considered including
identifiers of connections and IP flows,
matching among these identifiers, etc.
 To develop the routing mechanism to
support the harmonization of multiple
connections for multiple access
technologies.
Stage*1)
Stage
independent
Target date
2011-Q1
Location of Document
Planned
Stage
independent
2011-Q3
Planned
Q No
11/13
Doc No
Y.FMC-IMS
Rev1
Document Title
Fixed mobile convergence with a
common IMS session control
domain – Revision 1
*1) Stages are:
Stage 1: service aspects
Stage 2: functional network aspects
Stage 3: network implementation aspects
Stage independent: all stages are included.
Objectives and Scopes
This Recommendation is the Revision 1
document of Y.FMC-IMS. More scenarios of
FMC will be studied and seamless handover /
QoS requirements from different FMC services
will be investigated.
Stage*1)
2
Target date
TBD
Location of Document
Planned
4. WP4 Work Plan
 Title: QoS and Security
 Questions: 4, 16, 17 (details for question work scop, please look at COM13-C1)
Q No
4/13
Doc No
Y.2111
Document Title
Resource and admission control
functions in Next Generation
Networks
Objectives and Scopes
This Recommendation specifies the resource
and admission control functions (RACF) in
support of end-to-end quality of service (QoS)
and network border control (at access-core
and inter-domain boundaries) in Next
Generation Networks (NGNs). The RACF is
aimed at providing real-time applicationdriven and policy-based transport resource
management for a wide range of services and
for a variety of transport technologies (fixed,
mobile, etc.). Services can make use of RACF
whether the IP multimedia subsystem is
involved or not. This Recommendation
defines the related requirements and
functional architecture covering aspects such
as resource reservation, admission control and
gate control, network address port translation
(NAPT) and firewall control, and network
address translator (NAT) traversal.
It also defines the reference points between
different functional entities and the pertinent
stage 2 requirements and describes the
procedures for QoS-related transport resource
control, NAPT control and NAT traversal.
The pertinent protocol specifications are
described in separate Recommendations. Endto-end information flows for representative
applications, such as VoIP, bulk data transfer
and video-on-demand, are for further study.
Stage*1)
1&2
Target date
Published
(09/2006)
Location of Document
http://www.itu.int/rec/TREC-Y.2111-200609S/en
Q No
Doc No
Document Title
Objectives and Scopes
Stage*1)
Target date
Location of Document
Note that network management functionality
is outside the scope of this Recommendation.
4/13
4/13
Y.2112
Y.2121
A QoS control architecture for
Ethernet-based IP access network
Requirements for the support of
flow state aware transport
technology in an NGN
Administrations may require operators and
service providers to take into account national
regulatory and national policy requirements in
implementing this Recommendation
This Recommendation specifies a quality of
service (QoS) control architecture and
requirements covering aspects, such as
resource reservation, admission control and
gate control, for Ethernet-based IP access
networks. Based on the resource and
admission control functions (RACF) as
defined in [ITU-T Y.2111], this
Recommendation provides details specific to
Ethernet-based IP access networks. An
Ethernet-based IP access network is an IP
access network which comprises the Ethernet
aggregation network, access nodes, and edge
nodes, and may also include the IP
aggregation network.
In this Recommendation, the Ethernet
aggregation network supports VLANs as
defined in [b-IEEE 802.1Q] and [bIEEE 802.1ad]. Note that the QoS
mechanisms for the last mile user access
segment are MAC technology-specific and as
such are out of the scope of this
Recommendation.
This Recommendation provides
flow-state-aware requirements in support of
per-flow service options providing for edgeto-edge QoS and transport resource control
(including resource reservation and admission
1&2
Published
(06/2007)
http://www.itu.int/rec/TREC-Y.2112/en
1
Published
(01/2008)
http://www.itu.int/rec/TREC-Y.2121/en
Q No
Doc No
Document Title
4/13
Y.2171
Admission control priority levels
in Next Generation Networks
Objectives and Scopes
control) in next generation networks (NGNs).
The pertinent protocol specifications and
measurement requirements will be described
in separate Recommendations. Note that
network management functionality is outside
the scope of this Recommendation. Also out
of scope are any edge functions at network
domain boundaries needed for interworking
QoS support between FSA and non-FSA
networks. Similarly, out of scope are any edge
functions at network domain boundaries
needed for interworking between two FSA
networks, where one uses in-band signalling
exclusively for all FSA service support, and
the other uses out-of-band signalling for
resource reservation and clear-down coupled
with in-band signalling to establish the agreed
flow state in the involved FSA nodes.
Administrations may require operators and
service providers to take into account national
regulatory and national policy requirements in
implementing this Recommendation.
According to ITU-T Rec. Y.1271 [Y.1271],
enhanced priority treatment is an essential
requirement for the assured capabilities
needed for emergency telecommunications. A
critical component of enhanced priority
treatment is admission control for
telecommunications services seeking entry
into a network particularly during emergency
conditions when network resources may be
depleted. Admission control in the NGN can
be enabled by:
1)
development of admission control
priority levels based on the
Stage*1)
1
Target date
Published
(06/2007)
Location of Document
http://www.itu.int/rec/TREC-Y.2171/en
Q No
Doc No
Document Title
Objectives and Scopes
criticality of services seeking entry
in NGNs;
2)
development of necessary extensions
in signalling protocols that can
indicate the desired service priority
levels at NGN interfaces;
3)
development of admission control
mechanisms that can recognize the
signalled priority levels and
undertake necessary action.
Stage*1)
Target date
Location of Document
The scope of this Recommendation is limited
to the development of priority levels for
admission control. The purpose is to provide
guidance for the subsequent development of
the necessary signalling protocol extensions
and the priority enabling mechanisms.
4/13
Y.2172
Service restoration priority levels
in Next Generation Networks
Administrations may require operators and
service providers to take into account national
regulatory and national policy requirements in
implementing this Recommendation.
As stated in ITU-T Recommendation Y.1271
[ITU-T Y.1271], enhanced priority treatment
is an essential requirement for the assured
capabilities needed for emergency
telecommunications. One critical component
is admission control and associated priorities
as described in ITU-T Recommendation
Y.2171 [ITU-T Y.2171]. Another critical
component is service restoration particularly
during emergency conditions with potentially
reduced network bandwidth/resources. Under
such conditions, emergency
telecommunications interrupted by network
failures require preferential restoration
1
Published
(06/2007)
http://www.itu.int/rec/TREC-Y.2172/en
Q No
Doc No
Document Title
Objectives and Scopes
treatment. In the NGN, assured restoration can
be enabled by:
Stage*1)
Target date
Location of Document
1. Development of service restoration
priority levels based on the criticality of
services.
2. Development of the necessary extensions
in signalling protocols that can indicate
the restoration priority levels during
call/session setup.
3. Development of restoration mechanisms
that can recognize the signalled priority
levels and undertake the necessary
restoration/re-routing action.
The scope of this Recommendation is limited
to the development of priority levels for
service restoration in the NGN. This guidance
can be helpful in the development of the
subsequent signalling extensions and
restoration mechanisms.
4/13
Y.2173
Management of performance
measurement for NGN
Administrations may require operators and
service providers to take into account national
regulatory and national policy requirements in
implementing this Recommendation.
This document specifies the management
aspects of performance measurement. Its
scope is as follows:
- Requirements for management of
performance measurement.
- A reference measurement network model as
an extension of clause 8 specified in [ITU-T
Y.1543], which allows for various
measurement scenarios for NGN.
- A general and functional architecture for the
management of performance measurement
1&2
Pre-published
(09/2008)
http://www.itu.int/rec/TREC-Y.2173/en
Q No
4/13
Doc No
Y.2174
Document Title
Distributed RACF architecture
for MPLS networks
Objectives and Scopes
and the related stage-2 requirements
- Management procedures covering various
management scenarios such as discovery of
measurement entities, initiation of
measurement, and exchange of
measurement data among different NGN
domains.
- - Application scenarios for management of
performance measurement (MPM) use cases
such as procedures for performance
measurements degradation resolution and
RTP/RTCP-based performance notification.
Note that the pertinent protocol specifications
for reference points and procedures are
expected to be described in separate
Recommendations.
This Recommendation also describes the
following MPM use cases:
1) Performance degradation resolution
information reporting
2) RTP/RTCP-based performance
notification
Recommendation ITU-T Y.2111 [Y.2111]
defines general requirements for resource
and admission control functions for next
generation networks (NGN). These
requirements are independent of the
underlying transport technology.
Multi-protocol label switching (MPLS) is
considered to be a key transport technology
in core networks. In particular, networks
which use MPLS with traffic engineering
(MPLS-TE) capabilities provide significant
assurance that the delivery of desired quality
Stage*1)
1&2
Target date
Pre-published
(06/2008)
Location of Document
http://www.itu.int/rec/TREC-Y.2174/en
Q No
Doc No
Document Title
4/13
Y.2175
Centralized RACF architecture
for MPLS core networks
Objectives and Scopes
of service (QoS) for a variety of services and
applications will occur.
Resource and admission control functions
(RACF) are used to control the flow of traffic
from access networks into the MPLS core
[Y.2111]. A distributed architectural structure
of one RACF functional entity, the transport
resource control functional entity (TRC-FE),
is considered in this Recommendation. In this
architectural arrangement, MPLS transport
resource information is available in label edge
routers (LER) and gateways connected to the
LERs. This Recommendation defines the
distributed architecture for the TRC-FE and
specifies supporting requirements.
Recommendation ITU-T Y.2111 [ITU-T
Y.2111] defines general requirements for
resource and admission control functions for
Next Generation Networks (NGN). These
requirements are independent of the
underlying transport technology.
Multi-protocol label switching (MPLS) is
considered to be a key transport technology in
core networks. In particular, networks which
use MPLS with traffic engineering (MPLSTE) capabilities provide significant assurance
that the delivery of desired quality of service
(QoS) for a variety of services and
applications will occur.
Resource and admission control functions
(RACF) are used to control the flow of traffic
from access networks into the MPLS core
[ITU-T Y.2111]. A centralized architectural
structure of one RACF functional entity, the
transport resource control functional entity
Stage*1)
1&2
Target date
Pre-published
(11/2008)
Location of Document
http://www.itu.int/rec/TREC-Y.2175/en
Q No
Doc No
Document Title
Objectives and Scopes
(TRC-FE), is considered in this
Recommendation. In this architectural
arrangement, MPLS transport resource is
monitored and controlled by the centralized
control entity. This Recommendation defines
the centralized architecture for the TRC-FE
and specifies supporting requirements.
Stage*1)
Target date
Location of Document
Q No
4/13
Doc No
Y.2111Rev.1
Document Title
Resource and admission control
functions in Next Generation
Networks Revision 1
Objectives and Scopes
This Recommendation specifies the resource
and admission control functions (RACF) in
support of end-to-end quality of service (QoS)
and network border control (at access-core
and inter-domain boundaries) in Next
Generation Networks (NGNs). The RACF is
aimed at providing real-time applicationdriven and policy-based transport resource
management for a wide range of services and
for a variety of transport technologies (fixed,
mobile, etc.). Services can make use of RACF
whether the IP multimedia subsystem is
involved or not. The Recommendation defines
the related requirements and functional
architecture covering aspects such as resource
reservation, admission control and gate
control, network address port translation
(NAPT) and firewall control, and network
address translator (NAT) traversal.
It also defines the reference points between
different functional entities and the pertinent
stage 2 requirements and describes the
procedures for QoS-related transport resource
control, NAPT control and NAT traversal.
The pertinent protocol specifications are
described in separate Recommendations. Endto-end information flows for representative
applications, such as VoIP, bulk data transfer
and video on demand, are for further study.
Note that network management functionality
is outside the scope of this Recommendation.
Administrations may require operators and
service providers to take into account national
regulatory and national policy requirements in
implementing this Recommendation.
Stage*1)
1&2
Target date
Pre-published
(09/2008)
Location of Document
http://www.itu.int/rec/TREC-Y.2111-200811P/en
Q No
4/13
Doc No
Y.2113
Document Title
Ethernet QoS Control for Next
Generation Networks
4/13
Y.2111Rev.2
Resource and admission control
functions in Next Generation
Networks, Rev.2
Objectives and Scopes
This Recommendation addresses Ethernet
Quality of Service (QoS) control for next
generation networks. It specifies the
following:
 Service definitions and general
requirements for Ethernet-based NGNs
 Reference model of QoS architecture for
Ethernet-based NGNs
 Traffic management mechanisms for
Ethernet-based NGNs
 Operation, administration and
maintenance (OAM) mechanisms for
Ethernet-based NGNs
 Protection and restoration mechanisms for
Ethernet-based NGNs
The OAM and protection and restoration
mechanisms are specified by reference to
other Recommendations.
Ethernet-based NGN is broadly characterized
as the employment of IP protocols for the
control of Ethernet data flows. In the data link
layer, data link features and interfaces defined
in IEEE 802.3 will not be altered.
As considered in this Recommendation, the
Ethernet network encompasses not only the
customer’s local network but also the
operator’s access and core networks, which
are assumed to employ Ethernet technology.
This Recommendation specifies the functional
architecture and requirements for the resource
and admission control functions in Next
Generation Networks, which may involve a
variety of access and core transport
technologies and multiple domains. The
Stage*1)
1&2
Target date
Approved
(01/2009)
1&2
2Q/2010
Location of Document
http://www.itu.int/rec/TREC-Y.2113/en
TD 81 R1 (WP 4/13)
Q No
Doc No
Document Title
4/13
Y.2111Rev.1
Supplement
Supplement to ITU-T
Recommendation Y.2111 (
Resource and admission control
functions in Next Generation
Networks): Potential items for
post-Revision 1
4/13
Y.2122
Flow Aggregate Information
Exchange Functions in NGN
Objectives and Scopes
RACF provides real-time application-driven
and policy-based transport resource
management in support of end-to-end quality
of service (QoS), gate control, network
address translation, and traversal of remote
network address translators. The RACF is not
service-specific. Services can make use of
RACF whether the IP multimedia subsystem
is involved or not.
In particular, this Recommendation includes
extensions to Y.2111 to address issues related
to multicast in support of IPTV services,
nomadicity, and interactions between
CPE/CPN and RACF.
This document provides a tentative
placeholder for the potential items for postrevision 1 of the RACF. The content is subject
to further discussion, comment and
modification before being accepted and
incorporated into the new revisions or
addendums of the Y.2111 revision 1.
CPE/CPN and Mobility related materials are
moved from the section 8 and 9 of the output
of Seoul SG13 meeting.
This Recommendation defines the network
operating parameters of a flow aggregate (FA)
to be exchanged among different network
domains for various types of FAs in NGN,
and defines the architecture for exchanging
these parameters. It also defines, for
informational purpose, the mapping of the
transport technology specific parameters to
the defined network operating parameters.
Detail protocols are for further study and are
out of scope. Usage examples of the
Stage*1)
Target date
Location of Document
05/2009
(pre-published)
http://www.itu.int/rec/TREC-Y.2122/en
1&2
1&2
Q No
Doc No
Document Title
4/13
Y.IPTV-TM
Traffic management mechanisms
and capabilities for the support of
IPTV services
4/13
Amendment
to Y.2111 R1
New Annex A, RACF
Enhancement for Supporting
Policy-based Charging Control
16/13
Y.2701
Security requirements for NGN
release 1
Objectives and Scopes
exchanged operating parameters are shown in
Appendices.
The document Recommendation describes
specifies a set of traffic management
mechanisms which are aimed to facilitate the
efficient support of IPTV services over the
network infrastructure. Traffic management
mechanisms for the home, access, and core
networks are discussed. The network
supporting IPTV services will span a number
of network domains which may be designed,
deployed and operated by different providers
and which may differ in their traffic
management capabilities. Therefore, it is
expected that the network provider(s) will
implement a subset of these mechanisms to
ensure IPTV service objectives are satisfied
efficiently. Furthermore the traffic
management mechanisms also depend on the
specific network architectures used for IPTV
services as defined in the IPTV architecture
specification.
This document specifies the extensions of
policy-based charging and its associated
control requirements and functional
architecture to ITU-T Recommendation
Y.2111 R1.
This Recommendation provides security
requirements for next generation networks
(NGNs) against security threats. It is achieved
by applying the principles of [ITU-T X.805],
Security architecture for systems providing
end-to-end communications to [ITU-T
Y.2201], NGN release 1 requirements and
[ITU-T Y.2012], Functional requirements and
Stage*1)
Target date
Location of Document
1&2
1Q/2010
TD 80 R1 (WP 4/13)
1&2
2Q/2010
TD 281 (GEN/13)
independent
Published
(04/2007)
http://www.itu.int/rec/TREC-Y.2701/en
Q No
Doc No
Document Title
Objectives and Scopes
architecture of the NGN release 1.
The requirements are to protect the following
in a multi-network environment:
•
network and service provider
infrastructure and its assets (e.g., NGN assets
and resources such as network elements,
systems, components, interfaces, and data and
information), its resources, its
communications (i.e., signalling, management
and data/bearer traffic) and its services;
•
NGN services and capabilities (e.g.,
voice, video and data services);
•
end user communication and
information (e.g., private information).
The requirements are to provide networkbased security of end user communications
across multiple-network administrative
domains. Security of customer assets and
information in the customer domain (e.g., user
network), and the use of peer-to-peer
application capabilities on customer
equipment are not within the scope of this
Recommendation.
The requirements specified in this
Recommendation are applicable to an NGN,
including user to network interfaces (UNIs),
network-to-network interfaces (NNIs) and
application to network interfaces (ANIs) in a
multi-network environment.
NGN service providers will be deploying
"network elements" that support the functional
entities defined in [ITU-T Y.2012]. The
bundling of these functional entities to a given
network element will vary, depending on the
vendor. Therefore, this Recommendation will
Stage*1)
Target date
Location of Document
Q No
Doc No
Document Title
16/13
Y.2702
Authentication and authorization
requirements for NGN release 1
Objectives and Scopes
not attempt to show a strict and fixed bundling
between logical functional entities and
physical network elements.
The requirements in this Recommendation
should be treated as a minimum set of
requirements for NGN security and should not
be considered to be exhaustive. Therefore, an
NGN provider may need to take additional
measures beyond those specified in
Recommendations for NGN security.
In addition, the requirements in this
Recommendation cover some of the technical
aspects of what is generally known as IdM
("identity management"). A working
definition of IdM is "management by NGN
providers of trusted attributes of an entity
such as: a subscriber, a device or a provider".
This is not intended to indicate positive
validation of a person.
Administrations may require NGN providers
to take into account national regulatory and
national policy requirements in implementing
this Recommendation.
This Recommendation provides
authentication and authorization requirements
for Next Generation Network (NGN) based on
Recommendation Y.2012, Functional
requirements and architecture of the NGN
release 1 [Y.2012]. This includes
requirements forl authentication and
authorization across the user-to-network
interface (UNI), the network-to-network
interface (NNI) and the application-tonetwork interface (ANI) as well as any
entities internally with a network that may
Stage*1)
independent
Target date
Pre-published
(09/2008)
Location of Document
http://www.itu.int/rec/TREC-Y.2702/en
Q No
Doc No
Document Title
Objectives and Scopes
require authentication and authorization. The
scope of this Recommendation includes:
1. Authentication and authorization of
user for network access (e.g.,
authentication and authorization of an
end user device, a home network
gateway, or an enterprise gateway to
obtain access or attachment to the
network)
2. Service provider authentication and
authorization of user for access to
service/application (e.g.,
authentication and authorization of an
user, a device or a combined
user/device where the authentication
and authorization apply to NGN
service/application access)
3. User authentication and authorization
of Network (e.g., user authenticating
the identity of the connected NGN
network or of the service provider)
4. User peer-to-peer authentication and
authorization (e.g., authentication and
authorization of the called user (or
terminating entity), authentication
and authorization of the originating
entity, or data origin authentication as
network functions)
5. Mutual network authentication and
authorization (e.g., authentication and
authorization across NNI interface at
the transport level, or
service/application level)
6. Authentication and authorization of
Stage*1)
Target date
Location of Document
Q No
Doc No
Document Title
16/13
Y.2703
The application of AAA service
in NGN
Objectives and Scopes
service/application provider
7. Use of 3rd party authentication and
authorization service.
8. Authentication of objects (e.g.,
application process, message content
and data content identifiers).
The items above include authentication of
flows of the signalling, bearer and
management traffic as applicable.
In addition, this Recommendation also
provides reference models for NGN
authentication and authorization.
NOTE 1. NGN authentication and
authorization is viewed as part of the broader
topic of NGN identity management (IdM).
Specifically, the authentication and
authorization functions and capabilities
described in this Recommendation should be
used to support identity assurance capabilities
for NGN IdM.
NOTE 2. In this Recommendation, the use of
the term “user” is not intended to be restricted
to a person. A user could be a person, groups,
companies, or juridical entities.
NOTE 3. Authentication of an entity is not
intended to indicate positive validation of a
person.
This Recommendation describes an
application for authentication, authorization
and accounting (AAA) for Next Generation
Networks (NGNs) based on Recommendation
Y.2201 - NGN Release 1 Requirements,
Y.2012 - Functional Requirements and
Architecture of the NGN Release 1 (FRA),
Stage*1)
independent
Target date
01/2009
(Approved)
Location of Document
http://www.itu.int/rec/TREC-Y.2703/en
Q No
Doc No
Document Title
Objectives and Scopes
Y.2701 - Security Requirements for NGN
Release 1 and Y.2702 - NGN Authentication.
This Recommendation applies to the
authentication, authorization and accounting
process in accessing an NGN using the AAA
client and AAA server. In particular, this
Recommendation addresses the accounting
function only from the standpoint of its
contribution to security accounting.
The scope of this Recommendation is;
1. The enrolment process
2. Authentication functions and
procedures
3. Authorization functions and procedures
4. Security-accounting functions and
procedures
Stage*1)
Target date
Location of Document
Q No
16/13
Doc No
Y.2720
Document Title
NGN identity management
framework
Objectives and Scopes
This Recommendation provides an Identity
Management (IdM) framework for Next
Generation Network (NGN). The primary
purpose of this Recommendation is to
describe the fundamental concepts, functional
components and capabilities of IdM that can
be used to organize and guide structured
solutions for NGN. The scope of this
Recommendation includes to:
 Describe the business motivations,
benefits, and advantages of IdM
services, and the generic capabilities
used to provide identity assurance
and defining IdM concepts applicable
to NGN and based on the NGN
Functional Requirements and
Architecture (FRA) as defined in
Y.2012
 Identify and describe the functional
entities, roles, relationships, enablers
and communications supporting IdM
services and capabilities for NGN
 Identify and describe the (intranetwork) relationships for supporting
IdM services and capabilities within
an NGN,
 Identify and describe the
relationships for supporting IdM
services and capabilities between
NGN providers (e.g., within a
federation), and between NGN
providers and other providers (e.g.,
inter-federation)
The framework provided in this
Recommendation is intended for NGN (i.e.,
managed packet networks) as defined in [ITUT Y.2001], General overview of NGN.
However, it could be applied as appropriate to
other types of networks (e.g., private
corporation and enterprise networks).
Stage*1)
independent
Target date
01/2009
(Approved)
Location of Document
http://www.itu.int/rec/TREC-Y.2720/en
Q No
16/13
Doc No
Y.2704
(Y.NGN
Security
Mechanisms)
Document Title
Security mechanisms and
procedures for NGN
16/13
Y.NGN IdM
Requirements
NGN Identity management
requirements and use cases
Objectives and Scopes
Y.2701, Security Requirements for NGN
Release 1, provides security requirements for
next generation networks (NGNs) and its
interfaces (e.g., UNIs, NNIs and ANIs). This
Recommendation describes some security
mechanisms that can be used to fulfill the
requirements described in Y.2701, Security
Requirements for NGN Release 1, and
specifies the suite of options for each selected
mechanism. Specifically, this
Recommendation describes identification,
authentication and authorization mechanisms;
then discusses transport security for signalling
and OAMP, and media security. It then
describes audit-trail-related mechanisms and
finally describes the provisioning. The
security mechanisms described in this
recommendation are based on use of the trust
model defined in [Y.2701].
The list of security mechanisms described in
this Recommendation is not exhaustive. NGN
providers are encouraged to support additional
security tools, capabilities and operational
measures as needed beyond the mechanisms
specified in this Recommendation for NGN
security protection.
This Recommendation provides Identity
Management (IdM) requirements and and
example uses cases and guidelines for the
Next Generation Network (NGN) and its
interfaces. It is intended to facilitate a
structured approach for the IdM of the identity
or identities of an NGN entity such as:
a.
User/group
b.Organization/federation/enterprise/ser
Stage*1)
independent
Target date
09/2009
(Determination)
Location of Document
TD 58 R1 (PLEN/13)
independent
01/2010
(Determination)
TD 62 (WP 4/13)
Q No
Doc No
Document Title
Objectives and Scopes
vice provider
c.
Device/network
element/system
d.
Object (e.g., application
process, content, data).
The scope of this Recommendation includes
objectives, requirements and example uses
cases and guidelines addressing:
 Assurance of the identity or identities
of an NGN entity (e.g., user, group,
user device, service provider,
enterprise, federation, network
element and object).
 Secure management of the lifecycle
(e.g., registration, validation,
revocation) of an identity.
 IdM as an enabler of services (e.g.,
VoIP, Data, IPTV and identity-based
services) including real-time
communication sessions (e.g., SIP
communication sessions) and near
real-time communication sessions
(e.g., web-based transactions).
 Secure discovery and exchange of
information associated with an NGN
entity’s identity or identities. This
includes information that may be
located within an NGN and across
different administrative domains or
federations.
 Interworking among the network
elements within a NGN provider
domain (i.e., intra-network), and
among different provider domains or
federations.
Stage*1)
Target date
Location of Document
Q No
Doc No
Document Title
16/13
Y.NGN
Certificate
Management
Certificate management
Objectives and Scopes
 Functions and capabilities for
enforcement of applicable policy
(e.g., privacy) associated with an
entity’s identity or identity
information.
 IdM as an enabler for security of
services (e.g., VoIP, Data, IPTV and
identity-based services) including
real-time communication sessions
(e.g., SIP communication sessions)
and near real-time communication
sessions (e.g., web-based
transactions).
 Security of IdM functions,
capabilities, data and
communications.
The objectives and requirements in this
Recommendation are based on an analysis of
Use Case examples relevant to NGN
interoperability for Identity Management
(IdM)
This Recommendation defines the procedures
for managing X.509 certificates used for NGN
security. The Recommendation applies to
NGN using certificates based on the
framework for Public Key Infrastructure
(PKI) and Privilege Management
Infrastructure (PMI) specified in X.509. The
X.509 certificate may be used for
identification, authentication,
privilege/attribute management and/or
encryption between network elements, and
between user end-device and the NGN
Provider CPE Provisioning Element. This
includes use of X.509 certificates between
Stage*1)
Target date
Location of Document
independent
04/2010
(Determination)
T05-SG13-080114-TDWP2-0435
Q No
Doc No
Document Title
16/13
Y.NGN IdM
Mechanisms
NGN identity management
mechanisms
16/13
Y. mobSec
Mobility Security Framework in
NGN
16/13
Y.NGN
mobile
financial
requirements
Security Requirements for
Mobile Remote Financial
Transactions in NGN
16/13
Y.NGN
mobile
financial
architecture
Y.NGN
trusted SP
Architecture of Secure Mobile
Financial Transactions in NGN
16/13
NGN Requirements and Use
Cases for Trusted Service
Objectives and Scopes
network elements of peering providers based
on policy and business agreements.
Draft Y.idmRequirements, describes NGN
IdM requirements. The IdM mechanisms
selected to implement these requirements will
contain options; however, mismatched options
should be avoided since they tend to introduce
security vulnerabilities and make it more
difficult to achieve interoperability.
This Recommendation describes the specific
IdM mechanisms and suites of options that
should be used to meet the requirements in
Y.idmRequirements of NGN. In addition, it
could provide best practices, guidelines to
support interoperability and other needs.
This Recommendation provides the mobility
security framework in NGN transport stratum.
The mobility scenarios include but no limited
in intra-domain, inter-domain, intertechnology, intra-technology case.
The document covers the security
requirements and the security levels of the
Mobile Banking and Mobile Commerce
systems as well as their most probable risks.
The three security levels described determine
risk mitigation measures. The security level is
determined by the means of Security
Dimension implementation.
The document specifies the general
architecture of the security solution for
Mobile Commerce and Mobile Banking
Stage*1)
Target date
Location of Document
independent
03/2010
(Determination)
TD 63 (WP 4/13)
independent
3Q/2010
TD 64 (WP 4/13)
independent
2Q/2010
TD 65 (WP 4/13)
independent
2Q/2010
TD 66 (WP 4/13)
4Q/2010
TD 60/NGN GSI
Q No
Doc No
requirements
Y.NGN Sec.
Risk
Document Title
Provider Identity
Security Risk Assessment in
NGN
17/13
TR.dpias
Application Scenarios of Deep
Packet Inspection in packet based
networks and NGN environment
17/13
Y.dpireq
Requirements of Deep Packet
Inspection in packet based
networks and NGN environment
16/13
Objectives and Scopes
This recommendation provides guideline for
security risk assessment over NGN and may
be used as practical usage. As such, it relies
on the companion ITU-T Recommendations
that define the architecture, requirements, and
protocols for NGN, specifically those that are
relevant to NGN security.
The Technical Report is targeted primarily at
the application scenarios and deployment
models of DPI:
 To identify different user cases of DPI in
packet based networks and NGN
environment
 To describe the deploy models of DPI in
heterogenous or distributed network
environment
The Recommendation is targeted primarily at
the service requirements, capability
requirements and functional requirements of
DPI and performance requirements
identifying and defining (if necessary) ,
standard interfaces to interconnect with other
components, taking into account policy-based
networks in both packet-based networks (e.g.
IPv4/v6) and NGN environment. These
requirements will of the Deep Packet
Inspection (DPI), including: (1) provide realtime service awareness, and ,control and
security by partial or entire packet scanning
partial or the whole packet for service
awareness and control based on
static/dynamic rules in packet-based
networks and NGN environment.
Stage*1)
Target date
2011
--
independent
Location of Document
TD 68 (WP 4/13)
Planned
2010.1
TD 76 R1 (WP 4/13)
Q No
Q17/13
Doc No
Y.dpifr
Document Title
Framework of Deep Packet
Inspection in packet based
networks and NGN environment
*1) Stages are:
Stage 1: service aspects
Stage 2: functional network aspects
Stage 3: network implementation aspects
Stage independent: all stages are included.
Objectives and Scopes
The Recommendation is targeted primarily at
the framework or architecture of DPI:
 To describe the functionalities of different
DPI building blocks
 To define the standard interfaces,
mechanisms and the interaction involving
end users, control plane and management
plane
Stage*1)
--
Target date
2010.9
Location of Document
TD 75 (WP 4/13)
5. WP5 Work Plan
 Title: Future Networks
 Questions: 7, 19, 20, 21 (details for question work scop, please look at COM13-C1)
Q No
7/13
Doc No
Y.ipv6split
7/13
Y.ipv6-object
7/13
Y.ipv6-vmh
7/13
Y.ipv6migrati
on
Document Title
Objectives and Scopes
Framework of ID/LOC separation  This Recommendation includes IPv6 addressing
in IPv6-based NGN
schemes for ID/LOC separation, mapping
functions and procedures for ID/LOC
separation in IPv6-based NGN, and its
deployment scenarios for ID/LOC separation in
IPv6-based NGN.
Framework of object mapping
This Recommendation specifies basic concept
using IPv6 in NGN
and requirements of object mapping using IPv6 in
NGN in order to provide networking capabilities
to all of objects. This Recommendation also
describes mapping architecture, relationship
between identities and relevant mechanisms and
services for object mapping.
Framework of Vertical MultiThis Recommendation describes a framework of
homing in IPv6-based NGN
vertical multi-homing in IPv6-based NGN. For
this, Y.ipv6-vmh identifies the definition,
requirements, functional architecture, and
applications of vertical multi-homing in IPv6based NGN. Because the vertical multi-homing
issue is also related with the scope of Q9/13, the
work of this Recommendation will be coordinated
with the work of multi-connection by Q9/13
Roadmap for IPv6 Migration
This Recommendation is to give guidelines for
from NGN operators’
NGN operators on how to migrate from IPv4perspectives
based NGN to IPv6-based NGN. For this,
Y.ipv6migration identifies the IPv6 migration
phases and its migration strategies in each phase
for NGN operators.
Stage*1)
1
Target date
2010-9
Location of Document
TD 42 (WP 5/13)
1
2010-4
TD 43 (WP 5/13)
1
2010-9
TD 46 (WP 5/13)
1
2010-9
TD 44 Rev.1 (WP5/13)
Q No
7/13
Doc No
Y.ipv6na
Document Title
Functional requirement for
network access in IPv6-based
NGN
7/13
Y.ipv6-adhoc
Framework of ad-hoc network in
IPv6-based NGN
7/13
Y.ipv6Transport
Transport Stratum Extension in
IPv6-based NGN
7/13
Y.ipv6Service
Service Stratum Extension in
IPv6-based NGN
7/13
Y.ipv6interworking
Interworking with heterogeneous
networks in IPv6-based NGN
19/13
Y.dsnscen
Supplement on DSN use cases
19/13
Y.dsnreq
Recommendation on DSN
requirements
19/13
Y.dsnarch
19/13
Y.dsntocf
Recommendation on DSN
architecture
Recommendation on Traffic
Optimization Control Function
Objectives and Scopes
This Recommendation is to identify the impact on
network access in IPv6-based NGN and to
describe the relevant scenarios/models to find out
its functional requirements.
 Features and requirements of ad-hoc network
in IPv6-based NGN
 Functional architecture for IPv6 ad-hoc
network
 Technical solutions:
Ad-hoc routing and security, etc.
 IPv6-based Transport Functions
 IPv6 Enabled NACFs and RACFs
 Transport User Profiles in IPv6-based NGN
 IPv6 enabled Application and Service support
functions
 Service User Profiles in IPv6-based NGN
 IPv6-based Applications
 Requirements for interworking
 Interworking mechanism with
o Wireless PAN, ad-hoc network etc
 Interworking scenarios
 Technical considerations
 This supplement describes various use cases
and scenarios for distributed services
networks.
 This Recommendation describes the service
requirement, network capability requirements
of DSN
 This Recommendation describes the
architecture of DSN
 The Recommendation defines the functional
architecture covering aspects such as
Stage*1)
1
Target date
2010-9
Location of Document
TD 45 Rev. 1 (WP5/13)
1
TBD
2
TBD
2
TBD
1
TBD
1
2010-01
TD 52 Rev.2 (WP 5/13)
1
2010-01
TD 51 Rev.1 (WP 5/13)
2
2010-12
TD 50 R1 (WP 5/13)
2
2010-12
TD 53 (WP 5/13)
Q No
Doc No
Document Title
20/13
Y.PTDN
Y.PTDN: The general technical
architecture for PTDN.
20/13
Y.iSCP_Scen
Y.iSCP-scen: Draft supplement of
Scenarios for independent
scalable control plane in FPBN
20/13
Y.iSCP_Req
Y.iSCP-req: Requirements of
independent Scalable Control
Plane (iSCP) in FPBN
20/13
Y.iSCP_Arch
Y.iSCP-arch: Architecture of
independent Scalable Control
Plane (iSCP) in FPBN
*1) Stages are:
Stage 1: service aspects
Stage 2: functional network aspects
Objectives and Scopes
topology-aware optimization and cache
capability, as well as reference points between
function entities.
 The objective of this document is to provide
the technical architecture of PTDN, including
the format of the data link frame and network
packet, routing & forwarding mechanisms, as
well as the OAM and interworking methods
with other packet bearer networks. It also
provides the performance requirements of the
PTDN.
 This supplement describes the issues with
current IP networks and provides application
scenarios and improvements provided by an
independent scalable control plane (iSCP)
which separates the control plane from the
data plane in the future packet based networks
as described in [ITU-T Y.2601].
 This Recommendation describes technical
requirements of an independent scalable
control plane (iSCP) by separating the control
plane from the data plane in the future packet
based networks (FPBN) as described in [ITUT Y.2601]
 This Recommendation describes the
architecture, basic functional components,
interfaces of independent scalable control
plane (iSCP) by separating the control plane
from the data plane in the future packet based
networks (FPBN) as described in [ITU-T
Y.2601]
Stage*1)
Target date
Location of Document
2&3
2010-04
TD 59 (WP 5/13)
1
2010-01
TD 58 (WP 5/13)
1
2010-04
TD 57 (WP 5/13)
2&3
2010-12
TD 56 (WP 5/13)
Stage 3: network implementation aspects
Stage independent: all stages are included.
_______________