Re: BCP56bis - remaining work

Thanks for the suggestion; I agree the abstract needs work. However, I did something slightly different; I stole the last sentence of 1.1, since you liked it :)

Now:

> Applications often use HTTP as a substrate to create HTTP-based APIs. This document specifies best practices for writing specifications that use HTTP to define new application protocols. It is written primarily to guide IETF efforts to define application protocols using HTTP for deployment on the Internet, but might be applicable in other situations.

Cheers,


> On 21 Apr 2021, at 6:20 pm, Poul-Henning Kamp <phk@phk.freebsd.dk> wrote:
> 
> --------
> Mark Nottingham writes:
> 
>> [However,]
>> this BCP is for IETF standards-based HTTP APIs, not all HTTP APIs or all 
>> uses of HTTP. Given that the IETF is focused on internetworking, the 
>> examples of localhost APIs don't seem very applicable here.
> 
> In the last para before 1.1 that is said quite clearly, but the
> abstract feels a bit wishy-washy.
> 
> Proposed abstract:
> 
>   HTTP is often used as a substrate for other application protocols to
>   create HTTP-based APIs.  This document specifies best practices for
>   writing specifications that use HTTP to define new application
>   protocols for deployment on the Internet, (e.g., in standards efforts).
> 
> We should not need to spell out that "other situations" (as the
> para before 1.1 calls them) would be smart to use them as well.
> 
> -- 
> Poul-Henning Kamp       | UNIX since Zilog Zeus 3.20
> phk@FreeBSD.ORG         | TCP/IP since RFC 956
> FreeBSD committer       | BSD since 4.3-tahoe    
> Never attribute to malice what can adequately be explained by incompetence.

--
Mark Nottingham   https://www.mnot.net/

Received on Thursday, 22 April 2021 06:36:09 UTC