Trump names new FCC chairman

[Roy]

Trump has picked Ajit Pai to serve as the next chairman of the Federal 
Communications Commission. Pai is currently the senior Republican 
commissioner at the FCC and does not require Senate approval.


http://money.cnn.com/2017/01/23/technology/trump-fcc-chairman/index.html

Re: How ISPs bill : Time Zones & 95th Percentile Calculations

[Patrick W. Gilmore]

NANOG’ers:

Steve McManus of Akamai and I have a few questions regarding how providers use 
time zones for billing, and how the 95th percentile (95/5) is calculated.

Many ISPs use UTC on logs and such for reasons which should be obvious. But do 
they use local time for billing? What if there are ports in multiple time 
zones? When calculating 95/5 for LACP groups, is the aggregate used or 
individual physical ports? Etc.

We have created a short form to collect some real-world data on this.

https://goo.gl/d1HRNb

We fully understand this is far from a statistically randomized double-blind 
survey, but it is what we could do in the few minutes of spare time we had.

The form is only 7 multiple-choice questions, with two optional “comment” 
sections and an optional contact info section. We would really appreciate if 
people would share data (anonymously!) on how they bill or get billed.

The form is designed to be used once per relationship. If you have two 
upstreams who use two different billing methods, we would greatly appreciate if 
you could fill in the form twice. It seemed easier to have you click 7 radio 
buttons twice than ask you to explain the different methods on one form.

Thank you for your time. Results will be aggregated and published at some later 
date to be determined. If you would like the results faster, be sure to leave 
your email address in the contact section.

-- 
TTFN,
patrick



-- 
TTFN,
patrick

Call for presentations RIPE 74

[Benno Overeinder]

Dear colleagues,

Please find the CFP for RIPE 74 below or at
https://ripe74.ripe.net/submit-topic/cfp/.

The deadline for submissions is *12 March 2017*.

Please also note that speakers do not receive any extra reduction or
funding towards the meeting fee at the RIPE Meetings.

Kind regards,

Benno Overeinder
RIPE PC Chair
https://ripe74.ripe.net/programme/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 74 will take place from 8-12 May 2017 in Budapest, Hungary.

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 74.
See the full descriptions of the different presentation formats,
https://ripe74.ripe.net/submit-topic/presentation-formats/.

Proposals for plenary sessions, BoFs, panels, workshops and tutorials
must be submitted for full consideration no later than 12 March 2017.
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)


Submissions

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
- 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://ripe74.ripe.net/submit-topic/submission-form/.

- Lightning talks should also be submitted using the meeting submission
  system (https://ripe74.ripe.net/submit-topic/submission-form/) and can
  be submitted any time up to and including the meeting week.
  Allocation of lightning talks will start a few days before the
  meeting, and will continue throughout the meeting.  During the
  meeting, they may be announced on the day before the talk or even on
  the same day as the talk.

- Lightning talks should also be submitted using the meeting submission
  system (https://ripe74.ripe.net/submit-topic/submission-form/) 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.

- Due to potential technical issues, presenters/panellists should be
  physically present at the RIPE Meeting.

If you have any questions or requests concerning content submissions,
please email pc [at] ripe [dot] net.

-- 
Benno J. Overeinder
NLnet Labs
http://www.nlnetlabs.nl/

Re: Passive Optical Network (PON)

[Josh Reynolds]

That's a genious idead

On Jan 23, 2017 11:17 AM, "Leo Bicknell"  wrote:

> In a message written on Sat, Jan 21, 2017 at 03:22:20PM -0600, Stas Bilder
> wrote:
> > Now, to the projects.
> > I have never heard of seen PON on a DC level.
>
> A friend of mine told me of a fascinating in-data center PON solution.
>
> He had a customer that needed high speed multicast fan-out.  They
> chose to use a 10G/1G PON solution, a single source node sending
> 10G PON with a 1G backchannel, 100% of the traffic was multicast.
> It could be passively split in DC up to 128:1 with zero "packet
> loss", good luck finding an Ethernet switch which can take in 10G
> of multicast in and turn it into 1280G of multicast out without
> dropping a frame.  It was all done entirely inside of a single
> data center.
>
> Since then I've mentioned the trick to several other folks I know
> who need high speed multicast/broadcast replication.  In the DC
> distance is rarely an issue, so the solution degenerates to special
> SFP's and a splitter, which is pretty dang simple.
>
> However, this is clearly a corner case, and I agree with your
> assessment overall.
>
> --
> Leo Bicknell - bickn...@ufp.org
> PGP keys at http://www.ufp.org/~bicknell/
>

Re: Passive Optical Network (PON)

[Leo Bicknell]

In a message written on Sat, Jan 21, 2017 at 03:22:20PM -0600, Stas Bilder 
wrote:
> Now, to the projects.
> I have never heard of seen PON on a DC level.

A friend of mine told me of a fascinating in-data center PON solution.

He had a customer that needed high speed multicast fan-out.  They
chose to use a 10G/1G PON solution, a single source node sending
10G PON with a 1G backchannel, 100% of the traffic was multicast.
It could be passively split in DC up to 128:1 with zero "packet
loss", good luck finding an Ethernet switch which can take in 10G
of multicast in and turn it into 1280G of multicast out without
dropping a frame.  It was all done entirely inside of a single
data center.

Since then I've mentioned the trick to several other folks I know
who need high speed multicast/broadcast replication.  In the DC
distance is rarely an issue, so the solution degenerates to special
SFP's and a splitter, which is pretty dang simple.

However, this is clearly a corner case, and I agree with your
assessment overall.

-- 
Leo Bicknell - bickn...@ufp.org
PGP keys at http://www.ufp.org/~bicknell/


signature.asc
Description: PGP signature

Re: Passive Optical Network (PON)

[Max Tulyev]

Hi,

using in rural area, it works. Much cheaper than ETTH.

On 21.01.17 18:44, Kenneth McRae wrote:
> Greeting all,
> 
> Is anyone out there using PON in a campus or facility environment?  I am 
> talking to a few vendors who are pushing PON as a replacement for edge 
> switching on the campus and in some cases, ToR switch in the DC.  Opinions on 
> this technology would be greatly appreciated.
> 
> Thanks,
> 
> Kenneth
>