Re: "professional" in an IETF context

[Masataka Ohta <[e-mail]>]

Keith Moore wrote:

>> It's what we expect of our doctors, lawyers, and... ENGINEERS.  It
>> is an ENGINEERING Task Force, after all.  And I would hope that
>> most of us here are actually engineers, with some reasonable level
>> of engineering knowledge, experience, and professionalism.

And the goal should be to prevent IETF perform meaningless
engineering such as development of stupid protocols, including
but not limited to, IPv6 and LISP.

> 5. Whatever you’re working on, try to help build consensus
> or craft or find a compromise that can attract broad support.

That should be the gold paved road to the hell of committee
designed protocols.

> Again
> you’re free to withhold support or to point out problems with a
> proposal, you’re free to offer alternative proposals, and/or to
> appeal formal decisions, but not to obstruct discussion. State/log
> your objections and move on (But you should have a reasonable
> expectation that such objections will not be forgotten and be
> reviewed again at last call time).

Feel free to move forward on the road.

But, if you want to be a good engineer, learn to actively disrespect
not only poor engineering results but also poor engineers, even
though poor engineers say it is not "professional" behavior.

					Masataka Ohta