Exit Zen
75
../../protocols/bgp.rst:296
English
the router has been configured by the network operator to advertise over its BGP session some of the routes that it learns with its intradomain routing protocol. For example, an enterprise router may advertise over a BGP session with its provider the routes to remote sites when these routes are reachable and advertised by the intradomain routing protocol
0/3560 · 356
75
../../protocols/email.rst:238
English
20
0/100 · 2
75
../../protocols/ethernet.rst:335
English
the `cost` of the shortest path between the switch that sent the `BPDU` and the root switch (`c`)
0/970 · 97
75
../../protocols/http.rst:389
English
A second solution to allow servers to tune that content to the needs and capabilities of the user is to rely on the different types of `Accept-*` HTTP headers. For example, the `Accept-Language:` header can be used by the client to indicate its preferred languages. Unfortunately, in practice this header is usually set based on the default language of the browser and it is difficult for a user to indicate the language it prefers by selecting options for each visited web server.
0/4810 · 481
75
../../protocols/ipv6.rst:289
English
Assume that ``B`` and ``D`` are part of a multicast group. If ``A`` sends a multicast packet towards this group, then ``R1`` will replicate the packet to forward it to ``R2`` and ``R3``. ``R2`` would forward the packet towards ``B``. ``R3`` would forward the packet towards ``R4`` that would deliver it to ``D``.
0/3120 · 312
75
../../protocols/ethernet.rst:287
English
Security issues with Ethernet hubs and switches
0/470 · 47
75
../../protocols/tcp.rst:243
English
TCP reliable data transfer
0/260 · 26
75
../../protocols/tls.rst:401
English
In 2014, the IETF TLS working started to work on the development of version 1.3 of the TLS protocol. Their main objectives [Rescorla2015]_ for this new version were:
0/1650 · 165
76
../../glossary.rst:71
English
a public internet, i.e. a network composed of different networks that are running :term:`IPv4` or :term:`IPv6`
0/1100 · 110
76
../../principles/network.rst:339
English
Fragmenting packets on a per-link basis, as presented for the second solution, can minimize the transmission overhead since a packet is only fragmented on the links where fragmentation is required. Large packets can continue to be used downstream of a link that only accepts small packets. However, this reduction of the overhead comes with two drawbacks. First, fragmenting packets, potentially on all links, increases the processing time and the buffer requirements on the routers. Second, this solution leads to a longer end-to-end delay since the downstream router has to reassemble all the packet fragments before forwarding the packet.
0/6410 · 641
76
../../principles/reliability.rst:252
English
`ETX`: `0000011` b
0/180 · 18
76
../../principles/transport.rst:303
English
Once the connection has been established, the service provider supplies two data streams to the communicating users. The first data stream can be used by the initiating user to send SDUs. The second data stream allows the responding user to send SDUs to the initiating user. The data streams can be organized in different ways. A first organization is the `message-mode` transfer. With the `message-mode` transfer, the service provider guarantees that one and only one `Data.indication` will be delivered to the endpoint of the data stream for each `Data.request` primitive issued by the other endpoint. The `message-mode` transfer is illustrated in the figure below. The main advantage of the `message-transfer` mode is that the recipient receives exactly the SDUs that were sent by the other user. If each SDU contains a command, the receiving user can process each command as soon as it receives a SDU.
0/9050 · 905
76
../../principles/sharing.rst:309
English
ALOHA
0/100 · 5
76
../../principles/security.rst:891
English
agree on a way to encrypt the messages that they will exchange
0/620 · 62
76
../../exercises/ipv6.rst:696
English
To help students to start using IPMininet, `Mathieu Jadin <https://inl.info.ucl.ac.be/mjadin.html>`_ has created a Vagrant box that launches a Ubuntu virtual machine with all the required software. See https://ipmininet.readthedocs.io/en/latest/install.html for additional information.
0/2850 · 285
76
../../exercises/routing-protocols.rst:1066
English
Draw the network and try to predict how it will react to a shutdown of any of the customer-provider links ?
0/1070 · 107
76
../../protocols/bgp.rst:298
English
The first solution is the most frequent. Advertising routes learned from an intradomain routing protocol is not recommended, this is because if the route flaps [#fflap]_, this would cause a large number of BGP messages being exchanged in the global Internet.
0/2580 · 258
76
../../protocols/email.rst:238
English
U
0/100 · 1
76
../../protocols/ethernet.rst:336
English
the `identifier` of the switch that sent the `BPDU` (`T`)
0/570 · 57
76
../../protocols/http.rst:391
English
The third and widely adopted solution are HTTP cookies. HTTP cookies were initially developed as a private extension by Netscape_. They are now part of the standard :rfc:`6265`. In a nutshell, a cookie is a short string that is chosen by a server to represent a given client. Two HTTP headers are used : `Cookie:` and `Set-Cookie:`. When a server receives an HTTP request from a new client (i.e. an HTTP request that does not contain the `Cookie:` header), it generates a cookie for the client and includes it in the `Set-Cookie:` header of the returned HTTP response. The `Set-Cookie:` header contains several additional parameters including the domain names for which the cookie is valid. The client stores all received cookies on disk and every time it sends an HTTP request, it verifies whether it already knows a cookie for this domain. If so, it attaches the `Cookie:` header to the HTTP request. This is illustrated in the figure below with HTTP 1.1, but cookies also work with HTTP 1.0.
0/9940 · 994