From exim@www1.ietf.org  Mon Mar  1 00:37:10 2004
Received: from optimus.ietf.org (optimus.ietf.org [132.151.1.19])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id AAA06216
	for <rtgwg-archive@odin.ietf.org>; Mon, 1 Mar 2004 00:37:10 -0500 (EST)
Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1Axg6c-0006GJ-Uv
	for rtgwg-archive@odin.ietf.org; Mon, 01 Mar 2004 00:36:43 -0500
Received: (from exim@localhost)
	by www1.ietf.org (8.12.8/8.12.8/Submit) id i215ag48024065
	for rtgwg-archive@odin.ietf.org; Mon, 1 Mar 2004 00:36:42 -0500
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1Axg6c-0006G3-Ov
	for rtgwg-web-archive@optimus.ietf.org; Mon, 01 Mar 2004 00:36:42 -0500
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id AAA06187
	for <rtgwg-web-archive@ietf.org>; Mon, 1 Mar 2004 00:36:39 -0500 (EST)
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 1Axg6a-0003HI-00
	for rtgwg-web-archive@ietf.org; Mon, 01 Mar 2004 00:36:40 -0500
Received: from exim by ietf-mx with spam-scanned (Exim 4.12)
	id 1Axg5f-0003Ad-00
	for rtgwg-web-archive@ietf.org; Mon, 01 Mar 2004 00:35:44 -0500
Received: from optimus.ietf.org ([132.151.1.19])
	by ietf-mx with esmtp (Exim 4.12)
	id 1Axg4z-00033g-00
	for rtgwg-web-archive@ietf.org; Mon, 01 Mar 2004 00:35:01 -0500
Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1Axg4z-0005lx-0O; Mon, 01 Mar 2004 00:35:01 -0500
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1Axg4N-0005kT-3H
	for rtgwg@optimus.ietf.org; Mon, 01 Mar 2004 00:34:23 -0500
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id AAA05993
	for <rtgwg@ietf.org>; Mon, 1 Mar 2004 00:34:19 -0500 (EST)
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 1Axg4K-000306-00
	for rtgwg@ietf.org; Mon, 01 Mar 2004 00:34:20 -0500
Received: from exim by ietf-mx with spam-scanned (Exim 4.12)
	id 1Axg3M-0002u3-00
	for rtgwg@ietf.org; Mon, 01 Mar 2004 00:33:20 -0500
Received: from mx.uom.ac.mu ([202.60.7.12])
	by ietf-mx with esmtp (Exim 4.12)
	id 1Axg2M-0002lO-00
	for rtgwg@ietf.org; Mon, 01 Mar 2004 00:32:19 -0500
Received: from localhost ([])
        by mx.uom.ac.mu (Merak 7.2.0) with SMTP id DWA74278
        for <rtgwg@ietf.org>; Mon, 01 Mar 2004 09:31:44 +0400
Date: Mon, 01 Mar 2004 09:31:43 +0400
From: Boodhoo Avinash <boodhooa@mx.uom.ac.mu>
To: rtgwg@ietf.org
Subject: "Rtgwg" mailing list
Message-ID: <2d25ab8b567fc69145385f3874ed95f1@mx.uom.ac.mu>
X-Mailer: IceWarp Web Mail 5.2.2
X-Originating-IP: 172.22.28.36
MIME-Version: 1.0
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: 7bit
Content-Transfer-Encoding: 7bit
Sender: rtgwg-admin@ietf.org
Errors-To: rtgwg-admin@ietf.org
X-BeenThere: rtgwg@ietf.org
X-Mailman-Version: 2.0.12
Precedence: bulk
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/rtgwg>,
	<mailto:rtgwg-request@ietf.org?subject=unsubscribe>
List-Id: <rtgwg.ietf.org>
List-Post: <mailto:rtgwg@ietf.org>
List-Help: <mailto:rtgwg-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/rtgwg>,
	<mailto:rtgwg-request@ietf.org?subject=subscribe>
X-Spam-Checker-Version: SpamAssassin 2.60 (1.212-2003-09-23-exp) on 
	ietf-mx.ietf.org
X-Spam-Status: No, hits=0.1 required=5.0 tests=AWL autolearn=no version=2.60
Content-Transfer-Encoding: 7bit
Content-Transfer-Encoding: 7bit

subcribe boodhooa@mx.uom.ac.mu



_______________________________________________
Rtgwg mailing list
Rtgwg@ietf.org
https://www1.ietf.org/mailman/listinfo/rtgwg



From exim@www1.ietf.org  Wed Mar  3 01:37:41 2004
Received: from optimus.ietf.org (optimus.ietf.org [132.151.1.19])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id BAA06076
	for <rtgwg-archive@odin.ietf.org>; Wed, 3 Mar 2004 01:37:41 -0500 (EST)
Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1AyQ0F-00006M-UU
	for rtgwg-archive@odin.ietf.org; Wed, 03 Mar 2004 01:37:12 -0500
Received: (from exim@localhost)
	by www1.ietf.org (8.12.8/8.12.8/Submit) id i236bBjR000383
	for rtgwg-archive@odin.ietf.org; Wed, 3 Mar 2004 01:37:11 -0500
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1AyQ0F-000065-Er
	for rtgwg-web-archive@optimus.ietf.org; Wed, 03 Mar 2004 01:37:11 -0500
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id BAA06055
	for <rtgwg-web-archive@ietf.org>; Wed, 3 Mar 2004 01:37:09 -0500 (EST)
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 1AyQ0C-0000dO-00
	for rtgwg-web-archive@ietf.org; Wed, 03 Mar 2004 01:37:08 -0500
Received: from exim by ietf-mx with spam-scanned (Exim 4.12)
	id 1AyPzD-0000Ub-00
	for rtgwg-web-archive@ietf.org; Wed, 03 Mar 2004 01:36:07 -0500
Received: from optimus.ietf.org ([132.151.1.19])
	by ietf-mx with esmtp (Exim 4.12)
	id 1AyPyE-0000Ml-00
	for rtgwg-web-archive@ietf.org; Wed, 03 Mar 2004 01:35:06 -0500
Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1AyPyC-00081A-Dc; Wed, 03 Mar 2004 01:35:04 -0500
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1AyPxM-0007ox-UF
	for rtgwg@optimus.ietf.org; Wed, 03 Mar 2004 01:34:12 -0500
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id BAA06007
	for <rtgwg@ietf.org>; Wed, 3 Mar 2004 01:34:11 -0500 (EST)
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 1AyPxJ-0000Fn-00
	for rtgwg@ietf.org; Wed, 03 Mar 2004 01:34:09 -0500
Received: from exim by ietf-mx with spam-scanned (Exim 4.12)
	id 1AyPwM-00008e-00
	for rtgwg@ietf.org; Wed, 03 Mar 2004 01:33:11 -0500
Received: from mx.uom.ac.mu ([202.60.7.12])
	by ietf-mx with esmtp (Exim 4.12)
	id 1AyPw1-00000f-00
	for rtgwg@ietf.org; Wed, 03 Mar 2004 01:32:49 -0500
Received: from localhost ([])
        by mx.uom.ac.mu (Merak 7.2.0) with SMTP id DWA74278
        for <rtgwg@ietf.org>; Wed, 03 Mar 2004 10:32:13 +0400
Date: Wed, 03 Mar 2004 10:32:12 +0400
From: Boodhoo Avinash <boodhooa@mx.uom.ac.mu>
To: rtgwg@ietf.org
Subject: Research areas in IPv6
Message-ID: <49f49dca2cd7339f06ef389ef535c6d6@mx.uom.ac.mu>
X-Mailer: IceWarp Web Mail 5.2.2
X-Originating-IP: 172.22.28.36
MIME-Version: 1.0
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: 7bit
Content-Transfer-Encoding: 7bit
Sender: rtgwg-admin@ietf.org
Errors-To: rtgwg-admin@ietf.org
X-BeenThere: rtgwg@ietf.org
X-Mailman-Version: 2.0.12
Precedence: bulk
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/rtgwg>,
	<mailto:rtgwg-request@ietf.org?subject=unsubscribe>
List-Id: <rtgwg.ietf.org>
List-Post: <mailto:rtgwg@ietf.org>
List-Help: <mailto:rtgwg-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/rtgwg>,
	<mailto:rtgwg-request@ietf.org?subject=subscribe>
X-Spam-Checker-Version: SpamAssassin 2.60 (1.212-2003-09-23-exp) on 
	ietf-mx.ietf.org
X-Spam-Status: No, hits=0.7 required=5.0 tests=AWL,DEAR_SOMETHING 
	autolearn=no version=2.60
Content-Transfer-Encoding: 7bit
Content-Transfer-Encoding: 7bit

 Dear Sir,
           I present my salutations to you. I am Mr Avinash Boodhoo from Mauritius. I am currently doing an MPhil under the supervision of Dr KMS Soyjaudah at the University of Mauritius. My research is entitled "IPv6-Enabling the Mobile Internet". It would be very kind of you if you could help me in my reseach by suggesting some research areas in IPv6 or requesting to some specialists in the subject matter. I thank you in advance.

Yours Sincerly
  Avinash. 

_______________________________________________
Rtgwg mailing list
Rtgwg@ietf.org
https://www1.ietf.org/mailman/listinfo/rtgwg



From exim@www1.ietf.org  Wed Mar  3 08:36:32 2004
Received: from optimus.ietf.org (optimus.ietf.org [132.151.1.19])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id IAA26123
	for <rtgwg-archive@odin.ietf.org>; Wed, 3 Mar 2004 08:36:27 -0500 (EST)
Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1AyWXW-0004cR-SU
	for rtgwg-archive@odin.ietf.org; Wed, 03 Mar 2004 08:35:59 -0500
Received: (from exim@localhost)
	by www1.ietf.org (8.12.8/8.12.8/Submit) id i23DZwQa017749
	for rtgwg-archive@odin.ietf.org; Wed, 3 Mar 2004 08:35:58 -0500
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1AyWXR-0004cA-Gf
	for rtgwg-web-archive@optimus.ietf.org; Wed, 03 Mar 2004 08:35:58 -0500
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id IAA26090
	for <rtgwg-web-archive@ietf.org>; Wed, 3 Mar 2004 08:35:36 -0500 (EST)
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 1AyWXB-00031T-00
	for rtgwg-web-archive@ietf.org; Wed, 03 Mar 2004 08:35:37 -0500
Received: from exim by ietf-mx with spam-scanned (Exim 4.12)
	id 1AyWWF-0002rF-00
	for rtgwg-web-archive@ietf.org; Wed, 03 Mar 2004 08:34:40 -0500
Received: from optimus.ietf.org ([132.151.1.19])
	by ietf-mx with esmtp (Exim 4.12)
	id 1AyWVf-0002i1-00
	for rtgwg-web-archive@ietf.org; Wed, 03 Mar 2004 08:34:03 -0500
Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1AyWVc-000499-OP; Wed, 03 Mar 2004 08:34:00 -0500
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1AyWVO-00048l-E9
	for rtgwg@optimus.ietf.org; Wed, 03 Mar 2004 08:33:46 -0500
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id IAA26020
	for <rtgwg@ietf.org>; Wed, 3 Mar 2004 08:33:24 -0500 (EST)
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 1AyWV3-0002gD-00
	for rtgwg@ietf.org; Wed, 03 Mar 2004 08:33:25 -0500
Received: from exim by ietf-mx with spam-scanned (Exim 4.12)
	id 1AyWUD-0002YH-00
	for rtgwg@ietf.org; Wed, 03 Mar 2004 08:32:33 -0500
Received: from [208.246.215.201] (helo=mailhost.avici.com)
	by ietf-mx with esmtp (Exim 4.12)
	id 1AyWTK-0002HE-00
	for rtgwg@ietf.org; Wed, 03 Mar 2004 08:31:38 -0500
Received: from aatlas-lt2.avici.com (b2vpn2pc13.avici.com [10.2.104.13])
	by mailhost.avici.com (8.12.8/8.12.8) with ESMTP id i23DV0WV026905
	for <rtgwg@ietf.org>; Wed, 3 Mar 2004 08:31:01 -0500
Message-Id: <5.1.0.14.2.20040303083120.01d6d3c0@pop.avici.com>
X-Sender: aatlas@pop.avici.com
X-Mailer: QUALCOMM Windows Eudora Version 5.1
Date: Wed, 03 Mar 2004 08:33:31 -0500
To: rtgwg@ietf.org
From: Alia Atlas <aatlas@avici.com>
Subject: comments on draft-atlas-ip-local-protect-00
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-Avici-MailScanner: Found to be clean
Sender: rtgwg-admin@ietf.org
Errors-To: rtgwg-admin@ietf.org
X-BeenThere: rtgwg@ietf.org
X-Mailman-Version: 2.0.12
Precedence: bulk
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/rtgwg>,
	<mailto:rtgwg-request@ietf.org?subject=unsubscribe>
List-Id: <rtgwg.ietf.org>
List-Post: <mailto:rtgwg@ietf.org>
List-Help: <mailto:rtgwg-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/rtgwg>,
	<mailto:rtgwg-request@ietf.org?subject=subscribe>
X-Spam-Checker-Version: SpamAssassin 2.60 (1.212-2003-09-23-exp) on 
	ietf-mx.ietf.org
X-Spam-Status: No, hits=0.0 required=5.0 tests=none autolearn=no version=2.60

Are there any more comments or questions on this?  I know we didn't have 
time to discuss it in detail at the Routing Area meeting.

Thanks,
Alia


_______________________________________________
Rtgwg mailing list
Rtgwg@ietf.org
https://www1.ietf.org/mailman/listinfo/rtgwg



From exim@www1.ietf.org  Thu Mar 18 09:56:33 2004
Received: from optimus.ietf.org (optimus.ietf.org [132.151.1.19])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id JAA15409
	for <rtgwg-archive@odin.ietf.org>; Thu, 18 Mar 2004 09:56:33 -0500 (EST)
Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1B3yvy-00055E-B1
	for rtgwg-archive@odin.ietf.org; Thu, 18 Mar 2004 09:55:56 -0500
Received: (from exim@localhost)
	by www1.ietf.org (8.12.8/8.12.8/Submit) id i2IEtaiY019488
	for rtgwg-archive@odin.ietf.org; Thu, 18 Mar 2004 09:55:36 -0500
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1B3yvn-00053q-Rb
	for rtgwg-web-archive@optimus.ietf.org; Thu, 18 Mar 2004 09:55:35 -0500
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id JAA15309
	for <rtgwg-web-archive@ietf.org>; Thu, 18 Mar 2004 09:55:26 -0500 (EST)
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 1B3yvf-0001JC-00
	for rtgwg-web-archive@ietf.org; Thu, 18 Mar 2004 09:55:27 -0500
Received: from exim by ietf-mx with spam-scanned (Exim 4.12)
	id 1B3yuh-0001A9-00
	for rtgwg-web-archive@ietf.org; Thu, 18 Mar 2004 09:54:28 -0500
Received: from optimus.ietf.org ([132.151.1.19])
	by ietf-mx with esmtp (Exim 4.12)
	id 1B3ytl-00012r-00
	for rtgwg-web-archive@ietf.org; Thu, 18 Mar 2004 09:53:29 -0500
Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1B3ysN-0004at-2a; Thu, 18 Mar 2004 09:52:03 -0500
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1B3yql-0004WO-Uy
	for rtgwg@optimus.ietf.org; Thu, 18 Mar 2004 09:50:23 -0500
