Re: [nvo3-dt-encap] NVO3 Encap Design Team Weekly Sync

["Ganga, Ilango S" <[e-mail]>]

Hi Sami,

Here is a proposed text for Point 1: 
This suggested text below keeps the same message without getting too much into implementation details, as there are multiple ways for data plane implementations.  I borrowed a sentence from your point 3 below.

Suggested text for point 1:

We recommend the following enhancements to Geneve to make it more suitable to hardware and yet provide the flexibility for software:

We would propose a text such as, while TLV are more flexible, a control plane can restrict the number of option TLVs as well the order and size of the TLVs to make it simpler for a data plane implementation in software or hardware to handle. For example, there may be some critical information such as secure hash that must be processed in certain order at lowest latency.

A control plane can negotiate a subset of option TLVs and certain TLV ordering, as well can limit the total number of option TLVs present in the packet, for example, to allow hardware capable of processing fewer options. Hence, the control planes need to have the ability to describe the supported TLVs subset and their order.

The Geneve draft could specify that the subset and order of option TLVs should be configurable for each remote NVE in the absence of a protocol control plane.

Your other text for points 2 and 3 look fine.

Regards,
Ilango


-----Original Message-----
From: Sami Boutros [mailto:[e-mail]] 
Sent: Thursday, March 9, 2017 4:55 PM
To: Erik Nordmark <[e-mail]>; Erik Nordmark <[e-mail]>; Ganga, Ilango S <[e-mail]>; Pankaj Garg <[e-mail]>; [e-mail]; Sam Aldrin <[e-mail]>; Michael Smith (michsmit) <[e-mail]>
Subject: Re: [nvo3-dt-encap] NVO3 Encap Design Team Weekly Sync

Hi Guys,

Here is the suggested text for point 3 below.

4. We compared the TLV vs Bit-fields style extension and it was deemed that parsing both TLV and bit-fields is expensive and while bit-fields may be simpler to parse, it is also more restrictive and requires guessing which extensions will be widely implemented so they can get early bit assignments for efficiency, as well Bit-fields are not flexible enough to address the requirement of variable length and different subtypes of the same option. While TLV are more flexible, a control plane can restrict the number of option TLVs as well the order and size of the TLVs to make it simpler for a data plane implementation to handle.


As well added for point 2 the following:

The following use cases for extensions shows that there is a strong requirement to support variable length extensions with possible different subtypes.

And for point 1:

We recommend the following enhancements to Geneve to address shortcomings to make it more suitable to hardware and yet provide the flexibility for software:

We would propose a text such as, TLV processing may not be easy processed in TCAM. There may be some critical information such as secure hash that must get processed at lowest latency. A control plane can negotiate a subset of option TLVs and guarantee certain TLV ordering, as well can limit the total number of option TLVs present in the packet, to allow hardware capable of processing one or few options TLV in TCAM. Hence, the control planes defined today need to add the ability to describe the supported TLVs subset and their order.

The Geneve draft could specify that the subset and order of option TLVs should be configurable for each remote NVE in the absence of a protocol control plane.



Please let me know if you are good with the changes and I will submit the 01 version before the cut-off.

Thanks,


Sami



On 3/7/17, 9:18 AM, "Erik Nordmark" <[e-mail]> wrote:

>On 3/7/17 8:14 AM, Sami Boutros wrote:
>> Yes, IMO we need some edits.
>>
>> 1- To update the recommendations to Geneve, not to require a total option length of 64 bytes.
>> 2- To add in the use case section that there is a strong requirement to support variable length option with possible different subtypes.
>> 3- To clarify little more that ordered fixed length TLV can be achieved using a control plane, and this will be equivalent to bit-maps.
>
>Sounds good.
>
>However, bananas and apples are not equivalent AFAIK, so you need some 
>more clear wording for the last item.
>
>Thanks,
>     Erik
>
>
>>
>> Thanks,
>>
>> Sami
>>
>> On 3/7/17, 7:59 AM, "Erik Nordmark" <[e-mail]> wrote:
>>
>>> Also, are there any suggested edits with clarifications that we want 
>>> to put in an -01 draft before the IETF deadline?
>>>
>>> Thanks,
>>>     Erik
>>>
>>> On 3/6/17 5:37 PM, Ganga, Ilango S wrote:
>>>> Can we meet for 30mins, I would like to go over the recommendations 
>>>> in the DT draft to get clarifications.
>>>>
>>>> *From:* Pankaj Garg [mailto:[e-mail]]
>>>> *Sent:* Monday, March 6, 2017 4:25 PM
>>>> *To:* Sami Boutros <[e-mail]>; [e-mail]; 
>>>> Sam Aldrin <[e-mail]>; Erik Nordmark 
>>>> <[e-mail]>; Michael Smith (michsmit) 
>>>> <[e-mail]>; Ganga, Ilango S <[e-mail]>
>>>> *Subject:* RE: NVO3 Encap Design Team Weekly Sync
>>>>
>>>> Is there anything we want to discuss? Otherwise I can cancel it. In 
>>>> general I guess, once our recommendation is adopted, we can 
>>>> finalize the DT draft and conclude the group?
>>>>
>>>> *From:* Sami Boutros [mailto:[e-mail]]
>>>> *Sent:* Monday, March 6, 2017 4:21 PM
>>>> *To:* Pankaj Garg <[e-mail] 
>>>> <mailto:[e-mail]>>; [e-mail] 
>>>> <mailto:[e-mail]>; Sam Aldrin <[e-mail] 
>>>> <mailto:[e-mail]>>; Erik Nordmark <[e-mail] 
>>>> <mailto:[e-mail]>>; Michael Smith (michsmit) 
>>>> <[e-mail] <mailto:[e-mail]>>; Ganga, Ilango S 
>>>> <[e-mail] <mailto:[e-mail]>>
>>>> *Subject:* Re: NVO3 Encap Design Team Weekly Sync
>>>>
>>>> Is the meeting on tomorrow?
>>>>
>>>> Thanks,
>>>>
>>>> Sami
>>>>
>>>> *From: *[e-mail] <mailto:[e-mail]>
>>>> *When: *8:00 AM - 10:00 AM March 7, 2017
>>>> *Subject: *NVO3 Encap Design Team Weekly Sync
>>>> *Location: *Skype Meeting
>>>>
>>>> Sorry for being late on this. I have been struggling on the home 
>>>> front with both my kids and wife down with flu.
>>>>
>>>> I am setting up the regular 2 hour sync, based on preferred time in 
>>>> doodle. If an alternative method like WebEx is preferred for the 
>>>> online call, then please set it up as I only have access to Skype.
>>>>
>>>> Thanks
>>>>
>>>> Pankaj
>>>>
>>>>
>>>> .........................................................................................................................................
>>>> Join online meeting
>>>> <https://urldefense.proofpoint.com/v2/url?u=https-3A__na01.safelink
>>>> s.protection.outlook.com_-3Furl-3Dhttps-253A-252F-252Furldefense.pr
>>>> oofpoint.com-252Fv2-252Furl-253Fu-253Dhttps-2D3A-5F-5Fmeet.lync.com
>>>> -5Fmicrosoft-5Fpankajg-5F1XVG28EY-2526d-253DDwMFAw-2526c-253DuilaK9
>>>> 0D4TOVoH58JNXRgQ-2526r-253DIVzcTRLQdpta08L0b-5Fy2zDkqvwJhRKMCAbX-2D
>>>> 2K-2DLV98-2526m-253DhyNBA2gFelf-2D3jN7xMzPm2jkEkmesGmpklCKhp8tc1k-2
>>>> 526s-253Dgj1CBH3VLpxwGaz9NUKOYdWV1lgwC-5FmBv0Yp8jV9V0k-2526e-253D-2
>>>> 6data-3D02-257C01-257Cpankajg-2540microsoft.com-257Cf0f2e375328e442
>>>> d16c108d464efe3b1-257C72f988bf86f141af91ab2d7cd011db47-257C1-257C0-
>>>> 257C636244428916188134-26sdata-3DIRpuBv1RVMOOzY6hqgqM19sEizmyxrUzcW
>>>> Zq6MUj9fI-253D-26reserved-3D0&d=DwIC-g&c=uilaK90D4TOVoH58JNXRgQ&r=I
>>>> VzcTRLQdpta08L0b_y2zDkqvwJhRKMCAbX-2K-LV98&m=XlrYfnYa1Nis6dhmSfSkIj
>>>> qS9ZivuqDijjUPgQJ7GoI&s=kMWc85qNWhvyr1T0Ed9-wjbaH5dnPCslBukZW0MYDls
>>>> &e= >
>>>>
>>>> Join by Phone
>>>> [phone] <tel:[phone]> (Dial-in Number) English (United 
>>>> +States)
>>>>
>>>> Find local number
>>>> <https://urldefense.proofpoint.com/v2/url?u=https-3A__na01.safelink
>>>> s.protection.outlook.com_-3Furl-3Dhttps-253A-252F-252Furldefense.pr
>>>> oofpoint.com-252Fv2-252Furl-253Fu-253Dhttps-2D3A-5F-5Fdialin.lync.c
>>>> om-5F8551f4c1-2D2Dbea3-2D2D441a-2D2D8738-2D2D69aa517a91c5-2526d-253
>>>> DDwMFAw-2526c-253DuilaK90D4TOVoH58JNXRgQ-2526r-253DIVzcTRLQdpta08L0
>>>> b-5Fy2zDkqvwJhRKMCAbX-2D2K-2DLV98-2526m-253DhyNBA2gFelf-2D3jN7xMzPm
>>>> 2jkEkmesGmpklCKhp8tc1k-2526s-253DCfm-5FE3q4y1VF5-5FIYX9xUn2fog7HFS0
>>>> 28FDTPFbe4t0E-2526e-253D-26data-3D02-257C01-257Cpankajg-2540microso
>>>> ft.com-257Cf0f2e375328e442d16c108d464efe3b1-257C72f988bf86f141af91a
>>>> b2d7cd011db47-257C1-257C0-257C636244428916188134-26sdata-3DtsWBUikP
>>>> ZqlV40GDni-252BHbC6aA-252FzouZLP-252F7JLcVSie-252FE-253D-26reserved
>>>> -3D0&d=DwIC-g&c=uilaK90D4TOVoH58JNXRgQ&r=IVzcTRLQdpta08L0b_y2zDkqvw
>>>> JhRKMCAbX-2K-LV98&m=XlrYfnYa1Nis6dhmSfSkIjqS9ZivuqDijjUPgQJ7GoI&s=n
>>>> A0C5SYhfM7S3hjKYpMwt7W0-DEMxQyteyHY_JGxN-c&e= >
>>>>
>>>> Conference ID: 61250967
>>>> Help
>>>>
>>>>
>>>> Welcome to Skype for Business Online Meetings. All participants 
>>>> using the Join by Phone option must dial the full number for call access.
>>>> .........................................................................................................................................
>>>> _______________________________________________ nvo3-dt-encap 
>>>> mailing list [e-mail] <mailto:[e-mail]> 
>>>> https://urldefense.proofpoint.com/v2/url?u=https-3A__www.ietf.org_m
>>>> ailman_listinfo_nvo3-2Ddt-2Dencap&d=DwICAg&c=uilaK90D4TOVoH58JNXRgQ
>>>> &r=IVzcTRLQdpta08L0b_y2zDkqvwJhRKMCAbX-2K-LV98&m=hyNBA2gFelf-3jN7xM
>>>> zPm2jkEkmesGmpklCKhp8tc1k&s=sbwimXLUWrBM-KyYpfPOdtKdnFdBdeDMoN25x3Z
>>>> lceE&e= 
>>>> <https://urldefense.proofpoint.com/v2/url?u=https-3A__na01.safelink
>>>> s.protection.outlook.com_-3Furl-3Dhttps-253A-252F-252Furldefense.pr
>>>> oofpoint.com-252Fv2-252Furl-253Fu-253Dhttps-2D3A-5F-5Fwww.ietf.org-
>>>> 5Fmailman-5Flistinfo-5Fnvo3-2D2Ddt-2D2Dencap-2526d-253DDwICAg-2526c
>>>> -253DuilaK90D4TOVoH58JNXRgQ-2526r-253DIVzcTRLQdpta08L0b-5Fy2zDkqvwJ
>>>> hRKMCAbX-2D2K-2DLV98-2526m-253DhyNBA2gFelf-2D3jN7xMzPm2jkEkmesGmpkl
>>>> CKhp8tc1k-2526s-253DsbwimXLUWrBM-2DKyYpfPOdtKdnFdBdeDMoN25x3ZlceE-2
>>>> 526e-253D-26data-3D02-257C01-257Cpankajg-2540microsoft.com-257Cf0f2
>>>> e375328e442d16c108d464efe3b1-257C72f988bf86f141af91ab2d7cd011db47-2
>>>> 57C1-257C0-257C636244428916188134-26sdata-3DSHe3fXca2D-252FwA9ydub9
>>>> d6KB0IvpzcKiKP3ifaQLrir4-253D-26reserved-3D0&d=DwIC-g&c=uilaK90D4TO
>>>> VoH58JNXRgQ&r=IVzcTRLQdpta08L0b_y2zDkqvwJhRKMCAbX-2K-LV98&m=XlrYfnY
>>>> a1Nis6dhmSfSkIjqS9ZivuqDijjUPgQJ7GoI&s=slfZ_J5KI1SZk8FdNJgN4iUzP__J
>>>> qwZv6w-8T7DaPXQ&e= >
>>>>
>>>>
>>>>
>>>>
>>>> _______________________________________________
>>>> nvo3-dt-encap mailing list
>>>> [e-mail]
>>>> https://urldefense.proofpoint.com/v2/url?u=https-3A__www.ietf.org_m
>>>> ailman_listinfo_nvo3-2Ddt-2Dencap&d=DwIC-g&c=uilaK90D4TOVoH58JNXRgQ
>>>> &r=IVzcTRLQdpta08L0b_y2zDkqvwJhRKMCAbX-2K-LV98&m=XlrYfnYa1Nis6dhmSf
>>>> SkIjqS9ZivuqDijjUPgQJ7GoI&s=NjKtEtNQSOAN3MsTZWWQP5pNqZvPrnnE8j3oK44
>>>> 91uA&e=
>>>
>