Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Jump to bottom

wg-amp4email Status Update 2019-08-14 #9

Closed
dreamofabear opened this issue Aug 16, 2019 · 0 comments
Closed

wg-amp4email Status Update 2019-08-14 #9

dreamofabear opened this issue Aug 16, 2019 · 0 comments
Labels
Type: Status Update

Comments

@dreamofabear
Copy link
Collaborator

Highlights

  • Planning in-person meeting at ACS 2019 in NYC
  • Microsoft and VerizonMedia implementations still in progress

WG Meeting Notes (6/14, 7/12, 8/9)

  • Expanded wg-amp4email GitHub membership
  • Progress on alignment across provider-specific HTML/CSS whitelists and AMP4EMAIL spec
  • Consensus on deprecating proxy assertion tokens to avoid senders potentially only supporting large providers
  • Documented AMP viewer implementation guidelines
  • Consensus on approach for shared sender registration/whitelisting (with long-term goal of not having a sender whitelist at all)
  • Discussions on a new CORS mechanism specifically for AMP4EMAIL (Discussion: CORS for email #7)
  • Discussions on standardizing AMP MIME part expiry, max size, and max number of AMP elements (Discussion: AMP element limits #4)

Focus areas

  • Adapting the AMP4EMAIL spec to avoid potential ecosystem fragmentation

/cc @jasti
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
Type: Status Update
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
1 participant
@dreamofabear