<?xml version='1.0' encoding='UTF-8'?><?xml-stylesheet href="http://www.blogger.com/styles/atom.css" type="text/css"?><feed xmlns='http://www.w3.org/2005/Atom' xmlns:openSearch='http://a9.com/-/spec/opensearchrss/1.0/' xmlns:georss='http://www.georss.org/georss' xmlns:gd='http://schemas.google.com/g/2005' xmlns:thr='http://purl.org/syndication/thread/1.0'><id>tag:blogger.com,1999:blog-1684872071077872164</id><updated>2012-01-09T16:46:03.999+02:00</updated><category term='UNIX'/><category term='policing'/><category term='core network'/><category term='successful protocol'/><category term='ITU-T'/><category term='DNS'/><category term='transport'/><category term='connection-oriented'/><category term='China'/><category term='NTP'/><category term='C'/><category term='ping'/><category term='EFM'/><category term='flows'/><category term='protocols'/><category term='scaling'/><category term='first mile'/><category term='ring protection'/><category term='xDSL'/><category term='TICTOC'/><category term='DPI'/><category term='PWE'/><category term='3G'/><category term='reliable'/><category term='PM'/><category term='Steve Jobs'/><category term='Iub'/><category term='MEF'/><category term='MPLS-TP'/><category term='Koomey&apos;s law'/><category term='DSL'/><category term='OAM'/><category term='last mile'/><category term='IPv4'/><category term='PON'/><category term='IP'/><category term='BFD'/><category term='shaping'/><category term='standardization'/><category term='1588'/><category term='FECFRAME'/><category term='IPv6'/><category term='regular expression matching'/><category term='VCCV'/><category term='Carrier Ethernet'/><category term='user experience'/><category term='DNSSEC'/><category term='succulents'/><category term='research'/><category term='network coding'/><category term='Paris Hilton'/><category term='timing over packet'/><category term='MDM'/><category term='security'/><category term='EVC'/><category term='FM'/><category term='Dennis Ritchie'/><category term='information'/><category term='MPLS'/><category term='Moore&apos;s Law'/><category term='error correction'/><category term='backhaul network'/><category term='protection switching'/><category term='Open Source'/><category term='fault management'/><category term='Denial of Service'/><category term='patents'/><category term='IPR'/><category term='cellular phones'/><category term='bandwidth'/><category term='fast reroute'/><category term='performance management'/><category term='IETF'/><category term='CTO'/><category term='DoS'/><category term='connectionless'/><category term='seamless MPLS'/><category term='access network'/><category term='RAD'/><category term='utilization'/><category term='ring circuits'/><category term='checksum'/><title type='text'>Carrier Grade Communications</title><subtitle type='html'></subtitle><link rel='http://schemas.google.com/g/2005#feed' type='application/atom+xml' href='http://raddata.blogspot.com/feeds/posts/default'/><link rel='self' type='application/atom+xml' href='http://www.blogger.com/feeds/1684872071077872164/posts/default?max-results=100'/><link rel='alternate' type='text/html' href='http://raddata.blogspot.com/'/><link rel='hub' href='http://pubsubhubbub.appspot.com/'/><author><name>Yaakov (J) Stein</name><uri>http://www.blogger.com/profile/17092448930584936036</uri><email>noreply@blogger.com</email><gd:image rel='http://schemas.google.com/g/2005#thumbnail' width='22' height='32' src='http://2.bp.blogspot.com/_2apKpu52ETw/TEb9lseLrcI/AAAAAAAAAAM/_x8_ygIr_uI/S220/yjsformal.jpg'/></author><generator version='7.00' uri='http://www.blogger.com'>Blogger</generator><openSearch:totalResults>24</openSearch:totalResults><openSearch:startIndex>1</openSearch:startIndex><openSearch:itemsPerPage>100</openSearch:itemsPerPage><entry><id>tag:blogger.com,1999:blog-1684872071077872164.post-9085166318767231831</id><published>2012-01-09T16:42:00.000+02:00</published><updated>2012-01-09T16:42:28.784+02:00</updated><category scheme='http://www.blogger.com/atom/ns#' term='UNIX'/><category scheme='http://www.blogger.com/atom/ns#' term='C'/><category scheme='http://www.blogger.com/atom/ns#' term='Steve Jobs'/><category scheme='http://www.blogger.com/atom/ns#' term='Open Source'/><category scheme='http://www.blogger.com/atom/ns#' term='Dennis Ritchie'/><title type='text'>Jobs and Ritchie</title><summary type='text'>October 2011 marked the passing away of two men well-known in the computation and communications industries. One was Steve Jobs. In his honor Apple, Microsoft, and Disneyland all flew their flags at half-staff. October 16, 2011, was declared "Steve Jobs Day" in California. President Obama gave a eulogy calling Jobs “among the greatest of American innovators … a visionary”.

