Re: [OSPF] Mail regarding draft-ietf-ospf-ospfv3-autoconfig

Acee Lindem <acee.lindem@ericsson.com> Thu, 03 October 2013 12:37 UTC

Return-Path: <acee.lindem@ericsson.com>
X-Original-To: ospf@ietfa.amsl.com
Delivered-To: ospf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 226FD11E80F2 for <ospf@ietfa.amsl.com>; Thu, 3 Oct 2013 05:37:31 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.599
X-Spam-Level:
X-Spam-Status: No, score=-2.599 tagged_above=-999 required=5 tests=[AWL=0.001, 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 JPDlMaecoCXR for <ospf@ietfa.amsl.com>; Thu, 3 Oct 2013 05:37:16 -0700 (PDT)
Received: from usevmg20.ericsson.net (usevmg20.ericsson.net [198.24.6.45]) by ietfa.amsl.com (Postfix) with ESMTP id B623E11E80E6 for <ospf@ietf.org>; Thu, 3 Oct 2013 05:35:40 -0700 (PDT)
X-AuditID: c618062d-b7fda8e0000024c6-3c-524d649a6fa1
Received: from EUSAAHC008.ericsson.se (Unknown_Domain [147.117.188.96]) by usevmg20.ericsson.net (Symantec Mail Security) with SMTP id F6.5B.09414.A946D425; Thu, 3 Oct 2013 14:35:38 +0200 (CEST)
Received: from EUSAAMB101.ericsson.se ([147.117.188.118]) by EUSAAHC008.ericsson.se ([147.117.188.96]) with mapi id 14.02.0328.009; Thu, 3 Oct 2013 08:35:27 -0400
From: Acee Lindem <acee.lindem@ericsson.com>
To: Rajib Majila <rajib.majila@ericsson.com>
Thread-Topic: Mail regarding draft-ietf-ospf-ospfv3-autoconfig
Thread-Index: AQHOwASlI9PLx/zgAkW2E2LSvWff95ni+UKAgAAUHYCAAB+4AA==
Date: Thu, 03 Oct 2013 12:35:26 +0000
Message-ID: <94A203EA12AECE4BA92D42DBFFE0AE47030748E7@eusaamb101.ericsson.se>
References: <524D1358.3020509@ericsson.com> <94A203EA12AECE4BA92D42DBFFE0AE47030744EA@eusaamb101.ericsson.se> <524D49F3.3030502@ericsson.com>
In-Reply-To: <524D49F3.3030502@ericsson.com>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach:
X-MS-TNEF-Correlator:
x-originating-ip: [147.117.188.134]
Content-Type: text/plain; charset="us-ascii"
Content-ID: <B8BAE163B5A18D458F4ECD0573C3B623@ericsson.com>
Content-Transfer-Encoding: quoted-printable
MIME-Version: 1.0
X-Brightmail-Tracker: H4sIAAAAAAAAA+NgFnrKLMWRmVeSWpSXmKPExsUyuXRPgu6sFN8gg21H5SwWbP7HbtFy7x67 A5PHkiU/mTy+XP7MFsAUxWWTkpqTWZZapG+XwJVxcvo2poLJAhUzVpxma2B8ytPFyMkhIWAi 0fnsPzuELSZx4d56ti5GLg4hgaOMEhO3vmWBcJYxSjy/t5kFpIpNQEfi+aN/zCC2CJDdvHkm K0gRs0Abo8Tbc6fBEsICthIbl05kgSiyk7g+ezFTFyMHkO0k8fuKAUiYRUBFYsvByWDlvAK+ Em9efGCCWDaRUWJe03mwXk6gBXuO7GMDsRmBzvt+ag0TiM0sIC5x68l8JoizBSSW7DnPDGGL Srx8/I8VwlaWWPJkPwtEvY7Egt2f2EBuYBawlug7LQMR1pZYtvA11A2CEidnPmGZwCg+C8mG WUi6ZyF0z0LSPQtJ9wJG1lWMHKXFqWW56UYGmxiBUXVMgk13B+Oel5aHGKU5WJTEeb+8dQ4S EkhPLEnNTk0tSC2KLyrNSS0+xMjEwSnVwKhleOAua+3cozqearmXEzatDt2wPn5+S1TaJnE1 jyi3kPUzVQ79XbM2en7LxZgTxlY2iq5t899+LbR26y5kMlu2lTtGdcnVZ+5vpVW0DDinmXdc fX3g8Um5v1Zb9Gzsvq1t+LXD4i7v7e87Mrzf2sncjD28ZVZE8FMe44TTQr13J72cLn0i7pMS S3FGoqEWc1FxIgAiI0bVeAIAAA==
Cc: OSPF List <ospf@ietf.org>, "draft-ietf-ospf-ospfv3-autoconfig@tools.ietf.org" <draft-ietf-ospf-ospfv3-autoconfig@tools.ietf.org>
Subject: Re: [OSPF] Mail regarding draft-ietf-ospf-ospfv3-autoconfig
X-BeenThere: ospf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: The Official IETF OSPG WG Mailing List <ospf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ospf>, <mailto:ospf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ospf>
List-Post: <mailto:ospf@ietf.org>
List-Help: <mailto:ospf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ospf>, <mailto:ospf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Thu, 03 Oct 2013 12:37:31 -0000

Hi Rajib,

On Oct 3, 2013, at 6:41 AM, Rajib Majila wrote:

> Hi Acee,
> 
> Thanks for the response. Please find my comments below on the last point.
> "
> 3.    Duplicate router-id detection: Can a self originated hello packet be identified by looking at the source
> IPv6 address and comparing the same against the IP addresses of the local interfaces. If you do not see
> any issue with this approach, it can eliminate the need to have a new LSA and thereby simplifying the
> implementation.
> 
> Hello are only exchanged between adjacent neighbors.  The router-id must be unique within the entire OSPF routing domain.
> "
> 
> What I was getting at was not just hellos but any OSPFv3 packets which can loosely be termed as link-scope.
> Your primary intention here is to identify if the duplicate router-id detection mechanism is going to declare
> an id as duplicate because multiple router interfaces are wrongly connected to the same link. I was wondering
> if this can be achieved simply by comparing the source IP address against the link-local addresses of all the
> local interfaces. Since here we are talking about link-local addresses, I am not even considering the packets
> which are non-link scope (area or AS).

That would be the most straight forward way to implement duplicate detection on a link. I did not describe implementation in the draft. 


> 
> Also your draft sets the flooding scope of this new LSA to Area-scope. If you are actually trying to detect
> duplicate router-id across the the OSPF domain by flooding this LSA across the domain, should it not be set
> to AS-scope? Also detecting a duplicate router-id across the domain might be tricky as even AS-scope LSAs
> are not forwarded into stub/nssa.

I'd originally thought that area uniqueness would be good enough. I'm now thinking that it should be AS-External scope even though the initial auto-configuration use case is single area only. 

Thanks,
Acee

> 
> Rajib
> 
>