Category: Networking

May 27, 2017

Chapter 2: Application Layer

Table of Contents

2.1 Principles of Network Applications
- 2.1.1 Network Application Architectures
- 2.1.2 Process Communicating
- 2.1.3 Transport Services Available to Applications
- 2.1.4 Transport Services Provided by the Internet
- 2.1.5 Application-Layer Protocols
- 2.1.6 Network Applications Covered in This Book
2.2 The Web and HTTP
- 2.2.1 Overview of HTTP
- 2.2.2 Non-Persistent and Persistent Connections
- 2.2.3 HTTP Message Format
- 2.2.4 User-Server Interaction: Cookies
- 2.2.5 Web Caching
- 2.2.6 The Conditional Get
2.3 File Transfer: FTP
2.4 Electronic Mail in the Internet
2.5 DNS The Internet’s Directory Service
2.6 Peer-to-Peer Applications
2.7 Socket Programming: Creating Network Applications
2.8 Summary

2.1 Principles of Network Applications

Software you write should not need to actually have to be directly interact with network-core devices
2.1.1 Network Application Architectures
- Application architecture is distinctly different from the network architecture (5 layer)
- For a application developer all lower layers act as services
- The application architecture is designed by the developer and is structured on end systems to the developer’s desires
- There are 2 major types of architectures client-server and P2P
  - Client-Server Architecture
    - Always-on host which acts as the server
      - Servers have a fixed IP address
    - Servers are often collections of servers in a data center that act together as one virtual server
    - Clients do not directly contact each other
    - Clients only contact the server
  - Peer-to-Peer Architecture
    - Peers directly communicate with each other
    - Little to no reliance on dedicated server
  - Client-Server vs P2P?
    - P2P offers self-scalability
      - For each client that’s added it will also serve as a “server” to offer connections to other clients
    - P2P is harder to secure because peers have direct access to each other
2.1.2 Processes Communicating
- Processes on end systems communicate with each other using application level messages
- Client and Server Processes
  - Network applications consist of pairs of processes that send messages to each other over a network
  - One of these is the client and the other is the server
- The Interface Between the Process and the Computer Network
  - Processes receive and send messages through the network through a software interface called a socket
    - Think about this as the door to a house all things in and out must go through that door
  - A socket has its own API between application and network
  - This means that application developers only have access to what the API gives access to and thus there is very little control over the network components
- Addressing Processes
  - Two pieces of information are required to identify a receiving process
    1. Address of host (IP address)
    2. An identifier that specifies the receiving process in the destination host (port number)
      - Note some services over time have been given their own dedicated ports
2.1.3 Transport Services Available to Applications
- Non/Reliable Data Transfer
  - Reliable data transfer ensures that any packet that leaves a socket will be guaranteed to reach its destination even if a packet is dropped
  - If a packet is dropped it is re-transmitted
  - Loss-Tolerant applications don’t care if some packets are dropped often times these are multimedia applications
- Throughput
  - Throughput is defined as the rate at which the sending process can deliver bits to the receiving process
  - This rate is a fluctuating value and thus often reliable data transfer protocols will offer guaranteed speed
  - Bandwidth-sensitive Applications: Applications that depend on a minimum speed (eg. calls)
  - Elastic Applications: Applications that can suffer hits to throughput or random speeds (eg. sending email)
- Timing
  - Timing Guarantee is a guarantee that any bit that leaves arrives at the other socket within a guaranteed amount of time
  - Multiplayer games such as FPS games rely on low ping in order for it to feel as real time as possible
- Security
  - Transport protocol can provide security by encrypting the data
2.1.4 Transport Services Provided by the Internet
- Internet uses UDP and TCP
- TCP Services
  - TCP service model is a connection-oriented service and a reliable transfer service
  - Connection-Oriented Service: Client and server must identify and complete a handshake
    - After handshake a TCP connection is established
    - Once an application finishes sending messages the connection must be terminated
  - Reliable data transfer service: Relies on TCP to guarantee that every packet is sent without error in the proper order
  - TCP also contains a congestion control mechanism throttling the sending process if its sending things too fast
- UDP Services
  - Lightweight transport protocol for minimal services
  - Connectionless: No handshakes at the beginning
  - Unreliable data service, does not guarantee whole message gets sent
    - Data may also arrive out of order
  - No congestion control
