Re: [pim] Publication has been requested for draft-ietf-pim-reserved-bits-02

Stig Venaas <> Fri, 09 August 2019 17:02 UTC

Return-Path: <>
Received: from localhost (localhost []) by (Postfix) with ESMTP id D8A6712006F for <>; Fri, 9 Aug 2019 10:02:07 -0700 (PDT)
X-Virus-Scanned: amavisd-new at
X-Spam-Flag: NO
X-Spam-Score: -1.898
X-Spam-Status: No, score=-1.898 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, RCVD_IN_DNSWL_NONE=-0.0001, SPF_HELO_NONE=0.001, SPF_NONE=0.001] autolearn=ham autolearn_force=no
Authentication-Results: (amavisd-new); dkim=pass (2048-bit key)
Received: from ([]) by localhost ( []) (amavisd-new, port 10024) with ESMTP id 2-R0aziQxQmw for <>; Fri, 9 Aug 2019 10:02:05 -0700 (PDT)
Received: from ( [IPv6:2a00:1450:4864:20::542]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (No client certificate requested) by (Postfix) with ESMTPS id 3D66D12002F for <>; Fri, 9 Aug 2019 10:02:05 -0700 (PDT)
Received: by with SMTP id h8so7505135edv.7 for <>; Fri, 09 Aug 2019 10:02:05 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed;; s=20150623; h=mime-version:references:in-reply-to:from:date:message-id:subject:to :cc; bh=aLceJd9A4HttDOrkOYYgggtIqWLFaGCb9q3F9EcU+oE=; b=rhc8Cl9+VYSu9UiwDUudaMOYmrs/XQaFBRzrk5tSLa81+kxW7SgnFFoPR/IPgAaUHg q8SRPxa9mWyZvUTkI4kzGsHXYfgiKnAGmHED6/zchF38Y2OeRDNJda3mJio5Nbxz7+y2 tDzaF3slKUyPP3OK7t3PwlISXH5eHeOPBWHSl3wtPMcPPXQTbGvUeQMSErggvu/ZAJFk f614yyq9G/YzRi/bmikepBlZCsUL/iVPurB9jbQuFrhk6OjHRj56URy4r1VvRVvTvaH4 YAF1Hbz+sNx7H6EiXIlyvKTVAWrsCHbQBxObgnqK/uTT/u+2sG5OsKpWZa0yndAa4uZH aVWQ==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed;; s=20161025; h=x-gm-message-state:mime-version:references:in-reply-to:from:date :message-id:subject:to:cc; bh=aLceJd9A4HttDOrkOYYgggtIqWLFaGCb9q3F9EcU+oE=; b=FOYje27TUcA2ohAySQZHZm8RW9CCcXgjfLkG6dGOcqwzlHnZvsrxRR000n4VlJfVOz 9mrUzWfhOj5nPUH+9D4rP6ncOoMVxffstcS84T7P+C3e9pRs8qJq3kMklFHzsyuyz3g3 LZMeyPsn9dAkveXrnOlSoB+MSpSPoXTkMgUY+zHkSjyEoLuGkqOkx8Rodi+SX5Q/zwIg EI/l/yp/vdooln91gzHgG91/KjL1zycKCLCRhLfJVEjDOebzAodCiDv+gNtF4ECZha60 NiFJ8hAhUCT0W4ED6JDEHlfNZCYdMBQ3+P+Vfy58gt5ntsFakqhfCQFDDWCXVCk9RmTh tmPQ==
X-Gm-Message-State: APjAAAVSli+Rc67rjVrcJb0cEnm0goR9dEnZ7X2l1okOLk6/JlRNWchi 6bGGn5KF0jEIcMsVp197m3Gz2+mCU61WV5XQYwQlIg==
X-Google-Smtp-Source: APXvYqxPrqjy98Ik5JsiW6rTvb/JKOlMA5h+6CkyUksaYbqINfZK/f4nD5C/PfWJ8+RX4LUqneUJR+SB8H7jrxYFGA4=
X-Received: by 2002:a17:906:a3cb:: with SMTP id ca11mr19880083ejb.79.1565370123762; Fri, 09 Aug 2019 10:02:03 -0700 (PDT)
MIME-Version: 1.0
References: <> <>
In-Reply-To: <>
From: Stig Venaas <>
Date: Fri, 09 Aug 2019 10:01:53 -0700
Message-ID: <>
To: Anish Peter <>
Cc: Mike McBride <>,,
Content-Type: text/plain; charset="UTF-8"
Archived-At: <>
Subject: Re: [pim] Publication has been requested for draft-ietf-pim-reserved-bits-02
X-Mailman-Version: 2.1.29
Precedence: list
List-Id: Protocol Independent Multicast <>
List-Unsubscribe: <>, <>
List-Archive: <>
List-Post: <>
List-Help: <>
List-Subscribe: <>, <>
X-List-Received-Date: Fri, 09 Aug 2019 17:02:08 -0000


Re point 1:
Rather than delaying this draft several months, probably at least
until after next IETF, I would suggest that we have a separate
discussion on experimental/vendor reservations. We already have one WG
draft that might need a type soon. I think we've avoided
experimental/vendor reservations in the past since we had so little
space, but it is something to consider now. If we decide to do this,
that can be a separate small draft.

Point 2 and 4:
We can put in the recommended order of usage. We also got the chance
to suggest this to IANA if needed when they assign types to future
drafts. I agree about using LSB bits first since that may help future
type expansion if needed. We can put it in the draft, but this is also
something we as a WG should keep in mind.

Point 3:
Given that we should use the space in the order 13.0, 13.1, ... it
would be many years until we would potentially consider touching 15.
Since the types are only used for RFCs approved by the pim WG, we are
in control of this. If we do a draft for experimental/vendor
reservations, then that could maybe also mark 15 as reserved. I think
"reserved" mostly makes sense when assignments don't require IETF/WG
approval in general, and the IETF/WG wants to ensure they have control
of at least parts of the space.

The draft will go to IETF last call and we can take your input as part
of the last call input. I'll address at least points 2 and 4 then.

Thanks for the input. If you have further thoughts, or anyone else in
the WG does, please follow-up.

I stripped the cc-list a bit, removing the IETF wide addresses.

On Thu, Aug 8, 2019 at 9:04 PM Anish Peter <> wrote:
> Hi Authors,
>  This draft is very much needed and it gives a simple solution.
>  Few suggestions/thoughts on this draft.
> 1. Could you please consider reserving a few types are experimental / vendor specific usage
> 2. Though obvious, it might be better to mention that the order of usage recommended is 13.0, 13.1, . . . rather than 13.0, 14.0.
> 3. Thought 48 types is a very big space to expand wouldn't it be better to keep 15.x as reserved for the time being.
>  Over all my suggestion is
> 13.0 -14.11 unassigned
> 14.12-14.15 experimental
> 15.x reserved
>  4. Should this draft make a recommendation to use the reserved bits starting from LSB rather than the present usage pattern of MSB first?
> Thanks,
> Anish Peter
> On Thu, Aug 8, 2019 at 4:06 AM Mike McBride via Datatracker <> wrote:
>> Mike McBride has requested publication of draft-ietf-pim-reserved-bits-02 as Proposed Standard on behalf of the PIM working group.
>> Please verify the document's state at
>> _______________________________________________
>> pim mailing list
> _______________________________________________
> pim mailing list