Unit List
Units API.
See the Weblate's Web API documentation for detailed description of the API.
GET /api/units/?format=api&page=590
{ "count": 15869, "next": "https://weblate.info.ucl.ac.be/api/units/?format=api&page=591", "previous": "https://weblate.info.ucl.ac.be/api/units/?format=api&page=589", "results": [ { "translation": "https://weblate.info.ucl.ac.be/api/translations/cnp3-ebook/principlessharing/en/?format=api", "source": [ "Consider first a window of one segment. This segment takes 4 msec to reach host `D`. The destination replies with an acknowledgment and the next segment can be transmitted. With such a sending window, the transmission rate is roughly 250 segments per second or 250 Kbps. This is illustrated in the figure below where each square of the grid corresponds to one millisecond." ], "previous_source": "", "target": [ "Consider first a window of one segment. This segment takes 4 msec to reach host `D`. The destination replies with an acknowledgment and the next segment can be transmitted. With such a sending window, the transmission rate is roughly 250 segments per second or 250 Kbps. This is illustrated in the figure below where each square of the grid corresponds to one millisecond." ], "id_hash": -7099893755671594027, "content_hash": -7099893755671594027, "location": "../../principles/sharing.rst:1020", "context": "", "note": "", "flags": "", "state": 100, "fuzzy": false, "translated": true, "approved": false, "position": 170, "has_suggestion": false, "has_comment": false, "has_failing_check": false, "num_words": 63, "source_unit": "https://weblate.info.ucl.ac.be/api/units/34949/?format=api", "priority": 100, "id": 34949, "web_url": "https://weblate.info.ucl.ac.be/translate/cnp3-ebook/principlessharing/en/?checksum=1d781c3efe2e3bd5", "url": "https://weblate.info.ucl.ac.be/api/units/34949/?format=api", "explanation": "", "extra_flags": "", "pending": false, "timestamp": "2019-10-14T10:39:40.032407+02:00" }, { "translation": "https://weblate.info.ucl.ac.be/api/translations/cnp3-ebook/principlessharing/en/?format=api", "source": [ "Consider now a window of two segments. Host `A` can send two segments within 2 msec on its 1 Mbps link. If the first segment is sent at time :math:`t_{0}`, it reaches host `D` at :math:`t_{0}+4`. Host `D` replies with an acknowledgment that opens the sending window on host `A` and enables it to transmit a new segment. In the meantime, the second segment was buffered by router `R1`. It reaches host `D` at :math:`t_{0}+6` and an acknowledgment is returned. With a window of two segments, host `A` transmits at roughly 500 Kbps, i.e. the transmission rate of the bottleneck link." ], "previous_source": "", "target": [ "Consider now a window of two segments. Host `A` can send two segments within 2 msec on its 1 Mbps link. If the first segment is sent at time :math:`t_{0}`, it reaches host `D` at :math:`t_{0}+4`. Host `D` replies with an acknowledgment that opens the sending window on host `A` and enables it to transmit a new segment. In the meantime, the second segment was buffered by router `R1`. It reaches host `D` at :math:`t_{0}+6` and an acknowledgment is returned. With a window of two segments, host `A` transmits at roughly 500 Kbps, i.e. the transmission rate of the bottleneck link." ], "id_hash": 3009145348939091196, "content_hash": 3009145348939091196, "location": "../../principles/sharing.rst:1068", "context": "", "note": "", "flags": "", "state": 100, "fuzzy": false, "translated": true, "approved": false, "position": 171, "has_suggestion": false, "has_comment": false, "has_failing_check": false, "num_words": 101, "source_unit": "https://weblate.info.ucl.ac.be/api/units/34950/?format=api", "priority": 100, "id": 34950, "web_url": "https://weblate.info.ucl.ac.be/translate/cnp3-ebook/principlessharing/en/?checksum=a9c2a1c071088cfc", "url": "https://weblate.info.ucl.ac.be/api/units/34950/?format=api", "explanation": "", "extra_flags": "", "pending": false, "timestamp": "2019-10-14T10:39:40.132519+02:00" }, { "translation": "https://weblate.info.ucl.ac.be/api/translations/cnp3-ebook/principlessharing/en/?format=api", "source": [ "Our last example is a window of four segments. These segments are sent at :math:`t_{0}`, :math:`t_{0}+1`, :math:`t_{0}+2` and :math:`t_{0}+3`. The first segment reaches host `D` at :math:`t_{0}+4`. Host `D` replies to this segment by sending an acknowledgment that enables host `A` to transmit its fifth segment. This segment reaches router `R1` at :math:`t_{0}+5`. At that time, router `R1` is transmitting the third segment to router `R2` and the fourth segment is still in its buffers. At time :math:`t_{0}+6`, host `D` receives the second segment and returns the corresponding acknowledgment. This acknowledgment enables host `A` to send its sixth segment. This segment reaches router `R1` at roughly :math:`t_{0}+7`. At that time, the router starts to transmit the fourth segment to router `R2`. Since link `R1-R2` can only sustain 500 Kbps, packets will accumulate in the buffers of `R1`. On average, there will be two packets waiting in the buffers of `R1`. The presence of these two packets will induce an increase of the round-trip-time as measured by the transport protocol. While the first segment was acknowledged within 4 msec, the fifth segment (`data(4)`) that was transmitted at time :math:`t_{0}+4` is only acknowledged at time :math:`t_{0}+11`. On average, the sender transmits at 500 Kbps, but the utilization of a large window induces a longer delay through the network." ], "previous_source": "", "target": [ "Our last example is a window of four segments. These segments are sent at :math:`t_{0}`, :math:`t_{0}+1`, :math:`t_{0}+2` and :math:`t_{0}+3`. The first segment reaches host `D` at :math:`t_{0}+4`. Host `D` replies to this segment by sending an acknowledgment that enables host `A` to transmit its fifth segment. This segment reaches router `R1` at :math:`t_{0}+5`. At that time, router `R1` is transmitting the third segment to router `R2` and the fourth segment is still in its buffers. At time :math:`t_{0}+6`, host `D` receives the second segment and returns the corresponding acknowledgment. This acknowledgment enables host `A` to send its sixth segment. This segment reaches router `R1` at roughly :math:`t_{0}+7`. At that time, the router starts to transmit the fourth segment to router `R2`. Since link `R1-R2` can only sustain 500 Kbps, packets will accumulate in the buffers of `R1`. On average, there will be two packets waiting in the buffers of `R1`. The presence of these two packets will induce an increase of the round-trip-time as measured by the transport protocol. While the first segment was acknowledged within 4 msec, the fifth segment (`data(4)`) that was transmitted at time :math:`t_{0}+4` is only acknowledged at time :math:`t_{0}+11`. On average, the sender transmits at 500 Kbps, but the utilization of a large window induces a longer delay through the network." ], "id_hash": -3181305617201632254, "content_hash": -3181305617201632254, "location": "../../principles/sharing.rst:1141", "context": "", "note": "", "flags": "", "state": 100, "fuzzy": false, "translated": true, "approved": false, "position": 172, "has_suggestion": false, "has_comment": false, "has_failing_check": false, "num_words": 216, "source_unit": "https://weblate.info.ucl.ac.be/api/units/34951/?format=api", "priority": 100, "id": 34951, "web_url": "https://weblate.info.ucl.ac.be/translate/cnp3-ebook/principlessharing/en/?checksum=53d9bb657cbdec02", "url": "https://weblate.info.ucl.ac.be/api/units/34951/?format=api", "explanation": "", "extra_flags": "", "pending": false, "timestamp": "2019-10-14T10:39:40.212206+02:00" }, { "translation": "https://weblate.info.ucl.ac.be/api/translations/cnp3-ebook/principlessharing/en/?format=api", "source": [ "A congestion control scheme for our simple transport protocol could be implemented as follows." ], "previous_source": "", "target": [ "A congestion control scheme for our simple transport protocol could be implemented as follows." ], "id_hash": 8200104304025461365, "content_hash": 8200104304025461365, "location": "../../principles/sharing.rst:1231", "context": "", "note": "", "flags": "", "state": 100, "fuzzy": false, "translated": true, "approved": false, "position": 175, "has_suggestion": false, "has_comment": false, "has_failing_check": false, "num_words": 14, "source_unit": "https://weblate.info.ucl.ac.be/api/units/34954/?format=api", "priority": 100, "id": 34954, "web_url": "https://weblate.info.ucl.ac.be/translate/cnp3-ebook/principlessharing/en/?checksum=f1cc9f6b2296e275", "url": "https://weblate.info.ucl.ac.be/api/units/34954/?format=api", "explanation": "", "extra_flags": "", "pending": false, "timestamp": "2019-10-14T10:39:40.481542+02:00" }, { "translation": "https://weblate.info.ucl.ac.be/api/translations/cnp3-ebook/principlessharing/en/?format=api", "source": [ "In the above pseudocode, `cwin` contains the congestion window stored as a real number of segments. This congestion window is updated upon the arrival of each acknowledgment and when congestion is detected. For simplicity, we assume that `cwin` is stored as a floating point number but only full segments can be transmitted." ], "previous_source": "", "target": [ "In the above pseudocode, `cwin` contains the congestion window stored as a real number of segments. This congestion window is updated upon the arrival of each acknowledgment and when congestion is detected. For simplicity, we assume that `cwin` is stored as a floating point number but only full segments can be transmitted." ], "id_hash": -5385032964145792128, "content_hash": -5385032964145792128, "location": "../../principles/sharing.rst:1251", "context": "", "note": "", "flags": "", "state": 100, "fuzzy": false, "translated": true, "approved": false, "position": 176, "has_suggestion": false, "has_comment": false, "has_failing_check": false, "num_words": 52, "source_unit": "https://weblate.info.ucl.ac.be/api/units/34955/?format=api", "priority": 100, "id": 34955, "web_url": "https://weblate.info.ucl.ac.be/translate/cnp3-ebook/principlessharing/en/?checksum=3544850cdc523b80", "url": "https://weblate.info.ucl.ac.be/api/units/34955/?format=api", "explanation": "", "extra_flags": "", "pending": false, "timestamp": "2019-10-14T10:39:40.568148+02:00" }, { "translation": "https://weblate.info.ucl.ac.be/api/translations/cnp3-ebook/principlessharing/en/?format=api", "source": [ "As an illustration, let us consider the network scenario above and assume that the router implements the DECBit binary feedback scheme [RJ1995]_. This scheme uses a form of Forward Explicit Congestion Notification and a router marks the congestion bit in arriving packets when its buffer contains one or more packets. In the figure below, we use a `*` to indicate a marked packet." ], "previous_source": "", "target": [ "As an illustration, let us consider the network scenario above and assume that the router implements the DECBit binary feedback scheme [RJ1995]_. This scheme uses a form of Forward Explicit Congestion Notification and a router marks the congestion bit in arriving packets when its buffer contains one or more packets. In the figure below, we use a `*` to indicate a marked packet." ], "id_hash": 1793748934362623294, "content_hash": 1793748934362623294, "location": "../../principles/sharing.rst:1254", "context": "", "note": "", "flags": "", "state": 100, "fuzzy": false, "translated": true, "approved": false, "position": 177, "has_suggestion": false, "has_comment": false, "has_failing_check": false, "num_words": 63, "source_unit": "https://weblate.info.ucl.ac.be/api/units/34956/?format=api", "priority": 100, "id": 34956, "web_url": "https://weblate.info.ucl.ac.be/translate/cnp3-ebook/principlessharing/en/?checksum=98e4ad26f0eb6d3e", "url": "https://weblate.info.ucl.ac.be/api/units/34956/?format=api", "explanation": "", "extra_flags": "", "pending": false, "timestamp": "2019-10-14T10:39:40.666937+02:00" }, { "translation": "https://weblate.info.ucl.ac.be/api/translations/cnp3-ebook/principlessharing/en/?format=api", "source": [ "When the connection starts, its congestion window is set to one segment. Segment `S0` is sent an acknowledgment at roughly :math:`t_{0}+4`. The congestion window is increased by one segment and `S1` and `S2` are transmitted at time :math:`t_{0}+4` and :math:`t_{0}+5`. The corresponding acknowledgments are received at times :math:`t_{0}+8` and :math:`t_{0}+10`. Upon reception of this last acknowledgment, the congestion window reaches `3` and segments can be sent (`S4` and `S5`). When segment `S6` reaches router `R1`, its buffers already contain `S5`. The packet containing `S6` is thus marked to inform the sender of the congestion. Note that the sender will only notice the congestion once it receives the corresponding acknowledgment at :math:`t_{0}+18`. In the meantime, the congestion window continues to increase. At :math:`t_{0}+16`, upon reception of the acknowledgment for `S5`, it reaches `4`. When congestion is detected, the congestion window is decreased down to `2`. This explains the idle time between the reception of the acknowledgment for `S*6` and the transmission of `S10`." ], "previous_source": "", "target": [ "When the connection starts, its congestion window is set to one segment. Segment `S0` is sent an acknowledgment at roughly :math:`t_{0}+4`. The congestion window is increased by one segment and `S1` and `S2` are transmitted at time :math:`t_{0}+4` and :math:`t_{0}+5`. The corresponding acknowledgments are received at times :math:`t_{0}+8` and :math:`t_{0}+10`. Upon reception of this last acknowledgment, the congestion window reaches `3` and segments can be sent (`S4` and `S5`). When segment `S6` reaches router `R1`, its buffers already contain `S5`. The packet containing `S6` is thus marked to inform the sender of the congestion. Note that the sender will only notice the congestion once it receives the corresponding acknowledgment at :math:`t_{0}+18`. In the meantime, the congestion window continues to increase. At :math:`t_{0}+16`, upon reception of the acknowledgment for `S5`, it reaches `4`. When congestion is detected, the congestion window is decreased down to `2`. This explains the idle time between the reception of the acknowledgment for `S*6` and the transmission of `S10`." ], "id_hash": -2286512366664044188, "content_hash": -2286512366664044188, "location": "../../principles/sharing.rst:1409", "context": "", "note": "", "flags": "", "state": 100, "fuzzy": false, "translated": true, "approved": false, "position": 178, "has_suggestion": false, "has_comment": false, "has_failing_check": false, "num_words": 162, "source_unit": "https://weblate.info.ucl.ac.be/api/units/34957/?format=api", "priority": 100, "id": 34957, "web_url": "https://weblate.info.ucl.ac.be/translate/cnp3-ebook/principlessharing/en/?checksum=6044ad1df273b164", "url": "https://weblate.info.ucl.ac.be/api/units/34957/?format=api", "explanation": "", "extra_flags": "", "pending": false, "timestamp": "2019-10-14T10:39:40.752595+02:00" }, { "translation": "https://weblate.info.ucl.ac.be/api/translations/cnp3-ebook/principlessharing/en/?format=api", "source": [ "In practice, a router is connected to multiple input links. The figure below shows an example with two hosts." ], "previous_source": "", "target": [ "In practice, a router is connected to multiple input links. The figure below shows an example with two hosts." ], "id_hash": 6240394201199496091, "content_hash": 6240394201199496091, "location": "../../principles/sharing.rst:1411", "context": "", "note": "", "flags": "", "state": 100, "fuzzy": false, "translated": true, "approved": false, "position": 179, "has_suggestion": false, "has_comment": false, "has_failing_check": false, "num_words": 19, "source_unit": "https://weblate.info.ucl.ac.be/api/units/34958/?format=api", "priority": 100, "id": 34958, "web_url": "https://weblate.info.ucl.ac.be/translate/cnp3-ebook/principlessharing/en/?checksum=d69a557684e74b9b", "url": "https://weblate.info.ucl.ac.be/api/units/34958/?format=api", "explanation": "", "extra_flags": "", "pending": false, "timestamp": "2019-10-14T10:39:40.831292+02:00" }, { "translation": "https://weblate.info.ucl.ac.be/api/translations/cnp3-ebook/principlessharing/en/?format=api", "source": [ "In general, the links have a non-zero delay. This is illustrated in the figure below where a delay has been added on the link between `R` and `C`." ], "previous_source": "", "target": [ "In general, the links have a non-zero delay. This is illustrated in the figure below where a delay has been added on the link between `R` and `C`." ], "id_hash": -4979191856113469667, "content_hash": -4979191856113469667, "location": "../../principles/sharing.rst:1470", "context": "", "note": "", "flags": "", "state": 100, "fuzzy": false, "translated": true, "approved": false, "position": 180, "has_suggestion": false, "has_comment": false, "has_failing_check": false, "num_words": 28, "source_unit": "https://weblate.info.ucl.ac.be/api/units/34959/?format=api", "priority": 100, "id": 34959, "web_url": "https://weblate.info.ucl.ac.be/translate/cnp3-ebook/principlessharing/en/?checksum=3ae65b6343d6b71d", "url": "https://weblate.info.ucl.ac.be/api/units/34959/?format=api", "explanation": "", "extra_flags": "", "pending": false, "timestamp": "2019-10-14T10:39:40.929496+02:00" }, { "translation": "https://weblate.info.ucl.ac.be/api/translations/cnp3-ebook/principlessharing/en/?format=api", "source": [ "Footnotes" ], "previous_source": "", "target": [ "Footnotes" ], "id_hash": 4927974446680086946, "content_hash": 4927974446680086946, "location": "../../principles/sharing.rst:1517", "context": "", "note": "", "flags": "", "state": 100, "fuzzy": false, "translated": true, "approved": false, "position": 181, "has_suggestion": false, "has_comment": false, "has_failing_check": false, "num_words": 1, "source_unit": "https://weblate.info.ucl.ac.be/api/units/34960/?format=api", "priority": 100, "id": 34960, "web_url": "https://weblate.info.ucl.ac.be/translate/cnp3-ebook/principlessharing/en/?checksum=c463aea6549199a2", "url": "https://weblate.info.ucl.ac.be/api/units/34960/?format=api", "explanation": "", "extra_flags": "", "pending": false, "timestamp": "2019-10-14T10:39:41.019800+02:00" }, { "translation": "https://weblate.info.ucl.ac.be/api/translations/cnp3-ebook/principlessharing/en/?format=api", "source": [ "Some networking technologies allow to adjust dynamically the bandwidth of links. For example, some devices can reduce their bandwidth to preserve energy. We ignore these technologies in this basic course and assume that all links used inside the network have a fixed bandwidth." ], "previous_source": "", "target": [ "Some networking technologies allow to adjust dynamically the bandwidth of links. For example, some devices can reduce their bandwidth to preserve energy. We ignore these technologies in this basic course and assume that all links used inside the network have a fixed bandwidth." ], "id_hash": 3546618734593789992, "content_hash": 3546618734593789992, "location": "../../principles/sharing.rst:1522", "context": "", "note": "", "flags": "", "state": 100, "fuzzy": false, "translated": true, "approved": false, "position": 184, "has_suggestion": false, "has_comment": false, "has_failing_check": false, "num_words": 43, "source_unit": "https://weblate.info.ucl.ac.be/api/units/34963/?format=api", "priority": 100, "id": 34963, "web_url": "https://weblate.info.ucl.ac.be/translate/cnp3-ebook/principlessharing/en/?checksum=b1381ef2c5355028", "url": "https://weblate.info.ucl.ac.be/api/units/34963/?format=api", "explanation": "", "extra_flags": "", "pending": false, "timestamp": "2019-10-14T10:39:41.290438+02:00" }, { "translation": "https://weblate.info.ucl.ac.be/api/translations/cnp3-ebook/principlessharing/en/?format=api", "source": [ "In this section, we focus on congestion control mechanisms that regulate the transmission rate of the hosts. Other types of mechanisms have been proposed in the literature. For example, `credit-based` flow-control has been proposed to avoid congestion in ATM networks [KR1995]_. With a credit-based mechanism, hosts can only send packets once they have received credits from the routers and the credits depend on the occupancy of the router's buffers." ], "previous_source": "", "target": [ "In this section, we focus on congestion control mechanisms that regulate the transmission rate of the hosts. Other types of mechanisms have been proposed in the literature. For example, `credit-based` flow-control has been proposed to avoid congestion in ATM networks [KR1995]_. With a credit-based mechanism, hosts can only send packets once they have received credits from the routers and the credits depend on the occupancy of the router's buffers." ], "id_hash": -4364533790459554377, "content_hash": -4364533790459554377, "location": "../../principles/sharing.rst:1526", "context": "", "note": "", "flags": "", "state": 100, "fuzzy": false, "translated": true, "approved": false, "position": 186, "has_suggestion": false, "has_comment": false, "has_failing_check": false, "num_words": 69, "source_unit": "https://weblate.info.ucl.ac.be/api/units/34964/?format=api", "priority": 100, "id": 34964, "web_url": "https://weblate.info.ucl.ac.be/translate/cnp3-ebook/principlessharing/en/?checksum=436e0fa4517815b7", "url": "https://weblate.info.ucl.ac.be/api/units/34964/?format=api", "explanation": "", "extra_flags": "", "pending": false, "timestamp": "2019-10-14T10:39:41.379962+02:00" }, { "translation": "https://weblate.info.ucl.ac.be/api/translations/cnp3-ebook/principlessharing/en/?format=api", "source": [ "For example, the measurements performed in the Sprint network in 2004 reported more than 10k active TCP connections on a link, see https://research.sprintlabs.com/packstat/packetoverview.php. More recent information about backbone links may be obtained from caida_ 's real-time measurements, see e.g. http://www.caida.org/data/realtime/passive/" ], "previous_source": "", "target": [ "For example, the measurements performed in the Sprint network in 2004 reported more than 10k active TCP connections on a link, see https://research.sprintlabs.com/packstat/packetoverview.php. More recent information about backbone links may be obtained from caida_ 's real-time measurements, see e.g. http://www.caida.org/data/realtime/passive/" ], "id_hash": 8497258118560370752, "content_hash": 8497258118560370752, "location": "../../principles/sharing.rst:1528", "context": "", "note": "", "flags": "", "state": 100, "fuzzy": false, "translated": true, "approved": false, "position": 187, "has_suggestion": false, "has_comment": false, "has_failing_check": false, "num_words": 40, "source_unit": "https://weblate.info.ucl.ac.be/api/units/34965/?format=api", "priority": 100, "id": 34965, "web_url": "https://weblate.info.ucl.ac.be/translate/cnp3-ebook/principlessharing/en/?checksum=f5ec533d09985040", "url": "https://weblate.info.ucl.ac.be/api/units/34965/?format=api", "explanation": "", "extra_flags": "", "pending": false, "timestamp": "2019-10-14T10:39:41.469365+02:00" }, { "translation": "https://weblate.info.ucl.ac.be/api/translations/cnp3-ebook/protocolsdns/en/?format=api", "source": [ "The Domain Name System" ], "previous_source": "", "target": [ "The Domain Name System" ], "id_hash": 53545434685672637, "content_hash": 53545434685672637, "location": "../../protocols/dns.rst:7", "context": "", "note": "", "flags": "", "state": 100, "fuzzy": false, "translated": true, "approved": false, "position": 1, "has_suggestion": false, "has_comment": false, "has_failing_check": false, "num_words": 4, "source_unit": "https://weblate.info.ucl.ac.be/api/units/34966/?format=api", "priority": 100, "id": 34966, "web_url": "https://weblate.info.ucl.ac.be/translate/cnp3-ebook/protocolsdns/en/?checksum=80be3b4a05c88cbd", "url": "https://weblate.info.ucl.ac.be/api/units/34966/?format=api", "explanation": "", "extra_flags": "", "pending": false, "timestamp": "2019-10-14T10:41:48.079273+02:00" }, { "translation": "https://weblate.info.ucl.ac.be/api/translations/cnp3-ebook/protocolsdns/en/?format=api", "source": [ "The DNS header" ], "previous_source": "", "target": [ "The DNS header" ], "id_hash": 5059130310099444452, "content_hash": 5059130310099444452, "location": "../../protocols/dns.rst:24", "context": "", "note": "", "flags": "", "state": 100, "fuzzy": false, "translated": true, "approved": false, "position": 6, "has_suggestion": false, "has_comment": false, "has_failing_check": false, "num_words": 3, "source_unit": "https://weblate.info.ucl.ac.be/api/units/34971/?format=api", "priority": 100, "id": 34971, "web_url": "https://weblate.info.ucl.ac.be/translate/cnp3-ebook/protocolsdns/en/?checksum=c635a4366de3a2e4", "url": "https://weblate.info.ucl.ac.be/api/units/34971/?format=api", "explanation": "", "extra_flags": "", "pending": false, "timestamp": "2019-10-14T10:41:48.311868+02:00" }, { "translation": "https://weblate.info.ucl.ac.be/api/translations/cnp3-ebook/protocolsdns/en/?format=api", "source": [ "The `Transaction ID` (transaction identifier) is a 16-bits random value chosen by the client. When a client sends a question to a DNS server, it remembers the question and its identifier. When a server returns an answer, it returns in the `Transaction ID` field the identifier chosen by the client. Thanks to this identifier, the client can match the received answer with the question that it sent." ], "previous_source": "", "target": [ "The `Transaction ID` (transaction identifier) is a 16-bits random value chosen by the client. When a client sends a question to a DNS server, it remembers the question and its identifier. When a server returns an answer, it returns in the `Transaction ID` field the identifier chosen by the client. Thanks to this identifier, the client can match the received answer with the question that it sent." ], "id_hash": -770722116085384709, "content_hash": -770722116085384709, "location": "../../protocols/dns.rst:26", "context": "", "note": "", "flags": "", "state": 100, "fuzzy": false, "translated": true, "approved": false, "position": 7, "has_suggestion": false, "has_comment": false, "has_failing_check": false, "num_words": 67, "source_unit": "https://weblate.info.ucl.ac.be/api/units/34972/?format=api", "priority": 100, "id": 34972, "web_url": "https://weblate.info.ucl.ac.be/translate/cnp3-ebook/protocolsdns/en/?checksum=754dd851a23179fb", "url": "https://weblate.info.ucl.ac.be/api/units/34972/?format=api", "explanation": "", "extra_flags": "", "pending": false, "timestamp": "2019-10-14T10:41:48.369610+02:00" }, { "translation": "https://weblate.info.ucl.ac.be/api/translations/cnp3-ebook/protocolsdns/en/?format=api", "source": [ "The `RD` (recursion desired) bit is set by a client when it sends a query to a resolver. Such a query is said to be `recursive` because the resolver will recursively traverse the DNS hierarchy to retrieve the answer on behalf of the client. In the past, all resolvers were configured to perform recursive queries on behalf of any Internet host. However, this exposes the resolvers to several security risks. The simplest one is that the resolver could become overloaded by having too many recursive queries to process. Most resolvers [#f8888]_ only allow recursive queries from clients belonging to their company or network and discard all other recursive queries. The `RA` bit indicates whether the server supports recursion. The `RCODE` is used to distinguish between different types of errors. See :rfc:`1035` for additional details. The last four fields indicate the size of the `Question`, `Answer`, `Authority` and `Additional` sections of the DNS message." ], "previous_source": "", "target": [ "The `RD` (recursion desired) bit is set by a client when it sends a query to a resolver. Such a query is said to be `recursive` because the resolver will recursively traverse the DNS hierarchy to retrieve the answer on behalf of the client. In the past, all resolvers were configured to perform recursive queries on behalf of any Internet host. However, this exposes the resolvers to several security risks. The simplest one is that the resolver could become overloaded by having too many recursive queries to process. Most resolvers [#f8888]_ only allow recursive queries from clients belonging to their company or network and discard all other recursive queries. The `RA` bit indicates whether the server supports recursion. The `RCODE` is used to distinguish between different types of errors. See :rfc:`1035` for additional details. The last four fields indicate the size of the `Question`, `Answer`, `Authority` and `Additional` sections of the DNS message." ], "id_hash": -3961963045371250305, "content_hash": -3961963045371250305, "location": "../../protocols/dns.rst:39", "context": "", "note": "", "flags": "", "state": 100, "fuzzy": false, "translated": true, "approved": false, "position": 10, "has_suggestion": false, "has_comment": false, "has_failing_check": false, "num_words": 153, "source_unit": "https://weblate.info.ucl.ac.be/api/units/34975/?format=api", "priority": 100, "id": 34975, "web_url": "https://weblate.info.ucl.ac.be/translate/cnp3-ebook/protocolsdns/en/?checksum=4904479a036bf97f", "url": "https://weblate.info.ucl.ac.be/api/units/34975/?format=api", "explanation": "", "extra_flags": "", "pending": false, "timestamp": "2019-10-14T10:41:48.495084+02:00" }, { "translation": "https://weblate.info.ucl.ac.be/api/translations/cnp3-ebook/protocolsdns/en/?format=api", "source": [ "The last four sections of the DNS message contain `Resource Records` (RR). All RRs have the same top level format shown in the figure below." ], "previous_source": "", "target": [ "The last four sections of the DNS message contain `Resource Records` (RR). All RRs have the same top level format shown in the figure below." ], "id_hash": 3975678588177064952, "content_hash": 3975678588177064952, "location": "../../protocols/dns.rst:41", "context": "", "note": "", "flags": "", "state": 100, "fuzzy": false, "translated": true, "approved": false, "position": 11, "has_suggestion": false, "has_comment": false, "has_failing_check": false, "num_words": 25, "source_unit": "https://weblate.info.ucl.ac.be/api/units/34976/?format=api", "priority": 100, "id": 34976, "web_url": "https://weblate.info.ucl.ac.be/translate/cnp3-ebook/protocolsdns/en/?checksum=b72c729ca56ba3f8", "url": "https://weblate.info.ucl.ac.be/api/units/34976/?format=api", "explanation": "", "extra_flags": "", "pending": false, "timestamp": "2019-10-14T10:41:48.529445+02:00" }, { "translation": "https://weblate.info.ucl.ac.be/api/translations/cnp3-ebook/protocolsdns/en/?format=api", "source": [ "DNS Resource Records" ], "previous_source": "", "target": [ "DNS Resource Records" ], "id_hash": -673615187349469494, "content_hash": -673615187349469494, "location": "../../protocols/dns.rst:47", "context": "", "note": "", "flags": "", "state": 100, "fuzzy": false, "translated": true, "approved": false, "position": 12, "has_suggestion": false, "has_comment": false, "has_failing_check": false, "num_words": 3, "source_unit": "https://weblate.info.ucl.ac.be/api/units/34977/?format=api", "priority": 100, "id": 34977, "web_url": "https://weblate.info.ucl.ac.be/translate/cnp3-ebook/protocolsdns/en/?checksum=76a6d68e5aba06ca", "url": "https://weblate.info.ucl.ac.be/api/units/34977/?format=api", "explanation": "", "extra_flags": "", "pending": false, "timestamp": "2019-10-14T10:41:48.573176+02:00" }, { "translation": "https://weblate.info.ucl.ac.be/api/translations/cnp3-ebook/protocolsdns/en/?format=api", "source": [ "The `TTL` field indicates the lifetime of the `Resource Record` in seconds. This field is set by the server that returns an answer and indicates for how long a client or a resolver can store the `Resource Record` inside its cache. A long `TTL` indicates a stable `RR`. Some companies use short `TTL` values for mobile hosts and also for popular servers. For example, a web hosting company that wants to spread the load over a pool of hundred servers can configure its nameservers to return different answers to different clients. If each answer has a small `TTL`, the clients will be forced to send DNS queries regularly. The nameserver will reply to these queries by supplying the address of the less loaded server." ], "previous_source": "", "target": [ "The `TTL` field indicates the lifetime of the `Resource Record` in seconds. This field is set by the server that returns an answer and indicates for how long a client or a resolver can store the `Resource Record` inside its cache. A long `TTL` indicates a stable `RR`. Some companies use short `TTL` values for mobile hosts and also for popular servers. For example, a web hosting company that wants to spread the load over a pool of hundred servers can configure its nameservers to return different answers to different clients. If each answer has a small `TTL`, the clients will be forced to send DNS queries regularly. The nameserver will reply to these queries by supplying the address of the less loaded server." ], "id_hash": -4456492321405253230, "content_hash": -4456492321405253230, "location": "../../protocols/dns.rst:51", "context": "", "note": "", "flags": "", "state": 100, "fuzzy": false, "translated": true, "approved": false, "position": 14, "has_suggestion": false, "has_comment": false, "has_failing_check": false, "num_words": 124, "source_unit": "https://weblate.info.ucl.ac.be/api/units/34979/?format=api", "priority": 100, "id": 34979, "web_url": "https://weblate.info.ucl.ac.be/translate/cnp3-ebook/protocolsdns/en/?checksum=42275bd85e624992", "url": "https://weblate.info.ucl.ac.be/api/units/34979/?format=api", "explanation": "", "extra_flags": "", "pending": false, "timestamp": "2019-10-14T10:41:48.655944+02:00" } ] }