draft-ietf-geopriv-radius-lo-15.txt   draft-ietf-geopriv-radius-lo-16.txt 
GEOPRIV H. Tschofenig, Ed. GEOPRIV H. Tschofenig, Ed.
Internet-Draft Nokia Siemens Networks Internet-Draft Nokia Siemens Networks
Intended status: Standards Track F. Adrangi Intended status: Standards Track F. Adrangi
Expires: January 10, 2008 Intel Expires: February 27, 2008 Intel
M. Jones M. Jones
A. Lior A. Lior
Bridgewater Bridgewater
July 9, 2007 B. Aboba
Microsoft Corporation
August 26, 2007
Carrying Location Objects in RADIUS and Diameter Carrying Location Objects in RADIUS and Diameter
draft-ietf-geopriv-radius-lo-15.txt draft-ietf-geopriv-radius-lo-16.txt
Status of this Memo Status of this Memo
By submitting this Internet-Draft, each author represents that any By submitting this Internet-Draft, each author represents that any
applicable patent or other IPR claims of which he or she is aware applicable patent or other IPR claims of which he or she is aware
have been or will be disclosed, and any of which he or she becomes have been or will be disclosed, and any of which he or she becomes
aware will be disclosed, in accordance with Section 6 of BCP 79. aware will be disclosed, in accordance with Section 6 of BCP 79.
Internet-Drafts are working documents of the Internet Engineering Internet-Drafts are working documents of the Internet Engineering
Task Force (IETF), its areas, and its working groups. Note that Task Force (IETF), its areas, and its working groups. Note that
skipping to change at page 1, line 38 skipping to change at page 1, line 40
and may be updated, replaced, or obsoleted by other documents at any and may be updated, replaced, or obsoleted by other documents at any
time. It is inappropriate to use Internet-Drafts as reference time. It is inappropriate to use Internet-Drafts as reference
material or to cite them other than as "work in progress." material or to cite them other than as "work in progress."
The list of current Internet-Drafts can be accessed at The list of current Internet-Drafts can be accessed at
http://www.ietf.org/ietf/1id-abstracts.txt. http://www.ietf.org/ietf/1id-abstracts.txt.
The list of Internet-Draft Shadow Directories can be accessed at The list of Internet-Draft Shadow Directories can be accessed at
http://www.ietf.org/shadow.html. http://www.ietf.org/shadow.html.
This Internet-Draft will expire on January 10, 2008. This Internet-Draft will expire on February 27, 2008.
Copyright Notice Copyright Notice
Copyright (C) The IETF Trust (2007). Copyright (C) The IETF Trust (2007).
Abstract Abstract
This document describes procedures for conveying access network This document describes procedures for conveying access network
ownership and location information based on a civic and geospatial ownership and location information based on a civic and geospatial
location format in Remote Authentication Dial In User Service location format in Remote Authentication Dial In User Service
skipping to change at page 9, line 23 skipping to change at page 9, line 23
'FUTURE_REQUESTS'. This also implies the echoing of the Basic- 'FUTURE_REQUESTS'. This also implies the echoing of the Basic-
Location-Policy-Rules and Extended-Location-Policy-Rules Attributes Location-Policy-Rules and Extended-Location-Policy-Rules Attributes
received in the previous Access-Accept within the Access-Request sent received in the previous Access-Accept within the Access-Request sent
in response to the CoA-Request. in response to the CoA-Request.
Upon receiving the Access-Request message containing the Service-Type Upon receiving the Access-Request message containing the Service-Type
Attribute with a value of Authorize-Only from the NAS, the RADIUS Attribute with a value of Authorize-Only from the NAS, the RADIUS
server responds with either an Access-Accept or an Access-Reject server responds with either an Access-Accept or an Access-Reject
message. message.
RFC 3576 [RFC3576] is necessary when location information is needed [I-D.ietf-radext-rfc3576bis] is necessary when location information
on demand and cannot be obtained from accounting information in a is needed on demand and cannot be obtained from accounting
timely fashion. information in a timely fashion.
Figure 3 shows the above-described approach graphically. Figure 3 shows the above-described approach graphically.
+---------------+ +---------------+ +------+ +---------------+ +---------------+ +------+
| Dynamic | | Dynamic | |RADIUS| | Dynamic | | Dynamic | |RADIUS|
| Authorization | | Authorization | |Server| | Authorization | | Authorization | |Server|
| Server/NAS | | Client | | | | Server/NAS | | Client | | |
+---------------+ +---------------+ +------+ +---------------+ +---------------+ +------+
| | | | | |
| Access-Request | | | Access-Request | |
skipping to change at page 10, line 24 skipping to change at page 10, line 24
| + Requested-Location-Info | | | + Requested-Location-Info | |
(FUTURE_REQUESTS,...) | | (FUTURE_REQUESTS,...) | |
| + Basic-Location-Policy-Rules | | | + Basic-Location-Policy-Rules | |
| + Extended-Location-Policy-Rules | | | + Extended-Location-Policy-Rules | |
|<-----------------------------------------------------------| |<-----------------------------------------------------------|
| | | | | |
: : : : : :
: <<Some time later>> : : : <<Some time later>> : :
: : : : : :
| | | | | |
| CoA + Service-Type "Authorize Only" | | | CoA + Service-Type "Authorize Only" + State | |
|<--------------------------------------------| | |<--------------------------------------------| |
| | | | | |
| CoA NAK + Service-Type "Authorize Only" | | | CoA NAK + Service-Type "Authorize Only" | |
| + State | |
| + Error-Cause "Request Initiated" | | | + Error-Cause "Request Initiated" | |
|-------------------------------------------->| | |-------------------------------------------->| |
| | | | | |
| Access-Request | | | Access-Request | |
| + Service-Type "Authorize Only" | | | + Service-Type "Authorize Only" | |
| + State | |
| + Location-Information | | | + Location-Information | |
| + Location-Data | | | + Location-Data | |
| + Basic-Location-Policy-Rules | | | + Basic-Location-Policy-Rules | |
| + Extended-Location-Policy-Rules | | | + Extended-Location-Policy-Rules | |
|----------------------------------------------------------->| |----------------------------------------------------------->|
| Access-Accept | | | Access-Accept | |
|<-----------------------------------------------------------| |<-----------------------------------------------------------|
| | | | | |
Figure 3: Location Delivery based on CoA with Service-Type 'Authorize Figure 3: Location Delivery based on CoA with Service-Type 'Authorize
Only' Only'
When the Dynamic Authorization Client wants to change the values of When the Dynamic Authorization Client wants to change the values of
the requested location information, or set the values of the the requested location information, or set the values of the
requested location information for the first time, it may do so requested location information for the first time, it may do so
without triggering a reauthorization. Assuming that the NAS had without triggering a reauthorization. Assuming that the NAS had
previously sent an Access-Request containing a Location-Capable previously sent an Access-Request containing a Location-Capable
Attribute, the DAC can send a CoA-Request to the NAS without a Attribute, the DAC can send a CoA-Request to the NAS without a
Service-Type Attribute, but including the NAS Identifiers and Session Service-Type Attribute, but including the NAS Identifiers and Session
identifers as per RFC 3576 and the Requested-Location-Info, Basic- identifers as per [I-D.ietf-radext-rfc3576bis] and the Requested-
Location-Policy-Rules and Extended-Location-Policy-Rules Attributes. Location-Info, Basic-Location-Policy-Rules and Extended-Location-
The Requested-Location-Info, Basic-Location-Policy-Rules and Policy-Rules Attributes. The Requested-Location-Info, Basic-
Extended-Location-Policy-Rules Attributes MUST NOT be used for Location-Policy-Rules and Extended-Location-Policy-Rules Attributes
session identification. MUST NOT be used for session identification.
Figure 4 shows this approach graphically. Figure 4 shows this approach graphically.
+---------------+ +---------------+ +------+ +---------------+ +---------------+ +------+
| Dynamic | | Dynamic | |RADIUS| | Dynamic | | Dynamic | |RADIUS|
| Authorization | | Authorization | |Server| | Authorization | | Authorization | |Server|
| Server/NAS | | Client | | | | Server/NAS | | Client | | |
+---------------+ +---------------+ +------+ +---------------+ +---------------+ +------+
| | | | | |
| | | | | |
skipping to change at page 33, line 43 skipping to change at page 33, line 43
Legend: Legend:
0 This attribute MUST NOT be present. 0 This attribute MUST NOT be present.
0+ Zero or more instances of this attribute MAY be present. 0+ Zero or more instances of this attribute MAY be present.
0-1 Zero or one instance of this attribute MAY be present. 0-1 Zero or one instance of this attribute MAY be present.
1 Exactly one instance of this attribute MUST be present. 1 Exactly one instance of this attribute MUST be present.
1+ One or more of these attributes MUST be present. 1+ One or more of these attributes MUST be present.
Figure 14: Table of Attributes Figure 14: Table of Attributes
The Error-Cause Attribute is defined in [RFC3576]. The Error-Cause Attribute is defined in [I-D.ietf-radext-rfc3576bis].
The Location-Information and the Location-Data Attribute MAY appear The Location-Information and the Location-Data Attribute MAY appear
more than once. For example, if the server asks for civic and more than once. For example, if the server asks for civic and
geospatial location information two Location-Information Attributes geospatial location information two Location-Information Attributes
need to be sent. need to be sent.
The attributes defined in this document are not used in any messages The attributes defined in this document are not used in any messages
other than the onces listed in Figure 14. other than the onces listed in Figure 14.
This document requests IANA to allocate a new value from the Error- This document requests IANA to allocate a new value from the Error-
skipping to change at page 42, line 29 skipping to change at page 42, line 29
Location-Information Location-Information
Location-Data Location-Data
Basic-Location-Policy-Rules Basic-Location-Policy-Rules
Extended-Location-Policy-Rules Extended-Location-Policy-Rules
Location-Capable Location-Capable
Requested-Location-Info Requested-Location-Info
Please refer to Section 5 for the registered list of numbers. Please refer to Section 5 for the registered list of numbers.
This document also instructs IANA to assign a new value for the This document also instructs IANA to assign a new value for the
Error-Cause Attribute [RFC3576], of "Location-Info-Required" TBA. Error-Cause Attribute [I-D.ietf-radext-rfc3576bis], of "Location-
Info-Required" TBA.
Additionally, IANA is requested to create the following new Additionally, IANA is requested to create the following new
registries listed in the subsections below. registries listed in the subsections below.
8.1. New Registry: Operator Namespace Identifier 8.1. New Registry: Operator Namespace Identifier
This document also defines an operator namespace identifier registry This document also defines an operator namespace identifier registry
(used in the Namespace ID field of the Operator-Name Attribute). (used in the Namespace ID field of the Operator-Name Attribute).
Note that this document requests IANA only to maintain a registry of Note that this document requests IANA only to maintain a registry of
existing namespaces for use in this identifier field, and not to existing namespaces for use in this identifier field, and not to
skipping to change at page 50, line 28 skipping to change at page 50, line 28
RFC 2865, June 2000. RFC 2865, June 2000.
[RFC3490] Faltstrom, P., Hoffman, P., and A. Costello, [RFC3490] Faltstrom, P., Hoffman, P., and A. Costello,
"Internationalizing Domain Names in Applications (IDNA)", "Internationalizing Domain Names in Applications (IDNA)",
RFC 3490, March 2003. RFC 3490, March 2003.
[RFC3575] Aboba, B., "IANA Considerations for RADIUS (Remote [RFC3575] Aboba, B., "IANA Considerations for RADIUS (Remote
Authentication Dial In User Service)", RFC 3575, Authentication Dial In User Service)", RFC 3575,
July 2003. July 2003.
[RFC3576] Chiba, M., Dommety, G., Eklund, M., Mitton, D., and B.
Aboba, "Dynamic Authorization Extensions to Remote
Authentication Dial In User Service (RADIUS)", RFC 3576,
July 2003.
[RFC3588] Calhoun, P., Loughney, J., Guttman, E., Zorn, G., and J. [RFC3588] Calhoun, P., Loughney, J., Guttman, E., Zorn, G., and J.
Arkko, "Diameter Base Protocol", RFC 3588, September 2003. Arkko, "Diameter Base Protocol", RFC 3588, September 2003.
[RFC3825] Polk, J., Schnizlein, J., and M. Linsner, "Dynamic Host [RFC3825] Polk, J., Schnizlein, J., and M. Linsner, "Dynamic Host
Configuration Protocol Option for Coordinate-based Configuration Protocol Option for Coordinate-based
Location Configuration Information", RFC 3825, July 2004. Location Configuration Information", RFC 3825, July 2004.
[RFC4776] Schulzrinne, H., "Dynamic Host Configuration Protocol [RFC4776] Schulzrinne, H., "Dynamic Host Configuration Protocol
(DHCPv4 and DHCPv6) Option for Civic Addresses (DHCPv4 and DHCPv6) Option for Civic Addresses
Configuration Information", RFC 4776, November 2006. Configuration Information", RFC 4776, November 2006.
skipping to change at page 51, line 19 skipping to change at page 51, line 14
[I-D.ietf-geopriv-policy] [I-D.ietf-geopriv-policy]
Schulzrinne, H., "Geolocation Policy: A Document Format Schulzrinne, H., "Geolocation Policy: A Document Format
for Expressing Privacy Preferences for Location for Expressing Privacy Preferences for Location
Information", draft-ietf-geopriv-policy-12 (work in Information", draft-ietf-geopriv-policy-12 (work in
progress), May 2007. progress), May 2007.
[I-D.ietf-radext-rfc3576bis] [I-D.ietf-radext-rfc3576bis]
Chiba, M., "Dynamic Authorization Extensions to Remote Chiba, M., "Dynamic Authorization Extensions to Remote
Authentication Dial In User Service (RADIUS)", Authentication Dial In User Service (RADIUS)",
draft-ietf-radext-rfc3576bis-08 (work in progress), draft-ietf-radext-rfc3576bis-09 (work in progress),
June 2007. August 2007.
[I-D.ietf-simple-xcap] [I-D.ietf-simple-xcap]
Rosenberg, J., "The Extensible Markup Language (XML) Rosenberg, J., "The Extensible Markup Language (XML)
Configuration Access Protocol (XCAP)", Configuration Access Protocol (XCAP)",
draft-ietf-simple-xcap-12 (work in progress), draft-ietf-simple-xcap-12 (work in progress),
October 2006. October 2006.
[I-D.ietf-sip-location-conveyance] [I-D.ietf-sip-location-conveyance]
Polk, J. and B. Rosen, "Session Initiation Protocol Polk, J. and B. Rosen, "Location Conveyance for the
Location Conveyance", Session Initiation Protocol",
draft-ietf-sip-location-conveyance-07 (work in progress), draft-ietf-sip-location-conveyance-08 (work in progress),
February 2007. July 2007.
[I-D.josefsson-pppext-eap-tls-eap] [I-D.josefsson-pppext-eap-tls-eap]
Josefsson, S., Palekar, A., Simon, D., and G. Zorn, Josefsson, S., Palekar, A., Simon, D., and G. Zorn,
"Protected EAP Protocol (PEAP) Version 2", "Protected EAP Protocol (PEAP) Version 2",
draft-josefsson-pppext-eap-tls-eap-10 (work in progress), draft-josefsson-pppext-eap-tls-eap-10 (work in progress),
October 2004. October 2004.
[I-D.tschofenig-eap-ikev2] [I-D.tschofenig-eap-ikev2]
Tschofenig, H., "EAP IKEv2 Method", Tschofenig, H., "EAP IKEv2 Method",
draft-tschofenig-eap-ikev2-13 (work in progress), draft-tschofenig-eap-ikev2-13 (work in progress),
 End of changes. 14 change blocks. 
26 lines changed or deleted 26 lines changed or added

This html diff was produced by rfcdiff 1.34. The latest version is available from http://tools.ietf.org/tools/rfcdiff/