Re: [SAM] [irsg] IRSG review for draft-irtf-samrg-sam-baseline-protocol-02

Michael Welzl <michawe@ifi.uio.no> Wed, 06 March 2013 13:35 UTC

Return-Path: <michawe@ifi.uio.no>
X-Original-To: sam@ietfa.amsl.com
Delivered-To: sam@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 9168721F88D1; Wed, 6 Mar 2013 05:35:14 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -100.989
X-Spam-Level:
X-Spam-Status: No, score=-100.989 tagged_above=-999 required=5 tests=[AWL=0.810, BAYES_00=-2.599, SARE_SUB_RAND_LETTRS4=0.799, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id HCBx0PZVUtpa; Wed, 6 Mar 2013 05:35:13 -0800 (PST)
Received: from mail-out4.uio.no (mail-out4.uio.no [IPv6:2001:700:100:10::15]) by ietfa.amsl.com (Postfix) with ESMTP id 4F6E321F8873; Wed, 6 Mar 2013 05:35:13 -0800 (PST)
Received: from mail-mx3.uio.no ([129.240.10.44]) by mail-out4.uio.no with esmtp (Exim 4.80.1) (envelope-from <michawe@ifi.uio.no>) id 1UDEUy-0008Fk-Ks; Wed, 06 Mar 2013 14:35:12 +0100
Received: from boomerang.ifi.uio.no ([129.240.68.135]) by mail-mx3.uio.no with esmtpsa (TLSv1:AES128-SHA:128) user michawe (Exim 4.80) (envelope-from <michawe@ifi.uio.no>) id 1UDEUy-00066x-04; Wed, 06 Mar 2013 14:35:12 +0100
Mime-Version: 1.0 (Apple Message framework v1283)
Content-Type: text/plain; charset=iso-8859-1
From: Michael Welzl <michawe@ifi.uio.no>
In-Reply-To: <51263DD8.6070600@informatik.haw-hamburg.de>
Date: Wed, 6 Mar 2013 14:35:10 +0100
Content-Transfer-Encoding: quoted-printable
Message-Id: <28367F2A-BEB5-439E-BD66-0FC5911644B2@ifi.uio.no>
References: <5125FFE7.6000601@informatik.haw-hamburg.de> <208D1ADA-57CA-459C-A2DE-A6AB63F0160E@ifi.uio.no> <51263DD8.6070600@informatik.haw-hamburg.de>
To: Thomas C. Schmidt <schmidt@informatik.haw-hamburg.de>
X-Mailer: Apple Mail (2.1283)
X-UiO-SPF-Received:
X-UiO-Ratelimit-Test: rcpts/h 11 msgs/h 3 sum rcpts/h 16 sum msgs/h 6 total rcpts 2547 max rcpts/h 20 ratelimit 0
X-UiO-Spam-info: not spam, SpamAssassin (score=-5.6, required=5.0, autolearn=disabled, RP_MATCHES_RCVD=-0.552, UIO_MAIL_IS_INTERNAL=-5, uiobl=NO, uiouri=NO)
X-UiO-Scanned: 427A6E41CC4542BAF7CFB56EF9C4D287F013A5C0
X-UiO-SPAM-Test: remote_host: 129.240.68.135 spam_score: -55 maxlevel 80 minaction 2 bait 0 mail/h: 3 total 1052 max/h 12 blacklist 0 greylist 0 ratelimit 0
X-Mailman-Approved-At: Wed, 06 Mar 2013 08:11:46 -0800
Cc: sam <sam@irtf.org>, Internet Research Steering Group <irsg@irtf.org>
Subject: Re: [SAM] [irsg] IRSG review for draft-irtf-samrg-sam-baseline-protocol-02
X-BeenThere: sam@irtf.org
X-Mailman-Version: 2.1.12
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/options/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: Wed, 06 Mar 2013 13:35:14 -0000

Hi,

Here's my review. This is an outsider review if there ever was one, as I know nothing about RELOAD...
so I just had to try to make sense of the document as good as I could - I hope my comments are useful anyway!

Here it goes...


General higher-level comments:

I found parts of the document very hard to read, sometimes wondered if this is really necessary.

In particular, P2PCast appears to be a rather complex algorithm which is "sort of" described here... I doubt that the description in the document will help most readers to really fully understand P2PCast, and I  wonder, is it necessary for this doc to try to really explain the algorithm (when, in doing so, it can really only go half-way anyway)? e.g., wouldn't it suffice to just keep the "Overview" (section 9.1) but then point to [P2PCAST] for further details, and just list the necessary facts? e.g., the JOIN procedure - do we have to know all these details here, isn't it enough to e.g. list the reorganisation messages by name and say that they're used in accordance with [P2PCAST]?

Another source of confusion: the Scribe algorithm description has some pseudocode that I wasn't able to parse (maybe it refers to RELOAD things?) Not all functions there seem to clearly relate to messages that were described earlier. Even more confusing, the P2PCast algorithm description doesn't have these pseudocode snippets, so the whole thing appears inconsistent. Should it be everywhere? Should it be removed? If it stays, some explanations are needed. It can't be up to the reader to guess what e.g. "invokeMessageHandler" does, right?? (section 8.7). In this particular section, I would also expect the text and/or pseudocode to somehow draw a relationship to "push" (listed in fig. 3), but that's not there... so what is this?

Structure: even if the two algorithms are only a part of the whole thing you define, the text going with them feels a bit like "we've set the stage, now we apply it - the messages you heard about before are used like this & that with this & that algorithm". That's fine! But it also gives the reader the feeling of that being "part 2", i.e. I think it should be at the end, if that makes sense.

I also think that it would be better to move the examples (section 12) to where you introduce the messages, the flow of which they illustrate. First I have to imagine what an "INVITE" message flow could look like, then I get complicated explanations of how INVITE is applied in an algorithm that I can't fully understand from this text anyway, and THEN I get a nice example illustrating an INVITE message flow... that's not very helpful for the reader I think.  e.g., when I read 7.2.3, I wondered why the "peer_id" of the source peer is even needed in the struct. By looking at the example, this would have become clear to me.

Speaking of the examples, what's the point of showing more peers than you actually use in the example? Okay, I can understand that perhaps you wanted to have the same number for all of them, but then you could still remove P3 because it seems that you never use P3 for anything in any of the examples.


Nits:

IANA Considerations: are you sure that there is nothing? e.g., how would a new algorithm code be assigned?   (section 11.4)
- btw, why is the section called "Algorithm Codes" but then the text talks about "Algorithm Types" ?

Some references (CASTRO2003, P2PCAST) need a space (I mean, " ") after their first appearance.

p10: "Here is a simplistic algorithm for forming..." => but what follows is not an algorithm description?

p 11 end of section 6: this ends with a colon, but no text following it... loks as if there is something missing here.

p11, sec 7.1, par 1: "*makes* the SAM framework *is*" seems to be broken English

7.2.1 par 2 line 2: "other Peers" => "other peers"

p13, session_key: "a well-known string **that**, when hashed ..."

7.2.3 par 2 remove "then" in "...(see below) is then sent."

p14 par below "JoinDecline" in the list of messages: "...until either *a* retry limit is reached ..."

p15 7.2.6 par 1: "before the expiration of the JoinAccept" => this stands out here, as a strange requirement to impose on the peer receiving JoinAccept. I think the only thing you can put here is a note that this message would have to be received by the other end before a timer expires, and say that the specifics of this timer are up to the algorithm (hm, are they? Or is this a RELOAD thing?).

p 16 7.2.8 par 1: "...receiving a JoinAccept message which *it* does not wish..."

sec 7.2.15: "that it has received" seems broken English here?

sec 7.2.18: priority: you only say that a node may ignore this field, but not what it should otherwise do - is this up to the algorithm, in which way are priorities handled?

p 22 sec 7.2.19 last par: "nodes which were forwarded the push message" - not sure this is correct English

caption of figure 3: Scibe => Scribe

sec 84 ", which will travel up the multicast tree and will stop at a node which has still children remaining" => ", from where it will travel up the multicast tree and stop at a node that still has children remaining"

sec 9.1 par1: "independent on" => "independent of"

sec 9.5 par 1: "Distregarding" => "Disregarding"
same par: "a bubble is created" => no clue what that's supposed to mean

sec 11.1 algorithm: paragraph - " ... multicast algorithm*s* can co-exist..."

sec 12.2 par 1: end with a "."

same in sec 12.4

and sentence 2 of 13.1


Have fun!!
Michael



On 21. feb. 2013, at 16:31, Thomas C. Schmidt wrote:

> Great Michael,
> 
> many thanks!
> 
> Cheers,
> 
> Thomas
> 
> On 21.02.2013 15:58, Michael Welzl wrote:
>> I'm no expert on any of this, but stand up and volunteer nevertheless...
>> 
>> Michael
>> 
>> 
>> On 21. feb. 2013, at 12:07, Thomas C. Schmidt wrote:
>> 
>>> Hi all,
>>> 
>>> SAMRG has completed work on
>>> 
>>>            Application Layer Multicast Extensions to RELOAD
>>>               draft-irtf-samrg-sam-baseline-protocol-02
>>> 
>>> http://tools.ietf.org/html/draft-irtf-samrg-sam-baseline-protocol-02
>>> 
>>> http://trac.tools.ietf.org/group/irtf/trac/ticket/54
>>> 
>>> We are soliciting IRSG reviews now. Please let me know if you can review this draft.
>>> 
>>> Thanks,
>>> 
>>> Thomas
>>> 
>>> --
>>> 
>>> Prof. Dr. Thomas C. Schmidt
>>> ° Hamburg University of Applied Sciences                   Berliner Tor 7 °
>>> ° Dept. Informatik, Internet Technologies Group    20099 Hamburg, Germany °
>>> ° http://www.haw-hamburg.de/inet                   Fon: +49-40-42875-8452 °
>>> ° http://www.informatik.haw-hamburg.de/~schmidt    Fax: +49-40-42875-8409 °
>> 
> 
> -- 
> 
> Prof. Dr. Thomas C. Schmidt
> ° Hamburg University of Applied Sciences                   Berliner Tor 7 °
> ° Dept. Informatik, Internet Technologies Group    20099 Hamburg, Germany °
> ° http://www.haw-hamburg.de/inet                   Fon: +49-40-42875-8452 °
> ° http://www.informatik.haw-hamburg.de/~schmidt    Fax: +49-40-42875-8409 °