From mpls-bounces@ietf.org Wed Dec 1 02:50:33 2004 Received: from ietf-mx.ietf.org (ietf-mx.ietf.org [132.151.6.1]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id CAA12373; Wed, 1 Dec 2004 02:50:33 -0500 (EST) Received: from megatron.ietf.org ([132.151.6.71]) by ietf-mx.ietf.org with esmtp (Exim 4.33) id 1CZPLF-0001FL-Qm; Wed, 01 Dec 2004 02:56:02 -0500 Received: from localhost.localdomain ([127.0.0.1] helo=megatron.ietf.org) by megatron.ietf.org with esmtp (Exim 4.32) id 1CZP5z-0004Ra-Ql; Wed, 01 Dec 2004 02:40:15 -0500 Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org) by megatron.ietf.org with esmtp (Exim 4.32) id 1CZP3Z-0003gl-8B for mpls@megatron.ietf.org; Wed, 01 Dec 2004 02:37:45 -0500 Received: from cel-bangt-m02.india.celstream.com ([164.164.95.11]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id CAA06173 for ; Wed, 1 Dec 2004 02:37:32 -0500 (EST) Received: from cel-bangt-m02.india.celstream.com ([10.255.10.18]) by cel-bangt-m02.india.celstream.com with InterScan Messaging Security Suite; Wed, 01 Dec 2004 13:00:37 +0530 Received: by CEL-BANGT-M02 with Internet Mail Service (5.5.2653.19) id ; Wed, 1 Dec 2004 13:00:37 +0530 Message-ID: <80464F9A4D2BF042A154DD067F1F539302F14082@CEL-BANGT-M01> From: "RaviR [IS]" To: mpls@ietf.org Date: Wed, 1 Dec 2004 13:05:20 +0530 MIME-Version: 1.0 X-Mailer: Internet Mail Service (5.5.2653.19) Subject: [mpls] 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: , Content-Type: multipart/mixed; boundary="===============0275375907==" Sender: mpls-bounces@ietf.org Errors-To: mpls-bounces@ietf.org X-Spam-Score: 0.5 (/) X-Scan-Signature: bdc523f9a54890b8a30dd6fd53d5d024 This message is in MIME format. Since your mail reader does not understand this format, some or all of this message may not be legible. --===============0275375907== Content-Type: multipart/alternative; boundary="----_=_NextPart_001_01C4D778.4F7C4C90" This message is in MIME format. Since your mail reader does not understand this format, some or all of this message may not be legible. ------_=_NextPart_001_01C4D778.4F7C4C90 Content-Type: text/plain Hi, We have planned to have an MPLS connectivity from India to France. Can some one provide some comments on Pros & cons of MPLS over IPLC link. Regards, Ravi.R ---------------------------------------------------------------------------- -------- Celstream Technologies Pvt LTD. +91 80 51191919 This message is free from Virus - IMSS ------_=_NextPart_001_01C4D778.4F7C4C90 Content-Type: text/html

Hi,

We have planned to have an MPLS connectivity from India to France.

Can some one provide some comments on Pros & cons of MPLS over IPLC link.

Regards,

Ravi.R

------------------------------------------------------------------------------------

Celstream Technologies Pvt LTD.

+91 80 51191919

This message is free from Virus - IMSS

------_=_NextPart_001_01C4D778.4F7C4C90-- --===============0275375907== Content-Type: text/plain; charset="us-ascii" MIME-Version: 1.0 Content-Transfer-Encoding: 7bit Content-Disposition: inline Content-Transfer-Encoding: 7bit _______________________________________________ mpls mailing list mpls@lists.ietf.org https://www1.ietf.org/mailman/listinfo/mpls --===============0275375907==-- From mailman-bounces@ietf.org Wed Dec 1 06:06:58 2004 Received: from ietf-mx.ietf.org (ietf-mx.ietf.org [132.151.6.1]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id GAA13483 for ; Wed, 1 Dec 2004 06:06:58 -0500 (EST) Received: from megatron.ietf.org ([132.151.6.71]) by ietf-mx.ietf.org with esmtp (Exim 4.33) id 1CZSPN-0005X8-Oo for mpls-archive@ietf.org; Wed, 01 Dec 2004 06:12:29 -0500 Received: from localhost.localdomain ([127.0.0.1] helo=megatron.ietf.org) by megatron.ietf.org with esmtp (Exim 4.32) id 1CZRlL-0008Qe-MB for mpls-archive@ietf.org; Wed, 01 Dec 2004 05:31:07 -0500 MIME-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit Subject: lists.ietf.org mailing list memberships reminder From: mailman-owner@ietf.org To: mpls-archive@ietf.org X-No-Archive: yes Message-ID: Date: Wed, 01 Dec 2004 05:13:16 -0500 Precedence: bulk X-BeenThere: mailman@lists.ietf.org X-Mailman-Version: 2.1.5 List-Id: Mailman site list X-List-Administrivia: yes Sender: mailman-bounces@ietf.org Errors-To: mailman-bounces@ietf.org X-Spam-Score: 0.3 (/) X-Scan-Signature: 3e15cc4fdc61d7bce84032741d11c8e5 Content-Transfer-Encoding: 7bit This is a reminder, sent out once a month, about your lists.ietf.org mailing list memberships. It includes your subscription info and how to use it to change it or unsubscribe from a list. You can visit the URLs to change your membership status or configuration, including unsubscribing, setting digest-style delivery or disabling delivery altogether (e.g., for a vacation), and so on. In addition to the URL interfaces, you can also use email to make such changes. For more info, send a message to the '-request' address of the list (for example, mailman-request@lists.ietf.org) containing just the word 'help' in the message body, and an email message will be sent to you with instructions. ********************************************************************** NOTE WELL: Any submission to the IETF intended by the Contributor for publication as all or part of an IETF Internet-Draft or RFC and any statement made within the context of an IETF activity is considered an "IETF Contribution". Such statements include oral statements in IETF sessions, as well as written and electronic communications made at any time or place, which are addressed to: o the IETF plenary session, o any IETF working group or portion thereof, o the IESG, or any member thereof on behalf of the IESG, o the IAB or any member thereof on behalf of the IAB, o any IETF mailing list, including the IETF list itself, any working group or design team list, or any other list functioning under IETF auspices, o the RFC Editor or the Internet-Drafts function All IETF Contributions are subject to the rules of RFC 3667 and RFC 3668. Statements made outside of an IETF session, mailing list or other function, that are clearly not intended to be input to an IETF activity, group or function, are not IETF Contributions in the context of this notice. Please consult RFC 3667 for details. ******************************************************************************* If you have questions, problems, comments, etc, send them to mailman-owner@lists.ietf.org. Thanks! Passwords for mpls-archive@ietf.org: List Password // URL ---- -------- mpls@lists.ietf.org duubek https://www1.ietf.org/mailman/options/mpls/mpls-archive%40ietf.org From mpls-bounces@ietf.org Wed Dec 1 14:27:59 2004 Received: from ietf-mx.ietf.org (ietf-mx.ietf.org [132.151.6.1]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id OAA14108; Wed, 1 Dec 2004 14:27:59 -0500 (EST) Received: from megatron.ietf.org ([132.151.6.71]) by ietf-mx.ietf.org with esmtp (Exim 4.33) id 1CZaEJ-0001Lg-TZ; Wed, 01 Dec 2004 14:33:36 -0500 Received: from localhost.localdomain ([127.0.0.1] helo=megatron.ietf.org) by megatron.ietf.org with esmtp (Exim 4.32) id 1CZZNM-0004dv-M1; Wed, 01 Dec 2004 13:38:53 -0500 Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org) by megatron.ietf.org with esmtp (Exim 4.32) id 1CZYUI-0002Jt-5G for mpls@megatron.ietf.org; Wed, 01 Dec 2004 12:41:58 -0500 Received: from megatron.ietf.org (megatron.ietf.org [132.151.6.71]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id MAA02784 for ; Wed, 1 Dec 2004 12:41:56 -0500 (EST) Received: from apache by megatron.ietf.org with local (Exim 4.32) id 1CZXkF-0005w3-Ux; Wed, 01 Dec 2004 11:54:24 -0500 X-test-idtracker: no To: IETF-Announce From: The IESG Message-Id: Date: Wed, 01 Dec 2004 11:54:23 -0500 Cc: mpls@ietf.org Subject: [mpls] Last Call: 'Removing a Restriction on the use of MPLS Explicit NULL' 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@ietf.org Errors-To: mpls-bounces@ietf.org X-Spam-Score: 0.0 (/) X-Scan-Signature: 856eb5f76e7a34990d1d457d8e8e5b7f The IESG has received a request from the Multiprotocol Label Switching WG to consider the following document: - 'Removing a Restriction on the use of MPLS Explicit NULL ' 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 2004-12-15. The file can be obtained via http://www.ietf.org/internet-drafts/draft-ietf-mpls-explicit-null-01.txt _______________________________________________ mpls mailing list mpls@lists.ietf.org https://www1.ietf.org/mailman/listinfo/mpls From mpls-bounces@ietf.org Wed Dec 1 16:58:15 2004 Received: from ietf-mx.ietf.org (ietf-mx.ietf.org [132.151.6.1]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id QAA00938; Wed, 1 Dec 2004 16:58:15 -0500 (EST) Received: from megatron.ietf.org ([132.151.6.71]) by ietf-mx.ietf.org with esmtp (Exim 4.33) id 1CZcZk-00065z-BX; Wed, 01 Dec 2004 17:03:52 -0500 Received: from localhost.localdomain ([127.0.0.1] helo=megatron.ietf.org) by megatron.ietf.org with esmtp (Exim 4.32) id 1CZbxu-00084z-RV; Wed, 01 Dec 2004 16:24:46 -0500 Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org) by megatron.ietf.org with esmtp (Exim 4.32) id 1CZbVo-0006lo-Dp for mpls@megatron.ietf.org; Wed, 01 Dec 2004 15:55:44 -0500 Received: from megatron.ietf.org (megatron.ietf.org [132.151.6.71]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id PAA23328 for ; Wed, 1 Dec 2004 15:55:43 -0500 (EST) Received: from apache by megatron.ietf.org with local (Exim 4.32) id 1CZaBE-0001uh-3Z; Wed, 01 Dec 2004 14:30:24 -0500 X-test-idtracker: no To: IETF-Announce From: The IESG Message-Id: Date: Wed, 01 Dec 2004 14:30:24 -0500 Cc: mpls@ietf.org Subject: [mpls] Last Call: 'Encoding of Attributes for Multiprotocol Label Switching (MPLS) Label Switched Path (LSP) Establishment Using RSVP-TE' 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@ietf.org Errors-To: mpls-bounces@ietf.org X-Spam-Score: 0.0 (/) X-Scan-Signature: d6b246023072368de71562c0ab503126 The IESG has received a request from the Multiprotocol Label Switching WG to consider the following document: - 'Encoding of Attributes for Multiprotocol Label Switching (MPLS) Label Switched Path (LSP) Establishment Using RSVP-TE ' 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 2004-12-15. The file can be obtained via http://www.ietf.org/internet-drafts/draft-ietf-mpls-rsvpte-attributes-04.txt _______________________________________________ mpls mailing list mpls@lists.ietf.org https://www1.ietf.org/mailman/listinfo/mpls From mpls-bounces@ietf.org Mon Dec 6 06:45:15 2004 Received: from ietf-mx.ietf.org (ietf-mx.ietf.org [132.151.6.1]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id GAA27022; Mon, 6 Dec 2004 06:45:14 -0500 (EST) Received: from megatron.ietf.org ([132.151.6.71]) by ietf-mx.ietf.org with esmtp (Exim 4.33) id 1CbHPC-0000Cm-An; Mon, 06 Dec 2004 06:51:51 -0500 Received: from localhost.localdomain ([127.0.0.1] helo=megatron.ietf.org) by megatron.ietf.org with esmtp (Exim 4.32) id 1CbHGL-0005jz-PW; Mon, 06 Dec 2004 06:42:41 -0500 Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org) by megatron.ietf.org with esmtp (Exim 4.32) id 1CbHER-0005Gv-3P for mpls@megatron.ietf.org; Mon, 06 Dec 2004 06:40:43 -0500 Received: from ietf-mx.ietf.org (ietf-mx.ietf.org [132.151.6.1]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id GAA26141 for ; Mon, 6 Dec 2004 06:40:40 -0500 (EST) From: E.T.Metz@telecom.tno.nl Received: from ds04.tnoase.telecom.tno.nl ([139.63.192.204] helo=ds04.telecom.tno.nl) by ietf-mx.ietf.org with esmtp (Exim 4.33) id 1CbHKm-0008VV-BG for mpls@ietf.org; Mon, 06 Dec 2004 06:47:16 -0500 Content-class: urn:content-classes:message MIME-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: quoted-printable X-MimeOLE: Produced By Microsoft Exchange V6.5.7226.0 Date: Mon, 6 Dec 2004 12:40:29 +0100 Message-ID: Thread-Topic: LSP ping TLV definition: copy-paste error? Thread-Index: AcTbiGKx6uVTm8/AQWCMCAxrMz1/vA== To: , X-Spam-Score: 0.3 (/) X-Scan-Signature: 08170828343bcf1325e4a0fb4584481c Content-Transfer-Encoding: quoted-printable Cc: mpls@ietf.org Subject: [mpls] LSP ping TLV definition: copy-paste error? 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@ietf.org Errors-To: mpls-bounces@ietf.org X-Spam-Score: 0.3 (/) X-Scan-Signature: 79899194edc4f33a41f49410777972f8 Content-Transfer-Encoding: quoted-printable Hi Kireeti/George, It looks like a copy-paste error got into the mandatory/optional TLV definition in the LSP ping draft (draft-ietf-mpls-lsp-ping-07.txt): "Types with the high order bit not set (i.e., 1) are mandatory TLVs ..." "Types with the high order bit not set (i.e., 0) are optional TLVs ..." Probably should be: "Types with the high order bit not set (i.e., 0) are mandatory TLVs ..." "Types with the high order bit set (i.e., 1) are optional TLVs ..." cheers, Eduard _______________________________________________ mpls mailing list mpls@lists.ietf.org https://www1.ietf.org/mailman/listinfo/mpls From mpls-bounces@ietf.org Tue Dec 7 10:36:46 2004 Received: from ietf-mx.ietf.org (ietf-mx.ietf.org [132.151.6.1]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id KAA14379; Tue, 7 Dec 2004 10:36:46 -0500 (EST) Received: from megatron.ietf.org ([132.151.6.71]) by ietf-mx.ietf.org with esmtp (Exim 4.33) id 1CbhV2-0006f9-Dw; Tue, 07 Dec 2004 10:43:37 -0500 Received: from localhost.localdomain ([127.0.0.1] helo=megatron.ietf.org) by megatron.ietf.org with esmtp (Exim 4.32) id 1CbhCs-0005Xo-O0; Tue, 07 Dec 2004 10:24:50 -0500 Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org) by megatron.ietf.org with esmtp (Exim 4.32) id 1Cbh4J-00030i-Rk for mpls@megatron.ietf.org; Tue, 07 Dec 2004 10:16:00 -0500 Received: from ietf-mx.ietf.org (ietf-mx.ietf.org [132.151.6.1]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id KAA12106 for ; Tue, 7 Dec 2004 10:15:57 -0500 (EST) Received: from natint3.juniper.net ([66.129.224.36] helo=kummer.juniper.net) by ietf-mx.ietf.org with esmtp (Exim 4.33) id 1CbhAt-0006D7-3V for mpls@ietf.org; Tue, 07 Dec 2004 10:22:48 -0500 Received: from kummer.juniper.net (localhost [127.0.0.1]) by kummer.juniper.net (8.12.8p1/8.12.3) with ESMTP id iB7FFQXg055666; Tue, 7 Dec 2004 07:15:26 -0800 (PST) (envelope-from kireeti@juniper.net) Received: from localhost (kireeti@localhost) by kummer.juniper.net (8.12.8p1/8.12.3/Submit) with ESMTP id iB7FFHSu055663; Tue, 7 Dec 2004 07:15:26 -0800 (PST) X-Authentication-Warning: kummer.juniper.net: kireeti owned process doing -bs Date: Tue, 7 Dec 2004 07:15:17 -0800 (PST) From: Kireeti Kompella To: E.T.Metz@telecom.tno.nl In-Reply-To: Message-ID: <20041207071352.B55440@kummer.juniper.net> References: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII X-Spam-Score: 0.0 (/) X-Scan-Signature: 856eb5f76e7a34990d1d457d8e8e5b7f Cc: mpls@ietf.org Subject: [mpls] Re: LSP ping TLV definition: copy-paste error? 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@ietf.org Errors-To: mpls-bounces@ietf.org X-Spam-Score: 0.0 (/) X-Scan-Signature: 7655788c23eb79e336f5f8ba8bce7906 Hi Eduard, On Mon, 6 Dec 2004 E.T.Metz@telecom.tno.nl wrote: > It looks like a copy-paste error got into the mandatory/optional TLV > definition in the LSP ping draft (draft-ietf-mpls-lsp-ping-07.txt): > > "Types with the high order bit not set (i.e., 1) are mandatory TLVs ..." > "Types with the high order bit not set (i.e., 0) are optional TLVs ..." > > Probably should be: > "Types with the high order bit not set (i.e., 0) are mandatory TLVs ..." > "Types with the high order bit set (i.e., 1) are optional TLVs ..." Good catch! Will fix in the next version (you are right). Kireeti. ------- _______________________________________________ mpls mailing list mpls@lists.ietf.org https://www1.ietf.org/mailman/listinfo/mpls From mpls-bounces@ietf.org Tue Dec 7 12:57:15 2004 Received: from ietf-mx.ietf.org (ietf-mx.ietf.org [132.151.6.1]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id MAA29727; Tue, 7 Dec 2004 12:57:14 -0500 (EST) Received: from megatron.ietf.org ([132.151.6.71]) by ietf-mx.ietf.org with esmtp (Exim 4.33) id 1Cbjgh-0001lJ-GT; Tue, 07 Dec 2004 13:04:08 -0500 Received: from localhost.localdomain ([127.0.0.1] helo=megatron.ietf.org) by megatron.ietf.org with esmtp (Exim 4.32) id 1CbjWR-0000P3-SO; Tue, 07 Dec 2004 12:53:11 -0500 Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org) by megatron.ietf.org with esmtp (Exim 4.32) id 1CbjKk-0006E1-Jy for mpls@megatron.ietf.org; Tue, 07 Dec 2004 12:41:07 -0500 Received: from EXECDSL.COM (ns.execdsl.net [208.184.15.238]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id MAA28288 for ; Tue, 7 Dec 2004 12:41:03 -0500 (EST) Received: from [64.254.114.114] (HELO JLaptop.stevecrocker.com) by EXECDSL.COM (CommuniGate Pro SMTP 3.3) with ESMTP id 8160205; Tue, 07 Dec 2004 12:41:02 -0500 Message-Id: <6.1.2.0.0.20041207111453.03e2ed38@localhost> X-Sender: joel@stevecrocker.com@localhost X-Mailer: QUALCOMM Windows Eudora Version 6.1.2.0 Date: Tue, 07 Dec 2004 12:36:56 -0500 To: gen-art@alvestrand.no From: "Joel M. Halpern" In-Reply-To: <5E17B42A-485B-11D9-8830-000393CC2112@psg.com> References: <5E17B42A-485B-11D9-8830-000393CC2112@psg.com> Mime-Version: 1.0 Content-Type: text/plain; charset="us-ascii"; format=flowed Cc: dimitri.papadimitriou@alcatel.be, mpls@ietf.org, jpv@cisco.com Subject: [mpls] Re: Last Call Assignment: draft-ietf-mpls-rsvpte-attributes-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@ietf.org Errors-To: mpls-bounces@ietf.org X-Spam-Score: 0.0 (/) X-Scan-Signature: 50a516d93fd399dc60588708fd9a3002 [This is a General Area review at last call.] This draft is basically ready for publication as a Proposed Standard, but has nits that should be fixed before publication. IANA Considerations: The document identifies two new spaces for the IANA to manage. It lists the properties of relevance to values in these spaces. However, it does not indicate what procedure is to be followed for assigning values in these registries. Are they to be assigned only by IETF Standards Track RFCs? Are they assigned simply on a first-come, first-served basis with sufficient documentation? Minor comments: The document talks about several degrees or kinds of mandatory / optional information, ranging from information that must be examined at every node to information that only needs to be examined at the end-points. The specific example is given of information that needs to be examined at ABR/ASBRs, but should be deployable without upgrading all routers in the path. It is not clear that this stated goal is met by the solution provided. Some text on how the various cases listed are met by the documented method would be helpful. In section 7.3.1, there are two lines which confused me: The Attributes subobject is pushed onto the RECORD_ROUTE object immediately prior to pushing the node's IP address or link ... This means that an Attributes subobject is bound to the LSR identified by the subobject found in the RRO immediately before the Attributes subobject. The first sentence seems to say that when I parse the message I will find the Attributes subobject followed by the ID of the node which put it there. The later sentence seems to say that the Attributes subobject is bound to the ID which precedes it, rather than the ID which follows it? At 09:22 AM 12/7/2004, you wrote: >- Joel Halpern > 'Encoding of Attributes for Multiprotocol Label Switching (MPLS) >Label > Switched Path (LSP) Establishment Using RSVP-TE ' > as a Proposed Standard _______________________________________________ mpls mailing list mpls@lists.ietf.org https://www1.ietf.org/mailman/listinfo/mpls From mpls-bounces@ietf.org Tue Dec 7 17:18:41 2004 Received: from ietf-mx.ietf.org (ietf-mx.ietf.org [132.151.6.1]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id RAA06167; Tue, 7 Dec 2004 17:18:41 -0500 (EST) Received: from megatron.ietf.org ([132.151.6.71]) by ietf-mx.ietf.org with esmtp (Exim 4.33) id 1Cbnm3-0002Pm-B7; Tue, 07 Dec 2004 17:25:36 -0500 Received: from localhost.localdomain ([127.0.0.1] helo=megatron.ietf.org) by megatron.ietf.org with esmtp (Exim 4.32) id 1CbnPk-0006Lr-DX; Tue, 07 Dec 2004 17:02:32 -0500 Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org) by megatron.ietf.org with esmtp (Exim 4.32) id 1CbnCY-0007JK-JI for mpls@megatron.ietf.org; Tue, 07 Dec 2004 16:48:54 -0500 Received: from ranger.systems.pipex.net (ranger.systems.pipex.net [62.241.162.32]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id QAA01514 for ; Tue, 7 Dec 2004 16:48:51 -0500 (EST) Received: from dnni.com (81-178-2-190.dsl.pipex.com [81.178.2.190]) by ranger.systems.pipex.net (Postfix) with ESMTP id DAAD5E000394; Tue, 7 Dec 2004 21:48:16 +0000 (GMT) Received: from Puppy ([217.158.145.173] RDNS failed) by dnni.com with Microsoft SMTPSVC(6.0.3790.211); Tue, 7 Dec 2004 21:48:18 +0000 Message-ID: <04c401c4dca6$934dd550$fd919ed9@Puppy> From: "Adrian Farrel" To: , "Joel M. Halpern" References: <5E17B42A-485B-11D9-8830-000393CC2112@psg.com> <6.1.2.0.0.20041207111453.03e2ed38@localhost> Date: Tue, 7 Dec 2004 21:48:51 -0000 MIME-Version: 1.0 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: 7bit X-Priority: 3 X-MSMail-Priority: Normal X-Mailer: Microsoft Outlook Express 6.00.2800.1158 X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2800.1165 X-OriginalArrivalTime: 07 Dec 2004 21:48:19.0678 (UTC) FILETIME=[774307E0:01C4DCA6] Content-Transfer-Encoding: 7bit Cc: mpls@ietf.org, jpv@cisco.com Subject: [mpls] Re: Last Call Assignment: draft-ietf-mpls-rsvpte-attributes-04.txt X-BeenThere: mpls@lists.ietf.org X-Mailman-Version: 2.1.5 Precedence: list Reply-To: Adrian Farrel List-Id: Multi-Protocol Label Switching WG List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Sender: mpls-bounces@ietf.org Errors-To: mpls-bounces@ietf.org X-Spam-Score: 0.1 (/) X-Scan-Signature: 7aafa0432175920a4b3e118e16c5cb64 Content-Transfer-Encoding: 7bit Joel, Excellent. Thank you. In line. Adrian > IANA Considerations: > The document identifies two new spaces for the IANA to manage. It > lists the properties of relevance to values in these spaces. However, it > does not indicate what procedure is to be followed for assigning values in > these registries. Are they to be assigned only by IETF Standards Track > RFCs? Are they assigned simply on a first-come, first-served basis with > sufficient documentation? Good catch. I never did get IANA sections right. We'll think about this and update the draft. > Minor comments: > > The document talks about several degrees or kinds of mandatory / optional > information, ranging from information that must be examined at every node > to information that only needs to be examined at the end-points. The > specific example is given of information that needs to be examined at > ABR/ASBRs, but should be deployable without upgrading all routers in the > path. It is not clear that this stated goal is met by the solution > provided. Some text on how the various cases listed are met by the > documented method would be helpful. Sure. We can do that. > In section 7.3.1, there are two lines which confused me: > The Attributes subobject is pushed onto the RECORD_ROUTE object > immediately prior to pushing the node's IP address or link > ... > This means that an Attributes subobject is bound to the LSR > identified by the subobject found in the RRO immediately before the > Attributes subobject. > The first sentence seems to say that when I parse the message I will find > the Attributes subobject followed by the ID of the node which put it there. > The later sentence seems to say that the Attributes subobject is bound to > the ID which precedes it, rather than the ID which follows it? No, RRO is described as a stack. So, that which you push first, you pop last. You receive an RRO and you add your sub-objects to the front. You add the Attributes sub-object first, then you add your node/link. _______________________________________________ mpls mailing list mpls@lists.ietf.org https://www1.ietf.org/mailman/listinfo/mpls From mpls-bounces@ietf.org Tue Dec 7 18:34:06 2004 Received: from ietf-mx.ietf.org (ietf-mx.ietf.org [132.151.6.1]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id SAA14641; Tue, 7 Dec 2004 18:34:05 -0500 (EST) Received: from megatron.ietf.org ([132.151.6.71]) by ietf-mx.ietf.org with esmtp (Exim 4.33) id 1Cbowj-0004N9-G1; Tue, 07 Dec 2004 18:41:02 -0500 Received: from localhost.localdomain ([127.0.0.1] helo=megatron.ietf.org) by megatron.ietf.org with esmtp (Exim 4.32) id 1CboZW-0003Ri-NN; Tue, 07 Dec 2004 18:16:42 -0500 Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org) by megatron.ietf.org with esmtp (Exim 4.32) id 1CboIl-00087m-N9 for mpls@megatron.ietf.org; Tue, 07 Dec 2004 17:59:23 -0500 Received: from EXECDSL.COM (ns.execdsl.net [208.184.15.238]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id RAA10292 for ; Tue, 7 Dec 2004 17:59:20 -0500 (EST) Received: from [64.254.114.114] (HELO JLaptop.stevecrocker.com) by EXECDSL.COM (CommuniGate Pro SMTP 3.3) with ESMTP id 8163028; Tue, 07 Dec 2004 17:59:22 -0500 Message-Id: <6.1.2.0.0.20041207175414.04045830@localhost> X-Sender: joel@stevecrocker.com@localhost X-Mailer: QUALCOMM Windows Eudora Version 6.1.2.0 Date: Tue, 07 Dec 2004 17:55:59 -0500 To: "Adrian Farrel" , From: "Joel M. Halpern" In-Reply-To: <04c401c4dca6$934dd550$fd919ed9@Puppy> References: <5E17B42A-485B-11D9-8830-000393CC2112@psg.com> <6.1.2.0.0.20041207111453.03e2ed38@localhost> <04c401c4dca6$934dd550$fd919ed9@Puppy> Mime-Version: 1.0 Content-Type: text/plain; charset="us-ascii"; format=flowed Cc: mpls@ietf.org, jpv@cisco.com Subject: [mpls] Re: Last Call Assignment: draft-ietf-mpls-rsvpte-attributes-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@ietf.org Errors-To: mpls-bounces@ietf.org X-Spam-Score: 0.0 (/) X-Scan-Signature: b19722fc8d3865b147c75ae2495625f2 The description you provide makes sense. I am afraid that a reader who is not sufficiently involved in RRO work may well not understand what is meant. If you could elaborate the second sentence (the one with "the RRO immediately before") just a bit, it would probably help. Yours, Joel At 04:48 PM 12/7/2004, Adrian Farrel wrote: > > In section 7.3.1, there are two lines which confused me: > > The Attributes subobject is pushed onto the RECORD_ROUTE object > > immediately prior to pushing the node's IP address or link > > ... > > This means that an Attributes subobject is bound to the LSR > > identified by the subobject found in the RRO immediately before the > > Attributes subobject. > > The first sentence seems to say that when I parse the message I will find > > the Attributes subobject followed by the ID of the node which put it there. > > The later sentence seems to say that the Attributes subobject is bound to > > the ID which precedes it, rather than the ID which follows it? > >No, RRO is described as a stack. So, that which you push first, you pop last. > >You receive an RRO and you add your sub-objects to the front. You add the >Attributes >sub-object first, then you add your node/link. _______________________________________________ mpls mailing list mpls@lists.ietf.org https://www1.ietf.org/mailman/listinfo/mpls From mpls-bounces@ietf.org Wed Dec 8 07:52:00 2004 Received: from ietf-mx.ietf.org (ietf-mx.ietf.org [132.151.6.1]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id HAA19281; Wed, 8 Dec 2004 07:52:00 -0500 (EST) Received: from megatron.ietf.org ([132.151.6.71]) by ietf-mx.ietf.org with esmtp (Exim 4.33) id 1Cc1PJ-0004Bs-Ri; Wed, 08 Dec 2004 07:59:02 -0500 Received: from localhost.localdomain ([127.0.0.1] helo=megatron.ietf.org) by megatron.ietf.org with esmtp (Exim 4.32) id 1Cc1GH-0000hA-4Z; Wed, 08 Dec 2004 07:49:41 -0500 Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org) by megatron.ietf.org with esmtp (Exim 4.32) id 1Cc1CH-0008Gi-Ts for mpls@megatron.ietf.org; Wed, 08 Dec 2004 07:45:36 -0500 Received: from galaxy.systems.pipex.net (galaxy.systems.pipex.net [62.241.162.31]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id HAA18947 for ; Wed, 8 Dec 2004 07:45:31 -0500 (EST) Received: from dnni.com (81-178-2-190.dsl.pipex.com [81.178.2.190]) by galaxy.systems.pipex.net (Postfix) with ESMTP id A577EE000327; Wed, 8 Dec 2004 12:44:48 +0000 (GMT) Received: from Puppy ([217.158.145.168] RDNS failed) by dnni.com with Microsoft SMTPSVC(6.0.3790.211); Wed, 8 Dec 2004 12:44:52 +0000 Message-ID: <04e401c4dd23$d1add200$fd919ed9@Puppy> From: "Adrian Farrel" To: , "Joel M. Halpern" References: <5E17B42A-485B-11D9-8830-000393CC2112@psg.com> <6.1.2.0.0.20041207111453.03e2ed38@localhost> <04c401c4dca6$934dd550$fd919ed9@Puppy> <6.1.2.0.0.20041207175414.04045830@localhost> Date: Wed, 8 Dec 2004 12:39:47 -0000 MIME-Version: 1.0 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: 7bit X-Priority: 3 X-MSMail-Priority: Normal X-Mailer: Microsoft Outlook Express 6.00.2800.1158 X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2800.1165 X-OriginalArrivalTime: 08 Dec 2004 12:44:53.0389 (UTC) FILETIME=[B6CFEBD0:01C4DD23] Content-Transfer-Encoding: 7bit Cc: mpls@ietf.org, jpv@cisco.com Subject: [mpls] Re: Last Call Assignment: draft-ietf-mpls-rsvpte-attributes-04.txt X-BeenThere: mpls@lists.ietf.org X-Mailman-Version: 2.1.5 Precedence: list Reply-To: Adrian Farrel List-Id: Multi-Protocol Label Switching WG List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Sender: mpls-bounces@ietf.org Errors-To: mpls-bounces@ietf.org X-Spam-Score: 0.1 (/) X-Scan-Signature: 0ddefe323dd869ab027dbfff7eff0465 Content-Transfer-Encoding: 7bit OK, we can do that (although in fairness, anyone not familiar with the RRO should really not be playing with LSP Attributes!). A ----- Original Message ----- From: "Joel M. Halpern" To: "Adrian Farrel" ; Cc: "Dimitri Papadimitriou" ; ; "Arthi Ayyangar" ; ; "Alex Zinin" ; "George Swallow" ; "Loa Andersson" Sent: Tuesday, December 07, 2004 10:55 PM Subject: Re: Last Call Assignment: draft-ietf-mpls-rsvpte-attributes-04.txt > The description you provide makes sense. > I am afraid that a reader who is not sufficiently involved in RRO work may > well not understand what is meant. If you could elaborate the second > sentence (the one with "the RRO immediately before") just a bit, it would > probably help. > > Yours, > Joel > > At 04:48 PM 12/7/2004, Adrian Farrel wrote: > > > In section 7.3.1, there are two lines which confused me: > > > The Attributes subobject is pushed onto the RECORD_ROUTE object > > > immediately prior to pushing the node's IP address or link > > > ... > > > This means that an Attributes subobject is bound to the LSR > > > identified by the subobject found in the RRO immediately before the > > > Attributes subobject. > > > The first sentence seems to say that when I parse the message I will find > > > the Attributes subobject followed by the ID of the node which put it there. > > > The later sentence seems to say that the Attributes subobject is bound to > > > the ID which precedes it, rather than the ID which follows it? > > > >No, RRO is described as a stack. So, that which you push first, you pop last. > > > >You receive an RRO and you add your sub-objects to the front. You add the > >Attributes > >sub-object first, then you add your node/link. > > > _______________________________________________ mpls mailing list mpls@lists.ietf.org https://www1.ietf.org/mailman/listinfo/mpls From mpls-bounces@ietf.org Thu Dec 9 11:38:06 2004 Received: from ietf-mx.ietf.org (ietf-mx.ietf.org [132.151.6.1]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id LAA08743; Thu, 9 Dec 2004 11:38:05 -0500 (EST) Received: from megatron.ietf.org ([132.151.6.71]) by ietf-mx.ietf.org with esmtp (Exim 4.33) id 1CcRPu-0000xI-SO; Thu, 09 Dec 2004 11:45:23 -0500 Received: from localhost.localdomain ([127.0.0.1] helo=megatron.ietf.org) by megatron.ietf.org with esmtp (Exim 4.32) id 1CcRAo-00027Y-I7; Thu, 09 Dec 2004 11:29:46 -0500 Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org) by megatron.ietf.org with esmtp (Exim 4.32) id 1CcR6o-0007sw-Fw for mpls@megatron.ietf.org; Thu, 09 Dec 2004 11:25:38 -0500 Received: from ietf-mx.ietf.org (ietf-mx.ietf.org [132.151.6.1]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id LAA07061 for ; Thu, 9 Dec 2004 11:25:36 -0500 (EST) From: kurien_joseph@agilent.com Received: from msgbas1tx.cos.agilent.com ([192.25.240.37] helo=msgbas2x.cos.agilent.com) by ietf-mx.ietf.org with esmtp (Exim 4.33) id 1CcRDm-0000Wa-LN for mpls@ietf.org; Thu, 09 Dec 2004 11:32:53 -0500 Received: from pf-enccos5.cos.agilent.com (enccos5.cos.agilent.com [130.29.152.94]) by msgbas2x.cos.agilent.com (Postfix) with ESMTP id 89C667A5B for ; Thu, 9 Dec 2004 09:25:33 -0700 (MST) Received: from enccos5.cos.agilent.com (localhost.localdomain [127.0.0.1]) by localhost.enccos5.cos.agilent.com (Postfix) with SMTP id 9C483C0C6 for ; Thu, 9 Dec 2004 09:25:32 -0700 (MST) Received: from relcos1.cos.agilent.com (130.29.152.239) by enccos5.cos.agilent.com (Sigaba Gateway v3.83) with ESMTP id 7662566; Thu, 09 Dec 2004 09:25:32 -0700 Received: from wcosvs03.cos.agilent.com (wcosvs03.cos.agilent.com [130.29.152.233]) by relcos1.cos.agilent.com (Postfix) with ESMTP id 9352B40 for ; Thu, 9 Dec 2004 09:25:31 -0700 (MST) Received: from wcosbh23.cos.agilent.com ([130.29.152.145]) by wcosvs03.cos.agilent.com with InterScan Messaging Security Suite; Thu, 09 Dec 2004 09:25:30 -0700 Received: from wcosmb02.cos.agilent.com ([130.29.152.96]) by wcosbh23.cos.agilent.com with Microsoft SMTPSVC(5.0.2195.6713); Thu, 9 Dec 2004 09:25:30 -0700 X-MimeOLE: Produced By Microsoft Exchange V6.0.6603.0 Content-class: urn:content-classes:message MIME-Version: 1.0 Date: Thu, 9 Dec 2004 09:25:27 -0700 Message-ID: <9AB7C093B52FEE4EB66BAE9BE58A327303307827@wcosmb02.cos.agilent.com> Thread-Topic: Applying Qos on VPNs Thread-Index: AcTeC7Cgcqbv4FHUQbK7fHyzKYWiCQ== To: X-OriginalArrivalTime: 09 Dec 2004 16:25:30.0537 (UTC) FILETIME=[B32E2990:01C4DE0B] X-Spam-Score: 0.4 (/) X-Scan-Signature: 848ed35f2a4fc0638fa89629cb640f48 Subject: [mpls] Applying Qos on VPNs 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="===============0513133349==" Sender: mpls-bounces@ietf.org Errors-To: mpls-bounces@ietf.org X-Spam-Score: 0.5 (/) X-Scan-Signature: f2984bf50fb52a9e56055f779793d783 This is a multi-part message in MIME format. --===============0513133349== Content-class: urn:content-classes:message Content-Type: multipart/alternative; boundary="----_=_NextPart_001_01C4DE0B.B117181B" This is a multi-part message in MIME format. ------_=_NextPart_001_01C4DE0B.B117181B Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: quoted-printable Can QoS be applied to Layer 3 MPLS VPNs in such a manner that, two customers connected to the same ingress PE router but offered two types of services like GoldVoIP and SilverVoIP and two TE tunnels having different Path options but terminating together on a common egress PE? =20 Since the Egress PE for the both VPNs is the same, is it possible to have VPN traffic classified and routed to different tunnels? =20 Could someone pass a link to any cisco or juniper configuration guide ? =20 Thanks Kurien =20 =20 R & D Engineer,=20 MPLS/VPN Assurance=20 OSSD,=20 Agilent Technologies.=20 Tel : 916 788 6678 ( TELNET 788 6678)=20 =20 ------_=_NextPart_001_01C4DE0B.B117181B Content-Type: text/html; charset="us-ascii" Content-Transfer-Encoding: quoted-printable

Can QoS be applied to Layer 3 MPLS VPNs in such a = manner that, two customers connected to the same ingress PE router but offered = two types of services like GoldVoIP and SilverVoIP and two TE tunnels having different Path options but terminating together on a common egress = PE?

Since the Egress PE for the both VPNs is the same, is = it possible to have VPN traffic classified and routed to different = tunnels?

Could someone pass a link to any cisco or juniper configuration guide ?

Thanks

Kurien

R & D Engineer,
MPLS/VPN Assurance
OSSD,
Agilent Technologies.

Tel : 916 788 6678 ( TELNET 788 6678)

------_=_NextPart_001_01C4DE0B.B117181B-- --===============0513133349== Content-Type: text/plain; charset="us-ascii" MIME-Version: 1.0 Content-Transfer-Encoding: 7bit Content-Disposition: inline Content-Transfer-Encoding: 7bit _______________________________________________ mpls mailing list mpls@lists.ietf.org https://www1.ietf.org/mailman/listinfo/mpls --===============0513133349==-- From mpls-bounces@ietf.org Thu Dec 9 12:42:35 2004 Received: from ietf-mx.ietf.org (ietf-mx.ietf.org [132.151.6.1]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id MAA13756; Thu, 9 Dec 2004 12:42:35 -0500 (EST) Received: from megatron.ietf.org ([132.151.6.71]) by ietf-mx.ietf.org with esmtp (Exim 4.33) id 1CcSQI-0002Ka-4N; Thu, 09 Dec 2004 12:49:53 -0500 Received: from localhost.localdomain ([127.0.0.1] helo=megatron.ietf.org) by megatron.ietf.org with esmtp (Exim 4.32) id 1CcS2V-0004Q8-Jd; Thu, 09 Dec 2004 12:25:15 -0500 Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org) by megatron.ietf.org with esmtp (Exim 4.32) id 1CcRu3-0000Da-4q for mpls@megatron.ietf.org; Thu, 09 Dec 2004 12:16:31 -0500 Received: from ietf-mx.ietf.org (ietf-mx.ietf.org [132.151.6.1]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id MAA11585 for ; Thu, 9 Dec 2004 12:16:28 -0500 (EST) From: kurien_joseph@agilent.com Received: from msgbas1x.cos.agilent.com ([192.25.240.36]) by ietf-mx.ietf.org with esmtp (Exim 4.33) id 1CcS0r-0001iF-8N for mpls@ietf.org; Thu, 09 Dec 2004 12:23:46 -0500 Received: from pf-enccos5.cos.agilent.com (enccos5.cos.agilent.com [130.29.152.94]) by msgbas1x.cos.agilent.com (Postfix) with ESMTP id D770C21A27 for ; Thu, 9 Dec 2004 10:16:15 -0700 (MST) Received: from enccos5.cos.agilent.com (localhost.localdomain [127.0.0.1]) by localhost.enccos5.cos.agilent.com (Postfix) with SMTP id A88A7C0C6 for ; Thu, 9 Dec 2004 10:16:15 -0700 (MST) Received: from relcos2.cos.agilent.com (130.29.152.237) by enccos5.cos.agilent.com (Sigaba Gateway v3.83) with ESMTP id 7669492; Thu, 09 Dec 2004 10:16:15 -0700 Received: from wcosvs03.cos.agilent.com (wcosvs03.cos.agilent.com [130.29.152.233]) by relcos2.cos.agilent.com (Postfix) with ESMTP id 7F6CC30 for ; Thu, 9 Dec 2004 10:16:15 -0700 (MST) Received: from wcosbh22.cos.agilent.com ([130.29.152.178]) by wcosvs03.cos.agilent.com with InterScan Messaging Security Suite; Thu, 09 Dec 2004 10:16:14 -0700 Received: from wcosmb02.cos.agilent.com ([130.29.152.96]) by wcosbh22.cos.agilent.com with Microsoft SMTPSVC(5.0.2195.6713); Thu, 9 Dec 2004 10:16:14 -0700 X-MimeOLE: Produced By Microsoft Exchange V6.0.6603.0 Content-class: urn:content-classes:message MIME-Version: 1.0 Subject: RE: [mpls] Applying Qos on VPNs Date: Thu, 9 Dec 2004 10:16:13 -0700 Message-ID: <9AB7C093B52FEE4EB66BAE9BE58A327303307842@wcosmb02.cos.agilent.com> X-MS-Has-Attach: yes Thread-Topic: [mpls] Applying Qos on VPNs Thread-Index: AcTeC7Cgcqbv4FHUQbK7fHyzKYWiCQAAqhUAAAEW1wA= To: , X-OriginalArrivalTime: 09 Dec 2004 17:16:14.0150 (UTC) FILETIME=[C950A660:01C4DE12] X-Spam-Score: 0.5 (/) X-Scan-Signature: bfc9ec46aa2f66e5aee6a3bbffb0ebe9 Cc: mpls@ietf.org X-BeenThere: mpls@lists.ietf.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Multi-Protocol Label Switching WG List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Content-Type: multipart/mixed; boundary="===============1973655785==" Sender: mpls-bounces@ietf.org Errors-To: mpls-bounces@ietf.org X-Spam-Score: 2.3 (++) X-Scan-Signature: 8e140a89d08e89747ee196e282ac2228 This is a multi-part message in MIME format. --===============1973655785== Content-class: urn:content-classes:message Content-Type: multipart/related; boundary="----_=_NextPart_001_01C4DE12.C8C430E0"; type="multipart/alternative" This is a multi-part message in MIME format. ------_=_NextPart_001_01C4DE12.C8C430E0 Content-Type: multipart/alternative; boundary="----_=_NextPart_002_01C4DE12.C8C430E0" ------_=_NextPart_002_01C4DE12.C8C430E0 Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: quoted-printable Does it imply that the CEs linked to the ingress PE would send IP packet's TOS field to mark a QoS service. And additionally the PE would lookup the TOS field on all its inbound CE interfaces and mark EXP bit and forward them to any of the TE tunnels that which may have an EXP bit mapping? =20 Thanks Kurien =20 =20 _____ =20 From: jordan.britnell@bell.ca [mailto:jordan.britnell@bell.ca]=20 Sent: Thursday, December 09, 2004 8:46 AM To: kurien_joseph@agilent.com Subject: RE: [mpls] Applying Qos on VPNs =20 Absolutely. You can use half-duplex VRF routing as well as MPLS experimental bits to define how you would like traffic from a customer to be handled. A search on Cisco's site will show you the necessary steps.=20 =20 Jordan Britnell, CCNA IP Technology Research BCE/Bell Canada (416) 215-3729 jordan.britnell@bell.ca =20 -----Original Message----- From: mpls-bounces@lists.ietf.org [mailto:mpls-bounces@lists.ietf.org] On Behalf Of kurien_joseph@agilent.com Sent: December 9, 2004 11:25 AM To: mpls@ietf.org Subject: [mpls] Applying Qos on VPNs =20 Can QoS be applied to Layer 3 MPLS VPNs in such a manner that, two customers connected to the same ingress PE router but offered two types of services like GoldVoIP and SilverVoIP and two TE tunnels having different Path options but terminating together on a common egress PE? =20 Since the Egress PE for the both VPNs is the same, is it possible to have VPN traffic classified and routed to different tunnels? =20 Could someone pass a link to any cisco or juniper configuration guide ? =20 Thanks Kurien =20 =20 R & D Engineer,=20 MPLS/VPN Assurance=20 OSSD,=20 Agilent Technologies.=20 Tel : 916 788 6678 ( TELNET 788 6678)=20 =20 ------_=_NextPart_002_01C4DE12.C8C430E0 Content-Type: text/html; charset="us-ascii" Content-Transfer-Encoding: quoted-printable

Does it imply that the CEs linked = to the ingress PE would send IP packet’s TOS field to mark a QoS = service.

And additionally the PE would = lookup the TOS field on all its inbound CE interfaces and mark EXP bit and forward = them to any of the TE tunnels that which may have an EXP bit = mapping?

Thanks

Kurien

From: jordan.britnell@bell.ca [mailto:jordan.britnell@bell.ca]
Sent: Thursday, December = 09, 2004 8:46 AM
To: = kurien_joseph@agilent.com
Subject: RE: [mpls] = Applying Qos on VPNs

Absolutely. You = can use half-duplex VRF routing as well as MPLS experimental bits to define how = you would like traffic from a customer to be handled. A search on = Cisco’s site will show you the necessary steps.

Jordan Britnell, CCNA

IP Technology Research

BCE/Bell Canada

(416) 215-3729

jordan.britnell@bell.ca

-----Original = Message-----
From: = mpls-bounces@lists.ietf.org [mailto:mpls-bounces@lists.ietf.org] On Behalf Of kurien_joseph@agilent.com
Sent: December 9, 2004 = 11:25 AM
To: mpls@ietf.org
Subject: [mpls] Applying = Qos on VPNs

Can QoS be applied to Layer = 3 MPLS VPNs in such a manner that, two customers connected to the same ingress = PE router but offered two types of services like GoldVoIP and SilverVoIP = and two TE tunnels having different Path options but terminating together on a = common egress PE?

Since the Egress PE for the = both VPNs is the same, is it possible to have VPN traffic classified and = routed to different tunnels?

Could someone pass a link = to any cisco or juniper configuration guide ?

Thanks

Kurien

R & D Engineer,
MPLS/VPN Assurance
OSSD,
Agilent Technologies.

Tel : 916 788 6678 ( TELNET 788 = 6678)

------_=_NextPart_002_01C4DE12.C8C430E0-- ------_=_NextPart_001_01C4DE12.C8C430E0 Content-Type: image/gif; name="image001.gif" Content-Transfer-Encoding: base64 Content-ID: Content-Description: image001.gif Content-Location: image001.gif Content-Transfer-Encoding: base64 Content-Transfer-Encoding: base64 R0lGODlhOQFQAHcAMSH/C01TT0ZGSUNFOS4wDQAAAAFzUkdCAK7OHOkAIf8LTVNPRkZJQ0U5LjAX AAAAC21zT1BNU09GRklDRTkuMEI8pPUAIf8LTVNPRkZJQ0U5LjAVAAAACXBIWXMAAA7EAAAOwwHa apjcACwAAAAAOQFQAIcAAAD////+/v7+7J/+3FD+9c/+zxD+zAD++d/+76/+5X/+0iD+32D+8r/+ 2UD+/O/+4nD+1jD+6Y/v7/W/v9nPz+Lf3+x/f7IAAGYwMINwcKlAQIxgYKCvr8+Pj7yfn8UgIHkQ EHBQUJYAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAA AAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAA AAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAA AAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAA AAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAA AAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAA AAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAA AAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAA AAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAA AAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAA AAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAA AAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAI/wAFCBxIsKDBgwgTKlzI sKHDhxAjSpxIsaLFixgzatzIsaPHjyBDihxJsqTJkyhTqlzJsqXLlzBjypxJs6bNmzhz6tzJs6fP n0CDCh1KtKjRo0iTKl3KtKnTp1CjSp1KtarVq1izat3KtavXr2DDchxAQKzZsw0LGDiAAK3btwMT HDigAK5dtGsX3N0blsHcBHwDP23QYIACBQ4SHxgwsMDcsoIjB33QIIECCA4izN3M+QCDggvmtpVM uiZlwwQcdO6c+DDh0QUhzJVQunbLBhIwr1091wEBBQMaPHgomy1hwhIOK1eQOrFzBxCWS3htu/pB ysxD8zYAfTpsiY55i/8fLz7C7wbWSReQwED76u7CGZ5W8N2gX97Pnf9ezvy5ZvEGKDBcenCtR8Bu nHGnQAL1HYRAAwow4ACCBizUwGYFaFSAZf9tFgGBaCXQ3nsQMMgQbpjh9xtjC6lGl0fhbQZiWCIi 2JsC6CmEHQHuzWUecPFBdOEBFXZ031yfzcjVAwr0uAADCQyI0HojevhbAhlipB2LGD0gQY8QKLkV kxQykCNCELp4wAIOLJhlRwPMpZdFDwxwZG9ninlVAe4FKGVBXh54gAMMTPcnSA9gONF6am5mpp5a IUDhm9cBR2lJA2i3QIMIYTfhagQMcCikVinAGWQ1IfDYpQfhxkCHnD3/KSqpXQ25GQGAcfSgZZiN ypBfYRq0YXbiycoprVoNYGNv0R2XEGXHJRdhYsuuGVGdmjkwHwGwdqZglMiihYAE3ZJnboKtLRhk Qwk0ai6hOPoaLlrYIabYeNw5Fx2Q68pH2GGpVctam97Na/BDD+J2GbXmRuCiA4TJe/DBBfy7cGbk senbYdM1AFtxuU4sMkHdOpzYfvz2u9BatI3sMklzvSwzRnmCdkDNM+fc0IUGMDAAbAUQMBfOOlc3 AQVIJ6200hVIhAADAvsokAVLU9D00VVPEBPSWr9FtQVXXYDB2GSXbfbYGWhAwUMPJKDbXNxJMOAG Z3MgQAdnYwC2RBZc/3DB3gdN4DfgCo29tkEXbND0RxooblEFG2ggktgXNNR45Bp4IIAGHwRFd96g l213RhPk3TkHZ2dAEQVjj36Q2BgcvpDhB7UO0tiVT905RLBPjkHuDPktwAYglA58T6WfHcIGzBMf egcZ4X221iCcLflErI9N+EAThEA7Q98X5IHjjJOffUSQXw8S5Q4Jv4EIHIigfk/Sm605QRZkYHrg FHjg9/8X6MD2BII6s6nOAnmTXUSy97vXkU2BCQkfS85XE/Y1RHgg+AAGPrABoBTQbIsjyOfKFoKu CaQCGqhe6DCQwYKosGyV84DyKsI6EWCghAYJAQi8JzsLeEAEG/gbQf++J7iufeACh+vbBybgAQ4E cXtMdKIHJnDEAQqgigKgQAH9truCaPGJU7tAFwf3RSEyUQQi6KIAlHhFJwpxIBY8YeI4oMYsru0C VLRAHXfyQrKFQGkdSKHyQmiBEa6QbBnoWgUSKAAbmk0ENMTABvR3vCtiQIaxE0gHvJcBFUJPIN+z YQeH18AssrCPIQBcBbznx+pBUCB0u6PZRkkQDdyQbiEQCOtoiTYSeoCVY6Ml6zKgv7KNsZSbM+BS FnnIvIEAjwP5ADDHFoI3UnGaGLgeJkkIyrPt8SG71CAIXFjC71VABHuz4Ti7uTbUJRKWpcxeBsC2 SgyMrnuX1CUrX0n/ysNRsHYY0BrVdCnJgVBzbfW0p9Ywubjs/VEgsDucBTX40Ano75tD2WYzEflG U5otBCGEo9nW6ciyQbJ+ZbOiQ3YpgOp1UYOVk+BAmGnQ2LnThHTLXfZMKMNRio2WHuVnLAmKgQhu 0IsF7eYxAzoQShJVjXSDpAAsWL373S2pSDEk2ZrHvGKe7X59HBsIuNq8sBZVAPuzpTIj2UFxDmSH WpOgD71aU/29cyA5JShQWSqAixaEhwcZqkcT8rnj8RWtmdSrCOM5toJQFKINTJ4HlHbDpCRvrfjz akqZudHUXfVsYDPr/CTCUnxCD6bsFMgEChjExnZzbFaFp06xaspR/8pUsAUR7D8NMoHPbaBrhw3f YUk5W6AOdqoNZODZkoJSslVSICVNqXKdC8DqAhB6ai3bAfP2ydUl9actxSFiD0e3eXazprDrLnEV OxC+jk29LU1sbhO724NgcpTBle9w81pbpJ6Vfcw0IVOyW7aQZjG6W11j3p5LkAmYULSWXK5F+IpP 1AGPdgE+oWvHK0OQ4pWxe00q3eaHQPku1p8bToj0mpZf2e2XsUwdiC19WkrvYfQoZpUk87BpwK4R mGwg0EAAKdABv4lAf10rsdmgh2AMSJWtMqbmEDO5U+humHaoK55s2cveDgPOkUJNbIkFjL+arq3F 7aUtf7MHPHzuzv+CWRaw1lYrAjL7RMmdBTI0B/LLPKtOIBqUMI9jiz2slnh+tEteEEe4t0TbVWtr pi2F9ZfBDtgQsAbBrfc4QIFK2hKJl9Yamrm8Xo/akwIf0B8tLYjPDPYPBHbDJIN5otFmvu8CBube B0TA41latcmQnK72LjJc1BHue4G+4SaPOt4T6rBpkQ4xLXvrRw6a+MOykyY1CVeBF3q4v6kldbQJ rAETxrGQZdvAmd+LlqohjShU46dBVPqQeGtNf/LmLdcOUoF3b4Sl9m5IvAlnAXoXzSjJs7NMhntw sBgYdU+2CcMb3hUNZuB/+ktlTiZO8a1YgAPe5oDBYcLxjneFAgott8nRcm3ylrv85TCPucxnTvOa 2/zmOM+5znfO8577/OdAD7rQh070ohs9KwEBADs= ------_=_NextPart_001_01C4DE12.C8C430E0-- --===============1973655785== Content-Type: text/plain; charset="us-ascii" MIME-Version: 1.0 Content-Transfer-Encoding: 7bit Content-Disposition: inline Content-Transfer-Encoding: 7bit _______________________________________________ mpls mailing list mpls@lists.ietf.org https://www1.ietf.org/mailman/listinfo/mpls --===============1973655785==-- From mpls-bounces@ietf.org Thu Dec 9 12:45:26 2004 Received: from ietf-mx.ietf.org (ietf-mx.ietf.org [132.151.6.1]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id MAA14532; Thu, 9 Dec 2004 12:45:25 -0500 (EST) Received: from megatron.ietf.org ([132.151.6.71]) by ietf-mx.ietf.org with esmtp (Exim 4.33) id 1CcST3-0002Ri-KP; Thu, 09 Dec 2004 12:52:44 -0500 Received: from localhost.localdomain ([127.0.0.1] helo=megatron.ietf.org) by megatron.ietf.org with esmtp (Exim 4.32) id 1CcSAE-0006LW-Ko; Thu, 09 Dec 2004 12:33:14 -0500 Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org) by megatron.ietf.org with esmtp (Exim 4.32) id 1CcS20-00045o-N6 for mpls@megatron.ietf.org; Thu, 09 Dec 2004 12:24:44 -0500 Received: from ietf-mx.ietf.org (ietf-mx.ietf.org [132.151.6.1]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id MAA12218 for ; Thu, 9 Dec 2004 12:24:42 -0500 (EST) From: jordan.britnell@bell.ca Received: from bellwfep2-srv.bellnexxia.net ([207.236.237.108]) by ietf-mx.ietf.org with esmtp (Exim 4.33) id 1CcS91-0001to-Ip for mpls@ietf.org; Thu, 09 Dec 2004 12:32:00 -0500 Received: from dm3cn8.bell.ca ([206.47.0.145]) by bellwfep2-srv.bellnexxia.net (InterMail vM.5.01.06.10 201-253-122-130-110-20040306) with ESMTP id <20041209172412.PDKS1861.bellwfep2-srv.bellnexxia.net@dm3cn8.bell.ca>; Thu, 9 Dec 2004 12:24:12 -0500 Received: from 142.182.89.79dm3cn8.bell.ca with ESMTP (Tumbleweed MMS SMTP Relay (MMS v5.0)); Thu, 09 Dec 2004 12:24:06 -0500 X-Server-Uuid: D4A4E604-913A-4A1B-8C07-2866D92AD410 Received: from TOROONDC915.bell.corp.bce.ca ([142.182.89.18]) by TOROONDC918.bell.corp.bce.ca with Microsoft SMTPSVC(6.0.3790.211); Thu, 9 Dec 2004 12:24:06 -0500 X-MimeOLE: Produced By Microsoft Exchange V6.5.7226.0 Content-class: urn:content-classes:message MIME-Version: 1.0 Subject: RE: [mpls] Applying Qos on VPNs Date: Thu, 9 Dec 2004 12:24:05 -0500 Message-ID: <5BA2482D51EA8440B36B8329127619B8015F83A6@Toroondc915.bell.corp.bce.ca> X-MS-Has-Attach: yes Thread-Topic: [mpls] Applying Qos on VPNs Thread-Index: AcTeC7Cgcqbv4FHUQbK7fHyzKYWiCQAAqhUAAAEW1wAAAC5/4A== To: kurien_joseph@agilent.com X-OriginalArrivalTime: 09 Dec 2004 17:24:06.0388 (UTC) FILETIME=[E2CA7340:01C4DE13] X-WSS-ID: 6DA655BC513735-01-01 X-Spam-Score: 0.5 (/) X-Scan-Signature: 0634ec58aad05a6aa9ac7d4670be9c6c Cc: mpls@ietf.org X-BeenThere: mpls@lists.ietf.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Multi-Protocol Label Switching WG List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Content-Type: multipart/mixed; boundary="===============1429109088==" Sender: mpls-bounces@ietf.org Errors-To: mpls-bounces@ietf.org X-Spam-Score: 1.0 (+) X-Scan-Signature: 778b456acd32f555185589e04d062871 This is a multi-part message in MIME format. --===============1429109088== Content-class: urn:content-classes:message Content-Type: multipart/related; boundary="----_=_NextPart_001_01C4DE13.E27726AA"; type="multipart/alternative" This is a multi-part message in MIME format. ------_=_NextPart_001_01C4DE13.E27726AA Content-Type: multipart/alternative; boundary="----_=_NextPart_002_01C4DE13.E27726AA" ------_=_NextPart_002_01C4DE13.E27726AA Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: quoted-printable Sort of. The part up to tunnel lookup is correct. TOS stamping takes place on the CE along with some sort of rate limiting usually. Mapping the packets to tunnels would be done on a routing basis I believe. If I'm not mistaken you can also use half-duplex VRF to do this as well. As the CE TOS bit is encapsulated in the MPLS info the experimental bit will be used. Make sense? =20 Jordan Britnell, CCNA IP Technology Research BCE/Bell Canada (416) 215-3729 jordan.britnell@bell.ca =20 -----Original Message----- From: kurien_joseph@agilent.com [mailto:kurien_joseph@agilent.com]=20 Sent: December 9, 2004 12:16 PM To: Britnell, Jordan (5000008); kurien_joseph@agilent.com Cc: mpls@ietf.org Subject: RE: [mpls] Applying Qos on VPNs =20 Does it imply that the CEs linked to the ingress PE would send IP packet's TOS field to mark a QoS service. And additionally the PE would lookup the TOS field on all its inbound CE interfaces and mark EXP bit and forward them to any of the TE tunnels that which may have an EXP bit mapping? =20 Thanks Kurien =20 =20 ________________________________ From: jordan.britnell@bell.ca [mailto:jordan.britnell@bell.ca]=20 Sent: Thursday, December 09, 2004 8:46 AM To: kurien_joseph@agilent.com Subject: RE: [mpls] Applying Qos on VPNs =20 Absolutely. You can use half-duplex VRF routing as well as MPLS experimental bits to define how you would like traffic from a customer to be handled. A search on Cisco's site will show you the necessary steps.=20 =20 Jordan Britnell, CCNA IP Technology Research BCE/Bell Canada (416) 215-3729 jordan.britnell@bell.ca =20 -----Original Message----- From: mpls-bounces@lists.ietf.org [mailto:mpls-bounces@lists.ietf.org] On Behalf Of kurien_joseph@agilent.com Sent: December 9, 2004 11:25 AM To: mpls@ietf.org Subject: [mpls] Applying Qos on VPNs =20 Can QoS be applied to Layer 3 MPLS VPNs in such a manner that, two customers connected to the same ingress PE router but offered two types of services like GoldVoIP and SilverVoIP and two TE tunnels having different Path options but terminating together on a common egress PE? =20 Since the Egress PE for the both VPNs is the same, is it possible to have VPN traffic classified and routed to different tunnels? =20 Could someone pass a link to any cisco or juniper configuration guide ? =20 Thanks Kurien =20 =20 R & D Engineer,=20 MPLS/VPN Assurance=20 OSSD,=20 Agilent Technologies.=20 Tel : 916 788 6678 ( TELNET 788 6678)=20 =20 ------_=_NextPart_002_01C4DE13.E27726AA Content-Type: text/html; charset=us-ascii Content-Transfer-Encoding: quoted-printable

Sort of. The part up to tunnel = lookup is correct. TOS stamping takes place on the CE along with some sort of rate limiting usually. Mapping the packets to tunnels would be done on a = routing basis I believe. If I’m not mistaken you can also use half-duplex = VRF to do this as well. As the CE TOS bit is encapsulated in the MPLS info the experimental bit will be used. Make sense?

Jordan Britnell, CCNA

IP Technology Research

BCE/Bell Canada

(416) 215-3729

jordan.britnell@bell.ca

-----Original Message-----
From: = kurien_joseph@agilent.com [mailto:kurien_joseph@agilent.com]
Sent: December 9, 2004 = 12:16 PM
To: Britnell, Jordan (5000008); kurien_joseph@agilent.com
Cc: mpls@ietf.org
Subject: RE: [mpls] = Applying Qos on VPNs

Does it imply that the CEs linked to the ingress PE would = send IP packet’s TOS field to mark a QoS service.

And additionally the PE would lookup the TOS field on all = its inbound CE interfaces and mark EXP bit and forward them to any of the TE tunnels that which may have an EXP bit mapping?

Thanks

Kurien

From: jordan.britnell@bell.ca [mailto:jordan.britnell@bell.ca]
Sent: Thursday, December = 09, 2004 8:46 AM
To: = kurien_joseph@agilent.com
Subject: RE: [mpls] = Applying Qos on VPNs

Absolutely. You can use half-duplex VRF routing as well as MPLS experimental bits to = define how you would like traffic from a customer to be handled. A search on Cisco’s site will show you the necessary steps.

Jordan Britnell, CCNA

IP Technology Research

BCE/Bell Canada

(416) 215-3729

jordan.britnell@bell.ca

-----Original Message-----
From: = mpls-bounces@lists.ietf.org [mailto:mpls-bounces@lists.ietf.org] On Behalf Of kurien_joseph@agilent.com
Sent: December 9, 2004 = 11:25 AM
To: mpls@ietf.org
Subject: [mpls] Applying = Qos on VPNs

Can QoS be = applied to Layer 3 MPLS VPNs in such a manner that, two customers connected to the = same ingress PE router but offered two types of services like GoldVoIP and SilverVoIP and two TE tunnels having different Path options but = terminating together on a common egress PE?

Since the = Egress PE for the both VPNs is the same, is it possible to have VPN traffic classified = and routed to different tunnels?

Could someone = pass a link to any cisco or juniper configuration guide ?

Thanks

Kurien

R & D = Engineer,
MPLS/VPN Assurance =
OSSD,
Agilent Technologies.

Tel : 916 788 6678 ( TELNET = 788 6678)

------_=_NextPart_002_01C4DE13.E27726AA-- ------_=_NextPart_001_01C4DE13.E27726AA Content-Location: image001.gif Content-Type: image/gif; name=image001.gif Content-Transfer-Encoding: base64 Content-ID: Content-Description: image001.gif Content-Transfer-Encoding: base64 Content-Transfer-Encoding: base64 R0lGODlhOQFQAHcAMSH/C01TT0ZGSUNFOS4wDQAAAAFzUkdCAK7OHOkAIf8LTVNPRkZJQ0U5LjAX AAAAC21zT1BNU09GRklDRTkuMEI8pPUAIf8LTVNPRkZJQ0U5LjAVAAAACXBIWXMAAA7EAAAOwwHa apjcACwAAAAAOQFQAIcAAAD////+/v7+7J/+3FD+9c/+zxD+zAD++d/+76/+5X/+0iD+32D+8r/+ 2UD+/O/+4nD+1jD+6Y/v7/W/v9nPz+Lf3+x/f7IAAGYwMINwcKlAQIxgYKCvr8+Pj7yfn8UgIHkQ EHBQUJYAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAA AAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAA AAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAA AAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAA AAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAA AAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAA AAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAA AAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAA AAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAA AAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAA AAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAA AAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAI/wAFCBxIsKDBgwgTKlzI sKHDhxAjSpxIsaLFixgzatzIsaPHjyBDihxJsqTJkyhTqlzJsqXLlzBjypxJs6bNmzhz6tzJs6fP n0CDCh1KtKjRo0iTKl3KtKnTp1CjSp1KtarVq1izat3KtavXr2DDchxAQKzZsw0LGDiAAK3btwMT HDigAK5dtGsX3N0blsHcBHwDP23QYIACBQ4SHxgwsMDcsoIjB33QIIECCA4izN3M+QCDggvmtpVM uiZlwwQcdO6c+DDh0QUhzJVQunbLBhIwr1091wEBBQMaPHgomy1hwhIOK1eQOrFzBxCWS3htu/pB ysxD8zYAfTpsiY55i/8fLz7C7wbWSReQwED76u7CGZ5W8N2gX97Pnf9ezvy5ZvEGKDBcenCtR8Bu nHGnQAL1HYRAAwow4ACCBizUwGYFaFSAZf9tFgGBaCXQ3nsQMMgQbpjh9xtjC6lGl0fhbQZiWCIi 2JsC6CmEHQHuzWUecPFBdOEBFXZ031yfzcjVAwr0uAADCQyI0HojevhbAhlipB2LGD0gQY8QKLkV kxQykCNCELp4wAIOLJhlRwPMpZdFDwxwZG9ninlVAe4FKGVBXh54gAMMTPcnSA9gONF6am5mpp5a IUDhm9cBR2lJA2i3QIMIYTfhagQMcCikVinAGWQ1IfDYpQfhxkCHnD3/KSqpXQ25GQGAcfSgZZiN ypBfYRq0YXbiycoprVoNYGNv0R2XEGXHJRdhYsuuGVGdmjkwHwGwdqZglMiihYAE3ZJnboKtLRhk Qwk0ai6hOPoaLlrYIabYeNw5Fx2Q68pH2GGpVctam97Na/BDD+J2GbXmRuCiA4TJe/DBBfy7cGbk senbYdM1AFtxuU4sMkHdOpzYfvz2u9BatI3sMklzvSwzRnmCdkDNM+fc0IUGMDAAbAUQMBfOOlc3 AQVIJ6200hVIhAADAvsokAVLU9D00VVPEBPSWr9FtQVXXYDB2GSXbfbYGWhAwUMPJKDbXNxJMOAG Z3MgQAdnYwC2RBZc/3DB3gdN4DfgCo29tkEXbND0RxooblEFG2ggktgXNNR45Bp4IIAGHwRFd96g l213RhPk3TkHZ2dAEQVjj36Q2BgcvpDhB7UO0tiVT905RLBPjkHuDPktwAYglA58T6WfHcIGzBMf egcZ4X221iCcLflErI9N+EAThEA7Q98X5IHjjJOffUSQXw8S5Q4Jv4EIHIigfk/Sm605QRZkYHrg FHjg9/8X6MD2BII6s6nOAnmTXUSy97vXkU2BCQkfS85XE/Y1RHgg+AAGPrABoBTQbIsjyOfKFoKu CaQCGqhe6DCQwYKosGyV84DyKsI6EWCghAYJAQi8JzsLeEAEG/gbQf++J7iufeACh+vbBybgAQ4E cXtMdKIHJnDEAQqgigKgQAH9truCaPGJU7tAFwf3RSEyUQQi6KIAlHhFJwpxIBY8YeI4oMYsru0C VLRAHXfyQrKFQGkdSKHyQmiBEa6QbBnoWgUSKAAbmk0ENMTABvR3vCtiQIaxE0gHvJcBFUJPIN+z YQeH18AssrCPIQBcBbznx+pBUCB0u6PZRkkQDdyQbiEQCOtoiTYSeoCVY6Ml6zKgv7KNsZSbM+BS FnnIvIEAjwP5ADDHFoI3UnGaGLgeJkkIyrPt8SG71CAIXFjC71VABHuz4Ti7uTbUJRKWpcxeBsC2 SgyMrnuX1CUrX0n/ysNRsHYY0BrVdCnJgVBzbfW0p9Ywubjs/VEgsDucBTX40Ano75tD2WYzEflG U5otBCGEo9nW6ciyQbJ+ZbOiQ3YpgOp1UYOVk+BAmGnQ2LnThHTLXfZMKMNRio2WHuVnLAmKgQhu 0IsF7eYxAzoQShJVjXSDpAAsWL373S2pSDEk2ZrHvGKe7X59HBsIuNq8sBZVAPuzpTIj2UFxDmSH WpOgD71aU/29cyA5JShQWSqAixaEhwcZqkcT8rnj8RWtmdSrCOM5toJQFKINTJ4HlHbDpCRvrfjz akqZudHUXfVsYDPr/CTCUnxCD6bsFMgEChjExnZzbFaFp06xaspR/8pUsAUR7D8NMoHPbaBrhw3f YUk5W6AOdqoNZODZkoJSslVSICVNqXKdC8DqAhB6ai3bAfP2ydUl9actxSFiD0e3eXazprDrLnEV OxC+jk29LU1sbhO724NgcpTBle9w81pbpJ6Vfcw0IVOyW7aQZjG6W11j3p5LkAmYULSWXK5F+IpP 1AGPdgE+oWvHK0OQ4pWxe00q3eaHQPku1p8bToj0mpZf2e2XsUwdiC19WkrvYfQoZpUk87BpwK4R mGwg0EAAKdABv4lAf10rsdmgh2AMSJWtMqbmEDO5U+humHaoK55s2cveDgPOkUJNbIkFjL+arq3F 7aUtf7MHPHzuzv+CWRaw1lYrAjL7RMmdBTI0B/LLPKtOIBqUMI9jiz2slnh+tEteEEe4t0TbVWtr pi2F9ZfBDtgQsAbBrfc4QIFK2hKJl9Yamrm8Xo/akwIf0B8tLYjPDPYPBHbDJIN5otFmvu8CBube B0TA41latcmQnK72LjJc1BHue4G+4SaPOt4T6rBpkQ4xLXvrRw6a+MOykyY1CVeBF3q4v6kldbQJ rAETxrGQZdvAmd+LlqohjShU46dBVPqQeGtNf/LmLdcOUoF3b4Sl9m5IvAlnAXoXzSjJs7NMhntw sBgYdU+2CcMb3hUNZuB/+ktlTiZO8a1YgAPe5oDBYcLxjneFAgott8nRcm3ylrv85TCPucxnTvOa 2/zmOM+5znfO8577/OdAD7rQh070ohs9KwEBADs= ------_=_NextPart_001_01C4DE13.E27726AA-- --===============1429109088== Content-Type: text/plain; charset="us-ascii" MIME-Version: 1.0 Content-Transfer-Encoding: 7bit Content-Disposition: inline Content-Transfer-Encoding: 7bit _______________________________________________ mpls mailing list mpls@lists.ietf.org https://www1.ietf.org/mailman/listinfo/mpls --===============1429109088==-- From mpls-bounces@ietf.org Thu Dec 9 13:19:34 2004 Received: from ietf-mx.ietf.org (ietf-mx.ietf.org [132.151.6.1]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id NAA18011; Thu, 9 Dec 2004 13:19:34 -0500 (EST) Received: from megatron.ietf.org ([132.151.6.71]) by ietf-mx.ietf.org with esmtp (Exim 4.33) id 1CcT08-0003BY-Oe; Thu, 09 Dec 2004 13:26:53 -0500 Received: from localhost.localdomain ([127.0.0.1] helo=megatron.ietf.org) by megatron.ietf.org with esmtp (Exim 4.32) id 1CcSrZ-000091-IR; Thu, 09 Dec 2004 13:18:01 -0500 Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org) by megatron.ietf.org with esmtp (Exim 4.32) id 1CcSaJ-0005Q3-1s for mpls@megatron.ietf.org; Thu, 09 Dec 2004 13:00:11 -0500 Received: from ietf-mx.ietf.org (ietf-mx.ietf.org [132.151.6.1]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id NAA15974 for ; Thu, 9 Dec 2004 13:00:08 -0500 (EST) Received: from rwcrmhc13.comcast.net ([204.127.198.39]) by ietf-mx.ietf.org with esmtp (Exim 4.33) id 1CcShJ-0002ju-Kr for mpls@ietf.org; Thu, 09 Dec 2004 13:07:27 -0500 Received: from [10.129.74.91] (external47-240.cps.k12.il.us[209.175.47.240]) by comcast.net (rwcrmhc13) with ESMTP id <2004120917593701500d9v20e>; Thu, 9 Dec 2004 17:59:38 +0000 Message-ID: <41B89288.8020302@comcast.net> Date: Thu, 09 Dec 2004 11:59:36 -0600 From: Sam Munzani User-Agent: Mozilla Thunderbird 0.9 (Windows/20041103) X-Accept-Language: en-us, en MIME-Version: 1.0 To: jordan.britnell@bell.ca Subject: Re: [mpls] Applying Qos on VPNs References: <5BA2482D51EA8440B36B8329127619B8015F83A6@Toroondc915.bell.corp.bce.ca> In-Reply-To: <5BA2482D51EA8440B36B8329127619B8015F83A6@Toroondc915.bell.corp.bce.ca> Content-Type: text/plain; charset=windows-1252; format=flowed X-Spam-Score: 0.0 (/) X-Scan-Signature: 1a1bf7677bfe77d8af1ebe0e91045c5b Content-Transfer-Encoding: quoted-printable X-MIME-Autoconverted: from 8bit to quoted-printable by ietf.org id NAA15974 Cc: mpls@ietf.org X-BeenThere: mpls@lists.ietf.org X-Mailman-Version: 2.1.5 Precedence: list Reply-To: smunzani@comcast.net List-Id: Multi-Protocol Label Switching WG List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Sender: mpls-bounces@ietf.org Errors-To: mpls-bounces@ietf.org X-Spam-Score: 0.0 (/) X-Scan-Signature: 6d95a152022472c7d6cdf886a0424dc6 Content-Transfer-Encoding: quoted-printable > Sort of. The part up to tunnel lookup is correct. TOS stamping takes=20 > place on the CE along with some sort of rate limiting usually. Mapping=20 > the packets to tunnels would be done on a routing basis I believe. If=20 > I=92m not mistaken you can also use half-duplex VRF to do this as well.= =20 > As the CE TOS bit is encapsulated in the MPLS info the experimental=20 > bit will be used. Make sense? > What mechanism can ensure CE will not setup TOS bit differently than=20 they paid for? You may not have control on their equipments. Sam > Jordan Britnell, CCNA > > IP Technology Research > > BCE/Bell Canada > > (416) 215-3729 > > _jordan.britnell@bell.ca _ > > -----Original Message----- > *From:* kurien_joseph@agilent.com [mailto:kurien_joseph@agilent.com] > *Sent:* December 9, 2004 12:16 PM > *To:* Britnell, Jordan (5000008); kurien_joseph@agilent.com > *Cc:* mpls@ietf.org > *Subject:* RE: [mpls] Applying Qos on VPNs > > Does it imply that the CEs linked to the ingress PE would send IP=20 > packet=92s TOS field to mark a QoS service. > > And additionally the PE would lookup the TOS field on all its inbound=20 > CE interfaces and mark EXP bit and forward them to any of the TE=20 > tunnels that which may have an EXP bit mapping? > > Thanks > > Kurien > > -----------------------------------------------------------------------= - > > *From:* jordan.britnell@bell.ca [mailto:jordan.britnell@bell.ca] > *Sent:* Thursday, December 09, 2004 8:46 AM > *To:* kurien_joseph@agilent.com > *Subject:* RE: [mpls] Applying Qos on VPNs > > Absolutely. You can use half-duplex VRF routing as well as MPLS=20 > experimental bits to define how you would like traffic from a customer=20 > to be handled. A search on Cisco=92s site will show you the necessary=20 > steps. > > Jordan Britnell, CCNA > > IP Technology Research > > BCE/Bell Canada > > (416) 215-3729 > > _jordan.britnell@bell.ca _ > > -----Original Message----- > *From:* mpls-bounces@lists.ietf.org=20 > [mailto:mpls-bounces@lists.ietf.org] *On Behalf Of=20 > *kurien_joseph@agilent.com > *Sent:* December 9, 2004 11:25 AM > *To:* mpls@ietf.org > *Subject:* [mpls] Applying Qos on VPNs > > Can QoS be applied to Layer 3 MPLS VPNs in such a manner that, two=20 > customers connected to the same ingress PE router but offered two=20 > types of services like GoldVoIP and SilverVoIP and two TE tunnels=20 > having different Path options but terminating together on a common=20 > egress PE? > > Since the Egress PE for the both VPNs is the same, is it possible to=20 > have VPN traffic classified and routed to different tunnels? > > Could someone pass a link to any cisco or juniper configuration guide ? > > Thanks > > Kurien > > R & D Engineer, > MPLS/VPN Assurance > OSSD, > Agilent Technologies. > > Tel : 916 788 6678 ( TELNET 788 6678) > >------------------------------------------------------------------------ > >_______________________________________________ >mpls mailing list >mpls@lists.ietf.org >https://www1.ietf.org/mailman/listinfo/mpls > =20 > _______________________________________________ mpls mailing list mpls@lists.ietf.org https://www1.ietf.org/mailman/listinfo/mpls From mpls-bounces@ietf.org Sat Dec 11 14:56:57 2004 Received: from ietf-mx.ietf.org (ietf-mx.ietf.org [132.151.6.1]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id OAA14292; Sat, 11 Dec 2004 14:56:57 -0500 (EST) Received: from megatron.ietf.org ([132.151.6.71]) by ietf-mx.ietf.org with esmtp (Exim 4.33) id 1CdDTu-00013P-Jz; Sat, 11 Dec 2004 15:04:42 -0500 Received: from localhost.localdomain ([127.0.0.1] helo=megatron.ietf.org) by megatron.ietf.org with esmtp (Exim 4.32) id 1CdDK3-0003yT-SB; Sat, 11 Dec 2004 14:54:31 -0500 Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org) by megatron.ietf.org with esmtp (Exim 4.32) id 1CdDEz-000334-NN for mpls@megatron.ietf.org; Sat, 11 Dec 2004 14:49:17 -0500 Received: from ietf-mx.ietf.org (ietf-mx.ietf.org [132.151.6.1]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id OAA13935 for ; Sat, 11 Dec 2004 14:49:15 -0500 (EST) Received: from evita3.cs.fredonia.edu ([141.238.30.15]) by ietf-mx.ietf.org with esmtp (Exim 4.33) id 1CdDMR-0000tI-2i for mpls@ietf.org; Sat, 11 Dec 2004 14:57:00 -0500 Received: from zubairi (zubairi.cs.fredonia.edu [141.238.30.211]) by evita3.cs.fredonia.edu (8.10.2/8.10.2) with SMTP id iBBJmf210689 for ; Sat, 11 Dec 2004 14:48:41 -0500 Message-ID: <003701c4dfba$85225f70$d31eee8d@zubairi> From: "Junaid Ahmed Zubairi" To: Date: Sat, 11 Dec 2004 14:49:22 -0500 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 5.50.4942.400 X-MimeOLE: Produced By Microsoft MimeOLE V5.50.4942.400 X-Spam-Score: 0.0 (/) X-Scan-Signature: 4d87d2aa806f79fed918a62e834505ca Content-Transfer-Encoding: 7bit Subject: [mpls] Communication Symposium X-BeenThere: mpls@lists.ietf.org X-Mailman-Version: 2.1.5 Precedence: list Reply-To: Junaid Ahmed Zubairi List-Id: Multi-Protocol Label Switching WG List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Sender: mpls-bounces@ietf.org Errors-To: mpls-bounces@ietf.org X-Spam-Score: 0.0 (/) X-Scan-Signature: 5a9a1bd6c2d06a21d748b7d0070ddcb8 Content-Transfer-Encoding: 7bit Please submit papers to the following session on communication system performance. ---Junaid --------------------------------------------------------------------- Dear Colleagues, I would like to invite you to submit a paper (or an extended abstract) for a special session titled "Communication Systems and Networks Performance", which I am organizing as part of a well-known multi-conference SCI 2005 (The 9th World Multi-Conference on Systemics, Cybernetics and Informatics), to be held July 10-13, 2005 in Orlando, Florida, USA. More information about the conference is available at http://www.iiisci.org/sci2005/website/default.asp Please note that this session has been pre-approved by the conference organizing committee and your paper or extended abstract will be peer reviewed by researchers in your area. Also note that this session highlights one of the major themes of the conference, namely "Communication and Network Systems, Technologies and Applications". The best 30% of all (invited and regular) sessions' best papers will be published in the SCI Journal. Please submit your full paper or extended abstract via the conference web site with a copy to me at s.akhtar@uaeu.ac.ae following the conference guidelines provided at the conference web site latest by December 15th, 2004. Paper on any topic related to the above-mentioned session will be considered. Thanks. Shakil Akhtar, Ph.D. Professor College of Information Technology UAE University s.akhtar@uaeu.ac.ae http://faculty.uaeu.ac.ae/s.akhtar _______________________________________________ mpls mailing list mpls@lists.ietf.org https://www1.ietf.org/mailman/listinfo/mpls From mpls-bounces@ietf.org Sun Dec 12 21:21:38 2004 Received: from ietf-mx.ietf.org (ietf-mx.ietf.org [132.151.6.1]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id VAA28926; Sun, 12 Dec 2004 21:21:38 -0500 (EST) Received: from megatron.ietf.org ([132.151.6.71]) by ietf-mx.ietf.org with esmtp (Exim 4.33) id 1Cdfxy-0007M8-5Z; Sun, 12 Dec 2004 21:29:39 -0500 Received: from localhost.localdomain ([127.0.0.1] helo=megatron.ietf.org) by megatron.ietf.org with esmtp (Exim 4.32) id 1Cdfdp-0006bY-Mx; Sun, 12 Dec 2004 21:08:49 -0500 Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org) by megatron.ietf.org with esmtp (Exim 4.32) id 1CdfWv-0004Tm-52 for mpls@megatron.ietf.org; Sun, 12 Dec 2004 21:01:41 -0500 Received: from ietf-mx.ietf.org (ietf-mx.ietf.org [132.151.6.1]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id VAA27006 for ; Sun, 12 Dec 2004 21:01:39 -0500 (EST) Received: from bay17-f8.bay17.hotmail.com ([64.4.43.58] helo=hotmail.com) by ietf-mx.ietf.org with esmtp (Exim 4.33) id 1Cdfec-0006lI-Hl for mpls@ietf.org; Sun, 12 Dec 2004 21:09:40 -0500 Received: from mail pickup service by hotmail.com with Microsoft SMTPSVC; Sun, 12 Dec 2004 18:01:00 -0800 Message-ID: Received: from 218.104.71.162 by by17fd.bay17.hotmail.msn.com with HTTP; Mon, 13 Dec 2004 02:00:55 GMT X-Originating-IP: [218.104.71.162] X-Originating-Email: [garthdawn@hotmail.com] X-Sender: garthdawn@hotmail.com In-Reply-To: <003701c4dfba$85225f70$d31eee8d@zubairi> From: "Lee Garth" To: mpls@ietf.org Date: Mon, 13 Dec 2004 02:00:55 +0000 Mime-Version: 1.0 Content-Type: text/plain; charset=gb2312; format=flowed X-OriginalArrivalTime: 13 Dec 2004 02:01:00.0697 (UTC) FILETIME=[97FFB090:01C4E0B7] X-Spam-Score: 0.8 (/) X-Scan-Signature: 1ac7cc0a4cd376402b85bc1961a86ac2 Content-Transfer-Encoding: quoted-printable X-MIME-Autoconverted: from 8bit to quoted-printable by ietf.org id VAA27006 Subject: [mpls] I have questions 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@ietf.org Errors-To: mpls-bounces@ietf.org X-Spam-Score: 0.8 (/) X-Scan-Signature: 93238566e09e6e262849b4f805833007 Content-Transfer-Encoding: quoted-printable Hello to all: What if an LSR node receives a packet with a label, and the LFIB in t= he=20 LSR doesn't have a matching entry for the label? Eg. there is no entry in= =20 LFIB whose incoming label is the same as the label from the receiving=20 packet. I anticipate your kind answer. And in advance, Merry Christmas to you= ! garthda= wn _________________________________________________________________ =CF=ED=D3=C3=CA=C0=BD=E7=C9=CF=D7=EE=B4=F3=B5=C4=B5=E7=D7=D3=D3=CA=BC=FE=CF= =B5=CD=B3=A1=AA MSN Hotmail=A1=A3 http://www.hotmail.com =20 _______________________________________________ mpls mailing list mpls@lists.ietf.org https://www1.ietf.org/mailman/listinfo/mpls From mpls-bounces@ietf.org Mon Dec 13 02:17:05 2004 Received: from ietf-mx.ietf.org (ietf-mx.ietf.org [132.151.6.1]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id CAA03511; Mon, 13 Dec 2004 02:17:05 -0500 (EST) Received: from megatron.ietf.org ([132.151.6.71]) by ietf-mx.ietf.org with esmtp (Exim 4.33) id 1CdkZv-00056s-3M; Mon, 13 Dec 2004 02:25:08 -0500 Received: from localhost.localdomain ([127.0.0.1] helo=megatron.ietf.org) by megatron.ietf.org with esmtp (Exim 4.32) id 1CdkJ7-0004Ri-BV; Mon, 13 Dec 2004 02:07:45 -0500 Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org) by megatron.ietf.org with esmtp (Exim 4.32) id 1CdkEz-0001ve-A2 for mpls@megatron.ietf.org; Mon, 13 Dec 2004 02:03:29 -0500 Received: from ietf-mx.ietf.org (ietf-mx.ietf.org [132.151.6.1]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id CAA22017 for ; Mon, 13 Dec 2004 02:03:28 -0500 (EST) Received: from p-mail1.rd.francetelecom.com ([195.101.245.15]) by ietf-mx.ietf.org with esmtp (Exim 4.33) id 1CdkMk-0004oP-8f for mpls@ietf.org; Mon, 13 Dec 2004 02:11:30 -0500 Received: from ftrdmel1.rd.francetelecom.fr ([10.193.117.152]) by parsmtp1.rd.francetelecom.com with Microsoft SMTPSVC(6.0.3790.211); Mon, 13 Dec 2004 07:55:12 +0100 X-MimeOLE: Produced By Microsoft Exchange V6.5.7226.0 Content-class: urn:content-classes:message MIME-Version: 1.0 Subject: RE : [mpls] I have questions Date: Mon, 13 Dec 2004 07:54:26 +0100 Message-ID: Thread-Topic: [mpls] I have questions thread-index: AcTguqZAK+RkmRfRROWw4F2wA1+9/AAJYSOQ From: "LE ROUX Jean-Louis RD-CORE-LAN" To: "Lee Garth" X-OriginalArrivalTime: 13 Dec 2004 06:55:12.0116 (UTC) FILETIME=[B1107B40:01C4E0E0] X-Spam-Score: 0.0 (/) X-Scan-Signature: 856eb5f76e7a34990d1d457d8e8e5b7f Cc: mpls@ietf.org X-BeenThere: mpls@lists.ietf.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Multi-Protocol Label Switching WG List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Content-Type: multipart/mixed; boundary="===============1242401062==" Sender: mpls-bounces@ietf.org Errors-To: mpls-bounces@ietf.org X-Spam-Score: 0.0 (/) X-Scan-Signature: 8b30eb7682a596edff707698f4a80f7d --===============1242401062== Content-class: urn:content-classes:message Content-Type: text/plain; charset="utf-8" Content-Transfer-Encoding: base64 SGkgTGVlLA0KDQpTZWUgc2VjdGlvbiAzLjE4IG9mIFJGQyAzMDMxDQoNCkpMDQoNCj4tLS0tLU1l c3NhZ2UgZCdvcmlnaW5lLS0tLS0NCj5EZSA6IG1wbHMtYm91bmNlc0BsaXN0cy5pZXRmLm9yZyAN Cj5bbWFpbHRvOm1wbHMtYm91bmNlc0BsaXN0cy5pZXRmLm9yZ10gRGUgbGEgcGFydCBkZSBMZWUg R2FydGgNCj5FbnZvecOpIDogbHVuZGkgMTMgZMOpY2VtYnJlIDIwMDQgMDM6MDENCj7DgCA6IG1w bHNAaWV0Zi5vcmcNCj5PYmpldCA6IFttcGxzXSBJIGhhdmUgcXVlc3Rpb25zDQo+DQo+DQo+SGVs bG8gdG8gYWxsOg0KPg0KPiAgICBXaGF0IGlmIGFuIExTUiBub2RlIHJlY2VpdmVzIGEgcGFja2V0 IHdpdGggYSBsYWJlbCwgYW5kIA0KPnRoZSBMRklCIGluIHRoZSANCj5MU1IgZG9lc24ndCBoYXZl IGEgbWF0Y2hpbmcgZW50cnkgZm9yIHRoZSBsYWJlbD8gRWcuIHRoZXJlIGlzIA0KPm5vIGVudHJ5 IGluIA0KPkxGSUIgd2hvc2UgaW5jb21pbmcgbGFiZWwgaXMgdGhlIHNhbWUgYXMgdGhlIGxhYmVs IGZyb20gdGhlIHJlY2VpdmluZyANCj5wYWNrZXQuDQo+DQo+ICAgIEkgYW50aWNpcGF0ZSB5b3Vy IGtpbmQgYW5zd2VyLiBBbmQgaW4gYWR2YW5jZSwgTWVycnkgDQo+Q2hyaXN0bWFzIHRvIHlvdSEN Cj4NCj4gICAgICAgICAgICAgICAgICAgICAgICAgICAgICAgICAgICAgICAgICAgICAgICAgICAg ICAgICAgICAgICANCj4gICBnYXJ0aGRhd24NCj4NCj5fX19fX19fX19fX19fX19fX19fX19fX19f X19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fXw0KPuS6q+eUqOS4lueVjOS4 iuacgOWkp+eahOeUteWtkOmCruS7tuezu+e7n+KAlCBNU04gSG90bWFpbOOAgiAgaHR0cDovL3d3 dy5ob3RtYWlsLmNvbSAgDQo+DQo+DQo+X19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19f X19fX19fX19fX19fX18NCj5tcGxzIG1haWxpbmcgbGlzdA0KPm1wbHNAbGlzdHMuaWV0Zi5vcmcN Cj5odHRwczovL3d3dzEuaWV0Zi5vcmcvbWFpbG1hbi9saXN0aW5mby9tcGxzDQo+DQo= --===============1242401062== Content-Type: text/plain; charset="us-ascii" MIME-Version: 1.0 Content-Disposition: inline Content-Transfer-Encoding: 7bit _______________________________________________ mpls mailing list mpls@lists.ietf.org https://www1.ietf.org/mailman/listinfo/mpls --===============1242401062==-- From mpls-bounces@ietf.org Mon Dec 13 07:57:59 2004 Received: from ietf-mx.ietf.org (ietf-mx.ietf.org [132.151.6.1]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id HAA01736; Mon, 13 Dec 2004 07:57:59 -0500 (EST) Received: from megatron.ietf.org ([132.151.6.71]) by ietf-mx.ietf.org with esmtp (Exim 4.33) id 1Cdpts-0004a2-Ft; Mon, 13 Dec 2004 08:06:05 -0500 Received: from localhost.localdomain ([127.0.0.1] helo=megatron.ietf.org) by megatron.ietf.org with esmtp (Exim 4.32) id 1CdpjK-0005mO-Hy; Mon, 13 Dec 2004 07:55:10 -0500 Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org) by megatron.ietf.org with esmtp (Exim 4.32) id 1CdpYu-0003wo-Ix for mpls@megatron.ietf.org; Mon, 13 Dec 2004 07:44:24 -0500 Received: from p-mail1.rd.francetelecom.com (p-mail1.rd.francetelecom.com [195.101.245.15]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id HAA00989 for ; Mon, 13 Dec 2004 07:44:23 -0500 (EST) Received: from FTRDMEL2.rd.francetelecom.fr ([10.193.117.153]) by parsmtp1.rd.francetelecom.com with Microsoft SMTPSVC(6.0.3790.211); Mon, 13 Dec 2004 13:44:25 +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 Date: Mon, 13 Dec 2004 13:44:22 +0100 Message-ID: <3418F3471F1CA4409901547349FFAE2E02101DB1@FTRDMEL2.rd.francetelecom.fr> Thread-Topic: Welcome to the "mpls" mailing list Thread-Index: AcThBPK/5X9uwnP8R0i9kroPWPTiFwADHQiw From: "zze-CHAIEB Imene RD-CORE-LAN" To: X-OriginalArrivalTime: 13 Dec 2004 12:44:25.0539 (UTC) FILETIME=[7A471930:01C4E111] Content-Transfer-Encoding: quoted-printable Subject: [mpls] (no subject) 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@ietf.org Errors-To: mpls-bounces@ietf.org X-Spam-Score: 0.0 (/) X-Scan-Signature: 3002fc2e661cd7f114cb6bae92fe88f1 Content-Transfer-Encoding: quoted-printable -----Message d'origine----- De : mpls-bounces@lists.ietf.org [mailto:mpls-bounces@lists.ietf.org]De la part de mpls-request@lists.ietf.org Envoye : lundi 13 decembre 2004 12:07 A : zze-CHAIEB Imene RD-CORE-LAN Objet : Welcome to the "mpls" mailing list Welcome to the mpls@lists.ietf.org mailing list! To post to this list, send your email to: mpls@lists.ietf.org General information about the mailing list is at: https://www1.ietf.org/mailman/listinfo/mpls ********************************************************************** Note Well Any submission to the IETF intended by the Contributor for publication as all or part of an IETF Internet-Draft or RFC and any statement made within the context of an IETF activity is considered an "IETF Contribution". Such statements include oral statements in IETF sessions, as well as written and electronic communications made at any time or place, which are addressed to: * the IETF plenary session, * any IETF working group or portion thereof, * the IESG, or any member thereof on behalf of the IESG, * the IAB or any member thereof on behalf of the IAB, * any IETF mailing list, including the IETF list itself, any=20 working group or design team list, or any other list functioning under IETF auspices, * the RFC Editor or the Internet-Drafts function All IETF Contributions are subject to the rules of RFC 3667 and RFC 3668. Statements made outside of an IETF session, mailing list or other function, that are clearly not intended to be input to an IETF activity, group or function, are not IETF Contributions in the context of this notice. Please consult RFC 3667 for details. ************************************************************************ ******* If you ever want to unsubscribe or change your options (eg, switch to or from digest mode, change your password, etc.), visit your subscription page at: =20 https://www1.ietf.org/mailman/options/mpls/imene.chaieb%40rd.francetelec om.com You can also make such adjustments via email by sending a message to: mpls-request@lists.ietf.org with the word `help' in the subject or body (don't include the quotes), and you will get back a message with instructions. You must know your password to change your options (including changing the password, itself) or to unsubscribe. It is: rourou1112 Normally, Mailman will remind you of your lists.ietf.org mailing list passwords once every month, although you can disable this if you prefer. This reminder will also include instructions on how to unsubscribe or change your account options. There is also a button on your options page that will email your current password to you. _______________________________________________ mpls mailing list mpls@lists.ietf.org https://www1.ietf.org/mailman/listinfo/mpls From mpls-bounces@ietf.org Mon Dec 13 10:41:04 2004 Received: from ietf-mx.ietf.org (ietf-mx.ietf.org [132.151.6.1]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id KAA20554; Mon, 13 Dec 2004 10:41:03 -0500 (EST) Received: from megatron.ietf.org ([132.151.6.71]) by ietf-mx.ietf.org with esmtp (Exim 4.33) id 1CdsRi-00010j-G5; Mon, 13 Dec 2004 10:49:11 -0500 Received: from localhost.localdomain ([127.0.0.1] helo=megatron.ietf.org) by megatron.ietf.org with esmtp (Exim 4.32) id 1CdsCY-0004dv-Dc; Mon, 13 Dec 2004 10:33:30 -0500 Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org) by megatron.ietf.org with esmtp (Exim 4.32) id 1Cds3H-0001ie-ES for mpls@megatron.ietf.org; Mon, 13 Dec 2004 10:23:55 -0500 Received: from mailgate.pit.comms.marconi.com (mailgate.pit.comms.marconi.com [169.144.68.6]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id KAA18568 for ; Mon, 13 Dec 2004 10:23:53 -0500 (EST) Received: from mailman.pit.comms.marconi.com (mailman.pit.comms.marconi.com [169.144.2.12]) by mailgate.pit.comms.marconi.com (8.12.10+Sun/8.12.10) with ESMTP id iBDFNNcT005608 for ; Mon, 13 Dec 2004 10:23:23 -0500 (EST) Received: from [169.144.136.107] (dcharlap-pc.dc.fore.com [169.144.136.107]) by mailman.pit.comms.marconi.com (8.9.3/8.9.3) with ESMTP id KAA06420 for ; Mon, 13 Dec 2004 10:23:23 -0500 (EST) Message-ID: <41BDB3EA.3000102@marconi.com> Date: Mon, 13 Dec 2004 10:23:22 -0500 From: David Charlap Organization: Marconi, Vienna VA User-Agent: Mozilla Thunderbird 0.9 (Windows/20041103) X-Accept-Language: en-us, en MIME-Version: 1.0 To: IETF MPLS List Subject: Re: [mpls] I have questions References: In-Reply-To: Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit Content-Transfer-Encoding: 7bit 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@ietf.org Errors-To: mpls-bounces@ietf.org X-Spam-Score: 0.0 (/) X-Scan-Signature: ffa9dfbbe7cc58b3fa6b8ae3e57b0aa3 Content-Transfer-Encoding: 7bit Lee Garth wrote: > > What if an LSR node receives a packet with a label, and the LFIB in > the LSR doesn't have a matching entry for the label? Eg. there is no > entry in LFIB whose incoming label is the same as the label from the > receiving packet. If you receive a packet with an unknown label, you should drop the packet. To do anything else would result in undefined behavior. Some people have entertained the idea of popping the label in this situation. This is bad, because a transit switch does not know the nature of the packet under the label. It might not be an IP packet. The transit switch may not have routing information to the destination (assuming it is IP.) If there are inner labels, the transit switch may not be able to handle them either. (For example, VPN-identifying labels are usually unknown to all but the PE routers.) -- David _______________________________________________ mpls mailing list mpls@lists.ietf.org https://www1.ietf.org/mailman/listinfo/mpls From mpls-bounces@ietf.org Mon Dec 13 16:09:47 2004 Received: from ietf-mx.ietf.org (ietf-mx.ietf.org [132.151.6.1]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id QAA21539; Mon, 13 Dec 2004 16:09:47 -0500 (EST) Received: from megatron.ietf.org ([132.151.6.71]) by ietf-mx.ietf.org with esmtp (Exim 4.33) id 1CdxZu-0001lq-1d; Mon, 13 Dec 2004 16:17:58 -0500 Received: from localhost.localdomain ([127.0.0.1] helo=megatron.ietf.org) by megatron.ietf.org with esmtp (Exim 4.32) id 1CdwxH-0004OM-F7; Mon, 13 Dec 2004 15:38:03 -0500 Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org) by megatron.ietf.org with esmtp (Exim 4.32) id 1CdwtQ-0001q9-CR; Mon, 13 Dec 2004 15:34:04 -0500 Received: from CNRI.Reston.VA.US (localhost [127.0.0.1]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id PAA16371; Mon, 13 Dec 2004 15:34:02 -0500 (EST) Message-Id: <200412132034.PAA16371@ietf.org> Mime-Version: 1.0 Content-Type: Multipart/Mixed; Boundary="NextPart" To: i-d-announce@ietf.org From: Internet-Drafts@ietf.org Date: Mon, 13 Dec 2004 15:34:02 -0500 Cc: mpls@ietf.org Subject: [mpls] I-D ACTION:draft-ietf-mpls-p2mp-sig-requirement-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@ietf.org Errors-To: mpls-bounces@ietf.org X-Spam-Score: 0.4 (/) X-Scan-Signature: 9a2be21919e71dc6faef12b370c4ecf5 --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-00.txt Pages : 30 Date : 2004-12-13 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. It is intended that the requirements presented in this document are not limited to the requirements of packet switched networks, but also encompass the requirements of L2SC, 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-00.txt To remove yourself from the I-D Announcement list, send a message to i-d-announce-request@ietf.org with the word unsubscribe in the body of the message. You can also visit https://www1.ietf.org/mailman/listinfo/I-D-announce to change your subscription settings. Internet-Drafts are also available by anonymous FTP. Login with the username "anonymous" and a password of your e-mail address. After logging in, type "cd internet-drafts" and then "get draft-ietf-mpls-p2mp-sig-requirement-00.txt". A list of Internet-Drafts directories can be found in http://www.ietf.org/shadow.html or ftp://ftp.ietf.org/ietf/1shadow-sites.txt Internet-Drafts can also be obtained by e-mail. Send a message to: mailserv@ietf.org. In the body type: "FILE /internet-drafts/draft-ietf-mpls-p2mp-sig-requirement-00.txt". NOTE: The mail server at ietf.org can return the document in MIME-encoded form by using the "mpack" utility. To use this feature, insert the command "ENCODING mime" before the "FILE" command. To decode the response(s), you will need "munpack" or a MIME-compliant mail reader. Different MIME-compliant mail readers exhibit different behavior, especially when dealing with "multipart" MIME messages (i.e. documents which have been split up into multiple messages), so check your local documentation on how to manipulate these messages. Below is the data which will enable a MIME compliant mail reader implementation to automatically retrieve the ASCII version of the Internet-Draft. --NextPart Content-Type: Multipart/Alternative; Boundary="OtherAccess" --OtherAccess Content-Type: Message/External-body; access-type="mail-server"; server="mailserv@ietf.org" Content-Type: text/plain Content-ID: <2004-12-13145543.I-D@ietf.org> ENCODING mime FILE /internet-drafts/draft-ietf-mpls-p2mp-sig-requirement-00.txt --OtherAccess Content-Type: Message/External-body; name="draft-ietf-mpls-p2mp-sig-requirement-00.txt"; site="ftp.ietf.org"; access-type="anon-ftp"; directory="internet-drafts" Content-Type: text/plain Content-ID: <2004-12-13145543.I-D@ietf.org> --OtherAccess-- --NextPart Content-Type: text/plain; charset="us-ascii" MIME-Version: 1.0 Content-Transfer-Encoding: 7bit Content-Disposition: inline Content-Transfer-Encoding: 7bit _______________________________________________ mpls mailing list mpls@lists.ietf.org https://www1.ietf.org/mailman/listinfo/mpls --NextPart-- From mpls-bounces@ietf.org Tue Dec 14 21:51:16 2004 Received: from ietf-mx.ietf.org (ietf-mx.ietf.org [132.151.6.1]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id VAA19152; Tue, 14 Dec 2004 21:51:15 -0500 (EST) Received: from megatron.ietf.org ([132.151.6.71]) by ietf-mx.ietf.org with esmtp (Exim 4.33) id 1CePOA-00077a-8m; Tue, 14 Dec 2004 21:59:42 -0500 Received: from localhost.localdomain ([127.0.0.1] helo=megatron.ietf.org) by megatron.ietf.org with esmtp (Exim 4.32) id 1CePDj-0004Wq-VZ; Tue, 14 Dec 2004 21:48:56 -0500 Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org) by megatron.ietf.org with esmtp (Exim 4.32) id 1CePAB-0003tL-BY for mpls@megatron.ietf.org; Tue, 14 Dec 2004 21:45:15 -0500 Received: from ietf-mx.ietf.org (ietf-mx.ietf.org [132.151.6.1]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id VAA18376 for ; Tue, 14 Dec 2004 21:45:13 -0500 (EST) Received: from tama5.ecl.ntt.co.jp ([129.60.39.102]) by ietf-mx.ietf.org with esmtp (Exim 4.33) id 1CePII-0006x1-AV for mpls@ietf.org; Tue, 14 Dec 2004 21:53:40 -0500 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 iBF2j4QX018213; Wed, 15 Dec 2004 11:45:04 +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 iBF2j383008844; Wed, 15 Dec 2004 11:45:03 +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 iBF2j2JM008815; Wed, 15 Dec 2004 11:45:02 +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 iBF2j2J8016438; Wed, 15 Dec 2004 11:45:02 +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 iBF2j13O016429; Wed, 15 Dec 2004 11:45:01 +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 iBF2j10K003171; Wed, 15 Dec 2004 11:45:01 +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 iBF2j0Vr015730; Wed, 15 Dec 2004 11:45:00 +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 iBF2j0MP015727; Wed, 15 Dec 2004 11:45:00 +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 LAA21105; Wed, 15 Dec 2004 11:45:00 +0900 (JST) Message-Id: <5.0.2.5.2.20041215115443.066717d0@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: Wed, 15 Dec 2004 11:58:43 +0900 To: mpls@ietf.org From: Seisho Yasukawa Mime-Version: 1.0 Content-Type: text/plain; charset="us-ascii"; format=flowed X-Spam-Score: 0.0 (/) X-Scan-Signature: 8b30eb7682a596edff707698f4a80f7d Subject: [mpls] new version of the requirement draft for P2MP TE signaling 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@ietf.org Errors-To: mpls-bounces@ietf.org X-Spam-Score: 0.0 (/) X-Scan-Signature: 21c69d3cfc2dd19218717dbe1d974352 Hi List, We have published a new version of the requirements draft for P2MP MPLS TE signaling. You can see it at http://www.ietf.org/internet-drafts/draft-ietf-mpls-p2mp-sig-requirement-00.txt There are four major changes to this version which are all intended to answer the concerns raised by the multicast routing community in Washington. 1. We have changed the draft title and name to make it much more clear that this draft refers only to signaling requirements for P2MP TE MPLS LSPs. 2. We have removed all references about whether you can run a multicast routing protocol in the core. 3. We have removed the sections that illustrated the applicability of P2MP TE LSPs. 4. We have added a section to list some of the non-objectives of the draft. As was presented in the MPLS meeting in Washington, there are a few unresolved technical issues within the draft. Over the next few weeks I plan to start separate threads on this mailing list about each of these and attempt to close down the discussion within the next month or two. Please contribute to these discussions. Thanks, Seisho _______________________________________________ mpls mailing list mpls@lists.ietf.org https://www1.ietf.org/mailman/listinfo/mpls From mpls-bounces@ietf.org Wed Dec 15 18:24:44 2004 Received: from ietf-mx.ietf.org (ietf-mx.ietf.org [132.151.6.1]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id SAA29740; Wed, 15 Dec 2004 18:24:44 -0500 (EST) Received: from megatron.ietf.org ([132.151.6.71]) by ietf-mx.ietf.org with esmtp (Exim 4.33) id 1Ceie3-00076t-5p; Wed, 15 Dec 2004 18:33:23 -0500 Received: from localhost.localdomain ([127.0.0.1] helo=megatron.ietf.org) by megatron.ietf.org with esmtp (Exim 4.32) id 1CeiTc-0003aN-CB; Wed, 15 Dec 2004 18:22:36 -0500 Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org) by megatron.ietf.org with esmtp (Exim 4.32) id 1CeiL9-0007X5-Ha for mpls@megatron.ietf.org; Wed, 15 Dec 2004 18:13:51 -0500 Received: from ietf-mx.ietf.org (ietf-mx.ietf.org [132.151.6.1]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id SAA28633 for ; Wed, 15 Dec 2004 18:13:48 -0500 (EST) From: kurien_joseph@agilent.com Received: from msgbas1x.cos.agilent.com ([192.25.240.36]) by ietf-mx.ietf.org with esmtp (Exim 4.33) id 1CeiTS-0006to-SF for mpls@ietf.org; Wed, 15 Dec 2004 18:22:27 -0500 Received: from relcos1.cos.agilent.com (relcos1.cos.agilent.com [130.29.152.239]) by msgbas1x.cos.agilent.com (Postfix) with ESMTP id 262CF24226 for ; Wed, 15 Dec 2004 16:13:49 -0700 (MST) Received: from wlvdvs01.lvld.agilent.com (wlvdvs01.lvld.agilent.com [148.5.6.4]) by relcos1.cos.agilent.com (Postfix) with ESMTP id EAC2743 for ; Wed, 15 Dec 2004 16:13:46 -0700 (MST) Received: from wcosbh22.cos.agilent.com ([130.29.152.178]) by wlvdvs01.lvld.agilent.com with InterScan Messaging Security Suite; Wed, 15 Dec 2004 16:13:45 -0700 Received: from wcosmb02.cos.agilent.com ([130.29.152.96]) by wcosbh22.cos.agilent.com with Microsoft SMTPSVC(5.0.2195.6713); Wed, 15 Dec 2004 16:13:45 -0700 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: Wed, 15 Dec 2004 16:13:44 -0700 Message-ID: <9AB7C093B52FEE4EB66BAE9BE58A32730362DF79@wcosmb02.cos.agilent.com> Thread-Topic: Question on Path taken in an Inter AS VPN Thread-Index: AcTi+7vsE6gRVn3GSqCaE3Sr9xe0oQ== To: X-OriginalArrivalTime: 15 Dec 2004 23:13:45.0163 (UTC) FILETIME=[B997F9B0:01C4E2FB] X-Spam-Score: 0.3 (/) X-Scan-Signature: 2409bba43e9c8d580670fda8b695204a Content-Transfer-Encoding: quoted-printable Subject: [mpls] Question on Path taken in an Inter AS VPN 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@ietf.org Errors-To: mpls-bounces@ietf.org X-Spam-Score: 0.3 (/) X-Scan-Signature: 8abaac9e10c826e8252866cbe6766464 Content-Transfer-Encoding: quoted-printable I have a question on this following scenario having inter-AS VPNs. __ P1___ ASBR1(AS100)__ASBR3(AS200)___P3___ / \ CE1 -- PE1 PE2---CE2 \__ P2___ ASBR2(AS100)__ASBR4(AS200)___P4___/ If the network is configured with LDP-DU running in both Autonomous systems and PE1 and PE2 Peer with each other via their ASBRs. The ASBRs are configured with=20 External MP-BGP. Now which path will PE1 use to send data packets from the VPN customer at CE1?=20 Will it go via P1 or P2? Is the IGP used in computing the shortest LSP path between the PEs? Or does BGP decide on the path option?=20 Thanks for your time. Kurien _______________________________________________ mpls mailing list mpls@lists.ietf.org https://www1.ietf.org/mailman/listinfo/mpls From mpls-bounces@ietf.org Thu Dec 16 05:00:51 2004 Received: from ietf-mx.ietf.org (ietf-mx.ietf.org [132.151.6.1]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id FAA08529; Thu, 16 Dec 2004 05:00:51 -0500 (EST) Received: from megatron.ietf.org ([132.151.6.71]) by ietf-mx.ietf.org with esmtp (Exim 4.33) id 1CesZi-0004YA-Cz; Thu, 16 Dec 2004 05:09:35 -0500 Received: from localhost.localdomain ([127.0.0.1] helo=megatron.ietf.org) by megatron.ietf.org with esmtp (Exim 4.32) id 1CesO2-0006J2-FB; Thu, 16 Dec 2004 04:57:30 -0500 Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org) by megatron.ietf.org with esmtp (Exim 4.32) id 1CesLC-0005Z8-HB for mpls@megatron.ietf.org; Thu, 16 Dec 2004 04:54:38 -0500 Received: from ietf-mx.ietf.org (ietf-mx.ietf.org [132.151.6.1]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id EAA07946 for ; Thu, 16 Dec 2004 04:54:31 -0500 (EST) Received: from [81.80.206.211] (helo=tfr1mx1.telindus.intra) by ietf-mx.ietf.org with esmtp (Exim 4.33) id 1CesTb-0004MF-BU for mpls@ietf.org; Thu, 16 Dec 2004 05:03:16 -0500 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] Question on Path taken in an Inter AS VPN X-MimeOLE: Produced By Microsoft Exchange V6.5.7226.0 Date: Thu, 16 Dec 2004 10:54:02 +0100 Message-ID: Thread-Topic: [mpls] Question on Path taken in an Inter AS VPN Thread-Index: AcTi+7vsE6gRVn3GSqCaE3Sr9xe0oQAVoYxA From: "Mourad Berkane" To: X-Spam-Score: 0.0 (/) X-Scan-Signature: a7d6aff76b15f3f56fcb94490e1052e4 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@ietf.org Errors-To: mpls-bounces@ietf.org X-Spam-Score: 0.0 (/) X-Scan-Signature: c1c65599517f9ac32519d043c37c5336 Content-Transfer-Encoding: quoted-printable >From PE1 VRF table, the best path will be made by BGP. =20 -----Message d'origine----- De=A0: mpls-bounces@lists.ietf.org [mailto:mpls-bounces@lists.ietf.org] = De la part de kurien_joseph@agilent.com Envoy=E9=A0: jeudi 16 d=E9cembre 2004 00:14 =C0=A0: mpls@ietf.org Objet=A0: [mpls] Question on Path taken in an Inter AS VPN I have a question on this following scenario having inter-AS VPNs. __ P1___ ASBR1(AS100)__ASBR3(AS200)___P3___ / \ CE1 -- PE1 PE2---CE2 \__ P2___ ASBR2(AS100)__ASBR4(AS200)___P4___/ If the network is configured with LDP-DU running in both Autonomous systems and PE1 and PE2 Peer with each other via their ASBRs. The ASBRs are configured with=20 External MP-BGP. Now which path will PE1 use to send data packets from the VPN customer at CE1?=20 Will it go via P1 or P2? Is the IGP used in computing the shortest LSP path between the PEs? Or does BGP decide on the path option?=20 Thanks for your time. Kurien _______________________________________________ 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@ietf.org Fri Dec 17 22:10:18 2004 Received: from ietf-mx.ietf.org (ietf-mx.ietf.org [132.151.6.1]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id WAA26339; Fri, 17 Dec 2004 22:10:18 -0500 (EST) Received: from megatron.ietf.org ([132.151.6.71]) by ietf-mx.ietf.org with esmtp (Exim 4.33) id 1CfV7r-0003xj-Jx; Fri, 17 Dec 2004 22:19:24 -0500 Received: from localhost.localdomain ([127.0.0.1] helo=megatron.ietf.org) by megatron.ietf.org with esmtp (Exim 4.32) id 1CfUx4-00018T-TQ; Fri, 17 Dec 2004 22:08:14 -0500 Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org) by megatron.ietf.org with esmtp (Exim 4.32) id 1CfIrT-0007XV-Vb for mpls@megatron.ietf.org; Fri, 17 Dec 2004 09:13:40 -0500 Received: from smtp7.clb.oleane.net (smtp7.clb.oleane.net [213.56.31.27]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id JAA20698 for ; Fri, 17 Dec 2004 09:13:37 -0500 (EST) Received: from Pavillonquatre (upperside.rain.fr [194.206.151.59] (may be forged)) by smtp7.clb.oleane.net with ESMTP id iBHED4HF021443 for ; Fri, 17 Dec 2004 15:13:06 +0100 Message-Id: <200412171413.iBHED4HF021443@smtp7.clb.oleane.net> From: "gunter" To: Date: Fri, 17 Dec 2004 15:13:03 +0100 MIME-Version: 1.0 X-Mailer: Microsoft Office Outlook, Build 11.0.5510 Thread-Index: AcTkQoWUz2Ju8rwYSjeMy9v1hNEDdw== X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2900.2180 X-Mailman-Approved-At: Fri, 17 Dec 2004 22:08:13 -0500 Subject: [mpls] SSL VPN Conference - Paris - France 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="===============1647574020==" Sender: mpls-bounces@ietf.org Errors-To: mpls-bounces@ietf.org X-Spam-Score: 0.3 (/) X-Scan-Signature: 6ba8aaf827dcb437101951262f69b3de This is a multi-part message in MIME format. --===============1647574020== Content-Type: multipart/alternative; boundary="----=_NextPart_000_01A6_01C4E44A.E7A29040" This is a multi-part message in MIME format. ------=_NextPart_000_01A6_01C4E44A.E7A29040 Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit How to provide SSL-based remote access to a broad range of Web and legacy applications? What about application performance and requirements? Are encrypted application tunneling issues solved? What differences with Ipsec VPNs? The SSL VPN Conference will be held in Paris from April 5 to 8, 2005. Get details at: http://www.upperside.fr/sslvpn05/sslvpn05intro.htm ------=_NextPart_000_01A6_01C4E44A.E7A29040 Content-Type: text/html; charset="us-ascii" Content-Transfer-Encoding: quoted-printable

How to provide SSL-based remote access to a = broad range of Web and legacy applications?
What about application performance and requirements?
Are encrypted application tunneling issues solved?
What differences with Ipsec VPNs?

The SSL VPN Conference will be held in Paris from April 5 to 8, = 2005.

Get details = at:

http://www.upperside.fr/sslvpn05/sslvpn05intro.htm