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

"Ganga, Ilango S" <ilango.s.ganga@intel.com> Tue, 07 February 2017 16:24 UTC

Return-Path: <ilango.s.ganga@intel.com>
X-Original-To: nvo3-dt-encap@ietfa.amsl.com
Delivered-To: nvo3-dt-encap@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 74546129D33 for <nvo3-dt-encap@ietfa.amsl.com>; Tue, 7 Feb 2017 08:24:23 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -6.921
X-Spam-Level:
X-Spam-Status: No, score=-6.921 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RCVD_IN_DNSWL_HI=-5, RCVD_IN_MSPIKE_H3=-0.01, RCVD_IN_MSPIKE_WL=-0.01, RP_MATCHES_RCVD=-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 ae0LiEMHxqd6 for <nvo3-dt-encap@ietfa.amsl.com>; Tue, 7 Feb 2017 08:24:21 -0800 (PST)
Received: from mga09.intel.com (mga09.intel.com [134.134.136.24]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 0D814129D36 for <nvo3-dt-encap@ietf.org>; Tue, 7 Feb 2017 08:24:21 -0800 (PST)
Received: from fmsmga003.fm.intel.com ([10.253.24.29]) by orsmga102.jf.intel.com with ESMTP; 07 Feb 2017 08:24:20 -0800
X-ExtLoop1: 1
X-IronPort-AV: E=Sophos;i="5.33,346,1477983600"; d="scan'208";a="818108722"
Received: from orsmsx105.amr.corp.intel.com ([10.22.225.132]) by FMSMGA003.fm.intel.com with ESMTP; 07 Feb 2017 08:24:20 -0800
Received: from orsmsx156.amr.corp.intel.com (10.22.240.22) by ORSMSX105.amr.corp.intel.com (10.22.225.132) with Microsoft SMTP Server (TLS) id 14.3.248.2; Tue, 7 Feb 2017 08:24:20 -0800
Received: from orsmsx116.amr.corp.intel.com ([169.254.7.164]) by ORSMSX156.amr.corp.intel.com ([169.254.8.38]) with mapi id 14.03.0248.002; Tue, 7 Feb 2017 08:24:19 -0800
From: "Ganga, Ilango S" <ilango.s.ganga@intel.com>
To: Sami Boutros <sboutros@vmware.com>
Thread-Topic: [nvo3-dt-encap] NVO3 Encap Design Team Weekly Sync
Thread-Index: AQHSe2FEH0y8c1ShlEKJrtgtK3hg96FZJfEAgAO8iACAAAgAAIAADHOAgACRGACAACJDQIAAoTqA//96JHA=
Date: Tue, 7 Feb 2017 16:24:19 +0000
Message-ID: <C5A274B25007804B800CB5B289727E3556E06D49@ORSMSX116.amr.corp.intel.com>
References: <AB73A037-FF71-4FFE-94EE-93E739CA42C6@vmware.com> <A749B0B2-02A5-4ABF-A8A6-7A926778D193@vmware.com> <4bee19dc-1011-a83e-f727-2ea03d5d260d@sonic.net> <38D0FC4C-9882-47C3-BF76-55536F271E34@vmware.com> <cf3873f6-0cf1-794d-e2cd-e3e82dcf8b8b@sonic.net> <01F4A150-3709-4B18-86D2-70DF8F6921D6@vmware.com> <C5A274B25007804B800CB5B289727E3556E06BC9@ORSMSX116.amr.corp.intel.com> <58AD1150-1B97-4624-B6E9-BE3136280632@vmware.com>
In-Reply-To: <58AD1150-1B97-4624-B6E9-BE3136280632@vmware.com>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach:
X-MS-TNEF-Correlator:
x-titus-metadata-40: eyJDYXRlZ29yeUxhYmVscyI6IiIsIk1ldGFkYXRhIjp7Im5zIjoiaHR0cDpcL1wvd3d3LnRpdHVzLmNvbVwvbnNcL0ludGVsMyIsImlkIjoiMDQwYjc1MjQtZDg4Yi00YjIzLWJjMWEtZGU1OWE5NDkxOTA2IiwicHJvcHMiOlt7Im4iOiJDVFBDbGFzc2lmaWNhdGlvbiIsInZhbHMiOlt7InZhbHVlIjoiQ1RQX0lDIn1dfV19LCJTdWJqZWN0TGFiZWxzIjpbXSwiVE1DVmVyc2lvbiI6IjE1LjkuNi42IiwiVHJ1c3RlZExhYmVsSGFzaCI6IjhheFBuYmRLaFUwXC9MdVwvOXlEbVRaZXVnd2I0YVdSdHJKelFNcHhUNCs1az0ifQ==
x-ctpclassification: CTP_IC
x-originating-ip: [10.22.254.140]
Content-Type: text/plain; charset="utf-8"
Content-Transfer-Encoding: base64
MIME-Version: 1.0
Archived-At: <https://mailarchive.ietf.org/arch/msg/nvo3-dt-encap/vuFyVr9-mX1OgdngeNjVjftgDwQ>
Cc: "nvo3-dt-encap@ietf.org" <nvo3-dt-encap@ietf.org>
Subject: Re: [nvo3-dt-encap] NVO3 Encap Design Team Weekly Sync
X-BeenThere: nvo3-dt-encap@ietf.org
X-Mailman-Version: 2.1.17
Precedence: list
List-Id: Private mailing list for internal NVO3 Encapsulation Design Team discussions <nvo3-dt-encap.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/nvo3-dt-encap>, <mailto:nvo3-dt-encap-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/nvo3-dt-encap/>
List-Post: <mailto:nvo3-dt-encap@ietf.org>
List-Help: <mailto:nvo3-dt-encap-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/nvo3-dt-encap>, <mailto:nvo3-dt-encap-request@ietf.org?subject=subscribe>
X-List-Received-Date: Tue, 07 Feb 2017 16:24:23 -0000

Hi Sami,

If it is a "max single option length" that is stated as 256 bytes, then this is the point we discussed last week and as per my understanding there is no consensus to make this to 256 bytes.

Thanks,
Ilango


-----Original Message-----
From: Sami Boutros [mailto:sboutros@vmware.com] 
Sent: Tuesday, February 7, 2017 8:20 AM
To: Ganga, Ilango S <ilango.s.ganga@intel.com>
Cc: nvo3-dt-encap@ietf.org
Subject: Re: [nvo3-dt-encap] NVO3 Encap Design Team Weekly Sync

Hi Ilango,




On 2/7/17, 6:59 AM, "Ganga, Ilango S" <ilango.s.ganga@intel.com> wrote:

>Hi Sami,
>
>Regarding Section 6.4 Extension size. Currently 6.4 states first paragraph states, The Extension header length, min recommended size is 64B and later in the second paragraph it states, The recommended max option length value is 256 bytes. Does both the statements refer to the total extension header length?

No, the later statement refer to the max single option length, I changed the text from "max option length” -> “max single option length”

Thanks,

Sami 
> I remember we had a discussion last week about the max individual option size and we did not arrive at a consensus on the max size. Please clarify.
>
>Thanks,
>Ilango
>
>
>-----Original Message-----
>From: nvo3-dt-encap [mailto:nvo3-dt-encap-bounces@ietf.org] On Behalf 
>Of Sami Boutros
>Sent: Monday, February 6, 2017 8:41 PM
>To: Erik Nordmark <nordmark@sonic.net>et>; Michael Smith (michsmit) 
><michsmit@cisco.com>
>Cc: nvo3-dt-encap@ietf.org
>Subject: Re: [nvo3-dt-encap] NVO3 Encap Design Team Weekly Sync
>
>Draft updated.
>
>Thanks,
>
>Sami
>
>
>On 2/6/17, 12:01 PM, "Erik Nordmark" <nordmark@sonic.net> wrote:
>
>>On 2/6/17 11:16 AM, Sami Boutros 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.
>>I got this one, and the earlier one, but not your original one.
>>>
>>> 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.
>>
>>I think it is fine to have "extension" about the general concept, and 
>>"option" as the implementation of that concept in Geneve.
>>However, looking at the the current use of those words I'd suggest OLD
>>6.1 Current Encapsulations Options
>>NEW
>>6.1 Current Encapsulations
>>
>>I think some other text can have option changed to extension, but I'd 
>>leave the draft the way it is for now.
>>
>>
>>>
>>> On 2/6/17, 10:48 AM, "Erik Nordmark" <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.
>>
>>Then I think it makes sense to add a sentence to the end of item 6 
>>saying "Thus the C-bit remains as defined in Geneve."
>>>
>>>> 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.
>>Looks OK.
>>>
>>>> 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,
>>     Erik
>>
>>>
>>>
>>> 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>> on behalf of Sami Boutros 
>>>>> <sboutros@vmware.com <mailto:sboutros@vmware.com>>
>>>>> Date: Monday, January 30, 2017 at 5:28 PM
>>>>> To: "pankajg@microsoft.com <mailto:pankajg@microsoft.com>"
>>>>> <pankajg@microsoft.com <mailto:pankajg@microsoft.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
>>>>>
>>>>> 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>
>>>>> 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__meeteet.
>>>>> l 
>>>>> ync.com_microsoft_pankajg_GV7DS8RK&d=DgMFAw&c=uilaK90D4TOVoH58JNXR
>>>>> g 
>>>>> Q&r=IVzcTRLQdpta08L0b_y2zDkqvwJhRKMCAbX-2K-LV98&m=3Pr77Dew_fMgHmY0
>>>>> H 
>>>>> pgY2dkZrDHuUOszSOrBjA8FbNY&s=UmXWKhsr5ftLGNUPrRC5rAXvE6Lt2T-cs3ad-
>>>>> i
>>>>> Q_HEQ&e=>
>>>>>
>>>>> Trouble Joining? _Try Skype Web App 
>>>>> <https://urldefense.proofpoint.com/v2/url?u=https-3A__meet.lync.co
>>>>> m 
>>>>> _microsoft_pankajg_GV7DS8RK-3Fsl-3D1&d=DgMFAw&c=uilaK90D4TOVoH58JN
>>>>> X 
>>>>> RgQ&r=IVzcTRLQdpta08L0b_y2zDkqvwJhRKMCAbX-2K-LV98&m=3Pr77Dew_fMgHm
>>>>> Y 
>>>>> 0HpgY2dkZrDHuUOszSOrBjA8FbNY&s=2YOfmxoNQri7YQrWRUL-lrl44Xruly4NFUI
>>>>> a
>>>>> PGXdyeg&e=>
>>>>> _
>>>>>
>>>>> Join by phone
>>>>>
>>>>> +1 (425) 706-3470 <tel:+1%20%28425%29%20706-3470,28245940%23>
>>>>> (Redmond) English (United States)
>>>>>
>>>>> +1 (425) 707-0048 <tel:+1%20%28425%29%20707-0048,28245940%23>
>>>>> (Redmond) English (United States)
>>>>>
>>>>> +1 (425) 538-0005 <tel:+1%20%28425%29%20538-0005,28245940%23>
>>>>> (Redmond) English (United States)
>>>>>
>>>>> +1 (425) 538-0006 <tel:+1%20%28425%29%20538-0006,28245940%23>
>>>>> (Redmond) English (United States)
>>>>>
>>>>> +1 (866) 256-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.
>>>>> c 
>>>>> om_microsoft.com-3Fid-3D28245940&d=DgMFAw&c=uilaK90D4TOVoH58JNXRgQ
>>>>> & 
>>>>> r=IVzcTRLQdpta08L0b_y2zDkqvwJhRKMCAbX-2K-LV98&m=3Pr77Dew_fMgHmY0Hp
>>>>> g
>>>>> Y2dkZrDHuUOszSOrBjA8FbNY&s=e-WpXQTneFetp3czkAmWKYxQYE0_MVBGSeeSWys
>>>>> 8
>>>>> S1I&e=>_
>>>>>
>>>>> Conference ID: 28245940
>>>>>
>>>>> Forgot your dial-in PIN?
>>>>> <https://urldefense.proofpoint.com/v2/url?u=https-3A__dialin.lync.
>>>>> c
>>>>> om_microsoft.com&d=DgMFAw&c=uilaK90D4TOVoH58JNXRgQ&r=IVzcTRLQdpta0
>>>>> 8 
>>>>> L0b_y2zDkqvwJhRKMCAbX-2K-LV98&m=3Pr77Dew_fMgHmY0HpgY2dkZrDHuUOszSO
>>>>> r BjA8FbNY&s=PRReskp_6UTaQDZvlmyunr41Cjv3MQb0iOE8QI00En4&e=>|Help
>>>>> <https://urldefense.proofpoint.com/v2/url?u=http-3A__go.microsoft.
>>>>> c 
>>>>> om_fwlink_-3FLinkId-3D389737&d=DgMFAw&c=uilaK90D4TOVoH58JNXRgQ&r=I
>>>>> V 
>>>>> zcTRLQdpta08L0b_y2zDkqvwJhRKMCAbX-2K-LV98&m=3Pr77Dew_fMgHmY0HpgY2d
>>>>> k 
>>>>> ZrDHuUOszSOrBjA8FbNY&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
>>>>> https://urldefense.proofpoint.com/v2/url?u=https-3A__www.ietf.org_
>>>>> m 
>>>>> ailman_listinfo_nvo3-2Ddt-2Dencap&d=DwID-g&c=uilaK90D4TOVoH58JNXRg
>>>>> Q 
>>>>> &r=IVzcTRLQdpta08L0b_y2zDkqvwJhRKMCAbX-2K-LV98&m=POJQPmhf4KRfbnXI4
>>>>> r 
>>>>> Rk6kNiAMpKuPuD6jIE2qGWkF0&s=KBn4fq-_zk9mq-lnDFrg5uLnoErEkPgr3_1-Cr
>>>>> o
>>>>> DKkM&e=
>>>>
>>