[Asap] Re: Mike Bishop's No Objection on draft-ietf-asap-sip-auto-peer-36: (with COMMENT)

[Sreekanth Narayanan <[e-mail]>]

Hi Mike,

I've updated the latest version with changes suggested below.
https://author-tools.ietf.org/diff?doc_1=draft-ietf-asap-sip-auto-peer-36&doc_2=draft-ietf-asap-sip-auto-peer-37

Thanks
Sreekanth


On Monday, December 15th, 2025 at 8:20 AM, Mike Bishop via Datatracker <[e-mail]> wrote:

> Mike Bishop has entered the following ballot position for
> draft-ietf-asap-sip-auto-peer-36: No Objection
> 
> When responding, please keep the subject line intact and reply to all
> email addresses included in the To and CC lines. (Feel free to cut this
> introductory paragraph, however.)
> 
> 
> Please refer to https://www.ietf.org/about/groups/iesg/statements/handling-ballot-positions/
> for more information about how to handle DISCUSS and COMMENT positions.
> 
> 
> The document, along with other ballot positions, can be found here:
> https://datatracker.ietf.org/doc/draft-ietf-asap-sip-auto-peer/
> 
> 
> 
> ----------------------------------------------------------------------
> COMMENT:
> ----------------------------------------------------------------------
> 
> Thanks for addressing my previous DISCUSS and COMMENTs. A few notes left from
> the diff, but nothing blocking, so I'm updating my ballot.
> 
> In the third paragraph of 4.6, "in such statuses" => "in such responses". HTTP
> 
> responses contain a status code, (header and potentially trailer) fields, and a
> body.
> 
> Throughout, change most occurrences of "HTTPS" to "HTTP" except when talking
> specifically about the "https" URI scheme (which should be lower-cased).
> Compare to https://www.rfc-editor.org/rfc/rfc9110.html#https.uri for usage. I
> see that you've made changes in this direction, but now lower-case some
> instances where you're talking about the protocol rather than the scheme. The
> RFC Editor can probably help sort this if needed.
> 
> TLS is required, but no particular version? Why not 1.2 or later, or 1.3?
> 
> Consider using the line-wrapping format described in RFC8792.
> 
> 
> 
> --
> Asap mailing list -- [e-mail]
> To unsubscribe send an email to [e-mail]