IETF Logo Mail Archive

Re: [Roll] In what way is roll-unaware-leaves updating npdao?

"Pascal Thubert (pthubert)" <pthubert@cisco.com> Wed, 07 October 2020 08:18 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 EA8323A1642 for <roll@ietfa.amsl.com>; Wed, 7 Oct 2020 01:18:56 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -9.598
X-Spam-Level:
X-Spam-Status: No, score=-9.598 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, DKIM_VALID_EF=-0.1, RCVD_IN_MSPIKE_H3=0.001, RCVD_IN_MSPIKE_WL=0.001, SPF_PASS=-0.001, URIBL_BLOCKED=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 header.b=bwXhAG9E; dkim=pass (1024-bit key) header.d=cisco.onmicrosoft.com header.b=cAE9MBtV
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 rPimrTekybU3 for <roll@ietfa.amsl.com>; Wed, 7 Oct 2020 01:18:55 -0700 (PDT)
Received: from alln-iport-5.cisco.com (alln-iport-5.cisco.com [173.37.142.92]) (using TLSv1.2 with cipher DHE-RSA-SEED-SHA (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 9BFAE3A163B for <roll@ietf.org>; Wed, 7 Oct 2020 01:18:55 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=cisco.com; i=@cisco.com; l=1014; q=dns/txt; s=iport; t=1602058735; x=1603268335; h=from:to:subject:date:message-id:references:in-reply-to: content-transfer-encoding:mime-version; bh=yUByv6squiz8eoNdG2yiwP5YyXxd/+c4fC+7uIOXMRU=; b=bwXhAG9EsPLbq8la+WyvTOr/sUpeSqQ0xqJgy+HOV9FWA1/Y+D2mjTwk Jex6DmFcwWeLLgRe3DjTISs0E3GiSA/U5hD1g0MRf1fQ3ldvCovIB3yyV WLj8Vn++Esjdu14Qkjxxgqc9+gADOBmdBxs8YyGEW9Bp3BkNYuTb/Ty9L 8=;
IronPort-PHdr: 9a23:WCK3NhS67k0R3npTgoba7YVKU9psv++ubAcI9poqja5Pea2//pPkeVbS/uhpkESQBN+J6v9YhazRqa+zEWAD4JPUtncEfdQMUhIekswZkkQmB9LNEkz0KvPmLklYVMRPXVNo5Te3ZE5SHsutZlDOrDu19zFBUhn6PBB+c+LyHIOahs+r1ue0rpvUZQgAhDe0bb5oahusqgCEvcgNiowkIaE0mRY=
X-IronPort-Anti-Spam-Filtered: true
X-IronPort-Anti-Spam-Result: A0CEBwAgeX1f/4MNJK1ggQmBT4FSUQeBSS8shD2DRgONc4oRjmqBLoElA1ULAQEBDQEBLQIEAQGESgIXgXACJTUIDgIDAQELAQEFAQEBAgEGBG2FXAyFcgEBAQECARIREQwBATgECwIBCBgCAiYCAgIfERUQAgQBEggahVADDiABnXgCgTmIYXaBMoMBAQEFhRoNC4IQCYEOKoJyg2uGVhuBQT+BVIJNPoIagiWDFTOCLZM+hyqcGlIKgmiVW4UtgxGeGJMYgXqLYI80gwsCBAIEBQIOAQEFgVYCNoFXcBWDJFAXAg2SEIpWdDcCBgEJAQEDCXyNTAEB
X-IronPort-AV: E=Sophos;i="5.77,346,1596499200"; d="scan'208";a="569717784"
Received: from alln-core-1.cisco.com ([173.36.13.131]) by alln-iport-5.cisco.com with ESMTP/TLS/DHE-RSA-SEED-SHA; 07 Oct 2020 08:18:54 +0000
Received: from XCH-ALN-005.cisco.com (xch-aln-005.cisco.com [173.36.7.15]) by alln-core-1.cisco.com (8.15.2/8.15.2) with ESMTPS id 0978Is2c016533 (version=TLSv1.2 cipher=AES256-SHA bits=256 verify=FAIL); Wed, 7 Oct 2020 08:18:54 GMT
Received: from xhs-rtp-003.cisco.com (64.101.210.230) by XCH-ALN-005.cisco.com (173.36.7.15) with Microsoft SMTP Server (TLS) id 15.0.1497.2; Wed, 7 Oct 2020 03:18:54 -0500
Received: from xhs-rtp-002.cisco.com (64.101.210.229) by xhs-rtp-003.cisco.com (64.101.210.230) with Microsoft SMTP Server (TLS) id 15.0.1497.2; Wed, 7 Oct 2020 04:18:53 -0400
Received: from NAM12-BN8-obe.outbound.protection.outlook.com (64.101.32.56) by xhs-rtp-002.cisco.com (64.101.210.229) with Microsoft SMTP Server (TLS) id 15.0.1497.2 via Frontend Transport; Wed, 7 Oct 2020 04:18:53 -0400
ARC-Seal: i=1; a=rsa-sha256; s=arcselector9901; d=microsoft.com; cv=none; b=KmlH808R9GCpqqRltjKBi04qHX2CatY+D+tKvfe4YZmnk4vhAx9B/r9GB4yJDX4wJdLeedjQ/UKRjN7vBa1hfRzh4kBubvdKZrjhPhWgn+KFrWtBq3IH91vIy+bHvtPBRzvqkL3F/aM8WOA5wpcFwdEe31IYWfwKSUlYpvL9y4OzIch4TA6B0ckqVvBnc6yG1ZHarzaiDaOAZXpiGEslBGleynSVXl3csPTIsOwq+sxlnjERVzAnn509cuyooW4JFVfX6Zj9UPJ3kLYYRWJvSTodh3muJsqnNeCkyxixa77xzMWzg2Abmg9Q6RCyN6PUuPIl+pKqk3VF6MplSSFlSg==
ARC-Message-Signature: i=1; a=rsa-sha256; c=relaxed/relaxed; d=microsoft.com; s=arcselector9901; h=From:Date:Subject:Message-ID:Content-Type:MIME-Version:X-MS-Exchange-SenderADCheck; bh=yUByv6squiz8eoNdG2yiwP5YyXxd/+c4fC+7uIOXMRU=; b=PUFXVn2geMmjbUJHVOYsSUZoFG1EFOgYRkHapuVQLqngJUNg0bhSaFwC2mgWAYnT/kGUZ27Pdr7Zf2j75YWtajfkqouHqhLuXoC1UK3o503ZWK5fYtqaYo0hDYZOLlX/eiH996D8EJ6V9/qBE9mTnKZyaxSRURQvJAyVzIB73H8q53FIrEZR+TMqidm73Wje7CS+LiH79Z5jIEwdRLOloboRWRrjqNDmj+1B8nXswyagUJP1MPa656elR0z0svUjG+/m01r9ImAuimzmpAdHzHQg0nmbom+v9hTQHO8AYuajaCa9r+wn14OiOY4zKrQ08CpusBOOd+8ra962mnq3dQ==
ARC-Authentication-Results: i=1; mx.microsoft.com 1; spf=pass smtp.mailfrom=cisco.com; dmarc=pass action=none header.from=cisco.com; dkim=pass header.d=cisco.com; arc=none
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=cisco.onmicrosoft.com; s=selector2-cisco-onmicrosoft-com; h=From:Date:Subject:Message-ID:Content-Type:MIME-Version:X-MS-Exchange-SenderADCheck; bh=yUByv6squiz8eoNdG2yiwP5YyXxd/+c4fC+7uIOXMRU=; b=cAE9MBtV3OJ1wxDADFPyETagNC1msr0gAEsTnkV+B3hQMqQ2So6rVRzkjcxHRP2SwHEg7JWgB2RamabWorpnmFUKMRGxw2cOEP7o+mDHo48LWVVvIv4q/DBMaOTp38rscTQW4+KovuujyRhcc+Ve0cwB5gsuyB2vNQaw/31orYI=
Received: from MN2PR11MB3565.namprd11.prod.outlook.com (2603:10b6:208:ea::31) by MN2PR11MB3728.namprd11.prod.outlook.com (2603:10b6:208:f4::21) with Microsoft SMTP Server (version=TLS1_2, cipher=TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384) id 15.20.3433.38; Wed, 7 Oct 2020 08:18:52 +0000
Received: from MN2PR11MB3565.namprd11.prod.outlook.com ([fe80::119:f851:5860:da95]) by MN2PR11MB3565.namprd11.prod.outlook.com ([fe80::119:f851:5860:da95%4]) with mapi id 15.20.3455.021; Wed, 7 Oct 2020 08:18:52 +0000
From: "Pascal Thubert (pthubert)" <pthubert@cisco.com>
To: Routing Over Low power and Lossy networks <roll@ietf.org>, Alvaro Retana <aretana.ietf@gmail.com>
Thread-Topic: [Roll] In what way is roll-unaware-leaves updating npdao?
Thread-Index: AQHWnA0R+U3oRNZZHkOY+Mvq3wF4F6mK5kSAgABkzgCAAIBSUA==
Date: Wed, 07 Oct 2020 08:18:33 +0000
Deferred-Delivery: Wed, 7 Oct 2020 08:17:47 +0000
Message-ID: <MN2PR11MB356569111DE98AD387F6F910D80A0@MN2PR11MB3565.namprd11.prod.outlook.com>
References: <CAMMESszw4SuUQtchiqk-o7Z=62X+U2af4==X5S_=rJ-3y4Dn=w@mail.gmail.com> <MN2PR11MB356593481245BC85A03D4003D83F0@MN2PR11MB3565.namprd11.prod.outlook.com> <CAMMESsxgYifi+U=fTdFk5Fz+a1ArbFUzxBbeDeORhk30n2N3Ew@mail.gmail.com> <28970.1602008280@localhost> <CAMMESsyoxKOnedz60L7ukJgPq+VFk3y5fCkLiXv4cA9VeCBxTg@mail.gmail.com> <24657.1602030856@localhost>
In-Reply-To: <24657.1602030856@localhost>
Accept-Language: fr-FR, en-US
Content-Language: en-US
X-MS-Has-Attach:
X-MS-TNEF-Correlator:
authentication-results: ietf.org; dkim=none (message not signed) header.d=none;ietf.org; dmarc=none action=none header.from=cisco.com;
x-originating-ip: [2a01:cb1d:4ec:2200:2418:954:7e44:319f]
x-ms-publictraffictype: Email
x-ms-office365-filtering-correlation-id: b1157c9d-5402-4863-7af4-08d86a99a068
x-ms-traffictypediagnostic: MN2PR11MB3728:
x-microsoft-antispam-prvs: <MN2PR11MB3728F57F692E472AE8D6A81BD80A0@MN2PR11MB3728.namprd11.prod.outlook.com>
x-ms-oob-tlc-oobclassifiers: OLM:8882;
x-ms-exchange-senderadcheck: 1
x-microsoft-antispam: BCL:0;
x-microsoft-antispam-message-info: kcS2jSEYkXVZ/XA5BowBCUrCsYnzLVqFZCYQJGru7hm28uaDoE2uiOGEVU2AdDBCc0lN6BK3c+rvZ5lLu8V6+6YPcmT1mKLoco8FymprZax5Yyzi5cJfb8FDZPYIgjymgtC+KTBaVr+oe7/HFwTbVvGOd3ndjjHO3wxjA7hXHoFQT8K7SKU7BD8dmScr7xtBGL92o1Pd+t4kqbvCs5UkS0yJi7MKZUQ6J4Rc7OJ/HsTPs90P4lrbzSh9UZDAnZo+eRLJzhJt+OaweVvrjJE64XKlKMk8i+9Sr9xnM7Lt8c4yyNjt94yXSZcp+FMCRAmY+CZNWG/Z7E9nFW9XCloCwA==
x-forefront-antispam-report: CIP:255.255.255.255; CTRY:; LANG:en; SCL:1; SRV:; IPV:NLI; SFV:NSPM; H:MN2PR11MB3565.namprd11.prod.outlook.com; PTR:; CAT:NONE; SFS:(396003)(39860400002)(376002)(136003)(346002)(366004)(186003)(7696005)(4744005)(33656002)(76116006)(6506007)(86362001)(66446008)(71200400001)(66556008)(64756008)(6666004)(66476007)(52536014)(8676002)(9686003)(8936002)(110136005)(66946007)(478600001)(5660300002)(316002)(55016002)(83380400001)(2906002); DIR:OUT; SFP:1101;
x-ms-exchange-antispam-messagedata: LHOlyaUyO12BLbL/BRpieeDPrqCUMThnshYw9AhkBLPxUzwpbYhNjou7lTYLSBxiydWQCmmQOFnl1UBv48QZTUIAHiW5Y9DkJNU0SFnqPi/ac6OuxFBsEUWiGivcZUBFKzfR2mwKt6IpJ7tpw7X2k5HOM1naHt0eD3fYc2wh5NH5FMRz1WGhQa4YSChL02rl77izvRGrVgmGUDyY/ayNP1YjlZtkPwhD/yT9G2be830JE3cMtKACJ6ydrRpFrnrhifpVlcqvvwSkYbhJ85An0L9je2f8tWz9rpQmlrdQRqaxrxIEsLQucW5UalbJnhgsosGSVP/Ao+EjE+75k9eS+0BWFwjlY96yx1IJiEsifCps9RBEDwnTr+/EXCupfyHL1yvZi4K/CKUhtgZ/N8EUOXBlTqANr+euO9ANSpdyuir+JByBuCQA8Wor57Tkv+bK5m1GPLvTkFgr4G8IzWGQu0cHFrBt7G2VfCYPQgm481CKCa2ZwtQTVC2vkt6ZowGWC1FlsytZlgWb5tK7wdvBBNARILfpb0khSG0wpz4ePpQwBNAxaEhLcxxW1bQzrEysM+PQWtZ1LPHUV2EtszKHc4CuFeT5Wjs/RaeKVPB2DGOkQrzT2XpacNt19ySWk39rSNvmlf6Yjq52hIfk3hTQ4nuVc/E4pyXkwgcyE48/ojFXQzI18lMOii0jZ6q3kTO8lSfhGseVEcWEEFHH63+Stg==
x-ms-exchange-transport-forked: True
Content-Type: text/plain; charset="utf-8"
Content-Transfer-Encoding: base64
MIME-Version: 1.0
X-MS-Exchange-CrossTenant-AuthAs: Internal
X-MS-Exchange-CrossTenant-AuthSource: MN2PR11MB3565.namprd11.prod.outlook.com
X-MS-Exchange-CrossTenant-Network-Message-Id: b1157c9d-5402-4863-7af4-08d86a99a068
X-MS-Exchange-CrossTenant-originalarrivaltime: 07 Oct 2020 08:18:52.5128 (UTC)
X-MS-Exchange-CrossTenant-fromentityheader: Hosted
X-MS-Exchange-CrossTenant-id: 5ae1af62-9505-4097-a69a-c1553ef7840e
X-MS-Exchange-CrossTenant-mailboxtype: HOSTED
X-MS-Exchange-CrossTenant-userprincipalname: ruvb4Ld3Y1vEmsP/3StNALoqFA29Z/yL6Lq3l/Urm7cXcOBy10CA9DEQuF7dXX/K0e7apQs+NU3wZgj/G+v4Ng==
X-MS-Exchange-Transport-CrossTenantHeadersStamped: MN2PR11MB3728
X-OriginatorOrg: cisco.com
X-Outbound-SMTP-Client: 173.36.7.15, xch-aln-005.cisco.com
X-Outbound-Node: alln-core-1.cisco.com
Archived-At: <https://mailarchive.ietf.org/arch/msg/roll/EZP9xalDrU1AeQsEYcZfButi4GM>
Subject: Re: [Roll] In what way is roll-unaware-leaves updating npdao?
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, 07 Oct 2020 08:18:57 -0000

Many thanks to you both for your help here!

> Alvaro Retana <aretana.ietf@gmail.com> wrote:
>     > Just to make sure, we’re agreeing…right?
> 
> I was disagreeing with:
> 
>     >> [major] To me, Updating an RFC means that the implementations of that
>     >> RFC should also implement this one.  In this case, there would be an
>     >> expectation that all nodes that support the DCO would support the
>     >> Non-Storing MOP as well.  Is that what is intended?
> 
> That's not what's expected.
> 
Agreed, the formal update is already gone (this was about -18).
For 22 I'll change the name of eth section from "updating" to "extending"

Is that all that is needed for this point?

Keep safe,

Pascal

v2.23.0 | Report a Bug | By Email