From spoofer-info at caida.org  Fri Feb  8 19:00:02 2019
From: spoofer-info at caida.org (CAIDA Spoofer Project)
Date: Fri, 8 Feb 2019 10:00:02 -0800
Subject: [NLNOG] Spoofer Report for NLNOG for Jan 2019
Message-ID: <201902081800.x18I02YN086517@fro.caida.org>

In response to feedback from operational security communities,
CAIDA's source address validation measurement project
(https://spoofer.caida.org) is automatically generating monthly
reports of ASes originating prefixes in BGP for systems from which
we received packets with a spoofed source address.
We are publishing these reports to network and security operations
lists in order to ensure this information reaches operational
contacts in these ASes.

This report summarises tests conducted within nld.

Inferred improvements during Jan 2019:
 none inferred

Source Address Validation issues inferred during Jan 2019:
   ASN Name                           First-Spoofed Last-Spoofed
 28878 SIGNET                            2018-06-27   2019-01-30
201290 BlackGATE                         2018-10-16   2019-01-28
  8737 PT                                2019-01-16   2019-01-24
 33915 TNF                               2019-01-28   2019-01-28

Further information for these tests where we received spoofed
packets is available at:
https://spoofer.caida.org/recent_tests.php?country_include=nld&no_block=1

Please send any feedback or suggestions to spoofer-info at caida.org

From arnold at nipper.de  Fri Feb  8 20:07:47 2019
From: arnold at nipper.de (Arnold Nipper)
Date: Fri, 8 Feb 2019 20:07:47 +0100
Subject: [NLNOG] Fwd: [PDB Announce] Want to work as freelancer for
 PeeringDB Product Committee or know someone who could/should?
In-Reply-To: <FDD63798-ED64-4019-96D0-07E09DFF5065@ipergy.net>
References: <FDD63798-ED64-4019-96D0-07E09DFF5065@ipergy.net>
Message-ID: <fc0def3a-aaaa-05d8-6332-3b46b3fcc79a@nipper.de>

If you are interested or know someone who is.


Greetings
Arnold


-------- Weitergeleitete Nachricht --------
Betreff: 	[PDB Announce] Want to work as freelancer for PeeringDB
Product Committee or know someone who could/should?
Datum: 	Tue, 29 Jan 2019 19:10:26 +0100
Von: 	Eric Loos <eric at ipergy.net>
An: 	pdb-announce at lists.peeringdb.com



PeeringDB is a non-profit member-based organization focussed on
delivering a reference database service to the internet peering
community that facilitates the building and maintenance of
interconnections, a reference for data center locations, and contact
information for networks, IXs, data centers and more globally.

To deliver more value to the community, the PeeringDB Board of Directors
has freed up funds for a part-time contractor product manager resource.
With this announcement we are soliciting offers from the community first
to fill this position.

The product manager will work within the PeeringDB Product Committee
under direction of the Product Committee Chair.

The responsibilities of the product manager include, but are not limited to:

  *
    Participate in monthly calls with the Product Committee
  *
    Actively follow up action points
  *
    Organize customer focus group sessions
  *
    Facilitate the creation of an ongoing roadmap for PeeringDB and
    provide this as input to the Outreach Committee (1 year roadmap)
  *
    Shepherd the discussions of issues on Github and ensure resolution
    of issues that require decisions
  *
    Request quotes for the implementation of features and request the
    necessary approvals
  *
    Manage implementation  and rollout of new features
  *
    Maintain the PeeringDB software release schedule
  *
    Keep Product Committee related documents on docs.peeringdb.com
    <http://docs.peeringdb.com> up to date
  *
    Ensure that the the PeeringDB Acceptable Use Policy and Privacy
    Policy are consistently applied
  *



In addition, due to the recent open sourcing of the underlying software,
the product manager shall describe the way user contributed code can
make it into the main release, the product manager will document the
release process in collaboration with the board, using Github issues as
the tracking system.

The engagement would be for approximately 16 hours a week during the
initial three months and 5 hours per week after this, for an initial
contract length of 12 months.

There are no specific location requirements, however the Product
Committee members are based in Western Europe and both East/West coast
USA, candidates should take this in mind with regards to calls and
communications.
Experience with industry events like APRICOT, AfPIF, NANOG, GPF, EPF or
similar events considered a plus

PeeringDB does not and shall not discriminate on the basis of race,
color, religion (creed), gender, gender expression, age, national origin
(ancestry), disability, marital status, sexual orientation, or military
status, in any of its activities or operations. These activities
include, but are not limited to, hiring and firing of staff, selection
of volunteers and vendors, and provision of services. We are committed
to providing an inclusive and welcoming environment for all members of
our staff, clients, volunteers, subcontractors, vendors, and clients.

Performance Indicators for initial contract period:

  *
    Deliver a roadmap that has been agreed with the Product Committee
    within the initial 3 months of the engagement
  *
    Organize at least one customer focus session within the first 6
    months and 1 subsequently every year
  *
    Keep the age of issues within decision and for review queues on
    github to a maximum of 30 days.
  *
    Ensure that new issues are triaged within one business day


Please send your resume and application letter to eric at peeringdb.com
<mailto:eric at peeringdb.com> or reach out if you have questions!

Eric Loos
Chair PeeringDB Product Committee

-- 
Arnold Nipper
email: arnold at nipper.de
mobile: +49 172 2650958
-------------- next part --------------
_______________________________________________
Pdb-announce mailing list
Pdb-announce at lists.peeringdb.com
https://lists.peeringdb.com/cgi-bin/mailman/listinfo/pdb-announce
-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 261 bytes
Desc: OpenPGP digital signature
URL: <http://mailman.nlnog.net/pipermail/nlnog/attachments/20190208/3501815d/attachment.sig>

From job at instituut.net  Fri Feb  8 20:32:50 2019
From: job at instituut.net (Job Snijders)
Date: Fri, 8 Feb 2019 20:32:50 +0100
Subject: [NLNOG] Fwd: [PDB Announce] Want to work as freelancer for
 PeeringDB Product Committee or know someone who could/should?
In-Reply-To: <FDD63798-ED64-4019-96D0-07E09DFF5065@ipergy.net>
References: <FDD63798-ED64-4019-96D0-07E09DFF5065@ipergy.net>
Message-ID: <CACWOCC-1L9p92Z4gTAGg=RZtfdQv_4BPyQvRcfuyV2pws365Vg@mail.gmail.com>

PeeringDB is op zoek naar een Freelancer

---------- Forwarded message ---------
From: Eric Loos <eric at ipergy.net>
Date: Tue, Jan 29, 2019 at 19:10
Subject: [PDB Announce] Want to work as freelancer for PeeringDB Product
Committee or know someone who could/should?
To: <pdb-announce at lists.peeringdb.com>


PeeringDB is a non-profit member-based organization focussed on delivering
a reference database service to the internet peering community that
facilitates the building and maintenance of interconnections, a reference
for data center locations, and contact information for networks, IXs, data
centers and more globally.

To deliver more value to the community, the PeeringDB Board of Directors
has freed up funds for a part-time contractor product manager resource.
With this announcement we are soliciting offers from the community first to
fill this position.

The product manager will work within the PeeringDB Product Committee under
direction of the Product Committee Chair.

The responsibilities of the product manager include, but are not limited to:

   - Participate in monthly calls with the Product Committee
   - Actively follow up action points
   - Organize customer focus group sessions
   - Facilitate the creation of an ongoing roadmap for PeeringDB and
   provide this as input to the Outreach Committee (1 year roadmap)
   - Shepherd the discussions of issues on Github and ensure resolution of
   issues that require decisions
   - Request quotes for the implementation of features and request the
   necessary approvals
   - Manage implementation  and rollout of new features
   - Maintain the PeeringDB software release schedule
   - Keep Product Committee related documents on docs.peeringdb.com up to
   date
   - Ensure that the the PeeringDB Acceptable Use Policy and Privacy Policy
   are consistently applied
   -



In addition, due to the recent open sourcing of the underlying software,
the product manager shall describe the way user contributed code can make
it into the main release, the product manager will document the release
process in collaboration with the board, using Github issues as the
tracking system.

The engagement would be for approximately 16 hours a week during the
initial three months and 5 hours per week after this, for an initial
contract length of 12 months.

There are no specific location requirements, however the Product Committee
members are based in Western Europe and both East/West coast USA,
candidates should take this in mind with regards to calls and
communications.
Experience with industry events like APRICOT, AfPIF, NANOG, GPF, EPF or
similar events considered a plus

PeeringDB does not and shall not discriminate on the basis of race, color,
religion (creed), gender, gender expression, age, national origin
(ancestry), disability, marital status, sexual orientation, or military
status, in any of its activities or operations. These activities include,
but are not limited to, hiring and firing of staff, selection of volunteers
and vendors, and provision of services. We are committed to providing an
inclusive and welcoming environment for all members of our staff, clients,
volunteers, subcontractors, vendors, and clients.

Performance Indicators for initial contract period:

   - Deliver a roadmap that has been agreed with the Product Committee
   within the initial 3 months of the engagement
   - Organize at least one customer focus session within the first 6 months
   and 1 subsequently every year
   - Keep the age of issues within decision and for review queues on github
   to a maximum of 30 days.
   - Ensure that new issues are triaged within one business day


Please send your resume and application letter to eric at peeringdb.com or
reach out if you have questions!

Eric Loos
Chair PeeringDB Product Committee
_______________________________________________
Pdb-announce mailing list
Pdb-announce at lists.peeringdb.com
https://lists.peeringdb.com/cgi-bin/mailman/listinfo/pdb-announce
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://mailman.nlnog.net/pipermail/nlnog/attachments/20190208/bee11bb0/attachment-0001.html>