- Services Not Provided by Internet Transport Protocols
  - We have classified protocols by
    - Reliable data transfer, throughput, timing, and security
  - However we have not mentioned timing and throughput for UDP and TCP (refer to chapter 7)
  - A lot of applications prefer to use UDP due to lack of congestion control but almost always have a TCP backup in case UDP is blocked by firewalls
2.1.5 Application-Layer Protocols
- Application-Layer Protocol: Defines how applications at either end systems communicate with each other
- The following are defined by such protocol
  - Types of messages exchanged
  - The syntax of the messages exchanged
  - Semantics of the fields (meaning)
  - Rules for determining how a process sends and receives messages
- NOTE: Application-Layer Protocols are only one part of a network application and not a network application itself
- For example the web’s application layer protocol is HTTP which defines the format and sequence of messages sent between users/servers
- For example for email, SMTP

2.2 The Web and HTTP

2.2.1 Overview of HTTP
- NOTE: Web browsers implement the client side of HTTP and thus client==browser
- Web page: Collection of objects (files can be images, HTML pages, etc)
  - Web server: Implement server side of HTTP
- HTTP uses TCP as its transport protocol
  - 1. HTTP Client initiates TCP connections
  - 2. After TCP handshake is completed server and client communicate through the open socket interfaces
  - TCP will handle all the communications once the data is sent to the socket
- HTTP is stateless, this means that no information is stored about the state of the client
  - Therefore for example if the client requests the same file twice within a short period of time, the server will still send it twice
2.2.2 Non-Persistent and Persistent Connections
- HTTP with Non-Persistent Connections (separate TCP connection)
  - Suppose we are accessing a webpage with 1 HTML file and 10 jpg images
  - Process:
    - 1. HTTP Client initiates TCP connection with server on port 80 creating a socket on both ends
    - 2. HTTP client sends HTTP request message to server via socket
    - 3. HTTP server processes request message and retrieves file. The file is then encapsulated as a HTTP response message and sent back
    - 4. HTTP server after sending tells TCP to close the connection (which will formally be terminated after the whole file is sent)
    - 5. HTTP client receives the response message. TCP connection is terminated. Client then extracts the file from the HTTP message (HTML file first) and finds that there are 10 references to jpg objects
    - 6. 1-4 is repeated for each referenced object
  - The above is using a non-persistent connection where each TCP connection is closed after server sends the object and does not persist for subsequent objects
  - The 10 jpgs can be sent via parallel or serial connections
  - Round-Trip-Time (RTT): Time for a small packet to travel from client->server->client
    - This includes packet-propagation delays, packet-queuing delays in switches/intermediate routers, and packet-processing delays
    - Total time ~2 RTT + time for data transfer
- HTTP with Persistent Connections (same TCP connection)
  - Unlike non-persistent, TCP connections are kept open after the first file is transferred, meaning all files can then be sent from one connection removing overhead of recreating the TCP connection
  - This allows for back to back object requests and responses
2.2.3 HTTP Message Format (RFC 1945; RFC 2616)
- HTTP Request Message
  - - Note the carriage return and line feed
    - GET doesn’t use entity body but POST does
    - POST is thus often used for filling out forms
      - Possible to use GET by putting the arguments into form into the URL eg. http://www.somesite.com/animalserach?monkeys&bananas
  - GET /somedir/page.html HTTP/1.1 Host: http://www.someschool.edu Connection: close User-agent: Mozilla/5.0 Accept-language: fr
  - Request Line: First line
    - 3 fields: Method field, URL field, HTTP version
      - Method: GET, POST, HEAD, PUT, DELETE
        
        GET: Browser requests an object
        
        POST: The POST method is used to request that the origin server accept the entity enclosed in the request as a new subordinate of the resource identified by the Request-URL in the Request-Line
        
        HEAD: The HEAD method is identical to GET except that the server MUST NOT return a message-body in the response.
        
        PUT: The PUT method requests that the enclosed entity be stored under the supplied Request-URL
        
        DELETE: The DELETE method requests that the origin server delete the resource identified by the Request-URL
      - URL Field: Points to the directory and then the file on the server
      - HTTP version: Version information
  - Header Lines: Remaining message
    - Host: http://www.someschool.edu
      - Needed for web proxy caches even though TCP connection has already been established
    - Connection: close
      - Don’t use persistent connections
    - User-agent: Mozilla/5.0
      - Browser type of client
    - Accept-language: fr
      - Tells server to try and find a French version of the object
