
	Where results make sense

Topic: RFC 1819

Related Topics

POP3

Address Resolution Protocol

Transmission Control Protocol

Barrister

Sibayak

Derby hat

In the News (Tue 1 Dec 09)

Northern Trust

Marvin Harrison

Peter Chernin

Gary Locke

Match Play

Penelope Cruz

Mickey Rourke

AR Rahman

Danny Boyle

Hugh Jackman

	RFC 2383 - ST2+ over ATM Protocol Specification - UNI 3.1 Version
		RFC 2383 ST2+ over ATM August 1998 In the original definition of the Controlled-Load Service, the value of the [m] field must be less than or equal to the value of the [M] field.
		RFC 2383 ST2+ over ATM August 1998 When a PVC is selected for a hop of a stream, at least confirmations, that is the state of the PVC is vacant and the next hop IP address and QoS are consistent with the requirements from the stream, may be needed.
		RFC 2383 ST2+ over ATM August 1998 Acknowledgments ATM is a huge technology and without the help of many colleagues at NTT who are involved in ATM research and development, it would have been impossible for me to complete this protocol specification.
	www.muonics.com /rfc/rfc2383.php (11417 words)

	RFC 2383 (rfc2383) - ST2+ over ATM Protocol Specification - UNI 3.1 Version
		The specifications of the ST2+ over ATM protocol consist of a revision of RFC 1819 ST2+ and specifications of protocol interaction between ST2+ and ATM on the user plane, management plane, and control plane which correspond to the three planes of the B-ISDN protocol reference model.
		Revision of RFC 1819 ST2+ To specify the ST2+ over ATM protocol, the functions in RFC 1819 ST2+ must be extended to support ATM.
		This is because the descriptions of the stream recovery process in RFC 1819 (Sections 5.3.2, 6.2, and 6.2.1) are unclear and incomplete.
	www.faqs.org /rfcs/rfc2383.html (10903 words)

	RFC1819 (Site not responding. Last check: 2007-10-19)
		RFC 1819 ST2+ Protocol Specification August 1995 It is also assumed that the LRM provides functions to compare flow specifications, i.e., to decide whether a flow specification requires a greater, equal, or smaller amount of resource capacities to be reserved.
		RFC 1819 ST2+ Protocol Specification August 1995 number, a priority field (specifying a relative importance of streams in cases of conflict), a length counter, a stream identification, and a checksum.
		RFC 1819 ST2+ Protocol Specification August 1995 The membership of a stream in a group may affect the amount of resources that have to be allocated by the LRM, see Section 7.
	rfc.net /rfc1819.html (14803 words)

	RFC 1819 (rfc1819)
		Delgrossi & Berger, Editors Experimental [Page 13] RFC 1819 ST2+ Protocol Specification August 1995 It is also assumed that the LRM provides functions to compare flow specifications, i.e., to decide whether a flow specification requires a greater, equal, or smaller amount of resource capacities to be reserved.
		Delgrossi & Berger, Editors Experimental [Page 29] RFC 1819 ST2+ Protocol Specification August 1995 4.1.1 Stream Building Streams may be built in a sender-oriented fashion, receiver-oriented fashion, or with a mixed approach: o in the sender-oriented fashion, the application at the origin provides the ST agent with the list of receivers for the stream.
		Delgrossi & Berger, Editors Experimental [Page 58] RFC 1819 ST2+ Protocol Specification August 1995 If stream recovery is necessary, the different ST agents will need to perform different functions, depending on their relation to the failure: o An ST agent that is a next-hop from a failure should first verify that there was a failure.
	www.cse.ohio-state.edu /cgi-bin/rfc/rfc1819.html (16060 words)

	ITPRC - TCP/IP FAQ
		RFC 1122 summarises the requirements that must be met by an IP implementation in an Internet host, and RFC 1812 summarises the IP requirements for an Internet router.
		RFC 1141 and RFC 1624 describe incremental modification of an existing checksum, which can be useful in machines such as routers which modify fields in the IP header while forwarding a packet and therefore need to compute a new header checksum.
		RFC 1122 summarises the requirements that must be met by an ICMP implementation in an Internet host, and RFC 1812 summarises the ICMP requirements for an Internet router.
	www.itprc.com /tcpipfaq/faq-1.htm (5184 words)

	RFC 1946 (rfc1946)
		Jackowski Informational [Page 4] RFC 1946 Native ATM Support for ST2+ May 1996 In surveying protocols described in IETF RFCs and Internet Drafts, only two seem to meet these requirements: Experimental Internet Stream Protocol: Version 2 (RFC 1190) [4] and Internet STream Protocol Version 2+ (RFC 1819) [5]; ST2 and ST2+ respectively.
		This is because ST2+ was released as an RFC late in the summer of 1995.
		Jackowski Informational [Page 13] RFC 1946 Native ATM Support for ST2+ May 1996 One potential drawback to using LAN Emulation or SCMP messages encapsulated in IP over ATM, is the fact that there is no guarantee that the connectivity achieved to reach the target via signaling has any relationship to the data path.
	www.cse.ohio-state.edu /cgi-bin/rfc/rfc1946.html (6185 words)

	RFC 1818 - Best Current Practices
		Informational RFCs can be published on a less formal basis, subject to the reasonable constraints of the RFC editor.
		Informational RFCs are not subject to peer review and carry no significance whatsoever within the IETF process [4].
		RFC 1818 Best Current Practices August 1995 Possible examples of technical information to which BCPs could be applied are "OSI NSAP Allocation" [5], and "OSPF Applicability Statement" [6].
	www.muonics.com /rfc/rfc1818.php (426 words)

	RFCs @ Saint Roch Tree (tm)
		RFC 1822 - A Grant of Rights to Use a Specific IBM patent with Photuris.
		RFC 1838 - Use of the X.500 Directory to support mapping between X.400 and RFC 822 Addresses.
		RFC 1843 - HZ - A Data Format for Exchanging Files of Arbitrarily Mixed Chinese and ASCII characters.
	www.saintrochtree.com /zones/it/links/comtel-stand-ietf-all-1800.htm (563 words)

	[No title]
		The composition function may in practice be executed in a distributed fashion by the setup or routing protocol, or the characterization parameters may be gathered to a single point and the characterization computed at that point.
		The Shenker & Wroclawski Informational [Page 18] RFC 2216 Network Element Service Template September 1997 effect of this will be to limit packet sizes in the flow to those which can be handled by every instance of the service along the flow's path.
		Shenker & Wroclawski Informational [Page 19] RFC 2216 Network Element Service Template September 1997 o Guidelines for Implementors Many services may be defined in a manner which allows the range of behavior of a compliant network element to be rather broad.
	www.rfc-editor.org /rfc/rfc2216.txt (6984 words)

	[No title]
		The lack of this capability was found to be a significant limitation in the ability to scale the number of participants in a single ST stream.
		In the case of stream recovery, it will be propagated to the ST agent that is attempting the recovery, which may be an intermediate ST agent or the origin itself.
		The LRM may not be able to satisfy a particular request during stream setup or modification for a number of reasons, including a mismatched FlowSpec, an unknown FlowSpec version, an error in processing a FlowSpec, and an inability to allocate the requested resource.
	www.ietf.org /rfc/rfc1819.txt (16443 words)

	Computers Internet RFCs 1801 - 1900 (Site not responding. Last check: 2007-10-19)
		RFC 1857 - A Model for Common Operational Statistics.
		RFC 1871 - Addendum to RFC 1602 -- Variance Procedure.
		RFC 1876 - A Means for Expressing Location Information in the Domain Name System.
	www.iper1.com /iper1-odp/scat/id/Computers/Internet/RFCs/1801_-_1900 (806 words)

	RFC 1800 - 1899 (Site not responding. Last check: 2007-10-19)
		Obsoletes: RFC 1083, RFC 1100, RFC 1130, RFC 1140, RFC 1200, RFC 1250, RFC 1280, RFC 1360, RFC 1410, RFC 1500, RFC 1540, RFC 1600, RFC 1610, RFC 1720, RFC 1780.
		References: RFC 1112, RFC 1190, RFC 1363, RFC 1577, RFC 1583, RFC 1584, RFC 1633, RFC 1636, RFC 1755, RFC 1819, RFC 1825, RFC 1826.
		Obsoletes: RFC 1083, RFC 1100, RFC 1130, RFC 1140, RFC 1200, RFC 1250, RFC 1280, RFC 1360, RFC 1410, RFC 1500, RFC 1540, RFC 1600, RFC 1610, RFC 1720, RFC 1780, RFC 1800.
	www.networksorcery.com /enp/rfc1800.htm (1219 words)

	IP address
		They are used extensively due to the shortage of registerable addresses and therefore Network address translation is required to connect those networks to the Internet.
		What would be considered as IPv5 existed only as an experimental non-IP real time streaming protocol called ST2 described in RFC 1819.
		Further reading: Internet RFCs including RFC 791, RFC 1519 (IPv4 addresses), and RFC 2373 (IPv6 addresses).
	www.brainyencyclopedia.com /encyclopedia/i/ip/ip_address.html (987 words)

	RFCs 1800 - 1899 Index (Site not responding. Last check: 2007-10-19)
		The original RFC (RFC 1357) was written by D. Cohen, ISI, July 1992.This is a revision of RFC 1357.
		This RFC is intended to alert the IP community about the performance limitations of MD5, and to suggest that alternatives be considered for use in high speed IP implementations.
		This is a modification to the procedures of RFC 1602 and 1603.
	www.potaroo.net /ietf/rfc1800-1899.html (5005 words)

	[No title]
		Now consider the scenario where an incorrect or hurried routing change occurs and thus sends all of the traffic that was bound to the core router in company B to the e-mail host in company A. Both companies are instantly and dramatically impacted.
		It is important to note that neither company has the exclusive rights to that address as RFC 1819 declared that space "PRIVATE" and should not be used between two autonomous companies.
		By choosing to ignore RFC 1819 one company can impact another company’s ability to manage its own network effectively, which can result in many undesired effects.
	www.atis.org /esif/docs/ESIF_Issues_Files/ESIF-032.doc (1106 words)

	Diff: /away/ietf/rfc/rfc2383.txt - /away/ietf/all-ids/draft-suzuki-st2-over-atm-02.txt
		1819 appears in Appendix A. 1819 appears in Appendix A. 3.1 Extended Functions of RFC 1819 ST2+
		(RFC 1819, Section 4.4.1) with the S-bit set to 1.
		1819, Section 8.8), because this protocol does not support IP 1819, Section 8.8), because this protocol does not support IP encapsulation of ST.
	bgp.potaroo.net /cgi-bin/htmldiff?f1=rfc2383.txt&f2=draft-suzuki-st2-over-atm-02.txt (4991 words)

	1819 Kamehameha I April 4 July 19 Ezra Abbot April 28 March 3 Savannah, Georgia Panic of 1819 John Couch Adams August 7 (Site not responding. Last check: 2007-10-19)
		1816 1817 1818 - 1819 - 1820 1821 1822
		1819 was a common year starting on Friday (see link for calendar).
		This list contains all counties that have existed in Alabama since the state was created in 1819.
	en.powerwissen.com /8J0M5Mrno6HNJjhp276C9g==_1819.html (676 words)

	Berger, Lou (Site not responding. Last check: 2007-10-19)
		[RFC 2207] RSVP Extensions for IPSEC Data Flows.
		[RFC 2382] A Framework for Integrated Services and RSVP over ATM.
		[RFC 3209] RSVP-TE: Extensions to RSVP for LSP Tunnels.
	www.networksorcery.com /enp/authors/BergerLou.htm (88 words)

	RFC Index 1801 - 1900 - RFC Database - eLook.org
		RFC 1801 - MHS use of the X
		RFC 1802 - Introducing Project Long Bud: Internet Pilot Project for the Deployment of X
		RFC 1866 - Hypertext Markup Language - 2
	www.elook.org /computing/rfc/index19.html (710 words)

	The Internet Report (Site not responding. Last check: 2007-10-19)
		Since file-upload is a feature that will benefit many applications, this proposes an extension to HTML to allow information providers to express file upload requests uniformly, and a MIME compatible representation for file upload responses.
		This RFC describes a mechanism to allow the DNS to carry location information about hosts, networks, and subnets.
		This memo documents some experiences with the RFC 1797 [1] subnet A experiment (performed by the Net39 Test Group (see credits)) and provides a number of recommendations on future direction for both the Internet Registries and the Operations community.
	ietfreport.isoc.org /rfc1800-1899.html (5340 words)

	Re: rfc 1918? (Site not responding. Last check: 2007-10-19)
		As the stickie for holding that space, I field alot of spam complaints about drek that originates from RFC 1918 space.
		I really wish NATs were smart enough to rewrite SMTP headers...
		> > > > Scott > > > > AS long as you are filtering, could you -PLEASE- add the SMTP filter to > prevent email w/ RFC 1918 addresses in the headers from leaking out of > your networks?
	www.cctec.com /maillists/nanog/historical/0102/msg00810.html (139 words)

	Internet real-time new bandwidth protocols
		ST2+ (also called ST, ST2 or RFC 1819) is a new version of the base Internet protocol IP; RFC 1190 is now superseded.
		There is a new generation of IP (RFC 1883: IPng) with a version number of 6.
		However ST2+ is a version of IP with a version number of 5.
	www.phdcc.com /qos.html (576 words)

	RFC Index (1100 through 1199)
		RFC 0742) (Obsoleted by RFC 1288, RFC 1196) (Status: DRAFT STANDARD)
		RFC 1105) (Obsoleted by RFC 1267) (Status: HISTORIC)
		RFC 0958, RFC 1059) (Obsoleted by RFC 1305) (Status: STANDARD)
	www.lex-con.com /rfc/rfc-11.htm (917 words)

	[No title]
		Suzuki Informational [Page 1] RFC 2383 ST2+ over ATM August 1998 Therefore, in this document, ATM is only a subnet technology for the ST2+ stream.
		Suzuki Informational [Page 2] RFC 2383 ST2+ over ATM August 1998 o Support ST2+ stream across ATM and non-ATM networks.
		Suzuki Informational [Page 5] RFC 2383 ST2+ over ATM August 1998 2.2 Management Plane Architecture The management plane specifies the Null FlowSpec, the Controlled-Load Service [5] FlowSpec, and the Guaranteed Service [6] FlowSpec mapping rules [8] for UNI 3.1 traffic management.
	www.ietf.org /rfc/rfc2383.txt (1293 words)

	Articles - IP address (Site not responding. Last check: 2007-10-19)
		For this reason, the plan is that the Internet 128-bit IPv6 addressing scheme will be adopted over the next 5 to 15 years.
		This protocol was abandoned; RSVP has replaced it to some degree.
		IPv6 has many improvements over IPv4 other than just bigger address space, including autorenumbering and mandatory support for IPsec.
	www.ezorange.com /articles/IP_address (1106 words)

	Web Directory : Computers : Internet : RFCs : 1801 - 1900 (Site not responding. Last check: 2007-10-19)
		Web Directory : Computers : Internet : RFCs : 1801 - 1900
		Below are some useful links about 1801 - 1900 on RFCs:
		The content of this page about RFCs 1801 - 1900 is based on the Open Directory Project and has been modified.
	www.ebook2u.com /web/Computers/Internet/RFCs/1801_-_1900 (862 words)

	Information on ST2
		RFC 1190, Experimental Internet Stream Protocol: Version 2 (ST-II).
		Experimental Standard, 01 Oct 1990, TXT=386909 bytes, Obsoleted by RFC1819, see also ST2,
		RFC 2383, ST2+ over ATM Protocol Specification - UNI 3.1 Version.
	www.icir.org /netdb/protocols/ST2.html (365 words)

	Webmasters Internet Tools and Information Resources : RFCs : 1801 - 1900
		Webmasters Internet Tools and Information Resources : RFCs : 1801 - 1900
		Top : RFCs : 1801 - 1900
		Submit your Web site to the our directory!
	www.pjltechnology.com /links/RFCs/1801_-_1900 (147 words)

	hjp: doc: RFC 1819: Internet Stream Protocol Version 2 (ST2) Protocol Specification - Version ST2+
		hjp: doc: RFC 1819: Internet Stream Protocol Version 2 (ST2) Protocol Specification - Version ST2+
		Network Working Group ST2 Working Group Request for Comments: 1819 L. Delgrossi and L. Berger, Editors Obsoletes: 1190, IEN 119 August 1995 Category: Experimental
		The affected stream can be left in one of two states as a result of change failures: a) the stream can revert back to the state it was in prior to t
	www.hjp.at /doc/rfc/rfc1819.html (14214 words)

Try your search on: Qwika (all wikis)