Quite an interesting discussion. I would like to some of my experience in the hope some of the issues that I have seen may be fixed if any upgrades are made on the Chorus equipment. As far as I understand the EUBA products only support 802.1p 6 and 802.1p 0. "It is the responsibility of the Service Provider or End User to ensure traffic is tagged with the appropriate priority setting. Untagged or incorrectly tagged traffic will be discarded." (This differs from NGA that supports 802.1p 5 and 802.1p 0 but will remark anything else to 802.1p 0 rather than discard.) It has been a while since I looked by as far as I recall I found that Cisco sends some IPv6 ND packets marked with something other than 802.1p 6 or 802.1p 0 - I think possibly 802.1p 7 but could have been 802.1p 5. This broke IPv6 for us (using 0/110 PVC with VLAN 10 - Ethernet bridge). Cisco does not support the remarking or even setting of the default 802.1p values used, and the last response I had from Chorus was "EUBA is unable to support IPv6, reason is because the Alcatel equipment deployed for this network doesn’t support IPv6". Also of interest Chorus advised "The NGA services do not officially support IPv6, but we do know the equipment used is capable of supporting IPv6 and the feature is turned on in our network." I would be happy if somewhere along the line, EUBA changed its behavior to remarking unsupported 802.1p values rather than discarding the packets as this would help with IPv6. :-) Thanks Ivan On 27/01/2015 10:58 a.m., Brent Marquis wrote:

Yes Scott,

That is correct. The 0/110 PVC (with VLAN 10) is an Ethernet bridge and does not perform PPPoA->PPPoE (and vice versa for downstream) conversion - so shouldn’t be experiencing this issue. If you are using PPP on the 0/110 PVC, then it works out to be PPPoEoA and the ISAM strips the ATM header - rather than straight PPPoA with the ISAM interworking function to convert to PPPoE, which is what occurs on the 0/100 PVC.

Thanks, Brent

-----Original Message----- From: Scott Pettit [mailto:SPettit(a)end2end.co.nz] Sent: Tuesday, 27 January 2015 10:47 a.m. To: Brent Marquis; Simon Allard Cc: NZNOG Subject: Re: [nznog] Chorus EUBA + IPV6

On 26/01/15 21:37, "Brent Marquis" wrote:

...

...

Only affect PPPoE->PPPoA translation This also means that IPv6 over VDSL (PTM) should be fine.

...

From: nznog-bounces(a)list.waikato.ac.nz [mailto:nznog-bounces(a)list.waikato.ac.nz] On Behalf Of Simon Allard To summarise: IPV6 doesn’t work on Chorus EUBA on some line card types Only affect PPPoE->PPPoA translation PPPoE end to end is fine. Chorus say IPV6 not supported on EUBA Customer numbers effected are smallish.

Just to clarify, if a customer uses PVC 0/110 (Ethernet), there is no issue, right? We have lots of sites on EUBA using 0/110 and haven’t had any problems with IPv6, ditto for WVS.

-Scott --

