Minutes for APPSAWG at IETF-89
minutes-89-appsawg-1

Minutes of the APPSAWG Meeting at IETF 89
March 3, 2014 -- London, UK

Meeting called to order at 9:30am.

The co-chairs presented the Note Well and circulated Blue Sheets.

APPSAWG Section

The co-chairs summarized the WG's work completed since IETF 88:
- RFC7103 published
- Two documents ready for the IESG

Some time was spent discussing status of current documents, and what the authors need
going forward:

The status of some of the open documents was reviewed briefly by authors:
1) draft-ietf-appsawg-multipart-form-data, Larry Masinter
- minor changes
- created test suite to see what current practice is
- wants help from interest participants
2) draft-ietf-appsawg-uri-get-off-my-lawn, Mark Nottingham
- in WGLC
- has review comments from Dave Crocker
- plans one more rev before sending to the IESG

New work proposals:
1) draft-thaler-uri-scheme-reg-ps, Dave Thaler
- work not finished by IRI before it shut down
- most URI schemes are not registered, what to do about it?
- should we use expert review or FCFS?
-- Baker: been waiting a long time for a SASL registration; expert review doesn't work
-- Moore: lower bar may make little difference; people just pick a name and hope it's
   unique
-- Hansen: what if the expert rejects?
- discussion on whether something, even if incomplete, is better than nothing
- Nottingham: concerned that wide use conflicts with W3C web principles; is using a
  new URI scheme the best way to get from browser to another protocol?
-- recommends a W3C liaison statement; will take that offline
- should we be lowering the bar for provisional registrations?
-- current template plus defining document for provisional
-- drop document or simplify template?
-- Masinter: media types might be better for dispatch on mobile
- should we register a scheme prefix?
-- RFC4395 allows registration of a reversed domain name as a prefix
-- there is current informal use of "ms-" as reserved for Microsoft
-- this would be better with expert review
-- Nottingham: W3C maintains a "safe" list of prefixes for use in browsers
-- Moore: it's delusional to tie security to a prefix
-- sounds like x- which eventually leaks
-- web+ is supposed to identify security schemes; controversial
-- hum was roughly opposed
- register scheme prefix based on reversed domain name?
-- Baker: we can't trust ICANN to manage that properly; too much money at stake
-- and reserve dots for reversed domain names
-- need to get advice from W3C
- a hum supported adoption of this as a WG document; Dave to submit mini-charter
  and list of reviewers
- Klensin: be careful about overlap with the URI WG

2) draft-greevenbosch-appsawg-cbor-cddl, Bert Greevenbosch
- chair: how many using CBOR so this is useful? six hands up
- should we wait for similar work in JSON?
- do we want separate scheme languages for JSON and CBOR?

3) RFC 6237, IMAP4 Multimailbox SEARCH Extension, Chris Newman
- Have other people implemented this? Apparently not.
- Interest in other implementations? A little.
- Would like to move to standards track
- Barry Leiba will have draft by end of March

APPAREA Section

New working groups and BOFs:
	•	Public Notary Transparency, Melinda Shore
	•	EPPEXT, Jim Galvin
	•	TCMTF BOF, Brian
	•	TAPS, Michael Welzl
	•	ACE, Kepeng Li
	•	DBOUND, Andrew Sullivan, Marc Blanchet
	•	UTA, Leif Johansson
	•	DNS Encryption, Peter Koch
	•	VNFPOOL, Melinda Shore

JSON update, Matt Miller
- current work done, rechartering
- considering: i-json, nomenclature, schemas or metaschemas

getdns API source release, Allison Mankin
	•	recently updated spec
	•	open source implementation
	•	python bindings, Melinda Shore
	•	https://getdnsapi.net

Vocabularies and Namespaces, Olafur Gudmundsson
	•	simplified terms for concepts: navigation, integrity, specification, etc.
	•	wide ranging discussion of DNS issues
	•	
A Multilingual Content Type (Nik Tomkinson, - draft-tomkinson-multilangcontent
	•	Idea is fine, implementation needs work, will take it to list

Augmented Reality Is The Future: Why the IETF Should Care, Christine Perey
	•	lots of devices coming out, want standard APIs to interop