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

JP Vasseur <jvasseur@cisco.com> Mon, 06 February 2006 12:59 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 1F65xN-0007Nh-SQ; Mon, 06 Feb 2006 07:59:01 -0500
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org) by megatron.ietf.org with esmtp (Exim 4.32) id 1F65xD-0007MM-BG for gen-art@megatron.ietf.org; Mon, 06 Feb 2006 07:59:00 -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 HAA15281 for <gen-art@ietf.org>; Mon, 6 Feb 2006 07:57:02 -0500 (EST)
Received: from rtp-iport-1.cisco.com ([64.102.122.148]) by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1F669F-0005Yi-DM for gen-art@ietf.org; Mon, 06 Feb 2006 08:11:19 -0500
Received: from rtp-core-1.cisco.com ([64.102.124.12]) by rtp-iport-1.cisco.com with ESMTP; 06 Feb 2006 04:58:31 -0800
X-BrightmailFiltered: true
X-Brightmail-Tracker: AAAAAA==
X-IronPort-AV: i="4.02,91,1139212800"; d="scan'208"; a="21259585:sNHT25049188"
Received: from xbh-rtp-201.amer.cisco.com (xbh-rtp-201.cisco.com [64.102.31.12]) by rtp-core-1.cisco.com (8.12.10/8.12.6) with ESMTP id k16CwPPM018686; Mon, 6 Feb 2006 07:58:25 -0500 (EST)
Received: from xfe-rtp-202.amer.cisco.com ([64.102.31.21]) by xbh-rtp-201.amer.cisco.com with Microsoft SMTPSVC(6.0.3790.211); Mon, 6 Feb 2006 07:58:24 -0500
Received: from [192.168.1.101] ([10.86.240.249]) by xfe-rtp-202.amer.cisco.com with Microsoft SMTPSVC(6.0.3790.211); Mon, 6 Feb 2006 07:58:24 -0500
In-Reply-To: <2913423ED9ED9029779E82D7@B50854F0A9192E8EC6CDA126>
References: <31E5D26B8A12D889312D466C@B50854F0A9192E8EC6CDA126> <FB85FC92-E66E-4277-9D7D-6FA5D95A677C@cisco.com> <2913423ED9ED9029779E82D7@B50854F0A9192E8EC6CDA126>
Mime-Version: 1.0 (Apple Message framework v746.2)
Content-Type: text/plain; charset="US-ASCII"; delsp="yes"; format="flowed"
Message-Id: <78172685-CB09-4242-B936-67AE4017813B@cisco.com>
Content-Transfer-Encoding: 7bit
From: JP Vasseur <jvasseur@cisco.com>
Date: Mon, 06 Feb 2006 07:57:55 -0500
To: Harald Tveit Alvestrand <harald@alvestrand.no>
X-Mailer: Apple Mail (2.746.2)
X-OriginalArrivalTime: 06 Feb 2006 12:58:24.0434 (UTC) FILETIME=[03CB5120:01C62B1D]
X-Spam-Score: 0.0 (/)
X-Scan-Signature: b4a0a5f5992e2a4954405484e7717d8c
Content-Transfer-Encoding: 7bit
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>
Sender: gen-art-bounces@ietf.org
Errors-To: gen-art-bounces@ietf.org

Hi Harald,

Thanks for your reply (and your review)  - see in line

On Feb 5, 2006, at 7:12 AM, Harald Tveit Alvestrand wrote:

> 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.
>

You did not miss anything ;-) but in the mid-point notification case  
there are other cases that we handle such as the reoptimization for  
path maintenance and so on ... Thus starting with the head-end  
control function is more didactic ;-)

> Not terribly important!
>

Good, thanks. I'll repost today to move forward. Just a process- 
oriented question. What is the logical next step after having  
addressed the gen-art review comments ?

Thanks.

Cheers.

JP.

>

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