A Day in the Life of an L2/L3 TSN Data Packet.

Size: px
Start display at page:

Download "A Day in the Life of an L2/L3 TSN Data Packet."

Transcription

1 A ay in the ife of an 2/ N ata Packet. Norman Finn ersion 2 ar., 204 tsn-nfinn-ay-n-he-ife-024-v02.pdf 02 Plenary meeting, Beijing China, arch 204

2 his presentation, tsn-nfinn-ay-n-he-ife- 024-v02 is an annex to a two-part presentation. Part, tsn-nfinn-2-ata-plane-024-v04, introduces concepts on which these presentations depend. Part 2, tsn-nfinn--ata-plane-024-v0, is concerned with ayer issues. ee also cb-nfinn-how-any-ans-024- v02. tsn-nfinn-ay-n-he-ife-024-v02.pdf 2 02 Plenary meeting, Beijing China, arch 204

3 . A very brief introduction, using concepts introduced in the preceding decks, followed by A ay n he ife Of A Packet case studies. 2. Case : nd-to-end equenced N encaps.. Case 2: ixed 2/ Pgram pseudowire encaps. 4. Case : Pgram pseudowire to equenced N titching.. Case 4: C 249- HR or PRP encaps.. Case : nd-to-end thernet-over-xyz tunnels.. Case : P ulticast encaps.. A one-slide summary of conclusions is given. tsn-nfinn-ay-n-he-ife-024-v02.pdf 02 Plenary meeting, Beijing China, arch 204

4 tsn-nfinn-ay-n-he-ife-024-v02.pdf 02 Plenary meeting, Beijing China, arch 204 4

5 Higher ayers 2-ata-Plane Higher ayers work as always. equencing equencing numbers packets, and discards duplicates. plit / erge Circuit ncaps/ecaps plit /erge has one circuit above and two below its layer. Circuit ncaps /ecaps marks individual circuits. tsn-nfinn-ay-n-he-ife-024-v02.pdf 02 Plenary meeting, Beijing China, arch 204

6 2-ata-Plane his is the stack for a bridge that proxies for a non-n client, e.g. Bridge in the following examples: Proxy services bridge baggy pants diagram AN AC PHY Bridge relay N ncaps/ecaps plit/erge equencing Circuit etection AN AC 2 PHY 2 tsn-nfinn-ay-n-he-ife-024-v02.pdf 02 Plenary meeting, Beijing China, arch 204

7 equenced N tagging tsn-nfinn-ay-n-he-ife-024-v02.pdf 02 Plenary meeting, Beijing China, arch 204

8 op-down view tsn-nfinn-ay-n-he-ife-024-v02.pdf 02 Plenary meeting, Beijing China, arch 204

9 N tagging 2 4 Given that introduction, let us examine the simplest case: end-to-end connectivity through a Bridged AN. tsn-nfinn-ay-n-he-ife-024-v02.pdf 9 02 Plenary meeting, Beijing China, arch 204

10 N tagging 2 4 alker is N-aware, istener is not. alker is not AN-aware, istener is ANaware. tsn-nfinn-ay-n-he-ife-024-v02.pdf 0 02 Plenary meeting, Beijing China, arch 204

11 2 4 Without N, the bridges bridge. A: istener A: alker : whatever data A: istener A: alker AN 0 : whatever data tsn-nfinn-ay-n-he-ife-024-v02.pdf 02 Plenary meeting, Beijing China, arch 204

12 2 4 alker and istener have a higher layer relationship. A: istener A: alker : whatever data A: istener A: alker AN 0 : whatever data tsn-nfinn-ay-n-he-ife-024-v02.pdf 2 02 Plenary meeting, Beijing China, arch 204

13 2 4 he operator wants alker and istener to have a N circuit relationship,, (4[99]) so that they can get the N o. (he bridges need the circuit in order to provide the N o.) A: istener A: alker circuit_ : whatever data A: N 4 A: AN tag 99 : whatever data A: istener A: alker AN 0 : whatever data tsn-nfinn-ay-n-he-ife-024-v02.pdf 02 Plenary meeting, Beijing China, arch 204

14 2 4 But, the istener is N-unaware, so Bridge has to provide the N Circuit ecaps as a proxy service. A: istener A: alker circuit_ : whatever data A: N 4 A: AN tag 99 : whatever data A: istener A: alker AN 0 : whatever data tsn-nfinn-ay-n-he-ife-024-v02.pdf 4 02 Plenary meeting, Beijing China, arch 204

15 2 4 he operator wants equencing proxied for and by Router and Bridge, and seq. ecaps. A: N 4 A: istener A: istener A: alker circuit_ : whatever data A: N 4 A: AN tag 99 : whatever data A: AN tag 99 : N eq equence # : whatever data A: alker AN 0 circuit_ seq_number : whatever data A: istener : whatever data A: alker AN 0 tsn-nfinn-ay-n-he-ife-024-v02.pdf 02 Plenary meeting, Beijing China, arch 204

16 2 4 We want plit and erge functions, for seamless redundancy where the circuit bifurcates. A: N 40 A: N 2 A: A: A: A: A: istener A: N 4 A: alker A: AN tag 2 : N eq AN tag 0 : N eq vlan_ 0 circuit_ A: A: circuit_ AN tag 99 equence # equence # equence # AN 0 : whatever : whatever : whatever : whatever : whatever : whatever data data data data data data tsn-nfinn-ay-n-he-ife-024-v02.pdf 02 Plenary meeting, Beijing China, arch 204

17 Why is this N ecaps function upside down? Because it peers with alker s N ncaps function. tsn-nfinn-ay-n-he-ife-024-v02.pdf 02 Plenary meeting, Beijing China, arch 204

18 higher layers Host proxy 02. Relay 02. Relay Host proxy higher layers N e AN AC circuit- sequenceaware relay eq q N e plit N d N e AN AN AN AN AC virtual AC AC AN AC circuit- sequenceaware relay eq v N d erge N d AN AN AN virtual AC AC AN AC alker Bridge Bridge istener his is a more accurate picture, but you can only get so much information on one slide. tsn-nfinn-ay-n-he-ife-024-v02.pdf 02 Plenary meeting, Beijing China, arch 204

19 Higher ayers Circuit ncaps n this example, the Circuit ncaps is in the alker system (above the link). Circuit ecaps equencing plit Circuit ncaps And the equencing is in Bridge (below the link). tsn-nfinn-ay-n-he-ife-024-v02.pdf 9 02 Plenary meeting, Beijing China, arch 204

20 Higher ayers n this example, the istener system is Nunaware. equencing erge Circuit ecaps And the equencing, erge, and N ecaps are all in Bridge (below the link). tsn-nfinn-ay-n-he-ife-024-v02.pdf Plenary meeting, Beijing China, arch 204

21 ay-in-the-life view tsn-nfinn-ay-n-he-ife-024-v02.pdf 2 02 Plenary meeting, Beijing China, arch 204

22 equenced N tagging 2 4 A: A: circuit_identifier : P Pgram alker s stack is not ANaware. his is what the frame is when it hits the N ncaps layer. Note that Bridge would normally add a AN 0 tag to this frame. tsn-nfinn-ay-n-he-ife-024-v02.pdf Plenary meeting, Beijing China, arch 204

23 equenced N tagging 2 4 A: N 4 A: AN tag 99 : P Pgram alker is N-aware, so the N ncaps layer adds a AN tag, even though alker s stack is not ANaware. alker could add sequence number, but doesn t. tsn-nfinn-ay-n-he-ife-024-v02.pdf 2 02 Plenary meeting, Beijing China, arch 204

24 equenced N tagging 2 4 A: A: circuit_identifier 4[99] vlan_identifier 0 sequence_number : whatever data he equencing function adds a new N sequence number. (Notionally, the A/AN have been restored. n practice, one would not bother.) tsn-nfinn-ay-n-he-ife-024-v02.pdf Plenary meeting, Beijing China, arch 204

25 equenced N tagging 2 4 A: A: circuit_identifier 4[99] vlan_identifier 0 : N eq equence # : whatever data he equencing encaps function replaces the sequence_number parameter with a new N sequence number tag, to be defined by 02.. tsn-nfinn-ay-n-he-ife-024-v02.pdf 2 02 Plenary meeting, Beijing China, arch 204

26 equenced N tagging 2 4 A: A: circuit_ 40[2] or 2[0] vlan_identifier 0 : N eq equence # : whatever data he plit function creates two packets, with different circuit_identifiers. tsn-nfinn-ay-n-he-ife-024-v02.pdf 2 02 Plenary meeting, Beijing China, arch 204

27 equenced N tagging 2 4 A: N 40 A: AN tag 2 : N eq equence # : whatever data After being encoded, again, this is the thernet frame on the upper path. tsn-nfinn-ay-n-he-ife-024-v02.pdf 2 02 Plenary meeting, Beijing China, arch 204

28 equenced N tagging 2 4 A: N 2 A: AN tag 0 : N eq equence # : whatever data Note that we have a different circuit on the second path. Another presentation is required to discuss whether the A, the AN, both, or neither, should be different. tsn-nfinn-ay-n-he-ife-024-v02.pdf 2 02 Plenary meeting, Beijing China, arch 204

29 equenced N tagging 2 4 A: A: circuit_ 40[2] or 2[0] vlan_identifier : N eq 0 : equence N eq # : equence whatever # : whatever data data he N ecaps function restores the proper A and AN, and extracts the circuit_identifier. tsn-nfinn-ay-n-he-ife-024-v02.pdf Plenary meeting, Beijing China, arch 204

30 equenced N tagging 2 4 A: A: circuit_identifier 4[99] vlan_identifier 0 : N eq equence # : whatever data he erge function takes all packets and gives them the same circuit_identifier. (t is the same as on the alker to Bridge link.) (here are still 2 packets.) tsn-nfinn-ay-n-he-ife-024-v02.pdf 0 02 Plenary meeting, Beijing China, arch 204

