Re: [icnrg] [IANA #1280061] expert review for draft-irtf-icnrg-pathsteering (ccnx)
Hitoshi Asaeda <asaeda@nict.go.jp> Fri, 29 September 2023 05:16 UTC
Return-Path: <asaeda@nict.go.jp>
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 CAC89C16B5CF for <icnrg@ietfa.amsl.com>; Thu, 28 Sep 2023 22:16:56 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.108
X-Spam-Level:
X-Spam-Status: No, score=-2.108 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIMWL_WL_HIGH=-0.001, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, DKIM_VALID_EF=-0.1, RCVD_IN_DNSWL_NONE=-0.0001, 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 (2048-bit key) header.d=nict.go.jp
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 LnGK21-JtJKy for <icnrg@ietfa.amsl.com>; Thu, 28 Sep 2023 22:16:51 -0700 (PDT)
Received: from mo-csw.securemx.jp (mo-csw1122.securemx.jp [210.130.202.158]) (using TLSv1.3 with cipher TLS_AES_256_GCM_SHA384 (256/256 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 4C4A3C16B5A3 for <icnrg@irtf.org>; Thu, 28 Sep 2023 22:16:50 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=nict.go.jp; h=Content-Type: Mime-Version:Subject:From:In-Reply-To:Date:Cc:Content-Transfer-Encoding: Message-Id:References:To;i=asaeda@nict.go.jp;s=key1.smx;t=1695964585;x= 1697174185; bh=Yd5xJ2iInszL/gJXQb/Wj0tJygM4ij83zU2bpRDtQe4=; b=X6XbXSnzkOAw7JJh uFBZ23+xw4Ane5O8sOkzUm4JfThHzP4Kx0FgxPbMTZ9FyjpbaKlN9n2V2qb8fSwF1LItjD/9evLj/ C3y3L18myTZp+BLPQl6fRslvaQbdeiq/fR2coaHp1vP5hmz2sAh4MRrl5Zg2UF+QnWYSCyvKDN3WG 14JQsrurdh3ct4bcU5F9m6tPGSvX7ia1bpzRzwLvX6OQDU5qA1eLsELRWbk5hRJezoB8QCKBwmGyu FfNfr4nOosv56b8ascQeqwr4LcJ2SdQWmUWxsNMHNmZU0wsXAGC4O8FYccJe31jQ0rFff9S+M0SuG 8XjiXe2sxvDBQjb8kQ==;
Received: by mo-csw.securemx.jp (mx-mo-csw1122) id 38T5GOds3437936; Fri, 29 Sep 2023 14:16:25 +0900
X-Iguazu-Qid: 2rWhuPPyFLpxSPNICw
X-Iguazu-QSIG: v=2; s=0; t=1695964584; q=2rWhuPPyFLpxSPNICw; m=/qvvqKCRY9/fa3xyVGsVfgsLMs+qLuS6fPr9xFQf5u8=
Received: from mail2.nict.go.jp (mail2.nict.go.jp [133.243.18.15]) by relay.securemx.jp (mx-mr1122) id 38T5GNA62682978 (version=TLSv1.2 cipher=ECDHE-RSA-AES128-GCM-SHA256 bits=128 verify=NOT); Fri, 29 Sep 2023 14:16:24 +0900
Received: from smtpclient.apple (ssh1.nict.go.jp [133.243.3.49]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by mail2.nict.go.jp (NICT Mail Spool Server2) with ESMTPSA id B11E653716; Fri, 29 Sep 2023 14:16:06 +0900 (JST)
Content-Type: text/plain; charset="us-ascii"
Mime-Version: 1.0 (Mac OS X Mail 16.0 \(3696.120.41.1.4\))
From: Hitoshi Asaeda <asaeda@nict.go.jp>
In-Reply-To: <rt-5.0.3-1542532-1695945191-1392.1280061-37-0@icann.org>
Date: Fri, 29 Sep 2023 14:16:06 +0900
Cc: icnrg@irtf.org
Content-Transfer-Encoding: quoted-printable
Message-Id: <4E3C2214-C2DF-431D-8B48-9DEFB9950C9F@nict.go.jp>
References: <RT-Ticket-1280061@icann.org> <rt-5.0.3-1748910-1693529102-1110.1280061-37-0@icann.org> <rt-5.0.3-1754003-1693529557-575.1280061-37-0@icann.org> <50A22A97-206E-4E3E-BD30-35BF8C6DD85A@nict.go.jp> <rt-5.0.3-239771-1693722588-604.1280061-37-0@icann.org> <rt-5.0.3-419213-1693852562-997.1280061-37-0@icann.org> <FD174BF1-ECA2-4C3F-AA4D-223ECF38797E@nict.go.jp> <rt-5.0.3-2033283-1694498330-605.1280061-37-0@icann.org> <rt-5.0.3-1542532-1695945191-1392.1280061-37-0@icann.org>
To: drafts-expert-review@iana.org
X-Mailer: Apple Mail (2.3696.120.41.1.4)
Archived-At: <https://mailarchive.ietf.org/arch/msg/icnrg/WwVzQVjGuDL2ApfgsOzByRx71OA>
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 05:16:56 -0000
Hi Amanda and all, I've reviewed the revised draft. I confirmed all of my comments were addressed. One minor point is that this document requests assigning the value 0xA (if available) for the T_RETURN_INVALID_PATH_LABEL, but "0xA" should be "0x0A". I believe it will be corrected whenever this document enters AUTH48, though. Thanks. Regards, Hitoshi > On Sep 29, 2023, at 8:53, 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. > > 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] [IANA #1280061] expert review for draft-i… Amanda Baber via RT
- Re: [icnrg] [IANA #1280061] expert review for dra… Hitoshi Asaeda
- Re: [icnrg] [IANA #1280061] expert review for dra… David R. Oran
- [icnrg] [IANA #1280061] expert review for draft-i… Amanda Baber via RT
- Re: [icnrg] [IANA #1280061] expert review for dra… David R. Oran
- Re: [icnrg] [IANA #1280061] expert review for dra… Colin Perkins
- Re: [icnrg] [IANA #1280061] expert review for dra… Hitoshi Asaeda
- [icnrg] [IANA #1280061] expert review for draft-i… Amanda Baber via RT
- Re: [icnrg] [IANA #1280061] expert review for dra… Colin Perkins
- Re: [icnrg] [IANA #1280061] expert review for dra… Colin Perkins