Re: [Nea] NEA extensibility points

[Randy Turner <rturner at amalfisystems.com>]

Thanks for the reply Steve....

So IANA will keep a registry of SMI-specific attributes and PA- 
subtypes for SMI values OTHER than IETF (SMI=0)?

Also, does the expert review process only occur if we're registering  
additional values as standard IETF types(SMI=0), or
does the expert review process occur regardless of which SMI we're  
registering under?

Thanks!!
Randy


On Aug 5, 2009, at 10:55 AM, Stephen Hanna wrote:

> The PA Subtype registry is created in the PB-TNC spec.
> Look there for information about how that registry
> will be managed.
>
> To answer your question, any organization can get an
> SMI Private Enterprise Number (PEN) from IANA and then
> create new PA Subtypes of any kind and for any purpose
> that will be used with that organization's SMI PEN.
>
> For example, my employer Juniper has an SMI PEN of 2636.
> We could define a PA Subtype for Power Supply Firmware
> (or something else that we came up with). Let's say that
> we decided to make that PA Subtype 27, when used with
> our SMI PEN of 2636. No problem. Now we can send around
> PB-PA messages with that PA Subtype and SMI PEN.
>
> An organization that defines a new PA Subtype is not
> required to register their PA Subtype with IANA. They
> can keep it to themselves. But if they want to register
> their PA Subtype values with IANA, they can do so. They
> just need to send a spec for their PA Subtype value to
> IANA which will trigger the Expert Review process
> described in sectin 6.1 of PB-TNC. Of course, this
> process won't be ready to go until PB-TNC becomes
> an RFC (real soon now, I hope! ;-).
>
> I hope that helps.
>
> Thanks,
>
> Steve
>
> > -----Original Message-----
> > From: nea-bounces at ietf.org [mailto:nea-bounces at ietf.org] On
> > Behalf Of Randy Turner
> > Sent: Wednesday, August 05, 2009 12:48 PM
> > To: NEA
> > Subject: [Nea] NEA extensibility points
> >
> > Hi List,
> >
> > The PA-TNC document is clear on how attributes types are relative to
> > the vendor-ID value used in a message.
> >
> > The PA-TNC document also mentions a registry for PA-subtypes.
> > What I
> > wanted to make sure is that other organizations could
> > establish an SMI
> > value and register NEW PA subtypes that are relative to the
> > organization-specific SMI.
> >
> > Are there any limitations or constraints on creating new PA subtypes
> > under a specific SMI ?
> >
> > Thanks!
> > Randy
> >
> >
> > _______________________________________________
> > Nea mailing list
> > Nea at ietf.org
> > https://www.ietf.org/mailman/listinfo/nea