Re: [Rtg-dt-encap-considerations] routing area design team on dataplane encapsulation considerations

"Larry Kreeger (kreeger)" <> Thu, 07 May 2015 16:43 UTC

Return-Path: <>
Received: from localhost ( []) by (Postfix) with ESMTP id A166B1A90C6; Thu, 7 May 2015 09:43:09 -0700 (PDT)
X-Virus-Scanned: amavisd-new at
X-Spam-Flag: NO
X-Spam-Score: -14.51
X-Spam-Status: No, score=-14.51 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, HTML_MESSAGE=0.001, 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 ([]) by localhost ( []) (amavisd-new, port 10024) with ESMTP id AOyJJoaR4Ta5; Thu, 7 May 2015 09:43:07 -0700 (PDT)
Received: from ( []) (using TLSv1 with cipher RC4-SHA (128/128 bits)) (No client certificate requested) by (Postfix) with ESMTPS id 17C0D1A19E9; Thu, 7 May 2015 09:43:07 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple;;; l=14685; q=dns/txt; s=iport; t=1431016989; x=1432226589; h=from:to:subject:date:message-id:references:in-reply-to: mime-version; bh=WJf1oVZguzieEu+aO/F/e9qAZsvrWxB0S71kc+H10zo=; b=jD0joHE4MfGdwwWCJ+Z/NW4obpFECPRqjjGCFCGw/xj3amuhmX71SsRv fnxt1nrmEBk77/6VAd3veC0NGkofPKQjxUhIMKZfbcdyck1MzVCcRoUqm uhFJR48crOc6IcB93GkL5LgTKgU2DZsYkjaDim0eWql69EhE3BPWwSqVj U=;
X-IronPort-Anti-Spam-Filtered: true
X-IronPort-AV: E=Sophos;i="5.13,384,1427760000"; d="scan'208,217";a="417889750"
Received: from ([]) by with ESMTP; 07 May 2015 16:43:08 +0000
Received: from ( []) by (8.14.5/8.14.5) with ESMTP id t47Gh6t4007365 (version=TLSv1/SSLv3 cipher=AES128-SHA bits=128 verify=FAIL); Thu, 7 May 2015 16:43:06 GMT
Received: from ([]) by ([]) with mapi id 14.03.0195.001; Thu, 7 May 2015 11:43:06 -0500
From: "Larry Kreeger (kreeger)" <>
To: Alia Atlas <>, "" <>, "" <>
Thread-Topic: [Rtg-dt-encap-considerations] routing area design team on dataplane encapsulation considerations
Thread-Index: AQHQFAIB9AftLv4vd0W9L13ZsyC06p0bwPaAgFW+SwCAAAD4AA==
Date: Thu, 7 May 2015 16:43:05 +0000
Message-ID: <>
References: <> <> <>
In-Reply-To: <>
Accept-Language: en-US
Content-Language: en-US
user-agent: Microsoft-MacOutlook/
x-originating-ip: []
Content-Type: multipart/alternative; boundary="_000_D170E3BD147CA1kreegerciscocom_"
MIME-Version: 1.0
Archived-At: <>
Subject: Re: [Rtg-dt-encap-considerations] routing area design team on dataplane encapsulation considerations
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: Routing Area Design Team on Encapsulation Considerations discussion list <>
List-Unsubscribe: <>, <>
List-Archive: <>
List-Post: <>
List-Help: <>
List-Subscribe: <>, <>
X-List-Received-Date: Thu, 07 May 2015 16:43:09 -0000

OK, apparently there is no actual alias for routing-discussion-chairs.  Trying again with rtgwg-chairs.

From: Larry Kreeger <<>>
Date: Thursday, May 7, 2015 9:39 AM
To: "<>" <<>>, Alia Atlas <<>>, "<>" <<>>
Subject: Re: [Rtg-dt-encap-considerations] routing area design team on dataplane encapsulation considerations

Hi RTGWG Chairs,

At the RTGWG meeting in Dallas, I thought it was decided for the WG to either adopt, or call to adopt this document.  Erik is getting ready to publish a new version.  Should he rename it as a WG draft before doing that?

Thanks, Larry

From: Alia Atlas <<>>
Date: Friday, March 13, 2015 1:16 PM
To: "<>" <<>>
Subject: Re: routing area design team on dataplane encapsulation considerations

This design team has delivered a internet-draft, draft-rtg-dt-encap-01.
This draft will be discussed in RTGWG at IETF 92.  I would encourage you to all
read it and send comments to rtgwg.  I'm certain that the draft will be refined
and improved.

I'd like to thank the design team for their excellent work in a short time-frame.
I hope that this draft encourages useful discussion and thought as we move forward
on various encapsulations.


On Tue, Dec 9, 2014 at 5:46 PM, Alia Atlas <<>> 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 <<>>
  Erik Nordmark <<>>
  Jesse Gross <<>>
  Jon Hudson <<>>
  Larry Kreeger (kreeger) <<>>
  Pankaj Garg <<>>
  Pat Thaler <<>>
  Tom Herbert <<>>

The mailing list,<>, is closed but the archives are
publicly available at:

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’t 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 instead focus on common advice.