Next-Next Generation?

Since my last post from Beijing, I have presented at the MPLS Conference in Washington D.C. this past October on so called Next Generation Interconnect.

"Interconnect "is inaccurate really; because the opportunity is to consider a model for federated service abstraction with the following attributes:

1. Federated Services (network is a database) e.g., for experimentation or for network management (monitor, control)
2. API, Policies
3. Governance, Trust, Economics
4. Interoperable naming system
5. Service discovery
6. Resource management in a Federated environment
7. Ambient/Active Services e.g. delivery of service to device other than that requesting it
8. Application of of SOA (Service Oriented Architecture)
9. Fast growth of the Publish & Subscribe model (PubSub)

Dynamics:

10. Companies are using Enterprise Service Buses (ESBs) and Federation of ESBs

XML based routers and XML appears as a reference point

11. Semantic Web Services - self-contained, self-describing, semantically marked-up software resources that can be published, discovered, composed and executed across the Web in a task driven semi-automatic way
12. Emergence of Web 2.0, as an “architecture of participation”
13. Emergence of Web 3.0 as an “Executable” Web Abstraction Layer; Web 3.0 has also been linked to a possible convergence of Service-oriented architecture and the Semantic web
14. Where Web 1.0 was a “read-only” web, with content being produced by and large by the organizations backing any given site; and Web 2.0 was an extension into the “read-write” web that engaged users in an active role; Web 3.0 could extend this one step further by allowing people to modify the site or resource itself

Next-Next Generation? Perhaps…

Finally, November 12-14, I will be in Singapore at the Carrier Ethernet World APAC Congress chairing the plenary session in the morning, and speaking about best practice guidelines in reducing Opex for Service Providers:

• Addressing the key features that influence Opex when building packet transport / CE networks for the following applications:
  • converged NGN
  • mobile backhaul
  • business services at L3 and L2
  • consumer broadband and Triple Play
• Determining the OAM and protection requirements of NG packet transport networks
• What does it mean to service providers in practical terms as they switch from TDM networks to packet transport and CE networks?

• Identifying the tools available for OAM in a CE network:

  • Addressing both network and service management, provisioning, alarm management, fault isolation and diagnosis

• Will service providers manage CE in a similar way to their data networks, or does CE need to emulate TDM management features?

  • Considering the different approaches to survivability L1, L2 and L3 – does restoration at L3 make L2 protection less significant?
• Summing up best practice Opex rules to guide service provider investments in packet transport / CE networks - overall.

For more information:
http://www.iir-events.com/IIR-conf/Telecoms/EventPages.aspx?EventID=1617&SerialNo=4

Posted by Monique Morrow at 04:36PM PST

Ping this URL to post a trackback:
http://blogs.cisco.com/trackback/6583/Wxq4hQgX/

Previous post:
Not a car, a school bus, or a dumptruck...

Next post:
Revealing the Cisco ASR 9000 Series

Recent posts:
November 2009 Archive