
Integrated Services Parameters 

(last updated 2002-04-09)

Registries included below:
- Service Names
- Parameter Names
- Compression Hints

Note:
The namespace is a two-level hierarchy: <service_name>.<parameter_name>.
Each of these elements is a integer numerical quantity.


Registry Name: Service Names
Reference: [RFC2216]
Range        Registration Procedures         Notes
-----------  ------------------------------  ---------------------------------   
2-127        RFC
128-254      Experimental use                Service and Data Element Naming

Note:
<Service Name> is an integer in the range 1 to 254. The number space
is broken into three regions.  2-254 will be allocated to individual
QoS control services.

Registry:
Value     Description                                   Reference
--------  --------------------------------------------  ---------
0         (Unused to allow the direct mapping of        [RFC2216]
          parameter names to MIB object names)
1         Generic                                       [RFC2215]
2         Guaranteed service                            [RFC2212]
3-4       Unassigned
5         Controlled-load service                       [RFC2211]
6-127     Unassigned           
128-254   Experimental or private services              [RFC2216]
255       Reserved for future expansion                 [RFC2216]


Registry Name: Parameter Names   
Reference: [RFC2216]
Range        Registration Procedures                      
-----------  -----------------------------------------------------------
1-127        Parameters defined in [RFC2215] 
128-254      Parameters defined by author of service specification 
             document (Service and Data Element Naming)
Note:
<Parameter_name> is a number in the range 1 to 254, allocated on a
per-service basis. 

Registry:
Value     Description                                   Reference
--------  --------------------------------------------  ---------
0         (Unused to allow the direct mapping of        [RFC2216]
          parameter names to MIB object names)   
1         NON-IS_HOP flag (local)                       [RFC2215]
2         NON-IS_HOP flag (composed)                    [RFC2215]
3         NUMBER_OF_IS_HOPS (local)                     [RFC2215]
4         NUMBER_OF_IS_HOPS (composed)                  [RFC2215]
5         AVAILABLE_PATH_BANDWIDTH (local)              [RFC2215]
6         AVAILABLE_PATH_BANDWIDTH (composed)           [RFC2215]
7         MINIMUM_PATH_LATENCY (local)                  [RFC2215]
8         MINIMUM_PATH_LATENCY (composed)               [RFC2215]
9         PATH_MTU (local)                              [RFC2215]
10        PATH_MTU (composed)                           [RFC2215]
11-125    Reserved for assignment to parameters with a  [RFC2215]
          common, shared meaning across all services    
126       Compression Hint                              [RFC3006]
127       TOKEN_BUCKET_TSPEC                            [RFC2215]
128-254   Unassigned                                    [RFC2216] 
255       Reserved for future expansion                 [RFC2216]


Registry Name: Compression Hints 
Reference: [RFC3006]
Registration Procedures: IETF Consensus

Note:
Hints are represented by a 32 bit field, with the high order 16 bits
being the IP-compression-protocol number as defined in [RFC1332] and
[RFC3544].  The low order 16 bits are a sub-option for the cases
where the IP-compression-protocol number alone is not sufficient for
int-serv purposes.

Registry:
Value (in hex)   Description                       Reference
---------------  --------------------------------  ---------
0x002d0000       Van Jacobson Compressed TCP/IP    [RFC1144]
0x00610000       IP Header Compression             [RFC2507] 
0x00610100       RTP Header Compression            [RFC2508]
0x0003pppp       ROHC profile 0xpppp               [RFC3241]


References
----------
[RFC1144]  V. Jacobson, "Compressing TCP/IP Headers for Low-Speed 
           Serial Links", RFC 1144, February 1990.

[RFC1332]  McGregor, G., "The PPP Internet Protocol Control Protocol
           (IPCP)", RFC 1332, Merit, May 1992.

[RFC2211]  J. Wroclawski, "Specification of the Controlled-Load 
           Network Element Service", RFC 2211, September 1997.

[RFC2212]  S. Shenker, C. Partridge, and R. Guerin, "Specification 
           of Guaranteed Quality of Service", RFC 2212, September 1997.

[RFC2215]  S. Shenker and J. Wroclawski, "General Characterization 
           Parameters for Integrated Service Network Elements",
           RFC 2215, September 1997.

[RFC2216]  S. Shenker and J. Wroclawski, "Network Element Service 
           Specification Template", RFC 2216, September 1997.

[RFC2507]  M. Degermark, B. Nordgren, and S. Pink, "IP Header 
           Compression", RFC 2507, February 1999.

[RFC2508]  S. Casner and V. Jacobson, "Compressing IP/UDP/RTP Headers 
           for Low-Speed Serial Links", RFC 2508, February 1999.

[RFC3006]  B. Davie, C. Iturralde, D. Oran, S. Casner, and J. Wroclawski,
           "Integrated Services in the Presence of Compressible Flows"
           RFC 3006, November 2000.

[RFC3241]  C. Bormann, "ROHC over PPP", RFC 3241, April 2002.

[RFC3544]  T. Koren, S. Casner, C. Bormann, "IP Header Compression over 
           PPP", RFC 3544, July 2003.

(created 2002-03-05)

[]