Subject: [BLISS] Minutes from ACH: 2008.03.28

From: Shida Schubert <[email-masked]>
Date: Wed, 16 Apr 2008 14:36:31 -0700

Followings is the minutes from ACH design team meeting
3 weeks back. I apologize for submitting it so late.

Date/Time
---------------------------
2008.03.28 08:00PST-09:00PST

Attendees
---------------------------
- Francois Audet
- John Elwell
- Martin Dolly
- Shida Schubert

* Please send me an e-mail, if I've missed anybody..

Agenda: --------------------
1. Recapturing the discussions from the IETF 71.
2. Meeting Frequency.
3. Action Items

--------
1. Re-capturing the discussions from the IETF71.
Issue 1. How to resolve conflict between proxy/UA
  - Is 200 response in REGISTER request appropriate to tell
      UA that proxy is in charge of ACH?
  - Debate about what information it would carry.
     example.1: ACH is done at proxy.
     - Too vague.
    example.2: Forwarding to voice mail when busy is done on proxy.
     - Too specific, don't want to get into service.

  - Main use-case seems to be to prevent UA from doing 3xx on busy.
     Preventing UA from doing call-waiting may be there too (John).
     - Two flavors to tell the UA the same things.

  - Telling the UA not to execute ACH.
     Inform the UA about what ACH proxy is going to provide in hope of
     UA respecting the proxy.

  - Is it reasonable to take approach like this to address this issue?
     Francois is not convinced that the approach taken has a wide
      enough usage to define something specific like this. Need more
      use-cases.

- Francois suggests the use of config-fw
   - Debate on which profile type to use.
      - user seems to be the right profile.
   - Concern over dependency to config-fw.
      - Not sure if it ever gets deployed.

  - After some debate config-fw seems to be the way forward.

  - Francois is convinced that defining a parameters necessary
     to configure the proxy and same parameter to inform the UA
     is sufficient, how it be conveyed can be defined later
     (Config-FW, SOAP, XCAP etc.)

  - Chair stops the discussion as time was running out.

Meeting Frequency:
1. Will hold the meeting weekly until less is required.
    - Meeting time will be on Friday at 8:30-9:30 PST

Action Items:
1. Chair to write up a minutes.
2. Chair to get some feedback from Jonathan about what the
    design team should do with regards to configuring the proxy.
3. John to circulate some thoughts about the remaining issues
    so design team can use the ML to discuss them.

Regards
  Shida
_______________________________________________
BLISS mailing list
[email-masked]
https://www.ietf.org/mailman/listinfo/bliss