Brian E Carpenter wrote: >> Just to clarify, mandatory to implement doesn't mean you have to write the >> code. It means the functionality has to be present in the deployed >> implementation so that two communicating partners can be configured to use >> it. > > Um, where is that defined? Is there a BCP that says that? > > I don't think a protocol spec can say that feature X cannot be ifdeffed. > It can say that a protocol must be capable of X and that implementations > must therefore be capable of X. But if you tell implementors that they can't > ifdef unused stuff when building images for highly constrained nodes, I > don't think they will take you seriously.
Maybe slightly off-topic for homenet, but +1000 for constrained node networks. Grüße, Carsten _______________________________________________ homenet mailing list [email protected] https://www.ietf.org/mailman/listinfo/homenet
