draft-ietf-geopriv-radius-lo-17.txt   draft-ietf-geopriv-radius-lo-18.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: May 21, 2008 Intel Expires: June 13, 2008 Intel
M. Jones M. Jones
A. Lior A. Lior
Bridgewater Bridgewater
November 18, 2007 B. Aboba
Microsoft Corporation
December 11, 2007
Carrying Location Objects in RADIUS and Diameter Carrying Location Objects in RADIUS and Diameter
draft-ietf-geopriv-radius-lo-17.txt draft-ietf-geopriv-radius-lo-18.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 May 21, 2008. This Internet-Draft will expire on June 13, 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 37, line 5 skipping to change at page 36, line 6
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
RFC 4005 and RFC 4072. The above-mentioned 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
[RFC3693], namely mutual end-point authentication, data object [RFC3693], namely mutual end-point authentication, data object
skipping to change at page 50, line 52 skipping to change at page 50, line 52
Specification", OGC 02-023r4, Specification", OGC 02-023r4,
http://www.opengis.org/techno/implementation.htm", , http://www.opengis.org/techno/implementation.htm", ,
January 2003. January 2003.
[GSM] "TADIG Naming Conventions, Version 4.1", GSM Association [GSM] "TADIG Naming Conventions, Version 4.1", GSM Association
Official Document TD.13", , June 2006. Official Document TD.13", , June 2006.
[I-D.funk-eap-ttls-v0] [I-D.funk-eap-ttls-v0]
Funk, P. and S. Blake-Wilson, "EAP Tunneled TLS Funk, P. and S. Blake-Wilson, "EAP Tunneled TLS
Authentication Protocol Version 0 (EAP-TTLSv0)", Authentication Protocol Version 0 (EAP-TTLSv0)",
draft-funk-eap-ttls-v0-01 (work in progress), April 2007. draft-funk-eap-ttls-v0-02 (work in progress),
November 2007.
[I-D.ietf-geopriv-policy] [I-D.ietf-geopriv-policy]
Schulzrinne, H., Tschofenig, H., Morris, J., Cuellar, J., Schulzrinne, H., Tschofenig, H., Morris, J., Cuellar, J.,
and J. Polk, "Geolocation Policy: A Document Format for and J. Polk, "Geolocation Policy: A Document Format for
Expressing Privacy Preferences for Location Information", Expressing Privacy Preferences for Location Information",
draft-ietf-geopriv-policy-13 (work in progress), draft-ietf-geopriv-policy-13 (work in progress),
October 2007. October 2007.
[I-D.ietf-radext-rfc3576bis] [I-D.ietf-radext-rfc3576bis]
Chiba, M., Dommety, G., Eklund, M., Mitton, D., and B. Chiba, M., Dommety, G., Eklund, M., Mitton, D., and B.
skipping to change at page 51, line 28 skipping to change at page 51, line 29
[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, "Location Conveyance for the Polk, J. and B. Rosen, "Location Conveyance for the
Session Initiation Protocol", Session Initiation Protocol",
draft-ietf-sip-location-conveyance-08 (work in progress), draft-ietf-sip-location-conveyance-09 (work in progress),
July 2007. November 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., Kroeselberg, D., Pashalidis, A., Ohba, Y., Tschofenig, H., Kroeselberg, D., Pashalidis, A., Ohba, Y.,
and F. Bersani, "EAP-IKEv2 Method", and F. Bersani, "EAP-IKEv2 Method",
 End of changes. 7 change blocks. 
7 lines changed or deleted 14 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/