31 equenced N tagging 2 4 A: A: circuit_identifier 4[99] vlan_identifier 0 sequence_number : whatever data he equencing ecapsulation function exposes the sequence_ number so that the equence iscard function can discard the duplicates. (here are still 2 packets.) tsn-nfinn-ay-n-he-ife-024-v02.pdf 02 Plenary meeting, Beijing China, arch 204

32 equenced N tagging 2 4 A: A: AN tag 0 : whatever data A single frame is output from equencing function. t is what would have come from the alker, modulo the AN tag changes the bridges would make. tsn-nfinn-ay-n-he-ife-024-v02.pdf 2 02 Plenary meeting, Beijing China, arch 204

33 ummary: 2 4 his uses the full plit/erge functionality with different cicuit_identifiers on the paths. A: istener A: alker circuit_ : whatever data A: N 4 A: AN tag 99 : whatever data A: N 40 A: AN tag 2 : N eq equence # : whatever data A: N 2 A: AN tag 0 : N eq equence # : whatever data A: A: : whatever data AN 0 tsn-nfinn-ay-n-he-ife-024-v02.pdf 02 Plenary meeting, Beijing China, arch 204

34 ariant : 2 4 his uses the full plit/erge functionality with different cicuit_identifiers on the paths. A: istener A: alker circuit_ : whatever data A: N 4 A: AN tag 99 : whatever data A: N 4 A: AN tag 99 : N eq equence # : whatever data A: A: : whatever data AN 0 tsn-nfinn-ay-n-he-ife-024-v02.pdf 4 02 Plenary meeting, Beijing China, arch 204

35 ariant 2: 2 4 f alker does the sequencing and encaps, and all paths use the same encaps, it gets really simple! A: N 4 A: istener A: alker circuit_ : whatever data A: AN tag 99 : N eq equence # : whatever data A: A: : whatever data AN 0 tsn-nfinn-ay-n-he-ife-024-v02.pdf 02 Plenary meeting, Beijing China, arch 204

36 tsn-nfinn-ay-n-he-ife-024-v02.pdf 02 Plenary meeting, Beijing China, arch 204

37 2 Bridge 4 R/router N aware alker Router plit R R / Router R / Router Bridges Bridge erge N unaware istener ingle-port N- AN-aware alker and a single-port N- AN-unaware istener. he alker sequences, and peers to the iscard in Bridge. alker attached to a router; istener to a bridge. A network with a variety of routers and bridges. tsn-nfinn-ay-n-he-ife-024-v02.pdf 02 Plenary meeting, Beijing China, arch 204

38 2 Bridge 4 R/router pseudowire label 2 control (sequence) Pgram alker and Bridge have chosen to use an Pgram pseudowire for the circuit. tsn-nfinn-ay-n-he-ife-024-v02.pdf 02 Plenary meeting, Beijing China, arch 204

39 2 Bridge 4 R/router N aware alker Router plit R R / Router R / Router Bridges Bridge erge Router and Bridge are the split/merge (seamless redundancy) peers, because they split and merge the circuits. N unaware istener (nserting the plit function in Router requires an extra ncode/ecode pair.) tsn-nfinn-ay-n-he-ife-024-v02.pdf 9 02 Plenary meeting, Beijing China, arch 204

40 2 Bridge 4 R/router N aware alker Router plit R R / Router R / Router Bridges Bridge erge N unaware istener Assuming that the encode/decode used by the plit/erge are pseudowires, we require a network of abel witched Paths (Ps) to connect to to. ach endpoint is a abel dge Router (R) function. tsn-nfinn-ay-n-he-ife-024-v02.pdf Plenary meeting, Beijing China, arch 204

41 2 Bridge 4 R/router N aware alker N Circuit ncaps/ecaps pairs are needed to convey the circuit over the various Bridged ANs. (Note the blue, instead of purple, letter and outline.) Router plit R R / Router R / Router Bridges Bridge erge N unaware istener tsn-nfinn-ay-n-he-ife-024-v02.pdf 4 02 Plenary meeting, Beijing China, arch 204

42 tsn-nfinn-ay-n-he-ife-024-v02.pdf Plenary meeting, Beijing China, arch 204 Pgram pseudowire Pgram alker has an Pgram to send to istener. 2 4

43 Pgram pseudowire 2 4 pseudowire label 2 control (sequence) Pgram alker s combined N ncaps and equencing functions use an Pgram pseudowire for the circuit. Bridge s functions are at the other end of the network. tsn-nfinn-ay-n-he-ife-024-v02.pdf 4 02 Plenary meeting, Beijing China, arch 204

44 Pgram pseudowire 2 4 label 0 pseudowire label 2 control (sequence) Pgram n the general case, the R function would encapsulate the pseudowire would be carried in an P. tsn-nfinn-ay-n-he-ife-024-v02.pdf Plenary meeting, Beijing China, arch 204

45 Pgram pseudowire 2 4 label 0 pseudowire label 2 control (sequence) Pgram n this particular case, we will assume that Router is doing a Penultimate Hop Pop (PHP) function. hat eliminates the need for the outside label encaps. tsn-nfinn-ay-n-he-ife-024-v02.pdf 4 02 Plenary meeting, Beijing China, arch 204

46 he PHP step may be controversial. Perhaps there is another P label, a path label, on the frame between the alker and Router. tsn-nfinn-ay-n-he-ife-024-v02.pdf 4 02 Plenary meeting, Beijing China, arch 204

47 Pgram pseudowire 2 4 A: Router A: : P pseudowire label 2 control (sequence) Pgram o, the frame from alker to Router looks like this on the thernet between alker and Router. tsn-nfinn-ay-n-he-ife-024-v02.pdf 4 02 Plenary meeting, Beijing China, arch 204

48 Pgram pseudowire 2 4 circuit_ (psw 2) sequence_# (control) Pgram he plitter function Router is given the Pgram. in tsn-nfinn-ay-n-he-ife-024-v02.pdf 4 02 Plenary meeting, Beijing China, arch 204

49 Pgram pseudowire 2 4 circuit_ (psw 49) sequence_# (control) Pgram circuit_ (psw ) sequence_# (control) Pgram he plitter function has split the one pseudowire 2 into two pseudowires 49 and, copying the one control word to both of them. tsn-nfinn-ay-n-he-ife-024-v02.pdf Plenary meeting, Beijing China, arch 204

50 Pgram pseudowire 2 4 pseudowire label 49 control (sequence) Pgram pseudowire label control (sequence) Pgram he N ncapsulation function (an Pgram pseudowire encaps) generates these two packets, ready to enter the two Ps. tsn-nfinn-ay-n-he-ife-024-v02.pdf 0 02 Plenary meeting, Beijing China, arch 204

51 Pgram pseudowire 2 4 A: Router 4 A: Router vlan_identifier circuit_identifier : P unnel label pseudowire label 49 control (sequence) Pgram he upper tunnel looks like this, when labeled with unnel, and before applying the N ncapsulation. his would be the usual thernet frame from Router to Router 4 tsn-nfinn-ay-n-he-ife-024-v02.pdf 02 Plenary meeting, Beijing China, arch 204

52 Pgram pseudowire 2 4 A: N 40 A: Router AN tag 09 : P unnel label pseudowire label 49 control (sequence) Pgram But, Router and Router 4 are separated by a N bridged network, so require a N encapsulation. his gets the packet to Router 4. tsn-nfinn-ay-n-he-ife-024-v02.pdf 2 02 Plenary meeting, Beijing China, arch 204

53 Pgram pseudowire 2 4 A: Router A: Router : P unnel label pseudowire label control (sequence) Pgram eanwhile, Router/R, Router/R and Router/R are moving the second P packet along. No N encaps is needed in the absence of bridges. tsn-nfinn-ay-n-he-ife-024-v02.pdf 02 Plenary meeting, Beijing China, arch 204

54 Pgram pseudowire 2 4 A: Router A: Router : P unnel label 4 pseudowire label control (sequence) Pgram eanwhile, Router/R, Router/R and Router/R are moving the P packet along. Router/R changes the unnel label 4. tsn-nfinn-ay-n-he-ife-024-v02.pdf 4 02 Plenary meeting, Beijing China, arch 204

55 Pgram pseudowire 2 4 unnel label pseudowire label 49 control (sequence) Pgram After N decapsulation, Router 4 has this labeled packet. unnel label 4 pseudowire label control (sequence) Pgram And Router has this one. tsn-nfinn-ay-n-he-ife-024-v02.pdf 02 Plenary meeting, Beijing China, arch 204

56 Pgram pseudowire 2 4 pseudowire label 49 control (sequence) Pgram pseudowire label control (sequence) Pgram For the sake of reduced frame size, Router/Ps 4 and perform PHP, which eliminates unnel labels and 4 (and the Rs in Bridge ). tsn-nfinn-ay-n-he-ife-024-v02.pdf 02 Plenary meeting, Beijing China, arch 204

57 Pgram pseudowire 2 4 One can argue the semantics of the green tunnels. n theory, each tunnel continues to its natural end at Bridge. he control plane may maintain this. But, in the data plane, the tunnel label disappears. o, we will shorten the tunnel in the diagram to match the data plane encapsulation tsn-nfinn-ay-n-he-ife-024-v02.pdf 02 Plenary meeting, Beijing China, arch 204

58 Pgram pseudowire 2 4 A: istener A: Router 4 vlan_identifier 0 Router 4 prepares this thernet frame to transmit the pseudowire packet. : P pseudowire label 49 control (sequence) Pgram tsn-nfinn-ay-n-he-ife-024-v02.pdf 02 Plenary meeting, Beijing China, arch 204

