Re: [SAM] draft-kolberg-sam-baseline-protocol-00

["John Buford" <[e-mail]>]

I think that the API ID could be adopted as an RG work item by itself, and
the section in the baseline document could focus on how the API works
specifically with the RELOAD extensions we are describing.

John


  _____  

From: [e-mail] [mailto:[e-mail]] On Behalf Of
Gustavo Carneiro
Sent: Thursday, April 08, 2010 8:37 AM
To: [e-mail]
Subject: Re: [SAM] draft-kolberg-sam-baseline-protocol-00




On Thu, Apr 8, 2010 at 10:38 AM, Dr Mario Kolberg <[e-mail]> wrote:


Dear Gustavo,

many thanks for your comments. 



Another not so clear item is how the API in Sec. 5 articulates with Sec. 6.
Sec.6 starts like this:

   In this document we define messages for hybrid overlay multicast
   tree creation...


I get the feeling this used to be a separate draft that was converted to a
section of another draft.  I suppose that the Protocol described is
triggered by API calls of the Sec. 5 API, but I get the feeling I am
guessing what should be explicitly stated in the document.  In that sense,
draft-waehlisch-sam-common-api-02 (Fig. 2) is clearer.



Yes section 5 is the API to the application, whereas section 6 describes the
API between nodes. And yes this draft is based on a number of previous
drafts. The aim is to align them and to form a base document for the WG. I
accept there is still some work to be done.



OK, that is understandable in the first versions.

Still I was wondering if the plan is for the sam-common-api will continue to
evolve alongside sam-baseline-protocol, or whether it will be merged into
sam-baseline-protocol.
 
Many thanks for your answers (Matthias as well).

Regards,

-- 
Gustavo J. A. M. Carneiro
INESC Porto, UTM, WiN, http://win.inescporto.pt/gjc
"The universe is always one step beyond logic." -- Frank Herbert