Re: [v6ops] I-D Action: draft-ietf-v6ops-6204bis-03.txt

I was referring to the Broadband scenario, not to the 3GPP world.

Roberta

-----Original Message-----
From: Frank Bulk [mailto:frnkblk@iname.com]
Sent: domenica 4 dicembre 2011 4.35
To: Maglione Roberta
Cc: v6ops@ietf.org
Subject: RE: [v6ops] I-D Action: draft-ietf-v6ops-6204bis-03.txt

Roberta:

Why is this an issue for BNG's in the 3GPP world and not elsewhere?

Frank

-----Original Message-----
From: v6ops-bounces@ietf.org [mailto:v6ops-bounces@ietf.org] On Behalf Of
Maglione Roberta
Sent: Wednesday, November 30, 2011 7:16 PM
To: sarikaya@ieee.org
Cc: v6ops@ietf.org
Subject: Re: [v6ops] I-D Action: draft-ietf-v6ops-6204bis-03.txt

Yes you can install the aggregate route but you would need either another
dhc option that tells the BNG what aggregate route needs to be installed per
each customer or you have to do by manual configuration.

In my opinion using PD-exclude is operational much simpler

Roberta
________________________________________
From: Behcet Sarikaya [sarikaya2012@gmail.com]
Sent: Thursday, December 01, 2011 1:17 AM
To: Maglione Roberta
Cc: Lorenzo Colitti; v6ops@ietf.org
Subject: Re: [v6ops] I-D Action: draft-ietf-v6ops-6204bis-03.txt

Roberta,

I don't see that a problem either because usually you can install an
aggregate route.

Regards,

Behcet

On Wed, Nov 30, 2011 at 5:26 PM, Maglione Roberta
<roberta.maglione@telecomitalia.it<mailto:roberta.maglione@telecomitalia.it>
> wrote:
Behcet,
  the reason why you may need to have a single prefix instead of two per
customer is in order to have just a single route to install on the BNG
instead of two.

Regards
Roberta
________________________________________
From: Behcet Sarikaya
[sarikaya2012@gmail.com<mailto:sarikaya2012@gmail.com>]
Sent: Thursday, December 01, 2011 12:22 AM
To: Maglione Roberta
Cc: Lorenzo Colitti; v6ops@ietf.org<mailto:v6ops@ietf.org>
Subject: Re: [v6ops] I-D Action: draft-ietf-v6ops-6204bis-03.txt

Hi Roberta,

You don't need to restrict yourself to the use of a single prefix in IPv6.
Usually DR can allocate many prefixes to the RR.

Besides these prefixes are used for some time and then not needed any more.
I don't see any reason to be so frugal.

Regards,

Behcet

On Wed, Nov 30, 2011 at 1:31 PM, Maglione Roberta
<roberta.maglione@telecomitalia.it<mailto:roberta.maglione@telecomitalia.it>
<mailto:roberta.maglione@telecomitalia.it<mailto:roberta.maglione@telecomita
lia.it>>> wrote:
> If you're not using the /64 to number the link between the BNG and the CE,
then you can make the link unnumbered and you don't need to exclude
> anything.

You could make the link unnumbered, but the WAN link could also be numbered.
If you refer to BBF TR-187, TR-177, TR-124i2  you can see that both
unnumbered and numbered  are considered valid scenarios.
PD-exclude is need in order to build the WAN numbered scenario with a single
prefix.

Roberta

________________________________________
From: Lorenzo Colitti
[lorenzo@google.com<mailto:lorenzo@google.com><mailto:lorenzo@google.com<mai
lto:lorenzo@google.com>>]
Sent: Wednesday, November 30, 2011 8:24 PM
To: Maglione Roberta
Cc: jouni korhonen;
v6ops@ietf.org<mailto:v6ops@ietf.org><mailto:v6ops@ietf.org<mailto:v6ops@iet
f.org>>
Subject: Re: [v6ops] I-D Action: draft-ietf-v6ops-6204bis-03.txt

On Thu, Dec 1, 2011 at 04:12, Maglione Roberta
<roberta.maglione@telecomitalia.it<mailto:roberta.maglione@telecomitalia.it>
<mailto:roberta.maglione@telecomitalia.it<mailto:roberta.maglione@telecomita
lia.it>><mailto:roberta.maglione@telecomitalia.it<mailto:roberta.maglione@te
lecomitalia.it><mailto:roberta.maglione@telecomitalia.it<mailto:roberta.magl
ione@telecomitalia.it>>>> wrote:
PD-exclude allows to delegate a single prefix to the home network and than
use the PD-exclude option to tell the CPE to exclude a portion of the
delegated prefix and use it to number the point to point WAN link between
the requesting router (CPE) and the delegated router (BNG)

I still don't see why this is needed.

If you're using the /64 to number the link between the BNG and the CE
router, then the CE router already knows that the /64 is assigned to that
link via the O bit in the prefix information option in the RA.

If you're not using the /64 to number the link between the BNG and the CE,
then you can make the link unnumbered and you don't need to exclude
anything.

So...?

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.

_______________________________________________
v6ops mailing list
v6ops@ietf.org<mailto:v6ops@ietf.org><mailto:v6ops@ietf.org<mailto:v6ops@iet
f.org>>
https://www.ietf.org/mailman/listinfo/v6ops

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.

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.

_______________________________________________
v6ops mailing list
v6ops@ietf.org
https://www.ietf.org/mailman/listinfo/v6ops

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.