![]() |
![]() |
![]() |
![]() |
![]() |
![]() |
![]() |
![]() |
![]() |
![]() |
![]() |
![]() |
John,
As I am sure you will recall, I've been very concerned since you
first proposed this about the notion of a WG that starts on the
assumption that almost all of the work is done and proven in the
field and that the IETF's role is limited to fine-tuning that
really does not change anything...
1. "fine-tuning that really does not change anything" is a mis-representation of what I have described.
2. I did not "propose" anything. I noted that the transfer of existing technology into the IETF has an inherent issue with deciding whether to protect existing work and how much to protect it, and I noted that this is a long way from the first time the IETF has chosen to protect quite a bit.
3. What work do you want to have done by the working group that is prohibited by the the charter language in question?
I believe that,
in situations that are superficially similar, my colleague Dave
Crocker has argued that the IETF should not take on the work at
all because there is no value added other than endorsement. But
perhaps my memory is bad or this situation is subtly different.
or perhaps not so subtly.
Does "superficially similar" mean "not really similar"?
In any event, I'm sure you can substantiate your claim, here. It would be a shame for such an assertion not to be amenable to deeper evaluation.
It seems to me that you and your colleagues have asked for a charter constraint that asserts wide deployment and, on that
I believe the language that has been used does not match the language you are using.
(i) you are obligated to demonstrate that sufficient production-level deployment actually exists to justify
If you do not care about 5 months of open-participation discussion and revision to the charter that reached rough consensus on the draft charter text *twice*, then please simply say so.
Welcome to the modern IETF.
Infinite time to raise abstract principles, absent any specific technical concerns.
No time to focus on concrete work.
An excellent productivity disincentive for the community.
d/
--
Dave Crocker Brandenburg InternetWorking +1.408.246.8253 dcrocker a t ... WE'VE MOVED to: www.bbiw.net
_______________________________________________ Ietf mailing list Ietf at ietf.org https://www1.ietf.org/mailman/listinfo/ietf
Note Well: Messages sent to this mailing list are the opinions of the senders and do not imply endorsement by the IETF.