IETF Logo Mail Archive

Re: [nvo3] eVXLAN carrying Group information

"Pengshuping (Peng Shuping)" <pengshuping@huawei.com> Thu, 04 March 2021 02:24 UTC

Return-Path: <pengshuping@huawei.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 A22243A0B0E; Wed, 3 Mar 2021 18:24:10 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.899
X-Spam-Level:
X-Spam-Status: No, score=-1.899 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, HTML_MESSAGE=0.001, RCVD_IN_MSPIKE_H2=-0.001, SPF_HELO_NONE=0.001, SPF_PASS=-0.001, URIBL_BLOCKED=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 SNDV66Iwu_-e; Wed, 3 Mar 2021 18:24:07 -0800 (PST)
Received: from frasgout.his.huawei.com (frasgout.his.huawei.com [185.176.79.56]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 2A65B3A0B01; Wed, 3 Mar 2021 18:24:07 -0800 (PST)
Received: from fraeml739-chm.china.huawei.com (unknown [172.18.147.200]) by frasgout.his.huawei.com (SkyGuard) with ESMTP id 4DrZM91zb2z67vdS; Thu, 4 Mar 2021 10:19:49 +0800 (CST)
Received: from fraeml739-chm.china.huawei.com (10.206.15.220) by fraeml739-chm.china.huawei.com (10.206.15.220) with Microsoft SMTP Server (version=TLS1_2, cipher=TLS_ECDHE_RSA_WITH_AES_128_GCM_SHA256) id 15.1.2106.2; Thu, 4 Mar 2021 03:24:03 +0100
Received: from DGGEML424-HUB.china.huawei.com (10.1.199.41) by fraeml739-chm.china.huawei.com (10.206.15.220) with Microsoft SMTP Server (version=TLS1_0, cipher=TLS_ECDHE_RSA_WITH_AES_128_CBC_SHA) id 15.1.2106.2 via Frontend Transport; Thu, 4 Mar 2021 03:24:02 +0100
Received: from DGGEML512-MBX.china.huawei.com ([169.254.2.49]) by dggeml424-hub.china.huawei.com ([10.1.199.41]) with mapi id 14.03.0513.000; Thu, 4 Mar 2021 10:23:56 +0800
From: "Pengshuping (Peng Shuping)" <pengshuping@huawei.com>
To: Gyan Mishra <hayabusagsm@gmail.com>
CC: "apn@ietf.org" <apn@ietf.org>, "nvo3@ietf.org" <nvo3@ietf.org>
Thread-Topic: [nvo3] eVXLAN carrying Group information
Thread-Index: AdcORo5O2ZyXWAGiSueI62HOGIOv/v//uwSA//3mJICABCx0gP/9IG/w
Date: Thu, 04 Mar 2021 02:23:56 +0000
Message-ID: <4278D47A901B3041A737953BAA078ADE199663D4@dggeml512-mbx.china.huawei.com>
References: <4278D47A901B3041A737953BAA078ADE1994930E@DGGEML532-MBX.china.huawei.com> <CABNhwV0mh3fN3oLn4gEH3gk3OzJ4-jRzb_ppKN77-A5WYcjjpw@mail.gmail.com> <4278D47A901B3041A737953BAA078ADE1995068B@DGGEML532-MBX.china.huawei.com> <CABNhwV2EXmum-XELYwTMaKg-DpfXFs98r+WiB8Z6nQnxq12aOg@mail.gmail.com>
In-Reply-To: <CABNhwV2EXmum-XELYwTMaKg-DpfXFs98r+WiB8Z6nQnxq12aOg@mail.gmail.com>
Accept-Language: zh-CN, en-US
Content-Language: zh-CN
X-MS-Has-Attach: yes
X-MS-TNEF-Correlator:
x-originating-ip: [10.153.195.12]
Content-Type: multipart/related; boundary="_005_4278D47A901B3041A737953BAA078ADE199663D4dggeml512mbxchi_"; type="multipart/alternative"
MIME-Version: 1.0
X-CFilter-Loop: Reflected
Archived-At: <https://mailarchive.ietf.org/arch/msg/nvo3/gKXzQvjyQseQ1uYiowqZDH-kJ6c>
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: Thu, 04 Mar 2021 02:24:11 -0000

Hi Gyan,

It could be taken as a existing solution to be included in the gap analysis part, but different from APN.

Best regards,
Shuping


From: Gyan Mishra [mailto:hayabusagsm@gmail.com]
Sent: Tuesday, March 2, 2021 10:29 PM
To: Pengshuping (Peng Shuping) <pengshuping@huawei.com>
Cc: apn@ietf.org; nvo3@ietf.org
Subject: Re: [nvo3] eVXLAN carrying Group information

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<mailto: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<mailto:hayabusagsm@gmail.com>]
Sent: Monday, March 1, 2021 2:50 PM
To: Pengshuping (Peng Shuping) <pengshuping@huawei.com<mailto:pengshuping@huawei.com>>
Cc: apn@ietf.org<mailto:apn@ietf.org>; nvo3@ietf.org<mailto: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<mailto: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<mailto:nvo3@ietf.org>
https://www.ietf.org/mailman/listinfo/nvo3
--

[图像已被发件人删除。]<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 Architect

M 301 502-1347
13101 Columbia Pike
Silver Spring, MD

v2.23.0 | Report a Bug | By Email