| gTLD | Full Legal Name | E-mail suffix | Detail | | .LINCOLN | Ford Motor Company | hoganlovells.com | View |
Ford Motor Company (ʺApplicantʺ) can confirm that to the best of their knowledge there are no rendering problems with regard to .LINCOLN based on the fact that this is a US-ASCII based string and does not contain any non-US-ASCII characters.
In addition the string .LINCOLN is compliant with the following technical standards:
• DOD Internet Host Table Specification (RFC 952)
• Domain Names: Implementation and Specification (RFC 1035)
• Requirements for Internet Hosts — Application and Support (RFC 1123)
• Clarifications to the DNS Specification (RFC 2181)
• Application Techniques for Checking and Transformation of Names (RFC 3696)
With regard to potential operational issues, as outlined in RFC 3696, there are potential issues with regard to software not recognising new TLD names as valid or in some cases attempting to ʺguessʺ what the user may be looking for when the software judges the TLD to be invalid.
However, Applicant recognises that ICANN has taken steps to mitigate this by promoting the Universal Acceptance of all Top-Level Domains and providing TLD verification code for use by software developers and application providers.
| gTLD | Full Legal Name | E-mail suffix | Detail | | .FORD | Ford Motor Company | hoganlovells.com | View |
Ford Motor Company (ʺApplicantʺ) can confirm that to the best of their knowledge there are no rendering problems with regard to .FORD based on the fact that this is a US-ASCII based string and does not contain any non-US-ASCII characters.
In addition the string .FORD is compliant with the following technical standards:
• DOD Internet Host Table Specification (RFC 952)
• Domain Names: Implementation and Specification (RFC 1035)
• Requirements for Internet Hosts — Application and Support (RFC 1123)
• Clarifications to the DNS Specification (RFC 2181)
• Application Techniques for Checking and Transformation of Names (RFC 3696)
With regard to potential operational issues, as outlined in RFC 3696, there are potential issues with regard to software not recognising new TLD names as valid or in some cases attempting to ʺguessʺ what the user may be looking for when the software judges the TLD to be invalid.
However, Applicant recognises that ICANN has taken steps to mitigate this by promoting the Universal Acceptance of all Top-Level Domains and providing TLD verification code for use by software developers and application providers.