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

Hi Rajeev,

I think we should wait to get consensus from the group on your 2 comments below before including them.

I will submit what I have, and we can address those in the next rev.

Thanks,

Sami
From: Rajeev Manur <rajeev.manur@broadcom.com<mailto:rajeev.manur@broadcom.com>>
Date: Tuesday, February 7, 2017 at 10:13 AM
To: Sami Boutros <sboutros@vmware.com<mailto:sboutros@vmware.com>>
Cc: Erik Nordmark <nordmark@sonic.net<mailto:nordmark@sonic.net>>, "Michael Smith (michsmit)" <michsmit@cisco.com<mailto:michsmit@cisco.com>>, "nvo3-dt-encap@ietf.org<mailto:nvo3-dt-encap@ietf.org>" <nvo3-dt-encap@ietf.org<mailto:nvo3-dt-encap@ietf.org>>
Subject: Re: [nvo3-dt-encap] NVO3 Encap Design Team Weekly Sync

Hi,

i would want to suggest we bring down the minimum option length the middle boxes should support to "up to 32B". Vendors always have the option to support anything above this if they choose to. Also, any comments on the earlier point I brought up?

Thanks!
--Rajeev

On Mon, Feb 6, 2017 at 11:27 AM, Rajeev Manur <rajeev.manur@broadcom.com<mailto:rajeev.manur@broadcom.com>> wrote:
Hi Team,

In the current GENEVE proposal, when parsing multiple options hdrs, we have to keep track of the total OpeLen field in the base hdr to know which is the last options hdr. It would be much easier if we could just add a 1 bit flag to the options hdr to indicate it is the last option hdr. If you guys see value in this, we could add this to the recommendations.

Has it been already submitted to the WG list? If not could we could we hold off till EOB today?

Thanks!
--Rajeev

On Mon, Feb 6, 2017 at 11:16 AM, Sami Boutros <sboutros@vmware.com<mailto:sboutros@vmware.com>> wrote:
Hi Erik,

There was some issues with sending the draft to the list, please let me know if you don’t get the attachment.

One more comment to add, to be consistent should we change extension to option in the draft to be consistent with the language in Geneve? If we are ok with that, I can do this change in the next rev before submitting.

On 2/6/17, 10:48 AM, "Erik Nordmark" <nordmark@sonic.net<mailto:nordmark@sonic.net>> wrote:

>
>Sam,
>
>I have some minor issues; have others read the document and is it ready
>to submit as an I-D?
>Once we submit it as a I-D we can follow-up with a message to the NVO3
>list asking whether there are things folks want to see clarified so we
>can add any clarifications before Chicago.
>
>
>The things I saw are:
>1. I don't seem to be listed as an author at the end

Sorry, about that, I added your name in the attached draft.

>
>2. The section on Group Base Policy has '[reference]'.  Michael, do you
>have a reference we can add?
>
>3. It isn't clear whether we are recommending some change with respect
>to the 'C' bit. Section 7 item 6 says it is useful. Do we mean its
>definition is unchanged?

This is my assumption.

