I'm going to take silence as assent: i.e. we will specify
a default maximum message size of 2048, and leave the question
of how it can be exceeded to be a negotiable property of individual
objectives.
Regards
Brian
On 20/10/2016 15:34, Brian E Carpenter wrote:
> On one point:
>
>> *could* we
On one point:
> *could* we make the maximum objective (assuming intents are directly in an
> objective) size itself be a synchronizable parameter?
We could even make it negotiable, since GRASP supports negotiation :-).
But I think we'd better start off with a hard limit so that we don't
encounter
On 19/10/2016 21:41, Michael Behringer (mbehring) wrote:
>> -Original Message-
>> From: Anima [mailto:anima-boun...@ietf.org] On Behalf Of Brian E
>> Carpenter
>> Sent: 18 October 2016 22:06
>> To: Anima WG
>> Subject: [Anima] GRASP issue 58: Max
Michael Behringer (mbehring) wrote:
> My view: - We use GRASP to signal which Intent version we have, and
> where the latest version can be fetched from, and with which method /
> protocol. - We use that protocol to actually get the Intent file.
I agree that this is a better way to
Brian E Carpenter wrote:
> BC: Me too. I coded my prototype with recvfrom limited to 2048 bytes,
> but we probably need to specify something. On the other hand, Michael B
> wants to send infinitely long Intents, I think.
libcbor nicely responds to an incomplete message with CBOR_ERR_N
> -Original Message-
> From: Anima [mailto:anima-boun...@ietf.org] On Behalf Of Brian E
> Carpenter
> Sent: 18 October 2016 22:06
> To: Anima WG
> Subject: [Anima] GRASP issue 58: Maximum message size?
>
> 58: Maximum message size?
>
> MR: I'm a
58: Maximum message size?
MR: I'm also a bit concerned that we have no statement about maximum message
size.
BC: Me too. I coded my prototype with recvfrom limited to 2048 bytes, but we
probably
need to specify something. On the other hand, Michael B wants to send
infinitely long
Intents, I th
