Playstation Vue over IPv6 from Frontier Tampa Bay, FL

2018-03-08 Thread Clay Curtis
Playstation Vue is basically unusable when viewing over IPv6 from Tampa Bay
Frontier network. A little background first...

Almost all traffic from my metro area (Tampa Bay, FL) routes to Miami
first, and then continues on to the IPv4 Internet. Frontier does not have
residential IPv6 yet, so I am tunneling to the Hurricane Electric Miami POP
to get IPv6 connectivity. Point being, the tunneling does not really have
an adverse affect on latency.

That said, IPv4 streaming is great because I head down to Miami and jump
right over to Akamai for the content.

  1 4 ms 5 ms 5 ms  192.168.4.1
  2 *   18 ms 6 ms  192.168.100.1
  3 8 ms 6 ms 6 ms  47.199.160.1
  4 8 ms 9 ms 7 ms  172.99.45.80
  512 ms13 ms13 ms  ae8---0.scr02.mias.fl.frontiernet.net
[74.40.3.73]
  613 ms13 ms13 ms  ae1---0.cbr01.mias.fl.frontiernet.net
[74.40.1.126]
  712 ms12 ms12 ms  lag-101.ear3.Miami2.Level3.net [4.15.156.29]
  813 ms13 ms13 ms  NTT-level3-80G.Miami.Level3.net
[4.68.127.54]
  914 ms13 ms13 ms  ae-4.r05.miamfl02.us.bb.gin.ntt.net
[129.250.3.40]
 1014 ms14 ms14 ms  a204-2-178-194.deploy.akamaitechnologies.com
[204.2.178.194]

IPv6 on the other hand, goes down to Miami, up to Ashburn, and back to
Miami.

1   clay584-1.tunnel.tserv12.mia1.ipv6.he.net
(2001:470:4:4e5::1)17.460   ms  17.231  ms  16.867   ms
2   10ge13-20.core1.mia1.he.net
(2001:470:0:8c::1) 13.187   ms  13.446  ms  13.143   ms
3   100ge11-1.core1.atl1.he.net
(2001:470:0:18d::1)27.223   ms  31.532  ms  27.294   ms
4   100ge8-1.core1.ash1.he.net
   (2001:470:0:114::2)45.364   ms  39.037  ms  38.893   ms
5   xe-0.equinix.asbnva01.us.bb.gin.ntt.net
(2001:504:0:2::2914:1) 39.565   ms  39.485  ms  39.870   ms
6   ae-2.r23.asbnva02.us.bb.gin.ntt.net
(2001:418:0:2000::115) 39.356   ms  39.249  ms  42.904   ms
7   ae-1.r20.miamfl02.us.bb.gin.ntt.net
(2001:418:0:2000::f2)  64.380   ms  65.897  ms  64.124   ms
8   ae-1.r05.miamfl02.us.bb.gin.ntt.net
(2001:418:0:2000::26a) 65.341   ms  65.324  ms  65.114   ms
9   ae-8.a00.miamfl02.us.bb.gin.ntt.net
(2001:418:0:2000::166) 68.843   ms  68.839  ms  69.295   ms
10  2001:418:0:5000::929
   (2001:418:0:5000::929) 135.368  ms  84.350  ms  219.402  ms
11
g2600-1403-0015----48f7-f02b.deploy.static.akamaitechnologies.com
(2600:1403:15::48f7:f02b)  68.629   ms  65.356  ms  65.352   ms


>From what I can see it looks that Hurricane Electric only sees this prefix
from Equinix and thus routes it up to Ashburn and back. I suppose there
could be utilization issues along the path, but the path itself seems like
it could be better and may improve streaming with PS Vue. Going halfway up
the east coast just to come back to the same city (possibly the same
facility) is not ideal.

Is there anyone on list that can see if this can be improved?

Thanks in advance,

Clay


2nd call for presentations RIPE 76

2018-03-08 Thread Benno Overeinder
Dear colleagues,

Please note the approaching deadline of *11 March 2018* for RIPE 76
plenary programme submissions.

