draft-ietf-geopriv-radius-lo-23.txt   draft-ietf-geopriv-radius-lo-24.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: September 10, 2009 Intel Expires: November 8, 2009 Intel
M. Jones M. Jones
A. Lior A. Lior
Bridgewater Bridgewater
B. Aboba B. Aboba
Microsoft Corporation Microsoft Corporation
March 9, 2009 May 7, 2009
Carrying Location Objects in RADIUS and Diameter Carrying Location Objects in RADIUS and Diameter
draft-ietf-geopriv-radius-lo-23.txt draft-ietf-geopriv-radius-lo-24.txt
Status of this Memo Status of this Memo
This Internet-Draft is submitted to IETF in full conformance with the This Internet-Draft is submitted to IETF in full conformance with the
provisions of BCP 78 and BCP 79. provisions of BCP 78 and 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
other groups may also distribute working documents as Internet- other groups may also distribute working documents as Internet-
Drafts. Drafts.
skipping to change at page 1, line 38 skipping to change at page 1, line 38
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 September 10, 2009. This Internet-Draft will expire on November 8, 2009.
Copyright Notice Copyright Notice
Copyright (c) 2009 IETF Trust and the persons identified as the Copyright (c) 2009 IETF Trust and the persons identified as the
document authors. All rights reserved. document authors. All rights reserved.
This document is subject to BCP 78 and the IETF Trust's Legal This document is subject to BCP 78 and the IETF Trust's Legal
Provisions Relating to IETF Documents in effect on the date of Provisions Relating to IETF Documents in effect on the date of
publication of this document (http://trustee.ietf.org/license-info). publication of this document (http://trustee.ietf.org/license-info).
Please review these documents carefully, as they describe your rights Please review these documents carefully, as they describe your rights
skipping to change at page 3, line 17 skipping to change at page 3, line 17
1. Introduction . . . . . . . . . . . . . . . . . . . . . . . . . 4 1. Introduction . . . . . . . . . . . . . . . . . . . . . . . . . 4
2. Terminology . . . . . . . . . . . . . . . . . . . . . . . . . 5 2. Terminology . . . . . . . . . . . . . . . . . . . . . . . . . 5
3. Delivery Methods for Location Information . . . . . . . . . . 6 3. Delivery Methods for Location Information . . . . . . . . . . 6
3.1. Location Delivery based on Out-of-Band Agreements . . . . 6 3.1. Location Delivery based on Out-of-Band Agreements . . . . 6
3.2. Location Delivery based on Initial Request . . . . . . . . 7 3.2. Location Delivery based on Initial Request . . . . . . . . 7
3.3. Location Delivery based on Mid-Session Request . . . . . . 8 3.3. Location Delivery based on Mid-Session Request . . . . . . 8
3.4. Location Delivery in Accounting Messages . . . . . . . . . 12 3.4. Location Delivery in Accounting Messages . . . . . . . . . 12
4. Attributes . . . . . . . . . . . . . . . . . . . . . . . . . . 14 4. Attributes . . . . . . . . . . . . . . . . . . . . . . . . . . 14
4.1. Operator-Name Attribute . . . . . . . . . . . . . . . . . 14 4.1. Operator-Name Attribute . . . . . . . . . . . . . . . . . 14
4.2. Location-Information Attribute . . . . . . . . . . . . . . 17 4.2. Location-Information Attribute . . . . . . . . . . . . . . 17
4.3. Location-Data Attribute . . . . . . . . . . . . . . . . . 20 4.3. Location-Data Attribute . . . . . . . . . . . . . . . . . 19
4.3.1. Civic Location Profile . . . . . . . . . . . . . . . . 21 4.3.1. Civic Location Profile . . . . . . . . . . . . . . . . 20
4.3.2. Geospatial Location Profile . . . . . . . . . . . . . 22 4.3.2. Geospatial Location Profile . . . . . . . . . . . . . 21
4.4. Basic-Location-Policy-Rules Attribute . . . . . . . . . . 22 4.4. Basic-Location-Policy-Rules Attribute . . . . . . . . . . 21
4.5. Extended-Location-Policy-Rules Attribute . . . . . . . . . 24 4.5. Extended-Location-Policy-Rules Attribute . . . . . . . . . 23
4.6. Location-Capable Attribute . . . . . . . . . . . . . . . . 26 4.6. Location-Capable Attribute . . . . . . . . . . . . . . . . 25
4.7. Requested-Location-Info Attribute . . . . . . . . . . . . 29 4.7. Requested-Location-Info Attribute . . . . . . . . . . . . 28
5. Table of Attributes . . . . . . . . . . . . . . . . . . . . . 35 5. Table of Attributes . . . . . . . . . . . . . . . . . . . . . 34
6. Diameter RADIUS Interoperability . . . . . . . . . . . . . . . 37 6. Diameter RADIUS Interoperability . . . . . . . . . . . . . . . 36
7. Security Considerations . . . . . . . . . . . . . . . . . . . 39 7. Security Considerations . . . . . . . . . . . . . . . . . . . 38
7.1. Communication Security . . . . . . . . . . . . . . . . . . 39 7.1. Communication Security . . . . . . . . . . . . . . . . . . 38
7.2. Privacy Considerations . . . . . . . . . . . . . . . . . . 40 7.2. Privacy Considerations . . . . . . . . . . . . . . . . . . 39
7.2.1. RADIUS Client . . . . . . . . . . . . . . . . . . . . 41 7.2.1. RADIUS Client . . . . . . . . . . . . . . . . . . . . 40
7.2.2. RADIUS Server . . . . . . . . . . . . . . . . . . . . 41 7.2.2. RADIUS Server . . . . . . . . . . . . . . . . . . . . 40
7.2.3. RADIUS Proxy . . . . . . . . . . . . . . . . . . . . . 42 7.2.3. RADIUS Proxy . . . . . . . . . . . . . . . . . . . . . 41
7.3. Identity Information and Location Information . . . . . . 42 7.3. Identity Information and Location Information . . . . . . 41
8. IANA Considerations . . . . . . . . . . . . . . . . . . . . . 44 8. IANA Considerations . . . . . . . . . . . . . . . . . . . . . 43
8.1. New Registry: Operator Namespace Identifier . . . . . . . 44 8.1. New Registry: Operator Namespace Identifier . . . . . . . 43
8.2. New Registry: Location Profiles . . . . . . . . . . . . . 45 8.2. New Registry: Location Profiles . . . . . . . . . . . . . 44
8.3. New Registry: Location-Capable Attribute . . . . . . . . . 46 8.3. New Registry: Location-Capable Attribute . . . . . . . . . 45
8.4. New Registry: Entity Types . . . . . . . . . . . . . . . . 47 8.4. New Registry: Entity Types . . . . . . . . . . . . . . . . 46
8.5. New Registry: Privacy Flags . . . . . . . . . . . . . . . 47 8.5. New Registry: Privacy Flags . . . . . . . . . . . . . . . 46
8.6. New Registry: Requested-Location-Info Attribute . . . . . 47 8.6. New Registry: Requested-Location-Info Attribute . . . . . 46
9. Acknowledgments . . . . . . . . . . . . . . . . . . . . . . . 49 9. Acknowledgments . . . . . . . . . . . . . . . . . . . . . . . 48
10. References . . . . . . . . . . . . . . . . . . . . . . . . . . 50 10. References . . . . . . . . . . . . . . . . . . . . . . . . . . 50
10.1. Normative References . . . . . . . . . . . . . . . . . . . 50 10.1. Normative References . . . . . . . . . . . . . . . . . . . 50
10.2. Informative References . . . . . . . . . . . . . . . . . . 50 10.2. Informative References . . . . . . . . . . . . . . . . . . 50
Appendix A. Matching with Geopriv Requirements . . . . . . . . . 53 Appendix A. Matching with Geopriv Requirements . . . . . . . . . 53
A.1. Distribution of Location Information at the User's A.1. Distribution of Location Information at the User's
Home Network . . . . . . . . . . . . . . . . . . . . . . . 53 Home Network . . . . . . . . . . . . . . . . . . . . . . . 53
A.2. Distribution of Location Information at the Visited A.2. Distribution of Location Information at the Visited
Network . . . . . . . . . . . . . . . . . . . . . . . . . 54 Network . . . . . . . . . . . . . . . . . . . . . . . . . 54
A.3. Requirements matching . . . . . . . . . . . . . . . . . . 55 A.3. Requirements matching . . . . . . . . . . . . . . . . . . 55
Authors' Addresses . . . . . . . . . . . . . . . . . . . . . . . . 61 Authors' Addresses . . . . . . . . . . . . . . . . . . . . . . . . 61
skipping to change at page 15, line 19 skipping to change at page 15, line 19
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| Text (cont.) ... | Text (cont.) ...
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
Type: Type:
To Be Assigned by IANA - Operator-Name To Be Assigned by IANA - Operator-Name
Length: Length:
>= 5 >= 4
Text: Text:
This field is at least two octets in length, and the format The format is shown below. The data type of this field is
is shown below. The data type of this field is text. string. All fields are transmitted from left to right:
All fields are transmitted from left to right:
0 1 2 3 0 1 2 3
0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1 0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| Namespace ID | Operator-Name ... | Namespace ID | Operator-Name ...
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| Operator-Name ... | Operator-Name ...
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
Namespace ID: Namespace ID:
skipping to change at page 16, line 9 skipping to change at page 16, line 8
The Namespace ID field provides information about the operator The Namespace ID field provides information about the operator
namespace. This document defines four values for this attribute that namespace. This document defines four values for this attribute that
are listed below. Additional namespace identifiers must be are listed below. Additional namespace identifiers must be
registered with IANA (see Section 8.1) and must be associated with an registered with IANA (see Section 8.1) and must be associated with an
organization responsible for managing the namespace. organization responsible for managing the namespace.
TADIG ('0' (0x30)): TADIG ('0' (0x30)):
This namespace can be used to indicate operator names based on This namespace can be used to indicate operator names based on
Transferred Account Data Interchange Group (TADIG) codes defined Transferred Account Data Interchange Group (TADIG) codes, as
in [GSM]. TADIG codes are assigned by the TADIG Working Group defined in [GSM]. TADIG codes are assigned by the TADIG Working
within the GSM Association. The TADIG Code consists of two Group within the GSM Association. The TADIG Code consists of two
fields, with a total length of five ASCII characters consisting of fields, with a total length of five ASCII characters consisting of
a three-character country code and a two-character alphanumeric a three-character country code and a two-character alphanumeric
operator (or company) ID. operator (or company) ID.
REALM ('1' (0x31)): REALM ('1' (0x31)):
The REALM operator namespace can be used to indicate operator The REALM operator namespace can be used to indicate operator
names based on any registered domain name. Such names are names based on any registered domain name. Such names are
required to be unique and the rights to use a given realm name are required to be unique and the rights to use a given realm name are
obtained coincident with acquiring the rights to use a particular obtained coincident with acquiring the rights to use a particular
skipping to change at page 16, line 46 skipping to change at page 16, line 45
ICC ('3' (0x33)): ICC ('3' (0x33)):
The ICC namespace can be used to indicate operator names based on The ICC namespace can be used to indicate operator names based on
International Telecommunication Union (ITU) Carrier Codes (ICC) International Telecommunication Union (ITU) Carrier Codes (ICC)
defined in [ITU1400]. ICC values are assigned by national defined in [ITU1400]. ICC values are assigned by national
regulatory authorities and are coordinated by the regulatory authorities and are coordinated by the
Telecommunication Standardization Bureau (TSB) within the ITU Telecommunication Standardization Bureau (TSB) within the ITU
Telecommunication Standardization Sector (ITU-T). When using the Telecommunication Standardization Sector (ITU-T). When using the
ICC namespace, the attribute consists of three uppercase ASCII ICC namespace, the attribute consists of three uppercase ASCII
characters containing a three-letter alphabetic country code as characters containing a three-letter alphabetic country code, as
defined in [ISO], followed by one to six uppercase alphanumeric defined in [ISO], followed by one to six uppercase alphanumeric
ASCII characters containing the ICC itself. ASCII characters containing the ICC itself.
4.2. Location-Information Attribute 4.2. Location-Information Attribute
The Location-Information Attribute MAY be sent in Access-Request and The Location-Information Attribute MAY be sent in Access-Request and
in Accounting-Request messages. For the Accounting-Request message in Accounting-Request messages. For the Accounting-Request message
the Acc-Status-Type may be set to Start, Interim or Stop. the Acc-Status-Type may be set to Start, Interim or Stop.
The Location-Information Attribute provides meta-data about the The Location-Information Attribute provides meta-data about the
skipping to change at page 18, line 19 skipping to change at page 17, line 31
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| String (cont.) ... | String (cont.) ...
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
Type: Type:
To Be Assigned by IANA - Location-Information To Be Assigned by IANA - Location-Information
Length: Length:
>= 21 >= 23
String: String:
This field is at least 19 octets in length, and the format The format is shown below. The data type of this field is
is shown below. The data type of this field is string. string. All fields are transmitted from left to right:
The fields are transmitted from left to right:
0 1 2 3 0 1 2 3
0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1 0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| Index | Code | Entity | | Index | Code | Entity |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| Sighting Time ~ | Sighting Time ~
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| Sighting Time | | Sighting Time |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
skipping to change at page 21, line 19 skipping to change at page 20, line 19
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| String (cont.) ... | String (cont.) ...
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
Type: Type:
To Be Assigned by IANA - Location-Data To Be Assigned by IANA - Location-Data
Length: Length:
>= 21 >= 5
String: String:
This field is at least two octets in length, and the format The format is shown below. The data type of this field is
is shown below. The data type of this field is string. string. All fields are transmitted from left to right:
All fields are transmitted from left to right:
0 1 2 3 0 1 2 3
0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1 0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| Index | Location ... | Index | Location ...
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| Location ... | Location ...
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
Index (16 bits): Index (16 bits):
skipping to change at page 23, line 23 skipping to change at page 22, line 23
Type: Type:
To Be Assigned by IANA - Basic-Location-Policy-Rules To Be Assigned by IANA - Basic-Location-Policy-Rules
Length: Length:
>= 12 >= 12
String: String:
This field is at least 8 octets in length, and the format The format is shown below. The data type of this field is
is shown below. The data type of this field is string. string. All fields are transmitted from left to right:
All fields are transmitted from left to right:
0 1 2 3 0 1 2 3
0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1 0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| Flags | Retention Expires ... | Flags | Retention Expires ...
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| Retention Expires ... | Retention Expires ...
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| Retention Expires | Note Well ... | Retention Expires | Note Well ...
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| Note Well ... | Note Well ...
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
This document reuses fields of the RFC 4119 [RFC4119] 'usage-rules' This document reuses fields of the RFC 4119 [RFC4119] 'usage-rules'
element. These fields have the following meaning: element. These fields have the following meaning:
Flag (16 bits): Flags (16 bits):
The Flag' field is a bit mask and only the first bit (R) is The Flags field is a bit mask and only the first bit (R) is
defined in this document and corresponds to the retransmission- defined in this document and corresponds to the retransmission-
allowed field: allowed field:
0 1 0 1
0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
|R|o o o o o o o o o o o o o o o| |R|o o o o o o o o o o o o o o o|
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
R = retransmission-allowed R = retransmission-allowed
skipping to change at page 24, line 42 skipping to change at page 23, line 42
instructions. The data type of this field is string. This field instructions. The data type of this field is string. This field
is useful when location information is distributed to third party is useful when location information is distributed to third party
entities, which can include humans in a location based service. entities, which can include humans in a location based service.
RADIUS entities are not supposed to process this field. RADIUS entities are not supposed to process this field.
Whenever a Location Object leaves the RADIUS eco-system the URI in Whenever a Location Object leaves the RADIUS eco-system the URI in
the note-well attribute MUST be expanded to the human readable the note-well attribute MUST be expanded to the human readable
text. For example, when the Location Object is transferred to a text. For example, when the Location Object is transferred to a
SIP based environment then the human readable text is placed into SIP based environment then the human readable text is placed into
the 'note-well' element of the 'usage-rules' element contained in the 'note-well' element of the 'usage-rules' element contained in
the PIDF-LO document (see [RFC4119]). the PIDF-LO document (see [RFC4119]). The note-well field may be
empty.
4.5. Extended-Location-Policy-Rules Attribute 4.5. Extended-Location-Policy-Rules Attribute
The Extended-Location-Policy-Rules Attribute MAY be sent in an The Extended-Location-Policy-Rules Attribute MAY be sent in an
Access-Request, an Access-Accept, an Access-Challenge, an Access- Access-Request, an Access-Accept, an Access-Challenge, an Access-
Reject, an Change-of-Authorization and in an Accounting-Request Reject, an Change-of-Authorization and in an Accounting-Request
message. message.
The ruleset reference field of this attribute is of variable length. The ruleset reference field of this attribute is of variable length.
It contains a URI that indicates where the richer ruleset can be It contains a URI that indicates where the richer ruleset can be
skipping to change at page 26, line 19 skipping to change at page 25, line 19
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| String (cont.) ... | String (cont.) ...
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
Type: Type:
To Be Assigned by IANA - Extended-Location-Policy-Rules To Be Assigned by IANA - Extended-Location-Policy-Rules
Length: Length:
>= 4 >= 3
String: String:
This field is at least two octets in length, and the format This field is at least two octets in length, and the format
is shown below. The data type of this field is string. is shown below. The data type of this field is string.
The fields are transmitted from left to right: The fields are transmitted from left to right:
0 1 2 3 0 1 2 3
0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1 0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
skipping to change at page 27, line 23 skipping to change at page 26, line 23
Type: Type:
To Be Assigned by IANA - Location-Capable Attribute To Be Assigned by IANA - Location-Capable Attribute
Length: Length:
6 6
Integer: Integer:
This field is a 32-bit integer value. The content of the Integer field encodes the
requested capabilities.
Each capability value represents a bit position.
This document specifies the following capabilities: This document specifies the following capabilities:
Name: Name:
CIVIC_LOCATION CIVIC_LOCATION
Description: Description:
The RADIUS client uses the CIVIC_LOCATION to indicate that it is The RADIUS client uses the CIVIC_LOCATION to indicate that it is
skipping to change at page 30, line 15 skipping to change at page 29, line 20
computing an authorization decision. computing an authorization decision.
+---------+ +---------+ +---------+ +---------+
| RADIUS | | RADIUS | | RADIUS | | RADIUS |
| Client | | Server | | Client | | Server |
+---------+ +---------+ +---------+ +---------+
| | | |
| | | |
| Access-Request | | Access-Request |
| + Location-Capable | | + Location-Capable |
| ('CIVIC_LOCATION', |
| 'GEO_LOCATION', |
| 'NAS_LOCATION', |
| 'USERS_LOCATION') |
|--------------------------------->| |--------------------------------->|
| | | |
| Access-Challenge | | Access-Challenge |
| + Requested-Location-Info | | + Requested-Location-Info |
| ('CIVIC_LOCATION', | | ('CIVIC_LOCATION', |
| 'USERS_LOCATION') | | 'USERS_LOCATION') |
| + Basic-Location-Policy-Rules | | + Basic-Location-Policy-Rules |
| + Extended-Location-Policy-Rules | | + Extended-Location-Policy-Rules |
|<---------------------------------| |<---------------------------------|
| | | |
skipping to change at page 35, line 12 skipping to change at page 34, line 12
and the users' client device are returned in a geospatial location and the users' client device are returned in a geospatial location
format. format.
5. Table of Attributes 5. Table of Attributes
The following table provides a guide which attributes may be found in The following table provides a guide which attributes may be found in
which RADIUS messages, and in what quantity. which RADIUS messages, and in what quantity.
Request Accept Reject Challenge Accounting # Attribute Request Accept Reject Challenge Accounting # Attribute
Request Request
0-1 0 0 0 0-1 TBD Operator-Name 0-1 0-1 0 0 0+ TBD Operator-Name
0+ 0 0 0 0+ TBD Location-Information 0+ 0 0 0 0+ TBD Location-Information
0+ 0 0 0 0+ TBD Location-Data 0+ 0 0 0 0+ TBD Location-Data
0-1 0-1 0-1 0-1 0-1 TBD Basic-Location- 0-1 0-1 0-1 0-1 0-1 TBD Basic-Location-
Policy-Rules Policy-Rules
0-1 0-1 0-1 0-1 0-1 TBD Extended-Location- 0-1 0-1 0-1 0-1 0-1 TBD Extended-Location-
Policy-Rules Policy-Rules
0 0-1 0 0-1 0 TBD Requested-Location-Info 0 0-1 0 0-1 0 TBD Requested-Location-Info
0-1 0 0 0 0 TBD Location-Capable 0-1 0 0 0 0 TBD Location-Capable
0 0 0-1 0 0 101 Error-Cause [note1] 0 0 0-1 0 0 101 Error-Cause [note1]
skipping to change at page 37, line 10 skipping to change at page 36, line 10
other than the ones listed in Figure 7. other than the ones listed in Figure 7.
This document requests IANA to allocate a new value from the Error- This document requests IANA to allocate a new value from the Error-
Cause registry with the semantic of 'Location-Info-Required'. Cause registry with the semantic of 'Location-Info-Required'.
6. Diameter RADIUS Interoperability 6. Diameter RADIUS Interoperability
When used in Diameter, the attributes defined in this specification When used in Diameter, the attributes defined in this specification
can be used as Diameter AVPs from the Code space 1-255 (RADIUS can be used as Diameter AVPs from the Code space 1-255 (RADIUS
attribute compatibility space). No additional Diameter Code values attribute compatibility space). No additional Diameter Code values
are therefore allocated. The data types and flag rules for the are therefore allocated. The data types and flag rules, as defined
attributes are as follows: in [RFC3588], for the Diameter AVPs are as follows:
+---------------------+ +---------------------+
| AVP Flag rules | | AVP Flag rules |
+----+-----+------+-----+----+ +----+-----+------+-----+----+
| | |SHOULD| MUST| | | | |SHOULD| MUST| |
Attribute Name Value Type |MUST| MAY | NOT | NOT|Encr| Attribute Name Value Type |MUST| MAY | NOT | NOT|Encr|
+---------------------------------+----+-----+------+-----+----+ +---------------------------------+----+-----+------+-----+----+
|Operator-Name OctetString| | P | | V,M | Y | |Operator-Name OctetString| | P | | V,M | Y |
|Location-Information OctetString| | P | | V,M | Y | |Location-Information OctetString| | P | | V,M | Y |
|Location-Data OctetString| | P | | V,M | Y | |Location-Data OctetString| | P | | V,M | Y |
|Basic-Location- | | | | | | |Basic-Location- | | | | | |
| Policy-Rules OctetString| | P | | V,M | Y | | Policy-Rules OctetString| | P | | V,M | Y |
|Extended-Location- | | | | | | |Extended-Location- | | | | | |
| Policy-Rules OctetString| | P | | V,M | Y | | Policy-Rules OctetString| | P | | V,M | Y |
|Requested- | | | | | | |Requested- | | | | | |
| Location-Info OctetString| | P | | V,M | Y | | Location-Info OctetString| | P | | V,M | Y |
|Location-Capable OctetString| | P | | V,M | Y | |Location-Capable OctetString| | P | | V,M | Y |
+---------------------------------+----+-----+------+-----+----+ +---------------------------------+----+-----+------+-----+----+
The attributes in this specification have no special translation The RADIUS attributes in this specification have no special
requirements for Diameter to RADIUS or RADIUS to Diameter gateways; translation requirements for Diameter to RADIUS or RADIUS to Diameter
they are copied as is, except for changes relating to headers, gateways; they are copied as is, except for changes relating to
alignment, and padding. See also Section 4.1 of [RFC3588] and headers, alignment, and padding. See also Section 4.1 of [RFC3588]
Section 9 of [RFC4005]. and Section 9 of [RFC4005].
What this specification says about the applicability of the What this specification says about the applicability of the
attributes for RADIUS Access-Request packets applies in Diameter to attributes for RADIUS Access-Request packets applies in Diameter to
AA-Request [RFC4005] or Diameter-EAP-Request [RFC4072]. What is said AA-Request [RFC4005] or Diameter-EAP-Request [RFC4072]. What is said
about Access-Challenge applies in Diameter to AA-Answer [RFC4005] or about Access-Challenge applies in Diameter to AA-Answer [RFC4005] or
Diameter-EAP-Answer [RFC4072] with Result-Code AVP set to Diameter-EAP-Answer [RFC4072] with Result-Code AVP set to
DIAMETER_MULTI_ROUND_AUTH. What is said about Access-Accept applies DIAMETER_MULTI_ROUND_AUTH. What is said about Access-Accept applies
in Diameter to AA-Answer or Diameter-EAP-Answer messages that in Diameter to AA-Answer or Diameter-EAP-Answer messages that
indicate success. Similarly, what is said about RADIUS Access-Reject indicate success. Similarly, what is said about RADIUS Access-Reject
packets applies in Diameter to AA-Answer or Diameter-EAP-Answer packets applies in Diameter to AA-Answer or Diameter-EAP-Answer
messages that indicate failure. messages that indicate failure.
What is said about CoA-Request applies in Diameter to Re-Auth-Request What is said about CoA-Request applies in Diameter to Re-Auth-Request
[RFC4005]. [RFC4005].
What is said about Accounting-Request applies to Diameter Accounting- What is said about Accounting-Request applies to Diameter Accounting-
Request [RFC4005] as well. Request [RFC4005] as well.
Note that these AVPs may be used by Diameter applications other than Note that these AVPs may be used by Diameter applications other than
RFC 4005 and RFC 4072. The above-mentioned applications are, RFC 4005 [RFC4005] and RFC 4072 [RFC4072]. The above-mentioned
however, likely to be relevant in the context of this document. applications are, however, likely to be relevant in the context of
this document.
7. Security Considerations 7. Security Considerations
A number of security aspects are relevant for the distribution of A number of security aspects are relevant for the distribution of
location information via RADIUS. These aspects are discussed in location information via RADIUS. These aspects are discussed in
separate sub-sections. separate sub-sections.
7.1. Communication Security 7.1. Communication Security
Requirements for the protection of a Location Object are defined in Requirements for the protection of a Location Object are defined in
skipping to change at page 49, line 19 skipping to change at page 48, line 19
Black, Paul Congdon, Jouni Korhonen, Sami Ala-luukko, Farooq Bari, Ed Black, Paul Congdon, Jouni Korhonen, Sami Ala-luukko, Farooq Bari, Ed
Van Horne, Mark Grayson, Jukka Tuomi, Jorge Cuellar, and Christian Van Horne, Mark Grayson, Jukka Tuomi, Jorge Cuellar, and Christian
Guenther. Guenther.
Henning Schulzrinne provided the civic location information content Henning Schulzrinne provided the civic location information content
found in this draft. The geospatial location information format is found in this draft. The geospatial location information format is
based on work done by James Polk, John Schnizlein and Marc Linsner. based on work done by James Polk, John Schnizlein and Marc Linsner.
The authorization policy format is based on the work done by Jon The authorization policy format is based on the work done by Jon
Peterson. Peterson.
The authors would like to thank Victor Lortz, Jose Puthenkulam, The authors would like to thank Victor Lortz, Anthony Leibovitz, Jose
Bernrad Aboba, Jari Arkko, Parviz Yegani, Serge Manning, Kuntal Puthenkulam, Bernrad Aboba, Jari Arkko, Parviz Yegani, Serge Manning,
Chowdury, Pasi Eronen, Blair Bullock and Eugene Chang for their Kuntal Chowdury, Pasi Eronen, Blair Bullock and Eugene Chang for
feedback to an initial version of this draft. We would like to thank their feedback to an initial version of this draft. We would like to
Jari Arkko for his text contributions. Lionel Morand provided thank Jari Arkko for his text contributions. Lionel Morand provided
detailed feedback on numerous issues. His comments helped to improve detailed feedback on numerous issues. His comments helped to improve
the quality of this document. Jouni Korhonen, Victor Fajardo, Tolga the quality of this document. Jouni Korhonen, Victor Fajardo, Tolga
Asveren and John Loughney helped us with the Diameter RADIUS Asveren and John Loughney helped us with the Diameter RADIUS
interoperability section. Andreas Pashalidis reviewed a later interoperability section. Andreas Pashalidis reviewed a later
version document and provided a number of comments. Alan DeKok, version document and provided a number of comments. Alan DeKok,
Lionel Morand, Jouni Korhonen, David Nelson and Emile van Bergen Lionel Morand, Jouni Korhonen, David Nelson and Emile van Bergen
provided guidance on the Requested-Location-Info Attribute and provided guidance on the Requested-Location-Info Attribute and
participated in the capability exchange discussions. Allison Mankin, participated in the capability exchange discussions. Allison Mankin,
Jouni Korhonen and Pasi Eronen provided text for the operator Jouni Korhonen and Pasi Eronen provided text for the operator
namespace identifier registry. Jouni Korhonen interacted with the namespace identifier registry. Jouni Korhonen interacted with the
skipping to change at page 49, line 45 skipping to change at page 48, line 45
Scott Bradner consulted the ITU-T to find a contact person for the Scott Bradner consulted the ITU-T to find a contact person for the
E212 and the ICC operator namespace. E212 and the ICC operator namespace.
This document is based on the discussions within the IETF GEOPRIV This document is based on the discussions within the IETF GEOPRIV
working group. Therefore, the authors thank Henning Schulzrinne, working group. Therefore, the authors thank Henning Schulzrinne,
James Polk, John Morris, Allison Mankin, Randall Gellens, Andrew James Polk, John Morris, Allison Mankin, Randall Gellens, Andrew
Newton, Ted Hardie, Jon Peterson for their time to discuss a number Newton, Ted Hardie, Jon Peterson for their time to discuss a number
of issues with us. We thank Stephen Hayes for aligning this work of issues with us. We thank Stephen Hayes for aligning this work
with 3GPP activities. with 3GPP activities.
We would like to thank members of the Wimax Forum Global Roaming
Working Group (GRWG) for their feedback on the Operator-Name
attribute. Ray Jong Kiem helped us with his detailed description to
correct the document.
The RADEXT working group chairs, David Nelson and Bernard Aboba, The RADEXT working group chairs, David Nelson and Bernard Aboba,
provided several draft reviews and we would like to thank them for provided several draft reviews and we would like to thank them for
the help and their patience. the help and their patience.
Finally, we would like to thank Dan Romascanu, Glen Zorn, Russ Finally, we would like to thank Dan Romascanu, Glen Zorn, Russ
Housley, Jari Arkko, Tim Polk, and Lars Eggert for the IETF Last Call Housley, Jari Arkko, Ralph Droms, Adrial Farrel, Tim Polk, and Lars
comments, Derek Atkins for his security area directorate review and Eggert for the IETF Last Call comments, Derek Atkins for his security
Yoshiko Chong for spotting a bug in the IANA consideration section. area directorate review and Yoshiko Chong for spotting a bug in the
IANA consideration section.
10. References 10. References
10.1. Normative References 10.1. Normative References
[RFC2119] Bradner, S., "Key words for use in RFCs to Indicate [RFC2119] Bradner, S., "Key words for use in RFCs to Indicate
Requirement Levels", BCP 14, RFC 2119, March 1997. Requirement Levels", BCP 14, RFC 2119, March 1997.
[RFC2434] Narten, T. and H. Alvestrand, "Guidelines for Writing an [RFC2434] Narten, T. and H. Alvestrand, "Guidelines for Writing an
IANA Considerations Section in RFCs", BCP 26, RFC 2434, IANA Considerations Section in RFCs", BCP 26, RFC 2434,
 End of changes. 27 change blocks. 
70 lines changed or deleted 80 lines changed or added

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