On Tue, May 9, 2017 at 8:07 PM Scott O. Bradner <[email protected]> wrote:
> > > On May 9, 2017, at 1:41 PM, Alan DeKok <[email protected]> > wrote: > > > > I've taken a look at the latest draft, and have some serious concerns. > > > > Specifically, large chunks of the Security Considerations sections > appear to have been lifted from my post to the list: > > > > https://mailarchive.ietf.org/arch/msg/opsawg/tU2wBFIV4MkpKChWn6EvrqeZtXU > > > > There are minor edits, but multiple sentences are copied word for > word. Sentences which don't occur in the -05 draft, but do appear in my > review, and subsequently are copied to the -06 draft with minor edits. > > > > Multiple paragraphs are copied with only minor edits. The total > amounts to about a page of text. > > > > While I appreciate that the document is improving, blatant copying of > my text without attribution is entirely inappropriate. > > using the text that was contributed is legit but not acknowledging the > source in the acknowledgements section violates IETF requirement to > acknowledge all significant contributions > Yes. This document was resurrected from a really old document (1998) which did not have an Acknowledgement section. The authors have already said "Certainly, that was an oversight on our part" and that they would add an acknowledgement section and acknowledge Alan's contribution. W [ Monkey typed on a small screen, apologies for typos ] > Scott > > > > > > What are the chairs recommendations? > > > > Alan DeKok. > > > > > > _______________________________________________ > > OPSAWG mailing list > > [email protected] > > https://www.ietf.org/mailman/listinfo/opsawg > > _______________________________________________ > OPSAWG mailing list > [email protected] > https://www.ietf.org/mailman/listinfo/opsawg >
_______________________________________________ OPSAWG mailing list [email protected] https://www.ietf.org/mailman/listinfo/opsawg
