symmetric key- 128bit
asymmetric key-1096 minimum size..
disadvantage of asymmetric key is longer time to encrypt..
hashfunction used in digital signature forauthentication..
hash is one way.. cant be decoded so nt used for encryption..
-----------------------------------------------------------------------
ssl..protocol- process.. symmetric and asymmetric used together..
------------------------------------------------------------------------
computer networks and internet:
1.OSI
2.TCP/IP
3.Each layer and there protocol, use.
4.Routing algorithms.
5.Packet header,packet data-hex format.
6.IP addressing,classes,non routable ip addresses..eg:192.168...
7.ARP..link between ip and mac address
8.Subnet,ip subnetting,subnet calculation..
DNS:
classless ip addressing
supernetting
NAT- network address translation protocol
NAT-static/dynamic mapping..
PAT-port address translation/
DNS->uses UDP
uses of UDP
DNS Zones:
authorative/iterative..
Resource REcords(RR)-types
dnsstuff.com
SOA field in dns record.
MX records..
DNS packet..
DNS cache poisoning- avoid by random query id and using pik
5.3.10
RR
Common DNS RR types-record in the dns
RR type value 1
:text code A
RR type-address
contains ip addressess
Type2
gives details of name server
text code NS
its gives infor authorative server
the ip addres of dns is also given
RR type 5
Text code Cname or canonical name node name
it masks changes from outside users
RR type value 6
Text code SOA
Start of authority
Provides info in detail of that zone
RR type 12
PTR
pointer
Reverse domain mapping
IP address is mapped to domain name
RR type 15
MX
Mail exchange
Specifies name of device responsible for handling emails sent to the domain
RR type 16
TXT
gives additonal text of domain to be stored
------------------------------------------------------------------------
Zone transfer
updates are dont at primar dns
and the secondary dns roll back and looksup in primary
checking condition is done when serial no in primary changes
---------------------------------------------------------------------
recursive and iterative resolution
-------------------------------------------------------------
RR type value 1
:text code A
RR type-address
contains ip addressess
Type2
gives details of name server
text code NS
its gives infor authorative server
the ip addres of dns is also given
RR type 5
Text code Cname or canonical name node name
it masks changes from outside users
RR type value 6
Text code SOA
Start of authority
Provides info in detail of that zone
RR type 12
PTR
pointer
Reverse domain mapping
IP address is mapped to domain name
RR type 15
MX
Mail exchange
Specifies name of device responsible for handling emails sent to the domain
RR type 16
TXT
gives additonal text of domain to be stored
------------------------------------------------------------------------
Zone transfer
updates are dont at primar dns
and the secondary dns roll back and looksup in primary
checking condition is done when serial no in primary changes
---------------------------------------------------------------------
recursive and iterative resolution
-------------------------------------------------------------
24.10.09
class ids
My Computer: {20D04FE0-3AEA-1069-A2D8-08002B30309D}
Recycle Bin: {645FF040-5081-101B-9F08-00AA002F954E}
Control Panel: {21EC2020-3AEA-1069-A2DD-08002B30309D}
Printers: {2227A280-3AEA-1069-A2DE-08002B30309D}
Internet Explorer: {871C5380-42A0-1069-A2EA-08002B30309D}
Network Neighborhood: {208D2C60-3AEA-1069-A2D7-08002B30309D}
Subscriptions: {F5175861-2688-11d0-9C5E-00AA00A45957}
ActiveX Cache Folder: {88C6C381-2E85-11D0-94DE-444553540000}
.{20D04FE0-3AEA-1069-A2D8-08002B30309D} (= My Computer)
.{450D8FBA-AD25-11D0-98A8-0800361B1103} (= My Documents)
.{208D2C60-3AEA-1069-A2D7-08002B30309D} (= My Network Places)
.{645FF040-5081-101B-9F08-00AA002F954E} (= Recycle Bin)
.{871C5380-42A0-1069-A2EA-08002B30309D} (= Internet Explorer)
.{21EC2020-3AEA-1069-A2DD-08002B30309D} (= Control Panel)
.{D20EA4E1-3957-11D2-A40B-0C5020524153} (= Administrative Tools)
.{00020D75-0000-0000-C000-000000000046} (= Inbox)
.{D20EA4E1-3957-11D2-A40B-0C5020524152} (= Fonts)
.{7007ACC7-3202-11D1-AAD2-00805FC1270E} (= Network Connections)
.{2227A280-3AEA-1069-A2DE-08002B30309D} (= Printers and Faxes)
.{7BE9D83C-A729-4D97-b5A7-1B7313C39E0A} (= Programs Folder)
.{E211B736-43FD-11D1-9EFB-0000F8757FCD} (= Scanners and Cameras)
.{D6277990-4C6A-11CF-8D87-00AA0060F5BF} (= Scheduled Tasks)
.{48E7CAAB-B918-4E58-A94D-505519C795DC} (= Start Menu Folder)
.{7BD29E00-76C1-11CF-9DD0-00A0C9034933} (= Temporary Internet Files)
.{BDEADF00-C265-11d0-BCED-00A0C90AB50F} (= Web Folders)
.{6DFD7C5C-2451-11D3-A299-00C04F8EF6AF} (= Folder Options)
.{00020801-0000-0000-C000-000000000046} (= Folder)
.{00021400-0000-0000-C000-000000000046} (= Another Folder)
Recycle Bin: {645FF040-5081-101B-9F08-00AA002F954E}
Control Panel: {21EC2020-3AEA-1069-A2DD-08002B30309D}
Printers: {2227A280-3AEA-1069-A2DE-08002B30309D}
Internet Explorer: {871C5380-42A0-1069-A2EA-08002B30309D}
Network Neighborhood: {208D2C60-3AEA-1069-A2D7-08002B30309D}
Subscriptions: {F5175861-2688-11d0-9C5E-00AA00A45957}
ActiveX Cache Folder: {88C6C381-2E85-11D0-94DE-444553540000}
.{20D04FE0-3AEA-1069-A2D8-08002B30309D} (= My Computer)
.{450D8FBA-AD25-11D0-98A8-0800361B1103} (= My Documents)
.{208D2C60-3AEA-1069-A2D7-08002B30309D} (= My Network Places)
.{645FF040-5081-101B-9F08-00AA002F954E} (= Recycle Bin)
.{871C5380-42A0-1069-A2EA-08002B30309D} (= Internet Explorer)
.{21EC2020-3AEA-1069-A2DD-08002B30309D} (= Control Panel)
.{D20EA4E1-3957-11D2-A40B-0C5020524153} (= Administrative Tools)
.{00020D75-0000-0000-C000-000000000046} (= Inbox)
.{D20EA4E1-3957-11D2-A40B-0C5020524152} (= Fonts)
.{7007ACC7-3202-11D1-AAD2-00805FC1270E} (= Network Connections)
.{2227A280-3AEA-1069-A2DE-08002B30309D} (= Printers and Faxes)
.{7BE9D83C-A729-4D97-b5A7-1B7313C39E0A} (= Programs Folder)
.{E211B736-43FD-11D1-9EFB-0000F8757FCD} (= Scanners and Cameras)
.{D6277990-4C6A-11CF-8D87-00AA0060F5BF} (= Scheduled Tasks)
.{48E7CAAB-B918-4E58-A94D-505519C795DC} (= Start Menu Folder)
.{7BD29E00-76C1-11CF-9DD0-00A0C9034933} (= Temporary Internet Files)
.{BDEADF00-C265-11d0-BCED-00A0C90AB50F} (= Web Folders)
.{6DFD7C5C-2451-11D3-A299-00C04F8EF6AF} (= Folder Options)
.{00020801-0000-0000-C000-000000000046} (= Folder)
.{00021400-0000-0000-C000-000000000046} (= Another Folder)
ftp codes...
400
Cannot resolve the request.
401.x
Unauthorized.
403.x
Forbidden.
404.x
File or directory not found.
405
HTTP verb used to access this page is not allowed.
406
Client browser does not accept the MIME type of the requested page.
407
Initial proxy authentication required by the Web server.
412
Precondition set by the client failed when evaluated on the Web server.
413
Request entity too large.
414
Request URL is too large and therefore unacceptable on the Web server.
415
Unsupported media type.
416
Requested range not satisfiable.
417
Expectation failed.
423
Locked error.
Cannot resolve the request.
401.x
Unauthorized.
403.x
Forbidden.
404.x
File or directory not found.
405
HTTP verb used to access this page is not allowed.
406
Client browser does not accept the MIME type of the requested page.
407
Initial proxy authentication required by the Web server.
412
Precondition set by the client failed when evaluated on the Web server.
413
Request entity too large.
414
Request URL is too large and therefore unacceptable on the Web server.
415
Unsupported media type.
416
Requested range not satisfiable.
417
Expectation failed.
423
Locked error.
17.10.09
revision
firefox tools
---------------------------------
whois searches
-------------------------------
domain names
------------------------------
iptools.com
whois.sc
----------------------------
server logs
---------------------------
winhex
1.hash values
2.md5-32bit
3.sha1
4.view-show-tab control(opens in tabs)
5.text display only
6.specialist--- interpret image file as disk
7.save ram image
8.search---find text, simultaneous search,
9.recovering deleted files
10.splitting and joining of image files
------------------------------------------------------------------
DT-search(Indexing and searching tool)
searching options
------------------------------------------------------------------
x-ways(used for browser log file analysis)
1.internet- index.dat
.mozilla-history.dat
opera-dcache4.url
search for all browsers
-----------------------------------------------------------------
password breaking tools
1.after getting password, check if file opens.... then submit answer.
self decrypting archive--- SDA------recovery with edpr
edpr--install the server
then install agent
and connect both
2.Encrypt Analyser--searches password protected files
--------------------------------------------------------------------------------------------------------------------
spammimic
------------------------------
Snow
snow -C (compress) -m "message" -p "password" sourcefile destinationfile
unhide
snow -C -p "password" file (-c is optional)
---------------------------------------------------------------------------------------------------------------------
stools
works only for gif,bmp,wav files
-------------------------------
camoflague
------------------------------
steganos
-----------------------------
try truecrypt.org
-----------------------------
21.8.09
IP addressing and gaining IP's
The intent of this paper is to document the background
behind the current IP address assignments which I have offered to
coordinate. The proposed scheme has been reviewed by Phil Karn,
Bdale Garbee and (verbally with) Mike Chepponis, all of whom have
encouraged that it be used.
Phil's code does NOT currently support the subnetwork
aspects of the scheme but will do so in the future. There is no
real reason for any national coordination of these addresses
until actual networks or at least geographically coordinated
groups of experimenters are formed.
I have offered to issue and keep track of SUBNET addresses
and their "owners" who are presumably responsible *NETWORK*
implementors and managers.
The basic premise behind the proposed plan is that amateur
radio networks will be politically defined. The plan is based
upon the presumption that current voice networks serve as a
proper analog by which to predict general characteristics of the
as yet unconstructed digital networks. Political entities will
build networks; funded, controlled, maintained and used primarily
by their own members and guests.
Each of these separately managed networks should be viewed
as a subnetwork of AMPRNET (with the idea being to somehow
rationally partition the 044.xxx.xxx.xxx AMPRNET address space).
Each subnetwork within AMPRNET will maintain routing tables for
its own constituents. Each will provide its own hosts (TACs,
Gateways, i.e. the mechanism by which users with simple terminals
and AX25 level 2 boxes will access network resources), switches,
rules (network administration), security measures and quite
possibly its own link level protocols.
The natural limitations on span of control will probably
limit the service area of each of these networks. This is
another factor leading to the partitioning of the AMPRNET address
space with respect to separate subnetworks.
This partitioning of the address space will allow for
much simplified routing tables in each host. Internetworking
gateways will connect these independently controlled subnetworks.
Each gateway will maintain routing tables only for local hosts
and for gateways to other networks. Hosts and relay switches on
a given subnet will need to maintain routing information
regarding only members of that subnet and gateways to other
networks. The required routing tables should prove to be very
manageable and make any kind of geographically based hueristic
addressing schemes such as ZIP codes, area codes etc. moot.
1.
I would also like to propose that we coordinate logical
network names and their corresponding addresses based on these
political network subdivisions. The concept of a naming
convention which maps directly into an IP address is purely for
the convenience of network developers and is not considered
necessary. There is, however, some good reasoning behind making
network and host names hierarchical and meaningful to end users.
It will considerably aid in bootstrapping the initial networks
and in being comprehensible to the non-network folks who will be
the primary users of these networks. The naming convention
proposed is of the form USERID@HOST.SUBNET[.AMPRNET.RES].
WESTNET, SBARCnet (Santa Barbara ARC) and GFRN-net represent
three hypothetical networks with which this writer could be
involved, perhaps as a provider of gateway and/or host services.
Each of these subnetwork entities could have a distinct
address and perhaps several internally administered host/user
addresses.
[NOTE: Throughout this paper, Host or Host/User represents
any host or any user running IP protocols that has direct
network access. Also, for the purposes of the following
example, WA6JPR is not a network address, rather it
represents a user-id on a local host. It is the writer's
opinion that the majority of packet users for the forseeable
future will be using simple TNCs connected to hosts via
AX.25 level 2 protocols.]
WA6JPR may be "a user" on hosts on more than one network
such that a station in Washington D.C.,logged onto an AMPRNET
host, may send internet traffic successfully to
WA6JPR@JPRHOST.WESTNET (this traffic would be routed to Westnet
via various AMPRNET gateways and subnetwork level relays and then
to a Santa Barbara host known internally by Westnet to be
reachable via the W6AMT-2 switch). Traffic could also be
directed to Wally@SBARC (presuming that the Santa Barbara
Amateur Radio Club maintains a message server host gatewayed to
the AMPRNET catenet).
Based upon the presumption of the AMPRNET/SUBNET/HOST
hierarchy, it would seem that we could easily decide how to
allocate the 044.xxx.xxx.xxx 24 bit IP address field such that
there are bits allocated for a sufficient number of individually
managed subnetworks while leaving a correspondingly adequate
number of assignable bits for the internal addressing needs of
each individual subnetwork.
Accordingly, the following is proposed as an initial
addressing scheme and methodology for address assignment. [Bit
numbering is per RFC-960 Pg.2]
2
Bit 8 to be 0 for USA stations and 1 for non-USA stations.
[Note. This is not meant to imply a geographic basis for
assignments. It is meant to provide a very quick means for
segregating FCC controlled participants from non-FCC stations.]
Bits 9 - 18 to represent politically separate subnetworks within
AMPRNET. These bits are to be assigned in an inverse binary
sequence (see example below) beginning with the *MOST
SIGNIFICANT* bit first.
Bits 19 - 23 to be unassigned and reserved for future allocation
as network addresses, to network administrations for internally
assigned host and/or user addresses, to a combination of the
above or to a completely new intermediate class of addresses.
Bits 24 - 31 to be used within politically separate AMPRNET
subnetworks for individual hosts, switches, workstations etc. as
determined by local network administration. It would be
recommended that these bits be assigned in binary sequence with
the *LEAST SIGNIFICANT* bits being assigned first.
The resulting network addresses would be as follows:
AMPRNET
||
|| SUBNET----+
|| | |
|| | | HOST--+
|| | | | |
44:0...127:000:0...255------- 32,768 addresses assignable
44:0...127:001:0...255--+
| +- 1,015,808 addresses reserved
44:0...127:031:0...255--+
44:0...127:032:0...255------- 32,768 addresses assignable
44:0...127:033:0...255--+
| +- 1,015,808 addresses reserved
44:0...127:063:0...255--+
44:0...127:064:0...255------- 32,768 addresses assignable
44:0...127:065:0...255--+
| +- 1,015,808 addresses reserved
44:0...127:095:0...255--+
44:0...127:096:0...255------- 32,768 addresses assignable
44:0...127:097:0...255--+
| +- 1,015,808 addresses reserved
44:0...127:127:0...255--+
44:0...127:128:0...255------- 32,768 addresses assignable
44:0...127:129:0...255--+
| +- 1,015,808 addresses reserved
44:0...127:159:0...255--+
44:0...127:160:0...255------- 32,768 addresses assignable
44:0...127:161:0...255--+
| +- 1,015,808 addresses reserved
44:0...127:191:0...255--+
44:0...127:192:0...255------- 32,768 addresses assignable
3
44:0...127:193:0...255--+
| +- 1,015,808 addresses reserved
44:0...127:223:0...255--+
44:0...127:224:0...255------- 32,768 addresses assignable
44:0...127:225:0...255--+
| +- 1,015,808 addresses reserved
44:0...127:255:0...255--+
44:128:xxx:xxx----------+
| +- 8,388,608 addresses assignable (non USA)
44:255:xxx:xxx----------+
The above allocation and assignment scheme allows network
(subnet) and intranet (host/user) addresses to begin to be
immediately assigned to experimenters while retaining the largest
possible contiguous block of unassigned bits whose assignments
can be defined in the future with little or no impact on
previously allocated addresses. The USER @ HOSTNAME .
SUBNET/ADMINISTRATION naming scheme represents a human-friendly
network naming convention which maps easily into numerical
network addresses. I believe that the above approach is in
general conformance with the requirements of RFC-950, "Internet
Standard Subnetting Procedure."
The numbering scheme as initially proposed allows for up to
1024 AMPRNET subnetworks of up to 256 hosts in the USA while
retaining five bits for future expansion. That's 262,144
individual AMPRNET addressable entities. If the proposed method
of address assignment is followed and we run out of Host/User
addresses before we run out of network addresses, we can simply
pick up the least significant reserved bit and assign more
Host/User addresses. Conversely, if network addresses are more
popular we could easily expand by taking the most significant
reserved bit and allocating it for network addressing.
If it should become clear that every user on a network needs his
or her own IP address, each network could allocate user blocks in
256 user increments from the least significant reserved bits.
Possible combinations are 1024 networks each with up to 8192
individually addressable units or 2048 networks each with 4096
hosts/users (8,388,608 individually addressable entities).
The writer presumes that 8 million plus addresses ought to
last the US amateur population for some time to come. All we need
to do to avoid painting ourselves in a corner is to assign them
in a logical sequence rather than randomly.
4
The following table serves as an example of the "high bit
first" network address assignment table and some actual and
requested initial networking assignments.
"this" 44.000.000.xxx ;special case
KARNnet 44.064.000.xxx ;network admin: KA9Q
BDALEnet 44.032.000.xxx ;network admin: N3EUA
DCnet1 44.096.000.xxx ;network admin: WB6RQN
SOCALnet1 44.016.000.xxx ;network admin: WB5EKU
DCnet2 44.080.000.xxx ;network admin: WB6RQN
SOCALnet2 44.048.000.xxx ;network admin: WA6JPR
PITTNET 44.112.000.xxx ;network admin: N3CVL
next 44.008.000.xxx
next 44.072.000.xxx
.
.
.
last 44.063.000.xxx
"all" 44.127.000.xxx ;special case
behind the current IP address assignments which I have offered to
coordinate. The proposed scheme has been reviewed by Phil Karn,
Bdale Garbee and (verbally with) Mike Chepponis, all of whom have
encouraged that it be used.
Phil's code does NOT currently support the subnetwork
aspects of the scheme but will do so in the future. There is no
real reason for any national coordination of these addresses
until actual networks or at least geographically coordinated
groups of experimenters are formed.
I have offered to issue and keep track of SUBNET addresses
and their "owners" who are presumably responsible *NETWORK*
implementors and managers.
The basic premise behind the proposed plan is that amateur
radio networks will be politically defined. The plan is based
upon the presumption that current voice networks serve as a
proper analog by which to predict general characteristics of the
as yet unconstructed digital networks. Political entities will
build networks; funded, controlled, maintained and used primarily
by their own members and guests.
Each of these separately managed networks should be viewed
as a subnetwork of AMPRNET (with the idea being to somehow
rationally partition the 044.xxx.xxx.xxx AMPRNET address space).
Each subnetwork within AMPRNET will maintain routing tables for
its own constituents. Each will provide its own hosts (TACs,
Gateways, i.e. the mechanism by which users with simple terminals
and AX25 level 2 boxes will access network resources), switches,
rules (network administration), security measures and quite
possibly its own link level protocols.
The natural limitations on span of control will probably
limit the service area of each of these networks. This is
another factor leading to the partitioning of the AMPRNET address
space with respect to separate subnetworks.
This partitioning of the address space will allow for
much simplified routing tables in each host. Internetworking
gateways will connect these independently controlled subnetworks.
Each gateway will maintain routing tables only for local hosts
and for gateways to other networks. Hosts and relay switches on
a given subnet will need to maintain routing information
regarding only members of that subnet and gateways to other
networks. The required routing tables should prove to be very
manageable and make any kind of geographically based hueristic
addressing schemes such as ZIP codes, area codes etc. moot.
1.
I would also like to propose that we coordinate logical
network names and their corresponding addresses based on these
political network subdivisions. The concept of a naming
convention which maps directly into an IP address is purely for
the convenience of network developers and is not considered
necessary. There is, however, some good reasoning behind making
network and host names hierarchical and meaningful to end users.
It will considerably aid in bootstrapping the initial networks
and in being comprehensible to the non-network folks who will be
the primary users of these networks. The naming convention
proposed is of the form USERID@HOST.SUBNET[.AMPRNET.RES].
WESTNET, SBARCnet (Santa Barbara ARC) and GFRN-net represent
three hypothetical networks with which this writer could be
involved, perhaps as a provider of gateway and/or host services.
Each of these subnetwork entities could have a distinct
address and perhaps several internally administered host/user
addresses.
[NOTE: Throughout this paper, Host or Host/User represents
any host or any user running IP protocols that has direct
network access. Also, for the purposes of the following
example, WA6JPR is not a network address, rather it
represents a user-id on a local host. It is the writer's
opinion that the majority of packet users for the forseeable
future will be using simple TNCs connected to hosts via
AX.25 level 2 protocols.]
WA6JPR may be "a user" on hosts on more than one network
such that a station in Washington D.C.,logged onto an AMPRNET
host, may send internet traffic successfully to
WA6JPR@JPRHOST.WESTNET (this traffic would be routed to Westnet
via various AMPRNET gateways and subnetwork level relays and then
to a Santa Barbara host known internally by Westnet to be
reachable via the W6AMT-2 switch). Traffic could also be
directed to Wally@SBARC (presuming that the Santa Barbara
Amateur Radio Club maintains a message server host gatewayed to
the AMPRNET catenet).
Based upon the presumption of the AMPRNET/SUBNET/HOST
hierarchy, it would seem that we could easily decide how to
allocate the 044.xxx.xxx.xxx 24 bit IP address field such that
there are bits allocated for a sufficient number of individually
managed subnetworks while leaving a correspondingly adequate
number of assignable bits for the internal addressing needs of
each individual subnetwork.
Accordingly, the following is proposed as an initial
addressing scheme and methodology for address assignment. [Bit
numbering is per RFC-960 Pg.2]
2
Bit 8 to be 0 for USA stations and 1 for non-USA stations.
[Note. This is not meant to imply a geographic basis for
assignments. It is meant to provide a very quick means for
segregating FCC controlled participants from non-FCC stations.]
Bits 9 - 18 to represent politically separate subnetworks within
AMPRNET. These bits are to be assigned in an inverse binary
sequence (see example below) beginning with the *MOST
SIGNIFICANT* bit first.
Bits 19 - 23 to be unassigned and reserved for future allocation
as network addresses, to network administrations for internally
assigned host and/or user addresses, to a combination of the
above or to a completely new intermediate class of addresses.
Bits 24 - 31 to be used within politically separate AMPRNET
subnetworks for individual hosts, switches, workstations etc. as
determined by local network administration. It would be
recommended that these bits be assigned in binary sequence with
the *LEAST SIGNIFICANT* bits being assigned first.
The resulting network addresses would be as follows:
AMPRNET
||
|| SUBNET----+
|| | |
|| | | HOST--+
|| | | | |
44:0...127:000:0...255------- 32,768 addresses assignable
44:0...127:001:0...255--+
| +- 1,015,808 addresses reserved
44:0...127:031:0...255--+
44:0...127:032:0...255------- 32,768 addresses assignable
44:0...127:033:0...255--+
| +- 1,015,808 addresses reserved
44:0...127:063:0...255--+
44:0...127:064:0...255------- 32,768 addresses assignable
44:0...127:065:0...255--+
| +- 1,015,808 addresses reserved
44:0...127:095:0...255--+
44:0...127:096:0...255------- 32,768 addresses assignable
44:0...127:097:0...255--+
| +- 1,015,808 addresses reserved
44:0...127:127:0...255--+
44:0...127:128:0...255------- 32,768 addresses assignable
44:0...127:129:0...255--+
| +- 1,015,808 addresses reserved
44:0...127:159:0...255--+
44:0...127:160:0...255------- 32,768 addresses assignable
44:0...127:161:0...255--+
| +- 1,015,808 addresses reserved
44:0...127:191:0...255--+
44:0...127:192:0...255------- 32,768 addresses assignable
3
44:0...127:193:0...255--+
| +- 1,015,808 addresses reserved
44:0...127:223:0...255--+
44:0...127:224:0...255------- 32,768 addresses assignable
44:0...127:225:0...255--+
| +- 1,015,808 addresses reserved
44:0...127:255:0...255--+
44:128:xxx:xxx----------+
| +- 8,388,608 addresses assignable (non USA)
44:255:xxx:xxx----------+
The above allocation and assignment scheme allows network
(subnet) and intranet (host/user) addresses to begin to be
immediately assigned to experimenters while retaining the largest
possible contiguous block of unassigned bits whose assignments
can be defined in the future with little or no impact on
previously allocated addresses. The USER @ HOSTNAME .
SUBNET/ADMINISTRATION naming scheme represents a human-friendly
network naming convention which maps easily into numerical
network addresses. I believe that the above approach is in
general conformance with the requirements of RFC-950, "Internet
Standard Subnetting Procedure."
The numbering scheme as initially proposed allows for up to
1024 AMPRNET subnetworks of up to 256 hosts in the USA while
retaining five bits for future expansion. That's 262,144
individual AMPRNET addressable entities. If the proposed method
of address assignment is followed and we run out of Host/User
addresses before we run out of network addresses, we can simply
pick up the least significant reserved bit and assign more
Host/User addresses. Conversely, if network addresses are more
popular we could easily expand by taking the most significant
reserved bit and allocating it for network addressing.
If it should become clear that every user on a network needs his
or her own IP address, each network could allocate user blocks in
256 user increments from the least significant reserved bits.
Possible combinations are 1024 networks each with up to 8192
individually addressable units or 2048 networks each with 4096
hosts/users (8,388,608 individually addressable entities).
The writer presumes that 8 million plus addresses ought to
last the US amateur population for some time to come. All we need
to do to avoid painting ourselves in a corner is to assign them
in a logical sequence rather than randomly.
4
The following table serves as an example of the "high bit
first" network address assignment table and some actual and
requested initial networking assignments.
"this" 44.000.000.xxx ;special case
KARNnet 44.064.000.xxx ;network admin: KA9Q
BDALEnet 44.032.000.xxx ;network admin: N3EUA
DCnet1 44.096.000.xxx ;network admin: WB6RQN
SOCALnet1 44.016.000.xxx ;network admin: WB5EKU
DCnet2 44.080.000.xxx ;network admin: WB6RQN
SOCALnet2 44.048.000.xxx ;network admin: WA6JPR
PITTNET 44.112.000.xxx ;network admin: N3CVL
next 44.008.000.xxx
next 44.072.000.xxx
.
.
.
last 44.063.000.xxx
"all" 44.127.000.xxx ;special case
Subscribe to:
Comments (Atom)