Emergency Contacts (ECON)
1 / 12

Andrew Newton IETF ECRIT Working Group 1 February 2006 Washington, DC, US - PowerPoint PPT Presentation

  • Uploaded on

Emergency Contacts (ECON) draft-hardie-ecrit-iris-03 Andrew Newton, VeriSign Ted Hardie, Qualcomm Hannes Tschofenig, Siemens. Andrew Newton IETF ECRIT Working Group 1 February 2006 Washington, DC, US. Background. Emergency Contact (ECON) is specified as an IRIS (RFC 3981) registry type.

I am the owner, or an agent authorized to act on behalf of the owner, of the copyrighted work described.
Download Presentation

PowerPoint Slideshow about 'Andrew Newton IETF ECRIT Working Group 1 February 2006 Washington, DC, US' - trinh

An Image/Link below is provided (as is) to download presentation

Download Policy: Content on the Website is provided to you AS IS for your information and personal use and may not be sold / licensed / shared on other websites without getting consent from its author.While downloading, if for some reason you are not able to download a presentation, the publisher may have deleted the file from their server.

- - - - - - - - - - - - - - - - - - - - - - - - - - E N D - - - - - - - - - - - - - - - - - - - - - - - - - -
Presentation Transcript
Andrew newton ietf ecrit working group 1 february 2006 washington dc us

Emergency Contacts (ECON)draft-hardie-ecrit-iris-03Andrew Newton, VeriSignTed Hardie, QualcommHannes Tschofenig, Siemens

Andrew Newton

IETF ECRIT Working Group

1 February 2006

Washington, DC, US


  • Emergency Contact (ECON) is specified as an IRIS (RFC 3981) registry type.

    • A simple request/response protocol using XML.

    • Uses S-NAPTR (RFC 3958)

      • Profiled use of NAPTR and SRV

      • Distinguishes between App proto and Transfer Proto

      • Protocol preference can be stated.

      • Host/port preference can be stated.

  • IRIS was created in the CRISP working group by TLD operators.

    • Who know a thing or two about high resolution loads, operations of highly available services, and moving data around the globe.

A simple request
A Simple Request

<request xmlns="urn:ietf:params:xml:ns:iris1">



xmlns="urn:ietf:params:xml:ns:econ1" >



<A1>New York</A1>

<A3>New York</A3>



<LOC>Suite 75</LOC>







A simple response
A Simple Response

<response xmlns="urn:ietf:params:xml:ns:iris1">





authority="example.com" registryType="econ1"

entityClass="econ" entityName="nypd" >


New York City Police Department












  • Caching of answers by “seekers”.

  • In the case of civic addresses…

    • If your civic address does not change within X number of minutes, do not requery.

  • In the case of geo…

    • If your coordinates stay within polygon Y for X number of minutes, do not requery.

Database replication in econ
Database Replication in ECON

  • We take no single position on database replication with ECON.

    • It most likely will differ greatly throughout the world.

    • Isn’t it out of scope?

  • But we have identified 3 methods of conducting database replication with ECON.

    • Serialized database entries to a file as specified in IRIS.

      • And the file transfer protocol of your choice. Many people like SFTP.

    • ECONREP (ECON Replication)

      • Interactive IRIS profile.

      • Replication of entries before they become active.

      • Incremental replication.

    • Anything you find that works better for your situation.

      • RDBMS replication

      • Shared Network Memory

      • Osmosis, crystal balls, and strong hope

Object signing considered harmful
Object Signing Considered Harmful

  • My house is on fire. Who do I call?

    • Please update your client with the proper trust anchors.

      • My house is still on fire.

    • Please cryptographically verify these URIs.

      • It’s getting hotter.

    • Please check this CRL.

      • Did I mention that my house is on fire?

  • Object signing is useful for diagnosing problems.

    • But that happens after the incident, not during.

    • All the mechanisms to get object signing to work seem to be a pretty heavy price to pay for a diagnostic tool.

  • Due to the nature of ECRIT, will need to be “on-the-fly”.


Comparison to dns sos and lump
Comparison to DNS SOS and LUMP


    • Similar in that it is built for speed by trying to utilize UDP when possible.

    • Unlike in that its query framework is not intertwined with its octet framing.

      • IRIS/ECON uses XML, which is much more flexible.

  • LUMP

    • Similar in that is just as flexible in the query framework.

    • Unlike in that it does not require heavyweight transfer protocol interactions used by SOAP/HTTPS.

      • IRIS/ECON uses UDP when possible to gain efficiencies and takes into careful consideration the copious use of security mechanisms which may weigh down the protocol.

Packets in a simple udp transaction

Tell me about example.com

Here is the data

Packets in a Simple UDP Transaction



Packets in a typical tcp transaction


Open a TCP connection

Connection induced state.

Consumes memory, ports, and

CPU in the server.


Are you Sure?


I need some data.

NOTE: At this point 3

packets have been

exchanged, but no data

has been exchanged.

Here is the data


Close the TCP connection


Packets in a typical TCP Transaction



Messages in a typical tls transaction

Open a TCP connection

TLS( ClientHello).

TLS( Certificate ).

TLS( ServerHello).

Are you Sure?


TLS( ServerHelloDone ).

TLS( ChangeCipherSpec ).

TLS( ClientKeyExchange ).

I need some data.


Here is the data

TLS( Finished ).


This is where ECRIT data

starts to be exchanged.

TLS( ChangeCipherSpec ).

TLS( Finished ).

Close the TCP connection

TLS( ClosureAlert ).

TLS( ClosureAlert ).


Messages in a typical TLS Transaction



Udp vs tcp vs tls
UDP vs. TCP vs. TLS

  • IRIS queries over UDP, TCP, and TLS.

  • 5 distinct queries X 500 iterations

    • = 2,500 queries

  • UDP

    • 13.8 X faster than TCP

    • 45.9 X faster than TLS

  • TCP

    • 3.4 X faster than TLS