Agenda:
- Status
- 2806bis
- tel: url related drafts
- other uri schemes
- charter update discussion

****
Status:
Jon Peterson is the new AD affective Wednesday

1. 2806bis updated
2. saw some successful TRIP interop
3. CPL - will be unblocked soon (caller prefs in WGLC)
     - need to decide to do an XML schema or DTD.. will go to the list

4. TRIP MIB updated with MIB expert comments - waiting on MIB expert
final review

5. TGREP updated - need reviewers : volunteers will do by Apr 18th
   Bob Penfield
   Mary Barnes
   Vijay Gurbani

****
2806bis status (Henning)
- resolved the SIP resolution model (decided what the tel: URI is for)
      either a device has a dial plan (can translate to a public E164 or
a local number + context), or it doesn't (just use a SIP URI)
      the combination of local number and phone-context becomes unique
      ex: service numbers like 411/911 become  tel:911;phone-context=+1

- there are multiple phone-contexts allowed, is this a problem

-Flemming Andreason asked for clarification on tollfree (800) numbers
vs. service numbers
     this is a uniqueness vs. reachability issue
      a tel: URI of +18005551212 is globally unique, but not necessarily
globally reachable.

- comment from Keith Drage
   according to E.164, a local service number is NOT an E164 address

- Henning will issue -09, asking for nits review before WGLC

- Question: can we remove the multiple phone-contexts?....what was the
intent?  answer: label a number valid in local numbers
.. since this is a reachability question, these shouldn't be added in
the first

- Lawrence Conroy confirmed that this was originally motivated to
provide validity (reachability)

- Jonathan Rosenberg:  since this complicates URI matching, we should
remove it if it is not explicitly motivated.
- It's gone!

- Brian Rosen brought up issue that phone might have an extension
(which is not a tel URL) and an abbreviated phone number with a dial
plan (which can be), this might be confusing to user
- Mike Pierce - this is just a misunderstanding of the meaning of dial
plan, just use the same phone-context for both.
- Lots of variations of argreement on the above.

- Ready for WGLC

Review volunteer:
Flemming Andreason
Rohan Mahy
Paul Kyzivat
Tamara
Francios Audet

***
other tel URL-related drafts
- number portability params
- calling party category
- trunk group
- service-type parameter in tel URL

number portability and freephone
-Flemming:  what are the semantics of the cic parameter?  should we
just be stuffing things from ISUP right into the tel URL?
- Jon Peterson: some of these parameters are only ever useful in a PSTN
environment.  you wouldn't need them in a greenfield SIP network for
example
- Richard Statsny: We might need this information for a PSTN to PSTN
service using enum in a private environment
- Jonathan:  what do we use tel URL to mean?  dial this number? (its
original use)  no; a name for a PSTN resource?  yes
    ...things like transit selection (routing are out of scope)
- Jon P: the cic is part of the name in a freephone number  (it is a
naming authority which helps you lookup a pseudonym)
- Lawrence:  PINT tried to translate all ISUP parameters, and that was
horrible.  don't do it unless it is part of the names
- Jon P: both parameters in the draft are part of the name
- Henning: if you can take it away and it is still unique and still the
same resource then it is part of the name
- took a hum: lukewarm support but no objections

calling party category
- will take this to the list, there was no comment on the list.

trunk group stuff
- no comment since last time.
- Vijay asked if he should rev:  yes

service type parameter
- withdrawn

****
other URI schemes
enum URI
- Rohan, Jonathan: when would you use this instead of a tel URI?
- Lawrence: draft will be significantly simplified, maybe useful for a
webpage?  you have no way to say this is only useful if you do enum
lookup
- Henning:  just always resolve tel URI (and recurse), adding a hint
seems fine
- Juha: never do an enum lookup more than once
- Jon P: enum is broken.  not a perfect system.   maybe just want a
"don't lookup in enum" flag.  if you can create an enum URI, why not
just use another URI.
- out of time--take to list

****
charter update:
- trip mib - wglc monday
- tgrep - to IESG in May
- update to tel URL - to IESG in June
- extensions to tel URL (freephone to IESG in June)
   others?