[JMAP] Re: [Technical Errata Reported] RFC9749 (9055)

Joris Baum <post@jorisbaum.de> Fri, 25 September 2026 19:52 UTC

Content-Type: multipart/alternative; boundary="------------tzRlhDUy3YIYZyB3cQDYEKIc"
Message-ID: <0b81413c-582a-421c-981b-cb248616f327@jorisbaum.de>
Date: Fri, 25 Sep 2026 21:52:17 +0200
MIME-Version: 1.0
User-Agent: Mozilla Thunderbird
To: rfc-editor@rfc-editor.org, andy@hxr.us, brong@fastmailteam.com, daniel@gultsch.de, eckelcu@cisco.com, superuser@gmail.com
References: <178577520829.15.3718613074910206970@rfc-editor.org>
Content-Language: en-US
From: Joris Baum <post@jorisbaum.de>
Autocrypt: addr=post@jorisbaum.de; keydata= xjMEZnHYaBYJKwYBBAHaRw8BAQdAVG1xthxiwZhKmH/4PBfHy2awKJj7mYhHzyy47jTJ1BjN HkpvcmlzIEJhdW0gPHBvc3RAam9yaXNiYXVtLmRlPsKPBBMWCAA3FiEEd4vWGmv5znUuPCvL HzWTb0znH/sFAmZx2GgFCQWjmoACGwMECwkIBwUVCAkKCwUWAgMBAAAKCRAfNZNvTOcf+56/ AQCdcWbH0ULLT2OCRcVqjaNfVpo/WHz+jt1nh3XOY6ldagD+Pa25PEc8Nyjavqgnr7kIyhEQ Qu3fTQ5WYmmX2HjTbwLOOARmcdhoEgorBgEEAZdVAQUBAQdAzNq+w6+NI2L1VFuc88DkwYWg 3nH+FvPXkL4b6gPM9x0DAQgHwn4EGBYIACYWIQR3i9Yaa/nOdS48K8sfNZNvTOcf+wUCZnHY aAUJBaOagAIbDAAKCRAfNZNvTOcf+6LfAQC5BKPO2aS3FONszMsivIwQF3sJJJc4OkAQ4atz c+lmOwD+NdOh4Vcou1gnE8mI+wDS1sqk41lwOj3yk6up0fdIyQE=
In-Reply-To: <178577520829.15.3718613074910206970@rfc-editor.org>
Message-ID-Hash: ATZGVHVS37B5LFBSVJ5R6454NAA45VWI
CC: neilj@fastmailteam.com, jmap@ietf.org
Precedence: list
Subject: [JMAP] Re: [Technical Errata Reported] RFC9749 (9055)
Archived-At: <https://mailarchive.ietf.org/arch/msg/jmap/da4FA8EDsNKbmb8OiXf8Y4li2Bg>

Looks good to me. I am in favor of verifying.

Regards,

Joris


On 8/3/26 6:40 PM, rfc-editor@rfc-editor.org wrote:
> The following errata report has been submitted for RFC9749,
> "Use of Voluntary Application Server Identification (VAPID) in JSON Meta Application Protocol (JMAP) Web Push"
>
> --------------------------------------
> You may review the report below and at:
> https://errata.rfc-editor.org/eid9055/
>
> --------------------------------------
> Type: Technical
> Reported by: Neil Jenkins<neilj@fastmailteam.com>
>
> Section 5 says:
>
> Original Text
> -------------
> When destroying push subscriptions that include the data type PushSubscription,
> the server MAY issue one final StateChange push notification using the old URL and
> application server key to notify the client of changes to the PushSubscription data type.
> This prompts the client to make a PushSubscription/changes method call. The response
> to this call will contain an updated sessionState, which refers to a session object that
> contains the new VAPID key.
>
> Corrected Text
> --------------
> (Delete the paragraph.)
>
> Notes
> -----
> The PushSubscription object is not associated with an account id, and so cannot appear in
> the StateChange object as specified in RFC8620. Additionally, there is no
> "PushSubscription/changes" method call defined in RFC8620 — only "PushSubscription/get"
> and "PushSubscription/set".
>
> Suggested fix is to remove this paragraph. There is no good way of doing this right now,
> and it was a MAY anyway, not essential. Session state changes are likely to be picked up
> very quickly by a client anyway as they will get it as soon as they make any API call.
>
> Instructions:
> -------------
> This erratum is currently posted as "Reported". Please
> use "Reply All" to discuss whether it should be verified or
> rejected. When a decision is reached, the verifying party
> will log in to change the status and edit the report, if necessary.
>
> --------------------------------------
> RFC9749 (draft-ietf-jmap-webpush-vapid)
> --------------------------------------
> Title               : Use of Voluntary Application Server Identification (VAPID) in JSON Meta Application Protocol (JMAP) Web Push
> Publication Date    : March 2025
> Author(s)           : D. Gultsch
> Category            : Proposed Standard
> Source              : jmap (art)
> Stream              : IETF
> Verifying Party     : IESG
>
> _______________________________________________
> JMAP mailing list --jmap@ietf.org
> To unsubscribe send an email tojmap-leave@ietf.org

[JMAP] [Technical Errata Reported] RFC9749 (9055) rfc-editor
[JMAP] Re: [Technical Errata Reported] RFC9749 (9… Joris Baum