Re: [Nea] PA-TNC draft

[kaushik <kaushik at cisco.com>]

Hi Randy,

The editors have been debating the value of these data types given that it
will be difficult to define a complete set of primitives. We have decided to
remove Section 3.6 in the next revision of the PA-TNC ID.

It is safe to ignore these data/field types.

Regards,
 kaushik


On 8/13/09 2:52 PM, "Randy Turner" <rturner at amalfisystems.com> wrote:

> 
> Hi List,
> 
> I know this message is a little late to the party, so take it as just
> an informational comment/question...
> 
> In the PA-TNC draft (current version), a set of primitive data types
> are defined near the front of the document, however these data types are
> never referenced again during the definition of the attribute values.
> For instance, OctetArray, IPv4Address, IPv6Address, VersionNum, and
> TimeString
> are never used within the document.  They are defined, but never used
> (in compiler speak :) It looks like the someone changed their mind
> later in the document
> and instead of referencing existing data types, each attribute
> definition and encoding was completely specified in each attribute
> definition section, without any references to data types.
> 
> I'm assuming it's safe to ignore data types in an implementation and
> just encode exactly what is specified in each attribute definition and
> accompanying
> diagram.  Is this is safe assumption?
> 
> Thanks!
> Randy
> 
> 
> _______________________________________________
> Nea mailing list
> Nea at ietf.org
> https://www.ietf.org/mailman/listinfo/nea