Re: [trill] [sfc] Fwd: Mail regarding draft-ietf-trill-over-ip

"Templin, Fred L" <Fred.L.Templin@boeing.com> Wed, 06 May 2015 14:37 UTC

Return-Path: <Fred.L.Templin@boeing.com>
X-Original-To: trill@ietfa.amsl.com
Delivered-To: trill@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id F3EDA1ACD83; Wed, 6 May 2015 07:37:41 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -4.211
X-Spam-Level:
X-Spam-Status: No, score=-4.211 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RCVD_IN_DNSWL_MED=-2.3, SPF_PASS=-0.001, 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 RqxdT31YEtNL; Wed, 6 May 2015 07:37:40 -0700 (PDT)
Received: from blv-mbsout-01.boeing.com (blv-mbsout-01.boeing.com [130.76.32.231]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id DF2C21ACDB6; Wed, 6 May 2015 07:37:09 -0700 (PDT)
Received: from localhost (localhost [127.0.0.1]) by blv-mbsout-01.boeing.com (8.14.4/8.14.4/DOWNSTREAM_MBSOUT) with SMTP id t46Eb997021224; Wed, 6 May 2015 07:37:09 -0700
Received: from XCH-PHX-109.sw.nos.boeing.com (xch-phx-109.sw.nos.boeing.com [130.247.25.36]) by blv-mbsout-01.boeing.com (8.14.4/8.14.4/UPSTREAM_MBSOUT) with ESMTP id t46Eb1RP021136 (version=TLSv1/SSLv3 cipher=AES128-SHA bits=128 verify=OK); Wed, 6 May 2015 07:37:01 -0700
Received: from XCH-BLV-504.nw.nos.boeing.com ([169.254.4.120]) by XCH-PHX-109.sw.nos.boeing.com ([169.254.9.131]) with mapi id 14.03.0235.001; Wed, 6 May 2015 07:37:00 -0700
From: "Templin, Fred L" <Fred.L.Templin@boeing.com>
To: Joe Touch <touch@isi.edu>, Dave Dolson <ddolson@sandvine.com>, Xuxiaohu <xuxiaohu@huawei.com>, Donald Eastlake <d3e3e3@gmail.com>, "trill@ietf.org" <trill@ietf.org>
Thread-Topic: [trill] [sfc] Fwd: Mail regarding draft-ietf-trill-over-ip
Thread-Index: AQHQh3nJyhmZ+Lyhk0iSDo4t2tXKb51uY68A//+LwaCAAHsHAP//jdwwgACU9ACAAHdOQA==
Date: Wed, 6 May 2015 14:37:00 +0000
Message-ID: <2134F8430051B64F815C691A62D9831832E5B85B@XCH-BLV-504.nw.nos.boeing.com>
References: <4552F0907735844E9204A62BBDD325E76ABADC85@nkgeml512-mbx.china.huawei.com> <CAF4+nEHSGYa+1DHzwee+RNgkXfZra_Pa9706vqpTGJV71SmDaw@mail.gmail.com> <CAF4+nEFcUL2ieQKCm98_0XxfrrAR0M11irVFfOfqa=92OM1V=A@mail.gmail.com> <5543D870.6080108@isi.edu> <1FEE3F8F5CCDE64C9A8E8F4AD27C19EE0832A468@NKGEML512-MBS.china.huawei.com> <55479A6D.2040403@isi.edu> <1FEE3F8F5CCDE64C9A8E8F4AD27C19EE0832A7B7@NKGEML512-MBS.china.huawei.com> <5548F0B3.80602@isi.edu> <E8355113905631478EFF04F5AA706E9830BEFC3C@wtl-exchp-2.sandvine.com> <554904B8.9020504@isi.edu> <E8355113905631478EFF04F5AA706E9830BF0165@wtl-exchp-2.sandvine.com> <554931E2.5010101@isi.edu> <2134F8430051B64F815C691A62D9831832E5AF3A@XCH-BLV-504.nw.nos.boeing.com> <55493D10.90609@isi.edu> <2134F8430051B64F815C691A62D9831832E5AFC1@XCH-BLV-504.nw.nos.boeing.com> <554942C0.4000601@isi.edu> <2134F8430051B64F815C691A62D9831832E5B040@XCH-BLV-504.nw.nos.boeing.com> <55495FF4.7000100@isi.edu>
In-Reply-To: <55495FF4.7000100@isi.edu>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach:
X-MS-TNEF-Correlator:
x-originating-ip: [130.247.104.6]
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: quoted-printable
MIME-Version: 1.0
X-TM-AS-MML: disable
Archived-At: <http://mailarchive.ietf.org/arch/msg/trill/bjvvCu6h6-fTWKPwYd6qK8lnN7w>
Cc: "nvo3@ietf.org" <nvo3@ietf.org>, "int-area@ietf.org" <int-area@ietf.org>, "sfc@ietf.org" <sfc@ietf.org>
Subject: Re: [trill] [sfc] Fwd: Mail regarding draft-ietf-trill-over-ip
X-BeenThere: trill@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: "Developing a hybrid router/bridge." <trill.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/trill>, <mailto:trill-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/trill/>
List-Post: <mailto:trill@ietf.org>
List-Help: <mailto:trill-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/trill>, <mailto:trill-request@ietf.org?subject=subscribe>
X-List-Received-Date: Wed, 06 May 2015 14:37:42 -0000

Hi Joe,

> -----Original Message-----
> From: Joe Touch [mailto:touch@isi.edu]
> Sent: Tuesday, May 05, 2015 5:28 PM
> To: Templin, Fred L; Dave Dolson; Xuxiaohu; Donald Eastlake; trill@ietf.org
> Cc: nvo3@ietf.org; int-area@ietf.org; sfc@ietf.org
> Subject: Re: [trill] [sfc] Fwd: Mail regarding draft-ietf-trill-over-ip
> 
> 
> 
> On 5/5/2015 3:43 PM, Templin, Fred L wrote:
> >> Then what you're saying is that the tunnel ingress - as an app - has
> >> > flows that are distinguishable by the net. That can happen with any
> >> > application.
> >
> > But, that's just it - when the original source does the probing the data
> > packets are always part of the same application - always. When the
> > tunnel ingress probes, it may be asked to encapsulate the data
> > pacekts of many applications.
> 
> An "application" is a source of packets.
> 
> At a tunnel, the ingress arriving packets are that source - they ARE the
> "application".
> 
> To correlate flow IDs to behavior within that flow - i.e., to the user
> programs that generate the packets that arrive at the ingress - requires
> the ingress to somehow infer those flows, unless they're explicitly
> marked by the user applications.
> 
> That's a known limitation of any tunnel ingress. It's equally true of
> the user application if there are four people using one application, and
> you want 'flow' to map back to an individual person.

We are still not reaching. The concern is that if some tunneled packets
take a different network path than others then there is a chance that
the probes will take a different path than the data. The only way I know
to prevent that is to always set the Flow Label in the encapsulation
header to some fixed value (e.g., 0).

Thanks - Fred
fred.l.templin@boeing.com

> Joe