[pim] Alissa Cooper's No Objection on draft-ietf-pim-reserved-bits-03: (with COMMENT)

Alissa Cooper via Datatracker <noreply@ietf.org> Wed, 18 September 2019 16:47 UTC

Return-Path: <noreply@ietf.org>
X-Original-To: pim@ietf.org
Delivered-To: pim@ietfa.amsl.com
Received: from ietfa.amsl.com (localhost [IPv6:::1]) by ietfa.amsl.com (Postfix) with ESMTP id DE7C9120AEF; Wed, 18 Sep 2019 09:47:12 -0700 (PDT)
MIME-Version: 1.0
Content-Type: text/plain; charset="utf-8"
Content-Transfer-Encoding: 7bit
From: Alissa Cooper via Datatracker <noreply@ietf.org>
To: "The IESG" <iesg@ietf.org>
Cc: draft-ietf-pim-reserved-bits@ietf.org, Mike McBride <mmcbride7@gmail.com>, pim-chairs@ietf.org, mmcbride7@gmail.com, pim@ietf.org
X-Test-IDTracker: no
X-IETF-IDTracker: 6.101.0
Auto-Submitted: auto-generated
Precedence: bulk
Reply-To: Alissa Cooper <alissa@cooperw.in>
Message-ID: <156882523290.4585.6873922125613552164.idtracker@ietfa.amsl.com>
Date: Wed, 18 Sep 2019 09:47:12 -0700
Archived-At: <https://mailarchive.ietf.org/arch/msg/pim/l1W5Gqh7TNqQYKHTBJHJBhHp6tE>
Subject: [pim] Alissa Cooper's No Objection on draft-ietf-pim-reserved-bits-03: (with COMMENT)
X-BeenThere: pim@ietf.org
X-Mailman-Version: 2.1.29
List-Id: Protocol Independent Multicast <pim.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/pim>, <mailto:pim-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/pim/>
List-Post: <mailto:pim@ietf.org>
List-Help: <mailto:pim-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/pim>, <mailto:pim-request@ietf.org?subject=subscribe>
X-List-Received-Date: Wed, 18 Sep 2019 16:47:20 -0000

Alissa Cooper has entered the following ballot position for
draft-ietf-pim-reserved-bits-03: No Objection

When responding, please keep the subject line intact and reply to all
email addresses included in the To and CC lines. (Feel free to cut this
introductory paragraph, however.)


Please refer to https://www.ietf.org/iesg/statement/discuss-criteria.html
for more information about IESG DISCUSS and COMMENT positions.


The document, along with other ballot positions, can be found here:
https://datatracker.ietf.org/doc/draft-ietf-pim-reserved-bits/



----------------------------------------------------------------------
COMMENT:
----------------------------------------------------------------------

I'm guessing this is unnecessary but just wanted to check: do you need a
further extension point in case all 48 subtypes of types 13, 14, and 15 get
used up at some point? That is, RFC 6166 had reserved a code point for future
extensions of the type space. Is it possible that another future extension will
be needed and if so, should a code point be reserved for it?