Search

Mangesh M Kasbekar

from New York, NY
Age ~51
Get Report
Also known as:
Mangesh R
Connected to:
Gajanan R Kasbekar, 53Umesh M Kasbekar, 66Dave W Kasberg, 67Justin R Kasberg, 45Melodi E Kasberg, 68Stephen Kasberg, 43Denise J Kasbohm, 72Donna B Kasbohm, 91Bernadine M Kascak, 77Nancy T Kascak, 63

Mangesh Kasbekar Phones & Addresses

  • New York, NY
  • 329 Harvard St, Cambridge, MA 02139 (617) 498-0209
  • 1691 Cambridge St, Cambridge, MA 02138 (617) 498-0209
  • 1691 Cambridge St #13, Cambridge, MA 02138 (617) 498-0209
  • Watertown, MA
  • 445 Waupelani Dr, State College, PA 16801 (814) 867-6051
  • University Park, PA
  • Nashua, NH
  • 200 E 72Nd St APT 27H, New York, NY 10021

Work

Company: Akamai technologies May 2009 Position: Principal architect

Education

Degree: Doctorates, Doctor of Philosophy School / High School: Penn State University 1995 to 2000 Specialities: Computer Science, Philosophy

Skills

Distributed Systems • Cloud Computing • Algorithms • Saas • Scalability • Enterprise Software • Mobile Devices • Distributed Caching • Web Acceleration • Tcp/Ip • C++ • Python • Product Management • Mobile Applications • System Architecture • Shell Scripting • Javascript • Internet Protocol Suite • Software As A Service • Cdn • Content Distribution Networks • Media Delivery • Ios Development • Swift • Media Servers • Performance Engineering • High Availability Architecture • Mathematical Modeling • Energy Efficiency • Bottom Line Improvement • Cogs • Monitoring Performance • Overlay Networks • Computer Networking • Mobile Internet • Http/Https • 3G • Lte • Linux • Linux Server • Https • Unix • C • Sql • Mobile Networking • Financial Modeling

Languages

English

Industries

Computer Networking

Resumes

Resumes

Mangesh Kasbekar Photo 1

Principal Architect

View page
Location:
New York, NY
Industry:
Computer Networking
Work:
Akamai Technologies
Principal Architect
Akamai Technologies May 2002 - May 2009
Senior Architect
Akamai Technologies Oct 2000 - May 2002
Senior Software Engineer
Nokia Bell Labs May 1997 - Aug 1997
Summer Intern
Tata Consultancy Services Dec 1994 - Aug 1995
Assistant Systems Analyst
Education:
Penn State University 1995 - 2000
Doctorates, Doctor of Philosophy, Computer Science, Philosophy University of Bombay 1990 - 1994
Bachelors, Electrical Engineering
Skills:
Distributed Systems
Cloud Computing
Algorithms
Saas
Scalability
Enterprise Software
Mobile Devices
Distributed Caching
Web Acceleration
Tcp/Ip
C++
Python
Product Management
Mobile Applications
System Architecture
Shell Scripting
Javascript
Internet Protocol Suite
Software As A Service
Cdn
Content Distribution Networks
Media Delivery
Ios Development
Swift
Media Servers
Performance Engineering
High Availability Architecture
Mathematical Modeling
Energy Efficiency
Bottom Line Improvement
Cogs
Monitoring Performance
Overlay Networks
Computer Networking
Mobile Internet
Http/Https
3G
Lte
Linux
Linux Server
Https
Unix
C
Sql
Mobile Networking
Financial Modeling
Languages:
English

Publications

Us Patents

Content Delivery Network (Cdn) Cold Content Handling

View page
US Patent:
20120226649, Sep 6, 2012
Filed:
May 12, 2012
Appl. No.:
13/470262
Inventors:
Laszlo Kovacs - Foster City CA, US
Keith E. Oslakovic - Somerville MA, US
Mangesh Kasbekar - Cambridge MA, US
Zewei Chen - Somerville MA, US
Assignee:
AKAMAI TECHNOLOGIES, INC. - Cambridge MA
International Classification:
G06N 5/02
G06F 15/16
US Classification:
706 47
Abstract:
A method of content delivery in a content delivery network (CDN), where the CDN is deployed, operated and managed by a content delivery network service provider (CDNSP). The CDN comprises a set of content servers and a domain name system (DNS). For a given content provider, a determination is first made whether the content provider has “cold content” delivery requirements by evaluating one or more factors that include: total content size, size of content objects expected to be served, uniqueness of content, total number of content objects, and a percentage of the total content size that is expected to account for a given percentage of traffic. Upon a determination that the content provider has cold content delivery requirements, a subset of the CDN content servers are configured to implement a set of one or handling rules for managing delivery of the cold content from the CDN content servers.

Preventing Tcp From Becoming Too Conservative Too Quickly

