├── Makefile ├── README.md ├── data-management.tex ├── facilities.tex ├── introduction.tex ├── management.tex ├── mentoring.tex ├── outreach.tex ├── prior.tex ├── proposal.tex ├── ref.bib ├── rfc.bib ├── summary.tex └── synergistic.tex /Makefile: -------------------------------------------------------------------------------- 1 | REPORT=proposal 2 | LATEX=pdflatex 3 | BIBTEX=bibtex --min-crossrefs=1000 4 | REF1=ref 5 | REF2=rfc 6 | 7 | TEX = $(wildcard *.tex) 8 | CLS = $(wildcard *.cls) 9 | SRCS = $(TEX) 10 | REFS=$(REF1).bib $(REF2).bib 11 | 12 | all: pdf 13 | 14 | pdf: figures $(SRCS) $(CLS) 15 | $(LATEX) $(REPORT) 16 | $(BIBTEX) $(REPORT) 17 | perl -pi -e "s/%\s+//" $(REPORT).bbl 18 | $(LATEX) $(REPORT) 19 | $(LATEX) $(REPORT) 20 | 21 | $(REPORT).ps: $(REPORT).dvi figures 22 | # dvips -Pcmz -t letter $(REPORT).dvi -o $(REPORT).ps 23 | dvips -Ppdf -G0 -t letter $(REPORT).dvi -o $(REPORT).ps 24 | 25 | web: pdf 26 | scp -C $(REPORT).pdf feamster@central.gtnoise.net:/var/www/tmp/ 27 | 28 | spell: 29 | for i in *.tex; do ispell $$i; done 30 | 31 | double: 32 | for i in *.tex; do double.pl $$i; done 33 | 34 | split: pdf 35 | pdftk $(REPORT).pdf cat 1 output $(REPORT)-0.pdf 36 | pdftk $(REPORT).pdf cat 2-16 output $(REPORT)-1.pdf 37 | pdftk $(REPORT).pdf cat 17-21 output $(REPORT)-2.pdf 38 | 39 | #not relevant here 40 | figures: 41 | cd figures; make 42 | 43 | view: $(REPORT).dvi 44 | xdvi $(REPORT).dvi 45 | 46 | print: $(REPORT).dvi 47 | dvips $(REPORT).dvi 48 | 49 | printer: $(REPORT).ps 50 | lpr $(REPORT).ps 51 | 52 | tidy: 53 | rm -f *.dvi *.aux *.log *.blg *.bbl 54 | 55 | clean: 56 | rm -f *~ *.dvi *.aux *.log *.blg *.bbl *.brf *.out $(REPORT).ps $(REPORT).pdf 57 | 58 | -------------------------------------------------------------------------------- /README.md: -------------------------------------------------------------------------------- 1 | # nsf-template 2 | Template for NSF Proposals 3 | -------------------------------------------------------------------------------- /data-management.tex: -------------------------------------------------------------------------------- 1 | \begin{center} 2 | {\large \bf \TITLE} 3 | \end{center} 4 | 5 | \begin{center} 6 | {\bf Data Management Plan} 7 | \end{center} 8 | 9 | Our proposed research, outreach, and educational activities may handle a 10 | variety of datasets and data models. The data used in the project will be 11 | delineated between \emph{private data} that is unsuitable for any release and 12 | must be access-controlled (e.g.,personally-identifying information, as 13 | specified by an IRB, or private company data that is protected by NDA); and 14 | \emph{public data} that is already broadly available. 15 | 16 | \paragraph{Data Storage and Retention.} We will use the University of 17 | Chicago secure data enclave (\url{https://securedata.uchicago.edu}), which 18 | allows researchers to securely store and analyze sensitive research data 19 | according to various restrictions, including local, state, federal, and 20 | international laws. The facility provides best-in-class data security 21 | standards for the storage of sensitive data, as well as the ability to 22 | analyze sensitive data directly within the enclave, using software 23 | researchers install and co-located compute facilities, including the 24 | Research Computing Center's MidwayR computing cluster that is equipped 25 | with tools and software that provide compliance with state-of-the-art 26 | data protection. 27 | 28 | Data will be guaranteed to be stored for the lifetime of the proposed 29 | project, but in general we expect to store most data longer. Storage 30 | beyond the end of the project period will be at the data owner's (see 31 | below for definition) and data generator's discretion. 32 | 33 | We will use any standard collaboration/communication tools to transmit 34 | any data that can be released to those who request it. In general, 35 | private data will not be transferable from one site to another; if the 36 | need arises to transfer data between institutions, we will consult with 37 | our corresponding university IRBs and use suitable data protection 38 | mechanisms to transfer that data. 39 | 40 | \paragraph{Data Ownership}. We find it helpful to ensure that datasets 41 | always have a designated ``owner''. Although this person may or may 42 | not have been the generator of the data, they will be responsible for 43 | ensuring proper access control in the case of private data, facilitating 44 | timely responses to requests for releasable data, and for ensuring 45 | continued access for public 46 | data. The owner will be the co-PI or senior researcher most closely 47 | affiliated with the activity from which the data resulted. Should that 48 | co-PI leave their institution or be, for some other reason, unable to 49 | continue being owner of the data, they will either pass ownership to 50 | another co-PI for the project or to another senior researcher at their 51 | university. 52 | 53 | In cases of handling sensitive data from one of our partners, decisions 54 | regarding data management will be governed by corresponding negotiation 55 | of data use agreements with our corresponding universities. For example, 56 | the University of Chicago has a standard Data Use Agreement (DUA) 57 | template that is used for incoming and outgoing data and managed by the 58 | university research administration 59 | (\url{https://ura.uchicago.edu/page/data-sharing-agreements}) 60 | to ensure that proper procedures and protocols are implemented for 61 | transferring and protecting sensitive data. A critical first step will 62 | be careful consultation with partners and other university officials 63 | (e.g., university IRBs, university research administration and contracts 64 | offices) regarding the data that will be shared, to inform policy about 65 | the status of the data. 66 | 67 | \paragraph{Primary Data.} This project will involve the collection and sharing 68 | of various data concerning Internet connectivity, uptake, and student 69 | engagement and achievement. When appropriate, and as described below, we aim 70 | to make these datasets available through the Chicago Data 71 | Portal~\cite{www-chicago-data}, in cooperation with our partners. The 72 | datasets we plan to collect and/or analyze include the 73 | following: 74 | \begin{itemize} 75 | \itemsep=-1pt 76 | \item {\em Network performance data.} We will use existing tools and 77 | software, including the BISmark network measurement suite to gather 78 | continuous data about network performance, including throughput, 79 | latency, packet loss, and home wireless network performance. All 80 | performance data will be made publicly available, except for any data 81 | pertaining to specific devices in a house that could be linked to an 82 | individual (e.g., IP addresses and hardware addresses will be 83 | appropriately anonymized). 84 | \item {\em Application quality data.} We will use the existing 85 | NetMicroscope toolkit that we have developed to measure and infer 86 | application quality and user experience for a broad array of 87 | applications that Chicago Public School students depend on for online 88 | learning. As with network performance data, and identifying 89 | information, such as IP addresses and hardware addresses, will be 90 | appropriately anonymized before public release. 91 | \item {\em Application and Internet usage data.} Our ability to observe 92 | traffic inside of the home makes it possible to gain insight into 93 | Internet usage in the home, including what applications and services 94 | were being used at what times. This data is of a more sensitive nature 95 | and we do not plan to publicly release it in raw form. Rather, we will 96 | release data including aggregate statistics that are derived from the 97 | raw data, such as the breakdown of application and device usage across 98 | all homes, the typical numbers of simultaneous Internet users in a 99 | household, and so forth. 100 | \end{itemize} 101 | 102 | \paragraph{Other Data.} Several other kinds of data will be generated in the 103 | course of this project: 104 | 105 | \begin{itemize} 106 | \item 107 | \emph{Source code}: We will make all source code open 108 | source under a suitable nonrestrictive license. 109 | \item 110 | \emph{Educational materials}: As discussed in the proposal, we plan to 111 | create course modules and integrate these materials into both new an 112 | existing courses. Whenever possible, we will release course 113 | materials---lecture and assignment materials, videos, etc.---for other 114 | educators to integrate into their own courses. 115 | \end{itemize} 116 | -------------------------------------------------------------------------------- /facilities.tex: -------------------------------------------------------------------------------- 1 | \begin{center} 2 | {\large \bf \TITLE} 3 | \end{center} 4 | 5 | \begin{center} 6 | {\bf Facilities, Equipment, and Other Resources} 7 | \end{center} 8 | 9 | The Department of Computer Science is the hub of a large, diverse computing 10 | community of two hundred researchers focused on advancing foundations of 11 | computing and driving its most advanced applications. Long distinguished in 12 | theoretical computer science and artificial intelligence, the Department is 13 | building a strong Systems research group. This closely knit community includes 14 | the Data Science Institute (DSI), the Toyota Technological Institute, and 15 | Argonne’s Mathematics and Computer Science Division. 16 | 17 | In addition, as of August 2018, the Department of Computer Science moved into 18 | its new home on the second and third floors of the renovated John Crerar 19 | Library. This state-of-the-art academic space includes closed and open 20 | offices, conference rooms, spaces for experimental research, graduate student 21 | offices and a large gathering area for departmental seminars, workshops and 22 | distinguished speaker lectures. The PI has access to a substantial collection 23 | of computing resources at the University of Chicago including a large 24 | visualization display and GVU clusters. The PIs receive administrative support 25 | from the University of Chicago Physical Sciences Division, including contract 26 | and grant accounting, meeting organization, and other administrative tasks. 27 | The PIs also have access to a dedicated user studies laboratory at the 28 | department for any in-laboratory, user studies, or design activities held at 29 | the university as well as a graphic design studio, PSD Graphic Arts, housed in 30 | the basement of the John Crerar Library for creating example content for user 31 | studies and audit studies. All personnel involved in this project will be 32 | given office and desk spaces on the campus of the University of Chicago. 33 | 34 | Basic daily computing needs will be supplied partially by the Department of 35 | Computer Science where the PIs are faculty members. Faculty members also have 36 | access to the Research Computing Cluster (RCC) should the project team require 37 | more computer power for any activities designed as part of the project. RCC 38 | provides high-end research computing resources and support to researchers, 39 | enabling the advancement of critical inquiry across a diverse set of 40 | disciplines—the physical sciences, social sciences and humanities, medicine, 41 | and economics. University researchers and their collaborators are provided 42 | access to managed high-performance computing (HPC), storage, and visualization 43 | resources. In addition to the cutting-edge hardware and the advanced software 44 | that RCC maintains, its expert staff of computational scientists, research 45 | programmers, application developers, and HPC systems administrators assist 46 | researchers via consultation and training to help them fully leverage modern 47 | HPC technology within their projects. The RCC’s HPC resources include the 48 | Midway Compute Cluster housed in the 6045 Data Center. The Midway Cluster 49 | forms the core of RCC’s advanced computational infrastructure. 50 | -------------------------------------------------------------------------------- /introduction.tex: -------------------------------------------------------------------------------- 1 | \begin{center} 2 | {\large \bf \TITLE} 3 | \end{center} 4 | 5 | \section{Introduction} 6 | 7 | Broadband access networks are proliferating: Over 90\% of US households 8 | now have Internet access, and networks have become an essential part of 9 | every home. Video streaming already accounts for over 60\% of the peak 10 | download bandwidth for the Internet~\cite{www-bismark}; 11 | -------------------------------------------------------------------------------- /management.tex: -------------------------------------------------------------------------------- 1 | \section{Management Plan and Timeline}\label{sec:management} 2 | 3 | PI Feamster will manage all aspects of this project. The project will involve 4 | graduate students and research staff who will help with the implementation of 5 | the project, as well as sustaining the software over time and transferring the 6 | data and systems to other organizations, as described in 7 | Section~\ref{sec:impacts}. We envision that the themes of this project will 8 | proceed roughly in phases, in order, with some overlap as appropriate. For 9 | example, much of the research involving systems integration requires the work 10 | from the first two themes to be completed, but many other parts are 11 | independent and complementary. 12 | 13 | -------------------------------------------------------------------------------- /mentoring.tex: -------------------------------------------------------------------------------- 1 | \begin{center} 2 | {\large \bf \TITLE } \\ 3 | {\bf Mentoring Plan} 4 | \end{center} 5 | 6 | \noindent 7 | Postdoc and graduate student mentoring will include the 8 | following activities: 9 | 10 | \begin{enumerate} 11 | \itemsep=-1pt 12 | \item {\bf Orientation.} PIs will offer each researcher 13 | an 14 | initial orientation discussing mutual expectations including: the 15 | amount of independence the postdoctoral researcher requires, 16 | interaction with coworkers, productivity including the importance of 17 | scientific publications, work habits, and documentation of research 18 | methodologies and experimental details. 19 | 20 | \item {\bf Career counseling.} PIs will offer the researchers 21 | career counseling providing the researchers with the 22 | skills, knowledge, and experience needed to excel in his/her chosen 23 | career path. We will also encourage the researchers to 24 | discuss career options with other faculty at our respective 25 | institutions. 26 | 27 | \item {\bf Experience with funding applications.} When possible and 28 | appropriate, the PIs will involve researchers in the 29 | preparation of grant proposals, providing the opportunity to learn 30 | best practices in proposal preparation including: identification of 31 | key research questions, definition of objectives, description of 32 | approach and rationale, and construction of a work plan, timeline, and 33 | budget. 34 | 35 | \item {\bf Writing and presentation skills. } 36 | We will encourage researchers to 37 | write and publish scientific articles, 38 | as well as other reports and publications. We will ask the 39 | researchers to present and lead discussions on scientific 40 | research at project meetings and present the results of their research 41 | to related research groups on campus. The PIs will also coach the 42 | researchers for external presentations at conferences, to 43 | program managers, and for other face-to-face meetings. 44 | 45 | \item {\bf Mentoring experience.} 46 | Joint mentoring of graduate student interns work on the proposed project 47 | to expose the postdoctoral researcher to effective techniques in working 48 | with and managing students. Graduate students will be given 49 | opportunities to mentor undergraduates involved in the proposed 50 | research. 51 | 52 | \item {\bf Scientific guidance.} The fast pace of the proposed scientific 53 | program requires effective communication and a tight coordination of 54 | the effort. The progress of the postdoctoral researchers and graduate 55 | students will be carefully followed by 56 | the PI, usually on a daily basis. Group meetings take place at least 57 | weekly to discuss progress and plans. Additionally, the PIs will offer 58 | the researchers regular instruction in professional 59 | practices. 60 | 61 | \item {\bf Job search assistance.} The PIs will provide postdoctoral 62 | researchers and senior graduate students with assistance with career 63 | application materials, including (as 64 | applicable) preparation of academic curriculum vitae, faculty 65 | application materials, and related support required to enable a 66 | successful academic job search. 67 | 68 | \item {\bf Technology transfer and industry connections.} Technology 69 | transfer activities will include regular contact with partner 70 | companies involved in the project. 71 | 72 | \item {\bf Biannual assessment.} To assess the success of the above plan, 73 | the PI will meet with each graduate student and postdoctoral 74 | researcher twice a year for an additional, 75 | formal mentoring session. Weaknesses and strengths, career goals, research 76 | progress, work/life balance, interaction with students and collaborators, as 77 | well as other issues that may arise will be discussed, and help will be 78 | offered. 79 | 80 | \item {\bf Networking and career development.} The postdoctoral 81 | researchers and graduate students will be given 82 | opportunities to network with other scholars at the PIs' respective 83 | institutions. Many of the PIs on this project are located in the Chicago area, 84 | giving postdoctoral researchers a unique opportunity to network with each 85 | other, across institutions, and with PIs at other institutions (including 86 | through lectures and guest speaker engagements). 87 | from local opportunities. 88 | 89 | \item {\bf Travel.} This proposal includes travel funds 90 | to allow postdoctoral researchers and graduate students to attend collaboration meetings conferences. Active 91 | participation through 92 | presentations will be encouraged. 93 | \end{enumerate} 94 | \noindent 95 | Success of the mentoring plan will be assessed by monitoring the 96 | personal progress of the researchers through a tracking of 97 | progress towards career goals. 98 | PIs on this project have successfully mentored graduate students and postdocs 99 | who now have faculty 100 | positions at computer science departments in the United States and abroad. 101 | -------------------------------------------------------------------------------- /outreach.tex: -------------------------------------------------------------------------------- 1 | \section{Broader Impacts}\label{sec:impacts} 2 | 3 | This project aims to education the next generation of computer scientists on 4 | topics concerning the applications of machine learning to cybersecurity. As 5 | the focus on the project is education, many of the project's outcomes 6 | naturally already touch on broader impacts, through student education. Below, 7 | we expand on various themes and discuss how the research and education efforts 8 | that we described in previous sections can be translated to further broader 9 | impacts. 10 | 11 | 12 | \paragraph{Student and researcher mentorship.} To improve education in ways 13 | that broaden participation in computing, the PIs will create interconnected 14 | programs that merge sustained engagement with diverse students in Chicago 15 | Public Schools, provide summer research experiences, and carefully scaffold 16 | these research experiences with on-ramp immersions that lower barriers to 17 | participation. 18 | 19 | To provide meaningful research experiences to students, the PIs will annually 20 | mentor a diverse group of students, ranging in level from high school to 21 | post-graduate as a way to encourage future participation in computing 22 | programs. These efforts will benefit from engaged partnerships with 23 | organizations to aid in recruitment and tracking student outcomes, including 24 | established relationships between the University of Chicago computer science 25 | department and other organizational units, including: (1)~The UChicago 26 | Collegiate Scholars Program; (2) the Office of Special Programs (OSP) College 27 | Prep; (3)~The Fisk-Vanderbilt Master's-to-PhD Bridge Program for 28 | underrepresented students. 29 | 30 | PIs have a successful track record in mentoring women and underrepresented 31 | minorities. For example, PI Feamster currently advises three female Ph.D. 32 | students, two of whom are underrepresented minorities; PI Schmitt currently 33 | advises two female Masters students, both of whom are underrepresented minorities. In the past, students mentored by 34 | the PIs have won various awards. For example, both PIs mentored Annie 35 | Edmundson a Ph.D. student at Princeton who won the ACM Student Research 36 | Competition at ACM SIGCOMM. The PIs are involved with various efforts around 37 | the department to increase inclusion and diversity. Both PIs regularly 38 | involve undergraduate students in research, both during the academic year and 39 | summers. The research performed by undergraduates has often resulted in 40 | peer-reviewed publications (including as first author on top-tier venues such 41 | as SIGCOMM and IMC). Many of the PIs' undergraduates have continued either to 42 | top graduate programs or highly desirable companies. Another aspect of 43 | education is providing students with internship opportunities. The PI will 44 | seek out real-world opportunities at government offices, companies, and civil 45 | society organizations to train students. When hiring, the PI will follow best 46 | practices for encouraging diversity in hiring, including interviewing a 47 | diverse set of candidates and advertising in forums that serve 48 | under-represented minorities (\eg, Tapia and Grace Hopper). 49 | 50 | \paragraph{Outreach to under-represented high school students.} To further 51 | engage under-represented minorities in the project, the PIs will integrate 52 | results from this project into K-12 education programs, such as the University 53 | of Chicago's Upward Bound program, where PI Feamster currently teaches an 54 | ``Applications of Machine Learning to Networking'' summer course to 55 | under-represented students across the Chicago Public School system. This 56 | program has allowed the PI to directly engage with high school students 57 | enrolled in Chicago Public Schools (77\% economically disadvantaged and 83\% 58 | underrepresented minority) and their parents for an annual series of 10 59 | seminars and 6 weekend workshops hosted at UChicago on our project's key 60 | themes. This on-ramp will introduce core computing skills, build an 61 | understanding of the research process (e.g., how to ask a good research 62 | question), and help the students set productive routines in unstructured 63 | environments. Perhaps more importantly, it will help build a community and 64 | support network among each year's student cohort and the PIs through near-peer 65 | mentoring and informal interactions. Following this immersion, the students 66 | will work for the rest of the summer with their respective co-PIs. 67 | 68 | \paragraph{Course development.} The PI will develop new course materials 69 | pertaining to Internet security, both for courses at the University of Chicago 70 | and in the form of publicly accessible course material, as in Massive Open 71 | Online Courses (MOOCs), which PI Feamster has developed in the past. The PI 72 | already teaches several courses where topics from the research may be 73 | integrated, including undergraduate Information Security, Networking, Many 74 | University of Chicago undergraduate students also perform independent 75 | research. The PI will generate project ideas for independent work projects and 76 | undergraduate theses and will invite students to undertake these projects. A 77 | major expected outcome from this project is to create course and curriculum 78 | materials that can be used by large numbers of students, both at the 79 | University of Chicago and at other institutions. As described in earlier 80 | sections of the proposal, the PIs plan to develop these materials into content 81 | that can be used in textbooks, online courses, professional development 82 | materials, and other outlets. 83 | -------------------------------------------------------------------------------- /prior.tex: -------------------------------------------------------------------------------- 1 | \section{Results from Prior NSF Support} 2 | 3 | \paragraph{Feamster:} 4 | \textbf{CPS: Medium: Detecting and Controlling Unwanted 5 | Data Flows in the Internet of Things} \textit{1739809} (PI: Feamster); 6 | 10/1/18--9/30/22, \$875,000. 7 | This 8 | project develops technologies that ensure that IoT smart devices remain secure 9 | and protect user privacy in the face of the widespread deployment of connected 10 | smart devices. 11 | \textbf{Intellectual Merit:} This project advances the theory and practice of network traffic 12 | analysis and anomaly detection to secure IoT deployments. The project 13 | has resulted in publications at top-tier 14 | conferences~\cite{hooman2019:ccs,chu2018:iot:iotj,zheng2018:iot:cscw,feamster2018:iot:ctlj,doshi2018:iot,apthorpe2018:iot:imwut,datta2018:iot,acar2018:iot,weinberg2019:iot:www}, including studies of how home network traffic can 15 | expose users to new privacy risks, new methods for modeling user attitudes and 16 | norms about 17 | privacy in smart homes, with applications to using contextual integrity, 18 | and a broader understanding of how smart home 19 | devices from appliances to smart 20 | TVs may 21 | collect private user data. They also include broader research on IoT 22 | security and 23 | privacy~\cite{chu2018:iot:iotj,zheng2018:iot:cscw,feamster2018:iot:ctlj,doshi2018:iot,apthorpe2018:iot:imwut,datta2018:iot,acar2018:iot,weinberg2019:iot:www}. 24 | \textbf{Broader Impacts:} The research 25 | has produced open-source software (IoT Inspector) to help smart home users better understand 26 | how devices collect and share private data and the largest 27 | labeled dataset of smart home device traffic with data from about 10,000 28 | homes. 29 | -------------------------------------------------------------------------------- /proposal.tex: -------------------------------------------------------------------------------- 1 | \documentclass[10pt]{article} 2 | \usepackage{subfigure,psfrag,epsfig,graphics,url,amsmath,amssymb,fancyhdr,cite,color} 3 | \usepackage{multirow} 4 | \usepackage{palatino} 5 | \usepackage[font=small,format=plain,labelfont=bf,up,textfont=it,up]{caption} 6 | \usepackage[small,compact]{titlesec} 7 | \usepackage[margin=1in]{geometry} 8 | \usepackage{setspace} 9 | 10 | %\titleformat{\section} 11 | % {\normalfont\fontsize{10}{10}\bfseries}{\thesection}{0.5em}{} 12 | 13 | 14 | %%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%% 15 | % Hyperref stuff 16 | 17 | %\usepackage[filecolor=black,citecolor=black,urlcolor=black,linkcolor=black,colorlinks,pdfpagelabels,pdfpagelayout=SinglePage,dvips]{hyperref} 18 | %\usepackage{backref} 19 | %\usepackage{breakurl} 20 | %\renewcommand{\url}{\burl} 21 | 22 | %% \renewcommand*{\backref}[1]{} 23 | %% \renewcommand*{\backrefalt}[4]{ 24 | %% \ifcase #1 % 25 | %% (Not cited.) % 26 | %% \or 27 | %% {\small\sffamily (Cited on page~#2.)}% 28 | %% \else 29 | %% {\small\sffamily (Cited on pages~#2.)}% 30 | %% \fi 31 | %% } 32 | %% \renewcommand*{\backrefsep}{, } 33 | %% \renewcommand*{\backreftwosep}{ and~} 34 | %% \renewcommand*{\backreflastsep}{ and~} 35 | 36 | \newcommand{\TITLE}{TITLE HERE} 37 | \newcommand{\xxx}[1]{{\color{red} #1}} 38 | 39 | %%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%% 40 | 41 | \newtheorem{definition}{Definition} 42 | \newtheorem{task}{Task}[section] 43 | \newtheorem{problem}{Problem}[section] 44 | 45 | \usepackage[pdftex,hyperref,svgnames]{xcolor} 46 | \colorlet{todo}{FireBrick} % FireBrick prints better than red 47 | \newenvironment{todolist}[1][] 48 | {\color{todo}TODO: \em#1\begin{enumerate}} 49 | {\end{enumerate}} 50 | \newcommand{\todo}[2][TODO]{\textcolor{todo}{[{\em #1: #2}]}} 51 | 52 | \newcommand{\eg}{{\it e.g.}} 53 | \newcommand{\ie}{{\it i.e.}} 54 | \newcommand{\etal}{{\it et al.}} 55 | \newcommand{\comment}[1]{} 56 | 57 | \newcommand{\fp}{\vspace*{0.03in}\noindent} 58 | \renewcommand{\b}{$\bullet$} 59 | \renewcommand{\paragraph}[1]{\fp {\bf #1}} 60 | 61 | \begin{document} 62 | \date{} 63 | 64 | % 6 lines per inch, per research.gov 65 | \setstretch{1.004} 66 | 67 | \begin{sloppypar} 68 | \pagestyle{plain} 69 | \thispagestyle{empty} 70 | \input{summary} 71 | \pagebreak 72 | \setcounter{page}{0} 73 | \input{introduction} 74 | \input{outreach} 75 | \input{management} 76 | \input{prior} 77 | 78 | \pagebreak 79 | \setcounter{page}{1} 80 | \bibliographystyle{abbrv} 81 | \bibliography{ref,rfc} 82 | 83 | \pagebreak 84 | \setcounter{page}{1} 85 | \input{data-management} 86 | 87 | \pagebreak 88 | \setcounter{page}{1} 89 | \input{mentoring} 90 | 91 | \pagebreak 92 | \setcounter{page}{1} 93 | \input{synergistic} 94 | 95 | \pagebreak 96 | \setcounter{page}{1} 97 | \input{facilities} 98 | 99 | 100 | \end{sloppypar} 101 | \end{document} 102 | -------------------------------------------------------------------------------- /rfc.bib: -------------------------------------------------------------------------------- 1 | @string{IETF = "{Internet Engineering Task Force}"} 2 | 3 | % Put actual RFCs at the top, Internet-Drafts at the bottom 4 | 5 | @manual{rfc768, 6 | author = "J. ~B. ~Postel", 7 | title = "{User Datagram Protocol}", 8 | organization = IETF, 9 | note = {RFC 768}, 10 | year = 1980, 11 | month = aug, 12 | } 13 | 14 | @manual{rfc791, 15 | author = {J. ~B. ~Postel}, 16 | title = "{Internet Protocol}", 17 | note = {RFC 791}, 18 | organization = IETF, 19 | year = 1981, 20 | address = {Information Sciences Institute, Marina del Rey, CA}, 21 | month = sep 22 | } 23 | 24 | @manual{rfc792, 25 | author = "Postel, J.", 26 | title = "{Internet Control Message Protocol}", 27 | note = {RFC 792}, 28 | organization = IETF, 29 | year = 1981, 30 | month = sep 31 | } 32 | 33 | @manual{rfc793, 34 | author = {J. ~B. ~Postel}, 35 | title = "{Transmission Control Protocol}", 36 | note = {RFC 793}, 37 | year = 1981, 38 | organization = IETF, 39 | month = sep 40 | } 41 | 42 | @manual{rfc821, 43 | author = {J. ~B. ~Postel}, 44 | title = "{Simple Mail Transfer Protocol}", 45 | note = {RFC 821}, 46 | organization = IETF, 47 | month = aug, 48 | year = 1982, 49 | } 50 | 51 | @manual{rfc822, 52 | author = {D. H. Crocker}, 53 | title = "{Standard for the Format of ARPA Internet Text Messages}", 54 | note = {RFC 822}, 55 | organization = IETF, 56 | month = aug, 57 | year = 1982, 58 | } 59 | 60 | @manual{rfc854, 61 | author = "J. ~B. ~Postel and Reynolds, J.", 62 | title = "{TELNET Protocol Specification}", 63 | organization = IETF, 64 | note = {RFC 854}, 65 | month = may, 66 | year = 1983, 67 | } 68 | 69 | @manual{rfc908, 70 | author = "Velten, D. and Hinden, R. and Sax, J.", 71 | title = "{Reliable Data Protocol}", 72 | note = {RFC 908}, 73 | organization = IETF, 74 | month = jul, 75 | year = 1984, 76 | } 77 | 78 | @manual{rfc959, 79 | author = "J. ~B. ~Postel and Reynolds, J.", 80 | title = "{File Transfer Protocol (FTP)}", 81 | note = {RFC 959}, 82 | organization = IETF, 83 | month = oct, 84 | year = 1985, 85 | } 86 | 87 | @manual{rfc970, 88 | author = "Nagle, J.", 89 | title = "{On Packet Switches with Infinite Storage}", 90 | note = {RFC 970}, 91 | organization = IETF, 92 | year = 1985, 93 | month = dec, 94 | } 95 | 96 | @manual{rfc976, 97 | author="Horton, Mark R.", 98 | title="UUCP Mail Interchange Format Standard", 99 | note={RFC976}, 100 | organization = IETF, 101 | year = 1986, 102 | month = feb 103 | } 104 | 105 | 106 | @manual{rfc977, 107 | author = "Kantor, B. and Lapsley, P.", 108 | title = "{Network News Transfer Protocol (NNTP)}", 109 | note = {RFC-977}, 110 | address = "{UC San Diego}", 111 | month = feb, 112 | year = 1986, 113 | } 114 | 115 | @manual{rfc1016, 116 | author = "W. Prue and J. Postel", 117 | title = "{Something a Host Could Do with Source Quench: The Source Quench Introduced Delay (SQuID)}", 118 | organization = IETF, 119 | note = {RFC 1016}, 120 | month = jul, 121 | year = 1987, 122 | } 123 | 124 | @manual{rfc1034, 125 | author="Mockapetris, P. V.", 126 | title="Domain names - concepts and facilities", 127 | organization = IETF, 128 | note = {RFC 1034}, 129 | month=nov, 130 | year=1987, 131 | abstract="This RFC is the revised basic definition of The Domain 132 | Name System. It obsoletes RFC-882. This memo describes the 133 | domain style names and their used for host address look up 134 | and electronic mail forwarding. It discusses the clients 135 | and servers in the domain name system and the protocol used 136 | between them.", 137 | URL="\url{ftp://ftp.isi.edu/in-notes/rfc1034.txt}", 138 | entryby=Sc 139 | } 140 | 141 | @manual{rfc1035, 142 | author="Mockapetris, P. V.", 143 | title="Domain names - implementation and specification", 144 | organization = IETF, 145 | note = {RFC 1035}, 146 | month=nov, 147 | year=1987, 148 | abstract="This RFC is the revised specification of the protocol and 149 | format used in the implementation of the Domain Name 150 | System. It obsoletes RFC-883. This memo documents the 151 | details of the domain name client - server communication.", 152 | URL="\url{ftp://ftp.isi.edu/in-notes/rfc1035.txt}", 153 | entryby=Sc 154 | } 155 | 156 | @manual{rfc1058, 157 | author = "Hedrick, C.", 158 | title = "{Routing Information Protocol}", 159 | organization = IETF, 160 | note = {RFC 1058}, 161 | year = 1988, 162 | month = jun 163 | } 164 | 165 | @manual{rfc1070, 166 | author = {R. Hagens and N. Hall and M. Rose}, 167 | title = {Use of the Internet as a Subnetwork for Experimentation with the OSI Network Layer}, 168 | note = {RFC 1070}, 169 | organization = IETF, 170 | year = 1989, 171 | month = feb, 172 | } 173 | 174 | @manual{rfc1072, 175 | author = {Jacobson, V. and Braden, R. T.}, 176 | title = {TCP Extensions for Long Delay Paths}, 177 | note = {RFC 1072}, 178 | organization = IETF, 179 | year = 1988, 180 | month = oct, 181 | } 182 | 183 | @manual{rfc1094, 184 | author = {Sun Microsystems, Inc.}, 185 | title = {NFS: Network File System Protocol Specification}, 186 | note = {RFC 1094} , 187 | month = mar, 188 | year = 1989 189 | } 190 | 191 | @manual{rfc1102, 192 | author = {David Clark}, 193 | title = {Policy Routing in Internet Protocols}, 194 | note = {RFC 1102}, 195 | organization = IETF, 196 | year = 1989, 197 | month = may 198 | } 199 | 200 | @manual{rfc1112, 201 | author = {Steve Deering}, 202 | title = {Host Extensions for IP Multicasting}, 203 | note = {RFC 1112}, 204 | organization = IETF, 205 | year = 1989, 206 | address = {SRI International, Menlo Park, CA}, 207 | month = aug, 208 | } 209 | 210 | @manual{rfc1122, 211 | key = "RFC 1122", 212 | author = "Braden, R. T.", 213 | title = "{Requirements for Internet Hosts---Communication Layers}", 214 | organization = IETF, 215 | note = {RFC 1122}, 216 | month = oct, 217 | year = 1989, 218 | } 219 | 220 | @manual{rfc1142, 221 | key = "RFC 1142", 222 | author = "Oran, D.", 223 | title = "{OSI IS-IS intra-domain routing protocol}", 224 | organization = IETF, 225 | note = {RFC 1142}, 226 | month = feb, 227 | year = 1990 228 | } 229 | 230 | @manual{rfc1144, 231 | author = {Jacobson, V.}, 232 | title = "{Compressing TCP/IP Headers for Low-speed Serial Links}", 233 | organization = IETF, 234 | note = {RFC 1144}, 235 | year = 1990, 236 | month = feb, 237 | } 238 | 239 | @manual{rfc1151, 240 | author = {Partridge, C. and Hinden, R.~M.}, 241 | title = "{Version 2 of the Reliable Data Protocol (RDP)}", 242 | organization = IETF, 243 | note = {RFC 1151}, 244 | year = 1990, 245 | month = apr, 246 | } 247 | 248 | 249 | @manual{rfc1191, 250 | author = {Mogul, J. and Deering, S.}, 251 | title = "{Path MTU Discovery}", 252 | organization = IETF, 253 | note = {RFC 1191}, 254 | year = 1990, 255 | month = nov, 256 | } 257 | 258 | @manual{rfc1323, 259 | author = "Jacobson, V. and Braden, R. and Borman, D.", 260 | title = "{TCP} Extensions for High Performance", 261 | note = {RFC 1323}, 262 | organization = IETF, 263 | year = 1992, 264 | month = may, 265 | } 266 | 267 | @manual{rfc1379, 268 | author = "Braden, R.", 269 | title = "Extending {TCP} for Transactions -- Concepts", 270 | year = 1992, 271 | month = nov, 272 | note = {RFC 1379}, 273 | organization = IETF 274 | } 275 | 276 | @manual{rfc1426, 277 | author = "J. Klensin and N. Freed and M. Rose and E. Stefferud and D. Crocker", 278 | title = "{SMTP Service Extension for 8bit-MIMEtransport}", 279 | organization = IETF, 280 | note = {RFC 1426}, 281 | year = 1993, 282 | month = feb 283 | } 284 | 285 | @manual{rfc1478, 286 | author = "M. Steenstrup", 287 | title = "{An Architecture for Inter-Domain Policy Routing}", 288 | organization = IETF, 289 | note = {RFC 1478}, 290 | year = 1993, 291 | month = jun 292 | } 293 | 294 | @manual{rfc1518, 295 | author="Rekhter, Y. and Li, T.", 296 | title="An Architecture for {IP} Address Allocation with {CIDR}", 297 | organization = IETF, 298 | note = {RFC 1518}, 299 | month=sep, 300 | year=1993, 301 | abstract="This paper provides an architecture and a plan for 302 | allocating IP addresses in the Internet. This architecture 303 | and the plan are intended to play an important role in 304 | steering the Internet towards the Address Assignment and 305 | Aggregating Strategy outlined in RFC XXX. The IP address 306 | space is a scarce shared resource that must be managed for 307 | the good of the community. The managers of this resource 308 | are acting as its custodians. They have a responsibility to 309 | the community to manage it for the common good.", 310 | URL="\url{ftp://ftp.isi.edu/in-notes/rfc1518.txt}", 311 | entryby=Sc 312 | } 313 | 314 | @manual{rfc1519, 315 | author="Fuller, V. and Li, T. and Yu, J. and Varadhan, K.", 316 | title="Classless Inter-Domain Routing {(CIDR):} an Address Assignment 317 | and Aggregation Strategy", 318 | organization = IETF, 319 | note = {RFC 1519}, 320 | month=sep, 321 | year=1993, 322 | abstract="This memo discusses strategies for address assignment of 323 | the existing IP address space with a view to conserve the 324 | address space and stem the explosive growth of routing 325 | tables in default-route-free routers.", 326 | URL="ftp://ftp.isi.edu/in-notes/rfc1519.txt", 327 | entryby=Sc 328 | } 329 | 330 | @manual{rfc1520, 331 | author="Rekhter, Y. and Topolcic, C.", 332 | title="Exchanging Routing Information Across Provider Boundaries in the 333 | {CIDR} Environment", 334 | organization = IETF, 335 | note = {RFC 1520}, 336 | month=sep, 337 | year=1993, 338 | abstract={Classless Inter-Domain Routing (CIDR) has been adopted as 339 | a solution to the scaling problem in the Internet. The 340 | overall CIDR architecture is described in RFC XXX. The 341 | architecture for IP address assignment with CIDR is covered 342 | in RFC XXX and RFC XXX. The inter-domain routing protocols 343 | that are capable of supporting CIDR are covered in RFC 344 | XXX. The purpose of this document is twofold. First, it 345 | describes various alternatives for exchanging inter-domain 346 | routing information across domain boundaries, where one of 347 | the peering domain is CIDR-capable and another is 348 | not. Second, it addresses the implications of running 349 | CIDR-capable inter-domain routing protocols (e.g., BGP-4, 350 | IDRP) on intra-domain routing. This document is not 351 | intended to cover all the cases (either real or 352 | imaginable). Rather, it focuses on what are viewed to be 353 | the most common cases. We expect that individual service 354 | providers will use this document as guidelines in 355 | establishing their specific operational plans for the 356 | transition to CIDR. The concepts of "network service 357 | provider" and "network service subscriber" were introduced 358 | in RFC XXX. For the sake of brevity, we will use the term 359 | "provider" or "service provider" here to mean either 360 | "network service provider" or "network service subscriber", 361 | since for the most part, the distinction is not important 362 | to this discussion. Furthermore, we use the same terms to 363 | refer to the network and to the organization that operates 364 | the network. We feel that the context makes it amply clear 365 | whether we are talking about hardware or people, and 366 | defining different terms would only make this paper harder 367 | to read.}, 368 | URL="ftp://ftp.isi.edu/in-notes/rfc1520.txt", 369 | entryby=Sc 370 | } 371 | 372 | @manual{rfc1521, 373 | author = "Borenstein, N. and Freed, N.", 374 | title = "{MIME (Multipurpose Internet Mail Extensions) Part 375 | One: Mechanisms for Specifying and Describing the Format of Internet 376 | Message Bodies}", 377 | organization = IETF, 378 | note = "{RFC 1521}", 379 | year = 1993, 380 | month = sep, 381 | } 382 | 383 | @manual{rfc1546, 384 | author = "Partridge, C. and Mendez, T. and Milliken, W.", 385 | title = {Host Anycasting Service}, 386 | note = {RFC 1546}, 387 | organization = IETF, 388 | year = 1993, 389 | month = nov 390 | } 391 | 392 | @manual{rfc1548, 393 | author = "Simpson, W.", 394 | title = "{The Point-to-Point Protocol (PPP)}", 395 | note = {RFC 1548}, 396 | organization = IETF, 397 | month = dec, 398 | year = 1993, 399 | } 400 | 401 | @manual{rfc1583, 402 | author = "Moy, J.", 403 | title = {OSPF Version 2}, 404 | note = "{RFC 1583}", 405 | month = mar, 406 | year = 1994, 407 | } 408 | 409 | @manual{rfc1771, 410 | author= "Y. Rekhter and T. Li", 411 | title="{A Border Gateway Protocol 4 (BGP-4)}", 412 | note = {RFC 1771}, 413 | organization = IETF, 414 | year=1995, 415 | month=mar, 416 | } 417 | 418 | @manual{rfc1794, 419 | author = "T. Brisco", 420 | title = "{DNS Support for Load Balancing}", 421 | note = {RFC 1794}, 422 | organization = IETF, 423 | year=1995, 424 | month=apr, 425 | } 426 | 427 | @manual{rfc1809, 428 | title="Using the Flow Label Field in IPv6", 429 | author="C. Partridge", 430 | month=jun, 431 | note = {RFC 1809}, 432 | year=1995, 433 | organization = IETF, 434 | } 435 | 436 | @manual{rfc1812, 437 | author = "F. Baker", 438 | title = "Requirements for {IP} {V}ersion 4 Routers", 439 | note= "{RFC~1812}", 440 | organization = IETF, 441 | URL = "\url{http://www.ietf.org/rfc/rfc1812.txt}", 442 | month = jun, 443 | year = 1995 444 | } 445 | 446 | @manual{rfc1813, 447 | author = "B. Callaghan and B. Pawlowski and P. Staubach", 448 | title = {{NFS} Version 3 Protocol Specification}, 449 | note = {RFC 1813}, 450 | month = jun, 451 | year = 1995, 452 | } 453 | 454 | @manual{rfc1866, 455 | author = {Berners-Lee, T.}, 456 | title = {Hypertext Markup Language - 2.0}, 457 | note = {RFC 1866}, 458 | organization = {MIT Laboratory for Computer Science}, 459 | year = 1995, 460 | month = nov 461 | } 462 | 463 | @manual{rfc1884, 464 | author = "Hinden, R. and Deering, S.", 465 | title = {IP Version 6 Addressing Architecture}, 466 | note = {RFC 1884}, 467 | organization = IETF, 468 | year = 1995, 469 | month = dec 470 | } 471 | 472 | @manual{rfc1889, 473 | author = "Schulzrinne, H. and Casner, S. and Frederick, R. and Jacobson, V.", 474 | title = {RTP: A Transport Protocol for Real-Time Applications}, 475 | organization = IETF, 476 | note = {RFC 1889}, 477 | year = 1996, 478 | month = jan 479 | } 480 | 481 | @manual{rfc1918, 482 | author = {Rekhter,, Y. and Moskowitz,, B. and Karrenberg,, D. and Groot,, G. J. de and Lear,, E.}, 483 | title = {Address Allocation for Private Internets}, 484 | year = 1996, 485 | publisher = {RFC Editor}, 486 | address = {United States}, 487 | } 488 | 489 | 490 | 491 | @manual{rfc1945, 492 | author = "Berners-Lee, T. and Fielding, R. and Frystyk, H.", 493 | title = "{Hypertext Transfer Protocol--HTTP/1.0}", 494 | organization = IETF, 495 | note = {RFC 1945}, 496 | year = 1996, 497 | month = may, 498 | } 499 | 500 | @manual{rfc1948, 501 | author = "S. Bellovin.", 502 | title = "{Defending Against Sequence Number Attacks}", 503 | organization = IETF, 504 | note = {RFC 1948}, 505 | year = 1996, 506 | month = may, 507 | } 508 | 509 | @manual{rfc1992, 510 | title = {The Nimrod Routing Architecture}, 511 | author = {I. Canstineyra and N. Chiappa and M. Steenstrup}, 512 | organization = IETF, 513 | month = aug, 514 | year = 1996, 515 | note = {RFC 1992}, 516 | } 517 | 518 | @manual{rfc1997, 519 | title = {{BGP} Communities Attribute}, 520 | author = {R. Chandra and P. Traina }, 521 | organization = IETF, 522 | month = aug, 523 | year = 1996, 524 | note = {RFC 1997}, 525 | } 526 | 527 | 528 | 529 | @manual{rfc2001, 530 | author = "Stevens, W. R.", 531 | title = "{TCP Slow Start, Congestion Avoidance, Fast Retransmit, and Fast Recovery Algorithms}", 532 | organization = IETF, 533 | note = {RFC 2001}, 534 | year = 1997, 535 | month = jan 536 | } 537 | 538 | @manual{rfc2002, 539 | author = "Perkins, C.", 540 | title = {IP Mobility Support}, 541 | organization = IETF, 542 | note = {RFC 2002}, 543 | year = 1996, 544 | month = oct 545 | } 546 | 547 | @manual{rfc2018, 548 | author = "Mathis, M. and Mahdavi, J. and Floyd, S. and Romanow, A.", 549 | title = "{TCP} Selective Acknowledgment Options", 550 | organization = IETF, 551 | note = "{RFC 2018}", 552 | year = 1996, 553 | } 554 | 555 | @manual{rfc2068, 556 | author = "Fielding, R. and Gettys, J. and Mogul, J. and Frystyk, H. and Berners-Lee, T.", 557 | title = "{Hypertext Transfer Protocol---HTTP/1.1}", 558 | note = {RFC 2068}, 559 | organization = IETF, 560 | year = 1997, 561 | month = jan 562 | } 563 | 564 | @manual{rfc2104, 565 | author = "Crawczyk, H. and Bellare, M. and Canetti, R.", 566 | title = {HMAC: Keyed-Hashing for Message Authentication}, 567 | note = {RFC 2104}, 568 | organization = IETF, 569 | year = 1997, 570 | month = feb 571 | } 572 | 573 | @manual{rfc2131, 574 | author = "R. Droms", 575 | title = "Dynamic Host Configuration Protocol", 576 | note = "{RFC~2131}", 577 | organization = IETF, 578 | URL = "\url{http://www.ietf.org/rfc/rfc2131.txt}", 579 | year = 1997, 580 | month = mar 581 | } 582 | 583 | @manual{rfc2140, 584 | author = "Touch, J.", 585 | title = {TCP Control Block Interdependence}, 586 | note = {RFC 2140}, 587 | organization = IETF, 588 | year = 1997, 589 | month = apr 590 | } 591 | 592 | @manual{rfc2182, 593 | author = "R. Elz and R. Bush and S. Bradner and M. Patton", 594 | title = {Selection and Operation of Secondary DNS Servers}, 595 | note = {RFC 2182 / BCP 16}, 596 | organization = IETF, 597 | year = 1997, 598 | month = jul 599 | } 600 | 601 | @manual{rfc2186, 602 | author = "D. Wessels and K. Claffy", 603 | title = {Internet Cache Protocol (ICP), version 2}, 604 | note = {RFC 2186}, 605 | organization = IETF, 606 | year = 1997, 607 | month = sep 608 | } 609 | 610 | @manual{rfc2187, 611 | author = "D. Wessels and K. Claffy", 612 | title = {Application of Internet Cache Protocol (ICP), version 2}, 613 | note = {RFC 2187}, 614 | organization = IETF, 615 | year = 1997, 616 | month = sep 617 | } 618 | 619 | @manual{rfc2205, 620 | author = "R. Braden and L. Zhang and S. Berson and S. Herzog and S. Jamin", 621 | title = "Resource {ReSerVation Protocol} ({RSVP})", 622 | note = {RFC 2205}, 623 | organization = IETF, 624 | year = 1997, 625 | month = sep 626 | } 627 | 628 | @manual{rfc2246, 629 | author = {Tim Dierks and Christopher Allen}, 630 | title = {The {TLS} Protocol Version 1.0}, 631 | organization = IETF, 632 | note = {RFC 2246, Proposed Standard}, 633 | month = jan, 634 | year = 1999 635 | } 636 | 637 | @manual{rfc2250, 638 | author = "D. Hoffman and G. Fernando and V. Goyal", 639 | title = {RTP Payload Format for MPEG1/MPEG2 Video}, 640 | note = {RFC 2250}, 641 | organization = IETF, 642 | year = 1998, 643 | month = jan 644 | } 645 | % Obsoleted by RFC 2827 646 | @manual{rfc2267, 647 | author = "Paul Ferguson and Daniel Senie", 648 | title = "Network Ingress Filtering: Defeating Denial of Service 649 | Attacks which employ {IP} Source Address Spoofing", 650 | note = {RFC 2267}, 651 | organization = IETF, 652 | month = jan, 653 | year = 1998 654 | } 655 | 656 | 657 | @manual{rfc2295, 658 | author = "Holtman, K.", 659 | title = {Transparent Content Negotiation in HTTP}, 660 | note = {RFC 2295}, 661 | organization = IETF, 662 | year = 1998, 663 | month = mar 664 | } 665 | 666 | @manual{rfc2309, 667 | author = "Braden, B. and Clark, D. and Crowcroft, J. and Davie, B. and 668 | Deering, S. and Estrin, D. and Floyd, S. and Jacobson, V. and Minshall, G. and Partridge, C. and Peterson, L. and Ramakrishnan, K. and Shenker, S. and Wroclawski, J. and Zhang, L.", 669 | title = "{Recommendations on Queue Management and Congestion Avoidance in the Internet}", 670 | note = {RFC 2309}, 671 | organization = IETF, 672 | year = 1998, 673 | month = apr, 674 | } 675 | 676 | @manual{rfc2326, 677 | author = "Schulzrinne, H. and Rao, A. and Lanphier, R.", 678 | title = {Real Time Streaming Protocol (RTSP)}, 679 | note = {RFC 2326}, 680 | organization = IETF, 681 | year = 1998, 682 | month = apr 683 | } 684 | 685 | @manual{rfc2327, 686 | author = "Handley, M. and Jacobson, V.", 687 | title = {Session Description Protocol}, 688 | note = {RFC 2327}, 689 | organization = IETF, 690 | year = 1998, 691 | month = apr 692 | } 693 | 694 | @manual{rfc2330, 695 | author="V. Paxson and G. Almes and J. Mahdavi and M. Mathis", 696 | title="Framework for IP Performance Metrics", 697 | note = {RFC 2330}, 698 | organization = IETF, 699 | year=1998, 700 | month=may 701 | } 702 | 703 | @manual{rfc2343, 704 | author="M. Civanlar and G. Cash and B. Haskell", 705 | title="RTP Payload Format for Bundled MPEG ", 706 | note = {RFC 2343}, 707 | organization = IETF, 708 | year=1998, 709 | month=may 710 | } 711 | 712 | @manual{rfc2385, 713 | title = {Protection of BGP Sessions via the TCP MD5 Signature Option}, 714 | author = {A. Heffernan}, 715 | organization = IETF, 716 | month = aug, 717 | year = 1998, 718 | note = {RFC 2385}, 719 | } 720 | 721 | 722 | 723 | @manual{rfc2401, 724 | author = "S. Kent and R. Atkinson", 725 | title = "{Security Architecture for the Internet Protocol}", 726 | note = "{RFC~2401}", 727 | organization = IETF, 728 | month = nov, 729 | year = 1998, 730 | } 731 | 732 | 733 | @manual{rfc2406, 734 | author = "S. Kent and R. Atkinson", 735 | title = "{IP} Encapsulating Security Payload ({ESP})", 736 | note = "{RFC~2406}", 737 | organization = IETF, 738 | URL = "\url{http://www.ietf.org/rfc/rfc2406.txt}", 739 | year = 1998, 740 | } 741 | 742 | @manual{rfc2411, 743 | author="R. Thayer and N. Doraswamy and R. Glenn", 744 | title="IP Security Document Roadmap", 745 | note={RFC 2411}, 746 | organization = IETF, 747 | year=1998, 748 | month=nov 749 | } 750 | 751 | @manual{rfc2412, 752 | author = "H. Orman", 753 | title = "The {OAKLEY} Key Determination Protocol", 754 | note={RFC 2412}, 755 | organization = IETF, 756 | year = 1998, 757 | month = nov 758 | } 759 | 760 | @manual{rfc2439, 761 | author="C. Villamizar and R. Chandra and R. Govindan", 762 | title="{BGP} Route Flap Damping", 763 | note={RFC 2439}, 764 | organization = IETF, 765 | year=1998, 766 | month=nov 767 | } 768 | 769 | @manual{rfc2453, 770 | author = "Malkin, G.", 771 | title = "{RIP Version 2}", 772 | note = {RFC 2453}, 773 | organization = IETF, 774 | year = 1998, 775 | month = nov, 776 | } 777 | 778 | @manual{rfc2460, 779 | author = "S. Deering and R. Hinden", 780 | title = "{Internet Protocol, Version 6 (IPv6) Specification}", 781 | note = {RFC 2460}, 782 | organization = IETF, 783 | year = 1998, 784 | month = dec, 785 | } 786 | 787 | 788 | @manual{rfc2474, 789 | author = "K. Nichols and S. Blake and F. Baker and D. Black", 790 | title = "{D}efinition of the {Differentiated} {Services} Field ({DS} Field) in the {IPv4} and {IPv6} Headers", 791 | note = "{RFC~2474}", 792 | organization = IETF, 793 | URL = "\url{http://www.ietf.org/rfc/rfc2474.txt}", 794 | year = 1998, 795 | month = dec, 796 | } 797 | 798 | @manual{rfc2475, 799 | author = "Blake, S. and Black, D. and Carlson, M. and Davies, E. and Wang, Z. and Weiss, W.", 800 | title = "{An Architecture for Differentiated Services}", 801 | note = {RFC 2475}, 802 | organization = IETF, 803 | year = 1998, 804 | month = dec, 805 | } 806 | 807 | @manual{rfc2481, 808 | author = "Ramakrishnan, K. and Floyd, S.", 809 | title = "A Proposal to Add Explicit Congestion Notification ({ECN}) to {IP}", 810 | note = {RFC 2481}, 811 | organization = IETF, 812 | year = 1999, 813 | month = jan, 814 | } 815 | 816 | @manual{rfc2507, 817 | author = "M. Degermark and B. Nordgren and S. Pink", 818 | title = "{IP} header compression", 819 | organization = IETF, 820 | note = "{RFC~2507}", 821 | year = 1999, 822 | month = feb 823 | } 824 | %URL = "\url{http://www.ietf.org/rfc/rfc2507.txt}", 825 | 826 | @manual{rfc2547, 827 | author = "E. Rosen and Y. Rekhter", 828 | title = "{BGP/MPLS VPNs}", 829 | organization = IETF, 830 | note = "{RFC~2547}", 831 | URL = "\url{http://www.ietf.org/rfc/rfc2547.txt}", 832 | year = 1999, 833 | month = mar 834 | } 835 | 836 | 837 | @manual{rfc2581, 838 | author = "Allman, M. and Paxson, V.", 839 | title = "{TCP Congestion Control}", 840 | note = {RFC 2581}, 841 | organization = IETF, 842 | year = 1999, 843 | month = apr, 844 | } 845 | 846 | @manual{rfc2597, 847 | author = "J. Heinanen and F. Baker and W. Weiss and J. Wroclawski", 848 | title = "{A}ssured Forwarding {PHB} Group", 849 | note = "{RFC~2597}", 850 | organization = IETF, 851 | URL = "\url{http://www.ietf.org/rfc/rfc2597.txt}", 852 | year = 1999, 853 | month = jun, 854 | } 855 | 856 | @manual{rfc2582, 857 | author = "Floyd, S. and Henderson, T.", 858 | title = "{The NewReno Modification to TCP's Fast Recovery Algorithm}", 859 | note = {RFC 2582}, 860 | organization = IETF, 861 | year = 1999, 862 | month = apr, 863 | } 864 | 865 | @manual{rfc2608, 866 | author="Guttman, E. and Perkins, C. and Veizades, J. and Day, M.", 867 | title="Service Location Protocol, Version 2", 868 | organization = ietf, 869 | note = {RFC 2608}, 870 | month=jun, 871 | year=1999, 872 | abstract="The Service Location Protocol provides a scalable 873 | framework for the discovery and selection of network 874 | services. Using this protocol, computers using the Internet 875 | need little or no static configuration of network services 876 | for network based applications. This is especially 877 | important as computers become more portable, and users less 878 | tolerant or able to fulfill the demands of network system 879 | administration.", 880 | URL="ftp://ftp.isi.edu/in-notes/rfc2608.txt", 881 | entryby=Sc 882 | } 883 | 884 | @manual{rfc2616, 885 | author = "R. Fielding and J. Gettys and J. Mogul and H. Frystyk and L. Masinter and P. Leach and T. Berners-Lee", 886 | title = "Hyptertext Transfer Protocol -- {HTTP/1.1}", 887 | year = 1999, 888 | month = jun, 889 | organization = IETF, 890 | note = {RFC 2616} 891 | } 892 | 893 | @manual{rfc2622, 894 | title = {Routing Policy Specification Language (RPSL)}, 895 | author = {Alaettinoglu, C. and others}, 896 | month = jun, 897 | year = 1999, 898 | note = {RFC 2622}, 899 | organization = IETF, 900 | } 901 | 902 | @manual{rfc2660, 903 | title = {The Secure HyperText Transfer Protocol}, 904 | athor = {Rescorla, E. and Schiffman, A.}, 905 | month = aug, 906 | year = 1999, 907 | note = {RFC 2660}, 908 | organization = IETF 909 | } 910 | 911 | @manual{rfc2663, 912 | title = {IP Network Address Translator (NAT) Terminology and Considerations}, 913 | athor = {Srisuresh, P. and Holdrege, M.}, 914 | month = aug, 915 | year = 1999, 916 | note = {RFC 2663}, 917 | organization = IETF 918 | } 919 | 920 | @manual{rfc2692, 921 | title = {SPKI Requirements}, 922 | author = {Ellison, C.}, 923 | month = sep, 924 | year = 1999, 925 | note = {RFC 2692}, 926 | organization = IETF, 927 | } 928 | 929 | @manual{rfc2693, 930 | title = {SPKI Certificate Theory}, 931 | author = {Ellison, C. and Frantz, B. and Lampson, B. and Rivest, R. and Thomas, B. and Ylonen, T.}, 932 | month = sep, 933 | year = 1999, 934 | note = {RFC 2693}, 935 | organization = IETF, 936 | } 937 | 938 | @manual{rfc2702, 939 | title = {Requirements for Traffic Engineering Over MPLS}, 940 | author = {D. Awduche and J. Malcolm and J. Agogbua and M. O'Dell and J. McManus}, 941 | month = sep, 942 | year = 1999, 943 | note = {RFC 2702}, 944 | organization = IETF, 945 | } 946 | 947 | @manual{rfc2756, 948 | title = {Hyper Text Caching Protocol (HTCP/0.0)}, 949 | author = {Paul Vixie and Duane Wessels}, 950 | month = jan, 951 | year = 2000, 952 | note = {RFC 2756}, 953 | organization = IETF, 954 | } 955 | 956 | 957 | @manual{rfc2782, 958 | title = {A DNS RR for specifying the location of services (DNS SRV)}, 959 | author = {A. Gulbrandsen and P. Vixie and L. Esibov}, 960 | month = feb, 961 | year = 2000, 962 | note = {RFC 2782}, 963 | organization = IETF, 964 | } 965 | 966 | @manual{rfc2796, 967 | title = {{BGP} Route Reflection - An Alternative to Full Mesh {IBGP}}, 968 | author = {T. Bates and R. Chandra and E. Chen}, 969 | month = apr, 970 | year = 2000, 971 | note = {RFC 2796}, 972 | organization = IETF, 973 | } 974 | 975 | @manual{rfc2821, 976 | author = {J. Klensin}, 977 | title = {Simple Mail Transfer Protocol}, 978 | month = apr, 979 | year = 2001, 980 | note = {RFC 2821}, 981 | organization = IETF 982 | } 983 | 984 | @manual{rfc2827, 985 | author = "Paul Ferguson and Daniel Senie", 986 | title = "Network Ingress Filtering", 987 | year = 2000, 988 | month = may, 989 | note = {BCP 38, RFC 2827}, 990 | organization = IETF 991 | } 992 | 993 | @manual{rfc2858, 994 | author = "Bates T., Rekhter Y., Chandra R. and Katz D.", 995 | title = "Multiprotocol Extensions for BGP-4", 996 | year = 2000, 997 | month = jun, 998 | note = {RFC 2858}, 999 | organization = IETF 1000 | } 1001 | 1002 | @manual{rfc2883, 1003 | author = "Floyd S., Mahdavi J., Mathis M. and Podolsky M.", 1004 | title = "{An Extension to the Selective Acknowledgement (SACK) Option for TCP}", 1005 | note = {RFC 2883}, 1006 | organization = IETF, 1007 | year = 2000, 1008 | month = jul, 1009 | } 1010 | 1011 | @manual{rfc2988, 1012 | author = "Vern Paxson and Mark Allman", 1013 | title = "{Computing TCP's Retransmission Timer}", 1014 | note = {RFC 2988}, 1015 | organization = IETF, 1016 | year = 2000, 1017 | month = nov 1018 | } 1019 | 1020 | @manual{rfc2992, 1021 | author = "C. Hopps", 1022 | title = "Analysis of an Equal-cost Multi-Path algorithm", 1023 | note = {RFC 2992}, 1024 | organization = IETF, 1025 | year = 2000, 1026 | month = nov 1027 | } 1028 | 1029 | @manual{rfc3013, 1030 | author = "T. Killalea", 1031 | title = "{Internet Service Provider Security Services and Procedures}", 1032 | note = {RFC 3013}, 1033 | organization = IETF, 1034 | year = 2000, 1035 | month = nov 1036 | } 1037 | 1038 | 1039 | 1040 | @manual{rfc3016, 1041 | author = "Kikuchi, Y. and Nomura, T. and Fukunaga, S. and Matsui, Y. and Kimata, H.", 1042 | title = "{RTP Payload Format for MPEG-4 Audio/Visual Streams}", 1043 | note = {RFC 3016}, 1044 | organization = IETF, 1045 | year = 2000, 1046 | month = nov, 1047 | } 1048 | 1049 | @manual{rfc3027, 1050 | author = "Holdrege, M. and Srisuresh, P.", 1051 | title = "{Protocol Complications with the IP Network Address Translator}", 1052 | note = {RFC 3027}, 1053 | organization = IETF, 1054 | year = 2001, 1055 | month = jan 1056 | } 1057 | 1058 | @manual{rfc3042, 1059 | author="Allman, M. and Balakrishnan, H. and Floyd, S.", 1060 | title="Enhancing {TCP}'s Loss Recovery Using Limited Transmit", 1061 | note = "{RFC 3042}", 1062 | organization=IETF, 1063 | month=jan, 1064 | year=2001, 1065 | } 1066 | 1067 | @manual{rfc3065, 1068 | author="P. Traina and D. McPherson and J. Scudder", 1069 | title="{Autonomous System Confederations for BGP}", 1070 | note = "{RFC 3065}", 1071 | organization=IETF, 1072 | month=feb, 1073 | year=2001, 1074 | } 1075 | 1076 | @manual{rfc3080, 1077 | author="M. Rose", 1078 | title="The Blocks Extensible Exchange Protocol Core", 1079 | note = "{RFC 3080}", 1080 | organization=IETF, 1081 | month=mar, 1082 | year=2001, 1083 | } 1084 | 1085 | @manual{rfc3117, 1086 | author="Rose, M.", 1087 | title="{On the Design of Application Protocols}", 1088 | note = "{RFC} 3117", 1089 | organization=IETF, 1090 | month=nov, 1091 | year=2001, 1092 | } 1093 | 1094 | @manual{rfc3124, 1095 | author="Balakrishnan, H. and Seshan, S.", 1096 | title="{The Congestion Manager}", 1097 | note = "{RFC 3124}", 1098 | organization=IETF, 1099 | month=jun, 1100 | year=2001, 1101 | } 1102 | 1103 | @manual{rfc3168, 1104 | author = "Ramakrishnan, K. K. and Floyd, S. and Black, D.", 1105 | title = "The Addition of Explicit Congestion Notification {(ECN)} to {IP}", 1106 | note = "{RFC} 3168", 1107 | organization = IETF, 1108 | month = sep, 1109 | year = 2001 1110 | } 1111 | 1112 | @manual{rfc3208, 1113 | author = "T. Speakman et al", 1114 | title = "{PGM} Reliable Transport Protocol Specification", 1115 | note = "{RFC~3208}", 1116 | organization = IETF, 1117 | URL = "\url{http://www.ietf.org/rfc/rfc3208.txt}", 1118 | year = 2001, 1119 | month = dec 1120 | } 1121 | 1122 | @manual{rfc3209, 1123 | author = "D. Awduche and L. Berger and D. Gan and T. Li and V. Srinivasan and G. Swallow", 1124 | title = "{RSVP-TE}: Extensions to {RSVP} for {LSP} Tunnels", 1125 | month = dec, 1126 | year = 2001, 1127 | organization = IETF, 1128 | note = "{RFC} 3209" 1129 | } 1130 | 1131 | @manual{rfc3221, 1132 | author="Geoff Huston", 1133 | title="Commentary on Inter-Domain Routing in the Internet", 1134 | note = "{RFC 3221}", 1135 | organization=IETF, 1136 | month=dec, 1137 | year=2001, 1138 | } 1139 | 1140 | @manual{rfc3345, 1141 | title = {{B}order {G}ateway {P}rotocol ({BGP}) Persistent Route Oscillation Condition}, 1142 | author = { D. McPherson and V. Gill and D. Walton and A. Retana}, 1143 | organization = IETF, 1144 | month = aug, 1145 | year = 2002, 1146 | note = {RFC 3345}, 1147 | } 1148 | 1149 | @manual{rfc3272, 1150 | author="Daniel O. Awduche and Angela Chiu and Anwar Elwalid and Indra Widjaja and XiPeng Xiao", 1151 | title="Overview and Principles of Interent Traffic Engineering", 1152 | note = "{RFC 3272}", 1153 | organization=IETF, 1154 | month=may, 1155 | year=2002, 1156 | } 1157 | 1158 | @manual{rfc3286, 1159 | author = "L. Ong and J. Yoakum", 1160 | title = "An Introduction to the {S}tream {C}ontrol {T}ransmission {P}rotocol {(SCTP)}", 1161 | year = 2002, 1162 | month = may, 1163 | organization = IETF, 1164 | note = "{RFC 3286}" 1165 | } 1166 | 1167 | @manual{rfc3330, 1168 | author="IANA", 1169 | title="{Special Use IPv4 Addresses}", 1170 | note = "{RFC 3330}", 1171 | organization=IETF, 1172 | month=sep, 1173 | year=2002, 1174 | } 1175 | 1176 | @manual{rfc3393, 1177 | title = {{IP}{P}acket {D}elay {M}etric }, 1178 | author = { T. Demichelis and P. Chimento}, 1179 | organization = IETF, 1180 | month = nov, 1181 | year = 2002, 1182 | note = {RFC 3393}, 1183 | } 1184 | 1185 | @manual{rfc3411, 1186 | author = "D. Harrington and R. Preshun and B. Wijnen", 1187 | title = "An Architecture for Describing Simple Network Management Protocol (SNMP) Management Frameworks", 1188 | note = "{RFC} 3411", 1189 | organization=IETF, 1190 | month = dec, 1191 | year = 2002 1192 | } 1193 | 1194 | @manual{rfc3522, 1195 | author = "R. Ludwig and M. Meyer", 1196 | title = "The Eifel Detection Algorithm for TCP", 1197 | note = "{RFC} 3522", 1198 | organization=IETF, 1199 | month = apr, 1200 | year = 2003 1201 | } 1202 | 1203 | @manual{rfc3568, 1204 | author= "A. Barbir and B. Cain and R. Nair and O. Spatscheck", 1205 | title= "{Known Content Network (CN) Request-Routing Mechanisms}", 1206 | note = "{RFC} 3568", 1207 | organization=IETF, 1208 | year=2003, 1209 | month=jul 1210 | } 1211 | 1212 | 1213 | @manual{rfc3630, 1214 | author= "D. Katc and K. Kompella and D. Yeung", 1215 | title= "{Traffic Engineering (TE) Extensions to OSPF Version 2}", 1216 | note = "{RFC} 3630", 1217 | organization=IETF, 1218 | year=2003, 1219 | month=sep 1220 | } 1221 | 1222 | @manual{rfc3784, 1223 | author= "H. Smith and T. Li", 1224 | title= "{Intermediate System to Intermediate System (IS-IS) Extensions for Traffic Engineering (TE)}", 1225 | note = "{RFC} 3784", 1226 | organization=IETF, 1227 | year=2004, 1228 | month=jun 1229 | } 1230 | 1231 | @manual{rfc3782, 1232 | author= "S. Floyd and T. Henderson and A. Gurtov", 1233 | title= "{The NewReno Modification to TCP's Fast Recovery Algorithm}", 1234 | note = "{RFC} 3782", 1235 | organization=IETF, 1236 | year=2004, 1237 | month=apr 1238 | } 1239 | 1240 | 1241 | @manual{rfc3972, 1242 | author = "T. Aura", 1243 | title = "Cryptographically Generated Addresses ({CGA})", 1244 | note = "{RFC} 3972", 1245 | organization=IETF, 1246 | month = mar, 1247 | year = 2005 1248 | } 1249 | 1250 | @manual{rfc4124, 1251 | author = "Le Faucheur, F.", 1252 | title = "{Protocol Extensions for Support of Diffserv-aware MPLS Traffic Engineering}", 1253 | note = {RFC 4124}, 1254 | organization = IETF, 1255 | year = 2005, 1256 | month = jun 1257 | } 1258 | 1259 | @manual{rfc4138, 1260 | author = "P. Sarolahti and M. Kojo", 1261 | title = "Forward RTO-Recovery (F-RTO): An Algorithm for Detecting Spurious Retransmission Timeouts with TCP and the Stream Control Transmission Protocol (SCTP)", 1262 | note = "{RFC} 4138", 1263 | organization = IETF, 1264 | month = aug, 1265 | year = 2005 1266 | } 1267 | 1268 | @manual{rfc4251, 1269 | author= "Y. Ylonen and C. Lonvick", 1270 | title="The Secure Shell {SSH} Protocol Architecture", 1271 | note = {RFC 4251}, 1272 | organization = IETF, 1273 | year=2006, 1274 | month=jan 1275 | } 1276 | 1277 | @manual{rfc4271, 1278 | author= "Y. Rekhter and T. Li and S. Hares", 1279 | title="{A Border Gateway Protocol 4 (BGP-4)}", 1280 | note = {RFC 4271}, 1281 | organization = IETF, 1282 | year=2006, 1283 | month=jan, 1284 | } 1285 | 1286 | @manual{rfc4423, 1287 | author= "R. Moskowitz and P. Nikander", 1288 | title="{Host Identity Protocol (HIP) Architecture}", 1289 | note = {RFC 4423}, 1290 | organization = IETF, 1291 | year=2006, 1292 | month=may, 1293 | } 1294 | 1295 | @manual{rfc4655, 1296 | author= "A. Farrel and JP. Vasseur and J. Ash", 1297 | title="{A Path Computation Element (PCE)-Based Architecture}", 1298 | note = {RFC 4655}, 1299 | organization = IETF, 1300 | year=2006, 1301 | month=aug, 1302 | } 1303 | 1304 | @manual{rfc4787, 1305 | author= "F. Audet and C. Jennings", 1306 | title="Network Address Translation {(NAT)} Behavioral Requirements for Unicast {UDP}", 1307 | note = {RFC 4787}, 1308 | organization = IETF, 1309 | year=2007, 1310 | month=jan, 1311 | } 1312 | 1313 | @manual{rfc4915, 1314 | author= "P. Psenak and S. Mirtorabi and A. Roy and L. Nguyen and P. Pillay-Esnault", 1315 | title="{Multi-Topology Routing in OSPF}", 1316 | note = {RFC 4915}, 1317 | organization = IETF, 1318 | year=2007, 1319 | month=jun, 1320 | } 1321 | 1322 | @manual{rfc5150, 1323 | author= "A. Ayyangar and K. Kompella and JP. Vasseur and A. Farrel", 1324 | title="{Label Switched Path Stitching with Generalized Multiprotocol Label Switching Traffic Engineering (GMPLS TE)}", 1325 | note = {RFC 5150}, 1326 | organization = IETF, 1327 | year=2008, 1328 | month=feb, 1329 | } 1330 | 1331 | @manual{id-bgp4, 1332 | author="Rekhter, Y. and Li, T. and Hares, S.", 1333 | title="A Border Gateway Protocol 4 (BGP-4)", 1334 | note = "{Internet Draft draft-ietf-idr-bgp4-23.txt; work in progress}", 1335 | organization=IETF, 1336 | month=nov, 1337 | year=2003, 1338 | } 1339 | 1340 | @manual{id-ipv6, 1341 | author="Hinden, B. and Deering, S.", 1342 | title="Internet Protocol, Version 6 (IPv6) Specification", 1343 | note = "{Internet Draft draft-ietf-ipngwg-ipv6-spec-v2; work in progress}", 1344 | organization=IETF, 1345 | month=aug, 1346 | year=1998, 1347 | } 1348 | 1349 | @manual{id-2bit, 1350 | author="Nichols, K. and Jacobson, V. and Zhang, L.", 1351 | title="{A Two-bit Differentiated Services Architecture for the Internet}", 1352 | note = "{Internet Draft draft-nichols-diff-svc-arch-02.txt; work in progress}", 1353 | organization=IETF, 1354 | month=apr, 1355 | year=1999, 1356 | } 1357 | 1358 | @manual{id-cerf-dtn, 1359 | author = "V. Cerf and S. Burleigh and A. Hooke and L. Torgerson and R. Durst and K. Scott and K. Fall and H. Weiss", 1360 | title = "Delay-Tolerant Network Architecture", 1361 | note = "{Internet Draft draft-irtf-dtnrg-arch-02.txt; work in progress}", 1362 | organization = IETF, 1363 | month = jul, 1364 | year = 2004 1365 | } 1366 | 1367 | @manual{id-cm, 1368 | author="Balakrishnan, H. and Seshan, S.", 1369 | title="{The Congestion Manager}", 1370 | note = "{Internet Draft draft-balakrishnan-cm-03.txt (\url{http://www.ietf.org/internet-drafts/draft-balakrishnan-cm-03.txt}). Work in progress, expires May 2001}", 1371 | organization=IETF, 1372 | month=nov, 1373 | year=2000 1374 | } 1375 | 1376 | @misc{id-esd-analysis, 1377 | author = "M. Crawford and A. Mankin and T. Narten and J. W. Stewart and L. Zhang", 1378 | title = "Separating Identifiers and Locators in Addresses: An Analysis of the {GSE} Proposal for {IP}v6", 1379 | note = {Internet draft draft-ietf-ipngwg-esd-analysis-05.txt (Work in progress)}, 1380 | year = 1999, 1381 | month = Oct, 1382 | } 1383 | 1384 | 1385 | @manual{id-farinacci-lisp, 1386 | author = "D. Farinacci and V. Fuller and D. Oran and D. Meyer", 1387 | title = "{Locator/ID Separation Protocol (LISP)}", 1388 | note = "{Internet Draft (\url{http://tools.ietf.org/html/draft-farinacci-lisp-07}). Work in progress, expires October 2008}", 1389 | organization=IETF, 1390 | month=apr, 1391 | year = 2008, 1392 | } 1393 | 1394 | 1395 | @manual{id-forces-protocol, 1396 | author = "A. Doria and R. Haas and J. Salim and H. Khosravi and W. M. Wang", 1397 | title = "{ForCES Protocol Specification}", 1398 | note = "{Internet Draft (\url{http://www.ietf.org/internet-drafts/draft-ietf-corces-protocol-09.txt}). Work in progress, expires August 2007}", 1399 | organization=IETF, 1400 | month=mar, 1401 | year = 2007, 1402 | } 1403 | 1404 | 1405 | @manual{id-floyd-cm, 1406 | author = "Floyd, S.", 1407 | title = "{Congestion Control Principles}", 1408 | note = "{Internet Draft draft-floyd-cm-01.txt (\url{http://www.ietf.org/internet-drafts/draft-floyd-cong-01.txt}). Work in progress, expires June 2000}", 1409 | organization=IETF, 1410 | month=jan, 1411 | year = 2000, 1412 | } 1413 | 1414 | @manual{id-goland-ssdp, 1415 | title = {Simple Service Discovery Protocol/1.0, 1416 | Internet Draft, draft-cai-ssdp-v1-03.txt, Work in 1417 | Progress}, 1418 | author = {Goland et.al., Y. Y.}, 1419 | month = oct, 1420 | year = 1999, 1421 | } 1422 | 1423 | @manual{id-igp-convergence, 1424 | title = "Towards Mili-Second {IGP} Convergence", 1425 | author = "Cengiz Alaettinoglu and Van Jacobsen and Haobo Yu", 1426 | month = nov, 1427 | year = 2000, 1428 | organization = IETF, 1429 | note = "{Internet-Draft draft-alattinoglu-isis-convergence-00 \url{http://www.packetdesign.com/news/industry-publications/drafts/convergence.pdf}. Work in progress, expires May 2001}" 1430 | } 1431 | 1432 | @manual{id-li-ulp, 1433 | title = {An RTP Payload Format for Generic FEC with Uneven Level Protection}, 1434 | author = {A. Li and F. Liu and J. Villasenor and J. Park and D. Park and Y. Lee}, 1435 | organization = IETF, 1436 | OPTedition = {}, 1437 | month = oct, 1438 | year = 2001, 1439 | note = {\url{http://www.ietf.org/internet-drafts/draft-ietf-avt-ulp-02.txt} Work in progress, expires April 2002}, 1440 | } 1441 | 1442 | @manual{id-lisp-iab06, 1443 | title = "Locator/ID Separation Protocol (LISP)", 1444 | author = "D. Farinacci and V. Fuller and D. Oran and D. Meyer", 1445 | organization = IETF, 1446 | month = jul, 1447 | year = 2007, 1448 | note = {\url{http://www.ietf.org/internet-drafts/draft-farinacci-lisp-02.txt} Work in progress, expires January 18, 2008}, 1449 | } 1450 | 1451 | @manual{id-farinacci-lisp05, 1452 | title = "Locator/ID Separation Protocol (LISP)", 1453 | author = "D. Farinacci and V. Fuller and D. Oran and D. Meyer", 1454 | organization = IETF, 1455 | month = nov, 1456 | year = 2007, 1457 | note = {\url{http://www.ietf.org/internet-drafts/draft-farinacci-lisp-05.txt} Work in progress, expires May 17, 2008}, 1458 | } 1459 | 1460 | @manual{id-netconf, 1461 | title = {NETCONF Configuration Protocol}, 1462 | author = {R. Enns}, 1463 | organization = IETF, 1464 | OPTedition = {}, 1465 | month = jun, 1466 | year = 2005, 1467 | note = {\url{http://www.ietf.org/internet-drafts/draft-ietf-netconf-prot-07.txt} Work in progress, expires December 2005}, 1468 | } 1469 | 1470 | 1471 | 1472 | @manual{id-repos-struct, 1473 | title = {A Profile for Resource Certificate Repository Structure}, 1474 | author = {G. Huston and G. Michaelson and R. Loomans}, 1475 | organization = IETF, 1476 | month = jun, 1477 | year = 2006, 1478 | note = {\url{http://mirin.apnic.net/resourcecerts/project-notes/draft-ietf-sidr-repos-struct-00.html}}, 1479 | } 1480 | 1481 | 1482 | @manual{id-res-certs, 1483 | title = {A Profile for X.509 PKIX Resource Certificates}, 1484 | author = {G. Huston and G. Michaelson and R. Loomans}, 1485 | organization = IETF, 1486 | month = jul, 1487 | year = 2006, 1488 | note = {\url{http://mirin.apnic.net/resourcecerts/project-notes/draft-ietf-sidr-res-certs-02.html}}, 1489 | } 1490 | 1491 | 1492 | 1493 | 1494 | @manual{id-routing-reqs, 1495 | title = {Requirements For a Next Generation Routing and Addressing Architecture}, 1496 | author = {Kastenholtz, F. and others}, 1497 | organization = IETF, 1498 | month = apr, 1499 | year = 2002, 1500 | note = {\url{http://www.ietf.org/internet-drafts/draft-irtf-routing-reqs-groupa-00.txt}, expires October 2002}, 1501 | } 1502 | 1503 | @manual{id-routing-threats, 1504 | title = {Known Threats to Routing Protocols}, 1505 | author = {Beard, D. and others}, 1506 | organization = IETF, 1507 | month = oct, 1508 | year = 2002, 1509 | note = {\url{http://www.ietf.org/internet-drafts/draft-beard-rpsec-routing-threats-00.txt}}, 1510 | } 1511 | 1512 | @manual{id-troll-autoip, 1513 | title = {Automatically Choosing an IP Address in an Ad-Hoc 1514 | IPv4 Network, Internet-Draft, Work in Progress.}, 1515 | author = {R. Troll}, 1516 | month = oct, 1517 | year = 1999, 1518 | } 1519 | 1520 | @manual{id-lee-odmrp, 1521 | title = {On-Demand Multicast Routing Protocol (ODMRP) for 1522 | Ad Hoc Networks, Internet-Draft, Work in Progress.}, 1523 | author = {S. Lee and W. Su and M. Gerla}, 1524 | month = jan, 1525 | year = 2000, 1526 | } 1527 | 1528 | @manual{id-housley-crl, 1529 | title = {Internet X.509 Public Key Infrastructure, Certificate and CRL Profile, Internet Draft, PKIX Working Group. Work in Progress, expires May 2001.}, 1530 | author = {Housley, R. and Ford, W. and Polk, W. and Solo, D.}, 1531 | organization = IETF, 1532 | month = nov, 1533 | year = 2000, 1534 | note = {\url{http://www.ietf.org/internet-drafts/draft-ietf-pkix-new-part1-03.txt}}, 1535 | } 1536 | 1537 | @manual{id-miyazaki-rtpselret, 1538 | title = {RTP Payload Format to Enable Multiple Selective Retransmissions.}, 1539 | author = {Miyazaki, A. and others}, 1540 | organization = IETF, 1541 | month = nov, 1542 | year = 2001, 1543 | note = {\url{http://www.ietf.org/internet-drafts/draft-ietf-avt-rtp-selret-03.txt} Work in Progress, expires May 2002.}, 1544 | } 1545 | 1546 | @manual{id-multi-ospf, 1547 | title = "{Multi-Topology (MT) Routing in OSPF}", 1548 | author = {P. Psenak and S. Mirtorabi and A. Roy and L. Nguyen and P. Pillay-Esnault}, 1549 | organization = IETF, 1550 | month = jan, 1551 | year = 2007, 1552 | note = {\url{http://www.ietf.org/internet-drafts/draft-ietf-ospf-mt-08.txt} Work in Progress, expires July 2007.}, 1553 | } 1554 | 1555 | 1556 | 1557 | 1558 | @manual{id-ott-feedback, 1559 | title = { Extended RTP Profile for RTCP-based Feedback (RTP/AVPF).}, 1560 | author = {J. Ott and others}, 1561 | organization = IETF, 1562 | month = nov, 1563 | year = 2001, 1564 | note = {\url{http://www.ietf.org/internet-drafts/draft-ietf-avt-rtcp-feedback-01.txt} Work in Progress, expires May 2002.}, 1565 | } 1566 | 1567 | 1568 | @manual{id-scudder-bmp, 1569 | title = { BGP Monitoring Protocol}, 1570 | author = {J. Scudder}, 1571 | organization = IETF, 1572 | month = aug, 1573 | year = 2005, 1574 | note = {\url{http://tools.ietf.org/html/draft-scudder-bmp-00} Work in Progress, expired Feb 2006.}, 1575 | } 1576 | 1577 | 1578 | 1579 | 1580 | @manual{id-walton-add-paths, 1581 | title = { Advertisement of Multiple Paths in BGP}, 1582 | author = {D. Walton and others}, 1583 | organization = IETF, 1584 | month = nov, 1585 | year = 2002, 1586 | note = {\url{http://www.ietf.org/internet-drafts/draft-walton-bgp-add-paths-01.txt}}, 1587 | } 1588 | 1589 | @manual{id-yano-rtprx, 1590 | title = {RTP Profile for RTCP-based Retransmission Request for Unicast session}, 1591 | author = {Yano, K. and Podolsky, M. and McCanne, S.}, 1592 | organization = IETF, 1593 | month = jul, 1594 | year = 2000, 1595 | note = {\url{http://www.ietf.org/internet-drafts/draft-ietf-avt-rtprx-00.txt}}, 1596 | } 1597 | 1598 | @Manual{id-path-validation, 1599 | title = "{Considerations in Validating the Path in Routing Protocols}", 1600 | author = {Russ White and Nick Feamster}, 1601 | organization = {IETF}, 1602 | month = apr, 1603 | year = 2004, 1604 | note = {Internet Draft. Expires October 2004.}, 1605 | } 1606 | %% {\url{http://www.ietf.org/internet-drafts/draft-white-pathconsiderations-02.txt}. 1607 | 1608 | 1609 | @manual{id-hip-arch, 1610 | author = "R. Moskowitz and P. Nikander", 1611 | title = "Host Identity Protocol Architecture", 1612 | note = {draft-ietf-hip-base-06}, 1613 | organization = IETF, 1614 | year = 2006, 1615 | month = jun, 1616 | } 1617 | 1618 | @manual{id-eight, 1619 | author = "M. Ohta", 1620 | title = "8+8 Addressing for {IP}v6 End to End Multihoming", 1621 | note = {draft-ohta-multi6-8plus8-00 (Expired IETF Draft)}, 1622 | year = 2004, 1623 | month = jan, 1624 | } 1625 | 1626 | @manual{Kurtis03, 1627 | author = "K. Lindqvist", 1628 | title = "{Multihoming Road-map for IPv6}", 1629 | note = "draft-kurtis-multi6-roadmap-00 (Expired Internet Draft)", 1630 | month = feb, 1631 | year = 2003 1632 | } 1633 | %% howpublished = "{http://www.ietf.org/internet-drafts/draft-kurtis-multi6-roadmap-00.txt}" 1634 | 1635 | @manual{ bgpsecrec06, 1636 | author = "B. Christian and T. Tauber", 1637 | title = "{BGP} Security Requirements", 1638 | organization = IETF, 1639 | note = "Internet Draft: draft-ietf-rpsec-bgpsecrec-06.txt", 1640 | month = apr, 1641 | year = 2006, 1642 | } 1643 | 1644 | @manual{id-sixone, 1645 | author = "Christian Vogt", 1646 | title = "Six/One: A Solution for Routing and Addressing in IPv6", 1647 | organization = IETF, 1648 | month = nov, 1649 | year = 2007, 1650 | note = {\url{http://www.ietf.org/internet-drafts/draft-vogt-rrg-six-one-01.txt} Work in progress, expires May 22, 2008}, 1651 | } 1652 | 1653 | @manual{id-islay, 1654 | author = "Frank Kastenholz", 1655 | title = "{ISLAY}: A New Routing and Addressing Architecture", 1656 | organization = IETF, 1657 | month = may, 1658 | year = 2002, 1659 | note = {\url{http://ietfreport.isoc.org/idref/draft-irtf-routing-islay/}}, 1660 | } 1661 | 1662 | @manual{id-bfd, 1663 | author="Katz, D. and Ward, D.", 1664 | title="{Bidirectional Forwarding Detection}", 1665 | note = "{Internet Draft draft-ietf-bfd-base-08.txt; work in progress}", 1666 | organization=IETF, 1667 | month=mar, 1668 | year=2008, 1669 | } 1670 | 1671 | @manual{id-brpcp, 1672 | author="Vasseur, JP. and Zhang, R. and Bitar N. and Le Roux, JL.", 1673 | title="{A Backward Recursive PCE-based Computation (BRPC) Procedure To Compute Shortest Constrained Inter-domain Traffic Engineering Label Switched Paths}", 1674 | note = "{Internet Draft draft-ietf-pce-brpc-09.txt; work in progress}", 1675 | organization=IETF, 1676 | month=apr, 1677 | year=2008, 1678 | } 1679 | 1680 | 1681 | 1682 | @manual{ rfc4880, 1683 | author = "J. Callas and L. Donnerhacke and H. Finney and D. Shaw and R. Thayer", 1684 | title = "{OpenPGP} Message Format", 1685 | organization = IETF, 1686 | note = "{RFC} 4880", 1687 | month = nov, 1688 | year = 2007, 1689 | } 1690 | 1691 | @manual{rfc4893, 1692 | author = "Q. Vohra and E. Chen", 1693 | title = "{BGP} Support for Four-octet {AS} Number Space", 1694 | organization = IETF, 1695 | note = "{RFC} 4893", 1696 | month = may, 1697 | year = 2007 1698 | } 1699 | 1700 | @manual{rfc4984, 1701 | author= "David Meyer and Lixia Zhang and Kevin Fall", 1702 | title="Report from the {IAB} Workshop on Routing and Addressing", 1703 | note = "{RFC} 4984", 1704 | organization = IETF, 1705 | month=sep, 1706 | year=2007 1707 | } 1708 | 1709 | @manual{rfc5065, 1710 | author = "P. Traina and D. McPherson and J. Scudder", 1711 | title = "Autonomous System Confederations for {BGP}", 1712 | organization = IETF, 1713 | note = "{RFC} 5065", 1714 | month = aug, 1715 | year = 2007 1716 | } 1717 | 1718 | @manual{rfc3746, 1719 | author = "L. Yang and R. Dantu and T. Anderson and R. Gopal", 1720 | title = "Forwarding and Control Element Separation (ForCES) Framework", 1721 | organization = IETF, 1722 | note = "{RFC} 3746", 1723 | month = apr, 1724 | year = 2004 1725 | } 1726 | 1727 | @manual{rfc3022, 1728 | author = "P. Srisuresh and K. Egevang ", 1729 | title = "Forwarding and Control Element Separation (ForCES) Framework", 1730 | organization = IETF, 1731 | note = "{RFC} 3022", 1732 | month = jan, 1733 | year = 2001 1734 | } 1735 | 1736 | @manual{rfc1242, 1737 | author = "S. Bradner", 1738 | title = "Benchmarking Terminology for Network Interconnection Devices", 1739 | organization = IETF, 1740 | note = "{RFC} 1242", 1741 | month = jul, 1742 | year = 1991 1743 | } 1744 | 1745 | @manual{rfc3234, 1746 | author = "B. Carpenter", 1747 | title = "Middleboxes: Taxonomy and Issues", 1748 | organization = IETF, 1749 | note = "{RFC} 3234", 1750 | month = feb, 1751 | year = 2002 1752 | } 1753 | -------------------------------------------------------------------------------- /summary.tex: -------------------------------------------------------------------------------- 1 | \begin{center} 2 | {\large \bf \TITLE} 3 | \end{center} 4 | 5 | \fp {\bf Overview:} \\ 6 | 7 | \fp {\bf Intellectual merit:} \\ 8 | 9 | \fp {\bf Broader impacts:}\\ 10 | 11 | \fp {\bf Keywords:} Networking, Wired; Data Science, ML and AI 12 | -------------------------------------------------------------------------------- /synergistic.tex: -------------------------------------------------------------------------------- 1 | \begin{center} 2 | {\large \bf \TITLE} 3 | \end{center} 4 | 5 | \begin{center} 6 | {\bf Synergistic Activities} 7 | \end{center} 8 | 9 | \begin{enumerate} 10 | \itemsep=-1pt 11 | \item Policy Leadership: Feamster participates in leadership in technology policy 12 | that 13 | furthers the goals of research outcomes for society. Feamster works to ensure 14 | that the technical results of his research are known to policymakers through 15 | participation and leadership in many national policy organizations (e.g., 16 | Broadband Internet Technology Advisory Group). 17 | \item Conference Leadership: Feamster has founded several conferences that are 18 | synergistic with his research: He is the Founder of the USENIX Workshop on 19 | Free and Open Communication on the Internet (FOCI) and continues to help lead 20 | and organize this conference, which is now entering its 10th year. 21 | \item Online Education: Feamster has a strong track record integrating the 22 | results of 23 | his research with educational activities, especially online education. He 24 | conceived and developed the Coursera Software Defined Networking (SDN) 25 | Course, which had 50,000 enrollments in its first offering (May 2013) and has 26 | had more than 200,000 learners in total. The course is now offered in the 27 | University of Chicago Coursera offerings and is being expanded to include an 28 | additional module on machine learning for networking. 29 | \item Community Outreach: As part of efforts for industry outreach and to 30 | facilitate tech 31 | transfer of networking and security research, Feamster is a frequent presenter 32 | at 33 | many conferences that bridge the gap between research and practice. For 34 | example, Feamster is a regular contributor to the Internet Engineering Task 35 | Force (IETF), as an author of Internet drafts. 36 | \item Interdisciplinary Leadership: Feamster is research director of the at the 37 | Data 38 | Science Institute, and the director of the Internet Equity Inititative. 39 | Through this 40 | leadership, he engages with a variety of on-campus units. In this role, he 41 | helps 42 | transfer research to practice, through both entrepreneurship activities and 43 | civic 44 | engagement. 45 | \end{enumerate} 46 | --------------------------------------------------------------------------------