The other was Dennis </summary><link rel='edit' type='application/atom+xml' href='http://www.blogger.com/feeds/1684872071077872164/posts/default/9085166318767231831'/><link rel='self' type='application/atom+xml' href='http://www.blogger.com/feeds/1684872071077872164/posts/default/9085166318767231831'/><link rel='alternate' type='text/html' href='http://raddata.blogspot.com/2012/01/jobs-and-ritchie.html' title='Jobs and Ritchie'/><author><name>Yaakov (J) Stein</name><uri>http://www.blogger.com/profile/17092448930584936036</uri><email>noreply@blogger.com</email><gd:image rel='http://schemas.google.com/g/2005#thumbnail' width='22' height='32' src='http://2.bp.blogspot.com/_2apKpu52ETw/TEb9lseLrcI/AAAAAAAAAAM/_x8_ygIr_uI/S220/yjsformal.jpg'/></author></entry><entry><id>tag:blogger.com,1999:blog-1684872071077872164.post-3408629250706326318</id><published>2011-12-25T14:50:00.015+02:00</published><updated>2011-12-25T18:05:47.241+02:00</updated><category scheme='http://www.blogger.com/atom/ns#' term='patents'/><category scheme='http://www.blogger.com/atom/ns#' term='user experience'/><category scheme='http://www.blogger.com/atom/ns#' term='regular expression matching'/><category scheme='http://www.blogger.com/atom/ns#' term='IPR'/><category scheme='http://www.blogger.com/atom/ns#' term='cellular phones'/><title type='text'>The meaning of Apple's '647 patent</title><summary type='text'>On December 19th the U.S. International Trade Commission (ITC) issued its final determination on Apple's claims against HTC of Taiwan, finding that HTC violated Section 337 of the Tariff Act by selling Android phones containing a technology that infringed a patent held by Apple. Section 337 enables the ITC to block importation into the US of foreign products that unfairly compete with domestic </summary><link rel='edit' type='application/atom+xml' href='http://www.blogger.com/feeds/1684872071077872164/posts/default/3408629250706326318'/><link rel='self' type='application/atom+xml' href='http://www.blogger.com/feeds/1684872071077872164/posts/default/3408629250706326318'/><link rel='alternate' type='text/html' href='http://raddata.blogspot.com/2011/12/meaning-of-apples-647-patent.html' title='The meaning of Apple&apos;s &apos;647 patent'/><author><name>Yaakov (J) Stein</name><uri>http://www.blogger.com/profile/17092448930584936036</uri><email>noreply@blogger.com</email><gd:image rel='http://schemas.google.com/g/2005#thumbnail' width='22' height='32' src='http://2.bp.blogspot.com/_2apKpu52ETw/TEb9lseLrcI/AAAAAAAAAAM/_x8_ygIr_uI/S220/yjsformal.jpg'/></author></entry><entry><id>tag:blogger.com,1999:blog-1684872071077872164.post-5339121771938256967</id><published>2011-11-30T11:10:00.008+02:00</published><updated>2011-11-30T14:57:25.035+02:00</updated><category scheme='http://www.blogger.com/atom/ns#' term='scaling'/><category scheme='http://www.blogger.com/atom/ns#' term='Koomey&apos;s law'/><category scheme='http://www.blogger.com/atom/ns#' term='Moore&apos;s Law'/><category scheme='http://www.blogger.com/atom/ns#' term='MDM'/><category scheme='http://www.blogger.com/atom/ns#' term='information'/><title type='text'>On exa, zetta, and beyond</title><summary type='text'>Anyone who lives in metric system countries knows what "kilo" means. A kilogram is 1000 grams, a kilometer is 1000 meters. Of course frequencies are measured in kiloHertz and in the computer world we have kilobits and kilobytes (although we are never quite sure if that is 1000 or 1024!).Most people even know that "mega" means a million. Power stations output megawatts of electricity, FM radios </summary><link rel='edit' type='application/atom+xml' href='http://www.blogger.com/feeds/1684872071077872164/posts/default/5339121771938256967'/><link rel='self' type='application/atom+xml' href='http://www.blogger.com/feeds/1684872071077872164/posts/default/5339121771938256967'/><link rel='alternate' type='text/html' href='http://raddata.blogspot.com/2011/11/on-exa-zetta-and-beyond.html' title='On exa, zetta, and beyond'/><author><name>Yaakov (J) Stein</name><uri>http://www.blogger.com/profile/17092448930584936036</uri><email>noreply@blogger.com</email><gd:image rel='http://schemas.google.com/g/2005#thumbnail' width='22' height='32' src='http://2.bp.blogspot.com/_2apKpu52ETw/TEb9lseLrcI/AAAAAAAAAAM/_x8_ygIr_uI/S220/yjsformal.jpg'/></author></entry><entry><id>tag:blogger.com,1999:blog-1684872071077872164.post-2533319792012707529</id><published>2011-11-23T19:12:00.004+02:00</published><updated>2011-11-23T19:38:40.716+02:00</updated><category scheme='http://www.blogger.com/atom/ns#' term='RAD'/><category scheme='http://www.blogger.com/atom/ns#' term='research'/><category scheme='http://www.blogger.com/atom/ns#' term='CTO'/><category scheme='http://www.blogger.com/atom/ns#' term='standardization'/><title type='text'>My new CTO job</title><summary type='text'>As you all probably know, I have changed job titles.I am now RAD's Chief Technology Officer instead of (or perhaps in addition to?) Chief Scientist.Our previous CTO, Prof. Daniel Kofman, is still in touch with the company. However, he is a bit busy since in addition to his position as Professor at Telecom ParisTech (formerly ENST), he has been appointed by France's Minister of Research and </summary><link rel='edit' type='application/atom+xml' href='http://www.blogger.com/feeds/1684872071077872164/posts/default/2533319792012707529'/><link rel='self' type='application/atom+xml' href='http://www.blogger.com/feeds/1684872071077872164/posts/default/2533319792012707529'/><link rel='alternate' type='text/html' href='http://raddata.blogspot.com/2011/11/my-new-cto-job.html' title='My new CTO job'/><author><name>Yaakov (J) Stein</name><uri>http://www.blogger.com/profile/17092448930584936036</uri><email>noreply@blogger.com</email><gd:image rel='http://schemas.google.com/g/2005#thumbnail' width='22' height='32' src='http://2.bp.blogspot.com/_2apKpu52ETw/TEb9lseLrcI/AAAAAAAAAAM/_x8_ygIr_uI/S220/yjsformal.jpg'/></author></entry><entry><id>tag:blogger.com,1999:blog-1684872071077872164.post-5721691611487672921</id><published>2011-11-17T16:29:00.006+02:00</published><updated>2011-11-17T16:46:05.918+02:00</updated><category scheme='http://www.blogger.com/atom/ns#' term='IETF'/><category scheme='http://www.blogger.com/atom/ns#' term='ITU-T'/><category scheme='http://www.blogger.com/atom/ns#' term='MPLS-TP'/><category scheme='http://www.blogger.com/atom/ns#' term='MPLS'/><title type='text'>MPLS-TP update</title><summary type='text'>At the MPLS Working Group meeting this week it was announced that the core set of MPLS-TP RFCs have been finished.Indeed, we now have (I hope that I haven't missed too many):•RFC 5586 MPLS Generic Associated Channel (G-ACh and GAL)•RFC 5654 Requirements of an MPLS Transport Profile•RFC 5718 An In-Band Data Communication Network for MPLS-TP•RFC 5860 Requirements for OAM in MPLS Transport Networks•</summary><link rel='edit' type='application/atom+xml' href='http://www.blogger.com/feeds/1684872071077872164/posts/default/5721691611487672921'/><link rel='self' type='application/atom+xml' href='http://www.blogger.com/feeds/1684872071077872164/posts/default/5721691611487672921'/><link rel='alternate' type='text/html' href='http://raddata.blogspot.com/2011/11/mpls-tp-update.html' title='MPLS-TP update'/><author><name>Yaakov (J) Stein</name><uri>http://www.blogger.com/profile/17092448930584936036</uri><email>noreply@blogger.com</email><gd:image rel='http://schemas.google.com/g/2005#thumbnail' width='22' height='32' src='http://2.bp.blogspot.com/_2apKpu52ETw/TEb9lseLrcI/AAAAAAAAAAM/_x8_ygIr_uI/S220/yjsformal.jpg'/></author></entry><entry><id>tag:blogger.com,1999:blog-1684872071077872164.post-8194763873773889173</id><published>2011-11-16T19:12:00.008+02:00</published><updated>2011-11-16T19:34:11.956+02:00</updated><category scheme='http://www.blogger.com/atom/ns#' term='IP'/><category scheme='http://www.blogger.com/atom/ns#' term='checksum'/><category scheme='http://www.blogger.com/atom/ns#' term='error correction'/><title type='text'>The notorious IP checksum algorithm</title><summary type='text'>I have been asked several times to explain the checksum calculation used in the IP suite (IPv4, TCP and UDP all utilize the same checksum algorithm).RFC 791, which defines IPv4, gives the checksum algorithm as follows :The checksum field is the 16 bit one's complement of the one'scomplement sum of all 16 bit words in the header. For purposes ofcomputing the checksum, the value of the checksum </summary><link rel='edit' type='application/atom+xml' href='http://www.blogger.com/feeds/1684872071077872164/posts/default/8194763873773889173'/><link rel='self' type='application/atom+xml' href='http://www.blogger.com/feeds/1684872071077872164/posts/default/8194763873773889173'/><link rel='alternate' type='text/html' href='http://raddata.blogspot.com/2011/11/notorious-ip-checksum-algorithm.html' title='The notorious IP checksum algorithm'/><author><name>Yaakov (J) Stein</name><uri>http://www.blogger.com/profile/17092448930584936036</uri><email>noreply@blogger.com</email><gd:image rel='http://schemas.google.com/g/2005#thumbnail' width='22' height='32' src='http://2.bp.blogspot.com/_2apKpu52ETw/TEb9lseLrcI/AAAAAAAAAAM/_x8_ygIr_uI/S220/yjsformal.jpg'/></author></entry><entry><id>tag:blogger.com,1999:blog-1684872071077872164.post-6076404596918786987</id><published>2011-10-05T19:53:00.013+02:00</published><updated>2011-10-06T07:07:12.057+02:00</updated><category scheme='http://www.blogger.com/atom/ns#' term='FECFRAME'/><category scheme='http://www.blogger.com/atom/ns#' term='network coding'/><category scheme='http://www.blogger.com/atom/ns#' term='error correction'/><title type='text'>Network Coding</title><summary type='text'>In conventional communications networks the active network elements (e.g., Ethernet switches or IP routers) are store-and-forward devices. They perform no nontrivial computation. It turns out that in certain cases it is possible to optimize network operation (to conserve some network resource or to improve some network performance measure) by embedding more intelligence in the network elements.In</summary><link rel='edit' type='application/atom+xml' href='http://www.blogger.com/feeds/1684872071077872164/posts/default/6076404596918786987'/><link rel='self' type='application/atom+xml' href='http://www.blogger.com/feeds/1684872071077872164/posts/default/6076404596918786987'/><link rel='alternate' type='text/html' href='http://raddata.blogspot.com/2011/10/network-coding.html' title='Network Coding'/><author><name>Yaakov (J) Stein</name><uri>http://www.blogger.com/profile/17092448930584936036</uri><email>noreply@blogger.com</email><gd:image rel='http://schemas.google.com/g/2005#thumbnail' width='22' height='32' src='http://2.bp.blogspot.com/_2apKpu52ETw/TEb9lseLrcI/AAAAAAAAAAM/_x8_ygIr_uI/S220/yjsformal.jpg'/></author><media:thumbnail xmlns:media='http://search.yahoo.com/mrss/' url='http://4.bp.blogspot.com/-UyjiDeI6l5Y/Toya5wnupDI/AAAAAAAAACc/vX1O8LXlz90/s72-c/butterfly1.jpg' height='72' width='72'/></entry><entry><id>tag:blogger.com,1999:blog-1684872071077872164.post-4575162188698331460</id><published>2011-08-21T11:50:00.014+03:00</published><updated>2011-08-21T14:00:24.300+03:00</updated><title type='text'>The PW Associated Channel</title><summary type='text'>In the beginning of the development of pseudowire technology, it was obvious to many of us that PWs would require some sort of OAM support. As always with OAM the question was how to make OAM packets fate-share with user data packets. The original RAD proposition was to define a special "OAM PW" that would be placed alongside the monitored PWs. In the MPLS case this meant a special PW label for </summary><link rel='edit' type='application/atom+xml' href='http://www.blogger.com/feeds/1684872071077872164/posts/default/4575162188698331460'/><link rel='self' type='application/atom+xml' href='http://www.blogger.com/feeds/1684872071077872164/posts/default/4575162188698331460'/><link rel='alternate' type='text/html' href='http://raddata.blogspot.com/2011/08/pw-associated-channel.html' title='The PW Associated Channel'/><author><name>Yaakov (J) Stein</name><uri>http://www.blogger.com/profile/17092448930584936036</uri><email>noreply@blogger.com</email><gd:image rel='http://schemas.google.com/g/2005#thumbnail' width='22' height='32' src='http://2.bp.blogspot.com/_2apKpu52ETw/TEb9lseLrcI/AAAAAAAAAAM/_x8_ygIr_uI/S220/yjsformal.jpg'/></author></entry><entry><id>tag:blogger.com,1999:blog-1684872071077872164.post-8420733918495404998</id><published>2011-05-30T16:02:00.010+03:00</published><updated>2011-05-30T16:38:13.787+03:00</updated><category scheme='http://www.blogger.com/atom/ns#' term='Denial of Service'/><category scheme='http://www.blogger.com/atom/ns#' term='DPI'/><category scheme='http://www.blogger.com/atom/ns#' term='DoS'/><category scheme='http://www.blogger.com/atom/ns#' term='seamless MPLS'/><category scheme='http://www.blogger.com/atom/ns#' term='security'/><category scheme='http://www.blogger.com/atom/ns#' term='MPLS'/><title type='text'>"Seamless MPLS" and Denial of Service</title><summary type='text'>A Denial of Service (DoS) attack is an attack that attempts to render a service temporarily unavailable to legitimate users of the service. DoS attacks are carried out by attackers disrupting the function of any link in the service supply chain. In the context of services provided over telecommunications networks, DoS attacks can be directed at a web or mail server, routers, or at any necessary </summary><link rel='edit' type='application/atom+xml' href='http://www.blogger.com/feeds/1684872071077872164/posts/default/8420733918495404998'/><link rel='self' type='application/atom+xml' href='http://www.blogger.com/feeds/1684872071077872164/posts/default/8420733918495404998'/><link rel='alternate' type='text/html' href='http://raddata.blogspot.com/2011/05/seamless-mpls-and-denial-of-service.html' title='&quot;Seamless MPLS&quot; and Denial of Service'/><author><name>Yaakov (J) Stein</name><uri>http://www.blogger.com/profile/17092448930584936036</uri><email>noreply@blogger.com</email><gd:image rel='http://schemas.google.com/g/2005#thumbnail' width='22' height='32' src='http://2.bp.blogspot.com/_2apKpu52ETw/TEb9lseLrcI/AAAAAAAAAAM/_x8_ygIr_uI/S220/yjsformal.jpg'/></author></entry><entry><id>tag:blogger.com,1999:blog-1684872071077872164.post-2289544099105997616</id><published>2011-01-10T09:51:00.004+02:00</published><updated>2011-01-10T10:08:24.042+02:00</updated><category scheme='http://www.blogger.com/atom/ns#' term='successful protocol'/><category scheme='http://www.blogger.com/atom/ns#' term='IPv6'/><category scheme='http://www.blogger.com/atom/ns#' term='MPLS'/><category scheme='http://www.blogger.com/atom/ns#' term='IPv4'/><title type='text'>MPLS is not a "successful" protocol</title><summary type='text'>RFC 5218 defines what the Internet Architecture Board considers to be a "successful" protocol. A "successful" protocol is one that meets its original goals and is widely deployed, such as DNS, BGP, SMTP, and SIP. A "wildly successful" protocol far exceeds its original goals in terms of purpose and scale. Examples of the latter are IPv4, ARP, and HTTP. A protocol may be considered successful even </summary><link rel='edit' type='application/atom+xml' href='http://www.blogger.com/feeds/1684872071077872164/posts/default/2289544099105997616'/><link rel='self' type='application/atom+xml' href='http://www.blogger.com/feeds/1684872071077872164/posts/default/2289544099105997616'/><link rel='alternate' type='text/html' href='http://raddata.blogspot.com/2011/01/mpls-is-not-successful-protocol.html' title='MPLS is not a &quot;successful&quot; protocol'/><author><name>Yaakov (J) Stein</name><uri>http://www.blogger.com/profile/17092448930584936036</uri><email>noreply@blogger.com</email><gd:image rel='http://schemas.google.com/g/2005#thumbnail' width='22' height='32' src='http://2.bp.blogspot.com/_2apKpu52ETw/TEb9lseLrcI/AAAAAAAAAAM/_x8_ygIr_uI/S220/yjsformal.jpg'/></author></entry><entry><id>tag:blogger.com,1999:blog-1684872071077872164.post-1902577089548146974</id><published>2010-11-29T13:46:00.004+02:00</published><updated>2010-11-29T14:29:53.170+02:00</updated><category scheme='http://www.blogger.com/atom/ns#' term='protection switching'/><category scheme='http://www.blogger.com/atom/ns#' term='reliable'/><category scheme='http://www.blogger.com/atom/ns#' term='MPLS-TP'/><category scheme='http://www.blogger.com/atom/ns#' term='MPLS'/><category scheme='http://www.blogger.com/atom/ns#' term='OAM'/><category scheme='http://www.blogger.com/atom/ns#' term='transport'/><title type='text'>Reliable transport vs. reliable transport</title><summary type='text'>One of the most contradictory uses of terminology in communications concerns the word transport as used by the IETF and the ITU-T communities. To make matters worse, the term’s prevalent modifier reliable leads to even further divergence in meaning.To the Internet community, transport refers to the fourth layer of the OSI layer stack (a layer stack known to the ITU-T as X.200, but largely assumed</summary><link rel='edit' type='application/atom+xml' href='http://www.blogger.com/feeds/1684872071077872164/posts/default/1902577089548146974'/><link rel='self' type='application/atom+xml' href='http://www.blogger.com/feeds/1684872071077872164/posts/default/1902577089548146974'/><link rel='alternate' type='text/html' href='http://raddata.blogspot.com/2010/11/reliable-transport-vs-reliable.html' title='Reliable transport vs. reliable transport'/><author><name>Yaakov (J) Stein</name><uri>http://www.blogger.com/profile/17092448930584936036</uri><email>noreply@blogger.com</email><gd:image rel='http://schemas.google.com/g/2005#thumbnail' width='22' height='32' src='http://2.bp.blogspot.com/_2apKpu52ETw/TEb9lseLrcI/AAAAAAAAAAM/_x8_ygIr_uI/S220/yjsformal.jpg'/></author></entry><entry><id>tag:blogger.com,1999:blog-1684872071077872164.post-7435176569967220132</id><published>2010-11-23T23:05:00.002+02:00</published><updated>2010-11-23T23:15:24.027+02:00</updated><category scheme='http://www.blogger.com/atom/ns#' term='MEF'/><category scheme='http://www.blogger.com/atom/ns#' term='IETF'/><category scheme='http://www.blogger.com/atom/ns#' term='TICTOC'/><category scheme='http://www.blogger.com/atom/ns#' term='China'/><category scheme='http://www.blogger.com/atom/ns#' term='Paris Hilton'/><title type='text'>IETF79 - Beijing !</title><summary type='text'>I haven’t had much time to blog of late, having to catch up on work since returning from Beijing.Beijing ? I hear you ask. Yes, the 79th IETF meeting was held 7-12 November in the Chinese capital.This was my 26’th IETF, and things have changed since my first meeting. Back in the “old days” the meetings were mostly in the US (e.g., Minneapolis in the winter) and occasionally in Europe. This was </summary><link rel='edit' type='application/atom+xml' href='http://www.blogger.com/feeds/1684872071077872164/posts/default/7435176569967220132'/><link rel='self' type='application/atom+xml' href='http://www.blogger.com/feeds/1684872071077872164/posts/default/7435176569967220132'/><link rel='alternate' type='text/html' href='http://raddata.blogspot.com/2010/11/ietf79-beijing.html' title='IETF79 - Beijing !'/><author><name>Yaakov (J) Stein</name><uri>http://www.blogger.com/profile/17092448930584936036</uri><email>noreply@blogger.com</email><gd:image rel='http://schemas.google.com/g/2005#thumbnail' width='22' height='32' src='http://2.bp.blogspot.com/_2apKpu52ETw/TEb9lseLrcI/AAAAAAAAAAM/_x8_ygIr_uI/S220/yjsformal.jpg'/></author></entry><entry><id>tag:blogger.com,1999:blog-1684872071077872164.post-7523612905406573192</id><published>2010-11-02T21:47:00.003+02:00</published><updated>2010-11-02T21:54:10.344+02:00</updated><category scheme='http://www.blogger.com/atom/ns#' term='connectionless'/><category scheme='http://www.blogger.com/atom/ns#' term='connection-oriented'/><category scheme='http://www.blogger.com/atom/ns#' term='EVC'/><category scheme='http://www.blogger.com/atom/ns#' term='OAM'/><category scheme='http://www.blogger.com/atom/ns#' term='flows'/><title type='text'>OAM for flows</title><summary type='text'>Continuing my coverage of the recent joint IESG/IAB design team on OAM, this time I want to discuss the issue of OAM for flows in Packet Switched Networks (PSNs).From a pure topology standpoint any communications network is imply a set of source ports (i.e., interfaces into which we may input information), a set of destination ports (i.e., interfaces from which we may receive information), and a </summary><link rel='edit' type='application/atom+xml' href='http://www.blogger.com/feeds/1684872071077872164/posts/default/7523612905406573192'/><link rel='self' type='application/atom+xml' href='http://www.blogger.com/feeds/1684872071077872164/posts/default/7523612905406573192'/><link rel='alternate' type='text/html' href='http://raddata.blogspot.com/2010/11/oam-for-flows.html' title='OAM for flows'/><author><name>Yaakov (J) Stein</name><uri>http://www.blogger.com/profile/17092448930584936036</uri><email>noreply@blogger.com</email><gd:image rel='http://schemas.google.com/g/2005#thumbnail' width='22' height='32' src='http://2.bp.blogspot.com/_2apKpu52ETw/TEb9lseLrcI/AAAAAAAAAAM/_x8_ygIr_uI/S220/yjsformal.jpg'/></author></entry><entry><id>tag:blogger.com,1999:blog-1684872071077872164.post-1619276125186683694</id><published>2010-10-28T14:38:00.005+02:00</published><updated>2010-10-28T15:03:14.547+02:00</updated><category scheme='http://www.blogger.com/atom/ns#' term='VCCV'/><category scheme='http://www.blogger.com/atom/ns#' term='IETF'/><category scheme='http://www.blogger.com/atom/ns#' term='ping'/><category scheme='http://www.blogger.com/atom/ns#' term='PM'/><category scheme='http://www.blogger.com/atom/ns#' term='ITU-T'/><category scheme='http://www.blogger.com/atom/ns#' term='MPLS-TP'/><category scheme='http://www.blogger.com/atom/ns#' term='FM'/><category scheme='http://www.blogger.com/atom/ns#' term='BFD'/><category scheme='http://www.blogger.com/atom/ns#' term='OAM'/><category scheme='http://www.blogger.com/atom/ns#' term='PWE'/><title type='text'>IETF and OAM</title><summary type='text'>On October 12nd and 13th the IESG (Internet Engineering Steering Group) and IAB (Internet Architecture Board), the two IETF management bodies, held a joint design session on OAM. I was a bit surprised that the IETF leadership would be interested in devoting a separate meeting (not coinciding with an IETF conference) to the subject of OAM; OAM has never been an area of IETF expertise. Indeed, when</summary><link rel='edit' type='application/atom+xml' href='http://www.blogger.com/feeds/1684872071077872164/posts/default/1619276125186683694'/><link rel='self' type='application/atom+xml' href='http://www.blogger.com/feeds/1684872071077872164/posts/default/1619276125186683694'/><link rel='alternate' type='text/html' href='http://raddata.blogspot.com/2010/10/on-october-12nd-and-13th-iesg-internet.html' title='IETF and OAM'/><author><name>Yaakov (J) Stein</name><uri>http://www.blogger.com/profile/17092448930584936036</uri><email>noreply@blogger.com</email><gd:image rel='http://schemas.google.com/g/2005#thumbnail' width='22' height='32' src='http://2.bp.blogspot.com/_2apKpu52ETw/TEb9lseLrcI/AAAAAAAAAAM/_x8_ygIr_uI/S220/yjsformal.jpg'/></author></entry><entry><id>tag:blogger.com,1999:blog-1684872071077872164.post-2150297422534915829</id><published>2010-09-29T12:04:00.006+02:00</published><updated>2010-09-29T12:21:17.901+02:00</updated><category scheme='http://www.blogger.com/atom/ns#' term='user experience'/><category scheme='http://www.blogger.com/atom/ns#' term='PM'/><category scheme='http://www.blogger.com/atom/ns#' term='fault management'/><category scheme='http://www.blogger.com/atom/ns#' term='performance management'/><category scheme='http://www.blogger.com/atom/ns#' term='FM'/><category scheme='http://www.blogger.com/atom/ns#' term='OAM'/><title type='text'>OAM for FM and PM</title><summary type='text'>The Operations, Administration, and Maintenance (OAM) functionality provided in all modern communications systems supports two distinguishable functions, namely Fault Management (FM) and Performance Management (PM).It is important to remember that despite the use of the word “management” here, OAM is a user-plane function. OAM may trigger control plane procedures (e.g., protection switching) or </summary><link rel='edit' type='application/atom+xml' href='http://www.blogger.com/feeds/1684872071077872164/posts/default/2150297422534915829'/><link rel='self' type='application/atom+xml' href='http://www.blogger.com/feeds/1684872071077872164/posts/default/2150297422534915829'/><link rel='alternate' type='text/html' href='http://raddata.blogspot.com/2010/09/oam-for-fm-and-pm.html' title='OAM for FM and PM'/><author><name>Yaakov (J) Stein</name><uri>http://www.blogger.com/profile/17092448930584936036</uri><email>noreply@blogger.com</email><gd:image rel='http://schemas.google.com/g/2005#thumbnail' width='22' height='32' src='http://2.bp.blogspot.com/_2apKpu52ETw/TEb9lseLrcI/AAAAAAAAAAM/_x8_ygIr_uI/S220/yjsformal.jpg'/></author></entry><entry><id>tag:blogger.com,1999:blog-1684872071077872164.post-1832631338762334188</id><published>2010-09-08T12:56:00.003+03:00</published><updated>2010-09-08T13:00:58.650+03:00</updated><category scheme='http://www.blogger.com/atom/ns#' term='backhaul network'/><category scheme='http://www.blogger.com/atom/ns#' term='last mile'/><category scheme='http://www.blogger.com/atom/ns#' term='fault management'/><category scheme='http://www.blogger.com/atom/ns#' term='performance management'/><category scheme='http://www.blogger.com/atom/ns#' term='MPLS-TP'/><category scheme='http://www.blogger.com/atom/ns#' term='core network'/><category scheme='http://www.blogger.com/atom/ns#' term='access network'/><category scheme='http://www.blogger.com/atom/ns#' term='OAM'/><category scheme='http://www.blogger.com/atom/ns#' term='protocols'/><title type='text'>Deployment, R&amp;D, and protocols</title><summary type='text'>In my last entry I discussed why the last mile is a bandwidth bottleneck while the backhaul network is a utilization bottleneck. Since I was discussing the access network I did not delve into the core, but it is clear that the core is where the rates are highest, and where the traffic is the most diverse in nature.Based on these facts, we can enumerate the critical issues for deployment and R&amp;D </summary><link rel='edit' type='application/atom+xml' href='http://www.blogger.com/feeds/1684872071077872164/posts/default/1832631338762334188'/><link rel='self' type='application/atom+xml' href='http://www.blogger.com/feeds/1684872071077872164/posts/default/1832631338762334188'/><link rel='alternate' type='text/html' href='http://raddata.blogspot.com/2010/09/deployment-r-and-protocols.html' title='Deployment, R&amp;D, and protocols'/><author><name>Yaakov (J) Stein</name><uri>http://www.blogger.com/profile/17092448930584936036</uri><email>noreply@blogger.com</email><gd:image rel='http://schemas.google.com/g/2005#thumbnail' width='22' height='32' src='http://2.bp.blogspot.com/_2apKpu52ETw/TEb9lseLrcI/AAAAAAAAAAM/_x8_ygIr_uI/S220/yjsformal.jpg'/></author></entry><entry><id>tag:blogger.com,1999:blog-1684872071077872164.post-3498993952611701632</id><published>2010-08-26T12:04:00.004+03:00</published><updated>2010-08-26T12:17:38.264+03:00</updated><category scheme='http://www.blogger.com/atom/ns#' term='utilization'/><category scheme='http://www.blogger.com/atom/ns#' term='backhaul network'/><category scheme='http://www.blogger.com/atom/ns#' term='last mile'/><category scheme='http://www.blogger.com/atom/ns#' term='access network'/><category scheme='http://www.blogger.com/atom/ns#' term='bandwidth'/><title type='text'>Bandwidth and utilization bottlenecks</title><summary type='text'>Let us consider an end-to-end data transport path that can be decomposed into the following segments* end-to-end path = LAN + access network + core network + access network + LANThere may be distinct service providers for each of these segments, thus many different decompositions may make sense from the business perspective. Yet, the identity of the access network, and of its components * access </summary><link rel='edit' type='application/atom+xml' href='http://www.blogger.com/feeds/1684872071077872164/posts/default/3498993952611701632'/><link rel='self' type='application/atom+xml' href='http://www.blogger.com/feeds/1684872071077872164/posts/default/3498993952611701632'/><link rel='alternate' type='text/html' href='http://raddata.blogspot.com/2010/08/bandwidth-and-utilization-bottlenecks.html' title='Bandwidth and utilization bottlenecks'/><author><name>Yaakov (J) Stein</name><uri>http://www.blogger.com/profile/17092448930584936036</uri><email>noreply@blogger.com</email><gd:image rel='http://schemas.google.com/g/2005#thumbnail' width='22' height='32' src='http://2.bp.blogspot.com/_2apKpu52ETw/TEb9lseLrcI/AAAAAAAAAAM/_x8_ygIr_uI/S220/yjsformal.jpg'/></author></entry><entry><id>tag:blogger.com,1999:blog-1684872071077872164.post-6194661170174024409</id><published>2010-08-19T14:16:00.003+03:00</published><updated>2010-08-26T12:18:45.807+03:00</updated><category scheme='http://www.blogger.com/atom/ns#' term='backhaul network'/><category scheme='http://www.blogger.com/atom/ns#' term='last mile'/><category scheme='http://www.blogger.com/atom/ns#' term='access network'/><title type='text'>The access network equation</title><summary type='text'>My last entry provoked several emails on the subject of the terms last/first mile vs. access networks. While answering these emails I found it useful to bring in an additional term – the backhaul network. Since these discussions took place elsewhere, I thought it would be best to summarize my explanation here.Everyone knows what a LAN is and what a core network is. Simply put, the access network </summary><link rel='edit' type='application/atom+xml' href='http://www.blogger.com/feeds/1684872071077872164/posts/default/6194661170174024409'/><link rel='self' type='application/atom+xml' href='http://www.blogger.com/feeds/1684872071077872164/posts/default/6194661170174024409'/><link rel='alternate' type='text/html' href='http://raddata.blogspot.com/2010/08/access-network-equation.html' title='The access network equation'/><author><name>Yaakov (J) Stein</name><uri>http://www.blogger.com/profile/17092448930584936036</uri><email>noreply@blogger.com</email><gd:image rel='http://schemas.google.com/g/2005#thumbnail' width='22' height='32' src='http://2.bp.blogspot.com/_2apKpu52ETw/TEb9lseLrcI/AAAAAAAAAAM/_x8_ygIr_uI/S220/yjsformal.jpg'/></author></entry><entry><id>tag:blogger.com,1999:blog-1684872071077872164.post-4374715036004552356</id><published>2010-08-08T14:37:00.003+03:00</published><updated>2010-08-08T14:43:21.570+03:00</updated><category scheme='http://www.blogger.com/atom/ns#' term='first mile'/><category scheme='http://www.blogger.com/atom/ns#' term='last mile'/><category scheme='http://www.blogger.com/atom/ns#' term='DSL'/><category scheme='http://www.blogger.com/atom/ns#' term='PON'/><category scheme='http://www.blogger.com/atom/ns#' term='EFM'/><category scheme='http://www.blogger.com/atom/ns#' term='xDSL'/><title type='text'>Last mile or first mile ?</title><summary type='text'>Physical-layer access technologies with limited range are usually called last mile technologies. More specifically, we usually use the expression last mile when considering xDSL, that enables several Mbps to be transported over several kilometers, or a fiber optic link or PON, that enable hundreds or even thousands of Mbps to be transported over tens of kilometers.In the year 2000 the IEEE </summary><link rel='edit' type='application/atom+xml' href='http://www.blogger.com/feeds/1684872071077872164/posts/default/4374715036004552356'/><link rel='self' type='application/atom+xml' href='http://www.blogger.com/feeds/1684872071077872164/posts/default/4374715036004552356'/><link rel='alternate' type='text/html' href='http://raddata.blogspot.com/2010/08/last-mile-or-first-mile.html' title='Last mile or first mile ?'/><author><name>Yaakov (J) Stein</name><uri>http://www.blogger.com/profile/17092448930584936036</uri><email>noreply@blogger.com</email><gd:image rel='http://schemas.google.com/g/2005#thumbnail' width='22' height='32' src='http://2.bp.blogspot.com/_2apKpu52ETw/TEb9lseLrcI/AAAAAAAAAAM/_x8_ygIr_uI/S220/yjsformal.jpg'/></author></entry><entry><id>tag:blogger.com,1999:blog-1684872071077872164.post-6923759019434849138</id><published>2010-08-02T14:42:00.000+03:00</published><updated>2010-08-02T15:22:41.901+03:00</updated><category scheme='http://www.blogger.com/atom/ns#' term='IETF'/><category scheme='http://www.blogger.com/atom/ns#' term='DNSSEC'/><category scheme='http://www.blogger.com/atom/ns#' term='DNS'/><category scheme='http://www.blogger.com/atom/ns#' term='security'/><title type='text'>DNSSEC - Internet root signed</title><summary type='text'>IP addresses (even 4-byte IPv4 ones), are generally not easy to remember, which is why humans prefer to type domain names into their browser address window, even if they are longer. It is job of the Domain Name System (DNS) to translate the domain name into the correct IP address, which is placed in the IP header and enables proper forwarding.The DNS works recursively in the following way. When </summary><link rel='edit' type='application/atom+xml' href='http://www.blogger.com/feeds/1684872071077872164/posts/default/6923759019434849138'/><link rel='self' type='application/atom+xml' href='http://www.blogger.com/feeds/1684872071077872164/posts/default/6923759019434849138'/><link rel='alternate' type='text/html' href='http://raddata.blogspot.com/2010/08/dnssec-internet-root-signed.html' title='DNSSEC - Internet root signed'/><author><name>Yaakov (J) Stein</name><uri>http://www.blogger.com/profile/17092448930584936036</uri><email>noreply@blogger.com</email><gd:image rel='http://schemas.google.com/g/2005#thumbnail' width='22' height='32' src='http://2.bp.blogspot.com/_2apKpu52ETw/TEb9lseLrcI/AAAAAAAAAAM/_x8_ygIr_uI/S220/yjsformal.jpg'/></author></entry><entry><id>tag:blogger.com,1999:blog-1684872071077872164.post-5604535283960888077</id><published>2010-07-29T00:25:00.000+03:00</published><updated>2010-07-29T00:35:48.421+03:00</updated><category scheme='http://www.blogger.com/atom/ns#' term='timing over packet'/><category scheme='http://www.blogger.com/atom/ns#' term='1588'/><category scheme='http://www.blogger.com/atom/ns#' term='TICTOC'/><category scheme='http://www.blogger.com/atom/ns#' term='MPLS'/><category scheme='http://www.blogger.com/atom/ns#' term='NTP'/><title type='text'>TICTOC update</title><summary type='text'>This entry is an update for people who have been following the IETF TICTOC working group that I chair. We had a very lively meeting yesterday, and the topic that evoked the most interest was that of how to transfer timing flows (especially 1588, but NTP as well) over MPLS networks.The first question is why anything special treatment is needed here at all - after all, anything that can be carried </summary><link rel='edit' type='application/atom+xml' href='http://www.blogger.com/feeds/1684872071077872164/posts/default/5604535283960888077'/><link rel='self' type='application/atom+xml' href='http://www.blogger.com/feeds/1684872071077872164/posts/default/5604535283960888077'/><link rel='alternate' type='text/html' href='http://raddata.blogspot.com/2010/07/tictoc-update.html' title='TICTOC update'/><author><name>Yaakov (J) Stein</name><uri>http://www.blogger.com/profile/17092448930584936036</uri><email>noreply@blogger.com</email><gd:image rel='http://schemas.google.com/g/2005#thumbnail' width='22' height='32' src='http://2.bp.blogspot.com/_2apKpu52ETw/TEb9lseLrcI/AAAAAAAAAAM/_x8_ygIr_uI/S220/yjsformal.jpg'/></author></entry><entry><id>tag:blogger.com,1999:blog-1684872071077872164.post-1540110555413461847</id><published>2010-07-28T13:21:00.000+03:00</published><updated>2010-07-29T00:38:02.252+03:00</updated><category scheme='http://www.blogger.com/atom/ns#' term='IETF'/><category scheme='http://www.blogger.com/atom/ns#' term='IP'/><category scheme='http://www.blogger.com/atom/ns#' term='connectionless'/><category scheme='http://www.blogger.com/atom/ns#' term='connection-oriented'/><category scheme='http://www.blogger.com/atom/ns#' term='MPLS'/><title type='text'>Trains, planes, MPLS, and IP</title><summary type='text'>I am in Maastricht at the 78th IETF meeting.In the weeks before the meeting many IETF'ers complained about the fact that there were no direct flights to the venue. The closest airports are Amsterdam and Brussels, but from there three trains had to be taken.At first I had thought that the problem was related to carrying luggage between trains, but discovered that the concerns were more about the </summary><link rel='edit' type='application/atom+xml' href='http://www.blogger.com/feeds/1684872071077872164/posts/default/1540110555413461847'/><link rel='self' type='application/atom+xml' href='http://www.blogger.com/feeds/1684872071077872164/posts/default/1540110555413461847'/><link rel='alternate' type='text/html' href='http://raddata.blogspot.com/2010/07/i-am-in-maastricht-at-78th-ietf-meeting.html' title='Trains, planes, MPLS, and IP'/><author><name>Yaakov (J) Stein</name><uri>http://www.blogger.com/profile/17092448930584936036</uri><email>noreply@blogger.com</email><gd:image rel='http://schemas.google.com/g/2005#thumbnail' width='22' height='32' src='http://2.bp.blogspot.com/_2apKpu52ETw/TEb9lseLrcI/AAAAAAAAAAM/_x8_ygIr_uI/S220/yjsformal.jpg'/></author></entry><entry><id>tag:blogger.com,1999:blog-1684872071077872164.post-5864029529066661441</id><published>2010-07-26T19:06:00.001+03:00</published><updated>2010-07-26T19:46:20.878+03:00</updated><category scheme='http://www.blogger.com/atom/ns#' term='succulents'/><category scheme='http://www.blogger.com/atom/ns#' term='protection switching'/><category scheme='http://www.blogger.com/atom/ns#' term='ring protection'/><category scheme='http://www.blogger.com/atom/ns#' term='fast reroute'/><category scheme='http://www.blogger.com/atom/ns#' term='ring circuits'/><title type='text'>Succulents and (tele)protection mechanisms</title><summary type='text'>My wife and I cultivate succulents, plants that store water. Cacti are succulents, but we don’t collect them – only the cuddly and outwardly types. What I find so interesting about succulents is that the various types are relatively unrelated – there was never a proto-succulent that evolved into many subspecies. Instead many different kinds of plants developed similar mechanisms to cope with the </summary><link rel='edit' type='application/atom+xml' href='http://www.blogger.com/feeds/1684872071077872164/posts/default/5864029529066661441'/><link rel='self' type='application/atom+xml' href='http://www.blogger.com/feeds/1684872071077872164/posts/default/5864029529066661441'/><link rel='alternate' type='text/html' href='http://raddata.blogspot.com/2010/07/succulents-and-teleprotection.html' title='Succulents and (tele)protection mechanisms'/><author><name>Yaakov (J) Stein</name><uri>http://www.blogger.com/profile/17092448930584936036</uri><email>noreply@blogger.com</email><gd:image rel='http://schemas.google.com/g/2005#thumbnail' width='22' height='32' src='http://2.bp.blogspot.com/_2apKpu52ETw/TEb9lseLrcI/AAAAAAAAAAM/_x8_ygIr_uI/S220/yjsformal.jpg'/></author></entry><entry><id>tag:blogger.com,1999:blog-1684872071077872164.post-6710076953424619873</id><published>2010-07-21T11:05:00.000+03:00</published><updated>2010-07-26T19:50:58.310+03:00</updated><category scheme='http://www.blogger.com/atom/ns#' term='policing'/><category scheme='http://www.blogger.com/atom/ns#' term='Carrier Ethernet'/><category scheme='http://www.blogger.com/atom/ns#' term='shaping'/><category scheme='http://www.blogger.com/atom/ns#' term='Iub'/><category scheme='http://www.blogger.com/atom/ns#' term='3G'/><title type='text'>Shaping / policing in 3G networks</title><summary type='text'>This is my first blog entry on the world of traffic shaping. We have all been hearing about the need for shaping in 3G mobile networks. The subject’s popularity exploded with the publicity of network overload problems that some operators were experiencing with the introduction of the iPhone. Most of that turned out to be due to signaling overload. However, almost everyone is convinced that if </summary><link rel='edit' type='application/atom+xml' href='http://www.blogger.com/feeds/1684872071077872164/posts/default/6710076953424619873'/><link rel='self' type='application/atom+xml' href='http://www.blogger.com/feeds/1684872071077872164/posts/default/6710076953424619873'/><link rel='alternate' type='text/html' href='http://raddata.blogspot.com/2010/07/this-is-my-first-blog-entry-on-world-of.html' title='Shaping / policing in 3G networks'/><author><name>Yaakov (J) Stein</name><uri>http://www.blogger.com/profile/17092448930584936036</uri><email>noreply@blogger.com</email><gd:image rel='http://schemas.google.com/g/2005#thumbnail' width='22' height='32' src='http://2.bp.blogspot.com/_2apKpu52ETw/TEb9lseLrcI/AAAAAAAAAAM/_x8_ygIr_uI/S220/yjsformal.jpg'/></author></entry></feed>
