Multiprotocol tunneling over UDP using AERO
"Templin, Fred L" <Fred.L.Templin@boeing.com> Tue, 02 December 2014 20:57 UTC
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, 02 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-discussion list yesterday. Follow-up discussion was then posted in two additional messages. 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 seems 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, 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
- Multiprotocol tunneling over UDP using AERO Templin, Fred L
- RE: Multiprotocol tunneling over UDP using AERO Adrian Farrel
- RE: Multiprotocol tunneling over UDP using AERO Templin, Fred L
- Multiprotocol tunneling over UDP using AERO Templin, Fred L
- Re: Multiprotocol tunneling over UDP using AERO l.wood
- Re: [tsvwg] Multiprotocol tunneling over UDP usin… Tom Herbert
- RE: Multiprotocol tunneling over UDP using AERO Templin, Fred L
- RE: [tsvwg] Multiprotocol tunneling over UDP usin… Templin, Fred L
- RE: Multiprotocol tunneling over UDP using AERO Templin, Fred L