[homenet] Alia Atlas' No Objection on draft-ietf-homenet-prefix-assignment-07: (with COMMENT)

"Alia Atlas" <akatlas@gmail.com> Wed, 08 July 2015 22:06 UTC

Return-Path: <akatlas@gmail.com>
X-Original-To: homenet@ietfa.amsl.com
Delivered-To: homenet@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 7ED6B1A889D; Wed, 8 Jul 2015 15:06:09 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -101.898
X-Spam-Level:
X-Spam-Status: No, score=-101.898 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_ADSP_CUSTOM_MED=0.001, FREEMAIL_FROM=0.001, USER_IN_WHITELIST=-100] 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 lENWbMvWi7jY; Wed, 8 Jul 2015 15:06:08 -0700 (PDT)
Received: from ietfa.amsl.com (localhost [IPv6:::1]) by ietfa.amsl.com (Postfix) with ESMTP id 125581A888B; Wed, 8 Jul 2015 15:06:08 -0700 (PDT)
MIME-Version: 1.0
Content-Type: text/plain; charset="utf-8"
Content-Transfer-Encoding: 7bit
From: Alia Atlas <akatlas@gmail.com>
To: The IESG <iesg@ietf.org>
X-Test-IDTracker: no
X-IETF-IDTracker: 6.0.4.p2
Auto-Submitted: auto-generated
Precedence: bulk
Message-ID: <20150708220608.28131.99425.idtracker@ietfa.amsl.com>
Date: Wed, 08 Jul 2015 15:06:08 -0700
Archived-At: <http://mailarchive.ietf.org/arch/msg/homenet/a1WtyBUZbtH5syO61gDywblp0Q4>
Cc: homenet@ietf.org, Mark Townsley <mark@townsley.net>, ray@bellis.me.uk
Subject: [homenet] Alia Atlas' No Objection on draft-ietf-homenet-prefix-assignment-07: (with COMMENT)
X-BeenThere: homenet@ietf.org
X-Mailman-Version: 2.1.15
List-Id: IETF Homenet WG mailing list <homenet.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/homenet>, <mailto:homenet-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/homenet/>
List-Post: <mailto:homenet@ietf.org>
List-Help: <mailto:homenet-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/homenet>, <mailto:homenet-request@ietf.org?subject=subscribe>
X-List-Received-Date: Wed, 08 Jul 2015 22:06:09 -0000

Alia Atlas has entered the following ballot position for
draft-ietf-homenet-prefix-assignment-07: No Objection

When responding, please keep the subject line intact and reply to all
email addresses included in the To and CC lines. (Feel free to cut this
introductory paragraph, however.)


Please refer to https://www.ietf.org/iesg/statement/discuss-criteria.html
for more information about IESG DISCUSS and COMMENT positions.


The document, along with other ballot positions, can be found here:
https://datatracker.ietf.org/doc/draft-ietf-homenet-prefix-assignment/



----------------------------------------------------------------------
COMMENT:
----------------------------------------------------------------------

I agree with Alvaro and Brian on the need to clarify topology changes. 
In Sec 3, I see
"   The algorithm supports dynamically changing topologies:

   o  Nodes may join or leave the set of participating Nodes.

   o  Nodes may join or leave Links.

   o  Links may be joined or split."

and what isn't clearly stated is that when a link fails (partially or
fully) or comes into existence ,
is that a topology change?

For instance, if a link fails, surely that shouldn't be a topology change
for the prefix assignment,
but rather a matter for routing to handle.  I do see in Sec 4.3 "When a
Link is removed, all Assigned Prefixes
assigned to that Link MUST be destroyed."  Perhaps a link removal isn't
considered a topology change in this
context because it doesn't cause renumbering??

How is a new Link added to be considered?  How does a router know that
its end of a link is the
same link as on another router?  How is a link "removed" versus merely
down?

An assumption seems to be that the flooding mechanism can work without
any prefix numbering.  That's fine but
would be good to state.  I'm a bit twitchy about the bootstrapping.