
	Where results make sense

Topic: Resource ReSerVation Protocol

	RFC 2205 (rfc2205) - Resource ReSerVation Protocol (RSVP) -- Version 1 Fun
		One reservation option concerns the treatment of reservations for different senders within the same session: establish a "distinct" reservation for each upstream sender, or else make a single reservation that is "shared" among all packets of selected senders.
		Another reservation option controls the selection of senders; it may be an "explicit" list of all selected senders, or a "wildcard" that implicitly selects all the senders to the session.
		This reservation may be thought of as a shared "pipe", whose "size" is the largest of the resource requests from all receivers, independent of the number of senders using it.
	www.faqs.org /rfcs/rfc2205.html (17353 words)

	RSVP (Resource Reservation Protocol) (Linktionary term)
		RSVP is an Internet signaling protocol that is used to set up a type of circuit across an IP network, primarily as a means of providing QoS, for real-time traffic such as voice and video.
		Reservations are negotiated with each network device along a route to a destination.
		If each device has resources to support the flow, a reserved path is set up.
	www.linktionary.com /r/rsvp.html (326 words)

	Resource-Reservation Protocol (RSVP)
		Reservations can be thought of as a shared pipe whose size is the largest of the resource requests for that link from all receivers, independent of the number of senders.
		FF reservations that are requested by different receivers but that select the same sender must be merged to share a single reservation in a given node.
		The RSVP protocol then is used to pass the request to all the nodes (routers and hosts) along the reverse data path(s) to the data source(s).
	www.cisco.com /univercd/cc/td/doc/cisintwk/ito_doc/rsvp.htm (3814 words)

	Resource Reservation Protocol (Site not responding. Last check: 2007-10-15)
		Resource Reservation Protocol (RSVP) is an IETF-defined (RFC 2205) signaling protocol that uses Integrated Services (Intserv) to convey QoS requests to the network.
		However, it is a signaling protocol, not a routing protocol.
		Carries the bandwidth reservation request to each network device or hop (routers, switches, or proxies) responsible for managing resources in the data path between the sender and receiver (end nodes).
	www.microsoft.com /resources/documentation/Windows/2000/server/reskit/en-us/cnet/cndc_qos_ctam.asp (716 words)

	RFC 2205 - Resource ReSerVation Protocol (RSVP) -- Version 1 Functional Specification. R. Braden, Ed., L. Zhang, S. ... (Site not responding. Last check: 2007-10-15)
		A successful reservation request propagates upstream along the multicast tree until it reaches a point where an existing reservation is equal or greater Braden, Ed., et.
		RFC 2205 RSVP September 1997 Symbolically, we can represent an elementary FF reservation request by: FF(S{Q}) where S is the selected sender and Q is the corresponding flowspec; the pair forms a flow descriptor.
		RFC 2205 RSVP September 1997 and "Is this user allowed to make this reservation?" These two decisions are termed the "admission control" decision and the "policy control" decision, respectively, and both must be favorable in order for RSVP to make a reservation.
	rfc.sunsite.dk /rfc/rfc2205.html (16435 words)

	Resource Reservation Protocol, RSVP
		Resource Reservation Protocol (RSVP) is a signalling protocol, it does not attempt to control QoS itself: that is the scope of some or possibly several other protocols.
		An audio application might be an example of a shared reservation, even though each sender also emits a distinct data stream that requires admission and management in a queue.
		A Wild Card reserves bandwidth and delay characteristics for any sender, and is limited by the list of source addresses carried in the reservation message.
	www.netcraftsmen.net /welcher/papers/rsvp.html (1498 words)

	RSVP-TE: Resource Reservation Protocol: Trafic Extension RFC 3209
		The RSVP-TE protocol is an addition to the RSVP protocol for establishing label switched paths (LSPs) in MPLS networks.
		The extended RSVP protocol (RSVP-TE) supports the instantiation of explicitly routed LSPs, with or without resource reservations.
		Protocol Structure - RSVP-TE Resource Reservation Protocol - Traffic Extension Apart from the existing message types listed in RSVP an additional message type is available:
	www.javvin.com /protocolRSVPTE.html (312 words)

	RSVP, Resource ReSerVation Protocol
		RSVP is a unicast and multicast signalling protocol, designed to install and maintain reservation state information at each router along the path of a stream of data.
		From henceforth, the acronym RSVP on its own is used as a shorthand for the signalling protocol combined with the integrated service specifications.
		[RFC 3175] Aggregation of RSVP for IPv4 and IPv6 Reservations.
	www.networksorcery.com /enp/protocol/rsvp.htm (560 words)

	RSVP Protocol Overview (Site not responding. Last check: 2007-10-15)
		To make a resource reservation at a node, the RSVP daemon communicates with two local decision modules, admission control and policy control.
		The reservation for a single receiver does not need to travel to the source of a multicast tree; rather it travels only until it reaches a reserved branch of the tree.
		As routing changes paths to adapt to topology changes, RSVP adapts its reservation to the new paths wherever reservations are in place.
	www.isi.edu /div7/rsvp/overview.html (382 words)

	[No title] (Site not responding. Last check: 2007-10-15)
		With the addition of the 'Null Service Type' [NULLSERV], RSVP is also being adopted by mission critical applications that require some form of prioritized service, but cannot quantify their resource requirements.
		In cases where RSVP cannot travel end-to-end, these applications may still benefit from reservations that are not truly end-to-end, but that are 'proxied' by a network node on the data path between the sender and the receiver(s).
		RSVP Receiver Proxy is an extension to the RSVP message processing (not to the protocol itself) in which an intermediate network node originates the Resv message on behalf of the receiver(s) identified by the Path message.
	www.ietf.org /ids.by.wg/rsvp.html (162 words)

	Resource Reservation Protocol (RSVP) from Cisco Systems White Papers at Builder UK (Site not responding. Last check: 2007-10-15)
		Resource Reservation Protocol (RSVP) from Cisco Systems White Papers at Builder UK Home
		The Resource Reservation Protocol (RSVP) is a network-control protocol that enables Internet applications to obtain special qualities of service (QoSs) for their data flows.
		RSVP is not a routing protocol; instead, it works in conjunction with routing protocols and installs the equivalent of dynamic access lists along the routes that routing protocols calculate.
	uk.builder.com /whitepapers/0,39026692,60019024p-39000788q,00.htm (160 words)

	RSVP - Resource ReSerVation Protocol Software from FutureSoft
		The FutureSoft RSVP software is a portable implementation of RSVP (Resource ReSerVation Protocol) which includes both, the host and router functions.
		This feature is especially useful in the case where the hosts in the customer network(s) are not RSVP enabled, and the border/edge router has to initiate resource reservation.
		FutureSoft RSVP is easily ported to various architectures and reduces the time to market for OEMs and VARs who need to provide resource reservation initiation and signaling of the requested QoS parameters using RSVP.
	www.futsoft.com /german/rsvp.htm (333 words)

	[No title]
		Standards Track [Page 8] RFC 2205 RSVP September 1997 The exact format of a filter spec depends upon whether IPv4 or IPv6 is in use; see Appendix A. In the most general approach [RSVP93], filter specs may select arbitrary subsets of the packets in a given session.
		Standards Track [Page 27] RFC 2205 RSVP September 1997 and "Is this user allowed to make this reservation?" These two decisions are termed the "admission control" decision and the "policy control" decision, respectively, and both must be favorable in order for RSVP to make a reservation.
		The reservation scope, i.e., the set of senders towards which a particular reservation is to be forwarded (after merging), is determined as follows: o Explicit sender selection The reservation is forwarded to all senders whose SENDER_TEMPLATE objects recorded in the path state match a FILTER_SPEC object in the reservation.
	www.ietf.org /rfc/rfc2205.txt (14500 words)

	Resource Reservation Setup Protocol (rsvp) Charter (Site not responding. Last check: 2007-10-15)
		Its major features include: (1) the use of ``soft state'' in the routers, (2) receiver-controlled reservation requests, (3) flexible control over sharing of reservations and forwarding of subflows, and (4) the use of IP multicast for data distribution.
		The primary purpose of this working group is to evolve the RSVP specification and to introduce it into the Internet standards track.
		Resource ReSerVation Protocol (RSVP) -- Version 1 Functional Specification.
	www.ietf.cnri.reston.va.us /proceedings/96mar/charters/rsvp-charter.html (278 words)

	Resource ReSerVation Protocol---RSVP
		The RSVP protocol is also used by routers to deliver QoS control requests to all nodes along the path(s) of the flows and to establish and maintain state to provide the requested service.
		RSVP is also not a routing protocol but is intended to cooperate with unicast and multicast routing protocols.
		In addition, either one reservation can be shared among the flows within a session, or a distinct reservation is made for each data sender.
	www4.informatik.uni-erlangen.de /Projects/JRTP/pmt/node25.html (1664 words)

	RSVP for Mobile Hosts (Site not responding. Last check: 2007-10-15)
		The wireless network model we use, is a cellular type of network where only the last hop is wireless and the classical Mobile IP (RFC 2002) model is used for mobility.
		Figure 1 shows the message exchange needed to restore the RSVP reservation when a mobile node moves from one cell to another.
		In the case depicted in Figure 1, the mobile host is a receiver but similar signaling occurs when the mobile node is the sender.
	irl.cs.ucla.edu /~andreas/mobile.html (456 words)

	RFC 3476 - Documentation of IANA Assignments for Label Distribution Protocol (LDP), Resource ReSerVation Protocol ... (Site not responding. Last check: 2007-10-15)
		Specifically, the following IETF specifications are used: o Label distribution protocol (LDP) [6] o Resource reservation protocol (RSVP) [5] o GMPLS signaling and GMPLS extensions for SONET/SDH [4] o GMPLS RSVP-TE and CR-LDP extensions [2, 3] The aim of the OIF UNI specification is the maximal re-use of IETF protocol definitions.
		A few extensions to IETF protocols, however, have been defined to serve UNI-specific needs.
		RFC 3476 LDP and RSVP Extensions for Optical UNI Signaling March 2003 [3] Ashwood-Smith, P. and L. Berger, Editors, "Generalized Multi- Protocol Label Switching (MPLS) Signaling Constraint-based Routed Label Distribution Protocol (CR-LDP) Extensions", RFC 3472, January 2003.
	rfc.sunsite.dk /rfc/rfc3476.html (1794 words)

	Resource ReSerVation Protocol API (RAPI) - RAPI Objects
		RSVP defines several data objects which carry resource reservation information but are opaque to RSVP itself.
		The usage and data format of those objects is given in the referenced document RFC 2210.
		The rapi_policy_t type is a framework to carry the aforementioned integrity policy object.
	www.opengroup.org /onlinepubs/9619099/chap5.htm (439 words)

	Scheduling Software for Conferences, Rooms, Meetings, and Facilities - Asset Management Software - NetSimplicity
		Move up to software specifically designed to solve your most frustrating office administration challenges: the scheduling of meeting rooms, equipment and resources, and the management of office assets.
		Perhaps you need to schedule, reserve or manage resources for your small team, or, your entire corporation.
		Then consider taking our Resource Scheduler out for a trial run.
	www.netsimplicity.com (318 words)

	Model Library: RSVP (Site not responding. Last check: 2007-10-15)
		Initiate and Close RSVP processing for a given TCP/UDP session this includes making reservation decision making after a path or reservation error message is received
		Unsuccessful reservations can be re-attempted for selected senders, after the configurable timeout and with user specified reservation parameters
		Determine which reservation styles study is best suited for a given application type
	www.opnet.com /products/library/rsvp.html (267 words)

	EnterpriseVoIPplanet.com - www.voipplanet.com - The IT Manager's Guide to Voice Over IP
		The Differentiated Services architecture is a built-in feature of the Internet protocol that allows the coding of traffic streams for special treatment.
		The Resource Reservation Protocol—RSVP for short—is akin to the police traffic-directing detail that keeps a motorcade route open and trouble free.
		This mother of all QoS solutions tracks flows, schedules packets, and generally manages network resources to ensure adequate bandwidth for the services running at any given time.
	www.voipplanet.com (705 words)

	RSVP - Resource Reservation Protocol (Site not responding. Last check: 2007-10-15)
		TCP/IP may still run without RSVP which is a “service class” of an RSVP capable network
		TCP and UDP are supported to run on top of RSVP(also other protocols could be used)
		RSVP must be implemented in Hosts and Routers
	www.uni-kl.de /AG-Mueller/icsy0404/inhalte/vorlesung/html/tsld112.htm (56 words)

	RFC 2205
		This document specifies an Internet standards track protocol for the Internet community, and requests discussion and suggestions for improvements.
		This memo describes version 1 of RSVP, a resource reservation setup protocol designed for an integrated services Internet.
		Complete HTML RFC (TAR, TGZ, or ZIP format)
	www.freesoft.org /CIE/RFC/2205 (320 words)

	KnowledgeStorm - The Enterprise Software, Hardware, Services, and White Papers Resource (Site not responding. Last check: 2007-10-15)
		Generate leads and get broad exposure for your white papers, product or solution information, Webcasts, case studies and analyst reports.
		Benefits Administration, Employee Appraisal Solutions, Employee Self-Service Solutions, Human Capital Management, Integrated Human Resources Utilities, Personnel Administration, Professional Services Automation, Recruiting, Staffing and Applicant Tracking, Temporary and Contract Labor Management, Time & Attendance, Workforce Management
		Issue Tracking and Management, IT Portfolio Management, Professional Services Automation, Project Accounting, Requirements Management, Resource Planning and Scheduling, Time Reporting
	www.KnowledgeStorm.com (911 words)

Try your search on: Qwika (all wikis)