Skip to main content

Liaison statement
Liaison Statement to IETF on HELD protocol extensions

Additional information about IETF liaison relationships is available on the IETF webpage and the Internet Architecture Board liaison webpage.
State Posted
Submitted Date 2014-11-19
From Contact Sylwia Korycinska
To Group ecrit
To Contacts Marc Linsner <>
Roger Marshall <>
Cc Richard Barnes <>
Alissa Cooper <>
Response Contact
Purpose For comment
Deadline 2014-12-15 Action Needed
Attachments Liaison Statement to IETF on HELD protocol extensions
1. Overall description:

ETSI NTECH with collaboration of a number of other ETSI Technical Bodies is
developing the stage 3 specifications (protocols) in response to the European
Commission Mandate M/493 about delivery and transport of the emergency caller’s

The EC Mandate requires that, the emergency caller’s location information be
provided by the Voice Service Providers (VSPs) in signaling messages they send
towards PSAPs (Public Safety Answering Points) via an Emergency Service Routing
Proxy (ESRP). This information is used to reveal the caller's location to the
selected PSAP and to select the correct PSAP to be involved for an emergency

ETSI’s draft specification, ES 203 178, addresses the European mandate while at
the same time maintaining tight privacy requirements regulated by a number of
European member states prohibiting the disclosure of location information to
non-emergency entities.

In order to address the Commissions requirements and satisfy member state
regulatory constraints the architecture that was developed requires the access
network provider to supply emergency routeing information along with the
location information in a single request/response transaction.

Discussions have taken place in the ETSI NTECH committee on protocol mechanisms
for implementing the functionality in ES 203 178. The IETF HELD protocol
(RFC5985) along with its associated extension specifications support much of
the required functionality. However, the published protocol suite does not
support a mechanism for requesting and returning routing information. ETSI
NTECH is aware of an individual contribution,
draft-winterbottom-ecrit-priv-loc-04, that it deems sufficient to address its
remaining location and route acquisition requirements. ETSI NTECH is expressing
an interest in such a protocol mechanism.

ETSI NTECH is interested in receiving information from the IETF ECRIT on their
work plan and milestones for further developing the HELD Protocol, in order to
provide the extensions needed to provide the emergency caller routeing
information. Our goal is to approve stage 3 document by mid 2015.

2. Actions:

IETF ECRIT area to confirm that the group intends to work at the extensions of
the HELD protocol to enable its use to support the emergency caller location as
defined by ETSI M493 Group.

3. Date of next meetings of the originator:
TBD - call
16-18 December 2014, Paris (F)