[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

RE: [PWE3] New PWE3 Charter Items: SPVC Interworking



Chris,
> - You see the same faces at the different standards body 
> meetings and there 
> is both formal and informal cross-pollination of ideas which is good.

<snip>

> - We want to get it right.

When migrating to a multi-service core a service provider has to be certain that the solution they are deploying is 'right' and 'correct', as most of their business will rely on that multi-service core.  Any problems with the migration path deloyed, or any additional opex introduced by unnecessary complexity or violation of defined networking architectural principles (i.e. G.805/G.809) will in the long run cost the service provider dearly.

For e.g. (and I don't want to digress into a debate on this) managing a MPLS network is expensive and arguably more expensive than it should really be.  IMO this is in some part due to network architectural violations and the fact that things like OAM were not considered/designed in from day 1.


IMO, the issue is not that the IETF does not have the technical ability to address the problem, but that the IETF's consitution/modus operandi does not allow/encourage solutions to these sorts of problems that are 'right' and 'correct' straight out of the box so that they address the requirements of service providers (particularly traditional telco service providers like BT).


Ben



_______________________________________________
pwe3 mailing list
pwe3@ietf.org
https://www1.ietf.org/mailman/listinfo/pwe3