So in most cases I'm aware of, the cable provider did not use RIP directly
to a customer-managed device.  The cable operator would deploy their own
managed device, implement RIP and the appropriate keychains between the
operator-managed premise device and the CMTS.  As for the use cases, RIP was
implemented to address the specific 'recombine' use case where one day (or
evening) cable customer attachments could be moved from one CMTS to another.
Instrumenting that with DHCP or TR69 usually required other teams'
involvement and didn't allow portability.

With IPv6 you get PD which helps immensely.

Ed

-----Original Message-----
From: NANOG <nanog-bounces@nanog.org> On Behalf Of Javier Gutierrez Guerra
Sent: Friday, May 8, 2020 8:57 AM
To: NANOG list <nanog@nanog.org>
Subject: RE: How to manage Static IPs to customers

That's surprising to me, I have no intentions to do routing with our cable
subscribers, that seems like a headache for both sides Today we have
specific ranges within subnets from where we assign IPs to customers, my
main problem that I'm trying to get around is having to change a customer
static IP if their node gets splitter and I have to mode them to a different
CMTS

Thanks,

Javier Gutierrez Guerra
            


-----Original Message-----
From: NANOG <nanog-bounces@nanog.org> On Behalf Of Bryan Fields
Sent: Thursday, May 7, 2020 5:57 PM
To: nanog@nanog.org
Subject: Re: How to manage Static IPs to customers

CAUTION: This email is from an external source. Do not click links or open
attachments unless you recognize the sender and know the content is safe.

On 5/7/20 5:54 PM, Brandon Jackson via NANOG wrote:
> I have seen (Charter) and heard quite a few run RIP or some other
> routing protocol on the CPE.

Yep, it's RIP.  They don't support IPv6 on this either.  I've been asking
for
IPv6 since 2006, it's always next year.

--
Bryan Fields

727-409-1194 - Voice
http://bryanfields.net