default search action
Bob Braden
Person information
Refine list
refinements active!
zoomed in on ?? of ?? records
view refined list in
export refined list as
Journal Articles
- 2013
- [j8]Robert Braden:
Burroughs Algol at Stanford University, 1960-1963. IEEE Ann. Hist. Comput. 35(4): 69-73 (2013) - 2006
- [j7]Yu He, Cauligi S. Raghavendra, Steven Berson, Robert Braden:
An autonomic routing framework for sensor networks. Clust. Comput. 9(2): 191-200 (2006) - 2005
- [j6]David D. Clark, Craig Partridge, Robert Braden, Bruce S. Davie, Sally Floyd, Van Jacobson, Dina Katabi, Greg Minshall, K. K. Ramakrishnan, Timothy Roscoe, Ion Stoica, John Wroclawski, Lixia Zhang:
Making the world (of communications) a different place. Comput. Commun. Rev. 35(3): 91-96 (2005) - [j5]David D. Clark, John Wroclawski, Karen R. Sollins, Robert Braden:
Tussle in cyberspace: defining tomorrow's internet. IEEE/ACM Trans. Netw. 13(3): 462-475 (2005) - 2004
- [j4]Ruzena Bajcsy, Terry Benzel, Matt Bishop, Robert Braden, Carla E. Brodley, Sonia Fahmy, Sally Floyd, Wes Hardaker, Anthony D. Joseph, George Kesidis, Karl N. Levitt, Robert Lindell, Peng Liu, David J. Miller, Russ Mundy, Clifford Neuman, Ron Ostrenga, Vern Paxson, Phillip A. Porras, Catherine Rosenberg, J. Doug Tygar, Shankar Sastry, Daniel F. Sterne, Shyhtsun Felix Wu:
Cyber defense technology networking and evaluation. Commun. ACM 47(3): 58-61 (2004) - 2003
- [j3]Robert Braden, Theodore Faber, Mark Handley:
From protocol stack to protocol heap: role-based architecture. Comput. Commun. Rev. 33(1): 17-22 (2003) - [j2]David D. Clark, Robert Braden, Aaron Falk, Venkata K. Pingali:
FARA: reorganizing the addressing architecture. Comput. Commun. Rev. 33(4): 313-321 (2003) - 1989
- [j1]Robert Braden, David A. Borman, Craig Partridge:
Computing the internet checksum. Comput. Commun. Rev. 19(2): 86-94 (1989)
Conference and Workshop Papers
- 2014
- [c12]Alefiya Hussain, Ted Faber, Robert Braden, Terry V. Benzel, Tim Yardley, Jeremy Jones, David M. Nicol, William H. Sanders, Thomas W. Edgar, Thomas E. Carroll, David O. Manz, Laura Tinnel:
Enabling Collaborative Research for Security and Resiliency of Energy Cyber Physical Systems. DCOSS 2014: 358-360 - 2013
- [c11]Ryan Goodfellow, Robert Braden, Terry Benzel, David E. Bakken:
First steps toward scientific cyber-security experimentation in wide-area cyber-physical systems. CSIIRW 2013: 39 - 2008
- [c10]Kevin Lahey, Robert Braden, Keith Sklower:
Experiment Isolation in a Secure Cluster Testbed. CSET 2008 - 2007
- [c9]Terry Benzel, Robert Braden, Dongho Kim, Anthony D. Joseph, B. Clifford Neuman, Ron Ostrenga, Stephen Schwab, Keith Sklower:
Design, Deployment, and Use of the DETER Testbed. DETER 2007 - 2006
- [c8]Terry Benzel, Robert Braden, Dongho Kim, Clifford Neuman, Anthony D. Joseph, Keith Sklower:
Experience with deter: A testbed for security research. TRIDENTCOM 2006 - 2002
- [c7]Robert Braden, Robert Lindell, Steven Berson, Theodore Faber:
The ASP EE: An Active Network Execution Environment. DANCE 2002: 238-254 - [c6]Steven Berson, Steven Dawson, Robert Braden:
Evolution of an Active Networks Testbed. DANCE 2002: 446-465 - [c5]David D. Clark, John Wroclawski, Karen R. Sollins, Robert Braden:
Tussle in cyberspace: defining tomorrow's internet. SIGCOMM 2002: 347-356 - 1999
- [c4]Bob Braden:
Arguments Against IPSEC. NDSS 1999 - 1995
- [c3]Teunis J. Ott, Robert Braden, T. V. Lakshman, Upamanyu Madhow, Christina Brazdziunas, A. Broscius, Arnold L. Neidhardt:
The Internet in Evolution, and TCP Over ATM (Panel). SIGMETRICS 1995: 261-262 - 1988
- [c2]Robert Braden:
A pseudo-machine for packet monitoring and statistics. SIGCOMM 1988: 200-209 - 1977
- [c1]Robert T. Braden:
A server host system on the ARPANET. SIGCOMM 1977: 4
Informal and Other Publications
- 2015
- [i63]Martin H. Duke, Robert Braden, Wesley M. Eddy, Ethan Blanton, Alexander Zimmermann:
A Roadmap for Transmission Control Protocol (TCP) Specification Documents. RFC 7414: 1-57 (2015) - 2014
- [i62]David A. Borman, Bob Braden, Van Jacobson, Richard Scheffenegger:
TCP Extensions for High Performance. RFC 7323: 1-49 (2014) - 2009
- [i61]Robert Braden, Joel M. Halpern:
Procedures for Rights Handling in the RFC Independent Submission Stream. RFC 5744: 1-6 (2009) - 2006
- [i60]Martin H. Duke, Robert Braden, Wesley M. Eddy, Ethan Blanton:
A Roadmap for Transmission Control Protocol (TCP) Specification Documents. RFC 4614: 1-33 (2006) - 2002
- [i59]Joyce K. Reynolds, Robert Braden, Sandy Ginoza, Alison De La Cruz:
Internet Official Protocol Standards. RFC 3300: 1-49 (2002) - 2001
- [i58]Joyce K. Reynolds, Robert Braden, Sandy Ginoza:
Internet Official Protocol Standards. RFC 2800: 1-38 (2001) - [i57]Joyce K. Reynolds, Robert Braden, Sandy Ginoza:
Internet Official Protocol Standards. RFC 2900: 1-42 (2001) - [i56]Joyce K. Reynolds, Robert Braden, Sandy Ginoza, Lorrie Shiota:
Internet Official Protocol Standards. RFC 3000: 1-43 (2001) - [i55]Robert Braden, Lixia Zhang:
RSVP Cryptographic Authentication - Updated Message Type Value. RFC 3097: 1-4 (2001) - [i54]Robert Braden, Randy Bush, John C. Klensin:
Request to Move STD 39 to Historic Status. RFC 3109: 1-4 (2001) - 2000
- [i53]Joyce K. Reynolds, Robert Braden:
Internet Official Protocol Standards. RFC 2600: 1-31 (2000) - [i52]Joyce K. Reynolds, Robert Braden:
Internet Official Protocol Standards. RFC 2700: 1-32 (2000) - [i51]Andreas Terzis, Bob Braden, Subramaniam Vincent, Lixia Zhang:
RSVP Diagnostic Messages. RFC 2745: 1-23 (2000) - [i50]Yoram Bernet, Peter Ford, Raj Yavatkar, Fred Baker, Lixia Zhang, Michael Speer, Robert Braden, Bruce S. Davie, John Wroclawski, Eyal Felstaine:
A Framework for Integrated Services Operation over Diffserv Networks. RFC 2998: 1-31 (2000) - 1999
- [i49]Joyce K. Reynolds, Robert Braden:
Internet Official Protocol Standards. RFC 2500: 1-28 (1999) - [i48]Robert Braden, Joyce K. Reynolds, Steve Crocker, Vint Cerf, Jake Feinler, Celeste Anderson:
30 Years of RFCs. RFC 2555: 1-18 (1999) - 1998
- [i47]Bob Braden, David D. Clark, Jon Crowcroft, Bruce S. Davie, Steve Deering, Deborah Estrin, Sally Floyd, Van Jacobson, Greg Minshall, Craig Partridge, Larry L. Peterson, K. K. Ramakrishnan, Scott Shenker, John Wroclawski, Lixia Zhang:
Recommendations on Queue Management and Congestion Avoidance in the Internet. RFC 2309: 1-17 (1998) - 1997
- [i46]Robert Braden, Lixia Zhang, Steven Berson, Shai Herzog, Sugih Jamin:
Resource ReSerVation Protocol (RSVP) - Version 1 Functional Specification. RFC 2205: 1-112 (1997) - [i45]Allison Mankin, Fred Baker, Bob Braden, Scott O. Bradner, Michael D. O'Dell, Allyn Romanow, Abel Weinrib, Lixia Zhang:
Resource ReSerVation Protocol (RSVP) - Version 1 Applicability Statement Some Guidelines on Deployment. RFC 2208: 1-6 (1997) - [i44]Robert Braden, Lixia Zhang:
Resource ReSerVation Protocol (RSVP) - Version 1 Message Processing Rules. RFC 2209: 1-25 (1997) - 1994
- [i43]Bob Braden, Jon Postel, Yakov Rekhter:
Internet Architecture Extensions for Shared Media. RFC 1620: 1-19 (1994) - [i42]Robert Braden, David D. Clark, Scott Shenker:
Integrated Services in the Internet Architecture: an Overview. RFC 1633: 1-33 (1994) - [i41]Robert Braden, David D. Clark, Steve Crocker, Christian Huitema:
Report of IAB Workshop on Security in the Internet Architecture - February 8-10, 1994. RFC 1636: 1-52 (1994) - [i40]Robert Braden:
T/TCP - TCP Extensions for Transactions Functional Specification. RFC 1644: 1-38 (1994) - 1992
- [i39]Van Jacobson, Robert T. Braden, David A. Borman:
TCP Extensions for High Performance. RFC 1323: 1-37 (1992) - [i38]Robert T. Braden:
TIME-WAIT Assassination Hazards in TCP. RFC 1337: 1-11 (1992) - [i37]Robert T. Braden:
Extending TCP for Transactions - Concepts. RFC 1379: 1-38 (1992) - 1991
- [i36]David D. Clark, Lyman Chapin, Vint Cerf, Robert T. Braden, Russ Hobby:
Towards the Future Internet Architecture. RFC 1287: 1-29 (1991) - 1990
- [i35]Van Jacobson, Robert Braden, Lixia Zhang:
TCP Extension for High-Speed Paths. RFC 1185: 1-21 (1990) - 1989
- [i34]Robert T. Braden:
Requirements for Internet Hosts - Communication Layers. RFC 1122: 1-116 (1989) - [i33]Robert T. Braden:
Requirements for Internet Hosts - Application and Support. RFC 1123: 1-98 (1989) - [i32]Robert T. Braden:
Perspective on the Host Requirements RFCs. RFC 1127: 1-20 (1989) - 1988
- [i31]Annette L. DeSchon, Robert T. Braden:
Background File Transfer Program (BFTP). RFC 1068: 1-27 (1988) - [i30]Robert Braden, David A. Borman, Craig Partridge:
Computing the Internet checksum. RFC 1071: 1-24 (1988) - [i29]Van Jacobson, Robert Braden:
TCP extensions for long-delay paths. RFC 1072: 1-16 (1988) - 1987
- [i28]Robert T. Braden, Jon Postel:
Requirements for Internet gateways. RFC 1009: 1-54 (1987) - 1985
- [i27]Robert T. Braden:
Towards a transport service for transaction processing applications. RFC 955: 1-10 (1985) - 1982
- [i26]Robert T. Braden:
Backup access to the European side of SATNET. RFC 831: 1-6 (1982) - 1977
- [i25]Robert T. Braden:
NETRJS Protocol. RFC 740: 1-19 (1977) - 1973
- [i24]Robert T. Braden:
Comments on File Transfer Protocol. RFC 430: 1-8 (1973) - [i23]Robert T. Braden:
Print files in FTP. RFC 448: 1-3 (1973) - [i22]Robert T. Braden:
FTP data compression. RFC 468: 1-7 (1973) - [i21]Robert T. Braden:
On mail service to CCN. RFC 498: 1-3 (1973) - [i20]Robert T. Braden:
TENEX FTP Problem. RFC 571: 1 (1973) - [i19]Robert T. Braden:
CCN NETRJS server messages to remote user. RFC 589: 1-5 (1973) - [i18]Robert T. Braden:
Update on NETRJS. RFC 599: 1-9 (1973) - 1972
- [i17]Abhay K. Bhushan, Bob Braden, William R. Crowther, Eric Harslem, John F. Heafner, Alex M. McKenzie, Bob Sundberg, Dick Watson, James E. White:
The Data Transfer Protocol. RFC 264: 1-9 (1972) - [i16]Robert T. Braden:
EBCDIC/ASCII Mapping for Network RJE. RFC 338: 1-6 (1972) - [i15]Robert T. Braden:
Comments on "Proposed Remote Job Entry Protocol". RFC 368: 1-2 (1972) - [i14]Robert T. Braden:
Using TSO via ARPA Network Virtual Terminal. RFC 377: 1-4 (1972) - [i13]Robert T. Braden:
Using TSO at CCN. RFC 379: 1-5 (1972) - [i12]Robert T. Braden:
TSO Scenario. RFC 390: 1-4 (1972) - 1971
- [i11]Robert T. Braden, Stephen M. Wolfe:
NETRJS: A third level protocol for Remote Job Entry. RFC 88: 1-9 (1971) - [i10]Robert T. Braden:
CCN as a Network Service Center. RFC 90: 1-6 (1971) - [i9]Abhay K. Bhushan, Bob Braden, William R. Crowther, Eric Harslem, John F. Heafner, Alex M. McKenzie, John T. Melvin, Bob Sundberg, Dick Watson, James E. White:
The Data Transfer Protocol. RFC 171: 1-9 (1971) - [i8]Abhay K. Bhushan, Bob Braden, William R. Crowther, Eric Harslem, John F. Heafner, Alex M. McKenzie, John T. Melvin, Bob Sundberg, Dick Watson, James E. White:
The File Transfer Protocol. RFC 172: 1-12 (1971) - [i7]Robert T. Braden:
Interim NETRJS specifications. RFC 189: 1-19 (1971) - [i6]Robert T. Braden:
NETCRT - a character display protocol. RFC 205: 1-13 (1971) - [i5]Robert T. Braden:
Comments on DTP and FTP proposals. RFC 238: 1-2 (1971) - [i4]Robert T. Braden:
Host mnemonics proposed in RFC 226 (NIC 7625). RFC 239: 1 (1971) - [i3]Abhay K. Bhushan, Bob Braden, William R. Crowther, Eric Harslem, John F. Heafner, Alex M. McKenzie, John T. Melvin, Bob Sundberg, Dick Watson, James E. White:
The File Transfer Protocol. RFC 265: 1-12 (1971) - [i2]Abhay K. Bhushan, Robert T. Braden, Eric Harslem, John F. Heafner, Alex M. McKenzie, John T. Melvin, Robert L. Sundberg, Richard W. Watson, James E. White:
Revision of the Mail Box Protocol. RFC 278: 1-4 (1971) - [i1]Robert T. Braden:
NETRJT: Remote Job Service Protocol for TIPS. RFC 283: 1-9 (1971)
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-25 05:46 CEST by the dblp team
all metadata released as open data under CC0 1.0 license
see also: Terms of Use | Privacy Policy | Imprint