(Status: UNKNOWN) (DOI: 10.17487/RFC0037)
0038 Comments on Network Protocol from NWG/RFC #36. S.M. Wolfe.... (Status: UNKNOWN) (DOI: 10.17487/RFC0038)
0039 Comments on Protocol Re: NWG/RFC #36. E. Harslem, J.F. Hea... UNKNOWN)
(DOI: 10.17487/RFC0039)
0040 More Comments on the Forthcoming Protocol. E. Harslem, J.F. Hea... (Status: UNKNOWN) (DOI: 10.17487/RFC0043)
0044 Comments on NWG/RFC 33 and 36. A. Shoshani, R. Long, A. La
rg/info/rfc37>.
RFC0038 | | Wolfe, S., "Comments on Network Protocol from NWG/RFC #36", RFC 38, DO... FC0039 | | Harslem, E. and J. Heafner, "Comments on Protocol Re: NWG/RFC #36", RFC 39, DOI 10.1748... 0 | | Harslem, E. and J. Heafner, "More Comments on the Forthcoming Protocol", RFC 40, DOI 10.1748... | Shoshani, A., Long, R., and A. Landsberg, "Comments on NWG/RFC 33 and 36", RFC 44, DOI 10.17487/RFC00
July 1977. (Format: TXT =248 HTML= bytes)
0002 Comments on Internet Protocols and TCP. Postel. August 197... 1978. (Format:
TXT =20801 HTML= bytes)
0049 Comments on the Proposed TCP Checksum Scheme. Higginson. J... 1979.
0079 A Protocol Test Facility: Request for Comments. Lozano-Perez.
January 1979.
0080 Internet ... 1981.
(Format: TXT =35180 HTML= bytes)
0177 Comments on Action Items from the January Meeting. Postel.
E. Rescorla
Request for Comments: 3552 RTFM, In... that
document (with new section numbers). Our comments are indented and
prefaced with 'NOTE:'. We al... om that document (with new section numbers). Our comments
are indented and prefaced with 'NOTE:'.
6.2.1... r primary source for this document is specific
comments received from Steve Bellovin. Early review of th
TF) M. Kucherawy, Ed.
Request for Comments: 8713 ... The call for nominees must include a request for comments regarding
the past performance of incumbents, ... TF) M. Duke
Request for Comments: 9389 Google L