SIPPING                                                         M. Dolly
Internet-Draft                                                 AT&T Labs
Expires: March 24, 2007                                          B. Hall
                                                                     SBC
                                                              J. Zebarth
                                                                  Nortel
                                                        October 23, 2006


                         ATIS PTSC Work Program
                  draft-dolly-sipping-atis-ptsc-03.txt

Status of this Memo

   By submitting this Internet-Draft, each author represents that any
   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
   aware will be disclosed, in accordance with Section 6 of BCP 79.

   Internet-Drafts are working documents of the Internet Engineering
   Task Force (IETF), its areas, and its working groups.  Note that
   other groups may also distribute working documents as Internet-
   Drafts.

   Internet-Drafts are draft documents valid for a maximum of six months
   and may be updated, replaced, or obsoleted by other documents at any
   time.  It is inappropriate to use Internet-Drafts as reference
   material or to cite them other than as "work in progress."

   The list of current Internet-Drafts can be accessed at
   http://www.ietf.org/ietf/1id-abstracts.txt.

   The list of Internet-Draft Shadow Directories can be accessed at
   http://www.ietf.org/shadow.html.

   This Internet-Draft will expire on March 24, 2007.

Copyright Notice

   Copyright (C) The Internet Society (2006).

Abstract

   At the 67th San Diego IETF Meeting it is anticipated that the 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 to share the relevant portions



Dolly, et al.           Expires March 24, 2007               [Page 1]


Internet-Draft           ATIS PTSC Work Program               October 2006


   of the PTSC current work program with the IETF.  It is hoped that
   awareness of the Packet Technologies Systems Committee (PTSC) work
   program will allow for more informed discussion.


Table of Contents

   1.  Introduction . . . . . . . . . . . . . . . . . . . . . . . . .  3
   2.  PTSC Work Program  . . . . . . . . . . . . . . . . . . . . . .  3
     2.1.  IP Interconnection, and Services & Capabilities  . . . . .  3
     2.2.  IP Emergency Telecommunication Services  . . . . . . . . .  5
     2.3.  Security . . . . . . . . . . . . . . . . . . . . . . . . .  5
       2.3.1.  Security at NNIs and UNIs  . . . . . . . . . . . . . .  5
       2.3.2.  Security Mechanisms for Messaging Applications . . . .  6
       2.3.3.  End to End User Authentication and Signaling
               Security . . . . . . . . . . . . . . . . . . . . . . .  6
     2.4.  Lawfully Authorized Electronic Surveillance  . . . . . . .  7
     2.5.  Program Items related to IP Network Testing  . . . . . . .  7
   3.  Summary  . . . . . . . . . . . . . . . . . . . . . . . . . . .  7
   4.  Security Considerations  . . . . . . . . . . . . . . . . . . .  8
   5.  Changes from previous  . . . . . . . . . . . . . . . . . . . .  8
   6.  References . . . . . . . . . . . . . . . . . . . . . . . . . .  8
   Appendix A.  Acknowledgments . . . . . . . . . . . . . . . . . . .  9
   Authors' Addresses . . . . . . . . . . . . . . . . . . . . . . . . 10
   Intellectual Property and Copyright Statements . . . . . . . . . . 11


























Dolly, et al.           Expires March 24, 2007               [Page 2]


Internet-Draft           ATIS PTSC Work Program               October 2006


1.  Introduction

   At the 67th San Diego IETF Meeting it is anticipated that the 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
   to share the relevant portions of the PTSC current work program with
   the IETF.  It is hoped that awareness of the Packet Technologies
   Systems Committee (PTSC) work program will allow for more informed
   discussions to occur.

   The PTSC defines its work program in the context of Issues.  The PTSC
   operates on the principle that one deliverable is typically produced
   under one identified Issue (or project if you wish).  It is important
   to understand that the PTSC is quite prepared to recommend adoption
   of existing standards should they be available and appropriate.

   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.


2.  PTSC Work Program

   The PTSC is an ATIS sponsored technical committee.  The PTSC develops
   and recommends standards and Technical Reports related to packet
   based services, architectures, and signaling, in addition to working
   with related subjects under consideration in other North American and
   international standards bodies.  The PTSC is a major source of
   proposed United States Positions to the ITU.

   While the full PTSC work program is publicly available and can be
   found at: http://www.atis.org/0191/issues.asp, this document will
   identify those items that are related to this topical area and that
   are active.

