Hi,

A few somewhat random comments:

Everywhere you refer to "small" and "smaller" prefixes.
This is confusing. I assume you mean "long" and "longer".

> 4.1.  Data structures
...
>    Router ID:  The identifier of the advertising router.

Who assigns this? I think you mention that later but here
it's just a dangling reference.

> 
>    Link ID:  If the assignment is made on a connected link, an interface
>          identifier of the interface connected to that link.

That's a bit confusing because a link is not an interface, and the same
link connected to multiple interfaces will have multiple Link IDs
by this definition. Also, you can't call it Interface ID because that
has a specific meaning in IPv6. I don't have a good suggestion but
it needs to be tidied up IMHO.

> 4.2.  Routers' Interfaces
> 
>    Each interface MUST either be considered as internal or external.
>    Prefixes and addresses are only assigned to internal interfaces.  The
>    criteria to make this distinction are out of the scope of this
>    document.

By "criteria" do you mean mechanisms? That seems to be a discovery
problem (and it also occurs during security bootstrapping). But
I think you really need to define what internal and external *means*.
The words are not self-defining.

>    If an internal interface becomes external, all prefixes and addresses
>    assigned on the considered interface MUST be deleted...

Yes but... they can't be dropped instantly; at least for v6 they have
to go through the deprecation phase, surely?

...
>    Whenever two or more interfaces are connected to the same link,

How is this known to be the case? I imagine a little TV camera
peeping out from the router to look at the cables...

> 4.5.  Designated Router
> 
>    On a link where custom host configuration must be provided, or
>    whenever SLAAC cannot be used, a DHCP server must be elected.  That
>    router is called designated router and is dynamically chosen by the
>    prefix assignment algorithm.

You are assuming without stating it that the DHCP server MUST be located
in the same device as a router. Why?

Is the designated router the same one for v4 and v6, and if so, why?

> 4.5.1.  Sending Router Advertisement
> 
...
>    The designated router MUST advertise itself as a router for all IPv6
>    delegated prefixes using Route Information Options [RFC4191],
>    independently of whether there is a default route or not.

Why? Maybe different MIF PVDs should be handled by different routers,
if some form of SADR is supported.

> 6.6.  Making a New Assignment
...
>    When the algorithm decides to make a new assignment, it first needs
>    to specify the desired size of the assigned prefix.  Although this
>    algorithm intends to remain generic, the use of 64 bits long prefixes
>    is RECOMMENDED (See [I-D.ietf-6man-why64]).

And for v4?

> 6.10.  Downstream DHCPv6 Prefix Delegation support
...

>                             If DHCPv6 Reconfigure is
>    not supported, leases lifetimes SHOULD be significantly small.

Can't parse "significantly". Can you quantify this?

> 9.1.1.  Choosing the ULA prefix
> 
>    When a stable ULA prefix is advertised, all routers SHOULD remember
>    that prefix alongwith its associated valid and preferred lifetime.
>    If this prefix stops being advertised (e.g. due to a network split)
>    while its preferred lifetime is not null, the same ULA prefix SHOULD
>    be selected using the same valid and preferred lifetimes.

What is doing the selecting? This is a case where the passive tense is
confusing.

> 9.1.2.  Advertising a ULA prefix
> 
>    A router MAY start advertising a ULA prefix whenever the two
>    following conditions are met:
> 
>    o  It is the network leader.
> 
>    o  There is no other advertised ULA prefix.
> 
>    If no IPv6 prefix is available at all, the network leader SHOULD
>    start advertising a ULA delegated prefix.

Do these two bullets refer to the same thing (a complete ULA /48) or
to longer ULA prefixes?

> 
>    Additionaly, a router SHOULD start advertising its own ULA prefix
>    whenever the three following conditions are met:
> 
>    o  A stable ULA prefix is advertised by another router.
> 
>    o  The router owns the advertised stable ULA prefix.

I got confused about which router is which. Could you give
them names, e.g.

    Additionaly, a router "A" SHOULD start advertising its own ULA prefix
    whenever the three following conditions are met:

    o  A stable ULA prefix is advertised by another router "B".

    o  The router "A" owns the advertised stable ULA prefix.

And then it still doesn't make sense to me (and again I'm asking
whether we are talking about a /48 or something longer).

>    A router MUST stop advertising a spontaenously generated ULA prefix
>    whenever one of the two following condition is met:
> 
>    o  A different ULA prefix is being advertised.
> 
>    o  The same prefix is advertised by another router, and the router
>       doesn't own that prefix.

Here too I am confused about which router is which and which prefix
length is involved.

That's it for now.

    Brian

_______________________________________________
homenet mailing list
homenet@ietf.org
https://www.ietf.org/mailman/listinfo/homenet

Reply via email to