The document outlines a 7-week course on web technology management. Week 1 covers the history and current status of the World Wide Web. Weeks 2-3 cover web design principles related to networks, servers, clients, and programming. Weeks 4-5 cover management of open source and Microsoft web servers and databases. Week 6 covers specific web systems like content management systems and intranets. Week 7 addresses security issues on the web. The document also references architectural principles of the internet and web, including protocols like TCP/IP and DNS. It discusses the domain name system and how DNS translates names to IP addresses to locate devices on the internet.

1. The Principles of Web TechnologyManagementhttp://purl.org/net/wtmsopek@makolab.comPrincipia Webica

2. PlanWeek 1: The history and current status of the World Wide WebWeek 2: Web design principles – networks & serversWeek 3: Web design principles – Web clients, web programmingWeek 4:Management of Open Source Web Servers and databasesWeek 5: Management of Microsoft Web Servers and databasesWeek 6:Management of specific Web systems (CMS, Web services, Intranets)Week 7: Addressing the dangerous aspects of the Web

3. Architectural Principles of the Web.Network and Servers.Understanding WEB

4. Information Management: A proposalTim Berners-Lee, CERN, March 1989-May 1990http://www.w3.org/History/1989/proposal.html

5. Information Management: A proposalTim Berners-Lee, CERN, March 1989-May 1990http://www.w3.org/History/1989/proposal.html

6. Architectural Principles of the InternetRFC 1958; B. Carpenter; June, 1996„Fortunately, nobody owns the Internet, there is no centralized control, and nobody can turn it off. Its evolution depends on rough consensus about technical proposals, and on running code. Engineering feed-back from real implementations is more important than any architectural principles.”

7. Architectural Principles of the InternetRFC 1958; B. Carpenter; June, 1996„Is there an Internet Architecture? 2.1 Many members of the Internet community would argue that there is no architecture, but only a tradition, which was not written down for the first 25 years (…)However, in very general terms, the community believes that the goal is connectivity, the tool is the Internet Protocol, and the intelligence is end to end rather than hidden in the network.”

8. Architectural Principles of the InternetRFC 1958; B. Carpenter; June, 1996„Is there an Internet Architecture? 2.1 Many members of the Internet community would argue that there is no architecture, but only a tradition, which was not written down for the first 25 years (…)However, in very general terms, the community believes that the goal is connectivity, the tool is the Internet Protocol, and the intelligence is end to end rather than hidden in the network.” (…)The key to global connectivity is the inter-networking layer. The key to exploiting this layer over diverse hardware providing global connectivity is the "end to end argument".

9. General Design IssuesRFC 1958; B. Carpenter; June, 19963.1 Heterogeneity is inevitable and must be supported by design. Multiple types of hardware must be allowed for, e.g. transmission speeds differing by at least 7 orders of magnitude, various computer word lengths, and hosts ranging from memory-starved microprocessors up to massively parallel supercomputers. Multiple types of application protocol must be allowed for, ranging from the simplest such as remote login up to the most complex such as distributed databases. 3.2 If there are several ways of doing the same thing, choose one. If a previous design, in the Internet context or elsewhere, has successfully solved the same problem, choose the same solution unless there is a good technical reason not to. Duplication of the same protocol functionality should be avoided as far as possible, without of course using this argument to reject improvements.

10. General Design IssuesRFC 1958; B. Carpenter; June, 19963.3 All designs must scale readily to very many nodes per site and to many millions of sites. 3.4 Performance and cost must be considered as well as functionality. 3.5 Keep it simple. When in doubt during design, choose the simplest solution. 3.6 Modularity is good. If you can keep things separate, do so.

11. TCP/IP http://en.wikipedia.org/wiki/TCP/IPTCP/IPisnamed from two of the most important protocols in it: the Transmission Control Protocol (TCP) and the Internet Protocol (IP), which were the first two networking protocols defined in this standard.

12. TCP/IP http://en.wikipedia.org/wiki/TCP/IP

13. TCP/IP http://en.wikipedia.org/wiki/TCP/IP

14. DNS http://en.wikipedia.org/wiki/Domain_Name_SystemThe Domain Name System (DNS) is a hierarchical naming system built on a distributed database for computers, services, or any resource connected to the Internet or a private network. Most importantly, it translates domain names meaningful to humans into the numerical identifiers associated with networking equipment for the purpose of locating and addressing these devices worldwide.

15. DNS http://en.wikipedia.org/wiki/Domain_Name_System

16. DNS http://en.wikipedia.org/wiki/Domain_Name_SystemThe Domain Name SyntaxRFC 1035, RFC 1123, and RFC 2181.RULES:The right-most label conveys the top-level domain; for example, the domain name www.example.com belongs to the top-level domain com.The hierarchy of domains descends from right to left; each label to the left specifies a subdivision, or subdomain of the domain to the right.

17. DNS http://en.wikipedia.org/wiki/Domain_Name_SystemThetree of subdivisions may have up to 127 levels.Each label may contain up to 63 characters. The full domain name may not exceed a total length of 253 characters in its external dotted-label specificationDNS names may technically consist of any character representable in an octet. However, the allowed formulation of domain names in the DNS root zone, and most other sub domains, uses a preferred format and character set. The characters allowed in a label are a subset of the ASCII character set, and includes the characters a through z, A through Z, digits 0 through 9, and the hyphen.

18. DNS http://en.wikipedia.org/wiki/Domain_Name_SystemThis (last) rule is known as the LDH rule (letters, digits, hyphen). Domain names are interpreted in case-independent manner. Labels may not start or end with a hyphen.A hostname is a domain name that has at least one IP address associated. For example, the domain names www.example.com and example.com are also hostnames, whereas the com domain is not.

19. DNS http://en.wikipedia.org/wiki/Domain_Name_SystemThis (last) rule is known as the LDH rule (letters, digits, hyphen). Domain names are interpreted in case-independent manner. Labels may not start or end with a hyphen.A hostname is a domain name that has at least one IP address associated. For example, the domain names www.example.com and example.com are also hostnames, whereas the com domain is not.

20. DNS resolution http://en.wikipedia.org/wiki/Domain_Name_SystemDNS construction guarantees uniqueness

21. Lab work5.Remeber: http://purl.org/net/wtmExplore the web for topics:TCP/IP protocol stackWeb ArchitectureDNS and addressingMain transfer technologies (Fiber Optics, Copper Wire, Wireless Links)IPv4 and IPv6 – when we will use up all the address space ?Convergence: Network, Telephony, TV on the TCP/IP networks3 pages per topic