Received: from CNRI.Reston.VA.US (localhost [127.0.0.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id JAA14921;
	Thu, 18 Mar 2004 09:50:18 -0500 (EST)
Message-Id: <200403181450.JAA14921@ietf.org>
Mime-Version: 1.0
Content-Type: Multipart/Mixed; Boundary="NextPart"
To: IETF-Announce: ;
Cc: rtgwg@ietf.org
From: Internet-Drafts@ietf.org
Reply-to: Internet-Drafts@ietf.org
Subject: I-D ACTION:draft-ietf-rtgwg-rfc3682bis-00.txt
Date: Thu, 18 Mar 2004 09:50:18 -0500
Sender: rtgwg-admin@ietf.org
Errors-To: rtgwg-admin@ietf.org
X-BeenThere: rtgwg@ietf.org
X-Mailman-Version: 2.0.12
Precedence: bulk
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/rtgwg>,
	<mailto:rtgwg-request@ietf.org?subject=unsubscribe>
List-Id: <rtgwg.ietf.org>
List-Post: <mailto:rtgwg@ietf.org>
List-Help: <mailto:rtgwg-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/rtgwg>,
	<mailto:rtgwg-request@ietf.org?subject=subscribe>
X-Spam-Checker-Version: SpamAssassin 2.60 (1.212-2003-09-23-exp) on 
	ietf-mx.ietf.org
X-Spam-Status: No, hits=0.5 required=5.0 tests=AWL,MIME_BOUND_NEXTPART,
	NO_REAL_NAME autolearn=no version=2.60

--NextPart

A New Internet-Draft is available from the on-line Internet-Drafts directories.
This draft is a work item of the Routing Area Working Group Working Group of the IETF.

	Title		: The Generalized TTL Security Mechanism (GTSM)
	Author(s)	: V. Gill, J. Heasley, D. Meyer
	Filename	: draft-ietf-rtgwg-rfc3682bis-00.txt
	Pages		: 14
	Date		: 2004-3-17
	
The use of a packet's TTL (IPv4) or Hop Limit (IPv6) to protect a
   protocol stack from CPU-utilization based attacks has been proposed
   in many settings (see for example, RFC 2461). This document
   generalizes these techniques for use by other protocols such as BGP
   (RFC 1771), MSDP, Bidirectional Forwarding Detection, and LDP (RFC
   3036). While the Generalized TTL Security Mechanism (GTSM)  is most
   effective in protecting directly connected protocol peers, it can
   also provide a lower level of protection to multi-hop sessions. GTSM
   is not directly applicable to protocols employing flooding mechanisms
   (e.g., multicast), and use of multi-hop GTSM should be considered on
   a case-by-case basis.

A URL for this Internet-Draft is:
http://www.ietf.org/internet-drafts/draft-ietf-rtgwg-rfc3682bis-00.txt

To remove yourself from the IETF Announcement list, send a message to 
ietf-announce-request with the word unsubscribe in the body of the message.

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-rtgwg-rfc3682bis-00.txt".

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


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

Send a message to:
	mailserv@ietf.org.
In the body type:
	"FILE /internet-drafts/draft-ietf-rtgwg-rfc3682bis-00.txt".
	
NOTE:	The mail server at ietf.org can return the document in
	MIME-encoded form by using the "mpack" utility.  To use this
	feature, insert the command "ENCODING mime" before the "FILE"
	command.  To decode the response(s), you will need "munpack" or
	a MIME-compliant mail reader.  Different MIME-compliant mail readers
	exhibit different behavior, especially when dealing with
	"multipart" MIME messages (i.e. documents which have been split
	up into multiple messages), so check your local documentation on
	how to manipulate these messages.
		
		
Below is the data which will enable a MIME compliant mail reader
implementation to automatically retrieve the ASCII version of the
Internet-Draft.

--NextPart
Content-Type: Multipart/Alternative; Boundary="OtherAccess"

--OtherAccess
Content-Type: Message/External-body;
	access-type="mail-server";
	server="mailserv@ietf.org"

Content-Type: text/plain
Content-ID:	<2004-3-18101353.I-D@ietf.org>

ENCODING mime
FILE /internet-drafts/draft-ietf-rtgwg-rfc3682bis-00.txt

--OtherAccess
Content-Type: Message/External-body;
	name="draft-ietf-rtgwg-rfc3682bis-00.txt";
	site="ftp.ietf.org";
	access-type="anon-ftp";
	directory="internet-drafts"

Content-Type: text/plain
Content-ID:	<2004-3-18101353.I-D@ietf.org>

--OtherAccess--

--NextPart--



_______________________________________________
Rtgwg mailing list
Rtgwg@ietf.org
https://www1.ietf.org/mailman/listinfo/rtgwg



From exim@www1.ietf.org  Thu Mar 18 10:37:44 2004
Received: from optimus.ietf.org (optimus.ietf.org [132.151.1.19])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id KAA20553
	for <rtgwg-archive@odin.ietf.org>; Thu, 18 Mar 2004 10:37:44 -0500 (EST)
Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1B3zZT-0006Oa-QO
	for rtgwg-archive@odin.ietf.org; Thu, 18 Mar 2004 10:36:56 -0500
Received: (from exim@localhost)
	by www1.ietf.org (8.12.8/8.12.8/Submit) id i2IFaP2r024552
	for rtgwg-archive@odin.ietf.org; Thu, 18 Mar 2004 10:36:25 -0500
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1B3zZC-0006Mt-0i
	for rtgwg-web-archive@optimus.ietf.org; Thu, 18 Mar 2004 10:36:18 -0500
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id KAA20412
	for <rtgwg-web-archive@ietf.org>; Thu, 18 Mar 2004 10:36:05 -0500 (EST)
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 1B3zZ1-0006bJ-00
	for rtgwg-web-archive@ietf.org; Thu, 18 Mar 2004 10:36:07 -0500
Received: from exim by ietf-mx with spam-scanned (Exim 4.12)
	id 1B3zYC-0006Tf-00
	for rtgwg-web-archive@ietf.org; Thu, 18 Mar 2004 10:35:17 -0500
Received: from optimus.ietf.org ([132.151.1.19])
	by ietf-mx with esmtp (Exim 4.12)
	id 1B3zWn-0006Fn-00
	for rtgwg-web-archive@ietf.org; Thu, 18 Mar 2004 10:33:49 -0500
Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1B3zW9-00066r-H6; Thu, 18 Mar 2004 10:33:09 -0500
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1B3zVY-00063t-El
	for rtgwg@optimus.ietf.org; Thu, 18 Mar 2004 10:32:32 -0500
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id KAA19862
	for <rtgwg@ietf.org>; Thu, 18 Mar 2004 10:32:23 -0500 (EST)
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 1B3zVR-00060R-00
	for rtgwg@ietf.org; Thu, 18 Mar 2004 10:32:25 -0500
Received: from exim by ietf-mx with spam-scanned (Exim 4.12)
	id 1B3zTn-0005jn-00
	for rtgwg@ietf.org; Thu, 18 Mar 2004 10:30:44 -0500
Received: from netcore.fi ([193.94.160.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 1B3zSF-0005Pq-00
	for rtgwg@ietf.org; Thu, 18 Mar 2004 10:29:07 -0500
Received: from localhost (pekkas@localhost)
	by netcore.fi (8.11.6/8.11.6) with ESMTP id i2IFSZQ01175
	for <rtgwg@ietf.org>; Thu, 18 Mar 2004 17:28:35 +0200
Date: Thu, 18 Mar 2004 17:28:35 +0200 (EET)
From: Pekka Savola <pekkas@netcore.fi>
To: rtgwg@ietf.org
Subject: Re: I-D ACTION:draft-ietf-rtgwg-rfc3682bis-00.txt
In-Reply-To: <200403181450.JAA14921@ietf.org>
Message-ID: <Pine.LNX.4.44.0403181725410.552-100000@netcore.fi>
MIME-Version: 1.0
Content-Type: TEXT/PLAIN; charset=US-ASCII
Sender: rtgwg-admin@ietf.org
Errors-To: rtgwg-admin@ietf.org
X-BeenThere: rtgwg@ietf.org
X-Mailman-Version: 2.0.12
Precedence: bulk
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/rtgwg>,
	<mailto:rtgwg-request@ietf.org?subject=unsubscribe>
List-Id: <rtgwg.ietf.org>
List-Post: <mailto:rtgwg@ietf.org>
List-Help: <mailto:rtgwg-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/rtgwg>,
	<mailto:rtgwg-request@ietf.org?subject=subscribe>
X-Spam-Checker-Version: SpamAssassin 2.60 (1.212-2003-09-23-exp) on 
	ietf-mx.ietf.org
X-Spam-Status: No, hits=0.0 required=5.0 tests=AWL autolearn=no version=2.60

Hi -- just a comment,

Sigh.  So blatant typo in sect 3, i.b).  Hopefully, this should be 
rather obvious from the other text.

The bad news is that this document inherits all the typos etc. that
were fixed by RFC-editor; just wdiff RFC3682 and this to see that.

On Thu, 18 Mar 2004 Internet-Drafts@ietf.org wrote:
> A New Internet-Draft is available from the on-line Internet-Drafts directories.
> This draft is a work item of the Routing Area Working Group Working Group of the IETF.
> 
> 	Title		: The Generalized TTL Security Mechanism (GTSM)
> 	Author(s)	: V. Gill, J. Heasley, D. Meyer
> 	Filename	: draft-ietf-rtgwg-rfc3682bis-00.txt
> 	Pages		: 14
> 	Date		: 2004-3-17
> 	
> The use of a packet's TTL (IPv4) or Hop Limit (IPv6) to protect a
>    protocol stack from CPU-utilization based attacks has been proposed
>    in many settings (see for example, RFC 2461). This document
>    generalizes these techniques for use by other protocols such as BGP
>    (RFC 1771), MSDP, Bidirectional Forwarding Detection, and LDP (RFC
>    3036). While the Generalized TTL Security Mechanism (GTSM)  is most
>    effective in protecting directly connected protocol peers, it can
>    also provide a lower level of protection to multi-hop sessions. GTSM
>    is not directly applicable to protocols employing flooding mechanisms
>    (e.g., multicast), and use of multi-hop GTSM should be considered on
>    a case-by-case basis.
> 
> A URL for this Internet-Draft is:
> http://www.ietf.org/internet-drafts/draft-ietf-rtgwg-rfc3682bis-00.txt
> 
> To remove yourself from the IETF Announcement list, send a message to 
> ietf-announce-request with the word unsubscribe in the body of the message.
> 
> 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-rtgwg-rfc3682bis-00.txt".
> 
> A list of Internet-Drafts directories can be found in
> http://www.ietf.org/shadow.html 
> or ftp://ftp.ietf.org/ietf/1shadow-sites.txt
> 
> 
> Internet-Drafts can also be obtained by e-mail.
> 
> Send a message to:
> 	mailserv@ietf.org.
> In the body type:
> 	"FILE /internet-drafts/draft-ietf-rtgwg-rfc3682bis-00.txt".
> 	
> NOTE:	The mail server at ietf.org can return the document in
> 	MIME-encoded form by using the "mpack" utility.  To use this
> 	feature, insert the command "ENCODING mime" before the "FILE"
> 	command.  To decode the response(s), you will need "munpack" or
> 	a MIME-compliant mail reader.  Different MIME-compliant mail readers
> 	exhibit different behavior, especially when dealing with
> 	"multipart" MIME messages (i.e. documents which have been split
> 	up into multiple messages), so check your local documentation on
> 	how to manipulate these messages.
> 		
> 		
> Below is the data which will enable a MIME compliant mail reader
> implementation to automatically retrieve the ASCII version of the
> Internet-Draft.
> 

-- 
Pekka Savola                 "You each name yourselves king, yet the
Netcore Oy                    kingdom bleeds."
Systems. Networks. Security. -- George R.R. Martin: A Clash of Kings


_______________________________________________
Rtgwg mailing list
Rtgwg@ietf.org
https://www1.ietf.org/mailman/listinfo/rtgwg



From exim@www1.ietf.org  Thu Mar 18 11:13:10 2004
Received: from optimus.ietf.org (optimus.ietf.org [132.151.1.19])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id LAA22274
	for <rtgwg-archive@odin.ietf.org>; Thu, 18 Mar 2004 11:13:09 -0500 (EST)
Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1B408L-0000XG-0I
	for rtgwg-archive@odin.ietf.org; Thu, 18 Mar 2004 11:12:41 -0500
Received: (from exim@localhost)
	by www1.ietf.org (8.12.8/8.12.8/Submit) id i2IGCadR002052
	for rtgwg-archive@odin.ietf.org; Thu, 18 Mar 2004 11:12:36 -0500
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1B408K-0000Wx-Q4
	for rtgwg-web-archive@optimus.ietf.org; Thu, 18 Mar 2004 11:12:36 -0500
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id LAA22245
	for <rtgwg-web-archive@ietf.org>; Thu, 18 Mar 2004 11:12:34 -0500 (EST)
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 1B408J-0000m6-00
	for rtgwg-web-archive@ietf.org; Thu, 18 Mar 2004 11:12:35 -0500
Received: from exim by ietf-mx with spam-scanned (Exim 4.12)
	id 1B407K-0000jX-00
	for rtgwg-web-archive@ietf.org; Thu, 18 Mar 2004 11:11:35 -0500
Received: from optimus.ietf.org ([132.151.1.19])
	by ietf-mx with esmtp (Exim 4.12)
	id 1B4070-0000gy-00
	for rtgwg-web-archive@ietf.org; Thu, 18 Mar 2004 11:11:14 -0500
Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1B406L-0000JG-Vi; Thu, 18 Mar 2004 11:10:33 -0500
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1B404m-0008WF-Jt
	for rtgwg@optimus.ietf.org; Thu, 18 Mar 2004 11:08:56 -0500
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id LAA22075
	for <rtgwg@ietf.org>; Thu, 18 Mar 2004 11:08:31 -0500 (EST)
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 1B404O-0000aO-00
	for rtgwg@ietf.org; Thu, 18 Mar 2004 11:08:32 -0500
Received: from exim by ietf-mx with spam-scanned (Exim 4.12)
	id 1B403V-0000YH-00
	for rtgwg@ietf.org; Thu, 18 Mar 2004 11:07:38 -0500
Received: from m106.maoz.com ([205.167.76.9])
	by ietf-mx with esmtp (Exim 4.12)
	id 1B4038-0000Vq-00
	for rtgwg@ietf.org; Thu, 18 Mar 2004 11:07:15 -0500
Received: from m106.maoz.com (localhost.localdomain [127.0.0.1])
	by m106.maoz.com (8.12.11/8.12.11) with ESMTP id i2IG6fEm003408;
	Thu, 18 Mar 2004 08:06:41 -0800
Received: (from dmm@localhost)
	by m106.maoz.com (8.12.11/8.12.10/Submit) id i2IG6fQv003407;
	Thu, 18 Mar 2004 08:06:41 -0800
X-Authentication-Warning: m106.maoz.com: dmm set sender to dmm@1-4-5.net using -f
Date: Thu, 18 Mar 2004 08:06:41 -0800
From: David Meyer <dmm@1-4-5.net>
To: Pekka Savola <pekkas@netcore.fi>
Cc: rtgwg@ietf.org
Subject: Re: I-D ACTION:draft-ietf-rtgwg-rfc3682bis-00.txt
Message-ID: <20040318160641.GA2079@1-4-5.net>
References: <200403181450.JAA14921@ietf.org> <Pine.LNX.4.44.0403181725410.552-100000@netcore.fi>
Mime-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
In-Reply-To: <Pine.LNX.4.44.0403181725410.552-100000@netcore.fi>
User-Agent: Mutt/1.4.1i
X-public-key: http://www.1-4-5.net/~dmm/public-key.asc
X-philosophy: "I just had to let it go" -- John Lennon
Sender: rtgwg-admin@ietf.org
Errors-To: rtgwg-admin@ietf.org
X-BeenThere: rtgwg@ietf.org
X-Mailman-Version: 2.0.12
Precedence: bulk
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/rtgwg>,
	<mailto:rtgwg-request@ietf.org?subject=unsubscribe>
List-Id: <rtgwg.ietf.org>
List-Post: <mailto:rtgwg@ietf.org>
List-Help: <mailto:rtgwg-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/rtgwg>,
	<mailto:rtgwg-request@ietf.org?subject=subscribe>
X-Spam-Checker-Version: SpamAssassin 2.60 (1.212-2003-09-23-exp) on 
	ietf-mx.ietf.org
X-Spam-Status: No, hits=0.0 required=5.0 tests=AWL autolearn=no version=2.60


	Pekka,

	Thanks for the comments.

>> Sigh.  So blatant typo in sect 3, i.b).  Hopefully, this should be 
>> rather obvious from the other text.

	This is interesting because this is one of the sections
	that was (explicitly) changed (as you no doubt know). In
	any event, can you be more specific.

>> The bad news is that this document inherits all the typos etc. that
>> were fixed by RFC-editor; just wdiff RFC3682 and this to see that.

	I have to find a wdiff that will build on fedora then
	I'll do so. 

	Thanks,

	Dave

_______________________________________________
Rtgwg mailing list
Rtgwg@ietf.org
https://www1.ietf.org/mailman/listinfo/rtgwg



From exim@www1.ietf.org  Thu Mar 18 12:18:05 2004
Received: from optimus.ietf.org (optimus.ietf.org [132.151.1.19])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id MAA25911
	for <rtgwg-archive@odin.ietf.org>; Thu, 18 Mar 2004 12:18:05 -0500 (EST)
Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1B419F-000715-Vf
	for rtgwg-archive@odin.ietf.org; Thu, 18 Mar 2004 12:17:38 -0500
Received: (from exim@localhost)
	by www1.ietf.org (8.12.8/8.12.8/Submit) id i2IHHVEd026938
	for rtgwg-archive@odin.ietf.org; Thu, 18 Mar 2004 12:17:31 -0500
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1B4197-00070O-UC
	for rtgwg-web-archive@optimus.ietf.org; Thu, 18 Mar 2004 12:17:29 -0500
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id MAA25875
	for <rtgwg-web-archive@ietf.org>; Thu, 18 Mar 2004 12:17:21 -0500 (EST)
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 1B4191-00051h-00
	for rtgwg-web-archive@ietf.org; Thu, 18 Mar 2004 12:17:23 -0500
Received: from exim by ietf-mx with spam-scanned (Exim 4.12)
	id 1B4184-0004xm-00
	for rtgwg-web-archive@ietf.org; Thu, 18 Mar 2004 12:16:24 -0500
Received: from optimus.ietf.org ([132.151.1.19])
	by ietf-mx with esmtp (Exim 4.12)
	id 1B4176-0004vE-00
	for rtgwg-web-archive@ietf.org; Thu, 18 Mar 2004 12:15:24 -0500
Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1B416k-0006t0-IY; Thu, 18 Mar 2004 12:15:02 -0500
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1B416C-0006qw-OK
	for rtgwg@optimus.ietf.org; Thu, 18 Mar 2004 12:14:28 -0500
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id MAA25765
	for <rtgwg@ietf.org>; Thu, 18 Mar 2004 12:14:25 -0500 (EST)
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 1B416B-0004sf-00
	for rtgwg@ietf.org; Thu, 18 Mar 2004 12:14:27 -0500
Received: from exim by ietf-mx with spam-scanned (Exim 4.12)
	id 1B415L-0004qm-00
	for rtgwg@ietf.org; Thu, 18 Mar 2004 12:13:35 -0500
Received: from netcore.fi ([193.94.160.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 1B414b-0004lA-00
	for rtgwg@ietf.org; Thu, 18 Mar 2004 12:12:49 -0500
Received: from localhost (pekkas@localhost)
	by netcore.fi (8.11.6/8.11.6) with ESMTP id i2IHCG203357;
	Thu, 18 Mar 2004 19:12:16 +0200
Date: Thu, 18 Mar 2004 19:12:16 +0200 (EET)
From: Pekka Savola <pekkas@netcore.fi>
To: David Meyer <dmm@1-4-5.net>
cc: rtgwg@ietf.org
Subject: Re: I-D ACTION:draft-ietf-rtgwg-rfc3682bis-00.txt
In-Reply-To: <20040318160641.GA2079@1-4-5.net>
Message-ID: <Pine.LNX.4.44.0403181904231.1652-100000@netcore.fi>
MIME-Version: 1.0
Content-Type: TEXT/PLAIN; charset=US-ASCII
Sender: rtgwg-admin@ietf.org
Errors-To: rtgwg-admin@ietf.org
X-BeenThere: rtgwg@ietf.org
X-Mailman-Version: 2.0.12
Precedence: bulk
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/rtgwg>,
	<mailto:rtgwg-request@ietf.org?subject=unsubscribe>
List-Id: <rtgwg.ietf.org>
List-Post: <mailto:rtgwg@ietf.org>
List-Help: <mailto:rtgwg-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/rtgwg>,
	<mailto:rtgwg-request@ietf.org?subject=subscribe>
X-Spam-Checker-Version: SpamAssassin 2.60 (1.212-2003-09-23-exp) on 
	ietf-mx.ietf.org
X-Spam-Status: No, hits=0.0 required=5.0 tests=AWL autolearn=no version=2.60

On Thu, 18 Mar 2004, David Meyer wrote:
> >> Sigh.  So blatant typo in sect 3, i.b).  Hopefully, this should be 
> >> rather obvious from the other text.
> 
> 	This is interesting because this is one of the sections
> 	that was (explicitly) changed (as you no doubt know). In
> 	any event, can you be more specific.

I was just referring to the only substantial change made between the 
versions:

3682:
          (b). If the inbound TTL is 255 (for a directly
               connected peer), or 255-(configured-range-of-acceptable-hops)
               (for multi-hop peers), the packet is NOT
               processed. [...]

3682bis:
          (b). If the inbound TTL is less than 255 (for a directly
               connected peer), or 255-(configured-range-of-acceptable-hops)
               (for multi-hop peers), the packet is NOT
               processed. [...]

> >> The bad news is that this document inherits all the typos etc. that
> >> were fixed by RFC-editor; just wdiff RFC3682 and this to see that.
> 
> 	I have to find a wdiff that will build on fedora then
> 	I'll do so. 

In the meantime, I've put it at:

http://netcore.fi/pekkas/ietf/temp/rfc3682bis.html

-- 
Pekka Savola                 "You each name yourselves king, yet the
Netcore Oy                    kingdom bleeds."
Systems. Networks. Security. -- George R.R. Martin: A Clash of Kings


_______________________________________________
Rtgwg mailing list
Rtgwg@ietf.org
https://www1.ietf.org/mailman/listinfo/rtgwg



From exim@www1.ietf.org  Thu Mar 18 12:49:00 2004
Received: from optimus.ietf.org (optimus.ietf.org [132.151.1.19])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id MAA26802
	for <rtgwg-archive@odin.ietf.org>; Thu, 18 Mar 2004 12:49:00 -0500 (EST)
Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1B41dC-0001Ja-BT
	for rtgwg-archive@odin.ietf.org; Thu, 18 Mar 2004 12:48:34 -0500
Received: (from exim@localhost)
	by www1.ietf.org (8.12.8/8.12.8/Submit) id i2IHmY7x005054
	for rtgwg-archive@odin.ietf.org; Thu, 18 Mar 2004 12:48:34 -0500
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1B41dB-0001JR-G4
	for rtgwg-web-archive@optimus.ietf.org; Thu, 18 Mar 2004 12:48:33 -0500
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id MAA26781
	for <rtgwg-web-archive@ietf.org>; Thu, 18 Mar 2004 12:48:29 -0500 (EST)
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 1B41d9-0006cH-00
	for rtgwg-web-archive@ietf.org; Thu, 18 Mar 2004 12:48:31 -0500
Received: from exim by ietf-mx with spam-scanned (Exim 4.12)
	id 1B41cH-0006Xz-00
	for rtgwg-web-archive@ietf.org; Thu, 18 Mar 2004 12:47:38 -0500
Received: from optimus.ietf.org ([132.151.1.19])
	by ietf-mx with esmtp (Exim 4.12)
	id 1B41bO-0006UW-00
	for rtgwg-web-archive@ietf.org; Thu, 18 Mar 2004 12:46:42 -0500
Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1B41ak-0000x5-P0; Thu, 18 Mar 2004 12:46:02 -0500
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1B41aE-0000u3-35
	for rtgwg@optimus.ietf.org; Thu, 18 Mar 2004 12:45:30 -0500
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id MAA26701
	for <rtgwg@ietf.org>; Thu, 18 Mar 2004 12:45:26 -0500 (EST)
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 1B41aC-0006Pa-00
	for rtgwg@ietf.org; Thu, 18 Mar 2004 12:45:28 -0500
Received: from exim by ietf-mx with spam-scanned (Exim 4.12)
	id 1B41ZF-0006Nn-00
	for rtgwg@ietf.org; Thu, 18 Mar 2004 12:44:29 -0500
Received: from m106.maoz.com ([205.167.76.9])
	by ietf-mx with esmtp (Exim 4.12)
	id 1B41Ya-0006LX-00
	for rtgwg@ietf.org; Thu, 18 Mar 2004 12:43:48 -0500
Received: from m106.maoz.com (localhost.localdomain [127.0.0.1])
	by m106.maoz.com (8.12.11/8.12.11) with ESMTP id i2IHhEYj006700;
	Thu, 18 Mar 2004 09:43:14 -0800
Received: (from dmm@localhost)
	by m106.maoz.com (8.12.11/8.12.10/Submit) id i2IHhEcg006699;
	Thu, 18 Mar 2004 09:43:14 -0800
X-Authentication-Warning: m106.maoz.com: dmm set sender to dmm@1-4-5.net using -f
Date: Thu, 18 Mar 2004 09:43:14 -0800
From: David Meyer <dmm@1-4-5.net>
To: Pekka Savola <pekkas@netcore.fi>
Cc: rtgwg@ietf.org
Subject: Re: I-D ACTION:draft-ietf-rtgwg-rfc3682bis-00.txt
Message-ID: <20040318174314.GA6675@1-4-5.net>
References: <20040318160641.GA2079@1-4-5.net> <Pine.LNX.4.44.0403181904231.1652-100000@netcore.fi>
Mime-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
In-Reply-To: <Pine.LNX.4.44.0403181904231.1652-100000@netcore.fi>
User-Agent: Mutt/1.4.1i
X-public-key: http://www.1-4-5.net/~dmm/public-key.asc
X-philosophy: "I just had to let it go" -- John Lennon
Sender: rtgwg-admin@ietf.org
Errors-To: rtgwg-admin@ietf.org
X-BeenThere: rtgwg@ietf.org
X-Mailman-Version: 2.0.12
Precedence: bulk
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/rtgwg>,
	<mailto:rtgwg-request@ietf.org?subject=unsubscribe>
List-Id: <rtgwg.ietf.org>
List-Post: <mailto:rtgwg@ietf.org>
List-Help: <mailto:rtgwg-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/rtgwg>,
	<mailto:rtgwg-request@ietf.org?subject=subscribe>
X-Spam-Checker-Version: SpamAssassin 2.60 (1.212-2003-09-23-exp) on 
	ietf-mx.ietf.org
X-Spam-Status: No, hits=0.0 required=5.0 tests=AWL autolearn=no version=2.60

On Thu, Mar 18, 2004 at 07:12:16PM +0200, Pekka Savola wrote:
>> On Thu, 18 Mar 2004, David Meyer wrote:
>> > >> Sigh.  So blatant typo in sect 3, i.b).  Hopefully, this should be 
>> > >> rather obvious from the other text.
>> > 
>> > 	This is interesting because this is one of the sections
>> > 	that was (explicitly) changed (as you no doubt know). In
>> > 	any event, can you be more specific.
>> 
>> I was just referring to the only substantial change made between the 
>> versions:
>> 
>> 3682:
>>           (b). If the inbound TTL is 255 (for a directly
>>                connected peer), or 255-(configured-range-of-acceptable-hops)
>>                (for multi-hop peers), the packet is NOT
>>                processed. [...]
>> 
>> 3682bis:
>>           (b). If the inbound TTL is less than 255 (for a directly
>>                connected peer), or 255-(configured-range-of-acceptable-hops)
>>                (for multi-hop peers), the packet is NOT
>>                processed. [...]
>> 
>> > >> The bad news is that this document inherits all the typos etc. that
>> > >> were fixed by RFC-editor; just wdiff RFC3682 and this to see that.
>> > 
>> > 	I have to find a wdiff that will build on fedora then
>> > 	I'll do so. 
>> 
>> In the meantime, I've put it at:
>> 
>> http://netcore.fi/pekkas/ietf/temp/rfc3682bis.html

	Thanks. I was able to get it built (and thanks for the
	suggestion to look at what the RFC-Editor did). In any
	event, I'm posting -01 now, so it will be there rsn.

	Dave

_______________________________________________
Rtgwg mailing list
Rtgwg@ietf.org
https://www1.ietf.org/mailman/listinfo/rtgwg



From exim@www1.ietf.org  Fri Mar 19 16:10:01 2004
Received: from optimus.ietf.org (optimus.ietf.org [132.151.1.19])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id QAA22948
	for <rtgwg-archive@odin.ietf.org>; Fri, 19 Mar 2004 16:10:01 -0500 (EST)
Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1B4RFE-0008Ar-QC
	for rtgwg-archive@odin.ietf.org; Fri, 19 Mar 2004 16:09:32 -0500
Received: (from exim@localhost)
	by www1.ietf.org (8.12.8/8.12.8/Submit) id i2JL9WjV031417
	for rtgwg-archive@odin.ietf.org; Fri, 19 Mar 2004 16:09:32 -0500
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1B4RFE-0008Ae-Kl
	for rtgwg-web-archive@optimus.ietf.org; Fri, 19 Mar 2004 16:09:32 -0500
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id QAA22914
	for <rtgwg-web-archive@ietf.org>; Fri, 19 Mar 2004 16:09:30 -0500 (EST)
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 1B4RFD-0001vN-00
	for rtgwg-web-archive@ietf.org; Fri, 19 Mar 2004 16:09:31 -0500
Received: from exim by ietf-mx with spam-scanned (Exim 4.12)
	id 1B4REN-0001q6-00
	for rtgwg-web-archive@ietf.org; Fri, 19 Mar 2004 16:08:40 -0500
Received: from optimus.ietf.org ([132.151.1.19])
	by ietf-mx with esmtp (Exim 4.12)
	id 1B4RDn-0001k2-00
	for rtgwg-web-archive@ietf.org; Fri, 19 Mar 2004 16:08:04 -0500
Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1B4RDn-0007sc-T1; Fri, 19 Mar 2004 16:08:03 -0500
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1B4RCx-0007bk-Ah
	for rtgwg@optimus.ietf.org; Fri, 19 Mar 2004 16:07:11 -0500
Received: from CNRI.Reston.VA.US (localhost [127.0.0.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id QAA22719;
	Fri, 19 Mar 2004 16:07:08 -0500 (EST)
Message-Id: <200403192107.QAA22719@ietf.org>
Mime-Version: 1.0
Content-Type: Multipart/Mixed; Boundary="NextPart"
To: IETF-Announce: ;
Cc: rtgwg@ietf.org
From: Internet-Drafts@ietf.org
Reply-to: Internet-Drafts@ietf.org
Subject: I-D ACTION:draft-ietf-rtgwg-rfc3682bis-01.txt
Date: Fri, 19 Mar 2004 16:07:08 -0500
Sender: rtgwg-admin@ietf.org
Errors-To: rtgwg-admin@ietf.org
X-BeenThere: rtgwg@ietf.org
X-Mailman-Version: 2.0.12
Precedence: bulk
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/rtgwg>,
	<mailto:rtgwg-request@ietf.org?subject=unsubscribe>
List-Id: <rtgwg.ietf.org>
List-Post: <mailto:rtgwg@ietf.org>
List-Help: <mailto:rtgwg-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/rtgwg>,
	<mailto:rtgwg-request@ietf.org?subject=subscribe>
X-Spam-Checker-Version: SpamAssassin 2.60 (1.212-2003-09-23-exp) on 
	ietf-mx.ietf.org
X-Spam-Status: No, hits=0.5 required=5.0 tests=AWL,MIME_BOUND_NEXTPART,
	NO_REAL_NAME autolearn=no version=2.60

--NextPart

A New Internet-Draft is available from the on-line Internet-Drafts directories.
This draft is a work item of the Routing Area Working Group Working Group of the IETF.

	Title		: The Generalized TTL Security Mechanism (GTSM)
	Author(s)	: V. Gill, J. Heasley, D. Meyer
	Filename	: draft-ietf-rtgwg-rfc3682bis-01.txt
	Pages		: 14
	Date		: 2004-3-18
	
The use of a packet's TTL (IPv4) or Hop Limit (IPv6) to protect a
   protocol stack from CPU-utilization based attacks has been proposed
   in many settings (see for example, RFC 2461). This document
   generalizes these techniques for use by other protocols such as BGP
   (RFC 1771), MSDP, Bidirectional Forwarding Detection, and LDP (RFC
   3036). While the Generalized TTL Security Mechanism (GTSM)  is most
   effective in protecting directly connected protocol peers, it can
   also provide a lower level of protection to multi-hop sessions. GTSM
   is not directly applicable to protocols employing flooding mechanisms
   (e.g., multicast), and use of multi-hop GTSM should be considered on
   a case-by-case basis.

A URL for this Internet-Draft is:
http://www.ietf.org/internet-drafts/draft-ietf-rtgwg-rfc3682bis-01.txt

To remove yourself from the IETF Announcement list, send a message to 
ietf-announce-request with the word unsubscribe in the body of the message.

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-rtgwg-rfc3682bis-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-rtgwg-rfc3682bis-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:	<2004-3-18153521.I-D@ietf.org>

ENCODING mime
FILE /internet-drafts/draft-ietf-rtgwg-rfc3682bis-01.txt

--OtherAccess
Content-Type: Message/External-body;
	name="draft-ietf-rtgwg-rfc3682bis-01.txt";
	site="ftp.ietf.org";
	access-type="anon-ftp";
	directory="internet-drafts"

Content-Type: text/plain
Content-ID:	<2004-3-18153521.I-D@ietf.org>

--OtherAccess--

--NextPart--



_______________________________________________
Rtgwg mailing list
Rtgwg@ietf.org
https://www1.ietf.org/mailman/listinfo/rtgwg



From exim@www1.ietf.org  Fri Mar 19 20:58:06 2004
Received: from optimus.ietf.org (optimus.ietf.org [132.151.1.19])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id UAA05743
	for <rtgwg-archive@odin.ietf.org>; Fri, 19 Mar 2004 20:58:06 -0500 (EST)
Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1B4Vk2-0005Eg-6Y
	for rtgwg-archive@odin.ietf.org; Fri, 19 Mar 2004 20:57:38 -0500
Received: (from exim@localhost)
	by www1.ietf.org (8.12.8/8.12.8/Submit) id i2K1vci9020120
	for rtgwg-archive@odin.ietf.org; Fri, 19 Mar 2004 20:57:38 -0500
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1B4Vk1-0005ER-U7
	for rtgwg-web-archive@optimus.ietf.org; Fri, 19 Mar 2004 20:57:37 -0500
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id UAA05735
	for <rtgwg-web-archive@ietf.org>; Fri, 19 Mar 2004 20:57:35 -0500 (EST)
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 1B4Vjz-0006Mn-00
	for rtgwg-web-archive@ietf.org; Fri, 19 Mar 2004 20:57:35 -0500
Received: from exim by ietf-mx with spam-scanned (Exim 4.12)
	id 1B4Vj2-0006Gz-00
	for rtgwg-web-archive@ietf.org; Fri, 19 Mar 2004 20:56:36 -0500
Received: from optimus.ietf.org ([132.151.1.19])
	by ietf-mx with esmtp (Exim 4.12)
	id 1B4ViW-0006C3-00
	for rtgwg-web-archive@ietf.org; Fri, 19 Mar 2004 20:56:04 -0500
Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1B4ViT-00057t-Cy; Fri, 19 Mar 2004 20:56:01 -0500
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1B4VgP-00050R-26
	for rtgwg@optimus.ietf.org; Fri, 19 Mar 2004 20:53:53 -0500
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id UAA05593
	for <rtgwg@ietf.org>; Fri, 19 Mar 2004 20:53:50 -0500 (EST)
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 1B4VgM-00060m-00
	for rtgwg@ietf.org; Fri, 19 Mar 2004 20:53:50 -0500
Received: from exim by ietf-mx with spam-scanned (Exim 4.12)
	id 1B4Vfd-0005tM-00
	for rtgwg@ietf.org; Fri, 19 Mar 2004 20:53:05 -0500
Received: from psg.com ([147.28.0.62] ident=mailnull)
	by ietf-mx with esmtp (Exim 4.12)
	id 1B4VeU-0005jN-00
	for rtgwg@ietf.org; Fri, 19 Mar 2004 20:51:54 -0500
Received: from [147.28.0.62] (helo=127.0.0.1)
	by psg.com with esmtp (Exim 4.30; FreeBSD)
	id 1B4VeV-0007S9-4S
	for rtgwg@ietf.org; Sat, 20 Mar 2004 01:51:55 +0000
Date: Fri, 19 Mar 2004 17:51:21 -0800
From: Alex Zinin <zinin@psg.com>
X-Mailer: The Bat! (v1.62i) Personal
Reply-To: Alex Zinin <zinin@psg.com>
X-Priority: 3 (Normal)
Message-ID: <17320746772.20040319175121@psg.com>
To: rtgwg@ietf.org
Subject: Review Call: draft-hsmit-mpls-igp-spf-01.txt
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit
Content-Transfer-Encoding: 7bit
Sender: rtgwg-admin@ietf.org
Errors-To: rtgwg-admin@ietf.org
X-BeenThere: rtgwg@ietf.org
X-Mailman-Version: 2.0.12
Precedence: bulk
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/rtgwg>,
	<mailto:rtgwg-request@ietf.org?subject=unsubscribe>
List-Id: <rtgwg.ietf.org>
List-Post: <mailto:rtgwg@ietf.org>
List-Help: <mailto:rtgwg-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/rtgwg>,
	<mailto:rtgwg-request@ietf.org?subject=subscribe>
X-Spam-Checker-Version: SpamAssassin 2.60 (1.212-2003-09-23-exp) on 
	ietf-mx.ietf.org
X-Spam-Status: No, hits=0.3 required=5.0 tests=AWL,RCVD_NUMERIC_HELO 
	autolearn=no version=2.60
Content-Transfer-Encoding: 7bit
Content-Transfer-Encoding: 7bit

Folks-

 In preparation for the WG Last Call that will be started in a few weeks, we
 would like to solicit reviews of the draft-hsmit-mpls-igp-spf-01.txt document.
 The document is a WG item with the target status as an Informational RFC.

 Abstract below:

   This document describes how conventional hop-by-hop link-state
   routing protocols interact with new Traffic Engineering capabilities
   to create IGP shortcuts.  In particular this document describes how
   Dijkstra's SPF algorithm should be adapted so that link-state IGPs
   will calculate IP routes to forward traffic over tunnels that are
   set up by Traffic Engineering.

 The document is available at
 http://www.ietf.org/internet-drafts/draft-hsmit-mpls-igp-spf-01.txt
   
 Please send your comments to rtgwg@ietf.org
   
-- 
Alex
http://www.psg.com/~zinin/


_______________________________________________
Rtgwg mailing list
Rtgwg@ietf.org
https://www1.ietf.org/mailman/listinfo/rtgwg



From exim@www1.ietf.org  Sat Mar 20 12:51:29 2004
Received: from optimus.ietf.org (optimus.ietf.org [132.151.1.19])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id MAA17563
	for <rtgwg-archive@odin.ietf.org>; Sat, 20 Mar 2004 12:51:29 -0500 (EST)
Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1B4kcg-0004HM-4d
	for rtgwg-archive@odin.ietf.org; Sat, 20 Mar 2004 12:51:02 -0500
Received: (from exim@localhost)
	by www1.ietf.org (8.12.8/8.12.8/Submit) id i2KHp1C4016320
	for rtgwg-archive@odin.ietf.org; Sat, 20 Mar 2004 12:51:01 -0500
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1B4kcf-0004F3-2w
	for rtgwg-web-archive@optimus.ietf.org; Sat, 20 Mar 2004 12:51:01 -0500
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id MAA17558
	for <rtgwg-web-archive@ietf.org>; Sat, 20 Mar 2004 12:50:57 -0500 (EST)
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 1B4kcd-0002mt-00
	for rtgwg-web-archive@ietf.org; Sat, 20 Mar 2004 12:50:59 -0500
Received: from exim by ietf-mx with spam-scanned (Exim 4.12)
	id 1B4kbi-0002hj-00
	for rtgwg-web-archive@ietf.org; Sat, 20 Mar 2004 12:50:04 -0500
Received: from optimus.ietf.org ([132.151.1.19])
	by ietf-mx with esmtp (Exim 4.12)
	id 1B4kau-0002cY-00
	for rtgwg-web-archive@ietf.org; Sat, 20 Mar 2004 12:49:12 -0500
Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1B4kaj-00049F-48; Sat, 20 Mar 2004 12:49:01 -0500
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1B4kZn-00043S-30
	for rtgwg@optimus.ietf.org; Sat, 20 Mar 2004 12:48:03 -0500
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id MAA17501
	for <rtgwg@ietf.org>; Sat, 20 Mar 2004 12:47:59 -0500 (EST)
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 1B4kZl-0002Vx-00
	for rtgwg@ietf.org; Sat, 20 Mar 2004 12:48:01 -0500
Received: from exim by ietf-mx with spam-scanned (Exim 4.12)
	id 1B4kYo-0002QH-00
	for rtgwg@ietf.org; Sat, 20 Mar 2004 12:47:03 -0500
Received: from smtp2.procket.com ([65.174.124.37])
	by ietf-mx with esmtp (Exim 4.12)
	id 1B4kYH-0002F5-00
	for rtgwg@ietf.org; Sat, 20 Mar 2004 12:46:29 -0500
Received: from miata.procket.com (mil0-fw00-d-1.procket.com [65.174.124.60])
	by smtp2.procket.com (8.12.8p1/8.12.1) with ESMTP id i2KJqmAw051476;
	Sat, 20 Mar 2004 11:52:48 -0800 (PST)
Received: from exchangefe2.na.procket.com (email.na.procket.com [10.1.7.252])
	by miata.procket.com (8.12.1/8.12.1) with ESMTP id i2KHjhd1017753;
	Sat, 20 Mar 2004 09:45:43 -0800 (PST)
Received: from [127.0.0.1] ([10.1.1.1]) by exchangefe2.na.procket.com with Microsoft SMTPSVC(5.0.2195.6713);
	 Sat, 20 Mar 2004 09:45:43 -0800
In-Reply-To: <17320746772.20040319175121@psg.com>
References: <17320746772.20040319175121@psg.com>
Mime-Version: 1.0 (Apple Message framework v612)
Content-Type: text/plain; charset=US-ASCII; format=flowed
Message-Id: <6835954C-7A96-11D8-B567-00039303E9E2@rawdofmt.org>
Content-Transfer-Encoding: quoted-printable
Cc: rtgwg@ietf.org
From: Christian Hopps <chopps@rawdofmt.org>
Subject: Re: Review Call: draft-hsmit-mpls-igp-spf-01.txt
Date: Sat, 20 Mar 2004 09:45:41 -0800
To: Alex Zinin <zinin@psg.com>
X-Mailer: Apple Mail (2.612)
X-OriginalArrivalTime: 20 Mar 2004 17:45:43.0304 (UTC) FILETIME=[2AC22080:01C40EA3]
Content-Transfer-Encoding: quoted-printable
Sender: rtgwg-admin@ietf.org
Errors-To: rtgwg-admin@ietf.org
X-BeenThere: rtgwg@ietf.org
X-Mailman-Version: 2.0.12
Precedence: bulk
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/rtgwg>,
	<mailto:rtgwg-request@ietf.org?subject=unsubscribe>
List-Id: <rtgwg.ietf.org>
List-Post: <mailto:rtgwg@ietf.org>
List-Help: <mailto:rtgwg-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/rtgwg>,
	<mailto:rtgwg-request@ietf.org?subject=subscribe>
X-Spam-Checker-Version: SpamAssassin 2.60 (1.212-2003-09-23-exp) on 
	ietf-mx.ietf.org
X-Spam-Status: No, hits=0.0 required=5.0 tests=none autolearn=no version=2.60
Content-Transfer-Encoding: quoted-printable
Content-Transfer-Encoding: quoted-printable

>         Calculating IGP Routes Over Traffic Engineering Tunnels
>
>                     draft-shen-mpls-igp-spf-01.txt

[...]

Note, this correctly states when moved to PATHS.

>    During SPF, when a router finds the path to a new node (in other
>    words, this new node is moved from the TENTative list to the PATHS
>    list), the router must determine the first-hop information.  There
>    are three possible ways to do this:
>
>       - Examine the list of tail-end routers directly reachable via a
>         TE-tunnel. If there is a TE-tunnel to this node, we use the
>         TE-tunnel as the first-hop.
>
>       - If there is no TE-tunnel, and the node is directly connected,=20=

> we
>         will use the first-hop information from the adjacency =
database.
>
>       - If the node is not directly connected, and is not directly
>         reachable via a TE-tunnel, we will copy the first-hop
>         information from the parent node(s) to the new node.

[...]

> 5. Special cases and exceptions
>
>    The Shortest Path First algorithm will find equal-cost parallel=20
> paths
>    to destinations. The enhancement described in this document does =
not
>    change this. Traffic can be forwarded over one or more native IP
>    paths, over one or more TE-tunnels, or over a combination of native
>    IP paths and TE-tunnels.
>
>    A special situation occurs in the following topology:
>
>
>    rtrA -- rtrB -- rtrC
>             |       |
>            rtrD -- rtrE
>
>
>    Assume all links have the same cost. Assume a TE-tunnel is set up
>    from rtrA to rtrD. When the SPF calculation puts rtrC on the
>    TENTative list, it will realize that rtrC is not directly =
connected,
>    and thus it will use the first-hop information from the parent.=20
> Which
>    is rtrB.  When the SPF calculation on rtrA puts rtrD on the=20
> TENTative
>    list, it realizes that rtrD is the tail-end of a TE-tunnel. Thus=20
> rtrA
>    will install a route to rtrD via the TE-tunnel, and not via rtrB.

This incorrectly indicates "puts rtrD on the TENTative list..." If a TE=20=

nexthop will replace existing nexthops for rtrD it will be done when=20
rtrD is placed in PATHS.

[...]

> 6. Metric adjustment of IP routes over TE-tunnels
>
>    When an IGP route is installed in the routing table with a =
TE-tunnel
>    as next hop, an interesting question is what should be the cost or
>    metric of this route ?  The most obvious answer is to assign a=20
> metric
>    that is the same as the IGP metric of the native IP path as if the
>    TE-tunnels did not exist.  For example, rtrA can reach rtrC over a
>    path with a cost of 20. X is an IP prefix advertised by rtrC. We
>    install the route to X in rtrA's routing table with a cost of 20.
>    When a TE-tunnel from rtrA to rtrC comes up, by default the route =
is
>    still installed with metric of 20, only the next-hop information =
for
>    X is changed.
>
>    While this scheme works well, in some networks it might be useful =
to
>    change the cost of the path over a TE-tunnel, to make the route =
over
>    the TE-tunnel less or more preferred than other routes.
>
>    For instance when equal cost paths exist over a TE-tunnel and over =
a
>    native IP path, by adjusting the cost of the path over the=20
> TE-tunnel,
>    we can force traffic to prefer the path via the TE-tunnel, to =
prefer
>    the native IP path, or to load-balance among them. Another example=20=

> is
>    when multiple TE-tunnels go to the same or different destinations.
>    Adjusting TE-tunnel metrics can force the traffic to prefer some =
TE-
>    tunnels over others regardless of underlining IGP cost to those
>    destinations.
>
>    Setting a manual metric on a TE-tunnel does not impact the SPF
>    algorithm itself.  It only affects comparison of the new route with
>    existing routes in the routing table. Existing routes can be either
>    IP routes to another router that advertises the same IP prefix, or=20=

> it
>    can be a path to the same router, but via a different outgoing
>    interface or different TE-tunnel.  All routes to IP prefixes
>    advertised by the tail-end router will be affected by the TE-tunnel
>    metric. Also the metrics of paths to routers that are downstream of
>    the tail-end router will be influenced by the manual TE-tunnel
>    metric.
>
>    This mechanism is loop free since the TE-tunnels are source-routed.
>    The end result of TE-tunnel metric adjustment is more control over
>    traffic loadsharing. If there is only one way to reach a particular
>    IP prefix through a single TE-tunnel, then no matter what metric is
>    assigned, the traffic has only one path to go.

The mechanism is loop free b/c the source routed tunnels are only=20
utilized after a node is placed in PATHS. This is critical, and I think=20=

should be stated. Simply shoving a packet down a source routed tunnel=20
doesn't guarantee that it won't loop back. The fact that the tunnel was=20=

chosen only after SPF guaranteed the tunnel endpoint was truly=20
downstream towards the destination is what makes it loop free.

>    When the manual TE-tunnel metric is configured to be larger than
>    the IGP native path metric, this TE-tunnel can not be used in the
>    SPF calculation. Otherwise a routing loop may be formed. Here is
>    an example:

Note stating "this TE-tunnel can not be used in the SPF calculation" is=20=

confusing, as its critical that TE-tunnels *not* be used in the SPF=20
calculation.

This is stated earlier in this section:

"Setting a manual metric on a TE-tunnel does not impact the SPF=20
algorithm itself."

The only thing the TE tunnel metric can affect is whether TE tunnel=20
nexthop is chosen over the IGP nexthop when a route is being installed,=20=

and when *IGP metric* based ECMP routes are being considered.

> Shen, Smit                 Expires June 2004                    [Page=20=

> 4]
> =0C
> Internet Draft          IGP ShortCut Over MPLS LSPs        December=20
> 2003
>
>
>       (src)  2         2
>         A ------ B ------- C
>         |        =3D=3D=3D=3D=3D=3D=3D=3D=3D>|
>        5|            30    |2
>         |                  |
>         D ---------------- E (dst)
>                  5
>
>    There is a TE-tunnel from B->C with manual tunnel metric of 30.
>    The shortest path from source A to destination E is A->B->C->E with
>    the path metric of 6, thus A will use B as the nexthop router. If
>    this TE tunnel could be used by B's SPF calculation with the
>    metric of 30 for the span of B->C, then B->C->E will have the path
>    metric of 32, but B->A->D->E path will only have the metric of 12.
>    So B would send the traffic back to A, a routing loop formed.
>
> 6.1. Absolute and relative metrics
>
>    It is possible to represent the TE-tunnel metric in two different
>    ways: an absolute (or fixed) metric or a relative metric, which is
>    merely an adjustment of the dynamic IGP metric as calculate by the
>    SPF computation.  When using an absolute metric on a TE-tunnel, the
>    cost of the IP routes in the routing table does not depend on the
>    topology of the network. Note that this fixed metric is not only=20
> used
>    to compute the cost of IP routes advertised by the router that is=20=

> the
>    tail-end of the TE-tunnel, but also for all the routes that are
>    downstream of this tail-end router.  For example, if we have TE-
>    tunnels to two core routers in a remote POP, and one of them is
>    assigned with absolute metric of 1, then all the traffic going to
>    that POP will traverse this low-metric TE-tunnel.
>
>    By setting a relative metric, the cost of IP routes in the routing
>    table is based on the IGP metric as calculated by the SPF
>    computation.  This relative metric can be a positive or a negative
>    number.  Not configuring a metric on a TE-tunnel is a special case=20=

> of
>    the relative metric scheme. No metric is the same as a relative
>    metric of 0.  The relative metric is bounded by minimum and maximum
>    allowed metric values while the positive metric disables the
>    TE-tunnel in the SPF calculation.

I've always thought that positive relative metrics are silly. Do we=20
really need this method for disabling use of the tunnel in the IGP?

Chris.


_______________________________________________
Rtgwg mailing list
Rtgwg@ietf.org
https://www1.ietf.org/mailman/listinfo/rtgwg



From exim@www1.ietf.org  Sat Mar 20 18:42:44 2004
Received: from optimus.ietf.org (optimus.ietf.org [132.151.1.19])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id SAA00873
	for <rtgwg-archive@odin.ietf.org>; Sat, 20 Mar 2004 18:42:44 -0500 (EST)
Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1B4q6c-0008SM-52
	for rtgwg-archive@odin.ietf.org; Sat, 20 Mar 2004 18:42:18 -0500
Received: (from exim@localhost)
	by www1.ietf.org (8.12.8/8.12.8/Submit) id i2KNgIfx032500
	for rtgwg-archive@odin.ietf.org; Sat, 20 Mar 2004 18:42:18 -0500
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1B4q6c-0008S7-0k
	for rtgwg-web-archive@optimus.ietf.org; Sat, 20 Mar 2004 18:42:18 -0500
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id SAA00868
	for <rtgwg-web-archive@ietf.org>; Sat, 20 Mar 2004 18:42:13 -0500 (EST)
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 1B4q6Z-0001cA-00
	for rtgwg-web-archive@ietf.org; Sat, 20 Mar 2004 18:42:15 -0500
Received: from exim by ietf-mx with spam-scanned (Exim 4.12)
	id 1B4q5e-0001WJ-00
	for rtgwg-web-archive@ietf.org; Sat, 20 Mar 2004 18:41:19 -0500
Received: from optimus.ietf.org ([132.151.1.19])
	by ietf-mx with esmtp (Exim 4.12)
	id 1B4q5O-0001QS-00
	for rtgwg-web-archive@ietf.org; Sat, 20 Mar 2004 18:41:02 -0500
Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1B4q5N-0008Lf-ET; Sat, 20 Mar 2004 18:41:01 -0500
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1B4q4Z-0008KU-Pw
	for rtgwg@optimus.ietf.org; Sat, 20 Mar 2004 18:40:11 -0500
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id SAA00762
	for <rtgwg@ietf.org>; Sat, 20 Mar 2004 18:40:07 -0500 (EST)
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 1B4q4W-0001OS-00
	for rtgwg@ietf.org; Sat, 20 Mar 2004 18:40:08 -0500
Received: from exim by ietf-mx with spam-scanned (Exim 4.12)
	id 1B4q3Z-0001IB-00
	for rtgwg@ietf.org; Sat, 20 Mar 2004 18:39:10 -0500
Received: from slb-smtpout-01.boeing.com ([130.76.64.48])
	by ietf-mx with esmtp (Exim 4.12)
	id 1B4q2e-00017Z-00
	for rtgwg@ietf.org; Sat, 20 Mar 2004 18:38:12 -0500
Received: from slb-av-02.boeing.com ([129.172.13.7])
	by slb-smtpout-01.boeing.com (8.9.2.MG.10092003/8.8.5-M2) with ESMTP id PAA12248;
	Sat, 20 Mar 2004 15:37:36 -0800 (PST)
Received: from stl-hub-01.boeing.com (localhost [127.0.0.1])
	by slb-av-02.boeing.com (8.9.3/8.9.2/MBS-AV-02) with ESMTP id PAA14948;
	Sat, 20 Mar 2004 15:37:36 -0800 (PST)
Received: from xch-nebh-01.ne.nos.boeing.com (xch-nebh-01.ne.nos.boeing.com [128.225.80.200])
	by stl-hub-01.boeing.com (8.11.3/8.11.3/MBS-LDAP-01) with ESMTP id i2KNaUQ06489;
	Sat, 20 Mar 2004 17:36:30 -0600 (CST)
Received: from XCH-NE-02.ne.nos.boeing.com ([128.225.80.202]) by xch-nebh-01.ne.nos.boeing.com with Microsoft SMTPSVC(5.0.2195.6662);
	 Sat, 20 Mar 2004 18:36:30 -0500
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: Review Call: draft-hsmit-mpls-igp-spf-01.txt
Date: Sat, 20 Mar 2004 18:36:29 -0500
Message-ID: <EF40C42ACAB7A649B2EAE70C19B6CD6E01B98957@xch-ne-02.ne.nos.boeing.com>
Thread-Topic: Review Call: draft-hsmit-mpls-igp-spf-01.txt
Thread-Index: AcQOHqEsu6l0ZmoRRxSLMSYGvFkoMwAtODVw
From: "Manfredi, Albert E" <albert.e.manfredi@boeing.com>
To: "Alex Zinin" <zinin@psg.com>, <rtgwg@ietf.org>
X-OriginalArrivalTime: 20 Mar 2004 23:36:30.0213 (UTC) FILETIME=[2BB19350:01C40ED4]
Content-Transfer-Encoding: quoted-printable
Sender: rtgwg-admin@ietf.org
Errors-To: rtgwg-admin@ietf.org
X-BeenThere: rtgwg@ietf.org
X-Mailman-Version: 2.0.12
Precedence: bulk
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/rtgwg>,
	<mailto:rtgwg-request@ietf.org?subject=unsubscribe>
List-Id: <rtgwg.ietf.org>
List-Post: <mailto:rtgwg@ietf.org>
List-Help: <mailto:rtgwg-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/rtgwg>,
	<mailto:rtgwg-request@ietf.org?subject=subscribe>
X-Spam-Checker-Version: SpamAssassin 2.60 (1.212-2003-09-23-exp) on 
	ietf-mx.ietf.org
X-Spam-Status: No, hits=0.0 required=5.0 tests=none autolearn=no version=2.60
Content-Transfer-Encoding: quoted-printable
Content-Transfer-Encoding: quoted-printable

This reminds me of the ATM shortcut I-D of years ago. One issue with =
that concept was proof of being loop-free, and another was that security =
holes might occur if certain routers along the path are allowed to be =
bypassed. But I always found the idea very interesting, and again here.

Anyway, I believe this is a typo?

4. Enhancement to the Shortest Path First computation

   During each step of the SPF computation, a router discovers the path
   to one node in the network. If that node is directly connected to the
   calculating router, the first-hop information is derived from the
   adjacency database. If a node is not directly connected to the
   calculating router, it ***inherents*** the first-hop information from =
the
   parent(s) of that node.

Assume that's meant to be "inherits," yes?

Bert


> -----Original Message-----
> From: Alex Zinin [mailto:zinin@psg.com]
> Sent: Friday, March 19, 2004 8:51 PM
> To: rtgwg@ietf.org
> Subject: Review Call: draft-hsmit-mpls-igp-spf-01.txt
>=20
>=20
> Folks-
>=20
>  In preparation for the WG Last Call that will be started in=20
> a few weeks, we
>  would like to solicit reviews of the=20
> draft-hsmit-mpls-igp-spf-01.txt document.
>  The document is a WG item with the target status as an=20
> Informational RFC.
>=20
>  Abstract below:
>=20
>    This document describes how conventional hop-by-hop link-state
>    routing protocols interact with new Traffic Engineering=20
> capabilities
>    to create IGP shortcuts.  In particular this document describes how
>    Dijkstra's SPF algorithm should be adapted so that link-state IGPs
>    will calculate IP routes to forward traffic over tunnels that are
>    set up by Traffic Engineering.
>=20
>  The document is available at
>  http://www.ietf.org/internet-drafts/draft-hsmit-mpls-igp-spf-01.txt
>   =20
>  Please send your comments to rtgwg@ietf.org
>   =20
> --=20
> Alex
> http://www.psg.com/~zinin/
>=20
>=20
> _______________________________________________
> Rtgwg mailing list
> Rtgwg@ietf.org
> https://www1.ietf.org/mailman/listinfo/rtgwg
>=20

_______________________________________________
Rtgwg mailing list
Rtgwg@ietf.org
https://www1.ietf.org/mailman/listinfo/rtgwg



From exim@www1.ietf.org  Sun Mar 21 02:20:19 2004
Received: from optimus.ietf.org (optimus.ietf.org [132.151.1.19])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id CAA29264
	for <rtgwg-archive@odin.ietf.org>; Sun, 21 Mar 2004 02:20:19 -0500 (EST)
Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1B4xFO-00062t-Vk
	for rtgwg-archive@odin.ietf.org; Sun, 21 Mar 2004 02:19:51 -0500
Received: (from exim@localhost)
	by www1.ietf.org (8.12.8/8.12.8/Submit) id i2L7JoGM023199
	for rtgwg-archive@odin.ietf.org; Sun, 21 Mar 2004 02:19:50 -0500
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1B4xFM-00061r-JF
	for rtgwg-web-archive@optimus.ietf.org; Sun, 21 Mar 2004 02:19:48 -0500
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id CAA29208
	for <rtgwg-web-archive@ietf.org>; Sun, 21 Mar 2004 02:19:46 -0500 (EST)
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 1B4xFJ-0006SP-00
	for rtgwg-web-archive@ietf.org; Sun, 21 Mar 2004 02:19:45 -0500
Received: from exim by ietf-mx with spam-scanned (Exim 4.12)
	id 1B4xEQ-0006Kz-00
	for rtgwg-web-archive@ietf.org; Sun, 21 Mar 2004 02:18:51 -0500
Received: from optimus.ietf.org ([132.151.1.19])
	by ietf-mx with esmtp (Exim 4.12)
	id 1B4xDg-0006Cj-00
	for rtgwg-web-archive@ietf.org; Sun, 21 Mar 2004 02:18:04 -0500
Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1B4xDc-0005Td-R0; Sun, 21 Mar 2004 02:18:00 -0500
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1B4xD8-0005E3-Uc
	for rtgwg@optimus.ietf.org; Sun, 21 Mar 2004 02:17:33 -0500
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id CAA28998
	for <rtgwg@ietf.org>; Sun, 21 Mar 2004 02:17:28 -0500 (EST)
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 1B4xD5-00069p-00
	for rtgwg@ietf.org; Sun, 21 Mar 2004 02:17:27 -0500
Received: from exim by ietf-mx with spam-scanned (Exim 4.12)
	id 1B4xCG-00061f-00
	for rtgwg@ietf.org; Sun, 21 Mar 2004 02:16:37 -0500
Received: from prattle.redback.com ([155.53.12.9])
	by ietf-mx with esmtp (Exim 4.12)
	id 1B4xBI-0005vJ-00
	for rtgwg@ietf.org; Sun, 21 Mar 2004 02:15:37 -0500
Received: from localhost (localhost [127.0.0.1])
	by prattle.redback.com (Postfix) with ESMTP
	id 22254595397; Sat, 20 Mar 2004 23:15:32 -0800 (PST)
Received: from prattle.redback.com ([127.0.0.1])
 by localhost (prattle [127.0.0.1]) (amavisd-new, port 10024) with ESMTP
 id 15421-09; Sat, 20 Mar 2004 23:15:31 -0800 (PST)
Received: from redback.com (malt.redback.com [155.53.12.41])
	by prattle.redback.com (Postfix) with ESMTP
	id 7DB01595392; Sat, 20 Mar 2004 23:15:31 -0800 (PST)
Received: from malt (localhost [127.0.0.1])
	by redback.com (8.9.3-LCCHA/8.9.3/null redback solaris client) with ESMTP id XAA15587;
	Sat, 20 Mar 2004 23:15:31 -0800 (PST)
Message-Id: <200403210715.XAA15587@redback.com>
To: Christian Hopps <chopps@rawdofmt.org>
Cc: Alex Zinin <zinin@psg.com>, rtgwg@ietf.org
Subject: Re: Review Call: draft-hsmit-mpls-igp-spf-01.txt 
In-reply-to: Mail from Christian Hopps <chopps@rawdofmt.org> 
 dated Sat, 20 Mar 2004 09:45:41 PST
 <6835954C-7A96-11D8-B567-00039303E9E2@rawdofmt.org> 
Date: Sat, 20 Mar 2004 23:15:31 -0800
From: Naiming Shen <naiming@redback.com>
X-Virus-Scanned: by amavisd-new at redback.com
Sender: rtgwg-admin@ietf.org
Errors-To: rtgwg-admin@ietf.org
X-BeenThere: rtgwg@ietf.org
X-Mailman-Version: 2.0.12
Precedence: bulk
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/rtgwg>,
	<mailto:rtgwg-request@ietf.org?subject=unsubscribe>
List-Id: <rtgwg.ietf.org>
List-Post: <mailto:rtgwg@ietf.org>
List-Help: <mailto:rtgwg-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/rtgwg>,
	<mailto:rtgwg-request@ietf.org?subject=subscribe>
X-Spam-Checker-Version: SpamAssassin 2.60 (1.212-2003-09-23-exp) on 
	ietf-mx.ietf.org
X-Spam-Status: No, hits=0.0 required=5.0 tests=AWL autolearn=no version=2.60


Christian,

thanks for the good comments, in replies inline.

<cut...>

 ] >
 ] >    rtrA -- rtrB -- rtrC
 ] >             |       |
 ] >            rtrD -- rtrE
 ] >
 ] >
 ] >    Assume all links have the same cost. Assume a TE-tunnel is set up
 ] >    from rtrA to rtrD. When the SPF calculation puts rtrC on the
 ] >    TENTative list, it will realize that rtrC is not directly =
 ] connected,
 ] >    and thus it will use the first-hop information from the parent.=20
 ] > Which
 ] >    is rtrB.  When the SPF calculation on rtrA puts rtrD on the=20
 ] > TENTative
 ] >    list, it realizes that rtrD is the tail-end of a TE-tunnel. Thus=20
 ] > rtrA
 ] >    will install a route to rtrD via the TE-tunnel, and not via rtrB.
 ] 
 ] This incorrectly indicates "puts rtrD on the TENTative list..." If a TE=20=
 ] 
 ] nexthop will replace existing nexthops for rtrD it will be done when=20
 ] rtrD is placed in PATHS.

