Re: [sipcore] RESPONSE REQUESTED: SIPCORE work and milestones

["Asveren, Tolga" <[e-mail]>]

Sorted according to my order of preference:

i- A mechanism for labeling the nature of SIP calls, with <draft-schulzrinne-sipcore-callinfo-spam> as a likely candidate draft.
I can actively review. This draft addresses a real/practical/urgent industry need.

ii- "Happy Eyeballs for SIP" (aka Happy Earballs), currently under discussion on the list.
I can actively review/co-author. This shouldn’t; take too long and probably would end up standardizing a few common-sense/almost obvious semantics/changes in currently defined procedures -which makes it important-

iii- "DTLS Transport for SIP", as proposed by Tolga Asveren's recent messages.
I can (co)-author. Use of UDP in a secure way is important for large-scale servers.

The other two are of equal importance from my perspective and are at the bottom of my list.

I assume any RFC6555 Happy Eyeballs related discussions/bis activity should take place mainly in the V6ops WG(?)

Thanks,
Tolga

From: sipcore [mailto:[e-mail]] On Behalf Of Adam Roach
Sent: Tuesday, December 20, 2016 3:27 PM
To: 'SIPCORE' <[e-mail]>
Cc: Ben Campbell <[e-mail]>
Subject: [sipcore] RESPONSE REQUESTED: SIPCORE work and milestones

[as chair]

Now that we have our new charter approved, I'd like the working group to have a discussion about the specific work items that we should take on in the short- to medium-term so that we can revise our milestones appropriately. Based on recent discussions on the mailing list, the following topics have some mind-share behind them. What I'd like from everyone with an interest in any of these topics is to indicate (a) whether you are willing to actively review and comment on documents on the topic; and (b) what priority each task has relative to each other: there are five topics; please indicate a unique priority from one (most important) to five (least important) for each topic.

  1.  "Happy Eyeballs for SIP" (aka Happy Earballs), currently under discussion on the list.
  2.  "DTLS Transport for SIP", as proposed by Tolga Asveren's recent messages.
  3.  A mechanism for labeling the nature of SIP calls, with <draft-schulzrinne-sipcore-callinfo-spam> as a likely candidate draft.
  4.  Fixing Content-ID in SIP, as discussed in <https://www.ietf.org/mail-archive/web/sipcore/current/msg07245.html><https://www.ietf.org/mail-archive/web/sipcore/current/msg07245.html>, with <draft-holmberg-sipcore-content-id> as a likely candidate draft.
  5.  Clarifications around SIP name-addr, with <draft-sparks-sipcore-name-addr-guidance> as a likely candidate draft

I will also note that we have already declared consensus on adopting <draft-ietf-sipcore-status-unwanted> as a WG document, and will be adding an associated milestone. I want to take this opportunity to remind people that the document is in WGLC, and your comments are strongly encouraged, the earlier the better.

Please respond before the end of 2016. Thanks!

Thanks!

/a