Minutes 1st IANA RC Teleconference
Dear Review Committee
I’m attaching minutes of the 1st IANA RC teleconference for your perusal.
Regards
German
Thanks German. They look good to me!
Nurani
On 6 Mar 2017, at 13:06, German Valdez german@nro.net wrote:
Dear Review Committee
I’m attaching minutes of the 1st IANA RC teleconference for your perusal.
Regards
German
<20160215 Minutes IANA Review Committee .pdf> _______________________________________________ Rc mailing list Rc@nro.net https://nro.net/mailman/listinfo/rc
Thanks German,
Just a minor amendment for consistency. Please substitute MJ by EM in the reference to my name.
Everything else looks fine.
Regards
Ernesto
El 6/3/17 a las 09:06, German Valdez escribió:
Dear Review Committee
I’m attaching minutes of the 1st IANA RC teleconference for your perusal.
Regards
German
Rc mailing list Rc@nro.net https://nro.net/mailman/listinfo/rc
Please amend the sentence from: "JS reminded that the scope of the IANA RC is limited to an advisory role to the RIR." to: "JS reminded that it is clear that the output of the IANA RC is limited to an advise to the RIR."
Also a question...
It seems there is a lot of overlap between the RC and the ASO AC and the work is somewhat complementary. For example we had a discussion of additional f2f meetings for the ASO AC due to percieved work load of the RC. Would it he helpful to clearly distinguish ASO AC action items from RC action items by have a distinguishing prefix such as Action Item RC-170215004?
__Jason
On Mon, Mar 6, 2017 at 7:06 AM, German Valdez german@nro.net wrote:
Dear Review Committee
I’m attaching minutes of the 1st IANA RC teleconference for your perusal.
Regards
German
Rc mailing list Rc@nro.net https://nro.net/mailman/listinfo/rc
Jason,
To me there is no overlap. Maybe for some of us who are members of both groups.
All of us have to be clear and avoid confusion. The ASO AC focus is related with global numbers policies and the Review Committee is related to the IANA Number services performance.
Regards
Ernesto
El 6/3/17 a las 13:39, Jason Schiller escribió:
Also a question...
It seems there is a lot of overlap between the RC and the ASO AC and the work is somewhat complementary. For example we had a discussion of additional f2f meetings for the ASO AC due to percieved work load of the RC. Would it he helpful to clearly distinguish ASO AC action items from RC action items by have a distinguishing prefix such as ActionItemRC-170215004?
__Jason
On Mon, Mar 6, 2017 at 7:06 AM, German Valdez <german@nro.net mailto:german@nro.net> wrote:
Dear Review Committee I’m attaching minutes of the 1st IANA RC teleconference for your perusal. Regards German _______________________________________________ Rc mailing list Rc@nro.net <mailto:Rc@nro.net> https://nro.net/mailman/listinfo/rc <https://nro.net/mailman/listinfo/rc>-- _______________________________________________________ Jason Schiller|NetOps|jschiller@google.com mailto:jschiller@google.com|571-266-0006
Rc mailing list Rc@nro.net https://nro.net/mailman/listinfo/rc
Ernesto,
In definition you are absolutely correct.
But I think mentally (at least I) have put a lot of parallels between the two groups. I know I group the ASO AC and RC work together mentally, and have found myself being reminded to complete pending RC work because of an upcoming ASO AC meeting (knowing full well, the one has nothing to do with the other, and RC work will not come up at an ASO AC meeting).
I have seen others reverse the groups when talking about work that needs accomplishing.
Was just wondering if I have some ASO AC action items and RC action items on my personal to do list, would it be helpful to not confuse them as they have similar naming.
Sounds like the answer is no.
Thanks for the response.
__Jason
On Mon, Mar 6, 2017 at 12:00 PM, Ernesto Majo ernesto@lacnic.net wrote:
Jason,
To me there is no overlap. Maybe for some of us who are members of both groups.
All of us have to be clear and avoid confusion. The ASO AC focus is related with global numbers policies and the Review Committee is related to the IANA Number services performance.
Regards
Ernesto
El 6/3/17 a las 13:39, Jason Schiller escribió:
Also a question...
It seems there is a lot of overlap between the RC and the ASO AC and the work is somewhat complementary. For example we had a discussion of additional f2f meetings for the ASO AC due to percieved work load of the RC. Would it he helpful to clearly distinguish ASO AC action items from RC action items by have a distinguishing prefix such as Action Item RC-170215004?
__Jason
On Mon, Mar 6, 2017 at 7:06 AM, German Valdez german@nro.net wrote:
Dear Review Committee
I’m attaching minutes of the 1st IANA RC teleconference for your perusal.
Regards
German
Rc mailing list Rc@nro.net https://nro.net/mailman/listinfo/rc
-- _______________________________________________________ Jason Schiller|NetOps|jschiller@google.com|571-266-0006 <(571)%20266-0006>
Rc mailing listRc@nro.nethttps://nro.net/mailman/listinfo/rc
Rc mailing list Rc@nro.net https://nro.net/mailman/listinfo/rc
Hi,
I agre with both of you! :)
That the two groups are really quite distinct with very different focus. We have similar people in both groups, but the objectives and the roles are quite different. Therefore it’s even more important to keep them separate and not get them confused or mixed together. The RC has its working methods, members, actions and other groups have theirs.
But if I understand you correctly Jason, all you are asking for is for all action items in the RC to follow the naming convention “RC-YYMMDD-No”. That would make it easier for all of us to track our action items from different groups as it gives the RC action items unique IDs.
That sounds like a very sensible request to me! :)
Nurani
On 6 Mar 2017, at 19:07, Jason Schiller jschiller@google.com wrote:
Ernesto,
In definition you are absolutely correct.
But I think mentally (at least I) have put a lot of parallels between the two groups. I know I group the ASO AC and RC work together mentally, and have found myself being reminded to complete pending RC work because of an upcoming ASO AC meeting (knowing full well, the one has nothing to do with the other, and RC work will not come up at an ASO AC meeting).
I have seen others reverse the groups when talking about work that needs accomplishing.
Was just wondering if I have some ASO AC action items and RC action items on my personal to do list, would it be helpful to not confuse them as they have similar naming.
Sounds like the answer is no.
Thanks for the response.
__Jason
On Mon, Mar 6, 2017 at 12:00 PM, Ernesto Majo <ernesto@lacnic.net mailto:ernesto@lacnic.net> wrote: Jason,
To me there is no overlap. Maybe for some of us who are members of both groups. All of us have to be clear and avoid confusion. The ASO AC focus is related with global numbers policies and the Review Committee is related to the IANA Number services performance.
Regards
Ernesto
El 6/3/17 a las 13:39, Jason Schiller escribió:
Also a question...
It seems there is a lot of overlap between the RC and the ASO AC and the work is somewhat complementary. For example we had a discussion of additional f2f meetings for the ASO AC due to percieved work load of the RC. Would it he helpful to clearly distinguish ASO AC action items from RC action items by have a distinguishing prefix such as Action Item RC-170215004?
__Jason
On Mon, Mar 6, 2017 at 7:06 AM, German Valdez <german@nro.net mailto:german@nro.net> wrote: Dear Review Committee
I’m attaching minutes of the 1st IANA RC teleconference for your perusal.
Regards
German
Rc mailing list Rc@nro.net mailto:Rc@nro.net https://nro.net/mailman/listinfo/rc https://nro.net/mailman/listinfo/rc
-- _______________________________________________________ Jason Schiller|NetOps|jschiller@google.com mailto:jschiller@google.com|571-266-0006 tel:(571)%20266-0006
Rc mailing list Rc@nro.net mailto:Rc@nro.net https://nro.net/mailman/listinfo/rc https://nro.net/mailman/listinfo/rc
Rc mailing list Rc@nro.net mailto:Rc@nro.net https://nro.net/mailman/listinfo/rc https://nro.net/mailman/listinfo/rc
-- _______________________________________________________ Jason Schiller|NetOps|jschiller@google.com mailto:jschiller@google.com|571-266-0006
Rc mailing list Rc@nro.net https://nro.net/mailman/listinfo/rc
Thanks for the feedback of the minutes,
I’d like to give 24 hours more before I incorporate Ernesto and Jason input and publish it in the NRO website.
Thanks
German
On 7 Mar 2017, at 2:39 am, Jason Schiller jschiller@google.com wrote:
Please amend the sentence from: "JS reminded that the scope of the IANA RC is limited to an advisory role to the RIR." to: "JS reminded that it is clear that the output of the IANA RC is limited to an advise to the RIR."
Also a question...
It seems there is a lot of overlap between the RC and the ASO AC and the work is somewhat complementary. For example we had a discussion of additional f2f meetings for the ASO AC due to percieved work load of the RC. Would it he helpful to clearly distinguish ASO AC action items from RC action items by have a distinguishing prefix such as Action Item RC-170215004?
__Jason
On Mon, Mar 6, 2017 at 7:06 AM, German Valdez german@nro.net wrote: Dear Review Committee
I’m attaching minutes of the 1st IANA RC teleconference for your perusal.
Regards
German
Rc mailing list Rc@nro.net https://nro.net/mailman/listinfo/rc
-- _______________________________________________________ Jason Schiller|NetOps|jschiller@google.com|571-266-0006
participants (4)
-
Ernesto Majo -
German Valdez -
Jason Schiller -
Nurani Nimpuno