Re: [nvo3] Last Call: <draft-ietf-nvo3-framework-06.txt> (Framework for DC Network Virtualization) to Informational RFC

[Thomas Narten <[e-mail]>]

I've followed the discussion on this thread and want to  go back to
something folk may have forgotten.

More than a year ago, the WG made a considered and conscious decision
to "ship" the framework documemnt more or less "as is" and start work
on a followup architecure document. It was known and expected that the
architecture document would become the focus of work moving forward
and that substantive additions/changes would go there. Even if it
meant the framework document would be less complete.

Sadly, it has been more than a year since that decision was made, yet
the framework document appears stalled and unable to get
published. I'll note that the problem statement document to which the
framework is a companion, has been languishing in the RFC editor queue
for almost a year now, blocked on a normative reference to the
definitions in the framework document.

FWIW, I think the framework is good enough to publish more-or-less as
is. Or more to the point, there just isn't energy to make significant
changes to the document given that the focus of the WG has long since
moved to the architecture document.
 
If folk have substantive issues with the framework, I'd strongly
suggest first looking at the architecture
(draft-ietf-nvo3-arch-01.txt) and seeing whether their concern exists
there, and of so, whether the archictecture document would be a better
place to address the concern.

Thomas