[sfc] Fwd: Fwd: I-D Action: draft-ietf-sfc-multi-layer-oam-16.txt
Greg Mirsky <gregimirsky@gmail.com> Mon, 01 November 2021 17:36 UTC
Return-Path: <gregimirsky@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 79B6F3A5A9A; Mon, 1 Nov 2021 10:36:35 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.097
X-Spam-Level:
X-Spam-Status: No, score=-2.097 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, SPF_HELO_NONE=0.001, SPF_PASS=-0.001, URIBL_BLOCKED=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 ehtwEQBDsRw3; Mon, 1 Nov 2021 10:36:30 -0700 (PDT)
Received: from mail-ed1-x532.google.com (mail-ed1-x532.google.com [IPv6:2a00:1450:4864:20::532]) (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 EC4ED3A5A87; Mon, 1 Nov 2021 10:36:26 -0700 (PDT)
Received: by mail-ed1-x532.google.com with SMTP id z20so67195851edc.13; Mon, 01 Nov 2021 10:36:26 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20210112; h=mime-version:references:in-reply-to:from:date:message-id:subject:to :cc; bh=zh37BZkFnpD9tcWP9YnqoO0Dz2f7hk2i9DGY18orzuw=; b=D5uW+HK7I1SjSFFH12cuM40BO3OIJxtk+9lqqscLQeM0xTQcps+Scch5I+eScOFuyk UNApEsY10aRSuO6Yqgp8aTRPiVL71HFMlykLT+kOvprhInWZVCKWFW8PWdsdAPj8HmWT X6SdukIpDWsXYRswcDSUU4TtW6pdW0PoEq/3Bj3AFPegGzxDuR5PprFqCRTVoLVAFt3Y zQ1dGHFa7Jh7hRJV1dXxDQhDnC1MTZvZ9JqldRgWzdiigCR1pz4nNzmF7AEsslHgERGb BjRrfutWvGEmLpOFQOro+oLVGb75lO6ruV7CdzwVQXYYcCT1MmPATCsFjzFHFl/V5iw2 D94w==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20210112; h=x-gm-message-state:mime-version:references:in-reply-to:from:date :message-id:subject:to:cc; bh=zh37BZkFnpD9tcWP9YnqoO0Dz2f7hk2i9DGY18orzuw=; b=KGQYC/AEPluV9IOipQswyJIVOpM/X0rwulSTMfbtrJWB3aWpyQdVKFgzphLyWR8ctz 7/0bbV/HN2d8kp315JS1EI/pdpa2PlVUrQKO/jv8DsM9Tbo50xBJihhm/lqGMQHLr/lX 7bwXsXsJKv/RP4htThSmRw2c2z4Ewhz22QLM7u9TuWRVwJlCRycYCXuLpN2dOXB8HbPO zGiY2FKdXkZUEjJsG5GEv9sB8zkLslhcGiaxo16pmHPMzPVLfJUbXEHSELTN+QY5FkEq fOg4IB4y5zRy0fLC25BKUMhtUt8nWw/snoo87/TBEsx6bGPC4fd+UVlMV1fUivc0/OkJ Rxmw==
X-Gm-Message-State: AOAM533QrrQRLuVyR9QF/2oJX0ZGcI8fmgoKwykSJqaWbLudVfHpEzJE Tes7afT0q78TI2OJK3zU0SLVwIirjfxfjTYXNiDM/kyD
X-Google-Smtp-Source: ABdhPJzP3YAg9yYWCbg4eb1BYtbOiNzjnLGQvoEh3ctpuujiyuRoU7WYhwDDaOB9u21N9pbfHQWLvS31ALS/uRwL7yo=
X-Received: by 2002:a17:906:369a:: with SMTP id a26mr37121828ejc.539.1635788180032; Mon, 01 Nov 2021 10:36:20 -0700 (PDT)
MIME-Version: 1.0
References: <163466112750.7235.4587641153411151399@ietfa.amsl.com> <CA+RyBmXVKkEfNx707k9qXk1HoPNQg2EG8RhSM75TL-nbGJ6RoQ@mail.gmail.com> <e89dc949-cd19-f63c-a5cd-3b94af2cb4f9@joelhalpern.com> <CA+RyBmVxt3SKhQrPqrnCN3v0LS+E-+VLs8Ck8vURetGdk_mU+g@mail.gmail.com> <CA+RyBmU=KSUfehgGV0Mp-c-mdJfQQZ2-jCYrJSQ-gAU+vTigzQ@mail.gmail.com> <CANtnpwjBH2F7bQjBDuH90QayETASG=OdnC-5HZceSgFvhHqpTg@mail.gmail.com>
In-Reply-To: <CANtnpwjBH2F7bQjBDuH90QayETASG=OdnC-5HZceSgFvhHqpTg@mail.gmail.com>
From: Greg Mirsky <gregimirsky@gmail.com>
Date: Mon, 01 Nov 2021 10:36:09 -0700
Message-ID: <CA+RyBmW2YUH-ZfDy-YjPx6TO6vxy9ATAJdYj5g0X+V+VL-uv7A@mail.gmail.com>
To: sfc-chairs@ietf.org, Service Function Chaining IETF list <sfc@ietf.org>, "B. Khasnabish" <vumip1@gmail.com>
Cc: draft-ietf-sfc-multi-layer-oam@ietf.org
Content-Type: multipart/alternative; boundary="0000000000006613b005cfbd9d8e"
Archived-At: <https://mailarchive.ietf.org/arch/msg/sfc/8HBnkE4wmtaGR3uc-V6XllVp65M>
Subject: [sfc] Fwd: Fwd: I-D Action: draft-ietf-sfc-multi-layer-oam-16.txt
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: Mon, 01 Nov 2021 17:36:36 -0000
Dear Joel and Jim, I'm forwarding the response to the IPR poll from Bhumip Khasnabish. Regards, Greg ---------- Forwarded message --------- From: B. Khasnabish <vumip1@gmail.com> Date: Sat, Oct 30, 2021 at 11:24 PM Subject: Re: Fwd: [sfc] I-D Action: draft-ietf-sfc-multi-layer-oam-16.txt To: Greg Mirsky <gregimirsky@gmail.com> Cc: <meng.wei2@zte.com.cn>, <18555817@qq.com>, Kent Leung (kleung) < kleung@cisco.com>, Mishra, Gyan S <gyan.s.mishra@verizon.com>, Linda Wang < lindawangjoy@gmail.com>, <18918588897@189.cn>, Gyan Mishra < hayabusagsm@gmail.com> Hi Greg, Thanks and yes, I support the publication of this draft as an Individual Contributor. Also, do not have any IPR to declare. Once again, many Thanks in advance. Best Regards, Bhumip ----------------------------------------------------------------------------------------- Bhumip <https://about.me/bhumip>Khasnabish | +1-781-752-8003 (m) vumip1@gmail.com On Fri, Oct 29, 2021 at 3:58 PM Greg Mirsky <gregimirsky@gmail.com> wrote: > Dear All, > I much appreciate your help responding to SFC WG Chair question about the > IPR related to draft-ietf-sfc-multi-layer-oam. If you are not currently > subscribed to the SFC WG mailing list, please feel free to send your > response to the IPR question to me replying to this mail. I'll forward your > response to SFC WG Chairs promptly. > > Thank you for your help. > > Regards, > Greg > > On Wed, Oct 20, 2021 at 7:37 AM Greg Mirsky <gregimirsky@gmail.com> wrote: > >> Dear All, >> I hope this note finds you well. >> It has been a long work on this draft, and we're moving to the finish >> line, we are getting closer to the publication. I much appreciate your >> contributions to this document. As you may have noticed, the document now >> includes also the consistency and return path extensions. That was the only >> chance to have these published. As a result, I had to make a hard choice to >> keep the number of names on the front page under control (five is the >> recommended limit). It is IETF practice to credit contributors in a >> separate section. So, I've done that. I hope you understand. >> At this time, I greatly appreciate your help and timely response to the >> IPR poll by stating "I am not aware of any undisclosed IPR related to this >> draft". Also, in a separate thread >> <https://mailarchive.ietf.org/arch/msg/sfc/tcR6qBAkoQZfvn8JQ5TE6-dj4aU/>, >> you can express your support for the publication of this draft. >> Please let me know if you have any questions. >> >> Kind regards, >> Greg >> >> ---------- Forwarded message --------- >> From: Joel M. Halpern <jmh@joelhalpern.com> >> Date: Tue, Oct 19, 2021 at 11:02 AM >> Subject: Re: Fwd: [sfc] I-D Action: draft-ietf-sfc-multi-layer-oam-16.txt >> To: Greg Mirsky <gregimirsky@gmail.com>, Service Function Chaining IETF >> list <sfc@ietf.org> >> >> >> While we are conducting the last call, and deciding who will shepherd >> this document... >> 1) If anyone would like to shepherd it, please let me or Jim know. >> 2) Would the authors and key contributors please confirm to the lsit >> that all known relevant IPR has been disclosed. >> >> Thank you, >> Joel >> >> On 10/19/2021 12:39 PM, Greg Mirsky wrote: >> > Dear Jim and Joel, >> > we've completed merging the substantive parts of two SFC OAM drafts. >> > Many thanks to Med for his thorough reviews, thoughtful comments that >> > helped us improve the document. The authors believe that the draft is >> > stable and is ready for the WG LC. We greatly appreciate your >> > consideration of starting the WG LC and are committed to addressing >> > questions and comments. >> > >> > Regards, >> > Greg (on behalf off the authors) >> > >> > ---------- Forwarded message --------- >> > From: <internet-drafts@ietf.org <mailto:internet-drafts@ietf.org>> >> > Date: Tue, Oct 19, 2021 at 9:33 AM >> > Subject: [sfc] I-D Action: draft-ietf-sfc-multi-layer-oam-16.txt >> > To: <i-d-announce@ietf.org <mailto:i-d-announce@ietf.org>> >> > Cc: <sfc@ietf.org <mailto:sfc@ietf.org>> >> > >> > >> > >> > A New Internet-Draft is available from the on-line Internet-Drafts >> > directories. >> > This draft is a work item of the Service Function Chaining WG of the >> IETF. >> > >> > Title : Active OAM for Service Function Chaining >> > Authors : Greg Mirsky >> > Wei Meng >> > Ting Ao >> > Kent Leung >> > Gyan Mishra >> > Filename : draft-ietf-sfc-multi-layer-oam-16.txt >> > Pages : 37 >> > Date : 2021-10-19 >> > >> > Abstract: >> > A set of requirements for active Operation, Administration, and >> > Maintenance (OAM) of Service Function Chains (SFCs) in a network is >> > presented in this document. Based on these requirements, an >> > encapsulation of active OAM messages in SFC and a mechanism to >> detect >> > and localize defects are described. >> > >> > This document updates RFC 8300. Particularly, it updates the >> > definition of O (OAM) bit in the Network Service Header (NSH) (RFC >> > 8300) and defines how an active OAM message is identified in the >> NSH. >> > >> > >> > The IETF datatracker status page for this draft is: >> > https://datatracker.ietf.org/doc/draft-ietf-sfc-multi-layer-oam/ >> > <https://datatracker.ietf.org/doc/draft-ietf-sfc-multi-layer-oam/> >> > >> > There is also an HTML version available at: >> > https://www.ietf.org/archive/id/draft-ietf-sfc-multi-layer-oam-16.html >> > <https://www.ietf.org/archive/id/draft-ietf-sfc-multi-layer-oam-16.html >> > >> > >> > A diff from the previous version is available at: >> > https://www.ietf.org/rfcdiff?url2=draft-ietf-sfc-multi-layer-oam-16 >> > <https://www.ietf.org/rfcdiff?url2=draft-ietf-sfc-multi-layer-oam-16> >> > >> > >> > Internet-Drafts are also available by anonymous FTP at: >> > ftp://ftp.ietf.org/internet-drafts/ < >> ftp://ftp.ietf.org/internet-drafts/> >> > >> > >> > _______________________________________________ >> > sfc mailing list >> > sfc@ietf.org <mailto:sfc@ietf.org> >> > https://www.ietf.org/mailman/listinfo/sfc >> > <https://www.ietf.org/mailman/listinfo/sfc> >> >
- [sfc] I-D Action: draft-ietf-sfc-multi-layer-oam-… internet-drafts
- [sfc] Fwd: I-D Action: draft-ietf-sfc-multi-layer… Greg Mirsky
- Re: [sfc] Fwd: I-D Action: draft-ietf-sfc-multi-l… Joel M. Halpern
- Re: [sfc] Fwd: I-D Action: draft-ietf-sfc-multi-l… Greg Mirsky
- Re: [sfc] Fwd: I-D Action: draft-ietf-sfc-multi-l… Gyan Mishra
- [sfc] Fwd: Fwd: I-D Action: draft-ietf-sfc-multi-… Greg Mirsky
- Re: [sfc] Fwd: I-D Action: draft-ietf-sfc-multi-l… meng.wei2
- Re: [sfc] Fwd: I-D Action: draft-ietf-sfc-multi-l… Linda Wang
- Re: [sfc] Fwd: I-D Action: draft-ietf-sfc-multi-l… Gyan Mishra
- [sfc] Fwd: Fwd: Fwd: I-D Action: draft-ietf-sfc-m… Greg Mirsky
- [sfc] Fwd: Fwd: Fwd: I-D Action: draft-ietf-sfc-m… Greg Mirsky
- [sfc] Fwd: Fwd: I-D Action: draft-ietf-sfc-multi-… Donald Eastlake
- [sfc] Fwd: Please Respond on IPR in your Internet… Donald Eastlake