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

Spencer Dawkins at IETF <spencerdawkins.ietf@gmail.com> Wed, 11 March 2015 12:59 UTC

Return-Path: <spencerdawkins.ietf@gmail.com>
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 3A7751A8843 for <rtg-dt-encap-considerations@ietfa.amsl.com>; Wed, 11 Mar 2015 05:59:33 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -3.999
X-Spam-Level:
X-Spam-Status: No, score=-3.999 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, FREEMAIL_FROM=0.001, GB_I_INVITATION=-2, HTML_MESSAGE=0.001, SPF_PASS=-0.001] 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 ZsQ342n2phoe for <rtg-dt-encap-considerations@ietfa.amsl.com>; Wed, 11 Mar 2015 05:59:30 -0700 (PDT)
Received: from mail-la0-x22a.google.com (mail-la0-x22a.google.com [IPv6:2a00:1450:4010:c03::22a]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 5A3E11A8799 for <Rtg-dt-encap-considerations@ietf.org>; Wed, 11 Mar 2015 05:59:29 -0700 (PDT)
Received: by lams18 with SMTP id s18so8600271lam.2 for <Rtg-dt-encap-considerations@ietf.org>; Wed, 11 Mar 2015 05:59:27 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:in-reply-to:references:date:message-id:subject:from:to :cc:content-type; bh=ff+rn4n7HeRib12rjLfX/oEIMPZk8Bj2Qp0SNiHzPwY=; b=xs2U+338BgMZLhoSlFouTP9QA1giciPnsv7/DCYL4TtkHdKtkrxYJSFxTIXzvtthRR UxPNW66w2u4opcGfiB+BBFLgr8zLRavnhhCWirp7rQRdWQPZGoNLcUbUCB6gsypiuHjr 5RxHAdJ7OrpM1UDB6b0R+tidecU/A9ED3e1alHyxzmZLnydZVT2/ARImp+NG5gJZs6An ruXJlftZV0tUbkycqF8q0lfcL+0G3njt1eIqKP/sDaoCssPY83UE95elSYpxktHUchNG y1aHuuCWkv1igMNQytaCTBYt/by7TKWVQ8L3AGkecQbrcZWbvFgSjPH3EwE6AY8RRg5i T8Kw==
MIME-Version: 1.0
X-Received: by 10.112.162.232 with SMTP id yd8mr34078199lbb.41.1426078767790; Wed, 11 Mar 2015 05:59:27 -0700 (PDT)
Received: by 10.152.129.193 with HTTP; Wed, 11 Mar 2015 05:59:27 -0700 (PDT)
Received: by 10.152.129.193 with HTTP; Wed, 11 Mar 2015 05:59:27 -0700 (PDT)
In-Reply-To: <54FF1BCE.8090807@sonic.net>
References: <CE03DB3D7B45C245BCA0D243277949363DA59A@MX104CL02.corp.emc.com> <54FF1BCE.8090807@sonic.net>
Date: Wed, 11 Mar 2015 07:59:27 -0500
Message-ID: <CAKKJt-dpj9HrQjW36kkVfFBMhWg+s_HTzUj4ddLXjCVUYwUoeg@mail.gmail.com>
From: Spencer Dawkins at IETF <spencerdawkins.ietf@gmail.com>
To: Erik Nordmark <nordmark@sonic.net>
Content-Type: multipart/alternative; boundary="089e01184bba603f31051102d621"
Archived-At: <http://mailarchive.ietf.org/arch/msg/rtg-dt-encap-considerations/WWY9P3tCWEKoTkXEY2i3UjIiMWM>
X-Mailman-Approved-At: Wed, 11 Mar 2015 08:31:31 -0700
Cc: gorry@erg.abdn.ac.uk, tsv-ads@tools.ietf.org, "Black, David" <david.black@emc.com>, "rtg-dt-encap-considerations@ietf.org" <Rtg-dt-encap-considerations@ietf.org>, Alia Atlas <akatlas@gmail.com>
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: Wed, 11 Mar 2015 12:59:33 -0000

Hi, Erik and David,

I would be fine with David and Gorry bringing this to TSVWG.

I agree that TSVAREA needs to see it if we can work that out, but that can
take a back seat, especially if at least a couple of RTG design team
members can come to TSVWG.

If that happens, David, do you think sending a heads up to the TSVAREA list
would be helpful?

I suppose most folk who would flip out in TSVAREA would be in TSVWG anyway
:-)

Spencer

On Mar 10, 2015 11:29 AM, "Erik Nordmark" <nordmark@sonic.net> wrote:
>
> 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
>>>>
>