Re: [Gen-art] Genart last call review of draft-ietf-ippm-stamp-option-tlv-06
Greg Mirsky <gregimirsky@gmail.com> Thu, 02 July 2020 19:22 UTC
Return-Path: <gregimirsky@gmail.com>
X-Original-To: gen-art@ietfa.amsl.com
Delivered-To: gen-art@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id DA7A83A0365; Thu, 2 Jul 2020 12:22:31 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -0.596
X-Spam-Level:
X-Spam-Status: No, score=-0.596 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, HTML_COMMENT_SAVED_URL=1.391, HTML_MESSAGE=0.001, HTML_TAG_BALANCE_BODY=0.1, SPF_HELO_NONE=0.001, SPF_PASS=-0.001, T_HTML_ATTACH=0.01, URIBL_BLOCKED=0.001] autolearn=no autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (2048-bit key) header.d=gmail.com
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 3gub_JqKJF3Z; Thu, 2 Jul 2020 12:22:19 -0700 (PDT)
Received: from mail-lj1-x243.google.com (mail-lj1-x243.google.com [IPv6:2a00:1450:4864:20::243]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 6DF973A02C1; Thu, 2 Jul 2020 12:22:18 -0700 (PDT)
Received: by mail-lj1-x243.google.com with SMTP id s1so33681070ljo.0; Thu, 02 Jul 2020 12:22:18 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20161025; h=mime-version:references:in-reply-to:from:date:message-id:subject:to :cc; bh=tOjI7F4GlPpusA+KhdAUxmPdYHrFR5+AMuuvgo1aR1o=; b=rhoXsREJ/QY0UEjwGiUkEmA6Cg1SmrgF5bnoVBlGIo+JvniLZNkBrVox7B1xUxhugQ Qa1Is49b8bNsOwJ7uusRk3XIr7yDyxHEYQD/DCbhBEi5z68/RFi0UyUy+ZrrkYfnW5Ei ztACSLf0+QOFg69yTxLmU+GztoQDzXgvNsRmwYejTFcJa8Xsxi4JOY3yRy274oTzgLuS HG70QkZ3ctMwMpQK+DD/SvSaPaqxEvRac51NhvZeWFmD/IZCZk3Ut1YTtjvZ1YfkPeIG 8PVA5SsMMeTvon4oODje7faTwZ2I/ytxLqalv6XqxLQSKi9wga2ZT2xJxeLPI8g1UPJe KsUw==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:mime-version:references:in-reply-to:from:date :message-id:subject:to:cc; bh=tOjI7F4GlPpusA+KhdAUxmPdYHrFR5+AMuuvgo1aR1o=; b=Ivs8fWvreRpww7Cu5mErtq1PkjIVrx2crgXVWN6yfpBIEj4QzmJ6hkjU0Ekvabr/io AVWUm0AcbMHwrdaDLDrWO6xuy19x4CR8vhLQM92upop3ZHEMPRjJ0d6HqLw060GcROhG WKxOkenFppRnVFE9HKr3tbdX2Cdm1ZQQZMvl8i8y7gELmc8KYMaqssFh58GGGfgNJHP8 +yUT3YFm7ftl3Ddm+8Bpg3sOgxI5gYXgKPqsN/d5sG5tI0/Hu3BhfaphWcR5VMXkzp6N POJif+hBPO24dxGzAsISsVkmUOVdxs7gNBxQJUTcHyVeqzQx85ielxMJI1Xc+6C9+W6m 89vg==
X-Gm-Message-State: AOAM532FkO5W6sMR5CeHqlfhOJX65YANaqjpkyUDptpgXUWRAvxHx48L AQG2dKvKwG/mpQoop3H3Na23BH0gnsk/CekAZjc=
X-Google-Smtp-Source: ABdhPJxWcQrvGxIEhnpiQmUjHQyf0d9B/JTXxmxJOqHcq+N9fGpuSmFmHfnjI2pT3byJubFTip6musD9oxTHca5YQV8=
X-Received: by 2002:a2e:b88c:: with SMTP id r12mr16970411ljp.266.1593717736301; Thu, 02 Jul 2020 12:22:16 -0700 (PDT)
MIME-Version: 1.0
References: <159344297273.15718.9292174200591066435@ietfa.amsl.com>
In-Reply-To: <159344297273.15718.9292174200591066435@ietfa.amsl.com>
From: Greg Mirsky <gregimirsky@gmail.com>
Date: Thu, 02 Jul 2020 12:22:04 -0700
Message-ID: <CA+RyBmVjSezyTs=r4zL4OjzzK5eG1SMZHLs+5NoNhwniZYx18w@mail.gmail.com>
To: Dan Romascanu <dromasca@gmail.com>
Cc: gen-art@ietf.org, draft-ietf-ippm-stamp-option-tlv.all@ietf.org, last-call@ietf.org, IETF IPPM WG <ippm@ietf.org>
Content-Type: multipart/mixed; boundary="0000000000008bc18b05a97a53f3"
Archived-At: <https://mailarchive.ietf.org/arch/msg/gen-art/N2WkErpAU3csp7yIdpDbInkfmko>
X-Mailman-Approved-At: Thu, 02 Jul 2020 16:33:01 -0700
Subject: Re: [Gen-art] Genart last call review of draft-ietf-ippm-stamp-option-tlv-06
X-BeenThere: gen-art@ietf.org
X-Mailman-Version: 2.1.29
Precedence: list
List-Id: "GEN-ART: General Area Review Team" <gen-art.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/gen-art>, <mailto:gen-art-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/gen-art/>
List-Post: <mailto:gen-art@ietf.org>
List-Help: <mailto:gen-art-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/gen-art>, <mailto:gen-art-request@ietf.org?subject=subscribe>
X-List-Received-Date: Thu, 02 Jul 2020 19:22:32 -0000
Hi Dan, thank you for your review, detailed questions, and helpful suggestions. Please find my answers and notes below tagged GIM>>. Regards, Greg On Mon, Jun 29, 2020 at 8:02 AM Dan Romascanu via Datatracker < noreply@ietf.org> wrote: > Reviewer: Dan Romascanu > Review result: Ready with Issues > > I am the assigned Gen-ART reviewer for this draft. The General Area > Review Team (Gen-ART) reviews all IETF documents being processed > by the IESG for the IETF Chair. Please treat these comments just > like any other last call comments. > > For more information, please see the FAQ at > > <https://trac.ietf.org/trac/gen/wiki/GenArtfaq>. > > Document: draft-ietf-ippm-stamp-option-tlv-06 > Reviewer: Dan Romascanu > Review Date: 2020-06-29 > IETF LC End Date: 2020-07-06 > IESG Telechat date: Not scheduled for a telechat > > Summary: Ready with issues > > This is a clear, well-written document. There are a few minor issues that > would > benefit from clarifications and possible edits before approval. > > Major issues: > > Minor issues: > > 1. Section 3. Is there any recommended strategy to generate SSIDs? Are > these > supposed to be generated sequentially? Randomly? How soon is the 16 -bit > space > supposed to wrap-up? Some clarification would be useful I believe. > GIM>> Because test sessions, in general, will be performed for different periods of time, implementation will need to manage the pool of available identifiers. I agree, the initial allocation may use sequential ascending increment by one method, but at some point, it will be "get-the-next-available number". I propose to update the text as follows: OLD TEXT: A STAMP Session-Sender MAY generate a locally unique STAMP Session Identifier (SSID). SSID is two octets long non-zero unsigned integer. NEW TEXT: A STAMP Session-Sender MAY generate a locally unique STAMP Session Identifier (SSID). SSID is two octets long non-zero unsigned integer. SSID generation policy is implementation-specific. For example, sequentially ascending incremented by one method could be used for the initial allocation of SSID. Because of test sessions lasting different time an implementation that uses SSID MUST monitor the pool of available identifiers. An implementation SHOULD NOT assign the same identifier to different STAMP test sessions. > > 2. Section 4.5 - how is the value Session-Sender Tx counter (S_TxC) > determined > by the sender? > GIM>> The value of S_TxC is the current value of the transmitted in-profile packets. Would the following update (also addressing the #3) make it clearer? OLD TEXT: o Session-Sender Tx counter (S_TxC) is four octets long field. o Session-Reflector Rx counter (R_RxC) is four octets long field. MUST be zeroed by the Session-Sender and filled by the Session- Reflector. o Session-Reflector Tx counter (R_TxC) is four octets long field. MUST be zeroed by the Session-Sender and filled by the Session- Reflector. NEW TEXT: o Session-Sender Tx counter (S_TxC) is four octets long field. The Session-Reflector MUST set its value equal to the number of the transmitted in-profile packets. o Session-Reflector Rx counter (R_RxC) is four octets long field. MUST be zeroed by the Session-Sender on transmit and ingored by the Session-Reflector on receipt. The Session-Reflector MUST fill it with the value of in-profile packets received. o Session-Reflector Tx counter (R_TxC) is four octets long field. MUST be zeroed by the Session-Sender and ignored by the Session- Reflector on receipt. The Session-Reflector MUST fill with the value of the transmitted in-profile packets. > > 3. Section 4.5 - (R_RxC) and (R_TxC) MUST be zeroed by the Session-Sender > - Is > this verified at reception? What happens if a Session-Reflector detects a > non-zero value in one of these fields? > GIM>> Please let us know if the update above addresses your concern. > > 4. Section 4.6 - it seems that understanding [TS23501] is needed to > properly > implement this section and interpret the content of the TLV. Should not > this > reference be Normative rather than Informative? > GIM>> Agreed and moved it to the list of Normative References > > 5. Section 5.2 - as the values for Synchronization Sources in Table 4 > refer to > 'this document', it seems to be necessary to include in this document > references to the documents that define the respective terms / sources > GIM>> The only convenient place for references I see is in the Acronyms section. Would you suggest another section in the document? Besides the location, some of the listed sources of synchronization do not have a standard specification, e.g. BITS/SSU, or the specification is not easily available, e.g., Russian government's GLONASS. Some systems, like LORAL-C, are in the process of being decommissioned and only a few LORAL transmitters remain operational. Would adding references to NTP and PTP in the Acronyms section be acceptable? BITS Building Integrated Timing Supply CoS Class of Service DSCP Differentiated Services Code Point ECN Explicit Congestion Notification GLONASS Global Orbiting Navigation Satellite System GPS Global Positioning System [GPS] HMAC Hashed Message Authentication Code LORAN-C Long Range Navigation System Version C MBZ Must Be Zero NTP Network Time Protocol [RFC5905] PMF Performance Measurement Function PTP Precision Time Protocol [IEEE.1588.2008] TLV Type-Length-Value SSID STAMP Session Identifier SSU Synchronization Supply Unit STAMP Simple Two-way Active Measurement Protocol > > 6. Section 6 - Security Considerations: Is not sending of test packets to a > reflector that does not support SSID a potential sourse for DoS attacks? GIM>> A Session-Reflector that does not support SSID would transmit reflected test packet with SSID field zeroed. The local to the Session-Sender policy will control whether the Session-Sender stops or continues the test session. > Same > question about sending packets with unsupported TLV types. How do > Reflectors > protect against such situations? As such attacks would be beyond STAMP base > specifications, it may be good to discuss these. > GIM>> A Session-Reflector that does not support STAMP extensions is not expected to compare the value in the Length field of the UDP header and the length of the STAMP base packet. Hence the Session-Reflector will transmit the base STAMP packet. It is the local policy on the Session-Sender (similar to the handling of SSID == 0 situation) that will control the Sender's behavior. I think the text might be appended to the second paragraph of Section 4. The updated paragraph is below: A STAMP node, whether Session-Sender or Session-Reflector, receiving a test packet MUST determine whether the packet is a base STAMP packet or includes one or more TLVs. The node MUST compare the value in the Length field of the UDP header and the length of the base STAMP test packet in the mode, unauthenticated or authenticated based on the configuration of the particular STAMP test session. If the difference between the two values is larger than the length of UDP header, then the test packet includes one or more STAMP TLVs that immediately follow the base STAMP test packet. A Session-Reflector that does not support STAMP extensions is not expected to compare the value in the Length field of the UDP header and the length of the STAMP base packet. Hence the Session-Reflector will transmit the base STAMP packet. It is the local policy on the Session-Sender (similar to the handling of SSID == 0 scenario described in Section 3) that will control the sender's behavior. > > Nits/editorial comments: > > 1. Section 2.1 - it's more convenient for future users of the document if > acronyms were listed in alphabetical order > GIM>> Agree. Done (please check it above). > > 2. Sections 4.6, 4.7 - inconsistent use of capitalization: > > Reserved - ... must be zeroed on transmission > and ignored on receipt. > > It's a 'must' in 4.6, and a 'MUST' in 4.7 > GIM>> Thank you for pointing it out. I've found two cases of "must" that changed to normative-style.
- [Gen-art] Genart last call review of draft-ietf-i… Dan Romascanu via Datatracker
- Re: [Gen-art] Genart last call review of draft-ie… Dan Romascanu
- Re: [Gen-art] Genart last call review of draft-ie… Greg Mirsky
- Re: [Gen-art] Genart last call review of draft-ie… Greg Mirsky
- Re: [Gen-art] [ippm] Genart last call review of d… Alissa Cooper
- Re: [Gen-art] [Last-Call] Genart last call review… Benjamin Kaduk
- Re: [Gen-art] [Last-Call] Genart last call review… Greg Mirsky
- Re: [Gen-art] [Last-Call] Genart last call review… Dan Romascanu
- Re: [Gen-art] [Last-Call] Genart last call review… Benjamin Kaduk
- Re: [Gen-art] [Last-Call] Genart last call review… Greg Mirsky
- Re: [Gen-art] [Last-Call] Genart last call review… Greg Mirsky