Re: [Rtg-dt-encap-considerations] draft-rtg-dt-encap-01 & TSV in Dallas

Erik Nordmark <nordmark@sonic.net> Tue, 10 March 2015 16:29 UTC

Return-Path: <nordmark@sonic.net>
X-Original-To: rtg-dt-encap-considerations@ietfa.amsl.com
Delivered-To: rtg-dt-encap-considerations@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 802C21A1BE5 for <rtg-dt-encap-considerations@ietfa.amsl.com>; Tue, 10 Mar 2015 09:29:22 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -4.61
X-Spam-Level:
X-Spam-Status: No, score=-4.61 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, GB_I_INVITATION=-2, RCVD_IN_DNSWL_LOW=-0.7, T_RP_MATCHES_RCVD=-0.01] autolearn=ham
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 aGUdGK_7wcZ1 for <rtg-dt-encap-considerations@ietfa.amsl.com>; Tue, 10 Mar 2015 09:29:15 -0700 (PDT)
Received: from d.mail.sonic.net (d.mail.sonic.net [64.142.111.50]) (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 85DB01A1E0F for <Rtg-dt-encap-considerations@ietf.org>; Tue, 10 Mar 2015 09:29:15 -0700 (PDT)
Received: from [172.22.227.238] ([162.210.130.3]) (authenticated bits=0) by d.mail.sonic.net (8.15.1/8.15.1) with ESMTPSA id t2AGT2oJ012754 (version=TLSv1.2 cipher=DHE-RSA-AES256-SHA bits=256 verify=NOT); Tue, 10 Mar 2015 09:29:03 -0700
Message-ID: <54FF1BCE.8090807@sonic.net>
Date: Tue, 10 Mar 2015 09:29:02 -0700
From: Erik Nordmark <nordmark@sonic.net>
User-Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.10; rv:31.0) Gecko/20100101 Thunderbird/31.5.0
MIME-Version: 1.0
To: "Black, David" <david.black@emc.com>, Alia Atlas <akatlas@gmail.com>
References: <CE03DB3D7B45C245BCA0D243277949363DA59A@MX104CL02.corp.emc.com>
In-Reply-To: <CE03DB3D7B45C245BCA0D243277949363DA59A@MX104CL02.corp.emc.com>
Content-Type: text/plain; charset="utf-8"; format="flowed"
Content-Transfer-Encoding: 8bit
X-Sonic-CAuth: UmFuZG9tSVaHushG2BUC0gKWVwq30z4uxNulD72hWopEsEdSMkNxrfE7FZl3GRsw231nzjNL13lORyHw8h09/O7uWuP30zvU
X-Sonic-ID: C;VgQ5kELH5BGYgb5YxQPdhw== M;AllHkELH5BGYgb5YxQPdhw==
X-Sonic-Spam-Details: 0.0/5.0 by cerberusd
Archived-At: <http://mailarchive.ietf.org/arch/msg/rtg-dt-encap-considerations/9gJBwMPkCbG4WfKXt6qKF8HHzP0>
Cc: "gorry@erg.abdn.ac.uk" <gorry@erg.abdn.ac.uk>, "tsv-ads@tools.ietf.org" <tsv-ads@tools.ietf.org>, "rtg-dt-encap-considerations@ietf.org" <Rtg-dt-encap-considerations@ietf.org>
Subject: Re: [Rtg-dt-encap-considerations] draft-rtg-dt-encap-01 & TSV in Dallas
X-BeenThere: rtg-dt-encap-considerations@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: Routing Area Design Team on Encapsulation Considerations discussion list <rtg-dt-encap-considerations.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/rtg-dt-encap-considerations>, <mailto:rtg-dt-encap-considerations-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/rtg-dt-encap-considerations/>
List-Post: <mailto:rtg-dt-encap-considerations@ietf.org>
List-Help: <mailto:rtg-dt-encap-considerations-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/rtg-dt-encap-considerations>, <mailto:rtg-dt-encap-considerations-request@ietf.org?subject=subscribe>
X-List-Received-Date: Tue, 10 Mar 2015 16:29:22 -0000

