82
edits
Thunderbird:Autoconfiguration: Difference between revisions
→DNS based discovery
| Line 195: | Line 195: | ||
== DNS based discovery == | == DNS based discovery == | ||
Configuration files for all mail servers would be fetched according to the following standard, providing a unified approach and UI, based on existing discovery channels and transport layers | === Requirements Notation === | ||
The key words "MUST", "MUST NOT", "REQUIRED", "SHALL", "SHALL NOT", "SHOULD", "SHOULD NOT", "RECOMMENDED", "MAY", and "OPTIONAL" in this document are to be interpreted as described in [RFC2119] (Bradner, B., “Key words for use in RFCs to Indicate Requirement Levels,” 1997.). | |||
=== Overview === | |||
Configuration files for all mail servers would be fetched according to the following standard, providing a unified approach and UI, based on existing discovery channels and transport layers. | |||
=== Definitions === | |||
The location of the configuration file would be discovered by the following method: | The location of the configuration file would be discovered by the following method: | ||
| Line 220: | Line 228: | ||
Advantages | === Advantages === | ||
1.) Unified standard for all ISPs. | 1.) Unified standard for all ISPs. | ||
| Line 233: | Line 241: | ||
6.) Decentralized and autonomous. | 6.) Decentralized and autonomous. | ||
=== Examples === | |||
None yet. | |||
=== Disclaimer === | |||
This standard shall be licensed according to a Mozilla compatible licenses and is copyright (c) 2008 of Eddy Nigg. Not sure if this is needed, but prefer to be on the save side for now, just in case other vendors want to adopt it. Please advice on this. | |||
= Related Information = | = Related Information = | ||