From mpls-bounces@ietf.org Tue Feb 1 19:10:59 2005 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 TAA19869; Tue, 1 Feb 2005 19:10:59 -0500 (EST) Received: from megatron.ietf.org ([132.151.6.71]) by ietf-mx.ietf.org with esmtp (Exim 4.33) id 1Cw8P3-0005J6-HA; Tue, 01 Feb 2005 19:29:53 -0500 Received: from localhost.localdomain ([127.0.0.1] helo=megatron.ietf.org) by megatron.ietf.org with esmtp (Exim 4.32) id 1Cw83N-00088D-Pr; Tue, 01 Feb 2005 19:07:29 -0500 Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org) by megatron.ietf.org with esmtp (Exim 4.32) id 1Cw81r-0007XT-Us for mpls@megatron.ietf.org; Tue, 01 Feb 2005 19:05:56 -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 TAA19231 for ; Tue, 1 Feb 2005 19:05:53 -0500 (EST) Received: from sj-iport-3-in.cisco.com ([171.71.176.72] helo=sj-iport-3.cisco.com) by ietf-mx.ietf.org with esmtp (Exim 4.33) id 1Cw8K6-00059X-Rs for mpls@ietf.org; Tue, 01 Feb 2005 19:24:48 -0500 Received: from sj-core-2.cisco.com (171.71.177.254) by sj-iport-3.cisco.com with ESMTP; 01 Feb 2005 17:15:36 +0000 X-BrightmailFiltered: true X-Brightmail-Tracker: AAAAAA== Received: from flask.cisco.com (IDENT:mirapoint@flask.cisco.com [161.44.122.62]) by sj-core-2.cisco.com (8.12.10/8.12.6) with ESMTP id j1205Gl2006937; Tue, 1 Feb 2005 16:05:17 -0800 (PST) Received: from swallow-mac.cisco.com (sjc-vpn1-340.cisco.com [10.21.97.84]) by flask.cisco.com (MOS 3.4.6-GR) with ESMTP id AOT86234; Tue, 1 Feb 2005 19:05:12 -0500 (EST) Received: by swallow-mac.cisco.com (Postfix, from userid 501) id AACBA1FB9E8; Tue, 1 Feb 2005 14:10:18 -0500 (EST) Received: from cisco.com (localhost [127.0.0.1]) by swallow-mac.cisco.com (Postfix) with ESMTP id 84FEE1FB9C8; Tue, 1 Feb 2005 14:10:18 -0500 (EST) To: Loa Andersson From: George Swallow X-Mailer: MH-E 7.4.3; nmh 1.1; GNU Emacs 21.2.1 Date: Tue, 01 Feb 2005 14:10:17 -0500 Message-Id: <20050201191018.AACBA1FB9E8@swallow-mac.cisco.com> X-Spam-Score: 0.0 (/) X-Scan-Signature: 08170828343bcf1325e4a0fb4584481c Cc: mpls@ietf.org Subject: [mpls] BCP on ECMP 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: 79899194edc4f33a41f49410777972f8 If the working groups consents, I would like Loa to initiate a WG last call on: draft-ietf-mpls-ecmp-bcp-00.txt Thanks, ...George ======================================================================== George Swallow Cisco Systems (978) 936-1398 1414 Massachusetts Avenue Boxborough, MA 01719 _______________________________________________ mpls mailing list mpls@lists.ietf.org https://www1.ietf.org/mailman/listinfo/mpls From mpls-bounces@ietf.org Tue Feb 1 19:26:39 2005 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 TAA21109; Tue, 1 Feb 2005 19:26:39 -0500 (EST) Received: from megatron.ietf.org ([132.151.6.71]) by ietf-mx.ietf.org with esmtp (Exim 4.33) id 1Cw8eC-0005eR-Sp; Tue, 01 Feb 2005 19:45:34 -0500 Received: from localhost.localdomain ([127.0.0.1] helo=megatron.ietf.org) by megatron.ietf.org with esmtp (Exim 4.32) id 1Cw8Aq-0001Xi-41; Tue, 01 Feb 2005 19:15:12 -0500 Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org) by megatron.ietf.org with esmtp (Exim 4.32) id 1Cw846-0008Jg-U3 for mpls@megatron.ietf.org; Tue, 01 Feb 2005 19:08: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 TAA19538 for ; Tue, 1 Feb 2005 19:08:12 -0500 (EST) Received: from sj-iport-3-in.cisco.com ([171.71.176.72] helo=sj-iport-3.cisco.com) by ietf-mx.ietf.org with esmtp (Exim 4.33) id 1Cw8MM-0005EZ-SS for mpls@ietf.org; Tue, 01 Feb 2005 19:27:07 -0500 Received: from sj-core-2.cisco.com (171.71.177.254) by sj-iport-3.cisco.com with ESMTP; 01 Feb 2005 17:17:57 +0000 X-BrightmailFiltered: true X-Brightmail-Tracker: AAAAAA== Received: from flask.cisco.com (IDENT:mirapoint@flask.cisco.com [161.44.122.62]) by sj-core-2.cisco.com (8.12.10/8.12.6) with ESMTP id j1207al2008171; Tue, 1 Feb 2005 16:07:37 -0800 (PST) Received: from swallow-mac.cisco.com (sjc-vpn1-340.cisco.com [10.21.97.84]) by flask.cisco.com (MOS 3.4.6-GR) with ESMTP id AOT86384; Tue, 1 Feb 2005 19:07:23 -0500 (EST) Received: by swallow-mac.cisco.com (Postfix, from userid 501) id BE66C1FC349; Tue, 1 Feb 2005 19:08:15 -0500 (EST) Received: from cisco.com (localhost [127.0.0.1]) by swallow-mac.cisco.com (Postfix) with ESMTP id 6EC521FC340; Tue, 1 Feb 2005 19:08:15 -0500 (EST) To: mpls@ietf.org From: George Swallow X-Mailer: MH-E 7.4.3; nmh 1.1; GNU Emacs 21.2.1 Date: Tue, 01 Feb 2005 19:08:14 -0500 Message-Id: <20050202000815.BE66C1FC349@swallow-mac.cisco.com> X-Spam-Score: 0.0 (/) X-Scan-Signature: 7a6398bf8aaeabc7a7bb696b6b0a2aad Subject: [mpls] Time to set the MPLS Agenda X-BeenThere: mpls@lists.ietf.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Multi-Protocol Label Switching WG List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Sender: mpls-bounces@ietf.org Errors-To: mpls-bounces@ietf.org X-Spam-Score: 0.0 (/) X-Scan-Signature: 856eb5f76e7a34990d1d457d8e8e5b7f Please forward your agenda requests (including an estimate of time) to Loa and me. Thanks, ...George ======================================================================== George Swallow Cisco Systems (978) 936-1398 1414 Massachusetts Avenue Boxborough, MA 01719 _______________________________________________ mpls mailing list mpls@lists.ietf.org https://www1.ietf.org/mailman/listinfo/mpls From mpls-bounces@ietf.org Tue Feb 1 21:15:15 2005 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 VAA01757; Tue, 1 Feb 2005 21:15:15 -0500 (EST) Received: from megatron.ietf.org ([132.151.6.71]) by ietf-mx.ietf.org with esmtp (Exim 4.33) id 1CwALL-0008DS-Gv; Tue, 01 Feb 2005 21:34:11 -0500 Received: from localhost.localdomain ([127.0.0.1] helo=megatron.ietf.org) by megatron.ietf.org with esmtp (Exim 4.32) id 1CwA1F-000246-6S; Tue, 01 Feb 2005 21:13:25 -0500 Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org) by megatron.ietf.org with esmtp (Exim 4.32) id 1Cw9xk-0001KO-Hc for mpls@megatron.ietf.org; Tue, 01 Feb 2005 21:09:48 -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 VAA01341 for ; Tue, 1 Feb 2005 21:09:45 -0500 (EST) Received: from rtp-iport-1.cisco.com ([64.102.122.148]) by ietf-mx.ietf.org with esmtp (Exim 4.33) id 1CwAG0-00085p-JK for mpls@ietf.org; Tue, 01 Feb 2005 21:28:41 -0500 Received: from rtp-core-2.cisco.com (64.102.124.13) by rtp-iport-1.cisco.com with ESMTP; 01 Feb 2005 21:19:12 -0500 X-BrightmailFiltered: true X-Brightmail-Tracker: AAAAAA== Received: from fruitpie.cisco.com (IDENT:mirapoint@fruitpie.cisco.com [64.102.16.27]) by rtp-core-2.cisco.com (8.12.10/8.12.6) with ESMTP id j1229DQN022724; Tue, 1 Feb 2005 21:09:15 -0500 (EST) Received: from [128.107.178.86] (dhcp-128-107-178-86.cisco.com [128.107.178.86]) by fruitpie.cisco.com (MOS 3.4.6-GR) with ESMTP id BEZ97472; Tue, 1 Feb 2005 18:09:12 -0800 (PST) Message-ID: <42003648.8030206@cisco.com> Date: Tue, 01 Feb 2005 21:09:12 -0500 From: "W. Mark Townsley" User-Agent: Mozilla/5.0 (Windows; U; Windows NT 5.0; en-US; rv:1.7) Gecko/20040616 X-Accept-Language: en-us, en MIME-Version: 1.0 To: mpls@ietf.org Content-Type: text/plain; charset=us-ascii; format=flowed Content-Transfer-Encoding: 7bit X-Spam-Score: 0.0 (/) X-Scan-Signature: 7a6398bf8aaeabc7a7bb696b6b0a2aad Content-Transfer-Encoding: 7bit Subject: [mpls] MPLS over L2TPv3 as WG item 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: 856eb5f76e7a34990d1d457d8e8e5b7f Content-Transfer-Encoding: 7bit As requested by Loa at the last MPLS WG meeting, I have renamed the MPLS over L2TPv3 draft as follows: draft-townsley-mpls-over-l2tpv3-00.txt With consensus confirmation from this list, I would like to resubmit this version as a WG item (preferably before the upcoming deadline for the next meeting). Thanks, - Mark _______________________________________________ mpls mailing list mpls@lists.ietf.org https://www1.ietf.org/mailman/listinfo/mpls From mpls-bounces@ietf.org Tue Feb 1 23:23:45 2005 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 XAA23970; Tue, 1 Feb 2005 23:23:45 -0500 (EST) Received: from megatron.ietf.org ([132.151.6.71]) by ietf-mx.ietf.org with esmtp (Exim 4.33) id 1CwCLh-0002a7-Lz; Tue, 01 Feb 2005 23:42:42 -0500 Received: from localhost.localdomain ([127.0.0.1] helo=megatron.ietf.org) by megatron.ietf.org with esmtp (Exim 4.32) id 1CwC1g-00062F-Sz; Tue, 01 Feb 2005 23:22:00 -0500 Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org) by megatron.ietf.org with esmtp (Exim 4.32) id 1CwByq-0005Eg-Qz for mpls@megatron.ietf.org; Tue, 01 Feb 2005 23:19:04 -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 XAA23631 for ; Tue, 1 Feb 2005 23:19:03 -0500 (EST) Received: from ind-iport-1-sec.cisco.com ([64.104.129.9]) by ietf-mx.ietf.org with esmtp (Exim 4.33) id 1CwCH7-0002T4-88 for mpls@ietf.org; Tue, 01 Feb 2005 23:37:59 -0500 Received: from india-core-1.cisco.com (64.104.129.221) by ind-iport-1-sec.cisco.com with ESMTP; 02 Feb 2005 09:56:47 +0530 X-BrightmailFiltered: true X-Brightmail-Tracker: AAAAAA== Received: from ind-mira-01.cisco.com (IDENT:mirapoint@ind-mira-01.cisco.com [64.104.129.12]) by india-core-1.cisco.com (8.12.10/8.12.6) with ESMTP id j124ILQc019133 for ; Wed, 2 Feb 2005 04:18:21 GMT Received: from agoyalw2k (dhcp-10-77-7-158.cisco.com [10.77.7.158]) by ind-mira-01.cisco.com (MOS 3.4.6-GR) with ESMTP id AIH96884; Wed, 2 Feb 2005 09:42:55 +0530 (IST) Message-Id: <200502020412.AIH96884@ind-mira-01.cisco.com> From: "Amit Goyal \(agoyal\)" To: Date: Wed, 2 Feb 2005 09:48:27 +0530 MIME-Version: 1.0 X-Mailer: Microsoft Office Outlook, Build 11.0.5510 X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2800.1106 Thread-Index: AcUI3j4q4B+5nR12Q8CEKeNoBVdw1w== X-Spam-Score: 0.2 (/) X-Scan-Signature: ec7c6dab5a62df223002ae71b5179d41 Subject: [mpls] lsp trace route question X-BeenThere: mpls@lists.ietf.org X-Mailman-Version: 2.1.5 Precedence: list Reply-To: agoyal@cisco.com List-Id: Multi-Protocol Label Switching WG List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Content-Type: multipart/mixed; boundary="===============0770760413==" Sender: mpls-bounces@ietf.org Errors-To: mpls-bounces@ietf.org X-Spam-Score: 0.5 (/) X-Scan-Signature: bacfc6c7290e34d410f9bc22b825ce96 This is a multi-part message in MIME format. --===============0770760413== Content-Type: multipart/alternative; boundary="----=_NextPart_000_0003_01C5090C.58382820" This is a multi-part message in MIME format. ------=_NextPart_000_0003_01C5090C.58382820 Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit Hi All, I have a question for lsp trace route in scenario where label stack of depth n ( n>1) is required to reach the destination. In such cases how many FEC elements would be there in FEC stack of echo request? If there would be only one FEC element corresponding to destination (not tunnel end point) then how does the intermediate LSR makes the FEC to label matching processing (section 4.3 of draft-ietf-mpls-lsp-ping-70). I am assuming the intermediate LSR is not aware of the destination FEC. If the FEC stack contains same number of elements as there are tunnels then FEC to label matching processing could be done. so is it mandatory in case of tunnels that the trace route echo request contains all tunnel endpoints the LSP traverses. While "ping" mode echo request can contain only destination FEC element as only egress LSR control plane is going to do all that check. Another question I have is why the FEC matching is started from bottom of both the stacks, as intermediate router would not be aware of the bottom most label and FEC and as per section 4.3 step 3 in this case it would reply with a return code 4 "Replying router has no mapping for the FEC at stack-depth" Thanks in advance Amit Goyal ------=_NextPart_000_0003_01C5090C.58382820 Content-Type: text/html; charset="us-ascii" Content-Transfer-Encoding: quoted-printable

Hi All,

 

I have a question for lsp trace route in scenario = where label stack of depth n ( n>1) is required to reach the destination. = In such cases how many FEC elements would be there in FEC stack of echo request? = If there would be only one FEC element corresponding to destination (not = tunnel end point) then how does the intermediate LSR makes the FEC to label = matching processing (section 4.3 of = draft-ietf-mpls-lsp-ping-70).

 

I am assuming the intermediate LSR is not aware of = the destination FEC.

 

If the FEC stack contains same number of elements as = there are tunnels then FEC to label matching processing could be done… = so is it mandatory in case of tunnels that the trace route echo request contains = all tunnel endpoints the LSP traverses. While “ping” mode echo = request can contain only destination FEC element as only egress LSR control = plane is going to do all that check.

 

Another question I have is why the FEC matching is = started from bottom of both the stacks, as intermediate router would not be = aware of the bottom most label and FEC and as per section 4.3 step 3 in this case = it would reply with a return code 4 “Replying router has no mapping = for the FEC at stack-depth”

 

Thanks in advance

Amit Goyal

 

 

------=_NextPart_000_0003_01C5090C.58382820-- --===============0770760413== 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 --===============0770760413==-- From mpls-bounces@ietf.org Wed Feb 2 13:18:40 2005 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 NAA08437; Wed, 2 Feb 2005 13:18:40 -0500 (EST) Received: from megatron.ietf.org ([132.151.6.71]) by ietf-mx.ietf.org with esmtp (Exim 4.33) id 1CwPNq-0008Oi-W9; Wed, 02 Feb 2005 13:37:47 -0500 Received: from localhost.localdomain ([127.0.0.1] helo=megatron.ietf.org) by megatron.ietf.org with esmtp (Exim 4.32) id 1CwP0f-0005SU-Lw; Wed, 02 Feb 2005 13:13:49 -0500 Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org) by megatron.ietf.org with esmtp (Exim 4.32) id 1CwOt7-0003S8-Na for mpls@megatron.ietf.org; Wed, 02 Feb 2005 13:06:02 -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 NAA06884 for ; Wed, 2 Feb 2005 13:05:56 -0500 (EST) Received: from ranger.systems.pipex.net ([62.241.162.32]) by ietf-mx.ietf.org with esmtp (Exim 4.33) id 1CwPBU-0007rg-P7 for mpls@ietf.org; Wed, 02 Feb 2005 13:25:03 -0500 Received: from dnni.com (81-178-2-190.dsl.pipex.com [81.178.2.190]) by ranger.systems.pipex.net (Postfix) with ESMTP id DE8E6E000328; Wed, 2 Feb 2005 18:05:25 +0000 (GMT) Received: from Puppy ([212.43.203.33] RDNS failed) by dnni.com with Microsoft SMTPSVC(6.0.3790.211); Wed, 2 Feb 2005 18:05:25 +0000 Message-ID: <013101c50951$f26f7980$70cb2bd4@Puppy> From: "Adrian Farrel" To: "George Swallow" , "Loa Andersson" References: <20050202000815.BE66C1FC349@swallow-mac.cisco.com> Subject: Re: [mpls] Time to set the MPLS Agenda Date: Wed, 2 Feb 2005 16:31:26 -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: 02 Feb 2005 18:05:26.0301 (UTC) FILETIME=[C5A764D0:01C50951] X-Spam-Score: 0.1 (/) X-Scan-Signature: e1e48a527f609d1be2bc8d8a70eb76cb Content-Transfer-Encoding: 7bit Cc: mpls@ietf.org, Zafar Ali 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: 4adaf050708fb13be3316a9eee889caa Content-Transfer-Encoding: 7bit Hi, We'd like a brief slot for draft-yasukawa-mpls-p2mp-lsp-ping-01.txt (just submitted). 10 minutes is plenty (5 minutes if you're squeezed). We need to: - update on the status of the draft - get agreement from the WG that what we're doing to LSP Ping is OK Cheers, Adrian ----- Original Message ----- From: "George Swallow" To: Sent: Wednesday, February 02, 2005 12:08 AM Subject: [mpls] Time to set the MPLS Agenda > Please forward your agenda requests (including an estimate of time) to > Loa and me. > > Thanks, > > ...George > > ======================================================================== > George Swallow Cisco Systems (978) 936-1398 > 1414 Massachusetts Avenue > Boxborough, MA 01719 > > > > _______________________________________________ > mpls mailing list > mpls@lists.ietf.org > https://www1.ietf.org/mailman/listinfo/mpls > > _______________________________________________ mpls mailing list mpls@lists.ietf.org https://www1.ietf.org/mailman/listinfo/mpls From mpls-bounces@ietf.org Wed Feb 2 16:57:12 2005 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 QAA12352; Wed, 2 Feb 2005 16:57:12 -0500 (EST) Received: from megatron.ietf.org ([132.151.6.71]) by ietf-mx.ietf.org with esmtp (Exim 4.33) id 1CwSnM-0002F7-FT; Wed, 02 Feb 2005 17:16:20 -0500 Received: from localhost.localdomain ([127.0.0.1] helo=megatron.ietf.org) by megatron.ietf.org with esmtp (Exim 4.32) id 1CwSAR-0008OB-M3; Wed, 02 Feb 2005 16:36:07 -0500 Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org) by megatron.ietf.org with esmtp (Exim 4.32) id 1CwRMV-0001My-Tv for mpls@megatron.ietf.org; Wed, 02 Feb 2005 15:44:31 -0500 Received: from boreas.isi.edu (boreas.isi.edu [128.9.160.161]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id PAA26983 for ; Wed, 2 Feb 2005 15:44:27 -0500 (EST) Received: from ISI.EDU (adma.isi.edu [128.9.160.239]) by boreas.isi.edu (8.11.6p2+0917/8.11.2) with ESMTP id j12Kg5Q17239; Wed, 2 Feb 2005 12:42:05 -0800 (PST) Message-Id: <200502022042.j12Kg5Q17239@boreas.isi.edu> To: ietf-announce@ietf.org From: rfc-editor@rfc-editor.org Mime-Version: 1.0 Content-Type: Multipart/Mixed; Boundary=NextPart Date: Wed, 02 Feb 2005 12:42:05 -0800 X-ISI-4-30-3-MailScanner: Found to be clean X-MailScanner-From: rfc-ed@isi.edu Cc: mpls@ietf.org, rfc-editor@rfc-editor.org Subject: [mpls] RFC 3988 on Maximum Transmission Unit Signalling Extensions for the Label Distribution Protocol 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: -14.6 (--------------) X-Scan-Signature: 5ebbf074524e58e662bc8209a6235027 --NextPart A new Request for Comments is now available in online RFC libraries. RFC 3988 Title: Maximum Transmission Unit Signalling Extensions for the Label Distribution Protocol Author(s): B. Black, K. Kompella Status: Experimental Date: January 2005 Mailbox: ben@layer8.net, kireeti@juniper.net Pages: 9 Characters: 18841 Updates/Obsoletes/SeeAlso: None I-D Tag: draft-ietf-mpls-ldp-mtu-extensions-03.txt URL: ftp://ftp.rfc-editor.org/in-notes/rfc3988.txt Proper functioning of RFC 1191 path Maximum Transmission Unit (MTU) discovery requires that IP routers have knowledge of the MTU for each link to which they are connected. As currently specified, the Label Distribution Protocol (LDP) does not have the ability to signal the MTU for a Label Switched Path (LSP) to the ingress Label Switching Router (LSR). In the absence of this functionality, the MTU for each LSP must be statically configured by network operators or by equivalent off-line mechanisms. This document specifies experimental extensions to LDP in support of LSP MTU discovery. This document is a product of the Multiprotocol Label Switching Working Group of the IETF. This memo defines an Experimental Protocol for the Internet community. It does not specify an Internet standard of any kind. Discussion and suggestions for improvement are requested. Distribution of this memo is unlimited. This announcement is sent to the IETF list and the RFC-DIST list. Requests to be added to or deleted from the IETF distribution list should be sent to IETF-REQUEST@IETF.ORG. Requests to be added to or deleted from the RFC-DIST distribution list should be sent to RFC-DIST-REQUEST@RFC-EDITOR.ORG. Details on obtaining RFCs via FTP or EMAIL may be obtained by sending an EMAIL message to rfc-info@RFC-EDITOR.ORG with the message body help: ways_to_get_rfcs. For example: To: rfc-info@RFC-EDITOR.ORG Subject: getting rfcs help: ways_to_get_rfcs Requests for special distribution should be addressed to either the author of the RFC in question, or to RFC-Manager@RFC-EDITOR.ORG. Unless specifically noted otherwise on the RFC itself, all RFCs are for unlimited distribution. Submissions for Requests for Comments should be sent to RFC-EDITOR@RFC-EDITOR.ORG. Please consult RFC 2223, Instructions to RFC Authors, for further information. Joyce K. Reynolds and Sandy Ginoza USC/Information Sciences Institute ... Below is the data which will enable a MIME compliant Mail Reader implementation to automatically retrieve the ASCII version of the RFCs. --NextPart Content-Type: Multipart/Alternative; Boundary="OtherAccess" --OtherAccess Content-Type: Message/External-body; access-type="mail-server"; server="RFC-INFO@RFC-EDITOR.ORG" Content-Type: text/plain Content-ID: <050202124048.RFC@RFC-EDITOR.ORG> RETRIEVE: rfc DOC-ID: rfc3988 --OtherAccess Content-Type: Message/External-body; name="rfc3988.txt"; site="ftp.isi.edu"; access-type="anon-ftp"; directory="in-notes" Content-Type: text/plain Content-ID: <050202124048.RFC@RFC-EDITOR.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 Fri Feb 4 04:57:15 2005 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 EAA07789; Fri, 4 Feb 2005 04:57:15 -0500 (EST) Received: from megatron.ietf.org ([132.151.6.71]) by ietf-mx.ietf.org with esmtp (Exim 4.33) id 1Cx0W0-0003jE-26; Fri, 04 Feb 2005 05:16:41 -0500 Received: from localhost.localdomain ([127.0.0.1] helo=megatron.ietf.org) by megatron.ietf.org with esmtp (Exim 4.32) id 1Cx06j-0006sV-49; Fri, 04 Feb 2005 04:50:33 -0500 Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org) by megatron.ietf.org with esmtp (Exim 4.32) id 1Cx025-0004fO-BV for mpls@megatron.ietf.org; Fri, 04 Feb 2005 04:45:45 -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 EAA06922 for ; Fri, 4 Feb 2005 04:45:42 -0500 (EST) Received: from [80.86.78.228] (helo=tbdns.testbed.local) by ietf-mx.ietf.org with esmtp (Exim 4.33) id 1Cx0Kn-0003PD-Iw for mpls@ietf.org; Fri, 04 Feb 2005 05:05:08 -0500 Received: from [192.168.230.15] ([80.86.78.226]) (authenticated bits=0) by tbdns.testbed.local (8.12.8/8.12.8) with ESMTP id j149dupt010821 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO); Fri, 4 Feb 2005 10:40:01 +0100 Message-ID: <420343B3.1050808@pi.se> Date: Fri, 04 Feb 2005 10:43:15 +0100 From: Loa Andersson User-Agent: Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US; rv:1.7.2) Gecko/20040803 X-Accept-Language: en-us, en MIME-Version: 1.0 To: "W. Mark Townsley" Subject: Re: [mpls] MPLS over L2TPv3 as WG item References: <42003648.8030206@cisco.com> In-Reply-To: <42003648.8030206@cisco.com> Content-Type: text/plain; charset=us-ascii; format=flowed Content-Transfer-Encoding: 7bit X-Spam-Score: 0.0 (/) X-Scan-Signature: 4adaf050708fb13be3316a9eee889caa Content-Transfer-Encoding: 7bit Cc: mpls@ietf.org X-BeenThere: mpls@lists.ietf.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Multi-Protocol Label Switching WG List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Sender: mpls-bounces@ietf.org Errors-To: mpls-bounces@ietf.org X-Spam-Score: 0.0 (/) X-Scan-Signature: 8b431ad66d60be2d47c7bfeb879db82c Content-Transfer-Encoding: 7bit Working Group, the reception of the draft was a wee bit ambigious (some no, some no need and some yes), with some service providers strongly in favor. We would like to poll the working group on whether we want to make draft-townsley-mpls-over-l2tpv3-00.txt a wg doc. To make it possible to publish a working group document, given a rough consensus in the wg, we need to have comments Feb 11. Send comments to the mailing list or wg chairs. We are looking for both positive and negative comments. /Loa and George W. Mark Townsley wrote: > > As requested by Loa at the last MPLS WG meeting, I have renamed the MPLS > over L2TPv3 draft as follows: > > draft-townsley-mpls-over-l2tpv3-00.txt > > With consensus confirmation from this list, I would like to resubmit > this version as a WG item (preferably before the upcoming deadline for > the next meeting). > > Thanks, > > - Mark > > > _______________________________________________ > mpls mailing list > mpls@lists.ietf.org > https://www1.ietf.org/mailman/listinfo/mpls > -- Loa Andersson Principal Networking Architect Acreo AB phone: +46 8 632 77 14 Isafjordsgatan 22 mobile: +46 739 81 21 64 Kista, Sweden email: loa.andersson@acreo.se loa@pi.se _______________________________________________ mpls mailing list mpls@lists.ietf.org https://www1.ietf.org/mailman/listinfo/mpls From mpls-bounces@ietf.org Fri Feb 4 06:36:17 2005 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 GAA14631; Fri, 4 Feb 2005 06:36:17 -0500 (EST) Received: from megatron.ietf.org ([132.151.6.71]) by ietf-mx.ietf.org with esmtp (Exim 4.33) id 1Cx23r-0006M8-Ne; Fri, 04 Feb 2005 06:55:44 -0500 Received: from localhost.localdomain ([127.0.0.1] helo=megatron.ietf.org) by megatron.ietf.org with esmtp (Exim 4.32) id 1Cx1k0-0000Ac-F1; Fri, 04 Feb 2005 06:35:12 -0500 Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org) by megatron.ietf.org with esmtp (Exim 4.32) id 1CwS7b-0006XB-21; Wed, 02 Feb 2005 16:33:12 -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 QAA08537; Wed, 2 Feb 2005 16:33:03 -0500 (EST) Received: from out014pub.verizon.net ([206.46.170.46] helo=out014.verizon.net) by ietf-mx.ietf.org with esmtp (Exim 4.33) id 1CwSPx-0000pS-Jf; Wed, 02 Feb 2005 16:52:11 -0500 Received: from cow ([4.12.170.137]) by out014.verizon.net (InterMail vM.5.01.06.06 201-253-122-130-106-20030910) with ESMTP id <20050202213259.KPLG28388.out014.verizon.net@cow>; Wed, 2 Feb 2005 15:32:59 -0600 From: "Dawn " To: Date: Wed, 2 Feb 2005 15:32:57 -0600 Message-ID: <006e01c5096e$c39324a0$f922fea9@cow> MIME-Version: 1.0 X-Priority: 3 (Normal) X-MSMail-Priority: Normal X-Mailer: Microsoft Outlook, Build 10.0.6626 Importance: Normal X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2900.2180 X-Authentication-Info: Submitted using SMTP AUTH at out014.verizon.net from [4.12.170.137] at Wed, 2 Feb 2005 15:32:58 -0600 X-Spam-Score: 0.5 (/) X-Scan-Signature: ef89f32bda94ec20fe57b465fe684d49 X-Mailman-Approved-At: Fri, 04 Feb 2005 06:35:10 -0500 Subject: [mpls] MobiQuitous 2005 - Call for Papers 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="===============0648325397==" Sender: mpls-bounces@ietf.org Errors-To: mpls-bounces@ietf.org X-Spam-Score: 0.5 (/) X-Scan-Signature: 33fc46667f70a87403df4cb21ee8343c This is a multi-part message in MIME format. --===============0648325397== Content-Type: multipart/alternative; boundary="----=_NextPart_000_006F_01C5093C.78F8B4A0" This is a multi-part message in MIME format. ------=_NextPart_000_006F_01C5093C.78F8B4A0 Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: quoted-printable MobiQuitous 2005 - CALL FOR PAPERS =20 The Second Annual International Conference on Mobile and Ubiquitous = Systems: Networking and Services =20 http://www.mobiquitous.org =20 July 17-21, 2005, San Diego, California =20 ABSTRACT REGISTRATION DEADLINE: February 16, 2005 FULL PAPER SUBMISSION DEADLINE: February 23, 2005 =20 Sponsored by: =20 CreateNet (www.create-net.it) and ICST =20 Technically Co-Sponsored by IEEE Computer Society (Pending) Technically Co-Sponsored by IEEE Communications Society (Pending) In Cooperation with ACM SIGMOBILE (Pending) Technically Co-Sponsored by AAAI (Pending) =20 Proceedings to be published by IEEE Computer Society Press and to be = made available on IEEE Explore =20 **************************************** =20 The combination of mobile and ubiquitous computing is emerging as a promising new paradigm with the goal to provide computing and communication services all the time, everywhere, transparently and = invisibly to the user, using devices embedded in the surrounding physical environment. In this context, the communication devices, the objects = with which they interact, or both may be mobile. The implementation of such a paradigm requires advances in wireless network technologies and devices, development of infrastructures supporting cognitive environments, and discovery and identification of ubiquitous computing applications and services. =20 The second Annual International Conference on Mobile and Ubiquitous = Systems: networking and services (Mobiquitous-05) will cover all these aspects, representing a forum where practitioners and researchers coming from the many areas involved in ubiquitous solutions design and = deployment will be able to interact exchanging the cross-layer experiences needed = to build the overall ubiquitous systems. Areas addressed by the conference include: applications, service-oriented computing, middleware, = networking, agents, knowledge management and databases. =20 PAPERS: Technical papers describing original, previously unpublished research, not currently under review by another conference or journal, = are solicited. The conference is interested in contributions addressing all = the areas associated with mobile and ubiquitous architectures, = infrastructure and services. Technical works clearly identifying how the specific contributions fit to an overall working solution are particularly of interest. Topics include, but are not limited to, the following: =20 * Ubiquitous architectures and systems * Wearable computing and personal area network * Wireless technologies for mobile and ubiquitous (Bluetooth, ZigBee, 802.15.x, WiFi) * Incentive-based deployment of ad hoc networks * Reconfigurability and personalization of wireless network * Service discovery mechanisms, knowledge discovery, matching and composition mechanisms * Wireless/mobile service management and delivery * Security, privacy and social issues of mobile and ubiquitous systems * Peer-to-peer knowledge management * Emerging industrial/business scenarios * Multimodal interfaces (speech, video kinetic, tactile) * Smart spaces * Ad hoc and sensor networking * Localization and tracking * Context and location aware application * Multimedia encoding and transcoding * Middleware services * Agent technologies in ubiquitous, wearable, andmobile systems * Hardware and software platforms for ubiquitous systems, and testbeds * User interfaces * Toolkits, development environments, and languages for ubiquitous computing * Ontologies for mobile and ubiquitous computing =20 SUBMISSION INSTRUCTIONS: All paper submissions will be handled electronically (see the conference web page for details). Authors should prepare a Portable Document Format (PDF) or postscript version of their = full paper. Papers must not exceed 8 pages double column (US Letter size, 8.5 x 11 inches) including text, figures and references. The font size = must be at least 10 points. The deadline for registering the title and the abstract of the paper with our electronic submission system is February = 2, 2005. The deadline for submitting the actual paper is February 9, 2005. All deadlines are 11:59PM PST. =20 PUBLICATION: All submitted papers will be rigorously reviewed by = technical program committee members. Accepted papers will be published in the conference proceedings. Papers of particular merit will be proposed for publication in a ACM/Kluwer MONET special issue. =20 WORKSHOPS: Proposals for one-day workshops to be held in conjunction = with the conference are solicited. A maximum of 2 pages should be submitted which include the workshop name, its scope and a list of topic of = interests. Proposals should be submitted to both the Workshop co-Chairs by December 17 2004. =20 DEMOS: Proposals for research and industrial demos are solicited. A = maximum of 2 pages should be submitted which include a description of the demo and needed resources from the conference organizers. Proposals = should be submitted to Dr. Ramiro Liscano (Demo Chair) rliscano@ieee.org by May 29th, 2005. =20 IMPORTANT DATES: Paper registration deadline: February 16, 2005 Full paper submission deadline: February 23, 2005 Notification of acceptance: April 29, 2005 Camera-ready version due: May 15, 2005 =20 ORGANIZING COMMITTEE =20 General Chair: Ramesh Rao (Univ. of California, San Diego) =20 General Co-Vice-Chairs: Chiara Petrioli (Universit di Roma La Sapienza) Krishna Sivalingam (University of Maryland, Baltimore County) =20 Technical Program Co-Chairs: =20 Networking: Suresh Singh (Portland State University) Philippe Bonnet (University of Copenhagen) =20 Services/Knowledge Management: Anupam Joshi (University of Maryland, Baltimore County) Ryusuke Masuoka (Fujitsu Labs of America) =20 Publicity Co-Chairs: Andreas Savvides (Yale University) and Mohamed Younis (University of Maryland, Baltimore County) =20 Panels Chairs: TBA =20 Workshop Chairs: Stefano Basagni (Northeastern University) Prithwish Basu (BBN Technologies) =20 Demos Chair: Ramiro Liscano (University of Ottawa) =20 Publications Chair: Antonis Kalis (Athens Information Technology) =20 Local Arrangements Chair:=20 Kang Wang, Qualcomm Inc. =20 Finance Chair: Karen Decker (ICST Texas,USA) =20 Accommodations Chair: Kathy Kunz (ICST California,USA) =20 Registration Chair:=20 Vishal Anand, SUNY College at Brockport =20 Steering Committee:=20 Imrich Chlamtac (CreateNet, Inc.), Chair Michele Zorzi (Universita di Padova) =20 ------=_NextPart_000_006F_01C5093C.78F8B4A0 Content-Type: text/html; charset="us-ascii" Content-Transfer-Encoding: quoted-printable

MobiQuitous 2005 - CALL FOR PAPERS

 

The Second Annual International Conference on Mobile and Ubiquitous Systems: Networking and Services

 

http://www.mobiquitous.org

 

July 17-21, 2005, San Diego, California

 

ABSTRACT REGISTRATION DEADLINE: February 16, 2005

FULL PAPER SUBMISSION DEADLINE: February 23, 2005

 

Sponsored by:

 

CreateNet (www.create-net.it) and ICST

 

Technically Co-Sponsored by IEEE Computer Society (Pending)

Technically Co-Sponsored by IEEE Communications Society (Pending)

In Cooperation with ACM SIGMOBILE (Pending)

Technically Co-Sponsored by AAAI (Pending)

 

Proceedings to be published by IEEE Computer Society Press and to be made available = on IEEE Explore

 

****************************************

 

The combination of mobile and ubiquitous computing is emerging as a = promising new paradigm with the goal to provide computing and

communication services all the time, everywhere, transparently and invisibly to the = user, using devices embedded in the surrounding physical

environment. In this context, the communication devices, the objects with which they interact, or both may be mobile. The implementation of such a paradigm = requires advances in wireless network technologies and devices, development of infrastructures supporting cognitive environments, and

discovery and identification of ubiquitous computing applications and = services.

 

The second Annual International Conference on Mobile and = Ubiquitous Systems: networking and services (Mobiquitous-05) will cover all = these

aspects, representing a forum where practitioners and researchers coming from the = many areas involved in ubiquitous solutions design and deployment will be = able to interact exchanging the cross-layer experiences needed to build the = overall ubiquitous systems. Areas addressed by the conference include: = applications, service-oriented computing, middleware, networking, agents, knowledge management and databases.

 

PAPERS: Technical papers describing original, previously unpublished research, = not currently under review by another conference or journal, = are

solicited. The conference is interested in contributions addressing all the areas associated with mobile and ubiquitous architectures, infrastructure and services. Technical works clearly identifying how the specific = contributions fit to an overall working solution are particularly of interest. Topics include, but are not limited to, the following:

 

* Ubiquitous architectures and systems

* Wearable computing and personal area network

* Wireless technologies for mobile and ubiquitous (Bluetooth, = ZigBee,

802.15.x, WiFi)

* Incentive-based deployment of ad hoc networks

* Reconfigurability and personalization of wireless = network

* Service discovery mechanisms, knowledge discovery, matching = and

composition mechanisms

* Wireless/mobile service management and delivery

* Security, privacy and social issues of mobile and ubiquitous = systems

* Peer-to-peer knowledge management

* Emerging industrial/business scenarios

* Multimodal interfaces (speech, video kinetic, tactile)

* Smart spaces

* Ad hoc and sensor networking

* Localization and tracking

* Context and location aware application

* Multimedia encoding and transcoding

* Middleware services

* Agent technologies in ubiquitous, wearable, andmobile = systems

* Hardware and software platforms for ubiquitous systems, and = testbeds

* User interfaces

* Toolkits, development environments, and languages for = ubiquitous

computing

* Ontologies for mobile and ubiquitous computing

 

SUBMISSION INSTRUCTIONS:  All paper submissions will be handled electronically = (see the conference web page for details). Authors should

prepare a Portable Document Format (PDF) or postscript version of their full paper.  Papers must not exceed 8 pages double column (US Letter = size,

8.5 x 11 inches) including text, figures and references. The font size must = be at least 10 points. The deadline for registering the title and = the

abstract of the paper with our electronic submission system is = February 2, 2005. The deadline for submitting the actual = paper is February 9, 2005.

All deadlines are 11:59PM PST.

 

PUBLICATION: All submitted papers will be rigorously reviewed by technical program = committee members. Accepted papers will be published in the conference = proceedings.  Papers of particular merit will be proposed for publication in a = ACM/Kluwer MONET special issue.

 

WORKSHOPS: Proposals for one-day workshops to be held in conjunction with the = conference are solicited.  A maximum of 2 pages should be submitted which = include the workshop name, its scope and a list of topic of interests.  = Proposals should be submitted to both the Workshop co-Chairs

by December 17 2004.

 

DEMOS: Proposals for research and industrial demos are solicited.  A = maximum of 2 pages should be submitted which include a description of = the

demo and needed resources from the conference organizers. Proposals should be submitted to Dr. Ramiro Liscano (Demo Chair) rliscano@ieee.org by = May 29th, 2005.

 

IMPORTANT DATES:

Paper registration deadline:  February 16, 2005

Full paper submission deadline:      = February 23, 2005

Notification of acceptance:  April 29, 2005

Camera-ready version due:  May 15, 2005

 

ORGANIZING COMMITTEE

 

General Chair:

Ramesh Rao (Univ. of California, San Diego)

 

General Co-Vice-Chairs:

Chiara Petrioli (Universit di Roma La Sapienza)

Krishna Sivalingam (University of Maryland, Baltimore County)

 

Technical Program Co-Chairs:

 

Networking:

Suresh Singh (Portland State University)

Philippe Bonnet (University of Copenhagen)

 

Services/Knowledge Management:

Anupam Joshi (University of Maryland, Baltimore County)

Ryusuke Masuoka (Fujitsu Labs of America)

 

Publicity Co-Chairs:

Andreas Savvides (Yale University) and

Mohamed Younis (University of Maryland, Baltimore County)

 

Panels Chairs: TBA

 

Workshop Chairs:

Stefano Basagni (Northeastern University)

Prithwish Basu  (BBN Technologies)

 

Demos Chair:

Ramiro Liscano (University of Ottawa)

 

Publications Chair:

Antonis Kalis (Athens Information Technology)

 

Local Arrangements Chair:

Kang Wang, Qualcomm Inc.

 

Finance Chair:

Karen Decker (ICST Texas,USA)

 

Accommodations Chair:

Kathy Kunz (ICST California,USA)

 

Registration Chair:

Vishal Anand, SUNY College at Brockport

 

Steering Committee:

Imrich Chlamtac (CreateNet, Inc.), Chair

Michele Zorzi (Universita di Padova)

 

------=_NextPart_000_006F_01C5093C.78F8B4A0-- --===============0648325397== 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 --===============0648325397==-- From mpls-bounces@ietf.org Fri Feb 4 08:59:30 2005 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 IAA27628; Fri, 4 Feb 2005 08:59:30 -0500 (EST) Received: from megatron.ietf.org ([132.151.6.71]) by ietf-mx.ietf.org with esmtp (Exim 4.33) id 1Cx4IR-00027r-CV; Fri, 04 Feb 2005 09:18:57 -0500 Received: from localhost.localdomain ([127.0.0.1] helo=megatron.ietf.org) by megatron.ietf.org with esmtp (Exim 4.32) id 1Cx3w3-0005xG-Oq; Fri, 04 Feb 2005 08:55:47 -0500 Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org) by megatron.ietf.org with esmtp (Exim 4.32) id 1Cx3uU-0005IU-Iu for mpls@megatron.ietf.org; Fri, 04 Feb 2005 08:54:10 -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 IAA27331 for ; Fri, 4 Feb 2005 08:54:08 -0500 (EST) Received: from ams-iport-1.cisco.com ([144.254.224.140]) by ietf-mx.ietf.org with esmtp (Exim 4.33) id 1Cx4DF-00021Z-KX for mpls@ietf.org; Fri, 04 Feb 2005 09:13:35 -0500 Received: from ams-core-1.cisco.com (144.254.224.150) by ams-iport-1.cisco.com with ESMTP; 04 Feb 2005 15:04:27 +0100 X-BrightmailFiltered: true X-Brightmail-Tracker: AAAAAA== Received: from zaliwxp (che-vpn-cluster-2-70.cisco.com [10.86.242.70]) by ams-core-1.cisco.com (8.12.10/8.12.6) with ESMTP id j14DrXiN004408; Fri, 4 Feb 2005 14:53:34 +0100 (MET) Message-Id: <200502041353.j14DrXiN004408@ams-core-1.cisco.com> From: "Zafar Ali" To: "'Loa Andersson'" , "'W. Mark Townsley'" Subject: RE: [mpls] MPLS over L2TPv3 as WG item Date: Fri, 4 Feb 2005 08:53:33 -0500 MIME-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit X-Mailer: Microsoft Office Outlook, Build 11.0.5510 X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2800.1441 Thread-Index: AcUKoCHqvpEpMM6SSZOs3gc89DpaNwAILHqA In-Reply-To: <420343B3.1050808@pi.se> X-Spam-Score: 0.0 (/) X-Scan-Signature: 4b800b1eab964a31702fa68f1ff0e955 Content-Transfer-Encoding: 7bit Cc: mpls@ietf.org X-BeenThere: mpls@lists.ietf.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Multi-Protocol Label Switching WG List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Sender: mpls-bounces@ietf.org Errors-To: mpls-bounces@ietf.org X-Spam-Score: 0.0 (/) X-Scan-Signature: d8ae4fd88fcaf47c1a71c804d04f413d Content-Transfer-Encoding: 7bit Yes, strongly in favor Thanks Regards... Zafar > -----Original Message----- > From: mpls-bounces@lists.ietf.org > [mailto:mpls-bounces@lists.ietf.org] On Behalf Of Loa Andersson > Sent: Friday, February 04, 2005 4:43 AM > To: W. Mark Townsley > Cc: mpls@ietf.org > Subject: Re: [mpls] MPLS over L2TPv3 as WG item > > Working Group, > > the reception of the draft was a wee bit ambigious (some no, > some no need and some yes), with some service providers > strongly in favor. > We would like to poll the working group on whether we want to > make draft-townsley-mpls-over-l2tpv3-00.txt a wg doc. > > To make it possible to publish a working group document, > given a rough consensus in the wg, we need to have comments Feb 11. > > Send comments to the mailing list or wg chairs. We are > looking for both positive and negative comments. > > /Loa and George > > W. Mark Townsley wrote: > > > > > As requested by Loa at the last MPLS WG meeting, I have renamed the > > MPLS over L2TPv3 draft as follows: > > > > draft-townsley-mpls-over-l2tpv3-00.txt > > > > With consensus confirmation from this list, I would like to > resubmit > > this version as a WG item (preferably before the upcoming > deadline for > > the next meeting). > > > > Thanks, > > > > - Mark > > > > > > _______________________________________________ > > mpls mailing list > > mpls@lists.ietf.org > > https://www1.ietf.org/mailman/listinfo/mpls > > > > -- > Loa Andersson > > Principal Networking Architect > Acreo AB phone: +46 8 632 77 14 > Isafjordsgatan 22 mobile: +46 739 81 21 64 > Kista, Sweden email: loa.andersson@acreo.se > loa@pi.se > > _______________________________________________ > mpls mailing list > mpls@lists.ietf.org > https://www1.ietf.org/mailman/listinfo/mpls > _______________________________________________ mpls mailing list mpls@lists.ietf.org https://www1.ietf.org/mailman/listinfo/mpls From mpls-bounces@ietf.org Fri Feb 4 09:25:30 2005 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 JAA00646; Fri, 4 Feb 2005 09:25:30 -0500 (EST) Received: from megatron.ietf.org ([132.151.6.71]) by ietf-mx.ietf.org with esmtp (Exim 4.33) id 1Cx4hc-0002v9-Kc; Fri, 04 Feb 2005 09:44:57 -0500 Received: from localhost.localdomain ([127.0.0.1] helo=megatron.ietf.org) by megatron.ietf.org with esmtp (Exim 4.32) id 1Cx4LH-0002yv-Bq; Fri, 04 Feb 2005 09:21:51 -0500 Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org) by megatron.ietf.org with esmtp (Exim 4.32) id 1Cx4HW-0001HG-NC for mpls@megatron.ietf.org; Fri, 04 Feb 2005 09:17:58 -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 JAA29548 for ; Fri, 4 Feb 2005 09:17:56 -0500 (EST) Received: from rtp-iport-1.cisco.com ([64.102.122.148]) by ietf-mx.ietf.org with esmtp (Exim 4.33) id 1Cx4aI-0002a9-FZ for mpls@ietf.org; Fri, 04 Feb 2005 09:37:23 -0500 Received: from rtp-core-1.cisco.com (64.102.124.12) by rtp-iport-1.cisco.com with ESMTP; 04 Feb 2005 09:27:49 -0500 X-BrightmailFiltered: true X-Brightmail-Tracker: AAAAAA== Received: from flask.cisco.com (IDENT:mirapoint@flask.cisco.com [161.44.122.62]) by rtp-core-1.cisco.com (8.12.10/8.12.6) with ESMTP id j14EHNjZ009026; Fri, 4 Feb 2005 09:17:24 -0500 (EST) Received: from [192.168.1.100] (che-vpn-cluster-1-48.cisco.com [10.86.240.48]) by flask.cisco.com (MOS 3.4.6-GR) with ESMTP id AOV90193; Fri, 4 Feb 2005 09:17:22 -0500 (EST) In-Reply-To: <420343B3.1050808@pi.se> References: <42003648.8030206@cisco.com> <420343B3.1050808@pi.se> Mime-Version: 1.0 (Apple Message framework v619.2) Content-Type: text/plain; charset=US-ASCII; format=flowed Message-Id: <67aba1a65ab4fe90d73bdf21b0fd1d98@cisco.com> Content-Transfer-Encoding: 7bit From: "Thomas D. Nadeau" Subject: Re: [mpls] MPLS over L2TPv3 as WG item Date: Fri, 4 Feb 2005 09:17:00 -0500 To: Loa Andersson X-Mailer: Apple Mail (2.619.2) X-Spam-Score: 0.0 (/) X-Scan-Signature: 538aad3a3c4f01d8b6a6477ca4248793 Content-Transfer-Encoding: 7bit Cc: "W. Mark Townsley" , 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: f4c2cf0bccc868e4cc88dace71fb3f44 Content-Transfer-Encoding: 7bit On Feb 4, 2005, at 4:43 AM, Loa Andersson wrote: > Working Group, > > the reception of the draft was a wee bit ambigious (some no, some no > need and some yes), with some service providers strongly in favor. > We would like to poll the working group on whether we want to make > draft-townsley-mpls-over-l2tpv3-00.txt a wg doc. > > To make it possible to publish a working group document, given a rough > consensus in the wg, we need to have comments Feb 11. > > Send comments to the mailing list or wg chairs. We are looking for > both positive and negative comments. Please accept it. --Tom > > /Loa and George > > W. Mark Townsley wrote: > >> As requested by Loa at the last MPLS WG meeting, I have renamed the >> MPLS over L2TPv3 draft as follows: >> draft-townsley-mpls-over-l2tpv3-00.txt >> With consensus confirmation from this list, I would like to resubmit >> this version as a WG item (preferably before the upcoming deadline >> for the next meeting). >> Thanks, >> - Mark >> _______________________________________________ >> mpls mailing list >> mpls@lists.ietf.org >> https://www1.ietf.org/mailman/listinfo/mpls > > -- > Loa Andersson > > Principal Networking Architect > Acreo AB phone: +46 8 632 77 14 > Isafjordsgatan 22 mobile: +46 739 81 21 64 > Kista, Sweden email: loa.andersson@acreo.se > loa@pi.se > > _______________________________________________ > mpls mailing list > mpls@lists.ietf.org > https://www1.ietf.org/mailman/listinfo/mpls > _______________________________________________ mpls mailing list mpls@lists.ietf.org https://www1.ietf.org/mailman/listinfo/mpls From mpls-bounces@ietf.org Fri Feb 4 10:16:18 2005 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 KAA05076; Fri, 4 Feb 2005 10:16:18 -0500 (EST) Received: from megatron.ietf.org ([132.151.6.71]) by ietf-mx.ietf.org with esmtp (Exim 4.33) id 1Cx5Uo-000433-MK; Fri, 04 Feb 2005 10:35:46 -0500 Received: from localhost.localdomain ([127.0.0.1] helo=megatron.ietf.org) by megatron.ietf.org with esmtp (Exim 4.32) id 1Cx56z-0000P9-3T; Fri, 04 Feb 2005 10:11:09 -0500 Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org) by megatron.ietf.org with esmtp (Exim 4.32) id 1Cx4zc-0004ku-TZ for mpls@megatron.ietf.org; Fri, 04 Feb 2005 10:03:32 -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 KAA03392 for ; Fri, 4 Feb 2005 10:03:30 -0500 (EST) Received: from dsl081-098-224.den1.dsl.speakeasy.net ([64.81.98.224] helo=mail.castlepoint.net) by ietf-mx.ietf.org with esmtp (Exim 4.33) id 1Cx5IP-0003lu-1f for mpls@ietf.org; Fri, 04 Feb 2005 10:22:58 -0500 Received: from [127.0.0.1] (ns1.castlepoint.net [172.16.15.250]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (No client certificate requested) by mail.castlepoint.net (Postfix) with ESMTP id 176F1426FD; Fri, 4 Feb 2005 08:03:28 -0700 (MST) Message-ID: <42038EBE.3000708@castlepoint.net> Date: Fri, 04 Feb 2005 08:03:26 -0700 From: Shane Amante User-Agent: Mozilla Thunderbird 0.9 (Windows/20041103) X-Accept-Language: en-us, en MIME-Version: 1.0 To: Loa Andersson Subject: Re: [mpls] MPLS over L2TPv3 as WG item References: <42003648.8030206@cisco.com> <420343B3.1050808@pi.se> In-Reply-To: <420343B3.1050808@pi.se> Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit X-Spam-Score: 0.0 (/) X-Scan-Signature: de4f315c9369b71d7dd5909b42224370 Content-Transfer-Encoding: 7bit Cc: "W. Mark Townsley" , 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: 798b2e660f1819ae38035ac1d8d5e3ab Content-Transfer-Encoding: 7bit Loa Andersson wrote: > Working Group, > > the reception of the draft was a wee bit ambigious (some no, some no > need and some yes), with some service providers strongly in favor. > We would like to poll the working group on whether we want to make > draft-townsley-mpls-over-l2tpv3-00.txt a wg doc. > > To make it possible to publish a working group document, given a rough > consensus in the wg, we need to have comments Feb 11. > > Send comments to the mailing list or wg chairs. We are looking for > both positive and negative comments. Yes, please make it a WG item. -shane _______________________________________________ mpls mailing list mpls@lists.ietf.org https://www1.ietf.org/mailman/listinfo/mpls From mpls-bounces@ietf.org Fri Feb 4 10:26:29 2005 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 KAA06402; Fri, 4 Feb 2005 10:26:29 -0500 (EST) Received: from megatron.ietf.org ([132.151.6.71]) by ietf-mx.ietf.org with esmtp (Exim 4.33) id 1Cx5ef-0004In-S5; Fri, 04 Feb 2005 10:45:58 -0500 Received: from localhost.localdomain ([127.0.0.1] helo=megatron.ietf.org) by megatron.ietf.org with esmtp (Exim 4.32) id 1Cx5J9-0006Df-Au; Fri, 04 Feb 2005 10:23:43 -0500 Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org) by megatron.ietf.org with esmtp (Exim 4.32) id 1Cx5GC-0004jb-Q9 for mpls@megatron.ietf.org; Fri, 04 Feb 2005 10:20:40 -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 KAA05804 for ; Fri, 4 Feb 2005 10:20:38 -0500 (EST) Received: from ibogw-fw2.sprintlink.net ([199.0.233.3] helo=elle.res.sprintlink.net) by ietf-mx.ietf.org with esmtp (Exim 4.33) id 1Cx5Yz-00049R-5X for mpls@ietf.org; Fri, 04 Feb 2005 10:40:06 -0500 Received: from iscserv1.res.sprintlink.net (iscserv1.res.sprintlink.net [199.0.237.253]) by elle.res.sprintlink.net (8.11.6+Sun/8.11.6) with ESMTP id j14FEeJ24352; Fri, 4 Feb 2005 10:14:40 -0500 (EST) Received: from localhost (tseely@localhost) by iscserv1.res.sprintlink.net (8.8.8+Sun/8.6.12) with ESMTP id KAA14608; Fri, 4 Feb 2005 10:20:03 -0500 (EST) X-Authentication-Warning: iscserv1.res.sprintlink.net: tseely owned process doing -bs Date: Fri, 4 Feb 2005 10:20:03 -0500 (EST) From: Ted Seely X-X-Sender: To: Loa Andersson Subject: Re: [mpls] MPLS over L2TPv3 as WG item In-Reply-To: <420343B3.1050808@pi.se> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII X-Spam-Score: 0.0 (/) X-Scan-Signature: d8ae4fd88fcaf47c1a71c804d04f413d 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: bdc523f9a54890b8a30dd6fd53d5d024 Strongly in favor here. Ted On Fri, 4 Feb 2005, Loa Andersson wrote: > Working Group, > > the reception of the draft was a wee bit ambigious (some no, some no > need and some yes), with some service providers strongly in favor. > We would like to poll the working group on whether we want to make > draft-townsley-mpls-over-l2tpv3-00.txt a wg doc. > > To make it possible to publish a working group document, given a rough > consensus in the wg, we need to have comments Feb 11. > > Send comments to the mailing list or wg chairs. We are looking for > both positive and negative comments. > > /Loa and George > > W. Mark Townsley wrote: > > > > > As requested by Loa at the last MPLS WG meeting, I have renamed the MPLS > > over L2TPv3 draft as follows: > > > > draft-townsley-mpls-over-l2tpv3-00.txt > > > > With consensus confirmation from this list, I would like to resubmit > > this version as a WG item (preferably before the upcoming deadline for > > the next meeting). > > > > Thanks, > > > > - Mark > > > > > > _______________________________________________ > > mpls mailing list > > mpls@lists.ietf.org > > https://www1.ietf.org/mailman/listinfo/mpls > > > > -- > Loa Andersson > > Principal Networking Architect > Acreo AB phone: +46 8 632 77 14 > Isafjordsgatan 22 mobile: +46 739 81 21 64 > Kista, Sweden email: loa.andersson@acreo.se > loa@pi.se > > _______________________________________________ > mpls mailing list > mpls@lists.ietf.org > https://www1.ietf.org/mailman/listinfo/mpls > Ted Seely Principal Network Design Engineer Internet Engineering - SprintLink (W) 703.689.6425 (M) 703.967.3289 AIM - wanpro00 Yahoo IM - tseely01 There are no such things as friends in this industry. _______________________________________________ mpls mailing list mpls@lists.ietf.org https://www1.ietf.org/mailman/listinfo/mpls From mpls-bounces@ietf.org Fri Feb 4 12:57:38 2005 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 MAA19700; Fri, 4 Feb 2005 12:57:38 -0500 (EST) Received: from megatron.ietf.org ([132.151.6.71]) by ietf-mx.ietf.org with esmtp (Exim 4.33) id 1Cx80x-00081N-NK; Fri, 04 Feb 2005 13:17:08 -0500 Received: from localhost.localdomain ([127.0.0.1] helo=megatron.ietf.org) by megatron.ietf.org with esmtp (Exim 4.32) id 1Cx7gS-00055o-0q; Fri, 04 Feb 2005 12:55:56 -0500 Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org) by megatron.ietf.org with esmtp (Exim 4.32) id 1Cx7eJ-0004CM-8a for mpls@megatron.ietf.org; Fri, 04 Feb 2005 12:53: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 MAA19326 for ; Fri, 4 Feb 2005 12:53:39 -0500 (EST) Received: from slb-smtpout-01.boeing.com ([130.76.64.48]) by ietf-mx.ietf.org with esmtp (Exim 4.33) id 1Cx7x6-0007tu-53 for mpls@ietf.org; Fri, 04 Feb 2005 13:13:09 -0500 Received: from stl-av-01.boeing.com ([192.76.190.6]) by slb-smtpout-01.boeing.com (8.9.2.MG.10092003/8.8.5-M2) with ESMTP id JAA11687 for ; Fri, 4 Feb 2005 09:52:59 -0800 (PST) Received: from XCH-SWBH-04.sw.nos.boeing.com (localhost [127.0.0.1]) by stl-av-01.boeing.com (8.11.3/8.11.3/MBS-AV-LDAP-01) with ESMTP id j14Hr4J00781 for ; Fri, 4 Feb 2005 11:53:04 -0600 (CST) Received: from XCH-SW-42.sw.nos.boeing.com ([192.79.11.43]) by XCH-SWBH-04.sw.nos.boeing.com with Microsoft SMTPSVC(6.0.3790.211); Fri, 4 Feb 2005 09:52:58 -0800 X-MimeOLE: Produced By Microsoft Exchange V6.5.7226.0 Content-class: urn:content-classes:message MIME-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: quoted-printable Subject: RE: [mpls] MPLS over L2TPv3 as WG item Date: Fri, 4 Feb 2005 09:52:58 -0800 Message-ID: <626FC7C6A97381468FB872072AB5DDC805EE5B@XCH-SW-42.sw.nos.boeing.com> Thread-Topic: [mpls] MPLS over L2TPv3 as WG item Thread-Index: AcUKoCHqvpEpMM6SSZOs3gc89DpaNwAILHqAAAhWoxA= From: "Drake, John E" To: X-OriginalArrivalTime: 04 Feb 2005 17:52:58.0743 (UTC) FILETIME=[5CE69870:01C50AE2] X-Spam-Score: 0.0 (/) X-Scan-Signature: 3002fc2e661cd7f114cb6bae92fe88f1 Content-Transfer-Encoding: quoted-printable 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: f66b12316365a3fe519e75911daf28a8 Content-Transfer-Encoding: quoted-printable No compelling need for this > -----Original Message----- > From: Zafar Ali [mailto:zali@cisco.com] > Sent: Friday, February 04, 2005 5:54 AM > To: 'Loa Andersson'; 'W. Mark Townsley' > Cc: mpls@ietf.org > Subject: RE: [mpls] MPLS over L2TPv3 as WG item >=20 > Yes, strongly in favor >=20 > Thanks >=20 > Regards... Zafar >=20 >=20 > > -----Original Message----- > > From: mpls-bounces@lists.ietf.org > > [mailto:mpls-bounces@lists.ietf.org] On Behalf Of Loa Andersson > > Sent: Friday, February 04, 2005 4:43 AM > > To: W. Mark Townsley > > Cc: mpls@ietf.org > > Subject: Re: [mpls] MPLS over L2TPv3 as WG item > > > > Working Group, > > > > the reception of the draft was a wee bit ambigious (some no, > > some no need and some yes), with some service providers > > strongly in favor. > > We would like to poll the working group on whether we want to > > make draft-townsley-mpls-over-l2tpv3-00.txt a wg doc. > > > > To make it possible to publish a working group document, > > given a rough consensus in the wg, we need to have comments Feb 11. > > > > Send comments to the mailing list or wg chairs. We are > > looking for both positive and negative comments. > > > > /Loa and George > > > > W. Mark Townsley wrote: > > > > > > > > As requested by Loa at the last MPLS WG meeting, I have renamed the > > > MPLS over L2TPv3 draft as follows: > > > > > > draft-townsley-mpls-over-l2tpv3-00.txt > > > > > > With consensus confirmation from this list, I would like to > > resubmit > > > this version as a WG item (preferably before the upcoming > > deadline for > > > the next meeting). > > > > > > Thanks, > > > > > > - Mark > > > > > > > > > _______________________________________________ > > > mpls mailing list > > > mpls@lists.ietf.org > > > https://www1.ietf.org/mailman/listinfo/mpls > > > > > > > -- > > Loa Andersson > > > > Principal Networking Architect > > Acreo AB phone: +46 8 632 77 14 > > Isafjordsgatan 22 mobile: +46 739 81 21 64 > > Kista, Sweden email: loa.andersson@acreo.se > > loa@pi.se > > > > _______________________________________________ > > mpls mailing list > > mpls@lists.ietf.org > > https://www1.ietf.org/mailman/listinfo/mpls > > >=20 > _______________________________________________ > mpls mailing list > mpls@lists.ietf.org > https://www1.ietf.org/mailman/listinfo/mpls _______________________________________________ mpls mailing list mpls@lists.ietf.org https://www1.ietf.org/mailman/listinfo/mpls From mpls-bounces@ietf.org Fri Feb 4 14:54:45 2005 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 OAA27599; Fri, 4 Feb 2005 14:54:45 -0500 (EST) Received: from megatron.ietf.org ([132.151.6.71]) by ietf-mx.ietf.org with esmtp (Exim 4.33) id 1Cx9qI-0001ue-C7; Fri, 04 Feb 2005 15:14:15 -0500 Received: from localhost.localdomain ([127.0.0.1] helo=megatron.ietf.org) by megatron.ietf.org with esmtp (Exim 4.32) id 1Cx9OW-0002BP-M5; Fri, 04 Feb 2005 14:45:32 -0500 Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org) by megatron.ietf.org with esmtp (Exim 4.32) id 1Cx9Lg-0001p0-4I for mpls@megatron.ietf.org; Fri, 04 Feb 2005 14:42:36 -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 OAA26846 for ; Fri, 4 Feb 2005 14:42:34 -0500 (EST) Received: from sj-iport-2-in.cisco.com ([171.71.176.71] helo=sj-iport-2.cisco.com) by ietf-mx.ietf.org with esmtp (Exim 4.33) id 1Cx9eU-0001gZ-RM for mpls@ietf.org; Fri, 04 Feb 2005 15:02:04 -0500 Received: from sj-core-2.cisco.com (171.71.177.254) by sj-iport-2.cisco.com with ESMTP; 04 Feb 2005 11:49:48 -0800 Received: from wells.cisco.com (wells.cisco.com [171.71.177.223]) by sj-core-2.cisco.com (8.12.10/8.12.6) with ESMTP id j14JfrHo009962; Fri, 4 Feb 2005 11:41:53 -0800 (PST) Received: from [192.168.1.100] (che-vpn-cluster-1-2.cisco.com [10.86.240.2]) by wells.cisco.com (8.8.6 (PHNE_14041)/CISCO.SERVER.1.2) with ESMTP id LAA08503; Fri, 4 Feb 2005 11:41:55 -0800 (PST) In-Reply-To: <420343B3.1050808@pi.se> References: <42003648.8030206@cisco.com> <420343B3.1050808@pi.se> Mime-Version: 1.0 (Apple Message framework v619.2) Content-Type: text/plain; charset=US-ASCII; format=flowed Message-Id: <07bc4ae54391598ee6edd1b677f8a4ef@cisco.com> Content-Transfer-Encoding: 7bit From: JP Vasseur Subject: Re: [mpls] MPLS over L2TPv3 as WG item Date: Fri, 4 Feb 2005 14:42:02 -0500 To: Loa Andersson X-Mailer: Apple Mail (2.619.2) X-Spam-Score: 0.0 (/) X-Scan-Signature: 0ddefe323dd869ab027dbfff7eff0465 Content-Transfer-Encoding: 7bit Cc: "W. Mark Townsley" , 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: 3e15cc4fdc61d7bce84032741d11c8e5 Content-Transfer-Encoding: 7bit in favor. JP. On Feb 4, 2005, at 4:43 AM, Loa Andersson wrote: > Working Group, > > the reception of the draft was a wee bit ambigious (some no, some no > need and some yes), with some service providers strongly in favor. > We would like to poll the working group on whether we want to make > draft-townsley-mpls-over-l2tpv3-00.txt a wg doc. > > To make it possible to publish a working group document, given a rough > consensus in the wg, we need to have comments Feb 11. > > Send comments to the mailing list or wg chairs. We are looking for > both positive and negative comments. > > /Loa and George > > W. Mark Townsley wrote: > >> As requested by Loa at the last MPLS WG meeting, I have renamed the >> MPLS over L2TPv3 draft as follows: >> draft-townsley-mpls-over-l2tpv3-00.txt >> With consensus confirmation from this list, I would like to resubmit >> this version as a WG item (preferably before the upcoming deadline >> for the next meeting). >> Thanks, >> - Mark >> _______________________________________________ >> mpls mailing list >> mpls@lists.ietf.org >> https://www1.ietf.org/mailman/listinfo/mpls > > -- > Loa Andersson > > Principal Networking Architect > Acreo AB phone: +46 8 632 77 14 > Isafjordsgatan 22 mobile: +46 739 81 21 64 > Kista, Sweden email: loa.andersson@acreo.se > loa@pi.se > > _______________________________________________ > mpls mailing list > mpls@lists.ietf.org > https://www1.ietf.org/mailman/listinfo/mpls > _______________________________________________ mpls mailing list mpls@lists.ietf.org https://www1.ietf.org/mailman/listinfo/mpls From mpls-bounces@ietf.org Fri Feb 4 15:18:19 2005 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 PAA00321; Fri, 4 Feb 2005 15:18:19 -0500 (EST) Received: from megatron.ietf.org ([132.151.6.71]) by ietf-mx.ietf.org with esmtp (Exim 4.33) id 1CxAD7-0002Xr-4R; Fri, 04 Feb 2005 15:37:50 -0500 Received: from localhost.localdomain ([127.0.0.1] helo=megatron.ietf.org) by megatron.ietf.org with esmtp (Exim 4.32) id 1Cx9sq-0007wm-Ky; Fri, 04 Feb 2005 15:16:52 -0500 Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org) by megatron.ietf.org with esmtp (Exim 4.32) id 1Cx9kR-0002vZ-13 for mpls@megatron.ietf.org; Fri, 04 Feb 2005 15:08: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 PAA28740 for ; Fri, 4 Feb 2005 15:08:07 -0500 (EST) Received: from smtp1.phx.gblx.net ([64.208.25.103]) by ietf-mx.ietf.org with esmtp (Exim 4.33) id 1CxA3F-0002AH-HW for mpls@ietf.org; Fri, 04 Feb 2005 15:27:38 -0500 Received: (from daemon@localhost) by smtp1.phx.gblx.net (8.11.2/8.11.2) id j14K87002502; Fri, 4 Feb 2005 13:08:07 -0700 (MST) Received: from shell1.phx.gblx.net(64.208.25.102) via SMTP by smtp1.phx.gblx.net, id smtpdAAAyDay4e; Fri Feb 4 13:08:06 2005 Received: (from mmeyer@localhost) by shell1.phx.gblx.net (8.9.3+Sun/8.9.3) id NAA27546; Fri, 4 Feb 2005 13:08:06 -0700 (MST) Date: Fri, 4 Feb 2005 13:08:06 -0700 From: Matthew Meyer To: Loa Andersson Subject: Re: [mpls] MPLS over L2TPv3 as WG item Message-ID: <20050204200806.GI28064@gblx.net> Mail-Followup-To: Loa Andersson , "W. Mark Townsley" , mpls@ietf.org References: <42003648.8030206@cisco.com> <420343B3.1050808@pi.se> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <420343B3.1050808@pi.se> User-Agent: Mutt/1.5.6i X-Spam-Score: 0.0 (/) X-Scan-Signature: f4c2cf0bccc868e4cc88dace71fb3f44 Cc: "W. Mark Townsley" , 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: e8a67952aa972b528dd04570d58ad8fe I agree with making it a WG document. Matthew Thus spake Loa Andersson (loa@pi.se): |Working Group, | |the reception of the draft was a wee bit ambigious (some no, some no |need and some yes), with some service providers strongly in favor. |We would like to poll the working group on whether we want to make |draft-townsley-mpls-over-l2tpv3-00.txt a wg doc. | |To make it possible to publish a working group document, given a rough |consensus in the wg, we need to have comments Feb 11. | |Send comments to the mailing list or wg chairs. We are looking for |both positive and negative comments. | |/Loa and George | |W. Mark Townsley wrote: | |> |>As requested by Loa at the last MPLS WG meeting, I have renamed the MPLS |>over L2TPv3 draft as follows: |> |>draft-townsley-mpls-over-l2tpv3-00.txt |> |>With consensus confirmation from this list, I would like to resubmit |>this version as a WG item (preferably before the upcoming deadline for |>the next meeting). |> |>Thanks, |> |>- Mark |> |> |>_______________________________________________ |>mpls mailing list |>mpls@lists.ietf.org |>https://www1.ietf.org/mailman/listinfo/mpls |> | |-- |Loa Andersson | |Principal Networking Architect |Acreo AB phone: +46 8 632 77 14 |Isafjordsgatan 22 mobile: +46 739 81 21 64 |Kista, Sweden email: loa.andersson@acreo.se | loa@pi.se | |_______________________________________________ |mpls mailing list |mpls@lists.ietf.org |https://www1.ietf.org/mailman/listinfo/mpls _______________________________________________ mpls mailing list mpls@lists.ietf.org https://www1.ietf.org/mailman/listinfo/mpls From mpls-bounces@ietf.org Fri Feb 4 16:00:22 2005 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 QAA03988; Fri, 4 Feb 2005 16:00:22 -0500 (EST) Received: from megatron.ietf.org ([132.151.6.71]) by ietf-mx.ietf.org with esmtp (Exim 4.33) id 1CxAro-0003aZ-OF; Fri, 04 Feb 2005 16:19:53 -0500 Received: from localhost.localdomain ([127.0.0.1] helo=megatron.ietf.org) by megatron.ietf.org with esmtp (Exim 4.32) id 1CxASZ-0003AS-Tm; Fri, 04 Feb 2005 15:53:47 -0500 Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org) by megatron.ietf.org with esmtp (Exim 4.32) id 1CxAOd-0001Dr-V6 for mpls@megatron.ietf.org; Fri, 04 Feb 2005 15:49:45 -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 PAA03130 for ; Fri, 4 Feb 2005 15:49:41 -0500 (EST) Received: from bay21-f18.bay21.hotmail.com ([65.54.233.107] helo=hotmail.com) by ietf-mx.ietf.org with esmtp (Exim 4.33) id 1CxAhM-0003K1-TZ for mpls@ietf.org; Fri, 04 Feb 2005 16:09:12 -0500 Received: from mail pickup service by hotmail.com with Microsoft SMTPSVC; Fri, 4 Feb 2005 12:47:00 -0800 Message-ID: Received: from 81.178.20.174 by by21fd.bay21.hotmail.msn.com with HTTP; Fri, 04 Feb 2005 20:46:21 GMT X-Originating-IP: [81.178.20.174] X-Originating-Email: [bob_arthurs@hotmail.com] X-Sender: bob_arthurs@hotmail.com In-Reply-To: <20050204200806.GI28064@gblx.net> From: "Bob Arthurs" To: mpls@ietf.org Subject: Re: [mpls] MPLS over L2TPv3 as WG item Date: Fri, 04 Feb 2005 20:46:21 +0000 Mime-Version: 1.0 Content-Type: text/plain; format=flowed X-OriginalArrivalTime: 04 Feb 2005 20:47:00.0834 (UTC) FILETIME=[ACDF3C20:01C50AFA] X-Spam-Score: 0.8 (/) X-Scan-Signature: d8ae4fd88fcaf47c1a71c804d04f413d 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: bdc523f9a54890b8a30dd6fd53d5d024 I'm also in favor. >From: Matthew Meyer >To: Loa Andersson >CC: "W. Mark Townsley" , mpls@ietf.org >Subject: Re: [mpls] MPLS over L2TPv3 as WG item >Date: Fri, 4 Feb 2005 13:08:06 -0700 > > >I agree with making it a WG document. > >Matthew > >Thus spake Loa Andersson (loa@pi.se): > > |Working Group, > | > |the reception of the draft was a wee bit ambigious (some no, some no > |need and some yes), with some service providers strongly in favor. > |We would like to poll the working group on whether we want to make > |draft-townsley-mpls-over-l2tpv3-00.txt a wg doc. > | > |To make it possible to publish a working group document, given a rough > |consensus in the wg, we need to have comments Feb 11. > | > |Send comments to the mailing list or wg chairs. We are looking for > |both positive and negative comments. > | > |/Loa and George > | > |W. Mark Townsley wrote: > | > |> > |>As requested by Loa at the last MPLS WG meeting, I have renamed the >MPLS > |>over L2TPv3 draft as follows: > |> > |>draft-townsley-mpls-over-l2tpv3-00.txt > |> > |>With consensus confirmation from this list, I would like to resubmit > |>this version as a WG item (preferably before the upcoming deadline for > |>the next meeting). > |> > |>Thanks, > |> > |>- Mark > |> > |> > |>_______________________________________________ > |>mpls mailing list > |>mpls@lists.ietf.org > |>https://www1.ietf.org/mailman/listinfo/mpls > |> > | > |-- > |Loa Andersson > | > |Principal Networking Architect > |Acreo AB phone: +46 8 632 77 14 > |Isafjordsgatan 22 mobile: +46 739 81 21 64 > |Kista, Sweden email: loa.andersson@acreo.se > | loa@pi.se > | > |_______________________________________________ > |mpls mailing list > |mpls@lists.ietf.org > |https://www1.ietf.org/mailman/listinfo/mpls > >_______________________________________________ >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 Feb 4 16:57:17 2005 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 QAA10978; Fri, 4 Feb 2005 16:57:17 -0500 (EST) Received: from megatron.ietf.org ([132.151.6.71]) by ietf-mx.ietf.org with esmtp (Exim 4.33) id 1CxBkt-0005Wy-Ue; Fri, 04 Feb 2005 17:16:49 -0500 Received: from localhost.localdomain ([127.0.0.1] helo=megatron.ietf.org) by megatron.ietf.org with esmtp (Exim 4.32) id 1CxBPP-0005mh-I5; Fri, 04 Feb 2005 16:54:35 -0500 Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org) by megatron.ietf.org with esmtp (Exim 4.32) id 1CxBMP-00057z-B6 for mpls@megatron.ietf.org; Fri, 04 Feb 2005 16:51: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 QAA10141 for ; Fri, 4 Feb 2005 16:51:26 -0500 (EST) Received: from sj-iport-5.cisco.com ([171.68.10.87]) by ietf-mx.ietf.org with esmtp (Exim 4.33) id 1CxBfF-0005IQ-4Q for mpls@ietf.org; Fri, 04 Feb 2005 17:10:58 -0500 Received: from sj-core-4.cisco.com (171.68.223.138) by sj-iport-5.cisco.com with ESMTP; 04 Feb 2005 13:51:03 -0800 X-BrightmailFiltered: true X-Brightmail-Tracker: AAAAAA== Received: from dchengw2k (dhcp-171-71-206-178.cisco.com [171.71.206.178]) by sj-core-4.cisco.com (8.12.10/8.12.6) with ESMTP id j14Lor82021082; Fri, 4 Feb 2005 13:50:54 -0800 (PST) Message-Id: <200502042150.j14Lor82021082@sj-core-4.cisco.com> From: "Dean Cheng \(dcheng\)" To: "'Loa Andersson'" , "'W. Mark Townsley'" Subject: RE: [mpls] MPLS over L2TPv3 as WG item Date: Fri, 4 Feb 2005 13:50:53 -0800 MIME-Version: 1.0 Content-Type: text/plain; charset="US-ASCII" Content-Transfer-Encoding: 7bit X-Mailer: Microsoft Office Outlook, Build 11.0.5510 In-Reply-To: <420343B3.1050808@pi.se> X-MimeOLE: Produced By Microsoft MimeOLE V5.50.4939.300 Thread-index: AcUKoCKDZpI/YIemQKSxV+tv3ILJngAYu7uQ X-Spam-Score: 0.0 (/) X-Scan-Signature: 52f7a77164458f8c7b36b66787c853da Content-Transfer-Encoding: 7bit Cc: mpls@ietf.org X-BeenThere: mpls@lists.ietf.org X-Mailman-Version: 2.1.5 Precedence: list Reply-To: dcheng@cisco.com 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: 4b800b1eab964a31702fa68f1ff0e955 Content-Transfer-Encoding: 7bit Support to make it a WG item. Dean >-----Original Message----- >From: mpls-bounces@lists.ietf.org >[mailto:mpls-bounces@lists.ietf.org] On Behalf Of Loa Andersson >Sent: Friday, February 04, 2005 1:43 AM >To: W. Mark Townsley >Cc: mpls@ietf.org >Subject: Re: [mpls] MPLS over L2TPv3 as WG item > >Working Group, > >the reception of the draft was a wee bit ambigious (some no, >some no need and some yes), with some service providers >strongly in favor. >We would like to poll the working group on whether we want to >make draft-townsley-mpls-over-l2tpv3-00.txt a wg doc. > >To make it possible to publish a working group document, given >a rough consensus in the wg, we need to have comments Feb 11. > >Send comments to the mailing list or wg chairs. We are looking >for both positive and negative comments. > >/Loa and George > >W. Mark Townsley wrote: > >> >> As requested by Loa at the last MPLS WG meeting, I have renamed the >> MPLS over L2TPv3 draft as follows: >> >> draft-townsley-mpls-over-l2tpv3-00.txt >> >> With consensus confirmation from this list, I would like to resubmit >> this version as a WG item (preferably before the upcoming >deadline for >> the next meeting). >> >> Thanks, >> >> - Mark >> >> >> _______________________________________________ >> mpls mailing list >> mpls@lists.ietf.org >> https://www1.ietf.org/mailman/listinfo/mpls >> > >-- >Loa Andersson > >Principal Networking Architect >Acreo AB phone: +46 8 632 77 14 >Isafjordsgatan 22 mobile: +46 739 81 21 64 >Kista, Sweden email: loa.andersson@acreo.se > loa@pi.se > >_______________________________________________ >mpls mailing list >mpls@lists.ietf.org >https://www1.ietf.org/mailman/listinfo/mpls > _______________________________________________ mpls mailing list mpls@lists.ietf.org https://www1.ietf.org/mailman/listinfo/mpls From mpls-bounces@ietf.org Sat Feb 5 07:04:07 2005 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 HAA24456; Sat, 5 Feb 2005 07:04:06 -0500 (EST) Received: from megatron.ietf.org ([132.151.6.71]) by ietf-mx.ietf.org with esmtp (Exim 4.33) id 1CxOyX-00063m-FO; Sat, 05 Feb 2005 07:23:46 -0500 Received: from localhost.localdomain ([127.0.0.1] helo=megatron.ietf.org) by megatron.ietf.org with esmtp (Exim 4.32) id 1CxOd2-0000dH-Oj; Sat, 05 Feb 2005 07:01:32 -0500 Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org) by megatron.ietf.org with esmtp (Exim 4.32) id 1CxOc5-0000W8-JI for mpls@megatron.ietf.org; Sat, 05 Feb 2005 07:00:34 -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 HAA24210 for ; Sat, 5 Feb 2005 07:00:30 -0500 (EST) Received: from astro.systems.pipex.net ([62.241.163.6]) by ietf-mx.ietf.org with esmtp (Exim 4.33) id 1CxOv2-0005yC-G4 for mpls@ietf.org; Sat, 05 Feb 2005 07:20:10 -0500 Received: from dnni.com (81-178-2-190.dsl.pipex.com [81.178.2.190]) by astro.systems.pipex.net (Postfix) with ESMTP id 30401E00041C; Sat, 5 Feb 2005 11:59:48 +0000 (GMT) Received: from Puppy ([212.43.203.18] RDNS failed) by dnni.com with Microsoft SMTPSVC(6.0.3790.211); Sat, 5 Feb 2005 11:59:48 +0000 Message-ID: <039c01c50b7a$5e66fad0$70cb2bd4@Puppy> From: "Adrian Farrel" To: "Loa Andersson" , "W. Mark Townsley" References: <42003648.8030206@cisco.com> <420343B3.1050808@pi.se> Subject: Re: [mpls] MPLS over L2TPv3 as WG item Date: Sat, 5 Feb 2005 09:41:28 -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: 05 Feb 2005 11:59:49.0599 (UTC) FILETIME=[31998EF0:01C50B7A] X-Spam-Score: 0.1 (/) X-Scan-Signature: 00e94c813bef7832af255170dca19e36 Content-Transfer-Encoding: 7bit Cc: mpls@ietf.org X-BeenThere: mpls@lists.ietf.org X-Mailman-Version: 2.1.5 Precedence: list Reply-To: Adrian Farrel List-Id: Multi-Protocol Label Switching WG List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Sender: mpls-bounces@ietf.org Errors-To: mpls-bounces@ietf.org X-Spam-Score: 0.1 (/) X-Scan-Signature: d185fa790257f526fedfd5d01ed9c976 Content-Transfer-Encoding: 7bit Well, I suppose it does not harm. But does it do any good? Looking at the current draft, there are no protocol specifications and no code point definitions. The draft boils down to a statement that the payload of an L2TP packet may be an MPLS packet, some restatements from L2TPv3 about how the L2TP fields should be set, and an applicability statement. I would suggest that this should be simply recast as an informational draft making an applicability statement for MPLS over L2TP. Regards, Adrian ----- Original Message ----- From: "Loa Andersson" To: "W. Mark Townsley" Cc: Sent: Friday, February 04, 2005 9:43 AM Subject: Re: [mpls] MPLS over L2TPv3 as WG item > Working Group, > > the reception of the draft was a wee bit ambigious (some no, some no > need and some yes), with some service providers strongly in favor. > We would like to poll the working group on whether we want to make > draft-townsley-mpls-over-l2tpv3-00.txt a wg doc. > > To make it possible to publish a working group document, given a rough > consensus in the wg, we need to have comments Feb 11. > > Send comments to the mailing list or wg chairs. We are looking for > both positive and negative comments. > > /Loa and George > > W. Mark Townsley wrote: > > > > > As requested by Loa at the last MPLS WG meeting, I have renamed the MPLS > > over L2TPv3 draft as follows: > > > > draft-townsley-mpls-over-l2tpv3-00.txt > > > > With consensus confirmation from this list, I would like to resubmit > > this version as a WG item (preferably before the upcoming deadline for > > the next meeting). > > > > Thanks, > > > > - Mark > > > > > > _______________________________________________ > > mpls mailing list > > mpls@lists.ietf.org > > https://www1.ietf.org/mailman/listinfo/mpls > > > > -- > Loa Andersson > > Principal Networking Architect > Acreo AB phone: +46 8 632 77 14 > Isafjordsgatan 22 mobile: +46 739 81 21 64 > Kista, Sweden email: loa.andersson@acreo.se > loa@pi.se > > _______________________________________________ > mpls mailing list > mpls@lists.ietf.org > https://www1.ietf.org/mailman/listinfo/mpls > > _______________________________________________ mpls mailing list mpls@lists.ietf.org https://www1.ietf.org/mailman/listinfo/mpls From mpls-bounces@ietf.org Sat Feb 5 08:27:41 2005 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 IAA29936; Sat, 5 Feb 2005 08:27:41 -0500 (EST) Received: from megatron.ietf.org ([132.151.6.71]) by ietf-mx.ietf.org with esmtp (Exim 4.33) id 1CxQHQ-0007vV-4e; Sat, 05 Feb 2005 08:47:20 -0500 Received: from localhost.localdomain ([127.0.0.1] helo=megatron.ietf.org) by megatron.ietf.org with esmtp (Exim 4.32) id 1CxPvQ-0004xE-Bx; Sat, 05 Feb 2005 08:24:36 -0500 Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org) by megatron.ietf.org with esmtp (Exim 4.32) id 1CxPtW-0004TP-W8 for mpls@megatron.ietf.org; Sat, 05 Feb 2005 08:22:39 -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 IAA29637 for ; Sat, 5 Feb 2005 08:22:37 -0500 (EST) Received: from zcars04e.nortelnetworks.com ([47.129.242.56]) by ietf-mx.ietf.org with esmtp (Exim 4.33) id 1CxQCU-0007oG-Mt for mpls@ietf.org; Sat, 05 Feb 2005 08:42:16 -0500 Received: from zrtpd0jn.us.nortel.com (zrtpd0jn.us.nortel.com [47.140.202.35]) by zcars04e.nortelnetworks.com (Switch-2.2.6/Switch-2.2.0) with ESMTP id j15DLxN16780 for ; Sat, 5 Feb 2005 08:21:59 -0500 (EST) Received: by zrtpd0jn.us.nortel.com with Internet Mail Service (5.5.2653.19) id <1JJLHL6V>; Sat, 5 Feb 2005 08:22:00 -0500 Message-ID: <87AC5F88F03E6249AEA68D40BD3E00BE019BC6ED@zcarhxm2.corp.nortel.com> From: "David Allan" To: "'mpls@ietf.org'" Subject: RE: [mpls] MPLS over L2TPv3 as WG item Date: Sat, 5 Feb 2005 08:21:52 -0500 X-Mailer: Internet Mail Service (5.5.2653.19) X-Spam-Score: 0.0 (/) X-Scan-Signature: 1ac7cc0a4cd376402b85bc1961a86ac2 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: d6b246023072368de71562c0ab503126 Hi: I could support it if there was a stated intention to deprecate PWs over L2TPv3 as done today (aka not really interoperable in any simple sense with PWs over MPLS or MPLSinIP) which IMO would be a useful simplification... Otherwise it is simply one MORE way to do the same thing and I for one don't have the cycles for that... rgds Dave _______________________________________________ mpls mailing list mpls@lists.ietf.org https://www1.ietf.org/mailman/listinfo/mpls From mpls-bounces@ietf.org Sat Feb 5 08:54:16 2005 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 IAA01757; Sat, 5 Feb 2005 08:54:16 -0500 (EST) Received: from megatron.ietf.org ([132.151.6.71]) by ietf-mx.ietf.org with esmtp (Exim 4.33) id 1CxQh9-0008Px-Jw; Sat, 05 Feb 2005 09:13:55 -0500 Received: from localhost.localdomain ([127.0.0.1] helo=megatron.ietf.org) by megatron.ietf.org with esmtp (Exim 4.32) id 1CxQLO-0000Kq-Qe; Sat, 05 Feb 2005 08:51:26 -0500 Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org) by megatron.ietf.org with esmtp (Exim 4.32) id 1CxQKE-0008Ro-MR for mpls@megatron.ietf.org; Sat, 05 Feb 2005 08:50:14 -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 IAA01454 for ; Sat, 5 Feb 2005 08:50:12 -0500 (EST) Received: from galaga.kirurg.org ([217.8.158.30] helo=galaga.local) by ietf-mx.ietf.org with esmtp (Exim 4.33) id 1CxQdC-0008Kz-Pr for mpls@ietf.org; Sat, 05 Feb 2005 09:09:52 -0500 Received: from galaga.local (localhost.localdomain [127.0.0.1]) by galaga.local (8.13.1/8.12.11) with ESMTP id j15Do8xZ015113; Sat, 5 Feb 2005 14:50:08 +0100 Received: from localhost (perole@localhost) by galaga.local (8.13.1/8.13.1/Submit) with ESMTP id j15Do8Il015110; Sat, 5 Feb 2005 14:50:08 +0100 X-Authentication-Warning: galaga.local: perole owned process doing -bs Date: Sat, 5 Feb 2005 14:50:07 +0100 (CET) From: Per Ole Klemetsrud X-X-Sender: perole@galaga.local To: Loa Andersson Subject: Re: [mpls] MPLS over L2TPv3 as WG item In-Reply-To: <420343B3.1050808@pi.se> Message-ID: References: <42003648.8030206@cisco.com> <420343B3.1050808@pi.se> MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII; format=flowed X-Spam-Score: 0.0 (/) X-Scan-Signature: 769a46790fb42fbb0b0cc700c82f7081 Cc: "W. Mark Townsley" , 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: 538aad3a3c4f01d8b6a6477ca4248793 >From one service providers point if view, it is my hope that vendors will put their MPLS development resources elsewhere. Per Ole Klemetsrud Senior Network Engineer, Catch Communications On Fri, 4 Feb 2005, Loa Andersson wrote: > Working Group, > > the reception of the draft was a wee bit ambigious (some no, some no > need and some yes), with some service providers strongly in favor. > We would like to poll the working group on whether we want to make > draft-townsley-mpls-over-l2tpv3-00.txt a wg doc. > > To make it possible to publish a working group document, given a rough > consensus in the wg, we need to have comments Feb 11. > > Send comments to the mailing list or wg chairs. We are looking for > both positive and negative comments. > > /Loa and George > > W. Mark Townsley wrote: > >> >> As requested by Loa at the last MPLS WG meeting, I have renamed the MPLS >> over L2TPv3 draft as follows: >> >> draft-townsley-mpls-over-l2tpv3-00.txt >> >> With consensus confirmation from this list, I would like to resubmit this >> version as a WG item (preferably before the upcoming deadline for the next >> meeting). >> >> Thanks, >> >> - Mark >> >> >> _______________________________________________ >> 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 Sat Feb 5 09:50:55 2005 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 JAA05333; Sat, 5 Feb 2005 09:50:55 -0500 (EST) Received: from megatron.ietf.org ([132.151.6.71]) by ietf-mx.ietf.org with esmtp (Exim 4.33) id 1CxRZz-000157-Aa; Sat, 05 Feb 2005 10:10:35 -0500 Received: from localhost.localdomain ([127.0.0.1] helo=megatron.ietf.org) by megatron.ietf.org with esmtp (Exim 4.32) id 1CxR8a-0004AX-1o; Sat, 05 Feb 2005 09:42:16 -0500 Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org) by megatron.ietf.org with esmtp (Exim 4.32) id 1CxR59-0003iK-41 for mpls@megatron.ietf.org; Sat, 05 Feb 2005 09:38: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 JAA04650 for ; Sat, 5 Feb 2005 09:38:41 -0500 (EST) Received: from rtp-iport-1.cisco.com ([64.102.122.148]) by ietf-mx.ietf.org with esmtp (Exim 4.33) id 1CxRO8-0000qC-1s for mpls@ietf.org; Sat, 05 Feb 2005 09:58:21 -0500 Received: from rtp-core-1.cisco.com (64.102.124.12) by rtp-iport-1.cisco.com with ESMTP; 05 Feb 2005 09:48:44 -0500 X-BrightmailFiltered: true X-Brightmail-Tracker: AAAAAA== Received: from fruitpie.cisco.com (IDENT:mirapoint@fruitpie.cisco.com [64.102.16.27]) by rtp-core-1.cisco.com (8.12.10/8.12.6) with ESMTP id j15Ec41j021715; Sat, 5 Feb 2005 09:38:05 -0500 (EST) Received: from [10.83.1.105] (rtp-townsley-vpn8.cisco.com [10.83.1.105]) by fruitpie.cisco.com (MOS 3.4.6-GR) with SMTP id BFC59387; Sat, 5 Feb 2005 06:38:03 -0800 (PST) Message-ID: <4204DA4A.1010505@cisco.com> Date: Sat, 05 Feb 2005 09:38:02 -0500 From: "W. Mark Townsley" User-Agent: Mozilla/5.0 (Windows; U; Windows NT 5.0; en-US; rv:1.7) Gecko/20040616 X-Accept-Language: en-us, en MIME-Version: 1.0 To: Adrian Farrel Subject: Re: [mpls] MPLS over L2TPv3 as WG item References: <42003648.8030206@cisco.com> <420343B3.1050808@pi.se> <039c01c50b7a$5e66fad0$70cb2bd4@Puppy> In-Reply-To: <039c01c50b7a$5e66fad0$70cb2bd4@Puppy> Content-Type: text/plain; charset=us-ascii; format=flowed Content-Transfer-Encoding: 7bit X-Spam-Score: 0.0 (/) X-Scan-Signature: 10ba05e7e8a9aa6adb025f426bef3a30 Content-Transfer-Encoding: 7bit Cc: mpls@ietf.org X-BeenThere: mpls@lists.ietf.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Multi-Protocol Label Switching WG List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Sender: mpls-bounces@ietf.org Errors-To: mpls-bounces@ietf.org X-Spam-Score: 0.0 (/) X-Scan-Signature: a2c12dacc0736f14d6b540e805505a86 Content-Transfer-Encoding: 7bit Adrian Farrel wrote: > Well, I suppose it does not harm. But does it do any good? > > Looking at the current draft, there are no protocol specifications and no > code point definitions. The draft boils down to a statement that the > payload of an L2TP packet may be an MPLS packet, some restatements from > L2TPv3 about how the L2TP fields should be set, and an applicability > statement. The focus on encapsulation alone in this draft was made at the WG's request. - Mark > > I would suggest that this should be simply recast as an informational > draft making an applicability statement for MPLS over L2TP. > > Regards, > Adrian > ----- Original Message ----- > From: "Loa Andersson" > To: "W. Mark Townsley" > Cc: > Sent: Friday, February 04, 2005 9:43 AM > Subject: Re: [mpls] MPLS over L2TPv3 as WG item > > > >>Working Group, >> >>the reception of the draft was a wee bit ambigious (some no, some no >>need and some yes), with some service providers strongly in favor. >>We would like to poll the working group on whether we want to make >>draft-townsley-mpls-over-l2tpv3-00.txt a wg doc. >> >>To make it possible to publish a working group document, given a rough >>consensus in the wg, we need to have comments Feb 11. >> >>Send comments to the mailing list or wg chairs. We are looking for >>both positive and negative comments. >> >>/Loa and George >> >>W. Mark Townsley wrote: >> >> >>>As requested by Loa at the last MPLS WG meeting, I have renamed the > > MPLS > >>>over L2TPv3 draft as follows: >>> >>>draft-townsley-mpls-over-l2tpv3-00.txt >>> >>>With consensus confirmation from this list, I would like to resubmit >>>this version as a WG item (preferably before the upcoming deadline for >>>the next meeting). >>> >>>Thanks, >>> >>>- Mark >>> >>> >>>_______________________________________________ >>>mpls mailing list >>>mpls@lists.ietf.org >>>https://www1.ietf.org/mailman/listinfo/mpls >>> >> >>-- >>Loa Andersson >> >>Principal Networking Architect >>Acreo AB phone: +46 8 632 77 14 >>Isafjordsgatan 22 mobile: +46 739 81 21 64 >>Kista, Sweden email: loa.andersson@acreo.se >> loa@pi.se >> >>_______________________________________________ >>mpls mailing list >>mpls@lists.ietf.org >>https://www1.ietf.org/mailman/listinfo/mpls >> >> > > _______________________________________________ mpls mailing list mpls@lists.ietf.org https://www1.ietf.org/mailman/listinfo/mpls From mpls-bounces@ietf.org Sat Feb 5 16:40:55 2005 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 QAA01640; Sat, 5 Feb 2005 16:40:55 -0500 (EST) Received: from megatron.ietf.org ([132.151.6.71]) by ietf-mx.ietf.org with esmtp (Exim 4.33) id 1CxXyp-00005v-2k; Sat, 05 Feb 2005 17:00:39 -0500 Received: from localhost.localdomain ([127.0.0.1] helo=megatron.ietf.org) by megatron.ietf.org with esmtp (Exim 4.32) id 1CxXcr-0003cx-M8; Sat, 05 Feb 2005 16:37:57 -0500 Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org) by megatron.ietf.org with esmtp (Exim 4.32) id 1CxXc1-0003WP-Nv for mpls@megatron.ietf.org; Sat, 05 Feb 2005 16:37:05 -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 QAA01399 for ; Sat, 5 Feb 2005 16:37:03 -0500 (EST) Received: from omr1.netsolmail.com ([216.168.230.162]) by ietf-mx.ietf.org with esmtp (Exim 4.33) id 1CxXv4-0008Sm-6j for mpls@ietf.org; Sat, 05 Feb 2005 16:56:47 -0500 Received: from ms9.netsolmail.com (IDENT:mirapoint@[216.168.230.183]) by omr1.netsolmail.com (8.12.10/8.12.10) with ESMTP id j15LakTh005094 for ; Sat, 5 Feb 2005 16:36:50 -0500 (EST) Received: from ms9.netsolmail.com (localhost.netsolmail.com [127.0.0.1]) by ms9.netsolmail.com (Mirapoint Messaging Server MOS 3.2.2-GA) with ESMTP id CNP26550; Sat, 5 Feb 2005 16:36:44 -0500 (EST) Message-Id: <200502052136.CNP26550@ms9.netsolmail.com> Received: from 81.178.20.174 by ms9.netsolmail.com (Mirapoint Messaging Server MOS 3.2.2-GA) with HTTP/1.1; Sat, 5 Feb 2005 21:36:44 GMT Date: Sat, 5 Feb 2005 21:36:44 GMT From: Mark Lewis Subject: RE: [mpls] MPLS over L2TPv3 as WG item To: mpls@ietf.org X-Mailer: Webmail Mirapoint Direct 3.2.2-GA MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit X-Spam-Score: 0.8 (/) X-Scan-Signature: 10ba05e7e8a9aa6adb025f426bef3a30 Content-Transfer-Encoding: 7bit X-BeenThere: mpls@lists.ietf.org X-Mailman-Version: 2.1.5 Precedence: list Reply-To: mark@mjlnet.com 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: a2c12dacc0736f14d6b540e805505a86 Content-Transfer-Encoding: 7bit I also support making it a working group item. Mark > >>From: "Dean Cheng (dcheng)" >>Reply-To: dcheng@cisco.com >>To: "'Loa Andersson'" , "'W. Mark Townsley'" >> >>CC: mpls@ietf.org >>Subject: RE: [mpls] MPLS over L2TPv3 as WG item >>Date: Fri, 4 Feb 2005 13:50:53 -0800 >> >>Support to make it a WG item. >> >>Dean >> >-----Original Message----- >> >From: mpls-bounces@lists.ietf.org >> >[mailto:mpls-bounces@lists.ietf.org] On Behalf Of Loa Andersson >> >Sent: Friday, February 04, 2005 1:43 AM >> >To: W. Mark Townsley >> >Cc: mpls@ietf.org >> >Subject: Re: [mpls] MPLS over L2TPv3 as WG item >> > >> >Working Group, >> > >> >the reception of the draft was a wee bit ambigious (some no, >> >some no need and some yes), with some service providers >> >strongly in favor. >> >We would like to poll the working group on whether we want to >> >make draft-townsley-mpls-over-l2tpv3-00.txt a wg doc. >> > >> >To make it possible to publish a working group document, given >> >a rough consensus in the wg, we need to have comments Feb 11. >> > >> >Send comments to the mailing list or wg chairs. We are looking >> >for both positive and negative comments. >> > >> >/Loa and George >> > >> >W. Mark Townsley wrote: >> > >> >> >> >> As requested by Loa at the last MPLS WG meeting, I have renamed the >> >> MPLS over L2TPv3 draft as follows: >> >> >> >> draft-townsley-mpls-over-l2tpv3-00.txt >> >> >> >> With consensus confirmation from this list, I would like to resubmit >> >> this version as a WG item (preferably before the upcoming >> >deadline for >> >> the next meeting). >> >> >> >> Thanks, >> >> >> >> - Mark >> >> >> >> >> >> _______________________________________________ >> >> mpls mailing list >> >> mpls@lists.ietf.org >> >> https://www1.ietf.org/mailman/listinfo/mpls >> >> >> > >> >-- >> >Loa Andersson >> > >> >Principal Networking Architect >> >Acreo AB phone: +46 8 632 77 14 >> >Isafjordsgatan 22 mobile: +46 739 81 21 64 >> >Kista, Sweden email: loa.andersson@acreo.se >> > loa@pi.se >> > >> >_______________________________________________ >> >mpls mailing list >> >mpls@lists.ietf.org >> >https://www1.ietf.org/mailman/listinfo/mpls >> > >> >>_______________________________________________ >>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 Sun Feb 6 09:19:49 2005 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 JAA24190; Sun, 6 Feb 2005 09:19:49 -0500 (EST) Received: from megatron.ietf.org ([132.151.6.71]) by ietf-mx.ietf.org with esmtp (Exim 4.33) id 1CxnZY-0006Jj-SC; Sun, 06 Feb 2005 09:39:41 -0500 Received: from localhost.localdomain ([127.0.0.1] helo=megatron.ietf.org) by megatron.ietf.org with esmtp (Exim 4.32) id 1CxnEp-0005GY-FO; Sun, 06 Feb 2005 09:18:11 -0500 Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org) by megatron.ietf.org with esmtp (Exim 4.32) id 1Cx5Y1-0003P8-OB for mpls@megatron.ietf.org; Fri, 04 Feb 2005 10:39:05 -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 KAA07581 for ; Fri, 4 Feb 2005 10:39:03 -0500 (EST) Received: from zcars04e.nortelnetworks.com ([47.129.242.56]) by ietf-mx.ietf.org with esmtp (Exim 4.33) id 1Cx5qm-0004Yz-86 for mpls@ietf.org; Fri, 04 Feb 2005 10:58:31 -0500 Received: from zrtpd0jn.us.nortel.com (zrtpd0jn.us.nortel.com [47.140.202.35]) by zcars04e.nortelnetworks.com (Switch-2.2.6/Switch-2.2.0) with ESMTP id j14FcPl08025; Fri, 4 Feb 2005 10:38:25 -0500 (EST) Received: by zrtpd0jn.us.nortel.com with Internet Mail Service (5.5.2653.19) id <1JJLG7VB>; Fri, 4 Feb 2005 10:38:25 -0500 Message-ID: <87AC5F88F03E6249AEA68D40BD3E00BE019BC6D3@zcarhxm2.corp.nortel.com> From: "David Allan" To: "'Loa Andersson'" , "W. Mark Townsley" Subject: RE: [mpls] MPLS over L2TPv3 as WG item Date: Fri, 4 Feb 2005 10:38:04 -0500 X-Mailer: Internet Mail Service (5.5.2653.19) X-Spam-Score: 0.0 (/) X-Scan-Signature: d17f825e43c9aed4fd65b7edddddec89 X-Mailman-Approved-At: Sun, 06 Feb 2005 09:18:09 -0500 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: cf4fa59384e76e63313391b70cd0dd25 Hi: I could support it if there was a stated intention to deprecate PWs over L2TPv3 as done today (aka not really interoperable in any simple sense with PWs over MPLS or MPLSinIP) which IMO would be a useful simplification... Otherwise it is simply one MORE way to do the same thing and I for one don't have the cycles for that... rgds Dave _______________________________________________ mpls mailing list mpls@lists.ietf.org https://www1.ietf.org/mailman/listinfo/mpls From mpls-bounces@ietf.org Sun Feb 6 21:05:49 2005 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 VAA19658; Sun, 6 Feb 2005 21:05:49 -0500 (EST) Received: from megatron.ietf.org ([132.151.6.71]) by ietf-mx.ietf.org with esmtp (Exim 4.33) id 1Cxyax-0003JA-QF; Sun, 06 Feb 2005 21:25:48 -0500 Received: from localhost.localdomain ([127.0.0.1] helo=megatron.ietf.org) by megatron.ietf.org with esmtp (Exim 4.32) id 1CxyFW-00023L-A8; Sun, 06 Feb 2005 21:03:38 -0500 Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org) by megatron.ietf.org with esmtp (Exim 4.32) id 1CxyAJ-0000xH-Dc for mpls@megatron.ietf.org; Sun, 06 Feb 2005 20:58: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 UAA18739 for ; Sun, 6 Feb 2005 20:58:13 -0500 (EST) Received: from ams-iport-1.cisco.com ([144.254.224.140]) by ietf-mx.ietf.org with esmtp (Exim 4.33) id 1CxyTc-00036Q-2v for mpls@ietf.org; Sun, 06 Feb 2005 21:18:12 -0500 Received: from ams-core-1.cisco.com (144.254.224.150) by ams-iport-1.cisco.com with ESMTP; 07 Feb 2005 03:09:20 +0100 X-BrightmailFiltered: true X-Brightmail-Tracker: AAAAAA== Received: from xbh-ams-331.cisco.com (xbh-ams-331.cisco.com [144.254.231.71]) by ams-core-1.cisco.com (8.12.10/8.12.6) with ESMTP id j171velu020872; Mon, 7 Feb 2005 02:57:40 +0100 (MET) Received: from xmb-ams-33a.cisco.com ([144.254.231.85]) by xbh-ams-331.cisco.com with Microsoft SMTPSVC(6.0.3790.211); Mon, 7 Feb 2005 02:57:39 +0100 X-MimeOLE: Produced By Microsoft Exchange V6.5.7226.0 Content-class: urn:content-classes:message MIME-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: quoted-printable Subject: RE: [mpls] MPLS over L2TPv3 as WG item Date: Mon, 7 Feb 2005 02:57:39 +0100 Message-ID: Thread-Topic: [mpls] MPLS over L2TPv3 as WG item Thread-Index: AcUKoCVz5rfxH+f6TNmlSbgSGdwBHgCF6aCw From: "Monique Morrow \(mmorrow\)" To: "Loa Andersson" , "Mark Townsley \(townsley\)" X-OriginalArrivalTime: 07 Feb 2005 01:57:39.0938 (UTC) FILETIME=[67784C20:01C50CB8] X-Spam-Score: 0.0 (/) X-Scan-Signature: b4a0a5f5992e2a4954405484e7717d8c 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: 92df29fa99cf13e554b84c8374345c17 Content-Transfer-Encoding: quoted-printable Support this draft as WG. /m -----Original Message----- From: mpls-bounces@lists.ietf.org [mailto:mpls-bounces@lists.ietf.org] On Behalf Of Loa Andersson Sent: 04 February 2005 10:43 To: Mark Townsley (townsley) Cc: mpls@ietf.org Subject: Re: [mpls] MPLS over L2TPv3 as WG item Working Group, the reception of the draft was a wee bit ambigious (some no, some no need and some yes), with some service providers strongly in favor. We would like to poll the working group on whether we want to make draft-townsley-mpls-over-l2tpv3-00.txt a wg doc. To make it possible to publish a working group document, given a rough consensus in the wg, we need to have comments Feb 11. Send comments to the mailing list or wg chairs. We are looking for both positive and negative comments. /Loa and George W. Mark Townsley wrote: >=20 > As requested by Loa at the last MPLS WG meeting, I have renamed the MPLS=20 > over L2TPv3 draft as follows: >=20 > draft-townsley-mpls-over-l2tpv3-00.txt >=20 > With consensus confirmation from this list, I would like to resubmit=20 > this version as a WG item (preferably before the upcoming deadline for > the next meeting). >=20 > Thanks, >=20 > - Mark >=20 >=20 > _______________________________________________ > mpls mailing list > mpls@lists.ietf.org > https://www1.ietf.org/mailman/listinfo/mpls >=20 --=20 Loa Andersson Principal Networking Architect Acreo AB phone: +46 8 632 77 14 Isafjordsgatan 22 mobile: +46 739 81 21 64 Kista, Sweden email: loa.andersson@acreo.se loa@pi.se _______________________________________________ mpls mailing list mpls@lists.ietf.org https://www1.ietf.org/mailman/listinfo/mpls _______________________________________________ mpls mailing list mpls@lists.ietf.org https://www1.ietf.org/mailman/listinfo/mpls From mpls-bounces@ietf.org Mon Feb 7 03:59:33 2005 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 DAA07448; Mon, 7 Feb 2005 03:59:33 -0500 (EST) Received: from megatron.ietf.org ([132.151.6.71]) by ietf-mx.ietf.org with esmtp (Exim 4.33) id 1Cy53P-0002mq-NS; Mon, 07 Feb 2005 04:19:36 -0500 Received: from localhost.localdomain ([127.0.0.1] helo=megatron.ietf.org) by megatron.ietf.org with esmtp (Exim 4.32) id 1Cy4eI-00081O-1V; Mon, 07 Feb 2005 03:53:38 -0500 Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org) by megatron.ietf.org with esmtp (Exim 4.32) id 1Cy4bh-0007YU-Uj for mpls@megatron.ietf.org; Mon, 07 Feb 2005 03:50:58 -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 DAA06877 for ; Mon, 7 Feb 2005 03:50:55 -0500 (EST) From: richard.spencer@bt.com Received: from smtp3.smtp.bt.com ([217.32.164.138]) by ietf-mx.ietf.org with esmtp (Exim 4.33) id 1Cy4v4-0002b8-8k for mpls@ietf.org; Mon, 07 Feb 2005 04:10:58 -0500 Received: from i2km98-ukbr.domain1.systemhost.net ([193.113.197.85]) by smtp3.smtp.bt.com with Microsoft SMTPSVC(6.0.3790.80); Mon, 7 Feb 2005 08:52:03 +0000 Received: from i2km41-ukdy.domain1.systemhost.net ([193.113.30.29]) by i2km98-ukbr.domain1.systemhost.net with Microsoft SMTPSVC(5.0.2195.6713); Mon, 7 Feb 2005 08:52:02 +0000 X-MimeOLE: Produced By Microsoft Exchange V6.0.6487.1 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] MPLS over L2TPv3 as WG item Date: Mon, 7 Feb 2005 08:52:01 -0000 Message-ID: Thread-Topic: [mpls] MPLS over L2TPv3 as WG item Thread-Index: AcUKoCpgqR8bpb3WTAm7MJAMl+dRVQCTrz4Q To: , X-OriginalArrivalTime: 07 Feb 2005 08:52:02.0563 (UTC) FILETIME=[4ABFCD30:01C50CF2] X-Spam-Score: 0.3 (/) X-Scan-Signature: 5011df3e2a27abcc044eaa15befcaa87 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.3 (/) X-Scan-Signature: a87a9cdae4ac5d3fbeee75cd0026d632 Content-Transfer-Encoding: quoted-printable If an operator already has L2TP deployed, why not just continue to use = L2TP VPNs? Why go to the trouble of upgrading the edge to support MPLS = and leave L2TP in the core? Surely the real advantages of using MPLS are = for CAC, FRR, and TE across the core. This isn't analogous to the IP/GRE = case as these don't have their own muxing capabilities and therefore = MPLS is used for this purpose. So in the MPLS over L2TP case, what = advantages does swapping one muxing field at the edge for another have?=20 If its a greenfield network, again why would an operator choose to = deploy a mesh of PE-PE L2TP tunnels in the core with MPLS just at the = edge? The operator would have all the downsides of using MPLS (i.e. an = extra protocol to manage/troubleshoot) with none of the benefits. The only scenarios I can think of where L2TP would make sense are: i) Migration: If an operator is migrating from L2TP over to MPLS = (short term solution) ii) Support for multiple PSN types: If an operator had deployed (or = acquired) IP/L2TP and MPLS PSNs (probably short term solution if the = operator is looking for convergence) iii) Inter-provider: a) Where an operator with an L2TP network wants to = offer peer-to-peer inter-provider VPNs with another operator that uses = MPLS (avoids PW demux/signalling interworking), or b) where an operator = with an L2TP network wants to offer MPLS transit services, or c) where = two MPLS VPN providers want to use IP ASBR-ASBR instead of MPLS and want = use the L2TP cookie for increased security over IP/GRE.=20 Are these the types of scenarios that those supporting the draft need it = for? If so perhaps it would be worth adding them to the applicability = statement. Regards, Richard > -----Original Message----- > From: mpls-bounces@lists.ietf.org=20 > [mailto:mpls-bounces@lists.ietf.org]On > Behalf Of Loa Andersson > Sent: 04 February 2005 09:43 > To: W. Mark Townsley > Cc: mpls@ietf.org > Subject: Re: [mpls] MPLS over L2TPv3 as WG item >=20 >=20 > Working Group, >=20 > the reception of the draft was a wee bit ambigious (some no, some no > need and some yes), with some service providers strongly in favor. > We would like to poll the working group on whether we want to make > draft-townsley-mpls-over-l2tpv3-00.txt a wg doc. >=20 > To make it possible to publish a working group document, given a rough > consensus in the wg, we need to have comments Feb 11. >=20 > Send comments to the mailing list or wg chairs. We are looking for > both positive and negative comments. >=20 > /Loa and George >=20 > W. Mark Townsley wrote: >=20 > >=20 > > As requested by Loa at the last MPLS WG meeting, I have=20 > renamed the MPLS=20 > > over L2TPv3 draft as follows: > >=20 > > draft-townsley-mpls-over-l2tpv3-00.txt > >=20 > > With consensus confirmation from this list, I would like to=20 > resubmit=20 > > this version as a WG item (preferably before the upcoming=20 > deadline for=20 > > the next meeting). > >=20 > > Thanks, > >=20 > > - Mark > >=20 > >=20 > > _______________________________________________ > > mpls mailing list > > mpls@lists.ietf.org > > https://www1.ietf.org/mailman/listinfo/mpls > >=20 >=20 > --=20 > Loa Andersson >=20 > Principal Networking Architect > Acreo AB phone: +46 8 632 77 14 > Isafjordsgatan 22 mobile: +46 739 81 21 64 > Kista, Sweden email: loa.andersson@acreo.se > loa@pi.se >=20 > _______________________________________________ > mpls mailing list > mpls@lists.ietf.org > https://www1.ietf.org/mailman/listinfo/mpls >=20 _______________________________________________ mpls mailing list mpls@lists.ietf.org https://www1.ietf.org/mailman/listinfo/mpls From mpls-bounces@ietf.org Mon Feb 7 08:11:50 2005 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 IAA26241; Mon, 7 Feb 2005 08:11:49 -0500 (EST) Received: from megatron.ietf.org ([132.151.6.71]) by ietf-mx.ietf.org with esmtp (Exim 4.33) id 1Cy8zZ-0008Kv-Aq; Mon, 07 Feb 2005 08:31:54 -0500 Received: from localhost.localdomain ([127.0.0.1] helo=megatron.ietf.org) by megatron.ietf.org with esmtp (Exim 4.32) id 1Cy8cZ-0001nC-DK; Mon, 07 Feb 2005 08:08:07 -0500 Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org) by megatron.ietf.org with esmtp (Exim 4.32) id 1Cy8aA-0001Fi-3W for mpls@megatron.ietf.org; Mon, 07 Feb 2005 08:05: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 IAA25357 for ; Mon, 7 Feb 2005 08:05:35 -0500 (EST) Received: from smtp2.clb.oleane.net ([213.56.31.18]) by ietf-mx.ietf.org with esmtp (Exim 4.33) id 1Cy8tU-00081O-N0 for mpls@ietf.org; Mon, 07 Feb 2005 08:25:40 -0500 Received: from PAVILLONTROIS (upperside.rain.fr [194.206.151.59] (may be forged)) (authenticated) by smtp2.clb.oleane.net with ESMTP id j17D4hGk028682 for ; Mon, 7 Feb 2005 14:04:46 +0100 Message-Id: <200502071304.j17D4hGk028682@smtp2.clb.oleane.net> From: "Michel Gosse" To: Date: Mon, 7 Feb 2005 14:04:40 +0100 Organization: Upper Side Conferences MIME-Version: 1.0 X-Mailer: Microsoft Office Outlook, Build 11.0.5510 X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2800.1441 Thread-Index: AcUNFZVG4LWPnpPYSZa+ukAr3XhERQ== X-Spam-Score: 0.1 (/) X-Scan-Signature: f2984bf50fb52a9e56055f779793d783 Subject: [mpls] MPLS World Paris 2005 X-BeenThere: mpls@lists.ietf.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Multi-Protocol Label Switching WG List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Content-Type: multipart/mixed; boundary="===============0914399997==" Sender: mpls-bounces@ietf.org Errors-To: mpls-bounces@ietf.org X-Spam-Score: 0.1 (/) X-Scan-Signature: 7268a2980febc47a9fa732aba2b737ba This is a multi-part message in MIME format. --===============0914399997== Content-Type: multipart/alternative; boundary="----=_NextPart_000_0005_01C50D1D.F7B20960" This is a multi-part message in MIME format. ------=_NextPart_000_0005_01C50D1D.F7B20960 Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit MPLS World Congress 2005 will stand in Paris next week. Voice over MPLS is the most important session covered during this edition (with interdomain and VPN/VPLS issues). This year, the interop platform will cover OAM, multiservice and VPLS issues. Only few seats left. To get more info: http://www.upperside.fr/mplsworldcongress05/mplsworld2005intro.htm Thanks. Michel Gosse michelg@upperside.fr ------=_NextPart_000_0005_01C50D1D.F7B20960 Content-Type: text/html; charset="us-ascii" Content-Transfer-Encoding: quoted-printable

MPLS World Congress 2005 will stand in Paris next week.

Voice over MPLS is the most important session = covered during this edition (with interdomain and VPN/VPLS = issues).

 

This year, the interop platform = will cover OAM, multiservice and VPLS = issues.

 

Only few seats left. To get more info: = http://www.upperside.fr/mplsworldcongress05/mplsworld2005intro.htm

 

Thanks.

 

Michel Gosse

michelg@upperside.fr

 

------=_NextPart_000_0005_01C50D1D.F7B20960-- --===============0914399997== 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 --===============0914399997==-- From mpls-bounces@ietf.org Mon Feb 7 12:16:52 2005 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 MAA18352; Mon, 7 Feb 2005 12:16:52 -0500 (EST) Received: from megatron.ietf.org ([132.151.6.71]) by ietf-mx.ietf.org with esmtp (Exim 4.33) id 1CyCom-0005cM-N2; Mon, 07 Feb 2005 12:37:01 -0500 Received: from localhost.localdomain ([127.0.0.1] helo=megatron.ietf.org) by megatron.ietf.org with esmtp (Exim 4.32) id 1CyCTI-0000ND-8J; Mon, 07 Feb 2005 12:14:48 -0500 Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org) by megatron.ietf.org with esmtp (Exim 4.32) id 1CyCJS-00065X-LV for mpls@megatron.ietf.org; Mon, 07 Feb 2005 12:04: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 MAA17074 for ; Mon, 7 Feb 2005 12:04:35 -0500 (EST) Received: from rtp-iport-1.cisco.com ([64.102.122.148]) by ietf-mx.ietf.org with esmtp (Exim 4.33) id 1CyCct-0005Dr-Dg for mpls@ietf.org; Mon, 07 Feb 2005 12:24:43 -0500 Received: from rtp-core-1.cisco.com (64.102.124.12) by rtp-iport-1.cisco.com with ESMTP; 07 Feb 2005 12:15:04 -0500 X-BrightmailFiltered: true X-Brightmail-Tracker: AAAAAA== Received: from fruitpie.cisco.com (IDENT:mirapoint@fruitpie.cisco.com [64.102.16.27]) by rtp-core-1.cisco.com (8.12.10/8.12.6) with ESMTP id j17H441j001375; Mon, 7 Feb 2005 12:04:05 -0500 (EST) Received: from [10.83.1.105] (rtp-townsley-vpn8.cisco.com [10.83.1.105]) by fruitpie.cisco.com (MOS 3.4.6-GR) with SMTP id BFD20796; Mon, 7 Feb 2005 09:04:02 -0800 (PST) Message-ID: <42079F81.8090308@cisco.com> Date: Mon, 07 Feb 2005 12:04:01 -0500 From: "W. Mark Townsley" User-Agent: Mozilla/5.0 (Windows; U; Windows NT 5.0; en-US; rv:1.7) Gecko/20040616 X-Accept-Language: en-us, en MIME-Version: 1.0 To: richard.spencer@bt.com Subject: Re: [mpls] MPLS over L2TPv3 as WG item References: In-Reply-To: Content-Type: text/plain; charset=us-ascii; format=flowed Content-Transfer-Encoding: 7bit X-Spam-Score: 0.0 (/) X-Scan-Signature: 8f374d0786b25a451ef87d82c076f593 Content-Transfer-Encoding: 7bit Cc: mpls@ietf.org X-BeenThere: mpls@lists.ietf.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Multi-Protocol Label Switching WG List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Sender: mpls-bounces@ietf.org Errors-To: mpls-bounces@ietf.org X-Spam-Score: 0.0 (/) X-Scan-Signature: 200d029292fbb60d25b263122ced50fc Content-Transfer-Encoding: 7bit Richard, Thanks for the comments. A few replies inline. richard.spencer@bt.com wrote: > If an operator already has L2TP deployed, why not just continue to use L2TP > VPNs? Why go to the trouble of upgrading the edge to support MPLS and leave > L2TP in the core? L2TP(v3) is an edge-based service carried over IP, and thus is not "in" the core any more than any other protocol running over IP that the core happens to be carrying. P routers should not have a clue that L2TP exists. > Surely the real advantages of using MPLS are for CAC, FRR, > and TE across the core. These are features of MPLS that L2TP does not aim to provide. But, L2TP does not inhibit one from using MPLS within a portion of, or the entirety of, the IP network that L2TP is passing over. > This isn't analogous to the IP/GRE case as these > don't have their own muxing capabilities and therefore MPLS is used for this > purpose. Just to be clear, GRE has a muxing capability via its 32-bit Key. > So in the MPLS over L2TP case, what advantages does swapping one > muxing field at the edge for another have? For example, if an "MPLS VPN" (as its own named service) is being muxed along with other services already being provided by L2TPv3 - FR, ATM, etc. > > If its a greenfield network, again why would an operator choose to deploy a > mesh of PE-PE L2TP tunnels in the core with MPLS just at the edge? Note that the actual application may include point to multipoint L2TPv3 Session IDs (not a mesh of L2TP tunnels in the RFC2661 sense of the term). But, that is to some degree outside the boundaries of this document which has been scoped to just define the encapsulation format. > The > operator would have all the downsides of using MPLS (i.e. an extra protocol > to manage/troubleshoot) with none of the benefits. > > The only scenarios I can think of where L2TP would make sense are: > > i) Migration: If an operator is migrating from L2TP over to MPLS (short > term solution) ii) Support for multiple PSN types: If an operator had > deployed (or acquired) IP/L2TP and MPLS PSNs (probably short term solution if > the operator is looking for convergence) iii) Inter-provider: a) Where an > operator with an L2TP network wants to offer peer-to-peer inter-provider VPNs > with another operator that uses MPLS (avoids PW demux/signalling > interworking), or b) where an operator with an L2TP network wants to offer > MPLS transit services, or c) where two MPLS VPN providers want to use IP > ASBR-ASBR instead of MPLS and want use the L2TP cookie for increased security > over IP/GRE. > > Are these the types of scenarios that those supporting the draft need it for? > If so perhaps it would be worth adding them to the applicability statement. I believe some of these statements are on target, though I would rather pry them open in a separate thread - and perhaps on a different list (e.g., L2VPN or L3VPN). In any case, I would be happy to see these captured and worked on in more detail if the draft emerges as a WG document. Thanks, - Mark > > Regards, Richard > > >> -----Original Message----- From: mpls-bounces@lists.ietf.org >> [mailto:mpls-bounces@lists.ietf.org]On Behalf Of Loa Andersson Sent: 04 >> February 2005 09:43 To: W. Mark Townsley Cc: mpls@ietf.org Subject: Re: >> [mpls] MPLS over L2TPv3 as WG item >> >> >> Working Group, >> >> the reception of the draft was a wee bit ambigious (some no, some no need >> and some yes), with some service providers strongly in favor. We would like >> to poll the working group on whether we want to make >> draft-townsley-mpls-over-l2tpv3-00.txt a wg doc. >> >> To make it possible to publish a working group document, given a rough >> consensus in the wg, we need to have comments Feb 11. >> >> Send comments to the mailing list or wg chairs. We are looking for both >> positive and negative comments. >> >> /Loa and George >> >> W. Mark Townsley wrote: >> >> >>> As requested by Loa at the last MPLS WG meeting, I have >> >> renamed the MPLS >> >>> over L2TPv3 draft as follows: >>> >>> draft-townsley-mpls-over-l2tpv3-00.txt >>> >>> With consensus confirmation from this list, I would like to >> >> resubmit >> >>> this version as a WG item (preferably before the upcoming >> >> deadline for >> >>> the next meeting). >>> >>> Thanks, >>> >>> - Mark >>> >>> >>> _______________________________________________ mpls mailing list >>> mpls@lists.ietf.org https://www1.ietf.org/mailman/listinfo/mpls >>> >> >> -- Loa Andersson >> >> Principal Networking Architect Acreo AB phone: >> +46 8 632 77 14 Isafjordsgatan 22 mobile: +46 739 81 21 64 >> Kista, Sweden email: loa.andersson@acreo.se >> loa@pi.se >> >> _______________________________________________ mpls mailing list >> mpls@lists.ietf.org https://www1.ietf.org/mailman/listinfo/mpls >> > > > _______________________________________________ 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 Mon Feb 7 12:26:40 2005 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 MAA19663; Mon, 7 Feb 2005 12:26:40 -0500 (EST) Received: from megatron.ietf.org ([132.151.6.71]) by ietf-mx.ietf.org with esmtp (Exim 4.33) id 1CyCyH-0005ta-0a; Mon, 07 Feb 2005 12:46:49 -0500 Received: from localhost.localdomain ([127.0.0.1] helo=megatron.ietf.org) by megatron.ietf.org with esmtp (Exim 4.32) id 1CyCTg-0000gH-0S; Mon, 07 Feb 2005 12:15:12 -0500 Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org) by megatron.ietf.org with esmtp (Exim 4.32) id 1CyCR8-0007uL-P4 for mpls@megatron.ietf.org; Mon, 07 Feb 2005 12:12:34 -0500 Received: from smtp2.dataconnection.com (smtp2.dataconnection.com [192.91.191.8]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id MAA17878 for ; Mon, 7 Feb 2005 12:12:31 -0500 (EST) Received: from enfismtp2.datcon.co.uk ([172.19.16.2]) by smtp2.dataconnection.com with Microsoft SMTPSVC(6.0.3790.211); Mon, 7 Feb 2005 17:12:02 +0000 Content-class: urn:content-classes:message MIME-Version: 1.0 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: quoted-printable X-MimeOLE: Produced By Microsoft Exchange V6.5.7226.0 Date: Mon, 7 Feb 2005 17:11:54 -0000 Message-ID: <53F74F5A7B94D511841C00B0D0AB16F8057D8BC1@baker.datcon.co.uk> Thread-Topic: Signalling unnumbered links in RSVP-TE for IPv6 networks Thread-Index: AcUNOCOR982V77OLRxOBnMOxog+P6A== From: "Alan Davey" To: X-OriginalArrivalTime: 07 Feb 2005 17:12:02.0006 (UTC) FILETIME=[23CF8760:01C50D38] Content-Transfer-Encoding: quoted-printable Subject: [mpls] Signalling unnumbered links in RSVP-TE for IPv6 networks X-BeenThere: mpls@lists.ietf.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Multi-Protocol Label Switching WG List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Sender: mpls-bounces@ietf.org Errors-To: mpls-bounces@ietf.org X-Spam-Score: 0.0 (/) X-Scan-Signature: d0bdc596f8dd1c226c458f0b4df27a88 Content-Transfer-Encoding: quoted-printable Hi I have been looking at signalling RSVP-TE LSPs in IPv6 networks. I = think that the standard for signalling unnumbered links in RSVP-TE = requires extension for use in an IPv6 network. RFC3477 defines objects = and subobjects with 32-bit Router IDs. I think that there should be = equivalent objects and subobjects defined with 128-bit router IDs for = use in IPv6 networks. =20 That is, there should be IPv6 equivalents, with 128-bit Router IDs, to = the following. - LSP_TUNNEL_INTERFACE_ID Object. - The Unnumbered Interface ID ERO subobject. - The Unnumbered Interface ID RRO subobject. My reasoning is as follows. - In RFC3477, the term "Router ID" is defined in section 2. to mean a = stable IP address of an LSR that is always reachable if there is any = connectivity to the LSR. - If using OSPF or ISIS as the IGP, then RFC3477 recommends that the = router ID is set to the OSPF-TE "Router Address" or ISIS "TE Router ID". - Recent drafts from the OSPF and ISIS WGs have defined IPv6 traffic = engineering extensions with 128-bit router addresses. - draft-ietf-ospf-ospfv3-traffic, which defines extensions for traffic = engineering to OSPFv3, defines a "Router IPv6 Address" TLV to advertise = a stable IPv6 address that is always reachable if there is connectivity = to the OSPFv3 router. - draft-ietf-isis-ipv6-te defines a 128-bit "IPv6 TE Router ID" for = supporting IPv6 traffic engineering. - The MPLS TE specification needs to change (rather than changing the = OSPF and ISIS drafts) to allow a router in the path of an LSP to be = identified using an IPv6 address. In particular, to allow LSPs to be = signalled using a node IPv6 address where there are no interface = addresses. - Therefore, to signal unnumbered links in RSVP-TE there need to be = objects and subobjects defined that are the equivalent to those defined = in RFC3477 but with 128-bit Router IDs, as suggested above. Is there interest in a draft to specify extensions to RFC3477 for IPv6 = networks? Note also that I think a similar change is required to RFC3812 (TE-MIB) = to allow an IPv6 address to be specified to identify the ingress and = egress routers. All comments are welcome. Regards Alan Davey ------------------------------------ Alan Davey Data Connection Ltd Tel: +44 20 8366 1177 =20 Fax: +44 20 8363 1039 Email: Alan.Davey@dataconnection.com =20 Web: http://www.dataconnection.com=20 _______________________________________________ mpls mailing list mpls@lists.ietf.org https://www1.ietf.org/mailman/listinfo/mpls From mpls-bounces@ietf.org Mon Feb 7 12:57:31 2005 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 MAA24228; Mon, 7 Feb 2005 12:57:31 -0500 (EST) Received: from megatron.ietf.org ([132.151.6.71]) by ietf-mx.ietf.org with esmtp (Exim 4.33) id 1CyDS6-0006qm-FI; Mon, 07 Feb 2005 13:17:40 -0500 Received: from localhost.localdomain ([127.0.0.1] helo=megatron.ietf.org) by megatron.ietf.org with esmtp (Exim 4.32) id 1CyD1G-0001kM-OT; Mon, 07 Feb 2005 12:49:54 -0500 Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org) by megatron.ietf.org with esmtp (Exim 4.32) id 1CyCx1-0001BQ-OK for mpls@megatron.ietf.org; Mon, 07 Feb 2005 12:45: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 MAA23347 for ; Mon, 7 Feb 2005 12:45:28 -0500 (EST) From: richard.spencer@bt.com Received: from smtp2.smtp.bt.com ([217.32.164.150]) by ietf-mx.ietf.org with esmtp (Exim 4.33) id 1CyDGR-0006a1-Tf for mpls@ietf.org; Mon, 07 Feb 2005 13:05:37 -0500 Received: from i2km95-ukbr.domain1.systemhost.net ([193.113.197.29]) by smtp2.smtp.bt.com with Microsoft SMTPSVC(6.0.3790.80); Mon, 7 Feb 2005 17:46:38 +0000 Received: from i2km41-ukdy.domain1.systemhost.net ([193.113.30.29]) by i2km95-ukbr.domain1.systemhost.net with Microsoft SMTPSVC(5.0.2195.6713); Mon, 7 Feb 2005 17:46:34 +0000 X-MimeOLE: Produced By Microsoft Exchange V6.0.6487.1 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] MPLS over L2TPv3 as WG item Date: Mon, 7 Feb 2005 17:46:33 -0000 Message-ID: Thread-Topic: [mpls] MPLS over L2TPv3 as WG item Thread-Index: AcUNN6EkifC7Ri2URxKiRApWwnGkQgAACRGA To: X-OriginalArrivalTime: 07 Feb 2005 17:46:34.0071 (UTC) FILETIME=[F6DB8E70:01C50D3C] X-Spam-Score: 0.3 (/) X-Scan-Signature: bb8f917bb6b8da28fc948aeffb74aa17 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.3 (/) X-Scan-Signature: 7baded97d9887f7a0c7e8a33c2e3ea1b Content-Transfer-Encoding: quoted-printable Mark, Thanks for your response, a few replies inline to provide clarification. > > If an operator already has L2TP deployed, why not just=20 > > continue to use L2TP VPNs? Why go to the trouble of=20 > > upgrading the edge to support MPLS and leave L2TP > > in the core?=20 > > L2TP(v3) is an edge-based service carried over IP, and thus=20 > is not "in" the core any more than any other protocol running=20 > over IP that the core happens to be carrying. P routers should=20 > not have a clue that L2TP exists. When I say leave L2TP in the core, I mean continue to use L2TP on the PE = core facing interfaces to provide PE-PE tunnels across the core, as = opposed to using MPLS PE-PE tunnels across the core. > > This isn't analogous to the IP/GRE case as these don't have > > their own muxing capabilities and therefore MPLS is used for=20 > > this purpose.=20 >=20 > Just to be clear, GRE has a muxing capability via its 32-bit Key. And IP has a muxing capability via its UDP/TCP port numbers. I was = referring here to the use of muxing fields as defined by the IETF PWE3 = WG for VPN muxing. These are currently MPLS or L2TP session IDs (and = maybe IP UDP port numbers, I've lost track of whether on not this has = been accepted by PWE3 as a valid approach). The point being that = PWE/L2VPN L2TP based solutions exist today that do not require MPLS for = muxing, whereas I am not aware of any PWE3/L2VPN IP/GRE solutions that = do not require MPLS labels for muxing. Regards, Richard _______________________________________________ mpls mailing list mpls@lists.ietf.org https://www1.ietf.org/mailman/listinfo/mpls From mpls-bounces@ietf.org Mon Feb 7 13:33:40 2005 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 NAA27505; Mon, 7 Feb 2005 13:33:40 -0500 (EST) Received: from megatron.ietf.org ([132.151.6.71]) by ietf-mx.ietf.org with esmtp (Exim 4.33) id 1CyE17-0007e4-FX; Mon, 07 Feb 2005 13:53:49 -0500 Received: from localhost.localdomain ([127.0.0.1] helo=megatron.ietf.org) by megatron.ietf.org with esmtp (Exim 4.32) id 1CyDej-0000e7-6k; Mon, 07 Feb 2005 13:30:41 -0500 Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org) by megatron.ietf.org with esmtp (Exim 4.32) id 1CyDYd-0007rE-OS for mpls@megatron.ietf.org; Mon, 07 Feb 2005 13:24:23 -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 NAA26622 for ; Mon, 7 Feb 2005 13:24:20 -0500 (EST) Received: from colo-dns-ext2.juniper.net ([207.17.137.64]) by ietf-mx.ietf.org with esmtp (Exim 4.33) id 1CyDs4-0007Qk-C8 for mpls@ietf.org; Mon, 07 Feb 2005 13:44:29 -0500 Received: from merlot.juniper.net (merlot.juniper.net [172.17.27.10]) by colo-dns-ext2.juniper.net (8.12.3/8.12.3) with ESMTP id j17INpBm052720; Mon, 7 Feb 2005 10:23:51 -0800 (PST) (envelope-from yakov@juniper.net) Received: from juniper.net (sapphire.juniper.net [172.17.28.108]) by merlot.juniper.net (8.11.3/8.11.3) with ESMTP id j17INde81670; Mon, 7 Feb 2005 10:23:51 -0800 (PST) (envelope-from yakov@juniper.net) Message-Id: <200502071823.j17INde81670@merlot.juniper.net> To: "David Allan" Subject: Re: [mpls] MPLS over L2TPv3 as WG item In-Reply-To: Your message of "Sat, 05 Feb 2005 08:21:52 EST." <87AC5F88F03E6249AEA68D40BD3E00BE019BC6ED@zcarhxm2.corp.nortel.com> MIME-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Content-ID: <35761.1107800619.1@juniper.net> Date: Mon, 07 Feb 2005 10:23:39 -0800 From: Yakov Rekhter 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: , Sender: mpls-bounces@ietf.org Errors-To: mpls-bounces@ietf.org X-Spam-Score: 0.0 (/) X-Scan-Signature: 7655788c23eb79e336f5f8ba8bce7906 Dave, > Hi: > > I could support it if there was a stated intention to > deprecate PWs over L2TPv3 as done today (aka not really > interoperable in any simple sense with PWs over MPLS or > MPLSinIP) which IMO would be a useful simplification... I support your proposal to make a stated intention to deprecate PW over L2TPv3 as a prerequisite for this document to become a WG item. > Otherwise it is simply one MORE way to do the same thing and > I for one don't have the cycles for that... Agreed. Yakov. _______________________________________________ mpls mailing list mpls@lists.ietf.org https://www1.ietf.org/mailman/listinfo/mpls From mpls-bounces@ietf.org Mon Feb 7 13:43:31 2005 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 NAA28507; Mon, 7 Feb 2005 13:43:31 -0500 (EST) Received: from megatron.ietf.org ([132.151.6.71]) by ietf-mx.ietf.org with esmtp (Exim 4.33) id 1CyEAb-0007tx-Q4; Mon, 07 Feb 2005 14:03:38 -0500 Received: from localhost.localdomain ([127.0.0.1] helo=megatron.ietf.org) by megatron.ietf.org with esmtp (Exim 4.32) id 1CyDnx-0002fJ-UX; Mon, 07 Feb 2005 13:40:13 -0500 Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org) by megatron.ietf.org with esmtp (Exim 4.32) id 1CyDkZ-0001xt-Nv for mpls@megatron.ietf.org; Mon, 07 Feb 2005 13:36: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 NAA27792 for ; Mon, 7 Feb 2005 13:36:38 -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 1CyE3x-0007iA-9M for mpls@ietf.org; Mon, 07 Feb 2005 13:56:46 -0500 Received: from kummer.juniper.net (localhost [127.0.0.1]) by kummer.juniper.net (8.12.8p1/8.12.3) with ESMTP id j17Ia5Xg070270; Mon, 7 Feb 2005 10:36:05 -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 j17Ia1Zd070267; Mon, 7 Feb 2005 10:36:05 -0800 (PST) X-Authentication-Warning: kummer.juniper.net: kireeti owned process doing -bs Date: Mon, 7 Feb 2005 10:36:00 -0800 (PST) From: Kireeti Kompella To: "Drake, John E" Subject: RE: [mpls] MPLS over L2TPv3 as WG item In-Reply-To: <626FC7C6A97381468FB872072AB5DDC805EE5B@XCH-SW-42.sw.nos.boeing.com> Message-ID: <20050207103046.V70192@kummer.juniper.net> References: <626FC7C6A97381468FB872072AB5DDC805EE5B@XCH-SW-42.sw.nos.boeing.com> MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII X-Spam-Score: 0.0 (/) X-Scan-Signature: 68c8cc8a64a9d0402e43b8eee9fc4199 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: de4f315c9369b71d7dd5909b42224370 On Fri, 4 Feb 2005, Drake, John E wrote: > No compelling need for this I agree with John and Adrian ("But does it do any good?") This document would have the effect of confusing the market -- as Dave said, yet another way of doing MPLS over IP. I'm not sure that could be construed as 'doing good' -- I'll leave that to others to judge. Kireeti. ------- _______________________________________________ mpls mailing list mpls@lists.ietf.org https://www1.ietf.org/mailman/listinfo/mpls From mpls-bounces@ietf.org Mon Feb 7 13:46:07 2005 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 NAA28883; Mon, 7 Feb 2005 13:46:06 -0500 (EST) Received: from megatron.ietf.org ([132.151.6.71]) by ietf-mx.ietf.org with esmtp (Exim 4.33) id 1CyED7-0007wp-6u; Mon, 07 Feb 2005 14:06:14 -0500 Received: from localhost.localdomain ([127.0.0.1] helo=megatron.ietf.org) by megatron.ietf.org with esmtp (Exim 4.32) id 1CyDoL-0002mj-1F; Mon, 07 Feb 2005 13:40:37 -0500 Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org) by megatron.ietf.org with esmtp (Exim 4.32) id 1CyDmI-0002If-Ex for mpls@megatron.ietf.org; Mon, 07 Feb 2005 13:38:30 -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 NAA28015 for ; Mon, 7 Feb 2005 13:38:28 -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 1CyE5j-0007kV-51 for mpls@ietf.org; Mon, 07 Feb 2005 13:58:36 -0500 Received: from kummer.juniper.net (localhost [127.0.0.1]) by kummer.juniper.net (8.12.8p1/8.12.3) with ESMTP id j17IbuXg070276; Mon, 7 Feb 2005 10:37:56 -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 j17IbtEb070273; Mon, 7 Feb 2005 10:37:55 -0800 (PST) X-Authentication-Warning: kummer.juniper.net: kireeti owned process doing -bs Date: Mon, 7 Feb 2005 10:37:55 -0800 (PST) From: Kireeti Kompella To: Per Ole Klemetsrud Subject: Re: [mpls] MPLS over L2TPv3 as WG item In-Reply-To: Message-ID: <20050207103619.C70192@kummer.juniper.net> References: <42003648.8030206@cisco.com> <420343B3.1050808@pi.se> MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII X-Spam-Score: 0.0 (/) X-Scan-Signature: 30ac594df0e66ffa5a93eb4c48bcb014 Cc: "W. Mark Townsley" , 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: 1ac7cc0a4cd376402b85bc1961a86ac2 On Sat, 5 Feb 2005, Per Ole Klemetsrud wrote: > From one service providers point if view, it is my hope that vendors will > put their MPLS development resources elsewhere. We'll do our best! :-) Kireeti. ------- _______________________________________________ mpls mailing list mpls@lists.ietf.org https://www1.ietf.org/mailman/listinfo/mpls From mpls-bounces@ietf.org Mon Feb 7 14:49:54 2005 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 OAA04818; Mon, 7 Feb 2005 14:49:54 -0500 (EST) Received: from megatron.ietf.org ([132.151.6.71]) by ietf-mx.ietf.org with esmtp (Exim 4.33) id 1CyFCs-0000wN-W0; Mon, 07 Feb 2005 15:10:03 -0500 Received: from localhost.localdomain ([127.0.0.1] helo=megatron.ietf.org) by megatron.ietf.org with esmtp (Exim 4.32) id 1CyErD-0005iN-Sf; Mon, 07 Feb 2005 14:47:39 -0500 Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org) by megatron.ietf.org with esmtp (Exim 4.32) id 1CyEqR-0005Z7-Iq for mpls@megatron.ietf.org; Mon, 07 Feb 2005 14:46:52 -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 OAA04478 for ; Mon, 7 Feb 2005 14:46:49 -0500 (EST) Received: from zcars04f.nortelnetworks.com ([47.129.242.57]) by ietf-mx.ietf.org with esmtp (Exim 4.33) id 1CyF9t-0000rP-LL for mpls@ietf.org; Mon, 07 Feb 2005 15:06:58 -0500 Received: from zrtpd0j7.us.nortel.com (zrtpd0j7.us.nortel.com [47.140.203.25]) by zcars04f.nortelnetworks.com (Switch-2.2.6/Switch-2.2.0) with ESMTP id j17JkF907638 for ; Mon, 7 Feb 2005 14:46:15 -0500 (EST) Received: by zrtpd0j7.us.nortel.com with Internet Mail Service (5.5.2653.19) id <1J5A3Q8W>; Mon, 7 Feb 2005 14:46:15 -0500 Message-ID: From: "Don Fedyk" Subject: RE: [mpls] MPLS over L2TPv3 as WG item Date: Mon, 7 Feb 2005 14:46:05 -0500 X-Mailer: Internet Mail Service (5.5.2653.19) X-Spam-Score: 0.0 (/) X-Scan-Signature: 1a1bf7677bfe77d8af1ebe0e91045c5b 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: 944ecb6e61f753561f559a497458fb4f Very well put. I'll second that opinion. Regards, Don > -----Original Message----- > From: mpls-bounces@lists.ietf.org > [mailto:mpls-bounces@lists.ietf.org] On Behalf Of Adrian Farrel > Sent: Saturday, February 05, 2005 4:41 AM > To: Loa Andersson; W. Mark Townsley > Cc: mpls@ietf.org > Subject: Re: [mpls] MPLS over L2TPv3 as WG item > > > Well, I suppose it does not harm. But does it do any good? > > Looking at the current draft, there are no protocol > specifications and no code point definitions. The draft boils > down to a statement that the payload of an L2TP packet may be > an MPLS packet, some restatements from L2TPv3 about how the > L2TP fields should be set, and an applicability statement. > > I would suggest that this should be simply recast as an > informational draft making an applicability statement for > MPLS over L2TP. > > Regards, > Adrian > ----- Original Message ----- > From: "Loa Andersson" > To: "W. Mark Townsley" > Cc: > Sent: Friday, February 04, 2005 9:43 AM > Subject: Re: [mpls] MPLS over L2TPv3 as WG item > > > > Working Group, > > > > the reception of the draft was a wee bit ambigious (some > no, some no > > need and some yes), with some service providers strongly in > favor. We > > would like to poll the working group on whether we want to make > > draft-townsley-mpls-over-l2tpv3-00.txt a wg doc. > > > > To make it possible to publish a working group document, > given a rough > > consensus in the wg, we need to have comments Feb 11. > > > > Send comments to the mailing list or wg chairs. We are looking for > > both positive and negative comments. > > > > /Loa and George > > > > W. Mark Townsley wrote: > > > > > > > > As requested by Loa at the last MPLS WG meeting, I have > renamed the > MPLS > > > over L2TPv3 draft as follows: > > > > > > draft-townsley-mpls-over-l2tpv3-00.txt > > > > > > With consensus confirmation from this list, I would like > to resubmit > > > this version as a WG item (preferably before the upcoming > deadline > > > for the next meeting). > > > > > > Thanks, > > > > > > - Mark > > > > > > > > > _______________________________________________ > > > mpls mailing list > > > mpls@lists.ietf.org https://www1.ietf.org/mailman/listinfo/mpls > > > > > > > -- > > Loa Andersson > > > > Principal Networking Architect > > Acreo AB phone: +46 8 632 77 14 > > Isafjordsgatan 22 mobile: +46 739 81 21 64 > > Kista, Sweden email: loa.andersson@acreo.se > > loa@pi.se > > > > _______________________________________________ > > mpls mailing list > > mpls@lists.ietf.org https://www1.ietf.org/mailman/listinfo/mpls > > > > > > > _______________________________________________ > 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 Mon Feb 7 15:08:16 2005 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 PAA06657; Mon, 7 Feb 2005 15:08:16 -0500 (EST) Received: from megatron.ietf.org ([132.151.6.71]) by ietf-mx.ietf.org with esmtp (Exim 4.33) id 1CyFUd-0001La-UR; Mon, 07 Feb 2005 15:28:25 -0500 Received: from localhost.localdomain ([127.0.0.1] helo=megatron.ietf.org) by megatron.ietf.org with esmtp (Exim 4.32) id 1CyF8f-0002fI-F1; Mon, 07 Feb 2005 15:05:41 -0500 Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org) by megatron.ietf.org with esmtp (Exim 4.32) id 1CyF5N-0000Uz-BS for mpls@megatron.ietf.org; Mon, 07 Feb 2005 15:02: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 PAA06024 for ; Mon, 7 Feb 2005 15:02:15 -0500 (EST) Received: from sj-iport-5.cisco.com ([171.68.10.87]) by ietf-mx.ietf.org with esmtp (Exim 4.33) id 1CyFOo-0001CU-Nv for mpls@ietf.org; Mon, 07 Feb 2005 15:22:24 -0500 Received: from sj-core-2.cisco.com (171.71.177.254) by sj-iport-5.cisco.com with ESMTP; 07 Feb 2005 12:03:16 -0800 X-BrightmailFiltered: true X-Brightmail-Tracker: AAAAAA== Received: from cisco.com (erosen-u10.cisco.com [161.44.70.36]) by sj-core-2.cisco.com (8.12.10/8.12.6) with ESMTP id j17K1cq8029940; Mon, 7 Feb 2005 12:01:39 -0800 (PST) Message-Id: <200502072001.j17K1cq8029940@sj-core-2.cisco.com> To: Loa Andersson Subject: Re: [mpls] MPLS over L2TPv3 as WG item In-reply-to: Your message of Fri, 04 Feb 2005 10:43:15 +0100. <420343B3.1050808@pi.se> User-Agent: EMH/1.14.1 SEMI/1.14.3 (Ushinoya) FLIM/1.14.3 (=?ISO-8859-4?Q?Unebigory=F2mae?=) APEL/10.3 Emacs/21.3 (sparc-sun-solaris2.8) MULE/5.0 (SAKAKI) MIME-Version: 1.0 (generated by SEMI 1.14.3 - "Ushinoya") Content-Type: text/plain; charset=US-ASCII Date: Mon, 07 Feb 2005 15:01:40 -0500 From: Eric Rosen X-Spam-Score: 0.0 (/) X-Scan-Signature: 7bac9cb154eb5790ae3b2913587a40de Cc: "W. Mark Townsley" , mpls@ietf.org X-BeenThere: mpls@lists.ietf.org X-Mailman-Version: 2.1.5 Precedence: list Reply-To: erosen@cisco.com 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: 08170828343bcf1325e4a0fb4584481c I support this draft becoming a WG document, as (a) some service providers intend to use it, (b) interoperable standards for things that service providers intend to use are always good (indeed, some have argued that publication of such standards is the primary purpose of the IETF), (c) it does not in any way mess up the architecture of either MPLS or L2TPv3, but rather is a perfectly ordinary and valid use of them, and (d) there are no objective, substantive technical issues with it. _______________________________________________ mpls mailing list mpls@lists.ietf.org https://www1.ietf.org/mailman/listinfo/mpls From mpls-bounces@ietf.org Mon Feb 7 16:37:59 2005 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 QAA24356; Mon, 7 Feb 2005 16:37:59 -0500 (EST) Received: from megatron.ietf.org ([132.151.6.71]) by ietf-mx.ietf.org with esmtp (Exim 4.33) id 1CyGtT-0006Jc-VG; Mon, 07 Feb 2005 16:58:09 -0500 Received: from localhost.localdomain ([127.0.0.1] helo=megatron.ietf.org) by megatron.ietf.org with esmtp (Exim 4.32) id 1CyGJH-00027U-Os; Mon, 07 Feb 2005 16:20:43 -0500 Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org) by megatron.ietf.org with esmtp (Exim 4.32) id 1CyFhc-000560-76 for mpls@megatron.ietf.org; Mon, 07 Feb 2005 15:41:48 -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 PAA11751 for ; Mon, 7 Feb 2005 15:41:46 -0500 (EST) Received: from ams-iport-1.cisco.com ([144.254.224.140]) by ietf-mx.ietf.org with esmtp (Exim 4.33) id 1CyG13-0002KP-WB for mpls@ietf.org; Mon, 07 Feb 2005 16:01:55 -0500 Received: from ams-core-1.cisco.com (144.254.224.150) by ams-iport-1.cisco.com with ESMTP; 07 Feb 2005 21:53:06 +0100 X-BrightmailFiltered: true X-Brightmail-Tracker: AAAAAA== Received: from zaliwxp (che-vpn-cluster-1-110.cisco.com [10.86.240.110]) by ams-core-1.cisco.com (8.12.10/8.12.6) with ESMTP id j17Keilu024485; Mon, 7 Feb 2005 21:40:45 +0100 (MET) Message-Id: <200502072040.j17Keilu024485@ams-core-1.cisco.com> From: "Zafar Ali" To: "'Kireeti Kompella'" , "'Per Ole Klemetsrud'" Subject: RE: [mpls] MPLS over L2TPv3 as WG item Date: Mon, 7 Feb 2005 15:40:43 -0500 MIME-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit X-Mailer: Microsoft Office Outlook, Build 11.0.5510 X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2800.1441 Thread-Index: AcUNRXldeugjvsTISjm9ImVPif1DiQAAfj9g In-Reply-To: <20050207103619.C70192@kummer.juniper.net> X-Spam-Score: 0.0 (/) X-Scan-Signature: 7655788c23eb79e336f5f8ba8bce7906 Content-Transfer-Encoding: 7bit Cc: "'W. Mark Townsley'" , 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: 0bc60ec82efc80c84b8d02f4b0e4de22 Content-Transfer-Encoding: 7bit > -----Original Message----- > From: mpls-bounces@lists.ietf.org > [mailto:mpls-bounces@lists.ietf.org] On Behalf Of Kireeti Kompella > Sent: Monday, February 07, 2005 1:38 PM > To: Per Ole Klemetsrud > Cc: W. Mark Townsley; mpls@ietf.org > Subject: Re: [mpls] MPLS over L2TPv3 as WG item > > On Sat, 5 Feb 2005, Per Ole Klemetsrud wrote: > > > From one service providers point if view, it is my hope > that vendors > > will put their MPLS development resources elsewhere. > > We'll do our best! :-) Per Ole Klemetsrud's comment is for "one service provider", I am happy to service to "many other SP-es" that have this requirement, and not to mention "doing best" ;-) Is "my resources are somewhere else" your reason for reservation ;-) _______________________________________________ mpls mailing list mpls@lists.ietf.org https://www1.ietf.org/mailman/listinfo/mpls From mpls-bounces@ietf.org Mon Feb 7 19:10:24 2005 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 TAA18454; Mon, 7 Feb 2005 19:10:24 -0500 (EST) Received: from megatron.ietf.org ([132.151.6.71]) by ietf-mx.ietf.org with esmtp (Exim 4.33) id 1CyJH2-0004yA-Q1; Mon, 07 Feb 2005 19:30:37 -0500 Received: from localhost.localdomain ([127.0.0.1] helo=megatron.ietf.org) by megatron.ietf.org with esmtp (Exim 4.32) id 1CyIvv-00054K-Vn; Mon, 07 Feb 2005 19:08:47 -0500 Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org) by megatron.ietf.org with esmtp (Exim 4.32) id 1CyItv-0004c3-EW for mpls@megatron.ietf.org; Mon, 07 Feb 2005 19:06: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 TAA18310 for ; Mon, 7 Feb 2005 19:06:40 -0500 (EST) Received: from rtp-iport-2.cisco.com ([64.102.122.149]) by ietf-mx.ietf.org with esmtp (Exim 4.33) id 1CyJDP-0004t5-2R for mpls@ietf.org; Mon, 07 Feb 2005 19:26:52 -0500 Received: from rtp-core-2.cisco.com (64.102.124.13) by rtp-iport-2.cisco.com with ESMTP; 07 Feb 2005 19:06:11 -0500 X-BrightmailFiltered: true X-Brightmail-Tracker: AAAAAA== Received: from flask.cisco.com (IDENT:mirapoint@flask.cisco.com [161.44.122.62]) by rtp-core-2.cisco.com (8.12.10/8.12.6) with ESMTP id j18067hF001870; Mon, 7 Feb 2005 19:06:08 -0500 (EST) Received: from [192.168.2.168] (che-vpn-cluster-1-187.cisco.com [10.86.240.187]) by flask.cisco.com (MOS 3.4.6-GR) with ESMTP id AOX60776; Mon, 7 Feb 2005 19:06:07 -0500 (EST) In-Reply-To: <20050207103046.V70192@kummer.juniper.net> References: <626FC7C6A97381468FB872072AB5DDC805EE5B@XCH-SW-42.sw.nos.boeing.com> <20050207103046.V70192@kummer.juniper.net> Mime-Version: 1.0 (Apple Message framework v619.2) Content-Type: text/plain; charset=US-ASCII; format=flowed Message-Id: <724f49ce8f02c0fe54213a90046278a9@cisco.com> Content-Transfer-Encoding: 7bit From: "Thomas D. Nadeau" Subject: Re: [mpls] MPLS over L2TPv3 as WG item Date: Mon, 7 Feb 2005 19:06:01 -0500 To: Kireeti Kompella X-Mailer: Apple Mail (2.619.2) X-Spam-Score: 0.0 (/) X-Scan-Signature: 9466e0365fc95844abaf7c3f15a05c7d Content-Transfer-Encoding: 7bit Cc: mpls@ietf.org, "Drake, John E" 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: 97adf591118a232206bdb5a27b217034 Content-Transfer-Encoding: 7bit On Feb 7, 2005, at 1:36 PM, Kireeti Kompella wrote: > On Fri, 4 Feb 2005, Drake, John E wrote: > >> No compelling need for this > > I agree with John and Adrian ("But does it do any good?") > > This document would have the effect of confusing the market -- as Dave > said, yet another way of doing MPLS over IP. I'm not sure that could > be construed as 'doing good' -- I'll leave that to others to judge. I personally don't see why we should be predicting what the market will like. We produce solutions at the IETF; we are not a marketing organization last I checked. :P --Tom > > Kireeti. > ------- > > _______________________________________________ > 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 Tue Feb 8 05:35:32 2005 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 FAA23439; Tue, 8 Feb 2005 05:35:32 -0500 (EST) Received: from megatron.ietf.org ([132.151.6.71]) by ietf-mx.ietf.org with esmtp (Exim 4.33) id 1CyT24-0000Xy-14; Tue, 08 Feb 2005 05:55:49 -0500 Received: from localhost.localdomain ([127.0.0.1] helo=megatron.ietf.org) by megatron.ietf.org with esmtp (Exim 4.32) id 1CySgt-0003nb-1c; Tue, 08 Feb 2005 05:33:55 -0500 Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org) by megatron.ietf.org with esmtp (Exim 4.32) id 1CySdU-0002Pl-Jc for mpls@megatron.ietf.org; Tue, 08 Feb 2005 05:30:24 -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 FAA23123 for ; Tue, 8 Feb 2005 05:30:22 -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 1CySx0-0000RE-Mt for mpls@ietf.org; Tue, 08 Feb 2005 05:50:39 -0500 Received: from kummer.juniper.net (localhost [127.0.0.1]) by kummer.juniper.net (8.12.8p1/8.12.3) with ESMTP id j18ATfXg072856; Tue, 8 Feb 2005 02:29:41 -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 j18ATfrD072853; Tue, 8 Feb 2005 02:29:41 -0800 (PST) X-Authentication-Warning: kummer.juniper.net: kireeti owned process doing -bs Date: Tue, 8 Feb 2005 02:29:40 -0800 (PST) From: Kireeti Kompella To: "Thomas D. Nadeau" Subject: Re: [mpls] MPLS over L2TPv3 as WG item In-Reply-To: <724f49ce8f02c0fe54213a90046278a9@cisco.com> Message-ID: <20050208021317.L72828@kummer.juniper.net> References: <626FC7C6A97381468FB872072AB5DDC805EE5B@XCH-SW-42.sw.nos.boeing.com> <20050207103046.V70192@kummer.juniper.net> <724f49ce8f02c0fe54213a90046278a9@cisco.com> MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII X-Spam-Score: 0.0 (/) X-Scan-Signature: 8abaac9e10c826e8252866cbe6766464 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: 39bd8f8cbb76cae18b7e23f7cf6b2b9f Hi Tom, On Mon, 7 Feb 2005, Thomas D. Nadeau wrote: > > This document would have the effect of confusing the market -- as Dave > > said, yet another way of doing MPLS over IP. I'm not sure that could > > be construed as 'doing good' -- I'll leave that to others to judge. > > I personally don't see why we should be predicting > what the market will like. We produce solutions at > the IETF; we are not a marketing organization last I > checked. :P My comment was not a prediction of what the market will like. Nor does the fact that it uses the word 'market' make it marketing (it neither supports or is against a given proposal). It was simply a statement that the more ways there are of doing any particular function, the more difficult the decision among the options gets. If this additional choice offered a significant benefit, it might be worth the confusion it generates. But this benefit has yet to be clearly articulated. Such an articulation may be technical or -- you said it -- marketing. You might want to read http://www.newyorker.com/critics/books/?040301crbo_books . Then again, you'd probably accuse Schwarz of 'marketing' :-) 'Nuff said. Sorry, Per ... I've already used more cycles on this than I wanted to. Back to useful work :-) Kireeti. ------- _______________________________________________ mpls mailing list mpls@lists.ietf.org https://www1.ietf.org/mailman/listinfo/mpls From mpls-bounces@ietf.org Tue Feb 8 06:48:01 2005 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 GAA00278; Tue, 8 Feb 2005 06:48:01 -0500 (EST) Received: from megatron.ietf.org ([132.151.6.71]) by ietf-mx.ietf.org with esmtp (Exim 4.33) id 1CyUAE-0002Af-Er; Tue, 08 Feb 2005 07:08:18 -0500 Received: from localhost.localdomain ([127.0.0.1] helo=megatron.ietf.org) by megatron.ietf.org with esmtp (Exim 4.32) id 1CyTiW-00010v-D2; Tue, 08 Feb 2005 06:39:40 -0500 Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org) by megatron.ietf.org with esmtp (Exim 4.32) id 1CyTi4-0000uc-LL for mpls@megatron.ietf.org; Tue, 08 Feb 2005 06:39:12 -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 GAA29673 for ; Tue, 8 Feb 2005 06:39:10 -0500 (EST) Received: from sj-iport-3-in.cisco.com ([171.71.176.72] helo=sj-iport-3.cisco.com) by ietf-mx.ietf.org with esmtp (Exim 4.33) id 1CyU1e-00020W-CQ for mpls@ietf.org; Tue, 08 Feb 2005 06:59:27 -0500 Received: from sj-core-1.cisco.com (171.71.177.237) by sj-iport-3.cisco.com with ESMTP; 08 Feb 2005 04:50:09 +0000 X-BrightmailFiltered: true X-Brightmail-Tracker: AAAAAA== Received: from flask.cisco.com (IDENT:mirapoint@flask.cisco.com [161.44.122.62]) by sj-core-1.cisco.com (8.12.10/8.12.6) with ESMTP id j18BcbuC024207; Tue, 8 Feb 2005 03:38:38 -0800 (PST) Received: from [144.254.116.230] (dhcp-144-254-116-230.cisco.com [144.254.116.230]) by flask.cisco.com (MOS 3.4.6-GR) with ESMTP id AOX81421; Tue, 8 Feb 2005 06:38:36 -0500 (EST) In-Reply-To: <20050208021317.L72828@kummer.juniper.net> References: <626FC7C6A97381468FB872072AB5DDC805EE5B@XCH-SW-42.sw.nos.boeing.com> <20050207103046.V70192@kummer.juniper.net> <724f49ce8f02c0fe54213a90046278a9@cisco.com> <20050208021317.L72828@kummer.juniper.net> Mime-Version: 1.0 (Apple Message framework v619.2) Content-Type: text/plain; charset=US-ASCII; format=flowed Message-Id: <05154f5e34021bffbfda294785ef4d67@cisco.com> Content-Transfer-Encoding: 7bit From: "Thomas D. Nadeau" Subject: Re: [mpls] MPLS over L2TPv3 as WG item Date: Tue, 8 Feb 2005 06:38:41 -0500 To: Kireeti Kompella X-Mailer: Apple Mail (2.619.2) X-Spam-Score: 0.0 (/) X-Scan-Signature: 769a46790fb42fbb0b0cc700c82f7081 Content-Transfer-Encoding: 7bit Cc: mpls@ietf.org X-BeenThere: mpls@lists.ietf.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Multi-Protocol Label Switching WG List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Sender: mpls-bounces@ietf.org Errors-To: mpls-bounces@ietf.org X-Spam-Score: 0.0 (/) X-Scan-Signature: 538aad3a3c4f01d8b6a6477ca4248793 Content-Transfer-Encoding: 7bit On Feb 8, 2005, at 5:29 AM, Kireeti Kompella wrote: > Hi Tom, > > On Mon, 7 Feb 2005, Thomas D. Nadeau wrote: > >>> This document would have the effect of confusing the market -- as >>> Dave >>> said, yet another way of doing MPLS over IP. I'm not sure that could >>> be construed as 'doing good' -- I'll leave that to others to judge. >> >> I personally don't see why we should be predicting >> what the market will like. We produce solutions at >> the IETF; we are not a marketing organization last I >> checked. :P > > My comment was not a prediction of what the market will like. Nor > does the fact that it uses the word 'market' make it marketing (it > neither supports or is against a given proposal). It was simply a > statement that the more ways there are of doing any particular > function, the more difficult the decision among the options gets. If > this additional choice offered a significant benefit, it might be > worth the confusion it generates. But this benefit has yet to be > clearly articulated. Such an articulation may be technical or -- you > said it -- marketing. The IETF often produces multiple solutions in a certain space and lets the market sort things out; this case is no exception. So unless there are sound technical reasons for not moving this solution forward (which I have not heard/read), I don't see why we shouldn't adopt it as a WG document. --Tom > > You might want to read > http://www.newyorker.com/critics/books/?040301crbo_books . > Then again, you'd probably accuse Schwarz of 'marketing' :-) > > 'Nuff said. Sorry, Per ... I've already used more cycles on this than > I wanted to. Back to useful work :-) > > Kireeti. > ------- > _______________________________________________ mpls mailing list mpls@lists.ietf.org https://www1.ietf.org/mailman/listinfo/mpls From mpls-bounces@ietf.org Tue Feb 8 15:23:40 2005 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 PAA13189; Tue, 8 Feb 2005 15:23:40 -0500 (EST) Received: from megatron.ietf.org ([132.151.6.71]) by ietf-mx.ietf.org with esmtp (Exim 4.33) id 1CycDI-0005cX-1o; Tue, 08 Feb 2005 15:44:01 -0500 Received: from localhost.localdomain ([127.0.0.1] helo=megatron.ietf.org) by megatron.ietf.org with esmtp (Exim 4.32) id 1Cybjo-0003qM-Mc; Tue, 08 Feb 2005 15:13:32 -0500 Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org) by megatron.ietf.org with esmtp (Exim 4.32) id 1CybgW-0002US-8a for mpls@megatron.ietf.org; Tue, 08 Feb 2005 15:10:08 -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 PAA10737; Tue, 8 Feb 2005 15:10:06 -0500 (EST) Received: from kremlin.juniper.net ([207.17.137.120]) by ietf-mx.ietf.org with esmtp (Exim 4.33) id 1Cyc0A-00053Z-UO; Tue, 08 Feb 2005 15:30:27 -0500 Received: from unknown (HELO alpha.jnpr.net) (172.24.18.126) by kremlin.juniper.net with ESMTP; 08 Feb 2005 12:09:35 -0800 X-BrightmailFiltered: true X-Brightmail-Tracker: AAAAAA== X-IronPort-AV: i="3.88,187,1102320000"; d="scan'208"; a="227954984:sNHT20832600" Received: from electron.jnpr.net ([172.24.15.21]) by alpha.jnpr.net with Microsoft SMTPSVC(6.0.3790.211); Tue, 8 Feb 2005 12:09:35 -0800 X-MimeOLE: Produced By Microsoft Exchange V6.5.6944.0 Content-class: urn:content-classes:message MIME-Version: 1.0 Content-Type: text/plain; charset="US-ASCII" Content-Transfer-Encoding: quoted-printable Date: Tue, 8 Feb 2005 12:09:24 -0800 Message-ID: <27BCF2C7355655439636003CC56C152C031A509D@electron.jnpr.net> Thread-Topic: Establishment of a formal liaison relationship with IETF MPLS working group Thread-Index: AcUOGhTUadsda32VQu+JjozBImPmIQ== From: "J. Rao Cherukuri" To: "George Swallow" , "Loa Anderson" , "Ina Minei" X-OriginalArrivalTime: 08 Feb 2005 20:09:35.0479 (UTC) FILETIME=[1C304070:01C50E1A] X-Spam-Score: 0.0 (/) X-Scan-Signature: c1c65599517f9ac32519d043c37c5336 Content-Transfer-Encoding: quoted-printable Cc: mpls@ietf.org, statements@ietf.org Subject: [mpls] Establishment of a formal liaison relationship with IETF MPLS working group 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: 4d87d2aa806f79fed918a62e834505ca Content-Transfer-Encoding: quoted-printable Dear George, Loa and Ina: The MPLS and Frame Relay Alliance (MFA) met in San Francisco CA from 1-4 February 2005. We would like to thank the IETF MPLS working group for the=20 response to our recent communication. =20 We were very pleased to receive your communication indicating an interest in=20 establishing open communication with the MPLS & Frame Relay Alliance. The=20 MFA Technical Committee shares exactly the same view. Since both=20 organizations have indicated a desire to communicate, we would like to=20 pursue the IETF formal liaison process as described in:=20 http://www.ietf.org/internet-drafts/draft-iab-liaison-mgt-03.txt According to draft-iab-liaison-mgt-03.txt, "A liaison relationship is set up=20 when it is mutually agreeable and needed for some specific purpose, in the=20 view of the other organization, the IAB, and the IETF participants=20 conducting the work. There is no set process or form for this; the IETF=20 participants and the peer organization approach the IAB, and after=20 discussion come to an agreement to form the relationship." The MFA is creating MPLS implementation agreements based on protocols=20 developed by the IETF MPLS working group. The MFA can be a source of=20 requirements input for the MPLS and GMPLS protocols. The MFA understands=20 and supports the IETF processes. =20 Since there is interest from both sides to have an open communication that=20 would benefit both organizations, the MFA would appreciate the IETF MPLS working group taking the next step as suggested by the IETF document on the=20 management of liaison relations which is to approach the IAB with our mutual=20 interest. Cordially, Rao Cherukuri Chairman, MPLS and Frame Relay Alliance Technical Committee _______________________________________________ mpls mailing list mpls@lists.ietf.org https://www1.ietf.org/mailman/listinfo/mpls From mpls-bounces@ietf.org Tue Feb 8 16:35:27 2005 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 QAA27058; Tue, 8 Feb 2005 16:35:26 -0500 (EST) Received: from megatron.ietf.org ([132.151.6.71]) by ietf-mx.ietf.org with esmtp (Exim 4.33) id 1CydKm-0001VL-Sa; Tue, 08 Feb 2005 16:55:49 -0500 Received: from localhost.localdomain ([127.0.0.1] helo=megatron.ietf.org) by megatron.ietf.org with esmtp (Exim 4.32) id 1CycAw-0006FG-NX; Tue, 08 Feb 2005 15:41:34 -0500 Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org) by megatron.ietf.org with esmtp (Exim 4.32) id 1Cyc7V-0003vu-3D; Tue, 08 Feb 2005 15:38:01 -0500 Received: from CNRI.Reston.VA.US (localhost [127.0.0.1]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id PAA14971; Tue, 8 Feb 2005 15:37:59 -0500 (EST) Message-Id: <200502082037.PAA14971@ietf.org> Mime-Version: 1.0 Content-Type: Multipart/Mixed; Boundary="NextPart" To: i-d-announce@ietf.org From: Internet-Drafts@ietf.org Date: Tue, 08 Feb 2005 15:37:59 -0500 Cc: mpls@ietf.org Subject: [mpls] I-D ACTION:draft-ietf-mpls-nodeid-subobject-05.txt X-BeenThere: mpls@lists.ietf.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Multi-Protocol Label Switching WG List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Sender: mpls-bounces@ietf.org Errors-To: mpls-bounces@ietf.org X-Spam-Score: 0.4 (/) X-Scan-Signature: 944ecb6e61f753561f559a497458fb4f --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 : Definition of an RRO node-id subobject Author(s) : J. Vasseur, et al. Filename : draft-ietf-mpls-nodeid-subobject-05.txt Pages : 9 Date : 2005-2-8 In the context of MPLS TE Fast Reroute, the Merge Point (MP) address is required at the Point of Local Repair (PLR) in order to select a backup tunnel intersecting a fast reroutable Traffic Engineering LSP on a downstream LSR. However, existing protocol mechanisms are not sufficient to find an MP address in multi-areas or multi-domain routing networks. Hence, the current MPLS Fast Reroute mechanism cannot be used to protect inter-area or inter-AS TE LSPs from a failure of an ABR (Area Border Router) or ASBR (Autonomous System Border Router) respectively. Such functionality has been listed as a clear requirement in [INTER-AREA-TE-REQS] and [INTER-AS-TE-REQS]. This document specifies the use of existing RRO IPv4 and IPv6 subobjects (with a new flag defined) to define the node-id subobject in order to solve this issue. Note that the MPLS Fast reroute mechanism mentioned in this document refers to the "Facility backup" MPLS TE Fast Reroute method. A URL for this Internet-Draft is: http://www.ietf.org/internet-drafts/draft-ietf-mpls-nodeid-subobject-05.txt To remove yourself from the I-D Announcement list, send a message to i-d-announce-request@ietf.org with the word unsubscribe in the body of the message. You can also visit https://www1.ietf.org/mailman/listinfo/I-D-announce to change your subscription settings. Internet-Drafts are also available by anonymous FTP. Login with the username "anonymous" and a password of your e-mail address. After logging in, type "cd internet-drafts" and then "get draft-ietf-mpls-nodeid-subobject-05.txt". A list of Internet-Drafts directories can be found in http://www.ietf.org/shadow.html or ftp://ftp.ietf.org/ietf/1shadow-sites.txt Internet-Drafts can also be obtained by e-mail. Send a message to: mailserv@ietf.org. In the body type: "FILE /internet-drafts/draft-ietf-mpls-nodeid-subobject-05.txt". NOTE: The mail server at ietf.org can return the document in MIME-encoded form by using the "mpack" utility. To use this feature, insert the command "ENCODING mime" before the "FILE" command. To decode the response(s), you will need "munpack" or a MIME-compliant mail reader. Different MIME-compliant mail readers exhibit different behavior, especially when dealing with "multipart" MIME messages (i.e. documents which have been split up into multiple messages), so check your local documentation on how to manipulate these messages. Below is the data which will enable a MIME compliant mail reader implementation to automatically retrieve the ASCII version of the Internet-Draft. --NextPart Content-Type: Multipart/Alternative; Boundary="OtherAccess" --OtherAccess Content-Type: Message/External-body; access-type="mail-server"; server="mailserv@ietf.org" Content-Type: text/plain Content-ID: <2005-2-8160438.I-D@ietf.org> ENCODING mime FILE /internet-drafts/draft-ietf-mpls-nodeid-subobject-05.txt --OtherAccess Content-Type: Message/External-body; name="draft-ietf-mpls-nodeid-subobject-05.txt"; site="ftp.ietf.org"; access-type="anon-ftp"; directory="internet-drafts" Content-Type: text/plain Content-ID: <2005-2-8160438.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 Thu Feb 10 07:28:55 2005 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 HAA23353; Thu, 10 Feb 2005 07:28:55 -0500 (EST) Received: from megatron.ietf.org ([132.151.6.71]) by ietf-mx.ietf.org with esmtp (Exim 4.33) id 1CzDlI-000228-MJ; Thu, 10 Feb 2005 07:49:37 -0500 Received: from localhost.localdomain ([127.0.0.1] helo=megatron.ietf.org) by megatron.ietf.org with esmtp (Exim 4.32) id 1CzDId-0005rS-VA; Thu, 10 Feb 2005 07:19:59 -0500 Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org) by megatron.ietf.org with esmtp (Exim 4.32) id 1CzDEC-0004hX-Im for mpls@megatron.ietf.org; Thu, 10 Feb 2005 07:15:24 -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 HAA22235 for ; Thu, 10 Feb 2005 07:15:21 -0500 (EST) Received: from tama5.ecl.ntt.co.jp ([129.60.39.102]) by ietf-mx.ietf.org with esmtp (Exim 4.33) id 1CzDYC-0001il-O6 for mpls@ietf.org; Thu, 10 Feb 2005 07:36:05 -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 j1ACFJ7W025906 for ; Thu, 10 Feb 2005 21:15:19 +0900 (JST) Received: from vcs3.rdh.ecl.ntt.co.jp (localhost [127.0.0.1]) by vcs3.rdh.ecl.ntt.co.jp (8.12.11/8.12.11) with ESMTP id j1ACFJgZ015804 for ; Thu, 10 Feb 2005 21:15:19 +0900 (JST) Received: from mfs3.rdh.ecl.ntt.co.jp (mfs3.rdh.ecl.ntt.co.jp [129.60.39.112]) by vcs3.rdh.ecl.ntt.co.jp (8.12.11/8.12.11) with ESMTP id j1ACFIC9015799 for ; Thu, 10 Feb 2005 21:15:18 +0900 (JST) Received: from mfs3.rdh.ecl.ntt.co.jp (localhost [127.0.0.1]) by mfs3.rdh.ecl.ntt.co.jp (8.12.11/8.12.11) with ESMTP id j1ACFIca002302 for ; Thu, 10 Feb 2005 21:15:18 +0900 (JST) Received: from nttmail3.ecl.ntt.co.jp ([129.60.39.100]) by mfs3.rdh.ecl.ntt.co.jp (8.12.11/8.12.11) with ESMTP id j1ACFInj002297 for ; Thu, 10 Feb 2005 21:15:18 +0900 (JST) Received: from eclscan3.m.ecl.ntt.co.jp (eclscan3.m.ecl.ntt.co.jp [129.60.5.69]) by nttmail3.ecl.ntt.co.jp (8.12.11/8.12.11) with ESMTP id j1ACFH7J013621 for ; Thu, 10 Feb 2005 21:15:17 +0900 (JST) Received: from eclscan3.m.ecl.ntt.co.jp (localhost [127.0.0.1]) by eclscan3.m.ecl.ntt.co.jp (8.12.11/8.12.11) with ESMTP id j1ACFHQT010848 for ; Thu, 10 Feb 2005 21:15:17 +0900 (JST) Received: from imc.m.ecl.ntt.co.jp (imc0.m.ecl.ntt.co.jp [129.60.5.141]) by eclscan3.m.ecl.ntt.co.jp (8.12.11/8.12.11) with ESMTP id j1ACFHSB010843; Thu, 10 Feb 2005 21:15:17 +0900 (JST) Received: from win-yasukawa.lab.ntt.co.jp by imc.m.ecl.ntt.co.jp (8.9.3p2/3.7W) with ESMTP id VAA23427; Thu, 10 Feb 2005 21:15:16 +0900 (JST) Message-Id: <5.0.2.5.2.20050210203736.077ef4b0@imc.m.ecl.ntt.co.jp> X-Sender: sy003@imc.m.ecl.ntt.co.jp X-Mailer: QUALCOMM Windows Eudora Version 5.0.2-J Date: Thu, 10 Feb 2005 21:29:06 +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: b5d20af10c334b36874c0264b10f59f1 Subject: [mpls] Tree Re-merge in P2MP MPLS-TE 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: cf3becbbd6d1a45acbe2ffd4ab88bdc2 Hi, One of the remaining unresolved issues in draft-ietf-mpls-p2mp-sig-requirement is how to handle a "re-merge" of the P2MP LSP. A re-merge is defined as the receipt of more than one signaling message at one LSR for the same LSP where the messages are intended to establish the LSP to different (possibly overlapping) sets of egresses. The issues that arise concern both control plane state and data plane traffic. On the upstream side there are two possibilities. 1. The messages refer to the same upstream data plane interface. 2. The messages refer to different upstream data plane interfaces. On the downstream side there are also two distinct possibilities. a. There is no overlap of data flows. That is, each incoming signaling message results in outgoing signaling message(s) that do not refer to common data plane interfaces. b. There is some "re-merge" of data flows such that outgoing signaling messages caused by the separate incoming messages refer to the same outgoing data plane interface. The issues are clearly: - a desire to reduce unnecessary control plane state - a requirement not to duplicate traffic to any egress - a desire not to duplicate traffic on any link. The text in the current draft states: 4.11 Tree Remerge It is possible for a single transit LSR to receive multiple signaling messages for the same P2MP LSP but for different sets of destinations. These messages may be received from the same or different upstream nodes and may need to be passed on to the same or different downstream nodes. This situation may arise as the result of the signaling solution definition or implementation options within the signaling solution. Further, it may happen during make-before-break reoptimization (section 4.10), or as a result of signaling message fragmentation (section 4.5). It is even possible that it is necessary to construct distinct upstream branches in order to achieve the correct label choices in certain switching technologies managed by GMPLS (for example, photonic cross-connects where the selection of a particular lambda for the downstream branches is only available on different upstream switches). The solution MUST handle the case where multiple signaling messages for the same P2MP LSP are received at a single transit LSR with the end result of all receivers being added to the P2MP LSP. It seems to us that this final paragraph is too loose and propose to replace it as follows. The solution MUST support the case where of multiple signaling messages for the same P2MP LSP are received at a single transit LSR and refer to the same upstream interface. In this case the result of the protocol procedures SHOULD be a single data flow on the upstream interface. The solution SHOULD support the case where multiple signaling messages for the same P2MP LSP are received at a single transit LSR and refer to different upstream interfaces, and where each signaling message results in the use of different downstream interfaces. This case represents data flows that cross at the LSR but which do not merge. The solution MAY support the case where multiple signaling messages for the same P2MP LSP are received at a single transit LSR and refer to different upstream interfaces, and where the downstream interfaces are shared across the received signaling messages. This case represents the merging of data flows. A solution that supports this case MUST ensure that data is not replicated on the downstream interfaces. An alternative to supporting this last case is for the signaling protocol to indicate an error such that the merge may be resolved by the upstream LSRs. We would appreciate your input on this point. Regards, Seisho. _______________________________________________ mpls mailing list mpls@lists.ietf.org https://www1.ietf.org/mailman/listinfo/mpls From mpls-bounces@ietf.org Fri Feb 11 13:55:37 2005 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 NAA25793; Fri, 11 Feb 2005 13:55:37 -0500 (EST) Received: from megatron.ietf.org ([132.151.6.71]) by ietf-mx.ietf.org with esmtp (Exim 4.33) id 1CzgHK-0006kB-Q6; Fri, 11 Feb 2005 14:16:35 -0500 Received: from localhost.localdomain ([127.0.0.1] helo=megatron.ietf.org) by megatron.ietf.org with esmtp (Exim 4.32) id 1Czfof-000176-HG; Fri, 11 Feb 2005 13:46:57 -0500 Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org) by megatron.ietf.org with esmtp (Exim 4.32) id 1Czfgx-000734-C7; Fri, 11 Feb 2005 13:38:59 -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 NAA23890; Fri, 11 Feb 2005 13:38:56 -0500 (EST) Received: from kcmso1.att.com ([192.128.133.69] helo=kcmso1.proxy.att.com) by ietf-mx.ietf.org with esmtp (Exim 4.33) id 1Czg1A-0006Cv-1M; Fri, 11 Feb 2005 13:59:56 -0500 Received: from attrh5i.attrh.att.com ([135.38.62.12]) by kcmso1.proxy.att.com (AT&T IPNS/MSO-5.5) with ESMTP id j1BIcIH9025883; Fri, 11 Feb 2005 12:38:22 -0600 Received: from kcclust06evs1.ugd.att.com (135.38.164.88) by attrh5i.attrh.att.com (7.1.006) id 41EA9EF5005AF96E; Fri, 11 Feb 2005 13:38:21 -0500 X-MimeOLE: Produced By Microsoft Exchange V6.0.6603.0 content-class: urn:content-classes:message MIME-Version: 1.0 Content-Type: text/plain; charset="US-ASCII" Content-Transfer-Encoding: quoted-printable Subject: RE: [AVT] [mpls] Comments on draft-ash-avt-ecrtp-over-mpls-protocol-02.txt Date: Fri, 11 Feb 2005 12:38:21 -0600 Message-ID: <9473683187ADC049A855ED2DA739ABCA060C874E@KCCLUST06EVS1.ugd.att.com> Thread-Topic: [AVT] [mpls] Comments on draft-ash-avt-ecrtp-over-mpls-protocol-02.txt Thread-Index: AcUEiubgVGYXE8ktT1+oHQDMZEsiHgLFwakw From: "Ash, Gerald R \(Jerry\), ALABS" To: "Lars-Erik Jonsson \(LU/EAB\)" , "Magnus Westerlund" X-Spam-Score: 0.0 (/) X-Scan-Signature: 680445c3afe8c9e96925f2dfef141924 Content-Transfer-Encoding: quoted-printable Cc: rohc@ietf.org, IETF AVT WG , 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: 90fbdaf3c139ce803b358d56775b59ed Content-Transfer-Encoding: quoted-printable Lars-Erik, Magnus, Thank you for your comments on "Protocol Extensions for ECRTP over MPLS" http://ietf.org/internet-drafts/draft-ash-avt-ecrtp-over-mpls-protocol-0 2.txt. Please see responses below. Hopefully we will get MPLS and header compression SMEs to make comments and suggestions on the rather complex issues you have raised (e.g., signal the CIDs 'at layer 2', negotiate the HC parameters 'at layer 2'). Thanks, Jerry > I've now looked into the MPLS-HC solution draft as well as the > mail exchanges between Magnus and Jerry. The problems I see with=20 > the draft are very similar to those pointed out by Magnus. However, > in an attempt to avoid getting too influenced by Magnus comments > I will make my points purely based on my own reflections from the > draft, and then from that refer to the discussion between Magnus > and Jerry. >=20 > Overall document structure and purpose > -------------------------------------- > On a high level, I think this MPLS-HC document should be about > three things: > 1) Negotiation of use, i.e. setup signaling > 2) Encapsulation, i.e. how to send HC-packets over MPLS > 3) Operation, i.e. considerations for the actual compression=20 > scheme(s), e.g. how to implement the scheme(s) to be able to=20 > handle reordering >=20 > 1-2 are addressed in the draft, while 3) is not, although it is > essential as an ordinary implementation of the existing HC schemes > would e.g. not necessarily work well enough in case of reordering. I have no trouble with including discussion of #3 'operation'. =20 > I also strongly believe this MPLS-HC mapping solution should cover > the currently available HC schemes, IP-HC, CRTP, ECRTP, and ROHC. > I would not say we have to make it totally generic for *any* HC > scheme, as I do not think we can cover up for future solutions.=20 > RFC 3544 (i.e. RFC 2509bis), which provides 1) and 2) for IP-HC, > CRTP, and ECRTP, as well as RFC 3409, which do the same for ROHC, > could be used as a basis for this work. The similarities in how to > solve 1), 2), and 3) for existing HC schemes should be dominating > rather than the differences. Both Lars-Erik and Magnus are pushing for a solution to HC over MPLS that includes all existing HC schemes: IPHC (RFC 2507), CRTP (RFC 2508), ECRTP (RFC 3545), and ROHC (RFC 3095). Recall that the original AVT charter item was limited to ECRTP. Probably it is OK to generalize to CRTP, ECRTP, and ROHC, given the similarities in these protocols. However, I'm concerned about the possible morass of issues this may lead to regarding each of the schemes, especially wrt IPHC (RFC 2507), which addresses HC for TCP, etc. I wouldn't think there is a large demand for IPHC over MPLS. =20 > By the way, could we please avoid the terminology=20 > "control/data plane". This is common terminology, I don't know what is the issue with using this terminology? =20 > Context multiplexing within an LSP, why signaling? > --------------------------------------------------- > The second main concern I have is the same one as Magnus expressed, > about the multiplexing, which seems to require signaling that I > can not see the point of. As I know nothing about the details > of MPLS, my question from reading the draft was simply why there > would have to be any signaling for picking a CID value, existing > HC schemes assume the compressor does this without any signaling. > The draft just talks about "...to signal the SCIDs...", without > explaining the meaning of this. >=20 > I do not exactly understand the underlying MPLS problem that Magnus > talked about that might be the motivation for having to do CID tricks, > but I agree with his concerns about this approach, which seems to > require signaling for each new packet stream, and also contradicts > the way existing HC schemes handle CID assignment. In any case, the > draft should explain better the motivations behind solutions like > this. The issue is that MPLS labels may not be received at all at the header decompressor (HD), or, if received, do not uniquely identify the source of the compressed packets at the header compressor (HCO). Therefore a CID is used to uniquely identify the flow. In order to avoid duplication of CIDs at the HD, say from 2 HCs, HC-a and HC-b sending compressed packets to the HD, it is necessary to signal from HCO to HD to obtain unique CIDs allocated by the HD. It is not acceptable to have any chance of using the same CID for different flows occurring at the same time. > For the negotiation & encapsulation I would strongly recommend using > RFC 3544 and RFC 3409 as a basis, and clearly highlight potential=20 > deviations from the solutions used in these RFC's, that would help > to get more constructive involvement from the HC folks in this work. Regarding 'negotiating HC scheme parameters', it is probably valid that we should address how the HC scheme parameters are negotiated across an MPLS LSP. However, the current RFCs don't specify how this can be done across a (IP, GRE, or MPLS) tunnel. For example, RFC 3544 http://ietf.org/rfc/rfc3544.txt?number=3D3544 'IPHC over PPP', makes no mention of negotiating parameters across tunnels, it is oriented toward negotiating over a single PPP link (per the title of the RFC). RFC 3544 uses RFC 1332 http://ietf.org/rfc/rfc1332.txt?number=3D1332 'PPP IP Control Protocol (IPCP)' to signal/negotiate the HC parameters. For example, as specified in Section 2.3 of RFC 3544, the following ECRTP parameter negotiation object is sent from header compressor (HCO) to header decompressor (HD) over a PPP link using the IPCP specified in RFC 1332: 2.3. Enhanced RTP-Compression Suboption To use the enhanced RTP header compression defined in [RFC3545], a new sub-option 2 is added. Sub-option 2 is negotiated instead of, not in addition to, sub-option 1. Description Enable use of Protocol Identifiers COMPRESSED_RTP and CONTEXT_STATE as specified in [RFC2508]. In addition, enable use of [RFC3545] compliant compression including the use of Protocol Identifier COMPRESSED_UDP with additional flags and use of the C flag with the FULL_HEADER Protocol Identifier to indicate use of HDRCKSUM with COMPRESSED_RTP and COMPRESSED_UDP packets. 0 1 0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ | Type | Length | +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ Type 2 Length 2 For the HC over MPLS application, the above object would have to be sent between HCO and HD over an MPLS LSP. Perhaps this needs to be identified as one of the packet types (see below). In regard to the operation of HC schemes over tunnels, RFC 2507 (IPHC) http://ietf.org/rfc/rfc2507.txt?number=3D2507 does refer to operation = over IP tunnels in Section 4.1. RFC 3095 (ROHC) http://ietf.org/rfc/rfc3095.txt?number=3D3095 refers to operation over = GRE tunnels in Section 5.8.4.4. It would be useful to know how these HC schemes can already be made to work over IP and GRE tunnels, that is not explained in RFC 2507 or RFC 3095. That information would help to explain how to 'negotiate HC scheme parameters' over MPLS tunnels. =20 > On the CID handling question, I also noticed the text about how to > free up CID. I am not sure what the purpose of that is, but this also > represents a deviation from how existing HC schemes are defined. > Looking at packets not belonging to the flow (e.g. SIP messages) > also seems like a not very desirable approach, in my mind. There are two issues of concern on the CID handing question: =20 A. how to avoid duplication of CIDs at the HD for different flows. If the HCO assigns the CIDs rather than the HD (as currently proposed in the I-D, through RSVP-TE signaling), there is possible duplication of CIDs at the HD for different flows. B. how to free up CIDs at the HCO when a flow has ended. These issues are *not* addressed in *any* of the HC RFCs: IPHC (RFC 2507), CRTP (RFC 2508), ECRTP (RFC 3545), and ROHC (RFC 3095) are all silent on how CIDs are selected, kept unique, and freed up. So it is unclear how to 'extend' existing HC schemes where the HCO selects the CID when we don't have any documentation on what these existing schemes are. However, in looking at RFC 3550 (RTP) http://ietf.org/rfc/rfc3550.txt?number=3D3550, it does discuss the issue of assigning and freeing up the SSRC (synchronization source) ID, which is kind of analogous to CID in the HC schemes. An SSRC needs to be assigned to an RTP flow by the RTP source on initiation of the flow, and freed up when the flow ends. Perhaps CRTP and ECRTP implementations use the SSRC assignments to determine the CID assignments (only a guess)? It would be good to know how the SSRCs are uniquely assigned and removed, and how that might be applied to CID assignment and removal. =20 Appendix A.6 of RFC 3550 gives an algorithm (and C code) to generate random SSRC values, although of course there is non-zero probability of having duplicate SSRC values at the receiver. Sections 8 and 8.2 of RFC 3550 discuss the issues of probability of SSRC collision (duplication) and collision resolution, although the words on collision resolution in Section 8.2 are a bit vague: If a receiver discovers that two other sources are colliding, it MAY keep the packets from one and discard the packets from the other when this can be detected by different source transport addresses or CNAMEs. The two sources are expected to resolve the collision so that the situation doesn't last.=20 So how to chose CIDs at the HCO to completely avoid duplication at the HD is one issue. In any case, I feel it is essential to have *zero* chance of duplicating CIDs in the HD, since 2 VoIP conversations might get mixed together if CIDs are duplicated!? That's why we opted to use the RSVP-TE signaling approach to have the CIDs uniquely assigned by the HD. Freeing up CIDs to avoid running out of CIDs is the other issue. Section 6.2.1 of RFC 3550 (RTP) discusses freeing up SSRCs after an RTCP 'BYE' packet is received, which ends the RTP session. Section 6.3.5 discusses how to free up SSRCs after a time-out period. This might work for RTP flows, but how to do it for IPHC? =20 Perhaps the issue of freeing up CIDs isn't quite as difficult as avoiding duplication at the HD, but the issue of not running out of CIDs at the HCO is a concern (maybe 16 bits is sufficient to always avoid that?). > What creates a feedback channel? > -------------------------------- > Is the LSP per definition bidirectional, or are LSP's always set up > as pairs, one in each direction? If we talk about multiple LSP's, > there must be an exact 1-1 mapping, or there must be a way to create > that binding between them. We propose the following additional text in the I-D to explain the creation of the feedback MPLS LSP channel: "In Figure 1, we assume an example VoIP flow set up from R1/HC --> R2 --> R3 --> R4/HD, where R1/HC is the ingress router where header compression (HC) is performed, and R4/HD is the egress router where header decompression (HD) is done, and in the reverse direction. Each router functions as an LSR and supports RSVP-TE signaling of LSPs. Now we describe the following MPLS functions: 1. Associating the A-->B RTP flow with the B-->A RTP flow 2. Associating the A-->B LSP with the B-->A LSP 3. Signal the SCID for both the A-->B and B-->A RTP flows. A summary of the ECRTP flow setup is as follows: 1. R1/HC sends an RSVP-TE PATH message to R4/HD, which includes a SCID_Request object with a 2-byte ECRTP-Flow-ID. The RSVP-TE PATH message causes the intermediate LSRs R2 and R3 as well as R4 to install state, insuring that the R1 --> R4 LSP will be set up by the RESV message, which follows the prescribed path in the reverse direction. For an IP network in general, the reverse path might not be same as the forward path, but in the case of MPLS-TE, the state installed by the RSVP PATH message determines the path of the LSP to be set up by the RSVP RESV message. 2. R4/HD assigns a unique 2-byte SCID to the call and sends an RSVP-TE RESV message to R1/HC that includes a Header_Compression_Reply object with the ECRTP-Flow-ID and the assigned SCID. This RSVP RESV message traverses the path R4 --> R3 --> R2 --> R1, creating the R1 --> R4 LSP that follows that path. R1/HD uses this LSP to send CONTEXT_STATE packets to R4/HC and R1/HC uses this LSP to send compressed packets to R4/HD. 3. R4/HC sends an RSVP-TE PATH message to R1/HD, which includes a SCID_Request object with a 2-byte ECRTP-Flow-ID. The RSVP-TE PATH message causes the intermediate LSRs R3 and R2 as well as R1 to install state, insuring that the R4 --> R1 LSP will be set up by the RESV message, which follows the prescribed path in the reverse direction. =20 4. R1/HD assigns a unique 2-byte SCID to the call and sends an RSVP-TE RESV message to R1/HC that includes a Header_Compression_Reply object with the ECRTP-Flow-ID and the assigned SCID. This RSVP RESV message traverses the path R1 --> R2 --> R3 --> R4, creating the R4 --> R1 LSP that follows that path. R4/HD uses this LSP to send CONTEXT_STATE packets to R1/HC and R4/HC uses this LSP to send compressed packets to R1/HC. 5. R1/HC sets the SCID in compressed packets and FULL_HEADER packets. 6. Compressed packets and header compression control packets (FULL_HEADER and CONTEXT_STATE packets) are routed on a separate LSP, set up by RSVP-TE, from non-compressed packets; for example, FULL-HEADER packets are routed on the same R1/HC --> R4/HD LSP as the R1/HC to R4/HD compressed packets for the ECRTP flow; CONTEXT-STATE packets are routed on the same R4/HD --> R1/HC LSP as the R4/HD to R1/HC compressed packets for the ECRTP flow. 7. Compressed packets, FULL_HEADER packets, and CONTEXT_STATE packets are routed with MPLS labels. 8. R4/HD uses the incoming MPLS label and the SCID to locate the proper decompression context. 9. If needed to resync, R4/HD sends a CONTEXT_STATE packet to R1/HC with SCID set; R1/HC resends FULL_HEADER packet with SCID set to R4/HD, etc. 10. R4/HD frees up the SCID when the ECRTP flow disconnects (e.g., as indicated by RTP BYE message and RSVP-TE/PATH-TEAR messages), or by refreshing the PATH state." > ECRTP packet type identification > -------------------------------- > Inconsistency, first paragraph of 2.2 talks about a 4-bit packet type, > while the second paragraph says a one-octet PT ID is used. In the > figure, I wonder what the first octet of zeros is, not really=20 > explained. "Defined by PPP Data Link Layer Protocol" means? You are correct about the inconsistency, which needs to be corrected. Furthermore, perhaps the 2 byte packet type identifier we now specify in Section 2.2 of http://ietf.org/internet-drafts/draft-ash-avt-ecrtp-over-mpls-protocol-0 2.txt could be reduced to 1 byte, as follows: 0 1 2 3 4 5 6 7 8 +-+-+-+-+-+-+-+-+ |0 0 0 0|Pkt Typ| +-+-+-+-+-+-+-+-+ where: SCID_Packet_Type designation: 0000 (first nibble) "Packet Type" encoding: 0: Reserved 1: FULL_HEADER 2: COMPRESSED_TCP 3: COMPRESSED_TCP_NODELTA 4: COMPRESSED_NON_TCP 5: COMPRESSED_RTP_8 6: COMPRESSED_RTP_16 7: COMPRESSED_UDP_8 8: COMPRESSED_UDP_16 9: CONTEXT_STATE 10: ROHC 11 - 15: RESERVED =20 We need to add an ROHC packet type, as pointed out in Section 2.6 of RFC 3409 http://ietf.org/rfc/rfc3409.txt?number=3D3409. It is also pointed out that ROHC further identifies the packet type within its header. I don't feel we need to reserve 246 additional packet types with a 1-byte field, which seems like overkill. Also, this was an issue/concern raised by Loa Anderson when the HC over MPLS I-Ds were reviewed on the MPLS list a few months ago. Please let me know what you think of this proposal. > HC object formats > ----------------- > This section was very confusing to me. First, the text talks about > intermediates that do not understand HC and could drop the object. > My question is, should not the solution be transparent to=20 > intermediates, > i.e. compression should be possible between ingress and egress without > any knowledge in the notes in between? Why should it at all concern > intermediates? This is some standard discussion of how MPLS objects are treated at intermediates, however, some additional explanation/clarification can be added as you suggest. =20 > Further, I have a hard time commenting on the content as the fields > in these objects are not described. There should be explanations > after the figures. Agreed. =20 > Operations > ---------- > For the operations part, the draft currently says nothing, while we > know there are at least concerns related to reordering. The ROHC over > reordering draft can be a useful source for information in that area, > as well as the ECRTP evaluation I made the list aware of=20 > earlier today. > http://www.ietf.org/internet-drafts/draft-ietf-rohc-over-reordering-01.t xt > http://epubl.luth.se/1402-1617/2004/286/LTU-EX-04286-SE.pdf I agree that relevant 'operations' guidance should be included. > Summary > ------- > I thus suggest that the overall purpose of this document (to be adopted > as a WG document) should be to create a HC mapping for MPLS, covering > the HC schemes we currently have, similar to RFC 3544 and 3409. It > should address negotiation (setup), encapsulation, and potential issues > with operation of each HC scheme.=20 >=20 > I'll do my best to support this work from an HC perspective. OK, good. Please see the above comments, questions, and requests for input/clarification regarding your comments and suggestions. Your input and other MPLS/header compression SME input to specifically answer these questions would be very much appreciated. Thanks, Jerry >=20 > Cheers, > /L-E >=20 >=20 > > -----Original Message----- > > From: avt-bounces@ietf.org [mailto:avt-bounces@ietf.org] > > Sent: den 22 december 2004 22:30 > > To: IETF AVT WG; rohc@ietf.org; mpls@ietf.org > > Subject: [AVT] [mpls] Comments > > ondraft-ash-avt-ecrtp-over-mpls-protocol-01.txt > >=20 > > Hi, > >=20 > > Sorry for the crossposting, however this is something that I think needs > > to be generally discussed between all 3 WGs. To me it looks like the > > proposed solution for VoIP header compression across an MPLS network > > contains a problematic demultiplexing mechanism. I don't think people=20 > > has realized the issues with the proposed mechanism due to lack of=20 > > communication between the header compression and MPLS folks.=20 > > > > If it is my lack of knowledge please educate me, and the others. I=20 > > would request that people providing input in this discussion is > > overly explaining as education seems necessary. > >=20 > > The current draft is available at > > http://ietf.org/internet-drafts/draft-ash-avt-ecrtp-over-mpls-protocol-0 2.txt: > >=20 > > The header compression mechanisms such as CRTP and ROHC to my=20 > > understanding assumes that they have a lower link layer that > > carries their compressed messages between compressor and=20 > > decompressor. This is due to that they are intended to be > > used with only a single link between the compressor and=20 > > decompressor. In the case of CRTP, it also assumes that the=20 > > link-layer can also provide the with identification of the=20 > > packet types, while ROHC makes this identification internally. > >=20 > > The MPLS network uses one or more labels in the transport between=20 > > ingress and egress from the MPLS network. Due to the possible=20 > > relabeling in the middle of the network, it can't be generally > > assumed that packets arriving with the same label comes from the > > same ingress point. This makes the label not sufficient to=20 > > identify the ingress for the egress, thus not making labels equal > > to a link. > >=20 > > The proposed solution has thought of the above MPLS problem=20 > > and proposes that one uses the setup signaling to allow the=20 > > decompressor point to select which parts of its context > > identifier (SCID) space that belongs to different ingress points > > that arrives over the same label. However my understanding is > > that this definitely not without problems for the header > > compression mechanisms. I would like the header compression guy=20 > > to clarify what problems that would arise from such a solution. One=20 > > thing I definitely can see would be an issue, the proposed change > > would prevent MPLS HC to use any standard implementation of the HC=20 > > mechanism used. > >=20 > > I would also like to point out that the Header Compression=20 > > mechanism needs a return path from the decompressor mechanism. > > However the draft does not seem to discuss this issue at all.=20 > > Or is a MPLS label path automatically reversible? > >=20 > > It would be desirable if the MPLS people could consider if=20 > > there exist other ways of providing for the standard > > assumption on link layers that header compression has? For > > these assumption please see chapter 2 of RFC 2508, section > > 4.1 of RFC 3095, and RFC 3409. > >=20 > > For example, what would be the effects of requiring unique labels=20 > > between ingress and egress and for the reverse path? > >=20 > > What effects would it have to put the multiplexing point in the > > layer two extension? > >=20 > > I would also like to see the draft be more header compression=20 > > agnostic as has been agreed on in the requirements phase. There > > is no problem with using ECRTP as an example how one realize the > > solution, however the necessary hooks and signaling must be in > > place for any header compression mechanism. > >=20 > > So lets get the discussion going and hope that something good > > results. > >=20 > > Cheers > >=20 > > Magnus Westerlund > > AVT Chair _______________________________________________ mpls mailing list mpls@lists.ietf.org https://www1.ietf.org/mailman/listinfo/mpls From mpls-bounces@ietf.org Fri Feb 11 17:01:38 2005 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 RAA29499; Fri, 11 Feb 2005 17:01:38 -0500 (EST) Received: from megatron.ietf.org ([132.151.6.71]) by ietf-mx.ietf.org with esmtp (Exim 4.33) id 1CzjBP-0000Is-5d; Fri, 11 Feb 2005 17:22:39 -0500 Received: from localhost.localdomain ([127.0.0.1] helo=megatron.ietf.org) by megatron.ietf.org with esmtp (Exim 4.32) id 1CziNE-0000js-0K; Fri, 11 Feb 2005 16:30:48 -0500 Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org) by megatron.ietf.org with esmtp (Exim 4.32) id 1Czhhu-00024H-8v for mpls@megatron.ietf.org; Fri, 11 Feb 2005 15:48:06 -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 PAA08911 for ; Fri, 11 Feb 2005 15:48:04 -0500 (EST) Received: from [132.151.6.18] (helo=ticket.ietf.org) by ietf-mx.ietf.org with esmtp (Exim 4.33) id 1Czi2C-0001sG-Bp for mpls@ietf.org; Fri, 11 Feb 2005 16:09:04 -0500 Received: from apache by ticket.ietf.org with local (Exim 4.33) id 1CzhtL-00075E-Du for mpls@ietf.org; Fri, 11 Feb 2005 15:59:55 -0500 From: "Webmaster via RT" In-Reply-To: Message-ID: Precedence: bulk X-RT-Loop-Prevention: Inquiry RT-Ticket: Inquiry #37281 Managed-by: RT 3.2.1 (http://www.bestpractical.com/rt/) RT-Originator: mpls@ietf.org To: mpls@ietf.org MIME-Version: 1.0 Content-Type: text/plain; charset="utf-8" X-RT-Original-Encoding: utf-8 Date: Fri, 11 Feb 2005 15:59:55 -0500 X-Spam-Score: 0.0 (/) X-Scan-Signature: 7655788c23eb79e336f5f8ba8bce7906 Subject: [mpls] [Inquiry #37281] AutoReply: Delivery by mail X-BeenThere: mpls@lists.ietf.org X-Mailman-Version: 2.1.5 Reply-To: webmaster@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: 0bc60ec82efc80c84b8d02f4b0e4de22 Greetings, This message has been automatically generated in response to the creation of a ticket regarding: "Delivery by mail", a summary of which appears below. There is no need to reply to this message right now. Your ticket has been assigned an ID of [Inquiry #37281] in the queue: Webmaster. Please include the string: [Inquiry #37281] in the subject line of all future correspondence about this issue. To do so, you may reply to this message. Thank you, webmaster@ietf.org ------------------------------------------------------------------------- This transaction appears to have no content _______________________________________________ mpls mailing list mpls@lists.ietf.org https://www1.ietf.org/mailman/listinfo/mpls From mpls-bounces@ietf.org Sat Feb 12 12:55:11 2005 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 MAA17969; Sat, 12 Feb 2005 12:55:11 -0500 (EST) Received: from megatron.ietf.org ([132.151.6.71]) by ietf-mx.ietf.org with esmtp (Exim 4.33) id 1D01od-0007gb-4B; Sat, 12 Feb 2005 13:16:23 -0500 Received: from localhost.localdomain ([127.0.0.1] helo=megatron.ietf.org) by megatron.ietf.org with esmtp (Exim 4.32) id 1D01SH-0005Oc-Un; Sat, 12 Feb 2005 12:53:17 -0500 Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org) by megatron.ietf.org with esmtp (Exim 4.32) id 1D01Oy-0004a4-58 for mpls@megatron.ietf.org; Sat, 12 Feb 2005 12:49:52 -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 MAA17810 for ; Sat, 12 Feb 2005 12:49:49 -0500 (EST) Received: from [132.151.6.18] (helo=ticket.ietf.org) by ietf-mx.ietf.org with esmtp (Exim 4.33) id 1D01jR-0007bl-G9 for mpls@ietf.org; Sat, 12 Feb 2005 13:11:01 -0500 Received: from apache by ticket.ietf.org with local (Exim 4.33) id 1D01aa-0001b6-Bz for mpls@ietf.org; Sat, 12 Feb 2005 13:01:52 -0500 From: "Webmaster via RT" In-Reply-To: Message-ID: Precedence: bulk X-RT-Loop-Prevention: Inquiry RT-Ticket: Inquiry #37422 Managed-by: RT 3.2.1 (http://www.bestpractical.com/rt/) RT-Originator: mpls@ietf.org To: mpls@ietf.org MIME-Version: 1.0 Content-Type: text/plain; charset="utf-8" X-RT-Original-Encoding: utf-8 Date: Sat, 12 Feb 2005 13:01:52 -0500 X-Spam-Score: 0.0 (/) X-Scan-Signature: 7655788c23eb79e336f5f8ba8bce7906 Subject: [mpls] [Inquiry #37422] AutoReply: You are made active X-BeenThere: mpls@lists.ietf.org X-Mailman-Version: 2.1.5 Reply-To: webmaster@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: 0bc60ec82efc80c84b8d02f4b0e4de22 Greetings, This message has been automatically generated in response to the creation of a ticket regarding: "You are made active", a summary of which appears below. There is no need to reply to this message right now. Your ticket has been assigned an ID of [Inquiry #37422] in the queue: Webmaster. Please include the string: [Inquiry #37422] in the subject line of all future correspondence about this issue. To do so, you may reply to this message. Thank you, webmaster@ietf.org ------------------------------------------------------------------------- This transaction appears to have no content _______________________________________________ mpls mailing list mpls@lists.ietf.org https://www1.ietf.org/mailman/listinfo/mpls From mpls-bounces@ietf.org Sun Feb 13 00:52:36 2005 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 AAA03700; Sun, 13 Feb 2005 00:52:36 -0500 (EST) Received: from megatron.ietf.org ([132.151.6.71]) by ietf-mx.ietf.org with esmtp (Exim 4.33) id 1D0D10-0003up-Kl; Sun, 13 Feb 2005 01:13:54 -0500 Received: from localhost.localdomain ([127.0.0.1] helo=megatron.ietf.org) by megatron.ietf.org with esmtp (Exim 4.32) id 1D0CeF-0000B5-Cp; Sun, 13 Feb 2005 00:50:23 -0500 Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org) by megatron.ietf.org with esmtp (Exim 4.32) id 1D0CdO-0008Tc-49 for mpls@megatron.ietf.org; Sun, 13 Feb 2005 00:49:30 -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 AAA03519 for ; Sun, 13 Feb 2005 00:49:27 -0500 (EST) Received: from [132.151.6.18] (helo=ticket.ietf.org) by ietf-mx.ietf.org with esmtp (Exim 4.33) id 1D0Cxx-0003rT-Qz for mpls@ietf.org; Sun, 13 Feb 2005 01:10:45 -0500 Received: from apache by ticket.ietf.org with local (Exim 4.33) id 1D0Cp6-00038q-Br for mpls@ietf.org; Sun, 13 Feb 2005 01:01:36 -0500 Subject: [Inquiry #37422] RE: [mpls] [Inquiry #37422] AutoReply: You are made active From: "yhkwon via RT" In-Reply-To: Message-ID: Precedence: bulk X-RT-Loop-Prevention: Inquiry RT-Ticket: Inquiry #37422 Managed-by: RT 3.2.1 (http://www.bestpractical.com/rt/) RT-Originator: yhkwon@icu.ac.kr To: mpls@ietf.org MIME-Version: 1.0 Content-Type: text/plain; charset="utf-8" X-RT-Original-Encoding: utf-8 Date: Sun, 13 Feb 2005 01:01:36 -0500 X-Spam-Score: 0.0 (/) X-Scan-Signature: a7d6aff76b15f3f56fcb94490e1052e4 X-BeenThere: mpls@lists.ietf.org X-Mailman-Version: 2.1.5 Reply-To: webmaster@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: c1c65599517f9ac32519d043c37c5336 -----Original Message----- From: mpls-bounces@lists.ietf.org [mailto:mpls-bounces@lists.ietf.org] On Behalf Of Webmaster via RT Sent: Sunday, February 13, 2005 2:50 AM To: mpls@ietf.org Subject: [mpls] [Inquiry #37422] AutoReply: You are made active Greetings, This message has been automatically generated in response to the creation of a ticket regarding: "You are made active", a summary of which appears below. There is no need to reply to this message right now. Your ticket has been assigned an ID of [Inquiry #37422] in the queue: Webmaster. Please include the string: [Inquiry #37422] in the subject line of all future correspondence about this issue. To do so, you may reply to this message. Thank you, webmaster@ietf.org ------------------------------------------------------------------------- This transaction appears to have no content _______________________________________________ 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 Sun Feb 13 08:57:05 2005 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 IAA24974; Sun, 13 Feb 2005 08:57:05 -0500 (EST) Received: from megatron.ietf.org ([132.151.6.71]) by ietf-mx.ietf.org with esmtp (Exim 4.33) id 1D0KZp-0000UU-Rr; Sun, 13 Feb 2005 09:18:26 -0500 Received: from localhost.localdomain ([127.0.0.1] helo=megatron.ietf.org) by megatron.ietf.org with esmtp (Exim 4.32) id 1D0KCz-0004W8-4I; Sun, 13 Feb 2005 08:54:45 -0500 Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org) by megatron.ietf.org with esmtp (Exim 4.32) id 1Cz77b-0006C2-Nb; Thu, 10 Feb 2005 00:44: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 AAA05564; Thu, 10 Feb 2005 00:44:07 -0500 (EST) Received: from [69.72.240.66] (helo=fox.whbdns.com) by ietf-mx.ietf.org with esmtp (Exim 4.33) id 1Cz7RX-0002El-Fc; Thu, 10 Feb 2005 01:04:48 -0500 Received: from wbar5.dal1-4-12-170-137.dsl-verizon.net ([4.12.170.137] helo=cow) by fox.whbdns.com with esmtpa (Exim 4.43) id 1Cz7Ek-0002p5-Ja; Thu, 10 Feb 2005 00:51:36 -0500 From: "Dawn " To: Date: Wed, 9 Feb 2005 23:43:22 -0600 Message-ID: <002801c50f33$7004aaf0$f922fea9@cow> MIME-Version: 1.0 X-Priority: 3 (Normal) X-MSMail-Priority: Normal X-Mailer: Microsoft Outlook, Build 10.0.6626 X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2900.2180 Importance: Normal X-Antivirus-Scanner: Clean mail though you should still use an Antivirus X-AntiAbuse: This header was added to track abuse, please include it with any abuse report X-AntiAbuse: Primary Hostname - fox.whbdns.com X-AntiAbuse: Original Domain - ietf.org X-AntiAbuse: Originator/Caller UID/GID - [0 0] / [47 12] X-AntiAbuse: Sender Address Domain - icst.org X-Spam-Score: 3.2 (+++) X-Scan-Signature: 2822ab89c35e6a93e4f72d8e025158b9 X-Mailman-Approved-At: Sun, 13 Feb 2005 08:54:43 -0500 Subject: [mpls] Call for Papers - BroadNets 2005 (Broadband Optical Networking Symposium) 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="===============0572564729==" Sender: mpls-bounces@ietf.org Errors-To: mpls-bounces@ietf.org X-Spam-Score: 3.2 (+++) X-Scan-Signature: e2b52ed63f0b1853d90cc5ec6749519c This is a multi-part message in MIME format. --===============0572564729== Content-Type: multipart/alternative; boundary="----=_NextPart_000_0029_01C50F01.256A3AF0" This is a multi-part message in MIME format. ------=_NextPart_000_0029_01C50F01.256A3AF0 Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: quoted-printable We apologize if you receive this announcement multiple times =20 ----------------------------------------------------------------------- CALL FOR PAPERS =20 Second Annual International Conference on Broadband Networks (BROADNETS 2005) Broadband Optical Networking Symposium October 3 - 7, 2005 Boston, Massachusetts, USA http://www.broadnets.org =20 Submission Deadline Extended: February 25, 2005 ----------------------------------------------------------------------- =20 SCOPE ----- =20 BROADNETS 2005 is an international conference focusing on broadband networking and covers the entire gamut of next generation networks with high bandwidth available for both wireless and wireline networks. =20 The conference will consist of the following three symposia: =20 ** Broadband Optical Networking Symposium: covers WDM technologies, = Ethernet and MPLS integration into the optical layer, Next-Generation SONET/SDH, = as well as SAN extensions over DWDM/SONET/SDH. =20 ** Broadband Wireless Networking Symposium: covers mobility, routing for multihop, multimedia QoS and traffic management, cross-layer = optimization, MAC and emerging physical layer technologies (UWB, MIMO) for high-speed wireless networking. =20 ** Broadband Applications/Services Symposium: covers middleware and = service architectures for broadband applications, pervasive computing and = ubiquitous communications, and universal broadband access for information services. =20 BROADNETS 2005 will thus offer a unique forum for researchers from = academia, government and industry to share ideas and disseminate new=20 results in these important areas. =20 This Call for Papers describes the details for the Broadband Optical Networking Symposium ONLY. (Refer to the www.broadnets.org website for the details of Broadband Wireless Symposium and Broadband Applications/Services Symposium.) We are soliciting full papers in all research, development, and deployment areas on broadband optical = networking. Topics of interest include, but not limited to, the following: =20 - Wavelength-routed WDM networks - Integration of Ethernet and RPR into the optical layer - IP and MPLS over DWDM: integration and interworking - Next-generation SONET/SDH and MSPP - SAN over SONET/SDH and DWDM - Network control and management, GMPLS - Survivability in the data, TDM or optical layers - Optical packet switching and burst switching - High-speed switch and router architectures - Optical multicasting - Standards for multi-service networks - Long-haul optical transport networks - Metropolitan and regional optical networks - Access optical networks, PONs - Optical networking for video-on-demand - Trial implementations and test-beds - Multi-layer network design and optimization - Grid computing over optical networks - Optical technologies: switching, transmission and multiplexing =20 Conference proceedings will be published by IEEE Computer Society. =20 A set of selected papers from the symposium will be published in a = special issue of Elsevier Optical Switching and Networking Journal. =20 IMPORTANT DATES --------------- =20 Submission Deadline (Extended): February 25, 2005 Acceptance Notification: May 15, 2005 Final Manuscript Due: June 1, 2005 =20 PAPER SUBMISSION INSTRUCTIONS ----------------------------- =20 Authors are invited to submit full papers of up to 10 pages in IEEE conference proceedings format. Papers should be submitted in PDF format to the respective symposium through the EDAS system at http://edas.info/Conference.cgi. =20 =20 CONFERENCE ORGANIZING COMMITTEE ------------------------------- =20 General Chair: Dr. Arun Somani, Iowa State University, arun@iastate.edu =20 General Vice Chair: Dr. Thomas Hou, Virginia Tech, thou@vt.edu =20 Technical Program Chairs - Optical Networking Symposium Dr. David Griffith, NIST, david.griffith@nist.gov Dr. Srini Ramasubramanian, University of Arizona, srini@ece.arizona.edu =20 Technical Program Chair- Wireless Networking Symposium: Dr. Sherman Shen, Univ. of Waterloo, xshen@bbcr.uwaterloo.ca =20 Technical Program Chairs - Services and Applications Symposium Dr. Malathi Veeraraghavan, Univ. of Virginia, mv@cs.virginia.edu Dr. Admela Jukan, Georgia Tech, admela.jukan@ece.gatech.edu =20 Workshops Chairs: Dr. Wendi Heinzelman, University of Rochester, = wheinzel@ece.rochester.edu Dr. Byrav Ramamurthy, University of Nebraska-Lincoln, byrav@cse.unl.edu Dr. Behcet Sarikaya, University of Northern British Columbia, sarikaya@unbc.ca =20 Tutorials Chair: Dr. Steven Low, CalTech., slow@caltech.edu =20 Panels Chairs: Dr. Surendar Chandra, Univ. of Notre Dame, surendar@cse.nd.edu Dr. Rudra Dutta, NCSU, dutta@csc.ncsu.edu =20 Publicity Chairs: Dr. Bhaskar Krishnamachari, USC, bkrishna@usc.edu Dr. Takeo Hamada, Fujitsu Labs of America, thamada@fla.fujitsu.com =20 Website/Information Systems Chair: Dr. Shiwen Mao, Virginia Tech, smao@vt.edu =20 Local Arrangements Chairs: Dr. Aura Ganz, Univ. of Massachusetts, Amherst, ganz@ecs.umass.edu Dr. Ling Li, CIENA, linlisu@hotmail.com =20 Publications Chairs: Dr. Ahmed Kamal, Iowa State University, kamal@iastate.edu Dr. Hui Zang, Sprint Adv. Tech. Labs, hzang@sprintlabs.com =20 Exhibits and Sponsorships Chair: Dr. Sai Shankar N, Philips Research USA, sai.shankar@philips.com =20 Finance Chair: Karen Decker, ICST, karen@icst.org =20 Steering Committee Co-Chairs: Dr. Imrich Chlamtac, UT Dallas, chlamtac@utdallas.edu Dr. Krishna Sivalingam, Univ. of Maryland, Baltimore County, krishna@umbc.edu =20 -------------------------------------------------------------------------= - =20 =20 =20 =20 =20 ------=_NextPart_000_0029_01C50F01.256A3AF0 Content-Type: text/html; charset="us-ascii" Content-Transfer-Encoding: quoted-printable

We = apologize if you receive this announcement multiple times

 

--------------------------= ---------------------------------------------

CALL = FOR PAPERS

 

Second Annual International Conference on Broadband Networks

(BROADNETS 2005)

Broadband Optical Networking Symposium

October 3 - 7, 2005

Boston, Massachusetts, USA

http://www.broadnets.org

 

Submission Deadline Extended: February 25, = 2005

--------------------------= ---------------------------------------------

 

SCOPE

-----

 

BROADNETS 2005 is an international conference focusing on broadband networking and = covers the entire gamut of next generation networks

with = high bandwidth available for both wireless and wireline = networks.

 

The = conference will consist of the following three symposia:

 

** Broadband Optical = Networking Symposium: covers WDM technologies, Ethernet and MPLS integration into = the optical layer, Next-Generation SONET/SDH, as well as SAN extensions over DWDM/SONET/SDH.

 

** Broadband Wireless = Networking Symposium: covers mobility, routing for multihop, multimedia QoS and = traffic management, cross-layer optimization, MAC and emerging physical layer technologies (UWB, MIMO) for high-speed wireless = networking.

 

** Broadband = Applications/Services Symposium: covers middleware and service architectures for broadband applications, pervasive computing and ubiquitous communications, and = universal broadband access for information services.

 

BROADNETS 2005 will thus offer a unique forum for researchers from academia, government = and industry to share ideas and disseminate new

results in these important areas.

 

This = Call for Papers describes the details for the Broadband Optical Networking = Symposium ONLY. (Refer to the www.broadnets.org website

for = the details of Broadband Wireless Symposium and Broadband Applications/Services Symposium.)  We are soliciting full papers in all

research, development, and deployment areas on broadband optical networking. = Topics of interest include, but not limited to, the following:

 

- = Wavelength-routed WDM networks

- = Integration of Ethernet and RPR into the optical layer

- IP = and MPLS over DWDM: integration and interworking

- Next-generation SONET/SDH and MSPP

- = SAN over SONET/SDH and DWDM

- = Network control and management, GMPLS

- = Survivability in the data, TDM or optical layers

- = Optical packet switching and burst switching

- = High-speed switch and router architectures

- = Optical multicasting

- = Standards for multi-service networks

- = Long-haul optical transport networks

- = Metropolitan and regional optical networks

- = Access optical networks, PONs

- = Optical networking for video-on-demand

- = Trial implementations and test-beds

- = Multi-layer network design and optimization

- = Grid computing over optical networks

- = Optical technologies: switching, transmission and multiplexing

 

Conference proceedings will be published by IEEE Computer = Society.

 

A = set of selected papers from the symposium will be published in a special issue = of Elsevier Optical Switching and Networking Journal.

 

IMPORTANT = DATES

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

 

Submission Deadline (Extended):     February 25, 2005

Acceptance Notification:        = May 15, = 2005

Final Manuscript = Due:           = June 1, = 2005

 

PAPER SUBMISSION INSTRUCTIONS

--------------------------= ---

 

Authors are invited to submit full papers of up to 10 pages in IEEE conference = proceedings format.  Papers should be submitted in PDF

format to the respective symposium through the EDAS system at = http://edas.info/Conference.cgi.

 

 

CONFERENCE ORGANIZING COMMITTEE

--------------------------= -----

 

General = Chair:

Dr. = Arun Somani, Iowa State University, arun@iastate.edu

 

General Vice Chair:

Dr. = Thomas Hou, Virginia Tech, thou@vt.edu

 

Technical Program Chairs - Optical Networking Symposium

Dr. = David Griffith, NIST, david.griffith@nist.gov

Dr. = Srini Ramasubramanian, University of Arizona, srini@ece.arizona.edu

 

Technical Program Chair- Wireless Networking Symposium:

Dr. = Sherman Shen, Univ. of Waterloo, = xshen@bbcr.uwaterloo.ca

 

Technical Program Chairs - Services and Applications Symposium

Dr. = Malathi Veeraraghavan, Univ. of Virginia, mv@cs.virginia.edu

Dr. = Admela Jukan, Georgia Tech, admela.jukan@ece.gatech.edu

 

Workshops Chairs:

Dr. = Wendi Heinzelman, University of = Rochester, wheinzel@ece.rochester.edu

Dr. = Byrav Ramamurthy, University of = Nebraska-Lincoln, byrav@cse.unl.edu

Dr. = Behcet Sarikaya, University of Northern British Columbia,

sarikaya@unbc.ca

 

Tutorials Chair:

Dr. = Steven Low, CalTech., slow@caltech.edu

 

Panels = Chairs:

Dr. = Surendar Chandra, Univ. of Notre Dame, surendar@cse.nd.edu

Dr. = Rudra Dutta, NCSU, dutta@csc.ncsu.edu

 

Publicity Chairs:

Dr. = Bhaskar Krishnamachari, USC, bkrishna@usc.edu

Dr. = Takeo Hamada, Fujitsu Labs of America, = thamada@fla.fujitsu.com

 

Website/Information Systems Chair:

Dr. = Shiwen Mao, Virginia Tech, smao@vt.edu

 

Local Arrangements Chairs:

Dr. = Aura Ganz, Univ. of Massachusetts, Amherst, ganz@ecs.umass.edu

Dr. = Ling Li, CIENA, linlisu@hotmail.com

 

Publications Chairs:

Dr. = Ahmed Kamal, Iowa State University, kamal@iastate.edu

Dr. = Hui Zang, Sprint Adv. Tech. Labs, hzang@sprintlabs.com

 

Exhibits and Sponsorships Chair:

Dr. = Sai Shankar N, Philips Research USA, sai.shankar@philips.com

 

Finance = Chair:

Karen Decker, ICST, karen@icst.org

 

Steering Committee Co-Chairs:

Dr. = Imrich Chlamtac, UT Dallas, chlamtac@utdallas.edu

Dr. = Krishna Sivalingam, Univ. of Maryland, Baltimore County,

krishna@umbc.edu

 

--------------------------= ------------------------------------------------

 

 

 

 

 

------=_NextPart_000_0029_01C50F01.256A3AF0-- --===============0572564729== 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 --===============0572564729==-- From mpls-bounces@ietf.org Sun Feb 13 13:25:03 2005 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 NAA13403; Sun, 13 Feb 2005 13:25:03 -0500 (EST) Received: from megatron.ietf.org ([132.151.6.71]) by ietf-mx.ietf.org with esmtp (Exim 4.33) id 1D0OlI-0005Fa-6q; Sun, 13 Feb 2005 13:46:28 -0500 Received: from localhost.localdomain ([127.0.0.1] helo=megatron.ietf.org) by megatron.ietf.org with esmtp (Exim 4.32) id 1D0OJp-0000jL-Jf; Sun, 13 Feb 2005 13:18:05 -0500 Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org) by megatron.ietf.org with esmtp (Exim 4.32) id 1D0OIG-0000Yr-7m for mpls@megatron.ietf.org; Sun, 13 Feb 2005 13:16: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 NAA12820 for ; Sun, 13 Feb 2005 13:16:25 -0500 (EST) Received: from rtp-iport-2.cisco.com ([64.102.122.149]) by ietf-mx.ietf.org with esmtp (Exim 4.33) id 1D0Ocv-00055B-Fy for mpls@ietf.org; Sun, 13 Feb 2005 13:37:50 -0500 Received: from rtp-core-1.cisco.com (64.102.124.12) by rtp-iport-2.cisco.com with ESMTP; 13 Feb 2005 13:15:56 -0500 X-BrightmailFiltered: true X-Brightmail-Tracker: AAAAAA== Received: from flask.cisco.com (IDENT:mirapoint@flask.cisco.com [161.44.122.62]) by rtp-core-1.cisco.com (8.12.10/8.12.6) with ESMTP id j1DIFs1j006925; Sun, 13 Feb 2005 13:15:54 -0500 (EST) Received: from swallow-mac.cisco.com (che-vpn-cluster-2-223.cisco.com [10.86.242.223]) by flask.cisco.com (MOS 3.4.6-GR) with ESMTP id APB41449; Sun, 13 Feb 2005 13:15:50 -0500 (EST) Received: by swallow-mac.cisco.com (Postfix, from userid 501) id 10773211E7D; Sun, 13 Feb 2005 13:16:48 -0500 (EST) Received: from cisco.com (localhost [127.0.0.1]) by swallow-mac.cisco.com (Postfix) with ESMTP id CD73C211E74; Sun, 13 Feb 2005 13:16:48 -0500 (EST) To: mpls@ietf.org From: George Swallow X-Mailer: MH-E 7.4.3; nmh 1.1; GNU Emacs 21.2.1 Date: Sun, 13 Feb 2005 13:16:47 -0500 Message-Id: <20050213181648.10773211E7D@swallow-mac.cisco.com> X-Spam-Score: 0.0 (/) X-Scan-Signature: cf4fa59384e76e63313391b70cd0dd25 Subject: [mpls] Last Call on BCP on ECMP 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: 7d33c50f3756db14428398e2bdedd581 This begins a two week last call on Avoiding Equal Cost Multipath Treatment in MPLS Networks The last call ends Feb 27 24:00 UTC. ...George ======================================================================== George Swallow Cisco Systems (978) 936-1398 1414 Massachusetts Avenue Boxborough, MA 01719 _______________________________________________ mpls mailing list mpls@lists.ietf.org https://www1.ietf.org/mailman/listinfo/mpls From mpls-bounces@ietf.org Sun Feb 13 17:21:05 2005 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 RAA00266; Sun, 13 Feb 2005 17:21:05 -0500 (EST) Received: from megatron.ietf.org ([132.151.6.71]) by ietf-mx.ietf.org with esmtp (Exim 4.33) id 1D0SRj-000192-Pm; Sun, 13 Feb 2005 17:42:32 -0500 Received: from localhost.localdomain ([127.0.0.1] helo=megatron.ietf.org) by megatron.ietf.org with esmtp (Exim 4.32) id 1D0S4F-0006eI-L9; Sun, 13 Feb 2005 17:18:15 -0500 Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org) by megatron.ietf.org with esmtp (Exim 4.32) id 1D0S3T-0006Zd-N7 for mpls@megatron.ietf.org; Sun, 13 Feb 2005 17:17:27 -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 RAA00091 for ; Sun, 13 Feb 2005 17:17:25 -0500 (EST) Received: from pop-a065c10.pas.sa.earthlink.net ([207.217.121.184]) by ietf-mx.ietf.org with esmtp (Exim 4.33) id 1D0SOB-00015s-S2 for mpls@ietf.org; Sun, 13 Feb 2005 17:38:52 -0500 Received: from h-68-164-82-176.snvacaid.dynamic.covad.net ([68.164.82.176] helo=earthlink.net) by pop-a065c10.pas.sa.earthlink.net with esmtp (Exim 3.33 #1) id 1D0S1M-0005Zn-00; Sun, 13 Feb 2005 14:15:16 -0800 Message-ID: <420FD283.4AA186FF@earthlink.net> Date: Sun, 13 Feb 2005 14:19:47 -0800 From: Erblichs X-Sender: "Erblichs" <@smtp.earthlink.net> (Unverified) X-Mailer: Mozilla 4.72 [en]C-gatewaynet (Win98; I) X-Accept-Language: en MIME-Version: 1.0 To: George Swallow Subject: Re: [mpls] Last Call on BCP on ECMP References: <20050213181648.10773211E7D@swallow-mac.cisco.com> Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit X-Spam-Score: 0.0 (/) X-Scan-Signature: 00e94c813bef7832af255170dca19e36 Content-Transfer-Encoding: 7bit Cc: mpls@ietf.org X-BeenThere: mpls@lists.ietf.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Multi-Protocol Label Switching WG List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Sender: mpls-bounces@ietf.org Errors-To: mpls-bounces@ietf.org X-Spam-Score: 0.0 (/) X-Scan-Signature: d185fa790257f526fedfd5d01ed9c976 Content-Transfer-Encoding: 7bit Deorge Swallow, Sorry, I have a few minor NITs.. The long and short possible changes are suggested within.. All are contained within Current ECMP Practices. 1) Where we are in a IP environment, it is the re-ordering of individual flows where the segments in a TCP/IP flows can and do force false fast retransmits when multiple duplicate acks are recieved. This is due to the fact that one or more segments were lost or followed a different path that had a longer latency. Mis-ordering presumes that out-of-order segments can not be corrected at the destination addresses. This is not the case in a normal TCP/IP environment. Thus a simple change vs the longer one here, is to specify the "mis-ordering of flow between" to re-ordering of individual flows. 2) ECMP can only occur when multiple paths exist, thus I would suggest "splitting aggregated flows" to splitting aggregated flows where multiple paths exist. 3) Due to security purposes, some administrators are using intermediate systems that either aggregate or modify source addresses. This effectively hides the original source addresses and allows the intermediate systems to filter incoming non-solicited data flows to the original sources. Thus, as a FYI. I would possibly suggest ADDING something like. One should also be aware that some intermediate systems are intercepting flows between a source and destination and then modifing source addresses for security purposes. These modifications may alter the effectiveness of of removing ECMP routing behaviour. Of course, on the return to the modified source address, if the return flow is not modified, the flow is then re-directed back to the original source. Mitchell Erblich George Swallow wrote: > > This begins a two week last call on > > Avoiding Equal Cost Multipath Treatment in MPLS Networks > > > > The last call ends Feb 27 24:00 UTC. > > ...George > > ======================================================================== > George Swallow Cisco Systems (978) 936-1398 > 1414 Massachusetts Avenue > Boxborough, MA 01719 > > _______________________________________________ > mpls mailing list > mpls@lists.ietf.org > https://www1.ietf.org/mailman/listinfo/mpls _______________________________________________ mpls mailing list mpls@lists.ietf.org https://www1.ietf.org/mailman/listinfo/mpls From mpls-bounces@ietf.org Sun Feb 13 20:13:40 2005 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 UAA12467; Sun, 13 Feb 2005 20:13:40 -0500 (EST) Received: from megatron.ietf.org ([132.151.6.71]) by ietf-mx.ietf.org with esmtp (Exim 4.33) id 1D0V8l-0004AX-Gm; Sun, 13 Feb 2005 20:35:07 -0500 Received: from localhost.localdomain ([127.0.0.1] helo=megatron.ietf.org) by megatron.ietf.org with esmtp (Exim 4.32) id 1D0UlV-0002bY-Ko; Sun, 13 Feb 2005 20:11:05 -0500 Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org) by megatron.ietf.org with esmtp (Exim 4.32) id 1D0Ukv-0002YW-H3 for mpls@megatron.ietf.org; Sun, 13 Feb 2005 20:10: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 UAA12212 for ; Sun, 13 Feb 2005 20:10:24 -0500 (EST) Received: from gateway.avici.com ([208.246.215.5] helo=mailhost.avici.com) by ietf-mx.ietf.org with esmtp (Exim 4.33) id 1D0V5d-00046e-Bz for mpls@ietf.org; Sun, 13 Feb 2005 20:31:53 -0500 Received: from aatlas-lt.avici.com (b2-pc141.avici.com [10.2.100.141]) by mailhost.avici.com (8.12.8/8.12.8) with ESMTP id j1E19c7l012512; Sun, 13 Feb 2005 20:09:38 -0500 Message-Id: <5.1.0.14.2.20050213200040.01ececd0@pop.avici.com> X-Sender: aatlas@pop.avici.com X-Mailer: QUALCOMM Windows Eudora Version 5.1 Date: Sun, 13 Feb 2005 20:07:55 -0500 To: George Swallow From: Alia Atlas Subject: Re: [mpls] Last Call on BCP on ECMP In-Reply-To: <20050213181648.10773211E7D@swallow-mac.cisco.com> Mime-Version: 1.0 Content-Type: text/plain; charset="us-ascii"; format=flowed X-Avici-MailScanner-Information: Please contact the ISP for more information X-Spam-Score: 0.0 (/) X-Scan-Signature: 4adaf050708fb13be3316a9eee889caa 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: 8b431ad66d60be2d47c7bfeb879db82c The draft doesn't discuss at all the case where packets may be distributed to different paths based upon the MPLS label stack. This can occur for some equipment when either the packet is not identified as IPv4 or IPv6 or when the equipment cannot examine the header underneath the MPLS label stack, presumably due to its depth. This doesn't cause concerns for the PWE3 cases, but it was a definite issue when we were discussing LSP ping and other OAM issues. For instance, this was part of the concern for adding an OAM label into the label stack. If this is really to be a BCP describing how ECMP and MPLS interact, then I'd really like to see a very short section describing the possibility that packets may be load-balanced based on the label stack as well. At the time of the OAM label discussion, it was suggested that future implementations shouldn't include the reserved labels in any processing of the label stack done for load balancing. Perhaps we don't want to capture that here - the idea seemed a bit sensitive at the time - though I'd be in favor of it. Alia At 01:16 PM 2/13/2005, George Swallow wrote: >This begins a two week last call on > > Avoiding Equal Cost Multipath Treatment in MPLS Networks > > > > The last call ends Feb 27 24:00 UTC. > >...George > >======================================================================== >George Swallow Cisco Systems (978) 936-1398 > 1414 Massachusetts Avenue > Boxborough, MA 01719 > > > >_______________________________________________ >mpls mailing list >mpls@lists.ietf.org >https://www1.ietf.org/mailman/listinfo/mpls _______________________________________________ mpls mailing list mpls@lists.ietf.org https://www1.ietf.org/mailman/listinfo/mpls From mpls-bounces@ietf.org Mon Feb 14 05:27:21 2005 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 FAA12035; Mon, 14 Feb 2005 05:27:20 -0500 (EST) Received: from megatron.ietf.org ([132.151.6.71]) by ietf-mx.ietf.org with esmtp (Exim 4.33) id 1D0dmg-00064c-9J; Mon, 14 Feb 2005 05:48:54 -0500 Received: from localhost.localdomain ([127.0.0.1] helo=megatron.ietf.org) by megatron.ietf.org with esmtp (Exim 4.32) id 1D0dPV-0002dw-4H; Mon, 14 Feb 2005 05:24:57 -0500 Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org) by megatron.ietf.org with esmtp (Exim 4.32) id 1D0dO3-0002W4-Hn for mpls@megatron.ietf.org; Mon, 14 Feb 2005 05:23: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 FAA11746 for ; Mon, 14 Feb 2005 05:23:24 -0500 (EST) Received: from smtp.dataconnection.com ([192.91.191.4]) by ietf-mx.ietf.org with esmtp (Exim 4.33) id 1D0dis-0005zG-4j for mpls@ietf.org; Mon, 14 Feb 2005 05:44:58 -0500 Content-class: urn:content-classes:message MIME-Version: 1.0 Content-Type: multipart/mixed; boundary="----_=_NextPart_001_01C5127F.1A2D7360" X-MimeOLE: Produced By Microsoft Exchange V6.5.7226.0 Date: Mon, 14 Feb 2005 10:22:35 -0000 Message-ID: <53F74F5A7B94D511841C00B0D0AB16F8057D8BE2@baker.datcon.co.uk> X-MS-Has-Attach: yes Thread-Topic: I-D ACTION:draft-davey-mpls-rsvp-ipv6-unnum-00.txt Thread-Index: AcUPvUuDg2ecBZlQTgeUE2DINsytpACuwCcA From: "Alan Davey" To: X-Spam-Score: 0.0 (/) X-Scan-Signature: dbb8771284c7a36189745aa720dc20ab Subject: [mpls] FW: I-D ACTION:draft-davey-mpls-rsvp-ipv6-unnum-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.0 (/) X-Scan-Signature: 200d029292fbb60d25b263122ced50fc This is a multi-part message in MIME format. ------_=_NextPart_001_01C5127F.1A2D7360 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: quoted-printable Hi We have submitted the following draft for extensions to RSVP-TE for IPv6 = networks. All comments are welcome. Thanks Alan ------------------------------------ Alan Davey Data Connection Ltd Tel: +44 20 8366 1177 =20 Fax: +44 20 8363 1039 Email: Alan.Davey@dataconnection.com =20 Web: http://www.dataconnection.com=20 -----Original Message----- From: i-d-announce-bounces@ietf.org [mailto:Internet-Drafts@ietf.org] Sent: 10 February 2005 20:50 To: i-d-announce@ietf.org Subject: I-D ACTION:draft-davey-mpls-rsvp-ipv6-unnum-00.txt A New Internet-Draft is available from the on-line Internet-Drafts = directories. Title : Signalling Unnumbered Links in Resource ReSerVation Protocol=20 - Traffic Engineering (RSVP-TE) in an IPv6 Network Author(s) : A. Davey, N. Neate Filename : draft-davey-mpls-rsvp-ipv6-unnum-00.txt Pages : 7 Date : 2005-2-10 =09 Currently, RSVP-TE signalling over unnumbered links identifies=20 routers using 32-bit Router IDs [RFC3477]. Traffic engineering=20 extensions to IGP protocols for use in IPv6 networks use 128-bit IPv6 = addresses to identify routers [OSPFv3-TE], [ISIS-TE]. This document=20 specifies extensions for RSVP-TE signalling over unnumbered links to=20 use 128-bit Router IDs in an IPv6 network. A URL for this Internet-Draft is: http://www.ietf.org/internet-drafts/draft-davey-mpls-rsvp-ipv6-unnum-00.t= xt To remove yourself from the I-D Announcement list, send a message to=20 i-d-announce-request@ietf.org with the word unsubscribe in the body of = the message. =20 You can also visit https://www1.ietf.org/mailman/listinfo/I-D-announce=20 to change your subscription settings. Internet-Drafts are also available by anonymous FTP. Login with the = username "anonymous" and a password of your e-mail address. After logging in, type "cd internet-drafts" and then "get draft-davey-mpls-rsvp-ipv6-unnum-00.txt". A list of Internet-Drafts directories can be found in http://www.ietf.org/shadow.html=20 or ftp://ftp.ietf.org/ietf/1shadow-sites.txt Internet-Drafts can also be obtained by e-mail. Send a message to: mailserv@ietf.org. In the body type: "FILE /internet-drafts/draft-davey-mpls-rsvp-ipv6-unnum-00.txt". =09 NOTE: The mail server at ietf.org can return the document in MIME-encoded form by using the "mpack" utility. To use this feature, insert the command "ENCODING mime" before the "FILE" command. To decode the response(s), you will need "munpack" or a MIME-compliant mail reader. Different MIME-compliant mail readers exhibit different behavior, especially when dealing with "multipart" MIME messages (i.e. documents which have been split up into multiple messages), so check your local documentation on how to manipulate these messages. =09 =09 Below is the data which will enable a MIME compliant mail reader implementation to automatically retrieve the ASCII version of the Internet-Draft. ------_=_NextPart_001_01C5127F.1A2D7360 Content-Type: application/octet-stream; name="ATT71507.TXT" Content-Description: ATT71507.TXT Content-Disposition: attachment; filename="ATT71507.TXT" Content-Transfer-Encoding: base64 Q29udGVudC1UeXBlOiBNZXNzYWdlL0V4dGVybmFsLWJvZHk7IGFjY2Vzcy10eXBlPSJtYWlsLXNl cnZlciI7DQoJc2VydmVyPSJtYWlsc2VydkBpZXRmLm9yZyINCg0KQ29udGVudC1UeXBlOiB0ZXh0 L3BsYWluDQpDb250ZW50LUlEOiA8MjAwNS0yLTEwMTU1ODM5LkktREBpZXRmLm9yZz4NCg0KRU5D T0RJTkcgbWltZQ0KRklMRSAvaW50ZXJuZXQtZHJhZnRzL2RyYWZ0LWRhdmV5LW1wbHMtcnN2cC1p cHY2LXVubnVtLTAwLnR4dA0K ------_=_NextPart_001_01C5127F.1A2D7360 Content-Type: application/octet-stream; name="draft-davey-mpls-rsvp-ipv6-unnum-00.URL" Content-Description: draft-davey-mpls-rsvp-ipv6-unnum-00.URL Content-Disposition: attachment; filename="draft-davey-mpls-rsvp-ipv6-unnum-00.URL" Content-Transfer-Encoding: base64 W0ludGVybmV0U2hvcnRjdXRdDQpVUkw9ZnRwOi8vZnRwLmlldGYub3JnL2ludGVybmV0LWRyYWZ0 cy9kcmFmdC1kYXZleS1tcGxzLXJzdnAtaXB2Ni11bm51bS0wMC50eHQNCg== ------_=_NextPart_001_01C5127F.1A2D7360 Content-Type: text/plain; name="ATT71508.txt" Content-Description: ATT71508.txt Content-Disposition: attachment; filename="ATT71508.txt" Content-Transfer-Encoding: base64 X19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX18NCkktRC1Bbm5v dW5jZSBtYWlsaW5nIGxpc3QNCkktRC1Bbm5vdW5jZUBpZXRmLm9yZw0KaHR0cHM6Ly93d3cxLmll dGYub3JnL21haWxtYW4vbGlzdGluZm8vaS1kLWFubm91bmNlDQo= ------_=_NextPart_001_01C5127F.1A2D7360 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 ------_=_NextPart_001_01C5127F.1A2D7360-- From mpls-bounces@ietf.org Tue Feb 15 21:47:33 2005 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 VAA20294; Tue, 15 Feb 2005 21:47:33 -0500 (EST) Received: from megatron.ietf.org ([132.151.6.71]) by ietf-mx.ietf.org with esmtp (Exim 4.33) id 1D1FZ8-00035i-DG; Tue, 15 Feb 2005 22:09:27 -0500 Received: from localhost.localdomain ([127.0.0.1] helo=megatron.ietf.org) by megatron.ietf.org with esmtp (Exim 4.32) id 1D1F6A-0006Ij-QZ; Tue, 15 Feb 2005 21:39:30 -0500 Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org) by megatron.ietf.org with esmtp (Exim 4.32) id 1D1EtC-0001Us-JQ for mpls@megatron.ietf.org; Tue, 15 Feb 2005 21:26:06 -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 VAA16586 for ; Tue, 15 Feb 2005 21:26:04 -0500 (EST) Received: from rtp-iport-1.cisco.com ([64.102.122.148]) by ietf-mx.ietf.org with esmtp (Exim 4.33) id 1D1FEJ-0001wz-NY for mpls@ietf.org; Tue, 15 Feb 2005 21:47:58 -0500 Received: from rtp-core-2.cisco.com (64.102.124.13) by rtp-iport-1.cisco.com with ESMTP; 15 Feb 2005 21:37:58 -0500 X-BrightmailFiltered: true X-Brightmail-Tracker: AAAAAA== X-IronPort-AV: i="3.90,87,1107752400"; d="scan'208"; a="37135487:sNHT20760430" Received: from zaliwxp (che-vpn-cluster-2-40.cisco.com [10.86.242.40]) by rtp-core-2.cisco.com (8.12.10/8.12.6) with ESMTP id j1G2PThF019354; Tue, 15 Feb 2005 21:25:30 -0500 (EST) Message-Id: <200502160225.j1G2PThF019354@rtp-core-2.cisco.com> From: "Zafar Ali" To: "'George Swallow'" , , "'Loa Andersson'" Subject: RE: [mpls] Time to set the MPLS Agenda Date: Tue, 15 Feb 2005 21:25:28 -0500 MIME-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit X-Mailer: Microsoft Office Outlook, Build 11.0.5510 In-Reply-To: <20050202000815.BE66C1FC349@swallow-mac.cisco.com> Thread-Index: AcUIvgFi0afsRHtqQ8SjXi7kErGkLALECYVg X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2800.1441 X-Spam-Score: 0.0 (/) X-Scan-Signature: a7d6aff76b15f3f56fcb94490e1052e4 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: c1c65599517f9ac32519d043c37c5336 Content-Transfer-Encoding: 7bit Dear George/ Loa, We'd like a brief slot for draft-zamfir-explicit-resource-control-bundle-04.txt (just submitted). 10 minutes is plenty (5 minutes if you're squeezed). We need to: - update on the status of the draft - get agreement from the WG to accept it as a WG document Thanks Regards... Zafar > -----Original Message----- > From: mpls-bounces@lists.ietf.org > [mailto:mpls-bounces@lists.ietf.org] On Behalf Of George Swallow > Sent: Tuesday, February 01, 2005 7:08 PM > To: mpls@ietf.org > Subject: [mpls] Time to set the MPLS Agenda > > Please forward your agenda requests (including an estimate of > time) to Loa and me. > > Thanks, > > ...George > > ============================================================== > ========== > George Swallow Cisco Systems > (978) 936-1398 > 1414 Massachusetts Avenue > Boxborough, MA 01719 > > > > _______________________________________________ > mpls mailing list > mpls@lists.ietf.org > https://www1.ietf.org/mailman/listinfo/mpls > _______________________________________________ mpls mailing list mpls@lists.ietf.org https://www1.ietf.org/mailman/listinfo/mpls From mpls-bounces@ietf.org Wed Feb 16 14:54:54 2005 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 OAA11595; Wed, 16 Feb 2005 14:54:54 -0500 (EST) Received: from megatron.ietf.org ([132.151.6.71]) by ietf-mx.ietf.org with esmtp (Exim 4.33) id 1D1VbV-0007J4-4T; Wed, 16 Feb 2005 15:16:58 -0500 Received: from localhost.localdomain ([127.0.0.1] helo=megatron.ietf.org) by megatron.ietf.org with esmtp (Exim 4.32) id 1D1Trg-0005kS-4T; Wed, 16 Feb 2005 13:25:32 -0500 Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org) by megatron.ietf.org with esmtp (Exim 4.32) id 1D1SXv-0006WL-Gl for mpls@megatron.ietf.org; Wed, 16 Feb 2005 12:01:03 -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 MAA22384 for ; Wed, 16 Feb 2005 12:00:59 -0500 (EST) Received: from zrtps0kn.nortelnetworks.com ([47.140.192.55]) by ietf-mx.ietf.org with esmtp (Exim 4.33) id 1D1StB-0008VT-Jz for mpls@ietf.org; Wed, 16 Feb 2005 12:23:03 -0500 Received: from zrtpd0jn.us.nortel.com (zrtpd0jn.us.nortel.com [47.140.202.35]) by zrtps0kn.nortelnetworks.com (Switch-2.2.6/Switch-2.2.0) with ESMTP id j1GH0JQ29827 for ; Wed, 16 Feb 2005 12:00:19 -0500 (EST) Received: by zrtpd0jn.us.nortel.com with Internet Mail Service (5.5.2653.19) id <1JJLNCTY>; Wed, 16 Feb 2005 12:00:19 -0500 Message-ID: <87AC5F88F03E6249AEA68D40BD3E00BE03192CD6@zcarhxm2.corp.nortel.com> From: "David Allan" To: "'mpls@ietf.org'" Subject: [mpls] Last Call on BCP on ECMP Date: Wed, 16 Feb 2005 12:00:07 -0500 X-Mailer: Internet Mail Service (5.5.2653.19) X-Spam-Score: 0.0 (/) X-Scan-Signature: 7bac9cb154eb5790ae3b2913587a40de 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: 08170828343bcf1325e4a0fb4584481c I agree with Alia that fate sharing between LSPs and reserved labels would be a useful propery to at least START to get back (and IMO it goes beyond OAM/router alert, it should have remained a design intent). I would like to see that included in this BCP. Text to the effect that "the NHLFE selection criteria should be unaffected by the presence of reserved labels (0-15)..." rgds Dave _______________________________________________ mpls mailing list mpls@lists.ietf.org https://www1.ietf.org/mailman/listinfo/mpls From mpls-bounces@ietf.org Wed Feb 16 16:11:27 2005 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 QAA25664; Wed, 16 Feb 2005 16:11:27 -0500 (EST) Received: from megatron.ietf.org ([132.151.6.71]) by ietf-mx.ietf.org with esmtp (Exim 4.33) id 1D1Wnb-0002k8-AI; Wed, 16 Feb 2005 16:33:32 -0500 Received: from localhost.localdomain ([127.0.0.1] helo=megatron.ietf.org) by megatron.ietf.org with esmtp (Exim 4.32) id 1D1WHS-0005gx-Gl; Wed, 16 Feb 2005 16:00:18 -0500 Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org) by megatron.ietf.org with esmtp (Exim 4.32) id 1D1WAA-0001T8-Kh for mpls@megatron.ietf.org; Wed, 16 Feb 2005 15:52:46 -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 PAA23204 for ; Wed, 16 Feb 2005 15:52:44 -0500 (EST) Received: from colo-dns-ext1.juniper.net ([207.17.137.57]) by ietf-mx.ietf.org with esmtp (Exim 4.33) id 1D1WVT-00021p-I8 for mpls@ietf.org; Wed, 16 Feb 2005 16:14:48 -0500 Received: from merlot.juniper.net (merlot.juniper.net [172.17.27.10]) by colo-dns-ext1.juniper.net (8.11.3/8.9.3) with ESMTP id j1GKqC989312; Wed, 16 Feb 2005 12:52:12 -0800 (PST) (envelope-from ina@juniper.net) Received: from garnet.juniper.net (garnet.juniper.net [172.17.28.17]) by merlot.juniper.net (8.11.3/8.11.3) with ESMTP id j1GKq7e37214; Wed, 16 Feb 2005 12:52:07 -0800 (PST) (envelope-from ina@juniper.net) Date: Wed, 16 Feb 2005 12:52:07 -0800 (PST) From: Ina Minei To: mpls@ietf.org Message-ID: <20050216123857.T94598@garnet.juniper.net> MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII X-Spam-Score: 0.0 (/) X-Scan-Signature: cf4fa59384e76e63313391b70cd0dd25 Cc: Bob Thomas Subject: [mpls] Please comment on the LDP documents for advancing RFC3036 to draft-standard 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: 7d33c50f3756db14428398e2bdedd581 As part of advancing the LDP specification to draft standard, the operator survey is now available at: http://www.ietf.org/internet-drafts/draft-minei-ldp-operational-experience-00.txt After the last IETF, the LDP specification draft was respun and is available at: http://ietf.org/internet-drafts/draft-ietf-mpls-rfc3036bis-01.txt The changes from RFC3036 are clearly marked with ###. After the next round of review comments, I will remove the markup and respin the draft. Please send comments on both these documents. Thank you, Ina _______________________________________________ mpls mailing list mpls@lists.ietf.org https://www1.ietf.org/mailman/listinfo/mpls From mpls-bounces@ietf.org Thu Feb 17 13:12:32 2005 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 NAA10860; Thu, 17 Feb 2005 13:12:32 -0500 (EST) Received: from megatron.ietf.org ([132.151.6.71]) by ietf-mx.ietf.org with esmtp (Exim 4.33) id 1D1qUC-0000hk-8y; Thu, 17 Feb 2005 13:34:48 -0500 Received: from localhost.localdomain ([127.0.0.1] helo=megatron.ietf.org) by megatron.ietf.org with esmtp (Exim 4.32) id 1D1nPU-0004e0-QW; Thu, 17 Feb 2005 10:17:44 -0500 Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org) by megatron.ietf.org with esmtp (Exim 4.32) id 1D1nCf-0007hJ-6D; Thu, 17 Feb 2005 10:04:30 -0500 Received: from CNRI.Reston.VA.US (localhost [127.0.0.1]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id KAA02510; Thu, 17 Feb 2005 10:04:27 -0500 (EST) Message-Id: <200502171504.KAA02510@ietf.org> Mime-Version: 1.0 Content-Type: Multipart/Mixed; Boundary="NextPart" To: i-d-announce@ietf.org From: Internet-Drafts@ietf.org Date: Thu, 17 Feb 2005 10:04:27 -0500 Cc: mpls@ietf.org Subject: [mpls] I-D ACTION:draft-ietf-mpls-explicit-null-02.txt X-BeenThere: mpls@lists.ietf.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Multi-Protocol Label Switching WG List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Sender: mpls-bounces@ietf.org Errors-To: mpls-bounces@ietf.org X-Spam-Score: 0.4 (/) X-Scan-Signature: cf3becbbd6d1a45acbe2ffd4ab88bdc2 --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 : Removing a Restriction on the use of MPLS Explicit NULL Author(s) : E. Rosen Filename : draft-ietf-mpls-explicit-null-02.txt Pages : 7 Date : 2005-2-16 The label stack encoding for MPLS (Multi-protocol Label Switching) defines a reserved label value known as "IPv4 Explicit NULL" and a reserved label value known as "IPv6 Explicit NULL". Previously, these labels were only legal when they occurred at the bottom of the MPLS label stack. This restriction is now removed, so that these label values may legally occur anywhere in the stack. A URL for this Internet-Draft is: http://www.ietf.org/internet-drafts/draft-ietf-mpls-explicit-null-02.txt To remove yourself from the I-D Announcement list, send a message to i-d-announce-request@ietf.org with the word unsubscribe in the body of the message. You can also visit https://www1.ietf.org/mailman/listinfo/I-D-announce to change your subscription settings. Internet-Drafts are also available by anonymous FTP. Login with the username "anonymous" and a password of your e-mail address. After logging in, type "cd internet-drafts" and then "get draft-ietf-mpls-explicit-null-02.txt". A list of Internet-Drafts directories can be found in http://www.ietf.org/shadow.html or ftp://ftp.ietf.org/ietf/1shadow-sites.txt Internet-Drafts can also be obtained by e-mail. Send a message to: mailserv@ietf.org. In the body type: "FILE /internet-drafts/draft-ietf-mpls-explicit-null-02.txt". NOTE: The mail server at ietf.org can return the document in MIME-encoded form by using the "mpack" utility. To use this feature, insert the command "ENCODING mime" before the "FILE" command. To decode the response(s), you will need "munpack" or a MIME-compliant mail reader. Different MIME-compliant mail readers exhibit different behavior, especially when dealing with "multipart" MIME messages (i.e. documents which have been split up into multiple messages), so check your local documentation on how to manipulate these messages. Below is the data which will enable a MIME compliant mail reader implementation to automatically retrieve the ASCII version of the Internet-Draft. --NextPart Content-Type: Multipart/Alternative; Boundary="OtherAccess" --OtherAccess Content-Type: Message/External-body; access-type="mail-server"; server="mailserv@ietf.org" Content-Type: text/plain Content-ID: <2005-2-17102529.I-D@ietf.org> ENCODING mime FILE /internet-drafts/draft-ietf-mpls-explicit-null-02.txt --OtherAccess Content-Type: Message/External-body; name="draft-ietf-mpls-explicit-null-02.txt"; site="ftp.ietf.org"; access-type="anon-ftp"; directory="internet-drafts" Content-Type: text/plain Content-ID: <2005-2-17102529.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 Thu Feb 17 17:23:07 2005 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 RAA16305; Thu, 17 Feb 2005 17:23:07 -0500 (EST) Received: from megatron.ietf.org ([132.151.6.71]) by ietf-mx.ietf.org with esmtp (Exim 4.33) id 1D1uOh-0002UJ-Kx; Thu, 17 Feb 2005 17:45:24 -0500 Received: from localhost.localdomain ([127.0.0.1] helo=megatron.ietf.org) by megatron.ietf.org with esmtp (Exim 4.32) id 1D1thy-0005Fn-Cj; Thu, 17 Feb 2005 17:01:14 -0500 Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org) by megatron.ietf.org with esmtp (Exim 4.32) id 1D1sGa-0006lV-Dq for mpls@megatron.ietf.org; Thu, 17 Feb 2005 15:28:53 -0500 Received: from tm3.ca.alcatel.com (kanfw1.ottawa.alcatel.ca [192.75.23.69]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id PAA01575 for ; Thu, 17 Feb 2005 15:28:50 -0500 (EST) Received: from alcatel.com (localhost [127.0.0.1]) by tm3.ca.alcatel.com (8.13.0/8.13.0) with ESMTP id j1HKRjRC004841; Thu, 17 Feb 2005 15:27:46 -0500 (EST) Message-ID: <4214FE41.F8D844FF@alcatel.com> Date: Thu, 17 Feb 2005 15:27:45 -0500 From: Gatot Susilo Organization: Alcatel Canada X-Mailer: Mozilla 4.79 [en] (Windows NT 5.0; U) X-Accept-Language: en MIME-Version: 1.0 To: kireeti@juniper.net, swallow@cisco.com Cc: mpls@ietf.org Subject: [mpls] Comments for draft-ietf-mpls-lsp-ping-07 X-BeenThere: mpls@lists.ietf.org X-Mailman-Version: 2.1.5 Precedence: list Reply-To: gatot.susilo@alcatel.com List-Id: Multi-Protocol Label Switching WG List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Content-Type: multipart/mixed; boundary="===============0817144734==" Sender: mpls-bounces@ietf.org Errors-To: mpls-bounces@ietf.org X-Spam-Score: 0.5 (/) X-Scan-Signature: d185fa790257f526fedfd5d01ed9c976 --===============0817144734== Content-Type: text/html; charset=us-ascii Content-Transfer-Encoding: 7bit Hi Kireeti and George:
I have some comments for the draft.
1/ Timestamp on echo request message.
It's expected that the source and destination node will timestamp the echo message. It would be expected that each node will be synchronized by NTP server. If I am not mistaken, the NTP server will give accuracy about 10msec. Therefore, between two nodes synchronized by the same NTP server may have time difference up to 20msec. On the broadband network, the round-trip-time of echo message may be less than 10msec.
This may bring an issue that round-trip-time will be less than the trip-time.
Also when the destination node may have time lag (i.e., +/- 10msec) w.r.t the source node, the trip time will be a negative value (i.e. rx. timestamp - tx. timestamp).

Could you please explain what the benefit of having timestamp on the echo message and how do we deal with the issue above ?
If there is no benefit, probably it should be removed.

2/ Mandatory/Optional TLV.
The mandatory/optional TLV is identified by high-order bit. If the high-order bit is not set, the TLV is mandatory, otherwise it's optional.
To clarify this, would it be possible to include this "high-order" bit in the TLV format diagram?
Hence, the TLV format will look like this: 

 0                   1                   2                   3
 0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
|F|           Type              |            Length             |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
 |                             Value                             |
 .                                                               .
 .                                                               .
 .                                                               .
 |                                                               |
 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
F - set to 0 for mandatory TLV and set to 1 for optional TLV.
 

3/ Errored TLV:
The draft stated that the Errored TLV has type=32678 (i.e., 0x7FA6). As mentioned previously that the optional TLV sets the high-order bit , should this Errored TLV have value=0xFFA6 (i.e. 65446). This can also be fixed with the proposed TLV format above.

4/ Typo on length of  BGP Labelled IPv4 FEC and CR-LDP FEC.
The length of BGP Labelled IPv4 FEC should be "9" instead of "10".
The length of CR-LDP FEC should be "8" instead of "6".
 

Cheers,
/Gatot --===============0817144734== 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 --===============0817144734==-- From mpls-bounces@ietf.org Thu Feb 17 17:34:05 2005 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 RAA18070; Thu, 17 Feb 2005 17:34:05 -0500 (EST) Received: from megatron.ietf.org ([132.151.6.71]) by ietf-mx.ietf.org with esmtp (Exim 4.33) id 1D1uZK-0002wP-7r; Thu, 17 Feb 2005 17:56:23 -0500 Received: from localhost.localdomain ([127.0.0.1] helo=megatron.ietf.org) by megatron.ietf.org with esmtp (Exim 4.32) id 1D1tjh-0007Dm-1y; Thu, 17 Feb 2005 17:03:01 -0500 Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org) by megatron.ietf.org with esmtp (Exim 4.32) id 1D1ssQ-0008NF-Sc for mpls@megatron.ietf.org; Thu, 17 Feb 2005 16:07:58 -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 QAA05462 for ; Thu, 17 Feb 2005 16:07:57 -0500 (EST) Received: from kanfw1.ottawa.alcatel.ca ([192.75.23.69] helo=tm2.ca.alcatel.com) by ietf-mx.ietf.org with esmtp (Exim 4.33) id 1D1tDx-0007rh-Kd for mpls@ietf.org; Thu, 17 Feb 2005 16:30:13 -0500 Received: from alcatel.com (localhost [127.0.0.1]) by tm2.ca.alcatel.com (8.13.0/8.13.0) with ESMTP id j1HL7uJe024478 for ; Thu, 17 Feb 2005 16:07:56 -0500 (EST) Message-ID: <421507AB.6EACB468@alcatel.com> Date: Thu, 17 Feb 2005 16:07:55 -0500 From: Gatot Susilo Organization: Alcatel Canada X-Mailer: Mozilla 4.79 [en] (Windows NT 5.0; U) X-Accept-Language: en MIME-Version: 1.0 To: mpls@ietf.org Content-Type: multipart/mixed; boundary="------------21E8EB907A7A5A77DACA93C9" X-Spam-Score: 0.5 (/) X-Scan-Signature: f66b12316365a3fe519e75911daf28a8 Subject: [mpls] [Fwd: Comments for draft-ietf-mpls-lsp-ping-07] X-BeenThere: mpls@lists.ietf.org X-Mailman-Version: 2.1.5 Precedence: list Reply-To: gatot.susilo@alcatel.com 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.5 (/) X-Scan-Signature: 6e922792024732fb1bb6f346e63517e4 This is a multi-part message in MIME format. --------------21E8EB907A7A5A77DACA93C9 Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit --------------21E8EB907A7A5A77DACA93C9 Content-Type: message/rfc822 Content-Disposition: inline Message-ID: <4214FE41.F8D844FF@alcatel.com> Date: Thu, 17 Feb 2005 15:27:45 -0500 From: Gatot Susilo Reply-To: gatot.susilo@alcatel.com Organization: Alcatel Canada X-Mailer: Mozilla 4.79 [en] (Windows NT 5.0; U) X-Accept-Language: en MIME-Version: 1.0 To: kireeti@juniper.net, swallow@cisco.com CC: mpls@lists.ietf.org Subject: Comments for draft-ietf-mpls-lsp-ping-07 Content-Type: text/html; charset=us-ascii Content-Transfer-Encoding: 7bit Hi Kireeti and George:
I have some comments for the draft.
1/ Timestamp on echo request message.
It's expected that the source and destination node will timestamp the echo message. It would be expected that each node will be synchronized by NTP server. If I am not mistaken, the NTP server will give accuracy about 10msec. Therefore, between two nodes synchronized by the same NTP server may have time difference up to 20msec. On the broadband network, the round-trip-time of echo message may be less than 10msec.
This may bring an issue that round-trip-time will be less than the trip-time.
Also when the destination node may have time lag (i.e., +/- 10msec) w.r.t the source node, the trip time will be a negative value (i.e. rx. timestamp - tx. timestamp).

Could you please explain what the benefit of having timestamp on the echo message and how do we deal with the issue above ?
If there is no benefit, probably it should be removed.

2/ Mandatory/Optional TLV.
The mandatory/optional TLV is identified by high-order bit. If the high-order bit is not set, the TLV is mandatory, otherwise it's optional.
To clarify this, would it be possible to include this "high-order" bit in the TLV format diagram?
Hence, the TLV format will look like this: 

 0                   1                   2                   3
 0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
|F|           Type              |            Length             |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
 |                             Value                             |
 .                                                               .
 .                                                               .
 .                                                               .
 |                                                               |
 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
F - set to 0 for mandatory TLV and set to 1 for optional TLV.
 

3/ Errored TLV:
The draft stated that the Errored TLV has type=32678 (i.e., 0x7FA6). As mentioned previously that the optional TLV sets the high-order bit , should this Errored TLV have value=0xFFA6 (i.e. 65446). This can also be fixed with the proposed TLV format above.

4/ Typo on length of  BGP Labelled IPv4 FEC and CR-LDP FEC.
The length of BGP Labelled IPv4 FEC should be "9" instead of "10".
The length of CR-LDP FEC should be "8" instead of "6".
 

Cheers,
/Gatot --------------21E8EB907A7A5A77DACA93C9 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 --------------21E8EB907A7A5A77DACA93C9-- From mpls-bounces@ietf.org Fri Feb 18 16:54:51 2005 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 QAA00572; Fri, 18 Feb 2005 16:54:51 -0500 (EST) Received: from megatron.ietf.org ([132.151.6.71]) by ietf-mx.ietf.org with esmtp (Exim 4.33) id 1D2GR7-0008CV-Qk; Fri, 18 Feb 2005 17:17:22 -0500 Received: from localhost.localdomain ([127.0.0.1] helo=megatron.ietf.org) by megatron.ietf.org with esmtp (Exim 4.32) id 1D2EtU-00087Z-1L; Fri, 18 Feb 2005 15:38:32 -0500 Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org) by megatron.ietf.org with esmtp (Exim 4.32) id 1D2EiQ-0003Bw-Cw; Fri, 18 Feb 2005 15:27:06 -0500 Received: from CNRI.Reston.VA.US (localhost [127.0.0.1]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id PAA08967; Fri, 18 Feb 2005 15:27:04 -0500 (EST) Message-Id: <200502182027.PAA08967@ietf.org> Mime-Version: 1.0 Content-Type: Multipart/Mixed; Boundary="NextPart" To: i-d-announce@ietf.org From: Internet-Drafts@ietf.org Date: Fri, 18 Feb 2005 15:27:04 -0500 Cc: mpls@ietf.org Subject: [mpls] I-D ACTION:draft-ietf-mpls-p2mp-sig-requirement-01.txt X-BeenThere: mpls@lists.ietf.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Multi-Protocol Label Switching WG List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Sender: mpls-bounces@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-01.txt Pages : 29 Date : 2005-2-18 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-01.txt To remove yourself from the I-D Announcement list, send a message to i-d-announce-request@ietf.org with the word unsubscribe in the body of the message. You can also visit https://www1.ietf.org/mailman/listinfo/I-D-announce to change your subscription settings. Internet-Drafts are also available by anonymous FTP. Login with the username "anonymous" and a password of your e-mail address. After logging in, type "cd internet-drafts" and then "get draft-ietf-mpls-p2mp-sig-requirement-01.txt". A list of Internet-Drafts directories can be found in http://www.ietf.org/shadow.html or ftp://ftp.ietf.org/ietf/1shadow-sites.txt Internet-Drafts can also be obtained by e-mail. Send a message to: mailserv@ietf.org. In the body type: "FILE /internet-drafts/draft-ietf-mpls-p2mp-sig-requirement-01.txt". NOTE: The mail server at ietf.org can return the document in MIME-encoded form by using the "mpack" utility. To use this feature, insert the command "ENCODING mime" before the "FILE" command. To decode the response(s), you will need "munpack" or a MIME-compliant mail reader. Different MIME-compliant mail readers exhibit different behavior, especially when dealing with "multipart" MIME messages (i.e. documents which have been split up into multiple messages), so check your local documentation on how to manipulate these messages. Below is the data which will enable a MIME compliant mail reader implementation to automatically retrieve the ASCII version of the Internet-Draft. --NextPart Content-Type: Multipart/Alternative; Boundary="OtherAccess" --OtherAccess Content-Type: Message/External-body; access-type="mail-server"; server="mailserv@ietf.org" Content-Type: text/plain Content-ID: <2005-2-18144523.I-D@ietf.org> ENCODING mime FILE /internet-drafts/draft-ietf-mpls-p2mp-sig-requirement-01.txt --OtherAccess Content-Type: Message/External-body; name="draft-ietf-mpls-p2mp-sig-requirement-01.txt"; site="ftp.ietf.org"; access-type="anon-ftp"; directory="internet-drafts" Content-Type: text/plain Content-ID: <2005-2-18144523.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 Mon Feb 21 13:27:01 2005 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 NAA28302; Mon, 21 Feb 2005 13:27:00 -0500 (EST) Received: from megatron.ietf.org ([132.151.6.71]) by ietf-mx.ietf.org with esmtp (Exim 4.33) id 1D3IdD-0000ph-TO; Mon, 21 Feb 2005 13:50:08 -0500 Received: from localhost.localdomain ([127.0.0.1] helo=megatron.ietf.org) by megatron.ietf.org with esmtp (Exim 4.32) id 1D3Gel-0003rk-A2; Mon, 21 Feb 2005 11:43:35 -0500 Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org) by megatron.ietf.org with esmtp (Exim 4.32) id 1D3Fyb-00042R-QV for mpls@megatron.ietf.org; Mon, 21 Feb 2005 11:00:01 -0500 Received: from mail.mindsource.com (mail.mindsource.com [216.218.194.54]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id KAA13967 for ; Mon, 21 Feb 2005 10:59:43 -0500 (EST) Received: from pons.mindsource.com (pons.mindsource.com [10.10.10.8]) by mail.mindsource.com (8.13.1/8.13.1) with ESMTP id j1LFxfNS015298 for ; Mon, 21 Feb 2005 07:59:44 -0800 (PST) Content-Class: urn:content-classes:message Date: Mon, 21 Feb 2005 07:59:41 -0800 MIME-Version: 1.0 Message-ID: <6EA94041716E0C4EA1E6D1234DE87C2750F040@pons.mindsource.com> X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2800.1478 Importance: normal Priority: normal Thread-Topic: Fulltime opportunity for MPLS and BGP expert in San Jose, California thread-index: AcUYLnKkzoDSyuiFQjqqwN5/QlVsyQ== From: "Nikki Motas" To: Subject: [mpls] Fulltime opportunity for MPLS and BGP expert in San Jose, California 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="===============1370953002==" Sender: mpls-bounces@ietf.org Errors-To: mpls-bounces@ietf.org X-Spam-Score: 0.3 (/) X-Scan-Signature: b612707e1a3f67df80ae89cdab1ba981 This is a multi-part message in MIME format. --===============1370953002== Content-Class: urn:content-classes:message Content-Type: multipart/alternative; boundary="----_=_NextPart_001_01C5182E.5A95F4D5" This is a multi-part message in MIME format. ------_=_NextPart_001_01C5182E.5A95F4D5 Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: quoted-printable Hi Everyone, =20 I have a client in San Jose that is looking for a fulltime Network and Customer Support Engineer. Although it is Network and Customer support, the position is rather high profile and does pay very well. =20 I've included the job description below. Please let me know if you are interested and available. I'd like to talk to you more about this opportunity. =20 Thanks! Nikki =20 Senior Network and Customer Support Engineer=20 Duties and Responsibilities:=20 (List of responsibilities including daily, weekly, quarterly, etc.)=20 - Provide high-level technical expertise in resolving core design and avoid further product issues.=20 - Provides support to customers, resellers, and field personnel in resolving company product related issues=20 - Document sequence of events related to resolving customer technical issues=20 The Customer Support Engineer will provide daily phone consultation with clients as they call to report problems with their software and/or hardware; document client calls in the client management database; ensure client expectations are properly managed, and that issues and needs are resolved to the client's satisfaction in a timely manner. The successful candidate will work as a direct resource for external clients, as well as internal clients to resolve technical problems, provide troubleshooting skills and research for more difficult problems, escalate client problems that require a more complicated solution, maintain call ownership, and see the problem through to resolution. Additionally, they will test new releases for software products before distribution to clients to ensure the product is sound, work with third party vendors regarding client data that is transmitted to them, research and resolve problems that may occur with sending and/or receiving client data, troubleshoot client-reporting issues, contact vendors to clear up the issues, and provide follow-up to clients when issues are resolved. The Successful candidate understands all service offers and the benefits to our clients, works as a direct resource to answer client inquiries, and must have the ability to effectively communicate to both clients and internal personnel while working under pressure and with time constraints. Finally, the successful candidate will be involved in the creation and completion of department and individual goals and fulfilling all services the team promises to clients.=20 Job Qualifications Education and Work Experience:=20 MOST IMPORTANT - very strong BGP and MPLS experience CCIE training or certification is highly desirable FNCNE and/or FNCNP is highly preferred. Candidates hired without this certification will be required to complete the FNCNE certification program within six (6) months of hire date. Prefer BS or related discipline. Experience with STP, BGP, OSPF, RIP, L4-7 Switching, MPLS, IPX, AppleTalk=20 Federal clearance is a HUGE plus, but not a requirement. =20 This is 24/7 operation and this position will entail shift work after the first 4 months =20 =20 Nikki Motas Technical Recruiter EdisonSearch, A division of Mindsource, Inc 650.314.6411 direct 650.704.1201 mobile =20 ------_=_NextPart_001_01C5182E.5A95F4D5 Content-Type: text/html; charset="us-ascii" Content-Transfer-Encoding: quoted-printable

Hi = Everyone,

 

I have a client in = San Jose that is looking = for a fulltime Network and Customer Support Engineer.  Although it is Network and Customer support, the position is = rather high profile and does pay very well.

 

I’ve included the job = description below.  Please let me know = if you are interested and available.  = I’d like to talk to you more about this opportunity.

 

Thanks!

Nikki

 

Senior Network and Customer Support Engineer

Duties and Responsibilities:
(List of responsibilities including daily, weekly, quarterly, etc.)

- Provide high-level technical expertise in resolving core design and = avoid further product issues.
- Provides support to customers, resellers, and field personnel in = resolving company product related issues
- Document sequence of events related to resolving customer technical = issues

The Customer Support Engineer will provide daily phone consultation with clients as they call to report problems with their software and/or = hardware; document client calls in the client management database; ensure client expectations are properly managed, and that issues and needs are = resolved to the client's satisfaction in a timely manner. The successful candidate = will work as a direct resource for external clients, as well as internal = clients to resolve technical problems, provide troubleshooting skills and research = for more difficult problems, escalate client = problems that require a more complicated solution, maintain call ownership, and see = the problem through to resolution. Additionally, they will test new releases = for software products before distribution to clients to ensure the product = is sound, work with third party vendors regarding client data that is = transmitted to them, research and resolve problems that may occur with sending = and/or receiving client data, troubleshoot client-reporting issues, contact = vendors to clear up the issues, and provide follow-up to clients when issues are = resolved. The Successful candidate understands all service offers and the benefits = to our clients, works as a direct resource to answer client inquiries, and must = have the ability to effectively communicate to both clients and internal = personnel while working under pressure and with time constraints. Finally, the = successful candidate will be involved in the creation and completion of department = and individual goals and fulfilling all services the team promises to = clients.

Job = Qualifications

Education and = Work Experience:

MOST IMPORTANT = – very strong BGP and MPLS experience

CCIE training = or certification is highly desirable

FNCNE and/or FNCNP is highly preferred. = Candidates hired without this certification will be required to complete the FNCNE certification program within six (6) months of hire date. Prefer BS or = related discipline. Experience with STP, BGP, OSPF, RIP, L4-7 Switching, MPLS, = IPX, AppleTalk

Federal clearance is a HUGE plus, = but not a requirement.

 

This is 24/7 = operation and this position will entail shift work after the first 4 = months

 

 

Nikki Motas

Technical Recruiter

EdisonSearch, A division of Mindsource, = Inc

650.314.6411 direct

650.704.1201 mobile

 

=00 ------_=_NextPart_001_01C5182E.5A95F4D5-- --===============1370953002== 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 --===============1370953002==-- From mpls-bounces@ietf.org Wed Feb 23 01:16:32 2005 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 BAA16981; Wed, 23 Feb 2005 01:16:32 -0500 (EST) Received: from megatron.ietf.org ([132.151.6.71]) by ietf-mx.ietf.org with esmtp (Exim 4.33) id 1D3qBe-0003uX-Lb; Wed, 23 Feb 2005 01:39:57 -0500 Received: from localhost.localdomain ([127.0.0.1] helo=megatron.ietf.org) by megatron.ietf.org with esmtp (Exim 4.32) id 1D3kfs-0004YW-Fm; Tue, 22 Feb 2005 19:46:44 -0500 Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org) by megatron.ietf.org with esmtp (Exim 4.32) id 1D3e0O-000794-Qx for mpls@megatron.ietf.org; Tue, 22 Feb 2005 12:39:28 -0500 Received: from tbdns.testbed.local ([80.86.78.228]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id MAA27101 for ; Tue, 22 Feb 2005 12:39:18 -0500 (EST) Received: from [163.162.9.31] ([163.162.9.31]) (authenticated bits=0) by tbdns.testbed.local (8.12.8/8.12.8) with ESMTP id j1MHWEpt029573 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO) for ; Tue, 22 Feb 2005 18:32:17 +0100 Message-ID: <421B6E18.9030409@pi.se> Date: Tue, 22 Feb 2005 18:38:32 +0100 From: Loa Andersson User-Agent: Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US; rv:1.7.2) Gecko/20040803 X-Accept-Language: en-us, en MIME-Version: 1.0 To: mpls@ietf.org Content-Type: text/plain; charset=us-ascii; format=flowed Content-Transfer-Encoding: 7bit Content-Transfer-Encoding: 7bit Subject: [mpls] agenda for Minneapolis 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: 93238566e09e6e262849b4f805833007 Content-Transfer-Encoding: 7bit All, I've placed a temporary agenda for the MPLS wg meeting in Minneapolis at: http://www.tla-group.com/~mpls/mpls-agenda-mpls.htm Be kind when you remind me about my misstakes and omissions. /Loa -- Loa Andersson Principal Networking Architect Acreo AB phone: +46 8 632 77 14 Isafjordsgatan 22 mobile: +46 739 81 21 64 Kista, Sweden email: loa.andersson@acreo.se loa@pi.se _______________________________________________ mpls mailing list mpls@lists.ietf.org https://www1.ietf.org/mailman/listinfo/mpls From mpls-bounces@ietf.org Wed Feb 23 18:46:41 2005 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 SAA16015; Wed, 23 Feb 2005 18:46:40 -0500 (EST) Received: from megatron.ietf.org ([132.151.6.71]) by ietf-mx.ietf.org with esmtp (Exim 4.33) id 1D46a9-0001Fw-BT; Wed, 23 Feb 2005 19:10:17 -0500 Received: from localhost.localdomain ([127.0.0.1] helo=megatron.ietf.org) by megatron.ietf.org with esmtp (Exim 4.32) id 1D3kjk-0005T8-Qw; Tue, 22 Feb 2005 19:50:44 -0500 Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org) by megatron.ietf.org with esmtp (Exim 4.32) id 1D3hDe-0001EG-H1; Tue, 22 Feb 2005 16:05:22 -0500 Received: from CNRI.Reston.VA.US (localhost [127.0.0.1]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id QAA21488; Tue, 22 Feb 2005 16:05:20 -0500 (EST) Message-Id: <200502222105.QAA21488@ietf.org> Mime-Version: 1.0 Content-Type: Multipart/Mixed; Boundary="NextPart" To: i-d-announce@ietf.org From: Internet-Drafts@ietf.org Date: Tue, 22 Feb 2005 16:05:19 -0500 Cc: mpls@ietf.org Subject: [mpls] I-D ACTION:draft-ietf-mpls-lsp-ping-08.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: cf3becbbd6d1a45acbe2ffd4ab88bdc2 --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 : Detecting MPLS Data Plane Failures Author(s) : K. Kompella, G. Swallow Filename : draft-ietf-mpls-lsp-ping-08.txt Pages : 42 Date : 2005-2-22 This document describes a simple and efficient mechanism that can be used to detect data plane failures in Multi-Protocol Label Switching (MPLS) Label Switched Paths (LSPs). There are two parts to this document: information carried in an MPLS 'echo request' and 'echo reply' for the purposes of fault detection and isolation; and mechanisms for reliably sending the echo reply. A URL for this Internet-Draft is: http://www.ietf.org/internet-drafts/draft-ietf-mpls-lsp-ping-08.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-lsp-ping-08.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-lsp-ping-08.txt". NOTE: The mail server at ietf.org can return the document in MIME-encoded form by using the "mpack" utility. To use this feature, insert the command "ENCODING mime" before the "FILE" command. To decode the response(s), you will need "munpack" or a MIME-compliant mail reader. Different MIME-compliant mail readers exhibit different behavior, especially when dealing with "multipart" MIME messages (i.e. documents which have been split up into multiple messages), so check your local documentation on how to manipulate these messages. Below is the data which will enable a MIME compliant mail reader implementation to automatically retrieve the ASCII version of the Internet-Draft. --NextPart Content-Type: Multipart/Alternative; Boundary="OtherAccess" --OtherAccess Content-Type: Message/External-body; access-type="mail-server"; server="mailserv@ietf.org" Content-Type: text/plain Content-ID: <2005-2-22160518.I-D@ietf.org> ENCODING mime FILE /internet-drafts/draft-ietf-mpls-lsp-ping-08.txt --OtherAccess Content-Type: Message/External-body; name="draft-ietf-mpls-lsp-ping-08.txt"; site="ftp.ietf.org"; access-type="anon-ftp"; directory="internet-drafts" Content-Type: text/plain Content-ID: <2005-2-22160518.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 Wed Feb 23 18:59:40 2005 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 SAA18395; Wed, 23 Feb 2005 18:59:40 -0500 (EST) Received: from megatron.ietf.org ([132.151.6.71]) by ietf-mx.ietf.org with esmtp (Exim 4.33) id 1D46mj-0001zZ-7M; Wed, 23 Feb 2005 19:23:17 -0500 Received: from localhost.localdomain ([127.0.0.1] helo=megatron.ietf.org) by megatron.ietf.org with esmtp (Exim 4.32) id 1D3kjn-0005To-Mu; Tue, 22 Feb 2005 19:50:47 -0500 Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org) by megatron.ietf.org with esmtp (Exim 4.32) id 1D3hE1-0001FS-14; Tue, 22 Feb 2005 16:05:45 -0500 Received: from CNRI.Reston.VA.US (localhost [127.0.0.1]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id QAA21538; Tue, 22 Feb 2005 16:05:42 -0500 (EST) Message-Id: <200502222105.QAA21538@ietf.org> Mime-Version: 1.0 Content-Type: Multipart/Mixed; Boundary="NextPart" To: i-d-announce@ietf.org From: Internet-Drafts@ietf.org Date: Tue, 22 Feb 2005 16:05:42 -0500 Cc: mpls@ietf.org Subject: [mpls] I-D ACTION:draft-ietf-mpls-lsr-self-test-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.4 (/) X-Scan-Signature: e1b0e72ff1bbd457ceef31828f216a86 --NextPart A New Internet-Draft is available from the on-line Internet-Drafts directories. This draft is a work item of the Multiprotocol Label Switching Working Group of the IETF. Title : Label Switching Router Self-Test Author(s) : G. Swallow, et al. Filename : draft-ietf-mpls-lsr-self-test-04.txt Pages : 13 Date : 2005-2-22 This document defines a means of self test for a Label-Switching Router (LSR) to verify that its dataplane is functioning for certain key Multi-Protocol Label Switching (MPLS) applications including unicast forwarding based on LDP [LDP] and traffic engineering tunnels based on [RSVP-TE]. A new Loopback FEC type is defined to allow an upstream neighbor to assist in the testing at very low cost. MPLS Echo Request and MPLS Echo Reply messages [LSP-Ping] messages are extended to do the actually probing. A URL for this Internet-Draft is: http://www.ietf.org/internet-drafts/draft-ietf-mpls-lsr-self-test-04.txt To remove yourself from the I-D Announcement list, send a message to i-d-announce-request@ietf.org with the word unsubscribe in the body of the message. You can also visit https://www1.ietf.org/mailman/listinfo/I-D-announce to change your subscription settings. Internet-Drafts are also available by anonymous FTP. Login with the username "anonymous" and a password of your e-mail address. After logging in, type "cd internet-drafts" and then "get draft-ietf-mpls-lsr-self-test-04.txt". A list of Internet-Drafts directories can be found in http://www.ietf.org/shadow.html or ftp://ftp.ietf.org/ietf/1shadow-sites.txt Internet-Drafts can also be obtained by e-mail. Send a message to: mailserv@ietf.org. In the body type: "FILE /internet-drafts/draft-ietf-mpls-lsr-self-test-04.txt". NOTE: The mail server at ietf.org can return the document in MIME-encoded form by using the "mpack" utility. To use this feature, insert the command "ENCODING mime" before the "FILE" command. To decode the response(s), you will need "munpack" or a MIME-compliant mail reader. Different MIME-compliant mail readers exhibit different behavior, especially when dealing with "multipart" MIME messages (i.e. documents which have been split up into multiple messages), so check your local documentation on how to manipulate these messages. Below is the data which will enable a MIME compliant mail reader implementation to automatically retrieve the ASCII version of the Internet-Draft. --NextPart Content-Type: Multipart/Alternative; Boundary="OtherAccess" --OtherAccess Content-Type: Message/External-body; access-type="mail-server"; server="mailserv@ietf.org" Content-Type: text/plain Content-ID: <2005-2-22160524.I-D@ietf.org> ENCODING mime FILE /internet-drafts/draft-ietf-mpls-lsr-self-test-04.txt --OtherAccess Content-Type: Message/External-body; name="draft-ietf-mpls-lsr-self-test-04.txt"; site="ftp.ietf.org"; access-type="anon-ftp"; directory="internet-drafts" Content-Type: text/plain Content-ID: <2005-2-22160524.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 Wed Feb 23 20:18:03 2005 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 UAA09648; Wed, 23 Feb 2005 20:18:03 -0500 (EST) Received: from megatron.ietf.org ([132.151.6.71]) by ietf-mx.ietf.org with esmtp (Exim 4.33) id 1D480X-00005Q-TU; Wed, 23 Feb 2005 20:41:39 -0500 Received: from localhost.localdomain ([127.0.0.1] helo=megatron.ietf.org) by megatron.ietf.org with esmtp (Exim 4.32) id 1D3kms-0006U7-L9; Tue, 22 Feb 2005 19:53:58 -0500 Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org) by megatron.ietf.org with esmtp (Exim 4.32) id 1D3VA7-00051Q-FV for mpls@megatron.ietf.org; Tue, 22 Feb 2005 03:12:55 -0500 Received: from smtp-gateway.tataisp.com (smtp-gateway.tataisp.com [203.124.230.5]) by ietf.org (8.9.1a/8.9.1a) with SMTP id DAA23897 for ; Tue, 22 Feb 2005 03:12:52 -0500 (EST) Message-Id: <200502220812.DAA23897@ietf.org> Received: from lists.ietf.org ([203.124.240.10]) by smtp-gateway.tataisp.com (SAVSMTP 3.1.2.35) with SMTP id M2005022213450507040 for ; Tue, 22 Feb 2005 13:45:05 +0530 From: "Returned mail" To: mpls@ietf.org Date: Tue, 22 Feb 2005 13:34:11 +0530 MIME-Version: 1.0 Content-Type: multipart/mixed; boundary="----=_NextPart_000_0000_2B292F0C.D7F603FF" X-Priority: 3 X-MSMail-Priority: Normal X-Mailer: Microsoft Outlook Express 6.00.2600.0000 X-MIMEOLE: Produced By Microsoft MimeOLE V6.00.2600.0000 Subject: [mpls] Status 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: 5.2 (+++++) X-Spam-Flag: YES X-Scan-Signature: b19722fc8d3865b147c75ae2495625f2 This is a multi-part message in MIME format. ------=_NextPart_000_0000_2B292F0C.D7F603FF Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit ------=_NextPart_000_0000_2B292F0C.D7F603FF Content-Type: text/plain; name="DELETED0.TXT" Content-Disposition: attachment; filename="DELETED0.TXT" Content-Transfer-Encoding: base64 ------=_NextPart_000_0000_2B292F0C.D7F603FF 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 ------=_NextPart_000_0000_2B292F0C.D7F603FF-- From mpls-bounces@ietf.org Wed Feb 23 21:13:00 2005 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 VAA28547; Wed, 23 Feb 2005 21:13:00 -0500 (EST) Received: from megatron.ietf.org ([132.151.6.71]) by ietf-mx.ietf.org with esmtp (Exim 4.33) id 1D48ri-0005uX-7b; Wed, 23 Feb 2005 21:36:37 -0500 Received: from localhost.localdomain ([127.0.0.1] helo=megatron.ietf.org) by megatron.ietf.org with esmtp (Exim 4.32) id 1D3w6R-0006qk-1p; Wed, 23 Feb 2005 07:58:55 -0500 Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org) by megatron.ietf.org with esmtp (Exim 4.32) id 1D3w6O-0006qa-2t for mpls@megatron.ietf.org; Wed, 23 Feb 2005 07:58:53 -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 HAA12976 for ; Wed, 23 Feb 2005 07:58:44 -0500 (EST) Received: from ihemail2.lucent.com ([192.11.222.163]) by ietf-mx.ietf.org with esmtp (Exim 4.33) id 1D3wSy-0001eO-Ao for mpls@ietf.org; Wed, 23 Feb 2005 08:22:13 -0500 Received: from ii0015exch002u.wins.lucent.com (h135-254-246-205.lucent.com [135.254.246.205]) by ihemail2.lucent.com (8.12.11/8.12.11) with ESMTP id j1NCw6rG009294 for ; Wed, 23 Feb 2005 06:58:07 -0600 (CST) Received: from lucent.com (BHADRI-ST2.iidc.lucent.com [135.254.211.112]) by ii0015exch002u.wins.lucent.com with SMTP (Microsoft Exchange Internet Mail Service Version 5.5.2657.72) id 1TWCMY1K; Wed, 23 Feb 2005 18:28:05 +0530 Message-ID: <421C7DDD.9BD752E7@lucent.com> Date: Wed, 23 Feb 2005 18:28:05 +0530 From: Madhusudhan Bhadri Organization: Lucent Technologies X-Mailer: Mozilla 4.76 [en]C-CCK-MCD EMS-1.5 (Windows NT 5.0; U) X-Accept-Language: en MIME-Version: 1.0 To: Loa Andersson References: <421B6E18.9030409@pi.se> Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit X-Spam-Score: 0.0 (/) X-Scan-Signature: 7bac9cb154eb5790ae3b2913587a40de Content-Transfer-Encoding: 7bit Cc: mpls@ietf.org Subject: [mpls] Explicit/Implicit NULL for PHP case 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: 08170828343bcf1325e4a0fb4584481c Content-Transfer-Encoding: 7bit Hi, If we enable explicit null along with PHP enabled for LSP creation, what should be stamped on the data packet. Normally we will program a POP operation for a data plane. In this case should a NULL label be stamped on the data packet. Thanks in Advance Madhu --------------------- Lucent Technologies Bangalore _______________________________________________ mpls mailing list mpls@lists.ietf.org https://www1.ietf.org/mailman/listinfo/mpls From mpls-bounces@ietf.org Wed Feb 23 22:47:06 2005 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 WAA04932; Wed, 23 Feb 2005 22:47:05 -0500 (EST) Received: from megatron.ietf.org ([132.151.6.71]) by ietf-mx.ietf.org with esmtp (Exim 4.33) id 1D4AKp-0007yS-6f; Wed, 23 Feb 2005 23:10:43 -0500 Received: from localhost.localdomain ([127.0.0.1] helo=megatron.ietf.org) by megatron.ietf.org with esmtp (Exim 4.32) id 1D3knT-0006jT-Bo; Tue, 22 Feb 2005 19:54:35 -0500 Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org) by megatron.ietf.org with esmtp (Exim 4.32) id 1D3X79-0004m1-Md for mpls@megatron.ietf.org; Tue, 22 Feb 2005 05:18:03 -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 FAA10440 for ; Tue, 22 Feb 2005 05:17:51 -0500 (EST) Received: from ams-iport-1.cisco.com ([144.254.224.140]) by ietf-mx.ietf.org with esmtp (Exim 4.33) id 1D3XTW-0007Yk-4y for mpls@ietf.org; Tue, 22 Feb 2005 05:41:07 -0500 Received: from ams-core-1.cisco.com (144.254.224.150) by ams-iport-1.cisco.com with ESMTP; 22 Feb 2005 11:33:41 +0100 X-BrightmailFiltered: true X-Brightmail-Tracker: AAAAAA== Received: from xbh-ams-332.emea.cisco.com (xbh-ams-332.cisco.com [144.254.231.87]) by ams-core-1.cisco.com (8.12.10/8.12.6) with ESMTP id j1MAGUmU022535; Tue, 22 Feb 2005 11:17:15 +0100 (MET) Received: from xmb-ams-333.cisco.com ([144.254.231.78]) by xbh-ams-332.emea.cisco.com with Microsoft SMTPSVC(6.0.3790.0); Tue, 22 Feb 2005 11:17:14 +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: Tue, 22 Feb 2005 11:17:08 +0100 Message-ID: Thread-Topic: I-D ACTION:draft-lefaucheur-rsvp-dste-02.txt Thread-Index: AcUYx6nriNGVjsPQRA6AsynqF9TM5A== From: "Francois Le Faucheur \(flefauch\)" To: , "Jon Peterson" , X-OriginalArrivalTime: 22 Feb 2005 10:17:14.0053 (UTC) FILETIME=[ADA18750:01C518C7] X-Spam-Score: 0.0 (/) X-Scan-Signature: 21c69d3cfc2dd19218717dbe1d974352 Content-Transfer-Encoding: quoted-printable Cc: "Francois Le Faucheur \(flefauch\)" , Christou Chris , "Bruce Davie \(bdavie\)" , "GOODE, B \(Bur\), ALABS" , Davenport Michael Subject: [mpls] I-D ACTION:draft-lefaucheur-rsvp-dste-02.txt X-BeenThere: mpls@lists.ietf.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Multi-Protocol Label Switching WG List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Sender: mpls-bounces@ietf.org Errors-To: mpls-bounces@ietf.org X-Spam-Score: 0.0 (/) X-Scan-Signature: 50a516d93fd399dc60588708fd9a3002 Content-Transfer-Encoding: quoted-printable Hello, This note is to sollicit review and input from the MPLS WG on the referred draft which discusses "Aggregation of RSVP Reservations over MPLS TE/DS-TE Tunnels" and is progressed in the TSVWG. There are many similarities between "aggregation of RSVP reservations over RSVP-TE Tunnels" and "aggregation of RSVP-TE Tunnels over RSVP-TE Tunnels" (as defined in "Hierarchical LSPs" ). Hence, in response to earlier feed-back, the referred draft has been brought in close aligment with "Hierarchical LSPs" wherever possible. Broader review from the MPLS community is now sought. Thanks Francois =3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D= =3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D= =3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D =3D=3D=3D=3D=3D=3D=3D A New Internet-Draft is available from the on-line Internet-Drafts directories. Title : Aggregation of RSVP Reservations over MPLS TE/DS-TE Tunnels Author(s) : F. Le Faucheur, et al. Filename : draft-lefaucheur-rsvp-dste-02.txt Pages : 25 Date : 2005-2-14 =09 This document provides specification for aggregation of RSVP end-to- end reservations over MPLS Traffic Engineering (TE) tunnels or MPLS=20 Diffserv-aware MPLS Traffic Engineering (DS-TE) Tunnels. This=20 approach is based on RFC 3175 and simply modifies the corresponding=20 procedures for operations over MPLS TE tunnels instead of aggregated=20 RSVP reservations. This approach can be used to achieve admission=20 control of a very large number of flows in a scalable manner since=20 the devices in the core of the network are unaware of the end-to-end=20 RSVP reservations and are only aware of the MPLS TE tunnels. A URL for this Internet-Draft is: http://www.ietf.org/internet-drafts/draft-lefaucheur-rsvp-dste-02.txt _______________________________________________ mpls mailing list mpls@lists.ietf.org https://www1.ietf.org/mailman/listinfo/mpls From mpls-bounces@ietf.org Thu Feb 24 00:02:33 2005 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 AAA01258; Thu, 24 Feb 2005 00:02:32 -0500 (EST) Received: from megatron.ietf.org ([132.151.6.71]) by ietf-mx.ietf.org with esmtp (Exim 4.33) id 1D4BVr-0007ML-TM; Thu, 24 Feb 2005 00:26:12 -0500 Received: from localhost.localdomain ([127.0.0.1] helo=megatron.ietf.org) by megatron.ietf.org with esmtp (Exim 4.32) id 1D3ybf-0007t9-Br; Wed, 23 Feb 2005 10:39:19 -0500 Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org) by megatron.ietf.org with esmtp (Exim 4.32) id 1D3ybb-0007sI-So; Wed, 23 Feb 2005 10:39: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 KAA29455; Wed, 23 Feb 2005 10:39:07 -0500 (EST) Received: from penguin.ericsson.se ([193.180.251.47]) by ietf-mx.ietf.org with esmtp (Exim 4.33) id 1D3yyE-0005U4-Fs; Wed, 23 Feb 2005 11:02:39 -0500 Received: from esealmw140.al.sw.ericsson.se ([153.88.254.121]) by penguin.ericsson.se (8.12.10/8.12.10/WIREfire-1.8b) with ESMTP id j1NFd7h5015148; Wed, 23 Feb 2005 16:39:08 +0100 (MET) Received: from esealnt613.al.sw.ericsson.se ([153.88.254.125]) by esealmw140.al.sw.ericsson.se with Microsoft SMTPSVC(6.0.3790.211); Wed, 23 Feb 2005 16:39:48 +0100 Received: from [147.214.237.66] (vietas [147.214.237.66]) by esealnt613.al.sw.ericsson.se with SMTP (Microsoft Exchange Internet Mail Service Version 5.5.2657.72) id F3XNWRB3; Wed, 23 Feb 2005 16:39:07 +0100 Message-ID: <421CA39B.2050906@ericsson.com> Date: Wed, 23 Feb 2005 16:39:07 +0100 X-Sybari-Trust: b5add203 b8ec86c7 a29e4f76 00000139 From: Magnus Westerlund User-Agent: Mozilla Thunderbird 1.0 (Windows/20041206) X-Accept-Language: en-us, en MIME-Version: 1.0 To: "Ash, Gerald R \(Jerry\), ALABS" Subject: Re: [AVT] [mpls] Comments on draft-ash-avt-ecrtp-over-mpls-protocol-02.txt References: <9473683187ADC049A855ED2DA739ABCA060C874E@KCCLUST06EVS1.ugd.att.com> In-Reply-To: <9473683187ADC049A855ED2DA739ABCA060C874E@KCCLUST06EVS1.ugd.att.com> Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit X-OriginalArrivalTime: 23 Feb 2005 15:39:48.0342 (UTC) FILETIME=[E8196960:01C519BD] X-Spam-Score: 0.0 (/) X-Scan-Signature: 8b431ad66d60be2d47c7bfeb879db82c Content-Transfer-Encoding: 7bit Cc: mpls@ietf.org, rohc@ietf.org, IETF AVT WG X-BeenThere: mpls@lists.ietf.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Multi-Protocol Label Switching WG List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Sender: mpls-bounces@ietf.org Errors-To: mpls-bounces@ietf.org X-Spam-Score: 0.0 (/) X-Scan-Signature: 82c9bddb247d9ba4471160a9a865a5f3 Content-Transfer-Encoding: 7bit Hi Jerry, A few comments. 1. I think you are focus area in the CID debate is on solving the wrong problem. I think you should take one step back, and focus on what is need to solve the real problem. The real problem is in my eyes: The header compression mechanism is designed to be used over a point to point link. Where there can only be one compressor per decompressor. After an initial setup signalling, the compressor knows what it can do, like creating compression state IDs (CID). So instead of focusing and discussing the CID creation and removal, please look at how one can make the MPLS label path between compressor and decompressor look like a point to point link. Trying to use a reduction of the CID space for a compressor will result in: - Changed compressor implementations instead of simply the transport format of compressed frames. - Limitation on the capacity of the compressor - Extra signalling overhead, not normally existing over the link. Putting the compressor identify for a specific MPLS label into the layer 2.5 header that still goes above the MPLS header would not be more complex signalling wise, and avoids modifying the header compression implementations. 2. We do not need to define a complete solution for all the existing header compression mechanism, however should make it possible. And I would make it: "The MPLS HC framework must be able to use ECRTP and ROHC". And a correction on your RTP SSRC handling summary: Ash, Gerald R (Jerry), ALABS wrote: > Section 6.2.1 of RFC 3550 (RTP) discusses freeing up SSRCs after an RTCP > 'BYE' packet is received, which ends the RTP session. Section 6.3.5 > discusses how to free up SSRCs after a time-out period. This might work > for RTP flows, but how to do it for IPHC? Sending an RTCP BYE does not end the RTP session, it tells the other participants that this SSRC has left the session. That is a big difference. Cheers Magnus Westerlund Multimedia Technologies, Ericsson Research EAB/TVA/A ---------------------------------------------------------------------- Ericsson AB | Phone +46 8 4048287 Torshamsgatan 23 | Fax +46 8 7575550 S-164 80 Stockholm, Sweden | mailto: magnus.westerlund@ericsson.com _______________________________________________ mpls mailing list mpls@lists.ietf.org https://www1.ietf.org/mailman/listinfo/mpls From mpls-bounces@ietf.org Thu Feb 24 00:09:31 2005 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 AAA04000; Thu, 24 Feb 2005 00:09:31 -0500 (EST) Received: from megatron.ietf.org ([132.151.6.71]) by ietf-mx.ietf.org with esmtp (Exim 4.33) id 1D4Bcc-00088r-U5; Thu, 24 Feb 2005 00:33:11 -0500 Received: from localhost.localdomain ([127.0.0.1] helo=megatron.ietf.org) by megatron.ietf.org with esmtp (Exim 4.32) id 1D3ko8-00070h-Hq; Tue, 22 Feb 2005 19:55:16 -0500 Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org) by megatron.ietf.org with esmtp (Exim 4.32) id 1D3bAa-0004kb-HJ for mpls@megatron.ietf.org; Tue, 22 Feb 2005 09:37:48 -0500 Received: from newodin.ietf.org ([10.27.6.50]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id JAA05891 for ; Tue, 22 Feb 2005 09:37:46 -0500 (EST) Received: from apache by newodin.ietf.org with local (Exim 4.43) id 1D3bAZ-0007sN-BS; Tue, 22 Feb 2005 09:37:47 -0500 X-test-idtracker: no To: IETF-Announce From: The IESG Message-Id: Date: Tue, 22 Feb 2005 09:37:47 -0500 Cc: mpls@ietf.org Subject: [mpls] Last Call: 'Graceful Restart Mechanism for BGP with MPLS' 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: - 'Graceful Restart Mechanism for BGP with MPLS ' as a Proposed Standard The IESG plans to make a decision in the next few weeks, and solicits final comments on this action. Please send any comments to the iesg@ietf.org or ietf@ietf.org mailing lists by 2005-03-21. The file can be obtained via http://www.ietf.org/internet-drafts/draft-ietf-mpls-bgp-mpls-restart-04.txt _______________________________________________ mpls mailing list mpls@lists.ietf.org https://www1.ietf.org/mailman/listinfo/mpls From mpls-bounces@ietf.org Thu Feb 24 09:25:45 2005 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 JAA24203; Thu, 24 Feb 2005 09:25:45 -0500 (EST) Received: from megatron.ietf.org ([132.151.6.71]) by ietf-mx.ietf.org with esmtp (Exim 4.33) id 1D4KIw-00074v-MV; Thu, 24 Feb 2005 09:49:27 -0500 Received: from localhost.localdomain ([127.0.0.1] helo=megatron.ietf.org) by megatron.ietf.org with esmtp (Exim 4.32) id 1D4Jv3-0001Sw-45; Thu, 24 Feb 2005 09:24:45 -0500 Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org) by megatron.ietf.org with esmtp (Exim 4.32) id 1D4Jv1-0001Le-2E for mpls@megatron.ietf.org; Thu, 24 Feb 2005 09:24: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 JAA24066 for ; Thu, 24 Feb 2005 09:24:41 -0500 (EST) Received: from rtp-iport-1.cisco.com ([64.102.122.148]) by ietf-mx.ietf.org with esmtp (Exim 4.33) id 1D4KHu-00072X-U0 for mpls@ietf.org; Thu, 24 Feb 2005 09:48:24 -0500 Received: from rtp-core-1.cisco.com (64.102.124.12) by rtp-iport-1.cisco.com with ESMTP; 24 Feb 2005 09:38:30 -0500 X-BrightmailFiltered: true X-Brightmail-Tracker: AAAAAA== X-IronPort-AV: i="3.90,114,1107752400"; d="scan'208"; a="38214017:sNHT19647288" Received: from [10.86.240.77] (che-vpn-cluster-1-77.cisco.com [10.86.240.77]) by rtp-core-1.cisco.com (8.12.10/8.12.6) with ESMTP id j1OEOT1j008296; Thu, 24 Feb 2005 09:24:29 -0500 (EST) Message-ID: <421DE3A2.3060405@cisco.com> Date: Thu, 24 Feb 2005 09:24:34 -0500 From: Eric Osborne User-Agent: Mozilla Thunderbird 1.0 (Windows/20041206) X-Accept-Language: en-us, en MIME-Version: 1.0 To: Madhusudhan Bhadri Subject: Re: [mpls] Explicit/Implicit NULL for PHP case References: <421B6E18.9030409@pi.se> <421C7DDD.9BD752E7@lucent.com> In-Reply-To: <421C7DDD.9BD752E7@lucent.com> X-Enigmail-Version: 0.90.1.1 X-Enigmail-Supports: pgp-inline, pgp-mime Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 7bit X-Spam-Score: 0.0 (/) X-Scan-Signature: bb8f917bb6b8da28fc948aeffb74aa17 Content-Transfer-Encoding: 7bit Cc: mpls@ietf.org X-BeenThere: mpls@lists.ietf.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Multi-Protocol Label Switching WG List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Sender: mpls-bounces@ietf.org Errors-To: mpls-bounces@ietf.org X-Spam-Score: 0.0 (/) X-Scan-Signature: 7baded97d9887f7a0c7e8a33c2e3ea1b Content-Transfer-Encoding: 7bit -----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 Madhusudhan Bhadri wrote: > Hi, > If we enable explicit null along with PHP enabled for LSP creation, what should > be stamped on the data packet. Normally we will program a POP operation for a > data plane. In this case should a NULL label be stamped on the data packet. > Explicit null and PHP are mutually exclusive; PHP is the same thing as implicit-null. eric > Thanks in Advance > Madhu > --------------------- > Lucent Technologies > Bangalore > > _______________________________________________ > mpls mailing list > mpls@lists.ietf.org > https://www1.ietf.org/mailman/listinfo/mpls -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.2.1 (MingW32) iD8DBQFCHeOiYR4YGS5xhWIRAip8AJ9PDr/AXgYrCghAl7M9EnV33wMVYQCcDJ0u epns8IH1+Ns9dAkk/l77nuM= =oj+f -----END PGP SIGNATURE----- _______________________________________________ mpls mailing list mpls@lists.ietf.org https://www1.ietf.org/mailman/listinfo/mpls From mpls-bounces@ietf.org Thu Feb 24 15:38:16 2005 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 PAA17098; Thu, 24 Feb 2005 15:38:16 -0500 (EST) Received: from megatron.ietf.org ([132.151.6.71]) by ietf-mx.ietf.org with esmtp (Exim 4.33) id 1D4PkW-00032l-Jt; Thu, 24 Feb 2005 15:38:17 -0500 Received: from localhost.localdomain ([127.0.0.1] helo=megatron.ietf.org) by megatron.ietf.org with esmtp (Exim 4.32) id 1D4PbZ-00051p-T3; Thu, 24 Feb 2005 15:29:01 -0500 Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org) by megatron.ietf.org with esmtp (Exim 4.32) id 1D4PbW-00051H-Nh; Thu, 24 Feb 2005 15:29: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 PAA14209; Thu, 24 Feb 2005 15:28:56 -0500 (EST) Received: from astro.systems.pipex.net ([62.241.163.6]) by ietf-mx.ietf.org with esmtp (Exim 4.33) id 1D4PyT-00028G-Q3; Thu, 24 Feb 2005 15:52:42 -0500 Received: from dnni.com (81-178-2-190.dsl.pipex.com [81.178.2.190]) by astro.systems.pipex.net (Postfix) with ESMTP id A9799E00021A; Thu, 24 Feb 2005 20:28:47 +0000 (GMT) Received: from Puppy ([212.43.203.40] RDNS failed) by dnni.com with Microsoft SMTPSVC(6.0.3790.211); Thu, 24 Feb 2005 20:23:22 +0000 Message-ID: <105b01c51aae$e41fd410$adcb2bd4@Puppy> From: "Adrian Farrel" To: References: Date: Thu, 24 Feb 2005 18:41:09 -0000 MIME-Version: 1.0 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: 24 Feb 2005 20:23:24.0404 (UTC) FILETIME=[B0E02B40:01C51AAE] X-Spam-Score: 0.9 (/) X-Scan-Signature: e52c6009a9b39871b75233310d7f3490 Cc: mpls@ietf.org Subject: [mpls] Re: Last Call: 'Graceful Restart Mechanism for BGP with MPLS' to Proposed Standard X-BeenThere: mpls@lists.ietf.org X-Mailman-Version: 2.1.5 Precedence: list Reply-To: Adrian Farrel List-Id: Multi-Protocol Label Switching WG List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Content-Type: multipart/mixed; boundary="===============1982102863==" Sender: mpls-bounces@ietf.org Errors-To: mpls-bounces@ietf.org X-Spam-Score: 0.9 (/) X-Scan-Signature: 539f8b288ab42db633e5c7cf1c34fca1 This is a multi-part message in MIME format. --===============1982102863== Content-Type: multipart/alternative; boundary="----=_NextPart_000_103A_01C51AA0.6820B270" This is a multi-part message in MIME format. ------=_NextPart_000_103A_01C51AA0.6820B270 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: quoted-printable Hi, I am a little surprised that this I-D is in IETF last call when it is so = heavily dependent on another I-D (draft-ietf-idr-restart) that is only = in "Publication Requested" state. Should this I-D advance beyond IETF = last call and the dependent processes change we might be in a pickle. (OTOH, I am not clear why draft-ietf-idr-restart has been in its current = state for 12 months) Regards, Adrian =3D=3D=3D Might have been nice to de-nit this before issuing last call. =3D=3D=3D I think your page throws are misplaced wrt the page numbers. =3D=3D=3D My understanding is that the Abstract should not contain citations. =3D=3D=3D Section 1 In the case where a Label Switching Router (LSR) could preserve its MPLS forwarding state across restart of its control plane, and specifically its BGP component, and BGP is used to carry MPLS labels (e.g., as specified in [RFC3107]), it may be desirable not to perturb the LSPs going through that LSR (and specifically, the LSPs established by BGP) ADD after failure of or restart of the BGP component of the control = plane. =3D=3D=3D Section 1 OLD In this document, we describe a mechanism that allows to accomplish this goal. NEW In this document, we describe a mechanism that allows this goal to be accomplished. =3D=3D=3D Section 1 The mechanism described in this document is applicable to all LSRs, both those with the ability to preserve forwarding state during BGP restart and those without (although the latter need to implement only a subset of the mechanism described in this document). Supporting a subset of the mechanism described here by the LSRs that can not preserve their MPLS forwarding state across the restart would not reduce the negative impact on MPLS traffic caused by their control plane restart, but it would minimize the impact if their neighbor(s) are capable of preserving the forwarding state across the restart of their control plane and implement the mechanism described here. The subset includes all the procedures described in this document, except the procedures in Sections 4.1, 4.2, 4.3, 5, and 6. Section 6 describes procedures at the LSR adjacent to the restarting = LSR. This paragraph implies that "the LSRs that can not preserve their = MPLS forwarding state across restart" do not have to support the = procedures in section 6. This seems like a disconnect. =3D=3D=3D Section 2 OLD to create new label> bindings after restart, while temporary maintaining MPLS forwarding state corresponds to both the bindings NEW to create new label> bindings after restart, while = temporarily = ^^^ maintaining MPLS forwarding state corresponding to both the bindings =3D=3D=3D ^^^ Section 4 OLD Procedures in this section applies when a restarting LSR is able to NEW Procedures in this section apply when a restarting LSR is able to ^ =3D=3D=3D=20 Section 4.3 OLD not allocate label for that route. NEW not allocate a label for that route. ^ =3D=3D=3D Section 5 OLD restart, while temporary maintaining MPLS forwarding state NEW restart, while temporarily maintaining MPLS forwarding state ^^ =3D=3D=3D Section 5 OLD The procedures described in this section requires that for the use by NEW The procedures described in this section require that for the use by ^ =3D=3D=3D Section 5 The LSR MAY retain the forwarding state even a bit longer (the amount of extra time MAY be controlled by configuration on the LSR), as to allow the neighbors to receive and process the routes that have been advertised by the LSR. After that, the LSR MAY delete the MPLS forwarding state that it preserved across the restart. What do you mean "MAY delete". You mean that deletion is optional and an = implementation would normally continue to retain this state? =3D=3D=3D Section 6 To minimize the potential mis-routing caused by the label change, when creating a new binding the LSR SHOULD pick up the least recently used label. Once an LSR releases a label, the LSR SHALL NOT re-use this label for advertising a binding to a neighbor that supports graceful restart for at least the Restart Time, as advertised by the neighbor to the LSR. 1. The "SHOULD pick up the least recently used label" seems extreme to me. It is surely enough to use any label that has not been used for at least the Restart Time. 2. "Once an LSR releases a label, the LSR SHALL NOT..."=20 Are we to assume that this applies to *ANY* label release (as the text implies) or only to labels released during restart processing? I think the former, and it would be very helpful (important) to = stress this at this point in the text. =3D=3D=3D Section 8 OLD In addition, the mechanism described here renders LSRs that implement it to additional denial-of-service attacks as follows: NEW In addition, the mechanism described here renders LSRs that implement it vulnerable to additional denial-of-service attacks as follows: ^^^^^^^^^^^ =3D=3D=3D Section 12 [1] "Graceful Restart Mechanism for BGP", draft-ietf-idr- restart-01.txt This has moved on one or two revisions. Suggest you strike the version = number. ----- Original Message -----=20 From: "The IESG" To: "IETF-Announce" Cc: Sent: Tuesday, February 22, 2005 2:37 PM Subject: Last Call: 'Graceful Restart Mechanism for BGP with MPLS' to = Proposed Standard=20 > The IESG has received a request from the Multiprotocol Label Switching = WG to=20 > consider the following document: >=20 > - 'Graceful Restart Mechanism for BGP with MPLS ' > as a Proposed Standard >=20 > The IESG plans to make a decision in the next few weeks, and solicits > final comments on this action. Please send any comments to the > iesg@ietf.org or ietf@ietf.org mailing lists by 2005-03-21. >=20 > The file can be obtained via > = http://www.ietf.org/internet-drafts/draft-ietf-mpls-bgp-mpls-restart-04.t= xt >=20 >=20 > _______________________________________________ > IETF-Announce mailing list > IETF-Announce@ietf.org > https://www1.ietf.org/mailman/listinfo/ietf-announce >=20 > ------=_NextPart_000_103A_01C51AA0.6820B270 Content-Type: text/html; charset="iso-8859-1" Content-Transfer-Encoding: quoted-printable
Hi,
 
I am a little surprised that this I-D = is in IETF=20 last call when it is so heavily dependent on another I-D=20 (draft-ietf-idr-restart) that is only in "Publication Requested" state. = Should=20 this I-D advance beyond IETF last call and the dependent processes = change we=20 might be in a pickle.
 
(OTOH, I am not clear why = draft-ietf-idr-restart=20 has been in its current state for 12 months)
 
Regards,
Adrian
 
=3D=3D=3D
Might have been nice to de-nit this = before=20 issuing last call.
=3D=3D=3D
I think your page throws are = misplaced wrt the=20 page numbers.
=3D=3D=3D
My understanding is that the Abstract = should not=20 contain citations.
=3D=3D=3D
Section 1
   In the case where a = Label Switching=20 Router (LSR) could preserve its
   MPLS forwarding state = across=20 restart of its control plane, and
   specifically its BGP=20 component, and BGP is used to carry MPLS labels
   (e.g., = as=20 specified in [RFC3107]), it may be desirable not to = perturb
   the=20 LSPs going through that LSR (and specifically, the LSPs
  =20 established by BGP)
ADD
   after failure of or = restart of the=20 BGP component of the control plane.
=3D=3D=3D
Section 1
OLD
   In this document, we = describe a=20 mechanism that
   allows to accomplish this = goal.
NEW
   In this document, we = describe a=20 mechanism that
   allows this goal to be=20 accomplished.
=3D=3D=3D
Section 1
   The mechanism described = in this=20 document is applicable to all LSRs,
   both those with the = ability=20 to preserve forwarding state during BGP
   restart and = those=20 without (although the latter need to implement only
   a = subset of=20 the mechanism described in this document).  Supporting = a
  =20 subset of the mechanism described here by the LSRs that can = not
  =20 preserve their MPLS forwarding state across the restart would=20 not
   reduce the negative impact on MPLS traffic caused by = their=20 control
   plane restart, but it would minimize the impact = if their=20 neighbor(s)
   are capable of preserving the forwarding = state=20 across the restart of
   their control plane and implement = the=20 mechanism described here.  The
   subset includes all = the=20 procedures described in this document, except
   the = procedures in=20 Sections 4.1, 4.2, 4.3, 5, and 6.
Section 6 describes procedures at the = LSR=20 adjacent to the restarting LSR. This paragraph implies that "the LSRs = that can=20 not preserve their MPLS forwarding state across restart" do not have to = support=20 the procedures in section 6. This seems like a disconnect.
=3D=3D=3D
Section 2
OLD
   to create new <FEC = ->=20 label> bindings after restart, while temporary
   maintaining MPLS = forwarding state=20 corresponds to both the bindings
NEW
   to create new <FEC = ->=20 label> bindings after restart, while temporarily
          &nbs= p;            = ;            =             &= nbsp;           &n= bsp;          ^^^
&n= bsp; =20 maintaining MPLS forwarding state corresponding to both the=20 bindings
=3D=3D=3D        &nbs= p;            = ;            =             &= nbsp;=20 ^^^
Section 4
OLD
   Procedures in this = section applies=20 when a restarting LSR is able to
NEW
   Procedures in this = section apply=20 when a restarting LSR is able to
          &nbs= p;            = ;          =20 ^
=3D=3D=3D
Section 4.3
OLD
   not allocate label for = that=20 route.
NEW
   not allocate a label for = that=20 route.
          &nb= sp;     ^
=3D=3D=3D
Section 5
OLD
   restart, while temporary = maintaining=20 MPLS forwarding state
NEW
   restart, while = temporarily=20 maintaining MPLS forwarding state
          &nbs= p;            = ;   ^^
=3D=3D=3D
Section 5
OLD
   The procedures described = in this=20 section requires that for the use by
NEW
   The procedures described = in this=20 section require that for the use by
          &nbs= p;            = ;            =             &= nbsp;  =20 ^
=3D=3D=3D
Section 5
   The LSR MAY retain the = forwarding=20 state
   even a bit longer (the amount of extra time MAY be = controlled by
   configuration on the LSR), as to allow the = neighbors to receive and
   process the routes that have = been=20 advertised by the LSR. After that,
   the LSR MAY delete = the MPLS=20 forwarding state that it preserved across
   the=20 restart.
What do you mean "MAY delete". You = mean that=20 deletion is optional and an implementation would normally continue = to=20 retain this state?
=3D=3D=3D
Section 6
   To minimize the = potential=20 mis-routing caused by the label change,
   when creating a = new=20 <label, FEC> binding the LSR SHOULD pick up the
   = least=20 recently used label. Once an LSR releases a label, the = LSR
   SHALL=20 NOT re-use this label for advertising a <label, FEC> binding=20 to
   a neighbor that supports graceful restart for at = least the=20 Restart
   Time, as advertised by the neighbor to the = LSR.
1.=20 The "SHOULD pick up the least recently used label" seems extreme = to
   me. It is surely enough = to use any=20 label that has not been used for
   at least the Restart=20 Time.
2. "Once an LSR releases a label, the = LSR SHALL=20 NOT..."
   Are we to assume that = this applies=20 to *ANY* label release (as the
   text implies) or only to = labels=20 released during restart processing?
   I think the former, and = it would be=20 very helpful (important) to stress
   this at this point in = the=20 text.
=3D=3D=3D
Section 8
OLD
   In addition, the = mechanism described=20 here renders LSRs that implement
   it to additional=20 denial-of-service attacks as follows:
NEW
   In addition, the = mechanism described=20 here renders LSRs that implement
   it vulnerable to = additional=20 denial-of-service attacks as follows:
     =20 ^^^^^^^^^^^
=3D=3D=3D
Section 12
   [1] "Graceful Restart = Mechanism for=20 BGP", draft-ietf-idr-
   restart-01.txt
This has moved = on one or=20 two revisions. Suggest you strike the version number.
 
 
 
 
----- Original Message -----
From: "The IESG" <iesg-secretary@ietf.org>
To: "IETF-Announce" <ietf-announce@ietf.org>
Cc: <mpls@ietf.org>
Sent: Tuesday, February 22, 2005 2:37 = PM
Subject: Last Call: 'Graceful Restart = Mechanism=20 for BGP with MPLS' to Proposed Standard

> The IESG has received a request from the Multiprotocol = Label=20 Switching WG to
> consider the following document:
> =
> -=20 'Graceful Restart Mechanism for BGP with MPLS '
>   =20 <draft-ietf-mpls-bgp-mpls-restart-04.txt> as a Proposed = Standard
>=20
> The IESG plans to make a decision in the next few weeks, and=20 solicits
> final comments on this action.  Please send any = comments=20 to the
> iesg@ietf.org or = ietf@ietf.org mailing = lists by=20 2005-03-21.
>
> The file can be obtained via
> = http://www.ietf.org/internet-drafts/draft-ietf-mpls-bgp-mpls-res= tart-04.txt
>
>
>=20 _______________________________________________
> IETF-Announce = mailing=20 list
> IETF-Announce@ietf.org
>=20 https://www1.ietf.org/mailman/listinfo/ietf-announce<= BR>>
> ------=_NextPart_000_103A_01C51AA0.6820B270-- --===============1982102863== 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 --===============1982102863==-- From mpls-bounces@ietf.org Thu Feb 24 18:25:15 2005 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 SAA07062; Thu, 24 Feb 2005 18:25:15 -0500 (EST) Received: from megatron.ietf.org ([132.151.6.71]) by ietf-mx.ietf.org with esmtp (Exim 4.33) id 1D4SM8-0007qK-IQ; Thu, 24 Feb 2005 18:25:19 -0500 Received: from localhost.localdomain ([127.0.0.1] helo=megatron.ietf.org) by megatron.ietf.org with esmtp (Exim 4.32) id 1D4SJP-00012x-0h; Thu, 24 Feb 2005 18:22:27 -0500 Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org) by megatron.ietf.org with esmtp (Exim 4.32) id 1D4SJM-00012g-VA; Thu, 24 Feb 2005 18:22:24 -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 SAA06742; Thu, 24 Feb 2005 18:22:21 -0500 (EST) Received: from mail-dark.research.att.com ([192.20.225.112] helo=mail-yellow.research.att.com) by ietf-mx.ietf.org with esmtp (Exim 4.33) id 1D4SJM-0007kq-Qi; Thu, 24 Feb 2005 18:22:26 -0500 Received: from bright.research.att.com (bright.research.att.com [135.207.20.189]) by mail-green.research.att.com (Postfix) with ESMTP id 8FBEAA7BCA; Thu, 24 Feb 2005 18:22:11 -0500 (EST) Received: (from fenner@localhost) by bright.research.att.com (8.12.11/8.12.10/Submit) id j1ONMBkx007545; Thu, 24 Feb 2005 15:22:11 -0800 Message-Id: <200502242322.j1ONMBkx007545@bright.research.att.com> MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII To: adrian@olddog.co.uk References: <105b01c51aae$e41fd410$adcb2bd4@Puppy> Date: Thu, 24 Feb 2005 15:22:11 -0800 From: Bill Fenner Versions: dmail (linux) 2.6d/makemail 2.10 X-Spam-Score: 0.0 (/) X-Scan-Signature: 30ac594df0e66ffa5a93eb4c48bcb014 Cc: mpls@ietf.org, iesg@ietf.org Subject: [mpls] Re: Last Call: 'Graceful Restart Mechanism for BGP with MPLS' to Proposed Standard 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: 1ac7cc0a4cd376402b85bc1961a86ac2 Ouch. I only count 8 months, but you're right, this kind of delay is unacceptable. Much of the delay is because we refused to progress any idr documents until the base spec was done; now that the base spec is done I need to get cracking on helping things to progress. Bill _______________________________________________ mpls mailing list mpls@lists.ietf.org https://www1.ietf.org/mailman/listinfo/mpls From mpls-bounces@ietf.org Fri Feb 25 00:43:02 2005 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 AAA10109; Fri, 25 Feb 2005 00:43:02 -0500 (EST) Received: from megatron.ietf.org ([132.151.6.71]) by ietf-mx.ietf.org with esmtp (Exim 4.33) id 1D4YFo-0007bV-Iy; Fri, 25 Feb 2005 00:43:09 -0500 Received: from localhost.localdomain ([127.0.0.1] helo=megatron.ietf.org) by megatron.ietf.org with esmtp (Exim 4.32) id 1D4YD2-0005rc-7P; Fri, 25 Feb 2005 00:40:16 -0500 Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org) by megatron.ietf.org with esmtp (Exim 4.32) id 1D4YCj-0005pr-QF; Fri, 25 Feb 2005 00:39:58 -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 AAA09756; Fri, 25 Feb 2005 00:39:54 -0500 (EST) Received: from mail-red.research.att.com ([192.20.225.110] helo=mail-white.research.att.com) by ietf-mx.ietf.org with esmtp (Exim 4.33) id 1D4YCm-0007Wv-Oz; Fri, 25 Feb 2005 00:40:02 -0500 Received: from bright.research.att.com (bright.research.att.com [135.207.20.189]) by mail-blue.research.att.com (Postfix) with ESMTP id B68B31974E0; Fri, 25 Feb 2005 00:22:18 -0500 (EST) Received: (from fenner@localhost) by bright.research.att.com (8.12.11/8.12.10/Submit) id j1P5dliu018627; Thu, 24 Feb 2005 21:39:47 -0800 Message-Id: <200502250539.j1P5dliu018627@bright.research.att.com> MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII To: routing-discussion@ietf.org, mpls@ietf.org, ccamp@ops.ietf.org Date: Thu, 24 Feb 2005 21:39:47 -0800 From: Bill Fenner Versions: dmail (linux) 2.6d/makemail 2.10 X-Spam-Score: 0.0 (/) X-Scan-Signature: 34d35111647d654d033d58d318c0d21a Subject: [mpls] MPLS/GMPLS Change Process X-BeenThere: mpls@lists.ietf.org X-Mailman-Version: 2.1.5 Precedence: list Reply-To: routing-discussion@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: e1b0e72ff1bbd457ceef31828f216a86 We expect to talk about the MPLS/GMPLS Change Process at the Routing Area meeting in Minneapolis. The main changes from the -00 version are the addition of the preliminary process which doesn't require an I-D and additional mentions of where liaisons fit in the process. Let's please discuss this on the routing-discussion list, instead of trying to use both ccamp and mpls lists. Bill ----- Begin forwarded message: From: Internet-Drafts@ietf.org Subject: I-D ACTION:draft-andersson-rtg-gmpls-change-01.txt Date: Tue, 22 Feb 2005 15:50:01 -0500 To: i-d-announce@ietf.org Reply-to: internet-drafts@ietf.org Title : MPLS and GMPLS Change Process Author(s) : L. Andersson, et al. Filename : draft-andersson-rtg-gmpls-change-01.txt Pages : 23 Date : 2005-2-22 The MPLS and GMPLS protocol suites have become quite popular for a growing number of applications and deployment scenarios. One result of this popularity is a large number of suggestions for modifications and extensions. The IETF needs to be flexible and responsive in how it handles these suggestions, and has a responsiblity to supervise the growth and evolution of MPLS and GMPLS protocols. This memo describes the process through which individuals, working groups and external standards bodies can influence the development of the MPLS and GMPLS standards. This process means that extensions and changes to protocols specified by these working groups can only be made through the IETF, the body that created the (G)MPLS ((Generalized) Multiprotocol Label Switching) technologies. When possible, existing liaison relationships are used. A URL for this Internet-Draft is: http://www.ietf.org/internet-drafts/draft-andersson-rtg-gmpls-change-01.txt To remove yourself from the I-D Announcement list, send a message to i-d-announce-request@ietf.org with the word unsubscribe in the body of the message. You can also visit https://www1.ietf.org/mailman/listinfo/I-D-announce to change your subscription settings. Internet-Drafts are also available by anonymous FTP. Login with the username "anonymous" and a password of your e-mail address. After logging in, type "cd internet-drafts" and then "get draft-andersson-rtg-gmpls-change-01.txt". A list of Internet-Drafts directories can be found in http://www.ietf.org/shadow.html or ftp://ftp.ietf.org/ietf/1shadow-sites.txt Internet-Drafts can also be obtained by e-mail. Send a message to: mailserv@ietf.org. In the body type: "FILE /internet-drafts/draft-andersson-rtg-gmpls-change-01.txt". NOTE: The mail server at ietf.org can return the document in MIME-encoded form by using the "mpack" utility. To use this feature, insert the command "ENCODING mime" before the "FILE" command. To decode the response(s), you will need "munpack" or a MIME-compliant mail reader. Different MIME-compliant mail readers exhibit different behavior, especially when dealing with "multipart" MIME messages (i.e. documents which have been split up into multiple messages), so check your local documentation on how to manipulate these messages. Below is the data which will enable a MIME compliant mail reader implementation to automatically retrieve the ASCII version of the Internet-Draft. [Don't know how to fetch mail-server a3] _______________________________________________ I-D-Announce mailing list I-D-Announce@ietf.org https://www1.ietf.org/mailman/listinfo/i-d-announce ----- End forwarded message: _______________________________________________ mpls mailing list mpls@lists.ietf.org https://www1.ietf.org/mailman/listinfo/mpls From mpls-bounces@ietf.org Fri Feb 25 05:03:31 2005 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 FAA24696; Fri, 25 Feb 2005 05:03:31 -0500 (EST) Received: from megatron.ietf.org ([132.151.6.71]) by ietf-mx.ietf.org with esmtp (Exim 4.33) id 1D4cJw-0004bx-Js; Fri, 25 Feb 2005 05:03:40 -0500 Received: from localhost.localdomain ([127.0.0.1] helo=megatron.ietf.org) by megatron.ietf.org with esmtp (Exim 4.32) id 1D4cI3-0005bg-0j; Fri, 25 Feb 2005 05:01:43 -0500 Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org) by megatron.ietf.org with esmtp (Exim 4.32) id 1D4cI1-0005bY-2O for mpls@megatron.ietf.org; Fri, 25 Feb 2005 05: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 FAA24510 for ; Fri, 25 Feb 2005 05:01:38 -0500 (EST) Received: from hoemail2.lucent.com ([192.11.226.163]) by ietf-mx.ietf.org with esmtp (Exim 4.33) id 1D4cI6-0004Z1-KD for mpls@ietf.org; Fri, 25 Feb 2005 05:01:47 -0500 Received: from ii0015exch002u.wins.lucent.com (h135-254-246-205.lucent.com [135.254.246.205]) by hoemail2.lucent.com (8.12.11/8.12.11) with ESMTP id j1PA1Zi1012458 for ; Fri, 25 Feb 2005 04:01:37 -0600 (CST) Received: by ii0015exch002u.iprc.lucent.com with Internet Mail Service (5.5.2657.72) id <1TWC3X1F>; Fri, 25 Feb 2005 15:31:34 +0530 Message-ID: <6733C768256DEC42A72BAFEFA9CF06D212487FF2@ii0015exch002u.iprc.lucent.com> From: "Agiwal, Manoj (Manoj)" To: "'mpls@ietf.org'" Date: Fri, 25 Feb 2005 15:31:32 +0530 MIME-Version: 1.0 X-Mailer: Internet Mail Service (5.5.2657.72) Content-Type: text/plain; charset="iso-8859-1" X-Spam-Score: 0.0 (/) X-Scan-Signature: 30ac594df0e66ffa5a93eb4c48bcb014 Subject: [mpls] LSP ping query 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: 1ac7cc0a4cd376402b85bc1961a86ac2 Hi , Is it possible to run trace route and LSP ping functionality on PSN tunnels alone , which are supposed to carrying pseudowires and VPN IPV4 information. This would require to send LSP ping packet with a single mpls shim label on the data path , even though the edge nodes have been programmed for two label stacks . Manoj _______________________________________________ mpls mailing list mpls@lists.ietf.org https://www1.ietf.org/mailman/listinfo/mpls From mpls-bounces@ietf.org Fri Feb 25 07:33:07 2005 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 HAA08274; Fri, 25 Feb 2005 07:33:07 -0500 (EST) Received: from megatron.ietf.org ([132.151.6.71]) by ietf-mx.ietf.org with esmtp (Exim 4.33) id 1D4eeh-0007hO-Ot; Fri, 25 Feb 2005 07:33:16 -0500 Received: from localhost.localdomain ([127.0.0.1] helo=megatron.ietf.org) by megatron.ietf.org with esmtp (Exim 4.32) id 1D4ecC-0008Vq-VL; Fri, 25 Feb 2005 07:30:40 -0500 Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org) by megatron.ietf.org with esmtp (Exim 4.32) id 1D4ecA-0008Ir-ND for mpls@megatron.ietf.org; Fri, 25 Feb 2005 07:30: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 HAA07590 for ; Fri, 25 Feb 2005 07:30:36 -0500 (EST) Received: from zrtps0kp.nortelnetworks.com ([47.140.192.56]) by ietf-mx.ietf.org with esmtp (Exim 4.33) id 1D4ecF-0007XU-8l for mpls@ietf.org; Fri, 25 Feb 2005 07:30:43 -0500 Received: from zrtpd0jn.us.nortel.com (zrtpd0jn.us.nortel.com [47.140.202.35]) by zrtps0kp.nortelnetworks.com (Switch-2.2.6/Switch-2.2.0) with ESMTP id j1PCUNd03520 for ; Fri, 25 Feb 2005 07:30:23 -0500 (EST) Received: by zrtpd0jn.us.nortel.com with Internet Mail Service (5.5.2653.19) id <1JJLR012>; Fri, 25 Feb 2005 07:30:24 -0500 Message-ID: <87AC5F88F03E6249AEA68D40BD3E00BE03192D8C@zcarhxm2.corp.nortel.com> From: "David Allan" To: "'Agiwal, Manoj (Manoj)'" , "'mpls@ietf.org'" Subject: RE: [mpls] LSP ping query Date: Fri, 25 Feb 2005 07:30:19 -0500 X-Mailer: Internet Mail Service (5.5.2653.19) X-Spam-Score: 0.0 (/) X-Scan-Signature: b19722fc8d3865b147c75ae2495625f2 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: 69a74e02bbee44ab4f8eafdbcedd94a1 Hi Manoj: Yes, not a problem, except that you can only do a tree trace of the paths that your PWs and VPN PDUs MAY follow if you are using ECMP... cheers Dave > -----Original Message----- > From: mpls-bounces@lists.ietf.org > [mailto:mpls-bounces@lists.ietf.org] On Behalf Of Agiwal, > Manoj (Manoj) > Sent: Friday, February 25, 2005 5:02 AM > To: 'mpls@ietf.org' > Subject: [mpls] LSP ping query > > > Hi , > Is it possible to run trace route and LSP ping > functionality on PSN tunnels alone , which are supposed to > carrying pseudowires and VPN IPV4 information. > This would require to send LSP ping packet with a > single mpls shim label on the data path , even though the > edge nodes have been programmed for two label > stacks . > Manoj > > _______________________________________________ > 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 Feb 25 08:17:07 2005 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 IAA12289; Fri, 25 Feb 2005 08:17:07 -0500 (EST) Received: from megatron.ietf.org ([132.151.6.71]) by ietf-mx.ietf.org with esmtp (Exim 4.33) id 1D4fLI-0000KK-Gp; Fri, 25 Feb 2005 08:17:17 -0500 Received: from localhost.localdomain ([127.0.0.1] helo=megatron.ietf.org) by megatron.ietf.org with esmtp (Exim 4.32) id 1D4fI1-0006S2-NQ; Fri, 25 Feb 2005 08:13:53 -0500 Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org) by megatron.ietf.org with esmtp (Exim 4.32) id 1D4fI0-0006PA-3L for mpls@megatron.ietf.org; Fri, 25 Feb 2005 08:13:52 -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 IAA11965 for ; Fri, 25 Feb 2005 08:13:50 -0500 (EST) Received: from kanfw1.ottawa.alcatel.ca ([192.75.23.69] helo=tm3.ca.alcatel.com) by ietf-mx.ietf.org with esmtp (Exim 4.33) id 1D4fI6-0000Gj-Na for mpls@ietf.org; Fri, 25 Feb 2005 08:14:00 -0500 Received: from alcatel.com (localhost [127.0.0.1]) by tm3.ca.alcatel.com (8.13.0/8.13.0) with ESMTP id j1PDDhVZ009674; Fri, 25 Feb 2005 08:13:47 -0500 (EST) Message-ID: <421F2486.6ADD396B@alcatel.com> Date: Fri, 25 Feb 2005 08:13:42 -0500 From: Gatot Susilo Organization: Alcatel Canada X-Mailer: Mozilla 4.79 [en] (Windows NT 5.0; U) X-Accept-Language: en MIME-Version: 1.0 To: "Agiwal, Manoj (Manoj)" Subject: Re: [mpls] LSP ping query References: <6733C768256DEC42A72BAFEFA9CF06D212487FF2@ii0015exch002u.iprc.lucent.com> Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit X-Spam-Score: 0.0 (/) X-Scan-Signature: 9182cfff02fae4f1b6e9349e01d62f32 Content-Transfer-Encoding: 7bit Cc: "'mpls@ietf.org'" X-BeenThere: mpls@lists.ietf.org X-Mailman-Version: 2.1.5 Precedence: list Reply-To: gatot.susilo@alcatel.com 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: ea4ac80f790299f943f0a53be7e1a21a Content-Transfer-Encoding: 7bit Yes, I would think so. The tunnel is just like another LSP. Say you use RSVP-TE as your tunnel. Then your MPLS echo message would contain 1 label and 1 RSVP-TE FEC. It should be noted that label operation is treated individually. In this case, the tunnel label will have operation "pop and continue processing". /Gatot "Agiwal, Manoj (Manoj)" wrote: > Hi , > Is it possible to run trace route and LSP ping functionality on PSN > tunnels alone , which are supposed to carrying pseudowires and VPN IPV4 > information. > This would require to send LSP ping packet with a single mpls shim > label on the data path , even though the edge nodes have been programmed for > two label > stacks . > Manoj > > _______________________________________________ > 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 Feb 25 09:55:29 2005 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 JAA22631; Fri, 25 Feb 2005 09:55:28 -0500 (EST) Received: from megatron.ietf.org ([132.151.6.71]) by ietf-mx.ietf.org with esmtp (Exim 4.33) id 1D4gsW-0002gP-5M; Fri, 25 Feb 2005 09:55:40 -0500 Received: from localhost.localdomain ([127.0.0.1] helo=megatron.ietf.org) by megatron.ietf.org with esmtp (Exim 4.32) id 1D4gpo-0007Iz-Vx; Fri, 25 Feb 2005 09:52:52 -0500 Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org) by megatron.ietf.org with esmtp (Exim 4.32) id 1D4gpn-0007In-F8 for mpls@megatron.ietf.org; Fri, 25 Feb 2005 09:52: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 JAA22414 for ; Fri, 25 Feb 2005 09:52:49 -0500 (EST) Received: from sj-iport-3-in.cisco.com ([171.71.176.72] helo=sj-iport-3.cisco.com) by ietf-mx.ietf.org with esmtp (Exim 4.33) id 1D4gpv-0002dT-GD for mpls@ietf.org; Fri, 25 Feb 2005 09:53:00 -0500 Received: from sj-core-1.cisco.com (171.71.177.237) by sj-iport-3.cisco.com with ESMTP; 25 Feb 2005 08:06:58 +0000 X-BrightmailFiltered: true X-Brightmail-Tracker: AAAAAA== X-IronPort-AV: i="3.90,117,1107734400"; d="scan'208"; a="229224414:sNHT94839372" Received: from flask.cisco.com (IDENT:mirapoint@flask.cisco.com [161.44.122.62]) by sj-core-1.cisco.com (8.12.10/8.12.6) with ESMTP id j1PEq1uC005200; Fri, 25 Feb 2005 06:52:01 -0800 (PST) Received: from [192.168.1.100] (che-vpn-cluster-1-214.cisco.com [10.86.240.214]) by flask.cisco.com (MOS 3.4.6-GR) with ESMTP id APJ85717; Fri, 25 Feb 2005 09:52:02 -0500 (EST) In-Reply-To: <6733C768256DEC42A72BAFEFA9CF06D212487FF2@ii0015exch002u.iprc.lucent.com> References: <6733C768256DEC42A72BAFEFA9CF06D212487FF2@ii0015exch002u.iprc.lucent.com> Mime-Version: 1.0 (Apple Message framework v619.2) Content-Type: text/plain; charset=US-ASCII; format=flowed Message-Id: <32379d15029f90ed5284f0cf2c5de0b3@cisco.com> Content-Transfer-Encoding: 7bit From: "Thomas D. Nadeau" Subject: Re: [mpls] LSP ping query Date: Fri, 25 Feb 2005 09:52:01 -0500 To: "Agiwal, Manoj (Manoj)" X-Mailer: Apple Mail (2.619.2) X-Spam-Score: 0.0 (/) X-Scan-Signature: 2409bba43e9c8d580670fda8b695204a Content-Transfer-Encoding: 7bit Cc: "'mpls@ietf.org'" X-BeenThere: mpls@lists.ietf.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Multi-Protocol Label Switching WG List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Sender: mpls-bounces@ietf.org Errors-To: mpls-bounces@ietf.org X-Spam-Score: 0.0 (/) X-Scan-Signature: 8abaac9e10c826e8252866cbe6766464 Content-Transfer-Encoding: 7bit > Hi , > Is it possible to run trace route and LSP ping functionality > on PSN > tunnels alone , which are supposed to carrying pseudowires and VPN IPV4 > information. If by "PSN tunnels" you mean MPLS LSPs that attach PEs, then certainly you could. Of course, this is true as long as there is a FEC binding for the label that is bound to that route(s). --Tom > This would require to send LSP ping packet with a single mpls > shim > label on the data path , even though the edge nodes have been > programmed for > two label > stacks . > Manoj > > _______________________________________________ > 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 Feb 25 12:39:28 2005 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 MAA11572; Fri, 25 Feb 2005 12:39:28 -0500 (EST) Received: from megatron.ietf.org ([132.151.6.71]) by ietf-mx.ietf.org with esmtp (Exim 4.33) id 1D4jRF-00072b-Jp; Fri, 25 Feb 2005 12:39:41 -0500 Received: from localhost.localdomain ([127.0.0.1] helo=megatron.ietf.org) by megatron.ietf.org with esmtp (Exim 4.32) id 1D4jPA-0002EW-JM; Fri, 25 Feb 2005 12:37:32 -0500 Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org) by megatron.ietf.org with esmtp (Exim 4.32) id 1D4jP8-0002EB-G4 for mpls@megatron.ietf.org; Fri, 25 Feb 2005 12:37:30 -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 MAA11449 for ; Fri, 25 Feb 2005 12:37:27 -0500 (EST) Received: from kanfw1.ottawa.alcatel.ca ([192.75.23.69] helo=tm1.ca.alcatel.com) by ietf-mx.ietf.org with esmtp (Exim 4.33) id 1D4jPI-00070D-Hp for mpls@ietf.org; Fri, 25 Feb 2005 12:37:40 -0500 Received: from alcatel.com (localhost [127.0.0.1]) by tm1.ca.alcatel.com (8.13.0/8.13.0) with ESMTP id j1PHbQFV008208; Fri, 25 Feb 2005 12:37:26 -0500 (EST) Message-ID: <421F6255.4A8FCC56@alcatel.com> Date: Fri, 25 Feb 2005 12:37:25 -0500 From: Gatot Susilo Organization: Alcatel Canada X-Mailer: Mozilla 4.79 [en] (Windows NT 5.0; U) X-Accept-Language: en MIME-Version: 1.0 To: kireeti@juniper.net, swallow@cisco.com Subject: Re: [mpls] I-D ACTION:draft-ietf-mpls-lsp-ping-08.txt References: <200502222105.QAA21488@ietf.org> X-Spam-Score: 0.6 (/) X-Scan-Signature: 34d35111647d654d033d58d318c0d21a Cc: mpls@ietf.org X-BeenThere: mpls@lists.ietf.org X-Mailman-Version: 2.1.5 Precedence: list Reply-To: gatot.susilo@alcatel.com List-Id: Multi-Protocol Label Switching WG List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Content-Type: multipart/mixed; boundary="===============0902470740==" Sender: mpls-bounces@ietf.org Errors-To: mpls-bounces@ietf.org X-Spam-Score: 0.5 (/) X-Scan-Signature: 2857c5c041d6c02d7181d602c22822c8 --===============0902470740== Content-Type: text/html; charset=us-ascii Content-Transfer-Encoding: 7bit Hi,
I would like to have some comments/questions to the draft.
1/ Mandatory/Optional TLVs.
I would think this is applicable only for top level TLVs. Am I wrong ?
This should be made clear in the draft. Moreover, throughout draft not all top level TLVs are explicitly stated whether the TLV is mandatory or optional. Summarizing whether the TLV is mandatory/optional along with the TLV list will make it less ambiguity/error-prone. Therefore, I would like to propose some text changes:
In the section 3:
"A description of the Type and Values of level TLVs of LSP Ping ..."
until the end of section, should be replaced as follows:

"A description of the Types and Values of top level TLVs for LSP Ping are given below:
    Type #  Type  Value Field
    ------  ----  -----------
         1     M  Target FEC Stack
         2     O  Downstream Mapping
         3     M  Pad
         4     O  Error Code
         5     O  Vendor Enterprise Code
         6     O  TBD
         7     O  IPv4 Interface and Label Stack Object
         8     O  IPv6 Interface and Label Stack Object
         9     O  Errored TLVs
        10     O  Reply TOS Byte

(M) These are mandatory TLVs. The high order bit of Type field
    MUST be set to 0, which yields types less than 32768.
    These TLVs MUST either be supported by an implementation or result
    in the return code of 2 ("One or more of the TLVs was not
    understood" being sent in the echo response").

(O) These are optional TLVs. The high order bit of Type field
    MUST be set to 1, which yields types greater than or equal to 32768.
    These TLVs SHOULD be ignored if the implementation does not
    understand or support them.
"

2/ IPv4/IPv6 Interface and Label Stack Object
Section 3.7.1 and 3.7.2 indicates that the downstream interface addess may be set to either the downstream LSR's interface address or the index assigned by the downstream LSR to the interface when address type is IPv4/IPv6 or unnumbered respectively. When the originating node receives the MPLS echo reply, the originating node will not be able to tell what the downstream LSR has set to the downstream interface address field. In this case, I would like to propose that "Address Type" field should be added in these TLVs. This is similar to the downstream mapping TLV of which "Address Type" is explicitly specified.

3/ Typo on length of CR-LDP FEC
Appendix A.1 indicates that the length of CR-LDP FEC is 6 instead of 8.

4/ Non-Compliant Routers
In section 4.8, it mentioned about ALLROUTERs multicast address. What is the value ?
Moreover, why do we need to set "Validate FEC Stack" flag to 0?  I would think that we can continue validating FEC stack. The only thing that we can skip is validating the downstream mapping TLV. So I would propose that:
When the downstream IP address field is set to ALLROUTERs multicast address, the downstream mapping tlv MUST not be validated. The FEC stack SHOULD be validated as if the downstream mapping tlv is not present.

5/ Section 7.2 TLVs (i.e. overlapping value with optional TLVs)
Snipet from section 7.2:
"It is requested that IANA maintain registries for the Type field of top-level TLV as well as for sub-TLVs. The valid range for each of these is 0-65535"

As mentioned in the section 3, the high order bit of Type field is used to indicate whether the TLV is optional or mandatory. Presumably the high order bit mandatory/optional flag is only used by top-level TLV and Type 0 should be considered as invalid, then should it say something like this.
"The Type field of top-level TLVs has valid range from 1 to 32767 inclusive.
 The Type field of sub-TLVs has valid range from 1 to 65535 inclusive."

Moreover, all vendor specific top-level TLVs are considered as optional TLVs. Hence, the high order bit of Type field of these TLVs must be set to 1.

Cheers,
/Gatot --===============0902470740== 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 --===============0902470740==-- From mpls-bounces@ietf.org Mon Feb 28 07:27:57 2005 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 HAA12841; Mon, 28 Feb 2005 07:27:56 -0500 (EST) Received: from megatron.ietf.org ([132.151.6.71]) by ietf-mx.ietf.org with esmtp (Exim 4.33) id 1D5k0x-0005f4-Ng; Mon, 28 Feb 2005 07:28:43 -0500 Received: from localhost.localdomain ([127.0.0.1] helo=megatron.ietf.org) by megatron.ietf.org with esmtp (Exim 4.32) id 1D5jxr-0000Se-TN; Mon, 28 Feb 2005 07:25:31 -0500 Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org) by megatron.ietf.org with esmtp (Exim 4.32) id 1D5aim-00023o-OL for mpls@megatron.ietf.org; Sun, 27 Feb 2005 21:33:20 -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 VAA28008 for ; Sun, 27 Feb 2005 21:33:19 -0500 (EST) Received: from relay03.pair.com ([209.68.5.17]) by ietf-mx.ietf.org with smtp (Exim 4.33) id 1D5ajQ-0002o9-Lw for mpls@ietf.org; Sun, 27 Feb 2005 21:34:01 -0500 Received: (qmail 39110 invoked from network); 28 Feb 2005 02:33:12 -0000 Received: from unknown (HELO workhorse.faster-light.net) (unknown) by unknown with SMTP; 28 Feb 2005 02:33:12 -0000 X-pair-Authenticated: 69.37.59.162 Received: from workhorse.faster-light.net (localhost.faster-light.net [127.0.0.1]) by workhorse.faster-light.net (8.12.11/8.12.11) with ESMTP id j1S2X7oj002075; Sun, 27 Feb 2005 21:33:08 -0500 (EST) (envelope-from curtis@workhorse.faster-light.net) Message-Id: <200502280233.j1S2X7oj002075@workhorse.faster-light.net> To: routing-discussion@ietf.org In-reply-to: Your message of "Thu, 24 Feb 2005 21:39:47 PST." <200502250539.j1P5dliu018627@bright.research.att.com> Date: Sun, 27 Feb 2005 21:33:07 -0500 From: Curtis Villamizar X-Spam-Status: No, score=-2.8 required=5.0 tests=ALL_TRUSTED autolearn=failed version=3.0.1 X-Spam-Checker-Version: SpamAssassin 3.0.1 (2004-10-22) on workhorse.faster-light.net X-Spam-Score: 0.0 (/) X-Scan-Signature: 7655788c23eb79e336f5f8ba8bce7906 X-Mailman-Approved-At: Mon, 28 Feb 2005 07:25:30 -0500 Cc: ccamp@ops.ietf.org, mpls@ietf.org Subject: [mpls] Re: MPLS/GMPLS Change Process X-BeenThere: mpls@lists.ietf.org X-Mailman-Version: 2.1.5 Precedence: list Reply-To: curtis@faster-light.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: 0bc60ec82efc80c84b8d02f4b0e4de22 In message <200502250539.j1P5dliu018627@bright.research.att.com> Bill Fenner writes: > > > We expect to talk about the MPLS/GMPLS Change Process at the > Routing Area meeting in Minneapolis. The main changes from the > -00 version are the addition of the preliminary process which > doesn't require an I-D and additional mentions of where liaisons > fit in the process. > > Let's please discuss this on the routing-discussion list, instead > of trying to use both ccamp and mpls lists. > > Bill Bill, Excellent job on the liason section. Exactly as it should be. Curtis _______________________________________________ mpls mailing list mpls@lists.ietf.org https://www1.ietf.org/mailman/listinfo/mpls From mpls-bounces@ietf.org Mon Feb 28 09:40:37 2005 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 JAA25296; Mon, 28 Feb 2005 09:40:37 -0500 (EST) Received: from megatron.ietf.org ([132.151.6.71]) by ietf-mx.ietf.org with esmtp (Exim 4.33) id 1D5m5O-0008Uo-79; Mon, 28 Feb 2005 09:41:26 -0500 Received: from localhost.localdomain ([127.0.0.1] helo=megatron.ietf.org) by megatron.ietf.org with esmtp (Exim 4.32) id 1D5m32-0003FX-Lk; Mon, 28 Feb 2005 09:39:00 -0500 Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org) by megatron.ietf.org with esmtp (Exim 4.32) id 1D5m30-0003FH-Hu; Mon, 28 Feb 2005 09:38:58 -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 JAA25081; Mon, 28 Feb 2005 09:38:57 -0500 (EST) Received: from eagle.ericsson.se ([193.180.251.53]) by ietf-mx.ietf.org with esmtp (Exim 4.33) id 1D5m3l-0008Rh-1m; Mon, 28 Feb 2005 09:39:45 -0500 Received: from esealmw143.al.sw.ericsson.se ([153.88.254.118]) by eagle.ericsson.se (8.12.10/8.12.10/WIREfire-1.8b) with ESMTP id j1SEctO6009315; Mon, 28 Feb 2005 15:38:55 +0100 Received: from esealnt610.al.sw.ericsson.se ([153.88.254.120]) by esealmw143.al.sw.ericsson.se with Microsoft SMTPSVC(6.0.3790.211); Mon, 28 Feb 2005 15:39:41 +0100 Received: by esealnt610.al.sw.ericsson.se with Internet Mail Service (5.5.2657.72) id ; Mon, 28 Feb 2005 15:42:47 +0100 Message-ID: <026F8EEDAD2C4342A993203088C1FC051C26B7@esealmw109.eemea.ericsson.se> From: "Lars-Erik Jonsson (LU/EAB)" To: "'Ash, Gerald R (Jerry), ALABS'" , "Lars-Erik Jonsson (LU/EAB)" , "Magnus Westerlund (KI/EAB)" Subject: RE: [AVT] [mpls] Comments on draft-ash-avt-ecrtp-over-mpls-protoc ol-02.txt Date: Mon, 28 Feb 2005 15:39:28 +0100 MIME-Version: 1.0 X-Mailer: Internet Mail Service (5.5.2657.72) Content-Type: text/plain; charset="iso-8859-1" X-OriginalArrivalTime: 28 Feb 2005 14:39:41.0772 (UTC) FILETIME=[567B40C0:01C51DA3] X-Spam-Score: 0.0 (/) X-Scan-Signature: c54bc2f42d02429833c0ca4b8725abd7 Cc: mpls@ietf.org, rohc@ietf.org, IETF AVT WG X-BeenThere: mpls@lists.ietf.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Multi-Protocol Label Switching WG List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Sender: mpls-bounces@ietf.org Errors-To: mpls-bounces@ietf.org X-Spam-Score: 0.0 (/) X-Scan-Signature: 0770535483960d190d4a0d020e7060bd Jerry, I've provided further comments below. Since I fully agree with Magnus comment 1. on how to map existing HC solutions to MPLS, i.e. to address the right problem here, I will not repeat that discussion and therefore I do not address the CID negotiation and allocation part. However, I'll comment on a number of things that I find strange, unclear or incorrect. > Hopefully we will get MPLS and header compression SMEs to > make comments and suggestions on the rather complex issues > you have raised (e.g., signal the CIDs 'at layer 2', > negotiate the HC parameters 'at layer 2'). I do not think I have suggested to signal CIDs at layer 2, but I have pointed out that all existing HC schemes let the layer 2 protocol negotiate the CID-space to be used, and CIDs are then allocated by the compressor (within that space). > Both Lars-Erik and Magnus are pushing for a solution to HC > over MPLS that includes all existing HC schemes: IPHC (RFC 2507), > CRTP (RFC 2508), ECRTP (RFC 3545), and ROHC (RFC 3095). > Recall that the original AVT charter item was limited to > ECRTP. Probably it is OK to generalize to CRTP, ECRTP, and > ROHC, given the similarities in these protocols. However, > I'm concerned about the possible morass of issues this may lead > to regarding each of the schemes, especially wrt IPHC (RFC > 2507), which addresses HC for TCP, etc. Considering that IPHC is the basis for CRTP, and thus also eCRTP, I just do not see a reason to exclude IPHC if the AVT WG decides to develop an HC mapping for MPLS. > > By the way, could we please avoid the terminology > > "control/data plane". > > This is common terminology, I don't know what is the issue > with using this terminology? I know this terminology is commonly used within the telecom industry, but I do not consider it common IETF terminology. So, if you want to use that terminology here, in the context of header compression, you would have to define what it means, as its telco meaning does not really makes clear sense here. > It is not acceptable to have any chance of using the same CID > for different flows occurring at the same time. Here I fully agree with you, but existing HC schemes are designed based on the assumption that they operate on a dedicated link where this can not happen, and as Magnus has pointed out, the problem we should address here is how to create that point2point link over MPLS. > > For the negotiation & encapsulation I would strongly recommend using > > RFC 3544 and RFC 3409 as a basis, and clearly highlight potential > > deviations from the solutions used in these RFC's, that would help > > to get more constructive involvement from the HC folks in this work. > > Regarding 'negotiating HC scheme parameters', it is probably > valid that we should address how the HC scheme parameters are > negotiated across an MPLS LSP. However, the current RFCs don't > specify how this can be done across a (IP, GRE, or MPLS) tunnel. No, of course they do not, as they are for HC over PPP. However, they do handle all parameters that require negotiation for the various schemes, so you know what a mapping for the same schemes would require also in the MPLS case. Therefore, I think these RFC's have a useful base to be used for the MPLS HC mapping work. > There are two issues of concern on the CID handing question: > A. how to avoid duplication of CIDs at the HD for different flows. If > the HCO assigns the CIDs rather than the HD (as currently proposed in > the I-D, through RSVP-TE signaling), there is possible duplication of > CIDs at the HD for different flows. And my view of that problem is that the solution should make sure such duplication can not happen, by making sure one HD only get packets from one single peer HCO. > B. how to free up CIDs at the HCO when a flow has ended. Don't, but let the compressor control when/how to re-use CIDs when it gets out of CID-space. This is how existing HC schemes work. > > ECRTP packet type identification > > -------------------------------- > > Inconsistency, first paragraph of 2.2 talks about a 4-bit > > packet type, while the second paragraph says a one-octet > > PT ID is used. In the figure, I wonder what the first octet > > of zeros is, not really explained. > > "Defined by PPP Data Link Layer Protocol" means? > > You are correct about the inconsistency, which needs to be corrected. > > Furthermore, perhaps the 2 byte packet type identifier we now > specify in Section 2.2 of > http://ietf.org/internet-drafts/draft-ash-avt-ecrtp-over-mpls- > protocol-0 2.txt could be reduced to 1 byte, as follows: > > > 0 1 2 3 4 5 6 7 8 > +-+-+-+-+-+-+-+-+ > |0 0 0 0|Pkt Typ| > +-+-+-+-+-+-+-+-+ > where: > > SCID_Packet_Type designation: > 0000 (first nibble) > > "Packet Type" encoding: > 0: Reserved > 1: FULL_HEADER > 2: COMPRESSED_TCP > 3: COMPRESSED_TCP_NODELTA > 4: COMPRESSED_NON_TCP > 5: COMPRESSED_RTP_8 > 6: COMPRESSED_RTP_16 > 7: COMPRESSED_UDP_8 > 8: COMPRESSED_UDP_16 > 9: CONTEXT_STATE > 10: ROHC > 11 - 15: RESERVED > If you handle the choice of HC scheme in negotiation, you could (for ROHC) save this extra octet for type identification. Type identification is more efficiently handled within the compressed header itself, as ROHC do. > We need to add an ROHC packet type, as pointed out in Section > 2.6 of RFC 3409 http://ietf.org/rfc/rfc3409.txt?number=3409. > It is also pointed out that ROHC further identifies the packet > type within its header. I don't feel we need to reserve 246 > additional packet types with a 1-byte field, which seems like > overkill. If you still add padding, I would rather see a 1-octet field. Cheers, /L-E _______________________________________________ mpls mailing list mpls@lists.ietf.org https://www1.ietf.org/mailman/listinfo/mpls From mpls-bounces@ietf.org Mon Feb 28 12:05:41 2005 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 MAA09798; Mon, 28 Feb 2005 12:05:41 -0500 (EST) Received: from megatron.ietf.org ([132.151.6.71]) by ietf-mx.ietf.org with esmtp (Exim 4.33) id 1D5oLo-0003Gr-Df; Mon, 28 Feb 2005 12:06:32 -0500 Received: from localhost.localdomain ([127.0.0.1] helo=megatron.ietf.org) by megatron.ietf.org with esmtp (Exim 4.32) id 1D5oGy-0002PE-KQ; Mon, 28 Feb 2005 12:01:32 -0500 Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org) by megatron.ietf.org with esmtp (Exim 4.32) id 1D5oGx-0002P9-Jl for mpls@megatron.ietf.org; Mon, 28 Feb 2005 12:01:31 -0500 Received: from tbdns.testbed.local ([80.86.78.228]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id MAA09403 for ; Mon, 28 Feb 2005 12:01:28 -0500 (EST) Received: from [172.16.2.202] (gw.imc.kth.se [193.10.152.67]) (authenticated bits=0) by tbdns.testbed.local (8.12.8/8.12.8) with ESMTP id j1SGs8pt002837 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO) for ; Mon, 28 Feb 2005 17:54:11 +0100 Message-ID: <42234E2A.6080408@pi.se> Date: Mon, 28 Feb 2005 18:00:26 +0100 From: Loa Andersson User-Agent: Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US; rv:1.7.2) Gecko/20040803 X-Accept-Language: en-us, en MIME-Version: 1.0 To: mpls@ietf.org Content-Type: text/plain; charset=us-ascii; format=flowed Content-Transfer-Encoding: 7bit Content-Transfer-Encoding: 7bit Subject: [mpls] tentative agenda X-BeenThere: mpls@lists.ietf.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Multi-Protocol Label Switching WG List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Sender: mpls-bounces@ietf.org Errors-To: mpls-bounces@ietf.org X-Spam-Score: 0.0 (/) X-Scan-Signature: 6cca30437e2d04f45110f2ff8dc1b1d5 Content-Transfer-Encoding: 7bit All, there is some problem with my web server, so until I got that fixed here is a text version of the agenda for Minneapolis. /Loa MPLS WG Agenda for the Minneapolis Meeting WEDNESDAY, March 9, 2005, 9.00 - 11.30 1. Agenda bashing 2. Working group status (20 min) - communication from MPLS & Frame Relay Alliance on establishing a liaison relationship - new RFCs -- RFC3988 "Maximum Transmission Unit Signalling Extensions for the Label Distribution Protocol" -- RFC4023 "Encapsulating MPLS in IP or Generic Routing Encapsulation (GRE)" - in IESG review -- draft-ietf-mpls-bundle -- draft-ietf-mpls-rsvpte-attributes -- draft-ietf-mpls-nodeid-subobject-05.txt -- draft-ietf-mpls-bgp-mpls-restart -- draft-ietf-mpls-explicit-null - wg drafts -- soft preemption (version -04 in pipe) -- mpls over l2tpv3 (new) WG chairs 3. Incoming liaisons - G.motnni from ITU-T SG15 Steve 5 min - MFA: Establishing a liaison relationship 2 min Loa 4. LDP to Draft Standards draft-ietf-mpls-rfc3036bis-01.txt draft-minei-ldp-operational-experience-00.txt Ina Minei 15 min 5. P2MP TE signaling requirement draft draft-ietf-mpls-p2mp-sig-requirement Seisho 10 min 6. Extensions to RSVP-TE for Point to Multipoint TE LSPs draft-ietf-mpls-rsvp-te-p2mp-01.txt Dimitri 10 min 7. Detecting Data Plane Failures in Point-to-Multipoint MPLS Traffic Engineering - Extensions to LSP Ping draft-yasukawa-mpls-p2mp-lsp-ping-01.txt Adrian 10 min 8. A mini-FRR(Fast Rerouting) mechanism for IP/MPLS network draft-defeng-mpls-mini-fast-rerouting-00.txt Li Defeng 15 min 9. Component Link Recording and Resource Control for GMPLS Link Bundles draft-zamfir-explicit-resource-control-bundle-04.txt Ali 10 min -- Loa Andersson Principal Networking Architect Acreo AB phone: +46 8 632 77 14 Isafjordsgatan 22 mobile: +46 739 81 21 64 Kista, Sweden email: loa.andersson@acreo.se loa@pi.se _______________________________________________ mpls mailing list mpls@lists.ietf.org https://www1.ietf.org/mailman/listinfo/mpls From mpls-bounces@ietf.org Mon Feb 28 14:55:22 2005 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 OAA28918; Mon, 28 Feb 2005 14:55:22 -0500 (EST) Received: from megatron.ietf.org ([132.151.6.71]) by ietf-mx.ietf.org with esmtp (Exim 4.33) id 1D5r00-0007Py-Vx; Mon, 28 Feb 2005 14:56:14 -0500 Received: from localhost.localdomain ([127.0.0.1] helo=megatron.ietf.org) by megatron.ietf.org with esmtp (Exim 4.32) id 1D5qxz-0001Gx-6y; Mon, 28 Feb 2005 14:54:07 -0500 Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org) by megatron.ietf.org with esmtp (Exim 4.32) id 1D5qxw-0001Gn-LL for mpls@megatron.ietf.org; Mon, 28 Feb 2005 14:54:05 -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 OAA28728 for ; Mon, 28 Feb 2005 14:54:03 -0500 (EST) Received: from pop-a065c32.pas.sa.earthlink.net ([207.217.121.247]) by ietf-mx.ietf.org with esmtp (Exim 4.33) id 1D5qyj-0007Ny-4J for mpls@ietf.org; Mon, 28 Feb 2005 14:54:54 -0500 Received: from h-68-164-89-21.snvacaid.dynamic.covad.net ([68.164.89.21] helo=earthlink.net) by pop-a065c32.pas.sa.earthlink.net with esmtp (Exim 3.33 #1) id 1D5qws-0000vi-00; Mon, 28 Feb 2005 11:52:58 -0800 Message-ID: <422377CB.26959DA3@earthlink.net> Date: Mon, 28 Feb 2005 11:58:03 -0800 From: Erblichs X-Sender: "Erblichs" <@smtp.earthlink.net> (Unverified) X-Mailer: Mozilla 4.72 [en]C-gatewaynet (Win98; I) X-Accept-Language: en MIME-Version: 1.0 To: loa@pi.se, stbryant@cisco.com, swallow@cisco.com, mpls@ietf.org Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit X-Spam-Score: 0.0 (/) X-Scan-Signature: 08170828343bcf1325e4a0fb4584481c Content-Transfer-Encoding: 7bit Subject: [mpls] ECMP : draft-ietf-mpls-ecmp-bcp-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.0 (/) X-Scan-Signature: 79899194edc4f33a41f49410777972f8 Content-Transfer-Encoding: 7bit Authors, I would like to suggest two additional sentances. ECMP in MPLS is supported by allocating at least two labels for at least two different LSPs, which are then allocated to a single FEC. Each of these LSPs are then explciitly routed with the same TE characteristics. It should more than likely be placed within the 1st paragraph of the "2. Current ECMP Practices" between the third and fourth sentances.. Mitchell Erblich _______________________________________________ mpls mailing list mpls@lists.ietf.org https://www1.ietf.org/mailman/listinfo/mpls From mpls-bounces@ietf.org Mon Feb 28 15:00:02 2005 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 PAA29492; Mon, 28 Feb 2005 15:00:02 -0500 (EST) Received: from megatron.ietf.org ([132.151.6.71]) by ietf-mx.ietf.org with esmtp (Exim 4.33) id 1D5r4W-0007VG-Pq; Mon, 28 Feb 2005 15:00:53 -0500 Received: from localhost.localdomain ([127.0.0.1] helo=megatron.ietf.org) by megatron.ietf.org with esmtp (Exim 4.32) id 1D5r2x-0002Be-1T; Mon, 28 Feb 2005 14:59:15 -0500 Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org) by megatron.ietf.org with esmtp (Exim 4.32) id 1D5r2u-0002BZ-Nm for mpls@megatron.ietf.org; Mon, 28 Feb 2005 14:59:12 -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 OAA29368 for ; Mon, 28 Feb 2005 14:59:11 -0500 (EST) Received: from pop-a065c32.pas.sa.earthlink.net ([207.217.121.247]) by ietf-mx.ietf.org with esmtp (Exim 4.33) id 1D5r3h-0007UL-Q3 for mpls@ietf.org; Mon, 28 Feb 2005 15:00:03 -0500 Received: from h-68-164-89-21.snvacaid.dynamic.covad.net ([68.164.89.21] helo=earthlink.net) by pop-a065c32.pas.sa.earthlink.net with esmtp (Exim 3.33 #1) id 1D5r2q-0003PK-00; Mon, 28 Feb 2005 11:59:08 -0800 Message-ID: <4223793C.F553D55A@earthlink.net> Date: Mon, 28 Feb 2005 12:04:12 -0800 From: Erblichs X-Sender: "Erblichs" <@smtp.earthlink.net> (Unverified) X-Mailer: Mozilla 4.72 [en]C-gatewaynet (Win98; I) X-Accept-Language: en MIME-Version: 1.0 To: mpls@ietf.org, jpv@cisco.com, curtis@avici.com Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit X-Spam-Score: 0.0 (/) X-Scan-Signature: 7aefe408d50e9c7c47615841cb314bed Content-Transfer-Encoding: 7bit Subject: [mpls] draft-ietf-mpls-soft-preemption-03.txt X-BeenThere: mpls@lists.ietf.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Multi-Protocol Label Switching WG List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Sender: mpls-bounces@ietf.org Errors-To: mpls-bounces@ietf.org X-Spam-Score: 0.0 (/) X-Scan-Signature: 68c8cc8a64a9d0402e43b8eee9fc4199 Content-Transfer-Encoding: 7bit Group, Is this draft still alive??? It expired Oct. 04 and is in the draft section. Mitchell Erblich _______________________________________________ mpls mailing list mpls@lists.ietf.org https://www1.ietf.org/mailman/listinfo/mpls From mpls-bounces@ietf.org Mon Feb 28 16:11:14 2005 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 QAA08360; Mon, 28 Feb 2005 16:11:14 -0500 (EST) Received: from megatron.ietf.org ([132.151.6.71]) by ietf-mx.ietf.org with esmtp (Exim 4.33) id 1D5sBT-0000xt-6i; Mon, 28 Feb 2005 16:12:07 -0500 Received: from localhost.localdomain ([127.0.0.1] helo=megatron.ietf.org) by megatron.ietf.org with esmtp (Exim 4.32) id 1D5s8x-0005JM-1O; Mon, 28 Feb 2005 16:09:31 -0500 Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org) by megatron.ietf.org with esmtp (Exim 4.32) id 1D5s8v-0005JH-Pi for mpls@megatron.ietf.org; Mon, 28 Feb 2005 16:09: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 QAA08034 for ; Mon, 28 Feb 2005 16:09:27 -0500 (EST) Received: from [80.86.78.228] (helo=tbdns.testbed.local) by ietf-mx.ietf.org with esmtp (Exim 4.33) id 1D5s9j-0000uG-4f for mpls@ietf.org; Mon, 28 Feb 2005 16:10:20 -0500 Received: from [192.168.0.100] (h118n2fls31o874.telia.com [213.66.236.118]) (authenticated bits=0) by tbdns.testbed.local (8.12.8/8.12.8) with ESMTP id j1SL0npt002861 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO); Mon, 28 Feb 2005 22:00:51 +0100 Message-ID: <42238816.6000904@pi.se> Date: Mon, 28 Feb 2005 22:07:34 +0100 From: Loa Andersson User-Agent: Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US; rv:1.7.2) Gecko/20040803 X-Accept-Language: en-us, en MIME-Version: 1.0 To: Erblichs Subject: Re: [mpls] draft-ietf-mpls-soft-preemption-03.txt References: <4223793C.F553D55A@earthlink.net> In-Reply-To: <4223793C.F553D55A@earthlink.net> Content-Type: text/plain; charset=us-ascii; format=flowed Content-Transfer-Encoding: 7bit X-Spam-Score: 0.0 (/) X-Scan-Signature: b19722fc8d3865b147c75ae2495625f2 Content-Transfer-Encoding: 7bit Cc: mpls@ietf.org, jpv@cisco.com, curtis@avici.com X-BeenThere: mpls@lists.ietf.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Multi-Protocol Label Switching WG List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Sender: mpls-bounces@ietf.org Errors-To: mpls-bounces@ietf.org X-Spam-Score: 0.0 (/) X-Scan-Signature: 69a74e02bbee44ab4f8eafdbcedd94a1 Content-Transfer-Encoding: 7bit Mitchell, yes alive - Oct 04 is not expiring date, but publication date. Last note I've on this is that I've asked the authors to clean up a number of nits. Matthew promissed to publish a version -04 shortly. /Loa Erblichs wrote: > Group, > > Is this draft still alive??? > > It expired Oct. 04 and is in the draft section. > > Mitchell Erblich > > _______________________________________________ > mpls mailing list > mpls@lists.ietf.org > https://www1.ietf.org/mailman/listinfo/mpls > -- Loa Andersson Principal Networking Architect Acreo AB phone: +46 8 632 77 14 Isafjordsgatan 22 mobile: +46 739 81 21 64 Kista, Sweden email: loa.andersson@acreo.se loa@pi.se _______________________________________________ mpls mailing list mpls@lists.ietf.org https://www1.ietf.org/mailman/listinfo/mpls