Re: [RAI] Dispatch Charter - draft B

[Gonzalo Camarillo <[e-mail]>]

Hi,

yes, including so many drafts in the agenda does not make sense. More 
focused agendas where things can be actually discussed are much better 
and the way to go.

Cheers,

Gonzalo


Spencer Dawkins wrote:
> OK, now that we've executed code for something like DISPATCH once...
> 
> 
>>> > The Dispatch working group is chartered to consider proposals for
>>> > new work in the RAI area and identify, or help create, an
>>> > appropriate venue for the work. Options for handling new work
>>> > include:
>>> >
>>> > - Assigning the work to an existing WG.
>>> > - Developing a proposal for a BOF.
>>> > - Developing a charter and establishing consensus for a new WG
>>> >   or Exploratory Group. This option will primarily be used with
>>> >   fairly mature and well-defined efforts.
>>>
>>> One critical and insufficiently used option is the "gong".
>>> That is, we
>>> MUST be able to reject and defer work proposals. We might
>>> want this in
>>> the charter.
>>
>> A gong is only useful if the principals understand why the
>> gong was struck.  On the famous television show, some people
>> tried to get a gong -- it was funny.  At SIPPING (or DISPATCH),
>> I assure you that the principals are not trying to get a gong.
>>
>> The charter should explain what sort of feedback is given to
>> principals for rejected submissions:  point to another WG
>> (ugh, that's what DISPATCH is trying to avoid, no?), another
>> standards organization (e.g., 3GPP), "no, we don't like that
>> idea", or whatever.  The DISPATCH charter should explain this
>> with some crispness.
> 
> Gonzalo asked me to take notes for the DISPATCH session yesterday, and
> here's what my notes summarize as:
> 
> 1.1.1            Theo Zourzouvillys  Via Cookies
> draft-zourzouvillys-sip-via-cookie-02
> 
> What problem do we want Theo to work on? Don't want to take a hum for each
> attack - we'll discuss on the list.
> 
> 1.1.2            Christer Holmberg  Keepalive Without Outbound
> draft-holmberg-sip-keep-03
> 
> We'll take the hum on this draft on the list, after Christer submits a
> completed 04 draft.
> 
> 1.1.3            Hadriel Kaplan  Secure Call ID
> draft-kaplan-sip-secure-call-id-00
> 
> We'll continue discussions on the list.
> 
> 1.1.4            Hadriel Kaplan  Session ID
> draft-kaplan-sip-session-id-01
> 
> Will discuss this draft on the list...
> 
> 1.1.5            Alan Johnston  User to User for ISDN
> draft-johnston-sipping-cc-uui-07
> 
> Looking for continued feedback on this list.
> 
> 1.1.6            Alan Johnston  Batch NOTIFYs
> draft-johnston-sipping-batch-notify-00
> 
> More list discussion would be great.
> 
> 1.1.7            Salvatore Loreto  Context-ID Requirements
> draft-loreto-sipping-context-id-requirements
> 
> Need more discussion onlist.
> 
> 1.1.8            Salvatore Loreto  Changes to Referred-By
> draft-loreto-sipping-3892bis-01
> 
> 1.1.9            Hadriel Kaplan  Updates to the Updates to Asserted 
> Identity
> in SIP
> draft-kaplan-sipping-pai-responses-00
> 
> More conversation on the list, please.
> 
> 1.1.10       Radu State  Digest Relay Attack
> draft-state-sip-relay-attack-00
> 
> Gonzalo - there is interest, need to decide what the next step is.
> 
> So... I think that 8 out of 10 of the drafts presented weren't gonged, 
> but they didn't get to a point where we know what to do with them, either.
> 
> This wasn't quite as bad as the SubIP area used to be (IPO and CCAMP 
> routinely had 20 drafts presented at six minutes per draft, and we 
> didn't have time to talk about any of the drafts because we had to start 
> the presentation on the next draft), but we definitely need to get 
> better as a community at converging on stuff that's NOT controversial 
> before we get to a face-to-face meeting, so we can spend significant 
> amounts of time on stuff that IS controversial when we're face-to-face.
> 
> This would be good to think about, while we're thinking about the 
> DISPATCH charter, IMO.
> 
> Thanks,
> 
> Spencer
> 
> 
> _______________________________________________
> RAI mailing list
> [e-mail]
> https://www.ietf.org/mailman/listinfo/rai