Re: [hybi] Ben Campbell's No Objection on draft-ietf-hybi-permessage-compression-24: (with COMMENT)

[Takeshi Yoshino <[e-mail]>]

Hi Ben,

Thanks for review.

On Fri, Aug 21, 2015 at 7:32 AM, Ben Campbell <[e-mail]> wrote:

> [...]
>
>
>>
>> -- 6.1, Numbered list entry "2", third bullet (and several similar
>>> assertions)
>>>
>>> Do I understand correctly that the PMCE needs to know if the next
>>> extension wants frames, in order to determine whether to build them? How
>>> would it know that?
>>>
>>>
>> It's about gluing implementation of PMCE and one of the next extension. If
>> the next extension expects a frame for its input, we need to build a frame
>> to match the interface. RFC 6455 didn't defined detailed interface between
>> extensions, so we cannot write negotiation algorithm that work well with
>> every extension (including the case where they cannot connect with each
>> other). All I could do is listing two basic and known interfaces and
>> explain how to glue PMCE with them.
>>
>> - The _Send a WebSocket Message_ algorithm and _A WebSocket Message Has
>> Been Received_ are defined in it. So, I explained how to glue PMCE with
>> them.
>> - And mentioned another simplest case other extensions may adopt
>> (expecting
>> a sequence WebSocket frames for input/output), too.
>>
>
> I think I see--you know the next extension needs frames because your
> interface to it uses frames? If so, then I'm okay with the text.


Yes. At the spec level, the interface between PMCE and the next extension
is determined to use frames, and then at implementation level the next
extension code/module/etc. would need frames.


>
>
>> -- 3, third paragraph: "An extension in use next to extension"
>>>
>>> The construction "next to" usually connotes adjacency, not order. I
>>> suggest "The next extension in use" (without the "to").
>>>
>>>
>>> I see. But how should I connect the revised phrase with "extension X"?
>> The
>> next extension in use "of" extension X?
>>
>>
> How about "The next extension after extension X"?
>
> [...]
>

Thanks for suggestion. Replaced and published
https://tools.ietf.org/html/draft-ietf-hybi-permessage-compression-28