RE: draft-wbeebee-ipv6-cpe-router-04 comments

["Hemant Singh (shemant)" <shemant@cisco.com>]

Ralph,

Note the our draft covers both an embedded CPE Rtr and a standalone CPE
Rtr.  If the CPE Rtr is embedded in a cable or DSL modem, or 3GPP legacy
data device, then the L2 of the modem or 3GPP device can easily signal
the upper layers of the Rtr to be configured for cable, DSL, or 3GPP WAN
interface setup. 

For a standalone CPE Rtr, if one reads the draft, one will see that if
the CPE Rtr WAN interface sees an RA with M and O bits set when no PPP
link has been established prior to seeing this RA, it's a cable
deployment.  If an RA is seen after PPP negotiation, it's a DSL
deployment.  These are some ideas we have in mind thus far.  We can
certainly look into a flow chart for such provisioning in the standalone
rtr case.  Alternatively, for the standalone case, we may leave it to
the vendors to differentiate between their products as to how automatic
is their standalone CPE Rtr provisioning.  

Hemant

-----Original Message-----
From: owner-v6ops@ops.ietf.org [mailto:owner-v6ops@ops.ietf.org] On
Behalf Of Ralph Droms (rdroms)
Sent: Tuesday, March 24, 2009 10:57 AM
To: IPv6 Operations
Cc: Fred Baker (fred); james woodyatt
Subject: Re: draft-wbeebee-ipv6-cpe-router-04 comments

And there needs to be a way in which the CPE router can determine what  
mode it is supposed to operate in ... no matter whether it is  
connected directly to a WAN link (cable or DSL or IPoSN) or to a link  
inside the subscriber network.

- Ralph