Re: [sfc] WG Last Call draft-ietf-sfc-oam-framework-06
"Adrian Farrel" <adrian@olddog.co.uk> Fri, 31 May 2019 21:49 UTC
Return-Path: <adrian@olddog.co.uk>
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 63502120073 for <sfc@ietfa.amsl.com>; Fri, 31 May 2019 14:49:56 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -0.608
X-Spam-Level:
X-Spam-Status: No, score=-0.608 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, HTML_MESSAGE=0.001, HTTPS_HTTP_MISMATCH=1.989, RCVD_IN_DNSWL_LOW=-0.7, SPF_HELO_NONE=0.001, SPF_NONE=0.001] autolearn=ham autolearn_force=no
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 EWRagU92YByr for <sfc@ietfa.amsl.com>; Fri, 31 May 2019 14:49:53 -0700 (PDT)
Received: from mta5.iomartmail.com (mta5.iomartmail.com [62.128.193.155]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id B7503120020 for <sfc@ietf.org>; Fri, 31 May 2019 14:49:51 -0700 (PDT)
Received: from vs2.iomartmail.com (vs2.iomartmail.com [10.12.10.123]) by mta5.iomartmail.com (8.14.4/8.14.4) with ESMTP id x4VLnkYI002314; Fri, 31 May 2019 22:49:46 +0100
Received: from vs2.iomartmail.com (unknown [127.0.0.1]) by IMSVA (Postfix) with ESMTP id 3651022044; Fri, 31 May 2019 22:49:46 +0100 (BST)
Received: from asmtp3.iomartmail.com (unknown [10.12.10.224]) by vs2.iomartmail.com (Postfix) with ESMTPS id 2115C22042; Fri, 31 May 2019 22:49:46 +0100 (BST)
Received: from LAPTOPK7AS653V ([87.112.172.175]) (authenticated bits=0) by asmtp3.iomartmail.com (8.14.4/8.14.4) with ESMTP id x4VLnhKm013395 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-GCM-SHA384 bits=256 verify=NO); Fri, 31 May 2019 22:49:44 +0100
Reply-To: adrian@olddog.co.uk
From: Adrian Farrel <adrian@olddog.co.uk>
To: 'James Guichard' <james.n.guichard@futurewei.com>, sfc@ietf.org
References: <BYAPR13MB25978FD458B59EB22067685FD21E0@BYAPR13MB2597.namprd13.prod.outlook.com>
In-Reply-To: <BYAPR13MB25978FD458B59EB22067685FD21E0@BYAPR13MB2597.namprd13.prod.outlook.com>
Date: Fri, 31 May 2019 22:49:43 +0100
Organization: Old Dog Consulting
Message-ID: <062b01d517fa$c24cbed0$46e63c70$@olddog.co.uk>
MIME-Version: 1.0
Content-Type: multipart/alternative; boundary="----=_NextPart_000_062C_01D51803.241126D0"
X-Mailer: Microsoft Outlook 16.0
Thread-Index: AQHHNlpyth1Tt5lM3f8NY2gEYgqxLqahiK3A
Content-Language: en-gb
X-Originating-IP: 87.112.172.175
X-Thinkmail-Auth: adrian@olddog.co.uk
X-TM-AS-GCONF: 00
X-TM-AS-Product-Ver: IMSVA-9.0.0.1623-8.2.0.1013-24650.003
X-TM-AS-Result: No--12.733-10.0-31-10
X-imss-scan-details: No--12.733-10.0-31-10
X-TMASE-Version: IMSVA-9.0.0.1623-8.2.1013-24650.003
X-TMASE-Result: 10--12.733100-10.000000
X-TMASE-MatchedRID: m8E5UH2Q2aG+AWaOCXs78kNkUF3WMuv+cU9StUObqO3ujRbqge917uCA U8+z4gBpaXKzU8OFYuh1JcIKe4igQ1iv/vFtB9P7heOI9Wrg5NtO8qlnOXFSz6t8JTb7GATYr1u VaZUKda+m6tA6+Nf5hOOWnQzM/987lZCh4m94H0dM7gMW5+VNf2j110VUgQaLIgt1z4icQSuvIa W/gtYq38w7Chc5Gc+p9y0si6rTiyYQzB2LH5qdINB+FvCE3iAWdhnFihmbnwWnLZXtX62Wm4blM MKBhOiUOArqsGNfHKKhgfygFY12yXePWPGFF8/GNq1bCnLUo6e2+eU4nrUreuOGmthhJaWdpMQg 6AVyOoN7XEgV3uEXzXYMChw2OD8fejIyzPwjQVAnITjASO+40FwNehMcA+esZnol1sRLBs29K1j OJyKSa2K3yskfEbaLrX8Yl8y/h5E0ctDiif1H7I1pcgBT/7NsdPuue3cRiRgqaLKskc2Hck+86m aMM3aSRX34c0TChl9g9pztAeHjRiQUfW6C4J4IkG7KseF2pkEl/muXhDBEuC5Pvog0jk8MEBn6P JIWUUfwmYyDyIMChJ+9CAu07LMKIYOIWNY63iMcVG9OtZloO5VRzPxemJL0RiPTMMc/MmkG2HMv WEJenqjZ4vqVgtbFj0Zay9PpGRoGcDZwmRZXvqI0xRx+dH7GnVTWWiNp+v/kbMASTwgriPv7ndO c2uMkweO0CN4v0YryLyvrcoyz3pumkaYT3O8VdW9cfduY/2ko7b5tLxYZrd2GOg4qpcaxBQ0WPf n19vbl9fZvCJlkcDba6gSbbjl+nagtny7ZPcQfE8yM4pjsDzl/1fD/GopdyJ1gFgOMhOnQBQ8SB UzMX7FVO/b6tafeU6baA36eiaxsZUSYh+N/e/VM+KTAw9JMqLr2ziI56Os49GO+pUYonk22oeX7 BEuBAahFgTxM1O9jhmpn8iGfqIlSEfQYFga96OL3mvrRTSYMQSwKOL7B7Q==
X-TMASE-SNAP-Result: 1.821001.0001-0-1-12:0,22:0,33:0,34:0-0
Archived-At: <https://mailarchive.ietf.org/arch/msg/sfc/35ovF9zlg7vZY9SuVnM2QLvkXkQ>
Subject: Re: [sfc] WG Last Call draft-ietf-sfc-oam-framework-06
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: Fri, 31 May 2019 21:49:56 -0000
Hi, I support publication, but there are a number of minor issues. Thanks, Adrian === The document has 6 front-page authors: I assume the document shepherd will handle this with the AD. --- The RFC Editor's preferred expansion of "OAM" is "Operations, Administration, and Maintenance" per RFC 6291. --- Requirements language should use the latest boilerplate that includes the reference to RFC 8174. --- Section 2 Multiple layers come into play for implementing the SFC. These include the service layer and the underlying layers (Network, Link etc) Missing two periods. s/etc)/etc.)./ OLD o The service layer in Figure 1, consists of SFC data plane elements that includes classifiers, Service Functions (SF), Service Function Forwarders (SFF), SFC Proxy. This layer uses the overlay network for ensuring connectivity between SFC data plane elements. NEW o The service layer in Figure 1 consists of SFC data plane elements that include classifiers, Service Functions (SF), Service Function Forwarders (SFF), and an SFC Proxy. This layer uses the overlay network for ensuring connectivity between SFC data plane elements. END Ditto s/Figure 1,/Figure 1/ in all of the subsequent bullets. --- Looking at Figure 1, I don't understand how the overlay network has more granularity than the underlay network. Surely the "legs" in the overlay shown between VM1-VM2 and VM2-VM3 cannot exist without "legs" in the underlay network. --- In each of the bullets in Section 3, you say "OAM solutions for this component" but Section 1.1 has already said "Actual solutions and mechanisms are outside the scope of this document." I think you could change 1.1 to read "Details of actual solutions and mechanisms are outside the scope of this document." But maybe it would be better if the bullets in Section 3 were "OAM functions applicable at this component". Or you could use "OAM requirements" as in Section 3.1.1 etc. --- Section 3 s/Below figure/Figure 2/ The arrow for "Service Function Chain OAM" is misaligned in Figure 2 --- Section 5 does not sit easily. It is good to have a list of exist OAM solutions that might be applicable. But by presenting it as a gap analysis there is an implication that these solutions are to be used for SFC OAM. That is in opposition to the statement in Section 1.1. Maybe the way to handle this is to rebrand Section 5 as an informational list of pre-existing OAM solutions that might be applicable to SFC OAM. And then to state that an analysis of their applicability is for future study. But then Section 6.4 is a worry because it does talk about the applicability of solutions. That would probably mean changing the tilt of the whole document to be "Service Function Chaining (SFC) Operation, Administration, and Maintenance (OAM) Framework and Applicability of Existing OAM Tools to SFC." --- Section 6.3 has The Next Protocol field in NSH header may be used to indicate what OAM function is it intended to or what toolset is used. s/is it/is/ But (!) I think this is solution text. It is completely true that this is one way to do it, it might even be the best way to do it, but I think it is out of scope. --- Sections 6.5, 6.6, and 6.7, need to be out-dented to 7., 8., and 9. --- The security considerations are a little weak. In particular, isn't there a confidentiality issue. That is, if the results of OAM can be inspected by a third party, they can deduce a lot about the network and the structure of the Service function Chain. Since the chains are themselves often used for security functions, this sort of information is sensitive. --- I think [RFC0792] and [RFC4443] could afford to be Informative References as they are used in the same way as BFD, etc. From: sfc <sfc-bounces@ietf.org> On Behalf Of James Guichard Sent: 28 May 2019 15:30 To: sfc@ietf.org Subject: [sfc] WG Last Call draft-ietf-sfc-oam-framework-06 Dear WG: This message starts a new two week WG Last Call on advancing <https://nam03.safelinks.protection.outlook.com/?url=https%3A%2F%2Fdatatrack er.ietf.org%2Fdoc%2Fdraft-ietf-sfc-oam-framework%2F&data=02%7C01%7Cjames.n.g uichard%40futurewei.com%7Ce47e5eb13f224f18c46408d6e378b2f7%7C0fee8ff2a3b2401 89c753a1d5591fedc%7C1%7C0%7C636946504868870205&sdata=lkKvAgmKik7lkqGANQpnIvB RdbjKAqYtzTUdTfB9f3Y%3D&reserved=0> https://datatracker.ietf.org/doc/draft-ietf-sfc-oam-framework/ for publication as an Informational RFC. Substantive comments and statements of support for publishing this document should be directed to the mailing list. Editorial suggestions can be sent to the authors. This last call will end on 11th June 2019. Thanks! Jim & Joel
- [sfc] WG Last Call draft-ietf-sfc-oam-framework-06 James Guichard
- Re: [sfc] WG Last Call draft-ietf-sfc-oam-framewo… Nagendra Kumar Nainar (naikumar)
- Re: [sfc] WG Last Call draft-ietf-sfc-oam-framewo… mohamed.boucadair
- Re: [sfc] WG Last Call draft-ietf-sfc-oam-framewo… Andrew G. Malis
- Re: [sfc] WG Last Call draft-ietf-sfc-oam-framewo… Adrian Farrel
- Re: [sfc] WG Last Call draft-ietf-sfc-oam-framewo… Nagendra Kumar Nainar (naikumar)
- Re: [sfc] WG Last Call draft-ietf-sfc-oam-framewo… Sam Aldrin
- Re: [sfc] WG Last Call draft-ietf-sfc-oam-framewo… Nagendra Kumar Nainar (naikumar)
- Re: [sfc] WG Last Call draft-ietf-sfc-oam-framewo… mohamed.boucadair
- Re: [sfc] WG Last Call draft-ietf-sfc-oam-framewo… Greg Mirsky
- Re: [sfc] WG Last Call draft-ietf-sfc-oam-framewo… Carlos Pignataro (cpignata)
- Re: [sfc] WG Last Call draft-ietf-sfc-oam-framewo… Carlos Pignataro (cpignata)
- Re: [sfc] WG Last Call draft-ietf-sfc-oam-framewo… James Guichard
- Re: [sfc] WG Last Call draft-ietf-sfc-oam-framewo… mohamed.boucadair
- Re: [sfc] WG Last Call draft-ietf-sfc-oam-framewo… Sami Boutros
- Re: [sfc] WG Last Call draft-ietf-sfc-oam-framewo… Anoop Ghanwani
- Re: [sfc] WG Last Call draft-ietf-sfc-oam-framewo… Nagendra Kumar Nainar (naikumar)
- Re: [sfc] WG Last Call draft-ietf-sfc-oam-framewo… Carlos Pignataro (cpignata)
- Re: [sfc] WG Last Call draft-ietf-sfc-oam-framewo… Greg Mirsky
- Re: [sfc] WG Last Call draft-ietf-sfc-oam-framewo… Sam Aldrin
- Re: [sfc] WG Last Call draft-ietf-sfc-oam-framewo… Vengada Prasad Govindan (venggovi)
- Re: [sfc] WG Last Call draft-ietf-sfc-oam-framewo… Ashish Panda (aspanda)
- Re: [sfc] WG Last Call draft-ietf-sfc-oam-framewo… Diego R. Lopez
- Re: [sfc] WG Last Call draft-ietf-sfc-oam-framewo… Greg Mirsky
- Re: [sfc] WG Last Call draft-ietf-sfc-oam-framewo… Jeff Tantsura
- Re: [sfc] WG Last Call draft-ietf-sfc-oam-framewo… Greg Mirsky
- Re: [sfc] WG Last Call draft-ietf-sfc-oam-framewo… Carlos Pignataro (cpignata)
- Re: [sfc] WG Last Call draft-ietf-sfc-oam-framewo… James Guichard
- Re: [sfc] WG Last Call draft-ietf-sfc-oam-framewo… Greg Mirsky
- Re: [sfc] WG Last Call draft-ietf-sfc-oam-framewo… Nagendra Kumar Nainar (naikumar)
- Re: [sfc] WG Last Call draft-ietf-sfc-oam-framewo… Greg Mirsky
- Re: [sfc] WG Last Call draft-ietf-sfc-oam-framewo… Greg Mirsky
- Re: [sfc] WG Last Call draft-ietf-sfc-oam-framewo… Greg Mirsky
- Re: [sfc] WG Last Call draft-ietf-sfc-oam-framewo… Carlos Pignataro (cpignata)
- Re: [sfc] WG Last Call draft-ietf-sfc-oam-framewo… James Guichard
- Re: [sfc] WG Last Call draft-ietf-sfc-oam-framewo… Greg Mirsky
- Re: [sfc] WG Last Call draft-ietf-sfc-oam-framewo… James Guichard
- Re: [sfc] WG Last Call draft-ietf-sfc-oam-framewo… Greg Mirsky
- Re: [sfc] WG Last Call draft-ietf-sfc-oam-framewo… James Guichard
- Re: [sfc] WG Last Call draft-ietf-sfc-oam-framewo… Carlos Pignataro (cpignata)