>
>4. Item 7 in section 7 can be generalized by saying that there are
>already some extensions that are being discussed (see section 6.2) of
>varying sizes. (Is that the main point? We can enumerate them as
>"extensions for Telemetry, Security/Integrity, and Group Based Policy"
>if that makes it more clear.

I updated this item a bit in the attached draft, please have a look.

>
>5. Last sentence in section 7 might have a typo. It says "The control
>planes defined today need to add the ability to describe the different
>encapsulations." but the text above talks about the different
>TLVs/options, and we've talked about having the control plane describe
>the supported TLVs and their order. Thus should the text say "The
>control planes defined today need to add the ability to describe the
>supported TLVs and their order."?

Done.

Thanks,

Sami
>
>If we fix the above I think the draft is good enough to submit.
>
>Thanks,
>    Erik
>
>
>On 2/4/17 5:44 PM, Sami Boutros wrote:
>> I am resending the draft I sent on Thursday,
>>
>> Hopefully, it will get through this time.
>>
>> Thanks,
>>
>> Sami
>> From: nvo3-dt-encap <nvo3-dt-encap-bounces@ietf.org<mailto:nvo3-dt-encap-bounces@ietf.org>
>> <mailto:nvo3-dt-encap-bounces@ietf.org<mailto:nvo3-dt-encap-bounces@ietf.org>>> on behalf of Sami Boutros
>> <sboutros@vmware.com<mailto:sboutros@vmware.com> <mailto:sboutros@vmware.com<mailto:sboutros@vmware.com>>>
>> Date: Monday, January 30, 2017 at 5:28 PM
>> To: "pankajg@microsoft.com<mailto:pankajg@microsoft.com> <mailto:pankajg@microsoft.com<mailto:pankajg@microsoft.com>>"
>> <pankajg@microsoft.com<mailto:pankajg@microsoft.com> <mailto:pankajg@microsoft.com<mailto:pankajg@microsoft.com>>>,
>> "nvo3-dt-encap@ietf.org<mailto:nvo3-dt-encap@ietf.org> <mailto:nvo3-dt-encap@ietf.org<mailto:nvo3-dt-encap@ietf.org>>"
>> <nvo3-dt-encap@ietf.org<mailto:nvo3-dt-encap@ietf.org> <mailto:nvo3-dt-encap@ietf.org<mailto:nvo3-dt-encap@ietf.org>>>
>> Subject: Re: [nvo3-dt-encap] NVO3 Encap Design Team Weekly Sync
>>
>> Hey Folks,
>>
>> I don’t see much updates going to the doc?
>>
>> Are we still meeting tomorrow?
>>
>> The only comment was from David a suggestion to increase the MAX size
>> of a single TLV to be 256 bytes.
>>
>> Thanks,
>>
>> Sami
>> From: pankajg@microsoft.com<mailto:pankajg@microsoft.com> <mailto:pankajg@microsoft.com<mailto:pankajg@microsoft.com>>
>> When: 8:00 AM - 10:00 AM January 31, 2017
>> Subject: [nvo3-dt-encap] 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 Skype
>> Meeting<https://urldefense.proofpoint.com/v2/url?u=https-3A__meet.lync.com_microsoft_pankajg_GV7DS8RK&d=DgMFAw&c=uilaK90D4TOVoH58JNXRgQ&r=IVzcTRLQdpta08L0b_y2zDkqvwJhRKMCAbX-2K-LV98&m=3Pr77Dew_fMgHmY0HpgY2dkZrDHuUOszSOrBjA8FbNY&s=UmXWKhsr5ftLGNUPrRC5rAXvE6Lt2T-cs3ad-iQ_HEQ&e=>
>>
>> Trouble Joining? _Try Skype Web App
>> <https://urldefense.proofpoint.com/v2/url?u=https-3A__meet.lync.com_microsoft_pankajg_GV7DS8RK-3Fsl-3D1&d=DgMFAw&c=uilaK90D4TOVoH58JNXRgQ&r=IVzcTRLQdpta08L0b_y2zDkqvwJhRKMCAbX-2K-LV98&m=3Pr77Dew_fMgHmY0HpgY2dkZrDHuUOszSOrBjA8FbNY&s=2YOfmxoNQri7YQrWRUL-lrl44Xruly4NFUIaPGXdyeg&e=>
>> _
>>
>> Join by phone
>>
>> +1 (425) 706-3470<tel:%2B1%20%28425%29%20706-3470> <tel:+1%20%28425%29%20706-3470,28245940%23>
>> (Redmond) English (United States)
>>
>> +1 (425) 707-0048<tel:%2B1%20%28425%29%20707-0048> <tel:+1%20%28425%29%20707-0048,28245940%23>
>> (Redmond) English (United States)
>>
>> +1 (425) 538-0005<tel:(425)%20538-0005> <tel:+1%20%28425%29%20538-0005,28245940%23>
>> (Redmond) English (United States)
>>
>> +1 (425) 538-0006<tel:(425)%20538-0006> <tel:+1%20%28425%29%20538-0006,28245940%23>
>> (Redmond) English (United States)
>>
>> +1 (866) 256-4036<tel:(866)%20256-4036> <tel:+1%20%28866%29%20256-4036,28245940%23>
>> (Redmond) English (United Kingdom)
>>
>> _Find a local number
>> <https://urldefense.proofpoint.com/v2/url?u=https-3A__dialin.lync.com_microsoft.com-3Fid-3D28245940&d=DgMFAw&c=uilaK90D4TOVoH58JNXRgQ&r=IVzcTRLQdpta08L0b_y2zDkqvwJhRKMCAbX-2K-LV98&m=3Pr77Dew_fMgHmY0HpgY2dkZrDHuUOszSOrBjA8FbNY&s=e-WpXQTneFetp3czkAmWKYxQYE0_MVBGSeeSWys8S1I&e=>_
>>
>> Conference ID: 28245940
>>
>> Forgot your dial-in PIN?
>> <https://urldefense.proofpoint.com/v2/url?u=https-3A__dialin.lync.com_microsoft.com&d=DgMFAw&c=uilaK90D4TOVoH58JNXRgQ&r=IVzcTRLQdpta08L0b_y2zDkqvwJhRKMCAbX-2K-LV98&m=3Pr77Dew_fMgHmY0HpgY2dkZrDHuUOszSOrBjA8FbNY&s=PRReskp_6UTaQDZvlmyunr41Cjv3MQb0iOE8QI00En4&e=>|Help
>> <https://urldefense.proofpoint.com/v2/url?u=http-3A__go.microsoft.com_fwlink_-3FLinkId-3D389737&d=DgMFAw&c=uilaK90D4TOVoH58JNXRgQ&r=IVzcTRLQdpta08L0b_y2zDkqvwJhRKMCAbX-2K-LV98&m=3Pr77Dew_fMgHmY0HpgY2dkZrDHuUOszSOrBjA8FbNY&s=tVJ-dyXc7Dam55U6WsU98Ji7qx9i6KQqxrJpOSq57jc&e=>
>>
>> Welcome to Skype for Business Online Meetings. Participants using the
>> Join by Phone option must dial the full number for call access.
>>
>> _[!OC([1033])!]
>>
>> .........................................................................................................................................
>>
>>
>>
>> _______________________________________________
>> nvo3-dt-encap mailing list
>> nvo3-dt-encap@ietf.org<mailto:nvo3-dt-encap@ietf.org>
>> https://urldefense.proofpoint.com/v2/url?u=https-3A__www.ietf.org_mailman_listinfo_nvo3-2Ddt-2Dencap&d=DwID-g&c=uilaK90D4TOVoH58JNXRgQ&r=IVzcTRLQdpta08L0b_y2zDkqvwJhRKMCAbX-2K-LV98&m=POJQPmhf4KRfbnXI4rRk6kNiAMpKuPuD6jIE2qGWkF0&s=KBn4fq-_zk9mq-lnDFrg5uLnoErEkPgr3_1-CroDKkM&e=
>
>

_______________________________________________
nvo3-dt-encap mailing list
nvo3-dt-encap@ietf.org<mailto:nvo3-dt-encap@ietf.org>
https://www.ietf.org/mailman/listinfo/nvo3-dt-encap<https://urldefense.proofpoint.com/v2/url?u=https-3A__www.ietf.org_mailman_listinfo_nvo3-2Ddt-2Dencap&d=DwMFaQ&c=uilaK90D4TOVoH58JNXRgQ&r=IVzcTRLQdpta08L0b_y2zDkqvwJhRKMCAbX-2K-LV98&m=otykFBqsOOGDBBIzPQ4w7mlEigrtpCzN82IGRAPEaf8&s=GsHkRijM691HTmc_mpVVPaQkc1mjFRYACnuxnUydk5Y&e=>