IETF Logo Mail Archive

Re: [nvo3] eVXLAN carrying Group information

Gyan Mishra <hayabusagsm@gmail.com> Tue, 02 March 2021 14:29 UTC

Return-Path: <hayabusagsm@gmail.com>
X-Original-To: nvo3@ietfa.amsl.com
Delivered-To: nvo3@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id C7D1B3A18FD; Tue, 2 Mar 2021 06:29:27 -0800 (PST)
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 YOhfu_vb92TK; Tue, 2 Mar 2021 06:29:25 -0800 (PST)
Received: from mail-pf1-x42f.google.com (mail-pf1-x42f.google.com [IPv6:2607:f8b0:4864:20::42f]) (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 CE4D33A18FC; Tue, 2 Mar 2021 06:29:25 -0800 (PST)
Received: by mail-pf1-x42f.google.com with SMTP id q204so12880493pfq.10; Tue, 02 Mar 2021 06:29:25 -0800 (PST)
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=Z1ANABfEeX5uwGN94xUQzjZMblZD+kUq4wLYtVdN1Go=; b=pH9hDA7QGei7xYiPraF6fSKzRwRfIEXuHuNNpKW9O2FvHUuj6SyxMM/A2debKHuzU2 KnR92EoD6n/rEIqfUh9mYzBYIn+7J6rI8jOGpzhkYOY4LiL+eUQrtAqa+FUmYJxqPWsF F2KJPzs8oXRLdQC5iWjKm1OUkZQxxwTHcmpvnfAjLM0ZSJpNNtCZvaJVTWdWy1koyFw5 575kNALcoYktAaNdN3DtBOKdpUwaIINGZ9p7Mxo4m2oZ1WQvVaYWHFE7DpfQZjXHR0ie 2Ns9Bai+5+QynfrmjmGVf56h/5UimnpKjKsCqWkHqtXx6BpZKblscJdPk571E4yBxu+K trdQ==
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=Z1ANABfEeX5uwGN94xUQzjZMblZD+kUq4wLYtVdN1Go=; b=TVzza7Nv92IsiK4CzRkXonEgjeMUvwiXBwSJbG8ETrOYY7Yj1k6/tNNLp5Zju8wrq+ v+BCB0SKJbIOYax6/dY8IJuPlWJRBtRD/c1TgLFzftmocHJNhqdQmg4OMHTZD0UDefQh PxvBnnChRF9o90/JlgvVb/e3RiVmi7/b8WWpVQbBxLKQXFQl03d0FzyUxgoAXYncM2L5 f1sxzK9+6idjr8wg6iL4AONq9D8ShL8JBrO+yQb8y5yEb02ErjZPmMQBXIejLPoPgx4V U4EFsXxFDqtEz70WBIa877iuHDU06RrSDOnWSY2Z81UaPK49sSM8hzUYIvB+3Y2nwPbw DDaw==
X-Gm-Message-State: AOAM532pXsYU6Oxfc2QJkDBG5sjn1zJoTledMFa9CWrlqkh39under6t sWKYQ70JW9gJ3sYIx8oTN55/kz/d+H5+jUeXYJVw6Rv7t8k=
X-Google-Smtp-Source: ABdhPJxSZl5iOnIboFh/gCyM55PopA8e/o2zdCVZYCZRswJl7Rl42NdQOMGo3+rUUwULXoVQ79STRP9OFHacNnKhgao=
X-Received: by 2002:a63:db02:: with SMTP id e2mr4448368pgg.18.1614695364301; Tue, 02 Mar 2021 06:29:24 -0800 (PST)
MIME-Version: 1.0
References: <4278D47A901B3041A737953BAA078ADE1994930E@DGGEML532-MBX.china.huawei.com> <CABNhwV0mh3fN3oLn4gEH3gk3OzJ4-jRzb_ppKN77-A5WYcjjpw@mail.gmail.com> <4278D47A901B3041A737953BAA078ADE1995068B@DGGEML532-MBX.china.huawei.com>
In-Reply-To: <4278D47A901B3041A737953BAA078ADE1995068B@DGGEML532-MBX.china.huawei.com>
From: Gyan Mishra <hayabusagsm@gmail.com>
Date: Tue, 02 Mar 2021 09:29:13 -0500
Message-ID: <CABNhwV2EXmum-XELYwTMaKg-DpfXFs98r+WiB8Z6nQnxq12aOg@mail.gmail.com>
To: "Pengshuping (Peng Shuping)" <pengshuping@huawei.com>
Cc: "apn@ietf.org" <apn@ietf.org>, "nvo3@ietf.org" <nvo3@ietf.org>
Content-Type: multipart/related; boundary="0000000000009d014505bc8e8ff2"
Archived-At: <https://mailarchive.ietf.org/arch/msg/nvo3/X88N4yLX1iU6S2ZlfFiebldpgEg>
Subject: Re: [nvo3] eVXLAN carrying Group information
X-BeenThere: nvo3@ietf.org
X-Mailman-Version: 2.1.29
Precedence: list
List-Id: "Network Virtualization Overlays \(NVO3\) Working Group" <nvo3.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/nvo3>, <mailto:nvo3-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/nvo3/>
List-Post: <mailto:nvo3@ietf.org>
List-Help: <mailto:nvo3-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/nvo3>, <mailto:nvo3-request@ietf.org?subject=subscribe>
X-List-Received-Date: Tue, 02 Mar 2021 14:29:28 -0000

That’s great news that this can be a viable marking option for APN
signaling.

Kind Regards

Gyan

On Tue, Mar 2, 2021 at 3:56 AM Pengshuping (Peng Shuping) <
pengshuping@huawei.com> wrote:

> Hi Gyan,
>
>
>
> Many thanks for your information!
>
>
>
> I found the Group Policy ID explained as below,
>
>
>
>    o  Group Policy ID: 16-bit identifier that indicates the Group Policy
>
>       ID being encapsulated by this GBP shim header.  The Default GBP ID
>
>       value is special and indicates that the GBP option was not set.
>
>       Packet filters SHOULD be able to match on the Default GBP ID value
>
>       as a way to match packets that do not have the GBP option set.
>
>       The default Default GBP ID is 0, but MAY be configured to be a
>
>       value other than 0.  The allocation of Group Policy ID values is
>
>       outside the scope of this document.
>
>
>
> It seems that we could add this in the gap analysis draft,
>
> https://datatracker.ietf.org/doc/draft-peng-apn-scope-gap-analysis/
>
>
>
> Best regards,
>
> Shuping
>
>
>
>
>
>
>
> *From:* Gyan Mishra [mailto:hayabusagsm@gmail.com]
> *Sent:* Monday, March 1, 2021 2:50 PM
> *To:* Pengshuping (Peng Shuping) <pengshuping@huawei.com>
> *Cc:* apn@ietf.org; nvo3@ietf.org
> *Subject:* Re: [nvo3] eVXLAN carrying Group information
>
>
>
>
>
> Shuping
>
>
>
> I am not sure if you are referring to VXLAN-GPE vxlan Generic protocol
> extension which has changes in the vxlan header to support multi protocol
> encapsulation, OAM and BUM.
>
>
>
> https://tools.ietf.org/html/draft-ietf-nvo3-vxlan-gpe-10
>
>
>
>
>
>    The capabilities of the VXLAN-GPE protocol can be extended by
>
>    defining next protocol "shim" headers that are used to implement new
>
>    data plane functions.  For example, Group-Based Policy (GBP) or In-
>
>    situ Operations, Administration, and Maintenance (IOAM) metadata
>
>    functionalities can be added as specified in
>
>    [I-D.lemon-vxlan-lisp-gpe-gbp <https://tools.ietf.org/html/draft-ietf-nvo3-vxlan-gpe-10#ref-I-D.lemon-vxlan-lisp-gpe-gbp>] and
>
>    [I-D.brockners-ippm-ioam-vxlan-gpe <https://tools.ietf.org/html/draft-ietf-nvo3-vxlan-gpe-10#ref-I-D.brockners-ippm-ioam-vxlan-gpe>].
>
>
>
>
>
> Kind Regards
>
>
>
> Gyan
>
>
>
> On Sun, Feb 28, 2021 at 10:21 PM Pengshuping (Peng Shuping) <
> pengshuping@huawei.com> wrote:
>
> Dear all,
>
>
>
> Anybody knows about using eVXLAN to carry the Group information? What is
> the scenario? How the group is identified?
>
>
>
> Thank you very much!
>
>
>
> Best regards,
>
> Shuping
>
>
>
> _______________________________________________
> nvo3 mailing list
> nvo3@ietf.org
> https://www.ietf.org/mailman/listinfo/nvo3
>
> --
>
> [image: 图像已被发件人删除。] <http://www.verizon.com/>
>
> *Gyan Mishra*
>
> *Network Solutions Architect *
>
>
>
> *M 301 502-1347 13101 Columbia Pike
> <https://www.google.com/maps/search/13101+Columbia+Pike?entry=gmail&source=g>
> *Silver Spring, MD
>
>
>
-- 

<http://www.verizon.com/>

*Gyan Mishra*

*Network Solutions A**rchitect *



*M 301 502-134713101 Columbia Pike *Silver Spring, MD

v2.23.0 | Report a Bug | By Email