Response Format. Please provide the following information on the cover page of Vendor’s Proposal and ensure that Vendor’s name appears on each subsequent page of the document:
A. Vendor’s Name;
B. Vendor’s Address;
C. Contact Name;
D. Contact Job Title;
E. E-mail Address; and
Response Format. These terms of reference (TOR) summarize UNDP’s requirements to the products, services and service levels under the future LTAs. Bidders are expected to respond to each section of the TOR, confirming that requirements can be met and explaining how the desired outcome can be achieved. E.
Response Format. Offeror shall adhere to the format prescribed and content required for proposal responses. Offeror’s proposal response shall:
1. Provide Offeror’s full and complete response to the Google Response Form or, if technical difficulties arise, Appendix E, Sample Response Form.
2. Be succinct, self-explanatory and well organized so that the Evaluation Committee can understand how Offeror will fulfill the requirements of this solicitation. There is no page limit for proposal responses as a whole; however, the Google Response Form or Appendix E, Sample Response Form have a two-hundred (200) word limit for each Health Care Consulting Service Category. In the Google Response Form or Appendix E, the Offeror may list up to four (4) specific experiences/projects for each Health Care Consulting Service of up to fifty (50) words each. The Offeror may list fewer than four (4) examples as long as the mandatory experience requirement is met. The Department does not encourage excessive responses and does not desire unnecessary tables, graphs, photographs or attachments.
3. Include additional information, if requested, as attachments to the proposal.
Response Format. All information for the Technical Proposal must be combined into a single file/document for uploading. EXCEPTION: Single electronic files that exceed 50mb may be submitted as multiple uploads, which must be the least number of uploads necessary to fall under the 50mb limit. The Technical Proposals SHALL NOT contain any cost information.
Response Format. Responses to DNS queries can take many forms. The response can be an IP address, a name server address, or it can contain a Uniform Resource Locator (URL). The most efficient response for the purposes of CSC addressing would be a URL. Most people are familiar with URLs for their web applications; for example xxxx://xxx.xxxxxxx.xxx. This says that the HTTP protocol should be used to contact the file at xxx.xxxxxxx.xxx—a website. Using a URL will allow the Addressing Database to provide specific protocol addresses such as SMPP, SMTP, etc. In fact there are response formats that will provide multiple URLs allowing the Application Providers to provide CSC applications in multiple protocols. Carriers would provision their gateways to read the response and select the protocol they utilize.
Response Format. Offeror’s “Master” response shall consist of the following:
Response Format. 1.7.1 Each data object shall be represented as a set of key/value pairs, where each key runs from the start of the line, until the first colon (":"), and where any white space found immediately preceding the first colon shall not be counted as part of the key. All data excluding the first continuous sequence of white space following the first colon, up to but excluding the line feed should count as part of the value.
1.7.2 All WHOIS data will be in the ASCII character set, which has encoding compatible with UTF-8 for easy transition to including internationalized data, and as per the IETF's recommendations on i18n in Internet protocols. For fields where more than one value exists, multiple key/value pairs with the same key shall be allowed (for example to list multiple nameservers). The first key/value pair after a blank line should be considered the start of a new record, and should be considered as identifying that record, and is used to group data, such as hostnames and IP addresses, or a domain name and registrant information, together.
1.7.3 The following table specifies the data elements reported in response to various query types and levels:
(a) Flags and Public/Extensive WHOIS fields: • X - Field will always be output if data is available • O - Field is optional, and may not be displayed • M - Field may be represented as multiple key/value pairs
(b) Sections: • M - Multiple subrecords may be displayed If the data is not available, the key will not be displayed. The "flags" column applies to all output formats. Section Field name Flags Summary Standard Detailed Extensive Registry Domain ID X X X X Domain Name X X X X Registrar X X X X Registrar IANA ID X X X X Registrar Abuse Contact Email X X X Registrar Abuse Contact Phone X X X Domain Status M X X X X Registry Registrant ID X X X Registrant Name X X Registrant Organization O X X Registrant Street X X Registrant City X X Registrant State/Province O X X Registrant Postal Code O X X Registrant Country X X Registrant Phone Number X Registrant Fax Number X Registrant Email X Other names registered byregistrant OM X Registry Admin ID X X X Admin Name X X Admin Organization O X X Admin Street X X Admin City X X Section Field name Flags Summary Standard Detailed Extensive Admin State/Province O X X Admin Postal Code O X X Admin Country X X Admin Phone Number X X Admin Fax Number O X X Admin Email X X Registry Tech ID X X X Tech Name X X Tech Organization O X X Tech Street X X Tech City X X Tech State/Pro...
Response Format. Additional data elements can be added at the end of the text format outlined below. The data element may, at the option of Registrar, be followed by a blank line and a legal disclaimer specifying the rights of Registrar, and of the user querying the database (provided that any such legal disclaimer must be preceded by such blank line). Domain Name: EXAMPLE.TLD Registry Domain ID: D1234567-TLD Registrar WHOIS Server: whois.example-registrar.tld Registrar URL: xxxx://xxx.xxxxxxx-xxxxxxxxx.xxx Updated Date: 2009-05-29T20:13:00Z Creation Date: 2000-10-08T00:45:00Z Registrar Registration Expiration Date: 2010-10-08T00:44:59Z Registrar: EXAMPLE REGISTRAR LLC Registrar IANA ID: 5555555 Registrar Abuse Contact Email: email@registrar.tld Registrar Abuse Contact Phone: +1.1235551234 Reseller: EXAMPLE RESELLER1 Domain Status: clientDeleteProhibited2xxxxx://xxxxx.xxx/epp#clientDeleteProhibited Domain Status: clientRenewProhibited xxxxx://xxxxx.xxx/epp#clientRenewProhibited Domain Status: clientTransferProhibitedhttps://xxxxx.xxx/xxx#xxxxxxXxxxxxxxXxxxxxxxxx Registry Registrant ID: 5372808-ERL3 Registrant Name: EXAMPLE REGISTRANT4 Registrant Organization: EXAMPLE ORGANIZATION Registrant Street: 000 XXXXXXX XXXXXX Xxxxxxxxxx Xxxx: ANYTOWN Registrant State/Province: AP5 Registrant Postal Code: A1A1A16 Registrant Country: AA
Response Format. All responses must be on eight and one-half by eleven (8 1/2 x 11) inch recycled paper, typed, and placed in binders with tabs separating major sections. Responses are limited to forty (40) pages in length (twenty if printed on both sides) not including resumes and other appendices. The major sections shall include the technical (work plan), management, and cost specifications.
Response Format. Responses must address all aspects of the Invitation For Bid and should follow proper chronological order as presented in the Invitation For Bid. All submittals should note Invitation For Bid Section numbers. One (1) original and three (3) copies of your response to the Invitation For Bid are required. The original bid must be clearly labeled “ORIGINAL.” Should a discrepancy arise between various copies of the Invitation For Bid, information contained in the “ORIGINAL” shall prevail over conflicting information. All information requested in this Invitation For Bid must be submitted in a manner consistent with Section VI: Schedule of Required Submittals and Signature Sheet. Bids may be submitted in an organized fashion on 8-1/2” x 11”, letter sized paper. Submittals must be in chronological order as in this Invitation For Bid. Each bid should be prepared simply and economically, providing a straightforward concise description of the approach and ability to meet the LCSD requirements. This Invitation For Bid states the instructions for submitting bids, the procedures and criteria by which LCSD proposes to govern the relationship between it and the selected Vendor. Only information contained in this Invitation For Bid, or supplemental written information supplied by LCSD, will be considered in preparing bids. No verbal interpretations, changes or modifications will be considered. All assumptions made by the respondent must be clearly stated in the bid and qualifiers must be placed in context. The Vendor understands and agrees that it has the duty to explain and clarify any and all conditions imposed on, or included in, its response to this Invitation For Bid. Vendor further understands and agrees that it has an affirmative duty to inquire about, and clarify, any Invitation For Bid statement that the respondent does not fully understand or that respondent reasonably believes may be susceptible to more than one interpretation. Any respondent who does not follow the above prescribed methods of contact through the appropriate contact person, may be disqualified and its bid rejected, regardless of its value to LCSD.