You can find the CFP for RIPE 76 below or at
https://ripe76.ripe.net/submit-topic/cfp/, for your proposals for
plenary session presentations, tutorials, workshops, BoFs (Birds of a
Feather sessions) and lightning talks.

Please also note that speakers do not receive any extra reduction or
funding towards the meeting fee at the RIPE Meetings, see the "Speakers"
paragraph in CFP for more information.

Kind regards,

Benno Overeinder
RIPE PC Chair
https://ripe76.ripe.net/ripe-pc/


>>><<<

Call for Presentations

A RIPE Meeting is an open event where Internet Service Providers,
network operators and other interested parties get together.  Although
the meeting is mostly technical, it is also a chance for people to meet
and network with others in their field.

RIPE 76 will take place from 14-18 May in Marseille, France.

The RIPE Programme Committee (PC) is now seeking content proposals from
the RIPE community for the plenary sessions, BoFs (Birds of a Feather
sessions), panels, workshops, tutorials and lightning talks at RIPE 76.
See the full descriptions of the different presentation formats,
https://ripe76.ripe.net/submit-topic/presentation-formats/.

Proposals for plenary sessions, BoFs, panels, workshops and tutorials
must be submitted for full consideration no later than *11 March 2018*.
Proposals submitted after this date will be considered depending on the
remaining available space in the programme.

The PC is looking for presentations covering topics of network
engineering and operations, including but not limited to:

- IPv6 deployment
- Managing IPv4 scarcity
- Data centre technologies
- Network and DNS operations
- Internet governance and regulatory practices
- Network and routing security
- Content delivery
- Internet peering and mobile data exchange
- Connected Things (aka. Internet of Things - IoT)

Speakers

Presenters, RIPE Working Group Chairs and the RIPE Programme Committee
are required to cover their own costs to attend a RIPE Meeting (meeting
ticket, travel and accommodation).  We have various ticket options
available depending on your needs.

In extraordinary circumstances, the RIPE Chair can waive the meeting fee
for presenters.  These requests are dealt with on a case-by-case basis
via p...@ripe.net.  Also note that, on an individual basis, participants
can apply for a RIPE Fellowship to develop their professional or
academic career.  For more information, please visit:
https://www.ripe.net/participate/ripe/ripe-fellowship

Submissions

Presenters should be clear on whether they wish to submit a presentation
for a plenary or working group (WG) session.  At present, most working
groups will solicit policy proposals, discussion points or other content
directly via their mailing lists.  If you’re not sure what kind of
session you should be presenting at, please visit:
https://ripe76.ripe.net/plenary-or-wg/

RIPE Meeting attendees are quite sensitive to keeping presentations
non-commercial, and product marketing talks are strongly discouraged.
Repeated audience feedback shows that the most successful talks focus on
operational experience, research results, or case studies.  For example,
presenters wishing to describe a commercial solution should focus on the
underlying technology and not attempt a product demonstration.

Presenters should indicate how much time they will require.  In general,
the time allocated for the different presentation formats is as follows:

- Plenary presentations: 20-25 minutes presentation with 5-10 minutes
  discussion
- Tutorials: up to two hours (Monday morning)
- Workshops: one hour (during evening sessions) to two hours (Monday
  morning)
- BoFs: approximately one hour (during evening sessions)
- Lightning talks: 10 minutes total for both presentation and any
  discussion

The following general requirements apply:

- Proposals must be submitted using the meeting submission system,
  https://ripe76.ripe.net/submit-topic/
- Lightning talks should also be submitted using the meeting submission
  system (https://ripe76.ripe.net/submit-topic/) and can be submitted
  any time up to and including the meeting week.  The allocation of
  lightning talks will be announced on short notice, in some cases on
  the same day but often one day prior to the time slot allocated.
- Presenters who propose a panel or BoF are encouraged to include
  speakers from several (perhaps even competing) companies and/or a
  neutral facilitator.
- All presentation proposals will only be considered by the PC if they
  contain at least draft presentation slides (slides may be updated
  later on).  For panels, proposals must contain a clear description, as
  well as the names of invited panellists, presenters and moderators.

If you have any questions or requests concerning content submissions,
please email p...@ripe.net.

-- 
Benno J. Ov