
From nobody Mon Dec  1 09:29:16 2014
Return-Path: <Fred.L.Templin@boeing.com>
X-Original-To: routing-discussion@ietfa.amsl.com
Delivered-To: routing-discussion@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 63DEB1A871B for <routing-discussion@ietfa.amsl.com>; Mon,  1 Dec 2014 09:29:13 -0800 (PST)
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 mHBwLjj_zohY for <routing-discussion@ietfa.amsl.com>; Mon,  1 Dec 2014 09:29:11 -0800 (PST)
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 9CFEF1A871F for <routing-discussion@ietf.org>; Mon,  1 Dec 2014 09:29:01 -0800 (PST)
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 sB1HT14C001147; Mon, 1 Dec 2014 09:29:01 -0800
Received: from XCH-BLV-207.nw.nos.boeing.com (xch-blv-207.nw.nos.boeing.com [10.57.37.63]) by blv-mbsout-01.boeing.com (8.14.4/8.14.4/UPSTREAM_MBSOUT) with ESMTP id sB1HSvEd001113 (version=TLSv1/SSLv3 cipher=AES128-SHA bits=128 verify=OK) for <routing-discussion@ietf.org>; Mon, 1 Dec 2014 09:28:57 -0800
Received: from XCH-BLV-504.nw.nos.boeing.com ([169.254.4.76]) by XCH-BLV-207.nw.nos.boeing.com ([169.254.7.73]) with mapi id 14.03.0210.002; Mon, 1 Dec 2014 09:28:56 -0800
From: "Templin, Fred L" <Fred.L.Templin@boeing.com>
To: "routing-discussion@ietf.org" <routing-discussion@ietf.org>
Subject: Multiprotocol tunneling over UDP using AERO
Thread-Topic: Multiprotocol tunneling over UDP using AERO
Thread-Index: AdANi2m8UlvuyiTrTg+MXp53XC95kQ==
Date: Mon, 1 Dec 2014 17:28:55 +0000
Message-ID: <2134F8430051B64F815C691A62D9831832DA68F6@XCH-BLV-504.nw.nos.boeing.com>
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/routing-discussion/sv2vM4lABidXzltOuELOtdi21FE
X-BeenThere: routing-discussion@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: Routing Area General mailing list <routing-discussion.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/routing-discussion>, <mailto:routing-discussion-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/routing-discussion/>
List-Post: <mailto:routing-discussion@ietf.org>
List-Help: <mailto:routing-discussion-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/routing-discussion>, <mailto:routing-discussion-request@ietf.org?subject=subscribe>
X-List-Received-Date: Mon, 01 Dec 2014 17:29:13 -0000

Hello,

I am working on a spec for generic tunneling of any protocol over UDP, incl=
uding
MPLS, GRE, IPsec, etc. The spec is called "AERO", and it includes:

  - an encapsulation format
  - a fragmentation and reassembly capability for MTU mitigation
  - a virtual link model
  - a control messaging mechanism
  - a routing and addressing system based on BGP

https://datatracker.ietf.org/doc/draft-templin-aerolink/

I understand that there have been discussions regarding protocol-specific
GRE and MPLS encapsulations within UDP, but I would like to offer up AERO
as a protocol-independent way of accommodating UDP encapsulations. I
also believe the routing system and other aspects of AERO should be of
interest to the routing area.

This work is derived from an earlier experimental RFC (RFC6706) which was
originally briefed to the routing area several years ago and published as a=
n
AD-sponsored Individual Submission RFC. The current document can be
considered as a second edition of AERO, and the goal is to advance it to
standards track. Please send any comments or questions to the list.

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


From nobody Mon Dec  1 11:49:48 2014
Return-Path: <adrian@olddog.co.uk>
X-Original-To: routing-discussion@ietfa.amsl.com
Delivered-To: routing-discussion@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 32BCE1A8AC2 for <routing-discussion@ietfa.amsl.com>; Mon,  1 Dec 2014 11:49:44 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -101.9
X-Spam-Level: 
X-Spam-Status: No, score=-101.9 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RCVD_IN_DNSWL_NONE=-0.0001, USER_IN_WHITELIST=-100] 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 ajXtPTxBD69P for <routing-discussion@ietfa.amsl.com>; Mon,  1 Dec 2014 11:49:41 -0800 (PST)
Received: from asmtp2.iomartmail.com (asmtp2.iomartmail.com [62.128.201.249]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 4EB951A8A49 for <routing-discussion@ietf.org>; Mon,  1 Dec 2014 11:49:31 -0800 (PST)
Received: from asmtp2.iomartmail.com (localhost.localdomain [127.0.0.1]) by asmtp2.iomartmail.com (8.13.8/8.13.8) with ESMTP id sB1JnQPf019097; Mon, 1 Dec 2014 19:49:26 GMT
Received: from 950129200 (dsl-sp-81-140-15-32.in-addr.broadbandscope.com [81.140.15.32]) (authenticated bits=0) by asmtp2.iomartmail.com (8.13.8/8.13.8) with ESMTP id sB1JnPXe019080 (version=TLSv1/SSLv3 cipher=AES256-SHA bits=256 verify=NO); Mon, 1 Dec 2014 19:49:25 GMT
From: "Adrian Farrel" <adrian@olddog.co.uk>
To: "'Templin, Fred L'" <Fred.L.Templin@boeing.com>, <routing-discussion@ietf.org>
References: <2134F8430051B64F815C691A62D9831832DA68F6@XCH-BLV-504.nw.nos.boeing.com>
In-Reply-To: <2134F8430051B64F815C691A62D9831832DA68F6@XCH-BLV-504.nw.nos.boeing.com>
Subject: RE: Multiprotocol tunneling over UDP using AERO
Date: Mon, 1 Dec 2014 19:49:22 -0000
Message-ID: <081601d00d9f$e806b820$b8142860$@olddog.co.uk>
MIME-Version: 1.0
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: 7bit
X-Mailer: Microsoft Outlook 14.0
Thread-Index: AQI/LOePMZkWRbtgU5m7vfq7L1j//Zuc4wsA
Content-Language: en-gb
X-TM-AS-MML: disable
X-TM-AS-Product-Ver: IMSS-7.1.0.1576-7.5.0.1018-21144.001
X-TM-AS-Result: No--21.648-10.0-31-10
X-imss-scan-details: No--21.648-10.0-31-10
X-TMASE-MatchedRID: vsV5zF0VLZuPvrMjLFD6eOYAh37ZsBDCQKuv8uQBDjos+NN86TqCu1x9 1vue5xn5kYT5USYazQNFOo8YlMxNsjPAnsAORqSfnVTWWiNp+v/2kudi1D33EtUfIBFKJ53U94V amfVCBA5X6mZf8RDtgkbqDOdAo9D1TkaqbB0m3sLM1jffIgQXhh9fNWA7SFWqotQoHOwzCQmO9I TQYjB8RbN7Enw/fX+LAwhI3SAg8ijCpdw+7xrhsucFAGXwxaF1u2rcU2ygxCCTMTaQzhvoeuX9K wzrnWYoYyA5ge0CmXexwpYAbAfWP3S8vP347grLvHKClHGjjr0CVgBn/xl97czvOkSymob/82+Z JoKeNOW36h2hK5rvdpGTpe1iiCJqtD9qpBlNF8rAuFFGa+JUhYcSB+DBj8cnOAawE8JvIaK8QIu 4z6HhEH7cGd19dSFd
Archived-At: http://mailarchive.ietf.org/arch/msg/routing-discussion/EvpxsY642slVri10SQ9JJin710E
X-BeenThere: routing-discussion@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
Reply-To: adrian@olddog.co.uk
List-Id: Routing Area General mailing list <routing-discussion.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/routing-discussion>, <mailto:routing-discussion-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/routing-discussion/>
List-Post: <mailto:routing-discussion@ietf.org>
List-Help: <mailto:routing-discussion-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/routing-discussion>, <mailto:routing-discussion-request@ietf.org?subject=subscribe>
X-List-Received-Date: Mon, 01 Dec 2014 19:49:44 -0000

Hi Fred,

Thanks for the heads-up.

You're right that there has been some work going on in the Routing Area chiefly
around MPLS-in-UDP in the MPLS working group.
There has also been a lot of overlap with the TSV area. Specifically the TSVWG
has had a lot to say about MPLS-in-UDP and also has a document on its books for
GRE-in-UDP (https://datatracker.ietf.org/doc/draft-ietf-tsvwg-gre-in-udp-encap/)

These try to be conformant to
https://datatracker.ietf.org/doc/draft-eggert-tsvwg-rfc5405bis/ and there has
been a lot of debate about getting the congestion control and checksum parts of
the work correct.

Now, it should be said that both pieces of this work are handling the
encapsulation only.

They are not looking at forming a "new network layer" in the way that AERO is.

Regards,
Adrian

> -----Original Message-----
> From: routing-discussion [mailto:routing-discussion-bounces@ietf.org] On
Behalf
> Of Templin, Fred L
> Sent: 01 December 2014 17:29
> To: routing-discussion@ietf.org
> Subject: Multiprotocol tunneling over UDP using AERO
> 
> Hello,
> 
> I am working on a spec for generic tunneling of any protocol over UDP,
including
> MPLS, GRE, IPsec, etc. The spec is called "AERO", and it includes:
> 
>   - an encapsulation format
>   - a fragmentation and reassembly capability for MTU mitigation
>   - a virtual link model
>   - a control messaging mechanism
>   - a routing and addressing system based on BGP
> 
> https://datatracker.ietf.org/doc/draft-templin-aerolink/
> 
> I understand that there have been discussions regarding protocol-specific
> GRE and MPLS encapsulations within UDP, but I would like to offer up AERO
> as a protocol-independent way of accommodating UDP encapsulations. I
> also believe the routing system and other aspects of AERO should be of
> interest to the routing area.
> 
> This work is derived from an earlier experimental RFC (RFC6706) which was
> originally briefed to the routing area several years ago and published as an
> AD-sponsored Individual Submission RFC. The current document can be
> considered as a second edition of AERO, and the goal is to advance it to
> standards track. Please send any comments or questions to the list.
> 
> Thanks - Fred
> fred.l.templin@boeing.com
> 
> _______________________________________________
> routing-discussion mailing list
> routing-discussion@ietf.org
> https://www.ietf.org/mailman/listinfo/routing-discussion


From nobody Mon Dec  1 14:47:49 2014
Return-Path: <Fred.L.Templin@boeing.com>
X-Original-To: routing-discussion@ietfa.amsl.com
Delivered-To: routing-discussion@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id EE42A1ACD75 for <routing-discussion@ietfa.amsl.com>; Mon,  1 Dec 2014 14:47:47 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -4.21
X-Spam-Level: 
X-Spam-Status: No, score=-4.21 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RCVD_IN_DNSWL_MED=-2.3, 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 xlsTbbOI62BQ for <routing-discussion@ietfa.amsl.com>; Mon,  1 Dec 2014 14:47:25 -0800 (PST)
Received: from slb-mbsout-01.boeing.com (slb-mbsout-01.boeing.com [130.76.64.128]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 0D9091ACD51 for <routing-discussion@ietf.org>; Mon,  1 Dec 2014 14:46:55 -0800 (PST)
Received: from localhost (localhost [127.0.0.1]) by slb-mbsout-01.boeing.com (8.14.4/8.14.4/DOWNSTREAM_MBSOUT) with SMTP id sB1MktLe023042; Mon, 1 Dec 2014 14:46:55 -0800
Received: from XCH-BLV-501.nw.nos.boeing.com (xch-blv-501.nw.nos.boeing.com [130.247.25.190]) by slb-mbsout-01.boeing.com (8.14.4/8.14.4/UPSTREAM_MBSOUT) with ESMTP id sB1MkpGQ023018 (version=TLSv1/SSLv3 cipher=AES128-SHA bits=128 verify=OK); Mon, 1 Dec 2014 14:46:52 -0800
Received: from XCH-BLV-504.nw.nos.boeing.com ([169.254.4.76]) by XCH-BLV-501.nw.nos.boeing.com ([169.254.1.28]) with mapi id 14.03.0210.002; Mon, 1 Dec 2014 14:46:32 -0800
From: "Templin, Fred L" <Fred.L.Templin@boeing.com>
To: "adrian@olddog.co.uk" <adrian@olddog.co.uk>, "routing-discussion@ietf.org" <routing-discussion@ietf.org>
Subject: RE: Multiprotocol tunneling over UDP using AERO
Thread-Topic: Multiprotocol tunneling over UDP using AERO
Thread-Index: AdANi2m8UlvuyiTrTg+MXp53XC95kQAV4tgAAAscY5A=
Date: Mon, 1 Dec 2014 22:46:31 +0000
Message-ID: <2134F8430051B64F815C691A62D9831832DA6E25@XCH-BLV-504.nw.nos.boeing.com>
References: <2134F8430051B64F815C691A62D9831832DA68F6@XCH-BLV-504.nw.nos.boeing.com> <081601d00d9f$e806b820$b8142860$@olddog.co.uk>
In-Reply-To: <081601d00d9f$e806b820$b8142860$@olddog.co.uk>
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/routing-discussion/PuYopx6JyOVRHZiQZpHxYrOf-r0
X-BeenThere: routing-discussion@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: Routing Area General mailing list <routing-discussion.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/routing-discussion>, <mailto:routing-discussion-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/routing-discussion/>
List-Post: <mailto:routing-discussion@ietf.org>
List-Help: <mailto:routing-discussion-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/routing-discussion>, <mailto:routing-discussion-request@ietf.org?subject=subscribe>
X-List-Received-Date: Mon, 01 Dec 2014 22:47:48 -0000

Hi Adrian,

> -----Original Message-----
> From: Adrian Farrel [mailto:adrian@olddog.co.uk]
> Sent: Monday, December 01, 2014 11:49 AM
> To: Templin, Fred L; routing-discussion@ietf.org
> Subject: RE: Multiprotocol tunneling over UDP using AERO
>=20
> Hi Fred,
>=20
> Thanks for the heads-up.
>=20
> You're right that there has been some work going on in the Routing Area c=
hiefly
> around MPLS-in-UDP in the MPLS working group.
> There has also been a lot of overlap with the TSV area. Specifically the =
TSVWG
> has had a lot to say about MPLS-in-UDP and also has a document on its boo=
ks for
> GRE-in-UDP (https://datatracker.ietf.org/doc/draft-ietf-tsvwg-gre-in-udp-=
encap/)

Thanks for the pointer. It appears that this proposal is punting on tunnel =
fragmentation,
meaning that the tunnel would either have to use IP fragmentation or perfor=
m MTU
clamping. We would like for tunnels to be able to support a minimum 1500 MT=
U and
also allow larger packets when the path MTU is sufficient. Tunnels that cla=
mp the MTU
to something smaller than 1500 can't do that. AERO fixes this by including =
tunnel
fragmentation to avoid the need for MTU clamping.

> These try to be conformant to
> https://datatracker.ietf.org/doc/draft-eggert-tsvwg-rfc5405bis/ and there=
 has
> been a lot of debate about getting the congestion control and checksum pa=
rts of
> the work correct.

That looks like  a good reference, and I will read up on it further. I am p=
retty sure
we will find that AERO is also compliant.

> Now, it should be said that both pieces of this work are handling the
> encapsulation only.

OK.

> They are not looking at forming a "new network layer" in the way that AER=
O is.

Right, AERO is looking at a complete tunneling solution, including routing,=
 addressing,
mobility, security, etc. However, the AERO encapsulation format can be used=
 w/o
having to adopt the proposal in its entirety. But, I'm not sure why you wou=
ldn't.

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

> Regards,
> Adrian
>=20
> > -----Original Message-----
> > From: routing-discussion [mailto:routing-discussion-bounces@ietf.org] O=
n
> Behalf
> > Of Templin, Fred L
> > Sent: 01 December 2014 17:29
> > To: routing-discussion@ietf.org
> > Subject: Multiprotocol tunneling over UDP using AERO
> >
> > Hello,
> >
> > I am working on a spec for generic tunneling of any protocol over UDP,
> including
> > MPLS, GRE, IPsec, etc. The spec is called "AERO", and it includes:
> >
> >   - an encapsulation format
> >   - a fragmentation and reassembly capability for MTU mitigation
> >   - a virtual link model
> >   - a control messaging mechanism
> >   - a routing and addressing system based on BGP
> >
> > https://datatracker.ietf.org/doc/draft-templin-aerolink/
> >
> > I understand that there have been discussions regarding protocol-specif=
ic
> > GRE and MPLS encapsulations within UDP, but I would like to offer up AE=
RO
> > as a protocol-independent way of accommodating UDP encapsulations. I
> > also believe the routing system and other aspects of AERO should be of
> > interest to the routing area.
> >
> > This work is derived from an earlier experimental RFC (RFC6706) which w=
as
> > originally briefed to the routing area several years ago and published =
as an
> > AD-sponsored Individual Submission RFC. The current document can be
> > considered as a second edition of AERO, and the goal is to advance it t=
o
> > standards track. Please send any comments or questions to the list.
> >
> > Thanks - Fred
> > fred.l.templin@boeing.com
> >
> > _______________________________________________
> > routing-discussion mailing list
> > routing-discussion@ietf.org
> > https://www.ietf.org/mailman/listinfo/routing-discussion


From nobody Tue Dec  2 12:57:59 2014
Return-Path: <Fred.L.Templin@boeing.com>
X-Original-To: routing-discussion@ietfa.amsl.com
Delivered-To: routing-discussion@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 087EF1A7013; Tue,  2 Dec 2014 12:57:51 -0800 (PST)
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 z9_uWOrKIq1b; Tue,  2 Dec 2014 12:57:49 -0800 (PST)
Received: from slb-mbsout-01.boeing.com (slb-mbsout-01.boeing.com [130.76.64.128]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 49A741A1DE1; Tue,  2 Dec 2014 12:57:49 -0800 (PST)
Received: from localhost (localhost [127.0.0.1]) by slb-mbsout-01.boeing.com (8.14.4/8.14.4/DOWNSTREAM_MBSOUT) with SMTP id sB2KvmSG009944; Tue, 2 Dec 2014 12:57:48 -0800
Received: from XCH-PHX-211.sw.nos.boeing.com (xch-phx-211.sw.nos.boeing.com [130.247.25.140]) by slb-mbsout-01.boeing.com (8.14.4/8.14.4/UPSTREAM_MBSOUT) with ESMTP id sB2KvfcK009441 (version=TLSv1/SSLv3 cipher=AES128-SHA bits=128 verify=OK); Tue, 2 Dec 2014 12:57:42 -0800
Received: from XCH-BLV-504.nw.nos.boeing.com ([169.254.4.76]) by XCH-PHX-211.sw.nos.boeing.com ([169.254.11.133]) with mapi id 14.03.0210.002;  Tue, 2 Dec 2014 12:57:41 -0800
From: "Templin, Fred L" <Fred.L.Templin@boeing.com>
To: "tsvwg@ietf.org" <tsvwg@ietf.org>, "int-area@ietf.org" <int-area@ietf.org>, "routing-discussion@ietf.org" <routing-discussion@ietf.org>
Subject: Multiprotocol tunneling over UDP using AERO
Thread-Topic: Multiprotocol tunneling over UDP using AERO
Thread-Index: AdAOcPTIDrG60uxAS3KTsgWvKVuuvA==
Date: Tue, 2 Dec 2014 20:57:40 +0000
Message-ID: <2134F8430051B64F815C691A62D9831832DA7C70@XCH-BLV-504.nw.nos.boeing.com>
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/routing-discussion/EfqfiX5APgTvTaCa5VcgdHlR-V0
X-BeenThere: routing-discussion@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: Routing Area General mailing list <routing-discussion.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/routing-discussion>, <mailto:routing-discussion-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/routing-discussion/>
List-Post: <mailto:routing-discussion@ietf.org>
List-Help: <mailto:routing-discussion-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/routing-discussion>, <mailto:routing-discussion-request@ietf.org?subject=subscribe>
X-List-Received-Date: Tue, 02 Dec 2014 20:57:51 -0000

Hello,

I am replaying a message below that was originally posted on the routing-di=
scussion
list yesterday. Follow-up discussion was then posted in two additional mess=
ages. The
messages are here:

http://www.ietf.org/mail-archive/web/routing-discussion/current/msg01949.ht=
ml
http://www.ietf.org/mail-archive/web/routing-discussion/current/msg01950.ht=
ml
http://www.ietf.org/mail-archive/web/routing-discussion/current/msg01951.ht=
ml

I am cross-posting to transport area and int area now, because there seems =
to be
an overlap of interests with respect to UDP tunneling that may transcend tr=
aditional
area boundaries. Original message appears below; please post comments to th=
e lists.

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

---

Hello,

I am working on a spec for generic tunneling of any protocol over UDP, incl=
uding
MPLS, GRE, IPsec, etc. The spec is called "AERO", and it includes:

  - an encapsulation format
  - a fragmentation and reassembly capability for MTU mitigation
  - a virtual link model
  - a control messaging mechanism
  - a routing and addressing system based on BGP

https://datatracker.ietf.org/doc/draft-templin-aerolink/

I understand that there have been discussions regarding protocol-specific
GRE and MPLS encapsulations within UDP, but I would like to offer up AERO
as a protocol-independent way of accommodating UDP encapsulations. I
also believe the routing system and other aspects of AERO should be of
interest to the routing area.

This work is derived from an earlier experimental RFC (RFC6706) which was
originally briefed to the routing area several years ago and published as a=
n
AD-sponsored Individual Submission RFC. The current document can be
considered as a second edition of AERO, and the goal is to advance it to
standards track. Please send any comments or questions to the list.

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


From nobody Tue Dec  2 14:26:53 2014
Return-Path: <l.wood@surrey.ac.uk>
X-Original-To: routing-discussion@ietfa.amsl.com
Delivered-To: routing-discussion@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 28FE61A1AAF; Tue,  2 Dec 2014 14:26:48 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -4.202
X-Spam-Level: 
X-Spam-Status: No, score=-4.202 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RCVD_IN_DNSWL_MED=-2.3, SPF_HELO_PASS=-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 oBbEpsjODpUt; Tue,  2 Dec 2014 14:26:45 -0800 (PST)
Received: from mail1.bemta14.messagelabs.com (mail1.bemta14.messagelabs.com [193.109.254.112]) (using TLSv1.2 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 770291A0030; Tue,  2 Dec 2014 14:26:44 -0800 (PST)
Received: from [193.109.255.147] by server-8.bemta-14.messagelabs.com id 4E/07-03148-2AC3E745; Tue, 02 Dec 2014 22:26:42 +0000
X-Env-Sender: l.wood@surrey.ac.uk
X-Msg-Ref: server-6.tower-72.messagelabs.com!1417559201!14232901!1
X-Originating-IP: [131.227.200.39]
X-StarScan-Received: 
X-StarScan-Version: 6.12.4; banners=-,-,-
X-VirusChecked: Checked
Received: (qmail 17631 invoked from network); 2 Dec 2014 22:26:42 -0000
Received: from exht012p.surrey.ac.uk (HELO EXHT012P.surrey.ac.uk) (131.227.200.39) by server-6.tower-72.messagelabs.com with AES128-SHA encrypted SMTP; 2 Dec 2014 22:26:42 -0000
Received: from EXHY011V.surrey.ac.uk (131.227.200.103) by EXHT012P.surrey.ac.uk (131.227.200.39) with Microsoft SMTP Server (TLS) id 8.3.348.2; Tue, 2 Dec 2014 22:26:41 +0000
Received: from emea01-am1-obe.outbound.protection.outlook.com (131.227.200.4) by EXHY011v.surrey.ac.uk (131.227.200.103) with Microsoft SMTP Server (TLS) id 14.3.195.1; Tue, 2 Dec 2014 22:26:41 +0000
Received: from DB4PR06MB458.eurprd06.prod.outlook.com (10.141.238.19) by DB4PR06MB174.eurprd06.prod.outlook.com (10.242.155.148) with Microsoft SMTP Server (TLS) id 15.1.26.15; Tue, 2 Dec 2014 22:26:41 +0000
Received: from DB4PR06MB457.eurprd06.prod.outlook.com (10.141.238.15) by DB4PR06MB458.eurprd06.prod.outlook.com (10.141.238.19) with Microsoft SMTP Server (TLS) id 15.1.26.15; Tue, 2 Dec 2014 22:26:39 +0000
Received: from DB4PR06MB457.eurprd06.prod.outlook.com ([10.141.238.15]) by DB4PR06MB457.eurprd06.prod.outlook.com ([10.141.238.15]) with mapi id 15.01.0026.003; Tue, 2 Dec 2014 22:26:39 +0000
From: <l.wood@surrey.ac.uk>
To: <Fred.L.Templin@boeing.com>, <tsvwg@ietf.org>, <int-area@ietf.org>, <routing-discussion@ietf.org>
Subject: Re: Multiprotocol tunneling over UDP using AERO
Thread-Topic: Multiprotocol tunneling over UDP using AERO
Thread-Index: AdAOcPTIUlvuyiTrTg+MXp53XC95kQAB0fjf
Date: Tue, 2 Dec 2014 22:26:39 +0000
Message-ID: <1417559198240.10209@surrey.ac.uk>
References: <2134F8430051B64F815C691A62D9831832DA7C70@XCH-BLV-504.nw.nos.boeing.com>
In-Reply-To: <2134F8430051B64F815C691A62D9831832DA7C70@XCH-BLV-504.nw.nos.boeing.com>
Accept-Language: en-AU, en-US
Content-Language: en-US
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
x-originating-ip: [122.200.59.254]
x-microsoft-antispam: BCL:0;PCL:0;RULEID:;SRVR:DB4PR06MB458;UriScan:;
x-exchange-antispam-report-test: UriScan:;
x-exchange-antispam-report-cfa-test: BCL:0;PCL:0;RULEID:;SRVR:DB4PR06MB458;
x-forefront-prvs: 0413C9F1ED
x-forefront-antispam-report: SFV:NSPM; SFS:(10019020)(6009001)(199003)(585484001)(189002)(377454003)(19580405001)(19580395003)(117636001)(2656002)(15975445006)(74482002)(46102003)(101416001)(97736003)(2501002)(36756003)(99396003)(21056001)(1720100001)(15198665003)(62966003)(122556002)(4396001)(120916001)(87936001)(77156002)(40100003)(68736005)(20776003)(2201001)(64706001)(92566001)(66066001)(92726001)(15395725005)(15202345003)(86362001)(95666004)(105586002)(106356001)(107046002)(107886001)(31966008)(76176999)(77096005)(50986999)(54356999)(7059030); DIR:OUT; SFP:1102; SCL:1; SRVR:DB4PR06MB458; H:DB4PR06MB457.eurprd06.prod.outlook.com; FPR:; SPF:None; MLV:sfv; PTR:InfoNoRecords; A:1; MX:1; LANG:en; 
Content-Type: text/plain; charset="iso-8859-1"
Content-Transfer-Encoding: quoted-printable
MIME-Version: 1.0
X-OrganizationHeadersPreserved: DB4PR06MB458.eurprd06.prod.outlook.com
X-Microsoft-Antispam: BCL:0;PCL:0;RULEID:;SRVR:DB4PR06MB174;
X-OriginatorOrg: surrey.ac.uk
X-CrossPremisesHeadersPromoted: EXHY011v.surrey.ac.uk
X-CrossPremisesHeadersFiltered: EXHY011v.surrey.ac.uk
Archived-At: http://mailarchive.ietf.org/arch/msg/routing-discussion/55mGTn4OqhvhLJCOwnwrLcfWFQ8
X-BeenThere: routing-discussion@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: Routing Area General mailing list <routing-discussion.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/routing-discussion>, <mailto:routing-discussion-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/routing-discussion/>
List-Post: <mailto:routing-discussion@ietf.org>
List-Help: <mailto:routing-discussion-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/routing-discussion>, <mailto:routing-discussion-request@ietf.org?subject=subscribe>
X-List-Received-Date: Tue, 02 Dec 2014 22:26:48 -0000

Fred,=0A=
=0A=
I see Adrian mentioned checksums in his reply to you. To elaborate on his p=
oint:=0A=
=0A=
http://datatracker.ietf.org/doc/draft-templin-aerolink/=0A=
says:=0A=
=0A=
   The AERO interface=0A=
   also sets the UDP checksum field to zero (see: [RFC6935][RFC6936])=0A=
   unless an integrity check is required (see: Section 3.12.2).=0A=
=0A=
This misses the more subtle implications of zero checksums. As RFC6936 says=
:=0A=
   The current recommendation=0A=
   is to use or fall back to using UDP with full checksum coverage.=0A=
=0A=
RFC6935 is written from the perspective of tunnelled traffic that can have =
its own checks, rather than from the larger perspective of what is good for=
 the network; the zero checksum was inconvenient for tunnellers, hence RFC6=
935. (While RFC6936 is rather academic and nuanced in its tone, as it steps=
 through the necessary safeguards that that use of zero checksums requires =
of everything else; sometimes 'don't do that, stupid!' is the clearer and s=
impler approach to both writing and engineering.)=0A=
=0A=
A zero UDP checksum means:=0A=
=0A=
- in IPv4, potential delivery to any port on the destination device if ther=
e is UDP header corruption. (the IPv4 header checksum can prevent host misd=
elivery). This is port pollution.=0A=
=0A=
- in IPv6, potential delivery to anywhere if there is IP/UDP header corrupt=
ion (as there is no IP header checksum, and using a zero UDP sum turns off =
the endhost pseudoheader check - and tunnels often terminate on routers tha=
t forward packets...). This is network pollution.=0A=
=0A=
So, use a zero UDP checksum, and the IPv6 traffic you generate can be poten=
tially injected anywhere to affect anything, modulo all the careful nuance =
in RFC6936 to start guarding against this - guards required by everything e=
lse. But your tunnel traffic can have its own checks and its own repeat/rep=
lay, so you're alright.=0A=
=0A=
(UDP-Lite provides a minimal interface to build on with necessary endhost p=
seudo-header check and low computation cost for application designers; sham=
e it's not more prevalent.)=0A=
=0A=
Analogies with nice clean factories pumping into dirty rivers fit nicely he=
re. It's a tragedy that people downstream were relying on the river water, =
but it's clearly not the factory designer's fault. As if. Those people just=
 didn't implement the safeguards in the small print. And environmental prot=
ection wasn't a design goal. Why care about the commons?=0A=
=0A=
My take here is that IPv6 was not well-designed in this regard. An IP heade=
r checksum across non-mutable fields, excluding QoS/TTL etc., that did not =
need to be recomputed, would have been preferable. A mandatory endhost pseu=
doheader check would have been preferable. Expecting protocol designers to =
do the right thing above IP and do the necessary pseudo-header check has be=
en repeatedly demonstrated to presume too much knowledge in those that foll=
ow. Hardly the only IPv6 mistake, but not one we should be compounding.=0A=
=0A=
Please fix AERO, and follow RFC6936's recommendation.=0A=
=0A=
Lloyd Wood=0A=
http://about.me/lloydwood=0A=
=0A=
you'll notice I'm not also asking you to fix the bundle protocol. Lost caus=
e.=0A=
________________________________________=0A=
From: tsvwg <tsvwg-bounces@ietf.org> on behalf of Templin, Fred L <Fred.L.T=
emplin@boeing.com>=0A=
Sent: Wednesday, 3 December 2014 7:57 AM=0A=
To: tsvwg@ietf.org; int-area@ietf.org; routing-discussion@ietf.org=0A=
Subject: [tsvwg] Multiprotocol tunneling over UDP using AERO=0A=
=0A=
Hello,=0A=
=0A=
I am replaying a message below that was originally posted on the routing-di=
scussion=0A=
list yesterday. Follow-up discussion was then posted in two additional mess=
ages. The=0A=
messages are here:=0A=
=0A=
http://www.ietf.org/mail-archive/web/routing-discussion/current/msg01949.ht=
ml=0A=
http://www.ietf.org/mail-archive/web/routing-discussion/current/msg01950.ht=
ml=0A=
http://www.ietf.org/mail-archive/web/routing-discussion/current/msg01951.ht=
ml=0A=
=0A=
I am cross-posting to transport area and int area now, because there seems =
to be=0A=
an overlap of interests with respect to UDP tunneling that may transcend tr=
aditional=0A=
area boundaries. Original message appears below; please post comments to th=
e lists.=0A=
=0A=
Thanks - Fred=0A=
fred.l.templin@boeing.com=0A=
=0A=
---=0A=
=0A=
Hello,=0A=
=0A=
I am working on a spec for generic tunneling of any protocol over UDP, incl=
uding=0A=
MPLS, GRE, IPsec, etc. The spec is called "AERO", and it includes:=0A=
=0A=
  - an encapsulation format=0A=
  - a fragmentation and reassembly capability for MTU mitigation=0A=
  - a virtual link model=0A=
  - a control messaging mechanism=0A=
  - a routing and addressing system based on BGP=0A=
=0A=
https://datatracker.ietf.org/doc/draft-templin-aerolink/=0A=
=0A=
I understand that there have been discussions regarding protocol-specific=
=0A=
GRE and MPLS encapsulations within UDP, but I would like to offer up AERO=
=0A=
as a protocol-independent way of accommodating UDP encapsulations. I=0A=
also believe the routing system and other aspects of AERO should be of=0A=
interest to the routing area.=0A=
=0A=
This work is derived from an earlier experimental RFC (RFC6706) which was=
=0A=
originally briefed to the routing area several years ago and published as a=
n=0A=
AD-sponsored Individual Submission RFC. The current document can be=0A=
considered as a second edition of AERO, and the goal is to advance it to=0A=
standards track. Please send any comments or questions to the list.=0A=
=0A=
Thanks - Fred=0A=
fred.l.templin@boeing.com=0A=
=0A=


From nobody Tue Dec  2 14:46:23 2014
Return-Path: <therbert@google.com>
X-Original-To: routing-discussion@ietfa.amsl.com
Delivered-To: routing-discussion@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id B75AD1A1ACE for <routing-discussion@ietfa.amsl.com>; Tue,  2 Dec 2014 14:40:06 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.389
X-Spam-Level: 
X-Spam-Status: No, score=-1.389 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, FM_FORGED_GMAIL=0.622, SPF_PASS=-0.001, T_RP_MATCHES_RCVD=-0.01] autolearn=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 JIOipV0s2tGo for <routing-discussion@ietfa.amsl.com>; Tue,  2 Dec 2014 14:40:04 -0800 (PST)
Received: from mail-ie0-x230.google.com (mail-ie0-x230.google.com [IPv6:2607:f8b0:4001:c03::230]) (using TLSv1 with cipher ECDHE-RSA-RC4-SHA (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 5C2221A1A97 for <routing-discussion@ietf.org>; Tue,  2 Dec 2014 14:40:04 -0800 (PST)
Received: by mail-ie0-f176.google.com with SMTP id tr6so12595502ieb.21 for <routing-discussion@ietf.org>; Tue, 02 Dec 2014 14:40:03 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=google.com; s=20120113; h=mime-version:in-reply-to:references:date:message-id:subject:from:to :cc:content-type:content-transfer-encoding; bh=WhTVd3EkwIcNR3Q2aYBZlSlgJl/dlxPsDdiSvy0Wjiw=; b=ersED/3R9XLT8uPuWuE+hAHQWLtyEZjesNHbMvexBC71wKwaeve96OdSogMxtqVtZ8 bCw0VdNiWigerd0p/NwXTLswoFjTw/aRSixtfug6gTvt+s9pTUwtg7agVm0V1NieionU C2gaDccLLZRnFm3W67B3B0B89Ttg3f750e+N9uaxl0/d96SVlDEQCxQfjvtx3YXfpKXc RR/aNDSw8cs3iSlGhIDWqbxcLFgNKRwk0DYIUsJuoE8fzL4bip4NiLMJwfkMASxqPCkd LE3pk2y395O52I/kFVStyui9ZRjGLGJdZrdSlkdF87HS96AZ3qzLP9/DfdOGwbqcDz/8 WIFA==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20130820; h=x-gm-message-state:mime-version:in-reply-to:references:date :message-id:subject:from:to:cc:content-type :content-transfer-encoding; bh=WhTVd3EkwIcNR3Q2aYBZlSlgJl/dlxPsDdiSvy0Wjiw=; b=jqQVqSSGF8QckE+kw62irvMXbrC3BpWaM4XsTY3kuaXSnr6JiVgp1OOvwy6T8he1MR CrMPBkVMuqCqjXQhnKjUO27x5/Pg2TkhI6xqakld5rW44CuTaDVuCwcTXmY4scbR9PQv qh7lNS9RL8ftsKntw4H0hMeuF2+MJPmbPWDF4heIZh1drlaWuoWDJhIB7sNwc8MtgHpK tPcrOeBjv1KRhK1BjwVh7EyTJ73DkDCncWsTVMXuzVx3rPjU9P9dcDBmWk+Bxsk44sXx KCb7/sSRTNrp6AWiKYnFekS5k2Q0E4jl56heV6eb0pGkKgGyUjXnuX3Fx7mxpuuajWuP J38w==
X-Gm-Message-State: ALoCoQkyxzoqA7098RGy/90dJo1v5qa+/EkLxVfKVjz3mUfmIryzUQtbEy194F6hamWr7kIO4aaM
MIME-Version: 1.0
X-Received: by 10.42.255.72 with SMTP id nh8mr4650489icb.1.1417560003262; Tue, 02 Dec 2014 14:40:03 -0800 (PST)
Received: by 10.64.98.167 with HTTP; Tue, 2 Dec 2014 14:40:03 -0800 (PST)
In-Reply-To: <1417559198240.10209@surrey.ac.uk>
References: <2134F8430051B64F815C691A62D9831832DA7C70@XCH-BLV-504.nw.nos.boeing.com> <1417559198240.10209@surrey.ac.uk>
Date: Tue, 2 Dec 2014 14:40:03 -0800
Message-ID: <CA+mtBx9kuDoarkdPHeZCLEDZUW2PThc13hjkNtmf9va1G_XF=g@mail.gmail.com>
Subject: Re: [tsvwg] Multiprotocol tunneling over UDP using AERO
From: Tom Herbert <therbert@google.com>
To: l.wood@surrey.ac.uk
Content-Type: text/plain; charset=UTF-8
Content-Transfer-Encoding: quoted-printable
Archived-At: http://mailarchive.ietf.org/arch/msg/routing-discussion/0TI76C0Yoffm8fsW1FTzJ--doZU
X-Mailman-Approved-At: Tue, 02 Dec 2014 14:46:21 -0800
Cc: int-area@ietf.org, tsvwg@ietf.org, routing-discussion@ietf.org
X-BeenThere: routing-discussion@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: Routing Area General mailing list <routing-discussion.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/routing-discussion>, <mailto:routing-discussion-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/routing-discussion/>
List-Post: <mailto:routing-discussion@ietf.org>
List-Help: <mailto:routing-discussion-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/routing-discussion>, <mailto:routing-discussion-request@ietf.org?subject=subscribe>
X-List-Received-Date: Tue, 02 Dec 2014 22:40:07 -0000

On Tue, Dec 2, 2014 at 2:26 PM,  <l.wood@surrey.ac.uk> wrote:
> Fred,
>
> I see Adrian mentioned checksums in his reply to you. To elaborate on his=
 point:
>
> http://datatracker.ietf.org/doc/draft-templin-aerolink/
> says:
>
>    The AERO interface
>    also sets the UDP checksum field to zero (see: [RFC6935][RFC6936])
>    unless an integrity check is required (see: Section 3.12.2).
>
> This misses the more subtle implications of zero checksums. As RFC6936 sa=
ys:
>    The current recommendation
>    is to use or fall back to using UDP with full checksum coverage.
>
> RFC6935 is written from the perspective of tunnelled traffic that can hav=
e its own checks, rather than from the larger perspective of what is good f=
or the network; the zero checksum was inconvenient for tunnellers, hence RF=
C6935. (While RFC6936 is rather academic and nuanced in its tone, as it ste=
ps through the necessary safeguards that that use of zero checksums require=
s of everything else; sometimes 'don't do that, stupid!' is the clearer and=
 simpler approach to both writing and engineering.)
>
> A zero UDP checksum means:
>
> - in IPv4, potential delivery to any port on the destination device if th=
ere is UDP header corruption. (the IPv4 header checksum can prevent host mi=
sdelivery). This is port pollution.
>
> - in IPv6, potential delivery to anywhere if there is IP/UDP header corru=
ption (as there is no IP header checksum, and using a zero UDP sum turns of=
f the endhost pseudoheader check - and tunnels often terminate on routers t=
hat forward packets...). This is network pollution.
>
> So, use a zero UDP checksum, and the IPv6 traffic you generate can be pot=
entially injected anywhere to affect anything, modulo all the careful nuanc=
e in RFC6936 to start guarding against this - guards required by everything=
 else. But your tunnel traffic can have its own checks and its own repeat/r=
eplay, so you're alright.
>
> (UDP-Lite provides a minimal interface to build on with necessary endhost=
 pseudo-header check and low computation cost for application designers; sh=
ame it's not more prevalent.)
>
> Analogies with nice clean factories pumping into dirty rivers fit nicely =
here. It's a tragedy that people downstream were relying on the river water=
, but it's clearly not the factory designer's fault. As if. Those people ju=
st didn't implement the safeguards in the small print. And environmental pr=
otection wasn't a design goal. Why care about the commons?
>
> My take here is that IPv6 was not well-designed in this regard. An IP hea=
der checksum across non-mutable fields, excluding QoS/TTL etc., that did no=
t need to be recomputed, would have been preferable. A mandatory endhost ps=
eudoheader check would have been preferable. Expecting protocol designers t=
o do the right thing above IP and do the necessary pseudo-header check has =
been repeatedly demonstrated to presume too much knowledge in those that fo=
llow. Hardly the only IPv6 mistake, but not one we should be compounding.
>
> Please fix AERO, and follow RFC6936's recommendation.
>
Another alternative might be to include a checksum in the
encapsulation header that includes a pseudo header covering ports and
addresses. This is what we intend to do in Generic UDP Encapsulation
(draft-herbert-guecsum-00).

> Lloyd Wood
> http://about.me/lloydwood
>
> you'll notice I'm not also asking you to fix the bundle protocol. Lost ca=
use.
> ________________________________________
> From: tsvwg <tsvwg-bounces@ietf.org> on behalf of Templin, Fred L <Fred.L=
.Templin@boeing.com>
> Sent: Wednesday, 3 December 2014 7:57 AM
> To: tsvwg@ietf.org; int-area@ietf.org; routing-discussion@ietf.org
> Subject: [tsvwg] Multiprotocol tunneling over UDP using AERO
>
> Hello,
>
> I am replaying a message below that was originally posted on the routing-=
discussion
> list yesterday. Follow-up discussion was then posted in two additional me=
ssages. The
> messages are here:
>
> http://www.ietf.org/mail-archive/web/routing-discussion/current/msg01949.=
html
> http://www.ietf.org/mail-archive/web/routing-discussion/current/msg01950.=
html
> http://www.ietf.org/mail-archive/web/routing-discussion/current/msg01951.=
html
>
> I am cross-posting to transport area and int area now, because there seem=
s to be
> an overlap of interests with respect to UDP tunneling that may transcend =
traditional
> area boundaries. Original message appears below; please post comments to =
the lists.
>
> Thanks - Fred
> fred.l.templin@boeing.com
>
> ---
>
> Hello,
>
> I am working on a spec for generic tunneling of any protocol over UDP, in=
cluding
> MPLS, GRE, IPsec, etc. The spec is called "AERO", and it includes:
>
>   - an encapsulation format
>   - a fragmentation and reassembly capability for MTU mitigation
>   - a virtual link model
>   - a control messaging mechanism
>   - a routing and addressing system based on BGP
>
> https://datatracker.ietf.org/doc/draft-templin-aerolink/
>
> I understand that there have been discussions regarding protocol-specific
> GRE and MPLS encapsulations within UDP, but I would like to offer up AERO
> as a protocol-independent way of accommodating UDP encapsulations. I
> also believe the routing system and other aspects of AERO should be of
> interest to the routing area.
>
> This work is derived from an earlier experimental RFC (RFC6706) which was
> originally briefed to the routing area several years ago and published as=
 an
> AD-sponsored Individual Submission RFC. The current document can be
> considered as a second edition of AERO, and the goal is to advance it to
> standards track. Please send any comments or questions to the list.
>
> Thanks - Fred
> fred.l.templin@boeing.com
>
>


From nobody Tue Dec  2 15:11:25 2014
Return-Path: <Fred.L.Templin@boeing.com>
X-Original-To: routing-discussion@ietfa.amsl.com
Delivered-To: routing-discussion@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 304951A1A90; Tue,  2 Dec 2014 15:11:03 -0800 (PST)
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 pmQe7QcyqMiX; Tue,  2 Dec 2014 15:10:51 -0800 (PST)
Received: from stl-mbsout-02.boeing.com (stl-mbsout-02.boeing.com [130.76.96.170]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id E1BB31A1A6B; Tue,  2 Dec 2014 15:10:50 -0800 (PST)
Received: from localhost (localhost [127.0.0.1]) by stl-mbsout-02.boeing.com (8.14.4/8.14.4/DOWNSTREAM_MBSOUT) with SMTP id sB2NAn75025685; Tue, 2 Dec 2014 17:10:49 -0600
Received: from XCH-PHX-113.sw.nos.boeing.com (xch-phx-113.sw.nos.boeing.com [130.247.25.136]) by stl-mbsout-02.boeing.com (8.14.4/8.14.4/UPSTREAM_MBSOUT) with ESMTP id sB2NAk6U025655 (version=TLSv1/SSLv3 cipher=AES128-SHA bits=128 verify=OK); Tue, 2 Dec 2014 17:10:47 -0600
Received: from XCH-BLV-504.nw.nos.boeing.com ([169.254.4.76]) by XCH-PHX-113.sw.nos.boeing.com ([169.254.13.175]) with mapi id 14.03.0210.002;  Tue, 2 Dec 2014 15:10:45 -0800
From: "Templin, Fred L" <Fred.L.Templin@boeing.com>
To: "l.wood@surrey.ac.uk" <l.wood@surrey.ac.uk>, "tsvwg@ietf.org" <tsvwg@ietf.org>, "int-area@ietf.org" <int-area@ietf.org>, "routing-discussion@ietf.org" <routing-discussion@ietf.org>
Subject: RE: Multiprotocol tunneling over UDP using AERO
Thread-Topic: Multiprotocol tunneling over UDP using AERO
Thread-Index: AdAOcPTIDrG60uxAS3KTsgWvKVuuvAAUSOmAAA9L6SA=
Date: Tue, 2 Dec 2014 23:10:45 +0000
Message-ID: <2134F8430051B64F815C691A62D9831832DA7DE4@XCH-BLV-504.nw.nos.boeing.com>
References: <2134F8430051B64F815C691A62D9831832DA7C70@XCH-BLV-504.nw.nos.boeing.com> <1417559198240.10209@surrey.ac.uk>
In-Reply-To: <1417559198240.10209@surrey.ac.uk>
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/routing-discussion/oJVMFUmRM60CBLyztkD_vLpS5ew
X-BeenThere: routing-discussion@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: Routing Area General mailing list <routing-discussion.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/routing-discussion>, <mailto:routing-discussion-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/routing-discussion/>
List-Post: <mailto:routing-discussion@ietf.org>
List-Help: <mailto:routing-discussion-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/routing-discussion>, <mailto:routing-discussion-request@ietf.org?subject=subscribe>
X-List-Received-Date: Tue, 02 Dec 2014 23:11:03 -0000

Hi Llloyd,

Thanks for the excellent analysis. I have had my head down on other aspects=
 of the
spec and not following the UDP checksum discussions. I will fix it.

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

> -----Original Message-----
> From: l.wood@surrey.ac.uk [mailto:l.wood@surrey.ac.uk]
> Sent: Tuesday, December 02, 2014 2:27 PM
> To: Templin, Fred L; tsvwg@ietf.org; int-area@ietf.org; routing-discussio=
n@ietf.org
> Subject: Re: Multiprotocol tunneling over UDP using AERO
>=20
> Fred,
>=20
> I see Adrian mentioned checksums in his reply to you. To elaborate on his=
 point:
>=20
> http://datatracker.ietf.org/doc/draft-templin-aerolink/
> says:
>=20
>    The AERO interface
>    also sets the UDP checksum field to zero (see: [RFC6935][RFC6936])
>    unless an integrity check is required (see: Section 3.12.2).
>=20
> This misses the more subtle implications of zero checksums. As RFC6936 sa=
ys:
>    The current recommendation
>    is to use or fall back to using UDP with full checksum coverage.
>=20
> RFC6935 is written from the perspective of tunnelled traffic that can hav=
e its own checks, rather than from the larger perspective of
> what is good for the network; the zero checksum was inconvenient for tunn=
ellers, hence RFC6935. (While RFC6936 is rather academic
> and nuanced in its tone, as it steps through the necessary safeguards tha=
t that use of zero checksums requires of everything else;
> sometimes 'don't do that, stupid!' is the clearer and simpler approach to=
 both writing and engineering.)
>=20
> A zero UDP checksum means:
>=20
> - in IPv4, potential delivery to any port on the destination device if th=
ere is UDP header corruption. (the IPv4 header checksum can
> prevent host misdelivery). This is port pollution.
>=20
> - in IPv6, potential delivery to anywhere if there is IP/UDP header corru=
ption (as there is no IP header checksum, and using a zero UDP
> sum turns off the endhost pseudoheader check - and tunnels often terminat=
e on routers that forward packets...). This is network
> pollution.
>=20
> So, use a zero UDP checksum, and the IPv6 traffic you generate can be pot=
entially injected anywhere to affect anything, modulo all
> the careful nuance in RFC6936 to start guarding against this - guards req=
uired by everything else. But your tunnel traffic can have its
> own checks and its own repeat/replay, so you're alright.
>=20
> (UDP-Lite provides a minimal interface to build on with necessary endhost=
 pseudo-header check and low computation cost for
> application designers; shame it's not more prevalent.)
>=20
> Analogies with nice clean factories pumping into dirty rivers fit nicely =
here. It's a tragedy that people downstream were relying on the
> river water, but it's clearly not the factory designer's fault. As if. Th=
ose people just didn't implement the safeguards in the small print.
> And environmental protection wasn't a design goal. Why care about the com=
mons?
>=20
> My take here is that IPv6 was not well-designed in this regard. An IP hea=
der checksum across non-mutable fields, excluding QoS/TTL
> etc., that did not need to be recomputed, would have been preferable. A m=
andatory endhost pseudoheader check would have been
> preferable. Expecting protocol designers to do the right thing above IP a=
nd do the necessary pseudo-header check has been
> repeatedly demonstrated to presume too much knowledge in those that follo=
w. Hardly the only IPv6 mistake, but not one we should
> be compounding.
>=20
> Please fix AERO, and follow RFC6936's recommendation.
>=20
> Lloyd Wood
> http://about.me/lloydwood
>=20
> you'll notice I'm not also asking you to fix the bundle protocol. Lost ca=
use.
> ________________________________________
> From: tsvwg <tsvwg-bounces@ietf.org> on behalf of Templin, Fred L <Fred.L=
.Templin@boeing.com>
> Sent: Wednesday, 3 December 2014 7:57 AM
> To: tsvwg@ietf.org; int-area@ietf.org; routing-discussion@ietf.org
> Subject: [tsvwg] Multiprotocol tunneling over UDP using AERO
>=20
> Hello,
>=20
> I am replaying a message below that was originally posted on the routing-=
discussion
> list yesterday. Follow-up discussion was then posted in two additional me=
ssages. The
> messages are here:
>=20
> http://www.ietf.org/mail-archive/web/routing-discussion/current/msg01949.=
html
> http://www.ietf.org/mail-archive/web/routing-discussion/current/msg01950.=
html
> http://www.ietf.org/mail-archive/web/routing-discussion/current/msg01951.=
html
>=20
> I am cross-posting to transport area and int area now, because there seem=
s to be
> an overlap of interests with respect to UDP tunneling that may transcend =
traditional
> area boundaries. Original message appears below; please post comments to =
the lists.
>=20
> Thanks - Fred
> fred.l.templin@boeing.com
>=20
> ---
>=20
> Hello,
>=20
> I am working on a spec for generic tunneling of any protocol over UDP, in=
cluding
> MPLS, GRE, IPsec, etc. The spec is called "AERO", and it includes:
>=20
>   - an encapsulation format
>   - a fragmentation and reassembly capability for MTU mitigation
>   - a virtual link model
>   - a control messaging mechanism
>   - a routing and addressing system based on BGP
>=20
> https://datatracker.ietf.org/doc/draft-templin-aerolink/
>=20
> I understand that there have been discussions regarding protocol-specific
> GRE and MPLS encapsulations within UDP, but I would like to offer up AERO
> as a protocol-independent way of accommodating UDP encapsulations. I
> also believe the routing system and other aspects of AERO should be of
> interest to the routing area.
>=20
> This work is derived from an earlier experimental RFC (RFC6706) which was
> originally briefed to the routing area several years ago and published as=
 an
> AD-sponsored Individual Submission RFC. The current document can be
> considered as a second edition of AERO, and the goal is to advance it to
> standards track. Please send any comments or questions to the list.
>=20
> Thanks - Fred
> fred.l.templin@boeing.com


From nobody Tue Dec  2 15:18:17 2014
Return-Path: <Fred.L.Templin@boeing.com>
X-Original-To: routing-discussion@ietfa.amsl.com
Delivered-To: routing-discussion@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 81E3F1A6F0A; Tue,  2 Dec 2014 15:18:08 -0800 (PST)
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 UoFWySaG6SP2; Tue,  2 Dec 2014 15:18:06 -0800 (PST)
Received: from blv-mbsout-02.boeing.com (blv-mbsout-02.boeing.com [130.76.32.232]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 2C9D41A1BCA; Tue,  2 Dec 2014 15:18:06 -0800 (PST)
Received: from localhost (localhost [127.0.0.1]) by blv-mbsout-02.boeing.com (8.14.4/8.14.4/DOWNSTREAM_MBSOUT) with SMTP id sB2NI58R006778; Tue, 2 Dec 2014 15:18:05 -0800
Received: from XCH-PHX-410.sw.nos.boeing.com (xch-phx-410.sw.nos.boeing.com [10.57.37.41]) by blv-mbsout-02.boeing.com (8.14.4/8.14.4/UPSTREAM_MBSOUT) with ESMTP id sB2NHwNd006582 (version=TLSv1/SSLv3 cipher=AES128-SHA bits=128 verify=OK); Tue, 2 Dec 2014 15:17:58 -0800
Received: from XCH-BLV-504.nw.nos.boeing.com ([169.254.4.76]) by XCH-PHX-410.sw.nos.boeing.com ([169.254.10.179]) with mapi id 14.03.0210.002;  Tue, 2 Dec 2014 15:17:58 -0800
From: "Templin, Fred L" <Fred.L.Templin@boeing.com>
To: Tom Herbert <therbert@google.com>, "l.wood@surrey.ac.uk" <l.wood@surrey.ac.uk>
Subject: RE: [tsvwg] Multiprotocol tunneling over UDP using AERO
Thread-Topic: [tsvwg] Multiprotocol tunneling over UDP using AERO
Thread-Index: AQHQDoDvIrLJzf+uZkSV+8i05eS+EJx87W7Q
Date: Tue, 2 Dec 2014 23:17:57 +0000
Message-ID: <2134F8430051B64F815C691A62D9831832DA7E08@XCH-BLV-504.nw.nos.boeing.com>
References: <2134F8430051B64F815C691A62D9831832DA7C70@XCH-BLV-504.nw.nos.boeing.com> <1417559198240.10209@surrey.ac.uk> <CA+mtBx9kuDoarkdPHeZCLEDZUW2PThc13hjkNtmf9va1G_XF=g@mail.gmail.com>
In-Reply-To: <CA+mtBx9kuDoarkdPHeZCLEDZUW2PThc13hjkNtmf9va1G_XF=g@mail.gmail.com>
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="utf-8"
Content-Transfer-Encoding: base64
MIME-Version: 1.0
X-TM-AS-MML: disable
Archived-At: http://mailarchive.ietf.org/arch/msg/routing-discussion/Rn6dnlXNMHKvpoFxgNFtBTBsgqk
Cc: "int-area@ietf.org" <int-area@ietf.org>, "tsvwg@ietf.org" <tsvwg@ietf.org>, "routing-discussion@ietf.org" <routing-discussion@ietf.org>
X-BeenThere: routing-discussion@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: Routing Area General mailing list <routing-discussion.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/routing-discussion>, <mailto:routing-discussion-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/routing-discussion/>
List-Post: <mailto:routing-discussion@ietf.org>
List-Help: <mailto:routing-discussion-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/routing-discussion>, <mailto:routing-discussion-request@ietf.org?subject=subscribe>
X-List-Received-Date: Tue, 02 Dec 2014 23:18:08 -0000

SGkgVG9tLA0KDQo+IC0tLS0tT3JpZ2luYWwgTWVzc2FnZS0tLS0tDQo+IEZyb206IFRvbSBIZXJi
ZXJ0IFttYWlsdG86dGhlcmJlcnRAZ29vZ2xlLmNvbV0NCj4gU2VudDogVHVlc2RheSwgRGVjZW1i
ZXIgMDIsIDIwMTQgMjo0MCBQTQ0KPiBUbzogbC53b29kQHN1cnJleS5hYy51aw0KPiBDYzogVGVt
cGxpbiwgRnJlZCBMOyB0c3Z3Z0BpZXRmLm9yZzsgaW50LWFyZWFAaWV0Zi5vcmc7IHJvdXRpbmct
ZGlzY3Vzc2lvbkBpZXRmLm9yZw0KPiBTdWJqZWN0OiBSZTogW3RzdndnXSBNdWx0aXByb3RvY29s
IHR1bm5lbGluZyBvdmVyIFVEUCB1c2luZyBBRVJPDQo+IA0KPiBPbiBUdWUsIERlYyAyLCAyMDE0
IGF0IDI6MjYgUE0sICA8bC53b29kQHN1cnJleS5hYy51az4gd3JvdGU6DQo+ID4gRnJlZCwNCj4g
Pg0KPiA+IEkgc2VlIEFkcmlhbiBtZW50aW9uZWQgY2hlY2tzdW1zIGluIGhpcyByZXBseSB0byB5
b3UuIFRvIGVsYWJvcmF0ZSBvbiBoaXMgcG9pbnQ6DQo+ID4NCj4gPiBodHRwOi8vZGF0YXRyYWNr
ZXIuaWV0Zi5vcmcvZG9jL2RyYWZ0LXRlbXBsaW4tYWVyb2xpbmsvDQo+ID4gc2F5czoNCj4gPg0K
PiA+ICAgIFRoZSBBRVJPIGludGVyZmFjZQ0KPiA+ICAgIGFsc28gc2V0cyB0aGUgVURQIGNoZWNr
c3VtIGZpZWxkIHRvIHplcm8gKHNlZTogW1JGQzY5MzVdW1JGQzY5MzZdKQ0KPiA+ICAgIHVubGVz
cyBhbiBpbnRlZ3JpdHkgY2hlY2sgaXMgcmVxdWlyZWQgKHNlZTogU2VjdGlvbiAzLjEyLjIpLg0K
PiA+DQo+ID4gVGhpcyBtaXNzZXMgdGhlIG1vcmUgc3VidGxlIGltcGxpY2F0aW9ucyBvZiB6ZXJv
IGNoZWNrc3Vtcy4gQXMgUkZDNjkzNiBzYXlzOg0KPiA+ICAgIFRoZSBjdXJyZW50IHJlY29tbWVu
ZGF0aW9uDQo+ID4gICAgaXMgdG8gdXNlIG9yIGZhbGwgYmFjayB0byB1c2luZyBVRFAgd2l0aCBm
dWxsIGNoZWNrc3VtIGNvdmVyYWdlLg0KPiA+DQo+ID4gUkZDNjkzNSBpcyB3cml0dGVuIGZyb20g
dGhlIHBlcnNwZWN0aXZlIG9mIHR1bm5lbGxlZCB0cmFmZmljIHRoYXQgY2FuIGhhdmUgaXRzIG93
biBjaGVja3MsIHJhdGhlciB0aGFuIGZyb20gdGhlIGxhcmdlciBwZXJzcGVjdGl2ZSBvZg0KPiB3
aGF0IGlzIGdvb2QgZm9yIHRoZSBuZXR3b3JrOyB0aGUgemVybyBjaGVja3N1bSB3YXMgaW5jb252
ZW5pZW50IGZvciB0dW5uZWxsZXJzLCBoZW5jZSBSRkM2OTM1LiAoV2hpbGUgUkZDNjkzNiBpcyBy
YXRoZXIgYWNhZGVtaWMNCj4gYW5kIG51YW5jZWQgaW4gaXRzIHRvbmUsIGFzIGl0IHN0ZXBzIHRo
cm91Z2ggdGhlIG5lY2Vzc2FyeSBzYWZlZ3VhcmRzIHRoYXQgdGhhdCB1c2Ugb2YgemVybyBjaGVj
a3N1bXMgcmVxdWlyZXMgb2YgZXZlcnl0aGluZyBlbHNlOw0KPiBzb21ldGltZXMgJ2Rvbid0IGRv
IHRoYXQsIHN0dXBpZCEnIGlzIHRoZSBjbGVhcmVyIGFuZCBzaW1wbGVyIGFwcHJvYWNoIHRvIGJv
dGggd3JpdGluZyBhbmQgZW5naW5lZXJpbmcuKQ0KPiA+DQo+ID4gQSB6ZXJvIFVEUCBjaGVja3N1
bSBtZWFuczoNCj4gPg0KPiA+IC0gaW4gSVB2NCwgcG90ZW50aWFsIGRlbGl2ZXJ5IHRvIGFueSBw
b3J0IG9uIHRoZSBkZXN0aW5hdGlvbiBkZXZpY2UgaWYgdGhlcmUgaXMgVURQIGhlYWRlciBjb3Jy
dXB0aW9uLiAodGhlIElQdjQgaGVhZGVyIGNoZWNrc3VtIGNhbg0KPiBwcmV2ZW50IGhvc3QgbWlz
ZGVsaXZlcnkpLiBUaGlzIGlzIHBvcnQgcG9sbHV0aW9uLg0KPiA+DQo+ID4gLSBpbiBJUHY2LCBw
b3RlbnRpYWwgZGVsaXZlcnkgdG8gYW55d2hlcmUgaWYgdGhlcmUgaXMgSVAvVURQIGhlYWRlciBj
b3JydXB0aW9uIChhcyB0aGVyZSBpcyBubyBJUCBoZWFkZXIgY2hlY2tzdW0sIGFuZCB1c2luZyBh
IHplcm8NCj4gVURQIHN1bSB0dXJucyBvZmYgdGhlIGVuZGhvc3QgcHNldWRvaGVhZGVyIGNoZWNr
IC0gYW5kIHR1bm5lbHMgb2Z0ZW4gdGVybWluYXRlIG9uIHJvdXRlcnMgdGhhdCBmb3J3YXJkIHBh
Y2tldHMuLi4pLiBUaGlzIGlzDQo+IG5ldHdvcmsgcG9sbHV0aW9uLg0KPiA+DQo+ID4gU28sIHVz
ZSBhIHplcm8gVURQIGNoZWNrc3VtLCBhbmQgdGhlIElQdjYgdHJhZmZpYyB5b3UgZ2VuZXJhdGUg
Y2FuIGJlIHBvdGVudGlhbGx5IGluamVjdGVkIGFueXdoZXJlIHRvIGFmZmVjdCBhbnl0aGluZywg
bW9kdWxvIGFsbA0KPiB0aGUgY2FyZWZ1bCBudWFuY2UgaW4gUkZDNjkzNiB0byBzdGFydCBndWFy
ZGluZyBhZ2FpbnN0IHRoaXMgLSBndWFyZHMgcmVxdWlyZWQgYnkgZXZlcnl0aGluZyBlbHNlLiBC
dXQgeW91ciB0dW5uZWwgdHJhZmZpYyBjYW4gaGF2ZSBpdHMNCj4gb3duIGNoZWNrcyBhbmQgaXRz
IG93biByZXBlYXQvcmVwbGF5LCBzbyB5b3UncmUgYWxyaWdodC4NCj4gPg0KPiA+IChVRFAtTGl0
ZSBwcm92aWRlcyBhIG1pbmltYWwgaW50ZXJmYWNlIHRvIGJ1aWxkIG9uIHdpdGggbmVjZXNzYXJ5
IGVuZGhvc3QgcHNldWRvLWhlYWRlciBjaGVjayBhbmQgbG93IGNvbXB1dGF0aW9uIGNvc3QgZm9y
DQo+IGFwcGxpY2F0aW9uIGRlc2lnbmVyczsgc2hhbWUgaXQncyBub3QgbW9yZSBwcmV2YWxlbnQu
KQ0KPiA+DQo+ID4gQW5hbG9naWVzIHdpdGggbmljZSBjbGVhbiBmYWN0b3JpZXMgcHVtcGluZyBp
bnRvIGRpcnR5IHJpdmVycyBmaXQgbmljZWx5IGhlcmUuIEl0J3MgYSB0cmFnZWR5IHRoYXQgcGVv
cGxlIGRvd25zdHJlYW0gd2VyZSByZWx5aW5nIG9uDQo+IHRoZSByaXZlciB3YXRlciwgYnV0IGl0
J3MgY2xlYXJseSBub3QgdGhlIGZhY3RvcnkgZGVzaWduZXIncyBmYXVsdC4gQXMgaWYuIFRob3Nl
IHBlb3BsZSBqdXN0IGRpZG4ndCBpbXBsZW1lbnQgdGhlIHNhZmVndWFyZHMgaW4gdGhlIHNtYWxs
DQo+IHByaW50LiBBbmQgZW52aXJvbm1lbnRhbCBwcm90ZWN0aW9uIHdhc24ndCBhIGRlc2lnbiBn
b2FsLiBXaHkgY2FyZSBhYm91dCB0aGUgY29tbW9ucz8NCj4gPg0KPiA+IE15IHRha2UgaGVyZSBp
cyB0aGF0IElQdjYgd2FzIG5vdCB3ZWxsLWRlc2lnbmVkIGluIHRoaXMgcmVnYXJkLiBBbiBJUCBo
ZWFkZXIgY2hlY2tzdW0gYWNyb3NzIG5vbi1tdXRhYmxlIGZpZWxkcywgZXhjbHVkaW5nIFFvUy9U
VEwNCj4gZXRjLiwgdGhhdCBkaWQgbm90IG5lZWQgdG8gYmUgcmVjb21wdXRlZCwgd291bGQgaGF2
ZSBiZWVuIHByZWZlcmFibGUuIEEgbWFuZGF0b3J5IGVuZGhvc3QgcHNldWRvaGVhZGVyIGNoZWNr
IHdvdWxkIGhhdmUgYmVlbg0KPiBwcmVmZXJhYmxlLiBFeHBlY3RpbmcgcHJvdG9jb2wgZGVzaWdu
ZXJzIHRvIGRvIHRoZSByaWdodCB0aGluZyBhYm92ZSBJUCBhbmQgZG8gdGhlIG5lY2Vzc2FyeSBw
c2V1ZG8taGVhZGVyIGNoZWNrIGhhcyBiZWVuDQo+IHJlcGVhdGVkbHkgZGVtb25zdHJhdGVkIHRv
IHByZXN1bWUgdG9vIG11Y2gga25vd2xlZGdlIGluIHRob3NlIHRoYXQgZm9sbG93LiBIYXJkbHkg
dGhlIG9ubHkgSVB2NiBtaXN0YWtlLCBidXQgbm90IG9uZSB3ZSBzaG91bGQNCj4gYmUgY29tcG91
bmRpbmcuDQo+ID4NCj4gPiBQbGVhc2UgZml4IEFFUk8sIGFuZCBmb2xsb3cgUkZDNjkzNidzIHJl
Y29tbWVuZGF0aW9uLg0KPiA+DQo+IEFub3RoZXIgYWx0ZXJuYXRpdmUgbWlnaHQgYmUgdG8gaW5j
bHVkZSBhIGNoZWNrc3VtIGluIHRoZQ0KPiBlbmNhcHN1bGF0aW9uIGhlYWRlciB0aGF0IGluY2x1
ZGVzIGEgcHNldWRvIGhlYWRlciBjb3ZlcmluZyBwb3J0cyBhbmQNCj4gYWRkcmVzc2VzLiBUaGlz
IGlzIHdoYXQgd2UgaW50ZW5kIHRvIGRvIGluIEdlbmVyaWMgVURQIEVuY2Fwc3VsYXRpb24NCj4g
KGRyYWZ0LWhlcmJlcnQtZ3VlY3N1bS0wMCkuDQoNClRoYW5rcyBmb3Igc3VwcGx5aW5nIHRoZSBm
aXguIFRoaXMgc2FtZSBhcHByb2FjaCBjYW4gYmUgYWRvcHRlZCBieSBBRVJPLCBidXQNCnBlcmhh
cHMgaXQgd291bGQgYmUgc3VmZmljaWVudCB0byBpbmNsdWRlIGp1c3QgdGhlIHBzZXVkb2hlYWRl
ciBjaGVja3N1bSBhbmQNCm5vdCB3b3JyeSBhYm91dCBzdXBwbHlpbmcgYSBjb3ZlcmFnZSBsZW5n
dGggdG8gY2hlY2sgYWRkaXRpb25hbCBieXRlcyBiZXlvbmQNCnRoZSBwc2V1ZG9oZWFkZXI/DQoN
CkFFUk8gaXMgYSBnZW5lcmljIFVEUCBlbmNhcHN1bGF0aW9uIGZvcm1hdCBmb3IgSVAtaW4tKGZv
byktaW4tVURQLWluLUlQDQplbmNhcHN1bGF0aW9uLiBUaGUgIihmb28pIiBjYW4gYmUgYW55dGhp
bmcsIGUuZy4sIEdSRSwgTVBMUywgRVNQLCBBSCwgZXRjLg0KSXMgdGhhdCB3aGF0IHlvdXIgYXJl
IHRyeWluZyB0byBkbywgdG9vPw0KDQpUaGFua3MgLSBGcmVkDQpmcmVkLmwudGVtcGxpbkBib2Vp
bmcuY29tDQoNCj4gPiBMbG95ZCBXb29kDQo+ID4gaHR0cDovL2Fib3V0Lm1lL2xsb3lkd29vZA0K
PiA+DQo+ID4geW91J2xsIG5vdGljZSBJJ20gbm90IGFsc28gYXNraW5nIHlvdSB0byBmaXggdGhl
IGJ1bmRsZSBwcm90b2NvbC4gTG9zdCBjYXVzZS4NCj4gPiBfX19fX19fX19fX19fX19fX19fX19f
X19fX19fX19fX19fX19fX19fDQo+ID4gRnJvbTogdHN2d2cgPHRzdndnLWJvdW5jZXNAaWV0Zi5v
cmc+IG9uIGJlaGFsZiBvZiBUZW1wbGluLCBGcmVkIEwgPEZyZWQuTC5UZW1wbGluQGJvZWluZy5j
b20+DQo+ID4gU2VudDogV2VkbmVzZGF5LCAzIERlY2VtYmVyIDIwMTQgNzo1NyBBTQ0KPiA+IFRv
OiB0c3Z3Z0BpZXRmLm9yZzsgaW50LWFyZWFAaWV0Zi5vcmc7IHJvdXRpbmctZGlzY3Vzc2lvbkBp
ZXRmLm9yZw0KPiA+IFN1YmplY3Q6IFt0c3Z3Z10gTXVsdGlwcm90b2NvbCB0dW5uZWxpbmcgb3Zl
ciBVRFAgdXNpbmcgQUVSTw0KPiA+DQo+ID4gSGVsbG8sDQo+ID4NCj4gPiBJIGFtIHJlcGxheWlu
ZyBhIG1lc3NhZ2UgYmVsb3cgdGhhdCB3YXMgb3JpZ2luYWxseSBwb3N0ZWQgb24gdGhlIHJvdXRp
bmctZGlzY3Vzc2lvbg0KPiA+IGxpc3QgeWVzdGVyZGF5LiBGb2xsb3ctdXAgZGlzY3Vzc2lvbiB3
YXMgdGhlbiBwb3N0ZWQgaW4gdHdvIGFkZGl0aW9uYWwgbWVzc2FnZXMuIFRoZQ0KPiA+IG1lc3Nh
Z2VzIGFyZSBoZXJlOg0KPiA+DQo+ID4gaHR0cDovL3d3dy5pZXRmLm9yZy9tYWlsLWFyY2hpdmUv
d2ViL3JvdXRpbmctZGlzY3Vzc2lvbi9jdXJyZW50L21zZzAxOTQ5Lmh0bWwNCj4gPiBodHRwOi8v
d3d3LmlldGYub3JnL21haWwtYXJjaGl2ZS93ZWIvcm91dGluZy1kaXNjdXNzaW9uL2N1cnJlbnQv
bXNnMDE5NTAuaHRtbA0KPiA+IGh0dHA6Ly93d3cuaWV0Zi5vcmcvbWFpbC1hcmNoaXZlL3dlYi9y
b3V0aW5nLWRpc2N1c3Npb24vY3VycmVudC9tc2cwMTk1MS5odG1sDQo+ID4NCj4gPiBJIGFtIGNy
b3NzLXBvc3RpbmcgdG8gdHJhbnNwb3J0IGFyZWEgYW5kIGludCBhcmVhIG5vdywgYmVjYXVzZSB0
aGVyZSBzZWVtcyB0byBiZQ0KPiA+IGFuIG92ZXJsYXAgb2YgaW50ZXJlc3RzIHdpdGggcmVzcGVj
dCB0byBVRFAgdHVubmVsaW5nIHRoYXQgbWF5IHRyYW5zY2VuZCB0cmFkaXRpb25hbA0KPiA+IGFy
ZWEgYm91bmRhcmllcy4gT3JpZ2luYWwgbWVzc2FnZSBhcHBlYXJzIGJlbG93OyBwbGVhc2UgcG9z
dCBjb21tZW50cyB0byB0aGUgbGlzdHMuDQo+ID4NCj4gPiBUaGFua3MgLSBGcmVkDQo+ID4gZnJl
ZC5sLnRlbXBsaW5AYm9laW5nLmNvbQ0KPiA+DQo+ID4gLS0tDQo+ID4NCj4gPiBIZWxsbywNCj4g
Pg0KPiA+IEkgYW0gd29ya2luZyBvbiBhIHNwZWMgZm9yIGdlbmVyaWMgdHVubmVsaW5nIG9mIGFu
eSBwcm90b2NvbCBvdmVyIFVEUCwgaW5jbHVkaW5nDQo+ID4gTVBMUywgR1JFLCBJUHNlYywgZXRj
LiBUaGUgc3BlYyBpcyBjYWxsZWQgIkFFUk8iLCBhbmQgaXQgaW5jbHVkZXM6DQo+ID4NCj4gPiAg
IC0gYW4gZW5jYXBzdWxhdGlvbiBmb3JtYXQNCj4gPiAgIC0gYSBmcmFnbWVudGF0aW9uIGFuZCBy
ZWFzc2VtYmx5IGNhcGFiaWxpdHkgZm9yIE1UVSBtaXRpZ2F0aW9uDQo+ID4gICAtIGEgdmlydHVh
bCBsaW5rIG1vZGVsDQo+ID4gICAtIGEgY29udHJvbCBtZXNzYWdpbmcgbWVjaGFuaXNtDQo+ID4g
ICAtIGEgcm91dGluZyBhbmQgYWRkcmVzc2luZyBzeXN0ZW0gYmFzZWQgb24gQkdQDQo+ID4NCj4g
PiBodHRwczovL2RhdGF0cmFja2VyLmlldGYub3JnL2RvYy9kcmFmdC10ZW1wbGluLWFlcm9saW5r
Lw0KPiA+DQo+ID4gSSB1bmRlcnN0YW5kIHRoYXQgdGhlcmUgaGF2ZSBiZWVuIGRpc2N1c3Npb25z
IHJlZ2FyZGluZyBwcm90b2NvbC1zcGVjaWZpYw0KPiA+IEdSRSBhbmQgTVBMUyBlbmNhcHN1bGF0
aW9ucyB3aXRoaW4gVURQLCBidXQgSSB3b3VsZCBsaWtlIHRvIG9mZmVyIHVwIEFFUk8NCj4gPiBh
cyBhIHByb3RvY29sLWluZGVwZW5kZW50IHdheSBvZiBhY2NvbW1vZGF0aW5nIFVEUCBlbmNhcHN1
bGF0aW9ucy4gSQ0KPiA+IGFsc28gYmVsaWV2ZSB0aGUgcm91dGluZyBzeXN0ZW0gYW5kIG90aGVy
IGFzcGVjdHMgb2YgQUVSTyBzaG91bGQgYmUgb2YNCj4gPiBpbnRlcmVzdCB0byB0aGUgcm91dGlu
ZyBhcmVhLg0KPiA+DQo+ID4gVGhpcyB3b3JrIGlzIGRlcml2ZWQgZnJvbSBhbiBlYXJsaWVyIGV4
cGVyaW1lbnRhbCBSRkMgKFJGQzY3MDYpIHdoaWNoIHdhcw0KPiA+IG9yaWdpbmFsbHkgYnJpZWZl
ZCB0byB0aGUgcm91dGluZyBhcmVhIHNldmVyYWwgeWVhcnMgYWdvIGFuZCBwdWJsaXNoZWQgYXMg
YW4NCj4gPiBBRC1zcG9uc29yZWQgSW5kaXZpZHVhbCBTdWJtaXNzaW9uIFJGQy4gVGhlIGN1cnJl
bnQgZG9jdW1lbnQgY2FuIGJlDQo+ID4gY29uc2lkZXJlZCBhcyBhIHNlY29uZCBlZGl0aW9uIG9m
IEFFUk8sIGFuZCB0aGUgZ29hbCBpcyB0byBhZHZhbmNlIGl0IHRvDQo+ID4gc3RhbmRhcmRzIHRy
YWNrLiBQbGVhc2Ugc2VuZCBhbnkgY29tbWVudHMgb3IgcXVlc3Rpb25zIHRvIHRoZSBsaXN0Lg0K
PiA+DQo+ID4gVGhhbmtzIC0gRnJlZA0KPiA+IGZyZWQubC50ZW1wbGluQGJvZWluZy5jb20NCj4g
Pg0KPiA+DQo=


From nobody Tue Dec  2 15:30:07 2014
Return-Path: <Fred.L.Templin@boeing.com>
X-Original-To: routing-discussion@ietfa.amsl.com
Delivered-To: routing-discussion@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id D4AB91A1BCA; Tue,  2 Dec 2014 15:30:01 -0800 (PST)
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 YJRbwo1BoRfL; Tue,  2 Dec 2014 15:30:00 -0800 (PST)
Received: from slb-mbsout-01.boeing.com (slb-mbsout-01.boeing.com [130.76.64.128]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 00C7A1A1AFC; Tue,  2 Dec 2014 15:29:59 -0800 (PST)
Received: from localhost (localhost [127.0.0.1]) by slb-mbsout-01.boeing.com (8.14.4/8.14.4/DOWNSTREAM_MBSOUT) with SMTP id sB2NTxQK008035; Tue, 2 Dec 2014 15:29:59 -0800
Received: from XCH-PHX-312.sw.nos.boeing.com (xch-phx-312.sw.nos.boeing.com [130.247.25.173]) by slb-mbsout-01.boeing.com (8.14.4/8.14.4/UPSTREAM_MBSOUT) with ESMTP id sB2NTpU9007038 (version=TLSv1/SSLv3 cipher=AES128-SHA bits=128 verify=OK); Tue, 2 Dec 2014 15:29:51 -0800
Received: from XCH-BLV-504.nw.nos.boeing.com ([169.254.4.76]) by XCH-PHX-312.sw.nos.boeing.com ([169.254.12.151]) with mapi id 14.03.0210.002;  Tue, 2 Dec 2014 15:29:50 -0800
From: "Templin, Fred L" <Fred.L.Templin@boeing.com>
To: "tsvwg@ietf.org" <tsvwg@ietf.org>, "int-area@ietf.org" <int-area@ietf.org>, "routing-discussion@ietf.org" <routing-discussion@ietf.org>
Subject: RE: Multiprotocol tunneling over UDP using AERO
Thread-Topic: Multiprotocol tunneling over UDP using AERO
Thread-Index: AdAOcPTIDrG60uxAS3KTsgWvKVuuvAAFowtA
Date: Tue, 2 Dec 2014 23:29:50 +0000
Message-ID: <2134F8430051B64F815C691A62D9831832DA7E7D@XCH-BLV-504.nw.nos.boeing.com>
References: <2134F8430051B64F815C691A62D9831832DA7C70@XCH-BLV-504.nw.nos.boeing.com>
In-Reply-To: <2134F8430051B64F815C691A62D9831832DA7C70@XCH-BLV-504.nw.nos.boeing.com>
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/routing-discussion/GqWgq2bZhP6ldZRkddnYkl-lOH4
X-BeenThere: routing-discussion@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: Routing Area General mailing list <routing-discussion.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/routing-discussion>, <mailto:routing-discussion-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/routing-discussion/>
List-Post: <mailto:routing-discussion@ietf.org>
List-Help: <mailto:routing-discussion-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/routing-discussion>, <mailto:routing-discussion-request@ietf.org?subject=subscribe>
X-List-Received-Date: Tue, 02 Dec 2014 23:30:02 -0000

Hi,

One other thing that may or may not be worth mentioning is that AERO alread=
y has an
IANA-assigned UDP port number:

aero               8060        udp    Asymmetric Extended Route    [IESG]  =
                                              [IETF_Chair]                 =
                                                       [RFC6706]
                                      Optimization (AERO)

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

> -----Original Message-----
> From: Int-area [mailto:int-area-bounces@ietf.org] On Behalf Of Templin, F=
red L
> Sent: Tuesday, December 02, 2014 12:58 PM
> To: tsvwg@ietf.org; int-area@ietf.org; routing-discussion@ietf.org
> Subject: [Int-area] Multiprotocol tunneling over UDP using AERO
>=20
> Hello,
>=20
> I am replaying a message below that was originally posted on the routing-=
discussion
> list yesterday. Follow-up discussion was then posted in two additional me=
ssages. The
> messages are here:
>=20
> http://www.ietf.org/mail-archive/web/routing-discussion/current/msg01949.=
html
> http://www.ietf.org/mail-archive/web/routing-discussion/current/msg01950.=
html
> http://www.ietf.org/mail-archive/web/routing-discussion/current/msg01951.=
html
>=20
> I am cross-posting to transport area and int area now, because there seem=
s to be
> an overlap of interests with respect to UDP tunneling that may transcend =
traditional
> area boundaries. Original message appears below; please post comments to =
the lists.
>=20
> Thanks - Fred
> fred.l.templin@boeing.com
>=20
> ---
>=20
> Hello,
>=20
> I am working on a spec for generic tunneling of any protocol over UDP, in=
cluding
> MPLS, GRE, IPsec, etc. The spec is called "AERO", and it includes:
>=20
>   - an encapsulation format
>   - a fragmentation and reassembly capability for MTU mitigation
>   - a virtual link model
>   - a control messaging mechanism
>   - a routing and addressing system based on BGP
>=20
> https://datatracker.ietf.org/doc/draft-templin-aerolink/
>=20
> I understand that there have been discussions regarding protocol-specific
> GRE and MPLS encapsulations within UDP, but I would like to offer up AERO
> as a protocol-independent way of accommodating UDP encapsulations. I
> also believe the routing system and other aspects of AERO should be of
> interest to the routing area.
>=20
> This work is derived from an earlier experimental RFC (RFC6706) which was
> originally briefed to the routing area several years ago and published as=
 an
> AD-sponsored Individual Submission RFC. The current document can be
> considered as a second edition of AERO, and the goal is to advance it to
> standards track. Please send any comments or questions to the list.
>=20
> Thanks - Fred
> fred.l.templin@boeing.com
>=20
> _______________________________________________
> Int-area mailing list
> Int-area@ietf.org
> https://www.ietf.org/mailman/listinfo/int-area


From nobody Tue Dec  9 14:46:35 2014
Return-Path: <akatlas@gmail.com>
X-Original-To: routing-discussion@ietfa.amsl.com
Delivered-To: routing-discussion@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id C11D31A6EED for <routing-discussion@ietfa.amsl.com>; Tue,  9 Dec 2014 14:46:34 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.999
X-Spam-Level: 
X-Spam-Status: No, score=-1.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, HTML_MESSAGE=0.001, SPF_PASS=-0.001] autolearn=unavailable
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 JA5WHEzCjkEv for <routing-discussion@ietfa.amsl.com>; Tue,  9 Dec 2014 14:46:33 -0800 (PST)
Received: from mail-yh0-x231.google.com (mail-yh0-x231.google.com [IPv6:2607:f8b0:4002:c01::231]) (using TLSv1 with cipher ECDHE-RSA-RC4-SHA (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id E86591A6F3D for <routing-discussion@ietf.org>; Tue,  9 Dec 2014 14:46:30 -0800 (PST)
Received: by mail-yh0-f49.google.com with SMTP id f10so738444yha.8 for <routing-discussion@ietf.org>; Tue, 09 Dec 2014 14:46:30 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113;  h=mime-version:date:message-id:subject:from:to:content-type; bh=EkX7xIn5A5fSVVo2TU5F/ZsOCqZuRIMXxh0NLFxK24k=; b=kmvrw4pvlhPyfktJbJeX/Tm+Euj2zzvVkNmmLfnTWF8QBUNC0Dh1VnWruyD9TE7uKU X1X91/zIApyVNeGgxxHlUJL0paGC8apVthCcnW3bsZcWelMwQdHqU0uP55pEi7zH5LeU OTxWXYuaPQSg+35wXnjj7ynBtJZ6z+JB1PFjOPZb+VLbwLH35Kac0n8GuBSLyR/smPGd EGdyeWxeZOkwdnz6TqM6EP8ipgrtzvZmnEcNB7m7eOfUAZZ+8mpnIU9x2bwA+1U82D3T /l7Xs1gd7Z2STOmFbtOwSckiuJdE5lgRvB1gzID4n32sUs4u6iPNaAzRZc9yGnm+aFBy NFkg==
MIME-Version: 1.0
X-Received: by 10.170.164.193 with SMTP id g184mr643304ykd.72.1418165190135; Tue, 09 Dec 2014 14:46:30 -0800 (PST)
Received: by 10.170.136.132 with HTTP; Tue, 9 Dec 2014 14:46:30 -0800 (PST)
Date: Tue, 9 Dec 2014 17:46:30 -0500
Message-ID: <CAG4d1rd60hK8=WtYw-nid_Z7Z8+TvdzA52fNx3pFjND+eDWAfA@mail.gmail.com>
Subject: routing area design team on dataplane encapsulation considerations
From: Alia Atlas <akatlas@gmail.com>
To: "routing-discussion@ietf.org" <routing-discussion@ietf.org>
Content-Type: multipart/alternative; boundary=001a113936b46414e80509d05081
Archived-At: http://mailarchive.ietf.org/arch/msg/routing-discussion/XcWh_VLSSvq_BQYdM8BcgCI7M9Y
X-BeenThere: routing-discussion@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: Routing Area General mailing list <routing-discussion.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/routing-discussion>, <mailto:routing-discussion-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/routing-discussion/>
List-Post: <mailto:routing-discussion@ietf.org>
List-Help: <mailto:routing-discussion-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/routing-discussion>, <mailto:routing-discussion-request@ietf.org?subject=subscribe>
X-List-Received-Date: Tue, 09 Dec 2014 22:46:34 -0000

--001a113936b46414e80509d05081
Content-Type: text/plain; charset=UTF-8
Content-Transfer-Encoding: quoted-printable

I have chartered a Routing Area Design Team to work on data-plane
encapsulation considerations.

I've bcc'd nvo3, sfc, bier, and rtgwg as the most directly relevant.
Please keep any conversation in one place on routing-discussion.

Erik Nordmark has kindly agreed to lead this design team.  The members of
the design
team are:

  Albert Tian <albert.tian@ericsson.com>
  Erik Nordmark <nordmark@sonic.net>
  Jesse Gross <jgross@vmware.com>
  Jon Hudson <jon.hudson@gmail.com>
  Larry Kreeger (kreeger) <kreeger@cisco.com>
  Pankaj Garg <Garg.Pankaj@microsoft.com>
  Pat Thaler <pthaler@broadcom.com>
  Tom Herbert <therbert@google.com>

The mailing list, rgt-dt-encap-considerations@ietf.org, is closed but the
archives are
publicly available at:

http://www.ietf.org/mail-archive/web/rtg-dt-encap-considerations/current/ma=
illist.html

The Design Team is chartered as follows:

There have been multiple efforts over the years that have resulted in new
or modified data plane behaviors involving encapsulations. That includes
IETF efforts like MPLS, LISP, and TRILL but also industry efforts like
Vxlan and NVGRE.  These collectively can be seen as a source of insight
into the properties that data planes need to meet.  The IETF is currently
working on potentially new encapsulations in NVO3 and SFC and considering
working on BIER. In addition there is work on tunneling in the INT area.

This is a short term design team chartered to collect and construct useful
advice to parties working on new or modified data plane behaviors that
include additional encapsulations.  The goal is for the group to document
useful advice gathered from interacting with ongoing efforts.  An Internet
Draft will be produced for IETF92 to capture that advice, which will be
discussed in RTGWG.

Data plane encapsulations face a set of common issues such as:

  * How to provide entropy for ECMP
  * Issues around packet size and fragmentation/reassembly
  * OAM - what support is needed in an encapsulation format?
  * Security and privacy.
  * QoS
  * Congestion Considerations
  * IPv6 header protection (non-zero UDP checksum over IPv6 issue)
  * Extensibility - e.g., for evolving OAM, security, and/or congestion
control
  * Layering of multiple encapsulations e.g., SFC over NVO3 over BIER

The design team will provide advice on those issues. The intention is that
even where we have different encapsulations for different purposes carrying
different data, each such encapsulation doesn=E2=80=99t have to reinvent th=
e wheel
for the above common issues.

The design team will look across the routing area in particular at SFC,
NVO3 and BIER. It will not be involved in comparing or analyzing any
particular encapsulation formats proposed in those WGs and BoFs but instead
focus on common advice.

Regards,
Alia

--001a113936b46414e80509d05081
Content-Type: text/html; charset=UTF-8
Content-Transfer-Encoding: quoted-printable

<div dir=3D"ltr">I have chartered a Routing Area Design Team to work on dat=
a-plane encapsulation considerations.<div><br></div><div>I&#39;ve bcc&#39;d=
 nvo3, sfc, bier, and rtgwg as the most directly relevant.=C2=A0 Please kee=
p any conversation in one place on routing-discussion.<br><div><br></div><d=
iv>Erik Nordmark has kindly agreed to lead this design team.=C2=A0 The memb=
ers of the design</div><div>team are:</div><div><br></div><div><div style=
=3D"font-size:13px">=C2=A0 Albert Tian &lt;<a href=3D"mailto:albert.tian@er=
icsson.com" target=3D"_blank">albert.tian@ericsson.com</a>&gt;<br></div><di=
v style=3D"font-size:13px">=C2=A0 Erik Nordmark &lt;<a href=3D"mailto:nordm=
ark@sonic.net" target=3D"_blank">nordmark@sonic.net</a>&gt;<br>=C2=A0 Jesse=
 Gross &lt;<a href=3D"mailto:jgross@vmware.com" target=3D"_blank">jgross@vm=
ware.com</a>&gt;<br>=C2=A0 Jon Hudson &lt;<a href=3D"mailto:jon.hudson@gmai=
l.com" target=3D"_blank">jon.hudson@gmail.com</a>&gt;<br>=C2=A0 Larry Kreeg=
er (kreeger) &lt;<a href=3D"mailto:kreeger@cisco.com" target=3D"_blank">kre=
eger@cisco.com</a>&gt;<br>=C2=A0 Pankaj Garg &lt;<a href=3D"mailto:Garg.Pan=
kaj@microsoft.com" target=3D"_blank">Garg.Pankaj@microsoft.com</a>&gt;<br>=
=C2=A0 Pat Thaler &lt;<a href=3D"mailto:pthaler@broadcom.com" target=3D"_bl=
ank">pthaler@broadcom.com</a>&gt;<br>=C2=A0 Tom Herbert &lt;<a href=3D"mail=
to:therbert@google.com" target=3D"_blank">therbert@google.com</a>&gt;</div>=
</div><div style=3D"font-size:13px"><br></div><div style=3D"font-size:13px"=
>The mailing list, <a href=3D"mailto:rgt-dt-encap-considerations@ietf.org">=
rgt-dt-encap-considerations@ietf.org</a>, is closed but the archives are</d=
iv><div style=3D"font-size:13px">publicly available at:</div><div style=3D"=
font-size:13px">=C2=A0 =C2=A0<a href=3D"http://www.ietf.org/mail-archive/we=
b/rtg-dt-encap-considerations/current/maillist.html">http://www.ietf.org/ma=
il-archive/web/rtg-dt-encap-considerations/current/maillist.html</a></div><=
div style=3D"font-size:13px"><br></div><div style=3D"font-size:13px">The De=
sign Team is chartered as follows:</div><div style=3D"font-size:13px"><br><=
/div><div><span id=3D"docs-internal-guid-9bcbf1a5-3132-1b2d-c12f-3ac55f1d82=
65">There have been multiple efforts over the years that have resulted in n=
ew or modified data plane behaviors involving encapsulations. That includes=
 IETF efforts like MPLS, LISP, and TRILL but also industry efforts like Vxl=
an and NVGRE.=C2=A0 These collectively can be seen as a source of insight i=
nto the properties that data planes need to meet.=C2=A0 The IETF is current=
ly working on potentially new encapsulations in NVO3 and SFC and considerin=
g working on BIER. In addition there is work on tunneling in the INT area.<=
br><br>This is a short term design team chartered to collect and construct =
useful advice to parties working on new or modified data plane behaviors th=
at include additional encapsulations.=C2=A0 The goal is for the group to do=
cument useful advice gathered from interacting with ongoing efforts.=C2=A0 =
An Internet Draft will be produced for IETF92 to capture that advice, which=
 will be discussed in RTGWG.<br><br>Data plane encapsulations face a set of=
 common issues such as:<br><br>=C2=A0 * How to provide entropy for ECMP<br>=
=C2=A0 * Issues around packet size and fragmentation/reassembly<br>=C2=A0 *=
 OAM - what support is needed in an encapsulation format?<br>=C2=A0 * Secur=
ity and privacy.<br>=C2=A0 *=C2=A0QoS<br>=C2=A0 *=C2=A0Congestion Considera=
tions<br>=C2=A0 *=C2=A0IPv6 header protection (non-zero UDP checksum over I=
Pv6 issue)<br>=C2=A0 * Extensibility - e.g., for evolving OAM, security, an=
d/or congestion control<br>=C2=A0 * Layering of multiple encapsulations e.g=
., SFC over NVO3 over BIER</span></div><div><span><br></span></div><div><sp=
an>The design team will provide advice on those issues. The intention is th=
at even where we have different encapsulations for different purposes carry=
ing different data, each such encapsulation doesn=E2=80=99t have to reinven=
t the wheel for the above common issues.<br><br></span></div><div><span>The=
 design team will look across the routing area in particular at SFC, NVO3 a=
nd BIER. It will not be involved in comparing or analyzing any particular e=
ncapsulation formats proposed in those WGs and BoFs but instead focus on co=
mmon advice.</span></div><div><span><br></span></div><div><span>Regards,</s=
pan></div><div><span>Alia</span></div></div></div>

--001a113936b46414e80509d05081--


From nobody Tue Dec  9 14:53:25 2014
Return-Path: <stbryant@cisco.com>
X-Original-To: routing-discussion@ietfa.amsl.com
Delivered-To: routing-discussion@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 731831A8785 for <routing-discussion@ietfa.amsl.com>; Tue,  9 Dec 2014 14:53:20 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -14.511
X-Spam-Level: 
X-Spam-Status: No, score=-14.511 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, RCVD_IN_DNSWL_HI=-5, SPF_PASS=-0.001, T_RP_MATCHES_RCVD=-0.01, USER_IN_DEF_DKIM_WL=-7.5] 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 4pxBc1ap-vqO for <routing-discussion@ietfa.amsl.com>; Tue,  9 Dec 2014 14:53:19 -0800 (PST)
Received: from aer-iport-4.cisco.com (aer-iport-4.cisco.com [173.38.203.54]) (using TLSv1 with cipher RC4-SHA (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 655AF1A87B8 for <routing-discussion@ietf.org>; Tue,  9 Dec 2014 14:53:15 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=cisco.com; i=@cisco.com; l=419; q=dns/txt; s=iport; t=1418165595; x=1419375195; h=message-id:date:from:reply-to:mime-version:to:subject: references:in-reply-to:content-transfer-encoding; bh=FEzHuLVVu89gQn57OOWGeCxF5PRYsC17AQAibkMunZw=; b=func27PUMDCSXnxR5jkTCNHrpIywAnaGn/pEkkopMwYxRkdul+1jOdVC duRdSBhp6552m3zBdZ0MZjo5nZ47frwTrY2xjLWHJScnQaJH4qeLs1kT6 RNpr+ui2Brl3ub3+rVca8e1RgSMopK2lm5rOo29dQqABsL70tb/l2RLwf s=;
X-IronPort-AV: E=Sophos;i="5.07,548,1413244800"; d="scan'208";a="263394192"
Received: from aer-iport-nat.cisco.com (HELO aer-core-2.cisco.com) ([173.38.203.22]) by aer-iport-4.cisco.com with ESMTP; 09 Dec 2014 22:53:13 +0000
Received: from [10.61.97.162] (dhcp-10-61-97-162.cisco.com [10.61.97.162]) by aer-core-2.cisco.com (8.14.5/8.14.5) with ESMTP id sB9MrDrH029830; Tue, 9 Dec 2014 22:53:13 GMT
Message-ID: <54877D58.9050002@cisco.com>
Date: Tue, 09 Dec 2014 22:53:12 +0000
From: Stewart Bryant <stbryant@cisco.com>
User-Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.9; rv:24.0) Gecko/20100101 Thunderbird/24.6.0
MIME-Version: 1.0
To: Alia Atlas <akatlas@gmail.com>, "routing-discussion@ietf.org" <routing-discussion@ietf.org>
Subject: Re: routing area design team on dataplane encapsulation considerations
References: <CAG4d1rd60hK8=WtYw-nid_Z7Z8+TvdzA52fNx3pFjND+eDWAfA@mail.gmail.com>
In-Reply-To: <CAG4d1rd60hK8=WtYw-nid_Z7Z8+TvdzA52fNx3pFjND+eDWAfA@mail.gmail.com>
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit
Archived-At: http://mailarchive.ietf.org/arch/msg/routing-discussion/SnkXf0pHR7injJMzowaYlySJHK8
X-BeenThere: routing-discussion@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
Reply-To: stbryant@cisco.com
List-Id: Routing Area General mailing list <routing-discussion.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/routing-discussion>, <mailto:routing-discussion-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/routing-discussion/>
List-Post: <mailto:routing-discussion@ietf.org>
List-Help: <mailto:routing-discussion-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/routing-discussion>, <mailto:routing-discussion-request@ietf.org?subject=subscribe>
X-List-Received-Date: Tue, 09 Dec 2014 22:53:20 -0000

Alia

On 09/12/2014 22:46, Alia Atlas wrote:
> * IPv6 header protection (non-zero UDP checksum over IPv6 issue)
I am not sure if it is the non-zero UDP checksum over IPv6 issue, or
the zeroUDP checksum over IPv6 issue.

Most people doing tunneling seem quite happy with zero but get pushback
from the transport area.

Perhaps the topic is really

* IPv6 header protection (UDP checksum issue)

- Stewart



From nobody Tue Dec  9 14:57:36 2014
Return-Path: <akatlas@gmail.com>
X-Original-To: routing-discussion@ietfa.amsl.com
Delivered-To: routing-discussion@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 39A0E1A3BA1 for <routing-discussion@ietfa.amsl.com>; Tue,  9 Dec 2014 14:57:35 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.999
X-Spam-Level: 
X-Spam-Status: No, score=-1.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, 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 OrDaG2atxPkW for <routing-discussion@ietfa.amsl.com>; Tue,  9 Dec 2014 14:57:34 -0800 (PST)
Received: from mail-yk0-x22c.google.com (mail-yk0-x22c.google.com [IPv6:2607:f8b0:4002:c07::22c]) (using TLSv1 with cipher ECDHE-RSA-RC4-SHA (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 03E491A1BE1 for <routing-discussion@ietf.org>; Tue,  9 Dec 2014 14:57:34 -0800 (PST)
Received: by mail-yk0-f172.google.com with SMTP id 131so720984ykp.17 for <routing-discussion@ietf.org>; Tue, 09 Dec 2014 14:57:33 -0800 (PST)
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=3KzLSDQQpBkBhY10Vv8OvSAWKjmwFMqhgaY5Ef6tXFg=; b=e5yYcqMQQdQFzTEg5Q6yd5RSiwYDGWJpny9pKAsEJWI2I1KcNMe2OltShZPeYS3BBq zsPmnSUovg393pwO2v1Zwu7vU2j4oJD+ZCOlKJA1KxHlvBuHkdveCvYcgjllz09kxCF7 TydfagYVonnpLnK7nYJMaMDxRZ0c7Xyq17rzAgsVSP7PnFG+OhEwL4T+JgjqukBh58rX bqYQlsCYMsfQkRimPqHtpIIRVJLAhnMJJcjS1FA0Yx9IDwxYB1E0nMyYGwRiNTUJTCqq oUISzKN4TVw6IcXrxaPwudH1RBTFw6GC5Tr+DfJkXJjWX+pnJbLIn2DaR/75b9bwFPRX KnBw==
MIME-Version: 1.0
X-Received: by 10.170.202.196 with SMTP id t187mr698775yke.36.1418165853312; Tue, 09 Dec 2014 14:57:33 -0800 (PST)
Received: by 10.170.136.132 with HTTP; Tue, 9 Dec 2014 14:57:33 -0800 (PST)
In-Reply-To: <54877D58.9050002@cisco.com>
References: <CAG4d1rd60hK8=WtYw-nid_Z7Z8+TvdzA52fNx3pFjND+eDWAfA@mail.gmail.com> <54877D58.9050002@cisco.com>
Date: Tue, 9 Dec 2014 17:57:33 -0500
Message-ID: <CAG4d1revhK335r5T3H27eSwL5Kq9Vseu_BBiciz+krbXRfQnEw@mail.gmail.com>
Subject: Re: routing area design team on dataplane encapsulation considerations
From: Alia Atlas <akatlas@gmail.com>
To: Stewart Bryant <stbryant@cisco.com>
Content-Type: multipart/alternative; boundary=001a1139d06aeb5bf80509d077f5
Archived-At: http://mailarchive.ietf.org/arch/msg/routing-discussion/bCHTC6a4MzOQ38Tgp1l3EXTGICs
Cc: "routing-discussion@ietf.org" <routing-discussion@ietf.org>
X-BeenThere: routing-discussion@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: Routing Area General mailing list <routing-discussion.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/routing-discussion>, <mailto:routing-discussion-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/routing-discussion/>
List-Post: <mailto:routing-discussion@ietf.org>
List-Help: <mailto:routing-discussion-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/routing-discussion>, <mailto:routing-discussion-request@ietf.org?subject=subscribe>
X-List-Received-Date: Tue, 09 Dec 2014 22:57:35 -0000

--001a1139d06aeb5bf80509d077f5
Content-Type: text/plain; charset=UTF-8

Stewart,

On Tue, Dec 9, 2014 at 5:53 PM, Stewart Bryant <stbryant@cisco.com> wrote:

> Alia
>
> On 09/12/2014 22:46, Alia Atlas wrote:
>
>> * IPv6 header protection (non-zero UDP checksum over IPv6 issue)
>>
> I am not sure if it is the non-zero UDP checksum over IPv6 issue, or
> the zeroUDP checksum over IPv6 issue.
>
> Most people doing tunneling seem quite happy with zero but get pushback
> from the transport area.
>
> Perhaps the topic is really
>
> * IPv6 header protection (UDP checksum issue)


These are examples of considerations for the design team and aren't intended
to be exhaustive.

Alia


> - Stewart
>
>
>

--001a1139d06aeb5bf80509d077f5
Content-Type: text/html; charset=UTF-8
Content-Transfer-Encoding: quoted-printable

<div dir=3D"ltr">Stewart,<br><div class=3D"gmail_extra"><br><div class=3D"g=
mail_quote">On Tue, Dec 9, 2014 at 5:53 PM, Stewart Bryant <span dir=3D"ltr=
">&lt;<a href=3D"mailto:stbryant@cisco.com" target=3D"_blank">stbryant@cisc=
o.com</a>&gt;</span> wrote:<br><blockquote class=3D"gmail_quote" style=3D"m=
argin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">Alia<span cla=
ss=3D""><br>
<br>
On 09/12/2014 22:46, Alia Atlas wrote:<br>
<blockquote class=3D"gmail_quote" style=3D"margin:0 0 0 .8ex;border-left:1p=
x #ccc solid;padding-left:1ex">
* IPv6 header protection (non-zero UDP checksum over IPv6 issue)<br>
</blockquote></span>
I am not sure if it is the non-zero UDP checksum over IPv6 issue, or<br>
the zeroUDP checksum over IPv6 issue.<br>
<br>
Most people doing tunneling seem quite happy with zero but get pushback<br>
from the transport area.<br>
<br>
Perhaps the topic is really<br>
<br>
* IPv6 header protection (UDP checksum issue)</blockquote><div><br></div><d=
iv>These are examples of considerations for the design team and aren&#39;t =
intended</div><div>to be exhaustive. =C2=A0</div><div><br></div><div>Alia=
=C2=A0</div><div>=C2=A0</div><blockquote class=3D"gmail_quote" style=3D"mar=
gin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex"><span class=3D"=
HOEnZb"><font color=3D"#888888">
- Stewart<br>
<br>
<br>
</font></span></blockquote></div><br></div></div>

--001a1139d06aeb5bf80509d077f5--


From nobody Tue Dec  9 23:13:17 2014
Return-Path: <nordmark@acm.org>
X-Original-To: routing-discussion@ietfa.amsl.com
Delivered-To: routing-discussion@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id C1F911A1BFA for <routing-discussion@ietfa.amsl.com>; Tue,  9 Dec 2014 23:13:14 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.935
X-Spam-Level: 
X-Spam-Status: No, score=-1.935 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RCVD_IN_DNSWL_LOW=-0.7, SPF_SOFTFAIL=0.665] autolearn=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 BZufr1mOY-zF for <routing-discussion@ietfa.amsl.com>; Tue,  9 Dec 2014 23:13:13 -0800 (PST)
Received: from c.mail.sonic.net (c.mail.sonic.net [64.142.111.80]) (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 89EF91A1B4E for <routing-discussion@ietf.org>; Tue,  9 Dec 2014 23:13:13 -0800 (PST)
Received: from [10.0.1.54] (70-36-209-26.dsl.dynamic.sonic.net [70.36.209.26]) (authenticated bits=0) by c.mail.sonic.net (8.14.9/8.14.9) with ESMTP id sBA7D8oO013872 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NOT); Tue, 9 Dec 2014 23:13:10 -0800
Message-ID: <5487F284.8030803@acm.org>
Date: Tue, 09 Dec 2014 23:13:08 -0800
From: Erik Nordmark <nordmark@acm.org>
User-Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.10; rv:31.0) Gecko/20100101 Thunderbird/31.2.0
MIME-Version: 1.0
To: stbryant@cisco.com, Alia Atlas <akatlas@gmail.com>, "routing-discussion@ietf.org" <routing-discussion@ietf.org>
Subject: Re: routing area design team on dataplane encapsulation considerations
References: <CAG4d1rd60hK8=WtYw-nid_Z7Z8+TvdzA52fNx3pFjND+eDWAfA@mail.gmail.com> <54877D58.9050002@cisco.com>
In-Reply-To: <54877D58.9050002@cisco.com>
Content-Type: text/plain; charset=windows-1252; format=flowed
Content-Transfer-Encoding: 7bit
X-Sonic-CAuth: UmFuZG9tSVa60XKQ+48bqF63gTPwYb/3c8NFCXgJ+oWQcdEj51UWj/P7o7RRjiYDhpuMZPYZS3r5XLxPkXfVX5AJTX0v9NCs
X-Sonic-ID: C;igBw/juA5BG0y1Zegs/dsg== M;jL4Y/zuA5BG0y1Zegs/dsg==
X-Sonic-Spam-Details: 0.0/5.0 by cerberusd
Archived-At: http://mailarchive.ietf.org/arch/msg/routing-discussion/Mlti7rvgvuT3my7UrbeCLn4BkkM
X-BeenThere: routing-discussion@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: Routing Area General mailing list <routing-discussion.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/routing-discussion>, <mailto:routing-discussion-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/routing-discussion/>
List-Post: <mailto:routing-discussion@ietf.org>
List-Help: <mailto:routing-discussion-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/routing-discussion>, <mailto:routing-discussion-request@ietf.org?subject=subscribe>
X-List-Received-Date: Wed, 10 Dec 2014 07:13:15 -0000

On 12/9/14 2:53 PM, Stewart Bryant wrote:
> Alia
>
> On 09/12/2014 22:46, Alia Atlas wrote:
>> * IPv6 header protection (non-zero UDP checksum over IPv6 issue)
> I am not sure if it is the non-zero UDP checksum over IPv6 issue, or
> the zeroUDP checksum over IPv6 issue.
>
> Most people doing tunneling seem quite happy with zero but get pushback
> from the transport area.
>
> Perhaps the topic is really
>
> * IPv6 header protection (UDP checksum issue)

Stewart,

That would probably be a better way to name the issue.

Thanks,
    Erik

>
> - Stewart
>
>
> _______________________________________________
> routing-discussion mailing list
> routing-discussion@ietf.org
> https://www.ietf.org/mailman/listinfo/routing-discussion
>


From nobody Wed Dec 10 02:01:44 2014
Return-Path: <l.wood@surrey.ac.uk>
X-Original-To: routing-discussion@ietfa.amsl.com
Delivered-To: routing-discussion@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 345901A1B80 for <routing-discussion@ietfa.amsl.com>; Wed, 10 Dec 2014 02:01:43 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.902
X-Spam-Level: 
X-Spam-Status: No, score=-1.902 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RCVD_IN_DNSWL_NONE=-0.0001, SPF_HELO_PASS=-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 LmKBx6uysMNd for <routing-discussion@ietfa.amsl.com>; Wed, 10 Dec 2014 02:01:41 -0800 (PST)
Received: from mail1.bemta5.messagelabs.com (mail1.bemta5.messagelabs.com [195.245.231.143]) (using TLSv1.2 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id CCB171A3BA7 for <routing-discussion@ietf.org>; Wed, 10 Dec 2014 02:01:38 -0800 (PST)
Received: from [195.245.231.67] by server-7.bemta-5.messagelabs.com id CE/D4-31453-10A18845; Wed, 10 Dec 2014 10:01:37 +0000
X-Env-Sender: l.wood@surrey.ac.uk
X-Msg-Ref: server-4.tower-82.messagelabs.com!1418205691!34049558!3
X-Originating-IP: [131.227.200.39]
X-StarScan-Received: 
X-StarScan-Version: 6.12.5; banners=-,-,-
X-VirusChecked: Checked
Received: (qmail 4461 invoked from network); 10 Dec 2014 10:01:36 -0000
Received: from exht012p.surrey.ac.uk (HELO EXHT012P.surrey.ac.uk) (131.227.200.39) by server-4.tower-82.messagelabs.com with AES128-SHA encrypted SMTP; 10 Dec 2014 10:01:36 -0000
Received: from EXHY021V.surrey.ac.uk (131.227.200.104) by EXHT012P.surrey.ac.uk (131.227.200.39) with Microsoft SMTP Server (TLS) id 8.3.348.2; Wed, 10 Dec 2014 10:01:33 +0000
Received: from emea01-db3-obe.outbound.protection.outlook.com (131.227.200.4) by EXHY021v.surrey.ac.uk (131.227.200.104) with Microsoft SMTP Server (TLS) id 14.3.195.1; Wed, 10 Dec 2014 10:01:33 +0000
Received: from DB4PR06MB457.eurprd06.prod.outlook.com (10.141.238.15) by DB4PR06MB458.eurprd06.prod.outlook.com (10.141.238.19) with Microsoft SMTP Server (TLS) id 15.1.31.17; Wed, 10 Dec 2014 10:01:32 +0000
Received: from DB4PR06MB457.eurprd06.prod.outlook.com ([10.141.238.15]) by DB4PR06MB457.eurprd06.prod.outlook.com ([10.141.238.15]) with mapi id 15.01.0031.000; Wed, 10 Dec 2014 10:01:32 +0000
From: <l.wood@surrey.ac.uk>
To: <akatlas@gmail.com>, <routing-discussion@ietf.org>, <stbryant@cisco.com>
Subject: Re: routing area design team on dataplane encapsulation considerations
Thread-Topic: routing area design team on dataplane encapsulation considerations
Thread-Index: AQHQFAI+mxeM7C5mI06ufRYYSYZE2pyH3cwAgABL+58=
Date: Wed, 10 Dec 2014 10:01:32 +0000
Message-ID: <DB4PR06MB457D1FCFF0FBBA25E7A4EC3AD620@DB4PR06MB457.eurprd06.prod.outlook.com>
References: <CAG4d1rd60hK8=WtYw-nid_Z7Z8+TvdzA52fNx3pFjND+eDWAfA@mail.gmail.com>,  <54877D58.9050002@cisco.com>
In-Reply-To: <54877D58.9050002@cisco.com>
Accept-Language: en-AU, en-US
Content-Language: en-US
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
x-originating-ip: [124.168.9.252]
x-microsoft-antispam: BCL:0;PCL:0;RULEID:;SRVR:DB4PR06MB458;
x-exchange-antispam-report-test: UriScan:;
x-exchange-antispam-report-cfa-test: BCL:0;PCL:0;RULEID:;SRVR:DB4PR06MB458;
x-forefront-prvs: 0421BF7135
x-forefront-antispam-report: SFV:NSPM; SFS:(10019020)(6009001)(189002)(377454003)(479174003)(24454002)(199003)(40100003)(64706001)(20776003)(2656002)(105586002)(76176999)(77096005)(66066001)(107046002)(21056001)(107886001)(15975445007)(99396003)(102836002)(1720100001)(120916001)(86362001)(122556002)(87936001)(68736005)(106356001)(54606007)(106116001)(76576001)(50986999)(15395725005)(54356999)(4396001)(62966003)(77156002)(46102003)(74482002)(15198665003)(19580405001)(19580395003)(33656002)(92566001)(101416001)(74316001)(31966008)(54206007)(97736003); DIR:OUT; SFP:1102; SCL:1; SRVR:DB4PR06MB458; H:DB4PR06MB457.eurprd06.prod.outlook.com; FPR:; SPF:None; MLV:sfv; PTR:InfoNoRecords; MX:1; A:1; LANG:en; 
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: quoted-printable
MIME-Version: 1.0
X-OrganizationHeadersPreserved: DB4PR06MB458.eurprd06.prod.outlook.com
X-OriginatorOrg: surrey.ac.uk
X-CrossPremisesHeadersPromoted: EXHY021v.surrey.ac.uk
X-CrossPremisesHeadersFiltered: EXHY021v.surrey.ac.uk
Archived-At: http://mailarchive.ietf.org/arch/msg/routing-discussion/d4SVF4GkI0HfogfeRR2QXTOocCE
X-BeenThere: routing-discussion@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: Routing Area General mailing list <routing-discussion.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/routing-discussion>, <mailto:routing-discussion-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/routing-discussion/>
List-Post: <mailto:routing-discussion@ietf.org>
List-Help: <mailto:routing-discussion-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/routing-discussion>, <mailto:routing-discussion-request@ietf.org?subject=subscribe>
X-List-Received-Date: Wed, 10 Dec 2014 10:01:43 -0000

Of course the tunnellers are happy with a zero checksum. The pollution caus=
ed by missent corrupted ipv6 packets evading checks elsewhere does not affe=
ct them.

Congestion is not a problem for tunnellers either. Like zero checksums, any=
 congestion problem caused by a tunnel is just not the tunnel's problem. Wh=
y should the tunneller have to consider congestion? Or zero checksums? Or a=
nything that impedes tunnel performance?

The tragedy of the commons, in action.

Lloyd Wood
http://about.me/lloydwood
________________________________________
From: routing-discussion <routing-discussion-bounces@ietf.org> on behalf of=
 Stewart Bryant <stbryant@cisco.com>
Sent: Wednesday, 10 December 2014 9:53:12 AM
To: Alia Atlas; routing-discussion@ietf.org
Subject: Re: routing area design team on dataplane encapsulation considerat=
ions

Alia

On 09/12/2014 22:46, Alia Atlas wrote:
> * IPv6 header protection (non-zero UDP checksum over IPv6 issue)
I am not sure if it is the non-zero UDP checksum over IPv6 issue, or
the zeroUDP checksum over IPv6 issue.

Most people doing tunneling seem quite happy with zero but get pushback
from the transport area.

Perhaps the topic is really

* IPv6 header protection (UDP checksum issue)

- Stewart


_______________________________________________
routing-discussion mailing list
routing-discussion@ietf.org
https://www.ietf.org/mailman/listinfo/routing-discussion


From nobody Wed Dec 10 02:23:09 2014
Return-Path: <stbryant@cisco.com>
X-Original-To: routing-discussion@ietfa.amsl.com
Delivered-To: routing-discussion@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 7B1331A3BA7 for <routing-discussion@ietfa.amsl.com>; Wed, 10 Dec 2014 02:23:07 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -14.511
X-Spam-Level: 
X-Spam-Status: No, score=-14.511 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, RCVD_IN_DNSWL_HI=-5, SPF_PASS=-0.001, T_RP_MATCHES_RCVD=-0.01, USER_IN_DEF_DKIM_WL=-7.5] 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 xxGu3a0KXWzz for <routing-discussion@ietfa.amsl.com>; Wed, 10 Dec 2014 02:23:06 -0800 (PST)
Received: from aer-iport-1.cisco.com (aer-iport-1.cisco.com [173.38.203.51]) (using TLSv1 with cipher RC4-SHA (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 868C11A0099 for <routing-discussion@ietf.org>; Wed, 10 Dec 2014 02:23:05 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=cisco.com; i=@cisco.com; l=1760; q=dns/txt; s=iport; t=1418206986; x=1419416586; h=message-id:date:from:reply-to:mime-version:to:subject: references:in-reply-to:content-transfer-encoding; bh=x8SvUv6pFVd9/2gV7LbOxPlk7h6lpZWGvHmVxQiiDbs=; b=DVCEYPurqMe8oy689NGjt7NG5dsyUAAkmfj9r0G0qKNPN+X188A3y0DS qdD4gLnIngW8/dc1bW5Du7XWvcgcoaYiMY/hcpjiCltAaImECc0qWgMc6 y3+xf7Xh67RZ5smQXYl2uqguUhllb+AyedkZ4o3C8131JH02+S1h2pu2N g=;
X-IronPort-AV: E=Sophos;i="5.07,551,1413244800"; d="scan'208";a="268828528"
Received: from aer-iport-nat.cisco.com (HELO aer-core-3.cisco.com) ([173.38.203.22]) by aer-iport-1.cisco.com with ESMTP; 10 Dec 2014 10:23:04 +0000
Received: from [10.61.99.142] (dhcp-10-61-99-142.cisco.com [10.61.99.142]) by aer-core-3.cisco.com (8.14.5/8.14.5) with ESMTP id sBAAN3OV030439; Wed, 10 Dec 2014 10:23:03 GMT
Message-ID: <54881F05.3030907@cisco.com>
Date: Wed, 10 Dec 2014 10:23:01 +0000
From: Stewart Bryant <stbryant@cisco.com>
User-Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.9; rv:24.0) Gecko/20100101 Thunderbird/24.6.0
MIME-Version: 1.0
To: l.wood@surrey.ac.uk, akatlas@gmail.com, routing-discussion@ietf.org
Subject: Re: routing area design team on dataplane encapsulation considerations
References: <CAG4d1rd60hK8=WtYw-nid_Z7Z8+TvdzA52fNx3pFjND+eDWAfA@mail.gmail.com>,  <54877D58.9050002@cisco.com> <DB4PR06MB457D1FCFF0FBBA25E7A4EC3AD620@DB4PR06MB457.eurprd06.prod.outlook.com>
In-Reply-To: <DB4PR06MB457D1FCFF0FBBA25E7A4EC3AD620@DB4PR06MB457.eurprd06.prod.outlook.com>
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit
Archived-At: http://mailarchive.ietf.org/arch/msg/routing-discussion/GiQAV8yKo28f_PLIhPjIcvJMQFs
X-BeenThere: routing-discussion@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
Reply-To: stbryant@cisco.com
List-Id: Routing Area General mailing list <routing-discussion.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/routing-discussion>, <mailto:routing-discussion-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/routing-discussion/>
List-Post: <mailto:routing-discussion@ietf.org>
List-Help: <mailto:routing-discussion-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/routing-discussion>, <mailto:routing-discussion-request@ietf.org?subject=subscribe>
X-List-Received-Date: Wed, 10 Dec 2014 10:23:07 -0000

Lloyd

You run a network these days, what error rates are you actually measuring?

Stewart

On 10/12/2014 10:01, l.wood@surrey.ac.uk wrote:
> Of course the tunnellers are happy with a zero checksum. The pollution caused by missent corrupted ipv6 packets evading checks elsewhere does not affect them.
>
> Congestion is not a problem for tunnellers either. Like zero checksums, any congestion problem caused by a tunnel is just not the tunnel's problem. Why should the tunneller have to consider congestion? Or zero checksums? Or anything that impedes tunnel performance?
>
> The tragedy of the commons, in action.
>
> Lloyd Wood
> http://about.me/lloydwood
> ________________________________________
> From: routing-discussion <routing-discussion-bounces@ietf.org> on behalf of Stewart Bryant <stbryant@cisco.com>
> Sent: Wednesday, 10 December 2014 9:53:12 AM
> To: Alia Atlas; routing-discussion@ietf.org
> Subject: Re: routing area design team on dataplane encapsulation considerations
>
> Alia
>
> On 09/12/2014 22:46, Alia Atlas wrote:
>> * IPv6 header protection (non-zero UDP checksum over IPv6 issue)
> I am not sure if it is the non-zero UDP checksum over IPv6 issue, or
> the zeroUDP checksum over IPv6 issue.
>
> Most people doing tunneling seem quite happy with zero but get pushback
> from the transport area.
>
> Perhaps the topic is really
>
> * IPv6 header protection (UDP checksum issue)
>
> - Stewart
>
>
> _______________________________________________
> routing-discussion mailing list
> routing-discussion@ietf.org
> https://www.ietf.org/mailman/listinfo/routing-discussion
>


-- 
For corporate legal information go to:

http://www.cisco.com/web/about/doing_business/legal/cri/index.html


From nobody Wed Dec 10 02:31:10 2014
Return-Path: <l.wood@surrey.ac.uk>
X-Original-To: routing-discussion@ietfa.amsl.com
Delivered-To: routing-discussion@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id BCA9A1A19F8 for <routing-discussion@ietfa.amsl.com>; Wed, 10 Dec 2014 02:31:07 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -4.202
X-Spam-Level: 
X-Spam-Status: No, score=-4.202 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RCVD_IN_DNSWL_MED=-2.3, SPF_HELO_PASS=-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 77XhZFxmU0Ic for <routing-discussion@ietfa.amsl.com>; Wed, 10 Dec 2014 02:31:05 -0800 (PST)
Received: from mail1.bemta14.messagelabs.com (mail1.bemta14.messagelabs.com [193.109.254.119]) (using TLSv1.2 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 2523E1A064C for <routing-discussion@ietf.org>; Wed, 10 Dec 2014 02:31:04 -0800 (PST)
Received: from [193.109.255.147] by server-15.bemta-14.messagelabs.com id 70/74-02699-5E028845; Wed, 10 Dec 2014 10:31:01 +0000
X-Env-Sender: l.wood@surrey.ac.uk
X-Msg-Ref: server-16.tower-72.messagelabs.com!1418207460!14858375!1
X-Originating-IP: [131.227.200.39]
X-StarScan-Received: 
X-StarScan-Version: 6.12.5; banners=-,-,-
X-VirusChecked: Checked
Received: (qmail 10843 invoked from network); 10 Dec 2014 10:31:01 -0000
Received: from exht012p.surrey.ac.uk (HELO EXHT012P.surrey.ac.uk) (131.227.200.39) by server-16.tower-72.messagelabs.com with AES128-SHA encrypted SMTP; 10 Dec 2014 10:31:01 -0000
Received: from EXHY012V.surrey.ac.uk (131.227.201.103) by EXHT012P.surrey.ac.uk (131.227.200.39) with Microsoft SMTP Server (TLS) id 8.3.348.2; Wed, 10 Dec 2014 10:31:00 +0000
Received: from emea01-db3-obe.outbound.protection.outlook.com (131.227.201.241) by EXHY012v.surrey.ac.uk (131.227.201.103) with Microsoft SMTP Server (TLS) id 14.3.195.1; Wed, 10 Dec 2014 10:31:00 +0000
Received: from DB4PR06MB457.eurprd06.prod.outlook.com (10.141.238.15) by DB4PR06MB460.eurprd06.prod.outlook.com (10.141.238.24) with Microsoft SMTP Server (TLS) id 15.1.31.17; Wed, 10 Dec 2014 10:30:59 +0000
Received: from DB4PR06MB457.eurprd06.prod.outlook.com ([10.141.238.15]) by DB4PR06MB457.eurprd06.prod.outlook.com ([10.141.238.15]) with mapi id 15.01.0031.000; Wed, 10 Dec 2014 10:30:59 +0000
From: <l.wood@surrey.ac.uk>
To: <akatlas@gmail.com>, <routing-discussion@ietf.org>, <stbryant@cisco.com>
Subject: Re: routing area design team on dataplane encapsulation considerations
Thread-Topic: routing area design team on dataplane encapsulation considerations
Thread-Index: AQHQFAI+mxeM7C5mI06ufRYYSYZE2pyH3cwAgABL+5+AAHTBgIAAAF9W
Date: Wed, 10 Dec 2014 10:30:59 +0000
Message-ID: <DB4PR06MB4578A186E17D4EFC1C4180DAD620@DB4PR06MB457.eurprd06.prod.outlook.com>
References: <CAG4d1rd60hK8=WtYw-nid_Z7Z8+TvdzA52fNx3pFjND+eDWAfA@mail.gmail.com>,  <54877D58.9050002@cisco.com> <DB4PR06MB457D1FCFF0FBBA25E7A4EC3AD620@DB4PR06MB457.eurprd06.prod.outlook.com>, <54881F05.3030907@cisco.com>
In-Reply-To: <54881F05.3030907@cisco.com>
Accept-Language: en-AU, en-US
Content-Language: en-US
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
x-originating-ip: [124.168.9.252]
x-microsoft-antispam: BCL:0;PCL:0;RULEID:;SRVR:DB4PR06MB460;
x-exchange-antispam-report-test: UriScan:;
x-exchange-antispam-report-cfa-test: BCL:0;PCL:0;RULEID:;SRVR:DB4PR06MB460;
x-forefront-prvs: 0421BF7135
x-forefront-antispam-report: SFV:NSPM; SFS:(10019020)(6009001)(24454002)(479174003)(199003)(377454003)(54164003)(189002)(51704005)(93886004)(50986999)(105586002)(54206007)(107046002)(21056001)(107886001)(92566001)(86362001)(15395725005)(19580405001)(19580395003)(76176999)(54356999)(54606007)(74482002)(2656002)(87936001)(46102003)(122556002)(31966008)(101416001)(106116001)(15975445007)(102836002)(33656002)(76576001)(15198665003)(40100003)(74316001)(62966003)(97736003)(120916001)(64706001)(20776003)(77156002)(4396001)(1720100001)(106356001)(77096005)(68736005)(2501002)(99396003)(66066001); DIR:OUT; SFP:1102; SCL:1; SRVR:DB4PR06MB460; H:DB4PR06MB457.eurprd06.prod.outlook.com; FPR:; SPF:None; MLV:sfv; PTR:InfoNoRecords; A:1; MX:1; LANG:en; 
Content-Type: text/plain; charset="iso-8859-1"
Content-Transfer-Encoding: quoted-printable
MIME-Version: 1.0
X-OrganizationHeadersPreserved: DB4PR06MB460.eurprd06.prod.outlook.com
X-CrossPremisesHeadersFiltered: EXHY012v.surrey.ac.uk
Archived-At: http://mailarchive.ietf.org/arch/msg/routing-discussion/0mSEknIBzHz3innPZOKKni9K5bc
X-BeenThere: routing-discussion@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: Routing Area General mailing list <routing-discussion.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/routing-discussion>, <mailto:routing-discussion-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/routing-discussion/>
List-Post: <mailto:routing-discussion@ietf.org>
List-Help: <mailto:routing-discussion-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/routing-discussion>, <mailto:routing-discussion-request@ietf.org?subject=subscribe>
X-List-Received-Date: Wed, 10 Dec 2014 10:31:07 -0000

well, it's an IPv4 network.

because customers don't require or demand IPv6.

(see Jonathan Stone's papers for some large-scale IPv4 measurements. yes, y=
ou can quibble about whether software and hardware has improved in reliabil=
ity thanks to all of the ongoing engineering and lessons learned - and who =
is maintaining cef these days? - but the papers are a handy existence proof=
 of the problem.)
________________________________________
From: Stewart Bryant <stbryant@cisco.com>
Sent: Wednesday, 10 December 2014 9:23:01 PM
To: Wood L  Dr (Electronic Eng); akatlas@gmail.com; routing-discussion@ietf=
.org
Subject: Re: routing area design team on dataplane encapsulation considerat=
ions

Lloyd

You run a network these days, what error rates are you actually measuring?

Stewart

On 10/12/2014 10:01, l.wood@surrey.ac.uk wrote:
> Of course the tunnellers are happy with a zero checksum. The pollution ca=
used by missent corrupted ipv6 packets evading checks elsewhere does not af=
fect them.
>
> Congestion is not a problem for tunnellers either. Like zero checksums, a=
ny congestion problem caused by a tunnel is just not the tunnel's problem. =
Why should the tunneller have to consider congestion? Or zero checksums? Or=
 anything that impedes tunnel performance?
>
> The tragedy of the commons, in action.
>
> Lloyd Wood
> http://about.me/lloydwood
> ________________________________________
> From: routing-discussion <routing-discussion-bounces@ietf.org> on behalf =
of Stewart Bryant <stbryant@cisco.com>
> Sent: Wednesday, 10 December 2014 9:53:12 AM
> To: Alia Atlas; routing-discussion@ietf.org
> Subject: Re: routing area design team on dataplane encapsulation consider=
ations
>
> Alia
>
> On 09/12/2014 22:46, Alia Atlas wrote:
>> * IPv6 header protection (non-zero UDP checksum over IPv6 issue)
> I am not sure if it is the non-zero UDP checksum over IPv6 issue, or
> the zeroUDP checksum over IPv6 issue.
>
> Most people doing tunneling seem quite happy with zero but get pushback
> from the transport area.
>
> Perhaps the topic is really
>
> * IPv6 header protection (UDP checksum issue)
>
> - Stewart
>
>
> _______________________________________________
> routing-discussion mailing list
> routing-discussion@ietf.org
> https://www.ietf.org/mailman/listinfo/routing-discussion
>


--
For corporate legal information go to:

http://www.cisco.com/web/about/doing_business/legal/cri/index.html


From nobody Wed Dec 10 03:37:31 2014
Return-Path: <l.wood@surrey.ac.uk>
X-Original-To: routing-discussion@ietfa.amsl.com
Delivered-To: routing-discussion@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 79F731A1B3B for <routing-discussion@ietfa.amsl.com>; Wed, 10 Dec 2014 03:37:29 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.902
X-Spam-Level: 
X-Spam-Status: No, score=-1.902 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RCVD_IN_DNSWL_NONE=-0.0001, SPF_HELO_PASS=-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 pztsd6IYoczX for <routing-discussion@ietfa.amsl.com>; Wed, 10 Dec 2014 03:37:27 -0800 (PST)
Received: from mail1.bemta5.messagelabs.com (mail1.bemta5.messagelabs.com [195.245.231.143]) (using TLSv1.2 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id D856C1A1B17 for <routing-discussion@ietf.org>; Wed, 10 Dec 2014 03:37:26 -0800 (PST)
Received: from [85.158.136.51] by server-7.bemta-5.messagelabs.com id E1/34-31453-57038845; Wed, 10 Dec 2014 11:37:25 +0000
X-Env-Sender: l.wood@surrey.ac.uk
X-Msg-Ref: server-14.tower-49.messagelabs.com!1418211394!25033089!6
X-Originating-IP: [131.227.200.35]
X-StarScan-Received: 
X-StarScan-Version: 6.12.5; banners=-,-,-
X-VirusChecked: Checked
Received: (qmail 21780 invoked from network); 10 Dec 2014 11:37:24 -0000
Received: from exht021p.surrey.ac.uk (HELO EXHT021P.surrey.ac.uk) (131.227.200.35) by server-14.tower-49.messagelabs.com with AES128-SHA encrypted SMTP; 10 Dec 2014 11:37:24 -0000
Received: from EXHY012V.surrey.ac.uk (131.227.201.103) by EXHT021P.surrey.ac.uk (131.227.200.35) with Microsoft SMTP Server (TLS) id 8.3.348.2; Wed, 10 Dec 2014 11:37:14 +0000
Received: from emea01-db3-obe.outbound.protection.outlook.com (131.227.201.241) by EXHY012v.surrey.ac.uk (131.227.201.103) with Microsoft SMTP Server (TLS) id 14.3.195.1; Wed, 10 Dec 2014 11:37:14 +0000
Received: from DB4PR06MB457.eurprd06.prod.outlook.com (10.141.238.15) by DB4PR06MB457.eurprd06.prod.outlook.com (10.141.238.15) with Microsoft SMTP Server (TLS) id 15.1.31.17; Wed, 10 Dec 2014 11:37:13 +0000
Received: from DB4PR06MB457.eurprd06.prod.outlook.com ([10.141.238.15]) by DB4PR06MB457.eurprd06.prod.outlook.com ([10.141.238.15]) with mapi id 15.01.0031.000; Wed, 10 Dec 2014 11:37:13 +0000
From: <l.wood@surrey.ac.uk>
To: <akatlas@gmail.com>, <routing-discussion@ietf.org>, <stbryant@cisco.com>
Subject: Re: routing area design team on dataplane encapsulation considerations
Thread-Topic: routing area design team on dataplane encapsulation considerations
Thread-Index: AQHQFAI+mxeM7C5mI06ufRYYSYZE2pyH3cwAgADUTV8=
Date: Wed, 10 Dec 2014 11:37:12 +0000
Message-ID: <DB4PR06MB457F278EAF9C84BCA20E665AD620@DB4PR06MB457.eurprd06.prod.outlook.com>
References: <CAG4d1rd60hK8=WtYw-nid_Z7Z8+TvdzA52fNx3pFjND+eDWAfA@mail.gmail.com>,  <54877D58.9050002@cisco.com>
In-Reply-To: <54877D58.9050002@cisco.com>
Accept-Language: en-AU, en-US
Content-Language: en-US
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
x-originating-ip: [124.168.9.252]
x-microsoft-antispam: BCL:0;PCL:0;RULEID:;SRVR:DB4PR06MB457;
x-exchange-antispam-report-test: UriScan:;
x-exchange-antispam-report-cfa-test: BCL:0;PCL:0;RULEID:;SRVR:DB4PR06MB457;
x-forefront-prvs: 0421BF7135
x-forefront-antispam-report: SFV:NSPM; SFS:(10019020)(6009001)(189002)(199003)(24454002)(377454003)(479174003)(15975445007)(76576001)(92566001)(106356001)(74316001)(120916001)(101416001)(54206007)(1720100001)(15395725005)(77096005)(102836002)(68736005)(77156002)(15198665003)(62966003)(107046002)(107886001)(86362001)(40100003)(21056001)(64706001)(20776003)(97736003)(122556002)(46102003)(4396001)(74482002)(99396003)(105586002)(76176999)(106116001)(19580405001)(19580395003)(33656002)(2656002)(54356999)(50986999)(31966008)(54606007)(87936001)(66066001); DIR:OUT; SFP:1102; SCL:1; SRVR:DB4PR06MB457; H:DB4PR06MB457.eurprd06.prod.outlook.com; FPR:; SPF:None; MLV:sfv; PTR:InfoNoRecords; MX:1; A:1; LANG:en; 
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: quoted-printable
MIME-Version: 1.0
X-OrganizationHeadersPreserved: DB4PR06MB457.eurprd06.prod.outlook.com
X-CrossPremisesHeadersFiltered: EXHY012v.surrey.ac.uk
Archived-At: http://mailarchive.ietf.org/arch/msg/routing-discussion/ZtP-QKyQkPZtEyOwDqUFnapW-aQ
X-BeenThere: routing-discussion@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: Routing Area General mailing list <routing-discussion.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/routing-discussion>, <mailto:routing-discussion-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/routing-discussion/>
List-Post: <mailto:routing-discussion@ietf.org>
List-Help: <mailto:routing-discussion-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/routing-discussion>, <mailto:routing-discussion-request@ietf.org?subject=subscribe>
X-List-Received-Date: Wed, 10 Dec 2014 11:37:29 -0000

It's an issue with zero checksums, ie not hsving a functional working check=
sum. Non-zero checksums are not an issue.

It's a bit like 60s car manufacturers saying 'do we really need to add seat=
belts? They're expensive.' Seatbelts are clearly an issue! Like creationism=
 and evolution, it's not clearcut. We should teach the controversy!

Lloyd Wood
http://about.me/lloydwood
________________________________________
From: routing-discussion <routing-discussion-bounces@ietf.org> on behalf of=
 Stewart Bryant <stbryant@cisco.com>
Sent: Wednesday, 10 December 2014 9:53:12 AM
To: Alia Atlas; routing-discussion@ietf.org
Subject: Re: routing area design team on dataplane encapsulation considerat=
ions

Alia

On 09/12/2014 22:46, Alia Atlas wrote:
> * IPv6 header protection (non-zero UDP checksum over IPv6 issue)
I am not sure if it is the non-zero UDP checksum over IPv6 issue, or
the zeroUDP checksum over IPv6 issue.

Most people doing tunneling seem quite happy with zero but get pushback
from the transport area.

Perhaps the topic is really

* IPv6 header protection (UDP checksum issue)

- Stewart


_______________________________________________
routing-discussion mailing list
routing-discussion@ietf.org
https://www.ietf.org/mailman/listinfo/routing-discussion


From nobody Wed Dec 10 04:08:12 2014
Return-Path: <stbryant@cisco.com>
X-Original-To: routing-discussion@ietfa.amsl.com
Delivered-To: routing-discussion@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 5D5561A870D for <routing-discussion@ietfa.amsl.com>; Wed, 10 Dec 2014 04:08:07 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -14.511
X-Spam-Level: 
X-Spam-Status: No, score=-14.511 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, RCVD_IN_DNSWL_HI=-5, SPF_PASS=-0.001, T_RP_MATCHES_RCVD=-0.01, USER_IN_DEF_DKIM_WL=-7.5] 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 T9QhDfcwvKm6 for <routing-discussion@ietfa.amsl.com>; Wed, 10 Dec 2014 04:08:00 -0800 (PST)
Received: from aer-iport-4.cisco.com (aer-iport-4.cisco.com [173.38.203.54]) (using TLSv1 with cipher RC4-SHA (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 2AB581A8713 for <routing-discussion@ietf.org>; Wed, 10 Dec 2014 04:07:58 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=cisco.com; i=@cisco.com; l=3193; q=dns/txt; s=iport; t=1418213278; x=1419422878; h=message-id:date:from:reply-to:mime-version:to:subject: references:in-reply-to:content-transfer-encoding; bh=q6L2mu4slnC+GIy76cCFtVwV1dBVSDtLF/lt02XprMk=; b=mkKy1Bnbl/OdoWMqX8I7/gSBNmvDl9VaNpIcfRWKIsBbN0aYrIdnNC4j kTlxmpuoSRKz1vtyZje4XkF+ppreptUg8sa/7el9SeMFfTGxkZBhiVaBZ 15KnwPt/T8MXjsG244UgO4OORV/CNtm0Yq4Gn1IF4wMpwARtBs3o79c+v I=;
X-IronPort-AV: E=Sophos;i="5.07,552,1413244800"; d="scan'208";a="264137191"
Received: from aer-iport-nat.cisco.com (HELO aer-core-1.cisco.com) ([173.38.203.22]) by aer-iport-4.cisco.com with ESMTP; 10 Dec 2014 12:07:56 +0000
Received: from [10.61.99.142] (dhcp-10-61-99-142.cisco.com [10.61.99.142]) by aer-core-1.cisco.com (8.14.5/8.14.5) with ESMTP id sBAC7tBR009065; Wed, 10 Dec 2014 12:07:56 GMT
Message-ID: <5488379A.2000807@cisco.com>
Date: Wed, 10 Dec 2014 12:07:54 +0000
From: Stewart Bryant <stbryant@cisco.com>
User-Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.9; rv:24.0) Gecko/20100101 Thunderbird/24.6.0
MIME-Version: 1.0
To: l.wood@surrey.ac.uk, akatlas@gmail.com, routing-discussion@ietf.org
Subject: Re: routing area design team on dataplane encapsulation considerations
References: <CAG4d1rd60hK8=WtYw-nid_Z7Z8+TvdzA52fNx3pFjND+eDWAfA@mail.gmail.com>,  <54877D58.9050002@cisco.com> <DB4PR06MB457D1FCFF0FBBA25E7A4EC3AD620@DB4PR06MB457.eurprd06.prod.outlook.com>, <54881F05.3030907@cisco.com> <DB4PR06MB4578A186E17D4EFC1C4180DAD620@DB4PR06MB457.eurprd06.prod.outlook.com>
In-Reply-To: <DB4PR06MB4578A186E17D4EFC1C4180DAD620@DB4PR06MB457.eurprd06.prod.outlook.com>
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit
Archived-At: http://mailarchive.ietf.org/arch/msg/routing-discussion/mXT-zViLBmA8xvJq20NkGhDxe_0
X-BeenThere: routing-discussion@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
Reply-To: stbryant@cisco.com
List-Id: Routing Area General mailing list <routing-discussion.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/routing-discussion>, <mailto:routing-discussion-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/routing-discussion/>
List-Post: <mailto:routing-discussion@ietf.org>
List-Help: <mailto:routing-discussion-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/routing-discussion>, <mailto:routing-discussion-request@ietf.org?subject=subscribe>
X-List-Received-Date: Wed, 10 Dec 2014 12:08:07 -0000

Lloyd as a first approximation what do your IP header checksum error 
rates look like.

The old paper that you point to is not representative of modern routing 
technology
and I would like to see some new modern numbers relevant to router to 
router traffic
which is what we are talking about.

Stewart

On 10/12/2014 10:30, l.wood@surrey.ac.uk wrote:
> well, it's an IPv4 network.
>
> because customers don't require or demand IPv6.
>
> (see Jonathan Stone's papers for some large-scale IPv4 measurements. yes, you can quibble about whether software and hardware has improved in reliability thanks to all of the ongoing engineering and lessons learned - and who is maintaining cef these days? - but the papers are a handy existence proof of the problem.)
> ________________________________________
> From: Stewart Bryant <stbryant@cisco.com>
> Sent: Wednesday, 10 December 2014 9:23:01 PM
> To: Wood L  Dr (Electronic Eng); akatlas@gmail.com; routing-discussion@ietf.org
> Subject: Re: routing area design team on dataplane encapsulation considerations
>
> Lloyd
>
> You run a network these days, what error rates are you actually measuring?
>
> Stewart
>
> On 10/12/2014 10:01, l.wood@surrey.ac.uk wrote:
>> Of course the tunnellers are happy with a zero checksum. The pollution caused by missent corrupted ipv6 packets evading checks elsewhere does not affect them.
>>
>> Congestion is not a problem for tunnellers either. Like zero checksums, any congestion problem caused by a tunnel is just not the tunnel's problem. Why should the tunneller have to consider congestion? Or zero checksums? Or anything that impedes tunnel performance?
>>
>> The tragedy of the commons, in action.
>>
>> Lloyd Wood
>> http://about.me/lloydwood
>> ________________________________________
>> From: routing-discussion <routing-discussion-bounces@ietf.org> on behalf of Stewart Bryant <stbryant@cisco.com>
>> Sent: Wednesday, 10 December 2014 9:53:12 AM
>> To: Alia Atlas; routing-discussion@ietf.org
>> Subject: Re: routing area design team on dataplane encapsulation considerations
>>
>> Alia
>>
>> On 09/12/2014 22:46, Alia Atlas wrote:
>>> * IPv6 header protection (non-zero UDP checksum over IPv6 issue)
>> I am not sure if it is the non-zero UDP checksum over IPv6 issue, or
>> the zeroUDP checksum over IPv6 issue.
>>
>> Most people doing tunneling seem quite happy with zero but get pushback
>> from the transport area.
>>
>> Perhaps the topic is really
>>
>> * IPv6 header protection (UDP checksum issue)
>>
>> - Stewart
>>
>>
>> _______________________________________________
>> routing-discussion mailing list
>> routing-discussion@ietf.org
>> https://www.ietf.org/mailman/listinfo/routing-discussion
>>
>
> --
> For corporate legal information go to:
>
> http://www.cisco.com/web/about/doing_business/legal/cri/index.html
>
> _______________________________________________
> routing-discussion mailing list
> routing-discussion@ietf.org
> https://www.ietf.org/mailman/listinfo/routing-discussion
>


-- 
For corporate legal information go to:

http://www.cisco.com/web/about/doing_business/legal/cri/index.html


From nobody Wed Dec 10 04:15:17 2014
Return-Path: <stbryant@cisco.com>
X-Original-To: routing-discussion@ietfa.amsl.com
Delivered-To: routing-discussion@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 51C9C1A1B8B for <routing-discussion@ietfa.amsl.com>; Wed, 10 Dec 2014 04:15:13 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -14.511
X-Spam-Level: 
X-Spam-Status: No, score=-14.511 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, RCVD_IN_DNSWL_HI=-5, SPF_PASS=-0.001, T_RP_MATCHES_RCVD=-0.01, USER_IN_DEF_DKIM_WL=-7.5] 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 22bpViZAdmEo for <routing-discussion@ietfa.amsl.com>; Wed, 10 Dec 2014 04:15:07 -0800 (PST)
Received: from aer-iport-2.cisco.com (aer-iport-2.cisco.com [173.38.203.52]) (using TLSv1 with cipher RC4-SHA (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 5902E1A1B65 for <routing-discussion@ietf.org>; Wed, 10 Dec 2014 04:15:07 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=cisco.com; i=@cisco.com; l=1970; q=dns/txt; s=iport; t=1418213707; x=1419423307; h=message-id:date:from:reply-to:mime-version:to:subject: references:in-reply-to:content-transfer-encoding; bh=b83N8x+t09KTIR53TfdKCSxHVAOBYIXHFnLcsd9gplE=; b=Csf7KXuLJDFA9FcKUelpshjgkdPEGcYHDwf3thQT0bEo7bOHroVU2kEs t5NsybSAukXn9u3h+pF9HsaD6KKLqG7SJ375HNPxxBllFEkoljx3FZbMX ol3eDA70nBKw7VeQAJ6NmJ/SrdPht2yjuKfdNDF4UXgsERVm5rYKbcLEn o=;
X-IronPort-AV: E=Sophos;i="5.07,552,1413244800"; d="scan'208";a="268293846"
Received: from aer-iport-nat.cisco.com (HELO aer-core-1.cisco.com) ([173.38.203.22]) by aer-iport-2.cisco.com with ESMTP; 10 Dec 2014 12:15:05 +0000
Received: from [10.61.99.142] (dhcp-10-61-99-142.cisco.com [10.61.99.142]) by aer-core-1.cisco.com (8.14.5/8.14.5) with ESMTP id sBACF5Xx023844; Wed, 10 Dec 2014 12:15:05 GMT
Message-ID: <54883947.8000302@cisco.com>
Date: Wed, 10 Dec 2014 12:15:03 +0000
From: Stewart Bryant <stbryant@cisco.com>
User-Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.9; rv:24.0) Gecko/20100101 Thunderbird/24.6.0
MIME-Version: 1.0
To: l.wood@surrey.ac.uk, akatlas@gmail.com, routing-discussion@ietf.org
Subject: Re: routing area design team on dataplane encapsulation considerations
References: <CAG4d1rd60hK8=WtYw-nid_Z7Z8+TvdzA52fNx3pFjND+eDWAfA@mail.gmail.com>,  <54877D58.9050002@cisco.com> <DB4PR06MB457F278EAF9C84BCA20E665AD620@DB4PR06MB457.eurprd06.prod.outlook.com>
In-Reply-To: <DB4PR06MB457F278EAF9C84BCA20E665AD620@DB4PR06MB457.eurprd06.prod.outlook.com>
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit
Archived-At: http://mailarchive.ietf.org/arch/msg/routing-discussion/zcHdI172n3372f0a9gJgbnNCNCQ
X-BeenThere: routing-discussion@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
Reply-To: stbryant@cisco.com
List-Id: Routing Area General mailing list <routing-discussion.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/routing-discussion>, <mailto:routing-discussion-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/routing-discussion/>
List-Post: <mailto:routing-discussion@ietf.org>
List-Help: <mailto:routing-discussion-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/routing-discussion>, <mailto:routing-discussion-request@ietf.org?subject=subscribe>
X-List-Received-Date: Wed, 10 Dec 2014 12:15:13 -0000

Lloyd

Let's have a current data driven approach to this. You are in a position to
look inside an NMS and tell us what modern data error rates are.

A counter existence proof is MPLS networking which acts at the same
layer that we are discussing and does not seem to have a misdelivery
or "not in table drop rate" that is getting on anyone's radar. Certainly
no one is asking us to upgrade MPLS to add this protection.

- Stewart

On 10/12/2014 11:37, l.wood@surrey.ac.uk wrote:
> It's an issue with zero checksums, ie not hsving a functional working checksum. Non-zero checksums are not an issue.
>
> It's a bit like 60s car manufacturers saying 'do we really need to add seatbelts? They're expensive.' Seatbelts are clearly an issue! Like creationism and evolution, it's not clearcut. We should teach the controversy!
>
> Lloyd Wood
> http://about.me/lloydwood
> ________________________________________
> From: routing-discussion <routing-discussion-bounces@ietf.org> on behalf of Stewart Bryant <stbryant@cisco.com>
> Sent: Wednesday, 10 December 2014 9:53:12 AM
> To: Alia Atlas; routing-discussion@ietf.org
> Subject: Re: routing area design team on dataplane encapsulation considerations
>
> Alia
>
> On 09/12/2014 22:46, Alia Atlas wrote:
>> * IPv6 header protection (non-zero UDP checksum over IPv6 issue)
> I am not sure if it is the non-zero UDP checksum over IPv6 issue, or
> the zeroUDP checksum over IPv6 issue.
>
> Most people doing tunneling seem quite happy with zero but get pushback
> from the transport area.
>
> Perhaps the topic is really
>
> * IPv6 header protection (UDP checksum issue)
>
> - Stewart
>
>
> _______________________________________________
> routing-discussion mailing list
> routing-discussion@ietf.org
> https://www.ietf.org/mailman/listinfo/routing-discussion
>


-- 
For corporate legal information go to:

http://www.cisco.com/web/about/doing_business/legal/cri/index.html


From nobody Wed Dec 10 05:25:09 2014
Return-Path: <l.wood@surrey.ac.uk>
X-Original-To: routing-discussion@ietfa.amsl.com
Delivered-To: routing-discussion@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 626E61A89ED for <routing-discussion@ietfa.amsl.com>; Wed, 10 Dec 2014 05:25:05 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.602
X-Spam-Level: 
X-Spam-Status: No, score=-2.602 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RCVD_IN_DNSWL_LOW=-0.7, SPF_HELO_PASS=-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 VtUEQvfDma23 for <routing-discussion@ietfa.amsl.com>; Wed, 10 Dec 2014 05:25:01 -0800 (PST)
Received: from mail1.bemta3.messagelabs.com (mail1.bemta3.messagelabs.com [195.245.230.172]) (using TLSv1.2 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 4F2821A89A5 for <routing-discussion@ietf.org>; Wed, 10 Dec 2014 05:24:59 -0800 (PST)
Received: from [195.245.230.131] by server-12.bemta-3.messagelabs.com id 70/D1-26740-9A948845; Wed, 10 Dec 2014 13:24:57 +0000
X-Env-Sender: l.wood@surrey.ac.uk
X-Msg-Ref: server-8.tower-78.messagelabs.com!1418217895!34241101!1
X-Originating-IP: [131.227.200.39]
X-StarScan-Received: 
X-StarScan-Version: 6.12.5; banners=-,-,-
X-VirusChecked: Checked
Received: (qmail 23515 invoked from network); 10 Dec 2014 13:24:56 -0000
Received: from exht012p.surrey.ac.uk (HELO EXHT012P.surrey.ac.uk) (131.227.200.39) by server-8.tower-78.messagelabs.com with AES128-SHA encrypted SMTP; 10 Dec 2014 13:24:56 -0000
Received: from EXHY022V.surrey.ac.uk (131.227.201.104) by EXHT012P.surrey.ac.uk (131.227.200.39) with Microsoft SMTP Server (TLS) id 8.3.348.2; Wed, 10 Dec 2014 13:24:54 +0000
Received: from emea01-db3-obe.outbound.protection.outlook.com (131.227.201.241) by EXHY022v.surrey.ac.uk (131.227.201.104) with Microsoft SMTP Server (TLS) id 14.3.195.1; Wed, 10 Dec 2014 13:24:54 +0000
Received: from DB4PR06MB457.eurprd06.prod.outlook.com (10.141.238.15) by DB4PR06MB458.eurprd06.prod.outlook.com (10.141.238.19) with Microsoft SMTP Server (TLS) id 15.1.31.17; Wed, 10 Dec 2014 13:24:52 +0000
Received: from DB4PR06MB457.eurprd06.prod.outlook.com ([10.141.238.15]) by DB4PR06MB457.eurprd06.prod.outlook.com ([10.141.238.15]) with mapi id 15.01.0031.000; Wed, 10 Dec 2014 13:24:52 +0000
From: <l.wood@surrey.ac.uk>
To: <akatlas@gmail.com>, <routing-discussion@ietf.org>, <stbryant@cisco.com>
Subject: Re: routing area design team on dataplane encapsulation considerations
Thread-Topic: routing area design team on dataplane encapsulation considerations
Thread-Index: AQHQFAI+mxeM7C5mI06ufRYYSYZE2pyH3cwAgADUTV+AAAu8gIAACL4O
Date: Wed, 10 Dec 2014 13:24:52 +0000
Message-ID: <1418217891573.89120@surrey.ac.uk>
References: <CAG4d1rd60hK8=WtYw-nid_Z7Z8+TvdzA52fNx3pFjND+eDWAfA@mail.gmail.com>,  <54877D58.9050002@cisco.com> <DB4PR06MB457F278EAF9C84BCA20E665AD620@DB4PR06MB457.eurprd06.prod.outlook.com>, <54883947.8000302@cisco.com>
In-Reply-To: <54883947.8000302@cisco.com>
Accept-Language: en-AU, en-US
Content-Language: en-US
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
x-originating-ip: [122.200.59.254]
x-microsoft-antispam: BCL:0;PCL:0;RULEID:;SRVR:DB4PR06MB458;
x-exchange-antispam-report-test: UriScan:;
x-exchange-antispam-report-cfa-test: BCL:0;PCL:0;RULEID:;SRVR:DB4PR06MB458;
x-forefront-prvs: 0421BF7135
x-forefront-antispam-report: SFV:NSPM; SFS:(10019020)(6009001)(189002)(377454003)(479174003)(24454002)(243025005)(199003)(51704005)(66066001)(2656002)(20776003)(40100003)(77096005)(76176999)(105586002)(107886001)(107046002)(21056001)(2501002)(36756003)(64706001)(102836002)(1720100001)(99396003)(15975445007)(120916001)(86362001)(122556002)(87936001)(68736005)(106116001)(106356001)(15395725005)(50986999)(4396001)(62966003)(77156002)(54356999)(46102003)(74482002)(15198665003)(19580405001)(19580395003)(117636001)(92566001)(101416001)(31966008)(561924002)(93886004)(97736003); DIR:OUT; SFP:1102; SCL:1; SRVR:DB4PR06MB458; H:DB4PR06MB457.eurprd06.prod.outlook.com; FPR:; SPF:None; MLV:sfv; PTR:InfoNoRecords; MX:1; A:1; LANG:en; 
Content-Type: text/plain; charset="iso-8859-1"
Content-Transfer-Encoding: quoted-printable
MIME-Version: 1.0
X-OrganizationHeadersPreserved: DB4PR06MB458.eurprd06.prod.outlook.com
X-CrossPremisesHeadersFiltered: EXHY022v.surrey.ac.uk
Archived-At: http://mailarchive.ietf.org/arch/msg/routing-discussion/oKt2ElDp1OuQuAhWEvvVHMCP248
X-BeenThere: routing-discussion@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: Routing Area General mailing list <routing-discussion.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/routing-discussion>, <mailto:routing-discussion-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/routing-discussion/>
List-Post: <mailto:routing-discussion@ietf.org>
List-Help: <mailto:routing-discussion-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/routing-discussion>, <mailto:routing-discussion-request@ietf.org?subject=subscribe>
X-List-Received-Date: Wed, 10 Dec 2014 13:25:06 -0000

Stewart,=0A=
=0A=
Who needs an NMS? Let's go old school.=0A=
TCP and UDP have equivalent pseudo-header+payload ones complement checksums=
. So data from TCP can be considered as somewhat equivalent as the technolo=
gy is the same, and TCP is somewhat better instrumented and monitored than =
UDP is.=0A=
=0A=
Below sample from two core switches, on tcp connections to them  (not, alas=
, through them) shows e.g. 10287 TCP checksum errors for 4.3 million TCP/IP=
 packets received. That would be an error rate of 0.24% - the other switch =
is 0.45% . Note the figure of e.g. 19458 no port - entirely possible someth=
ing inside the core network is trying a port that isn't there, but also pos=
sible corruption of port nos. These are firewalled core devices with limite=
d traffic to them, so I would consider this a best case, without throwing e=
dge device data into the mix.=0A=
=0A=
Extrapolating from TCP checksum rates to UDP checksum rates, from traffic t=
o to traffic through, and from v4 to v6 is left as an exercise for the read=
er. =0A=
=0A=
Incidentally, these rates pretty much match the 1 in 400 observation made e=
arly in Stone's SIGCOMM 2000 paper. 1:400 is 10,000:4,000,000=0A=
http://conferences.sigcomm.org/sigcomm/2000/conf/paper/sigcomm2000-9-1.pdf=
=0A=
Zut alors, quelle surprise, physics is still physics, this particular SIGCO=
MM paper is still valid.=0A=
Checksums fail because of corruption. But at least there's a checksum to ca=
tch the corruption. Sans checksums, the corruption is unnoticed. =0A=
=0A=
The main reason noone has seen misbehaviour with MPLS is because no-one is =
looking for or instrumenting for it. (Just like MPLS doesn't need TTL, beca=
use no-one ever sees MPLS routing loops, right?) Please go measure MPLS and=
 report back.=0A=
=0A=
Traversing over UDP, as suggested in draft-ietf-mpls-in-udp and draft-ietf-=
tsvwg-gre-in-udp-encap, increases the scope for corruption across a longer =
path, rather than individual links - and the UDP checksum is an important l=
ast check.=0A=
=0A=
SWT1#sh tcp stat=0A=
Rcvd: 4332545 Total, 19458 no port=0A=
      10287 checksum error, 4959 bad offset, 0 too short=0A=
      62946 packets (2289083 bytes) in sequence=0A=
      93 dup packets (19167 bytes)=0A=
      34 partially dup packets (1878 bytes)=0A=
      107 out-of-order packets (17980 bytes)=0A=
      8 packets (8 bytes) with data after window=0A=
      0 packets after close=0A=
      0 window probe packets, 614 window update packets=0A=
      682 dup ack packets, 0 ack packets with unsend data=0A=
      179823 ack packets (37459618 bytes)=0A=
Sent: 2049509 Total, 0 urgent packets=0A=
      1774234 control packets (including 345 retransmitted)=0A=
      249103 data packets (37439059 bytes)=0A=
      308 data packets (41767 bytes) retransmitted=0A=
      46 data packets (4876 bytes) fastretransmitted=0A=
      25718 ack only packets (3764 delayed)=0A=
      0 window probe packets, 104 window update packets=0A=
9649 Connections initiated, 1230 connections accepted, 10857 connections es=
tablished=0A=
1760675 Connections closed (including 30 dropped, 1749812 embryonic dropped=
)=0A=
653 Total rxmt timeout, 9 connections dropped in rxmt timeout=0A=
0 Keepalive timeout, 6 keepalive probe, 0 Connections dropped in keepalive=
=0A=
=0A=
=0A=
SWT2#sh tcp stat=0A=
Rcvd: 6370948 Total, 37608 no port=0A=
      28419 checksum error, 1749 bad offset, 0 too short=0A=
      181714 packets (3507560 bytes) in sequence=0A=
      130 dup packets (4925 bytes)=0A=
      164 partially dup packets (302 bytes)=0A=
      35 out-of-order packets (278 bytes)=0A=
      64 packets (4549 bytes) with data after window=0A=
      0 packets after close=0A=
      0 window probe packets, 2006 window update packets=0A=
      3865 dup ack packets, 0 ack packets with unsend data=0A=
      857922 ack packets (92503306 bytes)=0A=
Sent: 3793587 Total, 0 urgent packets=0A=
      2667720 control packets (including 215 retransmitted)=0A=
      1042867 data packets (92804839 bytes)=0A=
      1772 data packets (74842 bytes) retransmitted=0A=
      192 data packets (7176 bytes) fastretransmitted=0A=
      81025 ack only packets (15840 delayed)=0A=
      0 window probe packets, 19 window update packets=0A=
28735 Connections initiated, 5928 connections accepted, 34638 connections e=
stablished=0A=
2626485 Connections closed (including 1349 dropped, 2591827 embryonic dropp=
ed)=0A=
1987 Total rxmt timeout, 4 connections dropped in rxmt timeout=0A=
0 Keepalive timeout, 0 keepalive probe, 0 Connections dropped in keepalive=
=0A=
=0A=
Lloyd Wood=0A=
http://about.me/lloydwood=0A=
=0A=
error-free modern networking technology? ha.=0A=
________________________________________=0A=
From: Stewart Bryant <stbryant@cisco.com>=0A=
Sent: Wednesday, 10 December 2014 11:15 PM=0A=
To: Wood L  Dr (Electronic Eng); akatlas@gmail.com; routing-discussion@ietf=
.org=0A=
Subject: Re: routing area design team on dataplane encapsulation considerat=
ions=0A=
=0A=
Lloyd=0A=
=0A=
Let's have a current data driven approach to this. You are in a position to=
=0A=
look inside an NMS and tell us what modern data error rates are.=0A=
=0A=
A counter existence proof is MPLS networking which acts at the same=0A=
layer that we are discussing and does not seem to have a misdelivery=0A=
or "not in table drop rate" that is getting on anyone's radar. Certainly=0A=
no one is asking us to upgrade MPLS to add this protection.=0A=
=0A=
- Stewart=0A=
=0A=
On 10/12/2014 11:37, l.wood@surrey.ac.uk wrote:=0A=
> It's an issue with zero checksums, ie not hsving a functional working che=
cksum. Non-zero checksums are not an issue.=0A=
>=0A=
> It's a bit like 60s car manufacturers saying 'do we really need to add se=
atbelts? They're expensive.' Seatbelts are clearly an issue! Like creationi=
sm and evolution, it's not clearcut. We should teach the controversy!=0A=
>=0A=
> Lloyd Wood=0A=
> http://about.me/lloydwood=0A=
> ________________________________________=0A=
> From: routing-discussion <routing-discussion-bounces@ietf.org> on behalf =
of Stewart Bryant <stbryant@cisco.com>=0A=
> Sent: Wednesday, 10 December 2014 9:53:12 AM=0A=
> To: Alia Atlas; routing-discussion@ietf.org=0A=
> Subject: Re: routing area design team on dataplane encapsulation consider=
ations=0A=
>=0A=
> Alia=0A=
>=0A=
> On 09/12/2014 22:46, Alia Atlas wrote:=0A=
>> * IPv6 header protection (non-zero UDP checksum over IPv6 issue)=0A=
> I am not sure if it is the non-zero UDP checksum over IPv6 issue, or=0A=
> the zeroUDP checksum over IPv6 issue.=0A=
>=0A=
> Most people doing tunneling seem quite happy with zero but get pushback=
=0A=
> from the transport area.=0A=
>=0A=
> Perhaps the topic is really=0A=
>=0A=
> * IPv6 header protection (UDP checksum issue)=0A=
>=0A=
> - Stewart=0A=
>=0A=
>=0A=
> _______________________________________________=0A=
> routing-discussion mailing list=0A=
> routing-discussion@ietf.org=0A=
> https://www.ietf.org/mailman/listinfo/routing-discussion=0A=
>=0A=
=0A=
=0A=
--=0A=
For corporate legal information go to:=0A=
=0A=
http://www.cisco.com/web/about/doing_business/legal/cri/index.html=0A=
=0A=


From nobody Wed Dec 10 06:27:22 2014
Return-Path: <agmalis@gmail.com>
X-Original-To: routing-discussion@ietfa.amsl.com
Delivered-To: routing-discussion@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id A6FF81A9039 for <routing-discussion@ietfa.amsl.com>; Wed, 10 Dec 2014 06:27:19 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.999
X-Spam-Level: 
X-Spam-Status: No, score=-1.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, 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 IY02g1_FmyM8 for <routing-discussion@ietfa.amsl.com>; Wed, 10 Dec 2014 06:27:17 -0800 (PST)
Received: from mail-qc0-x22c.google.com (mail-qc0-x22c.google.com [IPv6:2607:f8b0:400d:c01::22c]) (using TLSv1 with cipher ECDHE-RSA-RC4-SHA (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id D16161A9024 for <routing-discussion@ietf.org>; Wed, 10 Dec 2014 06:27:16 -0800 (PST)
Received: by mail-qc0-f172.google.com with SMTP id m20so2223810qcx.31 for <routing-discussion@ietf.org>; Wed, 10 Dec 2014 06:27:16 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113;  h=mime-version:in-reply-to:references:from:date:message-id:subject:to :cc:content-type; bh=ZFgXjCRAh9nMfURy3HGxKZeLZrObjpLrIgRMJsqU+sk=; b=I97ZjZik0QNDZGUmLbEVymbZZvD6LEDnfgmIXv3KCk6U0Oqj6Sgxyi+N0tRlJER1Vz 9IhLd1v4C9N2xr/Bn3Ggcqjl1wWlZOAbS0M97lgctPJLzWN8K3R7a33oYA7gruHAXQ2p Jb6xFViG/WLIRa5HUtbIa5pGXS3leEdTpkdDvFCiRKZpIFn99kdXDeQDQfRq0OyCgkxt tVUJgZRQIZ8oSU9KQAZCfGtjvXNoC1rc4JjkpiV5IzDYTDhMnA/UafEf8G7xbW8j9wa7 E8f2WpMcrRJvFoMBGUhrhylz/+KNDhIO9V9GSmmzKwi5GqMTnvxObRuky6w7+y6Oj1GH K6Rg==
X-Received: by 10.140.104.168 with SMTP id a37mr8634873qgf.9.1418221636080; Wed, 10 Dec 2014 06:27:16 -0800 (PST)
MIME-Version: 1.0
Received: by 10.140.20.143 with HTTP; Wed, 10 Dec 2014 06:26:55 -0800 (PST)
In-Reply-To: <CAG4d1rd60hK8=WtYw-nid_Z7Z8+TvdzA52fNx3pFjND+eDWAfA@mail.gmail.com>
References: <CAG4d1rd60hK8=WtYw-nid_Z7Z8+TvdzA52fNx3pFjND+eDWAfA@mail.gmail.com>
From: "Andrew G. Malis" <agmalis@gmail.com>
Date: Wed, 10 Dec 2014 09:26:55 -0500
Message-ID: <CAA=duU3boijLYXFKW4E-RU1fGhxH_xyAk7NJWqXTFL+896woBA@mail.gmail.com>
Subject: Re: routing area design team on dataplane encapsulation considerations
To: Alia Atlas <akatlas@gmail.com>
Content-Type: multipart/alternative; boundary=001a1134f762d4dc2d0509dd7424
Archived-At: http://mailarchive.ietf.org/arch/msg/routing-discussion/S4W13mktIZlakLcL3Pm7HWO14rg
Cc: "routing-discussion@ietf.org" <routing-discussion@ietf.org>
X-BeenThere: routing-discussion@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: Routing Area General mailing list <routing-discussion.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/routing-discussion>, <mailto:routing-discussion-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/routing-discussion/>
List-Post: <mailto:routing-discussion@ietf.org>
List-Help: <mailto:routing-discussion-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/routing-discussion>, <mailto:routing-discussion-request@ietf.org?subject=subscribe>
X-List-Received-Date: Wed, 10 Dec 2014 14:27:19 -0000

--001a1134f762d4dc2d0509dd7424
Content-Type: text/plain; charset=UTF-8
Content-Transfer-Encoding: quoted-printable

Alia,

To hijack this discussion back to your original post, I'm very surprised to
see no mention of PALS anywhere. We in PALS (and PWE3 before that) have
plenty of experience with data plane encapsulations, and we already have
solutions for a number of the issues in your list, including ECMP (RFC
6391), packet size and fragmentation (4623), OAM (5085 and others), and a
draft on congestion considerations just in the process of finishing up. PWs
have been extremely successful in the marketplace. So I hope the design
team keeps us in mind as well.

Cheers,
Andy

On Tue, Dec 9, 2014 at 5:46 PM, Alia Atlas <akatlas@gmail.com> wrote:

> I have chartered a Routing Area Design Team to work on data-plane
> encapsulation considerations.
>
> I've bcc'd nvo3, sfc, bier, and rtgwg as the most directly relevant.
> Please keep any conversation in one place on routing-discussion.
>
> Erik Nordmark has kindly agreed to lead this design team.  The members of
> the design
> team are:
>
>   Albert Tian <albert.tian@ericsson.com>
>   Erik Nordmark <nordmark@sonic.net>
>   Jesse Gross <jgross@vmware.com>
>   Jon Hudson <jon.hudson@gmail.com>
>   Larry Kreeger (kreeger) <kreeger@cisco.com>
>   Pankaj Garg <Garg.Pankaj@microsoft.com>
>   Pat Thaler <pthaler@broadcom.com>
>   Tom Herbert <therbert@google.com>
>
> The mailing list, rgt-dt-encap-considerations@ietf.org, is closed but the
> archives are
> publicly available at:
>
> http://www.ietf.org/mail-archive/web/rtg-dt-encap-considerations/current/=
maillist.html
>
> The Design Team is chartered as follows:
>
> There have been multiple efforts over the years that have resulted in new
> or modified data plane behaviors involving encapsulations. That includes
> IETF efforts like MPLS, LISP, and TRILL but also industry efforts like
> Vxlan and NVGRE.  These collectively can be seen as a source of insight
> into the properties that data planes need to meet.  The IETF is currently
> working on potentially new encapsulations in NVO3 and SFC and considering
> working on BIER. In addition there is work on tunneling in the INT area.
>
> This is a short term design team chartered to collect and construct usefu=
l
> advice to parties working on new or modified data plane behaviors that
> include additional encapsulations.  The goal is for the group to document
> useful advice gathered from interacting with ongoing efforts.  An Interne=
t
> Draft will be produced for IETF92 to capture that advice, which will be
> discussed in RTGWG.
>
> Data plane encapsulations face a set of common issues such as:
>
>   * How to provide entropy for ECMP
>   * Issues around packet size and fragmentation/reassembly
>   * OAM - what support is needed in an encapsulation format?
>   * Security and privacy.
>   * QoS
>   * Congestion Considerations
>   * IPv6 header protection (non-zero UDP checksum over IPv6 issue)
>   * Extensibility - e.g., for evolving OAM, security, and/or congestion
> control
>   * Layering of multiple encapsulations e.g., SFC over NVO3 over BIER
>
> The design team will provide advice on those issues. The intention is tha=
t
> even where we have different encapsulations for different purposes carryi=
ng
> different data, each such encapsulation doesn=E2=80=99t have to reinvent =
the wheel
> for the above common issues.
>
> The design team will look across the routing area in particular at SFC,
> NVO3 and BIER. It will not be involved in comparing or analyzing any
> particular encapsulation formats proposed in those WGs and BoFs but inste=
ad
> focus on common advice.
>
> Regards,
> Alia
>
> _______________________________________________
> routing-discussion mailing list
> routing-discussion@ietf.org
> https://www.ietf.org/mailman/listinfo/routing-discussion
>
>

--001a1134f762d4dc2d0509dd7424
Content-Type: text/html; charset=UTF-8
Content-Transfer-Encoding: quoted-printable

<div dir=3D"ltr">Alia,<div><br><div>To hijack this discussion back to your =
original post, I&#39;m very surprised to see no mention of PALS anywhere. W=
e in PALS (and PWE3 before that) have plenty of experience with data plane =
encapsulations, and we already have solutions for a number of the issues in=
 your list, including ECMP (RFC 6391), packet size and fragmentation (4623)=
, OAM (5085 and others), and a draft on congestion considerations just in t=
he process of finishing up. PWs have been extremely successful in the marke=
tplace. So I hope the design team keeps us in mind as well.</div></div><div=
><br></div><div>Cheers,</div><div>Andy</div></div><div class=3D"gmail_extra=
"><br><div class=3D"gmail_quote">On Tue, Dec 9, 2014 at 5:46 PM, Alia Atlas=
 <span dir=3D"ltr">&lt;<a href=3D"mailto:akatlas@gmail.com" target=3D"_blan=
k">akatlas@gmail.com</a>&gt;</span> wrote:<br><blockquote class=3D"gmail_qu=
ote" style=3D"margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex=
"><div dir=3D"ltr">I have chartered a Routing Area Design Team to work on d=
ata-plane encapsulation considerations.<div><br></div><div>I&#39;ve bcc&#39=
;d nvo3, sfc, bier, and rtgwg as the most directly relevant.=C2=A0 Please k=
eep any conversation in one place on routing-discussion.<br><div><br></div>=
<div>Erik Nordmark has kindly agreed to lead this design team.=C2=A0 The me=
mbers of the design</div><div>team are:</div><div><br></div><div><div style=
=3D"font-size:13px">=C2=A0 Albert Tian &lt;<a href=3D"mailto:albert.tian@er=
icsson.com" target=3D"_blank">albert.tian@ericsson.com</a>&gt;<br></div><di=
v style=3D"font-size:13px">=C2=A0 Erik Nordmark &lt;<a href=3D"mailto:nordm=
ark@sonic.net" target=3D"_blank">nordmark@sonic.net</a>&gt;<br>=C2=A0 Jesse=
 Gross &lt;<a href=3D"mailto:jgross@vmware.com" target=3D"_blank">jgross@vm=
ware.com</a>&gt;<br>=C2=A0 Jon Hudson &lt;<a href=3D"mailto:jon.hudson@gmai=
l.com" target=3D"_blank">jon.hudson@gmail.com</a>&gt;<br>=C2=A0 Larry Kreeg=
er (kreeger) &lt;<a href=3D"mailto:kreeger@cisco.com" target=3D"_blank">kre=
eger@cisco.com</a>&gt;<br>=C2=A0 Pankaj Garg &lt;<a href=3D"mailto:Garg.Pan=
kaj@microsoft.com" target=3D"_blank">Garg.Pankaj@microsoft.com</a>&gt;<br>=
=C2=A0 Pat Thaler &lt;<a href=3D"mailto:pthaler@broadcom.com" target=3D"_bl=
ank">pthaler@broadcom.com</a>&gt;<br>=C2=A0 Tom Herbert &lt;<a href=3D"mail=
to:therbert@google.com" target=3D"_blank">therbert@google.com</a>&gt;</div>=
</div><div style=3D"font-size:13px"><br></div><div style=3D"font-size:13px"=
>The mailing list, <a href=3D"mailto:rgt-dt-encap-considerations@ietf.org" =
target=3D"_blank">rgt-dt-encap-considerations@ietf.org</a>, is closed but t=
he archives are</div><div style=3D"font-size:13px">publicly available at:</=
div><div style=3D"font-size:13px">=C2=A0 =C2=A0<a href=3D"http://www.ietf.o=
rg/mail-archive/web/rtg-dt-encap-considerations/current/maillist.html" targ=
et=3D"_blank">http://www.ietf.org/mail-archive/web/rtg-dt-encap-considerati=
ons/current/maillist.html</a></div><div style=3D"font-size:13px"><br></div>=
<div style=3D"font-size:13px">The Design Team is chartered as follows:</div=
><div style=3D"font-size:13px"><br></div><div><span>There have been multipl=
e efforts over the years that have resulted in new or modified data plane b=
ehaviors involving encapsulations. That includes IETF efforts like MPLS, LI=
SP, and TRILL but also industry efforts like Vxlan and NVGRE.=C2=A0 These c=
ollectively can be seen as a source of insight into the properties that dat=
a planes need to meet.=C2=A0 The IETF is currently working on potentially n=
ew encapsulations in NVO3 and SFC and considering working on BIER. In addit=
ion there is work on tunneling in the INT area.<br><br>This is a short term=
 design team chartered to collect and construct useful advice to parties wo=
rking on new or modified data plane behaviors that include additional encap=
sulations.=C2=A0 The goal is for the group to document useful advice gather=
ed from interacting with ongoing efforts.=C2=A0 An Internet Draft will be p=
roduced for IETF92 to capture that advice, which will be discussed in RTGWG=
.<br><br>Data plane encapsulations face a set of common issues such as:<br>=
<br>=C2=A0 * How to provide entropy for ECMP<br>=C2=A0 * Issues around pack=
et size and fragmentation/reassembly<br>=C2=A0 * OAM - what support is need=
ed in an encapsulation format?<br>=C2=A0 * Security and privacy.<br>=C2=A0 =
*=C2=A0QoS<br>=C2=A0 *=C2=A0Congestion Considerations<br>=C2=A0 *=C2=A0IPv6=
 header protection (non-zero UDP checksum over IPv6 issue)<br>=C2=A0 * Exte=
nsibility - e.g., for evolving OAM, security, and/or congestion control<br>=
=C2=A0 * Layering of multiple encapsulations e.g., SFC over NVO3 over BIER<=
/span></div><div><span><br></span></div><div><span>The design team will pro=
vide advice on those issues. The intention is that even where we have diffe=
rent encapsulations for different purposes carrying different data, each su=
ch encapsulation doesn=E2=80=99t have to reinvent the wheel for the above c=
ommon issues.<br><br></span></div><div><span>The design team will look acro=
ss the routing area in particular at SFC, NVO3 and BIER. It will not be inv=
olved in comparing or analyzing any particular encapsulation formats propos=
ed in those WGs and BoFs but instead focus on common advice.</span></div><d=
iv><span><br></span></div><div><span>Regards,</span></div><div><span>Alia</=
span></div></div></div>
<br>_______________________________________________<br>
routing-discussion mailing list<br>
<a href=3D"mailto:routing-discussion@ietf.org">routing-discussion@ietf.org<=
/a><br>
<a href=3D"https://www.ietf.org/mailman/listinfo/routing-discussion" target=
=3D"_blank">https://www.ietf.org/mailman/listinfo/routing-discussion</a><br=
>
<br></blockquote></div><br></div>

--001a1134f762d4dc2d0509dd7424--


From nobody Wed Dec 10 06:38:43 2014
Return-Path: <akatlas@gmail.com>
X-Original-To: routing-discussion@ietfa.amsl.com
Delivered-To: routing-discussion@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 0D31D1A1B56 for <routing-discussion@ietfa.amsl.com>; Wed, 10 Dec 2014 06:38:41 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.999
X-Spam-Level: 
X-Spam-Status: No, score=-1.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, 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 s9KzBM-Va16A for <routing-discussion@ietfa.amsl.com>; Wed, 10 Dec 2014 06:38:38 -0800 (PST)
Received: from mail-yk0-x230.google.com (mail-yk0-x230.google.com [IPv6:2607:f8b0:4002:c07::230]) (using TLSv1 with cipher ECDHE-RSA-RC4-SHA (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 753C21A1B37 for <routing-discussion@ietf.org>; Wed, 10 Dec 2014 06:38:38 -0800 (PST)
Received: by mail-yk0-f176.google.com with SMTP id q200so1256709ykb.7 for <routing-discussion@ietf.org>; Wed, 10 Dec 2014 06:38:37 -0800 (PST)
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=goSxQDtBTyErb3Hlk0Gr8K36pb1JXkNGyZGpKpR0Oco=; b=XdWlpEzS5Y8DE98BgUoQIXRYrC45Mnjebt20zzdcJtLfQyxQUObZwxiyomOJwo+9KB 9SyAZzFU+pFjYObhu+34GY2tRdk4Zm/yxslFKuZQU0a/YBvjd9v6v7wITHjkWj4RZGJK maBJ5EqlXgocIgA081qBCjVC5Ja/oHZuIkBkdDFlg+bReadJyK7La3HFvki+OokyhV87 HmTUepwy38/AE/g8I52TV3P3oR2+V9lh3I0cyYsTGcuxmgt7dl6yrjBxkFMQU8bSWMDT SjFX5t1co+koyElSPy5K10qJXf5/W0rhPG3HsBg2NxsRIRYwKbwgtr4vu5vqB/YAduG6 40Ug==
MIME-Version: 1.0
X-Received: by 10.236.109.7 with SMTP id r7mr2966805yhg.107.1418222317745; Wed, 10 Dec 2014 06:38:37 -0800 (PST)
Received: by 10.170.136.132 with HTTP; Wed, 10 Dec 2014 06:38:37 -0800 (PST)
Received: by 10.170.136.132 with HTTP; Wed, 10 Dec 2014 06:38:37 -0800 (PST)
In-Reply-To: <CAA=duU3boijLYXFKW4E-RU1fGhxH_xyAk7NJWqXTFL+896woBA@mail.gmail.com>
References: <CAG4d1rd60hK8=WtYw-nid_Z7Z8+TvdzA52fNx3pFjND+eDWAfA@mail.gmail.com> <CAA=duU3boijLYXFKW4E-RU1fGhxH_xyAk7NJWqXTFL+896woBA@mail.gmail.com>
Date: Wed, 10 Dec 2014 09:38:37 -0500
Message-ID: <CAG4d1rfi=51fxsasu9qfz4=CQQuRSazW-6xoc-8gH5918j2Sxw@mail.gmail.com>
Subject: Re: routing area design team on dataplane encapsulation considerations
From: Alia Atlas <akatlas@gmail.com>
To: "Andrew G. Malis" <agmalis@gmail.com>
Content-Type: multipart/alternative; boundary=001a11c2c596763e7f0509dd9d3c
Archived-At: http://mailarchive.ietf.org/arch/msg/routing-discussion/k9y6Tg-mGbZpHqMw_MPSK56y4-4
Cc: routing-discussion@ietf.org
X-BeenThere: routing-discussion@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: Routing Area General mailing list <routing-discussion.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/routing-discussion>, <mailto:routing-discussion-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/routing-discussion/>
List-Post: <mailto:routing-discussion@ietf.org>
List-Help: <mailto:routing-discussion-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/routing-discussion>, <mailto:routing-discussion-request@ietf.org?subject=subscribe>
X-List-Received-Date: Wed, 10 Dec 2014 14:38:41 -0000

--001a11c2c596763e7f0509dd9d3c
Content-Type: text/plain; charset=UTF-8
Content-Transfer-Encoding: quoted-printable

Hi Andy,

Absolutely true.   I apologize for the oversight.   Psuedo-wires are
another encapsulation that we can learn from.

I expect the design team to be reaching out to get more insight on these
different issues.

Regards
Alia
On Dec 10, 2014 9:27 AM, "Andrew G. Malis" <agmalis@gmail.com> wrote:

> Alia,
>
> To hijack this discussion back to your original post, I'm very surprised
> to see no mention of PALS anywhere. We in PALS (and PWE3 before that) hav=
e
> plenty of experience with data plane encapsulations, and we already have
> solutions for a number of the issues in your list, including ECMP (RFC
> 6391), packet size and fragmentation (4623), OAM (5085 and others), and a
> draft on congestion considerations just in the process of finishing up. P=
Ws
> have been extremely successful in the marketplace. So I hope the design
> team keeps us in mind as well.
>
> Cheers,
> Andy
>
> On Tue, Dec 9, 2014 at 5:46 PM, Alia Atlas <akatlas@gmail.com> wrote:
>
>> I have chartered a Routing Area Design Team to work on data-plane
>> encapsulation considerations.
>>
>> I've bcc'd nvo3, sfc, bier, and rtgwg as the most directly relevant.
>> Please keep any conversation in one place on routing-discussion.
>>
>> Erik Nordmark has kindly agreed to lead this design team.  The members o=
f
>> the design
>> team are:
>>
>>   Albert Tian <albert.tian@ericsson.com>
>>   Erik Nordmark <nordmark@sonic.net>
>>   Jesse Gross <jgross@vmware.com>
>>   Jon Hudson <jon.hudson@gmail.com>
>>   Larry Kreeger (kreeger) <kreeger@cisco.com>
>>   Pankaj Garg <Garg.Pankaj@microsoft.com>
>>   Pat Thaler <pthaler@broadcom.com>
>>   Tom Herbert <therbert@google.com>
>>
>> The mailing list, rgt-dt-encap-considerations@ietf.org, is closed but
>> the archives are
>> publicly available at:
>>
>> http://www.ietf.org/mail-archive/web/rtg-dt-encap-considerations/current=
/maillist.html
>>
>> The Design Team is chartered as follows:
>>
>> There have been multiple efforts over the years that have resulted in ne=
w
>> or modified data plane behaviors involving encapsulations. That includes
>> IETF efforts like MPLS, LISP, and TRILL but also industry efforts like
>> Vxlan and NVGRE.  These collectively can be seen as a source of insight
>> into the properties that data planes need to meet.  The IETF is currentl=
y
>> working on potentially new encapsulations in NVO3 and SFC and considerin=
g
>> working on BIER. In addition there is work on tunneling in the INT area.
>>
>> This is a short term design team chartered to collect and construct
>> useful advice to parties working on new or modified data plane behaviors
>> that include additional encapsulations.  The goal is for the group to
>> document useful advice gathered from interacting with ongoing efforts.  =
An
>> Internet Draft will be produced for IETF92 to capture that advice, which
>> will be discussed in RTGWG.
>>
>> Data plane encapsulations face a set of common issues such as:
>>
>>   * How to provide entropy for ECMP
>>   * Issues around packet size and fragmentation/reassembly
>>   * OAM - what support is needed in an encapsulation format?
>>   * Security and privacy.
>>   * QoS
>>   * Congestion Considerations
>>   * IPv6 header protection (non-zero UDP checksum over IPv6 issue)
>>   * Extensibility - e.g., for evolving OAM, security, and/or congestion
>> control
>>   * Layering of multiple encapsulations e.g., SFC over NVO3 over BIER
>>
>> The design team will provide advice on those issues. The intention is
>> that even where we have different encapsulations for different purposes
>> carrying different data, each such encapsulation doesn=E2=80=99t have to=
 reinvent
>> the wheel for the above common issues.
>>
>> The design team will look across the routing area in particular at SFC,
>> NVO3 and BIER. It will not be involved in comparing or analyzing any
>> particular encapsulation formats proposed in those WGs and BoFs but inst=
ead
>> focus on common advice.
>>
>> Regards,
>> Alia
>>
>> _______________________________________________
>> routing-discussion mailing list
>> routing-discussion@ietf.org
>> https://www.ietf.org/mailman/listinfo/routing-discussion
>>
>>
>

--001a11c2c596763e7f0509dd9d3c
Content-Type: text/html; charset=UTF-8
Content-Transfer-Encoding: quoted-printable

<p dir=3D"ltr">Hi Andy,</p>
<p dir=3D"ltr">Absolutely true.=C2=A0=C2=A0 I apologize for the oversight.=
=C2=A0=C2=A0 Psuedo-wires are another encapsulation that we can learn from.=
 </p>
<p dir=3D"ltr">I expect the design team to be reaching out to get more insi=
ght on these different issues. </p>
<p dir=3D"ltr">Regards <br>
Alia</p>
<div class=3D"gmail_quote">On Dec 10, 2014 9:27 AM, &quot;Andrew G. Malis&q=
uot; &lt;<a href=3D"mailto:agmalis@gmail.com">agmalis@gmail.com</a>&gt; wro=
te:<br type=3D"attribution"><blockquote class=3D"gmail_quote" style=3D"marg=
in:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex"><div dir=3D"ltr"=
>Alia,<div><br><div>To hijack this discussion back to your original post, I=
&#39;m very surprised to see no mention of PALS anywhere. We in PALS (and P=
WE3 before that) have plenty of experience with data plane encapsulations, =
and we already have solutions for a number of the issues in your list, incl=
uding ECMP (RFC 6391), packet size and fragmentation (4623), OAM (5085 and =
others), and a draft on congestion considerations just in the process of fi=
nishing up. PWs have been extremely successful in the marketplace. So I hop=
e the design team keeps us in mind as well.</div></div><div><br></div><div>=
Cheers,</div><div>Andy</div></div><div class=3D"gmail_extra"><br><div class=
=3D"gmail_quote">On Tue, Dec 9, 2014 at 5:46 PM, Alia Atlas <span dir=3D"lt=
r">&lt;<a href=3D"mailto:akatlas@gmail.com" target=3D"_blank">akatlas@gmail=
.com</a>&gt;</span> wrote:<br><blockquote class=3D"gmail_quote" style=3D"ma=
rgin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex"><div dir=3D"lt=
r">I have chartered a Routing Area Design Team to work on data-plane encaps=
ulation considerations.<div><br></div><div>I&#39;ve bcc&#39;d nvo3, sfc, bi=
er, and rtgwg as the most directly relevant.=C2=A0 Please keep any conversa=
tion in one place on routing-discussion.<br><div><br></div><div>Erik Nordma=
rk has kindly agreed to lead this design team.=C2=A0 The members of the des=
ign</div><div>team are:</div><div><br></div><div><div style=3D"font-size:13=
px">=C2=A0 Albert Tian &lt;<a href=3D"mailto:albert.tian@ericsson.com" targ=
et=3D"_blank">albert.tian@ericsson.com</a>&gt;<br></div><div style=3D"font-=
size:13px">=C2=A0 Erik Nordmark &lt;<a href=3D"mailto:nordmark@sonic.net" t=
arget=3D"_blank">nordmark@sonic.net</a>&gt;<br>=C2=A0 Jesse Gross &lt;<a hr=
ef=3D"mailto:jgross@vmware.com" target=3D"_blank">jgross@vmware.com</a>&gt;=
<br>=C2=A0 Jon Hudson &lt;<a href=3D"mailto:jon.hudson@gmail.com" target=3D=
"_blank">jon.hudson@gmail.com</a>&gt;<br>=C2=A0 Larry Kreeger (kreeger) &lt=
;<a href=3D"mailto:kreeger@cisco.com" target=3D"_blank">kreeger@cisco.com</=
a>&gt;<br>=C2=A0 Pankaj Garg &lt;<a href=3D"mailto:Garg.Pankaj@microsoft.co=
m" target=3D"_blank">Garg.Pankaj@microsoft.com</a>&gt;<br>=C2=A0 Pat Thaler=
 &lt;<a href=3D"mailto:pthaler@broadcom.com" target=3D"_blank">pthaler@broa=
dcom.com</a>&gt;<br>=C2=A0 Tom Herbert &lt;<a href=3D"mailto:therbert@googl=
e.com" target=3D"_blank">therbert@google.com</a>&gt;</div></div><div style=
=3D"font-size:13px"><br></div><div style=3D"font-size:13px">The mailing lis=
t, <a href=3D"mailto:rgt-dt-encap-considerations@ietf.org" target=3D"_blank=
">rgt-dt-encap-considerations@ietf.org</a>, is closed but the archives are<=
/div><div style=3D"font-size:13px">publicly available at:</div><div style=
=3D"font-size:13px">=C2=A0 =C2=A0<a href=3D"http://www.ietf.org/mail-archiv=
e/web/rtg-dt-encap-considerations/current/maillist.html" target=3D"_blank">=
http://www.ietf.org/mail-archive/web/rtg-dt-encap-considerations/current/ma=
illist.html</a></div><div style=3D"font-size:13px"><br></div><div style=3D"=
font-size:13px">The Design Team is chartered as follows:</div><div style=3D=
"font-size:13px"><br></div><div><span>There have been multiple efforts over=
 the years that have resulted in new or modified data plane behaviors invol=
ving encapsulations. That includes IETF efforts like MPLS, LISP, and TRILL =
but also industry efforts like Vxlan and NVGRE.=C2=A0 These collectively ca=
n be seen as a source of insight into the properties that data planes need =
to meet.=C2=A0 The IETF is currently working on potentially new encapsulati=
ons in NVO3 and SFC and considering working on BIER. In addition there is w=
ork on tunneling in the INT area.<br><br>This is a short term design team c=
hartered to collect and construct useful advice to parties working on new o=
r modified data plane behaviors that include additional encapsulations.=C2=
=A0 The goal is for the group to document useful advice gathered from inter=
acting with ongoing efforts.=C2=A0 An Internet Draft will be produced for I=
ETF92 to capture that advice, which will be discussed in RTGWG.<br><br>Data=
 plane encapsulations face a set of common issues such as:<br><br>=C2=A0 * =
How to provide entropy for ECMP<br>=C2=A0 * Issues around packet size and f=
ragmentation/reassembly<br>=C2=A0 * OAM - what support is needed in an enca=
psulation format?<br>=C2=A0 * Security and privacy.<br>=C2=A0 *=C2=A0QoS<br=
>=C2=A0 *=C2=A0Congestion Considerations<br>=C2=A0 *=C2=A0IPv6 header prote=
ction (non-zero UDP checksum over IPv6 issue)<br>=C2=A0 * Extensibility - e=
.g., for evolving OAM, security, and/or congestion control<br>=C2=A0 * Laye=
ring of multiple encapsulations e.g., SFC over NVO3 over BIER</span></div><=
div><span><br></span></div><div><span>The design team will provide advice o=
n those issues. The intention is that even where we have different encapsul=
ations for different purposes carrying different data, each such encapsulat=
ion doesn=E2=80=99t have to reinvent the wheel for the above common issues.=
<br><br></span></div><div><span>The design team will look across the routin=
g area in particular at SFC, NVO3 and BIER. It will not be involved in comp=
aring or analyzing any particular encapsulation formats proposed in those W=
Gs and BoFs but instead focus on common advice.</span></div><div><span><br>=
</span></div><div><span>Regards,</span></div><div><span>Alia</span></div></=
div></div>
<br>_______________________________________________<br>
routing-discussion mailing list<br>
<a href=3D"mailto:routing-discussion@ietf.org" target=3D"_blank">routing-di=
scussion@ietf.org</a><br>
<a href=3D"https://www.ietf.org/mailman/listinfo/routing-discussion" target=
=3D"_blank">https://www.ietf.org/mailman/listinfo/routing-discussion</a><br=
>
<br></blockquote></div><br></div>
</blockquote></div>

--001a11c2c596763e7f0509dd9d3c--


From nobody Wed Dec 10 08:19:37 2014
Return-Path: <stbryant@cisco.com>
X-Original-To: routing-discussion@ietfa.amsl.com
Delivered-To: routing-discussion@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id C9C841A86EF for <routing-discussion@ietfa.amsl.com>; Wed, 10 Dec 2014 08:19:35 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -14.511
X-Spam-Level: 
X-Spam-Status: No, score=-14.511 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, RCVD_IN_DNSWL_HI=-5, SPF_PASS=-0.001, T_RP_MATCHES_RCVD=-0.01, USER_IN_DEF_DKIM_WL=-7.5] 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 Uqfy37laQg-k for <routing-discussion@ietfa.amsl.com>; Wed, 10 Dec 2014 08:19:33 -0800 (PST)
Received: from aer-iport-2.cisco.com (aer-iport-2.cisco.com [173.38.203.52]) (using TLSv1 with cipher RC4-SHA (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id A7EA21A7030 for <routing-discussion@ietf.org>; Wed, 10 Dec 2014 08:19:32 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=cisco.com; i=@cisco.com; l=6650; q=dns/txt; s=iport; t=1418228372; x=1419437972; h=message-id:date:from:reply-to:mime-version:to:subject: references:in-reply-to:content-transfer-encoding; bh=m16Cx8jHr4AIyesydPGaDSujY6fTwrIH9TIQNA2txYc=; b=fH6xbDJCAypsA34bJd8ipPaJ1LJLj4Dv1P2Pe1BG4LeJTMbh0y75u8VN 9+JKk9xjvXyXJpUnqtBFm6IH8iuiJKc1lxHhIDEg94ZMIbgI9LuijSGIa KNqgu2zu46QLGyNyNRGJ4jTDLLN0j+BWoCKYSmckUgbJXgc+BW0FhkT/+ U=;
X-IronPort-AV: E=Sophos;i="5.07,553,1413244800"; d="scan'208";a="268493235"
Received: from aer-iport-nat.cisco.com (HELO aer-core-3.cisco.com) ([173.38.203.22]) by aer-iport-2.cisco.com with ESMTP; 10 Dec 2014 16:19:30 +0000
Received: from [10.61.99.142] (dhcp-10-61-99-142.cisco.com [10.61.99.142]) by aer-core-3.cisco.com (8.14.5/8.14.5) with ESMTP id sBAGJUN2030728; Wed, 10 Dec 2014 16:19:30 GMT
Message-ID: <5488728F.5030003@cisco.com>
Date: Wed, 10 Dec 2014 16:19:27 +0000
From: Stewart Bryant <stbryant@cisco.com>
User-Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.9; rv:24.0) Gecko/20100101 Thunderbird/24.6.0
MIME-Version: 1.0
To: l.wood@surrey.ac.uk, akatlas@gmail.com, routing-discussion@ietf.org
Subject: dataplane encapsulation considerations - checksums
References: <CAG4d1rd60hK8=WtYw-nid_Z7Z8+TvdzA52fNx3pFjND+eDWAfA@mail.gmail.com>,  <54877D58.9050002@cisco.com> <DB4PR06MB457F278EAF9C84BCA20E665AD620@DB4PR06MB457.eurprd06.prod.outlook.com>, <54883947.8000302@cisco.com> <1418217891573.89120@surrey.ac.uk>
In-Reply-To: <1418217891573.89120@surrey.ac.uk>
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit
Archived-At: http://mailarchive.ietf.org/arch/msg/routing-discussion/CejBEW3bcb-zlXtwLcLGWb_iZss
X-BeenThere: routing-discussion@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
Reply-To: stbryant@cisco.com
List-Id: Routing Area General mailing list <routing-discussion.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/routing-discussion>, <mailto:routing-discussion-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/routing-discussion/>
List-Post: <mailto:routing-discussion@ietf.org>
List-Help: <mailto:routing-discussion-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/routing-discussion>, <mailto:routing-discussion-request@ietf.org?subject=subscribe>
X-List-Received-Date: Wed, 10 Dec 2014 16:19:36 -0000

Changing the thread title to match the subject

Lloyd

Those numbers are orders of magnitude larger than anything I have
seen elsewhere.

If we look at them in detail they are interesting because if the no ports
are c/s errors as you hypothesis, then only 1/3 of the errors are seemingly
caught by the c/s. I would thus expect  you to be arguing strongly
that we need to deprecate the existing c/s in favour of something
much stronger such as fletcher, or ideally a crypto checksum.
In the case of the link state IGPs we have operators that turn on
link state security not for security but for the enhanced checksum
and that seems to be what you need here in the host stacks.

However we have another study that is worth looking at:

https://www.verisigninc.com/assets/VRSN_Bitsquatting_TR_20120320.pdf

This looks at the UDP c/s errors received by DNS servers, and they
saw an error rate of 1 in 10^5. However if you read the detail there are 
some
systematic effects going on, with a significant fraction seemingly due
to transmit host stack problems which may be what you are seeing.

Now I think all this points to two things, firstly from a perspective
of a host the c/s looks inadequate and there may need to be a
revision of the host stack.

On the other hand the reported error rate for UDP that the paper
reports is an over estimate of the error rate in the tunnel case since
only an error in the IP and UDP header can cause misdelivery
with all other errors reflecting themselves as payload errors which
the payload error protection. Although I do note that they report
some systematic effect in terms of bit position which may point either
way.

One other aspect of this, which is important in Routing, if we are seeing
the error rates you imply are getting past the TCP c/s, surely the routing
protocols will be importing long term errors into the routing subsystems
(specifically BGP and LDP). Are people observing that and if so don't we
need to fix it?

- Stewart



On 10/12/2014 13:24, l.wood@surrey.ac.uk wrote:
> Stewart,
>
> Who needs an NMS? Let's go old school.
> TCP and UDP have equivalent pseudo-header+payload ones complement checksums. So data from TCP can be considered as somewhat equivalent as the technology is the same, and TCP is somewhat better instrumented and monitored than UDP is.
>
> Below sample from two core switches, on tcp connections to them  (not, alas, through them) shows e.g. 10287 TCP checksum errors for 4.3 million TCP/IP packets received. That would be an error rate of 0.24% - the other switch is 0.45% . Note the figure of e.g. 19458 no port - entirely possible something inside the core network is trying a port that isn't there, but also possible corruption of port nos. These are firewalled core devices with limited traffic to them, so I would consider this a best case, without throwing edge device data into the mix.
>
> Extrapolating from TCP checksum rates to UDP checksum rates, from traffic to to traffic through, and from v4 to v6 is left as an exercise for the reader.
>
> Incidentally, these rates pretty much match the 1 in 400 observation made early in Stone's SIGCOMM 2000 paper. 1:400 is 10,000:4,000,000
> http://conferences.sigcomm.org/sigcomm/2000/conf/paper/sigcomm2000-9-1.pdf
> Zut alors, quelle surprise, physics is still physics, this particular SIGCOMM paper is still valid.
> Checksums fail because of corruption. But at least there's a checksum to catch the corruption. Sans checksums, the corruption is unnoticed.
>
> The main reason noone has seen misbehaviour with MPLS is because no-one is looking for or instrumenting for it. (Just like MPLS doesn't need TTL, because no-one ever sees MPLS routing loops, right?) Please go measure MPLS and report back.
>
> Traversing over UDP, as suggested in draft-ietf-mpls-in-udp and draft-ietf-tsvwg-gre-in-udp-encap, increases the scope for corruption across a longer path, rather than individual links - and the UDP checksum is an important last check.
>
> SWT1#sh tcp stat
> Rcvd: 4332545 Total, 19458 no port
>        10287 checksum error, 4959 bad offset, 0 too short
>        62946 packets (2289083 bytes) in sequence
>        93 dup packets (19167 bytes)
>        34 partially dup packets (1878 bytes)
>        107 out-of-order packets (17980 bytes)
>        8 packets (8 bytes) with data after window
>        0 packets after close
>        0 window probe packets, 614 window update packets
>        682 dup ack packets, 0 ack packets with unsend data
>        179823 ack packets (37459618 bytes)
> Sent: 2049509 Total, 0 urgent packets
>        1774234 control packets (including 345 retransmitted)
>        249103 data packets (37439059 bytes)
>        308 data packets (41767 bytes) retransmitted
>        46 data packets (4876 bytes) fastretransmitted
>        25718 ack only packets (3764 delayed)
>        0 window probe packets, 104 window update packets
> 9649 Connections initiated, 1230 connections accepted, 10857 connections established
> 1760675 Connections closed (including 30 dropped, 1749812 embryonic dropped)
> 653 Total rxmt timeout, 9 connections dropped in rxmt timeout
> 0 Keepalive timeout, 6 keepalive probe, 0 Connections dropped in keepalive
>
>
> SWT2#sh tcp stat
> Rcvd: 6370948 Total, 37608 no port
>        28419 checksum error, 1749 bad offset, 0 too short
>        181714 packets (3507560 bytes) in sequence
>        130 dup packets (4925 bytes)
>        164 partially dup packets (302 bytes)
>        35 out-of-order packets (278 bytes)
>        64 packets (4549 bytes) with data after window
>        0 packets after close
>        0 window probe packets, 2006 window update packets
>        3865 dup ack packets, 0 ack packets with unsend data
>        857922 ack packets (92503306 bytes)
> Sent: 3793587 Total, 0 urgent packets
>        2667720 control packets (including 215 retransmitted)
>        1042867 data packets (92804839 bytes)
>        1772 data packets (74842 bytes) retransmitted
>        192 data packets (7176 bytes) fastretransmitted
>        81025 ack only packets (15840 delayed)
>        0 window probe packets, 19 window update packets
> 28735 Connections initiated, 5928 connections accepted, 34638 connections established
> 2626485 Connections closed (including 1349 dropped, 2591827 embryonic dropped)
> 1987 Total rxmt timeout, 4 connections dropped in rxmt timeout
> 0 Keepalive timeout, 0 keepalive probe, 0 Connections dropped in keepalive
>
> Lloyd Wood
> http://about.me/lloydwood
>
> error-free modern networking technology? ha.


From nobody Wed Dec 10 10:16:57 2014
Return-Path: <eric.osborne@level3.com>
X-Original-To: routing-discussion@ietfa.amsl.com
Delivered-To: routing-discussion@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 90DD91A8784 for <routing-discussion@ietfa.amsl.com>; Wed, 10 Dec 2014 10:16:55 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.902
X-Spam-Level: 
X-Spam-Status: No, score=-1.902 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RCVD_IN_DNSWL_NONE=-0.0001, SPF_HELO_PASS=-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 TroN7mz6RKuy for <routing-discussion@ietfa.amsl.com>; Wed, 10 Dec 2014 10:16:51 -0800 (PST)
Received: from mail1.bemta12.messagelabs.com (mail1.bemta12.messagelabs.com [216.82.251.15]) (using TLSv1.2 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 1BE6F1A8763 for <routing-discussion@ietf.org>; Wed, 10 Dec 2014 10:16:51 -0800 (PST)
Received: from [216.82.250.83] by server-15.bemta-12.messagelabs.com id DC/B5-02699-21E88845; Wed, 10 Dec 2014 18:16:50 +0000
X-Env-Sender: eric.osborne@level3.com
X-Msg-Ref: server-5.tower-120.messagelabs.com!1418235393!11394491!1
X-Originating-IP: [209.245.18.37]
X-StarScan-Received: 
X-StarScan-Version: 6.12.5; banners=-,-,-
X-VirusChecked: Checked
Received: (qmail 17729 invoked from network); 10 Dec 2014 18:16:33 -0000
Received: from bge23000.messagelabs1.prod.broomfield1.level3.net (HELO messagelabs1.level3.com) (209.245.18.37) by server-5.tower-120.messagelabs.com with DHE-RSA-AES256-SHA encrypted SMTP;  10 Dec 2014 18:16:33 -0000
Received: from USIDCWVEHT02.corp.global.level3.com (usidcwveht02.corp.global.level3.com [10.1.142.32]) (using TLSv1 with cipher RC4-SHA (128/128 bits)) (Client CN "USIDCWVEHT02.corp.global.level3.com", Issuer "VIDCCERT0001" (not verified)) by messagelabs1.level3.com (Postfix) with ESMTPS id E886F1F736; Wed, 10 Dec 2014 18:16:32 +0000 (GMT)
Received: from USIDCWVEHT03.corp.global.level3.com (10.1.196.123) by USIDCWVEHT02.corp.global.level3.com (10.1.142.32) with Microsoft SMTP Server (TLS) id 14.3.195.1; Wed, 10 Dec 2014 11:16:32 -0700
Received: from USIDCWVEMBX08.corp.global.level3.com ([fe80::20f7:9e5b:2efa:2ad8]) by USIDCWVEHT03.corp.global.level3.com ([::1]) with mapi id 14.03.0195.001; Wed, 10 Dec 2014 11:16:32 -0700
From: "Osborne, Eric" <eric.osborne@level3.com>
To: "stbryant@cisco.com" <stbryant@cisco.com>, "l.wood@surrey.ac.uk" <l.wood@surrey.ac.uk>, "akatlas@gmail.com" <akatlas@gmail.com>, "routing-discussion@ietf.org" <routing-discussion@ietf.org>
Subject: RE: dataplane encapsulation considerations - checksums
Thread-Topic: dataplane encapsulation considerations - checksums
Thread-Index: AQHQFJWWVTgrZkXK8UKgYttOEC8fzpyJHWng
Date: Wed, 10 Dec 2014 18:16:30 +0000
Message-ID: <63CB93BC589C1B4BAFDB41A0A19B7ACD010FC5D2@USIDCWVEMBX08.corp.global.level3.com>
References: <CAG4d1rd60hK8=WtYw-nid_Z7Z8+TvdzA52fNx3pFjND+eDWAfA@mail.gmail.com>,  <54877D58.9050002@cisco.com> <DB4PR06MB457F278EAF9C84BCA20E665AD620@DB4PR06MB457.eurprd06.prod.outlook.com>, <54883947.8000302@cisco.com> <1418217891573.89120@surrey.ac.uk> <5488728F.5030003@cisco.com>
In-Reply-To: <5488728F.5030003@cisco.com>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
x-originating-ip: [10.1.196.207]
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: quoted-printable
MIME-Version: 1.0
Archived-At: http://mailarchive.ietf.org/arch/msg/routing-discussion/-RyE3-QCuy6JLp5uxd2yK1of46M
X-BeenThere: routing-discussion@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: Routing Area General mailing list <routing-discussion.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/routing-discussion>, <mailto:routing-discussion-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/routing-discussion/>
List-Post: <mailto:routing-discussion@ietf.org>
List-Help: <mailto:routing-discussion-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/routing-discussion>, <mailto:routing-discussion-request@ietf.org?subject=subscribe>
X-List-Received-Date: Wed, 10 Dec 2014 18:16:55 -0000

Throwing in my two cents worth of data.

I looked at two routers - one in the US, one in South America.  The TCP num=
bers (largely BGP and SSH) are:

Router #1: =20
Rcvd: 3990580271 Total, 125489 no port
      60097 checksum error, 43239 bad offset, 0 too short

60097/3990580271 =3D 0.0015%


Router #2:
         1291670737 packets received
                 20332 discarded for bad checksums

(20332/1291670737) =3D 0.0015% again


A little worse than Stewarts 1/10^5, but not much.  Certainly not high on m=
y list of Things That Give Me Ulcers.




eric

> -----Original Message-----
> From: routing-discussion [mailto:routing-discussion-bounces@ietf.org] On
> Behalf Of Stewart Bryant
> Sent: Wednesday, December 10, 2014 11:19 AM
> To: l.wood@surrey.ac.uk; akatlas@gmail.com; routing-discussion@ietf.org
> Subject: dataplane encapsulation considerations - checksums
>=20
> Changing the thread title to match the subject
>=20
> Lloyd
>=20
> Those numbers are orders of magnitude larger than anything I have
> seen elsewhere.
>=20
> If we look at them in detail they are interesting because if the no ports
> are c/s errors as you hypothesis, then only 1/3 of the errors are seeming=
ly
> caught by the c/s. I would thus expect  you to be arguing strongly
> that we need to deprecate the existing c/s in favour of something
> much stronger such as fletcher, or ideally a crypto checksum.
> In the case of the link state IGPs we have operators that turn on
> link state security not for security but for the enhanced checksum
> and that seems to be what you need here in the host stacks.
>=20
> However we have another study that is worth looking at:
>=20
> https://www.verisigninc.com/assets/VRSN_Bitsquatting_TR_20120320.pdf
>=20
> This looks at the UDP c/s errors received by DNS servers, and they
> saw an error rate of 1 in 10^5. However if you read the detail there are
> some
> systematic effects going on, with a significant fraction seemingly due
> to transmit host stack problems which may be what you are seeing.
>=20
> Now I think all this points to two things, firstly from a perspective
> of a host the c/s looks inadequate and there may need to be a
> revision of the host stack.
>=20
> On the other hand the reported error rate for UDP that the paper
> reports is an over estimate of the error rate in the tunnel case since
> only an error in the IP and UDP header can cause misdelivery
> with all other errors reflecting themselves as payload errors which
> the payload error protection. Although I do note that they report
> some systematic effect in terms of bit position which may point either
> way.
>=20
> One other aspect of this, which is important in Routing, if we are seeing
> the error rates you imply are getting past the TCP c/s, surely the routin=
g
> protocols will be importing long term errors into the routing subsystems
> (specifically BGP and LDP). Are people observing that and if so don't we
> need to fix it?
>=20
> - Stewart
>=20
>=20
>=20
> On 10/12/2014 13:24, l.wood@surrey.ac.uk wrote:
> > Stewart,
> >
> > Who needs an NMS? Let's go old school.
> > TCP and UDP have equivalent pseudo-header+payload ones complement
> checksums. So data from TCP can be considered as somewhat equivalent as t=
he
> technology is the same, and TCP is somewhat better instrumented and
> monitored than UDP is.
> >
> > Below sample from two core switches, on tcp connections to them  (not, =
alas,
> through them) shows e.g. 10287 TCP checksum errors for 4.3 million TCP/IP
> packets received. That would be an error rate of 0.24% - the other switch=
 is
> 0.45% . Note the figure of e.g. 19458 no port - entirely possible somethi=
ng
> inside the core network is trying a port that isn't there, but also possi=
ble
> corruption of port nos. These are firewalled core devices with limited tr=
affic to
> them, so I would consider this a best case, without throwing edge device =
data
> into the mix.
> >
> > Extrapolating from TCP checksum rates to UDP checksum rates, from traff=
ic
> to to traffic through, and from v4 to v6 is left as an exercise for the r=
eader.
> >
> > Incidentally, these rates pretty much match the 1 in 400 observation ma=
de
> early in Stone's SIGCOMM 2000 paper. 1:400 is 10,000:4,000,000
> > http://conferences.sigcomm.org/sigcomm/2000/conf/paper/sigcomm2000-9-
> 1.pdf
> > Zut alors, quelle surprise, physics is still physics, this particular S=
IGCOMM
> paper is still valid.
> > Checksums fail because of corruption. But at least there's a checksum t=
o
> catch the corruption. Sans checksums, the corruption is unnoticed.
> >
> > The main reason noone has seen misbehaviour with MPLS is because no-one
> is looking for or instrumenting for it. (Just like MPLS doesn't need TTL,=
 because
> no-one ever sees MPLS routing loops, right?) Please go measure MPLS and
> report back.
> >
> > Traversing over UDP, as suggested in draft-ietf-mpls-in-udp and draft-i=
etf-
> tsvwg-gre-in-udp-encap, increases the scope for corruption across a longe=
r
> path, rather than individual links - and the UDP checksum is an important=
 last
> check.
> >
> > SWT1#sh tcp stat
> > Rcvd: 4332545 Total, 19458 no port
> >        10287 checksum error, 4959 bad offset, 0 too short
> >        62946 packets (2289083 bytes) in sequence
> >        93 dup packets (19167 bytes)
> >        34 partially dup packets (1878 bytes)
> >        107 out-of-order packets (17980 bytes)
> >        8 packets (8 bytes) with data after window
> >        0 packets after close
> >        0 window probe packets, 614 window update packets
> >        682 dup ack packets, 0 ack packets with unsend data
> >        179823 ack packets (37459618 bytes)
> > Sent: 2049509 Total, 0 urgent packets
> >        1774234 control packets (including 345 retransmitted)
> >        249103 data packets (37439059 bytes)
> >        308 data packets (41767 bytes) retransmitted
> >        46 data packets (4876 bytes) fastretransmitted
> >        25718 ack only packets (3764 delayed)
> >        0 window probe packets, 104 window update packets
> > 9649 Connections initiated, 1230 connections accepted, 10857 connection=
s
> established
> > 1760675 Connections closed (including 30 dropped, 1749812 embryonic
> dropped)
> > 653 Total rxmt timeout, 9 connections dropped in rxmt timeout
> > 0 Keepalive timeout, 6 keepalive probe, 0 Connections dropped in keepal=
ive
> >
> >
> > SWT2#sh tcp stat
> > Rcvd: 6370948 Total, 37608 no port
> >        28419 checksum error, 1749 bad offset, 0 too short
> >        181714 packets (3507560 bytes) in sequence
> >        130 dup packets (4925 bytes)
> >        164 partially dup packets (302 bytes)
> >        35 out-of-order packets (278 bytes)
> >        64 packets (4549 bytes) with data after window
> >        0 packets after close
> >        0 window probe packets, 2006 window update packets
> >        3865 dup ack packets, 0 ack packets with unsend data
> >        857922 ack packets (92503306 bytes)
> > Sent: 3793587 Total, 0 urgent packets
> >        2667720 control packets (including 215 retransmitted)
> >        1042867 data packets (92804839 bytes)
> >        1772 data packets (74842 bytes) retransmitted
> >        192 data packets (7176 bytes) fastretransmitted
> >        81025 ack only packets (15840 delayed)
> >        0 window probe packets, 19 window update packets
> > 28735 Connections initiated, 5928 connections accepted, 34638 connectio=
ns
> established
> > 2626485 Connections closed (including 1349 dropped, 2591827 embryonic
> dropped)
> > 1987 Total rxmt timeout, 4 connections dropped in rxmt timeout
> > 0 Keepalive timeout, 0 keepalive probe, 0 Connections dropped in keepal=
ive
> >
> > Lloyd Wood
> > http://about.me/lloydwood
> >
> > error-free modern networking technology? ha.
>=20
> _______________________________________________
> routing-discussion mailing list
> routing-discussion@ietf.org
> https://www.ietf.org/mailman/listinfo/routing-discussion


From nobody Wed Dec 10 11:42:46 2014
Return-Path: <pthaler@broadcom.com>
X-Original-To: routing-discussion@ietfa.amsl.com
Delivered-To: routing-discussion@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id C181D1A8AAD for <routing-discussion@ietfa.amsl.com>; Wed, 10 Dec 2014 11:42:43 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -4.21
X-Spam-Level: 
X-Spam-Status: No, score=-4.21 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RCVD_IN_DNSWL_MED=-2.3, 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 uzFjx6PLdY6M for <routing-discussion@ietfa.amsl.com>; Wed, 10 Dec 2014 11:42:41 -0800 (PST)
Received: from mail-gw1-out.broadcom.com (mail-gw1-out.broadcom.com [216.31.210.62]) by ietfa.amsl.com (Postfix) with ESMTP id 5EDF11A87A0 for <routing-discussion@ietf.org>; Wed, 10 Dec 2014 11:42:27 -0800 (PST)
X-IronPort-AV: E=Sophos;i="5.07,553,1413270000"; d="scan'208";a="52917904"
Received: from irvexchcas06.broadcom.com (HELO IRVEXCHCAS06.corp.ad.broadcom.com) ([10.9.208.53]) by mail-gw1-out.broadcom.com with ESMTP; 10 Dec 2014 13:31:40 -0800
Received: from SJEXCHCAS05.corp.ad.broadcom.com (10.16.203.12) by IRVEXCHCAS06.corp.ad.broadcom.com (10.9.208.53) with Microsoft SMTP Server (TLS) id 14.3.174.1; Wed, 10 Dec 2014 11:42:26 -0800
Received: from SJEXCHMB09.corp.ad.broadcom.com ([fe80::3da7:665e:cc78:181f]) by SJEXCHCAS05.corp.ad.broadcom.com ([::1]) with mapi id 14.03.0174.001; Wed, 10 Dec 2014 11:42:31 -0800
From: Pat Thaler <pthaler@broadcom.com>
To: "stbryant@cisco.com" <stbryant@cisco.com>, "l.wood@surrey.ac.uk" <l.wood@surrey.ac.uk>, "akatlas@gmail.com" <akatlas@gmail.com>, "routing-discussion@ietf.org" <routing-discussion@ietf.org>
Subject: RE: dataplane encapsulation considerations - checksums
Thread-Topic: dataplane encapsulation considerations - checksums
Thread-Index: AQHQFJUdrHRFvDP0302g8VCU7xu1pZyJLFtQ
Date: Wed, 10 Dec 2014 19:42:25 +0000
Message-ID: <EB9B93801780FD4CA165E0FBCB3C3E672B1EABCC@SJEXCHMB09.corp.ad.broadcom.com>
References: <CAG4d1rd60hK8=WtYw-nid_Z7Z8+TvdzA52fNx3pFjND+eDWAfA@mail.gmail.com>,  <54877D58.9050002@cisco.com> <DB4PR06MB457F278EAF9C84BCA20E665AD620@DB4PR06MB457.eurprd06.prod.outlook.com>, <54883947.8000302@cisco.com> <1418217891573.89120@surrey.ac.uk> <5488728F.5030003@cisco.com>
In-Reply-To: <5488728F.5030003@cisco.com>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
x-originating-ip: [10.16.203.100]
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: quoted-printable
MIME-Version: 1.0
Archived-At: http://mailarchive.ietf.org/arch/msg/routing-discussion/oIXlUm4XSeGZc-KqPQ9IzfHO8PY
X-BeenThere: routing-discussion@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: Routing Area General mailing list <routing-discussion.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/routing-discussion>, <mailto:routing-discussion-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/routing-discussion/>
List-Post: <mailto:routing-discussion@ietf.org>
List-Help: <mailto:routing-discussion-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/routing-discussion>, <mailto:routing-discussion-request@ietf.org?subject=subscribe>
X-List-Received-Date: Wed, 10 Dec 2014 19:42:44 -0000

"If we look at them in detail they are interesting because if the no ports
are c/s errors as you hypothesis, then only 1/3 of the errors are seemingly
caught by the c/s. I would thus expect  you to be arguing strongly
that we need to deprecate the existing c/s in favour of something
much stronger such as fletcher, or ideally a crypto checksum."

The no port errors could be happening on a much larger base of traffic than=
 the checksum errors.=20
Check sum is only being checked on traffic destined for the router.=20
Arrival of a packet with no corresponding port could be due to an error in =
the IP address of any packet on the network - presumably a much larger amou=
nt of traffic.=20
Checksum might be catching most of the errors but a very small portion of t=
he network traffic has the router as a destination so the router is more li=
kely to see a corrupted packet arrive (something where the destination IP c=
hanged but with good checksum and bad port number) than a checksum error.

However, the reason that checksum is being urged is to prevent delivering p=
ackets to the wrong tenants because of an undetected error causing misdirec=
tion.  If the no port traffic is from corrupted packets that the checksum d=
idn't catch, checksum isn't doing a thorough job of doing that. We don't kn=
ow what % is getting misdirected because we don't have a number for the tot=
al traffic.  Of course, that "if" is a big assumption - the no port traffic=
 may be from some other cause.

One can't evaluate the comparative strength of error detection methods with=
out knowing something about the kind of errors expected, the rate they occu=
r at and the acceptable rate of undetected error.

If the error mechanism is an alpha particle corrupting a bit in un-parity c=
hecked memory with a very low BER so that the likelihood of two bits in a p=
acket having 2 errors is below the goal for undetected errors, any of the c=
hecksum algorithms or any CRC will catch a single bit error. =20
On the other hand, if the memory is parity protected, it will catch the sin=
gle bit error itself

If the goal is catching burst errors of less than 32 bits or multiple singl=
e bit errors, Fletcher will catch more of the errors than the plain checksu=
m but not an order of magnitude better so if the plain checksum isn't good =
enough for the goal, one probably needs to go to a CRC (which gets a few or=
ders of magnitude improvement) or a cryptographic integrity check.

See RFC 3385.

Pat

-----Original Message-----
From: routing-discussion [mailto:routing-discussion-bounces@ietf.org] On Be=
half Of Stewart Bryant
Sent: Wednesday, December 10, 2014 8:19 AM
To: l.wood@surrey.ac.uk; akatlas@gmail.com; routing-discussion@ietf.org
Subject: dataplane encapsulation considerations - checksums

Changing the thread title to match the subject

Lloyd

Those numbers are orders of magnitude larger than anything I have
seen elsewhere.

If we look at them in detail they are interesting because if the no ports
are c/s errors as you hypothesis, then only 1/3 of the errors are seemingly
caught by the c/s. I would thus expect  you to be arguing strongly
that we need to deprecate the existing c/s in favour of something
much stronger such as fletcher, or ideally a crypto checksum.
In the case of the link state IGPs we have operators that turn on
link state security not for security but for the enhanced checksum
and that seems to be what you need here in the host stacks.

However we have another study that is worth looking at:

https://www.verisigninc.com/assets/VRSN_Bitsquatting_TR_20120320.pdf

This looks at the UDP c/s errors received by DNS servers, and they
saw an error rate of 1 in 10^5. However if you read the detail there are=20
some
systematic effects going on, with a significant fraction seemingly due
to transmit host stack problems which may be what you are seeing.

Now I think all this points to two things, firstly from a perspective
of a host the c/s looks inadequate and there may need to be a
revision of the host stack.

On the other hand the reported error rate for UDP that the paper
reports is an over estimate of the error rate in the tunnel case since
only an error in the IP and UDP header can cause misdelivery
with all other errors reflecting themselves as payload errors which
the payload error protection. Although I do note that they report
some systematic effect in terms of bit position which may point either
way.

One other aspect of this, which is important in Routing, if we are seeing
the error rates you imply are getting past the TCP c/s, surely the routing
protocols will be importing long term errors into the routing subsystems
(specifically BGP and LDP). Are people observing that and if so don't we
need to fix it?

- Stewart



On 10/12/2014 13:24, l.wood@surrey.ac.uk wrote:
> Stewart,
>
> Who needs an NMS? Let's go old school.
> TCP and UDP have equivalent pseudo-header+payload ones complement checksu=
ms. So data from TCP can be considered as somewhat equivalent as the techno=
logy is the same, and TCP is somewhat better instrumented and monitored tha=
n UDP is.
>
> Below sample from two core switches, on tcp connections to them  (not, al=
as, through them) shows e.g. 10287 TCP checksum errors for 4.3 million TCP/=
IP packets received. That would be an error rate of 0.24% - the other switc=
h is 0.45% . Note the figure of e.g. 19458 no port - entirely possible some=
thing inside the core network is trying a port that isn't there, but also p=
ossible corruption of port nos. These are firewalled core devices with limi=
ted traffic to them, so I would consider this a best case, without throwing=
 edge device data into the mix.
>
> Extrapolating from TCP checksum rates to UDP checksum rates, from traffic=
 to to traffic through, and from v4 to v6 is left as an exercise for the re=
ader.
>
> Incidentally, these rates pretty much match the 1 in 400 observation made=
 early in Stone's SIGCOMM 2000 paper. 1:400 is 10,000:4,000,000
> http://conferences.sigcomm.org/sigcomm/2000/conf/paper/sigcomm2000-9-1.pd=
f
> Zut alors, quelle surprise, physics is still physics, this particular SIG=
COMM paper is still valid.
> Checksums fail because of corruption. But at least there's a checksum to =
catch the corruption. Sans checksums, the corruption is unnoticed.
>
> The main reason noone has seen misbehaviour with MPLS is because no-one i=
s looking for or instrumenting for it. (Just like MPLS doesn't need TTL, be=
cause no-one ever sees MPLS routing loops, right?) Please go measure MPLS a=
nd report back.
>
> Traversing over UDP, as suggested in draft-ietf-mpls-in-udp and draft-iet=
f-tsvwg-gre-in-udp-encap, increases the scope for corruption across a longe=
r path, rather than individual links - and the UDP checksum is an important=
 last check.
>
> SWT1#sh tcp stat
> Rcvd: 4332545 Total, 19458 no port
>        10287 checksum error, 4959 bad offset, 0 too short
>        62946 packets (2289083 bytes) in sequence
>        93 dup packets (19167 bytes)
>        34 partially dup packets (1878 bytes)
>        107 out-of-order packets (17980 bytes)
>        8 packets (8 bytes) with data after window
>        0 packets after close
>        0 window probe packets, 614 window update packets
>        682 dup ack packets, 0 ack packets with unsend data
>        179823 ack packets (37459618 bytes)
> Sent: 2049509 Total, 0 urgent packets
>        1774234 control packets (including 345 retransmitted)
>        249103 data packets (37439059 bytes)
>        308 data packets (41767 bytes) retransmitted
>        46 data packets (4876 bytes) fastretransmitted
>        25718 ack only packets (3764 delayed)
>        0 window probe packets, 104 window update packets
> 9649 Connections initiated, 1230 connections accepted, 10857 connections =
established
> 1760675 Connections closed (including 30 dropped, 1749812 embryonic dropp=
ed)
> 653 Total rxmt timeout, 9 connections dropped in rxmt timeout
> 0 Keepalive timeout, 6 keepalive probe, 0 Connections dropped in keepaliv=
e
>
>
> SWT2#sh tcp stat
> Rcvd: 6370948 Total, 37608 no port
>        28419 checksum error, 1749 bad offset, 0 too short
>        181714 packets (3507560 bytes) in sequence
>        130 dup packets (4925 bytes)
>        164 partially dup packets (302 bytes)
>        35 out-of-order packets (278 bytes)
>        64 packets (4549 bytes) with data after window
>        0 packets after close
>        0 window probe packets, 2006 window update packets
>        3865 dup ack packets, 0 ack packets with unsend data
>        857922 ack packets (92503306 bytes)
> Sent: 3793587 Total, 0 urgent packets
>        2667720 control packets (including 215 retransmitted)
>        1042867 data packets (92804839 bytes)
>        1772 data packets (74842 bytes) retransmitted
>        192 data packets (7176 bytes) fastretransmitted
>        81025 ack only packets (15840 delayed)
>        0 window probe packets, 19 window update packets
> 28735 Connections initiated, 5928 connections accepted, 34638 connections=
 established
> 2626485 Connections closed (including 1349 dropped, 2591827 embryonic dro=
pped)
> 1987 Total rxmt timeout, 4 connections dropped in rxmt timeout
> 0 Keepalive timeout, 0 keepalive probe, 0 Connections dropped in keepaliv=
e
>
> Lloyd Wood
> http://about.me/lloydwood
>
> error-free modern networking technology? ha.

_______________________________________________
routing-discussion mailing list
routing-discussion@ietf.org
https://www.ietf.org/mailman/listinfo/routing-discussion


From nobody Wed Dec 10 12:11:54 2014
Return-Path: <don.fedyk@hp.com>
X-Original-To: routing-discussion@ietfa.amsl.com
Delivered-To: routing-discussion@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 66ECF1A8A0C for <routing-discussion@ietfa.amsl.com>; Wed, 10 Dec 2014 12:11:52 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -4.209
X-Spam-Level: 
X-Spam-Status: No, score=-4.209 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_MED=-2.3, 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 lYKd3xogqSqU for <routing-discussion@ietfa.amsl.com>; Wed, 10 Dec 2014 12:11:46 -0800 (PST)
Received: from g6t1526.atlanta.hp.com (g6t1526.atlanta.hp.com [15.193.200.69]) (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 CAD391A8AC5 for <routing-discussion@ietf.org>; Wed, 10 Dec 2014 12:11:45 -0800 (PST)
Received: from G6W4001.americas.hpqcorp.net (g6w4001.atlanta.hp.com [16.205.80.210]) (using TLSv1 with cipher AES128-SHA (128/128 bits)) (No client certificate requested) by g6t1526.atlanta.hp.com (Postfix) with ESMTPS id D290F14B; Wed, 10 Dec 2014 20:11:44 +0000 (UTC)
Received: from G5W5500.americas.hpqcorp.net (16.201.144.180) by G6W4001.americas.hpqcorp.net (16.205.80.210) with Microsoft SMTP Server (TLS) id 14.3.169.1; Wed, 10 Dec 2014 20:10:35 +0000
Received: from G6W2492.americas.hpqcorp.net ([169.254.8.160]) by G5W5500.americas.hpqcorp.net ([16.201.144.180]) with mapi id 14.03.0169.001; Wed, 10 Dec 2014 20:10:35 +0000
From: "Fedyk, Don" <don.fedyk@hp.com>
To: Alia Atlas <akatlas@gmail.com>, "Andrew G. Malis" <agmalis@gmail.com>
Subject: RE: routing area design team on dataplane encapsulation considerations
Thread-Topic: routing area design team on dataplane encapsulation considerations
Thread-Index: AQHQFAIBof6l1w2lzkaDttVw5IYW85yI4q2AgAADRYCAAFYvUA==
Date: Wed, 10 Dec 2014 20:10:35 +0000
Message-ID: <A46D9C092EA46F489F135060986AD9FF0F8BD5B6@G6W2492.americas.hpqcorp.net>
References: <CAG4d1rd60hK8=WtYw-nid_Z7Z8+TvdzA52fNx3pFjND+eDWAfA@mail.gmail.com> <CAA=duU3boijLYXFKW4E-RU1fGhxH_xyAk7NJWqXTFL+896woBA@mail.gmail.com> <CAG4d1rfi=51fxsasu9qfz4=CQQuRSazW-6xoc-8gH5918j2Sxw@mail.gmail.com>
In-Reply-To: <CAG4d1rfi=51fxsasu9qfz4=CQQuRSazW-6xoc-8gH5918j2Sxw@mail.gmail.com>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
x-originating-ip: [16.201.12.28]
Content-Type: multipart/alternative; boundary="_000_A46D9C092EA46F489F135060986AD9FF0F8BD5B6G6W2492americas_"
MIME-Version: 1.0
Archived-At: http://mailarchive.ietf.org/arch/msg/routing-discussion/ITSZ4Da1rzSr1sal8469hLCS8BQ
Cc: "routing-discussion@ietf.org" <routing-discussion@ietf.org>
X-BeenThere: routing-discussion@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: Routing Area General mailing list <routing-discussion.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/routing-discussion>, <mailto:routing-discussion-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/routing-discussion/>
List-Post: <mailto:routing-discussion@ietf.org>
List-Help: <mailto:routing-discussion-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/routing-discussion>, <mailto:routing-discussion-request@ietf.org?subject=subscribe>
X-List-Received-Date: Wed, 10 Dec 2014 20:11:52 -0000

--_000_A46D9C092EA46F489F135060986AD9FF0F8BD5B6G6W2492americas_
Content-Type: text/plain; charset="utf-8"
Content-Transfer-Encoding: base64

SGkgQWxpYQ0KDQpJIHRoaW5rIGl0IHdvdWxkIGJlIGdvb2QgZm9yIHRoZSBkZXNpZ24gdGVhbSB0
byAgYWxzbyBpbmNsdWRlIGZvciByZWZlcmVuY2UgY29tcGFyaXNvbnMgb2YgdGhlIEwyIGVuY2Fw
c3VsYXRpb25zIGZyb20gSUVFRSA4MDIuMSBzdWNoIGFzIFByb3ZpZGVyIGJhY2tib25lIEJyaWRn
aW5nKFBCQikgYWthIE1hYy1pbi1NQUMgYW5kIElFRUUgODAyLjFRYnAg4oCTIEVxdWFsIENvc3Qg
TXVsdGlwYXRoIChFQ01QKSAgKGFsc28gYSBNYWMtaW4tTUFDIGVuY2Fwcykgd2hpY2ggaGF2ZSBz
b21lIGNvbW1vbiBwcm9wZXJ0aWVzIHdpdGggZGF0YSBwbGFuZSBlbmNhcHN1bGF0aW9ucyBpbiBn
ZW5lcmFsLiAgQXMgd2l0aCBQV0UgdGhlIGRlc2lnbmVycyBvZiB0aGVzZSBlbmNhcHN1bGF0aW9u
cyBoYXZlIGdyYXBwbGVkIHdpdGggYSBsb3Qgb2YgdGhlIHNhbWUgaXNzdWVzLg0KDQpPbmUgIGFk
ZGl0aW9uIHRvIHlvdXIgbGlzdCB0aGVzZSBMMiBlbmNhcHN1bGF0aW9ucyAgaGF2ZSBzcGVjaWZp
YyBzdXBwb3J0IGZvciBtdWx0aWNhc3QgdGhhdCBjYW4gYmUgdXRpbGl6ZWQgaW4gdGhlIGluIHRo
ZSB1bmRlcmxheSBkYXRhIHBsYW5lLg0KDQpDaGVlcnMsDQpEb24NCg0KRnJvbTogcm91dGluZy1k
aXNjdXNzaW9uIFttYWlsdG86cm91dGluZy1kaXNjdXNzaW9uLWJvdW5jZXNAaWV0Zi5vcmddIE9u
IEJlaGFsZiBPZiBBbGlhIEF0bGFzDQpTZW50OiBXZWRuZXNkYXksIERlY2VtYmVyIDEwLCAyMDE0
IDk6MzkgQU0NClRvOiBBbmRyZXcgRy4gTWFsaXMNCkNjOiByb3V0aW5nLWRpc2N1c3Npb25AaWV0
Zi5vcmcNClN1YmplY3Q6IFJlOiByb3V0aW5nIGFyZWEgZGVzaWduIHRlYW0gb24gZGF0YXBsYW5l
IGVuY2Fwc3VsYXRpb24gY29uc2lkZXJhdGlvbnMNCg0KDQpIaSBBbmR5LA0KDQpBYnNvbHV0ZWx5
IHRydWUuICAgSSBhcG9sb2dpemUgZm9yIHRoZSBvdmVyc2lnaHQuICAgUHN1ZWRvLXdpcmVzIGFy
ZSBhbm90aGVyIGVuY2Fwc3VsYXRpb24gdGhhdCB3ZSBjYW4gbGVhcm4gZnJvbS4NCg0KSSBleHBl
Y3QgdGhlIGRlc2lnbiB0ZWFtIHRvIGJlIHJlYWNoaW5nIG91dCB0byBnZXQgbW9yZSBpbnNpZ2h0
IG9uIHRoZXNlIGRpZmZlcmVudCBpc3N1ZXMuDQoNClJlZ2FyZHMNCkFsaWENCk9uIERlYyAxMCwg
MjAxNCA5OjI3IEFNLCAiQW5kcmV3IEcuIE1hbGlzIiA8YWdtYWxpc0BnbWFpbC5jb208bWFpbHRv
OmFnbWFsaXNAZ21haWwuY29tPj4gd3JvdGU6DQpBbGlhLA0KDQpUbyBoaWphY2sgdGhpcyBkaXNj
dXNzaW9uIGJhY2sgdG8geW91ciBvcmlnaW5hbCBwb3N0LCBJJ20gdmVyeSBzdXJwcmlzZWQgdG8g
c2VlIG5vIG1lbnRpb24gb2YgUEFMUyBhbnl3aGVyZS4gV2UgaW4gUEFMUyAoYW5kIFBXRTMgYmVm
b3JlIHRoYXQpIGhhdmUgcGxlbnR5IG9mIGV4cGVyaWVuY2Ugd2l0aCBkYXRhIHBsYW5lIGVuY2Fw
c3VsYXRpb25zLCBhbmQgd2UgYWxyZWFkeSBoYXZlIHNvbHV0aW9ucyBmb3IgYSBudW1iZXIgb2Yg
dGhlIGlzc3VlcyBpbiB5b3VyIGxpc3QsIGluY2x1ZGluZyBFQ01QIChSRkMgNjM5MSksIHBhY2tl
dCBzaXplIGFuZCBmcmFnbWVudGF0aW9uICg0NjIzKSwgT0FNICg1MDg1IGFuZCBvdGhlcnMpLCBh
bmQgYSBkcmFmdCBvbiBjb25nZXN0aW9uIGNvbnNpZGVyYXRpb25zIGp1c3QgaW4gdGhlIHByb2Nl
c3Mgb2YgZmluaXNoaW5nIHVwLiBQV3MgaGF2ZSBiZWVuIGV4dHJlbWVseSBzdWNjZXNzZnVsIGlu
IHRoZSBtYXJrZXRwbGFjZS4gU28gSSBob3BlIHRoZSBkZXNpZ24gdGVhbSBrZWVwcyB1cyBpbiBt
aW5kIGFzIHdlbGwuDQoNCkNoZWVycywNCkFuZHkNCg0KT24gVHVlLCBEZWMgOSwgMjAxNCBhdCA1
OjQ2IFBNLCBBbGlhIEF0bGFzIDxha2F0bGFzQGdtYWlsLmNvbTxtYWlsdG86YWthdGxhc0BnbWFp
bC5jb20+PiB3cm90ZToNCkkgaGF2ZSBjaGFydGVyZWQgYSBSb3V0aW5nIEFyZWEgRGVzaWduIFRl
YW0gdG8gd29yayBvbiBkYXRhLXBsYW5lIGVuY2Fwc3VsYXRpb24gY29uc2lkZXJhdGlvbnMuDQoN
CkkndmUgYmNjJ2QgbnZvMywgc2ZjLCBiaWVyLCBhbmQgcnRnd2cgYXMgdGhlIG1vc3QgZGlyZWN0
bHkgcmVsZXZhbnQuICBQbGVhc2Uga2VlcCBhbnkgY29udmVyc2F0aW9uIGluIG9uZSBwbGFjZSBv
biByb3V0aW5nLWRpc2N1c3Npb24uDQoNCkVyaWsgTm9yZG1hcmsgaGFzIGtpbmRseSBhZ3JlZWQg
dG8gbGVhZCB0aGlzIGRlc2lnbiB0ZWFtLiAgVGhlIG1lbWJlcnMgb2YgdGhlIGRlc2lnbg0KdGVh
bSBhcmU6DQoNCiAgQWxiZXJ0IFRpYW4gPGFsYmVydC50aWFuQGVyaWNzc29uLmNvbTxtYWlsdG86
YWxiZXJ0LnRpYW5AZXJpY3Nzb24uY29tPj4NCiAgRXJpayBOb3JkbWFyayA8bm9yZG1hcmtAc29u
aWMubmV0PG1haWx0bzpub3JkbWFya0Bzb25pYy5uZXQ+Pg0KICBKZXNzZSBHcm9zcyA8amdyb3Nz
QHZtd2FyZS5jb208bWFpbHRvOmpncm9zc0B2bXdhcmUuY29tPj4NCiAgSm9uIEh1ZHNvbiA8am9u
Lmh1ZHNvbkBnbWFpbC5jb208bWFpbHRvOmpvbi5odWRzb25AZ21haWwuY29tPj4NCiAgTGFycnkg
S3JlZWdlciAoa3JlZWdlcikgPGtyZWVnZXJAY2lzY28uY29tPG1haWx0bzprcmVlZ2VyQGNpc2Nv
LmNvbT4+DQogIFBhbmthaiBHYXJnIDxHYXJnLlBhbmthakBtaWNyb3NvZnQuY29tPG1haWx0bzpH
YXJnLlBhbmthakBtaWNyb3NvZnQuY29tPj4NCiAgUGF0IFRoYWxlciA8cHRoYWxlckBicm9hZGNv
bS5jb208bWFpbHRvOnB0aGFsZXJAYnJvYWRjb20uY29tPj4NCiAgVG9tIEhlcmJlcnQgPHRoZXJi
ZXJ0QGdvb2dsZS5jb208bWFpbHRvOnRoZXJiZXJ0QGdvb2dsZS5jb20+Pg0KDQpUaGUgbWFpbGlu
ZyBsaXN0LCByZ3QtZHQtZW5jYXAtY29uc2lkZXJhdGlvbnNAaWV0Zi5vcmc8bWFpbHRvOnJndC1k
dC1lbmNhcC1jb25zaWRlcmF0aW9uc0BpZXRmLm9yZz4sIGlzIGNsb3NlZCBidXQgdGhlIGFyY2hp
dmVzIGFyZQ0KcHVibGljbHkgYXZhaWxhYmxlIGF0Og0KICAgaHR0cDovL3d3dy5pZXRmLm9yZy9t
YWlsLWFyY2hpdmUvd2ViL3J0Zy1kdC1lbmNhcC1jb25zaWRlcmF0aW9ucy9jdXJyZW50L21haWxs
aXN0Lmh0bWwNCg0KVGhlIERlc2lnbiBUZWFtIGlzIGNoYXJ0ZXJlZCBhcyBmb2xsb3dzOg0KDQpU
aGVyZSBoYXZlIGJlZW4gbXVsdGlwbGUgZWZmb3J0cyBvdmVyIHRoZSB5ZWFycyB0aGF0IGhhdmUg
cmVzdWx0ZWQgaW4gbmV3IG9yIG1vZGlmaWVkIGRhdGEgcGxhbmUgYmVoYXZpb3JzIGludm9sdmlu
ZyBlbmNhcHN1bGF0aW9ucy4gVGhhdCBpbmNsdWRlcyBJRVRGIGVmZm9ydHMgbGlrZSBNUExTLCBM
SVNQLCBhbmQgVFJJTEwgYnV0IGFsc28gaW5kdXN0cnkgZWZmb3J0cyBsaWtlIFZ4bGFuIGFuZCBO
VkdSRS4gIFRoZXNlIGNvbGxlY3RpdmVseSBjYW4gYmUgc2VlbiBhcyBhIHNvdXJjZSBvZiBpbnNp
Z2h0IGludG8gdGhlIHByb3BlcnRpZXMgdGhhdCBkYXRhIHBsYW5lcyBuZWVkIHRvIG1lZXQuICBU
aGUgSUVURiBpcyBjdXJyZW50bHkgd29ya2luZyBvbiBwb3RlbnRpYWxseSBuZXcgZW5jYXBzdWxh
dGlvbnMgaW4gTlZPMyBhbmQgU0ZDIGFuZCBjb25zaWRlcmluZyB3b3JraW5nIG9uIEJJRVIuIElu
IGFkZGl0aW9uIHRoZXJlIGlzIHdvcmsgb24gdHVubmVsaW5nIGluIHRoZSBJTlQgYXJlYS4NCg0K
VGhpcyBpcyBhIHNob3J0IHRlcm0gZGVzaWduIHRlYW0gY2hhcnRlcmVkIHRvIGNvbGxlY3QgYW5k
IGNvbnN0cnVjdCB1c2VmdWwgYWR2aWNlIHRvIHBhcnRpZXMgd29ya2luZyBvbiBuZXcgb3IgbW9k
aWZpZWQgZGF0YSBwbGFuZSBiZWhhdmlvcnMgdGhhdCBpbmNsdWRlIGFkZGl0aW9uYWwgZW5jYXBz
dWxhdGlvbnMuICBUaGUgZ29hbCBpcyBmb3IgdGhlIGdyb3VwIHRvIGRvY3VtZW50IHVzZWZ1bCBh
ZHZpY2UgZ2F0aGVyZWQgZnJvbSBpbnRlcmFjdGluZyB3aXRoIG9uZ29pbmcgZWZmb3J0cy4gIEFu
IEludGVybmV0IERyYWZ0IHdpbGwgYmUgcHJvZHVjZWQgZm9yIElFVEY5MiB0byBjYXB0dXJlIHRo
YXQgYWR2aWNlLCB3aGljaCB3aWxsIGJlIGRpc2N1c3NlZCBpbiBSVEdXRy4NCg0KRGF0YSBwbGFu
ZSBlbmNhcHN1bGF0aW9ucyBmYWNlIGEgc2V0IG9mIGNvbW1vbiBpc3N1ZXMgc3VjaCBhczoNCg0K
ICAqIEhvdyB0byBwcm92aWRlIGVudHJvcHkgZm9yIEVDTVANCiAgKiBJc3N1ZXMgYXJvdW5kIHBh
Y2tldCBzaXplIGFuZCBmcmFnbWVudGF0aW9uL3JlYXNzZW1ibHkNCiAgKiBPQU0gLSB3aGF0IHN1
cHBvcnQgaXMgbmVlZGVkIGluIGFuIGVuY2Fwc3VsYXRpb24gZm9ybWF0Pw0KICAqIFNlY3VyaXR5
IGFuZCBwcml2YWN5Lg0KICAqIFFvUw0KICAqIENvbmdlc3Rpb24gQ29uc2lkZXJhdGlvbnMNCiAg
KiBJUHY2IGhlYWRlciBwcm90ZWN0aW9uIChub24temVybyBVRFAgY2hlY2tzdW0gb3ZlciBJUHY2
IGlzc3VlKQ0KICAqIEV4dGVuc2liaWxpdHkgLSBlLmcuLCBmb3IgZXZvbHZpbmcgT0FNLCBzZWN1
cml0eSwgYW5kL29yIGNvbmdlc3Rpb24gY29udHJvbA0KICAqIExheWVyaW5nIG9mIG11bHRpcGxl
IGVuY2Fwc3VsYXRpb25zIGUuZy4sIFNGQyBvdmVyIE5WTzMgb3ZlciBCSUVSDQoNClRoZSBkZXNp
Z24gdGVhbSB3aWxsIHByb3ZpZGUgYWR2aWNlIG9uIHRob3NlIGlzc3Vlcy4gVGhlIGludGVudGlv
biBpcyB0aGF0IGV2ZW4gd2hlcmUgd2UgaGF2ZSBkaWZmZXJlbnQgZW5jYXBzdWxhdGlvbnMgZm9y
IGRpZmZlcmVudCBwdXJwb3NlcyBjYXJyeWluZyBkaWZmZXJlbnQgZGF0YSwgZWFjaCBzdWNoIGVu
Y2Fwc3VsYXRpb24gZG9lc27igJl0IGhhdmUgdG8gcmVpbnZlbnQgdGhlIHdoZWVsIGZvciB0aGUg
YWJvdmUgY29tbW9uIGlzc3Vlcy4NClRoZSBkZXNpZ24gdGVhbSB3aWxsIGxvb2sgYWNyb3NzIHRo
ZSByb3V0aW5nIGFyZWEgaW4gcGFydGljdWxhciBhdCBTRkMsIE5WTzMgYW5kIEJJRVIuIEl0IHdp
bGwgbm90IGJlIGludm9sdmVkIGluIGNvbXBhcmluZyBvciBhbmFseXppbmcgYW55IHBhcnRpY3Vs
YXIgZW5jYXBzdWxhdGlvbiBmb3JtYXRzIHByb3Bvc2VkIGluIHRob3NlIFdHcyBhbmQgQm9GcyBi
dXQgaW5zdGVhZCBmb2N1cyBvbiBjb21tb24gYWR2aWNlLg0KDQpSZWdhcmRzLA0KQWxpYQ0KDQpf
X19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fXw0Kcm91dGluZy1k
aXNjdXNzaW9uIG1haWxpbmcgbGlzdA0Kcm91dGluZy1kaXNjdXNzaW9uQGlldGYub3JnPG1haWx0
bzpyb3V0aW5nLWRpc2N1c3Npb25AaWV0Zi5vcmc+DQpodHRwczovL3d3dy5pZXRmLm9yZy9tYWls
bWFuL2xpc3RpbmZvL3JvdXRpbmctZGlzY3Vzc2lvbg0KDQo=

--_000_A46D9C092EA46F489F135060986AD9FF0F8BD5B6G6W2492americas_
Content-Type: text/html; charset="utf-8"
Content-Transfer-Encoding: base64

PGh0bWwgeG1sbnM6dj0idXJuOnNjaGVtYXMtbWljcm9zb2Z0LWNvbTp2bWwiIHhtbG5zOm89InVy
bjpzY2hlbWFzLW1pY3Jvc29mdC1jb206b2ZmaWNlOm9mZmljZSIgeG1sbnM6dz0idXJuOnNjaGVt
YXMtbWljcm9zb2Z0LWNvbTpvZmZpY2U6d29yZCIgeG1sbnM6bT0iaHR0cDovL3NjaGVtYXMubWlj
cm9zb2Z0LmNvbS9vZmZpY2UvMjAwNC8xMi9vbW1sIiB4bWxucz0iaHR0cDovL3d3dy53My5vcmcv
VFIvUkVDLWh0bWw0MCI+DQo8aGVhZD4NCjxtZXRhIGh0dHAtZXF1aXY9IkNvbnRlbnQtVHlwZSIg
Y29udGVudD0idGV4dC9odG1sOyBjaGFyc2V0PXV0Zi04Ij4NCjxtZXRhIG5hbWU9IkdlbmVyYXRv
ciIgY29udGVudD0iTWljcm9zb2Z0IFdvcmQgMTQgKGZpbHRlcmVkIG1lZGl1bSkiPg0KPHN0eWxl
PjwhLS0NCi8qIEZvbnQgRGVmaW5pdGlvbnMgKi8NCkBmb250LWZhY2UNCgl7Zm9udC1mYW1pbHk6
Q2FsaWJyaTsNCglwYW5vc2UtMToyIDE1IDUgMiAyIDIgNCAzIDIgNDt9DQpAZm9udC1mYWNlDQoJ
e2ZvbnQtZmFtaWx5OlRhaG9tYTsNCglwYW5vc2UtMToyIDExIDYgNCAzIDUgNCA0IDIgNDt9DQov
KiBTdHlsZSBEZWZpbml0aW9ucyAqLw0KcC5Nc29Ob3JtYWwsIGxpLk1zb05vcm1hbCwgZGl2Lk1z
b05vcm1hbA0KCXttYXJnaW46MGluOw0KCW1hcmdpbi1ib3R0b206LjAwMDFwdDsNCglmb250LXNp
emU6MTIuMHB0Ow0KCWZvbnQtZmFtaWx5OiJUaW1lcyBOZXcgUm9tYW4iLCJzZXJpZiI7fQ0KYTps
aW5rLCBzcGFuLk1zb0h5cGVybGluaw0KCXttc28tc3R5bGUtcHJpb3JpdHk6OTk7DQoJY29sb3I6
Ymx1ZTsNCgl0ZXh0LWRlY29yYXRpb246dW5kZXJsaW5lO30NCmE6dmlzaXRlZCwgc3Bhbi5Nc29I
eXBlcmxpbmtGb2xsb3dlZA0KCXttc28tc3R5bGUtcHJpb3JpdHk6OTk7DQoJY29sb3I6cHVycGxl
Ow0KCXRleHQtZGVjb3JhdGlvbjp1bmRlcmxpbmU7fQ0KcA0KCXttc28tc3R5bGUtcHJpb3JpdHk6
OTk7DQoJbXNvLW1hcmdpbi10b3AtYWx0OmF1dG87DQoJbWFyZ2luLXJpZ2h0OjBpbjsNCgltc28t
bWFyZ2luLWJvdHRvbS1hbHQ6YXV0bzsNCgltYXJnaW4tbGVmdDowaW47DQoJZm9udC1zaXplOjEy
LjBwdDsNCglmb250LWZhbWlseToiVGltZXMgTmV3IFJvbWFuIiwic2VyaWYiO30NCnNwYW4uRW1h
aWxTdHlsZTE4DQoJe21zby1zdHlsZS10eXBlOnBlcnNvbmFsLXJlcGx5Ow0KCWZvbnQtZmFtaWx5
OiJDYWxpYnJpIiwic2Fucy1zZXJpZiI7DQoJY29sb3I6IzFGNDk3RDt9DQouTXNvQ2hwRGVmYXVs
dA0KCXttc28tc3R5bGUtdHlwZTpleHBvcnQtb25seTsNCglmb250LWZhbWlseToiQ2FsaWJyaSIs
InNhbnMtc2VyaWYiO30NCkBwYWdlIFdvcmRTZWN0aW9uMQ0KCXtzaXplOjguNWluIDExLjBpbjsN
CgltYXJnaW46MS4waW4gMS4waW4gMS4waW4gMS4waW47fQ0KZGl2LldvcmRTZWN0aW9uMQ0KCXtw
YWdlOldvcmRTZWN0aW9uMTt9DQotLT48L3N0eWxlPjwhLS1baWYgZ3RlIG1zbyA5XT48eG1sPg0K
PG86c2hhcGVkZWZhdWx0cyB2OmV4dD0iZWRpdCIgc3BpZG1heD0iMTAyNiIgLz4NCjwveG1sPjwh
W2VuZGlmXS0tPjwhLS1baWYgZ3RlIG1zbyA5XT48eG1sPg0KPG86c2hhcGVsYXlvdXQgdjpleHQ9
ImVkaXQiPg0KPG86aWRtYXAgdjpleHQ9ImVkaXQiIGRhdGE9IjEiIC8+DQo8L286c2hhcGVsYXlv
dXQ+PC94bWw+PCFbZW5kaWZdLS0+DQo8L2hlYWQ+DQo8Ym9keSBsYW5nPSJFTi1VUyIgbGluaz0i
Ymx1ZSIgdmxpbms9InB1cnBsZSI+DQo8ZGl2IGNsYXNzPSJXb3JkU2VjdGlvbjEiPg0KPHAgY2xh
c3M9Ik1zb05vcm1hbCI+PHNwYW4gc3R5bGU9ImZvbnQtc2l6ZToxMS4wcHQ7Zm9udC1mYW1pbHk6
JnF1b3Q7Q2FsaWJyaSZxdW90OywmcXVvdDtzYW5zLXNlcmlmJnF1b3Q7O2NvbG9yOiMxRjQ5N0Qi
PkhpIEFsaWE8bzpwPjwvbzpwPjwvc3Bhbj48L3A+DQo8cCBjbGFzcz0iTXNvTm9ybWFsIj48c3Bh
biBzdHlsZT0iZm9udC1zaXplOjExLjBwdDtmb250LWZhbWlseTomcXVvdDtDYWxpYnJpJnF1b3Q7
LCZxdW90O3NhbnMtc2VyaWYmcXVvdDs7Y29sb3I6IzFGNDk3RCI+PG86cD4mbmJzcDs8L286cD48
L3NwYW4+PC9wPg0KPHAgY2xhc3M9Ik1zb05vcm1hbCI+PHNwYW4gc3R5bGU9ImZvbnQtc2l6ZTox
MS4wcHQ7Zm9udC1mYW1pbHk6JnF1b3Q7Q2FsaWJyaSZxdW90OywmcXVvdDtzYW5zLXNlcmlmJnF1
b3Q7O2NvbG9yOiMxRjQ5N0QiPkkgdGhpbmsgaXQgd291bGQgYmUgZ29vZCBmb3IgdGhlIGRlc2ln
biB0ZWFtIHRvICZuYnNwO2Fsc28gaW5jbHVkZSBmb3IgcmVmZXJlbmNlIGNvbXBhcmlzb25zIG9m
IHRoZSBMMiBlbmNhcHN1bGF0aW9ucyBmcm9tIElFRUUgODAyLjEgc3VjaCBhcyBQcm92aWRlciBi
YWNrYm9uZSBCcmlkZ2luZyhQQkIpDQogYWthIE1hYy1pbi1NQUMgYW5kIElFRUUgODAyLjFRYnAg
4oCTIEVxdWFsIENvc3QgTXVsdGlwYXRoIChFQ01QKSAmbmJzcDsoYWxzbyBhIE1hYy1pbi1NQUMg
ZW5jYXBzKSB3aGljaCBoYXZlIHNvbWUgY29tbW9uIHByb3BlcnRpZXMgd2l0aCBkYXRhIHBsYW5l
IGVuY2Fwc3VsYXRpb25zIGluIGdlbmVyYWwuICZuYnNwO0FzIHdpdGggUFdFIHRoZSBkZXNpZ25l
cnMgb2YgdGhlc2UgZW5jYXBzdWxhdGlvbnMgaGF2ZSBncmFwcGxlZCB3aXRoIGEgbG90IG9mIHRo
ZSBzYW1lDQogaXNzdWVzLiA8bzpwPjwvbzpwPjwvc3Bhbj48L3A+DQo8cCBjbGFzcz0iTXNvTm9y
bWFsIj48c3BhbiBzdHlsZT0iZm9udC1zaXplOjExLjBwdDtmb250LWZhbWlseTomcXVvdDtDYWxp
YnJpJnF1b3Q7LCZxdW90O3NhbnMtc2VyaWYmcXVvdDs7Y29sb3I6IzFGNDk3RCI+PG86cD4mbmJz
cDs8L286cD48L3NwYW4+PC9wPg0KPHAgY2xhc3M9Ik1zb05vcm1hbCI+PHNwYW4gc3R5bGU9ImZv
bnQtc2l6ZToxMS4wcHQ7Zm9udC1mYW1pbHk6JnF1b3Q7Q2FsaWJyaSZxdW90OywmcXVvdDtzYW5z
LXNlcmlmJnF1b3Q7O2NvbG9yOiMxRjQ5N0QiPk9uZSAmbmJzcDthZGRpdGlvbiB0byB5b3VyIGxp
c3QgdGhlc2UgTDIgZW5jYXBzdWxhdGlvbnMgJm5ic3A7aGF2ZSBzcGVjaWZpYyBzdXBwb3J0IGZv
ciBtdWx0aWNhc3QgdGhhdCBjYW4gYmUgdXRpbGl6ZWQgaW4gdGhlIGluIHRoZSB1bmRlcmxheSBk
YXRhIHBsYW5lLg0KPG86cD48L286cD48L3NwYW4+PC9wPg0KPHAgY2xhc3M9Ik1zb05vcm1hbCI+
PHNwYW4gc3R5bGU9ImZvbnQtc2l6ZToxMS4wcHQ7Zm9udC1mYW1pbHk6JnF1b3Q7Q2FsaWJyaSZx
dW90OywmcXVvdDtzYW5zLXNlcmlmJnF1b3Q7O2NvbG9yOiMxRjQ5N0QiPjxvOnA+Jm5ic3A7PC9v
OnA+PC9zcGFuPjwvcD4NCjxwIGNsYXNzPSJNc29Ob3JtYWwiPjxzcGFuIHN0eWxlPSJmb250LXNp
emU6MTEuMHB0O2ZvbnQtZmFtaWx5OiZxdW90O0NhbGlicmkmcXVvdDssJnF1b3Q7c2Fucy1zZXJp
ZiZxdW90Oztjb2xvcjojMUY0OTdEIj5DaGVlcnMsPGJyPg0KRG9uIDxvOnA+PC9vOnA+PC9zcGFu
PjwvcD4NCjxwIGNsYXNzPSJNc29Ob3JtYWwiPjxzcGFuIHN0eWxlPSJmb250LXNpemU6MTEuMHB0
O2ZvbnQtZmFtaWx5OiZxdW90O0NhbGlicmkmcXVvdDssJnF1b3Q7c2Fucy1zZXJpZiZxdW90Oztj
b2xvcjojMUY0OTdEIj48bzpwPiZuYnNwOzwvbzpwPjwvc3Bhbj48L3A+DQo8ZGl2IHN0eWxlPSJi
b3JkZXI6bm9uZTtib3JkZXItbGVmdDpzb2xpZCBibHVlIDEuNXB0O3BhZGRpbmc6MGluIDBpbiAw
aW4gNC4wcHQiPg0KPGRpdj4NCjxkaXYgc3R5bGU9ImJvcmRlcjpub25lO2JvcmRlci10b3A6c29s
aWQgI0I1QzRERiAxLjBwdDtwYWRkaW5nOjMuMHB0IDBpbiAwaW4gMGluIj4NCjxwIGNsYXNzPSJN
c29Ob3JtYWwiPjxiPjxzcGFuIHN0eWxlPSJmb250LXNpemU6MTAuMHB0O2ZvbnQtZmFtaWx5OiZx
dW90O1RhaG9tYSZxdW90OywmcXVvdDtzYW5zLXNlcmlmJnF1b3Q7Ij5Gcm9tOjwvc3Bhbj48L2I+
PHNwYW4gc3R5bGU9ImZvbnQtc2l6ZToxMC4wcHQ7Zm9udC1mYW1pbHk6JnF1b3Q7VGFob21hJnF1
b3Q7LCZxdW90O3NhbnMtc2VyaWYmcXVvdDsiPiByb3V0aW5nLWRpc2N1c3Npb24gW21haWx0bzpy
b3V0aW5nLWRpc2N1c3Npb24tYm91bmNlc0BpZXRmLm9yZ10NCjxiPk9uIEJlaGFsZiBPZiA8L2I+
QWxpYSBBdGxhczxicj4NCjxiPlNlbnQ6PC9iPiBXZWRuZXNkYXksIERlY2VtYmVyIDEwLCAyMDE0
IDk6MzkgQU08YnI+DQo8Yj5Ubzo8L2I+IEFuZHJldyBHLiBNYWxpczxicj4NCjxiPkNjOjwvYj4g
cm91dGluZy1kaXNjdXNzaW9uQGlldGYub3JnPGJyPg0KPGI+U3ViamVjdDo8L2I+IFJlOiByb3V0
aW5nIGFyZWEgZGVzaWduIHRlYW0gb24gZGF0YXBsYW5lIGVuY2Fwc3VsYXRpb24gY29uc2lkZXJh
dGlvbnM8bzpwPjwvbzpwPjwvc3Bhbj48L3A+DQo8L2Rpdj4NCjwvZGl2Pg0KPHAgY2xhc3M9Ik1z
b05vcm1hbCI+PG86cD4mbmJzcDs8L286cD48L3A+DQo8cD5IaSBBbmR5LDxvOnA+PC9vOnA+PC9w
Pg0KPHA+QWJzb2x1dGVseSB0cnVlLiZuYnNwOyZuYnNwOyBJIGFwb2xvZ2l6ZSBmb3IgdGhlIG92
ZXJzaWdodC4mbmJzcDsmbmJzcDsgUHN1ZWRvLXdpcmVzIGFyZSBhbm90aGVyIGVuY2Fwc3VsYXRp
b24gdGhhdCB3ZSBjYW4gbGVhcm4gZnJvbS4NCjxvOnA+PC9vOnA+PC9wPg0KPHA+SSBleHBlY3Qg
dGhlIGRlc2lnbiB0ZWFtIHRvIGJlIHJlYWNoaW5nIG91dCB0byBnZXQgbW9yZSBpbnNpZ2h0IG9u
IHRoZXNlIGRpZmZlcmVudCBpc3N1ZXMuDQo8bzpwPjwvbzpwPjwvcD4NCjxwPlJlZ2FyZHMgPGJy
Pg0KQWxpYTxvOnA+PC9vOnA+PC9wPg0KPGRpdj4NCjxwIGNsYXNzPSJNc29Ob3JtYWwiPk9uIERl
YyAxMCwgMjAxNCA5OjI3IEFNLCAmcXVvdDtBbmRyZXcgRy4gTWFsaXMmcXVvdDsgJmx0OzxhIGhy
ZWY9Im1haWx0bzphZ21hbGlzQGdtYWlsLmNvbSI+YWdtYWxpc0BnbWFpbC5jb208L2E+Jmd0OyB3
cm90ZTo8bzpwPjwvbzpwPjwvcD4NCjxkaXY+DQo8cCBjbGFzcz0iTXNvTm9ybWFsIj5BbGlhLDxv
OnA+PC9vOnA+PC9wPg0KPGRpdj4NCjxwIGNsYXNzPSJNc29Ob3JtYWwiPjxvOnA+Jm5ic3A7PC9v
OnA+PC9wPg0KPGRpdj4NCjxwIGNsYXNzPSJNc29Ob3JtYWwiPlRvIGhpamFjayB0aGlzIGRpc2N1
c3Npb24gYmFjayB0byB5b3VyIG9yaWdpbmFsIHBvc3QsIEknbSB2ZXJ5IHN1cnByaXNlZCB0byBz
ZWUgbm8gbWVudGlvbiBvZiBQQUxTIGFueXdoZXJlLiBXZSBpbiBQQUxTIChhbmQgUFdFMyBiZWZv
cmUgdGhhdCkgaGF2ZSBwbGVudHkgb2YgZXhwZXJpZW5jZSB3aXRoIGRhdGEgcGxhbmUgZW5jYXBz
dWxhdGlvbnMsIGFuZCB3ZSBhbHJlYWR5IGhhdmUgc29sdXRpb25zIGZvciBhDQogbnVtYmVyIG9m
IHRoZSBpc3N1ZXMgaW4geW91ciBsaXN0LCBpbmNsdWRpbmcgRUNNUCAoUkZDIDYzOTEpLCBwYWNr
ZXQgc2l6ZSBhbmQgZnJhZ21lbnRhdGlvbiAoNDYyMyksIE9BTSAoNTA4NSBhbmQgb3RoZXJzKSwg
YW5kIGEgZHJhZnQgb24gY29uZ2VzdGlvbiBjb25zaWRlcmF0aW9ucyBqdXN0IGluIHRoZSBwcm9j
ZXNzIG9mIGZpbmlzaGluZyB1cC4gUFdzIGhhdmUgYmVlbiBleHRyZW1lbHkgc3VjY2Vzc2Z1bCBp
biB0aGUgbWFya2V0cGxhY2UuDQogU28gSSBob3BlIHRoZSBkZXNpZ24gdGVhbSBrZWVwcyB1cyBp
biBtaW5kIGFzIHdlbGwuPG86cD48L286cD48L3A+DQo8L2Rpdj4NCjwvZGl2Pg0KPGRpdj4NCjxw
IGNsYXNzPSJNc29Ob3JtYWwiPjxvOnA+Jm5ic3A7PC9vOnA+PC9wPg0KPC9kaXY+DQo8ZGl2Pg0K
PHAgY2xhc3M9Ik1zb05vcm1hbCI+Q2hlZXJzLDxvOnA+PC9vOnA+PC9wPg0KPC9kaXY+DQo8ZGl2
Pg0KPHAgY2xhc3M9Ik1zb05vcm1hbCI+QW5keTxvOnA+PC9vOnA+PC9wPg0KPC9kaXY+DQo8L2Rp
dj4NCjxkaXY+DQo8cCBjbGFzcz0iTXNvTm9ybWFsIj48bzpwPiZuYnNwOzwvbzpwPjwvcD4NCjxk
aXY+DQo8cCBjbGFzcz0iTXNvTm9ybWFsIj5PbiBUdWUsIERlYyA5LCAyMDE0IGF0IDU6NDYgUE0s
IEFsaWEgQXRsYXMgJmx0OzxhIGhyZWY9Im1haWx0bzpha2F0bGFzQGdtYWlsLmNvbSIgdGFyZ2V0
PSJfYmxhbmsiPmFrYXRsYXNAZ21haWwuY29tPC9hPiZndDsgd3JvdGU6PG86cD48L286cD48L3A+
DQo8ZGl2Pg0KPHAgY2xhc3M9Ik1zb05vcm1hbCI+SSBoYXZlIGNoYXJ0ZXJlZCBhIFJvdXRpbmcg
QXJlYSBEZXNpZ24gVGVhbSB0byB3b3JrIG9uIGRhdGEtcGxhbmUgZW5jYXBzdWxhdGlvbiBjb25z
aWRlcmF0aW9ucy48bzpwPjwvbzpwPjwvcD4NCjxkaXY+DQo8cCBjbGFzcz0iTXNvTm9ybWFsIj48
bzpwPiZuYnNwOzwvbzpwPjwvcD4NCjwvZGl2Pg0KPGRpdj4NCjxwIGNsYXNzPSJNc29Ob3JtYWwi
PkkndmUgYmNjJ2QgbnZvMywgc2ZjLCBiaWVyLCBhbmQgcnRnd2cgYXMgdGhlIG1vc3QgZGlyZWN0
bHkgcmVsZXZhbnQuJm5ic3A7IFBsZWFzZSBrZWVwIGFueSBjb252ZXJzYXRpb24gaW4gb25lIHBs
YWNlIG9uIHJvdXRpbmctZGlzY3Vzc2lvbi48bzpwPjwvbzpwPjwvcD4NCjxkaXY+DQo8cCBjbGFz
cz0iTXNvTm9ybWFsIj48bzpwPiZuYnNwOzwvbzpwPjwvcD4NCjwvZGl2Pg0KPGRpdj4NCjxwIGNs
YXNzPSJNc29Ob3JtYWwiPkVyaWsgTm9yZG1hcmsgaGFzIGtpbmRseSBhZ3JlZWQgdG8gbGVhZCB0
aGlzIGRlc2lnbiB0ZWFtLiZuYnNwOyBUaGUgbWVtYmVycyBvZiB0aGUgZGVzaWduPG86cD48L286
cD48L3A+DQo8L2Rpdj4NCjxkaXY+DQo8cCBjbGFzcz0iTXNvTm9ybWFsIj50ZWFtIGFyZTo8bzpw
PjwvbzpwPjwvcD4NCjwvZGl2Pg0KPGRpdj4NCjxwIGNsYXNzPSJNc29Ob3JtYWwiPjxvOnA+Jm5i
c3A7PC9vOnA+PC9wPg0KPC9kaXY+DQo8ZGl2Pg0KPGRpdj4NCjxwIGNsYXNzPSJNc29Ob3JtYWwi
PjxzcGFuIHN0eWxlPSJmb250LXNpemU6MTAuMHB0Ij4mbmJzcDsgQWxiZXJ0IFRpYW4gJmx0Ozxh
IGhyZWY9Im1haWx0bzphbGJlcnQudGlhbkBlcmljc3Nvbi5jb20iIHRhcmdldD0iX2JsYW5rIj5h
bGJlcnQudGlhbkBlcmljc3Nvbi5jb208L2E+Jmd0OzxvOnA+PC9vOnA+PC9zcGFuPjwvcD4NCjwv
ZGl2Pg0KPGRpdj4NCjxwIGNsYXNzPSJNc29Ob3JtYWwiPjxzcGFuIHN0eWxlPSJmb250LXNpemU6
MTAuMHB0Ij4mbmJzcDsgRXJpayBOb3JkbWFyayAmbHQ7PGEgaHJlZj0ibWFpbHRvOm5vcmRtYXJr
QHNvbmljLm5ldCIgdGFyZ2V0PSJfYmxhbmsiPm5vcmRtYXJrQHNvbmljLm5ldDwvYT4mZ3Q7PGJy
Pg0KJm5ic3A7IEplc3NlIEdyb3NzICZsdDs8YSBocmVmPSJtYWlsdG86amdyb3NzQHZtd2FyZS5j
b20iIHRhcmdldD0iX2JsYW5rIj5qZ3Jvc3NAdm13YXJlLmNvbTwvYT4mZ3Q7PGJyPg0KJm5ic3A7
IEpvbiBIdWRzb24gJmx0OzxhIGhyZWY9Im1haWx0bzpqb24uaHVkc29uQGdtYWlsLmNvbSIgdGFy
Z2V0PSJfYmxhbmsiPmpvbi5odWRzb25AZ21haWwuY29tPC9hPiZndDs8YnI+DQombmJzcDsgTGFy
cnkgS3JlZWdlciAoa3JlZWdlcikgJmx0OzxhIGhyZWY9Im1haWx0bzprcmVlZ2VyQGNpc2NvLmNv
bSIgdGFyZ2V0PSJfYmxhbmsiPmtyZWVnZXJAY2lzY28uY29tPC9hPiZndDs8YnI+DQombmJzcDsg
UGFua2FqIEdhcmcgJmx0OzxhIGhyZWY9Im1haWx0bzpHYXJnLlBhbmthakBtaWNyb3NvZnQuY29t
IiB0YXJnZXQ9Il9ibGFuayI+R2FyZy5QYW5rYWpAbWljcm9zb2Z0LmNvbTwvYT4mZ3Q7PGJyPg0K
Jm5ic3A7IFBhdCBUaGFsZXIgJmx0OzxhIGhyZWY9Im1haWx0bzpwdGhhbGVyQGJyb2FkY29tLmNv
bSIgdGFyZ2V0PSJfYmxhbmsiPnB0aGFsZXJAYnJvYWRjb20uY29tPC9hPiZndDs8YnI+DQombmJz
cDsgVG9tIEhlcmJlcnQgJmx0OzxhIGhyZWY9Im1haWx0bzp0aGVyYmVydEBnb29nbGUuY29tIiB0
YXJnZXQ9Il9ibGFuayI+dGhlcmJlcnRAZ29vZ2xlLmNvbTwvYT4mZ3Q7PG86cD48L286cD48L3Nw
YW4+PC9wPg0KPC9kaXY+DQo8L2Rpdj4NCjxkaXY+DQo8cCBjbGFzcz0iTXNvTm9ybWFsIj48c3Bh
biBzdHlsZT0iZm9udC1zaXplOjEwLjBwdCI+PG86cD4mbmJzcDs8L286cD48L3NwYW4+PC9wPg0K
PC9kaXY+DQo8ZGl2Pg0KPHAgY2xhc3M9Ik1zb05vcm1hbCI+PHNwYW4gc3R5bGU9ImZvbnQtc2l6
ZToxMC4wcHQiPlRoZSBtYWlsaW5nIGxpc3QsIDxhIGhyZWY9Im1haWx0bzpyZ3QtZHQtZW5jYXAt
Y29uc2lkZXJhdGlvbnNAaWV0Zi5vcmciIHRhcmdldD0iX2JsYW5rIj4NCnJndC1kdC1lbmNhcC1j
b25zaWRlcmF0aW9uc0BpZXRmLm9yZzwvYT4sIGlzIGNsb3NlZCBidXQgdGhlIGFyY2hpdmVzIGFy
ZTxvOnA+PC9vOnA+PC9zcGFuPjwvcD4NCjwvZGl2Pg0KPGRpdj4NCjxwIGNsYXNzPSJNc29Ob3Jt
YWwiPjxzcGFuIHN0eWxlPSJmb250LXNpemU6MTAuMHB0Ij5wdWJsaWNseSBhdmFpbGFibGUgYXQ6
PG86cD48L286cD48L3NwYW4+PC9wPg0KPC9kaXY+DQo8ZGl2Pg0KPHAgY2xhc3M9Ik1zb05vcm1h
bCI+PHNwYW4gc3R5bGU9ImZvbnQtc2l6ZToxMC4wcHQiPiZuYnNwOyAmbmJzcDs8YSBocmVmPSJo
dHRwOi8vd3d3LmlldGYub3JnL21haWwtYXJjaGl2ZS93ZWIvcnRnLWR0LWVuY2FwLWNvbnNpZGVy
YXRpb25zL2N1cnJlbnQvbWFpbGxpc3QuaHRtbCIgdGFyZ2V0PSJfYmxhbmsiPmh0dHA6Ly93d3cu
aWV0Zi5vcmcvbWFpbC1hcmNoaXZlL3dlYi9ydGctZHQtZW5jYXAtY29uc2lkZXJhdGlvbnMvY3Vy
cmVudC9tYWlsbGlzdC5odG1sPC9hPjxvOnA+PC9vOnA+PC9zcGFuPjwvcD4NCjwvZGl2Pg0KPGRp
dj4NCjxwIGNsYXNzPSJNc29Ob3JtYWwiPjxzcGFuIHN0eWxlPSJmb250LXNpemU6MTAuMHB0Ij48
bzpwPiZuYnNwOzwvbzpwPjwvc3Bhbj48L3A+DQo8L2Rpdj4NCjxkaXY+DQo8cCBjbGFzcz0iTXNv
Tm9ybWFsIj48c3BhbiBzdHlsZT0iZm9udC1zaXplOjEwLjBwdCI+VGhlIERlc2lnbiBUZWFtIGlz
IGNoYXJ0ZXJlZCBhcyBmb2xsb3dzOjxvOnA+PC9vOnA+PC9zcGFuPjwvcD4NCjwvZGl2Pg0KPGRp
dj4NCjxwIGNsYXNzPSJNc29Ob3JtYWwiPjxzcGFuIHN0eWxlPSJmb250LXNpemU6MTAuMHB0Ij48
bzpwPiZuYnNwOzwvbzpwPjwvc3Bhbj48L3A+DQo8L2Rpdj4NCjxkaXY+DQo8cCBjbGFzcz0iTXNv
Tm9ybWFsIj5UaGVyZSBoYXZlIGJlZW4gbXVsdGlwbGUgZWZmb3J0cyBvdmVyIHRoZSB5ZWFycyB0
aGF0IGhhdmUgcmVzdWx0ZWQgaW4gbmV3IG9yIG1vZGlmaWVkIGRhdGEgcGxhbmUgYmVoYXZpb3Jz
IGludm9sdmluZyBlbmNhcHN1bGF0aW9ucy4gVGhhdCBpbmNsdWRlcyBJRVRGIGVmZm9ydHMgbGlr
ZSBNUExTLCBMSVNQLCBhbmQgVFJJTEwgYnV0IGFsc28gaW5kdXN0cnkgZWZmb3J0cyBsaWtlIFZ4
bGFuIGFuZCBOVkdSRS4mbmJzcDsNCiBUaGVzZSBjb2xsZWN0aXZlbHkgY2FuIGJlIHNlZW4gYXMg
YSBzb3VyY2Ugb2YgaW5zaWdodCBpbnRvIHRoZSBwcm9wZXJ0aWVzIHRoYXQgZGF0YSBwbGFuZXMg
bmVlZCB0byBtZWV0LiZuYnNwOyBUaGUgSUVURiBpcyBjdXJyZW50bHkgd29ya2luZyBvbiBwb3Rl
bnRpYWxseSBuZXcgZW5jYXBzdWxhdGlvbnMgaW4gTlZPMyBhbmQgU0ZDIGFuZCBjb25zaWRlcmlu
ZyB3b3JraW5nIG9uIEJJRVIuIEluIGFkZGl0aW9uIHRoZXJlIGlzIHdvcmsgb24gdHVubmVsaW5n
DQogaW4gdGhlIElOVCBhcmVhLjxicj4NCjxicj4NClRoaXMgaXMgYSBzaG9ydCB0ZXJtIGRlc2ln
biB0ZWFtIGNoYXJ0ZXJlZCB0byBjb2xsZWN0IGFuZCBjb25zdHJ1Y3QgdXNlZnVsIGFkdmljZSB0
byBwYXJ0aWVzIHdvcmtpbmcgb24gbmV3IG9yIG1vZGlmaWVkIGRhdGEgcGxhbmUgYmVoYXZpb3Jz
IHRoYXQgaW5jbHVkZSBhZGRpdGlvbmFsIGVuY2Fwc3VsYXRpb25zLiZuYnNwOyBUaGUgZ29hbCBp
cyBmb3IgdGhlIGdyb3VwIHRvIGRvY3VtZW50IHVzZWZ1bCBhZHZpY2UgZ2F0aGVyZWQgZnJvbSBp
bnRlcmFjdGluZw0KIHdpdGggb25nb2luZyBlZmZvcnRzLiZuYnNwOyBBbiBJbnRlcm5ldCBEcmFm
dCB3aWxsIGJlIHByb2R1Y2VkIGZvciBJRVRGOTIgdG8gY2FwdHVyZSB0aGF0IGFkdmljZSwgd2hp
Y2ggd2lsbCBiZSBkaXNjdXNzZWQgaW4gUlRHV0cuPGJyPg0KPGJyPg0KRGF0YSBwbGFuZSBlbmNh
cHN1bGF0aW9ucyBmYWNlIGEgc2V0IG9mIGNvbW1vbiBpc3N1ZXMgc3VjaCBhczo8YnI+DQo8YnI+
DQombmJzcDsgKiBIb3cgdG8gcHJvdmlkZSBlbnRyb3B5IGZvciBFQ01QPGJyPg0KJm5ic3A7ICog
SXNzdWVzIGFyb3VuZCBwYWNrZXQgc2l6ZSBhbmQgZnJhZ21lbnRhdGlvbi9yZWFzc2VtYmx5PGJy
Pg0KJm5ic3A7ICogT0FNIC0gd2hhdCBzdXBwb3J0IGlzIG5lZWRlZCBpbiBhbiBlbmNhcHN1bGF0
aW9uIGZvcm1hdD88YnI+DQombmJzcDsgKiBTZWN1cml0eSBhbmQgcHJpdmFjeS48YnI+DQombmJz
cDsgKiZuYnNwO1FvUzxicj4NCiZuYnNwOyAqJm5ic3A7Q29uZ2VzdGlvbiBDb25zaWRlcmF0aW9u
czxicj4NCiZuYnNwOyAqJm5ic3A7SVB2NiBoZWFkZXIgcHJvdGVjdGlvbiAobm9uLXplcm8gVURQ
IGNoZWNrc3VtIG92ZXIgSVB2NiBpc3N1ZSk8YnI+DQombmJzcDsgKiBFeHRlbnNpYmlsaXR5IC0g
ZS5nLiwgZm9yIGV2b2x2aW5nIE9BTSwgc2VjdXJpdHksIGFuZC9vciBjb25nZXN0aW9uIGNvbnRy
b2w8YnI+DQombmJzcDsgKiBMYXllcmluZyBvZiBtdWx0aXBsZSBlbmNhcHN1bGF0aW9ucyBlLmcu
LCBTRkMgb3ZlciBOVk8zIG92ZXIgQklFUjxvOnA+PC9vOnA+PC9wPg0KPC9kaXY+DQo8ZGl2Pg0K
PHAgY2xhc3M9Ik1zb05vcm1hbCI+PG86cD4mbmJzcDs8L286cD48L3A+DQo8L2Rpdj4NCjxkaXY+
DQo8cCBjbGFzcz0iTXNvTm9ybWFsIiBzdHlsZT0ibWFyZ2luLWJvdHRvbToxMi4wcHQiPlRoZSBk
ZXNpZ24gdGVhbSB3aWxsIHByb3ZpZGUgYWR2aWNlIG9uIHRob3NlIGlzc3Vlcy4gVGhlIGludGVu
dGlvbiBpcyB0aGF0IGV2ZW4gd2hlcmUgd2UgaGF2ZSBkaWZmZXJlbnQgZW5jYXBzdWxhdGlvbnMg
Zm9yIGRpZmZlcmVudCBwdXJwb3NlcyBjYXJyeWluZyBkaWZmZXJlbnQgZGF0YSwgZWFjaCBzdWNo
IGVuY2Fwc3VsYXRpb24gZG9lc27igJl0IGhhdmUgdG8NCiByZWludmVudCB0aGUgd2hlZWwgZm9y
IHRoZSBhYm92ZSBjb21tb24gaXNzdWVzLjxvOnA+PC9vOnA+PC9wPg0KPC9kaXY+DQo8ZGl2Pg0K
PHAgY2xhc3M9Ik1zb05vcm1hbCI+VGhlIGRlc2lnbiB0ZWFtIHdpbGwgbG9vayBhY3Jvc3MgdGhl
IHJvdXRpbmcgYXJlYSBpbiBwYXJ0aWN1bGFyIGF0IFNGQywgTlZPMyBhbmQgQklFUi4gSXQgd2ls
bCBub3QgYmUgaW52b2x2ZWQgaW4gY29tcGFyaW5nIG9yIGFuYWx5emluZyBhbnkgcGFydGljdWxh
ciBlbmNhcHN1bGF0aW9uIGZvcm1hdHMgcHJvcG9zZWQgaW4gdGhvc2UgV0dzIGFuZCBCb0ZzIGJ1
dCBpbnN0ZWFkIGZvY3VzIG9uIGNvbW1vbiBhZHZpY2UuPG86cD48L286cD48L3A+DQo8L2Rpdj4N
CjxkaXY+DQo8cCBjbGFzcz0iTXNvTm9ybWFsIj48bzpwPiZuYnNwOzwvbzpwPjwvcD4NCjwvZGl2
Pg0KPGRpdj4NCjxwIGNsYXNzPSJNc29Ob3JtYWwiPlJlZ2FyZHMsPG86cD48L286cD48L3A+DQo8
L2Rpdj4NCjxkaXY+DQo8cCBjbGFzcz0iTXNvTm9ybWFsIj5BbGlhPG86cD48L286cD48L3A+DQo8
L2Rpdj4NCjwvZGl2Pg0KPC9kaXY+DQo8cCBjbGFzcz0iTXNvTm9ybWFsIiBzdHlsZT0ibWFyZ2lu
LWJvdHRvbToxMi4wcHQiPjxicj4NCl9fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19f
X19fX19fX19fX19fPGJyPg0Kcm91dGluZy1kaXNjdXNzaW9uIG1haWxpbmcgbGlzdDxicj4NCjxh
IGhyZWY9Im1haWx0bzpyb3V0aW5nLWRpc2N1c3Npb25AaWV0Zi5vcmciIHRhcmdldD0iX2JsYW5r
Ij5yb3V0aW5nLWRpc2N1c3Npb25AaWV0Zi5vcmc8L2E+PGJyPg0KPGEgaHJlZj0iaHR0cHM6Ly93
d3cuaWV0Zi5vcmcvbWFpbG1hbi9saXN0aW5mby9yb3V0aW5nLWRpc2N1c3Npb24iIHRhcmdldD0i
X2JsYW5rIj5odHRwczovL3d3dy5pZXRmLm9yZy9tYWlsbWFuL2xpc3RpbmZvL3JvdXRpbmctZGlz
Y3Vzc2lvbjwvYT48bzpwPjwvbzpwPjwvcD4NCjwvZGl2Pg0KPHAgY2xhc3M9Ik1zb05vcm1hbCI+
PG86cD4mbmJzcDs8L286cD48L3A+DQo8L2Rpdj4NCjwvZGl2Pg0KPC9kaXY+DQo8L2Rpdj4NCjwv
Ym9keT4NCjwvaHRtbD4NCg==

--_000_A46D9C092EA46F489F135060986AD9FF0F8BD5B6G6W2492americas_--


From nobody Wed Dec 10 12:25:28 2014
Return-Path: <dwing@cisco.com>
X-Original-To: routing-discussion@ietfa.amsl.com
Delivered-To: routing-discussion@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id BE5FE1A908C for <routing-discussion@ietfa.amsl.com>; Wed, 10 Dec 2014 12:25:22 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -14.211
X-Spam-Level: 
X-Spam-Status: No, score=-14.211 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, MIME_8BIT_HEADER=0.3, RCVD_IN_DNSWL_HI=-5, SPF_PASS=-0.001, T_RP_MATCHES_RCVD=-0.01, USER_IN_DEF_DKIM_WL=-7.5] 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 uYPCUGd5cESL for <routing-discussion@ietfa.amsl.com>; Wed, 10 Dec 2014 12:25:18 -0800 (PST)
Received: from rcdn-iport-9.cisco.com (rcdn-iport-9.cisco.com [173.37.86.80]) (using TLSv1 with cipher RC4-SHA (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id B717B1A90DD for <routing-discussion@ietf.org>; Wed, 10 Dec 2014 12:24:55 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=cisco.com; i=@cisco.com; l=10434; q=dns/txt; s=iport; t=1418243095; x=1419452695; h=mime-version:subject:from:in-reply-to:date:cc: content-transfer-encoding:message-id:references:to; bh=UdAI1k4iKqTf0DALJLNEvJ/CJreRO3s0GVo34rAPNbM=; b=FxlgwWMPUTZJf7xamA7OhP8qjYQxlQy0RsYQc517tFJrz4bAtd0h+rT+ m2dIIkJMEuC9SYj27zt4LQ4fMViEkKzbOKIoanaPQKAAEx0OMtN6j9j9u j+jjdpcCRNk8HO0v0OlPCLgaddgorItQjgh7HFdDdj9wqRleZC7lEOwQ3 o=;
X-IronPort-AV: E=Sophos;i="5.07,553,1413244800"; d="scan'208";a="376103899"
Received: from alln-core-5.cisco.com ([173.36.13.138]) by rcdn-iport-9.cisco.com with ESMTP; 10 Dec 2014 20:24:55 +0000
Received: from [10.24.231.108] ([10.24.231.108]) by alln-core-5.cisco.com (8.14.5/8.14.5) with ESMTP id sBAKOn5Z003910 (version=TLSv1/SSLv3 cipher=AES128-SHA bits=128 verify=NO); Wed, 10 Dec 2014 20:24:52 GMT
Content-Type: text/plain; charset=us-ascii
Mime-Version: 1.0 (Mac OS X Mail 7.3 \(1878.6\))
Subject: Re: dataplane encapsulation considerations - checksums
From: =?utf-8?Q?=F0=9F=94=93Dan_Wing?= <dwing@cisco.com>
In-Reply-To: <EB9B93801780FD4CA165E0FBCB3C3E672B1EABCC@SJEXCHMB09.corp.ad.broadcom.com>
Date: Wed, 10 Dec 2014 12:24:49 -0800
Content-Transfer-Encoding: quoted-printable
Message-Id: <9415ED06-B9B6-4B04-AC04-441C8E4273C0@cisco.com>
References: <CAG4d1rd60hK8=WtYw-nid_Z7Z8+TvdzA52fNx3pFjND+eDWAfA@mail.gmail.com>,  <54877D58.9050002@cisco.com> <DB4PR06MB457F278EAF9C84BCA20E665AD620@DB4PR06MB457.eurprd06.prod.outlook.com>, <54883947.8000302@cisco.com> <1418217891573.89120@surrey.ac.uk> <5488728F.5030003@cisco.com> <EB9B93801780FD4CA165E0FBCB3C3E672B1EABCC@SJEXCHMB09.corp.ad.broadcom.com>
To: Pat Thaler <pthaler@broadcom.com>
X-Mailer: Apple Mail (2.1878.6)
Archived-At: http://mailarchive.ietf.org/arch/msg/routing-discussion/ksUbF5Zw8YAcxYmcWDLc5t_IgdU
Cc: "routing-discussion@ietf.org" <routing-discussion@ietf.org>, "l.wood@surrey.ac.uk" <l.wood@surrey.ac.uk>, "stbryant@cisco.com" <stbryant@cisco.com>
X-BeenThere: routing-discussion@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: Routing Area General mailing list <routing-discussion.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/routing-discussion>, <mailto:routing-discussion-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/routing-discussion/>
List-Post: <mailto:routing-discussion@ietf.org>
List-Help: <mailto:routing-discussion-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/routing-discussion>, <mailto:routing-discussion-request@ietf.org?subject=subscribe>
X-List-Received-Date: Wed, 10 Dec 2014 20:25:22 -0000

On Dec 10, 2014, at 11:42 AM, Pat Thaler <pthaler@broadcom.com> wrote:

> "If we look at them in detail they are interesting because if the no =
ports
> are c/s errors as you hypothesis, then only 1/3 of the errors are =
seemingly
> caught by the c/s. I would thus expect  you to be arguing strongly
> that we need to deprecate the existing c/s in favour of something
> much stronger such as fletcher, or ideally a crypto checksum."
>=20
> The no port errors could be happening on a much larger base of traffic =
than the checksum errors.=20

Would a (UDP a.k.a. "Unix-style") traceroute increment the 'no port' =
error?

-d


> Check sum is only being checked on traffic destined for the router.=20
> Arrival of a packet with no corresponding port could be due to an =
error in the IP address of any packet on the network - presumably a much =
larger amount of traffic.=20
> Checksum might be catching most of the errors but a very small portion =
of the network traffic has the router as a destination so the router is =
more likely to see a corrupted packet arrive (something where the =
destination IP changed but with good checksum and bad port number) than =
a checksum error.
>=20
> However, the reason that checksum is being urged is to prevent =
delivering packets to the wrong tenants because of an undetected error =
causing misdirection.  If the no port traffic is from corrupted packets =
that the checksum didn't catch, checksum isn't doing a thorough job of =
doing that. We don't know what % is getting misdirected because we don't =
have a number for the total traffic.  Of course, that "if" is a big =
assumption - the no port traffic may be from some other cause.
>=20
> One can't evaluate the comparative strength of error detection methods =
without knowing something about the kind of errors expected, the rate =
they occur at and the acceptable rate of undetected error.
>=20
> If the error mechanism is an alpha particle corrupting a bit in =
un-parity checked memory with a very low BER so that the likelihood of =
two bits in a packet having 2 errors is below the goal for undetected =
errors, any of the checksum algorithms or any CRC will catch a single =
bit error. =20
> On the other hand, if the memory is parity protected, it will catch =
the single bit error itself
>=20
> If the goal is catching burst errors of less than 32 bits or multiple =
single bit errors, Fletcher will catch more of the errors than the plain =
checksum but not an order of magnitude better so if the plain checksum =
isn't good enough for the goal, one probably needs to go to a CRC (which =
gets a few orders of magnitude improvement) or a cryptographic integrity =
check.
>=20
> See RFC 3385.
>=20
> Pat
>=20
> -----Original Message-----
> From: routing-discussion [mailto:routing-discussion-bounces@ietf.org] =
On Behalf Of Stewart Bryant
> Sent: Wednesday, December 10, 2014 8:19 AM
> To: l.wood@surrey.ac.uk; akatlas@gmail.com; =
routing-discussion@ietf.org
> Subject: dataplane encapsulation considerations - checksums
>=20
> Changing the thread title to match the subject
>=20
> Lloyd
>=20
> Those numbers are orders of magnitude larger than anything I have
> seen elsewhere.
>=20
> If we look at them in detail they are interesting because if the no =
ports
> are c/s errors as you hypothesis, then only 1/3 of the errors are =
seemingly
> caught by the c/s. I would thus expect  you to be arguing strongly
> that we need to deprecate the existing c/s in favour of something
> much stronger such as fletcher, or ideally a crypto checksum.
> In the case of the link state IGPs we have operators that turn on
> link state security not for security but for the enhanced checksum
> and that seems to be what you need here in the host stacks.
>=20
> However we have another study that is worth looking at:
>=20
> https://www.verisigninc.com/assets/VRSN_Bitsquatting_TR_20120320.pdf
>=20
> This looks at the UDP c/s errors received by DNS servers, and they
> saw an error rate of 1 in 10^5. However if you read the detail there =
are=20
> some
> systematic effects going on, with a significant fraction seemingly due
> to transmit host stack problems which may be what you are seeing.
>=20
> Now I think all this points to two things, firstly from a perspective
> of a host the c/s looks inadequate and there may need to be a
> revision of the host stack.
>=20
> On the other hand the reported error rate for UDP that the paper
> reports is an over estimate of the error rate in the tunnel case since
> only an error in the IP and UDP header can cause misdelivery
> with all other errors reflecting themselves as payload errors which
> the payload error protection. Although I do note that they report
> some systematic effect in terms of bit position which may point either
> way.
>=20
> One other aspect of this, which is important in Routing, if we are =
seeing
> the error rates you imply are getting past the TCP c/s, surely the =
routing
> protocols will be importing long term errors into the routing =
subsystems
> (specifically BGP and LDP). Are people observing that and if so don't =
we
> need to fix it?
>=20
> - Stewart
>=20
>=20
>=20
> On 10/12/2014 13:24, l.wood@surrey.ac.uk wrote:
>> Stewart,
>>=20
>> Who needs an NMS? Let's go old school.
>> TCP and UDP have equivalent pseudo-header+payload ones complement =
checksums. So data from TCP can be considered as somewhat equivalent as =
the technology is the same, and TCP is somewhat better instrumented and =
monitored than UDP is.
>>=20
>> Below sample from two core switches, on tcp connections to them  =
(not, alas, through them) shows e.g. 10287 TCP checksum errors for 4.3 =
million TCP/IP packets received. That would be an error rate of 0.24% - =
the other switch is 0.45% . Note the figure of e.g. 19458 no port - =
entirely possible something inside the core network is trying a port =
that isn't there, but also possible corruption of port nos. These are =
firewalled core devices with limited traffic to them, so I would =
consider this a best case, without throwing edge device data into the =
mix.
>>=20
>> Extrapolating from TCP checksum rates to UDP checksum rates, from =
traffic to to traffic through, and from v4 to v6 is left as an exercise =
for the reader.
>>=20
>> Incidentally, these rates pretty much match the 1 in 400 observation =
made early in Stone's SIGCOMM 2000 paper. 1:400 is 10,000:4,000,000
>> =
http://conferences.sigcomm.org/sigcomm/2000/conf/paper/sigcomm2000-9-1.pdf=

>> Zut alors, quelle surprise, physics is still physics, this particular =
SIGCOMM paper is still valid.
>> Checksums fail because of corruption. But at least there's a checksum =
to catch the corruption. Sans checksums, the corruption is unnoticed.
>>=20
>> The main reason noone has seen misbehaviour with MPLS is because =
no-one is looking for or instrumenting for it. (Just like MPLS doesn't =
need TTL, because no-one ever sees MPLS routing loops, right?) Please go =
measure MPLS and report back.
>>=20
>> Traversing over UDP, as suggested in draft-ietf-mpls-in-udp and =
draft-ietf-tsvwg-gre-in-udp-encap, increases the scope for corruption =
across a longer path, rather than individual links - and the UDP =
checksum is an important last check.
>>=20
>> SWT1#sh tcp stat
>> Rcvd: 4332545 Total, 19458 no port
>>       10287 checksum error, 4959 bad offset, 0 too short
>>       62946 packets (2289083 bytes) in sequence
>>       93 dup packets (19167 bytes)
>>       34 partially dup packets (1878 bytes)
>>       107 out-of-order packets (17980 bytes)
>>       8 packets (8 bytes) with data after window
>>       0 packets after close
>>       0 window probe packets, 614 window update packets
>>       682 dup ack packets, 0 ack packets with unsend data
>>       179823 ack packets (37459618 bytes)
>> Sent: 2049509 Total, 0 urgent packets
>>       1774234 control packets (including 345 retransmitted)
>>       249103 data packets (37439059 bytes)
>>       308 data packets (41767 bytes) retransmitted
>>       46 data packets (4876 bytes) fastretransmitted
>>       25718 ack only packets (3764 delayed)
>>       0 window probe packets, 104 window update packets
>> 9649 Connections initiated, 1230 connections accepted, 10857 =
connections established
>> 1760675 Connections closed (including 30 dropped, 1749812 embryonic =
dropped)
>> 653 Total rxmt timeout, 9 connections dropped in rxmt timeout
>> 0 Keepalive timeout, 6 keepalive probe, 0 Connections dropped in =
keepalive
>>=20
>>=20
>> SWT2#sh tcp stat
>> Rcvd: 6370948 Total, 37608 no port
>>       28419 checksum error, 1749 bad offset, 0 too short
>>       181714 packets (3507560 bytes) in sequence
>>       130 dup packets (4925 bytes)
>>       164 partially dup packets (302 bytes)
>>       35 out-of-order packets (278 bytes)
>>       64 packets (4549 bytes) with data after window
>>       0 packets after close
>>       0 window probe packets, 2006 window update packets
>>       3865 dup ack packets, 0 ack packets with unsend data
>>       857922 ack packets (92503306 bytes)
>> Sent: 3793587 Total, 0 urgent packets
>>       2667720 control packets (including 215 retransmitted)
>>       1042867 data packets (92804839 bytes)
>>       1772 data packets (74842 bytes) retransmitted
>>       192 data packets (7176 bytes) fastretransmitted
>>       81025 ack only packets (15840 delayed)
>>       0 window probe packets, 19 window update packets
>> 28735 Connections initiated, 5928 connections accepted, 34638 =
connections established
>> 2626485 Connections closed (including 1349 dropped, 2591827 embryonic =
dropped)
>> 1987 Total rxmt timeout, 4 connections dropped in rxmt timeout
>> 0 Keepalive timeout, 0 keepalive probe, 0 Connections dropped in =
keepalive
>>=20
>> Lloyd Wood
>> http://about.me/lloydwood
>>=20
>> error-free modern networking technology? ha.
>=20
> _______________________________________________
> routing-discussion mailing list
> routing-discussion@ietf.org
> https://www.ietf.org/mailman/listinfo/routing-discussion
>=20
> _______________________________________________
> routing-discussion mailing list
> routing-discussion@ietf.org
> https://www.ietf.org/mailman/listinfo/routing-discussion


From nobody Wed Dec 10 13:16:00 2014
Return-Path: <akatlas@gmail.com>
X-Original-To: routing-discussion@ietfa.amsl.com
Delivered-To: routing-discussion@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 3067C1A86FC for <routing-discussion@ietfa.amsl.com>; Wed, 10 Dec 2014 13:15:55 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.999
X-Spam-Level: 
X-Spam-Status: No, score=-1.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, 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 b2IC0SBekuVX for <routing-discussion@ietfa.amsl.com>; Wed, 10 Dec 2014 13:15:51 -0800 (PST)
Received: from mail-yh0-x230.google.com (mail-yh0-x230.google.com [IPv6:2607:f8b0:4002:c01::230]) (using TLSv1 with cipher ECDHE-RSA-RC4-SHA (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 385AA1A0025 for <routing-discussion@ietf.org>; Wed, 10 Dec 2014 13:15:44 -0800 (PST)
Received: by mail-yh0-f48.google.com with SMTP id i57so1686817yha.35 for <routing-discussion@ietf.org>; Wed, 10 Dec 2014 13:15:43 -0800 (PST)
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=ZdQ/bMRthL7eSbEGCHadPIb3CwBZhpl1mdMLmVlMuC0=; b=SJvlTIG3PoPgvQbM/8oHN/RO4y05mGe2u9aSkiL9qBXJtcDzzk3bYthA1vFwK8CtM1 3wCT/LSwWWQ0En+jurANkUXE5Om5LPfL0XTTx/C6kbWbhsx0b1YTNT1XtLLNDnlIXZ/A 4BLSHYWmxOa3wTXC0F/P7GUgGRUl9+WRBkVnRBXyefpT3pr4N7dzGg7dd9duYb+HhW9z mBzdoX9/lMQ8Ga0OkdxIZuuLEF3d+wdF9D+DrRHBE8xvifv/72K5lKP1n4nPlHRh7RC5 HgZXShLFMZElnuQZ9N4zNMQTvCoyF4KLDlcSZFdtDyCkNEVTaLqm9PaMy8aDMulygXOk 0f/g==
MIME-Version: 1.0
X-Received: by 10.170.39.70 with SMTP id 67mr4503583ykh.36.1418246143443; Wed, 10 Dec 2014 13:15:43 -0800 (PST)
Received: by 10.170.136.132 with HTTP; Wed, 10 Dec 2014 13:15:43 -0800 (PST)
In-Reply-To: <A46D9C092EA46F489F135060986AD9FF0F8BD5B6@G6W2492.americas.hpqcorp.net>
References: <CAG4d1rd60hK8=WtYw-nid_Z7Z8+TvdzA52fNx3pFjND+eDWAfA@mail.gmail.com> <CAA=duU3boijLYXFKW4E-RU1fGhxH_xyAk7NJWqXTFL+896woBA@mail.gmail.com> <CAG4d1rfi=51fxsasu9qfz4=CQQuRSazW-6xoc-8gH5918j2Sxw@mail.gmail.com> <A46D9C092EA46F489F135060986AD9FF0F8BD5B6@G6W2492.americas.hpqcorp.net>
Date: Wed, 10 Dec 2014 16:15:43 -0500
Message-ID: <CAG4d1re0Pp4qM89vYpke6C4HhmzZ-UP8o2OXqpfx9TZrxq_p9Q@mail.gmail.com>
Subject: Re: routing area design team on dataplane encapsulation considerations
From: Alia Atlas <akatlas@gmail.com>
To: "Fedyk, Don" <don.fedyk@hp.com>
Content-Type: multipart/alternative; boundary=001a11379da29589010509e32964
Archived-At: http://mailarchive.ietf.org/arch/msg/routing-discussion/xolFGJw94VVOTs-Qw1_fZ8fDvi4
Cc: "routing-discussion@ietf.org" <routing-discussion@ietf.org>
X-BeenThere: routing-discussion@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: Routing Area General mailing list <routing-discussion.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/routing-discussion>, <mailto:routing-discussion-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/routing-discussion/>
List-Post: <mailto:routing-discussion@ietf.org>
List-Help: <mailto:routing-discussion-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/routing-discussion>, <mailto:routing-discussion-request@ietf.org?subject=subscribe>
X-List-Received-Date: Wed, 10 Dec 2014 21:15:56 -0000

--001a11379da29589010509e32964
Content-Type: text/plain; charset=UTF-8
Content-Transfer-Encoding: quoted-printable

Hi Don,

Thanks for the suggestion.  I expect that Pat Thaler will be able to help
out with pulling
in experts on these technologies if the design team decides that
comparisons are useful.
In general, I'm expecting a draft that discusses options and the different
considerations
(of which a list was included).

I don't intend to revisit or revise the charter now - particularly for
other examples of technology
to consider.  However, I'm certain that the design team is following the
thread and taking in
the good advice.

An initial draft from the design team is expected before Dallas.

Regards,
Alia

On Wed, Dec 10, 2014 at 3:10 PM, Fedyk, Don <don.fedyk@hp.com> wrote:

>  Hi Alia
>
>
>
> I think it would be good for the design team to  also include for
> reference comparisons of the L2 encapsulations from IEEE 802.1 such as
> Provider backbone Bridging(PBB) aka Mac-in-MAC and IEEE 802.1Qbp =E2=80=
=93 Equal
> Cost Multipath (ECMP)  (also a Mac-in-MAC encaps) which have some common
> properties with data plane encapsulations in general.  As with PWE the
> designers of these encapsulations have grappled with a lot of the same
> issues.
>
>
>
> One  addition to your list these L2 encapsulations  have specific support
> for multicast that can be utilized in the in the underlay data plane.
>
>
>
> Cheers,
> Don
>
>
>
> *From:* routing-discussion [mailto:routing-discussion-bounces@ietf.org] *=
On
> Behalf Of *Alia Atlas
> *Sent:* Wednesday, December 10, 2014 9:39 AM
> *To:* Andrew G. Malis
> *Cc:* routing-discussion@ietf.org
> *Subject:* Re: routing area design team on dataplane encapsulation
> considerations
>
>
>
> Hi Andy,
>
> Absolutely true.   I apologize for the oversight.   Psuedo-wires are
> another encapsulation that we can learn from.
>
> I expect the design team to be reaching out to get more insight on these
> different issues.
>
> Regards
> Alia
>
> On Dec 10, 2014 9:27 AM, "Andrew G. Malis" <agmalis@gmail.com> wrote:
>
> Alia,
>
>
>
> To hijack this discussion back to your original post, I'm very surprised
> to see no mention of PALS anywhere. We in PALS (and PWE3 before that) hav=
e
> plenty of experience with data plane encapsulations, and we already have
> solutions for a number of the issues in your list, including ECMP (RFC
> 6391), packet size and fragmentation (4623), OAM (5085 and others), and a
> draft on congestion considerations just in the process of finishing up. P=
Ws
> have been extremely successful in the marketplace. So I hope the design
> team keeps us in mind as well.
>
>
>
> Cheers,
>
> Andy
>
>
>
> On Tue, Dec 9, 2014 at 5:46 PM, Alia Atlas <akatlas@gmail.com> wrote:
>
> I have chartered a Routing Area Design Team to work on data-plane
> encapsulation considerations.
>
>
>
> I've bcc'd nvo3, sfc, bier, and rtgwg as the most directly relevant.
> Please keep any conversation in one place on routing-discussion.
>
>
>
> Erik Nordmark has kindly agreed to lead this design team.  The members of
> the design
>
> team are:
>
>
>
>   Albert Tian <albert.tian@ericsson.com>
>
>   Erik Nordmark <nordmark@sonic.net>
>   Jesse Gross <jgross@vmware.com>
>   Jon Hudson <jon.hudson@gmail.com>
>   Larry Kreeger (kreeger) <kreeger@cisco.com>
>   Pankaj Garg <Garg.Pankaj@microsoft.com>
>   Pat Thaler <pthaler@broadcom.com>
>   Tom Herbert <therbert@google.com>
>
>
>
> The mailing list, rgt-dt-encap-considerations@ietf.org, is closed but the
> archives are
>
> publicly available at:
>
>
> http://www.ietf.org/mail-archive/web/rtg-dt-encap-considerations/current/=
maillist.html
>
>
>
> The Design Team is chartered as follows:
>
>
>
> There have been multiple efforts over the years that have resulted in new
> or modified data plane behaviors involving encapsulations. That includes
> IETF efforts like MPLS, LISP, and TRILL but also industry efforts like
> Vxlan and NVGRE.  These collectively can be seen as a source of insight
> into the properties that data planes need to meet.  The IETF is currently
> working on potentially new encapsulations in NVO3 and SFC and considering
> working on BIER. In addition there is work on tunneling in the INT area.
>
> This is a short term design team chartered to collect and construct usefu=
l
> advice to parties working on new or modified data plane behaviors that
> include additional encapsulations.  The goal is for the group to document
> useful advice gathered from interacting with ongoing efforts.  An Interne=
t
> Draft will be produced for IETF92 to capture that advice, which will be
> discussed in RTGWG.
>
> Data plane encapsulations face a set of common issues such as:
>
>   * How to provide entropy for ECMP
>   * Issues around packet size and fragmentation/reassembly
>   * OAM - what support is needed in an encapsulation format?
>   * Security and privacy.
>   * QoS
>   * Congestion Considerations
>   * IPv6 header protection (non-zero UDP checksum over IPv6 issue)
>   * Extensibility - e.g., for evolving OAM, security, and/or congestion
> control
>   * Layering of multiple encapsulations e.g., SFC over NVO3 over BIER
>
>
>
> The design team will provide advice on those issues. The intention is tha=
t
> even where we have different encapsulations for different purposes carryi=
ng
> different data, each such encapsulation doesn=E2=80=99t have to reinvent =
the wheel
> for the above common issues.
>
> The design team will look across the routing area in particular at SFC,
> NVO3 and BIER. It will not be involved in comparing or analyzing any
> particular encapsulation formats proposed in those WGs and BoFs but inste=
ad
> focus on common advice.
>
>
>
> Regards,
>
> Alia
>
>
> _______________________________________________
> routing-discussion mailing list
> routing-discussion@ietf.org
> https://www.ietf.org/mailman/listinfo/routing-discussion
>
>
>

--001a11379da29589010509e32964
Content-Type: text/html; charset=UTF-8
Content-Transfer-Encoding: quoted-printable

<div dir=3D"ltr">Hi Don,<div><br></div><div>Thanks for the suggestion.=C2=
=A0 I expect that Pat Thaler will be able to help out with pulling</div><di=
v>in experts on these technologies if the design team decides that comparis=
ons are useful.</div><div>In general, I&#39;m expecting a draft that discus=
ses options and the different considerations=C2=A0</div><div>(of which a li=
st was included).</div><div><br></div><div>I don&#39;t intend to revisit or=
 revise the charter now - particularly for other examples of technology</di=
v><div>to consider.=C2=A0 However, I&#39;m certain that the design team is =
following the thread and taking in</div><div>the good advice.</div><div><br=
></div><div>An initial draft from the design team is expected before Dallas=
.</div><div><br></div><div>Regards,</div><div>Alia</div></div><div class=3D=
"gmail_extra"><br><div class=3D"gmail_quote">On Wed, Dec 10, 2014 at 3:10 P=
M, Fedyk, Don <span dir=3D"ltr">&lt;<a href=3D"mailto:don.fedyk@hp.com" tar=
get=3D"_blank">don.fedyk@hp.com</a>&gt;</span> wrote:<br><blockquote class=
=3D"gmail_quote" style=3D"margin:0 0 0 .8ex;border-left:1px #ccc solid;padd=
ing-left:1ex">





<div lang=3D"EN-US" link=3D"blue" vlink=3D"purple">
<div>
<p class=3D"MsoNormal"><span style=3D"font-size:11.0pt;font-family:&quot;Ca=
libri&quot;,&quot;sans-serif&quot;;color:#1f497d">Hi Alia<u></u><u></u></sp=
an></p>
<p class=3D"MsoNormal"><span style=3D"font-size:11.0pt;font-family:&quot;Ca=
libri&quot;,&quot;sans-serif&quot;;color:#1f497d"><u></u>=C2=A0<u></u></spa=
n></p>
<p class=3D"MsoNormal"><span style=3D"font-size:11.0pt;font-family:&quot;Ca=
libri&quot;,&quot;sans-serif&quot;;color:#1f497d">I think it would be good =
for the design team to =C2=A0also include for reference comparisons of the =
L2 encapsulations from IEEE 802.1 such as Provider backbone Bridging(PBB)
 aka Mac-in-MAC and IEEE 802.1Qbp =E2=80=93 Equal Cost Multipath (ECMP) =C2=
=A0(also a Mac-in-MAC encaps) which have some common properties with data p=
lane encapsulations in general.=C2=A0 As with PWE the designers of these en=
capsulations have grappled with a lot of the same
 issues. <u></u><u></u></span></p>
<p class=3D"MsoNormal"><span style=3D"font-size:11.0pt;font-family:&quot;Ca=
libri&quot;,&quot;sans-serif&quot;;color:#1f497d"><u></u>=C2=A0<u></u></spa=
n></p>
<p class=3D"MsoNormal"><span style=3D"font-size:11.0pt;font-family:&quot;Ca=
libri&quot;,&quot;sans-serif&quot;;color:#1f497d">One =C2=A0addition to you=
r list these L2 encapsulations =C2=A0have specific support for multicast th=
at can be utilized in the in the underlay data plane.
<u></u><u></u></span></p>
<p class=3D"MsoNormal"><span style=3D"font-size:11.0pt;font-family:&quot;Ca=
libri&quot;,&quot;sans-serif&quot;;color:#1f497d"><u></u>=C2=A0<u></u></spa=
n></p>
<p class=3D"MsoNormal"><span style=3D"font-size:11.0pt;font-family:&quot;Ca=
libri&quot;,&quot;sans-serif&quot;;color:#1f497d">Cheers,<br>
Don <u></u><u></u></span></p>
<p class=3D"MsoNormal"><span style=3D"font-size:11.0pt;font-family:&quot;Ca=
libri&quot;,&quot;sans-serif&quot;;color:#1f497d"><u></u>=C2=A0<u></u></spa=
n></p>
<div style=3D"border:none;border-left:solid blue 1.5pt;padding:0in 0in 0in =
4.0pt">
<div>
<div style=3D"border:none;border-top:solid #b5c4df 1.0pt;padding:3.0pt 0in =
0in 0in">
<p class=3D"MsoNormal"><b><span style=3D"font-size:10.0pt;font-family:&quot=
;Tahoma&quot;,&quot;sans-serif&quot;">From:</span></b><span style=3D"font-s=
ize:10.0pt;font-family:&quot;Tahoma&quot;,&quot;sans-serif&quot;"> routing-=
discussion [mailto:<a href=3D"mailto:routing-discussion-bounces@ietf.org" t=
arget=3D"_blank">routing-discussion-bounces@ietf.org</a>]
<b>On Behalf Of </b>Alia Atlas<br>
<b>Sent:</b> Wednesday, December 10, 2014 9:39 AM<br>
<b>To:</b> Andrew G. Malis<br>
<b>Cc:</b> <a href=3D"mailto:routing-discussion@ietf.org" target=3D"_blank"=
>routing-discussion@ietf.org</a><span class=3D""><br>
<b>Subject:</b> Re: routing area design team on dataplane encapsulation con=
siderations<u></u><u></u></span></span></p>
</div>
</div>
<p class=3D"MsoNormal"><u></u>=C2=A0<u></u></p>
<p>Hi Andy,<u></u><u></u></p><div><div class=3D"h5">
<p>Absolutely true.=C2=A0=C2=A0 I apologize for the oversight.=C2=A0=C2=A0 =
Psuedo-wires are another encapsulation that we can learn from.
<u></u><u></u></p>
<p>I expect the design team to be reaching out to get more insight on these=
 different issues.
<u></u><u></u></p>
<p>Regards <br>
Alia<u></u><u></u></p>
<div>
<p class=3D"MsoNormal">On Dec 10, 2014 9:27 AM, &quot;Andrew G. Malis&quot;=
 &lt;<a href=3D"mailto:agmalis@gmail.com" target=3D"_blank">agmalis@gmail.c=
om</a>&gt; wrote:<u></u><u></u></p>
<div>
<p class=3D"MsoNormal">Alia,<u></u><u></u></p>
<div>
<p class=3D"MsoNormal"><u></u>=C2=A0<u></u></p>
<div>
<p class=3D"MsoNormal">To hijack this discussion back to your original post=
, I&#39;m very surprised to see no mention of PALS anywhere. We in PALS (an=
d PWE3 before that) have plenty of experience with data plane encapsulation=
s, and we already have solutions for a
 number of the issues in your list, including ECMP (RFC 6391), packet size =
and fragmentation (4623), OAM (5085 and others), and a draft on congestion =
considerations just in the process of finishing up. PWs have been extremely=
 successful in the marketplace.
 So I hope the design team keeps us in mind as well.<u></u><u></u></p>
</div>
</div>
<div>
<p class=3D"MsoNormal"><u></u>=C2=A0<u></u></p>
</div>
<div>
<p class=3D"MsoNormal">Cheers,<u></u><u></u></p>
</div>
<div>
<p class=3D"MsoNormal">Andy<u></u><u></u></p>
</div>
</div>
<div>
<p class=3D"MsoNormal"><u></u>=C2=A0<u></u></p>
<div>
<p class=3D"MsoNormal">On Tue, Dec 9, 2014 at 5:46 PM, Alia Atlas &lt;<a hr=
ef=3D"mailto:akatlas@gmail.com" target=3D"_blank">akatlas@gmail.com</a>&gt;=
 wrote:<u></u><u></u></p>
<div>
<p class=3D"MsoNormal">I have chartered a Routing Area Design Team to work =
on data-plane encapsulation considerations.<u></u><u></u></p>
<div>
<p class=3D"MsoNormal"><u></u>=C2=A0<u></u></p>
</div>
<div>
<p class=3D"MsoNormal">I&#39;ve bcc&#39;d nvo3, sfc, bier, and rtgwg as the=
 most directly relevant.=C2=A0 Please keep any conversation in one place on=
 routing-discussion.<u></u><u></u></p>
<div>
<p class=3D"MsoNormal"><u></u>=C2=A0<u></u></p>
</div>
<div>
<p class=3D"MsoNormal">Erik Nordmark has kindly agreed to lead this design =
team.=C2=A0 The members of the design<u></u><u></u></p>
</div>
<div>
<p class=3D"MsoNormal">team are:<u></u><u></u></p>
</div>
<div>
<p class=3D"MsoNormal"><u></u>=C2=A0<u></u></p>
</div>
<div>
<div>
<p class=3D"MsoNormal"><span style=3D"font-size:10.0pt">=C2=A0 Albert Tian =
&lt;<a href=3D"mailto:albert.tian@ericsson.com" target=3D"_blank">albert.ti=
an@ericsson.com</a>&gt;<u></u><u></u></span></p>
</div>
<div>
<p class=3D"MsoNormal"><span style=3D"font-size:10.0pt">=C2=A0 Erik Nordmar=
k &lt;<a href=3D"mailto:nordmark@sonic.net" target=3D"_blank">nordmark@soni=
c.net</a>&gt;<br>
=C2=A0 Jesse Gross &lt;<a href=3D"mailto:jgross@vmware.com" target=3D"_blan=
k">jgross@vmware.com</a>&gt;<br>
=C2=A0 Jon Hudson &lt;<a href=3D"mailto:jon.hudson@gmail.com" target=3D"_bl=
ank">jon.hudson@gmail.com</a>&gt;<br>
=C2=A0 Larry Kreeger (kreeger) &lt;<a href=3D"mailto:kreeger@cisco.com" tar=
get=3D"_blank">kreeger@cisco.com</a>&gt;<br>
=C2=A0 Pankaj Garg &lt;<a href=3D"mailto:Garg.Pankaj@microsoft.com" target=
=3D"_blank">Garg.Pankaj@microsoft.com</a>&gt;<br>
=C2=A0 Pat Thaler &lt;<a href=3D"mailto:pthaler@broadcom.com" target=3D"_bl=
ank">pthaler@broadcom.com</a>&gt;<br>
=C2=A0 Tom Herbert &lt;<a href=3D"mailto:therbert@google.com" target=3D"_bl=
ank">therbert@google.com</a>&gt;<u></u><u></u></span></p>
</div>
</div>
<div>
<p class=3D"MsoNormal"><span style=3D"font-size:10.0pt"><u></u>=C2=A0<u></u=
></span></p>
</div>
<div>
<p class=3D"MsoNormal"><span style=3D"font-size:10.0pt">The mailing list, <=
a href=3D"mailto:rgt-dt-encap-considerations@ietf.org" target=3D"_blank">
rgt-dt-encap-considerations@ietf.org</a>, is closed but the archives are<u>=
</u><u></u></span></p>
</div>
<div>
<p class=3D"MsoNormal"><span style=3D"font-size:10.0pt">publicly available =
at:<u></u><u></u></span></p>
</div>
<div>
<p class=3D"MsoNormal"><span style=3D"font-size:10.0pt">=C2=A0 =C2=A0<a hre=
f=3D"http://www.ietf.org/mail-archive/web/rtg-dt-encap-considerations/curre=
nt/maillist.html" target=3D"_blank">http://www.ietf.org/mail-archive/web/rt=
g-dt-encap-considerations/current/maillist.html</a><u></u><u></u></span></p=
>
</div>
<div>
<p class=3D"MsoNormal"><span style=3D"font-size:10.0pt"><u></u>=C2=A0<u></u=
></span></p>
</div>
<div>
<p class=3D"MsoNormal"><span style=3D"font-size:10.0pt">The Design Team is =
chartered as follows:<u></u><u></u></span></p>
</div>
<div>
<p class=3D"MsoNormal"><span style=3D"font-size:10.0pt"><u></u>=C2=A0<u></u=
></span></p>
</div>
<div>
<p class=3D"MsoNormal">There have been multiple efforts over the years that=
 have resulted in new or modified data plane behaviors involving encapsulat=
ions. That includes IETF efforts like MPLS, LISP, and TRILL but also indust=
ry efforts like Vxlan and NVGRE.=C2=A0
 These collectively can be seen as a source of insight into the properties =
that data planes need to meet.=C2=A0 The IETF is currently working on poten=
tially new encapsulations in NVO3 and SFC and considering working on BIER. =
In addition there is work on tunneling
 in the INT area.<br>
<br>
This is a short term design team chartered to collect and construct useful =
advice to parties working on new or modified data plane behaviors that incl=
ude additional encapsulations.=C2=A0 The goal is for the group to document =
useful advice gathered from interacting
 with ongoing efforts.=C2=A0 An Internet Draft will be produced for IETF92 =
to capture that advice, which will be discussed in RTGWG.<br>
<br>
Data plane encapsulations face a set of common issues such as:<br>
<br>
=C2=A0 * How to provide entropy for ECMP<br>
=C2=A0 * Issues around packet size and fragmentation/reassembly<br>
=C2=A0 * OAM - what support is needed in an encapsulation format?<br>
=C2=A0 * Security and privacy.<br>
=C2=A0 *=C2=A0QoS<br>
=C2=A0 *=C2=A0Congestion Considerations<br>
=C2=A0 *=C2=A0IPv6 header protection (non-zero UDP checksum over IPv6 issue=
)<br>
=C2=A0 * Extensibility - e.g., for evolving OAM, security, and/or congestio=
n control<br>
=C2=A0 * Layering of multiple encapsulations e.g., SFC over NVO3 over BIER<=
u></u><u></u></p>
</div>
<div>
<p class=3D"MsoNormal"><u></u>=C2=A0<u></u></p>
</div>
<div>
<p class=3D"MsoNormal" style=3D"margin-bottom:12.0pt">The design team will =
provide advice on those issues. The intention is that even where we have di=
fferent encapsulations for different purposes carrying different data, each=
 such encapsulation doesn=E2=80=99t have to
 reinvent the wheel for the above common issues.<u></u><u></u></p>
</div>
<div>
<p class=3D"MsoNormal">The design team will look across the routing area in=
 particular at SFC, NVO3 and BIER. It will not be involved in comparing or =
analyzing any particular encapsulation formats proposed in those WGs and Bo=
Fs but instead focus on common advice.<u></u><u></u></p>
</div>
<div>
<p class=3D"MsoNormal"><u></u>=C2=A0<u></u></p>
</div>
<div>
<p class=3D"MsoNormal">Regards,<u></u><u></u></p>
</div>
<div>
<p class=3D"MsoNormal">Alia<u></u><u></u></p>
</div>
</div>
</div>
<p class=3D"MsoNormal" style=3D"margin-bottom:12.0pt"><br>
_______________________________________________<br>
routing-discussion mailing list<br>
<a href=3D"mailto:routing-discussion@ietf.org" target=3D"_blank">routing-di=
scussion@ietf.org</a><br>
<a href=3D"https://www.ietf.org/mailman/listinfo/routing-discussion" target=
=3D"_blank">https://www.ietf.org/mailman/listinfo/routing-discussion</a><u>=
</u><u></u></p>
</div>
<p class=3D"MsoNormal"><u></u>=C2=A0<u></u></p>
</div>
</div>
</div></div></div>
</div>
</div>

</blockquote></div><br></div>

--001a11379da29589010509e32964--


From nobody Mon Dec 15 09:11:40 2014
Return-Path: <Fred.L.Templin@boeing.com>
X-Original-To: routing-discussion@ietfa.amsl.com
Delivered-To: routing-discussion@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 813891A8709 for <routing-discussion@ietfa.amsl.com>; Mon, 15 Dec 2014 09:11:38 -0800 (PST)
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 hjkNsBsdVHUi for <routing-discussion@ietfa.amsl.com>; Mon, 15 Dec 2014 09:11:37 -0800 (PST)
Received: from slb-mbsout-01.boeing.com (slb-mbsout-01.boeing.com [130.76.64.128]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 3E3791A8707 for <routing-discussion@ietf.org>; Mon, 15 Dec 2014 09:11:37 -0800 (PST)
Received: from localhost (localhost [127.0.0.1]) by slb-mbsout-01.boeing.com (8.14.4/8.14.4/DOWNSTREAM_MBSOUT) with SMTP id sBFHBaCs010303; Mon, 15 Dec 2014 09:11:36 -0800
Received: from XCH-BLV-508.nw.nos.boeing.com (xch-blv-508.nw.nos.boeing.com [130.247.25.198]) by slb-mbsout-01.boeing.com (8.14.4/8.14.4/UPSTREAM_MBSOUT) with ESMTP id sBFHBSOm010177 (version=TLSv1/SSLv3 cipher=AES128-SHA bits=128 verify=OK) for <routing-discussion@ietf.org>; Mon, 15 Dec 2014 09:11:28 -0800
Received: from XCH-BLV-504.nw.nos.boeing.com ([169.254.4.76]) by XCH-BLV-508.nw.nos.boeing.com ([169.254.8.240]) with mapi id 14.03.0210.002; Mon, 15 Dec 2014 09:11:27 -0800
From: "Templin, Fred L" <Fred.L.Templin@boeing.com>
To: "routing-discussion@ietf.org" <routing-discussion@ietf.org>
Subject: dataplane encapsulation considerations - fragmentation
Thread-Topic: dataplane encapsulation considerations - fragmentation
Thread-Index: AdAYiIhT9EHTGl7tQtOB208XEDdpGw==
Date: Mon, 15 Dec 2014 17:11:26 +0000
Message-ID: <2134F8430051B64F815C691A62D9831832DB6BCC@XCH-BLV-504.nw.nos.boeing.com>
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/routing-discussion/UnOGzIJ2QSYlxN2y7y83KBl0xb8
X-BeenThere: routing-discussion@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: Routing Area General mailing list <routing-discussion.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/routing-discussion>, <mailto:routing-discussion-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/routing-discussion/>
List-Post: <mailto:routing-discussion@ietf.org>
List-Help: <mailto:routing-discussion-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/routing-discussion>, <mailto:routing-discussion-request@ietf.org?subject=subscribe>
X-List-Received-Date: Mon, 15 Dec 2014 17:11:38 -0000

Hi,

Moving this to a different thread, I believe AERO has a workable solution f=
or
fragmentation. See Section 3.12 of:

https://datatracker.ietf.org/doc/draft-templin-aerolink/

In this solution, AERO provides tunnel fragmentation which is neither fragm=
entation
of the encapsulated packet nor fragmentation of the payload packet. It uses=
 two
magic numbers (1280 and 1500) as fragmentation thesholds. It uses fragmenta=
tion
(only when necessary) to take care of the smalls and lets the bigs take car=
e of
themselves.

General observation - there seems to be efforts on tunneling spread far and=
 wide
across numerous IETF working groups. Can we somehow find a way to consolida=
te
the discussions in one place so we can emerge with a common solution?

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


From nobody Wed Dec 17 12:20:02 2014
Return-Path: <Fred.L.Templin@boeing.com>
X-Original-To: routing-discussion@ietfa.amsl.com
Delivered-To: routing-discussion@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 4AB8E1A1BD2 for <routing-discussion@ietfa.amsl.com>; Wed, 17 Dec 2014 12:19:59 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -4.21
X-Spam-Level: 
X-Spam-Status: No, score=-4.21 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, HTML_MESSAGE=0.001, 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 0VEtHvso9EoN for <routing-discussion@ietfa.amsl.com>; Wed, 17 Dec 2014 12:19:50 -0800 (PST)
Received: from stl-mbsout-02.boeing.com (stl-mbsout-02.boeing.com [130.76.96.170]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id BE3B21A874E for <routing-discussion@ietf.org>; Wed, 17 Dec 2014 12:19:50 -0800 (PST)
Received: from localhost (localhost [127.0.0.1]) by stl-mbsout-02.boeing.com (8.14.4/8.14.4/DOWNSTREAM_MBSOUT) with SMTP id sBHKJnJu031676; Wed, 17 Dec 2014 14:19:49 -0600
Received: from XCH-BLV-507.nw.nos.boeing.com (xch-blv-507.nw.nos.boeing.com [130.247.25.197]) by stl-mbsout-02.boeing.com (8.14.4/8.14.4/UPSTREAM_MBSOUT) with ESMTP id sBHKJhcd030995 (version=TLSv1/SSLv3 cipher=AES128-SHA bits=128 verify=OK); Wed, 17 Dec 2014 14:19:43 -0600
Received: from XCH-BLV-504.nw.nos.boeing.com ([169.254.4.76]) by XCH-BLV-507.nw.nos.boeing.com ([169.254.7.38]) with mapi id 14.03.0210.002; Wed, 17 Dec 2014 12:19:42 -0800
From: "Templin, Fred L" <Fred.L.Templin@boeing.com>
To: "Andrew G. Malis" <agmalis@gmail.com>, Alia Atlas <akatlas@gmail.com>
Subject: RE: routing area design team on dataplane encapsulation considerations
Thread-Topic: routing area design team on dataplane encapsulation considerations
Thread-Index: AQHQFIVYS+Vc5GmdKUesEJgvy/aQyJyUQgYg
Date: Wed, 17 Dec 2014 20:19:42 +0000
Message-ID: <2134F8430051B64F815C691A62D9831832DB87D6@XCH-BLV-504.nw.nos.boeing.com>
References: <CAG4d1rd60hK8=WtYw-nid_Z7Z8+TvdzA52fNx3pFjND+eDWAfA@mail.gmail.com> <CAA=duU3boijLYXFKW4E-RU1fGhxH_xyAk7NJWqXTFL+896woBA@mail.gmail.com>
In-Reply-To: <CAA=duU3boijLYXFKW4E-RU1fGhxH_xyAk7NJWqXTFL+896woBA@mail.gmail.com>
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: multipart/alternative; boundary="_000_2134F8430051B64F815C691A62D9831832DB87D6XCHBLV504nwnosb_"
MIME-Version: 1.0
X-TM-AS-MML: disable
Archived-At: http://mailarchive.ietf.org/arch/msg/routing-discussion/bbYqI1lHqDcaVRmcw6ZiKpXDqIU
Cc: "routing-discussion@ietf.org" <routing-discussion@ietf.org>
X-BeenThere: routing-discussion@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: Routing Area General mailing list <routing-discussion.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/routing-discussion>, <mailto:routing-discussion-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/routing-discussion/>
List-Post: <mailto:routing-discussion@ietf.org>
List-Help: <mailto:routing-discussion-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/routing-discussion>, <mailto:routing-discussion-request@ietf.org?subject=subscribe>
X-List-Received-Date: Wed, 17 Dec 2014 20:19:59 -0000

--_000_2134F8430051B64F815C691A62D9831832DB87D6XCHBLV504nwnosb_
Content-Type: text/plain; charset="utf-8"
Content-Transfer-Encoding: base64

SGkgQW5keSwNCg0KWW91IG1lbnRpb25lZCBwYWNrZXQgc2l6ZSBhbmQgZnJhZ21lbnRhdGlvbiB3
cnQgUkZDNDYyMywgYW5kIEkganVzdCB3YW50ZWQNCnRvIG5vdGUgdGhhdCB0aGUgaWRlYSBvZiB0
dW5uZWwgZnJhZ21lbnRhdGlvbiBnb2VzIGJhY2sgZXZlbiBlYXJsaWVyIHRoYW4gdGhhdA0KdG8g
U2VjdGlvbiAzLjEuNyBvZiBSRkMyNzY0IHdoaWNoIEkgc2VlIHRoYXQgeW91IGFyZSBhbHNvIGNv
LWF1dGhvciBvbi4gSSBoYXZlDQpjaXRlZCB0aGlzIGluIHNvbWUgb2YgbXkgZWFybGllciB3b3Jr
cy4NCg0KQUVSTyBpcyBhbHNvIHVzaW5nIHR1bm5lbCBmcmFnbWVudGF0aW9uIGluIHByZXR0eSBt
dWNoIHRoZSBzYW1lIHdheSwgZXhjZXB0DQp0aGF0IEFFUk8gaGFzIGEgY29tcHJlaGVuc2l2ZSBz
cGVjaWZpY2F0aW9uIGZvciB3aGVuIHRvIGZyYWdtZW50LCB3aGVuIG5vdA0KdG8gZnJhZ21lbnQs
IGhvdyB0byB0ZXN0IGlmIGZyYWdtZW50YXRpb24gaXMgbmVjZXNzYXJ5LCBhbmQgd2hhdCBwYWNr
ZXQgc2l6ZQ0KcmFuZ2VzIGFyZSBjYW5kaWRhdGVzIGZvciBmcmFnbWVudGF0aW9uLiBTbywgaW4g
YWRkaXRpb24gdG8geW91ciBlYXJsaWVyIHdvcmtzDQpJIGhvcGUgdGhlIGRlc2lnbiB0ZWFtIHdp
bGwgaGF2ZSBhIGxvb2sgYXQgdGhlIHBhY2tldCBzaXplIGFuZCBmcmFnbWVudGF0aW9uDQphc3Bl
Y3RzIG9mIEFFUk8uDQoNClRoYW5rcyDigJMgRnJlZA0KZnJlZC5sLnRlbXBsaW5AYm9laW5nLmNv
bQ0KDQpGcm9tOiByb3V0aW5nLWRpc2N1c3Npb24gW21haWx0bzpyb3V0aW5nLWRpc2N1c3Npb24t
Ym91bmNlc0BpZXRmLm9yZ10gT24gQmVoYWxmIE9mIEFuZHJldyBHLiBNYWxpcw0KU2VudDogV2Vk
bmVzZGF5LCBEZWNlbWJlciAxMCwgMjAxNCA2OjI3IEFNDQpUbzogQWxpYSBBdGxhcw0KQ2M6IHJv
dXRpbmctZGlzY3Vzc2lvbkBpZXRmLm9yZw0KU3ViamVjdDogUmU6IHJvdXRpbmcgYXJlYSBkZXNp
Z24gdGVhbSBvbiBkYXRhcGxhbmUgZW5jYXBzdWxhdGlvbiBjb25zaWRlcmF0aW9ucw0KDQpBbGlh
LA0KDQpUbyBoaWphY2sgdGhpcyBkaXNjdXNzaW9uIGJhY2sgdG8geW91ciBvcmlnaW5hbCBwb3N0
LCBJJ20gdmVyeSBzdXJwcmlzZWQgdG8gc2VlIG5vIG1lbnRpb24gb2YgUEFMUyBhbnl3aGVyZS4g
V2UgaW4gUEFMUyAoYW5kIFBXRTMgYmVmb3JlIHRoYXQpIGhhdmUgcGxlbnR5IG9mIGV4cGVyaWVu
Y2Ugd2l0aCBkYXRhIHBsYW5lIGVuY2Fwc3VsYXRpb25zLCBhbmQgd2UgYWxyZWFkeSBoYXZlIHNv
bHV0aW9ucyBmb3IgYSBudW1iZXIgb2YgdGhlIGlzc3VlcyBpbiB5b3VyIGxpc3QsIGluY2x1ZGlu
ZyBFQ01QIChSRkMgNjM5MSksIHBhY2tldCBzaXplIGFuZCBmcmFnbWVudGF0aW9uICg0NjIzKSwg
T0FNICg1MDg1IGFuZCBvdGhlcnMpLCBhbmQgYSBkcmFmdCBvbiBjb25nZXN0aW9uIGNvbnNpZGVy
YXRpb25zIGp1c3QgaW4gdGhlIHByb2Nlc3Mgb2YgZmluaXNoaW5nIHVwLiBQV3MgaGF2ZSBiZWVu
IGV4dHJlbWVseSBzdWNjZXNzZnVsIGluIHRoZSBtYXJrZXRwbGFjZS4gU28gSSBob3BlIHRoZSBk
ZXNpZ24gdGVhbSBrZWVwcyB1cyBpbiBtaW5kIGFzIHdlbGwuDQoNCkNoZWVycywNCkFuZHkNCg0K
T24gVHVlLCBEZWMgOSwgMjAxNCBhdCA1OjQ2IFBNLCBBbGlhIEF0bGFzIDxha2F0bGFzQGdtYWls
LmNvbTxtYWlsdG86YWthdGxhc0BnbWFpbC5jb20+PiB3cm90ZToNCkkgaGF2ZSBjaGFydGVyZWQg
YSBSb3V0aW5nIEFyZWEgRGVzaWduIFRlYW0gdG8gd29yayBvbiBkYXRhLXBsYW5lIGVuY2Fwc3Vs
YXRpb24gY29uc2lkZXJhdGlvbnMuDQoNCkkndmUgYmNjJ2QgbnZvMywgc2ZjLCBiaWVyLCBhbmQg
cnRnd2cgYXMgdGhlIG1vc3QgZGlyZWN0bHkgcmVsZXZhbnQuICBQbGVhc2Uga2VlcCBhbnkgY29u
dmVyc2F0aW9uIGluIG9uZSBwbGFjZSBvbiByb3V0aW5nLWRpc2N1c3Npb24uDQoNCkVyaWsgTm9y
ZG1hcmsgaGFzIGtpbmRseSBhZ3JlZWQgdG8gbGVhZCB0aGlzIGRlc2lnbiB0ZWFtLiAgVGhlIG1l
bWJlcnMgb2YgdGhlIGRlc2lnbg0KdGVhbSBhcmU6DQoNCiAgQWxiZXJ0IFRpYW4gPGFsYmVydC50
aWFuQGVyaWNzc29uLmNvbTxtYWlsdG86YWxiZXJ0LnRpYW5AZXJpY3Nzb24uY29tPj4NCiAgRXJp
ayBOb3JkbWFyayA8bm9yZG1hcmtAc29uaWMubmV0PG1haWx0bzpub3JkbWFya0Bzb25pYy5uZXQ+
Pg0KICBKZXNzZSBHcm9zcyA8amdyb3NzQHZtd2FyZS5jb208bWFpbHRvOmpncm9zc0B2bXdhcmUu
Y29tPj4NCiAgSm9uIEh1ZHNvbiA8am9uLmh1ZHNvbkBnbWFpbC5jb208bWFpbHRvOmpvbi5odWRz
b25AZ21haWwuY29tPj4NCiAgTGFycnkgS3JlZWdlciAoa3JlZWdlcikgPGtyZWVnZXJAY2lzY28u
Y29tPG1haWx0bzprcmVlZ2VyQGNpc2NvLmNvbT4+DQogIFBhbmthaiBHYXJnIDxHYXJnLlBhbmth
akBtaWNyb3NvZnQuY29tPG1haWx0bzpHYXJnLlBhbmthakBtaWNyb3NvZnQuY29tPj4NCiAgUGF0
IFRoYWxlciA8cHRoYWxlckBicm9hZGNvbS5jb208bWFpbHRvOnB0aGFsZXJAYnJvYWRjb20uY29t
Pj4NCiAgVG9tIEhlcmJlcnQgPHRoZXJiZXJ0QGdvb2dsZS5jb208bWFpbHRvOnRoZXJiZXJ0QGdv
b2dsZS5jb20+Pg0KDQpUaGUgbWFpbGluZyBsaXN0LCByZ3QtZHQtZW5jYXAtY29uc2lkZXJhdGlv
bnNAaWV0Zi5vcmc8bWFpbHRvOnJndC1kdC1lbmNhcC1jb25zaWRlcmF0aW9uc0BpZXRmLm9yZz4s
IGlzIGNsb3NlZCBidXQgdGhlIGFyY2hpdmVzIGFyZQ0KcHVibGljbHkgYXZhaWxhYmxlIGF0Og0K
ICAgaHR0cDovL3d3dy5pZXRmLm9yZy9tYWlsLWFyY2hpdmUvd2ViL3J0Zy1kdC1lbmNhcC1jb25z
aWRlcmF0aW9ucy9jdXJyZW50L21haWxsaXN0Lmh0bWwNCg0KVGhlIERlc2lnbiBUZWFtIGlzIGNo
YXJ0ZXJlZCBhcyBmb2xsb3dzOg0KDQpUaGVyZSBoYXZlIGJlZW4gbXVsdGlwbGUgZWZmb3J0cyBv
dmVyIHRoZSB5ZWFycyB0aGF0IGhhdmUgcmVzdWx0ZWQgaW4gbmV3IG9yIG1vZGlmaWVkIGRhdGEg
cGxhbmUgYmVoYXZpb3JzIGludm9sdmluZyBlbmNhcHN1bGF0aW9ucy4gVGhhdCBpbmNsdWRlcyBJ
RVRGIGVmZm9ydHMgbGlrZSBNUExTLCBMSVNQLCBhbmQgVFJJTEwgYnV0IGFsc28gaW5kdXN0cnkg
ZWZmb3J0cyBsaWtlIFZ4bGFuIGFuZCBOVkdSRS4gIFRoZXNlIGNvbGxlY3RpdmVseSBjYW4gYmUg
c2VlbiBhcyBhIHNvdXJjZSBvZiBpbnNpZ2h0IGludG8gdGhlIHByb3BlcnRpZXMgdGhhdCBkYXRh
IHBsYW5lcyBuZWVkIHRvIG1lZXQuICBUaGUgSUVURiBpcyBjdXJyZW50bHkgd29ya2luZyBvbiBw
b3RlbnRpYWxseSBuZXcgZW5jYXBzdWxhdGlvbnMgaW4gTlZPMyBhbmQgU0ZDIGFuZCBjb25zaWRl
cmluZyB3b3JraW5nIG9uIEJJRVIuIEluIGFkZGl0aW9uIHRoZXJlIGlzIHdvcmsgb24gdHVubmVs
aW5nIGluIHRoZSBJTlQgYXJlYS4NCg0KVGhpcyBpcyBhIHNob3J0IHRlcm0gZGVzaWduIHRlYW0g
Y2hhcnRlcmVkIHRvIGNvbGxlY3QgYW5kIGNvbnN0cnVjdCB1c2VmdWwgYWR2aWNlIHRvIHBhcnRp
ZXMgd29ya2luZyBvbiBuZXcgb3IgbW9kaWZpZWQgZGF0YSBwbGFuZSBiZWhhdmlvcnMgdGhhdCBp
bmNsdWRlIGFkZGl0aW9uYWwgZW5jYXBzdWxhdGlvbnMuICBUaGUgZ29hbCBpcyBmb3IgdGhlIGdy
b3VwIHRvIGRvY3VtZW50IHVzZWZ1bCBhZHZpY2UgZ2F0aGVyZWQgZnJvbSBpbnRlcmFjdGluZyB3
aXRoIG9uZ29pbmcgZWZmb3J0cy4gIEFuIEludGVybmV0IERyYWZ0IHdpbGwgYmUgcHJvZHVjZWQg
Zm9yIElFVEY5MiB0byBjYXB0dXJlIHRoYXQgYWR2aWNlLCB3aGljaCB3aWxsIGJlIGRpc2N1c3Nl
ZCBpbiBSVEdXRy4NCg0KRGF0YSBwbGFuZSBlbmNhcHN1bGF0aW9ucyBmYWNlIGEgc2V0IG9mIGNv
bW1vbiBpc3N1ZXMgc3VjaCBhczoNCg0KICAqIEhvdyB0byBwcm92aWRlIGVudHJvcHkgZm9yIEVD
TVANCiAgKiBJc3N1ZXMgYXJvdW5kIHBhY2tldCBzaXplIGFuZCBmcmFnbWVudGF0aW9uL3JlYXNz
ZW1ibHkNCiAgKiBPQU0gLSB3aGF0IHN1cHBvcnQgaXMgbmVlZGVkIGluIGFuIGVuY2Fwc3VsYXRp
b24gZm9ybWF0Pw0KICAqIFNlY3VyaXR5IGFuZCBwcml2YWN5Lg0KICAqIFFvUw0KICAqIENvbmdl
c3Rpb24gQ29uc2lkZXJhdGlvbnMNCiAgKiBJUHY2IGhlYWRlciBwcm90ZWN0aW9uIChub24temVy
byBVRFAgY2hlY2tzdW0gb3ZlciBJUHY2IGlzc3VlKQ0KICAqIEV4dGVuc2liaWxpdHkgLSBlLmcu
LCBmb3IgZXZvbHZpbmcgT0FNLCBzZWN1cml0eSwgYW5kL29yIGNvbmdlc3Rpb24gY29udHJvbA0K
ICAqIExheWVyaW5nIG9mIG11bHRpcGxlIGVuY2Fwc3VsYXRpb25zIGUuZy4sIFNGQyBvdmVyIE5W
TzMgb3ZlciBCSUVSDQoNClRoZSBkZXNpZ24gdGVhbSB3aWxsIHByb3ZpZGUgYWR2aWNlIG9uIHRo
b3NlIGlzc3Vlcy4gVGhlIGludGVudGlvbiBpcyB0aGF0IGV2ZW4gd2hlcmUgd2UgaGF2ZSBkaWZm
ZXJlbnQgZW5jYXBzdWxhdGlvbnMgZm9yIGRpZmZlcmVudCBwdXJwb3NlcyBjYXJyeWluZyBkaWZm
ZXJlbnQgZGF0YSwgZWFjaCBzdWNoIGVuY2Fwc3VsYXRpb24gZG9lc27igJl0IGhhdmUgdG8gcmVp
bnZlbnQgdGhlIHdoZWVsIGZvciB0aGUgYWJvdmUgY29tbW9uIGlzc3Vlcy4NClRoZSBkZXNpZ24g
dGVhbSB3aWxsIGxvb2sgYWNyb3NzIHRoZSByb3V0aW5nIGFyZWEgaW4gcGFydGljdWxhciBhdCBT
RkMsIE5WTzMgYW5kIEJJRVIuIEl0IHdpbGwgbm90IGJlIGludm9sdmVkIGluIGNvbXBhcmluZyBv
ciBhbmFseXppbmcgYW55IHBhcnRpY3VsYXIgZW5jYXBzdWxhdGlvbiBmb3JtYXRzIHByb3Bvc2Vk
IGluIHRob3NlIFdHcyBhbmQgQm9GcyBidXQgaW5zdGVhZCBmb2N1cyBvbiBjb21tb24gYWR2aWNl
Lg0KDQpSZWdhcmRzLA0KQWxpYQ0KDQpfX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19f
X19fX19fX19fX19fXw0Kcm91dGluZy1kaXNjdXNzaW9uIG1haWxpbmcgbGlzdA0Kcm91dGluZy1k
aXNjdXNzaW9uQGlldGYub3JnPG1haWx0bzpyb3V0aW5nLWRpc2N1c3Npb25AaWV0Zi5vcmc+DQpo
dHRwczovL3d3dy5pZXRmLm9yZy9tYWlsbWFuL2xpc3RpbmZvL3JvdXRpbmctZGlzY3Vzc2lvbg0K
DQo=

--_000_2134F8430051B64F815C691A62D9831832DB87D6XCHBLV504nwnosb_
Content-Type: text/html; charset="utf-8"
Content-Transfer-Encoding: base64

PGh0bWwgeG1sbnM6dj0idXJuOnNjaGVtYXMtbWljcm9zb2Z0LWNvbTp2bWwiIHhtbG5zOm89InVy
bjpzY2hlbWFzLW1pY3Jvc29mdC1jb206b2ZmaWNlOm9mZmljZSIgeG1sbnM6dz0idXJuOnNjaGVt
YXMtbWljcm9zb2Z0LWNvbTpvZmZpY2U6d29yZCIgeG1sbnM6bT0iaHR0cDovL3NjaGVtYXMubWlj
cm9zb2Z0LmNvbS9vZmZpY2UvMjAwNC8xMi9vbW1sIiB4bWxucz0iaHR0cDovL3d3dy53My5vcmcv
VFIvUkVDLWh0bWw0MCI+DQo8aGVhZD4NCjxtZXRhIGh0dHAtZXF1aXY9IkNvbnRlbnQtVHlwZSIg
Y29udGVudD0idGV4dC9odG1sOyBjaGFyc2V0PXV0Zi04Ij4NCjxtZXRhIG5hbWU9IkdlbmVyYXRv
ciIgY29udGVudD0iTWljcm9zb2Z0IFdvcmQgMTUgKGZpbHRlcmVkIG1lZGl1bSkiPg0KPHN0eWxl
PjwhLS0NCi8qIEZvbnQgRGVmaW5pdGlvbnMgKi8NCkBmb250LWZhY2UNCgl7Zm9udC1mYW1pbHk6
V2luZ2RpbmdzOw0KCXBhbm9zZS0xOjUgMCAwIDAgMCAwIDAgMCAwIDA7fQ0KQGZvbnQtZmFjZQ0K
CXtmb250LWZhbWlseToiQ2FtYnJpYSBNYXRoIjsNCglwYW5vc2UtMToyIDQgNSAzIDUgNCA2IDMg
MiA0O30NCkBmb250LWZhY2UNCgl7Zm9udC1mYW1pbHk6Q2FsaWJyaTsNCglwYW5vc2UtMToyIDE1
IDUgMiAyIDIgNCAzIDIgNDt9DQovKiBTdHlsZSBEZWZpbml0aW9ucyAqLw0KcC5Nc29Ob3JtYWws
IGxpLk1zb05vcm1hbCwgZGl2Lk1zb05vcm1hbA0KCXttYXJnaW46MGluOw0KCW1hcmdpbi1ib3R0
b206LjAwMDFwdDsNCglmb250LXNpemU6MTIuMHB0Ow0KCWZvbnQtZmFtaWx5OiJUaW1lcyBOZXcg
Um9tYW4iLCJzZXJpZiI7fQ0KYTpsaW5rLCBzcGFuLk1zb0h5cGVybGluaw0KCXttc28tc3R5bGUt
cHJpb3JpdHk6OTk7DQoJY29sb3I6Ymx1ZTsNCgl0ZXh0LWRlY29yYXRpb246dW5kZXJsaW5lO30N
CmE6dmlzaXRlZCwgc3Bhbi5Nc29IeXBlcmxpbmtGb2xsb3dlZA0KCXttc28tc3R5bGUtcHJpb3Jp
dHk6OTk7DQoJY29sb3I6cHVycGxlOw0KCXRleHQtZGVjb3JhdGlvbjp1bmRlcmxpbmU7fQ0KcC5N
c29MaXN0UGFyYWdyYXBoLCBsaS5Nc29MaXN0UGFyYWdyYXBoLCBkaXYuTXNvTGlzdFBhcmFncmFw
aA0KCXttc28tc3R5bGUtcHJpb3JpdHk6MzQ7DQoJbWFyZ2luLXRvcDowaW47DQoJbWFyZ2luLXJp
Z2h0OjBpbjsNCgltYXJnaW4tYm90dG9tOjBpbjsNCgltYXJnaW4tbGVmdDouNWluOw0KCW1hcmdp
bi1ib3R0b206LjAwMDFwdDsNCglmb250LXNpemU6MTIuMHB0Ow0KCWZvbnQtZmFtaWx5OiJUaW1l
cyBOZXcgUm9tYW4iLCJzZXJpZiI7fQ0Kc3Bhbi5FbWFpbFN0eWxlMTcNCgl7bXNvLXN0eWxlLXR5
cGU6cGVyc29uYWw7DQoJZm9udC1mYW1pbHk6IkNhbGlicmkiLCJzYW5zLXNlcmlmIjsNCgljb2xv
cjojMUY0OTdEO30NCnNwYW4uRW1haWxTdHlsZTE5DQoJe21zby1zdHlsZS10eXBlOnBlcnNvbmFs
LWNvbXBvc2U7DQoJZm9udC1mYW1pbHk6IkNhbGlicmkiLCJzYW5zLXNlcmlmIjsNCgljb2xvcjp3
aW5kb3d0ZXh0O30NCi5Nc29DaHBEZWZhdWx0DQoJe21zby1zdHlsZS10eXBlOmV4cG9ydC1vbmx5
Ow0KCWZvbnQtZmFtaWx5OiJDYWxpYnJpIiwic2Fucy1zZXJpZiI7fQ0KQHBhZ2UgV29yZFNlY3Rp
b24xDQoJe3NpemU6OC41aW4gMTEuMGluOw0KCW1hcmdpbjoxLjBpbiAxLjBpbiAxLjBpbiAxLjBp
bjt9DQpkaXYuV29yZFNlY3Rpb24xDQoJe3BhZ2U6V29yZFNlY3Rpb24xO30NCi8qIExpc3QgRGVm
aW5pdGlvbnMgKi8NCkBsaXN0IGwwDQoJe21zby1saXN0LWlkOjE2MDU4NDgyODE7DQoJbXNvLWxp
c3QtdHlwZTpoeWJyaWQ7DQoJbXNvLWxpc3QtdGVtcGxhdGUtaWRzOi0yMTA2NDA1NjEwIC0yMzE5
ODkyNzIgNjc2OTg2OTEgNjc2OTg2OTMgNjc2OTg2ODkgNjc2OTg2OTEgNjc2OTg2OTMgNjc2OTg2
ODkgNjc2OTg2OTEgNjc2OTg2OTM7fQ0KQGxpc3QgbDA6bGV2ZWwxDQoJe21zby1sZXZlbC1zdGFy
dC1hdDowOw0KCW1zby1sZXZlbC1udW1iZXItZm9ybWF0OmJ1bGxldDsNCgltc28tbGV2ZWwtdGV4
dDrvg5g7DQoJbXNvLWxldmVsLXRhYi1zdG9wOm5vbmU7DQoJbXNvLWxldmVsLW51bWJlci1wb3Np
dGlvbjpsZWZ0Ow0KCXRleHQtaW5kZW50Oi0uMjVpbjsNCglmb250LWZhbWlseTpXaW5nZGluZ3M7
DQoJbXNvLWZhcmVhc3QtZm9udC1mYW1pbHk6Q2FsaWJyaTsNCgltc28tYmlkaS1mb250LWZhbWls
eToiVGltZXMgTmV3IFJvbWFuIjt9DQpAbGlzdCBsMDpsZXZlbDINCgl7bXNvLWxldmVsLW51bWJl
ci1mb3JtYXQ6YnVsbGV0Ow0KCW1zby1sZXZlbC10ZXh0Om87DQoJbXNvLWxldmVsLXRhYi1zdG9w
Om5vbmU7DQoJbXNvLWxldmVsLW51bWJlci1wb3NpdGlvbjpsZWZ0Ow0KCXRleHQtaW5kZW50Oi0u
MjVpbjsNCglmb250LWZhbWlseToiQ291cmllciBOZXciO30NCkBsaXN0IGwwOmxldmVsMw0KCXtt
c28tbGV2ZWwtbnVtYmVyLWZvcm1hdDpidWxsZXQ7DQoJbXNvLWxldmVsLXRleHQ674KnOw0KCW1z
by1sZXZlbC10YWItc3RvcDpub25lOw0KCW1zby1sZXZlbC1udW1iZXItcG9zaXRpb246bGVmdDsN
Cgl0ZXh0LWluZGVudDotLjI1aW47DQoJZm9udC1mYW1pbHk6V2luZ2RpbmdzO30NCkBsaXN0IGww
OmxldmVsNA0KCXttc28tbGV2ZWwtbnVtYmVyLWZvcm1hdDpidWxsZXQ7DQoJbXNvLWxldmVsLXRl
eHQ674K3Ow0KCW1zby1sZXZlbC10YWItc3RvcDpub25lOw0KCW1zby1sZXZlbC1udW1iZXItcG9z
aXRpb246bGVmdDsNCgl0ZXh0LWluZGVudDotLjI1aW47DQoJZm9udC1mYW1pbHk6U3ltYm9sO30N
CkBsaXN0IGwwOmxldmVsNQ0KCXttc28tbGV2ZWwtbnVtYmVyLWZvcm1hdDpidWxsZXQ7DQoJbXNv
LWxldmVsLXRleHQ6bzsNCgltc28tbGV2ZWwtdGFiLXN0b3A6bm9uZTsNCgltc28tbGV2ZWwtbnVt
YmVyLXBvc2l0aW9uOmxlZnQ7DQoJdGV4dC1pbmRlbnQ6LS4yNWluOw0KCWZvbnQtZmFtaWx5OiJD
b3VyaWVyIE5ldyI7fQ0KQGxpc3QgbDA6bGV2ZWw2DQoJe21zby1sZXZlbC1udW1iZXItZm9ybWF0
OmJ1bGxldDsNCgltc28tbGV2ZWwtdGV4dDrvgqc7DQoJbXNvLWxldmVsLXRhYi1zdG9wOm5vbmU7
DQoJbXNvLWxldmVsLW51bWJlci1wb3NpdGlvbjpsZWZ0Ow0KCXRleHQtaW5kZW50Oi0uMjVpbjsN
Cglmb250LWZhbWlseTpXaW5nZGluZ3M7fQ0KQGxpc3QgbDA6bGV2ZWw3DQoJe21zby1sZXZlbC1u
dW1iZXItZm9ybWF0OmJ1bGxldDsNCgltc28tbGV2ZWwtdGV4dDrvgrc7DQoJbXNvLWxldmVsLXRh
Yi1zdG9wOm5vbmU7DQoJbXNvLWxldmVsLW51bWJlci1wb3NpdGlvbjpsZWZ0Ow0KCXRleHQtaW5k
ZW50Oi0uMjVpbjsNCglmb250LWZhbWlseTpTeW1ib2w7fQ0KQGxpc3QgbDA6bGV2ZWw4DQoJe21z
by1sZXZlbC1udW1iZXItZm9ybWF0OmJ1bGxldDsNCgltc28tbGV2ZWwtdGV4dDpvOw0KCW1zby1s
ZXZlbC10YWItc3RvcDpub25lOw0KCW1zby1sZXZlbC1udW1iZXItcG9zaXRpb246bGVmdDsNCgl0
ZXh0LWluZGVudDotLjI1aW47DQoJZm9udC1mYW1pbHk6IkNvdXJpZXIgTmV3Ijt9DQpAbGlzdCBs
MDpsZXZlbDkNCgl7bXNvLWxldmVsLW51bWJlci1mb3JtYXQ6YnVsbGV0Ow0KCW1zby1sZXZlbC10
ZXh0Ou+CpzsNCgltc28tbGV2ZWwtdGFiLXN0b3A6bm9uZTsNCgltc28tbGV2ZWwtbnVtYmVyLXBv
c2l0aW9uOmxlZnQ7DQoJdGV4dC1pbmRlbnQ6LS4yNWluOw0KCWZvbnQtZmFtaWx5OldpbmdkaW5n
czt9DQpvbA0KCXttYXJnaW4tYm90dG9tOjBpbjt9DQp1bA0KCXttYXJnaW4tYm90dG9tOjBpbjt9
DQotLT48L3N0eWxlPjwhLS1baWYgZ3RlIG1zbyA5XT48eG1sPg0KPG86c2hhcGVkZWZhdWx0cyB2
OmV4dD0iZWRpdCIgc3BpZG1heD0iMTAyNiIgLz4NCjwveG1sPjwhW2VuZGlmXS0tPjwhLS1baWYg
Z3RlIG1zbyA5XT48eG1sPg0KPG86c2hhcGVsYXlvdXQgdjpleHQ9ImVkaXQiPg0KPG86aWRtYXAg
djpleHQ9ImVkaXQiIGRhdGE9IjEiIC8+DQo8L286c2hhcGVsYXlvdXQ+PC94bWw+PCFbZW5kaWZd
LS0+DQo8L2hlYWQ+DQo8Ym9keSBsYW5nPSJFTi1VUyIgbGluaz0iYmx1ZSIgdmxpbms9InB1cnBs
ZSI+DQo8ZGl2IGNsYXNzPSJXb3JkU2VjdGlvbjEiPg0KPHAgY2xhc3M9Ik1zb05vcm1hbCI+PHNw
YW4gc3R5bGU9ImZvbnQtc2l6ZToxMS4wcHQ7Zm9udC1mYW1pbHk6JnF1b3Q7Q2FsaWJyaSZxdW90
OywmcXVvdDtzYW5zLXNlcmlmJnF1b3Q7O2NvbG9yOiMxRjQ5N0QiPkhpIEFuZHksPG86cD48L286
cD48L3NwYW4+PC9wPg0KPHAgY2xhc3M9Ik1zb05vcm1hbCI+PHNwYW4gc3R5bGU9ImZvbnQtc2l6
ZToxMS4wcHQ7Zm9udC1mYW1pbHk6JnF1b3Q7Q2FsaWJyaSZxdW90OywmcXVvdDtzYW5zLXNlcmlm
JnF1b3Q7O2NvbG9yOiMxRjQ5N0QiPjxvOnA+Jm5ic3A7PC9vOnA+PC9zcGFuPjwvcD4NCjxwIGNs
YXNzPSJNc29Ob3JtYWwiPjxzcGFuIHN0eWxlPSJmb250LXNpemU6MTEuMHB0O2ZvbnQtZmFtaWx5
OiZxdW90O0NhbGlicmkmcXVvdDssJnF1b3Q7c2Fucy1zZXJpZiZxdW90Oztjb2xvcjojMUY0OTdE
Ij5Zb3UgbWVudGlvbmVkIHBhY2tldCBzaXplIGFuZCBmcmFnbWVudGF0aW9uIHdydCBSRkM0NjIz
LCBhbmQgSSBqdXN0IHdhbnRlZDxvOnA+PC9vOnA+PC9zcGFuPjwvcD4NCjxwIGNsYXNzPSJNc29O
b3JtYWwiPjxzcGFuIHN0eWxlPSJmb250LXNpemU6MTEuMHB0O2ZvbnQtZmFtaWx5OiZxdW90O0Nh
bGlicmkmcXVvdDssJnF1b3Q7c2Fucy1zZXJpZiZxdW90Oztjb2xvcjojMUY0OTdEIj50byBub3Rl
IHRoYXQgdGhlIGlkZWEgb2YgdHVubmVsIGZyYWdtZW50YXRpb24gZ29lcyBiYWNrIGV2ZW4gZWFy
bGllciB0aGFuIHRoYXQ8bzpwPjwvbzpwPjwvc3Bhbj48L3A+DQo8cCBjbGFzcz0iTXNvTm9ybWFs
Ij48c3BhbiBzdHlsZT0iZm9udC1zaXplOjExLjBwdDtmb250LWZhbWlseTomcXVvdDtDYWxpYnJp
JnF1b3Q7LCZxdW90O3NhbnMtc2VyaWYmcXVvdDs7Y29sb3I6IzFGNDk3RCI+dG8gU2VjdGlvbiAz
LjEuNyBvZiBSRkMyNzY0IHdoaWNoIEkgc2VlIHRoYXQgeW91IGFyZSBhbHNvIGNvLWF1dGhvciBv
bi4gSSBoYXZlPG86cD48L286cD48L3NwYW4+PC9wPg0KPHAgY2xhc3M9Ik1zb05vcm1hbCI+PHNw
YW4gc3R5bGU9ImZvbnQtc2l6ZToxMS4wcHQ7Zm9udC1mYW1pbHk6JnF1b3Q7Q2FsaWJyaSZxdW90
OywmcXVvdDtzYW5zLXNlcmlmJnF1b3Q7O2NvbG9yOiMxRjQ5N0QiPmNpdGVkIHRoaXMgaW4gc29t
ZSBvZiBteSBlYXJsaWVyIHdvcmtzLjxvOnA+PC9vOnA+PC9zcGFuPjwvcD4NCjxwIGNsYXNzPSJN
c29Ob3JtYWwiPjxzcGFuIHN0eWxlPSJmb250LXNpemU6MTEuMHB0O2ZvbnQtZmFtaWx5OiZxdW90
O0NhbGlicmkmcXVvdDssJnF1b3Q7c2Fucy1zZXJpZiZxdW90Oztjb2xvcjojMUY0OTdEIj48bzpw
PiZuYnNwOzwvbzpwPjwvc3Bhbj48L3A+DQo8cCBjbGFzcz0iTXNvTm9ybWFsIj48c3BhbiBzdHls
ZT0iZm9udC1zaXplOjExLjBwdDtmb250LWZhbWlseTomcXVvdDtDYWxpYnJpJnF1b3Q7LCZxdW90
O3NhbnMtc2VyaWYmcXVvdDs7Y29sb3I6IzFGNDk3RCI+QUVSTyBpcyBhbHNvIHVzaW5nIHR1bm5l
bCBmcmFnbWVudGF0aW9uIGluIHByZXR0eSBtdWNoIHRoZSBzYW1lIHdheSwgZXhjZXB0PG86cD48
L286cD48L3NwYW4+PC9wPg0KPHAgY2xhc3M9Ik1zb05vcm1hbCI+PHNwYW4gc3R5bGU9ImZvbnQt
c2l6ZToxMS4wcHQ7Zm9udC1mYW1pbHk6JnF1b3Q7Q2FsaWJyaSZxdW90OywmcXVvdDtzYW5zLXNl
cmlmJnF1b3Q7O2NvbG9yOiMxRjQ5N0QiPnRoYXQgQUVSTyBoYXMgYSBjb21wcmVoZW5zaXZlIHNw
ZWNpZmljYXRpb24gZm9yIHdoZW4gdG8gZnJhZ21lbnQsIHdoZW4gbm90PG86cD48L286cD48L3Nw
YW4+PC9wPg0KPHAgY2xhc3M9Ik1zb05vcm1hbCI+PHNwYW4gc3R5bGU9ImZvbnQtc2l6ZToxMS4w
cHQ7Zm9udC1mYW1pbHk6JnF1b3Q7Q2FsaWJyaSZxdW90OywmcXVvdDtzYW5zLXNlcmlmJnF1b3Q7
O2NvbG9yOiMxRjQ5N0QiPnRvIGZyYWdtZW50LCBob3cgdG8gdGVzdCBpZiBmcmFnbWVudGF0aW9u
IGlzIG5lY2Vzc2FyeSwgYW5kIHdoYXQgcGFja2V0IHNpemU8bzpwPjwvbzpwPjwvc3Bhbj48L3A+
DQo8cCBjbGFzcz0iTXNvTm9ybWFsIj48c3BhbiBzdHlsZT0iZm9udC1zaXplOjExLjBwdDtmb250
LWZhbWlseTomcXVvdDtDYWxpYnJpJnF1b3Q7LCZxdW90O3NhbnMtc2VyaWYmcXVvdDs7Y29sb3I6
IzFGNDk3RCI+cmFuZ2VzIGFyZSBjYW5kaWRhdGVzIGZvciBmcmFnbWVudGF0aW9uLiBTbywgaW4g
YWRkaXRpb24gdG8geW91ciBlYXJsaWVyIHdvcmtzPG86cD48L286cD48L3NwYW4+PC9wPg0KPHAg
Y2xhc3M9Ik1zb05vcm1hbCI+PHNwYW4gc3R5bGU9ImZvbnQtc2l6ZToxMS4wcHQ7Zm9udC1mYW1p
bHk6JnF1b3Q7Q2FsaWJyaSZxdW90OywmcXVvdDtzYW5zLXNlcmlmJnF1b3Q7O2NvbG9yOiMxRjQ5
N0QiPkkgaG9wZSB0aGUgZGVzaWduIHRlYW0gd2lsbCBoYXZlIGEgbG9vayBhdCB0aGUgcGFja2V0
IHNpemUgYW5kIGZyYWdtZW50YXRpb248bzpwPjwvbzpwPjwvc3Bhbj48L3A+DQo8cCBjbGFzcz0i
TXNvTm9ybWFsIj48c3BhbiBzdHlsZT0iZm9udC1zaXplOjExLjBwdDtmb250LWZhbWlseTomcXVv
dDtDYWxpYnJpJnF1b3Q7LCZxdW90O3NhbnMtc2VyaWYmcXVvdDs7Y29sb3I6IzFGNDk3RCI+YXNw
ZWN0cyBvZiBBRVJPLjxvOnA+PC9vOnA+PC9zcGFuPjwvcD4NCjxwIGNsYXNzPSJNc29Ob3JtYWwi
PjxzcGFuIHN0eWxlPSJmb250LXNpemU6MTEuMHB0O2ZvbnQtZmFtaWx5OiZxdW90O0NhbGlicmkm
cXVvdDssJnF1b3Q7c2Fucy1zZXJpZiZxdW90Oztjb2xvcjojMUY0OTdEIj48bzpwPiZuYnNwOzwv
bzpwPjwvc3Bhbj48L3A+DQo8cCBjbGFzcz0iTXNvTm9ybWFsIj48c3BhbiBzdHlsZT0iZm9udC1z
aXplOjExLjBwdDtmb250LWZhbWlseTomcXVvdDtDYWxpYnJpJnF1b3Q7LCZxdW90O3NhbnMtc2Vy
aWYmcXVvdDs7Y29sb3I6IzFGNDk3RCI+VGhhbmtzIOKAkyBGcmVkPG86cD48L286cD48L3NwYW4+
PC9wPg0KPHAgY2xhc3M9Ik1zb05vcm1hbCI+PHNwYW4gc3R5bGU9ImZvbnQtc2l6ZToxMS4wcHQ7
Zm9udC1mYW1pbHk6JnF1b3Q7Q2FsaWJyaSZxdW90OywmcXVvdDtzYW5zLXNlcmlmJnF1b3Q7O2Nv
bG9yOiMxRjQ5N0QiPmZyZWQubC50ZW1wbGluQGJvZWluZy5jb208bzpwPjwvbzpwPjwvc3Bhbj48
L3A+DQo8cCBjbGFzcz0iTXNvTm9ybWFsIj48c3BhbiBzdHlsZT0iZm9udC1zaXplOjExLjBwdDtm
b250LWZhbWlseTomcXVvdDtDYWxpYnJpJnF1b3Q7LCZxdW90O3NhbnMtc2VyaWYmcXVvdDs7Y29s
b3I6IzFGNDk3RCI+PG86cD4mbmJzcDs8L286cD48L3NwYW4+PC9wPg0KPGRpdiBzdHlsZT0iYm9y
ZGVyOm5vbmU7Ym9yZGVyLWxlZnQ6c29saWQgYmx1ZSAxLjVwdDtwYWRkaW5nOjBpbiAwaW4gMGlu
IDQuMHB0Ij4NCjxkaXY+DQo8ZGl2IHN0eWxlPSJib3JkZXI6bm9uZTtib3JkZXItdG9wOnNvbGlk
ICNFMUUxRTEgMS4wcHQ7cGFkZGluZzozLjBwdCAwaW4gMGluIDBpbiI+DQo8cCBjbGFzcz0iTXNv
Tm9ybWFsIj48Yj48c3BhbiBzdHlsZT0iZm9udC1zaXplOjExLjBwdDtmb250LWZhbWlseTomcXVv
dDtDYWxpYnJpJnF1b3Q7LCZxdW90O3NhbnMtc2VyaWYmcXVvdDsiPkZyb206PC9zcGFuPjwvYj48
c3BhbiBzdHlsZT0iZm9udC1zaXplOjExLjBwdDtmb250LWZhbWlseTomcXVvdDtDYWxpYnJpJnF1
b3Q7LCZxdW90O3NhbnMtc2VyaWYmcXVvdDsiPiByb3V0aW5nLWRpc2N1c3Npb24gW21haWx0bzpy
b3V0aW5nLWRpc2N1c3Npb24tYm91bmNlc0BpZXRmLm9yZ10NCjxiPk9uIEJlaGFsZiBPZiA8L2I+
QW5kcmV3IEcuIE1hbGlzPGJyPg0KPGI+U2VudDo8L2I+IFdlZG5lc2RheSwgRGVjZW1iZXIgMTAs
IDIwMTQgNjoyNyBBTTxicj4NCjxiPlRvOjwvYj4gQWxpYSBBdGxhczxicj4NCjxiPkNjOjwvYj4g
cm91dGluZy1kaXNjdXNzaW9uQGlldGYub3JnPGJyPg0KPGI+U3ViamVjdDo8L2I+IFJlOiByb3V0
aW5nIGFyZWEgZGVzaWduIHRlYW0gb24gZGF0YXBsYW5lIGVuY2Fwc3VsYXRpb24gY29uc2lkZXJh
dGlvbnM8bzpwPjwvbzpwPjwvc3Bhbj48L3A+DQo8L2Rpdj4NCjwvZGl2Pg0KPHAgY2xhc3M9Ik1z
b05vcm1hbCI+PG86cD4mbmJzcDs8L286cD48L3A+DQo8ZGl2Pg0KPHAgY2xhc3M9Ik1zb05vcm1h
bCI+QWxpYSw8bzpwPjwvbzpwPjwvcD4NCjxkaXY+DQo8cCBjbGFzcz0iTXNvTm9ybWFsIj48bzpw
PiZuYnNwOzwvbzpwPjwvcD4NCjxkaXY+DQo8cCBjbGFzcz0iTXNvTm9ybWFsIj5UbyBoaWphY2sg
dGhpcyBkaXNjdXNzaW9uIGJhY2sgdG8geW91ciBvcmlnaW5hbCBwb3N0LCBJJ20gdmVyeSBzdXJw
cmlzZWQgdG8gc2VlIG5vIG1lbnRpb24gb2YgUEFMUyBhbnl3aGVyZS4gV2UgaW4gUEFMUyAoYW5k
IFBXRTMgYmVmb3JlIHRoYXQpIGhhdmUgcGxlbnR5IG9mIGV4cGVyaWVuY2Ugd2l0aCBkYXRhIHBs
YW5lIGVuY2Fwc3VsYXRpb25zLCBhbmQgd2UgYWxyZWFkeSBoYXZlIHNvbHV0aW9ucyBmb3IgYQ0K
IG51bWJlciBvZiB0aGUgaXNzdWVzIGluIHlvdXIgbGlzdCwgaW5jbHVkaW5nIEVDTVAgKFJGQyA2
MzkxKSwgcGFja2V0IHNpemUgYW5kIGZyYWdtZW50YXRpb24gKDQ2MjMpLCBPQU0gKDUwODUgYW5k
IG90aGVycyksIGFuZCBhIGRyYWZ0IG9uIGNvbmdlc3Rpb24gY29uc2lkZXJhdGlvbnMganVzdCBp
biB0aGUgcHJvY2VzcyBvZiBmaW5pc2hpbmcgdXAuIFBXcyBoYXZlIGJlZW4gZXh0cmVtZWx5IHN1
Y2Nlc3NmdWwgaW4gdGhlIG1hcmtldHBsYWNlLg0KIFNvIEkgaG9wZSB0aGUgZGVzaWduIHRlYW0g
a2VlcHMgdXMgaW4gbWluZCBhcyB3ZWxsLjxvOnA+PC9vOnA+PC9wPg0KPC9kaXY+DQo8L2Rpdj4N
CjxkaXY+DQo8cCBjbGFzcz0iTXNvTm9ybWFsIj48bzpwPiZuYnNwOzwvbzpwPjwvcD4NCjwvZGl2
Pg0KPGRpdj4NCjxwIGNsYXNzPSJNc29Ob3JtYWwiPkNoZWVycyw8bzpwPjwvbzpwPjwvcD4NCjwv
ZGl2Pg0KPGRpdj4NCjxwIGNsYXNzPSJNc29Ob3JtYWwiPkFuZHk8bzpwPjwvbzpwPjwvcD4NCjwv
ZGl2Pg0KPC9kaXY+DQo8ZGl2Pg0KPHAgY2xhc3M9Ik1zb05vcm1hbCI+PG86cD4mbmJzcDs8L286
cD48L3A+DQo8ZGl2Pg0KPHAgY2xhc3M9Ik1zb05vcm1hbCI+T24gVHVlLCBEZWMgOSwgMjAxNCBh
dCA1OjQ2IFBNLCBBbGlhIEF0bGFzICZsdDs8YSBocmVmPSJtYWlsdG86YWthdGxhc0BnbWFpbC5j
b20iIHRhcmdldD0iX2JsYW5rIj5ha2F0bGFzQGdtYWlsLmNvbTwvYT4mZ3Q7IHdyb3RlOjxvOnA+
PC9vOnA+PC9wPg0KPGJsb2NrcXVvdGUgc3R5bGU9ImJvcmRlcjpub25lO2JvcmRlci1sZWZ0OnNv
bGlkICNDQ0NDQ0MgMS4wcHQ7cGFkZGluZzowaW4gMGluIDBpbiA2LjBwdDttYXJnaW4tbGVmdDo0
LjhwdDttYXJnaW4tcmlnaHQ6MGluIj4NCjxkaXY+DQo8cCBjbGFzcz0iTXNvTm9ybWFsIj5JIGhh
dmUgY2hhcnRlcmVkIGEgUm91dGluZyBBcmVhIERlc2lnbiBUZWFtIHRvIHdvcmsgb24gZGF0YS1w
bGFuZSBlbmNhcHN1bGF0aW9uIGNvbnNpZGVyYXRpb25zLjxvOnA+PC9vOnA+PC9wPg0KPGRpdj4N
CjxwIGNsYXNzPSJNc29Ob3JtYWwiPjxvOnA+Jm5ic3A7PC9vOnA+PC9wPg0KPC9kaXY+DQo8ZGl2
Pg0KPHAgY2xhc3M9Ik1zb05vcm1hbCI+SSd2ZSBiY2MnZCBudm8zLCBzZmMsIGJpZXIsIGFuZCBy
dGd3ZyBhcyB0aGUgbW9zdCBkaXJlY3RseSByZWxldmFudC4mbmJzcDsgUGxlYXNlIGtlZXAgYW55
IGNvbnZlcnNhdGlvbiBpbiBvbmUgcGxhY2Ugb24gcm91dGluZy1kaXNjdXNzaW9uLjxvOnA+PC9v
OnA+PC9wPg0KPGRpdj4NCjxwIGNsYXNzPSJNc29Ob3JtYWwiPjxvOnA+Jm5ic3A7PC9vOnA+PC9w
Pg0KPC9kaXY+DQo8ZGl2Pg0KPHAgY2xhc3M9Ik1zb05vcm1hbCI+RXJpayBOb3JkbWFyayBoYXMg
a2luZGx5IGFncmVlZCB0byBsZWFkIHRoaXMgZGVzaWduIHRlYW0uJm5ic3A7IFRoZSBtZW1iZXJz
IG9mIHRoZSBkZXNpZ248bzpwPjwvbzpwPjwvcD4NCjwvZGl2Pg0KPGRpdj4NCjxwIGNsYXNzPSJN
c29Ob3JtYWwiPnRlYW0gYXJlOjxvOnA+PC9vOnA+PC9wPg0KPC9kaXY+DQo8ZGl2Pg0KPHAgY2xh
c3M9Ik1zb05vcm1hbCI+PG86cD4mbmJzcDs8L286cD48L3A+DQo8L2Rpdj4NCjxkaXY+DQo8ZGl2
Pg0KPHAgY2xhc3M9Ik1zb05vcm1hbCI+PHNwYW4gc3R5bGU9ImZvbnQtc2l6ZToxMC4wcHQiPiZu
YnNwOyBBbGJlcnQgVGlhbiAmbHQ7PGEgaHJlZj0ibWFpbHRvOmFsYmVydC50aWFuQGVyaWNzc29u
LmNvbSIgdGFyZ2V0PSJfYmxhbmsiPmFsYmVydC50aWFuQGVyaWNzc29uLmNvbTwvYT4mZ3Q7PG86
cD48L286cD48L3NwYW4+PC9wPg0KPC9kaXY+DQo8ZGl2Pg0KPHAgY2xhc3M9Ik1zb05vcm1hbCI+
PHNwYW4gc3R5bGU9ImZvbnQtc2l6ZToxMC4wcHQiPiZuYnNwOyBFcmlrIE5vcmRtYXJrICZsdDs8
YSBocmVmPSJtYWlsdG86bm9yZG1hcmtAc29uaWMubmV0IiB0YXJnZXQ9Il9ibGFuayI+bm9yZG1h
cmtAc29uaWMubmV0PC9hPiZndDs8YnI+DQombmJzcDsgSmVzc2UgR3Jvc3MgJmx0OzxhIGhyZWY9
Im1haWx0bzpqZ3Jvc3NAdm13YXJlLmNvbSIgdGFyZ2V0PSJfYmxhbmsiPmpncm9zc0B2bXdhcmUu
Y29tPC9hPiZndDs8YnI+DQombmJzcDsgSm9uIEh1ZHNvbiAmbHQ7PGEgaHJlZj0ibWFpbHRvOmpv
bi5odWRzb25AZ21haWwuY29tIiB0YXJnZXQ9Il9ibGFuayI+am9uLmh1ZHNvbkBnbWFpbC5jb208
L2E+Jmd0Ozxicj4NCiZuYnNwOyBMYXJyeSBLcmVlZ2VyIChrcmVlZ2VyKSAmbHQ7PGEgaHJlZj0i
bWFpbHRvOmtyZWVnZXJAY2lzY28uY29tIiB0YXJnZXQ9Il9ibGFuayI+a3JlZWdlckBjaXNjby5j
b208L2E+Jmd0Ozxicj4NCiZuYnNwOyBQYW5rYWogR2FyZyAmbHQ7PGEgaHJlZj0ibWFpbHRvOkdh
cmcuUGFua2FqQG1pY3Jvc29mdC5jb20iIHRhcmdldD0iX2JsYW5rIj5HYXJnLlBhbmthakBtaWNy
b3NvZnQuY29tPC9hPiZndDs8YnI+DQombmJzcDsgUGF0IFRoYWxlciAmbHQ7PGEgaHJlZj0ibWFp
bHRvOnB0aGFsZXJAYnJvYWRjb20uY29tIiB0YXJnZXQ9Il9ibGFuayI+cHRoYWxlckBicm9hZGNv
bS5jb208L2E+Jmd0Ozxicj4NCiZuYnNwOyBUb20gSGVyYmVydCAmbHQ7PGEgaHJlZj0ibWFpbHRv
OnRoZXJiZXJ0QGdvb2dsZS5jb20iIHRhcmdldD0iX2JsYW5rIj50aGVyYmVydEBnb29nbGUuY29t
PC9hPiZndDs8bzpwPjwvbzpwPjwvc3Bhbj48L3A+DQo8L2Rpdj4NCjwvZGl2Pg0KPGRpdj4NCjxw
IGNsYXNzPSJNc29Ob3JtYWwiPjxzcGFuIHN0eWxlPSJmb250LXNpemU6MTAuMHB0Ij48bzpwPiZu
YnNwOzwvbzpwPjwvc3Bhbj48L3A+DQo8L2Rpdj4NCjxkaXY+DQo8cCBjbGFzcz0iTXNvTm9ybWFs
Ij48c3BhbiBzdHlsZT0iZm9udC1zaXplOjEwLjBwdCI+VGhlIG1haWxpbmcgbGlzdCwgPGEgaHJl
Zj0ibWFpbHRvOnJndC1kdC1lbmNhcC1jb25zaWRlcmF0aW9uc0BpZXRmLm9yZyIgdGFyZ2V0PSJf
YmxhbmsiPg0Kcmd0LWR0LWVuY2FwLWNvbnNpZGVyYXRpb25zQGlldGYub3JnPC9hPiwgaXMgY2xv
c2VkIGJ1dCB0aGUgYXJjaGl2ZXMgYXJlPG86cD48L286cD48L3NwYW4+PC9wPg0KPC9kaXY+DQo8
ZGl2Pg0KPHAgY2xhc3M9Ik1zb05vcm1hbCI+PHNwYW4gc3R5bGU9ImZvbnQtc2l6ZToxMC4wcHQi
PnB1YmxpY2x5IGF2YWlsYWJsZSBhdDo8bzpwPjwvbzpwPjwvc3Bhbj48L3A+DQo8L2Rpdj4NCjxk
aXY+DQo8cCBjbGFzcz0iTXNvTm9ybWFsIj48c3BhbiBzdHlsZT0iZm9udC1zaXplOjEwLjBwdCI+
Jm5ic3A7ICZuYnNwOzxhIGhyZWY9Imh0dHA6Ly93d3cuaWV0Zi5vcmcvbWFpbC1hcmNoaXZlL3dl
Yi9ydGctZHQtZW5jYXAtY29uc2lkZXJhdGlvbnMvY3VycmVudC9tYWlsbGlzdC5odG1sIiB0YXJn
ZXQ9Il9ibGFuayI+aHR0cDovL3d3dy5pZXRmLm9yZy9tYWlsLWFyY2hpdmUvd2ViL3J0Zy1kdC1l
bmNhcC1jb25zaWRlcmF0aW9ucy9jdXJyZW50L21haWxsaXN0Lmh0bWw8L2E+PG86cD48L286cD48
L3NwYW4+PC9wPg0KPC9kaXY+DQo8ZGl2Pg0KPHAgY2xhc3M9Ik1zb05vcm1hbCI+PHNwYW4gc3R5
bGU9ImZvbnQtc2l6ZToxMC4wcHQiPjxvOnA+Jm5ic3A7PC9vOnA+PC9zcGFuPjwvcD4NCjwvZGl2
Pg0KPGRpdj4NCjxwIGNsYXNzPSJNc29Ob3JtYWwiPjxzcGFuIHN0eWxlPSJmb250LXNpemU6MTAu
MHB0Ij5UaGUgRGVzaWduIFRlYW0gaXMgY2hhcnRlcmVkIGFzIGZvbGxvd3M6PG86cD48L286cD48
L3NwYW4+PC9wPg0KPC9kaXY+DQo8ZGl2Pg0KPHAgY2xhc3M9Ik1zb05vcm1hbCI+PHNwYW4gc3R5
bGU9ImZvbnQtc2l6ZToxMC4wcHQiPjxvOnA+Jm5ic3A7PC9vOnA+PC9zcGFuPjwvcD4NCjwvZGl2
Pg0KPGRpdj4NCjxwIGNsYXNzPSJNc29Ob3JtYWwiPlRoZXJlIGhhdmUgYmVlbiBtdWx0aXBsZSBl
ZmZvcnRzIG92ZXIgdGhlIHllYXJzIHRoYXQgaGF2ZSByZXN1bHRlZCBpbiBuZXcgb3IgbW9kaWZp
ZWQgZGF0YSBwbGFuZSBiZWhhdmlvcnMgaW52b2x2aW5nIGVuY2Fwc3VsYXRpb25zLiBUaGF0IGlu
Y2x1ZGVzIElFVEYgZWZmb3J0cyBsaWtlIE1QTFMsIExJU1AsIGFuZCBUUklMTCBidXQgYWxzbyBp
bmR1c3RyeSBlZmZvcnRzIGxpa2UgVnhsYW4gYW5kIE5WR1JFLiZuYnNwOw0KIFRoZXNlIGNvbGxl
Y3RpdmVseSBjYW4gYmUgc2VlbiBhcyBhIHNvdXJjZSBvZiBpbnNpZ2h0IGludG8gdGhlIHByb3Bl
cnRpZXMgdGhhdCBkYXRhIHBsYW5lcyBuZWVkIHRvIG1lZXQuJm5ic3A7IFRoZSBJRVRGIGlzIGN1
cnJlbnRseSB3b3JraW5nIG9uIHBvdGVudGlhbGx5IG5ldyBlbmNhcHN1bGF0aW9ucyBpbiBOVk8z
IGFuZCBTRkMgYW5kIGNvbnNpZGVyaW5nIHdvcmtpbmcgb24gQklFUi4gSW4gYWRkaXRpb24gdGhl
cmUgaXMgd29yayBvbiB0dW5uZWxpbmcNCiBpbiB0aGUgSU5UIGFyZWEuPGJyPg0KPGJyPg0KVGhp
cyBpcyBhIHNob3J0IHRlcm0gZGVzaWduIHRlYW0gY2hhcnRlcmVkIHRvIGNvbGxlY3QgYW5kIGNv
bnN0cnVjdCB1c2VmdWwgYWR2aWNlIHRvIHBhcnRpZXMgd29ya2luZyBvbiBuZXcgb3IgbW9kaWZp
ZWQgZGF0YSBwbGFuZSBiZWhhdmlvcnMgdGhhdCBpbmNsdWRlIGFkZGl0aW9uYWwgZW5jYXBzdWxh
dGlvbnMuJm5ic3A7IFRoZSBnb2FsIGlzIGZvciB0aGUgZ3JvdXAgdG8gZG9jdW1lbnQgdXNlZnVs
IGFkdmljZSBnYXRoZXJlZCBmcm9tIGludGVyYWN0aW5nDQogd2l0aCBvbmdvaW5nIGVmZm9ydHMu
Jm5ic3A7IEFuIEludGVybmV0IERyYWZ0IHdpbGwgYmUgcHJvZHVjZWQgZm9yIElFVEY5MiB0byBj
YXB0dXJlIHRoYXQgYWR2aWNlLCB3aGljaCB3aWxsIGJlIGRpc2N1c3NlZCBpbiBSVEdXRy48YnI+
DQo8YnI+DQpEYXRhIHBsYW5lIGVuY2Fwc3VsYXRpb25zIGZhY2UgYSBzZXQgb2YgY29tbW9uIGlz
c3VlcyBzdWNoIGFzOjxicj4NCjxicj4NCiZuYnNwOyAqIEhvdyB0byBwcm92aWRlIGVudHJvcHkg
Zm9yIEVDTVA8YnI+DQombmJzcDsgKiBJc3N1ZXMgYXJvdW5kIHBhY2tldCBzaXplIGFuZCBmcmFn
bWVudGF0aW9uL3JlYXNzZW1ibHk8YnI+DQombmJzcDsgKiBPQU0gLSB3aGF0IHN1cHBvcnQgaXMg
bmVlZGVkIGluIGFuIGVuY2Fwc3VsYXRpb24gZm9ybWF0Pzxicj4NCiZuYnNwOyAqIFNlY3VyaXR5
IGFuZCBwcml2YWN5Ljxicj4NCiZuYnNwOyAqJm5ic3A7UW9TPGJyPg0KJm5ic3A7ICombmJzcDtD
b25nZXN0aW9uIENvbnNpZGVyYXRpb25zPGJyPg0KJm5ic3A7ICombmJzcDtJUHY2IGhlYWRlciBw
cm90ZWN0aW9uIChub24temVybyBVRFAgY2hlY2tzdW0gb3ZlciBJUHY2IGlzc3VlKTxicj4NCiZu
YnNwOyAqIEV4dGVuc2liaWxpdHkgLSBlLmcuLCBmb3IgZXZvbHZpbmcgT0FNLCBzZWN1cml0eSwg
YW5kL29yIGNvbmdlc3Rpb24gY29udHJvbDxicj4NCiZuYnNwOyAqIExheWVyaW5nIG9mIG11bHRp
cGxlIGVuY2Fwc3VsYXRpb25zIGUuZy4sIFNGQyBvdmVyIE5WTzMgb3ZlciBCSUVSPG86cD48L286
cD48L3A+DQo8L2Rpdj4NCjxkaXY+DQo8cCBjbGFzcz0iTXNvTm9ybWFsIj48bzpwPiZuYnNwOzwv
bzpwPjwvcD4NCjwvZGl2Pg0KPGRpdj4NCjxwIGNsYXNzPSJNc29Ob3JtYWwiIHN0eWxlPSJtYXJn
aW4tYm90dG9tOjEyLjBwdCI+VGhlIGRlc2lnbiB0ZWFtIHdpbGwgcHJvdmlkZSBhZHZpY2Ugb24g
dGhvc2UgaXNzdWVzLiBUaGUgaW50ZW50aW9uIGlzIHRoYXQgZXZlbiB3aGVyZSB3ZSBoYXZlIGRp
ZmZlcmVudCBlbmNhcHN1bGF0aW9ucyBmb3IgZGlmZmVyZW50IHB1cnBvc2VzIGNhcnJ5aW5nIGRp
ZmZlcmVudCBkYXRhLCBlYWNoIHN1Y2ggZW5jYXBzdWxhdGlvbiBkb2VzbuKAmXQgaGF2ZSB0bw0K
IHJlaW52ZW50IHRoZSB3aGVlbCBmb3IgdGhlIGFib3ZlIGNvbW1vbiBpc3N1ZXMuPG86cD48L286
cD48L3A+DQo8L2Rpdj4NCjxkaXY+DQo8cCBjbGFzcz0iTXNvTm9ybWFsIj5UaGUgZGVzaWduIHRl
YW0gd2lsbCBsb29rIGFjcm9zcyB0aGUgcm91dGluZyBhcmVhIGluIHBhcnRpY3VsYXIgYXQgU0ZD
LCBOVk8zIGFuZCBCSUVSLiBJdCB3aWxsIG5vdCBiZSBpbnZvbHZlZCBpbiBjb21wYXJpbmcgb3Ig
YW5hbHl6aW5nIGFueSBwYXJ0aWN1bGFyIGVuY2Fwc3VsYXRpb24gZm9ybWF0cyBwcm9wb3NlZCBp
biB0aG9zZSBXR3MgYW5kIEJvRnMgYnV0IGluc3RlYWQgZm9jdXMgb24gY29tbW9uIGFkdmljZS48
bzpwPjwvbzpwPjwvcD4NCjwvZGl2Pg0KPGRpdj4NCjxwIGNsYXNzPSJNc29Ob3JtYWwiPjxvOnA+
Jm5ic3A7PC9vOnA+PC9wPg0KPC9kaXY+DQo8ZGl2Pg0KPHAgY2xhc3M9Ik1zb05vcm1hbCI+UmVn
YXJkcyw8bzpwPjwvbzpwPjwvcD4NCjwvZGl2Pg0KPGRpdj4NCjxwIGNsYXNzPSJNc29Ob3JtYWwi
PkFsaWE8bzpwPjwvbzpwPjwvcD4NCjwvZGl2Pg0KPC9kaXY+DQo8L2Rpdj4NCjxwIGNsYXNzPSJN
c29Ob3JtYWwiIHN0eWxlPSJtYXJnaW4tYm90dG9tOjEyLjBwdCI+PGJyPg0KX19fX19fX19fX19f
X19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX188YnI+DQpyb3V0aW5nLWRpc2N1c3Np
b24gbWFpbGluZyBsaXN0PGJyPg0KPGEgaHJlZj0ibWFpbHRvOnJvdXRpbmctZGlzY3Vzc2lvbkBp
ZXRmLm9yZyI+cm91dGluZy1kaXNjdXNzaW9uQGlldGYub3JnPC9hPjxicj4NCjxhIGhyZWY9Imh0
dHBzOi8vd3d3LmlldGYub3JnL21haWxtYW4vbGlzdGluZm8vcm91dGluZy1kaXNjdXNzaW9uIiB0
YXJnZXQ9Il9ibGFuayI+aHR0cHM6Ly93d3cuaWV0Zi5vcmcvbWFpbG1hbi9saXN0aW5mby9yb3V0
aW5nLWRpc2N1c3Npb248L2E+PG86cD48L286cD48L3A+DQo8L2Jsb2NrcXVvdGU+DQo8L2Rpdj4N
CjxwIGNsYXNzPSJNc29Ob3JtYWwiPjxvOnA+Jm5ic3A7PC9vOnA+PC9wPg0KPC9kaXY+DQo8L2Rp
dj4NCjwvZGl2Pg0KPC9ib2R5Pg0KPC9odG1sPg0K

--_000_2134F8430051B64F815C691A62D9831832DB87D6XCHBLV504nwnosb_--


From nobody Fri Dec 26 21:57:30 2014
Return-Path: <akatlas@gmail.com>
X-Original-To: routing-discussion@ietfa.amsl.com
Delivered-To: routing-discussion@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 34C0C1AD424 for <routing-discussion@ietfa.amsl.com>; Fri, 26 Dec 2014 21:57:29 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.999
X-Spam-Level: 
X-Spam-Status: No, score=-1.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, 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 3hpvMC3y0HBW for <routing-discussion@ietfa.amsl.com>; Fri, 26 Dec 2014 21:57:25 -0800 (PST)
Received: from mail-yk0-x22d.google.com (mail-yk0-x22d.google.com [IPv6:2607:f8b0:4002:c07::22d]) (using TLSv1 with cipher ECDHE-RSA-RC4-SHA (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 4395B1A1B7C for <routing-discussion@ietf.org>; Fri, 26 Dec 2014 21:57:25 -0800 (PST)
Received: by mail-yk0-f173.google.com with SMTP id 19so5350223ykq.4 for <routing-discussion@ietf.org>; Fri, 26 Dec 2014 21:57:24 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113;  h=mime-version:date:message-id:subject:from:to:content-type; bh=gDoTzY+fNHvDh984yQbBZZ8AuoeG14m8gmd010sxiAU=; b=hd9J3MUj2HeAdZOsL0pdlN7G2AuMpCfsecAaEeWllzYN/jZoAXXCADAoA61WW2Km/D PAIkDftuKpJxMG9zdpEmUGSWPYP/17ArJuMyDsfoG3qdXZp8rg2Wd14i4YKtz4ahM4Ml FEluJqs2fpmp4kQidmgv5JNKPD4MPlvi7k0I6JChN9EMtcFCjF584NnTxSWUZiKO+5+g mJNXpAlKlHvu/egBq6DGTQVpykWXmxi9ZMp+BKU2vE6cQVxHpdBSFkoVBEu6RiARF0kj rhYxEQC5xlnGEgr17MqBbvUKsgqqQG9Nxvb9jnq02rJAOxZUqswDHtqWJ46pzhNGn1G9 X4+Q==
MIME-Version: 1.0
X-Received: by 10.236.23.170 with SMTP id v30mr3167774yhv.25.1419659844449; Fri, 26 Dec 2014 21:57:24 -0800 (PST)
Received: by 10.170.133.18 with HTTP; Fri, 26 Dec 2014 21:57:24 -0800 (PST)
Date: Sat, 27 Dec 2014 00:57:24 -0500
Message-ID: <CAG4d1reqbAMX=0eVbLoZMOaKrs2Bg8DeyLYoUG+3fZKT10CwHg@mail.gmail.com>
Subject: Fwd: IETF areas re-organisation steps
From: Alia Atlas <akatlas@gmail.com>
To: "routing-discussion@ietf.org" <routing-discussion@ietf.org>
Content-Type: multipart/mixed; boundary=089e013a0c00bb143e050b2c50a8
Archived-At: http://mailarchive.ietf.org/arch/msg/routing-discussion/Qs2SEQY9XzILdlcHm8Or-8kHSAc
X-BeenThere: routing-discussion@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: Routing Area General mailing list <routing-discussion.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/routing-discussion>, <mailto:routing-discussion-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/routing-discussion/>
List-Post: <mailto:routing-discussion@ietf.org>
List-Help: <mailto:routing-discussion-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/routing-discussion>, <mailto:routing-discussion-request@ietf.org?subject=subscribe>
X-List-Received-Date: Sat, 27 Dec 2014 05:57:29 -0000

--089e013a0c00bb143e050b2c50a8
Content-Type: multipart/alternative; boundary=089e013a0c00bb1437050b2c50a6

--089e013a0c00bb1437050b2c50a6
Content-Type: text/plain; charset=UTF-8
Content-Transfer-Encoding: quoted-printable

FYI -  there is a healthy discussion going on on the ietf discussion list.
Conversation will continue well into January - so if you are catching up
after the new year, your comments will also be greatly valued and
appreciated.

Regards,
Alia


---------- Forwarded message ----------
From: Jari Arkko <jari.arkko@piuha.net>
Date: Thu, Dec 25, 2014 at 2:16 PM
Subject: IETF areas re-organisation steps
To: IETF Announcement List <ietf-announce@ietf.org>
Cc: IETF-Discussion list <ietf@ietf.org>


Dear Community:

In October, we let you know that we would be coming up with some proposals
and consulting with you on the topic of re-organizing the IESG and the IETF
areas with the intent to increase flexibility as IETF work evolves, to
ensure that
all IETF work is covered by an AD, and to balance and reduce the workload
across the ADs [1]. We committed to developing a re-organization proposal b=
y
May 2015 (thus including ADs that will be newly seated in March 2015). We
have taken several steps since then toward that goal: we recommended that
the
nomcom not to fill the APP AD vacancy in the current nomcom cycle [2], and
we
are taking steps to redistribute workload in order to allow for more
resources
to be focused on YANG model coordination [3].

This message provides an outline of further steps we propose to take in 201=
5
as part of the re-organization and invites community feedback on those
steps.
Step I below is already in progress. Step II in particular requires timely
action, and therefore we are requesting community feedback by January 15,
2015 on that step in particular and on the overall proposal.

None of the steps below should be viewed as permanent or overly constrainin=
g
how the IESG and the areas might be organized in future years. In general
we=E2=80=99d
like to increase the ability for the IESG to be flexible going forward. We
are
suggesting the steps below as measures to experiment with as a means to
determine their effectiveness. The IESG intends to continue to re-evaluate
all
of the steps on a regular basis.


PRINCIPLES

The IESG believes the re-organization should proceed according to the
following principles:

1) Agility: The IESG should be able to adapt as Internet engineering
evolves.
When work focus shifts and new technologies emerge, it is critical that the
the IESG can follow the shift and effectively manage the new work.

2) Relevance: The organization of the technical work must facilitate the
IETF's continued relevance to the industry. As we change how we develop
technology throughout the Internet, the IETF must be able to change how our
standards development works with the technology development.

3) Flexibility: The organization of the IESG and of the technical areas
should
accommodate variations in workloads, time commitments, and AD skillsets, as
well as changes in those over time. It is important to make it possible for
more IETF participants to be able to serve as Area Directors and to make th=
e
work co-exist with their normal jobs.

4) Sustainability: The Area Director role should be a position that
accomplished engineers aspire to and that employers want to support. We
should
emphasize the "steering" and "director" aspects, supporting and guiding the
technical work in the working groups.


THREE STEPS

We suggest taking the three steps described below to fulfill these
principles.


I.  FURTHER SHIFTING OF WG RESPONSIBILITY TO OUT-OF-AREA ADS

The ability to react to changes in the industry, for example the IESG YANG
Model Work Redistribution [3], requires flexibility within the IETF
leadership
positions. There are numerous instances where the constituency of a WG
exists
in a particular IETF area, but the most appropriate AD for that work happen=
s
to be in a different area, or where the ADs in the area are simply
overloaded
and an AD outside of the area is perfectly capable of managing the work. To
address these possibilities, the IESG is moving towards a model where a WG
can
exist in one area, but its shepherding AD comes from another area. This
flexibility will allow the IESG to apply its skills where they can be of
most
use while still keeping related WGs together within an area. The IESG
proposes
to experiment with this approach initially by shifting to out-of-area ADs
for
RADEXT, DIME, LMAP, and ANIMA, perhaps with another few WGs to follow.

In order to achieve the above, there is some tools development work needed.
Many components of the IETF tool set (e.g., the datatracker) make
assumptions
about WG/AD relationships based on the WG's assigned area. That issue is
currently being worked on by the tools team, but will take a few months'
time.
During this intermediate period (prior to the tools work completing), the
cross-area shepherding effort will be done informally by the IESG. This
informal approach will address:

a. Shepherding AD - Each WG will still have an AD assigned to it from its
area, referred to as the Home Area AD. The actual shepherding AD will be
temporarily listed as the Technical Advisor. The shepherding AD will be in
charge of all WG management issues. The IESG will develop a way to
explicitly
indicate the shepherding AD on the WG's charter page.

b. E-mail aliases - WG chairs and participants who wish to reach the ADs
for a
WG via the <foo>-ads tools aliases should explicitly include the AD listed
as
Technical Advisor for the WG.

c. Document shepherding - When a WG chair submits a publication request,
that
request will flow to the Home Area AD. The Home Area AD should then delegat=
e
shepherding responsibilities to the shepherding AD for handling.

d. Appeals - IETF participants should be directed to send any appeals
related
to the WG to the shepherding AD rather than the Home Area AD.


II.  ADDING A THIRD RTG AD

The IESG is considering requesting that the currently seated nomcom select
an
additional routing AD, such that two new routing ADs, rather than one, woul=
d
be seated for two-year terms in spring 2015. The reasoning behind this
request
is that the load in the RTG area is currently unsustainably high. The
placement of a third AD will have the effect of spreading that load such
that
the time requirement may now be more consistent with the work loads of ADs
in
other areas. The total number of ADs on the IESG would not change if the AP=
P
seat remains vacant.

This request is further justified by the considerable increase in
management-related work in the RTG area. Specifically, there are a lot of
new
YANG models being written. Although the coordination of YANG across the IET=
F
falls as the responsibility of the OPS ADs (specifically the Management AD)
it
is expected that the RTG ADs will need to work on an increasing number of
YANG
documents as well.

If an additional RTG AD were to be seated, the IESG would propose to move
three working groups from the INT area to the RTG area to balance AD loads:
L2TPEXT, LISP, and TRILL.

As with all of the proposed organizational changes, the IESG would expect t=
o
re-evaluate the need for this third RTG AD in future years and balance that
need against the need to have other skill sets or more generalist roles
represented on the IESG.

Work is underway to create support for this model in our process
documentation:
http://tools.ietf.org/html/draft-dawkins-iesg-one-or-more-04.


III.  MERGING OF UPPER LAYER PROTOCOL AREAS

As previously noted [1], a significant amount of the work that is going on
in
the APP area pertains to the web protocols, but that has a good deal of
crossover with work in RAI. There is also some crossover work between the
APP
and TSV areas. To accommodate these overlaps and provide better WG
management
across these three areas, the IESG is proposing to merge the APP, RAI, and
TSV
areas into one combined Network Applications (NAPP) area. From March
2015-March 2016, this combined area would be overseen by the five remaining
ADs from APP, RAI, and TSV, with some redistribution of WG shepherding
responsibilities among them to balance workloads. DISPATCH, TSVWG, and
APPSAWG
would continue to function much as they currently do.

The NAPP ADs would continue to encourage progress towards closure of the
many
WGs in the area that are close to completing their chartered work. As such,
the IESG would expect to request in the 2015-16 nomcom cycle a reduction in
NAPP AD headcount, yielding four seated NAPP ADs starting in March 2016. If
possible, we could reduce down to 4 NAPP ADs prior to that time and
re-assign
the fifth AD=E2=80=99s duties to further help balance IESG load.

Jari Arkko for the IESG


REFERENCES

[1] http://www.ietf.org/mail-archive/web/ietf-announce/current/msg13314.htm=
l
[2] http://www.ietf.org/mail-archive/web/ietf-announce/current/msg13364.htm=
l
[3] http://www.ietf.org/mail-archive/web/ietf-announce/current/msg13576.htm=
l

--089e013a0c00bb1437050b2c50a6
Content-Type: text/html; charset=UTF-8
Content-Transfer-Encoding: quoted-printable

<div dir=3D"ltr"><div>FYI - =C2=A0there is a healthy discussion going on on=
 the ietf discussion list.</div><div>Conversation will continue well into J=
anuary - so if you are catching up</div><div>after the new year, your comme=
nts will also be greatly valued and appreciated.</div><div><br></div><div>R=
egards,</div><div>Alia</div><div><br></div><br><div class=3D"gmail_quote">-=
--------- Forwarded message ----------<br>From: <b class=3D"gmail_sendernam=
e">Jari Arkko</b> <span dir=3D"ltr">&lt;<a href=3D"mailto:jari.arkko@piuha.=
net">jari.arkko@piuha.net</a>&gt;</span><br>Date: Thu, Dec 25, 2014 at 2:16=
 PM<br>Subject: IETF areas re-organisation steps<br>To: IETF Announcement L=
ist &lt;<a href=3D"mailto:ietf-announce@ietf.org">ietf-announce@ietf.org</a=
>&gt;<br>Cc: IETF-Discussion list &lt;<a href=3D"mailto:ietf@ietf.org">ietf=
@ietf.org</a>&gt;<br><br><br>Dear Community:<br>
<br>
In October, we let you know that we would be coming up with some proposals<=
br>
and consulting with you on the topic of re-organizing the IESG and the IETF=
<br>
areas with the intent to increase flexibility as IETF work evolves, to ensu=
re that<br>
all IETF work is covered by an AD, and to balance and reduce the workload<b=
r>
across the ADs [1]. We committed to developing a re-organization proposal b=
y<br>
May 2015 (thus including ADs that will be newly seated in March 2015). We<b=
r>
have taken several steps since then toward that goal: we recommended that t=
he<br>
nomcom not to fill the APP AD vacancy in the current nomcom cycle [2], and =
we<br>
are taking steps to redistribute workload in order to allow for more resour=
ces<br>
to be focused on YANG model coordination [3].<br>
<br>
This message provides an outline of further steps we propose to take in 201=
5<br>
as part of the re-organization and invites community feedback on those step=
s.<br>
Step I below is already in progress. Step II in particular requires timely<=
br>
action, and therefore we are requesting community feedback by January 15,<b=
r>
2015 on that step in particular and on the overall proposal.<br>
<br>
None of the steps below should be viewed as permanent or overly constrainin=
g<br>
how the IESG and the areas might be organized in future years. In general w=
e=E2=80=99d<br>
like to increase the ability for the IESG to be flexible going forward. We =
are<br>
suggesting the steps below as measures to experiment with as a means to<br>
determine their effectiveness. The IESG intends to continue to re-evaluate =
all<br>
of the steps on a regular basis.<br>
<br>
<br>
PRINCIPLES<br>
<br>
The IESG believes the re-organization should proceed according to the<br>
following principles:<br>
<br>
1) Agility: The IESG should be able to adapt as Internet engineering evolve=
s.<br>
When work focus shifts and new technologies emerge, it is critical that the=
<br>
the IESG can follow the shift and effectively manage the new work.<br>
<br>
2) Relevance: The organization of the technical work must facilitate the<br=
>
IETF&#39;s continued relevance to the industry. As we change how we develop=
<br>
technology throughout the Internet, the IETF must be able to change how our=
<br>
standards development works with the technology development.<br>
<br>
3) Flexibility: The organization of the IESG and of the technical areas sho=
uld<br>
accommodate variations in workloads, time commitments, and AD skillsets, as=
<br>
well as changes in those over time. It is important to make it possible for=
<br>
more IETF participants to be able to serve as Area Directors and to make th=
e<br>
work co-exist with their normal jobs.<br>
<br>
4) Sustainability: The Area Director role should be a position that<br>
accomplished engineers aspire to and that employers want to support. We sho=
uld<br>
emphasize the &quot;steering&quot; and &quot;director&quot; aspects, suppor=
ting and guiding the<br>
technical work in the working groups.<br>
<br>
<br>
THREE STEPS<br>
<br>
We suggest taking the three steps described below to fulfill these principl=
es.<br>
<br>
<br>
I.=C2=A0 FURTHER SHIFTING OF WG RESPONSIBILITY TO OUT-OF-AREA ADS<br>
<br>
The ability to react to changes in the industry, for example the IESG YANG<=
br>
Model Work Redistribution [3], requires flexibility within the IETF leaders=
hip<br>
positions. There are numerous instances where the constituency of a WG exis=
ts<br>
in a particular IETF area, but the most appropriate AD for that work happen=
s<br>
to be in a different area, or where the ADs in the area are simply overload=
ed<br>
and an AD outside of the area is perfectly capable of managing the work. To=
<br>
address these possibilities, the IESG is moving towards a model where a WG =
can<br>
exist in one area, but its shepherding AD comes from another area. This<br>
flexibility will allow the IESG to apply its skills where they can be of mo=
st<br>
use while still keeping related WGs together within an area. The IESG propo=
ses<br>
to experiment with this approach initially by shifting to out-of-area ADs f=
or<br>
RADEXT, DIME, LMAP, and ANIMA, perhaps with another few WGs to follow.<br>
<br>
In order to achieve the above, there is some tools development work needed.=
<br>
Many components of the IETF tool set (e.g., the datatracker) make assumptio=
ns<br>
about WG/AD relationships based on the WG&#39;s assigned area. That issue i=
s<br>
currently being worked on by the tools team, but will take a few months&#39=
; time.<br>
During this intermediate period (prior to the tools work completing), the<b=
r>
cross-area shepherding effort will be done informally by the IESG. This<br>
informal approach will address:<br>
<br>
a. Shepherding AD - Each WG will still have an AD assigned to it from its<b=
r>
area, referred to as the Home Area AD. The actual shepherding AD will be<br=
>
temporarily listed as the Technical Advisor. The shepherding AD will be in<=
br>
charge of all WG management issues. The IESG will develop a way to explicit=
ly<br>
indicate the shepherding AD on the WG&#39;s charter page.<br>
<br>
b. E-mail aliases - WG chairs and participants who wish to reach the ADs fo=
r a<br>
WG via the &lt;foo&gt;-ads tools aliases should explicitly include the AD l=
isted as<br>
Technical Advisor for the WG.<br>
<br>
c. Document shepherding - When a WG chair submits a publication request, th=
at<br>
request will flow to the Home Area AD. The Home Area AD should then delegat=
e<br>
shepherding responsibilities to the shepherding AD for handling.<br>
<br>
d. Appeals - IETF participants should be directed to send any appeals relat=
ed<br>
to the WG to the shepherding AD rather than the Home Area AD.<br>
<br>
<br>
II.=C2=A0 ADDING A THIRD RTG AD<br>
<br>
The IESG is considering requesting that the currently seated nomcom select =
an<br>
additional routing AD, such that two new routing ADs, rather than one, woul=
d<br>
be seated for two-year terms in spring 2015. The reasoning behind this requ=
est<br>
is that the load in the RTG area is currently unsustainably high. The<br>
placement of a third AD will have the effect of spreading that load such th=
at<br>
the time requirement may now be more consistent with the work loads of ADs =
in<br>
other areas. The total number of ADs on the IESG would not change if the AP=
P<br>
seat remains vacant.<br>
<br>
This request is further justified by the considerable increase in<br>
management-related work in the RTG area. Specifically, there are a lot of n=
ew<br>
YANG models being written. Although the coordination of YANG across the IET=
F<br>
falls as the responsibility of the OPS ADs (specifically the Management AD)=
 it<br>
is expected that the RTG ADs will need to work on an increasing number of Y=
ANG<br>
documents as well.<br>
<br>
If an additional RTG AD were to be seated, the IESG would propose to move<b=
r>
three working groups from the INT area to the RTG area to balance AD loads:=
<br>
L2TPEXT, LISP, and TRILL.<br>
<br>
As with all of the proposed organizational changes, the IESG would expect t=
o<br>
re-evaluate the need for this third RTG AD in future years and balance that=
<br>
need against the need to have other skill sets or more generalist roles<br>
represented on the IESG.<br>
<br>
Work is underway to create support for this model in our process documentat=
ion:<br>
<a href=3D"http://tools.ietf.org/html/draft-dawkins-iesg-one-or-more-04" ta=
rget=3D"_blank">http://tools.ietf.org/html/draft-dawkins-iesg-one-or-more-0=
4</a>.<br>
<br>
<br>
III.=C2=A0 MERGING OF UPPER LAYER PROTOCOL AREAS<br>
<br>
As previously noted [1], a significant amount of the work that is going on =
in<br>
the APP area pertains to the web protocols, but that has a good deal of<br>
crossover with work in RAI. There is also some crossover work between the A=
PP<br>
and TSV areas. To accommodate these overlaps and provide better WG manageme=
nt<br>
across these three areas, the IESG is proposing to merge the APP, RAI, and =
TSV<br>
areas into one combined Network Applications (NAPP) area. From March<br>
2015-March 2016, this combined area would be overseen by the five remaining=
<br>
ADs from APP, RAI, and TSV, with some redistribution of WG shepherding<br>
responsibilities among them to balance workloads. DISPATCH, TSVWG, and APPS=
AWG<br>
would continue to function much as they currently do.<br>
<br>
The NAPP ADs would continue to encourage progress towards closure of the ma=
ny<br>
WGs in the area that are close to completing their chartered work. As such,=
<br>
the IESG would expect to request in the 2015-16 nomcom cycle a reduction in=
<br>
NAPP AD headcount, yielding four seated NAPP ADs starting in March 2016. If=
<br>
possible, we could reduce down to 4 NAPP ADs prior to that time and re-assi=
gn<br>
the fifth AD=E2=80=99s duties to further help balance IESG load.<br>
<br>
Jari Arkko for the IESG<br>
<br>
<br>
REFERENCES<br>
<br>
[1] <a href=3D"http://www.ietf.org/mail-archive/web/ietf-announce/current/m=
sg13314.html" target=3D"_blank">http://www.ietf.org/mail-archive/web/ietf-a=
nnounce/current/msg13314.html</a><br>
[2] <a href=3D"http://www.ietf.org/mail-archive/web/ietf-announce/current/m=
sg13364.html" target=3D"_blank">http://www.ietf.org/mail-archive/web/ietf-a=
nnounce/current/msg13364.html</a><br>
[3] <a href=3D"http://www.ietf.org/mail-archive/web/ietf-announce/current/m=
sg13576.html" target=3D"_blank">http://www.ietf.org/mail-archive/web/ietf-a=
nnounce/current/msg13576.html</a><br>
</div><br></div>

--089e013a0c00bb1437050b2c50a6--
--089e013a0c00bb143e050b2c50a8
Content-Type: application/pgp-signature; name="signature.asc"
Content-Disposition: attachment; filename="signature.asc"
Content-Transfer-Encoding: base64
X-Attachment-Id: 9c12a0df32528ebc_0.1

LS0tLS1CRUdJTiBQR1AgU0lHTkFUVVJFLS0tLS0NCkNvbW1lbnQ6IEdQR1Rvb2xzIC0gaHR0cHM6
Ly9ncGd0b29scy5vcmcNCg0KaVFJY0JBRUJDZ0FHQlFKVW5HS0tBQW9KRU04MGdDVFFVNDZxVUM0
UC9pTmZxRFEveXdqMTJFV2ltZGVveHdYNQ0KZmhDUVFUV2ErTDRPZ2ZmYzhxamw2VTFIeHl1cU1S
b1pPNFFXbXMxZ3hyQUhCa2xsYVNYRXFpSmxHMGdOU3Bpaw0KUTlKL3pQV2NBRjg2ZUQrVkNoVGU2
WDNONUNUNFN1dGszVG5lL3hETkFyMzhBR1IyK1FqNlJtUTBHckFiMnUxbw0KU2hoS1RORkc5cGI4
UHlBbGw5WDJMaWFMcXhMSmRMV1Z6SkFNS2xTcHFnUG9YcVMxQUpQTEF4M1ZkY3dBME5FeA0KbTFt
L0I4QmNCVy93eG9CNjhBc3hEZnVIL3lmMSs5WlU5dUNJYW9VYzAyT0FVU0UwbzlUNGdDWHFnZWY5
OUxFSA0KKzRvQUtDcjVEeXBvRTFJMnpwV0xyWm5mYkxtWHdoWnVDT0cwajMxOGo1ZHIwMDkwWDVr
dmlKY1l1cTBMaldpSA0KVG9tVEN5amo2eE9CcE85dWE2a25uWVBITlhwY00yY1JqTDgwTlMzQVk5
R2ROSGdOQy80SU5uSVgwYUg3V0RzUw0Kd3NvNHlQNEZPSktqaHI5Q3ZYQStoNkZBU1N3NHlDQTFV
VmFSZG0xZEhUYXVlbkZNcS9sS1NFU05LaXZNYmFURA0KMWFMaXpoN3B6Q04yYVRvY201M2k2NStt
Y0c1Z0FQQ3d2M3Z6MWp5dzFtdWFrM3dzdDFzeWkrak9ZQ0wzL3pTNw0KK3M1UGpCMUxMZEhhUHJi
blF5UzhERmVyUndPK0U3eGl0OWRiOTVQRHZNa2xKRzlpbmZIMkZLcnUwNC9yU2hqQg0KVFFwTlNm
UUY4TlAxNUtIVDZ6OVNCaFFmNmJvMWZ3cWkrSzl4OXAzNU9MWC9CdnhPc2toTTdwSTh0YisvVnRi
OQ0KWmJocEdGUVkrVkpTdTU4NzNCQUcNCj1GN0VxDQotLS0tLUVORCBQR1AgU0lHTkFUVVJFLS0t
LS0NCg==
--089e013a0c00bb143e050b2c50a8--

