| 1 |
<pre>Network Working Group S. Yadav |
| 2 |
Request for Comments: 2752 R. Yavatkar |
| 3 |
Category: Standards Track Intel |
| 4 |
R. Pabbati |
| 5 |
P. Ford |
| 6 |
T. Moore |
| 7 |
Microsoft |
| 8 |
S. Herzog |
| 9 |
IPHighway |
| 10 |
January 2000 |
| 11 |
|
| 12 |
|
| 13 |
<span class="h1">Identity Representation for RSVP</span> |
| 14 |
|
| 15 |
Status of this Memo |
| 16 |
|
| 17 |
This document specifies an Internet standards track protocol for the |
| 18 |
Internet community, and requests discussion and suggestions for |
| 19 |
improvements. Please refer to the current edition of the "Internet |
| 20 |
Official Protocol Standards" (STD 1) for the standardization state |
| 21 |
and status of this protocol. Distribution of this memo is unlimited. |
| 22 |
|
| 23 |
Copyright Notice |
| 24 |
|
| 25 |
Copyright (C) The Internet Society (2000). All Rights Reserved. |
| 26 |
|
| 27 |
Abstract |
| 28 |
|
| 29 |
This document describes the representation of identity information in |
| 30 |
POLICY_DATA object [<a href="#ref-POL-EXT" title=""RSVP Extensions for Policy Control"">POL-EXT</a>] for supporting policy based admission |
| 31 |
control in RSVP. The goal of identity representation is to allow a |
| 32 |
process on a system to securely identify the owner and the |
| 33 |
application of the communicating process (e.g. user id) and convey |
| 34 |
this information in RSVP messages (PATH or RESV) in a secure manner. |
| 35 |
We describe the encoding of identities as RSVP policy element. We |
| 36 |
describe the processing rules to generate identity policy elements |
| 37 |
for multicast merged flows. Subsequently, we describe representations |
| 38 |
of user identities for Kerberos and Public Key based user |
| 39 |
authentication mechanisms. In summary we describe the use of this |
| 40 |
identity information in an operational setting. |
| 41 |
|
| 42 |
<span class="h2"><a class="selflink" id="section-1" href="#section-1">1</a>. Conventions used in this document</span> |
| 43 |
|
| 44 |
The key words "MUST", "MUST NOT", "REQUIRED", "SHALL", "SHALL NOT", |
| 45 |
"SHOULD", "SHOULD NOT", "RECOMMENDED", "MAY", and "OPTIONAL" in this |
| 46 |
document are to be interpreted as described in [<a href="./rfc2119">RFC-2119</a>]. |
| 47 |
|
| 48 |
|
| 49 |
|
| 50 |
|
| 51 |
|
| 52 |
<span class="grey">Yadav, et al. Standards Track [Page 1]</span></pre> |
| 53 |
<hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-2" ></span> |
| 54 |
<span class="grey"><a href="./rfc2752">RFC 2752</a> Identity Representation for RSVP January 2000</span> |
| 55 |
|
| 56 |
|
| 57 |
<span class="h2"><a class="selflink" id="section-2" href="#section-2">2</a>. Introduction</span> |
| 58 |
|
| 59 |
RSVP [<a href="./rfc2205">RFC 2205</a>] is a resource reservation setup protocol designed for |
| 60 |
an integrated services Internet [<a href="./rfc1633">RFC 1633</a>]. RSVP is used by a host to |
| 61 |
request specific quality of service (QoS) from the network for |
| 62 |
particular application data streams or flows. RSVP is also used by |
| 63 |
routers to deliver QoS requests to all nodes along the path(s) of the |
| 64 |
flows and to establish and maintain state to provide the requested |
| 65 |
service. RSVP requests will generally result in resources being |
| 66 |
reserved in each node along the data path. RSVP allows particular |
| 67 |
users to obtain preferential access to network resources, under the |
| 68 |
control of an admission control mechanism. Permission to make a |
| 69 |
reservation is based both upon the availability of the requested |
| 70 |
resources along the path of the data and upon satisfaction of policy |
| 71 |
rules. Providing policy based admission control mechanism based on |
| 72 |
user identity or application is one of the prime requirements. |
| 73 |
|
| 74 |
In order to solve these problems and implement identity based policy |
| 75 |
control it is required to identify the user and/or application making |
| 76 |
a RSVP request. |
| 77 |
|
| 78 |
This document proposes a mechanism for sending identification |
| 79 |
information in the RSVP messages and enables authorization decisions |
| 80 |
based on policy and identity. |
| 81 |
|
| 82 |
We describe the authentication policy element (AUTH_DATA) contained |
| 83 |
in the POLICY_DATA object. User process can generate an AUTH_DATA |
| 84 |
policy element and gives it to RSVP process (service) on the |
| 85 |
originating host. RSVP service inserts AUTH_DATA into the RSVP |
| 86 |
message to identify the owner (user and/or application) making the |
| 87 |
request for network resources. Network elements, such as routers, |
| 88 |
authenticate request using the credentials presented in the AUTH_DATA |
| 89 |
and admit the RSVP message based on admission policy. After a request |
| 90 |
has been authenticated, first hop router installs the RSVP state and |
| 91 |
forwards the new policy element returned by the Policy Decision Point |
| 92 |
(PDP) [<a href="#ref-POL-FRAME" title=""A Framework for Policy-based Admission Control RSVP"">POL-FRAME</a>]. |
| 93 |
|
| 94 |
<span class="h2"><a class="selflink" id="section-3" href="#section-3">3</a>. Policy Element for Authentication Data</span> |
| 95 |
|
| 96 |
<span class="h3"><a class="selflink" id="section-3.1" href="#section-3.1">3.1</a> Policy Data Object Format</span> |
| 97 |
|
| 98 |
POLICY_DATA objects contain policy information and are carried by |
| 99 |
RSVP messages. A detail description of the format of POLICY_DATA |
| 100 |
object can be found in "RSVP Extensions for Policy Control" [POL- |
| 101 |
EXT]. |
| 102 |
|
| 103 |
|
| 104 |
|
| 105 |
|
| 106 |
|
| 107 |
|
| 108 |
<span class="grey">Yadav, et al. Standards Track [Page 2]</span></pre> |
| 109 |
<hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-3" ></span> |
| 110 |
<span class="grey"><a href="./rfc2752">RFC 2752</a> Identity Representation for RSVP January 2000</span> |
| 111 |
|
| 112 |
|
| 113 |
<span class="h3"><a class="selflink" id="section-3.2" href="#section-3.2">3.2</a> Authentication Data Policy Element</span> |
| 114 |
|
| 115 |
In this section, we describe a policy element (PE) called |
| 116 |
authentication data (AUTH_DATA). AUTH_DATA policy element contains a |
| 117 |
list of authentication attributes. |
| 118 |
|
| 119 |
+-------------+-------------+-------------+-------------+ |
| 120 |
| Length | P-Type = Identity Type | |
| 121 |
+-------------+-------------+-------------+-------------+ |
| 122 |
// Authentication Attribute List // |
| 123 |
+-------------------------------------------------------+ |
| 124 |
|
| 125 |
Length |
| 126 |
The length of the policy element (including the Length and P- |
| 127 |
Type) is in number of octets (MUST be a multiple of 4) and |
| 128 |
indicates the end of the authentication attribute list. |
| 129 |
|
| 130 |
P-Type (Identity Type) |
| 131 |
Type of identity information contained in this Policy Element |
| 132 |
supplied as the Policy element type (P-type). The Internet |
| 133 |
Assigned Numbers Authority (IANA) acts as a registry for policy |
| 134 |
element types for identity as described in the [<a href="#ref-POL-EXT" title=""RSVP Extensions for Policy Control"">POL-EXT</a>]. |
| 135 |
Initially, the registry contains the following P-Types for |
| 136 |
identity: |
| 137 |
|
| 138 |
1 AUTH_USER Authentication scheme to identify users |
| 139 |
|
| 140 |
2 AUTH_APP Authentication scheme to identify |
| 141 |
applications |
| 142 |
|
| 143 |
Authentication Attribute List |
| 144 |
|
| 145 |
Authentication attributes contain information specific to |
| 146 |
authentication method and type of AUTH_DATA. The policy element |
| 147 |
provides the mechanism for grouping a collection of |
| 148 |
authentication attributes. |
| 149 |
|
| 150 |
<span class="h3"><a class="selflink" id="section-3.3" href="#section-3.3">3.3</a> Authentication Attributes</span> |
| 151 |
|
| 152 |
Authentication attributes MUST be encoded as a multiple of 4 octets, |
| 153 |
attributes that are not a multiple of 4 octets long MUST be padded to |
| 154 |
a 4-octet boundary. |
| 155 |
|
| 156 |
+--------+--------+--------+--------+ |
| 157 |
| Length | A-Type |SubType | |
| 158 |
+--------+--------+--------+--------+ |
| 159 |
| Value ... |
| 160 |
+--------+--------+--------+--------+ |
| 161 |
|
| 162 |
|
| 163 |
|
| 164 |
<span class="grey">Yadav, et al. Standards Track [Page 3]</span></pre> |
| 165 |
<hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-4" ></span> |
| 166 |
<span class="grey"><a href="./rfc2752">RFC 2752</a> Identity Representation for RSVP January 2000</span> |
| 167 |
|
| 168 |
|
| 169 |
|
| 170 |
Length |
| 171 |
The length field is two octets and indicates the actual length of |
| 172 |
the attribute (including the Length and A-Type fields) in number |
| 173 |
of octets. The length does not include any bytes padding to the |
| 174 |
value field to make the attribute multiple of 4 octets long. |
| 175 |
|
| 176 |
A-Type |
| 177 |
Authentication attribute type (A-Type) field is one octet. IANA |
| 178 |
acts as a registry for A-Types as described in the <a href="#section-9">section 9</a>, |
| 179 |
IANA Considerations. Initially, the registry contains the |
| 180 |
following A-Types: |
| 181 |
|
| 182 |
1 POLICY_LOCATOR Unique string for locating the |
| 183 |
admission policy (such as X.500 DN |
| 184 |
described in [<a href="./rfc1779">RFC 1779</a>]). |
| 185 |
|
| 186 |
2 CREDENTIAL User credential such as Kerberos |
| 187 |
ticket, or digital certificate. |
| 188 |
Application credential such as |
| 189 |
application ID. |
| 190 |
|
| 191 |
3 DIGITAL_SIGNATURE Digital signature of the |
| 192 |
authentication data policy element. |
| 193 |
|
| 194 |
4 POLICY_ERROR_OBJECT Detailed information on policy |
| 195 |
failures. |
| 196 |
|
| 197 |
SubType |
| 198 |
Authentication attribute sub-type field is one octet. Value of |
| 199 |
SubType depends on A-type. |
| 200 |
|
| 201 |
Value: |
| 202 |
The value field contains the attribute specific information. |
| 203 |
|
| 204 |
<span class="h4"><a class="selflink" id="section-3.3.1" href="#section-3.3.1">3.3.1</a> Policy Locator</span> |
| 205 |
|
| 206 |
POLICY_LOCATOR is used to locate the admission policy for the user |
| 207 |
or application. Distinguished Name (DN) is unique for each User or |
| 208 |
application hence a DN is used as policy locator. |
| 209 |
|
| 210 |
+-------+-------+-------+-------+ |
| 211 |
| Length |A-Type |SubType| |
| 212 |
+-------+-------+-------+-------+ |
| 213 |
| OctetString ... |
| 214 |
+-------+-------+-------+-------- |
| 215 |
|
| 216 |
|
| 217 |
|
| 218 |
|
| 219 |
|
| 220 |
<span class="grey">Yadav, et al. Standards Track [Page 4]</span></pre> |
| 221 |
<hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-5" ></span> |
| 222 |
<span class="grey"><a href="./rfc2752">RFC 2752</a> Identity Representation for RSVP January 2000</span> |
| 223 |
|
| 224 |
|
| 225 |
Length |
| 226 |
Length of the attribute, which MUST be >= 4. |
| 227 |
|
| 228 |
A-Type |
| 229 |
POLICY_LOCATOR |
| 230 |
|
| 231 |
SubType |
| 232 |
Following sub types for POLICY_LOCATOR are defined. IANA acts as |
| 233 |
a registry for POLICY_LOCATOR sub types as described in the |
| 234 |
<a href="#section-9">section 9</a>, IANA Considerations. Initially, the registry contains |
| 235 |
the following sub types for POLICY_LOCATOR: |
| 236 |
|
| 237 |
1 ASCII_DN OctetString contains the X.500 DN as described |
| 238 |
in the <a href="./rfc1779">RFC 1779</a> as an ASCII string. |
| 239 |
|
| 240 |
2 UNICODE_DN OctetString contains the X.500 DN described in |
| 241 |
the <a href="./rfc1779">RFC 1779</a> as an UNICODE string. |
| 242 |
|
| 243 |
3 ASCII_DN_ENCRYPT OctetString contains the encrypted X.500 |
| 244 |
DN. The Kerberos session key or digital |
| 245 |
certificate private key is used for encryption. |
| 246 |
For Kerberos encryption the format is the same |
| 247 |
as returned from gss_seal [<a href="./rfc1509">RFC 1509</a>]. |
| 248 |
|
| 249 |
4 UNICODE_DN_ENCRYPT OctetString contains the encrypted |
| 250 |
UNICODE X.500 DN. The Kerberos session key or |
| 251 |
digital certificate private key is used for |
| 252 |
encryption. For Kerberos encryption the format |
| 253 |
is the same as returned from gss_seal [RFC |
| 254 |
1509]. |
| 255 |
|
| 256 |
OctetString |
| 257 |
The OctetString field contains the DN. |
| 258 |
|
| 259 |
<span class="h4"><a class="selflink" id="section-3.3.2" href="#section-3.3.2">3.3.2</a> Credential</span> |
| 260 |
|
| 261 |
CREDENTIAL indicates the credential of the user or application to be |
| 262 |
authenticated. For Kerberos authentication method the CREDENTIAL |
| 263 |
object contains the Kerberos session ticket. For public key based |
| 264 |
authentication this field contains a digital certificate. |
| 265 |
|
| 266 |
A summary of the CREDENTIAL attribute format is shown below. The |
| 267 |
fields are transmitted from left to right. |
| 268 |
|
| 269 |
|
| 270 |
|
| 271 |
|
| 272 |
|
| 273 |
|
| 274 |
|
| 275 |
|
| 276 |
<span class="grey">Yadav, et al. Standards Track [Page 5]</span></pre> |
| 277 |
<hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-6" ></span> |
| 278 |
<span class="grey"><a href="./rfc2752">RFC 2752</a> Identity Representation for RSVP January 2000</span> |
| 279 |
|
| 280 |
|
| 281 |
+-------+-------+-------+-------+ |
| 282 |
| Length |A-Type |SubType| |
| 283 |
+-------+-------+-------+-------+ |
| 284 |
| OctetString ... |
| 285 |
+-------+-------+-------+-------- |
| 286 |
|
| 287 |
Length |
| 288 |
Length of the attribute, which MUST be >= 4. |
| 289 |
|
| 290 |
A-Type |
| 291 |
CREDENTIAL |
| 292 |
|
| 293 |
SubType |
| 294 |
IANA acts as a registry for CREDENTIAL sub types as described in |
| 295 |
the <a href="#section-9">section 9</a>, IANA Considerations. Initially, the registry |
| 296 |
contains the following sub types for CREDENTIAL: |
| 297 |
|
| 298 |
1 ASCII_ID OctetString contains user or application |
| 299 |
identification in plain ASCII text string. |
| 300 |
|
| 301 |
2 UNICODE_ID OctetString contains user or application |
| 302 |
identification in plain UNICODE text string. |
| 303 |
|
| 304 |
3 KERBEROS_TKT OctetString contains Kerberos ticket. |
| 305 |
|
| 306 |
4 X509_V3_CERT OctetString contains X.509 V3 digital |
| 307 |
certificate [<a href="#ref-X.509" title=""Internet X.509 Public Key Infrastructure Certificate and CRL Profile"">X.509</a>]. |
| 308 |
|
| 309 |
5 PGP_CERT OctetString contains PGP digital certificate. |
| 310 |
|
| 311 |
OctetString |
| 312 |
The OctetString contains the user or application credential. |
| 313 |
|
| 314 |
<span class="h4"><a class="selflink" id="section-3.3.3" href="#section-3.3.3">3.3.3</a> Digital Signature</span> |
| 315 |
|
| 316 |
The DIGITAL_SIGNATURE attribute MUST be the last attribute in the |
| 317 |
attribute list and contains the digital signature of the AUTH_DATA |
| 318 |
policy element. The digital signature signs all data in the |
| 319 |
AUTH_DATA policy element up to the DIGITAL_SIGNATURE. The algorithm |
| 320 |
used to compute the digital signature depends on the authentication |
| 321 |
method specified by the CREDENTIAL SubType field. |
| 322 |
|
| 323 |
A summary of DIGITAL_SIGNATURE attribute format is described below. |
| 324 |
|
| 325 |
|
| 326 |
|
| 327 |
|
| 328 |
|
| 329 |
|
| 330 |
|
| 331 |
|
| 332 |
<span class="grey">Yadav, et al. Standards Track [Page 6]</span></pre> |
| 333 |
<hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-7" ></span> |
| 334 |
<span class="grey"><a href="./rfc2752">RFC 2752</a> Identity Representation for RSVP January 2000</span> |
| 335 |
|
| 336 |
|
| 337 |
+-------+-------+-------+-------+ |
| 338 |
| Length |A-Type |SubType| |
| 339 |
+-------+-------+-------+-------+ |
| 340 |
| OctetString ... |
| 341 |
+-------+-------+-------+-------- |
| 342 |
|
| 343 |
Length |
| 344 |
Length of the attribute, which MUST be >= 4. |
| 345 |
|
| 346 |
ti3 A-Type |
| 347 |
DIGITAL_SIGNATURE |
| 348 |
|
| 349 |
SubType |
| 350 |
No sub types for DIGITAL_SIGNATURE are currently defined. This |
| 351 |
field MUST be set to 0. |
| 352 |
|
| 353 |
OctetString |
| 354 |
OctetString contains the digital signature of the AUTH_DATA. |
| 355 |
|
| 356 |
<span class="h4"><a class="selflink" id="section-3.3.4" href="#section-3.3.4">3.3.4</a> Policy Error Object</span> |
| 357 |
|
| 358 |
This attribute is used to carry any specific policy control errors |
| 359 |
generated by a node when processing/validating an Authentication Data |
| 360 |
Policy Element. When a RSVP policy node (local policy decision point |
| 361 |
or remote PDP) encounters a request that fails policy control due to |
| 362 |
its Authentication Policy Element, it SHOULD add a POLICY_ERROR_CODE |
| 363 |
containing additional information about the reason the failure |
| 364 |
occurred into the policy element. This will then cause an appropriate |
| 365 |
PATH_ERROR or RESV_ERROR message to be generated with the policy |
| 366 |
element and appropriate RSVP error code in the message, which is |
| 367 |
returned to the request's source. |
| 368 |
|
| 369 |
The AUTH_DATA policy element in the PATH or RSVP message SHOULD not |
| 370 |
contain the POLICY_ERROR_OBJECT attribute. These are only inserted |
| 371 |
into PATH_ERROR and RESV_ERROR messages when generated by policy |
| 372 |
aware intermediate nodes. |
| 373 |
|
| 374 |
+----------+----------+----------+----------+ |
| 375 |
| Length | A-Type |SubType(0)| |
| 376 |
+----------+----------+----------+----------+ |
| 377 |
| 0 (Reserved) | ErrorValue | |
| 378 |
+----------+----------+----------+----------+ |
| 379 |
| OctetString ... |
| 380 |
+----------+----------+----------+----------+ |
| 381 |
|
| 382 |
Length |
| 383 |
Length of the attribute, which MUST be >= 8. |
| 384 |
|
| 385 |
|
| 386 |
|
| 387 |
|
| 388 |
<span class="grey">Yadav, et al. Standards Track [Page 7]</span></pre> |
| 389 |
<hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-8" ></span> |
| 390 |
<span class="grey"><a href="./rfc2752">RFC 2752</a> Identity Representation for RSVP January 2000</span> |
| 391 |
|
| 392 |
|
| 393 |
A-Type |
| 394 |
POLICY_ERROR_CODE |
| 395 |
|
| 396 |
ErrorValue |
| 397 |
A 32-bit bit code containing the reason that the policy decision |
| 398 |
point failed to process the policy element. Following values have |
| 399 |
been defined. |
| 400 |
|
| 401 |
1 ERROR_NO_MORE_INFO No information is available. |
| 402 |
2 UNSUPPORTED_CREDENTIAL_TYPE This type of credentials is |
| 403 |
not supported. |
| 404 |
|
| 405 |
3 INSUFFICIENT_PRIVILEGES The credentials do not have |
| 406 |
sufficient privilege. |
| 407 |
|
| 408 |
4 EXPIRED_CREDENTIAL The credential has expired. |
| 409 |
|
| 410 |
5 IDENTITY_CHANGED Identity has changed. |
| 411 |
|
| 412 |
OctetString |
| 413 |
The OctetString field contains information from the policy |
| 414 |
decision point that MAY contain additional information about the |
| 415 |
policy failure. For example, it may include a human-readable |
| 416 |
message in the ASCII text. |
| 417 |
|
| 418 |
<span class="h2"><a class="selflink" id="section-4" href="#section-4">4</a>. Authentication Data Formats</span> |
| 419 |
|
| 420 |
Authentication attributes are grouped in a policy element to |
| 421 |
represent the identity credentials. |
| 422 |
|
| 423 |
<span class="h3"><a class="selflink" id="section-4.1" href="#section-4.1">4.1</a> Simple User Authentication</span> |
| 424 |
|
| 425 |
In simple user authentication method the user login ID (in plain |
| 426 |
ASCII or UNICODE text) is encoded as CREDENTIAL attribute. A summary |
| 427 |
of the simple user AUTH_DATA policy element is shown below. |
| 428 |
|
| 429 |
+--------------+--------------+--------------+--------------+ |
| 430 |
| Length | P-type = AUTH_USER | |
| 431 |
+--------------+--------------+--------------+--------------+ |
| 432 |
| Length |POLICY_LOCATOR| SubType | |
| 433 |
+--------------+--------------+--------------+--------------+ |
| 434 |
| OctetString (User's Distinguished Name) ... |
| 435 |
+--------------+--------------+--------------+--------------+ |
| 436 |
| Length |CREDENTIAL | ASCII_ID | |
| 437 |
+--------------+--------------+--------------+--------------+ |
| 438 |
| OctetString (User's login ID) ... |
| 439 |
+--------------+--------------+--------------+--------------+ |
| 440 |
|
| 441 |
|
| 442 |
|
| 443 |
|
| 444 |
<span class="grey">Yadav, et al. Standards Track [Page 8]</span></pre> |
| 445 |
<hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-9" ></span> |
| 446 |
<span class="grey"><a href="./rfc2752">RFC 2752</a> Identity Representation for RSVP January 2000</span> |
| 447 |
|
| 448 |
|
| 449 |
<span class="h3"><a class="selflink" id="section-4.2" href="#section-4.2">4.2</a> Kerberos User Authentication</span> |
| 450 |
|
| 451 |
Kerberos [<a href="./rfc1510">RFC 1510</a>] authentication uses a trusted third party (the |
| 452 |
Kerberos Distribution Center - KDC) to provide for authentication of |
| 453 |
the user to a network server. It is assumed that a KDC is present and |
| 454 |
both host and verifier of authentication information (router or PDP) |
| 455 |
implement Kerberos authentication. |
| 456 |
|
| 457 |
A summary of the Kerberos AUTH_DATA policy element is shown below. |
| 458 |
|
| 459 |
+--------------+--------------+--------------+--------------+ |
| 460 |
| Length | P-type = AUTH_USER | |
| 461 |
+--------------+--------------+--------------+--------------+ |
| 462 |
| Length |POLICY_LOCATOR| SubType | |
| 463 |
+--------------+--------------+--------------+--------------+ |
| 464 |
| OctetString (User's Distinguished Name) ... |
| 465 |
+--------------+--------------+--------------+--------------+ |
| 466 |
| Length | CREDENTIAL | KERBEROS_TKT | |
| 467 |
+--------------+--------------+--------------+--------------+ |
| 468 |
| OctetString (Kerberos Session Ticket) ... |
| 469 |
+--------------+--------------+--------------+--------------+ |
| 470 |
|
| 471 |
<span class="h4"><a class="selflink" id="section-4.2.1" href="#section-4.2.1">4.2.1</a>. Operational Setting using Kerberos Identities</span> |
| 472 |
|
| 473 |
An RSVP enabled host is configured to construct and insert AUTH_DATA |
| 474 |
policy element into RSVP messages that designate use of the Kerberos |
| 475 |
authentication method (KERBEROS_TKT). Upon RSVP session |
| 476 |
initialization, the user application contacts the KDC to obtain a |
| 477 |
Kerberos ticket for the next network node or its PDP. A router when |
| 478 |
generating a RSVP message contacts the KDC to obtain a Kerberos |
| 479 |
ticket for the next hop network node or its PDP. The identity of the |
| 480 |
PDP or next network hop can be statically configured, learned via |
| 481 |
DHCP or maintained in a directory service. The Kerberos ticket is |
| 482 |
sent to the next network node (which may be a router or host) in a |
| 483 |
RSVP message. The KDC is used to validate the ticket and |
| 484 |
authentication the user sending RSVP message. |
| 485 |
|
| 486 |
<span class="h3"><a class="selflink" id="section-4.3" href="#section-4.3">4.3</a> Public Key based User Authentication</span> |
| 487 |
|
| 488 |
In public key based user authentication method digital certificate is |
| 489 |
encoded as user credentials. The digital signature is used for |
| 490 |
authenticating the user. A summary of the public key user AUTH_DATA |
| 491 |
policy element is shown below. |
| 492 |
|
| 493 |
|
| 494 |
|
| 495 |
|
| 496 |
|
| 497 |
|
| 498 |
|
| 499 |
|
| 500 |
<span class="grey">Yadav, et al. Standards Track [Page 9]</span></pre> |
| 501 |
<hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-10" ></span> |
| 502 |
<span class="grey"><a href="./rfc2752">RFC 2752</a> Identity Representation for RSVP January 2000</span> |
| 503 |
|
| 504 |
|
| 505 |
+--------------+--------------+--------------+--------------+ |
| 506 |
| Length | P-type = AUTH_USER | |
| 507 |
+--------------+--------------+--------------+--------------+ |
| 508 |
| Length |POLICY_LOCATOR| SubType | |
| 509 |
+--------------+--------------+--------------+--------------+ |
| 510 |
| OctetString (User's Distinguished Name) ... |
| 511 |
+--------------+--------------+--------------+--------------+ |
| 512 |
| Length | CREDENTIAL | SubType | |
| 513 |
+--------------+--------------+--------------+--------------+ |
| 514 |
| OctetString (User's Digital Certificate) ... |
| 515 |
+--------------+--------------+--------------+--------------+ |
| 516 |
| Length |DIGITAL_SIGN. | 0 | |
| 517 |
+--------------+--------------+--------------+--------------+ |
| 518 |
| OctetString (Digital signature) ... |
| 519 |
+--------------+--------------+--------------+--------------+ |
| 520 |
|
| 521 |
<span class="h4"><a class="selflink" id="section-4.3.1" href="#section-4.3.1">4.3.1</a>. Operational Setting for public key based authentication</span> |
| 522 |
|
| 523 |
Public key based authentication assumes following: |
| 524 |
|
| 525 |
- RSVP service requestors have a pair of keys (private key and |
| 526 |
public key). |
| 527 |
|
| 528 |
- Private key is secured with the user. |
| 529 |
|
| 530 |
- Public keys are stored in digital certificates and a trusted |
| 531 |
party, certificate authority (CA) issues these digital |
| 532 |
certificates. |
| 533 |
|
| 534 |
- The verifier (PDP or router) has the ability to verify the |
| 535 |
digital certificate. |
| 536 |
|
| 537 |
RSVP requestor uses its private key to generate DIGITAL_SIGNATURE. |
| 538 |
User Authenticators (router, PDP) use the user's public key (stored |
| 539 |
in the digital certificate) to verify the signature and authenticate |
| 540 |
the user. |
| 541 |
|
| 542 |
<span class="h3"><a class="selflink" id="section-4.4" href="#section-4.4">4.4</a> Simple Application Authentication</span> |
| 543 |
|
| 544 |
The application authentication method encodes the application |
| 545 |
identification such as an executable filename as plain ASCII or |
| 546 |
UNICODE text. |
| 547 |
|
| 548 |
|
| 549 |
|
| 550 |
|
| 551 |
|
| 552 |
|
| 553 |
|
| 554 |
|
| 555 |
|
| 556 |
<span class="grey">Yadav, et al. Standards Track [Page 10]</span></pre> |
| 557 |
<hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-11" ></span> |
| 558 |
<span class="grey"><a href="./rfc2752">RFC 2752</a> Identity Representation for RSVP January 2000</span> |
| 559 |
|
| 560 |
|
| 561 |
+----------------+--------------+--------------+--------------+ |
| 562 |
| Length | P-type = AUTH_APP | |
| 563 |
+----------------+--------------+--------------+--------------+ |
| 564 |
| Length |POLICY_LOCATOR| SubType | |
| 565 |
+----------------+--------------+--------------+--------------+ |
| 566 |
| OctetString (Application Identity attributes in |
| 567 |
| the form of a Distinguished Name) ... |
| 568 |
+----------------+--------------+--------------+--------------+ |
| 569 |
| Length | CREDENTIAL | ASCII_ID | |
| 570 |
+----------------+--------------+--------------+--------------+ |
| 571 |
| OctetString (Application Id, e.g., vic.exe) |
| 572 |
+----------------+--------------+--------------+--------------+ |
| 573 |
|
| 574 |
<span class="h2"><a class="selflink" id="section-5" href="#section-5">5</a>. Operation</span> |
| 575 |
|
| 576 |
+-----+ +-----+ |
| 577 |
| PDP |-------+ | PDP | |
| 578 |
+-----+ | ................... +-----+ |
| 579 |
| : : | |
| 580 |
+--------+ : Transit : +-------+ |
| 581 |
+----| Router |------: Network : -------| Router|--+ |
| 582 |
| +--------+ : : +-------+ | |
| 583 |
| | :.................: | | |
| 584 |
| | | | |
| 585 |
Host A B C D |
| 586 |
|
| 587 |
Figure 1: User and Application Authentication using AUTH_DATA PE |
| 588 |
|
| 589 |
Network nodes (hosts/routers) generate AUTH_DATA policy elements, |
| 590 |
contents of which are depend on the identity type used and the |
| 591 |
authentication method used. These generally contain authentication |
| 592 |
credentials (Kerberos ticket or digital certificate) and policy |
| 593 |
locators (which can be the X.500 Distinguished Name of the user or |
| 594 |
network node or application names). Network nodes generate AUTH_DATA |
| 595 |
policy element containing the authentication identity when making the |
| 596 |
RSVP request or forwarding a RSVP message. |
| 597 |
|
| 598 |
Network nodes generate user AUTH_DATA policy element using the |
| 599 |
following rules |
| 600 |
|
| 601 |
1. For unicast sessions the user policy locator is copied from the |
| 602 |
previous hop. The authentication credentials are for the current |
| 603 |
network node identity. |
| 604 |
|
| 605 |
2. For multicast messages the user policy locator is for the current |
| 606 |
network node identity. The authentication credentials are for the |
| 607 |
current network node. |
| 608 |
|
| 609 |
|
| 610 |
|
| 611 |
|
| 612 |
<span class="grey">Yadav, et al. Standards Track [Page 11]</span></pre> |
| 613 |
<hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-12" ></span> |
| 614 |
<span class="grey"><a href="./rfc2752">RFC 2752</a> Identity Representation for RSVP January 2000</span> |
| 615 |
|
| 616 |
|
| 617 |
Network nodes generate application AUTH_DATA policy element using the |
| 618 |
following rules: |
| 619 |
|
| 620 |
1. For unicast sessions the application AUTH_DATA is copied from the |
| 621 |
previous hop. |
| 622 |
|
| 623 |
2. For multicast messages the application AUTH_DATA is either the |
| 624 |
first application AUTH_DATA in the message or chosen by the PDP. |
| 625 |
|
| 626 |
<span class="h2"><a class="selflink" id="section-6" href="#section-6">6</a>. Message Processing Rules</span> |
| 627 |
|
| 628 |
<span class="h3"><a class="selflink" id="section-6.1" href="#section-6.1">6.1</a> Message Generation (RSVP Host)</span> |
| 629 |
|
| 630 |
An RSVP message is created as specified in [<a href="./rfc2205">RFC2205</a>] with following |
| 631 |
modifications. |
| 632 |
|
| 633 |
1. RSVP message MAY contain multiple AUTH_DATA policy elements. |
| 634 |
|
| 635 |
2. Authentication policy element (AUTH_DATA) is created and the |
| 636 |
IdentityType field is set to indicate the identity type in the |
| 637 |
policy element. |
| 638 |
|
| 639 |
- DN is inserted as POLICY_LOCATOR attribute. |
| 640 |
|
| 641 |
- Credentials such as Kerberos ticket or digital certificate are |
| 642 |
inserted as the CREDENTIAL attribute. |
| 643 |
|
| 644 |
3. POLICY_DATA object (containing the AUTH_DATA policy element) is |
| 645 |
inserted in the RSVP message in appropriate place. If INTEGRITY |
| 646 |
object is not computed for the RSVP message then an INTEGRITY |
| 647 |
object SHOULD be computed for this POLICY_DATA object, as |
| 648 |
described in the [POL_EXT], and SHOULD be inserted as a Policy |
| 649 |
Data option. |
| 650 |
|
| 651 |
<span class="h3"><a class="selflink" id="section-6.2" href="#section-6.2">6.2</a> Message Reception (Router)</span> |
| 652 |
|
| 653 |
RSVP message is processed as specified in [<a href="./rfc2205">RFC2205</a>] with following |
| 654 |
modifications. |
| 655 |
|
| 656 |
1. If router is not policy aware then it SHOULD send the RSVP message |
| 657 |
to the PDP and wait for response. If the router is policy unaware |
| 658 |
then it ignores the policy data objects and continues processing |
| 659 |
the RSVP message. |
| 660 |
|
| 661 |
2. Reject the message if the response from the PDP is negative. |
| 662 |
|
| 663 |
3. Continue processing the RSVP message. |
| 664 |
|
| 665 |
|
| 666 |
|
| 667 |
|
| 668 |
<span class="grey">Yadav, et al. Standards Track [Page 12]</span></pre> |
| 669 |
<hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-13" ></span> |
| 670 |
<span class="grey"><a href="./rfc2752">RFC 2752</a> Identity Representation for RSVP January 2000</span> |
| 671 |
|
| 672 |
|
| 673 |
<span class="h3"><a class="selflink" id="section-6.3" href="#section-6.3">6.3</a> Authentication (Router/PDP)</span> |
| 674 |
|
| 675 |
1. Retrieve the AUTH_DATA policy element. Check the PE type field and |
| 676 |
return an error if the identity type is not supported. |
| 677 |
|
| 678 |
2. Verify user credential |
| 679 |
|
| 680 |
- Simple authentication: e.g. Get user ID and validate it, or get |
| 681 |
executable name and validate it. |
| 682 |
|
| 683 |
- Kerberos: Send the Kerberos ticket to the KDC to obtain the |
| 684 |
session key. Using the session key authenticate the user. |
| 685 |
|
| 686 |
- Public Key: Validate the certificate that it was issued by a |
| 687 |
trusted Certificate Authority (CA) and authenticate the user or |
| 688 |
application by verifying the digital signature. |
| 689 |
|
| 690 |
<span class="h2"><a class="selflink" id="section-7" href="#section-7">7</a>. Error Signaling</span> |
| 691 |
|
| 692 |
If PDP fails to verify the AUTH_DATA policy element then it MUST |
| 693 |
return policy control failure (Error Code = 02) to the PEP. The error |
| 694 |
values are described in [<a href="./rfc2205">RFC 2205</a>] and [<a href="#ref-POL-EXT" title=""RSVP Extensions for Policy Control"">POL-EXT</a>]. Also PDP SHOULD |
| 695 |
supply a policy data object containing an AUTH_DATA Policy Element |
| 696 |
with A-Type=POLICY_ERROR_CODE containing more details on the Policy |
| 697 |
Control failure (see <a href="#section-3.3.4">section 3.3.4</a>). The PEP will include this Policy |
| 698 |
Data object in the outgoing RSVP Error message. |
| 699 |
|
| 700 |
<span class="h2"><a class="selflink" id="section-8" href="#section-8">8</a>. IANA Considerations</span> |
| 701 |
|
| 702 |
Following the policies outlined in [<a href="#ref-IANA-CONSIDERATIONS" title="">IANA-CONSIDERATIONS</a>], |
| 703 |
authentication attribute types (A-Type)in the range 0-127 are |
| 704 |
allocated through an IETF Consensus action, A-Type values between |
| 705 |
128-255 are reserved for Private Use and are not assigned by IANA. |
| 706 |
|
| 707 |
Following the policies outlined in [<a href="#ref-IANA-CONSIDERATIONS" title="">IANA-CONSIDERATIONS</a>], |
| 708 |
POLICY_LOCATOR SubType values in the range 0-127 are allocated |
| 709 |
through an IETF Consensus action, POLICY_LOCATOR SubType values |
| 710 |
between 128-255 are reserved for Private Use and are not assigned by |
| 711 |
IANA. |
| 712 |
|
| 713 |
Following the policies outlined in [<a href="#ref-IANA-CONSIDERATIONS" title="">IANA-CONSIDERATIONS</a>], CREDENTIAL |
| 714 |
SubType values in the range 0-127 are allocated through an IETF |
| 715 |
Consensus action, CREDENTIAL SubType values between 128-255 are |
| 716 |
reserved for Private Use and are not assigned by IANA. |
| 717 |
|
| 718 |
|
| 719 |
|
| 720 |
|
| 721 |
|
| 722 |
|
| 723 |
|
| 724 |
<span class="grey">Yadav, et al. Standards Track [Page 13]</span></pre> |
| 725 |
<hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-14" ></span> |
| 726 |
<span class="grey"><a href="./rfc2752">RFC 2752</a> Identity Representation for RSVP January 2000</span> |
| 727 |
|
| 728 |
|
| 729 |
<span class="h2"><a class="selflink" id="section-9" href="#section-9">9</a>. Security Considerations</span> |
| 730 |
|
| 731 |
The purpose of this memo is to describe a mechanism to authenticate |
| 732 |
RSVP requests based on user identity in a secure manner. RSVP |
| 733 |
INTEGRITY object is used to protect the policy object containing user |
| 734 |
identity information from security (replay) attacks. Combining the |
| 735 |
AUTH_DATA policy element and the INTEGRITY object results in a secure |
| 736 |
access control that enforces authentication based on both the |
| 737 |
identity of the user and the identity of the originating node. |
| 738 |
|
| 739 |
Simple authentication does not contain credential that can be |
| 740 |
securely authenticated and is inherently less secured. |
| 741 |
|
| 742 |
The Kerberos authentication mechanism is reasonably well secured. |
| 743 |
|
| 744 |
User authentication using a public key certificate is known to |
| 745 |
provide the strongest security. |
| 746 |
|
| 747 |
<span class="h2"><a class="selflink" id="section-10" href="#section-10">10</a>. Acknowledgments</span> |
| 748 |
|
| 749 |
We would like to thank Andrew Smith, Bob Lindell and many others for |
| 750 |
their valuable comments on this memo. |
| 751 |
|
| 752 |
<span class="h2"><a class="selflink" id="section-11" href="#section-11">11</a>. References</span> |
| 753 |
|
| 754 |
[<a id="ref-ASCII">ASCII</a>] Coded Character Set -- 7-Bit American Standard |
| 755 |
Code for Information Interchange, ANSI X3.4- |
| 756 |
1986. |
| 757 |
|
| 758 |
[<a id="ref-IANA-CONSIDERATIONS">IANA-CONSIDERATIONS</a>] Alvestrand, H. and T. Narten, "Guidelines for |
| 759 |
Writing an IANA Considerations Section in |
| 760 |
RFCs", <a href="https://www.rfc-editor.org/bcp/bcp26">BCP 26</a>, <a href="./rfc2434">RFC 2434</a>, October 1998. |
| 761 |
|
| 762 |
[<a id="ref-POL-EXT">POL-EXT</a>] Herzog, S., "RSVP Extensions for Policy |
| 763 |
Control", <a href="./rfc2750">RFC 2750</a>, January 2000. |
| 764 |
|
| 765 |
[<a id="ref-POL-FRAME">POL-FRAME</a>] Yavatkar, R., Pendarakis, D. and R. Guerin, "A |
| 766 |
Framework for Policy-based Admission Control |
| 767 |
RSVP", <a href="./rfc2753">RFC 2753</a>, January 2000. |
| 768 |
|
| 769 |
[<a id="ref-RFC 1510">RFC 1510</a>] Kohl, J. and C. Neuman, "The Kerberos Network |
| 770 |
Authentication Service (V5)", <a href="./rfc1510">RFC 1510</a>, |
| 771 |
September 1993. |
| 772 |
|
| 773 |
[<a id="ref-RFC 1704">RFC 1704</a>] Haller, N. and R. Atkinson, "On Internet |
| 774 |
Authentication", <a href="./rfc1704">RFC 1704</a>, October 1994. |
| 775 |
|
| 776 |
|
| 777 |
|
| 778 |
|
| 779 |
|
| 780 |
<span class="grey">Yadav, et al. Standards Track [Page 14]</span></pre> |
| 781 |
<hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-15" ></span> |
| 782 |
<span class="grey"><a href="./rfc2752">RFC 2752</a> Identity Representation for RSVP January 2000</span> |
| 783 |
|
| 784 |
|
| 785 |
[<a id="ref-RFC 1779">RFC 1779</a>] Killie, S., "A String Representation of |
| 786 |
Distinguished Names", <a href="./rfc1779">RFC 1779</a>, March 1995. |
| 787 |
|
| 788 |
[<a id="ref-RFC 2205">RFC 2205</a>] Braden, R., Zhang, L., Berson, S., Herzog, S. |
| 789 |
and S. Jamin, "Resource ReSerVation Protocol |
| 790 |
(RSVP) - Version 1 Functional Specification", |
| 791 |
<a href="./rfc2205">RFC 2205</a>, September 1997. |
| 792 |
|
| 793 |
[<a id="ref-RFC 2209">RFC 2209</a>] Braden, R. and L. Zhang, "Resource ReSerVation |
| 794 |
Protocol (RSVP) - Version 1 Message Processing |
| 795 |
Rules", <a href="./rfc2209">RFC 2209</a>, September 1997. |
| 796 |
|
| 797 |
[<a id="ref-UNICODE">UNICODE</a>] The Unicode Consortium, "The Unicode Standard, |
| 798 |
Version 2.0", Addison-Wesley, Reading, MA, |
| 799 |
1996. |
| 800 |
|
| 801 |
[<a id="ref-X.509">X.509</a>] Housley, R., Ford, W., Polk, W. and D. Solo, |
| 802 |
"Internet X.509 Public Key Infrastructure |
| 803 |
Certificate and CRL Profile", <a href="./rfc2459">RFC 2459</a>, January |
| 804 |
1999. |
| 805 |
|
| 806 |
[<a id="ref-X.509-ITU">X.509-ITU</a>] ITU-T (formerly CCITT) Information technology - |
| 807 |
Open Systems Interconnection - The Directory: |
| 808 |
Authentication Framework Recommendation X.509 |
| 809 |
ISO/IEC 9594-8 |
| 810 |
|
| 811 |
|
| 812 |
|
| 813 |
|
| 814 |
|
| 815 |
|
| 816 |
|
| 817 |
|
| 818 |
|
| 819 |
|
| 820 |
|
| 821 |
|
| 822 |
|
| 823 |
|
| 824 |
|
| 825 |
|
| 826 |
|
| 827 |
|
| 828 |
|
| 829 |
|
| 830 |
|
| 831 |
|
| 832 |
|
| 833 |
|
| 834 |
|
| 835 |
|
| 836 |
<span class="grey">Yadav, et al. Standards Track [Page 15]</span></pre> |
| 837 |
<hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-16" ></span> |
| 838 |
<span class="grey"><a href="./rfc2752">RFC 2752</a> Identity Representation for RSVP January 2000</span> |
| 839 |
|
| 840 |
|
| 841 |
<span class="h2"><a class="selflink" id="section-12" href="#section-12">12</a>. Author Information</span> |
| 842 |
|
| 843 |
Satyendra Yadav |
| 844 |
Intel, JF3-206 |
| 845 |
2111 NE 25th Avenue |
| 846 |
Hillsboro, OR 97124 |
| 847 |
|
| 848 |
EMail: [email protected] |
| 849 |
|
| 850 |
|
| 851 |
Raj Yavatkar |
| 852 |
Intel, JF3-206 |
| 853 |
2111 NE 25th Avenue |
| 854 |
Hillsboro, OR 97124 |
| 855 |
|
| 856 |
EMail: [email protected] |
| 857 |
|
| 858 |
|
| 859 |
Ramesh Pabbati |
| 860 |
Microsoft |
| 861 |
1 Microsoft Way |
| 862 |
Redmond, WA 98054 |
| 863 |
|
| 864 |
EMail: [email protected] |
| 865 |
|
| 866 |
|
| 867 |
Peter Ford |
| 868 |
Microsoft |
| 869 |
1 Microsoft Way |
| 870 |
Redmond, WA 98054 |
| 871 |
|
| 872 |
EMail: [email protected] |
| 873 |
|
| 874 |
|
| 875 |
Tim Moore |
| 876 |
Microsoft |
| 877 |
1 Microsoft Way |
| 878 |
Redmond, WA 98054 |
| 879 |
|
| 880 |
EMail: [email protected] |
| 881 |
|
| 882 |
|
| 883 |
Shai Herzog |
| 884 |
IPHighway, Inc. |
| 885 |
55 New York Avenue |
| 886 |
Framingham, MA 01701 |
| 887 |
|
| 888 |
EMail: [email protected] |
| 889 |
|
| 890 |
|
| 891 |
|
| 892 |
<span class="grey">Yadav, et al. Standards Track [Page 16]</span></pre> |
| 893 |
<hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-17" ></span> |
| 894 |
<span class="grey"><a href="./rfc2752">RFC 2752</a> Identity Representation for RSVP January 2000</span> |
| 895 |
|
| 896 |
|
| 897 |
<span class="h2"><a class="selflink" id="section-13" href="#section-13">13</a>. Full Copyright Statement</span> |
| 898 |
|
| 899 |
Copyright (C) The Internet Society (2000). All Rights Reserved. |
| 900 |
|
| 901 |
This document and translations of it may be copied and furnished to |
| 902 |
others, and derivative works that comment on or otherwise explain it |
| 903 |
or assist in its implementation may be prepared, copied, published |
| 904 |
and distributed, in whole or in part, without restriction of any |
| 905 |
kind, provided that the above copyright notice and this paragraph are |
| 906 |
included on all such copies and derivative works. However, this |
| 907 |
document itself may not be modified in any way, such as by removing |
| 908 |
the copyright notice or references to the Internet Society or other |
| 909 |
Internet organizations, except as needed for the purpose of |
| 910 |
developing Internet standards in which case the procedures for |
| 911 |
copyrights defined in the Internet Standards process must be |
| 912 |
followed, or as required to translate it into languages other than |
| 913 |
English. |
| 914 |
|
| 915 |
The limited permissions granted above are perpetual and will not be |
| 916 |
revoked by the Internet Society or its successors or assigns. |
| 917 |
|
| 918 |
This document and the information contained herein is provided on an |
| 919 |
"AS IS" basis and THE INTERNET SOCIETY AND THE INTERNET ENGINEERING |
| 920 |
TASK FORCE DISCLAIMS ALL WARRANTIES, EXPRESS OR IMPLIED, INCLUDING |
| 921 |
BUT NOT LIMITED TO ANY WARRANTY THAT THE USE OF THE INFORMATION |
| 922 |
HEREIN WILL NOT INFRINGE ANY RIGHTS OR ANY IMPLIED WARRANTIES OF |
| 923 |
MERCHANTABILITY OR FITNESS FOR A PARTICULAR PURPOSE. |
| 924 |
|
| 925 |
Acknowledgement |
| 926 |
|
| 927 |
Funding for the RFC Editor function is currently provided by the |
| 928 |
Internet Society. |
| 929 |
|
| 930 |
|
| 931 |
|
| 932 |
|
| 933 |
|
| 934 |
|
| 935 |
|
| 936 |
|
| 937 |
|
| 938 |
|
| 939 |
|
| 940 |
|
| 941 |
|
| 942 |
|
| 943 |
|
| 944 |
|
| 945 |
|
| 946 |
|
| 947 |
|
| 948 |
Yadav, et al. Standards Track [Page 17] |
| 949 |
</pre> |