
IPv6 Network Programming
Description
Alles über E-Books | Antworten auf Fragen rund um E-Books, Kopierschutz und Dateiformate finden Sie in unserem Info- & Hilfebereich.
More details
Other editions
Additional editions

Person
Content
- Front Cover
- IPv6 Network Programming
- Copyright Page
- Contents
- Preface
- About This Book
- Write Portable Application Programs
- Be Security Conscious When Writing Programs
- Terminology and Portability
- Chapter 1. Introduction
- 1.1 A History of IPv6 and Its Key Features
- 1.2 Transition from IPv4-Only Internet to IPv4/v6 Dual Stack Internet
- 1.3 UNIX Socket Programming
- 1.4 IPv6 Architecture from a Programmer's Point of View
- Chapter 2. IPv6 Socket Programming
- 2.1 AF_INET6: The Address Family for IPv6
- 2.2 Why Programs Need to Be Address-Family Independent?
- 2.3 Guidelines to Address-Family Independent Socket Programming
- Chapter 3. Porting Applications to Support IPv6
- 3.1 Making Existing Applications IPv6 Ready
- 3.2 Finding Where to Rewrite, Reorganizing Code
- 3.3 Rewriting Client Applications
- 3.4 Rewriting Server Applications
- Chapter 4. Tips in IPv6 Programming
- 4.1 Parsing a IPv6 Address out of String
- 4.2 Issues with ":" As a Separator
- 4.3 Issues with an IPv4 Mapped Address
- 4.4 bind(2) Ordering and Conflicts
- 4.5 How IPv4 Traffic Gets Routed to Sockets
- 4.6 Portability across Systems
- 4.7 RFCs 2292/3542, Advanced API
- 4.8 Platform Support Status
- Chapter 5. A Practical Example
- 5.1 Server Program Example-popa3d
- 5.2 Further Extensions
- 5.3 Client Program Example-nail
- A. Coming updates to IPv6 APIs
- B. RFC2553 "Basic Socket Interface Extensions for IPv6
- C. RFC3493 "Basic Socket Interface Extensions for IPv6
- D. RFC2292 "Advanced Sockets API for IPv6
- E. RFC3542 "Advanced Sockets Application Program Interface (API) for IPv6
- F. IPv4-Mapped Address API Considered Harmful
- G. IPv4-Mapped Addresses on the Wire Considered Harmful
- H. Possible Abuse Against IPv6 Transition Technologies
- I. An Extension of format for IPv6 Scoped Addresses
- J. Protocol Independence Using the Sockets API
- References
System requirements
File format: PDF
Copy protection: Watermark-DRM (Digital Rights Management)
System requirements:
- Computer (Windows; MacOS X; Linux): Use the free software Adobe Reader, Adobe Digital Editions, or any other PDF viewer of your choice (see eBook Help).
- Tablet/Smartphone (Android; iOS): Install the free app Adobe Digital Editions or another reading app for eBooks, e.g., PocketBook (see eBook Help).
- E-reader: Bookeen, Kobo, Pocketbook, Sony, Tolino and many more (only limited: Kindle).
The file format PDF always displays a book page identically on any hardware. This makes PDF suitable for complex layouts such as those used in textbooks and reference books (images, tables, columns, footnotes). Unfortunately, on the small screens of e-readers or smartphones, PDFs are rather annoying, requiring too much scrolling.
This eBook uses Watermark-DRM, a „soft” copy protection. This means that there are no technical restrictions to prevent illegal distribution. However, there is a personalised watermark embedded in the eBook that can be used to identify the purchaser of the eBook in the event of misuse and to provide evidence for legal purposes.
For more information, see our eBook Help page.