Re: 答复: 答复: Soliciting WG feedback and comments on draft-zxd-rtgwg-ordered-metric-adjustment-00
Stewart Bryant <stbryant@cisco.com> Thu, 31 October 2013 14:11 UTC
Return-Path: <stbryant@cisco.com>
X-Original-To: rtgwg@ietfa.amsl.com
Delivered-To: rtgwg@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 1C9AC21E808F for <rtgwg@ietfa.amsl.com>; Thu, 31 Oct 2013 07:11:51 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -110.292
X-Spam-Level:
X-Spam-Status: No, score=-110.292 tagged_above=-999 required=5 tests=[AWL=-0.145, BAYES_00=-2.599, MIME_8BIT_HEADER=0.3, RCVD_IN_DNSWL_HI=-8, SARE_SUB_ENC_UTF8=0.152, USER_IN_WHITELIST=-100]
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 5sjqaL8FCqAm for <rtgwg@ietfa.amsl.com>; Thu, 31 Oct 2013 07:11:46 -0700 (PDT)
Received: from ams-iport-2.cisco.com (ams-iport-2.cisco.com [144.254.224.141]) by ietfa.amsl.com (Postfix) with ESMTP id A332F11E80FA for <rtgwg@ietf.org>; Thu, 31 Oct 2013 07:11:45 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=cisco.com; i=@cisco.com; l=5091; q=dns/txt; s=iport; t=1383228705; x=1384438305; h=message-id:date:from:reply-to:mime-version:to:subject: references:in-reply-to:content-transfer-encoding; bh=Rk0I0y7tdsatb+a3J0AlSVQZVWLEuzFkJdFSmJoNa40=; b=YJO2EWBpuvwDJATgLeoggNzDxVAih+iJyPA30Poo5CzslsLYTEkS1Y2e G6BBq5EfsLYOgfAeDA+J3nyxjASloZ0BsgF5zPLDNNPuH+rNhMiEKFyBZ +7aLTBbFkIS6j/FZQ8FHm1eR2t/j9Bb4MQyGwwKCZwl+Ld7VovJNWD/Dv g=;
X-IronPort-Anti-Spam-Filtered: true
X-IronPort-Anti-Spam-Result: AtQ4AKNjclKQ/khR/2dsb2JhbABZgwc4g2eJHrM3gSQWdIIlAQEBBAEBASAPAQU2ChEJAhgCAgUWBAQDAgIJAwIBAgEVHwYLEwYCAQEFh34NjgWbXpJbgSmOLYJrgUMDmAuBL5BagWiBPg
X-IronPort-AV: E=Sophos;i="4.93,609,1378857600"; d="scan'208";a="87806455"
Received: from ams-core-1.cisco.com ([144.254.72.81]) by ams-iport-2.cisco.com with ESMTP; 31 Oct 2013 14:11:37 +0000
Received: from cisco.com (mrwint.cisco.com [64.103.70.36]) by ams-core-1.cisco.com (8.14.5/8.14.5) with ESMTP id r9VEBV96020476 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO) for <rtgwg@ietf.org>; Thu, 31 Oct 2013 14:11:33 GMT
Received: from [IPv6:::1] (localhost [127.0.0.1]) by cisco.com (8.14.4+Sun/8.8.8) with ESMTP id r9VEBVNx017029; Thu, 31 Oct 2013 14:11:31 GMT
Message-ID: <52726513.8040705@cisco.com>
Date: Thu, 31 Oct 2013 14:11:31 +0000
From: Stewart Bryant <stbryant@cisco.com>
User-Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.8; rv:24.0) Gecko/20100101 Thunderbird/24.1.0
MIME-Version: 1.0
To: rtgwg@ietf.org
Subject: Re: 答复: 答复: Soliciting WG feedback and comments on draft-zxd-rtgwg-ordered-metric-adjustment-00
References: <D496C972D1A13540A730720631EC73413A39ECE3@nkgeml507-mbs.china.huawei.com> <94A203EA12AECE4BA92D42DBFFE0AE470309F337@eusaamb101.ericsson.se> <D496C972D1A13540A730720631EC73413A39EF60@nkgeml507-mbs.china.huawei.com> <94A203EA12AECE4BA92D42DBFFE0AE47030A2579@eusaamb101.ericsson.se> <D496C972D1A13540A730720631EC73413A39EF7C@nkgeml507-mbs.china.huawei.com> <5266434B.4050309@gmail.com>
In-Reply-To: <5266434B.4050309@gmail.com>
Content-Type: text/plain; charset="UTF-8"; format="flowed"
Content-Transfer-Encoding: 8bit
X-BeenThere: rtgwg@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
Reply-To: stbryant@cisco.com
List-Id: Routing Area Working Group <rtgwg.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/rtgwg>, <mailto:rtgwg-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/rtgwg>
List-Post: <mailto:rtgwg@ietf.org>
List-Help: <mailto:rtgwg-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/rtgwg>, <mailto:rtgwg-request@ietf.org?subject=subscribe>
X-List-Received-Date: Thu, 31 Oct 2013 14:11:51 -0000
Please note Cisco declared IPR on RFC 5715 section 6.1 - Stewart On 22/10/2013 10:20, Mike Shand wrote: > So you have described the difference with OFIB (RFC 6976), but how > does your proposal differ from "incremental cost advertisement" as > described in RFC 5715 section 6.1? > > Mike > > > > On 22/10/2013 04:39, Yangang wrote: >> OK, I got it. >> >> Actually, we pay attention to two point: >> >> 1. Which method will be more nicety? In RFC6976, all devices in >> network need calculate the schedule time, base on the different >> hardware and environment, we worry about its effect. In our draft, >> only failure point adjust the cost, the other device just response >> the cost change. I think the effect of this kind of difference will >> be less. >> >> 2. Due to no new extension, maybe the distribution will be more >> smoothly. >> >> -----邮件原件----- >> 发件人: Acee Lindem [mailto:acee.lindem@ericsson.com] >> 发送时间: 2013年10月22日 9:42 >> 收件人: Yangang >> 抄送: rtgwg@ietf.org; Zhangxudong (zhangxudong, VRP) >> 主题: Re: 答复: Soliciting WG feedback and comments on >> draft-zxd-rtgwg-ordered-metric-adjustment-00 >> >> I'm aware of the basic premise of the two drafts and was not asking >> for you to restate the obvious. Specifically, what are the benefits >> and determents of your draft when compared to RFC 6976? >> Acee >> >> On Oct 21, 2013, at 9:30 PM, Yangang wrote: >> >>> Our draft is similar with section 6.1 in RFC5715, the cost of >>> changed link will be adjusted and advertised, maybe more than one >>> time, this sequence will base on some pre-calculations. But in RFC >>> 6976, each device should calculate the distance with the failue >>> link, base on this distance, each device decide when the FIB will be >>> updated. >>> >>> -----邮件原件----- >>> 发件人: Acee Lindem [mailto:acee.lindem@ericsson.com] >>> 发送时间: 2013年10月21日 10:07 >>> 收件人: Yangang >>> 抄送: rtgwg@ietf.org; Zhangxudong (zhangxudong, VRP) >>> 主题: Re: Soliciting WG feedback and comments on >>> draft-zxd-rtgwg-ordered-metric-adjustment-00 >>> >>> Can you contrast this with RFC 6976? You include RFC 6976 in the >>> Normative References but it is never referenced (this will show up >>> if you run idnits). >>> Acee >>> On Oct 20, 2013, at 9:49 PM, Yangang wrote: >>> >>>> Hi: >>>> >>>> We had submitted the a new draft: >>>> http://tools.ietf.org/html/draft-zxd-rtgwg-ordered-metric-adjustment-00, >>>> we want to discuss the micro-loop problem through another method. >>>> Your feedback and comments on the rtgwg mailing list are appreciated. >>>> >>>> Thanks, >>>> Rahul.Yan >>>> >>>> -----邮件原件----- >>>> 发件人: internet-drafts@ietf.org [mailto:internet-drafts@ietf.org] >>>> 发送时间: 2013年10月18日 15:47 >>>> 收件人: Zhangxudong (zhangxudong, VRP); Yangang >>>> 主题: New Version Notification for >>>> draft-zxd-rtgwg-ordered-metric-adjustment-00.txt >>>> >>>> >>>> A new version of I-D, draft-zxd-rtgwg-ordered-metric-adjustment-00.txt >>>> has been successfully submitted by Xudong Zhang and posted to the >>>> IETF repository. >>>> >>>> Filename: draft-zxd-rtgwg-ordered-metric-adjustment >>>> Revision: 00 >>>> Title: Algorithm for Ordered Metric Adjustment >>>> Creation date: 2013-10-18 >>>> Group: Individual Submission >>>> Number of pages: 10 >>>> URL: >>>> http://www.ietf.org/internet-drafts/draft-zxd-rtgwg-ordered-metric-adjustment-00.txt >>>> Status: >>>> http://datatracker.ietf.org/doc/draft-zxd-rtgwg-ordered-metric-adjustment >>>> Htmlized: >>>> http://tools.ietf.org/html/draft-zxd-rtgwg-ordered-metric-adjustment-00 >>>> >>>> >>>> >>>> Abstract: >>>> Upon link down event or link up event, each device in network >>>> individually schedules route calculation. Because of different >>>> hardware capabilities and internal/external environments, the >>>> time to >>>> update forwarding entries on these devices are disordered which can >>>> cause a transient forwarding loop. This document introduces a >>>> method >>>> to prevent forwarding loop by adjusting link metric gradually for >>>> several times. >>>> >>>> >>>> >>>> >>>> >>>> Please note that it may take a couple of minutes from the time of >>>> submission >>>> until the htmlized version and diff are available at tools.ietf.org. >>>> >>>> The IETF Secretariat >>>> >>>> _______________________________________________ >>>> rtgwg mailing list >>>> rtgwg@ietf.org >>>> https://www.ietf.org/mailman/listinfo/rtgwg >> _______________________________________________ >> rtgwg mailing list >> rtgwg@ietf.org >> https://www.ietf.org/mailman/listinfo/rtgwg > > _______________________________________________ > rtgwg mailing list > rtgwg@ietf.org > https://www.ietf.org/mailman/listinfo/rtgwg -- For corporate legal information go to: http://www.cisco.com/web/about/doing_business/legal/cri/index.html
- Soliciting WG feedback and comments on draft-zxd-… Yangang
- Re: Soliciting WG feedback and comments on draft-… Acee Lindem
- Re: Soliciting WG feedback and comments on draft-… Alia Atlas
- 答复: Soliciting WG feedback and comments on draft-… Yangang
- Re: 答复: Soliciting WG feedback and comments on dr… Acee Lindem
- 答复: 答复: Soliciting WG feedback and comments on dr… Yangang
- Re: 答复: 答复: Soliciting WG feedback and comments o… Mike Shand
- RE: 答复: 答复: Soliciting WG feedback and comments o… stephane.litkowski
- RE: Soliciting WG feedback and comments on draft-… stephane.litkowski
- Re: 答复: 答复: Soliciting WG feedback and comments o… Stewart Bryant
- Re: Soliciting WG feedback and comments on draft-… Pierre Francois
- Re: Soliciting WG feedback and comments on draft-… Alia Atlas
- Re: Soliciting WG feedback and comments on draft-… Pierre Francois
- RE: Soliciting WG feedback and comments on draft-… stephane.litkowski