[dispatch] Summary notes from Dispatch 93
"A. Jean Mahoney" <mahoney@nostrum.com> Wed, 22 July 2015 14:36 UTC
Return-Path: <mahoney@nostrum.com>
X-Original-To: dispatch@ietfa.amsl.com
Delivered-To: dispatch@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 58AF11A87C2 for <dispatch@ietfa.amsl.com>; Wed, 22 Jul 2015 07:36:45 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.91
X-Spam-Level:
X-Spam-Status: No, score=-1.91 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, T_RP_MATCHES_RCVD=-0.01] autolearn=ham
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id KlubiufQn1sx for <dispatch@ietfa.amsl.com>; Wed, 22 Jul 2015 07:36:42 -0700 (PDT)
Received: from nostrum.com (raven-v6.nostrum.com [IPv6:2001:470:d:1130::1]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id B87151A886C for <dispatch@ietf.org>; Wed, 22 Jul 2015 07:36:41 -0700 (PDT)
Received: from dhcp-8c60.meeting.ietf.org (dhcp-8c60.meeting.ietf.org [31.133.140.96]) (authenticated bits=0) by nostrum.com (8.15.2/8.14.9) with ESMTPSA id t6MEacCe057073 (version=TLSv1.2 cipher=ECDHE-RSA-AES128-GCM-SHA256 bits=128 verify=NO) for <dispatch@ietf.org>; Wed, 22 Jul 2015 09:36:40 -0500 (CDT) (envelope-from mahoney@nostrum.com)
To: dispatch@ietf.org
From: "A. Jean Mahoney" <mahoney@nostrum.com>
Message-ID: <55AFAA76.1020108@nostrum.com>
Date: Wed, 22 Jul 2015 16:36:38 +0200
User-Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.9; rv:38.0) Gecko/20100101 Thunderbird/38.1.0
MIME-Version: 1.0
Content-Type: text/plain; charset="utf-8"; format="flowed"
Content-Transfer-Encoding: 7bit
Archived-At: <http://mailarchive.ietf.org/arch/msg/dispatch/zHSrtPuSZTxeZxIKzoaT6zuei34>
Subject: [dispatch] Summary notes from Dispatch 93
X-BeenThere: dispatch@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: DISPATCH Working Group Mail List <dispatch.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/dispatch>, <mailto:dispatch-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/dispatch/>
List-Post: <mailto:dispatch@ietf.org>
List-Help: <mailto:dispatch-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/dispatch>, <mailto:dispatch-request@ietf.org?subject=subscribe>
X-List-Received-Date: Wed, 22 Jul 2015 14:36:45 -0000
Hi all, Here are my summary notes from the meeting this morning. Jean ------------------------------------------------------------------ Dispatch 93 2015-07-22 09:00-11:30 Congress Hall III Status and agenda bash ____________________________________________ Presentation: https://www.ietf.org/proceedings/93/slides/slides-93-dispatch-3.pdf Presenters: Mary Barnes, Cullen Jennings Note Taker: Jean Mahoney Jabber Relay: Ted Hardy Change to agenda - ICE WG to be presented first. Proposed ICE WG ___________________________________________________ Presentation: https://www.ietf.org/proceedings/93/slides/slides-93-dispatch-4.pdf Presenter: Pal-Erick Martinsen Flemming Andreasen, as MMUSIC chair, felt there were a lot of advantages, but wanted to clarify that there would be both core ICE and ICE SDP work. Ben Campbell, as AD, felt that ICE-specific SDP could be handled on a case-by-case basis, like the payload WG does. Roland felt that the charter may need more text regarding the interactions with other working groups, which should be discussed on the ICE mailing list. No one in the meeting room was opposed to the formation of the working group. ACTIONs: Send charter to the dispatch mailing list. Discuss interactions with other working groups on the ICE mailing list. FFV1 and Matroska ________________________________________________ Presentation: https://www.ietf.org/proceedings/93/slides/slides-93-dispatch-6.pdf Presenter: Tessa Fallon, Emmanuel References: - FFV1 Video Specification: https://mediaarea.net/temp/ffv1.html - Github: http://matroska.org/technical/specs/index.html Robert Sparks and Roni Even asked what was Internet-specific about this work. Jerome Martinez pointed out that Matroska was used with VP8, VP9 and WebM. Steve Lhome said that Matroska was designed for streaming in networks and that Opus could be stored in Matroska for streaming. Matroska is supported in Chrome, Firefox and MS Edge. Jerome Martinez said that, while the main purpose of Matroska was storage, it could be used for transport and that they were looking for transparency, open source and openness for their specification. They didn't take it to SMPTE because it's paywalled. Tessa said that although the specifications are already available and the work is complete, the specifications would benefit from the IETF review process. Ben Campbell asked if it was ok if IETF take over change control, and Tessa said that was understood. Ted Hardy said that the community would need to participate in the IETF or the effort would fail. Tessa said that she hoped the community and IETF would come together. Steve Lhome, an original author of Matroska, said he would continue to participate where ever the work was going to happen. Cullen and Dave Rice pointed out the needs for lossless video. Cullen felt the specifications didn't support interoperability as they were currently written, but didn't see the effort as a huge leap for the IETF. Steve Bozko and ??? voiced concerns about the ongoing maintenance aspects of the work. By raising hands, two people at the meeting showed interest in contributing. 8-10 people indicated that they were willing to review documents. Richard Barnes pointed out that netvc people were not in the room and that they may be interested. ACTION: Dispatch chairs to take the discussion to the list, contact the netvc list. GeoJSON ________________________________________________________ Presentation: https://www.ietf.org/proceedings/93/slides/slides-93-dispatch-5.pdf Presenter: Sean Gillies Charter: https://github.com/geojson/draft-geojson/blob/master/charter.md Document: draft-butler-geojson There was a discussion about whether GeoJSON was Location Information or Location Object, and whether GeoJSON would carry a Location Object or whether a Location Object would carry GeoJSON. Privacy considerations were also discussed: unlike geopriv, GeoJSON can describe a large area with multiple points with in it. Privacy considerations would be different for collections of points than for a single point. Roger Marshall voiced support for this work. A show of hands indicated that a few people would sign up for a mailing list, read documents and provide comments. If the work was taken on, it would go to a new working group; geopriv would not be reopened. ACTION: Post the question of starting a new working group on the dispatch mailing list and geopriv mailing list, which is still open. Location source parameter _______________________________________ Presentation: https://www.ietf.org/proceedings/93/slides/slides-93-dispatch-0.pdf Presenter: Andrew Hutton Document: draft-winterbottom-dispatch-locparam-00 Conrad said that this was required to satisfy safety regulations. It was discussed whether this parameter would ever be used for non-emergency situations. Andy said that once specified, it could be, but that the emergency situation was the only use case he knew of. Alissa Cooper asked that the document clearly identify the use cases that it would be supporting. ACTION: Authors to update the draft with supported use cases. Via header field parm for received realm _________________________ Presentation: https://www.ietf.org/proceedings/93/slides/slides-93-dispatch-1.pdf Presenter: Christer Holmberg Document: draft-holmberg-dispatch-received-realm-00 Adam Roach, as sipcore chair, explained that this draft did not fall under sipcore's narrow charter. Ben Campbell, as AD, said that the document could be AD-sponsored, but it needed a security review first. ACTIONs: Adam Roach to become document shepherd. RAI security advisor to review. Ben to discuss with security advisor if it can be AD-sponsored. Draft can be discussed on the SIPCORE mailing list. SLIM charter _________________________________________________ Presentation: https://www.ietf.org/proceedings/93/slides/slides-93-dispatch-2.pdf Presenter: Randell Gellens Charter: https://datatracker.ietf.org/wg/slim/charter/ The charter wording around routing was discussed. People felt that since routing would probably be handled by the working group at some point, the charter should capture it now rather than go through a re-chartering process later. ACTIONs: Henning Schulzrinne to submit a draft usable for common use cases based on his experience with caller prefs. Discuss charter wording on the SLIM mailing list. Other items __________________________________________________ Ted Hardy announced the QUIC protocol bar bof this evening in Congress I.
- [dispatch] Summary notes from Dispatch 93 A. Jean Mahoney
- Re: [dispatch] Summary notes from Dispatch 93 Mary Barnes