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

Abdussalam Baryun <abdussalambaryun@gmail.com> Thu, 21 February 2013 22:51 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 8EBF221E803F for <roll@ietfa.amsl.com>; Thu, 21 Feb 2013 14:51:06 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -3.545
X-Spam-Level:
X-Spam-Status: No, score=-3.545 tagged_above=-999 required=5 tests=[AWL=0.054, 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 NBn0Q3mB4bpO for <roll@ietfa.amsl.com>; Thu, 21 Feb 2013 14:51:05 -0800 (PST)
Received: from mail-pb0-f54.google.com (mail-pb0-f54.google.com [209.85.160.54]) by ietfa.amsl.com (Postfix) with ESMTP id 0C84C21E803D for <roll@ietf.org>; Thu, 21 Feb 2013 14:51:02 -0800 (PST)
Received: by mail-pb0-f54.google.com with SMTP id rr4so28299pbb.13 for <roll@ietf.org>; Thu, 21 Feb 2013 14:51:01 -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=4W0LDr9J7Q2ltv8FH6XmC8YvzypBuRrrL0ql3ds0IEo=; b=hX/Ro5zlIYO4m7/NGgHhMe+//h9XTHCLhHX3MltwZ7U9SFAfRmjsrPQYnJVGu+NAUD iTB4BI6fX3sNac3FpDki2jyn5+WwrjjlOgqqq5/EME4ZYnXSzEDJ6yQIbMEnuKz41r+r NLEbwVePZfCYB1LSA74WyyFjNGNnlx4NNL3Ho0H1+tTbPvlhhkbx6kvTj/XgpoJHLRVh w4wCj7yDe43yBcoDJyTLhmJBCZi9zeObcYahj3qmiCNbNizKgHlGrUUaNa0aXKdMccPo HpdLehyUq/ine5MOzxjiBpC19YgpbRJdsVtDLv6N00os/ute8smK+dv63tQH6XiaIA6u ZBlg==
MIME-Version: 1.0
X-Received: by 10.66.220.227 with SMTP id pz3mr535805pac.190.1361487061872; Thu, 21 Feb 2013 14:51:01 -0800 (PST)
Received: by 10.68.33.132 with HTTP; Thu, 21 Feb 2013 14:51:01 -0800 (PST)
In-Reply-To: <21952.1361479420@sandelman.ca>
References: <26596.1361470574@sandelman.ca> <CD4BA525.1E3E5%d.sturek@att.net> <CADnDZ891sEYce1GPQqHk_ufva=JN2uX7h0WN+Q9_HZCSN01Kvw@mail.gmail.com> <21952.1361479420@sandelman.ca>
Date: Thu, 21 Feb 2013 23:51:01 +0100
Message-ID: <CADnDZ881Fm8FxF95XmK+7uwvRNJkyaj5kteaikFxYgNBrMZLWw@mail.gmail.com>
From: Abdussalam Baryun <abdussalambaryun@gmail.com>
To: Michael Richardson <mcr+ietf@sandelman.ca>
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 22:51:16 -0000

I agree with situation interoperability for the doc as you state in
your message, however, I ment that the interoperability among
different implemetation of the protocol. Will you include that in
draft as well?

AB

On 2/21/13, Michael Richardson <mcr+ietf@sandelman.ca> wrote:
>
>>>>>> "Abdussalam" == Abdussalam Baryun <abdussalambaryun@gmail.com>
>>>>>> writes:
>     Abdussalam> IMHO, I don't think the draft is about interoperability,
>     Abdussalam> nor commercial issues. The draft is an applicability
>     Abdussalam> draft, it helps users to use the protocol in such
>     Abdussalam> environment or applications,
>
> If there is anything in the document which is not essential for
> interoperability then it can be removed from the document.
>
> RFC6550 and friends (including the 6lowpan and 6man things) have given
> us palette of options.  The purpose of this document is how to apply
> those options to a specific situation.  This document *MUST* explain
> what options *MUST* be present in a device in order to interoperate
> in the situation.  Given the real constraints in the devices involved,
> they can be manufactured with every available feature of the protocol,
> nor can we assume that we can turn them all on at the same time, and
> create as much state (==memory) as we want.
>
> --
> Michael Richardson <mcr+IETF@sandelman.ca>, Sandelman Software Works
> IETF ROLL WG co-chair.    http://datatracker.ietf.org/wg/roll/charter/
>
>