Re: [Roll] WG call to adopt draft-brandt-roll-rpl-applicability-home-building-03

Abdussalam Baryun <abdussalambaryun@gmail.com> Thu, 21 February 2013 19:37 UTC

Return-Path: <abdussalambaryun@gmail.com>
X-Original-To: roll@ietfa.amsl.com
Delivered-To: roll@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 1B8B521F8F23 for <roll@ietfa.amsl.com>; Thu, 21 Feb 2013 11:37:58 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -3.544
X-Spam-Level:
X-Spam-Status: No, score=-3.544 tagged_above=-999 required=5 tests=[AWL=0.055, BAYES_00=-2.599, RCVD_IN_DNSWL_LOW=-1]
Received: from mail.ietf.org ([64.170.98.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id miRSyNrE24fu for <roll@ietfa.amsl.com>; Thu, 21 Feb 2013 11:37:57 -0800 (PST)
Received: from mail-da0-f46.google.com (mail-da0-f46.google.com [209.85.210.46]) by ietfa.amsl.com (Postfix) with ESMTP id 9532E21F8F13 for <roll@ietf.org>; Thu, 21 Feb 2013 11:37:57 -0800 (PST)
Received: by mail-da0-f46.google.com with SMTP id p5so4243200dak.19 for <roll@ietf.org>; Thu, 21 Feb 2013 11:37:57 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:x-received:in-reply-to:references:date:message-id :subject:from:to:cc:content-type; bh=J0Wo6cBOjmjeI8FoSKEOS95ZN8DxKmnaFnxM0s/igcU=; b=DG+TznEwhUO2BwrVJwpd2EIbh6x2Dx/3pbKprj76oggXY2+Y0IUgIMjgHw2c5n11Ne 7y+LJy1rSrh2e6Lr/HRK03mzHDIWprSpinL96BKmP1OlAb24eE5/X0hpofbLTeZVnfli W7TU+q7EMO20zyllvorunHc9cZUXYGcLVz1pQ5rPJgkLcZiUMf6odh8TlM5tn602cinf TJAGtN5DA4bPRXcka7roECUU6Jfr3FwEGIni4oWUcTjspoRJp7asycFbdXiKIsdN/w4t GZ674iYng7WLfnzWtwRZXC+8GT+y1GWIrM3nLBQpS6KVZ7UQQpHafWl2DGW6AUG+xgwY mD8g==
MIME-Version: 1.0
X-Received: by 10.68.28.194 with SMTP id d2mr9767396pbh.215.1361475477389; Thu, 21 Feb 2013 11:37:57 -0800 (PST)
Received: by 10.68.33.132 with HTTP; Thu, 21 Feb 2013 11:37:57 -0800 (PST)
In-Reply-To: <CD4BA525.1E3E5%d.sturek@att.net>
References: <26596.1361470574@sandelman.ca> <CD4BA525.1E3E5%d.sturek@att.net>
Date: Thu, 21 Feb 2013 20:37:57 +0100
Message-ID: <CADnDZ891sEYce1GPQqHk_ufva=JN2uX7h0WN+Q9_HZCSN01Kvw@mail.gmail.com>
From: Abdussalam Baryun <abdussalambaryun@gmail.com>
To: Don Sturek <d.sturek@att.net>
Content-Type: text/plain; charset="ISO-8859-1"
Cc: roll@ietf.org
Subject: Re: [Roll] WG call to adopt draft-brandt-roll-rpl-applicability-home-building-03
X-BeenThere: roll@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: Routing Over Low power and Lossy networks <roll.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/roll>, <mailto:roll-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/roll>
List-Post: <mailto:roll@ietf.org>
List-Help: <mailto:roll-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/roll>, <mailto:roll-request@ietf.org?subject=subscribe>
X-List-Received-Date: Thu, 21 Feb 2013 19:37:58 -0000

Hi Don,

IMHO, I don't think the draft is about interoperability, nor
commercial issues. The draft is an applicability draft, it helps users
to use the protocol in such environment or applications,

AB

On 2/21/13, Don Sturek <d.sturek@att.net> wrote:
> Hi Michael,
>
> Having implemented and certified 6 vendor solutions using ROLL RPL in
> ZigBee IP, I doubt very seriously that this is true:
>
> "......because these are questions that need to be
> answered if we are going to have interoperability between muyltiple
> vendors without resorting to yet another level of vendor forums)"
>
> It would be best to keep the scope of the applicability statement to just
> RPL P2P, not add assumptions on the use of outside RFCs/drafts and let
> commercial groups complete certification by choosing configuration
> parameters that address their needs.
>
> I would doubt we are going to get to a place where an ad hoc group of
> vendors are going to pick up 6LoWPAN, 6LoWPAN-ND, ROLL RPL, ROLL RPL P2P,
> ROLL Mr. HOF, etc. ....  ,   implement all these and find their solutions
> are all interoperable.   Just looking at all the configuration options in
> these various drafts, it is unlikely for interoperability to just happen
> (ignoring for a minute the security bootstrapping topic which has its own
> set of complications)
>
> Don