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

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
> > >
> > >
> > >