draft-ietf-geopriv-lbyr-requirements-04.txt   draft-ietf-geopriv-lbyr-requirements-05.txt 
GeoPriv R. Marshall, Ed. GeoPriv R. Marshall, Ed.
Internet-Draft TCS Internet-Draft TCS
Intended status: Informational November 3, 2008 Intended status: Informational November 28, 2008
Expires: May 7, 2009 Expires: June 1, 2009
Requirements for a Location-by-Reference Mechanism Requirements for a Location-by-Reference Mechanism
draft-ietf-geopriv-lbyr-requirements-04 draft-ietf-geopriv-lbyr-requirements-05
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 34 skipping to change at page 1, line 34
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 7, 2009. This Internet-Draft will expire on June 1, 2009.
Abstract Abstract
This document defines terminology and provides requirements relating This document defines terminology and provides requirements relating
to Location-by-Reference approach using a location URI to handle to Location-by-Reference approach using a location URI to handle
location information within signaling and other Internet messaging. location information within signaling and other Internet messaging.
Table of Contents Table of Contents
1. Introduction . . . . . . . . . . . . . . . . . . . . . . . . . 3 1. Introduction . . . . . . . . . . . . . . . . . . . . . . . . . 3
skipping to change at page 17, line 7 skipping to change at page 17, line 7
of the Target. This kind of threat may be mitigated somewhat by of the Target. This kind of threat may be mitigated somewhat by
introducing another layer of indirection: namely the use of a introducing another layer of indirection: namely the use of a
(remote) presence server. (remote) presence server.
6. IANA Considerations 6. IANA Considerations
This document does not require actions by the IANA. This document does not require actions by the IANA.
7. Acknowledgements 7. Acknowledgements
I would like to thank the present IETF GEOPRIV working group chair I would like to thank the present IETF GEOPRIV working group chairs,
for their continued support in progressing this document along, as Robert Sparks and Richard Barnes for their continued support in
well, I wish to thank past chairs, Andy Newton, Allison Mankin and progressing this document along, as well, I wish to thank past
Randall Gellens, for creating the design team which initiated this chairs, Andy Newton, Allison Mankin and Randall Gellens, for creating
requirements work. I'd also like to thank those original design team the design team which initiated this requirements work. I'd also
participants for their inputs, comments, and insightful reviews. The like to thank those original design team participants for their
design team included the following folks: Richard Barnes; Martin inputs, comments, and insightful reviews. The design team included
Dawson; Keith Drage; Randall Gellens; Ted Hardie; Cullen Jennings; the following folks: Richard Barnes; Martin Dawson; Keith Drage;
Marc Linsner; Rohan Mahy; Allison Mankin; Roger Marshall; Andrew Randall Gellens; Ted Hardie; Cullen Jennings; Marc Linsner; Rohan
Newton; Jon Peterson; James M. Polk; Brian Rosen; John Schnizlein; Mahy; Allison Mankin; Roger Marshall; Andrew Newton; Jon Peterson;
Henning Schulzrinne; Barbara Stark; Hannes Tschofenig; Martin James M. Polk; Brian Rosen; John Schnizlein; Henning Schulzrinne;
Thomson; and James Winterbottom. Barbara Stark; Hannes Tschofenig; Martin Thomson; and James
Winterbottom.
8. References 8. References
8.1. Normative References 8.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.
8.2. Informative References 8.2. Informative References
skipping to change at page 18, line 30 skipping to change at page 18, line 30
[I-D.ietf-geopriv-l7-lcp-ps] [I-D.ietf-geopriv-l7-lcp-ps]
Tschofenig, H. and H. Schulzrinne, "GEOPRIV Layer 7 Tschofenig, H. and H. Schulzrinne, "GEOPRIV Layer 7
Location Configuration Protocol; Problem Statement and Location Configuration Protocol; Problem Statement and
Requirements", draft-ietf-geopriv-l7-lcp-ps-08 (work in Requirements", draft-ietf-geopriv-l7-lcp-ps-08 (work in
progress), June 2008. progress), June 2008.
[I-D.ietf-geopriv-loc-filters] [I-D.ietf-geopriv-loc-filters]
Mahy, R. and B. Rosen, "A Document Format for Filtering Mahy, R. and B. Rosen, "A Document Format for Filtering
and Reporting Location Notications in the Presence and Reporting Location Notications in the Presence
Information Document Format Location Object (PIDF-LO)", Information Document Format Location Object (PIDF-LO)",
draft-ietf-geopriv-loc-filters-02 (work in progress), draft-ietf-geopriv-loc-filters-03 (work in progress),
July 2008. November 2008.
[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-17 (work in progress), draft-ietf-geopriv-policy-17 (work in progress),
June 2008. June 2008.
[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-11 (work in progress), draft-ietf-sip-location-conveyance-12 (work in progress),
October 2008. November 2008.
[RFC3693] Cuellar, J., Morris, J., Mulligan, D., Peterson, J., and [RFC3693] Cuellar, J., Morris, J., Mulligan, D., Peterson, J., and
J. Polk, "Geopriv Requirements", RFC 3693, February 2004. J. Polk, "Geopriv Requirements", RFC 3693, February 2004.
[RFC4119] Peterson, J., "A Presence-based GEOPRIV Location Object [RFC4119] Peterson, J., "A Presence-based GEOPRIV Location Object
Format", RFC 4119, December 2005. Format", RFC 4119, December 2005.
Appendix A. Change log Appendix A. Change log
Changes to this draft in comparison to the previous version (-05 vs.
-04):
1. Fixed minor spelilng errors.
Changes to this draft in comparison to the previous version (-04 vs. Changes to this draft in comparison to the previous version (-04 vs.
-03): -03):
1. Changed wording of section 1 "Introduction", (Thompson ~ 7/09/08 1. Changed wording of section 1 "Introduction", (Thomson ~ 7/09/08
list comments). list comments).
1. Relocated text in section 3 "Overview of Location-by-Reference" 1. Relocated text in section 3 "Overview of Location-by-Reference"
to section 1 (Intro), (Thompson comments). to section 1 (Intro), (Thomson comments).
2. (Sect. 3, con't) Fixed Figure 1. Label, based on (Thompson 2. (Sect. 3, con't) Fixed Figure 1. Label, based on (Thomson
comments). comments).
3. Fixed minor spelling errors, incl. Note B., Note C., etc., based 3. Fixed minor spelling errors, incl. Note B., Note C., etc., based
on (Thompson comments). on (Thomson comments).
4. Added some qualifying text (security) around possession model, 4. Added some qualifying text (security) around possession model,
based on (Thompson comments). based on (Thomson comments).
5. Replaced "use type" labels with "authorization models", "access 5. Replaced "use type" labels with "authorization models", "access
authorization model", and "possession authorization model", (Thompson authorization model", and "possession authorization model", (Thomson
comments). comments).
6. Changed the entity role of applying security from LIS (Server- 6. Changed the entity role of applying security from LIS (Server-
side authentication), to the Rule-Maker (owner/Target) providing side authentication), to the Rule-Maker (owner/Target) providing
policies to the LIS, (Thompson comments). policies to the LIS, (Thomson comments).
7. Changed requirement C3 to a MUST, (Thompson comments). 7. Changed requirement C3 to a MUST, (Thomson comments).
8. Added new requirement, C12, "C12. Location URI Lifetime:" as a 8. Added new requirement, C12, "C12. Location URI Lifetime:" as a
SHOULD for all, and MUST for possession auth model, (Thompson SHOULD for all, and MUST for possession auth model, (Thomson
comments). comments).
9. Changed name of requirement C8 to "Location Only", (Thompson 9. Changed name of requirement C8 to "Location Only", (Thomson
comments). comments).
10. Reworded C7 and D6 to be less implementation specific, (Thompson 10. Reworded C7 and D6 to be less implementation specific, (Thomson
comments). comments).
11. Changed requirements C11, D11 to SHOULD, (Thompson comments). 11. Changed requirements C11, D11 to SHOULD, (Thomson comments).
12. (Section 5:) Removed lead in sentence for readibility, (Thompson 12. (Section 5:) Removed lead in sentence for readibility, (Thomson
comments). comments).
13. Remove "pawn ticket" reference - replaced with "possession 13. Remove "pawn ticket" reference - replaced with "possession
authorization model", (Thompson comments). authorization model", (Thomson comments).
14. Added new paragraph to the security section (Thompson, 7/09/08 14. Added new paragraph to the security section (Thomson, 7/09/08
comments). comments).
15. Corrected other minor spelling and wording errors and 15. Corrected other minor spelling and wording errors and
deficiencies (refer to diff 04/03) (-Editor). deficiencies (refer to diff 04/03) (-Editor).
Changes to this draft in comparison to the previous version (-03 vs. Changes to this draft in comparison to the previous version (-03 vs.
-02): -02):
1. Changed wording of section 3 "Overview of Location-by-Reference" 1. Changed wording of section 3 "Overview of Location-by-Reference"
(Polk, Thomson, Winterbottom ~ 4/1/08 list comments). (Polk, Thomson, Winterbottom ~ 4/1/08 list comments).
 End of changes. 22 change blocks. 
35 lines changed or deleted 41 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/