You are correct. This one should have meant
 "takes rtrD off the TENTative list...".

<cut...>

 ] >
 ] >    This mechanism is loop free since the TE-tunnels are source-routed.
 ] >    The end result of TE-tunnel metric adjustment is more control over
 ] >    traffic loadsharing. If there is only one way to reach a particular
 ] >    IP prefix through a single TE-tunnel, then no matter what metric is
 ] >    assigned, the traffic has only one path to go.
 ] 
 ] The mechanism is loop free b/c the source routed tunnels are only=20
 ] utilized after a node is placed in PATHS. This is critical, and I think=20=
 ] 
 should be stated. Simply shoving a packet down a source routed tunnel=20
 ] doesn't guarantee that it won't loop back. The fact that the tunnel was=20=
 ] 
 ] chosen only after SPF guaranteed the tunnel endpoint was truly=20
 ] downstream towards the destination is what makes it loop free.

True, your reasoning is stronger, will add that.

 ] 
 ] >    When the manual TE-tunnel metric is configured to be larger than
 ] >    the IGP native path metric, this TE-tunnel can not be used in the
 ] >    SPF calculation. Otherwise a routing loop may be formed. Here is
 ] >    an example:
 ] 
 ] Note stating "this TE-tunnel can not be used in the SPF calculation" is=20=
 ] 
 ] confusing, as its critical that TE-tunnels *not* be used in the SPF=20
 ] calculation.