- HTTP Response Message
  - ```
  HTTP/1.1 200 OK
  Connection: close
  Date: Tue, 09 Aug 2011 15:44:04 GMT
  Server: Apache/2.2.3 (CentOS)
  Last-Modified: Tues, 09 Aug 2011 15:11:03 GMT
  Content-Length: 6821
  Content-Type: text/html
  (data ...)
```
- Status Line: First line
  - 3 Fields: Protocol version, status code, status message
    - Status Codes:
      
      200 OK: Request succeeded and the information is returned in response
      
      301 Moved Permanently: Permanently moved object and new URL is specified at the Location: header of response message which the client will automatically retrive
      
      400 Bad Request: Generic error
      
      404 Not Found: Requested document does not exist
      
      505 HTTP Version Not Supported
- Six Header Lines
  - ```
  Connection: close
```
    - Tells client that TCP connection will be closed
  - ```
  Date: Tue, 09 Aug 2011 15:44:04 GMT
```
    - When the HTTP response was created/sent by server
  - ```
  Server: Apache/2.2.3 (CentOS)
```
    - Information about the server
  - ```
  Last-Modified: Tues, 09 Aug 2011 15:11:03 GMT
```
    - When object was last modified
  - ```
  Content-Length: 6821
```
    - # of bytes of the object
  - ```
  Content-Type: text/html
```
    - Type of requested content
- Entity Body
2.2.4 User-Server Interaction: Cookies
- Recall HTTP server is stateless
- Cookies are a way to identify and track users on websites
- - An example of how a cookie is used to easily authenticate a user and enable such services as one-click shopping
2.2.5 Web Caching (Proxy Server)
- A server used to satisfy HTTP requests on behalf of an origin Web server
- This web cache stores recent copies of a web page/objects
  - 1. Reduces response time for client
  - 2. Reduce traffic on origin server
- - Web cache and origin server setup with clients
- Example of a request using a web cache
  - 1. Establish a TCP connection to the web cache and send the HTTP request there
  - 2. Web cache checks to see if it has a copy if so return the object to client
  - 3. If the web cache does not have the object the web cache creates a TCP connection with the origin server and then requests the object and receives it
  - 4. The web cache caches the object and then sends it to the client
- Internet Delay: Time for a router from sending a request to when it receives the response
- REFER TO PAGE 112-113 for an example with numbers on how this can make it faster
2.2.6 The Conditional GET
- This solves the problem of whether a user is getting the most updated version of the webpage or not
- This is the same as the GET message but also contains the “If-Modified Since: “ header line
- For example
  - 1. Client Request
  - 2. Web cache gets from origin server
  - 3. Web cache caches and sends to client
  - 4. Client Requests at a later date
  - 5. Web cache requests an up to date check using conditional get
    - ```
    GET /fruit/kiwi.gif HTTP/1.1
    Host: www.exotiquecusinie.com
    If-modified-since: Wed, 7 Sep 2011 09:23:24
```
- 6. Origin server responds
  - Not modified
    - HTTP/1.1 304 Not Modified Date: Sat, 15 Oct 2011 15:39:29 Server: Apache/1.3.0 (Unix) (empty entity body)
  - Modified
    - HTTP/1.1 304 Modified
      Date: Sat, 15 Oct 2011 15:39:29
      Server: Apache/1.3.0 (Unix)
      (entity body)
- 7. Web cache caches and forwards on to client

2.3 File Transfer: FTP

May 24, 2017

Chapter 1: Computer Networks and the internet

Return to top level page

Table of Contents

1.1 What is the Internet
- 1.1.1 A Nuts-and-Bolts Description
- 1.1.2 A Services Description
- 1.1.3 What is a protocol?
1.2 The Network Edge
- 1.2.1 Access Networks
- 1.2.2 Physical Media
1.3 The Network core
- 1.3.1 Packet Switching
- 1.3.2 Circuit Switching
- 1.3.3 A Network of Networks
1.4 Delay, Loss, and Throughput in Packet-Switched Networks
- 1.4.1 Overview of Delay in Packet-Switched Networks
- 1.4.2 Queuing Delay and Packet Loss
- 1.4.3 End-to-End Delay
- 1.4.4 Throughput in Computer Networks
1.5 Protocol Layers and Their Service Models
- 1.5.1 Layered Architecture
- 1.5.2 Encapsulation
1.6 Networks Under Attack

