Feedback-ID: ibf914243:Fastmail
Content-Type: multipart/alternative;
 boundary="------------7XJ81tCJJu9iH5NFaMEhc4rA"
Message-ID: <b11354df-1911-4c14-8a8d-18a4d375b8ef@fastmail.com>
Date: Thu, 24 Jul 2025 18:32:58 +0200
MIME-Version: 1.0
User-Agent: Mozilla Thunderbird
To: mailmaint@ietf.org
References: 
 <175311393139.1686140.11721119160895290978@dt-datatracker-7ff4b97469-cdtd8>
 <a865f860-19dc-48b8-bd4c-2fbc655700ef@localhost:3000>
Content-Language: en-US
From: Kenneth Murchison <murch@fastmail.com>
In-Reply-To: <a865f860-19dc-48b8-bd4c-2fbc655700ef@localhost:3000>
Message-ID-Hash: CNT2RMQXI6E5S62G4HHVITAVLLCQZPIQ
CC: Ben Bucksch <ben.bucksch@beonex.com>
Precedence: list
Subject: =?utf-8?q?=5Bmailmaint=5D_Re=3A_I-D_Action=3A_draft-ietf-mailmaint-pacc-00?=
	=?utf-8?q?=2Etxt?=
Archived-At: 
 <https://mailarchive.ietf.org/arch/msg/mailmaint/eqTBIblPLj1JPafOH3ULJQCvFnY>

This is a multi-part message in MIME format.
--------------7XJ81tCJJu9iH5NFaMEhc4rA
Content-Type: text/plain; charset=UTF-8; format=flowed
Content-Transfer-Encoding: 8bit

Ben,

I don't think you incorporated most/all of the feedback on the original 
draft (see mailing list posts on March 12-13, 2025).  Can you review and 
address those comments?

Also, can you:

  * Fix the document name in the boilerplate to be a WG doc?
  * Change the Intended Status to Standards Track?


Additionally, if you don't have time to churn on this frequently prior 
to IETF 124, I know of one or more people that might have some spare 
cycles to help co-author.


WG members,

If you have feedback on this draft, or suggested text, please post them 
to the list.


Cheers,
Ken


On 7/23/25 2:02 AM, Neil Jenkins wrote:
> Hi Ben,
>
> Just confirming, this is just a renamed version of the previous 
> private draft right? I don't think it has been updated with any of the 
> feedback 
> <https://mailarchive.ietf.org/arch/msg/mailmaint/L_0OTTwyFuCRwakXyclb4KqYx0M/> from 
> before.
>
> Related to this, in the previous group discussions we agreed you could 
> discover the authentication methods from the protocols so we should 
> drop this from the autoconfig — that made it simpler, and avoided the 
> possibility of it not matching reality. The exception was OAuth, where 
> you needed to know the issuer. However, I've discovered the recently 
> published RFC9728 <https://www.rfc-editor.org/rfc/rfc9728.html>, and 
> I'm thinking we might be able to do OAuth discovery using this, which 
> would further simplify things. Something to discuss at the meeting 
> this week.
>
> Cheers,
> Neil.

-- 
Kenneth Murchison
Senior Software Developer
Fastmail US LLC
MAILMAINT Co-chair

--------------7XJ81tCJJu9iH5NFaMEhc4rA
Content-Type: text/html; charset=UTF-8
Content-Transfer-Encoding: 8bit

<!DOCTYPE html>
<html>
  <head>
    <meta http-equiv="Content-Type" content="text/html; charset=UTF-8">
  </head>
  <body>
    <p>Ben,</p>
    <p>I don't think you incorporated most/all of the feedback on the
      original draft (see mailing list posts on March 12-13, 2025).  Can
      you review and address those comments?<br>
    </p>
    <p>Also, can you:</p>
    <ul>
      <li>Fix the document name in the boilerplate to be a WG doc?</li>
      <li>Change the Intended Status to Standards Track?</li>
    </ul>
    <p><br>
    </p>
    <p>Additionally, if you don't have time to churn on this frequently
      prior to IETF 124, I know of one or more people that might have
      some spare cycles to help co-author.</p>
    <p><br>
    </p>
    <p>WG members,</p>
    <p>If you have feedback on this draft, or suggested text, please
      post them to the list.</p>
    <p><br>
    </p>
    <p>Cheers,<br>
      Ken<br>
    </p>
    <p><br>
    </p>
    <div class="moz-cite-prefix">On 7/23/25 2:02 AM, Neil Jenkins wrote:<br>
    </div>
    <blockquote type="cite"
      cite="mid:a865f860-19dc-48b8-bd4c-2fbc655700ef@localhost:3000">
      <meta http-equiv="content-type" content="text/html; charset=UTF-8">
      <title></title>
      <div>Hi Ben,</div>
      <div><br>
      </div>
      <div>Just confirming, this is just a renamed version of the
        previous private draft right? I don't think it has been updated
        with any of <a
href="https://mailarchive.ietf.org/arch/msg/mailmaint/L_0OTTwyFuCRwakXyclb4KqYx0M/"
          moz-do-not-send="true">the feedback</a> from before.</div>
      <div><br>
      </div>
      <div>Related to this, in the previous group discussions we agreed
        you could discover the authentication methods from the protocols
        so we should drop this from the autoconfig — that made it
        simpler, and avoided the possibility of it not matching reality.
        The exception was OAuth, where you needed to know the issuer.
        However, I've discovered the recently published <a
          href="https://www.rfc-editor.org/rfc/rfc9728.html"
          moz-do-not-send="true">RFC9728</a>, and I'm thinking we might
        be able to do OAuth discovery using this, which would further
        simplify things. Something to discuss at the meeting this week.</div>
      <div><br>
      </div>
      <div>Cheers,</div>
      <div id="sig64588216">
        <div class="signature">Neil.<br>
        </div>
      </div>
    </blockquote>
    <pre class="moz-signature" cols="72">-- 
Kenneth Murchison
Senior Software Developer
Fastmail US LLC
MAILMAINT Co-chair
</pre>
  </body>
</html>

--------------7XJ81tCJJu9iH5NFaMEhc4rA--