Base specifications Sample Clauses

Base specifications. A conforming entity shall implement the following specifications: • IETF RFC 3261, "SIP: Session Initiation Protocol" • IETF RFC 3262, "Reliability of Provisional Responses in SIP" • IETF RFC 3311, “The SIP Update Method” • IETF RFC 3264, “An Offer / Answer Model with SDP” • IETF RFC 3265, “SIP Specific Event Notification” • IETF RFC 3323, “A Privacy Mechanism for SIP” • IETF RFC 3515, “The SIP REFER Method” • IETF draft-ietf-sip-referredby-05.txt, “The SIP Referred-By Mechanism”
Sample 1
AutoNDA by SimpleDocs
Base specifications. A conforming MGC shall implement the following specifications: • IETF RFC 3261, "TEL: Session Initiation Protocol" • IETF RFC 2976, "The SIP INFO Method" • IETF RFC 3204, "MIME media types for ISUP and QSIG Objects" • IETF RFC 3372, "SIP for Telephones (SIP-T): Context and Architectures" • IETF RFC 3262, "Reliability of Provisional Responses in SIP" • IETF RFC 3311, “The SIP Update Method” • IETF RFC 3264, “An Offer / Answer Model with SDP” • ITU-T Q.1912.5, “Inter-working between SIP and BICC/ISUP”
Sample 1
Base specifications. A conforming CA shall implement the following specifications: • IETF RFC 3261, "SIP: Session Initiation Protocol" • IETF RFC 3262, "Reliability of Provisional Responses in SIP" • IETF RFC 3311, “The SIP Update Method” • IETF RFC 3264, “An Offer / Answer Model with SDP” • IETF RFC 3515, “The SIP REFER Method” • IETF draft-ietf-sip-referredby-05.txt, “The SIP Referred-By Mechanism” • IETF draft-ietf-sip-resource-priority-03.txt “Resource Priority for SIP”
Sample 1
Base specifications. A conformant entity MUST support the following base specifications. The specifications are grouped into a) common specifications, b) those applicable within the MSFR3 network and c) those applicable between the MSFR3 network edge and the external network (e.g. to/from the UA). Common specifications: • IETF RFC 3261, "SIP: Session Initiation Protocol" • IETF RFC 3262, "Reliability of Provisional Responses in SIP" • IETF RFC 3311, “The SIP Update Method” • IETF RFC 3264, “An Offer / Answer Model with SDP” • IETF RFC 3265, “SIP Specific Event Notification” • IETF RFC 3515, “The SIP REFER Method” • IETF RFC 3892, “The SIP Referred-By Mechanism” • IETF RFC 3966, “The TEL URI for Telephone Numbers”, • RFC 3581 (August 2003): "An Extension to the Session Initiation Protocol (SIP) for Symmetric Response Routing". • IETF RFC 4028, “Session Timers in SIP”. • IETF RFC 3891,"The Session Inititiation Protocol (SIP) "Replaces" Header". • IETF RFC 3911, "The Session Inititiation Protocol (SIP) "Join" Header". • IETF RFC 3312, “Integration of Resource Management & SIP” • IETF RFC 3841,"Caller Preferences for the Session Initiation Protocol (SIP)" • IETF RFC 3840, "Indicating User Agent Capabilities in the Session Initiation Protocol (SIP) • IETF RFC 2617, “HTTP Authentication – Basic & Digest Authentication” • IETF RFC 3428, “SIP Extensions for Instant Messaging”, • IETF RFC 3903, “An Event State Publication extension to SIP”, • IETF RFC 3856, “A Presence Event Package for SIP”, • IETF RFC 3857, “A Watcher Information Event Package for SIP” • IETF RFC 3323, “A Privacy Mechanism for SIP” • IETF RFC 3325, “Private Extensions to SIP for Asserted Identity within trusted networks” Internal MSFR3 specifications: • IETF RFC 3455, “P-Header Extensions for 3GPP” • IETF RFC 3680, "A Session Initiation Protocol (SIP) Event Package for Registrations". • IETF RFC 3608, “SIP Extension Header Field for Service Route Discovery during registration”. • IETF RFC 3327, “SIP Extension Header Field for registering non-adjacent contacts”.
Sample 1

Related to Base specifications

  • The Specifications The Specifications are that portion of the Contract Documents consisting of the written requirements for materials, equipment, systems, standards and workmanship for the Work, and performance of related services.

  • DAF Specifications Developer shall submit initial specifications for the DAF, including System Protection Facilities, to Connecting Transmission Owner and NYISO at least one hundred eighty (180) Calendar Days prior to the Initial Synchronization Date; and final specifications for review and comment at least ninety (90) Calendar Days prior to the Initial Synchronization Date. Connecting Transmission Owner and NYISO shall review such specifications to ensure that the DAF are compatible with the technical specifications, operational control, and safety requirements of the Connecting Transmission Owner and NYISO and comment on such specifications within thirty (30) Calendar Days of Developer’s submission. All specifications provided hereunder shall be deemed to be Confidential Information.

  • Technical Specifications The Technical Specifications furnished on the CD are intended to establish the standards for quality, performance and technical requirements for all labor, workmanship, material, methods and equipment necessary to complete the Work. When specifications and drawings are provided or referenced by the County, these are to be considered part of the Scope of Work, and to be specifically documented in the Detailed Scope of Work. For convenience, the County supplied specifications, if any, and the Technical Specifications furnished on the CD.

  • Vehicle Base Specifications Note: The actual vehicle awarded may exceed the minimum specifications stated below. The Authorized User may elect to add additional Options, delete Options, or substitute a vehicle feature that is an Option with another Option. See Contract Section III.6

  • Technical Specification As enumerated in Special Conditions of Contract/Scope of Work/attached Drawing/ Details/Schedule of Rates.

  • General specifications 6.1.1. A vehicle and its electrical/electronic system(s) or ESA(s) shall be so designed, constructed and fitted as to enable the vehicle, in normal conditions of use, to comply with the requirements of this Regulation.

  • Service Specification The Parties have agreed upon the scope and specification of the Services provided under this Service Agreement in the Service Specification.

  • Billing Specifications 55.6.1 The Parties agree that billing requirements and outputs will be consistent with the Ordering & Billing Form (OBF) and also with Telcordia Technologies Billing Output Specifications (BOS).

  • Equipment Specifications All equipment must meet the contract specifications and all federal and State safety codes and regulations in effect at the date of manufacture. All equipment must be Original Equipment Manufacturer (OEM) equipment unless otherwise stated in the contract. Items Offered as New. All products, materials, supplies, replacement parts, and equipment offered and furnished must be new, of current manufacturer production, and must have been formally announced by the manufacturer as being commercially available, unless otherwise stated in this Contract.

  • Packing Specifications 7.3.1 A pack will contain a minimum of one message record or a maximum of 99,999 message records plus a pack header record and a pack trailer record. One transmission can contain a maximum of 99 packs and a minimum of one pack.

Time is Money Join Law Insider Premium to draft better contracts faster.