Common Open Policy Service (COPS) Protocol per [RFC2748]

The Client-type identifies the policy client application to which a
message refers. Client-type values within the range 0x0001-0x3FFF
are reserved Specification Required status as defined in [RFC2434].
These values MUST be registered with IANA and their behavior and
applicability MUST be described in a COPS extension document.

Client-type Values (0x0001-0x3FFF)

Value	Description					Reference
-----   ----------------------                          ---------

0x01	COPS Usage for RSVP				[RFC2749]


Client-type values in the range 0x4000 - 0x7FFF be IANA-re reserved for
Private Use as defined in [RFC2434]. These Client-types
are not tracked by IANA and are not to be used in standards or
general-release products, as their uniqueness cannot be assured.

Client-type values in the range 0x8000 - 0xFFFF are First Come
First Served as defined in [IANA-CONSIDERATIONS]. These Client-types are
tracked by IANA but do not require published documents describing
their use. IANA merely assures their uniqueness.

Client-Type Values (0x8000-0xFFFF)
------------------

Value   Description                                     Reference
-----   ----------------------                          --------- 
0x8001  IP Highway					[Herzog]
0x8002  IP Highway					[Herzog]
0x8003  IP Highway					[Herzog]
0x8004  IP Highway					[Herzog]
0x8005  Fujitsu Application Server Software Division    [Hanada]


Objects in the COPS Protocol are identified by their C-Num and
C-Type values. IETF Consensus as identified in [RFC2434] is
required to introduce new values for these numbers and, therefore,
new objects into the base COPS protocol.

Additional Context Object R-Types, Reason-Codes, Report-Types,
Decision Object Command-Codes/Flags, and Error-Codes MAY be defined
for use with future Client-types, but such additions require IETF
Consensus as defined in [RFC2434].

Context Object M-Types, Reason Sub-Codes, and Error Sub-codes MAY
defined relative to a particular Client-type following the same
IANA considerations as their respective Client-type.


REFERENCES
----------

[RFC2434]  Alvestrand, H. and T. Narten, "Guidelines for Writing
           an IANA Considerations Section in RFCs", BCP 26,
           RFC 2434, October 1998.

[RFC2748]  Durham, D., J. Boyle, R. Cohen, S. Herzog, R. Rajan, 
           A. Sastry, "The COPS (Common Open Policy Service)
           Protocol", RFC 2748, January 2000.

[RFC2749]  Boyle, J., Cohen, R., Durham, D., Herzog, S., Raja, R.
           and A. Sastry, "COPS Usage for RSVP", RFC 2749,
           January 2000.

PEOPLE
------

[Hanada]  Tetsuharu Hanada, <hanada@paso.fujitsu.co.jp>, 
          December 2000.

[Herzog]  Shai Herzog, <herzog@iphighway.com>, July 1999, 
          November 1999. 

(created 11/00)

[]