<?xml version="1.0" encoding="UTF-8"?><rss version="2.0"
	xmlns:content="http://purl.org/rss/1.0/modules/content/"
	xmlns:dc="http://purl.org/dc/elements/1.1/"
	xmlns:atom="http://www.w3.org/2005/Atom"
	xmlns:sy="http://purl.org/rss/1.0/modules/syndication/"
		>
<channel>
	<title>Comments on: Network Fabric:TRILL for Server and Network People. Welcome RBridges</title>
	<atom:link href="http://etherealmind.com/trill-introduction-review-overview-why-what-how/feed/" rel="self" type="application/rss+xml" />
	<link>http://etherealmind.com/trill-introduction-review-overview-why-what-how/</link>
	<description>Network design, architecture, thinking, working. Tech.</description>
	<lastBuildDate>Thu, 18 Mar 2010 09:04:15 +0000</lastBuildDate>
	<generator>http://wordpress.org/?v=2.9.2</generator>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
		<item>
		<title>By: peter ashwood-smith</title>
		<link>http://etherealmind.com/trill-introduction-review-overview-why-what-how/comment-page-1/#comment-4695</link>
		<dc:creator>peter ashwood-smith</dc:creator>
		<pubDate>Wed, 17 Feb 2010 00:52:16 +0000</pubDate>
		<guid isPermaLink="false">http://etherealmind.com/?p=1492#comment-4695</guid>
		<description>There is a lot of good information on 802.1aq on wikipedia under &quot;IEEE 802.1aq&quot;.
We&#039;ve been trying to keep it up to date with whats happening at the IEEE. 

