< draft-dolly-sipping-atis-ptsc-02.txt		draft-dolly-sipping-atis-ptsc-03.txt >
	SIPPING M. Dolly		SIPPING M. Dolly
	Internet-Draft AT&T Labs		Internet-Draft AT&T Labs
	Expires: September 6, 2006 B. Hall		Expires: March 24, 2007 B. Hall
	SBC		SBC
	J. Zebarth		J. Zebarth
	Nortel		Nortel
	March 5, 2006		October 23, 2006
	ATIS PTSC Work Program		ATIS PTSC Work Program
	draft-dolly-sipping-atis-ptsc-02.txt		draft-dolly-sipping-atis-ptsc-03.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 37 ¶		skipping to change at page 1, line 37 ¶
	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 September 6, 2006.		This Internet-Draft will expire on March 24, 2007.
	Copyright Notice		Copyright Notice
	Copyright (C) The Internet Society (2006).		Copyright (C) The Internet Society (2006).
	Abstract		Abstract
	At the 65th Dallas IETF Meeting it is anticipated that the Real-time		At the 67th San Diego IETF Meeting it is anticipated that the Real-time
	Applications and Infrastructure Area will meet for the first time and		Applications and Infrastructure Area will meet and its ongoing work program will be an item for discussion.
	its work program will be an item for discussion.
	This Internet Draft has been prepared to share the relevant portions		This Internet Draft has been prepared to share the relevant portions
	of the PTSC current work program with the IETF. It is hoped that		of the PTSC current work program with the IETF. It is hoped that
	awareness of the Packet Technologies Systems Committee (PTSC) work		awareness of the Packet Technologies Systems Committee (PTSC) work
	program will allow for more informed discussion.		program will allow for more informed discussion.
	Table of Contents		Table of Contents
	1. Introduction . . . . . . . . . . . . . . . . . . . . . . . . . 3		1. Introduction . . . . . . . . . . . . . . . . . . . . . . . . . 3
	2. PTSC Work Program . . . . . . . . . . . . . . . . . . . . . . 3		2. PTSC Work Program . . . . . . . . . . . . . . . . . . . . . . 3
	skipping to change at page 3, line 7 ¶		skipping to change at page 5, line ? ¶
	3. Summary . . . . . . . . . . . . . . . . . . . . . . . . . . . 7		3. Summary . . . . . . . . . . . . . . . . . . . . . . . . . . . 7
	4. Security Considerations . . . . . . . . . . . . . . . . . . . 8		4. Security Considerations . . . . . . . . . . . . . . . . . . . 8
	5. Changes from previous . . . . . . . . . . . . . . . . . . . . 8		5. Changes from previous . . . . . . . . . . . . . . . . . . . . 8
	6. References . . . . . . . . . . . . . . . . . . . . . . . . . . 8		6. References . . . . . . . . . . . . . . . . . . . . . . . . . . 8
	Appendix A. Acknowledgments . . . . . . . . . . . . . . . . . . . 9		Appendix A. Acknowledgments . . . . . . . . . . . . . . . . . . . 9
	Authors' Addresses . . . . . . . . . . . . . . . . . . . . . . . . 10		Authors' Addresses . . . . . . . . . . . . . . . . . . . . . . . . 10
	Intellectual Property and Copyright Statements . . . . . . . . . . 11		Intellectual Property and Copyright Statements . . . . . . . . . . 11
	1. Introduction		1. Introduction
	At the 65th Dallas IETF Meeting it is anticipated that discussions		At the 67th San Diego IETF Meeting it is anticipated that the Real-time
	will occur regarding the developed Area Description for a Real Time		Applications and Infrastructure Area will meet and its ongoing work program will be an item for discussion. This Internet Draft has been prepared
	Applications and Infrastructure Area, to be developed by the
	Transport and Applications ADs and the WG Chairs involved for
	discussion with the community. This Internet Draft has been prepared
	to share the relevant portions of the PTSC current work program with		to share the relevant portions of the PTSC current work program with
	the IETF. It is hoped that awareness of the Packet Technologies		the IETF. It is hoped that awareness of the Packet Technologies
	Systems Committee (PTSC) work program will allow for more informed		Systems Committee (PTSC) work program will allow for more informed
	discussions to occur.		discussions to occur.
	The PTSC defines its work program in the context of Issues. The PTSC		The PTSC defines its work program in the context of Issues. The PTSC
	operates on the principle that one deliverable is typically produced		operates on the principle that one deliverable is typically produced
	under one identified Issue (or project if you wish). It is important		under one identified Issue (or project if you wish). It is important
	to understand that the PTSC is quite prepared to recommend adoption		to understand that the PTSC is quite prepared to recommend adoption
	of existing standards should they be available and appropriate.		of existing standards should they be available and appropriate.
	skipping to change at page 3, line 45 ¶		skipping to change at page 5, line ? ¶
	While the full PTSC work program is publicly available and can be		While the full PTSC work program is publicly available and can be
	found at: http://www.atis.org/0191/issues.asp, this document will		found at: http://www.atis.org/0191/issues.asp, this document will
	identify those items that are related to this topical area and that		identify those items that are related to this topical area and that
	are active.		are active.
	2.1. IP Interconnection, and Services & Capabilities		2.1. IP Interconnection, and Services & Capabilities
	The following issue statements cover the topics related to general		The following issue statements cover the topics related to general
	network interconnection:		network interconnection:
	Issue S0009 - Authorizes development of a standard that defines the
	NNI interface to promote IP-IP interconnection between carriers in
	support of multi-media services.
	Issue S0010 - Authorizes development of an update to the interworking		Issue S0010 - Authorizes development of an update to the interworking
	requirements defined in T1.679 (SIP-I), as new RFCs become		requirements defined in T1.679 (SIP-I), as new RFCs become
	approved and as ITU-T Recommendations are modified.		approved and as ITU-T Recommendations are modified.
	Issue S0014 - Authorizes development of a Technical Report assessing		Issue S0014 - Authorizes development of a Technical Report assessing
	which industry groups are developing operator services-related		which industry groups are developing operator services-related
	standards for next generation equipment and what, if any, common		standards for next generation equipment and what, if any, common
	functions and architectures are emerging in support of operator		functions and architectures are emerging in support of operator
	services in the IP space.		services in the IP space.
	Issue S0018 - Authorizes development of a Technical Report that		Issue S0018 - Authorizes development of a Technical Report that
	defines an implementable architecture in support of IP QoS & RACs		defines an implementable architecture in support of IP QoS & RACs
	for USA networks.		for USA networks.
	Issue S0019 - Authorizes development of a Technical Report that		Issue S0019 - Authorizes development of a Technical Report that
	defines an implementable architecture in support of IP QoS & RACs		defines an implementable architecture in support of IP QoS & RACs
	for USA networks.		for USA networks.
	Issue S0020 - Supporting phased migration of existing services and
	CPE to an IP environment.
	Issue S0029 - An Interworking Standard to Support ANSI Extensions to
	NSS.
	Issue S0021 - Authorizes development of a Technical Report describing		Issue S0021 - Authorizes development of a Technical Report describing
	operator services functions and a common nomenclature and in		operator services functions and a common nomenclature and in
	support of operator services in the IP space.		support of operator services in the IP space.
	Issue S0023 - Authorizes development of Technical Report that		Issue S0023 - Authorizes development of Technical Report that
	specifies a set of requirements for communicating IP traffic		specifies a set of requirements for communicating IP traffic
	priority and QoS parameters between applications and the IP		priority and QoS parameters between applications and the IP
	transport. Specific aspects of such a work program are the		transport. Specific aspects of such a work program are the
	following:		following:
	Call/Session Flow Identification		Call/Session Flow Identification
	skipping to change at page 5, line 22 ¶		skipping to change at page 5, line ? ¶
	networks and within a single network domain.		networks and within a single network domain.
	Issue S0027 - Authorizes development of a standard for a signaling/		Issue S0027 - Authorizes development of a standard for a signaling/
	control interface between an End User's SIP UA and an IP Service		control interface between an End User's SIP UA and an IP Service
	Provider, with the focus on layer 4 and above, application		Provider, with the focus on layer 4 and above, application
	signaling and control. In addition to defining the interface in		signaling and control. In addition to defining the interface in
	support of the application services, the document will also		support of the application services, the document will also
	include procedures and call/signaling flows for device bootstrap,		include procedures and call/signaling flows for device bootstrap,
	discovery and data profile configuration.		discovery and data profile configuration.
			Issue S0029 – Authoriaes development of an Interworking Standard to Support ANSI Extensions to NSS.
	Issue S0030 - Authorizes development of a Technical Report that		Issue S0030 - Authorizes development of a Technical Report that
	documents signaling to support Call Admission Control and Traffic		documents signaling to support Call Admission Control and Traffic
	Management capabilities and procedures to be used between two IP		Management capabilities and procedures to be used between two IP
	service providers, or within a service provider's domain.		service providers, or within a service provider's domain.
	Issue S0031 - Authorizes development of a Technical Report that		Issue S0031 - Authorizes development of a Technical Report that
	recommends application of packet priority markings and call		recommends application of packet priority markings and call
	processing in managed IP networks.		processing in managed IP networks.
			Issue S0040 Authorizes extension of the NNI VoIP IP-IP interconnection standard, intended to facilitate interconnection between carriers, to address multimedia services in NGN
	2.2. IP Emergency Telecommunication Services		2.2. IP Emergency Telecommunication Services
	Issue S0016 - Authorizes development of a Technical Report that		Issue S0038 Authorizes development of a standard, applicable to managed IP networks using an NGN architecture, to support “911” Service.
	defines protocol and procedures for supporting ETS in IP networks.
	This will include:		Issue S0039 Authorizes development of a standard that recommends application of packet priority markings and call processing in managed IP networks based on future additions to DiffServ Code Points, such as a second Expedited Forwarding queue (with associated drop precedence, if applicable).
	Procedures and call flows for authorizing ETS users;
	Origination, termination and routing of ETS traffic in a		Issue S0041 Authorizes development of a standard that defines protocol and procedures for supporting ETS in NGN/IMS architectures, with a focus on security and authentication on IP access
	multiple service-provider environment;
	Population of control messages;		Issue S0043 Authorizes development of a Technical report that captures the Technical Requirements that define the network element requirements for ETS Phase 1
	Interworking between IP and other network types (e.g. PSTN,
	Wireless).		Issue 45 Authorizes development of a Technical report that specifies the service requirements for ETS in an NGN environment
			Issue 48 Authorizes development of ANSI IMS Standards
	2.3. Security		2.3. Security
	2.3.1. Security at NNIs and UNIs		2.3.1. Security at NNIs and UNIs
	As telecom networks migrate the Network-to Network Interface (NNI)		As telecom networks migrate the Network-to Network Interface (NNI)
	from circuit switched to IP, there is a need for network control		from circuit switched to IP, there is a need for network control
	security related specifications/ and standards which define the NNI		security related specifications/ and standards which define the NNI
	and the User Network Interface (UNI).		and the User Network Interface (UNI).
	skipping to change at page 6, line 21 ¶		skipping to change at page 6, line 21 ¶
	The security related standards being produced by the PTSC are as		The security related standards being produced by the PTSC are as
	described in the issue statements below follows(note that issue		described in the issue statements below follows(note that issue
	statements describe the deliverables of the PTSC):		statements describe the deliverables of the PTSC):
	Issue S0003 - Authorizes development of a standard which provides a		Issue S0003 - Authorizes development of a standard which provides a
	roadmap view of a subtending suite of standards, technical		roadmap view of a subtending suite of standards, technical
	reports, and requirements documents which provide a consistent set		reports, and requirements documents which provide a consistent set
	of baseline security recommendations for the control and signaling		of baseline security recommendations for the control and signaling
	plane.		plane.
	Issue S0004 - Authorizes development of a standard which describes
	generic control and signaling security issues applicable to any
	signaling network.
	Issue S0005- Authorizes development of a standard that describes
	security in the SS7/BICC network and NNI connection between the
	SS7/BICC network and any other network.
	Issue S0006 - Authorizes development of a standard that describes		Issue S0006 - Authorizes development of a standard that describes
	security issues specific to a VoP or Multimedia network		security issues specific to a VoP or Multimedia network
	Issue S0007 - Authorizes development of a standard that addresses		Issue S0007 - Authorizes development of a standard that addresses
	security issues specific to the UNI access.		security issues specific to the UNI access.
			Issue S0046 Authorizes develop a standard that provides recommendations and specifies requirements for NGN Security based on the ATIS NGN Architecture.
	2.3.2. Security Mechanisms for Messaging Applications		2.3.2. Security Mechanisms for Messaging Applications
	The following issue statement covers the Security Mechanisms for		The following issue statement covers the Security Mechanisms for
	Messaging Applications:		Messaging Applications:
	Issue S0032 - Authorizes development of a Technical Report that		Issue S0032 - Authorizes development of a Technical Report that
	details the minimum security mechanisms that carriers should		details the minimum security mechanisms that carriers should
	invoke, based on business objectives and policies for VoIP		invoke, based on business objectives and policies for VoIP
	messaging applications. The security mechanisms will address		messaging applications. The security mechanisms will address
	aspects related to SPIT and application layer DoS attacks in both		aspects related to SPIT and application layer DoS attacks in both
	skipping to change at page 7, line 11 ¶		skipping to change at page 7, line 11 ¶
	The following issue statement covers the End to End User		The following issue statement covers the End to End User
	Authentication and Signaling Security:		Authentication and Signaling Security:
	Issue S0033 - Authorizes development of a Technical Report to		Issue S0033 - Authorizes development of a Technical Report to
	address:		address:
	>End-to-end security transiting multiple domains		>End-to-end security transiting multiple domains
	>A mechanism(s) for a user to validate end-to-end security in		>A mechanism(s) for a user to validate end-to-end security in
	the presence of a "man in the middle network".		the presence of a "man in the middle network".
			Issued S0051 Authorizes development of a standard that specifies a harmonized IdM approach for the ATIS NGN architecture
	2.4. Lawfully Authorized Electronic Surveillance		2.4. Lawfully Authorized Electronic Surveillance
	The following issue statements cover the topics related to Lawfully		The following issue statements cover the topics related to Lawfully
	Authorized Electronic Surveillance (LAES):		Authorized Electronic Surveillance (LAES):
	Issue S0001 - Authorizes development of preparation of version 2 of		Issue S0001 - Authorizes development of preparation of version 2 of
	American National Standard T1.678 Lawfully Authorized Electronic		American National Standard T1.678 Lawfully Authorized Electronic
	Surveillance (LAES) for Voice over Packet Technologies in Wireline		Surveillance (LAES) for Voice over Packet Technologies in Wireline
	Telecommunications Networks, which can serve as a safe harbor		Telecommunications Networks, which can serve as a safe harbor
	document for LAES in support of Voice services over Packet-mode		document for LAES in support of Voice services over Packet-mode
	skipping to change at page 7, line 37 ¶		skipping to change at page 7, line 39 ¶
	Issue S0022 - Authorizes development of a Technical Report to		Issue S0022 - Authorizes development of a Technical Report to
	describe the evolution of the LAES capabilities and solutions		describe the evolution of the LAES capabilities and solutions
	specified in existing American National Standards to support NGN		specified in existing American National Standards to support NGN
	Issue S0035 - Authorizes development of a Technical Report that		Issue S0035 - Authorizes development of a Technical Report that
	describes various network and service provider scenarios and the		describes various network and service provider scenarios and the
	applicability and use of CALEA safeharbor and other LAES standards		applicability and use of CALEA safeharbor and other LAES standards
	documents (e.g. ANS T1.678, T1.ipna) to elements of the service		documents (e.g. ANS T1.678, T1.ipna) to elements of the service
	providers involved.		providers involved.
			Issue S0037 Authorizes development of a Technical Report that identifies detailed requirements and assesses their feasibility and the complexity of implementation, for reporting LAES events.
			Issue S0047 Authorizes the development of a Supplement to ATIS-1000678-2006, Lawfully Authorized Electronic Surveillance (LAES) for Voice over Packet Technologies in Wireline Telecommunication Networks
			Issue S0049 Authorizes the development of a Technical Report describing an appropriate buffering (short term storage) capability and corresponding file structure to support LAES.
	2.5. Program Items related to IP Network Testing		2.5. Program Items related to IP Network Testing
	S0008 - Authorizes development of a Technical Report that provides a		S0008 - Authorizes development of a Technical Report that provides a
	testing framework in order to ensure interoperability for IP-IP		testing framework in order to ensure interoperability for IP-IP
	interconnection between networks.		interconnection between networks.
			Issue S0050 Authorizes development of a Technical Report that provides a testing framework in order to help ensure interoperability for VoIP CPE-network interconnection.
	3. Summary		3. Summary
	This Internet Draft has been prepared to share the relevant portions		This Internet Draft has been prepared to share the relevant portions
	of the ATIS PTSC current work program, which may be related to this		of the ATIS PTSC current work program, which may be related to this
	topic and other topics, with the IETF. It is hoped that awareness of		topic and other topics, with the IETF. It is hoped that awareness of
	the Packet Technologies Systems Committee work program will allow for		the Packet Technologies Systems Committee work program will allow for
	a more informed discussion during the 64th IETF Meeting.		a more informed discussion during the 64th IETF Meeting.
	The PTSC wishes to maintain a good working relationship with the IETF		The PTSC wishes to maintain a good working relationship with the IETF
	and sees the IETF as a rich potential source of IP related protocols.		and sees the IETF as a rich potential source of IP related protocols.
	4. Security Considerations		4. Security Considerations
	This ID discusses among other things the security work program of the		This ID discusses among other things the security work program of the
	PTSC. There are no security issues raised by this ID.		PTSC. There are no security issues raised by this ID.
	5. Changes from previous		5. Changes from previous
	A new work item has been added to section 2.4, Issue S0035.		Work items deleted:
			Issue S0004, S0005, S0016 and S0020
			Work items added:
			Issue S0037, S0038, S0039, S0040, S0041, S0043, S0045, S0046, S0047, S0048, S0050 and S0051
	6. References		6. References
	[I-D.ietf-sipping-config-framework]		[I-D.ietf-sipping-config-framework]
	Petrie, D., "A Framework for Session Initiation Protocol		Petrie, D., "A Framework for Session Initiation Protocol
	User Agent Profile Delivery",		User Agent Profile Delivery",
	draft-ietf-sipping-config-framework-07 (work in progress),		draft-ietf-sipping-config-framework-07 (work in progress),
	July 2005.		July 2005.
	[I-D.petrie-sipping-profile-datasets]		[I-D.petrie-sipping-profile-datasets]
End of changes. 17 change blocks.
	40 lines changed or deleted		40 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/