On 3/9/15 11:05 PM, Black, David wrote:
> Erik,
>
>> On 3/9/15 6:00 PM, Black, David wrote:
>>>> Please take a read through.  It will be discussed in rtgwg.
>>> Bother - as a tsvwg chair, I won’t be in rtgwg :-(.
>>>
>> The design team might accept invitations to speak about it elsewhere ;-)
>>
>> In fact we are doing a short version at the NVO3 interim this Friday.
>>
>>      Erik
> I'll be on the phone for NVO3 on Friday.  I've cc:'d my tsvwg co-chair
> (Gorry) and the TSV ADs to consider which TSV invitation we should extend,
> as at least the following 5 sections of the draft are relevant to TSV:
>
>     7.  Entropy  . . . . . . . . . . . . . . . . . . . . . . . . . . .  7
>
>     9.  MTU and Fragmentation  . . . . . . . . . . . . . . . . . . . . 10
>
>     12. QoS  . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 15
>     13. Congestion Considerations  . . . . . . . . . . . . . . . . . . 16
>     14. Header Protection  . . . . . . . . . . . . . . . . . . . . . . 18
>
> UDP usage concerns are lurking behind both the Entropy and Header Protection
> topics (e.g., 5-tuple hash behavior, UDP zero checksum for IPv6, respectively).
>
> My initial inclination is to invite a short TSV-oriented discussion into the
> Tuesday afternoon TSVWG session, and arrange for the GRE-in-UDP draft to be
> taken up in that same session.  The only RTG WG in that time slot is IDR,
> which should not pose a content conflict concern.  If Alia wants to observe
> in person (as she's the AD for IDR), we can bash both WG agendas so she can
> be in the right room at the right time for the important topics.

I don't have any conflicts in that slot. FWIW it has
INT 6lo
OPS anima
OPS dnsop
RAI ecrit
RTG idr
SEC dots
TSV tsvwg


	
	
	

	
	
	
	

	
	
	
	

	
	
	
	

	
	
	
	

	
	
	


> That said, I'll give my honorable TSV ADs first shot at whether they'd like
> to pull this encap discussion into TSVAREA, probably the Monday session so
> that the TSV discussion comes before the RTG discussion.

The Monday TSVAREA conflicts with NVO3, which is an issue for myself 
and, I suspect, many of the other design team members.

   Erik
>
> Thoughts?
>
> Thanks,
> --David
>
>>> *From:*routing-discussion [mailto:routing-discussion-bounces@ietf.org]
>>> *On Behalf Of *Alia Atlas
>>> *Sent:* Monday, March 09, 2015 8:43 PM
>>> *To:* routing-discussion@ietf.org; rtgwg@ietf.org
>>> *Subject:* Fwd: [nvo3] Fwd: New Version Notification for
>>> draft-rtg-dt-encap-01.txt
>>>
>>> This is the internet-draft produced by the Data-Plane encapsulation
>>> design team
>>>
>>> that started at the last IETF.
>>>
>>> Please take a read through.  It will be discussed in rtgwg.
>>>
>>> Thanks,
>>>
>>> Alia
>>>
>>>
>>>
>>> -------- Forwarded Message --------
>>> Subject:        New Version Notification for draft-rtg-dt-encap-01.txt
>>> Date:   Mon, 09 Mar 2015 15:51:45 -0700
>>> From: internet-drafts@ietf.org <mailto:internet-drafts@ietf.org>
>>> To:     Jon Hudson <jon.hudson@gmail.com
>>> <mailto:jon.hudson@gmail.com>>, Tom Herbert <therbert@google.com
>>> <mailto:therbert@google.com>>, Lawrence Kreeger <kreeger@cisco.com
>>> <mailto:kreeger@cisco.com>>, Patricia Thaler <pthaler@broadcom.com
>>> <mailto:pthaler@broadcom.com>>, Patricia Thaler <pthaler@broadcom.com
>>> <mailto:pthaler@broadcom.com>>, Jon Hudson <jon.hudson@gmail.com
>>> <mailto:jon.hudson@gmail.com>>, Albert Tian <albert.tian@ericsson.com
>>> <mailto:albert.tian@ericsson.com>>, Jesse Gross <jgross@vmware.com
>>> <mailto:jgross@vmware.com>>, Albert Tian <albert.tian@ericsson.com
>>> <mailto:albert.tian@ericsson.com>>, Pankaj Garg <pankajg@microsoft.com
>>> <mailto:pankajg@microsoft.com>>, Pankaj Garg <pankajg@microsoft.com
>>> <mailto:pankajg@microsoft.com>>, Tom Herbert <therbert@google.com
>>> <mailto:therbert@google.com>>, Jesse Gross <jgross@vmware.com
>>> <mailto:jgross@vmware.com>>, Erik Nordmark <nordmark@arista.com
>>> <mailto:nordmark@arista.com>>, Lawrence Kreeger <kreeger@cisco.com
>>> <mailto:kreeger@cisco.com>>, Erik Nordmark <nordmark@arista.com
>>> <mailto:nordmark@arista.com>>
>>>
>>>
>>>
>>> A new version of I-D, draft-rtg-dt-encap-01.txt
>>> has been successfully submitted by Erik Nordmark and posted to the
>>> IETF repository.
>>>
>>> Name:           draft-rtg-dt-encap
>>> Revision:       01
>>> Title:          Encapsulation Considerations
>>> Document date:  2015-03-09
>>> Group:          Individual Submission
>>> Pages:          37
>>> URL: http://www.ietf.org/internet-drafts/draft-rtg-dt-encap-01.txt
>>> Status: https://datatracker.ietf.org/doc/draft-rtg-dt-encap/
>>> Htmlized: http://tools.ietf.org/html/draft-rtg-dt-encap-01
>>> Diff: http://www.ietf.org/rfcdiff?url2=draft-rtg-dt-encap-01
>>>
>>> Abstract:
>>>     The IETF Routing Area director has chartered a design team to look at
>>>     common issues for the different data plane encapsulations being
>>>     discussed in the NVO3 and SFC working groups and also in the BIER
>>>     BoF, and also to look at the relationship between such encapsulations
>>>     in the case that they might be used at the same time.  The purpose of
>>>     this design team is to discover, discuss and document considerations
>>>     across the different encapsulations in the different WGs/BoFs so that
>>>     we can reduce the number of wheels that need to be reinvented in the
>>>     future.
>>>
>>>
>>>
>>> Please note that it may take a couple of minutes from the time of
>>> submission
>>> until the htmlized version and diff are available at tools.ietf.org
>>> <http://tools.ietf.org>.
>>>
>>> The IETF Secretariat
>>>
>>>
>>>
>>> _______________________________________________
>>> nvo3 mailing list
>>> nvo3@ietf.org <mailto:nvo3@ietf.org>
>>> https://www.ietf.org/mailman/listinfo/nvo3
>>>