Tech-invite3GPPspaceIETFspace
96959493929190898887868584838281807978777675747372717069686766656463626160595857565554535251504948474645444342414039383736353433323130292827262524232221201918171615141312111009080706050403020100
in Index   Prev   Next

RFC 0148

Comments on RFC 123

Pages: 1
Unclassified
Updates:  0123

ToP   noToC   RFC0148 - Page 1
Network Working Group                             A. Bhushan
Request for Comments # 148                MIT -- Project MAC
NIC # 6751                                        7 May 1971
Categories: D.1


                          Comments on RFC #123
                          --------------------
	


        The requirement that byte size 's' be 32-bits for
the initial connection imposes some severe strains on some of
the 36-bit machines. For example, in our PDP-10 (DMCG-
ITS) NCP, we have at present no way of sending or receiving
exactly 32-bits of data. Data is transmitted either in
image mode (36-bit bytes) or in ASCII mode (8-bit characters
with the 8th bit as zero). Perhaps we should permit the
server to send more than 32-bits (say 72-bits) where the
remaining bits could be NULL fillers. The byte size
's' for the connection may be fixed at 8-bits.








  [ This RFC was put into machine readable form for entry ]
  [ into the online RFC archives by BBN Corp. under the   ]
  [ direction of Alex McKenzie.                   12/96   ]