Re: [Idr] Solicit feedbacks on draft-dong-idr-end-of-rib-use-extension

Robert Raszuk <raszuk@cisco.com> Thu, 11 August 2011 13:15 UTC

Return-Path: <raszuk@cisco.com>
X-Original-To: idr@ietfa.amsl.com
Delivered-To: idr@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 6B34D21F87FC for <idr@ietfa.amsl.com>; Thu, 11 Aug 2011 06:15:37 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.969
X-Spam-Level:
X-Spam-Status: No, score=-2.969 tagged_above=-999 required=5 tests=[AWL=-0.370, BAYES_00=-2.599]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id U0M+HXXmlBcb for <idr@ietfa.amsl.com>; Thu, 11 Aug 2011 06:15:36 -0700 (PDT)
Received: from rcdn-iport-5.cisco.com (rcdn-iport-5.cisco.com [173.37.86.76]) by ietfa.amsl.com (Postfix) with ESMTP id BC9EB21F87ED for <idr@ietf.org>; Thu, 11 Aug 2011 06:15:36 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=cisco.com; i=raszuk@cisco.com; l=1130; q=dns/txt; s=iport; t=1313068571; x=1314278171; h=message-id:date:from:reply-to:mime-version:to:cc:subject: references:in-reply-to:content-transfer-encoding; bh=ScPWoCSW8fLBy1HehLtYB9MTIgAgSZULRU0aKScEkRQ=; b=NFWGDYausjGeAHMh6RCoGIvLOau6+ZLAwCXErk5AGaxCMF/S6bg2BG2G 7ufesj6icKLOSh3E54uhtJ2ekDzL4rEulmwzsIFmpvgPTs1XClETyVN9r /P/tVArcYxZTVrzk2oj0As3QH+uw96XN4u+40iNpgtxuEWFhuJ/OUAhQm k=;
X-IronPort-AV: E=Sophos;i="4.67,355,1309737600"; d="scan'208";a="12172766"
Received: from mtv-core-2.cisco.com ([171.68.58.7]) by rcdn-iport-5.cisco.com with ESMTP; 11 Aug 2011 13:16:10 +0000
Received: from [192.168.1.51] (ams-raszuk-2-87113.cisco.com [10.55.99.78]) by mtv-core-2.cisco.com (8.14.3/8.14.3) with ESMTP id p7BDG801030558; Thu, 11 Aug 2011 13:16:08 GMT
Message-ID: <4E43D60C.3000906@cisco.com>
Date: Thu, 11 Aug 2011 15:15:56 +0200
From: Robert Raszuk <raszuk@cisco.com>
User-Agent: Mozilla/5.0 (Windows; U; Windows NT 6.1; en-US; rv:1.9.2.18) Gecko/20110616 Thunderbird/3.1.11
MIME-Version: 1.0
To: Jie Dong <jie.dong@huawei.com>
References: <76CD132C3ADEF848BD84D028D243C9270B76B48C@szxeml509-mbs.china.huawei.com> <4E4186ED.4070001@cisco.com> <76CD132C3ADEF848BD84D028D243C9270B76B7A0@szxeml509-mbs.china.huawei.com> <4E431244.5050206@cisco.com> <76CD132C3ADEF848BD84D028D243C9270B76BE40@szxeml509-mbs.china.huawei.com>
In-Reply-To: <76CD132C3ADEF848BD84D028D243C9270B76BE40@szxeml509-mbs.china.huawei.com>
Content-Type: text/plain; charset="ISO-8859-1"; format="flowed"
Content-Transfer-Encoding: 7bit
Cc: "idr@ietf.org" <idr@ietf.org>
Subject: Re: [Idr] Solicit feedbacks on draft-dong-idr-end-of-rib-use-extension
X-BeenThere: idr@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
Reply-To: raszuk@cisco.com
List-Id: Inter-Domain Routing <idr.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/idr>, <mailto:idr-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/idr>
List-Post: <mailto:idr@ietf.org>
List-Help: <mailto:idr-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/idr>, <mailto:idr-request@ietf.org?subject=subscribe>
X-List-Received-Date: Thu, 11 Aug 2011 13:15:37 -0000

Hi Jie,

> It's good that we agree on this scenario. IMO now GR capability with
> null AFI/SAFI is for signaling "GR helper and EoR".

I would not agree with that. It is in fact just the opposite.

> If we want to use it to signal EoR only, we may need another way to
 > signal the GR helper capability.

+

> IMO the two scenarios mentioned in sec 4 cannot be signaled
> separately through one single capability format. Thus some additional
> flag needs be defined

While I did suggested the addition of flag after rethinking this a bit 
more I do not think it is necessary.

Here is my idea:

--

* When you signal GR capability with null AFI/SAFI list - it just means 
use of EOR - it does not mean you support helper mode.

* When you signal GR capability with non-null AFI/SAFI (at least one 
AFI/SAFI included) - it will mean use of EOR, helper mode support + GR 
support for this/those AFI/SAFIs.

--

If the GR RFC will clarify that to reflect such semantics I think all 
confusions are addressed and all cases covered without any need for 
protocol extension.

Thoughts ?

Thx,
R.