[https://s3-ap-southeast-2.amazonaws.com/e2emailsig/unnamed.png]

Scott Pettit | Director +64 9 9502222 | SPettit(a)end2end.co.nz

End 2 End Limited +64 9 9502220 205/100 Parnell Road, Parnell, Auckland 1052, New Zealand http://www.end2end.co.nz

The content of this message and any attachments may be privileged, confidential or sensitive and is intended only for the use of the intended recipient(s). Any unauthorised used is prohibited. Views expressed in this message are those of the individual sender, except where stated otherwise with appropriate authority. All pricing provided is valid at the time of writing only and due to factors such as the exchange rate, may change without notice. Sales are made subject to our Terms & Conditions, available on our website or on request. This communication, including any attachments, is confidential and may be legally privileged. If you are not the intended recipient, you should not read it - please contact me immediately, destroy it, and do not copy or use any part of this communication or disclose anything about it. Thank you. No confidentiality or privilege is waived or lost by any mis-transmission or error. Please note that this communication does not designate an information system for the purposes of the Electronic Transactions Act 2002.

_______________________________________________ NZNOG mailing list NZNOG(a)list.waikato.ac.nz http://list.waikato.ac.nz/mailman/listinfo/nznog

Thanks Brent. I had pretty much accepted the processes around the EUBA changes. I am hopeful these is not too much demand from Chorus customers for the current way things work so at some stage it could be modified. (I don't suspect the existing setup is from customer demand but more likely some technical limitations.) Cheers Ivan On 27/01/2015 1:22 p.m., Brent Marquis wrote:

Hi Ivan,

In my opinion, the first statement about the equipment from us is wrong (not withstanding the issue that started this thread). The second statement about the feature being 'on' for NGA is correct (with 'the feature' being circuit and port ID insertion for v6)

In saying that - for EUBA behaviour to change, it is a fundamental change to the EUBA service description, which has industry processes around it...

Thanks, Brent

-----Original Message----- From: Ivan Walker [mailto:nznog(a)itpro.co.nz] Sent: Tuesday, 27 January 2015 1:08 p.m. To: nznog(a)list.waikato.ac.nz; Brent Marquis Subject: Re: [nznog] Chorus EUBA + IPV6

Quite an interesting discussion. I would like to some of my experience in the hope some of the issues that I have seen may be fixed if any upgrades are made on the Chorus equipment.

As far as I understand the EUBA products only support 802.1p 6 and 802.1p 0. "It is the responsibility of the Service Provider or End User to ensure traffic is tagged with the appropriate priority setting. Untagged or incorrectly tagged traffic will be discarded." (This differs from NGA that supports 802.1p 5 and 802.1p 0 but will remark anything else to 802.1p 0 rather than discard.)

It has been a while since I looked by as far as I recall I found that Cisco sends some IPv6 ND packets marked with something other than 802.1p 6 or 802.1p 0 - I think possibly 802.1p 7 but could have been 802.1p 5. This broke IPv6 for us (using 0/110 PVC with VLAN 10 - Ethernet bridge).

Cisco does not support the remarking or even setting of the default 802.1p values used, and the last response I had from Chorus was "EUBA is unable to support IPv6, reason is because the Alcatel equipment deployed for this network doesn’t support IPv6".

Also of interest Chorus advised "The NGA services do not officially support IPv6, but we do know the equipment used is capable of supporting IPv6 and the feature is turned on in our network."

I would be happy if somewhere along the line, EUBA changed its behavior to remarking unsupported 802.1p values rather than discarding the packets as this would help with IPv6. :-)

Thanks

Ivan

On 27/01/2015 10:58 a.m., Brent Marquis wrote:

...

Yes Scott,

That is correct. The 0/110 PVC (with VLAN 10) is an Ethernet bridge and does not perform PPPoA->PPPoE (and vice versa for downstream) conversion - so shouldn’t be experiencing this issue. If you are using PPP on the 0/110 PVC, then it works out to be PPPoEoA and the ISAM strips the ATM header - rather than straight PPPoA with the ISAM interworking function to convert to PPPoE, which is what occurs on the 0/100 PVC.

Thanks, Brent

-----Original Message----- From: Scott Pettit [mailto:SPettit(a)end2end.co.nz] Sent: Tuesday, 27 January 2015 10:47 a.m. To: Brent Marquis; Simon Allard Cc: NZNOG Subject: Re: [nznog] Chorus EUBA + IPV6

On 26/01/15 21:37, "Brent Marquis" wrote:

...

...

Only affect PPPoE->PPPoA translation This also means that IPv6 over VDSL (PTM) should be fine. From: nznog-bounces(a)list.waikato.ac.nz [mailto:nznog-bounces(a)list.waikato.ac.nz] On Behalf Of Simon Allard To summarise: IPV6 doesn’t work on Chorus EUBA on some line card types Only affect PPPoE->PPPoA translation PPPoE end to end is fine. Chorus say IPV6 not supported on EUBA Customer numbers effected are smallish. Just to clarify, if a customer uses PVC 0/110 (Ethernet), there is no issue, right? We have lots of sites on EUBA using 0/110 and haven’t had any problems with IPv6, ditto for WVS.

-Scott --

[https://s3-ap-southeast-2.amazonaws.com/e2emailsig/unnamed.png]

Scott Pettit | Director +64 9 9502222 | SPettit(a)end2end.co.nz

End 2 End Limited +64 9 9502220 205/100 Parnell Road, Parnell, Auckland 1052, New Zealand http://www.end2end.co.nz

The content of this message and any attachments may be privileged, confidential or sensitive and is intended only for the use of the intended recipient(s). Any unauthorised used is prohibited. Views expressed in this message are those of the individual sender, except where stated otherwise with appropriate authority. All pricing provided is valid at the time of writing only and due to factors such as the exchange rate, may change without notice. Sales are made subject to our Terms & Conditions, available on our website or on request. This communication, including any attachments, is confidential and may be legally privileged. If you are not the intended recipient, you should not read it - please contact me immediately, destroy it, and do not copy or use any part of this communication or disclose anything about it. Thank you. No confidentiality or privilege is waived or lost by any mis-transmission or error. Please note that this communication does not designate an information system for the purposes of the Electronic Transactions Act 2002.

_______________________________________________ NZNOG mailing list NZNOG(a)list.waikato.ac.nz http://list.waikato.ac.nz/mailman/listinfo/nznog