From shijiapan at cmu.edu Thu Aug 16 21:14:59 2018 From: shijiapan at cmu.edu (shijiapan at cmu.edu) Date: Thu, 16 Aug 2018 15:14:59 -0400 Subject: [address-policy-wg] [Deadline Extended] SenSys 2018 Workshop DATA -- Data: Acquisition To Analysis Message-ID: <5b75cd33d9653_7e72b2087f61300724940@massmail-02.andrew.cmu.edu.mail> An HTML attachment was scrubbed... URL: From shijiapan at cmu.edu Sat Aug 18 00:19:18 2018 From: shijiapan at cmu.edu (shijiapan at cmu.edu) Date: Fri, 17 Aug 2018 18:19:18 -0400 Subject: [address-policy-wg] [Deadline Extended] SenSys 2018 Poster/Demo Message-ID: <5b7749e6e4335_1ef3e2ab451f2b31062371@massmail-02.andrew.cmu.edu.mail> An HTML attachment was scrubbed... URL: From ingrid at ripe.net Tue Aug 21 13:29:32 2018 From: ingrid at ripe.net (Ingrid Wijte) Date: Tue, 21 Aug 2018 13:29:32 +0200 Subject: [address-policy-wg] New AS Number Block allocated to the RIPE NCC Message-ID: <5ff6e9b0-bc39-c2bb-613a-b9d0c1157bdc@ripe.net> Dear Colleagues, The RIPE NCC has received the following AS Number Blocks from the IANA on 20 August 2018: 207260-208283 208284-209307 209308-210331 You may want to update your records accordingly. Best regards, Ingrid Wijte Registration Services Assistant Manager and Policy Development RIPE NCC From mschmidt at ripe.net Mon Aug 27 14:20:09 2018 From: mschmidt at ripe.net (Marco Schmidt) Date: Mon, 27 Aug 2018 14:20:09 +0200 Subject: [address-policy-wg] Proposal Implemented: 2018-01, "Organisation-LIR Clarification in IPv6 Policy" Message-ID: Dear colleagues, We are pleased to announce that we have implemented the policy proposal 2018-01, "Organisation-LIR Clarification in IPv6 Policy". This proposal clarified the wording used in the RIPE IPv6 Policy regarding terms such as "organisation" and "LIR". The archived policy proposal can be found at: https://www.ripe.net/participate/policies/proposals/2018-01 The RIPE Document, "IPv6 Address Allocation and Assignment Policy", is available at: https://www.ripe.net/publications/docs/ripe-707 Kind regards, Marco Schmidt Policy Officer RIPE NCC Sent via RIPE Forum -- https://www.ripe.net/participate/mail/forum From gert at space.net Tue Aug 28 23:36:07 2018 From: gert at space.net (Gert Doering) Date: Tue, 28 Aug 2018 23:36:07 +0200 Subject: [address-policy-wg] 2018-03 Last Call for Comments (Fixing Outdated Information in the IPv4 Policy) In-Reply-To: References: Message-ID: <20180828213607.GA52794@Space.Net> Dear AP WG, On Tue, Jul 24, 2018 at 03:13:56PM +0200, Marco Schmidt wrote: > Proposal 2018-03, "Fixing Outdated Information in the IPv4 Policy", is now in Concluding Phase. [..] > Any objection must be made by 22 August 2018 and must be supported by an explanation. > > If no substantive objections are raised by the end of Last Call, the proposal will complete the PDP and will be evaluated by the WG Chairs for consensus. No comments have been received in Last Call, which according to the PDP signals "consent". Thus, Eric and I declare consensus, and ask the NCC to implement (= update the bits in the policy document that Andrea identified as "needing updates"). thanks, Gert Doering -- APWG chair -- have you enabled IPv6 on something today...? SpaceNet AG Vorstand: Sebastian v. Bomhard, Michael Emmer Joseph-Dollinger-Bogen 14 Aufsichtsratsvors.: A. Grundner-Culemann D-80807 Muenchen HRB: 136055 (AG Muenchen) Tel: +49 (0)89/32356-444 USt-IdNr.: DE813185279 -------------- next part -------------- A non-text attachment was scrubbed... Name: signature.asc Type: application/pgp-signature Size: 833 bytes Desc: not available URL: From aleksbulgakov at gmail.com Wed Aug 29 06:20:07 2018 From: aleksbulgakov at gmail.com (Aleksey Bulgakov) Date: Wed, 29 Aug 2018 07:20:07 +0300 Subject: [address-policy-wg] 2018-03 Last Call for Comments (Fixing Outdated Information in the IPv4 Policy) In-Reply-To: <20180828213607.GA52794@Space.Net> References: <20180828213607.GA52794@Space.Net> Message-ID: But is there any reasons to comment something? We did it for 2015-01, but you declared consensus. ??, 29 ??? 2018 ?., 0:36 Gert Doering : > Dear AP WG, > > On Tue, Jul 24, 2018 at 03:13:56PM +0200, Marco Schmidt wrote: > > Proposal 2018-03, "Fixing Outdated Information in the IPv4 Policy", is > now in Concluding Phase. > [..] > > Any objection must be made by 22 August 2018 and must be supported by an > explanation. > > > > If no substantive objections are raised by the end of Last Call, the > proposal will complete the PDP and will be evaluated by the WG Chairs for > consensus. > > No comments have been received in Last Call, which according to the PDP > signals "consent". Thus, Eric and I declare consensus, and ask the NCC > to implement (= update the bits in the policy document that Andrea > identified as "needing updates"). > > thanks, > > Gert Doering > -- APWG chair > -- > have you enabled IPv6 on something today...? > > SpaceNet AG Vorstand: Sebastian v. Bomhard, Michael > Emmer > Joseph-Dollinger-Bogen 14 Aufsichtsratsvors.: A. Grundner-Culemann > D-80807 Muenchen HRB: 136055 (AG Muenchen) > Tel: +49 (0)89/32356-444 USt-IdNr.: DE813185279 > -------------- next part -------------- An HTML attachment was scrubbed... URL: From mschmidt at ripe.net Wed Aug 29 13:29:11 2018 From: mschmidt at ripe.net (Marco Schmidt) Date: Wed, 29 Aug 2018 13:29:11 +0200 Subject: [address-policy-wg] 2018-02 New Version Policy Proposal (Assignment Clarification in IPv6 Policy) Message-ID: Dear colleagues, RIPE Policy proposal, 2018-02, "Assignment Clarification in IPv6 Policy" is now available for discussion again. This proposal aims to clarify the definition of "Assign" in ripe-707 (section 2.6). This proposal has been updated following the last round of discussion and is now at version v2.0. Some of the differences from version v1.0 include: - Adjusting the scope of what is considered a sub-assignment You can find the full proposal at: https://www.ripe.net/participate/policies/proposals/2018-02 As per the RIPE Policy Development Process (PDP), the purpose of this four week Discussion Phase is to discuss the proposal and provide feedback to the proposer. At the end of the Discussion Phase, the proposer, with the agreement of the WG Chairs, will decide how to proceed with the proposal. We encourage you to review this proposal and send your comments to before 27 September 2018. Regards, Marco Schmidt Policy Officer RIPE NCC Sent via RIPE Forum -- https://www.ripe.net/participate/mail/forum From gert at space.net Wed Aug 29 23:32:53 2018 From: gert at space.net (Gert Doering) Date: Wed, 29 Aug 2018 23:32:53 +0200 Subject: [address-policy-wg] 2018-03 Last Call for Comments (Fixing Outdated Information in the IPv4 Policy) In-Reply-To: References: <20180828213607.GA52794@Space.Net> Message-ID: <20180829213253.GU11393@Space.Net> Hi, On Wed, Aug 29, 2018 at 07:20:07AM +0300, Aleksey Bulgakov wrote: > But is there any reasons to comment something? We did it for 2015-01, but > you declared consensus. The mail where I declared consensus had a summary and detailed reasoning why decisions were made. That certain people did not like 2015-01 because it broke their business model of requesting and quickly selling off /22s is understandable, but that was the whole point of the change - so yes, the community ignored those complaints. You know quite well that the WG chairs look very closely at the discussion and see if there is enough support to call it "rough consensus" or not (and either send the proposal back, or extent the discussion/review phase) Gert Doering -- APWG chair -- have you enabled IPv6 on something today...? SpaceNet AG Vorstand: Sebastian v. Bomhard, Michael Emmer Joseph-Dollinger-Bogen 14 Aufsichtsratsvors.: A. Grundner-Culemann D-80807 Muenchen HRB: 136055 (AG Muenchen) Tel: +49 (0)89/32356-444 USt-IdNr.: DE813185279 -------------- next part -------------- A non-text attachment was scrubbed... Name: signature.asc Type: application/pgp-signature Size: 833 bytes Desc: not available URL: From vijaysrao at ieee.org Thu Aug 30 04:02:49 2018 From: vijaysrao at ieee.org (Vijay Rao) Date: Thu, 30 Aug 2018 04:02:49 +0200 Subject: [address-policy-wg] CFP IPSN 2019 Message-ID: The 18th ACM/IEEE The International Conference on Information Processing in Sensor Networks (IPSN) =================================================================== April 16-18, 2019, Montreal, Canada IPSN'19 is part of CPS-IoT Week 2019, co-located with HSCC, ICCPS, CPS-IoT, and RTAS. http://ipsn.acm.org/2019 =================================================================== The International Conference on Information Processing in Sensor Networks (IPSN) is a leading annual forum on research in networked sensing and control, broadly defined. IPSN brings together researchers from academia, industry, and government to present and discuss recent advances in both theoretical and experimental research. Its scope includes signal and image processing, information and coding theory, databases and information management, distributed algorithms, networks and protocols, wireless communications, collaborative objects and the Internet of Things, machine learning, mobile and social sensing, and embedded systems design. Of special interest are contributions at the confluence of multiple of these areas. Like prior years, IPSN 2019 will continue its co-location with CPS-IoT WEEK, the premier venue for research and development of Cyberphysical Systems, and its strong focus on algorithms, theory, and systems for information processing using networks of embedded, human-in-the-loop, or social sensors, as well as new hardware and software platforms, design methods, architectures, modelling, implementation, evaluation, deployment experiences, and tools for networked embedded sensor systems and the Internet of Things. Topics of interest include, but are not limited to: - Sensor data storage, retrieval, processing - Streaming sensor system tasking and operation - Coding, compression, and information theory - Theoretical foundation and fundamental bounds - Network and system architectures and protocols - IoT gateway platform architecture and services - Outdoor, wide-area sensing systems - Location, time, and other network services - Programming models, languages, and systems - Programming models for IoT ensembles - Modeling, simulation, and measurement tools - Operating systems and runtime environments - Applications in health, wellness & sustainability - Applications in smart cities and urban health - Experiences, challenges, comparisons of platforms - Discovery, coordination, and use of IoT services - Security and privacy in heterogeneous systems - IoT reliability, adaptability, and dependability - Technical assessment of emerging IoT standards - Wearable systems and data processing algorithms - Sensor-enabled drone platforms and algorithms In addition to IPSN's traditional focus, IPSN 2019 will place a particular emphasis on embedded machine learning and computer vision, with a special track centered on these topics. In this case, topics of interest include but are not limited to: - Machine learning and deep learning on sensor data - New hardware and system design to enable machine learning on sensor data - Novel embedded machine learning algorithms - Data related issues, such as methods, tools, and analysis - Computer vision for resource-constrained and mobile platforms ********Submission Guidelines******** Coming soon. ********Response Process******** As in previous years, IPSN will also elicit a review and response process. After the initial review, the program committee may request a short response from selected papers for additional clarifications. The authors will get a short time window of roughly 24 hours to respond. Participation in the response process is not mandatory. ****Joint statement from IPSN and IoTDI**** The two conferences are collaborating to create new synergies, also exploiting their CPSWEEK bi-annual co-location. Prospective authors are thus strongly encouraged to consider these guidelines: - Contributions of embedded nature and applying to network segments from the IoT gateway to field devices should be submitted to IPSN. Examples include localization, low-power wireless networking, and embedded data processing. - Contributions with an end-to-end perspective or applying to network segments from the IoT gateway to the cloud should be submitted to IoTDI. Examples include cloud data processing, edge computing, and systems covering multiple network segments. The TPC chairs of both conferences may agree to move a submitted paper from one to the other if they see a better fit, subject to the authors? consent. The final decision about where to submit, and therefore what program committee will review the work, ultimately rests with the authors. ********Key Dates******** Paper Abstract Registration: October 10th, 2018 11:59pm AoE(UTC-12) Paper Submission Deadline: (Firm*): October, 17th 2018 11:59pm AoE(UTC-12) Authors? rebuttal period December 17th - 19th, 2018 Acceptance Notification: January 16th, 2019 Camera-Ready Deadline: TBD ********Organizers******** General Chair: Rasit Eskicioglu (University of Manitoba) Technical Committee Chairs: Luca Mottola (Politecnico di Milan and RISE SICS) Bodhi Priyantha (Microsoft Research) -------------- next part -------------- An HTML attachment was scrubbed... URL: From elvis at velea.eu Thu Aug 30 06:55:52 2018 From: elvis at velea.eu (Elvis Daniel Velea) Date: Wed, 29 Aug 2018 21:55:52 -0700 Subject: [address-policy-wg] 2018-03 Last Call for Comments (Fixing Outdated Information in the IPv4 Policy) In-Reply-To: <20180829213253.GU11393@Space.Net> References: <20180828213607.GA52794@Space.Net> <20180829213253.GU11393@Space.Net> Message-ID: <797a1e86-9f39-e362-3248-0458289d233d@velea.eu> Gert, while this was more of a cosmetic change and while this proposal did have support an no objections, I think that 4-5 e-mails of support should have at least required an extended discussion/review phase. Especially since in last call nobody said a word. my 2 cents. Elvis On 8/29/18 14:32, Gert Doering wrote: > Hi, > > On Wed, Aug 29, 2018 at 07:20:07AM +0300, Aleksey Bulgakov wrote: >> But is there any reasons to comment something? We did it for 2015-01, but >> you declared consensus. > The mail where I declared consensus had a summary and detailed reasoning > why decisions were made. That certain people did not like 2015-01 because > it broke their business model of requesting and quickly selling off /22s > is understandable, but that was the whole point of the change - so yes, > the community ignored those complaints. > > You know quite well that the WG chairs look very closely at the discussion > and see if there is enough support to call it "rough consensus" or not > (and either send the proposal back, or extent the discussion/review phase) > > Gert Doering > -- APWG chair From gert at space.net Thu Aug 30 15:26:39 2018 From: gert at space.net (Gert Doering) Date: Thu, 30 Aug 2018 15:26:39 +0200 Subject: [address-policy-wg] 2018-03 Last Call for Comments (Fixing Outdated Information in the IPv4 Policy) In-Reply-To: <797a1e86-9f39-e362-3248-0458289d233d@velea.eu> References: <20180828213607.GA52794@Space.Net> <20180829213253.GU11393@Space.Net> <797a1e86-9f39-e362-3248-0458289d233d@velea.eu> Message-ID: <20180830132639.GA11393@Space.Net> Hi, On Wed, Aug 29, 2018 at 09:55:52PM -0700, Elvis Daniel Velea wrote: > while this was more of a cosmetic change and while this proposal did > have support an no objections, I think that 4-5 e-mails of support > should have at least required an extended discussion/review phase. This is a statement that should have been voiced after Erik's summary at the end of the review phase (and I do agree in principle that "more voices of support" would have been welcome). *Now* is too late for the WG chairs to do anything about it. The PDP for this proposal has concluded. (Technically, it could still run through an appeals process, though the question is "what for?" since nobody had any objections) > Especially since in last call nobody said a word. Last call does not require anyone to say anything. This is stated very explicitely in the PDP. Gert Doering -- NetMaster -- have you enabled IPv6 on something today...? SpaceNet AG Vorstand: Sebastian v. Bomhard, Michael Emmer Joseph-Dollinger-Bogen 14 Aufsichtsratsvors.: A. Grundner-Culemann D-80807 Muenchen HRB: 136055 (AG Muenchen) Tel: +49 (0)89/32356-444 USt-IdNr.: DE813185279 -------------- next part -------------- A non-text attachment was scrubbed... Name: signature.asc Type: application/pgp-signature Size: 833 bytes Desc: not available URL: From mschmidt at ripe.net Thu Aug 30 15:26:51 2018 From: mschmidt at ripe.net (Marco Schmidt) Date: Thu, 30 Aug 2018 15:26:51 +0200 Subject: [address-policy-wg] 2018-03 Proposal Accepted and Implemented (Fixing Outdated Information in the IPv4 Policy) Message-ID: Dear colleagues, Consensus has been reached on 2018-03, "Fixing Outdated Information in the IPv4 Policy". This proposal fixed outdated information in the RIPE Policy "IPv4 Address Allocation and Assignment Policies for the RIPE NCC Service Region". You can find the full proposal at: https://www.ripe.net/participate/policies/proposals/2018-03 The new RIPE Document is called ripe-708 and is available at: https://www.ripe.net/publications/docs/ripe-708 This proposal is implemented with immediate effect. Thank you to everyone who provided input. Kind regards, Marco Schmidt Policy Officer RIPE NCC Sent via RIPE Forum -- https://www.ripe.net/participate/mail/forum From aleksbulgakov at gmail.com Thu Aug 30 17:31:48 2018 From: aleksbulgakov at gmail.com (Aleksey Bulgakov) Date: Thu, 30 Aug 2018 18:31:48 +0300 Subject: [address-policy-wg] 2018-03 Last Call for Comments (Fixing Outdated Information in the IPv4 Policy) In-Reply-To: <20180830132639.GA11393@Space.Net> References: <20180828213607.GA52794@Space.Net> <20180829213253.GU11393@Space.Net> <797a1e86-9f39-e362-3248-0458289d233d@velea.eu> <20180830132639.GA11393@Space.Net> Message-ID: May we do it for 2015-01? For example it would help to switch to IPv6, but the NCC wants to earn money and don't think about the community. :) (Technically, it could still run through an appeals process, though the question is "what for?" since nobody had any objections) ??, 30 ??? 2018 ?., 16:26 Gert Doering : > Hi, > > On Wed, Aug 29, 2018 at 09:55:52PM -0700, Elvis Daniel Velea wrote: > > while this was more of a cosmetic change and while this proposal did > > have support an no objections, I think that 4-5 e-mails of support > > should have at least required an extended discussion/review phase. > > This is a statement that should have been voiced after Erik's summary > at the end of the review phase (and I do agree in principle that > "more voices of support" would have been welcome). > > *Now* is too late for the WG chairs to do anything about it. The PDP for > this proposal has concluded. > > (Technically, it could still run through an appeals process, though the > question is "what for?" since nobody had any objections) > > > > Especially since in last call nobody said a word. > > Last call does not require anyone to say anything. This is stated > very explicitely in the PDP. > > Gert Doering > -- NetMaster > -- > have you enabled IPv6 on something today...? > > SpaceNet AG Vorstand: Sebastian v. Bomhard, Michael > Emmer > Joseph-Dollinger-Bogen 14 Aufsichtsratsvors.: A. Grundner-Culemann > D-80807 Muenchen HRB: 136055 (AG Muenchen) > Tel: +49 (0)89/32356-444 USt-IdNr.: DE813185279 > -------------- next part -------------- An HTML attachment was scrubbed... URL: From gert at space.net Thu Aug 30 21:41:20 2018 From: gert at space.net (Gert Doering) Date: Thu, 30 Aug 2018 21:41:20 +0200 Subject: [address-policy-wg] 2018-03 Last Call for Comments (Fixing Outdated Information in the IPv4 Policy) In-Reply-To: References: <20180828213607.GA52794@Space.Net> <20180829213253.GU11393@Space.Net> <797a1e86-9f39-e362-3248-0458289d233d@velea.eu> <20180830132639.GA11393@Space.Net> Message-ID: <20180830194119.GC11393@Space.Net> Hi, On Thu, Aug 30, 2018 at 06:31:48PM +0300, Aleksey Bulgakov wrote: > May we do it for 2015-01? For example it would help to switch to IPv6, but > the NCC wants to earn money and don't think about the community. :) The NCC is not involved in policy making. The NCC provides feedback and implements what the community decides, by means of the PDP. But you know all that, so would you please stop trolling a completely unrelated discussion thread? Gert Doering -- APWG chair -- have you enabled IPv6 on something today...? SpaceNet AG Vorstand: Sebastian v. Bomhard, Michael Emmer Joseph-Dollinger-Bogen 14 Aufsichtsratsvors.: A. Grundner-Culemann D-80807 Muenchen HRB: 136055 (AG Muenchen) Tel: +49 (0)89/32356-444 USt-IdNr.: DE813185279 -------------- next part -------------- A non-text attachment was scrubbed... Name: signature.asc Type: application/pgp-signature Size: 833 bytes Desc: not available URL: