Re: [sfc] Shepherd Review of draft-ietf-sfc-oam-framework-10
Tal Mizrahi <tal.mizrahi.phd@gmail.com> Tue, 15 October 2019 11:11 UTC
Return-Path: <tal.mizrahi.phd@gmail.com>
X-Original-To: sfc@ietfa.amsl.com
Delivered-To: sfc@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 74CE31200DF; Tue, 15 Oct 2019 04:11:33 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.998
X-Spam-Level:
X-Spam-Status: No, score=-1.998 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, FREEMAIL_FROM=0.001, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_NONE=-0.0001, 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 ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id Lx7cGD00_LNG; Tue, 15 Oct 2019 04:11:30 -0700 (PDT)
Received: from mail-wm1-x32c.google.com (mail-wm1-x32c.google.com [IPv6:2a00:1450:4864:20::32c]) (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 E5A001200F3; Tue, 15 Oct 2019 04:11:29 -0700 (PDT)
Received: by mail-wm1-x32c.google.com with SMTP id 3so19833768wmi.3; Tue, 15 Oct 2019 04:11:29 -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=eLD7+omLh4zJTDbm4gnME9KBppL5JUohtXNp+zZ8EqY=; b=hGBdZT1/uvPZDucfZQxxlmmUpNKhAFIr1F2Iok9cP9SNzI75wDwIv/eIz5yCJy0BHd AY+0ygxm+KEAxYXsTA5FRSZwy/a/SNUiS0DD9WJAA7w58tWWeL0BV8pJ0lJqHgSkqLux ujPurujUyPVLHL9gl8fKYfJbByTeR6vBbQeJ9PABd9e8t4mgmyht61ijY/OL0ZFYp803 p8zc3tv4u5OH0DbfqsvBOjej98paXNwCBTrCEKZ3IzWJvhxWcLI2VCVUlvxOez6rXK8K o0LZumiXQRGyLV3q55wGsQ8a9N2XiONXOPbQX2jUm0EKqPgJlvdnHzh0B6Bsw4EMFZnM 8Eig==
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=eLD7+omLh4zJTDbm4gnME9KBppL5JUohtXNp+zZ8EqY=; b=pJ7k5AQbnAifQHC/zpooZ8+ROfHbO+1hdt/7SpFrJxGvY/9ju8naZ6wUksy1+kdcGV dIrOXMR4Loi1KnYkxjs/MtvUQZ4LcFo4Z0JKwdSuKkBbFvqnRZeONcrP4M1A+0PL/MIC +YIpQ/xOO08YeTL3NI2q7+iHj8eezTgeZI2q2dcZ1AcR6iNJ9dO28jERByO/ToSfKJNU 9cPEsbA2J0e8unlXsyrRVtYhuv5cxrCYwb2BFp8QT/JyR4i9BxiEHlvf1Mkw1+QBMQ3g c2FIrclGDhi34GLP3kq7B6n4QBDF+rsKMhddrZBOpIK7mBaxPAy3/yoXL7R5stAkpnaG yXXA==
X-Gm-Message-State: APjAAAVxn7zOGVWH/ZUHIAOSTIq+Lhm70limTwHDgId6a0rNuNCaYoWq mghNXR6ighxIaZt5AfSUYKLf/LBQ9dx5moa1D1g=
X-Google-Smtp-Source: APXvYqxI0vagRi3p1Uil+YlMAgKTY6YmsxtKgtjn1dr1DV/IJEbZF8c0qiEZcP/JqtFZO8Gudh7gU4m8nn+OUpDvzm4=
X-Received: by 2002:a05:600c:2319:: with SMTP id 25mr19679913wmo.3.1571137887848; Tue, 15 Oct 2019 04:11:27 -0700 (PDT)
MIME-Version: 1.0
References: <CABUE3XkrHjhTBnmjnxcV0nUJS9kCZ2p6DYcaHD9v7husBkRvsw@mail.gmail.com> <175B6B2A-1318-4D91-AF73-00E590173506@cisco.com> <0A7EAE17-D6C4-4B3B-8958-4106B09C43EB@cisco.com> <CABUE3Xnxm_74NnNSX148gDppQdRtSArp78POXWCgdV38NbRG-g@mail.gmail.com>
In-Reply-To: <CABUE3Xnxm_74NnNSX148gDppQdRtSArp78POXWCgdV38NbRG-g@mail.gmail.com>
From: Tal Mizrahi <tal.mizrahi.phd@gmail.com>
Date: Tue, 15 Oct 2019 14:11:16 +0300
Message-ID: <CABUE3XnoAFeYkQKwGm21fAvqTxqi9xuAM824v-ZeVUh_-S+SbA@mail.gmail.com>
To: "Nagendra Kumar Nainar (naikumar)" <naikumar@cisco.com>
Cc: "draft-ietf-sfc-oam-framework@ietf.org" <draft-ietf-sfc-oam-framework@ietf.org>, Service Function Chaining IETF list <sfc@ietf.org>, "sfc-chairs@ietf.org" <sfc-chairs@ietf.org>
Content-Type: multipart/alternative; boundary="000000000000b2cd3c0594f10b01"
Archived-At: <https://mailarchive.ietf.org/arch/msg/sfc/tAYPaS4E3Y_fD_2JmHsgKLutXQg>
Subject: Re: [sfc] Shepherd Review of draft-ietf-sfc-oam-framework-10
X-BeenThere: sfc@ietf.org
X-Mailman-Version: 2.1.29
Precedence: list
List-Id: Network Service Chaining <sfc.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/sfc>, <mailto:sfc-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/sfc/>
List-Post: <mailto:sfc@ietf.org>
List-Help: <mailto:sfc-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/sfc>, <mailto:sfc-request@ietf.org?subject=subscribe>
X-List-Received-Date: Tue, 15 Oct 2019 11:11:34 -0000
Dear authors, This is a reminder that we are waiting for two authors to respond to the IPR call - Sam and Ramki. Cheers, Tal. On Wed, Sep 25, 2019 at 11:30 AM Tal Mizrahi <tal.mizrahi.phd@gmail.com> wrote: > Hi Nagendra, authors, > > Many thanks for addressing the comments and posting the updated draft. > > We are still waiting for two remaining authors to respond to the IPR call: > > https://mailarchive.ietf.org/arch/msg/sfc/b5FHtp2IB-8MQLEMCZkOwnN5Aqk > > Once we complete the IPR call we can proceed with the publication process. > > Thanks, > Tal. > > On Thu, Sep 19, 2019 at 11:31 PM Nagendra Kumar Nainar (naikumar) < > naikumar@cisco.com> wrote: > >> Hi Tal, >> >> >> >> Thank you again for the review and comments. We have submitted a new >> revision addressing the comments. >> >> >> >> A new version of I-D, draft-ietf-sfc-oam-framework-11.txt >> >> has been successfully submitted by Nagendra Kumar and posted to the >> >> IETF repository. >> >> >> >> Name: draft-ietf-sfc-oam-framework >> >> Revision: 11 >> >> Title: Service Function Chaining (SFC) Operations, >> Administration and Maintenance (OAM) Framework >> >> Document date: 2019-09-19 >> >> Group: sfc >> >> Pages: 21 >> >> URL: >> https://www.ietf.org/internet-drafts/draft-ietf-sfc-oam-framework-11.txt >> >> Status: >> https://datatracker.ietf.org/doc/draft-ietf-sfc-oam-framework/ >> >> Htmlized: >> https://tools.ietf.org/html/draft-ietf-sfc-oam-framework-11 >> >> Htmlized: >> https://datatracker.ietf.org/doc/html/draft-ietf-sfc-oam-framework >> >> Diff: >> https://www.ietf.org/rfcdiff?url2=draft-ietf-sfc-oam-framework-11 >> >> >> >> >> >> Thanks, >> >> Nagendra >> >> >> >> *From: *Nagendra Kumar <naikumar@cisco.com> >> *Date: *Tuesday, September 3, 2019 at 10:29 AM >> *To: *Tal Mizrahi <tal.mizrahi.phd@gmail.com>, " >> draft-ietf-sfc-oam-framework@ietf.org" < >> draft-ietf-sfc-oam-framework@ietf.org>, Service Function Chaining IETF >> list <sfc@ietf.org>, "sfc-chairs@ietf.org" <sfc-chairs@ietf.org> >> *Subject: *Re: [sfc] Shepherd Review of draft-ietf-sfc-oam-framework-10 >> *Resent-From: *<alias-bounces@ietf.org> >> *Resent-To: *<aldrin.ietf@gmail.com>, <cpignata@cisco.com>, Nagendra >> Kumar <naikumar@cisco.com>, <ramkri123@gmail.com>, <anoop@alumni.duke.edu >> > >> *Resent-Date: *Tuesday, September 3, 2019 at 10:28 AM >> >> >> >> Hi Tal, >> >> >> >> Thank you for the comments. We will address the same and will submit a >> new version. >> >> >> >> Regards, >> >> Nagendra >> >> >> >> *From: *sfc <sfc-bounces@ietf.org> on behalf of Tal Mizrahi < >> tal.mizrahi.phd@gmail.com> >> *Date: *Monday, September 2, 2019 at 1:14 AM >> *To: *"draft-ietf-sfc-oam-framework@ietf.org" < >> draft-ietf-sfc-oam-framework@ietf.org>, Service Function Chaining IETF >> list <sfc@ietf.org>, "sfc-chairs@ietf.org" <sfc-chairs@ietf.org> >> *Subject: *[sfc] Shepherd Review of draft-ietf-sfc-oam-framework-10 >> >> >> >> Hi, >> >> >> >> I am the assigned shepherd of draft-ietf-sfc-oam-framework-10. >> >> I believe the document is almost ready for publication. >> I have a few (mostly editorial) comments, as follows. >> It would be great if the authors could post a new version that addresses >> these comments, and then we can proceed with the publication process. >> >> - RFC 7498 is an informative reference, but the introduction says >> that the reader is expected to be familiar with it. I suggest to change >> either one or the other. >> - Is there a reason why RFC 8459 is a normative reference? I suggest >> to make it informative. >> - Regarding IOAM (Section 6.4.3) - the section describes the >> proof-of-transit draft, but should also mention >> - draft-ietf-sfc-ioam-nsh. >> - Section 1 (Introduction) lists the content in the rest of the >> sections, but does not mention Section 6, which suggests candidate tools. >> - "with the same" ==> "this terminology" >> - "The link layer, which is dependent upon the physical technology >> used." ==> "The link layer, which is tightly coupled with the physical >> technology used." >> - "depicts a sample example" ==> "depicts an example" >> - In Tables 3 and 4, it is not clear why some of the columns are >> separated by "|", and some are separated by "+". >> - "Tables 4" ==> "Table 4" >> - "for fast failure detection" - I suggest to remove the word fast, >> as BFD is not necessarily fast. >> - Section 6..4 says that "This section describes the applicability of >> some of the available toolsets in the service layer.", however, section >> "6.4.4 SFC Traceroute" describes a tool that was defined in an expired >> individual submission. I suggest to either remove section 6.4.4., or to >> explicitly mention that this draft has expired, and that a new tool can be >> defined along the lines of this proposal. >> - Section 3 describes three OAM components (SF, SFC, Classifier), but >> then Section 5 and Section 7 (Table 3, Table 4) do not refer to these three >> components, but to Underlay, Overlay, SF and SFC. Please be consistent, so >> that Section 5-7 refer to the same components that were defined in Section >> 3. >> - Moreover, in Section 3, for each of the first two components (SF >> and SFC) there is a discussion about availability and performance >> measurement. However, for the third component (Classifier), there is no >> explicit discussion about availability and performance measurement. I >> suggest to add this missing discussion (even if these functions are not >> required, it is still important to mention this). >> >> Cheers, >> >> Tal. >> >
- [sfc] Shepherd Review of draft-ietf-sfc-oam-frame… Tal Mizrahi
- Re: [sfc] Shepherd Review of draft-ietf-sfc-oam-f… Nagendra Kumar Nainar (naikumar)
- Re: [sfc] Shepherd Review of draft-ietf-sfc-oam-f… Nagendra Kumar Nainar (naikumar)
- Re: [sfc] Shepherd Review of draft-ietf-sfc-oam-f… Tal Mizrahi
- Re: [sfc] Shepherd Review of draft-ietf-sfc-oam-f… Tal Mizrahi