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:[email protected]] Sent: Tuesday, March 2, 2021 10:29 PM To: Pengshuping (Peng Shuping) <[email protected]> Cc: [email protected]; [email protected] 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) <[email protected]<mailto:[email protected]>> 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:[email protected]<mailto:[email protected]>] Sent: Monday, March 1, 2021 2:50 PM To: Pengshuping (Peng Shuping) <[email protected]<mailto:[email protected]>> Cc: [email protected]<mailto:[email protected]>; [email protected]<mailto:[email protected]> 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) <[email protected]<mailto:[email protected]>> 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 [email protected]<mailto:[email protected]> 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
_______________________________________________ nvo3 mailing list [email protected] https://www.ietf.org/mailman/listinfo/nvo3
