Where results make sense

About us   |   Why use us?   |   Reviews   |   PR   |   Contact us

Topic: RSVP-TE

    Note: these results are not from the primary (high quality) database.

Ads by Google

In the News (Wed 23 Dec 09)

Northern Trust

Marvin Harrison

Peter Chernin

Gary Locke

Match Play

Penelope Cruz

Mickey Rourke

AR Rahman

Danny Boyle

Hugh Jackman

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

SWITCH - Projects - TF-NGN RFC 3209: RSVP-TE: Extensions to RSVP for LSP Tunnels RFC 3210: Applicability Statement for Extensions to RSVP for LSP-Tunnels RFC 2207: RSVP Extensions for IPSEC Data Flows www.switch.ch /tf-tant/references/rsvp.html   (1055 words)

IDEO Laboratories GmbH is an consulting and research company with individual development and optimization of future telecommunication networks (UMTS WLAN WiMAX GSM 4G MPLS NS2 RSVP) and logistics IDEO Laboratories GmbH is an consulting and research company with individual development and optimization of future telecommunication networks (UMTS WLAN WiMAX GSM 4G MPLS NS2 RSVP) and logistics IDEO Laboratories offers a patch for the RSVP-TE protocol in NS2. However, a lot of other proposals (like the RSVP-TE or HELLO extensions [RFC, 3209]) add message types for new messages. www.ideo-labs.com /index.php?structureID=44&sid=7fab3f5fa212e6d5aeb5da533ce0f003   (745 words)

RFC 3476 - Documentation of IANA Assignments for Label Distribution Protocol (LDP), Resource ReSerVation Protocol (RSVP), and Resource ReSerVation Protocol-Traffic Engineering (RSVP-TE) Extensions for Optical UNI Signaling. B. Rajagopalan. 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. 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. Abstract The Optical Interworking Forum (OIF) has defined extensions to the Label Distribution Protocol (LDP) and the Resource ReSerVation Protocol (RSVP) for optical User Network Interface (UNI) signaling. rfc.sunsite.dk /rfc/rfc3476.html   (745 words)

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

draft-zamfir-explicit-resource-control-bundle-05.txt Zamfir, A., Ali, Z., Papadimitriou, D [Page 7] draft-zamfir-explicit-resource-control-bundle-05.txt June 2005 If U-bit of the subobject being examined is cleared (0) and the upstream interface specified in this subobject is acceptable, then the value of the upstream component interface is translated locally in the TLV of the IF_ID RSVP HOP object [RFC 3471]. When the destination node of an RSVP session receives a Path message with an RRO and the "Component Link Recording desired" flag set, this indicates that the sender node needs TE route as well as component link recording. Zamfir, A., Ali, Z., Papadimitriou, D [Page 5] draft-zamfir-explicit-resource-control-bundle-05.txt June 2005 Note also that, unlike Labels, Component Link identifiers are always known on receipt of the Path message. sunsite.utk.edu /ftp/usr-218-2/internet-drafts/draft-zamfir-explicit-resource-control-bundle-05.txt   (88 words)

Length field in Label ERO subobject Hi all, I have a question about the RSVP Label ERO subobject defined in section 5 of draft-ietf-mpls-generalized-rsvp-te-03. In this subobject, the Length field is defined to be one byte in size. Such a label could not be represented in the Label ERO subobject as it stands. psg.com /lists/ccamp/ccamp.2001/msg00290.html   (160 words)

rfc3468.txt Development of this type of signalling protocol took two different tracks: - extensions to RSVP for setting up MPLS tunnels [RFC3209] - extensions to LDP for setting constraint based LSPs [RFC3212] The motivation for the choice of protocol in both cases was straightforward. Extending RSVP-TE to do in an MPLS environment what it already was doing (handling QoS information and reserving resources) in an IP environment is comprehensible; you only have to add the label distribution capability. Extending a native MPLS Andersson & Swallow Informational [Page 3] RFC 3468 Decision on MPLS Signaling Protocols February 2003 protocol like LDP, which was designed to do label distribution, to handle some extra TLVs with QoS information is also not revolutionary. www.simpleweb.org /ietf/rfcs/complete/rfc3468.txt   (1774 words)

rfc3468.txt Development of this type of signalling protocol took two different tracks: - extensions to RSVP for setting up MPLS tunnels [RFC3209] - extensions to LDP for setting constraint based LSPs [RFC3212] The motivation for the choice of protocol in both cases was straightforward. Extending RSVP-TE to do in an MPLS environment what it already was doing (handling QoS information and reserving resources) in an IP environment is comprehensible; you only have to add the label distribution capability. Extending a native MPLS protocol like LDP, which was designed to do label distribution, to handle some extra TLVs with QoS information is also not revolutionary. web.mit.edu /afs/athena/reference/rfc/authors/rfc3468.txt   (1713 words)

draft-lefaucheur-rsvp-dste-01.txt Because, as pointed out in the previous section, the IP TTL may have been decremented by the penultimate hop router in some situations and thus be different from the RSVP TTL, the Deaggregator must not set the Break bit in the Adspec even if the IP TTL is different from the Le Faucheur, et al. We note that, in this case, the Penultimate Router would still decrement the IP TTL in the IP Header of the Path message while it would not decrement the RSVP TTL. When Penultimate Hop Popping is used, the penultimate Router will pop the tunnel label and, if no other label was imposed by the Aggregator, the Path message will then be exposed. faqs.org /ftp/pub/pub/internet-drafts/draft-lefaucheur-rsvp-dste-01.txt   (3897 words)

