Steve Crocker American Internet pioneer
Crocker, Stephen David, 1944-
VIAF ID: 48830236 (Personal)
Permalink: http://viaf.org/viaf/48830236
Preferred Forms
4xx's: Alternate Name Forms (16)
Works
| Title | Sources |
|---|---|
| The ARPA network, 1972: |
|
| RFC 1: Host Software |
|
| RFC 1640: The Process for Organization of Internet Standards Working Group (POISED) |
|
| RFC 169: COMPUTER NETWORKS |
|
| RFC 1692: Transport Multiplexing Protocol (TMux) |
|
| RFC 1741: MIME Content Type for BinHex Encoded Files |
|
| RFC 1750: Randomness Recommendations for Security |
|
| RFC 1767: MIME Encapsulation of EDI Objects |
|
| RFC 1775: To Be "On" the Internet |
|
| RFC 1776: The Address is the Message |
|
| RFC 1796: Not All RFCs are Standards |
|
| RFC 1847: Security Multiparts for MIME: Multipart/Signed and Multipart/Encrypted |
|
| RFC 1848: MIME Object Security Services |
|
| RFC 1898: CyberCash Credit Card Protocol Version 0.8 |
|
| RFC 2142: Mailbox Names for Common Services, Roles and Functions |
|
| RFC 25: No High Link Numbers |
|
| RFC 3: Documentation conventions |
|
| RFC 3297: Content Negotiation for Messaging Services based on Email |
|
| RFC 3343: The Application Exchange (APEX) Presence Service |
|
| RFC 352: TIP Site Information Form |
|
| RFC 36: Protocol Notes |
|
| RFC 4141: SMTP and MIME Extensions for Content Conversion |
|
| RFC 4142: Full-mode Fax Profile for Internet Mail (FFPIM) |
|
| RFC 4143: Facsimile Using Internet Mail (IFAX) Service of ENUM |
|
| RFC 45: New Protocol is Coming |
|
| RFC 462: Responding to user needs |
|
| RFC 47: BBN's Comments on NWG/RFC #33 |
|
| RFC 48: Possible protocol plateau |
|
| RFC 4986: Requirements Related to DNS Security (DNSSEC) Trust Anchor Rollover |
|
| RFC 5068: Email Submission Operations: Access and Accountability Requirements |
|
| RFC 52: Updated distribution list |
|
| RFC 5234: Augmented BNF for Syntax Specifications: ABNF |
|
| RFC 539: Thoughts on the mail protocol proposed in RFC 524 |
|
| RFC 54: Official Protocol Proffering |
|
| RFC 55: Prototypical implementation of the NCP |
|
| RFC 5598: Internet Mail Architecture |
|
| RFC 577: Mail priority |
|
| RFC 584: Charter for ARPANET Users Interest Working Group |
|
| RFC 6: Conversation with Bob Kahn |
|
| RFC 615: Proposed Network Standard Data Pathname syntax |
|
| RFC 6152: SMTP Service Extension for 8-bit MIME Transport |
|
| RFC 6376: DomainKeys Identified Mail (DKIM) Signatures |
|
| RFC 6410: Reducing the Standards Track to Two Maturity Levels |
|
| RFC 656: Telnet output vertical tabstops option |
|
| RFC 658: Telnet output linefeed disposition |
|
| RFC 66: NIC - third level ideas and other noise |
|
| RFC 6647: Email Greylisting: An Applicability Statement for SMTP |
|
| RFC 6648: Deprecating the "X-" Prefix and Similar Constructs in Application Protocols |
|
| RFC 6729: Indicating Email Handling States in Trace Fields |
|
| RFC 6975: Signaling Cryptographic Algorithm Understanding in DNS Security Extensions (DNSSEC) |
|
| RFC 70: Note on Padding |
|
| RFC 720: Address Specification Syntax for Network Mail |
|
| RFC 7221: Handling of Internet-Drafts by IETF Working Groups |
|
| RFC 726: Remote Controlled Transmission and Echoing Telnet option |
|
| RFC 73: Response to NWG/RFC 67 |
|
| RFC 735: Revised Telnet byte macro option |
|
| RFC 7704: An IETF with Much Diversity and Professional Conduct |
|
| RFC 822: Standard for the Format of ARPA Internet Text Messages |
|
| RFC 85: Network Working Group meeting |
|
| RFC 8552: Scoped Interpretation of DNS Resource Records through "Underscored" Naming of Attribute Leaves |
|
| RFC 8553: DNS Attrleaf Changes: Fixing Specifications That Use Underscored Node Names |
|
| RFC 86: Proposal for a Network Standard Format for a Data Stream to Control Graphics Display |
|
| RFC 95: Distribution of NWG/RFC's through the NIC |
|