I'm not sure why this is confusing. It simply says the there may be
a problem using such a tunnel with such a metric. We don't want to
say that if certain conditions don't exist, then it's ok to use those
tunnels.

 ] 
 ] This is stated earlier in this section:
 ] 
 ] "Setting a manual metric on a TE-tunnel does not impact the SPF=20
 ] algorithm itself."
 ] 
 ] The only thing the TE tunnel metric can affect is whether TE tunnel=20
 ] nexthop is chosen over the IGP nexthop when a route is being installed,=20=
 ] 
 ] and when *IGP metric* based ECMP routes are being considered.
 ]

<cut...>
 
 ] >
 ] > 6.1. Absolute and relative metrics
 ] >
 ] >    It is possible to represent the TE-tunnel metric in two different
 ] >    ways: an absolute (or fixed) metric or a relative metric, which is
 ] >    merely an adjustment of the dynamic IGP metric as calculate by the
 ] >    SPF computation.  When using an absolute metric on a TE-tunnel, the
 ] >    cost of the IP routes in the routing table does not depend on the
 ] >    topology of the network. Note that this fixed metric is not only=20
 ] > used
 ] >    to compute the cost of IP routes advertised by the router that is=20=
 ] 
 ] > the
 ] >    tail-end of the TE-tunnel, but also for all the routes that are
 ] >    downstream of this tail-end router.  For example, if we have TE-
 ] >    tunnels to two core routers in a remote POP, and one of them is
 ] >    assigned with absolute metric of 1, then all the traffic going to
 ] >    that POP will traverse this low-metric TE-tunnel.
 ] >
 ] >    By setting a relative metric, the cost of IP routes in the routing
 ] >    table is based on the IGP metric as calculated by the SPF
 ] >    computation.  This relative metric can be a positive or a negative
 ] >    number.  Not configuring a metric on a TE-tunnel is a special case=20=
 ] 
 ] > of
 ] >    the relative metric scheme. No metric is the same as a relative
 ] >    metric of 0.  The relative metric is bounded by minimum and maximum
 ] >    allowed metric values while the positive metric disables the
 ] >    TE-tunnel in the SPF calculation.
 ] 
 ] I've always thought that positive relative metrics are silly. Do we=20
 ] really need this method for disabling use of the tunnel in the IGP?
 ] 

