[Internal-cg] Action items from ICG Face-to-Face Meeting #4, 6-7 February 2015
paf at frobbit.se
Sun Feb 8 00:46:10 UTC 2015
I have a clarification question on the below two action points.
Background: If ICG members do bring up issues, there are (at least) two different kind of issues / questions.
A. Clarifications that ICG members want to have (in writing) which the what I call "token holder" inside the ICG can create. This is what I would call *INTERNAL* communication. This can directly be an action point by the "token holder" to create this writeup. The interaction will be visible in the mailing list archive, list of action points and minutes from the meetings.
B. Questions that ICG send to the OC for clarification. This is to be formally sent to the OC, and a timer start ticking when we wait for action by the OC. These questions are to be sent by ICG Chair (Alissa), specifically posted on the ICG web page etc part from of course be visible in the minutes etc like [a].
Quite often [B] is preceded by [A].
When looking at these two action points, and trying to remember the discussion:
> 2. Arkko to compile a list of for a request for information from the protocol parameters community re jurisdiction, NTIA oversight and send it to internal-cg list.
> 3. Wilson to request clarification from CRISP team, questions put forth by Arasteh (regarding Section II.B.2 and III.A of the numbers proposal).
I in fact do think both are of class [A] above, i.e. the 2nd is *NOT* for ICG to send a question to the Numbers OC, at least not at this stage.
I.e. both action items should be actions on the token holder to do a writeup on summary of the discussions, and because of this, they should be:
2. Arkko to do write up of jurisdiction and NTIA oversight in the Protocols OC.
3. Wilson to do write up clarification re. questions put forth by Arasteh regarding Section II.B.2 and III.A of the Numbers OC.
I do NOT see any of these two at this stage be communication between ICG and OC. But the 2nd might be.
Whether things are class A and class B is and must also be driven by information from the token holder. That person MIGHT rather want things ICG might believe is class A to in fact be class B so that it is a more formal response.
-------------- next part --------------
A non-text attachment was scrubbed...
Size: 195 bytes
Desc: Message signed with OpenPGP using GPGMail
More information about the Internal-cg