From routing-discussion-admin@ietf.org Mon May 5 13:00:56 2003 Received: from www1.ietf.org (ietf.org [132.151.1.19] (may be forged)) by ietf.org (8.9.1a/8.9.1a) with ESMTP id NAA07994 for ; Mon, 5 May 2003 13:00:56 -0400 (EDT) Received: from www1.ietf.org (localhost.localdomain [127.0.0.1]) by www1.ietf.org (8.11.6/8.11.6) with ESMTP id h45Gx9816607; Mon, 5 May 2003 12:59:09 -0400 Received: from ietf.org (odin.ietf.org [132.151.1.176]) by www1.ietf.org (8.11.6/8.11.6) with ESMTP id h45Gu9816488 for ; Mon, 5 May 2003 12:56:09 -0400 Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id MAA07471 for ; Mon, 5 May 2003 12:47:34 -0400 (EDT) Received: from ietf-mx ([132.151.6.1]) by ietf-mx with esmtp (Exim 4.12) id 19Cj9p-0006y3-00 for routing-discussion@ietf.org; Mon, 05 May 2003 12:49:41 -0400 Received: from web41804.mail.yahoo.com ([66.218.93.138]) by ietf-mx with smtp (Exim 4.12) id 19Cj9j-0006xl-00 for routing-discussion@ietf.org; Mon, 05 May 2003 12:49:35 -0400 Message-ID: <20030505164943.14475.qmail@web41804.mail.yahoo.com> Received: from [65.213.193.49] by web41804.mail.yahoo.com via HTTP; Mon, 05 May 2003 09:49:43 PDT From: CAITR Reply-To: info@caitr.org Subject: Internetworking 2003: Call for Participation To: routing-discussion@ietf.org MIME-Version: 1.0 Content-Type: multipart/alternative; boundary="0-1505361720-1052153383=:13982" Sender: routing-discussion-admin@ietf.org Errors-To: routing-discussion-admin@ietf.org X-BeenThere: routing-discussion@ietf.org X-Mailman-Version: 2.0.12 Precedence: bulk List-Unsubscribe: , List-Id: Routing Area General mailing list List-Post: List-Help: List-Subscribe: , List-Archive: Date: Mon, 5 May 2003 09:49:43 -0700 (PDT) --0-1505361720-1052153383=:13982 Content-Type: text/plain; charset=us-ascii Internetworking 2003 International Conference Hilton San Jose & Towers Hotel, California June 22-June 24, 2003 http://www.caitr.org/internetworking03/index.htm You are cordially invited to attend the Internetworking 2003 International Conference to be held in San Jose, California, June 22-24, 2003. The 3-day event consists of two-days of highly technical sessions, preceded by four technical tutorials.Registration for the conference is underway. Please visit http://www.caitr.org/internetworking03/registration.htm and follow instructions for registration. The early registration discounts are extremely attractive and are valid till June 1, 2003.Important Dates: --------------------- - Early Registration Rates Cut-Off Date: Sept 30 - Tutorials: Oct 27, 1:00-6:00 pm - Conference sessions: October 28-29 8:30am-6:00pmProgram: ------------- (visit http://www.caitr.org/internetworking03/program.htm for abstracts and speaker details)Sunday June 22 Tutorial-1: MPLS VPNs Tutorial-2: IPv6 Tutorial-3: Mobile Wireless Internet Architecture and Protocols Tutorial-4: Voice over Packet Monday June 23 Welcome and Keynote Session: Network Technology Trends - Forwarding Element and Control Separation - Evolution of Inter-Domain Routing - Network Processing Building Blocks: Enabling the Routers of the Future Session: Network Architecture - An architecture for IPv6 VPNs and IPv6 transport over MPLS/GMPLS multiservice backbones IPv6 - A new routing architecture: Atomised Routing - Internetworking MPLS Layer 2 Transport with an IP Services Network Session: Storage Area Networks - Storage as a Network Node - Object-Based Storage - Design, Implementation, and Performance Analysis of the iSCSI Protocol for SCSI over TCP/IP - SANs Considerations Session: Mobile & Wireless Networks - CertBU: Certificate-based Techniques for Securing Mobile IPv6 Binding Updates IPv6 - Challenges and Roadmap of UMTS Network Deployment - Inter-working Mobile IPv6 with IP Multimedia Subsystem in UMTS - Mobile Authentication and QoS - Mobile Handoff Technologies Tuesday June 24 Session: Inter-Domain Routing - Optimizing Route Convergence - Traceroute and BGP AS Path Incongruities - Domain Constrained Multicast: A New Approach for IP Multicast Routing Session: Applications & Services - Securing the Web with Next Generation Encryption Technologies - Impact of the live radio on the Internet, and the real-time streaming audio, in the ComUNITY cable system from Com21 - A novel EAC semantic for the RTSP protocol - Towards an end-to-end architecture integrating new Transport and IP services in a DiffServ Internet Session: Network Management & Planning - Pseudowire OAM: A Mandatory Yet Often Overlooked Feature - A Multicommodity Flow Formulation for the MPLS Layout Design: Reduced Complexity Layout and Minimum Relayout Probems - Design Of Fast Fault Restoration System For WDM Networks - Cross-domain multimedia service provisioning, the EVOLUTE solution Session: QoS Based Routing - QoS Routing in Networks with Non-Deterministic Information - Active Dynamic Routing - QoS routing for Differentiated Services: simulations and prototype experiments - Probabilistic routing for QoS improvement in GPS networks - Fluid flow network modeling for hop-by-hop feedback control design and analysis We look forward to seeing you at the Conference. Regards, Conference Technical Co-chairs: - Dr. Maurice Gagnaire, ENST, France - Daniel Awduche Technical Program Committee of the Internetworking 2003 Conference: - Roberto Sabella, Erisson - Dr. Moshe Zukerman, Univ. of Melbourne - Nada Golmie, NIST - Dr. Guy Pujolle, LIP6, France - Dr. Samir Tohme, ENST, France - Stefano Trumpy, Italian National Research Council - Dr. Ibrahim Habib, City Univ. of NY - Dr. Marc Lobelle, UCL University, Belgium - Dr. Parviz Yegani, Cisco Systems - Dr. G.S. Kuo - Dr. Abbas Jamalipour, Univ. of Sydney - Dr. Hussein Mouftah, Univ. of Ottawa - James Kempf - Elizabeth Rodriguez - Dr. Ferit Yegenoglu, Isocore - Dr. Ali Zadeh, George Mason University - Dr. Tony Przygienda, Xebeo - Ran Canetti, IBM --0-1505361720-1052153383=:13982 Content-Type: text/html; charset=us-ascii
 
     Internetworking 2003 International Conference
     Hilton San Jose & Towers Hotel, California
              June 22-June 24, 2003
    http://www.caitr.org/internetworking03/index.htm
  
