From: Acee Lindem <acee.lindem@ericsson.com>
To: "Retana, Alvaro" <alvaro.retana@hp.com>
Date: Thu, 31 May 2012 11:43:44 -0400
Thread-Topic: New Version Notification for
 draft-acee-ospf-ospfv3-autoconfig-02.txt
Thread-Index: Ac0/RCqU61zFhtkwRZmaLSNweOaP3A==
Message-ID: <4E55EFFC-AC9F-4CAD-A959-658A37D9DD23@ericsson.com>
References: <20120528194115.31565.2145.idtracker@ietfa.amsl.com>
 <4086D39E-4BC9-47CC-809D-271CEC738B57@ericsson.com>
 <C03AAF38AD209F4BB02BC0A34B774CE701D7A3@G2W2446.americas.hpqcorp.net>
In-Reply-To: <C03AAF38AD209F4BB02BC0A34B774CE701D7A3@G2W2446.americas.hpqcorp.net>
Accept-Language: en-US
Content-Language: en-US
acceptlanguage: en-US
Content-Type: text/plain; charset="Windows-1252"
Content-Transfer-Encoding: quoted-printable
MIME-Version: 1.0
Cc: OSPF List <ospf@ietf.org>, Jari Arkko <jari.arkko@piuha.net>
Subject: Re: [OSPF] New Version Notification for
 draft-acee-ospf-ospfv3-autoconfig-02.txt
Precedence: list

On May 31, 2012, at 11:34 AM, Retana, Alvaro wrote:

Hi!

My reason for the suggestion was that requiring a special instance ID (even=
 if well known) takes away from the auto-* properties by requiring other ro=
uters to behave in a special way.  IOW, the use case of adding an auto-conf=
iguration-capable router to an existing network would not be possible w/out=
 additional configuration and/or hacks.

I obviously like option #2. :)

IMHO, option #3 is not good because it still requires the auto-configuratio=
n-capable router to be configured beforehand=85which is an oxymoron!

This was not the intent of #3 - it was meant to allow an implementation to =
decide dependent on the targeted deployments. Even without the reserved ins=
tance ID, other parameters (area, hello, dead, etc) in the existing network=
 would need to use the auto-configured values.

Thanks,
Acee



Thanks!

Alvaro.

From: Acee Lindem [mailto:acee.lindem@ericsson.com]
Sent: Monday, May 28, 2012 4:19 PM
To: OSPF List
Cc: Jari Arkko; Retana, Alvaro
Subject: Fwd: New Version Notification for draft-acee-ospf-ospfv3-autoconfi=
g-02.txt

Speaking as a Draft Author:

This version includes additions based on comments received at IETF 83. Sect=
ion 5.1 clarifies the detection of a neighbor with a duplicate Router-ID to=
 exclude the case where multiple router interfaces are connected to the sam=
e link. Section 5.4 was added to mitigate the effects of a duplicate OSPFv3=
 Router-ID in the OSPFv3 routing domain prior to duplicate Router-ID resolu=
tion.

Additionally, we received a suggestion from Alvaro Retana to not use an res=
erved OSPFv3 instance ID for auto-configured routers. Rather, allow OSPFv3 =
auto-configured routers to use the default OSPFv3 instance ID and automatic=
ally join an existing non-autoconfigured OSPFv3 routing domain. I see three=
 possible alternatives:

    1. Reject the suggestion. The alternate OSPFv3 instance ID was added sp=
ecifically to prevent this.
    2. Adopt the suggestion and remove the reserved instance ID. The securi=
ty considerations now recommend that implementation provide the capability =
to configure a single key.
    3. Add an applicability statement indicating that an implementation MAY=
 use the default OSPFv3 instance if the network where the implementation is=
 deployed requires incorporation into an existing OSPFv3 network.

Please provide your thoughts on this issue.

Thanks,
Acee




Begin forwarded message:


From: "internet-drafts@ietf.org<mailto:internet-drafts@ietf.org>" <internet=
-drafts@ietf.org<mailto:internet-drafts@ietf.org>>
Date: May 28, 2012 3:41:15 PM EDT
To: Acee Lindem <acee.lindem@ericsson.com<mailto:acee.lindem@ericsson.com>>
Cc: "jari.arkko@piuha.net<mailto:jari.arkko@piuha.net>" <jari.arkko@piuha.n=
et<mailto:jari.arkko@piuha.net>>
Subject: New Version Notification for draft-acee-ospf-ospfv3-autoconfig-02.=
txt

A new version of I-D, draft-acee-ospf-ospfv3-autoconfig-02.txt has been suc=
cessfully submitted by Acee Lindem and posted to the IETF repository.

Filename:       draft-acee-ospf-ospfv3-autoconfig
Revision:       02
Title:              OSPFv3 Auto-Configuration
Creation date:            2012-05-28
WG ID:                     Individual Submission
Number of pages: 14

Abstract:
  OSPFv3 is a candidate for deployments in environments where auto-
  configuration is a requirement.  One such environment is the IPv6
  home network where users expect to simply plug in a router and have
  it automatically use OSPFv3 for intra-domain routing.  This document
  describes the necessary mechanisms for OSPFv3 to be self-configuring.




The IETF Secretariat