1.1 What is the Internet

1.1.1 A Nuts-and-Bolts Description
- Devices that are connected are known as hosts or end systems
- End systems are connected together with communication links or network switches
- Packets are information appended with headers
- ISPs are made of multiple packet-switched networks which act as information highways
  - Lower level ISPs such as NTT, Sprint, ATT are connected on an international level with fiber optic cables
- End systems run TCP/IP which control sending and receiving packets from the internet
  - TCP: Transmission Control Protocol
  - IP: Internet Protocol
- 1.1.2 A Services Description
  - The internet is an infrastructure for services such as VoIP and web surfing
  - Distributed Applications: Applications that have multiple end systems exchanging data
- 1.1.3 What is a Protocol?
  - A protocol defines the format and the order of messages exchanged between two or more communicating entities, as well as the actions taken on the transmission and/or receipt of a message or other event

1.2 The Network Edge

End System=Host because they also run (host) application programs
Hosts are sometimes divided into 2 subcategories clients and servers
1.2.1 Access Networks
- Edge routers are the first router that the end system encounters, for example your home router
- DSL: Digital Subscriber Link
  - DSLAM: Digital subscriber line access modem located at the CO
  - CO: Central Office
  - Designed for short distance from the CO
- Cable/Fiber
  - CMTS: Cable modem termination system similar to DSLAM
- Fiber to the Home (FTTH)
  - ONT: Optical network terminator
  - OLT: Optical line terminator
  - Both are used to go from light pulses to electrical signals
  - All network terminators receive all data and its up to the terminator to disassemble that and find the packets one is looking for
- LAN (Local Area Network): Ethernet and Wi-Fi
- Wide Area Access: 3G and LTE
- Types of Cables and their capabilities
  - Refer to the book for more information on this I don’t think this is important right now will update this section if needed later on

1.3 The Network Core

Network Core: Mesh of packet switches and links that interconnect the Internet’s end systems
1.3.1 Packet Switching
- A message/data is split into multiple packets
- A packet then travels between packet switches and communication links such as routers and link-layer switches
- Packets are transferred at the max speed a cable will allow
  - L bits per packet R bits/sec total time required is L/R seconds
- Store-and-Forward Transmission
  - Receive entire packet before transmitting first bit
  - For example if we want to transmit 3 packets
    - Let T=L/R
    - T to transmit from source to router
    - T to transmit first packet from router to destination and to receive second packet at the router
    - T to transmit second packet from router to destination and to receive third packet at router
    - T to transmit third packet for a total of 4T
  - Every packet has multiple links and each link has an output buffer (queue)
  - This is used if the input traffic is faster than the output capabilities and all packets wait to be transmitted from here
    - If the buffer becomes completely full packet loss will occur if data continues to stream in
  - This then introduces queuing delays
- Forwarding Tables and Routing Protocols
  - How to determine where to route data to? Use IP addresses
  - IP addresses contain sections each representing a level of hierarchy
  - A forwarding table will match sections of the IP address to a certain destination
  - The generation of forwarding is discussed in Chapter 4 however there are routing protocols that are used to automatically generate these tables
1.3.2 Circuit Switching
- This is the alternative to packet switching
- If a connection is established that link is completely reserved for that one source and destination versus packet switching where the link is allocated on demand
- Circuit switching creates end-to-end connections between two hosts
- In the picture above if the switch has 1 Mbps capability then each link will be given 250 kbps of bandwidth
- Multiplexing in Circuit-Switched Networks
  - A circuit is implemented with FDM or TDM (frequency division multiplexing or time division multiplexing)
  - FDM: Divide the frequency spectrum into slices for each link
  - TDM: Divide the a frame (time slice) into the number of links (similar to round robin scheduling)
- Packet Switching vs Circuit Switching
  - Circuit switching will waste bandwidth if there are dead times during transmission
  - Circuit switching will severely limit number of active users
  - Packet switching will cause more delays for each individual user
  - Packet switching will also drop packets when there are too many users
  - However if there is enough downtime, packet switching will be more useful in increasing the number of concurrent users that are actually able to do crap
