File: rfc148.txt

package info (click to toggle)
doc-rfc 20181229-2
  • links: PTS, VCS
  • area: non-free
  • in suites: buster
  • size: 570,944 kB
  • sloc: xml: 285,646; sh: 107; python: 90; perl: 42; makefile: 14
file content (59 lines) | stat: -rw-r--r-- 1,149 bytes parent folder | download | duplicates (5)
1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
31
32
33
34
35
36
37
38
39
40
41
42
43
44
45
46
47
48
49
50
51
52
53
54
55
56
57
58
59






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   ]



















                                                                [Page 1]