You are cordially invited to attend the Internetworking 2003 International Conference to be held in San Jose, California, June 22-24, 2003. The 3-day event consists of two-days of highly technical sessions, preceded by four technical tutorials.
Registration for the conference is underway. Please visit http://www.caitr.org/internetworking03/registration.htm and follow instructions for registration. The early registration discounts are extremely attractive and are valid till June 1, 2003.
Important Dates:
---------------------
- Early Registration Rates Cut-Off Date: Sept 30
- Tutorials: Oct 27, 1:00-6:00 pm
- Conference sessions: October 28-29 8:30am-6:00pm
Program:
-------------
(visit http://www.caitr.org/internetworking03/program.htm for abstracts and speaker details)
Sunday June 22
    Tutorial-1: MPLS VPNs 
    Tutorial-2: IPv6 
    Tutorial-3: Mobile Wireless Internet Architecture and Protocols
    Tutorial-4: Voice over Packet 
Monday June 23
    Welcome and Keynote 
    Session: Network Technology Trends
      - Forwarding Element and Control Separation
      - Evolution of Inter-Domain Routing
      - Network Processing Building Blocks: Enabling the Routers of the Future
    Session: Network Architecture
      - An architecture for IPv6 VPNs and IPv6 transport over MPLS/GMPLS multiservice backbones IPv6
      - A new routing architecture: Atomised Routing
      - Internetworking MPLS Layer 2 Transport with an IP Services Network
    Session: Storage Area Networks
      - Storage as a Network Node
      - Object-Based Storage
      - Design, Implementation, and ! Performance Analysis of the iSCSI Protocol for SCSI over TCP/IP
      - SANs Considerations
 
    Session: Mobile & Wireless Networks
      - CertBU: Certificate-based Techniques for Securing Mobile IPv6 Binding Updates IPv6
      - Challenges and Roadmap of UMTS Network Deployment
      - Inter-working Mobile IPv6 with IP Multimedia Subsystem in UMTS 
      - Mobile Authentication and QoS 
      - Mobile Handoff Technologies 
Tuesday June 24
    Session: Inter-Domain Routing
      - Optimizing Route Convergence
      - Traceroute and BGP AS Path Incongruities 
      - Domain Constrained Multicast: A New Approach for IP Multicast Routing
 
    Session: Applications & Services
     -  Securing the Web with Next Generation Encryption Technologies
     - Impact of the live radio on the Internet, and the real-time streaming audio, in the ComUNITY cable system from Com21
     - A novel EAC semantic for the RTSP protocol
     - Towards an end-to-end architecture integrating new Transport and IP services in a DiffServ Internet
 
    Session: Network Management & Planning
     -  Pseudowire OAM: A Mandatory Ye! t Often Overlooked Feature 
     - A Multicommodity Flow Formulation for the MPLS Layout Design: Reduced Complexity Layout and Minimum Relayout Probems
     - Design Of Fast Fault Restoration System For WDM Networks
     - Cross-domain multimedia service provisioning, the EVOLUTE solution
 
    Session: QoS Based Routing
     - QoS Routing in Networks with Non-Deterministic Information
     - Active Dynamic Routing
     - QoS routing for Differentiated Services: simulations and prototype experiments
     - Probabilistic routing for QoS improvement in GPS networks
     - Fluid flow network modeling for hop-by-hop feedback control design and analysis
 
We look forward to seeing you at the Conference.
Regards,
 Conference Technical Co-chai! rs:
 - Dr. Maurice Gagnaire, ENST, France
 - Daniel Awduche
 Technical Program Committee of the Internetworking 2003 Conference:
 - Roberto Sabella, Erisson
 - Dr. Moshe Zukerman, Univ. of Melbourne
 - Nada Golmie, NIST
 - Dr. Guy Pujolle, LIP6, France
 - Dr. Samir Tohme, ENST, France
 - Stefano Trumpy, Italian National Research Council
 - Dr. Ibrahim Habib, City Univ. of NY
 - Dr. Marc Lobelle, UCL University, Belgium
 - Dr. Parviz Yegani, Cisco Systems
 - Dr. G.S. Kuo
 - Dr. Abbas Jamalipour, Univ. of Sydney
 - Dr. Hussein Mouftah, Univ. of Ottawa
 - James Kempf
 - Elizabeth Rodriguez
 - Dr. Ferit Yegenoglu, Isocore
 - Dr. Ali Zadeh, George Mason University
 - Dr. Tony Przygienda, Xebeo
 - Ran Canetti, IBM

 
--0-1505361720-1052153383=:13982-- _______________________________________________ routing-discussion mailing list routing-discussion@ietf.org https://www1.ietf.org/mailman/listinfo/routing-discussion From mailnull@www1.ietf.org Mon May 5 13:02:06 2003 Received: from www1.ietf.org (ietf.org [132.151.1.19] (may be forged)) by ietf.org (8.9.1a/8.9.1a) with ESMTP id NAA08032 for ; Mon, 5 May 2003 13:02:06 -0400 (EDT) Received: (from mailnull@localhost) by www1.ietf.org (8.11.6/8.11.6) id h45HABb18098 for routing-discussion-archive@odin.ietf.org; Mon, 5 May 2003 13:10:11 -0400 Received: from www1.ietf.org (localhost.localdomain [127.0.0.1]) by www1.ietf.org (8.11.6/8.11.6) with ESMTP id h45Gx9816607; Mon, 5 May 2003 12:59:09 -0400 Received: from ietf.org (odin.ietf.org [132.151.1.176]) by www1.ietf.org (8.11.6/8.11.6) with ESMTP id h45Gu9816488 for ; Mon, 5 May 2003 12:56:09 -0400 Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id MAA07471 for ; Mon, 5 May 2003 12:47:34 -0400 (EDT) Received: from ietf-mx ([132.151.6.1]) by ietf-mx with esmtp (Exim 4.12) id 19Cj9p-0006y3-00 for routing-discussion@ietf.org; Mon, 05 May 2003 12:49:41 -0400 Received: from web41804.mail.yahoo.com ([66.218.93.138]) by ietf-mx with smtp (Exim 4.12) id 19Cj9j-0006xl-00 for routing-discussion@ietf.org; Mon, 05 May 2003 12:49:35 -0400 Message-ID: <20030505164943.14475.qmail@web41804.mail.yahoo.com> Received: from [65.213.193.49] by web41804.mail.yahoo.com via HTTP; Mon, 05 May 2003 09:49:43 PDT From: CAITR Reply-To: info@caitr.org Subject: Internetworking 2003: Call for Participation To: routing-discussion@ietf.org MIME-Version: 1.0 Content-Type: multipart/alternative; boundary="0-1505361720-1052153383=:13982" Sender: routing-discussion-admin@ietf.org Errors-To: routing-discussion-admin@ietf.org X-BeenThere: routing-discussion@ietf.org X-Mailman-Version: 2.0.12 Precedence: bulk List-Unsubscribe: , List-Id: Routing Area General mailing list List-Post: List-Help: List-Subscribe: , List-Archive: Date: Mon, 5 May 2003 09:49:43 -0700 (PDT) --0-1505361720-1052153383=:13982 Content-Type: text/plain; charset=us-ascii Internetworking 2003 International Conference Hilton San Jose & Towers Hotel, California June 22-June 24, 2003 http://www.caitr.org/internetworking03/index.htm You are cordially invited to attend the Internetworking 2003 International Conference to be held in San Jose, California, June 22-24, 2003. The 3-day event consists of two-days of highly technical sessions, preceded by four technical tutorials.Registration for the conference is underway. Please visit http://www.caitr.org/internetworking03/registration.htm and follow instructions for registration. The early registration discounts are extremely attractive and are valid till June 1, 2003.Important Dates: --------------------- - Early Registration Rates Cut-Off Date: Sept 30 - Tutorials: Oct 27, 1:00-6:00 pm - Conference sessions: October 28-29 8:30am-6:00pmProgram: ------------- (visit http://www.caitr.org/internetworking03/program.htm for abstracts and speaker details)Sunday June 22 Tutorial-1: MPLS VPNs Tutorial-2: IPv6 Tutorial-3: Mobile Wireless Internet Architecture and Protocols Tutorial-4: Voice over Packet Monday June 23 Welcome and Keynote Session: Network Technology Trends - Forwarding Element and Control Separation - Evolution of Inter-Domain Routing - Network Processing Building Blocks: Enabling the Routers of the Future Session: Network Architecture - An architecture for IPv6 VPNs and IPv6 transport over MPLS/GMPLS multiservice backbones IPv6 - A new routing architecture: Atomised Routing - Internetworking MPLS Layer 2 Transport with an IP Services Network Session: Storage Area Networks - Storage as a Network Node - Object-Based Storage - Design, Implementation, and Performance Analysis of the iSCSI Protocol for SCSI over TCP/IP - SANs Considerations Session: Mobile & Wireless Networks - CertBU: Certificate-based Techniques for Securing Mobile IPv6 Binding Updates IPv6 - Challenges and Roadmap of UMTS Network Deployment - Inter-working Mobile IPv6 with IP Multimedia Subsystem in UMTS - Mobile Authentication and QoS - Mobile Handoff Technologies Tuesday June 24 Session: Inter-Domain Routing - Optimizing Route Convergence - Traceroute and BGP AS Path Incongruities - Domain Constrained Multicast: A New Approach for IP Multicast Routing Session: Applications & Services - Securing the Web with Next Generation Encryption Technologies - Impact of the live radio on the Internet, and the real-time streaming audio, in the ComUNITY cable system from Com21 - A novel EAC semantic for the RTSP protocol - Towards an end-to-end architecture integrating new Transport and IP services in a DiffServ Internet Session: Network Management & Planning - Pseudowire OAM: A Mandatory Yet Often Overlooked Feature - A Multicommodity Flow Formulation for the MPLS Layout Design: Reduced Complexity Layout and Minimum Relayout Probems - Design Of Fast Fault Restoration System For WDM Networks - Cross-domain multimedia service provisioning, the EVOLUTE solution Session: QoS Based Routing - QoS Routing in Networks with Non-Deterministic Information - Active Dynamic Routing - QoS routing for Differentiated Services: simulations and prototype experiments - Probabilistic routing for QoS improvement in GPS networks - Fluid flow network modeling for hop-by-hop feedback control design and analysis We look forward to seeing you at the Conference. Regards, Conference Technical Co-chairs: - Dr. Maurice Gagnaire, ENST, France - Daniel Awduche Technical Program Committee of the Internetworking 2003 Conference: - Roberto Sabella, Erisson - Dr. Moshe Zukerman, Univ. of Melbourne - Nada Golmie, NIST - Dr. Guy Pujolle, LIP6, France - Dr. Samir Tohme, ENST, France - Stefano Trumpy, Italian National Research Council - Dr. Ibrahim Habib, City Univ. of NY - Dr. Marc Lobelle, UCL University, Belgium - Dr. Parviz Yegani, Cisco Systems - Dr. G.S. Kuo - Dr. Abbas Jamalipour, Univ. of Sydney - Dr. Hussein Mouftah, Univ. of Ottawa - James Kempf - Elizabeth Rodriguez - Dr. Ferit Yegenoglu, Isocore - Dr. Ali Zadeh, George Mason University - Dr. Tony Przygienda, Xebeo - Ran Canetti, IBM --0-1505361720-1052153383=:13982 Content-Type: text/html; charset=us-ascii
 
     Internetworking 2003 International Conference
     Hilton San Jose & Towers Hotel, California
              June 22-June 24, 2003
    http://www.caitr.org/internetworking03/index.htm
  
You are cordially invited to attend the Internetworking 2003 International Conference to be held in San Jose, California, June 22-24, 2003. The 3-day event consists of two-days of highly technical sessions, preceded by four technical tutorials.
Registration for the conference is underway. Please visit http://www.caitr.org/internetworking03/registration.htm and follow instructions for registration. The early registration discounts are extremely attractive and are valid till June 1, 2003.
Important Dates:
---------------------
- Early Registration Rates Cut-Off Date: Sept 30
- Tutorials: Oct 27, 1:00-6:00 pm
- Conference sessions: October 28-29 8:30am-6:00pm
Program:
-------------
(visit http://www.caitr.org/internetworking03/program.htm for abstracts and speaker details)
Sunday June 22
    Tutorial-1: MPLS VPNs 
    Tutorial-2: IPv6 
    Tutorial-3: Mobile Wireless Internet Architecture and Protocols
    Tutorial-4: Voice over Packet 
Monday June 23
    Welcome and Keynote 
    Session: Network Technology Trends
      - Forwarding Element and Control Separation
      - Evolution of Inter-Domain Routing
      - Network Processing Building Blocks: Enabling the Routers of the Future
    Session: Network Architecture
      - An architecture for IPv6 VPNs and IPv6 transport over MPLS/GMPLS multiservice backbones IPv6
      - A new routing architecture: Atomised Routing
      - Internetworking MPLS Layer 2 Transport with an IP Services Network
    Session: Storage Area Networks
      - Storage as a Network Node
      - Object-Based Storage
      - Design, Implementation, and ! Performance Analysis of the iSCSI Protocol for SCSI over TCP/IP
      - SANs Considerations
 
    Session: Mobile & Wireless Networks
      - CertBU: Certificate-based Techniques for Securing Mobile IPv6 Binding Updates IPv6
      - Challenges and Roadmap of UMTS Network Deployment
      - Inter-working Mobile IPv6 with IP Multimedia Subsystem in UMTS 
      - Mobile Authentication and QoS 
      - Mobile Handoff Technologies 
Tuesday June 24
    Session: Inter-Domain Routing
      - Optimizing Route Convergence
      - Traceroute and BGP AS Path Incongruities 
      - Domain Constrained Multicast: A New Approach for IP Multicast Routing
 
    Session: Applications & Services
     -  Securing the Web with Next Generation Encryption Technologies
     - Impact of the live radio on the Internet, and the real-time streaming audio, in the ComUNITY cable system from Com21
     - A novel EAC semantic for the RTSP protocol
     - Towards an end-to-end architecture integrating new Transport and IP services in a DiffServ Internet
 
    Session: Network Management & Planning
     -  Pseudowire OAM: A Mandatory Ye! t Often Overlooked Feature 
     - A Multicommodity Flow Formulation for the MPLS Layout Design: Reduced Complexity Layout and Minimum Relayout Probems
     - Design Of Fast Fault Restoration System For WDM Networks
     - Cross-domain multimedia service provisioning, the EVOLUTE solution
 
    Session: QoS Based Routing
     - QoS Routing in Networks with Non-Deterministic Information
     - Active Dynamic Routing
     - QoS routing for Differentiated Services: simulations and prototype experiments
     - Probabilistic routing for QoS improvement in GPS networks
     - Fluid flow network modeling for hop-by-hop feedback control design and analysis
 
We look forward to seeing you at the Conference.
Regards,
 Conference Technical Co-chai! rs:
 - Dr. Maurice Gagnaire, ENST, France
 - Daniel Awduche
 Technical Program Committee of the Internetworking 2003 Conference:
 - Roberto Sabella, Erisson
 - Dr. Moshe Zukerman, Univ. of Melbourne
 - Nada Golmie, NIST
 - Dr. Guy Pujolle, LIP6, France
 - Dr. Samir Tohme, ENST, France
 - Stefano Trumpy, Italian National Research Council
 - Dr. Ibrahim Habib, City Univ. of NY
 - Dr. Marc Lobelle, UCL University, Belgium
 - Dr. Parviz Yegani, Cisco Systems
 - Dr. G.S. Kuo
 - Dr. Abbas Jamalipour, Univ. of Sydney
 - Dr. Hussein Mouftah, Univ. of Ottawa
 - James Kempf
 - Elizabeth Rodriguez
 - Dr. Ferit Yegenoglu, Isocore
 - Dr. Ali Zadeh, George Mason University
 - Dr. Tony Przygienda, Xebeo
 - Ran Canetti, IBM

 
--0-1505361720-1052153383=:13982-- _______________________________________________ routing-discussion mailing list routing-discussion@ietf.org https://www1.ietf.org/mailman/listinfo/routing-discussion From routing-discussion-admin@ietf.org Tue May 6 13:01:52 2003 Received: from www1.ietf.org (ietf.org [132.151.1.19] (may be forged)) by ietf.org (8.9.1a/8.9.1a) with ESMTP id NAA29418 for ; Tue, 6 May 2003 13:01:52 -0400 (EDT) Received: from www1.ietf.org (localhost.localdomain [127.0.0.1]) by www1.ietf.org (8.11.6/8.11.6) with ESMTP id h46H2d808077; Tue, 6 May 2003 13:02:39 -0400 Received: from ietf.org (odin.ietf.org [132.151.1.176]) by www1.ietf.org (8.11.6/8.11.6) with ESMTP id h46H00807949 for ; Tue, 6 May 2003 13:00:00 -0400 Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id MAA29135 for ; Tue, 6 May 2003 12:50:56 -0400 (EDT) Received: from ietf-mx ([132.151.6.1]) by ietf-mx with esmtp (Exim 4.12) id 19D5gb-0000XO-00 for routing-discussion@ietf.org; Tue, 06 May 2003 12:53:01 -0400 Received: from web13307.mail.yahoo.com ([216.136.175.43]) by ietf-mx with smtp (Exim 4.12) id 19D5gb-0000XK-00 for routing-discussion@ietf.org; Tue, 06 May 2003 12:53:01 -0400 Message-ID: <20030506165351.50033.qmail@web13307.mail.yahoo.com> Received: from [129.21.145.88] by web13307.mail.yahoo.com via HTTP; Tue, 06 May 2003 12:53:51 EDT From: Sudip Misra Subject: SWP and WSP Routing Algorithms To: routing-discussion@ietf.org MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Sender: routing-discussion-admin@ietf.org Errors-To: routing-discussion-admin@ietf.org X-BeenThere: routing-discussion@ietf.org X-Mailman-Version: 2.0.12 Precedence: bulk List-Unsubscribe: , List-Id: Routing Area General mailing list List-Post: List-Help: List-Subscribe: , List-Archive: Date: Tue, 6 May 2003 12:53:51 -0400 (EDT) Hi, Is there anyone who has worked on or implemented the following Routing Algorithms before. * Shortest Widest Path Algorithms (by Wong and Crowcroft). * Widest Shortest Path (by Guerin et al.) I would need some help in this regard in terms of some clarifications and informations. If there is anyone out there who could possibly of help, I would very much apprecite it. Thanks a lot. Regards, Sudip ______________________________________________________________________ Post your free ad now! http://personals.yahoo.ca _______________________________________________ routing-discussion mailing list routing-discussion@ietf.org https://www1.ietf.org/mailman/listinfo/routing-discussion From mailnull@www1.ietf.org Tue May 6 13:02:58 2003 Received: from www1.ietf.org (ietf.org [132.151.1.19] (may be forged)) by ietf.org (8.9.1a/8.9.1a) with ESMTP id NAA29473 for ; Tue, 6 May 2003 13:02:57 -0400 (EDT) Received: (from mailnull@localhost) by www1.ietf.org (8.11.6/8.11.6) id h46HBWR09401 for routing-discussion-archive@odin.ietf.org; Tue, 6 May 2003 13:11:32 -0400 Received: from www1.ietf.org (localhost.localdomain [127.0.0.1]) by www1.ietf.org (8.11.6/8.11.6) with ESMTP id h46H2d808077; Tue, 6 May 2003 13:02:39 -0400 Received: from ietf.org (odin.ietf.org [132.151.1.176]) by www1.ietf.org (8.11.6/8.11.6) with ESMTP id h46H00807949 for ; Tue, 6 May 2003 13:00:00 -0400 Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id MAA29135 for ; Tue, 6 May 2003 12:50:56 -0400 (EDT) Received: from ietf-mx ([132.151.6.1]) by ietf-mx with esmtp (Exim 4.12) id 19D5gb-0000XO-00 for routing-discussion@ietf.org; Tue, 06 May 2003 12:53:01 -0400 Received: from web13307.mail.yahoo.com ([216.136.175.43]) by ietf-mx with smtp (Exim 4.12) id 19D5gb-0000XK-00 for routing-discussion@ietf.org; Tue, 06 May 2003 12:53:01 -0400 Message-ID: <20030506165351.50033.qmail@web13307.mail.yahoo.com> Received: from [129.21.145.88] by web13307.mail.yahoo.com via HTTP; Tue, 06 May 2003 12:53:51 EDT From: Sudip Misra Subject: SWP and WSP Routing Algorithms To: routing-discussion@ietf.org MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Sender: routing-discussion-admin@ietf.org Errors-To: routing-discussion-admin@ietf.org X-BeenThere: routing-discussion@ietf.org X-Mailman-Version: 2.0.12 Precedence: bulk List-Unsubscribe: , List-Id: Routing Area General mailing list List-Post: List-Help: List-Subscribe: , List-Archive: Date: Tue, 6 May 2003 12:53:51 -0400 (EDT) Hi, Is there anyone who has worked on or implemented the following Routing Algorithms before. * Shortest Widest Path Algorithms (by Wong and Crowcroft). * Widest Shortest Path (by Guerin et al.) I would need some help in this regard in terms of some clarifications and informations. If there is anyone out there who could possibly of help, I would very much apprecite it. Thanks a lot. Regards, Sudip ______________________________________________________________________ Post your free ad now! http://personals.yahoo.ca _______________________________________________ routing-discussion mailing list routing-discussion@ietf.org https://www1.ietf.org/mailman/listinfo/routing-discussion From routing-discussion-admin@ietf.org Tue May 6 19:34:52 2003 Received: from www1.ietf.org (ietf.org [132.151.1.19] (may be forged)) by ietf.org (8.9.1a/8.9.1a) with ESMTP id TAA14183 for ; Tue, 6 May 2003 19:34:51 -0400 (EDT) Received: from www1.ietf.org (localhost.localdomain [127.0.0.1]) by www1.ietf.org (8.11.6/8.11.6) with ESMTP id h46Naf807519; Tue, 6 May 2003 19:36:41 -0400 Received: from ietf.org (odin.ietf.org [132.151.1.176]) by www1.ietf.org (8.11.6/8.11.6) with ESMTP id h46NYL807436 for ; Tue, 6 May 2003 19:34:21 -0400 Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id TAA13922 for ; Tue, 6 May 2003 19:25:09 -0400 (EDT) Received: from ietf-mx ([132.151.6.1]) by ietf-mx with esmtp (Exim 4.12) id 19DBq6-0003Q2-00 for routing-discussion@ietf.org; Tue, 06 May 2003 19:27:14 -0400 Received: from web13309.mail.yahoo.com ([216.136.175.192]) by ietf-mx with smtp (Exim 4.12) id 19DBq5-0003Pz-00 for routing-discussion@ietf.org; Tue, 06 May 2003 19:27:13 -0400 Message-ID: <20030506232804.28696.qmail@web13309.mail.yahoo.com> Received: from [65.48.32.73] by web13309.mail.yahoo.com via HTTP; Tue, 06 May 2003 19:28:04 EDT From: Sudip Misra Subject: Shortest Widest Path (SWP) and Widest Shortest Path (WSP) Routing Algorithms To: routing-discussion@ietf.org MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Sender: routing-discussion-admin@ietf.org Errors-To: routing-discussion-admin@ietf.org X-BeenThere: routing-discussion@ietf.org X-Mailman-Version: 2.0.12 Precedence: bulk List-Unsubscribe: , List-Id: Routing Area General mailing list List-Post: List-Help: List-Subscribe: , List-Archive: Date: Tue, 6 May 2003 19:28:04 -0400 (EDT) Hi, Is there anyone who has worked on or implemented any of the following Routing Algorithms before. * Shortest Widest Path (SWP) Algorithms (by Wong and Crowcroft). * Widest Shortest Path (WSP) (by Guerin et al.) I would need some help in this regard in terms of some clarifications and informations. If there is anyone out there who could possibly be of help, I would very much apprecite it. Thanks a lot. Regards, Sudip ______________________________________________________________________ Post your free ad now! http://personals.yahoo.ca _______________________________________________ routing-discussion mailing list routing-discussion@ietf.org https://www1.ietf.org/mailman/listinfo/routing-discussion From mailnull@www1.ietf.org Tue May 6 19:35:35 2003 Received: from www1.ietf.org (ietf.org [132.151.1.19] (may be forged)) by ietf.org (8.9.1a/8.9.1a) with ESMTP id TAA14199 for ; Tue, 6 May 2003 19:35:35 -0400 (EDT) Received: (from mailnull@localhost) by www1.ietf.org (8.11.6/8.11.6) id h46NiH008810 for routing-discussion-archive@odin.ietf.org; Tue, 6 May 2003 19:44:17 -0400 Received: from www1.ietf.org (localhost.localdomain [127.0.0.1]) by www1.ietf.org (8.11.6/8.11.6) with ESMTP id h46Naf807519; Tue, 6 May 2003 19:36:41 -0400 Received: from ietf.org (odin.ietf.org [132.151.1.176]) by www1.ietf.org (8.11.6/8.11.6) with ESMTP id h46NYL807436 for ; Tue, 6 May 2003 19:34:21 -0400 Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id TAA13922 for ; Tue, 6 May 2003 19:25:09 -0400 (EDT) Received: from ietf-mx ([132.151.6.1]) by ietf-mx with esmtp (Exim 4.12) id 19DBq6-0003Q2-00 for routing-discussion@ietf.org; Tue, 06 May 2003 19:27:14 -0400 Received: from web13309.mail.yahoo.com ([216.136.175.192]) by ietf-mx with smtp (Exim 4.12) id 19DBq5-0003Pz-00 for routing-discussion@ietf.org; Tue, 06 May 2003 19:27:13 -0400 Message-ID: <20030506232804.28696.qmail@web13309.mail.yahoo.com> Received: from [65.48.32.73] by web13309.mail.yahoo.com via HTTP; Tue, 06 May 2003 19:28:04 EDT From: Sudip Misra Subject: Shortest Widest Path (SWP) and Widest Shortest Path (WSP) Routing Algorithms To: routing-discussion@ietf.org MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Sender: routing-discussion-admin@ietf.org Errors-To: routing-discussion-admin@ietf.org X-BeenThere: routing-discussion@ietf.org X-Mailman-Version: 2.0.12 Precedence: bulk List-Unsubscribe: , List-Id: Routing Area General mailing list List-Post: List-Help: List-Subscribe: , List-Archive: Date: Tue, 6 May 2003 19:28:04 -0400 (EDT) Hi, Is there anyone who has worked on or implemented any of the following Routing Algorithms before. * Shortest Widest Path (SWP) Algorithms (by Wong and Crowcroft). * Widest Shortest Path (WSP) (by Guerin et al.) I would need some help in this regard in terms of some clarifications and informations. If there is anyone out there who could possibly be of help, I would very much apprecite it. Thanks a lot. Regards, Sudip ______________________________________________________________________ Post your free ad now! http://personals.yahoo.ca _______________________________________________ routing-discussion mailing list routing-discussion@ietf.org https://www1.ietf.org/mailman/listinfo/routing-discussion From routing-discussion-admin@ietf.org Thu May 8 22:08:51 2003 Received: from www1.ietf.org (ietf.org [132.151.1.19] (may be forged)) by ietf.org (8.9.1a/8.9.1a) with ESMTP id WAA19737 for ; Thu, 8 May 2003 22:08:50 -0400 (EDT) Received: from www1.ietf.org (localhost.localdomain [127.0.0.1]) by www1.ietf.org (8.11.6/8.11.6) with ESMTP id h4927u809136; Thu, 8 May 2003 22:07:56 -0400 Received: from ietf.org (odin.ietf.org [132.151.1.176]) by www1.ietf.org (8.11.6/8.11.6) with ESMTP id h4925e808206 for ; Thu, 8 May 2003 22:05:40 -0400 Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id VAA19396 for ; Thu, 8 May 2003 21:55:25 -0400 (EDT) Received: from ietf-mx ([132.151.6.1]) by ietf-mx with esmtp (Exim 4.12) id 19Dx8a-0000S5-00 for routing-discussion@ietf.org; Thu, 08 May 2003 21:57:28 -0400 Received: from web13303.mail.yahoo.com ([216.136.175.39]) by ietf-mx with smtp (Exim 4.12) id 19Dx8a-0000S2-00 for routing-discussion@ietf.org; Thu, 08 May 2003 21:57:28 -0400 Message-ID: <20030509015823.23341.qmail@web13303.mail.yahoo.com> Received: from [65.48.32.73] by web13303.mail.yahoo.com via HTTP; Thu, 08 May 2003 21:58:23 EDT From: Sudip Misra Subject: Bellman-Ford's Shortest Path algorithm To: routing-discussion@ietf.org, ns-users@isi.edu, mpls-ops@mplsrc.com MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Sender: routing-discussion-admin@ietf.org Errors-To: routing-discussion-admin@ietf.org X-BeenThere: routing-discussion@ietf.org X-Mailman-Version: 2.0.12 Precedence: bulk List-Unsubscribe: , List-Id: Routing Area General mailing list List-Post: List-Help: List-Subscribe: , List-Archive: Date: Thu, 8 May 2003 21:58:23 -0400 (EDT) Hi, Does anyone have the implementation of Bellman-Ford's shortest path algorithm or an analogous algorithm. I am sure someone out there must have already done it already. I would be thankful, if someone can share his/her code with me. Thanks, Sudip ______________________________________________________________________ Post your free ad now! http://personals.yahoo.ca _______________________________________________ routing-discussion mailing list routing-discussion@ietf.org https://www1.ietf.org/mailman/listinfo/routing-discussion From mailnull@www1.ietf.org Thu May 8 22:09:35 2003 Received: from www1.ietf.org (ietf.org [132.151.1.19] (may be forged)) by ietf.org (8.9.1a/8.9.1a) with ESMTP id WAA19781 for ; Thu, 8 May 2003 22:09:35 -0400 (EDT) Received: (from mailnull@localhost) by www1.ietf.org (8.11.6/8.11.6) id h492JJb09499 for routing-discussion-archive@odin.ietf.org; Thu, 8 May 2003 22:19:19 -0400 Received: from www1.ietf.org (localhost.localdomain [127.0.0.1]) by www1.ietf.org (8.11.6/8.11.6) with ESMTP id h4927u809136; Thu, 8 May 2003 22:07:56 -0400 Received: from ietf.org (odin.ietf.org [132.151.1.176]) by www1.ietf.org (8.11.6/8.11.6) with ESMTP id h4925e808206 for ; Thu, 8 May 2003 22:05:40 -0400 Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id VAA19396 for ; Thu, 8 May 2003 21:55:25 -0400 (EDT) Received: from ietf-mx ([132.151.6.1]) by ietf-mx with esmtp (Exim 4.12) id 19Dx8a-0000S5-00 for routing-discussion@ietf.org; Thu, 08 May 2003 21:57:28 -0400 Received: from web13303.mail.yahoo.com ([216.136.175.39]) by ietf-mx with smtp (Exim 4.12) id 19Dx8a-0000S2-00 for routing-discussion@ietf.org; Thu, 08 May 2003 21:57:28 -0400 Message-ID: <20030509015823.23341.qmail@web13303.mail.yahoo.com> Received: from [65.48.32.73] by web13303.mail.yahoo.com via HTTP; Thu, 08 May 2003 21:58:23 EDT From: Sudip Misra Subject: Bellman-Ford's Shortest Path algorithm To: routing-discussion@ietf.org, ns-users@isi.edu, mpls-ops@mplsrc.com MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Sender: routing-discussion-admin@ietf.org Errors-To: routing-discussion-admin@ietf.org X-BeenThere: routing-discussion@ietf.org X-Mailman-Version: 2.0.12 Precedence: bulk List-Unsubscribe: , List-Id: Routing Area General mailing list List-Post: List-Help: List-Subscribe: , List-Archive: Date: Thu, 8 May 2003 21:58:23 -0400 (EDT) Hi, Does anyone have the implementation of Bellman-Ford's shortest path algorithm or an analogous algorithm. I am sure someone out there must have already done it already. I would be thankful, if someone can share his/her code with me. Thanks, Sudip ______________________________________________________________________ Post your free ad now! http://personals.yahoo.ca _______________________________________________ routing-discussion mailing list routing-discussion@ietf.org https://www1.ietf.org/mailman/listinfo/routing-discussion From routing-discussion-admin@ietf.org Thu May 8 23:55:36 2003 Received: from www1.ietf.org (ietf.org [132.151.1.19] (may be forged)) by ietf.org (8.9.1a/8.9.1a) with ESMTP id XAA21889 for ; Thu, 8 May 2003 23:55:36 -0400 (EDT) Received: from www1.ietf.org (localhost.localdomain [127.0.0.1]) by www1.ietf.org (8.11.6/8.11.6) with ESMTP id h493pZ815552; Thu, 8 May 2003 23:51:35 -0400 Received: from ietf.org (odin.ietf.org [132.151.1.176]) by www1.ietf.org (8.11.6/8.11.6) with ESMTP id h493o1815514 for ; Thu, 8 May 2003 23:50:01 -0400 Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id XAA21599 for ; Thu, 8 May 2003 23:39:44 -0400 (EDT) Received: from ietf-mx ([132.151.6.1]) by ietf-mx with esmtp (Exim 4.12) id 19DylX-0000yA-00 for routing-discussion@ietf.org; Thu, 08 May 2003 23:41:47 -0400 Received: from workhorse.fictitious.org ([209.150.1.230]) by ietf-mx with esmtp (Exim 4.12) id 19DylW-0000y7-00 for routing-discussion@ietf.org; Thu, 08 May 2003 23:41:47 -0400 Received: from workhorse.fictitious.org (localhost.fictitious.org [127.0.0.1]) by workhorse.fictitious.org (8.9.3/8.9.3) with ESMTP id XAA36419; Thu, 8 May 2003 23:42:21 -0400 (EDT) (envelope-from curtis@workhorse.fictitious.org) Message-Id: <200305090342.XAA36419@workhorse.fictitious.org> To: Sudip Misra cc: routing-discussion@ietf.org, ns-users@isi.edu, mpls-ops@mplsrc.com Reply-To: curtis@fictitious.org Subject: Re: Bellman-Ford's Shortest Path algorithm In-reply-to: Your message of "Thu, 08 May 2003 21:58:23 EDT." <20030509015823.23341.qmail@web13303.mail.yahoo.com> From: Curtis Villamizar Sender: routing-discussion-admin@ietf.org Errors-To: routing-discussion-admin@ietf.org X-BeenThere: routing-discussion@ietf.org X-Mailman-Version: 2.0.12 Precedence: bulk List-Unsubscribe: , List-Id: Routing Area General mailing list List-Post: List-Help: List-Subscribe: , List-Archive: Date: Thu, 08 May 2003 23:42:20 -0400 In message <20030509015823.23341.qmail@web13303.mail.yahoo.com>, Sudip Misra wr ites: > Hi, > > Does anyone have the implementation of Bellman-Ford's > shortest path algorithm or an analogous algorithm. > > I am sure someone out there must have already done it > already. No. Never been implemented. Try the IRTF. [Just kidding.] > I would be thankful, if someone can share his/her code > with me. > > Thanks, > > Sudip There is a complete implementation of the OSPF protocol in John Moy's book with the CD. Also the gated code, zebra, probably lots of other sources. These are likely to be optimized Dykstra rather than Bellman-Ford. Plus Bellman-Ford, Dykstra, or optimized Dykstra is trivial to write yourself. Read Moy's book please. btw - Do you think you could shotgun your question to a few thousand more people? Routing-discuss is specifically for the work of the IETF routing area and NOT for newbie questions about routing! That also means that you probably shouldn't bother with a thank you or followup questions like "what's Dykstra" or "does anyone know the ISBN number". Curtis ps - appologies to the lists for keeping you on the Cc. Better one reply than many. _______________________________________________ routing-discussion mailing list routing-discussion@ietf.org https://www1.ietf.org/mailman/listinfo/routing-discussion From mailnull@www1.ietf.org Thu May 8 23:56:21 2003 Received: from www1.ietf.org (ietf.org [132.151.1.19] (may be forged)) by ietf.org (8.9.1a/8.9.1a) with ESMTP id XAA21921 for ; Thu, 8 May 2003 23:56:21 -0400 (EDT) Received: (from mailnull@localhost) by www1.ietf.org (8.11.6/8.11.6) id h49468p16146 for routing-discussion-archive@odin.ietf.org; Fri, 9 May 2003 00:06:08 -0400 Received: from www1.ietf.org (localhost.localdomain [127.0.0.1]) by www1.ietf.org (8.11.6/8.11.6) with ESMTP id h493pZ815552; Thu, 8 May 2003 23:51:35 -0400 Received: from ietf.org (odin.ietf.org [132.151.1.176]) by www1.ietf.org (8.11.6/8.11.6) with ESMTP id h493o1815514 for ; Thu, 8 May 2003 23:50:01 -0400 Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id XAA21599 for ; Thu, 8 May 2003 23:39:44 -0400 (EDT) Received: from ietf-mx ([132.151.6.1]) by ietf-mx with esmtp (Exim 4.12) id 19DylX-0000yA-00 for routing-discussion@ietf.org; Thu, 08 May 2003 23:41:47 -0400 Received: from workhorse.fictitious.org ([209.150.1.230]) by ietf-mx with esmtp (Exim 4.12) id 19DylW-0000y7-00 for routing-discussion@ietf.org; Thu, 08 May 2003 23:41:47 -0400 Received: from workhorse.fictitious.org (localhost.fictitious.org [127.0.0.1]) by workhorse.fictitious.org (8.9.3/8.9.3) with ESMTP id XAA36419; Thu, 8 May 2003 23:42:21 -0400 (EDT) (envelope-from curtis@workhorse.fictitious.org) Message-Id: <200305090342.XAA36419@workhorse.fictitious.org> To: Sudip Misra cc: routing-discussion@ietf.org, ns-users@isi.edu, mpls-ops@mplsrc.com Reply-To: curtis@fictitious.org Subject: Re: Bellman-Ford's Shortest Path algorithm In-reply-to: Your message of "Thu, 08 May 2003 21:58:23 EDT." <20030509015823.23341.qmail@web13303.mail.yahoo.com> From: Curtis Villamizar Sender: routing-discussion-admin@ietf.org Errors-To: routing-discussion-admin@ietf.org X-BeenThere: routing-discussion@ietf.org X-Mailman-Version: 2.0.12 Precedence: bulk List-Unsubscribe: , List-Id: Routing Area General mailing list List-Post: List-Help: List-Subscribe: , List-Archive: Date: Thu, 08 May 2003 23:42:20 -0400 In message <20030509015823.23341.qmail@web13303.mail.yahoo.com>, Sudip Misra wr ites: > Hi, > > Does anyone have the implementation of Bellman-Ford's > shortest path algorithm or an analogous algorithm. > > I am sure someone out there must have already done it > already. No. Never been implemented. Try the IRTF. [Just kidding.] > I would be thankful, if someone can share his/her code > with me. > > Thanks, > > Sudip There is a complete implementation of the OSPF protocol in John Moy's book with the CD. Also the gated code, zebra, probably lots of other sources. These are likely to be optimized Dykstra rather than Bellman-Ford. Plus Bellman-Ford, Dykstra, or optimized Dykstra is trivial to write yourself. Read Moy's book please. btw - Do you think you could shotgun your question to a few thousand more people? Routing-discuss is specifically for the work of the IETF routing area and NOT for newbie questions about routing! That also means that you probably shouldn't bother with a thank you or followup questions like "what's Dykstra" or "does anyone know the ISBN number". Curtis ps - appologies to the lists for keeping you on the Cc. Better one reply than many. _______________________________________________ routing-discussion mailing list routing-discussion@ietf.org https://www1.ietf.org/mailman/listinfo/routing-discussion From routing-discussion-admin@ietf.org Sun May 11 14:08:57 2003 Received: from www1.ietf.org (ietf.org [132.151.1.19] (may be forged)) by ietf.org (8.9.1a/8.9.1a) with ESMTP id OAA09296 for ; Sun, 11 May 2003 14:08:57 -0400 (EDT) Received: from www1.ietf.org (localhost.localdomain [127.0.0.1]) by www1.ietf.org (8.11.6/8.11.6) with ESMTP id h4BH0fB04156; Sun, 11 May 2003 13:00:41 -0400 Received: from ietf.org (odin.ietf.org [132.151.1.176]) by www1.ietf.org (8.11.6/8.11.6) with ESMTP id h498dd815565 for ; Fri, 9 May 2003 04:39:39 -0400 Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id EAA09226 for ; Fri, 9 May 2003 04:29:17 -0400 (EDT) Received: from ietf-mx ([132.151.6.1]) by ietf-mx with esmtp (Exim 4.12) id 19E3Hk-0002e8-00 for routing-discussion@ietf.org; Fri, 09 May 2003 04:31:20 -0400 Received: from alc240.alcatel.be ([195.207.101.240] helo=bt0rjw.god.bel.alcatel.be) by ietf-mx with esmtp (Exim 4.12) id 19E3Hj-0002dg-00 for routing-discussion@ietf.org; Fri, 09 May 2003 04:31:19 -0400 Received: from Bemail06.net.alcatel.be (bemail06.net.alcatel.be [138.203.144.83]) by bt0rjw.god.bel.alcatel.be (8.12.9/8.11.4) with ESMTP id h498VeLt029336; Fri, 9 May 2003 10:31:41 +0200 (MEST) Received: from bt0azf ([138.203.12.179]) by Bemail06.net.alcatel.be (Lotus Domino Release 5.0.11) with SMTP id 2003050910313779:2116 ; Fri, 9 May 2003 10:31:37 +0200 From: Sebastien.Spas@alcatel.be To: "Sudip Misra" , , , Subject: RE: [MPLS-OPS]: Bellman-Ford's Shortest Path algorithm Message-ID: MIME-Version: 1.0 X-Priority: 3 (Normal) X-MSMail-Priority: Normal X-Mailer: Microsoft Outlook IMO, Build 9.0.2416 (9.0.2911.0) X-MimeOLE: Produced By Microsoft MimeOLE V5.50.4910.0300 In-Reply-To: <20030509015823.23341.qmail@web13303.mail.yahoo.com> Importance: Normal X-MIMETrack: Itemize by SMTP Server on BEMAIL06/BE/ALCATEL(Release 5.0.11 |July 24, 2002) at 05/09/2003 10:31:37, Serialize by Router on BEMAIL06/BE/ALCATEL(Release 5.0.11 |July 24, 2002) at 05/09/2003 10:31:40, Serialize complete at 05/09/2003 10:31:40 Content-Transfer-Encoding: 7bit Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit Sender: routing-discussion-admin@ietf.org Errors-To: routing-discussion-admin@ietf.org X-BeenThere: routing-discussion@ietf.org X-Mailman-Version: 2.0.12 Precedence: bulk List-Unsubscribe: , List-Id: Routing Area General mailing list List-Post: List-Help: List-Subscribe: , List-Archive: Date: Fri, 9 May 2003 10:31:38 +0200 Content-Transfer-Encoding: 7bit Hi, you can find some on the web : http://www.people.virginia.edu/~ec3z/software.html one in excel : http://www.cs.uwyo.edu/~duden/spring2002/cs3020/lab9/ one in java : http://rollerjm.free.fr/pro/graphs.html kr, sebastien. -----Original Message----- From: Sudip Misra [mailto:sudip_misra2003@yahoo.ca] Sent: vendredi 9 mai 2003 3:58 To: routing-discussion@ietf.org; ns-users@isi.edu; mpls-ops@mplsrc.com Subject: [MPLS-OPS]: Bellman-Ford's Shortest Path algorithm Hi, Does anyone have the implementation of Bellman-Ford's shortest path algorithm or an analogous algorithm. I am sure someone out there must have already done it already. I would be thankful, if someone can share his/her code with me. Thanks, Sudip ______________________________________________________________________ Post your free ad now! http://personals.yahoo.ca ------- The MPLS-OPS Mailing List Subscribe/Unsubscribe: http://www.mplsrc.com/mplsops.shtml Archive: http://www.mplsrc.com/mpls-ops_archive.shtml _______________________________________________ routing-discussion mailing list routing-discussion@ietf.org https://www1.ietf.org/mailman/listinfo/routing-discussion From mailnull@www1.ietf.org Sun May 11 14:12:51 2003 Received: from www1.ietf.org (ietf.org [132.151.1.19] (may be forged)) by ietf.org (8.9.1a/8.9.1a) with ESMTP id OAA09357 for ; Sun, 11 May 2003 14:12:51 -0400 (EDT) Received: (from mailnull@localhost) by www1.ietf.org (8.11.6/8.11.6) id h4BHc1k06893 for routing-discussion-archive@odin.ietf.org; Sun, 11 May 2003 13:38:01 -0400 Received: from www1.ietf.org (localhost.localdomain [127.0.0.1]) by www1.ietf.org (8.11.6/8.11.6) with ESMTP id h4BH0fB04156; Sun, 11 May 2003 13:00:41 -0400 Received: from ietf.org (odin.ietf.org [132.151.1.176]) by www1.ietf.org (8.11.6/8.11.6) with ESMTP id h498dd815565 for ; Fri, 9 May 2003 04:39:39 -0400 Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id EAA09226 for ; Fri, 9 May 2003 04:29:17 -0400 (EDT) Received: from ietf-mx ([132.151.6.1]) by ietf-mx with esmtp (Exim 4.12) id 19E3Hk-0002e8-00 for routing-discussion@ietf.org; Fri, 09 May 2003 04:31:20 -0400 Received: from alc240.alcatel.be ([195.207.101.240] helo=bt0rjw.god.bel.alcatel.be) by ietf-mx with esmtp (Exim 4.12) id 19E3Hj-0002dg-00 for routing-discussion@ietf.org; Fri, 09 May 2003 04:31:19 -0400 Received: from Bemail06.net.alcatel.be (bemail06.net.alcatel.be [138.203.144.83]) by bt0rjw.god.bel.alcatel.be (8.12.9/8.11.4) with ESMTP id h498VeLt029336; Fri, 9 May 2003 10:31:41 +0200 (MEST) Received: from bt0azf ([138.203.12.179]) by Bemail06.net.alcatel.be (Lotus Domino Release 5.0.11) with SMTP id 2003050910313779:2116 ; Fri, 9 May 2003 10:31:37 +0200 From: Sebastien.Spas@alcatel.be To: "Sudip Misra" , , , Subject: RE: [MPLS-OPS]: Bellman-Ford's Shortest Path algorithm Message-ID: MIME-Version: 1.0 X-Priority: 3 (Normal) X-MSMail-Priority: Normal X-Mailer: Microsoft Outlook IMO, Build 9.0.2416 (9.0.2911.0) X-MimeOLE: Produced By Microsoft MimeOLE V5.50.4910.0300 In-Reply-To: <20030509015823.23341.qmail@web13303.mail.yahoo.com> Importance: Normal X-MIMETrack: Itemize by SMTP Server on BEMAIL06/BE/ALCATEL(Release 5.0.11 |July 24, 2002) at 05/09/2003 10:31:37, Serialize by Router on BEMAIL06/BE/ALCATEL(Release 5.0.11 |July 24, 2002) at 05/09/2003 10:31:40, Serialize complete at 05/09/2003 10:31:40 Content-Transfer-Encoding: 7bit Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit Sender: routing-discussion-admin@ietf.org Errors-To: routing-discussion-admin@ietf.org X-BeenThere: routing-discussion@ietf.org X-Mailman-Version: 2.0.12 Precedence: bulk List-Unsubscribe: , List-Id: Routing Area General mailing list List-Post: List-Help: List-Subscribe: , List-Archive: Date: Fri, 9 May 2003 10:31:38 +0200 Content-Transfer-Encoding: 7bit Hi, you can find some on the web : http://www.people.virginia.edu/~ec3z/software.html one in excel : http://www.cs.uwyo.edu/~duden/spring2002/cs3020/lab9/ one in java : http://rollerjm.free.fr/pro/graphs.html kr, sebastien. -----Original Message----- From: Sudip Misra [mailto:sudip_misra2003@yahoo.ca] Sent: vendredi 9 mai 2003 3:58 To: routing-discussion@ietf.org; ns-users@isi.edu; mpls-ops@mplsrc.com Subject: [MPLS-OPS]: Bellman-Ford's Shortest Path algorithm Hi, Does anyone have the implementation of Bellman-Ford's shortest path algorithm or an analogous algorithm. I am sure someone out there must have already done it already. I would be thankful, if someone can share his/her code with me. Thanks, Sudip ______________________________________________________________________ Post your free ad now! http://personals.yahoo.ca ------- The MPLS-OPS Mailing List Subscribe/Unsubscribe: http://www.mplsrc.com/mplsops.shtml Archive: http://www.mplsrc.com/mpls-ops_archive.shtml _______________________________________________ routing-discussion mailing list routing-discussion@ietf.org https://www1.ietf.org/mailman/listinfo/routing-discussion From routing-discussion-admin@ietf.org Tue May 20 03:02:10 2003 Received: from www1.ietf.org (ietf.org [132.151.1.19] (may be forged)) by ietf.org (8.9.1a/8.9.1a) with ESMTP id DAA01658 for ; Tue, 20 May 2003 03:02:10 -0400 (EDT) Received: from www1.ietf.org (localhost.localdomain [127.0.0.1]) by www1.ietf.org (8.11.6/8.11.6) with ESMTP id h4K6OdB03540; Tue, 20 May 2003 02:24:39 -0400 Received: from ietf.org (odin.ietf.org [132.151.1.176]) by www1.ietf.org (8.11.6/8.11.6) with ESMTP id h4K6M8B03473 for ; Tue, 20 May 2003 02:22:08 -0400 Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id CAA01453 for ; Tue, 20 May 2003 02:52:19 -0400 (EDT) Received: from ietf-mx ([132.151.6.1]) by ietf-mx with esmtp (Exim 4.12) id 19I10h-0002Ju-00 for routing-discussion@ietf.org; Tue, 20 May 2003 02:54:07 -0400 Received: from web20706.mail.yahoo.com ([216.136.226.179]) by ietf-mx with smtp (Exim 4.12) id 19I10g-0002Jq-00 for routing-discussion@ietf.org; Tue, 20 May 2003 02:54:07 -0400 Message-ID: <20030520065525.34196.qmail@web20706.mail.yahoo.com> Received: from [210.118.108.254] by web20706.mail.yahoo.com via HTTP; Tue, 20 May 2003 02:55:25 EDT From: Tulip Rasputin Subject: BGP anomalous Behaviour To: routing-discussion@ietf.org MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Sender: routing-discussion-admin@ietf.org Errors-To: routing-discussion-admin@ietf.org X-BeenThere: routing-discussion@ietf.org X-Mailman-Version: 2.0.12 Precedence: bulk List-Unsubscribe: , List-Id: Routing Area General mailing list List-Post: List-Help: List-Subscribe: , List-Archive: Date: Tue, 20 May 2003 02:55:25 -0400 (EDT) Hello, I understand that this message is more pertinent to the BGP Working Group but since i am unable to send mails to that WG i am posting it here - as its anyway related to routing. Suppose a BGP Peer receives three UPDATEs for the same prefix (say a.b.c.d/mask) with the following attributes: Route 1: AS_PATH 10 100 MED 10 NEXT_HOP NH1 calculated IGP cost to reach the next-hop NH1 is 6 Route 2: AS_PATH 6 100 MED 1 NEXT_HOP NH2 IGP cost to reach NH2 is 5 Route 3: AS_PATH 6 100 MED 0 NEXT_HOP NH3 IGP cost to reach NH3 is 12 Now this router starts running its decision process. I want to know if the final outcome of the Decision Process depends upon the order in which the paths are processed. Case 1: If the receiving router processes Paths 1,2 and 3 respectively in this order. From 1 and 2 it will not compare the MEDs as they are from different ASes. Hence it looks at the IGP cost which is less in case of 2. It thus selects Path 2 and discards 1. Next it picks up 3. Here the AS is the same and hence compares the MED - and thus selects as Path 3 as the best one and uses this and this is the route which is propogated to everyone else. Case II: It processes as paths 2,3 and 1 respectively. From 2 and 3 it compares the MED as they are from same AS. It selects 3 as the MED is small. Next it compares this with 1 and selects the latter as the IGP cost to reach the NH is smaller there (6<12). Thus it now arrives at a different best path!!! Please let me know if i am correct in my understanding. Would appreciate the comments from the routing fraternity. Thanks Rasputin. ______________________________________________________________________ Post your free ad now! http://personals.yahoo.ca _______________________________________________ routing-discussion mailing list routing-discussion@ietf.org https://www1.ietf.org/mailman/listinfo/routing-discussion From mailnull@www1.ietf.org Tue May 20 03:03:01 2003 Received: from www1.ietf.org (ietf.org [132.151.1.19] (may be forged)) by ietf.org (8.9.1a/8.9.1a) with ESMTP id DAA01679 for ; Tue, 20 May 2003 03:03:01 -0400 (EDT) Received: (from mailnull@localhost) by www1.ietf.org (8.11.6/8.11.6) id h4K6WKe04223 for routing-discussion-archive@odin.ietf.org; Tue, 20 May 2003 02:32:20 -0400 Received: from www1.ietf.org (localhost.localdomain [127.0.0.1]) by www1.ietf.org (8.11.6/8.11.6) with ESMTP id h4K6OdB03540; Tue, 20 May 2003 02:24:39 -0400 Received: from ietf.org (odin.ietf.org [132.151.1.176]) by www1.ietf.org (8.11.6/8.11.6) with ESMTP id h4K6M8B03473 for ; Tue, 20 May 2003 02:22:08 -0400 Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id CAA01453 for ; Tue, 20 May 2003 02:52:19 -0400 (EDT) Received: from ietf-mx ([132.151.6.1]) by ietf-mx with esmtp (Exim 4.12) id 19I10h-0002Ju-00 for routing-discussion@ietf.org; Tue, 20 May 2003 02:54:07 -0400 Received: from web20706.mail.yahoo.com ([216.136.226.179]) by ietf-mx with smtp (Exim 4.12) id 19I10g-0002Jq-00 for routing-discussion@ietf.org; Tue, 20 May 2003 02:54:07 -0400 Message-ID: <20030520065525.34196.qmail@web20706.mail.yahoo.com> Received: from [210.118.108.254] by web20706.mail.yahoo.com via HTTP; Tue, 20 May 2003 02:55:25 EDT From: Tulip Rasputin Subject: BGP anomalous Behaviour To: routing-discussion@ietf.org MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Sender: routing-discussion-admin@ietf.org Errors-To: routing-discussion-admin@ietf.org X-BeenThere: routing-discussion@ietf.org X-Mailman-Version: 2.0.12 Precedence: bulk List-Unsubscribe: , List-Id: Routing Area General mailing list List-Post: List-Help: List-Subscribe: , List-Archive: Date: Tue, 20 May 2003 02:55:25 -0400 (EDT) Hello, I understand that this message is more pertinent to the BGP Working Group but since i am unable to send mails to that WG i am posting it here - as its anyway related to routing. Suppose a BGP Peer receives three UPDATEs for the same prefix (say a.b.c.d/mask) with the following attributes: Route 1: AS_PATH 10 100 MED 10 NEXT_HOP NH1 calculated IGP cost to reach the next-hop NH1 is 6 Route 2: AS_PATH 6 100 MED 1 NEXT_HOP NH2 IGP cost to reach NH2 is 5 Route 3: AS_PATH 6 100 MED 0 NEXT_HOP NH3 IGP cost to reach NH3 is 12 Now this router starts running its decision process. I want to know if the final outcome of the Decision Process depends upon the order in which the paths are processed. Case 1: If the receiving router processes Paths 1,2 and 3 respectively in this order. From 1 and 2 it will not compare the MEDs as they are from different ASes. Hence it looks at the IGP cost which is less in case of 2. It thus selects Path 2 and discards 1. Next it picks up 3. Here the AS is the same and hence compares the MED - and thus selects as Path 3 as the best one and uses this and this is the route which is propogated to everyone else. Case II: It processes as paths 2,3 and 1 respectively. From 2 and 3 it compares the MED as they are from same AS. It selects 3 as the MED is small. Next it compares this with 1 and selects the latter as the IGP cost to reach the NH is smaller there (6<12). Thus it now arrives at a different best path!!! Please let me know if i am correct in my understanding. Would appreciate the comments from the routing fraternity. Thanks Rasputin. ______________________________________________________________________ Post your free ad now! http://personals.yahoo.ca _______________________________________________ routing-discussion mailing list routing-discussion@ietf.org https://www1.ietf.org/mailman/listinfo/routing-discussion From mailnull@www1.ietf.org Tue May 20 19:28:33 2003 Received: from www1.ietf.org (ietf.org [132.151.1.19] (may be forged)) by ietf.org (8.9.1a/8.9.1a) with ESMTP id TAA05675 for ; Tue, 20 May 2003 19:28:33 -0400 (EDT) Received: (from mailnull@localhost) by www1.ietf.org (8.11.6/8.11.6) id h4KMt6l13124 for routing-discussion-archive@odin.ietf.org; Tue, 20 May 2003 18:55:06 -0400 Received: from www1.ietf.org (localhost.localdomain [127.0.0.1]) by www1.ietf.org (8.11.6/8.11.6) with ESMTP id h4KMn2B12753; Tue, 20 May 2003 18:49:02 -0400 Received: from ietf.org (odin.ietf.org [132.151.1.176]) by www1.ietf.org (8.11.6/8.11.6) with ESMTP id h4G8AxB22939 for ; Fri, 16 May 2003 04:10:59 -0400 Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id EAA16667 for ; Fri, 16 May 2003 04:42:49 -0400 (EDT) From: rt13@uow.edu.au Received: from ietf-mx ([132.151.6.1]) by ietf-mx with esmtp (Exim 4.12) id 19GaiB-0005FV-00 for routing-discussion@ietf.org; Fri, 16 May 2003 04:37:07 -0400 Received: from beru.its.uow.edu.au ([130.130.68.31]) by ietf-mx with esmtp (Exim 4.12) id 19Gai5-0005FO-00 for routing-discussion@ietf.org; Fri, 16 May 2003 04:37:01 -0400 Received: from beru (localhost [127.0.0.1]) by beru.its.uow.edu.au (8.12.9/8.12.9) with ESMTP id h4G8bdkq014976; Fri, 16 May 2003 18:37:40 +1000 (EST) Received: from inti.its.uow.edu.au ([130.130.37.4]) by beru.its.uow.edu.au (MailMonitor for SMTP v1.2.2 ) ; Fri, 16 May 2003 18:37:37 +1000 (EST) Received: (from sendmail@localhost) by inti.its.uow.edu.au (8.12.9/8.12.9) id h4G8bHmU022548; Fri, 16 May 2003 18:37:17 +1000 (EST) Received: from mirapoint.uow.edu.au (mirapoint.uow.edu.au[130.130.68.27]) by inti.its.uow.edu.au (UWSMTPD 1.1) with ESMTP id 4498234.22546; Friday, 16 May 2003 18:37:14 +1000 Received: from 130.130.159.81 by mirapoint.uow.edu.au (Mirapoint Messaging Server MOS 3.3.3-GR) with HTTP/1.1; Fri, 16 May 2003 18:37:13 +1000 Subject: CODE:BELLMAN FORD To: routing-discussion@ietf.org Cc: sudip_misra2003@yahoo.ca X-Mailer: Webmail Mirapoint Direct 3.3.3-GR MIME-Version: 1.0 Message-Id: <368f7.84d013bf.8166200@mirapoint.uow.edu.au> Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Content-Transfer-Encoding: 7bit Sender: routing-discussion-admin@ietf.org Errors-To: routing-discussion-admin@ietf.org X-BeenThere: routing-discussion@ietf.org X-Mailman-Version: 2.0.12 Precedence: bulk List-Unsubscribe: , List-Id: Routing Area General mailing list List-Post: List-Help: List-Subscribe: , List-Archive: Date: Fri, 16 May 2003 18:37:13 +1000 Content-Transfer-Encoding: 7bit Hi, I need a code for Bellman Ford algorithm.It could be in any language. My question is: Write a program which generates a network with controllable number of nodes N.The easiest way 2 do this is to start with a rectangle with sides X and Y.Use a pair of random numbers rx (n) and ry(n) to set coordianates of point, n at X rx(n) and Y ry(n).Allow n to cover the range 1 to N.ur program must decide whether a link exists between every pair of nodes.This can be done based on distance between them. It could be decided that a link exists if the distance between 2 nodes is less than a certain distance. Extend the program so that it simulates operation of BGP for 1 node at a time.Start the program with a fixed set of link costs perhaps unity.Set N=10.Now change value of 1 link only and allow program 2 run until all routing tables r stable.Measure time taken 2 reach stability.Repeat this test 100 times & find average time 2 reach stability.Repeat this with N=32,100,316,1000.Present results graphically showing settling time vs number of nodes. I request you 2 send me this solution by 20 May to rt13@uow.edu.au Thanks a lot.I would appreciate ur favour very much. Robin. _______________________________________________ routing-discussion mailing list routing-discussion@ietf.org https://www1.ietf.org/mailman/listinfo/routing-discussion From mailnull@www1.ietf.org Tue May 20 19:40:49 2003 Received: from www1.ietf.org (ietf.org [132.151.1.19] (may be forged)) by ietf.org (8.9.1a/8.9.1a) with ESMTP id TAA06026 for ; Tue, 20 May 2003 19:40:49 -0400 (EDT) Received: (from mailnull@localhost) by www1.ietf.org (8.11.6/8.11.6) id h4KN7Mc14204 for routing-discussion-archive@odin.ietf.org; Tue, 20 May 2003 19:07:22 -0400 Received: from www1.ietf.org (localhost.localdomain [127.0.0.1]) by www1.ietf.org (8.11.6/8.11.6) with ESMTP id h4KN1FB13387; Tue, 20 May 2003 19:01:15 -0400 Received: from ietf.org (odin.ietf.org [132.151.1.176]) by www1.ietf.org (8.11.6/8.11.6) with ESMTP id h4KN06B13320 for ; Tue, 20 May 2003 19:00:06 -0400 Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id TAA05761 for ; Tue, 20 May 2003 19:33:03 -0400 (EDT) Received: from ietf-mx ([132.151.6.1]) by ietf-mx with esmtp (Exim 4.12) id 19IGa8-0001nA-00 for routing-discussion@ietf.org; Tue, 20 May 2003 19:31:44 -0400 Received: from ginger.lcs.mit.edu ([18.26.0.82]) by ietf-mx with esmtp (Exim 4.12) id 19IGa8-0001n7-00 for routing-discussion@ietf.org; Tue, 20 May 2003 19:31:44 -0400 Received: from ginger.lcs.mit.edu (localhost [127.0.0.1]) by ginger.lcs.mit.edu (8.12.9/8.12.9) with ESMTP id h4KNX3tU019376; Tue, 20 May 2003 19:33:03 -0400 Received: (from jnc@localhost) by ginger.lcs.mit.edu (8.12.9/8.12.9/Submit) id h4KNX2Q7019375; Tue, 20 May 2003 19:33:02 -0400 From: "J. Noel Chiappa" Message-Id: <200305202333.h4KNX2Q7019375@ginger.lcs.mit.edu> To: routing-discussion@ietf.org, rt13@uow.edu.au Subject: Re: CODE:BELLMAN FORD Cc: jnc@ginger.lcs.mit.edu Sender: routing-discussion-admin@ietf.org Errors-To: routing-discussion-admin@ietf.org X-BeenThere: routing-discussion@ietf.org X-Mailman-Version: 2.0.12 Precedence: bulk List-Unsubscribe: , List-Id: Routing Area General mailing list List-Post: List-Help: List-Subscribe: , List-Archive: Date: Tue, 20 May 2003 19:33:02 -0400 > From: rt13@uow.edu.au > I need a code for Bellman Ford algorithm. .. My question is: > Write a program which generates a network > ... > I request you 2 send me this solution by 20 May Maybe you should do your own homework assignment, instead of asking someone else to do it for you? Noel _______________________________________________ routing-discussion mailing list routing-discussion@ietf.org https://www1.ietf.org/mailman/listinfo/routing-discussion From mailnull@www1.ietf.org Tue May 20 19:46:00 2003 Received: from www1.ietf.org (ietf.org [132.151.1.19] (may be forged)) by ietf.org (8.9.1a/8.9.1a) with ESMTP id TAA06175 for ; Tue, 20 May 2003 19:46:00 -0400 (EDT) Received: (from mailnull@localhost) by www1.ietf.org (8.11.6/8.11.6) id h4KNCXj14813 for routing-discussion-archive@odin.ietf.org; Tue, 20 May 2003 19:12:33 -0400 Received: from www1.ietf.org (localhost.localdomain [127.0.0.1]) by www1.ietf.org (8.11.6/8.11.6) with ESMTP id h4KN6DB13673; Tue, 20 May 2003 19:06:13 -0400 Received: from ietf.org (odin.ietf.org [132.151.1.176]) by www1.ietf.org (8.11.6/8.11.6) with ESMTP id h4KN5gB13602 for ; Tue, 20 May 2003 19:05:42 -0400 Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id TAA05941 for ; Tue, 20 May 2003 19:38:39 -0400 (EDT) Received: from ietf-mx ([132.151.6.1]) by ietf-mx with esmtp (Exim 4.12) id 19IGfY-0001pr-00 for routing-discussion@ietf.org; Tue, 20 May 2003 19:37:20 -0400 Received: from [64.115.125.242] (helo=bridge.axiowave.com) by ietf-mx with esmtp (Exim 4.12) id 19IGfX-0001pE-00 for routing-discussion@ietf.org; Tue, 20 May 2003 19:37:19 -0400 Message-ID: From: Jeff Parker To: "'rt13@uow.edu.au'" , routing-discussion@ietf.org Cc: sudip_misra2003@yahoo.ca Subject: RE: CODE:BELLMAN FORD MIME-Version: 1.0 Content-Type: text/plain; charset="iso-8859-1" Sender: routing-discussion-admin@ietf.org Errors-To: routing-discussion-admin@ietf.org X-BeenThere: routing-discussion@ietf.org X-Mailman-Version: 2.0.12 Precedence: bulk List-Unsubscribe: , List-Id: Routing Area General mailing list List-Post: List-Help: List-Subscribe: , List-Archive: Date: Tue, 20 May 2003 19:37:55 -0400 I think we could eliminate a hop if we just sent the solution directly to the professor running the course. If you give us his (her) e-mail, I'd be happy to communicate directly with him (her). - jeff parker > Hi, > > I need a code for Bellman Ford algorithm.It could be in any > language. > My question is: _______________________________________________ routing-discussion mailing list routing-discussion@ietf.org https://www1.ietf.org/mailman/listinfo/routing-discussion From mailnull@www1.ietf.org Tue May 20 19:46:56 2003 Received: from www1.ietf.org (ietf.org [132.151.1.19] (may be forged)) by ietf.org (8.9.1a/8.9.1a) with ESMTP id TAA06201 for ; Tue, 20 May 2003 19:46:56 -0400 (EDT) Received: (from mailnull@localhost) by www1.ietf.org (8.11.6/8.11.6) id h4KNDTr14851 for routing-discussion-archive@odin.ietf.org; Tue, 20 May 2003 19:13:29 -0400 Received: from www1.ietf.org (localhost.localdomain [127.0.0.1]) by www1.ietf.org (8.11.6/8.11.6) with ESMTP id h4KN69B13654; Tue, 20 May 2003 19:06:09 -0400 Received: from ietf.org (odin.ietf.org [132.151.1.176]) by www1.ietf.org (8.11.6/8.11.6) with ESMTP id h4KN4AB13494 for ; Tue, 20 May 2003 19:04:10 -0400 Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id TAA05901 for ; Tue, 20 May 2003 19:37:06 -0400 (EDT) Received: from ietf-mx ([132.151.6.1]) by ietf-mx with esmtp (Exim 4.12) id 19IGe3-0001p0-00 for routing-discussion@ietf.org; Tue, 20 May 2003 19:35:47 -0400 Received: from dmz1.procket.com ([65.174.124.36]) by ietf-mx with esmtp (Exim 4.12) id 19IGe3-0001ox-00 for routing-discussion@ietf.org; Tue, 20 May 2003 19:35:47 -0400 Received: from miata.procket.com (zeus-d-1.procket.com [65.174.124.60]) by dmz1.procket.com (Postfix) with ESMTP id B17CE23C3D; Tue, 20 May 2003 16:24:49 -0700 (PDT) Received: from EXCHANGE0-0.na.procket.com (exchange0a.na.procket.com [10.1.7.7]) by miata.procket.com (8.12.1/8.12.1) with ESMTP id h4KNabYB007059; Tue, 20 May 2003 16:36:37 -0700 (PDT) X-MimeOLE: Produced By Microsoft Exchange V6.0.6249.0 content-class: urn:content-classes:message MIME-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Subject: RE: CODE:BELLMAN FORD Message-ID: Thread-Topic: CODE:BELLMAN FORD Thread-Index: AcMfKC/8fna0y+m7RPellOIh7Da5CAAAGfzg From: "Tony Li" To: , Cc: Content-Transfer-Encoding: 8bit X-MIME-Autoconverted: from quoted-printable to 8bit by www1.ietf.org id h4KN4AB13495 Sender: routing-discussion-admin@ietf.org Errors-To: routing-discussion-admin@ietf.org X-BeenThere: routing-discussion@ietf.org X-Mailman-Version: 2.0.12 Precedence: bulk List-Unsubscribe: , List-Id: Routing Area General mailing list List-Post: List-Help: List-Subscribe: , List-Archive: Date: Tue, 20 May 2003 16:36:36 -0700 Content-Transfer-Encoding: 8bit Homework is only educational if you do it. Tony | -----Original Message----- | From: rt13@uow.edu.au [mailto:rt13@uow.edu.au] | Sent: Friday, May 16, 2003 1:37 AM | To: routing-discussion@ietf.org | Cc: sudip_misra2003@yahoo.ca | Subject: CODE:BELLMAN FORD | | | Hi, | | I need a code for Bellman Ford algorithm.It could be in any | language. | My question is: | Write a program which generates a network with controllable | number of nodes N.The easiest way 2 do this is to start with | a rectangle with sides X and Y.Use a pair of random numbers rx | (n) and ry(n) to set coordianates of point, n at X rx(n) and | Y ry(n).Allow n to cover the range 1 to N.ur program must | decide whether a link exists between every pair of nodes.This | can be done based on distance between them. It could be | decided that a link exists if the distance between 2 nodes is | less than a certain distance. | Extend the program so that it simulates operation of BGP for | 1 node at a time.Start the program with a fixed set of link | costs perhaps unity.Set N=10.Now change value of 1 link only | and allow program 2 run until all routing tables r | stable.Measure time taken 2 reach stability.Repeat this test | 100 times & find average time 2 reach stability.Repeat this | with N=32,100,316,1000.Present results graphically showing | settling time vs number of nodes. | I request you 2 send me this solution by 20 May to | rt13@uow.edu.au | Thanks a lot.I would appreciate ur favour very much. | Robin. | | _______________________________________________ | routing-discussion mailing list | routing-discussion@ietf.org | https://www1.ietf.org/mailman/listinfo/routing-discussion | _______________________________________________ routing-discussion mailing list routing-discussion@ietf.org https://www1.ietf.org/mailman/listinfo/routing-discussion From mailnull@www1.ietf.org Tue May 20 19:53:09 2003 Received: from www1.ietf.org (ietf.org [132.151.1.19] (may be forged)) by ietf.org (8.9.1a/8.9.1a) with ESMTP id TAA06376 for ; Tue, 20 May 2003 19:53:09 -0400 (EDT) Received: (from mailnull@localhost) by www1.ietf.org (8.11.6/8.11.6) id h4KNJgp15195 for routing-discussion-archive@odin.ietf.org; Tue, 20 May 2003 19:19:42 -0400 Received: from www1.ietf.org (localhost.localdomain [127.0.0.1]) by www1.ietf.org (8.11.6/8.11.6) with ESMTP id h4KNEFB14919; Tue, 20 May 2003 19:14:15 -0400 Received: from ietf.org (odin.ietf.org [132.151.1.176]) by www1.ietf.org (8.11.6/8.11.6) with ESMTP id h4KNDwB14868 for ; Tue, 20 May 2003 19:13:58 -0400 Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id TAA06199 for ; Tue, 20 May 2003 19:46:55 -0400 (EDT) Received: from ietf-mx ([132.151.6.1]) by ietf-mx with esmtp (Exim 4.12) id 19IGnY-0001te-00 for routing-discussion@ietf.org; Tue, 20 May 2003 19:45:36 -0400 Received: from letters.cs.ucsb.edu ([128.111.41.13]) by ietf-mx with esmtp (Exim 4.12) id 19IGnX-0001tb-00 for routing-discussion@ietf.org; Tue, 20 May 2003 19:45:35 -0400 Received: from calvin.cs.ucsb.edu (calvin [128.111.43.21]) by letters.cs.ucsb.edu (8.11.6+Sun/8.11.6) with ESMTP id h4KNkmC29239; Tue, 20 May 2003 16:46:48 -0700 (PDT) Received: from localhost (zaera@localhost) by calvin.cs.ucsb.edu (8.11.6/8.11.6) with ESMTP id h4KNkvC24531; Tue, 20 May 2003 16:46:57 -0700 X-Authentication-Warning: calvin.cs.ucsb.edu: zaera owned process doing -bs From: guStaVo ZaeRa To: Tony Li cc: rt13@uow.edu.au, , Subject: RE: CODE:BELLMAN FORD In-Reply-To: Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: routing-discussion-admin@ietf.org Errors-To: routing-discussion-admin@ietf.org X-BeenThere: routing-discussion@ietf.org X-Mailman-Version: 2.0.12 Precedence: bulk List-Unsubscribe: , List-Id: Routing Area General mailing list List-Post: List-Help: List-Subscribe: , List-Archive: Date: Tue, 20 May 2003 16:46:57 -0700 (PDT) i love this, and i definitely agree. figure it out on your own, that's how you learn.. gustavo On Tue, 20 May 2003, Tony Li wrote: | | | Homework is only educational if you do it. | | Tony | | | | -----Original Message----- | | From: rt13@uow.edu.au [mailto:rt13@uow.edu.au] | | Sent: Friday, May 16, 2003 1:37 AM | | To: routing-discussion@ietf.org | | Cc: sudip_misra2003@yahoo.ca | | Subject: CODE:BELLMAN FORD | | | | | | Hi, | | | | I need a code for Bellman Ford algorithm.It could be in any | | language. | | My question is: | | Write a program which generates a network with controllable | | number of nodes N.The easiest way 2 do this is to start with | | a rectangle with sides X and Y.Use a pair of random numbers rx | | (n) and ry(n) to set coordianates of point, n at X rx(n) and | | Y ry(n).Allow n to cover the range 1 to N.ur program must | | decide whether a link exists between every pair of nodes.This | | can be done based on distance between them. It could be | | decided that a link exists if the distance between 2 nodes is | | less than a certain distance. | | Extend the program so that it simulates operation of BGP for | | 1 node at a time.Start the program with a fixed set of link | | costs perhaps unity.Set N=10.Now change value of 1 link only | | and allow program 2 run until all routing tables r | | stable.Measure time taken 2 reach stability.Repeat this test | | 100 times & find average time 2 reach stability.Repeat this | | with N=32,100,316,1000.Present results graphically showing | | settling time vs number of nodes. | | I request you 2 send me this solution by 20 May to | | rt13@uow.edu.au | | Thanks a lot.I would appreciate ur favour very much. | | Robin. | | | | _______________________________________________ | | routing-discussion mailing list | | routing-discussion@ietf.org | | https://www1.ietf.org/mailman/listinfo/routing-discussion | | | _______________________________________________ | routing-discussion mailing list | routing-discussion@ietf.org | https://www1.ietf.org/mailman/listinfo/routing-discussion | -- . g u s t a v o z a e r a . "My goal is to make any information available from anywhere, at anytime." _______________________________________________ routing-discussion mailing list routing-discussion@ietf.org https://www1.ietf.org/mailman/listinfo/routing-discussion From mailnull@www1.ietf.org Tue May 20 20:20:28 2003 Received: from www1.ietf.org (ietf.org [132.151.1.19] (may be forged)) by ietf.org (8.9.1a/8.9.1a) with ESMTP id UAA06917 for ; Tue, 20 May 2003 20:20:28 -0400 (EDT) Received: (from mailnull@localhost) by www1.ietf.org (8.11.6/8.11.6) id h4KNl1T17131 for routing-discussion-archive@odin.ietf.org; Tue, 20 May 2003 19:47:01 -0400 Received: from www1.ietf.org (localhost.localdomain [127.0.0.1]) by www1.ietf.org (8.11.6/8.11.6) with ESMTP id h4KNdXB16868; Tue, 20 May 2003 19:39:33 -0400 Received: from ietf.org (odin.ietf.org [132.151.1.176]) by www1.ietf.org (8.11.6/8.11.6) with ESMTP id h4KNVQB15686 for ; Tue, 20 May 2003 19:31:26 -0400 Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id UAA06594 for ; Tue, 20 May 2003 20:04:22 -0400 (EDT) Received: from ietf-mx ([132.151.6.1]) by ietf-mx with esmtp (Exim 4.12) id 19IH4R-0001zm-00 for routing-discussion@ietf.org; Tue, 20 May 2003 20:03:03 -0400 Received: from web80506.mail.yahoo.com ([66.218.79.76]) by ietf-mx with smtp (Exim 4.12) id 19IH4Q-0001zd-00 for routing-discussion@ietf.org; Tue, 20 May 2003 20:03:02 -0400 Message-ID: <20030521000351.66310.qmail@web80506.mail.yahoo.com> Received: from [64.221.212.131] by web80506.mail.yahoo.com via HTTP; Tue, 20 May 2003 17:03:50 PDT From: Mark Griswold Subject: RE: CODE:IP ROUTING STACK To: routing-discussion@ietf.org Cc: sudip_misra2003@yahoo.ca MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Sender: routing-discussion-admin@ietf.org Errors-To: routing-discussion-admin@ietf.org X-BeenThere: routing-discussion@ietf.org X-Mailman-Version: 2.0.12 Precedence: bulk List-Unsubscribe: , List-Id: Routing Area General mailing list List-Post: List-Help: List-Subscribe: , List-Archive: Date: Tue, 20 May 2003 17:03:50 -0700 (PDT) I need complete production-worthy code for the full IP routing stack (OSPF, ISIS, BGP inc. extensions/bugs, RIP, all multicast protocols, GRE, IP-in-IP, etc). It would be so awesome if you could send this to me at foo@bigbiz.com by May 20th. ;-) Thanks, Chip __________________________________ Do you Yahoo!? The New Yahoo! Search - Faster. Easier. Bingo. http://search.yahoo.com _______________________________________________ routing-discussion mailing list routing-discussion@ietf.org https://www1.ietf.org/mailman/listinfo/routing-discussion From mailnull@www1.ietf.org Fri May 23 14:04:18 2003 Received: from www1.ietf.org (ietf.org [132.151.1.19] (may be forged)) by ietf.org (8.9.1a/8.9.1a) with ESMTP id OAA17849 for ; Fri, 23 May 2003 14:04:18 -0400 (EDT) Received: (from mailnull@localhost) by www1.ietf.org (8.11.6/8.11.6) id h4NI3np15764 for routing-discussion-archive@odin.ietf.org; Fri, 23 May 2003 14:03:49 -0400 Received: from www1.ietf.org (localhost.localdomain [127.0.0.1]) by www1.ietf.org (8.11.6/8.11.6) with ESMTP id h4NHnSB12264; Fri, 23 May 2003 13:49:28 -0400 Received: from ietf.org (odin.ietf.org [132.151.1.176]) by www1.ietf.org (8.11.6/8.11.6) with ESMTP id h4NBcOB08054 for ; Fri, 23 May 2003 07:38:24 -0400 Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id IAA03156 for ; Fri, 23 May 2003 08:10:11 -0400 (EDT) Received: from ietf-mx ([132.151.6.1]) by ietf-mx with esmtp (Exim 4.12) id 19JBLq-0004Xw-00 for routing-discussion@ietf.org; Fri, 23 May 2003 08:08:46 -0400 Received: from motgate5.mot.com ([144.189.100.105]) by ietf-mx with esmtp (Exim 4.12) id 19JBLp-0004Xs-00 for routing-discussion@ietf.org; Fri, 23 May 2003 08:08:45 -0400 Received: from il06exr06.mot.com (il06exr06.mot.com [129.188.137.136]) by motgate5.mot.com (Motorola/Motgate5) with ESMTP id h4NC9tfj011185; Fri, 23 May 2003 05:09:55 -0700 (MST) Received: from thorgal.crm.mot.com (thorgal.crm.mot.com [140.101.173.1]) by il06exr06.mot.com (Motorola/il06exr06) with ESMTP id h4NC9onb005099; Fri, 23 May 2003 07:09:52 -0500 Received: from nal.motlabs.com (test9.crm.mot.com [140.101.173.239]) by thorgal.crm.mot.com (Postfix) with ESMTP id D68982EC86; Fri, 23 May 2003 14:09:49 +0200 (CEST) Message-ID: <3ECE0F88.2080902@nal.motlabs.com> From: Alexandru Petrescu User-Agent: Mozilla/5.0 (Windows; U; Windows NT 5.0; en-US; rv:1.4b) Gecko/20030507 X-Accept-Language: en-us, en MIME-Version: 1.0 To: curtis@fictitious.org Cc: Sudip Misra , routing-discussion@ietf.org Subject: Re: Bellman-Ford's Shortest Path algorithm References: <200305090342.XAA36419@workhorse.fictitious.org> In-Reply-To: <200305090342.XAA36419@workhorse.fictitious.org> X-Enigmail-Version: 0.75.0.0 X-Enigmail-Supports: pgp-inline, pgp-mime Content-Type: text/plain; charset=us-ascii; format=flowed Content-Transfer-Encoding: 7bit Content-Transfer-Encoding: 7bit Sender: routing-discussion-admin@ietf.org Errors-To: routing-discussion-admin@ietf.org X-BeenThere: routing-discussion@ietf.org X-Mailman-Version: 2.0.12 Precedence: bulk List-Unsubscribe: , List-Id: Routing Area General mailing list List-Post: List-Help: List-Subscribe: , List-Archive: Date: Fri, 23 May 2003 14:09:44 +0200 Content-Transfer-Encoding: 7bit Curtis Villamizar wrote: > questions like "what's Dykstra" What's Dykstra? Is it something like Dijkstra? What does Dijk stand for? Is it because there are many dikes in Holland? Alex GBU _______________________________________________ routing-discussion mailing list routing-discussion@ietf.org https://www1.ietf.org/mailman/listinfo/routing-discussion From mailnull@www1.ietf.org Fri May 23 14:06:42 2003 Received: from www1.ietf.org (ietf.org [132.151.1.19] (may be forged)) by ietf.org (8.9.1a/8.9.1a) with ESMTP id OAA17990 for ; Fri, 23 May 2003 14:06:42 -0400 (EDT) Received: (from mailnull@localhost) by www1.ietf.org (8.11.6/8.11.6) id h4NI6DG16083 for routing-discussion-archive@odin.ietf.org; Fri, 23 May 2003 14:06:13 -0400 Received: from www1.ietf.org (localhost.localdomain [127.0.0.1]) by www1.ietf.org (8.11.6/8.11.6) with ESMTP id h4NHqiB12782; Fri, 23 May 2003 13:52:44 -0400 Received: from ietf.org (odin.ietf.org [132.151.1.176]) by www1.ietf.org (8.11.6/8.11.6) with ESMTP id h4NCZJB11140 for ; Fri, 23 May 2003 08:35:19 -0400 Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id JAA04005 for ; Fri, 23 May 2003 09:07:04 -0400 (EDT) Received: from ietf-mx ([132.151.6.1]) by ietf-mx with esmtp (Exim 4.12) id 19JCEt-0004lv-00 for routing-discussion@ietf.org; Fri, 23 May 2003 09:05:39 -0400 Received: from workhorse.fictitious.org ([209.150.1.230]) by ietf-mx with esmtp (Exim 4.12) id 19JCEr-0004lr-00 for routing-discussion@ietf.org; Fri, 23 May 2003 09:05:38 -0400 Received: from workhorse.fictitious.org (localhost.fictitious.org [127.0.0.1]) by workhorse.fictitious.org (8.9.3/8.9.3) with ESMTP id JAA11816; Fri, 23 May 2003 09:07:20 -0400 (EDT) (envelope-from curtis@workhorse.fictitious.org) Message-Id: <200305231307.JAA11816@workhorse.fictitious.org> To: Alexandru Petrescu cc: curtis@fictitious.org, Sudip Misra , routing-discussion@ietf.org Reply-To: curtis@fictitious.org Subject: Re: Bellman-Ford's Shortest Path algorithm In-reply-to: Your message of "Fri, 23 May 2003 14:09:44 +0200." <3ECE0F88.2080902@nal.motlabs.com> From: Curtis Villamizar Sender: routing-discussion-admin@ietf.org Errors-To: routing-discussion-admin@ietf.org X-BeenThere: routing-discussion@ietf.org X-Mailman-Version: 2.0.12 Precedence: bulk List-Unsubscribe: , List-Id: Routing Area General mailing list List-Post: List-Help: List-Subscribe: , List-Archive: Date: Fri, 23 May 2003 09:07:20 -0400 In message <3ECE0F88.2080902@nal.motlabs.com>, Alexandru Petrescu writes: > Curtis Villamizar wrote: > > questions like "what's Dykstra" > > What's Dykstra? Is it something like Dijkstra? What does Dijk stand > for? Is it because there are many dikes in Holland? > > Alex > GBU Thanks for the spelling correction. Curtis _______________________________________________ routing-discussion mailing list routing-discussion@ietf.org https://www1.ietf.org/mailman/listinfo/routing-discussion From routing-discussion-admin@ietf.org Thu May 29 03:07:43 2003 Received: from www1.ietf.org (ietf.org [132.151.1.19] (may be forged)) by ietf.org (8.9.1a/8.9.1a) with ESMTP id DAA21027 for ; Thu, 29 May 2003 03:07:43 -0400 (EDT) Received: from www1.ietf.org (localhost.localdomain [127.0.0.1]) by www1.ietf.org (8.11.6/8.11.6) with ESMTP id h4T6xWB27890; Thu, 29 May 2003 02:59:33 -0400 Received: from ietf.org (odin.ietf.org [132.151.1.176]) by www1.ietf.org (8.11.6/8.11.6) with ESMTP id h4T6uXB27795 for ; Thu, 29 May 2003 02:56:33 -0400 Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id CAA20886 for ; Thu, 29 May 2003 02:56:28 -0400 (EDT) Received: from ietf-mx ([132.151.6.1]) by ietf-mx with esmtp (Exim 4.12) id 19LHJK-0003uz-00 for routing-discussion@ietf.org; Thu, 29 May 2003 02:54:50 -0400 Received: from [203.199.83.148] (helo=rediffmail.com) by ietf-mx with smtp (Exim 4.12) id 19LHJJ-0003uq-00 for routing-discussion@ietf.org; Thu, 29 May 2003 02:54:49 -0400 Received: (qmail 32043 invoked by uid 510); 29 May 2003 06:54:08 -0000 Message-ID: <20030529065408.32042.qmail@webmail26.rediffmail.com> Received: from unknown (203.200.20.226) by rediffmail.com via HTTP; 29 may 2003 06:54:08 -0000 MIME-Version: 1.0 From: "Karthikeyan Subramaniam" Reply-To: "Karthikeyan Subramaniam" To: routing-discussion@ietf.org Subject: Software upgradation time Content-type: text/plain; format=flowed Content-Disposition: inline Sender: routing-discussion-admin@ietf.org Errors-To: routing-discussion-admin@ietf.org X-BeenThere: routing-discussion@ietf.org X-Mailman-Version: 2.0.12 Precedence: bulk List-Unsubscribe: , List-Id: Routing Area General mailing list List-Post: List-Help: List-Subscribe: , List-Archive: Date: 29 May 2003 06:54:08 -0000 Hi, I have doubt about restart timer value in protocols. In OSPF default restart timer is specified as 120 seconds in the draft "draft-ietf-ospf-hitless-restart-07.txt" and in the case of BGP default restart timer should not be greater than the HOLDTIME(suggested value as per RFC 1771 is 90 secs)carried in OPEN. Can control software be upgraded within 120/90 seconds? On what basis this timer value has been fixed? with regards, S.Karthikeyan. ___________________________________________________ Get www. mycompany .com and 5 matching email ids. Just Rs. 1499/ year. Click here http://www.rediffmailpro.com _______________________________________________ routing-discussion mailing list routing-discussion@ietf.org https://www1.ietf.org/mailman/listinfo/routing-discussion From mailnull@www1.ietf.org Thu May 29 03:08:31 2003 Received: from www1.ietf.org (ietf.org [132.151.1.19] (may be forged)) by ietf.org (8.9.1a/8.9.1a) with ESMTP id DAA21047 for ; Thu, 29 May 2003 03:08:31 -0400 (EDT) Received: (from mailnull@localhost) by www1.ietf.org (8.11.6/8.11.6) id h4T786G29034 for routing-discussion-archive@odin.ietf.org; Thu, 29 May 2003 03:08:06 -0400 Received: from www1.ietf.org (localhost.localdomain [127.0.0.1]) by www1.ietf.org (8.11.6/8.11.6) with ESMTP id h4T6xWB27890; Thu, 29 May 2003 02:59:33 -0400 Received: from ietf.org (odin.ietf.org [132.151.1.176]) by www1.ietf.org (8.11.6/8.11.6) with ESMTP id h4T6uXB27795 for ; Thu, 29 May 2003 02:56:33 -0400 Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id CAA20886 for ; Thu, 29 May 2003 02:56:28 -0400 (EDT) Received: from ietf-mx ([132.151.6.1]) by ietf-mx with esmtp (Exim 4.12) id 19LHJK-0003uz-00 for routing-discussion@ietf.org; Thu, 29 May 2003 02:54:50 -0400 Received: from [203.199.83.148] (helo=rediffmail.com) by ietf-mx with smtp (Exim 4.12) id 19LHJJ-0003uq-00 for routing-discussion@ietf.org; Thu, 29 May 2003 02:54:49 -0400 Received: (qmail 32043 invoked by uid 510); 29 May 2003 06:54:08 -0000 Message-ID: <20030529065408.32042.qmail@webmail26.rediffmail.com> Received: from unknown (203.200.20.226) by rediffmail.com via HTTP; 29 may 2003 06:54:08 -0000 MIME-Version: 1.0 From: "Karthikeyan Subramaniam" Reply-To: "Karthikeyan Subramaniam" To: routing-discussion@ietf.org Subject: Software upgradation time Content-type: text/plain; format=flowed Content-Disposition: inline Sender: routing-discussion-admin@ietf.org Errors-To: routing-discussion-admin@ietf.org X-BeenThere: routing-discussion@ietf.org X-Mailman-Version: 2.0.12 Precedence: bulk List-Unsubscribe: , List-Id: Routing Area General mailing list List-Post: List-Help: List-Subscribe: , List-Archive: Date: 29 May 2003 06:54:08 -0000 Hi, I have doubt about restart timer value in protocols. In OSPF default restart timer is specified as 120 seconds in the draft "draft-ietf-ospf-hitless-restart-07.txt" and in the case of BGP default restart timer should not be greater than the HOLDTIME(suggested value as per RFC 1771 is 90 secs)carried in OPEN. Can control software be upgraded within 120/90 seconds? On what basis this timer value has been fixed? with regards, S.Karthikeyan. ___________________________________________________ Get www. mycompany .com and 5 matching email ids. Just Rs. 1499/ year. Click here http://www.rediffmailpro.com _______________________________________________ routing-discussion mailing list routing-discussion@ietf.org https://www1.ietf.org/mailman/listinfo/routing-discussion From routing-discussion-admin@ietf.org Thu May 29 04:55:14 2003 Received: from www1.ietf.org (ietf.org [132.151.1.19] (may be forged)) by ietf.org (8.9.1a/8.9.1a) with ESMTP id EAA23568 for ; Thu, 29 May 2003 04:55:14 -0400 (EDT) Received: from www1.ietf.org (localhost.localdomain [127.0.0.1]) by www1.ietf.org (8.11.6/8.11.6) with ESMTP id h4T8lUB02513; Thu, 29 May 2003 04:47:30 -0400 Received: from ietf.org (odin.ietf.org [132.151.1.176]) by www1.ietf.org (8.11.6/8.11.6) with ESMTP id h4T8jlB02463 for ; Thu, 29 May 2003 04:45:47 -0400 Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id EAA23180 for ; Thu, 29 May 2003 04:45:44 -0400 (EDT) Received: from ietf-mx ([132.151.6.1]) by ietf-mx with esmtp (Exim 4.12) id 19LJ15-0004Yi-00 for routing-discussion@ietf.org; Thu, 29 May 2003 04:44:07 -0400 Received: from web42006.mail.yahoo.com ([66.218.93.174]) by ietf-mx with smtp (Exim 4.12) id 19LJ14-0004Ye-00 for routing-discussion@ietf.org; Thu, 29 May 2003 04:44:06 -0400 Message-ID: <20030529084514.1308.qmail@web42006.mail.yahoo.com> Received: from [203.124.140.97] by web42006.mail.yahoo.com via HTTP; Thu, 29 May 2003 09:45:14 BST From: =?iso-8859-1?q?Spice=20Sylvia?= Subject: newbie question on BGP To: routing-discussion@ietf.org MIME-Version: 1.0 Content-Type: multipart/alternative; boundary="0-645734468-1054197914=:98568" Content-Transfer-Encoding: 8bit Sender: routing-discussion-admin@ietf.org Errors-To: routing-discussion-admin@ietf.org X-BeenThere: routing-discussion@ietf.org X-Mailman-Version: 2.0.12 Precedence: bulk List-Unsubscribe: , List-Id: Routing Area General mailing list List-Post: List-Help: List-Subscribe: , List-Archive: Date: Thu, 29 May 2003 09:45:14 +0100 (BST) --0-645734468-1054197914=:98568 Content-Type: text/plain; charset=iso-8859-1 Content-Transfer-Encoding: 8bit Hello, I wanted to get this clarified from some of the people who were involved when BGP deployment was happening. Can you please clarify as to what BGP was made to do? Was it never meant to be run on all routers in an AS? It does behave a lot like RIP except that there might now be a bandwidth as a metric, but as someone told me, it would still learn "by rumor" except in full mesh scenarios. Is learning "by rumor" a topological issue? Is it a problem if a routing protocol learns by rumor if the updates and the source of the update are immediately propogated? -S.F. --------------------------------- Yahoo! Plus - For a better Internet experience --0-645734468-1054197914=:98568 Content-Type: text/html; charset=iso-8859-1 Content-Transfer-Encoding: 8bit
Hello,
 
I wanted to get this clarified from some of the people who were involved when BGP deployment was happening.
 
Can you please clarify as to what BGP was made to do? Was it never meant to be run on all routers in an AS?
 
It does behave a lot like RIP except that there might now be a bandwidth as a metric, but as someone told me, it would still learn "by rumor" except in full mesh scenarios.
 
Is learning "by rumor" a topological issue? Is it a problem if a routing protocol learns by rumor if the updates and the source of the update are immediately propogated?
 
-S.F.
 


Yahoo! Plus - For a better Internet experience
--0-645734468-1054197914=:98568-- _______________________________________________ routing-discussion mailing list routing-discussion@ietf.org https://www1.ietf.org/mailman/listinfo/routing-discussion From mailnull@www1.ietf.org Thu May 29 04:56:01 2003 Received: from www1.ietf.org (ietf.org [132.151.1.19] (may be forged)) by ietf.org (8.9.1a/8.9.1a) with ESMTP id EAA23587 for ; Thu, 29 May 2003 04:56:01 -0400 (EDT) Received: (from mailnull@localhost) by www1.ietf.org (8.11.6/8.11.6) id h4T8tYD02713 for routing-discussion-archive@odin.ietf.org; Thu, 29 May 2003 04:55:34 -0400 Received: from www1.ietf.org (localhost.localdomain [127.0.0.1]) by www1.ietf.org (8.11.6/8.11.6) with ESMTP id h4T8lUB02513; Thu, 29 May 2003 04:47:30 -0400 Received: from ietf.org (odin.ietf.org [132.151.1.176]) by www1.ietf.org (8.11.6/8.11.6) with ESMTP id h4T8jlB02463 for ; Thu, 29 May 2003 04:45:47 -0400 Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id EAA23180 for ; Thu, 29 May 2003 04:45:44 -0400 (EDT) Received: from ietf-mx ([132.151.6.1]) by ietf-mx with esmtp (Exim 4.12) id 19LJ15-0004Yi-00 for routing-discussion@ietf.org; Thu, 29 May 2003 04:44:07 -0400 Received: from web42006.mail.yahoo.com ([66.218.93.174]) by ietf-mx with smtp (Exim 4.12) id 19LJ14-0004Ye-00 for routing-discussion@ietf.org; Thu, 29 May 2003 04:44:06 -0400 Message-ID: <20030529084514.1308.qmail@web42006.mail.yahoo.com> Received: from [203.124.140.97] by web42006.mail.yahoo.com via HTTP; Thu, 29 May 2003 09:45:14 BST From: =?iso-8859-1?q?Spice=20Sylvia?= Subject: newbie question on BGP To: routing-discussion@ietf.org MIME-Version: 1.0 Content-Type: multipart/alternative; boundary="0-645734468-1054197914=:98568" Content-Transfer-Encoding: 8bit Sender: routing-discussion-admin@ietf.org Errors-To: routing-discussion-admin@ietf.org X-BeenThere: routing-discussion@ietf.org X-Mailman-Version: 2.0.12 Precedence: bulk List-Unsubscribe: , List-Id: Routing Area General mailing list List-Post: List-Help: List-Subscribe: , List-Archive: Date: Thu, 29 May 2003 09:45:14 +0100 (BST) --0-645734468-1054197914=:98568 Content-Type: text/plain; charset=iso-8859-1 Content-Transfer-Encoding: 8bit Hello, I wanted to get this clarified from some of the people who were involved when BGP deployment was happening. Can you please clarify as to what BGP was made to do? Was it never meant to be run on all routers in an AS? It does behave a lot like RIP except that there might now be a bandwidth as a metric, but as someone told me, it would still learn "by rumor" except in full mesh scenarios. Is learning "by rumor" a topological issue? Is it a problem if a routing protocol learns by rumor if the updates and the source of the update are immediately propogated? -S.F. --------------------------------- Yahoo! Plus - For a better Internet experience --0-645734468-1054197914=:98568 Content-Type: text/html; charset=iso-8859-1 Content-Transfer-Encoding: 8bit
Hello,
 
I wanted to get this clarified from some of the people who were involved when BGP deployment was happening.
 
Can you please clarify as to what BGP was made to do? Was it never meant to be run on all routers in an AS?
 
It does behave a lot like RIP except that there might now be a bandwidth as a metric, but as someone told me, it would still learn "by rumor" except in full mesh scenarios.
 
Is learning "by rumor" a topological issue? Is it a problem if a routing protocol learns by rumor if the updates and the source of the update are immediately propogated?
 
-S.F.
 


Yahoo! Plus - For a better Internet experience
--0-645734468-1054197914=:98568-- _______________________________________________ routing-discussion mailing list routing-discussion@ietf.org https://www1.ietf.org/mailman/listinfo/routing-discussion From routing-discussion-admin@ietf.org Thu May 29 06:36:37 2003 Received: from www1.ietf.org (ietf.org [132.151.1.19] (may be forged)) by ietf.org (8.9.1a/8.9.1a) with ESMTP id GAA25360 for ; Thu, 29 May 2003 06:36:37 -0400 (EDT) Received: from www1.ietf.org (localhost.localdomain [127.0.0.1]) by www1.ietf.org (8.11.6/8.11.6) with ESMTP id h4TATUB08257; Thu, 29 May 2003 06:29:30 -0400 Received: from ietf.org (odin.ietf.org [132.151.1.176]) by www1.ietf.org (8.11.6/8.11.6) with ESMTP id h4TARkB08223 for ; Thu, 29 May 2003 06:27:46 -0400 Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id GAA25164 for ; Thu, 29 May 2003 06:27:39 -0400 (EDT) Received: from ietf-mx ([132.151.6.1]) by ietf-mx with esmtp (Exim 4.12) id 19LKbj-000556-00 for routing-discussion@ietf.org; Thu, 29 May 2003 06:26:03 -0400 Received: from ms-smtp-02.southeast.rr.com ([24.93.67.83]) by ietf-mx with esmtp (Exim 4.12) id 19LKbi-000553-00 for routing-discussion@ietf.org; Thu, 29 May 2003 06:26:02 -0400 Received: from redback.com (rdu162-241-056.nc.rr.com [24.162.241.56]) by ms-smtp-02.southeast.rr.com (8.12.5/8.12.2) with ESMTP id h4TAP8Zh008269; Thu, 29 May 2003 06:25:08 -0400 (EDT) Message-ID: <3ED5E028.2040302@redback.com> From: Acee Lindem User-Agent: Mozilla/5.0 (X11; U; Linux i686; en-US; rv:1.0.2) Gecko/20030208 Netscape/7.02 X-Accept-Language: en-us, en MIME-Version: 1.0 To: Karthikeyan Subramaniam CC: routing-discussion@ietf.org Subject: Re: Software upgradation time References: <20030529065408.32042.qmail@webmail26.rediffmail.com> Content-Type: text/plain; charset=us-ascii; format=flowed Content-Transfer-Encoding: 7bit Content-Transfer-Encoding: 7bit Sender: routing-discussion-admin@ietf.org Errors-To: routing-discussion-admin@ietf.org X-BeenThere: routing-discussion@ietf.org X-Mailman-Version: 2.0.12 Precedence: bulk List-Unsubscribe: , List-Id: Routing Area General mailing list List-Post: List-Help: List-Subscribe: , List-Archive: Date: Thu, 29 May 2003 06:25:44 -0400 Content-Transfer-Encoding: 7bit Karthikeyan Subramaniam wrote: > Hi, > > I have doubt about restart timer value in protocols. > > In OSPF default restart timer is specified as 120 seconds in the draft > "draft-ietf-ospf-hitless-restart-07.txt" and in the case of BGP default > restart timer should not be greater than the HOLDTIME(suggested value as > per RFC 1771 is 90 secs)carried in OPEN. > > Can control software be upgraded within 120/90 seconds? I guess that depends on your implementation and the type of upgrade. If your software is modular it is certainly enough time for an incremental upgrade or a switchover to a redundant control processor. > On what basis > this timer value has been fixed? This was thought to be an upper bound on restart time, redistribution, and synchronization with other protocols. The restart should complete much sooner. Note the timer value is configurable. > > with regards, > S.Karthikeyan. > > > > ___________________________________________________ > Get www. mycompany .com and 5 matching email ids. > Just Rs. 1499/ year. > Click here http://www.rediffmailpro.com > > _______________________________________________ > routing-discussion mailing list > routing-discussion@ietf.org > https://www1.ietf.org/mailman/listinfo/routing-discussion > -- Acee _______________________________________________ routing-discussion mailing list routing-discussion@ietf.org https://www1.ietf.org/mailman/listinfo/routing-discussion From mailnull@www1.ietf.org Thu May 29 06:37:21 2003 Received: from www1.ietf.org (ietf.org [132.151.1.19] (may be forged)) by ietf.org (8.9.1a/8.9.1a) with ESMTP id GAA25400 for ; Thu, 29 May 2003 06:37:21 -0400 (EDT) Received: (from mailnull@localhost) by www1.ietf.org (8.11.6/8.11.6) id h4TAavT08571 for routing-discussion-archive@odin.ietf.org; Thu, 29 May 2003 06:36:57 -0400 Received: from www1.ietf.org (localhost.localdomain [127.0.0.1]) by www1.ietf.org (8.11.6/8.11.6) with ESMTP id h4TATUB08257; Thu, 29 May 2003 06:29:30 -0400 Received: from ietf.org (odin.ietf.org [132.151.1.176]) by www1.ietf.org (8.11.6/8.11.6) with ESMTP id h4TARkB08223 for ; Thu, 29 May 2003 06:27:46 -0400 Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id GAA25164 for ; Thu, 29 May 2003 06:27:39 -0400 (EDT) Received: from ietf-mx ([132.151.6.1]) by ietf-mx with esmtp (Exim 4.12) id 19LKbj-000556-00 for routing-discussion@ietf.org; Thu, 29 May 2003 06:26:03 -0400 Received: from ms-smtp-02.southeast.rr.com ([24.93.67.83]) by ietf-mx with esmtp (Exim 4.12) id 19LKbi-000553-00 for routing-discussion@ietf.org; Thu, 29 May 2003 06:26:02 -0400 Received: from redback.com (rdu162-241-056.nc.rr.com [24.162.241.56]) by ms-smtp-02.southeast.rr.com (8.12.5/8.12.2) with ESMTP id h4TAP8Zh008269; Thu, 29 May 2003 06:25:08 -0400 (EDT) Message-ID: <3ED5E028.2040302@redback.com> From: Acee Lindem User-Agent: Mozilla/5.0 (X11; U; Linux i686; en-US; rv:1.0.2) Gecko/20030208 Netscape/7.02 X-Accept-Language: en-us, en MIME-Version: 1.0 To: Karthikeyan Subramaniam CC: routing-discussion@ietf.org Subject: Re: Software upgradation time References: <20030529065408.32042.qmail@webmail26.rediffmail.com> Content-Type: text/plain; charset=us-ascii; format=flowed Content-Transfer-Encoding: 7bit Content-Transfer-Encoding: 7bit Sender: routing-discussion-admin@ietf.org Errors-To: routing-discussion-admin@ietf.org X-BeenThere: routing-discussion@ietf.org X-Mailman-Version: 2.0.12 Precedence: bulk List-Unsubscribe: , List-Id: Routing Area General mailing list List-Post: List-Help: List-Subscribe: , List-Archive: Date: Thu, 29 May 2003 06:25:44 -0400 Content-Transfer-Encoding: 7bit Karthikeyan Subramaniam wrote: > Hi, > > I have doubt about restart timer value in protocols. > > In OSPF default restart timer is specified as 120 seconds in the draft > "draft-ietf-ospf-hitless-restart-07.txt" and in the case of BGP default > restart timer should not be greater than the HOLDTIME(suggested value as > per RFC 1771 is 90 secs)carried in OPEN. > > Can control software be upgraded within 120/90 seconds? I guess that depends on your implementation and the type of upgrade. If your software is modular it is certainly enough time for an incremental upgrade or a switchover to a redundant control processor. > On what basis > this timer value has been fixed? This was thought to be an upper bound on restart time, redistribution, and synchronization with other protocols. The restart should complete much sooner. Note the timer value is configurable. > > with regards, > S.Karthikeyan. > > > > ___________________________________________________ > Get www. mycompany .com and 5 matching email ids. > Just Rs. 1499/ year. > Click here http://www.rediffmailpro.com > > _______________________________________________ > routing-discussion mailing list > routing-discussion@ietf.org > https://www1.ietf.org/mailman/listinfo/routing-discussion > -- Acee _______________________________________________ routing-discussion mailing list routing-discussion@ietf.org https://www1.ietf.org/mailman/listinfo/routing-discussion