Re: [pim] Zaheduzzaman Sarker's Discuss on draft-ietf-pim-null-register-packing-14: (with DISCUSS)
Alvaro Retana <aretana.ietf@gmail.com> Wed, 01 March 2023 11:39 UTC
Return-Path: <aretana.ietf@gmail.com>
X-Original-To: pim@ietfa.amsl.com
Delivered-To: pim@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 695D1C14CE44; Wed, 1 Mar 2023 03:39:31 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.098
X-Spam-Level:
X-Spam-Status: No, score=-2.098 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, DKIM_VALID_EF=-0.1, FREEMAIL_FROM=0.001, RCVD_IN_DNSWL_NONE=-0.0001, RCVD_IN_ZEN_BLOCKED_OPENDNS=0.001, SPF_HELO_NONE=0.001, SPF_PASS=-0.001] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (2048-bit key) header.d=gmail.com
Received: from mail.ietf.org ([50.223.129.194]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id jidrUf4_munJ; Wed, 1 Mar 2023 03:39:30 -0800 (PST)
Received: from mail-pf1-x42f.google.com (mail-pf1-x42f.google.com [IPv6:2607:f8b0:4864:20::42f]) (using TLSv1.3 with cipher TLS_AES_128_GCM_SHA256 (128/128 bits) key-exchange X25519 server-signature RSA-PSS (2048 bits) server-digest SHA256) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id DAC44C14CEFF; Wed, 1 Mar 2023 03:39:30 -0800 (PST)
Received: by mail-pf1-x42f.google.com with SMTP id n2so7685569pfo.12; Wed, 01 Mar 2023 03:39:30 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20210112; h=content-transfer-encoding:cc:to:subject:message-id:date :mime-version:references:in-reply-to:from:from:to:cc:subject:date :message-id:reply-to; bh=LvjZErkrKRi90ssoJWYr4T0oN5T0ETX3JeIG0saNZ34=; b=GDZsOwxbd4OFcJSIabZJyMMHYnDirEgZwwcy+mU1xhDyMBQC+RJyW8memX7huvLdV2 CrCHJ+m5+e+O696QmfyTSMKOPujHkvyO1pAfRmzLPA6UAOVFp80SXrQiaoBWK0XYiZbD G9uchjvaSBqHmW0Q7l87uwKiapRHXdkAlT/muhGjOgmvJoQWyAQiDORYwm37UrsjPxIh xjA6GzQ3w7Q2eaX+nbRHfGcXFvMeomV+SywlLMr658r5yrRwNKV22KVySRUYfvsHKuRn hvhSybgrymy/9bW9ANioyg9ITvv0YVvlVJ3KmIi69r0jIRBCGWG4F3tw80CDmYBuXeu0 GB+g==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20210112; h=content-transfer-encoding:cc:to:subject:message-id:date :mime-version:references:in-reply-to:from:x-gm-message-state:from:to :cc:subject:date:message-id:reply-to; bh=LvjZErkrKRi90ssoJWYr4T0oN5T0ETX3JeIG0saNZ34=; b=kpVVVRKe+sOhPNQhW4hI1Trhqa3yiAFeGo9BQm2ln4jmEKbEt2DlkJl3QE8JBjIg+e +48kk7kTk6j5tZaGty5Y7rYhdHA5LSwVx8tUus4ZC8vmOEY6lkudCcpasN9Ga8D180xM PF3FBkrMT7Lox191jQQJwPgPzKjHNV4FzcNg9DbvgJ0lbtjaD6D3BW0BmxYANxTHpuyA pBQw/0uyZFoIXMlC2arAwV7EtWc1sWexgnfdEFa4wUZtNmQL6IsnghQ+yZZa6bs1f5tZ AI55ArijGyQ08P3wxU46/fnjwREtRIIphjX3sd9c76h+ebwNtTICmJOyzP8ByQ7oey7q MvrA==
X-Gm-Message-State: AO0yUKVaigWnn+RUgqtO7YcesWTl6SC0rZrqzbg1fUYZWkPchKo4MwfD np1yhxzfW8h+bGHPAzoKsdwkqoltYpe/qwvN2oXpknSM
X-Google-Smtp-Source: AK7set+9uIkjRXIndDZ2AVvO64/XmgkUGhDhfBdvQg4QdG+setB1oyof2H5Eh+a7Bpyw+jqpviy8+W7IEyx2JtpwJio=
X-Received: by 2002:a05:6a00:bc3:b0:590:3182:933a with SMTP id x3-20020a056a000bc300b005903182933amr2313629pfu.1.1677670769556; Wed, 01 Mar 2023 03:39:29 -0800 (PST)
Received: from 1058052472880 named unknown by gmailapi.google.com with HTTPREST; Wed, 1 Mar 2023 03:39:28 -0800
From: Alvaro Retana <aretana.ietf@gmail.com>
In-Reply-To: <167761405187.37670.6526616540879325374@ietfa.amsl.com>
References: <167761405187.37670.6526616540879325374@ietfa.amsl.com>
MIME-Version: 1.0
Date: Wed, 01 Mar 2023 03:39:28 -0800
Message-ID: <CAMMESsxiV6Ywob4F5+Brsf+RE4_wreNX8XpqpnYXVD0vFwn7Aw@mail.gmail.com>
To: The IESG <iesg@ietf.org>, Zaheduzzaman Sarker <zaheduzzaman.sarker@ericsson.com>
Cc: pim-chairs@ietf.org, Mike McBride <mmcbride7@gmail.com>, draft-ietf-pim-null-register-packing@ietf.org, pim@ietf.org
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
Archived-At: <https://mailarchive.ietf.org/arch/msg/pim/DULGSgZoM0o7OfYUX95VpWkjRUk>
Subject: Re: [pim] Zaheduzzaman Sarker's Discuss on draft-ietf-pim-null-register-packing-14: (with DISCUSS)
X-BeenThere: pim@ietf.org
X-Mailman-Version: 2.1.39
Precedence: list
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, 01 Mar 2023 11:39:31 -0000
On February 28, 2023 at 2:54:12 PM, Zaheduzzaman Sarker wrote: Zahed: Hi! Thanks for the review! > ---------------------------------------------------------------------- > DISCUSS: > ---------------------------------------------------------------------- > > Thanks for working on this document. > > I would like to discuss - what is the "P" bit in section 2 and what is "FB" in > section 3? without proper description of those fields this specification will > be confusing to be implemented. May be I have missed something in the > referenced specifications, in that case I would prefer to have the references > properly stated here. The P-bit is first mentioned in the text in §5 as "P-bit (Flag bit TBD1)". But the definition of the "Packing Capability bit" didn't explicitly call the it P-bit, I see the confusion. Suggestion (for §2)> OLD> Packing Capability bit (Flag Bit TBD1): When set, it indicates the ability of the RP to receive PIM Packed Null-Register messages, and send PIM Packed Register-Stop messages. NEW> Packing Capability bit (P-bit / Flag Bit TBD1): When set, it indicates the ability of the RP to receive PIM Packed Null-Register messages, and send PIM Packed Register-Stop messages. The FB ("flag bits") field is part of the common header -- there's a reference to rfc8736 right after figures 2 and 3. For the new message types this document is requesting, Figure 3/rfc8736 applies: 5. PIM Type Space Extension This document defines types 13, 14, and 15, such that each of these types has 16 subtypes, providing a total of 48 subtypes available for future PIM extensions. This is achieved by defining a new Subtype field (see Figure 3) using the four most significant flag bits (bits 4-7). The notation type.subtype is used to reference these new extended types. The remaining four flag bits (bits 0-3) are reserved to be used by each extended type (abbreviated as FB below). 0 1 2 3 0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ |PIM Ver| Type |Subtype| FB | Checksum | +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ Figure 3: Subtypes Do you want the authors to add something specific to this document? Thanks! Alvaro.
- [pim] Zaheduzzaman Sarker's Discuss on draft-ietf… Zaheduzzaman Sarker via Datatracker
- Re: [pim] Zaheduzzaman Sarker's Discuss on draft-… Alvaro Retana
- Re: [pim] Zaheduzzaman Sarker's Discuss on draft-… Ananya Gopal (ananygop)
- Re: [pim] Zaheduzzaman Sarker's Discuss on draft-… Zaheduzzaman Sarker