Re: [Forces-protocol] Feedback: Section 6.4

----- Original Message -----
From: "Jamal Hadi Salim" <hadi@znyx.com>
> On Sun, 2004-10-24 at 23:44, Wang,Weiming wrote:
> > ----- Original Message -----
> > From: "Jamal Hadi Salim" <hadi@znyx.com>
>
> Lets take an example of noop, since the xml for that is there and its a
> very simple example.
>
> The class NOOP is 5. owned by IANA.
> It has a simple table called datatable whose ID is 6.
>Defined at xml creation.
[Weiming] Let me call this ID an 'attribute ID'. Also in your XML, you'v called
the table an attribute, right?

> To point to first entry of datatable: 6,1
[Weiming]I'm glad to see this. It also means you'v agreed that the 'path'
includes one subsection  which is for attribute ID, right? Now the problem is,
how many bits are you going to use for such ID, 8 bits or 16bits? I suppose you
will not use a variable size for this ID. Whether the ID length is variable or
not, we  then can both reasonably think the 'path' as composed of follows:
                Path : = AttributeID  Index
 that really matches my idea. I also think  it mathces your idea too as
presented in your example here as 6.1, 6.2.3, etc.

To summarize, what I proposed actually include two thoughts:
a) Attribute ID is necessary;
b) the attribute ID should appear in the protocol layer. The followed Index can
be included in Data field, becaue not all attributes need Index (they may only
have one entry).

I'm not sure if above helps or not.

Cheers,
Weiming

> to point to foo1 within entry 2 of datatable: 6,2,3
> to point to foo2 of entry 3 of datatable: 6,3,4
>
> I hope this clears it. I have attached two docs i worked on to
> clarify this.
>
> As i said earlier, the path issue is resolved but not the data packing.
> Of course if you disagree we could continue that discussion.
> As you will notice in these docs, the text clearly states that the
> data packing is not resolved.
>
> cheers,
> jamal
>

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