From mpls-bounces@lists.ietf.org Fri Jul 01 04:10:28 2005 Received: from localhost.localdomain ([127.0.0.1] helo=megatron.ietf.org) by megatron.ietf.org with esmtp (Exim 4.32) id 1DoGbU-0008Jd-F0; Fri, 01 Jul 2005 04:10:28 -0400 Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org) by megatron.ietf.org with esmtp (Exim 4.32) id 1DoGbS-0008Ig-F7 for mpls@megatron.ietf.org; Fri, 01 Jul 2005 04:10:26 -0400 Received: from ietf-mx.ietf.org (ietf-mx [132.151.6.1]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id EAA05068 for ; Fri, 1 Jul 2005 04:10:24 -0400 (EDT) Received: from p-mail1.rd.francetelecom.com ([195.101.245.15]) by ietf-mx.ietf.org with esmtp (Exim 4.33) id 1DoH1M-0006r4-Tj for mpls@ietf.org; Fri, 01 Jul 2005 04:37:14 -0400 Received: from ftrdmel1.rd.francetelecom.fr ([10.193.117.152]) by ftrdsmtp1.rd.francetelecom.fr with Microsoft SMTPSVC(6.0.3790.211); Fri, 1 Jul 2005 10:10:22 +0200 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] draft-zamfir-explicit-resource-control-bundle-05.txt as a wgdoc Date: Fri, 1 Jul 2005 10:10:21 +0200 Message-ID: Thread-Topic: [mpls] draft-zamfir-explicit-resource-control-bundle-05.txt as a wgdoc Thread-Index: AcV9QTqUj/7hxucLRXSiEYkvugSxYQA0v4Hw From: "LE ROUX Jean-Louis RD-CORE-LAN" To: "Loa Andersson" , X-OriginalArrivalTime: 01 Jul 2005 08:10:22.0361 (UTC) FILETIME=[53FF4090:01C57E14] X-Spam-Score: 0.0 (/) X-Scan-Signature: 21c69d3cfc2dd19218717dbe1d974352 Content-Transfer-Encoding: quoted-printable Cc: Bill Fenner 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 This ID should be adopted as WG doc Regards JL >-----Message d'origine----- >De : mpls-bounces@lists.ietf.org=20 >[mailto:mpls-bounces@lists.ietf.org] De la part de Loa Andersson >Envoy=E9 : jeudi 30 juin 2005 08:56 >=C0 : mpls@ietf.org >Cc : Bill Fenner >Objet : [mpls]=20 >draft-zamfir-explicit-resource-control-bundle-05.txt as a wgdoc > > >Working group, > >in Minneapolis we discussed the=20 >draft-zamfir-explicit-resource-control-bundle-05.txt >(well an earlier version but anyway...) The authors suggested=20 >that we make it a wg document. There were pretty good support=20 >for this at the meeting could you before July 18th state your=20 >opinions on making it a wg document. > > >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 Fri Jul 01 10:10:57 2005 Received: from localhost.localdomain ([127.0.0.1] helo=megatron.ietf.org) by megatron.ietf.org with esmtp (Exim 4.32) id 1DoMEL-0002EQ-9m; Fri, 01 Jul 2005 10:10:57 -0400 Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org) by megatron.ietf.org with esmtp (Exim 4.32) id 1DoMEI-0002EL-Mc for mpls@megatron.ietf.org; Fri, 01 Jul 2005 10:10:54 -0400 Received: from ietf-mx.ietf.org (ietf-mx [132.151.6.1]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id KAA27902 for ; Fri, 1 Jul 2005 10:10:52 -0400 (EDT) Received: from zrc2s0jx.nortelnetworks.com ([47.103.122.112]) by ietf-mx.ietf.org with esmtp (Exim 4.33) id 1DoMeF-0004Ra-A1 for mpls@ietf.org; Fri, 01 Jul 2005 10:37:45 -0400 Received: from zrtphxm2.corp.nortel.com (zrtphxm2.corp.nortel.com [47.140.202.51]) by zrc2s0jx.nortelnetworks.com (Switch-2.2.6/Switch-2.2.0) with ESMTP id j61EAfI22521; Fri, 1 Jul 2005 09:10:41 -0500 (CDT) X-MimeOLE: Produced By Microsoft Exchange V6.5.7226.0 Content-class: urn:content-classes:message Subject: RE: [mpls] draft-zamfir-explicit-resource-control-bundle-05.txt as a wgdoc Date: Fri, 1 Jul 2005 10:10:20 -0400 Message-ID: <34B3EAA5B3066A42914D28C5ECF5FEA402D2B451@zrtphxm2> Thread-Topic: [mpls] draft-zamfir-explicit-resource-control-bundle-05.txt as a wgdoc Thread-Index: AcV9QQHMmXxBkv4sQUqBk8dIyJXFqwBBB7cA From: "Don Fedyk" To: "Loa Andersson" , X-Spam-Score: 0.0 (/) X-Scan-Signature: c1c65599517f9ac32519d043c37c5336 Cc: Bill Fenner 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 Loa In Favor of making this a WG document. The feature is useful. (Also in favor of clarifying the forward compatibility section. I cannot quite parse it in its current form.) Regards, Don > -----Original Message----- > From: mpls-bounces@lists.ietf.org > [mailto:mpls-bounces@lists.ietf.org] On Behalf Of Loa Andersson > Sent: Thursday, June 30, 2005 2:56 AM > To: mpls@ietf.org > Cc: Bill Fenner > Subject: [mpls] > draft-zamfir-explicit-resource-control-bundle-05.txt as a wgdoc > > > Working group, > > in Minneapolis we discussed the > draft-zamfir-explicit-resource-control-bundle-05.txt > (well an earlier version but anyway...) The authors suggested > that we make it a wg document. There were pretty good support > for this at the meeting could you before July 18th state your > opinions on making it a wg document. > > > 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 Tue Jul 05 18:50:04 2005 Received: from localhost.localdomain ([127.0.0.1] helo=megatron.ietf.org) by megatron.ietf.org with esmtp (Exim 4.32) id 1DpwEu-00053M-KO; Tue, 05 Jul 2005 18:50:04 -0400 Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org) by megatron.ietf.org with esmtp (Exim 4.32) id 1DpwEs-00052Y-4Z for mpls@megatron.ietf.org; Tue, 05 Jul 2005 18:50:02 -0400 Received: from newodin.ietf.org (newodin.ietf.org [10.27.6.50]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id SAA11772 for ; Tue, 5 Jul 2005 18:49:59 -0400 (EDT) Received: from mlee by newodin.ietf.org with local (Exim 4.43) id 1DpwEr-0007bh-Ln; Tue, 05 Jul 2005 18:50:01 -0400 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, 05 Jul 2005 18:50:01 -0400 Cc: mpls@ietf.org Subject: [mpls] I-D ACTION:draft-ietf-mpls-p2mp-sig-requirement-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 --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 : Signaling Requirements for Point to Multipoint Traffic Engineered MPLS LSPs Author(s) : S. Yasukawa Filename : draft-ietf-mpls-p2mp-sig-requirement-03.txt Pages : 28 Date : 2005-7-5 This document presents a set of requirements for the establishment and maintenance of Point-to-Multipoint (P2MP) Traffic Engineered (TE) Multiprotocol Label Switching (MPLS) Label Switched Paths (LSPs). There is no intent to specify solution specific details nor application specific requirements in this document. The requirements presented in this document are not limited to the requirements of packet switched networks, but also encompass the requirements of Layer two Switching (L2SC), Time Division Multiplexing (TDM), lambda and port switching networks managed by Generalized MPLS (GMPLS) protocols. Protocol solutions developed to meet the requirements set out in this document must attempt to be equally applicable to MPLS and GMPLS. A URL for this Internet-Draft is: http://www.ietf.org/internet-drafts/draft-ietf-mpls-p2mp-sig-requirement-03.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-sig-requirement-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@ietf.org. In the body type: "FILE /internet-drafts/draft-ietf-mpls-p2mp-sig-requirement-03.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: <2005-7-5171432.I-D@ietf.org> ENCODING mime FILE /internet-drafts/draft-ietf-mpls-p2mp-sig-requirement-03.txt --OtherAccess Content-Type: Message/External-body; name="draft-ietf-mpls-p2mp-sig-requirement-03.txt"; site="ftp.ietf.org"; access-type="anon-ftp"; directory="internet-drafts" Content-Type: text/plain Content-ID: <2005-7-5171432.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 Wed Jul 06 06:40:38 2005 Received: from localhost.localdomain ([127.0.0.1] helo=megatron.ietf.org) by megatron.ietf.org with esmtp (Exim 4.32) id 1Dq7KY-0002W9-6I; Wed, 06 Jul 2005 06:40:38 -0400 Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org) by megatron.ietf.org with esmtp (Exim 4.32) id 1Dq7KV-0002VV-SI for mpls@megatron.ietf.org; Wed, 06 Jul 2005 06:40:35 -0400 Received: from ietf-mx.ietf.org (ietf-mx [132.151.6.1]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id GAA22161 for ; Wed, 6 Jul 2005 06:40:29 -0400 (EDT) From: neil.2.harrison@bt.com Received: from smtp4.smtp.bt.com ([217.32.164.151]) by ietf-mx.ietf.org with esmtp (Exim 4.33) id 1Dq7e5-0002I5-9Y for mpls@ietf.org; Wed, 06 Jul 2005 07:00:50 -0400 Received: from i2km95-ukbr.domain1.systemhost.net ([193.113.197.29]) by smtp4.smtp.bt.com with Microsoft SMTPSVC(6.0.3790.211); Wed, 6 Jul 2005 11:32:39 +0100 Received: from i2km07-ukbr.domain1.systemhost.net ([193.113.197.26]) by i2km95-ukbr.domain1.systemhost.net with Microsoft SMTPSVC(5.0.2195.6713); Wed, 6 Jul 2005 11:32:35 +0100 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] I-D ACTION:draft-ietf-mpls-p2mp-sig-requirement-03.txt Date: Wed, 6 Jul 2005 11:32:35 +0100 Message-ID: <0536FC9B908BEC4597EE721BE6A353890A9F1D77@i2km07-ukbr.domain1.systemhost.net> Thread-Topic: [mpls] I-D ACTION:draft-ietf-mpls-p2mp-sig-requirement-03.txt Thread-Index: AcWBtD5uzNGTBNRkS/+OMb6ZlA++ngAXgcgQ To: X-OriginalArrivalTime: 06 Jul 2005 10:32:35.0450 (UTC) FILETIME=[062E0DA0:01C58216] X-Spam-Score: 0.3 (/) X-Scan-Signature: 9466e0365fc95844abaf7c3f15a05c7d Content-Transfer-Encoding: quoted-printable 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 Seisho, I have a question on this draft: In section 1 there is the following stated requirement: "A P2MP TE LSP will be protected by fast error recovery mechanisms to minimize disconnection of a P2MP service." Which is obviously sensible, and of course implies that all the defect cases of interest can be detected and the appropriate consequent actions taken. Note this should include defects of this layer network and not just defects that arise in lower layer networks. And remember....the links between nodes in this layer network are provided by (p2p) trails in a lower layer network....and this client/server relationship recurses to the duct. The point I am making here is that IF the lower layer network has decent OAM itself you should get some indication of failure from this, but this is over/above any defects you detect in this layer network either from (i) lower layer defects or (ii) defects arising in this layer network (which of course cannot be detected at all in any lower layer network). Yet it says in section 1.1 that a 'non-objective' is: "OAM for P2MP LSPs" Can someone please explain this apparent contradiction? regards, Neil _______________________________________________ mpls mailing list mpls@lists.ietf.org https://www1.ietf.org/mailman/listinfo/mpls From mpls-bounces@lists.ietf.org Wed Jul 06 15:50:05 2005 Received: from localhost.localdomain ([127.0.0.1] helo=megatron.ietf.org) by megatron.ietf.org with esmtp (Exim 4.32) id 1DqFuG-0007yo-R5; Wed, 06 Jul 2005 15:50:04 -0400 Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org) by megatron.ietf.org with esmtp (Exim 4.32) id 1DqFuE-0007uL-Au for mpls@megatron.ietf.org; Wed, 06 Jul 2005 15:50:02 -0400 Received: from newodin.ietf.org (newodin.ietf.org [10.27.6.50]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id PAA10044 for ; Wed, 6 Jul 2005 15:50:00 -0400 (EDT) Received: from mlee by newodin.ietf.org with local (Exim 4.43) id 1DqFuE-00087h-0Q; Wed, 06 Jul 2005 15:50:02 -0400 Content-Type: Multipart/Mixed; Boundary="NextPart" Mime-Version: 1.0 To: i-d-announce@ietf.org From: Internet-Drafts@ietf.org Message-Id: Date: Wed, 06 Jul 2005 15:50:02 -0400 Cc: mpls@ietf.org Subject: [mpls] I-D ACTION:draft-ietf-mpls-ecmp-bcp-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: , 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 : Avoiding Equal Cost Multipath Treatment in MPLS Networks Author(s) : G. Swallow, et al. Filename : draft-ietf-mpls-ecmp-bcp-01.txt Pages : 7 Date : 2005-7-6 This document describes the Equal Cost Multipath (ECMP) behavior of currently deployed MPLS networks and makes best practice recommendations for anyone defining an application to run over an MPLS network and wishes to avoid such treatment. A URL for this Internet-Draft is: http://www.ietf.org/internet-drafts/draft-ietf-mpls-ecmp-bcp-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-ecmp-bcp-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-ecmp-bcp-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: <2005-7-6115414.I-D@ietf.org> ENCODING mime FILE /internet-drafts/draft-ietf-mpls-ecmp-bcp-01.txt --OtherAccess Content-Type: Message/External-body; name="draft-ietf-mpls-ecmp-bcp-01.txt"; site="ftp.ietf.org"; access-type="anon-ftp"; directory="internet-drafts" Content-Type: text/plain Content-ID: <2005-7-6115414.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 Wed Jul 06 18:45:26 2005 Received: from localhost.localdomain ([127.0.0.1] helo=megatron.ietf.org) by megatron.ietf.org with esmtp (Exim 4.32) id 1DqIdy-0004Qj-Rv; Wed, 06 Jul 2005 18:45:26 -0400 Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org) by megatron.ietf.org with esmtp (Exim 4.32) id 1DqIdw-0004Ms-41 for mpls@megatron.ietf.org; Wed, 06 Jul 2005 18:45:24 -0400 Received: from ietf-mx.ietf.org (ietf-mx [132.151.6.1]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id SAA07475 for ; Wed, 6 Jul 2005 18:45:21 -0400 (EDT) Received: from relay2.mail.uk.clara.net ([80.168.70.142]) by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1DqJ50-0006Ei-Fb for mpls@ietf.org; Wed, 06 Jul 2005 19:13:22 -0400 Received: from du-069-0012.access.clara.net ([217.158.132.12] helo=Puppy) by relay2.mail.uk.clara.net with smtp (Exim 4.50) id 1DqIdo-000CpM-9A; Wed, 06 Jul 2005 23:45:18 +0100 Message-ID: <04e401c5827c$b897aa30$db849ed9@Puppy> From: "Adrian Farrel" To: , References: <0536FC9B908BEC4597EE721BE6A353890A9F1D77@i2km07-ukbr.domain1.systemhost.net> Subject: Re: [mpls] I-D ACTION:draft-ietf-mpls-p2mp-sig-requirement-03.txt Date: Wed, 6 Jul 2005 23:47:41 +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.1158 X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2800.1165 X-Spam-Score: 0.1 (/) 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 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 Neil, Speaking as a co-author of draft-ietf-mpls-p2mp-sig-requirement-03.txt and of draft-yasukawa-mpls-p2mp-oam-reqs-00.txt I can give an answer. Seisho may want to comment further. "protected by" is certainly not supposed to suggest that each and every fault can be rectified by fast error recovery mechanisms. And, of course, it would be crazy to expect that since failures of, for example, the ingress router are not recoverable. So, yes, "protected by" refers to defects that are protectable and reported/detected, and only applies if the service has actually been protected. As you say, fault rectification is only going to take place if it is detected in or reported to the layer in which we are deploying P2MP MPLS TE. Further, as we attempt to say in the P2MP OAM requirements draft (and/or inherit from the P2P OAM requirements draft) the higher layer must be careful not to react too precipitously to a fault which the lower layer may be in the process of solving. With regard to "non-objectives". The non-objectives stated are NOT non-objectives of the MPLS WG wrt to P2MP TE signaling. They are non-objectives of *this* I-D. As the specific OAM subsection states, P2MP OAM is discussed in a separate I-D. There are three reasons for this: 1. OAM is not really a signaling requirement. 2. It is sufficiently large and important that folding it into the signaling requirements I-D would make the signaling requirements I-D unwieldy. 3. P2MP OAM needs to apply more widely than just TE (e.g. to LDP multicast) Cheers, Adrian ----- Original Message ----- From: To: Cc: Sent: Wednesday, July 06, 2005 11:32 AM Subject: RE: [mpls] I-D ACTION:draft-ietf-mpls-p2mp-sig-requirement-03.txt Seisho, I have a question on this draft: In section 1 there is the following stated requirement: "A P2MP TE LSP will be protected by fast error recovery mechanisms to minimize disconnection of a P2MP service." Which is obviously sensible, and of course implies that all the defect cases of interest can be detected and the appropriate consequent actions taken. Note this should include defects of this layer network and not just defects that arise in lower layer networks. And remember....the links between nodes in this layer network are provided by (p2p) trails in a lower layer network....and this client/server relationship recurses to the duct. The point I am making here is that IF the lower layer network has decent OAM itself you should get some indication of failure from this, but this is over/above any defects you detect in this layer network either from (i) lower layer defects or (ii) defects arising in this layer network (which of course cannot be detected at all in any lower layer network). Yet it says in section 1.1 that a 'non-objective' is: "OAM for P2MP LSPs" Can someone please explain this apparent contradiction? regards, Neil _______________________________________________ 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 Jul 07 07:55:48 2005 Received: from localhost.localdomain ([127.0.0.1] helo=megatron.ietf.org) by megatron.ietf.org with esmtp (Exim 4.32) id 1DqUyq-0002pu-GF; Thu, 07 Jul 2005 07:55:48 -0400 Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org) by megatron.ietf.org with esmtp (Exim 4.32) id 1DqUyo-0002mD-Oc for mpls@megatron.ietf.org; Thu, 07 Jul 2005 07:55:46 -0400 Received: from ietf-mx.ietf.org (ietf-mx [132.151.6.1]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id HAA27517 for ; Thu, 7 Jul 2005 07:55:45 -0400 (EDT) From: kkhanna@isocore.com Received: from ns1.cpanel.btnaccess.com ([205.177.121.2]) by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1DqVPz-0003L7-4a for mpls@ietf.org; Thu, 07 Jul 2005 08:23:52 -0400 Received: from cpanel by ns1.cpanel.btnaccess.com with local (Exim 4.50) id 1DqUyl-0001Jz-E4 for mpls@ietf.org; Thu, 07 Jul 2005 07:55:43 -0400 Received: from 68.228.14.164 ([68.228.14.164]) by isocore.com (Horde) with HTTP for ; Thu, 07 Jul 2005 07:55:43 -0400 Message-ID: <20050707075543.46npa1bmua3kgc8o@isocore.com> Date: Thu, 07 Jul 2005 07:55:43 -0400 To: mpls@ietf.org References: <27A0F290348F8E45AEF79889DDE65A5204F52307@exrad2.ad.rad.co.il> In-Reply-To: <27A0F290348F8E45AEF79889DDE65A5204F52307@exrad2.ad.rad.co.il> MIME-Version: 1.0 Content-Type: text/plain; charset=ISO-8859-1; format="flowed" Content-Disposition: inline Content-Transfer-Encoding: 7bit User-Agent: Internet Messaging Program (IMP) H3 (4.0) X-AntiAbuse: This header was added to track abuse, please include it with any abuse report X-AntiAbuse: Primary Hostname - ns1.cpanel.btnaccess.com X-AntiAbuse: Original Domain - ietf.org X-AntiAbuse: Originator/Caller UID/GID - [32001 502] / [47 12] X-AntiAbuse: Sender Address Domain - isocore.com X-Spam-Score: 0.3 (/) X-Scan-Signature: 0bc60ec82efc80c84b8d02f4b0e4de22 Content-Transfer-Encoding: 7bit Cc: Subject: [mpls] MPLS 2005 Program: October 16-19, Washington DC 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 MPLS 2005 International Conference Omni Shoreham Hotel, Washington DC October 16-19, 2005 http://www.mpls2005.com You are cordially invited to attend the MPLS 2005 International Conference to be held in Washington, DC from October 16-19, 2005. The 4-day event consists of highly technical sessions, tutorials, panel discussions, and exhibits. Program details are available at . Registration for the conference is now open. Early registration discounts are highly attractive and are valid for a limited time only. To register, go to . Important Dates: ------------------------ - Early Registration Rates Cut-Off Date: July 22 - Tutorials: October 16, 10:30 am - 6:00 pm - Technical Tracks: October 17-18, 8:30 am - 6:00 pm October 19, 8:30 am ? 4:45 pm - Exhibits: October 17-18, 9:00 am - 6:00 pm October 19, 9:00 am - 12:00 pm _______________________________________________ mpls mailing list mpls@lists.ietf.org https://www1.ietf.org/mailman/listinfo/mpls From mpls-bounces@lists.ietf.org Thu Jul 07 08:56:41 2005 Received: from localhost.localdomain ([127.0.0.1] helo=megatron.ietf.org) by megatron.ietf.org with esmtp (Exim 4.32) id 1DqVvk-0005Fx-U1; Thu, 07 Jul 2005 08:56:40 -0400 Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org) by megatron.ietf.org with esmtp (Exim 4.32) id 1DqVvh-0005F2-3H for mpls@megatron.ietf.org; Thu, 07 Jul 2005 08:56:37 -0400 Received: from ietf-mx.ietf.org (ietf-mx [132.151.6.1]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id IAA02558 for ; Thu, 7 Jul 2005 08:56:35 -0400 (EDT) Received: from tama5.ecl.ntt.co.jp ([129.60.39.102]) by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1DqWMp-0005kY-15 for mpls@ietf.org; Thu, 07 Jul 2005 09:24:43 -0400 Received: from vcs3.rdh.ecl.ntt.co.jp (vcs3.rdh.ecl.ntt.co.jp [129.60.39.110]) by tama5.ecl.ntt.co.jp (8.12.11/8.12.11) with ESMTP id j67CuJJO009911; Thu, 7 Jul 2005 21:56:19 +0900 (JST) Received: from vcs3.rdh.ecl.ntt.co.jp (localhost [127.0.0.1]) by vcs3.rdh.ecl.ntt.co.jp (8.12.11/8.12.11) with ESMTP id j67CuI9f023950; Thu, 7 Jul 2005 21:56:19 +0900 (JST) Received: from mfs3.rdh.ecl.ntt.co.jp (mfs3.rdh.ecl.ntt.co.jp [129.60.39.112]) by vcs3.rdh.ecl.ntt.co.jp (8.12.11/8.12.11) with ESMTP id j67CuItZ023940; Thu, 7 Jul 2005 21:56:18 +0900 (JST) Received: from mfs3.rdh.ecl.ntt.co.jp (localhost [127.0.0.1]) by mfs3.rdh.ecl.ntt.co.jp (8.12.11/8.12.11) with ESMTP id j67CuIE6026442; Thu, 7 Jul 2005 21:56:18 +0900 (JST) Received: from nttmail3.ecl.ntt.co.jp ([129.60.39.100]) by mfs3.rdh.ecl.ntt.co.jp (8.12.11/8.12.11) with ESMTP id j67CuIkw026439; Thu, 7 Jul 2005 21:56:18 +0900 (JST) Received: from eclscan3.m.ecl.ntt.co.jp (eclscan3.m.ecl.ntt.co.jp [129.60.5.69]) by nttmail3.ecl.ntt.co.jp (8.12.11/8.12.11) with ESMTP id j67CuHR3003789; Thu, 7 Jul 2005 21:56:17 +0900 (JST) Received: from eclscan3.m.ecl.ntt.co.jp (localhost [127.0.0.1]) by eclscan3.m.ecl.ntt.co.jp (8.12.11/8.12.11) with ESMTP id j67CuHRn000781; Thu, 7 Jul 2005 21:56:17 +0900 (JST) Received: from imc.m.ecl.ntt.co.jp (imc0.m.ecl.ntt.co.jp [129.60.5.141]) by eclscan3.m.ecl.ntt.co.jp (8.12.11/8.12.11) with ESMTP id j67CuH9B000775; Thu, 7 Jul 2005 21:56:17 +0900 (JST) Received: from win-yasukawa.lab.ntt.co.jp by imc.m.ecl.ntt.co.jp (8.9.3p2/3.7W) with ESMTP id VAA15041; Thu, 7 Jul 2005 21:56:16 +0900 (JST) Message-Id: <5.0.2.5.2.20050707215258.078221a0@imc.m.ecl.ntt.co.jp> X-Sender: sy003@imc.m.ecl.ntt.co.jp X-Mailer: QUALCOMM Windows Eudora Version 5.0.2-J Date: Thu, 07 Jul 2005 22:13:12 +0900 To: "Adrian Farrel" , From: Seisho Yasukawa Subject: Re: [mpls] I-D ACTION:draft-ietf-mpls-p2mp-sig-requirement-03.txt In-Reply-To: <04e401c5827c$b897aa30$db849ed9@Puppy> References: <0536FC9B908BEC4597EE721BE6A353890A9F1D77@i2km07-ukbr.domain1.systemhost.net> Mime-Version: 1.0 Content-Type: text/plain; charset="us-ascii"; format=flowed X-Spam-Score: 0.0 (/) X-Scan-Signature: b5d20af10c334b36874c0264b10f59f1 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 Neil, Thank you for reviewing the draft and providing following comments. Even though it seems me Adrian already covered my point, I would like to rephrase that we would like to cover P2MP OAM aspects in the separate draft because OAM is important and we should discuss this issue based on not only from signaling perspective. Regards, Seisho At 23:47 05/07/06 +0100, Adrian Farrel wrote: >Hi Neil, > >Speaking as a co-author of draft-ietf-mpls-p2mp-sig-requirement-03.txt and >of draft-yasukawa-mpls-p2mp-oam-reqs-00.txt I can give an answer. Seisho >may want to comment further. > >"protected by" is certainly not supposed to suggest that each and every >fault can be rectified by fast error recovery mechanisms. And, of course, >it would be crazy to expect that since failures of, for example, the >ingress router are not recoverable. > >So, yes, "protected by" refers to defects that are protectable and >reported/detected, and only applies if the service has actually been >protected. > >As you say, fault rectification is only going to take place if it is >detected in or reported to the layer in which we are deploying P2MP MPLS >TE. Further, as we attempt to say in the P2MP OAM requirements draft >(and/or inherit from the P2P OAM requirements draft) the higher layer must >be careful not to react too precipitously to a fault which the lower layer >may be in the process of solving. > >With regard to "non-objectives". The non-objectives stated are NOT >non-objectives of the MPLS WG wrt to P2MP TE signaling. They are >non-objectives of *this* I-D. As the specific OAM subsection states, P2MP >OAM is discussed in a separate I-D. > >There are three reasons for this: >1. OAM is not really a signaling requirement. >2. It is sufficiently large and important that folding it into the >signaling requirements I-D would make the signaling requirements I-D >unwieldy. >3. P2MP OAM needs to apply more widely than just TE (e.g. to LDP >multicast) > >Cheers, >Adrian > >----- Original Message ----- >From: >To: >Cc: >Sent: Wednesday, July 06, 2005 11:32 AM >Subject: RE: [mpls] I-D ACTION:draft-ietf-mpls-p2mp-sig-requirement-03.txt > > >Seisho, > >I have a question on this draft: > >In section 1 there is the following stated requirement: >"A P2MP TE LSP will be protected by fast error recovery mechanisms to >minimize disconnection of a P2MP service." > >Which is obviously sensible, and of course implies that all the defect >cases of interest can be detected and the appropriate consequent actions >taken. Note this should include defects of this layer network and not >just defects that arise in lower layer networks. And remember....the >links between nodes in this layer network are provided by (p2p) trails >in a lower layer network....and this client/server relationship recurses >to the duct. The point I am making here is that IF the lower layer >network has decent OAM itself you should get some indication of failure >from this, but this is over/above any defects you detect in this layer >network either from (i) lower layer defects or (ii) defects arising in >this layer network (which of course cannot be detected at all in any >lower layer network). > > >Yet it says in section 1.1 that a 'non-objective' is: >"OAM for P2MP LSPs" > >Can someone please explain this apparent contradiction? > > >regards, Neil > >_______________________________________________ >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 Jul 07 09:01:42 2005 Received: from localhost.localdomain ([127.0.0.1] helo=megatron.ietf.org) by megatron.ietf.org with esmtp (Exim 4.32) id 1DqW0c-0008Cw-1a; Thu, 07 Jul 2005 09:01:42 -0400 Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org) by megatron.ietf.org with esmtp (Exim 4.32) id 1DqW0Z-0008BC-0q for mpls@megatron.ietf.org; Thu, 07 Jul 2005 09:01:39 -0400 Received: from ietf-mx.ietf.org (ietf-mx [132.151.6.1]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id JAA03192 for ; Thu, 7 Jul 2005 09:01:37 -0400 (EDT) Received: from tama5.ecl.ntt.co.jp ([129.60.39.102]) by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1DqWRj-00064D-9E for mpls@ietf.org; Thu, 07 Jul 2005 09:29:45 -0400 Received: from vcs3.rdh.ecl.ntt.co.jp (vcs3.rdh.ecl.ntt.co.jp [129.60.39.110]) by tama5.ecl.ntt.co.jp (8.12.11/8.12.11) with ESMTP id j67D1YS6011324 for ; Thu, 7 Jul 2005 22:01:34 +0900 (JST) Received: from vcs3.rdh.ecl.ntt.co.jp (localhost [127.0.0.1]) by vcs3.rdh.ecl.ntt.co.jp (8.12.11/8.12.11) with ESMTP id j67D1XZb026181 for ; Thu, 7 Jul 2005 22:01:34 +0900 (JST) Received: from mfs3.rdh.ecl.ntt.co.jp (mfs3.rdh.ecl.ntt.co.jp [129.60.39.112]) by vcs3.rdh.ecl.ntt.co.jp (8.12.11/8.12.11) with ESMTP id j67D1XoQ026178 for ; Thu, 7 Jul 2005 22:01:33 +0900 (JST) Received: from mfs3.rdh.ecl.ntt.co.jp (localhost [127.0.0.1]) by mfs3.rdh.ecl.ntt.co.jp (8.12.11/8.12.11) with ESMTP id j67D1XHJ028664 for ; Thu, 7 Jul 2005 22:01:33 +0900 (JST) Received: from nttmail3.ecl.ntt.co.jp ([129.60.39.100]) by mfs3.rdh.ecl.ntt.co.jp (8.12.11/8.12.11) with ESMTP id j67D1WGt028655 for ; Thu, 7 Jul 2005 22:01:32 +0900 (JST) Received: from eclscan3.m.ecl.ntt.co.jp (eclscan3.m.ecl.ntt.co.jp [129.60.5.69]) by nttmail3.ecl.ntt.co.jp (8.12.11/8.12.11) with ESMTP id j67D1WCk004381 for ; Thu, 7 Jul 2005 22:01:32 +0900 (JST) Received: from eclscan3.m.ecl.ntt.co.jp (localhost [127.0.0.1]) by eclscan3.m.ecl.ntt.co.jp (8.12.11/8.12.11) with ESMTP id j67D1WqA002114 for ; Thu, 7 Jul 2005 22:01:32 +0900 (JST) Received: from imc.m.ecl.ntt.co.jp (imc0.m.ecl.ntt.co.jp [129.60.5.141]) by eclscan3.m.ecl.ntt.co.jp (8.12.11/8.12.11) with ESMTP id j67D1Wwk002109; Thu, 7 Jul 2005 22:01:32 +0900 (JST) Received: from win-yasukawa.lab.ntt.co.jp by imc.m.ecl.ntt.co.jp (8.9.3p2/3.7W) with ESMTP id WAA15537; Thu, 7 Jul 2005 22:01:31 +0900 (JST) Message-Id: <5.0.2.5.2.20050707221337.0782d990@imc.m.ecl.ntt.co.jp> X-Sender: sy003@imc.m.ecl.ntt.co.jp X-Mailer: QUALCOMM Windows Eudora Version 5.0.2-J Date: Thu, 07 Jul 2005 22:18:26 +0900 To: From: Seisho Yasukawa Mime-Version: 1.0 Content-Type: text/plain; charset="us-ascii"; format=flowed X-Spam-Score: 0.0 (/) X-Scan-Signature: 0a7aa2e6e558383d84476dc338324fab Cc: Subject: [mpls] revised P2MP signaling requirement draft after wg last call 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 MPLS WG, I have updated the P2MP Signaling Requirements draft after WG last call comments. http://www.ietf.org/internet-drafts/draft-ietf-mpls-p2mp-sig-requirement-03.txt Thank you all who commented or contributed to the off-line discussions. The agreed changes can be seen in the emails exchanged on the MPLS mailing list. The highlight changes are as follows. Section 1 - Remove comment about how TED might be populated. - Add early exposure of discussion of rate of change of leaves. Section 2.2 - Some re-work of definitions - Note PID becomes P2ID Section 4.1 - Clarify different switching types. Section 4.3 - Explain "widely scoped abstract node" - Clarify that policy may prevent the ingress learning the full tree of the LSP Section 4.4 - Clarify optimality versus scalability Section 4.7 - Point out that route recording introduces scaling issues. - Remove reference to RSVP-TE Section 4.12 - Distinguish short-term packet duplication from long-term Section 4.14 - Re-write for clarity Section 4.15 - Remove solution-based hints Section 4.16 - Deleted entire section as out of scope. Section 4.17 [was 4.18] - Simplify and add reference to P2MP-OAM draft Section 4.19 [was 4.20] - Remove reference to CCAMP WG Section 4.22 - Deleted entire section as out of scope. Thank you, Seisho _______________________________________________ mpls mailing list mpls@lists.ietf.org https://www1.ietf.org/mailman/listinfo/mpls From mpls-bounces@lists.ietf.org Fri Jul 08 12:35:41 2005 Received: from localhost.localdomain ([127.0.0.1] helo=megatron.ietf.org) by megatron.ietf.org with esmtp (Exim 4.32) id 1DqvpF-0004Qu-Ab; Fri, 08 Jul 2005 12:35:41 -0400 Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org) by megatron.ietf.org with esmtp (Exim 4.32) id 1DqvpD-0004Qc-03 for mpls@megatron.ietf.org; Fri, 08 Jul 2005 12:35:39 -0400 Received: from ietf-mx.ietf.org (ietf-mx [132.151.6.1]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id MAA26358 for ; Fri, 8 Jul 2005 12:35:36 -0400 (EDT) Received: from mail126.messagelabs.com ([216.82.254.83]) by ietf-mx.ietf.org with smtp (Exim 4.43) id 1DqwGd-0004ZW-6O for mpls@ietf.org; Fri, 08 Jul 2005 13:03:59 -0400 X-VirusChecked: Checked X-Env-Sender: gash@att.com X-Msg-Ref: server-7.tower-126.messagelabs.com!1120840528!4874721!1 X-StarScan-Version: 5.4.15; banners=-,-,- X-Originating-IP: [192.128.134.71] Received: (qmail 11496 invoked from network); 8 Jul 2005 16:35:28 -0000 Received: from kcmso2.att.com (HELO kcmso2.proxy.att.com) (192.128.134.71) by server-7.tower-126.messagelabs.com with SMTP; 8 Jul 2005 16:35:28 -0000 Received: from attrh3i.attrh.att.com ([135.38.62.9]) by kcmso2.proxy.att.com (AT&T IPNS/MLO-6.0) with ESMTP id j68GZ8Tm031616 for ; Fri, 8 Jul 2005 11:35:27 -0500 Received: from kcclust06evs1.ugd.att.com (135.38.164.89) by attrh3i.attrh.att.com (7.2.052) id 42BED276002626D0 for mpls@ietf.org; Fri, 8 Jul 2005 12:35:27 -0400 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 Date: Fri, 8 Jul 2005 11:35:27 -0500 Message-ID: <9473683187ADC049A855ED2DA739ABCA09FA9032@KCCLUST06EVS1.ugd.att.com> Thread-Topic: I-D ACTION:draft-ash-avt-hc-over-mpls-protocol-01.txt Thread-Index: AcWD0YbHU77AD7LDTN2AdZ1EHqnoVgAAEz7AAAJK7pA= From: "Ash, Gerald R \(Jerry\), ALABS" To: X-Spam-Score: 0.0 (/) X-Scan-Signature: f66b12316365a3fe519e75911daf28a8 Content-Transfer-Encoding: quoted-printable Cc: Subject: [mpls] RE: I-D ACTION:draft-ash-avt-hc-over-mpls-protocol-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: , Sender: mpls-bounces@lists.ietf.org Errors-To: mpls-bounces@lists.ietf.org Hi All, Please review and comment on the (significantly) updated draft 'Protocol Extensions for Header Compression over MPLS' (http://www.ietf.org/internet-drafts/draft-ash-avt-hc-over-mpls-protocol -01.txt). Note that a work item and milestone were recently added to the AVT charter on this work: "- in collaboration with the MPLS and ROHC WGs, to develop a solution for header compression of RTP across MPLS networks that avoid decompression and compression at each MPLS node. ... Dec 05 Submit any extensions for RTP HC on MPLS networks for Proposed Standard"=20 The updated I-D responds to comments on the AVT list from Lars-Erik Jonsson and Colin Perkins: http://www1.ietf.org/mail-archive/web/avt/current/msg05408.html http://www1.ietf.org/mail-archive/web/avt/current/msg05419.html http://www1.ietf.org/mail-archive/web/avt/current/msg05428.html http://www1.ietf.org/mail-archive/web/avt/current/msg05433.html http://www1.ietf.org/mail-archive/web/avt/current/msg05530.html The main changes are as follows: 1. Lars-Erik's suggested outline is used, in particular: - Section 2 'Terminology' is added - Section 3 'Header Compression over MPLS Protocol Overview' is added - Section 4 'Protocol Specifications' is reorganized 2. Pseudowire (PW) setup and header compression session configuration are covered in Sections 3.1 and 4.1. In particular, the PW Interface Parameters Sub-TLV is used to signal header compression session setup and header compression parameter negotiation, such as described for header-compression-over-PPP mechanisms [RFC3241, RFC3544]. 3. Encapsulation of header compressed packets is covered in Sections 3.2 and 4.2. See in particular Figure 3 illustrating 'Header Compression over MPLS Media Stream Transport'. 4. A PW type has been assigned to each header compression scheme, as discussed in Section 4.1 and [IANA] (http://ietf.org/internet-drafts/draft-ietf-pwe3-iana-allocation-11.txt) . Once again, please review and comment on the updated draft. It will be good to have some discussion on the list in anticipation of proposing this as an AVT WG document at the IETF-63/AVT meeting. Thanks, Jerry -----Original Message----- From: i-d-announce-bounces@ietf.org [mailto:i-d-announce-bounces@ietf.org] On Behalf Of Internet-Drafts@ietf.org Sent: Friday, July 08, 2005 10:50 AM To: i-d-announce@ietf.org Subject: I-D ACTION:draft-ash-avt-hc-over-mpls-protocol-01.txt=20 A New Internet-Draft is available from the on-line Internet-Drafts directories. Title : Protocol Extensions for Header Compression over MPLS Author(s) : J. Ash, et al. Filename : draft-ash-avt-hc-over-mpls-protocol-01.txt Pages : 17 Date : 2005-7-8 =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), and the pseudowires define a point to point instance of each HC session at the header decompressor. Standard HC methods (e.g., ECRTP, ROHC, etc.) are re-used to determine the context. A URL for this Internet-Draft is: http://www.ietf.org/internet-drafts/draft-ash-avt-hc-over-mpls-protocol- 01.txt _______________________________________________ mpls mailing list mpls@lists.ietf.org https://www1.ietf.org/mailman/listinfo/mpls From mpls-bounces@lists.ietf.org Tue Jul 12 03:20:24 2005 Received: from localhost.localdomain ([127.0.0.1] helo=megatron.ietf.org) by megatron.ietf.org with esmtp (Exim 4.32) id 1DsF44-0002r9-D8; Tue, 12 Jul 2005 03:20:24 -0400 Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org) by megatron.ietf.org with esmtp (Exim 4.32) id 1DsF42-0002oo-6F for mpls@megatron.ietf.org; Tue, 12 Jul 2005 03:20:22 -0400 Received: from ietf-mx.ietf.org (ietf-mx [132.151.6.1]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id DAA26038 for ; Tue, 12 Jul 2005 03:20:20 -0400 (EDT) Received: from p-mail1.rd.francetelecom.com ([195.101.245.15]) by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1DsFW9-0006z8-JA for mpls@ietf.org; Tue, 12 Jul 2005 03:49:28 -0400 Received: from ftrdmel1.rd.francetelecom.fr ([10.193.117.152]) by ftrdsmtp2.rd.francetelecom.fr with Microsoft SMTPSVC(6.0.3790.211); Tue, 12 Jul 2005 09:20:17 +0200 X-MimeOLE: Produced By Microsoft Exchange V6.5.7226.0 Content-class: urn:content-classes:message MIME-Version: 1.0 Date: Tue, 12 Jul 2005 09:20:14 +0200 Message-ID: Thread-Topic: I-D ACTION:draft-leroux-mpls-mp-ldp-reqs-00.txt Thread-Index: AcWGq+AdScnmdHJ4TQiJmJFlywdjEQAAA52w From: "LE ROUX Jean-Louis RD-CORE-LAN" To: X-OriginalArrivalTime: 12 Jul 2005 07:20:17.0148 (UTC) FILETIME=[274B63C0:01C586B2] X-Spam-Score: 0.6 (/) X-Scan-Signature: 6437e26f1586b9f35812ea5ebeedf4ad Cc: Subject: [mpls] TR : I-D ACTION:draft-leroux-mpls-mp-ldp-reqs-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="===============0840771061==" Sender: mpls-bounces@lists.ietf.org Errors-To: mpls-bounces@lists.ietf.org This is a multi-part message in MIME format. --===============0840771061== Content-class: urn:content-classes:message Content-Type: multipart/alternative; boundary="----_=_NextPart_001_01C586B2.2741C5B9" This is a multi-part message in MIME format. ------_=_NextPart_001_01C586B2.2741C5B9 Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: quoted-printable Hi all, This new draft lists a set of requirements for multipoint extensions to LDP Your comments on this draft would be appreciated Best Regards, JL > A New Internet-Draft is available from the on-line Internet-Drafts > directories. >=20 >=20 > Title : Requirements for multipoint extensions to the > Label Distribution Protocol=20 > Author(s) : J. Le Roux, et al. > Filename : draft-leroux-mpls-mp-ldp-reqs-00.txt > Pages : 15 > Date : 2005-7-11 > =09 > This document lists a set of functional requirements for Label=20 > Distribution Protocol (LDP) extensions for setting up point-to- > multipoint (P2MP) and potentially multipoint-to-multipoint (MP2MP)=20 > Label Switched Paths (LSP), in order to deliver point-to-multipoint >=20 > applications over a Multi Protocol Label Switching (MPLS)=20 > infrastructure. It is intended that solutions that specify LDP=20 > procedures for setting up P2MP and MP2MP LSP satisfy these=20 > requirements.=20 >=20 > A URL for this Internet-Draft is: > http://www.ietf.org/internet-drafts/draft-leroux-mpls-mp-ldp-reqs-00.t > xt >=20 > 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. >=20 >=20 > 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-00.txt". >=20 > 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 >=20 >=20 > Internet-Drafts can also be obtained by e-mail. >=20 > Send a message to: > mailserv at ietf.org. > In the body type: > "FILE /internet-drafts/draft-leroux-mpls-mp-ldp-reqs-00.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. > xt> > xt> =20 > _______________________________________________ > I-D-Announce mailing list > I-D-Announce at ietf.org > https://www1.ietf.org/mailman/listinfo/i-d-announce >=20 ------_=_NextPart_001_01C586B2.2741C5B9 Content-Type: text/html; charset="us-ascii" Content-Transfer-Encoding: quoted-printable TR : I-D ACTION:draft-leroux-mpls-mp-ldp-reqs-00.txt

Hi all,

This new draft lists = a set of requirements for multipoint extensions to LDP

Your comments on this = draft would be appreciated

Best Regards,

JL



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


        Title   =         : Requirements for multipoint = extensions to the
           &n= bsp;           &nb= sp;  Label Distribution Protocol
        Author(s)       : J. = Le Roux, et al.
        Filename        = : draft-leroux-mpls-mp-ldp-reqs-00.txt
        Pages   =         : 15
        Date    =         : 2005-7-11
       =20
   This document lists = a set of functional requirements for Label
   Distribution = Protocol (LDP) extensions for setting up point-to-
   multipoint (P2MP) = and potentially multipoint-to-multipoint (MP2MP)
   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 and MP2MP LSP satisfy these
   requirements. =

A URL for this Internet-Draft = is:
http://www.ietf.org/internet-drafts/draft-leroux-mpls-mp-ldp-reqs-00= .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-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 at ietf.org.
In the body type:
        "FILE = /internet-drafts/draft-leroux-mpls-mp-ldp-reqs-00.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-00.txt>
_______________________________________________
I-D-Announce mailing list
I-D-Announce at ietf.org
https://www1.ietf.org/mailman/listinfo/i-d-announce

------_=_NextPart_001_01C586B2.2741C5B9-- --===============0840771061== 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 --===============0840771061==-- From mpls-bounces@lists.ietf.org Tue Jul 12 04:50:43 2005 Received: from localhost.localdomain ([127.0.0.1] helo=megatron.ietf.org) by megatron.ietf.org with esmtp (Exim 4.32) id 1DsGTT-0004RT-4s; Tue, 12 Jul 2005 04:50:43 -0400 Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org) by megatron.ietf.org with esmtp (Exim 4.32) id 1DsGTR-0004RO-RE for mpls@megatron.ietf.org; Tue, 12 Jul 2005 04:50:41 -0400 Received: from ietf-mx.ietf.org (ietf-mx [132.151.6.1]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id EAA01974 for ; Tue, 12 Jul 2005 04:50:40 -0400 (EDT) Received: from p-mail1.rd.francetelecom.com ([195.101.245.15]) by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1DsGvc-0002AA-FO for mpls@ietf.org; Tue, 12 Jul 2005 05:19:48 -0400 Received: from ftrdmel3.rd.francetelecom.fr ([10.193.117.155]) by ftrdsmtp1.rd.francetelecom.fr with Microsoft SMTPSVC(6.0.3790.211); Tue, 12 Jul 2005 10:50:38 +0200 Content-class: urn:content-classes:message MIME-Version: 1.0 Content-Type: multipart/mixed; boundary="----_=_NextPart_001_01C586BE.C6B0C968" X-MimeOLE: Produced By Microsoft Exchange V6.5.7226.0 Date: Tue, 12 Jul 2005 10:50:37 +0200 Message-ID: <5A0FF108221C7C4E85738678804B567C022BB158@ftrdmel3.rd.francetelecom.fr> X-MS-Has-Attach: yes Thread-Topic: I-D ACTION:draft-decraene-mpls-ldp-interarea-00.txt Thread-Index: AcWGVLx4MbfYk7cqS9y/zCulGd+4OwAaUP8A From: "DECRAENE Bruno RD-CORE-ISS" To: X-OriginalArrivalTime: 12 Jul 2005 08:50:38.0771 (UTC) FILETIME=[C6D56830:01C586BE] X-Spam-Score: 0.0 (/) X-Scan-Signature: 9a2be21919e71dc6faef12b370c4ecf5 Cc: LE ROUX Jean-Louis RD-CORE-LAN Subject: [mpls] FW: I-D ACTION:draft-decraene-mpls-ldp-interarea-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 This is a multi-part message in MIME format. ------_=_NextPart_001_01C586BE.C6B0C968 Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: quoted-printable Hi all,=20 This new draft proposes an LDP extension to ease the establishment of inter-area LSP and allows IP agregation on area border routers. Your comments on this draft would be appreciated. Best Regards,=20 Jean-Louis, Bruno =20 -----Original Message----- From: i-d-announce-bounces@ietf.org [mailto:i-d-announce-bounces@ietf.org] On Behalf Of Internet-Drafts@ietf.org Sent: Monday, July 11, 2005 9:50 PM To: i-d-announce@ietf.org Subject: I-D ACTION:draft-decraene-mpls-ldp-interarea-00.txt=20 A New Internet-Draft is available from the on-line Internet-Drafts directories. Title : LDP extensions for Inter-Area LSP=20 Author(s) : B. Decraene, J. Le Roux Filename : draft-decraene-mpls-ldp-interarea-00.txt Pages : 8 Date : 2005-7-11 =09 To facilitate the establishment of Label Switched Paths (LSP) that=20 would span multiple IGP areas in a given autonomous system, this=20 document proposes a new optional label mapping procedure for the=20 Label Distribution Protocol (LDP).=20 =20 This procedure allows the use of a label if the Forwarding=20 Equivalence Class (FEC) Element matches an entry in the routing table (RIB). Matching is defined by an IP longest match search and does not mandate an exact match.=20 A URL for this Internet-Draft is: http://www.ietf.org/internet-drafts/draft-decraene-mpls-ldp-interarea-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. =20 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-decraene-mpls-ldp-interarea-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-decraene-mpls-ldp-interarea-00.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. ------_=_NextPart_001_01C586BE.C6B0C968 Content-Type: application/octet-stream; name="draft-decraene-mpls-ldp-interarea-00.URL" Content-Description: draft-decraene-mpls-ldp-interarea-00.URL Content-Disposition: attachment; filename="draft-decraene-mpls-ldp-interarea-00.URL" Content-Transfer-Encoding: base64 W0ludGVybmV0U2hvcnRjdXRdDQpVUkw9ZnRwOi8vZnRwLmlldGYub3JnL2ludGVybmV0LWRyYWZ0 cy9kcmFmdC1kZWNyYWVuZS1tcGxzLWxkcC1pbnRlcmFyZWEtMDAudHh0DQo= ------_=_NextPart_001_01C586BE.C6B0C968 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_001_01C586BE.C6B0C968-- From mpls-bounces@lists.ietf.org Thu Jul 14 03:58:42 2005 Received: from localhost.localdomain ([127.0.0.1] helo=megatron.ietf.org) by megatron.ietf.org with esmtp (Exim 4.32) id 1DsycE-0001Gz-Gv; Thu, 14 Jul 2005 03:58:42 -0400 Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org) by megatron.ietf.org with esmtp (Exim 4.32) id 1DsycB-0001Gu-LZ for mpls@megatron.ietf.org; Thu, 14 Jul 2005 03:58:39 -0400 Received: from ietf-mx.ietf.org (ietf-mx [132.151.6.1]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id DAA14917 for ; Thu, 14 Jul 2005 03:58:38 -0400 (EDT) Received: from [80.86.78.228] (helo=smtp.testbed.se) by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1Dsz4k-0005K0-8F for mpls@ietf.org; Thu, 14 Jul 2005 04:28:11 -0400 Received: from gw.imc.kth.se ([193.10.152.67] helo=[172.16.2.208]) by fw.testbed.se with esmtpsa (TLSv1:RC4-MD5:128) (Exim 4.43) id 1Dsyby-0000hx-38 for mpls@ietf.org; Thu, 14 Jul 2005 09:58:28 +0200 Message-ID: <42D61AA1.2030003@pi.se> Date: Thu, 14 Jul 2005 09:56:17 +0200 From: Loa Andersson Organization: Acreo AB User-Agent: Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US; rv:1.7.7) Gecko/20050414 X-Accept-Language: en-us, en MIME-Version: 1.0 To: mpls@ietf.org Content-Type: text/plain; charset=us-ascii; format=flowed Content-Transfer-Encoding: 7bit X-Spam-Score: 0.0 (/) X-Spam-Score: 0.0 (/) X-Scan-Signature: cf4fa59384e76e63313391b70cd0dd25 Content-Transfer-Encoding: 7bit Cc: Subject: [mpls] implementation status for draft-ietf-mpls-nodeid-subobject-04.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 Folks, the draft-ietf-mpls-nodeid-subobject-04.txt has gone into IETF Last Call, we need reports on implementation status for this ID. Send to wg chairs or the mailing list. /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 Fri Jul 15 01:38:35 2005 Received: from localhost.localdomain ([127.0.0.1] helo=megatron.ietf.org) by megatron.ietf.org with esmtp (Exim 4.32) id 1DtIuB-00009a-2p; Fri, 15 Jul 2005 01:38:35 -0400 Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org) by megatron.ietf.org with esmtp (Exim 4.32) id 1DtIu7-000094-QJ for mpls@megatron.ietf.org; Fri, 15 Jul 2005 01:38:31 -0400 Received: from somnath.ghen.net (somnath.ghen.net [206.251.242.139]) by ietf.org (8.9.1a/8.9.1a) with SMTP id BAA11389 for ; Fri, 15 Jul 2005 01:38:25 -0400 (EDT) Received: (qmail 15693 invoked by uid 48); 15 Jul 2005 05:38:25 -0000 Message-ID: <20050715053825.15692.qmail@somnath.ghen.net> Date: Thu, 14 Jul 2005 22:38:25 -0700 From: "navaneeeth kumar d" To: mpls@ietf.org Content-Type: text/plain; charset="US-ASCII" Content-Transfer-Encoding: quoted-printable Mime-Version: 1.0 X-Gmail-Account: navaneeth@vidyapatha.com X-Originating-Ip: 202.83.61.116 Content-Transfer-Encoding: quoted-printable Cc: Subject: [mpls] need mails about mpls 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 -- This email was brought to you by Vidyapatha Mail http://vidyapatha.com/ _______________________________________________ mpls mailing list mpls@lists.ietf.org https://www1.ietf.org/mailman/listinfo/mpls From mpls-bounces@lists.ietf.org Fri Jul 15 07:31:28 2005 Received: from localhost.localdomain ([127.0.0.1] helo=megatron.ietf.org) by megatron.ietf.org with esmtp (Exim 4.32) id 1DtOPg-0001cY-If; Fri, 15 Jul 2005 07:31:28 -0400 Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org) by megatron.ietf.org with esmtp (Exim 4.32) id 1DtOPe-0001cP-J0 for mpls@megatron.ietf.org; Fri, 15 Jul 2005 07:31:26 -0400 Received: from ietf-mx.ietf.org (ietf-mx [132.151.6.1]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id HAA26418 for ; Fri, 15 Jul 2005 07:31:25 -0400 (EDT) Received: from relay2.mail.uk.clara.net ([80.168.70.142]) by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1DtOsR-0004n7-JY for mpls@ietf.org; Fri, 15 Jul 2005 08:01:12 -0400 Received: from du-069-0111.access.clara.net ([217.158.132.111] helo=Puppy) by relay2.mail.uk.clara.net with smtp (Exim 4.50) id 1DtOPS-000CKs-7Z; Fri, 15 Jul 2005 12:31:15 +0100 Message-ID: <080e01c58931$0d210dc0$d6849ed9@Puppy> From: "Adrian Farrel" To: , References: <42D6FAB3.9050804@kddilabs.jp> Date: Fri, 15 Jul 2005 12:29:51 +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.1158 X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2800.1165 X-Spam-Score: 0.1 (/) X-Scan-Signature: f4c2cf0bccc868e4cc88dace71fb3f44 Content-Transfer-Encoding: 7bit Cc: Subject: [mpls] Re: GMPLS OSPF-TE MIB 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 Cross-posting to the OSPF and MPLS mailing lists. Folk in CCAMP are starting to look at what MIB extensions are needed to handle TE and GMPLS extensions to OSPF. This work is at a very early stage. We anticipate that this work will require significant review in the OSPF, MPLS and CCAMP working groups. For the moment it would be helpful to concentrate discussions on one mailing list. Let's make that CCAMP for now. Thanks, Adrian ----- Original Message ----- From: "Tomohiro Otani" To: Sent: Friday, July 15, 2005 12:52 AM Subject: GMPLS OSPF-TE MIB > Hi everyone, > > We posted a new draft about GMPLS OSPF-TE MIB as follows. > http://www.ietf.org/internet-drafts/draft-otani-ccamp-gmpls-ospf-mib-00.txt > > We welcome your comments and feedbacks, pls. > And please make a comment whether this is within ccamp WG or not (OSPF-WG?). > > We believe that this is a very significant definition of OSPF-TE MIB, > being complementary to other GMPLS related MIBs (TE/LSR/LMP mibs) in order > to deploy GMPLS control plane in the actual environment with simple but > reliable network management. > > With best regards, > > tomo > > ------------------------------------ > Tomohiro Otani > KDDI R&D Laboratories, Inc. > Optical network architecture lab. > 2-1-15 Ohara Kamifukuoka Saitama, 356-8502, Japan > TEL: +81-49-278-7357 > FAX: +81-49-278-7811 > E-mail: otani@kddilabs.jp > ------------------------------------ > > > > > _______________________________________________ mpls mailing list mpls@lists.ietf.org https://www1.ietf.org/mailman/listinfo/mpls From mpls-bounces@lists.ietf.org Fri Jul 15 07:35:42 2005 Received: from localhost.localdomain ([127.0.0.1] helo=megatron.ietf.org) by megatron.ietf.org with esmtp (Exim 4.32) id 1DtOTm-0003wG-Ij; Fri, 15 Jul 2005 07:35:42 -0400 Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org) by megatron.ietf.org with esmtp (Exim 4.32) id 1Dt7Cp-0006DK-7x for mpls@megatron.ietf.org; Thu, 14 Jul 2005 13:09:03 -0400 Received: from newodin.ietf.org (newodin.ietf.org [10.27.6.50]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id NAA29644 for ; Thu, 14 Jul 2005 13:09:00 -0400 (EDT) Received: from apache by newodin.ietf.org with local (Exim 4.43) id 1Dt7Co-0002b5-Lr; Thu, 14 Jul 2005 13:09:02 -0400 X-test-idtracker: no To: IETF-Announce From: The IESG Message-Id: Date: Thu, 14 Jul 2005 13:09:02 -0400 X-Mailman-Approved-At: Fri, 15 Jul 2005 07:35:41 -0400 Cc: mpls@ietf.org Subject: [mpls] Last Call: 'Definition of an RRO node-id subobject' to Proposed 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 document: - 'Definition of an RRO node-id subobject ' as a Proposed Standard 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 2005-07-28. The file can be obtained via http://www.ietf.org/internet-drafts/draft-ietf-mpls-nodeid-subobject-06.txt _______________________________________________ mpls mailing list mpls@lists.ietf.org https://www1.ietf.org/mailman/listinfo/mpls From mpls-bounces@lists.ietf.org Fri Jul 15 09:11:14 2005 Received: from localhost.localdomain ([127.0.0.1] helo=megatron.ietf.org) by megatron.ietf.org with esmtp (Exim 4.32) id 1DtPyE-0000nS-25; Fri, 15 Jul 2005 09:11:14 -0400 Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org) by megatron.ietf.org with esmtp (Exim 4.32) id 1DtPyB-0000nK-BK for mpls@megatron.ietf.org; Fri, 15 Jul 2005 09:11:11 -0400 Received: from ietf-mx.ietf.org (ietf-mx [132.151.6.1]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id JAA02745 for ; Fri, 15 Jul 2005 09:11:08 -0400 (EDT) Received: from mail.riverstonenet.com ([63.113.148.10] helo=riverstonenet.com) by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1DtQQw-000847-9R for mpls@ietf.org; Fri, 15 Jul 2005 09:40:57 -0400 Received: from gondor.rs.riverstonenet.com by riverstonenet.com (8.9.3+Sun/SMI-SVR4-Yago) id GAA27836; Fri, 15 Jul 2005 06:10:42 -0700 (PDT) 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] Last Call: 'Definition of an RRO node-id subobject' to Proposed Standard Date: Fri, 15 Jul 2005 18:40:40 +0530 Message-ID: Thread-Topic: [mpls] Last Call: 'Definition of an RRO node-id subobject' to Proposed Standard Thread-Index: AcWJMWyxTSGJgRZeS4O4zBrkDpSLfAAC3i0g From: "Balaji, Hemanth" To: X-Spam-Score: 0.0 (/) X-Scan-Signature: 082a9cbf4d599f360ac7f815372a6a15 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, I have a small doubt. ( may be related to the following draft or just related to RRO ) " http://www.ietf.org/internet-drafts/draft-ietf-mpls-nodeid-subobject-06. txt" The doubt might sound basic but it would be helpful if the authors or anyone else could clarify it. My Question is this, Since we are talking about Inter-area or Inter-AS TE LSPs, what will be the Behavior in case of duplication of Node-ids. i.e Since the scope of router/node id is within the AS, the same router-id could exist in another AS. Though this can always be prevented by being careful with our configurations. I just wanted to know what will happen if the RRO encounters the same node/router ID(in different ASs) along its path. Since the router-id is appearing for a second time in the path, that node will not be added to the RRO presuming that a loop would be formed. But in this case, it is not so. So what would be the behavior? Thanks, Hemanth. -----Original Message----- From: mpls-bounces@lists.ietf.org [mailto:mpls-bounces@lists.ietf.org] On Behalf Of The IESG Sent: Thursday, July 14, 2005 10:39 PM To: IETF-Announce Cc: mpls@ietf.org Subject: [mpls] Last Call: 'Definition of an RRO node-id subobject' to Proposed Standard=20 The IESG has received a request from the Multiprotocol Label Switching WG to=20 consider the following document: - 'Definition of an RRO node-id subobject ' as a Proposed Standard 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 2005-07-28. The file can be obtained via http://www.ietf.org/internet-drafts/draft-ietf-mpls-nodeid-subobject-06. txt _______________________________________________ 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 Jul 15 10:23:36 2005 Received: from localhost.localdomain ([127.0.0.1] helo=megatron.ietf.org) by megatron.ietf.org with esmtp (Exim 4.32) id 1DtR6G-0002y9-H8; Fri, 15 Jul 2005 10:23:36 -0400 Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org) by megatron.ietf.org with esmtp (Exim 4.32) id 1DtR6E-0002xv-KR for mpls@megatron.ietf.org; Fri, 15 Jul 2005 10:23:34 -0400 Received: from ietf-mx.ietf.org (ietf-mx [132.151.6.1]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id KAA09607 for ; Fri, 15 Jul 2005 10:23:32 -0400 (EDT) Received: from ausfe02.broadwing.com ([216.140.58.196]) by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1DtRZ1-00027V-6m for mpls@ietf.org; Fri, 15 Jul 2005 10:53:22 -0400 Received: from ausex02.BRW.Corvis.com ([172.16.229.21]) by ausfe02.broadwing.com with Microsoft SMTPSVC(5.0.2195.6713); Fri, 15 Jul 2005 09:23:20 -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.0.6603.0 Subject: RE: [mpls] need data about mpls Date: Fri, 15 Jul 2005 09:23:19 -0500 Message-ID: Thread-Topic: [mpls] need data about mpls Thread-Index: AcWJR88WxGEyqdm3Qz6HPKP75f/XfwAAIoJA From: "Bilbo, Matt" To: "navaneeth kumar d" , X-OriginalArrivalTime: 15 Jul 2005 14:23:20.0003 (UTC) FILETIME=[BFE4F130:01C58948] X-Spam-Score: 0.7 (/) 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 =20 While your responding can you also provide the following: - the formula for turning lead to gold - the process for converting sea water to gasoline - the working design for cold fusion Thanks! -----Original Message----- From: mpls-bounces@lists.ietf.org [mailto:mpls-bounces@lists.ietf.org] On Behalf Of navaneeth kumar d Sent: Friday, July 15, 2005 9:13 AM To: mpls@ietf.org Subject: [mpls] need data about mpls greetings, need all architectural information about mpls technology starting from its origin _________________________________________________________________ Top-of-the-line jobs!.=20 http://creative.mediaturf.net/creatives/timesjobs/hotmail_TOL.htm Log on to www.timesjobs.com and apply TODAY! _______________________________________________ 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 Jul 15 16:18:03 2005 Received: from localhost.localdomain ([127.0.0.1] helo=megatron.ietf.org) by megatron.ietf.org with esmtp (Exim 4.32) id 1DtWdH-0005xS-Ay; Fri, 15 Jul 2005 16:18:03 -0400 Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org) by megatron.ietf.org with esmtp (Exim 4.32) id 1DtWdD-0005wM-Ro for mpls@megatron.ietf.org; Fri, 15 Jul 2005 16:18:01 -0400 Received: from ietf-mx.ietf.org (ietf-mx [132.151.6.1]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id QAA21472 for ; Fri, 15 Jul 2005 16:17:56 -0400 (EDT) Received: from sj-iport-5.cisco.com ([171.68.10.87]) by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1DtX62-0003GM-T5 for mpls@ietf.org; Fri, 15 Jul 2005 16:47:49 -0400 Received: from sj-core-3.cisco.com (171.68.223.137) by sj-iport-5.cisco.com with ESMTP; 15 Jul 2005 13:17:40 -0700 X-IronPort-AV: i="3.93,293,1115017200"; d="scan'208"; a="198589657:sNHT25832896" Received: from [171.71.207.132] (dhcp-171-71-207-132.cisco.com [171.71.207.132]) by sj-core-3.cisco.com (8.12.10/8.12.6) with ESMTP id j6FKHb6p014646; Fri, 15 Jul 2005 13:17:38 -0700 (PDT) Message-ID: <42D819DC.6010008@hotpop.com> Date: Fri, 15 Jul 2005 13:17:32 -0700 From: Syed Junaid Farooqi User-Agent: Mozilla Thunderbird 1.0.2 (Windows/20050317) X-Accept-Language: en-us, en MIME-Version: 1.0 To: "Bilbo, Matt" Subject: Re: [mpls] need data about mpls References: In-Reply-To: Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit X-Spam-Score: 0.7 (/) X-Scan-Signature: 538aad3a3c4f01d8b6a6477ca4248793 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 Matt ..... ;o) Navneeth --------------:o) Check out books on amazon u got a lot of em there and RFC 3031 to start with Ciao Bilbo, Matt wrote: > >While your responding can you also provide the following: >- the formula for turning lead to gold >- the process for converting sea water to gasoline >- the working design for cold fusion > >Thanks! > > > >-----Original Message----- >From: mpls-bounces@lists.ietf.org [mailto:mpls-bounces@lists.ietf.org] >On Behalf Of navaneeth kumar d >Sent: Friday, July 15, 2005 9:13 AM >To: mpls@ietf.org >Subject: [mpls] need data about mpls > >greetings, > > need all architectural information about mpls technology >starting from its origin > >_________________________________________________________________ >Top-of-the-line jobs!. >http://creative.mediaturf.net/creatives/timesjobs/hotmail_TOL.htm Log on >to www.timesjobs.com and apply TODAY! > > >_______________________________________________ >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 Sat Jul 16 06:55:36 2005 Received: from localhost.localdomain ([127.0.0.1] helo=megatron.ietf.org) by megatron.ietf.org with esmtp (Exim 4.32) id 1DtkKV-0007Pg-Sq; Sat, 16 Jul 2005 06:55:35 -0400 Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org) by megatron.ietf.org with esmtp (Exim 4.32) id 1DtkKT-0007PT-To; Sat, 16 Jul 2005 06:55:33 -0400 Received: from ietf-mx.ietf.org (ietf-mx [132.151.6.1]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id GAA07711; Sat, 16 Jul 2005 06:55:31 -0400 (EDT) Received: from relay3.mail.uk.clara.net ([80.168.70.143]) by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1DtknT-0002lW-Ta; Sat, 16 Jul 2005 07:25:32 -0400 Received: from du-069-0104.access.clara.net ([217.158.132.104] helo=Puppy) by relay3.mail.uk.clara.net with smtp (Exim 4.46) id 1DtkKI-000LrP-FP; Sat, 16 Jul 2005 11:55:25 +0100 Message-ID: <09bf01c589f5$366be280$d6849ed9@Puppy> From: "Adrian Farrel" To: References: Date: Sat, 16 Jul 2005 11:52:45 +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.1158 X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2800.1165 X-Spam-Score: 0.1 (/) X-Scan-Signature: 827a2a57ca7ab0837847220f447e8d56 Content-Transfer-Encoding: 7bit Cc: mpls@ietf.org Subject: [mpls] Re: Last Call: 'Definition of an RRO node-id subobject' to Proposed Standard 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, I know that the RFC editor will reformat, etc., but I do feel that I-Ds should be presentable when they come up for last call. It would make the review process so much easier. This document needs significant editorial work before it can be progressed. Section 1 Bypass Tunnel defined but not used. Please delete or indicate that this a synonym for "backup tunnel". CSPF defined but not used. Please delete. You feel it necessary to define ASBR, but not ABR. Odd. LER defined but not used. LSDB defined but not used. PCC and PCE. PCC is not used at all. PCE gets a single reference. While I love PCE dearly, I think this reference is not helpful because: - it is not in the section stated - it is given without any explanation - there are no wider references in the references sections - the use of PCE is not fundamental to the document. I suggest removing PCC and PCE completely. Where Section 1 definitions in this document are copied from RFC4090, would it not be better to refer the reader to RCF4090 instead? The definition of MP could usefully be revised to read MP: Merge Point. The LSR where detour or backup tunnels meet the protected LSP. A MP may also be a PLR for a different backup tunnel. - No need to talk about one-to-one since this document doesn't deal in detours - An MP cannot be a PLR for the same backup tunnel! The definition of PLR should be revised as PLR: Point of Local Repair. The head-end of a backup tunnel. - No need to talk about detours since this document doesn't deal in one-to-one backup. The first paragraph of section 2 states that in FRR the protected LSPs are rerouted "in tens of msecs". I am not sure of the value of this marketing statement. The earth goes around the Sun in tens of msecs - a lot of tens. OTOH, the speed of rerouting is an implementation issue. Since RFC4090 defines FRR and since the mechanism is accepted and deployed, we do not need the sales blurb. Section 2 states that the PLR "should be" at the head end of the backup tunnel and that the MP "should be" at the tail end of the backup tunnel. Don't you mean "is" in both cases? Section 2 rather casually states that the inter-area technique just described can also be applied to inter-AS. As Hemanth just asked on the MPLS list, what happens when ASs use overlapping address spaces? Also, what happens when ASs apply confidentiality at the AS border? Step 1 in section 2 is confused/confusing > 1. The backup tunnel intersects with the primary tunnel at the MP > (and thus has a valid MP address). For the sake of illustration, > in Figure 1, R1 needs to determine that T1 and B1 share the same > MP node R2. This should be rephrased in line with the definition of MP. I.e. you can't "share an MP". You select an MP. What does "has a valid MP address" mean? How could an MP have an invalid address? In step 2 in section 2, what is meant by "(preferably, protecting against a node failure versus a link failure)". The PLR may prefer node protection to link protection, but it has no choice. Are you attempting to make a statement about the protection type that the ingress should request? The subsequent paragraph is odd. > A PLR can make sure that condition (1) is met by examining the Record > Route Object (RRO) of the primary tunnel to see if any of the addresses > specified in the RRO is attached to the tail-end of the backup tunnel. The implication here is that you have built a backup tunnel "at random" and you are now seeing if it is any use to protect your primary LSP. If it is the case that you are choosing between a set of existing backup tunnels to see which is suitable, then please make this far clearer. If, on the other hand, the backup tunnel is signaled to satisfy the requirements of the primary LSP (as you have previously indicated) then clearly the process described here is broken. My feeling is that your current text may reflect a deployment model where bypass tunnels are manually configured and selected as needed. I suspect you need both steps. First see if any existing bypass tunnel is suitable. Then set up a new bypass tunnel dynamically. Why are there two section 2s? In the second section 2, you should point out that legacy LSRs that do not support setting the new 0x20 bit may still supply sufficient information for the purpose. That is, they may still supply an RRO subobject of type IPv4 or IPv6 containing the TE Router ID of the LSR and this can be used to determine the MP. In this respect, the use of the 0x20 bit is a minor optimization that helps the PLR parse the RRO rapidly. In the second section 2... >Node-id: 0x20 > When set, this indicates that the address specified in the > RRO's IPv4 or IPv6 subobject is a node-id address, which refers > to the "Router Address" as defined in [OSPF-TE], or "Traffic > Engineering Router ID" as defined in [ISIS-TE]. A node MUST use > the same address consistently. Once an address is used in RRO's > IPv4 or IPv6 subobject, it should always be used for the > lifetime of the LSP. s/should/SHOULD/ Section 4 Since you are dealing with protocol extensions that cross AS boundaries, you are necessarily introducing new security/confidentiality issues. At the very least you need to discuss the fact that ASBRs might normally choose to strip (or aggregate) the RRO at the ASBR. You have introduced a requirement that modifies this behavior. You also need to point out the significant security issue of mis-selection of a bypass tunnel since this may lead to mis-connection and mis-delivery. (Of course, this item should have been in the security section of RFC 4090, but it isn't.) Arguably, this issue is considerably more important in inter-domain networks. Section 5 I don't believe that IANA currently manages this name space. If you require IANA to create a new name space you will need to explain it and define the circumstances under which assignments can be made. Section 8.1 RFCs 3667 and 3668 have been obsoleted. Thanks, Adrian ----- Original Message ----- From: "The IESG" To: "IETF-Announce" Cc: Sent: Thursday, July 14, 2005 6:09 PM Subject: Last Call: 'Definition of an RRO node-id subobject' to Proposed Standard > The IESG has received a request from the Multiprotocol Label Switching WG to > consider the following document: > > - 'Definition of an RRO node-id subobject ' > as a Proposed Standard > > 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 2005-07-28. > > The file can be obtained via > http://www.ietf.org/internet-drafts/draft-ietf-mpls-nodeid-subobject-06.txt > > > _______________________________________________ > IETF-Announce mailing list > IETF-Announce@ietf.org > https://www1.ietf.org/mailman/listinfo/ietf-announce > > _______________________________________________ mpls mailing list mpls@lists.ietf.org https://www1.ietf.org/mailman/listinfo/mpls From mpls-bounces@lists.ietf.org Mon Jul 18 04:43:03 2005 Received: from localhost.localdomain ([127.0.0.1] helo=megatron.ietf.org) by megatron.ietf.org with esmtp (Exim 4.32) id 1DuRDL-0008L9-3R; Mon, 18 Jul 2005 04:43:03 -0400 Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org) by megatron.ietf.org with esmtp (Exim 4.32) id 1DuRDJ-0008L1-RE for mpls@megatron.ietf.org; Mon, 18 Jul 2005 04:43:01 -0400 Received: from ietf-mx.ietf.org (ietf-mx [132.151.6.1]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id EAA22836 for ; Mon, 18 Jul 2005 04:42:59 -0400 (EDT) Received: from oberon.imc.kth.se ([193.10.152.20]) by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1DuRgg-0006WF-4S for mpls@ietf.org; Mon, 18 Jul 2005 05:13:24 -0400 Received: from mail1.imc.kth.se (mail1.imc.kth.se [193.10.152.140]) by oberon.imc.kth.se (8.11.6/8.11.6) with ESMTP id j6I8YWU30753 for ; Mon, 18 Jul 2005 10:34:32 +0200 Received: from [127.0.0.1] ([172.16.2.208]) by mail1.imc.kth.se; Mon, 18 Jul 2005 10:40:20 +0200 Message-ID: <42DB6AF3.1040206@pi.se> Date: Mon, 18 Jul 2005 10:40:19 +0200 From: Loa Andersson Organization: Acreo AB User-Agent: Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US; rv:1.7.7) Gecko/20050414 X-Accept-Language: en-us, en MIME-Version: 1.0 To: Seisho Yasukawa References: <5.0.2.5.2.20050707221337.0782d990@imc.m.ecl.ntt.co.jp> In-Reply-To: <5.0.2.5.2.20050707221337.0782d990@imc.m.ecl.ntt.co.jp> Content-Type: text/plain; charset=us-ascii; format=flowed Content-Transfer-Encoding: 7bit X-Spam-Score: 0.0 (/) X-Scan-Signature: b5d20af10c334b36874c0264b10f59f1 Content-Transfer-Encoding: 7bit Cc: mpls@ietf.org Subject: [mpls] short wg last call on draft-ietf-mpls-p2mp-sig-requirement-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 Seisho, thanks for taking care of the comments! Working group, this is to initiate a short wg last call (ending July 25th), on draft-ietf-mpls-p2mp-sig-requirement-03.txt restricted to the changes as a result of comments from the earlier last call. Please, send comments to the wg mailing list. Loa and George. Seisho Yasukawa wrote: > Dear MPLS WG, > > I have updated the P2MP Signaling Requirements draft after WG last call > comments. > > http://www.ietf.org/internet-drafts/draft-ietf-mpls-p2mp-sig-requirement-03.txt > > > Thank you all who commented or contributed to the off-line discussions. > > The agreed changes can be seen in the emails exchanged on the MPLS mailing > list. The highlight changes are as follows. > > Section 1 > - Remove comment about how TED might be populated. > - Add early exposure of discussion of rate of change of leaves. > > Section 2.2 > - Some re-work of definitions > - Note PID becomes P2ID > > Section 4.1 > - Clarify different switching types. > > Section 4.3 > - Explain "widely scoped abstract node" > - Clarify that policy may prevent the ingress learning the full tree of > the LSP > > Section 4.4 > - Clarify optimality versus scalability > > Section 4.7 > - Point out that route recording introduces scaling issues. > - Remove reference to RSVP-TE > > Section 4.12 > - Distinguish short-term packet duplication from long-term > > Section 4.14 > - Re-write for clarity > > Section 4.15 > - Remove solution-based hints > > Section 4.16 > - Deleted entire section as out of scope. > > Section 4.17 [was 4.18] > - Simplify and add reference to P2MP-OAM draft > > Section 4.19 [was 4.20] > - Remove reference to CCAMP WG > > Section 4.22 > - Deleted entire section as out of scope. > > > Thank you, > Seisho > > _______________________________________________ > mpls mailing list > mpls@lists.ietf.org > https://www1.ietf.org/mailman/listinfo/mpls > -- 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 Jul 18 21:24:55 2005 Received: from localhost.localdomain ([127.0.0.1] helo=megatron.ietf.org) by megatron.ietf.org with esmtp (Exim 4.32) id 1Dugqt-0007ym-70; Mon, 18 Jul 2005 21:24:55 -0400 Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org) by megatron.ietf.org with esmtp (Exim 4.32) id 1Dugqr-0007wC-2b for mpls@megatron.ietf.org; Mon, 18 Jul 2005 21:24:53 -0400 Received: from ietf-mx.ietf.org (ietf-mx [132.151.6.1]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id VAA06963 for ; Mon, 18 Jul 2005 21:24:51 -0400 (EDT) Received: from colo-dns-ext1.juniper.net ([207.17.137.57]) by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1DuhKN-0004nW-8n for mpls@ietf.org; Mon, 18 Jul 2005 21:55:24 -0400 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 j6J1Of932049; Mon, 18 Jul 2005 18:24:42 -0700 (PDT) (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 j6J1OaQ80474; Mon, 18 Jul 2005 18:24:36 -0700 (PDT) (envelope-from arthi@juniper.net) Date: Mon, 18 Jul 2005 18:24:36 -0700 (PDT) From: Arthi Ayyangar To: Loa Andersson Subject: Re: [mpls] draft-zamfir-explicit-resource-control-bundle-05.txt as a wg doc In-Reply-To: <42C39782.4030108@pi.se> Message-ID: <20050718182038.Y93118@zircon.juniper.net> References: <42C39782.4030108@pi.se> MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII X-Spam-Score: 0.0 (/) X-Scan-Signature: 9466e0365fc95844abaf7c3f15a05c7d Cc: Bill Fenner , 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. -arthi > > in Minneapolis we discussed the > draft-zamfir-explicit-resource-control-bundle-05.txt > (well an earlier version but anyway...) The authors suggested > that we make it a wg document. There were pretty good support > for this at the meeting could you before July 18th state > your opinions on making it a wg document. > > > 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 Jul 18 21:51:33 2005 Received: from localhost.localdomain ([127.0.0.1] helo=megatron.ietf.org) by megatron.ietf.org with esmtp (Exim 4.32) id 1DuhGf-0006oU-N3; Mon, 18 Jul 2005 21:51:33 -0400 Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org) by megatron.ietf.org with esmtp (Exim 4.32) id 1DuhGc-0006oP-Vj for mpls@megatron.ietf.org; Mon, 18 Jul 2005 21:51:31 -0400 Received: from ietf-mx.ietf.org (ietf-mx [132.151.6.1]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id VAA08383 for ; Mon, 18 Jul 2005 21:51:29 -0400 (EDT) Received: from mandala.kddilabs.jp ([192.26.91.6]) by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1DuhkA-0005jK-E5 for mpls@ietf.org; Mon, 18 Jul 2005 22:22:02 -0400 Received: from localhost (localhost [127.0.0.1]) by mandala.kddilabs.jp (Postfix) with ESMTP id 961A1EC82B; Tue, 19 Jul 2005 10:51:20 +0900 (JST) Received: from platinum.onw.kddilabs.jp (platinum.onw.kddilabs.jp [2001:200:601:1300:172:19:83:254]) by mandala.kddilabs.jp (Postfix) with ESMTP id 5CECBEC829; Tue, 19 Jul 2005 10:51:20 +0900 (JST) Received: from [IPv6:2001:200:601:1e02:0:5efe:ac13:570c] (unknown [IPv6:2001:200:601:1e02:0:5efe:ac13:570c]) by platinum.onw.kddilabs.jp (Postfix) with ESMTP id A31EF578103; Tue, 19 Jul 2005 10:46:28 +0900 (JST) Message-ID: <42DC5CEA.9020705@kddilabs.jp> Date: Tue, 19 Jul 2005 10:52:42 +0900 From: Tomohiro Otani User-Agent: Mozilla/5.0 (Windows; U; Windows NT 5.1; ja-JP; rv:1.7.2) Gecko/20040803 X-Accept-Language: ja, en-us, en MIME-Version: 1.0 To: Loa Andersson Subject: Re: [mpls] draft-zamfir-explicit-resource-control-bundle-05.txt as a wg doc References: <42C39782.4030108@pi.se> In-Reply-To: <42C39782.4030108@pi.se> Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit X-Virus-Scanned: by amavisd-new X-Spam-Score: 0.0 (/) X-Scan-Signature: 93238566e09e6e262849b4f805833007 Content-Transfer-Encoding: 7bit Cc: Bill Fenner , 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 support this draft. Regards, tomo Loa Andersson wrote: >Working group, > >in Minneapolis we discussed the >draft-zamfir-explicit-resource-control-bundle-05.txt >(well an earlier version but anyway...) The authors suggested >that we make it a wg document. There were pretty good support >for this at the meeting could you before July 18th state >your opinions on making it a wg document. > > >Loa and George > > > _______________________________________________ mpls mailing list mpls@lists.ietf.org https://www1.ietf.org/mailman/listinfo/mpls From mpls-bounces@lists.ietf.org Tue Jul 19 08:48:51 2005 Received: from localhost.localdomain ([127.0.0.1] helo=megatron.ietf.org) by megatron.ietf.org with esmtp (Exim 4.32) id 1DurWl-0004sz-DN; Tue, 19 Jul 2005 08:48:51 -0400 Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org) by megatron.ietf.org with esmtp (Exim 4.32) id 1DurWj-0004sf-QW for mpls@megatron.ietf.org; Tue, 19 Jul 2005 08:48:49 -0400 Received: from ietf-mx.ietf.org (ietf-mx [132.151.6.1]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id IAA10187 for ; Tue, 19 Jul 2005 08:48:48 -0400 (EDT) Received: from webmail.movaz.com ([65.205.166.188] helo=jera.movaz.com) by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1Dus0M-0005Mp-7X for mpls@ietf.org; Tue, 19 Jul 2005 09:19:27 -0400 Received: from ib (unknown [172.16.24.122]) by jera.movaz.com (Postfix) with SMTP id 9F66316A88 for ; Tue, 19 Jul 2005 08:48:36 -0400 (EDT) Message-ID: <006901c58c60$2df09de0$7a1810ac@movaz.com> From: "Igor Bryskin" To: References: Subject: Re: [mpls] draft-zamfir-explicit-resource-control-bundle-05.txt as a wgdoc Date: Tue, 19 Jul 2005 08:48:36 -0400 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.1437 X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2800.1441 X-Spam-Score: 0.0 (/) X-Scan-Signature: 8b30eb7682a596edff707698f4a80f7d Content-Transfer-Encoding: 7bit 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 support making this draft WG document. Igor -----Original Message----- From: mpls-bounces@lists.ietf.org [mailto:mpls-bounces@lists.ietf.org] On Behalf Of Loa Andersson Sent: Thursday, June 30, 2005 2:56 AM To: mpls@ietf.org Cc: Bill Fenner Subject: [mpls] draft-zamfir-explicit-resource-control-bundle-05.txt as a wgdoc Working group, in Minneapolis we discussed the draft-zamfir-explicit-resource-control-bundle-05.txt (well an earlier version but anyway...) The authors suggested that we make it a wg document. There were pretty good support for this at the meeting could you before July 18th state your opinions on making it a wg document. 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 Tue Jul 19 15:50:17 2005 Received: from localhost.localdomain ([127.0.0.1] helo=megatron.ietf.org) by megatron.ietf.org with esmtp (Exim 4.32) id 1Duy6b-0002co-13; Tue, 19 Jul 2005 15:50:17 -0400 Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org) by megatron.ietf.org with esmtp (Exim 4.32) id 1Duy6N-0002TX-Cm for mpls@megatron.ietf.org; Tue, 19 Jul 2005 15:50:03 -0400 Received: from newodin.ietf.org (newodin.ietf.org [10.27.6.50]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id PAA27898 for ; Tue, 19 Jul 2005 15:50:01 -0400 (EDT) Received: from mlee by newodin.ietf.org with local (Exim 4.43) id 1Duy6M-0002LG-JO; Tue, 19 Jul 2005 15:50:02 -0400 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, 19 Jul 2005 15:50:02 -0400 Cc: mpls@ietf.org Subject: [mpls] I-D ACTION:draft-ietf-mpls-rsvp-te-p2mp-02.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 : Extensions to RSVP-TE for Point to Multipoint TE LSPs Author(s) : R. Aggarwal, et al. Filename : draft-ietf-mpls-rsvp-te-p2mp-02.txt Pages : 48 Date : 2005-7-19 This document describes extensions to Resource Reservation Protocol - Traffic Engineering (RSVP-TE) for the setup of Traffic Engineered (TE) point-to-multipoint (P2MP) Label Switched Paths (LSPs) in Multi- Protocol Label Switching (MPLS) and Generalized MPLS (GMPLS) networks. The solution relies on RSVP-TE without requiring a multicast routing protocol in the Service Provider core. Protocol elements and procedures for this solution are described. There can be various applications for P2MP TE LSPs such as IP multicast. Specification of how such applications will use a P2MP TE LSP is outside the scope of this document. A URL for this Internet-Draft is: http://www.ietf.org/internet-drafts/draft-ietf-mpls-rsvp-te-p2mp-02.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-rsvp-te-p2mp-02.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-rsvp-te-p2mp-02.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: <2005-7-19121918.I-D@ietf.org> ENCODING mime FILE /internet-drafts/draft-ietf-mpls-rsvp-te-p2mp-02.txt --OtherAccess Content-Type: Message/External-body; name="draft-ietf-mpls-rsvp-te-p2mp-02.txt"; site="ftp.ietf.org"; access-type="anon-ftp"; directory="internet-drafts" Content-Type: text/plain Content-ID: <2005-7-19121918.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 Jul 19 15:50:18 2005 Received: from localhost.localdomain ([127.0.0.1] helo=megatron.ietf.org) by megatron.ietf.org with esmtp (Exim 4.32) id 1Duy6c-0002eA-Me; Tue, 19 Jul 2005 15:50:18 -0400 Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org) by megatron.ietf.org with esmtp (Exim 4.32) id 1Duy6N-0002TW-Ex for mpls@megatron.ietf.org; Tue, 19 Jul 2005 15:50:03 -0400 Received: from newodin.ietf.org (newodin.ietf.org [10.27.6.50]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id PAA27892 for ; Tue, 19 Jul 2005 15:50:01 -0400 (EDT) Received: from mlee by newodin.ietf.org with local (Exim 4.43) id 1Duy6M-0002Kd-Bi; Tue, 19 Jul 2005 15:50:02 -0400 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, 19 Jul 2005 15:50:02 -0400 Cc: mpls@ietf.org Subject: [mpls] I-D ACTION:draft-ietf-mpls-lsr-self-test-05.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 : Label Switching Router Self-Test Author(s) : G. Swallow, et al. Filename : draft-ietf-mpls-lsr-self-test-05.txt Pages : 14 Date : 2005-7-19 This document defines a means for a Label-Switching Router (LSR) to verify that its dataplane is functioning for certain key Multi- Protocol Label Switching (MPLS) applications, including unicast forwarding based on LDP [LDP] and traffic engineering tunnels based on [RSVP-TE]. A new Loopback FEC type is defined to allow an upstream neighbor to assist in the testing at very low cost. MPLS Echo Request and MPLS Echo Reply messages [LSP-Ping] are extended to do the actual probing. A URL for this Internet-Draft is: http://www.ietf.org/internet-drafts/draft-ietf-mpls-lsr-self-test-05.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-lsr-self-test-05.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-lsr-self-test-05.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: <2005-7-19120723.I-D@ietf.org> ENCODING mime FILE /internet-drafts/draft-ietf-mpls-lsr-self-test-05.txt --OtherAccess Content-Type: Message/External-body; name="draft-ietf-mpls-lsr-self-test-05.txt"; site="ftp.ietf.org"; access-type="anon-ftp"; directory="internet-drafts" Content-Type: text/plain Content-ID: <2005-7-19120723.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 Wed Jul 20 04:48:24 2005 Received: from localhost.localdomain ([127.0.0.1] helo=megatron.ietf.org) by megatron.ietf.org with esmtp (Exim 4.32) id 1DvAFc-0001Ym-9O; Wed, 20 Jul 2005 04:48:24 -0400 Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org) by megatron.ietf.org with esmtp (Exim 4.32) id 1DvAFa-0001Y3-6s for mpls@megatron.ietf.org; Wed, 20 Jul 2005 04:48:22 -0400 Received: from ietf-mx.ietf.org (ietf-mx [132.151.6.1]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id EAA20321 for ; Wed, 20 Jul 2005 04:48:20 -0400 (EDT) Received: from oberon.imc.kth.se ([193.10.152.20]) by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1DvAjL-0008Mh-Dc for mpls@ietf.org; Wed, 20 Jul 2005 05:19:10 -0400 Received: from mail1.imc.kth.se (mail1.imc.kth.se [193.10.152.140]) by oberon.imc.kth.se (8.11.6/8.11.6) with ESMTP id j6K8dgU24868 for ; Wed, 20 Jul 2005 10:39:42 +0200 Received: from [127.0.0.1] ([172.16.2.192]) by mail1.imc.kth.se; Wed, 20 Jul 2005 10:45:34 +0200 Message-ID: <42DE0F2D.5020904@pi.se> Date: Wed, 20 Jul 2005 10:45:33 +0200 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: Loa Andersson References: <42C39782.4030108@pi.se> In-Reply-To: <42C39782.4030108@pi.se> Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit X-Spam-Score: 0.0 (/) X-Scan-Signature: 69a74e02bbee44ab4f8eafdbcedd94a1 Content-Transfer-Encoding: 7bit Cc: Bill Fenner , mpls@ietf.org Subject: [mpls] draft-zamfir-explicit-resource-control-bundle-05.txt accepted as wg draft 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 find that there is a very good support for accepting the draft-zamfir-explicit-resource-control-bundle-05.txt as a working group draft. For all practical purposes we should from now on treat it as a wg draft, when it will appear from the next submission the name will be something like draft-ietf-mpls-explicit-resource-control-bundle-05.txt, possibly after the Paris meeting. Loa and George Loa Andersson wrote: > Working group, > > in Minneapolis we discussed the > draft-zamfir-explicit-resource-control-bundle-05.txt > (well an earlier version but anyway...) The authors suggested > that we make it a wg document. There were pretty good support > for this at the meeting could you before July 18th state > your opinions on making it a wg document. > > > 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 Wed Jul 20 10:41:56 2005 Received: from localhost.localdomain ([127.0.0.1] helo=megatron.ietf.org) by megatron.ietf.org with esmtp (Exim 4.32) id 1DvFlk-0001Ea-G7; Wed, 20 Jul 2005 10:41:56 -0400 Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org) by megatron.ietf.org with esmtp (Exim 4.32) id 1DvFlj-0001EH-1p for mpls@megatron.ietf.org; Wed, 20 Jul 2005 10:41:55 -0400 Received: from ietf-mx.ietf.org (ietf-mx [132.151.6.1]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id KAA22595 for ; Wed, 20 Jul 2005 10:41:52 -0400 (EDT) Received: from [80.86.78.228] (helo=smtp.testbed.se) by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1DvGFY-0007Ib-UK for mpls@ietf.org; Wed, 20 Jul 2005 11:12:46 -0400 Received: from gw.imc.kth.se ([193.10.152.67] helo=[172.16.2.192]) by fw.testbed.se with esmtpsa (TLSv1:AES256-SHA:256) (Exim 4.43) id 1DvFlT-0003SW-GJ; Wed, 20 Jul 2005 16:41:42 +0200 Message-ID: <42DE6214.7050605@pi.se> Date: Wed, 20 Jul 2005 16:39:16 +0200 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-Spam-Report: Spam detection software, running on the system "fw.testbed.se", has identified this incoming email as possible spam. The original message has been attached to this so you can view it (if it isn't spam) or label similar future email. If you have any questions, see the administrator of that system for details. Content preview: Working group, we've produced a first cut on the agenda for the Paris meeting. http://www.tla-group.com/~mpls/mpls-agenda-paris.htm [...] Content analysis details: (0.0 points, 5.0 required) pts rule name description ---- ---------------------- -------------------------------------------------- X-Spam-Score: 0.0 (/) X-Scan-Signature: 7d33c50f3756db14428398e2bdedd581 Content-Transfer-Encoding: 7bit Cc: Bill Fenner Subject: [mpls] MPLS wg agenda for Paris 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've produced a first cut on the agenda for the Paris meeting. http://www.tla-group.com/~mpls/mpls-agenda-paris.htm it is still preliminary and it is fully possible that we've dropped requests for agenda slots, if so get back to us. We will not close the agenda until the Monday morning of the IETF week. 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 Thu Jul 21 03:56:19 2005 Received: from localhost.localdomain ([127.0.0.1] helo=megatron.ietf.org) by megatron.ietf.org with esmtp (Exim 4.32) id 1DvVuj-0001LP-A1; Thu, 21 Jul 2005 03:56:17 -0400 Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org) by megatron.ietf.org with esmtp (Exim 4.32) id 1DvVug-0001L9-0s for mpls@megatron.ietf.org; Thu, 21 Jul 2005 03:56:15 -0400 Received: from ietf-mx.ietf.org (ietf-mx [132.151.6.1]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id DAA09754 for ; Thu, 21 Jul 2005 03:56:12 -0400 (EDT) Received: from p-mail1.rd.francetelecom.com ([195.101.245.15]) by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1DvWOf-0003WX-Bv for mpls@ietf.org; Thu, 21 Jul 2005 04:27:14 -0400 Received: from ftrdmel1.rd.francetelecom.fr ([10.193.117.152]) by ftrdsmtp1.rd.francetelecom.fr with Microsoft SMTPSVC(6.0.3790.211); Thu, 21 Jul 2005 09:55:37 +0200 X-MimeOLE: Produced By Microsoft Exchange V6.5.7226.0 Content-class: urn:content-classes:message MIME-Version: 1.0 Date: Thu, 21 Jul 2005 09:54:44 +0200 Message-ID: Thread-Topic: I-D ACTION:draft-leroux-mpls-mp-ldp-reqs-01.txt Thread-Index: AcWNx4ahgMNKBFcdSYWoQOCkW5Si0wAABxcg From: "LE ROUX Jean-Louis RD-CORE-LAN" To: X-OriginalArrivalTime: 21 Jul 2005 07:55:37.0157 (UTC) FILETIME=[94A2D750:01C58DC9] X-Spam-Score: 0.6 (/) X-Scan-Signature: e654cfa5e44bd623be3eb2c720858b05 Cc: Subject: [mpls] TR: I-D ACTION:draft-leroux-mpls-mp-ldp-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: , Content-Type: multipart/mixed; boundary="===============0394539237==" Sender: mpls-bounces@lists.ietf.org Errors-To: mpls-bounces@lists.ietf.org This is a multi-part message in MIME format. --===============0394539237== Content-class: urn:content-classes:message Content-Type: multipart/alternative; boundary="----_=_NextPart_001_01C58DC9.2BE18C85" This is a multi-part message in MIME format. ------_=_NextPart_001_01C58DC9.2BE18C85 Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: quoted-printable Hi all, Here is version 01 of the requirements for P2MP extensions to LDP. Detailed requirements for multipoint-to-multipoint LSPs have been removed as they were too solution dependant. They are left for further study. Please comment on this new version. Best Regards, JL et al. > A New Internet-Draft is available from the on-line Internet-Drafts > directories. >=20 >=20 > 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-01.txt > Pages : 15 > Date : 2005-7-20 > =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. >=20 > A URL for this Internet-Draft is: > http://www.ietf.org/internet-drafts/draft-leroux-mpls-mp-ldp-reqs-01.t > xt >=20 > 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. >=20 >=20 > 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-01.txt". >=20 > 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 >=20 >=20 > Internet-Drafts can also be obtained by e-mail. >=20 > Send a message to: > mailserv at ietf.org. > In the body type: > "FILE /internet-drafts/draft-leroux-mpls-mp-ldp-reqs-01.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. > xt> > xt> =20 > _______________________________________________ > I-D-Announce mailing list > I-D-Announce at ietf.org > https://www1.ietf.org/mailman/listinfo/i-d-announce >=20 ------_=_NextPart_001_01C58DC9.2BE18C85 Content-Type: text/html; charset="us-ascii" Content-Transfer-Encoding: quoted-printable TR: I-D ACTION:draft-leroux-mpls-mp-ldp-reqs-01.txt

Hi all,

Here is version 01 of = the requirements for P2MP extensions to LDP.
Detailed = requirements for multipoint-to-multipoint LSPs have been removed as they = were too solution dependant.
They are left for = further study.

Please comment on = this new version.

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-01.txt
        Pages   =         : 15
        Date    =         : 2005-7-20
       =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-01= .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-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 at ietf.org.
In the body type:
        "FILE = /internet-drafts/draft-leroux-mpls-mp-ldp-reqs-01.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-01.txt>
_______________________________________________
I-D-Announce mailing list
I-D-Announce at ietf.org
https://www1.ietf.org/mailman/listinfo/i-d-announce

------_=_NextPart_001_01C58DC9.2BE18C85-- --===============0394539237== 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 --===============0394539237==-- From mpls-bounces@lists.ietf.org Thu Jul 21 07:44:22 2005 Received: from localhost.localdomain ([127.0.0.1] helo=megatron.ietf.org) by megatron.ietf.org with esmtp (Exim 4.32) id 1DvZTS-0008Bl-5B; Thu, 21 Jul 2005 07:44:22 -0400 Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org) by megatron.ietf.org with esmtp (Exim 4.32) id 1DvZTQ-0008Bg-Bk for mpls@megatron.ietf.org; Thu, 21 Jul 2005 07:44:20 -0400 Received: from ietf-mx.ietf.org (ietf-mx [132.151.6.1]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id HAA21952 for ; Thu, 21 Jul 2005 07:44:19 -0400 (EDT) Received: from [80.86.78.228] (helo=smtp.testbed.se) by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1DvZxO-0001MO-Bx for mpls@ietf.org; Thu, 21 Jul 2005 08:15:22 -0400 Received: from gw.imc.kth.se ([193.10.152.67] helo=[172.16.2.192]) by fw.testbed.se with esmtpsa (TLSv1:AES256-SHA:256) (Exim 4.43) id 1DvZT2-0008Mp-Mt for mpls@ietf.org; Thu, 21 Jul 2005 13:44:00 +0200 Message-ID: <42DF89E8.8040503@pi.se> Date: Thu, 21 Jul 2005 13:41:28 +0200 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-Spam-Report: Spam detection software, running on the system "fw.testbed.se", has identified this incoming email as possible spam. The original message has been attached to this so you can view it (if it isn't spam) or label similar future email. If you have any questions, see the administrator of that system for details. Content preview: All, I've updated the mpls wg agenda after comments. http://www.tla-group.com/~mpls/mpls-agenda-paris.htm [...] Content analysis details: (0.0 points, 5.0 required) pts rule name description ---- ---------------------- -------------------------------------------------- X-Spam-Score: 0.0 (/) X-Scan-Signature: 79899194edc4f33a41f49410777972f8 Content-Transfer-Encoding: 7bit Cc: Subject: [mpls] updated agenda 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, I've updated the mpls wg agenda after comments. http://www.tla-group.com/~mpls/mpls-agenda-paris.htm I will continue update until the meeting, but won't in the interest of traffic load announce every update to the list. /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 Thu Jul 21 18:50:09 2005 Received: from localhost.localdomain ([127.0.0.1] helo=megatron.ietf.org) by megatron.ietf.org with esmtp (Exim 4.32) id 1Dvjrl-0005pe-J4; Thu, 21 Jul 2005 18:50:09 -0400 Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org) by megatron.ietf.org with esmtp (Exim 4.32) id 1Dvjre-0005nT-TZ for mpls@megatron.ietf.org; Thu, 21 Jul 2005 18:50:03 -0400 Received: from newodin.ietf.org (newodin.ietf.org [10.27.6.50]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id SAA22505 for ; Thu, 21 Jul 2005 18:49:59 -0400 (EDT) Received: from mlee by newodin.ietf.org with local (Exim 4.43) id 1Dvjre-0004Z4-67; Thu, 21 Jul 2005 18:50:02 -0400 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, 21 Jul 2005 18:50:02 -0400 Cc: mpls@ietf.org Subject: [mpls] I-D ACTION:draft-ietf-mpls-oam-requirements-06.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 : OAM Requirements for MPLS Networks Author(s) : T. Nadeau, et al. Filename : draft-ietf-mpls-oam-requirements-06.txt Pages : 15 Date : 2005-7-21 As transport of diverse traffic types such as voice, frame relay, and ATM over MPLS become more common, the ability to detect, handle and diagnose control and data plane defects becomes critical. Detection and specification of how to handle those defects is not only important because such defects may not only affect the fundamental operation of an Multi-Protocol Label Switching (MPLS) network, but also because they MAY impact service level specification commitments for customers of that network. This document describes requirements for user and data plane operations and management for MPLS. These requirements have been gathered from network operators who have extensive experience deploying MPLS networks, similarly some of these requirements have appeared in other documents. This draft specifies Operations and Management requirements for Multi-Protocol Label Switching, as well as for applications of Multi-Protocol Label Switching such as pseudowire voice and virtual private network services. Those interested in specific issues relating to instrumenting MPLS for Operations and Management purposes are directed to the Multi-Protocol Label Switching Architecture specification. A URL for this Internet-Draft is: http://www.ietf.org/internet-drafts/draft-ietf-mpls-oam-requirements-06.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-oam-requirements-06.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-oam-requirements-06.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: <2005-7-21172318.I-D@ietf.org> ENCODING mime FILE /internet-drafts/draft-ietf-mpls-oam-requirements-06.txt --OtherAccess Content-Type: Message/External-body; name="draft-ietf-mpls-oam-requirements-06.txt"; site="ftp.ietf.org"; access-type="anon-ftp"; directory="internet-drafts" Content-Type: text/plain Content-ID: <2005-7-21172318.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 Jul 22 06:43:18 2005 Received: from localhost.localdomain ([127.0.0.1] helo=megatron.ietf.org) by megatron.ietf.org with esmtp (Exim 4.32) id 1Dvuzu-0001yx-LU; Fri, 22 Jul 2005 06:43:18 -0400 Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org) by megatron.ietf.org with esmtp (Exim 4.32) id 1Dvuzr-0001ve-WF for mpls@megatron.ietf.org; Fri, 22 Jul 2005 06:43:16 -0400 Received: from ietf-mx.ietf.org (ietf-mx [132.151.6.1]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id GAA00335 for ; Fri, 22 Jul 2005 06:43:12 -0400 (EDT) From: benjamin.niven-jenkins@bt.com Received: from smtp3.smtp.bt.com ([217.32.164.138]) by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1DvvU4-000789-Ta for mpls@ietf.org; Fri, 22 Jul 2005 07:14:30 -0400 Received: from i2km95-ukbr.domain1.systemhost.net ([193.113.197.29]) by smtp3.smtp.bt.com with Microsoft SMTPSVC(6.0.3790.211); Fri, 22 Jul 2005 11:43:00 +0100 Received: from i2km86-ukdy.domain1.systemhost.net ([193.113.30.79]) by i2km95-ukbr.domain1.systemhost.net with Microsoft SMTPSVC(5.0.2195.6713); Fri, 22 Jul 2005 11:43:00 +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] I-D ACTION:draft-ietf-mpls-oam-requirements-06.txt Date: Fri, 22 Jul 2005 11:43:50 +0100 Message-ID: Thread-Topic: [mpls] I-D ACTION:draft-ietf-mpls-oam-requirements-06.txt Thread-Index: AcWOSWEIEHyUbSdIR2yKdHlaJWkcJwAXtoAA To: X-OriginalArrivalTime: 22 Jul 2005 10:43:00.0885 (UTC) FILETIME=[2193DC50:01C58EAA] X-Spam-Score: 0.3 (/) X-Scan-Signature: 50a516d93fd399dc60588708fd9a3002 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 Colleagues, Following a very quick scan of draft-ietf-mpls-oam-requirements-06, I have the following comments/suggestions. 1) In the abstract & introduction the document refers to "requirements for user and data plane operations and management", in later sections reference is made to "MPLS data plane". The usage of such terms appear to be inconsistent to me. I tend to interpret 'user plane' to mean the plane along which user data is transferred and 'data plane' to mean the data forwarding plane of any plane - i.e. data plane can be used to refer to the data forwarding plane of the user plane, or the data forwarding plane of the control plane, or the data forwarding plane of the management plane. However I get the impression from the document that user plane =3D=3D data plane. So I would suggest that either the document standardises on one term for (what I would call) the user plane, or that the terminology section is expanded to highlight the difference between what is meant by user plane Vs data plane. 2) The document refers to "customer traffic" and "user traffic". Is customer traffic synonymous with user traffic, in which case I would suggest that the document standardises on one term. 3) Furthermore, I am not sure what is meant by customer - I assume what is meant is the client layer of the MPLS (server) layer, in which case I would comment that this client layer does not necessarily belong to a "customer". I would suggest either replacing customer with a less ambiguous term (e.g. client or client layer) or that the terminology section be expanded to include a definition of what is meant by customer and how this differs from a client layer that is not owned by a customer (e.g. a SP may use a label stack to help scaling/aggregation, but the same SP owns the client & server MPLS layers, so who is the customer?). 4) Section 4.5, insofaras =3D> insofar as Thanks Ben --=20 Ben Niven-Jenkins Networking Specialist, 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 Sat Jul 23 22:44:03 2005 Received: from localhost.localdomain ([127.0.0.1] helo=megatron.ietf.org) by megatron.ietf.org with esmtp (Exim 4.32) id 1DwWTD-0002mF-OI; Sat, 23 Jul 2005 22:44:03 -0400 Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org) by megatron.ietf.org with esmtp (Exim 4.32) id 1DwLJG-000248-6V; Sat, 23 Jul 2005 10:49:02 -0400 Received: from ietf-mx.ietf.org (ietf-mx [132.151.6.1]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id KAA00422; Sat, 23 Jul 2005 10:48:58 -0400 (EDT) Received: from smtp11.singnet.com.sg ([165.21.6.21]) by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1DwLng-0007bF-Hp; Sat, 23 Jul 2005 11:20:29 -0400 Received: from bearty1 (qtas0852.singnet.com.sg [165.21.57.242]) by smtp11.singnet.com.sg (8.13.4/8.13.4) with SMTP id j6NEiCfb007762; Sat, 23 Jul 2005 22:44:16 +0800 Message-ID: <000501c58f95$04589360$f23915a5@bearty1> From: "Boon Sain Yeo" To: Date: Sat, 23 Jul 2005 22:03:35 +0800 MIME-Version: 1.0 X-Priority: 3 X-MSMail-Priority: Normal X-Mailer: Microsoft Outlook Express 6.00.2900.2180 X-MIMEOLE: Produced By Microsoft MimeOLE V6.00.2900.2180 X-Spam-Score: 0.7 (/) X-Scan-Signature: 10d2fdecab7a7fa796e06e001d026c91 X-Mailman-Approved-At: Sat, 23 Jul 2005 22:44:01 -0400 Cc: Subject: [mpls] Call for Participation ---ISWCS 2005, Siena, Italy, 5 - 7 September 2005 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="===============0015503631==" Sender: mpls-bounces@lists.ietf.org Errors-To: mpls-bounces@lists.ietf.org This is a multi-part message in MIME format. --===============0015503631== Content-Type: multipart/alternative; boundary="----=_NextPart_000_001F_01C58FD2.5F4097E0" This is a multi-part message in MIME format. ------=_NextPart_000_001F_01C58FD2.5F4097E0 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: quoted-printable (My apologies if you receive multiple copies of this message) =20 Dear Colleagues, =20 Please find the call for participation for ISWCS 2005, 5 - 7 September = 2005, Siena, Italy below. =20 On behalf we look forward to receiving you at ISWCS 2005. =20 Many thanks Best regards, Boon =20 General Co-chair =20 *************** CALL FOR PARTICIPATION ********************** =20 ISWCS 2005 2nd International Symposium on Wireless Communication Systems http://www.iswcs.org/iswcs2005 5 - 7 September 2005, Siena, Italy =20 *************** CALL FOR PARTICIPATION ********************** =20 The Technical Program includes 100 full papers and 33 poster papers. Out = of 252 submissions, the Technical Program Committee worked very = diligently and professionally in the selection of the final papers, with = at least three reviews for each submitted contribution. The Program is = structured in three parallel tracks and 5 sessions per track, with a = total of 15 sessions. The three tracks represent key areas in wireless = communications, namely: wireless network layer; radio channel modulation = and coding, and; wireless network applications. The session topics (and = the paper contributions) are very indicative of current research = interests in the wireless field. Please find more information with = regards to the technical program at the following URL: = http://www.iswcs.org/iswcs2005/plan_technical_sessions_ISWCS_2005.pdf =20 Posters represent work in progress and have been given a very visible = role (and an important slot) in the program. In fact, the poster = presentations will follow immediately the Plenary Session on the morning = of Sept 7. We expect active discussion around posters and interaction = with authors. The panel will precede the social dinner on Sept 6 - it = will be addressing the very timely and, in many aspects still = controversial topic, entitled "Towards a wireless and ubiquitous = information society". The panelists comprise of researchers from IBM, = Harris Corporation, Alcatel, KDDI R&D Lab, among others. =20 We have been very lucky to secure two well known and esteemed = researchers in the wireless community - Dr Victor Bahl, Microsoft = Research and Prof Dharma P. Agrawal, University of Cincinnati - as = keynote and plenary speakers respectively. Dr Bahl talk "Bridging the = Information Divide: Challenges & Opportunities" will touch a very = critical problem created by the Internet today and will describe how = wireless technologies will enable ubiquitous connectivity and services = connecting rural villages in remote areas using a programmable mobile = platform. Prof Agrawal talk, entitled "Why use Aggregate Logical Sensor = Units for large Sensor Networks?", will address a critical area of = sensor networks - tight energy constraints. Dr Agrawal will show that = such constraints can be relaxed by aggregating off the shelf sensors = into logical units that support the desired functions. =20 =20 ------=_NextPart_000_001F_01C58FD2.5F4097E0 Content-Type: text/html; charset="iso-8859-1" Content-Transfer-Encoding: quoted-printable
(My apologies=20 if you receive multiple copies of this message)

 

Dear Colleagues,

 

Please find the call for participation for ISWCS 2005, 5 - 7 = September=20 2005, Siena,=20 Italy = below.

 

On behalf we look forward to receiving you at ISWCS = 2005.

 

Many thanks

Best regards,

Boon

 

General Co-chair

 

*************** CALL FOR PARTICIPATION = **********************

 

ISWCS 2005

2nd International Symposium on Wireless Communication = Systems

http://www.iswcs.org/iswcs2005

5 - 7 September=20 2005, Siena,=20 Italy<= /P>

 

*************** CALL FOR PARTICIPATION = **********************

 

The Technical Program includes 100 full papers and 33 poster = papers. Out=20 of 252 submissions, the Technical Program Committee worked very = diligently and=20 professionally in the selection of the final papers, with at least three = reviews=20 for each submitted contribution. The Program is structured in three = parallel=20 tracks and 5 sessions per track, with a total of 15 sessions. The three = tracks=20 represent key areas in wireless communications, namely: wireless network = layer;=20 radio channel modulation and coding, and; wireless network applications. = The=20 session topics (and the paper contributions) are very indicative of = current=20 research interests in the wireless field. =20 Please find more information with regards to the technical = program at the=20 following URL: http://www.iswcs.org/iswcs2005/plan_technical_sessions_ISWCS_200= 5.pdf

 

Posters represent work in progress and have been given a very = visible=20 role (and an important slot) in the program. In fact, the poster = presentations=20 will follow immediately the Plenary Session on the morning of Sept 7. We = expect=20 active discussion around posters and interaction with authors. The panel = will=20 precede the social dinner on Sept 6 =96 it will be addressing the very = timely and,=20 in many aspects still controversial topic, entitled "Towards a wireless = and=20 ubiquitous information society". The panelists comprise of researchers = from IBM,=20 Harris Corporation, Alcatel, KDDI R&D Lab, among others.

 

We have been very lucky to secure two well known and esteemed = researchers=20 in the wireless community =96 Dr Victor Bahl, Microsoft Research  and Prof Dharma P. Agrawal,=20 University of=20 Cincinnati - as keynote and = plenary=20 speakers respectively.  Dr = Bahl talk=20 =93Bridging the Information Divide: Challenges & Opportunities=94 = will touch a=20 very critical problem created by the Internet today and will describe = how=20 wireless technologies will enable ubiquitous connectivity and services=20 connecting rural villages in remote areas using a programmable mobile=20 platform.  Prof Agrawal = talk,=20 entitled =93Why use Aggregate Logical Sensor Units for large Sensor = Networks?=94,=20 will address a critical area of sensor networks =96 tight energy = constraints. Dr=20 Agrawal will show that such constraints can be relaxed by aggregating = off the=20 shelf sensors into logical units that support the desired = functions.

 

 

------=_NextPart_000_001F_01C58FD2.5F4097E0-- --===============0015503631== 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 --===============0015503631==-- From mpls-bounces@lists.ietf.org Tue Jul 26 07:52:53 2005 Received: from localhost.localdomain ([127.0.0.1] helo=megatron.ietf.org) by megatron.ietf.org with esmtp (Exim 4.32) id 1DxNzR-0004nc-Re; Tue, 26 Jul 2005 07:52:53 -0400 Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org) by megatron.ietf.org with esmtp (Exim 4.32) id 1DxEpy-0003j5-99; Mon, 25 Jul 2005 22:06:30 -0400 Received: from ietf-mx.ietf.org (ietf-mx [132.151.6.1]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id WAA14135; Mon, 25 Jul 2005 22:06:27 -0400 (EDT) Received: from rodin.i2r.a-star.edu.sg ([192.122.139.27]) by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1DxFKs-0000rj-5l; Mon, 25 Jul 2005 22:38:29 -0400 Received: from rodin.i2r.a-star.edu.sg (localhost [127.0.0.1]) by rodin.i2r.a-star.edu.sg (8.13.1/8.13.1) with ESMTP id j6Q265HU019309; Tue, 26 Jul 2005 10:06:05 +0800 (SGT) Received: from newmailhost.i2r.a-star.edu.sg ([192.122.134.76])by rodin.i2r. a-star.edu.sg (8.13.1/8.13.1) with ESMTP id j6Q261ej019234; Tue, 26 Jul 2005 10:06:02 +0800 (SGT) Received: from Athena ([192.168.136.189])by mailhost.lit.org.sg (Sun Java Sy stem Messaging Server 6.1 HotFix 0.06(built Nov 11 2004)) with SMTP id <0IK 7001N3PU58240@mailhost.lit.org.sg>; Tue,26 Jul 2005 10:06:05 +0800 (SGT) Date: Tue, 26 Jul 2005 10:05:06 +0800 From: Yeo Boon Sain To: Message-id: <002d01c59186$716f1e40$bd88a8c0@Athena> MIME-version: 1.0 X-MIMEOLE: Produced By Microsoft MimeOLE V6.00.2800.1506 X-Mailer: Microsoft Outlook Express 6.00.2800.1506 Content-type: text/plain; charset=iso-8859-1 Content-transfer-encoding: 7BIT X-Priority: 3 X-MSMail-priority: Normal X-imss-version: 2.0 X-imss-result: Passed X-imss-scores: Clean:33.86113 C:17 M:1 S:5 R:5 X-imss-settings: Baseline:5 C:4 M:4 S:4 R:4 (1.5000 6.0000) X-Spam-Score: 0.0 (/) X-Scan-Signature: a2c12dacc0736f14d6b540e805505a86 Content-Transfer-Encoding: 7BIT X-Mailman-Approved-At: Tue, 26 Jul 2005 07:52:51 -0400 Cc: Subject: [mpls] CFP - Internationl Symposium on Wireless Pervasive Computing 2006, P huket, Thailand 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 We sincerely apologize if you receive this CFP more than once. -------------------------------------------------------- 1st International Symposium on Wireless Pervasive Computing 2006 16 - 18 January 2006, Phuket, Thailand Technically Sponsored by IEEE Communications Society Hosted by Suranaree University of Technology, Thailand IMPORTANT DATES Last date for submitting of papers, proposals for tutorials and panel sessions: August 1, 2005 Notification of Acceptance: September 15, 2005 Last date for submission of camera-ready versions of accepted papers: November 15, 2005 Wireless pervasive computing is a rapidly growing area increasingly attracting attention due to its potential impact on the quality of lifestyles of individuals. This can only be made possible by integrating technologies from the fields of communications , signal processing , computing and numerous other fields. This symposium aims to provide a platform for researchers in the collective area of wireless pervasive computing or any of the related areas to showcase their results, launch new ideas, as well as to interact with colleagues from this area. The scope of the symposium covers concepts and all enabling technologies of wireless pervasive computing. This includes a huge variety of topics ranging from wireless communications and networking to services and applications of pervasive computing . A series of panel and tutorials will also seek to inform and invoke interaction among researchers which are interested in this area. Topics of interest include but are NOT LIMITED to the following: . PCS, GPRS, EDGE, 3GPP, UMTS, GSM and B3G systems . Bluetooth technologies . Air interfaces (e.g. CDMA, OFDM, TDMA) . Dynamic spectrum management . Signal processing . Wireless access techniques . Multirate and multicarrier communications . Detection and estimation . Signal separation and interference rejection . Power control . Interference avoidance . Wireless systems design . Propagation and channel characterization . Diversity techniques & equalization . UWB . Multi-user Detection . MIMO systems . WiMAX . Cooperative coding and algorithms . WLANs and WPANs . RF systems . Coding and modulation techniques . Location management techniques . Localization and tracking techniques . Wireless multimedia . Switching and routing techniques . Wireless multicasting . Wireless network architecture . Ad hoc networks . Wireless sensor networks . Speech and video processing . Wireless security . Security applications . Wearable devices . Middleware . Multimedia systems . Resource management and interference management . Healthcare applications PAPER SUBMISSION GUIDELINES Acceptance will be based on an extended abstract of about 1500 words (two pages in the standard IEEE conference format). The extended abstract should include diagrams, initial results, and details required for the reviewers to assess the contribution of your work. A short summary of approximately 150 words is also required at the time of submission of the extended abstract. Extended abstracts must be submitted electronically by August 1, 2005, via EDAS (http://edas.info). PANEL SESSIONS & TUTORIALS Proposals for Tutorial and Panel Sessions are also being solicited. Tutorials (half-day or full-day sessions) are intended to provide in-depth learning on a specific topic of interest to the participants. Panel sessions are 60 minutes long. They present leaders in a particular area discussing a topic of interest within the scope of the symposium. Proposals for Tutorials and Panel sessions should consist of 1000 words summary, a 150 word abstract, and a cover page listing the details of the author(s). The pdf version of the cfp can be found at http://www.iswpc.org/2006/cfp.pdf _______________________________________________ mpls mailing list mpls@lists.ietf.org https://www1.ietf.org/mailman/listinfo/mpls