Re: [Apn] [nvo3] eVXLAN carrying Group information

Gyan Mishra <hayabusagsm@gmail.com> Mon, 01 March 2021 06:50 UTC

Return-Path: <hayabusagsm@gmail.com>
X-Original-To: apn@ietfa.amsl.com
Delivered-To: apn@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 4296D3A168D; Sun, 28 Feb 2021 22:50:30 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -0.187
X-Spam-Level:
X-Spam-Status: No, score=-0.187 tagged_above=-999 required=5 tests=[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, RCVD_IN_DNSWL_NONE=-0.0001, SPF_HELO_NONE=0.001, SPF_PASS=-0.001, T_REMOTE_IMAGE=0.01, 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 Izpc6A-VGwRQ; Sun, 28 Feb 2021 22:50:28 -0800 (PST)
Received: from mail-pj1-x1034.google.com (mail-pj1-x1034.google.com [IPv6:2607:f8b0:4864:20::1034]) (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 23B6F3A16CB; Sun, 28 Feb 2021 22:50:22 -0800 (PST)
Received: by mail-pj1-x1034.google.com with SMTP id b15so10429940pjb.0; Sun, 28 Feb 2021 22:50:22 -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=JhUJJRc+QodQtM6n38bNOGb+i1vUkNFyAELjwr0HhOE=; b=hwrlM/iwhVpPg8jLrL6UuDKEqYd3Gok0bG1OqzMWUXD3w3zyMvO2wIzE3IYqQXp1sc f2/KKzdEaqdkUzTM2382S+0OwFVo4sqKW0wGYGxgvMttFn10irqMuwLakHmSi1QqG6KQ DLpOKF+kg9DYoeAnyYpqIbGJxNZ1me8hZ3GL/dD0fgFp2wvULumUqaspOMOQQdfTarX+ fUnb60oFsqL2KdFFI5hbSGnPWI06i/+Fr+3DjMy4oirUDqKORCpsCx3lplwE0J+HoUq8 OSYMDstdYBz06PcxFVD+CkTH3khNkxI/eIn1BxDI0Xp7wTjfNZu88ZSQbo/6siw3N8XM vbWw==
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=JhUJJRc+QodQtM6n38bNOGb+i1vUkNFyAELjwr0HhOE=; b=jb9jqeY/yjl7SlEhP1qWVLsV6Jj0Rr/nppbfGffJn//C2HVfACqY4saGeFltTmLHHB XcT1ZQNic2CYerScBYg25x0/wu1d0OWIKWIE1s6ExFDZAheWDBds5Ev+HwiWfl/zc7B/ U49jtm2eM/mkgqRtoU3UcUDc/NbJYcwhlyYNZXDpH6VhQje/X3lVdaagxCG9P3QJZ2gi NkaD6YfLJLDZfFc9tUrLbdCHQukZ7A6IgipbmK2tF3NYx3k33eMO4J/oBaGy9g40ohI7 T1eSwyaaJzxAivJslvxF9nRCUg99q/16ExBMYPRifulBnETWio3QJzVKrViDNmHv8P4f Xthg==
X-Gm-Message-State: AOAM533SIhIN3osWc1HmKFWHCQjMfXt5ZwoZjIq6wvcfK7MtqMNforbA L7VgfHy8WvET0wP1eEeEH7R4ZftXrOMpxEa5OiU=
X-Google-Smtp-Source: ABdhPJyz9kZrufWL4Aux7VibXRZZU2qIB9/As5r3BlN9xWgS7Tj0qoF+TGkFzFeAPEhtoA+rQwgdvmWxBN9Cc2TNdos=
X-Received: by 2002:a17:90a:4a0a:: with SMTP id e10mr15336768pjh.112.1614581419586; Sun, 28 Feb 2021 22:50:19 -0800 (PST)
MIME-Version: 1.0
References: <4278D47A901B3041A737953BAA078ADE1994930E@DGGEML532-MBX.china.huawei.com>
In-Reply-To: <4278D47A901B3041A737953BAA078ADE1994930E@DGGEML532-MBX.china.huawei.com>
From: Gyan Mishra <hayabusagsm@gmail.com>
Date: Mon, 01 Mar 2021 01:50:09 -0500
Message-ID: <CABNhwV0mh3fN3oLn4gEH3gk3OzJ4-jRzb_ppKN77-A5WYcjjpw@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/alternative; boundary="000000000000f9b97c05bc740765"
Archived-At: <https://mailarchive.ietf.org/arch/msg/apn/ne_minICyP319TBpsO5Ve-A1eJg>
Subject: Re: [Apn] [nvo3] eVXLAN carrying Group information
X-BeenThere: apn@ietf.org
X-Mailman-Version: 2.1.29
Precedence: list
List-Id: Application-aware Networking <apn.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/apn>, <mailto:apn-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/apn/>
List-Post: <mailto:apn@ietf.org>
List-Help: <mailto:apn-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/apn>, <mailto:apn-request@ietf.org?subject=subscribe>
X-List-Received-Date: Mon, 01 Mar 2021 06:50:30 -0000

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
>
-- 

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

*Gyan Mishra*

*Network Solutions A**rchitect *



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