IETF Logo Mail Archive

Re: [Roll] draft-ietf-6man-rpl-routing-header-07

Jonathan Hui <jonhui@cisco.com> Tue, 20 December 2011 16:27 UTC

Return-Path: <jonhui@cisco.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 A8A4121F84CD for <roll@ietfa.amsl.com>; Tue, 20 Dec 2011 08:27:30 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -6.599
X-Spam-Level:
X-Spam-Status: No, score=-6.599 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, RCVD_IN_DNSWL_MED=-4]
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 Zarm0tplRXMS for <roll@ietfa.amsl.com>; Tue, 20 Dec 2011 08:27:30 -0800 (PST)
Received: from mtv-iport-4.cisco.com (mtv-iport-4.cisco.com [173.36.130.15]) by ietfa.amsl.com (Postfix) with ESMTP id 2F83821F8484 for <roll@ietf.org>; Tue, 20 Dec 2011 08:27:30 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=cisco.com; i=jonhui@cisco.com; l=687; q=dns/txt; s=iport; t=1324398450; x=1325608050; h=subject:mime-version:from:in-reply-to:date:cc: content-transfer-encoding:message-id:references:to; bh=b1lgwPZxc4W9mc2E9Ka3mcDQQLvz1hSCoGv4w39HcJc=; b=boTjLaEdzphUtdKwRMeCiyTXpzhearFhcKP7QKGbiRx6JScreXpI5dVF UxcmLxSJBZ1T+xWaCqjqxYPZDaPgw7m9Qu+GqXw8mBPZuOWLUfDyxmH3O 08K56pPcI3KPhf1Zxzn+NAxpNEK57FveTSzve9t61MOFGyv2WmZCD61mG k=;
X-IronPort-Anti-Spam-Filtered: true
X-IronPort-Anti-Spam-Result: Av0EAL228E6rRDoI/2dsb2JhbABDDqtygQWBcgEBAQMBEgEnPwULC0ZXBjWHWJhfAZ48iyljBIg3jEiReVg
X-IronPort-AV: E=Sophos;i="4.71,382,1320624000"; d="scan'208";a="21715504"
Received: from mtv-core-3.cisco.com ([171.68.58.8]) by mtv-iport-4.cisco.com with ESMTP; 20 Dec 2011 16:27:30 +0000
Received: from dhcp-128-107-155-213.cisco.com (dhcp-128-107-155-213.cisco.com [128.107.155.213]) by mtv-core-3.cisco.com (8.14.3/8.14.3) with ESMTP id pBKGRTYu002728; Tue, 20 Dec 2011 16:27:29 GMT
Mime-Version: 1.0 (Apple Message framework v1084)
Content-Type: text/plain; charset="us-ascii"
From: Jonathan Hui <jonhui@cisco.com>
In-Reply-To: <1076398681.709387.1324397661047.JavaMail.root@mail17.pantherlink.uwm.edu>
Date: Tue, 20 Dec 2011 08:27:29 -0800
Content-Transfer-Encoding: quoted-printable
Message-Id: <B28ACA7A-EBCD-426E-B9E3-F3979E8F7101@cisco.com>
References: <1076398681.709387.1324397661047.JavaMail.root@mail17.pantherlink.uwm.edu>
To: Mukul Goyal <mukul@uwm.edu>
X-Mailer: Apple Mail (2.1084)
Cc: roll <roll@ietf.org>
Subject: Re: [Roll] draft-ietf-6man-rpl-routing-header-07
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: Tue, 20 Dec 2011 16:27:30 -0000

Mukul,

As defined in the draft today, you cannot use a RPL routing header to cross RPL Instances.  My understanding is that roll-p2p-rpl makes use of local RPL instances.  Can you describe the issue you are concerned about?

--
Jonathan Hui

On Dec 20, 2011, at 8:14 AM, Mukul Goyal wrote:

> Jonathan
> 
> The IESG-approved draft refers to the RPL instance as the scope where the routing header can be used. How would this routing header be used for general source routing (across RPL instances) in an LLN? How would a node use this routing header if it wants to travel along a source route discovered using P2P-RPL?
> 
> Thanks
> Mukul
>

v2.23.0 | Report a Bug | By Email