Re: [Roll] [Anima] on the use of RPL without RPI (was Re: [6lo] Adaption of ROLL for mesh-under)

Brian E Carpenter <brian.e.carpenter@gmail.com> Fri, 14 April 2017 20:26 UTC

Return-Path: <brian.e.carpenter@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 AB499129AA8; Fri, 14 Apr 2017 13:26:40 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2
X-Spam-Level:
X-Spam-Status: No, score=-2 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, FREEMAIL_FROM=0.001, RCVD_IN_DNSWL_NONE=-0.0001, SPF_PASS=-0.001] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (2048-bit key) header.d=gmail.com
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 tdRZV9ebBRWh; Fri, 14 Apr 2017 13:26:39 -0700 (PDT)
Received: from mail-pg0-x243.google.com (mail-pg0-x243.google.com [IPv6:2607:f8b0:400e:c05::243]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 2A7D3129A97; Fri, 14 Apr 2017 13:26:39 -0700 (PDT)
Received: by mail-pg0-x243.google.com with SMTP id g2so17764941pge.2; Fri, 14 Apr 2017 13:26:39 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20161025; h=subject:to:references:cc:from:organization:message-id:date :user-agent:mime-version:in-reply-to:content-transfer-encoding; bh=iH98L8qtaW2AyaqWt9WwhXlO05iJMLGFQ9KwYT7vO8w=; b=guY68TuYosCqd49B8Lw9I5Dbxl8oFCtGDeVRsXOaEmnqqQYrPj9/aGUrbV8Aaa34// zkVvX+PmyR/UxjvpmBtIhw0B5kBc4dBO68qUoFMUHUUSWcRKwQR/CUAue/y8kQetOmH3 QSldxAobA85sUxwPFzL8zeyyiBJg91+qj+A1smAY9kG64UYvwJSMIGqciRU/mFNGy0Y1 9esj2U4RuDUWYzpBTJRWgCtBiUGqwF7Vf7aNlRsv515bX+Zlj/CmfR4AW6L0cVJlnxxh X+vWJpIv6sfHjbmEvc5bunPLNOGVLoD4RGDeltTGPrkWDNvRrqWb4iAFtpEBfo5AdAdC IN0w==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:subject:to:references:cc:from:organization :message-id:date:user-agent:mime-version:in-reply-to :content-transfer-encoding; bh=iH98L8qtaW2AyaqWt9WwhXlO05iJMLGFQ9KwYT7vO8w=; b=ordElpDf20QuxqrtkFIR6TSMEsNYgs6uimJAprmcrnoYCEtXGmmsFgOM4Q4BecsVPq 7TlVqTJa2K+nLQveFxKAIZNmnx/+X8lyQ/f/mGkJ7hjkJ4bkz4CrEuOXl3QasKHIGXVx gQQbTRf9ZXkLJ951ABIrcGIdV1tzTP8xs9QkGrqjwPFC+7I+6nfp/U0xrJmJxNSYSTBU H3e2sU9lUgS2kLoniSCB8fEEADPHCC2FvI9Bb+duUoWMqck/vP5qJ3203Z017UZtIXjg J0wopvfUGlkAxQVdRZzMAIJsvlffL11kGj7o9JHePhjdb1dDlSx1TrnYUHsTdaJocN+I c82w==
X-Gm-Message-State: AN3rC/5mXQzQhNRTGlfiYEfAm1J9uZZ60g14Aq85LEG6hisfDOnYwR36 7vZKOirSfpfDpQ==
X-Received: by 10.98.210.2 with SMTP id c2mr9008635pfg.83.1492201598679; Fri, 14 Apr 2017 13:26:38 -0700 (PDT)
Received: from ?IPv6:2406:e001:38c5:1:28cc:dc4c:9703:6781? ([2406:e001:38c5:1:28cc:dc4c:9703:6781]) by smtp.gmail.com with ESMTPSA id 74sm4739754pfn.102.2017.04.14.13.26.36 (version=TLS1_2 cipher=ECDHE-RSA-AES128-GCM-SHA256 bits=128/128); Fri, 14 Apr 2017 13:26:38 -0700 (PDT)
To: "Pascal Thubert (pthubert)" <pthubert@cisco.com>
References: <1491971619970.42705@ssni.com> <CD3480AD-3934-4C9E-B6F3-E399A32BACC8@tzi.org> <1491974218584.69073@ssni.com> <ae35261f3dac4a9fa123f33610bb9805@XCH-RCD-001.cisco.com> <15236.1492095258@obiwan.sandelman.ca> <6ce1718ab83342bcad9c19d6d9e96935@XCH-RCD-001.cisco.com> <6577.1492101395@obiwan.sandelman.ca> <07e8d178-0545-5fe1-75a6-ecad449565ae@gmail.com> <B8BA574A-EBC0-437A-BD0B-99C9E44C36D1@cisco.com>
Cc: Michael Richardson <mcr+ietf@sandelman.ca>, "roll@ietf.org" <roll@ietf.org>, "anima@ietf.org" <anima@ietf.org>
From: Brian E Carpenter <brian.e.carpenter@gmail.com>
Organization: University of Auckland
Message-ID: <89e0474e-3084-9eae-cdfa-3ae5b7aca65f@gmail.com>
Date: Sat, 15 Apr 2017 08:26:43 +1200
User-Agent: Mozilla/5.0 (Windows NT 6.1; WOW64; rv:45.0) Gecko/20100101 Thunderbird/45.8.0
MIME-Version: 1.0
In-Reply-To: <B8BA574A-EBC0-437A-BD0B-99C9E44C36D1@cisco.com>
Content-Type: text/plain; charset="utf-8"
Content-Transfer-Encoding: quoted-printable
Archived-At: <https://mailarchive.ietf.org/arch/msg/roll/PFItP_U5C8Ks85ubYNXgYSaxUj0>
Subject: Re: [Roll] [Anima] on the use of RPL without RPI (was Re: [6lo] Adaption of ROLL for mesh-under)
X-BeenThere: roll@ietf.org
X-Mailman-Version: 2.1.22
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: <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: Fri, 14 Apr 2017 20:26:41 -0000

Hi Pascal,

> Would ANIMA wish that ROLL publishes that doc?

I certainly can't speak for the WG, but to me it seems like an issue that
might arise for other use cases, so an answer from ROLL for the general
case seems to make sense.

   Brian
On 14/04/2017 19:28, Pascal Thubert (pthubert) wrote:
> Hello Brian
> 
> This is unspecified since prior to ACP there is always an RPI, thus the need to express it somewhere, which we did in the ANIMA spec; and the problem you raised has 2 sides.
> 
> Could be that nodes always expect an RPI and could be that they never do. Either way nodes may drop the packet in some default: case.
> 
> I think that what we have now at ANIMA works, and that a more complete specification would be useful for a more general case, explaining pro cons of using RPI and in which case mixed mode could work. Would ANIMA wish that ROLL publishes that doc?
> 
> Take care,
> 
> Pascal
> 
>> Le 13 avr. 2017 à 23:31, Brian E Carpenter <brian.e.carpenter@gmail.com> a écrit :
>>
>>> On 14/04/2017 04:36, Michael Richardson wrote:
>>> ...
>>> I also think we could in light of rfc2460bis renegotiation, argue for
>>> insertion of RPI header by the ACP without IPIP encapsulation :-)
>>
>> I wouldn't bet on that for a few more weeks yet. We do have a couple of
>> mitigations however:
>>
>> 1) Since the ACP is strictly using ULAs, we can assert that ACP packets
>> are not intended for the open Internet. It would in fact be tragic for
>> many reasons if an ACP packet "escaped".
>>
>> 2) Since the ACP will be based on IPsec/ESP, we can assert that breaking
>> IPsec/AUTH is not an issue.
>>
>> However, we would also need a story on PMTUD within the ACP.
>>
>>>> So all in all, considering the hassle of updating silicon along the
>>>> forwarding plane, I'd think that living without RPI is fine. Now if you
>>>> tell me that it is always going through software that is easy to
>>>> update, then why not?
>>>
>>> I think that this is the case.
>>
>> Updating the ACP code network-wide, in a large network, might not be so easy.
>> Ignorant question: what happens if only some RPL nodes support RPI?
>>
>>   Brian
>