IETF Logo Mail Archive

[rtgwg] draft-ietf-rtgwg-mrt-frr-algorithm-03

"Anil Kumar S N (VRP Network BL)" <anil.sn@huawei.com> Mon, 22 June 2015 10:00 UTC

Return-Path: <anil.sn@huawei.com>
X-Original-To: rtgwg@ietfa.amsl.com
Delivered-To: rtgwg@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 909CE1B2DA0; Mon, 22 Jun 2015 03:00:20 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.011
X-Spam-Level:
X-Spam-Status: No, score=-2.011 tagged_above=-999 required=5 tests=[BAYES_20=-0.001, HTML_MESSAGE=0.001, MIME_8BIT_HEADER=0.3, RCVD_IN_DNSWL_MED=-2.3, SPF_PASS=-0.001, T_RP_MATCHES_RCVD=-0.01] autolearn=ham
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id zgeUg9-9DxGH; Mon, 22 Jun 2015 03:00:18 -0700 (PDT)
Received: from lhrrgout.huawei.com (lhrrgout.huawei.com [194.213.3.17]) (using TLSv1 with cipher RC4-SHA (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id D0D7A1B2EED; Mon, 22 Jun 2015 03:00:14 -0700 (PDT)
Received: from 172.18.7.190 (EHLO lhreml402-hub.china.huawei.com) ([172.18.7.190]) by lhrrg01-dlp.huawei.com (MOS 4.3.7-GA FastPath queued) with ESMTP id BXU63808; Mon, 22 Jun 2015 10:00:13 +0000 (GMT)
Received: from NKGEML403-HUB.china.huawei.com (10.98.56.34) by lhreml402-hub.china.huawei.com (10.201.5.241) with Microsoft SMTP Server (TLS) id 14.3.158.1; Mon, 22 Jun 2015 11:00:11 +0100
Received: from NKGEML512-MBX.china.huawei.com ([169.254.7.152]) by nkgeml403-hub.china.huawei.com ([10.98.56.34]) with mapi id 14.03.0158.001; Mon, 22 Jun 2015 18:00:05 +0800
From: "Anil Kumar S N (VRP Network BL)" <anil.sn@huawei.com>
To: Chris Bowers <cbowers@juniper.net>, Gábor Sándor Enyedi <gabor.sandor.enyedi@ericsson.com>, "Andras.Csaszar@ericsson.com" <Andras.Csaszar@ericsson.com>, Alia Atlas <akatlas@juniper.net>, "abishek@ece.arizona.edu" <abishek@ece.arizona.edu>
Subject: [rtgwg] draft-ietf-rtgwg-mrt-frr-algorithm-03
Thread-Topic: [rtgwg] draft-ietf-rtgwg-mrt-frr-algorithm-03
Thread-Index: AdCs0jJZPAk3Yrp1Ru+HLJ2KHEUVNA==
Date: Mon, 22 Jun 2015 10:00:03 +0000
Message-ID: <327562D94EA7BF428CD805F338C31EF04FB4417E@nkgeml512-mbx.china.huawei.com>
Accept-Language: en-US, zh-CN
Content-Language: en-US
X-MS-Has-Attach:
X-MS-TNEF-Correlator:
x-originating-ip: [10.18.212.150]
Content-Type: multipart/alternative; boundary="_000_327562D94EA7BF428CD805F338C31EF04FB4417Enkgeml512mbxchi_"
MIME-Version: 1.0
X-CFilter-Loop: Reflected
Archived-At: <http://mailarchive.ietf.org/arch/msg/rtgwg/oKZaRLeAO4tAqoaXr2_FMbOekng>
Cc: "rtgwg-owner@ietf.org" <rtgwg-owner@ietf.org>, "rtgwg@ietf.org" <rtgwg@ietf.org>
X-BeenThere: rtgwg@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
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: <https://mailarchive.ietf.org/arch/browse/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: Mon, 22 Jun 2015 10:00:20 -0000

Hi Chris,

                It's a small suggestion/request :) , The directions are more meaningful than what's explained under terminology section.
nomenclature is very clear that links are assigned with a direction , as a new reader I would like to know
when a link will be undirected/Outgoing/Incoming before jumping into algorithm and its purpose,
If you can elaborate it would be really helpful.

"In the GADAG, each link is marked as OUTGOING, INCOMING or both.  " is repeated.

3.  Terminology and Definitions

   UNDIRECTED:   In the GADAG, each link is marked as OUTGOING, INCOMING
      or both.  Until the directionality of the link is determined, the
      link is marked as UNDIRECTED to indicate that its direction hasn't
      been determined.

   OUTGOING:   In the GADAG, each link is marked as OUTGOING, INCOMING
      or both.  A link marked as OUTGOING has direction from the
      interface's router to the remote end.

   INCOMING:   In the GADAG, each link is marked as OUTGOING, INCOMING
      or both.  A link marked as INCOMING has direction from the remote
      end to the interface's router.


Thanks & Regards
Anil S N

"Be liberal in what you accept, and conservative in what you send" - Jon Postel

v2.23.0 | Report a Bug | By Email