59 A: N 994 A: Router 4 AN tag pseudowire label 49 control (sequence) Pgram Pgram pseudowire 2 4 And Router 4 s N ncaps function produces this. tsn-nfinn-ay-n-he-ife-024-v02.pdf 9 02 Plenary meeting, Beijing China, arch 204

60 Pgram pseudowire 2 4 A: N 200 A: Router AN tag pseudowire label control (sequence) And Pgram pseudowire label is translated by Router s N ncaps into this. Pgram tsn-nfinn-ay-n-he-ife-024-v02.pdf 0 02 Plenary meeting, Beijing China, arch 204

61 Pgram pseudowire A: istener A: Router 4 or vlan_identifier 0 circ_ 994[] or 200[] pseudowire label 49 control (sequence) Pgram 2 4 he N ecaps function exposes the pseudowire and restores the thernet frame parameters. tsn-nfinn-ay-n-he-ife-024-v02.pdf 02 Plenary meeting, Beijing China, arch 204

62 Pgram pseudowire A: istener A: Router 4 or vlan_identifier 0 circuit_ psw 49 or sequence_number : P Pgram 2 4 he erge function has to operate on the circuit and sequence number after the pseudowire ecaps function makes these parameters available (and adds the P therype). tsn-nfinn-ay-n-he-ife-024-v02.pdf 2 02 Plenary meeting, Beijing China, arch 204

63 Pgram pseudowire 2 4 A: istener Output from erge function A: Router 4 or vlan_identifier 0 circuit_ psw 2 sequence_number : P Pgram Pseudowire labels 49 and have been combined into the original pseudowire label 2. here are still two packets! tsn-nfinn-ay-n-he-ife-024-v02.pdf 02 Plenary meeting, Beijing China, arch 204

64 Pgram pseudowire 2 4 A: istener A: Router 4 vlan_identifier 0 circuit_ psw 2 sequence_number : P Pgram he equencing iscard function then deletes the redundant frames, passing whichever (from Router 4, in this case) happens to arrive, first. tsn-nfinn-ay-n-he-ife-024-v02.pdf 4 02 Plenary meeting, Beijing China, arch 204

65 Pgram pseudowire 2 4 A: A: Router 4 AN tag 0 : P Pgram When the frame is put on the wire to istener, the circuit_identifier and sequence_number are discarded, and the remaining parameters make the frame. tsn-nfinn-ay-n-he-ife-024-v02.pdf 02 Plenary meeting, Beijing China, arch 204

66 UARY: 2 4 A: N 40 A: Router A: Router A: Router AN tag 09 A: Router A: N 994 A: : P : P A: Router 4 A: istener : P unnel unnel 4 AN tag A: Router 4 Pseudowire 2 Pseudowire 449 Pseudowire Pseudowire 49 AN tag 0 control (seq) control (seq) control (seq) control (seq) : P Pgram Pgram Pgram Pgram Pgram tsn-nfinn-ay-n-he-ife-024-v02.pdf 02 Plenary meeting, Beijing China, arch 204

67 ariant : 2 4 A: N 40 A: Router A: Router A: Router AN tag 09 A: Router A: N 994 A: : P : P A: Router 4 A: istener : P unnel unnel 4 AN tag A: Router 4 Pseudowire 2 Pseudowire 2 Pseudowire 2 Pseudowire 2 AN tag 0 control (seq) control (seq) control (seq) control (seq) : P Pgram Pgram Pgram Pgram Pgram tsn-nfinn-ay-n-he-ife-024-v02.pdf 02 Plenary meeting, Beijing China, arch 204

68 ariant : 2 4 Note that the plit function is still present, in this case, because pseudowire duplication is not a function that is built into the data plane. t does not create new pseudowire labels, though. But, the erge function is now a no-op. tsn-nfinn-ay-n-he-ife-024-v02.pdf 02 Plenary meeting, Beijing China, arch 204

69 tsn-nfinn-ay-n-he-ife-024-v02.pdf 02 Plenary meeting, Beijing China, arch 204 9

70 2 4 gnoring the lower layers, for a moment, we have the pair in alker peering with the pair in Bridge. tsn-nfinn-ay-n-he-ife-024-v02.pdf 0 02 Plenary meeting, Beijing China, arch 204

71 2 4 pseudowire label 49 control (sequence) Pgram n the left-hand world, we want the Circuit ncaps/ecaps to be an Pgram pseudowire, because it is the natural format for a router. tsn-nfinn-ay-n-he-ife-024-v02.pdf 02 Plenary meeting, Beijing China, arch 204

72 2 4 n the right-hand world, we want the Circuit ncaps/ecaps to be the erialized N encaps, because it is the natural format for a Bridge. A: N 40 A: Router 4 AN tag 2 : N eq equence # : P Pgram tsn-nfinn-ay-n-he-ife-024-v02.pdf 2 02 Plenary meeting, Beijing China, arch 204

73 2 W 4 W pseudowire label 49 control (sequence) Pgram An nterworking function carries the equence number across the gap. W A: N 40 A: Router 4 AN tag 2 : N eq equence # : P Pgram tsn-nfinn-ay-n-he-ife-024-v02.pdf 02 Plenary meeting, Beijing China, arch 204

74 2 W 4 W he nterworking Functions W enable the N Pseudowire ncaps function and the equenced N ecaps function at the very ends of the network to be peers, just like the equenced N and Pgram pseudowire end-to-end cases. tsn-nfinn-ay-n-he-ife-024-v02.pdf 4 02 Plenary meeting, Beijing China, arch 204

75 alker side Higher layers Pseudowire Circuit ncaps/ecaps istener side Higher layers eq N Circuit ncaps/ecaps We have two differet protocol stacks, pseudowire and sequenced N, that perform essentially the same function. We want them to peer with each other. tsn-nfinn-ay-n-he-ife-024-v02.pdf 02 Plenary meeting, Beijing China, arch 204

76 alker side Higher layers equencing Pseudowire Circuit ncaps/ecaps istener side Higher layers equencing eq N Circuit ncaps/ecaps Note that we are not including the sublayers that act on the sequence numbers. tsn-nfinn-ay-n-he-ife-024-v02.pdf 02 Plenary meeting, Beijing China, arch 204

77 alker side istener side equence- and Circuit-aware Relay Pseudowire Circuit ncaps/ecaps eq N Circuit ncaps/ecaps f we connect these two stacks with a trivial two-port relay that carries the sequence_number and circuit_identifier parameters intact,... tsn-nfinn-ay-n-he-ife-024-v02.pdf 02 Plenary meeting, Beijing China, arch 204

78 Pseudowire / equenced N nterworking function alker side istener side equence- and Circuit-aware Relay W Pseudowire Circuit ncaps/ecaps eq N Circuit ncaps/ecaps... we have an interworking function. We ll show the interworking relay as W, and the whole interworking function as W. tsn-nfinn-ay-n-he-ife-024-v02.pdf 02 Plenary meeting, Beijing China, arch 204

79 P Pseudo / N titching 2 4 Returning to our previous discussion, we were peering Pgram pseudowire encapsulations at both ends. tsn-nfinn-ay-n-he-ife-024-v02.pdf 9 02 Plenary meeting, Beijing China, arch 204

80 P Pseudo / N titching 2 4 On the right hand side, we eliminate the simple N encaps used to carry the pseudowire, and replace the Pgram pseudowire encaps with the equenced N enaps that we want. tsn-nfinn-ay-n-he-ife-024-v02.pdf 0 02 Plenary meeting, Beijing China, arch 204

81 P Pseudo / N titching 2 4 On the left hand side, we supply termination for the Pgram pseudowire encaps used by alker. tsn-nfinn-ay-n-he-ife-024-v02.pdf 02 Plenary meeting, Beijing China, arch 204

82 P Pseudo / N titching W 2 4 W When we add the interworking relay W,the Pgram pseudowire / equenced N titching nterworking Function W cements the gap. tsn-nfinn-ay-n-he-ife-024-v02.pdf 2 02 Plenary meeting, Beijing China, arch 204

83 P Pseudo / N titching W 2 4 W pseudowire label 49 control (sequence) Pgram pseudowire label control (sequence) Pgram At this point in the end-toend Pgram pseudowire description, we had the naked pseudowire packets in Routers 4 and. tsn-nfinn-ay-n-he-ife-024-v02.pdf 02 Plenary meeting, Beijing China, arch 204

84 P Pseudo / N titching 2 W 4 W circuit_ 49/40[2] sequence_number Pgram hese packets are decapsulated. circuit_ /2[0] sequence_number Pgram tsn-nfinn-ay-n-he-ife-024-v02.pdf 4 02 Plenary meeting, Beijing China, arch 204

85 P Pseudo / N titching A: N 40 A: Router 4 AN tag 2 : N eq equence # W 2 4 W And when re-encapsulated by the equenced N ncaps, the packet in Router 4 becomes 40[2]. : P Pgram tsn-nfinn-ay-n-he-ife-024-v02.pdf 02 Plenary meeting, Beijing China, arch 204

86 P Pseudo / N titching A: N 2 A: Router AN tag 0 : N eq equence # : P W 2 4 W And Pgram pseudowire label 4 is translated by Router s nterworking function W into N circuit 2[0]. Pgram tsn-nfinn-ay-n-he-ife-024-v02.pdf 02 Plenary meeting, Beijing China, arch 204

87 A: istener A: Router 4 or vlan_identifier 0 circuit_ 40[2] or 2[0] sequence_number : P Pgram P Pseudo / N titching W 2 4 W he N ecaps function unwraps the circuit_identifier and sequence_number, and restores the thernet frame parameters. tsn-nfinn-ay-n-he-ife-024-v02.pdf 02 Plenary meeting, Beijing China, arch 204

88 P Pseudo / N titching A: istener W 2 4 W Output from erge function A: Router 4 or vlan_identifier 0 circuit_ xyz sequence_number N circuit s 40[2] and 2[0] have been combined, but there are still 2 packets. : P Pgram o Bridge, this is the endto-end circuit from alker. tsn-nfinn-ay-n-he-ife-024-v02.pdf 02 Plenary meeting, Beijing China, arch 204

