HELD-02 James Winterbottom. What is HELD? HELD is an application layer location acquisition protocol Designed to provide location in the form of a PIDF-LO.

Slides:



Advertisements
Similar presentations
© 2008 Cisco Systems, Inc. All rights reserved.Cisco ConfidentialPresentation_ID 1 W. Schulte Chapter 5: Network Address Translation for IPv4  Connecting.
Advertisements

Problem Statement and Architecture for Information Exchange Between Interconnected Traffic Engineered Networks draft-farrel-interconnected-te-info-exchange-03.txt.
SACM Terminology Nancy Cam-Winget, David Waltermire, March.
IPv4 and IPv6 Mobility Support Using MPLS and MP-BGP draft-berzin-malis-mpls-mobility-00 Oleg Berzin, Andy Malis {oleg.berzin,
NGMAST’08 – Jani Pellikkawww.mediateam.oulu.fi 1 Partially Decentralized Context Management for P2P Communities Jani Pellikka, Timo Koskela, Mika Ylianttila.
1 OMA Location Working Group Update Mike Loushine Senior Scientist / Program Manager Emerging Mobile Technologies Group Telcordia Applied Research May.
DHCP Dynamic Host Configuration Protocol by: Kirk Z. Moreno.
A Study of Mobile IP Kunal Ganguly Wichita State University CS843 – Distributed Computing.
EventBook What – An Android based Mobile App. Using Social Networking APIs Who – Every mobile user specially targeted to the age group of 16 – 40 Why –
MIF API draft-ietf-mif-api-extension-05 Dapeng Liu.
Copyright © 2004 Juniper Networks, Inc. Proprietary and Confidentialwww.juniper.net 1 ANCP protocol draft updates draft-ietf-ancp-protocol-00.txt ANCP.
Use Cases and API Extension for Source IP Address Selection draft-sijeon-dmm-use-cases-api-source-00.txt Presenter: Alper Yegin Authors: Seil Jeon, Sergio.
Lectured By: Vivek Dimri Asst Professor CSE Deptt. Sharda University, Gr. Noida.
Binary to Decimal Conversion for LCI IETF 67 – GeoPriv WG 11/06/2006 San Diego.
Ethernet Basics - 5 IGMP. The Internet Group Management Protocol (IGMP) is an Internet protocol that provides a way for an Internet computer to report.
HELD Location Acquisition Solution James Winterbottom Andrew Corporation March 2007.
Jun Li DHCP Option for Access Network Information draft-lijun-dhc-clf-nass-option-01.
1 IETF 78: NETEXT Working Group IPSec/IKEv2 Access Link Support in Proxy Mobile IPv6 IPSec/IKEv2-based Access Link Support in Proxy Mobile IPv6 Sri Gundavelli.
EAP Extensions for EAP Re- authentication Protocol (ERP) draft-wu-hokey-rfc5296bis-01 Yang Shi Qin Wu Zhen Cao
AAA and Mobile IPv6 Franck Le AAA WG - IETF55. Why Diameter support for Mobile IPv6? Mobile IPv6 is a routing protocol and does not deal with issues related.
IETF GEOPRIV Status Richard L. Barnes BBN Technologies GEOPRIV Secretary Emergency Services Workshop October 2008.
GEOPRIV Layer 7 Location Configuration Protocol; Problem Statement and Requirements draft-ietf-geopriv-l7-lcp-ps-00.txt Hannes Tschofenig, Henning Schulzrinne.
© 2008 Cisco Systems, Inc. All rights reserved.Cisco ConfidentialPresentation_ID 1 Chapter 11: Network Address Translation for IPv4 Routing And Switching.
Fonkey Project Update: Target Applications TechSec WG, RIPE-45 May 14, 2003 Yuri Demchenko.
Draft-ietf-fecframe-config-signaling-02 1 FEC framework Configuration Signaling draft-ietf-fecframe-config-signaling-02.txt IETF 76 Rajiv Asati.
CCAMP WG, IETF 80th, Prague, Czech Republic draft-ietf-ccamp-gmpls-g709-framework-04.txt Framework for GMPLS and PCE Control of G.709 Optical Transport.
Requirements For Handover Information Services MIPSHOP – IETF #65 Srinivas Sreemanthula (Ed.)
SIP Extensions for Network-Asserted Caller Identity and Privacy within Trusted Networks Flemming Andreasen W. Marshall, K. K. Ramakrishnan,
ECRIT - Getting Certain URIs, and Alternatives to Getting Emergency Dialstring(s) draft-polk-ecrit-lost-server-uri-00 draft-polk-dhc-ecrit-uri-psap-esrp-00.
Simo Veikkolainen Simple Application Configuration Protocol draft-veikkolainen-sipping-app-config-00 Simo Veikkolainen APP area open meeting.
1 The Internet Introductory material. An overview lecture that covers Internet related topics, including a definition of the Internet, an overview of its.
IETF-Vienna IEPREP WG, July 2003 Ken Carlberg. Discussion Update –draft-ietf-ieprep-framework-05.txt –draft-ietf-ieprep-ets-general-03.txt –draft-ietf-ieprep-ets-telephony-05.txt.
Dnssd requirements draft-ietf-dnssd-requirements-03 Kerry Lynn Stuart Cheshire Marc Blanchet Daniel Migault IETF 90, Toronto, 24 July
PCE 64 th IETF PCE Policy Architecture draft-berger-pce-policy-architecture-00.txt Lou Berger Igor Bryskin Dimitri Papadimitriou.
A Framework for Session Initiation Protocol User Agent Profile Delivery (draft-ietf-sipping-config-framework-11) SIPPING – IETF 68 Mar 19, 2007 Sumanth.
IETF #65 Network Discovery and Selection Problem draft-ietf-eap-netsel-problem-04 Farooq Bari Jouni Korhonen.
August 2, 2005 IETF 63 – Paris, France Media Independent Handover Services and Interoperability Ajay Rajkumar Chair, IEEE WG.
Draft-melia-mipshop-mobility-services-ps-01.txt. From IETF #66 Discuss MIH PS (as expressed by the WG chair) Need a single PS at WG level (several drafts.
NVO3 VDP Gap Analysis VM to NVE Specific Control Plane Requirements Paul Bottorff (HP) Joseph Pelissier (Cisco) Patricia Thaler (Broadcom)
Extensions to PCEP for Hierarchical Path Computation Elements PCE draft-zhang-pcep-hierarchy-extensions-00 Fatai Zhang Quintin Zhao.
Requirements for PCE Discovery draft-leroux-pce-discovery-reqs-00.txt Jean-Louis Le Roux (France Telecom) Paul Mabey (Qwest) Eiji Oki (NTT) Ting Wo Chung.
DHCP-DNS Interaction Bernie Volz IETF-61, DHC WG.
S. Ali, K. Cartwright, D. Guyton, A. Mayrhofer, J-F. Mulé Data for Reachability of Inter/tra-NetworK SIP (drinks) DRINKS WG draft-mule-drinks-proto-02.
Page 1 IETF DRINKS Working Group Data Model and Protocol Requirements for DRINKS IETF 72 - Thursday July Tom Creighton -
64th IETF Vancouver November 2005 ASON-Compatible Signaling.
PIDF-LO Profile James Winterbottom, Martin Thomson IETF-65.
Submission doc.: IEEE 11-12/0346r2 WLAN and Cellular Interworking and Discovery Use Case Date: Slide 1Joseph Levy, InterDigital Communications,
David B. Johnson Rice University Department of Computer Science DSR Draft Status Monarch Project 57th IETF.
Chapter 7: Transport Layer
NACK-Oriented Reliable Multicast (NORM) Update
Zhenbin Li, Kai Lu Huawei Technologies IETF 98, Chicago, USA
RELO: Retrieving End System Location Information draft-schulzrinne-geopriv-relo-03 Henning Schulzrinne March 2007 IETF68 - GEOPRIV.
Host of Troubles : Multiple Host Ambiguities in HTTP Implementations
Location Configuration at Layer 7
Sanjay Wadhwa Juniper Networks
Interface to Routing System (I2RS)
Net 323: NETWORK Protocols
HTTP Enabled Location Delivery (HELD)
Wsdl.
Percy S. Tarapore, AT&T Robert Sayko, AT&T
DetNet DetNet Flow Information Model draft-farkas-detnet-flow-information-model-02 Balázs Varga, János Farkas, Rodney Cummings, Jiang Yuanlong and.
RELO: Retrieving End System Location Information draft-schulzrinne-geopriv-relo-03 Henning Schulzrinne March 2007 IETF68 - GEOPRIV.
AMP Cache Sandeep Davu.
Introduction to TCP/IP
Chapter 11: Network Address Translation for IPv4
Mobile IP Regional Registration
SAML/SIP Profiles and Call Initiation
János Farkas, Balázs Varga, Rodney Cummings, Jiang Yuanlong
Standard Representation Of Domain Sequence
Presentation transcript:

HELD-02 James Winterbottom

What is HELD? HELD is an application layer location acquisition protocol Designed to provide location in the form of a PIDF-LO while remaining access agnostic. Supports mobile, nomadic and static users Complies with RFC-3693 requirements for a using-protocol Supports delivery of location by-value, and location by-reference Supports location assertion

A Service View

Changes to HELD Draft format changed to be task oriented describing what parameters should be set for specific types of operations. Changed terminology to be inline with RFC-3963 Removed OBO Moved examples to main body of document. Corrected and added more examples.

What’s New Tentatively added SLP as a service discovery technique based on comments from last IETF. Added using HELD to talk with LG. Added using HELD for LS to LS comms Speculatively added LERO Added identity parameters and extension parameters.

Some misconceptions HELD discovery is intended to support the finding of the LS for an arbitrary Target. –HELD discovery is intend for a Target to find the LS in its administrative domain. The Target may then provide recipients or other nodes with a locationURI from which they may acquire location from the LS on request.

Some misconceptions HELD location acquisition introduces overheads vs layer 2 techniques. –The LS serving the access network must be discovered. This is a one time operation. Once discovered the LS may be queried many times without requiring LS re-discovery.