Re: [Teas] Status update on <draft-ietf-teas-pce-central-control>

["Adrian Farrel" <[e-mail]>]

Thanks Michael,

I don't agree with all the points you make, but thanks for the advice on
designing network protocols. I guess I am learning all the time.

With regard to...

> > An architecture does not typically try to constrain solutions, but I
wouldn't
> > think it harmful to include a note on "Guidance for Solution Developers"
that
> > could touch *lightly* on these points at least by pointing them out, but not
> > necessarily directing how they are handled.
> 
> Indeed, albeit I believe some discussion on the potential challenges of PCEP
> extensions could also be homed in Section 4 or 6.
> 
> > Michael ends by asking about manageability impact. I find that difficult to
> > answer. This is a management architecture. It is all about management. So
> > the impact is that the management of the network would change.
> >
> > I confess that Section 6 seemed light when I wrote it. But what to add? What
> > would you like to see covered in addition?
> 
> The impact on interoperability of existing PCEP implementations and a
discussion
> how to ensure this interoperability in future might fit in here, no?

Great.
We'll wait for your text.

Thanks,
Adrian