Re: Opsdir last call review of draft-ietf-pim-reserved-bits-03

Alvaro Retana <alvaro.retana@futurewei.com> Mon, 16 September 2019 16:57 UTC

Return-Path: <alvaro.retana@futurewei.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 344B0120072; Mon, 16 Sep 2019 09:57:02 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.998
X-Spam-Level:
X-Spam-Status: No, score=-1.998 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_NONE=-0.0001, SPF_NONE=0.001] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (1024-bit key) header.d=futurewei.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 GM97YJbES1Z2; Mon, 16 Sep 2019 09:56:59 -0700 (PDT)
Received: from NAM02-SN1-obe.outbound.protection.outlook.com (mail-eopbgr770090.outbound.protection.outlook.com [40.107.77.90]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 706E0120122; Mon, 16 Sep 2019 09:56:59 -0700 (PDT)
ARC-Seal: i=1; a=rsa-sha256; s=arcselector9901; d=microsoft.com; cv=none; b=fnhmw4tC7vvRbj1q0F6xaOxcn14K/Tr8Ocz5l1Q3B+dO46hkerVbCb8VDglaEm+Re5/DMRad62TQn+ZcBic0HMeiBFErPsq3kCUDChQC0dIDO/yr4iRhdEpMrZ3Vk12SZRdYbPQ4V1NPSOpPQTPaFLYHH4+ivS8GOtWUxL/vaBXgzFKoHFgQ5cDbgsPUObMCIgg5tmQhRM9i9Gp5mBC6CpOKaG2I8eL48H/ry+I0Dq/cG3fgeQQgTumg7ayMMDUt6oHlhDOZCjDQWXY3EVOhgUBNiiHUCY8fP0kh3I0Is7hxccAVBc/lOK82hHqrkkGqaKtf8wStqxU2Uhhw42stDQ==
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=iteYRMEQ7YeSwIRDr+u4mRcKhsxQxoOFidzkGhYOAtQ=; b=O8mcPJ0F1kPTkZS0abdmzrCifXKwNrPnTcN5ys7oaHEwpan9SOZxYvnlFOwmgOFe6d30tt/iBb1Pi9d9fNDAMrD+3q7J0zxvlRH5LPXpUMzdAzqV2tAd4J18vN5uXMPiiPNH+bgFSfcisSIqfmX1PBtE+OIxYrCdflOOj2fvEfdorZ35sVnWbFO4HtSgHN8nkjQ88keeBQ1O0rXa1cR0LxLFP6noZ7ch2PgyUEUzMk+1kSCoAFdlsMGnkcQ7ofQS+ZeNshRF57Lj3AXPqyXnK3qiCxBXxdF1z5zcziBYB4AeHBKGva+Xtm9/UbWzvDLzbEF9PTjEzg88heWEbdiRyA==
ARC-Authentication-Results: i=1; mx.microsoft.com 1; spf=pass smtp.mailfrom=futurewei.com; dmarc=pass action=none header.from=futurewei.com; dkim=pass header.d=futurewei.com; arc=none
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=Futurewei.com; s=selector2; h=From:Date:Subject:Message-ID:Content-Type:MIME-Version:X-MS-Exchange-SenderADCheck; bh=iteYRMEQ7YeSwIRDr+u4mRcKhsxQxoOFidzkGhYOAtQ=; b=I+xmNO1XACELWVVYgCZNvKs31BxVj7Yz5uENjW74EQXZ6T6nWeCl2tXw4p8c3KYACQ1o1rkvL8U74aNCWJkKPcGjpBLjPC1254KCi/X8DhN/M/TtiOEPsrCVE3F+7hx5XJF0/e5ZKGdefxvZuuvzzXloEhtfNkJOq4uYl9jMrYI=
Received: from CY4PR13MB1671.namprd13.prod.outlook.com (10.171.167.22) by CY4PR13MB1111.namprd13.prod.outlook.com (10.173.179.147) with Microsoft SMTP Server (version=TLS1_2, cipher=TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384) id 15.20.2284.13; Mon, 16 Sep 2019 16:56:56 +0000
Received: from CY4PR13MB1671.namprd13.prod.outlook.com ([fe80::ac1e:1214:2ca8:23b4]) by CY4PR13MB1671.namprd13.prod.outlook.com ([fe80::ac1e:1214:2ca8:23b4%12]) with mapi id 15.20.2284.009; Mon, 16 Sep 2019 16:56:56 +0000
From: Alvaro Retana <alvaro.retana@futurewei.com>
To: Susan Hares <shares@ndzh.com>, "ops-dir@ietf.org" <ops-dir@ietf.org>
CC: "pim@ietf.org" <pim@ietf.org>, "draft-ietf-pim-reserved-bits.all@ietf.org" <draft-ietf-pim-reserved-bits.all@ietf.org>, "ietf@ietf.org" <ietf@ietf.org>
Subject: Re: Opsdir last call review of draft-ietf-pim-reserved-bits-03
Thread-Topic: Opsdir last call review of draft-ietf-pim-reserved-bits-03
Thread-Index: AQHVak2FW4eF0TmjhUiszzyV5xjgTKcuioyA
Date: Mon, 16 Sep 2019 16:56:55 +0000
Message-ID: <etPan.5d7fbe8f.5e22fa25.54c@futurewei.com>
References: <156839092320.32031.10069621346683776171@ietfa.amsl.com>
In-Reply-To: <156839092320.32031.10069621346683776171@ietfa.amsl.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=alvaro.retana@futurewei.com;
x-originating-ip: [65.190.21.9]
x-ms-publictraffictype: Email
x-ms-office365-filtering-correlation-id: 8ebaf001-e6a7-4132-73ea-08d73ac6e1aa
x-microsoft-antispam: BCL:0; PCL:0; RULEID:(2390118)(7020095)(4652040)(8989299)(4534185)(4627221)(201703031133081)(201702281549075)(8990200)(5600167)(711020)(4605104)(1401327)(2017052603328)(7193020); SRVR:CY4PR13MB1111;
x-ms-traffictypediagnostic: CY4PR13MB1111:
x-microsoft-antispam-prvs: <CY4PR13MB11113EA7CF4B61A0E1EC103AEF8C0@CY4PR13MB1111.namprd13.prod.outlook.com>
x-ms-oob-tlc-oobclassifiers: OLM:10000;
x-forefront-prvs: 0162ACCC24
x-forefront-antispam-report: SFV:NSPM; SFS:(10019020)(4636009)(366004)(199004)(189003)(51914003)(5660300002)(66446008)(66556008)(76116006)(498600001)(186003)(66946007)(229853002)(86362001)(91956017)(14454004)(6506007)(26005)(102836004)(36756003)(76176011)(8676002)(2906002)(446003)(11346002)(64756008)(66476007)(2501003)(81166006)(81156014)(110136005)(54906003)(8936002)(53936002)(4326008)(6116002)(3846002)(6486002)(6246003)(476003)(2616005)(236005)(54896002)(6512007)(25786009)(66066001)(486006)(71200400001)(44832011)(7736002)(256004)(71190400001)(99286004)(6436002)(14444005); DIR:OUT; SFP:1102; SCL:1; SRVR:CY4PR13MB1111; H:CY4PR13MB1671.namprd13.prod.outlook.com; FPR:; SPF:None; LANG:en; PTR:InfoNoRecords; A:1; MX:1;
received-spf: None (protection.outlook.com: futurewei.com does not designate permitted sender hosts)
x-ms-exchange-senderadcheck: 1
x-microsoft-antispam-message-info: 5fYVROk+WdkYt23DKqQmBvq9H86J5a279lXozcUQy2N3v2ETL+bNTxEP2wslon83SKkvHFmCIMeCZRPxqzhiStscM3FvRvg7pY5uD7A+TMgbG2XsjZrZNSJKGLDcCYwV4w4IP3Z5ter2oVIHPxhlHg/n4/5h4X42yGvbIS7Yk1NlpB83PxWTYoE1oAXgnJG6PBP1rcX9b5iOZsfTifPTQY0fKhslq1Ph4JURhK9Xl3viUvIMrtXWPtZYQndgZB8x3+4BvoEb88bUdbfBNAIh44tzbEcp1L2cCev7BVawVHSK4HIudysf16W+GVK6FyJYWX0XMUpqsHiMWEtqGg2HWlbxOZPg9waJlyRGaE6l5zVuYZMYpFIMur3UERUFKsOni2L/1NUDtgro/0v/blZLtBMCCK5adsPJrgCN5hXjTDo=
x-ms-exchange-transport-forked: True
Content-Type: multipart/alternative; boundary="_000_etPan5d7fbe8f5e22fa2554cfutureweicom_"
MIME-Version: 1.0
X-OriginatorOrg: Futurewei.com
X-MS-Exchange-CrossTenant-Network-Message-Id: 8ebaf001-e6a7-4132-73ea-08d73ac6e1aa
X-MS-Exchange-CrossTenant-originalarrivaltime: 16 Sep 2019 16:56:55.8485 (UTC)
X-MS-Exchange-CrossTenant-fromentityheader: Hosted
X-MS-Exchange-CrossTenant-id: 0fee8ff2-a3b2-4018-9c75-3a1d5591fedc
X-MS-Exchange-CrossTenant-mailboxtype: HOSTED
X-MS-Exchange-CrossTenant-userprincipalname: O0hUxKm6pCTzVknbakbXimuhYIghT28DbMqQHMS7Z1W4pmZsMRGRtctx/8kI08Dw6gZhD/bouhTUZNN+4m39VA==
X-MS-Exchange-Transport-CrossTenantHeadersStamped: CY4PR13MB1111
Archived-At: <https://mailarchive.ietf.org/arch/msg/ietf/xcB3HFo-GTPJfQdoVwEvgvo7w1g>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.29
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/ietf/>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Mon, 16 Sep 2019 16:57:02 -0000

On September 13, 2019 at 12:08:47 PM, Susan Hares via Datatracker (noreply@ietf.org<mailto:noreply@ietf.org>) wrote:

[Author hat on.]

Sue:

Hi!  Thanks for the review!

...
Issue: Issue/Error in document
However, this document does not specify the error handling if a PIM implementation does
not abid by the MUSTs in section 4 defined as follows:

Unless otherwise specified, all the Flag Bits for each PIM type are
Reserved [RFC8126]. They MUST be set to zero on transmission, and
they MUST be ignored upon receipt. The specification of a new PIM
type, MUST indicate whether the bits should be treated differently.

This issues becomes a serious issue if it negates any error handling or changes
any existing error handling.

I suspect this is not really a serious issue, but a flaw in the write-up.
I suspect that because you set to zero on transmission, and
ignored on receipt you will not engage in any error handling.

However, it is necessary to state that so that machines testing
the PIM and SM-PIM protocols will easily add this to their testing suite.

The Flag Bits are currently Reserved in rfc7761, which describes the field as: "Set to zero on transmission.  Ignored upon receipt.”  IOW, the behavior doesn’t change at all…really just the name of the field and the per-type applicability.

I’m not sure what you would like to see added, given that there is no change in the behavior specified in rfc7761.  Can you suggest something?


2) Issue: Security considerations in general are the same as
[RFC7761] and {RFC3973], but bogus error handling (depending how you do #1)
may impact the security considerations.

3) Minor Issue: Should Section 3 include a change to RFC3973 - section 4.7.1

No.  PIM-DM (rfc3973) uses the packet formats (including the Header of course, §4.7.1) defined by PIM-SM…from §4.7: "All PIM-DM packets use the same format as PIM-SM packets.  In the event of a discrepancy, PIM-SM [4] should be considered the definitive specification.”  The reference is to rfc2362, the PIM-DM spec at the time, which has now been replaced by rfc7761.

Thanks!

Alvaro.