2.1.  IP Interconnection, and Services & Capabilities

   The following issue statements cover the topics related to general
   network interconnection:

   Issue S0010 - Authorizes development of an update to the interworking
      requirements defined in T1.679 (SIP-I), as new RFCs become
      approved and as ITU-T Recommendations are modified.

   Issue S0014 - Authorizes development of a Technical Report assessing
      which industry groups are developing operator services-related
      standards for next generation equipment and what, if any, common
      functions and architectures are emerging in support of operator
      services in the IP space.

   Issue S0018 - Authorizes development of a Technical Report that
      defines an implementable architecture in support of IP QoS & RACs
      for USA networks.

   Issue S0019 - Authorizes development of a Technical Report that
      defines an implementable architecture in support of IP QoS & RACs
      for USA networks.

   Issue S0021 - Authorizes development of a Technical Report describing
      operator services functions and a common nomenclature and in
      support of operator services in the IP space.

   Issue S0023 - Authorizes development of Technical Report that
      specifies a set of requirements for communicating IP traffic
      priority and QoS parameters between applications and the IP
      transport.  Specific aspects of such a work program are the
      following:
         Call/Session Flow Identification
         Vertical Interface Requirements

   Issue S0024 - Authorizes development of a Technical Report that
      defines the Session/Border Control Functions (S/BCF), performed
      within various different network types.  The functions required
      depend on the interface.  The document will include illustrative
      examples of physical realizations of the functions.  The physical
      distribution of the functions will depend on scale, operational
      and application needs.

   Issue S0025 - Authorizes development of a Standard that defines the
      NNI numbering and routing capabilities and procedures to promote
      IP-IP interconnection between carriers in support of multi-media
      services.  This includes the support of carrier based ENUM.

   Issue S0026 - Authorizes development of a Technical Report, in the
      form of a users guide, on how to use SIP History-Info, between
      networks and within a single network domain.

   Issue S0027 - Authorizes development of a standard for a signaling/
      control interface between an End User's SIP UA and an IP Service
      Provider, with the focus on layer 4 and above, application
      signaling and control.  In addition to defining the interface in
      support of the application services, the document will also
      include procedures and call/signaling flows for device bootstrap,
      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
      documents signaling to support Call Admission Control and Traffic
      Management capabilities and procedures to be used between two IP
      service providers, or within a service provider's domain.

   Issue S0031 - Authorizes development of a Technical Report that
      recommends application of packet priority markings and call
      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

   Issue S0038 Authorizes development of a standard, applicable to managed IP networks using an NGN architecture, to support “911” Service.

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).

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

   Issue S0043 Authorizes development of a Technical report that captures the Technical Requirements that define the network element requirements for ETS Phase 1

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.1.  Security at NNIs and UNIs

   As telecom networks migrate the Network-to Network Interface (NNI)
   from circuit switched to IP, there is a need for network control
   security related specifications/ and standards which define the NNI
   and the User Network Interface (UNI).

   The PTSC is in the process of developing a suite of 5 Security IP



Dolly, et al.           Expires March 24, 2007               [Page 5]