I don't have strong opinions either way. This is mainly for completeness.
Some implementations do have mechanism to assign positive metric. It's
mainly an implementation issue to allow it or not. But from documentation
point of view, it helps to explicitly mentioning this.

thanks.

 ] Chris.
 ] 
 ] 
 ] _______________________________________________
 ] Rtgwg mailing list
 ] Rtgwg@ietf.org
 ] https://www1.ietf.org/mailman/listinfo/rtgwg

- Naiming

_______________________________________________
Rtgwg mailing list
Rtgwg@ietf.org
https://www1.ietf.org/mailman/listinfo/rtgwg



From exim@www1.ietf.org  Sun Mar 21 02:37:01 2004
Received: from optimus.ietf.org (optimus.ietf.org [132.151.1.19])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id CAA00104
	for <rtgwg-archive@odin.ietf.org>; Sun, 21 Mar 2004 02:37:01 -0500 (EST)
Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1B4xVZ-0008IG-Bj
	for rtgwg-archive@odin.ietf.org; Sun, 21 Mar 2004 02:36:34 -0500
Received: (from exim@localhost)
	by www1.ietf.org (8.12.8/8.12.8/Submit) id i2L7aX3s031881
	for rtgwg-archive@odin.ietf.org; Sun, 21 Mar 2004 02:36:33 -0500
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1B4xVY-0008I4-SN
	for rtgwg-web-archive@optimus.ietf.org; Sun, 21 Mar 2004 02:36:32 -0500
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id CAA00098
	for <rtgwg-web-archive@ietf.org>; Sun, 21 Mar 2004 02:36:30 -0500 (EST)
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 1B4xVV-0000aV-00
	for rtgwg-web-archive@ietf.org; Sun, 21 Mar 2004 02:36:29 -0500
Received: from exim by ietf-mx with spam-scanned (Exim 4.12)
	id 1B4xUa-0000VD-00
	for rtgwg-web-archive@ietf.org; Sun, 21 Mar 2004 02:35:33 -0500
Received: from optimus.ietf.org ([132.151.1.19])
	by ietf-mx with esmtp (Exim 4.12)
	id 1B4xU6-0000Pa-00
	for rtgwg-web-archive@ietf.org; Sun, 21 Mar 2004 02:35:02 -0500
Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1B4xU5-0008As-6a; Sun, 21 Mar 2004 02:35:01 -0500
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1B4xTj-00089c-R1
	for rtgwg@optimus.ietf.org; Sun, 21 Mar 2004 02:34:39 -0500
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id CAA00008
	for <rtgwg@ietf.org>; Sun, 21 Mar 2004 02:34:37 -0500 (EST)
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 1B4xTg-0000Oo-00
	for rtgwg@ietf.org; Sun, 21 Mar 2004 02:34:36 -0500
Received: from exim by ietf-mx with spam-scanned (Exim 4.12)
	id 1B4xSs-0000Ii-00
	for rtgwg@ietf.org; Sun, 21 Mar 2004 02:33:47 -0500
Received: from prattle.redback.com ([155.53.12.9])
	by ietf-mx with esmtp (Exim 4.12)
	id 1B4xSH-0000B2-00
	for rtgwg@ietf.org; Sun, 21 Mar 2004 02:33:09 -0500
Received: from localhost (localhost [127.0.0.1])
	by prattle.redback.com (Postfix) with ESMTP
	id 3393459539D; Sat, 20 Mar 2004 23:33:10 -0800 (PST)
Received: from prattle.redback.com ([127.0.0.1])
 by localhost (prattle [127.0.0.1]) (amavisd-new, port 10024) with ESMTP
 id 17638-05; Sat, 20 Mar 2004 23:33:09 -0800 (PST)
Received: from redback.com (malt.redback.com [155.53.12.41])
	by prattle.redback.com (Postfix) with ESMTP
	id C3D7F59539C; Sat, 20 Mar 2004 23:33:09 -0800 (PST)
Received: from malt (localhost [127.0.0.1])
	by redback.com (8.9.3-LCCHA/8.9.3/null redback solaris client) with ESMTP id XAA15752;
	Sat, 20 Mar 2004 23:33:09 -0800 (PST)
Message-Id: <200403210733.XAA15752@redback.com>
To: "Manfredi, Albert E" <albert.e.manfredi@boeing.com>
Cc: "Alex Zinin" <zinin@psg.com>, rtgwg@ietf.org
Subject: Re: Review Call: draft-hsmit-mpls-igp-spf-01.txt 
In-reply-to: Mail from "Manfredi, Albert E" <albert.e.manfredi@boeing.com> 
 dated Sat, 20 Mar 2004 18:36:29 EST
 <EF40C42ACAB7A649B2EAE70C19B6CD6E01B98957@xch-ne-02.ne.nos.boeing.com> 
Date: Sat, 20 Mar 2004 23:33:09 -0800
From: Naiming Shen <naiming@redback.com>
X-Virus-Scanned: by amavisd-new at redback.com
Sender: rtgwg-admin@ietf.org
Errors-To: rtgwg-admin@ietf.org
X-BeenThere: rtgwg@ietf.org
X-Mailman-Version: 2.0.12
Precedence: bulk
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/rtgwg>,
	<mailto:rtgwg-request@ietf.org?subject=unsubscribe>
List-Id: <rtgwg.ietf.org>
List-Post: <mailto:rtgwg@ietf.org>
List-Help: <mailto:rtgwg-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/rtgwg>,
	<mailto:rtgwg-request@ietf.org?subject=subscribe>
X-Spam-Checker-Version: SpamAssassin 2.60 (1.212-2003-09-23-exp) on 
	ietf-mx.ietf.org
X-Spam-Status: No, hits=0.0 required=5.0 tests=AWL autolearn=no version=2.60


Bert,

 ] This reminds me of the ATM shortcut I-D of years ago. One issue with =
 ] that concept was proof of being loop-free,

Since we are sending traffic to a downstream node, or to a downstream's
downstream nodes, it has to be loop-free in the steady state. Allowing
the traffic to pass multi nodes in the middle to reach the same
tunnel-end node should not change the loop status. Although this
is not a formal proof;-)

 ] and another was that security =
 ] holes might occur if certain routers along the path are allowed to be =
 ] bypassed. But I always found the idea very interesting, and again here.

The IGP is running in the same area/level, usually is admined by
the same organization. If in some weired cases a provider runs IGP
to it's customers and also allow their customers setting MPLS TEs
directly into their center of the backbone nodes, then we have to
assume those providers know how to check security on those backbone nodes...

 ] 
 ] Anyway, I believe this is a typo?
 ] 
 ] 4. Enhancement to the Shortest Path First computation
 ] 
 ]    During each step of the SPF computation, a router discovers the path
 ]    to one node in the network. If that node is directly connected to the
 ]    calculating router, the first-hop information is derived from the
 ]    adjacency database. If a node is not directly connected to the
 ]    calculating router, it ***inherents*** the first-hop information from =
 ] the
 ]    parent(s) of that node.
 ] 
 ] Assume that's meant to be "inherits," yes?

yes, this is a typo, will correct that.

thanks!

 ] 
 ] Bert
 ] 
 ] 
 ] > -----Original Message-----
 ] > From: Alex Zinin [mailto:zinin@psg.com]
 ] > Sent: Friday, March 19, 2004 8:51 PM
 ] > To: rtgwg@ietf.org
 ] > Subject: Review Call: draft-hsmit-mpls-igp-spf-01.txt
 ] >=20
 ] >=20
 ] > Folks-
 ] >=20
 ] >  In preparation for the WG Last Call that will be started in=20
 ] > a few weeks, we
 ] >  would like to solicit reviews of the=20
 ] > draft-hsmit-mpls-igp-spf-01.txt document.
 ] >  The document is a WG item with the target status as an=20
 ] > Informational RFC.
 ] >=20
 ] >  Abstract below:
 ] >=20
 ] >    This document describes how conventional hop-by-hop link-state
 ] >    routing protocols interact with new Traffic Engineering=20
 ] > capabilities
 ] >    to create IGP shortcuts.  In particular this document describes how
 ] >    Dijkstra's SPF algorithm should be adapted so that link-state IGPs
 ] >    will calculate IP routes to forward traffic over tunnels that are
 ] >    set up by Traffic Engineering.
 ] >=20
 ] >  The document is available at
 ] >  http://www.ietf.org/internet-drafts/draft-hsmit-mpls-igp-spf-01.txt
 ] >   =20
 ] >  Please send your comments to rtgwg@ietf.org
 ] >   =20
 ] > --=20
 ] > Alex
 ] > http://www.psg.com/~zinin/
 ] >=20
 ] >=20
 ] > _______________________________________________
 ] > Rtgwg mailing list
 ] > Rtgwg@ietf.org
 ] > https://www1.ietf.org/mailman/listinfo/rtgwg
 ] >=20
 ] 
 ] _______________________________________________
 ] Rtgwg mailing list
 ] Rtgwg@ietf.org
 ] https://www1.ietf.org/mailman/listinfo/rtgwg

- Naiming

_______________________________________________
Rtgwg mailing list
Rtgwg@ietf.org
https://www1.ietf.org/mailman/listinfo/rtgwg



From exim@www1.ietf.org  Mon Mar 22 17:10:24 2004
Received: from optimus.ietf.org (optimus.ietf.org [132.151.1.19])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id RAA28093
	for <rtgwg-archive@odin.ietf.org>; Mon, 22 Mar 2004 17:10:24 -0500 (EST)
Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1B5XcK-0006Pm-Hn
	for rtgwg-archive@odin.ietf.org; Mon, 22 Mar 2004 17:09:57 -0500
Received: (from exim@localhost)
	by www1.ietf.org (8.12.8/8.12.8/Submit) id i2MM9udg024652
	for rtgwg-archive@odin.ietf.org; Mon, 22 Mar 2004 17:09:56 -0500
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1B5XcK-0006PX-Bs
	for rtgwg-web-archive@optimus.ietf.org; Mon, 22 Mar 2004 17:09:56 -0500
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id RAA28086
	for <rtgwg-web-archive@ietf.org>; Mon, 22 Mar 2004 17:09:53 -0500 (EST)
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 1B5XcI-00066U-00
	for rtgwg-web-archive@ietf.org; Mon, 22 Mar 2004 17:09:54 -0500
Received: from exim by ietf-mx with spam-scanned (Exim 4.12)
	id 1B5XbN-000615-00
	for rtgwg-web-archive@ietf.org; Mon, 22 Mar 2004 17:08:58 -0500
Received: from optimus.ietf.org ([132.151.1.19])
	by ietf-mx with esmtp (Exim 4.12)
	id 1B5Xaj-0005uY-00
	for rtgwg-web-archive@ietf.org; Mon, 22 Mar 2004 17:08:17 -0500
Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1B5XaX-0006BN-Sz; Mon, 22 Mar 2004 17:08:05 -0500
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1B5XLq-0005JF-TU
	for rtgwg@optimus.ietf.org; Mon, 22 Mar 2004 16:52:54 -0500
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id QAA27200
	for <rtgwg@ietf.org>; Mon, 22 Mar 2004 16:52:51 -0500 (EST)
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 1B5XLo-0004GC-00
	for rtgwg@ietf.org; Mon, 22 Mar 2004 16:52:52 -0500
