RE: Multiprotocol tunneling over UDP using AERO

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