Changes between Version 144 and Version 145 of WikiStart


Ignore:
Timestamp:
03/02/21 18:11:00 (17 months ago)
Author:
kirsty.p@…
Comment:

--

Legend:

Unmodified
Added
Removed
Modified

  • WikiStart

    v144 v145  
    11= Welcome to the IETF DISPATCH WG Wiki =
    22
    3 The DISPATCH WG in the ART area is chartered to review new work in the ART area. Based on mailing list discussion, if there is sufficient interest, willingness to contribute and WG consensus, new work items are dispatched in various ways depending upon the scope and applicability of the work.  Mailing list discussions should focus on the problem statement, objectives and deliverables in the form of a proposed charter.   Note, that not all new work items are required to be discussed in the DISPATCH WG - exceptions are items that clearly fit within the chart of an existing WG (in this case those WG chairs should be contacted) and in the case of topics that would clearly require an official Bof (in which case the ADs should be contacted).
     3The DISPATCH WG is chartered to bring on new work in the ART area and provide a conduit for new drafts, ideas and potential WGs. We're like a matchmaker between keen engineers and IETF processes/groups/procedures. DISPATCH is a catalyst to make recommendations to ADs or Chairs, based on the wisdom of the group – we don't make the decisions ourselves.
    44
    5 The following summarizes the current dispatchment options:
     5Please get in touch with the chairs if you have questions: Kirsty and Patrick, dispatch-chairs@ietf.org
     6It's tough navigating the IETF and we're here to help.
    67
    7 * New work item in DISPATCH WG for registrations only
     8== I want to be dispatched, what do I do? ==
     9
     10Bring up your intentions on the DISPATCH list (i.e. please send an email with your idea or draft to dispatch@ietf.org) and if you want agenda time, email the chairs (see "How to get on the agenda" below): dispatch-chairs@ietf.org
     11
     12It's easier to dispatch work when it's been discussed on the mailing list; it gives the group a good idea of what the work will involve. Even if there's not much interest or chatter, it lets participants see what is coming up at the meeting and can help discussion in the meeting.
     13
     14It's also usually helpful to bring a "charter" for your work – a simple page that sets out the problem statement, the scope, goals and non-goals, and deliverables. Even if you don't need or want a WG, it helps set out the scope of what you want to do.
     15
     16DISPATCH is not the only path to getting work started in the ART area, but it can helpful to expedite many cases. New work items are dispatched in various ways depending upon the scope and applicability of the work. Possible recommendations as a result of a DISPATCH meeting are:
    817
    918* New work item in currently chartered WG
     19* New WG
     20* Full BoF
     21* Individual/AD sponsored - for items limited in scope and applicability
     22* Feedback to refine the idea for the next meeting cycle
     23* New work item in DISPATCH WG
     24* Declination to adopt the work at that time
    1025
    11 * New WG
     26== How to get on the agenda ==
     27Email the chairs and email the dispatch list. If you email at least 4 weeks before the meeting to ask for a slot, you go to the front of the list for agenda time. But get in touch anyway if you missed this soft deadline and we'll see what we can do.
    1228
    13 * IETF official BoF - typically for work items that are of broad interest and potential impact within the ART area and across areas.
     29The chairs will aim to announce topics that have been dispatched for a particular IETF meeting 4 weeks before the meeting starts and update as necessary. Please cut us slack whilst there's a global pandemic and plenty of cyber attacks going on.
    1430
    15 * Individual/AD sponsored - for items limited in scope and applicability
     31A complete list of deadlines for IETF meetings is available here: [https://datatracker.ietf.org/meeting/important-dates/]
    1632
    17 === IETF-106 Deadlines===
    18 
    19 * Oct 4, 2019. Cutoff date for IETF BoF submissions.
    20 
    21 * Oct 7, 2019.  Cutoff date to notify the chairs/DISPATCH WG of plans to submit a proposal/topic.
    22 
    23 * Oct 14, 2019.  Cutoff for proposals (i.e., problem statement and proposed deliverables) for topics posted to the DISPATCH WG mailing list. 
    24 
    25 * Oct 21,  2019. Announcement of topics that have been dispatched for IETF-105.
    26 
    27 * Nov 4, 2019. Draft submission deadline.
    28 
    29 A complete list of deadlines for IETF-106 is available here:
    30 https://datatracker.ietf.org/meeting/important-dates/
    31 
    32 === Working with Deadlines ===
    33 
    34 * If you make the deadlines, you go to the front of the list for agenda time.
    35 
    36 * If you miss the deadlines, you go behind "Any Other Business" in terms of priority.
    37 
    38 * '''Please''' start draft names with: draft-<your-name-here>-dispatch-
    39 
    40 == DISPATCHed Topics ==
    41 
    42 The following summarizes the work items that have been dispatched or are in the process of being dispatched. Please note that this is *not* a complete summary of the topics discussed in DISPATCH, but rather the items that have been put forth for discussion at the meetings and/or agreed to be progressed. The status of the work items still underway is periodically posted to the DISPATCH WG mailing list. Please note that up-to-date charters are available on the DISPATCH or topic specific mailing list (s).
    43 
    44 === IETF-105 topics ===
    45 
    46 * Web Transport:  Agreement to pursue a formal BoF.
    47 
    48 === IETF-104 topics ===
    49 
    50 * Relay User Machine (RUM) :  '''RUM''' WG chartered.
    51  
    52 * JSON Contact:   Discussion to continue on DISPATCH mailing list. 
    53 
    54 * Web Packaging:  Agreement to pursue a formal BoF.
    55 
    56 === IETF-103 topics ===
    57 
    58 * HTTP Header Registry:   Agreement with proposal to split.
    59 
    60 * The Secret Token URI scheme:  Agreed to be progressed as  '''AD sponsored'''.
    61  * Document: https://datatracker.ietf.org/doc/draft-nottingham-how-did-that-get-into-the-repo/
    62 
    63 * Regular Expressions for Internet Mail:  Agreed to be progressed as  '''AD sponsored'''.
    64   * Document: https://datatracker.ietf.org/doc/draft-seantek-mail-regexen/
    65 
    66 === IETF-102 topics ===
    67 
    68 * HELIUM:  Discussion to continue on DISPATCH WG mailing list.
    69  *  Document: https://datatracker.ietf.org/doc/draft-schwartz-httpbis-helium/
    70 
    71 === IETF-101 topics ===
    72 
    73 * JSON Content Rules: Discussion to continue on ART list. 
    74  * Documents:
    75   * https://datatracker.ietf.org/doc/draft-newton-json-content-rules/
    76   * https://datatracker.ietf.org/doc/draft-newton-rdap-jcr/
    77 
    78 * Defining Well-Known URI:  Agreed to be progressed as '''AD sponsored'''.
    79  * Document: https://datatracker.ietf.org/doc/draft-nottingham-rfc5785bis/
    80 
    81 * New Media Stack: Discussion to continue on a new dedicated mailing list.
    82  * Document: https://datatracker.ietf.org/doc/draft-jennings-dispatch-new-media/
    83 
    84 === IETF-100 topics ===
    85 
    86 * i18n - Internationalization (Again): Discussion to continue on ART list.  ADs to consider how to progress documents.
    87  * Documents:
    88   * https://datatracker.ietf.org/doc/draft-klensin-idna-rfc5891bis
    89   * https://datatracker.ietf.org/doc/draft-freytag-troublesome-characters
    90   * https://datatracker.ietf.org/doc/draft-klensin-idna-5892upd-unicode70
    91 
    92 * E2E Secure Messaging for SIP/SIMPLE:  Agreed to be progressed as  '''AD sponsored'''.
    93  * Document: https://datatracker.ietf.org/doc/draft-campbell-sip-messaging-smime
    94 
    95 * Zstandard compression:  '''AD sponsored'''.  Published as '''RFC 8478'''.
    96 
    97 
    98 === IETF-99 topics ===
    99 
    100 * ECMAscript Media type updates:  Dispatched to '''DISPATCH WG'''
    101  
    102 * DNS Over HTTPS:  '''DOH WG''' chartered.
    103 
    104 * Web Packaging:  See IETF-104.
    105 
    106 
    107 === IETF-98 topics ===
    108 
    109 * Path MTU Discovery (PMTUD) for RTP/RTCP:  Will not be progressed.
    110  * Document:  https://datatracker.ietf.org/doc/draft-petithuguenin-dispatch-rtp-pmtud
    111 
    112 * Web Linking: '''AD sponsored'''.  Published as '''RFC 8288'''.
    113 
    114 * Q.850 Reason Location:  Dispatched to '''SIPCORE WG'''.
    115 
    116 * Cryptographic Update to DKIM:  '''DCRUP WG''' chartered.
    117 
    118 === IETF-97 topics ===
    119 
    120 * VoIP Spam: Dispatched to '''SIPCORE WG'''.
    121 
    122 * Regular Expressions for Email:  See IETF-103.
    123 
    124 === IETF-96 topics ===
    125 
    126 *   Glass to Glass Internet Ecosystem (GGIE): Interest in proponents refining work. More discussion needed.
    127  * Documents:
    128   * https://datatracker.ietf.org/doc/draft-deen-daigle-ggie/
    129   * https://datatracker.ietf.org/doc/draft-deen-naik-ggie-men-mpeg-dash/
    130 
    131 * Signalling one-click functionality for list email headers:  '''AD sponsored'''.  Published as '''RFC 8058'''.
    132 
    133 * Using a DNS SRV Record to Locate an X.509 Certificate Store: Agreed to be progressed as  '''AD sponsored'''.
    134   * Document: https://datatracker.ietf.org/doc/draft-bhjl-x509-srv/
    135 
    136 === IETF-95 topics ===
    137 
    138 * Best Practices for Securing RTP Media Signaled with SIP: '''SIPBrandy WG''' chartered.
    139 
    140 *  IANA Registration of SIP Resource- Priority Namespace for Mission Critical Push To Talk service:  '''AD sponsored'''.  Published as '''RFC 8101'''.
    141 
    142 * Last Diverting Line Identity: Needs more discussion.
    143   * Document: https://datatracker.ietf.org/doc/draft-weinronk-dispatch-last-diverting-line-id/
    144 
    145 === IETF-94 topics ===
    146 
    147 * An Opportunistic Approach for Secure Real-time Transport Protocol:  See IETF-95 '''SIPBrandy WG'''.
    148 
    149 === IETF-93 topics ===
    150 
    151 * GEOJson: '''GEOJSON WG''' chartered.
    152 
    153 * FFV1/Matroska: Proposed '''CELLAR WG'''.
    154 
    155 * Location Source Parameter:
    156  * Document: http://datatracker.ietf.org/doc/draft-winterbottom-dispatch-locparam/
    157 
    158 * Via header field parameter for received realm:  '''AD sponsored'''.  Published as '''RFC 8055'''.
    159 
    160 * Selection of Language for Internet Media (SLIM): '''SLIM WG''' chartered.
    161 
    162 === IETF-92 topics ===
    163 
    164 * Routing out of dialog requests: Needs more discussion.
    165   * Document:  https://datatracker.ietf.org/doc/draft-allen-dispatch-routing-out-of-dialog-request/
    166 
    167 * GEOJson: see IETF-93
    168 
    169 * Calling name identity Trust (CNIT):  Post IETF-92 discussion on cnit mailing list.  See draft-ietf-stir-passport-rcd in '''STIR WG'''.
    170  
    171 * VRS purpose for the Call Info header:  Needs more discussion
    172  * Document: https://datatracker.ietf.org/doc/draft-kyzivat-dispatch-trs-call-info-purpose/
    173 
    174 * Cause URI for service number translation. '''AD sponsored'''.  Published as '''RFC 8119'''
    175 
    176 
    177 === IETF-91 topics ===
    178 
    179 *  Correlation of multiple responses of forked INVITES in Back to Back User Agents: Needs more discussion.
    180  * Document: http://tools.ietf.org/html/draft-jesske-dispatch-forking-answer-correlation-00       
    181  * Mailing list discussion:   http://www.ietf.org/mail-archive/web/dispatch/current/msg05625.html
    182 
    183 === IETF-90 topics ===
    184 
    185 * Webpush: '''WEBPUSH WG''' chartered.
    186 
    187 * SIP URI Inter Operator Traffic Leg (IOTL) parameter: '''AD sponsored'''. Published as '''RFC 7549'''
    188 
    189 *  Mobile Equipment Identity (MEID) URNs: '''AD sponsored'''.  Published as '''RFC 8464'''
    190  
    191 
    192 === IETF-89 topics ===
    193 
    194 * OpenBTS:  Needs more mailing list discussion and a firmer proposal of problems being solved and deliverables.
    195  * Proposal: http://www.ietf.org/mail-archive/web/dispatch/current/msg05233.html
    196  * References:
    197    * [http://tools.ietf.org/wg/dispatch/trac/attachment/wiki/WikiStart/OpenBTS-Diagram-DISPATCH.pdf Architecture Diagram]
    198    * Source code:  https://wush.net/trac/rangepublic
    199 
    200 === IETF-88 topics ===
    201 
    202 * SDP negotiation of Data Channel sub-protocols: Dispatched to '''MMUSIC WG'''.
    203 
    204 
    205 === IETF-87 topics ===
    206 
    207 No topics dispatched.  See mailing list for some of the topics that were proposed:
    208 http://www.ietf.org/mail-archive/web/dispatch/current/msg04969.html
    209 
    210 === IETF-86 topics ===
    211 
    212 * SIP/XMPP:  '''STOX WG''' chartered
    213 
    214 * Logging: General support for adopting this work.  Dispatched to '''INSIPID WG'''.
    215 
    216 *  SIP Usage for Trickle ICE: Dispatched to '''MMUSIC WG'''. 
    217 
    218 *  BFCP over websockets: Dispatched to '''BFCPBIS WG'''.
    219 
    220 * MSRP over Websockets: '''AD sponsored'''.  Published as '''RFC 7977'''
    221  
    222 === IETF-85 topics ===
    223 
    224 * Indicating Fax over IP Capability in SIP:  '''AD sponsored'''.  Published as '''RFC 6913'''
    225 
    226 * Telephone-Related Queries (TERQ): '''MODERN WG''' chartered.
    227 
    228 
    229 === IETF-84 topics ===
    230 
    231 * Combined Use of SIP and XMPP (CUSAX): '''AD sponsored'''. Published as '''RFC 7081'''
    232 
    233 === IETF-83 topics ===
    234 
    235 * SIP Traversal Required for Applications to Work (STRAW): '''STRAW WG''' chartered.
    236 
    237 * Media Stream Signaling (MESS):  Dispatched to '''AVTEXT WG'''
    238  
    239 * Telephone-Related Queries (TERQ): See IETF-85.
    240 
    241 === IETF-82 topics ===
    242 
    243 * Remote Call, Device Control:  Post-IETF-82 decision not to charter.
    244    * (Original) Charter: http://www.ietf.org/mail-archive/web/dispatch/current/msg03778.html
    245 
    246 * Referencing and Verifying User Attributes: Interest in topic. Discussion to continue on the mailing list.
    247    * Related document: http://datatracker.ietf.org/doc/draft-ono-dispatch-attribute-validation/
    248 
    249 
    250 === IETF-81 topics ===
    251 
    252 * Session-ID: '''INSIPID WG'''  chartered.
    253  
    254 * Load Balancing:  WG interest but needs more discussion.
    255  * Charter: http://www.ietf.org/mail-archive/web/dispatch/current/msg03649.html
    256 
    257 * BFCP for UDP:  '''BFCPBIS WG''' chartered.
    258 
    259 * Global Service Provider Identification Number: Agreed to be progressed (likely as AD sponsored). Ongoing discussion should be on RAI area list (as opposed to DRINKS or DISPATCH). 
    260  * Related document: http://www.ietf.org/id/draft-pfautz-service-provider-identifier-urn-00.txt
    261 
    262 * SIP Action Referral: See Remote Device, Call Control @ IETF-82.
    263 
    264 === IETF-80 topics ===
    265 
    266 * Q4S (on agenda):  No interest in chartering this work.  Being published via '''ISE'''.
    267  * Related document:  http://datatracker.ietf.org/doc/draft-aranda-dispatch-q4s/
    268 
    269 * Reason header in responses:  '''AD sponsored'''. Published as '''RFC 6432'''
    270 
    271 * RTCWEB:  '''RTCWEB WG''' chartered.
    272 
    273 * VIPR: '''VIPR WG''' chartered.
    274 
    275 * SIP Action Referral:  See IETF-81.
    276 
    277 * SIP Interconnect guidelines:   No interest in chartering this work. 
    278 
    279 
    280 === IETF-79 topics ===
    281 
    282 * DTMF Info: No WG interest in this work. 
    283 
    284 * Telepresence: '''CLUE WG''' chartered.
    285 
    286 * BFCP for UDP:  See IETF-81
    287  
    288 
    289 === IETF-78 topics ===
    290 
    291 * Session-ID:  See IETF-81
    292 
    293 * Telepresence:  See IETF-79
    294 
    295 * VIPR:  See IETF-80
    296 
    297 * TEL URI WG proposal:  No interest in adopting this work as is. The recommendation is to go back to the general problem and describe the use cases such that an optimal solution can be developed.   
    298 
    299 
    300 === IETF-77 topics ===
    301 
    302 * E.164 to Metadata (E2M). '''BoF'''.
    303   * BoF meeting minutes: http://www.ietf.org/proceedings/10mar/minutes/e2md.txt
    304 
    305 
    306 === IETF-76 topics ===
    307 
    308 * Session Recording: '''SIPREC WG''' chartered.
    309 
    310 * Domain Registration: '''MARTINI WG''' chartered (completed deliverables, closed March 9th, 2011)
    311 
    312 * Disaggregated Media:  '''SPLICES WG''' chartered.
    313 
    314 * Alert-URNs:  '''SALUD WG''' chartered.
    315 
    316 * Reason in Response: see IETF-80.
    317 
    318 * SIP-XMPP: XMPP WG consensus not to charter this work (at IETF-80)
    319   * Proposed SIXPAC charter: http://www.ietf.org/mail-archive/web/dispatch/current/msg02699.html
    320 
    321 * SIP Overload: '''SOC WG''' chartered.
    322 
    323 
    324 === IETF-75 topics ===
    325 
    326 * Sound level indicator (for conferences): Work item added to '''AVT WG''' charter.
    327 
    328 * Codec: '''CODEC WG''' chartered.
    329 
    330 * Common Log Format: '''SIPCLF WG''' chartered.
    331 
    332 * Call Control User-to-User Information:  '''CUSS WG''' chartered.
    333 
    334 * Profile datasets (related to SIP configuration - from SIPPING WG): Work item removed from DISPATCH WG charter due to lack of interest.