You want resumes? You've got linkedin for that. The sort of thing Doug describes is actually quite common.
For example, I once had a group chair threaten to have me disciplined by the company I worked for, for pointing out the technical failings of his pet protocol. The IETF isn't a lovey-dovey bunch of hippies working in harmony for humanity. The IETF is hardball. Lloyd Wood http://sat-net.com/L.Wood/ ________________________________________ From: [email protected] [[email protected]] On Behalf Of Doug Ewell [[email protected]] Sent: 15 May 2013 22:28 To: [email protected] Subject: Re: Gather Profiles/Resumes [was Re: call for ideas: tail-heavy IETF process] John C Klensin <john dash ietf at jck dot com> wrote: > I think it is all very well to ask for affiliations in principle > and, also in principle, I agree that it is a good idea. But, in > practice, I think there are a lot of clarifications and other > changes that would be required and that might or might not be > practical. I used the term "Consultant" in RFCs 4645 and 5645, instead of revealing the name of my company (which was different each time, and neither of which contributed any time or money to my WG effort). I did this because the WG at the time included a malicious contributor who had already contacted the HR department of another contributor's employer, asking them to professionally discipline the employee, because he had supported an RFC 3683 PR-action against the first contributor. Full disclosure can be a dangerous thing. -- Doug Ewell | Thornton, CO, USA http://ewellic.org | @DougEwell
