11 Matching Annotations
  1. Mar 2017
    1. The report itself contains data about messages addressed to users at gmail.com and many other domains hosted by Google

      This implies a receiver cannot attempt to match received reports with the mail it sent. Looking up Public Suffix List does not disclose that google and gmail belong to the same organization.

    2. DMARC aggregate reports should use UTC day boundaries for the reporting intervals.

      Reports can be sent some time after the end of the interval. (A difficulty is to set a cron job at UTC, so I send with one hour delay.)

    3. The receiver could use the following data points to better understand their incoming email traffic:

      How does a receiver collect that data?

    4. Incremental Roll-Out.

      A possibility is to enable/disable honoring DMARC policy on a per-domain basis (I currently have globally disable and enable on a few domains which send only transactional mail).

      Perhaps, the possibility to override the remote policy should also be considered.

    5. The collection of feedback statistics for use in generating DMARC aggregate likely presents the most opportunity for new development.

      An important consideration is the sending domains database. SMTP specification need no database (except the ubiquitous DNS). DMARC needs some kind of database in order to send reports. This need should be enounced early in this document. Many practices can then be expressed in terms of database operations and structure.

  2. Oct 2016
    1. DNC stores 'temporal links' to keep track of the order things were written in

      This would be the definition of "temporal", in a cosmology-oriented theorization.

  3. Sep 2016
    1. several

      two, actually

    2. Figure 1 illustrates the relationship between verification conditions and Authentication-Results.

      It should at least be stated that SPF and DKIM records can, in turn, exist in the domain's DNS or not.

    1. Data centers

      Should we not mention the possibility that someone plainly hosts a server at home? For one thing, the security of not allowing remote shells at all is unbeatable.

  4. Jul 2016
    1. All public annotations made on Hypothesis are explicitly in the public domain. See also the Hypothesis Terms of Service, https://hypothes.is/terms-of-service/. Note that Hypothesis itself is a non-profit organization.

      That seems to imply that the IETF should use hypothes.is for the service. That is just one possible annotation providers. If the experiment is successful, annotations will presumably have to be moved to an IETF server and use Annotator directly.

    1. A Standard for the Transmission of IP Datagrams on Avian Carriers

      Can U see 2 annotations on this title?