< draft-polk-newton-ecrit-arch-considerations-01.txt		draft-polk-newton-ecrit-arch-considerations-02.txt >
	ECRIT Working Group James Polk		ECRIT Working Group James Polk
	Internet-Draft Cisco Systems		Internet-Draft Cisco Systems
	Expires: April 24th, 2006 Andrew Newton		Expires: Sept 6th, 2006 Andrew Newton
	VeriSign		VeriSign
	October 24th, 2005		March 6th, 2006
	Emergency Context Routing of Internet Technologies		Emergency Context Routing of Internet Technologies
	Architecture Considerations		Architecture Considerations
	draft-polk-newton-ecrit-arch-considerations-01		draft-polk-newton-ecrit-arch-considerations-02
	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 36 ¶		skipping to change at page 1, line 36 ¶
	months and may be updated, replaced, or obsoleted by other documents		months and may be updated, replaced, or obsoleted by other documents
	at any time. It is inappropriate to use Internet-Drafts as		at any time. It is inappropriate to use Internet-Drafts as
	reference material or to cite them other than as "work in progress."		reference 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 March 6th, 2006.		This Internet-Draft will expire on September 6th, 2006.
	Copyright Notice		Copyright Notice
	Copyright (C) The Internet Society (2005).		Copyright (C) The Internet Society (2006).
	Abstract		Abstract
	This document discusses architectural considerations for emergency		This document discusses architectural considerations for emergency
	context routing of Internet technologies. The purpose of this		context routing of Internet technologies. The purpose of this
	document is to provide a systemic view of emergency context routing,		document is to provide a systemic view of emergency context routing,
	discuss unresolved issues, and explain the relationship of some of		discuss unresolved issues, and explain the relationship of some of
	the proposals to these issues, while discussing potential directions		the proposals to these issues, while discussing potential directions
	that might be still be necessary for the working group to		that might be still be necessary for the working group to
	investigate.		investigate.
	skipping to change at page 5, line 31 ¶		skipping to change at page 5, line 31 ¶
	Gateway addresses. This could also be used to deliver the		Gateway addresses. This could also be used to deliver the
	geospatial or civic address of the client to it for future use.		geospatial or civic address of the client to it for future use.
	This is typically done at device or individual application		This is typically done at device or individual application
	boot times. Unlike other parts of the architecture, bootstrapping		boot times. Unlike other parts of the architecture, bootstrapping
	is the only phase of the emergency call routing process that does		is the only phase of the emergency call routing process that does
	not have a single solution. This is due to the many network		not have a single solution. This is due to the many network
	configuration techniques used by access networks.		configuration techniques used by access networks.
	There are three well-known methods of bootstrapping:		There are three well-known methods of bootstrapping:
	1. Using the DHCP protocol		1. Using the DHCP protocol
	2. Using the PPP protocol		2. Using the PPP protocol
	3. Using IEEE 802.1 LLDP-MED		3. Using IEEE 802.1 LLDP-MED
	For location information, there are two types: location information		For location information, there are two types: location information
	regarding a civic address (e.g. 123 Main St ) and geospatial		regarding a civic address (e.g. 123 Main St ) and geospatial
	information (e.g. x, y, z coordinates).		information (e.g. x, y, z coordinates).
	The set of configuration data types has not been discussed or		The set of configuration data types has not been discussed or
	resolved. But the following types of configuration information have		resolved. But the following types of configuration information have
	been noted: 1) references to LCMS servers, 2) references to PSAPs,		been noted: 1) references to LCMS servers, 2) references to PSAPs,
	and 3) references to location information servers.		and 3) references to location information servers.
	skipping to change at page 14, line 43 ¶		skipping to change at page 14, line 43 ¶
	[RFC3825] J. Polk, J. Schnizlein, M. Linsner, "Dynamic Host		[RFC3825] J. Polk, J. Schnizlein, M. Linsner, "Dynamic Host
	Configuration Protocol Option for Coordinate-based Location		Configuration Protocol Option for Coordinate-based Location
	Configuration Information", RFC 3825, July 2004		Configuration Information", RFC 3825, July 2004
	[RFC3118] Droms, R. and W. Arbaugh, "Authentication for DHCP		[RFC3118] Droms, R. and W. Arbaugh, "Authentication for DHCP
	Messages", RFC 3118, June 2001.		Messages", RFC 3118, June 2001.
	13.2 Informative References		13.2 Informative References
	[ID-DHC-URI] J. Polk, "DHCP URI Option", draft-polk-dhc-uri-00.txt,		[ID-DHC-URI] J. Polk, "A Dynamic Host Configuration Protocol Option
	"work-in-progress", Sept 05		for Requesting and Receiving Uniform Resource Identifiers",
			draft-polk-dhc-uri-03.txt, "work in progress", March 2006
	[ID-ECRIT-JAPAN] H. Arai, M. Kawanishi, draft-arai-ecrit-japan-req-		[ID-ECRIT-JAPAN] H. Arai, M. Kawanishi, draft-arai-ecrit-japan-req-
	01.txt, "work-in-progress", May 2005		01.txt, "work-in-progress", May 2005
	Author's Address		Author's Address
	James M. Polk		James M. Polk
	3913 Treemont Circle		3913 Treemont Circle
	Colleyville, Texas 76034		Colleyville, Texas 76034
	USA		USA
	skipping to change at page 16, line 11 ¶		skipping to change at page 16, line 11 ¶
	This document and the information contained herein are provided on		This document and the information contained herein are provided on
	an "AS IS" basis and THE CONTRIBUTOR, THE ORGANIZATION HE/SHE		an "AS IS" basis and THE CONTRIBUTOR, THE ORGANIZATION HE/SHE
	REPRESENTS OR IS SPONSORED BY (IF ANY), THE INTERNET SOCIETY AND THE		REPRESENTS OR IS SPONSORED BY (IF ANY), THE INTERNET SOCIETY AND THE
	INTERNET ENGINEERING TASK FORCE DISCLAIM ALL WARRANTIES, EXPRESS OR		INTERNET ENGINEERING TASK FORCE DISCLAIM ALL WARRANTIES, EXPRESS OR
	IMPLIED, INCLUDING BUT NOT LIMITED TO ANY WARRANTY THAT THE USE OF		IMPLIED, INCLUDING BUT NOT LIMITED TO ANY WARRANTY THAT THE USE OF
	THE INFORMATION HEREIN WILL NOT INFRINGE ANY RIGHTS OR ANY IMPLIED		THE INFORMATION HEREIN WILL NOT INFRINGE ANY RIGHTS OR ANY IMPLIED
	WARRANTIES OF MERCHANTABILITY OR FITNESS FOR A PARTICULAR PURPOSE.		WARRANTIES OF MERCHANTABILITY OR FITNESS FOR A PARTICULAR PURPOSE.
	Copyright Statement		Copyright Statement
	Copyright (C) The Internet Society (2005). This document is subject		Copyright (C) The Internet Society (2006). This document is subject
	to the rights, licenses and restrictions contained in BCP 78, and		to the rights, licenses and restrictions contained in BCP 78, and
	except as set forth therein, the authors retain all their rights.		except as set forth therein, the authors retain all their rights.
	Acknowledgment		Acknowledgment
	Funding for the RFC Editor function is currently provided by the		Funding for the RFC Editor function is currently provided by the
	Internet Society.		Internet Society.
End of changes. 8 change blocks.
	13 lines changed or deleted		14 lines changed or added
This html diff was produced by rfcdiff 1.48. The latest version is available from http://tools.ietf.org/tools/rfcdiff/