Received: from exim by ietf-mx with spam-scanned (Exim 4.12)
	id 1B5XL4-00049Y-00
	for rtgwg@ietf.org; Mon, 22 Mar 2004 16:52:07 -0500
Received: from smtp2.procket.com ([65.174.124.37])
	by ietf-mx with esmtp (Exim 4.12)
	id 1B5XKS-00040i-00
	for rtgwg@ietf.org; Mon, 22 Mar 2004 16:51:28 -0500
Received: from miata.procket.com (mil0-fw00-d-1.procket.com [65.174.124.60])
	by smtp2.procket.com (8.12.8p1/8.12.1) with ESMTP id i2MNvxAw072837;
	Mon, 22 Mar 2004 15:57:59 -0800 (PST)
Received: from exchangefe2.na.procket.com (email.na.procket.com [10.1.7.252])
	by miata.procket.com (8.12.1/8.12.1) with ESMTP id i2MLoqd1023329;
	Mon, 22 Mar 2004 13:50:52 -0800 (PST)
Received: from [127.0.0.1] ([10.1.1.1]) by exchangefe2.na.procket.com with Microsoft SMTPSVC(5.0.2195.6713);
	 Mon, 22 Mar 2004 13:50:51 -0800
In-Reply-To: <200403210715.XAA15587@redback.com>
References: <200403210715.XAA15587@redback.com>
Mime-Version: 1.0 (Apple Message framework v612)
Content-Type: text/plain; charset=US-ASCII; format=flowed
Message-Id: <FC2091A7-7C4A-11D8-9354-00039303E9E2@procket.com>
Content-Transfer-Encoding: 7bit
Cc: Alex Zinin <zinin@psg.com>, rtgwg@ietf.org
From: Christian Hopps <chopps@procket.com>
Subject: Re: Review Call: draft-hsmit-mpls-igp-spf-01.txt 
Date: Mon, 22 Mar 2004 13:50:50 -0800
To: Naiming Shen <naiming@redback.com>
X-Mailer: Apple Mail (2.612)
X-OriginalArrivalTime: 22 Mar 2004 21:50:52.0554 (UTC) FILETIME=[BEFB0EA0:01C41057]
Content-Transfer-Encoding: 7bit
Sender: rtgwg-admin@ietf.org
Errors-To: rtgwg-admin@ietf.org
X-BeenThere: rtgwg@ietf.org
X-Mailman-Version: 2.0.12
Precedence: bulk
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/rtgwg>,
	<mailto:rtgwg-request@ietf.org?subject=unsubscribe>
List-Id: <rtgwg.ietf.org>
List-Post: <mailto:rtgwg@ietf.org>
List-Help: <mailto:rtgwg-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/rtgwg>,
	<mailto:rtgwg-request@ietf.org?subject=subscribe>
X-Spam-Checker-Version: SpamAssassin 2.60 (1.212-2003-09-23-exp) on 
	ietf-mx.ietf.org
X-Spam-Status: No, hits=0.0 required=5.0 tests=none autolearn=no version=2.60
Content-Transfer-Encoding: 7bit
Content-Transfer-Encoding: 7bit


On Mar 20, 2004, at 11:15 PM, Naiming Shen wrote:
>  ] >    When the manual TE-tunnel metric is configured to be larger 
> than
>  ] >    the IGP native path metric, this TE-tunnel can not be used in 
> the
>  ] >    SPF calculation. Otherwise a routing loop may be formed. Here 
> is
>  ] >    an example:
>  ]
>  ] Note stating "this TE-tunnel can not be used in the SPF 
> calculation" is=20=
>  ]
>  ] confusing, as its critical that TE-tunnels *not* be used in the 
> SPF=20
>  ] calculation.
>
> I'm not sure why this is confusing. It simply says the there may be
> a problem using such a tunnel with such a metric. We don't want to
> say that if certain conditions don't exist, then it's ok to use those
> tunnels.

I'm only concerned that the above text is indicating that one uses the 
TE metric rather than the IGP metric in the SPF algorithm specifically 
I'm focussed on the phrase "SPF calculation" above.

Note the example that follows in the text. Regardless of whether the TE 
tunnel metric is more or less it MUST not affect the path choice, the 
example and the text above seem to imply that it can.

Which again, is why the following is stated earlier in the document.

>  ] This is stated earlier in this section:
>  ]
>  ] "Setting a manual metric on a TE-tunnel does not impact the SPF=20
>  ] algorithm itself."
>  ]
>  ] The only thing the TE tunnel metric can affect is whether TE 
> tunnel=20
>  ] nexthop is chosen over the IGP nexthop when a route is being 
> installed,=20=
>  ]
>  ] and when *IGP metric* based ECMP routes are being considered.

Chris.

> - Naiming
>
> _______________________________________________
> Rtgwg mailing list
> Rtgwg@ietf.org
> https://www1.ietf.org/mailman/listinfo/rtgwg


_______________________________________________
Rtgwg mailing list
Rtgwg@ietf.org
https://www1.ietf.org/mailman/listinfo/rtgwg



From exim@www1.ietf.org  Thu Mar 25 21:50:09 2004
Received: from optimus.ietf.org (optimus.ietf.org [132.151.1.19])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id VAA10644
	for <rtgwg-archive@odin.ietf.org>; Thu, 25 Mar 2004 21:50:09 -0500 (EST)
Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1B6hPi-0002Yq-KX
	for rtgwg-archive@odin.ietf.org; Thu, 25 Mar 2004 21:49:42 -0500
Received: (from exim@localhost)
	by www1.ietf.org (8.12.8/8.12.8/Submit) id i2Q2ngcw009840
	for rtgwg-archive@odin.ietf.org; Thu, 25 Mar 2004 21:49:42 -0500
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1B6hPi-0002Yd-GJ
	for rtgwg-web-archive@optimus.ietf.org; Thu, 25 Mar 2004 21:49:42 -0500
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id VAA10631
	for <rtgwg-web-archive@ietf.org>; Thu, 25 Mar 2004 21:49:39 -0500 (EST)
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 1B6hPf-0001uw-00
	for rtgwg-web-archive@ietf.org; Thu, 25 Mar 2004 21:49:39 -0500
Received: from exim by ietf-mx with spam-scanned (Exim 4.12)
	id 1B6hOj-0001sE-00
	for rtgwg-web-archive@ietf.org; Thu, 25 Mar 2004 21:48:42 -0500
Received: from optimus.ietf.org ([132.151.1.19])
	by ietf-mx with esmtp (Exim 4.12)
	id 1B6hO4-0001pR-00
	for rtgwg-web-archive@ietf.org; Thu, 25 Mar 2004 21:48:00 -0500
Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1B6hO5-0002V2-NS; Thu, 25 Mar 2004 21:48:01 -0500
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1B6hNp-0002RR-7S
	for rtgwg@optimus.ietf.org; Thu, 25 Mar 2004 21:47:45 -0500
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id VAA10560
	for <rtgwg@ietf.org>; Thu, 25 Mar 2004 21:47:41 -0500 (EST)
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 1B6hNm-0001oz-00
	for rtgwg@ietf.org; Thu, 25 Mar 2004 21:47:42 -0500
Received: from exim by ietf-mx with spam-scanned (Exim 4.12)
	id 1B6hMt-0001m8-00
	for rtgwg@ietf.org; Thu, 25 Mar 2004 21:46:48 -0500
Received: from prattle.redback.com ([155.53.12.9])
	by ietf-mx with esmtp (Exim 4.12)
	id 1B6hMa-0001is-00
	for rtgwg@ietf.org; Thu, 25 Mar 2004 21:46:29 -0500
Received: from localhost (localhost [127.0.0.1])
	by prattle.redback.com (Postfix) with ESMTP
	id CC69EC63689; Thu, 25 Mar 2004 18:46:28 -0800 (PST)
Received: from prattle.redback.com ([127.0.0.1])
 by localhost (prattle [127.0.0.1]) (amavisd-new, port 10024) with ESMTP
 id 23652-02; Thu, 25 Mar 2004 18:46:28 -0800 (PST)
Received: from redback.com (malt.redback.com [155.53.12.41])
	by prattle.redback.com (Postfix) with ESMTP
	id 66D2BC63686; Thu, 25 Mar 2004 18:46:28 -0800 (PST)
Received: from malt (localhost [127.0.0.1])
	by redback.com (8.9.3-LCCHA/8.9.3/null redback solaris client) with ESMTP id SAA13183;
	Thu, 25 Mar 2004 18:46:28 -0800 (PST)
Message-Id: <200403260246.SAA13183@redback.com>
To: Christian Hopps <chopps@procket.com>
Cc: Naiming Shen <naiming@redback.com>, Alex Zinin <zinin@psg.com>,
        rtgwg@ietf.org
Subject: Re: Review Call: draft-hsmit-mpls-igp-spf-01.txt 
In-reply-to: Mail from Christian Hopps <chopps@procket.com> 
 dated Mon, 22 Mar 2004 13:50:50 PST
 <FC2091A7-7C4A-11D8-9354-00039303E9E2@procket.com> 
Date: Thu, 25 Mar 2004 18:46:28 -0800
From: Naiming Shen <naiming@redback.com>
X-Virus-Scanned: by amavisd-new at redback.com
Sender: rtgwg-admin@ietf.org
Errors-To: rtgwg-admin@ietf.org
X-BeenThere: rtgwg@ietf.org
X-Mailman-Version: 2.0.12
Precedence: bulk
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/rtgwg>,
	<mailto:rtgwg-request@ietf.org?subject=unsubscribe>
List-Id: <rtgwg.ietf.org>
List-Post: <mailto:rtgwg@ietf.org>
List-Help: <mailto:rtgwg-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/rtgwg>,
	<mailto:rtgwg-request@ietf.org?subject=subscribe>
X-Spam-Checker-Version: SpamAssassin 2.60 (1.212-2003-09-23-exp) on 
	ietf-mx.ietf.org
X-Spam-Status: No, hits=0.0 required=5.0 tests=AWL autolearn=no version=2.60

 ] 
 ] On Mar 20, 2004, at 11:15 PM, Naiming Shen wrote:
 ] >  ] >    When the manual TE-tunnel metric is configured to be larger 
 ] > than
 ] >  ] >    the IGP native path metric, this TE-tunnel can not be used in 
 ] > the
 ] >  ] >    SPF calculation. Otherwise a routing loop may be formed. Here 
 ] > is
 ] >  ] >    an example:
 ] >  ]
 ] >  ] Note stating "this TE-tunnel can not be used in the SPF 
 ] > calculation" is=20=
 ] >  ]
 ] >  ] confusing, as its critical that TE-tunnels *not* be used in the 
 ] > SPF=20
 ] >  ] calculation.
 ] >
 ] > I'm not sure why this is confusing. It simply says the there may be
 ] > a problem using such a tunnel with such a metric. We don't want to
 ] > say that if certain conditions don't exist, then it's ok to use those
 ] > tunnels.
 ] 
 ] I'm only concerned that the above text is indicating that one uses the 
 ] TE metric rather than the IGP metric in the SPF algorithm specifically 
 ] I'm focussed on the phrase "SPF calculation" above.
 ] 
 ] Note the example that follows in the text. Regardless of whether the TE 
 ] tunnel metric is more or less it MUST not affect the path choice, the 
 ] example and the text above seem to imply that it can.

I think my example in the draft was not good. By (dst), which I meant
some prefix/subnet. There are posibility that multiple nodes inject
the same subnet. Even though the shortcut does not change the SPF,
it does change the metric assigned into routes, and the lower ones
will win, which can cause a loop. something like the following diagram:

      (src)  2         2
        A ------ B ------- C
        |        =========>|
      20|            30    |2
        |                  |
        D                  E (dst X)
       (dst X)

does this diagram change make sense?

thanks.

 ] 
 ] Which again, is why the following is stated earlier in the document.
 ] 
 ] >  ] This is stated earlier in this section:
 ] >  ]
 ] >  ] "Setting a manual metric on a TE-tunnel does not impact the SPF=20
 ] >  ] algorithm itself."
 ] >  ]
 ] >  ] The only thing the TE tunnel metric can affect is whether TE 
 ] > tunnel=20
 ] >  ] nexthop is chosen over the IGP nexthop when a route is being 
 ] > installed,=20=
 ] >  ]
 ] >  ] and when *IGP metric* based ECMP routes are being considered.
 ] 
 ] Chris.
 ] 
 ] > - Naiming
 ] >
 ] > _______________________________________________
 ] > Rtgwg mailing list
 ] > Rtgwg@ietf.org
 ] > https://www1.ietf.org/mailman/listinfo/rtgwg
 ] 
 ] 
 ] _______________________________________________
 ] Rtgwg mailing list
 ] Rtgwg@ietf.org
 ] https://www1.ietf.org/mailman/listinfo/rtgwg

- Naiming

_______________________________________________
Rtgwg mailing list
Rtgwg@ietf.org
https://www1.ietf.org/mailman/listinfo/rtgwg



From exim@www1.ietf.org  Thu Mar 25 22:38:41 2004
Received: from optimus.ietf.org (optimus.ietf.org [132.151.1.19])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id WAA12572
	for <rtgwg-archive@odin.ietf.org>; Thu, 25 Mar 2004 22:38:41 -0500 (EST)
Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1B6iAh-00068v-03
	for rtgwg-archive@odin.ietf.org; Thu, 25 Mar 2004 22:38:15 -0500
Received: (from exim@localhost)
	by www1.ietf.org (8.12.8/8.12.8/Submit) id i2Q3cEEc023607
	for rtgwg-archive@odin.ietf.org; Thu, 25 Mar 2004 22:38:14 -0500
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1B6iAg-00068g-Qr
	for rtgwg-web-archive@optimus.ietf.org; Thu, 25 Mar 2004 22:38:14 -0500
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id WAA12459
	for <rtgwg-web-archive@ietf.org>; Thu, 25 Mar 2004 22:38:10 -0500 (EST)
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 1B6iAd-0006P5-00
	for rtgwg-web-archive@ietf.org; Thu, 25 Mar 2004 22:38:11 -0500
Received: from exim by ietf-mx with spam-scanned (Exim 4.12)
	id 1B6i9P-00069Z-00
	for rtgwg-web-archive@ietf.org; Thu, 25 Mar 2004 22:36:56 -0500
Received: from [65.246.255.50] (helo=mx2.foretec.com)
	by ietf-mx with esmtp (Exim 4.12)
	id 1B6i82-0005tv-02
	for rtgwg-web-archive@ietf.org; Thu, 25 Mar 2004 22:35:30 -0500
Received: from optimus22.ietf.org ([132.151.6.22] helo=optimus.ietf.org)
	by mx2.foretec.com with esmtp (Exim 4.24)
	id 1B6hv0-00013H-40
	for rtgwg-web-archive@ietf.org; Thu, 25 Mar 2004 22:22:02 -0500
Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1B6huz-0005G9-04; Thu, 25 Mar 2004 22:22:01 -0500
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1B6hue-0005FL-Uy
	for rtgwg@optimus.ietf.org; Thu, 25 Mar 2004 22:21:41 -0500
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id WAA11830
	for <rtgwg@ietf.org>; Thu, 25 Mar 2004 22:21:36 -0500 (EST)
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 1B6hub-0004wg-00
	for rtgwg@ietf.org; Thu, 25 Mar 2004 22:21:37 -0500
Received: from exim by ietf-mx with spam-scanned (Exim 4.12)
	id 1B6hte-0004sB-00
	for rtgwg@ietf.org; Thu, 25 Mar 2004 22:20:39 -0500
Received: from smtp1.procket.com ([65.174.124.36])
	by ietf-mx with esmtp (Exim 4.12)
	id 1B6hsl-0004hj-00
	for rtgwg@ietf.org; Thu, 25 Mar 2004 22:19:43 -0500
Received: from miata.procket.com (mil0-fw00-d-1.procket.com [65.174.124.60])
	by smtp1.procket.com (8.12.8p1/8.12.1) with ESMTP id i2Q5TQpL091705;
	Thu, 25 Mar 2004 21:29:26 -0800 (PST)
Received: from exchangefe2.na.procket.com (email.na.procket.com [10.1.7.252])
	by miata.procket.com (8.12.1/8.12.1) with ESMTP id i2Q3J8d1020610;
	Thu, 25 Mar 2004 19:19:08 -0800 (PST)
Received: from [127.0.0.1] ([10.1.1.1]) by exchangefe2.na.procket.com with Microsoft SMTPSVC(5.0.2195.6713);
	 Thu, 25 Mar 2004 19:19:08 -0800
In-Reply-To: <200403260246.SAA13183@redback.com>
References: <200403260246.SAA13183@redback.com>
Mime-Version: 1.0 (Apple Message framework v613)
Content-Type: text/plain; charset=US-ASCII; format=flowed
Message-Id: <58C20958-7ED4-11D8-8353-00039303E9E2@procket.com>
Content-Transfer-Encoding: 7bit
Cc: "Alex Zinin" <zinin@psg.com>, <rtgwg@ietf.org>
From: Christian Hopps <chopps@procket.com>
Subject: Re: Review Call: draft-hsmit-mpls-igp-spf-01.txt 
Date: Thu, 25 Mar 2004 19:19:09 -0800
To: "Naiming Shen" <naiming@redback.com>
X-Mailer: Apple Mail (2.613)
X-OriginalArrivalTime: 26 Mar 2004 03:19:08.0854 (UTC) FILETIME=[1A212D60:01C412E1]
Content-Transfer-Encoding: 7bit
Sender: rtgwg-admin@ietf.org
Errors-To: rtgwg-admin@ietf.org
X-BeenThere: rtgwg@ietf.org
X-Mailman-Version: 2.0.12
Precedence: bulk
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/rtgwg>,
	<mailto:rtgwg-request@ietf.org?subject=unsubscribe>
List-Id: <rtgwg.ietf.org>
List-Post: <mailto:rtgwg@ietf.org>
List-Help: <mailto:rtgwg-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/rtgwg>,
	<mailto:rtgwg-request@ietf.org?subject=subscribe>
X-Spam-Checker-Version: SpamAssassin 2.60 (1.212-2003-09-23-exp) on 
	ietf-mx.ietf.org
X-Spam-Status: No, hits=0.0 required=5.0 tests=none autolearn=no version=2.60
Content-Transfer-Encoding: 7bit
Content-Transfer-Encoding: 7bit


On Mar 25, 2004, at 6:46 PM, Naiming Shen wrote:
>  ] Note the example that follows in the text. Regardless of whether 
> the TE
>  ] tunnel metric is more or less it MUST not affect the path choice, 
> the
>  ] example and the text above seem to imply that it can.
>
> I think my example in the draft was not good. By (dst), which I meant
> some prefix/subnet. There are posibility that multiple nodes inject
> the same subnet. Even though the shortcut does not change the SPF,
> it does change the metric assigned into routes, and the lower ones
> will win, which can cause a loop. something like the following diagram:
>
>       (src)  2         2
>         A ------ B ------- C
>         |        =========>|
>       20|            30    |2
>         |                  |
>         D                  E (dst X)
>        (dst X)
>
> does this diagram change make sense?

There is no possibility of a loop here. B will choose C for E because 
of the SPF, the TE metric plays no part in the SPF at all. That is, B 
will choose C, E will go into TENT, B will then choose E through C by 
putting E in PATHS next. The draft can say that B uses the IGP because 
its metric to dst x is 4 and the TE metric is 32, but talking about it 
in the context of the SPF is misleading.

More to the point, a vendor could actually have an option "always 
prefer TE tunnels to IGP" and B could then use the metric 30 tunnel, 
there would *still* be no loop.

The draft should clearly state that the TE metric only arbitrates for 
nexthop selection once the best routes have been discovered. In the 
above example why would A even be looking at D as a route for dst x?

Thanks,
Chris.


> thanks.
>
>  ]
>  ] Which again, is why the following is stated earlier in the document.
>  ]
>  ] >  ] This is stated earlier in this section:
>  ] >  ]
>  ] >  ] "Setting a manual metric on a TE-tunnel does not impact the 
> SPF=20
>  ] >  ] algorithm itself."
>  ] >  ]
>  ] >  ] The only thing the TE tunnel metric can affect is whether TE
>  ] > tunnel=20
>  ] >  ] nexthop is chosen over the IGP nexthop when a route is being
>  ] > installed,=20=
>  ] >  ]
>  ] >  ] and when *IGP metric* based ECMP routes are being considered.
>  ]
>  ] Chris.
>  ]
>  ] > - Naiming
>  ] >
>  ] > _______________________________________________
>  ] > Rtgwg mailing list
>  ] > Rtgwg@ietf.org
>  ] > https://www1.ietf.org/mailman/listinfo/rtgwg
>  ]
>  ]
>  ] _______________________________________________
>  ] Rtgwg mailing list
>  ] Rtgwg@ietf.org
>  ] https://www1.ietf.org/mailman/listinfo/rtgwg
>
> - Naiming


_______________________________________________
Rtgwg mailing list
Rtgwg@ietf.org
https://www1.ietf.org/mailman/listinfo/rtgwg



From exim@www1.ietf.org  Thu Mar 25 23:15:16 2004
Received: from optimus.ietf.org (optimus.ietf.org [132.151.1.19])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id XAA14089
	for <rtgwg-archive@odin.ietf.org>; Thu, 25 Mar 2004 23:15:16 -0500 (EST)
Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1B6ik4-0000j3-Ro
	for rtgwg-archive@odin.ietf.org; Thu, 25 Mar 2004 23:14:49 -0500
Received: (from exim@localhost)
	by www1.ietf.org (8.12.8/8.12.8/Submit) id i2Q4EmXC002786
	for rtgwg-archive@odin.ietf.org; Thu, 25 Mar 2004 23:14:48 -0500
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1B6ik4-0000ir-LR
	for rtgwg-web-archive@optimus.ietf.org; Thu, 25 Mar 2004 23:14:48 -0500
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id XAA14083
	for <rtgwg-web-archive@ietf.org>; Thu, 25 Mar 2004 23:14:45 -0500 (EST)
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 1B6ik2-0001Wn-00
	for rtgwg-web-archive@ietf.org; Thu, 25 Mar 2004 23:14:46 -0500
Received: from exim by ietf-mx with spam-scanned (Exim 4.12)
	id 1B6ijA-0001TH-00
	for rtgwg-web-archive@ietf.org; Thu, 25 Mar 2004 23:13:53 -0500
Received: from optimus.ietf.org ([132.151.1.19])
	by ietf-mx with esmtp (Exim 4.12)
	id 1B6iiL-0001P7-00
	for rtgwg-web-archive@ietf.org; Thu, 25 Mar 2004 23:13:01 -0500
Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1B6iiJ-0000dC-SV; Thu, 25 Mar 2004 23:12:59 -0500
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1B6ii3-0000cW-3v
	for rtgwg@optimus.ietf.org; Thu, 25 Mar 2004 23:12:43 -0500
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id XAA14013
	for <rtgwg@ietf.org>; Thu, 25 Mar 2004 23:12:40 -0500 (EST)
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 1B6ii1-0001N2-00
	for rtgwg@ietf.org; Thu, 25 Mar 2004 23:12:41 -0500
Received: from exim by ietf-mx with spam-scanned (Exim 4.12)
	id 1B6ih8-0001Jj-00
	for rtgwg@ietf.org; Thu, 25 Mar 2004 23:11:47 -0500
Received: from prattle.redback.com ([155.53.12.9])
	by ietf-mx with esmtp (Exim 4.12)
	id 1B6igJ-0001GM-00
	for rtgwg@ietf.org; Thu, 25 Mar 2004 23:10:56 -0500
Received: from localhost (localhost [127.0.0.1])
	by prattle.redback.com (Postfix) with ESMTP
	id 57BA9283BC7; Thu, 25 Mar 2004 20:10:56 -0800 (PST)
Received: from prattle.redback.com ([127.0.0.1])
 by localhost (prattle [127.0.0.1]) (amavisd-new, port 10024) with ESMTP
 id 03495-05; Thu, 25 Mar 2004 20:10:55 -0800 (PST)
Received: from redback.com (malt.redback.com [155.53.12.41])
	by prattle.redback.com (Postfix) with ESMTP
	id B8C4C283BC5; Thu, 25 Mar 2004 20:10:55 -0800 (PST)
Received: from malt (localhost [127.0.0.1])
	by redback.com (8.9.3-LCCHA/8.9.3/null redback solaris client) with ESMTP id UAA13614;
	Thu, 25 Mar 2004 20:10:55 -0800 (PST)
Message-Id: <200403260410.UAA13614@redback.com>
To: Christian Hopps <chopps@procket.com>
Cc: "Naiming Shen" <naiming@redback.com>, "Alex Zinin" <zinin@psg.com>,
        rtgwg@ietf.org
Subject: Re: Review Call: draft-hsmit-mpls-igp-spf-01.txt 
In-reply-to: Mail from Christian Hopps <chopps@procket.com> 
 dated Thu, 25 Mar 2004 19:19:09 PST
 <58C20958-7ED4-11D8-8353-00039303E9E2@procket.com> 
Date: Thu, 25 Mar 2004 20:10:55 -0800
From: Naiming Shen <naiming@redback.com>
X-Virus-Scanned: by amavisd-new at redback.com
Sender: rtgwg-admin@ietf.org
Errors-To: rtgwg-admin@ietf.org
X-BeenThere: rtgwg@ietf.org
X-Mailman-Version: 2.0.12
Precedence: bulk
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/rtgwg>,
	<mailto:rtgwg-request@ietf.org?subject=unsubscribe>
List-Id: <rtgwg.ietf.org>
List-Post: <mailto:rtgwg@ietf.org>
List-Help: <mailto:rtgwg-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/rtgwg>,
	<mailto:rtgwg-request@ietf.org?subject=subscribe>
X-Spam-Checker-Version: SpamAssassin 2.60 (1.212-2003-09-23-exp) on 
	ietf-mx.ietf.org
X-Spam-Status: No, hits=0.0 required=5.0 tests=AWL autolearn=no version=2.60

 ] 
 ] On Mar 25, 2004, at 6:46 PM, Naiming Shen wrote:
 ] >  ] Note the example that follows in the text. Regardless of whether 
 ] > the TE
 ] >  ] tunnel metric is more or less it MUST not affect the path choice, 
 ] > the
 ] >  ] example and the text above seem to imply that it can.
 ] >
 ] > I think my example in the draft was not good. By (dst), which I meant
 ] > some prefix/subnet. There are posibility that multiple nodes inject
 ] > the same subnet. Even though the shortcut does not change the SPF,
 ] > it does change the metric assigned into routes, and the lower ones
 ] > will win, which can cause a loop. something like the following diagram:
 ] >
 ] >       (src)  2         2
 ] >         A ------ B ------- C
 ] >         |        =========>|
 ] >       20|            30    |2
 ] >         |                  |
 ] >         D                  E (dst X)
 ] >        (dst X)
 ] >
 ] > does this diagram change make sense?
 ] 
 ] There is no possibility of a loop here. B will choose C for E because 
 ] of the SPF, the TE metric plays no part in the SPF at all. That is, B 
 ] will choose C, E will go into TENT, B will then choose E through C by 
 ] putting E in PATHS next. The draft can say that B uses the IGP because 
 ] its metric to dst x is 4 and the TE metric is 32, but talking about it 
 ] in the context of the SPF is misleading.
 ] 
 ] More to the point, a vendor could actually have an option "always 
 ] prefer TE tunnels to IGP" and B could then use the metric 30 tunnel, 
 ] there would *still* be no loop.
 ] 
 ] The draft should clearly state that the TE metric only arbitrates for 
 ] nexthop selection once the best routes have been discovered. In the 
 ] above example why would A even be looking at D as a route for dst x?
                          ^^^

I think you meant B above.
Here is why regardless of lsp tunnels:

         10           20
    a ------------> b -- Y
    |
    +-------------> c -- Y
         15           5

assume node 'a' is the source of the SPF, it has metric 10 to reach
node 'b' and metric 15 to reach node 'c'. node 'b' announce routes Y
with metric of 20, and node 'c' announces route Y with metric of 5.
are you saying from node 'a' to destination of Y, it should take
node 'b' instead of node 'c' ?


thanks.

 ] 
 ] Thanks,
 ] Chris.
 ] 
 ] 
 ] > thanks.
 ] >
 ] >  ]
 ] >  ] Which again, is why the following is stated earlier in the document.
 ] >  ]
 ] >  ] >  ] This is stated earlier in this section:
 ] >  ] >  ]
 ] >  ] >  ] "Setting a manual metric on a TE-tunnel does not impact the 
 ] > SPF=20
 ] >  ] >  ] algorithm itself."
 ] >  ] >  ]
 ] >  ] >  ] The only thing the TE tunnel metric can affect is whether TE
 ] >  ] > tunnel=20
 ] >  ] >  ] nexthop is chosen over the IGP nexthop when a route is being
 ] >  ] > installed,=20=
 ] >  ] >  ]
 ] >  ] >  ] and when *IGP metric* based ECMP routes are being considered.
 ] >  ]
 ] >  ] Chris.
 ] >  ]
 ] >  ] > - Naiming
 ] >  ] >
 ] >  ] > _______________________________________________
 ] >  ] > Rtgwg mailing list
 ] >  ] > Rtgwg@ietf.org
 ] >  ] > https://www1.ietf.org/mailman/listinfo/rtgwg
 ] >  ]
 ] >  ]
 ] >  ] _______________________________________________
 ] >  ] Rtgwg mailing list
 ] >  ] Rtgwg@ietf.org
 ] >  ] https://www1.ietf.org/mailman/listinfo/rtgwg
 ] >
 ] > - Naiming
 ] 
 ] 
 ] _______________________________________________
 ] Rtgwg mailing list
 ] Rtgwg@ietf.org
 ] https://www1.ietf.org/mailman/listinfo/rtgwg

- Naiming

_______________________________________________
Rtgwg mailing list
Rtgwg@ietf.org
https://www1.ietf.org/mailman/listinfo/rtgwg



From exim@www1.ietf.org  Thu Mar 25 23:25:13 2004
Received: from optimus.ietf.org (optimus.ietf.org [132.151.1.19])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id XAA14537
	for <rtgwg-archive@odin.ietf.org>; Thu, 25 Mar 2004 23:25:13 -0500 (EST)
Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1B6ith-0001hD-Of
	for rtgwg-archive@odin.ietf.org; Thu, 25 Mar 2004 23:24:45 -0500
Received: (from exim@localhost)
	by www1.ietf.org (8.12.8/8.12.8/Submit) id i2Q4OjGA006513
	for rtgwg-archive@odin.ietf.org; Thu, 25 Mar 2004 23:24:45 -0500
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1B6ith-0001gy-K2
	for rtgwg-web-archive@optimus.ietf.org; Thu, 25 Mar 2004 23:24:45 -0500
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id XAA14524
	for <rtgwg-web-archive@ietf.org>; Thu, 25 Mar 2004 23:24:42 -0500 (EST)
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 1B6itf-0002Oq-00
	for rtgwg-web-archive@ietf.org; Thu, 25 Mar 2004 23:24:43 -0500
Received: from exim by ietf-mx with spam-scanned (Exim 4.12)
	id 1B6isk-0002Le-00
	for rtgwg-web-archive@ietf.org; Thu, 25 Mar 2004 23:23:46 -0500
Received: from optimus.ietf.org ([132.151.1.19])
	by ietf-mx with esmtp (Exim 4.12)
	id 1B6is0-0002I8-00
	for rtgwg-web-archive@ietf.org; Thu, 25 Mar 2004 23:23:00 -0500
Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1B6is0-0001ds-RP; Thu, 25 Mar 2004 23:23:00 -0500
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1B6irj-0001cP-Rg
	for rtgwg@optimus.ietf.org; Thu, 25 Mar 2004 23:22:43 -0500
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id XAA14432
	for <rtgwg@ietf.org>; Thu, 25 Mar 2004 23:22:40 -0500 (EST)
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 1B6irh-0002GA-00
	for rtgwg@ietf.org; Thu, 25 Mar 2004 23:22:42 -0500
Received: from exim by ietf-mx with spam-scanned (Exim 4.12)
	id 1B6iql-0002BG-00
	for rtgwg@ietf.org; Thu, 25 Mar 2004 23:21:44 -0500
Received: from smtp1.procket.com ([65.174.124.36])
	by ietf-mx with esmtp (Exim 4.12)
	id 1B6ipw-00022f-00
	for rtgwg@ietf.org; Thu, 25 Mar 2004 23:20:52 -0500
Received: from miata.procket.com (mil0-fw00-d-1.procket.com [65.174.124.60])
	by smtp1.procket.com (8.12.8p1/8.12.1) with ESMTP id i2Q6UYpL092118;
	Thu, 25 Mar 2004 22:30:34 -0800 (PST)
Received: from exchangefe2.na.procket.com (email.na.procket.com [10.1.7.252])
	by miata.procket.com (8.12.1/8.12.1) with ESMTP id i2Q4KHd1023339;
	Thu, 25 Mar 2004 20:20:17 -0800 (PST)
Received: from [127.0.0.1] ([10.1.1.1]) by exchangefe2.na.procket.com with Microsoft SMTPSVC(5.0.2195.6713);
	 Thu, 25 Mar 2004 20:20:17 -0800
In-Reply-To: <200403260410.UAA13614@redback.com>
References: <200403260410.UAA13614@redback.com>
Mime-Version: 1.0 (Apple Message framework v613)
Content-Type: text/plain; charset=US-ASCII; format=flowed
Message-Id: <E2E0450D-7EDC-11D8-8353-00039303E9E2@procket.com>
Content-Transfer-Encoding: 7bit
Cc: "Alex Zinin" <zinin@psg.com>, <rtgwg@ietf.org>
From: Christian Hopps <chopps@procket.com>
Subject: Re: Review Call: draft-hsmit-mpls-igp-spf-01.txt 
Date: Thu, 25 Mar 2004 20:20:17 -0800
To: "Naiming Shen" <naiming@redback.com>
X-Mailer: Apple Mail (2.613)
X-OriginalArrivalTime: 26 Mar 2004 04:20:17.0565 (UTC) FILETIME=[A4DA0CD0:01C412E9]
Content-Transfer-Encoding: 7bit
Sender: rtgwg-admin@ietf.org
Errors-To: rtgwg-admin@ietf.org
X-BeenThere: rtgwg@ietf.org
X-Mailman-Version: 2.0.12
Precedence: bulk
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/rtgwg>,
	<mailto:rtgwg-request@ietf.org?subject=unsubscribe>
List-Id: <rtgwg.ietf.org>
List-Post: <mailto:rtgwg@ietf.org>
List-Help: <mailto:rtgwg-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/rtgwg>,
	<mailto:rtgwg-request@ietf.org?subject=subscribe>
X-Spam-Checker-Version: SpamAssassin 2.60 (1.212-2003-09-23-exp) on 
	ietf-mx.ietf.org
X-Spam-Status: No, hits=0.0 required=5.0 tests=none autolearn=no version=2.60
Content-Transfer-Encoding: 7bit
Content-Transfer-Encoding: 7bit


On Mar 25, 2004, at 8:10 PM, Naiming Shen wrote:
>  ] On Mar 25, 2004, at 6:46 PM, Naiming Shen wrote:
>  ] >  ] Note the example that follows in the text. Regardless of 
> whether
>  ] > the TE
>  ] >  ] tunnel metric is more or less it MUST not affect the path 
> choice,
>  ] > the
>  ] >  ] example and the text above seem to imply that it can.
>  ] >
>  ] > I think my example in the draft was not good. By (dst), which I 
> meant
>  ] > some prefix/subnet. There are posibility that multiple nodes 
> inject
>  ] > the same subnet. Even though the shortcut does not change the SPF,
>  ] > it does change the metric assigned into routes, and the lower ones
>  ] > will win, which can cause a loop. something like the following 
> diagram:
>  ] >
>  ] >       (src)  2         2
>  ] >         A ------ B ------- C
>  ] >         |        =========>|
>  ] >       20|            30    |2
>  ] >         |                  |
>  ] >         D                  E (dst X)
>  ] >        (dst X)
>  ] >
>  ] > does this diagram change make sense?
>  ]
>  ] There is no possibility of a loop here. B will choose C for E 
> because
>  ] of the SPF, the TE metric plays no part in the SPF at all. That is, 
> B
>  ] will choose C, E will go into TENT, B will then choose E through C 
> by
>  ] putting E in PATHS next. The draft can say that B uses the IGP 
> because
>  ] its metric to dst x is 4 and the TE metric is 32, but talking about 
> it
>  ] in the context of the SPF is misleading.
>  ]
>  ] More to the point, a vendor could actually have an option "always
>  ] prefer TE tunnels to IGP" and B could then use the metric 30 tunnel,
>  ] there would *still* be no loop.
>  ]
>  ] The draft should clearly state that the TE metric only arbitrates 
> for
>  ] nexthop selection once the best routes have been discovered. In the
>  ] above example why would A even be looking at D as a route for dst x?
>                           ^^^
>
> I think you meant B above.
> Here is why regardless of lsp tunnels:
>
>          10           20
>     a ------------> b -- Y
>     |
>     +-------------> c -- Y
>          15           5
>
> assume node 'a' is the source of the SPF, it has metric 10 to reach
> node 'b' and metric 15 to reach node 'c'. node 'b' announce routes Y
> with metric of 20, and node 'c' announces route Y with metric of 5.
> are you saying from node 'a' to destination of Y, it should take
> node 'b' instead of node 'c' ?

Absolutely not. The cost to Y through b by SPF is 30. The cost to Y 
through c is 20. Clearly c is the only nexthop A should (MUST) use to 
Y. I'm saying TE metric has nothing to do with choosing the set of best 
cost paths to Y. When that set is chosen, and only when, you can do 
whatever you want in selecting which ones you want to use, including 
the use of the TE metric; however, TE MUST not play any part in 
selecting the initial set of best cost paths.

Chris.

