Re: [SAM] draft-kolberg-sam-baseline-protocol-00
Matthias Waehlisch <waehlisch@ieee.org> Thu, 08 April 2010 03:48 UTC
Return-Path: <waehlisch@ieee.org>
X-Original-To: sam@core3.amsl.com
Delivered-To: sam@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id 9223B3A68A5 for <sam@core3.amsl.com>; Wed, 7 Apr 2010 20:48:59 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -99.649
X-Spam-Level:
X-Spam-Status: No, score=-99.649 tagged_above=-999 required=5 tests=[BAYES_50=0.001, HELO_EQ_DE=0.35, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([64.170.98.32]) by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id fDPwamg6tZ2d for <sam@core3.amsl.com>; Wed, 7 Apr 2010 20:48:58 -0700 (PDT)
Received: from mail2.rz.htw-berlin.de (mail2.rz.htw-berlin.de [141.45.10.102]) by core3.amsl.com (Postfix) with ESMTP id 343C43A6827 for <sam@irtf.org>; Wed, 7 Apr 2010 20:48:58 -0700 (PDT)
Envelope-to: sam@irtf.org
Received: from adsl-76-231-184-62.dsl.pltn13.sbcglobal.net ([76.231.184.62] helo=mw-thinkpad) by mail2.rz.htw-berlin.de with esmtpsa (TLSv1:RC4-MD5:128) (Exim 4.68 (FreeBSD)) (envelope-from <waehlisch@ieee.org>) id 1Nzijd-0002Ej-Gg; Thu, 08 Apr 2010 05:48:54 +0200
Date: Wed, 07 Apr 2010 20:48:45 -0700
From: Matthias Waehlisch <waehlisch@ieee.org>
To: Gustavo Carneiro <gjcarneiro@gmail.com>
In-Reply-To: <y2wa467ca4f1004071054v35602b3axacd6b774e16da524@mail.gmail.com>
Message-ID: <Pine.WNT.4.64.1004071958180.5636@mw-thinkpad>
References: <y2wa467ca4f1004071054v35602b3axacd6b774e16da524@mail.gmail.com>
X-X-Sender: mw@mail2.rz.fhtw-berlin.de
MIME-Version: 1.0
Content-Type: TEXT/PLAIN; charset="US-ASCII"
X-HTW-SPAMINFO: this message was scanned by eXpurgate (http://www.eleven.de)
Cc: sam@irtf.org
Subject: Re: [SAM] draft-kolberg-sam-baseline-protocol-00
X-BeenThere: sam@irtf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: "For use by members of the Scalable Adaptive Multicast \(SAM\) RG" <sam.irtf.org>
List-Unsubscribe: <http://www.irtf.org/mailman/listinfo/sam>, <mailto:sam-request@irtf.org?subject=unsubscribe>
List-Archive: <http://www.irtf.org/mail-archive/web/sam>
List-Post: <mailto:sam@irtf.org>
List-Help: <mailto:sam-request@irtf.org?subject=help>
List-Subscribe: <http://www.irtf.org/mailman/listinfo/sam>, <mailto:sam-request@irtf.org?subject=subscribe>
X-List-Received-Date: Thu, 08 Apr 2010 03:48:59 -0000
Hi Gustavo, many thanks for your valuable feedback! Please see my reply inline. On Wed, 7 Apr 2010, Gustavo Carneiro wrote: > I am trying to understand draft-kolberg-sam-baseline-protocol-00 > > One thing that confuses me is in Sec. 5. Group Management API. > First it says, > > While native multicast is bound to IP addresses, ALM uses arbitrary > strings as multicast names, which will be mapped to the overlay > identifier space. > > The aim of this API is to implement group-oriented data communication > independent of the underlying distribution technologies. > > But then the API described is based on Address types, which are described > as: > > Address is any address structure suitable with respect to the > technology available at the host. This may be an IPv4 or an IPv6 > address, or any overlay identifier. > > So it seems that the Group Management API does not work with > high-level abstract identifiers, it already works with > transport-specific identifiers. > Yes, this is misleading presented in the current version. We updated this to mention explicit naming using the URI scheme with respect to draft-waehlisch-sam-common-api. However, this update has not been published yet, as we want to add some further extensions in the draft-kolberg-sam-baseline-protocol. [...] > And what is exactly the relationship between > draft-waehlisch-sam-common-api-02 and > draft-kolberg-sam-baseline-protocol-00. They were published almost at > the same time (for the meeting?); are they competing proposals? > No, they are not competing proposals. From the perspective of draft-waehlisch-sam-common-api the baseline protocol is a special use case for the common API. In contrast, from the perspective of draft-kolberg-sam-baseline-protocol the common API fills the gap to develop hybrid group communication applications. Thanks matthias -- Matthias Waehlisch . FU Berlin, Inst. fuer Informatik, AG CST . Takustr. 9, D-14195 Berlin, Germany .. mailto:waehlisch@ieee.org .. http://www.inf.fu-berlin.de/~waehl :. Also: http://inet.cpt.haw-hamburg.de .. http://www.link-lab.net
- [SAM] draft-kolberg-sam-baseline-protocol-00 Gustavo Carneiro
- Re: [SAM] draft-kolberg-sam-baseline-protocol-00 Matthias Waehlisch
- Re: [SAM] draft-kolberg-sam-baseline-protocol-00 Dr Mario Kolberg
- Re: [SAM] draft-kolberg-sam-baseline-protocol-00 Gustavo Carneiro
- Re: [SAM] draft-kolberg-sam-baseline-protocol-00 Matthias Waehlisch
- Re: [SAM] draft-kolberg-sam-baseline-protocol-00 John Buford