User avatar None

String updated in the repository
This model considers a hypothetical TCP connection that suffers from equally spaced segment losses. If :math:`p` is the segment loss ratio, then the TCP connection successfully transfers :math:`\frac{1}{p}-1` segments and the next segment is lost. If we ignore the slow-start at the beginning of the connection, TCP in this environment is always in congestion avoidance as there are only isolated losses that can be recovered by using fast retransmit. The evolution of the congestion window is thus as shown in the figure below. Note that the `x-axis` of this figure represents time measured in units of one round-trip-time, which is supposed to be constant in the model, and the `y-axis` represents the size of the congestion window measured in MSS-sized segments.
This model considers a hypothetical TCP connection that suffers from equally spaced segment losses. If :math:`p` is the segment loss ratio, then the TCP connection successfully transfers :math:`\frac{1}{p}-1` segments and the next segment is lost. If we ignore the slow-start at the beginning of the connection, TCP in this environment is always in congestion avoidance as there are only isolated losses that can be recovered by using fast retransmit. The evolution of the congestion window is thus as shown in the figure below. Note that the `x-axis` of this figure represents time measured in units of one round-trip-time, which is supposed to be constant in the model, and the `y-axis` represents the size of the congestion window measured in MSS-sized segments.
3 years ago
User avatar None

Resource updated
File “locale/pot/protocols/bgp.pot” was added. 3 years ago
User avatar None

Resource updated
File “locale/pot/exercises/trace.pot” was added. 3 years ago
User avatar None

Resource updated
File “locale/pot/exercises/tls.pot” was added. 3 years ago
User avatar None

Resource updated
File “locale/pot/exercises/tcp.pot” was added. 3 years ago
User avatar None

Resource updated
File “locale/pot/exercises/tcp-2.pot” was added. 3 years ago
User avatar None

Resource updated
File “locale/pot/exercises/routing-protocols.pot” was added. 3 years ago
User avatar None

Resource updated
File “locale/pot/exercises/routing-policies.pot” was added. 3 years ago
User avatar None

Resource updated
File “locale/pot/exercises/lan.pot” was added. 3 years ago
User avatar None

Resource updated
File “locale/pot/exercises/ipv6.pot” was added. 3 years ago
User avatar None

Resource updated
File “locale/pot/exercises/http.pot” was added. 3 years ago
User avatar None

Resource updated
File “locale/pot/exercises/email.pot” was added. 3 years ago
User avatar None

Resource updated
File “locale/pot/exercises/dns.pot” was added. 3 years ago
User avatar None

Resource updated
File “locale/pot/principles/security.pot” was added. 3 years ago
User avatar None

String updated in the repository
a decryption function, :math:`D_{p}`, that takes a key and a message as parameters
a decryption function, :math:`D_{p}`, that takes a key and a message as parameters
3 years ago
User avatar None

String updated in the repository
an encryption function, :math:`E_{p}`, that takes a key and a message as parameters
an encryption function, :math:`E_{p}`, that takes a key and a message as parameters
3 years ago
User avatar None

Resource updated
File “locale/pot/protocols/dns.pot” was added. 3 years ago
User avatar None

String updated in the repository
An important point to note regarding the Domain Name System it that it is extensible. Thanks to the `Type` and `RDLength` fields, the format of the Resource Records can easily be extended. Furthermore, a DNS implementation that receives a new Resource Record that it does not understand can ignore the record while still being able to process the other parts of the message. This allows, for example, a DNS server that only supports IPv6 to safely ignore the IPv4 addresses listed in the DNS reply for `www.ietf.org` while still being able to correctly parse the Resource Records that it understands. This allowed the Domain Name System to evolve over the years while still preserving the backward compatibility with already deployed DNS implementations.
An important point to note regarding the Domain Name System it that it is extensible. Thanks to the `Type` and `RDLength` fields, the format of the Resource Records can easily be extended. Furthermore, a DNS implementation that receives a new Resource Record that it does not understand can ignore the record while still being able to process the other parts of the message. This allows, for example, a DNS server that only supports IPv6 to safely ignore the IPv4 addresses listed in the DNS reply for `www.ietf.org` while still being able to correctly parse the Resource Records that it understands. This allowed the Domain Name System to evolve over the years while still preserving the backward compatibility with already deployed DNS implementations.
3 years ago
User avatar None

String updated in the repository
Several types of DNS RR are used in practice. The `A` type encodes the IPv4 address that corresponds to the specified name. The `AAAA` type encodes the IPv6 address that corresponds to the specified name. A `NS` record contains the name of the DNS server that is responsible for a given domain. For example, a query for the `AAAA` record associated to the `www.ietf.org` name returned the following answer.
Several types of DNS RR are used in practice. The `A` type encodes the IPv4 address that corresponds to the specified name. The `AAAA` type encodes the IPv6 address that corresponds to the specified name. A `NS` record contains the name of the DNS server that is responsible for a given domain. For example, a query for the `AAAA` record associated to the `www.ietf.org` name returned the following answer.
3 years ago
User avatar None

String updated in the repository
In a `Resource Record` (`RR`), the `Name` indicates the name of the node to which this resource record pertains. The two-)bytes `Type` field indicates the type of resource record. The `Class` field was used to support the utilization of the DNS in other environments than the Internet. The `IN` `Class` refers to Internet names.
In a `Resource Record` (`RR`), the `Name` indicates the name of the node to which this resource record pertains. The two-)bytes `Type` field indicates the type of resource record. The `Class` field was used to support the utilization of the DNS in other environments than the Internet. The `IN` `Class` refers to Internet names.
3 years ago

Search