Control of host/server processing overload...
<[email protected]> Fri, 11 Jun 2004 10:09:49 +0100
| Newsgroups | gmane.ietf.tewg |
|---|---|
| Message-ID | <0AAF93247C75E3408638B965DEE11A700543DCFB@i2km41-ukdy.domain1.systemhost.net> |
Hello, I am interested in understanding if the Internet Traffic Engineering = Working Group has considered the following issue: control of processing = overload of hosts/servers running protocols such as DNS, LDAP, SIP, = HTTP, COPS, SNMP, Radius, and Diameter.=20 My impression from a brief trawl is that, within the IETF, much thought = has been, and is being, given to the management of bandwidth and router = congestion, but almost none to control of host and server processing = overload. Indeed, although some of the above listed protocols do provide = response or status codes that might be used to indicate processing = overload, I have found none which explicitly specifies an overload = control mechanism. The same conclusion also seems to apply to the following non-IETF = protocols: H.323, SOAP, SAML, SMPP, and Parlay. This contrasts with the telephony/ATM world where there are examples of = protocols that have built-in overload control features: INAP, ISUP, = BICC, PNNI and more recently H.248.11. Such controls are crucial during = extremes of network operation where surges of service requests (or = Denial of Service attacks) can be an order of magnitude greater than = normal demand levels.=20 Please can you advise me of any work that is addressing this area. Thanks in advance for your help Martin Whitehead=20 BTexact Performance Engineering Critical Solutions Performance =20 Tel. 01473 605430 Fax 01473 623 BT MeetMe 0870 241 2993 Participant passcode 137305=20 PP 9, Floor 1 Orion Building, Adastral Park, Martlesham Heath. Ipswich, = Suffolk IP5 3RE BTexact is a trademark of British Telecommunications plc Registered office: 81 Newgate Street London EC1A 7AJ Registered in England no. 1800000 This electronic message contains information from British = Telecommunications plc which may be privileged or confidential. The = information is intended to be for the use of the individual(s) or entity = named above. If you are not the intended recipient be aware that any = disclosure, copying, distribution or use of the contents of this = information is prohibited. If you have received this electronic message = in error, please notify us by telephone or email (to the numbers or = address above) immediately.