Re: [pim] draft-venaas-pim-reserved-bits-01 Adoption Call

Hi

I'm responding to this as an author, not as chair.

I'm hoping for more responses, whether positive or negative. It is
frustrating how silent the WG is.

My impression from the discussion at the meeting was that people are
OK with the draft itself, but some people think that we should not
work on extending the type space until it is needed. If people prefer,
I could split this draft into one draft to create the registry for
reserved bits which is purely procedural/administrative, and another
for the type space extension. Let me know if you have thoughts on
this.

Do people agree that the method of extending the type space is
reasonable, and that we should not assign any new types without first
extending the type space? If we do not, we will have less bits
available for type extension.

There are proposals like draft-ramki-pim-null-register-packing that
would require new types. I'm hoping people that support that draft, or
want new types for other reasons would support extending the type
space.

Thoughts? I need your feedback so I know what the WG wants me to do
with this draft, if anything.

Thanks,
Stig

On Mon, Sep 17, 2018 at 5:30 PM <zhang.zheng@zte.com.cn> wrote:
>
> Support.
>
>
> Thanks,
>
> Sandy
>
>
> 原始邮件
> 发件人：MichaelMcBride <Michael.McBride@huawei.com>
> 收件人：pim@ietf.org <pim@ietf.org>
> 日 期 ：2018年09月18日 06:00
> 主 题 ：[pim] draft-venaas-pim-reserved-bits-01 Adoption Call
> _______________________________________________
> pim mailing list
> pim@ietf.org
> https://www.ietf.org/mailman/listinfo/pim
>
>
>
> Hello pimers,
>
>
>
> Today begins a two week call for adoption of draft-venaas-pim-reserved-bits-01. We had a good discussion on this draft in Montreal and now need formal support/non-support feedback from you on adoption of this draft.
>
>
>
> https://datatracker.ietf.org/doc/draft-venaas-pim-reserved-bits/
>
>
>
> thanks,
>
> mike
>
>
> _______________________________________________
> pim mailing list
> pim@ietf.org
> https://www.ietf.org/mailman/listinfo/pim