>
> thanks.
>
>  ]
>  ] Thanks,
>  ] Chris.
>  ]
>  ]
>  ] > thanks.
>  ] >
>  ] >  ]
>  ] >  ] Which again, is why the following is stated earlier in the 
> document.
>  ] >  ]
>  ] >  ] >  ] This is stated earlier in this section:
>  ] >  ] >  ]
>  ] >  ] >  ] "Setting a manual metric on a TE-tunnel does not impact 
> the
>  ] > SPF=20
>  ] >  ] >  ] algorithm itself."
>  ] >  ] >  ]
>  ] >  ] >  ] The only thing the TE tunnel metric can affect is whether 
> TE
>  ] >  ] > tunnel=20
>  ] >  ] >  ] nexthop is chosen over the IGP nexthop when a route is 
> being
>  ] >  ] > installed,=20=
>  ] >  ] >  ]
>  ] >  ] >  ] and when *IGP metric* based ECMP routes are being 
> considered.
>  ] >  ]
>  ] >  ] Chris.
>  ] >  ]
>  ] >  ] > - Naiming
>  ] >  ] >
>  ] >  ] > _______________________________________________
>  ] >  ] > Rtgwg mailing list
>  ] >  ] > Rtgwg@ietf.org
>  ] >  ] > https://www1.ietf.org/mailman/listinfo/rtgwg
>  ] >  ]
>  ] >  ]
>  ] >  ] _______________________________________________
>  ] >  ] Rtgwg mailing list
>  ] >  ] Rtgwg@ietf.org
>  ] >  ] https://www1.ietf.org/mailman/listinfo/rtgwg
>  ] >
>  ] > - Naiming
>  ]
>  ]
>  ] _______________________________________________
>  ] Rtgwg mailing list
>  ] Rtgwg@ietf.org
>  ] https://www1.ietf.org/mailman/listinfo/rtgwg
>
> - Naiming


_______________________________________________
Rtgwg mailing list
Rtgwg@ietf.org
https://www1.ietf.org/mailman/listinfo/rtgwg



From exim@www1.ietf.org  Fri Mar 26 00:00:18 2004
Received: from optimus.ietf.org (optimus.ietf.org [132.151.1.19])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id AAA15529
	for <rtgwg-archive@odin.ietf.org>; Fri, 26 Mar 2004 00:00:18 -0500 (EST)
Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1B6jRf-0003u6-JP
	for rtgwg-archive@odin.ietf.org; Thu, 25 Mar 2004 23:59:51 -0500
Received: (from exim@localhost)
	by www1.ietf.org (8.12.8/8.12.8/Submit) id i2Q4xpqQ015000
	for rtgwg-archive@odin.ietf.org; Thu, 25 Mar 2004 23:59:51 -0500
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1B6jRf-0003tr-F9
	for rtgwg-web-archive@optimus.ietf.org; Thu, 25 Mar 2004 23:59:51 -0500
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id XAA15509
	for <rtgwg-web-archive@ietf.org>; Thu, 25 Mar 2004 23:59:48 -0500 (EST)
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 1B6jRd-0004bN-00
	for rtgwg-web-archive@ietf.org; Thu, 25 Mar 2004 23:59:49 -0500
Received: from exim by ietf-mx with spam-scanned (Exim 4.12)
	id 1B6jQk-0004Xc-00
	for rtgwg-web-archive@ietf.org; Thu, 25 Mar 2004 23:58:55 -0500
Received: from optimus.ietf.org ([132.151.1.19])
	by ietf-mx with esmtp (Exim 4.12)
	id 1B6jPr-0004TU-00
	for rtgwg-web-archive@ietf.org; Thu, 25 Mar 2004 23:57:59 -0500
Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1B6jPs-0003nS-IH; Thu, 25 Mar 2004 23:58:00 -0500
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1B6jPf-0003lp-5n
	for rtgwg@optimus.ietf.org; Thu, 25 Mar 2004 23:57:47 -0500
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id XAA15436
	for <rtgwg@ietf.org>; Thu, 25 Mar 2004 23:57:43 -0500 (EST)
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 1B6jPc-0004Rd-00
	for rtgwg@ietf.org; Thu, 25 Mar 2004 23:57:44 -0500
Received: from exim by ietf-mx with spam-scanned (Exim 4.12)
	id 1B6jOm-0004OF-00
	for rtgwg@ietf.org; Thu, 25 Mar 2004 23:56:53 -0500
Received: from prattle.redback.com ([155.53.12.9])
	by ietf-mx with esmtp (Exim 4.12)
	id 1B6jNt-0004L2-00
	for rtgwg@ietf.org; Thu, 25 Mar 2004 23:55:57 -0500
Received: from localhost (localhost [127.0.0.1])
	by prattle.redback.com (Postfix) with ESMTP
	id 4DF1B283BC7; Thu, 25 Mar 2004 20:55:58 -0800 (PST)
Received: from prattle.redback.com ([127.0.0.1])
 by localhost (prattle [127.0.0.1]) (amavisd-new, port 10024) with ESMTP
 id 08821-06; Thu, 25 Mar 2004 20:55:57 -0800 (PST)
Received: from redback.com (malt.redback.com [155.53.12.41])
	by prattle.redback.com (Postfix) with ESMTP
	id 3E986283BC8; Thu, 25 Mar 2004 20:55:57 -0800 (PST)
Received: from malt (localhost [127.0.0.1])
	by redback.com (8.9.3-LCCHA/8.9.3/null redback solaris client) with ESMTP id UAA13846;
	Thu, 25 Mar 2004 20:55:57 -0800 (PST)
Message-Id: <200403260455.UAA13846@redback.com>
To: Christian Hopps <chopps@procket.com>
Cc: "Naiming Shen" <naiming@redback.com>, "Alex Zinin" <zinin@psg.com>,
        rtgwg@ietf.org
Subject: Re: Review Call: draft-hsmit-mpls-igp-spf-01.txt 
In-reply-to: Mail from Christian Hopps <chopps@procket.com> 
 dated Thu, 25 Mar 2004 20:20:17 PST
 <E2E0450D-7EDC-11D8-8353-00039303E9E2@procket.com> 
Date: Thu, 25 Mar 2004 20:55:57 -0800
From: Naiming Shen <naiming@redback.com>
X-Virus-Scanned: by amavisd-new at redback.com
Sender: rtgwg-admin@ietf.org
Errors-To: rtgwg-admin@ietf.org
X-BeenThere: rtgwg@ietf.org
X-Mailman-Version: 2.0.12
Precedence: bulk
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/rtgwg>,
	<mailto:rtgwg-request@ietf.org?subject=unsubscribe>
List-Id: <rtgwg.ietf.org>
List-Post: <mailto:rtgwg@ietf.org>
List-Help: <mailto:rtgwg-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/rtgwg>,
	<mailto:rtgwg-request@ietf.org?subject=subscribe>
X-Spam-Checker-Version: SpamAssassin 2.60 (1.212-2003-09-23-exp) on 
	ietf-mx.ietf.org
X-Spam-Status: No, hits=0.0 required=5.0 tests=AWL autolearn=no version=2.60

 ] 
 ] On Mar 25, 2004, at 8:10 PM, Naiming Shen wrote:
 ] >  ] On Mar 25, 2004, at 6:46 PM, Naiming Shen wrote:
 ] >  ] >  ] Note the example that follows in the text. Regardless of 
 ] > whether
 ] >  ] > the TE
 ] >  ] >  ] tunnel metric is more or less it MUST not affect the path 
 ] > choice,
 ] >  ] > the
 ] >  ] >  ] example and the text above seem to imply that it can.
 ] >  ] >
 ] >  ] > I think my example in the draft was not good. By (dst), which I 
 ] > meant
 ] >  ] > some prefix/subnet. There are posibility that multiple nodes 
 ] > inject
 ] >  ] > the same subnet. Even though the shortcut does not change the SPF,
 ] >  ] > it does change the metric assigned into routes, and the lower ones
 ] >  ] > will win, which can cause a loop. something like the following 
 ] > diagram:
 ] >  ] >
 ] >  ] >       (src)  2         2
 ] >  ] >         A ------ B ------- C
 ] >  ] >         |        =========>|
 ] >  ] >       20|            30    |2
 ] >  ] >         |                  |
 ] >  ] >         D                  E (dst X)
 ] >  ] >        (dst X)
 ] >  ] >
 ] >  ] > does this diagram change make sense?
 ] >  ]
 ] >  ] There is no possibility of a loop here. B will choose C for E 
 ] > because
 ] >  ] of the SPF, the TE metric plays no part in the SPF at all. That is, 
 ] > B
 ] >  ] will choose C, E will go into TENT, B will then choose E through C 
 ] > by
 ] >  ] putting E in PATHS next. The draft can say that B uses the IGP 
 ] > because
 ] >  ] its metric to dst x is 4 and the TE metric is 32, but talking about 
 ] > it
 ] >  ] in the context of the SPF is misleading.
 ] >  ]
 ] >  ] More to the point, a vendor could actually have an option "always
 ] >  ] prefer TE tunnels to IGP" and B could then use the metric 30 tunnel,
 ] >  ] there would *still* be no loop.
 ] >  ]
 ] >  ] The draft should clearly state that the TE metric only arbitrates 
 ] > for
 ] >  ] nexthop selection once the best routes have been discovered. In the
 ] >  ] above example why would A even be looking at D as a route for dst x?
 ] >                           ^^^
 ] >
 ] > I think you meant B above.
 ] > Here is why regardless of lsp tunnels:
 ] >
 ] >          10           20
 ] >     a ------------> b -- Y
 ] >     |
 ] >     +-------------> c -- Y
 ] >          15           5
 ] >
 ] > assume node 'a' is the source of the SPF, it has metric 10 to reach
 ] > node 'b' and metric 15 to reach node 'c'. node 'b' announce routes Y
 ] > with metric of 20, and node 'c' announces route Y with metric of 5.
 ] > are you saying from node 'a' to destination of Y, it should take
 ] > node 'b' instead of node 'c' ?
 ] 
 ] Absolutely not. The cost to Y through b by SPF is 30. The cost to Y 
 ] through c is 20. Clearly c is the only nexthop A should (MUST) use to 
 ] Y. I'm saying TE metric has nothing to do with choosing the set of best 
 ] cost paths to Y. When that set is chosen, and only when, you can do 
 ] whatever you want in selecting which ones you want to use, including 
 ] the use of the TE metric; however, TE MUST not play any part in 
 ] selecting the initial set of best cost paths.
 ] 

we are not talking about changing the paths to the spf nodes. we are
only discussing how to determine the paths to reach the prefixes with
TE tunnel being used. unless as you suggested, an implementation 
have an 'always use TE tunnel' for the routes, there is certainly
the possibility of routing loop if higher than 'normal' metric being
used for the routes. again, this is also implementation issues, one
can store the TE tunnel metric along with the hop-by-hop metric; later
when one comes to another nodes announcing the same route, only
compare with the hop-by-hop metric.

since the route preference duing calculation is part of the spf
implementation, I would think we need to mention this possibility
of looping issues.

thanks.

 ] Chris.
 ] 
 ] >
 ] > thanks.
 ] >
 ] >  ]
 ] >  ] Thanks,
 ] >  ] Chris.
 ] >  ]
 ] >  ]
 ] >  ] > thanks.
 ] >  ] >
 ] >  ] >  ]
 ] >  ] >  ] Which again, is why the following is stated earlier in the 
 ] > document.
 ] >  ] >  ]
 ] >  ] >  ] >  ] This is stated earlier in this section:
 ] >  ] >  ] >  ]
 ] >  ] >  ] >  ] "Setting a manual metric on a TE-tunnel does not impact 
 ] > the
 ] >  ] > SPF=20
 ] >  ] >  ] >  ] algorithm itself."
 ] >  ] >  ] >  ]
 ] >  ] >  ] >  ] The only thing the TE tunnel metric can affect is whether 
 ] > TE
 ] >  ] >  ] > tunnel=20
 ] >  ] >  ] >  ] nexthop is chosen over the IGP nexthop when a route is 
 ] > being
 ] >  ] >  ] > installed,=20=
 ] >  ] >  ] >  ]
 ] >  ] >  ] >  ] and when *IGP metric* based ECMP routes are being 
 ] > considered.
 ] >  ] >  ]
 ] >  ] >  ] Chris.
 ] >  ] >  ]
 ] >  ] >  ] > - Naiming
 ] >  ] >  ] >
 ] >  ] >  ] > _______________________________________________
 ] >  ] >  ] > Rtgwg mailing list
 ] >  ] >  ] > Rtgwg@ietf.org
 ] >  ] >  ] > https://www1.ietf.org/mailman/listinfo/rtgwg
 ] >  ] >  ]
 ] >  ] >  ]
 ] >  ] >  ] _______________________________________________
 ] >  ] >  ] Rtgwg mailing list
 ] >  ] >  ] Rtgwg@ietf.org
 ] >  ] >  ] https://www1.ietf.org/mailman/listinfo/rtgwg
 ] >  ] >
 ] >  ] > - Naiming
 ] >  ]
 ] >  ]
 ] >  ] _______________________________________________
 ] >  ] Rtgwg mailing list
 ] >  ] Rtgwg@ietf.org
 ] >  ] https://www1.ietf.org/mailman/listinfo/rtgwg
 ] >
 ] > - Naiming
 ] 
 ] 
 ] _______________________________________________
 ] Rtgwg mailing list
 ] Rtgwg@ietf.org
 ] https://www1.ietf.org/mailman/listinfo/rtgwg

- Naiming

_______________________________________________
Rtgwg mailing list
Rtgwg@ietf.org
https://www1.ietf.org/mailman/listinfo/rtgwg



From exim@www1.ietf.org  Tue Mar 30 18:56:25 2004
Received: from optimus.ietf.org (optimus.ietf.org [132.151.1.19])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id SAA07992
	for <rtgwg-archive@odin.ietf.org>; Tue, 30 Mar 2004 18:56:25 -0500 (EST)
Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1B8Riv-0006ZK-Vw
	for rtgwg-archive@odin.ietf.org; Tue, 30 Mar 2004 17:28:45 -0500
Received: (from exim@localhost)
	by www1.ietf.org (8.12.8/8.12.8/Submit) id i2IKgwSg015048
	for rtgwg-archive@odin.ietf.org; Thu, 18 Mar 2004 15:42:58 -0500
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1B44Ly-0003ua-06
	for rtgwg-web-archive@optimus.ietf.org; Thu, 18 Mar 2004 15:42:58 -0500
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id PAA07663
	for <rtgwg-web-archive@ietf.org>; Thu, 18 Mar 2004 15:42:55 -0500 (EST)
Received: from ietf-mx ([132.151.6.1])
	by ietf-mx with esmtp (Exim 4.12)
	id 1B44Lw-0002Hx-00
	for rtgwg-web-archive@ietf.org; Thu, 18 Mar 2004 15:42:56 -0500
Received: from exim by ietf-mx with spam-scanned (Exim 4.12)
	id 1B44Ku-0002CI-00
	for rtgwg-web-archive@ietf.org; Thu, 18 Mar 2004 15:41:53 -0500
Received: from optimus.ietf.org ([132.151.1.19])
	by ietf-mx with esmtp (Exim 4.12)
	id 1B44KC-00027x-00
	for rtgwg-web-archive@ietf.org; Thu, 18 Mar 2004 15:41:08 -0500
Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1B44J6-0002yZ-LV; Thu, 18 Mar 2004 15:40:00 -0500
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org)
	by optimus.ietf.org with esmtp (Exim 4.20)
	id 1B44Il-0002tN-BK
	for rtgwg@optimus.ietf.org; Thu, 18 Mar 2004 15:39:39 -0500
Received: from CNRI.Reston.VA.US (localhost [127.0.0.1])
	by ietf.org (8.9.1a/8.9.1a) with ESMTP id PAA07361;
	Thu, 18 Mar 2004 15:39:36 -0500 (EST)
Message-Id: <200403182039.PAA07361@ietf.org>
Mime-Version: 1.0
Content-Type: Multipart/Mixed; Boundary="NextPart"
To: IETF-Announce: ;
Cc: rtgwg@ietf.org
From: Internet-Drafts@ietf.org
Reply-to: Internet-Drafts@ietf.org
Subject: I-D ACTION:draft-ietf-rtgwg-rfc3682bis-01.txt
Date: Thu, 18 Mar 2004 15:39:36 -0500
Sender: rtgwg-admin@ietf.org
Errors-To: rtgwg-admin@ietf.org
X-BeenThere: rtgwg@ietf.org
X-Mailman-Version: 2.0.12
Precedence: bulk
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/rtgwg>,
	<mailto:rtgwg-request@ietf.org?subject=unsubscribe>
List-Id: <rtgwg.ietf.org>
List-Post: <mailto:rtgwg@ietf.org>
List-Help: <mailto:rtgwg-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/rtgwg>,
	<mailto:rtgwg-request@ietf.org?subject=subscribe>
X-Spam-Checker-Version: SpamAssassin 2.60 (1.212-2003-09-23-exp) on 
	ietf-mx.ietf.org
X-Spam-Status: No, hits=0.5 required=5.0 tests=AWL,MIME_BOUND_NEXTPART,
	NO_REAL_NAME autolearn=no version=2.60

--NextPart

A New Internet-Draft is available from the on-line Internet-Drafts directories.
This draft is a work item of the Routing Area Working Group Working Group of the IETF.

	Title		: The Generalized TTL Security Mechanism (GTSM)
	Author(s)	: V. Gill, J. Heasley, D. Meyer
	Filename	: draft-ietf-rtgwg-rfc3682bis-01.txt
	Pages		: 14
	Date		: 2004-3-18
	
The use of a packet's TTL (IPv4) or Hop Limit (IPv6) to protect a
   protocol stack from CPU-utilization based attacks has been proposed
   in many settings (see for example, RFC 2461). This document
   generalizes these techniques for use by other protocols such as BGP
   (RFC 1771), MSDP, Bidirectional Forwarding Detection, and LDP (RFC
   3036). While the Generalized TTL Security Mechanism (GTSM)  is most
   effective in protecting directly connected protocol peers, it can
   also provide a lower level of protection to multi-hop sessions. GTSM
   is not directly applicable to protocols employing flooding mechanisms
   (e.g., multicast), and use of multi-hop GTSM should be considered on
   a case-by-case basis.

A URL for this Internet-Draft is:
http://www.ietf.org/internet-drafts/draft-ietf-rtgwg-rfc3682bis-01.txt

To remove yourself from the IETF Announcement list, send a message to 
ietf-announce-request with the word unsubscribe in the body of the message.

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-rtgwg-rfc3682bis-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-rtgwg-rfc3682bis-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:	<2004-3-18153521.I-D@ietf.org>

ENCODING mime
FILE /internet-drafts/draft-ietf-rtgwg-rfc3682bis-01.txt

--OtherAccess
Content-Type: Message/External-body;
	name="draft-ietf-rtgwg-rfc3682bis-01.txt";
	site="ftp.ietf.org";
	access-type="anon-ftp";
	directory="internet-drafts"

Content-Type: text/plain
Content-ID:	<2004-3-18153521.I-D@ietf.org>

--OtherAccess--

--NextPart--



_______________________________________________
Rtgwg mailing list
Rtgwg@ietf.org
https://www1.ietf.org/mailman/listinfo/rtgwg