89 P Pseudo / N titching W 2 4 W A: istener A: Router 4 vlan_identifier 0 : P Pgram he equencing iscard function passes only one of the frames. he circuit_identifier and sequence_number are no longer needed. tsn-nfinn-ay-n-he-ife-024-v02.pdf 9 02 Plenary meeting, Beijing China, arch 204

90 P Pseudo / N titching W 2 4 W A: istener A: Router 4 : P Pgram After discarding the unused parameters and converting the rest to the appropriate frame, this is what is output to istener. tsn-nfinn-ay-n-he-ife-024-v02.pdf Plenary meeting, Beijing China, arch 204

91 UARY: W 2 4 W A: N 40 A: Router A: Router A: N 2 A: Router AN tag 09 A: Router A: Router A: : P : P AN tag 0 : P unnel unnel 4 : N eq A: istener Pseudowire 2 Pseudowire 449 Pseudowire equence # A: Router 4 control (seq) control (seq) control (seq) : P : P Pgram Pgram Pgram Pgram Pgram tsn-nfinn-ay-n-he-ife-024-v02.pdf 9 02 Plenary meeting, Beijing China, arch 204

92 ariant 4: W 2 4 W CRCU A: N 40 A: Router A: Router A: N 2 A: Router AN tag 09 A: Router A: Router A: : P : P AN tag 0 : P unnel unnel 4 : N eq A: istener Pseudowire 2 Pseudowire 2 Pseudowire 2 equence # A: Router 4 control (seq) control (seq) control (seq) : P : P Pgram Pgram Pgram Pgram Pgram tsn-nfinn-ay-n-he-ife-024-v02.pdf Plenary meeting, Beijing China, arch 204

93 ariant : Ω pseudowire label 2 control (sequence) Pgram alker could be dual-homed. n this case, clearly must supply the sequence numbers. he sequence numbers are usually part of the encapsulation. o, terminates the pseudowire, not routers 2 and. tsn-nfinn-ay-n-he-ife-024-v02.pdf 9 02 Plenary meeting, Beijing China, arch 204

94 tsn-nfinn-ay-n-he-ife-024-v02.pdf 02 Plenary meeting, Beijing China, arch

95 HR tagging 2 4 Again, alker is N-aware, istener is not. his time, alker is not AN-aware, istener is AN-aware. n this case, HR and N ncaps and ecaps are combined into a single layer. tsn-nfinn-ay-n-he-ife-024-v02.pdf 9 02 Plenary meeting, Beijing China, arch 204

96 his is not HR. t is the HR format used for a different purpose. his idea may or may not sit well with C CX. his HR-like layer: Connects to a single port, not two. ay use one sequence number variable per circuit, not one per host. (his is debatable.) f the station is AN aware, has the AN tagging below (outside) the HR sublayer. tsn-nfinn-ay-n-he-ife-024-v02.pdf 9 02 Plenary meeting, Beijing China, arch 204

97 host bridge HR Higher ayers equencing Circuit ncaps/ecaps plit / erge Note that this is the layering the top box is alker, and the bottom box is Bridge. HR combines the Circuit ncaps/ecaps and equencing functions. t also encapsulates the destination AC address which, as we will see, is not really very useful. tsn-nfinn-ay-n-he-ife-024-v02.pdf 9 02 Plenary meeting, Beijing China, arch 204

98 HR-like tagging 2 4 A: A: circuit_identifier : P Pgram alker s stack is not ANaware. his is what the frame is when it hits the N ncaps layer. Note that Bridge would normally add a AN 0 tag to this frame. tsn-nfinn-ay-n-he-ife-024-v02.pdf 9 02 Plenary meeting, Beijing China, arch 204

99 HR-like tagging 2 4 A: N 4 A: AN tag 99 HR therype pid, length, sequence A: he equencing and combined HR/N ncaps layer create a sequence number and add a N/HR tag. therype ata tsn-nfinn-ay-n-he-ife-024-v02.pdf Plenary meeting, Beijing China, arch 204

100 HR-like tagging 2 4 A: N 40 A: AN tag 2 HR therype pid, length, sequence A: therype ata he plit function operates on the N header, for the path, and the HR header, for the sequence number. (he pid field includes a path A / path B flag that intended to be different between the two paths. We may or may not follow that usage.) tsn-nfinn-ay-n-he-ife-024-v02.pdf Plenary meeting, Beijing China, arch 204

101 HR-like tagging 2 4 A: N 2 A: AN tag 0 HR therype pid, length, sequence A: therype ata he other path gets a different A and AN tag. Note that the plit function split N 4[99] into N 40[2] and 2[0]. tsn-nfinn-ay-n-he-ife-024-v02.pdf 0 02 Plenary meeting, Beijing China, arch 204

102 HR-like tagging 2 4 A: istener A: alker vlan_identifier 0 circuit_ 40[2] or 2[0] sequence_number he erge function operates on the circuit_identifier exposed by the decapsulation function therype ata tsn-nfinn-ay-n-he-ife-024-v02.pdf Plenary meeting, Beijing China, arch 204

103 HR-like tagging 2 4 A: istener A: alker vlan_identifier 0 circuit_ 4[99] sequence_number therype ata Output from erge function is the original 4[99] tunnel that originated from Bridge. wo packets are present until the equencing iscard function discards one. tsn-nfinn-ay-n-he-ife-024-v02.pdf 0 02 Plenary meeting, Beijing China, arch 204

104 HR-like tagging 2 4 A: A: AN tag 0 : P Pgram And this is delivered on the wire. tsn-nfinn-ay-n-he-ife-024-v02.pdf Plenary meeting, Beijing China, arch 204

105 ummary: 2 4 A: N 4 A: N 40 A: N 2 A: A: A: AN tag 99 AN tag 2 AN tag 0 HR therype pid, length, seq A: therype ata HR therype pid, length, seq A: therype ata HR therype pid, length, pid, sequence length, seq A: therype ata A: A: AN tag 0 : P Pgram tsn-nfinn-ay-n-he-ife-024-v02.pdf 0 02 Plenary meeting, Beijing China, arch 204

106 ariant : Ω pseudowire label 2 control (sequence) Pgram alker could be dual-homed. n this case, clearly must supply the sequence numbers. he sequence numbers are usually part of the encapsulation. o, terminates the pseudowire, not routers 2 and. tsn-nfinn-ay-n-he-ife-024-v02.pdf 0 02 Plenary meeting, Beijing China, arch 204

107 PRP tagging 2 4 A: N 2 A: AN tag 0 therype ata pid, length, sequence HR therype PRP would work similarly. his could be useful to interoperate with existing deployments. A big issue with the PRP trailer is that you can t tell what it s position is in the tag layering. tsn-nfinn-ay-n-he-ife-024-v02.pdf 0 02 Plenary meeting, Beijing China, arch 204

108 ummary: 2 4 A: N 4 A: N 40 A: N 2 A: A: A: AN tag 99 therype ata pid, length, seq HR therype AN tag 2 therype ata pid, length, seq HR therype AN tag 0 therype ata pid, length, seq HR therype A: A: AN tag 0 : P Pgram tsn-nfinn-ay-n-he-ife-024-v02.pdf 0 02 Plenary meeting, Beijing China, arch 204

109 tsn-nfinn-ay-n-he-ife-024-v02.pdf 02 Plenary meeting, Beijing China, arch

110 2 4 You can always create end-to-end encapsulated thernet circuits using, for example, thernet pseudowire and/or PBB- AC-in-AC in the standard ways it s done, today. tsn-nfinn-ay-n-he-ife-024-v02.pdf 0 02 Plenary meeting, Beijing China, arch 204

111 2 4 he catch is that the alker has a separate thernet port per N flow. his is not compatible with a simple P stack; each port needs its own P address. tsn-nfinn-ay-n-he-ife-024-v02.pdf 02 Plenary meeting, Beijing China, arch 204

112 2 4 here are solutions to this classic multihomed P host problem. t would take some effort to make them compatible with our simple o purpose. tsn-nfinn-ay-n-he-ife-024-v02.pdf 2 02 Plenary meeting, Beijing China, arch 204

113 2 4 And, of course, it still begs the question, How are these packet encapsulated? Again, there are many standard answers to that question. tsn-nfinn-ay-n-he-ife-024-v02.pdf 02 Plenary meeting, Beijing China, arch 204

114 tsn-nfinn-ay-n-he-ife-024-v02.pdf 02 Plenary meeting, Beijing China, arch 204 4

115 Assume for a moment that we do not need to transmit multiple copies on different paths, so we do not need the equencing functions. hen, all we need is a per-flow circuit_identifier on every packet, at both 2 and. P ulticast can supply this, even if it cannot supply a sequence number. tsn-nfinn-ay-n-he-ife-024-v02.pdf 02 Plenary meeting, Beijing China, arch 204

116 n general, an P multicast flow is identified by the ulticast P destination address and the (unicast) P source address. here is a 2: mapping of P multicast addresses to AC Group As. tsn-nfinn-ay-n-he-ife-024-v02.pdf 02 Plenary meeting, Beijing China, arch 204

117 f the network administrator and protocols can ensure that the P multicast addresses are unique over the flows, no N encapsulation is necessary. Otherwise, the usual N encapsulation will solve the Bridges problems with multicast, and the Routers can easily identify the streams to apply N o. tsn-nfinn-ay-n-he-ife-024-v02.pdf 02 Plenary meeting, Beijing China, arch 204

118 2 4 he normal P Group address and AN may or may not be sufficient for Bridged N networks, but the N encapsulation fixes this. A: Group Z? A: Group Z A: : P C Pgram A: Router AN tag 09? : P C Pgram A: Group Z? A: Router 4 AN tag 0 : P Pgram tsn-nfinn-ay-n-he-ife-024-v02.pdf 02 Plenary meeting, Beijing China, arch 204

119 And, if the protocol carried in the P ulticast packet has a sequence number, then of course, the P ulticast format is sufficient, in the data plane, for seamless redundancy, as well. tsn-nfinn-ay-n-he-ife-024-v02.pdf 9 02 Plenary meeting, Beijing China, arch 204

120 2 4 he P multicast control protocols, of course, would need work. A: Group Z A: : P C Pgram A: Group Z? A: Router AN tag 09? : P C Pgram A: Group Z? A: Router 4 AN tag 0 : P Pgram tsn-nfinn-ay-n-he-ife-024-v02.pdf Plenary meeting, Beijing China, arch 204

121 tsn-nfinn-ay-n-he-ife-024-v02.pdf 02 Plenary meeting, Beijing China, arch 204 2

122 he layering scheme in tsn-nfinn-2-ata-plane-024-v04 works. here are existing protocols for carrying both all-2 and mixed 2/ N circuits. here are other possibilities for creating N circuits: xan, P, and dozens of as-yet proprietary schemes. A new 02. sequence number tag can handle thernet end-to-end seamless redundancy. ixed 2/ seamless redundancy requires either: electing a single end-to-end 2+ split/merge format (e.g. pseudowire); or An interworking function between and 2 split/merge technologies; or Creating explicit end-to-end thernet tunnels. tsn-nfinn-ay-n-he-ife-024-v02.pdf Plenary meeting, Beijing China, arch 204

123 hank you.

Layering for the TSN Layer 2 Data Plane

Layering for the TSN Layer 2 Data Plane Layering for the TSN Layer 2 Data Plane Norman Finn Version 3 Feb. 17, 2014 tsn-nfinn-l2-data-plane-0214-v03.pdf 1 At the AVnu face-to-face meeting in December, Norm Finn made presentations on the subject

More information

How many VLAN IDs are required for 802.1CB seamless redundancy?

How many VLAN IDs are required for 802.1CB seamless redundancy? How many AN IDs are required for 802.1CB seamless redundancy? Norman Finn ersion 2 Mar. 4, 2014 cb-nfinn-how-many-ans-0214-v02.pdf 1 This presentation is cb-nfinn-how-many- ANs-0214-v02.pdf. It is based

More information

Layering for the TSN Layer 3 Data Plane

Layering for the TSN Layer 3 Data Plane Layering for the TSN Layer 3 Data Plane Norman Finn, Peter Jones, Rudy Klecka, Pascal Thubert Cisco Systems Version 3 Mar. 3, 2014 tsn-nfinn-l3-data-plane-0214-v03.pdf 1 This is tsn-nfinn-l3-data-plane-0214-v03.

More information

Layering for the TSN Layer 3 Data Plane

Layering for the TSN Layer 3 Data Plane Layering for the TSN Layer 3 Data Plane Norman Finn, Rudy Klecka, Pascal Thubert, Cisco Systems Version 2 Feb. 17, 2014 tsn-nfinn-l3-data-plane-0214-v02.pdf 1 This is part 2 of a two-part presentation.

More information

Scheduled queues, UBS, CQF, and Input Gates

Scheduled queues, UBS, CQF, and Input Gates Scheduled queues, UBS, CQF, and Input Gates Norman Finn Cisco Systems V03 January 12, 2015 new-nfinn-input-gates-0115-v03.pdf IEEE 802.2 interim, Atlanta, January, 2015 1 1. Building a robust network has

More information

Suggestions for P802.1Qcc Inputs and Outputs

Suggestions for P802.1Qcc Inputs and Outputs Suggestions for P802.1Qcc Inputs and Outputs Norman Finn Cisco Systems Version 1 Mar. 16, 2014 cc-nfinn-inputs-outputs-0314-v01 1 This is cc-nfinn-inputs-outputs-0314-v01. It is based on tsn-nfinn-l2-data-plane-0214-

More information

Changes to 802.1Q necessary for 802.1Qbz (bridging media)

Changes to 802.1Q necessary for 802.1Qbz (bridging media) Changes to 802.1Q necessary for 802.1Qbz (bridging 802.11 media) Norman Finn March, 2013 v01 bz-nfinn-802-1q-changes-0313-v01.pdf 1 2010 Cisco and/or its affiliates. All rights reserved. Cisco Confidential

More information

SRP and non-1722 applications

SRP and non-1722 applications SRP and non-1722 applications Norman Finn March, 2013 v01 new-tsn-nfinn-non-1722-srp-0313-v01.pdf 1 When I try to use SRP (and AVB, in general) with applications not using IEEE 1722, there are problems.

More information

DetNet. Flow Definition and Identification, Features and Mapping to/from TSN. DetNet TSN joint workshop IETF / IEEE 802, Bangkok

DetNet. Flow Definition and Identification, Features and Mapping to/from TSN. DetNet TSN joint workshop IETF / IEEE 802, Bangkok DetNet Flow Definition and Identification, Features and Mapping to/from TSN DetNet TSN joint workshop IETF / IEEE 802, Bangkok Balázs Varga 2018-11-11 DetNet - Data plane and related functions Page 1 Balázs

More information

Scheduled queues, UBS, CQF, and Input Gates

Scheduled queues, UBS, CQF, and Input Gates Scheduled queues, UBS, CQF, and Input Gates Norman Finn Cisco Systems V04 January 14, 2015 new-nfinn-input-gates-0115-v04.pdf IEEE 802.2 interim, Atlanta, January, 2015 1 1. Building a robust network has

More information

CB Seamless Failover. How to separate multiple copies of one stream?

CB Seamless Failover. How to separate multiple copies of one stream? How to separate multiple copies of one stream? CB Seamless Failover IEEE 802.3 Plenary Session Dallas Marcel Kiessling, Siemens AG Franz-Josef Goetz, Siemens AG Goal of this presentation his presentation

More information

Simplifying Seamless Redundancy

Simplifying Seamless Redundancy Simplifying Seamless Redundancy Norman Finn Cisco Systems January 18, 2016 IEEE 802.1 interim, Atlanta GA USA, Jan. 2016 cb-finn-simplifying-seamless-redundancy-0116-v01.pdf 1 This document supports a

More information

Proposal for P802.1Qcc Control Flows

Proposal for P802.1Qcc Control Flows Proposal for P802.1Qcc Control Flows Norman Finn Cisco Systems Version 1 Apr. 9, 2014 cc-nfinn-control-flows-0414-v01 1 This is cc-nfinn-control-flows-0414-v01. It is based on cc-nfinn-inputs-outputs-0314-

More information

CS519: Computer Networks. Lecture 1 (part 2): Jan 28, 2004 Intro to Computer Networking

CS519: Computer Networks. Lecture 1 (part 2): Jan 28, 2004 Intro to Computer Networking : Computer Networks Lecture 1 (part 2): Jan 28, 2004 Intro to Computer Networking Remember this picture? How did the switch know to forward some packets to B and some to D? From the address in the packet

More information

LARGE SCALE IP ROUTING LECTURE BY SEBASTIAN GRAF

LARGE SCALE IP ROUTING LECTURE BY SEBASTIAN GRAF LARGE SCALE IP ROUTING LECTURE BY SEBASTIAN GRAF MODULE 07 - MPLS BASED LAYER 2 SERVICES 1 by Xantaro MPLS BASED LAYER 2 VPNS USING MPLS FOR POINT-TO-POINT LAYER 2 SERVICES 2 by Xantaro Why are Layer-2

More information

Cisco Systems, Inc. Norman Finn. July 9, /12. Class of Service in Class of Service in Norman Finn Cisco Systems

Cisco Systems, Inc. Norman Finn. July 9, /12. Class of Service in Class of Service in Norman Finn Cisco Systems Class of Service in 802.1 Norman Finn Cisco Systems, Inc. July 9, 1996 1/12 CoS Bridging Example sw2 16 Mb T-R 100 Mb Ether sw3 sw1 10 Mb Ether FDDI X Y 100 Mb and 10 Mb Ethernet prevent passing access

More information

P802.1Qbz + P802.11ak Proposal for Division of Work

P802.1Qbz + P802.11ak Proposal for Division of Work P802.1Qbz + P802.11ak Proposal for Division of Work Norman Finn May 6, 2013 1 This document is also available on the 802.11 document system (IEEE Mentor) as document 11-13/406. 2 Portal AP-AP link B AP1

More information

Station Bridges

Station Bridges 802.11 Station Bridges A path to standardization of 802.11 non-ap s that are bridge ports Rev. 1 Norman Finn nfinn@cisco.com new-nfinn--bridge-0309-v01 1 References This presentation is available at: http://www.ieee802.org/1/files/public/docs2009/new-nfinn-bridge-0309-v01.ppt

More information

DetNet/TSN Flow/QoS mapping between DetNet and TSN. Norman Finn Huawei Technologies Co, Ldt

DetNet/TSN Flow/QoS mapping between DetNet and TSN. Norman Finn Huawei Technologies Co, Ldt DetNet/TSN Flow/QoS mapping between DetNet and TSN Norman Finn Huawei Technologies Co, Ldt Mapping between DetNet and TSN Several areas subject to mapping Terminology Data plane: QoS execution Data plane:

More information

Lab 1: Static MPLS LSP-RTX4-RTX1 LSP-RTX1-RTX4 LSP-RTX3-RTX2 LSP-RTX2-RTX3

Lab 1: Static MPLS LSP-RTX4-RTX1 LSP-RTX1-RTX4 LSP-RTX3-RTX2 LSP-RTX2-RTX3 Lab 1: Static MPLS First lab gives a basic understanding of MPLS label swapping No signaling manually assign labels like static routing Understand configuration, forwarding tables, and debugging of MPLS

More information

An SCTP-Protocol Data Unit with several chunks

