Tagged: RFC

Have your say: KAREN network capacity RFC

REANNZ is seeking your input on how we will manage network capacity on KAREN if and when it becomes a scarce resource.

Second chance for comment – KARENRFC on network capacity

KARENRFC P-0002-00 addresses how REANNZ will manage network capacity if and when it becomes a scarce resource, and the role of the KAREN. Member community in providing guidance and advice to REANNZ on such matters.

A second video conference has been scheduled to take place this Thursday provide members an extended opportunity to comment on this important issue. If you are unable to attend please post your comments on the KARENRFC wiki or email your engagement contact at REANNZ who will post comments on your behalf.

View and comment on the RFC

To view and comment on KARENRFC P-0002-00 visit the KARENRFC page on the KAREN wiki.

Share

Reminder – three KAREN RFCs open for comment

The first of three video conferences to discuss your feedback on the KAREN Request for Comment papers currently open for consultation will take place in a week’s time, on Thursday 3 February.

KARENRFCs open for comment

REANNZ has three KAREN Request for Comment papers open for consultation, covering resource allocation, working groups, and the RFC process. The papers are open for comment until early February 2011.

  1. KARENRFC S-0003-00 – KAREN Working Group Formation, Lifecycle and Terms of Reference
  2. KARENRFC P-0002-00 – Resource Allocation – Network Capacity
  3. KARENRFC S-0001-01 – Addendum to KAREN Request For Comment KARENRFC S-0001-00

Visit the KARENRFC page on the KAREN wiki to view and comment on the papers, and for the video conference connection details.

Related stories

Share

Three KAREN RFCs open for comment

REANNZ has 3 KAREN Request for Comment papers open for consultation, covering resource allocation, working groups, and the RFC process. The papers are open for comment until early February 2011.

KARENRFCs open for comment

  1. KARENRFC S-0003-00 – KAREN Working Group Formation, Lifecycle and Terms of Reference
  2. KARENRFC P-0002-00 – Resource Allocation – Network Capacity
  3. KARENRFC S-0001-01 – Addendum to KAREN Request For Comment KARENRFC S-0001-00

Visit the KARENRFC page on the KAREN wiki for full details, and to view and comment on the papers.

Share

KAREN Request for Comment Process Approved

The first KAREN Request for Comment document was approved by the REANNZ Board last week, confirming the KARENRFC process. This milestone was achieved after rough consensus was obtained from the KAREN community.

First KAREN request for comment document approved

The first KAREN Request for Comment document was approved by the REANNZ Board on 18 November. This document detailed the KARENRFC submission, consultation and approvals process.

This milestone was achieved after rough consensus was obtained from the KAREN community, who provided comments via KAREN wiki, telephone, video conference, face to face and email. Many thanks to those members who contributed to this outcome.

We now welcome additional KARENRFC documents from the community using the format and process described in KARENRFC S-0001-00. This is your opportunity to contribute to KAREN’s continual evolution.

Second KAREN request for comment now open for your comment

REANNZ has submitted a second KARENRFC which is open for comment on the KARENRFC wiki.

Resource Allocation – Network Capacity KARENRFC P-0002-00: Abstract

As members increase their capability to exploit KAREN’s capabilities, situations are emerging where some specific and aggregate usage patterns are placing some network circuits at full capacity, e.g. Astronomy and YouTube. Additional planned activities, e.g. off-net route transit and high performance computing, are likely to create additional stress.

Visit the KARENRFC page on the KAREN wiki (http://www.wiki.karen.net.nz/index.php/KARENRFC) to download the full document and make your comments. The VC details are also on this page.

Share

Reminder: Have your say on the evolution of KAREN

REANNZ recently launched a new request for comment process to enable KAREN members to have a greater say in the evolution of KAREN. Members are welcome to join tomorrow’s video conference to discuss community feedback.

Why the KARENRFC process?

Our members’ confidence and usage of KAREN is changing and growing. This may impact KAREN in its functionality, scalability and reach. KAREN users are busy people, but member contribution to what KAREN is and might become is crucial. To ensure KAREN evolves in a way that accounts for the needs of our members, we are proposing a KAREN Request for Comment process.

About the KAREN Request for Comment process

REANNZ is proposing a KAREN Request for Comment process (RFC), modelled on the principles of the Internet Engineering Task Force RFC process and procedures. This process provides the KAREN community a structured method to constructively contribute to the evolution of KAREN policy and codes of practice.

For further information, see the KARENRFC page on the KAREN wiki )

The first KARENRFC for your comment

The first KARENRFC (KARENRFC S-0001-00) has been submitted for your comment. This submission from REANNZ seeks comment on the proposed KARENRFC procedure.

KARENRFC S-0001-00: Abstract

The provision of this KAREN request for comment (KARENRFC) document by REANNZ provides KAREN members a method to develop standards, design and policy. Ultimately members who use the KARENRFC process have the ability to contribute to the evolution of KAREN policy and codes of practice. This document describes the KARENRFC document and procedure leading to publication and adoption by the community.

Visit the KARENRFC page on the KAREN wiki ) to download the full document and make your comments. The VC details are also on this page.

Share

Have your say in the evolution of KAREN

REANNZ has today launched a new request for comment process to enable KAREN members to have a greater say in the evolution of KAREN.

Why the KARENRFC process?

Our members’ confidence and usage of KAREN is changing and growing. This may impact KAREN in its functionality, scalability and reach. KAREN users are busy people, but member contribution to what KAREN is and might become is crucial. To ensure KAREN evolves in a way that accounts for the needs of our members, we are proposing a KAREN Request for Comment process.

About the KAREN Request for Comment process

REANNZ is proposing a KAREN Request for Comment process (RFC), modelled on the principles of the Internet Engineering Task Force RFC process and procedures. This process provides the KAREN community a structured method to constructively contribute to the evolution of KAREN policy and codes of practice.

For further information, see the KARENRFC page on the KAREN wiki )

The first KARENRFC for your comment

The first KARENRFC (KARENRFC S-0001-00) has been submitted for your comment. This submission from REANNZ seeks comment on the proposed KARENRFC procedure.

KARENRFC S-0001-00: Abstract

The provision of this KAREN request for comment (KARENRFC) document by REANNZ provides KAREN members a method to develop standards, design and policy. Ultimately members who use the KARENRFC process have the ability to contribute to the evolution of KAREN policy and codes of practice. This document describes the KARENRFC document and procedure leading to publication and adoption by the community.

Visit the KARENRFC page on the KAREN wiki ) to download the full document and make your comments.

Share