Terminology starts to be widely adopted… Now that we’ve start last step on signalling, new bunch of “requirement” I-d’s (note: we never took “requirement phrasing” in the P&R I-d’s) with two scopes: either requirements summaries (any specific need ?) or extended/uncovered approaches (>< P&R scope is definition of one common baseline … not yet a universal GMPLS-based recovery protocol) => current expectations are more on consolidation ! >< analysis I-d has shown to be still too largely scoped (to be nailed down) More “philosophical” still too much defensive (affiliation-based) approaches… but we are under recovery phase ;-) After 1+ year some feelings… |