Re: [auth48] AUTH48: RFC-to-be 9521 <draft-ietf-nvo3-bfd-geneve-13> for your review
Greg Mirsky <gregimirsky@gmail.com> Tue, 19 December 2023 01:23 UTC
Return-Path: <gregimirsky@gmail.com>
X-Original-To: auth48archive@ietfa.amsl.com
Delivered-To: auth48archive@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id D4FDBC14CE52; Mon, 18 Dec 2023 17:23:06 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.105
X-Spam-Level:
X-Spam-Status: No, score=-2.105 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_MESSAGE=0.001, RCVD_IN_DNSWL_NONE=-0.0001, RCVD_IN_ZEN_BLOCKED_OPENDNS=0.001, SPF_HELO_NONE=0.001, SPF_PASS=-0.001, T_SCC_BODY_TEXT_LINE=-0.01, URIBL_DBL_BLOCKED_OPENDNS=0.001, URIBL_ZEN_BLOCKED_OPENDNS=0.001] autolearn=unavailable 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 Hp-JXPaQyF0Y; Mon, 18 Dec 2023 17:23:02 -0800 (PST)
Received: from mail-yb1-xb2d.google.com (mail-yb1-xb2d.google.com [IPv6:2607:f8b0:4864:20::b2d]) (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 9CC72C14EB17; Mon, 18 Dec 2023 17:22:57 -0800 (PST)
Received: by mail-yb1-xb2d.google.com with SMTP id 3f1490d57ef6-db3fa47c2f7so2448075276.0; Mon, 18 Dec 2023 17:22:57 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20230601; t=1702948976; x=1703553776; darn=rfc-editor.org; h=cc:to:subject:message-id:date:from:in-reply-to:references :mime-version:from:to:cc:subject:date:message-id:reply-to; bh=TQpCqEduCOo9uzASP9oySOv4533aHO6Uq5/leaQwEpU=; b=YiCBYekRfktQUG2f5UMfRod67jtvvrP6eplJwYsMWmNPdRKdi89qPpMjLFrJfcydVd 8pBdT63u0ZsI4fylSnJfGkgHpDhTtUQY/by4oLgxheOFKgV0R6nOMNO4sxD4ye/mEIg4 xWlO8aRzTucCyYprDS4Zbcfg+lyRzY5oPDkPVWw3l581fC1k4U4NsZAd9CtVJlAFnlg3 wKzCemmPaiftf9G/Xz6LZTM1+YFn2hsfsKTM6NJm0UbxGm0xrvV9CD5qetFn3mKcbUnc uxKs8xrEfHOLwCRQVxy//nm4BD3w6LgU34BEGIHDd4PaegbS563ikQ0ri/lEWX5LLwYq B1CQ==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20230601; t=1702948976; x=1703553776; h=cc:to:subject:message-id:date:from:in-reply-to:references :mime-version:x-gm-message-state:from:to:cc:subject:date:message-id :reply-to; bh=TQpCqEduCOo9uzASP9oySOv4533aHO6Uq5/leaQwEpU=; b=XmUz3wy3OpSDB+f/giUNPTrVuzi7pFfcOZ7DwDmcuy+cwJBHJjyto/rsTBOGDhQgNs WX389lN0eQ7E+djXfy5XwB8J6gd119G7PxGNkyiqk+/gTmdvTnNhks73eAiW9B73xfp9 tpAZf+E2X1ev4DDNewCETKfLKP2bv+E5MUMsCn1j/X9zMaq6jqqFGePMcF9bS3dQ4K1l CJJv0wkDMD+JOogn7JpSz4QPZ5zKhYnCoc7aDVCnRBST48avFVCsu4/zDA6gJeZfjBPW Q6efK7U5qGr8zxKU1wVDSFCdTk20hUCDflPIlqN37v+gN0P+ijINlaCfF6Dg4u6bA8Go Llvw==
X-Gm-Message-State: AOJu0Yxm4h0xxj/MDjXNCucMzYSvhmPwidcl8xfQzTdsigUXjSqPKJ/c V3a1aDH/KpMrL2zgyBui1edWQJ5ziYgaJ2tx0tE=
X-Google-Smtp-Source: AGHT+IFaSH/fO1Jw0MfBfl2H/MPZnjSuA6mQgdibDKWjCzAHGTeLT35WiP7BXzyS5H2Ka6lIo2uYj2uxLCCU/7EW1Nc=
X-Received: by 2002:a25:698b:0:b0:dbc:fa8a:e967 with SMTP id e133-20020a25698b000000b00dbcfa8ae967mr2639190ybc.25.1702948976250; Mon, 18 Dec 2023 17:22:56 -0800 (PST)
MIME-Version: 1.0
References: <AB267627-8E56-4DC0-A93D-895E2AD9BE46@amsl.com> <202312190909040526190@zte.com.cn>
In-Reply-To: <202312190909040526190@zte.com.cn>
From: Greg Mirsky <gregimirsky@gmail.com>
Date: Mon, 18 Dec 2023 17:22:44 -0800
Message-ID: <CA+RyBmVyKh6UPsXWoetaSXtVDrzMus=DSyM+5wUrnDokYMAeqQ@mail.gmail.com>
To: xiao.min2@zte.com.cn
Cc: mferguson@amsl.com, rfc-editor@rfc-editor.org, santosh.pallagatti@gmail.com, jefftant.ietf@gmail.com, aldrin.ietf@gmail.com, nvo3-ads@ietf.org, nvo3-chairs@ietf.org, matthew.bocci@nokia.com, andrew-ietf@liquid.tech, auth48archive@rfc-editor.org
Content-Type: multipart/alternative; boundary="000000000000ccd4f5060cd2b47a"
Archived-At: <https://mailarchive.ietf.org/arch/msg/auth48archive/5RPgzSq_aBtg7gIkv4D8zytJbUc>
Subject: Re: [auth48] AUTH48: RFC-to-be 9521 <draft-ietf-nvo3-bfd-geneve-13> for your review
X-BeenThere: auth48archive@rfc-editor.org
X-Mailman-Version: 2.1.39
Precedence: list
List-Id: "Archiving AUTH48 exchanges between the RFC Production Center, the authors, and other related parties" <auth48archive.rfc-editor.org>
List-Unsubscribe: <https://mailman.rfc-editor.org/mailman/options/auth48archive>, <mailto:auth48archive-request@rfc-editor.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/auth48archive/>
List-Post: <mailto:auth48archive@rfc-editor.org>
List-Help: <mailto:auth48archive-request@rfc-editor.org?subject=help>
List-Subscribe: <https://mailman.rfc-editor.org/mailman/listinfo/auth48archive>, <mailto:auth48archive-request@rfc-editor.org?subject=subscribe>
X-List-Received-Date: Tue, 19 Dec 2023 01:23:06 -0000
Hi Xiao Min, thank you for putting a light on this. I find two occurrences of If the BFD packet is received with a Your Discriminator equals to 0 ... I agree with you (apologies for the confusion my earlier response could have caused) that in the current form s/equals/equal/ is appropriate. But it could be that the whole passage is a bit too terse. Perhaps the following text may be used: NEW TEXT: If the BFD packet is received with the value of the Your Discriminator field 0 ... That update can be applied to both occasions of the text. WDYT? Regards, Greg On Mon, Dec 18, 2023 at 5:09 PM <xiao.min2@zte.com.cn> wrote: > Hi Megan, > > > Thank you for the revision. > > Considering the one rejected change, I propose one more editorial change > as below. > > Section #5.1 > OLD: > a Your Discriminator equals to 0 > NEW: > a Your Discriminator equal to 0 > > > Cheers, > > Xiao Min > Original > *From: *MeganFerguson <mferguson@amsl.com> > *To: *肖敏10093570;Greg Mirsky <gregimirsky@gmail.com>; > *Cc: *rfc-editor@rfc-editor.org <rfc-editor@rfc-editor.org>; > santosh.pallagatti@gmail.com <santosh.pallagatti@gmail.com>; > jefftant.ietf@gmail.com <jefftant.ietf@gmail.com>;aldrin.ietf@gmail.com < > aldrin.ietf@gmail.com>;nvo3-ads@ietf.org <nvo3-ads@ietf.org>; > nvo3-chairs@ietf.org <nvo3-chairs@ietf.org>;matthew.bocci@nokia.com < > matthew.bocci@nokia.com>;andrew-ietf@liquid.tech <andrew-ietf@liquid.tech > >;auth48archive@rfc-editor.org <auth48archive@rfc-editor.org>; > *Date: *2023年12月19日 05:38 > *Subject: **Re: AUTH48: RFC-to-be 9521 <draft-ietf-nvo3-bfd-geneve-13> > for your review* > Xiao and Greg, > > > Thank you for your replies. We have updated the document as requested with the exception of the following: > > > Section #4.1 > > OLD: > > a Your Discriminator equal to 0 > > NEW: > > a Your Discriminator equals to 0 > > > > > > Please review this request as the suggested text introduces a subject/verb agreement error. > > > We have posted the updated files below. Please review carefully as we do not make updates once the document is published as an RFC. > > The files have been posted here (please refresh): > https://www.rfc-editor.org/authors/rfc9521.txt > https://www.rfc-editor.org/authors/rfc9521.pdf > https://www.rfc-editor.org/authors/rfc9521.html > https://www.rfc-editor.org/authors/rfc9521.xml > > The relevant diff files have been posted here (please refresh): > https://www.rfc-editor.org/authors/rfc9521-diff.html > (comprehensive diff) > https://www.rfc-editor.org/authors/rfc9521-auth48diff.html > (AUTH48 changes only) > > Please contact us with any further updates/questions/comments you may have. > > > We will await approvals from each of the parties listed on the AUTH48 status page prior to moving forward to publication. > > > The AUTH48 status page for this document is available here: > > https://www.rfc-editor.org/auth48/rfc9521 > > Thank you. > > RFC Editor/mf > > > On Dec 18, 2023, at 1:29 AM, xiao.min2@zte.com.cn wrote: > > > > Dear RFC Editor, > > > > > > > > Thanks for your efforts. > > > Please see inline my answers to your questions and several proposed editorial changes. > > > > Original > > From: rfc-editor@rfc-editor.org <rfc-editor@rfc-editor.org> > > To: 肖敏10093570;gregimirsky@gmail.com <gregimirsky@gmail.com>; > santosh.pallagatti@gmail.com <santosh.pallagatti@gmail.com>; > jefftant.ietf@gmail.com <jefftant.ietf@gmail.com>;aldrin.ietf@gmail.com < > aldrin.ietf@gmail.com>; > > Cc: rfc-editor@rfc-editor.org <rfc-editor@rfc-editor.org>; > nvo3-ads@ietf.org <nvo3-ads@ietf.org>;nvo3-chairs@ietf.org < > nvo3-chairs@ietf.org>;matthew.bocci@nokia.com <matthew.bocci@nokia.com > >;andrew-ietf@liquid.tech <andrew-ietf@liquid.tech>; > auth48archive@rfc-editor.org <auth48archive@rfc-editor.org>; > > Date: 2023年12月16日 01:10 > > > Subject: Re: AUTH48: RFC-to-be 9521 <draft-ietf-nvo3-bfd-geneve-13> for your review > > Authors, > > > > > While reviewing this document during AUTH48, please resolve (as necessary) the following questions, which are also in the XML file. > > > > 1) <!-- [rfced] Please note that the title of the document has been > > updated as follows: > > > > Abbreviations have been expanded per Section 3.6 of RFC 7322 ("RFC > > Style Guide"). Please review. > > > > Original: > > BFD for Geneve > > > > Current: > > Bidirectional Forwarding Detection (BFD) for Generic Network > > Virtualization Encapsulation (Geneve) > > --> > > [XM]>>> Agreed. > > > > 2) <!-- [rfced] Please insert any keywords (beyond those that appear in > > the title) for use on https://www.rfc-editor.org/search. --> > > [XM]>>> NVE, VAP, VNI. > > > > 3) <!--[rfced] For clarity, may we rephrase the run-on sentence below? > > > > Original: > > This document supports establishing multiple BFD sessions between the > > same pair of NVEs, each BFD session over a pair of VAPs residing in > > the same pair of NVEs, there SHOULD be a mechanism to control the > > maximum number of such sessions that can be active at the same time. > > > > Perhaps: > > This document supports establishing multiple BFD sessions between the > > same pair of NVEs. For each BFD session over a pair of VAPs residing > > in the same pair of NVEs, there SHOULD be a mechanism to control the > > maximum number of such sessions that can be active at the same time. > > --> > > [XM]>>> Agreed. > > > > 4) <!-- [rfced] We see a number of uses of the "/" character separating > > terms in this document. Please review and let us know if we > > should adjust any of these instances to "and/or", "and", or "or" > > for clarity and ease of the reader. > > --> > > > [XM]>>> I don't see a need to adjust any of them. I believe it's common to say Ethernet/IP/UDP, Ethernet/IP, IP/UDP, etc. > > > > 5) <!-- [rfced] Please review the "Inclusive Language" portion of the > > online Style Guide > > <https://www.rfc-editor.org/styleguide/part2/#inclusive_language> > > and let us know if any changes are needed. > > > > Note that our script did not flag any words in particular, but this > > should still be reviewed as a best practice. > > --> > > [XM]>>> I don't see a need for any changes. Thank you for the reminder. > > > > > > > [XM]>>> Besides the above answers to your questions, I propose a few editorial changes as below. > > > > Section #1 > > OLD: > > For simplicity, NVE is used > > NEW: > > For simplicity, a NVE is used > > > > Section #4 > > OLD: > > TTL or Hop Limit: These MUST be set to 255 > > NEW: > > > TTL or Hop Limit: The TTL for IPv4 or Hop Limit for IPv6 MUST be set to 255 > > > > Section #4 > > OLD: > > Geneve specification [RFC8926] depending on > > NEW: > > Geneve specification ([RFC8926]) depending on > > > > Section #4.1 > > OLD: > > N-to-1 mapping between a VAP and a VNI > > NEW: > > N-to-1 mapping between VAPs and VNIs > > > > > > > > Section #5 > > OLD: > > TTL or Hop Limit: These MUST be set to 255 > > NEW: > > > TTL or Hop Limit: The TTL for IPv4 or Hop Limit for IPv6 MUST be set to 255 > > > > > > > > Best Regards, > > > > Xiao Min > > > > > > > > Thank you. > > > > RFC Editor/kf/mf > > > > *****IMPORTANT***** > > > > Updated 2023/12/15 > > > > RFC Author(s): > > -------------- > > > > Instructions for Completing AUTH48 > > > > Your document has now entered AUTH48. Once it has been reviewed and > > approved by you and all coauthors, it will be published as an RFC. > > If an author is no longer available, there are several remedies > > available as listed in the FAQ (https://www.rfc-editor.org/faq/). > > > > You and you coauthors are responsible for engaging other parties > > (e.g., Contributors or Working Group) as necessary before providing > > your approval. > > > > Planning your review > > --------------------- > > > > Please review the following aspects of your document: > > > > * RFC Editor questions > > > > Please review and resolve any questions raised by the RFC Editor > > that have been included in the XML file as comments marked as > > follows: > > > > <!-- [rfced] ... --> > > > > These questions will also be sent in a subsequent email. > > > > * Changes submitted by coauthors > > > > Please ensure that you review any changes submitted by your > > coauthors. We assume that if you do not speak up that you > > agree to changes submitted by your coauthors. > > > > * Content > > > > Please review the full content of the document, as this cannot > > change once the RFC is published. Please pay particular attention to: > > - IANA considerations updates (if applicable) > > - contact information > > - references > > > > * Copyright notices and legends > > > > Please review the copyright notice and legends as defined in > > RFC 5378 and the Trust Legal Provisions > > (TLP – https://trustee.ietf.org/license-info/). > > > > * Semantic markup > > > > Please review the markup in the XML file to ensure that elements of > > > content are correctly tagged. For example, ensure that <sourcecode> > > > and <artwork> are set correctly. See details at > > <https://authors.ietf.org/rfcxml-vocabulary>. > > > > * Formatted output > > > > Please review the PDF, HTML, and TXT files to ensure that the > > formatted output, as generated from the markup in the XML file, is > > reasonable. Please note that the TXT will have formatting > > limitations compared to the PDF and HTML. > > > > > > Submitting changes > > ------------------ > > > > To submit changes, please reply to this email using ‘REPLY ALL’ as all > > the parties CCed on this message need to see your changes. The parties > > include: > > > > * your coauthors > > > > * rfc-editor@rfc-editor.org (the RPC team) > > > > * other document participants, depending on the stream (e.g., > > IETF Stream participants are your working group chairs, the > > responsible ADs, and the document shepherd). > > > > * auth48archive@rfc-editor.org, which is a new archival mailing list > > > to preserve AUTH48 conversations; it is not an active discussion > > list: > > > > * More info: > > > https://mailarchive.ietf.org/arch/msg/ietf-announce/yb6lpIGh-4Q9l2USxIAe6P8O4Zc > > > > * The archive itself: > > https://mailarchive.ietf.org/arch/browse/auth48archive/ > > > > * Note: If only absolutely necessary, you may temporarily opt out > > > > of the archiving of messages (e.g., to discuss a sensitive matter). > > If needed, please add a note at the top of the message that you > > > have dropped the address. When the discussion is concluded, > > auth48archive@rfc-editor.org will be re-added to the CC list and > > > its addition will be noted at the top of the message. > > > > You may submit your changes in one of two ways: > > > > An update to the provided XML file > > — OR — > > An explicit list of changes in this format > > > > Section # (or indicate Global) > > > > OLD: > > old text > > > > NEW: > > new text > > > > You do not need to reply with both an updated XML file and an explicit > > list of changes, as either form is sufficient. > > > > We will ask a stream manager to review and approve any changes that seem > > beyond editorial in nature, e.g., addition of new text, deletion of text, > > > and technical changes. Information about stream managers can be found in > > > > the FAQ. Editorial changes do not require approval from a stream manager. > > > > > > Approving for publication > > -------------------------- > > > > To approve your RFC for publication, please reply to this email stating > > that you approve this RFC for publication. Please use ‘REPLY ALL’, > > as all the parties CCed on this message need to see your approval. > > > > > > Files > > ----- > > > > The files are available here: > > https://www.rfc-editor.org/authors/rfc9521.xml > > https://www.rfc-editor.org/authors/rfc9521.html > > https://www.rfc-editor.org/authors/rfc9521.pdf > > https://www.rfc-editor.org/authors/rfc9521.txt > > > > Diff file of the text: > > https://www.rfc-editor.org/authors/rfc9521-diff.html > > https://www.rfc-editor.org/authors/rfc9521-rfcdiff.html > (side by side) > > > > Diff of the XML: > > https://www.rfc-editor.org/authors/rfc9521-xmldiff1.html > > > > The following files are provided to facilitate creation of your own > > diff files of the XML. > > > > Initial XMLv3 created using XMLv2 as input: > > https://www.rfc-editor.org/authors/rfc9521.original.v2v3.xml > > > > XMLv3 file that is a best effort to capture v3-related format updates > > only: > > https://www.rfc-editor.org/authors/rfc9521.form.xml > > > > > > Tracking progress > > ----------------- > > > > The details of the AUTH48 status of your document are here: > > https://www.rfc-editor.org/auth48/rfc9521 > > > > Please let us know if you have any questions. > > > > Thank you for your cooperation, > > > > RFC Editor > > > > -------------------------------------- > > RFC9521 (draft-ietf-nvo3-bfd-geneve-13) > > > > Title : BFD for Geneve > > > Author(s) : X. Min, G. Mirsky, S. Pallagatti, J. Tantsura, S. Aldrin > > WG Chair(s) : Matthew Bocci, Sam Aldrin > > Area Director(s) : Alvaro Retana, John Scudder, Andrew Alston > > > > > > > > >
- [auth48] AUTH48: RFC-to-be 9521 <draft-ietf-nvo3-… rfc-editor
- Re: [auth48] AUTH48: RFC-to-be 9521 <draft-ietf-n… rfc-editor
- Re: [auth48] AUTH48: RFC-to-be 9521 <draft-ietf-n… Greg Mirsky
- Re: [auth48] AUTH48: RFC-to-be 9521 <draft-ietf-n… xiao.min2
- Re: [auth48] AUTH48: RFC-to-be 9521 <draft-ietf-n… Megan Ferguson
- Re: [auth48] AUTH48: RFC-to-be 9521 <draft-ietf-n… Greg Mirsky
- Re: [auth48] AUTH48: RFC-to-be 9521 <draft-ietf-n… xiao.min2
- Re: [auth48] AUTH48: RFC-to-be 9521 <draft-ietf-n… Greg Mirsky
- Re: [auth48] AUTH48: RFC-to-be 9521 <draft-ietf-n… xiao.min2
- Re: [auth48] AUTH48: RFC-to-be 9521 <draft-ietf-n… Megan Ferguson
- Re: [auth48] AUTH48: RFC-to-be 9521 <draft-ietf-n… Greg Mirsky
- Re: [auth48] AUTH48: RFC-to-be 9521 <draft-ietf-n… Megan Ferguson
- Re: [auth48] AUTH48: RFC-to-be 9521 <draft-ietf-n… xiao.min2
- Re: [auth48] AUTH48: RFC-to-be 9521 <draft-ietf-n… Jeff Tantsura
- Re: [auth48] AUTH48: RFC-to-be 9521 <draft-ietf-n… Megan Ferguson
- Re: [auth48] AUTH48: RFC-to-be 9521 <draft-ietf-n… Greg Mirsky
- Re: [auth48] AUTH48: RFC-to-be 9521 <draft-ietf-n… Sam Aldrin
- Re: [auth48] AUTH48: RFC-to-be 9521 <draft-ietf-n… xiao.min2
- Re: [auth48] AUTH48: RFC-to-be 9521 <draft-ietf-n… Megan Ferguson
- Re: [auth48] AUTH48: RFC-to-be 9521 <draft-ietf-n… Megan Ferguson
- Re: [auth48] AUTH48: RFC-to-be 9521 <draft-ietf-n… Santosh P K