View page
US Patent:
20140056136, Feb 27, 2014
Filed:
Aug 27, 2013
Appl. No.:
14/011021
Inventors:
Mangesh M. Kasbekar - New York NY, US
Assignee:
Akamai Technologies, Inc. - Cambridge MA
International Classification:
H04L 12/801
US Classification:
370230
Abstract:
A technique that addresses the problem of a TCP connection's throughput being very vulnerable to early losses implements a pair of controls around ssthresh. A first control is a loss forgiveness mechanism that applies to the first n-loss events by the TCP connection. Generally, this mechanism prevents new TCP connections from ending slow-start and becoming conservative on window growth too early (which would otherwise occur due to the early losses). The second control is a self-decay mechanism that is applied beyond the first n-losses that are handled by the first control. This mechanism decouples of ssthresh drop from cwnd and is thus useful in arresting otherwise steep ssthresh drops. The self-decay mechanism also enables TCP to enter/continue to be slow-start even after fast-recovery from a loss event.

Content Delivery Network (Cdn) Cold Content Handling

View page
US Patent:
8180720, May 15, 2012
Filed:
Jul 21, 2008
Appl. No.:
12/176806
Inventors:
Laszlo Kovacs - Foster City CA, US
Keith E. Oslakovic - Somerville MA, US
Mangesh Kasbekar - Cambridge MA, US
Zewei Chen - Somerville MA, US
Assignee:
Akamai Technologies, Inc. - Cambridge MA
International Classification:
G06F 17/00
G06N 5/02
US Classification:
706 47
Abstract:
A method of content delivery in a content delivery network (CDN), where the CDN is deployed, operated and managed by a content delivery network service provider (CDNSP). The CDN comprises a set of content servers and a domain name system (DNS) associated with a CDN namespace. For a given content provider, a determination is first made whether the content provider has “cold content” delivery requirements by evaluating one or more factors that include: total content size, size of content objects expected to be served, uniqueness of content, total number of content objects, and a percentage of the total content size that is expected to account for a given percentage of traffic. Upon a determination that the content provider has cold content delivery requirements, a subset of the CDN content servers are configured to implement a set of one or handling rules for managing delivery of the cold content from the CDN content servers.

Https Request Enrichment

View page
US Patent:
20200021614, Jan 16, 2020
Filed:
Sep 23, 2019
Appl. No.:
16/578746
Inventors:
- Cambridge MA, US
Mangesh Kasbekar - New York NY, US
International Classification:
H04L 29/06
H04L 29/08
Abstract:
This disclosure provides for a network element (in the middle) to inject enrichments into SSL connections, and for taking them out. This network element is sometimes referred to herein as a “middle box.” In the context of layered software architecture, this solution preferably is implemented by a library that operates below the SSL layer and above the TCP sockets layer at the two endpoints of the SSL connection. Preferably, the SSL enrichments are implemented as SSL/TLS records.

Preventing Tcp From Becoming Too Conservative Too Quickly

View page
US Patent:
20170346738, Nov 30, 2017
Filed:
Aug 14, 2017
Appl. No.:
15/675816
Inventors:
- Cambridge MA, US
Mangesh M. Kasbekar - New York NY, US
International Classification:
H04L 12/801
H04L 12/807
H04L 12/841
H04W 28/02
Abstract:
A technique that addresses the problem of a TCP connection's throughput being very vulnerable to early losses implements a pair of controls around ssthresh. A first control is a loss forgiveness mechanism that applies to the first n-loss events by the TCP connection. Generally, this mechanism prevents new TCP connections from ending slow-start and becoming conservative on window growth too early (which would otherwise occur due to the early losses). The second control is a self-decay mechanism that is applied beyond the first n-losses that are handled by the first control. This mechanism decouples of ssthresh drop from cwnd and is thus useful in arresting otherwise steep ssthresh drops. The self-decay mechanism also enables TCP to enter/continue to be slow-start even after fast-recovery from a loss event.

Content Delivery Network (Cdn) Cold Content Handling

View page
US Patent:
20170279916, Sep 28, 2017
Filed:
Jun 12, 2017
Appl. No.:
15/620210
Inventors:
- Cambridge MA, US
Mangesh Kasbekar - Cambridge MA, US
Zewei Chen - Somerville MA, US
Assignee:
Akamai Technologies, Inc. - Cambridge MA
International Classification:
H04L 29/08
Abstract:
A method of content delivery in a content delivery network (CDN), where the CDN is deployed, operated and managed by a content delivery network service provider (CDNSP). The CDN comprises a set of content servers and a domain name system (DNS). For a given content provider, a determination is first made whether the content provider has “cold content” delivery requirements by evaluating one or more factors that include: total content size, size of content objects expected to be served, uniqueness of content, total number of content objects, and a percentage of the total content size that is expected to account for a given percentage of traffic. Upon a determination that the content provider has cold content delivery requirements, a subset of the CDN content servers are configured to implement a set of one or handling rules for managing delivery of the cold content from the CDN content servers.

Https Request Enrichment

View page
US Patent:
20160094581, Mar 31, 2016
Filed:
Sep 29, 2015
Appl. No.:
14/868771
Inventors:
- Cambridge MA, US
Mangesh Kasbekar - New York NY, US
International Classification:
H04L 29/06
Abstract:
This disclosure provides for a network element (in the middle) to inject enrichments into SSL connections, and for taking them out. This network element is sometimes referred to herein as a “middle box.” In the context of layered software architecture, this solution preferably is implemented by a library that operates below the SSL layer and above the TCP sockets layer at the two endpoints of the SSL connection. Preferably, the SSL enrichments are implemented as SSL/TLS records.
Control profile
Mangesh M Kasbekar from New York, NY, age ~51 Get Report