[Euro-board] Fwd: [Finance-sc] REMINDER - FY19 Additional Budget Requests - Timeline and Criteria

Tue Jan 9 18:12:29 UTC 2018

Sorry, just off the vacation, missed the deadline.
Wale,  lot of details behind the simple statements. Such as:
- connection of IOT systems to the public internet: security of critical
infrastructure vs. perception of what internet of things is. In fact, most
of the people start thinking about smart house. Which is small fraction of
IOT.
- autonomous systems running on batteries: CPU power vs lifecircle. Support
full IP stack on single battery for 10 years? Not yet there...
- IP-less communications: up to 90% of all IOT devices currently are not IP
based, especially in manufacturing, sensors networks, medicine, smart city
management, utilities metering and monitoring
- dogma of mobile operators (sell more SIM cards): expectations of NB-IOT
as a silver bullet. Right to the head of mobile telecom :) Because it
doesn't work as RPU model
I can go on for few pages, but lets get to the point. If we think the topic
might be interesting as EURALO session at next IGF, we have to focus on IG
topics:
- risk of proprietary protocols and war of standards. ISO vs RFC, history
repeat itself?
- risk of governmental overcontrol;
- what happens to the data generated by IOT? Stays within national boarder?
At what conditions and under what kind of regulations it crosses the border?
- sensitive private data gained from IOT big data patterns: patch to GDPR
or something brand new?
Kinda in this direction.

Yours, --andrei


2018-01-09 0:27 GMT+03:00 Olawale Bakare <wales.baky at gmail.com>:

> Dear Andrei,
>
> Thank you for your kind email. Great having your support for this topic. I
> believe, if we are able to package this IoT proposal well in time enough
> before the deadline date, EURALO would have a great team for its workshop,
> come next IGF.
>
> I understand your mindset about the concept of all-IP-based and
> acknowledge your busy schedules. But In the meantime, I would appreciate
> getting your comment(s) further in that regard.
>
> Nevertheless, the unified communication paradigm is an enterprise-wide
> approach to designing, implementing and delivery of IoT solutions, using
> the legacy telecommunication systems. There are other models and approaches
> from other service providers or implementers though.  Meanwhile, the
> complexity of the design ( networks, standards, and interoperability),
> there are also strong security concerns and the reliability of its entwined
> software-driven processes.
>
> This is an interesting topic, I hope we hear and/or get support from
> others before the deadline of 5 January.
>
> With regards,
> Wale
>
>

-- 
Andrey Kolesnikov
https://iotas.ru


2018-01-09 0:27 GMT+03:00 Olawale Bakare <wales.baky at gmail.com>:

> Dear Andrei,
>
> Thank you for your kind email. Great having your support for this topic. I
> believe, if we are able to package this IoT proposal well in time enough
> before the deadline date, EURALO would have a great team for its workshop,
> come next IGF.
>
> I understand your mindset about the concept of all-IP-based and
> acknowledge your busy schedules. But In the meantime, I would appreciate
> getting your comment(s) further in that regard.
>
> Nevertheless, the unified communication paradigm is an enterprise-wide
> approach to designing, implementing and delivery of IoT solutions, using
> the legacy telecommunication systems. There are other models and approaches
> from other service providers or implementers though.  Meanwhile, the
> complexity of the design ( networks, standards, and interoperability),
> there are also strong security concerns and the reliability of its entwined
> software-driven processes.
>
> This is an interesting topic, I hope we hear and/or get support from
> others before the deadline of 5 January.
>
> With regards,
> Wale
>
>
>
> On Mon, Jan 8, 2018 at 9:34 AM, Andrei Kolesnikov <andrei at rol.ru> wrote:
>
>> I support this. However 95% of IoT has nothing to do with all-ip-based :)
>> So we have a great topic for discussion.
>>
>> --andrei
>>
>> 2018-01-07 17:23 GMT+03:00 Olawale Bakare <wales.baky at gmail.com>:
>>
>>> Dear all,
>>>
>>> Please, I would like to propose a topic on IoT, as a workshop to be
>>> funded
>>> at the next IGF.
>>>
>>> *EURALO Workshop Proposal at 2018 IGF.  Topic*: *The Internet-of-Things
>>> (IoT) and the Increasing Governance Challenge Ahead.*
>>>
>>> *Background Information*
>>>
>>>
>>> The IoT evolution includes a broad range of sectors, including the
>>> automotive, finance, consumer electronic devices, retail services and
>>> even
>>> agriculture. Central to the solutions and deployments of IoT: Unified
>>> communication. The unified communication relies heavily on the
>>> All-IP-Based
>>> scheme for end-to-end delivery of IoT solutions.
>>>
>>> All-IP-Based Deployment: what about the internet architecture? All things
>>> internet; as implementation and deployment on top gear the use of IP
>>> addressing ( IPv6) and DNS schemes are important for the success of IoT's
>>> applications, security, and governance.
>>>
>>> Workshop's themes - governance, out-set resilient security design,
>>> internet
>>> end-users from the angle of privacy, rights to know the sharing of
>>> individual's personal data (GDPR implementation?), across the
>>> hyper-connectedness, clustered objects, public infrastructure as well as
>>> the centralized process systems.
>>>
>>> With regards,
>>> Wale
>>>
>>> On Sat, Jan 6, 2018 at 1:09 AM, Olivier MJ Crépin-Leblond <ocl at gih.com>
>>> wrote:
>>>
>>> > FYI -- we need to discuss this at our EURALO Board call, but ahead of
>>> > the call, please make suggestions about any request EURALO might need
>>> to
>>> > make.
>>> > Kindest regards,
>>> >
>>> > Olivier
>>> >
>>> >
>>> > -------- Forwarded Message --------
>>> > Subject:        [Finance-sc] REMINDER - FY19 Additional Budget
>>> Requests -
>>> > Timeline and Criteria
>>> > Date:   Sat, 6 Jan 2018 00:45:36 +0000
>>> > From:   ICANN At-Large Staff <staff at atlarge.icann.org>
>>> > To:     'finance-sc at atlarge-lists.icann.org'
>>> > <finance-sc at atlarge-lists.icann.org>
>>> > CC:     Alan Greenberg (alan.greenberg at mcgill.ca) <
>>> > alan.greenberg at mcgill.ca>
>>> >
>>> >
>>> >
>>> > Dear All,
>>> >
>>> > This is a friendly reminder to please follow up with your RALO's ALSes
>>> > regarding possible FY19 Additional Budget Requests.
>>> >
>>> > They must be submitted to At-Large staff by 12 January to be
>>> considered by
>>> > the FBSC.
>>> >
>>> > Kind regards,
>>> >
>>> > ICANN Policy Staff in support of the At-Large Community
>>> > E-mail: staff at atlarge.icann.org<mailto:staff at atlarge.icann.org>
>>> > Website: atlarge.icann.org<https://atlarge.icann.org/>
>>> > Facebook: facebook.com/icann<https://www.facebook.com/icannatlarge>
>>> > atlarge<https://www.facebook.com/icannatlarge>
>>> > Twitter: @<https://twitter.com/ICANNAtLarge>ICANNAtLarge<http
>>> > s://twitter.com/ICANNAtLarge>
>>> > [unknown.png]
>>> >
>>> >
>>> >
>>> > From: ICANN At-Large Staff
>>> > Sent: Monday, December 11, 2017 10:24 AM
>>> > To: 'finance-sc at atlarge-lists.icann.org' <finance-sc at atlarge-lists.
>>> > icann.org>
>>> > Cc: Alan Greenberg (alan.greenberg at mcgill.ca) <
>>> alan.greenberg at mcgill.ca>;
>>> > ICANN At-Large Staff <staff at atlarge.icann.org>
>>> > Subject: FY19 Additional Budget Requests - Timeline and Criteria
>>> >
>>> > Dear All,
>>> >
>>> > Welcome to all the 2018 Members and Participants of the ALAC
>>> Sub-Committee
>>> > on Finance and Budget<https://community.icann.org/display/atlarge/
>>> > ALAC+Subcommittee+on+Finance+and+Budget#ALACSubcommitteeonFinanceandBu
>>> > dget-1537253> (FBSC).
>>> >
>>> > This note is to announce that the FY19 Additional Budget Request
>>> process
>>> > has started.  This process pertains to a dedicated part of the overall
>>> > ICANN annual budget that is set aside to fund specific requests from
>>> the
>>> > community for activities that are not already included in the recurring
>>> > ICANN budget. FY19 Additional Budget Requests cover the period 1 July
>>> 2018
>>> > through 30 June 2019.
>>> >
>>> > The relevant information is available on the At-Large FY19 Additional
>>> > Budget Request Workspace<https://community.ic
>>> ann.org/display/atlarge/At-
>>> > Large+FY19+Additional+Budget+Request+Workspace>, including the key
>>> > deadlines, details of the process, principles and the request template.
>>> > The FBSC plays a key role in reviewing all At-Large FY19 Additional
>>> Budget
>>> > Requests for submission to ICANN.
>>> >
>>> > IMPORTANT: In 2016, the members of the ALAC Finance and Budget
>>> > Sub-Committee (FBSC) agreed to the following criteria for At-Large
>>> > proposals:
>>> >
>>> >   *   Outreach should not be a major focus. Activities to improve
>>> > engagement with existing members is encouraged.
>>> >   *   If any request is made on outreach, it should probably go through
>>> > the CROPP program and not this special request process.
>>> >   *   Proposals should include ways in which will make the ALAC and/or
>>> the
>>> > At-Large community more effective and develop the At-Large community.
>>> >   *   RALO requests must go through a bottom up process within their
>>> RALO
>>> > prior to being submitted for consideration by the FBSC.
>>> >   *   They must be explicitly supported by the RALO representative on
>>> the
>>> > FBSC.
>>> >   *   Staff is currently expecting that basic resources for community
>>> > communications/printing will be supported through the core ICANN
>>> budget,
>>> > but that community proposals for printing , etc. will be accepted as a
>>> > back-up in case expectations change.  Specific proposals for
>>> communications
>>> > resources beyond simple printing and editing functions should be
>>> prepared
>>> > and submitted.
>>> >  IMPORTANT:  Between now and 12 January 2018 the RALOs are asked to
>>> review
>>> > any ALS request or complete a template on behalf of the RALO and send
>>> > requests to At-Large Staff<mailto:staff at atlarge.icann.org>.
>>> >
>>> > Kind regards,
>>> > ICANN Policy Staff in support of the At-Large Community
>>> > E-mail: staff at atlarge.icann.org<mailto:staff at atlarge.icann.org>
>>> > Website: atlarge.icann.org<https://atlarge.icann.org/>
>>> > Facebook: facebook.com/icann<https://www.facebook.com/icannatlarge>
>>> > atlarge<https://www.facebook.com/icannatlarge>
>>> > Twitter: @<https://twitter.com/ICANNAtLarge>ICANNAtLarge<http
>>> > s://twitter.com/ICANNAtLarge>
>>> > [unknown.png]
>>> >
>>> > _______________________________________________
>>> > Finance-sc mailing list
>>> > Finance-sc at atlarge-lists.icann.org
>>> > https://atlarge-lists.icann.org/mailman/listinfo/finance-sc
>>> >
>>> > _______________________________________________
>>> > Euro-board mailing list
>>> > Euro-board at atlarge-lists.icann.org
>>> > https://atlarge-lists.icann.org/mailman/listinfo/euro-board
>>> >
>>> _______________________________________________
>>> Euro-board mailing list
>>> Euro-board at atlarge-lists.icann.org
>>> https://atlarge-lists.icann.org/mailman/listinfo/euro-board
>>>
>>
>>
>>
>> --
>> Andrey Kolesnikov
>> RIPN.NET
>>
>>
>


-- 
Andrey Kolesnikov
RIPN.NET