An SCTP-Protocol Data Unit with several chunks SCTP for Beginners Section 2 SCTP Packets he protocol data units (PDU) of SCTP are called SCTP packets. If SCTP runs over IP (as described in RFC2960 ), an SCTP packet forms the payload of an IP packet.

More information

More Details on Resource Allocation Protocol (RAP)

More Details on Resource Allocation Protocol (RAP) More Details on Resource Allocation Protocol (RAP) Feng Chen, Franz-Josef Götz, Jürgen Schmitt Siemens AG July 2017 Siemens AG 2017 Recap Motivations for a new Resource Allocation Protocol (RAP): (see

More information

This presentation provides a high level overview of Gen Z unicast and multicast operations.

This presentation provides a high level overview of Gen Z unicast and multicast operations. This presentation provides a high level overview of Gen Z unicast and multicast operations. 1 2 Gen Z specifies two packet types: Link local packets that are exchanged between two interfaces across a single

More information

Overview. Overview. OTV Fundamentals. OTV Terms. This chapter provides an overview for Overlay Transport Virtualization (OTV) on Cisco NX-OS devices.

Overview. Overview. OTV Fundamentals. OTV Terms. This chapter provides an overview for Overlay Transport Virtualization (OTV) on Cisco NX-OS devices. This chapter provides an overview for Overlay Transport Virtualization (OTV) on Cisco NX-OS devices., page 1 Sample Topologies, page 6 OTV is a MAC-in-IP method that extends Layer 2 connectivity across

More information

AP Bridges and MSTP

AP Bridges and MSTP 802.11 A Bridges and MST Two MST problems are encountered when non-a 802.11 s can be bridges Rev. 1 Norman Finn nfinn@cisco.com 1 References This presentation is available at: http://www.ieee802.org/1/files/public/docs2008/new-nfinnap-bridge-mstp-1108-v1

More information

Locator ID Separation Protocol (LISP) Overview

Locator ID Separation Protocol (LISP) Overview Locator ID Separation Protocol (LISP) is a network architecture and protocol that implements the use of two namespaces instead of a single IP address: Endpoint identifiers (EIDs) assigned to end hosts.

More information

Failure rates and P802.1CB

Failure rates and P802.1CB Failure rates and P0.CB Norman Finn Rev November, 0 cb-nfinn-packet-loss-ratio-0--v0.pdf IEEE plenary Dallas TX November 0 cb-nfinn-packet-loss-ratio-0--v0.pdf IEEE plenary Dallas TX November 0 Source

More information

Optical + Ethernet: Converging the Transport Network. An Overview

Optical + Ethernet: Converging the Transport Network. An Overview Optical + Ethernet: Converging the Transport Network An Overview Trends Regional Optical Networks for Research Locally-managed fiber termination points Locally-organized peering relationships Locally-controlled

More information

Data Plane for Resilient Network Interconnect. János Farkas Balázs Péter Gerő Panagiotis Saltsidis

Data Plane for Resilient Network Interconnect. János Farkas Balázs Péter Gerő Panagiotis Saltsidis Data Plane for Resilient Network nterconnect János Farkas alázs Péter Gerő Panagiotis altsidis ntroduction Data paths do not depend on the applied control protocol How to implement the data paths within

More information

Computer Network Architectures and Multimedia. Guy Leduc. Chapter 2 MPLS networks. Chapter 2: MPLS

Computer Network Architectures and Multimedia. Guy Leduc. Chapter 2 MPLS networks. Chapter 2: MPLS Computer Network Architectures and Multimedia Guy Leduc Chapter 2 MPLS networks Chapter based on Section 5.5 of Computer Networking: A Top Down Approach, 6 th edition. Jim Kurose, Keith Ross Addison-Wesley,

More information

The MAC Address Format

The MAC Address Format Directing data is what addressing is all about. At the Data Link layer, this is done by pointing PDUs to the destination MAC address for delivery of a frame within a LAN. The MAC address is the number

More information

Table of Contents Chapter 1 Tunneling Configuration

Table of Contents Chapter 1 Tunneling Configuration Table of Contents Table of Contents... 1-1 1.1 Introduction to Tunneling... 1-1 1.1.1 IPv6 over IPv4 Tunnel... 1-2 1.1.2 IPv4 over IPv4 Tunnel... 1-7 1.2 Tunneling Configuration Task List... 1-8 1.3 Configuring

More information

IEEE Time-Sensitive Networking (TSN)

IEEE Time-Sensitive Networking (TSN) IEEE 802.1 Time-Sensitive Networking (TSN) Norman Finn, IEEE 802.1CB, IEEE 802.1CS Editor Huawei Technologies Co. Ltd norman.finn@mail01.huawei.com Geneva, 27 January, 2018 Before We Start This presentation

More information

Goals and topics. Verkkomedian perusteet Fundamentals of Network Media T Circuit switching networks. Topics. Packet-switching networks

Goals and topics. Verkkomedian perusteet Fundamentals of Network Media T Circuit switching networks. Topics. Packet-switching networks Verkkomedian perusteet Fundamentals of Media T-110.250 19.2.2002 Antti Ylä-Jääski 19.2.2002 / AYJ lide 1 Goals and topics protocols Discuss how packet-switching networks differ from circuit switching networks.

More information

More Details on Resource Allocation Protocol (RAP)

More Details on Resource Allocation Protocol (RAP) More Details on Resource Allocation Protocol (RAP) Feng Chen, Franz-Josef Götz, Jürgen Schmitt Siemens AG July 2017 Siemens AG 2017 Recap Motivations for a new Resource Allocation Protocol (RAP): (see

More information

Ahead of the challenge, ahead of the change. Beyond classical substation How seamless communication networks can be used in special applications

Ahead of the challenge, ahead of the change. Beyond classical substation How seamless communication networks can be used in special applications Ahead of the challenge, ahead of the change Beyond classical substation How seamless communication networks can be used in special applications siemens.com/energy-management Agenda Today s reliability

More information

Lecture 2: Internet Architecture

Lecture 2: Internet Architecture CS 3700 Networks and Distributed Systems Lecture 2: Internet Architecture Revised 1/6/14 Organizing Network Functionality 2 Organizing Network Functionality 2 Networks are built from many components! Networking

More information

Network Working Group. Category: Informational Bay Networks Inc. September 1997

Network Working Group. Category: Informational Bay Networks Inc. September 1997 Network Working Group Request for Comments: 2185 Category: Informational R. Callon Cascade Communications Co. D. Haskin Bay Networks Inc. September 1997 Routing Aspects Of IPv6 Transition Status of this

More information

DRNI: State of the Model Wars

DRNI: State of the Model Wars DRNI: State of the Model Wars Version 01 Stephen Haddock January 18, 2012 1 Coming out of the November meeting it seemed as though Norm, Maarten, and I were converging in our respective DRNI models. Since

More information

ENTERPRISE MPLS. Kireeti Kompella

ENTERPRISE MPLS. Kireeti Kompella ENTERPRISE MPLS Kireeti Kompella AGENDA The New VLAN Protocol Suite Signaling Labels Hierarchy Signaling Advanced Topics Layer 2 or Layer 3? Resilience and End-to-end Service Restoration Multicast ECMP

More information

CS4700/5700: Network fundamentals

CS4700/5700: Network fundamentals Cristina Nita-Rotaru CS4700/5700: Network fundamentals. 1: Organizing network functionality } Networks are built from many components } Networking technologies } Ethernet, Wifi, Bluetooth, Fiber Optic,

More information

Internet Engineering Task Force (IETF) ISSN: A. Sajassi Cisco J. Uttaro AT&T May 2018

Internet Engineering Task Force (IETF) ISSN: A. Sajassi Cisco J. Uttaro AT&T May 2018 Internet Engineering Task Force (IETF) Request for Comments: 8388 Category: Informational ISSN: 2070-1721 J. Rabadan, Ed. S. Palislamovic W. Henderickx Nokia A. Sajassi Cisco J. Uttaro AT&T May 2018 Usage

More information

Configuring Virtual Private LAN Service (VPLS) and VPLS BGP-Based Autodiscovery

Configuring Virtual Private LAN Service (VPLS) and VPLS BGP-Based Autodiscovery Configuring Virtual Private LAN Service (VPLS) and VPLS BGP-Based Autodiscovery Finding Feature Information, page 1 Configuring VPLS, page 1 Configuring VPLS BGP-based Autodiscovery, page 17 Finding Feature

More information

TRILL Transparent Transport over MPLS

TRILL Transparent Transport over MPLS TRILL Transparent Transport over MPLS draft-muks-trill-transport-over-mpls- 00 Mohammad Umair, Kingston Smiler, Donald Eastlake, Lucy Yong Overview This draft covers two problems as follows. Providing

More information

EIGRP Over the Top. Finding Feature Information. Information About EIGRP Over the Top. EIGRP Over the Top Overview

EIGRP Over the Top. Finding Feature Information. Information About EIGRP Over the Top. EIGRP Over the Top Overview The feature enables a single end-to-end routing domain between two or more Enhanced Interior Gateway Routing Protocol (EIGRP) sites that are connected using a private or a public WAN connection. This module

More information

MPLS VPN. 5 ian 2010

MPLS VPN. 5 ian 2010 MPLS VPN 5 ian 2010 What this lecture is about: IP CEF MPLS architecture What is MPLS? MPLS labels Packet forwarding in MPLS MPLS VPNs 3 IP CEF & MPLS Overview How does a router forward packets? Process

More information

Configuration and Management of Networks. Pedro Amaral

Configuration and Management of Networks. Pedro Amaral Configuration and Management of Networks Pedro Amaral 2012 Service Provider Networks Carrier grade networks that carry customers traffic: Triple play residential customers Voice High Speed Internet Broadcast

More information

AToM (Any Transport over MPLS)

