KEYDATA was Re: ipv6 was Re: LC model draft draft-ietf-forces-model-07.txt

---- Original Message -----
From: "Joel M. Halpern" <[email protected]>
To: <[email protected]>
Sent: Friday, October 27, 2006 1:27 AM
Subject: Re: ipv6 was Re: LC model draft draft-ietf-forces-model-07.txt


> KEYDATA can be anything.  It can be a simple integer.  It can be a
> string.  It can be an entire struct.
>
> Basically, when we decided to allow content based element selection,
> we concluded that we could not restrict the type of content that
> served as the key.
>

Obviously, I had not picked this up.  I suggest adding something to that effect
to 4.5.3. What I read, and did not - still do not - understand, was
  "Arrays MUST only be subscripted by integers, and will be presumed to
      start with index 0.

      In addition to their subscripts, arrays may be declared to have
      content keys."

I expect an array to have an index, of one of more elements, and do not
understand the difference here between an index and a content key.  Content key
has overtones of a CAM for me, but obviously there is more to it than that.

Issue 99?

Tom Petch

> Yours,
> Joel M. Halpern
>
> At 07:47 AM 10/26/2006, tom.petch wrote:
> >So is there any constraint on what type of data a KEYDATA can be?  I was
> >assuming it would be numeric of fixed length but you are suggesting it can be
> >(almost) anything.  I note that the examples I see in -protocol are type u32.
> >
> >Tom Petch
> >
> >----- Original Message -----
> >From: "Joel M. Halpern" <[email protected]>
> >To: <[email protected]>
> >Sent: Thursday, October 26, 2006 1:26 PM
> >Subject: Re: ipv6 was Re: LC model draft draft-ietf-forces-model-07.txt
> >
> > > IP addresses (like MAC addresses) should use the byte[N] construct to
> > > represent the string of bytes for the address.  (A variable length
> > > address would use octetstring[N].)  So IPv4 addresses use byte[4],
> > > and IPv6 addresses use byte[16].
> > >
> > > Yours,
> > > Joel M. Halpern
> > >
> > > At 03:22 PM 10/25/2006, tom.petch wrote:
> > > >How are ipv6 addresses represented in the data model?  Should there be an
> > > >int128??
> > > >
> > > >Tom Petch
> > > >
> > > >----- Original Message -----
> > > >From: "Patrick Droz" <[email protected]>
> > > >To: <[email protected]>
> > > >Sent: Friday, October 13, 2006 10:36 AM
> > > >Subject: LC model draft draft-ietf-forces-model-07.txt
> > > >
> > > >
> > > > > I would like to issue last call on the model draft. As this is
> > > > > a fairly large document the LC will last for 3 weeks and will
> > > > > therefore end just before the next IETF. It is draft:
> > > > > draft-ietf-forces-model-07.txt
> > > > > and can be found at:
> > > > > http://www.ietf.org/internet-drafts/draft-ietf-forces-model-07.txt
> > > > >
> > > > > A number of people have indicated that if the document is in
> > > > > LC they would thoroughly review the document. I hope people will
> > > > > stick to their promises.
> > > > >
> > > > > Regards,
> > > > > Patrick
> > > > >
> > > > >
> > > > >