Na základe vzťahov možno definovať pravdepodobnosť doručenia správy v čase t  t 0
Ide zrejme o určenie maximálneho počtu retransmisií a následne o súčet pravdepodobnosti pre
prípady žiadnej, jednej, dvoch až x retransmisií. Matematicky vyjadrené:
 B  i  1 i
  q  1  q B1
Pd t  t0     1
i
i 0 

x
Po dosadení a úprave dostaneme:
 B2  B1  S  1

s 1


, kde x  
mRb 1  Pb 
D
m  r  n1  Rb t p
m r
Štýly
A1 – Kodčík (alt+p)
A2 – Kodčík (alt+o)
A3 – Kodčík (alt+i)
A1
A1This memo is a
status report on the
parameters (i.e.,
numbers and
keywords) used in
protocols in the
Internet community.
Distribution
of this memo is
unlimited.
A2
We expect that various readers will notice specific items that
should be
corrected. Please send any specific corrections via email to
<iana@isi.edu>.
A3
Network Working Group
Request for Comments: 1700
J. Reynolds
J. Postel
STD: 2
Obsoletes RFCs: 1340, 1060, 1010, 990, 960,
943, 923, 900, 870, 820, 790, 776, 770,
762, 758,755, 750, 739, 604, 503, 433, 349
Obsoletes IENs: 127, 117, 93
Category: Standards Track
ASSIGNED NUMBERS
Status of this Memo
This memo is a
status report on the
parameters (i.e.,
numbers and
keywords) used in
protocols in the
Internet community.
Distribution
ISI
October 1994
of this memo is
unlimited.
This RFC is a snapshot of the ongoing process of the assignment of
protocol parameters for the Internet protocol suite. To make the
current information readily available the assignments are kept uptodate in a set of online text files. This RFC has been assembled
by
catinating these files together with a minimum of formatting
"glue".
OVERVIEW
The authors appologize for the somewhat rougher formatting and style
than is typical of most RFCs.
We expect that various readers will notice specific items that should be
corrected. Please send any specific corrections via email to
<iana@isi.edu>.
Reynolds & Postel
RFC 1700
[Page 1]
Assigned Numbers
October 1994
INTRODUCTION
The files in this
directory document the
currently assigned
values for
several series of
numbers used in network
protocol
implementations.
ftp://ftp.isi.edu/in-notes/iana/assignments
The Internet Assigned Numbers Authority (IANA) is the central
coordinator for the assignment of unique parameter values for
Internet
protocols. The IANA is chartered by the Internet Society (ISOC)
and
the Federal Network Council (FNC) to act as the clearinghouse to
assign and coordinate the use of numerous Internet protocol
parameters.
The Internet protocol suite, as defined by the Internet Engineering
Task Force (IETF) and its steering group (the IESG), contains numerous
parameters, such as internet addresses, domain names, autonomous
system numbers (used in some routing protocols), protocol numbers,
port numbers, management information base object identifiers,
including private enterprise numbers, and many others.
The common use of the
Internet protocols by
the Internet community
requires that the particular values used in these parameter fields be
assigned uniquely. It
is the task of the IANA
to make those unique
assignments as
requested and to
maintain a registry of
the currently
assigned values.
Requests for parameter assignments (protocols, ports, etc.) should be
sent to <iana@isi.edu>.
Requests for SNMP network management private enterprise number
assignments should be sent to <iana-mib@isi.edu>.
The IANA is located at
and operated by the
Information Sciences
Institute (ISI) of the
University of Southern
California (USC).
If you are developing a
protocol or application
that will require the
use of a link, socket,
port, protocol, etc.,
please contact the IANA
to receive a number
assignment.
Joyce K. Reynolds
Internet Assigned Numbers Authority
USC - Information Sciences Institute
4676 Admiralty Way
Marina del Rey, California 90292-6695
Electronic mail: IANA@ISI.EDU
Phone: +1 310-822-1511
Reynolds & Postel
[Page 2]
RFC 1700
Assigned Numbers
October 1994
Most of the protocols are documented in the RFC series of notes.
Some
of the items listed are undocumented. Further information on
protocols can be found in the memo, "Internet Official Protocol
Standards" (STD 1).
Data Notations
The convention in the documentation of Internet Protocols is to
express numbers in decimal and to picture data in "big-endian"
order
[COHEN]. That is, fields are described left to right, with the
most
significant octet on the left and the least significant octet on
the
right.
The order of transmission of the header and data described in this
document is resolved to the octet level. Whenever a diagram shows a
group of octets, the order of transmission of those octets is the
normal order in which they are read in English. For example, in the
following diagram the octets are transmitted in the order they are
numbered.
0
1
2
3
0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
|
1
|
2
|
3
|
4
|
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
|
5
|
6
|
7
|
8
|
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
|
9
|
10
|
11
|
12
|
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
Transmission Order of Bytes
Whenever an octet
represents a numeric
quantity the left most
bit in the
diagram is the high
order or most
significant bit. That
is, the bit
labeled 0 is the most
significant bit. For
example, the following
diagram represents the
value 170 (decimal).
0 1 2 3 4 5 6 7
+-+-+-+-+-+-+-+-+
|1 0 1 0 1 0 1 0|
+-+-+-+-+-+-+-+-+
Significance of Bits
Similarly, whenever a multi-octet field represents a numeric
quantity
the left most bit of the whole field is the most significant bit.
When
Reynolds & Postel
[Page 3]
RFC 1700
Assigned Numbers
October 1994
a multi-octet quantity is transmitted the most significant octet is
transmitted first.
Special Addresses
There are five classes of IP addresses: Class A through Class E.
Of
these, Classes A, B, and C are used for unicast addresses, Class D
is
used for multicast addresses, and Class E addresses are reserved
for
future use.
With the advent of
classless addressing
[CIDR1, CIDR2], the
network-number part of
an address may be of
any length, and the
whole
notion of address
classes becomes less
important.
There are certain special cases for IP addresses. These special cases
can be concisely summarized using the earlier notation for an IP
address:
IP-address ::=
{ <Network-number>, <Host-number> }
or
IP-address ::=
{ <Network-number>, <Subnet-number>,
<Host-number> }
if we also use the notation "-1" to mean the field contains all 1
bits. Some common special cases are as follows:
(a)
{0, 0}
This host on this network.
address (see note later).
(b)
Can only be used as a source
{0, <Host-number>}
Specified host on this network.
source address.
(c)
Can only be used as a
{ -1, -1}
Limited broadcast. Can only be used as a destination
address, and a datagram with this address must never be
forwarded outside the (sub-)net of the source.
(d)
{<Network-number>, -1}
Directed broadcast to specified network.
as a destination address.
Reynolds & Postel
Can only be used
[Page 4]
RFC 1700
Assigned Numbers
(e)
October 1994
{<Network-number>, <Subnet-number>, -1}
Directed broadcast to specified subnet.
a destination address.
(f)
Can only be used as
{<Network-number>, -1, -1}
Directed broadcast to all subnets of specified subnetted
network. Can only be used as a destination address.
(g)
{127, <any>}
Internal host loopback address.
a host.
Should never appear outside
REFERENCES
[COHEN]
Cohen, D., "On Holy Wars and a Plea for Peace", IEEE Computer
Magazine, October 1981.
[CIDR1]
Fuller, V., T. Li, J. Yu, and K. Varadhan, "Classless
Inter-Domain Routing (CIDR): an Address Assignment and
Aggregation Strategy", RFC 1519, September 1993.
[CIDR2]
Rekhter, Y., and T. Li, "An Architecture for IP Address
Allocation with CIDR", RFC 1518, September 1993.
[]
URL = ftp://ftp.isi.edu/in-notes/iana/assignments/introduction
Reynolds & Postel
[Page 5]
RFC 1700
Assigned Numbers
October 1994
VERSION NUMBERS
In the Internet Protocol (IP) [RFC791] there is a field to identify
the version of the internetwork general protocol. This field is 4
bits in size.
Assigned Internet Version Numbers
Decimal
------0
1-3
4
5
6
7
8
9
10-14
15
Keyword
------IP
ST
SIP
TP/IX
PIP
TUBA
Version
------Reserved
Unassigned
Internet Protocol
ST Datagram Mode
Simple Internet Protocol
TP/IX: The Next Internet
The P Internet Protocol
TUBA
Unassigned
Reserved
References
---------[JBP]
[JBP]
[RFC791,JBP]
[RFC1190,JWF]
[RH6]
[RXU]
[PXF]
[RXC]
[JBP]
[JBP]
REFERENCES
[RFC791] Postel, J., ed., "Internet Protocol - DARPA Internet Program
Protocol Specification", STD 5, RFC 791, USC/Information
Sciences Institute, September 1981.
[RFC1190] Topolcic, C., Editor, "Experimental Internet Stream
Protocol, Version 2 (ST-II)", RFC 1190, CIP Working Group,
October 1990.
PEOPLE
[JPB] Jon Postel <postel@isi.edu>
[JWF] Jim Forgie <FORGIE@XN.LL.MIT.ED>
[RH6] Robert Hinden <Hinden@ENG.SUN.COM>
[RXU] Robert Ullmann <ariel@world.std.com>
[PXF] Paul Francis <francis@cactus.ntt.jp>
[RXC] Ross Callon <callon@wellfleet.com>
[]
Reynolds & Postel
[Page 6]
RFC 1700
Assigned Numbers
October 1994
URL = ftp://ftp.isi.edu/in-notes/iana/assignments/version-numbers
Reynolds & Postel
[Page 7]
RFC 1700
Assigned Numbers
October 1994
PROTOCOL NUMBERS
In the Internet Protocol (IP) [DDN], [RFC791] there is a field, called
Protocol, to identify the next level protocol. This is an 8 bit
field.
Assigned Internet Protocol Numbers
Decimal
------0
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
Keyword
-------
Protocol
References
----------------Reserved
[JBP]
ICMP
Internet Control Message
[RFC792,JBP]
IGMP
Internet Group Management
[RFC1112,JBP]
GGP
Gateway-to-Gateway
[RFC823,MB]
IP
IP in IP (encasulation)
[JBP]
ST
Stream
[RFC1190,IEN119,JWF]
TCP
Transmission Control
[RFC793,JBP]
UCL
UCL
[PK]
EGP
Exterior Gateway Protocol
[RFC888,DLM1]
IGP
any private interior gateway
[JBP]
BBN-RCC-MON BBN RCC Monitoring
[SGC]
NVP-II
Network Voice Protocol
[RFC741,SC3]
PUP
PUP
[PUP,XEROX]
ARGUS
ARGUS
[RWS4]
EMCON
EMCON
[BN7]
XNET
Cross Net Debugger
[IEN158,JFH2]
CHAOS
Chaos
[NC3]
UDP
User Datagram
[RFC768,JBP]
MUX
Multiplexing
[IEN90,JBP]
DCN-MEAS
DCN Measurement Subsystems
[DLM1]
HMP
Host Monitoring
[RFC869,RH6]
PRM
Packet Radio Measurement
[ZSU]
XNS-IDP
XEROX NS IDP
[ETHERNET,XEROX]
TRUNK-1
Trunk-1
[BWB6]
TRUNK-2
Trunk-2
[BWB6]
LEAF-1
Leaf-1
[BWB6]
LEAF-2
Leaf-2
[BWB6]
RDP
Reliable Data Protocol
[RFC908,RH6]
IRTP
Internet Reliable Transaction [RFC938,TXM]
ISO-TP4
ISO Transport Protocol Class 4 [RFC905,RC77]
NETBLT
Bulk Data Transfer Protocol
[RFC969,DDC1]
MFE-NSP
MFE Network Services Protocol [MFENET,BCH2]
MERIT-INP
MERIT Internodal Protocol
[HWB]
SEP
Sequential Exchange Protocol
[JC120]
3PC
Third Party Connect Protocol
[SAF3]
IDPR
Inter-Domain Policy Routing Protocol [MXS1]
Reynolds & Postel
[Page 8]
RFC 1700
36
37
38
39
40
41
42
43
44
45
46
47
48
49
50
51
52
53
54
55-60
61
62
63
64
65
66
67
68
69
70
71
72
73
74
75
76
77
78
79
80
81
82
83
84
85
86
87
88
Assigned Numbers
October 1994
XTP
DDP
IDPR-CMTP
TP++
IL
SIP
SDRP
SIP-SR
SIP-FRAG
IDRP
RSVP
GRE
MHRP
BNA
SIPP-ESP
SIPP-AH
I-NLSP
SWIPE
NHRP
XTP
[GXC]
Datagram Delivery Protocol
[WXC]
IDPR Control Message Transport Proto [MXS1]
TP++ Transport Protocol
[DXF]
IL Transport Protocol
[DXP2]
Simple Internet Protocol
[SXD]
Source Demand Routing Protocol
[DXE1]
SIP Source Route
[SXD]
SIP Fragment
[SXD]
Inter-Domain Routing Protocol
[Sue Hares]
Reservation Protocol
[Bob Braden]
General Routing Encapsulation
[Tony Li]
Mobile Host Routing Protocol[David Johnson]
BNA
[Gary Salamon]
SIPP Encap Security Payload [Steve Deering]
SIPP Authentication Header [Steve Deering]
Integrated Net Layer Security TUBA [GLENN]
IP with Encryption
[JI6]
NBMA Next Hop Resolution Protocol
Unassigned
[JBP]
any host internal protocol
[JBP]
CFTP
CFTP
[CFTP,HCF2]
any local network
[JBP]
SAT-EXPAK
SATNET and Backroom EXPAK
[SHB]
KRYPTOLAN
Kryptolan
[PXL1]
RVD
MIT Remote Virtual Disk Protocol
[MBG]
IPPC
Internet Pluribus Packet Core
[SHB]
any distributed file system
[JBP]
SAT-MON
SATNET Monitoring
[SHB]
VISA
VISA Protocol
[GXT1]
IPCV
Internet Packet Core Utility
[SHB]
CPNX
Computer Protocol Network Executive [DXM2]
CPHB
Computer Protocol Heart Beat
[DXM2]
WSN
Wang Span Network
[VXD]
PVP
Packet Video Protocol
[SC3]
BR-SAT-MON Backroom SATNET Monitoring
[SHB]
SUN-ND
SUN ND PROTOCOL-Temporary
[WM3]
WB-MON
WIDEBAND Monitoring
[SHB]
WB-EXPAK
WIDEBAND EXPAK
[SHB]
ISO-IP
ISO Internet Protocol
[MTR]
VMTP
VMTP
[DRC3]
SECURE-VMTP SECURE-VMTP
[DRC3]
VINES
VINES
[BXH]
TTP
TTP
[JXS]
NSFNET-IGP NSFNET-IGP
[HWB]
DGP
Dissimilar Gateway Protocol
[DGP,ML109]
TCF
TCF
[GAL5]
IGRP
IGRP
[CISCO,GXS]
Reynolds & Postel
[Page 9]