Re: [Rtg-dt-encap-considerations] Proliferation of encapsulations ...

"Larry Kreeger (kreeger)" <> Thu, 21 May 2015 17:24 UTC

Return-Path: <>
Received: from localhost ( []) by (Postfix) with ESMTP id 789F01A00CC for <>; Thu, 21 May 2015 10:24:30 -0700 (PDT)
X-Virus-Scanned: amavisd-new at
X-Spam-Flag: NO
X-Spam-Score: -14.511
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 ([]) by localhost ( []) (amavisd-new, port 10024) with ESMTP id y1rFQDv6RUTZ for <>; Thu, 21 May 2015 10:24:28 -0700 (PDT)
Received: from ( []) (using TLSv1 with cipher RC4-SHA (128/128 bits)) (No client certificate requested) by (Postfix) with ESMTPS id 2E5CB1A010D for <>; Thu, 21 May 2015 10:23:31 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple;;; l=1454; q=dns/txt; s=iport; t=1432229011; x=1433438611; h=from:to:subject:date:message-id:references:in-reply-to: content-id:content-transfer-encoding:mime-version; bh=1EHoAPPEadRwN2GzJOfQyBbuqZPPqWNS1tLKleXpZvg=; b=TDvAZhnW+zKg0ZHDiKQZ0F8KuhTBmApcsxtOFw/FowbNMZOMXuGTZ5xP 2GaN8/EGLqRpH6UtcgJOwVT2KywHD0skLm8PA0qkq7VkslYqeAhlvHr9H aDFpguI8leCK3/Qqe/OhKs4Lc5wfon1S9HRg6pvlOL7RQi0ZWXjM8WYoo Y=;
X-IronPort-Anti-Spam-Filtered: true
X-IronPort-AV: E=Sophos;i="5.13,470,1427760000"; d="scan'208";a="152247621"
Received: from ([]) by with ESMTP/TLS/DHE-RSA-AES256-SHA; 21 May 2015 17:23:30 +0000
Received: from ( []) by (8.14.5/8.14.5) with ESMTP id t4LHNUQV017388 (version=TLSv1/SSLv3 cipher=AES128-SHA bits=128 verify=FAIL); Thu, 21 May 2015 17:23:30 GMT
Received: from ([]) by ([]) with mapi id 14.03.0195.001; Thu, 21 May 2015 12:23:30 -0500
From: "Larry Kreeger (kreeger)" <>
To: Erik Nordmark <>, "" <>
Thread-Topic: [Rtg-dt-encap-considerations] Proliferation of encapsulations ...
Thread-Index: AQHQk+l9vo6VGMhkcU6Qfrp6Gv4Zs52GjFiA
Date: Thu, 21 May 2015 17:23:29 +0000
Message-ID: <>
References: <>
In-Reply-To: <>
Accept-Language: en-US
Content-Language: en-US
user-agent: Microsoft-MacOutlook/
x-originating-ip: []
Content-Type: text/plain; charset="us-ascii"
Content-ID: <>
Content-Transfer-Encoding: quoted-printable
MIME-Version: 1.0
Archived-At: <>
Subject: Re: [Rtg-dt-encap-considerations] Proliferation of encapsulations ...
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, 21 May 2015 17:24:30 -0000

Hi Erik,

Where you wrote "where there might already exist an encapsulation over IP
or Ethernet." do you think it would be useful to name a couple of
examples?  e.g. are you referring to GRE or something else?

 - Larry

On 5/21/15 10:12 AM, "Erik Nordmark" <> wrote:

>Based on our discussion I propose adding this text to the scope section:
>"While the origin and focus of this document is the routing area and in
>particular NVO3, SFC, and BIER, the considerations apply to other
>encapsulations that are being defined in the IETF and elsewhere. There
>seems to be an increase in the number of encapsulations being defined to
>run over UDP, where there might already exist an encapsulation over IP
>or Ethernet. Feedback on how these considerations apply in those
>contexts is welcome."
>Once that is in place and the document is out I'll send a note to the
>IESG to raise awareness.
>In that note I'll include any examples we have. Is there something other
>than draft-xu-softwire-ip-in-udp and draft-ietf-trill-over-ip that we
>should use as examples?
>Based on how that goes I'll raise the "profileration of encapsulations"
>with the IAB later.
>    Erik
>Rtg-dt-encap-considerations mailing list