Technical Interface: Task Identification Forms
Network Interconnection Group
TITF001.DOC - 63KB - TIF reports for the March 30, 1999 - TASK DESCRIPTION: This task involves the definition of interconnection interfaces between LEC networks and IXC networks. Services to be supported across the interfaces include toll services and toll-free services. Network interworking for service capabilities such as Calling Name and CLASS/CMS will also be addressed.
TITF001C.RTF - 19448 bytes - TASK DESCRIPTION: This task involves the definition of interconnection interfaces between LEC networks and IXC networks. Services to be supported across the interfaces include toll services and toll-free services. Network interworking for service capabilities such as Calling Name and CLASS/CMS will also be addressed - 1997/06/16 - Revised
TITF001D.DOC - 33,792 bytes - TASK DESCRIPTION: This task involves the definition of interconnection interfaces between LEC networks and IXC networks. Services to be supported across the interfaces include toll services and toll-free services. Network interworking for service capabilities such as Calling Name and CLASS/CMS will also be addressed. - 1997/06/16 - Update
TITF001F.DOC - 23040 bytes - TASK DESCRIPTION: This task involves the definition of interconnection interfaces between LEC networks and IXC networks. Services to be supported across the interfaces include toll services and toll-free services. Network interworking for service capabilities such as Calling Name and CLASS/CMS will also be addressed.
TITF001G.DOC - 39936 bytes -TASK DESCRIPTION: This task involves the definition of interconnection interfaces between LEC networks and IXC networks. Services to be supported across the interfaces include toll services and toll-free services. Network interworking for service capabilities such as Calling Name and CLASS/CMS will also be addressed. - UPDATED 1998/04/17
TITF001H.DOC - 27136 bytes - TASK DESCRIPTION: This task involves the definition of interconnection interfaces between LEC networks and IXC networks. Services to be supported across the interfaces include toll services and toll-free services. Network interworking for service capabilities such as Calling Name and CLASS/CMS will also be addressed. - UPDATED 1998/04/18
TITF001J.DOC - 27,136 bytes - TASK DESCRIPTION: This task involves the definition of interconnection interfaces between LEC networks and IXC networks. Services to be supported across the interfaces include toll services and toll-free services. Network interworking for service capabilities such as Calling Name and CLASS/CMS will also be addressed. - UPDATED 1998/04/18
Titf001k.doc - 41KB - TASK DESCRIPTION: This task involves the definition of interconnection interfaces between LEC networks and IXC networks. Services to be supported across the interfaces include toll services and toll-free services. Network interworking for service capabilities such as Calling Name and CLASS/CMS will also be addressed. - UPDATED 1998/04/18
TITF002E.DOC - 29696 bytes - Number Portability Interfaces. - 1997/06/13 - Revised
TITF002F.DOC - 48,128 bytes - Number Portability Interfaces. - 1997/06/13 - Update
TITF002G.DOC - 54,272 bytes - Number Portability Interfaces. - 1997/06/13 - Update
TITF002H.DOC - 69,632 bytes - Number Portability Interfaces. - 1997/06/13 - Update
TITF002I.DOC - 68,096 bytes - This task is to specify the interfaces required between LECs, WSPs, and IXCs for communicating the information needed to complete calls destined to a portable number.
TITF002J.DOC - 43,520 bytes - TASK DESCRIPTION: This task is to specify the interfaces required between LECs, WSPs, and IXCs for communicating the information needed to complete calls destined to a portable number. The task includes: Switch to switch interfaces needed to transmit routing information for the calls. Switch to database interfaces needed to obtain routing information associated with a portable number.
TITF002K.DOC - 60,928 bytes - TASK DESCRIPTION: This task is to specify the interfaces required between LECs, WSPs, and IXCs for communicating the information needed to complete calls destined to a protable number.
TITF002L.DOC - 70656 bytes - TASK DESCRIPTION: This task is to specify the interfaces required between LECs, WSPs, and IXCs for communicating the information needed to complete calls destined to a portable number.
TITF002M.DOC - 70656 bytes - TASK DESCRIPTION: This task is to specify the interfaces required between LECs, WSPs, and IXCs for communicating the information needed to complete calls destined to a portable number.
TITF002N.DOC - 111616 bytes - TASK DESCRIPTION: This task is to specify the interfaces required between LECs, WSPs, and IXCs for communicating the information needed to complete calls destined to a portable number. The task includes: a. Switch to switch interfaces needed to transmit routing information for the calls. b. Switch to database interfaces needed to obtain routing information associated with a portable number. The task should use the recently completed ANSI Standard T1.660, "Call Completion to a Portable Number" as the basis for developing the interface definitions. The specific interfaces required may depend on local interconnection and transiting architectures to be developed in the Network Planning SWG. - UPDATED 1998/02/13
TITF002O.DOC - 98816 bytes - TASK DESCRIPTION: This task is to specify the interfaces required between LECs, WSPs, and IXCs for communicating the information needed to complete calls destined to a portable number. The task includes: a. Switch to switch interfaces needed to transmit routing information for the calls. b. Switch to database interfaces needed to obtain routing information associated with a portable number. The task should use the recently completed ANSI Standard T1.660, "Call Completion to a Portable Number" as the basis for developing the interface definitions. The specific interfaces required may depend on local interconnection and transiting architectures to be developed in the Network Planning SWG. - UPDATED 1998/03/12
TITF002P.DOC - 128512 bytes - TASK DESCRIPTION: This task is to specify the interfaces required between LECs, WSPs, and IXCs for communicating the information needed to complete calls destined to a portable number. The task includes: a. Switch to switch interfaces needed to transmit routing information for the calls. b. Switch to database interfaces needed to obtain routing information associated with a portable number. The task should use the recently completed ANSI Standard T1.660, "Call Completion to a Portable Number" as the basis for developing the interface definitions. The specific interfaces required may depend on local interconnection and transiting architectures to be developed in the Network Planning SWG. - UPDATED 1998/03/31
TITF002Q.DOC - 151522 bytes - TASK DESCRIPTION: This task is to specify the interfaces required between LECs, WSPs, and IXCs for communicating the information needed to complete calls destined to a portable number. The task includes:a. Switch to switch interfaces needed to transmit routing information for the calls. b. Switch to database interfaces needed to obtain routing information associated with a portable number. The task should use the recently completed ANSI Standard T1.660, "Call Completion to a Portable Number" as the basis for developing the interface definitions. The specific interfaces required may depend on local interconnection and transiting architectures to be developed in the Network Planning SWG.
TITF002S.DOC - 147968 bytes - TASK DESCRIPTION: This task is to specify the interfaces required between LECs, WSPs, and IXCs for communicating the information needed to complete calls destined to a portable number. The task includes: a. Switch to switch interfaces needed to transmit routing information for the calls. b. Switch to database interfaces needed to obtain routing information associated with a portable number. The task should use the recently completed ANSI Standard T1.660, "Call Completion to a Portable Number" as the basis for developing the interface definitions.The specific interfaces required may depend on local interconnection and transiting architectures to be developed in the Network Planning SWG. - UPDATED 1998/05/28
TITF002T.DOC - 129,536 bytes - TASK DESCRIPTION: This task is to specify the interfaces required between LECs, WSPs, and IXCs for communicating the information needed to complete calls destined to a portable number. The task includes: a. Switch to switch interfaces needed to transmit routing information for the calls. b. Switch to database interfaces needed to obtain routing information associated with a portable number. The task should use the recently completed ANSI Standard T1.660, "Call Completion to a Portable Number" as the basis for developing the interface definitions.The specific interfaces required may depend on local interconnection and transiting architectures to be developed in the Network Planning SWG. - UPDATED 1998/05/28
TITF003.DOC - 48,128 bytes - TASK DESCRIPTION: In order to facilitate interconnection between carriers there must be an establishment of a Minimum SS7 Message Set . This intent of this TIF is to 1. provide a recommendation for the Minimum SS7 Set for LEC to LEC interconnection. 2. provide a recommendation for how all LECs will handle calls that have messages which are not included in the Minimum SS7 Set
TITF004I.DOC - 24576 bytes - TASK DESCRIPTION: In order to identify the various loop types available for unbundling, there is a need for Stentor to disclose the technical specifications for all loop types currently used by ILECs to provide local exchange services. A need to establish a disclosure process for future loop types employed by ILECs in the provision of future local exchange services has also been identified.
TITF004J.DOC - 26,112 bytes - TASK DESCRIPTION: In order to identify the various loop types available for unbundling, there is a need for Stentor to disclose the technical specifications for all loop types currently used by ILECs to provide local exchange services. A need to establish a disclosure process for future loop types employed by ILECs in the provision of future local exchange services has also been identified.
TITF04L.RTF - 53952 bytes - In order to identify the various loop types available for unbundling, there is a need for Stentor to disclose the technical specifications for all loop types currently used by ILECs to provide local exchange services. A need to establish a disclosure process for future loop types employed by ILECs in the provision of future local exchange services has also been identified
TITF004M.DOC - 32768 bytes - TASK DESCRIPTION: In order to identify the various loop types available for unbundling, there is a need for Stentor to disclose the technical specifications for all loop types currently used by ILECs to provide local exchange services. A need to establish a disclosure process for future loop types employed by ILECs in the provision of future local exchange services has also been identified.
TITF04N.DOC - 32768 bytes - TASK DESCRIPTION: In order to identify the various loop types available for unbundling, there is a need for Stentor to disclose the technical specifications for all loop types currently used by ILECs to provide local exchange services. A need to establish a disclosure process for future loop types employed by ILECs in the provision of future local exchange services has also been identified.
TITF04P.DOC - 34304 bytes - TASK DESCRIPTION: In order to identify the various loop types available for unbundling, there is a need for Stentor to disclose the technical specifications for all loop types currently used by ILECs to provide local exchange services. A need to establish a disclosure process for future loop types employed by ILECs in the provision of future local exchange services has also been identified.
TITF04Q.DOC - 36352 bytes - TASK DESCRIPTION: In order to identify the various loop types available for unbundling, there is a need for Stentor to disclose the technical specifications for all loop types currently used by ILECs to provide local exchange services. A need to establish a disclosure process for future loop types employed by ILECs in the provision of future local exchange services has also been identified.
TITF04R6.DOC - 40448 bytes - TASK DESCRIPTION: In order to identify the various loop types available for unbundling, there is a need for Stentor to disclose the technical specifications for all loop types currently used by ILECs to provide local exchange services. A need to establish a disclosure process for future loop types employed by ILECs in the provision of future local exchange services has also been identified.
TITF04S.DOC - 43008 bytes - TASK DESCRIPTION: In order to identify the various loop types available for unbundling, there is a need for Stentor to disclose the technical specifications for all loop types currently used by ILECs to provide local exchange services. A need to establish a disclosure process for future loop types employed by ILECs in the provision of future local exchange services has also been identified.
TITF04T.DOC - 46,592 bytes - TASK DESCRIPTION: In order to identify the various loop types available for unbundling, there is a need for Stentor to disclose the technical specifications for all loop types currently used by ILECs to provide local exchange services. A need to establish a disclosure process for future loop types employed by ILECs in the provision of future local exchange services has also been identified.
TITF04U.DOC - 50,176 bytes - TASK DESCRIPTION: In order to identify the various loop types available for unbundling, there is a need for Stentor to disclose the technical specifications for all loop types currently used by ILECs to provide local exchange services. A need to establish a disclosure process for future loop types employed by ILECs in the provision of future local exchange services has also been identified.
TITF04V.doc - 22KB - Oct 27/98 meeting - TASK DESCRIPTION: In order to identify the various loop types available for unbundling, there is a need for Stentor to disclose the technical specifications for all loop types currently used by ILECs to provide local exchange services. A need to establish a disclosure process for future loop types employed by ILECs in the provision of future local exchange services has also been identified.
TITF04W.doc - 52KB - TASK DESCRIPTION: In order to identify the various loop types available for unbundling, there is a need for Stentor to disclose the technical specifications for all loop types currently used by ILECs to provide local exchange services. A need to establish a disclosure process for future loop types employed by ILECs in the provision of future local exchange services has also been identified.
TITF005.DOC - 16896 bytes - TASK DESCRIPTION: In order to complete the technical interface specifications, there must a decision regarding the base reference spec to be used by the industry. - UPDATED 1997/08/12
TITF006.DOC - 14KB
TITF006.DOC - 103KB - TIF reports for the March 30, 1999 - TASK DESCRIPTION: In order to complete the Calling Name interface specifications, there must a decision regarding the interface to be used to exchange CNAM information between carriers. - UPDATED 1999/03/30
TITF006A.DOC - 25,600 bytes - TASK DESCRIPTION: In order to complete the Calling Name interface specifications, there must a decision regarding the interface to be used to exchange CNAM information between carriers. - UPDATED 1997/10/14
TITF006B.DOC - 61,825 bytes - TASK DESCRIPTION: In order to complete the Calling Name interface specifications, there must a decision regarding the interface to be used to exchange CNAM information between carriers. - UPDATED 1997/10/28
TITF006B.RTF - Rich*Text - 67,386 bytes - In order to complete the Calling Name interface specifications, there must a decision regarding the interface to be used to exchange CNAM information between carriers.
TITF006C.DOC - 67,072 bytes - TASK DESCRIPTION: In order to complete the Calling Name interface specifications, there must a decision regarding the interface to be used to exchange CNAM information between carriers.
TITF006D.DOC - 69,120 bytes - TASK DESCRIPTION: In order to complete the Calling Name Interface Specification, there must be a decision regarding the interface to be used to exchange CNAM information between carriers.
TITF006G.DOC - 54272 bytes - TASK DESCRIPTION: In order to complete the Calling Name interface specifications, there must a decision regarding the interface to be used to exchange CNAM information between carriers.
TITF007.DOC - 20864 bytes - TASK DESCRIPTION: There is a need to determine how interfaces are negotiated between LECs when there are several possible interfaces in contention. This necessitates the establishment of appropriate criteria and procedures to select suitable specifications for implementing local service competition in Canada, in order to avoid interoperability and operational issues which could adversely impact the availability of future competitive service. - 1997/07/30
TITF008.DOC - 13312 bytes - TASK DESCRIPTION: Develop interface specifications identifying characteristics of the LEC to LEC network interface specific to calls originating from or terminating to ISDN accesses.
TITF008A.DOC - 27,136 bytes
TITF008b.doc - 22KB - TASK DESCRIPTION: Develop interface specifications identifying characteristics of the LEC to LEC network interface specific to calls originating from or terminating to ISDN accesses.
TITF009.DOC - 31KB - TIF reports for the March 30, 1999 - TASK DESCRIPTION: In the Commission’s August 5, 1998 letter on Telecom Order 98-626 and Telecom Order 98-8, the TI SWG was requested to initiate a task to identify issues and to ensure that such issues are addressed in the appropriate CISC subgroups.
- Date modified: