[Gen-art] Re: GEN-ART review of draft-ietf-ccamp-loose-path-reopt-01

Harald Tveit Alvestrand <harald@alvestrand.no> Sun, 05 February 2006 12:26 UTC

Received: from localhost.cnri.reston.va.us ([127.0.0.1] helo=megatron.ietf.org) by megatron.ietf.org with esmtp (Exim 4.32) id 1F5iy1-0005Xu-N5; Sun, 05 Feb 2006 07:26:09 -0500
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org) by megatron.ietf.org with esmtp (Exim 4.32) id 1F5ixz-0005Wu-K0 for gen-art@megatron.ietf.org; Sun, 05 Feb 2006 07:26:08 -0500
Received: from ietf-mx.ietf.org (ietf-mx [132.151.6.1]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id HAA03772 for <gen-art@ietf.org>; Sun, 5 Feb 2006 07:24:27 -0500 (EST)
Received: from eikenes.alvestrand.no ([158.38.152.233]) by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1F5j9x-0001zb-LY for gen-art@ietf.org; Sun, 05 Feb 2006 07:38:31 -0500
Received: from localhost (eikenes.alvestrand.no [127.0.0.1]) by eikenes.alvestrand.no (Postfix) with ESMTP id 6312625970F; Sun, 5 Feb 2006 13:24:38 +0100 (CET)
Received: from eikenes.alvestrand.no ([127.0.0.1]) by localhost (eikenes.alvestrand.no [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 25504-07; Sun, 5 Feb 2006 13:24:33 +0100 (CET)
Received: from halvestr-w2k02.emea.cisco.com (eikenes.alvestrand.no [127.0.0.1]) by eikenes.alvestrand.no (Postfix) with ESMTP id 3F71225970D; Sun, 5 Feb 2006 13:24:32 +0100 (CET)
Date: Sun, 05 Feb 2006 13:12:26 +0100
From: Harald Tveit Alvestrand <harald@alvestrand.no>
To: JP Vasseur <jvasseur@cisco.com>
Message-ID: <2913423ED9ED9029779E82D7@B50854F0A9192E8EC6CDA126>
In-Reply-To: <FB85FC92-E66E-4277-9D7D-6FA5D95A677C@cisco.com>
References: <31E5D26B8A12D889312D466C@B50854F0A9192E8EC6CDA126> <FB85FC92-E66E-4277-9D7D-6FA5D95A677C@cisco.com>
X-Mailer: Mulberry/4.0.3 (Win32)
MIME-Version: 1.0
X-Virus-Scanned: by amavisd-new at alvestrand.no
X-Spam-Score: 0.0 (/)
X-Scan-Signature: f4c2cf0bccc868e4cc88dace71fb3f44
Cc: raymond_zhang@infonet.com, kireeti@juniper.net, adrian@olddog.co.uk, gen-art@ietf.org, fenner@research.att.com, y.ikejiri@ntt.com, jpv@cisco.com
Subject: [Gen-art] Re: GEN-ART review of draft-ietf-ccamp-loose-path-reopt-01
X-BeenThere: gen-art@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: "GEN-ART: General Area Review Team" <gen-art.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/gen-art>, <mailto:gen-art-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www1.ietf.org/pipermail/gen-art>
List-Post: <mailto:gen-art@ietf.org>
List-Help: <mailto:gen-art-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/gen-art>, <mailto:gen-art-request@ietf.org?subject=subscribe>
Content-Type: multipart/mixed; boundary="===============0002517861=="
Sender: gen-art-bounces@ietf.org
Errors-To: gen-art-bounces@ietf.org

Good that it was helpful!

One outstanding issue.....

--On 2. februar 2006 11:22 -0500 JP Vasseur <jvasseur@cisco.com> wrote:

>> - The order in which the two mechanisms are introduced in section 2
>> and 4 was confusing to me at first read. I think it would flow
>> better if the midpoint to headend signalling was mentioned first,
>> and the headend to midpoint mechanism was defined afterwards,
>> saying something like
>>
>>        - A head-end LSR to trigger on every LSR whose next hop is a
>>        loose hop or an abstract node the re-evaluation of the current
>>        path in order to detect a potential more optimal path, which
>> may
>>        result in the mid-point LSR using the mechanism above to signal
>>        the existence of such a more optimal path
>>
>> (Note: The English of the paragraph reads oddly, given that the
>> bullets do not form complete sentences without the introductory
>> text; it's possible to do this better, I think.)
>>
>
> I kept the same order (because the first mechanism is likely to be  the
> one more commonly used - that said, they're not exclusive) but I
> reworded a bit since indeed clarify could be improved. Thanks.

isn't the answer to the headend-to-midpoint query an instance of the 
midpoint-to-headend signal?

from the doc, I understood it as if the headend can't tell the difference 
between a spontaneous reoptimization and a reoptimization done in response 
to a headend query - but there may be a difference I missed.

Not terribly important!


_______________________________________________
Gen-art mailing list
Gen-art@ietf.org
https://www1.ietf.org/mailman/listinfo/gen-art