On 1/21/2016 11:18 AM, Shumon Huque wrote:
Lastly, new protocols take a long time to get deployed. Look at IPv6 - I'm speaking from experience, having first deployed it in production in 2002. And it's still largely undeployed. Shutting down the DANE working group while the protocol is still in its infancy, and while there is still potential work in the queue, sends the wrong message in my opinion.
If there is work to do, then where is the draft charter text describing the problem and nature of work to be done, timeline for completion, indication of who is asking for the work, indication of who will do the work, and indication of who will adopt (use) the work?
In terms of overseeing adoption of an IETF specification, that's not the job of the IETF. That's the job of whatever Internet constituency(ies) want to see the adoption. The IETF work is a segment of an industry process. Simplistically, it divides into : 1) formulate the needs, 2) design a solution, 3) deploy the solution. The IETF is (only) step #2.
d/ -- Dave Crocker Brandenburg InternetWorking bbiw.net _______________________________________________ dane mailing list [email protected] https://www.ietf.org/mailman/listinfo/dane
