Re: I-D Action:draft-wbeebee-ipv6-cpe-router-00.txt

[Brian E Carpenter <brian.e.carpenter@gmail.com>]

Hi, some comments on other points.

> 5.3.  Acquire IPv6 address and other configuration parameters

I suggest that if address acquistion by DHCPv6 fails, there
should be a (configurable) option to discover a 6to4
relay. CPE routers were in fact a target when 6to4 was designed.
It only needs a few lines and a reference to RFC 3056 and 3068.

Also I suggest that there should be a configurable option
to generate and support a ULA prefix. Again, a few lines
and a reference to RFC 4193.

> 6.  IPv6 Data forwarding
...
>                                       Each protocol that the CPE
>    Router can forward packets for must have a separate routing table.

I've read that sentence several times and can't understand it. Do you
simply mean that the IPv6 table is separate from IPv4?

...
>                         Before forwarding a packet
>    in any direction from CPE router, the CPE Router will perform a MAC
>    rewrite operation that rewrites the source L2 address of the packet
>    with CPE Router's WAN or LAN interface MAC address.  

I also don't understand that sentence. Surely a router moves an L3
packet from one L2 interface to another, and removing and creating
L2 headers is nothing to do with routing as such?

> 7.1.  Path MTU Discovery Support
> 
>    GRE tunnels, such as 6-to-4 tunnels (which may be terminated on the
>    CPE Router),

This is confusing. 6to4 (no hyphens) refers to RFC 3056 and has nothing
to do with GRE. In fact any kind of Protocol 41 tunnel can interfere
with MTU too - do you expect a typical CPE to support generic Protocol 41
tunnels? I think that by '6-to-4' you probably mean "IPv6 in IPv4"?

> 8.  Quality Of Service(QoS)
> 
>    The CPE router may map the IPv6 Traffic Class field from [RFC2460] to
>    individual queues of different priority to provide differentiated
>    classes of service for traffic either destined to the LAN or WAN
>    interfaces (e.g. for IPTV service).

You shouldn't use the word 'priority' because the diffserv model is
not about priority. Better to use 'behavior' plus a reference to
RFC 2474. In fact, the whole thing can be expressed as

  The CPE router MAY support differentiated services [RFC2474].

     Brian