[Isis-wg] Vendor proprietary LSP option codes

[Rijsman, Bruno (Bruno)]

We are considering to use a proprietary LSP option for one of our
applications and we a considering which LSP option code we could use for
this application. We want to pick an option code which guarantueed not to
conflict with any existing or future option codes used in integrated IS-IS
and proprietary option codes of other vendors.

It seems to me that 
(a) there is currently no official way for allocating unique option codes
(b) option codes are a scarce resource (only 255 codes available)

To solve this, it would be a good idea to:
(a) allocate a single option code for "vendor proprietary options"
(b) to require that the first three bytes in such "vendor proprietary
options" must be an ethernet OUI allocated to that vendor
(c) to strongly recommend that "vendor proprietary options" be small in size
and do not change frequently (to avoid impact on "innocent" nodes).
(d) to require that "vendor proprietary options" which are not recognized
must be silently ignored but propagated anyway (actually, this is already
part of ISO 10589).

If such an option already exists, could someone point me to it. If it
doesn't exist yet, what would be the proper process for me to standardize
such an option?

PS - It might be relevant to know that for this particular application we
are using IS-IS in an OSI CLNP network (the OSI network is used for
management of SDH/SONET network elements).

Bruno Rijsman
Lucent Technologies - Optical Networking Group