< draft-norreys-ecrit-authority2individuals-requirements-00.txt		draft-norreys-ecrit-authority2individuals-requirements-01.txt >
	ECRIT S. Norreys		ECRIT S. Norreys
	Internet-Draft BT Group		Internet-Draft BT Group
	Intended status: Informational H. Tschofenig		Intended status: Informational H. Tschofenig
	Expires: January 2, 2008 Nokia Siemens Networks		Expires: January 13, 2009 Nokia Siemens Networks
	H. Schulzrinne		H. Schulzrinne
	Columbia University		Columbia University
	July 1, 2007		July 12, 2008
	Requirements for Authority-to-Individuals Communication for Emergency		Requirements for Authority-to-Individuals Communication for Emergency
	Situations		Situations
	draft-norreys-ecrit-authority2individuals-requirements-00.txt		draft-norreys-ecrit-authority2individuals-requirements-01.txt
	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 38 ¶		skipping to change at page 1, line 38 ¶
	and may be updated, replaced, or obsoleted by other documents at any		and may be updated, replaced, or obsoleted by other documents at any
	time. It is inappropriate to use Internet-Drafts as reference		time. It is inappropriate to use Internet-Drafts as reference
	material or to cite them other than as "work in progress."		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 January 2, 2008.		This Internet-Draft will expire on January 13, 2009.
	Copyright Notice
	Copyright (C) The IETF Trust (2007).
	Abstract		Abstract
	Public safety agencies need to provide information to the general		Public safety agencies need to provide information to the general
	public before and during large-scale emergencies. While many aspects		public before and during large-scale emergencies. While many aspects
	of such systems are specific to national or local jurisdictions,		of such systems are specific to national or local jurisdictions,
	emergencies span such boundaries and notifications need to reach		emergencies span such boundaries and notifications need to reach
	visitors from other jurisdictions. This document summarizes		visitors from other jurisdictions. This document summarizes
	requirements for protocols to alert individuals within a defined		requirements for protocols to alert individuals within a defined
	geographic area.		geographic area.
	skipping to change at page 8, line 15 ¶		skipping to change at page 8, line 15 ¶
	6. Acknowledgments		6. Acknowledgments
	This document reuses requirements captured outside the IETF, namely		This document reuses requirements captured outside the IETF, namely
	ETSI (with [ETSI-TS-102-182]), and the 3GPP (with [3GPP-TR-22.968]).		ETSI (with [ETSI-TS-102-182]), and the 3GPP (with [3GPP-TR-22.968]).
	We would like to thank the authors of these specifications for their		We would like to thank the authors of these specifications for their
	work. Note, however, that only a small subset of the requirements		work. Note, however, that only a small subset of the requirements
	have been reflected that do not relate to specific deployments, user		have been reflected that do not relate to specific deployments, user
	interface aspects, detailed regulatory requirements, management and		interface aspects, detailed regulatory requirements, management and
	operational considerations, and non-IP specific technologies.		operational considerations, and non-IP specific technologies.
			We would like to thank Leopold Murhammer for his review in July 2007.
	7. References		7. References
	7.1. Normative References		7.1. Normative References
	[RFC2119] Bradner, S., "Key words for use in RFCs to Indicate		[RFC2119] Bradner, S., "Key words for use in RFCs to Indicate
	Requirement Levels", BCP 14, RFC 2119, March 1997.		Requirement Levels", BCP 14, RFC 2119, March 1997.
	7.2. Informative References		7.2. Informative References
	[3GPP-TR-22.968]		[3GPP-TR-22.968]
	skipping to change at page 9, line 6 ¶		skipping to change at page 9, line 6 ¶
	Steve Norreys		Steve Norreys
	BT Group		BT Group
	1 London Road		1 London Road
	Brentwood, Essex CM14 4QP		Brentwood, Essex CM14 4QP
	UK		UK
	Phone: +44 1277 32 32 20		Phone: +44 1277 32 32 20
	Email: steve.norreys@bt.com		Email: steve.norreys@bt.com
	Hannes Tschofenig		Hannes Tschofenig
	Nokia Siemens Networks		Nokia Siemens Networks
	Otto-Hahn-Ring 6		Linnoitustie 6
	Munich, Bavaria 81739		Espoo 02600
	Germany		Finland
	Email: Hannes.Tschofenig@nsn.com		Phone: +358 (50) 4871445
	URI: http://www.tschofenig.com		Email: Hannes.Tschofenig@gmx.net
			URI: http://www.tschofenig.priv.at
	Henning Schulzrinne		Henning Schulzrinne
	Columbia University		Columbia University
	Department of Computer Science		Department of Computer Science
	450 Computer Science Building		450 Computer Science Building
	New York, NY 10027		New York, NY 10027
	US		US
	Phone: +1 212 939 7004		Phone: +1 212 939 7004
	Email: hgs+ecrit@cs.columbia.edu		Email: hgs+ecrit@cs.columbia.edu
	URI: http://www.cs.columbia.edu		URI: http://www.cs.columbia.edu
	Full Copyright Statement		Full Copyright Statement
	Copyright (C) The IETF Trust (2007).		Copyright (C) The IETF Trust (2008).
	This document is subject to the rights, licenses and restrictions		This document is subject to the rights, licenses and restrictions
	contained in BCP 78, and except as set forth therein, the authors		contained in BCP 78, and except as set forth therein, the authors
	retain all their rights.		retain all their rights.
	This document and the information contained herein are provided on an		This document and the information contained herein are provided on an
	"AS IS" basis and THE CONTRIBUTOR, THE ORGANIZATION HE/SHE REPRESENTS		"AS IS" basis and THE CONTRIBUTOR, THE ORGANIZATION HE/SHE REPRESENTS
	OR IS SPONSORED BY (IF ANY), THE INTERNET SOCIETY, THE IETF TRUST AND		OR IS SPONSORED BY (IF ANY), THE INTERNET SOCIETY, THE IETF TRUST AND
	THE INTERNET ENGINEERING TASK FORCE DISCLAIM ALL WARRANTIES, EXPRESS		THE INTERNET ENGINEERING TASK FORCE DISCLAIM ALL WARRANTIES, EXPRESS
	OR IMPLIED, INCLUDING BUT NOT LIMITED TO ANY WARRANTY THAT THE USE OF		OR IMPLIED, INCLUDING BUT NOT LIMITED TO ANY WARRANTY THAT THE USE OF
	skipping to change at page 10, line 44 ¶		skipping to change at line 395 ¶
	attempt made to obtain a general license or permission for the use of		attempt made to obtain a general license or permission for the use of
	such proprietary rights by implementers or users of this		such proprietary rights by implementers or users of this
	specification can be obtained from the IETF on-line IPR repository at		specification can be obtained from the IETF on-line IPR repository at
	http://www.ietf.org/ipr.		http://www.ietf.org/ipr.
	The IETF invites any interested party to bring to its attention any		The IETF invites any interested party to bring to its attention any
	copyrights, patents or patent applications, or other proprietary		copyrights, patents or patent applications, or other proprietary
	rights that may cover technology that may be required to implement		rights that may cover technology that may be required to implement
	this standard. Please address the information to the IETF at		this standard. Please address the information to the IETF at
	ietf-ipr@ietf.org.		ietf-ipr@ietf.org.
	Acknowledgment
	Funding for the RFC Editor function is provided by the IETF
	Administrative Support Activity (IASA).
End of changes. 9 change blocks.
	14 lines changed or deleted		13 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/