Re: [OSPF] New Version Notification for draft-acee-ospf-ospfv3-autoconfig-02.txt

["Retana, Alvaro" <[e-mail]>]

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 routers to behave in a special way.  IOW, the use case of adding an auto-configuration-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-configuration-capable router to be configured beforehand...which is an oxymoron!

Thanks!

Alvaro.

From: Acee Lindem [mailto:[e-mail]]
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-autoconfig-02.txt

Speaking as a Draft Author:

This version includes additions based on comments received at IETF 83. Section 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 same 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 resolution.

Additionally, we received a suggestion from Alvaro Retana to not use an reserved OSPFv3 instance ID for auto-configured routers. Rather, allow OSPFv3 auto-configured routers to use the default OSPFv3 instance ID and automatically join an existing non-autoconfigured OSPFv3 routing domain. I see three possible alternatives:

    1. Reject the suggestion. The alternate OSPFv3 instance ID was added specifically to prevent this.
    2. Adopt the suggestion and remove the reserved instance ID. The security 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: "[e-mail]<mailto:[e-mail]>" <[e-mail]<mailto:[e-mail]>>
Date: May 28, 2012 3:41:15 PM EDT
To: Acee Lindem <[e-mail]<mailto:[e-mail]>>
Cc: "[e-mail]<mailto:[e-mail]>" <[e-mail]<mailto:[e-mail]>>
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 successfully 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