1.3.3 A Network of Networks
- Now we discuss the way ISPs and users are connected
- Access ISP: This is the one a home user pays to get access to the internet
- Regional ISP: Access ISPs pay regional ISPs to get access to the internet
- Tier 1 ISP: Regional ISPs pay Tier 1 ISPs to get access to the internet
- IXP: Internet Exchange Point, these are points which allow ISPs to peer together
- Content Provider: Such as Google, they have a large amount of data centers and servers which are sometimes able to directly make contact with Non tier-1 ISPs allowing them to also circumvent fees when giving access to internet
- Peer: Connect networks together so that all traffic between two sources can share a direct connection
  - This is often used to circumvent paying lower level ISPs which bill them based on usage

1.4 Delay, Loss, and Throughput in Packet-Switched Networks

1.4.1 Overview of Delay in Packet-Switched Networks
- A packet suffers multiple types of delays
  - Nodal processing, queuing, transmission, propagation delay
  - These sum to give a total nodal delay
- Types of Delay
  - Processing Delay
    - Time required to examine the packet’s header and determine where to direct the packet is part of the processing delay
    - May also include checking for bit-level errors
    - Usually on the order of microseconds or less
  - Queuing Delay
    - Time a packet waits to be transmitted onto the link
    - Depends on size of the queue, the speed of the link, and the intensity and nature of the traffic at arriving
    - On the order of microseconds to milliseconds
  - Transmission Delay (Packet pre pushed to link)
    - L: Length of packet in bits
    - R: Transmission rate in bits/sec
    - L/R: Transmission delay in seconds from router A to B
    - On the order of microseconds to milliseconds
  - Propagation Delay (Packet after pushed to link)
    - Time to propagate data from router A to B
    - Depends on the media (copper wire, optics, etc)
    - s: Propagation speed of link
    - d: Distance to travel
    - d/s: Propagation delay
    - After all bits arrive at router B then B performs forwarding
- Comparing Transmission and Propagation Delay
  - Transmission: Time required for the router to push out the packet
  - Propagation: Time it takes a bit to propagate from one router to the next
- Total Nodal Delay
  - $d_{nodal}=d_{proc}+d_{queue}+d_{trans}+d_{prop}$
1.4.2 Queuing Delay and Packet Loss
- $d_{queue}$ is very complicated
- Can vary from packet to packet thus often all estimates are calculated statistically
- a: Average rate at which packets arrive (packets/sec)
- L: Length of packet (assume uniform)
- R: bits/sec of link
- La/R: Traffic intensity
  - If La/R>1 then queue will grow and exceed the size
  - Design a system such that $La/R \leq 1$
- Typically, the arrival process to a queue is random and not at preordained time slices
  - La/R is not sufficient to categorize traffic intensity
- Packet Loss
  - In reality queues have finite capacity
  - Once a queue reaches full capacity the next packet that arrives before a spot is opened is dropped
  - Performance of a node thus also needs to take into consideration the probability of packet loss
  - Often packet loss may be re-transmitted
1.4.3 End-to-End Delay
- Defined as delay from source to destination
- Assume N-1 routers and no congestion allowing us to neglect queuing delay
- - $d_{trans}=L/R$
- Traceroute
  - This is used to trace the number of nodes one hits when resolving an address
  - The source sends N special packets (labeled 1 to N) to N-1 routers
  - When the nth router receives a packet it does not forward it but sends a message back to the source allowing us to build a roardmap
  - Traceroute runs 3 times (sends 3N packets)
  - - Column 1: nth packet value
    - Column 2: name of router
    - Column 3: address of router
    - Columns 4-6: time taken to reach the nth router
    - It is important to note that these times are not constant due to the queuing on the routers which may increase or decrease as the traffic evolves
    - Not all routers have names
- End System, Application, and Other Delays
  - If an end system wants to transmit into a shared medium (eg. Wi-Fi uses)
  - Then it may purposefully delay until all packets are received before continuing
  - Packetization delay: The process of converting data into a format which can be stored in packets
    - In voice over IP this is turning an analog voice signal into a digital one
1.4.4. Throughput in Computer Networks
- Instantaneous Throughput: At any point in time how many bits/sec a destination is receiving data
- Average Throughput: F/T where F=total bits and T=total time
- Let the following which are both measured in bits per second
  - $R_{s}$ : Rate of link between server and router
  - $R_{c}$ : Rate of link between router and client
