Scribd Logo
Upload

Welcome to Scribd!

  • 35 views

    Computer Networks Chapter 2 Application Layer Notes

    Uploaded by

    derguenhart
    This document summarizes key concepts in network applications including client-server architecture, web and HTTP, email protocols, DNS, and peer-to-peer architectures. Client-server models have permanent server hosts that clients communicate with intermittently, while peer-to-peer architectures have no dedicated servers and clients directly communicate and provide services to each other. The document also outlines HTTP request and response methods, how cookies work, SMTP and IMAP email protocols, and how the distributed DNS system works to resolve domain names to IP addresses through an iterative query process.

    Copyright:

    © All Rights Reserved
    Download as PDF, TXT or read online from Scribd

    Computer Networks Chapter 2 Application Layer Notes

    Uploaded by

    derguenhart
    35 views5 pages
    This document summarizes key concepts in network applications including client-server architecture, web and HTTP, email protocols, DNS, and peer-to-peer architectures. Client-server models have permanent server hosts that clients communicate with intermittently, while peer-to-peer architectures have no dedicated servers and clients directly communicate and provide services to each other. The document also outlines HTTP request and response methods, how cookies work, SMTP and IMAP email protocols, and how the distributed DNS system works to resolve domain names to IP addresses through an iterative query process.

    Original Description:

    Computer Networks Chapter 2 Application Layer Notes

    Original Title

    Computer_Networks_Chapter_2_Application_Layer_Notes

    Copyright

    © © All Rights Reserved

    Available Formats

    PDF, TXT or read online from Scribd

    Did you find this document useful?

    Is this content inappropriate?

    This document summarizes key concepts in network applications including client-server architecture, web and HTTP, email protocols, DNS, and peer-to-peer architectures. Client-server models have permanent server hosts that clients communicate with intermittently, while peer-to-peer architectures have no dedicated servers and clients directly communicate and provide services to each other. The document also outlines HTTP request and response methods, how cookies work, SMTP and IMAP email protocols, and how the distributed DNS system works to resolve domain names to IP addresses through an iterative query process.

    Copyright:

    © All Rights Reserved
    Download as PDF, TXT or read online from Scribd
    Download as pdf or txt
    35 views5 pages

    Computer Networks Chapter 2 Application Layer Notes

    Uploaded by

    derguenhart
    This document summarizes key concepts in network applications including client-server architecture, web and HTTP, email protocols, DNS, and peer-to-peer architectures. Client-server models have permanent server hosts that clients communicate with intermittently, while peer-to-peer architectures have no dedicated servers and clients directly communicate and provide services to each other. The document also outlines HTTP request and response methods, how cookies work, SMTP and IMAP email protocols, and how the distributed DNS system works to resolve domain names to IP addresses through an iterative query process.

    Copyright:

    © All Rights Reserved
    Download as PDF, TXT or read online from Scribd
    Download as pdf or txt
    of 5

    Principles of network applications

    Client-server architecture
    server:
    always-on host
    permanent IP address
    often in data cencers for scaling

    clients:
    communicate with server
    may be intermittently connected
    may have dynamic IP addresses
    do not communicate directly with each other

    process
    program running within a host

    within same host, two processes communicate using inter-process communication


    (defined by OS)
    processes in different hosts communicate by exchanging messaes via sockets
    aside: applications with P2P architectures have client processes & server processes

    Web and HTTP


    HTTP
    HTTP: hyertext trasfer protocol

    Web's application layer protocol


    client/server model

    - client: browser that requests, receivies, (using HTTP protocol) and dispalys Web
    objects

    - server: Web server sends (using HTTP protocol) objects in resporse to requests

    HTTP is stateless
    server mantains no information about past client requests
    non-perisistent HTTP

    1. TCP connection opend


    2. at most one object sent over TCP connection
    3. TCP connection closed

    perisistent HTTP

    1. TCP connection opend to a server


    2. multiple ojects can be sent over single TCP connection between client, and that
    server
    3. TCP connection closed-

    Request messages
    POST method:
    web page often includes form input
    user input sent from client to server in entity body of HTTP POST request messages

    GET method:
    uses GET method
    input is uploaded in URL field of request line

    Cookies
    many Web sites use cookies

    four components:

    1. cookie header line of HTTP response message


    2. cookie header line in next HTTP request message
    3. cookie file kept on user's browser
    4. back-end database at Web site

    E-mail, SMPT, IMAP


    Electronic mail
    user agents
    mail servers
    SMTP simple mail trasfer protocol

    User Agent
    aka mail reader
    composing, editing, reading mail messages
    e.g., Outlook, iPhone mail client
    outgoing, incoming messages stored on server

    Mail servers
    mailbox contains incoming messages for user
    message queue of outgoing (to be sent) mail messages
    SMTP protocol between mail servers to lend email messages
    client: sending mail server
    server receiving mail server

    SMPT

    uses TCP to reliably transfer email message from client(mail server initiating
    connection) to server, port 25

    direct transfer: sending server (acting like client) to receiving server

    three phases of transfer

    SMTP handshaking
    SMTP tranfer of messages
    SMTP closure

    command/response interaction (like HTTP)

    commands ASCII text


    response status code and phrase

    SMTP uses perisistent connections

    SMTP requires message header \ body to be in 7-bit


    The Domain Name System DNS
    distributed database implemented in hierarchy of many name servers
    application-layer protocol hosts, name servers communicate to resolve names

    humongous distributed database

    handles many trillions of queries/day

    organizationally physically decentralized

    bulletproof reliablity security

    iterated query:

    contacted server relpies with name of server to contact


    i don't know this name, but ask this server

    recursive query:

    puts burden of name resolution on contacted name server


    heavy load at upper levels of hierarchy?

    caching, updating records


    once any name server learns mapping, it caches mapping immediately returns a
    cached mapping in response to a query
    caching improves response time
    cache entries timeout disappear after some time TTL
    TLD servers typically cached in local name servers
    thus root name servers not often visited
    cached entries may be out-of-date
    if name host changes IP address, may not be known Internet-wide until all TTLs
    expire
    best effort name-to-address translation!

    Attacking DNS
    DDoS attacks
    bombard root servers with traffic
    not successful to date
    traffic filtering
    local DNS servers cache IPs of TLD servers, allowwing root server bypass
    bombard TLD servers
    potentially more dangerous

    Spoofing attacks
    intercept DNS queries, returning bogus replies
    DNS cache poisoning

    Pure P2P architecture


    no always-on server
    arbitrary end systems directly communicate
    peers are intermittently connected and change IP addresses
    peers request services from other peers, provide service in return to other peers

    You might also like