> On Nov 19, 2015, at 05:14, Ted Lemon <[email protected]> wrote: > > Wednesday, Nov 18, 2015 6:49 PM Juliusz Chroboczek wrote: >> It's not a simple matter of sending a few mailing list messages -- it's >> a long-term effort that consists of writing portable, open source, >> lightweight implementations (hnetd, shncpd), of deploying HNCP ourselves >> (Paris network, Henning's network somewhere in Germany), of getting HNCP >> implementations into Linux and Unix distributions (OpenWRT by Steven, >> Debian/Ubuntu soon, I'm not telling), of speaking to people at community >> meetings (Battlemesh, IETF, CCC, FOSDEM), in short, making HNCP familiar >> and easily available. > > Sure, that's fair enough. > >> (And as we're trying to communicate our message in a clear and accurate >> manner, how helpful it is to be able to say that a feature is "mandatory >> to implement, optional to use, but you're not allowed to #ifdef it away".) > > Just to clarify, mandatory to implement doesn't mean you have to write the > code.
s/write/run ? - Mark > It means the functionality has to be present in the deployed implementation > so that two communicating partners can be configured to use it. Mandatory > to use means that the functionality has to be used at all times. > > > -- > Sent from Whiteout Mail - https://whiteout.io > > My PGP key: https://keys.whiteout.io/[email protected] > _______________________________________________ > homenet mailing list > [email protected] > https://www.ietf.org/mailman/listinfo/homenet _______________________________________________ homenet mailing list [email protected] https://www.ietf.org/mailman/listinfo/homenet