- The bottleneck becomes $min(R_{s}, R_{c})$
- With multiple routers in between the above becomes a minimum of all the rates
- - On the left we have a direct link between server and client
  - The right we have a pipe (imagine its an ISP) connected to 10 servers and 10 clients
    - Often the R capacity of the ISP is much higher than any of the individual connections so that is usually not the bottleneck
    - However if it is exceeded the solution will be to ration the total R between the 10 client-server connections either based on priority or evenly
1.5 Protocol Layers and Their Service Models
- 1.5.1 Layered Architecture
  - A human analog is the airline functionality
    - Each component is modular and each higher level component depends on each lower level component where everything is defined by an API (aka just cause the gates change doesn’t mean you can’t load luggage anymore)
    - Therefore each layer
      - 1. Performs its designated actions
      - 2. Uses information provided from a lower level to do so
    - Layered architecture provides modularity
- - Protocol Layering
    - - Stack refers to the culmination of all the layers of the protocols
    - The same ideas apply
      - 1. Performs its designated actions
      - 2. Uses information provided from a lower level to do so
      - And allows for modularity
      - Each layer n often contains components from the layer below
    - Protocols can be designed in both hardware and software
    - Here for example if layer n provides a reliable delivery message in reality layer n only provides something like error correction while n-1 is the actual main brains of the delivery system
- - Application Layer
    - Includes HTTP (web) and SMTP (mail) and DNS (domain name system URL->32 bit address)
    - Two end systems using an application will use this layer to exchange packets
    - Refer to application layer packets as messages
- - Transport Layer
    - Transports application-layer messages between application endpoints
    - TCP: Transmission Control Protocol
      - This focuses on guaranteed delivery of application-layer messages and flow control (matching source destination speeds)
      - Congestion control to throttle source speed if too much traffic
    - UDP: User Datagram Protocol
      - Connectionless service to its applications
      - No reliability and flow control and no congestion control
    - Refer to transport layer packets as segments
- - Network Layer
    - Moving network-layer packets from one host to another
    - TCP/UDP passes a transport-layer segment and a destination address to the network layer
    - IP Protocol: Defines the datagram fields and how end systems and routers act on these fields all internet components at network layer must run the IP protocol
    - Network-layer packets are known as datagrams
- - Link Layer
    - While network layer sets the destination (routing) the link layer actually facilitates the transfer of datagrams from node to node (host/router)
    - There are multiple link layer protocols such as Ethernet/Wi-Fi
      - Different link layer protocols handle the datagram deifferently
    - Link-layer packets are known as frames
- - Physical Layer
    - This depends on the physical media used such as cable type (copper/fiber)
- - OSI Model
    - OSI Model differs by adding 2 new layers (presentation layer, session layer)
    - The other 5 layers act in similar manner
    - Presentation Layer: Services to allow applications (top level) to properly interpret the data such as de/encrypting messages or de/compression of data
    - Session Layer: Allows for delimiting and synchronization of data exchange allowing for checkpoints or data recovery
- 1.5.2 Encapsulation
  - Router vs Link Layer Switch
    - These are both packet switches but routers operate at level 3 and link-layer switches at level 2
  - Hosts (end points) implement all 5 levels
  - - Note here that each layer adds its own header or some form of change to the M (message)
    - For instance the application level message M+H_transport=transport-layer segment encapsulating the application-level message
    - In general, each level after processing will contain a payload field and a header field
1.6 Networks Under Attack
- Virus: Malware which requires interaction from user to infect user’s device
- Worm: Malware which does not require interaction from user to infect devices
- DoS: Denial of Service
  - Vulnerability Attack: Sending specific packets to the destination to stop the service or hinder it
  - Bandwidth Flooding: Sending so many packets that the access link becomes so clogged it can’t actually receive legitimate packets
  - Connection Flooding: Establish a large amount of half open/fully open TCP connections to block all legitimate connections
- DDoS: Same as a DoS but uses multiple sources (botnet)
- Packet sniffing: To sniff the packets from a source to destination passively as a passive receiver
- IP Spoofing: Create a packet with arbitrary source address, packet content, and destination address and then inject the packets onto the internet
  - Can be solved with end point authentication