License File for Open Source Repositories
Many working groups work with open source repositories, even for their work on specifications.
The intent behind this policy is to balance people's legitimate desire not to be photographed with the IETF's ability to document activities and enable remote participation. The following policy applies to all IETF events, including WG meetings, plenaries, and the hackathon.
The IETF will make available a mechanism for participants to label themselves as desiring not to be photographed. The secretariat will determine the details in consultation with the IESG.
Any photographer engaged on behalf of the IETF should not photograph individuals displaying the "do-not-photograph" label, should make reasonable efforts to avoid photographing small groups with one or more members displaying the label, and should not publish small group photographs with such individuals in them. There are two important exceptions to this policy:
Working group meetings are generally video recorded and broadcast, for remote participation and archival purposes, and no attempt will be made to avoid recording individuals. However, if the IETF publishes still frames of these videos, individuals displaying the labels should not be shown.
Note: the use of "should" above is intended to reflect that although this is IETF policy, it is a best effort service and some mistakes will likely be made, perhaps because someone's label is not noticed or visible. Individuals can contact Greg Wood (wood at isoc.org) to arrange for redaction of their images or to report abuse.
Many IETF participants also engage in photography. We ask that those participants avoid photographing individuals who have asked not to be photographed or are displaying the "do-not-photograph" label, except under the conditions listed above.
Many working groups work with open source repositories, even for their work on specifications.
There is a class of documents that help guiding a working group to agree on the problem(s) and even converge on a solution. These support documents can include, for example, problem statements, use cases, and requirements.
The IETF has recognised that the act of accessing public information required for routine tasks can be privacy sensitive and can benefit from using a confidentiality service, such as is provided by TLS. [BCP188]
The IESG has received some reports of IETF participants having been listed as document authors on drafts without their consent ("surprised authorship").
RFC 2026 defines a "Historic" status for documents: A specification that has been superseded by a more recent specification or is for any other reason considered to be obsolete is assigned to the "Historic" level.
Show all