[Rest] Draft-Minutes: BLISS-REST 2009.02.06

[Shida Schubert]

All;

  I sincerely apologize for my belated action to
send this minutes. A really bad form of influenza
has been going around in Japan, and I caught it
over the weekend, making me literally crippled
for the last few days.

  I do want to thank everybody who attended the
teleconference, thank you.

  Anyhow, here is the minutes.. Please send in
any comments by Friday night. I will send out
the minutes to the BLISS ML on Saturday.

Minutes:
  Meeting Date: 2009.02.06
  Note-taker: Shida Schubert
  Attendees:
    Andrew
    Christien
    Kemo
    Salvatore
    Sanjay
    Simon
    Shida
    Theo

1. Debate about the scoping of the REST-BLISS activity.
   - Need to distinguish from XCAP.
     - Chair asked the motivation behind what Nokia is doing with  
regards
        to XCAP/HTTP+CPL and the background behind Marku's comment.

     - Kemo explained that Markus's comment was based on the
        requirements draft.
        draft-zourzouvillys-bliss-ach-config-requirements

     - Kemo further went on to explain that in the req draft,  
something like
        time based policy etc. was being discussed.
     - Based on the req, if Common Policy based ruleset is necessary,
        it's already defined in 3GPP or may be something like CPL + HTTP
        may be considered?
    >  Kemo suggested that if policy based ruleset is to be considered,
         the design team should look at the ongoing work in 3GPP..

   - Even if REST approach is taken, there is still a need to identify  
the
     resources available for alteration.
   - Salvatore agreed and added the need to define syntax of the
      resources.

   - Simon pointed out the following points about adopting REST like
     approach as it has been debated in XCON.
      > Application level error codes and transport level error codes,
         and where error codes are to be sent need to be carefully  
considered
      > Can simply use HTTP error + body with error indication

      > Debate on why use REST? XCAP?
       - Some comments on how they are pretty much the same things.

 > Sanjay asked if we are designing SIP-REST general framework.
   > Shida explained that at the last meeting, as part of the scope of  
BLISS
      WG, BLISS will not design a general framework and focus only on  
the
      use-cases of ACH but do not limit the extensibility and further  
usage.

 > It was agreed that we need use-cases/requirements
   > Sanjay asked if we want to gather use-cases for anything or ACH?
    > Shida suggests to open up for anything.
    > Andrew argued that that we should focus on ACH only.
      > Shida agress.

 > Debate on the current requirements draft.
        draft-zourzouvillys-bliss-ach-config-requirements
  > Has a lot in there..
   > Theo agreed, and explained that it was because it included
     everything people expressed for its potential uses.
   > It was pointed out that by presenting the draft, we were able
      to narrow the scope of this work a tad.

Conclusion: We need use-cases/requirements. Especially use-cases
beside what's mentioned in the ACH draft.

** Action Plan ***
  > Each will go back and share their findings on the list.

** Next Meeting ***
  > Tentatively set for Feb 20th 14:00GMT - 15:00GMT.

Many Thanks
   Shida 
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://bliss-ietf.org/pipermail/rest_bliss-ietf.org/attachments/20090211/43ba0a45/attachment-0001.html>