[ICANN-CSC] Letter to CSC Charter Review team

[Elaine Pruis]

Just an FYI to the CSC,  the Charter Review Team has incorporated this
language into their draft report and proposed changes.
If it doesn't address your concerns, let's be sure to discuss on our call
on Thursday:

In the report:
The Charter includes a provision for the CSC or PTI to request a review or
change to service level targets. This provision needs to be amended to
include an SLE change procedure.

PLACEHOLDER

Need for proportionate Service Level Agreement change mechanism:
- Major change to SLA, arduous change procedure <-> Trivial change,
light-weight
procedure
- The SLA change procedure needs to be detailed (and linked to the charter)
for
consideration as part of this review.
Currently PTI, ICANN Org and CSC are working on it: Review team awaits
outcome.
Potential overlap and delineation between role CSC and IFRT under IFR
(section 18.3 (a), (b),
and (c ) (see below)


New Charter language:
The CSC will develop with the IANA Function Operator and ICANN a process
for timely amendments to the SLE’s where such changes are minor and are
unlikely to impose additional resource requirements on PTI (15).

Hope that helps.
Elaine

On Tue, Feb 13, 2018 at 11:37 AM, Allan MacGillivray <
allan.macgillivray at cira.ca> wrote:

> Kal – I just looked at this for the first time this afternoon.  It
> prompted me to go back and try to figure out where this stands.  In the
> hope of perhaps saving people a few steps, I believe that Jay and you
> produced the attached ‘Variable SLA Change Procedures’ document.  It
> defined four categories of SLA changes: 1. New SLA, 2. Change SLA
> definition and target/threshold, 3. Change SLA target/threshold (only), and
> 4. Remove SLA.  For three of the four categories (1, 2, 4) there would be
> ‘full community consultation’, while for 3, there would be no ‘full
> consultation’, but the CSC would directly consult the affected customer
> communities’.  Unless this very sensible approach has been superseded by
> something I have missed, you could perhaps incorporate the following into
> the letter with the following words:
>
>
>
> “The CSC will develop appropriate processes for engagement with registry
> operators and the community commensurate with the nature of the SLA change
> being proposed.  While consultations with registry operators would always
> be required, where the changes proposed are more minor, such as a change to
> only a target/threshold, a full community consultation would not be
> required”.
>
>
>
>
>
>
>
> Allan
>
>
>
>
>
>
>
>
>
> *From:* ICANN-CSC [mailto:icann-csc-bounces at icann.org] *On Behalf Of *Feher,
> Kal via ICANN-CSC
> *Sent:* Sunday, January 28, 2018 4:39 PM
> *To:* icann-csc at icann.org
> *Subject:* [ICANN-CSC] Letter to CSC Charter Review team
>
>
>
> Hello all,
>
> Attached is the proposed letter to be sent to the CSC Charter Review team.
>
> Please feel free to provide any alterations or feedback.
>
>
>
> --
>
> Kal Feher
>
> Neustar Inc.
>
> Melbourne, Australia
>
>
>
> _______________________________________________
> ICANN-CSC mailing list
> ICANN-CSC at icann.org
> https://mm.icann.org/mailman/listinfo/icann-csc
>
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://mm.icann.org/pipermail/icann-csc/attachments/20180214/5d4545fb/attachment.html>