Re: [core] Review of draft-bormann-core-responses-01

[Carsten Bormann <[e-mail]>]

Hi Marco,

thank you for this detailed review!
I think we’ll need some time to digest this.

I have started pushing in the smaller observations (and some that derive from it) into https://github.com/core-wg/core-responses

I have one terminology issue that probably just needs one new term:

> [Section 2.2]
> 
> * "One way to do that is to exchange a "phantom request", which is a request that client and server will agree to have sent and received, respectively, without it actually being sent between those endpoints."
> 
>    Basically, the "phantom request" referred here (and used in -core-observe-multicast-notifications) is an example of "configured request" as defined in this document. Correct? If so, it's worth mentioning.
>    
>    It is also consistent with the first paragraph of Section 4.2.

I’m no longer sure that using “configured” for any kind of non-traditional transmittal of a request works so well.
Maybe we want to have another word that takes the current definition of “configured” (i.e., non-traditionally transmitted) and use the word instead for cases where the non-traditionally transmitted request actually has some persistence in the configuration of the server.

Another potential improvement to terminology:

> [Section 2]
[…]
> * "Some established responses (observations defined in [RFC7641], and multicast responses in [I-D.ietf-core-groupcomm-bis]) match ..."
> 
>    I think you mean "and responses to multicast requests in [I-D.ietf-core-groupcomm-bis]) match ..." . Multicast responses are not part of that document and are rather used in -core-observe-multicast-notifications.

This indeed has a quick fix:
-and multicast responses in {{?I-D.ietf-core-groupcomm-bis}})
+and responses to multicast requests in {{?I-D.ietf-core-groupcomm-bis}})

We probably need to be a bit more conspicuous in distinguishing “multicast response” from “response to a multicast request”, maybe we need to create a more specific term for multicast response.

Looking forward to discussing this further this afternoon…

Grüße, Carsten