The IESG discussed this years ago (during my prior term) and decided the following:
- Such disclaimers are impossible for us to stop: they're mandated by people's companies and they will appear. - Regardless of what disclaimers appear in people's messages, any messages that amount to Contributions, as defined in BCP 79, are covered by the terms in BCP 79. - People might have the option of using non-work email addresses to avoid having such disclaimers put on their mail by their employers, but some employers might forbid that as well. - We need to just let this stuff go and not worry about it. Barry On Mon, Mar 2, 2020 at 2:10 PM Alvaro Retana <aretana.i...@gmail.com> wrote: > > On March 2, 2020 at 1:21:25 PM, S Moonesamy wrote: > > [Changed the subject to better reflect the topic and for easier tracking.] > > > SM: > > Hi! How are you? > > > I sent a message to the SPRING Working Group Chairs. The reply which > > I received from a person who is listed as one of the SPRING Working > > Group Chairs contains the following footer: > > > > "This message and its attachments may contain confidential or privileged > > information that may be protected by law; they should not be distributed, > > used or copied without authorisation. > > If you have received this email in error, please notify the > > sender and delete this message and its attachments. > > As emails may be altered, Orange is not liable for messages that > > have been modified, changed or falsified." > > > > From what I understand, the IESG position on automated disclaimers > > was that they are not applicable within the context of BCP 9. Was > > there a change to that? > > I looked at BCP 9, but didn't find anything related to your question. > If I missed it, please point me in the right direction. I think you > may be referring to BCP 78. > > Specifically, rfc5378 (Rights Contributors Provide to the IETF Trust) reads: > > 5.2. Confidentiality Obligations > > No information or document that is subject to any requirement of > confidentiality or any restriction on its dissemination may be > submitted as a Contribution or otherwise considered in any part of > the IETF Standards Process, and there must be no assumption of any > confidentiality obligation with respect to any Contribution. Each > Contributor agrees that any statement in a Contribution, whether > generated automatically or otherwise, that states or implies that the > Contribution is confidential or subject to any privilege, can be > disregarded for all purposes, and will be of no force or effect. > > > Note that this section is clearly only talking about statements in a > Contribution (I pasted the definition of "Contribution" below, from > the same RFC). > > If you have other general questions or concerns about this topic, it > might be more productive to separate them into their own thread. > > Regards, > > Alvaro. > > > > >From rfc5378/§1: > > a. "Contribution": any submission to the IETF intended by the > Contributor for publication as all or part of an Internet-Draft or > RFC (except for RFC Editor Contributions described in Section 4 > below) and any statement made within the context of an IETF > activity. Such statements include oral statements in IETF > sessions as well as written and electronic communications, made at > any time or place, that are addressed to: > > o the IETF plenary session, > o any IETF working group or portion thereof, > o any Birds of a Feather (BOF) session, > o the IESG, or any member thereof on behalf of the IESG, > o the IAB, or any member thereof on behalf of the IAB, > o any IETF mailing list, including the IETF list itself, any > working group or design team list, or any other list functioning > under IETF auspices, > o the RFC Editor or the Internet-Drafts function (except for RFC > Editor Contributions, as described in Section 4 below). > > Statements made outside of an IETF session, mailing list, or other > function, that are clearly not intended to be input to an IETF > activity, group, or function are not IETF Contributions in the > context of this document. > _______________________________________________ spring mailing list spring@ietf.org https://www.ietf.org/mailman/listinfo/spring
