B. R.
Tina
http://tinatsou.weebly.com




On Sep 10, 2010, at 11:52 AM, Maglione Roberta wrote:

PPP is not used here. There are numerous different deployment models, PPP is an expensive one that should be avoided unless there is serious use for
it.

While it is true that PPP is not used here, I won't say that PPP should be avoided. PPP is a valid and widely deployed model in DSL Broadband environment; Broadband Forum has already published TR-187 that explains how to deploy IPv6 with PPP.

In addition in case of bridged Layer 2 RG model, PPP + SLAAC with the /64 announced in the RA PIO is a valid solution.

Best Regards,
Roberta

-----Original Message-----
From: [email protected] [mailto:[email protected]] On Behalf Of Mikael Abrahamsson
Sent: giovedì 9 settembre 2010 17.10
To: Mark Smith
Cc: [email protected]; Fred Baker
Subject: Re: New version available

On Thu, 9 Sep 2010, Mark Smith wrote:

I don't know about other vendors, however Cisco have a model of SLAAC
address assignment where a single /64 is used for address assignment to
PPP sessions, with the /64 announced in the RA PIO. In effect the PPP
connections become part of a NBMA point to multipoint topology. RADIUS reports this assignment (as it will with individual /64s per PPP session
too from within a pool).

PPP is not used here. There are numerous different deployment models, PPP is an expensive one that should be avoided unless there is serious use for
it.
Some operators have serious use for PPPoE in large scale. It is a tradeoff for them to decide whether it is expensive or not from the whole picture point of view.

It's when you want to share a subnet with multiple DHCPv6(-PD)- handouted IP addresses and routed subnets it becomes a bit more complicated. That
situation is what I was referring to.

I'm not really sure I understand the scenario you're describing. I'm
having no trouble with RA + SLAAC + DHCPv6-PD, static and dynamic
assignments of /64 for PPP session and delegated prefixes via
DHCPv6-PD.

ETTH doesn't include PPP for me. Tunneling is expensive.

--
Mikael Abrahamsson    email: [email protected]
--------------------------------------------------------------------
IETF IPv6 working group mailing list
[email protected]
Administrative Requests: https://www.ietf.org/mailman/listinfo/ipv6
--------------------------------------------------------------------

Questo messaggio e i suoi allegati sono indirizzati esclusivamente alle persone indicate. La diffusione, copia o qualsiasi altra azione derivante dalla conoscenza di queste informazioni sono rigorosamente vietate. Qualora abbiate ricevuto questo documento per errore siete cortesemente pregati di darne immediata comunicazione al mittente e di provvedere alla sua distruzione, Grazie.

This e-mail and any attachments is confidential and may contain privileged information intended for the addressee(s) only. Dissemination, copying, printing or use by anybody else is unauthorised. If you are not the intended recipient, please delete this message and any attachments and advise the sender by return e- mail, Thanks.

--------------------------------------------------------------------
IETF IPv6 working group mailing list
[email protected]
Administrative Requests: https://www.ietf.org/mailman/listinfo/ipv6
--------------------------------------------------------------------

--------------------------------------------------------------------
IETF IPv6 working group mailing list
[email protected]
Administrative Requests: https://www.ietf.org/mailman/listinfo/ipv6
--------------------------------------------------------------------

Reply via email to