RSVP ERO subobject IPv4 address Hi, In RSVP-TE, the format of subobject 1: IPv4 address (4.4.1.1) is 0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1 Type From the implementation point of view, it should be much easy to put IPv4 address in a single word. www.atm.tut.fi /list-archive/rsvp/msg00350.html   (84 words)

Signalling protocol work in Q.14/15 G.7713.2, which is based on the GMPLS RSVP-TE signalling protocol The plan is to reach consent on the draft recommendations in the upcoming ITU-T Study Group 15 meeting in January 20 — 31, 2003. G.7713.3, which is based on the GMPLS CR-LDP signalling protocol www.ietf.org /IESG/LIAISON/file24.htm   (153 words)

Zvon - RFC 3473 [Generalized Multi-Protocol Label Switching (GMPLS) Signaling Resource ReserVation Protocol-Traffic Engineering (RSVP-TE) Extensions] - Contributors Zvon - RFC 3473 [Generalized Multi-Protocol Label Switching (GMPLS) Signaling Resource ReserVation Protocol-Traffic Engineering (RSVP-TE) Extensions] - Contributors www.zvon.org /tmRFC/RFC3473/Output/chapter16.html   (153 words)

iwata-mpls-crankback-00.txt We propose the use of crankback routing in CR-LDP and RSVP-TE. Therefore, the alternate routing should be indicated based on an explicit indication (as in examples 2 and 5), and it is best to know the following information separately: a) where blockage/congestion occurred (as in examples 2-3), and b) whether alternate routing "should" be attempted even if there is no "blockage" (as in example 4). Since the crankback routing may happen more than once for establishing an specific LSP, the history table of all experienced blockages for this LSP should be maintained to perform an accurate path computation to detour the blockages. www.ietf.org /proceedings/01mar/I-D/iwata-mpls-crankback-00.txt   (7891 words)

label distribution protocol RSVP-TE, LDP, TDP and MP-BGP for VPN label distribution. cell-relay.indiana.edu /mhonarc/mpls/2001-Nov/msg00090.html   (29 words)

Bell Labs Research China Publications [1] Zhiyu Zhou, and Donghui Gao, "An Efficient Adaptation of RSVP-TE in GMPLS", Proceedings of the 2004 International Symposium on Performance Evaluation of Computer and Telecommunication Systems (SPECTS’2004), pp. [1] J. Qiu, R. Hao and X. Li, "The Optimal Rate-limiting Timer of BGP for Routing Convergence", accepted by IEICE Transactions on Communications, special issue on Internet Technology, Nov., 2004. [1] Jianping Zheng, Keqin Li, Zhimei Wu, "Selection Algorithms for Anycast Relay Routing," Proceedings of the 2004 IEEE International Performance, Computing and Communications Conference, Edited by Hossam Hassanein, Richard L. Oliver, Golden G. Richard III, and Linda F. Wilson, Phoenix, Arizona, USA, April 15-17, 2004, pp.21-28 View www.blrc.edu.cn /blrcweb/publication.htm   (29 words)

Telecommunications: Signaling in MPLS Networks With RSVP-TE - Technology Information Telecommunications: Signaling in MPLS Networks With RSVP-TE - Technology Information FindArticles > Computers and Technology > Telecommunications > Nov, 2000 > Article Computer network equipment industry / Equipment and supplies www.findarticles.com /p/articles/mi_m0TLC/is_11_34/ai_67447072   (1396 words)

draft-kim-ccamp-interaction-grsvpte-lcas-00.txt When a signaling protocol such as GMPLS RSVP-TE and LCAS are used together within a node and the bi- directional connection is requested over the same route, the relevant requirements are identified to avoid the initiation process of egress node by EMS or NMS systems. The LCAS protocol handled by ITU-T is a protocol that is used to change the bandwidth capacity of a virtual concatenated signal used by transport networks (i.e. Introduction As described in [G.7042], LCAS is a link capacity adjustment scheme that should be used to increase or decrease the capacity of a container that is transported in an SDH/OTN network using Virtual Concatenation(VC). www.faqs.org /ftp/pub/pub/internet-drafts/draft-kim-ccamp-interaction-grsvpte-lcas-00.txt   (1748 words)

Multiprotocol Label Switching (mpls) Charter MPLS Upstream Label Assignment for RSVP-TE (17014 bytes) MPLS Upstream Label Assignment for LDP (19923 bytes) ICMP Extensions for MultiProtocol Label Switching (13174 bytes) www.ietf.org /html.charters/mpls-charter.html   (1128 words)

draft-ietf-mpls-nodeid-subobject-06.txt Signaling node-ids in RROs As mentioned above, the limitation that we need to address is the generality of the contents of the RRO IPv4 and IPv6 sub-objects, as defined in [RSVP-TE]. A PLR can make sure that condition (1) is met by examining the Record Route Object (RRO) of the primary tunnel to see if any of the addresses specified in the RRO is attached to the tail-end of the backup tunnel. 2) Add an IPv4/IPv6 sub-object recording the interface address and, when required, add a node-id subobject in the RRO object. www.ietf.org /internet-drafts/draft-ietf-mpls-nodeid-subobject-06.txt   (1970 words)

NextHop :: Welcome to NextHop GateD NGC now builds on this legacy and adds support for MPLS, LDP, RSVP-TE and Virtual Routing. Thank you for your interest in the GateD routing software and the industry consortium that pioneered the de facto standard for network routing. NextHop Technologies has acquired all the rights to GateD from Merit and the University of Michigan. www.gated.org   (392 words)

Try your search on: Qwika (all wikis)

About us   |   Why use us?   |   Reviews   |   Press   |   Contact us   Copyright © 2005-2007 www.factbites.com Usage implies agreement with terms.