2013
DOI: 10.17487/rfc6848
|View full text |Cite
|
Sign up to set email alerts
|

Specifying Civic Address Extensions in the Presence Information Data Format Location Object (PIDF-LO)

Abstract: New fields are occasionally added to civic addresses. A backwardcompatible mechanism for adding civic address elements to the Geopriv civic address format is described. A formal mechanism for handling unsupported extensions when translating between XML and DHCP civic address forms is defined for entities that need to perform this translation. Initial extensions for some new elements are also defined. The Location-to-Service Translation (LoST) protocol mechanism (defined in RFC 5222) that returns civic address … Show more

Help me understand this report

Search citation statements

Order By: Relevance

Paper Sections

Select...
1
1

Citation Types

0
2
0

Year Published

2015
2015
2017
2017

Publication Types

Select...
5
1

Relationship

1
5

Authors

Journals

citations
Cited by 6 publications
(2 citation statements)
references
References 15 publications
0
2
0
Order By: Relevance
“…Where a "one off" data is involved (no human communication), data is sent without initialising a SIP session by using the SIP MESSAGE transaction as recommended in [3]. Data structures and mechanisms will follow work in [4], which includes: location (conveyed in the Presence Information Data Format Location Object (PIDF-LO) [5][6][7][8][9]), call related information (device type (including sensor type), service providers, subscriber (including personal information), contact information) and caller information (medical information and "in case of emergency" (ICE) contact data).…”
Section: Figure 1 -Nexes Overviewmentioning
confidence: 99%
“…Where a "one off" data is involved (no human communication), data is sent without initialising a SIP session by using the SIP MESSAGE transaction as recommended in [3]. Data structures and mechanisms will follow work in [4], which includes: location (conveyed in the Presence Information Data Format Location Object (PIDF-LO) [5][6][7][8][9]), call related information (device type (including sensor type), service providers, subscriber (including personal information), contact information) and caller information (medical information and "in case of emergency" (ICE) contact data).…”
Section: Figure 1 -Nexes Overviewmentioning
confidence: 99%
“…Data Associated with a Location: Primary location data is conveyed in the Presence Information Data Format Location Object (PIDF-LO) data structure as defined in RFC 4119 [RFC4119] and extended by RFC 5139 [RFC5139] and RFC 6848 [RFC6848] (for civic location information), RFC 5491 [RFC5491] and RFC 5962 [RFC5962] (for geodetic location information), and RFC 7035 [RFC7035] (for relative location). This primary location data identifies the location or estimated location of the caller.…”
Section: Introductionmentioning
confidence: 99%