Re: [sfc] The SFC WG has placed draft-wang-sfc-multi-layer-oam instate"Candidate for WG Adoption"

"Carlos Pignataro (cpignata)" <cpignata@cisco.com> Fri, 26 October 2018 21:35 UTC

Return-Path: <cpignata@cisco.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 7CED9127148; Fri, 26 Oct 2018 14:35:32 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -14.97
X-Spam-Level:
X-Spam-Status: No, score=-14.97 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIMWL_WL_HIGH=-0.47, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_HI=-5, SPF_PASS=-0.001, USER_IN_DEF_DKIM_WL=-7.5] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (1024-bit key) header.d=cisco.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 w1nQusHV-Azw; Fri, 26 Oct 2018 14:35:30 -0700 (PDT)
Received: from alln-iport-7.cisco.com (alln-iport-7.cisco.com [173.37.142.94]) (using TLSv1.2 with cipher DHE-RSA-SEED-SHA (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 16A69130DDA; Fri, 26 Oct 2018 14:35:30 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=cisco.com; i=@cisco.com; l=28316; q=dns/txt; s=iport; t=1540589730; x=1541799330; h=from:to:cc:subject:date:message-id:references: in-reply-to:mime-version; bh=w7q2XW7hfsHVaHZpyyR/ekBFAe2MHHaUus60bV8NFtk=; b=Tz1dtIbuHDDZ7TWMZW1uyAUsSErfgsLAUvDcsap21In9ioQLw4eb599H XrD3OeDlPvxfQOGCaGkrE/msEdOI5fMmR1teZBkgh8VvgVvLbLf6Yqh79 +VmrWLTlc7OlR9nCamf+pKSsMgRjThGU0S9plgBJgM6mFWj8o7QFyZkVy g=;
X-IronPort-Anti-Spam-Filtered: true
X-IronPort-Anti-Spam-Result: A0ANAADZh9Nb/5xdJa1jGwEBAQEDAQEBBwMBAQGBUQYBAQELAYENd2Z/KAqDa4gYjBmZKoF6CwEBGAEKhEkCF4MBITQNDQEDAQECAQECbRwBC4U7AgQBARsGSwsQAgEGAj8DAgICJQsUEQIEDgUbgwYBgR1kD4s0m02BLoQ+QIUdBYtnF4FBP4ERJx+CTIMbAQEDAYFcgwUxgiYCiHiFTpA5CQKGZ4oWGIFShHeDG4ZhjG2HKoJUAhEUgSYdOIFVcBU7KgGCQT6CEYhKhT0Bb4wfgR8BAQ
X-IronPort-AV: E=Sophos;i="5.54,429,1534809600"; d="scan'208,217";a="191613508"
Received: from rcdn-core-5.cisco.com ([173.37.93.156]) by alln-iport-7.cisco.com with ESMTP/TLS/DHE-RSA-AES256-GCM-SHA384; 26 Oct 2018 21:35:29 +0000
Received: from XCH-RTP-020.cisco.com (xch-rtp-020.cisco.com [64.101.220.160]) by rcdn-core-5.cisco.com (8.15.2/8.15.2) with ESMTPS id w9QLZSmf014263 (version=TLSv1.2 cipher=AES256-SHA bits=256 verify=FAIL); Fri, 26 Oct 2018 21:35:29 GMT
Received: from xch-rtp-020.cisco.com (64.101.220.160) by XCH-RTP-020.cisco.com (64.101.220.160) with Microsoft SMTP Server (TLS) id 15.0.1395.4; Fri, 26 Oct 2018 17:35:27 -0400
Received: from xch-rtp-020.cisco.com ([64.101.220.160]) by XCH-RTP-020.cisco.com ([64.101.220.160]) with mapi id 15.00.1395.000; Fri, 26 Oct 2018 17:35:27 -0400
From: "Carlos Pignataro (cpignata)" <cpignata@cisco.com>
To: "xiao.min2@zte.com.cn" <xiao.min2@zte.com.cn>
CC: "sfc-chairs@ietf.org" <sfc-chairs@ietf.org>, "draft-wang-sfc-multi-layer-oam@ietf.org" <draft-wang-sfc-multi-layer-oam@ietf.org>, "sfc@ietf.org" <sfc@ietf.org>
Thread-Topic: [sfc] The SFC WG has placed draft-wang-sfc-multi-layer-oam instate"Candidate for WG Adoption"
Thread-Index: AQHUbXPP/Ob0HPeF10S84CXeiTTOYg==
Date: Fri, 26 Oct 2018 21:35:27 +0000
Message-ID: <C1717AF1-9B0C-43EB-811C-6400FED68E1C@cisco.com>
References: <153903723495.18337.3050104581221499764.idtracker@ietfa.amsl.com, D0756B6B-8FA2-4D8E-9F2C-2FF0A6FBF9D9@cisco.com> <201810261601427799745@zte.com.cn>
In-Reply-To: <201810261601427799745@zte.com.cn>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach:
X-MS-TNEF-Correlator:
x-mailer: Apple Mail (2.3445.100.39)
x-ms-exchange-messagesentrepresentingtype: 1
x-ms-exchange-transport-fromentityheader: Hosted
x-originating-ip: [10.118.116.132]
Content-Type: multipart/alternative; boundary="_000_C1717AF19B0C43EB811C6400FED68E1Cciscocom_"
MIME-Version: 1.0
X-Outbound-SMTP-Client: 64.101.220.160, xch-rtp-020.cisco.com
X-Outbound-Node: rcdn-core-5.cisco.com
Archived-At: <https://mailarchive.ietf.org/arch/msg/sfc/qqpKrhGqzShyElNgLItJc7gtN1E>
Subject: Re: [sfc] The SFC WG has placed draft-wang-sfc-multi-layer-oam instate"Candidate for WG Adoption"
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, 26 Oct 2018 21:35:33 -0000

Hi, Xiao Min,

Thank for for clarifying! I totally missed the “Comments” section including not only the actual “Adoption Call”, but also the deadline!

While the deadline passed, as I just learned, I trust you can entertain this follow-up:

As to the already adopted draft-ietf-sfc-oam-framework, if I understand it correctly, this draft is informational and it doesn't raise any practical solution of SFC OAM, so I believe the alignment between draft-ietf-sfc-oam-framework and draft-wang-sfc-multi-layer-oam can be done and should be done after the adoption poll conclude.

It really does not matter what the Intended Status of a document versus the other one is…

draft-ietf-sfc-oam-framework does not raise solutions *by design* because it is a *framework* document. However, solutions should align to the framework itself.  Clearly, aligning a solution to an existing framework *after* adoption would defeat its purpose.

So, if the framework includes *existing* protocols as parts of it — why does this document invents a new protocol from scratch modeled after MPLS LSP Ping?

Xiao, you also wrote this before:

I support WG adotion of this draft, because this work of active OAM is within our charter and complementary with already adopted iOAM.

So, for me to understand, I see no mention of IOAM in draft-wang-sfc-multi-layer-oam. What is complementary about it (other than the same complementarity between IOAM and any other OAM solution)?

Thanks again, ad apologies for the belated note.

— Carlos Pignataro

On Oct 26, 2018, at 4:01 AM, xiao.min2@zte.com.cn<mailto:xiao.min2@zte.com.cn> wrote:


Hi Carlos,


I read the clear comment from the chairs Joel and Jim, especially the following words.

-----------------------------------------------------------   snip   -------------------------------------------------------------

This starts a two week call for that adoption.  Please speak up, preferably with supporting explanations,
in favor of or opposed to the working group adopting this document.

-----------------------------------------------------------   snap   ------------------------------------------------------------

As to the already adopted draft-ietf-sfc-oam-framework, if I understand it correctly, this draft is informational and it doesn't raise any practical solution of SFC OAM, so I believe the alignment between draft-ietf-sfc-oam-framework and draft-wang-sfc-multi-layer-oam can be done and should be done after the adoption poll conclude.


Best Regards,

Xiao Min


原始邮件
发件人:CarlosPignataro(cpignata) <cpignata@cisco.com<mailto:cpignata@cisco.com>>
收件人:肖敏10093570;
抄送人:sfc-chairs@ietf.org<mailto:sfc-chairs@ietf.org> <sfc-chairs@ietf.org<mailto:sfc-chairs@ietf.org>>;draft-wang-sfc-multi-layer-oam@ietf.org<mailto:draft-wang-sfc-multi-layer-oam@ietf.org> <draft-wang-sfc-multi-layer-oam@ietf.org<mailto:draft-wang-sfc-multi-layer-oam@ietf.org>>;sfc@ietf.org<mailto:sfc@ietf.org> <sfc@ietf.org<mailto:sfc@ietf.org>>;
日 期 :2018年10月26日 11:35
主 题 :Re: [sfc]  The SFC WG has placed draft-wang-sfc-multi-layer-oam instate"Candidate for WG Adoption"
Is this an active adoption poll issued by the chairs? Candidate indicates potential or intent, not action, so far as I know.
As this is being discussed, does this draft conform with the SFC WG adopted OAM framework draft-ietf-sfc-oam-framework?

Thanks,

— Carlos Pignataro

On Oct 10, 2018, at 1:52 AM, xiao.min2@zte.com.cn<mailto:xiao.min2@zte.com.cn> wrote:


Hi SFC Chairs et al,


I support WG adotion of this draft, because this work of active OAM is within our charter and complementary with already adopted iOAM.


Best Regards,

Xiao Min


_______________________________________________
sfc mailing list
sfc@ietf.org<mailto:sfc@ietf.org>
https://www.ietf.org/mailman/listinfo/sfc

发件人:IETFSecretariat <ietf-secretariat-reply@ietf.org<mailto:ietf-secretariat-reply@ietf.org>>
收件人:draft-wang-sfc-multi-layer-oam@ietf.org<mailto:draft-wang-sfc-multi-layer-oam@ietf.org> <draft-wang-sfc-multi-layer-oam@ietf.org<mailto:draft-wang-sfc-multi-layer-oam@ietf.org>>sfc-chairs@ietf.org<mailto:sfc-chairs@ietf.org>  <sfc-chairs@ietf.org<mailto:sfc-chairs@ietf.org>>sfc@ietf.org<mailto:sfc@ietf.org> <sfc@ietf.org<mailto:sfc@ietf.org>>
日 期 :2018年10月09日 06:20
主 题 :[sfc] The SFC WG has placed draft-wang-sfc-multi-layer-oam in state"Candidate for WG Adoption"

The SFC WG has placed draft-wang-sfc-multi-layer-oam in state
Candidate for WG Adoption (entered by Joel Halpern)

The document is available at
https://datatracker.ietf.org/doc/draft-wang-sfc-multi-layer-oam/

Comment:
This document has been presented at several SFC working group sessions.  The
authors have asked for Working Group Adoption.  This starts a two week call
for that adoption.  Please speak up, preferably with supporting explanations,
in favor of or opposed to the working group adopting this document. The last
call will end CoB  somewhere 22-October-2018 (e.g. by the time I do anything
about it, it will be at least the 23rd everywhere.)

Thank you,
Joel and Jim

_______________________________________________
sfc mailing list
sfc@ietf.org<mailto:sfc@ietf.org>
https://www.ietf.org/mailman/listinfo/sfc