Re: [Roll] FW: New Version Notification for draft-thubert-6lo-routing-dispatch-04.txt

"Timothy J. Salo" <salo@saloits.com> Tue, 07 July 2015 21:01 UTC

Return-Path: <salo@saloits.com>
X-Original-To: roll@ietfa.amsl.com
Delivered-To: roll@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 900501A90B6; Tue, 7 Jul 2015 14:01:06 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.911
X-Spam-Level:
X-Spam-Status: No, score=-1.911 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, SPF_PASS=-0.001, T_RP_MATCHES_RCVD=-0.01] autolearn=ham
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id CempQlKuOAjc; Tue, 7 Jul 2015 14:01:04 -0700 (PDT)
Received: from mail.saloits.com (saloits.com [208.42.140.127]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 752E91A90DD; Tue, 7 Jul 2015 14:01:04 -0700 (PDT)
Received: from [192.168.63.62] (173-11-44-141-Minnesota.hfc.comcastbusiness.net [173.11.44.141]) by mail.saloits.com (8.14.4/8.14.3) with ESMTP id t67L11Ue017694; Tue, 7 Jul 2015 16:01:02 -0500
Message-ID: <559C3E04.40702@saloits.com>
Date: Tue, 07 Jul 2015 16:00:52 -0500
From: "Timothy J. Salo" <salo@saloits.com>
User-Agent: Mozilla/5.0 (Windows NT 6.1; WOW64; rv:31.0) Gecko/20100101 Thunderbird/31.7.0
MIME-Version: 1.0
To: Routing Over Low power and Lossy networks <roll@ietf.org>, "6tisch@ietf.org" <6tisch@ietf.org>
References: <20150630165644.26795.43642.idtracker@ietfa.amsl.com> <E045AECD98228444A58C61C200AE1BD849F044E4@xmb-rcd-x01.cisco.com>
In-Reply-To: <E045AECD98228444A58C61C200AE1BD849F044E4@xmb-rcd-x01.cisco.com>
Content-Type: text/plain; charset=windows-1252; format=flowed
Content-Transfer-Encoding: 7bit
Archived-At: <http://mailarchive.ietf.org/arch/msg/roll/gm4m56E_-3ibXmJ_LVBlQUeT89o>
Subject: Re: [Roll] FW: New Version Notification for draft-thubert-6lo-routing-dispatch-04.txt
X-BeenThere: roll@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
Reply-To: Routing Over Low power and Lossy networks <roll@ietf.org>
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: <https://mailarchive.ietf.org/arch/browse/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: Tue, 07 Jul 2015 21:01:06 -0000

> Please consider those options, and come discuss them at 6Lo:
>
>        Option 1 considers that a network where this specification applies
>        is physically separate from a network where the Mesh Header
>        defined in [RFC4944] is used.  With that assumption, the Mesh
>        Header dispatch space can be reused.

How is this configured?  Does it require manual configuration?
Or, can it be reliably detected automatically?

-tjs