Lectures notes for 2010 - KTH
Lectures notes for 2010 - KTH Lectures notes for 2010 - KTH
Quality-of-Service Capabilities • for packet streams • Flow characterized by flow id + source address + destination address • unique random flow id for each source CLASS (8 bits) • Class field FLOW ID (20 bits) D (1 bit) Network-wide priority (3 bits) Reserved (4 bits) Delay sensitive Encodes the priority of traffic, can be used to provide “Differentiated services” Researchers would like to use two of these bits for congestion avoidance control: ♦ one bit which could be set by routers to indicate that congestion was experienced; ♦ the other bit could be used by the source to mark that it is “ready to adapt”. • Flow ID - indicates packets which should all be handled the same way. The original specified in RFC 1809: Using the Flow Label Field in IPv6 Subsequently updated - see Chapter 6 of Huitema, 2nd edition; this change occurred because of Steve McCanne’s SigComm’96 paper [6]. Note that chapter 27 in Forouzan is incorrect! Maguire Quality-of-Service Capabilities 10: 12 of 54 maguire@kth.se 2010.03.21 Internetworking/Internetteknik
Payload length Payload length is the length of the data carried after the header. As the length field is 16 bits ⇒ maximum packet size of 64 kilobytes; but there is a provision for "jumbograms" [via the Hop-by-Hop option header with option type 194]. See RFC 2675 [7]. Maguire Payload length 10: 13 of 54 maguire@kth.se 2010.03.21 Internetworking/Internetteknik
- Page 607 and 608: Inter-domain Management task force
- Page 609 and 610: Applications • E-mail • E-mail
- Page 611 and 612: Deregulation ⇒ New regulations
- Page 613 and 614: Latency 1 Usability FAX relay/broad
- Page 615 and 616: Voice Gateway 2B+D or 30B+D or …
- Page 617 and 618: Fax Support Both store-and-forward
- Page 619 and 620: Cisco Voice Over IP Enables Cisco 3
- Page 621 and 622: 2,400/4,800/7,200/9,600/14,400 bps
- Page 623 and 624: “The wireless workplace will soon
- Page 625 and 626: Carriers offering VOIP “Equant, a
- Page 627 and 628: Economics "Can Carriers Make Money
- Page 629 and 630: Patents Mixing voice and data in th
- Page 631 and 632: Deregulation ⇒ Trends • replaci
- Page 633 and 634: RTP: Real-Time Transport Protocol D
- Page 635 and 636: SIP: Session Initiation Protocol SI
- Page 637 and 638: SIP Invite 1 INVITE sip:bob@biloxi.
- Page 639 and 640: SIP Methods Method Invite Bye Optio
- Page 641 and 642: ENUM IETF’s E.164 Number Mapping
- Page 643 and 644: Web Services Using protocols built
- Page 645 and 646: This lecture we have discussed: •
- Page 647 and 648: IK1550 Internetworking/Internettekn
- Page 649 and 650: Internet Protocol Version 6 (IPv6)
- Page 651 and 652: • Wireless computers • supporti
- Page 653 and 654: Device Control • Control everyday
- Page 655 and 656: IPv6 header format version 4 bits C
- Page 657: Simplifications IPv6 builds on 20 y
- Page 661 and 662: Extension headers • Each header i
- Page 663 and 664: Writing an IPv6 address The 128 bit
- Page 665 and 666: Binary prefix Hex. prefix Fraction
- Page 667 and 668: Interface ID Must be unique to the
- Page 669 and 670: Link local addresses Link local add
- Page 671 and 672: Permanently assigned groups For exa
- Page 673 and 674: Prefix for IPv6 documentation The I
- Page 675 and 676: IPv6 Routing • all standard routi
- Page 677 and 678: Fragment header Next Header (8 bits
- Page 679 and 680: intermediate relays on the way to t
- Page 681 and 682: Security • Header Authentication
- Page 683 and 684: IPv6 ICMP [13] Type (8 bits) Code (
- Page 685 and 686: IPv6 ICMP Echo Request/Reply (PING)
- Page 687 and 688: Summary of IPv6 ICMP • incorporat
- Page 689 and 690: IPv6 Transition Mechanisms • Incr
- Page 691 and 692: IPv6 networks 6Bone - http://www.6b
- Page 693 and 694: If things are to be connected they
- Page 695 and 696: Where are ISPs? “… There is evi
- Page 697 and 698: This lecture we have discussed: •
- Page 699 and 700: [13] A. Conta and S. Deering, “In
- Page 701 and 702: IK1550 Internetworking/Internettekn
- Page 703 and 704: Emerging Network Architecture H …
- Page 705 and 706: Updating after a move Host name:
- Page 707 and 708: Communication from Z to X γ Z C X
Payload length<br />
Payload length is the length of the data carried after the header.<br />
As the length field is 16 bits ⇒ maximum packet size of 64 kilobytes; but there is<br />
a provision <strong>for</strong> "jumbograms" [via the Hop-by-Hop option header with option type<br />
194]. See RFC 2675 [7].<br />
Maguire Payload length 10: 13 of 54<br />
maguire@kth.se <strong>2010</strong>.03.21 Internetworking/Internetteknik
Change language