default search action
Stephen T. Kent
Person information
Refine list
refinements active!
zoomed in on ?? of ?? records
view refined list in
export refined list as
2020 – today
- 2024
- [i32]Job Snijders, Ben Maddison, Matthew Baker Lepinski, Derrick Kong, Stephen T. Kent:
A Profile for Route Origin Authorizations (ROAs). RFC 9582: 1-15 (2024) - 2022
- [i31]Rob Austein, Geoff Huston, Stephen T. Kent, Matt Lepinski:
Manifests for the Resource Public Key Infrastructure (RPKI). RFC 9286: 1-16 (2022) - 2020
- [i30]Di Ma, Stephen T. Kent:
Requirements for Resource Public Key Infrastructure (RPKI) Relying Parties. RFC 8897: 1-11 (2020)
2010 – 2019
- 2019
- [i29]Geoff Huston, Samuel Weiler, George Michaelson, Stephen T. Kent, Tim Bruijnzeels:
Resource Public Key Infrastructure (RPKI) Trust Anchor Locator. RFC 8630: 1-11 (2019) - 2017
- [i28]Mark C. Reynolds, Sean Turner, Stephen T. Kent:
A Profile for BGPsec Router Certificates, Certificate Revocation Lists, and Certification Requests. RFC 8209: 1-15 (2017) - [i27]Stephen T. Kent, Di Ma:
Adverse Actions by a Certification Authority (CA) or Repository Manager in the Resource Public Key Infrastructure (RPKI). RFC 8211: 1-26 (2017) - 2016
- [i26]Geoff Huston, Samuel Weiler, George Michaelson, Stephen T. Kent:
Resource Public Key Infrastructure (RPKI) Trust Anchor Locator. RFC 7730: 1-8 (2016) - 2015
- [i25]Stephen T. Kent, Derrick Kong, Karen Seo:
Template for a Certification Practice Statement (CPS) for the Resource PKI (RPKI). RFC 7382: 1-38 (2015) - 2014
- [i24]Stephen T. Kent, Andrew Chi:
Threat Model for BGP Path Security. RFC 7132: 1-20 (2014) - 2013
- [i23]Roque Gagliano, Stephen T. Kent, Sean Turner:
Algorithm Agility Procedure for the Resource Public Key Infrastructure (RPKI). RFC 6916: 1-20 (2013) - [i22]Richard L. Barnes, Stephen T. Kent, Eric Rescorla:
Further Key Words for Use in RFCs to Indicate Requirement Levels. RFC 6919: 1-6 (2013) - [i21]Sean Turner, Stephen T. Kent, James Manger:
Additional Methods for Generating Key Identifiers Values. RFC 7093: 1-5 (2013) - 2012
- [i20]Matt Lepinski, Stephen T. Kent:
An Infrastructure to Support Secure Internet Routing. RFC 6480: 1-24 (2012) - [i19]Matt Lepinski, Stephen T. Kent, Derrick Kong:
A Profile for Route Origin Authorizations (ROAs). RFC 6482: 1-9 (2012) - [i18]Stephen T. Kent, Derrick Kong, Karen Seo, Ronald J. Watro:
Certificate Policy (CP) for the Resource Public Key Infrastructure (RPKI). RFC 6484: 1-35 (2012) - [i17]Rob Austein, Geoff Huston, Stephen T. Kent, Matt Lepinski:
Manifests for the Resource Public Key Infrastructure (RPKI). RFC 6486: 1-19 (2012) - [i16]Matt Lepinski, Andrew Chi, Stephen T. Kent:
Signed Object Template for the Resource Public Key Infrastructure (RPKI). RFC 6488: 1-13 (2012) - [i15]Geoff Huston, George Michaelson, Stephen T. Kent:
Certification Authority (CA) Key Rollover in the Resource Public Key Infrastructure (RPKI). RFC 6489: 1-10 (2012) - [i14]Geoff Huston, Samuel Weiler, George Michaelson, Stephen T. Kent:
Resource Public Key Infrastructure (RPKI) Trust Anchor Locator. RFC 6490: 1-7 (2012)
2000 – 2009
- 2009
- [i13]Sang Hwan Park, Haeryong Park, Yoojae Won, Jaeil Lee, Stephen T. Kent:
Traceable Anonymous Certificate. RFC 5636: 1-31 (2009) - 2008
- [i12]Matt Lepinski, Stephen T. Kent:
Additional Diffie-Hellman Groups for Use with IETF Standards. RFC 5114: 1-23 (2008) - 2006
- [c10]Stephen T. Kent:
An Infrastructure Supporting Secure Internet Routing. EuroPKI 2006: 116-129 - 2005
- [i11]Stephen T. Kent, Karen Seo:
Security Architecture for the Internet Protocol. RFC 4301: 1-101 (2005) - [i10]Stephen T. Kent:
IP Authentication Header. RFC 4302: 1-34 (2005) - [i9]Stephen T. Kent:
IP Encapsulating Security Payload (ESP). RFC 4303: 1-44 (2005) - [i8]Stephen T. Kent:
Extended Sequence Number (ESN) Addendum to IPsec Domain of Interpretation (DOI) for Internet Security Association and Key Management Protocol (ISAKMP). RFC 4304: 1-5 (2005) - 2004
- [i7]Charles Lynn, Stephen T. Kent, Karen Seo:
X.509 Extensions for IP Addresses and AS Identifiers. RFC 3779: 1-27 (2004) - 2003
- [c9]Stephen T. Kent:
Securing the Border Gateway Protocol: A Status Update. Communications and Multimedia Security 2003: 40-53 - 2002
- [j14]Alex C. Snoeren, Craig Partridge, Luis A. Sanchez, Christine E. Jones, Fabrice Tchakountio, Beverly Schwartz, Stephen T. Kent, W. Timothy Strayer:
Single-packet IP traceback. IEEE/ACM Trans. Netw. 10(6): 721-734 (2002) - [c8]Stephen T. Kent:
Rethinking PKI: What's Trust Got to Do with It? EUROCRYPT 2002: 398-399 - 2000
- [j13]Stephen T. Kent, Charles Lynn, Karen Seo:
Secure Border Gateway Protocol (S-BGP). IEEE J. Sel. Areas Commun. 18(4): 582-592 (2000) - [c7]Stephen T. Kent, Charles Lynn, Joanne Mikkelson, Karen Seo:
Secure Border Gateway Protocol (S-BGP) - Real World Performance and Deployment Issues. NDSS 2000
1990 – 1999
- 1999
- [j12]John Zao, Stephen T. Kent, Joshua Gahm, Gregory D. Troxel, Matthew Condell, Pam Helinek, Nina Yuan, Isidro Castiñeyra:
A public-key based secure Mobile IP. Wirel. Networks 5(5): 373-390 (1999) - [c6]Stephen T. Kent:
R&D Challenges: Notes from the "Trust in Cyberspace" Report. NDSS 1999 - [c5]Stephen T. Kent:
Network Security: Then and Now, or, 20 Years in 10 Minutes. S&P 1999: 117 - 1998
- [i6]Stephen T. Kent, Randall J. Atkinson:
Security Architecture for the Internet Protocol. RFC 2401: 1-66 (1998) - [i5]Stephen T. Kent, Randall J. Atkinson:
IP Authentication Header. RFC 2402: 1-22 (1998) - [i4]Stephen T. Kent, Randall J. Atkinson:
IP Encapsulating Security Payload (ESP). RFC 2406: 1-22 (1998) - [i3]Rob Glenn, Stephen T. Kent:
The NULL Encryption Algorithm and Its Use With IPsec. RFC 2410: 1-6 (1998) - 1997
- [c4]John Zao, Stephen T. Kent, Joshua Gahm, Gregory D. Troxel, Matthew Condell, Pam Helinek, Nina Yuan, Isidro Castiñeyra:
A Public-Key Based Secure Mobile IP. MobiCom 1997: 173-184 - [c3]Karen E. Sirois, Stephen T. Kent:
Securing the Nimrod Routing Architecture. NDSS 1997: 74-84 - 1994
- [j11]Susan Landau, Stephen T. Kent, Clinton Brooks, Scott Charney, Dorothy E. Denning, Whitfield Diffie, Anthony Lauck, Douglas Miller, Peter G. Neumann, David Sobel:
Crypto Policy Perspectives. Commun. ACM 37(8): 115-121 (1994) - [j10]Stephen T. Kent:
Internet security standards: past, present, and future. ACM Stand. 2(2): 78-85 (1994) - 1993
- [j9]Stephen T. Kent:
Internet Privacy Enhanced Mail. Commun. ACM 36(8): 48-60 (1993) - 1991
- [i2]Stephen T. Kent:
U.S. Department of Defense Security Options for the Internet Protocol. RFC 1108: 1-17 (1991)
1980 – 1989
- 1989
- [j8]Stephen T. Kent:
Comments on "security problems in the TCP/IP protocol suite". Comput. Commun. Rev. 19(3): 10-19 (1989) - [i1]Stephen T. Kent, John Linn:
Privacy enhancement for Internet electronic mail: Part II - certificate-based key management. RFC 1114: 1-25 (1989) - 1985
- [j7]Victor L. Voydock, Stephen T. Kent:
Security in high-level network protocols. IEEE Commun. Mag. 23(7): 12-24 (1985) - [j6]Victor L. Voydock, Stephen T. Kent:
Security mechanisms in a transport layer protocol. Comput. Secur. 4(4): 325-341 (1985) - 1984
- [j5]Victor L. Voydock, Stephen T. Kent:
Security Mechanisms in a Transport Layer Protocol. Comput. Networks 8: 433-449 (1984) - 1983
- [j4]Victor L. Voydock, Stephen T. Kent:
Security Mechanisms in High-Level Network Protocols. ACM Comput. Surv. 15(2): 135-171 (1983) - 1981
- [j3]Stephen T. Kent:
Security Requirements and Protocols for a Broadcast Scenario. IEEE Trans. Commun. 29(6): 778-786 (1981) - [j2]Stephen T. Kent:
Correction to "Security Requirements and Protocols for a Broadcast Scenario". IEEE Trans. Commun. 29(9): 1409 (1981) - [j1]Miles E. Smid, Richard E. Lennon, Stephen M. Matyas, Carl H. Meyer, Stephen T. Kent:
Correction to the Special Section on Computer Network Security of the June 1981 Issue. IEEE Trans. Commun. 29(9): 1409 (1981) - [c2]Stephen T. Kent:
Some Cryptographic Techniques for File Protection. CRYPTO 1981: 80 - 1980
- [b1]Stephen T. Kent:
Protecting externally supplied software in small computers. Massachusetts Institute of Technology, Cambridge, MA, USA, 1980
1970 – 1979
- 1977
- [c1]Stephen T. Kent:
Encryption-based protection for interactive user/computer communication. SIGCOMM 1977: 5
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-09-29 00:25 CEST by the dblp team
all metadata released as open data under CC0 1.0 license
see also: Terms of Use | Privacy Policy | Imprint