Re: Acknowledgements section in a RFC (Was: Last Call: 'Matching of Language Tags' to BCP (draft-ietf-ltru-matching)
At 10:02 07/06/2006, Stephane Bortzmeyer wrote: On Wed, Jun 07, 2006 at 03:58:15AM +0200, JFC (Jefsey) Morfin <[EMAIL PROTECTED]> wrote a message of 13 lines which said: > - Appendix A - some names seem to be missing. I could quote a small > score of them? I do not know if there are written rules about the "Acknowledgements" or "Credits" section in a RFC. It seems quite variable between the RFCs. I am mentioned in draft-ietf-ltru-matching-14 for what I regard as a very small contribution and not in RFC 4408 where I feel that my contribution is more substantive. Dear Stephane, This may seem trivial, but IMHO quoting every contributor is important for several key reasons. - the IETF is made of paid and free volunteers. The reward of the free participants is their exposure. If we want top quality participants we must acknowledge their contributions. - every contribution can be a key stone in the final construct. That people like Michael Everson, Ned Freed, Lee Gillam, John C. Klensin, Felix Sasaki, Michel Suignard, and Tex Texin are not quotted seems odd. Others like Scott Hollenbeck and Sam Hartman really helped. What about Karen Broome, M.T. Carrasco Benitez, N. Piercei? Inputs or help from Brian Carpenter, Ted Hardie, Dylan N. Pierce are real. - the IPR is to all the co-authors. Every person having contributed a word, a concept, a change, positively or negatively is a co-author. This also has some importance to show the document is not the work of an affinity group (as discussed in RFC 3774) but of a true WG. - I consider BCP 47 went from an initial error to a technical split of the International US Internet from the Multilingual Global Network. We now need to insure interroperability between them two (for example MGN will accept "en-EU", IANA not). Afrer the PR-action, this calls for many experts to accept this is a true IETF proposition. jfc ___ Ietf mailing list Ietf@ietf.org https://www1.ietf.org/mailman/listinfo/ietf
Re: Acknowledgements section in a RFC (Was: Last Call: 'Matching of Language Tags' to BCP (draft-ietf-ltru-matching)
Perhaps I lead a sheltered life, but on two of these points... > - Appendix A - some names seem to be missing. I could quote a small > score of them? I do not know if there are written rules about the "Acknowledgements" or "Credits" section in a RFC. It seems quite variable between the RFCs. I am mentioned in draft-ietf-ltru-matching-14 for what I regard as a very small contribution and not in RFC 4408 where I feel that my contribution is more substantive. Dear Stephane, This may seem trivial, but IMHO quoting every contributor is important for several key reasons. - the IETF is made of paid and free volunteers. The reward of the free participants is their exposure. If we want top quality participants we must acknowledge their contributions. This is a real concern (I am a working group draft editor for a draft where probably 30 percent of the e-mail I've received on the draft has been about acknowledgements). I thought it was a more serious concern for academics and consultants, but am now seeing the same concerns from corporate standards types and development engineers in other working groups. I have expressed this as a concern in private e-mail, but don't know what the answer is. - the IPR is to all the co-authors. Every person having contributed a word, a concept, a change, positively or negatively is a co-author. This also has some importance to show the document is not the work of an affinity group (as discussed in RFC 3774) but of a true WG. In my limited SDO experience, beyond IETF I am most familar with IEEE 802.1 practice, which is to list "participants" (at least, this is what appears in the most recent IEEE 802.1 standard appearing on "Getieee802" at http://standards.ieee.org/getieee802/download/802.1AB-2005.pdf), where the list is "membership at the time of approval", and "balloted at various times". Since we have no clue who the "membership" of an IETF working group is, I don't know how to do the equivalent thing here. Spencer ___ Ietf mailing list Ietf@ietf.org https://www1.ietf.org/mailman/listinfo/ietf
Re: Acknowledgements section in a RFC (Was: Last Call: 'Matching of Language Tags' to BCP (draft-ietf-ltru-matching)
The basic problem is that there is no way to acknowledge all the folks who helped, for the most general definition of "contributor". One would have to keep track of every person who made a comment on the mailing list (whether the particular change ended up used or not) and everyone who spoke at the meeting. That is why it is common (but not mandatory) to acknowledge the working group that worked on the draft. This relates to the acknowledgement section more than the contributors section. Acknowledging folks who helped is a good idea. Particularly for a volunteer organization. But we can not and do not have to be fanatic about trying to acknowledge everyone. On a historical note, the acknowledgements section was intended for folks who wrote pieces, or folks who suggested useful ideas, or provided significant useful corrections, etc. The contributors section was introduced in conjunction with the effort to reduce the set of authors to those who wrote the primary text. So Contributors is usually used for those who wrote sections of text, but not enough to be authors. (The debate about whether we should ahve that distinction is a different discussion, please.) So we actually should be trying to be careful and thurough about the "contributors" section, since those are folks who wrote noticeably more than a single paragraph, and we ought to be able to tell who they are. Even then, mistakes will be made, and as far as I can tell it is not fatal. Yours, Joel M. Halpern At 07:47 AM 6/7/2006, Spencer Dawkins wrote: Perhaps I lead a sheltered life, but on two of these points... > - Appendix A - some names seem to be missing. I could quote a small > score of them? I do not know if there are written rules about the "Acknowledgements" or "Credits" section in a RFC. It seems quite variable between the RFCs. I am mentioned in draft-ietf-ltru-matching-14 for what I regard as a very small contribution and not in RFC 4408 where I feel that my contribution is more substantive. Dear Stephane, This may seem trivial, but IMHO quoting every contributor is important for several key reasons. - the IETF is made of paid and free volunteers. The reward of the free participants is their exposure. If we want top quality participants we must acknowledge their contributions. This is a real concern (I am a working group draft editor for a draft where probably 30 percent of the e-mail I've received on the draft has been about acknowledgements). I thought it was a more serious concern for academics and consultants, but am now seeing the same concerns from corporate standards types and development engineers in other working groups. I have expressed this as a concern in private e-mail, but don't know what the answer is. - the IPR is to all the co-authors. Every person having contributed a word, a concept, a change, positively or negatively is a co-author. This also has some importance to show the document is not the work of an affinity group (as discussed in RFC 3774) but of a true WG. In my limited SDO experience, beyond IETF I am most familar with IEEE 802.1 practice, which is to list "participants" (at least, this is what appears in the most recent IEEE 802.1 standard appearing on "Getieee802" at http://standards.ieee.org/getieee802/download/802.1AB-2005.pdf), where the list is "membership at the time of approval", and "balloted at various times". Since we have no clue who the "membership" of an IETF working group is, I don't know how to do the equivalent thing here. Spencer ___ Ietf mailing list Ietf@ietf.org https://www1.ietf.org/mailman/listinfo/ietf ___ Ietf mailing list Ietf@ietf.org https://www1.ietf.org/mailman/listinfo/ietf
Re: Acknowledgements section in a RFC (Was: Last Call: 'Matching of Language Tags' to BCP (draft-ietf-ltru-matching)
On Wed, Jun 07, 2006 at 09:10:25AM -0400, Joel M. Halpern <[EMAIL PROTECTED]> wrote a message of 86 lines which said: > the acknowledgements section was intended for folks who wrote > pieces, or folks who suggested useful ideas, or provided significant > useful corrections, etc. The contributors section was introduced in > conjunction with the effort to reduce the set of authors to those > who wrote the primary text. So Contributors is usually used for > those who wrote sections of text, but not enough to be authors. These rules are perfectly reasonable (even if they would cost me my acknowledgment in draft-ietf-ltru-matching) but: 1) They do not seem to be written somewhere. I cannot find them in the RFCs talking about RFCs (meta-RFCs? IPODs?). 2) They are not currently applied or enforced, as anyone can see when comparing a RFC with the work in the WG which created it. (Not a big deal but good to keep in mind when you read an Ack section.) ___ Ietf mailing list Ietf@ietf.org https://www1.ietf.org/mailman/listinfo/ietf
Re: Acknowledgements section in a RFC (Was: Last Call: 'Matching of Language Tags' to BCP (draft-ietf-ltru-matching)
Hi, In all the documents that I participated or edited, I always keep track of all the inputs and comments received and unless they are just editorial comments (unless very extensive) include them in the ack section. It is a simple matter of gratitude and simply to achieve. For many reasons, including legal ones, all the co-authors should be explicitly listed with all their details in the authors section. I will say in alphabetic order ? One possible way to avoid some of the problems listing many co-authors, co-editors, etc., in the front page header could be so simple as not having any one. Being IETF work, at the end, that don't really cares so much. However, recognizing all kind of contributors (I'm not referring just "all" the WG members), is a must, as many people contributes with their own time and it possibly the only way to get some recognition, otherwise we will start missing more and more contributors sooner or later. Also, co-authors have the right to as for who should be acknowledged. For example, several documents I've participated have been only possible thanks to the funding of research programs, such as national ones or in Europe the IST-EC one. We have the obligation to get listed as co-authors and have a citation to that co-funding to be able to get our expenses paid, and nobody can oppose to that. Regards, Jordi > De: "Joel M. Halpern" <[EMAIL PROTECTED]> > Responder a: <[EMAIL PROTECTED]> > Fecha: Wed, 07 Jun 2006 09:10:25 -0400 > Para: > Asunto: Re: Acknowledgements section in a RFC (Was: Last Call: 'Matching of > Language Tags' to BCP (draft-ietf-ltru-matching) > > The basic problem is that there is no way to acknowledge all the > folks who helped, for the most general definition of > "contributor". One would have to keep track of every person who made > a comment on the mailing list (whether the particular change ended up > used or not) and everyone who spoke at the meeting. > That is why it is common (but not mandatory) to acknowledge the > working group that worked on the draft. This relates to the > acknowledgement section more than the contributors section. > > Acknowledging folks who helped is a good idea. Particularly for a > volunteer organization. But we can not and do not have to be fanatic > about trying to acknowledge everyone. > > On a historical note, the acknowledgements section was intended for > folks who wrote pieces, or folks who suggested useful ideas, or > provided significant useful corrections, etc. The contributors > section was introduced in conjunction with the effort to reduce the > set of authors to those who wrote the primary text. So Contributors > is usually used for those who wrote sections of text, but not enough > to be authors. (The debate about whether we should ahve that > distinction is a different discussion, please.) So we actually > should be trying to be careful and thurough about the "contributors" > section, since those are folks who wrote noticeably more than a > single paragraph, and we ought to be able to tell who they are. Even > then, mistakes will be made, and as far as I can tell it is not fatal. > > Yours, > Joel M. Halpern > > At 07:47 AM 6/7/2006, Spencer Dawkins wrote: >> Perhaps I lead a sheltered life, but on two of these points... >> >>>>> - Appendix A - some names seem to be missing. I could quote a small >>>>> score of them? >>>> >>>> I do not know if there are written rules about the "Acknowledgements" >>>> or "Credits" section in a RFC. It seems quite variable between the >>>> RFCs. I am mentioned in draft-ietf-ltru-matching-14 for what I regard >>>> as a very small contribution and not in RFC 4408 where I feel that my >>>> contribution is more substantive. >>> >>> Dear Stephane, >>> This may seem trivial, but IMHO quoting every contributor is >>> important for several key reasons. >>> >>> - the IETF is made of paid and free volunteers. The reward of the >>> free participants is their exposure. If we want top quality >>> participants we must acknowledge their contributions. >> >> This is a real concern (I am a working group draft editor for a >> draft where probably 30 percent of the e-mail I've received on the >> draft has been about acknowledgements). I thought it was a more >> serious concern for academics and consultants, but am now seeing the >> same concerns from corporate standards types and development >> engineers in other working groups. I have expressed this as a >> concern in private e-mail, but don't know what the answer is. >> &g
Re: Acknowledgements section in a RFC (Was: Last Call: 'Matching of Language Tags' to BCP (draft-ietf-ltru-matching)
On 06/07/2006 09:22 AM, Stephane Bortzmeyer allegedly wrote: > These rules are perfectly reasonable (even if they would cost me my > acknowledgment in draft-ietf-ltru-matching) but: > > 1) They do not seem to be written somewhere. I cannot find them in the > RFCs talking about RFCs (meta-RFCs? IPODs?). > > 2) They are not currently applied or enforced, as anyone can see when > comparing a RFC with the work in the WG which created it. (Not a big > deal but good to keep in mind when you read an Ack section.) They should not be *rules*. If you try to formalize the definition of a "contribution", then we get into eternal niggling. If you feel like you have been unjustly left out of an acknowledgments section in a specific draft or RFC, argue your case. Let's not have yet more process and procedure and administration for issues that don't affect running code. ___ Ietf mailing list Ietf@ietf.org https://www1.ietf.org/mailman/listinfo/ietf
Re: Acknowledgements section in a RFC (Was: Last Call: 'Matching of Language Tags' to BCP (draft-ietf-ltru-matching)
On Wed, Jun 07, 2006 at 09:36:53AM -0400, Scott W Brim <[EMAIL PROTECTED]> wrote a message of 17 lines which said: > If you feel like you have been unjustly left out of an > acknowledgments section in a specific draft or RFC, Not at all. (You can read the whole thread to get the details but, as many people said, the Ack section has no practical consequences.) ___ Ietf mailing list Ietf@ietf.org https://www1.ietf.org/mailman/listinfo/ietf
Re: Acknowledgements section in a RFC (Was: Last Call: 'Matching of Language Tags' to BCP (draft-ietf-ltru-matching)
At 15:10 07/06/2006, Joel M. Halpern wrote: The basic problem is that there is no way to acknowledge all the folks who helped, for the most general definition of "contributor". One would have to keep track of every person who made a comment on the mailing list (whether the particular change ended up used or not) and everyone who spoke at the meeting. Yes. This seems to be exactly what contributing means for the IETF mailing list environment, IPR wise. Some additional attention can be paid to ADs, reviewers, and IESG Member having worked in a detailed appeal (what IESG did for my appeal against the first part of BCP47). That is why it is common (but not mandatory) to acknowledge the working group that worked on the draft. This relates to the acknowledgement section more than the contributors section. In _this_ case we have an additional element which is that a single RFC BCP becomes a two RFC BCP. The people who contributed to the first RFC and the people who contributed to the former practice should be acknowledged. Otherwise, there is no reason why we would have a BCP. Acknowledging folks who helped is a good idea. Particularly for a volunteer organization. But we can not and do not have to be fanatic about trying to acknowledge everyone. Full agreement. In _this_ case we also have an additional key need: to externally demonstrate an IETF consensus, and its respect by the IESG. The currently listed names and the way the IESG does not respect the first part of BCP 47 (cf. my appeal) lead external people feel this text is biased. I am very concerned because I think this was but is no more true (the proposed text failed two IETF LCs, this one should not): there is a tough consensus that this text is acceptable for the Internationalized ASCII Internet. jfc ___ Ietf mailing list Ietf@ietf.org https://www1.ietf.org/mailman/listinfo/ietf
RE: Acknowledgements section in a RFC (Was: Last Call: 'Matching of Language Tags' to BCP (draft-ietf-ltru-matching)
Spencer, This opens up yet another can of worms. Suppose that everybody who makes a comment on a draft (substantive, or otherwise) has to be listed and every one listed is bound by BCPs relating to IPR, copyright, etc. in RFC content. What happens if someone - perhaps having suggested that a word was misspelled - would prefer not to be bound by the BCPs (or perhaps is not permitted to be so bound)? Can they request to be left out? If they do, can an editor leave them out? It occasionally happens now that a draft departs from the original direction that some of the contributors wanted it to go, and - slightly less often - those that disagree with the outcome ask to be de-listed. There are good and reasonable reasons to allow this - especially as there may be very strong reactions from a particular employer that is seen as "advocating" something they do not intend to do. In such cases, these early contributors provided much of the content - even if the over-all outcome is not in line with their intentions. So, again, would we be able to omit their names? -- Eric --> -Original Message- --> From: Spencer Dawkins [mailto:[EMAIL PROTECTED] --> Sent: Wednesday, June 07, 2006 7:48 AM --> To: ietf@ietf.org --> Subject: Re: Acknowledgements section in a RFC (Was: Last --> Call: 'Matching of Language Tags' to BCP (draft-ietf-ltru-matching) --> --> Perhaps I lead a sheltered life, but on two of these points... --> --> >> > - Appendix A - some names seem to be missing. I could --> quote a small --> >> > score of them? --> >> --> >>I do not know if there are written rules about the --> "Acknowledgements" --> >>or "Credits" section in a RFC. It seems quite variable between the --> >>RFCs. I am mentioned in draft-ietf-ltru-matching-14 for --> what I regard --> >>as a very small contribution and not in RFC 4408 where I --> feel that my --> >>contribution is more substantive. --> > --> > Dear Stephane, --> > This may seem trivial, but IMHO quoting every contributor --> is important for --> > several key reasons. --> > --> > - the IETF is made of paid and free volunteers. The --> reward of the free --> > participants is their exposure. If we want top quality --> participants we --> > must acknowledge their contributions. --> --> This is a real concern (I am a working group draft editor --> for a draft where --> probably 30 percent of the e-mail I've received on the --> draft has been about --> acknowledgements). I thought it was a more serious concern --> for academics and --> consultants, but am now seeing the same concerns from --> corporate standards --> types and development engineers in other working groups. I --> have expressed --> this as a concern in private e-mail, but don't know what --> the answer is. --> --> > - the IPR is to all the co-authors. Every person having --> contributed a --> > word, a concept, a change, positively or negatively is a --> co-author. This --> > also has some importance to show the document is not the --> work of an --> > affinity group (as discussed in RFC 3774) but of a true WG. --> --> In my limited SDO experience, beyond IETF I am most familar --> with IEEE 802.1 --> practice, which is to list "participants" (at least, this --> is what appears in --> the most recent IEEE 802.1 standard appearing on "Getieee802" at --> http://standards.ieee.org/getieee802/download/802.1AB-2005.p --> df), where the --> list is "membership at the time of approval", and "balloted --> at various --> times". --> --> Since we have no clue who the "membership" of an IETF --> working group is, I --> don't know how to do the equivalent thing here. --> --> Spencer --> --> --> --> ___ --> Ietf mailing list --> Ietf@ietf.org --> https://www1.ietf.org/mailman/listinfo/ietf --> ___ Ietf mailing list Ietf@ietf.org https://www1.ietf.org/mailman/listinfo/ietf
Re: Acknowledgements section in a RFC (Was: Last Call: 'Matching of Language Tags' to BCP (draft-ietf-ltru-matching)
*> *> > the acknowledgements section was intended for folks who wrote *> > pieces, or folks who suggested useful ideas, or provided significant *> > useful corrections, etc. The contributors section was introduced in *> > conjunction with the effort to reduce the set of authors to those *> > who wrote the primary text. So Contributors is usually used for *> > those who wrote sections of text, but not enough to be authors. *> *> These rules are perfectly reasonable (even if they would cost me my *> acknowledgment in draft-ietf-ltru-matching) but: *> *> 1) They do not seem to be written somewhere. I cannot find them in the *> RFCs talking about RFCs (meta-RFCs? IPODs?). The text in Section 2.12 of RFC223bis is intended to state these guidelines. See: ftp://ftp.rfc-editor.org/in-notes/rfc-editor/instructions2authors.txt The RFC Editor would be happy to receive suggestions for augmentation or modification of the text in this section. Bob Braden for the RFC Editor ___ Ietf mailing list Ietf@ietf.org https://www1.ietf.org/mailman/listinfo/ietf
Re: Acknowledgements section in a RFC (Was: Last Call: 'Matching of Language Tags' to BCP (draft-ietf-ltru-matching)
On Wed, 7 Jun 2006, Spencer Dawkins wrote: Perhaps I lead a sheltered life, but on two of these points... - the IETF is made of paid and free volunteers. The reward of the free participants is their exposure. If we want top quality participants we must acknowledge their contributions. This is a real concern (I am a working group draft editor for a draft where probably 30 percent of the e-mail I've received on the draft has been about acknowledgements). I thought it was a more serious concern for academics and consultants, but am now seeing the same concerns from corporate standards types and development engineers in other working groups. I have expressed this as a concern in private e-mail, but don't know what the answer is. The entire archive of any WG list is saved and available, so comments made to the list are easy to track. Thoughtful comments and reviews published to the list should serve to document individual opinions and contributions. We use list traffic now to document objections, so I don't see why we can't use it to document WG member contributions. - the IPR is to all the co-authors. Every person having contributed a word, a concept, a change, positively or negatively is a co-author. This also has some importance to show the document is not the work of an affinity group (as discussed in RFC 3774) but of a true WG. In my limited SDO experience, beyond IETF I am most familar with IEEE 802.1 practice, which is to list "participants" (at least, this is what appears in the most recent IEEE 802.1 standard appearing on "Getieee802" at http://standards.ieee.org/getieee802/download/802.1AB-2005.pdf), where the list is "membership at the time of approval", and "balloted at various times". Since we have no clue who the "membership" of an IETF working group is, I don't know how to do the equivalent thing here. Maybe we can say that this is documented via public posting to the list - private comments made off list are just that - private comments. Spencer ___ Ietf mailing list Ietf@ietf.org https://www1.ietf.org/mailman/listinfo/ietf -- Lucy E. Lynch Academic User Services Computing CenterUniversity of Oregon llynch @darkwing.uoregon.edu (541) 346-1774 ___ Ietf mailing list Ietf@ietf.org https://www1.ietf.org/mailman/listinfo/ietf
RE: Acknowledgements section in a RFC (Was: Last Call: 'Matching of Language Tags' to BCP (draft-ietf-ltru-matching)
--On Wednesday, 07 June, 2006 12:33 -0400 "Gray, Eric" <[EMAIL PROTECTED]> wrote: > Spencer, > > This opens up yet another can of worms. Suppose that > everybody who makes a comment on a draft (substantive, or > otherwise) has to be listed and every one listed is bound by > BCPs relating to IPR, copyright, etc. in RFC content. They are so bound... read the Note Well. Whether they should be so listed is a separate issue. > What happens if someone - perhaps having suggested that > a word was misspelled - would prefer not to be bound by the > BCPs (or perhaps is not permitted to be so bound)? Can they > request to be left out? If they do, can an editor leave them > out? Too bad. If they participate in the IETF at the level of either attending meetings or saying anything, they are stuck. While there are guidelines now (see Bob Braden's note) and guidelines can always be further tuned, I think we need to give some discretion to document editors about who should be listed --at least until and unless we have a clear definition of, e.g., WG membership. > It occasionally happens now that a draft departs from > the original direction that some of the contributors wanted > it to go, and - slightly less often - those that disagree > with the outcome ask to be de-listed. There are good and > reasonable reasons to allow this - especially as there may > be very strong reactions from a particular employer that is > seen as "advocating" something they do not intend to do. > > In such cases, these early contributors provided much > of the content - even if the over-all outcome is not in line > with their intentions. So, again, would we be able to omit > their names? I have often dealt with that issue in acknowledgements by being very explicit that all contributors may not agree with the conclusions reached as a consequence of their suggestions (or with their suggestions included). An even more extreme case exists than the ones that you mention: someone raises an issue and preference and the document is ultimately clarified to reflect exactly the opposite preference. In some of these cases, the document would not have addressed the topic at all had the issue not been raised. The person who raised the issue may still have made a contribution significant enough to justify acknowledgement but may have always been in violent disagreement with the conclusion reached by the IETF process about how to deal with it. The underlying problem here is not unique to the IETF. And people who don't want to contribute or be bound by the rules should avoid participation -- there isn't any "whoops, I don't like the results so the rules should retroactively not apply to me and the fact that I participated at all should be erased" option. Having such an option with regard to rule-conforming would result in chaos. Again, the Note Well is very clear about this (and there is a parallel discussion going in circles, perhaps parallel ones, in the IPR WG). john ___ Ietf mailing list Ietf@ietf.org https://www1.ietf.org/mailman/listinfo/ietf
RE: Acknowledgements section in a RFC (Was: Last Call: 'Matching of Language Tags' to BCP (draft-ietf-ltru-matching)
John, I disagree both in the belief that the Note Well is clear on this and the sense of your argument that anyone participating in any part of a discussion can be made retroactively responsible for the entire discussion. The Note Well is not clear because it makes sweeping statements about the way in which BCP 78 and 79 may apply to "contributions". The obvious (but not clear) intent is that what you contribute is now subject to provisions of these BCPs that apply to contributions. What is both more subtle and not clearly excluded is that _only_ what you've contributed applies and that contributing to a work is not the same as "authoring" it. I refer directly to the required RFC inclusions that specifically use the word "author" and their rights and responsibilities with respect to IPR and copyrights. If I make a comment about a rev -01 version of a draft and stop participating in the work, I may not be held accountable for IPR I may know of but which did not enter into the text until sometime after I stopped looking at it. Similarly, if I object to work that has been done, you may not attach my name to it against my objections - unless either the Note Well, and the BCPs, both explicitly include a provision for implied consent. If that is the case, now, then it is most certainly not "clear" that it is. This is the negative side of the discussion going on. People are focusing on reasons why someone might want to be included in acknowledgements. I am merely pointing out that it is also possible that someone might not want this. -- Eric --> -Original Message- --> From: John C Klensin [mailto:[EMAIL PROTECTED] --> Sent: Wednesday, June 07, 2006 1:53 PM --> To: Gray, Eric; Spencer Dawkins --> Cc: ietf@ietf.org --> Subject: RE: Acknowledgements section in a RFC (Was: Last --> Call: 'Matching of Language Tags' to BCP (draft-ietf-ltru-matching) --> --> --> --> --On Wednesday, 07 June, 2006 12:33 -0400 "Gray, Eric" --> <[EMAIL PROTECTED]> wrote: --> --> > Spencer, --> > --> > This opens up yet another can of worms. Suppose that --> > everybody who makes a comment on a draft (substantive, or --> > otherwise) has to be listed and every one listed is bound by --> > BCPs relating to IPR, copyright, etc. in RFC content. --> --> They are so bound... read the Note Well. Whether they should be --> so listed is a separate issue. --> --> > What happens if someone - perhaps having suggested that --> > a word was misspelled - would prefer not to be bound by the --> > BCPs (or perhaps is not permitted to be so bound)? Can they --> > request to be left out? If they do, can an editor leave them --> > out? --> --> Too bad. If they participate in the IETF at the level of either --> attending meetings or saying anything, they are stuck. While --> there are guidelines now (see Bob Braden's note) and guidelines --> can always be further tuned, I think we need to give some --> discretion to document editors about who should be listed --at --> least until and unless we have a clear definition of, e.g., WG --> membership. --> --> > It occasionally happens now that a draft departs from --> > the original direction that some of the contributors wanted --> > it to go, and - slightly less often - those that disagree --> > with the outcome ask to be de-listed. There are good and --> > reasonable reasons to allow this - especially as there may --> > be very strong reactions from a particular employer that is --> > seen as "advocating" something they do not intend to do. --> > --> > In such cases, these early contributors provided much --> > of the content - even if the over-all outcome is not in line --> > with their intentions. So, again, would we be able to omit --> > their names? --> --> I have often dealt with that issue in acknowledgements by being --> very explicit that all contributors may not agree with the --> conclusions reached as a consequence of their suggestions (or --> with their suggestions included). An even more extreme case --> exists than the ones that you mention: someone raises an issue --> and preference and the document is ultimately clarified to --> reflect exactly the opposite preference. In some of these --> cases, the document would not have addressed the topic at all --> had the issue not been raised. The person who raised the issue --> may still have made a contribution significant enough to justify --> acknowledgement but may have always been in violent disagreement --> with the conclusion reached by the IETF process about how to --> deal with it. --> --> The under
RE: Acknowledgements section in a RFC (Was: Last Call: 'Matching of Language Tags' to BCP (draft-ietf-ltru-matching)
Hi, In transferring responsibility for the Bridge MIBs to IEEE 802, we learned that the IETF has certain copyrights to documents that have been submitted to the IETF for IETF purposes. All other rights remain with the authors, and the IEEE had to contact the authors to get permission to do non-IETF things with the documents. The IETF has no authority to transfer the authors' rights to other organizations/persons for non-IETF purposes. So it is not important for IETF purposes for the IETF to define requirements about listing authors and contributors to IETF documents. It may be important to the authors and contributors and to others who want to ask those authors for permissions to do non-IETF things, or if the IETF decides it needs the rights to transfer rights to others for non-IETF purposes. David Harrington [EMAIL PROTECTED] [EMAIL PROTECTED] [EMAIL PROTECTED] > -Original Message- > From: John C Klensin [mailto:[EMAIL PROTECTED] > Sent: Wednesday, June 07, 2006 1:53 PM > To: Gray, Eric; Spencer Dawkins > Cc: ietf@ietf.org > Subject: RE: Acknowledgements section in a RFC (Was: Last > Call: 'Matching of Language Tags' to BCP (draft-ietf-ltru-matching) > > > > --On Wednesday, 07 June, 2006 12:33 -0400 "Gray, Eric" > <[EMAIL PROTECTED]> wrote: > > > Spencer, > > > > This opens up yet another can of worms. Suppose that > > everybody who makes a comment on a draft (substantive, or > > otherwise) has to be listed and every one listed is bound by > > BCPs relating to IPR, copyright, etc. in RFC content. > > They are so bound... read the Note Well. Whether they should be > so listed is a separate issue. > > > What happens if someone - perhaps having suggested that > > a word was misspelled - would prefer not to be bound by the > > BCPs (or perhaps is not permitted to be so bound)? Can they > > request to be left out? If they do, can an editor leave them > > out? > > Too bad. If they participate in the IETF at the level of either > attending meetings or saying anything, they are stuck. While > there are guidelines now (see Bob Braden's note) and guidelines > can always be further tuned, I think we need to give some > discretion to document editors about who should be listed --at > least until and unless we have a clear definition of, e.g., WG > membership. > > > It occasionally happens now that a draft departs from > > the original direction that some of the contributors wanted > > it to go, and - slightly less often - those that disagree > > with the outcome ask to be de-listed. There are good and > > reasonable reasons to allow this - especially as there may > > be very strong reactions from a particular employer that is > > seen as "advocating" something they do not intend to do. > > > > In such cases, these early contributors provided much > > of the content - even if the over-all outcome is not in line > > with their intentions. So, again, would we be able to omit > > their names? > > I have often dealt with that issue in acknowledgements by being > very explicit that all contributors may not agree with the > conclusions reached as a consequence of their suggestions (or > with their suggestions included). An even more extreme case > exists than the ones that you mention: someone raises an issue > and preference and the document is ultimately clarified to > reflect exactly the opposite preference. In some of these > cases, the document would not have addressed the topic at all > had the issue not been raised. The person who raised the issue > may still have made a contribution significant enough to justify > acknowledgement but may have always been in violent disagreement > with the conclusion reached by the IETF process about how to > deal with it. > > The underlying problem here is not unique to the IETF. And > people who don't want to contribute or be bound by the rules > should avoid participation -- there isn't any "whoops, I don't > like the results so the rules should retroactively not apply to > me and the fact that I participated at all should be erased" > option. Having such an option with regard to rule-conforming > would result in chaos. Again, the Note Well is very clear about > this (and there is a parallel discussion going in circles, > perhaps parallel ones, in the IPR WG). > > john > > > > ___ > Ietf mailing list > Ietf@ietf.org > https://www1.ietf.org/mailman/listinfo/ietf > ___ Ietf mailing list Ietf@ietf.org https://www1.ietf.org/mailman/listinfo/ietf
RE: Acknowledgements section in a RFC (Was: Last Call: 'Matching of Language Tags' to BCP (draft-ietf-ltru-matching)
--On Wednesday, 07 June, 2006 14:22 -0400 "Gray, Eric" <[EMAIL PROTECTED]> wrote: > John, > > I disagree both in the belief that the Note Well is > clear on this and the sense of your argument that anyone > participating in any part of a discussion can be made > retroactively responsible for the entire discussion. I think were we disagree is about the notion that inclusion of one's name in an acknowledgement implies "responsibility" for any part of the discussion, much less all of it. > The Note Well is not clear because it makes sweeping > statements about the way in which BCP 78 and 79 may apply > to "contributions". The obvious (but not clear) intent is > that what you contribute is now subject to provisions of > these BCPs that apply to contributions. What is both more > subtle and not clearly excluded is that _only_ what you've > contributed applies and that contributing to a work is not > the same as "authoring" it. To the extent to which you believe that the Note Well is unclear or defective, please take that to the IPR WG. > I refer directly to the required RFC inclusions that > specifically use the word "author" and their rights and > responsibilities with respect to IPR and copyrights. If I > make a comment about a rev -01 version of a draft and stop > participating in the work, I may not be held accountable > for IPR I may know of but which did not enter into the text > until sometime after I stopped looking at it. I believe that is true. I also do not believe that an acknowledgement constitutes an assertion of accountability. But those are matters for counsel -- I will assert my beliefs about what ought to be happening here, but not about the legal implications of particular text. In particular, I do not believe that inclusion or exclusion from an acknowledgement implies an IPR claims or responsibilities at all: to do so would confound many centuries of publications history. An exception might(and probably would) arise if the contribution were identified in very specific terms, but those terms would bind that particular author/ contributor only to that text. As far as I recall, we have never included text in acknowledgements that says, e.g., "Joe Blow contributed section 1.2.3.4 in its entirety and it is used with his permission", so the implications of that form are not relevant. > Similarly, if I object to work that has been done, you > may not attach my name to it against my objections - unless > either the Note Well, and the BCPs, both explicitly include > a provision for implied consent. If that is the case, now, > then it is most certainly not "clear" that it is. It would clearly be inappropriate to list you as an author. Given our current peculiar definition of "Contributor" in the RFC sense, it would probably be inappropriate to include you as one of those, at least without permitting you to include a statement of dissent. It seems to me that you have no standing to object to the inclusion of your name in an acknowledgement if you, in fact, did something that the author thought was appropriate to acknowledge. I'd hope that, in normal circumstances, the author would honor your request to remove your name, but I can also see circumstances in which removing your name would be inappropriate. As one specific example, suppose the acknowledgements said "Significant contributions to the topics discussed in this document came from an ad hoc group consisting of ". Now, adding a "not all members of the group agree with the final conclusions represented in this document" would be appropriate if true. But removing a name from the list of people who participated in the group, especially the name of someone who could be clearly determined from the group's mailing list to have actively participated, would simply be a lie and, IMO, completely inappropriate. > This is the negative side of the discussion going on. > People are focusing on reasons why someone might want to be > included in acknowledgements. I am merely pointing out that > it is also possible that someone might not want this. Understood. But that is precisely why listing in an acknowledgement must not have implications of "responsibility" for the whole document. And this discussion really belongs in the IPR WG. john ___ Ietf mailing list Ietf@ietf.org https://www1.ietf.org/mailman/listinfo/ietf
RE: Acknowledgements section in a RFC (Was: Last Call: 'Matching of Language Tags' to BCP (draft-ietf-ltru-matching)
John, Agree. --> -Original Message- --> From: John C Klensin [mailto:[EMAIL PROTECTED] --> Sent: Wednesday, June 07, 2006 3:04 PM --> To: Gray, Eric --> Cc: ietf@ietf.org --> Subject: RE: Acknowledgements section in a RFC (Was: Last --> Call: 'Matching of Language Tags' to BCP (draft-ietf-ltru-matching) --> --> --> --> --On Wednesday, 07 June, 2006 14:22 -0400 "Gray, Eric" --> <[EMAIL PROTECTED]> wrote: --> --> > John, --> > --> > I disagree both in the belief that the Note Well is --> > clear on this and the sense of your argument that anyone --> > participating in any part of a discussion can be made --> > retroactively responsible for the entire discussion. --> --> I think were we disagree is about the notion that inclusion of --> one's name in an acknowledgement implies "responsibility" for --> any part of the discussion, much less all of it. --> --> > The Note Well is not clear because it makes sweeping --> > statements about the way in which BCP 78 and 79 may apply --> > to "contributions". The obvious (but not clear) intent is --> > that what you contribute is now subject to provisions of --> > these BCPs that apply to contributions. What is both more --> > subtle and not clearly excluded is that _only_ what you've --> > contributed applies and that contributing to a work is not --> > the same as "authoring" it. --> --> To the extent to which you believe that the Note Well is unclear --> or defective, please take that to the IPR WG. --> --> > I refer directly to the required RFC inclusions that --> > specifically use the word "author" and their rights and --> > responsibilities with respect to IPR and copyrights. If I --> > make a comment about a rev -01 version of a draft and stop --> > participating in the work, I may not be held accountable --> > for IPR I may know of but which did not enter into the text --> > until sometime after I stopped looking at it. --> --> I believe that is true. I also do not believe that an --> acknowledgement constitutes an assertion of accountability. --> But those are matters for counsel -- I will assert my beliefs --> about what ought to be happening here, but not about the legal --> implications of particular text. In particular, I do not --> believe that inclusion or exclusion from an acknowledgement --> implies an IPR claims or responsibilities at all: to do so would --> confound many centuries of publications history. An exception --> might(and probably would) arise if the contribution were --> identified in very specific terms, but those terms would bind --> that particular author/ contributor only to that text. As far --> as I recall, we have never included text in acknowledgements --> that says, e.g., "Joe Blow contributed section 1.2.3.4 in its --> entirety and it is used with his permission", so the --> implications of that form are not relevant. --> --> > Similarly, if I object to work that has been done, you --> > may not attach my name to it against my objections - unless --> > either the Note Well, and the BCPs, both explicitly include --> > a provision for implied consent. If that is the case, now, --> > then it is most certainly not "clear" that it is. --> --> It would clearly be inappropriate to list you as an author. --> Given our current peculiar definition of "Contributor" in the --> RFC sense, it would probably be inappropriate to include you as --> one of those, at least without permitting you to include a --> statement of dissent. It seems to me that you have no standing --> to object to the inclusion of your name in an acknowledgement if --> you, in fact, did something that the author thought was --> appropriate to acknowledge. I'd hope that, in normal --> circumstances, the author would honor your request to remove --> your name, but I can also see circumstances in which removing --> your name would be inappropriate. --> --> As one specific example, suppose the acknowledgements said --> "Significant contributions to the topics discussed in this --> document came from an ad hoc group consisting of participants in that group>". Now, adding a "not all members of --> the group agree with the final conclusions represented in this --> document" would be appropriate if true. But removing a name --> from the list of people who participated in the group, --> especially the name of someone who could be clearly determined --> from the group's mailing list to have actively participated, --> would simply be a lie and
Re: Acknowledgements section in a RFC (Was: Last Call: 'Matching of Language Tags' to BCP (draft-ietf-ltru-matching)
On Jun 7, 2006, at 12:03 PM, John C Klensin wrote: This is the negative side of the discussion going on. People are focusing on reasons why someone might want to be included in acknowledgements. I am merely pointing out that it is also possible that someone might not want this. Understood. But that is precisely why listing in an acknowledgement must not have implications of "responsibility" for the whole document. Guys: can you say "majoring on the minors"? Acknowledgments are used every way under the sun. Marshall Rose, in early SNMP documents, listed the entire working group by name as having contributed in some way. I generally list the people who send me comments on drafts, and if they send unusually large number of comments, I might say as much. The fact that they sent notes doesn't mean they agree - far from it. For example, RFC 4192 (procedures for renumbering) makes the following observation: This document grew out of a discussion on the IETF list. Commentary on the document came from [major snippage]. Some took it on themselves to convince the authors that the concept of network renumbering as a normal or frequent procedure is daft. Their comments, if they result in improved address management practices in networks, may be the best contribution this note has to offer. I would be hard pressed to say that the folks who wrote to tell me I was wasting my time even thinking about the subject were responsible for what I wrote. No acknowledgment that I know of attributes responsibility to those who commented. That is invariably the domain of the authors, editors, or the working group that managed them. ___ Ietf mailing list Ietf@ietf.org https://www1.ietf.org/mailman/listinfo/ietf
RE: Acknowledgements section in a RFC (Was: Last Call: 'Matching of Language Tags' to BCP (draft-ietf-ltru-matching)
Disclaimer: IANAL, and this message is not intended as legal advice. Please, read RFC3979 for yourself, and if you have concerns as to what your obligations are or what you can get away with, consult a lawyer. On Wednesday, June 07, 2006 02:22:06 PM -0400 "Gray, Eric" <[EMAIL PROTECTED]> wrote: The Note Well is not clear because it makes sweeping statements about the way in which BCP 78 and 79 may apply to "contributions". The "Note Well" is a notification that if you contribute, you have certain obligations. It is not a normative description of those obligations; for that, you need to refer to BCP 78 and 79. Those documents make it quite clear that you are obligated to disclose certain IPR if you make a contribution in _any_ form, including comments made in a meeting or on a mailing list, or to an IESG or IAB member, or to a "portion" of any working group, which is intended to cover a variety of ways in which people provide input outside the context of a formal meeting. BCP79 requires you to make disclosures of your or your employers IPR in a contribution you make, and normally in contributions you don't make but are aware of, even if you become aware of the IPR after the contribution is made. Not becoming aware of the IPR until after the document is published does not relieve you of the obligation to disclose it. Nor does having the contribution be made by someone else, even if they don't work for your company and/or are unaware of the IPR. participating in the work, I may not be held accountable for IPR I may know of but which did not enter into the text until sometime after I stopped looking at it. You're only obligated to make an IPR disclosure if the IPR is owned by you or your company and either (1) you made the contribution, or (2) the contribution was made in a discussion in which you are participating. If you stop participating in a discussion, you no longer have the responsibility to make IPR disclosures related to contributions made after you stop participating. Similarly, if I object to work that has been done, you may not attach my name to it against my objections - unless either the Note Well, and the BCPs, both explicitly include a provision for implied consent. If that is the case, now, then it is most certainly not "clear" that it is. Certainly, no one should be represented as supporting work which they do not support. It is entirely reasonable to request that your name be removed from the list of authors, if you no longer wish to perform the duties of an author, or from the list of contributors, if you did not make a contribution or don't want your contribution noted. Acknowledgements are more of a "thanks for your input", and it's not really reasonable to tell authors that he can't acknowledge people whose input they found helpful - as long as an acknowledgement does not imply endorsement on the part of the person who is acknowledged. On the other hand, IMHO it would be even _more_ unreasonable for an author to refuse to remove the name of a person who did not want to be acknowledged. This is the negative side of the discussion going on. People are focusing on reasons why someone might want to be included in acknowledgements. I am merely pointing out that it is also possible that someone might not want this. And John's point is this: There may be legitimate reasons for not wanting to be acknowledged or listed as an author or contributor. However, having your name removed from the document does not change the fact of your contribution, or relieve you of your obligations with respect to that contribution. Now, you made specific reference to the IPR disclosure acknowledgement which is required by RFC3978 section 5.1 to be present in all I-D's. Your argument seems to be that this statement imposes an additional burden upon anyone listed as an author, and that one might want to be removed from the author list in order to be relieved of this burden. But if you read the acknowledgement carefully, the representation being made by the authors is that they are in compliance with BCP 79 section 6(*). Since compliance with that section is required for _anyone_ making a contribution to the IETF, being removed from the author list does _not_ relieve you of that burden - it simply allows you to avoid preiodically representing that you are meeting it. I completely agree that anyone who no longer wishes to be listed as an author of an I-D should be able to have their name removed. However, doing so does not remove your obligations relating to IPR disclosures. (*) The exact text quoted in RFC3978 is "... in accordance with Section 6 of BCP 79." Ordinarily, a reference is made to a BCP or STD number rather than to an RFC number when the goal is to produce a "live" reference that always refers to the latest approved version of the document. We usually avoid doing this in protocol
Re: Acknowledgements section in a RFC (Was: Last Call: 'Matching of Language Tags' to BCP (draft-ietf-ltru-matching)
Jeffrey Hutzelman wrote: Disclaimer: IANAL, and this message is not intended as legal advice. Please, read RFC3979 for yourself, and if you have concerns as to what your obligations are or what you can get away with, consult a lawyer. On Wednesday, June 07, 2006 02:22:06 PM -0400 "Gray, Eric" <[EMAIL PROTECTED]> wrote: The Note Well is not clear because it makes sweeping statements about the way in which BCP 78 and 79 may apply to "contributions". Eric, there is no "may" about it. It states very clearly that *all* contributions are covered. The definition of "contribution" is spelled out in BCP 79 as Definition 1.c. I see no ambiguity whatever. The "Note Well" is a notification that if you contribute, you have certain obligations. It is not a normative description of those obligations; for that, you need to refer to BCP 78 and 79. Those documents make it quite clear that you are obligated to disclose certain IPR if you make a contribution in _any_ form, including comments made in a meeting or on a mailing list, or to an IESG or IAB member, or to a "portion" of any working group, which is intended to cover a variety of ways in which people provide input outside the context of a formal meeting. BCP79 requires you to make disclosures of your or your employers IPR in a contribution you make, and normally in contributions you don't make but are aware of, even if you become aware of the IPR after the contribution is made. Not becoming aware of the IPR until after the document is published does not relieve you of the obligation to disclose it. Nor does having the contribution be made by someone else, even if they don't work for your company and/or are unaware of the IPR. participating in the work, I may not be held accountable for IPR I may know of but which did not enter into the text until sometime after I stopped looking at it. You're only obligated to make an IPR disclosure if the IPR is owned by you or your company and either (1) you made the contribution, or (2) the contribution was made in a discussion in which you are participating. If you stop participating in a discussion, you no longer have the responsibility to make IPR disclosures related to contributions made after you stop participating. Also, BCP 79 does not require a patent search - it applies explicitly to IPR of which the contributor is reasonably and personally aware. So it isn't an onerous obligation; you don't have to worry about unknowns. Brian Similarly, if I object to work that has been done, you may not attach my name to it against my objections - unless either the Note Well, and the BCPs, both explicitly include a provision for implied consent. If that is the case, now, then it is most certainly not "clear" that it is. Certainly, no one should be represented as supporting work which they do not support. It is entirely reasonable to request that your name be removed from the list of authors, if you no longer wish to perform the duties of an author, or from the list of contributors, if you did not make a contribution or don't want your contribution noted. Acknowledgements are more of a "thanks for your input", and it's not really reasonable to tell authors that he can't acknowledge people whose input they found helpful - as long as an acknowledgement does not imply endorsement on the part of the person who is acknowledged. On the other hand, IMHO it would be even _more_ unreasonable for an author to refuse to remove the name of a person who did not want to be acknowledged. This is the negative side of the discussion going on. People are focusing on reasons why someone might want to be included in acknowledgements. I am merely pointing out that it is also possible that someone might not want this. And John's point is this: There may be legitimate reasons for not wanting to be acknowledged or listed as an author or contributor. However, having your name removed from the document does not change the fact of your contribution, or relieve you of your obligations with respect to that contribution. Now, you made specific reference to the IPR disclosure acknowledgement which is required by RFC3978 section 5.1 to be present in all I-D's. Your argument seems to be that this statement imposes an additional burden upon anyone listed as an author, and that one might want to be removed from the author list in order to be relieved of this burden. But if you read the acknowledgement carefully, the representation being made by the authors is that they are in compliance with BCP 79 section 6(*). Since compliance with that section is required for _anyone_ making a contribution to the IETF, being removed from the author list does _not_ relieve you of that burden - it simply allows you to avoid preiodically representing that you are meeting it. I completely agree that anyone who no longer wishes to be listed as an author of an I-D should be