Re: WG docs reminder

mike shand <mshand@cisco.com> Mon, 20 November 2006 09:46 UTC

Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com) by megatron.ietf.org with esmtp (Exim 4.43) id 1Gm5jb-0008D3-Be; Mon, 20 Nov 2006 04:46:39 -0500
Received: from [10.90.34.44] (helo=chiedprmail1.ietf.org) by megatron.ietf.org with esmtp (Exim 4.43) id 1Gm5jZ-0008Cx-UA for rtgwg@ietf.org; Mon, 20 Nov 2006 04:46:37 -0500
Received: from ams-iport-1.cisco.com ([144.254.224.140]) by chiedprmail1.ietf.org with esmtp (Exim 4.43) id 1Gm5jX-0006ur-ES for rtgwg@ietf.org; Mon, 20 Nov 2006 04:46:37 -0500
Received: from ams-dkim-1.cisco.com ([144.254.224.138]) by ams-iport-1.cisco.com with ESMTP; 20 Nov 2006 10:46:32 +0100
Received: from ams-core-1.cisco.com (ams-core-1.cisco.com [144.254.224.150]) by ams-dkim-1.cisco.com (8.12.11/8.12.11) with ESMTP id kAK9kVws025877; Mon, 20 Nov 2006 10:46:31 +0100
Received: from cisco.com (mrwint.cisco.com [64.103.71.48]) by ams-core-1.cisco.com (8.12.10/8.12.6) with ESMTP id kAK9kVwv021722; Mon, 20 Nov 2006 10:46:31 +0100 (MET)
Received: from mshand-wxp.cisco.com (ams3-vpn-dhcp4595.cisco.com [10.61.81.242]) by cisco.com (8.8.8-Cisco List Logging/8.8.8) with ESMTP id JAA02963; Mon, 20 Nov 2006 09:46:28 GMT
Message-Id: <7.0.1.0.0.20061120093834.0212d640@cisco.com>
X-Mailer: QUALCOMM Windows Eudora Version 7.0.1.0
Date: Mon, 20 Nov 2006 09:45:53 +0000
To: menth@informatik.uni-wuerzburg.de
From: mike shand <mshand@cisco.com>
In-Reply-To: <4561573E.9050604@informatik.uni-wuerzburg.de>
References: <p0623090bc1823a37fa83@[10.0.1.2]> <4561573E.9050604@informatik.uni-wuerzburg.de>
Mime-Version: 1.0
Content-Type: text/plain; charset="us-ascii"; format="flowed"
DKIM-Signature: v=0.5; a=rsa-sha256; q=dns/txt; l=2785; t=1164015991; x=1164879991; c=relaxed/simple; s=amsdkim1002; h=Content-Type:From:Subject:Content-Transfer-Encoding:MIME-Version; d=cisco.com; i=mshand@cisco.com; z=From:=20mike=20shand=20<mshand@cisco.com> |Subject:=20Re=3A=20WG=20docs=20reminder |Sender:=20; bh=nnp2lYl4qRCdATN4yycwm+Bpfu7MRQ2pXm+ZNkc3gns=; b=Z8G8j1NcYklCgq2SpMDTq889zsc2WAm14m5lMs0dck0KigCeTUvpm6LCZdPBXBN+kPaQ75wz ZqNoOK0wZdKR/DqELoU4/BFBXCVFAUzaplCRJAvps6Wwn9vBer6lptRg;
Authentication-Results: ams-dkim-1; header.From=mshand@cisco.com; dkim=pass ( sig from cisco.com/amsdkim1002 verified; );
X-Spam-Score: 0.0 (/)
X-Scan-Signature: 10d3e4e3c32e363f129e380e644649be
Cc: RĂ¼diger, "John G. Scudder" <jgs@cisco.com>, Martin <martin@informatik.uni-wuerzburg.de>, rtgwg@ietf.org
Subject: Re: WG docs reminder
X-BeenThere: rtgwg@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: rtgwg.ietf.org
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/rtgwg>, <mailto:rtgwg-request@ietf.org?subject=unsubscribe>
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>
Errors-To: rtgwg-bounces@ietf.org

At 07:20 20/11/2006, Michael Menth wrote:
>Dear John,
>
>draft-bryant-shand-lf-conv-frmwk-03.txt
>draft-bryant-shand-ipfrr-notvia-addresses-03.txt
>draft-francois-ordered-fib-02.txt
>We support these drafts.
>
>Here are some comments on draft-bryant-shand-ipfrr-notvia-addresses-03.txt.
>
>4.4 5.a.i: Does Fig. 3 refer to this case? In Fig. 3 P is NOT a next 
>hop of Y. I can imagine what this passage want, but it is hard to understand.

Yes it does refer to figure 3. I agree it is slightly confusing.

By "Y, a node whose next hop is P"

we mean that S's next hop towards Y is P

and conversely that S's next hop towards Z is not P

We will try to clarify that in the next version


>Regarding the iSPF calculation in 3):
>We studied the time savings achievable by incremental Shortest Path
>First algorithms in the context of resource management with resilience.
>Experimental results showed that the computation time can be reduced
>by up to 90% compared to full SPF computations when we also recomputed
>the new load distribution.
>http://www3.informatik.uni-wuerzburg.de/~menth/Publications/Menth06r.pdf


Interesting paper. I'll read it in depth later.

There are a number of furhter optimizations which can be applied to 
the not-via iSPF computation.

Have you thought about the effect of the use of the "early 
termination" once the not-via addresses have been re-attached.

>Typos:
>* 1. last sentence "in not" -> "is not"
>* 10. "process the chose encapsulation" -> "process the chosen encapsulation"
>* 14. "If an attacker were" -> "If an attacker was"

Thanks for the first two

actually the use of "were" (the subjunctive) is better English than 
"was" in this context.



>Best wishes,
>
>    Michael
>
>John G. Scudder wrote:
>>As a reminder, three documents were proposed as WG documents at our 
>>IETF-67 meeting:
>>
>>draft-bryant-shand-lf-conv-frmwk-03.txt
>>draft-bryant-shand-ipfrr-notvia-addresses-03.txt
>>draft-francois-ordered-fib-02.txt
>>
>>Rough consensus at the in-person meeting favored adoption.  The 
>>deadline for comments to the list is November 21 (this coming Tuesday).
>>
>>--John
>>
>>_______________________________________________
>>rtgwg mailing list
>>rtgwg@ietf.org
>>https://www1.ietf.org/mailman/listinfo/rtgwg
>
>--
>Dr. Michael Menth, Assistant Professor
>University of Wuerzburg, Institute of Computer Science
>Am Hubland, D-97074 Wuerzburg, Germany, room B206
>phone: (+49)-931/888-6644, fax: (+49)-931/888-6632
>mailto:menth@informatik.uni-wuerzburg.de
>http://www3.informatik.uni-wuerzburg.de/research/ngn
>
>
>_______________________________________________
>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