AToM (Any Transport over MPLS) I N D E X A AAL5 over MPLS operation, 459 460 configuration, 462 463 flowchart configuration, 461 PE router, 461 provider router, 461 verification, 463 465 AAL5 to VLAN Interworking, 515 517 AC (Attachment

More information

Resilient Network Interconnect using Distributed Link Aggregation Version 3. Stephen Haddock Extreme Networks September 15, 2010

Resilient Network Interconnect using Distributed Link Aggregation Version 3. Stephen Haddock Extreme Networks September 15, 2010 Resilient Network Interconnect using Distributed Link Aggregation Version 3 Stephen Haddock Extreme Networks September 15, 2010 1 Premise and Basic Questions Adapting Link Aggregation to be a Resilient

More information

IETF YANG models for VLAN interface classification. draft-wilton-netmod-intf-vlan-yang Robert Wilton (Cisco)

IETF YANG models for VLAN interface classification. draft-wilton-netmod-intf-vlan-yang Robert Wilton (Cisco) IETF YANG models for VLAN interface classification draft-wilton-netmod-intf-vlan-yang Robert Wilton (Cisco) rwilton@cisco.com Presentation Objectives To explain what this IETF model is trying to achieve

More information

Station Bridges

Station Bridges 802.11 Station Bridges Three solutions to the problem of 802.11 s that are also s Rev. 2 Norman Finn nfinn@cisco.com 1 References This presentation is available at: http://www.ieee802.org/1/files/public/docs2008/avb-nfinn-

More information

ET4254 Communications and Networking 1

ET4254 Communications and Networking 1 Topic 9 Internet Protocols Aims:- basic protocol functions internetworking principles connectionless internetworking IP IPv6 IPSec 1 Protocol Functions have a small set of functions that form basis of

More information

An Update on Bridging Technologies. Change and evolution: Why, what, and how. Mick Seaman

An Update on Bridging Technologies. Change and evolution: Why, what, and how. Mick Seaman An Update on Bridging Technologies Change and evolution: Why, what, and how Mick Seaman mick_seaman@ieee.org Agenda Why has bridging evolved Bridging basics What has changed/is changing And how! 802 July

More information

Growth. Individual departments in a university buy LANs for their own machines and eventually want to interconnect with other campus LANs.

Growth. Individual departments in a university buy LANs for their own machines and eventually want to interconnect with other campus LANs. Internetworking Multiple networks are a fact of life: Growth. Individual departments in a university buy LANs for their own machines and eventually want to interconnect with other campus LANs. Fault isolation,

More information

Tag Switching. Background. Tag-Switching Architecture. Forwarding Component CHAPTER

Tag Switching. Background. Tag-Switching Architecture. Forwarding Component CHAPTER CHAPTER 23 Tag Switching Background Rapid changes in the type (and quantity) of traffic handled by the Internet and the explosion in the number of Internet users is putting an unprecedented strain on the

More information

WiNG 5.x How-To Guide

WiNG 5.x How-To Guide WiNG 5.x How-To Guide Tunneling Remote Traffic using L2TPv3 Part No. TME-08-2012-01 Rev. A MOTOROLA, MOTO, MOTOROLA SOLUTIONS and the Stylized M Logo are trademarks or registered trademarks of Motorola

More information

4.2 Multicast IP supports multicast to support one-to-many (radio, news, IP multicast was originally a many-to-many (any source MC or

4.2 Multicast IP supports multicast to support one-to-many (radio, news, IP multicast was originally a many-to-many (any source MC or CS475 Networks Lecture 14 Chapter 4 Advanced Internetworking Assignments Reading for Lecture 15: Sections 5.1-5.2 Homework 5, Wireshark Project 3 posted, due next Thursday; Programming Project 3 posted,

More information

IP/LDP FAST PROTECTION SCHEMES

IP/LDP FAST PROTECTION SCHEMES IP/LDP FAST PROTECTION SCHEMES PL-NOG, OCT 203 Julian Lucek AGENDA Loop-Free Alternate (LFA) brief review Improving LFA coverage Remote LFA (rlfa) Directed forwarding label LFA with automatically created

More information

Previous Lecture. Link Layer & Network Layer. Link Layer. This Lecture. Framing. Sending bits. Chapter 7.C and 7.D

Previous Lecture. Link Layer & Network Layer. Link Layer. This Lecture. Framing. Sending bits. Chapter 7.C and 7.D hapter 7. and 7. Previous Lecture Layer & Network Layer The network is organized into layers Prof. ina Katabi Some slides are from lectures by Nick Mckeown, Ion Stoica, Frans Kaashoek, Hari alakrishnan,

More information

TCP/IP protocol suite

TCP/IP protocol suite TCP/IP protocol suite The TCP/IP protocol suite was developed prior to the OSI model. Therefore, the layers in the TCP/IP protocol suite do not match exactly with those in the OSI model. The original TCP/IP

More information

Internet Engineering Task Force (IETF) Category: Experimental Columbia U. ISSN: Samsung J. Bang Samsung AIT March 2011

Internet Engineering Task Force (IETF) Category: Experimental Columbia U. ISSN: Samsung J. Bang Samsung AIT March 2011 Internet Engineering Task Force (IETF) C. Shen Request for Comments: 5979 H. Schulzrinne Category: Experimental Columbia U. ISSN: 2070-1721 S. Lee Samsung J. Bang Samsung AIT March 2011 Abstract NSIS Operation

More information

Contents. EVPN overview 1

Contents. EVPN overview 1 Contents EVPN overview 1 EVPN network model 1 MP-BGP extension for EVPN 2 Configuration automation 3 Assignment of traffic to VXLANs 3 Traffic from the local site to a remote site 3 Traffic from a remote

More information

Managing and Securing Computer Networks. Guy Leduc. Chapter 2: Software-Defined Networks (SDN) Chapter 2. Chapter goals:

Managing and Securing Computer Networks. Guy Leduc. Chapter 2: Software-Defined Networks (SDN) Chapter 2. Chapter goals: Managing and Securing Computer Networks Guy Leduc Chapter 2: Software-Defined Networks (SDN) Mainly based on: Computer Networks and Internets, 6 th Edition Douglas E. Comer Pearson Education, 2015 (Chapter

More information

FRS IPO CONFIGURATIONS

FRS IPO CONFIGURATIONS Document ID: FLXN110 FRS IPO CONFIGURATIONS Application Note This document could contain technical inaccuracies or typographical errors. Flexibilis Oy may make changes in the product described in this

More information

MPLS Networks: Design and Routing Functions

MPLS Networks: Design and Routing Functions MPLS Networks: Design and Routing Functions Course Description This course provides an understanding of how MPLS works its advantages and limitations and how it can be deployed to provide effective services

More information

What LinkSec Should Know About Bridges Norman Finn

What LinkSec Should Know About Bridges Norman Finn What LinkSec Should Know About Bridges Norman Finn What LinkSec Should Know About Bridges Rev. 2 Norman Finn, Cisco Systems IEEE 802 LinkSec SG 1/20 What Do Bridges Do? (1) A network of bridges emulates

More information

ECE4110 Internetwork Programming. Introduction and Overview

ECE4110 Internetwork Programming. Introduction and Overview ECE4110 Internetwork Programming Introduction and Overview 1 EXAMPLE GENERAL NETWORK ALGORITHM Listen to wire Are signals detected Detect a preamble Yes Read Destination Address No data carrying or noise?

More information

Routing without tears: Bridging without danger

Routing without tears: Bridging without danger Routing without tears: Bridging without danger Radia Perlman Sun Microsystems Laboratories Radia.Perlman@sun.com 1 Before we get to RBridges Let s sort out bridges, routers, switches... 2 What are bridges,

More information

Intended status: Standards Track. Cisco Systems October 22, 2018

Intended status: Standards Track. Cisco Systems October 22, 2018 BESS WorkGroup Internet-Draft Intended status: Standards Track Expires: April 25, 2019 Ali. Sajassi Mankamana. Mishra Samir. Thoria Patrice. Brissette Cisco Systems October 22, 2018 AC-Aware Bundling Service

More information

Operation Manual MPLS VLL. Table of Contents

Operation Manual MPLS VLL. Table of Contents Table of Contents Table of Contents... 1-1 1.1 MPLS VLL Overview... 1-2 1.1.1 Concepts in MPLS VLL... 1-2 1.1.2 Introduction to MPLS VLL... 1-2 1.1.3 Packet Forwarding... 1-3 1.1.4 Implementation... 1-4

More information

MPLS AToM Overview. Documentation Specifics. Feature Overview

MPLS AToM Overview. Documentation Specifics. Feature Overview MPLS AToM Overview This document provides an introduction to MPLS AToM and includes the following sections: Documentation Specifics, page 14 Feature Overview, page 14 Benefits, page 26 What To Do Next,

More information

Multiple 802.1Q Spanning Trees

Multiple 802.1Q Spanning Trees 802.1 HILI Working Group IEEE LMSC Meeting, July 1998 Norman Finn Michael Smith July 7, 1998 1/16 Outline Why use one spanning tree or more than one? How many spanning trees? How to encapsulate BPDUs?

More information

EEC-682/782 Computer Networks I

EEC-682/782 Computer Networks I EEC-682/782 Computer Networks I Lecture 16 Wenbing Zhao w.zhao1@csuohio.edu http://academic.csuohio.edu/zhao_w/teaching/eec682.htm (Lecture nodes are based on materials supplied by Dr. Louise Moser at

More information

CSE 123: Computer Networks

CSE 123: Computer Networks CSE 123: Computer Networks Homework 3 Out: 11/19 Due: 11/26 Instructions 1. Turn in a physical copy at the beginning of the class on 11/26 2. Ensure the HW cover page has the following information clearly

More information

Multiple I-tag Registration Protocol

Multiple I-tag Registration Protocol Multiple I-tag Registration Protocol Multiple I-tag Registration Protocol (MIRP) for signaling among I-components Version 1 Norman Finn Cisco Systems IEEE 802.1 interim, Los Gatos, California, January-February,

More information

MPLS опорни мрежи MPLS core networks

MPLS опорни мрежи MPLS core networks MPLS опорни мрежи MPLS core networks Николай Милованов/Nikolay Milovanov http://niau.org Objectives Identify the drawbacks of traditional IP routing Describe basic MPLS concepts and LSR types. MPLS Labels

More information

MPLS LSP Ping Traceroute for LDP TE and LSP Ping for VCCV

MPLS LSP Ping Traceroute for LDP TE and LSP Ping for VCCV MPLS LSP Ping Traceroute for LDP TE and LSP Ping for VCCV The MPLS LSP Ping/Traceroute for LDP/TE, and LSP Ping for VCCV feature helps service providers monitor label switched paths (LSPs) and quickly

More information

Telematics. 5th Tutorial - LLC vs. MAC, HDLC, Flow Control, E2E-Arguments

Telematics. 5th Tutorial - LLC vs. MAC, HDLC, Flow Control, E2E-Arguments 19531 - Telematics 5th Tutorial - LLC vs. MAC, HDLC, Flow Control, E2E-Arguments Bastian Blywis Department of Mathematics and Computer Science Institute of Computer Science 18. November, 2010 Institute

More information

Unit 8. Spanning Tree protocol, Virtual LANs (VLANs) and Access Networks

Unit 8. Spanning Tree protocol, Virtual LANs (VLANs) and Access Networks nit 8 panning ree protocol, Virtual s (Vs) and ccess etworks panning ree Protocol (P) Designed to prevent bridging loops ach bridge has unique D consisting of Priority + address n power up the bridge or

More information

Question 7: What are Asynchronous links?

Question 7: What are Asynchronous links? Question 1:.What is three types of LAN traffic? Unicasts - intended for one host. Broadcasts - intended for everyone. Multicasts - intended for an only a subset or group within an entire network. Question2:

More information

Network Working Group. Intended status: Experimental Expires: March 16, 2010 Tsinghua University C. Metz Cisco Systems, Inc. September 12, 2009

Network Working Group. Intended status: Experimental Expires: March 16, 2010 Tsinghua University C. Metz Cisco Systems, Inc. September 12, 2009 Network Working Group Internet-Draft Intended status: Experimental Expires: March 16, 2010 J. Wu Y. Cui X. Li M. Xu Tsinghua University C. Metz Cisco Systems, Inc. September 12, 2009 4over6 Transit Solution

More information

Multiprotocol Label Switching (MPLS)

Multiprotocol Label Switching (MPLS) 36 CHAPTER Prerequisites for MPLS, page 36-1 Restrictions for MPLS, page 36-1 Information About MPLS, page 36-2 Default Settings for MPLS, page 36-7 How to Configure MPLS Features, page 36-7 Configuration

More information

IEEE Frame Replication and Elimination for Reliability. Franz-Josef Goetz, Member of IEEE TSN TG, Siemens AG

IEEE Frame Replication and Elimination for Reliability. Franz-Josef Goetz, Member of IEEE TSN TG, Siemens AG Joint IEEE-SA and ITU Workshop on Ethernet IEEE 802.1 Frame Replication and Elimination for Reliability Franz-Josef Goetz, Member of IEEE 802.1 TSN TG, Siemens AG Geneva, Switzerland, 13 July 2013 Scope:

More information

CS-461 Internetworking. Dr. Mohamed Aboutabl

CS-461 Internetworking. Dr. Mohamed Aboutabl CS-461 Internetworking Dr. Mohamed Aboutabl http://www.cs.jmu.edu/users/aboutams The McGraw-Hill Companies, Inc., 2000 1 Chapter 1 Introduction The McGraw-Hill Companies, Inc., 2000 2 Internet today Network

More information

Lecture 7. Reminder: Homework 2, Programming Project 1 due today. Homework 3, Programming Project 2 out, due Thursday next week. Questions?

Lecture 7. Reminder: Homework 2, Programming Project 1 due today. Homework 3, Programming Project 2 out, due Thursday next week. Questions? Lecture 7 Reminder: Homework 2, Programming Project 1 due today. Homework 3, Programming Project 2 out, due Thursday next week. Questions? Thursday, September 15 CS 475 Networks - Lecture 7 1 Outline Chapter

More information

Implementing IEEE 802.1ah Provider Backbone Bridge

Implementing IEEE 802.1ah Provider Backbone Bridge Implementing IEEE 802.1ah Provider Backbone Bridge This module provides conceptual and configuration information for IEEE 802.1ah Provider Backbone Bridge on Cisco ASR 9000 Series Routers. The IEEE 802.1ah

More information

Request for Comments: S. Gabe Nortel (Northern Telecom) Ltd. May Nortel s Virtual Network Switching (VNS) Overview

Request for Comments: S. Gabe Nortel (Northern Telecom) Ltd. May Nortel s Virtual Network Switching (VNS) Overview Network Working Group Request for Comments: 2340 Category: Informational B. Jamoussi D. Jamieson D. Williston S. Gabe Nortel (Northern Telecom) Ltd. May 1998 Status of this Memo Nortel s Virtual Network

More information

Higher scalability to address more Layer 2 segments: up to 16 million VXLAN segments.

Higher scalability to address more Layer 2 segments: up to 16 million VXLAN segments. This chapter tells how to configure Virtual extensible LAN (VXLAN) interfaces. VXLANs act as Layer 2 virtual networks over Layer 3 physical networks to stretch Layer 2 networks. About VXLAN Encapsulation

More information

APT: A Practical Transit-Mapping Service Overview and Comparisons

APT: A Practical Transit-Mapping Service Overview and Comparisons APT: A Practical Transit-Mapping Service Overview and Comparisons draft-jen-apt Dan Jen, Michael Meisel, Dan Massey, Lan Wang, Beichuan Zhang, and Lixia Zhang The Big Picture APT is similar to LISP at

More information

Network Security Fundamentals. Network Security Fundamentals. Roadmap. Security Training Course. Module 2 Network Fundamentals

Network Security Fundamentals. Network Security Fundamentals. Roadmap. Security Training Course. Module 2 Network Fundamentals Network Security Fundamentals Security Training Course Dr. Charles J. Antonelli The University of Michigan 2013 Network Security Fundamentals Module 2 Network Fundamentals Roadmap Network Fundamentals

More information

L2 MPLS VPN (VPLS) Technology White Paper

L2 MPLS VPN (VPLS) Technology White Paper S9500 L2 MPLS VPN (VPLS) Technology White Paper L2 MPLS VPN (VPLS) Technology White Paper Keywords: MPLS, VPLS Abstract: MPLS technologies make it very easy to provide VPN services based on IP technologies

More information

Connectionless and Connection-Oriented Protocols OSI Layer 4 Common feature: Multiplexing Using. The Transmission Control Protocol (TCP)

Connectionless and Connection-Oriented Protocols OSI Layer 4 Common feature: Multiplexing Using. The Transmission Control Protocol (TCP) Lecture (07) OSI layer 4 protocols TCP/UDP protocols By: Dr. Ahmed ElShafee ١ Dr. Ahmed ElShafee, ACU Fall2014, Computer Networks II Introduction Most data-link protocols notice errors then discard frames

More information

Internet Engineering Task Force (IETF) A. Dolganow Nokia T. Przygienda. Juniper Networks, Inc. S. Aldrin Google, Inc.

Internet Engineering Task Force (IETF) A. Dolganow Nokia T. Przygienda. Juniper Networks, Inc. S. Aldrin Google, Inc. Internet Engineering Task Force (IETF) Request for Comments: 8279 Category: Experimental ISSN: 2070-1721 IJ. Wijnands, Ed. Cisco Systems, Inc. E. Rosen, Ed. Juniper Networks, Inc. A. Dolganow Nokia T.

More information

Chapter 12 Network Protocols

Chapter 12 Network Protocols Chapter 12 Network Protocols 1 Outline Protocol: Set of defined rules to allow communication between entities Open Systems Interconnection (OSI) Transmission Control Protocol/Internetworking Protocol (TCP/IP)

More information

Chapter 4 Network Layer: The Data Plane

Chapter 4 Network Layer: The Data Plane Chapter 4 Network Layer: The Data Plane A note on the use of these Powerpoint slides: We re making these slides freely available to all (faculty, students, readers). They re in PowerPoint form so you see

More information

Implementing SES Network Duplication A Best Practices Guide.

Implementing SES Network Duplication A Best Practices Guide. Implementing SES Network Duplication A Best Practices Guide. SIP Enablement Services 5.1 Avaya ABSTRACT This application note is a tutorial on Avaya SIP Enablement Services Network Duplication from an

More information

Cloud e Datacenter Networking

Cloud e Datacenter Networking Cloud e Datacenter Networking Università degli Studi di Napoli Federico II Dipartimento di Ingegneria Elettrica e delle Tecnologie dell Informazione DIETI Laurea Magistrale in Ingegneria Informatica Prof.

More information

Request for Comments: University of Twente/Ericsson J. Loughney Nokia S. Van den Bosch Alcatel June 2005

Request for Comments: University of Twente/Ericsson J. Loughney Nokia S. Van den Bosch Alcatel June 2005 Network Working Group Request for Comments: 4080 Category: Informational R. Hancock Siemens/RMR G. Karagiannis University of Twente/Ericsson J. Loughney Nokia S. Van den Bosch Alcatel June 2005 Status

More information

TSN Configuration Roadmap (proposed "what's next?")

TSN Configuration Roadmap (proposed what's next?) TSN Configuration Roadmap (proposed "what's next?") Rodney Cummings National Instruments IEEE 802.1, July 2017, Berlin Introduction P802.1Qcc moves TSN config forward in major ways We have identified gaps

More information