<html>
<head>
<meta http-equiv="Content-Type" content="text/html; charset=utf-8">
</head>
<body dir="auto">
<div>Este es uno de los BOFs que ya se aprobaron para Berlin.</div>
<div><br>
</div>
<div>Si estan interesados por favor unanse a la lista.</div>
<div><br>
</div>
<div>Alvaro.<br>
<br>
Sent from my iPhone</div>
<div><br>
Begin forwarded message:<br>
<br>
</div>
<blockquote type="cite">
<div><b>From:</b> Stewart Bryant <<a href="mailto:stbryant@cisco.com">stbryant@cisco.com</a>><br>
<b>Date:</b> June 20, 2013, 3:06:50 PM EDT<br>
<b>To:</b> <<a href="mailto:routing-discussion@ietf.org">routing-discussion@ietf.org</a>><br>
<b>Cc:</b> <<a href="mailto:status@ietf.org">status@ietf.org</a>><br>
<b>Subject:</b> <b>[Status] Status BOF in Berlin</b><br>
<b>Reply-To:</b> <<a href="mailto:stbryant@cisco.com">stbryant@cisco.com</a>><br>
<br>
</div>
</blockquote>
<blockquote type="cite">
<div>
<h4 id="STATUS">STATUS</h4>
<ul>
<li>Name: Stacked Tunnels for Source Routing (STATUS) [Was TUBAS] </li><li>Status: Approved </li><li>Description </li></ul>
<blockquote>
<p>The IETF has two packet-based forwarding technologies: IP and MPLS. </p>
</blockquote>
<blockquote>
<p>IP previously had a source-based routing mechanism made available through an IP Option. This mechanism has, however, not been widely used and has a number of issues that make its use inadvisable, and other mechanisms (such as
<a href="http://tools.ietf.org/html/rfc1940" class="wiki">RFC 1940</a>) do not appear to have been implemented at all.
</p>
</blockquote>
<blockquote>
<p>The ability of a router to influence or control the forwarding path of an individual packet or all the packets of a given Forwarding Equivalence Class (FEC) is a desirable feature for a number of reasons including Label Switched Path stitching, egress protection,
explicit routing, egress ASBR link selection, and backup (bypass tunnels, Remote Loop-Free Alternates) routing. This can be achieved by facilitating source-initiated selection of routes to complement the route selection provided by existing routing protocols
for both inter- domain and intra-domain routes. </p>
</blockquote>
<blockquote>
<p>Historically, distribution of MPLS label binding information was done by relying on label distribution protocols such as LDP and RSVP-TE.
</p>
</blockquote>
<blockquote>
<p>Several new proposals have been made to make use of the MPLS forwarding plane in novel but backward-compatible ways, and to install forwarding instructions using information distributed by the IGP running in the network, or through the management plane.
It has been suggested that similar mechanisms might also be applied in IPv6. </p>
</blockquote>
<blockquote>
<p>This BoF is intended to discuss the practicalities of various use cases and to establish a consensus around the problem space and desirability of developing solutions in this area with a view to determining whether the IETF should have a Working Group on
this topic.</p>
</blockquote>
<ul>
<li>Responsible Area Directors: Adrian Farrel and Stewart Bryant </li><li>BoF Chairs: Alvaro Retana, John Scudder </li><li><br>
</li><li>Mailing list: <a class="ext-link" href="https://www.ietf.org/mailman/listinfo/status">
<span class="icon"></span>https://www.ietf.org/mailman/listinfo/status</a> </li></ul>
<p>Further details can be found at <a href="http://trac.tools.ietf.org/bof/trac/wiki">
http://trac.tools.ietf.org/bof/trac/wiki</a><br>
</p>
<p>- Stewart<br>
</p>
</div>
</blockquote>
<blockquote type="cite">
<div><span>_______________________________________________</span><br>
<span>status mailing list</span><br>
<span><a href="mailto:status@ietf.org">status@ietf.org</a></span><br>
<span><a href="https://www.ietf.org/mailman/listinfo/status">https://www.ietf.org/mailman/listinfo/status</a></span><br>
</div>
</blockquote>
</body>
</html>