Re: [savi] WGLC: draft-ietf-savi-dhcp-22

[Ted Lemon <[e-mail]>]

On Apr 23, 2014, at 8:01 AM, Pascal Thubert (pthubert) <[e-mail]> wrote:
> It seems to me that the draft goes very deep into the implementation of the guts of the FSM as opposed to the externally observable behavior, and I'm not sure that this particular FSM is the only way to implement the function and get all the necessary interoperation.

BTW, I am reluctant to weigh in on this question because I don't think there's energy to do this work.   The level of detail here seems similar to SAVI-send, and while I think in principle you may be right that there are multiple ways to solve this problem, getting the state machine right is actually pretty hard, and required a lot of review from DHCP experts.   I'm not convinced it's completely perfect, but it's improved a lot as a result of this review.   I think the added flexibility you are talking about might in theory be a good thing, but might in practice actually be a bad outcome.   In any case, it's certainly true that implementors can do this differently if they like, as long as their implementation behaves in a way that interoperate with implementations that follow the documented FSM.   There's always room for a document update later that talks about this if someone gains experience doing it.