[dispatch] Cullen raw notes from Dispatch Session IETF93

Cullen Jennings <fluffy@iii.ca> Wed, 22 July 2015 08:57 UTC

Return-Path: <fluffy@iii.ca>
X-Original-To: dispatch@ietfa.amsl.com
Delivered-To: dispatch@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com []) by ietfa.amsl.com (Postfix) with ESMTP id 7B74D1ACF55 for <dispatch@ietfa.amsl.com>; Wed, 22 Jul 2015 01:57:58 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.901
X-Spam-Status: No, score=-1.901 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RCVD_IN_DNSWL_NONE=-0.0001, SPF_PASS=-0.001] autolearn=ham
Received: from mail.ietf.org ([]) by localhost (ietfa.amsl.com []) (amavisd-new, port 10024) with ESMTP id s5eb6IFoYx_i for <dispatch@ietfa.amsl.com>; Wed, 22 Jul 2015 01:57:56 -0700 (PDT)
Received: from smtp112.iad3a.emailsrvr.com (smtp112.iad3a.emailsrvr.com []) (using TLSv1 with cipher ADH-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id D9CA01ACEC5 for <dispatch@ietf.org>; Wed, 22 Jul 2015 01:57:56 -0700 (PDT)
Received: from smtp31.relay.iad3a.emailsrvr.com (localhost.localdomain []) by smtp31.relay.iad3a.emailsrvr.com (SMTP Server) with ESMTP id 18DA23801B5; Wed, 22 Jul 2015 04:57:56 -0400 (EDT)
Received: by smtp31.relay.iad3a.emailsrvr.com (Authenticated sender: fluffy-AT-iii.ca) with ESMTPSA id 420823800FB; Wed, 22 Jul 2015 04:57:55 -0400 (EDT)
X-Sender-Id: fluffy@iii.ca
Received: from dhcp-a276.meeting.ietf.org (dhcp-a276.meeting.ietf.org []) (using TLSv1 with cipher DHE-RSA-AES256-SHA) by (trex/5.4.2); Wed, 22 Jul 2015 08:57:56 GMT
Content-Type: text/plain; charset="us-ascii"
Mime-Version: 1.0 (Mac OS X Mail 8.2 \(2102\))
From: Cullen Jennings <fluffy@iii.ca>
Date: Wed, 22 Jul 2015 10:57:53 +0200
Content-Transfer-Encoding: quoted-printable
Message-Id: <776E7383-EFDF-4119-9176-D05C54F06054@iii.ca>
To: IETF Dispatch <dispatch@ietf.org>
X-Mailer: Apple Mail (2.2102)
Archived-At: <http://mailarchive.ietf.org/arch/msg/dispatch/9NGD2XHj9z_UExrd0shx_hsZ5fk>
Cc: Cullen Jennings <fluffy@cisco.com>
Subject: [dispatch] Cullen raw notes from Dispatch Session IETF93
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 08:57:58 -0000

Theses are not the official minutes just some random notes I took as an individual contributor. The chairs will merge various notes together and form the minutes. 


Minute taker: Jean Mahoney

Agenda based to put ICE first. 

Would like to move all the ICE stuff in mmusic out to a separate WG. 

Flemming raise there is core ICE work and ICE SDP work. Need to get clarity on on 

No one spoke against forming new ICE WG. 

* We need to send the charter to the dispatch list. 


Matroska / ffv1  - start 9:18

Q. around what is internet standard 
- more IETF has right openness 

Q. do these need to be done together
- could be separated but both useful

Q. why not at SMPTE
- specs there are behind a paywall

Q. does development community meet in person
- mostly not

Q. what is the support in development community to bring this
- support from both
Q. Will they join actively 
- depends on outcome of if the IETF wants, both communities want to have these 

Mary -  clear there is interest in the room

Q. Do we have people people willing to review this work 
- we had more than a handful of people 
- need to get the 

* Action Chairs - ping the netvc and codec list 


GeoJson - start 9:50 

- not addressing location, location objects etc

- described some of the changes wanted to the spec 

Discussion around geopriv and privacy. One can look at Geo URL and there is a difference between specifying a location, and attaching that to something such as a device.  GeoJSON may be a layer down from the geolocation issues. 

Probably an interesting technical conversation around if relation of this and a geopriv location object. 

Who in room would sign up mailing list, read docs, and provide feedback? 

Handfull of people in the room said yes 


Location Source - start 10:15 

Asked who had read it 
- had a handfull of people in room 

Proposal - have the authors spin a rev of this document that clarifies this privcay and usage issue. 

No one was opposed to doing somehtin


Received Real - via parameter 

Propose we AD sponsor this but decision to be made by AD after security review. Use SIP Core mailing list. Need security review - we should ask EKR. And a side note that Adam Roach would make a great shepherd for draft. 


SLIM - start 10:38

Some discussion around routing. Multiple that had previously had issues had not problem with this version of charter. 

The charter is designed to allow the WG to decide what to do with routing or not.

Will likely change words to not require a recharter 

Further discussion of charter to happen on slim mailing list