Re: [icnrg] [IANA #1280061] expert review for draft-irtf-icnrg-pathsteering (ccnx)

"David R. Oran" <daveoran@orandom.net> Fri, 29 September 2023 01:15 UTC

Return-Path: <daveoran@orandom.net>
X-Original-To: icnrg@ietfa.amsl.com
Delivered-To: icnrg@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 7AC49C15155F for <icnrg@ietfa.amsl.com>; Thu, 28 Sep 2023 18:15:52 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.907
X-Spam-Level:
X-Spam-Status: No, score=-1.907 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, RCVD_IN_ZEN_BLOCKED_OPENDNS=0.001, SPF_PASS=-0.001, T_SCC_BODY_TEXT_LINE=-0.01, URIBL_BLOCKED=0.001, URIBL_DBL_BLOCKED_OPENDNS=0.001, URIBL_ZEN_BLOCKED_OPENDNS=0.001] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (1024-bit key) header.d=crystalorb.net header.b="drxLIBA2"; dkim=neutral reason="invalid (unsupported algorithm ed25519-sha256)" header.d=crystalorb.net header.b="Uur4SADy"
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 zfMmx-OEKpBw for <icnrg@ietfa.amsl.com>; Thu, 28 Sep 2023 18:15:48 -0700 (PDT)
Received: from crystalorb.net (omega.crystalorb.net [IPv6:2600:3c01:e000:42e::1]) (using TLSv1.3 with cipher TLS_AES_256_GCM_SHA384 (256/256 bits) key-exchange ECDHE (P-256) server-signature RSA-PSS (2048 bits) server-digest SHA256) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 0050FC1516E1 for <icnrg@irtf.org>; Thu, 28 Sep 2023 18:15:47 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; q=dns/txt; c=relaxed/relaxed; d=crystalorb.net; s=mail; h=To:In-Reply-To:Cc:References:Message-Id:Date: Subject:Mime-Version:From:Content-Transfer-Encoding:Content-Type:From:Sender: Reply-To:Subject:Date:Message-ID:To:Cc:MIME-Version:Content-Type: Content-Transfer-Encoding:Content-ID:Content-Description:Resent-Date: Resent-From:Resent-Sender:Resent-To:Resent-Cc:Resent-Message-ID:In-Reply-To: References:List-Id:List-Help:List-Unsubscribe:List-Subscribe:List-Post: List-Owner:List-Archive; bh=8lBoFREZB0JTiw4DtqjasPkDtXbenBieSq9DHYR43t8=; b=d rxLIBA2IznUQndsSAPIVQRnaeiQ4b/2By3vhL3LGg+fLw+Dggwn6QBzG/yHGGCXRbFFv7wqHJRasx YmYGU0GzE0j/DvOA37aNUUXbUu9bRwPSkaicCkUBOaZpmv4lLbTP/EaVtt4n7iTQb1Cg2WcLzwTAc 8ayTdkpXl/OHYg4M=;
DKIM-Signature: v=1; a=ed25519-sha256; q=dns/txt; c=relaxed/relaxed; d=crystalorb.net; s=omegamail; h=To:In-Reply-To:Cc:References:Message-Id:Date :Subject:Mime-Version:From:Content-Transfer-Encoding:Content-Type:From:Sender :Reply-To:Subject:Date:Message-ID:To:Cc:MIME-Version:Content-Type: Content-Transfer-Encoding:Content-ID:Content-Description:Resent-Date: Resent-From:Resent-Sender:Resent-To:Resent-Cc:Resent-Message-ID:In-Reply-To: References:List-Id:List-Help:List-Unsubscribe:List-Subscribe:List-Post: List-Owner:List-Archive; bh=8lBoFREZB0JTiw4DtqjasPkDtXbenBieSq9DHYR43t8=; b=U ur4SADyOsdPZ99C5Dv71ak4/lyTZj/Jjigzv4R+5qngY6lgULc1M/RpuyDI2kKHgZI3UHEs/BRsBU pLWWHlAQ==;
Received: from [2601:184:407f:80cf:bc08:bc56:175b:5fba] (helo=smtpclient.apple) by crystalorb.net with esmtpsa (TLS1.3) tls TLS_ECDHE_RSA_WITH_AES_128_GCM_SHA256 (Exim 4.94.2) (envelope-from <daveoran@orandom.net>) id 1qm22h-00Cb68-2w; Thu, 28 Sep 2023 18:11:43 -0700
Content-Type: multipart/signed; boundary="Apple-Mail-F40EF85F-3F5D-48EE-8045-ECDCEAC1F3BA"; protocol="application/pkcs7-signature"; micalg="sha-256"
Content-Transfer-Encoding: 7bit
From: "David R. Oran" <daveoran@orandom.net>
Mime-Version: 1.0 (1.0)
Date: Thu, 28 Sep 2023 21:14:35 -0400
Message-Id: <B207A78A-041F-4273-AF91-032F98045D81@orandom.net>
References: <rt-5.0.3-1542532-1695945191-1392.1280061-37-0@icann.org>
Cc: icnrg@irtf.org, asaeda@nict.go.jp
In-Reply-To: <rt-5.0.3-1542532-1695945191-1392.1280061-37-0@icann.org>
To: drafts-expert-review@iana.org
X-Mailer: iPad Mail (21A351)
X-SA-Exim-Connect-IP: 2601:184:407f:80cf:bc08:bc56:175b:5fba
X-SA-Exim-Mail-From: daveoran@orandom.net
X-SA-Exim-Scanned: No (on crystalorb.net); SAEximRunCond expanded to false
Archived-At: <https://mailarchive.ietf.org/arch/msg/icnrg/s7AMteCIznXxEkVbLp80ltLzLbM>
Subject: Re: [icnrg] [IANA #1280061] expert review for draft-irtf-icnrg-pathsteering (ccnx)
X-BeenThere: icnrg@irtf.org
X-Mailman-Version: 2.1.39
Precedence: list
List-Id: Information-Centric Networking research group discussion list <icnrg.irtf.org>
List-Unsubscribe: <https://www.irtf.org/mailman/options/icnrg>, <mailto:icnrg-request@irtf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/icnrg/>
List-Post: <mailto:icnrg@irtf.org>
List-Help: <mailto:icnrg-request@irtf.org?subject=help>
List-Subscribe: <https://www.irtf.org/mailman/listinfo/icnrg>, <mailto:icnrg-request@irtf.org?subject=subscribe>
X-List-Received-Date: Fri, 29 Sep 2023 01:15:52 -0000

See below - IANA does not manage the registries for NDN. The NDN community and NDN research project does.
___________________________
iDevice - please excuse typos.

> On Sep 28, 2023, at 7:49 PM, Amanda Baber via RT <drafts-expert-review@iana.org> wrote:
> 
> Hi Hitoshi (cc: ICNRG),
> 
> Does the new version of the document (published today) address your concerns?
> 
> https://datatracker.ietf.org/doc/html/draft-irtf-icnrg-pathsteering-06
> 
> There is an issue for us: the IANA Considerations section has removed the request to register four of the five entries in Table 2, but Table 2 itself hasn't been removed, and is labeled "TLV-TYPE number assignments for NDN," which seems to indicate an action for IANA.
> 
No, IANA is not needed to do assignments for NDN.

Thanks!

> thanks,
> Amanda
> 
>> On Tue Sep 12 05:58:50 2023, asaeda@nict.go.jp wrote:
>> Hi folks and pathsteering draft authors,
>> 
>> I reviewed the pathsteering draft and have couple of comments.
>> 
>> At first I'd like to ask about the following Table 2 mentioned in
>> section 3.3 (Path label encoding for NDN).
>> 
>> Flag    (Suggested) Value (hex)
>> T_PATH_LABEL    0x0A
>> T_PATH_LABEL_FLAGS      0x0B
>> T_PATH_LABEL_BITMAP     0x0D
>> T_PATH_LABEL_NEXTHOP_LABEL      0x0E
>> T_PATH_LABEL_HOP_COUNT  0x0F
>> 
>> Table 2: TLV-TYPE number assignments
>> 
>> Except T_PATH_LABEL, there are no explanation about these types in
>> this draft. What are these labels used? It is necessary to explain all
>> of these types and scenarios how they use.
>> Even though this section title is with NDN (not CCNx), you are asking
>> the IANA assignment for these five type values in CCNx registry. You
>> may want to move this table to a different section.
>> 
>> In IANA consideration section, the authors say;
>> "1. Please assign the value 0x0004 (if still available) for
>> T_PATH_LABEL in the CCNx Hop-by-Hop Types registry established by
>> [RFC8609]."
>> But 0x0004 is already reserved by rfc8609, meaning it is not
>> available. Instead you can request 0x000A. BTW, you mentioned
>> T_PATH_LABEL in Table 2. Are they same even though you assigned
>> different values in this section (0x0004) and Table 2 (0x0A)?
>> 
>> "4. Please create the CCNx Path Label Flags registry and assign the
>> values listed in Table 1. The registration procedure for this registry
>> should be "Specification Required" as defined in [RFC8126]."
>> My question is where the CCNx Path Label Flags are specified in a
>> CCNx packet? Under which TLV field, this new TLV field is encoded?
>> 
>> Going back to section 3.1 (Path label TLV), two type values,
>> T_RETURN_INVALID_PATH_LABEL and T_RETURN_MALFORMED_INTEREST, are
>> defined for interest return. But only T_RETURN_INVALID_PATH_LABEL is
>> mentioned in the IANA section.
>> 
>> I think it is necessary to revise the draft.
>> 
>> Regards,
>> 
>> Hitoshi
>> 
>> 
>>> On Sep 5, 2023, at 3:36, Amanda Baber via RT <drafts-expert-
>>> review@iana.org> wrote:
>>> 
>>> Hi Hitoshi  (cc: ICNRG),
>>> 
>>> Sorry, looks like I didn't copy the list on my initial request!
>>> Adding them now.
>>> 
>>> thanks,
>>> Amanda
>>> 
>>> On Sun Sep 03 06:29:48 2023, asaeda@nict.go.jp wrote:
>>>> Dear Amanda,
>>>> 
>>>> I'll reply you before Sep. 14.
>>>> (Were your mail sent to ICNRG ML?)
>>>> 
>>>> Regards,
>>>> 
>>>> Hitoshi
>>>> 
>>>>> On Sep 1, 2023, at 9:52, Amanda Baber via RT <drafts-expert-
>>>>> review@iana.org> wrote:
>>>>> 
>>>>> Dear Hitoshi (cc: ICNRG),
>>>>> 
>>>>> As a designated expert for the "CCNx Interest Return Code Types"
>>>>> registry, can you review the proposed registration in this document
>>>>> for us?
>>>>> 
>>>>> https://datatracker.ietf.org/doc/html/draft-irtf-icnrg-pathsteering
>>>>> 
>>>>> The due date is September 14th.
>>>>> 
>>>>> If this is OK, when we're asked to implement the registry actions
>>>>> for
>>>>> this document, we'll make the registration at
>>>>> 
>>>>> http://www.iana.org/assignments/ccnx
>>>>> 
>>>>> With thanks,
>>>>> 
>>>>> Amanda Baber
>>>>> IANA Operations Manager
>>>>> 
>>>>> 
>>> 
> 
> _______________________________________________
> icnrg mailing list
> icnrg@irtf.org
> https://www.irtf.org/mailman/listinfo/icnrg