default search action
Nathaniel S. Borenstein
Person information
Refine list
refinements active!
zoomed in on ?? of ?? records
view refined list in
export refined list as
2010 – 2019
- 2017
- [i16]Nik Tomkinson, Nathaniel S. Borenstein:
Multiple Language Content Type. RFC 8255: 1-19 (2017) - 2013
- [i15]Nathaniel S. Borenstein, Murray S. Kucherawy:
An Architecture for Reputation Reporting. RFC 7070: 1-14 (2013) - [i14]Nathaniel S. Borenstein, Murray S. Kucherawy:
A Media Type for Reputation Interchange. RFC 7071: 1-17 (2013) - [i13]Nathaniel S. Borenstein, Murray S. Kucherawy:
A Reputation Query Protocol. RFC 7072: 1-9 (2013) - [i12]Nathaniel S. Borenstein, Murray S. Kucherawy:
A Reputation Response Set for Email Identifiers. RFC 7073: 1-8 (2013) - 2011
- [j8]Nathaniel S. Borenstein, James Blake:
Cloud Computing Standards: Where's the Beef? IEEE Internet Comput. 15(3): 74-78 (2011)
2000 – 2009
- 2006
- [c14]Morton Swimmer, Ian Whalley, Barry Leiba, Nathaniel S. Borenstein:
Breaking Anti-Spam Systems with Parasitic Spam. CEAS 2006 - 2004
- [c13]Barry Leiba, Nathaniel S. Borenstein:
A Multifaceted Approach to Spam Reduction. CEAS 2004
1990 – 1999
- 1999
- [c12]Nathaniel S. Borenstein:
Utopia, Oblivion, or Muddled Compromise ? Fantasies and Realities about the Coming Global Society. WebNet 1999: 2-6 - 1998
- [j7]Nathaniel S. Borenstein:
Whose Net Is It Anyway? Commun. ACM 41(4): 19-21 (1998) - [c11]Netiva Caftori, Nathaniel S. Borenstein, Harry Hochheiser, Andy Oram:
One Planet, One Net: Principles for the Internet Era. WebNet 1998 - 1996
- [j6]Nathaniel S. Borenstein:
Perils and Pitfalls of Practical Cybercommerce. Commun. ACM 39(6): 36-44 (1996) - [j5]Nathaniel S. Borenstein:
CMU's Andrew Project: A Retrospective. Commun. ACM 39(12es): 298-311 (1996) - [i11]Ned Freed, Nathaniel S. Borenstein:
Multipurpose Internet Mail Extensions (MIME) Part One: Format of Internet Message Bodies. RFC 2045: 1-31 (1996) - [i10]Ned Freed, Nathaniel S. Borenstein:
Multipurpose Internet Mail Extensions (MIME) Part Two: Media Types. RFC 2046: 1-44 (1996) - [i9]Ned Freed, Nathaniel S. Borenstein:
Multipurpose Internet Mail Extensions (MIME) Part Five: Conformance Criteria and Examples. RFC 2049: 1-24 (1996) - 1994
- [c10]Nathaniel S. Borenstein:
EMail With A Mind of Its Own: The Safe-Tcl Language for Enabled Mail. ULPAA 1994: 389-402 - [c9]Nathaniel S. Borenstein:
Enabled Mail. ULPAA 1994: 411-412 - [e1]Manuel Medina, Nathaniel S. Borenstein:
Upper Layer Protocols, Architectures and Applications, Proceedings of the IFIP TC6/WG6.5 International Conference on Upper Layer Protocols, Architectures and Applications, Barcelona, Spain, 1-3 June, 1994. IFIP Transactions C-25, Elsevier 1994, ISBN 0-444-82047-7 [contents] - [i8]Nathaniel S. Borenstein:
The text/enriched MIME Content-type. RFC 1563: 1-16 (1994) - 1993
- [j4]Nathaniel S. Borenstein:
MIME: A Portable and Robust Multimedia Format for Internet Mail. Multim. Syst. 1(1): 29-36 (1993) - [i7]Nathaniel S. Borenstein, Mark Linimon:
The Extension of MIME Content-Types to a New Medium. RFC 1437: 1-6 (1993) - [i6]Nathaniel S. Borenstein, Ned Freed:
MIME (Multipurpose Internet Mail Extensions) Part One: Mechanisms for Specifying and Describing the Format of Internet Message Bodies. RFC 1521: 1-81 (1993) - [i5]Nathaniel S. Borenstein:
The text/enriched MIME Content-type. RFC 1523: 1-15 (1993) - [i4]Nathaniel S. Borenstein:
A User Agent Configuration Mechanism For Multimedia Mail Format Information. RFC 1524: 1-12 (1993) - 1992
- [c8]Nathaniel S. Borenstein:
Computational Mail as Network Infrastructure for Computer-Supported Cooperative Work. CSCW 1992: 67-74 - [c7]Nathaniel S. Borenstein:
Internet Multimedia Mail with MIME: Emerging Standards for Interoperability. ULPAA 1992: 183-192 - [c6]Nathaniel S. Borenstein:
Multimedia Mail. ULPAA 1992: 461-462 - [i3]Nathaniel S. Borenstein, Ned Freed:
MIME (Multipurpose Internet Mail Extensions): Mechanisms for Specifying and Describing the Format of Internet Message Bodies. RFC 1341: 1-80 (1992) - [i2]Nathaniel S. Borenstein:
A User Agent Configuration Mechanism for Multimedia Mail Format Information. RFC 1343: 1-10 (1992) - [i1]Nathaniel S. Borenstein:
Implications of MIME for Internet Mail Gateways. RFC 1344: 1-9 (1992) - 1991
- [j3]Nathaniel S. Borenstein:
Multimedia Electronic Mail: Will the Dream Become a Reality? Commun. ACM 34(4): 117-119 (1991) - [j2]Nathaniel S. Borenstein, Chris A. Thyberg:
Power, Ease of Use and Cooperative Work in a Practical Multimedia Message System. Int. J. Man Mach. Stud. 34(2): 229-259 (1991)
1980 – 1989
- 1988
- [c5]Nathaniel S. Borenstein, Chris A. Thyberg:
Cooperative Work in the Andrew Message System. CSCW 1988: 306-323 - [c4]Nathaniel S. Borenstein, James Gosling:
UNIX Emacs: A Retrospective (lessons for flexible system design). ACM Symposium on User Interface Software and Technology 1988: 95-101 - [c3]Nathaniel S. Borenstein, Craig Everhart, Jonathan Rosenberg, Adam Stoller:
A Multi-media Message System for Andrew. USENIX Winter 1988: 37-42 - 1987
- [j1]Jonathan Rosenberg, Craig Everhart, Nathaniel S. Borenstein:
An overview of the Andrew message system. Comput. Commun. Rev. 17(5): 99-108 (1987) - 1985
- [c2]Nathaniel S. Borenstein:
The evaluation of text editors: a critical review of the Roberts and Morgan methodology based on new experiments. CHI 1985: 99-105 - [c1]Nathaniel S. Borenstein:
Help Texts vs. Help Mechanisms: A New Mandate for Documentation Writers. SIGDOC 1985: 78-83
Coauthor Index
manage site settings
To protect your privacy, all features that rely on external API calls from your browser are turned off by default. You need to opt-in for them to become active. All settings here will be stored as cookies with your web browser. For more information see our F.A.Q.
Unpaywalled article links
Add open access links from to the list of external document links (if available).
Privacy notice: By enabling the option above, your browser will contact the API of unpaywall.org to load hyperlinks to open access articles. Although we do not have any reason to believe that your call will be tracked, we do not have any control over how the remote server uses your data. So please proceed with care and consider checking the Unpaywall privacy policy.
Archived links via Wayback Machine
For web page which are no longer available, try to retrieve content from the of the Internet Archive (if available).
Privacy notice: By enabling the option above, your browser will contact the API of archive.org to check for archived content of web pages that are no longer available. Although we do not have any reason to believe that your call will be tracked, we do not have any control over how the remote server uses your data. So please proceed with care and consider checking the Internet Archive privacy policy.
Reference lists
Add a list of references from , , and to record detail pages.
load references from crossref.org and opencitations.net
Privacy notice: By enabling the option above, your browser will contact the APIs of crossref.org, opencitations.net, and semanticscholar.org to load article reference information. Although we do not have any reason to believe that your call will be tracked, we do not have any control over how the remote server uses your data. So please proceed with care and consider checking the Crossref privacy policy and the OpenCitations privacy policy, as well as the AI2 Privacy Policy covering Semantic Scholar.
Citation data
Add a list of citing articles from and to record detail pages.
load citations from opencitations.net
Privacy notice: By enabling the option above, your browser will contact the API of opencitations.net and semanticscholar.org to load citation information. Although we do not have any reason to believe that your call will be tracked, we do not have any control over how the remote server uses your data. So please proceed with care and consider checking the OpenCitations privacy policy as well as the AI2 Privacy Policy covering Semantic Scholar.
OpenAlex data
Load additional information about publications from .
Privacy notice: By enabling the option above, your browser will contact the API of openalex.org to load additional information. Although we do not have any reason to believe that your call will be tracked, we do not have any control over how the remote server uses your data. So please proceed with care and consider checking the information given by OpenAlex.
last updated on 2024-04-24 22:48 CEST by the dblp team
all metadata released as open data under CC0 1.0 license
see also: Terms of Use | Privacy Policy | Imprint