Below is the minutes from ACH design team meeting
two weeks back.
Meeting Date/Time
---------------------------
2008.04.04 08:30PST-09:30PST
Attendees
---------------------------
- Francois Audet
- John Elwell
- Martin Dolly
- Shida Schubert
- John Zhao
Agenda: --------------------
1. Recapturing the remaining discussions from the IETF 71.
2. Action Items
3. Next meeting schedule
--------
1. Recapturing the remaining discussions from the IETF71.
- Issue 3 (Enumerating the condition to status code)
Debate on what the design team would do in regards to this.
- Enumerate the condition and relevant status codes.
- Busy, Reject, DND, Not available.
If one wants to allude the action of forwarding it to a
voicemail, is it a different condition?
- No. Probably don't want to do this, leave it to proxy.
- If UA is initiating ACH it probably uses 3xx, so there is not
much we need to define.
Conclusion:
- Send the list of conditions that we believe need to be
addressed to the BLISS and get the feedback from the WG,
once we have the final list, assign appropriate status codes.
- Issue 5 (Scope of the response codes)
There are 3 cases
- Case where one sends 6xx and that's the end of it.
- Case where UA sends 4xx and leave it to proxy.
- Case where UA sends 302 to forward the call to voicemail etc.
- Debate on what the design team would do in regards to this.
- Recommend the usage of 6xx and discourage the use of 6xx for
cases where 4xx is sufficient.
- Explain what it means to use 6xx, it's ramification and
discourage the use of 6xx.
Conclusion:
- Recommend the use of 6xx only when the condition applies to
all the branches, discourage the use otherwise and recommend
the alternatives using 4xx if possible for situation where 6xx
is currently used.
- Also document the implication of 6xx usage.
- DND
Debate over DND
- Two flavours.
1. In call rejection (DND).
2. Pre-configured rejection (DND).
- Need to document the two flavors.
Conclusion;
- Capture the 2 flavours of DND in the document.
- Documentations
Debate on documentation method
- Whether to start a new document or to include the recommendations
in the analysis document.
Conclusion:
- Will include the recommendations into the analysis document
for now.
- When ready, we can either split the document or change
the analysis document to BCP document.
2. Action Items
- John will revise the documents based on the feedback from last
2 teleconf.
- Continue the discussions on the design team list on any of
the unresolved issues.
- Post the questions regarding the conditions design team is
to address to the BLISS list. (John?)
3. Next meeting schedule
04/18/2008 8:30-9:30 PST
Regards
Shida
_______________________________________________
BLISS mailing list
[email protected]
https://www.ietf.org/mailman/listinfo/bliss
