From mpls-bounces@lists.ietf.org Thu Feb 02 22:08:06 2006 Received: from localhost.cnri.reston.va.us ([127.0.0.1] helo=megatron.ietf.org) by megatron.ietf.org with esmtp (Exim 4.32) id 1F4rIr-0005Rm-HZ; Thu, 02 Feb 2006 22:08:06 -0500 Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org) by megatron.ietf.org with esmtp (Exim 4.32) id 1F4rIn-0005KO-Pc for mpls@megatron.ietf.org; Thu, 02 Feb 2006 22:08:01 -0500 Received: from web37806.mail.mud.yahoo.com (web37806.mail.mud.yahoo.com [209.191.87.119]) by ietf.org (8.9.1a/8.9.1a) with SMTP id WAA14212 for ; Thu, 2 Feb 2006 22:06:18 -0500 (EST) Received: (qmail 91093 invoked by uid 60001); 3 Feb 2006 03:07:19 -0000 DomainKey-Signature: a=rsa-sha1; q=dns; c=nofws; s=s1024; d=yahoo.com; h=Message-ID:Received:Date:From:Subject:To:MIME-Version:Content-Type:Content-Transfer-Encoding; b=gKem4zRqM1B3/YEJA2WGB8ZrHULlIe6Rxvwmzb9glepbNtm/9NXyKntPTcrFdCWZ49sgXt7fOZxHScj4lKL0t/VBzBWwdLinO4ADNeeqgwmvnL8PVKgWuG6ekpgFB1mhQIDdJjMIil83tlmXDDnnnlPsgrYqE2m12ojF9j7o4uA= ; Message-ID: <20060203030719.91091.qmail@web37806.mail.mud.yahoo.com> Received: from [12.159.148.121] by web37806.mail.mud.yahoo.com via HTTP; Thu, 02 Feb 2006 19:07:19 PST Date: Thu, 2 Feb 2006 19:07:19 -0800 (PST) From: Hassan Hosseini To: mpls@ietf.org MIME-Version: 1.0 Cc: Subject: [mpls] CFP: Special session on distributed computing and applications X-BeenThere: mpls@lists.ietf.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Multi-Protocol Label Switching WG List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Content-Type: multipart/mixed; boundary="===============1170521977==" Sender: mpls-bounces@lists.ietf.org Errors-To: mpls-bounces@lists.ietf.org --===============1170521977== Content-Type: multipart/alternative; boundary="0-980525575-1138936039=:91085" Content-Transfer-Encoding: 8bit --0-980525575-1138936039=:91085 Content-Type: text/plain; charset=iso-8859-1 Content-Transfer-Encoding: 8bit C A L L F O R P A P E R S ============================= The 2006 International Conference on Communications in Computing (CIC'06) June 26-29, 2006 Monte Carlo Resort, Las Vegas, Nevada, USA The CIC'06 Conference will be held simultaneously with a number of other international conferences as part of WORLDCOMP'06 (The 2006 World Congress in Computer Science, Computer Engineering, and Applied Computing). For the complete list of joint conferences refer to: http://www.world-academy-of-science.org/worldcomp06/ws ) SPECIAL SESSION: Distributed Computing and Applications SESSION CHAIR: Dr. Hassan Hosseini, Cisco Systems SCOPE OF THE SESSION This session will explore and discuss the development of relevant topics that are of high importance in distributed systems: - Data distribution and program mapping - Load balancing - Congestion control - Scalability and performance - High availability - Routing algorithms - Convergence - Security - Constraint based routing - Policy based routing - Multicast SUBMISSION OF PAPERS: Prospective authors are invited to submit their draft paper (about 5 to 8 pages - single space, font size of 10 to 12) via email to Dr. Hassan Hosseini (hhassan@cisco.com) by Feb. 20, 2006. E-mail submissions in MS document or PDF formats are preferable (Fax or postal submissions are also fine.) All reasonable typesetting formats are acceptable (later, the authors of accepted papers will be asked to follow a particular typesetting format to prepare their papers for publication.) The length of the Camera-Ready papers (if accepted) will be limited to 7 (IEEE style) pages. Papers must not have been previously published or currently submitted for publication elsewhere. The first page of the draft paper should include: title of the paper, name, affiliation, postal address, E-mail address, telephone number, and Fax number for each author. The first page should also include the name of the author who will be presenting the paper (if accepted) and a maximum of 5 keywords. Also, the name of the conference that the paper is being submitted to must be mentioned on the first page. Papers will be evaluated for originality, significance, clarity, and soundness. Each paper will be refereed by two researchers in the topical area. The Camera-Ready papers will be reviewed by the session chair. CATEGORIES OF ACCEPTED PAPERS: (RRP) Regular Research Papers 7-page IEEE-style publication in the proceedings 20-minute formal presentation slot (RRR) Regular Research Reports 7-page IEEE-style publication in the proceedings Presentation in an informal setting (during Discussion Sessions) (SRP) Short Research Papers 4-page IEEE-style publication in the proceedings Presentation in an informal setting (during Discussion Sessions) (PST) Posters 1-page IEEE-style publication in the proceedings Presentation in an informal setting (during Discussion Sessions) PURPOSE / HISTORY: CIC'06 is an international conference held simultaneously (ie, same location and dates) with a number of other joint conferences as part of WORLDCOMP'06 (The 2006 World Congress in Computer Science, Computer Engineering, and Applied Computing). WORLDCOMP'06 is the largest annual gathering of researchers in computer science, computer engineering and applied computing. Many of the 28 joint conferences in WORLDCOMP are the premier conferences for presentation of advances in their respective fields. WORLDCOMP'06 is composed of the following international conferences: Parallel and Distributed Processing Techniques and Applications; Scientific Computing; Grid Computing and Applications; Security and Management; Artificial Intelligence; Machine Learning; Software Engineering Research and Practice; Programming Languages and Compilers; Internet Computing; Semantic Web and Web Services; Computer Design; Real-Time Computing Systems and Applications; Embedded Systems and Applications;! Wireless Networks; Pervasive Systems and Computing; Image Processing, Computer Vision, and Pattern Recognition; Computer Graphics and Virtual Reality; Modeling, Simulation and Visualization Methods; Computer Games Development; Frontiers in Education in Computer Science and Engineering; Foundations of Computer Science; e-Learning, e-Business, Enterprise Information Systems, e-Government, and Outsourcing; Data Mining; Information and Knowledge Engineering; Bioinformatics and Computational Biology; Computing in Nanotechnology; Engineering of Reconfigurable Systems and Algorithms; Communications in Computing. The motivation is to assemble a spectrum of affiliated research conferences into a coordinated research meeting held in a common place at a common time. The main goal is to provide a forum for exchange of ideas in a number of research areas that interact. The model used to form these annual conferences facilitates communication among researchers in different fields of computer science, computer engineering and applied computing. Both inward research (core areas of computer science and engineering) and outward research (multi-disciplinary, Inter-disciplinary, and applications) will be covered during the conferences. LOCATION OF CONFERENCES: The conferences will be held in the Monte Carlo Resort hotel, Las Vegas, Nevada, USA (with any overflows at other near-by hotels). The Monte Carlo Resort is a mega hotel with excellent conference facilities and over 3,000 rooms. The hotel is minutes from the airport with 24-hour shuttle service to and from the airport. This hotel has many recreational attractions, including: waterfalls, spa, pools and kiddie pools, sunning decks, Easy River water ride, wave pool with cascades, lighted tennis courts, health spa (with workout equipment, whirlpool, sauna, ...), arcade virtual reality game rooms, nightly shows, snack bars, a number of restaurants, shopping area, bars, ... Many of these attractions are open 24 hours a day and most are suitable for families and children. The negotiated room rate for conference attendees is very reasonable. The hotel is within walking distance from most other attractions (major shopping areas, recreational destinations, fine dining and night club! s, free street shows, ...). SESSION CHAIR: Dr. Hassan Hosseini Cisco Systems Ottawa, Ontario K2K 3J9 Canada Email: hhassan@cisco.com Phone: (613) 254-3796 Fax: (613) 254-3778 IMPORTANT DATES: Submission of draft papers: February 20, 2006 Notification of acceptance: March 20, 2006 Submission of camera-ready papers: April 20, 2006 --------------------------------- Brings words and photos together (easily) with PhotoMail - it's free and works with Yahoo! Mail. --0-980525575-1138936039=:91085 Content-Type: text/html; charset=iso-8859-1 Content-Transfer-Encoding: 8bit
 
C A L L   F O R   P A P E R S
=============================
 
The 2006 International Conference on
Communications in Computing (CIC'06)
 
June 26-29, 2006
Monte Carlo Resort, Las Vegas, Nevada, USA
 
 
The CIC'06 Conference will be held simultaneously with a number of other international conferences as part of WORLDCOMP'06 (The 2006 World Congress in Computer Science, Computer Engineering, and Applied Computing). For the complete list of joint conferences refer to: http://www.world-academy-of-science.org/worldcomp06/ws )
 
 
SPECIAL SESSION: Distributed Computing and Applications
 
SESSION CHAIR: Dr. Hassan Hosseini, Cisco Systems
 
SCOPE OF THE SESSION
 
This session will explore and discuss the development of relevant! topics that are of high importance in distributed systems:
- Data distribution and program mapping
- Load balancing
- Congestion control
- Scalability and performance
- High availability
- Routing algorithms
- Convergence
- Security
- Constraint based routing
- Policy based routing
- Multicast

 
SUBMISSION OF PAPERS:
 
Prospective authors are invited to submit their draft paper (about 5 to 8 pages - single space, font size of 10 to 12) via email to Dr. Hassan Hosseini (hhassan@cisco.com) by Feb. 20, 2006. E-mail submissions in MS document or PDF formats are preferable (Fax or postal submissions are also fine.)  All reasonable typesetting formats are acceptable (later, the authors of accepted papers will be asked to follow a particular typesetting format to prepare their papers for publication.)

The length of the Camera-Ready papers (if accepted) ! will be limited to 7 (IEEE style) pages. Papers must not have been previously published or currently submitted for publication elsewhere. The first page of the draft paper should include: title of the paper, name, affiliation, postal address, E-mail address, telephone number, and Fax number for each author. The first page should also include the name of the author who will be presenting the paper (if accepted) and a maximum of 5 keywords. Also, the name of the conference that the paper is being submitted to must be mentioned on the first page.

Papers will be evaluated for originality, significance, clarity, and soundness.  Each paper will be refereed by two researchers in the topical area.  The Camera-Ready papers will be reviewed by the session chair.
 
CATEGORIES OF ACCEPTED PAPERS:

(RRP)  Regular Research Papers
          7-page IEEE-style publication in the proceedings
          20-minute formal presentation slot
 
(RRR)  Regular Research Reports
          7-page IEEE-style publication in the proceedings
          Presentation in an informal setting (during Discussion Sessions)
 
(SRP)  Short Research Papers
          4-page IEEE-style publication in the proceedings
          Presentation in an informal setting (during Discussion Sessions)
 
(PST)  Posters
          1-page IEEE-style publication in the proceedings
          Presentation in an informal setting (during Discussion Sessions)
 
 
PURPOSE / HISTORY:

CIC'0! 6 is an international conference held simultaneously (ie, same location and dates) with a number of other joint conferences as part of WORLDCOMP'06 (The 2006 World Congress in Computer Science, Computer Engineering, and Applied Computing).  WORLDCOMP'06 is the largest annual gathering of researchers in computer science, computer engineering and applied computing.  Many of the 28 joint conferences in WORLDCOMP are the premier conferences for presentation of advances in their respective fields. WORLDCOMP'06 is composed of the following international conferences: Parallel and Distributed Processing Techniques and Applications; Scientific Computing; Grid Computing and Applications; Security and Management; Artificial Intelligence; Machine Learning; Software Engineering Research and Practice; Programming Languages and Compilers; Internet Computing; Semantic Web and Web Services; Computer Design; Real-Time Computing Systems and Applications; Embedded Systems and Applications; W! ireless Networks; Pervasive Systems and Computing; Image Processing, Computer Vision, and Pattern Recognition; Computer Graphics and Virtual Reality; Modeling, Simulation and Visualization Methods; Computer Games Development; Frontiers in Education in Computer Science and Engineering; Foundations of Computer Science; e-Learning, e-Business, Enterprise Information Systems, e-Government, and Outsourcing; Data Mining; Information and Knowledge Engineering; Bioinformatics and Computational Biology; Computing in Nanotechnology; Engineering of Reconfigurable Systems and Algorithms; Communications in Computing.
The motivation is to assemble a spectrum of affiliated research conferences into a coordinated research meeting held in a common place at a common time.  The main goal is to provide a forum for exchange of ideas in a number of research areas that interact.  The model used to form these annual conferences facilitates communication among researchers in different! fields of computer science, computer engineering and applied computing.  Both inward research (core areas of computer science and engineering) and outward research (multi-disciplinary, Inter-disciplinary, and applications) will be covered during the conferences.
 
 
LOCATION OF CONFERENCES:

The conferences will be held in the Monte Carlo Resort hotel, Las Vegas, Nevada, USA (with any overflows at other near-by hotels). The Monte Carlo Resort is a mega hotel with excellent conference facilities and over 3,000 rooms. The hotel is minutes from the airport with 24-hour shuttle service to and from the airport. This hotel has many recreational attractions, including: waterfalls, spa, pools and kiddie pools, sunning decks, Easy River water ride, wave pool with cascades, lighted tennis courts, health spa (with workout equipment, whirlpool, sauna, ...), arcade virtual reality game rooms, nightly shows, snack bars, a number of restaurants, shopping a! rea, bars, ...  Many of these attractions are open 24 hours a day and most are suitable for families and children. The negotiated room rate for conference attendees is very reasonable.  The hotel is within walking distance from most other attractions (major shopping areas, recreational destinations, fine dining and night clubs, free street shows, ...).
 
 
SESSION CHAIR:

   Dr. Hassan Hosseini
   Cisco Systems
   Ottawa, Ontario K2K 3J9 Canada
   Email: hhassan@cisco.com
   Phone: (613) 254-3796
   Fax: (613) 254-3778
 
 
IMPORTANT DATES:
Submission of draft papers:            February 20, 2006 
Notification of acceptance:            March 20, 2006
Submission of camera-re! ady papers:     April 20, 2006

Brings words and photos together (easily) with
PhotoMail - it's free and works with Yahoo! Mail. --0-980525575-1138936039=:91085-- --===============1170521977== Content-Type: text/plain; charset="us-ascii" MIME-Version: 1.0 Content-Transfer-Encoding: 7bit Content-Disposition: inline _______________________________________________ mpls mailing list mpls@lists.ietf.org https://www1.ietf.org/mailman/listinfo/mpls --===============1170521977==-- From mpls-bounces@lists.ietf.org Fri Feb 03 11:06:53 2006 Received: from localhost.cnri.reston.va.us ([127.0.0.1] helo=megatron.ietf.org) by megatron.ietf.org with esmtp (Exim 4.32) id 1F53SX-0002vF-FB; Fri, 03 Feb 2006 11:06:53 -0500 Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org) by megatron.ietf.org with esmtp (Exim 4.32) id 1F53SU-0002py-Jy for mpls@megatron.ietf.org; Fri, 03 Feb 2006 11:06:50 -0500 Received: from ietf-mx.ietf.org (ietf-mx [132.151.6.1]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id LAA14394 for ; Fri, 3 Feb 2006 11:05:12 -0500 (EST) Received: from gw.imc.kth.se ([193.10.152.67] helo=oberon.imc.kth.se) by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1F53e1-0000L0-BJ for mpls@ietf.org; Fri, 03 Feb 2006 11:18:50 -0500 Received: from mail1.imc.kth.se (mail1.imc.kth.se [193.10.152.140]) by oberon.imc.kth.se (8.13.1/8.13.1) with ESMTP id k13FxxOK002395 for ; Fri, 3 Feb 2006 17:00:00 +0100 Received: from [127.0.0.1] ([172.16.2.233]) by mail1.imc.kth.se; Fri, 03 Feb 2006 17:04:58 +0100 Message-ID: <43E37F28.10706@pi.se> Date: Fri, 03 Feb 2006 17:04:56 +0100 From: Loa Andersson Organization: Acreo AB User-Agent: Mozilla Thunderbird 1.0.5 (Windows/20050711) X-Accept-Language: en-us, en MIME-Version: 1.0 To: mpls@ietf.org Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit X-Spam-Score: 0.0 (/) X-Scan-Signature: f4c2cf0bccc868e4cc88dace71fb3f44 Content-Transfer-Encoding: 7bit Cc: Subject: [mpls] Internet-Drafts Submission Cutoff Dates for the 65th IETF Meeting in Dallas, TX, USA X-BeenThere: mpls@lists.ietf.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Multi-Protocol Label Switching WG List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Sender: mpls-bounces@lists.ietf.org Errors-To: mpls-bounces@lists.ietf.org Working group, this is the dead-lines for Internet Draft submissions for the meeting in Dallas. /Loa There are two (2) Internet-Draft cutoff dates for the 65th IETF Meeting in Dallas, TX, USA: February 27th: Cutoff Date for Initial (i.e., version -00) Internet-Draft Submissions All initial Internet-Drafts (version -00) must be submitted by Monday, February 27th at 9:00 AM ET. As always, all initial submissions with a filename beginning with "draft-ietf" must be approved by the appropriate WG Chair before they can be processed or announced. The Secretariat would appreciate receiving WG Chair approval by Monday, February 20th at 9:00 AM ET. March 6th: Cutoff Date for Revised (i.e., version -01 and higher) Internet-Draft Submissions All revised Internet-Drafts (version -01 and higher) must be submitted by Monday, March 6th at 9:00 AM ET. Initial and revised Internet-Drafts received after their respective cutoff dates will not be made available in the Internet-Drafts directory or announced until on or after Monday, March 20th at 9:00 AM ET, when Internet-Draft posting resumes. Please do not wait until the last minute to submit. Thank you for your understanding and cooperation. If you have any questions or concerns, then please send a message to internet-drafts@ietf.org. The IETF Secretariat FYI: The Internet-Draft cutoff dates as well as other significant dates for the 65th IETF Meeting can be found at http://www.ietf.org/meetings/cutoff_dates_65.html. _______________________________________________ IETF-Announce mailing list IETF-Announce@ietf.org https://www1.ietf.org/mailman/listinfo/ietf-announce -- Loa Andersson Principal Networking Architect Acreo AB phone: +46 8 632 77 14 Isafjordsgatan 22 mobile: +46 739 81 21 64 Kista, Sweden email: loa.andersson@acreo.se loa@pi.se _______________________________________________ mpls mailing list mpls@lists.ietf.org https://www1.ietf.org/mailman/listinfo/mpls From mpls-bounces@lists.ietf.org Fri Feb 03 11:11:55 2006 Received: from localhost.cnri.reston.va.us ([127.0.0.1] helo=megatron.ietf.org) by megatron.ietf.org with esmtp (Exim 4.32) id 1F53XO-0005AM-B4; Fri, 03 Feb 2006 11:11:54 -0500 Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org) by megatron.ietf.org with esmtp (Exim 4.32) id 1F53XK-00059N-2d for mpls@megatron.ietf.org; Fri, 03 Feb 2006 11:11:50 -0500 Received: from ietf-mx.ietf.org (ietf-mx [132.151.6.1]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id LAA15258 for ; Fri, 3 Feb 2006 11:10:11 -0500 (EST) Received: from gw.imc.kth.se ([193.10.152.67] helo=oberon.imc.kth.se) by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1F53iu-0000jU-RK for mpls@ietf.org; Fri, 03 Feb 2006 11:23:50 -0500 Received: from mail1.imc.kth.se (mail1.imc.kth.se [193.10.152.140]) by oberon.imc.kth.se (8.13.1/8.13.1) with ESMTP id k13G5JTv002676 for ; Fri, 3 Feb 2006 17:05:19 +0100 Received: from [127.0.0.1] ([172.16.2.233]) by mail1.imc.kth.se; Fri, 03 Feb 2006 17:10:07 +0100 Message-ID: <43E3805D.7070405@pi.se> Date: Fri, 03 Feb 2006 17:10:05 +0100 From: Loa Andersson Organization: Acreo AB User-Agent: Mozilla Thunderbird 1.0.5 (Windows/20050711) X-Accept-Language: en-us, en MIME-Version: 1.0 References: <43CCAD30.1070008@pi.se> <20060126090110.L91141@kummer.juniper.net> In-Reply-To: <20060126090110.L91141@kummer.juniper.net> Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit X-Spam-Score: 0.0 (/) X-Scan-Signature: 82c9bddb247d9ba4471160a9a865a5f3 Content-Transfer-Encoding: 7bit Cc: mpls@ietf.org Subject: [mpls] Two drafts to become working gorup documents! X-BeenThere: mpls@lists.ietf.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Multi-Protocol Label Switching WG List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Sender: mpls-bounces@lists.ietf.org Errors-To: mpls-bounces@lists.ietf.org All, we have seen a good support to make these drafts working group documents. Could the authors please re-publish them as draft-ieft-mpls-upstream-label-00 and draft-ietf-mpls-multicast-encaps-00 /Loa >> All, >> >> the authors of the following two drafts >> >> draft-raggarwa-mpls-upstream-label-01 >> draft-rosen-mpls-multicast-encaps-01 >> >> has requested that they are made working group >> drafts. We are seeking the the working group consensus >> on this, please send your comments to the working group >> mailing list or to the working group co-chairs before >> EOB January 31st. >> >> -- >> Loa Andersson >> >> Principal Networking Architect >> Acreo AB phone: +46 8 632 77 14 >> Isafjordsgatan 22 mobile: +46 739 81 21 64 >> Kista, Sweden email: loa.andersson@acreo.se >> loa@pi.se >> >> _______________________________________________ >> mpls mailing list >> mpls@lists.ietf.org >> https://www1.ietf.org/mailman/listinfo/mpls > > > Kireeti. > ------- > -- Loa Andersson Principal Networking Architect Acreo AB phone: +46 8 632 77 14 Isafjordsgatan 22 mobile: +46 739 81 21 64 Kista, Sweden email: loa.andersson@acreo.se loa@pi.se _______________________________________________ mpls mailing list mpls@lists.ietf.org https://www1.ietf.org/mailman/listinfo/mpls From mpls-bounces@lists.ietf.org Fri Feb 03 11:15:35 2006 Received: from localhost.cnri.reston.va.us ([127.0.0.1] helo=megatron.ietf.org) by megatron.ietf.org with esmtp (Exim 4.32) id 1F53ax-0006NG-QL; Fri, 03 Feb 2006 11:15:35 -0500 Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org) by megatron.ietf.org with esmtp (Exim 4.32) id 1F53av-0006Dv-06 for mpls@megatron.ietf.org; Fri, 03 Feb 2006 11:15:33 -0500 Received: from ietf-mx.ietf.org (ietf-mx [132.151.6.1]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id LAA15700 for ; Fri, 3 Feb 2006 11:13:43 -0500 (EST) Received: from gw.imc.kth.se ([193.10.152.67] helo=oberon.imc.kth.se) by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1F53mK-0000w6-AM for mpls@ietf.org; Fri, 03 Feb 2006 11:27:21 -0500 Received: from mail1.imc.kth.se (mail1.imc.kth.se [193.10.152.140]) by oberon.imc.kth.se (8.13.1/8.13.1) with ESMTP id k13G8pMR002789 for ; Fri, 3 Feb 2006 17:08:51 +0100 Received: from [127.0.0.1] ([172.16.2.233]) by mail1.imc.kth.se; Fri, 03 Feb 2006 17:14:05 +0100 Message-ID: <43E3814B.80503@pi.se> Date: Fri, 03 Feb 2006 17:14:03 +0100 From: Loa Andersson Organization: Acreo AB User-Agent: Mozilla Thunderbird 1.0.5 (Windows/20050711) X-Accept-Language: en-us, en MIME-Version: 1.0 To: mpls@ietf.org Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit X-Spam-Score: 0.0 (/) X-Scan-Signature: 856eb5f76e7a34990d1d457d8e8e5b7f Content-Transfer-Encoding: 7bit Cc: Subject: [mpls] draft-raggarwa-mpls-ldp-upstream-00 for wg doc? X-BeenThere: mpls@lists.ietf.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Multi-Protocol Label Switching WG List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Sender: mpls-bounces@lists.ietf.org Errors-To: mpls-bounces@lists.ietf.org All, the authors of draft-raggarwa-mpls-ldp-upstream-00 has requested that it is made a working group document. Please review, comment and respond to the working group mailing list if you support it becoming a wg or not. /Loa and George -- Loa Andersson Principal Networking Architect Acreo AB phone: +46 8 632 77 14 Isafjordsgatan 22 mobile: +46 739 81 21 64 Kista, Sweden email: loa.andersson@acreo.se loa@pi.se _______________________________________________ mpls mailing list mpls@lists.ietf.org https://www1.ietf.org/mailman/listinfo/mpls From mpls-bounces@lists.ietf.org Fri Feb 03 11:18:08 2006 Received: from localhost.cnri.reston.va.us ([127.0.0.1] helo=megatron.ietf.org) by megatron.ietf.org with esmtp (Exim 4.32) id 1F53dQ-0008Br-Ce; Fri, 03 Feb 2006 11:18:08 -0500 Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org) by megatron.ietf.org with esmtp (Exim 4.32) id 1F53dN-0008AF-5K for mpls@megatron.ietf.org; Fri, 03 Feb 2006 11:18:06 -0500 Received: from ietf-mx.ietf.org (ietf-mx [132.151.6.1]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id LAA16059 for ; Fri, 3 Feb 2006 11:16:18 -0500 (EST) Received: from gw.imc.kth.se ([193.10.152.67] helo=oberon.imc.kth.se) by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1F53oq-00014Y-2v for mpls@ietf.org; Fri, 03 Feb 2006 11:29:57 -0500 Received: from mail1.imc.kth.se (mail1.imc.kth.se [193.10.152.140]) by oberon.imc.kth.se (8.13.1/8.13.1) with ESMTP id k13GBQkN002910 for ; Fri, 3 Feb 2006 17:11:26 +0100 Received: from [127.0.0.1] ([172.16.2.233]) by mail1.imc.kth.se; Fri, 03 Feb 2006 17:16:23 +0100 Message-ID: <43E381D5.8020008@pi.se> Date: Fri, 03 Feb 2006 17:16:21 +0100 From: Loa Andersson Organization: Acreo AB User-Agent: Mozilla Thunderbird 1.0.5 (Windows/20050711) X-Accept-Language: en-us, en MIME-Version: 1.0 To: mpls@ietf.org Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit X-Spam-Score: 0.0 (/) X-Scan-Signature: 9466e0365fc95844abaf7c3f15a05c7d Content-Transfer-Encoding: 7bit Cc: Subject: [mpls] draft-raggarwa-mpls-rsvp-upstream-00 for wg doc? X-BeenThere: mpls@lists.ietf.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Multi-Protocol Label Switching WG List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Sender: mpls-bounces@lists.ietf.org Errors-To: mpls-bounces@lists.ietf.org All, the authors of draft-raggarwa-mpls-rsvp-upstream-00 has requested that it is made a working group document. Please review, comment and respond to the working group mailing list if you support it becoming a wg or not. /Loa and George PS yes - there are two separate polls one for draft-raggarwa-mpls-ldp-upstream-00 and one for draft-raggarwa-mpls-rsvp-upstream-00 :) -- Loa Andersson Principal Networking Architect Acreo AB phone: +46 8 632 77 14 Isafjordsgatan 22 mobile: +46 739 81 21 64 Kista, Sweden email: loa.andersson@acreo.se loa@pi.se _______________________________________________ mpls mailing list mpls@lists.ietf.org https://www1.ietf.org/mailman/listinfo/mpls From mpls-bounces@lists.ietf.org Fri Feb 03 19:28:59 2006 Received: from localhost.cnri.reston.va.us ([127.0.0.1] helo=megatron.ietf.org) by megatron.ietf.org with esmtp (Exim 4.32) id 1F5BIR-0001Ei-Or; Fri, 03 Feb 2006 19:28:59 -0500 Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org) by megatron.ietf.org with esmtp (Exim 4.32) id 1F5BIP-0001D6-LW for mpls@megatron.ietf.org; Fri, 03 Feb 2006 19:28:58 -0500 Received: from nit.isi.edu (nit.isi.edu [128.9.160.116]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id TAA02722 for ; Fri, 3 Feb 2006 19:27:01 -0500 (EST) Received: from nit.isi.edu (loopback [127.0.0.1]) by nit.isi.edu (8.12.8/8.12.8) with ESMTP id k140SY55009714; Fri, 3 Feb 2006 16:28:34 -0800 Received: (from apache@localhost) by nit.isi.edu (8.12.8/8.12.8/Submit) id k140SYFh009713; Fri, 3 Feb 2006 16:28:34 -0800 Date: Fri, 3 Feb 2006 16:28:34 -0800 Message-Id: <200602040028.k140SYFh009713@nit.isi.edu> To: ietf-announce@ietf.org, rfc-dist@rfc-editor.org From: rfc-editor@rfc-editor.org MIME-Version: 1.0 Content-Type: multipart/mixed; boundary=c1bb507a9b27b8405bda7bd08b306cc7 Cc: mpls@ietf.org, rfc-editor@rfc-editor.org Subject: [mpls] RFC 4377 on Operations and Management (OAM) Requirements for Multi-Protocol Label Switched (MPLS) Networks X-BeenThere: mpls@lists.ietf.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Multi-Protocol Label Switching WG List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Sender: mpls-bounces@lists.ietf.org Errors-To: mpls-bounces@lists.ietf.org --c1bb507a9b27b8405bda7bd08b306cc7 Content-Type: text/plain Content-Transfer-Encoding: 8bit A new Request for Comments is now available in online RFC libraries. RFC 4377 Title: Operations and Management (OAM) Requirements for Multi-Protocol Label Switched (MPLS) Networks Author: T. Nadeau, M. Morrow, G. Swallow, D. Allan, S. Matsushima Status: Informational Date: February 2006 Mailbox: tnadeau@cisco.com, mmorrow@cisco.com, swallow@cisco.com, dallan@nortel.com, satoru@ft.solteria.net Pages: 15 Characters: 31889 Updates/Obsoletes/SeeAlso: None I-D Tag: draft-ietf-mpls-oam-requirements-07.txt URL: http://www.rfc-editor.org/rfc/rfc4377.txt This document specifies Operations and Management (OAM) requirements for Multi-Protocol Label Switching (MPLS), as well as for applications of MPLS, such as pseudo-wire voice and virtual private network services. These requirements have been gathered from network operators who have extensive experience deploying MPLS networks. This memo provides information for the Internet community. This document is a product of the Multiprotocol Label Switching Working Group of the IETF. INFORMATIONAL: This memo provides information for the Internet community. It does not specify an Internet standard of any kind. Distribution of this memo is unlimited. This announcement is sent to the IETF list and the RFC-DIST list. Requests to be added to or deleted from the IETF distribution list should be sent to IETF-REQUEST@IETF.ORG. Requests to be added to or deleted from the RFC-DIST distribution list should be sent to RFC-DIST-REQUEST@RFC-EDITOR.ORG. Details on obtaining RFCs via FTP or EMAIL may be obtained by sending an EMAIL message to rfc-info@RFC-EDITOR.ORG with the message body help: ways_to_get_rfcs. For example: To: rfc-info@RFC-EDITOR.ORG Subject: getting rfcs help: ways_to_get_rfcs Requests for special distribution should be addressed to either the author of the RFC in question, or to RFC-Manager@RFC-EDITOR.ORG. Unless specifically noted otherwise on the RFC itself, all RFCs are for unlimited distribution. Submissions for Requests for Comments should be sent to RFC-EDITOR@RFC-EDITOR.ORG. Please consult RFC 2223, Instructions to RFC Authors, for further information. Joyce K. Reynolds and Sandy Ginoza USC/Information Sciences Institute ... --c1bb507a9b27b8405bda7bd08b306cc7 A new Request for Comments is now available in online RFC libraries. RFC 4377 Title: Operations and Management (OAM) Requirements for Multi-Protocol Label Switched (MPLS) Networks Author: T. Nadeau, M. Morrow, G. Swallow, D. Allan, S. Matsushima Status: Informational Date: February 2006 Mailbox: tnadeau@cisco.com, mmorrow@cisco.com, swallow@cisco.com, dallan@nortel.com, satoru@ft.solteria.net Pages: 15 Characters: 31889 Updates/Obsoletes/SeeAlso: None I-D Tag: draft-ietf-mpls-oam-requirements-07.txt URL: http://www.rfc-editor.org/rfc/rfc4377.txt This document specifies Operations and Management (OAM) requirements for Multi-Protocol Label Switching (MPLS), as well as for applications of MPLS, such as pseudo-wire voice and virtual private network services. These requirements have been gathered from network operators who have extensive experience deploying MPLS networks. This memo provides information for the Internet community. This document is a product of the Multiprotocol Label Switching Working Group of the IETF. INFORMATIONAL: This memo provides information for the Internet community. It does not specify an Internet standard of any kind. Distribution of this memo is unlimited. This announcement is sent to the IETF list and the RFC-DIST list. Requests to be added to or deleted from the IETF distribution list should be sent to IETF-REQUEST@IETF.ORG. Requests to be added to or deleted from the RFC-DIST distribution list should be sent to RFC-DIST-REQUEST@RFC-EDITOR.ORG. Details on obtaining RFCs via FTP or EMAIL may be obtained by sending an EMAIL message to rfc-info@RFC-EDITOR.ORG with the message body help: ways_to_get_rfcs. For example: To: rfc-info@RFC-EDITOR.ORG Subject: getting rfcs help: ways_to_get_rfcs Requests for special distribution should be addressed to either the author of the RFC in question, or to RFC-Manager@RFC-EDITOR.ORG. Unless specifically noted otherwise on the RFC itself, all RFCs are for unlimited distribution. Submissions for Requests for Comments should be sent to RFC-EDITOR@RFC-EDITOR.ORG. Please consult RFC 2223, Instructions to RFC Authors, for further information. Joyce K. Reynolds and Sandy Ginoza USC/Information Sciences Institute ... --c1bb507a9b27b8405bda7bd08b306cc7 Content-Type: text/plain; charset="us-ascii" MIME-Version: 1.0 Content-Transfer-Encoding: 7bit Content-Disposition: inline _______________________________________________ mpls mailing list mpls@lists.ietf.org https://www1.ietf.org/mailman/listinfo/mpls --c1bb507a9b27b8405bda7bd08b306cc7-- From mpls-bounces@lists.ietf.org Fri Feb 03 19:30:06 2006 Received: from localhost.cnri.reston.va.us ([127.0.0.1] helo=megatron.ietf.org) by megatron.ietf.org with esmtp (Exim 4.32) id 1F5BJW-0001PS-Dp; Fri, 03 Feb 2006 19:30:06 -0500 Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org) by megatron.ietf.org with esmtp (Exim 4.32) id 1F5BJU-0001MG-I2 for mpls@megatron.ietf.org; Fri, 03 Feb 2006 19:30:04 -0500 Received: from nit.isi.edu (nit.isi.edu [128.9.160.116]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id TAA02887 for ; Fri, 3 Feb 2006 19:28:07 -0500 (EST) Received: from nit.isi.edu (loopback [127.0.0.1]) by nit.isi.edu (8.12.8/8.12.8) with ESMTP id k140Th55009722; Fri, 3 Feb 2006 16:29:43 -0800 Received: (from apache@localhost) by nit.isi.edu (8.12.8/8.12.8/Submit) id k140ThXB009721; Fri, 3 Feb 2006 16:29:43 -0800 Date: Fri, 3 Feb 2006 16:29:43 -0800 Message-Id: <200602040029.k140ThXB009721@nit.isi.edu> To: ietf-announce@ietf.org, rfc-dist@rfc-editor.org From: rfc-editor@rfc-editor.org MIME-Version: 1.0 Content-Type: multipart/mixed; boundary=4be0e4aaa6947779078c9dc6f3dcf2d1 Cc: mpls@ietf.org, rfc-editor@rfc-editor.org Subject: [mpls] RFC 4378 on A Framework for Multi-Protocol Label Switching (MPLS) Operations and Management (OAM) X-BeenThere: mpls@lists.ietf.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Multi-Protocol Label Switching WG List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Sender: mpls-bounces@lists.ietf.org Errors-To: mpls-bounces@lists.ietf.org --4be0e4aaa6947779078c9dc6f3dcf2d1 Content-Type: text/plain Content-Transfer-Encoding: 8bit A new Request for Comments is now available in online RFC libraries. RFC 4378 Title: A Framework for Multi-Protocol Label Switching (MPLS) Operations and Management (OAM) Author: D. Allan, Ed., T. Nadeau, Ed. Status: Informational Date: February 2006 Mailbox: dallan@nortel.com, tnadeau@cisco.com Pages: 11 Characters: 23640 Updates/Obsoletes/SeeAlso: None I-D Tag: draft-ietf-mpls-oam-frmwk-05.txt URL: http://www.rfc-editor.org/rfc/rfc4378.txt This document is a framework for how data plane protocols can be applied to operations and maintenance procedures for Multi-Protocol Label Switching (MPLS). The document is structured to outline how Operations and Management (OAM) functionality can be used to assist in fault, configuration, accounting, performance, and security management, commonly known by the acronym FCAPS. This memo provides information for the Internet community. This document is a product of the Multiprotocol Label Switching Working Group of the IETF. INFORMATIONAL: This memo provides information for the Internet community. It does not specify an Internet standard of any kind. Distribution of this memo is unlimited. This announcement is sent to the IETF list and the RFC-DIST list. Requests to be added to or deleted from the IETF distribution list should be sent to IETF-REQUEST@IETF.ORG. Requests to be added to or deleted from the RFC-DIST distribution list should be sent to RFC-DIST-REQUEST@RFC-EDITOR.ORG. Details on obtaining RFCs via FTP or EMAIL may be obtained by sending an EMAIL message to rfc-info@RFC-EDITOR.ORG with the message body help: ways_to_get_rfcs. For example: To: rfc-info@RFC-EDITOR.ORG Subject: getting rfcs help: ways_to_get_rfcs Requests for special distribution should be addressed to either the author of the RFC in question, or to RFC-Manager@RFC-EDITOR.ORG. Unless specifically noted otherwise on the RFC itself, all RFCs are for unlimited distribution. Submissions for Requests for Comments should be sent to RFC-EDITOR@RFC-EDITOR.ORG. Please consult RFC 2223, Instructions to RFC Authors, for further information. Joyce K. Reynolds and Sandy Ginoza USC/Information Sciences Institute ... --4be0e4aaa6947779078c9dc6f3dcf2d1 A new Request for Comments is now available in online RFC libraries. RFC 4378 Title: A Framework for Multi-Protocol Label Switching (MPLS) Operations and Management (OAM) Author: D. Allan, Ed., T. Nadeau, Ed. Status: Informational Date: February 2006 Mailbox: dallan@nortel.com, tnadeau@cisco.com Pages: 11 Characters: 23640 Updates/Obsoletes/SeeAlso: None I-D Tag: draft-ietf-mpls-oam-frmwk-05.txt URL: http://www.rfc-editor.org/rfc/rfc4378.txt This document is a framework for how data plane protocols can be applied to operations and maintenance procedures for Multi-Protocol Label Switching (MPLS). The document is structured to outline how Operations and Management (OAM) functionality can be used to assist in fault, configuration, accounting, performance, and security management, commonly known by the acronym FCAPS. This memo provides information for the Internet community. This document is a product of the Multiprotocol Label Switching Working Group of the IETF. INFORMATIONAL: This memo provides information for the Internet community. It does not specify an Internet standard of any kind. Distribution of this memo is unlimited. This announcement is sent to the IETF list and the RFC-DIST list. Requests to be added to or deleted from the IETF distribution list should be sent to IETF-REQUEST@IETF.ORG. Requests to be added to or deleted from the RFC-DIST distribution list should be sent to RFC-DIST-REQUEST@RFC-EDITOR.ORG. Details on obtaining RFCs via FTP or EMAIL may be obtained by sending an EMAIL message to rfc-info@RFC-EDITOR.ORG with the message body help: ways_to_get_rfcs. For example: To: rfc-info@RFC-EDITOR.ORG Subject: getting rfcs help: ways_to_get_rfcs Requests for special distribution should be addressed to either the author of the RFC in question, or to RFC-Manager@RFC-EDITOR.ORG. Unless specifically noted otherwise on the RFC itself, all RFCs are for unlimited distribution. Submissions for Requests for Comments should be sent to RFC-EDITOR@RFC-EDITOR.ORG. Please consult RFC 2223, Instructions to RFC Authors, for further information. Joyce K. Reynolds and Sandy Ginoza USC/Information Sciences Institute ... --4be0e4aaa6947779078c9dc6f3dcf2d1 Content-Type: text/plain; charset="us-ascii" MIME-Version: 1.0 Content-Transfer-Encoding: 7bit Content-Disposition: inline _______________________________________________ mpls mailing list mpls@lists.ietf.org https://www1.ietf.org/mailman/listinfo/mpls --4be0e4aaa6947779078c9dc6f3dcf2d1-- From mpls-bounces@lists.ietf.org Fri Feb 03 19:32:23 2006 Received: from localhost.cnri.reston.va.us ([127.0.0.1] helo=megatron.ietf.org) by megatron.ietf.org with esmtp (Exim 4.32) id 1F5BLj-0001kn-Eu; Fri, 03 Feb 2006 19:32:23 -0500 Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org) by megatron.ietf.org with esmtp (Exim 4.32) id 1F5BLf-0001ia-AI for mpls@megatron.ietf.org; Fri, 03 Feb 2006 19:32:19 -0500 Received: from nit.isi.edu (nit.isi.edu [128.9.160.116]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id TAA03184 for ; Fri, 3 Feb 2006 19:30:24 -0500 (EST) Received: from nit.isi.edu (loopback [127.0.0.1]) by nit.isi.edu (8.12.8/8.12.8) with ESMTP id k140Vw55009752; Fri, 3 Feb 2006 16:31:58 -0800 Received: (from apache@localhost) by nit.isi.edu (8.12.8/8.12.8/Submit) id k140Vwsx009751; Fri, 3 Feb 2006 16:31:58 -0800 Date: Fri, 3 Feb 2006 16:31:58 -0800 Message-Id: <200602040031.k140Vwsx009751@nit.isi.edu> To: ietf-announce@ietf.org, rfc-dist@rfc-editor.org From: rfc-editor@rfc-editor.org MIME-Version: 1.0 Content-Type: multipart/mixed; boundary=9eb9a5199c752d01b2076db844de79bd Cc: mpls@ietf.org, rfc-editor@rfc-editor.org Subject: [mpls] RFC 4379 on Detecting Multi-Protocol Label Switched (MPLS) Data Plane Failures X-BeenThere: mpls@lists.ietf.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Multi-Protocol Label Switching WG List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Sender: mpls-bounces@lists.ietf.org Errors-To: mpls-bounces@lists.ietf.org --9eb9a5199c752d01b2076db844de79bd Content-Type: text/plain Content-Transfer-Encoding: 8bit A new Request for Comments is now available in online RFC libraries. RFC 4379 Title: Detecting Multi-Protocol Label Switched (MPLS) Data Plane Failures Author: K. Kompella, G. Swallow Status: Standards Track Date: February 2006 Mailbox: kireeti@juniper.net, swallow@cisco.com Pages: 50 Characters: 116872 Updates: RFC1122 See-Also: I-D Tag: draft-ietf-mpls-lsp-ping-13.txt URL: http://www.rfc-editor.org/rfc/rfc4379.txt This document describes a simple and efficient mechanism that can be used to detect data plane failures in Multi-Protocol Label Switching (MPLS) Label Switched Paths (LSPs). There are two parts to this document: information carried in an MPLS \"echo request\" and \"echo reply\" for the purposes of fault detection and isolation, and mechanisms for reliably sending the echo reply. [STANDARDS TRACK] This document is a product of the Multiprotocol Label Switching Working Group of the IETF. This is now a Proposed Standard Protocol. STANDARDS TRACK: This document specifies an Internet standards track protocol for the Internet community,and requests discussion and suggestions for improvements.Please refer to the current edition of the Internet Official Protocol Standards (STD 1) for the standardization state and status of this protocol. Distribution of this memo is unlimited. This announcement is sent to the IETF list and the RFC-DIST list. Requests to be added to or deleted from the IETF distribution list should be sent to IETF-REQUEST@IETF.ORG. Requests to be added to or deleted from the RFC-DIST distribution list should be sent to RFC-DIST-REQUEST@RFC-EDITOR.ORG. Details on obtaining RFCs via FTP or EMAIL may be obtained by sending an EMAIL message to rfc-info@RFC-EDITOR.ORG with the message body help: ways_to_get_rfcs. For example: To: rfc-info@RFC-EDITOR.ORG Subject: getting rfcs help: ways_to_get_rfcs Requests for special distribution should be addressed to either the author of the RFC in question, or to RFC-Manager@RFC-EDITOR.ORG. Unless specifically noted otherwise on the RFC itself, all RFCs are for unlimited distribution. Submissions for Requests for Comments should be sent to RFC-EDITOR@RFC-EDITOR.ORG. Please consult RFC 2223, Instructions to RFC Authors, for further information. Joyce K. Reynolds and Sandy Ginoza USC/Information Sciences Institute ... --9eb9a5199c752d01b2076db844de79bd A new Request for Comments is now available in online RFC libraries. RFC 4379 Title: Detecting Multi-Protocol Label Switched (MPLS) Data Plane Failures Author: K. Kompella, G. Swallow Status: Standards Track Date: February 2006 Mailbox: kireeti@juniper.net, swallow@cisco.com Pages: 50 Characters: 116872 Updates: RFC1122 See-Also: I-D Tag: draft-ietf-mpls-lsp-ping-13.txt URL: http://www.rfc-editor.org/rfc/rfc4379.txt This document describes a simple and efficient mechanism that can be used to detect data plane failures in Multi-Protocol Label Switching (MPLS) Label Switched Paths (LSPs). There are two parts to this document: information carried in an MPLS \"echo request\" and \"echo reply\" for the purposes of fault detection and isolation, and mechanisms for reliably sending the echo reply. [STANDARDS TRACK] This document is a product of the Multiprotocol Label Switching Working Group of the IETF. This is now a Proposed Standard Protocol. STANDARDS TRACK: This document specifies an Internet standards track protocol for the Internet community,and requests discussion and suggestions for improvements.Please refer to the current edition of the Internet Official Protocol Standards (STD 1) for the standardization state and status of this protocol. Distribution of this memo is unlimited. This announcement is sent to the IETF list and the RFC-DIST list. Requests to be added to or deleted from the IETF distribution list should be sent to IETF-REQUEST@IETF.ORG. Requests to be added to or deleted from the RFC-DIST distribution list should be sent to RFC-DIST-REQUEST@RFC-EDITOR.ORG. Details on obtaining RFCs via FTP or EMAIL may be obtained by sending an EMAIL message to rfc-info@RFC-EDITOR.ORG with the message body help: ways_to_get_rfcs. For example: To: rfc-info@RFC-EDITOR.ORG Subject: getting rfcs help: ways_to_get_rfcs Requests for special distribution should be addressed to either the author of the RFC in question, or to RFC-Manager@RFC-EDITOR.ORG. Unless specifically noted otherwise on the RFC itself, all RFCs are for unlimited distribution. Submissions for Requests for Comments should be sent to RFC-EDITOR@RFC-EDITOR.ORG. Please consult RFC 2223, Instructions to RFC Authors, for further information. Joyce K. Reynolds and Sandy Ginoza USC/Information Sciences Institute ... --9eb9a5199c752d01b2076db844de79bd Content-Type: text/plain; charset="us-ascii" MIME-Version: 1.0 Content-Transfer-Encoding: 7bit Content-Disposition: inline _______________________________________________ mpls mailing list mpls@lists.ietf.org https://www1.ietf.org/mailman/listinfo/mpls --9eb9a5199c752d01b2076db844de79bd-- From mpls-bounces@lists.ietf.org Fri Feb 03 22:24:10 2006 Received: from localhost.cnri.reston.va.us ([127.0.0.1] helo=megatron.ietf.org) by megatron.ietf.org with esmtp (Exim 4.32) id 1F5E1x-0007HS-Eh; Fri, 03 Feb 2006 22:24:09 -0500 Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org) by megatron.ietf.org with esmtp (Exim 4.32) id 1F5E1t-00078C-VR for mpls@megatron.ietf.org; Fri, 03 Feb 2006 22:24:06 -0500 Received: from ietf-mx.ietf.org (ietf-mx [132.151.6.1]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id WAA27440 for ; Fri, 3 Feb 2006 22:22:21 -0500 (EST) Received: from pop-canoe.atl.sa.earthlink.net ([207.69.195.66]) by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1F5EDT-0000QZ-TE for mpls@ietf.org; Fri, 03 Feb 2006 22:36:05 -0500 Received: from h-68-164-152-195.snvacaid.dynamic.covad.net ([68.164.152.195] helo=earthlink.net) by pop-canoe.atl.sa.earthlink.net with esmtp (Exim 3.36 #10) id 1F5E1e-0002ST-00 for mpls@ietf.org; Fri, 03 Feb 2006 22:23:50 -0500 Message-ID: <43E420CC.F8B1BE4F@earthlink.net> Date: Fri, 03 Feb 2006 19:34:36 -0800 From: Erblichs X-Sender: "Erblichs" <@smtp.earthlink.net> (Unverified) X-Mailer: Mozilla 4.72 [en]C-gatewaynet (Win98; I) X-Accept-Language: en MIME-Version: 1.0 To: mpls@ietf.org Content-Type: text/plain; charset=iso-8859-2 Content-Transfer-Encoding: 7bit X-Spam-Score: 0.1 (/) X-Scan-Signature: d17f825e43c9aed4fd65b7edddddec89 Content-Transfer-Encoding: 7bit Cc: Subject: [mpls] Detecting Multi-Protocol Label Switched (MPLS)Data Plane Failures X-BeenThere: mpls@lists.ietf.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Multi-Protocol Label Switching WG List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Sender: mpls-bounces@lists.ietf.org Errors-To: mpls-bounces@lists.ietf.org Authors, Hopefully a simple question.. 4.3. Sending an MPLS Echo Request When sending a MPLS Echo request in traceroute mode, and the LSP changes before it is completed. SHOULD this situation cause any issues? Mitchell Erblich _______________________________________________ mpls mailing list mpls@lists.ietf.org https://www1.ietf.org/mailman/listinfo/mpls From mpls-bounces@lists.ietf.org Sun Feb 05 11:12:19 2006 Received: from localhost.cnri.reston.va.us ([127.0.0.1] helo=megatron.ietf.org) by megatron.ietf.org with esmtp (Exim 4.32) id 1F5mUt-0003oz-NV; Sun, 05 Feb 2006 11:12:19 -0500 Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org) by megatron.ietf.org with esmtp (Exim 4.32) id 1F5mUq-0003nN-7q for mpls@megatron.ietf.org; Sun, 05 Feb 2006 11:12:17 -0500 Received: from huawei-3com.com (smtp.huawei-3com.com [210.21.230.51]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id LAA22221 for ; Sun, 5 Feb 2006 11:10:24 -0500 (EST) Received: from huawei-3com.com (localhost [127.0.0.1]) by h3cml01-in.huawei-3com.com (iPlanet Messaging Server 5.2 HotFix 1.25 (built Mar 3 2004)) with ESMTP id <0IU800ACB2FEAI@h3cml01-in.huawei-3com.com> for mpls@lists.ietf.org; Mon, 06 Feb 2006 00:14:02 +0800 (CST) Received: from monza ([59.108.192.34]) by h3cml01-in.huawei-3com.com (iPlanet Messaging Server 5.2 HotFix 1.25 (built Mar 3 2004)) with ESMTPA id <0IU8005QS2FDPM@h3cml01-in.huawei-3com.com> for mpls@lists.ietf.org; Mon, 06 Feb 2006 00:14:02 +0800 (CST) Date: Mon, 06 Feb 2006 00:11:26 +0800 From: hongang To: mpls@ietf.org Message-id: <02ae01c62a6e$d0f5d9e0$c202a8c0@monza> MIME-version: 1.0 X-MIMEOLE: Produced By Microsoft MimeOLE V6.00.2900.2180 X-Mailer: Microsoft Outlook Express 6.00.2900.2180 Content-type: text/plain; charset=iso-8859-1 Content-transfer-encoding: 7BIT X-Priority: 3 X-MSMail-priority: Normal References: <0IU400H2GGHVL8@h3cml01-in.huawei-3com.com> Content-Transfer-Encoding: 7BIT Cc: Subject: [mpls] Re: mpls Digest, Vol 22, Issue 2 X-BeenThere: mpls@lists.ietf.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Multi-Protocol Label Switching WG List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Sender: mpls-bounces@lists.ietf.org Errors-To: mpls-bounces@lists.ietf.org ----- Original Message ----- From: To: Sent: Saturday, February 04, 2006 1:27 AM Subject: mpls Digest, Vol 22, Issue 2 > Send mpls mailing list submissions to > mpls@lists.ietf.org > > To subscribe or unsubscribe via the World Wide Web, visit > https://www1.ietf.org/mailman/listinfo/mpls > or, via email, send a message with subject or body 'help' to > mpls-request@lists.ietf.org > > You can reach the person managing the list at > mpls-owner@lists.ietf.org > > When replying, please edit your Subject line so it is more specific > than "Re: Contents of mpls digest..." > > > Today's Topics: > > 1. CFP: Special session on distributed computing and > applications (Hassan Hosseini) > 2. Internet-Drafts Submission Cutoff Dates for the 65th IETF > Meeting in Dallas, TX, USA (Loa Andersson) > 3. Two drafts to become working gorup documents! (Loa Andersson) > 4. draft-raggarwa-mpls-ldp-upstream-00 for wg doc? (Loa Andersson) > 5. draft-raggarwa-mpls-rsvp-upstream-00 for wg doc? (Loa Andersson) > > > ---------------------------------------------------------------------- > > Message: 1 > Date: Thu, 2 Feb 2006 19:07:19 -0800 (PST) > From: Hassan Hosseini > Subject: [mpls] CFP: Special session on distributed computing and > applications > To: mpls@ietf.org > Message-ID: <20060203030719.91091.qmail@web37806.mail.mud.yahoo.com> > Content-Type: text/plain; charset="iso-8859-1" > > > C A L L F O R P A P E R S > ============================= > > The 2006 International Conference on > Communications in Computing (CIC'06) > > June 26-29, 2006 > Monte Carlo Resort, Las Vegas, Nevada, USA > > > The CIC'06 Conference will be held simultaneously with a number of other international conferences as part of WORLDCOMP'06 (The 2006 World Congress in Computer Science, Computer Engineering, and Applied Computing). For the complete list of joint conferences refer to: http://www.world-academy-of-science.org/worldcomp06/ws ) > > > SPECIAL SESSION: Distributed Computing and Applications > > > SESSION CHAIR: Dr. Hassan Hosseini, Cisco Systems > > SCOPE OF THE SESSION > > This session will explore and discuss the development of relevant topics that are of high importance in distributed systems: > - Data distribution and program mapping > - Load balancing > - Congestion control > - Scalability and performance > - High availability > - Routing algorithms > - Convergence > - Security > - Constraint based routing > - Policy based routing > - Multicast > > > SUBMISSION OF PAPERS: > > Prospective authors are invited to submit their draft paper (about 5 to 8 pages - single space, font size of 10 to 12) via email to Dr. Hassan Hosseini (hhassan@cisco.com) by Feb. 20, 2006. E-mail submissions in MS document or PDF formats are preferable (Fax or postal submissions are also fine.) All reasonable typesetting formats are acceptable (later, the authors of accepted papers will be asked to follow a particular typesetting format to prepare their papers for publication.) > > The length of the Camera-Ready papers (if accepted) will be limited to 7 (IEEE style) pages. Papers must not have been previously published or currently submitted for publication elsewhere. The first page of the draft paper should include: title of the paper, name, affiliation, postal address, E-mail address, telephone number, and Fax number for each author. The first page should also include the name of the author who will be presenting the paper (if accepted) and a maximum of 5 keywords. Also, the name of the conference that the paper is being submitted to must be mentioned on the first page. > > Papers will be evaluated for originality, significance, clarity, and soundness. Each paper will be refereed by two researchers in the topical area. The Camera-Ready papers will be reviewed by the session chair. > > CATEGORIES OF ACCEPTED PAPERS: > > (RRP) Regular Research Papers > 7-page IEEE-style publication in the proceedings > 20-minute formal presentation slot > > (RRR) Regular Research Reports > 7-page IEEE-style publication in the proceedings > Presentation in an informal setting (during Discussion Sessions) > > (SRP) Short Research Papers > 4-page IEEE-style publication in the proceedings > Presentation in an informal setting (during Discussion Sessions) > > (PST) Posters > 1-page IEEE-style publication in the proceedings > Presentation in an informal setting (during Discussion Sessions) > > > PURPOSE / HISTORY: > > CIC'06 is an international conference held simultaneously (ie, same location and dates) with a number of other joint conferences as part of WORLDCOMP'06 (The 2006 World Congress in Computer Science, Computer Engineering, and Applied Computing). WORLDCOMP'06 is the largest annual gathering of researchers in computer science, computer engineering and applied computing. Many of the 28 joint conferences in WORLDCOMP are the premier conferences for presentation of advances in their respective fields. WORLDCOMP'06 is composed of the following international conferences: Parallel and Distributed Processing Techniques and Applications; Scientific Computing; Grid Computing and Applications; Security and Management; Artificial Intelligence; Machine Learning; Software Engineering Research and Practice; Programming Languages and Compilers; Internet Computing; Semantic Web and Web Services; Computer Design; Real-Time Computing Systems and Applications; Embedded Systems and Application! s;! > Wireless > Networks; Pervasive Systems and Computing; Image Processing, Computer Vision, and Pattern Recognition; Computer Graphics and Virtual Reality; Modeling, Simulation and Visualization Methods; Computer Games Development; Frontiers in Education in Computer Science and Engineering; Foundations of Computer Science; e-Learning, e-Business, Enterprise Information Systems, e-Government, and Outsourcing; Data Mining; Information and Knowledge Engineering; Bioinformatics and Computational Biology; Computing in Nanotechnology; Engineering of Reconfigurable Systems and Algorithms; Communications in Computing. > The motivation is to assemble a spectrum of affiliated research conferences into a coordinated research meeting held in a common place at a common time. The main goal is to provide a forum for exchange of ideas in a number of research areas that interact. The model used to form these annual conferences facilitates communication among researchers in different fields of computer science, computer engineering and applied computing. Both inward research (core areas of computer science and engineering) and outward research (multi-disciplinary, Inter-disciplinary, and applications) will be covered during the conferences. > > > LOCATION OF CONFERENCES: > > The conferences will be held in the Monte Carlo Resort hotel, Las Vegas, Nevada, USA (with any overflows at other near-by hotels). The Monte Carlo Resort is a mega hotel with excellent conference facilities and over 3,000 rooms. The hotel is minutes from the airport with 24-hour shuttle service to and from the airport. This hotel has many recreational attractions, including: waterfalls, spa, pools and kiddie pools, sunning decks, Easy River water ride, wave pool with cascades, lighted tennis courts, health spa (with workout equipment, whirlpool, sauna, ...), arcade virtual reality game rooms, nightly shows, snack bars, a number of restaurants, shopping area, bars, ... Many of these attractions are open 24 hours a day and most are suitable for families and children. The negotiated room rate for conference attendees is very reasonable. The hotel is within walking distance from most other attractions (major shopping areas, recreational destinations, fine dining and night cl! ub! > s, free > street shows, ...). > > > SESSION CHAIR: > > Dr. Hassan Hosseini > Cisco Systems > Ottawa, Ontario K2K 3J9 Canada > Email: hhassan@cisco.com > Phone: (613) 254-3796 > Fax: (613) 254-3778 > > > IMPORTANT DATES: > Submission of draft papers: February 20, 2006 > Notification of acceptance: March 20, 2006 > Submission of camera-ready papers: April 20, 2006 > > > > > --------------------------------- > Brings words and photos together (easily) with > PhotoMail - it's free and works with Yahoo! Mail. > -------------- next part -------------- > An HTML attachment was scrubbed... > URL: http://www1.ietf.org/pipermail/mpls/attachments/20060202/5e08ba81/attachment-0001.htm > > ------------------------------ > > Message: 2 > Date: Fri, 03 Feb 2006 17:04:56 +0100 > From: Loa Andersson > Subject: [mpls] Internet-Drafts Submission Cutoff Dates for the 65th > IETF Meeting in Dallas, TX, USA > To: mpls@ietf.org > Message-ID: <43E37F28.10706@pi.se> > Content-Type: text/plain; charset=ISO-8859-1; format=flowed > > Working group, > > this is the dead-lines for Internet Draft submissions for the > meeting in Dallas. > > /Loa > > > There are two (2) Internet-Draft cutoff dates for the 65th > IETF Meeting in Dallas, TX, USA: > > February 27th: Cutoff Date for Initial (i.e., version -00) > Internet-Draft Submissions > > All initial Internet-Drafts (version -00) must be submitted by Monday, > February 27th at 9:00 AM ET. As always, all initial submissions with a > filename beginning with "draft-ietf" must be approved by the > appropriate WG Chair before they can be processed or announced. The > Secretariat would appreciate receiving WG Chair approval by Monday, > February 20th at 9:00 AM ET. > > March 6th: Cutoff Date for Revised (i.e., version -01 and higher) > Internet-Draft Submissions > > All revised Internet-Drafts (version -01 and higher) must be submitted > by Monday, March 6th at 9:00 AM ET. > > Initial and revised Internet-Drafts received after their respective > cutoff dates will not be made available in the Internet-Drafts > directory or announced until on or after Monday, March 20th at 9:00 > AM ET, when Internet-Draft posting resumes. Please do not wait until > the last minute to submit. > > Thank you for your understanding and cooperation. If you have any > questions or concerns, then please send a message to > internet-drafts@ietf.org. > > The IETF Secretariat > > FYI: The Internet-Draft cutoff dates as well as other significant dates > for the 65th IETF Meeting can be found at > http://www.ietf.org/meetings/cutoff_dates_65.html. > > _______________________________________________ > IETF-Announce mailing list > IETF-Announce@ietf.org > https://www1.ietf.org/mailman/listinfo/ietf-announce > > > > -- > Loa Andersson > > Principal Networking Architect > Acreo AB phone: +46 8 632 77 14 > Isafjordsgatan 22 mobile: +46 739 81 21 64 > Kista, Sweden email: loa.andersson@acreo.se > loa@pi.se > > > > ------------------------------ > > Message: 3 > Date: Fri, 03 Feb 2006 17:10:05 +0100 > From: Loa Andersson > Subject: [mpls] Two drafts to become working gorup documents! > Cc: mpls@ietf.org > Message-ID: <43E3805D.7070405@pi.se> > Content-Type: text/plain; charset=ISO-8859-1; format=flowed > > All, > > we have seen a good support to make these drafts working group > documents. > Could the authors please re-publish them as > > draft-ieft-mpls-upstream-label-00 > and > draft-ietf-mpls-multicast-encaps-00 > > > > /Loa > > >>> All, >>> >>> the authors of the following two drafts >>> >>> draft-raggarwa-mpls-upstream-label-01 >>> draft-rosen-mpls-multicast-encaps-01 >>> >>> has requested that they are made working group >>> drafts. We are seeking the the working group consensus >>> on this, please send your comments to the working group >>> mailing list or to the working group co-chairs before >>> EOB January 31st. >>> >>> -- >>> Loa Andersson >>> >>> Principal Networking Architect >>> Acreo AB phone: +46 8 632 77 14 >>> Isafjordsgatan 22 mobile: +46 739 81 21 64 >>> Kista, Sweden email: loa.andersson@acreo.se >>> loa@pi.se >>> >>> _______________________________________________ >>> mpls mailing list >>> mpls@lists.ietf.org >>> https://www1.ietf.org/mailman/listinfo/mpls >> >> >> Kireeti. >> ------- >> > > > -- > Loa Andersson > > Principal Networking Architect > Acreo AB phone: +46 8 632 77 14 > Isafjordsgatan 22 mobile: +46 739 81 21 64 > Kista, Sweden email: loa.andersson@acreo.se > loa@pi.se > > > > ------------------------------ > > Message: 4 > Date: Fri, 03 Feb 2006 17:14:03 +0100 > From: Loa Andersson > Subject: [mpls] draft-raggarwa-mpls-ldp-upstream-00 for wg doc? > To: mpls@ietf.org > Message-ID: <43E3814B.80503@pi.se> > Content-Type: text/plain; charset=ISO-8859-1; format=flowed > > All, > > the authors of draft-raggarwa-mpls-ldp-upstream-00 > has requested that it is made a working group document. > > Please review, comment and respond to the working group mailing > list if you support it becoming a wg or not. > > /Loa and George > > -- > Loa Andersson > > Principal Networking Architect > Acreo AB phone: +46 8 632 77 14 > Isafjordsgatan 22 mobile: +46 739 81 21 64 > Kista, Sweden email: loa.andersson@acreo.se > loa@pi.se > > > > ------------------------------ > > Message: 5 > Date: Fri, 03 Feb 2006 17:16:21 +0100 > From: Loa Andersson > Subject: [mpls] draft-raggarwa-mpls-rsvp-upstream-00 for wg doc? > To: mpls@ietf.org > Message-ID: <43E381D5.8020008@pi.se> > Content-Type: text/plain; charset=ISO-8859-1; format=flowed > > All, > > the authors of draft-raggarwa-mpls-rsvp-upstream-00 > has requested that it is made a working group document. > > Please review, comment and respond to the working group mailing > list if you support it becoming a wg or not. > > /Loa and George > > PS > > yes - there are two separate polls one for > > draft-raggarwa-mpls-ldp-upstream-00 > and one for > draft-raggarwa-mpls-rsvp-upstream-00 > > :) > > > -- > Loa Andersson > > Principal Networking Architect > Acreo AB phone: +46 8 632 77 14 > Isafjordsgatan 22 mobile: +46 739 81 21 64 > Kista, Sweden email: loa.andersson@acreo.se > loa@pi.se > > > > ------------------------------ > > _______________________________________________ > mpls mailing list > mpls@lists.ietf.org > https://www1.ietf.org/mailman/listinfo/mpls > > > End of mpls Digest, Vol 22, Issue 2 > *********************************** > _______________________________________________ mpls mailing list mpls@lists.ietf.org https://www1.ietf.org/mailman/listinfo/mpls From mpls-bounces@lists.ietf.org Mon Feb 06 04:25:21 2006 Received: from localhost.cnri.reston.va.us ([127.0.0.1] helo=megatron.ietf.org) by megatron.ietf.org with esmtp (Exim 4.32) id 1F62cb-0005gf-Jh; Mon, 06 Feb 2006 04:25:21 -0500 Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org) by megatron.ietf.org with esmtp (Exim 4.32) id 1F62cZ-0005gG-MA for mpls@megatron.ietf.org; Mon, 06 Feb 2006 04:25:19 -0500 Received: from ietf-mx.ietf.org (ietf-mx [132.151.6.1]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id EAA01013 for ; Mon, 6 Feb 2006 04:23:31 -0500 (EST) Received: from gw.imc.kth.se ([193.10.152.67] helo=oberon.imc.kth.se) by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1F62oX-000241-U2 for mpls@ietf.org; Mon, 06 Feb 2006 04:37:47 -0500 Received: from mail1.imc.kth.se (mail1.imc.kth.se [193.10.152.140]) by oberon.imc.kth.se (8.13.1/8.13.1) with ESMTP id k169IIZj028666 for ; Mon, 6 Feb 2006 10:18:19 +0100 Received: from [127.0.0.1] ([172.16.2.233]) by mail1.imc.kth.se; Mon, 06 Feb 2006 10:23:19 +0100 Message-ID: <43E7158C.7060109@pi.se> Date: Mon, 06 Feb 2006 10:23:24 +0100 From: Loa Andersson Organization: Acreo AB User-Agent: Mozilla Thunderbird 1.0.5 (Windows/20050711) X-Accept-Language: en-us, en MIME-Version: 1.0 To: mpls@ietf.org Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit X-Spam-Score: 0.0 (/) X-Scan-Signature: 856eb5f76e7a34990d1d457d8e8e5b7f Content-Transfer-Encoding: 7bit Cc: Subject: [mpls] agenda for wg meeting in Dallas X-BeenThere: mpls@lists.ietf.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Multi-Protocol Label Switching WG List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Sender: mpls-bounces@lists.ietf.org Errors-To: mpls-bounces@lists.ietf.org Working group, we will have a working group meeting in Dallas, it is time to start getting the agenda together. We clearly expect discussion on the multicast drafts. Please send request for agenda slots to the working group chairs. /Loa -- Loa Andersson Principal Networking Architect Acreo AB phone: +46 8 632 77 14 Isafjordsgatan 22 mobile: +46 739 81 21 64 Kista, Sweden email: loa.andersson@acreo.se loa@pi.se _______________________________________________ mpls mailing list mpls@lists.ietf.org https://www1.ietf.org/mailman/listinfo/mpls From mpls-bounces@lists.ietf.org Mon Feb 06 07:50:55 2006 Received: from localhost.cnri.reston.va.us ([127.0.0.1] helo=megatron.ietf.org) by megatron.ietf.org with esmtp (Exim 4.32) id 1F65pX-0004sI-TG; Mon, 06 Feb 2006 07:50:55 -0500 Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org) by megatron.ietf.org with esmtp (Exim 4.32) id 1F65pW-0004rX-LK for mpls@megatron.ietf.org; Mon, 06 Feb 2006 07:50:54 -0500 Received: from ietf-mx.ietf.org (ietf-mx [132.151.6.1]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id HAA14697 for ; Mon, 6 Feb 2006 07:49:04 -0500 (EST) Received: from ams-iport-1.cisco.com ([144.254.224.140]) by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1F661W-0003xn-AU for mpls@ietf.org; Mon, 06 Feb 2006 08:03:20 -0500 Received: from ams-core-1.cisco.com ([144.254.224.150]) by ams-iport-1.cisco.com with ESMTP; 06 Feb 2006 13:50:32 +0100 Received: from xbh-ams-331.emea.cisco.com (xbh-ams-331.cisco.com [144.254.231.71]) by ams-core-1.cisco.com (8.12.10/8.12.6) with ESMTP id k16Co26A024999; Mon, 6 Feb 2006 13:50:30 +0100 (MET) Received: from xfe-ams-332.cisco.com ([144.254.231.73]) by xbh-ams-331.emea.cisco.com with Microsoft SMTPSVC(6.0.3790.0); Mon, 6 Feb 2006 13:50:28 +0100 Received: from SwallowPB.local ([10.61.80.189]) by xfe-ams-332.cisco.com with Microsoft SMTPSVC(6.0.3790.0); Mon, 6 Feb 2006 04:50:26 -0800 Received: from cisco.com (localhost [127.0.0.1]) by SwallowPB.local (Postfix) with ESMTP id 3E3BD17B472; Mon, 6 Feb 2006 07:50:51 -0500 (EST) To: mpls@ietf.org From: George Swallow X-Mailer: MH-E 7.4.3; nmh 1.1-RC3; GNU Emacs 21.2.1 Date: Mon, 06 Feb 2006 07:50:51 -0500 Message-Id: <20060206125051.3E3BD17B472@SwallowPB.local> X-OriginalArrivalTime: 06 Feb 2006 12:50:28.0513 (UTC) FILETIME=[E81F8910:01C62B1B] X-Spam-Score: 0.0 (/) X-Scan-Signature: 79899194edc4f33a41f49410777972f8 Cc: Subject: [mpls] LDP Multicast to WG Document X-BeenThere: mpls@lists.ietf.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Multi-Protocol Label Switching WG List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Sender: mpls-bounces@lists.ietf.org Errors-To: mpls-bounces@lists.ietf.org It has been requested that Label Distribution Protocol Extensions for Point-to-Multipoint and Multipoint-to-Multipoint Label Switched Paths draft-minei-wijnands-mpls-ldp-p2mp-00 become a MPLS WG document. Please indicate your support or objections by the end of this week. Thanks, ...George ======================================================================== George Swallow Cisco Systems (978) 936-1398 1414 Massachusetts Avenue Boxborough, MA 01719 _______________________________________________ mpls mailing list mpls@lists.ietf.org https://www1.ietf.org/mailman/listinfo/mpls From mpls-bounces@lists.ietf.org Mon Feb 06 15:04:25 2006 Received: from localhost.cnri.reston.va.us ([127.0.0.1] helo=megatron.ietf.org) by megatron.ietf.org with esmtp (Exim 4.32) id 1F6Cb3-0001SC-6x; Mon, 06 Feb 2006 15:04:25 -0500 Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org) by megatron.ietf.org with esmtp (Exim 4.32) id 1F6Cb1-0001Rz-MM for mpls@megatron.ietf.org; Mon, 06 Feb 2006 15:04:23 -0500 Received: from newodin.ietf.org (newodin.ietf.org [10.27.6.50]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id PAA17564 for ; Mon, 6 Feb 2006 15:02:42 -0500 (EST) Received: from apache by newodin.ietf.org with local (Exim 4.43) id 1F6Cb0-0007bS-Ug; Mon, 06 Feb 2006 15:04:22 -0500 X-test-idtracker: no To: IETF-Announce From: The IESG Message-Id: Date: Mon, 06 Feb 2006 15:04:22 -0500 Cc: mpls@ietf.org Subject: [mpls] Last Call: 'LDP Specification' to Draft Standard X-BeenThere: mpls@lists.ietf.org X-Mailman-Version: 2.1.5 Precedence: list Reply-To: iesg@ietf.org List-Id: Multi-Protocol Label Switching WG List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Sender: mpls-bounces@lists.ietf.org Errors-To: mpls-bounces@lists.ietf.org The IESG has received a request from the Multiprotocol Label Switching WG to consider the following documents: - 'LDP Specification ' as a Draft Standard - 'Experience with the LDP protocol ' as an Informational RFC - 'LDP Implementation Survey Results ' as an Informational RFC The IESG plans to make a decision in the next few weeks, and solicits final comments on this action. Please send any comments to the iesg@ietf.org or ietf@ietf.org mailing lists by 2006-02-20. The file can be obtained via http://www.ietf.org/internet-drafts/draft-ietf-mpls-rfc3036bis-03.txt http://www.ietf.org/internet-drafts/draft-ietf-mpls-ldp-experience-00.txt http://www.ietf.org/internet-drafts/draft-ietf-mpls-ldp-survey2002-00.txt Implementation Report can be accessed at http://www.ietf.org/internet-drafts/draft-ietf-mpls-ldp-survey2002-00.txt _______________________________________________ mpls mailing list mpls@lists.ietf.org https://www1.ietf.org/mailman/listinfo/mpls From mpls-bounces@lists.ietf.org Mon Feb 06 19:00:15 2006 Received: from localhost.cnri.reston.va.us ([127.0.0.1] helo=megatron.ietf.org) by megatron.ietf.org with esmtp (Exim 4.32) id 1F6GHH-0002qg-SW; Mon, 06 Feb 2006 19:00:15 -0500 Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org) by megatron.ietf.org with esmtp (Exim 4.32) id 1F6GHG-0002p3-I8 for mpls@megatron.ietf.org; Mon, 06 Feb 2006 19:00:14 -0500 Received: from ietf-mx.ietf.org (ietf-mx [132.151.6.1]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id SAA24811 for ; Mon, 6 Feb 2006 18:58:25 -0500 (EST) Received: from stl-smtpout-01.boeing.com ([130.76.96.56]) by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1F6GTK-0003rN-Su for mpls@ietf.org; Mon, 06 Feb 2006 19:12:48 -0500 Received: from blv-av-01.boeing.com ([192.42.227.216]) by stl-smtpout-01.boeing.com (8.9.2.MG.10092003/8.8.5-M2) with ESMTP id RAA28753; Mon, 6 Feb 2006 17:59:51 -0600 (CST) Received: from XCH-SWBH-04.sw.nos.boeing.com (localhost [127.0.0.1]) by blv-av-01.boeing.com (8.11.3/8.11.3/MBS-AV-LDAP-01) with ESMTP id k16NxoW12194; Mon, 6 Feb 2006 15:59:50 -0800 (PST) Received: from XCH-SW-42.sw.nos.boeing.com ([192.79.11.43]) by XCH-SWBH-04.sw.nos.boeing.com with Microsoft SMTPSVC(6.0.3790.211); Mon, 6 Feb 2006 15:59:49 -0800 X-MimeOLE: Produced By Microsoft Exchange V6.5.7226.0 Content-class: urn:content-classes:message MIME-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: quoted-printable Subject: RE: [mpls] LDP Multicast to WG Document Date: Mon, 6 Feb 2006 15:59:49 -0800 Message-ID: <626FC7C6A97381468FB872072AB5DDC83699C7@XCH-SW-42.sw.nos.boeing.com> Thread-Topic: [mpls] LDP Multicast to WG Document Thread-Index: AcYrHjIUYnsOn964RBGgIdtt/TVmXwAWzVkA From: "Drake, John E" To: "George Swallow" , X-OriginalArrivalTime: 06 Feb 2006 23:59:49.0953 (UTC) FILETIME=[6A34F310:01C62B79] X-Spam-Score: 0.0 (/) X-Scan-Signature: 39bd8f8cbb76cae18b7e23f7cf6b2b9f Content-Transfer-Encoding: quoted-printable Cc: X-BeenThere: mpls@lists.ietf.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Multi-Protocol Label Switching WG List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Sender: mpls-bounces@lists.ietf.org Errors-To: mpls-bounces@lists.ietf.org yes > -----Original Message----- > From: George Swallow [mailto:swallow@cisco.com] > Sent: Monday, February 06, 2006 4:51 AM > To: mpls@ietf.org > Subject: [mpls] LDP Multicast to WG Document >=20 > It has been requested that >=20 > Label Distribution Protocol Extensions for Point-to-Multipoint and > Multipoint-to-Multipoint Label Switched Paths > draft-minei-wijnands-mpls-ldp-p2mp-00 >=20 > become a MPLS WG document. >=20 > Please indicate your support or objections by the end of this week. >=20 > Thanks, >=20 > ...George >=20 > =3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D= =3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D= =3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D > George Swallow Cisco Systems (978) 936-1398 > 1414 Massachusetts Avenue > Boxborough, MA 01719 >=20 >=20 >=20 > _______________________________________________ > mpls mailing list > mpls@lists.ietf.org > https://www1.ietf.org/mailman/listinfo/mpls _______________________________________________ mpls mailing list mpls@lists.ietf.org https://www1.ietf.org/mailman/listinfo/mpls From mpls-bounces@lists.ietf.org Tue Feb 07 01:32:18 2006 Received: from localhost.cnri.reston.va.us ([127.0.0.1] helo=megatron.ietf.org) by megatron.ietf.org with esmtp (Exim 4.32) id 1F6MOf-00023s-Tl; Tue, 07 Feb 2006 01:32:17 -0500 Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org) by megatron.ietf.org with esmtp (Exim 4.32) id 1F6MOd-0001bf-Iu for mpls@megatron.ietf.org; Tue, 07 Feb 2006 01:32:15 -0500 Received: from ietf-mx.ietf.org (ietf-mx [132.151.6.1]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id BAA24439 for ; Tue, 7 Feb 2006 01:28:59 -0500 (EST) Received: from pop-sarus.atl.sa.earthlink.net ([207.69.195.72]) by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1F6MZR-0001z3-Dc for mpls@ietf.org; Tue, 07 Feb 2006 01:43:25 -0500 Received: from h-68-164-152-195.snvacaid.dynamic.covad.net ([68.164.152.195] helo=earthlink.net) by pop-sarus.atl.sa.earthlink.net with esmtp (Exim 3.36 #10) id 1F6HHB-0006HU-00; Mon, 06 Feb 2006 20:04:14 -0500 Message-ID: <43E7F3CD.ADD76DE0@earthlink.net> Date: Mon, 06 Feb 2006 17:11:41 -0800 From: Erblichs X-Sender: "Erblichs" <@smtp.earthlink.net> (Unverified) X-Mailer: Mozilla 4.72 [en]C-gatewaynet (Win98; I) X-Accept-Language: en MIME-Version: 1.0 To: George Swallow Subject: Re: [mpls] LDP Multicast to WG Document References: <20060206125051.3E3BD17B472@SwallowPB.local> Content-Type: text/plain; charset=iso-8859-2 Content-Transfer-Encoding: 7bit X-Spam-Score: 0.1 (/) X-Scan-Signature: 825e642946eda55cd9bc654a36dab8c2 Content-Transfer-Encoding: 7bit Cc: mpls@ietf.org X-BeenThere: mpls@lists.ietf.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Multi-Protocol Label Switching WG List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Sender: mpls-bounces@lists.ietf.org Errors-To: mpls-bounces@lists.ietf.org George Swallow, I have done little work with P2MP and MP2MP, so I do not feel correct in voicing my opinion, however, I would like to ask a few questions. Just clarifying a few issues in my mind. Any answers would be helpful. 1) 1.2 Terminology With transit and bud LSR types,"directly connected" is used. Can I assume that basic and extended nbr peer discovery and establishment both qualify for "directly connected". Because, I only consider the extended with targeted hello's and have a "grey" understanding of whether those are always really "directly connected". 2) 2.3.1.1. Determining one's 'upstream LSR' A node Z that is part of P2MP LSP determines the LDP peer U which lies on the best path from Z to the root node X. If there are more than one such LDP peers, only one of them is picked. U is Z's "Upstream LSR" for . Multiple parts: "only one of them is picked" Am I correct that you are picking U equals? Why isn't some identifier for the LDP peer used to compare the multiple LDP peers for the "picking"? Why wouldn't you want to have a known result based on a public algortihm, like highest router-id? Why can't more tban one be picked? And why wouldn't you want to pick 2 or more and load balance or have done it because of some fast-reroute policy if one of the selected "U" fails? 3) 4. Setting up MP2MP LSPs with LDP Am I right that we would want the identical forward and reverse (ack/replies) data flows (directional LSPs) to follow the same LDP peers in both directions? we could verify this with a LSP traceroute. If both the paths don't traverse the same LDP peers, I could assume that one direction could have a significantly faster bandwidth. Thus both sides (ingress/egress) of the 2 or more directional LSPs should attempt to use the same transit LDP peers. Thus, some form of consistent selection should be available. (Clarify: One path of Ingress A to Egress B, and the replies coming from Ingress B to Egress A, both directional data flows transitioning either the same set of LDP peers or a different set. I would assume that they should be the same set of transit LDP peers.) My reason why... Thus, If the reply segments take a faster bandwidth LSP and our data flows are also controlled by TCP, won't the acks return with less inter segment / packet spacing. This decreased spacing will force the newer data segments to be bunched even more (congestion avoidance) than just adding 1 segment per round trip. If the first source/Ingress to Egress data path is faster than the return, won't we waste the return bandwidth capacity? Thus a LSP traceroute should be the same as either initiated from the Ingress or from the Egress ends of the path. You can offline the email if you don't think anyone is intereted in the answers. Thanks, Mitchell Erblich ----------------- George Swallow wrote: > > It has been requested that > > Label Distribution Protocol Extensions for Point-to-Multipoint and > Multipoint-to-Multipoint Label Switched Paths > draft-minei-wijnands-mpls-ldp-p2mp-00 > > become a MPLS WG document. > > Please indicate your support or objections by the end of this week. > > Thanks, > > ...George > > ======================================================================== > George Swallow Cisco Systems (978) 936-1398 > 1414 Massachusetts Avenue > Boxborough, MA 01719 > > _______________________________________________ > mpls mailing list > mpls@lists.ietf.org > https://www1.ietf.org/mailman/listinfo/mpls _______________________________________________ mpls mailing list mpls@lists.ietf.org https://www1.ietf.org/mailman/listinfo/mpls From mpls-bounces@lists.ietf.org Tue Feb 07 02:41:47 2006 Received: from localhost.cnri.reston.va.us ([127.0.0.1] helo=megatron.ietf.org) by megatron.ietf.org with esmtp (Exim 4.32) id 1F6NTv-0006WS-Ag; Tue, 07 Feb 2006 02:41:47 -0500 Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org) by megatron.ietf.org with esmtp (Exim 4.32) id 1F6NTt-0006VN-HD for mpls@megatron.ietf.org; Tue, 07 Feb 2006 02:41:45 -0500 Received: from ietf-mx.ietf.org (ietf-mx [132.151.6.1]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id CAA29159 for ; Tue, 7 Feb 2006 02:39:56 -0500 (EST) Received: from smtp11.wanadoo.fr ([193.252.22.31]) by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1F6Ng6-0004OR-9T for mpls@ietf.org; Tue, 07 Feb 2006 02:54:23 -0500 Received: from me-wanadoo.net (localhost [127.0.0.1]) by mwinf1101.wanadoo.fr (SMTP Server) with ESMTP id BB15C1C000BC for ; Tue, 7 Feb 2006 08:41:26 +0100 (CET) Received: from home.treizh.net (ARennes-252-1-98-37.w81-48.abo.wanadoo.fr [81.48.229.37]) by mwinf1101.wanadoo.fr (SMTP Server) with ESMTP id AAD831C000A6; Tue, 7 Feb 2006 08:41:26 +0100 (CET) X-ME-UUID: 20060207074126699.AAD831C000A6@mwinf1101.wanadoo.fr Received: from wintermute (localhost [127.0.0.1]) by home.treizh.net (Postfix) with ESMTP id 1DFB022FF3; Tue, 7 Feb 2006 08:41:26 +0100 (CET) Subject: Re: [mpls] LDP Multicast to WG Document From: Thomas Morin To: George Swallow In-Reply-To: <20060206125051.3E3BD17B472@SwallowPB.local> References: <20060206125051.3E3BD17B472@SwallowPB.local> Content-Type: text/plain Organization: France Telecom R&D Date: Tue, 07 Feb 2006 08:41:16 +0100 Message-Id: <1139298077.12608.1.camel@wintermute> Mime-Version: 1.0 X-Mailer: Evolution 2.4.2.1 Content-Transfer-Encoding: 7bit X-Spam-Score: 0.1 (/) X-Scan-Signature: 856eb5f76e7a34990d1d457d8e8e5b7f Content-Transfer-Encoding: 7bit Cc: mpls@ietf.org X-BeenThere: mpls@lists.ietf.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Multi-Protocol Label Switching WG List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Sender: mpls-bounces@lists.ietf.org Errors-To: mpls-bounces@lists.ietf.org George Swallow: > It has been requested that > > Label Distribution Protocol Extensions for Point-to-Multipoint and > Multipoint-to-Multipoint Label Switched Paths > draft-minei-wijnands-mpls-ldp-p2mp-00 > > become a MPLS WG document. > > Please indicate your support or objections by the end of this week. I support this work becoming a working group item. -Thomas _______________________________________________ mpls mailing list mpls@lists.ietf.org https://www1.ietf.org/mailman/listinfo/mpls From mpls-bounces@lists.ietf.org Tue Feb 07 12:54:42 2006 Received: from localhost.cnri.reston.va.us ([127.0.0.1] helo=megatron.ietf.org) by megatron.ietf.org with esmtp (Exim 4.32) id 1F6X30-0002bO-WB; Tue, 07 Feb 2006 12:54:39 -0500 Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org) by megatron.ietf.org with esmtp (Exim 4.32) id 1F6X2w-0002YY-2s for mpls@megatron.ietf.org; Tue, 07 Feb 2006 12:54:34 -0500 Received: from ietf-mx.ietf.org (ietf-mx [132.151.6.1]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id MAA16062 for ; Tue, 7 Feb 2006 12:52:53 -0500 (EST) Received: from p-mail2.rd.francetelecom.com ([195.101.245.16]) by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1F6XFM-0000md-6G for mpls@ietf.org; Tue, 07 Feb 2006 13:07:25 -0500 Received: from ftrdmel10.rd.francetelecom.fr ([10.193.117.156]) by ftrdsmtp2.rd.francetelecom.fr with Microsoft SMTPSVC(6.0.3790.211); Tue, 7 Feb 2006 18:54:08 +0100 Received: from wintermute ([10.193.4.45]) by ftrdmel10.rd.francetelecom.fr with Microsoft SMTPSVC(6.0.3790.211); Tue, 7 Feb 2006 18:54:08 +0100 Subject: Re: [mpls] LDP Multicast to WG Document From: Thomas Morin To: Erblichs In-Reply-To: <43E7F3CD.ADD76DE0@earthlink.net> References: <20060206125051.3E3BD17B472@SwallowPB.local> <43E7F3CD.ADD76DE0@earthlink.net> Content-Type: text/plain Organization: France Telecom R&D Date: Tue, 07 Feb 2006 18:53:51 +0100 Message-Id: <1139334831.6740.58.camel@wintermute> Mime-Version: 1.0 X-Mailer: Evolution 2.4.2.1 Content-Transfer-Encoding: 7bit X-OriginalArrivalTime: 07 Feb 2006 17:54:08.0439 (UTC) FILETIME=[7E755C70:01C62C0F] X-Spam-Score: 0.0 (/) X-Scan-Signature: 31247fb3be228bb596db9127becad0bc Content-Transfer-Encoding: 7bit Cc: mpls@ietf.org X-BeenThere: mpls@lists.ietf.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Multi-Protocol Label Switching WG List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Sender: mpls-bounces@lists.ietf.org Errors-To: mpls-bounces@lists.ietf.org Hi Mitchell, folks, Erblichs: > 2) 2.3.1.1. Determining one's 'upstream LSR' > > A node Z that is part of P2MP LSP determines the LDP peer U > which lies on the best path from Z to the root node X. If there are > more than one such LDP peers, only one of them is picked. U is Z's > "Upstream LSR" for . > > Multiple parts: > > "only one of them is picked" > Am I correct that you are picking U equals? > > Why isn't some identifier for the LDP peer used to compare > the multiple LDP peers for the "picking"? > > Why wouldn't you want to have a known result based on a public > algortihm, like highest router-id? > > Why can't more tban one be picked? > > And why wouldn't you want to pick 2 or more and load balance or have > done it because of some fast-reroute policy if one of the selected > "U" fails? Load balancing for one tree can't work: if you have more than one upstream branch, since all traffic for this P2MP FEC has to flow on each of them, so you'll end up with duplicates at the point where they meet again downstream. I think your points are relevant though: - its true a router has to chose precisely one upstream (for a said P2MP tree) - among the set of upstreams that the lowest cost - in the case where there happens to be a transit LAN, then the procedure for choosing one upstream would need to be standardized; or else two downstream may elect a different upstream which would result in some bandwidth waste (when no transit LAN exists, this doesn't need to be standardized, local decision is ok) - it could be a very simple procedure: as you suggested "take the highest router id" - but it could be one that would allow for load balancing, like hashing each {root,opaque-id,upstream-candidate} with a simple standard hash and electing as upstream router the one with the lowest hash value. That would be very nice. -Thomas > George Swallow wrote: > > > > It has been requested that > > > > Label Distribution Protocol Extensions for Point-to-Multipoint and > > Multipoint-to-Multipoint Label Switched Paths > > draft-minei-wijnands-mpls-ldp-p2mp-00 > > > > become a MPLS WG document. > > > > Please indicate your support or objections by the end of this week. > > > > Thanks, > > > > ...George > > > > ======================================================================== > > George Swallow Cisco Systems (978) 936-1398 > > 1414 Massachusetts Avenue > > Boxborough, MA 01719 > > > > _______________________________________________ > > mpls mailing list > > mpls@lists.ietf.org > > https://www1.ietf.org/mailman/listinfo/mpls > > _______________________________________________ > mpls mailing list > mpls@lists.ietf.org > https://www1.ietf.org/mailman/listinfo/mpls _______________________________________________ mpls mailing list mpls@lists.ietf.org https://www1.ietf.org/mailman/listinfo/mpls From mpls-bounces@lists.ietf.org Tue Feb 07 15:37:50 2006 Received: from localhost.cnri.reston.va.us ([127.0.0.1] helo=megatron.ietf.org) by megatron.ietf.org with esmtp (Exim 4.32) id 1F6Zaw-0000rV-M5; Tue, 07 Feb 2006 15:37:50 -0500 Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org) by megatron.ietf.org with esmtp (Exim 4.32) id 1F6Zat-0000lH-IN for mpls@megatron.ietf.org; Tue, 07 Feb 2006 15:37:49 -0500 Received: from ietf-mx.ietf.org (ietf-mx [132.151.6.1]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id PAA27714 for ; Tue, 7 Feb 2006 15:36:05 -0500 (EST) Received: from tcmail22.telekom.de ([217.6.95.236]) by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1F6ZnK-0006Gd-R8 for mpls@ietf.org; Tue, 07 Feb 2006 15:50:40 -0500 Received: from g9jbr.mgb01.telekom.de (g9jbr.mgb01.telekom.de [164.20.31.6]) by tcmail21.dmz.telekom.de with ESMTP; Tue, 7 Feb 2006 21:37:29 +0100 Received: by G9JBR.mgb01.telekom.de with Internet Mail Service (5.5.2653.19) id <1MK8FLA1>; Tue, 7 Feb 2006 21:37:29 +0100 Message-Id: <1E4CCB2441C5C0409AD8A929482A09F3122642@S4DE9JSAAIG.ost.t-com.de> From: "Leymann, Nicolai" To: swallow@cisco.com, mpls@ietf.org Subject: AW: [mpls] LDP Multicast to WG Document Date: Tue, 7 Feb 2006 21:38:32 +0100 MIME-Version: 1.0 X-Mailer: Internet Mail Service (5.5.2653.19) Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: quoted-printable X-Spam-Score: 0.0 (/) X-Scan-Signature: e1e48a527f609d1be2bc8d8a70eb76cb Content-Transfer-Encoding: quoted-printable Cc: X-BeenThere: mpls@lists.ietf.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Multi-Protocol Label Switching WG List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Sender: mpls-bounces@lists.ietf.org Errors-To: mpls-bounces@lists.ietf.org Yes. Nic > -----Urspr=FCngliche Nachricht----- > Von: George Swallow [mailto:swallow@cisco.com]=20 > Gesendet: Montag, 6. Februar 2006 13:51 > An: mpls@ietf.org > Betreff: [mpls] LDP Multicast to WG Document >=20 > It has been requested that=20 >=20 > Label Distribution Protocol Extensions for Point-to-Multipoint and > Multipoint-to-Multipoint Label Switched Paths > draft-minei-wijnands-mpls-ldp-p2mp-00 >=20 > become a MPLS WG document. >=20 > Please indicate your support or objections by the end of this week. >=20 > Thanks, >=20 > ...George >=20 > = =3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D= =3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D= =3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D > =3D=3D=3D=3D=3D=3D=3D=3D=3D=3D > George Swallow Cisco Systems =20 > (978) 936-1398 > 1414 Massachusetts Avenue > Boxborough, MA 01719 >=20 >=20 >=20 > _______________________________________________ > mpls mailing list > mpls@lists.ietf.org > https://www1.ietf.org/mailman/listinfo/mpls >=20 _______________________________________________ mpls mailing list mpls@lists.ietf.org https://www1.ietf.org/mailman/listinfo/mpls From mpls-bounces@lists.ietf.org Tue Feb 07 18:46:24 2006 Received: from localhost.cnri.reston.va.us ([127.0.0.1] helo=megatron.ietf.org) by megatron.ietf.org with esmtp (Exim 4.32) id 1F6cXQ-0004zG-KA; Tue, 07 Feb 2006 18:46:24 -0500 Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org) by megatron.ietf.org with esmtp (Exim 4.32) id 1F6cXO-0004yC-V6 for mpls@megatron.ietf.org; Tue, 07 Feb 2006 18:46:22 -0500 Received: from ietf-mx.ietf.org (ietf-mx [132.151.6.1]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id SAA12020 for ; Tue, 7 Feb 2006 18:44:34 -0500 (EST) Received: from rtp-iport-2.cisco.com ([64.102.122.149]) by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1F6cjj-0004FN-Ai for mpls@ietf.org; Tue, 07 Feb 2006 18:59:09 -0500 Received: from rtp-core-2.cisco.com ([64.102.124.13]) by rtp-iport-2.cisco.com with ESMTP; 07 Feb 2006 18:46:00 -0500 X-IronPort-AV: i="4.02,96,1139202000"; d="scan'208"; a="81908468:sNHT10826928734" Received: from xbh-rtp-201.amer.cisco.com (xbh-rtp-201.cisco.com [64.102.31.12]) by rtp-core-2.cisco.com (8.12.10/8.12.6) with ESMTP id k17NjN6d001909 for ; Tue, 7 Feb 2006 18:45:58 -0500 (EST) Received: from xfe-rtp-202.amer.cisco.com ([64.102.31.21]) by xbh-rtp-201.amer.cisco.com with Microsoft SMTPSVC(6.0.3790.211); Tue, 7 Feb 2006 18:45:52 -0500 Received: from [192.168.1.101] ([10.86.242.189]) by xfe-rtp-202.amer.cisco.com with Microsoft SMTPSVC(6.0.3790.211); Tue, 7 Feb 2006 18:45:52 -0500 Mime-Version: 1.0 (Apple Message framework v746.2) Content-Transfer-Encoding: 7bit Message-Id: <6343A00D-F629-4026-AD4B-C2EAB85CFF1C@cisco.com> Content-Type: text/plain; charset=US-ASCII; delsp=yes; format=flowed To: mpls@ietf.org From: JP Vasseur Date: Tue, 7 Feb 2006 18:45:23 -0500 X-Mailer: Apple Mail (2.746.2) X-OriginalArrivalTime: 07 Feb 2006 23:45:52.0069 (UTC) FILETIME=[A133BF50:01C62C40] X-Spam-Score: 0.0 (/) X-Scan-Signature: 30ac594df0e66ffa5a93eb4c48bcb014 Content-Transfer-Encoding: 7bit Cc: Subject: [mpls] draft-vasseur-mpls-number-0-bw-te-lsps-00 X-BeenThere: mpls@lists.ietf.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Multi-Protocol Label Switching WG List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Sender: mpls-bounces@lists.ietf.org Errors-To: mpls-bounces@lists.ietf.org Hi, Just to let you know that a new (quite simple) ID has been posted proposing OSPF/ISIS Link sub-TLV to advertise the number of unconstrained TE LSPs signaled across a link. Comments are very welcome. Thanks. JP. _______________________________________________ mpls mailing list mpls@lists.ietf.org https://www1.ietf.org/mailman/listinfo/mpls From mpls-bounces@lists.ietf.org Tue Feb 07 22:20:27 2006 Received: from localhost.cnri.reston.va.us ([127.0.0.1] helo=megatron.ietf.org) by megatron.ietf.org with esmtp (Exim 4.32) id 1F6fsY-0007jJ-7T; Tue, 07 Feb 2006 22:20:26 -0500 Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org) by megatron.ietf.org with esmtp (Exim 4.32) id 1F6fsT-0007et-LQ for mpls@megatron.ietf.org; Tue, 07 Feb 2006 22:20:23 -0500 Received: from ietf-mx.ietf.org (ietf-mx [132.151.6.1]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id WAA07721 for ; Tue, 7 Feb 2006 22:18:31 -0500 (EST) Received: from szxga03-in.huawei.com ([61.144.161.55] helo=huawei.com) by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1F6g4m-0000PA-U2 for mpls@ietf.org; Tue, 07 Feb 2006 22:33:10 -0500 Received: from huawei.com (szxga03-in [172.24.2.9]) by szxga03-in.huawei.com (iPlanet Messaging Server 5.2 HotFix 1.25 (built Mar 3 2004)) with ESMTP id <0IUC002I1MT1TU@szxga03-in.huawei.com> for mpls@ietf.org; Wed, 08 Feb 2006 11:24:38 +0800 (CST) Received: from szxml02-in ([172.24.1.6]) by szxga03-in.huawei.com (iPlanet Messaging Server 5.2 HotFix 1.25 (built Mar 3 2004)) with ESMTP id <0IUC00I7UMO6OE@szxga03-in.huawei.com> for mpls@ietf.org; Wed, 08 Feb 2006 11:24:37 +0800 (CST) Received: from z40693 ([10.70.77.228]) by szxml02-in.huawei.com (iPlanet Messaging Server 5.2 HotFix 1.25 (built Mar 3 2004)) with ESMTPA id <0IUC00AVQN0PQC@szxml02-in.huawei.com>; Wed, 08 Feb 2006 11:29:13 +0800 (CST) Date: Wed, 08 Feb 2006 11:17:07 +0800 From: Zhang Haiyan Subject: Re: [mpls] LDP Multicast to WG Document To: Erblichs Message-id: <009601c62c5e$27348860$e44d460a@china.huawei.com> MIME-version: 1.0 X-MIMEOLE: Produced By Microsoft MimeOLE V6.00.2800.1165 X-Mailer: Microsoft Outlook Express 6.00.2800.1158 Content-type: text/plain; charset=iso-8859-2 Content-transfer-encoding: 7BIT X-Priority: 3 X-MSMail-priority: Normal References: <20060206125051.3E3BD17B472@SwallowPB.local> <43E7F3CD.ADD76DE0@earthlink.net> X-Spam-Score: 0.0 (/) X-Scan-Signature: 03169bfe4792634a390035a01a6c6d2f Content-Transfer-Encoding: 7BIT Cc: mpls@ietf.org X-BeenThere: mpls@lists.ietf.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Multi-Protocol Label Switching WG List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Sender: mpls-bounces@lists.ietf.org Errors-To: mpls-bounces@lists.ietf.org Mitchell, > 3) 4. Setting up MP2MP LSPs with LDP > > Am I right that we would want the identical > forward and reverse (ack/replies) data flows (directional LSPs) > to follow the same LDP peers in both directions? we could verify > this with a LSP traceroute. > > If both the paths don't traverse the same LDP peers, I could > assume that one direction could have a significantly faster > bandwidth. > > Thus both sides (ingress/egress) of the 2 or more directional > LSPs should attempt to use the same transit LDP peers. Thus, > some form of consistent selection should be available. IMO, when the transit node reveives the downstream Label Map, it allocates label and installs forwarding state for both downstream and upstream, i.e. the two directional LSPs are set up at the same time in the MP2MP Label Map procedures. It ensures that both directions follow the same transit nodes (LDP peers). Regards, Zhang ----- Original Message ----- From: "Erblichs" To: "George Swallow" Cc: Sent: Tuesday, February 07, 2006 9:11 AM Subject: Re: [mpls] LDP Multicast to WG Document > George Swallow, > > I have done little work with P2MP and MP2MP, > so I do not feel correct in voicing my opinion, > however, I would like to ask a few questions. > > Just clarifying a few issues in my mind. Any answers > would be helpful. > > 1) 1.2 Terminology > > With transit and bud LSR types,"directly connected" > is used. Can I assume that basic and extended nbr > peer discovery and establishment both qualify for > "directly connected". > > Because, I only consider the extended with targeted > hello's and have a "grey" understanding of whether > those are always really "directly connected". > > 2) 2.3.1.1. Determining one's 'upstream LSR' > > A node Z that is part of P2MP LSP determines the LDP peer U > which lies on the best path from Z to the root node X. If there are > more than one such LDP peers, only one of them is picked. U is Z's > "Upstream LSR" for . > > Multiple parts: > > "only one of them is picked" > Am I correct that you are picking U equals? > > Why isn't some identifier for the LDP peer used to compare > the multiple LDP peers for the "picking"? > > Why wouldn't you want to have a known result based on a public > algortihm, like highest router-id? > > Why can't more tban one be picked? > > And why wouldn't you want to pick 2 or more and load balance or have > done it because of some fast-reroute policy if one of the selected > "U" fails? > > > 3) 4. Setting up MP2MP LSPs with LDP > > Am I right that we would want the identical > forward and reverse (ack/replies) data flows (directional LSPs) > to follow the same LDP peers in both directions? we could verify > this with a LSP traceroute. > > If both the paths don't traverse the same LDP peers, I could > assume that one direction could have a significantly faster > bandwidth. > > Thus both sides (ingress/egress) of the 2 or more directional > LSPs should attempt to use the same transit LDP peers. Thus, > some form of consistent selection should be available. > > (Clarify: One path of Ingress A to Egress B, and the replies > coming from Ingress B to Egress A, both directional > data flows transitioning either the same set of LDP peers > or a different set. I would assume that they should be the > same set of transit LDP peers.) > > My reason why... > > Thus, If the reply segments take a faster bandwidth LSP and > our data flows are also controlled by TCP, won't the acks > return with less inter segment / packet spacing. This decreased > spacing will force the newer data segments to be bunched even > more (congestion avoidance) than just adding 1 segment per > round trip. > > If the first source/Ingress to Egress data path is faster than > the return, won't we waste the return bandwidth capacity? > > Thus a LSP traceroute should be the same as either initiated > from the Ingress or from the Egress ends of the path. > > You can offline the email if you don't think anyone is > intereted in the answers. > > Thanks, > Mitchell Erblich > ----------------- > > > > > > George Swallow wrote: > > > > It has been requested that > > > > Label Distribution Protocol Extensions for Point-to-Multipoint and > > Multipoint-to-Multipoint Label Switched Paths > > draft-minei-wijnands-mpls-ldp-p2mp-00 > > > > become a MPLS WG document. > > > > Please indicate your support or objections by the end of this week. > > > > Thanks, > > > > ...George > > > > ======================================================================== > > George Swallow Cisco Systems (978) 936-1398 > > 1414 Massachusetts Avenue > > Boxborough, MA 01719 > > > > _______________________________________________ > > mpls mailing list > > mpls@lists.ietf.org > > https://www1.ietf.org/mailman/listinfo/mpls > > _______________________________________________ > mpls mailing list > mpls@lists.ietf.org > https://www1.ietf.org/mailman/listinfo/mpls _______________________________________________ mpls mailing list mpls@lists.ietf.org https://www1.ietf.org/mailman/listinfo/mpls From mpls-bounces@lists.ietf.org Tue Feb 07 23:51:59 2006 Received: from localhost.cnri.reston.va.us ([127.0.0.1] helo=megatron.ietf.org) by megatron.ietf.org with esmtp (Exim 4.32) id 1F6hJ9-0006w2-62; Tue, 07 Feb 2006 23:51:59 -0500 Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org) by megatron.ietf.org with esmtp (Exim 4.32) id 1F6hJ7-0006uS-2J for mpls@megatron.ietf.org; Tue, 07 Feb 2006 23:51:57 -0500 Received: from ietf-mx.ietf.org (ietf-mx [132.151.6.1]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id XAA13211 for ; Tue, 7 Feb 2006 23:49:56 -0500 (EST) Received: from uproxy.gmail.com ([66.249.92.204]) by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1F6hVK-0003DQ-Tx for mpls@ietf.org; Wed, 08 Feb 2006 00:04:36 -0500 Received: by uproxy.gmail.com with SMTP id u2so170867uge for ; Tue, 07 Feb 2006 20:51:36 -0800 (PST) DomainKey-Signature: a=rsa-sha1; q=dns; c=nofws; s=beta; d=gmail.com; h=received:message-id:date:from:to:subject:mime-version:content-type:content-transfer-encoding:content-disposition; b=B2bJ8brxjGgMz3JTF6u6g2LaTPRTIiK0qqW4HmBIOxJrxod1qtR0XVizW1xcMjpQWJjn3C5DE12Yl2YH47BkYQ1rHtuIZSud36G28cOaIVsTibuRW+LR5QtXTVK0SoeLZI/Av8JIwP7EFEFFMlSNOtfUo+VaLTSonlKghTdaju8= Received: by 10.49.34.11 with SMTP id m11mr1821270nfj; Tue, 07 Feb 2006 20:51:35 -0800 (PST) Received: by 10.48.14.6 with HTTP; Tue, 7 Feb 2006 20:51:35 -0800 (PST) Message-ID: Date: Wed, 8 Feb 2006 12:51:35 +0800 From: Bob Anders To: mpls@ietf.org MIME-Version: 1.0 Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: quoted-printable Content-Disposition: inline X-Spam-Score: 2.2 (++) X-Scan-Signature: d6b246023072368de71562c0ab503126 Content-Transfer-Encoding: quoted-printable Cc: Subject: [mpls] MPLS Header Compression X-BeenThere: mpls@lists.ietf.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Multi-Protocol Label Switching WG List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Sender: mpls-bounces@lists.ietf.org Errors-To: mpls-bounces@lists.ietf.org Dear Group, I came across the problem when the header, due to its arbitrary length, can exceed the MTU of the whole packet and was looking into MPLS header compression schemes. Dealing for not too long with MPLS, I have seen from the mailing list archive that there were some attempts to solve this problem, with discussions around 2000 (draft-berger-mpls-hdr-comp-00.txt, draft-swallow-mpls-simple-hdr-compress-00.txt) and 2003. But I couldn't find that one of these drafts made it to a RFC document. Could someone help me with what the current status/consensus regarding header compression in the MPLS community is? How is it solved or implemented (if any)? You don't have to tell stories, any RFC document, paper or link is fine... Thanks, Bob _______________________________________________ mpls mailing list mpls@lists.ietf.org https://www1.ietf.org/mailman/listinfo/mpls From mpls-bounces@lists.ietf.org Wed Feb 08 05:49:15 2006 Received: from localhost.cnri.reston.va.us ([127.0.0.1] helo=megatron.ietf.org) by megatron.ietf.org with esmtp (Exim 4.32) id 1F6mst-0005hD-7h; Wed, 08 Feb 2006 05:49:15 -0500 Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org) by megatron.ietf.org with esmtp (Exim 4.32) id 1F6msr-0005gJ-5b for mpls@megatron.ietf.org; Wed, 08 Feb 2006 05:49:13 -0500 Received: from ietf-mx.ietf.org (ietf-mx [132.151.6.1]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id FAA09546 for ; Wed, 8 Feb 2006 05:47:22 -0500 (EST) Received: from colo-dns-ext2.juniper.net ([207.17.137.64]) by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1F6n5G-0007Jz-7c for mpls@ietf.org; Wed, 08 Feb 2006 06:02:05 -0500 Received: from merlot.juniper.net (merlot.juniper.net [172.17.27.10]) by colo-dns-ext2.juniper.net (8.12.3/8.12.3) with ESMTP id k18Amq1Z075453; Wed, 8 Feb 2006 02:48:52 -0800 (PST) (envelope-from yakov@juniper.net) Received: from juniper.net (sapphire.juniper.net [172.17.28.108]) by merlot.juniper.net (8.11.3/8.11.3) with ESMTP id k18Amq592996; Wed, 8 Feb 2006 02:48:52 -0800 (PST) (envelope-from yakov@juniper.net) Message-Id: <200602081048.k18Amq592996@merlot.juniper.net> To: George Swallow Subject: Re: [mpls] LDP Multicast to WG Document In-Reply-To: Your message of "Mon, 06 Feb 2006 07:50:51 EST." <20060206125051.3E3BD17B472@SwallowPB.local> MIME-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Content-ID: <73551.1139395732.1@juniper.net> Date: Wed, 08 Feb 2006 02:48:52 -0800 From: Yakov Rekhter X-Spam-Score: 0.0 (/) X-Scan-Signature: cf4fa59384e76e63313391b70cd0dd25 Cc: mpls@ietf.org X-BeenThere: mpls@lists.ietf.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Multi-Protocol Label Switching WG List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Sender: mpls-bounces@lists.ietf.org Errors-To: mpls-bounces@lists.ietf.org George, > It has been requested that > > Label Distribution Protocol Extensions for Point-to-Multipoint and > Multipoint-to-Multipoint Label Switched Paths > draft-minei-wijnands-mpls-ldp-p2mp-00 > > become a MPLS WG document. > > Please indicate your support or objections by the end of this week. Support. Yakov. _______________________________________________ mpls mailing list mpls@lists.ietf.org https://www1.ietf.org/mailman/listinfo/mpls From mpls-bounces@lists.ietf.org Wed Feb 08 05:54:26 2006 Received: from localhost.cnri.reston.va.us ([127.0.0.1] helo=megatron.ietf.org) by megatron.ietf.org with esmtp (Exim 4.32) id 1F6mxu-0006ha-2j; Wed, 08 Feb 2006 05:54:26 -0500 Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org) by megatron.ietf.org with esmtp (Exim 4.32) id 1F6mxn-0006bu-Nh for mpls@megatron.ietf.org; Wed, 08 Feb 2006 05:54:22 -0500 Received: from ietf-mx.ietf.org (ietf-mx [132.151.6.1]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id FAA09953 for ; Wed, 8 Feb 2006 05:52:36 -0500 (EST) Received: from colo-dns-ext2.juniper.net ([207.17.137.64]) by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1F6nAM-0007UB-6D for mpls@ietf.org; Wed, 08 Feb 2006 06:07:19 -0500 Received: from merlot.juniper.net (merlot.juniper.net [172.17.27.10]) by colo-dns-ext2.juniper.net (8.12.3/8.12.3) with ESMTP id k18As81Z075497; Wed, 8 Feb 2006 02:54:08 -0800 (PST) (envelope-from yakov@juniper.net) Received: from juniper.net (sapphire.juniper.net [172.17.28.108]) by merlot.juniper.net (8.11.3/8.11.3) with ESMTP id k18As4593622; Wed, 8 Feb 2006 02:54:08 -0800 (PST) (envelope-from yakov@juniper.net) Message-Id: <200602081054.k18As4593622@merlot.juniper.net> To: Loa Andersson Subject: Re: [mpls] draft-raggarwa-mpls-ldp-upstream-00 for wg doc? In-Reply-To: Your message of "Fri, 03 Feb 2006 17:14:03 +0100." <43E3814B.80503@pi.se> MIME-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Content-ID: <73800.1139396044.1@juniper.net> Date: Wed, 08 Feb 2006 02:54:04 -0800 From: Yakov Rekhter X-Spam-Score: 0.0 (/) X-Scan-Signature: 7a6398bf8aaeabc7a7bb696b6b0a2aad Cc: mpls@ietf.org X-BeenThere: mpls@lists.ietf.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Multi-Protocol Label Switching WG List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Sender: mpls-bounces@lists.ietf.org Errors-To: mpls-bounces@lists.ietf.org Loa, > All, > > the authors of draft-raggarwa-mpls-ldp-upstream-00 > has requested that it is made a working group document. > > Please review, comment and respond to the working group mailing > list if you support it becoming a wg or not. Support. Yakov. _______________________________________________ mpls mailing list mpls@lists.ietf.org https://www1.ietf.org/mailman/listinfo/mpls From mpls-bounces@lists.ietf.org Wed Feb 08 05:54:59 2006 Received: from localhost.cnri.reston.va.us ([127.0.0.1] helo=megatron.ietf.org) by megatron.ietf.org with esmtp (Exim 4.32) id 1F6myR-0006si-NM; Wed, 08 Feb 2006 05:54:59 -0500 Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org) by megatron.ietf.org with esmtp (Exim 4.32) id 1F6myP-0006rt-T8 for mpls@megatron.ietf.org; Wed, 08 Feb 2006 05:54:57 -0500 Received: from ietf-mx.ietf.org (ietf-mx [132.151.6.1]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id FAA10051 for ; Wed, 8 Feb 2006 05:53:14 -0500 (EST) Received: from colo-dns-ext1.juniper.net ([207.17.137.57]) by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1F6nAx-0007WG-Mb for mpls@ietf.org; Wed, 08 Feb 2006 06:07:58 -0500 Received: from merlot.juniper.net (merlot.juniper.net [172.17.27.10]) by colo-dns-ext1.juniper.net (8.11.3/8.9.3) with ESMTP id k18AsfX16209; Wed, 8 Feb 2006 02:54:41 -0800 (PST) (envelope-from yakov@juniper.net) Received: from juniper.net (sapphire.juniper.net [172.17.28.108]) by merlot.juniper.net (8.11.3/8.11.3) with ESMTP id k18Asa593672; Wed, 8 Feb 2006 02:54:36 -0800 (PST) (envelope-from yakov@juniper.net) Message-Id: <200602081054.k18Asa593672@merlot.juniper.net> To: Loa Andersson Subject: Re: [mpls] draft-raggarwa-mpls-rsvp-upstream-00 for wg doc? In-Reply-To: Your message of "Fri, 03 Feb 2006 17:16:21 +0100." <43E381D5.8020008@pi.se> MIME-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Content-ID: <73810.1139396076.1@juniper.net> Date: Wed, 08 Feb 2006 02:54:36 -0800 From: Yakov Rekhter X-Spam-Score: 0.0 (/) X-Scan-Signature: 7a6398bf8aaeabc7a7bb696b6b0a2aad Cc: mpls@ietf.org X-BeenThere: mpls@lists.ietf.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Multi-Protocol Label Switching WG List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Sender: mpls-bounces@lists.ietf.org Errors-To: mpls-bounces@lists.ietf.org Loa, > All, > > the authors of draft-raggarwa-mpls-rsvp-upstream-00 > has requested that it is made a working group document. > > Please review, comment and respond to the working group mailing > list if you support it becoming a wg or not. Support. Yakov. _______________________________________________ mpls mailing list mpls@lists.ietf.org https://www1.ietf.org/mailman/listinfo/mpls From mpls-bounces@lists.ietf.org Wed Feb 08 08:23:00 2006 Received: from localhost.cnri.reston.va.us ([127.0.0.1] helo=megatron.ietf.org) by megatron.ietf.org with esmtp (Exim 4.32) id 1F6pHg-0005E0-BG; Wed, 08 Feb 2006 08:23:00 -0500 Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org) by megatron.ietf.org with esmtp (Exim 4.32) id 1F6pHd-00053f-2a; Wed, 08 Feb 2006 08:22:57 -0500 Received: from ietf-mx.ietf.org (ietf-mx [132.151.6.1]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id IAA21717; Wed, 8 Feb 2006 08:21:05 -0500 (EST) Received: from mail121.messagelabs.com ([216.82.241.195]) by ietf-mx.ietf.org with smtp (Exim 4.43) id 1F6pU1-0004MT-59; Wed, 08 Feb 2006 08:35:48 -0500 X-VirusChecked: Checked X-Env-Sender: gash@att.com X-Msg-Ref: server-6.tower-121.messagelabs.com!1139404934!7489557!6 X-StarScan-Version: 5.5.9.1; banners=-,-,- X-Originating-IP: [134.24.146.4] Received: (qmail 1549 invoked from network); 8 Feb 2006 13:22:32 -0000 Received: from unknown (HELO attrh3i.attrh.att.com) (134.24.146.4) by server-6.tower-121.messagelabs.com with SMTP; 8 Feb 2006 13:22:32 -0000 Received: from kcclust06evs1.ugd.att.com (135.38.164.89) by attrh3i.attrh.att.com (7.2.052) id 43D3BB520024322E; Wed, 8 Feb 2006 08:22:32 -0500 X-MimeOLE: Produced By Microsoft Exchange V6.5.7226.0 Content-class: urn:content-classes:message MIME-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: quoted-printable Subject: RE: [mpls] MPLS Header Compression Date: Wed, 8 Feb 2006 07:22:31 -0600 Message-ID: <9473683187ADC049A855ED2DA739ABCA09FA9ABA@KCCLUST06EVS1.ugd.att.com> Thread-Topic: [mpls] MPLS Header Compression Thread-Index: AcYsa7x6Ep2phg9ITaKlWzOI0dlhtQARmhjQ From: "Ash, Gerald R \(Jerry\), ALABS" To: "Bob Anders" , X-Spam-Score: 0.0 (/) X-Scan-Signature: 50a516d93fd399dc60588708fd9a3002 Content-Transfer-Encoding: quoted-printable Cc: IETF AVT WG X-BeenThere: mpls@lists.ietf.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Multi-Protocol Label Switching WG List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Sender: mpls-bounces@lists.ietf.org Errors-To: mpls-bounces@lists.ietf.org Bob, Header compression over MPLS is being worked in the AVT working group. The requirements are given in RFC 4247 http://www.ietf.org/rfc/rfc4247.txt?number=3D4247. The protocol extensions work is in progress, the latest draft is at http://ietf.org/internet-drafts/draft-ietf-avt-hc-over-mpls-protocol-02. txt. Please let us know if you have any comments or questions (on the AVT list). Thanks, Jerry=20 -----Original Message----- From: mpls-bounces@lists.ietf.org [mailto:mpls-bounces@lists.ietf.org] On Behalf Of Bob Anders Sent: Tuesday, February 07, 2006 11:52 PM To: mpls@ietf.org Subject: [mpls] MPLS Header Compression Dear Group, I came across the problem when the header, due to its arbitrary length, can exceed the MTU of the whole packet and was looking into MPLS header compression schemes. Dealing for not too long with MPLS, I have seen from the mailing list archive that there were some attempts to solve this problem, with discussions around 2000 (draft-berger-mpls-hdr-comp-00.txt, draft-swallow-mpls-simple-hdr-compress-00.txt) and 2003. But I couldn't find that one of these drafts made it to a RFC document. Could someone help me with what the current status/consensus regarding header compression in the MPLS community is? How is it solved or implemented (if any)? You don't have to tell stories, any RFC document, paper or link is fine... Thanks, Bob _______________________________________________ mpls mailing list mpls@lists.ietf.org https://www1.ietf.org/mailman/listinfo/mpls _______________________________________________ mpls mailing list mpls@lists.ietf.org https://www1.ietf.org/mailman/listinfo/mpls From mpls-bounces@lists.ietf.org Wed Feb 08 11:13:52 2006 Received: from localhost.cnri.reston.va.us ([127.0.0.1] helo=megatron.ietf.org) by megatron.ietf.org with esmtp (Exim 4.32) id 1F6rx2-0004No-G8; Wed, 08 Feb 2006 11:13:52 -0500 Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org) by megatron.ietf.org with esmtp (Exim 4.32) id 1F6rx0-0004Mz-C7 for mpls@megatron.ietf.org; Wed, 08 Feb 2006 11:13:50 -0500 Received: from ietf-mx.ietf.org (ietf-mx [132.151.6.1]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id LAA05999 for ; Wed, 8 Feb 2006 11:11:59 -0500 (EST) Received: from protext01.itu.ch ([156.106.192.41]) by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1F6s9U-0002HS-2v for mpls@ietf.org; Wed, 08 Feb 2006 11:26:45 -0500 Received: from protext01.itu.ch ([156.106.192.41]) by protext01.itu.ch with Microsoft SMTPSVC(5.0.2195.6713); Wed, 8 Feb 2006 17:13:28 +0100 Received: From mail5.itu.ch ([156.106.192.21]) by protext01.itu.ch (WebShield SMTP v4.5 MR1a); id 1139415207582; Wed, 8 Feb 2006 17:13:27 +0100 Received: from Puppy ([156.106.205.30]) by mail5.itu.ch (8.13.5/8.13.5) with SMTP id k18GDOuS145215 for ; Wed, 8 Feb 2006 17:13:27 +0100 (MET) Message-ID: <078f01c62ccb$27da02a0$49cc6a9c@Puppy> From: "Adrian Farrel" To: Date: Wed, 8 Feb 2006 16:17:14 -0000 MIME-Version: 1.0 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: 7bit X-Priority: 3 X-MSMail-Priority: Normal X-Mailer: Microsoft Outlook Express 6.00.2800.1158 X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2800.1165 X-Greylist: Sender IP whitelisted, not delayed by milter-greylist-2.0.2 (mail5.itu.ch [156.106.192.21]); Wed, 08 Feb 2006 17:13:27 +0100 (MET) X-OriginalArrivalTime: 08 Feb 2006 16:13:28.0269 (UTC) FILETIME=[98A64FD0:01C62CCA] X-Spam-Score: 0.0 (/) X-Scan-Signature: 08170828343bcf1325e4a0fb4584481c Content-Transfer-Encoding: 7bit Cc: Subject: [mpls] CCAMP last call on draft-ietf-ccamp-automesh-01.txt X-BeenThere: mpls@lists.ietf.org X-Mailman-Version: 2.1.5 Precedence: list Reply-To: Adrian Farrel List-Id: Multi-Protocol Label Switching WG List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Sender: mpls-bounces@lists.ietf.org Errors-To: mpls-bounces@lists.ietf.org Hi, Please be aware that CCAMP is holding a WG last call on draft-ietf-ccamp-automesh-01.txt This I-D may be of particular interest for people implementing MPLS-TE networks. Comments should be sent to the CCAMP mailing list. The last call ends on 22nd Feb. Thanks, Adrian _______________________________________________ mpls mailing list mpls@lists.ietf.org https://www1.ietf.org/mailman/listinfo/mpls From mpls-bounces@lists.ietf.org Thu Feb 09 01:57:49 2006 Received: from localhost.cnri.reston.va.us ([127.0.0.1] helo=megatron.ietf.org) by megatron.ietf.org with esmtp (Exim 4.32) id 1F75kS-00087y-VC; Thu, 09 Feb 2006 01:57:48 -0500 Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org) by megatron.ietf.org with esmtp (Exim 4.32) id 1F75kQ-000875-SL for mpls@megatron.ietf.org; Thu, 09 Feb 2006 01:57:47 -0500 Received: from ietf-mx.ietf.org (ietf-mx [132.151.6.1]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id BAA22588 for ; Thu, 9 Feb 2006 01:55:57 -0500 (EST) Received: from szxga01-in.huawei.com ([61.144.161.53] helo=huawei.com) by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1F75x3-0002Jt-CX for mpls@ietf.org; Thu, 09 Feb 2006 02:10:49 -0500 Received: from huawei.com (szxga01-in [172.24.2.3]) by szxga01-in.huawei.com (iPlanet Messaging Server 5.2 HotFix 1.25 (built Mar 3 2004)) with ESMTP id <0IUE00IO7RQ6JJ@szxga01-in.huawei.com> for mpls@ietf.org; Thu, 09 Feb 2006 15:06:06 +0800 (CST) Received: from l48253 ([10.111.12.100]) by szxga01-in.huawei.com (iPlanet Messaging Server 5.2 HotFix 1.25 (built Mar 3 2004)) with ESMTPA id <0IUE00HBORQ5K1@szxga01-in.huawei.com> for mpls@ietf.org; Thu, 09 Feb 2006 15:06:06 +0800 (CST) Date: Thu, 09 Feb 2006 14:56:07 +0800 From: liushuying Subject: Re: [mpls] LDP Multicast to WG Document To: swallow@cisco.com, ina@juniper.net, ice@cisco.com Message-id: <006201c62d45$e7142bd0$640c6f0a@china.huawei.com> MIME-version: 1.0 X-MIMEOLE: Produced By Microsoft MimeOLE V6.00.2900.2180 X-Mailer: Microsoft Outlook Express 6.00.2900.2180 Content-type: text/plain; charset=iso-8859-1 Content-transfer-encoding: 7BIT X-Priority: 3 X-MSMail-priority: Normal References: <0IUA002ZH0BV7M@szxga02-in.huawei.com> X-Spam-Score: 0.0 (/) X-Scan-Signature: 244a2fd369eaf00ce6820a760a3de2e8 Content-Transfer-Encoding: 7BIT Cc: mpls@ietf.org X-BeenThere: mpls@lists.ietf.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Multi-Protocol Label Switching WG List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Sender: mpls-bounces@lists.ietf.org Errors-To: mpls-bounces@lists.ietf.org Hi folks, I support this draft becoming a WG document. However,i am about to ask a question. 1) 2.3.2.4. Upstream LSR change If, for a given node Z participating in a P2MP LSP , the upstream LSR changes, say from U to U', then Z MUST update its forwarding state by deleting the state for label L, allocating a new label, L', for , and installing the forwarding state for L'. In addition Z MUST send a Label Map to U' and send a Label Withdraw to U. The question: When a large quantity of P2MP LSPs exists in MPLS networks, if unicast routing information changes, there may be many LSRs whose upstream LSRs have changed in every P2MP LSP, each of them sends a Label Withdraw message to its old upstream LSR and a Label Map message to its new upstream LSR at the same time, so the load of every LSR will enhance sharply and last for a long time. As a result, the time of traffic disruption in every P2MP LSP will last for a long time, and so many packets will be lost. Thanks Shuying Liu ----- Original Message ----- > Date: Mon, 06 Feb 2006 07:50:51 -0500 > From: George Swallow > Subject: [mpls] LDP Multicast to WG Document > To: mpls@ietf.org > Message-ID: <20060206125051.3E3BD17B472@SwallowPB.local> > > It has been requested that > > Label Distribution Protocol Extensions for Point-to-Multipoint and > Multipoint-to-Multipoint Label Switched Paths > draft-minei-wijnands-mpls-ldp-p2mp-00 > > become a MPLS WG document. > > Please indicate your support or objections by the end of this week. > > Thanks, > > ...George > > ======================================================================== > George Swallow Cisco Systems (978) 936-1398 > 1414 Massachusetts Avenue > Boxborough, MA 01719 > > > > > > ------------------------------ > > _______________________________________________ > mpls mailing list > mpls@lists.ietf.org > https://www1.ietf.org/mailman/listinfo/mpls > _______________________________________________ mpls mailing list mpls@lists.ietf.org https://www1.ietf.org/mailman/listinfo/mpls From mpls-bounces@lists.ietf.org Thu Feb 09 04:13:23 2006 Received: from localhost.cnri.reston.va.us ([127.0.0.1] helo=megatron.ietf.org) by megatron.ietf.org with esmtp (Exim 4.32) id 1F77rd-00089o-1t; Thu, 09 Feb 2006 04:13:21 -0500 Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org) by megatron.ietf.org with esmtp (Exim 4.32) id 1F77qP-0007am-4Z for mpls@megatron.ietf.org; Thu, 09 Feb 2006 04:12:05 -0500 Received: from ietf-mx.ietf.org (ietf-mx [132.151.6.1]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id EAA01585 for ; Thu, 9 Feb 2006 04:10:17 -0500 (EST) Received: from odd-brew.cisco.com ([144.254.15.119] helo=av-tac-bru.cisco.com) by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1F7834-0007LY-ON for mpls@ietf.org; Thu, 09 Feb 2006 04:25:12 -0500 X-TACSUNS: Virus Scanned Received: from strange-brew.cisco.com (localhost [127.0.0.1]) by av-tac-bru.cisco.com (8.11.7p1+Sun/8.11.7) with ESMTP id k199BQU21865; Thu, 9 Feb 2006 10:11:26 +0100 (CET) Received: from [81.254.5.157] (ams-clip-vpn-dhcp268.cisco.com [10.61.65.12]) by strange-brew.cisco.com (8.11.7p1+Sun/8.11.7) with ESMTP id k199BNC27796; Thu, 9 Feb 2006 10:11:23 +0100 (CET) In-Reply-To: <006201c62d45$e7142bd0$640c6f0a@china.huawei.com> References: <0IUA002ZH0BV7M@szxga02-in.huawei.com> <006201c62d45$e7142bd0$640c6f0a@china.huawei.com> Mime-Version: 1.0 (Apple Message framework v623) Content-Type: text/plain; charset=US-ASCII; delsp=yes; format=flowed Message-Id: <383c087519d13ce17272a63930bb7581@cisco.com> Content-Transfer-Encoding: 7bit From: IJsbrand Wijnands Subject: Re: [mpls] LDP Multicast to WG Document Date: Thu, 9 Feb 2006 10:11:21 +0100 To: liushuying X-Mailer: Apple Mail (2.623) X-Spam-Score: 0.0 (/) X-Scan-Signature: 73734d43604d52d23b3eba644a169745 Content-Transfer-Encoding: 7bit Cc: mpls@ietf.org X-BeenThere: mpls@lists.ietf.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Multi-Protocol Label Switching WG List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Sender: mpls-bounces@lists.ietf.org Errors-To: mpls-bounces@lists.ietf.org Hi Shuying, We have some ideas on how to minimize the traffic loss during switchover, but I'm not sure if we can prevent it without some kind of FRR mechanism. Thx, Ice. BTW, I support make this a WG document. On Feb 9, 2006, at 7:56 AM, liushuying wrote: > Hi folks, > I support this draft becoming a WG document. > > However,i am about to ask a question. > > 1) 2.3.2.4. Upstream LSR change > > If, for a given node Z participating in a P2MP LSP , the > upstream LSR changes, say from U to U', then Z MUST update its > forwarding state by deleting the state for label L, allocating a new > label, L', for , and installing the forwarding state for L'. > In > addition Z MUST send a Label Map to U' and send a Label > Withdraw to U. > > The question: > When a large quantity of P2MP LSPs exists in MPLS networks, > if unicast routing information changes, there may be many LSRs > whose upstream LSRs have changed in every P2MP LSP, each of them > sends a Label Withdraw message > to its old upstream LSR and a Label Map message to its new upstream > LSR at the same time, > so the load of every LSR will enhance sharply and last for a long > time. > As a result, the time of traffic disruption in every P2MP LSP will > last for a long time, > and so many packets will be lost. > > Thanks > Shuying Liu > > > ----- Original Message ----- >> Date: Mon, 06 Feb 2006 07:50:51 -0500 >> From: George Swallow >> Subject: [mpls] LDP Multicast to WG Document >> To: mpls@ietf.org >> Message-ID: <20060206125051.3E3BD17B472@SwallowPB.local> >> >> It has been requested that >> >> Label Distribution Protocol Extensions for Point-to-Multipoint and >> Multipoint-to-Multipoint Label Switched Paths >> draft-minei-wijnands-mpls-ldp-p2mp-00 >> >> become a MPLS WG document. >> >> Please indicate your support or objections by the end of this week. >> >> Thanks, >> >> ...George >> >> ====================================================================== >> == >> George Swallow Cisco Systems (978) >> 936-1398 >> 1414 Massachusetts Avenue >> Boxborough, MA 01719 >> >> >> >> >> >> ------------------------------ >> >> _______________________________________________ >> mpls mailing list >> mpls@lists.ietf.org >> https://www1.ietf.org/mailman/listinfo/mpls >> _______________________________________________ mpls mailing list mpls@lists.ietf.org https://www1.ietf.org/mailman/listinfo/mpls From mpls-bounces@lists.ietf.org Thu Feb 09 05:51:29 2006 Received: from localhost.cnri.reston.va.us ([127.0.0.1] helo=megatron.ietf.org) by megatron.ietf.org with esmtp (Exim 4.32) id 1F79Oa-0004oV-Uh; Thu, 09 Feb 2006 05:51:28 -0500 Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org) by megatron.ietf.org with esmtp (Exim 4.32) id 1F79OY-0004oG-PA for mpls@megatron.ietf.org; Thu, 09 Feb 2006 05:51:26 -0500 Received: from ietf-mx.ietf.org (ietf-mx [132.151.6.1]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id FAA08622 for ; Thu, 9 Feb 2006 05:49:43 -0500 (EST) Received: from web8604.mail.in.yahoo.com ([202.43.219.79]) by ietf-mx.ietf.org with smtp (Exim 4.43) id 1F79bJ-000294-Gk for mpls@ietf.org; Thu, 09 Feb 2006 06:04:39 -0500 Received: (qmail 90785 invoked by uid 60001); 9 Feb 2006 10:51:07 -0000 DomainKey-Signature: a=rsa-sha1; q=dns; c=nofws; s=s1024; d=yahoo.co.in; h=Message-ID:Received:Date:From:Subject:To:MIME-Version:Content-Type:Content-Transfer-Encoding; b=KPx2j4mRsZlWAnTDKSR996w4amH7Mbx9Je3lQBJWn7gevNTOqkLPJZzhaVdPkk3VKurcCrsaXZluuYhp8+NUGAo7biUjOAVM9QYTCCuVlIRcy8/s9hwLcGEWkBAlT4JjvKaG1ULOu9/RfEYO4AxKXnf9M+CsvfDSj/cMYuHyAcs= ; Message-ID: <20060209105106.90783.qmail@web8604.mail.in.yahoo.com> Received: from [203.197.74.148] by web8604.mail.in.yahoo.com via HTTP; Thu, 09 Feb 2006 10:51:06 GMT Date: Thu, 9 Feb 2006 10:51:06 +0000 (GMT) From: Aryan Thakkar To: mplslist , MPLS List MIME-Version: 1.0 Content-Type: text/plain; charset=iso-8859-1 X-Spam-Score: 0.9 (/) X-Scan-Signature: 856eb5f76e7a34990d1d457d8e8e5b7f Content-Transfer-Encoding: quoted-printable X-MIME-Autoconverted: from 8bit to quoted-printable by ietf.org id FAA08622 Cc: Subject: [mpls] Qeueing delays X-BeenThere: mpls@lists.ietf.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Multi-Protocol Label Switching WG List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Sender: mpls-bounces@lists.ietf.org Errors-To: mpls-bounces@lists.ietf.org Hi, I would like to know whether there is any MIB available for polling queuing delays.. I want to retrieve the information regarding the queuing delays on each router. How do I go about doing that? Please help me regarding this=85 Regards=85. Aryan. =09 __________________________________________________________=20 Yahoo! India Matrimony: Find your partner now. Go to http://yahoo.shaadi.= com _______________________________________________ mpls mailing list mpls@lists.ietf.org https://www1.ietf.org/mailman/listinfo/mpls From mpls-bounces@lists.ietf.org Thu Feb 09 05:51:49 2006 Received: from localhost.cnri.reston.va.us ([127.0.0.1] helo=megatron.ietf.org) by megatron.ietf.org with esmtp (Exim 4.32) id 1F79Ov-0004rP-J6; Thu, 09 Feb 2006 05:51:49 -0500 Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org) by megatron.ietf.org with esmtp (Exim 4.32) id 1F79Ot-0004qY-AA for mpls@megatron.ietf.org; Thu, 09 Feb 2006 05:51:47 -0500 Received: from web8604.mail.in.yahoo.com (web8604.mail.in.yahoo.com [202.43.219.79]) by ietf.org (8.9.1a/8.9.1a) with SMTP id FAA08639 for ; Thu, 9 Feb 2006 05:50:02 -0500 (EST) Received: (qmail 90785 invoked by uid 60001); 9 Feb 2006 10:51:07 -0000 DomainKey-Signature: a=rsa-sha1; q=dns; c=nofws; s=s1024; d=yahoo.co.in; h=Message-ID:Received:Date:From:Subject:To:MIME-Version:Content-Type:Content-Transfer-Encoding; b=KPx2j4mRsZlWAnTDKSR996w4amH7Mbx9Je3lQBJWn7gevNTOqkLPJZzhaVdPkk3VKurcCrsaXZluuYhp8+NUGAo7biUjOAVM9QYTCCuVlIRcy8/s9hwLcGEWkBAlT4JjvKaG1ULOu9/RfEYO4AxKXnf9M+CsvfDSj/cMYuHyAcs= ; Message-ID: <20060209105106.90783.qmail@web8604.mail.in.yahoo.com> Received: from [203.197.74.148] by web8604.mail.in.yahoo.com via HTTP; Thu, 09 Feb 2006 10:51:06 GMT Date: Thu, 9 Feb 2006 10:51:06 +0000 (GMT) From: Aryan Thakkar To: mplslist , MPLS List MIME-Version: 1.0 Content-Type: text/plain; charset=iso-8859-1 Content-Transfer-Encoding: quoted-printable X-MIME-Autoconverted: from 8bit to quoted-printable by ietf.org id FAA08639 Cc: Subject: [mpls] Qeueing delays X-BeenThere: mpls@lists.ietf.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Multi-Protocol Label Switching WG List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Sender: mpls-bounces@lists.ietf.org Errors-To: mpls-bounces@lists.ietf.org Hi, I would like to know whether there is any MIB available for polling queuing delays.. I want to retrieve the information regarding the queuing delays on each router. How do I go about doing that? Please help me regarding this=85 Regards=85. Aryan. =09 __________________________________________________________=20 Yahoo! India Matrimony: Find your partner now. Go to http://yahoo.shaadi.= com _______________________________________________ mpls mailing list mpls@lists.ietf.org https://www1.ietf.org/mailman/listinfo/mpls From mpls-bounces@lists.ietf.org Sun Feb 12 16:34:57 2006 Received: from localhost.cnri.reston.va.us ([127.0.0.1] helo=megatron.ietf.org) by megatron.ietf.org with esmtp (Exim 4.32) id 1F8Orx-00085d-JN; Sun, 12 Feb 2006 16:34:57 -0500 Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org) by megatron.ietf.org with esmtp (Exim 4.32) id 1F8Orv-00085Y-HM for mpls@megatron.ietf.org; Sun, 12 Feb 2006 16:34:55 -0500 Received: from ietf-mx.ietf.org (ietf-mx [132.151.6.1]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id QAA15714 for ; Sun, 12 Feb 2006 16:33:11 -0500 (EST) Received: from borg.juniper.net ([207.17.137.119]) by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1F8P5O-0006qp-R4 for mpls@ietf.org; Sun, 12 Feb 2006 16:48:52 -0500 Received: from unknown (HELO alpha.jnpr.net) ([172.24.18.126]) by borg.juniper.net with ESMTP; 12 Feb 2006 13:34:45 -0800 X-BrightmailFiltered: true X-Brightmail-Tracker: AAAAAA== X-IronPort-AV: i="4.02,105,1139212800"; d="scan'208"; a="529338157:sNHT24573852" Received: from sapphire.juniper.net ([172.17.28.108]) by alpha.jnpr.net over TLS secured channel with Microsoft SMTPSVC(6.0.3790.1830); Sun, 12 Feb 2006 13:34:44 -0800 Date: Sun, 12 Feb 2006 13:34:44 -0800 (PST) From: Rahul Aggarwal To: George Swallow Subject: Re: [mpls] LDP Multicast to WG Document In-Reply-To: <20060206125051.3E3BD17B472@SwallowPB.local> Message-ID: <20060212133428.A73485@sapphire.juniper.net> References: <20060206125051.3E3BD17B472@SwallowPB.local> MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII X-OriginalArrivalTime: 12 Feb 2006 21:34:44.0771 (UTC) FILETIME=[23FE1730:01C6301C] X-Spam-Score: 0.0 (/) X-Scan-Signature: 52e1467c2184c31006318542db5614d5 Cc: mpls@ietf.org X-BeenThere: mpls@lists.ietf.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Multi-Protocol Label Switching WG List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Sender: mpls-bounces@lists.ietf.org Errors-To: mpls-bounces@lists.ietf.org Hi George, On Mon, 6 Feb 2006, George Swallow wrote: > It has been requested that > > Label Distribution Protocol Extensions for Point-to-Multipoint and > Multipoint-to-Multipoint Label Switched Paths > draft-minei-wijnands-mpls-ldp-p2mp-00 > > become a MPLS WG document. > > Please indicate your support or objections by the end of this week. > Support. rahul > Thanks, > > ...George > > ======================================================================== > George Swallow Cisco Systems (978) 936-1398 > 1414 Massachusetts Avenue > Boxborough, MA 01719 > > > > _______________________________________________ > mpls mailing list > mpls@lists.ietf.org > https://www1.ietf.org/mailman/listinfo/mpls > _______________________________________________ mpls mailing list mpls@lists.ietf.org https://www1.ietf.org/mailman/listinfo/mpls From mpls-bounces@lists.ietf.org Sun Feb 12 19:19:34 2006 Received: from localhost.cnri.reston.va.us ([127.0.0.1] helo=megatron.ietf.org) by megatron.ietf.org with esmtp (Exim 4.32) id 1F8RRG-0004TM-2t; Sun, 12 Feb 2006 19:19:34 -0500 Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org) by megatron.ietf.org with esmtp (Exim 4.32) id 1F8RRF-0004TH-0D for mpls@megatron.ietf.org; Sun, 12 Feb 2006 19:19:33 -0500 Received: from ietf-mx.ietf.org (ietf-mx [132.151.6.1]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id TAA25953 for ; Sun, 12 Feb 2006 19:17:47 -0500 (EST) Received: from p-mail1.rd.francetelecom.com ([195.101.245.15]) by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1F8Rek-0002qp-D4 for mpls@ietf.org; Sun, 12 Feb 2006 19:33:30 -0500 Received: from ftrdmel10.rd.francetelecom.fr ([10.193.117.156]) by ftrdsmtp2.rd.francetelecom.fr with Microsoft SMTPSVC(6.0.3790.1830); Mon, 13 Feb 2006 01:19:26 +0100 Received: from wintermute ([10.193.4.45]) by ftrdmel10.rd.francetelecom.fr with Microsoft SMTPSVC(6.0.3790.211); Sun, 12 Feb 2006 18:11:41 +0100 Subject: Re: [mpls] LDP Multicast to WG Document From: Thomas Morin To: IJsbrand Wijnands In-Reply-To: <383c087519d13ce17272a63930bb7581@cisco.com> References: <0IUA002ZH0BV7M@szxga02-in.huawei.com> <006201c62d45$e7142bd0$640c6f0a@china.huawei.com> <383c087519d13ce17272a63930bb7581@cisco.com> Content-Type: text/plain Organization: France Telecom R&D Date: Fri, 10 Feb 2006 22:52:51 +0100 Message-Id: <1139608371.5389.146.camel@wintermute> Mime-Version: 1.0 X-Mailer: Evolution 2.4.2.1 Content-Transfer-Encoding: 7bit X-OriginalArrivalTime: 12 Feb 2006 17:11:41.0386 (UTC) FILETIME=[645CAAA0:01C62FF7] X-Spam-Score: 0.0 (/) X-Scan-Signature: a8a20a483a84f747e56475e290ee868e Content-Transfer-Encoding: 7bit Cc: mpls@ietf.org X-BeenThere: mpls@lists.ietf.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Multi-Protocol Label Switching WG List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Sender: mpls-bounces@lists.ietf.org Errors-To: mpls-bounces@lists.ietf.org I believe liushuying was perhaps more worried about control plane load, at reconvergence, for a high number of P2MP tunnels. Though the concern is valid, I would say that things should roughly be comparable to what happens with PIM. But I think it is fair to say that this aspect requires consideration in the solution design. Cheers, -Thomas IJsbrand Wijnands: > > We have some ideas on how to minimize the traffic loss during > switchover, but I'm not sure if we can prevent it without some kind of > FRR mechanism. > > Thx, > > Ice. > > BTW, I support make this a WG document. > > > On Feb 9, 2006, at 7:56 AM, liushuying wrote: > > > Hi folks, > > I support this draft becoming a WG document. > > > > However,i am about to ask a question. > > > > 1) 2.3.2.4. Upstream LSR change > > > > If, for a given node Z participating in a P2MP LSP , the > > upstream LSR changes, say from U to U', then Z MUST update its > > forwarding state by deleting the state for label L, allocating a new > > label, L', for , and installing the forwarding state for L'. > > In > > addition Z MUST send a Label Map to U' and send a Label > > Withdraw to U. > > > > The question: > > When a large quantity of P2MP LSPs exists in MPLS networks, > > if unicast routing information changes, there may be many LSRs > > whose upstream LSRs have changed in every P2MP LSP, each of them > > sends a Label Withdraw message > > to its old upstream LSR and a Label Map message to its new upstream > > LSR at the same time, > > so the load of every LSR will enhance sharply and last for a long > > time. > > As a result, the time of traffic disruption in every P2MP LSP will > > last for a long time, > > and so many packets will be lost. > > > > Thanks > > Shuying Liu > > > > > > ----- Original Message ----- > >> Date: Mon, 06 Feb 2006 07:50:51 -0500 > >> From: George Swallow > >> Subject: [mpls] LDP Multicast to WG Document > >> To: mpls@ietf.org > >> Message-ID: <20060206125051.3E3BD17B472@SwallowPB.local> > >> > >> It has been requested that > >> > >> Label Distribution Protocol Extensions for Point-to-Multipoint and > >> Multipoint-to-Multipoint Label Switched Paths > >> draft-minei-wijnands-mpls-ldp-p2mp-00 > >> > >> become a MPLS WG document. > >> > >> Please indicate your support or objections by the end of this week. > >> > >> Thanks, > >> > >> ...George > >> > >> ====================================================================== > >> == > >> George Swallow Cisco Systems (978) > >> 936-1398 > >> 1414 Massachusetts Avenue > >> Boxborough, MA 01719 > >> > >> > >> > >> > >> > >> ------------------------------ > >> > >> _______________________________________________ > >> mpls mailing list > >> mpls@lists.ietf.org > >> https://www1.ietf.org/mailman/listinfo/mpls > >> > > > _______________________________________________ > mpls mailing list > mpls@lists.ietf.org > https://www1.ietf.org/mailman/listinfo/mpls _______________________________________________ mpls mailing list mpls@lists.ietf.org https://www1.ietf.org/mailman/listinfo/mpls From mpls-bounces@lists.ietf.org Mon Feb 13 04:38:11 2006 Received: from localhost.cnri.reston.va.us ([127.0.0.1] helo=megatron.ietf.org) by megatron.ietf.org with esmtp (Exim 4.32) id 1F8a9q-0004qA-VB; Mon, 13 Feb 2006 04:38:10 -0500 Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org) by megatron.ietf.org with esmtp (Exim 4.32) id 1F8a9l-0004pQ-Oa for mpls@megatron.ietf.org; Mon, 13 Feb 2006 04:38:08 -0500 Received: from ietf-mx.ietf.org (ietf-mx [132.151.6.1]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id EAA29284 for ; Mon, 13 Feb 2006 04:36:20 -0500 (EST) Received: from odd-brew.cisco.com ([144.254.15.119] helo=av-tac-bru.cisco.com) by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1F8aNL-0000q1-R6 for mpls@ietf.org; Mon, 13 Feb 2006 04:52:08 -0500 X-TACSUNS: Virus Scanned Received: from strange-brew.cisco.com (localhost [127.0.0.1]) by av-tac-bru.cisco.com (8.11.7p1+Sun/8.11.7) with ESMTP id k1D9btZ14666; Mon, 13 Feb 2006 10:37:55 +0100 (CET) Received: from [10.61.255.122] (ams-stealth-iwijnand-2.cisco.com [10.61.255.122]) by strange-brew.cisco.com (8.11.7p1+Sun/8.11.7) with ESMTP id k1D9bsC13805; Mon, 13 Feb 2006 10:37:54 +0100 (CET) In-Reply-To: <1139608371.5389.146.camel@wintermute> References: <0IUA002ZH0BV7M@szxga02-in.huawei.com> <006201c62d45$e7142bd0$640c6f0a@china.huawei.com> <383c087519d13ce17272a63930bb7581@cisco.com> <1139608371.5389.146.camel@wintermute> Mime-Version: 1.0 (Apple Message framework v623) Content-Type: text/plain; charset=US-ASCII; delsp=yes; format=flowed Message-Id: <34cd361f2de9a7fe97d641332875af74@cisco.com> Content-Transfer-Encoding: 7bit From: IJsbrand Wijnands Subject: Re: [mpls] LDP Multicast to WG Document Date: Mon, 13 Feb 2006 10:37:54 +0100 To: Thomas Morin X-Mailer: Apple Mail (2.623) X-Spam-Score: 0.0 (/) X-Scan-Signature: 093efd19b5f651b2707595638f6c4003 Content-Transfer-Encoding: 7bit Cc: mpls@ietf.org X-BeenThere: mpls@lists.ietf.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Multi-Protocol Label Switching WG List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Sender: mpls-bounces@lists.ietf.org Errors-To: mpls-bounces@lists.ietf.org Hi Thomas, > I believe liushuying was perhaps more worried about control plane load, > at reconvergence, for a high number of P2MP tunnels. > Though the concern is valid, I would say that things should roughly be > comparable to what happens with PIM. But I think it is fair to say that > this aspect requires consideration in the solution design. LDP uses TCP to send the label mappings to its peers. So in case of a large number of P2MP LSP we will take maximum benefit of the flow control en reliability in TCP, I don't think we can do better then that. I think the real problem behind the need to send many updates is that during that time, which increases with the number of updates, you have traffic loss. Thx, Ice. > > Cheers, > > -Thomas > > IJsbrand Wijnands: >> >> We have some ideas on how to minimize the traffic loss during >> switchover, but I'm not sure if we can prevent it without some kind of >> FRR mechanism. >> >> Thx, >> >> Ice. >> >> BTW, I support make this a WG document. >> >> >> On Feb 9, 2006, at 7:56 AM, liushuying wrote: >> >>> Hi folks, >>> I support this draft becoming a WG document. >>> >>> However,i am about to ask a question. >>> >>> 1) 2.3.2.4. Upstream LSR change >>> >>> If, for a given node Z participating in a P2MP LSP , the >>> upstream LSR changes, say from U to U', then Z MUST update its >>> forwarding state by deleting the state for label L, allocating a >>> new >>> label, L', for , and installing the forwarding state for L'. >>> In >>> addition Z MUST send a Label Map to U' and send a Label >>> Withdraw to U. >>> >>> The question: >>> When a large quantity of P2MP LSPs exists in MPLS networks, >>> if unicast routing information changes, there may be many LSRs >>> whose upstream LSRs have changed in every P2MP LSP, each of them >>> sends a Label Withdraw message >>> to its old upstream LSR and a Label Map message to its new upstream >>> LSR at the same time, >>> so the load of every LSR will enhance sharply and last for a long >>> time. >>> As a result, the time of traffic disruption in every P2MP LSP will >>> last for a long time, >>> and so many packets will be lost. >>> >>> Thanks >>> Shuying Liu >>> >>> >>> ----- Original Message ----- >>>> Date: Mon, 06 Feb 2006 07:50:51 -0500 >>>> From: George Swallow >>>> Subject: [mpls] LDP Multicast to WG Document >>>> To: mpls@ietf.org >>>> Message-ID: <20060206125051.3E3BD17B472@SwallowPB.local> >>>> >>>> It has been requested that >>>> >>>> Label Distribution Protocol Extensions for Point-to-Multipoint and >>>> Multipoint-to-Multipoint Label Switched Paths >>>> draft-minei-wijnands-mpls-ldp-p2mp-00 >>>> >>>> become a MPLS WG document. >>>> >>>> Please indicate your support or objections by the end of this week. >>>> >>>> Thanks, >>>> >>>> ...George >>>> >>>> ==================================================================== >>>> == >>>> == >>>> George Swallow Cisco Systems (978) >>>> 936-1398 >>>> 1414 Massachusetts Avenue >>>> Boxborough, MA 01719 >>>> >>>> >>>> >>>> >>>> >>>> ------------------------------ >>>> >>>> _______________________________________________ >>>> mpls mailing list >>>> mpls@lists.ietf.org >>>> https://www1.ietf.org/mailman/listinfo/mpls >>>> >> >> >> _______________________________________________ >> mpls mailing list >> mpls@lists.ietf.org >> https://www1.ietf.org/mailman/listinfo/mpls > > > _______________________________________________ > mpls mailing list > mpls@lists.ietf.org > https://www1.ietf.org/mailman/listinfo/mpls _______________________________________________ mpls mailing list mpls@lists.ietf.org https://www1.ietf.org/mailman/listinfo/mpls From mpls-bounces@lists.ietf.org Mon Feb 13 07:30:17 2006 Received: from localhost.cnri.reston.va.us ([127.0.0.1] helo=megatron.ietf.org) by megatron.ietf.org with esmtp (Exim 4.32) id 1F8cqP-00058n-Nc; Mon, 13 Feb 2006 07:30:17 -0500 Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org) by megatron.ietf.org with esmtp (Exim 4.32) id 1F8cqN-00058i-Uw for mpls@megatron.ietf.org; Mon, 13 Feb 2006 07:30:16 -0500 Received: from ietf-mx.ietf.org (ietf-mx [132.151.6.1]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id HAA14258 for ; Mon, 13 Feb 2006 07:28:30 -0500 (EST) Received: from p-mail2.rd.francetelecom.com ([195.101.245.16]) by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1F8d3z-0006M8-0E for mpls@ietf.org; Mon, 13 Feb 2006 07:44:20 -0500 Received: from ftrdmel10.rd.francetelecom.fr ([10.193.117.156]) by ftrdsmtp2.rd.francetelecom.fr with Microsoft SMTPSVC(6.0.3790.1830); Mon, 13 Feb 2006 13:30:12 +0100 Received: from l-at8613.rd.francetelecom.fr ([10.193.15.12]) by ftrdmel10.rd.francetelecom.fr with Microsoft SMTPSVC(6.0.3790.211); Mon, 13 Feb 2006 13:30:11 +0100 Subject: Re: [mpls] draft-raggarwa-mpls-rsvp-upstream-00 for wg doc? From: Thomas Morin To: Loa Andersson In-Reply-To: <43E381D5.8020008@pi.se> References: <43E381D5.8020008@pi.se> Content-Type: text/plain Organization: France Telecom R&D Date: Mon, 13 Feb 2006 13:29:56 +0100 Message-Id: <1139833796.30639.5.camel@wintermute> Mime-Version: 1.0 X-Mailer: Evolution 2.4.2.1 Content-Transfer-Encoding: 7bit X-OriginalArrivalTime: 13 Feb 2006 12:30:11.0790 (UTC) FILETIME=[3BCA96E0:01C63099] X-Spam-Score: 0.0 (/) X-Scan-Signature: 9466e0365fc95844abaf7c3f15a05c7d Content-Transfer-Encoding: 7bit Cc: mpls@ietf.org X-BeenThere: mpls@lists.ietf.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Multi-Protocol Label Switching WG List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Sender: mpls-bounces@lists.ietf.org Errors-To: mpls-bounces@lists.ietf.org In favor. -Thomas [with WG in Cc, this time] Loa Andersson: > All, > > the authors of draft-raggarwa-mpls-rsvp-upstream-00 > has requested that it is made a working group document. > > Please review, comment and respond to the working group mailing > list if you support it becoming a wg or not. > > /Loa and George > > PS > > yes - there are two separate polls one for > > draft-raggarwa-mpls-ldp-upstream-00 > and one for > draft-raggarwa-mpls-rsvp-upstream-00 > > :) > > _______________________________________________ mpls mailing list mpls@lists.ietf.org https://www1.ietf.org/mailman/listinfo/mpls From mpls-bounces@lists.ietf.org Mon Feb 13 07:31:36 2006 Received: from localhost.cnri.reston.va.us ([127.0.0.1] helo=megatron.ietf.org) by megatron.ietf.org with esmtp (Exim 4.32) id 1F8crg-0005ZE-7G; Mon, 13 Feb 2006 07:31:36 -0500 Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org) by megatron.ietf.org with esmtp (Exim 4.32) id 1F8crd-0005Z3-QZ for mpls@megatron.ietf.org; Mon, 13 Feb 2006 07:31:33 -0500 Received: from ietf-mx.ietf.org (ietf-mx [132.151.6.1]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id HAA14386 for ; Mon, 13 Feb 2006 07:29:47 -0500 (EST) Received: from p-mail2.rd.francetelecom.com ([195.101.245.16]) by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1F8d5E-0006P9-HP for mpls@ietf.org; Mon, 13 Feb 2006 07:45:38 -0500 Received: from ftrdmel10.rd.francetelecom.fr ([10.193.117.156]) by ftrdsmtp1.rd.francetelecom.fr with Microsoft SMTPSVC(6.0.3790.1830); Mon, 13 Feb 2006 13:31:29 +0100 Received: from l-at8613.rd.francetelecom.fr ([10.193.15.12]) by ftrdmel10.rd.francetelecom.fr with Microsoft SMTPSVC(6.0.3790.211); Mon, 13 Feb 2006 13:31:28 +0100 Subject: Re: [mpls] draft-raggarwa-mpls-ldp-upstream-00 for wg doc? From: Thomas Morin To: Loa Andersson In-Reply-To: <43E3814B.80503@pi.se> References: <43E3814B.80503@pi.se> Content-Type: text/plain Organization: France Telecom R&D Date: Mon, 13 Feb 2006 13:31:13 +0100 Message-Id: <1139833873.30639.9.camel@wintermute> Mime-Version: 1.0 X-Mailer: Evolution 2.4.2.1 Content-Transfer-Encoding: 7bit X-OriginalArrivalTime: 13 Feb 2006 12:31:28.0853 (UTC) FILETIME=[69B97850:01C63099] X-Spam-Score: 0.0 (/) X-Scan-Signature: 856eb5f76e7a34990d1d457d8e8e5b7f Content-Transfer-Encoding: 7bit Cc: mpls@ietf.org X-BeenThere: mpls@lists.ietf.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Multi-Protocol Label Switching WG List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Sender: mpls-bounces@lists.ietf.org Errors-To: mpls-bounces@lists.ietf.org In favor. -Thomas [with WG in Cc, this time] Loa Andersson: > All, > > the authors of draft-raggarwa-mpls-ldp-upstream-00 > has requested that it is made a working group document. > > Please review, comment and respond to the working group mailing > list if you support it becoming a wg or not. > > /Loa and George > _______________________________________________ mpls mailing list mpls@lists.ietf.org https://www1.ietf.org/mailman/listinfo/mpls From mpls-bounces@lists.ietf.org Mon Feb 13 09:48:14 2006 Received: from localhost.cnri.reston.va.us ([127.0.0.1] helo=megatron.ietf.org) by megatron.ietf.org with esmtp (Exim 4.32) id 1F8ezu-0006is-A7; Mon, 13 Feb 2006 09:48:14 -0500 Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org) by megatron.ietf.org with esmtp (Exim 4.32) id 1F8ezs-0006in-MG for mpls@megatron.ietf.org; Mon, 13 Feb 2006 09:48:12 -0500 Received: from ietf-mx.ietf.org (ietf-mx [132.151.6.1]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id JAA26107 for ; Mon, 13 Feb 2006 09:46:28 -0500 (EST) Received: from mail121.messagelabs.com ([216.82.241.195]) by ietf-mx.ietf.org with smtp (Exim 4.43) id 1F8fDR-0002ee-Nv for mpls@ietf.org; Mon, 13 Feb 2006 10:02:18 -0500 X-VirusChecked: Checked X-Env-Sender: luyuanfang@att.com X-Msg-Ref: server-7.tower-121.messagelabs.com!1139842055!7603738!3 X-StarScan-Version: 5.5.9.1; banners=-,-,- X-Originating-IP: [134.24.146.4] Received: (qmail 5848 invoked from network); 13 Feb 2006 14:47:57 -0000 Received: from unknown (HELO attrh3i.attrh.att.com) (134.24.146.4) by server-7.tower-121.messagelabs.com with SMTP; 13 Feb 2006 14:47:57 -0000 Received: from kcclust06evs1.ugd.att.com (135.38.164.88) by attrh3i.attrh.att.com (7.2.052) id 43D3BB52002E433D; Mon, 13 Feb 2006 09:47:57 -0500 Content-class: urn:content-classes:message MIME-Version: 1.0 Content-Type: text/plain; charset="US-ASCII" Content-Transfer-Encoding: quoted-printable X-MimeOLE: Produced By Microsoft Exchange V6.5.7226.0 Subject: RE: [mpls] draft-raggarwa-mpls-ldp-upstream-00 for wg doc? Date: Mon, 13 Feb 2006 08:47:56 -0600 Message-ID: Thread-Topic: [mpls] draft-raggarwa-mpls-ldp-upstream-00 for wg doc? Thread-Index: AcYo3cF+L2furyn/Tq+DzupttXcgUwHzn2/w From: "Fang, Luyuan, ALABS" To: "Loa Andersson" , X-Spam-Score: 0.0 (/) X-Scan-Signature: 97adf591118a232206bdb5a27b217034 Content-Transfer-Encoding: quoted-printable Cc: X-BeenThere: mpls@lists.ietf.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Multi-Protocol Label Switching WG List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Sender: mpls-bounces@lists.ietf.org Errors-To: mpls-bounces@lists.ietf.org Support. -Luyuan=20 -----Original Message----- From: mpls-bounces@lists.ietf.org [mailto:mpls-bounces@lists.ietf.org] On Behalf Of Loa Andersson Sent: Friday, February 03, 2006 11:14 AM To: mpls@ietf.org Subject: [mpls] draft-raggarwa-mpls-ldp-upstream-00 for wg doc? All, the authors of draft-raggarwa-mpls-ldp-upstream-00 has requested that it is made a working group document. Please review, comment and respond to the working group mailing list if you support it becoming a wg or not. /Loa and George --=20 Loa Andersson Principal Networking Architect Acreo AB phone: +46 8 632 77 14 Isafjordsgatan 22 mobile: +46 739 81 21 64 Kista, Sweden email: loa.andersson@acreo.se loa@pi.se _______________________________________________ mpls mailing list mpls@lists.ietf.org https://www1.ietf.org/mailman/listinfo/mpls _______________________________________________ mpls mailing list mpls@lists.ietf.org https://www1.ietf.org/mailman/listinfo/mpls From mpls-bounces@lists.ietf.org Mon Feb 13 09:48:19 2006 Received: from localhost.cnri.reston.va.us ([127.0.0.1] helo=megatron.ietf.org) by megatron.ietf.org with esmtp (Exim 4.32) id 1F8ezz-0006je-7N; Mon, 13 Feb 2006 09:48:19 -0500 Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org) by megatron.ietf.org with esmtp (Exim 4.32) id 1F8ezx-0006jU-TP for mpls@megatron.ietf.org; Mon, 13 Feb 2006 09:48:17 -0500 Received: from ietf-mx.ietf.org (ietf-mx [132.151.6.1]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id JAA26115 for ; Mon, 13 Feb 2006 09:46:33 -0500 (EST) Received: from mail126.messagelabs.com ([216.82.250.99]) by ietf-mx.ietf.org with smtp (Exim 4.43) id 1F8fDa-0002fD-4G for mpls@ietf.org; Mon, 13 Feb 2006 10:02:23 -0500 X-VirusChecked: Checked X-Env-Sender: luyuanfang@att.com X-Msg-Ref: server-9.tower-126.messagelabs.com!1139842076!9252082!5 X-StarScan-Version: 5.5.9.1; banners=-,-,- X-Originating-IP: [134.24.146.4] Received: (qmail 21625 invoked from network); 13 Feb 2006 14:48:05 -0000 Received: from unknown (HELO attrh3i.attrh.att.com) (134.24.146.4) by server-9.tower-126.messagelabs.com with SMTP; 13 Feb 2006 14:48:05 -0000 Received: from kcclust06evs1.ugd.att.com (135.38.164.88) by attrh3i.attrh.att.com (7.2.052) id 43D3BB52002E4356; Mon, 13 Feb 2006 09:48:05 -0500 Content-class: urn:content-classes:message MIME-Version: 1.0 Content-Type: text/plain; charset="US-ASCII" Content-Transfer-Encoding: quoted-printable X-MimeOLE: Produced By Microsoft Exchange V6.5.7226.0 Subject: RE: [mpls] draft-raggarwa-mpls-rsvp-upstream-00 for wg doc? Date: Mon, 13 Feb 2006 08:48:04 -0600 Message-ID: Thread-Topic: [mpls] draft-raggarwa-mpls-rsvp-upstream-00 for wg doc? Thread-Index: AcYo3f3oMVO8ciJNQbifojKeNa6qxQHzW9Lw From: "Fang, Luyuan, ALABS" To: "Loa Andersson" , X-Spam-Score: 0.0 (/) X-Scan-Signature: cab78e1e39c4b328567edb48482b6a69 Content-Transfer-Encoding: quoted-printable Cc: X-BeenThere: mpls@lists.ietf.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Multi-Protocol Label Switching WG List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Sender: mpls-bounces@lists.ietf.org Errors-To: mpls-bounces@lists.ietf.org Support. - Luyuan=20 -----Original Message----- From: mpls-bounces@lists.ietf.org [mailto:mpls-bounces@lists.ietf.org] On Behalf Of Loa Andersson Sent: Friday, February 03, 2006 11:16 AM To: mpls@ietf.org Subject: [mpls] draft-raggarwa-mpls-rsvp-upstream-00 for wg doc? All, the authors of draft-raggarwa-mpls-rsvp-upstream-00 has requested that it is made a working group document. Please review, comment and respond to the working group mailing list if you support it becoming a wg or not. /Loa and George PS yes - there are two separate polls one for draft-raggarwa-mpls-ldp-upstream-00 and one for draft-raggarwa-mpls-rsvp-upstream-00 :) --=20 Loa Andersson Principal Networking Architect Acreo AB phone: +46 8 632 77 14 Isafjordsgatan 22 mobile: +46 739 81 21 64 Kista, Sweden email: loa.andersson@acreo.se loa@pi.se _______________________________________________ mpls mailing list mpls@lists.ietf.org https://www1.ietf.org/mailman/listinfo/mpls _______________________________________________ mpls mailing list mpls@lists.ietf.org https://www1.ietf.org/mailman/listinfo/mpls From mpls-bounces@lists.ietf.org Mon Feb 13 09:49:52 2006 Received: from localhost.cnri.reston.va.us ([127.0.0.1] helo=megatron.ietf.org) by megatron.ietf.org with esmtp (Exim 4.32) id 1F8f1U-00070Q-BB; Mon, 13 Feb 2006 09:49:52 -0500 Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org) by megatron.ietf.org with esmtp (Exim 4.32) id 1F8f1T-00070G-0b for mpls@megatron.ietf.org; Mon, 13 Feb 2006 09:49:51 -0500 Received: from ietf-mx.ietf.org (ietf-mx [132.151.6.1]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id JAA26274 for ; Mon, 13 Feb 2006 09:48:06 -0500 (EST) Received: from slb-smtpout-01.boeing.com ([130.76.64.48]) by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1F8fF3-0002iP-Rf for mpls@ietf.org; Mon, 13 Feb 2006 10:03:56 -0500 Received: from stl-av-01.boeing.com ([192.76.190.6]) by slb-smtpout-01.boeing.com (8.9.2.MG.10092003/8.8.5-M2) with ESMTP id GAA07144 for ; Mon, 13 Feb 2006 06:49:39 -0800 (PST) Received: from XCH-SWBH-04.sw.nos.boeing.com (localhost [127.0.0.1]) by stl-av-01.boeing.com (8.11.3/8.11.3/MBS-AV-LDAP-01) with ESMTP id k1DEncN00443 for ; Mon, 13 Feb 2006 08:49:38 -0600 (CST) Received: from XCH-SW-42.sw.nos.boeing.com ([192.79.11.43]) by XCH-SWBH-04.sw.nos.boeing.com with Microsoft SMTPSVC(6.0.3790.211); Mon, 13 Feb 2006 06:48:55 -0800 X-MimeOLE: Produced By Microsoft Exchange V6.5.7226.0 Content-class: urn:content-classes:message MIME-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: quoted-printable Subject: RE: [mpls] draft-raggarwa-mpls-rsvp-upstream-00 for wg doc? Date: Mon, 13 Feb 2006 06:48:54 -0800 Message-ID: <626FC7C6A97381468FB872072AB5DDC83699E6@XCH-SW-42.sw.nos.boeing.com> Thread-Topic: [mpls] draft-raggarwa-mpls-rsvp-upstream-00 for wg doc? Thread-Index: AcYo4RArLqY0NrtwRIqzDMYwExOhogHyr1zA From: "Drake, John E" To: X-OriginalArrivalTime: 13 Feb 2006 14:48:55.0038 (UTC) FILETIME=[9CD571E0:01C630AC] X-Spam-Score: 0.0 (/) X-Scan-Signature: a7d6aff76b15f3f56fcb94490e1052e4 Content-Transfer-Encoding: quoted-printable Cc: X-BeenThere: mpls@lists.ietf.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Multi-Protocol Label Switching WG List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Sender: mpls-bounces@lists.ietf.org Errors-To: mpls-bounces@lists.ietf.org Yes > -----Original Message----- > From: Loa Andersson [mailto:loa@pi.se] > Sent: Friday, February 03, 2006 8:16 AM > To: mpls@ietf.org > Subject: [mpls] draft-raggarwa-mpls-rsvp-upstream-00 for wg doc? >=20 > All, >=20 > the authors of draft-raggarwa-mpls-rsvp-upstream-00 > has requested that it is made a working group document. >=20 > Please review, comment and respond to the working group mailing > list if you support it becoming a wg or not. >=20 > /Loa and George >=20 > PS >=20 > yes - there are two separate polls one for >=20 > draft-raggarwa-mpls-ldp-upstream-00 > and one for > draft-raggarwa-mpls-rsvp-upstream-00 >=20 > :) >=20 >=20 > -- > Loa Andersson >=20 > Principal Networking Architect > Acreo AB phone: +46 8 632 77 14 > Isafjordsgatan 22 mobile: +46 739 81 21 64 > Kista, Sweden email: loa.andersson@acreo.se > loa@pi.se >=20 > _______________________________________________ > mpls mailing list > mpls@lists.ietf.org > https://www1.ietf.org/mailman/listinfo/mpls _______________________________________________ mpls mailing list mpls@lists.ietf.org https://www1.ietf.org/mailman/listinfo/mpls From mpls-bounces@lists.ietf.org Mon Feb 13 09:49:53 2006 Received: from localhost.cnri.reston.va.us ([127.0.0.1] helo=megatron.ietf.org) by megatron.ietf.org with esmtp (Exim 4.32) id 1F8f1V-00070v-PT; Mon, 13 Feb 2006 09:49:53 -0500 Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org) by megatron.ietf.org with esmtp (Exim 4.32) id 1F8f1T-00070L-Cs for mpls@megatron.ietf.org; Mon, 13 Feb 2006 09:49:51 -0500 Received: from ietf-mx.ietf.org (ietf-mx [132.151.6.1]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id JAA26273 for ; Mon, 13 Feb 2006 09:48:06 -0500 (EST) Received: from slb-smtpout-01.boeing.com ([130.76.64.48]) by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1F8fF4-0002iT-Dy for mpls@ietf.org; Mon, 13 Feb 2006 10:03:56 -0500 Received: from stl-av-01.boeing.com ([192.76.190.6]) by slb-smtpout-01.boeing.com (8.9.2.MG.10092003/8.8.5-M2) with ESMTP id GAA07159 for ; Mon, 13 Feb 2006 06:49:39 -0800 (PST) Received: from XCH-SWBH-04.sw.nos.boeing.com (localhost [127.0.0.1]) by stl-av-01.boeing.com (8.11.3/8.11.3/MBS-AV-LDAP-01) with ESMTP id k1DEncN00468 for ; Mon, 13 Feb 2006 08:49:39 -0600 (CST) Received: from XCH-SW-42.sw.nos.boeing.com ([192.79.11.43]) by XCH-SWBH-04.sw.nos.boeing.com with Microsoft SMTPSVC(6.0.3790.211); Mon, 13 Feb 2006 06:49:02 -0800 X-MimeOLE: Produced By Microsoft Exchange V6.5.7226.0 Content-class: urn:content-classes:message MIME-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: quoted-printable Subject: RE: [mpls] draft-raggarwa-mpls-ldp-upstream-00 for wg doc? Date: Mon, 13 Feb 2006 06:49:02 -0800 Message-ID: <626FC7C6A97381468FB872072AB5DDC83699E7@XCH-SW-42.sw.nos.boeing.com> Thread-Topic: [mpls] draft-raggarwa-mpls-ldp-upstream-00 for wg doc? Thread-Index: AcYo3YInaWsRhRW6Roq3kc2IZCgiugHzjTQA From: "Drake, John E" To: X-OriginalArrivalTime: 13 Feb 2006 14:49:02.0834 (UTC) FILETIME=[A17B0520:01C630AC] X-Spam-Score: 0.0 (/) X-Scan-Signature: e5ba305d0e64821bf3d8bc5d3bb07228 Content-Transfer-Encoding: quoted-printable Cc: X-BeenThere: mpls@lists.ietf.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Multi-Protocol Label Switching WG List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Sender: mpls-bounces@lists.ietf.org Errors-To: mpls-bounces@lists.ietf.org Yes > -----Original Message----- > From: Loa Andersson [mailto:loa@pi.se] > Sent: Friday, February 03, 2006 8:14 AM > To: mpls@ietf.org > Subject: [mpls] draft-raggarwa-mpls-ldp-upstream-00 for wg doc? >=20 > All, >=20 > the authors of draft-raggarwa-mpls-ldp-upstream-00 > has requested that it is made a working group document. >=20 > Please review, comment and respond to the working group mailing > list if you support it becoming a wg or not. >=20 > /Loa and George >=20 > -- > Loa Andersson >=20 > Principal Networking Architect > Acreo AB phone: +46 8 632 77 14 > Isafjordsgatan 22 mobile: +46 739 81 21 64 > Kista, Sweden email: loa.andersson@acreo.se > loa@pi.se >=20 > _______________________________________________ > mpls mailing list > mpls@lists.ietf.org > https://www1.ietf.org/mailman/listinfo/mpls _______________________________________________ mpls mailing list mpls@lists.ietf.org https://www1.ietf.org/mailman/listinfo/mpls From mpls-bounces@lists.ietf.org Mon Feb 13 10:10:24 2006 Received: from localhost.cnri.reston.va.us ([127.0.0.1] helo=megatron.ietf.org) by megatron.ietf.org with esmtp (Exim 4.32) id 1F8fLM-000643-Bm; Mon, 13 Feb 2006 10:10:24 -0500 Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org) by megatron.ietf.org with esmtp (Exim 4.32) id 1F8fLK-00063o-Bd for mpls@megatron.ietf.org; Mon, 13 Feb 2006 10:10:22 -0500 Received: from ietf-mx.ietf.org (ietf-mx [132.151.6.1]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id KAA28640 for ; Mon, 13 Feb 2006 10:08:37 -0500 (EST) Received: from mail120.messagelabs.com ([216.82.250.83]) by ietf-mx.ietf.org with smtp (Exim 4.43) id 1F8fYw-0003UC-Cb for mpls@ietf.org; Mon, 13 Feb 2006 10:24:27 -0500 X-VirusChecked: Checked X-Env-Sender: gash@att.com X-Msg-Ref: server-9.tower-120.messagelabs.com!1139843016!8267685!105 X-StarScan-Version: 5.5.9.1; banners=-,-,- X-Originating-IP: [134.24.146.4] Received: (qmail 7973 invoked from network); 13 Feb 2006 15:10:10 -0000 Received: from unknown (HELO attrh3i.attrh.att.com) (134.24.146.4) by server-9.tower-120.messagelabs.com with SMTP; 13 Feb 2006 15:10:10 -0000 Received: from kcclust06evs1.ugd.att.com (135.38.164.88) by attrh3i.attrh.att.com (7.2.052) id 43D3BB52002E599F for mpls@ietf.org; Mon, 13 Feb 2006 10:10:09 -0500 Content-class: urn:content-classes:message MIME-Version: 1.0 Content-Type: text/plain; charset="US-ASCII" Content-Transfer-Encoding: quoted-printable X-MimeOLE: Produced By Microsoft Exchange V6.5.7226.0 Subject: RE: [mpls] draft-raggarwa-mpls-ldp-upstream-00 for wg doc? Date: Mon, 13 Feb 2006 09:10:09 -0600 Message-ID: <9473683187ADC049A855ED2DA739ABCA09FA9B0B@KCCLUST06EVS1.ugd.att.com> Thread-Topic: [mpls] draft-raggarwa-mpls-ldp-upstream-00 for wg doc? Thread-Index: AcYo3YInaWsRhRW6Roq3kc2IZCgiugHzjTQAAADjiZA= From: "Ash, Gerald R \(Jerry\), ALABS" To: X-Spam-Score: 0.0 (/) X-Scan-Signature: 7aefe408d50e9c7c47615841cb314bed Content-Transfer-Encoding: quoted-printable Cc: X-BeenThere: mpls@lists.ietf.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Multi-Protocol Label Switching WG List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Sender: mpls-bounces@lists.ietf.org Errors-To: mpls-bounces@lists.ietf.org > the authors of draft-raggarwa-mpls-ldp-upstream-00 > has requested that it is made a working group document. >=20 > Please review, comment and respond to the working group mailing > list if you support it becoming a wg or not. Yes. _______________________________________________ mpls mailing list mpls@lists.ietf.org https://www1.ietf.org/mailman/listinfo/mpls From mpls-bounces@lists.ietf.org Mon Feb 13 10:10:43 2006 Received: from localhost.cnri.reston.va.us ([127.0.0.1] helo=megatron.ietf.org) by megatron.ietf.org with esmtp (Exim 4.32) id 1F8fLf-00066Z-51; Mon, 13 Feb 2006 10:10:43 -0500 Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org) by megatron.ietf.org with esmtp (Exim 4.32) id 1F8fLc-00066L-TN for mpls@megatron.ietf.org; Mon, 13 Feb 2006 10:10:40 -0500 Received: from ietf-mx.ietf.org (ietf-mx [132.151.6.1]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id KAA28662 for ; Mon, 13 Feb 2006 10:08:56 -0500 (EST) Received: from mail126.messagelabs.com ([216.82.250.99]) by ietf-mx.ietf.org with smtp (Exim 4.43) id 1F8fZE-0003V1-Bn for mpls@ietf.org; Mon, 13 Feb 2006 10:24:46 -0500 X-VirusChecked: Checked X-Env-Sender: gash@att.com X-Msg-Ref: server-5.tower-126.messagelabs.com!1139843116!9534258!86 X-StarScan-Version: 5.5.9.1; banners=-,-,- X-Originating-IP: [134.24.146.4] Received: (qmail 3747 invoked from network); 13 Feb 2006 15:10:24 -0000 Received: from unknown (HELO attrh3i.attrh.att.com) (134.24.146.4) by server-5.tower-126.messagelabs.com with SMTP; 13 Feb 2006 15:10:24 -0000 Received: from kcclust06evs1.ugd.att.com (135.38.164.88) by attrh3i.attrh.att.com (7.2.052) id 43D3BB52002E59D7 for mpls@ietf.org; Mon, 13 Feb 2006 10:10:24 -0500 Content-class: urn:content-classes:message MIME-Version: 1.0 Content-Type: text/plain; charset="US-ASCII" Content-Transfer-Encoding: quoted-printable X-MimeOLE: Produced By Microsoft Exchange V6.5.7226.0 Subject: RE: [mpls] draft-raggarwa-mpls-rsvp-upstream-00 for wg doc? Date: Mon, 13 Feb 2006 09:10:22 -0600 Message-ID: <9473683187ADC049A855ED2DA739ABCA09FA9B0C@KCCLUST06EVS1.ugd.att.com> Thread-Topic: [mpls] draft-raggarwa-mpls-rsvp-upstream-00 for wg doc? Thread-Index: AcYo4RArLqY0NrtwRIqzDMYwExOhogHyr1zAAADnEcA= From: "Ash, Gerald R \(Jerry\), ALABS" To: X-Spam-Score: 0.0 (/) X-Scan-Signature: 7aefe408d50e9c7c47615841cb314bed Content-Transfer-Encoding: quoted-printable Cc: X-BeenThere: mpls@lists.ietf.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Multi-Protocol Label Switching WG List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Sender: mpls-bounces@lists.ietf.org Errors-To: mpls-bounces@lists.ietf.org > the authors of draft-raggarwa-mpls-rsvp-upstream-00 > has requested that it is made a working group document. >=20 > Please review, comment and respond to the working group mailing > list if you support it becoming a wg or not. Yes. _______________________________________________ mpls mailing list mpls@lists.ietf.org https://www1.ietf.org/mailman/listinfo/mpls From mpls-bounces@lists.ietf.org Mon Feb 13 14:05:18 2006 Received: from localhost.cnri.reston.va.us ([127.0.0.1] helo=megatron.ietf.org) by megatron.ietf.org with esmtp (Exim 4.32) id 1F8j0g-0005Wc-73; Mon, 13 Feb 2006 14:05:18 -0500 Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org) by megatron.ietf.org with esmtp (Exim 4.32) id 1F8j0e-0005WX-5B for mpls@megatron.ietf.org; Mon, 13 Feb 2006 14:05:16 -0500 Received: from ietf-mx.ietf.org (ietf-mx [132.151.6.1]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id OAA15538 for ; Mon, 13 Feb 2006 14:03:30 -0500 (EST) Received: from colo-dns-ext1.juniper.net ([207.17.137.57]) by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1F8jEF-0002TC-LV for mpls@ietf.org; Mon, 13 Feb 2006 14:19:24 -0500 Received: from merlot.juniper.net (merlot.juniper.net [172.17.27.10]) by colo-dns-ext1.juniper.net (8.11.3/8.9.3) with ESMTP id k1DJ52X35764; Mon, 13 Feb 2006 11:05:02 -0800 (PST) (envelope-from arthi@juniper.net) Received: from zircon.juniper.net (zircon.juniper.net [172.17.28.113]) by merlot.juniper.net (8.11.3/8.11.3) with ESMTP id k1DJ4v573444; Mon, 13 Feb 2006 11:04:57 -0800 (PST) (envelope-from arthi@juniper.net) Date: Mon, 13 Feb 2006 11:04:57 -0800 (PST) From: Arthi Ayyangar To: Loa Andersson Subject: Re: [mpls] draft-raggarwa-mpls-ldp-upstream-00 for wg doc? In-Reply-To: <43E3814B.80503@pi.se> Message-ID: <20060213110436.R74961@zircon.juniper.net> References: <43E3814B.80503@pi.se> MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII; format=flowed X-Spam-Score: 0.0 (/) X-Scan-Signature: ffa9dfbbe7cc58b3fa6b8ae3e57b0aa3 Cc: mpls@ietf.org X-BeenThere: mpls@lists.ietf.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Multi-Protocol Label Switching WG List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Sender: mpls-bounces@lists.ietf.org Errors-To: mpls-bounces@lists.ietf.org Support. -arthi > the authors of draft-raggarwa-mpls-ldp-upstream-00 > has requested that it is made a working group document. > > Please review, comment and respond to the working group mailing > list if you support it becoming a wg or not. > > /Loa and George > > -- > Loa Andersson > > Principal Networking Architect > Acreo AB phone: +46 8 632 77 14 > Isafjordsgatan 22 mobile: +46 739 81 21 64 > Kista, Sweden email: loa.andersson@acreo.se > loa@pi.se > > _______________________________________________ > mpls mailing list > mpls@lists.ietf.org > https://www1.ietf.org/mailman/listinfo/mpls > _______________________________________________ mpls mailing list mpls@lists.ietf.org https://www1.ietf.org/mailman/listinfo/mpls From mpls-bounces@lists.ietf.org Mon Feb 13 14:05:32 2006 Received: from localhost.cnri.reston.va.us ([127.0.0.1] helo=megatron.ietf.org) by megatron.ietf.org with esmtp (Exim 4.32) id 1F8j0u-0005bv-Ap; Mon, 13 Feb 2006 14:05:32 -0500 Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org) by megatron.ietf.org with esmtp (Exim 4.32) id 1F8j0s-0005bn-9Q for mpls@megatron.ietf.org; Mon, 13 Feb 2006 14:05:30 -0500 Received: from ietf-mx.ietf.org (ietf-mx [132.151.6.1]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id OAA15564 for ; Mon, 13 Feb 2006 14:03:44 -0500 (EST) Received: from colo-dns-ext2.juniper.net ([207.17.137.64]) by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1F8jEW-0002TU-Qw for mpls@ietf.org; Mon, 13 Feb 2006 14:19:38 -0500 Received: from merlot.juniper.net (merlot.juniper.net [172.17.27.10]) by colo-dns-ext2.juniper.net (8.12.3/8.12.3) with ESMTP id k1DJ5J1Z067460; Mon, 13 Feb 2006 11:05:19 -0800 (PST) (envelope-from arthi@juniper.net) Received: from zircon.juniper.net (zircon.juniper.net [172.17.28.113]) by merlot.juniper.net (8.11.3/8.11.3) with ESMTP id k1DJ5J573547; Mon, 13 Feb 2006 11:05:19 -0800 (PST) (envelope-from arthi@juniper.net) Date: Mon, 13 Feb 2006 11:05:19 -0800 (PST) From: Arthi Ayyangar To: Loa Andersson Subject: Re: [mpls] draft-raggarwa-mpls-rsvp-upstream-00 for wg doc? In-Reply-To: <43E381D5.8020008@pi.se> Message-ID: <20060213110507.L74961@zircon.juniper.net> References: <43E381D5.8020008@pi.se> MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII; format=flowed X-Spam-Score: 0.0 (/) X-Scan-Signature: 39bd8f8cbb76cae18b7e23f7cf6b2b9f Cc: mpls@ietf.org X-BeenThere: mpls@lists.ietf.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Multi-Protocol Label Switching WG List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Sender: mpls-bounces@lists.ietf.org Errors-To: mpls-bounces@lists.ietf.org Support. -arthi > the authors of draft-raggarwa-mpls-rsvp-upstream-00 > has requested that it is made a working group document. > > Please review, comment and respond to the working group mailing > list if you support it becoming a wg or not. > > /Loa and George > > PS > > yes - there are two separate polls one for > > draft-raggarwa-mpls-ldp-upstream-00 > and one for > draft-raggarwa-mpls-rsvp-upstream-00 > > :) > > > -- > Loa Andersson > > Principal Networking Architect > Acreo AB phone: +46 8 632 77 14 > Isafjordsgatan 22 mobile: +46 739 81 21 64 > Kista, Sweden email: loa.andersson@acreo.se > loa@pi.se > > _______________________________________________ > mpls mailing list > mpls@lists.ietf.org > https://www1.ietf.org/mailman/listinfo/mpls > _______________________________________________ mpls mailing list mpls@lists.ietf.org https://www1.ietf.org/mailman/listinfo/mpls From mpls-bounces@lists.ietf.org Mon Feb 13 14:05:58 2006 Received: from localhost.cnri.reston.va.us ([127.0.0.1] helo=megatron.ietf.org) by megatron.ietf.org with esmtp (Exim 4.32) id 1F8j1K-0005d0-Nb; Mon, 13 Feb 2006 14:05:58 -0500 Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org) by megatron.ietf.org with esmtp (Exim 4.32) id 1F8j1I-0005cs-FD for mpls@megatron.ietf.org; Mon, 13 Feb 2006 14:05:56 -0500 Received: from ietf-mx.ietf.org (ietf-mx [132.151.6.1]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id OAA15591 for ; Mon, 13 Feb 2006 14:04:10 -0500 (EST) Received: from colo-dns-ext1.juniper.net ([207.17.137.57]) by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1F8jEx-0002UD-1A for mpls@ietf.org; Mon, 13 Feb 2006 14:20:04 -0500 Received: from merlot.juniper.net (merlot.juniper.net [172.17.27.10]) by colo-dns-ext1.juniper.net (8.11.3/8.9.3) with ESMTP id k1DJ5jX35788; Mon, 13 Feb 2006 11:05:45 -0800 (PST) (envelope-from arthi@juniper.net) Received: from zircon.juniper.net (zircon.juniper.net [172.17.28.113]) by merlot.juniper.net (8.11.3/8.11.3) with ESMTP id k1DJ5e573641; Mon, 13 Feb 2006 11:05:40 -0800 (PST) (envelope-from arthi@juniper.net) Date: Mon, 13 Feb 2006 11:05:40 -0800 (PST) From: Arthi Ayyangar To: George Swallow Subject: Re: [mpls] LDP Multicast to WG Document In-Reply-To: <20060206125051.3E3BD17B472@SwallowPB.local> Message-ID: <20060213110533.T74961@zircon.juniper.net> References: <20060206125051.3E3BD17B472@SwallowPB.local> MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII; format=flowed X-Spam-Score: 0.0 (/) X-Scan-Signature: ea4ac80f790299f943f0a53be7e1a21a Cc: mpls@ietf.org X-BeenThere: mpls@lists.ietf.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Multi-Protocol Label Switching WG List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Sender: mpls-bounces@lists.ietf.org Errors-To: mpls-bounces@lists.ietf.org Support. -arthi > It has been requested that > > Label Distribution Protocol Extensions for Point-to-Multipoint and > Multipoint-to-Multipoint Label Switched Paths > draft-minei-wijnands-mpls-ldp-p2mp-00 > > become a MPLS WG document. > > Please indicate your support or objections by the end of this week. > > Thanks, > > ...George > > ======================================================================== > George Swallow Cisco Systems (978) 936-1398 > 1414 Massachusetts Avenue > Boxborough, MA 01719 > > > > _______________________________________________ > mpls mailing list > mpls@lists.ietf.org > https://www1.ietf.org/mailman/listinfo/mpls > _______________________________________________ mpls mailing list mpls@lists.ietf.org https://www1.ietf.org/mailman/listinfo/mpls From mpls-bounces@lists.ietf.org Mon Feb 13 16:35:48 2006 Received: from localhost.cnri.reston.va.us ([127.0.0.1] helo=megatron.ietf.org) by megatron.ietf.org with esmtp (Exim 4.32) id 1F8lMK-0007cY-4E; Mon, 13 Feb 2006 16:35:48 -0500 Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org) by megatron.ietf.org with esmtp (Exim 4.32) id 1F8lMH-0007cT-Da for mpls@megatron.ietf.org; Mon, 13 Feb 2006 16:35:45 -0500 Received: from ietf-mx.ietf.org (ietf-mx [132.151.6.1]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id QAA25155 for ; Mon, 13 Feb 2006 16:34:00 -0500 (EST) Received: from mail126.messagelabs.com ([216.82.250.99]) by ietf-mx.ietf.org with smtp (Exim 4.43) id 1F8lZv-0006lh-TJ for mpls@ietf.org; Mon, 13 Feb 2006 16:49:54 -0500 X-VirusChecked: Checked X-Env-Sender: luyuanfang@att.com X-Msg-Ref: server-13.tower-126.messagelabs.com!1139866472!9618399!17 X-StarScan-Version: 5.5.9.1; banners=-,-,- X-Originating-IP: [134.24.146.4] Received: (qmail 12223 invoked from network); 13 Feb 2006 21:35:32 -0000 Received: from unknown (HELO attrh3i.attrh.att.com) (134.24.146.4) by server-13.tower-126.messagelabs.com with SMTP; 13 Feb 2006 21:35:32 -0000 Received: from kcclust06evs1.ugd.att.com (135.38.164.88) by attrh3i.attrh.att.com (7.2.052) id 43D3BB52002FDE11; Mon, 13 Feb 2006 16:35:32 -0500 X-MimeOLE: Produced By Microsoft Exchange V6.5.7226.0 Content-class: urn:content-classes:message MIME-Version: 1.0 Content-Type: text/plain; charset="US-ASCII" Content-Transfer-Encoding: quoted-printable Subject: RE: [mpls] LDP Multicast to WG Document Date: Mon, 13 Feb 2006 15:35:17 -0600 Message-ID: Thread-Topic: [mpls] LDP Multicast to WG Document Thread-Index: AcYrHgQzZgLaGtBeT/+N8VA3mHin9wFx1Chw From: "Fang, Luyuan, ALABS" To: "George Swallow" , X-Spam-Score: 0.0 (/) X-Scan-Signature: 69a74e02bbee44ab4f8eafdbcedd94a1 Content-Transfer-Encoding: quoted-printable Cc: X-BeenThere: mpls@lists.ietf.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Multi-Protocol Label Switching WG List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Sender: mpls-bounces@lists.ietf.org Errors-To: mpls-bounces@lists.ietf.org Support. - Luyuan=20 -----Original Message----- From: mpls-bounces@lists.ietf.org [mailto:mpls-bounces@lists.ietf.org] On Behalf Of George Swallow Sent: Monday, February 06, 2006 7:51 AM To: mpls@ietf.org Subject: [mpls] LDP Multicast to WG Document It has been requested that=20 Label Distribution Protocol Extensions for Point-to-Multipoint and Multipoint-to-Multipoint Label Switched Paths draft-minei-wijnands-mpls-ldp-p2mp-00 become a MPLS WG document. Please indicate your support or objections by the end of this week. Thanks, ...George =3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D= =3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D= =3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D George Swallow Cisco Systems (978) 936-1398 1414 Massachusetts Avenue Boxborough, MA 01719 _______________________________________________ mpls mailing list mpls@lists.ietf.org https://www1.ietf.org/mailman/listinfo/mpls _______________________________________________ mpls mailing list mpls@lists.ietf.org https://www1.ietf.org/mailman/listinfo/mpls From mpls-bounces@lists.ietf.org Mon Feb 13 21:44:11 2006 Received: from localhost.cnri.reston.va.us ([127.0.0.1] helo=megatron.ietf.org) by megatron.ietf.org with esmtp (Exim 4.32) id 1F8qAk-0007tf-VN; Mon, 13 Feb 2006 21:44:10 -0500 Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org) by megatron.ietf.org with esmtp (Exim 4.32) id 1F8qAj-0007tU-4W for mpls@megatron.ietf.org; Mon, 13 Feb 2006 21:44:09 -0500 Received: from ietf-mx.ietf.org (ietf-mx [132.151.6.1]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id VAA18905 for ; Mon, 13 Feb 2006 21:42:24 -0500 (EST) Received: from szxga03-in.huawei.com ([61.144.161.55] helo=huawei.com) by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1F8qON-000153-Hx for mpls@ietf.org; Mon, 13 Feb 2006 21:58:21 -0500 Received: from huawei.com (szxga03-in [172.24.2.9]) by szxga03-in.huawei.com (iPlanet Messaging Server 5.2 HotFix 1.25 (built Mar 3 2004)) with ESMTP id <0IUN00ISMP2O73@szxga03-in.huawei.com> for mpls@ietf.org; Tue, 14 Feb 2006 10:47:12 +0800 (CST) Received: from szxml01-in ([172.24.1.3]) by szxga03-in.huawei.com (iPlanet Messaging Server 5.2 HotFix 1.25 (built Mar 3 2004)) with ESMTP id <0IUN001XSP2NGI@szxga03-in.huawei.com> for mpls@ietf.org; Tue, 14 Feb 2006 10:47:12 +0800 (CST) Received: from c50408 ([10.111.12.77]) by szxml01-in.huawei.com (iPlanet Messaging Server 5.2 HotFix 1.25 (built Mar 3 2004)) with ESMTPA id <0IUN00BN7PHGW6@szxml01-in.huawei.com>; Tue, 14 Feb 2006 10:56:04 +0800 (CST) Date: Tue, 14 Feb 2006 10:40:17 +0800 From: Cao Wei Subject: Re: [mpls] LDP Multicast to WG Document To: mpls@ietf.org Message-id: <00b301c6310f$fdc05a70$4d0c6f0a@china.huawei.com> MIME-version: 1.0 X-MIMEOLE: Produced By Microsoft MimeOLE V6.00.2900.2180 X-Mailer: Microsoft Outlook Express 6.00.2900.2180 X-Priority: 3 X-MSMail-priority: Normal X-Spam-Score: 0.5 (/) X-Scan-Signature: f60fbf3dbcaca652b6d10036f0630412 Cc: Thomas Morin X-BeenThere: mpls@lists.ietf.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Multi-Protocol Label Switching WG List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Content-Type: multipart/mixed; boundary="===============0013881787==" Sender: mpls-bounces@lists.ietf.org Errors-To: mpls-bounces@lists.ietf.org This is a multi-part message in MIME format. --===============0013881787== Content-type: multipart/alternative; boundary="Boundary_(ID_CubpAVjlD90Uh7ZU0ah71g)" This is a multi-part message in MIME format. --Boundary_(ID_CubpAVjlD90Uh7ZU0ah71g) Content-type: text/plain; charset=gb2312 Content-Transfer-Encoding: 7BIT Salability is a important issue for multicast. The load will be very heavy to maintain large number of multicast route entry in control plane. If used in MVPN environment mpls p2mp will face to the requirement to support more and more VPNs. And I also think reconvergence is a tougher problem for multicast (PIM or other) than unicast. Currently unicast routing protocols already have many techniques to reduce the impact of route change, but multicast depends on unicast and reconstructing forwarding tree needs more time. Further more, packet loss caused by reconvergence have more impact on multicast traffic than unicast traffic because of less of retransmitting mechanism for multicast and the property of multicast application. MPLS have bring a lot of benefit to unicast forwarding such as FRR and TE, I think it is good if mpls solution can do something for multicast in this aspect. So I think more consideration at design stage on these aspects will show its advantage. Thanks. Have a good day! ----- Original Message ----- From: "Thomas Morin" To: "IJsbrand Wijnands" Cc: Sent: Saturday, February 11, 2006 5:52 AM Subject: Re: [mpls] LDP Multicast to WG Document >I believe liushuying was perhaps more worried about control plane load, > at reconvergence, for a high number of P2MP tunnels. > Though the concern is valid, I would say that things should roughly be > comparable to what happens with PIM. But I think it is fair to say that > this aspect requires consideration in the solution design. > > Cheers, > > -Thomas > > IJsbrand Wijnands: >> >> We have some ideas on how to minimize the traffic loss during >> switchover, but I'm not sure if we can prevent it without some kind of >> FRR mechanism. >> >> Thx, >> >> Ice. >> >> BTW, I support make this a WG document. >> >> >> On Feb 9, 2006, at 7:56 AM, liushuying wrote: >> >> > Hi folks, >> > I support this draft becoming a WG document. >> > >> > However,i am about to ask a question. >> > >> > 1) 2.3.2.4. Upstream LSR change >> > >> > If, for a given node Z participating in a P2MP LSP , the >> > upstream LSR changes, say from U to U', then Z MUST update its >> > forwarding state by deleting the state for label L, allocating a new >> > label, L', for , and installing the forwarding state for L'. >> > In >> > addition Z MUST send a Label Map to U' and send a Label >> > Withdraw to U. >> > >> > The question: >> > When a large quantity of P2MP LSPs exists in MPLS networks, >> > if unicast routing information changes, there may be many LSRs >> > whose upstream LSRs have changed in every P2MP LSP, each of them >> > sends a Label Withdraw message >> > to its old upstream LSR and a Label Map message to its new upstream >> > LSR at the same time, >> > so the load of every LSR will enhance sharply and last for a long >> > time. >> > As a result, the time of traffic disruption in every P2MP LSP will >> > last for a long time, >> > and so many packets will be lost. >> > >> > Thanks >> > Shuying Liu >> > >> > >> > ----- Original Message ----- >> >> Date: Mon, 06 Feb 2006 07:50:51 -0500 >> >> From: George Swallow >> >> Subject: [mpls] LDP Multicast to WG Document >> >> To: mpls@ietf.org >> >> Message-ID: <20060206125051.3E3BD17B472@SwallowPB.local> >> >> >> >> It has been requested that >> >> >> >> Label Distribution Protocol Extensions for Point-to-Multipoint and >> >> Multipoint-to-Multipoint Label Switched Paths >> >> draft-minei-wijnands-mpls-ldp-p2mp-00 >> >> >> >> become a MPLS WG document. >> >> >> >> Please indicate your support or objections by the end of this week. >> >> >> >> Thanks, >> >> >> >> ...George >> >> >> >> ====================================================================== >> >> == >> >> George Swallow Cisco Systems (978) >> >> 936-1398 >> >> 1414 Massachusetts Avenue >> >> Boxborough, MA 01719 >> >> >> >> >> >> >> >> >> >> >> >> ------------------------------ >> >> >> >> _______________________________________________ >> >> mpls mailing list >> >> mpls@lists.ietf.org >> >> https://www1.ietf.org/mailman/listinfo/mpls >> >> >> >> >> _______________________________________________ >> mpls mailing list >> mpls@lists.ietf.org >> https://www1.ietf.org/mailman/listinfo/mpls > > > _______________________________________________ > mpls mailing list > mpls@lists.ietf.org > https://www1.ietf.org/mailman/listinfo/mpls --Boundary_(ID_CubpAVjlD90Uh7ZU0ah71g) Content-type: text/html; charset=gb2312 Content-Transfer-Encoding: 7BIT
Salability is a important issue for multicast. The load will be very heavy to maintain

large number of multicast route entry in control plane. If used in MVPN  environment

mpls p2mp  will face to the requirement to support more and more VPNs.

 

And I also think reconvergence is a tougher problem for multicast (PIM or other)

than unicast. Currently unicast routing protocols already have many techniques

to reduce the impact of route change, but multicast depends on unicast

and reconstructing forwarding tree needs more time. Further more, packet

loss caused by reconvergence have more impact on multicast traffic

than unicast traffic because of less of retransmitting mechanism for multicast

and the property of multicast application.

 

MPLS have bring a lot of benefit to unicast forwarding such as FRR and TE,

I think it is good if mpls solution can do something for multicast in this

aspect.

 

So I think more consideration at design stage on these aspects will show

its advantage.

 

Thanks.

Have a good day!

----- Original Message -----
From: "Thomas Morin" <thomas.morin@rd.francetelecom.com>
To: "IJsbrand Wijnands" <ice@cisco.com>
Cc: <mpls@ietf.org>
Sent: Saturday, February 11, 2006 5:52 AM
Subject: Re: [mpls] LDP Multicast to WG Document


>I believe liushuying was perhaps more worried about control plane load,
> at reconvergence, for a high number of P2MP tunnels.
> Though the concern is valid, I would say that things should roughly be
> comparable to what happens with PIM. But I think it is fair to say that
> this aspect requires consideration in the solution design.
>
> Cheers,
>
> -Thomas
>
> IJsbrand Wijnands:
>>
>> We have some ideas on how to minimize the traffic loss during 
>> switchover, but I'm not sure if we can prevent it without some kind of 
>> FRR mechanism.
>>
>> Thx,
>>
>> Ice.
>>
>> BTW, I support make this a WG document.
>>
>>
>> On Feb 9, 2006, at 7:56 AM, liushuying wrote:
>>
>> > Hi folks,
>> >     I support this draft becoming a WG document.
>> >
>> >     However,i am about to ask a  question.
>> >
>> >    1) 2.3.2.4.  Upstream LSR change
>> >
>> >    If, for a given node Z participating in a P2MP LSP <X, Y>, the
>> >    upstream LSR changes, say from U to U', then Z MUST update its
>> >    forwarding state by deleting the state for label L, allocating a new
>> >    label, L', for <X,Y>, and installing the forwarding state for L'.  
>> > In
>> >    addition Z MUST send a Label Map <X, Y, L'> to U' and send a Label
>> >    Withdraw <X, Y, L> to U.
>> >
>> >   The question:
>> >   When a large quantity of P2MP LSPs exists in MPLS networks,
>> >   if unicast routing information changes, there may be many LSRs
>> >   whose upstream LSRs have changed in every P2MP LSP, each of them 
>> > sends a Label Withdraw message
>> >   to its old upstream LSR and a Label Map message to its new upstream 
>> > LSR  at the same time,
>> >   so the load of every LSR will enhance sharply and last for a long 
>> > time.
>> >   As a result, the time of traffic disruption in every P2MP LSP will 
>> > last for a long time,
>> >   and so many packets will be lost.
>> >
>> >   Thanks
>> >   Shuying Liu
>> >
>> >
>> > ----- Original Message -----
>> >> Date: Mon, 06 Feb 2006 07:50:51 -0500
>> >> From: George Swallow <swallow@cisco.com>
>> >> Subject: [mpls] LDP Multicast to WG Document
>> >> To: mpls@ietf.org
>> >> Message-ID: <20060206125051.3E3BD17B472@SwallowPB.local>
>> >>
>> >> It has been requested that
>> >>
>> >> Label Distribution Protocol Extensions for Point-to-Multipoint and
>> >>             Multipoint-to-Multipoint Label Switched Paths
>> >>                 draft-minei-wijnands-mpls-ldp-p2mp-00
>> >>
>> >> become a MPLS WG document.
>> >>
>> >> Please indicate your support or objections by the end of this week.
>> >>
>> >> Thanks,
>> >>
>> >> ...George
>> >>
>> >> ======================================================================
>> >> ==
>> >> George Swallow             Cisco Systems                  (978) 
>> >> 936-1398
>> >>                           1414 Massachusetts Avenue
>> >>                           Boxborough, MA 01719
>> >>
>> >>
>> >>
>> >>
>> >>
>> >> ------------------------------
>> >>
>> >> _______________________________________________
>> >> mpls mailing list
>> >> mpls@lists.ietf.org
>> >> https://www1.ietf.org/mailman/listinfo/mpls
>> >>
>>
>>
>> _______________________________________________
>> mpls mailing list
>> mpls@lists.ietf.org
>> https://www1.ietf.org/mailman/listinfo/mpls
>
>
> _______________________________________________
> mpls mailing list
> mpls@lists.ietf.org
> https://www1.ietf.org/mailman/listinfo/mpls
--Boundary_(ID_CubpAVjlD90Uh7ZU0ah71g)-- --===============0013881787== Content-Type: text/plain; charset="us-ascii" MIME-Version: 1.0 Content-Transfer-Encoding: 7bit Content-Disposition: inline _______________________________________________ mpls mailing list mpls@lists.ietf.org https://www1.ietf.org/mailman/listinfo/mpls --===============0013881787==-- From mpls-bounces@lists.ietf.org Tue Feb 14 03:42:20 2006 Received: from localhost.cnri.reston.va.us ([127.0.0.1] helo=megatron.ietf.org) by megatron.ietf.org with esmtp (Exim 4.32) id 1F8vlM-0003yT-GR; Tue, 14 Feb 2006 03:42:20 -0500 Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org) by megatron.ietf.org with esmtp (Exim 4.32) id 1F8vlJ-0003y3-JT for mpls@megatron.ietf.org; Tue, 14 Feb 2006 03:42:17 -0500 Received: from ietf-mx.ietf.org (ietf-mx [132.151.6.1]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id DAA08372 for ; Tue, 14 Feb 2006 03:40:30 -0500 (EST) Received: from p-mail2.rd.francetelecom.com ([195.101.245.16]) by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1F8vz5-0001ba-MQ for mpls@ietf.org; Tue, 14 Feb 2006 03:56:32 -0500 Received: from ftrdmel1.rd.francetelecom.fr ([10.193.117.152]) by ftrdsmtp1.rd.francetelecom.fr with Microsoft SMTPSVC(6.0.3790.1830); Tue, 14 Feb 2006 09:42:13 +0100 X-MimeOLE: Produced By Microsoft Exchange V6.5.7226.0 Content-class: urn:content-classes:message MIME-Version: 1.0 Subject: RE: [mpls] LDP Multicast to WG Document Date: Tue, 14 Feb 2006 09:42:37 +0100 Message-ID: Thread-Topic: [mpls] LDP Multicast to WG Document thread-index: AcYxEUvjhmsfoRXpS1Sv8SEBcgrUnQAMMwJQ From: "LE ROUX Jean-Louis RD-CORE-LAN" To: "Cao Wei" , X-OriginalArrivalTime: 14 Feb 2006 08:42:13.0867 (UTC) FILETIME=[8D86EBB0:01C63142] X-Spam-Score: 0.9 (/) X-Scan-Signature: c8d1e86bb8f49de8156b6392faa4a63b Cc: MORIN Thomas RD-CORE-LAN X-BeenThere: mpls@lists.ietf.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Multi-Protocol Label Switching WG List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Content-Type: multipart/mixed; boundary="===============0518873377==" Sender: mpls-bounces@lists.ietf.org Errors-To: mpls-bounces@lists.ietf.org This is a multi-part message in MIME format. --===============0518873377== Content-class: urn:content-classes:message Content-Type: multipart/alternative; boundary="----_=_NextPart_001_01C63142.8D744DC6" This is a multi-part message in MIME format. ------_=_NextPart_001_01C63142.8D744DC6 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: quoted-printable Hi Cao =20 >MPLS have bring a lot of benefit to unicast forwarding such as FRR and = TE,=20 =20 Here you are refering to MPLS-TE, and not LDP-based MPLS. Note that = unicast LDP does not improve unicast routing, and the same actually = applies for multicast.... =20 >I think it is good if mpls solution can do something for multicast in = this >aspect.=20 =20 If you want FRR and TE you can rely on P2MP RSVP-TE. =20 Regards, =20 JL =20 =20 ________________________________ De : mpls-bounces@lists.ietf.org [mailto:mpls-bounces@lists.ietf.org] = De la part de Cao Wei Envoy=E9 : mardi 14 f=E9vrier 2006 03:40 =C0 : mpls@ietf.org Cc : MORIN Thomas RD-CORE-LAN Objet : Re: [mpls] LDP Multicast to WG Document =09 =09 Salability is a important issue for multicast. The load will be very = heavy to maintain =09 large number of multicast route entry in control plane. If used in MVPN = environment =09 mpls p2mp will face to the requirement to support more and more VPNs.=20 =09 =20 =09 And I also think reconvergence is a tougher problem for multicast (PIM = or other)=20 =09 than unicast. Currently unicast routing protocols already have many = techniques =09 to reduce the impact of route change, but multicast depends on unicast=20 =09 and reconstructing forwarding tree needs more time. Further more, = packet =09 loss caused by reconvergence have more impact on multicast traffic =09 than unicast traffic because of less of retransmitting mechanism for = multicast =09 and the property of multicast application. =09 =20 =09 MPLS have bring a lot of benefit to unicast forwarding such as FRR and = TE,=20 =09 I think it is good if mpls solution can do something for multicast in = this =09 aspect.=20 =09 =20 =09 So I think more consideration at design stage on these aspects will = show=20 =09 its advantage.=20 =09 =20 =09 Thanks.=20 =09 Have a good day! =09 ----- Original Message -----=20 From: "Thomas Morin" To: "IJsbrand Wijnands" Cc: Sent: Saturday, February 11, 2006 5:52 AM Subject: Re: [mpls] LDP Multicast to WG Document =09 =09 >I believe liushuying was perhaps more worried about control plane = load, > at reconvergence, for a high number of P2MP tunnels.=20 > Though the concern is valid, I would say that things should roughly = be > comparable to what happens with PIM. But I think it is fair to say = that > this aspect requires consideration in the solution design. >=20 > Cheers, >=20 > -Thomas >=20 > IJsbrand Wijnands: >>=20 >> We have some ideas on how to minimize the traffic loss during =20 >> switchover, but I'm not sure if we can prevent it without some kind = of =20 >> FRR mechanism. >>=20 >> Thx, >>=20 >> Ice. >>=20 >> BTW, I support make this a WG document. >>=20 >>=20 >> On Feb 9, 2006, at 7:56 AM, liushuying wrote: >>=20 >> > Hi folks, >> > I support this draft becoming a WG document. >> > >> > However,i am about to ask a question. >> > >> > 1) 2.3.2.4. Upstream LSR change >> > >> > If, for a given node Z participating in a P2MP LSP , the >> > upstream LSR changes, say from U to U', then Z MUST update its >> > forwarding state by deleting the state for label L, allocating = a new >> > label, L', for , and installing the forwarding state for = L'. =20 >> > In >> > addition Z MUST send a Label Map to U' and send a = Label >> > Withdraw to U. >> > >> > The question: >> > When a large quantity of P2MP LSPs exists in MPLS networks, >> > if unicast routing information changes, there may be many LSRs >> > whose upstream LSRs have changed in every P2MP LSP, each of them = =20 >> > sends a Label Withdraw message >> > to its old upstream LSR and a Label Map message to its new = upstream =20 >> > LSR at the same time, >> > so the load of every LSR will enhance sharply and last for a = long =20 >> > time. >> > As a result, the time of traffic disruption in every P2MP LSP = will =20 >> > last for a long time, >> > and so many packets will be lost. >> > >> > Thanks >> > Shuying Liu >> > >> > >> > ----- Original Message ----- >> >> Date: Mon, 06 Feb 2006 07:50:51 -0500 >> >> From: George Swallow >> >> Subject: [mpls] LDP Multicast to WG Document >> >> To: mpls@ietf.org >> >> Message-ID: <20060206125051.3E3BD17B472@SwallowPB.local> >> >> >> >> It has been requested that >> >> >> >> Label Distribution Protocol Extensions for Point-to-Multipoint = and >> >> Multipoint-to-Multipoint Label Switched Paths >> >> draft-minei-wijnands-mpls-ldp-p2mp-00 >> >> >> >> become a MPLS WG document. >> >> >> >> Please indicate your support or objections by the end of this = week. >> >> >> >> Thanks, >> >> >> >> ...George >> >> >> >> = =3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D= =3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D= =3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=20 >> >> =3D=3D >> >> George Swallow Cisco Systems (978) =20 >> >> 936-1398 >> >> 1414 Massachusetts Avenue >> >> Boxborough, MA 01719 >> >> >> >> >> >> >> >> >> >> >> >> ------------------------------ >> >> >> >> _______________________________________________ >> >> mpls mailing list >> >> mpls@lists.ietf.org >> >> https://www1.ietf.org/mailman/listinfo/mpls >> >> >>=20 >>=20 >> _______________________________________________ >> mpls mailing list >> mpls@lists.ietf.org >> https://www1.ietf.org/mailman/listinfo/mpls >=20 >=20 > _______________________________________________ > mpls mailing list > mpls@lists.ietf.org > https://www1.ietf.org/mailman/listinfo/mpls ------_=_NextPart_001_01C63142.8D744DC6 Content-Type: text/html; charset="iso-8859-1" Content-Transfer-Encoding: quoted-printable
Hi Cao
 
>MPLS=20 have bring a lot of benefit to unicast forwarding such as FRR and TE,=20
 
Here=20 you are refering to MPLS-TE, and not LDP-based MPLS. Note that unicast = LDP does=20 not improve unicast routing, and the same actually applies for=20 multicast....
 

>I think it = is good if=20 mpls solution can do something for multicast in this

>aspect.=20
 
If you want FRR and TE you can = rely on P2MP=20 RSVP-TE.
 
Regards,
 
JL
 
 


De : = mpls-bounces@lists.ietf.org=20 [mailto:mpls-bounces@lists.ietf.org] De la part de Cao=20 Wei
Envoy=E9 : mardi 14 f=E9vrier 2006 = 03:40
=C0 :=20 mpls@ietf.org
Cc : MORIN Thomas=20 RD-CORE-LAN
Objet : Re: [mpls] LDP Multicast to WG=20 Document

Salability is a important issue for multicast. The = load will=20 be very heavy to maintain

large number of multicast route entry = in=20 control plane. If used in MVPN  environment

mpls = p2mp  will=20 face to the requirement to support more and more VPNs.=20

 

And I also think reconvergence is a tougher = problem for=20 multicast (PIM or other)

than unicast. Currently unicast = routing=20 protocols already have many techniques

to reduce the impact of = route=20 change, but multicast depends on unicast

and reconstructing = forwarding=20 tree needs more time. Further more, packet

loss caused by = reconvergence=20 have more impact on multicast traffic

than unicast traffic = because of=20 less of retransmitting mechanism for multicast

and the property = of=20 multicast application.

 

MPLS have bring a lot of = benefit=20 to unicast forwarding such as FRR and TE,

I think it is good = if mpls=20 solution can do something for multicast in this

aspect.=20

 

So I think more consideration at design stage on = these=20 aspects will show

its advantage.

 

Thanks. =

Have a good day!

----- Original = Message=20 -----
From: "Thomas Morin" <thomas.morin@rd.francet= elecom.com>
To:=20 "IJsbrand Wijnands" <ice@cisco.com>
Cc: <mpls@ietf.org>
Sent: Saturday, = February=20 11, 2006 5:52 AM
Subject: Re: [mpls] LDP Multicast to WG=20 Document


>I believe liushuying was perhaps more worried = about=20 control plane load,
> at reconvergence, for a high number of = P2MP=20 tunnels.
> Though the concern is valid, I would say that things = should=20 roughly be
> comparable to what happens with PIM. But I think it = is fair=20 to say that
> this aspect requires consideration in the solution = design.
>
> Cheers,
>
> -Thomas
> =
>=20 IJsbrand Wijnands:
>>
>> We have some ideas on how = to=20 minimize the traffic loss during 
>> switchover, but = I'm not=20 sure if we can prevent it without some kind of 
>> FRR=20 mechanism.
>>
>> Thx,
>>
>>=20 Ice.
>>
>> BTW, I support make this a WG=20 document.
>>
>>
>> On Feb 9, 2006, at = 7:56 AM,=20 liushuying wrote:
>>
>> > Hi folks,
>>=20 >     I support this draft becoming a WG=20 document.
>> >
>> >     = However,i=20 am about to ask a  question.
>> >
>>=20 >    1) 2.3.2.4.  Upstream LSR = change
>>=20 >
>> >    If, for a given node Z = participating=20 in a P2MP LSP <X, Y>, the
>> >    = upstream=20 LSR changes, say from U to U', then Z MUST update its
>>=20 >    forwarding state by deleting the state for = label L,=20 allocating a new
>> >    label, L', for=20 <X,Y>, and installing the forwarding state for L'.  =20
>> > In
>> >    addition Z = MUST send a=20 Label Map <X, Y, L'> to U' and send a Label
>>=20 >    Withdraw <X, Y, L> to U.
>>=20 >
>> >   The question:
>> = >  =20 When a large quantity of P2MP LSPs exists in MPLS = networks,
>>=20 >   if unicast routing information changes, there may be = many=20 LSRs
>> >   whose upstream LSRs have changed in = every=20 P2MP LSP, each of them 
>> > sends a Label Withdraw=20 message
>> >   to its old upstream LSR and a = Label Map=20 message to its new upstream 
>> > LSR  at the = same=20 time,
>> >   so the load of every LSR will = enhance=20 sharply and last for a long 
>> > time.
>>=20 >   As a result, the time of traffic disruption in every = P2MP LSP=20 will 
>> > last for a long time,
>>=20 >   and so many packets will be lost.
>>=20 >
>> >   Thanks
>> >   = Shuying=20 Liu
>> >
>> >
>> > ----- Original = Message=20 -----
>> >> Date: Mon, 06 Feb 2006 07:50:51 = -0500
>>=20 >> From: George Swallow <swallow@cisco.com>
>> = >>=20 Subject: [mpls] LDP Multicast to WG Document
>> >> To: = mpls@ietf.org
>> >> = Message-ID:=20 <20060206125051= .3E3BD17B472@SwallowPB.local>
>>=20 >>
>> >> It has been requested that
>>=20 >>
>> >> Label Distribution Protocol Extensions = for=20 Point-to-Multipoint and
>>=20 = >>           = ; =20 Multipoint-to-Multipoint Label Switched Paths
>>=20 = >>           = ;     =20 draft-minei-wijnands-mpls-ldp-p2mp-00
>> >>
>> = >> become a MPLS WG document.
>> >>
>> = >>=20 Please indicate your support or objections by the end of this=20 week.
>> >>
>> >> Thanks,
>>=20 >>
>> >> ...George
>> = >>
>>=20 >>=20 = =3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D= =3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D= =3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=20
>> >> =3D=3D
>> >> George=20 = Swallow           =  =20 Cisco=20 = Systems           =       =20 (978) 
>> >> 936-1398
>>=20 = >>           = ;            =    =20 1414 Massachusetts Avenue
>>=20 = >>           = ;            =    =20 Boxborough, MA 01719
>> >>
>> = >>
>>=20 >>
>> >>
>> >>
>> = >>=20 ------------------------------
>> >>
>> = >>=20 _______________________________________________
>> >> = mpls=20 mailing list
>> >> mpls@lists.ietf.org
>> = >>=20 https://www1.ietf.or= g/mailman/listinfo/mpls
>>=20 >>
>>
>>
>>=20 _______________________________________________
>> mpls = mailing=20 list
>> mpls@lists.ietf.org
>> = https://www1.ietf.or= g/mailman/listinfo/mpls
>=20
>
> = _______________________________________________
> mpls=20 mailing list
> mpls@lists.ietf.org
> https://www1.ietf.or= g/mailman/listinfo/mpls
------_=_NextPart_001_01C63142.8D744DC6-- --===============0518873377== Content-Type: text/plain; charset="us-ascii" MIME-Version: 1.0 Content-Transfer-Encoding: 7bit Content-Disposition: inline _______________________________________________ mpls mailing list mpls@lists.ietf.org https://www1.ietf.org/mailman/listinfo/mpls --===============0518873377==-- From mpls-bounces@lists.ietf.org Tue Feb 14 05:59:52 2006 Received: from localhost.cnri.reston.va.us ([127.0.0.1] helo=megatron.ietf.org) by megatron.ietf.org with esmtp (Exim 4.32) id 1F8xuR-00044k-RX; Tue, 14 Feb 2006 05:59:51 -0500 Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org) by megatron.ietf.org with esmtp (Exim 4.32) id 1F8xuF-00043J-3z for mpls@megatron.ietf.org; Tue, 14 Feb 2006 05:59:39 -0500 Received: from ietf-mx.ietf.org (ietf-mx [132.151.6.1]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id FAA15728 for ; Tue, 14 Feb 2006 05:57:51 -0500 (EST) From: benjamin.niven-jenkins@bt.com Received: from smtp2.smtp.bt.com ([217.32.164.150]) by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1F8xsg-0004y9-1U for mpls@ietf.org; Tue, 14 Feb 2006 05:58:06 -0500 Received: from i2km97-ukbr.domain1.systemhost.net ([193.113.197.30]) by smtp2.smtp.bt.com with Microsoft SMTPSVC(6.0.3790.211); Tue, 14 Feb 2006 10:43:34 +0000 Received: from i2km86-ukdy.domain1.systemhost.net ([193.113.30.79]) by i2km97-ukbr.domain1.systemhost.net with Microsoft SMTPSVC(5.0.2195.6713); Tue, 14 Feb 2006 10:43:18 +0000 X-MimeOLE: Produced By Microsoft Exchange V6.5.7226.0 Content-class: urn:content-classes:message MIME-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: quoted-printable Date: Tue, 14 Feb 2006 10:43:17 -0000 Message-ID: Thread-Topic: draft-ietf-mpls-p2mp-oam-reqs Thread-Index: AcYxU3cBbXvIfIZlRve1AQTH/fcKkQ== To: X-OriginalArrivalTime: 14 Feb 2006 10:43:18.0783 (UTC) FILETIME=[77C120F0:01C63153] X-Spam-Score: 0.3 (/) X-Scan-Signature: f607d15ccc2bc4eaf3ade8ffa8af02a0 Content-Transfer-Encoding: quoted-printable Cc: Subject: [mpls] draft-ietf-mpls-p2mp-oam-reqs X-BeenThere: mpls@lists.ietf.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Multi-Protocol Label Switching WG List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Sender: mpls-bounces@lists.ietf.org Errors-To: mpls-bounces@lists.ietf.org Colleagues, Following discussions both inside and outside of BT I have been giving P2MP OAM some thought and have come to the conclusion that P2MP OAM must be unidirectional in nature. P2MP LSPs are uni-directional in nature. It is the tailend router that must take the appropriate consequent actions in the first place - e.g. dropping traffic if it is misconnected to a P2MP LSP that it should not be etc. It is not practical for the headend of a P2MP LSP to receive acknowledgements from every tailend router in response to a Connectivity Verification (CV) probe because the number of responses received could be very large (e.g. if there are lots of tailends and/or lots of P2MP LSPs orginating from the same headend router). This is compounded if proactive CV is performed and delaying responses to 'spread them out' is not a practical solution for proactive CV IMO. CV sweeps where the connectivity between the headend and each tailend is tested in turn is also not practical for proactive CV. Therefore I would request that an appropriate requirement be inserted into draft-ietf-mpls-p2mp-oam-reqs to reflect the requirement that proactive P2MP OAM must be unidirectional. Note: once a defect has been detected by the uni-directional proactive OAM other OAM tools/techniques (which may be bidirectional in nature) can be triggered such as route tracing etc. Below is some suggested text for inclusion in section 4.2 that reflects this requirement. "Continuous path connectivity and SLA measurement mechanisms for P2MP LSPs MUST be unidirectional in nature so that the ingress LER is not overwhelmed with responses from egress LERs. If a fault is detected by an egress LER the detecting LER MUST take the appropriate consequent actions which MAY include raising an alarm (e.g. an SNMP trap) and/or informing the ingress LER of the fault." The following text in section 4.2 may have to be modified to align with the requirement I am suggesting in order to clarify what timeouts it is referring to as by default the headend LER will not expect responses from tailend LERs in response to proactive CV or SLA measurement mechanisms. "It must be possible for the operator (or an automated process) to stipulate a timeout after which the failure to see a response shall be flagged as an error." Ben --=20 Ben Niven-Jenkins Network Architect, BT Exact =20 E-mail: benjamin.niven-jenkins@bt.com=20 Office: +44 (0)1473 648225 Mobile: +44 (0)7918 077205 Fax: +44 (0)1332 578827 _______________________________________________ mpls mailing list mpls@lists.ietf.org https://www1.ietf.org/mailman/listinfo/mpls From mpls-bounces@lists.ietf.org Tue Feb 14 08:57:05 2006 Received: from localhost.cnri.reston.va.us ([127.0.0.1] helo=megatron.ietf.org) by megatron.ietf.org with esmtp (Exim 4.32) id 1F90fx-0005qC-Da; Tue, 14 Feb 2006 08:57:05 -0500 Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org) by megatron.ietf.org with esmtp (Exim 4.32) id 1F90fv-0005pC-9E for mpls@megatron.ietf.org; Tue, 14 Feb 2006 08:57:03 -0500 Received: from ietf-mx.ietf.org (ietf-mx [132.151.6.1]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id IAA27461 for ; Tue, 14 Feb 2006 08:55:16 -0500 (EST) Received: from rose.ctd.hcltech.com ([202.54.64.23]) by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1F90ti-0002SR-IK for mpls@ietf.org; Tue, 14 Feb 2006 09:11:21 -0500 Content-Class: urn:content-classes:message X-MessageTextProcessor: DisclaimIt (2.50.252) [HCL Technologies Limited] Received: from Ganesh.ctd.hcltech.com ([202.54.64.2]) by rose.ctd.hcltech.com with Microsoft SMTPSVC(5.0.2195.6713); Tue, 14 Feb 2006 19:26:38 +0530 Received: by Ganesh.ctd.hcltech.com with Internet Mail Service (5.5.2653.19) id <179FDPF5>; Tue, 14 Feb 2006 19:26:50 +0530 Message-ID: <434F1CE611459F45BBC351FEB5A83F4335E861@kavithai.ctd.hcltech.com> From: "Vijayanand C - CTD, Chennai." Content-Transfer-Encoding: quoted-printable To: "Loa Andersson" , Subject: RE: [mpls] draft-raggarwa-mpls-rsvp-upstream-00 for wg doc? Date: Tue, 14 Feb 2006 19:26:49 +0530 X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2800.1106 MIME-Version: 1.0 X-Mailer: Internet Mail Service (5.5.2653.19) Content-Type: text/plain; charset="iso-8859-1" X-OriginalArrivalTime: 14 Feb 2006 13:56:38.0828 (UTC) FILETIME=[79EB86C0:01C6316E] X-Spam-Score: 0.3 (/) X-Scan-Signature: d0bdc596f8dd1c226c458f0b4df27a88 Content-Transfer-Encoding: quoted-printable Cc: X-BeenThere: mpls@lists.ietf.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Multi-Protocol Label Switching WG List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Sender: mpls-bounces@lists.ietf.org Errors-To: mpls-bounces@lists.ietf.org I have a question/suggestion here applicable to both the drafts- While the downstream(Rd) indicates its capability to accept upstream = labels from its peer(Ru),would nt it be desirable for it to advertise a label = range it can accept. This would avoid problems of the upstream assigned label distributed by a peer(Ru) colliding with an LSRs(Rd) own downstream assigned label which it has distributed out to its other peers(other = than Ru) for other FECs/flows, especially when the upstream label is not = tunneled in ip or mpls. Regards, Vijay > -----Original Message----- > From: mpls-bounces@lists.ietf.org=20 > [mailto:mpls-bounces@lists.ietf.org]On > Behalf Of Loa Andersson > Sent: Friday, February 03, 2006 9:46 PM > To: mpls@ietf.org > Subject: [mpls] draft-raggarwa-mpls-rsvp-upstream-00 for wg doc? >=20 >=20 > All, >=20 > the authors of draft-raggarwa-mpls-rsvp-upstream-00 > has requested that it is made a working group document. >=20 > Please review, comment and respond to the working group mailing > list if you support it becoming a wg or not. >=20 > /Loa and George >=20 > PS >=20 > yes - there are two separate polls one for >=20 > draft-raggarwa-mpls-ldp-upstream-00 > and one for > draft-raggarwa-mpls-rsvp-upstream-00 >=20 > :) >=20 >=20 > --=20 > Loa Andersson >=20 > Principal Networking Architect > Acreo AB phone: +46 8 632 77 14 > Isafjordsgatan 22 mobile: +46 739 81 21 64 > Kista, Sweden email: loa.andersson@acreo.se > loa@pi.se >=20 _______________________________________________ > mpls mailing list > mpls@lists.ietf.org > https://www1.ietf.org/mailman/listinfo/mpls >=20 DISCLAIMER=20 This message and any attachment(s) contained here are information that = is confidential, proprietary to HCL Technologies=20 and its customers. Contents may be privileged or otherwise protected by = law. The information is solely intended for the=20 individual or the entity it is addressed to. If you are not the intended = recipient of this message, you are not authorized to=20 read, forward, print, retain, copy or disseminate this message or any = part of it. If you have received this e-mail in error,=20 please notify the sender immediately by return e-mail and delete it from = your computer _______________________________________________ mpls mailing list mpls@lists.ietf.org https://www1.ietf.org/mailman/listinfo/mpls From mpls-bounces@lists.ietf.org Tue Feb 14 10:13:46 2006 Received: from localhost.cnri.reston.va.us ([127.0.0.1] helo=megatron.ietf.org) by megatron.ietf.org with esmtp (Exim 4.32) id 1F91sA-0007uC-4Y; Tue, 14 Feb 2006 10:13:46 -0500 Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org) by megatron.ietf.org with esmtp (Exim 4.32) id 1F91s9-0007tk-1R for mpls@megatron.ietf.org; Tue, 14 Feb 2006 10:13:45 -0500 Received: from ietf-mx.ietf.org (ietf-mx [132.151.6.1]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id KAA03064 for ; Tue, 14 Feb 2006 10:11:59 -0500 (EST) Received: from rtp-iport-2.cisco.com ([64.102.122.149]) by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1F925z-0004zz-7v for mpls@ietf.org; Tue, 14 Feb 2006 10:28:03 -0500 Received: from rtp-core-2.cisco.com ([64.102.124.13]) by rtp-iport-2.cisco.com with ESMTP; 14 Feb 2006 10:13:37 -0500 X-IronPort-AV: i="4.02,114,1139202000"; d="scan'208"; a="82363496:sNHT31064664" Received: from [10.83.15.57] (rtp-tnadeau-vpn8.cisco.com [10.83.15.57]) by rtp-core-2.cisco.com (8.12.10/8.12.6) with SMTP id k1EFDX6I016534; Tue, 14 Feb 2006 10:13:34 -0500 (EST) In-Reply-To: References: Mime-Version: 1.0 (Apple Message framework v746.2) Content-Type: text/plain; charset=US-ASCII; delsp=yes; format=flowed Message-Id: Content-Transfer-Encoding: 7bit From: "Thomas D. Nadeau" Subject: Re: [mpls] draft-ietf-mpls-p2mp-oam-reqs Date: Tue, 14 Feb 2006 10:13:31 -0500 To: benjamin.niven-jenkins@bt.com X-Mailer: Apple Mail (2.746.2) X-Spam-Score: 0.0 (/) X-Scan-Signature: b280b4db656c3ca28dd62e5e0b03daa8 Content-Transfer-Encoding: 7bit Cc: mpls@ietf.org X-BeenThere: mpls@lists.ietf.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Multi-Protocol Label Switching WG List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Sender: mpls-bounces@lists.ietf.org Errors-To: mpls-bounces@lists.ietf.org Yes, I agree this is a good addition to the text that makes complete sense. --Tom > Colleagues, > > Following discussions both inside and outside of BT I have been giving > P2MP OAM some thought and have come to the conclusion that P2MP OAM > must > be unidirectional in nature. > > P2MP LSPs are uni-directional in nature. > > It is the tailend router that must take the appropriate consequent > actions in the first place - e.g. dropping traffic if it is > misconnected > to a P2MP LSP that it should not be etc. > > It is not practical for the headend of a P2MP LSP to receive > acknowledgements from every tailend router in response to a > Connectivity > Verification (CV) probe because the number of responses received could > be very large (e.g. if there are lots of tailends and/or lots of P2MP > LSPs orginating from the same headend router). This is compounded if > proactive CV is performed and delaying responses to 'spread them > out' is > not a practical solution for proactive CV IMO. CV sweeps where the > connectivity between the headend and each tailend is tested in turn is > also not practical for proactive CV. > > Therefore I would request that an appropriate requirement be inserted > into draft-ietf-mpls-p2mp-oam-reqs to reflect the requirement that > proactive P2MP OAM must be unidirectional. Note: once a defect has > been > detected by the uni-directional proactive OAM other OAM tools/ > techniques > (which may be bidirectional in nature) can be triggered such as route > tracing etc. > > Below is some suggested text for inclusion in section 4.2 that > reflects > this requirement. > > "Continuous path connectivity and SLA measurement mechanisms for P2MP > LSPs MUST be unidirectional in nature so that the ingress LER is not > overwhelmed with responses from egress LERs. If a fault is > detected by > an egress LER the detecting LER MUST take the appropriate consequent > actions which MAY include raising an alarm (e.g. an SNMP trap) and/or > informing the ingress LER of the fault." > > The following text in section 4.2 may have to be modified to align > with > the requirement I am suggesting in order to clarify what timeouts > it is > referring to as by default the headend LER will not expect responses > from tailend LERs in response to proactive CV or SLA measurement > mechanisms. > > "It must be possible for the operator (or an automated process) to > stipulate a timeout after which the failure to see a response shall be > flagged as an error." > > > Ben > > -- > Ben Niven-Jenkins > Network Architect, BT Exact > > E-mail: benjamin.niven-jenkins@bt.com > Office: +44 (0)1473 648225 > Mobile: +44 (0)7918 077205 > Fax: +44 (0)1332 578827 > > _______________________________________________ > mpls mailing list > mpls@lists.ietf.org > https://www1.ietf.org/mailman/listinfo/mpls _______________________________________________ mpls mailing list mpls@lists.ietf.org https://www1.ietf.org/mailman/listinfo/mpls From mpls-bounces@lists.ietf.org Wed Feb 15 04:05:22 2006 Received: from localhost.cnri.reston.va.us ([127.0.0.1] helo=megatron.ietf.org) by megatron.ietf.org with esmtp (Exim 4.32) id 1F9IbC-0000ww-6f; Wed, 15 Feb 2006 04:05:22 -0500 Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org) by megatron.ietf.org with esmtp (Exim 4.32) id 1F9IbA-0000w1-G8 for mpls@megatron.ietf.org; Wed, 15 Feb 2006 04:05:20 -0500 Received: from ietf-mx.ietf.org (ietf-mx [132.151.6.1]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id EAA21741 for ; Wed, 15 Feb 2006 04:03:32 -0500 (EST) Received: from astro.systems.pipex.net ([62.241.163.6]) by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1F9Ip9-0001CJ-Ox for mpls@ietf.org; Wed, 15 Feb 2006 04:19:48 -0500 Received: from pc6 (1Cust139.tnt101.lnd4.gbr.da.uu.net [213.116.50.139]) by astro.systems.pipex.net (Postfix) with SMTP id F33D4E000326; Wed, 15 Feb 2006 09:05:06 +0000 (GMT) Message-ID: <000901c63206$64e416a0$0601a8c0@pc6> From: "Tom Petch" To: "Thomas D. Nadeau" , References: Subject: Re: [mpls] draft-ietf-mpls-p2mp-oam-reqs Date: Tue, 14 Feb 2006 18:37:22 +0100 MIME-Version: 1.0 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: 7bit X-Priority: 3 X-MSMail-Priority: Normal X-Mailer: Microsoft Outlook Express 6.00.2800.1106 X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2800.1106 X-Spam-Score: 0.5 (/) X-Scan-Signature: 6e922792024732fb1bb6f346e63517e4 Content-Transfer-Encoding: 7bit Cc: mpls@ietf.org X-BeenThere: mpls@lists.ietf.org X-Mailman-Version: 2.1.5 Precedence: list Reply-To: Tom Petch List-Id: Multi-Protocol Label Switching WG List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Sender: mpls-bounces@lists.ietf.org Errors-To: mpls-bounces@lists.ietf.org One tiny quibble; the current, SNMP preferred term is notification rather than trap. Tom Petch ----- Original Message ----- From: "Thomas D. Nadeau" To: Cc: Sent: Tuesday, February 14, 2006 4:13 PM Subject: Re: [mpls] draft-ietf-mpls-p2mp-oam-reqs > > Yes, I agree this is a good addition to the > text that makes complete sense. > > --Tom > > > > Colleagues, > > > > Following discussions both inside and outside of BT I have been giving > > P2MP OAM some thought and have come to the conclusion that P2MP OAM > > must > > be unidirectional in nature. > > > > P2MP LSPs are uni-directional in nature. > > > > It is the tailend router that must take the appropriate consequent > > actions in the first place - e.g. dropping traffic if it is > > misconnected > > to a P2MP LSP that it should not be etc. > > > > It is not practical for the headend of a P2MP LSP to receive > > acknowledgements from every tailend router in response to a > > Connectivity > > Verification (CV) probe because the number of responses received could > > be very large (e.g. if there are lots of tailends and/or lots of P2MP > > LSPs orginating from the same headend router). This is compounded if > > proactive CV is performed and delaying responses to 'spread them > > out' is > > not a practical solution for proactive CV IMO. CV sweeps where the > > connectivity between the headend and each tailend is tested in turn is > > also not practical for proactive CV. > > > > Therefore I would request that an appropriate requirement be inserted > > into draft-ietf-mpls-p2mp-oam-reqs to reflect the requirement that > > proactive P2MP OAM must be unidirectional. Note: once a defect has > > been > > detected by the uni-directional proactive OAM other OAM tools/ > > techniques > > (which may be bidirectional in nature) can be triggered such as route > > tracing etc. > > > > Below is some suggested text for inclusion in section 4.2 that > > reflects > > this requirement. > > > > "Continuous path connectivity and SLA measurement mechanisms for P2MP > > LSPs MUST be unidirectional in nature so that the ingress LER is not > > overwhelmed with responses from egress LERs. If a fault is > > detected by > > an egress LER the detecting LER MUST take the appropriate consequent > > actions which MAY include raising an alarm (e.g. an SNMP trap) and/or > > informing the ingress LER of the fault." > > > > The following text in section 4.2 may have to be modified to align > > with > > the requirement I am suggesting in order to clarify what timeouts > > it is > > referring to as by default the headend LER will not expect responses > > from tailend LERs in response to proactive CV or SLA measurement > > mechanisms. > > > > "It must be possible for the operator (or an automated process) to > > stipulate a timeout after which the failure to see a response shall be > > flagged as an error." > > > > > > Ben > > > > -- > > Ben Niven-Jenkins > > Network Architect, BT Exact > > > > E-mail: benjamin.niven-jenkins@bt.com > > Office: +44 (0)1473 648225 > > Mobile: +44 (0)7918 077205 > > Fax: +44 (0)1332 578827 > > > > _______________________________________________ > > mpls mailing list > > mpls@lists.ietf.org > > https://www1.ietf.org/mailman/listinfo/mpls > > _______________________________________________ > mpls mailing list > mpls@lists.ietf.org > https://www1.ietf.org/mailman/listinfo/mpls _______________________________________________ mpls mailing list mpls@lists.ietf.org https://www1.ietf.org/mailman/listinfo/mpls From mpls-bounces@lists.ietf.org Wed Feb 15 05:57:52 2006 Received: from localhost.cnri.reston.va.us ([127.0.0.1] helo=megatron.ietf.org) by megatron.ietf.org with esmtp (Exim 4.32) id 1F9KM4-0004jI-M5; Wed, 15 Feb 2006 05:57:52 -0500 Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org) by megatron.ietf.org with esmtp (Exim 4.32) id 1F9KM3-0004jD-9M for mpls@megatron.ietf.org; Wed, 15 Feb 2006 05:57:51 -0500 Received: from ietf-mx.ietf.org (ietf-mx [132.151.6.1]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id FAA28404 for ; Wed, 15 Feb 2006 05:56:05 -0500 (EST) Received: from rtp-iport-1.cisco.com ([64.102.122.148]) by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1F9Ka3-0004kr-K9 for mpls@ietf.org; Wed, 15 Feb 2006 06:12:20 -0500 Received: from rtp-core-2.cisco.com ([64.102.124.13]) by rtp-iport-1.cisco.com with ESMTP; 15 Feb 2006 02:57:42 -0800 X-BrightmailFiltered: true X-Brightmail-Tracker: AAAAAA== X-IronPort-AV: i="4.02,116,1139212800"; d="scan'208,217"; a="21921718:sNHT41450404" Received: from xbh-rtp-201.amer.cisco.com (xbh-rtp-201.cisco.com [64.102.31.12]) by rtp-core-2.cisco.com (8.12.10/8.12.6) with ESMTP id k1FAvc6H022847; Wed, 15 Feb 2006 05:57:39 -0500 (EST) Received: from xmb-rtp-213.amer.cisco.com ([64.102.31.112]) by xbh-rtp-201.amer.cisco.com with Microsoft SMTPSVC(6.0.3790.211); Wed, 15 Feb 2006 05:57:38 -0500 X-MimeOLE: Produced By Microsoft Exchange V6.5 Content-class: urn:content-classes:message MIME-Version: 1.0 Subject: Re: [mpls] draft-ietf-mpls-p2mp-oam-reqs Date: Wed, 15 Feb 2006 05:57:38 -0500 Message-ID: Thread-Topic: [mpls] draft-ietf-mpls-p2mp-oam-reqs Thread-Index: AcYyDv2r73M3TyJtSL6PqRBFxQGhLwAD6SHb From: "Tom Nadeau \(tnadeau\)" To: "Tom Petch" , X-OriginalArrivalTime: 15 Feb 2006 10:57:38.0550 (UTC) FILETIME=[A2A0E960:01C6321E] X-Spam-Score: 0.0 (/) X-Scan-Signature: c0aa019322dfce838bd8604f5a841b57 Cc: mpls@ietf.org X-BeenThere: mpls@lists.ietf.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Multi-Protocol Label Switching WG List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Content-Type: multipart/mixed; boundary="===============1690620496==" Sender: mpls-bounces@lists.ietf.org Errors-To: mpls-bounces@lists.ietf.org This is a multi-part message in MIME format. --===============1690620496== Content-class: urn:content-classes:message Content-Type: multipart/alternative; boundary="----_=_NextPart_001_01C6321E.A2590AA9" This is a multi-part message in MIME format. ------_=_NextPart_001_01C6321E.A2590AA9 Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: quoted-printable Indeed. Will use the correct term. -----Original Message----- From: Tom Petch [mailto:nwnetworks@dial.pipex.com] Sent: Wed Feb 15 04:05:39 2006 To: Tom Nadeau (tnadeau); benjamin.niven-jenkins@bt.com Cc: mpls@ietf.org Subject: Re: [mpls] draft-ietf-mpls-p2mp-oam-reqs One tiny quibble; the current, SNMP preferred term is notification = rather than trap. Tom Petch ----- Original Message ----- From: "Thomas D. Nadeau" To: Cc: Sent: Tuesday, February 14, 2006 4:13 PM Subject: Re: [mpls] draft-ietf-mpls-p2mp-oam-reqs > > Yes, I agree this is a good addition to the > text that makes complete sense. > > --Tom > > > > Colleagues, > > > > Following discussions both inside and outside of BT I have been = giving > > P2MP OAM some thought and have come to the conclusion that P2MP OAM > > must > > be unidirectional in nature. > > > > P2MP LSPs are uni-directional in nature. > > > > It is the tailend router that must take the appropriate consequent > > actions in the first place - e.g. dropping traffic if it is > > misconnected > > to a P2MP LSP that it should not be etc. > > > > It is not practical for the headend of a P2MP LSP to receive > > acknowledgements from every tailend router in response to a > > Connectivity > > Verification (CV) probe because the number of responses received = could > > be very large (e.g. if there are lots of tailends and/or lots of = P2MP > > LSPs orginating from the same headend router). This is compounded = if > > proactive CV is performed and delaying responses to 'spread them > > out' is > > not a practical solution for proactive CV IMO. CV sweeps where the > > connectivity between the headend and each tailend is tested in turn = is > > also not practical for proactive CV. > > > > Therefore I would request that an appropriate requirement be = inserted > > into draft-ietf-mpls-p2mp-oam-reqs to reflect the requirement that > > proactive P2MP OAM must be unidirectional. Note: once a defect has > > been > > detected by the uni-directional proactive OAM other OAM tools/ > > techniques > > (which may be bidirectional in nature) can be triggered such as = route > > tracing etc. > > > > Below is some suggested text for inclusion in section 4.2 that > > reflects > > this requirement. > > > > "Continuous path connectivity and SLA measurement mechanisms for = P2MP > > LSPs MUST be unidirectional in nature so that the ingress LER is not > > overwhelmed with responses from egress LERs. If a fault is > > detected by > > an egress LER the detecting LER MUST take the appropriate consequent > > actions which MAY include raising an alarm (e.g. an SNMP trap) = and/or > > informing the ingress LER of the fault." > > > > The following text in section 4.2 may have to be modified to align > > with > > the requirement I am suggesting in order to clarify what timeouts > > it is > > referring to as by default the headend LER will not expect responses > > from tailend LERs in response to proactive CV or SLA measurement > > mechanisms. > > > > "It must be possible for the operator (or an automated process) to > > stipulate a timeout after which the failure to see a response shall = be > > flagged as an error." > > > > > > Ben > > > > -- > > Ben Niven-Jenkins > > Network Architect, BT Exact > > > > E-mail: benjamin.niven-jenkins@bt.com > > Office: +44 (0)1473 648225 > > Mobile: +44 (0)7918 077205 > > Fax: +44 (0)1332 578827 > > > > _______________________________________________ > > mpls mailing list > > mpls@lists.ietf.org > > https://www1.ietf.org/mailman/listinfo/mpls > > _______________________________________________ > mpls mailing list > mpls@lists.ietf.org > https://www1.ietf.org/mailman/listinfo/mpls ------_=_NextPart_001_01C6321E.A2590AA9 Content-Type: text/html; charset="us-ascii" Content-Transfer-Encoding: quoted-printable Re: [mpls] draft-ietf-mpls-p2mp-oam-reqs

Indeed.  Will use the correct term.


 -----Original Message-----
From:   Tom Petch [mailto:nwnetworks@dial.pipex.co= m]
Sent:   Wed Feb 15 04:05:39 2006
To:     Tom Nadeau (tnadeau); = benjamin.niven-jenkins@bt.com
Cc:     mpls@ietf.org
Subject:        Re: [mpls] = draft-ietf-mpls-p2mp-oam-reqs

One tiny quibble; the current, SNMP preferred term is notification = rather than
trap.

Tom Petch

----- Original Message -----
From: "Thomas D. Nadeau" <tnadeau@cisco.com>
To: <benjamin.niven-jenkins@bt.com>
Cc: <mpls@ietf.org>
Sent: Tuesday, February 14, 2006 4:13 PM
Subject: Re: [mpls] draft-ietf-mpls-p2mp-oam-reqs


>
> Yes, I agree this is a good addition to the
> text that makes complete sense.
>
> --Tom
>
>
> > Colleagues,
> >
> > Following discussions both inside and outside of BT I have = been giving
> > P2MP OAM some thought and have come to the conclusion that = P2MP OAM
> > must
> > be unidirectional in nature.
> >
> > P2MP LSPs are uni-directional in nature.
> >
> > It is the tailend router that must take the appropriate = consequent
> > actions in the first place - e.g. dropping traffic if it = is
> > misconnected
> > to a P2MP LSP that it should not be etc.
> >
> > It is not practical for the headend of a P2MP LSP to = receive
> > acknowledgements from every tailend router in response to = a
> > Connectivity
> > Verification (CV) probe because the number of responses = received could
> > be very large (e.g. if there are lots of tailends and/or lots = of P2MP
> > LSPs orginating from the same headend router).  This is = compounded if
> > proactive CV is performed and delaying responses to 'spread = them
> > out' is
> > not a practical solution for proactive CV IMO.  CV sweeps = where the
> > connectivity between the headend and each tailend is tested in = turn is
> > also not practical for proactive CV.
> >
> > Therefore I would request that an appropriate requirement be = inserted
> > into draft-ietf-mpls-p2mp-oam-reqs to reflect the requirement = that
> > proactive P2MP OAM must be unidirectional.  Note: once a = defect has
> > been
> > detected by the uni-directional proactive OAM other OAM = tools/
> > techniques
> > (which may be bidirectional in nature) can be triggered such = as route
> > tracing etc.
> >
> > Below is some suggested text for inclusion in section 4.2 = that
> > reflects
> > this requirement.
> >
> > "Continuous path connectivity and SLA measurement = mechanisms for P2MP
> > LSPs MUST be unidirectional in nature so that the ingress LER = is not
> > overwhelmed with responses from egress LERs.  If a fault = is
> > detected by
> > an egress LER the detecting LER MUST take the appropriate = consequent
> > actions which MAY include raising an alarm (e.g. an SNMP trap) = and/or
> > informing the ingress LER of the fault."
> >
> > The following text in section 4.2 may have to be modified to = align
> > with
> > the requirement I am suggesting in order to clarify what = timeouts
> > it is
> > referring to as by default the headend LER will not expect = responses
> > from tailend LERs in response to proactive CV or SLA = measurement
> > mechanisms.
> >
> > "It must be possible for the operator (or an automated = process) to
> > stipulate a timeout after which the failure to see a response = shall be
> > flagged as an error."
> >
> >
> > Ben
> >
> > --
> > Ben Niven-Jenkins
> > Network Architect, BT Exact
> >
> > E-mail: benjamin.niven-jenkins@bt.com
> > Office: +44 (0)1473 648225
> > Mobile: +44 (0)7918 077205
> >    Fax: +44 (0)1332 578827
> >
> > _______________________________________________
> > mpls mailing list
> > mpls@lists.ietf.org
> > https://www1.ietf.or= g/mailman/listinfo/mpls
>
> _______________________________________________
> mpls mailing list
> mpls@lists.ietf.org
> https://www1.ietf.or= g/mailman/listinfo/mpls

------_=_NextPart_001_01C6321E.A2590AA9-- --===============1690620496== Content-Type: text/plain; charset="us-ascii" MIME-Version: 1.0 Content-Transfer-Encoding: 7bit Content-Disposition: inline _______________________________________________ mpls mailing list mpls@lists.ietf.org https://www1.ietf.org/mailman/listinfo/mpls --===============1690620496==-- From mpls-bounces@lists.ietf.org Wed Feb 15 08:15:21 2006 Received: from localhost.cnri.reston.va.us ([127.0.0.1] helo=megatron.ietf.org) by megatron.ietf.org with esmtp (Exim 4.32) id 1F9MV7-00079S-3g; Wed, 15 Feb 2006 08:15:21 -0500 Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org) by megatron.ietf.org with esmtp (Exim 4.32) id 1F9MV4-00078X-Sj for mpls@megatron.ietf.org; Wed, 15 Feb 2006 08:15:18 -0500 Received: from ietf-mx.ietf.org (ietf-mx [132.151.6.1]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id IAA07713 for ; Wed, 15 Feb 2006 08:13:31 -0500 (EST) Received: from mail120.messagelabs.com ([216.82.250.83]) by ietf-mx.ietf.org with smtp (Exim 4.43) id 1F9Mj5-0001Ag-IP for mpls@ietf.org; Wed, 15 Feb 2006 08:29:48 -0500 X-VirusChecked: Checked X-Env-Sender: gash@att.com X-Msg-Ref: server-14.tower-120.messagelabs.com!1140009281!9273804!4 X-StarScan-Version: 5.5.9.1; banners=-,-,- X-Originating-IP: [134.24.146.4] Received: (qmail 23490 invoked from network); 15 Feb 2006 13:15:05 -0000 Received: from unknown (HELO attrh3i.attrh.att.com) (134.24.146.4) by server-14.tower-120.messagelabs.com with SMTP; 15 Feb 2006 13:15:05 -0000 Received: from kcclust06evs1.ugd.att.com (135.38.164.88) by attrh3i.attrh.att.com (7.2.052) id 43D3BB520033CE81 for mpls@ietf.org; Wed, 15 Feb 2006 08:15:05 -0500 X-MimeOLE: Produced By Microsoft Exchange V6.5.7226.0 Content-class: urn:content-classes:message MIME-Version: 1.0 Content-Type: text/plain; charset="US-ASCII" Content-Transfer-Encoding: quoted-printable Date: Wed, 15 Feb 2006 07:14:31 -0600 Message-ID: <9473683187ADC049A855ED2DA739ABCA09FA9B22@KCCLUST06EVS1.ugd.att.com> Thread-Topic: I-D ACTION:draft-ietf-avt-hc-over-mpls-protocol-03.txt Thread-Index: AcYLyFsejL/BjwjESlW0JP3AZZAcJwACpOMQCZZP6dAAAV84kA== From: "Ash, Gerald R \(Jerry\), ALABS" To: X-Spam-Score: 0.0 (/) X-Scan-Signature: 41c17b4b16d1eedaa8395c26e9a251c4 Content-Transfer-Encoding: quoted-printable Cc: Subject: [mpls] RE: I-D ACTION:draft-ietf-avt-hc-over-mpls-protocol-03.txt X-BeenThere: mpls@lists.ietf.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Multi-Protocol Label Switching WG List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Sender: mpls-bounces@lists.ietf.org Errors-To: mpls-bounces@lists.ietf.org Hi All, Please review and comment on the updated draft "Protocol Extensions for Header Compression over MPLS" (http://www.ietf.org/internet-drafts/draft-ietf-avt-hc-over-mpls-protoco l-03.txt). The updates are based primarily on comments from Colin Perkins, see http://www1.ietf.org/mail-archive/web/avt/current/msg06257.html. The main changes include the following: 1. Updated terminology Section 2. 2. Revised and expanded introductory material in Section 3 'Header Compression over MPLS Protocol Overview' for clarity. 3. Revised and expanded Section 4 'Protocol Specifications' for clarity. 4. Provided a complete worked example in Section 5 of pseudowire setup and header compression negotiation. =20 Once again, please review and comment on the updated draft. =20 Thanks, Jerry=20 (note: the following is a "manual" I-D ACTION announcement; I-D ACTION announcements did not go out on February 11 for any I-Ds for some unknown reason) -----Original Message----- From: i-d-announce-bounces@ietf.org [mailto:i-d-announce-bounces@ietf.org] On Behalf Of Internet-Drafts@ietf.org Sent: Saturday, February 11, 2006 To: i-d-announce@ietf.org Cc: avt@ietf.org Subject: I-D ACTION:draft-ietf-avt-hc-over-mpls-protocol-03.txt=20 A New Internet-Draft is available from the on-line Internet-Drafts directories. This draft is a work item of the Audio/Video Transport Working Group of the IETF. Title : Protocol Extensions for Header Compression over MPLS Author(s) : J. Ash Filename : draft-ietf-avt-hc-over-mpls-protocol-03.txt Pages : 23 Date : 2006-02-11 =09 VoIP typically uses the encapsulation voice/RTP/UDP/IP. When MPLS labels are added, this becomes voice/RTP/UDP/IP/MPLS-labels. For an MPLS VPN, the packet header is typically 48 bytes, while the voice payload is often no more than 30 bytes, for example. Header compression can significantly reduce the overhead through various compression mechanisms. MPLS is used to route header-compressed (HC) packets over an MPLS LSP without compression/decompression cycles at each router. Such an HC over MPLS capability increases the bandwidth efficiency as well as processing scalability of the maximum number of simultaneous compressed flows that use HC at each router. MPLS pseudowires are used to transport the HC context and other control messages between the ingress and egress MPLS label switched router (LSR). Standard HC methods (e.g., ECRTP, ROHC, etc.) are re-used to determine the context. Each HC scheme operates over a single pseudowire instance very much like it would over a single point-to-point link. A URL for this Internet-Draft is: http://www.ietf.org/internet-drafts/draft-ietf-avt-hc-over-mpls-protocol -03.txt _______________________________________________ mpls mailing list mpls@lists.ietf.org https://www1.ietf.org/mailman/listinfo/mpls From mpls-bounces@lists.ietf.org Thu Feb 16 10:30:35 2006 Received: from localhost.cnri.reston.va.us ([127.0.0.1] helo=megatron.ietf.org) by megatron.ietf.org with esmtp (Exim 4.32) id 1F9l5X-0000t1-58; Thu, 16 Feb 2006 10:30:35 -0500 Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org) by megatron.ietf.org with esmtp (Exim 4.32) id 1F9l5V-0000sD-BD for mpls@megatron.ietf.org; Thu, 16 Feb 2006 10:30:33 -0500 Received: from ietf-mx.ietf.org (ietf-mx [132.151.6.1]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id KAA03352 for ; Thu, 16 Feb 2006 10:28:44 -0500 (EST) Received: from generic.riverstonenet.com ([66.17.149.13] helo=riverstonenet.com) by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1F9lJV-0001WE-I9 for mpls@ietf.org; Thu, 16 Feb 2006 10:45:17 -0500 Received: from gondor.rs.riverstonenet.com by riverstonenet.com (8.9.3+Sun/SMI-SVR4-Yago) id HAA13211; Thu, 16 Feb 2006 07:30:01 -0800 (PST) X-MimeOLE: Produced By Microsoft Exchange V6.5.7226.0 Content-class: urn:content-classes:message MIME-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: quoted-printable Subject: RE: [mpls] draft-raggarwa-mpls-rsvp-upstream-00 for wg doc? Date: Thu, 16 Feb 2006 21:00:06 +0530 Message-ID: Thread-Topic: [mpls] draft-raggarwa-mpls-rsvp-upstream-00 for wg doc? Thread-Index: AcYxbvQfx1TCHldVS2S8mTh2WAbdIABnTGRQ From: "Pal, Anjaneya" To: "Vijayanand C - CTD, Chennai." , "Loa Andersson" , X-Spam-Score: 0.2 (/) X-Scan-Signature: e1b0e72ff1bbd457ceef31828f216a86 Content-Transfer-Encoding: quoted-printable Cc: X-BeenThere: mpls@lists.ietf.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Multi-Protocol Label Switching WG List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Sender: mpls-bounces@lists.ietf.org Errors-To: mpls-bounces@lists.ietf.org Vijay, I think the collision won't happen bcoz Rd will be using different (context-specific) labelspace for the label distributed by peer Ru (as a part of upstream assigned label) and that distributed by itself to other peers (as a part of downstream assigned label). So if Rd support upstream-assigned label bindings then it maintains different ILM tables for different context-specific labelspaces. And when Rd gets a labeled pkt it first determines the context-specific labelspace and hence looks up for the label in the corresponding ILM table. Section 7 of "draft-raggarwa-mpls-upstream-label-01.txt" gives some insight on this. Regards, -Anjan -----Original Message----- From: mpls-bounces@lists.ietf.org [mailto:mpls-bounces@lists.ietf.org] On Behalf Of Vijayanand C - CTD, Chennai. Sent: Tuesday, February 14, 2006 7:27 PM To: Loa Andersson; mpls@ietf.org Subject: RE: [mpls] draft-raggarwa-mpls-rsvp-upstream-00 for wg doc? I have a question/suggestion here applicable to both the drafts- While the downstream(Rd) indicates its capability to accept upstream labels from its peer(Ru),would nt it be desirable for it to advertise a label range it can accept. This would avoid problems of the upstream assigned label distributed by a peer(Ru) colliding with an LSRs(Rd) own downstream assigned label which it has distributed out to its other peers(other than Ru) for other FECs/flows, especially when the upstream label is not tunneled in ip or mpls. Regards, Vijay > -----Original Message----- > From: mpls-bounces@lists.ietf.org=20 > [mailto:mpls-bounces@lists.ietf.org]On > Behalf Of Loa Andersson > Sent: Friday, February 03, 2006 9:46 PM > To: mpls@ietf.org > Subject: [mpls] draft-raggarwa-mpls-rsvp-upstream-00 for wg doc? >=20 >=20 > All, >=20 > the authors of draft-raggarwa-mpls-rsvp-upstream-00 > has requested that it is made a working group document. >=20 > Please review, comment and respond to the working group mailing > list if you support it becoming a wg or not. >=20 > /Loa and George >=20 > PS >=20 > yes - there are two separate polls one for >=20 > draft-raggarwa-mpls-ldp-upstream-00 > and one for > draft-raggarwa-mpls-rsvp-upstream-00 >=20 > :) >=20 >=20 > --=20 > Loa Andersson >=20 > Principal Networking Architect > Acreo AB phone: +46 8 632 77 14 > Isafjordsgatan 22 mobile: +46 739 81 21 64 > Kista, Sweden email: loa.andersson@acreo.se > loa@pi.se >=20 _______________________________________________ > mpls mailing list > mpls@lists.ietf.org > https://www1.ietf.org/mailman/listinfo/mpls >=20 DISCLAIMER=20 This message and any attachment(s) contained here are information that is confidential, proprietary to HCL Technologies=20 and its customers. Contents may be privileged or otherwise protected by law. The information is solely intended for the=20 individual or the entity it is addressed to. If you are not the intended recipient of this message, you are not authorized to=20 read, forward, print, retain, copy or disseminate this message or any part of it. If you have received this e-mail in error,=20 please notify the sender immediately by return e-mail and delete it from your computer _______________________________________________ mpls mailing list mpls@lists.ietf.org https://www1.ietf.org/mailman/listinfo/mpls _______________________________________________ mpls mailing list mpls@lists.ietf.org https://www1.ietf.org/mailman/listinfo/mpls From mpls-bounces@lists.ietf.org Thu Feb 16 10:58:03 2006 Received: from localhost.cnri.reston.va.us ([127.0.0.1] helo=megatron.ietf.org) by megatron.ietf.org with esmtp (Exim 4.32) id 1F9lW7-0005UF-R9; Thu, 16 Feb 2006 10:58:03 -0500 Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org) by megatron.ietf.org with esmtp (Exim 4.32) id 1F9lW5-0005Rx-Rv; Thu, 16 Feb 2006 10:58:01 -0500 Received: from ietf-mx.ietf.org (ietf-mx [132.151.6.1]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id KAA06926; Thu, 16 Feb 2006 10:56:11 -0500 (EST) Received: from bgslc11.burtongroup.com ([63.99.125.13]) by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1F9lkF-0002xF-B7; Thu, 16 Feb 2006 11:12:43 -0500 Received: bgslc11.burtongroup.com 63.99.125.13 from 216.151.229.244 216.151.229.244 via HTTP with MS-WebStorage 6.0.6249 User-Agent: Microsoft-Entourage/11.2.1.051004 Date: Thu, 16 Feb 2006 10:57:44 -0500 From: Irwin Lazar To: , L2VPN , , , Message-ID: Thread-Topic: MPLScon 2006 Program Thread-Index: AcYzEbkg99xz9p8EEdqUmAAKlZoW5A== Mime-version: 1.0 X-Spam-Score: 0.5 (/) X-Scan-Signature: 52f7a77164458f8c7b36b66787c853da Cc: Subject: [mpls] MPLScon 2006 Program X-BeenThere: mpls@lists.ietf.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Multi-Protocol Label Switching WG List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Content-Type: multipart/mixed; boundary="===============1484375130==" Sender: mpls-bounces@lists.ietf.org Errors-To: mpls-bounces@lists.ietf.org > This message is in MIME format. Since your mail reader does not understand this format, some or all of this message may not be legible. --===============1484375130== Content-type: multipart/alternative; boundary="B_3222932264_1089758" > This message is in MIME format. Since your mail reader does not understand this format, some or all of this message may not be legible. --B_3222932264_1089758 Content-type: text/plain; charset="US-ASCII" Content-Transfer-Encoding: 7bit The program for MPLScon 2006 is now available at http://www.mplscon.com/attend/conf_at_a_glance.html MPLScon 2006 takes place May 22-26 at the Marriott Financial Center in NYC, NY. Please let me know if you have any questions. Irwin -- Irwin Lazar, Conference Director, MPLScon http://www.mplscon.com ilazar@burtongroup.com Phone: 703-742-9659 AIM/iChat/Google/MSN/Gizmo/Skype/Yahoo: imlazar --B_3222932264_1089758 Content-type: text/html; charset="US-ASCII" Content-Transfer-Encoding: quoted-printable MPLScon 2006 Program The p= rogram for MPLScon 2006 is now available at http://www.mplscon.com/attend/conf_at_a_glance= .html

MPLScon 2006 takes place May 22-26 at the Marriott Financial Center in NYC,= NY.

Please let me know if you have any questions.

Irwin


--
Irwin Lazar, Conference Director, MPLScon
http://www.mplscon.com
ilazar@burtongroup.com
Phone: 703-742-9659
AIM/iChat/Google/MSN/Gizmo/Skype/Yahoo: imlazar

 --B_3222932264_1089758-- --===============1484375130== Content-Type: text/plain; charset="us-ascii" MIME-Version: 1.0 Content-Transfer-Encoding: 7bit Content-Disposition: inline _______________________________________________ mpls mailing list mpls@lists.ietf.org https://www1.ietf.org/mailman/listinfo/mpls --===============1484375130==-- From mpls-bounces@lists.ietf.org Fri Feb 17 06:19:55 2006 Received: from localhost.cnri.reston.va.us ([127.0.0.1] helo=megatron.ietf.org) by megatron.ietf.org with esmtp (Exim 4.32) id 1FA3eU-0004zB-Hz; Fri, 17 Feb 2006 06:19:54 -0500 Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org) by megatron.ietf.org with esmtp (Exim 4.32) id 1FA3eR-0004z6-5E for mpls@megatron.ietf.org; Fri, 17 Feb 2006 06:19:51 -0500 Received: from willow.neustar.com (willow.neustar.com [209.173.53.84]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id GAA20429 for ; Fri, 17 Feb 2006 06:18:03 -0500 (EST) Received: from stiedprstage1.ietf.org (stiedprstage1.va.neustar.com [10.31.47.10]) by willow.neustar.com (8.12.8/8.12.8) with ESMTP id k1GNo19W000833 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO); Thu, 16 Feb 2006 23:50:01 GMT Received: from ietf by stiedprstage1.ietf.org with local (Exim 4.43) id 1F9ssr-00045R-8F; Thu, 16 Feb 2006 18:50:01 -0500 Content-Type: Multipart/Mixed; Boundary="NextPart" Mime-Version: 1.0 To: i-d-announce@ietf.org From: Internet-Drafts@ietf.org Message-Id: Date: Thu, 16 Feb 2006 18:50:01 -0500 Cc: mpls@ietf.org Subject: [mpls] I-D ACTION:draft-ietf-mpls-multicast-encaps-00.txt X-BeenThere: mpls@lists.ietf.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Multi-Protocol Label Switching WG List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Sender: mpls-bounces@lists.ietf.org Errors-To: mpls-bounces@lists.ietf.org --NextPart A New Internet-Draft is available from the on-line Internet-Drafts directories. This draft is a work item of the Multiprotocol Label Switching Working Group of the IETF. Title : MPLS Multicast Encapsulations Author(s) : T. Eckert, et al. Filename : draft-ietf-mpls-multicast-encaps-00.txt Pages : 9 Date : 2006-2-16 RFC 3032 established two data link layer codepoints for MPLS: one to indicate that the data link layer frame is carrying an MPLS unicast packet, and the other to indicate that the data link layer frame is carrying an MPLS multicast packet. This specification updates RFC3032 by redefining the meaning of these two codepoints. The former "multicast codepoint" is now to be used only on multiaccess media, and it is to mean "the top label of the following label stack is an upstream-assigned label". The former "unicast codepoint" is to be used in all other cases. Whether the data link layer payload is a unicast MPLS packet or a multicast MPLS packet is now to be determined by looking up the top label, rather than by the codepoint. RFC3032 does not specify the destination address to be placed in the "MAC DA" field of an ethernet frame which carries an MPLS multicast packet. This document provides that specification. This document updates RFC 3032 and RFC 4023. A URL for this Internet-Draft is: http://www.ietf.org/internet-drafts/draft-ietf-mpls-multicast-encaps-00.txt To remove yourself from the I-D Announcement list, send a message to i-d-announce-request@ietf.org with the word unsubscribe in the body of the message. You can also visit https://www1.ietf.org/mailman/listinfo/I-D-announce to change your subscription settings. Internet-Drafts are also available by anonymous FTP. Login with the username "anonymous" and a password of your e-mail address. After logging in, type "cd internet-drafts" and then "get draft-ietf-mpls-multicast-encaps-00.txt". A list of Internet-Drafts directories can be found in http://www.ietf.org/shadow.html or ftp://ftp.ietf.org/ietf/1shadow-sites.txt Internet-Drafts can also be obtained by e-mail. Send a message to: mailserv@ietf.org. In the body type: "FILE /internet-drafts/draft-ietf-mpls-multicast-encaps-00.txt". NOTE: The mail server at ietf.org can return the document in MIME-encoded form by using the "mpack" utility. To use this feature, insert the command "ENCODING mime" before the "FILE" command. To decode the response(s), you will need "munpack" or a MIME-compliant mail reader. Different MIME-compliant mail readers exhibit different behavior, especially when dealing with "multipart" MIME messages (i.e. documents which have been split up into multiple messages), so check your local documentation on how to manipulate these messages. Below is the data which will enable a MIME compliant mail reader implementation to automatically retrieve the ASCII version of the Internet-Draft. --NextPart Content-Type: Multipart/Alternative; Boundary="OtherAccess" --OtherAccess Content-Type: Message/External-body; access-type="mail-server"; server="mailserv@ietf.org" Content-Type: text/plain Content-ID: <2006-2-16150232.I-D@ietf.org> ENCODING mime FILE /internet-drafts/draft-ietf-mpls-multicast-encaps-00.txt --OtherAccess Content-Type: Message/External-body; name="draft-ietf-mpls-multicast-encaps-00.txt"; site="ftp.ietf.org"; access-type="anon-ftp"; directory="internet-drafts" Content-Type: text/plain Content-ID: <2006-2-16150232.I-D@ietf.org> --OtherAccess-- --NextPart Content-Type: text/plain; charset="us-ascii" MIME-Version: 1.0 Content-Transfer-Encoding: 7bit Content-Disposition: inline _______________________________________________ mpls mailing list mpls@lists.ietf.org https://www1.ietf.org/mailman/listinfo/mpls --NextPart-- From mpls-bounces@lists.ietf.org Fri Feb 17 09:51:24 2006 Received: from localhost.cnri.reston.va.us ([127.0.0.1] helo=megatron.ietf.org) by megatron.ietf.org with esmtp (Exim 4.32) id 1FA6xA-0002Kf-UD; Fri, 17 Feb 2006 09:51:24 -0500 Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org) by megatron.ietf.org with esmtp (Exim 4.32) id 1FA6vn-0001Gk-KE for mpls@megatron.ietf.org; Fri, 17 Feb 2006 09:49:59 -0500 Received: from ietf-mx.ietf.org (ietf-mx [132.151.6.1]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id IAA28660 for ; Fri, 17 Feb 2006 08:55:48 -0500 (EST) Received: from protext01.itu.ch ([156.106.192.41]) by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1FA3DO-00070i-Tf for mpls@ietf.org; Fri, 17 Feb 2006 05:51:59 -0500 Received: from protext01.itu.ch ([156.106.192.41]) by protext01.itu.ch with Microsoft SMTPSVC(5.0.2195.6713); Fri, 17 Feb 2006 11:36:48 +0100 Received: From mail5.itu.ch ([156.106.192.21]) by protext01.itu.ch (WebShield SMTP v4.5 MR1a); id 114017260819; Fri, 17 Feb 2006 11:36:48 +0100 Received: from Puppy ([156.106.224.72]) by mail5.itu.ch (8.13.5/8.13.5) with SMTP id k1HAalfl476320; Fri, 17 Feb 2006 11:36:47 +0100 (MET) Message-ID: <00d501c633ae$a0dc0e20$48e06a9c@Puppy> From: "Adrian Farrel" To: , References: Subject: Re: [mpls] draft-ietf-mpls-p2mp-oam-reqs Date: Fri, 17 Feb 2006 10:40:50 -0000 MIME-Version: 1.0 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: 7bit X-Priority: 3 X-MSMail-Priority: Normal X-Mailer: Microsoft Outlook Express 6.00.2800.1158 X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2800.1165 X-Greylist: Sender IP whitelisted, not delayed by milter-greylist-2.0.2 (mail5.itu.ch [156.106.192.21]); Fri, 17 Feb 2006 11:36:47 +0100 (MET) X-OriginalArrivalTime: 17 Feb 2006 10:36:48.0660 (UTC) FILETIME=[0E765540:01C633AE] X-Spam-Score: 0.0 (/) X-Scan-Signature: 6e922792024732fb1bb6f346e63517e4 Content-Transfer-Encoding: 7bit Cc: X-BeenThere: mpls@lists.ietf.org X-Mailman-Version: 2.1.5 Precedence: list Reply-To: Adrian Farrel List-Id: Multi-Protocol Label Switching WG List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Sender: mpls-bounces@lists.ietf.org Errors-To: mpls-bounces@lists.ietf.org Ben, I am sympathetic to your concerns and proposal. But we should try to separate requirements from solutions (even if the solutions are obvious consequences of the requirements). Your reasoning for unidirectional OAM is very strong, but isn't the requirement actually that "LSRs or other network resources MUST NOT be overwhelmed by the operation of normal OAM procedures, and measures taken to protect LSRs and network resources against being overwhelmed MUST NOT degrade the operational value or responsiveness of proactive OAM procedures." Presumably your (good) suggestion on the behaviour of an egress LER that detects a fault is actually applicable to *any* LER that detects a fault. I would also like to point out that section 4.2 is intended to refer to "diagnosis" not "detection". This means that bi-directional mechanisms *are* in scope. I believe that your comments are more applicable to section 4.1 Does that sound reasonable? If so I will fold these thoughts into a new revision and bounce it off you before publication. Cheers, Adrian ----- Original Message ----- From: To: Sent: Tuesday, February 14, 2006 10:43 AM Subject: [mpls] draft-ietf-mpls-p2mp-oam-reqs Colleagues, Following discussions both inside and outside of BT I have been giving P2MP OAM some thought and have come to the conclusion that P2MP OAM must be unidirectional in nature. P2MP LSPs are uni-directional in nature. It is the tailend router that must take the appropriate consequent actions in the first place - e.g. dropping traffic if it is misconnected to a P2MP LSP that it should not be etc. It is not practical for the headend of a P2MP LSP to receive acknowledgements from every tailend router in response to a Connectivity Verification (CV) probe because the number of responses received could be very large (e.g. if there are lots of tailends and/or lots of P2MP LSPs orginating from the same headend router). This is compounded if proactive CV is performed and delaying responses to 'spread them out' is not a practical solution for proactive CV IMO. CV sweeps where the connectivity between the headend and each tailend is tested in turn is also not practical for proactive CV. Therefore I would request that an appropriate requirement be inserted into draft-ietf-mpls-p2mp-oam-reqs to reflect the requirement that proactive P2MP OAM must be unidirectional. Note: once a defect has been detected by the uni-directional proactive OAM other OAM tools/techniques (which may be bidirectional in nature) can be triggered such as route tracing etc. Below is some suggested text for inclusion in section 4.2 that reflects this requirement. "Continuous path connectivity and SLA measurement mechanisms for P2MP LSPs MUST be unidirectional in nature so that the ingress LER is not overwhelmed with responses from egress LERs. If a fault is detected by an egress LER the detecting LER MUST take the appropriate consequent actions which MAY include raising an alarm (e.g. an SNMP trap) and/or informing the ingress LER of the fault." The following text in section 4.2 may have to be modified to align with the requirement I am suggesting in order to clarify what timeouts it is referring to as by default the headend LER will not expect responses from tailend LERs in response to proactive CV or SLA measurement mechanisms. "It must be possible for the operator (or an automated process) to stipulate a timeout after which the failure to see a response shall be flagged as an error." Ben -- Ben Niven-Jenkins Network Architect, BT Exact E-mail: benjamin.niven-jenkins@bt.com Office: +44 (0)1473 648225 Mobile: +44 (0)7918 077205 Fax: +44 (0)1332 578827 _______________________________________________ mpls mailing list mpls@lists.ietf.org https://www1.ietf.org/mailman/listinfo/mpls _______________________________________________ mpls mailing list mpls@lists.ietf.org https://www1.ietf.org/mailman/listinfo/mpls From mpls-bounces@lists.ietf.org Fri Feb 17 10:24:39 2006 Received: from localhost.cnri.reston.va.us ([127.0.0.1] helo=megatron.ietf.org) by megatron.ietf.org with esmtp (Exim 4.32) id 1FA7TL-0004FW-IB; Fri, 17 Feb 2006 10:24:39 -0500 Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org) by megatron.ietf.org with esmtp (Exim 4.32) id 1FA7TK-0004Ew-6g for mpls@megatron.ietf.org; Fri, 17 Feb 2006 10:24:38 -0500 Received: from ietf-mx.ietf.org (ietf-mx [132.151.6.1]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id KAA23662 for ; Fri, 17 Feb 2006 10:22:49 -0500 (EST) Received: from rtp-iport-1.cisco.com ([64.102.122.148]) by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1FA7hl-0006Pl-5k for mpls@ietf.org; Fri, 17 Feb 2006 10:39:34 -0500 Received: from rtp-core-1.cisco.com ([64.102.124.12]) by rtp-iport-1.cisco.com with ESMTP; 17 Feb 2006 07:24:28 -0800 X-BrightmailFiltered: true X-Brightmail-Tracker: AAAAAA== X-IronPort-AV: i="4.02,124,1139212800"; d="scan'208"; a="22110635:sNHT358608342" Received: from [10.83.15.58] (rtp-tnadeau-vpn9.cisco.com [10.83.15.58]) by rtp-core-1.cisco.com (8.12.10/8.12.6) with SMTP id k1HFOOPN016480; Fri, 17 Feb 2006 10:24:25 -0500 (EST) In-Reply-To: <00d501c633ae$a0dc0e20$48e06a9c@Puppy> References: <00d501c633ae$a0dc0e20$48e06a9c@Puppy> Mime-Version: 1.0 (Apple Message framework v746.2) X-Priority: 3 Content-Type: text/plain; charset=US-ASCII; delsp=yes; format=flowed Message-Id: Content-Transfer-Encoding: 7bit From: "Thomas D. Nadeau" Subject: Re: [mpls] draft-ietf-mpls-p2mp-oam-reqs Date: Fri, 17 Feb 2006 10:24:18 -0500 To: Adrian Farrel X-Mailer: Apple Mail (2.746.2) X-Spam-Score: 0.0 (/) X-Scan-Signature: 7da5a831c477fb6ef97f379a05fb683c Content-Transfer-Encoding: 7bit Cc: mpls@ietf.org X-BeenThere: mpls@lists.ietf.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Multi-Protocol Label Switching WG List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Sender: mpls-bounces@lists.ietf.org Errors-To: mpls-bounces@lists.ietf.org On Feb 17, 2006, at 5:40 AM, Adrian Farrel wrote: > Ben, > > I am sympathetic to your concerns and proposal. But we should try to > separate requirements from solutions (even if the solutions are > obvious > consequences of the requirements). > > Your reasoning for unidirectional OAM is very strong, but isn't the > requirement actually that "LSRs or other network resources MUST NOT be > overwhelmed by the operation of normal OAM procedures, and measures > taken > to protect LSRs and network resources against being overwhelmed > MUST NOT > degrade the operational value or responsiveness of proactive OAM > procedures." It might also be a good idea to quantify just what "overwhelmed" means in a little more precise terms. I had a number of comments on this WRT the p2p OAM requirements from the IESG during the RFC review, so I suspect the same questions will come up again WRT this document. --Tom > Presumably your (good) suggestion on the behaviour of an egress LER > that > detects a fault is actually applicable to *any* LER that detects a > fault. > > I would also like to point out that section 4.2 is intended to > refer to > "diagnosis" not "detection". This means that bi-directional mechanisms > *are* in scope. I believe that your comments are more applicable to > section 4.1 > > Does that sound reasonable? If so I will fold these thoughts into a > new > revision and bounce it off you before publication. > > Cheers, > Adrian > > ----- Original Message ----- > From: > To: > Sent: Tuesday, February 14, 2006 10:43 AM > Subject: [mpls] draft-ietf-mpls-p2mp-oam-reqs > > > Colleagues, > > Following discussions both inside and outside of BT I have been giving > P2MP OAM some thought and have come to the conclusion that P2MP OAM > must > be unidirectional in nature. > > P2MP LSPs are uni-directional in nature. > > It is the tailend router that must take the appropriate consequent > actions in the first place - e.g. dropping traffic if it is > misconnected > to a P2MP LSP that it should not be etc. > > It is not practical for the headend of a P2MP LSP to receive > acknowledgements from every tailend router in response to a > Connectivity > Verification (CV) probe because the number of responses received could > be very large (e.g. if there are lots of tailends and/or lots of P2MP > LSPs orginating from the same headend router). This is compounded if > proactive CV is performed and delaying responses to 'spread them > out' is > not a practical solution for proactive CV IMO. CV sweeps where the > connectivity between the headend and each tailend is tested in turn is > also not practical for proactive CV. > > Therefore I would request that an appropriate requirement be inserted > into draft-ietf-mpls-p2mp-oam-reqs to reflect the requirement that > proactive P2MP OAM must be unidirectional. Note: once a defect has > been > detected by the uni-directional proactive OAM other OAM tools/ > techniques > (which may be bidirectional in nature) can be triggered such as route > tracing etc. > > Below is some suggested text for inclusion in section 4.2 that > reflects > this requirement. > > "Continuous path connectivity and SLA measurement mechanisms for P2MP > LSPs MUST be unidirectional in nature so that the ingress LER is not > overwhelmed with responses from egress LERs. If a fault is > detected by > an egress LER the detecting LER MUST take the appropriate consequent > actions which MAY include raising an alarm (e.g. an SNMP trap) and/or > informing the ingress LER of the fault." > > The following text in section 4.2 may have to be modified to align > with > the requirement I am suggesting in order to clarify what timeouts > it is > referring to as by default the headend LER will not expect responses > from tailend LERs in response to proactive CV or SLA measurement > mechanisms. > > "It must be possible for the operator (or an automated process) to > stipulate a timeout after which the failure to see a response shall be > flagged as an error." > > > Ben > > -- > Ben Niven-Jenkins > Network Architect, BT Exact > > E-mail: benjamin.niven-jenkins@bt.com > Office: +44 (0)1473 648225 > Mobile: +44 (0)7918 077205 > Fax: +44 (0)1332 578827 > > _______________________________________________ > mpls mailing list > mpls@lists.ietf.org > https://www1.ietf.org/mailman/listinfo/mpls > > > > _______________________________________________ > mpls mailing list > mpls@lists.ietf.org > https://www1.ietf.org/mailman/listinfo/mpls _______________________________________________ mpls mailing list mpls@lists.ietf.org https://www1.ietf.org/mailman/listinfo/mpls From mpls-bounces@lists.ietf.org Fri Feb 17 10:39:47 2006 Received: from localhost.cnri.reston.va.us ([127.0.0.1] helo=megatron.ietf.org) by megatron.ietf.org with esmtp (Exim 4.32) id 1FA7hz-00033v-Qj; Fri, 17 Feb 2006 10:39:47 -0500 Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org) by megatron.ietf.org with esmtp (Exim 4.32) id 1FA7hx-00032S-Gy for mpls@megatron.ietf.org; Fri, 17 Feb 2006 10:39:45 -0500 Received: from ietf-mx.ietf.org (ietf-mx [132.151.6.1]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id KAA27435 for ; Fri, 17 Feb 2006 10:37:55 -0500 (EST) From: neil.2.harrison@bt.com Received: from smtp5.smtp.bt.com ([217.32.164.139]) by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1FA7wM-0007za-Om for mpls@ietf.org; Fri, 17 Feb 2006 10:54:41 -0500 Received: from i2kc07-ukbr.domain1.systemhost.net ([193.113.197.14]) by smtp5.smtp.bt.com with Microsoft SMTPSVC(6.0.3790.211); Fri, 17 Feb 2006 15:39:32 +0000 Received: from i2km07-ukbr.domain1.systemhost.net ([193.113.197.26]) by i2kc07-ukbr.domain1.systemhost.net with Microsoft SMTPSVC(6.0.3790.211); Fri, 17 Feb 2006 15:39:31 +0000 X-MimeOLE: Produced By Microsoft Exchange V6.0.6603.0 Content-class: urn:content-classes:message MIME-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: quoted-printable Subject: RE: [mpls] draft-ietf-mpls-p2mp-oam-reqs Date: Fri, 17 Feb 2006 15:39:31 -0000 Message-ID: <0536FC9B908BEC4597EE721BE6A3538914591DA9@i2km07-ukbr.domain1.systemhost.net> Thread-Topic: [mpls] draft-ietf-mpls-p2mp-oam-reqs Thread-Index: AcYz0dvSDgRhi3XKTj6TJEuU6HJ30AABJRNQ To: , , X-OriginalArrivalTime: 17 Feb 2006 15:39:31.0700 (UTC) FILETIME=[587A4B40:01C633D8] X-Spam-Score: 0.3 (/) X-Scan-Signature: 6640e3bbe8a4d70c4469bcdcbbf0921d Content-Transfer-Encoding: quoted-printable Cc: X-BeenThere: mpls@lists.ietf.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Multi-Protocol Label Switching WG List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Sender: mpls-bounces@lists.ietf.org Errors-To: mpls-bounces@lists.ietf.org Hi Adrian....sounds reasonable to me. We have to separate out OAM into the 'always-on' type and the 'on-demand' type. The former is all about taking local actions to deal with defects as/when they arise....so its needs to be simple and it also need to be processed in a unidirectional sense when we are dealing with the co-ps and co-cs modes as the initial key actions need taking at the sink trail termination point. This becomes esp important when p2mp trails are considered. =20 The 'on-demand' type of OAM is, as you have noted below, all about diagnostics....though I'd also lump PM flows in here because in a well-engineered network you only need this to investigate (hopefully rare) rogue behaviour and its generally not cost-effective to process PM flows on the vast majority of good systems. regards, Neil > -----Original Message----- > From: mpls-bounces@lists.ietf.org=20 > [mailto:mpls-bounces@lists.ietf.org] On Behalf Of Adrian Farrel > Sent: 17 February 2006 10:41 > To: Niven-jenkins,B,Ben,XDE73 R; mpls@ietf.org > Subject: Re: [mpls] draft-ietf-mpls-p2mp-oam-reqs >=20 >=20 > Ben, >=20 > I am sympathetic to your concerns and proposal. But we should=20 > try to separate requirements from solutions (even if the=20 > solutions are obvious consequences of the requirements). >=20 > Your reasoning for unidirectional OAM is very strong, but=20 > isn't the requirement actually that "LSRs or other network=20 > resources MUST NOT be overwhelmed by the operation of normal=20 > OAM procedures, and measures taken to protect LSRs and=20 > network resources against being overwhelmed MUST NOT degrade=20 > the operational value or responsiveness of proactive OAM procedures." >=20 > Presumably your (good) suggestion on the behaviour of an=20 > egress LER that detects a fault is actually applicable to=20 > *any* LER that detects a fault. >=20 > I would also like to point out that section 4.2 is intended=20 > to refer to "diagnosis" not "detection". This means that=20 > bi-directional mechanisms > *are* in scope. I believe that your comments are more=20 > applicable to section 4.1 >=20 > Does that sound reasonable? If so I will fold these thoughts=20 > into a new revision and bounce it off you before publication. >=20 > Cheers, > Adrian >=20 > ----- Original Message -----=20 > From: > To: > Sent: Tuesday, February 14, 2006 10:43 AM > Subject: [mpls] draft-ietf-mpls-p2mp-oam-reqs >=20 >=20 > Colleagues, >=20 > Following discussions both inside and outside of BT I have=20 > been giving P2MP OAM some thought and have come to the=20 > conclusion that P2MP OAM must be unidirectional in nature. >=20 > P2MP LSPs are uni-directional in nature. >=20 > It is the tailend router that must take the appropriate=20 > consequent actions in the first place - e.g. dropping traffic=20 > if it is misconnected to a P2MP LSP that it should not be etc. >=20 > It is not practical for the headend of a P2MP LSP to receive=20 > acknowledgements from every tailend router in response to a=20 > Connectivity Verification (CV) probe because the number of=20 > responses received could be very large (e.g. if there are=20 > lots of tailends and/or lots of P2MP LSPs orginating from the=20 > same headend router). This is compounded if proactive CV is=20 > performed and delaying responses to 'spread them out' is not=20 > a practical solution for proactive CV IMO. CV sweeps where=20 > the connectivity between the headend and each tailend is=20 > tested in turn is also not practical for proactive CV. >=20 > Therefore I would request that an appropriate requirement be=20 > inserted into draft-ietf-mpls-p2mp-oam-reqs to reflect the=20 > requirement that proactive P2MP OAM must be unidirectional. =20 > Note: once a defect has been detected by the uni-directional=20 > proactive OAM other OAM tools/techniques (which may be=20 > bidirectional in nature) can be triggered such as route tracing etc. >=20 > Below is some suggested text for inclusion in section 4.2=20 > that reflects this requirement. >=20 > "Continuous path connectivity and SLA measurement mechanisms=20 > for P2MP LSPs MUST be unidirectional in nature so that the=20 > ingress LER is not overwhelmed with responses from egress=20 > LERs. If a fault is detected by an egress LER the detecting=20 > LER MUST take the appropriate consequent actions which MAY=20 > include raising an alarm (e.g. an SNMP trap) and/or informing=20 > the ingress LER of the fault." >=20 > The following text in section 4.2 may have to be modified to=20 > align with the requirement I am suggesting in order to=20 > clarify what timeouts it is referring to as by default the=20 > headend LER will not expect responses from tailend LERs in=20 > response to proactive CV or SLA measurement mechanisms. >=20 > "It must be possible for the operator (or an automated=20 > process) to stipulate a timeout after which the failure to=20 > see a response shall be flagged as an error." >=20 >=20 > Ben >=20 > --=20 > Ben Niven-Jenkins > Network Architect, BT Exact >=20 > E-mail: benjamin.niven-jenkins@bt.com > Office: +44 (0)1473 648225 > Mobile: +44 (0)7918 077205 > Fax: +44 (0)1332 578827 >=20 > _______________________________________________ > mpls mailing list > mpls@lists.ietf.org > https://www1.ietf.org/mailman/listinfo/mpls >=20 >=20 >=20 > _______________________________________________ > mpls mailing list > mpls@lists.ietf.org > https://www1.ietf.org/mailman/listinfo/mpls >=20 _______________________________________________ mpls mailing list mpls@lists.ietf.org https://www1.ietf.org/mailman/listinfo/mpls From mpls-bounces@lists.ietf.org Tue Feb 21 11:24:30 2006 Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com) by megatron.ietf.org with esmtp (Exim 4.43) id 1FBaHI-0001Xp-RB; Tue, 21 Feb 2006 11:22:16 -0500 Received: from [10.91.34.44] (helo=ietf-mx.ietf.org) by megatron.ietf.org with esmtp (Exim 4.43) id 1FBaHH-0001Xj-5y for mpls@ietf.org; Tue, 21 Feb 2006 11:22:15 -0500 Received: from mx3.equant.com ([199.184.38.93]) by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1FBaHF-0003BO-VV for mpls@ietf.org; Tue, 21 Feb 2006 11:22:15 -0500 Received: from us-res-dms1.domino.globalone.net (mail.internal.equant.com [199.184.38.65]) by mx3.equant.com with ESMTP id k1LGMCMg028750 for ; Tue, 21 Feb 2006 11:22:13 -0500 (EST) Subject: Re: [mpls] draft-raggarwa-mpls-rsvp-upstream-00 for wg doc? To: mpls@ietf.org X-Mailer: Lotus Notes Release 5.0.4 June 8, 2000 Message-ID: From: zubair.ahmad@equant.com Date: Tue, 21 Feb 2006 11:22:10 -0500 X-MIMETrack: Serialize by Router on US-Res-DMS1/Servers/GlobalOne(5012HF429 | October 14, 2003) at 02/21/2006 11:22:12 AM MIME-Version: 1.0 Content-type: text/plain; charset=iso-8859-1 Content-transfer-encoding: quoted-printable X-Spam-Score: 0.2 (/) X-Scan-Signature: f607d15ccc2bc4eaf3ade8ffa8af02a0 Cc: X-BeenThere: mpls@lists.ietf.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Multi-Protocol Label Switching WG List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Errors-To: mpls-bounces@lists.ietf.org Hi, > draft-raggarwa-mpls-ldp-upstream-00 Support. > draft-raggarwa-mpls-rsvp-upstream-00 Support. Regards, Zubair > -----Message d'origine----- > De : mpls-bounces@lists.ietf.org > [mailto:mpls-bounces@lists.ietf.org] De la part de Loa Andersson > Envoy=E9 : vendredi 3 f=E9vrier 2006 17:16 > =C0 : mpls@ietf.org > Objet : [mpls] draft-raggarwa-mpls-rsvp-upstream-00 for wg doc? > > All, > > the authors of draft-raggarwa-mpls-rsvp-upstream-00 > has requested that it is made a working group document. > > Please review, comment and respond to the working group > mailing list if you support it becoming a wg or not. > > /Loa and George > > PS > > yes - there are two separate polls one for > > draft-raggarwa-mpls-ldp-upstream-00 > and one for > draft-raggarwa-mpls-rsvp-upstream-00 > > :) > > > -- > Loa Andersson > > Principal Networking Architect > Acreo AB phone: +46 8 632 77 14 > Isafjordsgatan 22 mobile: +46 739 81 21 64 > Kista, Sweden email: loa.andersson@acreo.se > loa@pi.se > > _______________________________________________ > mpls mailing list > mpls@lists.ietf.org > https://www1.ietf.org/mailman/listinfo/mpls > = _______________________________________________ mpls mailing list mpls@lists.ietf.org https://www1.ietf.org/mailman/listinfo/mpls From mpls-bounces@lists.ietf.org Tue Feb 21 20:47:35 2006 Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com) by megatron.ietf.org with esmtp (Exim 4.43) id 1FBj4K-0000Zo-DB; Tue, 21 Feb 2006 20:45:28 -0500 Received: from [10.91.34.44] (helo=ietf-mx.ietf.org) by megatron.ietf.org with esmtp (Exim 4.43) id 1FBj4J-0000Zj-Od for mpls@ietf.org; Tue, 21 Feb 2006 20:45:27 -0500 Received: from lhrga01-in.huawei.com ([57.66.76.5] helo=huawei.com) by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1FBj4J-00070E-Ft for mpls@ietf.org; Tue, 21 Feb 2006 20:45:27 -0500 Received: from huawei.com ([172.24.2.9]) by lhrga01-in.huawei.com (iPlanet Messaging Server 5.2 HotFix 1.25 (built Mar 3 2004)) with ESMTP id <0IV2007L0EPQFS@lhrga01-in.huawei.com> for mpls@ietf.org; Wed, 22 Feb 2006 01:27:27 +0000 (GMT) Received: from huawei.com (szxga03-in [172.24.2.9]) by szxga03-in.huawei.com (iPlanet Messaging Server 5.2 HotFix 1.25 (built Mar 3 2004)) with ESMTP id <0IV200KVXFQXE8@szxga03-in.huawei.com> for mpls@ietf.org; Wed, 22 Feb 2006 09:49:45 +0800 (CST) Received: from szxml01-in ([172.24.1.3]) by szxga03-in.huawei.com (iPlanet Messaging Server 5.2 HotFix 1.25 (built Mar 3 2004)) with ESMTP id <0IV200J3QFIJY3@szxga03-in.huawei.com> for mpls@ietf.org; Wed, 22 Feb 2006 09:49:45 +0800 (CST) Received: from z18605 ([10.111.12.131]) by szxml01-in.huawei.com (iPlanet Messaging Server 5.2 HotFix 1.25 (built Mar 3 2004)) with ESMTPA id <0IV200EF2G1TPX@szxml01-in.huawei.com> for mpls@ietf.org; Wed, 22 Feb 2006 09:56:17 +0800 (CST) Date: Wed, 22 Feb 2006 09:13:05 +0800 From: Zhang Renhai Subject: Re: [mpls] draft-raggarwa-mpls-rsvp-upstream-00 for wg doc? To: mpls@ietf.org Message-id: <007d01c6374d$22821e00$830c6f0a@huawei.com> MIME-version: 1.0 X-MIMEOLE: Produced By Microsoft MimeOLE V5.50.4807.1700 X-Mailer: Microsoft Outlook Express 5.50.4807.1700 Content-type: text/plain; charset=ISO-8859-1 Content-transfer-encoding: 7BIT X-Priority: 3 X-MSMail-priority: Normal References: <43E381D5.8020008@pi.se> X-Spam-Score: 0.0 (/) X-Scan-Signature: 538aad3a3c4f01d8b6a6477ca4248793 Cc: X-BeenThere: mpls@lists.ietf.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Multi-Protocol Label Switching WG List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Errors-To: mpls-bounces@lists.ietf.org Hi, > draft-raggarwa-mpls-ldp-upstream-00 > draft-raggarwa-mpls-rsvp-upstream-00 Support both. Regards, Zhang ----- Original Message ----- From: "Loa Andersson" To: Sent: Saturday, February 04, 2006 12:16 AM Subject: [mpls] draft-raggarwa-mpls-rsvp-upstream-00 for wg doc? > All, > > the authors of draft-raggarwa-mpls-rsvp-upstream-00 > has requested that it is made a working group document. > > Please review, comment and respond to the working group mailing > list if you support it becoming a wg or not. > > /Loa and George > > PS > > yes - there are two separate polls one for > > draft-raggarwa-mpls-ldp-upstream-00 > and one for > draft-raggarwa-mpls-rsvp-upstream-00 > > :) > > > -- > Loa Andersson > > Principal Networking Architect > Acreo AB phone: +46 8 632 77 14 > Isafjordsgatan 22 mobile: +46 739 81 21 64 > Kista, Sweden email: loa.andersson@acreo.se > loa@pi.se > > _______________________________________________ > mpls mailing list > mpls@lists.ietf.org > https://www1.ietf.org/mailman/listinfo/mpls _______________________________________________ mpls mailing list mpls@lists.ietf.org https://www1.ietf.org/mailman/listinfo/mpls From mpls-bounces@lists.ietf.org Wed Feb 22 03:32:33 2006 Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com) by megatron.ietf.org with esmtp (Exim 4.43) id 1FBpO2-0002Xg-Mf; Wed, 22 Feb 2006 03:30:14 -0500 Received: from [10.91.34.44] (helo=ietf-mx.ietf.org) by megatron.ietf.org with esmtp (Exim 4.43) id 1FBp6B-0001RW-Iw for mpls@ietf.org; Wed, 22 Feb 2006 03:11:47 -0500 Received: from p-mail1.rd.francetelecom.com ([195.101.245.15]) by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1FBots-00063B-Qw for mpls@ietf.org; Wed, 22 Feb 2006 02:59:08 -0500 Received: from ftrdmel1.rd.francetelecom.fr ([10.193.117.152]) by ftrdsmtp2.rd.francetelecom.fr with Microsoft SMTPSVC(6.0.3790.1830); Wed, 22 Feb 2006 08:59:03 +0100 X-MimeOLE: Produced By Microsoft Exchange V6.5.7226.0 Content-class: urn:content-classes:message MIME-Version: 1.0 Date: Wed, 22 Feb 2006 08:59:34 +0100 Message-ID: X-MS-Has-Attach: X-MS-TNEF-Correlator: Thread-Topic: TR: I-D ACTION:draft-leroux-mpls-mp-ldp-reqs-03.txt thread-index: AcY3hes8fx0Mw9e1Tt21ZbXB98Mijg== From: "LE ROUX Jean-Louis RD-CORE-LAN" To: X-OriginalArrivalTime: 22 Feb 2006 07:59:03.0953 (UTC) FILETIME=[D91F6810:01C63785] X-Spam-Score: 0.0 (/) X-Scan-Signature: d8921dd2ebcb07edebf7bfaf4808c2ad Cc: Subject: [mpls] TR: I-D ACTION:draft-leroux-mpls-mp-ldp-reqs-03.txt X-BeenThere: mpls@lists.ietf.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Multi-Protocol Label Switching WG List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Content-Type: multipart/mixed; boundary="===============1867439656==" Errors-To: mpls-bounces@lists.ietf.org This is a multi-part message in MIME format. --===============1867439656== Content-class: urn:content-classes:message Content-Type: multipart/alternative; boundary="----_=_NextPart_001_01C63785.D86FF0D7" This is a multi-part message in MIME format. ------_=_NextPart_001_01C63785.D86FF0D7 Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: quoted-printable Hi all, This is a new revision of the P2MP LDP requirement draft. It accounts for comments received in Vancouver:=20 -We removed solution specific text, related to routing (in previous verison it was stated "the solution MUST not require the use of a multicast routing protocol"), and label allocation on LAN interfaces (the previous version was suggesting upstream label assignement). -We added a requirement for efficient balancing of a set of P2MP LSPs among a set of upstream LSRs on a LAN interface while avoiding data replication (in section 5.9). -We made some rewordings for the sake of clarity. Your comments on this new version would be really appreciated. Best Regards, JL et al. A New Internet-Draft is available from the on-line Internet-Drafts directories. Title : Requirements for point-to-multipoint=20 extensions to the Label Distribution Protocol Author(s) : J. Le Roux, et al. Filename : draft-leroux-mpls-mp-ldp-reqs-03.txt Pages : 16 Date : 2006-2-21 =09 This document lists a set of functional requirements for Label=20 Distribution Protocol (LDP) extensions for setting up point-to- multipoint (P2MP) Label Switched Paths (LSP), in order to deliver=20 point-to-multipoint applications over a Multi Protocol Label=20 Switching (MPLS) infrastructure. It is intended that solutions that=20 specify LDP procedures for setting up P2MP LSP satisfy these=20 requirements. A URL for this Internet-Draft is: http://www.ietf.org/internet-drafts/draft-leroux-mpls-mp-ldp-reqs-03.txt To remove yourself from the I-D Announcement list, send a message to=20 i-d-announce-request at ietf.org with the word unsubscribe in the body of the message. =20 You can also visit https://www1.ietf.org/mailman/listinfo/I-D-announce=20 to change your subscription settings. Internet-Drafts are also available by anonymous FTP. Login with the username "anonymous" and a password of your e-mail address. After logging in, type "cd internet-drafts" and then "get draft-leroux-mpls-mp-ldp-reqs-03.txt". A list of Internet-Drafts directories can be found in http://www.ietf.org/shadow.html=20 or ftp://ftp.ietf.org/ietf/1shadow-sites.txt Internet-Drafts can also be obtained by e-mail. Send a message to: mailserv at ietf.org. In the body type: "FILE /internet-drafts/draft-leroux-mpls-mp-ldp-reqs-03.txt". =09 NOTE: The mail server at ietf.org can return the document in MIME-encoded form by using the "mpack" utility. To use this feature, insert the command "ENCODING mime" before the "FILE" command. To decode the response(s), you will need "munpack" or a MIME-compliant mail reader. Different MIME-compliant mail readers exhibit different behavior, especially when dealing with "multipart" MIME messages (i.e. documents which have been split up into multiple messages), so check your local documentation on how to manipulate these messages. =09 =09 Below is the data which will enable a MIME compliant mail reader implementation to automatically retrieve the ASCII version of the Internet-Draft. =20 _______________________________________________ I-D-Announce mailing list I-D-Announce at ietf.org https://www1.ietf.org/mailman/listinfo/i-d-announce ------_=_NextPart_001_01C63785.D86FF0D7 Content-Type: text/html; charset="us-ascii" Content-Transfer-Encoding: quoted-printable TR: I-D ACTION:draft-leroux-mpls-mp-ldp-reqs-03.txt

Hi all,

This is a new revision of the = P2MP LDP requirement draft.
It accounts for comments = received in Vancouver:
-We removed solution specific = text, related to routing (in previous verison it was stated "the = solution MUST not require the use of a multicast routing = protocol"), and label allocation on LAN interfaces (the previous = version was suggesting upstream label assignement).

-We added a requirement for = efficient balancing of a set of P2MP LSPs among a set of upstream LSRs = on a LAN interface while avoiding data replication (in section = 5.9).

-We made some rewordings for the = sake of clarity.

Your comments on this new version = would be really appreciated.

Best Regards,

JL et al.


A New Internet-Draft is available = from the on-line Internet-Drafts directories.


        Title   =         : Requirements for = point-to-multipoint
           &n= bsp;           &nb= sp;  extensions to the Label Distribution Protocol
        Author(s)       : J. = Le Roux, et al.
        Filename        = : draft-leroux-mpls-mp-ldp-reqs-03.txt
        Pages   =         : 16
        Date    =         : 2006-2-21
       =20
This document lists a set of = functional requirements for Label
   Distribution = Protocol (LDP) extensions for setting up point-to-
   multipoint (P2MP) = Label Switched Paths (LSP), in order to deliver
   point-to-multipoint = applications over a Multi Protocol Label
   Switching (MPLS) = infrastructure. It is intended that solutions that
   specify LDP = procedures for setting up P2MP LSP satisfy these
   = requirements.

A URL for this Internet-Draft = is:
http://www.ietf.org/internet-drafts/draft-leroux-mpls-mp-ldp-reqs-03= .txt

To remove yourself from the I-D = Announcement list, send a message to
i-d-announce-request at ietf.org = with the word unsubscribe in the body of the message. 
You can also visit https://www1.ietf.org/mailman/listinfo/I-D-announce
to change your subscription = settings.


Internet-Drafts are also = available by anonymous FTP. Login with the username
"anonymous" and a = password of your e-mail address. After logging in,
type "cd = internet-drafts" and then
        "get = draft-leroux-mpls-mp-ldp-reqs-03.txt".

A list of Internet-Drafts = directories can be found in
http://www.ietf.org/shadow.html
or ftp://ftp.ietf.org/ietf/1shadow-sites.txt


Internet-Drafts can also be = obtained by e-mail.

Send a message to:
        mailserv at ietf.org.
In the body type:
        "FILE = /internet-drafts/draft-leroux-mpls-mp-ldp-reqs-03.txt".
       =20
NOTE:   The mail = server at ietf.org can return the document in
        MIME-encoded form by using the "mpack" = utility.  To use this
        feature, insert the command "ENCODING = mime" before the "FILE"
        command.  To decode the response(s), you will = need "munpack" or
        a MIME-compliant mail reader.  Different = MIME-compliant mail readers
        exhibit different behavior, especially when dealing = with
        "multipart" MIME messages (i.e. documents = which have been split
        up into multiple messages), so check your local = documentation on
        how to manipulate these messages.
        =        =20
        =        =20
Below is the data which will = enable a MIME compliant mail reader
implementation to automatically = retrieve the ASCII version of the
Internet-Draft.
<ftp://ftp.ietf.org/internet-drafts/draft-leroux-mpls-mp-ldp-re= qs-03.txt>
_______________________________________________
I-D-Announce mailing list
I-D-Announce at ietf.org
https://www1.ietf.org/mailman/listinfo/i-d-announce

------_=_NextPart_001_01C63785.D86FF0D7-- --===============1867439656== Content-Type: text/plain; charset="us-ascii" MIME-Version: 1.0 Content-Transfer-Encoding: 7bit Content-Disposition: inline _______________________________________________ mpls mailing list mpls@lists.ietf.org https://www1.ietf.org/mailman/listinfo/mpls --===============1867439656==-- From mpls-bounces@lists.ietf.org Thu Feb 23 06:45:14 2006 Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com) by megatron.ietf.org with esmtp (Exim 4.43) id 1FCEuI-0003gI-Ni; Thu, 23 Feb 2006 06:45:14 -0500 Received: from [10.91.34.44] (helo=ietf-mx.ietf.org) by megatron.ietf.org with esmtp (Exim 4.43) id 1FCEuH-0003gA-SK for mpls@ietf.org; Thu, 23 Feb 2006 06:45:13 -0500 Received: from mgw2.noc.ntt.com ([210.163.32.69]) by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1FCEuG-0005lm-Ad for mpls@ietf.org; Thu, 23 Feb 2006 06:45:13 -0500 Received: from mop2.noc.ntt.com by mgw2.noc.ntt.com (NTT-Com MailSV) with ESMTP id k1NBj2XL024257 for ; Thu, 23 Feb 2006 20:45:04 +0900 (JST) Received: from mip2.noc.ntt.com (mvi3.noc.ntt.com) by mop2.noc.ntt.com (NTT-Com MailSV) with ESMTP id <0IV5000WU1Z1D9@ntt.com> for mpls@ietf.org; Thu, 23 Feb 2006 20:45:02 +0900 (JST) Date: Thu, 23 Feb 2006 20:44:58 +0900 From: "Yuji KAMITE" Subject: RE: [mpls] draft-raggarwa-mpls-rsvp-upstream-00 for wg doc? In-reply-to: <43E381D5.8020008@pi.se> To: mpls@ietf.org Message-id: <0IV500KWH1Z1R9@ntt.com> MIME-version: 1.0 X-MIMEOLE: Produced By Microsoft MimeOLE V6.00.2800.1506 X-Mailer: Microsoft Office Outlook, Build 11.0.6353 Content-type: text/plain; charset=us-ascii Content-transfer-encoding: 7bit Thread-index: AcYo3fwn3F8+N8W9SAyFq/r3neCUMwPj7urA X-Spam-Score: 0.0 (/) X-Scan-Signature: 4adaf050708fb13be3316a9eee889caa Cc: X-BeenThere: mpls@lists.ietf.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Multi-Protocol Label Switching WG List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Errors-To: mpls-bounces@lists.ietf.org Support. - Yuji > -----Original Message----- > From: mpls-bounces@lists.ietf.org > [mailto:mpls-bounces@lists.ietf.org] On Behalf Of Loa Andersson > Sent: Saturday, February 04, 2006 1:16 AM > To: mpls@ietf.org > Subject: [mpls] draft-raggarwa-mpls-rsvp-upstream-00 for wg doc? > > All, > > the authors of draft-raggarwa-mpls-rsvp-upstream-00 > has requested that it is made a working group document. > > Please review, comment and respond to the working group > mailing list if you support it becoming a wg or not. > > /Loa and George > > PS > > yes - there are two separate polls one for > > draft-raggarwa-mpls-ldp-upstream-00 > and one for > draft-raggarwa-mpls-rsvp-upstream-00 > > :) > > > -- > Loa Andersson > > Principal Networking Architect > Acreo AB phone: +46 8 632 77 14 > Isafjordsgatan 22 mobile: +46 739 81 21 64 > Kista, Sweden email: loa.andersson@acreo.se > loa@pi.se > > _______________________________________________ > mpls mailing list > mpls@lists.ietf.org > https://www1.ietf.org/mailman/listinfo/mpls _______________________________________________ mpls mailing list mpls@lists.ietf.org https://www1.ietf.org/mailman/listinfo/mpls From mpls-bounces@lists.ietf.org Thu Feb 23 10:30:15 2006 Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com) by megatron.ietf.org with esmtp (Exim 4.43) id 1FCIO4-00027D-BC; Thu, 23 Feb 2006 10:28:12 -0500 Received: from [10.91.34.44] (helo=ietf-mx.ietf.org) by megatron.ietf.org with esmtp (Exim 4.43) id 1FCIO3-000278-4M for mpls@ietf.org; Thu, 23 Feb 2006 10:28:11 -0500 Received: from smtp3.smtp.bt.com ([217.32.164.138]) by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1FCIO0-0007Hc-F1 for mpls@ietf.org; Thu, 23 Feb 2006 10:28:11 -0500 Received: from i2km95-ukbr.domain1.systemhost.net ([193.113.197.29]) by smtp3.smtp.bt.com with Microsoft SMTPSVC(6.0.3790.211); Thu, 23 Feb 2006 15:28:00 +0000 Received: from i2km86-ukdy.domain1.systemhost.net ([193.113.30.79]) by i2km95-ukbr.domain1.systemhost.net with Microsoft SMTPSVC(5.0.2195.6713); Thu, 23 Feb 2006 15:28:00 +0000 X-MimeOLE: Produced By Microsoft Exchange V6.5.7226.0 Content-class: urn:content-classes:message MIME-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: quoted-printable Subject: RE: [mpls] TR: I-D ACTION:draft-leroux-mpls-mp-ldp-reqs-03.txt Date: Thu, 23 Feb 2006 15:28:47 -0000 Message-ID: X-MS-Has-Attach: X-MS-TNEF-Correlator: Thread-Topic: [mpls] TR: I-D ACTION:draft-leroux-mpls-mp-ldp-reqs-03.txt Thread-Index: AcY3hes8fx0Mw9e1Tt21ZbXB98MijgBA5BJA From: To: X-OriginalArrivalTime: 23 Feb 2006 15:28:00.0932 (UTC) FILETIME=[BB39F640:01C6388D] X-Spam-Score: 0.2 (/) X-Scan-Signature: 41c17b4b16d1eedaa8395c26e9a251c4 Cc: X-BeenThere: mpls@lists.ietf.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Multi-Protocol Label Switching WG List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Errors-To: mpls-bounces@lists.ietf.org Colleagues, After reading draft-leroux-mpls-mp-ldp-reqs-03 I have the following editorial comments/suggestions: Section 3.1, Paragraphs 1,2,3,4,5,7 - put a blank line after each paragraph. Section 3.1, Paragraph 6 - "A P2MP LSPs is an LSP" =3D> "A P2MP LSP is = an LSP" Section 3.1, Paragraph 8 - "without the need of traffic engineering" = =3D> "without the need for traffic engineering" Section 3.2, Paragraph 1 - you use egress LSR but everywhere else in the document you use Egress LSR. Section 3.2, Paragraph 5 - "This may allow reducing the amount of LDP state to be maintained by a LSR" suggest changing this to "This may allow a reduction in the amount of LDP state that must be maintained by a LSR" Section 5.2, Paragraph 2 - "Such P2MP FEC MUST be distinguished clearly from the exiting P2P FEC." I think you mean 'existing' not 'exiting'. Section 5.8, Paragraph 2 - "Given that P2MP LDP routing must rely on the RIB, the achievement of the following requirements also implies the underlying routing protocols (IGP, etc.)." I think what you're trying to say is something like "Given that P2MP LDP routing must rely on the RIB, the achievement of the following requirements also implies the underlying routing protocols (IGP, etc.) must meet these requirements." Section 5.8.1, Paragraph 2 - "The rerouting time SHOULD be as much as possible minimized so as to reduce traffic disruption." =3D> "The rerouting time SHOULD be minimized as much as possible so as to reduce traffic disruption."=20 Section 5.8.2 - "Traffic disruption SHOULD be as much as possible minimized during such rerouting." =3D> "Traffic disruption SHOULD be minimized as much as possible during such rerouting." and "Unnecessary data duplication during such rerouting SHOULD also be as much as possible minimized." =3D> "Unnecessary data duplication during such rerouting SHOULD also be minimized as much as possible." Section 5.8.3 - Same comments as for Section 5.8.2 Section 5.9, Paragraph 1 - "This requires that the same label be negotiated will all downstream LSRs for the LSP." 'will' =3D> 'with' Section 5.16 " A solution SHOULD avoid whatever single points of failures or propose some technical solutions for a failover mechanism." remove 'whatever' as it's superfluous? Section 6.1, Paragrpah 3 "Particularly it is RECOMMENDED that the size of a MP2MP state on a LSR" remove the superfluous 'a' before MP2MP Ben --=20 Ben Niven-Jenkins Network Architect, BT Exact =20 E-mail: benjamin.niven-jenkins@bt.com=20 Office: +44 (0)1473 648225 Mobile: +44 (0)7918 077205 Fax: +44 (0)1332 578827 _______________________________________________ mpls mailing list mpls@lists.ietf.org https://www1.ietf.org/mailman/listinfo/mpls From mpls-bounces@lists.ietf.org Thu Feb 23 14:46:35 2006 Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com) by megatron.ietf.org with esmtp (Exim 4.43) id 1FCMO2-0001D7-Dk; Thu, 23 Feb 2006 14:44:26 -0500 Received: from [10.91.34.44] (helo=ietf-mx.ietf.org) by megatron.ietf.org with esmtp (Exim 4.43) id 1FCMO1-0001Cy-8g for mpls@ietf.org; Thu, 23 Feb 2006 14:44:25 -0500 Received: from p-mail1.rd.francetelecom.com ([195.101.245.15]) by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1FCMNz-0001Ze-MS for mpls@ietf.org; Thu, 23 Feb 2006 14:44:25 -0500 Received: from ftrdmel3.rd.francetelecom.fr ([10.193.117.155]) by ftrdsmtp2.rd.francetelecom.fr with Microsoft SMTPSVC(6.0.3790.1830); Thu, 23 Feb 2006 20:33:50 +0100 X-MimeOLE: Produced By Microsoft Exchange V6.5.7226.0 Content-class: urn:content-classes:message MIME-Version: 1.0 Content-Type: text/plain; charset="US-ASCII" Content-Transfer-Encoding: quoted-printable Subject: RE: [mpls] draft-raggarwa-mpls-rsvp-upstream-00 for wg doc? Date: Thu, 23 Feb 2006 20:33:42 +0100 Message-ID: <5A0FF108221C7C4E85738678804B567C02F9784B@ftrdmel3.rd.francetelecom.fr> X-MS-Has-Attach: X-MS-TNEF-Correlator: Thread-Topic: [mpls] draft-raggarwa-mpls-rsvp-upstream-00 for wg doc? Thread-Index: AcYo32usv9MAu5aHRpKWAyuqaxKeRQPz2jbA From: "DECRAENE Bruno RD-CORE-ISS" To: "Loa Andersson" , X-OriginalArrivalTime: 23 Feb 2006 19:33:50.0814 (UTC) FILETIME=[12D757E0:01C638B0] X-Spam-Score: 0.0 (/) X-Scan-Signature: 7aafa0432175920a4b3e118e16c5cb64 Cc: X-BeenThere: mpls@lists.ietf.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Multi-Protocol Label Switching WG List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Errors-To: mpls-bounces@lists.ietf.org Hi, > draft-raggarwa-mpls-ldp-upstream-00 I support. > draft-raggarwa-mpls-rsvp-upstream-00 I support. Regards, Bruno > -----Original Message----- > From: mpls-bounces@lists.ietf.org [mailto:mpls-bounces@lists.ietf.org] On Behalf Of Loa Andersson > Sent: Friday, February 03, 2006 5:16 PM > To: mpls@ietf.org > Subject: [mpls] draft-raggarwa-mpls-rsvp-upstream-00 for wg doc? >=20 > All, >=20 > the authors of draft-raggarwa-mpls-rsvp-upstream-00 > has requested that it is made a working group document. >=20 > Please review, comment and respond to the working group mailing > list if you support it becoming a wg or not. >=20 > /Loa and George >=20 > PS >=20 > yes - there are two separate polls one for >=20 > draft-raggarwa-mpls-ldp-upstream-00 > and one for > draft-raggarwa-mpls-rsvp-upstream-00 >=20 > :) >=20 >=20 > -- > Loa Andersson >=20 > Principal Networking Architect > Acreo AB phone: +46 8 632 77 14 > Isafjordsgatan 22 mobile: +46 739 81 21 64 > Kista, Sweden email: loa.andersson@acreo.se > loa@pi.se >=20 > _______________________________________________ > mpls mailing list > mpls@lists.ietf.org > https://www1.ietf.org/mailman/listinfo/mpls _______________________________________________ mpls mailing list mpls@lists.ietf.org https://www1.ietf.org/mailman/listinfo/mpls From mpls-bounces@lists.ietf.org Fri Feb 24 03:30:25 2006 Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com) by megatron.ietf.org with esmtp (Exim 4.43) id 1FCYH2-0001JJ-VF; Fri, 24 Feb 2006 03:26:00 -0500 Received: from [10.91.34.44] (helo=ietf-mx.ietf.org) by megatron.ietf.org with esmtp (Exim 4.43) id 1FCYH1-0001JE-IX for mpls@ietf.org; Fri, 24 Feb 2006 03:25:59 -0500 Received: from p-mail2.rd.francetelecom.com ([195.101.245.16]) by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1FCYH1-0001tN-4N for mpls@ietf.org; Fri, 24 Feb 2006 03:25:59 -0500 Received: from ftrdmel1.rd.francetelecom.fr ([10.193.117.152]) by ftrdsmtp1.rd.francetelecom.fr with Microsoft SMTPSVC(6.0.3790.1830); Fri, 24 Feb 2006 09:25:57 +0100 X-MimeOLE: Produced By Microsoft Exchange V6.5.7226.0 Content-class: urn:content-classes:message MIME-Version: 1.0 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: quoted-printable Subject: RE: [mpls] TR: I-D ACTION:draft-leroux-mpls-mp-ldp-reqs-03.txt Date: Fri, 24 Feb 2006 09:26:31 +0100 Message-ID: X-MS-Has-Attach: X-MS-TNEF-Correlator: Thread-Topic: [mpls] TR: I-D ACTION:draft-leroux-mpls-mp-ldp-reqs-03.txt thread-index: AcY3hes8fx0Mw9e1Tt21ZbXB98MijgBA5BJAACSJ3PA= From: "LE ROUX Jean-Louis RD-CORE-LAN" To: , X-OriginalArrivalTime: 24 Feb 2006 08:25:57.0160 (UTC) FILETIME=[EF7EC280:01C6391B] X-Spam-Score: 0.0 (/) X-Scan-Signature: 8de5f93cb2b4e3bee75302e9eacc33db Cc: X-BeenThere: mpls@lists.ietf.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Multi-Protocol Label Switching WG List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Errors-To: mpls-bounces@lists.ietf.org Hi Ben Thanks a lot for these suggestions. They will be incorporated in the next revision. Best Regards, JL > -----Message d'origine----- > De : benjamin.niven-jenkins@bt.com=20 > [mailto:benjamin.niven-jenkins@bt.com]=20 > Envoy=E9 : jeudi 23 f=E9vrier 2006 16:29 > =C0 : mpls@ietf.org > Objet : RE: [mpls] TR: I-D=20 > ACTION:draft-leroux-mpls-mp-ldp-reqs-03.txt=20 >=20 > Colleagues, >=20 > After reading draft-leroux-mpls-mp-ldp-reqs-03 I have the=20 > following editorial comments/suggestions: >=20 > Section 3.1, Paragraphs 1,2,3,4,5,7 - put a blank line after=20 > each paragraph. >=20 > Section 3.1, Paragraph 6 - "A P2MP LSPs is an LSP" =3D> "A P2MP=20 > LSP is an LSP" >=20 > Section 3.1, Paragraph 8 - "without the need of traffic=20 > engineering" =3D> "without the need for traffic engineering" >=20 > Section 3.2, Paragraph 1 - you use egress LSR but everywhere=20 > else in the document you use Egress LSR. >=20 > Section 3.2, Paragraph 5 - "This may allow reducing the=20 > amount of LDP state to be maintained by a LSR" suggest=20 > changing this to "This may allow a reduction in the amount of=20 > LDP state that must be maintained by a LSR" >=20 > Section 5.2, Paragraph 2 - "Such P2MP FEC MUST be=20 > distinguished clearly from the exiting P2P FEC." I think you=20 > mean 'existing' not 'exiting'. >=20 > Section 5.8, Paragraph 2 - "Given that P2MP LDP routing must=20 > rely on the RIB, the achievement of the following=20 > requirements also implies the underlying routing protocols=20 > (IGP, etc.)." I think what you're trying to say is something=20 > like "Given that P2MP LDP routing must rely on the RIB, the=20 > achievement of the following requirements also implies the=20 > underlying routing protocols (IGP, etc.) must meet these=20 > requirements." >=20 > Section 5.8.1, Paragraph 2 - "The rerouting time SHOULD be as=20 > much as possible minimized so as to reduce traffic=20 > disruption." =3D> "The rerouting time SHOULD be minimized as=20 > much as possible so as to reduce traffic disruption."=20 >=20 > Section 5.8.2 - "Traffic disruption SHOULD be as much as=20 > possible minimized during such rerouting." =3D> "Traffic=20 > disruption SHOULD be minimized as much as possible during=20 > such rerouting." and "Unnecessary data duplication during=20 > such rerouting SHOULD also be as much as possible minimized."=20 > =3D> "Unnecessary data duplication during such rerouting SHOULD=20 > also be minimized as much as possible." >=20 > Section 5.8.3 - Same comments as for Section 5.8.2 >=20 > Section 5.9, Paragraph 1 - "This requires that the same label=20 > be negotiated will all downstream LSRs for the LSP." 'will' =3D> = 'with' >=20 > Section 5.16 " A solution SHOULD avoid whatever single points of > failures or propose some technical solutions for a failover=20 > mechanism." > remove 'whatever' as it's superfluous? >=20 > Section 6.1, Paragrpah 3 "Particularly it is RECOMMENDED that=20 > the size of a MP2MP state on a LSR" remove the superfluous=20 > 'a' before MP2MP >=20 > Ben >=20 >=20 > -- > Ben Niven-Jenkins > Network Architect, BT Exact > =20 > E-mail: benjamin.niven-jenkins@bt.com > Office: +44 (0)1473 648225 > Mobile: +44 (0)7918 077205 > Fax: +44 (0)1332 578827 >=20 > _______________________________________________ > mpls mailing list > mpls@lists.ietf.org > https://www1.ietf.org/mailman/listinfo/mpls >=20 _______________________________________________ mpls mailing list mpls@lists.ietf.org https://www1.ietf.org/mailman/listinfo/mpls From mpls-bounces@lists.ietf.org Fri Feb 24 11:41:17 2006 Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com) by megatron.ietf.org with esmtp (Exim 4.43) id 1FCfyF-0001so-DP; Fri, 24 Feb 2006 11:39:07 -0500 Received: from [10.91.34.44] (helo=ietf-mx.ietf.org) by megatron.ietf.org with esmtp (Exim 4.43) id 1FCfyD-0001sb-LU for mpls@ietf.org; Fri, 24 Feb 2006 11:39:05 -0500 Received: from sa.infonet.com ([192.157.130.21]) by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1FCfyD-0000hp-AI for mpls@ietf.org; Fri, 24 Feb 2006 11:39:05 -0500 Received: from zhang-D600.sa.infonet.com ([204.231.159.43]) by sa.infonet.com with ESMTP id k0OEd1Lc015488; Tue, 24 Jan 2006 14:39:03 GMT Message-Id: <6.2.1.2.2.20060224083818.03af34e0@sa.infonet.com> X-Mailer: QUALCOMM Windows Eudora Version 6.2.1.2 Date: Fri, 24 Feb 2006 08:38:30 -0800 To: Loa Andersson , mpls@ietf.org From: raymond zhang Subject: Re: [mpls] draft-raggarwa-mpls-rsvp-upstream-00 for wg doc? In-Reply-To: <43E381D5.8020008@pi.se> References: <43E381D5.8020008@pi.se> Mime-Version: 1.0 Content-Type: text/plain; charset="us-ascii"; format=flowed X-Spam-Score: 0.0 (/) X-Scan-Signature: a7d6aff76b15f3f56fcb94490e1052e4 Cc: X-BeenThere: mpls@lists.ietf.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Multi-Protocol Label Switching WG List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Errors-To: mpls-bounces@lists.ietf.org At 08:16 AM 2/3/2006, Loa Andersson wrote: >All, > >the authors of draft-raggarwa-mpls-rsvp-upstream-00 >has requested that it is made a working group document. > >Please review, comment and respond to the working group mailing >list if you support it becoming a wg or not. Support.. Regards, Raymond >/Loa and George > >PS > >yes - there are two separate polls one for > >draft-raggarwa-mpls-ldp-upstream-00 >and one for >draft-raggarwa-mpls-rsvp-upstream-00 > >:) > > >-- >Loa Andersson > >Principal Networking Architect >Acreo AB phone: +46 8 632 77 14 >Isafjordsgatan 22 mobile: +46 739 81 21 64 >Kista, Sweden email: loa.andersson@acreo.se > loa@pi.se > >_______________________________________________ >mpls mailing list >mpls@lists.ietf.org >https://www1.ietf.org/mailman/listinfo/mpls _______________________________________________ mpls mailing list mpls@lists.ietf.org https://www1.ietf.org/mailman/listinfo/mpls From mpls-bounces@lists.ietf.org Fri Feb 24 11:41:17 2006 Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com) by megatron.ietf.org with esmtp (Exim 4.43) id 1FCfyG-0001sx-8K; Fri, 24 Feb 2006 11:39:08 -0500 Received: from [10.91.34.44] (helo=ietf-mx.ietf.org) by megatron.ietf.org with esmtp (Exim 4.43) id 1FCfyE-0001sj-F7 for mpls@ietf.org; Fri, 24 Feb 2006 11:39:06 -0500 Received: from sa.infonet.com ([192.157.130.21]) by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1FCfyC-0000ho-Ot for mpls@ietf.org; Fri, 24 Feb 2006 11:39:06 -0500 Received: from zhang-D600.sa.infonet.com ([204.231.159.43]) by sa.infonet.com with ESMTP id k0OEd1La015488; Tue, 24 Jan 2006 14:39:02 GMT Message-Id: <6.2.1.2.2.20060224083754.03af30e0@sa.infonet.com> X-Mailer: QUALCOMM Windows Eudora Version 6.2.1.2 Date: Fri, 24 Feb 2006 08:38:10 -0800 To: Loa Andersson , mpls@ietf.org From: raymond zhang Subject: Re: [mpls] draft-raggarwa-mpls-ldp-upstream-00 for wg doc? In-Reply-To: <43E3814B.80503@pi.se> References: <43E3814B.80503@pi.se> Mime-Version: 1.0 Content-Type: text/plain; charset="us-ascii"; format=flowed X-Spam-Score: 0.0 (/) X-Scan-Signature: 8abaac9e10c826e8252866cbe6766464 Cc: X-BeenThere: mpls@lists.ietf.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Multi-Protocol Label Switching WG List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Errors-To: mpls-bounces@lists.ietf.org At 08:14 AM 2/3/2006, Loa Andersson wrote: >All, > >the authors of draft-raggarwa-mpls-ldp-upstream-00 >has requested that it is made a working group document. > >Please review, comment and respond to the working group mailing >list if you support it becoming a wg or not. Support... Regards, Raymond >/Loa and George > >-- >Loa Andersson > >Principal Networking Architect >Acreo AB phone: +46 8 632 77 14 >Isafjordsgatan 22 mobile: +46 739 81 21 64 >Kista, Sweden email: loa.andersson@acreo.se > loa@pi.se > >_______________________________________________ >mpls mailing list >mpls@lists.ietf.org >https://www1.ietf.org/mailman/listinfo/mpls _______________________________________________ mpls mailing list mpls@lists.ietf.org https://www1.ietf.org/mailman/listinfo/mpls From mpls-bounces@lists.ietf.org Fri Feb 24 11:41:17 2006 Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com) by megatron.ietf.org with esmtp (Exim 4.43) id 1FCfyF-0001so-DP; Fri, 24 Feb 2006 11:39:07 -0500 Received: from [10.91.34.44] (helo=ietf-mx.ietf.org) by megatron.ietf.org with esmtp (Exim 4.43) id 1FCfyD-0001sb-LU for mpls@ietf.org; Fri, 24 Feb 2006 11:39:05 -0500 Received: from sa.infonet.com ([192.157.130.21]) by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1FCfyD-0000hp-AI for mpls@ietf.org; Fri, 24 Feb 2006 11:39:05 -0500 Received: from zhang-D600.sa.infonet.com ([204.231.159.43]) by sa.infonet.com with ESMTP id k0OEd1Lc015488; Tue, 24 Jan 2006 14:39:03 GMT Message-Id: <6.2.1.2.2.20060224083818.03af34e0@sa.infonet.com> X-Mailer: QUALCOMM Windows Eudora Version 6.2.1.2 Date: Fri, 24 Feb 2006 08:38:30 -0800 To: Loa Andersson , mpls@ietf.org From: raymond zhang Subject: Re: [mpls] draft-raggarwa-mpls-rsvp-upstream-00 for wg doc? In-Reply-To: <43E381D5.8020008@pi.se> References: <43E381D5.8020008@pi.se> Mime-Version: 1.0 Content-Type: text/plain; charset="us-ascii"; format=flowed X-Spam-Score: 0.0 (/) X-Scan-Signature: a7d6aff76b15f3f56fcb94490e1052e4 Cc: X-BeenThere: mpls@lists.ietf.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Multi-Protocol Label Switching WG List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Errors-To: mpls-bounces@lists.ietf.org At 08:16 AM 2/3/2006, Loa Andersson wrote: >All, > >the authors of draft-raggarwa-mpls-rsvp-upstream-00 >has requested that it is made a working group document. > >Please review, comment and respond to the working group mailing >list if you support it becoming a wg or not. Support.. Regards, Raymond >/Loa and George > >PS > >yes - there are two separate polls one for > >draft-raggarwa-mpls-ldp-upstream-00 >and one for >draft-raggarwa-mpls-rsvp-upstream-00 > >:) > > >-- >Loa Andersson > >Principal Networking Architect >Acreo AB phone: +46 8 632 77 14 >Isafjordsgatan 22 mobile: +46 739 81 21 64 >Kista, Sweden email: loa.andersson@acreo.se > loa@pi.se > >_______________________________________________ >mpls mailing list >mpls@lists.ietf.org >https://www1.ietf.org/mailman/listinfo/mpls _______________________________________________ mpls mailing list mpls@lists.ietf.org https://www1.ietf.org/mailman/listinfo/mpls From mpls-bounces@lists.ietf.org Fri Feb 24 11:41:17 2006 Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com) by megatron.ietf.org with esmtp (Exim 4.43) id 1FCfyG-0001sx-8K; Fri, 24 Feb 2006 11:39:08 -0500 Received: from [10.91.34.44] (helo=ietf-mx.ietf.org) by megatron.ietf.org with esmtp (Exim 4.43) id 1FCfyE-0001sj-F7 for mpls@ietf.org; Fri, 24 Feb 2006 11:39:06 -0500 Received: from sa.infonet.com ([192.157.130.21]) by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1FCfyC-0000ho-Ot for mpls@ietf.org; Fri, 24 Feb 2006 11:39:06 -0500 Received: from zhang-D600.sa.infonet.com ([204.231.159.43]) by sa.infonet.com with ESMTP id k0OEd1La015488; Tue, 24 Jan 2006 14:39:02 GMT Message-Id: <6.2.1.2.2.20060224083754.03af30e0@sa.infonet.com> X-Mailer: QUALCOMM Windows Eudora Version 6.2.1.2 Date: Fri, 24 Feb 2006 08:38:10 -0800 To: Loa Andersson , mpls@ietf.org From: raymond zhang Subject: Re: [mpls] draft-raggarwa-mpls-ldp-upstream-00 for wg doc? In-Reply-To: <43E3814B.80503@pi.se> References: <43E3814B.80503@pi.se> Mime-Version: 1.0 Content-Type: text/plain; charset="us-ascii"; format=flowed X-Spam-Score: 0.0 (/) X-Scan-Signature: 8abaac9e10c826e8252866cbe6766464 Cc: X-BeenThere: mpls@lists.ietf.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Multi-Protocol Label Switching WG List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Errors-To: mpls-bounces@lists.ietf.org At 08:14 AM 2/3/2006, Loa Andersson wrote: >All, > >the authors of draft-raggarwa-mpls-ldp-upstream-00 >has requested that it is made a working group document. > >Please review, comment and respond to the working group mailing >list if you support it becoming a wg or not. Support... Regards, Raymond >/Loa and George > >-- >Loa Andersson > >Principal Networking Architect >Acreo AB phone: +46 8 632 77 14 >Isafjordsgatan 22 mobile: +46 739 81 21 64 >Kista, Sweden email: loa.andersson@acreo.se > loa@pi.se > >_______________________________________________ >mpls mailing list >mpls@lists.ietf.org >https://www1.ietf.org/mailman/listinfo/mpls _______________________________________________ mpls mailing list mpls@lists.ietf.org https://www1.ietf.org/mailman/listinfo/mpls From mpls-bounces@lists.ietf.org Fri Feb 24 11:51:35 2006 Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com) by megatron.ietf.org with esmtp (Exim 4.43) id 1FCg8P-0000ke-NK; Fri, 24 Feb 2006 11:49:37 -0500 Received: from [10.91.34.44] (helo=ietf-mx.ietf.org) by megatron.ietf.org with esmtp (Exim 4.43) id 1FCg8O-0000kM-60 for mpls@ietf.org; Fri, 24 Feb 2006 11:49:36 -0500 Received: from usjk1002.kddi.com ([211.4.169.18]) by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1FCg8M-0000xs-Hy for mpls@ietf.org; Fri, 24 Feb 2006 11:49:36 -0500 Received: from usjk1006.kddi.com (usjk1006 [10.96.2.3]) by usjk1002.kddi.com with ESMTP id k1OGnXv25310 for ; Sat, 25 Feb 2006 01:49:33 +0900 (JST) Received: from usjk1037 (localhost [127.0.0.1]) by usjk1006.kddi.com with SMTP id k1OGnXP20572 for ; Sat, 25 Feb 2006 01:49:33 +0900 (JST) Received: from [127.0.0.1] ([133.128.75.150]) by usjk1010.kddi.com (InterMail vM.5.01.02.00 201-253-116-121-20001201) with ESMTP id <20060224164926.PTRZ13468.usjk1010.kddi.com@[127.0.0.1]> for ; Sat, 25 Feb 2006 01:49:26 +0900 Date: Sat, 25 Feb 2006 01:49:24 +0900 From: Kenji Kumaki To: mpls@ietf.org Subject: Re: [mpls] draft-raggarwa-mpls-ldp-upstream-00 for wg doc? In-Reply-To: <43E3814B.80503@pi.se> References: <43E3814B.80503@pi.se> Message-Id: <20060225014327.C42C.KE-KUMAKI@kddi.com> MIME-Version: 1.0 Content-Type: text/plain; charset="US-ASCII" Content-Transfer-Encoding: 7bit X-Mailer: Becky! ver. 2.21.03 [ja] X-WAuditID: 0602250149260000028702 X-Spam-Score: 0.0 (/) X-Scan-Signature: 97adf591118a232206bdb5a27b217034 Cc: X-BeenThere: mpls@lists.ietf.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Multi-Protocol Label Switching WG List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Errors-To: mpls-bounces@lists.ietf.org > All, > > the authors of draft-raggarwa-mpls-ldp-upstream-00 > has requested that it is made a working group document. > > Please review, comment and respond to the working group mailing > list if you support it becoming a wg or not. > Yes. Thanks, Kenji > /Loa and George > > -- > Loa Andersson > > Principal Networking Architect > Acreo AB phone: +46 8 632 77 14 > Isafjordsgatan 22 mobile: +46 739 81 21 64 > Kista, Sweden email: loa.andersson@acreo.se > loa@pi.se > > _______________________________________________ > mpls mailing list > mpls@lists.ietf.org > https://www1.ietf.org/mailman/listinfo/mpls -- Kenji Kumaki _______________________________________________ mpls mailing list mpls@lists.ietf.org https://www1.ietf.org/mailman/listinfo/mpls From mpls-bounces@lists.ietf.org Fri Feb 24 11:51:35 2006 Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com) by megatron.ietf.org with esmtp (Exim 4.43) id 1FCg8Q-0000lB-CX; Fri, 24 Feb 2006 11:49:38 -0500 Received: from [10.91.34.44] (helo=ietf-mx.ietf.org) by megatron.ietf.org with esmtp (Exim 4.43) id 1FCg8P-0000kZ-9o for mpls@ietf.org; Fri, 24 Feb 2006 11:49:37 -0500 Received: from usjk1002.kddi.com ([211.4.169.18]) by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1FCg8N-0000xu-LJ for mpls@ietf.org; Fri, 24 Feb 2006 11:49:37 -0500 Received: from usjk1006.kddi.com (usjk1006 [10.96.2.3]) by usjk1002.kddi.com with ESMTP id k1OGnYv25322 for ; Sat, 25 Feb 2006 01:49:34 +0900 (JST) Received: from usjk1037 (localhost [127.0.0.1]) by usjk1006.kddi.com with SMTP id k1OGnYP20578 for ; Sat, 25 Feb 2006 01:49:34 +0900 (JST) Received: from [127.0.0.1] ([133.128.75.150]) by usjk1010.kddi.com (InterMail vM.5.01.02.00 201-253-116-121-20001201) with ESMTP id <20060224164930.PTSA13468.usjk1010.kddi.com@[127.0.0.1]> for ; Sat, 25 Feb 2006 01:49:30 +0900 Date: Sat, 25 Feb 2006 01:49:28 +0900 From: Kenji Kumaki To: mpls@ietf.org Subject: Re: [mpls] draft-raggarwa-mpls-rsvp-upstream-00 for wg doc? In-Reply-To: <43E381D5.8020008@pi.se> References: <43E381D5.8020008@pi.se> Message-Id: <20060225014354.C432.KE-KUMAKI@kddi.com> MIME-Version: 1.0 Content-Type: text/plain; charset="US-ASCII" Content-Transfer-Encoding: 7bit X-Mailer: Becky! ver. 2.21.03 [ja] X-WAuditID: 0602250149300000028716 X-Spam-Score: 0.0 (/) X-Scan-Signature: cab78e1e39c4b328567edb48482b6a69 Cc: X-BeenThere: mpls@lists.ietf.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Multi-Protocol Label Switching WG List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Errors-To: mpls-bounces@lists.ietf.org > All, > > the authors of draft-raggarwa-mpls-rsvp-upstream-00 > has requested that it is made a working group document. > > Please review, comment and respond to the working group mailing > list if you support it becoming a wg or not. > Yes. Thanks, Kenji > /Loa and George > > PS > > yes - there are two separate polls one for > > draft-raggarwa-mpls-ldp-upstream-00 > and one for > draft-raggarwa-mpls-rsvp-upstream-00 > > :) > > > -- > Loa Andersson > > Principal Networking Architect > Acreo AB phone: +46 8 632 77 14 > Isafjordsgatan 22 mobile: +46 739 81 21 64 > Kista, Sweden email: loa.andersson@acreo.se > loa@pi.se > > _______________________________________________ > mpls mailing list > mpls@lists.ietf.org > https://www1.ietf.org/mailman/listinfo/mpls -- Kenji Kumaki _______________________________________________ mpls mailing list mpls@lists.ietf.org https://www1.ietf.org/mailman/listinfo/mpls From mpls-bounces@lists.ietf.org Sat Feb 25 03:22:48 2006 Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com) by megatron.ietf.org with esmtp (Exim 4.43) id 1FCufO-0005EJ-6f; Sat, 25 Feb 2006 03:20:38 -0500 Received: from [10.91.34.44] (helo=ietf-mx.ietf.org) by megatron.ietf.org with esmtp (Exim 4.43) id 1FCufN-0005E0-1F for mpls@ietf.org; Sat, 25 Feb 2006 03:20:37 -0500 Received: from [80.86.78.228] (helo=smtp.testbed.se) by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1FCufL-0007NE-NE for mpls@ietf.org; Sat, 25 Feb 2006 03:20:37 -0500 Received: from 37.253.dhcp.conference.apricot.net ([169.223.253.37]) by fw.testbed.se with esmtpsa (TLSv1:AES256-SHA:256) (Exim 4.43) id 1FCufG-0006Q9-Eq; Sat, 25 Feb 2006 09:20:33 +0100 Message-ID: <44001344.30600@pi.se> Date: Sat, 25 Feb 2006 09:20:20 +0100 From: Loa Andersson Organization: Acreo AB User-Agent: Mozilla Thunderbird 1.0.5 (Windows/20050711) X-Accept-Language: en-us, en MIME-Version: 1.0 To: mpls@ietf.org, Internet-Drafts@ietf.org, Rahul Aggarwal , Ina Minei , IJsbrand Wijnands Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit X-Spam-Score: -1.4 (-) X-Spam-Report: -1.4 ALL_TRUSTED Passed through trusted hosts only via SMTP X-Spam-Score: 0.0 (/) X-Scan-Signature: 7baded97d9887f7a0c7e8a33c2e3ea1b Cc: Subject: [mpls] Three new wg documents X-BeenThere: mpls@lists.ietf.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Multi-Protocol Label Switching WG List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Errors-To: mpls-bounces@lists.ietf.org All, we have three outstanding requests for documents to be accepted as working group docuements. We have enough a rough consensus for all of them. They are: draft-raggarwa-mpls-ldp-upstream-00 draft-raggarwa-mpls-rsvp-upstream-00 draft-minei-wijnands-mpls-ldp-p2mp-00 Could the authors please publish (if at all possible) them as follows draft-ietf-mpls-ldp-upstream-00.txt - (Rahul) draft-ietf-mpls-rsvp-upstream-00.txt - (Rahul) draft-ietf-mpls-ldp-p2mp-00.txt - (Ina/Ice) As you can see from the following excerpt below this is quite close to the cut off date: "All initial Internet-Drafts (version -00) must be submitted by Monday, February 27th at 9:00 AM ET. As always, all initial submissions with a filename beginning with "draft-ietf" must be approved by the appropriate WG Chair before they can be processed or announced. The Secretariat would appreciate receiving WG Chair approval by Monday, February 20th at 9:00 AM ET." /Loa and George -- Loa Andersson Principal Networking Architect Acreo AB phone: +46 8 632 77 14 Isafjordsgatan 22 mobile: +46 739 81 21 64 Kista, Sweden email: loa.andersson@acreo.se loa@pi.se _______________________________________________ mpls mailing list mpls@lists.ietf.org https://www1.ietf.org/mailman/listinfo/mpls From mpls-bounces@lists.ietf.org Sat Feb 25 07:39:51 2006 Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com) by megatron.ietf.org with esmtp (Exim 4.43) id 1FCygD-0000qe-S1; Sat, 25 Feb 2006 07:37:45 -0500 Received: from [10.91.34.44] (helo=ietf-mx.ietf.org) by megatron.ietf.org with esmtp (Exim 4.43) id 1FCh8b-0001Sl-Oe for mpls@ietf.org; Fri, 24 Feb 2006 12:53:53 -0500 Received: from msgbas1x.cos.agilent.com ([192.25.240.36]) by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1FCh8Z-0003Zm-Bv for mpls@ietf.org; Fri, 24 Feb 2006 12:53:53 -0500 Received: from relcos2.cos.agilent.com (relcos2.cos.agilent.com [130.29.152.237]) by msgbas1x.cos.agilent.com (Postfix) with ESMTP id ED3FC269FC for ; Fri, 24 Feb 2006 10:53:50 -0700 (MST) Received: from wcosvs03.cos.agilent.com (wcosvs03.cos.agilent.com [130.29.152.233]) by relcos2.cos.agilent.com (Postfix) with ESMTP id A046253A for ; Fri, 24 Feb 2006 10:53:50 -0700 (MST) Received: from wcosbh02.cos.agilent.com ([130.29.152.126]) by wcosvs03.cos.agilent.com with InterScan Messaging Security Suite; Fri, 24 Feb 2006 10:53:50 -0700 Received: from wcosmb09.cos.agilent.com ([130.29.152.137]) by wcosbh02.cos.agilent.com with Microsoft SMTPSVC(6.0.3790.1830); Fri, 24 Feb 2006 10:53:50 -0700 X-MimeOLE: Produced By Microsoft Exchange V6.5.7226.0 Content-class: urn:content-classes:message MIME-Version: 1.0 Content-Type: text/plain; charset="US-ASCII" Content-Transfer-Encoding: quoted-printable Subject: RE: [mpls] draft-raggarwa-mpls-rsvp-upstream-00 for wg doc? Date: Fri, 24 Feb 2006 10:53:49 -0700 Message-ID: X-MS-Has-Attach: X-MS-TNEF-Correlator: Thread-Topic: [mpls] draft-raggarwa-mpls-rsvp-upstream-00 for wg doc? Thread-Index: AcYo3iddwK8pmqYQTUaiRN5c74vr4wQiRzqQ From: To: X-OriginalArrivalTime: 24 Feb 2006 17:53:50.0109 (UTC) FILETIME=[448E2CD0:01C6396B] X-Spam-Score: 0.2 (/) X-Scan-Signature: c1c65599517f9ac32519d043c37c5336 X-Mailman-Approved-At: Sat, 25 Feb 2006 07:37:45 -0500 Cc: X-BeenThere: mpls@lists.ietf.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Multi-Protocol Label Switching WG List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Errors-To: mpls-bounces@lists.ietf.org Support -Thomson =20 -----Original Message----- From: mpls-bounces@lists.ietf.org [mailto:mpls-bounces@lists.ietf.org] = On Behalf Of Loa Andersson Sent: Friday, February 03, 2006 11:16 AM To: mpls@ietf.org Subject: [mpls] draft-raggarwa-mpls-rsvp-upstream-00 for wg doc? All, the authors of draft-raggarwa-mpls-rsvp-upstream-00 has requested that it is made a working group document. Please review, comment and respond to the working group mailing list if you support it becoming a wg or not. /Loa and George PS yes - there are two separate polls one for draft-raggarwa-mpls-ldp-upstream-00 and one for draft-raggarwa-mpls-rsvp-upstream-00 :) --=20 Loa Andersson Principal Networking Architect Acreo AB phone: +46 8 632 77 14 Isafjordsgatan 22 mobile: +46 739 81 21 64 Kista, Sweden email: loa.andersson@acreo.se loa@pi.se _______________________________________________ mpls mailing list mpls@lists.ietf.org https://www1.ietf.org/mailman/listinfo/mpls _______________________________________________ mpls mailing list mpls@lists.ietf.org https://www1.ietf.org/mailman/listinfo/mpls From mpls-bounces@lists.ietf.org Sat Feb 25 07:39:51 2006 Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com) by megatron.ietf.org with esmtp (Exim 4.43) id 1FCygE-0000qk-Ed; Sat, 25 Feb 2006 07:37:46 -0500 Received: from [10.91.34.44] (helo=ietf-mx.ietf.org) by megatron.ietf.org with esmtp (Exim 4.43) id 1FCh8i-0001k0-Iv for mpls@ietf.org; Fri, 24 Feb 2006 12:54:00 -0500 Received: from msgbas9x.lvld.agilent.com ([192.25.144.41]) by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1FCh8h-0003Zt-8Y for mpls@ietf.org; Fri, 24 Feb 2006 12:54:00 -0500 Received: from relcos1.cos.agilent.com (relcos1.cos.agilent.com [130.29.152.239]) by msgbas9x.lvld.agilent.com (Postfix) with ESMTP id B63166F for ; Fri, 24 Feb 2006 10:53:58 -0700 (MST) Received: from wlvdvs01.lvld.agilent.com (wlvdvs01.lvld.agilent.com [148.5.6.4]) by relcos1.cos.agilent.com (Postfix) with ESMTP id 1A8295EC for ; Fri, 24 Feb 2006 10:53:54 -0700 (MST) Received: from wcosbh01.cos.agilent.com ([130.29.152.125]) by wlvdvs01.lvld.agilent.com with InterScan Messaging Security Suite; Fri, 24 Feb 2006 10:53:53 -0700 Received: from wcosmb09.cos.agilent.com ([130.29.152.137]) by wcosbh01.cos.agilent.com with Microsoft SMTPSVC(6.0.3790.1830); Fri, 24 Feb 2006 10:53:53 -0700 X-MimeOLE: Produced By Microsoft Exchange V6.5.7226.0 Content-class: urn:content-classes:message MIME-Version: 1.0 Content-Type: text/plain; charset="US-ASCII" Content-Transfer-Encoding: quoted-printable Subject: RE: [mpls] draft-raggarwa-mpls-ldp-upstream-00 for wg doc? Date: Fri, 24 Feb 2006 10:53:52 -0700 Message-ID: X-MS-Has-Attach: X-MS-TNEF-Correlator: Thread-Topic: [mpls] draft-raggarwa-mpls-ldp-upstream-00 for wg doc? Thread-Index: AcYo3b7jxXtSmXAUSp+G1LXHOEVbLgQiP01Q From: To: X-OriginalArrivalTime: 24 Feb 2006 17:53:53.0592 (UTC) FILETIME=[46A1A380:01C6396B] X-Spam-Score: 0.2 (/) X-Scan-Signature: bb8f917bb6b8da28fc948aeffb74aa17 X-Mailman-Approved-At: Sat, 25 Feb 2006 07:37:45 -0500 Cc: X-BeenThere: mpls@lists.ietf.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Multi-Protocol Label Switching WG List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Errors-To: mpls-bounces@lists.ietf.org Support -Thomson =20 -----Original Message----- From: mpls-bounces@lists.ietf.org [mailto:mpls-bounces@lists.ietf.org] = On Behalf Of Loa Andersson Sent: Friday, February 03, 2006 11:14 AM To: mpls@ietf.org Subject: [mpls] draft-raggarwa-mpls-ldp-upstream-00 for wg doc? All, the authors of draft-raggarwa-mpls-ldp-upstream-00 has requested that it is made a working group document. Please review, comment and respond to the working group mailing list if you support it becoming a wg or not. /Loa and George --=20 Loa Andersson Principal Networking Architect Acreo AB phone: +46 8 632 77 14 Isafjordsgatan 22 mobile: +46 739 81 21 64 Kista, Sweden email: loa.andersson@acreo.se loa@pi.se _______________________________________________ mpls mailing list mpls@lists.ietf.org https://www1.ietf.org/mailman/listinfo/mpls _______________________________________________ mpls mailing list mpls@lists.ietf.org https://www1.ietf.org/mailman/listinfo/mpls From mpls-bounces@lists.ietf.org Sat Feb 25 07:40:35 2006 Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com) by megatron.ietf.org with esmtp (Exim 4.43) id 1FCyh8-0001Ym-AV; Sat, 25 Feb 2006 07:38:42 -0500 Received: from [10.91.34.44] (helo=ietf-mx.ietf.org) by megatron.ietf.org with esmtp (Exim 4.43) id 1FCgN9-0003sI-R8 for mpls@ietf.org; Fri, 24 Feb 2006 12:04:51 -0500 Received: from pmesmtp04.mci.com ([199.249.20.36]) by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1FCgN8-0001XN-G3 for mpls@ietf.org; Fri, 24 Feb 2006 12:04:51 -0500 Received: from dgismtp02.mcilink.com ([166.38.58.142]) by firewall.mci.com (Iplanet MTA 5.2) with ESMTP id <0IV7001M6B551K@firewall.mci.com> for mpls@ietf.org; Fri, 24 Feb 2006 16:58:17 +0000 (GMT) Received: from dgismtp02.mcilink.com ([127.0.0.1]) by dgismtp02.mcilink.com (iPlanet Messaging Server 5.2 HotFix 2.08 (built Sep 22 2005)) with SMTP id <0IV7005B9B55SS@dgismtp02.mcilink.com> for mpls@ietf.org; Fri, 24 Feb 2006 16:58:17 +0000 (GMT) Received: from xs344v8065929 ([153.39.146.167]) by dgismtp02.mcilink.com (iPlanet Messaging Server 5.2 HotFix 2.08 (built Sep 22 2005)) with ESMTP id <0IV70047GB55ZT@dgismtp02.mcilink.com> for mpls@ietf.org; Fri, 24 Feb 2006 16:58:17 +0000 (GMT) Date: Fri, 24 Feb 2006 11:58:16 -0500 From: "durga.gangisetti" Subject: RE: [mpls] draft-raggarwa-mpls-ldp-upstream-00 for wg doc? In-reply-to: <6.2.1.2.2.20060224083754.03af30e0@sa.infonet.com> To: 'raymond zhang' , 'Loa Andersson' , mpls@ietf.org Message-id: <000801c63963$81a29820$a7922799@mcilink.com> MIME-version: 1.0 X-MIMEOLE: Produced By Microsoft MimeOLE V6.00.2900.2180 X-Mailer: Microsoft Outlook, Build 10.0.6626 Content-type: text/plain; charset=us-ascii Content-transfer-encoding: 7bit Importance: Normal X-Priority: 3 (Normal) X-MSMail-priority: Normal X-Spam-Score: 0.0 (/) X-Scan-Signature: 68c8cc8a64a9d0402e43b8eee9fc4199 X-Mailman-Approved-At: Sat, 25 Feb 2006 07:38:41 -0500 Cc: durga.gangisetti@verizon.com X-BeenThere: mpls@lists.ietf.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Multi-Protocol Label Switching WG List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Errors-To: mpls-bounces@lists.ietf.org At 08:14 AM 2/3/2006, Loa Andersson wrote: >All, > >the authors of draft-raggarwa-mpls-ldp-upstream-00 >has requested that it is made a working group document. > >Please review, comment and respond to the working group mailing >list if you support it becoming a wg or not. Yes. Durga, MCI/Verizon. _______________________________________________ mpls mailing list mpls@lists.ietf.org https://www1.ietf.org/mailman/listinfo/mpls From mission@dotnet.com Sun Feb 26 13:11:33 2006 Received: from [10.91.34.44] (helo=ietf-mx.ietf.org) by megatron.ietf.org with esmtp (Exim 4.43) id 1FDQMn-00040L-P4 for mpls-archive@lists.ietf.org; Sun, 26 Feb 2006 13:11:33 -0500 Received: from muedsl-82-207-199-174.citykom.de ([82.207.199.174]) by ietf-mx.ietf.org with smtp (Exim 4.43) id 1FDQMm-0002TM-4j for mpls-archive@lists.ietf.org; Sun, 26 Feb 2006 13:11:33 -0500 Received: from acropolis by microsoft.com with local (Exim 4.41 (FreeBSD)) id 85-8-52 for camilla; Sun, 26 Feb 2006 13:11:10 -0500 Message-ID: <762791@veda> From: Saul Saunders To: mpls-archive@lists.ietf.org Subject: Your Order Date: Sun, 26 Feb 2006 16:03:11 -0500 MIME-Version: 1.0 X-Priority: 3 X-MSMail-Priority: Normal X-Mailer: Microsoft Outlook Express 27515.040396.14842.75531 X-MimeOLE: Produced By Microsoft MimeOLE 49654706.975164.808094.12726654 Content-Type: multipart/mixed; boundary="------=97992248092493" Content-Transfer-Encoding: 7bit X-Spam-Score: 0.1 (/) X-Scan-Signature: fb6060cb60c0cea16e3f7219e40a0a81 --------=97992248092493 Content-Type: text/html; charset="us-ascii" Content-Transfer-Encoding: 8bit

Even if you have no erection problems Cialis would help you to make better sex more often and to bring unimaginable plesure to her. Just disolve half a pill under your tongue and get ready for action in 15 minutes. The tests showed that the majority of men after taking this medication were able to have perfect erection during 36 hours!

Package Quantity Price in your local drugstore* Our price

Learn
More
Now
10 softtabs 20 doses $149.95 $119.95
20 softtabs 40 doses $299.95 $159.95
30 softtabs 60 doses $849.95 $169.95
60 softtabs 120 doses $1 999.95 $259.95
90 softtabs 180 doses $3 099.95 $299.95

When you are young and stressed up…
When you are aged and never give up…
Cialis gives you confidence in any chance, every time.


Men's fame is like their hair, which grows after they are dead, and with just as little use to them.
The tighter you squeeze, the less you have.The best audience is one that is intelligent, well-educated, and a little drunk. --------=97992248092493 Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit Good morning sir, Your Order-> http://au.geocities.com/rhonda25229gallagher26793/ --------=97992248092493-- From mpls-bounces@lists.ietf.org Mon Feb 27 15:52:20 2006 Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com) by megatron.ietf.org with esmtp (Exim 4.43) id 1FDpJl-0005nj-PI; Mon, 27 Feb 2006 15:50:05 -0500 Received: from [10.91.34.44] (helo=ietf-mx.ietf.org) by megatron.ietf.org with esmtp (Exim 4.43) id 1FDpJi-0005mw-NN; Mon, 27 Feb 2006 15:50:02 -0500 Received: from oak.neustar.com ([209.173.53.70]) by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1FDpJi-0001U6-GT; Mon, 27 Feb 2006 15:50:02 -0500 Received: from stiedprstage1.ietf.org (stiedprstage1.va.neustar.com [10.31.47.10]) by oak.neustar.com (8.12.8/8.12.8) with ESMTP id k1RKo2BX001494 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO); Mon, 27 Feb 2006 20:50:02 GMT Received: from ietf by stiedprstage1.ietf.org with local (Exim 4.43) id 1FDpJi-000723-87; Mon, 27 Feb 2006 15:50:02 -0500 Content-Type: Multipart/Mixed; Boundary="NextPart" Mime-Version: 1.0 To: i-d-announce@ietf.org From: Internet-Drafts@ietf.org Message-Id: Date: Mon, 27 Feb 2006 15:50:02 -0500 X-Spam-Score: 0.3 (/) X-Scan-Signature: c3a18ef96977fc9bcc21a621cbf1174b Cc: mpls@lists.ietf.org Subject: [mpls] I-D ACTION:draft-ietf-mpls-over-l2tpv3-01.txt X-BeenThere: mpls@lists.ietf.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Multi-Protocol Label Switching WG List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Errors-To: mpls-bounces@lists.ietf.org --NextPart A New Internet-Draft is available from the on-line Internet-Drafts directories. This draft is a work item of the Multiprotocol Label Switching Working Group of the IETF. Title : Encapsulation of MPLS over Layer 2 Tunneling Protocol Version 3 Author(s) : M. Townsley, et al. Filename : draft-ietf-mpls-over-l2tpv3-01.txt Pages : 11 Date : 2006-2-27 The Layer 2 Tunneling Protocol, Version 3, (L2TPv3) defines a protocol for tunneling a variety of payload types over IP networks. This document defines how to carry an MPLS label stack and its payload over L2TPv3. This enables an application which traditionally requires an MPLS-enabled core network to utilize an L2TPv3 encapsulation over an IP network instead. A URL for this Internet-Draft is: http://www.ietf.org/internet-drafts/draft-ietf-mpls-over-l2tpv3-01.txt To remove yourself from the I-D Announcement list, send a message to i-d-announce-request@ietf.org with the word unsubscribe in the body of the message. You can also visit https://www1.ietf.org/mailman/listinfo/I-D-announce to change your subscription settings. Internet-Drafts are also available by anonymous FTP. Login with the username "anonymous" and a password of your e-mail address. After logging in, type "cd internet-drafts" and then "get draft-ietf-mpls-over-l2tpv3-01.txt". A list of Internet-Drafts directories can be found in http://www.ietf.org/shadow.html or ftp://ftp.ietf.org/ietf/1shadow-sites.txt Internet-Drafts can also be obtained by e-mail. Send a message to: mailserv@ietf.org. In the body type: "FILE /internet-drafts/draft-ietf-mpls-over-l2tpv3-01.txt". NOTE: The mail server at ietf.org can return the document in MIME-encoded form by using the "mpack" utility. To use this feature, insert the command "ENCODING mime" before the "FILE" command. To decode the response(s), you will need "munpack" or a MIME-compliant mail reader. Different MIME-compliant mail readers exhibit different behavior, especially when dealing with "multipart" MIME messages (i.e. documents which have been split up into multiple messages), so check your local documentation on how to manipulate these messages. Below is the data which will enable a MIME compliant mail reader implementation to automatically retrieve the ASCII version of the Internet-Draft. --NextPart Content-Type: Multipart/Alternative; Boundary="OtherAccess" --OtherAccess Content-Type: Message/External-body; access-type="mail-server"; server="mailserv@ietf.org" Content-Type: text/plain Content-ID: <2006-2-27140458.I-D@ietf.org> ENCODING mime FILE /internet-drafts/draft-ietf-mpls-over-l2tpv3-01.txt --OtherAccess Content-Type: Message/External-body; name="draft-ietf-mpls-over-l2tpv3-01.txt"; site="ftp.ietf.org"; access-type="anon-ftp"; directory="internet-drafts" Content-Type: text/plain Content-ID: <2006-2-27140458.I-D@ietf.org> --OtherAccess-- --NextPart Content-Type: text/plain; charset="us-ascii" MIME-Version: 1.0 Content-Transfer-Encoding: 7bit Content-Disposition: inline _______________________________________________ mpls mailing list mpls@lists.ietf.org https://www1.ietf.org/mailman/listinfo/mpls --NextPart-- From mpls-bounces@lists.ietf.org Mon Feb 27 16:22:58 2006 Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com) by megatron.ietf.org with esmtp (Exim 4.43) id 1FDpUY-0008V9-A8; Mon, 27 Feb 2006 16:01:14 -0500 Received: from [10.91.34.44] (helo=ietf-mx.ietf.org) by megatron.ietf.org with esmtp (Exim 4.43) id 1FDpU8-00073x-4y; Mon, 27 Feb 2006 16:00:48 -0500 Received: from willow.neustar.com ([209.173.53.84]) by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1FDpU7-0003Fv-Ry; Mon, 27 Feb 2006 16:00:48 -0500 Received: from stiedprstage1.ietf.org (stiedprstage1.va.neustar.com [10.31.47.10]) by willow.neustar.com (8.12.8/8.12.8) with ESMTP id k1RKo29W019353 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO); Mon, 27 Feb 2006 20:50:02 GMT Received: from ietf by stiedprstage1.ietf.org with local (Exim 4.43) id 1FDpJi-00072O-9w; Mon, 27 Feb 2006 15:50:02 -0500 Content-Type: Multipart/Mixed; Boundary="NextPart" Mime-Version: 1.0 To: i-d-announce@ietf.org From: Internet-Drafts@ietf.org Message-Id: Date: Mon, 27 Feb 2006 15:50:02 -0500 X-Spam-Score: 0.3 (/) X-Scan-Signature: 8de5f93cb2b4e3bee75302e9eacc33db Cc: mpls@lists.ietf.org Subject: [mpls] I-D ACTION:draft-ietf-mpls-explicit-resource-control-bundle-01.txt X-BeenThere: mpls@lists.ietf.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Multi-Protocol Label Switching WG List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Errors-To: mpls-bounces@lists.ietf.org --NextPart A New Internet-Draft is available from the on-line Internet-Drafts directories. This draft is a work item of the Multiprotocol Label Switching Working Group of the IETF. Title : Component Link Recording and Resource Control for GMPLS Link Bundles Author(s) : A. Zamfir, et al. Filename : draft-ietf-mpls-explicit-resource-control-bundle-01.txt Pages : 12 Date : 2006-2-27 Record Route is a useful administrative tool that has been used extensively by the service providers. However, when TE links are bundled, identification of label resource in RRO is not enough for the administrative purpose. Network service providers would like to know the component link within a TE link that is being used by a given LSP. In other words, when link bundling is used, resource recording requires mechanisms to specify the component link identifier, along with the TE link identifier and Label. As , it is not possible to record component link in the RRO, this draft defines the extensions to RSVP-TE [RFC3209] and [RFC3473] to specify component link identifiers for resource recording purposes. This draft also defines the ERO counterpart of the RRO extension. The ERO extensions are needed to perform explicit label/ resource control over bundled TE link. Hence, this draft defines the extensions to RSVP-TE [RFC3209] and [RFC3473] to specify component link identifiers for explicit resource control and recording over GMPLS link bundles. A URL for this Internet-Draft is: http://www.ietf.org/internet-drafts/draft-ietf-mpls-explicit-resource-control-bundle-01.txt To remove yourself from the I-D Announcement list, send a message to i-d-announce-request@ietf.org with the word unsubscribe in the body of the message. You can also visit https://www1.ietf.org/mailman/listinfo/I-D-announce to change your subscription settings. Internet-Drafts are also available by anonymous FTP. Login with the username "anonymous" and a password of your e-mail address. After logging in, type "cd internet-drafts" and then "get draft-ietf-mpls-explicit-resource-control-bundle-01.txt". A list of Internet-Drafts directories can be found in http://www.ietf.org/shadow.html or ftp://ftp.ietf.org/ietf/1shadow-sites.txt Internet-Drafts can also be obtained by e-mail. Send a message to: mailserv@ietf.org. In the body type: "FILE /internet-drafts/draft-ietf-mpls-explicit-resource-control-bundle-01.txt". NOTE: The mail server at ietf.org can return the document in MIME-encoded form by using the "mpack" utility. To use this feature, insert the command "ENCODING mime" before the "FILE" command. To decode the response(s), you will need "munpack" or a MIME-compliant mail reader. Different MIME-compliant mail readers exhibit different behavior, especially when dealing with "multipart" MIME messages (i.e. documents which have been split up into multiple messages), so check your local documentation on how to manipulate these messages. Below is the data which will enable a MIME compliant mail reader implementation to automatically retrieve the ASCII version of the Internet-Draft. --NextPart Content-Type: Multipart/Alternative; Boundary="OtherAccess" --OtherAccess Content-Type: Message/External-body; access-type="mail-server"; server="mailserv@ietf.org" Content-Type: text/plain Content-ID: <2006-2-27141645.I-D@ietf.org> ENCODING mime FILE /internet-drafts/draft-ietf-mpls-explicit-resource-control-bundle-01.txt --OtherAccess Content-Type: Message/External-body; name="draft-ietf-mpls-explicit-resource-control-bundle-01.txt"; site="ftp.ietf.org"; access-type="anon-ftp"; directory="internet-drafts" Content-Type: text/plain Content-ID: <2006-2-27141645.I-D@ietf.org> --OtherAccess-- --NextPart Content-Type: text/plain; charset="us-ascii" MIME-Version: 1.0 Content-Transfer-Encoding: 7bit Content-Disposition: inline _______________________________________________ mpls mailing list mpls@lists.ietf.org https://www1.ietf.org/mailman/listinfo/mpls --NextPart-- From mpls-bounces@lists.ietf.org Tue Feb 28 00:46:30 2006 Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com) by megatron.ietf.org with esmtp (Exim 4.43) id 1FDxef-0000zz-EP; Tue, 28 Feb 2006 00:44:13 -0500 Received: from [10.91.34.44] (helo=ietf-mx.ietf.org) by megatron.ietf.org with esmtp (Exim 4.43) id 1FDxee-0000xJ-BS for mpls@ietf.org; Tue, 28 Feb 2006 00:44:12 -0500 Received: from usjk1001.kddi.com ([211.4.169.17]) by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1FDxec-00061y-NZ for mpls@ietf.org; Tue, 28 Feb 2006 00:44:12 -0500 Received: from usjk1006.kddi.com (usjk1006 [10.96.2.3]) by usjk1001.kddi.com with ESMTP id k1S5i5a20583 for ; Tue, 28 Feb 2006 14:44:05 +0900 (JST) Received: from usjk1037 (localhost [127.0.0.1]) by usjk1006.kddi.com with SMTP id k1S5i5P13837 for ; Tue, 28 Feb 2006 14:44:05 +0900 (JST) Received: from [127.0.0.1] ([133.128.75.50]) by usjk1009.kddi.com (InterMail vM.5.01.02.00 201-253-116-121-20001201) with ESMTP id <20060228054401.QRSU23807.usjk1009.kddi.com@[127.0.0.1]> for ; Tue, 28 Feb 2006 14:44:01 +0900 Date: Tue, 28 Feb 2006 14:43:56 +0900 From: Kenji Kumaki To: mpls@ietf.org Subject: Re: [mpls] draft-vasseur-mpls-number-0-bw-te-lsps-00 In-Reply-To: <6343A00D-F629-4026-AD4B-C2EAB85CFF1C@cisco.com> References: <6343A00D-F629-4026-AD4B-C2EAB85CFF1C@cisco.com> Message-Id: <20060228143648.0019.KE-KUMAKI@kddi.com> MIME-Version: 1.0 Content-Type: text/plain; charset="US-ASCII" Content-Transfer-Encoding: 7bit X-Mailer: Becky! ver. 2.21.03 [ja] X-WAuditID: 0602281444010000017818 X-Spam-Score: 0.0 (/) X-Scan-Signature: b19722fc8d3865b147c75ae2495625f2 Cc: X-BeenThere: mpls@lists.ietf.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Multi-Protocol Label Switching WG List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Errors-To: mpls-bounces@lists.ietf.org Hi, I think this draft is very useful. Many sevice providers including my company use 0 bandwidth LSPs and them for load balance and fast reroute. I'd like to support this draft. Thanks, Kenji On Tue, 7 Feb 2006 18:45:23 -0500 JP Vasseur wrote: > Hi, > > Just to let you know that a new (quite simple) ID has been posted > proposing OSPF/ISIS Link sub-TLV to advertise the number of > unconstrained TE LSPs signaled across a link. Comments are very welcome. > > Thanks. > > JP. > > _______________________________________________ > mpls mailing list > mpls@lists.ietf.org > https://www1.ietf.org/mailman/listinfo/mpls -- Kenji Kumaki _______________________________________________ mpls mailing list mpls@lists.ietf.org https://www1.ietf.org/mailman/listinfo/mpls From mpls-bounces@lists.ietf.org Tue Feb 28 02:10:35 2006 Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com) by megatron.ietf.org with esmtp (Exim 4.43) id 1FDyyI-0005rE-Oh; Tue, 28 Feb 2006 02:08:34 -0500 Received: from [10.91.34.44] (helo=ietf-mx.ietf.org) by megatron.ietf.org with esmtp (Exim 4.43) id 1FDyyG-0005oN-86 for mpls@ietf.org; Tue, 28 Feb 2006 02:08:32 -0500 Received: from lhrga01-in.huawei.com ([57.66.76.5] helo=huawei.com) by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1FDyyE-0008KP-QY for mpls@ietf.org; Tue, 28 Feb 2006 02:08:32 -0500 Received: from huawei.com ([172.24.2.9]) by lhrga01-in.huawei.com (iPlanet Messaging Server 5.2 HotFix 1.25 (built Mar 3 2004)) with ESMTP id <0IVD0011GWYRAV@lhrga01-in.huawei.com> for mpls@ietf.org; Tue, 28 Feb 2006 06:35:16 +0000 (GMT) Received: from huawei.com (szxga03-in [172.24.2.9]) by szxga03-in.huawei.com (iPlanet Messaging Server 5.2 HotFix 1.25 (built Mar 3 2004)) with ESMTP id <0IVD00CMUY00SC@szxga03-in.huawei.com> for mpls@ietf.org; Tue, 28 Feb 2006 14:57:37 +0800 (CST) Received: from l48253 ([10.111.12.100]) by szxga03-in.huawei.com (iPlanet Messaging Server 5.2 HotFix 1.25 (built Mar 3 2004)) with ESMTPA id <0IVD0063GY00W1@szxga03-in.huawei.com> for mpls@ietf.org; Tue, 28 Feb 2006 14:57:36 +0800 (CST) Date: Tue, 28 Feb 2006 14:50:27 +0800 From: liushuying To: mpls@ietf.org Message-id: <00d801c63c33$425652b0$640c6f0a@china.huawei.com> MIME-version: 1.0 X-MIMEOLE: Produced By Microsoft MimeOLE V6.00.2900.2180 X-Mailer: Microsoft Outlook Express 6.00.2900.2180 X-Priority: 3 X-MSMail-priority: Normal X-Spam-Score: 0.2 (/) X-Scan-Signature: 32b73d73e8047ed17386f9799119ce43 Cc: Subject: [mpls] Reroute Extensions to LDP for P2MP LSP--draft-liu-mpls-ldp-p2mp-reroute-00.txt X-BeenThere: mpls@lists.ietf.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Multi-Protocol Label Switching WG List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Content-Type: multipart/mixed; boundary="===============1874646353==" Errors-To: mpls-bounces@lists.ietf.org This is a multi-part message in MIME format. --===============1874646353== Content-type: multipart/alternative; boundary="Boundary_(ID_5Oaay4Nt5msi0Ep+i4ttew)" This is a multi-part message in MIME format. --Boundary_(ID_5Oaay4Nt5msi0Ep+i4ttew) Content-type: text/plain; charset=gb2312 Content-transfer-encoding: base64 SGkgZm9sa3MuDQogICAgQSBOZXcgSW50ZXJuZXQtRHJhZnQgaXMgYXZhaWxhYmxlIGZyb20gdGhl IG9uLWxpbmUgSW50ZXJuZXQtRHJhZnRzIGRpcmVjdG9yaWVzLg0KVGhlIGRyYWZ0IGNhbiBiZSBm b3VuZCBoZXJlOg0KDQpodHRwOi8vd3d3LmlldGYub3JnL2ludGVybmV0LWRyYWZ0cy9kcmFmdC1s aXUtbXBscy1sZHAtcDJtcC1yZXJvdXRlLTAwLnR4dA0KDQpUaXRsZSA6IFJlcm91dGUgRXh0ZW5z aW9ucyB0byBMRFAgZm9yIFAyTVAgTFNQDQpBdXRob3IocykgOiBTaHV5aW5nIExpdSwgR2FuZyBD aGVuZywgTGlhbnNodSBaaGVuZw0KRmlsZW5hbWUgOiBkcmFmdC1saXUtbXBscy1sZHAtcDJtcC1y ZXJvdXRlLTAwLnR4dA0KUGFnZXMgOiAyMA0KRGF0ZSA6IDIwMDYtMi0yNA0KDQpUaGlzIGRvY3Vt ZW50IGRlc2NyaWJlcyBzb21lIGV4dGVuc2lvbnMgdG8gdGhlIExhYmVsIERpc3RyaWJ1dGlvbiAN ClByb3RvY29sIChMRFApIGZvciB0aGUgcmVyb3V0ZSBvZiBwb2ludCB0byBtdWx0aS1wb2ludCAo UDJNUCkgTGFiZWwgDQpTd2l0Y2hlZCBQYXRocyAoTFNQcykgaW4gTXVsdGktUHJvdG9jb2wgTGFi ZWwgU3dpdGNoaW5nIChNUExTKSANCm5ldHdvcmtzLiBUaGUgc29sdXRpb24gcmVsaWVzIG9uIExE UCBvbmx5IGFuZCBoYXMgbm8gcmVxdWlyZW1lbnQgb2YgYSANCm11bHRpY2FzdCByb3V0aW5nIHBy b3RvY29sIGluIHRoZSBuZXR3b3JrLiAgUHJvdG9jb2wgZWxlbWVudHMgYW5kIA0KcHJvY2VkdXJl cyBmb3IgdGhpcyBzb2x1dGlvbiBhcmUgZGVzY3JpYmVkIGZvciByZXJvdXRpbmcgYSBQMk1QIExT UCANCmluIHRoZSBmb2xsb3dpbmcgY2FzZXM6MSluZXR3b3JrIGZhaWx1cmUgKGxpbmsgb3Igbm9k ZSk7IDIpYSBiZXR0ZXIgDQpwYXRoIGVtZXJnZXMgKGUuZy4gbmV3IGxpbmsgYXZhaWxhYmxlLCBt ZXRyaWMgY2hhbmdlKTszKXBsYW5uZWQgDQptYWludGVuYW5jZS4gVGhlIHJlcm91dGluZyBtZWNo YW5pc20gZGVzY3JpYmVkIGluIHRoaXMgZG9jdW1lbnQgY2FuIA0KbWluaW1pemUgdGhlIHRpbWUg b2YgdHJhZmZpYyBkaXNydXB0aW9uIHdoZW4gbmV0d29yayBmYWlsdXJlIGhhcHBlbnMuIA0KSXQg d2lsbCBhbHNvIG1pbmltaXplIHRoZSBkYXRhIGR1cGxpY2F0aW9uIGFuZCBndWFyYW50ZWUgdGhl IHRyYWZmaWMgDQpjb250aW51aXR5IGR1cmluZyB0aGUgcHJvY2VkdXJlIG9mIHJlcm91dGluZyBp biB0aGUgbGFzdCB0d28gY2FzZXMgDQptZW50aW9uZWQgYWJvdmUuIA0KDQpQbGVhc2UgZ2l2ZSB5 b3VyIGNvbW1lbnRzIG9uIHRoaXMgZG9jdW1lbnQhIFRoYW5rIHlvdSB2ZXJ5IG11Y2guDQoNCkJl c3QgcmVnYXJkcw0KU2h1eWluZyBMaXUNCkh1YVdlaSBCbGQuLCBOby4zIFhpbnhpIFJkLiwgICAN ClNoYW5nLURpIEluZm9ybWF0aW9uIEluZHVzdHJ5IEJhc2UsICAgICAgICAgICAgIA0KSGFpLURp YW4gRGlzdHJpY3QgQmVpamluZyBQLlIuIENoaW5hDQpaSVCjujEwMDA4NSANCg0KDQo= --Boundary_(ID_5Oaay4Nt5msi0Ep+i4ttew) Content-type: text/html; charset=gb2312 Content-transfer-encoding: base64 PCFET0NUWVBFIEhUTUwgUFVCTElDICItLy9XM0MvL0RURCBIVE1MIDQuMCBUcmFuc2l0aW9uYWwv L0VOIj4NCjxIVE1MPjxIRUFEPg0KPE1FVEEgaHR0cC1lcXVpdj1Db250ZW50LVR5cGUgY29udGVu dD0idGV4dC9odG1sOyBjaGFyc2V0PWdiMjMxMiI+DQo8TUVUQSBjb250ZW50PSJNU0hUTUwgNi4w MC4yOTAwLjI4MDIiIG5hbWU9R0VORVJBVE9SPg0KPFNUWUxFPjwvU1RZTEU+DQo8L0hFQUQ+DQo8 Qk9EWSBiZ0NvbG9yPSNmZmZmZmY+DQo8RElWPkhpIGZvbGtzLjwvRElWPg0KPERJVj48Rk9OVCBz aXplPTI+PEZPTlQgc2l6ZT0zPiZuYnNwOyZuYnNwOyZuYnNwOyBBIE5ldyBJbnRlcm5ldC1EcmFm dCBpcyANCmF2YWlsYWJsZSBmcm9tIHRoZSBvbi1saW5lIEludGVybmV0LURyYWZ0cyBkaXJlY3Rv cmllcy48L0ZPTlQ+PC9GT05UPjwvRElWPg0KPERJVj48Rk9OVCBzaXplPTI+PEZPTlQgc2l6ZT0z PlRoZSBkcmFmdCBjYW4gYmUgZm91bmQgaGVyZTo8L0ZPTlQ+PC9GT05UPjwvRElWPg0KPERJVj48 Rk9OVCBzaXplPTI+PEZPTlQgc2l6ZT0zPjxGT05UIHNpemU9Mj48L0ZPTlQ+Jm5ic3A7PC9ESVY+ DQo8RElWPjxGT05UIHNpemU9Mj48QSANCmhyZWY9Imh0dHA6Ly93d3cuaWV0Zi5vcmcvaW50ZXJu ZXQtZHJhZnRzL2RyYWZ0LWxpdS1tcGxzLWxkcC1wMm1wLXJlcm91dGUtMDAudHh0Ij5odHRwOi8v d3d3LmlldGYub3JnL2ludGVybmV0LWRyYWZ0cy9kcmFmdC1saXUtbXBscy1sZHAtcDJtcC1yZXJv dXRlLTAwLnR4dDwvQT48L0ZPTlQ+PC9ESVY+PC9GT05UPjwvRk9OVD4NCjxESVY+PEZPTlQgc2l6 ZT0yPjxGT05UIHNpemU9Mz48Rk9OVCBzaXplPTI+PC9GT05UPjxCUj5UaXRsZSA6IFJlcm91dGUg DQpFeHRlbnNpb25zIHRvIExEUCBmb3IgUDJNUCBMU1A8QlI+QXV0aG9yKHMpIDogU2h1eWluZyBM aXUsIEdhbmcgQ2hlbmcsIExpYW5zaHUgDQpaaGVuZzxCUj5GaWxlbmFtZSA6IGRyYWZ0LWxpdS1t cGxzLWxkcC1wMm1wLXJlcm91dGUtMDAudHh0PC9GT05UPjwvRk9OVD48L0RJVj4NCjxESVY+PEZP TlQgc2l6ZT0yPjxGT05UIHNpemU9Mz5QYWdlcyA6IDIwPEJSPkRhdGUgOiANCjIwMDYtMi0yNDxC Uj48L0ZPTlQ+PC9GT05UPjwvRElWPg0KPERJVj48Rk9OVCBzaXplPTI+PEZPTlQgc2l6ZT0zPlRo aXMgZG9jdW1lbnQgZGVzY3JpYmVzIHNvbWUgZXh0ZW5zaW9ucyB0byB0aGUgDQpMYWJlbCBEaXN0 cmlidXRpb24mbmJzcDs8QlI+UHJvdG9jb2wgKExEUCkgZm9yIHRoZSByZXJvdXRlIG9mIHBvaW50 IHRvIA0KbXVsdGktcG9pbnQgKFAyTVApIExhYmVsJm5ic3A7PEJSPlN3aXRjaGVkIFBhdGhzIChM U1BzKSBpbiBNdWx0aS1Qcm90b2NvbCBMYWJlbCANClN3aXRjaGluZyAoTVBMUykmbmJzcDs8QlI+ bmV0d29ya3MuIFRoZSBzb2x1dGlvbiByZWxpZXMgb24gTERQIG9ubHkgYW5kIGhhcyBubyANCnJl cXVpcmVtZW50IG9mIGEmbmJzcDs8QlI+bXVsdGljYXN0IHJvdXRpbmcgcHJvdG9jb2wgaW4gdGhl IG5ldHdvcmsuJm5ic3A7IA0KUHJvdG9jb2wgZWxlbWVudHMgYW5kJm5ic3A7PEJSPnByb2NlZHVy ZXMgZm9yIHRoaXMgc29sdXRpb24gYXJlIGRlc2NyaWJlZCBmb3IgDQpyZXJvdXRpbmcgYSBQMk1Q IExTUCZuYnNwOzxCUj5pbiB0aGUgZm9sbG93aW5nIGNhc2VzOjEpbmV0d29yayBmYWlsdXJlIChs aW5rIG9yIA0Kbm9kZSk7IDIpYSBiZXR0ZXImbmJzcDs8QlI+cGF0aCBlbWVyZ2VzIChlLmcuIG5l dyBsaW5rIGF2YWlsYWJsZSwgbWV0cmljIA0KY2hhbmdlKTszKXBsYW5uZWQmbmJzcDs8QlI+bWFp bnRlbmFuY2UuIFRoZSByZXJvdXRpbmcgbWVjaGFuaXNtIGRlc2NyaWJlZCBpbiANCnRoaXMgZG9j dW1lbnQgY2FuJm5ic3A7PEJSPm1pbmltaXplIHRoZSB0aW1lIG9mIHRyYWZmaWMgZGlzcnVwdGlv biB3aGVuIG5ldHdvcmsgDQpmYWlsdXJlIGhhcHBlbnMuJm5ic3A7PEJSPkl0IHdpbGwgYWxzbyBt aW5pbWl6ZSB0aGUgZGF0YSBkdXBsaWNhdGlvbiBhbmQgDQpndWFyYW50ZWUgdGhlIHRyYWZmaWMm bmJzcDs8QlI+Y29udGludWl0eSBkdXJpbmcgdGhlIHByb2NlZHVyZSBvZiByZXJvdXRpbmcgaW4g DQp0aGUgbGFzdCB0d28gY2FzZXMmbmJzcDs8QlI+bWVudGlvbmVkIGFib3ZlLiA8L0ZPTlQ+PC9G T05UPjwvRElWPg0KPERJVj48Rk9OVCBzaXplPTI+PEZPTlQgc2l6ZT0zPjwvRk9OVD48L0ZPTlQ+ Jm5ic3A7PC9ESVY+DQo8RElWPjxGT05UIHNpemU9Mj48Rk9OVCBzaXplPTM+UGxlYXNlIGdpdmUg eW91ciBjb21tZW50cyZuYnNwO29uIHRoaXMgZG9jdW1lbnQhIA0KVGhhbmsgeW91IHZlcnkgbXVj aC48L0ZPTlQ+PC9GT05UPjwvRElWPg0KPERJVj48Rk9OVCBzaXplPTI+PC9GT05UPiZuYnNwOzwv RElWPg0KPERJVj48Rk9OVCBzaXplPTI+PEZPTlQgc2l6ZT0zPkJlc3QgcmVnYXJkczwvRk9OVD48 L0RJVj4NCjxESVY+DQo8RElWPjxGT05UIGZhY2U9y87M5SBzaXplPTM+PFNQQU4gc3R5bGU9IkZP TlQtU0laRTogMTBwdCI+U2h1eWluZyANCkxpdTwvU1BBTj48L0ZPTlQ+PC9ESVY+DQo8RElWPjxG T05UIGZhY2U9y87M5T48U1BBTiBzdHlsZT0iRk9OVC1TSVpFOiAxMHB0Ij48L1NQQU4+PC9GT05U PjxGT05UIGZhY2U9y87M5SANCnNpemU9Mz48U1BBTiBzdHlsZT0iRk9OVC1TSVpFOiAxMHB0Ij5I dWFXZWkgQmxkLiwgTm8uMyBYaW54aSBSZC4sJm5ic3A7Jm5ic3A7IA0KPEJSPlNoYW5nLURpIElu Zm9ybWF0aW9uIEluZHVzdHJ5IA0KQmFzZSwmbmJzcDsmbmJzcDsmbmJzcDsmbmJzcDsmbmJzcDsm bmJzcDsmbmJzcDsmbmJzcDsmbmJzcDsmbmJzcDsmbmJzcDsmbmJzcDsgDQo8QlI+SGFpLURpYW4g RGlzdHJpY3QgQmVpamluZyBQLlIuIENoaW5hPEJSPlpJUDxTUEFOIA0KbGFuZz1aSC1DTj6jujwv U1BBTj4xMDAwODUmbmJzcDs8L1NQQU4+PC9GT05UPjwvRElWPjxCUj48QlI+PC9ESVY+PC9GT05U PjwvQk9EWT48L0hUTUw+DQo= --Boundary_(ID_5Oaay4Nt5msi0Ep+i4ttew)-- --===============1874646353== Content-Type: text/plain; charset="us-ascii" MIME-Version: 1.0 Content-Transfer-Encoding: 7bit Content-Disposition: inline _______________________________________________ mpls mailing list mpls@lists.ietf.org https://www1.ietf.org/mailman/listinfo/mpls --===============1874646353==-- From mpls-bounces@lists.ietf.org Tue Feb 28 16:05:16 2006 Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com) by megatron.ietf.org with esmtp (Exim 4.43) id 1FEBzo-0007Tt-RD; Tue, 28 Feb 2006 16:03:00 -0500 Received: from [10.91.34.44] (helo=ietf-mx.ietf.org) by megatron.ietf.org with esmtp (Exim 4.43) id 1FEBpp-0000W8-5g; Tue, 28 Feb 2006 15:52:41 -0500 Received: from [156.154.16.129] (helo=chiedprmail1.ietf.org) by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1FEBnK-0001a0-F4; Tue, 28 Feb 2006 15:50:06 -0500 Received: from [156.154.24.129] (helo=oak.neustar.com) by chiedprmail1.ietf.org with esmtp (Exim 4.43) id 1FEBnG-0003U6-7p; Tue, 28 Feb 2006 15:50:06 -0500 Received: from stiedprstage1.ietf.org (stiedprstage1.va.neustar.com [10.31.47.10]) by oak.neustar.com (8.12.8/8.12.8) with ESMTP id k1SKo1BX019704 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO); Tue, 28 Feb 2006 20:50:01 GMT Received: from ietf by stiedprstage1.ietf.org with local (Exim 4.43) id 1FEBnF-0000zc-Qj; Tue, 28 Feb 2006 15:50:01 -0500 Content-Type: Multipart/Mixed; Boundary="NextPart" Mime-Version: 1.0 To: i-d-announce@ietf.org From: Internet-Drafts@ietf.org Message-Id: Date: Tue, 28 Feb 2006 15:50:01 -0500 X-Spam-Score: -5.9 (-----) X-Scan-Signature: 32b73d73e8047ed17386f9799119ce43 Cc: mpls@lists.ietf.org Subject: [mpls] I-D ACTION:draft-ietf-mpls-p2mp-oam-reqs-01.txt X-BeenThere: mpls@lists.ietf.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Multi-Protocol Label Switching WG List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Errors-To: mpls-bounces@lists.ietf.org --NextPart A New Internet-Draft is available from the on-line Internet-Drafts directories. This draft is a work item of the Multiprotocol Label Switching Working Group of the IETF. Title : OAM Requirements for Point-to-Multipoint MPLS Networks Author(s) : A. Farrel, et al. Filename : draft-ietf-mpls-p2mp-oam-reqs-01.txt Pages : 12 Date : 2006-2-28 Multi-Protocol Label Switching (MPLS) has been extended to encompass point-to-multipoint (P2MP) Label Switched Paths (LSPs). As with point-to-point MPLS LSPs the requirement to detect, handle and diagnose control and data plane defects is critical. For operators deploying services based on P2MP MPLS LSPs the detection and specification of how to handle those defects is important because such defects may not only affect the fundamentals of an MPLS network, but also because they may impact service level specification commitments for customers of their network. A URL for this Internet-Draft is: http://www.ietf.org/internet-drafts/draft-ietf-mpls-p2mp-oam-reqs-01.txt To remove yourself from the I-D Announcement list, send a message to i-d-announce-request@ietf.org with the word unsubscribe in the body of the message. You can also visit https://www1.ietf.org/mailman/listinfo/I-D-announce to change your subscription settings. Internet-Drafts are also available by anonymous FTP. Login with the username "anonymous" and a password of your e-mail address. After logging in, type "cd internet-drafts" and then "get draft-ietf-mpls-p2mp-oam-reqs-01.txt". A list of Internet-Drafts directories can be found in http://www.ietf.org/shadow.html or ftp://ftp.ietf.org/ietf/1shadow-sites.txt Internet-Drafts can also be obtained by e-mail. Send a message to: mailserv@ietf.org. In the body type: "FILE /internet-drafts/draft-ietf-mpls-p2mp-oam-reqs-01.txt". NOTE: The mail server at ietf.org can return the document in MIME-encoded form by using the "mpack" utility. To use this feature, insert the command "ENCODING mime" before the "FILE" command. To decode the response(s), you will need "munpack" or a MIME-compliant mail reader. Different MIME-compliant mail readers exhibit different behavior, especially when dealing with "multipart" MIME messages (i.e. documents which have been split up into multiple messages), so check your local documentation on how to manipulate these messages. Below is the data which will enable a MIME compliant mail reader implementation to automatically retrieve the ASCII version of the Internet-Draft. --NextPart Content-Type: Multipart/Alternative; Boundary="OtherAccess" --OtherAccess Content-Type: Message/External-body; access-type="mail-server"; server="mailserv@ietf.org" Content-Type: text/plain Content-ID: <2006-2-28142619.I-D@ietf.org> ENCODING mime FILE /internet-drafts/draft-ietf-mpls-p2mp-oam-reqs-01.txt --OtherAccess Content-Type: Message/External-body; name="draft-ietf-mpls-p2mp-oam-reqs-01.txt"; site="ftp.ietf.org"; access-type="anon-ftp"; directory="internet-drafts" Content-Type: text/plain Content-ID: <2006-2-28142619.I-D@ietf.org> --OtherAccess-- --NextPart Content-Type: text/plain; charset="us-ascii" MIME-Version: 1.0 Content-Transfer-Encoding: 7bit Content-Disposition: inline _______________________________________________ mpls mailing list mpls@lists.ietf.org https://www1.ietf.org/mailman/listinfo/mpls --NextPart--