These are some of the technology specifications that I've been publicly associated with over the last few years. Most of these are independent efforts that resulted from discovering problems while studying a particular technology.
- SMTP Extension for Per-Recipient Response Codes: This I-D describes an extension mechanism for the SMTP protocol that allows a server to indicate whether or not a message has been accepted for processing for each of the individual recipients, as opposed to simply indicating whether or not the messages has been accepted for processing by the server itself.
- The application/mbox Media Type: This proposal defines a MIME type for traditional *NIX mbox files as email attachments. This proposal was subsequently republished as RFC4155.
- DNS SRV Definitions for Email Clients: This I-D specified resource records and processing rules that could be used by IMAP/POP/SMTP email clients to automatically configure themselves.
- Considerations for DNS Resource Records: This informational I-D was written to provide a common starting point for people who want to put a new something in the global Domain Name System database, and describes some of the issues that can arise whenever that happens.
- DNS Definitions for "All Addresses": This I-D proposed a mechanism which allows clients to request all of the known IPv4 and IPv6 addresses associated with a domain name simultaneously, without having to issue discrete requests for the IPv6 and IPv4 addresses separately.
- Multicast DNS Resolver Configuration: This I-D explored the use of multicasting to initially configure a DNS resolver.
- LDAP Definitions for UTF-8 Internationalized Domain Names: This I-D defined LDAP attributes and processing rules for storing internationalized domain names in their UTF-8 form, instead of requiring them to be converted into an ASCII encoded form first.
- LDAP Definitions for Access Auditing: This I-D defined an attribute and object class pair that would allow administrators to track the accesses and modifications to a specific entry.
- Domain Name Data-Types: The more time that I spent working on DNS issues (especially in regards to internationalized names), the more obvious it became that the lack of official domain name data-types and syntax rules was a source of many problems. This I-D suggested definitions and data-type rules that would provide some necessary structure to the DNS data.
- The Internationalized Domain Name System: When the internationalized domain name working group was going through its process, I submitted this proposal for a way to process domain names as either UTF8 or in the 7-bit ASCII form, according to the preference of the application protocol.
- The DNS "Status" OPCODE: This I-D proposed a mechanism that would allow DNS operators to query a server for the operational status of a particular zone.
- Multicast BOOTP/DHCP Relays: In the default form, BOOTP/DHCP relay agents must be explicitly defined in order for client devices to function properly. This I-D describes a mechanism that allows clients to use well-known multicast addresses instead.
Apart from the individual submissions above, I also specified a distributed Internet registry query service called FIRS as a secure, distributed, and well-defined replacement to the aging WHOIS service for the CRISP working group. Although an alternative proposal was selected for the specific focus of the working group, I still belive that this is a necessary infrastructure project, especially as a precursor to services such as authenticated email transfers.
- Federated Internet Registry Architecture: This I-D describes the FIRS architecture and some of the implementation considerations.
- Federated Internet Registry Core Components: This I-D describes the core LDAP schema and processing rules used with FIRS.
- Federated Internet Registry Contact Definitions: This I-D describes the LDAP schema and processing rules for administrative contact objects in FIRS.
- Federated Internet Registry IPv4 Definitions: This I-D describes the LDAP schema and processing rules for IPv4 objects in FIRS.
- Federated Internet Registry IPv6 Definitions: This I-D describes the LDAP schema and processing rules for IPv6 objects in FIRS.
- Federated Internet Registry ASN Definitions: This I-D describes the LDAP schema and processing rules for Autonomous System objects in FIRS.
- Federated Internet Registry Domain Definitions: This I-D describes the LDAP schema and processing rules for domain name objects in FIRS.
- Federated Internet Registry DNS Record Definitions: This I-D describes the LDAP schema and processing rules for DNS resource records in FIRS.
Another document of some interest here is the Internationalization Considerations for CRISP report (PDF), which was written as a private analysis on behalf of Network Solutions (the other major contributor to the CRISP working group) and was not published through the IETF process.
Separately, I have also done some preliminary work on a Mail Transfer v2 protocol that attempts to address some of the design flaws and security issues with SMTP, although I have not yet had the opportunity to convert this into a form that is suitable for submission to the IETF.