Re: [Anima] [Cbor] GRASP packet header extensions (CBOR question)

2022-08-19 Thread Brian E Carpenter
On 20-Aug-22 09:15, Carsten Bormann wrote: On 2022-08-19, at 23:05, Brian E Carpenter wrote: EXTENSION_TYPE = 0..255 There is no reason to limit this to 255. ➔ EXTENSION_TYPE = uint (Do you plan to creat a registry for these? The 'extension_type' terminology is confusing, because these wou

Re: [Anima] [Cbor] GRASP packet header extensions (CBOR question)

2022-08-19 Thread Carsten Bormann
On 2022-08-19, at 23:05, Brian E Carpenter wrote: > >>> EXTENSION_TYPE = 0..255 >> There is no reason to limit this to 255. >> ➔ EXTENSION_TYPE = uint >> (Do you plan to creat a registry for these? > > The 'extension_type' terminology is confusing, because these would > be new GRASP options, and

[Anima] Extending GRASP messages and signing GRASP multicasts

2022-08-19 Thread Brian E Carpenter
Hi ANIMA, Some background on the new discussion: A few of us have been discussing the need to cryptographically sign GRASP multicasts (especially M_FLOOD messages) and this has shown up a gap in RFC8990 (the GRASP spec). We're currently thinking that this topic will need a draft (or maybe two dr

Re: [Anima] [Cbor] GRASP packet header extensions (CBOR question)

2022-08-19 Thread Brian E Carpenter
On 20-Aug-22 06:56, Carsten Bormann wrote: In GRASP (RFC8990] we define the GRASP message structure as follows: message-structure = [MESSAGE_TYPE, session-id, ?initiator, *grasp-option] MESSAGE_TYPE = 0..255 session-id = 0..4294967295 ; up to 32 bits grasp-option = any Then we've defined a few

Re: [Anima] [Cbor] GRASP packet header extensions (CBOR question)

2022-08-19 Thread Toerless Eckert
On Fri, Aug 19, 2022 at 08:56:35PM +0200, Carsten Bormann wrote: > > EXTENSION_TYPE = 0..255 > > There is no reason to limit this to 255. Agreed. I just copied from MESSAGE_TYPE in GRASP. > ➔ EXTENSION_TYPE = uint > > (Do you plan to creat a registry for these? Probably we should. Typical subd

Re: [Anima] [Cbor] GRASP packet header extensions (CBOR question)

2022-08-19 Thread Carsten Bormann
> In GRASP (RFC8990] we define the GRASP message structure as follows: > > message-structure = [MESSAGE_TYPE, session-id, ?initiator, *grasp-option] > > MESSAGE_TYPE = 0..255 > session-id = 0..4294967295 ; up to 32 bits > grasp-option = any > > Then we've defined a few MESSAGE_TYPEs of which the

[Anima] remote attestation Epoch ID distribution in IPv6 and GRASP

2022-08-19 Thread Michael Richardson
As explained at: https://www.ietf.org/archive/id/draft-ietf-rats-reference-interaction-models-05.html#name-uni-directional-remote-atte and also referenced at: https://www.ietf.org/archive/id/draft-ietf-rats-architecture-21.html#name-example-3-epoch-id-based-pa (which has a cool SVG diagra

[Anima] GRASP packet header extensions (CBOR question)

2022-08-19 Thread Toerless Eckert
[ Sorry for cross-post but given how this is about ANIMA GRASP, a CBOR protocol, i think its the best/fastest way to converge. ] In GRASP (RFC8990] we define the GRASP message structure as follows: message-structure = [MESSAGE_TYPE, session-id, ?initiator, *grasp-option] MESSAGE_TYPE = 0..255