In particular the l2 multipathing work has progressed rather well and now allows 16 symmetric algorithms with additional opaque mechanisms for the addition of many more. What is very interesting about this work is that these are head end chosen so you get a lot of control over how traffic will be placed.</description>
		<content:encoded><![CDATA[<p>There is a lot of good information on 802.1aq on wikipedia under “IEEE 802.1aq”.<br />
We’ve been trying to keep it up to date with whats happening at the IEEE. </p>
<p>In particular the l2 multipathing work has progressed rather well and now allows 16 symmetric algorithms with additional opaque mechanisms for the addition of many more. What is very interesting about this work is that these are head end chosen so you get a lot of control over how traffic will be placed.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Donald Eastlake 3rd</title>
		<link>http://etherealmind.com/trill-introduction-review-overview-why-what-how/comment-page-1/#comment-3862</link>
		<dc:creator>Donald Eastlake 3rd</dc:creator>
		<pubDate>Sun, 08 Nov 2009 00:29:53 +0000</pubDate>
		<guid isPermaLink="false">http://etherealmind.com/?p=1492#comment-3862</guid>
		<description>The Referenced Internet Draft (​d​r​a​f​t​-​i​e​t​f​-​t​r​i​l​l​-​p​rob-06.txt) has now been published as RFC 5556.
See http://www.ietf.org/rfc/rfc5556.txt

The TRILL base protocol specification is now quite mature and the latest version is available at
​http://tools.ietf.org/html/draft-ietf-trill-rbridge-protocol-14

Thanks,
Donald</description>
		<content:encoded><![CDATA[<p>The Referenced Internet Draft (​d​r​a​f​t​-​i​e​t​f​-​t​r​i​l​l​-​p​rob-06.txt) has now been published as RFC 5556.<br />
See <a href="http://www.ietf.org/rfc/rfc5556.txt" rel="nofollow">http://www.ietf.org/rfc/rfc5556.txt</a></p>
<p>The TRILL base protocol specification is now quite mature and the latest version is available at<br />
​http://tools.ietf.org/html/draft-ietf-trill-rbridge-protocol-14</p>
<p>Thanks,<br />
Donald</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: DCB, CEE or DCE ? Whose term is best ? &#124; My Etherealmind</title>
		<link>http://etherealmind.com/trill-introduction-review-overview-why-what-how/comment-page-1/#comment-3710</link>
		<dc:creator>DCB, CEE or DCE ? Whose term is best ? &#124; My Etherealmind</dc:creator>
		<pubDate>Tue, 13 Oct 2009 12:54:39 +0000</pubDate>
		<guid isPermaLink="false">http://etherealmind.com/?p=1492#comment-3710</guid>
		<description>[...] is one other stand­ard that is import­ant. L2 Multipathing (L2MP) (which I have dis­cussed here) is going to be a vital part of mak­ing scal­able data centre net­works. There are two [...]</description>
		<content:encoded><![CDATA[<p>[…] is one other stand­ard that is import­ant. L2 Multipathing (L2MP) (which I have dis­cussed here) is going to be a vital part of mak­ing scal­able data centre net­works. There are two […]</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Donald Eastlake 3rd</title>
		<link>http://etherealmind.com/trill-introduction-review-overview-why-what-how/comment-page-1/#comment-3320</link>
		<dc:creator>Donald Eastlake 3rd</dc:creator>
		<pubDate>Fri, 04 Sep 2009 03:45:06 +0000</pubDate>
		<guid isPermaLink="false">http://etherealmind.com/?p=1492#comment-3320</guid>
		<description>OK. Thanks. It is true that the IEEE process is much more secretive than the IETF process. However, if you go back to your post, you will see that you typoed &quot;IEEE&quot; and &quot;IETF&quot; in the first line of your comment so I was confused.

Donald</description>
		<content:encoded><![CDATA[<p>OK. Thanks. It is true that the IEEE process is much more secretive than the IETF process. However, if you go back to your post, you will see that you typoed “IEEE” and “IETF” in the first line of your comment so I was confused.</p>
<p>Donald</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Greg Ferro</title>
		<link>http://etherealmind.com/trill-introduction-review-overview-why-what-how/comment-page-1/#comment-3212</link>
		<dc:creator>Greg Ferro</dc:creator>
		<pubDate>Fri, 28 Aug 2009 08:05:52 +0000</pubDate>
		<guid isPermaLink="false">http://etherealmind.com/?p=1492#comment-3212</guid>
		<description>Donald

I claimed that the IEEE is not open. You can&#039;t get any material on what they are doing, or how they do it, or what the the current progress is. Which is quite annoying for &#039;public&#039; standards.

I was easily able to access and evaluate material from the IETF. I agree, you could not be anymore open.

Greg</description>
		<content:encoded><![CDATA[<p>Donald</p>
<p>I claimed that the IEEE is not open. You can’t get any material on what they are doing, or how they do it, or what the the current progress is. Which is quite annoying for ‘public’ standards.</p>
<p>I was easily able to access and evaluate material from the IETF. I agree, you could not be anymore open.</p>
<p>Greg</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Donald Eastlake 3rd</title>
		<link>http://etherealmind.com/trill-introduction-review-overview-why-what-how/comment-page-1/#comment-3203</link>
		<dc:creator>Donald Eastlake 3rd</dc:creator>
		<pubDate>Thu, 27 Aug 2009 17:38:27 +0000</pubDate>
		<guid isPermaLink="false">http://etherealmind.com/?p=1492#comment-3203</guid>
		<description>Hi,

I don&#039;t understand why you are having difficulties getting access to what is going on in the TRILL WG in the IETF. The charter, which I admit is a little out of date, is here:
   http://www.ietf.org/dyn/wg/charter/trill-charter.html

That charter page has links to the one RFC the TRILL WG has had published and to the base protocol specification draft, currently at:
   http://www.ietf.org/id/draft-ietf-trill-rbridge-protocol-13.txt

As drafts are updated in the IETF, the direct text link, as above, to the old version goes away and a new link with the version number incremented is created, but here is a link to an html-ized version of draft -13 which should continue to work even after draft -14 comes out:
    http://tools.ietf.org/html/draft-ietf-trill-rbridge-protocol-13

As for what is happening in the TRILL WG itself, minutes of all its meetings, like those for every IETF working group, are published in the proceedings of the IETF meetings. The proceedings are all linked from here:
    http://www.ietf.org/meeting/proceedings.html
TRILL did not meet at the 72nd or 75th IETF meetings and I think there is at least one earlier one it skipped but if you go look at, for example, the proceedings for the 73rd and 74th IETF meetings, it is not that hard to find the TRILL meeting minutes. In fact, if you can&#039;t make it to an IETF meeting, most of the WG meetings are publicly broadcast by streaming audio and you can call in to ask questions and there is usually an IRC channel with someone posting summaries of what is happening in real time and relaying questions anyone on the IRC channel has.
    In fact, I find it very hard to conceive of any practical way in which IETF working groups could be more open. (I haven&#039;t even mentioned the IETF fundamental that all the working group mailing lists are open and anyone can subscribe.)

Thanks,
Donald</description>
		<content:encoded><![CDATA[<p>Hi,</p>
<p>I don’t understand why you are having difficulties getting access to what is going on in the TRILL WG in the IETF. The charter, which I admit is a little out of date, is here:<br />
   <a href="http://www.ietf.org/dyn/wg/charter/trill-charter.html" rel="nofollow">http://www.ietf.org/dyn/wg/charter/trill-charter.html</a></p>
<p>That charter page has links to the one RFC the TRILL WG has had published and to the base protocol specification draft, currently at:<br />
   <a href="http://www.ietf.org/id/draft-ietf-trill-rbridge-protocol-13.txt" rel="nofollow">http://www.ietf.org/id/draft-ietf-trill-rbridge-protocol-13.txt</a></p>
<p>As drafts are updated in the IETF, the direct text link, as above, to the old version goes away and a new link with the version number incremented is created, but here is a link to an html-ized version of draft –13 which should continue to work even after draft –14 comes out:<br />
    <a href="http://tools.ietf.org/html/draft-ietf-trill-rbridge-protocol-13" rel="nofollow">http://tools.ietf.org/html/draft-ietf-trill-rbridge-protocol-13</a></p>
<p>As for what is happening in the TRILL WG itself, minutes of all its meetings, like those for every IETF working group, are published in the proceedings of the IETF meetings. The proceedings are all linked from here:<br />
    <a href="http://www.ietf.org/meeting/proceedings.html" rel="nofollow">http://www.ietf.org/meeting/proceedings.html</a><br />
TRILL did not meet at the 72nd or 75th IETF meetings and I think there is at least one earlier one it skipped but if you go look at, for example, the proceedings for the 73rd and 74th IETF meetings, it is not that hard to find the TRILL meeting minutes. In fact, if you can’t make it to an IETF meeting, most of the WG meetings are publicly broadcast by streaming audio and you can call in to ask questions and there is usually an IRC channel with someone posting summaries of what is happening in real time and relaying questions anyone on the IRC channel has.<br />
    In fact, I find it very hard to conceive of any practical way in which IETF working groups could be more open. (I haven’t even mentioned the IETF fundamental that all the working group mailing lists are open and anyone can subscribe.)</p>
<p>Thanks,<br />
Donald</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Dave Allan</title>
		<link>http://etherealmind.com/trill-introduction-review-overview-why-what-how/comment-page-1/#comment-2651</link>
		<dc:creator>Dave Allan</dc:creator>
		<pubDate>Fri, 29 May 2009 13:26:34 +0000</pubDate>
		<guid isPermaLink="false">http://etherealmind.com/?p=1492#comment-2651</guid>
		<description>FYI, 2010 is because 802.1ah as well as 802.1ad is now in scope. That aspect only commenced early in 2007.

I do not believe the drafts are publically available, but most of the input to them is, check out:

http://www.ieee802.org/1/files/public/docs2009/

If you want to go backwards in time, the directories are also there for previous years...enjoy!

IMO there has been steady progress since 802.1ah was in scope, as it was a more natural fit for what SPB was trying to achieve....

cheers
D</description>
		<content:encoded><![CDATA[<p>FYI, 2010 is because 802.1ah as well as 802.1ad is now in scope. That aspect only commenced early in 2007.</p>
<p>I do not believe the drafts are publically available, but most of the input to them is, check out:</p>
<p><a href="http://www.ieee802.org/1/files/public/docs2009/" rel="nofollow">http://www.ieee802.org/1/files/public/docs2009/</a></p>
<p>If you want to go backwards in time, the directories are also there for previous years…enjoy!</p>
<p>IMO there has been steady progress since 802.1ah was in scope, as it was a more natural fit for what SPB was trying to achieve.…</p>
<p>cheers<br />
D</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Greg Ferro</title>
		<link>http://etherealmind.com/trill-introduction-review-overview-why-what-how/comment-page-1/#comment-2649</link>
		<dc:creator>Greg Ferro</dc:creator>
		<pubDate>Fri, 29 May 2009 07:21:59 +0000</pubDate>
		<guid isPermaLink="false">http://etherealmind.com/?p=1492#comment-2649</guid>
		<description>I guess i have to disagree. I have looked the the IETF web site and I cannot get access to any information about the progress of the meetings, or read the latest documents. For something that is supposed to be a &#039;standard&#039; it&#039;s not very transparent. Given the time/date stamps it would seem that things are not going smoothly, but I can&#039;t get any details to confirm or deny that since its all done in secret. 

I also remain skeptical about the IEEE competence. Ethernet is a success in spite of IEEE procedures and processes when I consider the multiple Wireless LAN cockups. Not to mention VLAN tagging.... oh I could go on.

It&#039;s a shame that it won&#039;t be ready until 2H2010, it was originally promised in 2008, maybe early 2009. 

Until the IEEE does it better, I will remain critical. Show me results and transparency.</description>
		<content:encoded><![CDATA[<p>I guess i have to disagree. I have looked the the IETF web site and I cannot get access to any information about the progress of the meetings, or read the latest documents. For something that is supposed to be a ‘standard’ it’s not very transparent. Given the time/date stamps it would seem that things are not going smoothly, but I can’t get any details to confirm or deny that since its all done in secret. </p>
<p>I also remain skeptical about the IEEE competence. Ethernet is a success in spite of IEEE procedures and processes when I consider the multiple Wireless LAN cockups. Not to mention VLAN tagging.… oh I could go on.</p>
<p>It’s a shame that it won’t be ready until 2H2010, it was originally promised in 2008, maybe early 2009. </p>
<p>Until the IEEE does it better, I will remain critical. Show me results and transparency.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Dave Allan</title>
		<link>http://etherealmind.com/trill-introduction-review-overview-why-what-how/comment-page-1/#comment-2648</link>
		<dc:creator>Dave Allan</dc:creator>
		<pubDate>Thu, 28 May 2009 19:29:19 +0000</pubDate>
		<guid isPermaLink="false">http://etherealmind.com/?p=1492#comment-2648</guid>
		<description>TRILL is not that conceptually aligned with 802.1aq other than that the service model is similar. 802.1aq was focused on re-use of ethernet, specifically leveraging 802.1ag (OAM), 802.1ah (adaptation+large scale virtualization) and 802.1Qay (population of the FDB by management or control plane). TRILL was about creating a new uniquitous specialized L3 specifically for Ethernet, different constraints, different results.

The critique of IEEE is IMO ill-informed. IETF (for example) resolves conflicts by publishing multiple RFCs and letting the industry decide, which simply punts their problems onto all of us. IEEE at least has the concept of &quot;distinct identity&quot; for a given project. It may take a little longer to get a standard but any industry confusion is capped there....

BTW 802.1aq is progressing nicely, has numerous pre-standard deployments, and should be baked as a standard in 1H2010...</description>
		<content:encoded><![CDATA[<p>TRILL is not that conceptually aligned with 802.1aq other than that the service model is similar. 802.1aq was focused on re-use of ethernet, specifically leveraging 802.1ag (OAM), 802.1ah (adaptation+large scale virtualization) and 802.1Qay (population of the FDB by management or control plane). TRILL was about creating a new uniquitous specialized L3 specifically for Ethernet, different constraints, different results.</p>
<p>The critique of IEEE is IMO ill-informed. IETF (for example) resolves conflicts by publishing multiple RFCs and letting the industry decide, which simply punts their problems onto all of us. IEEE at least has the concept of “distinct identity” for a given project. It may take a little longer to get a standard but any industry confusion is capped there.…</p>
<p>BTW 802.1aq is progressing nicely, has numerous pre-standard deployments, and should be baked as a standard in 1H2010…</p>
]]></content:encoded>
	</item>
</channel>
</rss>