Internet-Draft           ATIS PTSC Work Program               October 2006


   network interconnection related standards that deal with this
   security area.  These standards complement the security work already
   undertaken by the ATIS TMOC Committee
   (http://www.atis.org/0130/index.asp) and the security work currently
   underway in the ATIS PRQC Committee
   (http://www.atis.org/0010/index.asp).

   The security related standards being produced by the PTSC are as
   described in the issue statements below follows(note that issue
   statements describe the deliverables of the PTSC):

   Issue S0003 - Authorizes development of a standard which provides a
      roadmap view of a subtending suite of standards, technical
      reports, and requirements documents which provide a consistent set
      of baseline security recommendations for the control and signaling
      plane.



   Issue S0006 - Authorizes development of a standard that describes
      security issues specific to a VoP or Multimedia network

   Issue S0007 - Authorizes development of a standard that addresses
      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

   The following issue statement covers the Security Mechanisms for
   Messaging Applications:

   Issue S0032 - Authorizes development of a Technical Report that
      details the minimum security mechanisms that carriers should
      invoke, based on business objectives and policies for VoIP
      messaging applications.  The security mechanisms will address
      aspects related to SPIT and application layer DoS attacks in both
      signaling and data planes.

2.3.3.  End to End User Authentication and Signaling Security

   The following issue statement covers the End to End User
   Authentication and Signaling Security:




Dolly, et al.           Expires March 24, 2007               [Page 6]


Internet-Draft           ATIS PTSC Work Program               October 2006


   Issue S0033 - Authorizes development of a Technical Report to
      address:
         >End-to-end security transiting multiple domains
         >A mechanism(s) for a user to validate end-to-end security in
         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

   The following issue statements cover the topics related to Lawfully
   Authorized Electronic Surveillance (LAES):

   Issue S0001 - Authorizes development of preparation of version 2 of
      American National Standard T1.678 Lawfully Authorized Electronic
      Surveillance (LAES) for Voice over Packet Technologies in Wireline
      Telecommunications Networks, which can serve as a safe harbor
      document for LAES in support of Voice services over Packet-mode
      technologies in a wireline environment.

   Issue S0002 - Authorizes development of a new standard to specify
      LAES support for Public IP Network Access Service (PIPNAS)
      provider.

   Issue S0022 - Authorizes development of a Technical Report to
      describe the evolution of the LAES capabilities and solutions
      specified in existing American National Standards to support NGN

   Issue S0035 - Authorizes development of a Technical Report that
      describes various network and service provider scenarios and the
      applicability and use of CALEA safeharbor and other LAES standards
      documents (e.g.  ANS T1.678, T1.ipna) to elements of the service
      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

   S0008 - Authorizes development of a Technical Report that provides a
      testing framework in order to ensure interoperability for IP-IP
      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

   This Internet Draft has been prepared to share the relevant portions
   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
   the Packet Technologies Systems Committee work program will allow for
   a more informed discussion during the 64th IETF Meeting.

   The PTSC wishes to maintain a good working relationship with the IETF



Dolly, et al.           Expires March 24, 2007               [Page 7]


Internet-Draft           ATIS PTSC Work Program               October 2006


   and sees the IETF as a rich potential source of IP related protocols.


4.  Security Considerations

   This ID discusses among other things the security work program of the
   PTSC.  There are no security issues raised by this ID.


5.  Changes from previous

   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

   [I-D.ietf-sipping-config-framework]
              Petrie, D., "A Framework for Session Initiation Protocol
              User Agent Profile Delivery",
              draft-ietf-sipping-config-framework-07 (work in progress),
              July 2005.

   [I-D.petrie-sipping-profile-datasets]
              Petrie, D., "A Schema and Guidelines for Defining Session
              Initiation Protocol User Agent  Profile Data Sets",
              draft-petrie-sipping-profile-datasets-03 (work in
              progress), October 2005.

   [I-D.sinnreich-sipdev-req]
              Sinnreich, H., "SIP Telephony Device Requirements and
              Configuration", draft-sinnreich-sipdev-req-08 (work in
              progress), October 2005.

   [RFC0822]  Crocker, D., "Standard for the format of ARPA Internet
              text messages", STD 11, RFC 822, August 1982.

   [RFC2119]  Bradner, S., "Key words for use in RFCs to Indicate
              Requirement Levels", BCP 14, RFC 2119, March 1997.

   [RFC3261]  Rosenberg, J., Schulzrinne, H., Camarillo, G., Johnston,
              A., Peterson, J., Sparks, R., Handley, M., and E.
              Schooler, "SIP: Session Initiation Protocol", RFC 3261,
              June 2002.

   [RFC3265]  Roach, A., "Session Initiation Protocol (SIP)-Specific
              Event Notification", RFC 3265, June 2002.

   [RFC3470]  Hollenbeck, S., Rose, M., and L. Masinter, "Guidelines for
              the Use of Extensible Markup Language (XML) within IETF



Dolly, et al.           Expires March 24, 2007               [Page 8]


Internet-Draft           ATIS PTSC Work Program               October 2006


              Protocols", BCP 70, RFC 3470, January 2003.


Appendix A.  Acknowledgments















































Dolly, et al.           Expires March 24, 2007               [Page 9]


Internet-Draft           ATIS PTSC Work Program               October 2006


Authors' Addresses

   Martin Dolly
   AT&T Labs
   200 Laurel Avenue
   Middletowm, NJ  07748
   USA

   Phone:
   Email: mdolly AT att DOT com
   URI:


   Bob Hall
   SBC
   Austin, TX
   USA

   Phone:
   Email:
   URI:


   Joe Zebarth
   Nortel
   Ottawa, Ontario
   Canada

   Phone:
   Email:
   URI:




















Dolly, et al.           Expires March 24, 2007              [Page 10]


Internet-Draft           ATIS PTSC Work Program               October 2006


Intellectual Property Statement

   The IETF takes no position regarding the validity or scope of any
   Intellectual Property Rights or other rights that might be claimed to
   pertain to the implementation or use of the technology described in
   this document or the extent to which any license under such rights
   might or might not be available; nor does it represent that it has
   made any independent effort to identify any such rights.  Information
   on the procedures with respect to rights in RFC documents can be
   found in BCP 78 and BCP 79.

   Copies of IPR disclosures made to the IETF Secretariat and any
   assurances of licenses to be made available, or the result of an
   attempt made to obtain a general license or permission for the use of
   such proprietary rights by implementers or users of this
   specification can be obtained from the IETF on-line IPR repository at
   http://www.ietf.org/ipr.

   The IETF invites any interested party to bring to its attention any
   copyrights, patents or patent applications, or other proprietary
   rights that may cover technology that may be required to implement
   this standard.  Please address the information to the IETF at
   ietf-ipr@ietf.org.


Disclaimer of Validity

   This document and the information contained herein are provided on an
   "AS IS" basis and THE CONTRIBUTOR, THE ORGANIZATION HE/SHE REPRESENTS
   OR IS SPONSORED BY (IF ANY), THE INTERNET SOCIETY AND THE INTERNET
   ENGINEERING TASK FORCE DISCLAIM ALL WARRANTIES, EXPRESS OR IMPLIED,
   INCLUDING BUT NOT LIMITED TO ANY WARRANTY THAT THE USE OF THE
   INFORMATION HEREIN WILL NOT INFRINGE ANY RIGHTS OR ANY IMPLIED
   WARRANTIES OF MERCHANTABILITY OR FITNESS FOR A PARTICULAR PURPOSE.


Copyright Statement

   Copyright (C) The Internet Society (2006).  This document is subject
   to the rights, licenses and restrictions contained in BCP 78, and
   except as set forth therein, the authors retain all their rights.


Acknowledgment

   Funding for the RFC Editor function is currently provided by the
   Internet Society.




Dolly, et al.           Expires March 24, 2007              [Page 11]