IETF Logo Mail Archive

Re: [Roll] DAO-Projection and new MOPs

"Pascal Thubert (pthubert)" <pthubert@cisco.com> Wed, 19 December 2018 07:12 UTC

Return-Path: <pthubert@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 E95C3130DEB for <roll@ietfa.amsl.com>; Tue, 18 Dec 2018 23:12:46 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -14.501
X-Spam-Level:
X-Spam-Status: No, score=-14.501 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIMWL_WL_MED=-0.001, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_HI=-5, SPF_PASS=-0.001, USER_IN_DEF_DKIM_WL=-7.5] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (1024-bit key) header.d=cisco.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 b4YleZguao4V for <roll@ietfa.amsl.com>; Tue, 18 Dec 2018 23:12:44 -0800 (PST)
Received: from alln-iport-8.cisco.com (alln-iport-8.cisco.com [173.37.142.95]) (using TLSv1.2 with cipher DHE-RSA-SEED-SHA (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id C3DFE130DEF for <roll@ietf.org>; Tue, 18 Dec 2018 23:12:42 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=cisco.com; i=@cisco.com; l=12767; q=dns/txt; s=iport; t=1545203562; x=1546413162; h=from:to:subject:date:message-id:references:in-reply-to: mime-version; bh=8EVwFNj9IkEG7XMA8ehFntQPmyQO2MK+c1GDkySZBl8=; b=A3ePJ7gDaY97xre6aZTejoZ/0JvfLMBO5jGXtDdb0DhUL5UICZ+4NX2M 4A05klofILiIcLt1zJ7soRLzCzQX56DQfGDkGftiDM6cS42tX2KDP/bYu 4FLfymOX+PDnPSTi7LJaNXEZ3PrJYeGd5Mwl3GwrAUtK/hx2n/lREP8Kj g=;
X-IronPort-Anti-Spam-Filtered: true
X-IronPort-Anti-Spam-Result: A0ADAABB7hlc/5tdJa1kGQEBAQEBAQEBAQEBAQcBAQEBAQGBUQQBAQEBAQsBggNmgQIng32IGYt8gg2JFYhshVuBewsBARgBCoFUgnUCF4JNIjQJDQEDAQECAQECbRwMhTwBAQEBAwEBIUsXBAIBCBEEAQEoAwICAh8GCxQJCAIEE4MiAYEdTAMVD6Y+gS+FQIJHDYIYBYw/F4FAP4E4H4JMgldHAQECgUODJDGCJgKPPpE+MwkCji6DMRiRVo9SigMCERSBJx84gVZwFTsqAYJBixyFP0ExjmcBAQ
X-IronPort-AV: E=Sophos;i="5.56,371,1539648000"; d="scan'208,217";a="214779094"
Received: from rcdn-core-4.cisco.com ([173.37.93.155]) by alln-iport-8.cisco.com with ESMTP/TLS/DHE-RSA-AES256-GCM-SHA384; 19 Dec 2018 07:12:41 +0000
Received: from XCH-ALN-005.cisco.com (xch-aln-005.cisco.com [173.36.7.15]) by rcdn-core-4.cisco.com (8.15.2/8.15.2) with ESMTPS id wBJ7Ce8D014101 (version=TLSv1.2 cipher=AES256-SHA bits=256 verify=FAIL) for <roll@ietf.org>; Wed, 19 Dec 2018 07:12:41 GMT
Received: from xch-rcd-001.cisco.com (173.37.102.11) by XCH-ALN-005.cisco.com (173.36.7.15) with Microsoft SMTP Server (TLS) id 15.0.1395.4; Wed, 19 Dec 2018 01:12:39 -0600
Received: from xch-rcd-001.cisco.com ([173.37.102.11]) by XCH-RCD-001.cisco.com ([173.37.102.11]) with mapi id 15.00.1395.000; Wed, 19 Dec 2018 01:12:40 -0600
From: "Pascal Thubert (pthubert)" <pthubert@cisco.com>
To: Routing Over Low power and Lossy networks <roll@ietf.org>
Thread-Topic: [Roll] DAO-Projection and new MOPs
Thread-Index: AQHUimiXEKsU4tniOU6pS6xXVR2aEKWCoHfQgAERqYD//76Bg4AA6UwA///bRUCAAcWjAP//xM5r
Date: Wed, 19 Dec 2018 07:12:39 +0000
Message-ID: <ACC29967-AFD4-4F8F-818F-8EB659166553@cisco.com>
References: <CAO0Djp0wiHUg15SfLzqXRF6Ko9JBbeL7C9CLZ6HRXcNxf+=Gew@mail.gmail.com> <0cb3313f79eb475090937a932b793efc@XCH-RCD-001.cisco.com> <16712.1545069107@localhost> <6811D20F-DC62-4E16-86EE-684BD288E2CF@cisco.com> <982B626E107E334DBE601D979F31785C5DD4D8E0@BLREML503-MBX.china.huawei.com> <a472122b1597405c9d8519c6b4737baf@XCH-RCD-001.cisco.com>, <CADnDZ88x5VN3dtbAVJ24JMbzrVsOpZpoio6CyLjruSxuWg6J2Q@mail.gmail.com>
In-Reply-To: <CADnDZ88x5VN3dtbAVJ24JMbzrVsOpZpoio6CyLjruSxuWg6J2Q@mail.gmail.com>
Accept-Language: fr-FR, en-US
Content-Language: fr-FR
X-MS-Has-Attach:
X-MS-TNEF-Correlator:
x-ms-exchange-transport-fromentityheader: Hosted
Content-Type: multipart/alternative; boundary="_000_ACC29967AFD44F8F818F8EB659166553ciscocom_"
MIME-Version: 1.0
X-Outbound-SMTP-Client: 173.36.7.15, xch-aln-005.cisco.com
X-Outbound-Node: rcdn-core-4.cisco.com
Archived-At: <https://mailarchive.ietf.org/arch/msg/roll/Bu2QVoiKH6HRkOBlhwKzJd7ciYE>
Subject: Re: [Roll] DAO-Projection and new MOPs
X-BeenThere: roll@ietf.org
X-Mailman-Version: 2.1.29
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: Wed, 19 Dec 2018 07:12:47 -0000

Hello Abdussalam

We do care about backwards compatibility. And we do not change RFCs. What we do is publish new RFCs the supersede the old for new devices in a spirit of maintaining maximum compatibility with old devices.

Regards,

Pascal

Le 19 déc. 2018 à 05:45, Abdussalam Baryun <abdussalambaryun@gmail.com<mailto:abdussalambaryun@gmail.com>> a écrit :



On Tue, Dec 18, 2018 at 9:42 AM Pascal Thubert (pthubert) <pthubert@cisco.com<mailto:pthubert@cisco.com>> wrote:
All for it. What do others think?

I think I posted a message before months about this MOP problem but no reply from the list, but now seems there started a discussion, but yes the MOP should be more than 3 bit. I suggest modifying that RFC that specifies 3 bits, I don't support extending but changing.


> -----Original Message-----
> From: Roll <roll-bounces@ietf.org<mailto:roll-bounces@ietf.org>> On Behalf Of Rahul Arvind Jadhav
> Sent: mardi 18 décembre 2018 04:52
> To: Routing Over Low power and Lossy networks <roll@ietf.org<mailto:roll@ietf.org>>
> Subject: Re: [Roll] DAO-Projection and new MOPs
>
> I'm wondering apart from MOP extension, it would be nice to have capability
> flags in DIO.
> 1. Capabilities field can work with ext-MOP to handshake additional
> capabilities ..
> 2. Even leaf nodes can understand capabilities ... unlike MOP which is relevant
> only to routers.
> Capabilities may be optional to support unlike MOP which is mandatory to be
> supported if the node is to be a 6LR in the instance.
>
>
> > -----Original Message-----
> > From: Roll [mailto:roll-bounces@ietf.org<mailto:roll-bounces@ietf.org>] On Behalf Of Pascal Thubert
> > (pthubert)
> > Sent: 18 December 2018 01:27
> > To: Routing Over Low power and Lossy networks <roll@ietf.org<mailto:roll@ietf.org>>
> > Subject: Re: [Roll] DAO-Projection and new MOPs
> >
> > I agree Michael
> >
> > Trouble is that there is no room left in MOP space (3 bits). We’ll
> > soon need to define a value to mean extended.
> >
> >
> > Regards,
> >
> > Pascal
> >
> > > Le 17 déc. 2018 à 18:52, Michael Richardson <mcr+ietf@sandelman.ca<mailto:mcr%2Bietf@sandelman.ca>>
> > > a
> > écrit :
> > >
> > >
> > > I strongly believe that we should have a specific new MOP:
> > >  "Non-storing with DAO-project"
> > >
> > > --
> > > Michael Richardson <mcr+IETF@sandelman.ca<mailto:mcr%2BIETF@sandelman.ca>>, Sandelman Software
> > Works
> > > -= IPv6 IoT consulting =-
> > >
> > >
> > >
> > > _______________________________________________
> > > Roll mailing list
> > > Roll@ietf..org<mailto:Roll@ietf.org>
> > > https://www.ietf.org/mailman/listinfo/roll
> > _______________________________________________
> > Roll mailing list
> > Roll@ietf.org<mailto:Roll@ietf.org>
> > https://www.ietf.org/mailman/listinfo/roll
> _______________________________________________
> Roll mailing list
> Roll@ietf.org<mailto:Roll@ietf.org>
> https://www.ietf.org/mailman/listinfo/roll
_______________________________________________
Roll mailing list
Roll@ietf.org<mailto:Roll@ietf.org>
https://www.ietf.org/mailman/listinfo/roll
_______________________________________________
Roll mailing list
Roll@ietf.org<mailto:Roll@ietf.org>
https://www.ietf.org/mailman/listinfo/roll

v2.23.0 | Report a Bug | By Email