IETF Logo Mail Archive

Re: [Roll] multicast in unaware-leaves

"Li Zhao (liz3)" <liz3@cisco.com> Wed, 10 July 2019 01:48 UTC

Return-Path: <liz3@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 B61B4120048; Tue, 9 Jul 2019 18:48:33 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -14.499
X-Spam-Level:
X-Spam-Status: No, score=-14.499 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, 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, 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=QUt+VtwS; dkim=pass (1024-bit key) header.d=cisco.onmicrosoft.com header.b=SUalUcA1
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 cXmbU34IIG27; Tue, 9 Jul 2019 18:48:31 -0700 (PDT)
Received: from rcdn-iport-8.cisco.com (rcdn-iport-8.cisco.com [173.37.86.79]) (using TLSv1.2 with cipher DHE-RSA-SEED-SHA (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 22B1D12001E; Tue, 9 Jul 2019 18:48:31 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=cisco.com; i=@cisco.com; l=13543; q=dns/txt; s=iport; t=1562723311; x=1563932911; h=from:to:cc:subject:date:message-id:references: in-reply-to:mime-version; bh=u3ahHW0akNXUa6K8iO/nnkB6FAOSZTiFcpZCHeoqrbQ=; b=QUt+VtwSO1h8612M1xe5qtEaM7gIJvCMvhbZNymGDZZGDimIxVFUFgtf SNPNm83/g5x+JXRWihQfOAiwZoTdQniVO12bPEUSlSkRCPkvuFG9SlgPh Ph5K6rYGAVOKIjm5mJ55m1aNkZKbJ4Hd8y5W6owvO4LOzS2ieGPGPS+XJ Y=;
IronPort-PHdr: 9a23:ghKMghQ0srHsthKqOksjJMpHtNpsv++ubAcI9poqja5Pea2//pPkeVbS/uhpkESUANfA8/wRje3QvuigQmEG7Zub+FE6OJ1XH15NksAKh0olCc+BB1f8Kavubj5hNM9DT1RiuXq8NBsdFQ==
X-IronPort-Anti-Spam-Filtered: true
X-IronPort-Anti-Spam-Result: A0BNAQCiQyVd/4YNJK1mHAEBAQQBAQcEAQGBVgQBAQsBgRQvUANqVSAECygKhBKDRwOOTZVOhFSBQoEQA1QJAQEBDAEBIwoCAQGEQAIXgiwjNwYOAQMBAQQBAQIBBW2FPAyFSwIEEhEKEwEBNwEPAgEIQgICAjAlAgQBDSeDAAGBHU0DHQECDKIdAoE4iGBxgTKCeQEBBYUEGIISAwaBNAGLXoIWgTgfgkw+gmEBAQOBRkWCXTKCJoExAY0+hH2VfG0GAwKCF4ZWjS8bgiyHIY4zjTCHQY99AgQCBAUCDgEBBYFmIoFYcHoBc4FOgkGDcYUUhT9ygSmNJAGBIAEB
X-IronPort-AV: E=Sophos;i="5.63,472,1557187200"; d="scan'208,217";a="590891247"
Received: from alln-core-12.cisco.com ([173.36.13.134]) by rcdn-iport-8.cisco.com with ESMTP/TLS/DHE-RSA-SEED-SHA; 10 Jul 2019 01:48:03 +0000
Received: from XCH-ALN-004.cisco.com (xch-aln-004.cisco.com [173.36.7.14]) by alln-core-12.cisco.com (8.15.2/8.15.2) with ESMTPS id x6A1m2dc002531 (version=TLSv1.2 cipher=AES256-SHA bits=256 verify=FAIL); Wed, 10 Jul 2019 01:48:02 GMT
Received: from xhs-rtp-001.cisco.com (64.101.210.228) by XCH-ALN-004.cisco.com (173.36.7.14) with Microsoft SMTP Server (TLS) id 15.0.1473.3; Tue, 9 Jul 2019 20:48:02 -0500
Received: from xhs-rtp-001.cisco.com (64.101.210.228) by xhs-rtp-001.cisco.com (64.101.210.228) with Microsoft SMTP Server (TLS) id 15.0.1473.3; Tue, 9 Jul 2019 21:48:01 -0400
Received: from NAM02-BL2-obe.outbound.protection.outlook.com (64.101.32.56) by xhs-rtp-001.cisco.com (64.101.210.228) with Microsoft SMTP Server (TLS) id 15.0.1473.3 via Frontend Transport; Tue, 9 Jul 2019 21:48:01 -0400
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=u3ahHW0akNXUa6K8iO/nnkB6FAOSZTiFcpZCHeoqrbQ=; b=SUalUcA1dvjP/g7mewUn/U3qZHkK8hPJiUxkeThve4x8gYBx/DNQuZdSLJy6K2qwctdMq9ugbgIERCpvpvyZZhiW2rYnfmAEUlUZRiX3ImcurWFCbdt5u/UEcphqRq1pRJxc2WiD146DnQCEKQSaV16W5H4RCx9ZVDcK6j61ciY=
Received: from MN2PR11MB3680.namprd11.prod.outlook.com (20.178.252.96) by MN2PR11MB3805.namprd11.prod.outlook.com (20.178.254.24) with Microsoft SMTP Server (version=TLS1_2, cipher=TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384) id 15.20.2052.18; Wed, 10 Jul 2019 01:48:01 +0000
Received: from MN2PR11MB3680.namprd11.prod.outlook.com ([fe80::4815:c3d4:9fce:2d52]) by MN2PR11MB3680.namprd11.prod.outlook.com ([fe80::4815:c3d4:9fce:2d52%4]) with mapi id 15.20.2052.020; Wed, 10 Jul 2019 01:48:01 +0000
From: "Li Zhao (liz3)" <liz3@cisco.com>
To: "Pascal Thubert (pthubert)" <pthubert@cisco.com>, "draft-ietf-roll-unaware-leaves@ietf.org" <draft-ietf-roll-unaware-leaves@ietf.org>
CC: Routing Over Low power and Lossy networks <roll@ietf.org>
Thread-Topic: multicast in unaware-leaves
Thread-Index: AQHVNjNXlfxFW3XNtU+NsE/nsIg/8abCDQ3AgAGCq4A=
Date: Wed, 10 Jul 2019 01:48:00 +0000
Message-ID: <198E1F7E-8A3F-4AB8-ABB4-F673B8801E6D@cisco.com>
References: <3A0F19AC-493B-4A1F-8E53-5CCB310D8B0C@cisco.com> <MN2PR11MB3565CFE831041ED5FFFEE6C9D8F10@MN2PR11MB3565.namprd11.prod.outlook.com>
In-Reply-To: <MN2PR11MB3565CFE831041ED5FFFEE6C9D8F10@MN2PR11MB3565.namprd11.prod.outlook.com>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach:
X-MS-TNEF-Correlator:
authentication-results: spf=none (sender IP is ) smtp.mailfrom=liz3@cisco.com;
x-originating-ip: [64.104.125.239]
x-ms-publictraffictype: Email
x-ms-office365-filtering-correlation-id: 20e21f0d-ab7b-4ca8-7ce6-08d704d8a435
x-microsoft-antispam: BCL:0; PCL:0; RULEID:(2390118)(7020095)(4652040)(8989299)(4534185)(4627221)(201703031133081)(201702281549075)(8990200)(5600148)(711020)(4605104)(1401327)(2017052603328)(7193020); SRVR:MN2PR11MB3805;
x-ms-traffictypediagnostic: MN2PR11MB3805:
x-ms-exchange-purlcount: 3
x-microsoft-antispam-prvs: <MN2PR11MB3805128922F3CDDECA4AB2D98CF00@MN2PR11MB3805.namprd11.prod.outlook.com>
x-ms-oob-tlc-oobclassifiers: OLM:10000;
x-forefront-prvs: 0094E3478A
x-forefront-antispam-report: SFV:NSPM; SFS:(10009020)(4636009)(136003)(366004)(376002)(346002)(396003)(39860400002)(199004)(189003)(7736002)(36756003)(11346002)(2906002)(26005)(186003)(3480700005)(53936002)(486006)(6436002)(790700001)(66476007)(6116002)(3846002)(236005)(2616005)(66066001)(14454004)(2501003)(446003)(5660300002)(6506007)(6512007)(76176011)(25786009)(71200400001)(68736007)(8936002)(81156014)(33656002)(8676002)(76116006)(86362001)(91956017)(6306002)(71190400001)(4326008)(478600001)(102836004)(966005)(81166006)(450100002)(6246003)(606006)(99286004)(54896002)(476003)(6486002)(256004)(316002)(66556008)(66946007)(229853002)(66446008)(110136005)(64756008)(88722002); DIR:OUT; SFP:1101; SCL:1; SRVR:MN2PR11MB3805; H:MN2PR11MB3680.namprd11.prod.outlook.com; FPR:; SPF:None; LANG:en; PTR:InfoNoRecords; A:1; MX:1;
received-spf: None (protection.outlook.com: cisco.com does not designate permitted sender hosts)
x-ms-exchange-senderadcheck: 1
x-microsoft-antispam-message-info: VVHefZFJqF0iciazN7OZGU+Y08onWfcl/40T5HRU4wv7puBxG8CfaPIzDZLdIokpHkT5Li1ihMY4c6YF25UkUT63nJv0BhVeKO8hlWObSHuLzY1eul4qFj4rOO456c2Q84wLRbQkG8Bm/shaJRlh2zEl703O5yNeACAb3DApOXUc8vciKWd7pZZTDh8GE0Bu076TVr6hGdVLAsYvB6h7Vo6qpe1mblfT+ZrHKTAnNUi0cB9Ti0oT8NDjI08ZkNBvnxFh48sHbMyp4pmst4dHVfWefWqgWnaRQ3Fm9YtLkS+pRw6lLcyNgnE2ml5HQFV6jtyLDsMJ7zWn1OGR9YuS7UouIyMe6kPRBKizUEFE7OCM7pjlKq/t677y8B92TS4OR0++quDmVSlVPX5w+YcrwbjcO3+QCjwp55VUX5mXxqs=
Content-Type: multipart/alternative; boundary="_000_198E1F7E8A3F4AB8ABB4F673B8801E6Dciscocom_"
MIME-Version: 1.0
X-MS-Exchange-CrossTenant-Network-Message-Id: 20e21f0d-ab7b-4ca8-7ce6-08d704d8a435
X-MS-Exchange-CrossTenant-originalarrivaltime: 10 Jul 2019 01:48:00.8991 (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: liz3@cisco.com
X-MS-Exchange-Transport-CrossTenantHeadersStamped: MN2PR11MB3805
X-OriginatorOrg: cisco.com
X-Outbound-SMTP-Client: 173.36.7.14, xch-aln-004.cisco.com
X-Outbound-Node: alln-core-12.cisco.com
Archived-At: <https://mailarchive.ietf.org/arch/msg/roll/Ah9JKmX8xtTjKJavrAIkfmFGPm0>
Subject: Re: [Roll] multicast in unaware-leaves
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, 10 Jul 2019 01:48:34 -0000

Thanks Pascal. Please find my comment inline.


Ø  RUL should not be a MPL forwarder
Though it has dependencies on them, this spec does not mandate anything on RULs, it is only on routers.  So we could say that the spec does not expect the RUL to understand MPL and to forward it. Now if it does, it does not hurt does it?
[Li]: Agree with you. The spec does not mandate anything. It only need to cover MPL cases.


Ø  MPL Hop-by-Hop Header can be ignored when not understood

MPL option type cannot be ignored. It is 6D and the first two bits indicate that the IPv6 node must discard the packet if it doesn't recognize the option type. This is why https://tools.ietf.org/html/draft-ietf-roll-useofrplinfo changes the RPL option from x63 to x23. So the HbH must be encapsulated and removed.



Ø  6LR might decapsulate MPL’s IP-in-IP packet and forward to RUL

Yes, no choice there I guess.
[Li]: Does 6LR need to know 6LN’s capability of MPL? If not, it doesn’t know whether to decapsulate HbH.
        Consider one case that 6LN supports MPL but 6LR decapsulates HbH. 6LN will lost all capability of MPL, for example, data retransmit.


Best regards,
Li

v2.23.0 | Report a Bug | By Email