RE: [Forces-protocol] Feedback: Section 6.4

Jamal, Weiming,

I finally got the chance to read some of these emails...sorry for not
responding earlier. In general, we will need the concept of PATH atleast
for Query messages (GET), but I don't believe from any of the emails
that I have read so far that there was any concensus on what this would
look like. Jamal has a reasonable proposal which needs more discussion
and refinement.

Some specific comments on Jamal's proposal so far...

Where is the Table ID ? Is this part of the path IDs?
I don't believe we need any Flags in the path, this is similar to the
comment that Joel had as well.
Also, for Config msgs, I think the path can be part of the data itself,
but lets discuss this further...cause I am not sure if you guys agree
with this,

Talk to you soon,

regards
Hormuzd

-----Original Message-----
From: Jamal Hadi Salim [mailto:hadi@znyx.com] 
Sent: Tuesday, October 26, 2004 3:59 AM
To: Wang,Weiming
Cc: Joel M. Halpern; Khosravi, Hormuzd M; ram.gopal@nokia.com;
forces-protocol@ietf.org; avri@psg.com; Ligang Dong; Robert Haas
Subject: Re: [Forces-protocol] Feedback: Section 6.4

On Tue, 2004-10-26 at 00:01, Wang,Weiming wrote:

> I have no doubt to agree with this. Just need to calrify that a path
is more
> than 32 bits long, or there will be not enough bits.
> 

Aha! I think i see where the misunderstanding is;->
Weiming sees either a path like 6 or 1,2,3,4 as represented by _one_
_fixed_ sized element. In which case you have to find a way to pack both
representations into that fixed size element.

The suggested "path" representation is in fact _variable_.
>From the notes i sent earlier to you, the suggestion is:

----
 A possible path-data layout. 
----------------------------

OPER_TLV : = <PATH-DATA>
PATH-DATA := flags IDcount <IDs> [BLOCK_OR_KEY_NOTATION] [DATA]
The operational TLV contains an opcode in the T part. Its V
contains the PATH-DATA.
Opcodes discussed so far:
* SET (create, modify or both depending on PATH-DATA flags}
* DEL (remove an existing entity specified by PATH-DATA }
* GET (Access a entity specified in PATH-DATA }
* EV_S (subscribe to an event defined in PATH-DATA }
* EV_U (unsubscribe to an event defined in PATH-DATA }
-> IDs := a series of 32bit IDs (whose size is given by IDcount)
defining the path.
-> flags are used to further refine the operation to be applied
on the ID_TLV.
-> BLOCK_OR_KEY_NOTATION := optional different BLOCK or KEY extension
defined in section 4.2 and 4.3 of [1]
-> DATA : = Optional variable sized data dependent on PATH
and applied operations (eg GET will not have DATA).

-------

Well read the rest of the doc; and for completion the notes posted by
Steve/Zsolt.

cheers,
jamal

_______________________________________________
Forces-protocol mailing list
Forces-protocol@ietf.org
https://www1.ietf.org/mailman/listinfo/forces-protocol