[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
RE: CPE router acting as host on its WAN interface (RE: draft-ietf-v6ops-ipv6-cpe-router-03.txt WGLC)
>-----Original Message-----
>From: STARK, BARBARA H (ATTLABS) [mailto:bs7652@att.com]
>Sent: Wednesday, January 06, 2010 8:09 PM
>To: Templin, Fred L; Hemant Singh (shemant); Fred Baker (fred);
v6ops@ops.ietf.org
>Cc: kurtis@kurtis.pp.se; rbonica@juniper.net
>Subject: RE: CPE router acting as host on its WAN interface (RE:
draft-ietf-v6ops-ipv6-cpe-router-03.txt WGLC)
>Telcos will create the SP Router standards in the BBF, more than
likely.
>I wouldn't be surprised if CableLabs did standards for the cable
>companies, but I have no direct knowledge of that.
That is correct. CableLabs has defined the standards for the IPv6 Cable
Router in their network with no mention of the IsRouter flag.
>My guess is that the BBF standards won't even mention the IsRouter
flag. There will be no NS
>or RS messages sent to CE routers (or hosts).
Hmm, why won't a SP Rtr send an NS to the CE Rtr? For one, the SP Rtr
can send an NS to resolve the link-local or global of the WAN interface
of the CE Rtr.
>So there will be no solicited NA or RA messages coming from the CE
routers.
The CE Rtr can send an NA in response to the NS I mentioned above.
Hemant